diff --git a/marked/Rel-16/29_series/29002/00965742b9d7c465ff2058c927ff2e6c_img.jpg b/marked/Rel-16/29_series/29002/00965742b9d7c465ff2058c927ff2e6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9133ea2bfefe067c88a00fdfa59fa534f0a754b5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/00965742b9d7c465ff2058c927ff2e6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00f2c3e750f540e26c3b5799d65b1c5484a33eaeb8aad0f91392325ee3b0b05e
+size 109379
diff --git a/marked/Rel-16/29_series/29002/031de8ea6c5568a02faffd59b5c337f7_img.jpg b/marked/Rel-16/29_series/29002/031de8ea6c5568a02faffd59b5c337f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93094cfb82022f36e8f965646d7d2da9b9372240
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/031de8ea6c5568a02faffd59b5c337f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:510db386bdc76087aaaa06a4102653f6af3a8f2d1bbbd266423a430c9be8b069
+size 125798
diff --git a/marked/Rel-16/29_series/29002/03309222b5fe7a7ea59f058201f46a78_img.jpg b/marked/Rel-16/29_series/29002/03309222b5fe7a7ea59f058201f46a78_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b3583325af4f938041dc1a4bb3c868eefa21a3a3
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/03309222b5fe7a7ea59f058201f46a78_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd5aced0c0c763ebb03d6827f5e448bd63401b14223065a2f58687654ae9fe56
+size 30272
diff --git a/marked/Rel-16/29_series/29002/03bef5405d97ca0e39305ead6376a8da_img.jpg b/marked/Rel-16/29_series/29002/03bef5405d97ca0e39305ead6376a8da_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9f6edd67d8dcd855c0f6f7031271845fa92f484
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/03bef5405d97ca0e39305ead6376a8da_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e54972c65e22006f39cc7b54e7e125c2be96146edcc1bc7d80ae3fe2f7be0770
+size 107863
diff --git a/marked/Rel-16/29_series/29002/050e99bf626cb208bd2646b0e0b80708_img.jpg b/marked/Rel-16/29_series/29002/050e99bf626cb208bd2646b0e0b80708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..798919866512433ceea8f657a0b6bfbff3d3ee40
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/050e99bf626cb208bd2646b0e0b80708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4aa89002254ddb148a9aaad56977596877d7ff74d32d45cd69a3365648070ac5
+size 13598
diff --git a/marked/Rel-16/29_series/29002/0577ff4803feb3ebe2ea861edefc99c8_img.jpg b/marked/Rel-16/29_series/29002/0577ff4803feb3ebe2ea861edefc99c8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1255599e9632e40069ac2b5e532d0c735122467
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0577ff4803feb3ebe2ea861edefc99c8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db161162578c4b71e95f402e2b39011e80c8260c7b24cb900456b5c2e44678b3
+size 118146
diff --git a/marked/Rel-16/29_series/29002/0629ebd517a3f52337d7d1087e06e07b_img.jpg b/marked/Rel-16/29_series/29002/0629ebd517a3f52337d7d1087e06e07b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3271ba89f4b298ca78289f56f0a86feff60ebf1e
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0629ebd517a3f52337d7d1087e06e07b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c9833c9f10c2f0498c2a53e08d7909b9f98d5d547f931b2326ba7efcede4a55
+size 15779
diff --git a/marked/Rel-16/29_series/29002/07ccb21f70641797dd02a891ced72b7e_img.jpg b/marked/Rel-16/29_series/29002/07ccb21f70641797dd02a891ced72b7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..530e261c9fcf8395c27383975c51a121a88cd1b5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/07ccb21f70641797dd02a891ced72b7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5c2f0205d8c99f8a93dca9f37fb4439355105910c427b6bd6be46b3f5c0cb2b
+size 15777
diff --git a/marked/Rel-16/29_series/29002/08246879b7e3340f5c7af67ca43e48ff_img.jpg b/marked/Rel-16/29_series/29002/08246879b7e3340f5c7af67ca43e48ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bf6963cfccffe125b36aec94c0aef7f7457ca4d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/08246879b7e3340f5c7af67ca43e48ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:970d5567ef8b60888e95b702054282d3dfc4caf67390c54630a104dbc4eb944d
+size 112099
diff --git a/marked/Rel-16/29_series/29002/08fe3e18ddb50f54361fd8af73781bf7_img.jpg b/marked/Rel-16/29_series/29002/08fe3e18ddb50f54361fd8af73781bf7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f615404df2ada315c04bcaeb0d83ee3b00b7cfa5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/08fe3e18ddb50f54361fd8af73781bf7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71acd1a474f92857dbe3e56aee1c4e3470458d9b91402101063f326420f84852
+size 103550
diff --git a/marked/Rel-16/29_series/29002/0ab41cb59d8d1227f6df86aaa7e9b093_img.jpg b/marked/Rel-16/29_series/29002/0ab41cb59d8d1227f6df86aaa7e9b093_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..44f13df6ba39139917de60a826d7be65630e6e0d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0ab41cb59d8d1227f6df86aaa7e9b093_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3650a0a3f415bf9cb1825415d0bd9d66e023e00bfdaeaae3a2c60fcec0a77a08
+size 118661
diff --git a/marked/Rel-16/29_series/29002/0c3b372a05c47c6225a71f3801035526_img.jpg b/marked/Rel-16/29_series/29002/0c3b372a05c47c6225a71f3801035526_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4db82524575d64aa4f63603ed1fc06e5d7d644cc
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0c3b372a05c47c6225a71f3801035526_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:83b9e6af7236d0c95aea425314370da25816445dade5f485df62881383eae01b
+size 49702
diff --git a/marked/Rel-16/29_series/29002/0e3bda106879c7cf2aff2a375fbb044a_img.jpg b/marked/Rel-16/29_series/29002/0e3bda106879c7cf2aff2a375fbb044a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a83d46259a70586b30966e14ce216e85d0e4ea2d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0e3bda106879c7cf2aff2a375fbb044a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d25beb006dfd5dcd8f9a2eb60126f3efc2a647382b45d126d94adb4e660a7fba
+size 83003
diff --git a/marked/Rel-16/29_series/29002/0e9742f79dd41bef90d8187d1716879b_img.jpg b/marked/Rel-16/29_series/29002/0e9742f79dd41bef90d8187d1716879b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9bc35dc9b7c29ec4d54cc670c027113d20394bd8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0e9742f79dd41bef90d8187d1716879b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:87da98cf26de8b9245aac832b37db3fc96c76948c7df3d41347555e0b457574d
+size 91207
diff --git a/marked/Rel-16/29_series/29002/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg b/marked/Rel-16/29_series/29002/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec8e03463e9d95e0396cd4250ae5807830b6a185
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/0fca2efbeef5c006cbab2fd86aca84d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9f660712136e7046176b63dbdfbc6308131c8c163007ea64600459004c6a6763
+size 15267
diff --git a/marked/Rel-16/29_series/29002/10b5f8259a1411e6de336da5a0e96bd7_img.jpg b/marked/Rel-16/29_series/29002/10b5f8259a1411e6de336da5a0e96bd7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e825febc1fce91c03b746ee2018c916c1464911
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/10b5f8259a1411e6de336da5a0e96bd7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c514ccb40c872195851cab6bcee9b8e1fec2882ddca69a27d2c95d22f428ec30
+size 64921
diff --git a/marked/Rel-16/29_series/29002/12280970bb3eea7f6fbdc08200d444c2_img.jpg b/marked/Rel-16/29_series/29002/12280970bb3eea7f6fbdc08200d444c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fed6ca1e480ecfc753ca79e2b8dd533de6dfb349
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/12280970bb3eea7f6fbdc08200d444c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f4246435fce1714e8c205e9d1a91bcabb7b51fb7c0c539e4398b4d7736e444a
+size 27587
diff --git a/marked/Rel-16/29_series/29002/1582c665ca9405e127473c291eaed480_img.jpg b/marked/Rel-16/29_series/29002/1582c665ca9405e127473c291eaed480_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3471f30f12b24e9cb06ddfe93cf8926090f42c70
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/1582c665ca9405e127473c291eaed480_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98dd10c0bff1d92321992a982a32fbe50260fb59997c059ed5da6325818bcffb
+size 128183
diff --git a/marked/Rel-16/29_series/29002/16a18f2eaad504c8769530bd393a4eb9_img.jpg b/marked/Rel-16/29_series/29002/16a18f2eaad504c8769530bd393a4eb9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c063fc581040317b4f197d95e00f2b65552a495d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/16a18f2eaad504c8769530bd393a4eb9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7066005959f44b41f6174e4bc61c3e5309d96b9f14a9cb3c568faa25425499e7
+size 25796
diff --git a/marked/Rel-16/29_series/29002/193552cf6503ba3edd53a717d66779f4_img.jpg b/marked/Rel-16/29_series/29002/193552cf6503ba3edd53a717d66779f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8caa334732cd6d8ee8af62d02c279344256960a0
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/193552cf6503ba3edd53a717d66779f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db4b719baadecbbf31508a44ec1808993d8521172555f71eff27f3f4ea7f019f
+size 13348
diff --git a/marked/Rel-16/29_series/29002/195bfcf817b1bea7a7c4ad3ba8c02ccc_img.jpg b/marked/Rel-16/29_series/29002/195bfcf817b1bea7a7c4ad3ba8c02ccc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..97b3508350f80021142e2bb3a7d1ad442b5918b9
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/195bfcf817b1bea7a7c4ad3ba8c02ccc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9800bc41436a1c597d2307d602ebf82343159452035186807c35d427541407c
+size 125126
diff --git a/marked/Rel-16/29_series/29002/199607ec43a5b7ad43b1896e152e742b_img.jpg b/marked/Rel-16/29_series/29002/199607ec43a5b7ad43b1896e152e742b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df9513fc81ded1ff1ffbbe0d81177729e90f2e12
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/199607ec43a5b7ad43b1896e152e742b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:482a4a1931932c88edaee5fe0c3a9766407c1429043717176a1392ab2a2db3df
+size 104860
diff --git a/marked/Rel-16/29_series/29002/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg b/marked/Rel-16/29_series/29002/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..084a2837fe0cc444dca813eae81939a0316d34ba
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/1a1c6e97fdffe8ffed7b997b7e682d3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e3e98fc39f200d985d80f4c519dc8d4fe054108f7452a6bdcca6efd78648378
+size 60341
diff --git a/marked/Rel-16/29_series/29002/1dd97d21e745e17aa9bf424cac55737d_img.jpg b/marked/Rel-16/29_series/29002/1dd97d21e745e17aa9bf424cac55737d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1359cad997a2b03138e495fa2dcfbe5cbdfa09e
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/1dd97d21e745e17aa9bf424cac55737d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1aea00191d20793fddbd353080fee53ccb1b9f9a0a9718cea2e887528cf6c7a0
+size 128012
diff --git a/marked/Rel-16/29_series/29002/1ee51f33f2ba2e715d4ee844b1dab99a_img.jpg b/marked/Rel-16/29_series/29002/1ee51f33f2ba2e715d4ee844b1dab99a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..551ee8c17bbd421d4531eb1797261325173060c1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/1ee51f33f2ba2e715d4ee844b1dab99a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e06c23ea5e58b538504731ebfef057b9506ea9ed23331e2d61e5dfdf04d0c901
+size 23363
diff --git a/marked/Rel-16/29_series/29002/1fa646088a731bde9ff4c9af87f93d3c_img.jpg b/marked/Rel-16/29_series/29002/1fa646088a731bde9ff4c9af87f93d3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0dd6de521d728d88b9f37004230106b1e80cf0a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/1fa646088a731bde9ff4c9af87f93d3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2cd5cc6da180d96b5dabfaae7c673747270cdc7b9342a8d63ab5c390088215fa
+size 32355
diff --git a/marked/Rel-16/29_series/29002/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg b/marked/Rel-16/29_series/29002/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..174c50c62d1fca6307f400642640592e2a45e264
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/24ca424ca19ebeeafb6a9249dcd7bcfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff4261fec2ebb994f0e2480100a2edb02eaf64cf37fefbadcc62ae6938e707b9
+size 107580
diff --git a/marked/Rel-16/29_series/29002/2505a4217cba07d8e4b87d77438fc196_img.jpg b/marked/Rel-16/29_series/29002/2505a4217cba07d8e4b87d77438fc196_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9790bdd3dbe644a03e41aba4c2790760c3eda64
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2505a4217cba07d8e4b87d77438fc196_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eca40a54a3569a871a09bebd1e03a88abe8d46468f67f47758dbb2ec1557497d
+size 99467
diff --git a/marked/Rel-16/29_series/29002/2965c9e826cfc7efc1936b2e25f48e63_img.jpg b/marked/Rel-16/29_series/29002/2965c9e826cfc7efc1936b2e25f48e63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9f48028e4d2bb94827d4a76ef25783f19f80a3b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2965c9e826cfc7efc1936b2e25f48e63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e51475d816e92c7804fc9d98a33efe9d8b5b03207794b05b2914f9c055224b06
+size 159036
diff --git a/marked/Rel-16/29_series/29002/29aa6165ccf449dee0b4335676fa7b1a_img.jpg b/marked/Rel-16/29_series/29002/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..639da4e5d829a67c8c0925d131c7b70adcb1ac17
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/29aa6165ccf449dee0b4335676fa7b1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a742ea93d8ec76c74582ea1da03d55b4026cdcc006517c905fd0f0b356d6979
+size 119858
diff --git a/marked/Rel-16/29_series/29002/29ec21437e0dff9d3f11718bca722b88_img.jpg b/marked/Rel-16/29_series/29002/29ec21437e0dff9d3f11718bca722b88_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..937df0969ce516d36bcbb2cee563dc68c395a827
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/29ec21437e0dff9d3f11718bca722b88_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d614844f14b916e784ac72fa1a62dba552d8b3fd99419484eb73e0230b655ea5
+size 121789
diff --git a/marked/Rel-16/29_series/29002/2b04e13962c123370e90b83ab666b87f_img.jpg b/marked/Rel-16/29_series/29002/2b04e13962c123370e90b83ab666b87f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f4cb28741fa9edf6e4bc934f1b0b4670379b0bf
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2b04e13962c123370e90b83ab666b87f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f7ac08814d726c6c194b725db261fd39568dfc41128fc974e5152f9010558a6
+size 112297
diff --git a/marked/Rel-16/29_series/29002/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg b/marked/Rel-16/29_series/29002/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62eb1613b58badb73cba7bd58632a39d28adca34
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2ce4c14cc166ab2d1635adf7c1a2dda9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:035d79487a7ccaa22e4d7ea27f7359d279f70e33ee0499ff5494854669c73ca1
+size 13192
diff --git a/marked/Rel-16/29_series/29002/2d93ffdbf312453a8ac346eee7e4d180_img.jpg b/marked/Rel-16/29_series/29002/2d93ffdbf312453a8ac346eee7e4d180_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c12186efd3341264fd976c8254abd18886a4b8f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2d93ffdbf312453a8ac346eee7e4d180_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3521ba07943472653315d4161b5f149164dde8b1f05d37931dd5c020a06ccc8
+size 99869
diff --git a/marked/Rel-16/29_series/29002/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg b/marked/Rel-16/29_series/29002/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21cffcbc285694c18da1ad142c951932594a4993
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c401dd48c63dc82910bdeb0ee44cd5e49714a439cf60e0c70bf21141b35d6121
+size 75851
diff --git a/marked/Rel-16/29_series/29002/3100b9f8708f586e472f3d9e44f10e52_img.jpg b/marked/Rel-16/29_series/29002/3100b9f8708f586e472f3d9e44f10e52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46bd957482d5f1d88651b494763cc5e0be61910b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3100b9f8708f586e472f3d9e44f10e52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d91bf5bc89822ab37ade1767f9b0101540ae142dfa7d6ac4e3138e8a2ebec83
+size 127700
diff --git a/marked/Rel-16/29_series/29002/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg b/marked/Rel-16/29_series/29002/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1fc45348495a41618cd08596e9514e149795430
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/33cbd34b2ff74e39d12fae4db73f5b41_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49a86b1f51f96d5aab771dca99920947f2e97726bbf740f1fb2eaf3cf957f6ac
+size 133831
diff --git a/marked/Rel-16/29_series/29002/3b0fe07fd5839a26dc188478a1898980_img.jpg b/marked/Rel-16/29_series/29002/3b0fe07fd5839a26dc188478a1898980_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c2c93be2f6a9949a4ae729bc67d2b61a7b0060ef
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3b0fe07fd5839a26dc188478a1898980_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:124342051f0be532a0b942c8a1d6bf126498bfe5bc29fc487b6eb6497f83f29f
+size 36393
diff --git a/marked/Rel-16/29_series/29002/3d3c6241ebe0653d7cf2f2e4524e5f84_img.jpg b/marked/Rel-16/29_series/29002/3d3c6241ebe0653d7cf2f2e4524e5f84_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c0d061a9fee89602500e932233592d886cdfd9c
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3d3c6241ebe0653d7cf2f2e4524e5f84_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ead3a6011e386e65859ff8e57df47a892b54b84fa5979d2f5c0964b04d92e58
+size 112330
diff --git a/marked/Rel-16/29_series/29002/3d46409f8d0190e611a910ff27f8ec07_img.jpg b/marked/Rel-16/29_series/29002/3d46409f8d0190e611a910ff27f8ec07_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d0c4a1272bea1321213d3311c095dc5ed06e761
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3d46409f8d0190e611a910ff27f8ec07_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a196c6667a125932cf2de73e2980e762f0b8ad34f5ef5c06c2085f7cc505c250
+size 81681
diff --git a/marked/Rel-16/29_series/29002/3ee8220e66bef13817d8e8eac304f984_img.jpg b/marked/Rel-16/29_series/29002/3ee8220e66bef13817d8e8eac304f984_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5ffbb7cec1d85dc052d6df71988370193c06e4b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3ee8220e66bef13817d8e8eac304f984_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13a0d326cf773b7a68378a28e1300652ec8dcff5f2a571932f40b3db72e0488d
+size 15542
diff --git a/marked/Rel-16/29_series/29002/3f7ba755d862e1fda11adee98518ec2a_img.jpg b/marked/Rel-16/29_series/29002/3f7ba755d862e1fda11adee98518ec2a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..923be7d9e39c6e0f7121df32844eaf06deb44961
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/3f7ba755d862e1fda11adee98518ec2a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ec15f682c19bd33bdcdb525582794a75872bf82c789e887b58fc572e12b0a22
+size 108488
diff --git a/marked/Rel-16/29_series/29002/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg b/marked/Rel-16/29_series/29002/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05783bdcf31e5b464317fd17aa9701eb4263c5b1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/40b685b3ae31d84f5f9edf37cbb945bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:addc3eccbcbb66956b3ad52628cfd0407796b961d731047856e096d5d0bc8c9d
+size 130154
diff --git a/marked/Rel-16/29_series/29002/4391cd8ac8f58d1b46439ea0cb130782_img.jpg b/marked/Rel-16/29_series/29002/4391cd8ac8f58d1b46439ea0cb130782_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e779cf0e073d999720f65b33560626a02c8c7b03
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4391cd8ac8f58d1b46439ea0cb130782_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e994d4c7add173f2812f4e4aa2383e21a6c6210e98e38b675b9a1cf7331e27ad
+size 80291
diff --git a/marked/Rel-16/29_series/29002/43f7b6b61db9a2f3e3920740a9527d97_img.jpg b/marked/Rel-16/29_series/29002/43f7b6b61db9a2f3e3920740a9527d97_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12afcafa45dc0810c077638199bccf6d58482aa5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/43f7b6b61db9a2f3e3920740a9527d97_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9aa2233573accb4bf59354c3b84e97769efd95ab776a5fc464732bcaca0f1ae2
+size 124851
diff --git a/marked/Rel-16/29_series/29002/444aae06b7856be544a8e1bbae1302c3_img.jpg b/marked/Rel-16/29_series/29002/444aae06b7856be544a8e1bbae1302c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..722d95fba71b6be46c625e67644123462297bd74
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/444aae06b7856be544a8e1bbae1302c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a2639fae03cfbe1d60e16cc0f2ef3cdd7924c32eb648856d082a044688a1970
+size 90294
diff --git a/marked/Rel-16/29_series/29002/4628881725ec2d73799a0521cb4036c5_img.jpg b/marked/Rel-16/29_series/29002/4628881725ec2d73799a0521cb4036c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12abd8e32e173cd0dabe27d84c95ac3e9305151f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4628881725ec2d73799a0521cb4036c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80318483e0a7fbaa14b792f1c22167accc2b59bd3bc70660dbd582875ce93df1
+size 23306
diff --git a/marked/Rel-16/29_series/29002/4778d9d7c0721f39c453edbe614ccf7d_img.jpg b/marked/Rel-16/29_series/29002/4778d9d7c0721f39c453edbe614ccf7d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e918539c07b504d2e9e51a8ae413dd306a71b77b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4778d9d7c0721f39c453edbe614ccf7d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3edfd9f8855e57859cb3d8f6512175fa75a0eac5173badaeeee4e916023aa93
+size 12372
diff --git a/marked/Rel-16/29_series/29002/49d7bfbc65a92a7e1bd61777326a212d_img.jpg b/marked/Rel-16/29_series/29002/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e077532a5a622ec45b79aa0c6ed27f3f6d4546d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/49d7bfbc65a92a7e1bd61777326a212d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b329f68fa9aefe71b161196891d96f22a6049be387de7ff981542ff86a6c8e5f
+size 85133
diff --git a/marked/Rel-16/29_series/29002/4ca691e62964f6ddaf28f3c43d7c14b8_img.jpg b/marked/Rel-16/29_series/29002/4ca691e62964f6ddaf28f3c43d7c14b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de629c995cf30dc665a7e7ce8fb51de5b383ab7a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4ca691e62964f6ddaf28f3c43d7c14b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:822fe7aef7dbdbc647fda05a67ff9e037c6d43f71162b0d675bee5fa2dbc771b
+size 96824
diff --git a/marked/Rel-16/29_series/29002/4ecc29a3c000f2a2409ade321df55f28_img.jpg b/marked/Rel-16/29_series/29002/4ecc29a3c000f2a2409ade321df55f28_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82dde3bc8a8bc463dd8eb8050819540fd64e38b6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4ecc29a3c000f2a2409ade321df55f28_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d854f4f7388b88c2f6e1a28b9742994f87e588cbc5182f1e3fd4d58d04315e2
+size 54278
diff --git a/marked/Rel-16/29_series/29002/4ef412e08808c40e0beb7808d36b9379_img.jpg b/marked/Rel-16/29_series/29002/4ef412e08808c40e0beb7808d36b9379_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fa52b281fde10f4497b2b81d54bb506b951c319
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4ef412e08808c40e0beb7808d36b9379_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52a4f54e20b08d45878f630d4d507415a28f53fb1d8513cba6d50c7e9584165b
+size 95321
diff --git a/marked/Rel-16/29_series/29002/4f33a6e9083ffb400e3c2e074c21434e_img.jpg b/marked/Rel-16/29_series/29002/4f33a6e9083ffb400e3c2e074c21434e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34b5e250bb533d41c679f8191a7536a1c53e6e15
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/4f33a6e9083ffb400e3c2e074c21434e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2b564c50d0a933496e981d22095589248a909bb30b067afa4b087ab7d86985c
+size 122423
diff --git a/marked/Rel-16/29_series/29002/51501a01b2c29ac95e126882508f8831_img.jpg b/marked/Rel-16/29_series/29002/51501a01b2c29ac95e126882508f8831_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b2d30cc6f26a4993cacf67bb48b89fc4e239e669
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/51501a01b2c29ac95e126882508f8831_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ac03b1ebd38ac9db8fa3af2d667e3d2c536504a0b9687972acf72c10b8efa3b2
+size 8216
diff --git a/marked/Rel-16/29_series/29002/52363723032e1459b30b98b074ec86eb_img.jpg b/marked/Rel-16/29_series/29002/52363723032e1459b30b98b074ec86eb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e23cf282074ae2884f302076610b44e6b19b166
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/52363723032e1459b30b98b074ec86eb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:949e54e21ddc9bdd7faf63ea96fc383a8e5aced55feef87971b0fbc5926ea759
+size 40325
diff --git a/marked/Rel-16/29_series/29002/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg b/marked/Rel-16/29_series/29002/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad68015d1fde3a5dd408f228075992a2463b3bb1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/524ed6dbe4bf1dd88e75c40fa79f3d4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:268c74c1f0aa7b56b9ac9b34c956f20b474672317f4f30ac7fcbc18498e50ad3
+size 139033
diff --git a/marked/Rel-16/29_series/29002/53668fc0567b0e9fce35a73e32dcee59_img.jpg b/marked/Rel-16/29_series/29002/53668fc0567b0e9fce35a73e32dcee59_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b3f42d610aa5a2a9392ffd3c61a72936b6e28c1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/53668fc0567b0e9fce35a73e32dcee59_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dfc409ce7113e03898c4f15652dfacbd817d0dc24b1bc1056f3915cef2266ec
+size 120016
diff --git a/marked/Rel-16/29_series/29002/54159e6d8f5ecc73ad262758e3a60677_img.jpg b/marked/Rel-16/29_series/29002/54159e6d8f5ecc73ad262758e3a60677_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d57d9d417ee72273f1f5d132e862dad261b878cf
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/54159e6d8f5ecc73ad262758e3a60677_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd5659b76578888b732792bbe8ca18f7d27db56cb3989647b86b43ecb01db54e
+size 7785
diff --git a/marked/Rel-16/29_series/29002/5457388d54cda61fa1779bf87adf4266_img.jpg b/marked/Rel-16/29_series/29002/5457388d54cda61fa1779bf87adf4266_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f20c97a2409e7bcee11738a5d4fb5bbce3c277eb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5457388d54cda61fa1779bf87adf4266_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e38121d9349eab5c59087a53116a739aeff1384a3e80e709e781db0ea6f4b6c4
+size 124979
diff --git a/marked/Rel-16/29_series/29002/547d3ca5aa7eacefb6ef7c761ca2c7e1_img.jpg b/marked/Rel-16/29_series/29002/547d3ca5aa7eacefb6ef7c761ca2c7e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6d7d4ffe4a7e4f1332123dddb22a5da7711b38f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/547d3ca5aa7eacefb6ef7c761ca2c7e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e37f5287715c572c4206a2827866a754910f5a0249ab210852914352e6a5170c
+size 114620
diff --git a/marked/Rel-16/29_series/29002/54ab5749327b822e800fc41bafa685c1_img.jpg b/marked/Rel-16/29_series/29002/54ab5749327b822e800fc41bafa685c1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c06e825166ca935cb491f4e4808edaad91b5449
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/54ab5749327b822e800fc41bafa685c1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b394ff4f048d8df3f00ad45ae5eb5ee9f3181922714ab679f69f575ac52eef3b
+size 113380
diff --git a/marked/Rel-16/29_series/29002/59c80f0ea70df39c80235fd2fbac0cb0_img.jpg b/marked/Rel-16/29_series/29002/59c80f0ea70df39c80235fd2fbac0cb0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6720f68fe6611f2e623a3f40fbc6fc26989333f3
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/59c80f0ea70df39c80235fd2fbac0cb0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65fc3d546b42b2e900851ff4ee859241d830c28fab46245628bb3bedc50ee30e
+size 154712
diff --git a/marked/Rel-16/29_series/29002/59ea0c624afed35197f8f7e25ff7d064_img.jpg b/marked/Rel-16/29_series/29002/59ea0c624afed35197f8f7e25ff7d064_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..121387f54df2e4a82023483e859ce79872e31ea5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/59ea0c624afed35197f8f7e25ff7d064_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6651d77d166868ae87fa49ac2952737ee8b02decb56bd44f12c2f93315c32de6
+size 102054
diff --git a/marked/Rel-16/29_series/29002/5a117b6be68313978ace1d09f0304f32_img.jpg b/marked/Rel-16/29_series/29002/5a117b6be68313978ace1d09f0304f32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..470e285cc5fedbfcf09feb02710340781ec113e7
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5a117b6be68313978ace1d09f0304f32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:823829cc1f6d02a03fc36908c776992434cb5ceb18763b5799bf0538a99533fe
+size 14100
diff --git a/marked/Rel-16/29_series/29002/5adc166130f17d36dceddf6c168495f9_img.jpg b/marked/Rel-16/29_series/29002/5adc166130f17d36dceddf6c168495f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b921d37bccb6f90ea95027c0e05e61a39c1bd394
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5adc166130f17d36dceddf6c168495f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf3078b01fe60af80582edaad498ab0827de2903a79aa6b803f78a2d567f415e
+size 119978
diff --git a/marked/Rel-16/29_series/29002/5c690861d263afceef4f7ab56ab13264_img.jpg b/marked/Rel-16/29_series/29002/5c690861d263afceef4f7ab56ab13264_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a92b6b1668f007264b7f4daa1e19f7b3edd81bad
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5c690861d263afceef4f7ab56ab13264_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab78d1bd97de540167780296e3ab215cf5d4290ac7fe71f82612773fb97c2560
+size 132348
diff --git a/marked/Rel-16/29_series/29002/5f127fc0b2f4aabd5403ebdad4915b09_img.jpg b/marked/Rel-16/29_series/29002/5f127fc0b2f4aabd5403ebdad4915b09_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7f7bcf3526b5f6cb143063780c403a46d8f3a2b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5f127fc0b2f4aabd5403ebdad4915b09_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c12398c3fc6243568cf80673e61f41509118f2e8f9b246c130d13e5df64e88a0
+size 130440
diff --git a/marked/Rel-16/29_series/29002/5f46be30e6ab02f9ce75b6ed98bb0d50_img.jpg b/marked/Rel-16/29_series/29002/5f46be30e6ab02f9ce75b6ed98bb0d50_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d12d4796700b1e2983c5a36aca06b8c86ef697c5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/5f46be30e6ab02f9ce75b6ed98bb0d50_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b6b9756065d99804bac09133f378b8b83da064c4780c563ab1a23b792430cc01
+size 128162
diff --git a/marked/Rel-16/29_series/29002/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg b/marked/Rel-16/29_series/29002/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..782fa6e874fa84aa6b7a92b18ed524565c6cfc79
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6043644d04a0b251ad3e2ba078ae5ce4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a4c538ec9c7502d67711b39cdd027f00b85b75906adcf68905d425f6bd9d805
+size 34480
diff --git a/marked/Rel-16/29_series/29002/6199756f70e60e3be4da10ba26719b8f_img.jpg b/marked/Rel-16/29_series/29002/6199756f70e60e3be4da10ba26719b8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1b3177c0e4f2ab09370c0e1b6b3d9ed46c35902
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6199756f70e60e3be4da10ba26719b8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbd446c93dcf06fc2d563e4173c30f4ba5cc2b6c35421d6a0e06318a081ae1a7
+size 84444
diff --git a/marked/Rel-16/29_series/29002/62b7ceaeaf17d096b9e241bc9231b225_img.jpg b/marked/Rel-16/29_series/29002/62b7ceaeaf17d096b9e241bc9231b225_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23e1a2b26645ed124f32fffc624d3aff74eb5a26
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/62b7ceaeaf17d096b9e241bc9231b225_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6a3092bf2d4e214e013f9e52b9149009db256ce4d2e756362d7f0692c314db9
+size 65003
diff --git a/marked/Rel-16/29_series/29002/65c3a00aa9457af841a9e548ef5a5c30_img.jpg b/marked/Rel-16/29_series/29002/65c3a00aa9457af841a9e548ef5a5c30_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49e8656737352044edb7d1ea83440bdb1eaef8ce
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/65c3a00aa9457af841a9e548ef5a5c30_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0cb25febc38b9f722b37d20520057206cce7514d7d882a46497bbb28d6071bce
+size 88000
diff --git a/marked/Rel-16/29_series/29002/6710e02072f5396076a74557b6b43142_img.jpg b/marked/Rel-16/29_series/29002/6710e02072f5396076a74557b6b43142_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14902de89935180ecd64dd5cb90f0c7c2b1a0af7
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6710e02072f5396076a74557b6b43142_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da5f9527e5fce86286204c36ac8ebf79c071aafd5b39bd1dfb74a9028e471dca
+size 141373
diff --git a/marked/Rel-16/29_series/29002/6ab36474772ce6a61e97fd5d19770270_img.jpg b/marked/Rel-16/29_series/29002/6ab36474772ce6a61e97fd5d19770270_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57002438f4c3b2c5d83b8f99def7f86d4d09972e
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6ab36474772ce6a61e97fd5d19770270_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44c468d1ee6469bbcebd742ed998b5b0038f507ceda8b422758cd06b958d6a49
+size 21431
diff --git a/marked/Rel-16/29_series/29002/6c2f572f3cbbbae048521f83d7add4da_img.jpg b/marked/Rel-16/29_series/29002/6c2f572f3cbbbae048521f83d7add4da_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9db52e5a1e46267e9d1b0c629422ff3e12843c9c
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6c2f572f3cbbbae048521f83d7add4da_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02ff0f3fb04bac47a90ed11e7c7974023daceccc8be262f873eb0ddf2a9d1626
+size 115186
diff --git a/marked/Rel-16/29_series/29002/6ca842602b0473809416a9cf0d4106a4_img.jpg b/marked/Rel-16/29_series/29002/6ca842602b0473809416a9cf0d4106a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74fe00d86b80e4f805fabf08f482acf4d4404e64
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6ca842602b0473809416a9cf0d4106a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ffbf3b94b13b7ba2547fce667b626890f1318e39aa046ef4bfcfa99d94ad5ddb
+size 141219
diff --git a/marked/Rel-16/29_series/29002/6e3ab0d80a7b8a8378464a9fd212275b_img.jpg b/marked/Rel-16/29_series/29002/6e3ab0d80a7b8a8378464a9fd212275b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81fd96a955f1e0f08dbe3e760095e796e464a17e
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/6e3ab0d80a7b8a8378464a9fd212275b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89b09262598c631fe03ad18496e602bd669aa3ce337f58458f7d44204ac97d17
+size 40763
diff --git a/marked/Rel-16/29_series/29002/70daffd6a754a0bf2fe12e4c77b932a4_img.jpg b/marked/Rel-16/29_series/29002/70daffd6a754a0bf2fe12e4c77b932a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5632c845d2627a2db3e09c368d93662a5d0ce03
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/70daffd6a754a0bf2fe12e4c77b932a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:26a458b52498dedcbeea9ab4a4320d6b8577e4f04890d8aa81eac0a58c8f0237
+size 122362
diff --git a/marked/Rel-16/29_series/29002/7188dd653353235466aea783783e26c8_img.jpg b/marked/Rel-16/29_series/29002/7188dd653353235466aea783783e26c8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..555fdbbc09051c02c70d93f71c0b30767c681400
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7188dd653353235466aea783783e26c8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10121ce600593ac9c84fd67e981d5464f6a5729b8543fc37fb7da612ef8fc545
+size 89441
diff --git a/marked/Rel-16/29_series/29002/71d7b20ced0151b68d524e8163f48ecb_img.jpg b/marked/Rel-16/29_series/29002/71d7b20ced0151b68d524e8163f48ecb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29d15145f15dcfcd4f24e64f7a5fe8811eabc3c7
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/71d7b20ced0151b68d524e8163f48ecb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f47b5e21e09afe86bafbc5d3721194497ad7be937bb53f5827743b2806452c6
+size 151722
diff --git a/marked/Rel-16/29_series/29002/71f90c29879d9ee23038e83f2c9fa746_img.jpg b/marked/Rel-16/29_series/29002/71f90c29879d9ee23038e83f2c9fa746_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bff030f16655fecf6bc2510b4d8dd2aadf61329
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/71f90c29879d9ee23038e83f2c9fa746_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bd9bb817c65b19fadd45590e731e052cc2f48000aa05f9d5ee801d65b02d437
+size 126189
diff --git a/marked/Rel-16/29_series/29002/73d3803c185aec360c10043aed1e2b36_img.jpg b/marked/Rel-16/29_series/29002/73d3803c185aec360c10043aed1e2b36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b128170dbc581efa514afae361a0a8f9619c2099
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/73d3803c185aec360c10043aed1e2b36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34379ed4c8f7985302810462487899dd919221acbf5a1ec93431acf0f2b098d4
+size 91413
diff --git a/marked/Rel-16/29_series/29002/7450203d6606590615fbbeaf2f663b36_img.jpg b/marked/Rel-16/29_series/29002/7450203d6606590615fbbeaf2f663b36_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..963e7c43290b1c7df6aa75d0a3c9ae4f7bacb5ac
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7450203d6606590615fbbeaf2f663b36_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:621e686fc56bb91df28e318fbca9a2b6159a64a6b7ccab702c8aff3769a133a9
+size 35316
diff --git a/marked/Rel-16/29_series/29002/74f0036bd52ddc9ce88094831854622e_img.jpg b/marked/Rel-16/29_series/29002/74f0036bd52ddc9ce88094831854622e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..947256a3ed530abc036e9aac546d8310cc1f77bb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/74f0036bd52ddc9ce88094831854622e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1c407ab5149de7615184254080e3f6ba32333cc7afab8ed38ae37643c6f876c
+size 106593
diff --git a/marked/Rel-16/29_series/29002/75f5e8a70ce294160298220122ac295b_img.jpg b/marked/Rel-16/29_series/29002/75f5e8a70ce294160298220122ac295b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d395153dc6a3cdf9b75736d28ff49f3e66aee695
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/75f5e8a70ce294160298220122ac295b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d1e38f1320eef0d4d2df9ba8a2741af9a3f5545ad87854278bb9bbe16fb80ae
+size 110257
diff --git a/marked/Rel-16/29_series/29002/770a7855c28a3cd0511dd73cc85c0f64_img.jpg b/marked/Rel-16/29_series/29002/770a7855c28a3cd0511dd73cc85c0f64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dbab9ff1154cf965a06bfbffac1a5c8efe29079a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/770a7855c28a3cd0511dd73cc85c0f64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5de2193a64fedaf9903271668188facaeecdc28948ed9529c4c9bcadf3cf9ca5
+size 105424
diff --git a/marked/Rel-16/29_series/29002/777d960032b7f10e3585eedb118ccbda_img.jpg b/marked/Rel-16/29_series/29002/777d960032b7f10e3585eedb118ccbda_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9771303b834cf27b0f48ec3da688d3b2acbde0e1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/777d960032b7f10e3585eedb118ccbda_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:363234f3217be41a2d524001b2a570680f55c30583d0f46e552f3d54ce74b4f6
+size 87529
diff --git a/marked/Rel-16/29_series/29002/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg b/marked/Rel-16/29_series/29002/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01af9af591f801423f86e55276a994647a348c0a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/792a3e6edb8dc2fc545f0782d6b4d3f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b21390cf0ed16db42e9b8eb7ac2a11487204f323f89c6af71ae15109df844657
+size 137340
diff --git a/marked/Rel-16/29_series/29002/7987261f8ee9bbbfb3a4bd048a86bf72_img.jpg b/marked/Rel-16/29_series/29002/7987261f8ee9bbbfb3a4bd048a86bf72_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1401a82de5689fd8faf41787861306c9e21af41
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7987261f8ee9bbbfb3a4bd048a86bf72_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:156bc6967219814f621e5e958268e597004db5f9e93218ce84f801a33e11e7b4
+size 84647
diff --git a/marked/Rel-16/29_series/29002/7c1c0ddb3109199835d107a41b20ffae_img.jpg b/marked/Rel-16/29_series/29002/7c1c0ddb3109199835d107a41b20ffae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1ac34493a5b935a5c0b33428b2da8bdc9b98935
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7c1c0ddb3109199835d107a41b20ffae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a70aec222722ec91d68d7be9443a2771cd07d375e71f43e2a942387b44767dd9
+size 120243
diff --git a/marked/Rel-16/29_series/29002/7c3fe67da652458629a549d6be97b7c5_img.jpg b/marked/Rel-16/29_series/29002/7c3fe67da652458629a549d6be97b7c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d367531745be163ef8ef78bf966ce814d93fc80c
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7c3fe67da652458629a549d6be97b7c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4371bcc5bb1f3083176c3d1b5838f9f6a2cca7c0c5a6bfa35411b2c99e601ca
+size 103383
diff --git a/marked/Rel-16/29_series/29002/7dee647ca55bbe4aeb005761e9795761_img.jpg b/marked/Rel-16/29_series/29002/7dee647ca55bbe4aeb005761e9795761_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87bfefcfb7e9ceeb00e667bea06845c84b19fbf6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/7dee647ca55bbe4aeb005761e9795761_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a00753439f509afdb1257680d38b573792f587f6c8cb23c7eade855772fe8e7a
+size 81882
diff --git a/marked/Rel-16/29_series/29002/811c0426b6fdf23228c6620c4f9d047f_img.jpg b/marked/Rel-16/29_series/29002/811c0426b6fdf23228c6620c4f9d047f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4834b57fe81e21bb2e6dfb901a560b4a67d99c38
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/811c0426b6fdf23228c6620c4f9d047f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcbd30e4cdfeef8de858464f3161c865dd4d6b59d719b2002a5360c5834e9191
+size 128484
diff --git a/marked/Rel-16/29_series/29002/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg b/marked/Rel-16/29_series/29002/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5a2f344d2b9422c58eae4a2399d9b310a307e06
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/81e0bc85cbb6bdb4779d4af6d86e80cd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:664eb0fd624f29658f2e68268d1a15e539923b5c1aa764db00b2faffa8832111
+size 120113
diff --git a/marked/Rel-16/29_series/29002/81eebff59300420692082c50d4f0d1fc_img.jpg b/marked/Rel-16/29_series/29002/81eebff59300420692082c50d4f0d1fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d11164eaefae8caf2bbbfa6c96b4e7504107ee8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/81eebff59300420692082c50d4f0d1fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b4dfea1718b0b5dab1c54d68869146d6bad7e25251bdb18c4674f323ebf78db
+size 104561
diff --git a/marked/Rel-16/29_series/29002/831c19022658f416cb09b881629c2574_img.jpg b/marked/Rel-16/29_series/29002/831c19022658f416cb09b881629c2574_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82c90c339a26b5d6fdbf3cec6495e403ef62d6e8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/831c19022658f416cb09b881629c2574_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a914abf7b6cf6ebe6f6ab9d80a8d62e2a2fca13c1afab75f835d791f60dcebba
+size 94853
diff --git a/marked/Rel-16/29_series/29002/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg b/marked/Rel-16/29_series/29002/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1dddd584f137e10556701ce6a07d8306b338f496
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/84d7d5863a5092cbe730c1baeb4fae2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8454c6773e9dc794b2cf8d5b477e716594fac9f9867e7829e8d8bb6c10544306
+size 36121
diff --git a/marked/Rel-16/29_series/29002/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-16/29_series/29002/84e5b251aa38db522f76f5cc3afcb853_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a02e1e752f0e27fcd1ede4978598997d6e90786
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/84e5b251aa38db522f76f5cc3afcb853_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:407a147dd6901f547954219989cc1530b6d15c2b7471506c96b8818490e067c7
+size 18993
diff --git a/marked/Rel-16/29_series/29002/85e117a13c46e2b4c8b69e1179f25f14_img.jpg b/marked/Rel-16/29_series/29002/85e117a13c46e2b4c8b69e1179f25f14_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..984b30ae1fdcdef749ccac581bfde433b137e0a6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/85e117a13c46e2b4c8b69e1179f25f14_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f54890ddece6c789cba792866fd531e16c6a8064938b30cf1984e2c7a77cebe0
+size 85312
diff --git a/marked/Rel-16/29_series/29002/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg b/marked/Rel-16/29_series/29002/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a58a5e6ff8a1f165015d81072abd4140daff1e12
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/886a88caad59e8f8b1cf54c72e8adf4a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a85a87c829d274d83c8bdd0ee488e8e902f9e747d243b71fd222a41814268f8
+size 107783
diff --git a/marked/Rel-16/29_series/29002/88c92858439684b2103e88cb143fb98e_img.jpg b/marked/Rel-16/29_series/29002/88c92858439684b2103e88cb143fb98e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..78b4e99b9a0cfcc6ac7574d11a1330eb1b41a3e6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/88c92858439684b2103e88cb143fb98e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7847ad86d9ded8f5f122b0fd7cfc9fc1219eeaed15ac79220935df1293329b99
+size 133870
diff --git a/marked/Rel-16/29_series/29002/8afb9001f2f71544fbd36082ccc727e4_img.jpg b/marked/Rel-16/29_series/29002/8afb9001f2f71544fbd36082ccc727e4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a232e5a6ca494356920f945d5825194a1c556d8d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/8afb9001f2f71544fbd36082ccc727e4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90b90c7275611c06c3b9f49d741f16359934448419e6879048d7e8a621459082
+size 94351
diff --git a/marked/Rel-16/29_series/29002/8b964751bc72fac53d873c674d3fa937_img.jpg b/marked/Rel-16/29_series/29002/8b964751bc72fac53d873c674d3fa937_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12873827c211a49102c4c4fee43670d02048e0bd
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/8b964751bc72fac53d873c674d3fa937_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b157a92397221f958ee5fc113f73c93e1ba859f2418471c889279c16db8d9b3c
+size 120071
diff --git a/marked/Rel-16/29_series/29002/8fa278297791e5bf818bbf11579151fb_img.jpg b/marked/Rel-16/29_series/29002/8fa278297791e5bf818bbf11579151fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a37196857f50823e9281367c58bfd16a821611f6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/8fa278297791e5bf818bbf11579151fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd2f5b7dd791f9f4b45bbb70ddecd473f120c401a460701e542d95709f3239fe
+size 101544
diff --git a/marked/Rel-16/29_series/29002/933a097f8f087e901730352801e25555_img.jpg b/marked/Rel-16/29_series/29002/933a097f8f087e901730352801e25555_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91717db13952e9e388387b4bbb8e5c516d383302
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/933a097f8f087e901730352801e25555_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb534faccfe802bfab704e748a04543d0cb13ca1dbe807a3e5a793f74b685b26
+size 75692
diff --git a/marked/Rel-16/29_series/29002/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-16/29_series/29002/93bd00a00fa28558486f0664550699b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51df5f724727745bee370d84da62a0d8c65400e5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/93bd00a00fa28558486f0664550699b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:843068fbaa3f12d62aff56a0bc134d8e1d26c2fbf0567cb72d4dfdaddf3a4d6c
+size 16673
diff --git a/marked/Rel-16/29_series/29002/96d77cb2f738859fd462953fad369a1f_img.jpg b/marked/Rel-16/29_series/29002/96d77cb2f738859fd462953fad369a1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c7f58c951b8d9426fdbdd36951ac80f1f30f1d6b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/96d77cb2f738859fd462953fad369a1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a7b0582aa3464c7a78c5d02aed37c5415344f136740e52adf254eeec3f0c1f0
+size 23664
diff --git a/marked/Rel-16/29_series/29002/97390572a8ffb768231d191922d28d74_img.jpg b/marked/Rel-16/29_series/29002/97390572a8ffb768231d191922d28d74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d38ad262efc32ff47399e96b763663aa73465e9f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/97390572a8ffb768231d191922d28d74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7413a102e808ef1de3909549aa77cb0fd329dcccfab4df5c63388e2020fd2c25
+size 138632
diff --git a/marked/Rel-16/29_series/29002/997b07a913097ec381a81470ca4ab97e_img.jpg b/marked/Rel-16/29_series/29002/997b07a913097ec381a81470ca4ab97e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0bb8b59777220627efab3ca118b6e3c4dd3769f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/997b07a913097ec381a81470ca4ab97e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02f6df51bb4a6af83fe82d2b9b3b6edc7cf0fb91b0cf86a8565b7237bb164b0a
+size 90250
diff --git a/marked/Rel-16/29_series/29002/9997ce2599510a8912ccac15865ae602_img.jpg b/marked/Rel-16/29_series/29002/9997ce2599510a8912ccac15865ae602_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3497c2e2fdfb7161139396d8ed0eeaf1491919f2
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9997ce2599510a8912ccac15865ae602_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d265644c0f58614512d3c4ac9c6620e3faa6762752f6847db2a9f1d71c313715
+size 68083
diff --git a/marked/Rel-16/29_series/29002/9bd5073900339d75c2f66243d037e6e0_img.jpg b/marked/Rel-16/29_series/29002/9bd5073900339d75c2f66243d037e6e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5e93e79490056794aad3b7e8c870e7a1e69f3fdd
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9bd5073900339d75c2f66243d037e6e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fce3b5e8f44d540cc123e8c84f61968c83454113797a9707e13cc68a311a3ee
+size 144503
diff --git a/marked/Rel-16/29_series/29002/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg b/marked/Rel-16/29_series/29002/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c88fa101ca765d7dcca73f9c9edd9490c9fc4a27
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:717f24b0bc4f7ac63337df12ca24d0f32aa960af049cef5952c1cac39981ed8f
+size 5418
diff --git a/marked/Rel-16/29_series/29002/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg b/marked/Rel-16/29_series/29002/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c544aedeeea000f2c30b4e98edc3f797fb3deb1
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9e290fa7e4578ba0a8b8c5008c99b564_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd5a106b32664eca36e67043f3f8a88f1c37bd5fe10af74bb91edd34c9cd271f
+size 91141
diff --git a/marked/Rel-16/29_series/29002/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg b/marked/Rel-16/29_series/29002/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17a620af9209e37238ab47721196f37318989966
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9ef8e686bf7d4fdc4504d136e1b350f0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc82a0835682f6ba371832eb52869cd31c456452a07f12e7ce6bfa405fa4fb97
+size 149289
diff --git a/marked/Rel-16/29_series/29002/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg b/marked/Rel-16/29_series/29002/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d00ab8d0e191678b2dc1d80db1dac15917a3b794
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/9f2de980bdf4633bdf738b33d2ed8ff1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:21e2baa12261150268088ed2265f00131409a4789b858e94d3fdcb6d76c57c69
+size 108374
diff --git a/marked/Rel-16/29_series/29002/a168167bf5e95524ddc74df99b4a977f_img.jpg b/marked/Rel-16/29_series/29002/a168167bf5e95524ddc74df99b4a977f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f3f938570adf5df39cf9f467488926f5fe9035e
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a168167bf5e95524ddc74df99b4a977f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4385f8e3962edd1dba9daf056f67b9470a3a69e9a7755f33aa7e3d3be98fef9a
+size 107787
diff --git a/marked/Rel-16/29_series/29002/a2763753bfc5fc69f0694c695973cd40_img.jpg b/marked/Rel-16/29_series/29002/a2763753bfc5fc69f0694c695973cd40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcae6dbf84f936ac277369e7ab4b235c900b6eac
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a2763753bfc5fc69f0694c695973cd40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a564e280854e81de1f8c3550b03e344cdf29666ed9f0c2fadd5eb00537bab01e
+size 73699
diff --git a/marked/Rel-16/29_series/29002/a279fe19aaba00682377b0c7f8f21fa0_img.jpg b/marked/Rel-16/29_series/29002/a279fe19aaba00682377b0c7f8f21fa0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c43c3309104901c9afb4b84c9ce98874dbf520e3
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a279fe19aaba00682377b0c7f8f21fa0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e09e2e5c8e8a6754d4b941bfba87cbfa3c990fccec7b9c0d427a054580b9ab1c
+size 124740
diff --git a/marked/Rel-16/29_series/29002/a3ce3e5191a737483aa2635e69dd15ff_img.jpg b/marked/Rel-16/29_series/29002/a3ce3e5191a737483aa2635e69dd15ff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e37db340261f8c70a03cb94e065aa80df866e426
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a3ce3e5191a737483aa2635e69dd15ff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b07b44c4bc67d7ed53037c6e5225d9b558c6de6320ad07e4362e4c50bbaee15
+size 21845
diff --git a/marked/Rel-16/29_series/29002/a72557efa52586542f028f0a62ff9cf5_img.jpg b/marked/Rel-16/29_series/29002/a72557efa52586542f028f0a62ff9cf5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d61081c05d2f449e75365dad151527473280594
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a72557efa52586542f028f0a62ff9cf5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96c2f791934dad79bac44addf71f7f3c440b44dfb7dc75a3896d5a31cd85ee80
+size 106227
diff --git a/marked/Rel-16/29_series/29002/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg b/marked/Rel-16/29_series/29002/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49203f8944ad0fb20b203e8af4fce457ec99d2d9
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a76fd8608a1490167e6c1a4ed32b38e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a873681fe8180f082becd2f5e4d4ce48be42ae79edb453822c9fc33c5a1b019
+size 126101
diff --git a/marked/Rel-16/29_series/29002/a9fa083478f6c517e7970c46d1b928e9_img.jpg b/marked/Rel-16/29_series/29002/a9fa083478f6c517e7970c46d1b928e9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..632659350d356809fc413910186f80626cb6cc76
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/a9fa083478f6c517e7970c46d1b928e9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbc5901b6ecf7d4b831b1082115f0c13ed9b84e9eff33f3afb8843e8be97ee01
+size 133413
diff --git a/marked/Rel-16/29_series/29002/ab838f5438281aeac2619c5602dca07c_img.jpg b/marked/Rel-16/29_series/29002/ab838f5438281aeac2619c5602dca07c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cad97a403c31f591612b8b19ad9b0803db021448
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ab838f5438281aeac2619c5602dca07c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9fd9ab7d846b082eaa912e80816472a8181818085e8342b9d2b41c8a11411d78
+size 118573
diff --git a/marked/Rel-16/29_series/29002/ac991aadd44a0ddcae4451e75069dbdc_img.jpg b/marked/Rel-16/29_series/29002/ac991aadd44a0ddcae4451e75069dbdc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..077373bb37c8606e5a1c8458e811ac9b710cf0dd
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ac991aadd44a0ddcae4451e75069dbdc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e786acc71a4f2bddb709163418cd852a58112f006577e6cbce0fedfcfe047878
+size 122078
diff --git a/marked/Rel-16/29_series/29002/acdac69e9c807eb930e4e5fef84d1833_img.jpg b/marked/Rel-16/29_series/29002/acdac69e9c807eb930e4e5fef84d1833_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0cbc85bc1a22da3f950c9c0574c59afe045833a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/acdac69e9c807eb930e4e5fef84d1833_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f07b1ec96234fa93dc029733746f4dedb6afa077cc61bfbfdb7547d4be46ba2
+size 109330
diff --git a/marked/Rel-16/29_series/29002/ad73d5ca7408dae269a6a821e33b1869_img.jpg b/marked/Rel-16/29_series/29002/ad73d5ca7408dae269a6a821e33b1869_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..001a14ef481f1df67babb69bd2ece80bf31aa8d7
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ad73d5ca7408dae269a6a821e33b1869_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4603843621065bf4db78300e4b89ef0f28c662d710aab1bf290a6193d099819d
+size 116268
diff --git a/marked/Rel-16/29_series/29002/aed3396820a10fad2d1554d72c525982_img.jpg b/marked/Rel-16/29_series/29002/aed3396820a10fad2d1554d72c525982_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f670433d59ac29ec837f7b590e7f035187c18917
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/aed3396820a10fad2d1554d72c525982_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cecb3051a7418bdc6aaec71e637e17b4a56c11833cdf39ec0747e58a98bd46e9
+size 58566
diff --git a/marked/Rel-16/29_series/29002/b12888c1d6957245d70f09798a69a807_img.jpg b/marked/Rel-16/29_series/29002/b12888c1d6957245d70f09798a69a807_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..819b89cd2aa259d5fe9dc1de475273064e4be2bf
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b12888c1d6957245d70f09798a69a807_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49c0b189ab8264cfe1c79ab5123b7d58d70e428342246bd9db6b9f984143302e
+size 142814
diff --git a/marked/Rel-16/29_series/29002/b24d82be8e3c17b96af762d92ab72ffe_img.jpg b/marked/Rel-16/29_series/29002/b24d82be8e3c17b96af762d92ab72ffe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..109be88088420a8f21af6536750ee2d2b787af9d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b24d82be8e3c17b96af762d92ab72ffe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:11d1641e100267d1cb018c2f7f4b6dc2ffa4e59afa58def8dfcbde35e7d7e99c
+size 97040
diff --git a/marked/Rel-16/29_series/29002/b2cc48c15fd9cf146aa4bd0fd007b946_img.jpg b/marked/Rel-16/29_series/29002/b2cc48c15fd9cf146aa4bd0fd007b946_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e5936ca157b1645787f579d71c24d84285ab5de0
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b2cc48c15fd9cf146aa4bd0fd007b946_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e327717a6d0eedc0ea68c26f3179061af7d9f1d7e9aca392080944ec488a414e
+size 93200
diff --git a/marked/Rel-16/29_series/29002/b3825574940d90a7356ca976ef522110_img.jpg b/marked/Rel-16/29_series/29002/b3825574940d90a7356ca976ef522110_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0c2d5ddf0b297ba1bd08e0d7e58d565f4d1c1573
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b3825574940d90a7356ca976ef522110_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6298bd48a93dbed73e508f61652741868e0bd1bbaecc5f04916a3d458867c1b6
+size 110479
diff --git a/marked/Rel-16/29_series/29002/b396319adaa959d447ae3eb7b6017dae_img.jpg b/marked/Rel-16/29_series/29002/b396319adaa959d447ae3eb7b6017dae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bbb363ccd1e0986529e34a88ad4817e21951b199
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b396319adaa959d447ae3eb7b6017dae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ede88397566afd6f3bb8507c249c639ab590f36980102f0c479ef9498744ad4a
+size 27534
diff --git a/marked/Rel-16/29_series/29002/b57a7a090805d3dfef36a0130a473432_img.jpg b/marked/Rel-16/29_series/29002/b57a7a090805d3dfef36a0130a473432_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95b6daadec81e048d75c616a34afddcd9f98d3d9
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b57a7a090805d3dfef36a0130a473432_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a2c1618ab1bfa3dcc0e5e78622fb7e12dfcf954cc38e9386adab1fdbc04ccd96
+size 96784
diff --git a/marked/Rel-16/29_series/29002/b5ce6d659e1431289c2e79b01bf38a15_img.jpg b/marked/Rel-16/29_series/29002/b5ce6d659e1431289c2e79b01bf38a15_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04de2d7dff8927f19f5868fdc08caad6bdeef4cb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b5ce6d659e1431289c2e79b01bf38a15_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7205492a39ae889eb6afd86a19efc0d6f5a1783ad3bf50d56eb24e335437a1e
+size 86000
diff --git a/marked/Rel-16/29_series/29002/b912fdb51e54b026873e19ecfb1ea1fa_img.jpg b/marked/Rel-16/29_series/29002/b912fdb51e54b026873e19ecfb1ea1fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..596b100df787e41d027715cb204243d435753354
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/b912fdb51e54b026873e19ecfb1ea1fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:35eaa7d52349a0db658d6a1442f4df9250d9a91bb0c012f2580f2177c74f813c
+size 14102
diff --git a/marked/Rel-16/29_series/29002/ba727916d67bd9a343429b763a6e8f12_img.jpg b/marked/Rel-16/29_series/29002/ba727916d67bd9a343429b763a6e8f12_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9a706055bce0c716fbf69f274399e2205827abb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ba727916d67bd9a343429b763a6e8f12_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cf58ff532d6e9acb96bd38a1ba64c90ef4d85df2278b49250a32108356ca4a4
+size 130637
diff --git a/marked/Rel-16/29_series/29002/bb8035cd106b4d77b3615e90645f8e37_img.jpg b/marked/Rel-16/29_series/29002/bb8035cd106b4d77b3615e90645f8e37_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ee1597adc51328cac0d6d44960293a83a633d3b8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/bb8035cd106b4d77b3615e90645f8e37_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fa969b091ce9e4a7c18a8290b161c99fde78ff53ffa52b03af51237310078c8
+size 137821
diff --git a/marked/Rel-16/29_series/29002/bbdb91b475e5915fd7e690eea9e6220b_img.jpg b/marked/Rel-16/29_series/29002/bbdb91b475e5915fd7e690eea9e6220b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf12e1b7b346bdd95f4f27c2ec69f035ec9a1108
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/bbdb91b475e5915fd7e690eea9e6220b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef58589856b8be16b4577553f487a1b16a62602cc5326ff571698ceadcda38ae
+size 141651
diff --git a/marked/Rel-16/29_series/29002/bbfc430d910c0bd4382db83adb64e2e0_img.jpg b/marked/Rel-16/29_series/29002/bbfc430d910c0bd4382db83adb64e2e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2d62c73793095d78ad329061781c1aaa500c2fb0
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/bbfc430d910c0bd4382db83adb64e2e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cff021eb97b4e2adab7444ee43faee7c6863743c1157c09ab1f044ed4ac77e7a
+size 103534
diff --git a/marked/Rel-16/29_series/29002/bebff9f8a50fa7778fe927cd332ec6aa_img.jpg b/marked/Rel-16/29_series/29002/bebff9f8a50fa7778fe927cd332ec6aa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..863e1f08babc11af668b8382d6dc31e6b4e74d00
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/bebff9f8a50fa7778fe927cd332ec6aa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01fc6e6a642be26fe0b024d9fbb41cf2e9353a7e276b78c49ceb7c5150024c1d
+size 106913
diff --git a/marked/Rel-16/29_series/29002/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg b/marked/Rel-16/29_series/29002/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e971faa04c8fce16696a8af0c6eb68e8867b3af8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/bf9abec3605f1a8d00ae6524a9af02ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8e97d655902f85adc3e08f0172a0527d9e7616dbc4d9e29078d660d94ca992e
+size 61210
diff --git a/marked/Rel-16/29_series/29002/c07637986c84860270f00b7af39e1956_img.jpg b/marked/Rel-16/29_series/29002/c07637986c84860270f00b7af39e1956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1711bbbdb09335b032dc5c829d271cc31cba5bf2
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c07637986c84860270f00b7af39e1956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d26589e01adcab1bbde4bd129e354a436f3d87c41a41d5f2f026e8ebb22f8b7
+size 108040
diff --git a/marked/Rel-16/29_series/29002/c07bedd918cbe46227a83594c2745b25_img.jpg b/marked/Rel-16/29_series/29002/c07bedd918cbe46227a83594c2745b25_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2dc1d2fa90745dcfc4e640d8728f534bbefe0d94
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c07bedd918cbe46227a83594c2745b25_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:351235796ffb80fd9aa86c02892ea8ef64af1c60ce67e044bd40ccb587e6eeed
+size 111862
diff --git a/marked/Rel-16/29_series/29002/c2977ae6a26e279377b14561930225c6_img.jpg b/marked/Rel-16/29_series/29002/c2977ae6a26e279377b14561930225c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3253e36963c7582c93d2785b7809a4752b48f6f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c2977ae6a26e279377b14561930225c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5264be0a200ed0a617936083aff8b18f4e3d94fd2fb7d96a9c551c2f37244e5a
+size 116529
diff --git a/marked/Rel-16/29_series/29002/c2cc51cbfd1851b44a294c5345de6b04_img.jpg b/marked/Rel-16/29_series/29002/c2cc51cbfd1851b44a294c5345de6b04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d6a249269f86d1bf342d104a5efdcbf7391ae52
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c2cc51cbfd1851b44a294c5345de6b04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8cf52a1bd840121bccbfcc8f1aea6855e8c66af261bd8525929d51737731ead7
+size 112814
diff --git a/marked/Rel-16/29_series/29002/c32a0686e908be9af1f8b695612e69bf_img.jpg b/marked/Rel-16/29_series/29002/c32a0686e908be9af1f8b695612e69bf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b72632b79b584e51fbaf8fae85a3d9021f8e8114
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c32a0686e908be9af1f8b695612e69bf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2ad992155987868f89bfd582c801b42d122ebc5c86ff77564a7380682a9bff1
+size 120753
diff --git a/marked/Rel-16/29_series/29002/c700124873e73d0731c82ef7e12b71f4_img.jpg b/marked/Rel-16/29_series/29002/c700124873e73d0731c82ef7e12b71f4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f602e41a052c7ee8dff96cef71caefe759709a43
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c700124873e73d0731c82ef7e12b71f4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d64d99e1494f2e2c822c69198e33334ea09e8b2c4b01191c61ec6fe58dea50d
+size 140671
diff --git a/marked/Rel-16/29_series/29002/c71cc20c24544f057770d4066ecaadc4_img.jpg b/marked/Rel-16/29_series/29002/c71cc20c24544f057770d4066ecaadc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea99245e2590d34299b4d768fa9b8d30f542762d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c71cc20c24544f057770d4066ecaadc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d90bbf371a0bd202116cf0f5e3712bfd835c63ef85e88cc85b144a1a453f219d
+size 90701
diff --git a/marked/Rel-16/29_series/29002/c75655fff16f4b6895777220a57d21e5_img.jpg b/marked/Rel-16/29_series/29002/c75655fff16f4b6895777220a57d21e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f4ac59eaa0812c88c5b1fc38cfc2e1775ee51ef
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c75655fff16f4b6895777220a57d21e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ef415d5718aad99580124be730a219b42b79a9ce54fbf392e7a5b7d97a13f3f
+size 109613
diff --git a/marked/Rel-16/29_series/29002/c79d10d97e1f525e9c85e96e91616923_img.jpg b/marked/Rel-16/29_series/29002/c79d10d97e1f525e9c85e96e91616923_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..544c4ac060e759a1c08f2f500253757ba106faa9
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c79d10d97e1f525e9c85e96e91616923_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2edb1ea5223d87513dd5c43c359c21e44bacc7e3bdaef861deb916fcd0a022f
+size 90116
diff --git a/marked/Rel-16/29_series/29002/c941bae4c5b877af807a9dc7ef13c666_img.jpg b/marked/Rel-16/29_series/29002/c941bae4c5b877af807a9dc7ef13c666_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1aae45e89f4bc7e4c9f670a37b4c2b0df3be5fe8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/c941bae4c5b877af807a9dc7ef13c666_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48cc122ff2dade4b1f7b3f0ccd63d3d6dca253922a75a6c547c17e2c97d5a29d
+size 94901
diff --git a/marked/Rel-16/29_series/29002/cbc0c1be46de4edbd03d0c54889f4846_img.jpg b/marked/Rel-16/29_series/29002/cbc0c1be46de4edbd03d0c54889f4846_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1b3b288c07754933cf9197bbc3dd2cc20a99cef
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/cbc0c1be46de4edbd03d0c54889f4846_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f88c0400fea589c5ed1495a34335cfc47db6d00457c9537f636f3435e4ac7439
+size 124244
diff --git a/marked/Rel-16/29_series/29002/cbf400f805c12c870d53a2cce2a45ae4_img.jpg b/marked/Rel-16/29_series/29002/cbf400f805c12c870d53a2cce2a45ae4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..99fb78f437e044ed3fa1c39080e92290d7fcbff8
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/cbf400f805c12c870d53a2cce2a45ae4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8bfa4c6f0b4d81cade232e05020ee8953b1d524e98c6a2aad24c93e087a6035
+size 121957
diff --git a/marked/Rel-16/29_series/29002/ce8d8abf4743a32e2b6549946e73e5cb_img.jpg b/marked/Rel-16/29_series/29002/ce8d8abf4743a32e2b6549946e73e5cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2222bf91c046885c0524226a496072ca20ec4939
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ce8d8abf4743a32e2b6549946e73e5cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc5838305de7573ba4919cc0b6544a057030c84fa93563c8dd90fb6d7c88e9f8
+size 122927
diff --git a/marked/Rel-16/29_series/29002/cf6b2e5b134aeadae43f0ba8d04dea2f_img.jpg b/marked/Rel-16/29_series/29002/cf6b2e5b134aeadae43f0ba8d04dea2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3cd2934c04759fb8e723886f20b015412f3e412
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/cf6b2e5b134aeadae43f0ba8d04dea2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74a5d6f4d8e282b349ac2fa644d9e791caeb2678cad80909e6589621145db450
+size 145101
diff --git a/marked/Rel-16/29_series/29002/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg b/marked/Rel-16/29_series/29002/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bed871162de5f1610af1dcb997f7ee3719390fab
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/cf8d9315f7f99ef87b4040c7312c5c6f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f04ad59917985d8a09215b90523238d871c509065386a974b014cafe081ca4b5
+size 138869
diff --git a/marked/Rel-16/29_series/29002/d019f7011b290eab4ed0293f4972df51_img.jpg b/marked/Rel-16/29_series/29002/d019f7011b290eab4ed0293f4972df51_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf91b083fd14d12f1a14cafd421c5e25be8b815f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d019f7011b290eab4ed0293f4972df51_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:699f09790e50e6d3772ebbca6294fdc1b0d4956d2ba8c87f5707f7cc285b4855
+size 113382
diff --git a/marked/Rel-16/29_series/29002/d081abfd06a4b868f797e5669c6dff78_img.jpg b/marked/Rel-16/29_series/29002/d081abfd06a4b868f797e5669c6dff78_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54fdc626187204348073071f8b092ba0c16b611f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d081abfd06a4b868f797e5669c6dff78_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:144e72e32022e73ad3c06baf8668fa5f840120fd6cbf0fd8f2611a2ed7fbeb3b
+size 111839
diff --git a/marked/Rel-16/29_series/29002/d11039755489421fdcdad3ed6edd05d8_img.jpg b/marked/Rel-16/29_series/29002/d11039755489421fdcdad3ed6edd05d8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..756a874358ffed8968b1f001cc17304d580e0969
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d11039755489421fdcdad3ed6edd05d8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8ba384177b0572409e673d1e842ea0e18068b395e4f0577a12064533858b85a
+size 123170
diff --git a/marked/Rel-16/29_series/29002/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg b/marked/Rel-16/29_series/29002/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0c0bc6e03adc856521c9f7eaa8733ce560e4f46
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d1aa8db844a6bb8519d74e48d1cf5343_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12b8fc48c36af15b140cfb51d44c9dfa4a100a4a52201fefa18cbe68a86623a5
+size 38409
diff --git a/marked/Rel-16/29_series/29002/d1b395074f5e8d79044e1666eceb8841_img.jpg b/marked/Rel-16/29_series/29002/d1b395074f5e8d79044e1666eceb8841_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..233ca9fbcc8e80a8c7c381e4e00b78eebde8dd3a
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d1b395074f5e8d79044e1666eceb8841_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f17b1e7fb2d25d8b69af3dcda45da1eb6fa7f18bc6cea81c9582ebb75190f2f
+size 11213
diff --git a/marked/Rel-16/29_series/29002/d3581354fc6f1b5e27d3c990e41cc805_img.jpg b/marked/Rel-16/29_series/29002/d3581354fc6f1b5e27d3c990e41cc805_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32fd7aaa2325246ae1627575a44e5acccdef07cb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d3581354fc6f1b5e27d3c990e41cc805_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02375c68e09ea1c23e05a96dd472fa6f761d376dbd7cf409d014ad43988f23f3
+size 100241
diff --git a/marked/Rel-16/29_series/29002/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg b/marked/Rel-16/29_series/29002/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..45b90e3340c79c36dfd280c275126dcfc93ed0c5
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d6b0963170ed3d0ed9c5bfaccec452e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4008fece67ecb6a3ada86cf58829f00687203eb8460b0b3c049f593c24a01e3
+size 137280
diff --git a/marked/Rel-16/29_series/29002/d841e9dc5c67c17299341829b95da4ad_img.jpg b/marked/Rel-16/29_series/29002/d841e9dc5c67c17299341829b95da4ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7da6ae6884c247aad0ffec157112a80ede9621eb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/d841e9dc5c67c17299341829b95da4ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e61781d3a431fb794dea52f11ac5df3845ecc74a153e646108363c9394d8ad3
+size 100176
diff --git a/marked/Rel-16/29_series/29002/df079c3046a59bebedea2cc7a9ce5f98_img.jpg b/marked/Rel-16/29_series/29002/df079c3046a59bebedea2cc7a9ce5f98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d0b3c980dd93f3f0b97800952d72b14b84285f3
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/df079c3046a59bebedea2cc7a9ce5f98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c75687aa5cae995e06eb8e54b12e59e815fa02df023178dc82dc3735f5671f7a
+size 61991
diff --git a/marked/Rel-16/29_series/29002/e3042743e7b2aebe2621e3d3691e323c_img.jpg b/marked/Rel-16/29_series/29002/e3042743e7b2aebe2621e3d3691e323c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26f4024e1319cd6cab535aeacaab8569af08ca53
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e3042743e7b2aebe2621e3d3691e323c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b804532f9297f7e63b2a475586c3b5825918aef53b274ef5ef3c6a04ff5b3762
+size 64048
diff --git a/marked/Rel-16/29_series/29002/e3a3eef92d316db2c9bd020f739c5809_img.jpg b/marked/Rel-16/29_series/29002/e3a3eef92d316db2c9bd020f739c5809_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88cb8302a130a05c07ef6cd2af0df67c8506f3ee
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e3a3eef92d316db2c9bd020f739c5809_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b4c6106a19784a0f2a5c48dc8bf272f6ef88a79aee7dc8199bd283ee2746497
+size 136238
diff --git a/marked/Rel-16/29_series/29002/e47d450f315d0b633906c03cc91f90ef_img.jpg b/marked/Rel-16/29_series/29002/e47d450f315d0b633906c03cc91f90ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f12f501752220ad4398479f12fe0b4d902082646
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e47d450f315d0b633906c03cc91f90ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc0e0519ce0d79922a3e4aa2b12e9acfcbc4c36815b10b200c11cae50b960352
+size 108940
diff --git a/marked/Rel-16/29_series/29002/e4b6ed98fad76b79cb9f85783e13086a_img.jpg b/marked/Rel-16/29_series/29002/e4b6ed98fad76b79cb9f85783e13086a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7715c03f7cbe86630134946297edb799a02a49ed
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e4b6ed98fad76b79cb9f85783e13086a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:732dc016c9e761f98013661a31bf2141494ca7a0b4024a4c2b6650ef7bbe8a4e
+size 74291
diff --git a/marked/Rel-16/29_series/29002/e54b4825299a9c5abf4bdc11266ca4b5_img.jpg b/marked/Rel-16/29_series/29002/e54b4825299a9c5abf4bdc11266ca4b5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db541af3c3a3ac9c99ae53f154bf6805b3c4672f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e54b4825299a9c5abf4bdc11266ca4b5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:071561ca23758864f181f77f1f8b7f17f09124f3f45d237b5b3cbc94a72cf557
+size 145595
diff --git a/marked/Rel-16/29_series/29002/e5640b1b38f2f17ad31dfc251ebdd5b9_img.jpg b/marked/Rel-16/29_series/29002/e5640b1b38f2f17ad31dfc251ebdd5b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3ef8785f2f1748f23a693843730126c2132872c
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e5640b1b38f2f17ad31dfc251ebdd5b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91e553e51ad79773142d0c796f7f213557c1b02a647c8951a525bca7cf16409a
+size 106911
diff --git a/marked/Rel-16/29_series/29002/e645ed71024459749170f5d01e301b37_img.jpg b/marked/Rel-16/29_series/29002/e645ed71024459749170f5d01e301b37_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6d5fe42b4fde6a94bbfee0065db9ad991daa2bc
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e645ed71024459749170f5d01e301b37_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb5c1f3a7939e2e7f4a033fb908c07073a9672ef8c93d65410c1b431d942d9eb
+size 13690
diff --git a/marked/Rel-16/29_series/29002/e9710be0a467e598361041106caa1246_img.jpg b/marked/Rel-16/29_series/29002/e9710be0a467e598361041106caa1246_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2274bb1da0a42d6bb30f90a6fe23a84289e2585f
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/e9710be0a467e598361041106caa1246_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc6e7769943fca647c7378c418ecfbd1bb4473f7217a73955754e3cc610d653f
+size 25909
diff --git a/marked/Rel-16/29_series/29002/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg b/marked/Rel-16/29_series/29002/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..14a65eb1ea3f13f8b762958d932cb310ca0bc7da
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ea6b9ace0ed0694c2ce8dcdb8b5ea52b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72b2c4ef50c775f81abb2ab7bd002a8cf657d0c5d8aef0733d194fb7c41d74a2
+size 17028
diff --git a/marked/Rel-16/29_series/29002/edc59af09c4549de94796dd81a19987f_img.jpg b/marked/Rel-16/29_series/29002/edc59af09c4549de94796dd81a19987f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72b35d4a4f80f96d49b1b80716e5926d96a3887b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/edc59af09c4549de94796dd81a19987f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6065e8369450749c115641bf5591663363069053ac42a2436abbb0f035ff8afc
+size 100459
diff --git a/marked/Rel-16/29_series/29002/ee6c6e5be3d4537bbe12da740318b301_img.jpg b/marked/Rel-16/29_series/29002/ee6c6e5be3d4537bbe12da740318b301_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3df5e302cf44f5a496f827c1e7b969ee3db1d8c4
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ee6c6e5be3d4537bbe12da740318b301_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e529de00f7e6a8f6c1fe23d95c4c199577f34f669f89517b4493fc0fa34f91f
+size 41173
diff --git a/marked/Rel-16/29_series/29002/ef8d84dccd07f6da2dd2abb10ba9d176_img.jpg b/marked/Rel-16/29_series/29002/ef8d84dccd07f6da2dd2abb10ba9d176_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7546d51304d1a81f48965ef729d50e4a6583f12
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/ef8d84dccd07f6da2dd2abb10ba9d176_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85af21575c442b32d36fe763a79919aa89f0b6693bfccff450d3f196005265f3
+size 29901
diff --git a/marked/Rel-16/29_series/29002/f134541214bf186a785a96cfd8b7325b_img.jpg b/marked/Rel-16/29_series/29002/f134541214bf186a785a96cfd8b7325b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88f368ac54c4364d12c297e6a6b2073e9d7c12be
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/f134541214bf186a785a96cfd8b7325b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be1c5a38a2ff17bc518ce594b77ab89afd860194fefbf50dbd80e1ed4b4294d8
+size 123789
diff --git a/marked/Rel-16/29_series/29002/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg b/marked/Rel-16/29_series/29002/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..857164f606b7032d2786d3fd0e220699150115b7
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/f21295f56ab9da5a7ea269beb8cf4afe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f4fc28102d0cdb26388b1e1d8fdb69b512356f16a3ce04fa2206b186d2dba532
+size 108213
diff --git a/marked/Rel-16/29_series/29002/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg b/marked/Rel-16/29_series/29002/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71425456241bc9e55093d7be813a6ae07c361481
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/f2a3faa7fc860dd26eda5b88460b0bcf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1cb91dbb64e0d887df395ad8fae4c70871f34eca56b04dd2cf021782243056f
+size 139181
diff --git a/marked/Rel-16/29_series/29002/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg b/marked/Rel-16/29_series/29002/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d89b3ab37af70a53d820de17827c60a971f92e68
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/f512ae9c630f2fb53197fa77a1bda0e8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8f0d643b8bb76e970f7055c834c22ff1fff503413fcee79e5d45fc60cf7a56f6
+size 110520
diff --git a/marked/Rel-16/29_series/29002/f803be090d37a5189dbc87c1c87b6c63_img.jpg b/marked/Rel-16/29_series/29002/f803be090d37a5189dbc87c1c87b6c63_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..804577297e5437b57ac9620b0c1660ee9cd91e2b
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/f803be090d37a5189dbc87c1c87b6c63_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4833e9bc101d6fb63cf45991442f57c503601ca96645bad798018191c1406c62
+size 144842
diff --git a/marked/Rel-16/29_series/29002/fa676d145fed4fc3621ea24c653c0299_img.jpg b/marked/Rel-16/29_series/29002/fa676d145fed4fc3621ea24c653c0299_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aad2b49aeb4988e50072e89b9206241ce51bd34d
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/fa676d145fed4fc3621ea24c653c0299_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:409df37486e7fd056c2a36c2b6c30da3f12db09a4fe607708075a7d411c9069e
+size 54786
diff --git a/marked/Rel-16/29_series/29002/faa19fa09003307090f38a25ece74252_img.jpg b/marked/Rel-16/29_series/29002/faa19fa09003307090f38a25ece74252_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8ef64e05cc3c70ee47d3cced115b163f604c7cdb
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/faa19fa09003307090f38a25ece74252_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07aed4a211f243d21dc6b2d70d8a2740665c6d81943c9f496053ae3fbddf6c0f
+size 41878
diff --git a/marked/Rel-16/29_series/29002/fad4b22bbd4eb39d94bd3c80cea4cc13_img.jpg b/marked/Rel-16/29_series/29002/fad4b22bbd4eb39d94bd3c80cea4cc13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08c09ab0e8d91df6080ba3bb1470b2c4dc3b3c27
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/fad4b22bbd4eb39d94bd3c80cea4cc13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e31a083b7c45a523aab0f8fc21b1cde41f7fab0656db6fc19cd7a477e18164a
+size 94090
diff --git a/marked/Rel-16/29_series/29002/fc7c83167c4e9e614f40e52b39ef735d_img.jpg b/marked/Rel-16/29_series/29002/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ff28a29a1affdd2438003dbed7038bb8cadd5b6
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/fc7c83167c4e9e614f40e52b39ef735d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:80e461f0bdb4c1da9838e9a12e5fe94d8756ad700d2dfe50f01a785cc5c7708d
+size 148054
diff --git a/marked/Rel-16/29_series/29002/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg b/marked/Rel-16/29_series/29002/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30753b5f027c28d19fd86133871f26055df27774
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/fda85db2e355bb8e3edcd5a74bf3d673_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:559c3db78e0f78ed32b4d1dba8c3603dcb8656bbad34f26eaa631b9f2f819ea0
+size 128805
diff --git a/marked/Rel-16/29_series/29002/fe694a4274db4790f390794fb487ab8f_img.jpg b/marked/Rel-16/29_series/29002/fe694a4274db4790f390794fb487ab8f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e3d2325f471cda9d03e52e7179f4b913de36190
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/fe694a4274db4790f390794fb487ab8f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6dbda7de68e15463757af6d20ec1a86e1c2f4c7c756cf37ad0467647318db1cb
+size 30727
diff --git a/marked/Rel-16/29_series/29002/febfdd6a7182116484c126105b53fdaf_img.jpg b/marked/Rel-16/29_series/29002/febfdd6a7182116484c126105b53fdaf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..213e8dbf09244938a2c5784c233cce33e9175197
--- /dev/null
+++ b/marked/Rel-16/29_series/29002/febfdd6a7182116484c126105b53fdaf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2eed640a6966e297981188798db3a9f78ecc99c5529a71ca055ad6f8ac046b24
+size 70477
diff --git a/marked/Rel-16/29_series/29171/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/29_series/29171/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..506f3a6f3bbb8fece924148d15f01945b65f076b
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4cceaeea36192a4ffc51d6b2b619d8c4c6c78052d2339f66e9def1dd62d9b165
+size 27201
diff --git a/marked/Rel-16/29_series/29171/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29171/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f4652b60be4b2772a1f4a001664442872320bba
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d80d05b11e2f5b762efafbae418ed413f7a6a7b4160610e9da2a8b6ba7e59afa
+size 9417
diff --git a/marked/Rel-16/29_series/29171/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29171/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d25ffe05e9be1418087d3b59d3dc8424816ea866
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4366985a0540974077ba268dedb121cb9f163bdbde04f6d8e85587a54b11c02
+size 6399
diff --git a/marked/Rel-16/29_series/29171/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/Rel-16/29_series/29171/70de8885bd7de15723aaad5eb5c5febf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa1211902f7088e7b9ad3dde06a43cb2fa883ec6
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/70de8885bd7de15723aaad5eb5c5febf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39565b7c64e6b96e1d94a3dfce0718f2bc65bc1e482caaea74a94e252aeafcd4
+size 20163
diff --git a/marked/Rel-16/29_series/29171/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/29_series/29171/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..656cd27b544bfcad6ecd41797d00d3034a5b7d67
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5b4fa1ca96a2685d8529b0f5f59c51bba4bb3a666e2d65424a731f212030ca2c
+size 19198
diff --git a/marked/Rel-16/29_series/29171/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-16/29_series/29171/b90144cfbb81a2d610d920240fda689d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f267e70efeb8aa890b257d0a6486cde977975eb0
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/b90144cfbb81a2d610d920240fda689d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23306cfbd335b78cad86d4379b481a34180192b86694e8817ae17116f4cf81de
+size 20607
diff --git a/marked/Rel-16/29_series/29171/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/29_series/29171/dbe553cf16dd14073b89a8263a428664_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..30d3233558e114da0cfcc19c31ae6c863411abf6
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/dbe553cf16dd14073b89a8263a428664_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f01ae79a439cf8ec68ed66ab38364d14913663dc6f1b88b505ddf7a806152ec
+size 22226
diff --git a/marked/Rel-16/29_series/29171/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/29_series/29171/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c86a6a9840fb55b0f8ffa544e12160b70e4823df
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d1b34b898d0134c470414d67ff600600bd86fa9892718a84d030d8f62cb6c25
+size 20935
diff --git a/marked/Rel-16/29_series/29171/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/29_series/29171/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..654e1a18baa6e96ff16ca3bd1508a0f3afe7d380
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b5a0d400e96f8312fcd498ddb9466745021652496346b658a5f373518c419f6a
+size 30693
diff --git a/marked/Rel-16/29_series/29171/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/29_series/29171/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..024e4d2df0e4ca4f0e60de4b1d26b7f96ba846dd
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05cf0e57efe5d3f078795c448a50d01bac933a82b10dc04d94f52df40a57b795
+size 20523
diff --git a/marked/Rel-16/29_series/29171/raw.md b/marked/Rel-16/29_series/29171/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3368e22ffe7e523c6315675c50dd0b6417d7574e
--- /dev/null
+++ b/marked/Rel-16/29_series/29171/raw.md
@@ -0,0 +1,3113 @@
+
+
+# 3GPP TS 29.171 V16.6.0 (2023-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location Services (LCS); LCS Application Protocol (LCS-AP) between the Mobile Management Entity (MME) and Evolved Serving Mobile Location Centre (E-SMLC); SLs interface (Release 16)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 't' is a green signal icon with three bars. To the right of the 't' are the words 'Advanced Pro' in a smaller font. A small 'TM' symbol is at the bottom right of the 'e'.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon with three bars. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font. A small 'TM' symbol is at the bottom right of the 'P'.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                            |    |
+|------------------------------------------------------------|----|
+| Foreword .....                                             | 6  |
+| 1 Scope.....                                               | 7  |
+| 2 References.....                                          | 7  |
+| 3 Definitions and abbreviations .....                      | 8  |
+| 3.1 Definitions.....                                       | 8  |
+| 3.2 Abbreviations .....                                    | 8  |
+| 4 Functional Overview.....                                 | 9  |
+| 4.1 General .....                                          | 9  |
+| 5 LCS-AP Message Transport .....                           | 9  |
+| 5.1 General .....                                          | 9  |
+| 5.2 Protocol Layering.....                                 | 9  |
+| 5.3 Usage of SCTP Associations.....                        | 10 |
+| 6 LCS-AP Procedures .....                                  | 10 |
+| 6.1 General .....                                          | 10 |
+| 6.2 Procedures Applicable to LCS-AP.....                   | 11 |
+| 6.2.1 Location Service Request.....                        | 11 |
+| 6.2.1.1 General.....                                       | 11 |
+| 6.2.1.2 Successful Operation .....                         | 11 |
+| 6.2.1.3 Unsuccessful Operation .....                       | 12 |
+| 6.2.2 Location Information Exchange .....                  | 13 |
+| 6.2.2.1 Connection Oriented Information Transfer .....     | 13 |
+| 6.2.2.1.1 General .....                                    | 13 |
+| 6.2.2.1.2 Successful Operation.....                        | 13 |
+| 6.2.2.1.3 Abnormal Conditions .....                        | 13 |
+| 6.2.2.2 Connectionless Information Transfer .....          | 14 |
+| 6.2.2.2.1 General .....                                    | 14 |
+| 6.2.2.2.2 Successful Operation.....                        | 14 |
+| 6.2.2.2.3 Unsuccessful Operation.....                      | 14 |
+| 6.2.2.2.4 Abnormal Conditions .....                        | 15 |
+| 6.2.3 Ciphering Keys Delivery .....                        | 15 |
+| 6.2.3.1 General.....                                       | 15 |
+| 6.2.3.2 Successful Operation .....                         | 15 |
+| 6.2.3.3 Unsuccessful Operation .....                       | 15 |
+| 6.3 Exception Procedures.....                              | 16 |
+| 6.3.1 Location Abort.....                                  | 16 |
+| 6.3.1.1 General.....                                       | 16 |
+| 6.3.1.2 Normal Operation .....                             | 16 |
+| 6.3.1.3 Abnormal Conditions.....                           | 16 |
+| 6.3.2 Reset .....                                          | 16 |
+| 6.3.2.1 General.....                                       | 16 |
+| 6.3.2.2 Normal Operation .....                             | 17 |
+| 6.3.2.3 Abnormal Conditions.....                           | 17 |
+| 6.4 Error Handling.....                                    | 17 |
+| 6.4.1 Abnormal Conditions .....                            | 17 |
+| 6.4.2 Overload .....                                       | 17 |
+| 7 LCS-AP Messages and Message Formats .....                | 18 |
+| 7.1 General .....                                          | 18 |
+| 7.2 Message Formats.....                                   | 18 |
+| 7.3 LCS-AP Messages.....                                   | 18 |
+| 7.3.1 LCS-AP Location Request message.....                 | 19 |
+| 7.3.2 LCS-AP Location Response message .....               | 19 |
+| 7.3.3 LCS-AP Location Abort Request message .....          | 20 |
+| 7.3.4 LCS-AP Connection Oriented Information message ..... | 20 |
+
+|        |                                                                  |    |
+|--------|------------------------------------------------------------------|----|
+| 7.3.5  | LCS-AP Connectionless Information message .....                  | 20 |
+| 7.3.6  | LCS-AP Reset Request message .....                               | 21 |
+| 7.3.7  | LCS-AP Reset Acknowledge message .....                           | 21 |
+| 7.3.8  | LCS-AP Ciphering Key Data message .....                          | 21 |
+| 7.3.9  | LCS-AP Ciphering Key Data Result message .....                   | 21 |
+| 7.4    | Information Elements .....                                       | 22 |
+| 7.4.1  | General .....                                                    | 22 |
+| 7.4.2  | Message Type .....                                               | 22 |
+| 7.4.3  | Location Type .....                                              | 22 |
+| 7.4.4  | E-CGI .....                                                      | 22 |
+| 7.4.5  | LCS Client Type .....                                            | 23 |
+| 7.4.6  | LCS Priority .....                                               | 23 |
+| 7.4.7  | LCS QoS .....                                                    | 23 |
+| 7.4.8  | UE Positioning Capability .....                                  | 24 |
+| 7.4.9  | Include Velocity .....                                           | 24 |
+| 7.4.10 | IMSI .....                                                       | 24 |
+| 7.4.11 | IMEI .....                                                       | 25 |
+| 7.4.12 | Geographic Area .....                                            | 26 |
+| 7.4.13 | Positioning Data .....                                           | 29 |
+| 7.4.14 | Velocity Estimate .....                                          | 32 |
+| 7.4.15 | Accuracy Fulfilment Indicator .....                              | 32 |
+| 7.4.16 | LCS Cause .....                                                  | 33 |
+| 7.4.17 | Payload Type .....                                               | 34 |
+| 7.4.18 | APDU .....                                                       | 34 |
+| 7.4.19 | Network Element .....                                            | 34 |
+| 7.4.20 | Return Error Request .....                                       | 34 |
+| 7.4.21 | Return Error Cause .....                                         | 34 |
+| 7.4.22 | Altitude and direction .....                                     | 35 |
+| 7.4.23 | Geographical Coordinates .....                                   | 35 |
+| 7.4.24 | Uncertainty Ellipse .....                                        | 36 |
+| 7.4.25 | Horizontal Speed and Bearing .....                               | 36 |
+| 7.4.26 | Vertical Velocity .....                                          | 36 |
+| 7.4.27 | PLMN Identity .....                                              | 37 |
+| 7.4.28 | Correlation ID .....                                             | 37 |
+| 7.4.29 | eNB ID .....                                                     | 38 |
+| 7.4.30 | LCS Service Type ID .....                                        | 38 |
+| 7.4.31 | Cell Portion ID .....                                            | 38 |
+| 7.4.32 | Civic Address .....                                              | 38 |
+| 7.4.33 | Barometric Pressure .....                                        | 39 |
+| 7.4.34 | RAT Type .....                                                   | 39 |
+| 7.4.35 | Coverage Level .....                                             | 39 |
+| 7.4.36 | Ciphering Data .....                                             | 39 |
+| 7.4.37 | Ciphering Data Ack .....                                         | 40 |
+| 7.4.38 | Ciphering Data Error Report .....                                | 40 |
+| 7.4.39 | Ciphering Data Set .....                                         | 41 |
+| 7.4.40 | Ciphering Data Error Report Contents .....                       | 44 |
+| 7.4.41 | High Accuracy Geographical Coordinates .....                     | 44 |
+| 7.4.42 | High Accuracy Uncertainty Ellipse .....                          | 45 |
+| 7.4.43 | High Accuracy Altitude .....                                     | 45 |
+| 7.4.44 | High Accuracy Extended Uncertainty Ellipse .....                 | 46 |
+| 7.4.45 | High Accuracy Scalable Uncertainty Ellipse .....                 | 46 |
+| 7.4.46 | High Accuracy Scalable Uncertainty Altitude .....                | 46 |
+| 7.5    | Message and information element abstract syntax .....            | 47 |
+| 7.5.1  | General .....                                                    | 47 |
+| 7.5.2  | Usage of protocol extension mechanism for non-standard use ..... | 47 |
+| 7.5.3  | Elementary procedure definitions .....                           | 47 |
+| 7.5.4  | PDU definitions .....                                            | 50 |
+| 7.5.5  | Information element definitions .....                            | 54 |
+| 7.5.6  | Common definitions .....                                         | 63 |
+| 7.5.7  | Constant definitions .....                                       | 64 |
+| 7.5.8  | Container Definitions .....                                      | 65 |
+| 7.5.9  | Message transfer syntax .....                                    | 67 |
+
+|                                              |                                                                  |           |
+|----------------------------------------------|------------------------------------------------------------------|-----------|
+| 7.6                                          | Handling of unknown, unforeseen and erroneous protocol data..... | 67        |
+| 8                                            | LCS-AP Timers.....                                               | 67        |
+| 8.1                                          | General .....                                                    | 67        |
+| 8.2                                          | Timers of LCS-AP .....                                           | 67        |
+| <b>Annex A (informative): Change history</b> |                                                                  | <b>68</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the procedures and information coding for LCS Application Protocol (LCS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in 3GPP TS 23.271 [3].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 36.305: "Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN".
+- [3] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
+- [4] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [5] TTA/EIA/IS-J-STD-036 (2000): "Wireless Enhanced Emergency Services".
+- [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+- [7] 3GPP TS 36.413: "S1 Application Protocol (S1AP)".
+- [8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+- [9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification".
+- [10] 3GPP TS 22.071: "Location Services (LCS); Service Description; Stage1".
+- [11] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [12] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)".
+- [13] IETF RFC 4119: "A Presence-based GEOPRIV Location Object Format".
+
+- [14] IETF RFC 5139: "Revised Civic Location Format for Presence Information Data Format Location Object".
+- [15] IETF RFC 6848: "Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)".
+- [16] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification".
+- [17] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Elementary Procedure:** LCS-AP protocol consists of Elementary Procedures (EPs). An LCS-AP Elementary Procedure is a unit of interaction between the MME and the E-SMLC. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
+
+- **Class 1:** Elementary Procedures with response (success or failure),
+- **Class 2:** Elementary Procedures without response.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|         |                                                    |
+|---------|----------------------------------------------------|
+| CID     | Cell-ID (positioning method)                       |
+| E-CID   | Enhanced Cell-ID (positioning method)              |
+| E-SMLC  | Enhanced Serving Mobile Location Centre            |
+| E-UTRAN | Evolved Universal Terrestrial Radio Access Network |
+| GNSS    | Global Navigation Satellite System                 |
+| GPS     | Global Positioning System                          |
+| LCS     | LoCation Services                                  |
+| LCS-AP  | LCS Application Protocol                           |
+| LPP     | LTE Positioning Protocol                           |
+| LPPa    | LTE Positioning Protocol Annex                     |
+| LTE     | Long Term Evolution                                |
+| MBS     | Metropolitan Beacon System                         |
+| MO-LR   | Mobile Originated Location Request                 |
+| MT-LR   | Mobile Terminated Location Request                 |
+| NI-LR   | Network Induced Location Request                   |
+| MME     | Mobility Management Entity                         |
+| OTDOA   | Observed Time Difference Of Arrival                |
+| PDU     | Protocol Data Unit                                 |
+| SCTP    | Stream Control Transmission Protocol               |
+| SET     | SUPL Enabled Terminal                              |
+| SLP     | SUPL Location Platform                             |
+| SUPL    | Secure User Plane Location                         |
+| TA      | Timing Advanced                                    |
+| UE      | User Equipment                                     |
+| U-TDOA  | Uplink Time Difference Of Arrival                  |
+
+# 4 Functional Overview
+
+## 4.1 General
+
+Figure 4.1-1 below shows the architecture applicable to the positioning of a UE with E-UTRAN access. The SLs interface is used to convey LCS-AP messages and parameters between the MME to the E-SMLC. It is also used for tunnelling LTE Positioning Protocols (LPP between the E-SMLC and the target UE, LPPa between the E-SMLC and the eNB), which are transparent to the MME as described in 3GPP TS 36.305 [2].
+
+![Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces.](dbe553cf16dd14073b89a8263a428664_img.jpg)
+
+```
+graph LR; UE[UE] -- LTE-Uu --> SeNB[Serving eNB]; SeNB -- S1 --> MME[MME]; NeNB[Neighbor eNB] -- S1 --> MME; MME -- SLs --> E-SMLC[E-SMLC];
+```
+
+The diagram illustrates the network architecture for positioning. A User Equipment (UE) is connected to a Serving eNB via the LTE-Uu interface. The Serving eNB is connected to an MME via the S1 interface. A Neighbor eNB is also connected to the MME via the S1 interface. The MME is connected to an E-SMLC via the SLs interface.
+
+Diagram of positioning interfaces in E-UTRAN showing UE, Serving eNB, Neighbor eNB, MME, and E-SMLC connected via LTE-Uu, S1, and SLs interfaces.
+
+Figure 4.1-1 Positioning Interfaces in E-UTRAN
+
+# 5 LCS-AP Message Transport
+
+## 5.1 General
+
+The LCS-AP is a logical interface between the MME and the E-SMLC. This clause specifies the standards for signaling transport to be used across LCS-AP.
+
+## 5.2 Protocol Layering
+
+Figure 5.2-1 below shows the protocol layering used to support the transfer of LCS-AP PDUs between an E-SMLC and a MME. The LTE Positioning Protocols (LPP and LPPa) can be carried in LCS-AP messages which are transparent to the MME.
+
+![Figure 5.2-1: Protocol Layering for LCS-AP. The diagram shows two protocol stacks. The left stack is for the MME, with layers from top to bottom: NAS (labeled 'Relay'), S1-AP, SCTP, IP, L2, and L1. The right stack is for the E-SMLC, with layers from top to bottom: LPP/LPPa, LCS-AP, SCTP, IP, L2, and L1. A vertical dashed line labeled 'SLs' separates the two stacks. Horizontal dashed lines connect corresponding layers between the MME and E-SMLC: NAS to LCS-AP, SCTP to SCTP, IP to IP, L2 to L2, and L1 to L1.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+Figure 5.2-1: Protocol Layering for LCS-AP. The diagram shows two protocol stacks. The left stack is for the MME, with layers from top to bottom: NAS (labeled 'Relay'), S1-AP, SCTP, IP, L2, and L1. The right stack is for the E-SMLC, with layers from top to bottom: LPP/LPPa, LCS-AP, SCTP, IP, L2, and L1. A vertical dashed line labeled 'SLs' separates the two stacks. Horizontal dashed lines connect corresponding layers between the MME and E-SMLC: NAS to LCS-AP, SCTP to SCTP, IP to IP, L2 to L2, and L1 to L1.
+
+Figure 5.2-1 Protocol Layering for LCS-AP
+
+## 5.3 Usage of SCTP Associations
+
+SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of LCS-AP messages.
+
+Semi-permanent SCTP associations shall be established between MME and E-SMLC, i.e. the SCTP associations shall remain up under normal circumstances.
+
+Local multi-homing should be supported. Remote multi-homing shall be supported.
+
+Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and E-SMLC.
+
+The MME shall establish the SCTP association. Since under normal operation there should always be an SCTP association established between an MME and an E-SMLC, if the E-SMLC needs to initiate a message towards an MME it shall do so over an existing SCTP association already established with that MME.
+
+When an entity detects that an SCTP association has been lost, all resources for transactions open on that association shall be released.
+
+The registered port number for LCS-AP is 9082. The registered payload protocol identifier for LCS-AP is 29.
+
+# 6 LCS-AP Procedures
+
+## 6.1 General
+
+The LCS-AP interface can be divided into the following procedures:
+
+- Location service request procedure
+- Location information exchange procedure
+
+The E-UTRAN positioning capabilities are intended to be forward compatible to other access types and other position methods, in an effort to reduce the amount of additional positioning support needed in the future.
+
+## 6.2 Procedures Applicable to LCS-AP
+
+### 6.2.1 Location Service Request
+
+#### 6.2.1.1 General
+
+The purpose of the location service request procedure is to obtain the location estimate for a target UE in E-UTRAN.
+
+#### 6.2.1.2 Successful Operation
+
+![Sequence diagram of the Location Service Request Procedure, Successful Operation. The diagram shows two vertical lifelines: MME on the left and E-SMLC on the right. A horizontal arrow labeled 'LOCATION REQUEST' points from the MME to the E-SMLC. A horizontal arrow labeled 'LOCATION RESPONSE' points from the E-SMLC back to the MME. Both lifelines end with a thick horizontal bar at the bottom.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg)
+
+```
+sequenceDiagram
+    participant MME
+    participant E-SMLC
+    Note left of MME: Initiator
+    MME->>E-SMLC: LOCATION REQUEST
+    Note right of E-SMLC: Responder
+    E-SMLC-->>MME: LOCATION RESPONSE
+```
+
+Sequence diagram of the Location Service Request Procedure, Successful Operation. The diagram shows two vertical lifelines: MME on the left and E-SMLC on the right. A horizontal arrow labeled 'LOCATION REQUEST' points from the MME to the E-SMLC. A horizontal arrow labeled 'LOCATION RESPONSE' points from the E-SMLC back to the MME. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 6.2.1.2-1 Location Service Request Procedure, Successful Operation**
+
+The initiator (MME) of the location service request procedure sends a LCS-AP Location Request message to the E-SMLC associated with the current or last known serving cell for the target UE and starts the timer T3x01. The message contains the following mandatory (M), conditional (C) and optional (O) information, where conditional parameters are required if available.
+
+- Correlation ID (M)
+- Location Type (M)
+- Cell Identifier (M)
+- LCS Client Type (C)
+- LCS Priority (C)
+- LCS Service Type ID (C)
+- LCS QoS (C)
+- UE Positioning Capability (O)
+- Include Velocity (O)
+- IMSI of target UE (O)
+- IMEI of target UE (O)
+- APDU (O)
+- RAT Type (O)
+- Coverage Level (O)
+
+The Correlation ID is assigned by the MME and enables association of the location response with the location request when more than one location service request procedure is ongoing for the UE with the same E-SMLC.
+
+The Location Type IE indicates the type of Location Information being requested. The following types are supported:
+
+- Current geographic location estimate
+- Location assistance data for the target UE
+- Last known location estimate
+
+If the location estimate is requested, the E-SMLC performs positioning procedure on the target UE using a particular position method or a combination of more than one positioning method based on the UE capability. If UE capability is unknown, the E-SMLC may request UE position capability through LPP as defined in 3GPP TS 36.305 [2].
+
+Alternatively, if assistance data was requested, the E-SMLC may provide positioning assistance data to the UE. The E-SMLC may invoke the following LCS-AP procedures to get assistance data:
+
+- Connection Oriented Information Transfer
+- Connectionless Information Transfer
+
+Otherwise, if a last known location estimate is requested, the E-SMLC obtains a geographic location estimate using only the information provided in the LCS-AP Location Request message. The E-SMLC shall not attempt to obtain location information for the target UE from either the E-UTRAN or the target UE (e.g. because the UE may not be currently reachable).
+
+If a location estimate or a last known location estimate was requested and was subsequently obtained, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request using the same SCTP association as the location request. This message contains the following mandatory (M), conditional (C) and optional parameters (O).
+
+- Correlation ID (M)
+- Location Estimate (M).
+- Accuracy Fulfilment Indicator (O).
+- Velocity estimate (C).
+- Positioning Data (C).
+- E-UTRAN Cell Identifier (O).
+- Cell Portion ID (O).
+- Civic Address (O).
+- Barometric Pressure (O).
+
+If assistance data was instead requested for an UE and the E-SMLC was able successfully to transfer this to the UE, the E-SMLC shall return a LCS-AP Location Response to the initiator of the location request (MME). This message shall contain no parameters. The absence of a LCS Cause parameter in this case implies that the transfer was successful.
+
+If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01.
+
+#### 6.2.1.3 Unsuccessful Operation
+
+If the E-SMLC is unable to obtain any of the location information requested or if requested LCS assistance data could not be transferred, the E-SMLC shall return a LCS-AP Location Response to the initiator of the Location Request carrying the following parameters:
+
+- Correlation ID (M)
+- LCS Cause (M)
+- Positioning Data (O)
+
+The E-SMLC shall use the same SCTP association for the Location Response as was used for the request.
+
+If the MME receives the LCS-AP Location Response for corresponding request message, the MME shall stop the timer T3x01.
+
+On the expiry of the timer T3x01, the MME shall abort the procedure, release any resources allocated for this location request procedure and notify the node that triggered the Location Request about the error.
+
+### 6.2.2 Location Information Exchange
+
+#### 6.2.2.1 Connection Oriented Information Transfer
+
+##### 6.2.2.1.1 General
+
+The Connection Oriented Information transfer procedure enables two-way transfer of LPP and LPPa messages between an E-SMLC and a MME. The procedure is only valid while a location request procedure for the target UE is ongoing. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE.
+
+##### 6.2.2.1.2 Successful Operation
+
+![Diagram illustrating the successful operation of Connection Oriented Information transfer. Endpoint A sends a message labeled 'CONNECTION ORIENTED INFORMATION' to Endpoint B.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+```
+graph LR; A[Endpoint A] -- "CONNECTION ORIENTED INFORMATION" --> B[Endpoint B];
+```
+
+Diagram illustrating the successful operation of Connection Oriented Information transfer. Endpoint A sends a message labeled 'CONNECTION ORIENTED INFORMATION' to Endpoint B.
+
+**Figure 6.2.2.1.2-1 Connection Oriented Information, Successful Operation**
+
+The initiator of the procedure (E-SMLC or MME) with a LPP or LPPa message to transfer concerning a particular target UE sends a LCS-AP Connection Oriented Information message to a recipient carrying the following parameters:
+
+- Correlation ID (M)
+- Payload Type (M)
+- APDU (M);
+
+The Correlation ID in this message is the Correlation ID used for the Location Request. It shall be present for a message transfer from the E-SMLC to the MME and for a message transfer from the MME to the E-SMLC.
+
+The Payload Type shall be present to indicate the type of the APDU. The supported information types are LPP and LPPa.
+
+The APDU shall contain an LPP APDU when communicating between the E-SMLC and the target UE or an LPPa APDU when communicating between the E-SMLC and serving eNB. The MME shall forward this to the serving eNB for the target UE.
+
+If the intended recipient is the E-SMLC for a target UE, the message is terminated in the E-SMLC. The E-SMLC shall then perform interpretation of the APDU.
+
+##### 6.2.2.1.3 Abnormal Conditions
+
+At an intermediate entity, if a received LCS-AP Connection Oriented Information message contains unrecognized information or if the message cannot be sent on, the message shall be discarded.
+
+#### 6.2.2.2 Connectionless Information Transfer
+
+##### 6.2.2.2.1 General
+
+The Connectionless Information transfer procedure enables two-way transfer of LPPa messages between an E-SMLC and a MME when there is no existing signalling connection association. This procedure can be used to query eNBs for the information not related to a UE connection, such as Timing information on the eNB.
+
+##### 6.2.2.2.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the Connectionless Information Procedure between Endpoint A and Endpoint B. Endpoint A sends a CONNECTIONLESS INFORMATION message to Endpoint B, and Endpoint B responds with a CONNECTIONLESS INFORMATION message.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+```
+sequenceDiagram
+    participant Endpoint A
+    participant Endpoint B
+    Note left of Endpoint A: 
+    Endpoint A->>Endpoint B: CONNECTIONLESS INFORMATION
+    Note right of Endpoint B: 
+    Endpoint B->>Endpoint A: CONNECTIONLESS INFORMATION
+    Note left of Endpoint A: 
+    Note right of Endpoint B: 
+```
+
+Sequence diagram showing the successful operation of the Connectionless Information Procedure between Endpoint A and Endpoint B. Endpoint A sends a CONNECTIONLESS INFORMATION message to Endpoint B, and Endpoint B responds with a CONNECTIONLESS INFORMATION message.
+
+**Figure 6.2.2.2.2-1 Connectionless Information Procedure, Successful Operation**
+
+The initiator of the procedure (either E-SMLC or MME) sends a LCS-AP Connectionless Information message to a recipient carrying the following parameters:
+
+- Source Entity (M)
+- Destination Entity (M)
+- APDU (M)
+- Return Error Request (O)
+
+The source entity identifies the sender. The recipient entity identifies the final destination. The APDU contains a LPPa APDU to be transferred. The Return Error Request may be included to request notification in the event of unsuccessful transfer and indicate the type of notification needed. If the recipient entity is not the final destination, the recipient shall transfer the LCS-AP Connectionless Information message to either the final destination or an intermediate entity capable of forward it to the final destination.
+
+##### 6.2.2.2.3 Unsuccessful Operation
+
+If the message cannot be transferred by an intermediate entity or destination entity and the Return Error Request is not included, the message shall be discarded. If the Return Error Request is included, the intermediate or destination entity shall, depending on the Return Error Request type, send a LCS-AP Connectionless Information message to, or towards, the original source containing the following parameters:
+
+- Source Entity (M)
+- Destination Entity (M)
+- APDU (M)
+- Return Error Cause (M)
+
+The Source entity shall indicate the Destination Entity in the original received message. The Destination Entity shall indicate the Source Entity in the original message. The Return Error cause shall indicate the reason for unsuccessful transfer. The APDU shall contain any originally received APDU.
+
+If a received LCS-AP Connectionless Information message containing a Return Error Cause cannot be transferred by an intermediate entity, it shall be discarded with no return error message.
+
+##### 6.2.2.2.4 Abnormal Conditions
+
+At an intermediate entity, if a received LCS-AP Connectionless Information message contains unrecognized or invalid information, the message shall be discarded.
+
+At the recipient entity, if a received LCS-AP Connectionless Information message contains invalid or unrecognized information as defined for LCS-AP, the message shall be discarded.
+
+### 6.2.3 Ciphering Keys Delivery
+
+#### 6.2.3.1 General
+
+The purpose of the ciphering keys delivery procedure is to enable the E-SMLC to send ciphering keys for broadcast assistance data to the MME so that the MME can then distribute the ciphering keys to suitably subscribed UEs.
+
+#### 6.2.3.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the Ciphering Keys Delivery Procedure. The E-SMLC sends a CIPHERING KEY DATA message to the MME, and the MME responds with a CIPHERING KEY DATA RESULT message.](70de8885bd7de15723aaad5eb5c5febf_img.jpg)
+
+```
+sequenceDiagram
+    participant E-SMLC
+    participant MME
+    Note left of MME: 
+    E-SMLC->>MME: CIPHERING KEY DATA
+    Note right of MME: 
+    MME->>E-SMLC: CIPHERING KEY DATA RESULT
+    Note right of E-SMLC: 
+```
+
+Sequence diagram showing the successful operation of the Ciphering Keys Delivery Procedure. The E-SMLC sends a CIPHERING KEY DATA message to the MME, and the MME responds with a CIPHERING KEY DATA RESULT message.
+
+**Figure 6.2.3.2-1 Ciphering Keys Delivery Procedure, Successful Operation**
+
+The initiator (E-SMLC) of the ciphering keys delivery procedure sends a Ciphering Key Data message to the MME and starts the timer T3x03. The message contains the following mandatory (M) information:
+
+- Ciphering Data (M):
+
+If the MME is able to successfully store all ciphering data sets included in the Ciphering Key Data message, the MME sends a Ciphering Key Data Result message. The message contains the following mandatory (M) information:
+
+- Ciphering Data Ack (M)
+
+If the E-SMLC receives the Ciphering Key Data Result message, the E-SMLC shall stop the timer T3x03.
+
+#### 6.2.3.3 Unsuccessful Operation
+
+If the MME is unable to successfully store one or more ciphering data sets included in the Ciphering Key Data message, the MME shall return a Ciphering Key Data Result message carrying the following mandatory (M) information:
+
+- Ciphering Data Error Report (M)
+
+If the E-SMLC receives the Ciphering Key Data Result message message, the E-SMLC shall stop the timer T3x03.
+
+On the expiry of the timer T3x03, the E-SMLC shall abort the procedure and release any resources allocated for this ciphering keys delivery procedure.
+
+## 6.3 Exception Procedures
+
+### 6.3.1 Location Abort
+
+#### 6.3.1.1 General
+
+The purpose of the Location Abort procedure is to cancel an ongoing positioning attempt or the request for assistance data. This message can be sent from the MME to the E-SMLC. This procedure makes use of the same SCTP association as the location request procedure for the particular target UE.
+
+#### 6.3.1.2 Normal Operation
+
+![Sequence diagram of the Location Abort Procedure, Normal Operation. The MME sends a LOCATION ABORT REQUEST message to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE message.](b90144cfbb81a2d610d920240fda689d_img.jpg)
+
+```
+sequenceDiagram
+    participant MME
+    participant E-SMLC
+    Note left of MME: 
+    MME->>E-SMLC: LOCATION ABORT REQUEST
+    Note right of E-SMLC: 
+    E-SMLC-->>MME: LOCATION RESPONSE
+    Note left of MME: 
+    Note right of E-SMLC: 
+```
+
+Sequence diagram of the Location Abort Procedure, Normal Operation. The MME sends a LOCATION ABORT REQUEST message to the E-SMLC, and the E-SMLC responds with a LOCATION RESPONSE message.
+
+**Figure 6.3.1.2-1 Location Abort Procedure, Normal Operation**
+
+The MME sends a LCS-AP Location Abort Request message to the E-SMLC across the SLs interface. The message contains a LCS Cause parameter indicating the reason of cancellation.
+
+On receipt of this message, the E-SMLC shall stop the positioning transactions of the target UE and may release any resources previously allocated. The E-SMLC shall return a LCS-AP Location Response message containing the LCS Cause received in Location Abort Request and, optionally, positioning data. The E-SMLC may also optionally include in this response any "best-effort" location estimate that it has already determined prior to receiving the LCS-AP Location Abort Request.
+
+#### 6.3.1.3 Abnormal Conditions
+
+At the recipient entity, if no ongoing location transaction for the target UE is found, the recipient entity shall discard the received LCS-AP Location Abort Request message with no return error message.
+
+### 6.3.2 Reset
+
+#### 6.3.2.1 General
+
+The Reset procedure is an optional procedure applicable to the LCS-AP. It enables an E-SMLC or a MME that has undergone a failure with loss of location service transactions to indicate this to a partner entity. The recipient entity can then release its own connection and transaction resources. The Reset procedure may not be applicable when only a limited part of an E-SMLC or a MME has suffered a failure, since error recovery procedures specific to individual connections and transactions may then be used. The Reset procedure applies to all transactions initiated on a single SCTP association.
+
+#### 6.3.2.2 Normal Operation
+
+![Sequence diagram illustrating the Reset Procedure, Normal Operation. Endpoint A sends a RESET REQUEST to Endpoint B, and Endpoint B responds with a RESET ACKNOWLEDGE.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+```
+sequenceDiagram
+    participant Endpoint A
+    participant Endpoint B
+    Note left of Endpoint A: 
+    Endpoint A->>Endpoint B: RESET REQUEST
+    Note right of Endpoint B: 
+    Endpoint B-->>Endpoint A: RESET ACKNOWLEDGE
+    Note left of Endpoint A: 
+    Note right of Endpoint B: 
+```
+
+Sequence diagram illustrating the Reset Procedure, Normal Operation. Endpoint A sends a RESET REQUEST to Endpoint B, and Endpoint B responds with a RESET ACKNOWLEDGE.
+
+Figure 6.3.2.2-1 Reset Procedure, Normal Operation
+
+In the event of a failure at an E-SMLC or a MME that results in the loss of location service transactions, a LCS-AP Reset Request message may be sent to the partner entity across the SLs interface. The message contains a LCS Cause parameter indicating the reason for the reset. The sending entity shall ensure that all information on location service transactions for the SCTP association on which the Reset Request was sent is reinitialized to indicate no existing transactions.
+
+On receiving a LCS-AP Reset Request message, the recipient entity (E-SMLC or MME) shall clear all references and state information for the location service transactions on the SCTP association on which the Reset Request was received and shall release any associated resources. The recipient entity shall then return a LCS-AP Reset Acknowledge message using the same SCTP association as the Reset Request.
+
+If the initiating entity (E-SMLC or MME) received the LCS-AP Reset Acknowledge message, it shall stop the timer T3x02.
+
+#### 6.3.2.3 Abnormal Conditions
+
+On the first expiry of the timer T3x02, the Source entity (E-SMLC or MME) shall resend the LCS-AP Reset Request message and shall reset and restart timer T3x02. This retransmission is repeated a maximum of "n" times, where "n" is an O&M administered parameter. Following "n" unsuccessful reset attempts, the procedure shall be terminated and maintenance shall be informed.
+
+## 6.4 Error Handling
+
+### 6.4.1 Abnormal Conditions
+
+If an ongoing location request is pre-empted at the initiator by an inter-eNB handover and MME relocation, or if the main signalling link to the target UE is released by the MME, or if a main signalling link failure indicated by the serving eNodeB persists for more than a certain timeout interval or if there is a timeout waiting for the positioning response, or any other abnormal conditions for which the positioning procedure cannot be maintained, the MME shall send a LCS-AP Location Abort message to the E-SMLC to terminate the positioning procedure.
+
+For Intra-MME handovers, the location session between the MME and E-SMLC is not affected. Application layer impacts on these handovers are handled by higher protocol layers.
+
+If the E-SMLC cannot proceed with positioning due to some protocol violation or error condition (e.g. inter-eNB handover), it shall return a LCS-AP Location Response message to the initiator containing a LCS cause and, optionally, positioning data.
+
+### 6.4.2 Overload
+
+If an E-SMLC is in overload condition, it may reject a LCS-AP Location Request by returning a LCS-AP Location Response containing a LCS Cause parameter indicating congestion. The initiator of the location requests (i.e. MME) may reduce the frequency of later location requests until rejection due to overload has ceased. In reducing the frequency
+
+of location service requests, the MME shall reduce lower priority requests, to zero if necessary, before reducing the frequency of higher priority requests. An E-SMLC shall similarly reject location requests of a lower priority, to zero if necessary, due to overload before rejecting location requests of a higher priority. An E-SMLC in overload condition may optionally employ the following procedures to alleviate overload:
+
+- a) Allow higher priority location service requests to pre-empt lower priority requests for which location service procedures are already in progress.
+- b) Abort lower priority location service requests already in progress.
+- c) Reduce the supported QoS for lower priority requests for a location estimate – e.g. by reducing accuracy or increasing response time.
+- d) Employ UE based positioning methods, where supported by the target UE and the E-SMLC, rather than UE assisted or network based methods (except TA).
+
+The priority of a location request shall be defined according to the value in the LCS Priority parameter. If this parameter is absent in a LCS-AP Location Request, the lowest priority shall be assumed.
+
+# --- 7 LCS-AP Messages and Message Formats
+
+## 7.1 General
+
+This clause describes the structure of the messages and information elements required for the LCS-AP messages.
+
+## 7.2 Message Formats
+
+LCS-AP ASN.1 definition conforms to ITU-T Recommendations ITU-T Recommendation X.680 (07/2002) [8] and ITU-T Recommendation X.681 (07/2002) [9]. The ASN.1 definition specifies the structure and content of LCS-AP messages. The LCS-AP messages may contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error.
+
+For the handling of unknown, unforeseen and erroneous protocol data, please refer to 3GPP TS 36.413 [7].
+
+## 7.3 LCS-AP Messages
+
+The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in 3GPP TS 36.413 [7].
+
+### 7.3.1 LCS-AP Location Request message
+
+This message is sent by the MME to request a location estimate for a target UE and contains sufficient information to enable location according to the required QoS using any positioning method supported. The message is also used to request LCS assistance data transfer to an UE.
+
+Direction: MME → E-SMLC
+
+**Table 7.3.1-1: Location Request message contents**
+
+| IE/Group Name             | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type              | M        |       | 7.4.2                 |                       | YES         | reject               |
+| Correlation ID            | M        |       | 7.4.28                |                       | YES         | reject               |
+| Location Type             | M        |       | 7.4.3                 |                       | YES         | reject               |
+| E-UTRAN Cell Identifier   | M        |       | E-CGI / 7.4.4         |                       | YES         | ignore               |
+| LCS Client Type           | O        |       | 7.4.5                 |                       | YES         | reject               |
+| LCS Priority              | O        |       | 7.4.6                 |                       | YES         | reject               |
+| LCS QoS                   | O        |       | 7.4.7                 |                       | YES         | reject               |
+| LCS Service Type ID       | O        |       | 7.4.30                |                       | YES         | ignore               |
+| UE Positioning Capability | O        |       | 7.4.8                 |                       | YES         | reject               |
+| Include Velocity          | O        |       | 7.4.9                 |                       | YES         | reject               |
+| IMSI                      | O        |       | 7.4.10                |                       | YES         | ignore               |
+| IMEI                      | O        |       | 7.4.11                |                       | YES         | ignore               |
+| Multiple APDUs            |          | 0..3  |                       |                       |             |                      |
+| APDU                      | M        |       | 7.4.18                |                       | YES         | reject               |
+| RAT Type                  | O        |       | 7.4.34                |                       | YES         | ignore               |
+| Coverage Level            | O        |       | 7.4.35                |                       | YES         | ignore               |
+
+NOTE: The IMSI should be sent preferably if known. The IMEI may be sent if the IMSI is not known, or in addition to the IMSI for the purpose of allowing correlation between the two identities.
+
+### 7.3.2 LCS-AP Location Response message
+
+This message is sent in response to a LCS-AP Location Request to return a successful location estimate for a target UE or to indicate some failure in obtaining this. The message is also sent in response to a LCS-AP Location Request to return an indication that LCS assistance data has been successfully delivered to an UE.
+
+Direction: E-SMLC → MME
+
+**Table 7.3.2-1: Location Response message contents**
+
+| IE/Group Name                 | Presence | Range | IE type and reference    | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------|
+| Message Type                  | M        |       | 7.4.2                    |                       | YES         | reject               |
+| Correlation ID                | M        |       | 7.4.28                   |                       | YES         | reject               |
+| Location Estimate             | O        |       | Geographic Area / 7.4.12 |                       | YES         | reject               |
+| Positioning Data              | O        |       | 7.4.13                   |                       | YES         | reject               |
+| Velocity Estimate             | O        |       | 7.4.14                   |                       | YES         | reject               |
+| Accuracy Fulfilment Indicator | O        |       | 7.4.15                   |                       | YES         | reject               |
+| LCS Cause                     | O        |       | 7.4.16                   |                       | YES         | ignore               |
+| E-UTRAN Cell Identifier       | O        |       | E-CGI / 7.4.4            |                       | YES         | ignore               |
+| Cell Portion ID               | O        |       | 7.4.31                   |                       | YES         | ignore               |
+| Civic Address                 | O        |       | 7.4.32                   |                       | YES         | ignore               |
+| Barometric Pressure           | O        |       | 7.4.33                   |                       | YES         | ignore               |
+
+### 7.3.3 LCS-AP Location Abort Request message
+
+This message is sent by the MME to abort the positioning attempt or the request for assistance data.
+
+Direction: MME → E-SMLC
+
+**Table 7.3.3-1: Location Abort Request message contents**
+
+| IE/Group Name  | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type   | M        |       | 7.4.2                 |                       | YES         | reject               |
+| Correlation ID | M        |       | 7.4.28                |                       | YES         | reject               |
+| LCS Cause      | M        |       | 7.4.16                |                       | YES         | ignore               |
+
+### 7.3.4 LCS-AP Connection Oriented Information message
+
+This message is sent in association with an existing signalling connection between an E-SMLC and another entity to transfer information between the E-SMLC and other entity belonging to a higher level protocol.
+
+Direction: E-SMLC → MME or MME → E-SMLC
+
+**Table 7.3.4-1: Connection Oriented Information message contents**
+
+| IE/Group Name  | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type   | M        |       | 7.4.2                 |                       | YES         | reject               |
+| Correlation ID | M        |       | 7.4.28                |                       | YES         | reject               |
+| Payload Type   | M        |       | 7.4.17                |                       | YES         | reject               |
+| APDU           | M        |       | 7.4.18                |                       | YES         | reject               |
+
+### 7.3.5 LCS-AP Connectionless Information message
+
+This message conveys signalling information associated with a higher protocol level between an E-SMLC and another entity when there is no existing signalling connection association.
+
+Direction: E-SMLC → MME or MME → E-SMLC
+
+**Table 7.3.5-1: Connectionless Information message contents**
+
+| IE/Group Name        | Presence | Range | IE type and reference    | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|--------------------------|-----------------------|-------------|----------------------|
+| Message Type         | M        |       | 7.4.2                    |                       | YES         | reject               |
+| Source Identity      | M        |       | Network Element / 7.4.19 |                       | YES         | reject               |
+| Destination Identity | M        |       | Network Element / 7.4.19 |                       | YES         | reject               |
+| APDU                 | M        |       | 7.4.18                   |                       | YES         | reject               |
+| Return Error Request | O        |       | 7.4.20                   |                       | YES         | reject               |
+| Return Error Cause   | O        |       | 7.4.21                   |                       | YES         | ignore               |
+
+### 7.3.6 LCS-AP Reset Request message
+
+This message is sent to indicate a failure in the sending entity with loss of location service transactions that were established or were being established.
+
+Direction: E-SMLC → MME or MME → E-SMLC
+
+**Table 7.3.6-1: Reset Request message contents**
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type  | M        |       | 7.4.2                 |                       | YES         | reject               |
+| LCS Cause     | M        |       | 7.4.16                |                       | YES         | ignore               |
+
+### 7.3.7 LCS-AP Reset Acknowledge message
+
+This message is sent in response to a LCS-AP Reset message to indicate that references and resources associated with location service transactions towards the entity sending the LCS-AP Reset have been released.
+
+Direction: E-SMLC → MME or MME → E-SMLC
+
+**Table 7.3.7-1: Reset Acknowledge message contents**
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type  | M        |       | 7.4.2                 |                       | YES         | reject               |
+
+### 7.3.8 LCS-AP Ciphering Key Data message
+
+This message is used by the E-SMLC to send ciphering keys for broadcast assistance data to the MME.
+
+Direction: E-SMLC → MME
+
+**Table 7.3.8-1: Ciphering Key Data message contents**
+
+| IE/Group Name  | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type   | M        |       | 7.4.2                 |                       | YES         | reject               |
+| Ciphering Data | M        |       | 7.4.36                |                       | YES         | reject               |
+
+### 7.3.9 LCS-AP Ciphering Key Data Result message
+
+This message is used by the MME to indicate to the E-SMLC whether the MME was able to successfully store the ciphering data sets received from the E-SMLC in a Ciphering Data Key message.
+
+Direction: MME → E-SMLC
+
+**Table 7.3.9-1: Ciphering Key Data Result message contents**
+
+| IE/Group Name               | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-----------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type                | M        |       | 7.4.2                 |                       | YES         | reject               |
+| Ciphering Data Ack          | C        |       | 7.4.37                |                       | YES         | reject               |
+| Ciphering Data Error Report | C        |       | 7.4.38                |                       | YES         | reject               |
+
+## 7.4 Information Elements
+
+### 7.4.1 General
+
+When specifying information elements which are to be represented by bit strings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
+
+- The first bit (leftmost bit) contains the most significant bit (MSB)
+- The last bit (rightmost bit) contains the least significant bit (LSB)
+- When importing bit strings from other specifications, the first bit of the bit string contains the first bit of the concerned information
+
+### 7.4.2 Message Type
+
+The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages.
+
+**Table 7.4.2-1: Message Type**
+
+| IE/Group Name   | Presence | Range | IE type and reference                                                          | Semantics description                                                                                                                                                                                                                      |
+|-----------------|----------|-------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure Code  | M        |       | INTEGER (0..255)                                                               | "0" = LCS-AP LOCATION SERVICE REQUEST<br>"1" = LCS-AP CONNECTION ORIENTED INFORMATION TRANSFER<br>"2" = LCS-AP CONNECTIONLESS INFORMATION TRANSFER<br>"3" = LCS-AP LOCATION ABORT<br>"4" = LCS-AP RESET<br>"5" = LCS-AP CIPHERING KEY DATA |
+| Type of Message | M        |       | ENUMERATED (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) |                                                                                                                                                                                                                                            |
+
+### 7.4.3 Location Type
+
+This parameter defines the type of location information being requested.
+
+**Table 7.4.3-1: Location Type**
+
+| IE/Group Name | Presence | Range | IE type and reference                                                              | Semantics description |
+|---------------|----------|-------|------------------------------------------------------------------------------------|-----------------------|
+| Location Type | M        |       | ENUMERATED (geographic location, assistance information, ..., last known location) |                       |
+
+### 7.4.4 E-CGI
+
+This parameter gives the current cell location of the target UE or the last known cell location for the case when the Location Type IE is set to last known location. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell.
+
+Table 7.4.4-1: ECGI
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                                                |
+|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------|
+| PLMN Identity | M        |       | 7.4.27                |                                                                                      |
+| Cell Identity | M        |       | BIT STRING (28)       | The leftmost bits of the Cell Identity correspond to the eNB ID (defined in 7.4.19). |
+
+### 7.4.5 LCS Client Type
+
+This parameter defines the type of the originating LCS Client. It shall be included if the Location Type indicates a request for a location estimate and may be included in other cases to assist an SMLC to appropriately prioritize a location request.
+
+Table 7.4.5-1: LCS Client Type
+
+| IE/Group Name | Presence | Range | IE type and reference                                                                                                                                                                                                                                   | Semantics description                  |
+|---------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|
+| Client Type   | M        |       | ENUMERATED (Emergency Services, Value Added Services, PLMN Operator Services, Lawful Intercept Services, PLMN Operator - broadcast services, PLMN Operator - O&M, PLMN Operator - anonymous statistics, PLMN Operator - Target MS service support, ...) | Identifies the category of LCS client. |
+
+### 7.4.6 LCS Priority
+
+This parameter defines the priority of the location request.
+
+Table 7.4.6-1: LCS Priority
+
+| IE/Group Name | Presence | Range | IE type and reference  | Semantics description                                                                                                    |
+|---------------|----------|-------|------------------------|--------------------------------------------------------------------------------------------------------------------------|
+| LCS Priority  | M        |       | OCTET STRING (SIZE(1)) | 0= highest priority<br>1= normal priority<br>all other values treated as 1<br>For details, refer to 3GPP TS 22.071 [10]. |
+
+### 7.4.7 LCS QoS
+
+This parameter provides the required Quality of Service for the LCS Request. Quality of Service may include horizontal accuracy, vertical accuracy and allowed response time.
+
+Table 7.4.7-1: LCS QoS
+
+| IE/Group Name       | Presence | Range | IE type and reference                                                                       | Semantics description                                                                                                                                                                                                                                                                                                                            |
+|---------------------|----------|-------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Horizontal Accuracy | O        |       | INTEGER(0..127)                                                                             | bit 8 = 0<br>bits 7-1 = 7 bit Uncertainty Code defined in 3GPP TS 23.032 [6].<br>The horizontal location error should be less than the error indicated by the uncertainty code with 67% confidence.                                                                                                                                              |
+| Vertical Requested  | O        |       | ENUMERATED(Vertical Coordinate Is Not Requested (0), Vertical Coordinate Is Requested (1) ) | Default value if this IE is not present is: Vertical Coordinate Is Not Requested (0).                                                                                                                                                                                                                                                            |
+| Vertical Accuracy   | O        |       | INTEGER(0..127)                                                                             | bit 8 = 0<br>bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3GPP TS 23.032 [6].<br>The vertical location error should be less than the error indicated by the uncertainty code with 67% confidence.<br>If the vertical requested IE is not present or present with a value of 0, then this vertical accuracy will be ignored, if present. |
+| Response Time       | O        |       | ENUMERATED(Low Delay(0), Delay Tolerant (1), ...)                                           | For details, refer to 3GPP TS 22.071 [10].                                                                                                                                                                                                                                                                                                       |
+
+### 7.4.8 UE Positioning Capability
+
+This parameter provides information about the LCS capabilities of the target UE.
+
+Table 7.4.8-1: UE Positioning Capability
+
+| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description                                           | Criticality | Assigned Criticality |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------|-------------|----------------------|
+| LPP Support   | M        |       | BOOLEAN               | Defines if the UE supports LPP or not.<br>TRUE means supported. | –           |                      |
+
+### 7.4.9 Include Velocity
+
+This parameter indicates if the Velocity of the target UE is requested in the Location Response.
+
+Table 7.4.9-1: Include Velocity
+
+| IE/Group Name      | Presence | Range | IE type and reference                     | Semantics description                   |
+|--------------------|----------|-------|-------------------------------------------|-----------------------------------------|
+| Velocity Indicator | O        |       | ENUMERATED(requested, not requested, ...) | Specify if Velocity of UE is requested. |
+
+### 7.4.10 IMSI
+
+This parameter identifies the IMSI of the target UE.
+
+Table 7.4.10-1: IMSI
+
+| IE/Group Name | Presence | Range | IE type and reference      | Semantics description                                                                                                                                     |
+|---------------|----------|-------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMSI          | M        |       | OCTET STRING (SIZE (3..8)) | The number of decimal digits shall be from 6 to 15 starting with the digits from the PLMN identity. It is encoded with TBCD String, two digits per octet. |
+
+### 7.4.11 IMEI
+
+This parameter identifies the IMEI of the target UE.
+
+Table 7.4.11-1: IMEI
+
+| IE/Group Name | Presence | Range | IE type and reference   | Semantics description                                                                                                                                                                                                                                                                                                                                              |
+|---------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMEI          | M        |       | OCTET STRING (SIZE (8)) | <p>Refers to International Mobile Station Equipment Identity and Software Version Number (SVN) defined in TS 3GPP TS 23.003 [11].</p> <p>This IE is 16 digits encoded with TBCD String, two digits per octet.</p> <p>If the SVN is not present the last octet shall contain the digit 0 as filler.<br/>If present the SVN shall be included in the last octet.</p> |
+
+### 7.4.12 Geographic Area
+
+This parameter provides a location estimate for the target UE in the case of a successful location attempt.
+
+**Table 7.4.12-1: Geographic Area**
+
+| IE/Group Name                                            | Presence | Range              | IE type and reference            | Semantics description                                                                                                                                                                                    |
+|----------------------------------------------------------|----------|--------------------|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Geographical Area</i>                          |          |                    |                                  |                                                                                                                                                                                                          |
+| >Point                                                   |          |                    |                                  | Ellipsoid point                                                                                                                                                                                          |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >Point With Uncertainty                                  |          |                    |                                  | Ellipsoid point with uncertainty circle                                                                                                                                                                  |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >>Uncertainty Code                                       | M        |                    | INTEGER ( 0..127)                | The uncertainty "r" expressed in meters is derived from the "Uncertainty Code" k by $r = 10 \times (1.1^k - 1)$                                                                                          |
+| >Ellipsoid point with uncertainty Ellipse                |          |                    |                                  |                                                                                                                                                                                                          |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >>Uncertainty Ellipse                                    | M        |                    | 7.4.24                           |                                                                                                                                                                                                          |
+| >>Confidence                                             | M        |                    | INTEGER ( 0..100)                | In percentage                                                                                                                                                                                            |
+| >Polygon                                                 |          |                    |                                  | List of Ellipsoid points                                                                                                                                                                                 |
+| >>Polygon Point                                          |          | 1..<maxnoofPoints> |                                  | The minimum number of points allowed is 3.                                                                                                                                                               |
+| >>>Geographical Coordinates                              | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >Ellipsoid point with altitude                           |          |                    |                                  |                                                                                                                                                                                                          |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >>Altitude and direction                                 | M        |                    | 7.4.22                           |                                                                                                                                                                                                          |
+| >Ellipsoid point with altitude and uncertainty Ellipsoid |          |                    |                                  |                                                                                                                                                                                                          |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >>Altitude and direction                                 | M        |                    | 7.4.22                           |                                                                                                                                                                                                          |
+| >>Uncertainty Ellipse                                    | M        |                    | 7.4.24                           |                                                                                                                                                                                                          |
+| >>Uncertainty Altitude                                   | M        |                    | INTEGER ( 0..127)                | The uncertainty altitude "h" expressed in metres is derived from the "Uncertainty Altitude" k, by: $h = 45 \times (1.025^k - 1)$                                                                         |
+| >>Confidence                                             | M        |                    | INTEGER ( 0..100)                | In percentage                                                                                                                                                                                            |
+| >Ellipsoid Arc                                           |          |                    |                                  |                                                                                                                                                                                                          |
+| >>Geographical Coordinates                               | M        |                    | 7.4.23                           |                                                                                                                                                                                                          |
+| >>Inner radius                                           | M        |                    | INTEGER ( 0..2 <sup>16</sup> -1) | The relation between the value (N) and the radius (r) in meters it describes is $5N \leq r < 5(N+1)$ , except for $N = 2^{16} - 1$ for which the range is extended to include all greater values of (r). |
+
+| IE/Group Name                                                                   | Presence | Range | IE type and reference | Semantics description                                                                                                                                    |
+|---------------------------------------------------------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >>Uncertainty radius                                                            | M        |       | INTEGER ( 0..127)     | The uncertainty "r" is derived from the "Uncertainty radius" k by $r = 10 \times (1.1^k - 1)$                                                            |
+| >>Offset angle                                                                  | M        |       | INTEGER ( 0..179)     | The relation between the value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$                                                     |
+| >>Included angle                                                                | M        |       | INTEGER ( 0..179)     | The relation between the value (N) and the angle (a) in degrees it describes is $2N < a \leq 2(N+1)$                                                     |
+| >>Confidence                                                                    | M        |       | INTEGER ( 0..100)     |                                                                                                                                                          |
+| >High Accuracy Ellipsoid point with uncertainty Ellipse                         |          |       |                       |                                                                                                                                                          |
+| >>High Accuracy Geographical Coordinates                                        | M        |       | 7.4.41                |                                                                                                                                                          |
+| >>High Accuracy Uncertainty Ellipse                                             | M        |       | 7.4.42                |                                                                                                                                                          |
+| >>Confidence                                                                    | M        |       | INTEGER ( 0..100)     | In percentage                                                                                                                                            |
+| >High Accuracy Ellipsoid point with Scalable uncertainty Ellipse                |          |       |                       |                                                                                                                                                          |
+| >>High Accuracy Geographical Coordinates                                        | M        |       | 7.4.41                |                                                                                                                                                          |
+| >>High Accuracy Scalable Uncertainty Ellipse                                    | M        |       | 7.4.45                |                                                                                                                                                          |
+| >>Confidence                                                                    | M        |       | INTEGER ( 0..100)     | In percentage                                                                                                                                            |
+| >High Accuracy Ellipsoid point with altitude and uncertainty Ellipsoid          |          |       |                       |                                                                                                                                                          |
+| >>High Accuracy Geographical Coordinates                                        | M        |       | 7.4.41                |                                                                                                                                                          |
+| >>High Accuracy Altitude                                                        | M        |       | 7.4.43                |                                                                                                                                                          |
+| >>High Accuracy Uncertainty Ellipse                                             | M        |       | 7.4.42                |                                                                                                                                                          |
+| >>Confidence                                                                    | M        |       | INTEGER ( 0..100)     | In percentage                                                                                                                                            |
+| >>High Accuracy Uncertainty Altitude                                            | M        |       | INTEGER ( 0..255)     | The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by: $h = 0.3 \times (1.02^k - 1)$ |
+| >>Vertical Confidence                                                           | M        |       | INTEGER ( 0..100)     | In percentage                                                                                                                                            |
+| >High Accuracy Ellipsoid point with altitude and scalable uncertainty Ellipsoid |          |       |                       |                                                                                                                                                          |
+| >>High Accuracy Geographical Coordinates                                        | M        |       | 7.4.41                |                                                                                                                                                          |
+| >>High Accuracy Altitude                                                        | M        |       | 7.4.43                |                                                                                                                                                          |
+| >>High Accuracy Scalable Uncertainty Ellipse                                    | M        |       | 7.4.45                |                                                                                                                                                          |
+| >>Confidence                                                                    | M        |       | INTEGER ( 0..100)     | In percentage                                                                                                                                            |
+| >>High Accuracy Scalable Uncertainty Altitude                                   | M        |       | 7.4.46                |                                                                                                                                                          |
+
+| IE/Group Name         | Presence | Range | IE type and reference | Semantics description |
+|-----------------------|----------|-------|-----------------------|-----------------------|
+| >>Vertical Confidence | M        |       | INTEGER ( 0..100)     | In percentage         |
+
+**Table 7.4.12-2: Range bound**
+
+| Range bound   | Explanation                                    |
+|---------------|------------------------------------------------|
+| maxnoofPoints | Maximum no. of points in polygon. Value is 15. |
+
+### 7.4.13 Positioning Data
+
+This parameter provides additional information for the positioning attempt from the E-SMLC.
+
+**Table 7.4.13-1: Positioning Data**
+
+| IE/Group Name                  | Presence | Range       | IE type and reference | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------------|----------|-------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Position Data</b>           | M        |             |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| >Positioning Data Set          | O        |             |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| >>Positioning Method and Usage |          | 1..<maxSet> | OCTET STRING (1)      | <p>Coding of positioning method (bits 8-4):<br/> 00000 Cell ID<br/> 00001 Reserved<br/> 00010 E-CID<br/> 00011 Reserved<br/> 00100 OTDOA<br/> 00101 Reserved<br/> 00110 Reserved<br/> 00111 Reserved<br/> 01000 U-TDOA<br/> 01001 Reserved<br/> 01010 Reserved<br/> 01011 Reserved<br/> 01100 to 01111 reserved for other location technologies<br/> 10000 to 11111 reserved for network specific positioning methods</p> <p>Coding of usage (bits 3-1):<br/> 000 Attempted unsuccessfully due to failure or interruption - not used.<br/> 001 Attempted successfully: results not used to generate location - not used.<br/> 010 Attempted successfully: results used to verify but not generate location - not used.<br/> 011 Attempted successfully: results used to generate location.<br/> 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.</p> |
+| >GNSS Positioning Data Set     | O        |             |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+
+|                                           |   |                         |                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|-------------------------------------------|---|-------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >>GNSS<br>Positioning Method<br>and Usage | O | 1..<ma<br>xGNS<br>SSet> | OCTET<br>STRING (1) | <p>Coding of Method (Bits 8-7) :</p> <p>00 : UE-Based<br/>01 : UE-Assisted<br/>10 : Conventional<br/>11 : Reserved</p> <p>Coding of GNSS ID (Bits 6-4) :</p> <p>000 : GPS<br/>001 : Galileo<br/>010 : SBAS<br/>011 : Modernized GPS<br/>100 : QZSS<br/>101 : GLONASS<br/>110 : BDS<br/>111 : NavIC</p> <p>Coding of usage (bits 3-1):</p> <p>000 Attempted unsuccessfully due to failure or interruption<br/>001 Attempted successfully: results not used to generate location<br/>010 Attempted successfully: results used to verify but not generate location<br/>011 Attempted successfully: results used to generate location<br/>100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.</p> |
+| >Additional<br>Positioning Data<br>Set    | O |                         |                     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+|                                           |  |                     |                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-------------------------------------------|--|---------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >>Additional Positioning Method and Usage |  | 1 to <maxAddPosSet> | OCTET STRING (SIZE(1)) | <p>Coding of positioning method (bits 8-7):<br/> 00 UE-Based;<br/> 01 UE-Assisted;<br/> 10 Standalone;<br/> 11 Reserved.</p> <p>Coding of Additional Positioning ID (bits 6-4):<br/> 000 Barometric Pressure;<br/> 001 WLAN;<br/> 010 Bluetooth;<br/> 011 MBS;<br/> 100 Motion-Sensor(s);<br/> other values reserved.</p> <p>Coding of usage (bits 3-1):</p> <p>000 Attempted unsuccessfully due to failure or interruption<br/> 001 Attempted successfully: results not used to generate location<br/> 010 Attempted successfully: results used to verify but not generate location<br/> 011 Attempted successfully: results used to generate location<br/> 100 Attempted successfully: case where UE supports multiple mobile based positioning methods and the actual method or methods used by the UE cannot be determined.</p> |
+|-------------------------------------------|--|---------------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+Table 7.4.13-2: Range bound
+
+| Range bound  | Explanation                               |
+|--------------|-------------------------------------------|
+| maxSet       | Maximum size of the data set. Value is 9. |
+| maxGNSSSet   | Maximum size of the data. Value is 9.     |
+| maxAddPosSet | Maximum size of the data Value is 8.      |
+
+### 7.4.14 Velocity Estimate
+
+This parameter provides the velocity estimate for the target UE.
+
+**Table 7.4.14-1: Velocity Estimate**
+
+| IE/Group Name                                      | Presence | Range | IE type and reference | Semantics description                                                                                                                                                                                                                   |
+|----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Choice <i>Velocity Estimate</i>                    |          |       |                       |                                                                                                                                                                                                                                         |
+| >Horizontal Velocity                               |          |       |                       | Horizontal speed and bearing (the direction of travel).                                                                                                                                                                                 |
+| >>Horizontal Speed and Bearing                     | M        |       | 7.4.25                |                                                                                                                                                                                                                                         |
+| >Horizontal with Vertical Velocity                 |          |       |                       | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward)                                                                                                                 |
+| >>Horizontal Speed and Bearing                     | M        |       | 7.4.25                |                                                                                                                                                                                                                                         |
+| >>Vertical Velocity                                | M        |       | 7.4.26                |                                                                                                                                                                                                                                         |
+| >Horizontal Velocity with Uncertainty              |          |       |                       | Horizontal speed, bearing (the direction of travel), and the uncertainty of the reported speed.                                                                                                                                         |
+| >>Horizontal Speed and Bearing                     | M        |       | 7.4.25                |                                                                                                                                                                                                                                         |
+| >>Uncertainty Speed                                | M        |       | INTEGER (0..255)      | Uncertainty speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified            |
+| >Horizontal with Vertical Velocity and Uncertainty |          |       |                       | Horizontal speed and bearing (the direction of travel) as well as vertical speed and the direction (upward or downward) and the uncertainty of the reported speed.                                                                      |
+| >>Horizontal Speed and Bearing                     | M        |       | 7.4.25                |                                                                                                                                                                                                                                         |
+| >>Vertical Velocity                                | M        |       | 7.4.26                |                                                                                                                                                                                                                                         |
+| >>Horizontal Uncertainty Speed                     | M        |       | INTEGER (0..255)      | Horizontal Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified |
+| >>Vertical Uncertainty Speed                       | M        |       | INTEGER (0..255)      | Vertical Uncertainty Speed is encoded in increments of 1 kilometer per hour using an 8 bit binary coded number (N). The value of N gives the uncertainty speed except for N=255 which indicates that the uncertainty is not specified   |
+
+### 7.4.15 Accuracy Fulfilment Indicator
+
+This parameter whether the returned position estimate satisfies the requested accuracy or not.
+
+Table 7.4.15-1: Accuracy Fulfilment Indicator
+
+| IE/Group Name                 | Presence | Range | IE type and reference                                                                     | Semantics description                                    |
+|-------------------------------|----------|-------|-------------------------------------------------------------------------------------------|----------------------------------------------------------|
+| Accuracy Fulfilment Indicator | O        |       | ENUMERATED<br>(requested accuracy fulfilled,<br>requested accuracy not fulfilled,<br>...) | Indicates if the requested accuracy is fulfilled or not. |
+
+### 7.4.16 LCS Cause
+
+The LCS Cause is included if and only if a requested location estimate was not successfully obtained (e.g. location estimate not available), requested LCS assistance data was not successfully transferred to the UE or location-related data has been lost. The parameter provides the reason for the failure.
+
+Table 7.4.16-1: LCS Cause
+
+| IE/Group Name               | Presence | Range | IE Type and Reference                                                                                                                                                                                                                                                             | Semantics Description |
+|-----------------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| CHOICE Cause Group          |          |       |                                                                                                                                                                                                                                                                                   |                       |
+| >Radio Network Layer        |          |       |                                                                                                                                                                                                                                                                                   |                       |
+| >>Radio Network Layer Cause | M        |       | ENUMERATED<br>(<br>Unspecified<br>...)                                                                                                                                                                                                                                            |                       |
+| >Transport Layer            |          |       |                                                                                                                                                                                                                                                                                   |                       |
+| >>Transport Layer Cause     | M        |       | ENUMERATED<br>(Transport Resource Unavailable,<br>Unspecified,<br>...)                                                                                                                                                                                                            |                       |
+| >Protocol                   |          |       |                                                                                                                                                                                                                                                                                   |                       |
+| >>Protocol Cause            | M        |       | ENUMERATED<br>(Transfer Syntax Error,<br>Abstract Syntax Error (Reject),<br>Abstract Syntax Error (Ignore and<br>Notify),<br>Message not Compatible with<br>Receiver State,<br>Semantic Error,<br>Unspecified,<br>Abstract Syntax Error (Falsely<br>Constructed Message),<br>...) |                       |
+| >Misc                       |          |       |                                                                                                                                                                                                                                                                                   |                       |
+| >>Misc Cause                | M        |       | ENUMERATED<br>(Processing Overload,<br>Hardware Failure,<br>O&M Intervention,<br>Unspecified,<br>...,<br>Ciphering Key Data Lost)                                                                                                                                                 |                       |
+
+### 7.4.17 Payload Type
+
+This parameter indicates the type of APDU included in LCS-AP Connected Oriented Information message. The supported information types are LPP and LPPa.
+
+**Table 7.4.17-1: Payload Type**
+
+| IE/Group Name | Presence | Range | IE type and reference                | Semantics description |
+|---------------|----------|-------|--------------------------------------|-----------------------|
+| Payload Type  | M        |       | ENUMERATED<br>(LPP,<br>LPPa,<br>...) |                       |
+
+### 7.4.18 APDU
+
+This parameter contains an embedded APDU. For information transfer between an E-SMLC and an eNB this shall be an LPPa APDU. For information transfer between an E-SMLC and a target UE, this shall be an LPP APDU.
+
+**Table 7.4.18-1: APDU**
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                                                            |
+|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------|
+| APDU          | M        |       | OCTET STRING          | This IE contains a message whose content and encoding are defined according to the Payload Type. |
+
+### 7.4.19 Network Element
+
+This parameter identifies the source or destination of the message. The network element is identified by association with either an eNB ID or the identity of an E-SMLC.
+
+**Table 7.4.19-1: Network Element**
+
+| IE/Group Name                 | Presence | Range | IE type and reference | Semantics description                                                                                              |
+|-------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>Network Element</i> | M        |       |                       |                                                                                                                    |
+| >Global eNB ID                |          |       |                       | The global identity of the eNB                                                                                     |
+| >>PLMN Identity               |          |       | 7.4.27                |                                                                                                                    |
+| >>eNB ID                      |          |       | 7.4.29                |                                                                                                                    |
+| >E-SMLC Identity              |          |       | INTEGER (0..255)      | The identity of the E-SMLC (an index to identify a specific E-SMLC among all the available E-SMLCs in the network) |
+
+### 7.4.20 Return Error Request
+
+This parameter may be included to request an error response if LCS-AP message cannot be delivered successfully to its final destination. This parameter shall not be included if the Return Error cause is present.
+
+**Table 7.4.20-1: Return Error Type**
+
+| IE/Group Name     | Presence | Range | IE type and reference           | Semantics description |
+|-------------------|----------|-------|---------------------------------|-----------------------|
+| Return Error Type | M        |       | ENUMERATED (<br>Yes,<br>No<br>) |                       |
+
+### 7.4.21 Return Error Cause
+
+This parameter indicates an error response for a LCS-AP connectionless information message that could not be delivered to its final destination. The APDU should be present and the same as the APDU in the original undelivered
+
+message. The source and destination identities shall be included and the same as the destination and source identities, respectively, in the original undelivered message.
+
+**Table 7.4.21-1: Return Error Cause**
+
+| IE/Group Name      | Presence | Range | IE type and reference                                                                                               | Semantics description |
+|--------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------|-----------------------|
+| Return Error Cause | M        |       | ENUMERATED<br>(systemfailure,<br>protocolerror,<br>destinationunkown,<br>destinationunreachable,<br>congestion,...) |                       |
+
+### 7.4.22 Altitude and direction
+
+**Table 7.4.22-1: Altitude and direction**
+
+| IE/Group Name         | Presence | Range | IE type and reference               | Semantics description                                                                                                                                                                              |
+|-----------------------|----------|-------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Direction of Altitude | M        |       | ENUMERATED<br>(Height, Depth)       |                                                                                                                                                                                                    |
+| Altitude              | M        |       | INTEGER (<br>0..2 <sup>15</sup> -1) | The relation between the value (N) and the altitude (a) in meters it describes is $N \leq a < N+1$ , except for $N=2^{15}-1$ for which the range is extended to include all greater values of (a). |
+
+### 7.4.23 Geographical Coordinates
+
+This IE contains the geographical coordinates.
+
+**Table 7.4.23-1: Geographical Coordinates**
+
+| IE/Group Name        | Presence | Range | IE type and reference                               | Semantics description                                                                                                            |
+|----------------------|----------|-------|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|
+| Latitude Sign        | M        |       | ENUMERATED<br>(North, South)                        |                                                                                                                                  |
+| Degrees Of Latitude  | M        |       | INTEGER (<br>0..2 <sup>23</sup> -1)                 | The IE value (N) is derived by this formula: $N \leq 2^{23} \times X / 90 < N+1$ X being the latitude in degree (0°.. 90°)       |
+| Degrees Of Longitude | M        |       | INTEGER (<br>-2 <sup>23</sup> ..2 <sup>23</sup> -1) | The IE value (N) is derived by this formula: $N \leq 2^{24} \times X / 360 < N+1$ X being the longitude in degree (-180°..+180°) |
+
+### 7.4.24 Uncertainty Ellipse
+
+This IE contains the uncertainty ellipse of a geographical area.
+
+**Table 7.4.24-1: Uncertainty Ellipse**
+
+| IE/Group Name             | Presence | Range | IE type and reference | Semantics description                                                                                   |
+|---------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------|
+| Uncertainty semi-major    | M        |       | INTEGER (0..127)      | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$             |
+| Uncertainty semi-minor    | M        |       | INTEGER (0..127)      | The uncertainty "r" is derived from the "uncertainty code" k by $r = 10 \times (1.1^k - 1)$             |
+| Orientation of major axis | M        |       | INTEGER (0..89)       | The relation between the IE value (N) and the angle (a) in degrees it describes is $2N \leq a < 2(N+1)$ |
+
+### 7.4.25 Horizontal Speed and Bearing
+
+This IE contains the two components of horizontal velocity: speed and bearing
+
+**Table 7.4.25-1: Horizontal Speed and Bearing**
+
+| IE/Group Name    | Presence | Range | IE type and reference           | Semantics description                                                                                                                                                                                                         |
+|------------------|----------|-------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Bearing          | M        |       | INTEGER (0..359)                | The direction of movement is given in degrees where '0' represents North, '90' represents East, etc.                                                                                                                          |
+| Horizontal Speed | M        |       | INTEGER (0..2 <sup>11</sup> -1) | The relationship between (N) and the horizontal speed (h) in kilometers per hour it describes is:<br>$N \leq h < N + 0.5$ (N=0)<br>$N - 0.5 \leq h < N + 0.5$ (0 < N < 2 <sup>11</sup> -1)<br>$N - 0.5 \leq h (N = 2^{11}-1)$ |
+
+### 7.4.26 Vertical Velocity
+
+This IE contains the two components of vertical velocity: speed and direction
+
+**Table 7.4.26-1: Vertical Velocity**
+
+| IE/Group Name            | Presence | Range | IE type and reference          | Semantics description                                                                                                                                                                                                     |
+|--------------------------|----------|-------|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Vertical Speed           | M        |       | INTEGER (0..2 <sup>8</sup> -1) | The relationship between (N) and the vertical speed (v) in kilometers per hour it describes is:<br>$N \leq v < N + 0.5$ (N = 0)<br>$N - 0.5 \leq v < N + 0.5$ (0 < N < 2 <sup>8</sup> -1)<br>$N - 0.5 \leq v (N = 2^8-1)$ |
+| Vertical Speed Direction |          |       | ENUMERATED (upward, downward)  |                                                                                                                                                                                                                           |
+
+### 7.4.27 PLMN Identity
+
+This information element indicates the PLMN Identity.
+
+**Table 7.4.27-1: PLMN Identity**
+
+| IE/Group Name | Presence | Range | IE type and reference   | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------|----------|-------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN identity | M        |       | OCTET STRING (SIZE (3)) | <ul style="list-style-type: none"> <li>- digits 0 to 9, encoded 0000 to 1001,</li> <li>- 1111 used as filler digit, two digits per octet,</li> <li>- bits 4 to 1 of octet n encoding digit 2n-1</li> <li>- bits 8 to 5 of octet n encoding digit 2n</li> </ul> <p>-The Selected PLMN identity consists of 3 digits from MCC followed by either</p> <ul style="list-style-type: none"> <li>-a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or</li> <li>-3 digits from MNC (in case of a 3 digit MNC).</li> </ul> |
+
+### 7.4.28 Correlation ID
+
+This IE indicates a specific location session. It is used in order to correlate request/response and an ongoing location session.
+
+**Table 7.4.28-1: Correlation ID**
+
+| IE/Group Name  | Presence | Range | IE type and reference   | Semantics description                                                                                                                   |
+|----------------|----------|-------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Correlation ID | M        |       | OCTET STRING (SIZE (4)) | The identifier of a location session in E-UTRAN. It should be unique for all concurrently active location sessions in a particular MME. |
+
+### 7.4.29 eNB ID
+
+This information element is used to identify an eNB.
+
+**Table 7.4.29-1: eNB ID**
+
+| IE/Group Name       | Presence | Range | IE type and reference | Semantics description                                                                                                                                 |
+|---------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE eNB ID       |          |       |                       |                                                                                                                                                       |
+| >Macro eNB ID       |          |       | BIT STRING (20)       | Equal to the 20 leftmost bits of the <i>Cell Identity</i> IE contained in the <i>E-UTRAN CGI</i> IE (see clause 7.4.4) of each cell served by the eNB |
+| >Home eNB ID        |          |       | BIT STRING (28)       | Equal to the <i>Cell Identity</i> IE contained in the <i>E-UTRAN CGI</i> IE (see clause 7.4.4) of the cell served by the eNB                          |
+| >Short Macro eNB ID |          |       | BIT STRING (18)       | Equal to the 18 leftmost bits of the <i>Cell Identity</i> IE contained in the <i>E-UTRAN CGI</i> IE (see clause 7.4.4) of each cell served by the eNB |
+| >Long Macro eNB ID  |          |       | BIT STRING (21)       | Equal to the 21 leftmost bits of the <i>Cell Identity</i> IE contained in the <i>E-UTRAN CGI</i> IE (see clause 7.4.4) of each cell served by the eNB |
+
+### 7.4.30 LCS Service Type ID
+
+This parameter defines the service type ID for the location request.
+
+**Table 7.4.30-1: LCS Service Type ID**
+
+| IE/Group Name       | Presence | Range | IE type and reference | Semantics description                                                                                                   |
+|---------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------|
+| LCS Service Type ID | O        |       | INTEGER(0..127)       | Identifies the type of service requested. The meaning of the different service types is defined in 3GPP TS 22.071 [10]. |
+
+### 7.4.31 Cell Portion ID
+
+This parameter gives the current Cell Portion location of the target UE. The Cell Portion ID is the unique identifier for a cell portion within a cell.
+
+**Table 7.4.31-1: Cell Portion**
+
+| IE/Group Name   | Presence | Range | IE type and reference         | Semantics description |
+|-----------------|----------|-------|-------------------------------|-----------------------|
+| Cell Portion ID | M        |       | INTEGER(0..255,...,256..4095) |                       |
+
+### 7.4.32 Civic Address
+
+This information element contains a location estimate for the target UE expressed as a Civic address.
+
+Table 7.4.32-1: Civic Address
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                                                                                                                                                                                                                                                                                   |
+|---------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Civic Address | O        |       | OCTET STRING          | This IE contains a UTF-8 encoded PIDF-LO XML document as defined in IETF RFC 4119 [13]. The document shall only contain a civic address using the namespaces "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" per IETF RFC 5139 [14] and "urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr:ext" per IETF RFC 6848 [15]. |
+
+### 7.4.33 Barometric Pressure
+
+This information element contains the barometric pressure measurement as reported by the target UE.
+
+Table 7.4.33-1: Barometric Pressure
+
+| IE/Group Name       | Presence | Range | IE type and reference   | Semantics description                                                                      |
+|---------------------|----------|-------|-------------------------|--------------------------------------------------------------------------------------------|
+| Barometric Pressure | O        |       | INTEGER (30000..115000) | This IE specifies the measured uncompensated atmospheric pressure in units of Pascal (Pa). |
+
+### 7.4.34 RAT Type
+
+This parameter provides the serving RAT type for the target UE or the last known serving RAT type for the case when the Location Type IE is set to last known location.
+
+Table 7.4.34-1: RAT Type
+
+| IE/Group Name | Presence | Range | IE type and reference                   | Semantics description                  |
+|---------------|----------|-------|-----------------------------------------|----------------------------------------|
+| RAT Type      | O        |       | ENUMERATED (lte-wb, nb-iot, lte-m, ...) | This IE provides the serving RAT type. |
+
+### 7.4.35 Coverage Level
+
+This parameter defines the type of coverage level being requested.
+
+Table 7.4.35-1: Coverage Level
+
+| IE/Group Name  | Presence | Range | IE type and reference               | Semantics description |
+|----------------|----------|-------|-------------------------------------|-----------------------|
+| Coverage Level | O        |       | ENUMERATED (Extended Coverage, ...) |                       |
+
+### 7.4.36 Ciphering Data
+
+This parameter contains the ciphering data sets sent by the E-SMLC to the MME.
+
+Table 7.4.36-1: Ciphering Data
+
+| IE/Group Name         | Presence | Range              | IE type and reference | Semantics description |
+|-----------------------|----------|--------------------|-----------------------|-----------------------|
+| <b>Ciphering Data</b> | M        |                    |                       |                       |
+| >Ciphering Data Set   | M        | 1..<maxCiphetrSet> | 7.4.39                |                       |
+
+Table 7.4.36-2: Range bound
+
+| Range bound  | Explanation                               |
+|--------------|-------------------------------------------|
+| maxCipherSet | Maximum size of the data set. Value is 16 |
+
+### 7.4.37 Ciphering Data Ack
+
+This parameter contains the ciphering data acknowledgement information sent by the MME to the E-SMLC.
+
+Table 7.4.37-1: Ciphering Data Ack
+
+| IE/Group Name      | Presence | Range             | IE type and reference | Semantics description                                                                          |
+|--------------------|----------|-------------------|-----------------------|------------------------------------------------------------------------------------------------|
+| Ciphering Data Ack | M        |                   |                       | This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement |
+| >Ciphering Set ID  | M        | 1..<maxCipherSet> | INTEGER (0..65535)    |                                                                                                |
+
+Table 7.4.37-2: Range bound
+
+| Range bound  | Explanation                               |
+|--------------|-------------------------------------------|
+| maxCipherSet | Maximum size of the data set. Value is 16 |
+
+### 7.4.38 Ciphering Data Error Report
+
+This parameter contains a list of ciphering data sets with the associated outcome of storage attempt at the MME.
+
+Table 7.4.38-1: Ciphering Data Error Report
+
+| IE/Group Name                         | Presence | Range             | IE type and reference | Semantics description |
+|---------------------------------------|----------|-------------------|-----------------------|-----------------------|
+| Ciphering Data Error Report           | M        |                   |                       |                       |
+| >Ciphering Data Error Report Contents | M        | 1..<maxCipherSet> | 7.4.40                |                       |
+
+Table 7.4.38-2: Range bound
+
+| Range bound  | Explanation                               |
+|--------------|-------------------------------------------|
+| maxCipherSet | Maximum size of the data set. Value is 16 |
+
+### 7.4.39 Ciphering Data Set
+
+This parameter contains a ciphering data set sent by the E-SMLC to the MME.
+
+**Table 7.4.39-1: Ciphering Data Set**
+
+| IE/Group Name             | Presence | Range | IE type and reference            | Semantics description |
+|---------------------------|----------|-------|----------------------------------|-----------------------|
+| <b>Ciphering Data Set</b> | M        |       |                                  |                       |
+| >Ciphering Set ID         | M        |       | INTEGER<br>(0..65535)            |                       |
+| >Ciphering Key            | M        |       | OCTET<br>STRING<br>(SIZE(16))    |                       |
+| >c0                       | M        |       | BIT STRING<br>(SIZE<br>(1..128)) |                       |
+
+|            |   |  |                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|------------|---|--|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >SIB Types | M |  | OCTET STRING (SIZE(4)) | <p>This IE contains a bitmap indicating the positioning SIB types for which the ciphering data set is applicable:</p> <ul style="list-style-type: none"> <li>-- a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type</li> <li>- a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type</li> </ul> <p>The mapping of the bits to the positioning SIB types is as follows:</p> <ul style="list-style-type: none"> <li>-- bit 8 in the first octet maps to positioning SIB Type 1-1</li> <li>-- bit 7 in the first octet maps to positioning SIB Type 1-2</li> <li>-- bit 6 in the first octet maps to positioning SIB Type 1-3</li> <li>-- bit 5 in the first octet maps to positioning SIB Type 1-4</li> <li>-- bit 4 in the first octet maps to positioning SIB Type 1-5</li> <li>-- bit 3 in the first octet maps to positioning SIB Type 1-6</li> <li>-- bit 2 in the first octet maps to positioning SIB Type 1-7</li> <li>-- bit 1 in the first octet maps to positioning SIB Type 2-1</li> </ul> <ul style="list-style-type: none"> <li>-- bit 8 in the second octet maps to positioning SIB Type 2-2</li> <li>-- bit 7 in the second octet maps to positioning SIB Type 2-3</li> <li>-- bit 6 in the second octet maps to positioning SIB Type 2-4</li> <li>-- bit 5 in the second octet maps to positioning SIB Type 2-5</li> <li>-- bit 4 in the second octet maps to positioning SIB Type 2-6</li> <li>-- bit 3 in the second octet maps to positioning SIB Type 2-7</li> <li>-- bit 2 in the second octet maps to positioning SIB Type 2-8</li> <li>-- bit 1 in the second octet maps to positioning SIB Type 2-9</li> </ul> <ul style="list-style-type: none"> <li>-- bit 8 in the third octet maps to positioning SIB Type 2-10</li> <li>-- bit 7 in the third octet maps to positioning SIB</li> </ul> |
+|------------|---|--|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                |   |  |                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|----------------|---|--|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >SIB Types Ext | O |  | OCTET<br>STRING<br>(SIZE(4)) | <p>This IE contains extension of the bitmap SIB Types indicating the positioning SIB types for which the ciphering data set is applicable:</p> <ul style="list-style-type: none"> <li>-- a bit set to 0 indicates that the ciphering data set is not applicable to the corresponding positioning SIB type</li> <li>-- a bit set to 1 indicates that the ciphering data set is applicable to the corresponding positioning SIB type</li> </ul> <p>The mapping of the bits to the positioning SIB types is as follows:</p> <ul style="list-style-type: none"> <li>-- bit 8 in the first octet maps to positioning SIB Type 1-8</li> <li>-- bit 7 in the first octet maps to positioning SIB Type 2-20</li> <li>-- bit 6 in the first octet maps to positioning SIB Type 2-21</li> <li>-- bit 5 in the first octet maps to positioning SIB Type 2-22</li> <li>-- bit 4 in the first octet maps to positioning SIB Type 2-23</li> <li>-- bit 3 in the first octet maps to positioning SIB Type 2-24</li> <li>-- bit 2 in the first octet maps to positioning SIB Type 2-25</li> </ul> <p>Any unassigned bits are spare and shall be coded as zero. In the absence of this IE, the ciphering data set is not applicable for any of the positioning SIB types mapped by this IE.</p> |
+|----------------|---|--|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+|                      |   |  |                             |                                                                                                                                                                                                                                                                                                             |
+|----------------------|---|--|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| >Validity Start time | M |  | OCTET STRING (SIZE(4))      | This IE contains the UTC time when the ciphering data set becomes valid, encoded in the same format as the first four octets of the 64-bit timestamp format as defined in clause 6 of IETF RFC 5905 [16].                                                                                                   |
+| >Validity Duration   | M |  | INTEGER (0..65535)          | In minutes                                                                                                                                                                                                                                                                                                  |
+| >TAIs List           | O |  | OCTET STRING (SIZE (7..97)) | This IE contains the TAIs of the tracking areas for which the ciphering data set is applicable. It is encoded as octets 2 to n of the Tracking area identity list IE specified in clause 9.9.3.33 of 3GPP TS 24.301 [17].<br><br>If this IE is omitted, the ciphering data set is valid in the entire PLMN. |
+
+### 7.4.40 Ciphering Data Error Report Contents
+
+This parameter contains a ciphering data set ID with the associated outcome of storage attempt at the MME.
+
+**Table 7.4.40-1: Ciphering Data Error Report Contents**
+
+| IE/Group Name                               | Presence | Range | IE type and reference             | Semantics description                                                                          |
+|---------------------------------------------|----------|-------|-----------------------------------|------------------------------------------------------------------------------------------------|
+| <b>Ciphering Data Error Report Contents</b> | M        |       |                                   |                                                                                                |
+| >Ciphering Set ID                           | M        |       | INTEGER (0..65535)                | This IE contains the list of ciphering set IDs for which the MME is sending an acknowledgement |
+| >Storage outcome                            | M        |       | ENUMERATED ( Successful, Failed ) |                                                                                                |
+
+### 7.4.41 High Accuracy Geographical Coordinates
+
+This IE contains the high accuracy geographical coordinates.
+
+**Table 7.4.41-1: High Accuracy Geographical Coordinates**
+
+| IE/Group Name                      | Presence | Range | IE type and reference           | Semantics description                                                                                                                       |
+|------------------------------------|----------|-------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| High Accuracy Degrees Of Latitude  | M        |       | INTEGER ( $-2^{31}..2^{31}-1$ ) | The IE value (N) is derived by this formula:<br>$N = 2^{31} \times X / 90$<br>X being the latitude in degree ( $-90^\circ..+90^\circ$ )     |
+| High Accuracy Degrees Of Longitude | M        |       | INTEGER ( $-2^{31}..2^{31}-1$ ) | The IE value (N) is derived by this formula:<br>$N = 2^{31} \times X / 180$<br>X being the longitude in degree ( $-180^\circ..+180^\circ$ ) |
+
+### 7.4.42 High Accuracy Uncertainty Ellipse
+
+This IE contains the high accuracy uncertainty ellipse of a geographical area, using the range (0..255) for high-accuracy uncertainty code "k", as specified in 3GPP TS 23.032 [6].
+
+**Table 7.4.42-1: High Accuracy Uncertainty Ellipse**
+
+| IE/Group Name                        | Presence | Range | IE type and reference | Semantics description                                                                                                         |
+|--------------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| High Accuracy Uncertainty semi-major | M        |       | INTEGER (0..255)      | The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by:<br>$r = 0.3 \times (1.02^k - 1)$ |
+| High Accuracy Uncertainty semi-minor | M        |       | INTEGER (0..255)      | The high accuracy uncertainty "r" is derived from the high accuracy uncertainty code "k" by:<br>$r = 0.3 \times (1.02^k - 1)$ |
+| Orientation of major axis            | M        |       | INTEGER (0..179)      | Angle in degrees between the major axis and north                                                                             |
+
+### 7.4.43 High Accuracy Altitude
+
+**Table 7.4.43-1: High Accuracy Altitude**
+
+| IE/Group Name          | Presence | Range | IE type and reference         | Semantics description                                                                                                                            |
+|------------------------|----------|-------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| High Accuracy Altitude | M        |       | INTEGER ( $-64000..1280000$ ) | The relation between the IE value (N) and the altitude a (in metres) it encodes is described by the following equation:<br>$a = N \times 2^{-7}$ |
+
+### 7.4.44 High Accuracy Extended Uncertainty Ellipse
+
+This IE contains the high accuracy extended uncertainty ellipse of a geographical area, using the range (0..255) for High Accuracy Extended Uncertainty code "k", as specified in 3GPP TS 23.032 [6].
+
+**Table 7.4.44-1: High Accuracy Extended Uncertainty Ellipse**
+
+| IE/Group Name                                 | Presence | Range | IE type and reference | Semantics description                                                                                                                          |
+|-----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| High Accuracy Extended Uncertainty semi-major | M        |       | INTEGER (0..255)      | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6] |
+| High Accuracy Extended Uncertainty semi-minor | M        |       | INTEGER (0..255)      | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6] |
+| Orientation of major axis                     | M        |       | INTEGER (0..179)      | Angle in degrees between the major axis and north                                                                                              |
+
+### 7.4.45 High Accuracy Scalable Uncertainty Ellipse
+
+**Table 7.4.45-1: High Accuracy Scalable Uncertainty Ellipse**
+
+| IE/Group Name                                            | Presence | Range | IE type and reference | Semantics description |
+|----------------------------------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE <i>High Accuracy Scalable Uncertainty Ellipse</i> |          |       |                       |                       |
+| >High Accuracy Uncertainty Ellipse                       |          |       | 7.4.42                |                       |
+| >High Accuracy Extended Uncertainty Ellipse              |          |       | 7.4.44                |                       |
+
+### 7.4.46 High Accuracy Scalable Uncertainty Altitude
+
+**Table 7.4.46-1: High Accuracy Scalable Uncertainty Altitude**
+
+| IE/Group Name                                             | Presence | Range | IE type and reference | Semantics description                                                                                                                                     |
+|-----------------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| CHOICE <i>High Accuracy Scalable Uncertainty Altitude</i> |          |       |                       |                                                                                                                                                           |
+| >High Accuracy Uncertainty Altitude                       |          |       | INTEGER (0..255)      | The high accuracy uncertainty altitude "h" expressed in metres is derived from the high accuracy uncertainty code "k", by:<br>$h=0.3 \times (1.02^k - 1)$ |
+| >High Accuracy Extended Uncertainty Altitude              |          |       | INTEGER (0..255)      | The high accuracy extended uncertainty "r" is derived from the high accuracy extended uncertainty code "k", as specified in 3GPP TS 23.032 [6]            |
+
+## 7.5 Message and information element abstract syntax
+
+### 7.5.1 General
+
+LCS-AP ASN.1 definition conforms to [8] and [9].
+
+The ASN.1 definition specifies the structure and content of LCS-AP messages. LCS-AP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a LCS-AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+If a LCS-AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax error in clause 10 of [7].
+
+### 7.5.2 Usage of protocol extension mechanism for non-standard use
+
+The protocol extension mechanism for non-standard use may be used:
+
+- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multi-vendor interoperability.
+- by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
+
+The extension mechanism shall not be used for basic functionality. Such functionality shall be standardised.
+
+### 7.5.3 Elementary procedure definitions
+
+```
+
+-- *****
+--
+-- Elementary Procedure definitions
+--
+-- *****
+
+LCS-AP-PDU-Descriptions {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Descriptions (0)}
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+
+IMPORTS
+  Criticality,
+  ProcedureCode
+FROM LCS-AP-CommonDataTypes
+
+```
+
+```
+
+Location-Request,
+Location-Response,
+Location-Abort-Request,
+Connection-Oriented-Information,
+Connectionless-Information,
+Reset-Request,
+Reset-Acknowledge,
+Ciphering-Key-Data,
+Ciphering-Key-Data-Result
+FROM LCS-AP-PDU-Contents
+
+id-Location-Service-Request,
+id-Connection-Oriented-Information-Transfer,
+id-Connectionless-Information-Transfer,
+id-Location-Abort,
+id-Reset,
+id-Ciphering-Key-Data-Delivery
+FROM LCS-AP-Constants;
+
+-- *****
+--
+-- Interface Elementary Procedure Class
+--
+-- *****
+
+LCS-AP-ELEMENTARY-PROCEDURE ::= CLASS {
+    &InitiatingMessage ,
+    &SuccessfulOutcome OPTIONAL,
+    &UnsuccessfulOutcome OPTIONAL,
+    &procedureCode ProcedureCode UNIQUE,
+    &criticality Criticality DEFAULT ignore
+}
+WITH SYNTAX {
+    INITIATING MESSAGE &InitiatingMessage
+    [SUCCESSFUL OUTCOME &SuccessfulOutcome]
+    [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
+    PROCEDURE CODE &procedureCode
+    [CRITICALITY &criticality]
+}
+
+-- *****
+--
+-- Interface PDU Definition
+--
+-- *****
+
+LCS-AP-PDU ::= CHOICE {
+    initiatingMessage InitiatingMessage,
+    successfulOutcome SuccessfulOutcome,
+    unsuccessfulOutcome UnsuccessfulOutcome,
+    ...
+}
+
+InitiatingMessage ::= SEQUENCE {
+    procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),
+    criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value LCS-AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+SuccessfulOutcome ::= SEQUENCE {
+    procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),
+    criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value LCS-AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+UnsuccessfulOutcome ::= SEQUENCE {
+    procedureCode LCS-AP-ELEMENTARY-PROCEDURE.&procedureCode ({LCS-AP-ELEMENTARY-PROCEDURES}),
+    criticality LCS-AP-ELEMENTARY-PROCEDURE.&criticality ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value LCS-AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({LCS-AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+-- *****
+
+```
+
+```
+--  
+-- Interface Elementary Procedure List  
+--  
+-- *****  
+  
+LCS-AP-ELEMENTARY-PROCEDURES LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 |  
+    LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 ,  
+    ...  
+}  
+  
+LCS-AP-ELEMENTARY-PROCEDURES-CLASS-1 LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    location-Service-Request |  
+    connectionless-Information-Transfer |  
+    location-Abort |  
+    reset |  
+    ciphering-Key-Data-Delivery ,  
+    ...  
+}  
+  
+LCS-AP-ELEMENTARY-PROCEDURES-CLASS-2 LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    connection-Oriented-Information-Transfer ,  
+    ...  
+}  
+  
+-- *****  
+--  
+-- Interface Elementary Procedures  
+--  
+-- *****  
+  
+location-Service-Request LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Location-Request  
+    SUCCESSFUL OUTCOME Location-Response  
+    UNSUCCESSFUL OUTCOME Location-Response  
+    PROCEDURE CODE id-Location-Service-Request  
+    CRITICALITY reject  
+}  
+  
+connection-Oriented-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Connection-Oriented-Information  
+    PROCEDURE CODE id-Connection-Oriented-Information-Transfer  
+    CRITICALITY reject  
+}  
+  
+connectionless-Information-Transfer LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Connectionless-Information  
+    UNSUCCESSFUL OUTCOME Connectionless-Information  
+    PROCEDURE CODE id-Connectionless-Information-Transfer  
+    CRITICALITY reject  
+}  
+  
+location-Abort LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Location-Abort-Request  
+    SUCCESSFUL OUTCOME Location-Response  
+    PROCEDURE CODE id-Location-Abort  
+    CRITICALITY reject  
+}  
+  
+reset LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Reset-Request  
+    SUCCESSFUL OUTCOME Reset-Acknowledge  
+    PROCEDURE CODE id-Reset  
+    CRITICALITY reject  
+}  
+  
+ciphering-Key-Data-Delivery LCS-AP-ELEMENTARY-PROCEDURE ::= {  
+    INITIATING MESSAGE Ciphering-Key-Data  
+    SUCCESSFUL OUTCOME Ciphering-Key-Data-Result  
+    UNSUCCESSFUL OUTCOME Ciphering-Key-Data-Result  
+    PROCEDURE CODE id-Ciphering-Key-Data-Delivery  
+    CRITICALITY reject  
+}  
+  
+END
+```
+
+### 7.5.4 PDU definitions
+
+```
+
+-- *****
+--
+-- PDU definitions for LCS-AP.
+--
+-- *****
+
+LCS-AP-PDU-Contents {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-PDU-Contents (1) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+
+IMPORTS
+
+  APDU,
+  Accuracy-Fulfillment-Indicator,
+  Barometric-Pressure,
+  Cell-Portion-ID,
+  Ciphering-Data,
+  Ciphering-Data-Ack,
+  Ciphering-Data-Error-Report,
+  Civic-Address,
+  Correlation-ID,
+  Coverage-Level,
+  E-CGI,
+  Geographical-Area,
+  IMSI,
+  IMEI,
+  Include-Velocity,
+  LCS-Cause,
+  LCS-Client-Type,
+  LCS-Service-Type-ID,
+  LCS-Priority,
+  LCS-QoS,
+  Location-Type,
+  MultipleAPDUs,
+  Network-Element,
+  Payload-Type,
+  Positioning-Data,
+  RAT-Type,
+  Return-Error-Type,
+  Return-Error-Cause,
+  UE-Positioning-Capability,
+  Velocity-Estimate
+FROM LCS-AP-IEs
+
+  ProtocolExtensionContainer{},
+  ProtocolIE-Container{},
+  LCS-AP-PROTOCOL-EXTENSION,
+  LCS-AP-PROTOCOL-IES
+FROM LCS-AP-Containers
+
+  id-Accuracy-Fulfillment-Indicator,
+  id-APDU,
+  id-Barometric-Pressure,
+  id-Cell-Portion-ID,
+  id-Ciphering-Data,
+  id-Ciphering-Data-Ack,
+  id-Ciphering-Data-Error-Report,
+  id-Civic-Address,
+  id-Correlation-ID,
+  id-Coverage-Level,
+  id-Destination-ID,
+  id-E-UTRAN-Cell-Identifier,
+  id-Include-Velocity,
+  id-IMEI,
+
+```
+
+```
+
+id-IMSI,
+id-LCS-Client-Type,
+id-LCS-Priority,
+id-LCS-QoS,
+id-LCS-Cause,
+id-LCS-Service-Type-ID,
+id-Location-Estimate,
+id-Location-Type,
+id-MultipleAPDUs,
+id-Payload-Type,
+id-Positioning-Data,
+id-RAT-Type,
+id-Return-Error-Request,
+id-Return-Error-Cause,
+id-Source-Identity,
+id-UE-Positioning-Capability,
+id-Velocity-Estimate
+FROM LCS-AP-Constants;
+
+-- *****
+--
+-- Location-Request
+--
+-- *****
+
+Location-Request ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { { Location-Request-IEs} },
+  protocolExtensions ProtocolExtensionContainer { { Location-Request-Extensions} } OPTIONAL,
+  ...
+}
+
+Location-Request-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |
+  { ID id-Location-Type CRITICALITY reject TYPE Location-Type PRESENCE mandatory } |
+  { ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore TYPE E-CGI PRESENCE mandatory } |
+  { ID id-LCS-Client-Type CRITICALITY reject TYPE LCS-Client-Type PRESENCE optional } |
+  { ID id-LCS-Priority CRITICALITY reject TYPE LCS-Priority PRESENCE optional } |
+  { ID id-LCS-QoS CRITICALITY reject TYPE LCS-QoS PRESENCE optional } |
+  { ID id-UE-Positioning-Capability CRITICALITY reject TYPE UE-Positioning-Capability PRESENCE
+optional } |
+  { ID id-Include-Velocity CRITICALITY reject TYPE Include-Velocity PRESENCE optional } |
+  { ID id-IMSI CRITICALITY ignore TYPE IMSI PRESENCE optional } |
+  { ID id-IMEI CRITICALITY ignore TYPE IMEI PRESENCE optional } |
+  { ID id-MultipleAPDUs CRITICALITY reject TYPE MultipleAPDUs PRESENCE optional } |
+  { ID id-RAT-Type CRITICALITY ignore TYPE RAT-Type PRESENCE optional } |
+  { ID id-Coverage-Level CRITICALITY ignore TYPE Coverage-Level PRESENCE optional},
+  ...
+}
+
+Location-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  { ID id-LCS-Service-Type-ID CRITICALITY ignore EXTENSION LCS-Service-Type-ID PRESENCE
+optional },
+  ...
+}
+
+-- *****
+--
+-- Location-Response
+--
+-- *****
+
+Location-Response ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { { Location-Response-IEs} },
+  protocolExtensions ProtocolExtensionContainer { { Location-Response-Extensions} } OPTIONAL,
+  ...
+}
+
+Location-Response-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |
+  { ID id-Location-Estimate CRITICALITY reject TYPE Geographical-Area PRESENCE optional } |
+  { ID id-Positioning-Data CRITICALITY reject TYPE Positioning-Data PRESENCE optional } |
+  { ID id-Velocity-Estimate CRITICALITY reject TYPE Velocity-Estimate PRESENCE optional } |
+
+```
+
+```
+
+    { ID id-Accuracy-Fulfillment-Indicator CRITICALITY reject TYPE Accuracy-Fulfillment-Indicator
+      PRESENCE optional } |
+    { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE optional } ,
+  ...
+}
+
+Location-Response-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  { ID id-E-UTRAN-Cell-Identifier CRITICALITY ignore EXTENSION E-CGI PRESENCE optional } |
+  { ID id-Cell-Portion-ID CRITICALITY ignore EXTENSION Cell-Portion-ID PRESENCE optional } |
+  { ID id-Civic-Address CRITICALITY ignore EXTENSION Civic-Address PRESENCE optional } |
+  { ID id-Barometric-Pressure CRITICALITY ignore EXTENSION Barometric-Pressure PRESENCE
+    optional } ,
+  ...
+}
+
+-- *****
+--
+-- Location-Abort
+--
+-- *****
+
+Location-Abort-Request ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {Location-Abort-Request-IEs} },
+  protocolExtensions ProtocolExtensionContainer { {Location-Abort-Request-Extensions} } OPTIONAL,
+  ...
+}
+
+Location-Abort-Request-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE mandatory } |
+  { ID id-LCS-Cause CRITICALITY ignore TYPE LCS-Cause PRESENCE mandatory } ,
+  ...
+}
+
+Location-Abort-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Connection-Oriented-Information
+--
+-- *****
+
+Connection-Oriented-Information ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {Connection-Oriented-Information-IEs} },
+  protocolExtensions ProtocolExtensionContainer { {Connection-Oriented-Information-Extensions} }
+  OPTIONAL,
+  ...
+}
+
+Connection-Oriented-Information-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Correlation-ID CRITICALITY reject TYPE Correlation-ID PRESENCE optional } |
+  { ID id-Payload-Type CRITICALITY reject TYPE Payload-Type PRESENCE optional } |
+  { ID id-APDU CRITICALITY reject TYPE APDU PRESENCE optional } ,
+  ...
+}
+
+Connection-Oriented-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Connectionless-Information
+--
+-- *****
+
+Connectionless-Information ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {Connectionless-Information-IEs} },
+  protocolExtensions ProtocolExtensionContainer { {Connectionless-Information-Extensions} }
+  OPTIONAL,
+  ...
+}
+
+Connectionless-Information-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Source-Identity CRITICALITY reject TYPE Network-Element PRESENCE mandatory } |
+  { ID id-Destination-ID CRITICALITY reject TYPE Network-Element PRESENCE mandatory } |
+
+```
+
+```
+
+    { ID id-APDU      CRITICALITY reject  TYPE APDU      PRESENCE mandatory } |
+    { ID id-Return-Error-Request  CRITICALITY reject  TYPE Return-Error-Type  PRESENCE optional }
+|
+    { ID id-Return-Error-Cause  CRITICALITY ignore  TYPE Return-Error-Cause  PRESENCE optional } ,
+    ...
+}
+
+Connectionless-Information-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Reset-Request
+--
+-- *****
+
+Reset-Request ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {Reset-Request-IEs} },
+  protocolExtensions ProtocolExtensionContainer { {Reset-Request-Extensions} } OPTIONAL,
+  ...
+}
+
+Reset-Request-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-LCS-Cause  CRITICALITY ignore  TYPE LCS-Cause  PRESENCE mandatory } ,
+  ...
+}
+
+Reset-Request-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Reset-Acknowledge
+--
+-- *****
+
+Reset-Acknowledge ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { { Reset-Acknowledge-IEs} },
+  protocolExtensions ProtocolExtensionContainer { { Reset-Acknowledge-Extensions} } OPTIONAL,
+  ...
+}
+
+Reset-Acknowledge-IEs LCS-AP-PROTOCOL-IES ::= {
+  ...
+}
+
+Reset-Acknowledge-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- *****
+--
+-- Ciphering-Key-Data
+--
+-- *****
+
+Ciphering-Key-Data ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {Ciphering-Key-Data-IEs} },
+  protocolExtensions ProtocolExtensionContainer { {Ciphering-Key-Data-Extensions} } OPTIONAL,
+  ...
+}
+
+Ciphering-Key-Data-IEs LCS-AP-PROTOCOL-IES ::= {
+  { ID id-Ciphering-Data  CRITICALITY reject  TYPE Ciphering-Data  PRESENCE mandatory } ,
+  ...
+}
+
+Ciphering-Key-Data-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- Ciphering-Key-Data-Result
+--
+-- *****
+
+Ciphering-Key-Data-Result ::= SEQUENCE {
+    protocolIEs ProtocolIE-Container { {Ciphering-Key-Data-Result-IEs} },
+    protocolExtensions ProtocolExtensionContainer { {Ciphering-Key-Data-Result-Extensions} }
+    OPTIONAL,
+    ...
+}
+
+Ciphering-Key-Data-Result-IEs LCS-AP-PROTOCOL-IES ::= {
+    { ID id-Ciphering-Data-Ack CRITICALITY reject TYPE Ciphering-Data-Ack PRESENCE conditional } |
+    { ID id-Ciphering-Data-Error-Report CRITICALITY reject TYPE Ciphering-Data-Error-Report
+    PRESENCE conditional } ,
+    ...
+}
+
+Ciphering-Key-Data-Result-Extensions LCS-AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+END
+
+```
+
+### 7.5.5 Information element definitions
+
+```
+
+-- *****
+--
+-- Information Element Definitions
+--
+-- *****
+
+LCS-AP-IEs {
+    itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+    eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-IEs (2)}
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+IMPORTS
+
+    max-No-Of-Points,
+    max-Set,
+    max-GNSS-Set,
+    max-Add-Pos-Set,
+    max-Cipher-Set,
+    id-Additional-PositioningDataSet
+FROM LCS-AP-Constants
+
+    Criticality,
+    ProcedureCode,
+    TriggeringMessage,
+    ProtocolIE-ID
+FROM LCS-AP-CommonDataTypes
+
+    ProtocolExtensionContainer{},
+    LCS-AP-PROTOCOL-EXTENSION
+FROM LCS-AP-Containers;
+
+-- A
+
+APDU ::= OCTET STRING
+
+Accuracy-Fulfillment-Indicator ::= ENUMERATED {
+    requested-accuracy-fulfilled,
+    requested-accuracy-not-fulfilled,
+}
+
+```
+
+```
+    ...  
+}  
+  
+Additional-PositioningDataSet ::= SEQUENCE (SIZE (1..max-Add-Pos-Set)) OF Additional-  
+PositioningMethodAndUsage  
+  
+Additional-PositioningMethodAndUsage ::= OCTET STRING (SIZE (1))  
+  
+Altitude ::= INTEGER (0..65535)  
+-- The valid value for this IE is 0 to 32767.  
+-- Reception of value greater than 32767 shall be mapped to the value 32767.  
+  
+Altitude-And-Direction ::= SEQUENCE {  
+    direction-Of-Altitude   Direction-Of-Altitude,  
+    altitude                Altitude,  
+    ...  
+}  
+  
+Angle ::= INTEGER (0..179)  
+  
+-- B  
+  
+Barometric-Pressure ::= INTEGER (30000..115000)  
+  
+Bearing ::= INTEGER (0..359)  
+  
+-- C  
+  
+C0 ::= BIT STRING (SIZE (1..128))  
+  
+CellIdentity ::= BIT STRING (SIZE (28))  
+  
+Cell-Portion-ID ::= INTEGER (0..255,..., 256..4095)  
+  
+Ciphering-Data ::= SEQUENCE (SIZE (1..max-Cipher-Set)) OF Ciphering-Data-Set  
+  
+Ciphering-Data-Ack ::= SEQUENCE (SIZE (1..max-Cipher-Set)) OF Ciphering-Set-ID  
+  
+Ciphering-Data-Error-Report ::= SEQUENCE (SIZE (1..max-Cipher-Set)) OF Ciphering-Data-Error-Report-  
+Contents  
+  
+Ciphering-Data-Set ::= SEQUENCE {  
+    ciphering-Set-ID      Ciphering-Set-ID,  
+    ciphering-Key         Ciphering-Key,  
+    C0                    C0,  
+    sib-Types             SIB-Types,  
+    validity-Start-Time   Validity-Start-Time,  
+    validity-Duration     Validity-Duration,  
+    tais-List             TAIs-List,  
+    ...  
+}  
+  
+Ciphering-Data-Error-Report-Contents ::= SEQUENCE {  
+    ciphering-Set-ID      Ciphering-Set-ID,  
+    storage-Outcome       Storage-Outcome,  
+    ...  
+}  
+  
+Ciphering-Set-ID ::= INTEGER (0..65535)  
+  
+Ciphering-Key ::= OCTET STRING (SIZE (16))  
+  
+Civic-Address ::= OCTET STRING  
+  
+Confidence ::= INTEGER (0..100)  
+  
+Correlation-ID ::= OCTET STRING (SIZE (4))  
+  
+-- D  
+  
+DegreesLatitude ::= INTEGER (0..8388607) -- 23 bit field  
+  
+DegreesLongitude ::= INTEGER (-8388608..8388607) -- 24 bit field
+```
+
+```
+Direction-Of-Altitude ::= ENUMERATED {  
+    height,  
+    depth  
+}  
+  
+-- E  
+  
+E-CGI ::= SEQUENCE {  
+    pLMNidentity    PLMN-ID,  
+    cell-ID         CellIdentity,  
+    iE-Extensions   ProtocolExtensionContainer { { E-CGI-ExtIEs} } OPTIONAL,  
+    ...  
+}  
+  
+E-CGI-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Coverage-Level ::= ENUMERATED {  
+    extendedcoverage,  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE {  
+    geographical-Coordinates    Geographical-Coordinates,  
+    uncertainty-Ellipse         Uncertainty-Ellipse,  
+    confidence                  Confidence,  
+    iE-Extensions               ProtocolExtensionContainer { { Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs}  
+} OPTIONAL,  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Altitude ::= SEQUENCE {  
+    geographical-Coordinates    Geographical-Coordinates,  
+    altitude-And-Direction      Altitude-And-Direction,  
+    iE-Extensions               ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-ExtIEs} } OPTIONAL,  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Altitude-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE {  
+    geographical-Coordinates    Geographical-Coordinates,  
+    altitude-And-Direction      Altitude-And-Direction,  
+    uncertainty-Ellipse         Uncertainty-Ellipse,  
+    uncertainty-Altitude        Uncertainty-Altitude,  
+    confidence                  Confidence,  
+    iE-Extensions               ProtocolExtensionContainer { { Ellipsoid-Point-With-Altitude-And-Uncertainty-  
+Ellipsoid-ExtIEs} } OPTIONAL,  
+    ...  
+}  
+  
+Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Ellipsoid-Arc ::= SEQUENCE {  
+    geographical-Coordinates    Geographical-Coordinates,  
+    inner-Radius                Inner-Radius,  
+    uncertainty-Radius          Uncertainty-Code,  
+    offset-Angle                Angle,  
+    included-Angle              Angle,  
+    confidence                  Confidence,  
+    iE-Extensions               ProtocolExtensionContainer { { Ellipsoid-Arc-ExtIEs} } OPTIONAL,  
+    ...  
+}  
+  
+Ellipsoid-Arc-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}
+```
+
+```
+
+ENB-ID ::= CHOICE {
+    macro-eNB-ID    Macro-eNB-ID,
+    home-eNB-ID     Home-eNB-ID,
+    ...,
+    short-macro-eNB-ID    Short-Macro-eNB-ID,
+    long-macro-eNB-ID     Long-Macro-eNB-ID
+}
+
+E-SMLC-ID ::= INTEGER (0..255)
+
+-- F
+-- G
+
+Geographical-Area ::= CHOICE {
+    point             Point,
+    point-With-Uncertainty        Point-With-Uncertainty,
+    ellipsoidPoint-With-Uncertainty-Ellipse     Ellipsoid-Point-With-Uncertainty-Ellipse,
+    polygon             Polygon,
+    ellipsoid-Point-With-Altitude     Ellipsoid-Point-With-Altitude,
+    ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid     Ellipsoid-Point-With-Altitude-And-
+    Uncertainty-Ellipsoid,
+    ellipsoid-Arc             Ellipsoid-Arc,
+    ...,
+    high-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse     High-Accuracy-Ellipsoid-Point-With-
+    Uncertainty-Ellipse,
+    high-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid     High-Accuracy-Ellipsoid-
+    Point-With-Altitude-And-Uncertainty-Ellipsoid,
+    high-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse     High-Accuracy-Ellipsoid-Point-
+    With-Scalable-Uncertainty-Ellipse,
+    high-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid     High- Accuracy-
+    Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid
+}
+
+Geographical-Coordinates ::= SEQUENCE {
+    latitudeSign    LatitudeSign,
+    degreesLatitude     DegreesLatitude,
+    degreesLongitude     DegreesLongitude,
+    iE-Extensions     ProtocolExtensionContainer { {Geographical-Coordinates-ExtIEs} } OPTIONAL,
+    ...
+}
+
+Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Global-eNB-ID ::= SEQUENCE {
+    pLMN-ID     PLMN-ID,
+    eNB-ID     ENB-ID
+}
+
+GNSS-Positioning-Method-And-Usage ::= OCTET STRING (SIZE (1))
+
+GNSS-Positioning-Data-Set ::= SEQUENCE (SIZE (1..max-GNSS-Set)) OF GNSS-Positioning-Method-And-Usage
+
+-- H
+
+High-Accuracy-Altitude ::= INTEGER (-64000..1280000)
+
+High-Accuracy-DegreesLatitude ::= INTEGER(-2147483648..2147483647)
+
+High-Accuracy-DegreesLongitude ::= INTEGER(-2147483648..2147483647)
+
+High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse ::= SEQUENCE {
+    high-Accuracy-Geographical-Coordinates     High-Accuracy-Geographical-Coordinates,
+    high-Accuracy-Uncertainty-Ellipse     High-Accuracy-Uncertainty-Ellipse,
+    confidence     Confidence,
+    iE-Extensions     ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Uncertainty-
+    Ellipse-ExtIEs} } OPTIONAL,
+    ...
+}
+
+```
+
+```
+High-Accuracy-Ellipsoid-Point-With-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse ::= SEQUENCE {
+  high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,
+  high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse,
+  confidence Confidence,
+  iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Scalable-
+  Uncertainty-Ellipse-ExtIEs} } OPTIONAL,
+  ...}
+
+High-Accuracy-Ellipsoid-Point-With-Scalable-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::=
+{
+  ...
+}
+
+High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid ::= SEQUENCE {
+  high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,
+  high-Accuracy-Altitude High-Accuracy-Altitude,
+  high-Accuracy-Uncertainty-Ellipse High-Accuracy-Uncertainty-Ellipse,
+  confidence Confidence,
+  high-Accuracy-Uncertainty-Altitude High-Accuracy-Uncertainty-Code,
+  vertical-Confidence Confidence,
+  iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And-
+  Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL,
+  ...}
+
+High-Accuracy-Ellipsoid-Point-With-Altitude-And-Uncertainty-Ellipsoid-ExtIEs LCS-AP-PROTOCOL-
+EXTENSION ::= {
+  ...
+}
+
+High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid ::= SEQUENCE {
+  high-Accuracy-Geographical-Coordinates High-Accuracy-Geographical-Coordinates,
+  high-Accuracy-Altitude High-Accuracy-Altitude,
+  high-Accuracy-Scalable-Uncertainty-Ellipse High-Accuracy-Scalable-Uncertainty-Ellipse,
+  confidence Confidence,
+  high-Accuracy-Scalable-Uncertainty-Altitude High-Accuracy-Scalable-Uncertainty-Altitude,
+  vertical-Confidence Confidence,
+  iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Ellipsoid-Point-With-Altitude-And-
+  Scalable-Uncertainty-Ellipsoid-ExtIEs} } OPTIONAL,
+  ...}
+
+High-Accuracy-Ellipsoid-Point-With-Altitude-And-Scalable-Uncertainty-Ellipsoid-ExtIEs LCS-AP-
+PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+High-Accuracy-Geographical-Coordinates ::= SEQUENCE {
+  high-Accuracy-DegreesLatitude High-Accuracy-DegreesLatitude,
+  high-Accuracy-DegreesLongitude High-Accuracy-DegreesLongitude,
+  iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Geographical-Coordinates-ExtIEs} }
+  OPTIONAL,
+  ...
+}
+
+High-Accuracy-Geographical-Coordinates-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+High-Accuracy-Uncertainty-Code ::= INTEGER (0..255)
+
+High-Accuracy-Extended-Uncertainty-Code ::= INTEGER (0..255)
+
+High-Accuracy-Uncertainty-Ellipse ::= SEQUENCE {
+  high-Accuracy-Uncertainty-SemiMajor High-Accuracy-Uncertainty-Code,
+  high-Accuracy-Uncertainty-SemiMinor High-Accuracy-Uncertainty-Code,
+  orientation-Major-Axis INTEGER (0..179),
+  iE-Extensions ProtocolExtensionContainer { { High-Accuracy-Uncertainty-Ellipse-ExtIEs} }
+  OPTIONAL,
+  ...
+}
+```
+
+```
+}  
+  
+High-Accuracy-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+High-Accuracy-Extended-Uncertainty-Ellipse ::= SEQUENCE {  
+  high-Accuracy-Extended-Uncertainty-SemiMajor   High-Accuracy-Extended-Uncertainty-Code,  
+  high-Accuracy-Extended-Uncertainty-SemiMinor   High-Accuracy-Extended-Uncertainty-Code,  
+  orientation-Major-Axis   INTEGER (0..179),  
+  iE-Extensions   ProtocolExtensionContainer { { High-Accuracy-Extended-Uncertainty-Ellipse-ExtIEs} } OPTIONAL,  
+  ...  
+}  
+  
+High-Accuracy-Extended-Uncertainty-Ellipse-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+High-Accuracy-Scalable-Uncertainty-Ellipse ::= CHOICE {  
+  high-Accuracy-Uncertainty-Ellipse   High-Accuracy-Uncertainty-Ellipse,  
+  high-Accuracy-Extended-Uncertainty-Ellipse   High-Accuracy-Extended-Uncertainty-Ellipse  
+}  
+  
+High-Accuracy-Scalable-Uncertainty-Altitude ::= CHOICE {  
+  high-Accuracy-Uncertainty-Altitude   High-Accuracy-Uncertainty-Code,  
+  high-Accuracy-Extended-Uncertainty-Altitude   High-Accuracy-Extended-Uncertainty-Code  
+}  
+  
+Home-eNB-ID ::= BIT STRING (SIZE (28))  
+  
+Horizontal-Accuracy ::= INTEGER (0..127)  
+  
+  
+Horizontal-Speed-And-Bearing ::= SEQUENCE {  
+  bearing   INTEGER (0..359),  
+  horizontal-Speed   INTEGER (0..2047)  
+}  
+  
+Horizontal-Velocity ::= SEQUENCE {  
+  horizontal-Speed-And-Bearing   Horizontal-Speed-And-Bearing,  
+  iE-Extensions   ProtocolExtensionContainer { { Horizontal-Velocity-ExtIEs} } OPTIONAL,  
+  ...  
+}  
+  
+Horizontal-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+Horizontal-With-Vertical-Velocity ::= SEQUENCE {  
+  horizontal-Speed-And-Bearing   Horizontal-Speed-And-Bearing,  
+  vertical-Velocity   Vertical-Velocity,  
+  iE-Extensions   ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-ExtIEs} } OPTIONAL,  
+  ...  
+}  
+  
+Horizontal-With-Vertical-Velocity-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+Horizontal-Velocity-With-Uncertainty ::= SEQUENCE {  
+  horizontal-Speed-And-Bearing   Horizontal-Speed-And-Bearing,  
+  uncertainty-Speed   INTEGER (0..255),  
+  iE-Extensions   ProtocolExtensionContainer { { Horizontal-Velocity-With-Uncertainty-ExtIEs} } OPTIONAL,  
+  ...  
+}  
+  
+Horizontal-Velocity-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+Horizontal-With-Vertical-Velocity-And-Uncertainty ::= SEQUENCE {  
+  horizontal-Speed-And-Bearing   Horizontal-Speed-And-Bearing,  
+  vertical-Velocity   Vertical-Velocity,  
+  ...  
+}
+```
+
+```
+    horizontal-Uncertainty-Speed    INTEGER (0..255),  
+    vertical-Uncertainty-Speed    INTEGER (0..255),  
+    iE-Extensions                ProtocolExtensionContainer { { Horizontal-With-Vertical-Velocity-And-  
+Uncertainty-ExtIEs } } OPTIONAL,  
+    ...  
+}  
+  
+Horizontal-With-Vertical-Velocity-And-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+-- I  
+  
+IMSI    ::= OCTET STRING (SIZE (3..8))  
+  
+IMEI    ::= OCTET STRING (SIZE (8))  
+  
+Include-Velocity    ::= ENUMERATED {  
+    requested,  
+    not-Requested,  
+    ...  
+}  
+  
+Inner-Radius    ::= INTEGER (0..65535)    -- 16 bit field  
+  
+-- J  
+-- K  
+-- L  
+  
+LatitudeSign    ::= ENUMERATED {  
+    north,  
+    south  
+}  
+  
+Location-Type    ::= ENUMERATED {  
+    geographic-Information,  
+    assistance-Information,  
+    ...,  
+    last-known-location  
+}  
+  
+LCS-Cause    ::= CHOICE {  
+    radio-Network-Layer Radio-Network-Layer-Cause,  
+    transport-Layer Transport-Layer-Cause,  
+    protocol    Protocol-Cause,  
+    misc    Misc-Cause  
+}  
+  
+LCS-Client-Type ::= ENUMERATED {  
+    emergency-Services,  
+    value-Added-Services,  
+    pLMN-Operator-Services,  
+    lawful-Intercept-Services,  
+    pLMN-Operator-broadcast-Services,  
+    pLMN-Operator-OM,  
+    pLMN-Operator-Anonymous-Statistics,  
+    pLMN-Operator-Target-MS-Service-Support,  
+    ...  
+}  
+  
+LCS-Priority    ::= OCTET STRING (SIZE (1))  
+  
+LCS-QoS    ::= SEQUENCE {  
+    horizontal-Accuracy Horizontal-Accuracy OPTIONAL,  
+    vertical-Requested Vertical-Requested OPTIONAL,  
+    vertical-Accuracy Vertical-Accuracy OPTIONAL,  
+    response-Time Response-Time OPTIONAL,  
+    ...  
+}
+```
+
+```
+LCS-Service-Type-ID ::= INTEGER (0..127)
+
+Long-Macro-eNB-ID ::= BIT STRING (SIZE (21))
+
+-- M
+
+Macro-eNB-ID ::= BIT STRING (SIZE (20))
+
+Message-Identifier ::= BIT STRING (SIZE (16))
+
+Misc-Cause ::= ENUMERATED {
+    processing-Overload,
+    hardware-Failure,
+    o-And-M-Intervention,
+    unspecified,
+    ...
+    ciphering-key-data-lost
+}
+
+MultipleAPDUs ::= SEQUENCE (SIZE (1.. 3)) OF APDU
+
+-- N
+
+Network-Element ::= CHOICE {
+    global-eNB-ID   Global-eNB-ID,
+    e-SMLC-ID       E-SMLC-ID
+}
+
+-- O
+
+Orientation-Major-Axis ::= INTEGER (0..89)
+
+-- P
+
+Payload-Type ::= ENUMERATED {
+    lPP,
+    lPPa,
+    ...
+}
+
+PLMN-ID ::= TBCD-STRING
+
+Point ::= SEQUENCE {
+    geographical-Coordinates    Geographical-Coordinates,
+    iE-Extensions               ProtocolExtensionContainer { {Point-ExtIEs} } OPTIONAL,
+    ...
+}
+
+Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Point-With-Uncertainty ::= SEQUENCE {
+    geographical-Coordinates    Geographical-Coordinates,
+    uncertainty-Code            Uncertainty-Code,
+    iE-Extensions               ProtocolExtensionContainer { {Point-With-Uncertainty-ExtIEs} } OPTIONAL,
+    ...
+}
+
+Point-With-Uncertainty-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Polygon ::= SEQUENCE (SIZE (1..max-No-Of-Points)) OF Polygon-Point
+
+Polygon-Point ::= SEQUENCE {
+    geographical-Coordinates    Geographical-Coordinates,
+    iE-Extensions               ProtocolExtensionContainer { {Polygon-Point-ExtIEs} } OPTIONAL,
+    ...
+}
+
+Polygon-Point-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+```
+
+```
+Positioning-Data      ::= SEQUENCE {  
+    positioning-Data-Set    Positioning-Data-Set OPTIONAL,  
+    gnss-Positioning-Data-Set    GNSS-Positioning-Data-Set OPTIONAL,  
+    iE-Extensions    ProtocolExtensionContainer { { Positioning-Data-ExtIEs} } OPTIONAL,  
+    ...  
+}  
+  
+Positioning-Data-ExtIEs LCS-AP-PROTOCOL-EXTENSION ::= {  
+    ID id-Additional-PositioningDataSet    CRITICALITY ignore    EXTENSION Additional-  
+    PositioningDataSet    PRESENCE optional },  
+    ...  
+}  
+  
+Positioning-Data-Set      ::= SEQUENCE (SIZE (1..max-Set)) OF Positioning-Method-And-Usage  
+  
+Positioning-Method-And-Usage      ::= OCTET STRING (SIZE (1))  
+  
+Protocol-Cause      ::= ENUMERATED {  
+    transfer-Syntax-Error,  
+    abstract-Syntax-Error-Reject,  
+    abstract-Syntax-Error-Ignore-And-Notify,  
+    message-Not-Compatible-With-Receiver-State,  
+    semantic-Error,  
+    unspecified,  
+    abstract-Syntax-Error,  
+    ...  
+}  
+  
+-- Q  
+-- R  
+  
+Radio-Network-Layer-Cause      ::= ENUMERATED {  
+    unspecified,  
+    ...  
+}  
+  
+RAT-Type      ::= ENUMERATED {  
+    lte-wb,  
+    nb-iot,  
+    ...,  
+    lte-m  
+}  
+  
+Response-Time      ::= ENUMERATED {  
+    low-Delay(0),  
+    delay-Tolerant(1),  
+    ...  
+}  
+  
+Return-Error-Type ::= ENUMERATED {  
+    yes,  
+    no  
+}  
+  
+Return-Error-Cause ::= ENUMERATED {  
+    system-Failure,  
+    protocol-Error,  
+    destination-Unknown,  
+    destination-Unreachable,  
+    congestion,  
+    ...  
+}  
+  
+-- S  
+  
+Short-Macro-eNB-ID ::= BIT STRING (SIZE (18))  
+  
+SIB-Types ::= OCTET STRING (SIZE (4))  
+  
+Storage-Outcome ::= ENUMERATED {  
+    successful,  
+    failed  
+}  
+  
+-- T  
+  
+TAIs-List ::= OCTET STRING (SIZE (7..97))
+```
+
+```
+
+TBCD-STRING ::= OCTET STRING (SIZE (3))
+
+Transport-Layer-Cause ::= ENUMERATED {
+  tranport-Resource-Unavailable,
+  unspecified,
+  ...
+}
+
+-- U
+
+Uncertainty-Altitude ::= INTEGER (0..127)
+
+Uncertainty-Code ::= INTEGER (0..127)
+
+Uncertainty-Ellipse ::= SEQUENCE {
+  uncertainty-SemiMajor   Uncertainty-Code,
+  uncertainty-SemiMinor   Uncertainty-Code,
+  orientation-Major-Axis  Orientation-Major-Axis
+}
+
+UE-Positioning-Capability ::= SEQUENCE {
+  lpp   BOOLEAN,
+  ...
+}
+
+-- V
+
+Validity-Duration ::= INTEGER (0..65535)
+
+Validity-Start-Time ::= OCTET STRING (SIZE (4))
+
+Velocity-Estimate ::= CHOICE {
+  horizontal-Velocity       Horizontal-Velocity,
+  horizontal-With-Vertical-Velocity   Horizontal-With-Vertical-Velocity,
+  horizontal-Velocity-With-Uncertainty   Horizontal-Velocity-With-Uncertainty,
+  horizontal-With-Vertical-Velocity-And-Uncertainty   Horizontal-With-Vertical-Velocity-And-
+  Uncertainty,
+  ...
+}
+
+Vertical-Requested ::= ENUMERATED {
+  vertical-coordinate-Is-Not-Requested(0),
+  vertical-coordinate-Is-Requested(1)
+}
+
+Vertical-Accuracy ::= INTEGER (0..127)
+
+Vertical-Velocity ::= SEQUENCE {
+  vertical-Speed      INTEGER (0..255),
+  vertical-Speed-Direction   Vertical-Speed-Direction
+}
+
+Vertical-Speed-Direction ::= ENUMERATED {
+  upward,
+  downward
+}
+
+-- W
+-- X
+-- Y
+
+END
+
+```
+
+### 7.5.6 Common definitions
+
+```
+
+-- *****
+--
+-- Common definitions
+--
+-- *****
+
+LCS-AP-CommonDataTypes {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-CommonDataTypes (3)}
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+```
+
+```
+
+BEGIN
+
+Criticality := ENUMERATED { reject, ignore, notify }
+
+Presence := ENUMERATED { optional, conditional, mandatory }
+
+ProcedureCode := INTEGER (0..255)
+
+ProtocolExtensionID := INTEGER (0..65535)
+
+ProtocolIE-ID := INTEGER (0..65535)
+
+TriggeringMessage := ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome,
+outcome }
+
+END
+
+```
+
+### 7.5.7 Constant definitions
+
+```
+
+-- *****
+--
+-- Constant definitions
+--
+-- *****
+
+LCS-AP-Constants {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Constants (4)}
+
+DEFINITIONS AUTOMATIC TAGS :=
+
+BEGIN
+
+-- *****
+--
+-- Elementary Procedures
+--
+-- *****
+
+id-Location-Service-Request      INTEGER := 0
+id-Connection-Oriented-Information-Transfer INTEGER := 1
+id-Connectionless-Information-Transfer INTEGER := 2
+id-Location-Abort                INTEGER := 3
+id-Reset                         INTEGER := 4
+id-Ciphering-Key-Data-Delivery   INTEGER := 5
+
+-- *****
+--
+-- IEs
+--
+-- *****
+
+id-Accuracy-Fulfillment-Indicator  INTEGER := 0
+id-APDU                            INTEGER := 1
+id-Correlation-ID                  INTEGER := 2
+id-Destination-ID                  INTEGER := 3
+id-E-UTRAN-Cell-Identifier       INTEGER := 4
+id-Include-Velocity                INTEGER := 5
+id-IMEI                            INTEGER := 6
+id-IMSI                            INTEGER := 7
+id-LCS-Client-Type                 INTEGER := 8
+id-LCS-Priority                    INTEGER := 9
+id-LCS-QOS                         INTEGER := 10
+id-LCS-Cause                       INTEGER := 11
+id-Location-Estimate               INTEGER := 12
+id-Location-Type                   INTEGER := 13
+id-MultipleAPDUs                   INTEGER := 14
+id-Payload-Type                    INTEGER := 15
+id-Positioning-Data                INTEGER := 16
+id-Return-Error-Request            INTEGER := 17
+id-Return-Error-Cause              INTEGER := 18
+id-Source-Identity                 INTEGER := 19
+
+```
+
+```
+
+id-UE-Positioning-Capability    INTEGER ::= 20
+id-Velocity-Estimate            INTEGER ::= 21
+id-LCS-Service-Type-ID          INTEGER ::= 22
+id-Cell-Portion-ID              INTEGER ::= 23
+id-Civic-Address                INTEGER ::= 24
+id-Barometric-Pressure          INTEGER ::= 25
+id-Additional-PositioningDataSet    INTEGER ::= 26
+id-RAT-Type                     INTEGER ::= 27
+id-Ciphering-Data               INTEGER ::= 28
+id-Ciphering-Data-Ack           INTEGER ::= 29
+id-Ciphering-Data-Error-Report  INTEGER ::= 30
+id-Coverage-Level               INTEGER ::= 31
+
+-- **************************************************************
+--
+-- Extension constants
+--
+-- **************************************************************
+
+-- **************************************************************
+--
+-- Lists
+--
+-- **************************************************************
+
+max-No-Of-Points                INTEGER ::= 15
+max-Set                         INTEGER ::= 9
+max-GNSS-Set                    INTEGER ::= 9
+max-Add-Pos-Set                 INTEGER ::= 8
+max-Cipher-Set                  INTEGER ::= 16
+
+maxProtocolExtensions           INTEGER ::= 65535
+maxProtocolIEs                  INTEGER ::= 65535
+
+END
+
+```
+
+### 7.5.8 Container Definitions
+
+```
+
+-- **************************************************************
+--
+-- Container definitions
+--
+-- **************************************************************
+
+LCS-AP-Containers {
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+eps-Access (21) modules (3) lcs-AP (4) version1 (1) lcs-AP-Containers (5)}
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- **************************************************************
+--
+-- IE parameter types from other modules.
+--
+-- **************************************************************
+
+IMPORTS
+  Criticality,
+  Presence,
+  ProtocolExtensionID,
+  ProtocolIE-ID
+FROM LCS-AP-CommonDataTypes
+
+  maxProtocolExtensions,
+  maxProtocolIEs
+FROM LCS-AP-Constants;
+
+-- **************************************************************
+--
+-- Class Definition for Protocol IEs
+
+```
+
+```
+
+--
+-- *****
+
+LCS-AP-PROTOCOL-IES ::= CLASS {
+    &id ProtocolIE-ID    UNIQUE,
+    &criticality   Criticality DEFAULT ignore,
+    &Value,
+    &presence    Presence
+}
+WITH SYNTAX {
+    ID      &id
+    CRITICALITY &criticality
+    TYPE      &Value
+    PRESENCE    &presence
+}
+
+-- *****
+--
+-- Class Definition for Protocol Extensions
+--
+-- *****
+
+LCS-AP-PROTOCOL-EXTENSION ::= CLASS {
+    &id ProtocolExtensionID UNIQUE,
+    &criticality   Criticality DEFAULT ignore,
+    &Extension,
+    &presence    Presence
+}
+WITH SYNTAX {
+    ID      &id
+    CRITICALITY &criticality
+    EXTENSION    &Extension
+    PRESENCE    &presence
+}
+
+-- *****
+--
+-- Container for Protocol IEs
+--
+-- *****
+
+ProtocolIE-Container {LCS-AP-PROTOCOL-IES : IEsSetParam} ::=
+    SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+        ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Field {LCS-AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
+    id    LCS-AP-PROTOCOL-IES.&id    ({IEsSetParam}),
+    criticality    LCS-AP-PROTOCOL-IES.&criticality    ({IEsSetParam}{@id}),
+    value    LCS-AP-PROTOCOL-IES.&Value    ({IEsSetParam}{@id})
+}
+
+-- *****
+--
+-- Container Lists for Protocol IE Containers
+--
+-- *****
+
+ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, LCS-AP-PROTOCOL-IES :
+    IEsSetParam} ::=
+    SEQUENCE (SIZE (lowerBound..upperBound)) OF
+        ProtocolIE-Container {{IEsSetParam}}
+
+-- *****
+--
+-- Container for Protocol Extensions
+--
+-- *****
+
+ProtocolExtensionContainer {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=
+    SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
+        ProtocolExtensionField {{ExtensionSetParam}}
+
+ProtocolExtensionField {LCS-AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
+    id    LCS-AP-PROTOCOL-EXTENSION.&id    ({ExtensionSetParam}),
+    criticality    LCS-AP-PROTOCOL-EXTENSION.&criticality    ({ExtensionSetParam}{@id}),
+    extensionValue    LCS-AP-PROTOCOL-EXTENSION.&Extension    ({ExtensionSetParam}{@id})
+}
+
+```
+
+END
+
+### 7.5.9 Message transfer syntax
+
+LCS-AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ITU-T Recommendation X.691 [12].
+
+## 7.6 Handling of unknown, unforeseen and erroneous protocol data
+
+Clause 10 of 3GPP TS 36.413 [7] is applicable for the purposes of the present document.
+
+# 8 LCS-AP Timers
+
+## 8.1 General
+
+The description of timers in the following tables should be considered a brief summary.
+
+## 8.2 Timers of LCS-AP
+
+**Table 8.2.1: LCS-AP timers**
+
+| <b>TIMER NUM.</b> | <b>TIMER VALUE</b>                                                                | <b>CAUSE OF START</b>                                     | <b>NORMAL STOP</b>                            | <b>ON EXPIRY</b>                                                                       |
+|-------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------------|
+| T3x01             | This value can be operator configurable, based on the received QoS response time. | A Location Request procedure started in the MME.          | Location Response message is received         | MME shall send Abort message to E-SMLC and return error to the requesting entity       |
+| T3x02             | 3 seconds                                                                         | A Reset message is sent                                   | Reset Acknowledge message is received         | Retransmission of the Reset message                                                    |
+| T3x03             | This value can be operator configurable                                           | A Ciphering Keys Delivery procedure started in the E-SMLC | Ciphering Key Data Result message is received | E-SMLC shall abort the procedure and release any resources allocated for the procedure |
+
+# Annex A (informative): Change history
+
+| Date    | TSG #  | TSG Doc.  | CR   | Rev | Cev | Subject/Comment                                                                         | New    |
+|---------|--------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------|--------|
+| 2010-03 | CP-47  | CP-100054 |      |     |     | 3GPP TS presented for approval in CT#47                                                 | 9.0.0  |
+| 2010-06 | CP-48  | CP-100286 | 0001 |     | F   | Correction to Positioning Data Element                                                  | 9.1.0  |
+|         |        |           | 0003 |     | F   | Correction to Cell ID Category                                                          |        |
+| 2010-06 | CP-48  | CP-100417 | 0002 | 3   | F   | Provide Service Type ID to E-SMLC                                                       | 10.0.0 |
+| 2010-09 | CP-49  | CP-100463 | 0006 | 1   | F   | Define message transfer syntax in LCS-AP                                                | 10.1.0 |
+|         |        |           |      |     | F   | Add LCS-AP port identifier, payload protocol identifier and Elementary Procedure number |        |
+| 2011-03 | CP-51  | CP-110054 | 0014 | 2   | F   | Fix mismatches between technical description and ASN.1 coding                           | 10.2.0 |
+| 2011-06 | CP-52  | CP-110365 | 0016 | 1   | F   | Protocol Layering for LCS-AP                                                            | 10.3.0 |
+| 2011-09 | CP-53  | CP-110579 | 0020 | 1   | F   | Polygon encoding correction                                                             | 11.0.0 |
+| 2012-03 | CP-55  | CP-120038 | 0021 | 2   | F   | Use of multiple SCTP associations between MME and E-SMLC                                | 11.1.0 |
+| 2012-12 | CP-58  | CP-120880 | 0023 | 1   | F   | Mandatory Correlation ID in Connection Oriented Information                             | 11.2.0 |
+| 2013-06 | CP-60  | CP-130287 | 0024 | 1   | F   | APDU in Connection Oriented Information message                                         | 11.3.0 |
+| 2013-12 | CP-62  | CP-130631 | 0025 | 1   | F   | Adding E-SMLC provided Cell info and Cell Portion                                       | 12.0.0 |
+| 2014-06 | CP-64  | CP-140269 | 0026 | -   | F   | Value range of Cell-Portion-ID                                                          | 12.1.0 |
+| 2015-09 | CP-69  | CP-150441 | 0027 | 1   | F   | Clarification on the MME behaviour upon expiration of timer T3x01                       | 13.0.0 |
+| 2015-12 | CP-70  | CP-150740 | 0033 | -   | F   | ASN.1 Corrections                                                                       | 13.1.0 |
+| 2015-12 | CP-70  | CP-150766 | 0029 | 2   | F   | Indoor Positioning support in LCS-AP                                                    | 13.1.0 |
+| 2016-03 | CP/71  | CP-160024 | 0034 | -   | F   | Implementation Error in CR#29                                                           | 13.2.0 |
+| 2016-12 | CT#74  | CP-160668 | 0035 | 1   | F   | Consistency for UE-Based positioning method in LPP                                      | 14.0.0 |
+| 2016-12 | CT#74  | CP-160668 | 0036 | 1   | F   | Cell Portion ID Extension                                                               | 14.0.0 |
+| 2017-06 | CT#76  | CP-171030 | 0037 | 3   | F   | Enhancements to Location Services for CLoT                                              | 14.1.0 |
+| 2017-06 | CT#76  | CP-171030 | 0038 | 1   | F   | Location service message size adaptation according to coverage level                    | 14.1.0 |
+| 2017-06 | CT#76  | CP-171025 | 0039 | 2   | F   | LCS-AP corrections                                                                      | 14.1.0 |
+| 2017-12 | CT#78  | CP-173020 | 0042 | -   | F   | Introduction of New types of eNB ID                                                     | 14.2.0 |
+| 2018-06 | CT#80  | CP-181124 | 0043 | 1   | F   | Ciphering keys delivery to support broadcast of ciphered assistance data in E-UTRAN     | 15.0.0 |
+| 2018-09 | CT#81  | CP-182077 | 0045 | -   | F   | Update of SIB Types information in Ciphering Data Set                                   | 15.1.0 |
+| 2019-03 | CT#83  | CP-190034 | 0046 | 1   | F   | LTE-M RAT Type                                                                          | 15.2.0 |
+| 2019-09 | CT#85  | CP-192095 | 0047 | -   | F   | Ciphering key lost                                                                      | 15.3.0 |
+| 2019-09 | CT#85  | CP-192095 | 0050 | 1   | F   | Correction of ASN.1 errors                                                              | 15.3.0 |
+| 2019-09 | CT#85  | CP-192095 | 0051 | 1   | F   | Addition of High Accuracy location estimates                                            | 15.3.0 |
+| 2019-09 | CT#85  | CP-192093 | 0053 | 1   | F   | Correction on Coverage Level                                                            | 15.3.0 |
+| 2019-12 | CT#86  | CP-193034 | 0054 | -   | F   | Adding Motion-Sensor Method                                                             | 15.4.0 |
+| 2020-07 | CT#88e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                          | 16.0.0 |
+| 2020-09 | CT#89e | CP-202112 | 0055 | 1   | F   | Updating positioning SIBs in Ciphering Data Set                                         | 16.1.0 |
+| 2020-12 | CT#90e | CP-203023 | 0058 | 1   | A   | Essential Corrections to "High Accuracy Uncertainty Ellipse" type definition            | 16.2.0 |
+| 2021-12 | CT#94e | CP-213142 | 0059 | 1   | F   | High Accuracy GAD Shape with Scalable Uncertainty                                       | 16.3.0 |
+| 2022-09 | CT#97e | CP-222066 | 0061 | -   | F   | ASN.1 correction on Geographical-Area                                                   | 16.4.0 |
+| 2022-12 | CT#98e | CP-223072 | 0063 | -   | F   | Correction on High Accuracy Altitude                                                    | 16.5.0 |
+| 2023-06 | CT#100 | CP-231092 | 0066 | -   | F   | Missing GNSS IDs                                                                        | 16.6.0 |
+| 2023-06 | CT#100 | CP-231094 | 0068 | -   | F   | Remove Mandatory Presence Requirement for CHOICE Alternatives                           | 16.6.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29230/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29230/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d954c168d82e053a4ea42659953c6b8cb0204144
--- /dev/null
+++ b/marked/Rel-16/29_series/29230/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9be9098cc273aedf456ea528e6db65c2b7fecd1f8bd2d2548b829ee4bb2cd371
+size 10175
diff --git a/marked/Rel-16/29_series/29230/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29230/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..13b5604ef96ff159ce585e9c293e35af4495aa0d
--- /dev/null
+++ b/marked/Rel-16/29_series/29230/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0e735d138d15363cc674678a857d1caba672eb7c353fc97ac824ce56bddda62
+size 5626
diff --git a/marked/Rel-16/29_series/29230/raw.md b/marked/Rel-16/29_series/29230/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0556e0dc276afb3ccf2275eb91b7aa754051550
--- /dev/null
+++ b/marked/Rel-16/29_series/29230/raw.md
@@ -0,0 +1,2854 @@
+
+
+# 3GPP TS 29.230 V16.7.0 (2021-09)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Diameter applications; 3GPP specific codes and identifiers (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is the phrase "A GLOBAL INITIATIVE" in a smaller, all-caps, sans-serif font. To the right of the "3GPP" text is a small "TM" symbol.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                                              |           |
+|----------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                               | 4         |
+| 1 Scope.....                                                                                 | 5         |
+| 2 References.....                                                                            | 5         |
+| 3 Definitions and abbreviations .....                                                        | 7         |
+| 3.1 Definitions.....                                                                         | 7         |
+| 3.2 Abbreviations .....                                                                      | 7         |
+| 4 Application identifiers.....                                                               | 7         |
+| 4.1 3GPP specific application identifiers .....                                              | 7         |
+| 5 Command codes.....                                                                         | 9         |
+| 5.1 Command codes allocated for 3GPP.....                                                    | 9         |
+| 6 Vendor identifier.....                                                                     | 11        |
+| 6.1 3GPP's vendor identifier .....                                                           | 11        |
+| 7 Attribute-Value-Pair codes .....                                                           | 12        |
+| 7.1 3GPP specific AVP codes.....                                                             | 13        |
+| 8 Experimental result codes .....                                                            | 38        |
+| 8.1 3GPP specific result codes .....                                                         | 38        |
+| 8.1.1 Informational .....                                                                    | 38        |
+| 8.1.2 Success .....                                                                          | 38        |
+| 8.1.3 Transient Failures .....                                                               | 39        |
+| 8.1.4 Permanent Failures .....                                                               | 39        |
+| <b>Annex A (informative): Assignment of the Diameter codes and identifiers in 3GPP .....</b> | <b>43</b> |
+| A.1 Application identifiers.....                                                             | 43        |
+| A.2 Command codes.....                                                                       | 43        |
+| A.3 AVP codes.....                                                                           | 43        |
+| A.4 Result codes .....                                                                       | 43        |
+| <b>Annex B (informative): Change history .....</b>                                           | <b>45</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document lists the 3GPP specific Diameter protocol codes, including the AVP codes and Experimental result codes.
+
+This document lists also the application identifiers assigned to 3GPP specific Diameter applications by IANA and the Diameter command code range which is assigned to 3GPP by IANA.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents".
+- [2] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; Protocol details".
+- [3] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents".
+- [4] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; Protocol details".
+- [5] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications".
+- [6] 3GPP TS 29.234, Release 11: "3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3".
+- [7] 3GPP TS 29.109: "Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3".
+- [8] 3GPP TS 29.209, Release 6: "Policy control over Gq interface".
+- [9] IETF RFC 3588: "Diameter Base Protocol".
+- [10] IETF RFC 3589: "Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5".
+- [11] IANA's Enterprise-Numbers: <http://www.iana.org/assignments/enterprise-numbers>
+- [12] IANA's AAA parameters register: <ftp://ftp.iana.org/assignments/aaa-parameters/>
+
+- [13] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
+- [14] 3GPP TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces".
+- [15] 3GPP TS 29.210, Release 6: "Charging rule provisioning over Gx interface".
+- [16] 3GPP TS 29.140, Release 6: "Multimedia Messaging Service (MMS); MM10 interface based on Diameter protocol; Stage 3".
+- [17] 3GPP TS 29.211, Release 6: "Rx Interface and Rx/Gx signalling flows".
+- [18] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
+- [19] 3GPP TS 29.212: "Policy and Charging Control (PCC);Reference points".
+- [20] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
+- [21] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
+- [22] 3GPP TS 29.215: "Policy and Charging Control (PCC) over S9 reference point; Stage 3".
+- [23] IETF RFC 5516: "Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS)".
+- [24] 3GPP TS 29.172: "Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface".
+- [25] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS".
+- [26] 3GPP TS 29.219: "Policy and Charging Control: Spending Limit Reporting over Sy reference point".
+- [27] 3GPP TS 29.368: "Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS)".
+- [28] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
+- [29] 3GPP TS 29.337: "Diameter-based T4 interface for communications with packet data networks and applications".
+- [30] 3GPP TS 29.338: "Diameter based protocols to support SMS capable MMEs".
+- [31] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE)".
+- [32] 3GPP TS 29.343: "Proximity-services (ProSe) function to ProSe application server aspects (PC2)".
+- [33] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects".
+- [34] 3GPP TS 29.345: "Inter-Proximity-services (Prose) function signalling aspects; Stage 3".
+- [35] 3GPP TS 29.217: "Policy and Charging Control over Np reference point".
+- [36] 3GPP TS 29.128: "Diameter based T6a/T6b interface between the MME/SGSN and the SCEF".
+- [37] 3GPP TS 29.153: "Service exposure functionality between SCEF and RCAF reference point".
+- [38] 3GPP TS 29.154: "Service capability exposure functionality over Nt Reference point".
+- [39] 3GPP TS 29.283: "Diameter Data Management applications".
+
+- [40] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)".
+- [41] 3GPP TS 29.389: "Inter-V2X Control Function Signalling aspects (V6)".
+- [42] 3GPP TS 29.561: "Interworking between 5G Network and external Data Networks; Stage 3".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**3GPP specific:** A definition which is used in conjunction with the 3GPP's vendor identifier.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                     |
+|------|-------------------------------------|
+| AVP  | Attribute-Value-Pair                |
+| CR   | Change Request                      |
+| IANA | Internet Assigned Numbers Authority |
+| IETF | Internet Engineering Task Force     |
+| LS   | Liaison Statement                   |
+
+# --- 4 Application identifiers
+
+The Diameter applications are identified with the application identifiers as specified in the RFC 3588 [9]. There are two kind of applications: IETF standards track applications and vendor specific applications. All application identifiers are assigned by IANA [12]. This chapter lists the application identifiers assigned by IANA to all 3GPP Diameter applications.
+
+The application identifiers are transferred in Diameter command's header in the Application-ID field.
+
+## 4.1 3GPP specific application identifiers
+
+The 3GPP specific application identifiers allocated by IANA are listed in the following table.
+
+Table 4.1: 3GPP specific application identifiers
+
+| Application identifier | Application                   | 3GPP TS                   |
+|------------------------|-------------------------------|---------------------------|
+| 16777216               | 3GPP Cx/Px                    | 29.228 [1] and 29.229 [2] |
+| 16777217               | 3GPP Sh/Ph                    | 29.328 [3] and 29.329 [4] |
+| 16777218               | 3GPP Re                       | 32.296 [14]               |
+| 16777219               | 3GPP Wx                       | 29.234 [6]                |
+| 16777220               | 3GPP Zn                       | 29.109 [7]                |
+| 16777221               | 3GPP Zh                       | 29.109 [7]                |
+| 16777222               | 3GPP Gq                       | 29.209 [8]                |
+| 16777223               | 3GPP Gmb                      | 29.061 [13]               |
+| 16777224               | 3GPP Gx                       | 29.210 [15]               |
+| 16777225               | 3GPP Gx over Gy               | 29.210 [15]               |
+| 16777226               | 3GPP MM10                     | 29.140 [16]               |
+| 16777229               | 3GPP Rx                       | 29.211 [17]               |
+| 16777230               | 3GPP Pr                       | 29.234 [6]                |
+| 16777236               | 3GPP Rx                       | 29.214 [18]               |
+| 16777238               | 3GPP Gx                       | 29.212 [19]               |
+| 16777250               | 3GPP STa                      | 29.273 [20]               |
+| 16777251               | 3GPP S6a                      | 29.272 [21]               |
+| 16777252               | 3GPP S13/S13'                 | 29.272 [21]               |
+| 16777255               | 3GPP SLg                      | 29.172 [24]               |
+| 16777264               | 3GPP SWm                      | 29.273 [20]               |
+| 16777265               | 3GPP SWx                      | 29.273 [20]               |
+| 16777266               | 3GPP Gxx                      | 29.212 [19]               |
+| 16777267               | 3GPP S9                       | 29.215 [22]               |
+| 16777268               | 3GPP Zpn                      | 29.109 [7]                |
+| 16777272               | 3GPP S6b                      | 29.273 [20]               |
+| 16777291               | 3GPP SLh                      | 29.173 [25]               |
+| 16777292               | 3GPP SGmb                     | 29.061 [13]               |
+| 16777302               | 3GPP Sy                       | 29.219 [26]               |
+| 16777303               | 3GPP Sd                       | 29.212 [19]               |
+| 16777308               | 3GPP S7a                      | 29.272 [21]               |
+| 16777309               | 3GPP Tsp                      | 29.368 [27]               |
+| 16777310               | 3GPP S6m                      | 29.336 [28]               |
+| 16777311               | 3GPP T4                       | 29.337 [29]               |
+| 16777312               | 3GPP S6c                      | 29.338 [30]               |
+| 16777313               | 3GPP SGd                      | 29.338 [30]               |
+| 16777318               | 3GPP S15                      | 29.212 [19]               |
+| 16777319               | 3GPP S9a                      | 29.215 [22]               |
+| 16777320               | 3GPP S9a*                     | 29.215 [22]               |
+| 16777335               | 3GPP MB2-C                    | 29.468 [31]               |
+| 16777336               | 3GPP PC4a                     | 29.344 [33]               |
+| 16777337               | 3GPP PC2                      | 29.343 [32]               |
+| 16777340               | 3GPP PC6/PC7                  | 29.345 [34]               |
+| 16777342               | 3GPP Np                       | 29.217 [35]               |
+| 16777345               | 3GPP S6t                      | 29.336 [28]               |
+| 16777346               | 3GPP T6a/T6b                  | 29.128 [36]               |
+| 16777347               | 3GPP Ns                       | 29.153[37]                |
+| 16777348               | 3GPP Nt                       | 29.154[38]                |
+| 16777349               | 3GPP St                       | 29.212 [19]               |
+| 16777350               | 3GPP PC2                      | 29.343 [32]               |
+| 16777351               | 3GPP Diameter Data Management | 29.283 [39]               |
+| 16777355               | 3GPP V4                       | 29.388 [40]               |
+| 16777356               | 3GPP V6                       | 29.389 [41]               |
+| 16777358               | 3GPP Nta                      | 29.154 [38]               |
+
+# 5 Command codes
+
+The command codes are used for communicating the command associated with the Diameter message. The command code is carried in the Diameter header's Command-Code field. The command codes can be divided into standard command codes allocated by IANA and experimental command codes for testing purposes only.
+
+## 5.1 Command codes allocated for 3GPP
+
+Based on the IETF RFC 3589 [10] the IANA has allocated a standard command code range 300 - 313 for 3GPP. The command codes are presented in the following table.
+
+**Table 5.1/1: Command code values allocated for 3GPP**
+
+| Command code value | Command name                             | Abbreviation | Specified in 3GPP TS |
+|--------------------|------------------------------------------|--------------|----------------------|
+| 300                | User-Authorization-Request/-Answer       | UAR/UAA      | 29.229 [2]           |
+| 301                | Server-Assignment-Request/-Answer        | SAR/SAA      |                      |
+| 302                | Location-Info-Request/-Answer            | LIR/LIA      |                      |
+| 303                | Multimedia-Auth-Request/-Answer          | MAR/MAA      |                      |
+| 304                | Registration-Termination-Request/-Answer | RTR/RTA      |                      |
+| 305                | Push-Profile-Request/-Answer             | PPR/PPA      | 29.329 [4]           |
+| 306                | User-Data-Request/-Answer                | UDR/UDA      |                      |
+| 307                | Profile-Update-Request/-Answer           | PUR/PUA      |                      |
+| 308                | Subscribe-Notifications-Request/-Answer  | SNR/SNA      |                      |
+| 309                | Push-Notification-Request/-Answer        | PNR/PNA      |                      |
+| 310                | Boostrapping-Info-Request/Answer         | BIR/BIA      | 29.109 [7]           |
+| 311                | Message-Process-Request/Answer           | MPR/MPA      | 29.140 [16]          |
+| 312                | GBAPush-Info-Request/Answer              | GPR/GPI      | 29.109 [7]           |
+
+**Editor's Note:** The following command codes have been allocated to 3GPP, but they have not been used yet.
+
+**Table 5.1/2: Command codes allocated for 3GPP**
+
+| Command code value | Command name | Abbreviation | Specified in 3GPP TS |
+|--------------------|--------------|--------------|----------------------|
+| 313                |              |              |                      |
+
+As defined in the IETF RFC 5516 [23], IANA has allocated the following command code values for the S6a/S6d interface application and S13/S13' interface application.
+
+**Table 5.1/3: SAE related Standard Command code values allocated for 3GPP**
+
+| Command code value | Command name                                 | Abbreviation | Specified in 3GPP TS |
+|--------------------|----------------------------------------------|--------------|----------------------|
+| 316                | Update-Location-Request/Answer               | ULR/ULA      | 29.272 [21]          |
+| 317                | Cancel-Location-Request/Answer               | CLR/CLA      |                      |
+| 318                | Authentication- Information - Request/Answer | AIR/AIA      |                      |
+| 319                | Insert Subscriber Data-Request/Answer        | IDR/IDA      |                      |
+| 320                | Delete-Subscriber-Data-Request/Answer        | DSR/DSA      |                      |
+| 321                | Purge-UE-Request/Answer                      | PUR/PUA      |                      |
+| 322                | Reset-Request/Answer                         | RSR/RSA      |                      |
+| 323                | Notify-Request/Answer                        | NOR/NOA      |                      |
+| 324                | ME-Identity-Check-Request/Answer             | ECR/ECA      |                      |
+
+Besides the standard command code values allocated for 3GPP, IANA has allocated the following vendor-specific command code values for 3GPP vendor-specific Diameter applications:
+
+Table 5.1/4: Vendor-specific command codes allocated for 3GPP
+
+| Command code value | Command name                                      | Abbreviation | Specified in 3GPP TS |
+|--------------------|---------------------------------------------------|--------------|----------------------|
+| 8388620            | Provide-Location-Request/Answer                   | PLR/PLA      | 29.172 [24]          |
+| 8388621            | Location-Report-Request/Answer                    | LRR/LRA      |                      |
+| 8388622            | LCS-Routing-Info-Request/Answer                   | RIR/RIA      | 29.173 [25]          |
+| 8388635            | Spending-Limit-Request/Answer                     | SLR/SLA      | 29.219 [26]          |
+| 8388636            | Spending-Status-Notification-Request/Answer       | SNR/SNA      |                      |
+| 8388637            | TDF-Session-Request/Answer                        | TSR/TSA      | 29.212 [19]          |
+| 8388731            | TSSF-Notification-Request/Answer                  | TNR/TNA      |                      |
+| 8388638            | Update-VCSG-Location-Request/Answer               | UVR/UVA      | 29.272 [21]          |
+| 8388642            | Cancel-VCSG-Location-Request/Answer               | CVR/CVA      |                      |
+| 8388639            | Device-Action-Request/Answer                      | DAR/DAA      | 29.368 [27]          |
+| 8388640            | Device-Notification-Request/Answer                | DNR/DNA      |                      |
+| 8388641            | Subscriber-Information-Request/Answer             | SIR/SIA      | 29.336 [28]          |
+| 8388718            | Configuration-Information-Request/Answer          | CIR/CIA      | 29.336 [28]          |
+| 8388719            | Reporting-Information-Request/Answer              | RIR/RIA      |                      |
+| 8388726            | NIDD-Information-Request/Answer                   | NIR/NIA      |                      |
+| 8388643            | Device-Trigger-Request/Answer                     | DTR/DTA      | 29.337 [29]          |
+| 8388644            | Delivery-Report-Request/Answer                    | DRR/DRA      |                      |
+| 8388645            | MO-Forward-Short-Message Request/Answer           | OFR/OFA      | 29.338 [30]          |
+| 8388646            | MT-Forward-Short-Message Request/Answer           | TFR/TFA      |                      |
+| 8388647            | Send-Routing-Info-for-SM-Request/Answer           | SRR/SRA      |                      |
+| 8388648            | Alert-Service-Centre-Request/Answer               | ALR/ALA      |                      |
+| 8388649            | Report-SM-Delivery-Status-Request/Answer          | RDR/RDA      |                      |
+| 8388656            | Trigger-Establishment-Request/Answer              | TER/TEA      | 29.215 [30]          |
+| 8388662            | GCS-Action-Request/Answer                         | GAR/GAA      | 29.468 [31]          |
+| 8388663            | GCS-Notification-Request/Answer                   | GNR/GNA      |                      |
+| 8388664            | ProSe-Subscriber-Information-Request/Answer       | PIR/PIA      | 29.344 [33]          |
+| 8388665            | Update-ProSe-Subscriber-Data-Request/Answer       | UPR/UPA      |                      |
+| 8388666            | ProSe-Notify-Request/Answer                       | PNR/PNA      |                      |
+| 8388713            | ProSe-Initial-Location-Information-Request/Answer | PSR/PSA      |                      |
+| 8388668            | ProSe-Authorization-Request/Answer                | PAR/PAA      | 29.345 [34]          |
+| 8388669            | ProSe-Discovery-Request/Answer                    | PDR/PDA      |                      |
+
+|         |                                                 |         |             |
+|---------|-------------------------------------------------|---------|-------------|
+| 8388670 | ProSe-Match-Request/Answer                      | PMR/PMA | 29.343 [32] |
+| 8388671 | ProSe-Match-Report-Info-Request/Answer          | PIR/PIA |             |
+| 8388672 | ProSe-Proximity-Request/Answer                  | PRR/PRA |             |
+| 8388673 | ProSe-Location-Update-Request/Answer            | PLR/PLA |             |
+| 8388674 | ProSe-Alert-Request/Answer                      | ALR/ALA |             |
+| 8388675 | ProSe-Cancellation-Request/Answer               | RPR/RPA |             |
+| 8388676 | ProXimity-Action-Request/Answer                 | PXR/PXA |             |
+| 8388727 | ProXimity-Application-Request/Answer            | XAR/XAA |             |
+| 8388720 | Non-Aggregated-RUCI-Report-Request/Answer       | NRR/NRA | 29.217 [35] |
+| 8388721 | Aggregated-RUCI-Report-Request/Answer           | ARR/ARA |             |
+| 8388722 | Modify-Uecontext-Request/Answer                 | MUR/MUA |             |
+| 8388724 | Network-Status-Request/Answer                   | NSR/NSA | 29.153 [37] |
+| 8388725 | Network-Status-Continuous-Report-Request/Answer | NCR/NCA |             |
+| 8388723 | Background-Data-Transfer-Request/Answer         | BTR/BTA | 29.154 [38] |
+| 8388728 | Data-Pull-Request/Answer                        | DPR/DPA | 29.283 [39] |
+| 8388729 | Data-Update-Request/Answer                      | DUR/DUA |             |
+| 8388730 | Notification-Data-Request/Answer                | NDR/NDA |             |
+| 8388732 | Connection-Management-Request/Answer            | CMR/CMA | 29.128 [36] |
+| 8388733 | MO-Data-Request/Answer                          | ODR/ODA |             |
+| 8388734 | MT-Data-Request/Answer                          | TDR/TDA |             |
+| 8388735 | Event-Configuration-Request/Answer              | ECR/ECA | 29.154 [38] |
+| 8388736 | Event-Reporting-Request/Answer                  | ERR/ERA |             |
+
+# 6 Vendor identifier
+
+The vendor identifier (also known as Enterprise number) indicates the vendor specific attributes, result codes and application identifiers in Diameter commands. The vendor identifier is used in the Vendor-ID field of the AVP header and in the Vendor-Id AVP. The Vendor-Id AVP is used to identify the vendor in the Vendor-Specific-Application-Id and Experimental-Result-Code grouped AVPs.
+
+## 6.1 3GPP's vendor identifier
+
+The IANA has allocated a vendor identifier value 10415 for 3GPP [11].
+
+# --- 7 Attribute-Value-Pair codes
+
+The AVP codes are used together with the vendor identifier to identify each attribute uniquely. There are multiple AVP namespaces. The IETF IANA namespace, that is, the AVPs with vendor identifier zero or without vendor identifier, is controlled by IANA. Each vendor controls the AVP codes within their AVP namespaces.
+
+## 7.1 3GPP specific AVP codes
+
+The 3GPP specific AVPs have the Vendor-Specific bit ('V' bit) set in the AVP header and they carry the 3GPP's vendor identifier in the Vendor-ID field of the AVP header. The 3GPP specific AVP codes are presented in the following table.
+
+**Table 7.1: 3GPP specific AVP codes**
+
+| AVP Code                                                                                                                                                                                     | Attribute Name                           | Data Type        | Specified in the 3GPP TS             |  |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------|--------------------------------------|--|
+| 100                                                                                                                                                                                          | 3GPP-WLAN-APN-Id                         | OctetString      |                                      |  |
+| 101                                                                                                                                                                                          | 3GPP-WLAN-QoS-Filter-Rule                | UTF8String       | 29.234 [6]                           |  |
+| 102                                                                                                                                                                                          | 3GPP-WLAN-QoS-Filter-Support             | OctetString      |                                      |  |
+| Note: The AVP codes from 1 to 255 are reserved for backwards compatibility with 3GPP RADIUS Vendor Specific Attributes (See 3GPP TS 29.061 [13], 3GPP TS 29.561 [42] and 3GPP TS 29.234 [6]) |                                          |                  |                                      |  |
+| Note: The AVP codes from 256 to 299 are reserved for future use.                                                                                                                             |                                          |                  |                                      |  |
+| 300                                                                                                                                                                                          | Authentication-Method                    | Enumerated       | 29.234 [6]                           |  |
+| 301                                                                                                                                                                                          | Authentication-Information-SIM           | OctetString      |                                      |  |
+| 302                                                                                                                                                                                          | Authorization -Information-SIM           | OctetString      |                                      |  |
+| 303                                                                                                                                                                                          | WLAN-User-Data                           | Grouped          |                                      |  |
+| 304                                                                                                                                                                                          | Charging-Data                            | Grouped          |                                      |  |
+| 305                                                                                                                                                                                          | WLAN-Access                              | Enumerated       |                                      |  |
+| 306                                                                                                                                                                                          | WLAN- 3GPP-IP-Access                     | Enumerated       |                                      |  |
+| 307                                                                                                                                                                                          | APN-Authorized                           | Grouped          |                                      |  |
+| 308                                                                                                                                                                                          | APN-Id                                   |                  |                                      |  |
+| 309                                                                                                                                                                                          | APN-Barring-Type                         | Enumerated       |                                      |  |
+| 310                                                                                                                                                                                          | WLAN-Direct-IP-Access                    | Enumerated       |                                      |  |
+| 311                                                                                                                                                                                          | Session-Request-Type                     | Enumerated       |                                      |  |
+| 312                                                                                                                                                                                          | Routing-Policy                           | IPFilterRule     |                                      |  |
+| 313                                                                                                                                                                                          | Max-Requested-Bandwidth                  | OctetString      |                                      |  |
+| 314                                                                                                                                                                                          | Charging-Characteristics                 | Integer          |                                      |  |
+| 315                                                                                                                                                                                          | Charging-Nodes                           | Grouped          |                                      |  |
+| 316                                                                                                                                                                                          | Primary-OCS-Charging-Function-Name       | DiameterIdentity |                                      |  |
+| 317                                                                                                                                                                                          | Secondary-OCS-Charging-Function-Name     | DiameterIdentity |                                      |  |
+| 318                                                                                                                                                                                          | 3GPP-AAA-Server-Name                     | DiameterIdentity |                                      |  |
+| 319                                                                                                                                                                                          | Maximum-Number-Accesses                  | Unsigned32       |                                      |  |
+| Note 1: The AVP codes from 320 to 399 are reserved for TS 29.234                                                                                                                             |                                          |                  |                                      |  |
+| Note 2: The 3GPP-AAA-Server-Name definition is moved to TS 29.273 starting from Rel-12.                                                                                                      |                                          |                  |                                      |  |
+| 400                                                                                                                                                                                          | GBA-UserSecSettings                      | OctetString      | 29.109 [7]                           |  |
+| 401                                                                                                                                                                                          | Transaction-Identifier                   | OctetString      |                                      |  |
+| 402                                                                                                                                                                                          | NAF-Hostname                             | OctetString      |                                      |  |
+| 403                                                                                                                                                                                          | GAA-Service-Identifier                   | OctetString      |                                      |  |
+| 404                                                                                                                                                                                          | Key-ExpiryTime                           | Time             |                                      |  |
+| 405                                                                                                                                                                                          | ME-Key-Material                          | OctetString      |                                      |  |
+| 406                                                                                                                                                                                          | UICC-Key-Material                        | OctetString      |                                      |  |
+| 407                                                                                                                                                                                          | GBA_U-Awareness-Indicator                | Enumerated       |                                      |  |
+| 408                                                                                                                                                                                          | BootstrapInfoCreationTime                | Time             |                                      |  |
+| 409                                                                                                                                                                                          | GUSS-Timestamp                           | Time             |                                      |  |
+| 410                                                                                                                                                                                          | GBA-Type                                 | Enumerated       |                                      |  |
+| 411                                                                                                                                                                                          | UE-Id                                    | OctetString      |                                      |  |
+| 412                                                                                                                                                                                          | UE-Id-Type                               | Enumerated       |                                      |  |
+| 413                                                                                                                                                                                          | UICC-App-Label                           | OctetString      |                                      |  |
+| 414                                                                                                                                                                                          | UICC-ME                                  | Enumerated       |                                      |  |
+| 415                                                                                                                                                                                          | Requested-Key-Lifetime                   | Time             |                                      |  |
+| 416                                                                                                                                                                                          | Private-Identity-Request                 | Enumerated       |                                      |  |
+| 417                                                                                                                                                                                          | GBA-Push-Info                            | OctetString      |                                      |  |
+| 418                                                                                                                                                                                          | NAF-SA-Identifier                        | OctetString      |                                      |  |
+| 419                                                                                                                                                                                          | Security-Feature-Request                 | OctetString      |                                      |  |
+| 420                                                                                                                                                                                          | Security-Feature-Response                | OctetString      |                                      |  |
+| Note: The AVP codes from 421 to 499 are reserved for TS 29.109                                                                                                                               |                                          |                  |                                      |  |
+| 500                                                                                                                                                                                          | Abort-Cause                              | Enumerated       | 29.209 [8], 29.211 [17], 29.214 [18] |  |
+| 501                                                                                                                                                                                          | Access-Network-Charging-Address          | Address          |                                      |  |
+| 502                                                                                                                                                                                          | Access-Network-Charging-Identifier       | Grouped          |                                      |  |
+| 503                                                                                                                                                                                          | Access-Network-Charging-Identifier-Value | OctetString      |                                      |  |
+| 504                                                                                                                                                                                          | AF-Application-Identifier                | OctetString      |                                      |  |
+| 505                                                                                                                                                                                          | AF-Charging-Identifier                   | OctetString      |                                      |  |
+| 506                                                                                                                                                                                          | Authorization-Token                      | OctetString      |                                      |  |
+
+|     |                                       |              |
+|-----|---------------------------------------|--------------|
+| 507 | Flow-Description                      | IPFilterRule |
+| 508 | Flow-Grouping                         | Grouped      |
+| 509 | Flow-Number                           | Unsigned32   |
+| 510 | Flows                                 | Grouped      |
+| 511 | Flow-Status                           | Enumerated   |
+| 512 | Flow-Usage                            | Enumerated   |
+| 513 | Specific-Action                       | Enumerated   |
+| 514 | Max-Requested-Bandwidth               | Unsigned32   |
+| 515 | Max-Requested-Bandwidth-DL            | Unsigned32   |
+| 516 | Max-Requested-Bandwidth-UL            | Unsigned32   |
+| 517 | Media-Component-Description           | Grouped      |
+| 518 | Media-Component-Number                | Unsigned32   |
+| 519 | Media-Sub-Component AVP               | Grouped      |
+| 520 | Media-Type                            | Enumerated   |
+| 521 | RR-Bandwidth                          | Unsigned32   |
+| 522 | RS-Bandwidth                          | Unsigned32   |
+| 523 | SIP-Forking-Indication                | Enumerated   |
+| 524 | Codec-Data                            | OctetString  |
+| 525 | Service-URN                           | OctetString  |
+| 526 | Acceptable-Service-Info               | Grouped      |
+| 527 | Service-Info-Status                   | Enumerated   |
+| 528 | MPS-Identifier                        | OctetString  |
+| 529 | AF-Signalling-Protocol                | Enumerated   |
+| 530 | Sponsored-Connectivity-Data           | Grouped      |
+| 531 | Sponsor-Identity                      | OctetString  |
+| 532 | Application-Service-Provider-Identity | OctetString  |
+| 533 | Rx-Request-Type                       | Enumerated   |
+| 534 | Min-Requested-Bandwidth-DL            | Unsigned32   |
+| 535 | Min-Requested-Bandwidth-UL            | Unsigned32   |
+| 536 | Required-Access-Info                  | Enumerated   |
+| 537 | IP-Domain-Id                          | OctetString  |
+| 538 | GCS-Identifier                        | OctetString  |
+| 539 | Sharing-Key-DL                        | Unsigned32   |
+| 540 | Sharing-Key-UL                        | Unsigned32   |
+| 541 | Retry-Interval                        | Unsigned32   |
+| 542 | Sponsoring-Action                     | Enumerated   |
+| 543 | Max-Supported-Bandwidth-DL            | Unsigned32   |
+| 544 | Max-Supported-Bandwidth-UL            | Unsigned32   |
+| 545 | Min-Desired-Bandwidth-DL              | Unsigned32   |
+| 546 | Min-Desired-Bandwidth-UL              | Unsigned32   |
+| 547 | MCPTT-Identifier                      | OctetString  |
+| 548 | Service-Authorization-Info            | Unsigned32   |
+| 549 | Media-Component-Status                | Unsigned32   |
+| 550 | Priority-Sharing-Indicator            | Enumerated   |
+| 551 | AF-Requested-Data                     | Unsigned32   |
+| 552 | Content-Version                       | Unsigned64   |
+| 553 | Pre-emption-Control-Info              | Unsigned32   |
+| 554 | Extended-Max-Requested-BW-DL          | Unsigned32   |
+| 555 | Extended-Max-Requested-BW-UL          | Unsigned32   |
+| 556 | Extended-Max-Supported-BW-DL          | Unsigned32   |
+| 557 | Extended-Max-Supported-BW-UL          | Unsigned32   |
+| 558 | Extended-Min-Desired-BW-DL            | Unsigned32   |
+| 559 | Extended-Min-Desired-BW-UL            | Unsigned32   |
+| 560 | Extended-Min-Requested-BW-DL          | Unsigned32   |
+| 561 | Extended-Min-Requested-BW-UL          | Unsigned32   |
+| 562 | MCVideo-Identifier                    | OctetString  |
+| 563 | IMS-Content-Identifier                | OctetString  |
+| 564 | IMS-Content-Type                      | Enumerated   |
+| 565 | Callee-Information                    | Grouped      |
+| 566 | FLUS-Identifier                       | OctetString  |
+| 567 | Desired-Max-Latency                   | Float32      |
+| 568 | Desired-Max-Loss                      | Float32      |
+| 569 | NID                                   | OctetString  |
+| 570 | MA-Information                        | Grouped      |
+| 571 | MA-Information-Action                 | Unsigned32   |
+
+|                                                                                         |                                             |             |            |
+|-----------------------------------------------------------------------------------------|---------------------------------------------|-------------|------------|
+| 572                                                                                     | 5GS-RAN-NAS-Release-Cause                   | Grouped     |            |
+| 573                                                                                     | 5GMM-Cause                                  | Unsigned32  |            |
+| 574                                                                                     | 5GSM-Cause                                  | Unsigned32  |            |
+| 575                                                                                     | NGAP-Cause                                  | Grouped     |            |
+| 576                                                                                     | NGAP-Group                                  | Unsigned32  |            |
+| 577                                                                                     | NGAP-Value                                  | Unsigned32  |            |
+| 578                                                                                     | Wireline-User-Location-Info                 | Grouped     |            |
+| 579                                                                                     | HFC-Node-Identifier                         | OctetString |            |
+| 580                                                                                     | GLI-Identifier                              | OctetString |            |
+| 581                                                                                     | Line-Type                                   | Unsigned32  |            |
+| Note: The AVP codes from 582 to 599 are reserved for TS 29.209, TS 29.211 and TS 29.214 |                                             |             |            |
+| 600                                                                                     | Visited-Network-Identifier                  | OctetString |            |
+| 601                                                                                     | Public-Identity                             | UTF8String  |            |
+| 602                                                                                     | Server-Name                                 | UTF8String  |            |
+| 603                                                                                     | Server-Capabilities                         | Grouped     |            |
+| 604                                                                                     | Mandatory-Capability                        | Unsigned32  |            |
+| 605                                                                                     | Optional-Capability                         | Unsigned32  |            |
+| 606                                                                                     | User-Data                                   | OctetString |            |
+| 607                                                                                     | SIP-Number-Auth-Items                       | Unsigned32  |            |
+| 608                                                                                     | SIP-Authentication-Scheme                   | UTF8String  |            |
+| 609                                                                                     | SIP-Authenticate                            | OctetString |            |
+| 610                                                                                     | SIP-Authorization                           | OctetString |            |
+| 611                                                                                     | SIP-Authentication-Context                  | OctetString |            |
+| 612                                                                                     | SIP-Auth-Data-Item                          | Grouped     |            |
+| 613                                                                                     | SIP-Item-Number                             | Unsigned32  |            |
+| 614                                                                                     | Server-Assignment-Type                      | Enumerated  |            |
+| 615                                                                                     | Deregistration-Reason                       | Grouped     |            |
+| 616                                                                                     | Reason-Code                                 | Enumerated  |            |
+| 617                                                                                     | Reason-Info                                 | UTF8String  |            |
+| 618                                                                                     | Charging-Information                        | Grouped     |            |
+| 619                                                                                     | Primary-Event-Charging-Function-Name        | DiameterURI |            |
+| 620                                                                                     | Secondary-Event-Charging-Function-Name      | DiameterURI |            |
+| 621                                                                                     | Primary-Charging-Collection-Function-Name   | DiameterURI |            |
+| 622                                                                                     | Secondary-Charging-Collection-Function-Name | DiameterURI |            |
+| 623                                                                                     | User-Authorization-Type                     | Enumerated  |            |
+| 624                                                                                     | User-Data-Already-Available                 | Enumerated  |            |
+| 625                                                                                     | Confidentiality-Key                         | OctetString |            |
+| 626                                                                                     | Integrity-Key                               | OctetString |            |
+| 627                                                                                     | User-Data-Request-Type                      | Enumerated  | 29.229 [2] |
+| 628                                                                                     | Supported-Features                          | Grouped     |            |
+| 629                                                                                     | Feature-List-ID                             | Unsigned32  |            |
+| 630                                                                                     | Feature-List                                | Unsigned32  |            |
+| 631                                                                                     | Supported-Applications                      | Grouped     |            |
+| 632                                                                                     | Associated-Identities                       | Grouped     |            |
+| 633                                                                                     | Originating-Request                         | Enumerated  |            |
+| 634                                                                                     | Wildcarded-Public-Identity                  | UTF8String  |            |
+| 635                                                                                     | SIP-Digest-Authenticate                     | Grouped     |            |
+| 636                                                                                     | Wildcarded-IMPU                             | UTF8String  |            |
+| 637                                                                                     | UAR-Flags                                   | Unsigned32  |            |
+| 638                                                                                     | Loose-Route-Indication                      | Enumerated  |            |
+| 639                                                                                     | SCSCF-Restoration-Info                      | Grouped     |            |
+| 640                                                                                     | Path                                        | OctetString |            |
+| 641                                                                                     | Contact                                     | OctetString |            |
+| 642                                                                                     | Subscription-Info                           | Grouped     |            |
+| 643                                                                                     | Call-ID-SIP-Header                          | OctetString |            |
+| 644                                                                                     | From-SIP-Header                             | OctetString |            |
+| 645                                                                                     | To-SIP-Header                               | OctetString |            |
+| 646                                                                                     | Record-Route                                | OctetString |            |
+| 647                                                                                     | Associated-Registered-Identities            | Grouped     |            |
+| 648                                                                                     | Multiple-Registration-Indication            | Enumerated  |            |
+| 649                                                                                     | Restoration-Info                            | Grouped     |            |
+| 650                                                                                     | Session-Priority                            | Enumerated  |            |
+| 651                                                                                     | Identity-with-Emergency-Registration        | Grouped     |            |
+| 652                                                                                     | Privileged-Sender-Indication                | Enumerated  |            |
+| 653                                                                                     | LIA-Flags                                   | Unsigned32  |            |
+
+|                                                                 |                                           |             |            |
+|-----------------------------------------------------------------|-------------------------------------------|-------------|------------|
+| 654                                                             | Initial-CSeq-Sequence-Number              | Unsigned32  |            |
+| 655                                                             | SAR-Flags                                 | Unsigned32  |            |
+| 656                                                             | Allowed-WAF-WWSF-Identities               | Grouped     |            |
+| 657                                                             | WebRTC-Authentication-Function-Name       | UTF8String  |            |
+| 658                                                             | WebRTC-Web-Server-Function-Name           | UTF8String  |            |
+| 659                                                             | RTR-Flags                                 | Unsigned32  |            |
+| 660                                                             | P-CSCF-Subscription-Info                  | Grouped     |            |
+| 661                                                             | Registration-Time-Out                     | Time        |            |
+| Note: The AVP codes from 662 to 699 are reserved for TS 29.229. |                                           |             |            |
+| 700                                                             | User-Identity                             | Grouped     |            |
+| 701                                                             | MSISDN                                    | OctetString |            |
+| 702                                                             | User-Data                                 | OctetString |            |
+| 703                                                             | Data-Reference                            | Enumerated  |            |
+| 704                                                             | Service-Indication                        | OctetString |            |
+| 705                                                             | Subs-Req-Type                             | Enumerated  |            |
+| 706                                                             | Requested-Domain                          | Enumerated  |            |
+| 707                                                             | Current-Location                          | Enumerated  |            |
+| 708                                                             | Identity-Set                              | Enumerated  |            |
+| 709                                                             | Expiry-Time                               | Time        |            |
+| 710                                                             | Send-Data-Indication                      | Enumerated  |            |
+| 711                                                             | DSAI-Tag                                  | OctetString | 29.329 [4] |
+| 712                                                             | One-Time-Notification                     | Enumerated  |            |
+| 713                                                             | Requested-Nodes                           | Unsigned32  |            |
+| 714                                                             | Serving-Node-Indication                   | Enumerated  |            |
+| 715                                                             | Repository-Data-ID                        | Grouped     |            |
+| 716                                                             | Sequence-Number                           | Unsigned32  |            |
+| 717                                                             | Pre-paging-Supported                      | Enumerated  |            |
+| 718                                                             | Local-Time-Zone-Indication                | Enumerated  |            |
+| 719                                                             | UDR-Flags                                 | Unsigned32  |            |
+| 720                                                             | Call-Reference-Info                       | Grouped     |            |
+| 721                                                             | Call-Reference-Number                     | OctetString |            |
+| 722                                                             | AS-Number                                 | OctetString |            |
+| Note: The AVP codes from 723 to 799 are reserved for TS 29.329. |                                           |             |            |
+| Note: The AVP codes from 800 to 822 are reserved for TS 32.299. |                                           |             |            |
+| 823                                                             | Event-Type                                | Grouped     |            |
+| 824                                                             | SIP-Method                                | UTF8String  |            |
+| 825                                                             | Event                                     | UTF8String  |            |
+| 826                                                             | Content-Type                              | UTF8String  |            |
+| 827                                                             | Content-Length                            | Unsigned32  |            |
+| 828                                                             | Content-Disposition                       | UTF8String  |            |
+| 829                                                             | Role-of-Node                              | Enumerated  |            |
+| 830                                                             | User-Session-Id                           | UTF8String  |            |
+| 831                                                             | Calling-Party-Address                     | UTF8String  |            |
+| 832                                                             | Called-Party-Address                      | UTF8String  |            |
+| 833                                                             | Time-Stamps                               | Grouped     |            |
+| 834                                                             | SIP-Request-Timestamp                     | Time        |            |
+| 835                                                             | SIP-Response-Timestamp                    | Time        |            |
+| 836                                                             | Application-Server                        | UTF8String  |            |
+| 837                                                             | Application-provided-called-party-address | UTF8String  |            |
+| 838                                                             | Inter-Operator-Identifier                 | Grouped     | 32.299 [5] |
+| 839                                                             | Originating-IOI                           | UTF8String  |            |
+| 840                                                             | Terminating-IOI                           | UTF8String  |            |
+| 841                                                             | IMS-Charging-Identifier                   | UTF8String  |            |
+| 842                                                             | SDP-Session-Description                   | UTF8String  |            |
+| 843                                                             | SDP-Media-Component                       | Grouped     |            |
+| 844                                                             | SDP-Media-Name                            | UTF8String  |            |
+| 845                                                             | SDP-Media-Description                     | UTF8String  |            |
+| 846                                                             | CG-Address                                | Address     |            |
+| 847                                                             | GGSN-Address                              | Address     |            |
+| 848                                                             | Served-Party-IP-Address                   | Address     |            |
+| 849                                                             | Authorized-QoS                            | UTF8String  |            |
+| 850                                                             | Application-Server-Information            | Grouped     |            |
+| 851                                                             | Trunk-Group-Id                            | Grouped     |            |
+| 852                                                             | Incoming-Trunk-Group-Id                   | UTF8String  |            |
+| 853                                                             | Outgoing-Trunk-Group-Id                   | UTF8String  |            |
+
+|     |                                         |             |                |
+|-----|-----------------------------------------|-------------|----------------|
+| 854 | Bearer-Service                          | OctetString |                |
+| 855 | Service-Id                              | UTF8String  |                |
+| 856 | Associated-URI                          | UTF8String  |                |
+| 857 | Charged-Party                           | UTF8String  |                |
+| 858 | PoC-Controlling-Address                 | UTF8String  |                |
+| 859 | PoC-Group-Name                          | UTF8String  |                |
+| 860 | Cause                                   | Grouped     |                |
+| 861 | Cause-Code                              | Integer32   |                |
+| 862 | Node-Functionality                      | Enumerated  |                |
+| 863 | Service-Specific-Data                   | UTF8String  |                |
+| 864 | Originator                              | Enumerated  |                |
+| 865 | PS-Furnish-Charging-Information         | Grouped     |                |
+| 866 | PS-Free-Format-Data                     | OctetString |                |
+| 867 | PS-Append-Free-Format-Data              | Enumerated  |                |
+| 868 | Time-Quota-Threshold                    | Unsigned32  |                |
+| 869 | Volume-Quota-Threshold                  | Unsigned32  |                |
+| 870 | Trigger-Type                            | Enumerated  |                |
+| 871 | Quota-Holding-Time                      | Unsigned32  |                |
+| 872 | Reporting-Reason                        | Enumerated  |                |
+| 873 | Service-Information                     | Grouped     |                |
+| 874 | PS-Information                          | Grouped     |                |
+| 875 | Reserved                                | -           |                |
+| 876 | IMS-Information                         | Grouped     |                |
+| 877 | MMS-Information                         | Grouped     |                |
+| 878 | LCS-Information                         | Grouped     |                |
+| 879 | PoC-Information                         | Grouped     |                |
+| 880 | MBMS-Information                        | Grouped     |                |
+| 881 | Quota-Consumption-Time                  | Unsigned32  |                |
+| 882 | Media-Initiator-Flag                    | Enumerated  |                |
+| 883 | PoC-Server-Role                         | Enumerated  |                |
+| 884 | PoC-Session-Type                        | Enumerated  |                |
+| 885 | Number-Of-Participants                  | Unsigned32  |                |
+| 886 | Originator-Address                      | Grouped     |                |
+| 887 | Participants-Involved                   | UTF8String  |                |
+| 888 | Expires                                 | Unsigned32  |                |
+| 889 | Message-Body                            | Grouped     |                |
+| 890 | Reserved                                | -           |                |
+| 891 | Reserved                                | -           |                |
+| 892 | Reserved                                | -           |                |
+| 893 | Reserved                                | -           |                |
+| 894 | Reserved                                | -           |                |
+| 895 | Reserved                                | -           |                |
+| 896 | Reserved                                | -           |                |
+| 897 | Address-Data                            | UTF8String  |                |
+| 898 | Address-Domain                          | Grouped     |                |
+| 899 | Address-Type                            | Enumerated  |                |
+| 900 | TMGI                                    | OctetString | 29.061<br>[13] |
+| 901 | Required-MBMS-Bearer-Capabilities       | UTF8String  |                |
+| 902 | MBMS-StartStop-Indication               | Enumerated  |                |
+| 903 | MBMS-Service-Area                       | OctetString |                |
+| 904 | MBMS-Session-Duration                   | Unsigned32  |                |
+| 905 | Alternative-APN                         | UTF8String  |                |
+| 906 | MBMS-Service-Type                       | Enumerated  |                |
+| 907 | MBMS-2G-3G-Indicator                    | Enumerated  |                |
+| 908 | MBMS-Session-Identity                   | OctetString |                |
+| 909 | RAI                                     | UTF8String  |                |
+| 910 | Additional-MBMS-Trace-Info              | OctetString |                |
+| 911 | MBMS-Time-To-Data-Transfer              | Unsigned32  |                |
+| 912 | MBMS-Session-Identity-Repetition-Number | Unsigned32  |                |
+| 913 | MBMS-Required-QoS                       | UTF8String  |                |
+| 914 | MBMS-Counting-Information               | Enumerated  |                |
+| 915 | MBMS-User-Data-Mode-Indication          | Enumerated  |                |
+| 916 | MBMS-GGSN-Address                       | UTF8String  |                |
+| 917 | MBMS-GGSN-IPv6-Address                  | UTF8String  |                |
+
+|     |                              |             |  |
+|-----|------------------------------|-------------|--|
+| 918 | MBMS-BMSC-SSM-IP-Address     | UTF8String  |  |
+| 919 | MBMS-BMSC-SSM-IPv6-Address   | UTF8String  |  |
+| 920 | MBMS-Flow-Identifier         | OctetString |  |
+| 921 | CN-IP-Multicast-Distribution | Enumerated  |  |
+| 922 | MBMS-HC-Indicator            | Enumerated  |  |
+| 923 | MBMS-Access-Indicator        | Enumerated  |  |
+| 924 | MBMS-GW-SSM-IP-Address       | OctetString |  |
+| 925 | MBMS-GW-SSM-IPv6-Address     | OctetString |  |
+| 926 | MBMS-BMSC-SSM-UDP-Port       | OctetString |  |
+| 927 | MBMS-GW-UDP-Port             | OctetString |  |
+| 928 | MBMS-GW-UDP-Port-Indicator   | Enumerated  |  |
+| 929 | MBMS-Data-Transfer-Start     | Unsigned64  |  |
+| 930 | MBMS-Data-Transfer-Stop      | Unsigned64  |  |
+| 931 | MBMS-Flags                   | Unsigned32  |  |
+| 932 | Restart-Counter              | Unsigned32  |  |
+| 933 | Diagnostic-Info              | Unsigned32  |  |
+| 934 | MBMS-Cell-List               | OctetString |  |
+
+Note: The AVP codes from 935 to 999 are reserved for TS 29.061
+
+|      |                                       |              |             |
+|------|---------------------------------------|--------------|-------------|
+| 1000 | Bearer-Usage                          | Enumerated   |             |
+| 1001 | Charging-Rule-Install                 | Grouped      |             |
+| 1002 | Charging-Rule-Remove                  | Grouped      |             |
+| 1003 | Charging-Rule-Definition              | Grouped      |             |
+| 1004 | Charging-Rule-Base-Name               | UTF8String   |             |
+| 1005 | Charging-Rule-Name                    | OctetString  |             |
+| 1006 | Event-Trigger                         | Enumerated   |             |
+| 1007 | Metering-Method                       | Enumerated   |             |
+| 1008 | Offline                               | Enumerated   |             |
+| 1009 | Online                                | Enumerated   |             |
+| 1010 | Precedence                            | Unsigned32   |             |
+| 1011 | Reporting-Level                       | Enumerated   |             |
+| 1012 | TFT-Filter                            | IPFilterRule |             |
+| 1013 | TFT-Packet-Filter-Information         | Grouped      |             |
+| 1014 | ToS-Traffic-Class                     | OctetString  |             |
+| 1016 | QoS-Information                       | Grouped      |             |
+| 1018 | Charging-Rule-Report                  | Grouped      |             |
+| 1019 | PCC-Rule-Status                       | Enumerated   |             |
+| 1020 | Bearer-Identifier                     | OctetString  |             |
+| 1021 | Bearer-Operation                      | Enumerated   |             |
+| 1022 | Access-Network-Charging-Identifier-Gx | Grouped      |             |
+| 1023 | Bearer-Control-Mode                   | Enumerated   |             |
+| 1024 | Network-Request-Support               | Enumerated   |             |
+| 1025 | Guaranteed-Bitrate-DL                 | Unsigned32   | 29.212 [19] |
+| 1026 | Guaranteed-Bitrate-UL                 | Unsigned32   |             |
+| 1027 | IP-CAN-Type                           | Enumerated   |             |
+| 1028 | QoS-Class-Identifier                  | Enumerated   |             |
+| 1029 | QoS-Negotiation                       | Enumerated   |             |
+| 1030 | QoS-Upgrade                           | Enumerated   |             |
+| 1031 | Rule-Failure-Code                     | Enumerated   |             |
+| 1032 | RAT-Type                              | Enumerated   |             |
+| 1033 | Event-Report-Indication               | Grouped      |             |
+| 1034 | Allocation-Retention-Priority         | Grouped      |             |
+| 1035 | CoA-IP-Address                        | Address      |             |
+| 1036 | Tunnel-Header-Filter                  | IPFilterRule |             |
+| 1037 | Tunnel-Header-Length                  | Unsigned32   |             |
+| 1038 | Tunnel-Information                    | Grouped      |             |
+| 1039 | CoA-Information                       | Grouped      |             |
+| 1040 | APN-Aggregate-Max-Bitrate-DL          | Unsigned32   |             |
+| 1041 | APN-Aggregate-Max-Bitrate-UL          | Unsigned32   |             |
+| 1042 | Revalidation-Time                     | Time         |             |
+| 1043 | Rule-Activation-Time                  | Time         |             |
+| 1044 | Rule-DeActivation-Time                | Time         |             |
+| 1045 | Session-Release-Cause                 | Enumerated   |             |
+| 1046 | Priority-Level                        | Unsigned32   |             |
+| 1047 | Pre-emption-Capability                | Enumerated   |             |
+| 1048 | Pre-emption-Vulnerability             | Enumerated   |             |
+
+|                                                                  |                                   |                  |             |
+|------------------------------------------------------------------|-----------------------------------|------------------|-------------|
+| 1049                                                             | Default-EPS-Bearer-QoS            | Grouped          |             |
+| 1050                                                             | AN-GW-Address                     | Address          |             |
+| 1051                                                             | QoS-Rule-Install                  | Grouped          |             |
+| 1052                                                             | QoS-Rule-Remove                   | Grouped          |             |
+| 1053                                                             | QoS-Rule-Definition               | Grouped          |             |
+| 1054                                                             | QoS-Rule-Name                     | OctetString      |             |
+| 1055                                                             | QoS-Rule-Report                   | Grouped          |             |
+| 1056                                                             | Security-Parameter-Index          | OctetString      |             |
+| 1057                                                             | Flow-Label                        | OctetString      |             |
+| 1058                                                             | Flow-Information                  | Grouped          |             |
+| 1059                                                             | Packet-Filter-Content             | IPFilterRule     |             |
+| 1060                                                             | Packet-Filter-Identifier          | OctetString      |             |
+| 1061                                                             | Packet-Filter-Information         | Grouped          |             |
+| 1062                                                             | Packet-Filter-Operation           | Enumerated       |             |
+| 1063                                                             | Resource-Allocation-Notification  | Enumerated       |             |
+| 1064                                                             | Session-Linking-Indicator         | Enumerated       |             |
+| 1065                                                             | PDN-Connection-ID                 | OctetString      |             |
+| 1066                                                             | Monitoring-Key                    | OctetString      |             |
+| 1067                                                             | Usage-Monitoring-Information      | Grouped          |             |
+| 1068                                                             | Usage-Monitoring-Level            | Enumerated       |             |
+| 1069                                                             | Usage-Monitoring-Report           | Enumerated       |             |
+| 1070                                                             | Usage-Monitoring-Support          | Enumerated       |             |
+| 1071                                                             | CSG-Information-Reporting         | Enumerated       |             |
+| 1072                                                             | Packet-Filter-Usage               | Enumerated       |             |
+| 1073                                                             | Charging-Correlation-Indicator    | Enumerated       |             |
+| 1074                                                             | QoS-Rule-Base-Name                | UTF8String       |             |
+| 1075                                                             | Routing-Rule-Remove               | Grouped          |             |
+| 1076                                                             | Routing-Rule-Definition           | Grouped          |             |
+| 1077                                                             | Routing-Rule-Identifier           | OctetString      |             |
+| 1078                                                             | Routing-Filter                    | Grouped          |             |
+| 1079                                                             | Routing-IP-Address                | Address          |             |
+| 1080                                                             | Flow-Direction                    | Enumerated       |             |
+| 1081                                                             | Routing-Rule-Install              | Grouped          |             |
+| 1082                                                             | Credit-Management-Status          | Unsigned32       |             |
+| 1085                                                             | Redirect-Information              | Grouped          |             |
+| 1086                                                             | Redirect- Support                 | Enumerated       |             |
+| 1087                                                             | TDF-Information                   | Grouped          |             |
+| 1088                                                             | TDF-Application-Identifier        | OctetString      |             |
+| 1089                                                             | TDF-Destination-Host              | DiameterIdentity |             |
+| 1090                                                             | TDF-Destination-Realm             | DiameterIdentity |             |
+| 1091                                                             | TDF-IP-address                    | Address          |             |
+| 1092                                                             | ADC-Rule-Install                  | Grouped          |             |
+| 1093                                                             | ADC-Rule-Remove                   | Grouped          |             |
+| 1094                                                             | ADC-Rule-Definition               | Grouped          |             |
+| 1095                                                             | ADC-Rule-Base-Name                | UTF8String       |             |
+| 1096                                                             | ADC-Rule-Name                     | OctetString      |             |
+| 1097                                                             | ADC-Rule-Report                   | Grouped          |             |
+| 1098                                                             | Application-Detection-Information | Grouped          |             |
+| 1099                                                             | PS-to-CS-Session-Continuity       | Enumerated       |             |
+| Note: The AVP codes from 1083 to 1084 are reserved for TS 29.212 |                                   |                  |             |
+| 1100                                                             | Served-User-Identity              | Groupe           | 29.140 [16] |
+| 1101                                                             | VASP-ID                           | UTF8Str          |             |
+| 1102                                                             | VAS-ID                            | UTF8String       |             |
+| 1103                                                             | Trigger-Event                     | Enumerated       |             |
+| 1104                                                             | Sender-Address                    | UTF8String       |             |
+| 1105                                                             | Initial-Recipient-Address         | Grouped          |             |
+| 1106                                                             | Result-Recipient-Address          | Grouped          |             |
+| 1107                                                             | Sequence-Number                   | Unsigned32       |             |
+| 1108                                                             | Recipient-Address                 | UTF8String       |             |
+| 1109                                                             | Routeing-Address                  | UTF8String       |             |
+| 1110                                                             | Originating-Interface             | Enumerated       |             |
+| 1111                                                             | Delivery-Report                   | Enumerated       |             |
+| 1112                                                             | Read-Reply                        | Enumerated       |             |
+| 1113                                                             | Sender-Visibility                 | Enumerated       |             |
+| 1114                                                             | Service-Key                       | UTF8String       |             |
+
+|                                                                  |                                |             |            |
+|------------------------------------------------------------------|--------------------------------|-------------|------------|
+| 1115                                                             | Billing-Information            | UTF8String  |            |
+| 1116                                                             | Status                         | Grouped     |            |
+| 1117                                                             | Status-Code                    | UTF8String  |            |
+| 1118                                                             | Status-Text                    | UTF8String  |            |
+| Note: The AVP codes from 1119 to 1199 are reserved for TS 29.140 |                                |             |            |
+| 1200                                                             | Domain-Name                    | UTF8String  |            |
+| 1201                                                             | Recipient-Address              | Grouped     |            |
+| 1202                                                             | Submission-Time                | Time        |            |
+| 1203                                                             | MM-Content-Type                | Grouped     |            |
+| 1204                                                             | Type-Number                    | Enumerated  |            |
+| 1205                                                             | Additional-Type-Information    | UTF8String  |            |
+| 1206                                                             | Content-Size                   | Unsigned32  |            |
+| 1207                                                             | Additional-Content-Information | Grouped     |            |
+| 1208                                                             | Addressee-Type                 | Enumerated  |            |
+| 1209                                                             | Priority                       | Enumerated  |            |
+| 1210                                                             | Message-ID                     | UTF8String  |            |
+| 1211                                                             | Message-Type                   | Enumerated  |            |
+| 1212                                                             | Message-Size                   | Unsigned32  |            |
+| 1213                                                             | Message-Class                  | Grouped     |            |
+| 1214                                                             | Class-Identifier               | Enumerated  |            |
+| 1215                                                             | Token-Text                     | UTF8String  |            |
+| 1216                                                             | Delivery-Report-Requested      | Enumerated  |            |
+| 1217                                                             | Adaptations                    | Enumerated  |            |
+| 1218                                                             | Applic-ID                      | UTF8String  |            |
+| 1219                                                             | Aux-Applic-Info                | UTF8String  |            |
+| 1220                                                             | Content-Class                  | Enumerated  |            |
+| 1221                                                             | DRM-Content                    | Enumerated  |            |
+| 1222                                                             | Read-Reply-Report-Requested    | Enumerated  |            |
+| 1223                                                             | Reply-Applic-ID                | UTF8String  |            |
+| 1224                                                             | File-Repair-Supported          | Enumerated  |            |
+| 1225                                                             | MBMS-User-Service-Type         | Enumerated  |            |
+| 1226                                                             | Unit-Quota-Threshold           | Unsigned32  |            |
+| 1227                                                             | PDP-Address                    | Address     |            |
+| 1228                                                             | SGSN-Address                   | Address     |            |
+| 1229                                                             | PoC-Session-Id                 | UTF8String  |            |
+| 1230                                                             | Deferred-Location-Even-Type    | UTF8String  | 32.299 [5] |
+| 1231                                                             | LCS-APN                        | UTF8String  |            |
+| 1232                                                             | LCS-Client-Id                  | Grouped     |            |
+| 1233                                                             | LCS-Client-Dialed-By-MS        | UTF8String  |            |
+| 1234                                                             | LCS-Client-External-ID         | UTF8String  |            |
+| 1235                                                             | LCS-Client-Name                | Grouped     |            |
+| 1236                                                             | LCS-Data-Coding-Scheme         | UTF8String  |            |
+| 1237                                                             | LCS-Format-Indicator           | Enumerated  |            |
+| 1238                                                             | LCS-Name-String                | UTF8String  |            |
+| 1239                                                             | LCS-Requestor-Id               | Grouped     |            |
+| 1240                                                             | LCS-Requestor-Id-String        | UTF8String  |            |
+| 1241                                                             | LCS-Client-Type                | Enumerated  |            |
+| 1242                                                             | Location-Estimate              | OctetString |            |
+| 1243                                                             | Location-Estimate-Type         | Enumerated  |            |
+| 1244                                                             | Location-Type                  | Grouped     |            |
+| 1245                                                             | Positioning-Data               | UTF8String  |            |
+| 1246                                                             | Reserved                       | -           |            |
+| 1247                                                             | PDP-Context-Type               | Enumerated  |            |
+| 1248                                                             | MMBox-Storage-Requested        | Enumerated  |            |
+| 1249                                                             | Service-Specific-Info          | Grouped     |            |
+| 1250                                                             | Called-Asserted-Identity       | UTF8String  |            |
+| 1251                                                             | Requested-Party-Address        | UTF8String  |            |
+| 1252                                                             | PoC-User-Role                  | Grouped     |            |
+| 1253                                                             | PoC-User-Role-IDs              | UTF8String  |            |
+| 1254                                                             | PoC-User-Role-info-Units       | Enumerated  |            |
+| 1255                                                             | Talk-Burst-Exchange            | Grouped     |            |
+| 1256                                                             | Service-Generic-Information    | Grouped     |            |
+| 1257                                                             | Service-Specific-Type          | Unsigned32  |            |
+| 1258                                                             | Event-Charging-TimeStamp       | Time        |            |
+| 1259                                                             | Participant-Access-Priority    | Enumerated  |            |
+
+|                                                                   |                                            |             |  |
+|-------------------------------------------------------------------|--------------------------------------------|-------------|--|
+| 1260                                                              | Participant-Group                          | Grouped     |  |
+| 1261                                                              | PoC-Change-Conditions                      | Enumerated  |  |
+| 1262                                                              | PoC-Change-Time                            | Time        |  |
+| 1263                                                              | Access-Network-Information                 | OctetString |  |
+| 1264                                                              | Trigger                                    | Grouped     |  |
+| 1265                                                              | Base-Time-Interval                         | Unsigned32  |  |
+| 1266                                                              | Envelope                                   | Grouped     |  |
+| 1267                                                              | Envelope-End-Time                          | Time        |  |
+| 1268                                                              | Envelope-Reporting                         | Enumerated  |  |
+| 1269                                                              | Envelope-Start-Time                        | Time        |  |
+| 1270                                                              | Time-Quota-Mechanism                       | Grouped     |  |
+| 1271                                                              | Time-Quota-Type                            | Enumerated  |  |
+| 1272                                                              | Early-Media-Description                    | Grouped     |  |
+| 1273                                                              | SDP-TimeStamps                             | Grouped     |  |
+| 1274                                                              | SDP-Offer-Timestamp                        | Time        |  |
+| 1275                                                              | SDP-Answer-Timestamp                       | Time        |  |
+| 1276                                                              | AF-Correlation-Information                 | Grouped     |  |
+| 1277                                                              | PoC-Session-Initiation-type                | Enumerated  |  |
+| 1278                                                              | Offline-Charging                           | Grouped     |  |
+| 1279                                                              | User-Participating-Type                    | Enumerated  |  |
+| 1280                                                              | Alternate-Charged-Party-Address            | UTF8String  |  |
+| 1281                                                              | IMS-Communication-Service-Identifier       | UTF8String  |  |
+| 1282                                                              | Number-Of-Received-Talk-Bursts             | Unsigned32  |  |
+| 1283                                                              | Number-Of-Talk-Bursts                      | Unsigned32  |  |
+| 1284                                                              | Received-Talk-Burst-Time                   | Unsigned32  |  |
+| 1285                                                              | Received-Talk-Burst-Volume                 | Unsigned32  |  |
+| 1286                                                              | Talk-Burst-Time                            | Unsigned32  |  |
+| 1287                                                              | Talk-Burst-Volume                          | Unsigned32  |  |
+| 1288                                                              | Media-Initiator-Party                      | UTF8String  |  |
+| Note: The AVP codes from 1289 to 1299 are reserved for TS 32.299  |                                            |             |  |
+| 1300                                                              | PC5-Radio-Technology                       | Enumerated  |  |
+| 1301                                                              | RAN-End-Time                               | Time        |  |
+| 1302                                                              | RAN-Secondary-RAT-Usage-Report             | Grouped     |  |
+| 1303                                                              | RAN-Start-Time                             | Time        |  |
+| 1304                                                              | Secondary-RAT-Type                         | OctetString |  |
+| 1305                                                              | Civic-Address-Information                  | UTF8String  |  |
+| 1306                                                              | WLAN-Operator-Id                           | Grouped     |  |
+| 1307                                                              | WLAN-Operator-Name                         | UTF8String  |  |
+| 1308                                                              | WLAN-PLMN-Id                               | UTF8String  |  |
+| 1309                                                              | API-Content                                | UTF8String  |  |
+| 1310                                                              | API-Direction                              | Enumerated  |  |
+| 1311                                                              | API-Identifier                             | OctetString |  |
+| 1312                                                              | API-Invocation-Timestamp                   | Time        |  |
+| 1313                                                              | API-Result-Code                            | Unsigned32  |  |
+| 1314                                                              | API-Size                                   | Unsigned64  |  |
+| 1315                                                              | API-Network-Service-Node                   | Enumerated  |  |
+| 1316                                                              | Exposure-Function-API-Information          | Grouped     |  |
+| 1317                                                              | SCEF-Address                               | Address     |  |
+| 1318                                                              | TLTRI                                      | Unsigned32  |  |
+| 1319                                                              | TTRI                                       | Unsigned32  |  |
+| 1320                                                              | 3GPP-OC-Specific-Reduction                 | Grouped     |  |
+| 1321                                                              | 3GPP-OC-Rating-Group                       | Unsigned32  |  |
+| 1322                                                              | 3GPP-OC-Request-Type                       | Enumerated  |  |
+| 1323                                                              | VoLTE-Information                          | Grouped     |  |
+| Note: The AVP codes from 1324 to 1399 are reserved for TS 32.229. |                                            |             |  |
+| 1400                                                              | Subscription-Data                          | Grouped     |  |
+| 1401                                                              | Terminal-Information                       | Grouped     |  |
+| 1402                                                              | IMEI                                       | UTF8String  |  |
+| 1403                                                              | Software-Version                           | UTF8String  |  |
+| 1404                                                              | QoS-Subscribed                             | UTF8String  |  |
+| 1405                                                              | ULR-Flags                                  | Unsigned32  |  |
+| 1406                                                              | ULA-Flags                                  | Unsigned32  |  |
+| 1407                                                              | Visited PLMN Id                            | OctetString |  |
+| 1408                                                              | Requested-EUTRAN-Authentication-Info       | Grouped     |  |
+| 1409                                                              | Requested-UTRAN- GERAN-Authentication-Info | Grouped     |  |
+
+32.299 [5]
+
+29.272 [21]
+
+|      |                                               |             |
+|------|-----------------------------------------------|-------------|
+| 1410 | Number-Of-Requested-Vectors                   | Unsigned32  |
+| 1411 | Re-Synchronization-Info                       | OctetString |
+| 1412 | Immediate-Response-Preferred                  | Unsigned32  |
+| 1413 | Authentication-Info                           | Grouped     |
+| 1414 | E-UTRAN-Vector                                | Grouped     |
+| 1415 | UTRAN-Vector                                  | Grouped     |
+| 1416 | GERAN-Vector                                  | Grouped     |
+| 1417 | Network-Access-Mode                           | Enumerated  |
+| 1418 | HPLMN-ODB                                     | Enumerated  |
+| 1419 | Item-Number                                   | Unsigned32  |
+| 1420 | Cancellation-Type                             | Enumerated  |
+| 1421 | DSR-Flags                                     | Unsigned32  |
+| 1422 | DSA-Flags                                     | Unsigned32  |
+| 1423 | Context-Identifier                            | Unsigned32  |
+| 1424 | Subscriber-Status                             | Enumerated  |
+| 1425 | Operator-Determined-Barring                   | Unsigned32  |
+| 1426 | Access-Restriction-Data                       | Unsigned32  |
+| 1427 | APN-OI-Replacement                            | UTF8String  |
+| 1428 | All-APN-Configurations-Included-Indicator     | Enumerated  |
+| 1429 | APN-Configuration-Profile                     | Grouped     |
+| 1430 | APN-Configuration                             | Grouped     |
+| 1431 | EPS-Subscribed-QoS-Profile                    | Grouped     |
+| 1432 | VPLMN-Dynamic-Address-Allowed                 | Enumerated  |
+| 1433 | STN-SR                                        | OctetString |
+| 1434 | Alert-Reason                                  | Enumerated  |
+| 1435 | AMBR                                          | Grouped     |
+| 1436 | CSG-Subscription-Data                         | Grouped     |
+| 1437 | CSG-Id                                        | Unsigned32  |
+| 1438 | PDN-GW-Allocation-Type                        | Enumerated  |
+| 1439 | Expiration-Date                               | Time        |
+| 1440 | RAT-Frequency-Selection-Priority-ID           | Unsigned32  |
+| 1441 | IDA-Flags                                     | Unsigned32  |
+| 1442 | PUA-Flags                                     | Unsigned32  |
+| 1443 | NOR-Flags                                     | Unsigned32  |
+| 1444 | User-Id                                       | UTF8String  |
+| 1445 | Equipment-Status                              | Enumerated  |
+| 1446 | Regional-Subscription-Zone-Code               | OctetString |
+| 1447 | RAND                                          | OctetString |
+| 1448 | XRES                                          | OctetString |
+| 1449 | AUTN                                          | OctetString |
+| 1450 | KASME                                         | OctetString |
+| 1451 | Reserved                                      | -           |
+| 1452 | Trace-Collection-Entity                       | Address     |
+| 1453 | Kc                                            | OctetString |
+| 1454 | SRES                                          | OctetString |
+| 1455 | Reserved                                      | -           |
+| 1456 | PDN-Type                                      | Enumerated  |
+| 1457 | Roaming-Restricted-Due-To-Unsupported-Feature | Enumerated  |
+| 1458 | Trace-Data                                    | Grouped     |
+| 1459 | Trace-Reference                               | OctetString |
+| 1460 | Reserved                                      | -           |
+| 1461 | Reserved                                      | -           |
+| 1462 | Trace-Depth                                   | Enumerated  |
+| 1463 | Trace-NE-Type-List                            | OctetString |
+| 1464 | Trace-Interface-List                          | OctetString |
+| 1465 | Trace-Event-List                              | OctetString |
+| 1466 | OMC-Id                                        | OctetString |
+| 1467 | GPRS-Subscription-Data                        | Grouped     |
+| 1468 | Complete-Data-List-Included-Indicator         | Enumerated  |
+| 1469 | PDP-Context                                   | Grouped     |
+| 1470 | PDP-Type                                      | OctetString |
+| 1471 | 3GPP2-MEID                                    | OctetString |
+| 1472 | Specific-APN-Info                             | Grouped     |
+| 1473 | LCS-Info                                      | Grouped     |
+| 1474 | GMLC-Number                                   | OctetString |
+
+|      |                                                   |                  |             |
+|------|---------------------------------------------------|------------------|-------------|
+| 1475 | LCS-PrivacyException                              | Grouped          |             |
+| 1476 | SS-Code                                           | OctetString      |             |
+| 1477 | SS-Status                                         | OctetString      |             |
+| 1478 | Notification-To-UE-User                           | Enumerated       |             |
+| 1479 | External-Client                                   | Grouped          |             |
+| 1480 | Client-Identity                                   | OctetString      |             |
+| 1481 | GMLC-Restriction                                  | Enumerated       |             |
+| 1482 | PLMN-Client                                       | Enumerated       |             |
+| 1483 | Service-Type                                      | Grouped          |             |
+| 1484 | ServiceTypeIdentity                               | Unsigned32       |             |
+| 1485 | MO-LR                                             | Grouped          |             |
+| 1486 | Teleservice-List                                  | Grouped          |             |
+| 1487 | TS-Code                                           | Enumerated       |             |
+| 1488 | Call-Barring-Info                                 | Grouped          |             |
+| 1489 | SGSN-Number                                       | OctetString      |             |
+| 1490 | IDR-Flags                                         | Unsigned32       |             |
+| 1491 | ICS-Indicator                                     | Enumerated       |             |
+| 1492 | IMS-Voice-Over-PS-Sessions-Supported              | Enumerated       |             |
+| 1493 | Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions | Enumerated       |             |
+| 1494 | Last-UE-Activity-Time                             | Time             |             |
+| 1495 | EPS-User-State                                    | Grouped          |             |
+| 1496 | EPS-Location-Information                          | Grouped          |             |
+| 1497 | MME-User-State                                    | Grouped          |             |
+| 1498 | SGSN-User-State                                   | Grouped          |             |
+| 1499 | User-State                                        | Enumerated       |             |
+| 1500 | Non-3GPP-User-Data                                | Grouped          | 29.273 [20] |
+| 1501 | Non-3GPP-IP-Access                                | Enumerated       |             |
+| 1502 | Non-3GPP-IP-Access-APN                            | Enumerated       |             |
+| 1503 | AN-Trusted                                        | Enumerated       |             |
+| 1504 | ANID                                              | UTF8String       |             |
+| 1505 | Trace-Info                                        | Grouped          |             |
+| 1506 | MIP-FA-RK                                         | OctetString      |             |
+| 1507 | MIP-FA-RK-SPI                                     | Unsigned32       |             |
+| 1508 | PPR-Flags                                         | Unsigned32       |             |
+| 1509 | WLAN-Identifier                                   | Grouped          |             |
+| 1510 | TWAN-Access-Info                                  | Grouped          |             |
+| 1511 | Access-Authorization-Flags                        | Unsigned32       |             |
+| 1512 | TWAN-Default-APN-Context-Id                       | Unsigned32       |             |
+| 1513 | Reserved                                          | -                |             |
+| 1514 | Reserved                                          | -                |             |
+| 1515 | Reserved                                          | -                |             |
+| 1516 | Full-Network-Name                                 | OctetString      |             |
+| 1517 | Short-Network-Name                                | OctetString      |             |
+| 1518 | AAA-Failure-Indication                            | Unsigned32       |             |
+| 1519 | Transport-Access-Type                             | Enumerated       |             |
+| 1520 | DER-Flags                                         | Unsigned32       |             |
+| 1521 | DEA-Flags                                         | Unsigned32       |             |
+| 1522 | RAR-Flags                                         | Unsigned32       |             |
+| 1523 | DER-S6b-Flags                                     | Unsigned32       |             |
+| 1524 | SSID                                              | UTF8String       |             |
+| 1525 | HESSID                                            | UTF8String       |             |
+| 1526 | Access-Network-Info                               | Grouped          |             |
+| 1527 | TWAN-Connection-Mode                              | Unsigned32       |             |
+| 1528 | TWAN-Connectivity-Parameters                      | Grouped          |             |
+| 1529 | Connectivity-Flags                                | Unsigned32       |             |
+| 1530 | TWAN-PCO                                          | OctetString      |             |
+| 1531 | TWAG-CP-Address                                   | Address          |             |
+| 1532 | TWAG-UP-Address                                   | UTF8String       |             |
+| 1533 | TWAN-S2a-Failure-Cause                            | Unsigned32       |             |
+| 1534 | SM-Back-Off-Timer                                 | Unsigned32       |             |
+| 1535 | WLCP-Key                                          | OctetString      |             |
+| 318  | 3GPP-AAA-Server-Name                              | DiameterIdentity |             |
+| 1536 | Origination-Time-Stamp                            | Unsigned64       |             |
+| 1537 | Maximum-Wait-Time                                 | Unsigned32       |             |
+
+|                                                                                                                                 |                                   |                  |  |
+|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------------------|--|
+| 1538                                                                                                                            | Emergency-Services                | Unsigned32       |  |
+| 1539                                                                                                                            | AAR-Flags                         | Unsigned32       |  |
+| 1540                                                                                                                            | IMEI-Check-In-VPLMN-Result        | Unsigned32       |  |
+| 1541                                                                                                                            | ERP-Authorization                 | Unsigned32       |  |
+| Note 1: The AVP codes from 1542 to 1599 are reserved for TS 29.273                                                              |                                   |                  |  |
+| Note 2: The AVP 3GPP-AAA-Server-Name was originally defined in 3GPP TS 29.234 and is now defined in 3GPP TS 29.273 from Rel-12. |                                   |                  |  |
+| 1600                                                                                                                            | MME-Location-Information          | Grouped          |  |
+| 1601                                                                                                                            | SGSN-Location-Information         | Grouped          |  |
+| 1602                                                                                                                            | E-UTRAN-Cell-Global-Identity      | OctetString      |  |
+| 1603                                                                                                                            | Tracking-Area-Identity            | OctetString      |  |
+| 1604                                                                                                                            | Cell-Global-Identity              | OctetString      |  |
+| 1605                                                                                                                            | Routing-Area-Identity             | OctetString      |  |
+| 1606                                                                                                                            | Location-Area-Identity            | OctetString      |  |
+| 1607                                                                                                                            | Service-Area-Identity             | OctetString      |  |
+| 1608                                                                                                                            | Geographical-Information          | OctetString      |  |
+| 1609                                                                                                                            | Geodetic-Information              | OctetString      |  |
+| 1610                                                                                                                            | Current-Location-Retrieved        | Enumerated       |  |
+| 1611                                                                                                                            | Age-Of-Location-Information       | Unsigned32       |  |
+| 1612                                                                                                                            | Active-APN                        | Grouped          |  |
+| 1613                                                                                                                            | SIPTO-Permission                  | Enumerated       |  |
+| 1614                                                                                                                            | Error-Diagnostic                  | Enumerated       |  |
+| 1615                                                                                                                            | UE-SRVCC-Capability               | Enumerated       |  |
+| 1616                                                                                                                            | MPS-Priority                      | Unsigned32       |  |
+| 1617                                                                                                                            | VPLMN-LIPA-Allowed                | Enumerated       |  |
+| 1618                                                                                                                            | LIPA-Permission                   | Enumerated       |  |
+| 1619                                                                                                                            | Subscribed-Periodic-RAU-TAU-Timer | Unsigned32       |  |
+| 1620                                                                                                                            | Ext-PDP-Type                      | OctetString      |  |
+| 1621                                                                                                                            | Ext-PDP-Address                   | Address          |  |
+| 1622                                                                                                                            | MDT-Configuration                 | Grouped          |  |
+| 1623                                                                                                                            | Job-Type                          | Enumerated       |  |
+| 1624                                                                                                                            | Area-Scope                        | Grouped          |  |
+| 1625                                                                                                                            | List-Of-Measurements              | Unsigned32       |  |
+| 1626                                                                                                                            | Reporting-Trigger                 | Unsigned32       |  |
+| 1627                                                                                                                            | Report-Interval                   | Enumerated       |  |
+| 1628                                                                                                                            | Report-Amount                     | Enumerated       |  |
+| 1629                                                                                                                            | Event-ThresholdRSRP               | Unsigned32       |  |
+| 1630                                                                                                                            | Event-ThresholdRSRQ               | Unsigned32       |  |
+| 1631                                                                                                                            | Logging-Interval                  | Enumerated       |  |
+| 1632                                                                                                                            | Logging-Duration                  | Enumerated       |  |
+| 1633                                                                                                                            | Relay-Node-Indicator              | Enumerated       |  |
+| 1634                                                                                                                            | MDT-User-Consent                  | Enumerated       |  |
+| 1635                                                                                                                            | PUR-Flags                         | Unsigned32       |  |
+| 1636                                                                                                                            | Subscribed-VSRVCC                 | Enumerated       |  |
+| 1637                                                                                                                            | Equivalent-PLMN-List              | Grouped          |  |
+| 1638                                                                                                                            | CLR-Flags                         | Unsigned32       |  |
+| 1639                                                                                                                            | UVR-Flags                         | Unsigned32       |  |
+| 1640                                                                                                                            | UVA-Flags                         | Unsigned32       |  |
+| 1641                                                                                                                            | VPLMN-CSG-Subscription-Data       | Grouped          |  |
+| 1642                                                                                                                            | Time-Zone                         | UTF8String       |  |
+| 1643                                                                                                                            | A-MSISDN                          | OctetString      |  |
+| 1644                                                                                                                            | Reserved                          | -                |  |
+| 1645                                                                                                                            | MME-Number-for-MT-SMS             | OctetString      |  |
+| 1646                                                                                                                            | Reserved                          | -                |  |
+| 1647                                                                                                                            | Reserved                          | -                |  |
+| 1648                                                                                                                            | SMS-Register-Request              | Enumerated       |  |
+| 1649                                                                                                                            | Local-Time-Zone                   | Grouped          |  |
+| 1650                                                                                                                            | Daylight-Saving-Time              | Enumerated       |  |
+| 1651                                                                                                                            | GMLC-Info                         | Grouped          |  |
+| 1652                                                                                                                            | GMLC-Name                         | DiameterIdentity |  |
+| 1653                                                                                                                            | GMLC-Realm                        | DiameterIdentity |  |
+| 1654                                                                                                                            | Subscription-Data-Flags           | Unsigned32       |  |
+| 1655                                                                                                                            | Measurement-Period-LTE            | Enumerated       |  |
+| 1656                                                                                                                            | Measurement-Period-UMTS           | Enumerated       |  |
+| 1657                                                                                                                            | Collection-Period-RRM-LTE         | Enumerated       |  |
+
+29.272  
+[21]
+
+|                                                                   |                                          |                  |            |
+|-------------------------------------------------------------------|------------------------------------------|------------------|------------|
+| 1658                                                              | Collection-Period-RRM-UMTS               | Enumerated       |            |
+| 1659                                                              | Positioning-Method                       | OctetString      |            |
+| 1660                                                              | Measurement-Quantity                     | OctetString      |            |
+| 1661                                                              | Event-Threshold-Event-1F                 | Integer32        |            |
+| 1662                                                              | Event-Threshold-Event-1I                 | Integer32        |            |
+| 1663                                                              | Restoration-Priority                     | Unsigned32       |            |
+| 1664                                                              | SGs-MME-Identity                         | UTF8String       |            |
+| 1665                                                              | SIPTO-Local-Network-Permission           | Unsigned32       |            |
+| 1666                                                              | Coupled-Node-Diameter-ID                 | DiameterIdentity |            |
+| 1667                                                              | WLAN-offloadability                      | Grouped          |            |
+| 1668                                                              | WLAN-offloadability-EUTRAN               | Unsigned32       |            |
+| 1669                                                              | WLAN-offloadability-UTRAN                | Unsigned32       |            |
+| 1670                                                              | Reset-ID                                 | OctetString      |            |
+| 1671                                                              | MDT-Allowed-PLMN-Id                      | OctetString      |            |
+| 1672                                                              | Adjacent-PLMNs                           | Grouped          |            |
+| 1673                                                              | Adjacent-Access-Restriction-Data         | Grouped          |            |
+| 1674                                                              | DL-Buffering-Suggested-Packet-Count      | Integer32        |            |
+| 1675                                                              | IMSI-Group-Id                            | Grouped          |            |
+| 1676                                                              | Group-Service-Id                         | Unsigned32       |            |
+| 1677                                                              | Group-PLMN-Id                            | OctetString      |            |
+| 1678                                                              | Local-Group-Id                           | OctetString      |            |
+| 1679                                                              | AIR-Flags                                | Unsigned32       |            |
+| 1680                                                              | UE-Usage-Type                            | Unsigned32       |            |
+| 1681                                                              | Non-IP-PDN-Type-Indicator                | Enumerated       |            |
+| 1682                                                              | Non-IP-Data-Delivery-Mechanism           | Unsigned32       |            |
+| 1683                                                              | Additional-Context-Identifier            | Unsigned32       |            |
+| 1684                                                              | SCEF-Realm                               | DiameterIdentity |            |
+| 1685                                                              | Subscription-Data-Deletion               | Grouped          |            |
+| 1686                                                              | Preferred-Data-Mode                      | Unsigned32       |            |
+| 1687                                                              | Emergency-Info                           | Grouped          |            |
+| 1688                                                              | V2X-Subscription-Data                    | Grouped          |            |
+| 1689                                                              | V2X-Permission                           | Unsigned32       |            |
+| 1690                                                              | PDN-Connection-Continuity                | Unsigned32       |            |
+| 1691                                                              | eDRX-Cycle-Length                        | Grouped          |            |
+| 1692                                                              | eDRX-Cycle-Length-Value                  | OctetString      |            |
+| 1693                                                              | UE-PC5-AMBR                              | Unsigned32       |            |
+| 1694                                                              | MBSFN-Area                               | Grouped          |            |
+| 1695                                                              | MBSFN-Area-ID                            | Unsigned32       |            |
+| 1696                                                              | Carrier-Frequency                        | Unsigned32       |            |
+| 1697                                                              | RDS-Indicator                            | Enumerated       |            |
+| 1698                                                              | Service-Gap-Time                         | Unsigned32       |            |
+| 1699                                                              | Aerial-UE-Subscription-Information       | Unsigned32       |            |
+| 1700                                                              | Broadcast-Location-Assistance-Data-Types | Unsigned64       |            |
+| 1701                                                              | Paging-Time-Window                       | Grouped          |            |
+| 1702                                                              | Operation-Mode                           | Unsigned32       |            |
+| 1703                                                              | Paging-Time-Window-Length                | OctetString      |            |
+| 1704                                                              | Core-Network-Restrictions                | Unsigned32       |            |
+| 1705                                                              | eDRX-Related-RAT                         | Grouped          |            |
+| 1706                                                              | Interworking-5GS-Indicator               | Enumerated       |            |
+| 1707                                                              | Ethernet-PDN-Type-Indicator              | Enumerated       |            |
+| 1708                                                              | Subscribed-ARPI                          | Unsigned32       |            |
+| 1709                                                              | IAB-Operation-Permission                 | Enumerated       |            |
+| 1710                                                              | V2X-Subscription-Data-Nr                 | Grouped          |            |
+| 1711                                                              | UE-PC5-QoS                               | Grouped          |            |
+| 1712                                                              | PC5-QoS-Flow                             | Grouped          |            |
+| 1713                                                              | 5QI                                      | Integer32        |            |
+| 1714                                                              | PC5-Flow-Bitrates                        | Grouped          |            |
+| 1715                                                              | Guaranteed-Flow-Bitrates                 | Integer32        |            |
+| 1716                                                              | Maximum-Flow-Bitrates                    | Integer32        |            |
+| 1717                                                              | PC5-Range                                | Integer32        |            |
+| 1718                                                              | PC5-Link-AMBR                            | Integer32        |            |
+| 1719                                                              | Third-Context-ID                         | Unsigned32       |            |
+| Note: The AVP codes from 1720 to 1799 are reserved for TS 29.272. |                                          |                  |            |
+| 2000                                                              | SMS-Information                          | Grouped          | 32.299 [5] |
+| 2001                                                              | Data-Coding-Scheme                       | Integer32        |            |
+
+|      |                                        |             |
+|------|----------------------------------------|-------------|
+| 2002 | Destination-Interface                  | Grouped     |
+| 2003 | Interface-Id                           | UTF8String  |
+| 2004 | Interface-Port                         | UTF8String  |
+| 2005 | Interface-Text                         | UTF8String  |
+| 2006 | Interface-Type                         | Enumerated  |
+| 2007 | SM-Message-Type                        | Enumerated  |
+| 2008 | Originating-SCCP-Address               | Address     |
+| 2009 | Originator-Interface                   | Grouped     |
+| 2010 | Recipient-SCCP-Address                 | Address     |
+| 2011 | Reply-Path-Requested                   | Enumerated  |
+| 2012 | SM-Discharge-Time                      | Time        |
+| 2013 | SM-Protocol-ID                         | OctetString |
+| 2014 | SM-Status                              | OctetString |
+| 2015 | SM-User-Data-Header                    | OctetString |
+| 2016 | SMS-Node                               | Enumerated  |
+| 2017 | SMSC-Address                           | Address     |
+| 2018 | Client-Address                         | Address     |
+| 2019 | Number-of-Messages-Sent                | Unsigned32  |
+| 2020 | Low-Balance-Indication                 | Enumerated  |
+| 2021 | Remaining-Balance                      | Grouped     |
+| 2022 | Refund-Information                     | OctetString |
+| 2023 | Carrier-Select-Routing-Information     | UTF8String  |
+| 2024 | Number-Portability-Routing-Information | UTF8String  |
+| 2025 | PoC-Event-Type                         | Enumerated  |
+| 2026 | Recipient-Info                         | Grouped     |
+| 2027 | Originator-Received-Address            | Grouped     |
+| 2028 | Recipient-Received-Address             | Grouped     |
+| 2029 | SM-Service-Type                        | Enumerated  |
+| 2030 | MMTel-Information                      | Grouped     |
+| 2031 | MMTel-Sservice-Type                    | Unsigned32  |
+| 2032 | Service-Mode                           | Unsigned32  |
+| 2033 | Subscriber-Role                        | Enumerated  |
+| 2034 | Number-Of-Divertions                   | Unsigned32  |
+| 2035 | Associated-Party-Address               | UTF8String  |
+| 2036 | SDP-Type                               | Enumerated  |
+| 2037 | Change-Condition                       | Integer32   |
+| 2038 | Change-Time                            | Time        |
+| 2039 | Diagnostics                            | Integer32   |
+| 2040 | Service-Data-Container                 | Grouped     |
+| 2041 | Start-Time                             | Time        |
+| 2042 | Stop-Time                              | Time        |
+| 2043 | Time-First-Usage                       | Time        |
+| 2044 | Time-Last-Usage                        | Time        |
+| 2045 | Time-Usage                             | Unsigned32  |
+| 2046 | Traffic-Data-Volumes                   | Grouped     |
+| 2047 | Serving-Node-Type                      | Enumerated  |
+| 2048 | Supplementary-Service                  | Grouped     |
+| 2049 | Participant-Action-Type                | Enumerated  |
+| 2050 | PDN-Connection-Charging-ID             | Unsigned32  |
+| 2051 | Dynamic-Address-Flag                   | Enumerated  |
+| 2052 | Accumulated-Cost                       | Grouped     |
+| 2053 | AoC-Cost-Information                   | Grouped     |
+| 2054 | AoC-Information                        | Grouped     |
+| 2055 | AoC-Request-Type                       | Enumerated  |
+| 2056 | Current-Tariff                         | Grouped     |
+| 2057 | Next-Tariff                            | Grouped     |
+| 2058 | Rate-Element                           | Grouped     |
+| 2059 | Scale-Factor                           | Grouped     |
+| 2060 | Tariff-Information                     | Grouped     |
+| 2061 | Unit-Cost                              | Grouped     |
+| 2062 | Incremental-Cost                       | Grouped     |
+| 2063 | Local-Sequence-Number                  | Unsigned32  |
+| 2064 | Node-Id                                | UTF8String  |
+| 2065 | SGW-Change                             | Enumerated  |
+| 2066 | Charging-Characteristic-Selection-Mode | Enumerated  |
+
+|                                                                   |                                          |                  |            |
+|-------------------------------------------------------------------|------------------------------------------|------------------|------------|
+| 2067                                                              | SGW-Address                              | Address          |            |
+| 2068                                                              | Dynamic-Address-Flag-Extension           | Enumerated       |            |
+| Note: The AVP codes from 2069 to 2099 are reserved for TS 32.299. |                                          |                  |            |
+| 2100                                                              | reserved                                 | -                |            |
+| 2101                                                              | Application-Server-ID                    | UTF8String       |            |
+| 2102                                                              | Application-Service-Type                 | Enumerated       |            |
+| 2103                                                              | Application-Session-ID                   | Unsigned32       |            |
+| 2104                                                              | Delivery-Status                          | UTF8String       |            |
+| 2105                                                              | reserved                                 | -                |            |
+| 2106                                                              | reserved                                 | -                |            |
+| 2107                                                              | reserved                                 | -                |            |
+| 2108                                                              | reserved                                 | -                |            |
+| 2109                                                              | reserved                                 | -                | 32.299 [5] |
+| 2110                                                              | IM-Information                           | Grouped          |            |
+| 2111                                                              | Number-Of-Messages-Successfully-Exploded | Unsigned32       |            |
+| 2112                                                              | Number-Of-Messages-Successfully-Sent     | Unsigned32       |            |
+| 2113                                                              | Total-Number-Of-Messages-Exploded        | Unsigned32       |            |
+| 2114                                                              | Total-Number-Of-Messages-Sent            | Unsigned32       |            |
+| 2115                                                              | DCD-Information                          | Grouped          |            |
+| 2116                                                              | Content-ID                               | UTF8String       |            |
+| 2117                                                              | Content-provider-ID                      | UTF8String       |            |
+| 2118                                                              | Charge-Reason-Code                       | Enumerated       |            |
+| Note: The AVP codes from 2119 to 2199 are reserved for TS 32.299. |                                          |                  |            |
+| 2200                                                              | Subsession-Decision-Info                 | Grouped          |            |
+| 2201                                                              | Subsession-Enforcement-Info              | Grouped          |            |
+| 2202                                                              | Subsession-Id                            | Unsigned32       |            |
+| 2203                                                              | Subsession-Operation                     | Enumerated       |            |
+| 2204                                                              | Multiple-BBERF-Action                    | Enumerated       | 29.215     |
+| 2205                                                              | UE-Local-IPv6-Prefix                     | OctetString      | [22]       |
+| 2206                                                              | DRA-Deployment                           | Enumerated       |            |
+| 2207                                                              | PCRF-Address                             | DiameterIdentity |            |
+| 2208                                                              | DRA-Binding                              | Enumerated       |            |
+| Note: The AVP codes from 2209 to 2299 are reserved for TS 29.215. |                                          |                  |            |
+| 2300                                                              | reserved                                 | -                |            |
+| 2301                                                              | SIP-Request-Timestamp-Fraction           | Unsigned32       |            |
+| 2302                                                              | SIP-Response-Timestamp-Fraction          | Unsigned32       |            |
+| 2303                                                              | Online-Charging-Flag                     | Enumerated       |            |
+| 2304                                                              | CUG-Information                          | OctetString      |            |
+| 2305                                                              | Real-Time-Tariff-Information             | Grouped          |            |
+| 2306                                                              | Tariff-XML                               | UTF8String       |            |
+| 2307                                                              | MBMS GW-Address                          | Address          |            |
+| 2308                                                              | IMSI-Unauthenticated-Flag                | Enumerated       |            |
+| 2309                                                              | Account-Expiration                       | Time             |            |
+| 2310                                                              | AoC-Format                               | Enumerated       |            |
+| 2311                                                              | AoC-Service                              | Enumerated       |            |
+| 2312                                                              | AoC-Service-Obligatory-Type              | Grouped          | 32.299 [5] |
+| 2313                                                              | AoC-Service-Type                         | Enumerated       |            |
+| 2314                                                              | AoC-Subscription-Information             | Grouped          |            |
+| 2315                                                              | Preferred-AoC-Currency                   | Unsigned32       |            |
+| 2316                                                              | Reserved                                 | -                |            |
+| 2317                                                              | CSG-Access-Mode                          | Enumerated       |            |
+| 2318                                                              | CSG-Membership-Indication                | Enumerated       |            |
+| 2319                                                              | User-CSG-Information                     | Grouped          |            |
+| 2320                                                              | Outgoing-Session-Id                      | UTF8String       |            |
+| 2321                                                              | Initial-IMS-Charging-Identifier          | UTF8String       |            |
+| 2322                                                              | IMS-Emergency-Indicator                  | Enumerated       |            |
+| 2323                                                              | MBMS-Charged-Party                       | Enumerated       |            |
+| Note: The AVP codes from 2324 to 2399 are reserved for TS 32.299. |                                          |                  |            |
+| 2400                                                              | LMSI                                     | OctetString      |            |
+| 2401                                                              | Serving-Node                             | Grouped          |            |
+| 2402                                                              | MME-Name                                 | DiameterIdentity |            |
+| 2403                                                              | MSC-Number                               | OctetString      | 29.173     |
+| 2404                                                              | LCS-Capabilities-Sets                    | Unsigned32       | [25]       |
+| 2405                                                              | GMLC-Address                             | Address          |            |
+| 2406                                                              | Additional-Serving-Node                  | Grouped          |            |
+
+|                                                                   |                                     |                  |                |
+|-------------------------------------------------------------------|-------------------------------------|------------------|----------------|
+| 2407                                                              | PPR-Address                         | Address          |                |
+| 2408                                                              | MME-Realm                           | DiameterIdentity |                |
+| 2409                                                              | SGSN-Name                           | DiameterIdentity |                |
+| 2410                                                              | SGSN-Realm                          | DiameterIdentity |                |
+| 2411                                                              | RIA-Flags                           | Unsigned32       |                |
+| Note: The AVP codes from 2412 to 2499 are reserved for TS 29.173. |                                     |                  |                |
+| 2500                                                              | SLG-Location-Type                   | Enumerated       |                |
+| 2501                                                              | LCS-EPS-Client-Name                 | Grouped          |                |
+| 2502                                                              | LCS-Requestor-Name                  | Grouped          |                |
+| 2503                                                              | LCS-Priority                        | Unsigned32       |                |
+| 2504                                                              | LCS-QoS                             | Grouped          |                |
+| 2505                                                              | Horizontal-Accuracy                 | Unsigned32       |                |
+| 2506                                                              | Vertical-Accuracy                   | Unsigned32       |                |
+| 2507                                                              | Vertical-Requested                  | Enumerated       |                |
+| 2508                                                              | Velocity-Requested                  | Enumerated       |                |
+| 2509                                                              | Response-Time                       | Enumerated       |                |
+| 2510                                                              | Supported-GAD-Shapes                | Unsigned32       |                |
+| 2511                                                              | LCS-Codeword                        | UTF8String       |                |
+| 2512                                                              | LCS-Privacy-Check                   | Enumerated       |                |
+| 2513                                                              | Accuracy-Fulfilment-Indicator       | Enumerated       |                |
+| 2514                                                              | Age-Of-Location-Estimate            | Unsigned32       |                |
+| 2515                                                              | Velocity-Estimate                   | OctetString      |                |
+| 2516                                                              | EUTRAN-Positioning-Data             | OctetString      |                |
+| 2517                                                              | ECGI                                | OctetString      |                |
+| 2518                                                              | Location-Event                      | Enumerated       |                |
+| 2519                                                              | Pseudonym-Indicator                 | Enumerated       |                |
+| 2520                                                              | LCS-Service-Type-ID                 | Unsigned32       |                |
+| 2521                                                              | LCS-Privacy-Check-Non-Session       | Grouped          |                |
+| 2522                                                              | LCS-Privacy-Check-Session           | Grouped          |                |
+| 2523                                                              | LCS-QoS-Class                       | Enumerated       |                |
+| 2524                                                              | GERAN-Positioning-Info              | Grouped          |                |
+| 2525                                                              | GERAN-Positioning-Data              | OctetString      |                |
+| 2526                                                              | GERAN-GANSS-Positioning-Data        | OctetString      |                |
+| 2527                                                              | UTRAN-Positioning-Info              | Grouped          |                |
+| 2528                                                              | UTRAN-Positioning-Data              | OctetString      |                |
+| 2529                                                              | UTRAN-GANSS-Positioning-Data        | OctetString      |                |
+| 2530                                                              | LRR-Flags                           | Unsigned32       |                |
+| 2531                                                              | LCS-Reference-Number                | OctetString      |                |
+| 2532                                                              | Deferred-Location-Type              | Unsigned32       |                |
+| 2533                                                              | Area-Event-Info                     | Grouped          |                |
+| 2534                                                              | Area-Definition                     | Grouped          |                |
+| 2535                                                              | Area                                | Grouped          |                |
+| 2536                                                              | Area-Type                           | Unsigned32       |                |
+| 2537                                                              | Area-Identification                 | Grouped          |                |
+| 2538                                                              | Occurrence-Info                     | Enumerated       |                |
+| 2539                                                              | Interval-Time                       | Unsigned32       |                |
+| 2540                                                              | Periodic-LDR-Information            | Grouped          |                |
+| 2541                                                              | Reporting-Amount                    | Unsigned32       |                |
+| 2542                                                              | Reporting-Interval                  | Unsigned32       |                |
+| 2543                                                              | Reporting-PLMN-List                 | Grouped          |                |
+| 2544                                                              | PLMN-ID-List                        | Grouped          |                |
+| 2545                                                              | PLR-Flags                           | Unsigned32       |                |
+| 2546                                                              | PLA-Flags                           | Unsigned32       |                |
+| 2547                                                              | Deferred-MT-LR-Data                 | Grouped          |                |
+| 2548                                                              | Termination-Cause                   | Unsigned32       |                |
+| 2549                                                              | LRA-Flags                           | Unsigned32       |                |
+| 2550                                                              | Periodic-Location-Support-Indicator | Enumerated       |                |
+| 2551                                                              | Prioritized-List-Indicator          | Enumerated       |                |
+| 2552                                                              | ESMLC-Cell-Info                     | Grouped          |                |
+| 2553                                                              | Cell-Portion-ID                     | Unsigned32       |                |
+| 2554                                                              | 1xRTT-RCID                          | OctetString      |                |
+| 2555                                                              | Delayed-Location-Reporting-Data     | Grouped          |                |
+| 2556                                                              | Civic-Address                       | UTF8String       |                |
+| 2557                                                              | Barometric-Pressure                 | Unsigned32       |                |
+| 2558                                                              | UTRAN-Additional-Positioning-Data   | OctetString      | 29.172<br>[24] |
+
+|                                                                   |                                       |             |             |
+|-------------------------------------------------------------------|---------------------------------------|-------------|-------------|
+| 2559                                                              | Motion-Event-Info                     | Grouped     |             |
+| 2560                                                              | Linear-Distance                       | Unsigned32  |             |
+| 2561                                                              | Maximum-Interval                      | Unsigned32  |             |
+| 2562                                                              | Sampling-Interval                     | Unsigned32  |             |
+| 2563                                                              | Reporting-Duration                    | Unsigned32  |             |
+| 2564                                                              | Reporting-Location-Requirements       | Unsigned32  |             |
+| 2565                                                              | Additional-Area                       | Grouped     |             |
+| Note: The AVP codes from 2566 to 2599 are reserved for TS 29.172. |                                       |             |             |
+| 2600                                                              | reserved                              | -           |             |
+| 2601                                                              | IMS-Application-Reference-Identifier  | UTF8String  |             |
+| 2602                                                              | Low-Priority-Indicator                | Enumerated  |             |
+| 2603                                                              | IP-Realm-Default-Indicator            | Enumerated  | 32.299 [5]  |
+| 2604                                                              | Local-GW-Inserted-Indicator           | Enumerated  |             |
+| 2605                                                              | Transcoder-Inserted-Indicator         | Enumerated  |             |
+| 2606                                                              | PDP-Address-Prefix-Length             | Unsigned32  |             |
+| Note: The AVP codes from 2607 to 2699 are reserved for TS 32.299. |                                       |             |             |
+| 2700                                                              | Reserved                              | -           |             |
+| 2701                                                              | Transit-IOI-List                      | UTF8String  |             |
+| 2702                                                              | Status-AS-Code                        | Enumerated  |             |
+| 2703                                                              | NNI-Information                       | Grouped     |             |
+| 2704                                                              | NNI-Type                              | Enumerated  |             |
+| 2705                                                              | Neighbour-Node-Address                | Address     |             |
+| 2706                                                              | Relationship-Mode                     | Enumerated  |             |
+| 2707                                                              | Session-Direction                     | Enumerated  |             |
+| 2708                                                              | From-Address                          | UTF8String  | 32.299 [5]  |
+| 2709                                                              | Access-Transfer-Information           | Grouped     |             |
+| 2710                                                              | Access-Transfer-Type                  | Enumerated  |             |
+| 2711                                                              | Related-IMS-Charging-Identifier       | UTF8String  |             |
+| 2712                                                              | Related-IMS-Charging-Identifier-Node  | Address     |             |
+| 2713                                                              | IMS-Visited-Network-Identifier        | UTF8String  |             |
+| 2714                                                              | TWAN-User-Location-Info               | Grouped     |             |
+| 2715                                                              | Reserved                              | -           |             |
+| 2716                                                              | BSSID                                 | UTF8String  |             |
+| 2717                                                              | TAD-Identifier                        | Enumerated  |             |
+| Note: The AVP codes from 2718 to 2799 are reserved for TS 32.299. |                                       |             |             |
+| 2800                                                              | Reserved                              | -           |             |
+| 2801                                                              | ADC-Revalidation-Time                 | Time        |             |
+| 2802                                                              | TDF-Application-Instance-Identifier   | OctetString |             |
+| 2803                                                              | HeNB-BBF-FQDN                         | UTF8String  |             |
+| 2804                                                              | HeNB-Local-IP-Address                 | Address     |             |
+| 2805                                                              | UE-Local-IP-Address                   | Address     |             |
+| 2806                                                              | UDP-Source-Port                       | Unsigned32  |             |
+| 2807                                                              | CS-Service-QoS-Request-Identifier     | OctetString |             |
+| 2808                                                              | CS-Service-QoS-Request-Operation      | Enumerated  |             |
+| 2809                                                              | Mute-Notification                     | Enumerated  |             |
+| 2810                                                              | Monitoring-Time                       | Time        |             |
+| 2811                                                              | AN-GW-Status                          | Enumerated  |             |
+| 2812                                                              | User-Location-Info-Time               | Grouped     |             |
+| 2813                                                              | CS-Service-Resource-Report            | Time        |             |
+| 2814                                                              | CS-Service-Resource-Failure-Cause     | Enumerated  |             |
+| 2815                                                              | CS-Service-Resource-Result-Operation  | Enumerated  | 29.212 [19] |
+| 2816                                                              | Default-QoS-Information               | Grouped     |             |
+| 2817                                                              | Default-QoS-Name                      | UTF8String  |             |
+| 2818                                                              | Conditional-APN-Aggregate-Max-Bitrate | Grouped     |             |
+| 2819                                                              | RAN-NAS-Release-Cause                 | OctetString |             |
+| 2820                                                              | Presence-Reporting-Area-Elements-List | OctetString |             |
+| 2821                                                              | Presence-Reporting-Area-Identifier    | OctetString |             |
+| 2822                                                              | Presence-Reporting-Area-Information   | Grouped     |             |
+| 2823                                                              | Presence-Reporting-Area-Status        | Unsigned32  |             |
+| 2824                                                              | NetLoc-Access-Support                 | Unsigned32  |             |
+| 2825                                                              | Fixed-User-Location-Info              | Grouped     |             |
+| 2826                                                              | PCSCF-Restoration-Indication          | Unsigned32  |             |
+| 2827                                                              | IP-CAN-Session-Charging-Scope         | Enumerated  |             |
+| 2828                                                              | Monitoring-Flags                      | Unsigned32  |             |
+| 2829                                                              | Default-Access                        | Enumerated  |             |
+
+|                                                                   |                                       |                  |                |
+|-------------------------------------------------------------------|---------------------------------------|------------------|----------------|
+| 2830                                                              | NBIFOM-Mode                           | Enumerated       |                |
+| 2831                                                              | NBIFOM-Support                        | Enumerated       |                |
+| 2832                                                              | RAN-Rule-Support                      | Unsigned32       |                |
+| 2833                                                              | Access-Availability-Change-Reason     | Unsigned32       |                |
+| 2834                                                              | Routing-Rule-Failure-Code             | Unsigned32       |                |
+| 2835                                                              | Routing-Rule-Report                   | Grouped          |                |
+| 2836                                                              | Traffic-Steering-Policy-Identifier-DL | OctetString      |                |
+| 2837                                                              | Traffic-Steering-Policy-Identifier-UL | OctetString      |                |
+| 2838                                                              | Request-Type                          | Unsigned32       |                |
+| 2839                                                              | Execution-Time                        | Time             |                |
+| 2840                                                              | Conditional-Policy-Information        | Grouped          |                |
+| 2841                                                              | Resource-Release-Notification         | Enumerated       |                |
+| 2842                                                              | Removal-Of-Access                     | Enumerated       |                |
+| 2843                                                              | TCP-Source-Port                       | Unsigned32       |                |
+| 2844                                                              | Default-Bearer-Indication             | Enumerated       |                |
+| 2845                                                              | PRA-Install                           | Grouped          |                |
+| 2846                                                              | PRA-Remove                            | Grouped          |                |
+| 2847                                                              | 3GPP-PS-Data-Off-Status               | Enumerated       |                |
+| 2848                                                              | Extended-APN-AMBR-DL                  | Unsigned32       |                |
+| 2849                                                              | Extended-APN-AMBR-UL                  | Unsigned32       |                |
+| 2850                                                              | Extended-GBR-DL                       | Unsigned32       |                |
+| 2851                                                              | Extended-GBR-UL                       | Unsigned32       |                |
+| 2852                                                              | Max-PLR-DL                            | Unsigned32       |                |
+| 2853                                                              | Max-PLR-UL                            | Unsigned32       |                |
+| 2854                                                              | UE-Status                             | Unsigned32       |                |
+| Note: The AVP codes from 2855 to 2899 are reserved for TS 29.212. |                                       |                  |                |
+| 2900                                                              | reserved                              | -                |                |
+| 2901                                                              | Policy-Counter-Identifier             | Grouped          | 29.219<br>[26] |
+| 2902                                                              | Policy-Counter-Status                 | UTF8String       |                |
+| 2903                                                              | Policy-Counter-Status-Report          | Grouped          |                |
+| 2904                                                              | SL-Request-Type                       | Enumerated       |                |
+| 2905                                                              | Pending-Policy-Counter-Information    | Grouped          |                |
+| 2906                                                              | Pending-Policy-Counter-Change-Time    | Time             |                |
+| 2907                                                              | SN-Request-Type                       | Unsigned32       |                |
+| Note: The AVP codes from 2908 to 2999 are reserved for TS 29.219. |                                       |                  |                |
+| 3000                                                              | reserved                              | -                |                |
+| 3001                                                              | Device-Action                         | Grouped          | 29.368<br>[27] |
+| 3002                                                              | Device-Notification                   | Grouped          |                |
+| 3003                                                              | Trigger-Data                          | Grouped          |                |
+| 3004                                                              | Payload                               | OctetString      |                |
+| 3005                                                              | Action-Type                           | Enumerated       |                |
+| 3006                                                              | Priority-Indication                   | Enumerated       |                |
+| 3007                                                              | Reference-Number                      | Unsigned32       |                |
+| 3008                                                              | Request-Status                        | Enumerated       |                |
+| 3009                                                              | Delivery-Outcome                      | Enumerated       |                |
+| 3010                                                              | Application-Port-Identifier           | Unsigned32       |                |
+| 3011                                                              | Old-Reference-Number                  | Unsigned32       |                |
+| 3012                                                              | Feature-Supported-In-Final-Target     | Unsigned32       |                |
+| Note: The AVP codes from 3013 to 3099 are reserved for TS 29.368. |                                       |                  |                |
+| 3100                                                              | IP-SM-GW-Number                       | OctetString      | 29.336<br>[28] |
+| 3101                                                              | IP-SM-GW-Name                         | DiameterIdentity |                |
+| 3102                                                              | User-Identifier                       | Grouped          |                |
+| 3103                                                              | Service-ID                            | Enumerated       |                |
+| 3104                                                              | SCS-Identity                          | OctetString      |                |
+| 3105                                                              | Service-Parameters                    | Grouped          |                |
+| 3106                                                              | T4-Parameters                         | Grouped          |                |
+| 3107                                                              | Service-Data                          | Grouped          |                |
+| 3108                                                              | T4-Data                               | Grouped          |                |
+| 3109                                                              | HSS-Cause                             | Unsigned32       |                |
+| 3110                                                              | SIR-Flags                             | Unsigned32       |                |
+| 3111                                                              | External-Identifier                   | UTF8String       |                |
+| 3112                                                              | IP-SM-GW-Realm                        | DiameterIdentity |                |
+| 3113                                                              | AESE-Communication-Pattern            | Grouped          |                |
+| 3114                                                              | Communication-Pattern-Set             | Grouped          |                |
+| 3115                                                              | Periodic-Communication-Indicator      | Unsigned32       |                |
+
+|      |                                          |                  |
+|------|------------------------------------------|------------------|
+| 3116 | Communication-Duration-Time              | Unsigned32       |
+| 3117 | Periodic-Time                            | Unsigned32       |
+| 3118 | Scheduled-Communication-Time             | Grouped          |
+| 3119 | Stationary-Indication                    | Unsigned32       |
+| 3120 | AESE-Communication-Pattern-Config-Status | Grouped          |
+| 3121 | AESE-Error-Report                        | Grouped          |
+| 3122 | Monitoring-Event-Configuration           | Grouped          |
+| 3123 | Monitoring-Event-Report                  | Grouped          |
+| 3124 | SCEF-Reference-ID                        | Unsigned32       |
+| 3125 | SCEF-ID                                  | DiameterIdentity |
+| 3126 | SCEF-Reference-ID-for-Deletion           | Unsigned32       |
+| 3127 | Monitoring-Type                          | Unsigned32       |
+| 3128 | Maximum-Number-of-Reports                | Unsigned32       |
+| 3129 | UE-Reachability-Configuration            | Grouped          |
+| 3130 | Monitoring-Duration                      | Time             |
+| 3131 | Maximum-Detection-Time                   | Unsigned32       |
+| 3132 | Reachability-Type                        | Unsigned32       |
+| 3133 | Maximum-Latency                          | Unsigned32       |
+| 3134 | Maximum-Response-Time                    | Unsigned32       |
+| 3135 | Location-Information-Configuration       | Grouped          |
+| 3136 | MONTE-Location-Type                      | Unsigned32       |
+| 3137 | Accuracy                                 | Unsigned32       |
+| 3138 | Association-Type                         | Unsigned32       |
+| 3139 | Roaming-Information                      | Unsigned32       |
+| 3140 | Reachability-Information                 | Unsigned32       |
+| 3141 | IMEI-Change                              | Unsigned32       |
+| 3142 | Monitoring-Event-Config-Status           | Grouped          |
+| 3143 | Supported-Service                        | Grouped          |
+| 3144 | Supported-Monitoring-Event               | Unsigned64       |
+| 3145 | CIR-Flags                                | Unsigned32       |
+| 3146 | Service-Result                           | Grouped          |
+| 3147 | Service-Result-Code                      | Unsigned32       |
+| 3148 | Reference-ID-Validity-Time               | Time             |
+| 3149 | Event-handling                           | Unsigned32       |
+| 3150 | NIDD-Authorization-Request               | Grouped          |
+| 3151 | NIDD-Authorization-Response              | Grouped          |
+| 3152 | Service-Report                           | Grouped          |
+| 3153 | Node-Type                                | Unsigned32       |
+| 3154 | S6t-HSS-Cause                            | Unsigned32       |
+| 3155 | Enhanced-Coverage-Restriction            | Grouped          |
+| 3156 | Enhanced-Coverage-Restriction-Data       | Grouped          |
+| 3157 | Restricted-PLMN-List                     | Grouped          |
+| 3158 | Allowed-PLMN-List                        | Grouped          |
+| 3159 | Requested-Validity-Time                  | Time             |
+| 3160 | Granted-Validity-Time                    | Time             |
+| 3161 | NIDD-Authorization-Update                | Grouped          |
+| 3162 | Loss-Of-Connectivity-Reason              | Unsigned32       |
+| 3163 | Group-Reporting-Guard-Timer              | Unsigned32       |
+| 3164 | CIA-Flags                                | Unsigned32       |
+| 3165 | Group-Report                             | Grouped          |
+| 3166 | Group-Report-Item                        | Grouped          |
+| 3167 | RIR-Flags                                | Unsigned32       |
+| 3168 | Type-Of-External-Identifier              | Unsigned32       |
+| 3169 | APN-Validity-Time                        | Grouped          |
+| 3170 | Suggested-Network-Configuration          | Grouped          |
+| 3171 | Monitoring-Event-Report-Status           | Grouped          |
+| 3172 | PLMN-ID-Requested                        | Enumerated       |
+| 3173 | AdditionalIdentifiers                    | Grouped          |
+| 3174 | NIR-Flags                                | Unsigned32       |
+| 3175 | Reporting-Time-Stamp                     | Time             |
+| 3176 | Group-User-Identifier                    | Grouped          |
+| 3177 | NIA-Flags                                | Unsigned32       |
+| 3178 | MTC-Provider-Info                        | Grouped          |
+| 3179 | MTC-Provider-ID                          | UTF8String       |
+| 3180 | PDN-Connectivity-Status-Configuration    | Grouped          |
+
+|                                                                   |                                           |                  |                |
+|-------------------------------------------------------------------|-------------------------------------------|------------------|----------------|
+| 3181                                                              | PDN-Connectivity-Status-Report            | Grouped          |                |
+| 3182                                                              | PDN-Connectivity-Status-Type              | Unsigned32       |                |
+| 3183                                                              | Traffic-Profile                           | Unsigned32       |                |
+| 3184                                                              | Updated-Network-Configuration             | Grouped          |                |
+| 3185                                                              | Battery-Indicator                         | Unsigned32       |                |
+| 3186                                                              | SCEF-Reference-ID-Ext                     | Unsigned64       |                |
+| 3187                                                              | SCEF-Reference-ID-for-Deletion-Ext        | Unsigned64       |                |
+| Note: The AVP codes from 3188 to 3199 are reserved for TS 29.336. |                                           |                  |                |
+| 3200                                                              | SM-Delivery-Outcome-T4                    | Enumerated       | 29.337<br>[29] |
+| 3201                                                              | Absent-Subscriber-Diagnostic-T4           | Enumerated       |                |
+| 3202                                                              | Trigger-Action                            | Unsigned32       |                |
+| 3203                                                              | MTC-Error-Diagnostic                      | Unsigned32       |                |
+| Note: The AVP codes from 3204 to 3299 are reserved for TS 29.337. |                                           |                  |                |
+| 3300                                                              | SC-Address                                | OctetString      | 29.338<br>[30] |
+| 3301                                                              | SM-RP-UI                                  | OctetString      |                |
+| 3302                                                              | TFR-Flags                                 | Unsigned32       |                |
+| 3303                                                              | SM-Delivery- Failure-Cause                | Grouped          |                |
+| 3304                                                              | SM-Enumerated-Delivery-Failure-Cause      | Enumerated       |                |
+| 3305                                                              | SM-Diagnostic-Info                        | OctetString      |                |
+| 3306                                                              | SM-Delivery-Timer                         | Unsigned32       |                |
+| 3307                                                              | SM-Delivery-Start-Time                    | Time             |                |
+| 3308                                                              | SM-RP-MTI                                 | Enumerated       |                |
+| 3309                                                              | SM-RP-SMEA                                | OctetString      |                |
+| 3310                                                              | SRR-Flags                                 | Unsigned32       |                |
+| 3311                                                              | SM-Delivery-Not-Intended                  | Enumerated       |                |
+| 3312                                                              | MWD-Status                                | Unsigned32       |                |
+| 3313                                                              | MME-Absent-User-Subscriber-Diagnostic-SM  | Unsigned32       |                |
+| 3314                                                              | MSC-Absent-User-Subscriber-Diagnostic-SM  | Unsigned32       |                |
+| 3315                                                              | SGSN-Absent-User-Subscriber-Diagnostic SM | Unsigned32       |                |
+| 3316                                                              | SM-Delivery-Outcome                       | Grouped          |                |
+| 3317                                                              | MME-SM-Delivery-Outcome                   | Grouped          |                |
+| 3318                                                              | MSC-SM-Delivery-Outcome                   | Grouped          |                |
+| 3319                                                              | SGSN-SM-Delivery-Outcome                  | Grouped          |                |
+| 3320                                                              | IP-SM-GW-SM-Delivery-Outcome              | Grouped          |                |
+| 3321                                                              | SM-Delivery-Cause                         | Enumerated       |                |
+| 3322                                                              | Absent-User-Diagnostic-SM                 | Unsigned32       |                |
+| 3323                                                              | RDR-Flags                                 | Unsigned32       |                |
+| 3324                                                              | SMSMI-Correlation-ID                      | Unsigned32       |                |
+| 3325                                                              | HSS-ID                                    | UTF8String       |                |
+| 3326                                                              | Originating-SIP-URI                       | UTF8String       |                |
+| 3327                                                              | Destination-SIP-URI                       | UTF8String       |                |
+| 3328                                                              | OFR-Flags                                 | Unsigned32       |                |
+| 3329                                                              | Maximum-UE-Availability-Time              | Time             |                |
+| 3330                                                              | Maximum-Retransmission-Time               | Time             |                |
+| 3331                                                              | Requested-Retransmission-Time             | Time             |                |
+| 3332                                                              | SMS-GMSC-Address                          | OctetString      |                |
+| 3333                                                              | SMS-GMSC-Alert-Event                      | Unsigned32       |                |
+| 3334                                                              | SMSF-3GPP-Absent-User-Diagnostic-SM       | Unsigned32       |                |
+| 3335                                                              | SMSF-Non-3GPP-Absent-User-Diagnostic-SM   | Unsigned32       |                |
+| 3336                                                              | SMSF-3GPP-SM-Delivery-Outcome             | Grouped          |                |
+| 3337                                                              | SMSF-Non-3GPP-SM-Delivery-Outcome         | Grouped          |                |
+| 3338                                                              | SMSF-3GPP-Number                          | OctetString      |                |
+| 3339                                                              | SMSF-Non-3GPP-Number                      | OctetString      |                |
+| 3340                                                              | SMSF-3GPP-Name                            | DiameterIdentity |                |
+| 3341                                                              | SMSF-Non-3GPP-Name                        | DiameterIdentity |                |
+| 3342                                                              | SMSF-3GPP-Realm                           | DiameterIdentity |                |
+| 3343                                                              | SMSF-Non-3GPP-Realm                       | DiameterIdentity |                |
+| 3344                                                              | SMSF-3GPP-Address                         | Grouped          |                |
+| 3345                                                              | SMSF-Non-3GPP-Address                     | Grouped          |                |
+| Note: The AVP codes from 3346 to 3399 are reserved for TS 29.338. |                                           |                  |                |
+| 3400                                                              | reserved                                  | -                | 32.299 [5]     |
+| 3401                                                              | Reason-Header                             | UTF8String       |                |
+| 3402                                                              | Instance-Id                               | UTF8String       |                |
+| 3403                                                              | Route-Header-Received                     | UTF8String       |                |
+| 3404                                                              | Route-Header-Transmitted                  | UTF8String       |                |
+
+|      |                                                        |             |
+|------|--------------------------------------------------------|-------------|
+| 3405 | SM-Device-Trigger-Information                          | Grouped     |
+| 3406 | MTC-IWF-Address                                        | Address     |
+| 3407 | SM-Device-Trigger-Indicator                            | Enumerated  |
+| 3408 | SM-Sequence-Number                                     | Unsigned32  |
+| 3409 | SMS-Result                                             | Unsigned32  |
+| 3410 | VCS-Information                                        | Grouped     |
+| 3411 | Basic-Service-Code                                     | Grouped     |
+| 3412 | Bearer-Capability                                      | OctetString |
+| 3413 | Teleservice                                            | OctetString |
+| 3414 | ISUP-Location-Number                                   | OctetString |
+| 3415 | Forwarding-Pending                                     | Enumerated  |
+| 3416 | ISUP-Release-Cause                                     | Unsigned32  |
+| 3417 | MSC-Address                                            | OctetString |
+| 3418 | Network-Call-Reference-Number                          | OctetString |
+| 3419 | Start-of-Charging                                      | Time        |
+| 3420 | VLR-Number                                             | OctetString |
+| 3421 | CN-Operator-Selection-Entity                           | Enumerated  |
+| 3422 | ISUP-Cause-Diagnostics                                 | OctetString |
+| 3423 | ISUP-Cause-Location                                    | Unsigned32  |
+| 3424 | ISUP-Cause-Value                                       | Unsigned32  |
+| 3425 | EPDG-Address                                           | Address     |
+| 3426 | Announcing-UE-HPLMN-Identifier                         | UTF8String  |
+| 3427 | Announcing-UE-VPLMN-Identifier                         | UTF8String  |
+| 3428 | Coverage-Status                                        | Enumerated  |
+| 3429 | Layer-2-Group-ID                                       | OctetString |
+| 3430 | Monitored-PLMN-Identifier                              | UTF8String  |
+| 3431 | Monitoring-UE-HPLMN-Identifier                         | UTF8String  |
+| 3432 | Monitoring-UE-Identifier                               | UTF8String  |
+| 3433 | Monitoring-UE-VPLMN-Identifier                         | UTF8String  |
+| 3434 | ProSe-PC3-Control-Protocol-Cause                       | Integer32   |
+| 3435 | ProSe-PC3-EPC-Control-Protocol-Cause                   | Integer32   |
+| 3436 | Requested-PLMN-Identifier                              | UTF8String  |
+| 3437 | Requestor-PLMN-Identifier                              | UTF8String  |
+| 3438 | Role-Of-ProSe-Function                                 | Enumerated  |
+| 3439 | Usage-Information-Report-Sequence-Number               | Integer32   |
+| 3440 | ProSe-3rd-Party-Application-ID                         | UTF8String  |
+| 3441 | ProSe-Direct-Communication-Transmission-Data-Container | Grouped     |
+| 3442 | ProSe-Direct-Discovery-Model                           | Enumerated  |
+| 3443 | ProSe-Event-Type                                       | Enumerated  |
+| 3444 | ProSe-Function-IP-Address                              | Address     |
+| 3445 | ProSe-Functionality                                    | Enumerated  |
+| 3446 | ProSe-Group-IP-Multicast-Addresses                     | Address     |
+| 3447 | ProSe-Information                                      | Grouped     |
+| 3448 | ProSe-Range-Class                                      | Enumerated  |
+| 3449 | ProSe-Reason-For-Cancellation                          | Enumerated  |
+| 3450 | ProSe-Request-Timestamp                                | Time        |
+| 3451 | ProSe-Role-Of-UE                                       | Enumerated  |
+| 3452 | ProSe-Source-IP-Address                                | Address     |
+| 3453 | ProSe-UE-ID                                            | OctetString |
+| 3454 | Proximity-Alert-Indication                             | Enumerated  |
+| 3455 | Proximity-Alert-Timestamp                              | Time        |
+| 3456 | Proximity-Cancellation-Timestamp                       | Time        |
+| 3457 | ProSe-Function-PLMN-Identifier                         | UTF8String  |
+| 3458 | Application-Specific-Data                              | OctetString |
+| 3459 | Coverage-Info                                          | Grouped     |
+| 3460 | Location-Info                                          | Grouped     |
+| 3461 | ProSe-Direct-Communication-Reception-Data-Container    | Grouped     |
+| 3462 | Radio-Frequency                                        | OctetString |
+| 3463 | Radio-Parameter-Set-Info                               | Grouped     |
+| 3464 | Radio-Parameter-Set-Values                             | OctetString |
+| 3465 | Radio-Resources-Indicator                              | Integer32   |
+| 3466 | Time-First-Reception                                   | Time        |
+| 3467 | Time-First-Transmission                                | Time        |
+| 3468 | Transmitter-Info                                       | Grouped     |
+
+Note: The AVP codes from 3469 to 3499 are reserved for TS 32.299.
+
+|                                                                   |                                    |             |                |
+|-------------------------------------------------------------------|------------------------------------|-------------|----------------|
+| 3500                                                              | BMSC-Address                       | Address     | 29.468<br>[31] |
+| 3501                                                              | BMSC-Port                          | Unsigned32  |                |
+| 3502                                                              | MBMS-Bearer-Event                  | Unsigned32  |                |
+| 3503                                                              | MBMS-Bearer-Event-Notification     | Grouped     |                |
+| 3504                                                              | MBMS-Bearer-Request                | Grouped     |                |
+| 3505                                                              | MBMS-Bearer-Response               | Grouped     |                |
+| 3506                                                              | MBMS-Bearer-Result                 | Unsigned32  |                |
+| 3507                                                              | MBMS-Start-Time                    | Time        |                |
+| 3508                                                              | Radio-Frequency                    | Unsigned32  |                |
+| 3509                                                              | TMGI-Allocation-Request            | Grouped     |                |
+| 3510                                                              | TMGI-Allocation-Response           | Grouped     |                |
+| 3511                                                              | TMGI-Allocation-Result             | Unsigned32  |                |
+| 3512                                                              | TMGI-Deallocation-Request          | Grouped     |                |
+| 3513                                                              | TMGI-Deallocation-Response         | Grouped     |                |
+| 3514                                                              | TMGI-Deallocation-Result           | Unsigned32  |                |
+| 3515                                                              | TMGI-Expiry                        | Grouped     |                |
+| 3516                                                              | TMGI-Number                        | Unsigned32  |                |
+| 3517                                                              | MB2U-Security                      | Unsigned32  |                |
+| 3518                                                              | Local-M1-Information               | Grouped     |                |
+| 3519                                                              | Local-MB2-U-Information            | Grouped     |                |
+| 3520                                                              | MBMS-eNB-IP-Multicast-Address      | Address     |                |
+| 3521                                                              | MBMS-eNB-IPv6-Multicast-Address    | Address     |                |
+| 3522                                                              | MBMS-GW-SSM-IP-Address             | Address     |                |
+| 3523                                                              | MBMS-GW-SSM-IPv6-Address           | Address     |                |
+| 3524                                                              | Common-Tunnel-Endpoint-Identifier  | OctetString |                |
+| 3525                                                              | FEC-Request                        | OctetString |                |
+| 3526                                                              | ROHC-Request                       | Grouped     |                |
+| 3527                                                              | ROHC-Full-Header-Periodicity       | Float32     |                |
+| 3528                                                              | ROHC-Profile                       | Unsigned32  |                |
+| 3529                                                              | Userplane-Protocol-Result          | Grouped     |                |
+| 3530                                                              | ROHC-Result                        | Unsigned32  |                |
+| 3531                                                              | FEC-Result                         | Unsigned32  |                |
+| 3532                                                              | ROHC-Max-CID                       | Unsigned32  |                |
+| Note: The AVP codes from 3533 to 3599 are reserved for TS 29.468. |                                    |             |                |
+| 3600                                                              | Origin-App-Layer-User-Id           | UTF8String  | 29.343<br>[32] |
+| 3601                                                              | Target-App-Layer-User-Id           | UTF8String  |                |
+| 3602                                                              | ProSe-Function-ID                  | OctetString |                |
+| 3603                                                              | ProSe-Request-Type                 | Unsigned32  |                |
+| 3604                                                              | PDUID                              | OctetString |                |
+| 3605                                                              | Application-Data                   | UTF8String  |                |
+| 3606                                                              | Allowed-Suffixes-Number            | Unsigned32  |                |
+| 3607                                                              | Monitor-Target                     | Grouped     |                |
+| 3608                                                              | ProSe-Code-Suffix-Mask             | Grouped     |                |
+| 3609                                                              | Suffix-Code                        | OctetString |                |
+| 3610                                                              | Suffix-Mask                        | OctetString |                |
+| 3611                                                              | Banned-User-Target                 | Grouped     |                |
+| 3612                                                              | Metadata-Indicator                 | Unsigned32  |                |
+| Note: The AVP codes from 3613 to 3699 are reserved for TS 29.343. |                                    |             |                |
+| 3701                                                              | ProSe-Subscription-Data            | Grouped     | 29.344<br>[33] |
+| 3702                                                              | ProSe-Permission                   | Unsigned32  |                |
+| 3703                                                              | ProSe-Allowed-PLMN                 | Grouped     |                |
+| 3704                                                              | ProSe-Direct-Allowed               | Unsigned32  |                |
+| 3705                                                              | UPR-Flags                          | Unsigned32  |                |
+| 3706                                                              | PNR-Flags                          | Unsigned32  |                |
+| 3707                                                              | ProSe-Initial-Location-Information | Grouped     |                |
+| 3708                                                              | Authorized-Discovery-Range         | Unsigned32  |                |
+| Note: The AVP codes from 3709 to 3799 are reserved for TS 29.344. |                                    |             |                |
+| 3800                                                              | Reserved                           |             | 29.345<br>[34] |
+| 3801                                                              | App-Layer-User-Id                  | UTF8String  |                |
+| 3802                                                              | Assistance-info                    | Grouped     |                |
+| 3803                                                              | Assistance-Info-Validity-Timer     | Unsigned32  |                |
+| 3804                                                              | Discovery-Type                     | Unsigned32  |                |
+| 3805                                                              | Filter-Id                          | OctetString |                |
+| 3806                                                              | MAC-Address                        | UTF8String  |                |
+| 3807                                                              | Match-Report                       | Grouped     |                |
+
+|                                                                   |                                    |             |            |
+|-------------------------------------------------------------------|------------------------------------|-------------|------------|
+| 3808                                                              | Operating-Channel                  | Unsigned32  |            |
+| 3809                                                              | P2P-Features                       | Unsigned32  |            |
+| 3810                                                              | ProSe-App-Code                     | UTF8String  |            |
+| 3811                                                              | ProSe-App-Id                       | UTF8String  |            |
+| 3812                                                              | ProSe-App-Mask                     | UTF8String  |            |
+| 3813                                                              | ProSe-Discovery-Filter             | Grouped     |            |
+| 3814                                                              | PRR-Flags                          | Unsigned32  |            |
+| 3815                                                              | ProSe-Validity-Timer               | Unsigned32  |            |
+| 3816                                                              | Requesting-EPUID                   | UTF8String  |            |
+| 3817                                                              | Targeted-EPUID                     | UTF8String  |            |
+| 3818                                                              | Time-Window                        | Unsigned32  |            |
+| 3819                                                              | WiFi-P2P-Assistance-Info           | Grouped     |            |
+| 3820                                                              | WLAN-Assistance-Info               | Grouped     |            |
+| 3821                                                              | WLAN-Link-Layer-Id                 | OctetString |            |
+| 3822                                                              | WLAN-Link-Layer-Id-List            | Grouped     |            |
+| 3823                                                              | Location-Update-Trigger            | Grouped     |            |
+| 3824                                                              | Location-Update-Event-Type         | Unsigned32  |            |
+| 3825                                                              | Change-Of-Area-Type                | Grouped     |            |
+| 3826                                                              | Location-Update-Event-Trigger      | Unsigned32  |            |
+| 3827                                                              | Report-Cardinality                 | Enumerated  |            |
+| 3828                                                              | Minimum-Interval-Time              | Unsigned32  |            |
+| 3829                                                              | Periodic-Location-Type             | Grouped     |            |
+| 3830                                                              | Location-Report-Interval-Time      | Unsigned32  |            |
+| 3831                                                              | Total-Number-Of-Reports            | Unsigned32  |            |
+| 3832                                                              | Validity-Time-Announce             | Unsigned32  |            |
+| 3833                                                              | Validity-Time-Monitor              | Unsigned32  |            |
+| 3834                                                              | Validity-Time-Communication        | Unsigned32  |            |
+| 3835                                                              | ProSe-App-Code-Info                | Grouped     |            |
+| 3836                                                              | MIC                                | OctetString |            |
+| 3837                                                              | UTC-based-Counter                  | Unsigned32  |            |
+| 3838                                                              | ProSe-Match-Refresh-Timer          | Unsigned32  |            |
+| 3839                                                              | ProSe-Metadata-Index-Mask          | OctetString |            |
+| 3840                                                              | App-Identifier                     | Grouped     |            |
+| 3841                                                              | OS-ID                              | OctetString |            |
+| 3842                                                              | OS-App-ID                          | UTF8String  |            |
+| 3843                                                              | Requesting-RPAUID                  | UTF8String  |            |
+| 3844                                                              | Target-RPAUID                      | UTF8String  |            |
+| 3845                                                              | Target-PDUID                       | OctetString |            |
+| 3846                                                              | ProSe-Restricted-Code              | OctetString |            |
+| 3847                                                              | ProSe-Restricted-Code-Suffix-Range | OctetString |            |
+| 3848                                                              | Beginning-Suffix                   | OctetString |            |
+| 3849                                                              | Ending-Suffix                      | OctetString |            |
+| 3850                                                              | Discovery-Entry-ID                 | Unsigned32  |            |
+| 3851                                                              | Match-Timestamp                    | Time        |            |
+| 3852                                                              | PMR-Flags                          | Unsigned32  |            |
+| 3853                                                              | ProSe-Application-Metadata         | UTF8String  |            |
+| 3854                                                              | Discovery-Auth-Request             | Grouped     |            |
+| 3855                                                              | Discovery-Auth-Response            | Grouped     |            |
+| 3856                                                              | Match-Request                      | Grouped     |            |
+| 3857                                                              | Match-Report-Info                  | Grouped     |            |
+| 3858                                                              | Banned-RPAUID                      | UTF8String  |            |
+| 3859                                                              | Banned-PDUID                       | OctetString |            |
+| 3860                                                              | Code-Receiving-Security-Material   | Grouped     |            |
+| 3861                                                              | Code-Sending-Security-Material     | Grouped     |            |
+| 3862                                                              | DUSK                               | OctetString |            |
+| 3863                                                              | DUIK                               | OctetString |            |
+| 3864                                                              | DUCK                               | OctetString |            |
+| 3865                                                              | MIC-Check-indicator                | Unsigned32  |            |
+| 3866                                                              | Encrypted-Bitmask                  | OctetString |            |
+| 3867                                                              | ProSe-App-Code-Suffix-Range        | OctetString |            |
+| 3868                                                              | PC5-tech                           | OctetString |            |
+| Note: The AVP codes from 3869 to 3899 are reserved for TS 29.345. |                                    |             |            |
+| 3900                                                              | Reserved                           |             |            |
+| 3901                                                              | Enhanced-Diagnostics               | Grouped     | 32.299 [5] |
+| 3902                                                              | Inter-UE-Transfer                  | Enumerated  |            |
+
+|                                                                   |                                         |                  |        |
+|-------------------------------------------------------------------|-----------------------------------------|------------------|--------|
+| 3903                                                              | TWAG-Address                            | Address          |        |
+| 3904                                                              | Announcement-Information                | Grouped          |        |
+| 3905                                                              | Announcement-Identifier                 | Unsigned32       |        |
+| 3906                                                              | Announcement-Order                      | Unsigned32       |        |
+| 3907                                                              | Variable-Part                           | Grouped          |        |
+| 3908                                                              | Variable-Part-Order                     | Unsigned32       |        |
+| 3909                                                              | Variable-Part-Type                      | Unsigned32       |        |
+| 3910                                                              | Variable-Part-Value                     | UTF8String       |        |
+| 3911                                                              | Time-Indicator                          | Unsigned32       |        |
+| 3912                                                              | Quota-Indicator                         | Enumerated       |        |
+| 3913                                                              | Play-Alternative                        | Enumerated       |        |
+| 3914                                                              | Language                                | UTF8String       |        |
+| 3915                                                              | Privacy-Indicator                       | Enumerated       |        |
+| 3916                                                              | Called-Identity                         | UTF8String       |        |
+| 3917                                                              | Called-Identity-Change                  | Grouped          |        |
+| 3918                                                              | UWAN-User-Location-Info                 | Grouped          |        |
+| 3919                                                              | Monitoring-Event-Configuration-Activity | Integer32        |        |
+| 3920                                                              | Monitoring-Event-Report-Data            | Grouped          |        |
+| 3921                                                              | Monitoring-Event-Information            | Grouped          |        |
+| 3922                                                              | Monitoring-Event-Functionality          | Integer32        |        |
+| 3923                                                              | Monitoring-Event-Report-Number          | Unsigned32       |        |
+| 3924                                                              | Cellular-Network-Information            | OctetString      |        |
+| 3925                                                              | Related-Change-Condition-Information    | Grouped          |        |
+| 3926                                                              | Related-Trigger                         | Grouped          |        |
+| 3927                                                              | CPDT-Information                        | Grouped          |        |
+| 3928                                                              | NIDD-Submission                         | Grouped          |        |
+| 3929                                                              | Serving-Node-Identity                   | DiameterIdentity |        |
+| 3930                                                              | CP-CIoT-EPS-Optimisation-Indicator      | Enumerated       |        |
+| 3931                                                              | SGi-PtP-Tunnelling-Method               | Enumerated       |        |
+| 3932                                                              | UNI-PDU-CP-Only-Flag                    | Enumerated       |        |
+| 3933                                                              | APN-Rate-Control                        | Grouped          |        |
+| 3934                                                              | APN-Rate-Control-Downlink               | Grouped          |        |
+| 3935                                                              | APN-Rate-Control-Uplink                 | Grouped          |        |
+| 3936                                                              | Additional-Exception-Reports            | Enumerated       |        |
+| 3937                                                              | Rate-Control-Max-Message-Size           | Unsigned32       |        |
+| 3938                                                              | Rate-Control-Max-Rate                   | Unsigned32       |        |
+| 3939                                                              | Rate-Control-Time-Unit                  | Unsigned32       |        |
+| 3940                                                              | SCS-AS-Address                          | Grouped          |        |
+| 3941                                                              | SCS-Address                             | Address          |        |
+| 3942                                                              | SCS-Realm                               | DiameterIdentity |        |
+| Note: The AVP codes from 3943 to 3999 are reserved for TS 32.299. |                                         |                  |        |
+| 4000                                                              | Aggregated-Congestion-Info              | Grouped          |        |
+| 4001                                                              | Aggregated-RUCI-Report                  | Grouped          |        |
+| 4002                                                              | Congestion-Level-Definition             | Grouped          |        |
+| 4003                                                              | Congestion-Level-Range                  | Unsigned32       |        |
+| 4004                                                              | Congestion-Level-Set-Id                 | Unsigned32       |        |
+| 4005                                                              | Congestion-Level-Value                  | Unsigned32       |        |
+| 4006                                                              | Congestion-Location-Id                  | Grouped          |        |
+| 4007                                                              | Conditional-Restriction                 | Unsigned32       |        |
+| 4008                                                              | eNodeB-Id                               | OctetString      |        |
+| 4009                                                              | IMSI-List                               | OctetString      |        |
+| 4010                                                              | RCAF-Id                                 | DiameterIdentity |        |
+| 4011                                                              | Reporting-Restriction                   | Unsigned32       |        |
+| 4012                                                              | RUCI-Action                             | Unsigned32       |        |
+| 4013                                                              | Extended-eNodeB-ID                      | OctetString      |        |
+| Note: The AVP codes from 4014 to 4099 are reserved for TS 29.217. |                                         |                  |        |
+| 4101                                                              | Network-Congestion-Area-Report          | Grouped          | 29.153 |
+| 4102                                                              | Ns-Request-Type                         | Unsigned32       | [37]   |
+| Note: The AVP codes from 4103 to 4199 are reserved for TS 29.153. |                                         |                  |        |
+| 4201                                                              | Network-Area-Info-List                  | OctetString      |        |
+| 4202                                                              | Reference-Id                            | OctetString      |        |
+| 4203                                                              | Transfer-Request-Type                   | Unsigned32       | 29.154 |
+| 4204                                                              | Time-Window                             | Grouped          | [38]   |
+| 4205                                                              | Transfer-End-Time                       | Time             |        |
+| 4206                                                              | Transfer-Start-Time                     | Time             |        |
+
+29.217  
+[35]29.153  
+[37]29.154  
+[38]
+
+|                                                                   |                                         |             |  |
+|-------------------------------------------------------------------|-----------------------------------------|-------------|--|
+| 4207                                                              | Transfer-Policy                         | Grouped     |  |
+| 4208                                                              | Transfer-Policy-Id                      | Unsigned32  |  |
+| 4209                                                              | Number-Of-UEs                           | Unsigned32  |  |
+| 4210                                                              | Access-Network-Reports                  | Grouped     |  |
+| 4211                                                              | Event-Configuration                     | Grouped     |  |
+| 4212                                                              | Event-Configuration-State               | Unsigned32  |  |
+| 4213                                                              | Event-Configuration-Status              | Grouped     |  |
+| 4214                                                              | Event-Reporting-Results                 | Unsigned32  |  |
+| 4215                                                              | Event-Reports                           | Grouped     |  |
+| 4216                                                              | Extended-SCEF-Reference-ID              | Unsigned64  |  |
+| Note: The AVP codes from 4217 to 4299 are reserved for TS 29.154. |                                         |             |  |
+| 4300                                                              | Communication-Failure-Information       | Grouped     |  |
+| 4301                                                              | Cause-Type                              | Unsigned32  |  |
+| 4302                                                              | S1AP-Cause                              | Unsigned32  |  |
+| 4303                                                              | RANAP-Cause                             | Unsigned32  |  |
+| 4304                                                              | GMM-Cause                               | Unsigned32  |  |
+| 4305                                                              | SM-Cause                                | Unsigned32  |  |
+| 4306                                                              | Number-of-UE-Per-Location-Configuration | Grouped     |  |
+| 4307                                                              | Number-of-UE-Per-Location-Report        | Grouped     |  |
+| 4308                                                              | UE-Count                                | Unsigned32  |  |
+| 4309                                                              | BSSGP-Cause                             | Unsigned32  |  |
+| 4310                                                              | Serving-PLMN-Rate-Control               | Grouped     |  |
+| 4311                                                              | Uplink-Rate-Limit                       | Unsigned32  |  |
+| 4312                                                              | Downlink-Rate-Limit                     | Unsigned32  |  |
+| 4313                                                              | Extended-PCO                            | OctetString |  |
+| 4314                                                              | Connection-Action                       | Unsigned32  |  |
+| 4315                                                              | Non-IP-Data                             | OctetString |  |
+| 4316                                                              | SCEF-Wait-Time                          | Time        |  |
+| 4317                                                              | CMR-Flags                               | Unsigned32  |  |
+| 4318                                                              | RR-Cause-Counter                        | Grouped     |  |
+| 4319                                                              | Counter-Value                           | Unsigned32  |  |
+| 4320                                                              | RR-Counter-Timestamp                    | Time        |  |
+| 4321                                                              | TDA-Flags                               | Unsigned32  |  |
+| 4322                                                              | Idle-Status-Indication                  | Grouped     |  |
+| 4323                                                              | Idle-Status-Timestamp                   | Time        |  |
+| 4324                                                              | Active-Time                             | Unsigned32  |  |
+| 4325                                                              | Reachability-Cause                      | Unsigned32  |  |
+| 4326                                                              | APN-Rate-Control-Status                 | Grouped     |  |
+| 4327                                                              | Uplink-Number-Of-Packets-Allowed        | Unsigned32  |  |
+| 4328                                                              | Number-Of-Additional-Exception-Reports  | Unsigned32  |  |
+| 4329                                                              | Downlink-Number-Of-Packets-Allowed      | Unsigned32  |  |
+| 4330                                                              | APN-Rate-Control-Status-Validity-Time   | Unsigned64  |  |
+| Note: The AVP codes from 4331 to 4399 are reserved for TS 29.128. |                                         |             |  |
+| 4400                                                              | Charging-Per-IP-CAN-Session-Indicator   | Enumerated  |  |
+| 4401                                                              | Access-Network-Info-Change              | Enumerated  |  |
+| 4402                                                              | Discoveree-UE-HPLMN-Identifier          | UTF8String  |  |
+| 4403                                                              | Discoveree-UE-VPLMN-Identifier          | UTF8String  |  |
+| 4404                                                              | Discoverer-UE-HPLMN-Identifier          | UTF8String  |  |
+| 4405                                                              | Discoverer-UE-VPLMN-Identifier          | UTF8String  |  |
+| 4406                                                              | 3GPP-PS-Data-Off-Status                 | Enumerated  |  |
+| 4407                                                              | Unused-Quota-Timer                      | Unsigned32  |  |
+| 4408                                                              | Announcing-PLMN-ID                      | UTF8String  |  |
+| 4409                                                              | ProSe-UE-to-Network-Relay-UE-ID         | OctetString |  |
+| 4410                                                              | ProSe-Target-Layer-2-ID                 | OctetString |  |
+| 4411                                                              | Relay-IP-address                        | Address     |  |
+| 4412                                                              | Target-IP-Address                       | Address     |  |
+| 4413                                                              | FE-Identifier-List                      | UTF8String  |  |
+| Note: The AVP codes from 4414 to 4499 are reserved for TS 32.299  |                                         |             |  |
+| 4500                                                              | MCPTT-ID                                | UTF8String  |  |
+| 4501                                                              | Data-Identification                     | Grouped     |  |
+| 4502                                                              | Data-Identification-Prefix              | Unsigned32  |  |
+| 4503                                                              | Data-Identification-Flags               | Unsigned64  |  |
+| 4504                                                              | DPR-Flags                               | Unsigned32  |  |
+| 4505                                                              | DPA-Flags                               | Unsigned32  |  |
+| 4506                                                              | DUR-Flags                               | Unsigned32  |  |
+
+29.128  
+[36]
+
+32.299 [5]
+
+29.283  
+[39]
+
+|                                                                          |                              |            |                |
+|--------------------------------------------------------------------------|------------------------------|------------|----------------|
+| 4507                                                                     | DUA-Flags                    | Unsigned32 |                |
+| 4508                                                                     | NDR-Flags                    | Unsigned32 |                |
+| 4509                                                                     | NDA-Flags                    | Unsigned32 |                |
+| 4510                                                                     | User-Data-Id                 | Unsigned32 |                |
+| 4511                                                                     | MC-Service-User-Profile-Data | Grouped    |                |
+| 4512                                                                     | Sequence-Number              | Unsigned32 |                |
+| 4513                                                                     | MCVideo-ID                   | UTF8String |                |
+| 4514                                                                     | MC-Data-ID                   | UTF8String |                |
+| Note: The AVP codes from 4515 to 4599 are reserved for TS 29.283.        |                              |            |                |
+| 4600                                                                     | V2X-PC5-Allowed-PLMN         | Grouped    | 29.388<br>[40] |
+| 4601                                                                     | V2X-Update-Flags             | Unsigned32 |                |
+| 4602                                                                     | V2X-Notify-Flags             | Unsigned32 |                |
+| 4603                                                                     | PLMN-Allowed-PC5-RATs        | Grouped    |                |
+| 4604                                                                     | PC5-RAT-Type                 | Enumerated |                |
+| Note: The AVP codes from 4605 to 4799 are reserved for TS 29.388.        |                              |            |                |
+| 4700                                                                     | V2X-Authorization-Data       | Grouped    | 29.389<br>[41] |
+| 4701                                                                     | V2X-Permission-in-VPLMN      | Unsigned32 |                |
+| 4702                                                                     | V2X-Application-Server       | Grouped    |                |
+| Note: The AVP codes from 4703 to 4799 are reserved for TS and TS 29.389. |                              |            |                |
+|                                                                          |                              |            | 29.561<br>[42] |
+| Note: The AVP codes from 4800 to 4999 are reserved for TS and TS 29.561. |                              |            |                |
+
+# 8 Experimental result codes
+
+The Diameter answer messages must carry either Result-Code AVP or Experimental-Result AVP. The values of Result-Code AVP are controlled by IANA. The Experimental-Result AVP is a grouped AVP containing the Vendor-Id AVP and Experimental-Result-Code AVP, thus the experimental result codes are controlled in a vendor-specific manner.
+
+## 8.1 3GPP specific result codes
+
+The 3GPP specific result codes are always transferred in the Experimental-Result AVP, which has the Vendor-Id with value of 3GPP's vendor identifier. The 3GPP specific result codes shall follow the same classification as defined for the values of Result-Code AVP in IETF RFC 3588 [9]. That means, the result codes are grouped to following ranges:
+
+- 1xxx (Informational)
+- 2xxx (Success)
+- 4xxx (Transient Failures)
+- 5xxx (Permanent Failures)
+
+### 8.1.1 Informational
+
+The Informational result codes shall use the values from 1001 to 1999 in the Experimental-Result-Code AVP.
+
+**Editor's note:** No informational result codes have been yet defined in 3GPP.
+
+### 8.1.2 Success
+
+The Success result codes shall use the values from 2001 to 2999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Success result codes are presented in the following table.
+
+Table 8.1.2: 3GPP specific Success result codes
+
+| Experimental Result Code                                                              | Result text                              | Specified in the TS |
+|---------------------------------------------------------------------------------------|------------------------------------------|---------------------|
+| 2001                                                                                  | DIAMETER_FIRST_REGISTRATION              | 29.229 [2]          |
+| 2002                                                                                  | DIAMETER_SUBSEQUENT_REGISTRATION         |                     |
+| 2003                                                                                  | DIAMETER_UNREGISTERED_SERVICE            |                     |
+| 2004                                                                                  | DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED  |                     |
+| 2005                                                                                  | <i>Deprecated value</i>                  |                     |
+| Note: The Experimental Result Codes from 2006 to 2020 are reserved for the TS 29.229. |                                          |                     |
+| 2021                                                                                  | DIAMETER_PDP_CONTEXT_DELETION_INDICATION | 29.061 [13]         |
+| Note: The Experimental Result Codes from 2022 to 2040 are reserved for the TS 29.061  |                                          |                     |
+|                                                                                       |                                          | 29.109 [7]          |
+| Note: The Experimental Result Codes from 2401 to 2420 are reserved for the TS 29.109. |                                          |                     |
+| 2421                                                                                  | DIAMETER_QOS_FLOW_DELETION_INDICATION    | 29.561 [42]         |
+| Note: The Experimental Result Codes from 2422 to 2440 are reserved for the TS 29.561. |                                          |                     |
+
+### 8.1.3 Transient Failures
+
+The Transient Failure result codes shall use the values from 4001 to 4999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Transient Failure result codes are presented in the following table.
+
+Table 8.1.3: 3GPP specific Transient Failure result codes
+
+| Experimental Result Code                                                              | Result text                                   | Specified in the TS |
+|---------------------------------------------------------------------------------------|-----------------------------------------------|---------------------|
+| 4100                                                                                  | DIAMETER_USER_DATA_NOT_AVAILABLE              | 29.329 [4]          |
+| 4101                                                                                  | DIAMETER_PRIOR_UPDATE_IN_PROGRESS             |                     |
+| Note: The Experimental Result Codes from 4102 to 4120 are reserved for the TS 29.329. |                                               |                     |
+| 4121                                                                                  | DIAMETER_ERROR_OUT_OF_RESOURCES               | 29.061 [13]         |
+| Note: The Experimental Result Codes from 4122 to 4140 are reserved for the TS 29.061. |                                               |                     |
+| 4141                                                                                  | DIAMETER_PCC_BEARER_EVENT                     | 29.212 [19]         |
+| 4142                                                                                  | DIAMETER_BEARER_EVENT                         |                     |
+| 4143                                                                                  | DIAMETER_AN_GW_FAILED                         |                     |
+| 4144                                                                                  | DIAMETER_PENDING_TRANSACTION                  |                     |
+| 4145                                                                                  | DIAMETER_UE_STATUS_SUSPEND                    |                     |
+| Note: The Experimental Result Codes from 4146 to 4160 are reserved for the TS 29.212  |                                               |                     |
+|                                                                                       |                                               | 32.299 [5]          |
+| Note: The Experimental Result Codes from 4161 to 4180 are reserved for the TS 32.299. |                                               |                     |
+| 4181                                                                                  | DIAMETER_AUTHENTICATION_DATA_UNAVAILABLE      | 29.272 [21]         |
+| 4182                                                                                  | DIAMETER_ERROR_CAMEL_SUBSCRIPTION_PRESENT     |                     |
+| Note: The Experimental Result Codes from 4182 to 4200 are reserved for the TS 29.272. |                                               |                     |
+| 4201                                                                                  | DIAMETER_ERROR_ABSENT_USER                    | 29.173 [25]         |
+| Note: The Experimental Result Codes from 4202 to 4220 are reserved for the TS 29.173. |                                               |                     |
+| 4221                                                                                  | DIAMETER_ERROR_UNREACHABLE_USER               | 29.172 [24]         |
+| 4222                                                                                  | DIAMETER_ERROR_SUSPENDED_USER                 |                     |
+| 4223                                                                                  | DIAMETER_ERROR_DETACHED_USER                  |                     |
+| 4224                                                                                  | DIAMETER_ERROR_POSITIONING_DENIED             |                     |
+| 4225                                                                                  | DIAMETER_ERROR_POSITIONING_FAILED             |                     |
+| 4226                                                                                  | DIAMETER_ERROR_UNKNOWN_UNREACHABLE_LCS_CLIENT |                     |
+| Note: The Experimental Result Codes from 4227 to 4240 are reserved for the TS 29.172. |                                               |                     |
+| 4241                                                                                  | DIAMETER_ERROR_NO_AVAILABLE_POLICY_COUNTERS   | 29.219 [26]         |
+| Note: The Experimental Result Codes from 4242 to 4260 are reserved for the TS 29.219. |                                               |                     |
+| 4261                                                                                  | REQUESTED_SERVICE_TEMPORARILY_NOT_AUTHORIZED  | 29.214 [18]         |
+| Note: The Experimental Result Codes from 4262 to 4280 are reserved for the TS 29.214. |                                               |                     |
+
+### 8.1.4 Permanent Failures
+
+The Permanent Failure result codes shall use the values from 5001 to 5999 in the Experimental-Result-Code AVP. The reserved 3GPP specific Permanent Failure result codes are presented in the following table.
+
+Table 8.1.4: 3GPP specific Permanent Failure result codes
+
+| Experimental Result Code                                                                                   | Result text                                           | Specified in the TS                        |
+|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------------------------------------------|
+| 5001                                                                                                       | DIAMETER_ERROR_USER_UNKNOWN                           | 29.229 [2]                                 |
+| 5002                                                                                                       | DIAMETER_ERROR_IDENTITIES_DONT_MATCH                  |                                            |
+| 5003                                                                                                       | DIAMETER_ERROR_IDENTITY_NOT_REGISTERED                |                                            |
+| 5004                                                                                                       | DIAMETER_ERROR_ROAMING_NOT_ALLOWED                    |                                            |
+| 5005                                                                                                       | DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED            |                                            |
+| 5006                                                                                                       | DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED              |                                            |
+| 5007                                                                                                       | DIAMETER_ERROR_IN_ASSIGNMENT_TYPE                     |                                            |
+| 5008                                                                                                       | DIAMETER_ERROR_TOO_MUCH_DATA                          |                                            |
+| 5009                                                                                                       | DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA                |                                            |
+| 5010                                                                                                       | unassigned                                            |                                            |
+| 5011                                                                                                       | DIAMETER_ERROR_FEATURE_UNSUPPORTED                    |                                            |
+| 5012                                                                                                       | DIAMETER_ERROR_SERVING_NODE_FEATURE_UNSUP<br>PORTED   |                                            |
+| Note: The Experimental Result Codes from 5013 to 5020 are reserved for the TS 29.229.                      |                                                       | 32.299 [5]                                 |
+| Note: The Experimental Result Codes from 5021 to 5040 are reserved for the TS 32.299.                      |                                                       |                                            |
+| 5041                                                                                                       | DIAMETER_ERROR_USER_NO_WLAN_SUBSCRIPTION              | 29.234 [6]                                 |
+| 5042                                                                                                       | DIAMETER_ERROR_W-APN_UNUSED_BY_USER                   |                                            |
+| 5043                                                                                                       | DIAMETER_ERROR_NO_ACCESS_INDEPENDENT_SUBS<br>CRIPTION |                                            |
+| 5044                                                                                                       | DIAMETER_ERROR_USER_NO_W-APN_SUBSCRIPTION             |                                            |
+| 5045                                                                                                       | DIAMETER_ERROR_UNSUITABLE_NETWORK                     |                                            |
+| Note: The Experimental Result Codes from 5046 to 5060 are reserved for the TS 29.234.                      |                                                       |                                            |
+| 5061                                                                                                       | INVALID_SERVICE_INFORMATION                           | 29.209 [8],<br>29.211 [17],<br>29.214 [18] |
+| 5062                                                                                                       | FILTER_RESTRICTIONS                                   |                                            |
+| 5063                                                                                                       | REQUESTED_SERVICE_NOT_AUTHORIZED                      |                                            |
+| 5064                                                                                                       | DUPLICATED_AF_SESSION                                 |                                            |
+| 5065                                                                                                       | IP-CAN_SESSION_NOT_AVAILABLE                          |                                            |
+| 5066                                                                                                       | UNAUTHORIZED_NON_EMERGENCY_SESSION                    |                                            |
+| 5067                                                                                                       | UNAUTHORIZED_SPONSORED_DATA_CONNECTIVITY              |                                            |
+| 5068                                                                                                       | TEMPORARY_NETWORK_FAILURE                             |                                            |
+| Note: The Experimental Result Codes from 5069 to 5080 are reserved for TS 29.209, TS 29.211 and TS 29.214. |                                                       |                                            |
+| 5100                                                                                                       | DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED               | 29.329 [4]                                 |
+| 5101                                                                                                       | DIAMETER_ERROR_OPERATION_NOT_ALLOWED                  |                                            |
+| 5102                                                                                                       | DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ               |                                            |
+| 5103                                                                                                       | DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIE<br>D       |                                            |
+| 5104                                                                                                       | DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIE<br>D       |                                            |
+| 5105                                                                                                       | DIAMETER_ERROR_TRANSPARENT_DATA<br>OUT_OF_SYNC        |                                            |
+| 5106                                                                                                       | DIAMETER_ERROR_SUBS_DATA_ABSENT                       |                                            |
+| 5107                                                                                                       | DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA                |                                            |
+| 5108                                                                                                       | DIAMETER_ERROR_DSAI_NOT_AVAILABLE                     |                                            |
+| Note: The Experimental Result Codes from 5109 to 5119 are reserved for the TS 29.329.                      |                                                       |                                            |
+| 5120                                                                                                       | DIAMETER_ERROR_START_INDICATION                       | 29.061 [13]                                |
+| 5121                                                                                                       | DIAMETER_ERROR_STOP_INDICATION                        |                                            |
+| 5122                                                                                                       | DIAMETER_ERROR_UNKNOWN_MBMS_BEARER_SERVI<br>CE        |                                            |
+| 5123                                                                                                       | DIAMETER_ERROR_SERVICE_AREA                           |                                            |
+| Note: The Experimental Result Codes from 5124 to 5139 are reserved for the TS 29.061.                      |                                                       |                                            |
+| 5140                                                                                                       | DIAMETER_ERROR_INITIAL_PARAMETERS                     | 29.212 [19]                                |
+| 5141                                                                                                       | DIAMETER_ERROR_TRIGGER_EVENT                          |                                            |
+| 5142                                                                                                       | DIAMETER_PCC_RULE_EVENT                               |                                            |
+| 5143                                                                                                       | DIAMETER_ERROR_BEARER_NOT_AUTHORIZED                  |                                            |
+| 5144                                                                                                       | DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTE<br>D      |                                            |
+| 5145                                                                                                       | DIAMETER_QOS_RULE_EVENT                               |                                            |
+| 5146                                                                                                       | reserved                                              |                                            |
+| 5147                                                                                                       | DIAMETER_ERROR_CONFLICTING_REQUEST                    |                                            |
+| 5148                                                                                                       | DIAMETER_ADC_RULE_EVENT                               |                                            |
+
+|                                                                                       |                                                           |             |
+|---------------------------------------------------------------------------------------|-----------------------------------------------------------|-------------|
+| 5149                                                                                  | DIAMETER_ERROR_NBIFOM_NOT_AUTHORIZED                      |             |
+| Note: The Experimental Result Codes from 5150 to 5159 are reserved for the TS 29.212. |                                                           |             |
+| 5401                                                                                  | DIAMETER_ERROR_IMPI_UNKNOWN                               | 29.109 [7]  |
+| 5402                                                                                  | DIAMETER_ERROR_NOT_AUTHORIZED                             |             |
+| 5403                                                                                  | DIAMETER_ERROR_TRANSACTION_IDENTIFIER_INVALID             |             |
+| Note: The Experimental Result Codes from 5404 to 5419 are reserved for the TS 29.109. |                                                           |             |
+| 5420                                                                                  | DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION                   | 29.272 [21] |
+| 5421                                                                                  | DIAMETER_ERROR_RAT_NOT_ALLOWED                            |             |
+| 5422                                                                                  | DIAMETER_ERROR_EQUIPMENT_UNKNOWN                          |             |
+| 5423                                                                                  | DIAMETER_ERROR_UNKNOWN_SERVING_NODE                       |             |
+| Note: The Experimental Result Codes from 5424 to 5449 are reserved for the TS 29.272. |                                                           |             |
+| 5450                                                                                  | DIAMETER_ERROR_USER_NO_NON_3GPP_SUBSCRIPTION              | 29.273 [20] |
+| 5451                                                                                  | DIAMETER_ERROR_USER_NO_APN_SUBSCRIPTION                   |             |
+| 5452                                                                                  | DIAMETER_ERROR_RAT_TYPE_NOT_ALLOWED                       |             |
+| 5453                                                                                  | DIAMETER_ERROR_LATE_OVERLAPPING_REQUEST                   |             |
+| 5454                                                                                  | DIAMETER_ERROR_TIMED_OUT_REQUEST                          |             |
+| Note: The Experimental Result Codes from 5455 to 5469 are reserved for the TS 29.273. |                                                           |             |
+| 5470                                                                                  | DIAMETER_ERROR_SUBSESSION                                 | 29.215 [22] |
+| 5471                                                                                  | DIAMETER_ERROR_ONGOING_SESSION_ESTABLISHMENT              |             |
+| Note: The Experimental Result Codes from 5472 to 5489 are reserved for the TS 29.215. |                                                           |             |
+| 5490                                                                                  | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK            | 29.173 [25] |
+| Note: The Experimental Result Codes from 5491 to 5509 are reserved for the TS 29.173. |                                                           |             |
+| 5510                                                                                  | DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_ENTITY             | 29.336 [28] |
+| 5511                                                                                  | DIAMETER_ERROR_UNAUTHORIZED_SERVICE                       |             |
+| 5512                                                                                  | DIAMETER_ERROR_REQUESTED_RANGE_IS_NOT_ALLOWED             |             |
+| 5513                                                                                  | DIAMETER_ERROR_CONFIGURATION_EVENT_STORAGE_NOT_SUCCESSFUL |             |
+| 5514                                                                                  | DIAMETER_ERROR_CONFIGURATION_EVENT_NON_EXISTANT           |             |
+| 5515                                                                                  | DIAMETER_ERROR_SCEF_REFERENCE_ID_UNKNOWN                  |             |
+| 5516                                                                                  | DIAMETER_ERROR_UNAUTHORIZED_MTC_PROVIDER                  |             |
+| Note: The Experimental Result Codes from 5517 to 5529 are reserved for the TS 29.336. |                                                           |             |
+| 5530                                                                                  | DIAMETER_ERROR_INVALID_SME_ADDRESS                        | 29.337 [29] |
+| 5531                                                                                  | DIAMETER_ERROR_SC_CONGESTION                              |             |
+| 5532                                                                                  | DIAMETER_ERROR_SM_PROTOCOL                                |             |
+| 5533                                                                                  | DIAMETER_ERROR_TRIGGER_REPLACE_FAILURE                    |             |
+| 5534                                                                                  | DIAMETER_ERROR_TRIGGER_RECALL_FAILURE                     |             |
+| 5535                                                                                  | DIAMETER_ERROR_ORIGINAL_MESSAGE_NOT_PENDING               |             |
+| Note: The Experimental Result Codes from 5536 to 5549 are reserved for the TS 29.337. |                                                           |             |
+| 5550                                                                                  | DIAMETER_ERROR_ABSENT_USER                                | 29.338 [30] |
+| 5551                                                                                  | DIAMETER_ERROR_USER_BUSY_FOR_MT_SMS                       |             |
+| 5552                                                                                  | DIAMETER_ERROR_FACILITY_NOT_SUPPORTED                     |             |
+| 5553                                                                                  | DIAMETER_ERROR_ILLEGAL_USER                               |             |
+| 5554                                                                                  | DIAMETER_ERROR_ILLEGAL_EQUIPMENT                          |             |
+| 5555                                                                                  | DIAMETER_ERROR_SM_DELIVERY_FAILURE                        |             |
+| 5556                                                                                  | DIAMETER_ERROR_SERVICE_NOT_SUBSCRIBED                     |             |
+| 5557                                                                                  | DIAMETER_ERROR_SERVICE_BARRED                             |             |
+| 5558                                                                                  | DIAMETER_ERROR_MWD_LIST_FULL                              |             |
+| Note: The Experimental Result Codes from 5559 to 5569 are reserved for the TS 29.338. |                                                           |             |
+| 5570                                                                                  | DIAMETER_ERROR_UNKNOWN_POLICY_COUNTERS                    | 29.219 [26] |
+| Note: The Experimental Result Codes from 5571 to 5589 are reserved for the TS 29.219. |                                                           |             |
+| 5590                                                                                  | DIAMETER_ERROR_ORIGIN_AUID_UNKNOWN                        | 29.343 [32] |
+| 5591                                                                                  | DIAMETER_ERROR_TARGET_AUID_UNKNOWN                        |             |
+| 5592                                                                                  | DIAMETER_ERROR_PPID_UNKNOWN                               |             |
+| 5593                                                                                  | DIAMETER_ERROR_APP_REGISTER_REJECT                        |             |
+| 5594                                                                                  | DIAMETER_ERROR_PROSE_MAP_REQUEST_DISALLOWED               |             |
+| 5595                                                                                  | DIAMETER_ERROR_MAP_REQUEST_REJECT                         |             |
+| 5596                                                                                  | DIAMETER_ERROR_REQUESTING_RPAUID_UNKNOWN                  |             |
+
+|                                                                                       |                                                  |             |
+|---------------------------------------------------------------------------------------|--------------------------------------------------|-------------|
+| 5597                                                                                  | DIAMETER_ERROR_UNKNOWN_OR_INVALID_TARGET_SET     |             |
+| 5598                                                                                  | DIAMETER_ERROR_MISSING_APPLICATION_DATA          |             |
+| 5599                                                                                  | DIAMETER_ERROR_AUTHORIZATION_REJECT              |             |
+| 5600                                                                                  | DIAMETER_ERROR_DISCOVERY_NOT_PERMITTED           |             |
+| 5601                                                                                  | DIAMETER_ERROR_TARGET_RPAUID_UNKNOWN             |             |
+| 5602                                                                                  | DIAMETER_ERROR_INVALID_APPLICATION_DATA          |             |
+| Note: The Experimental Result Codes from 5603 to 5609 are reserved for the TS 29.343. |                                                  |             |
+| 5610                                                                                  | DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION        | 29.344 [33] |
+| 5611                                                                                  | DIAMETER_ERROR_PROSE_NOT_ALLOWED                 |             |
+| 5612                                                                                  | DIAMETER_ERROR_UE_LOCATION_UNKNOWN               |             |
+| Note: The Experimental Result Codes from 5613 to 5629 are reserved for the TS 29.344. |                                                  |             |
+| 5630                                                                                  | DIAMETER_ERROR_NO_ASSOCIATED_DISCOVERY_FILTER    | 29.345 [34] |
+| 5631                                                                                  | DIAMETER_ERROR_ANNOUNCING_UNAUTHORIZED_IN_PLMN   |             |
+| 5632                                                                                  | DIAMETER_ERROR_INVALID_APPLICATION_CODE          |             |
+| 5633                                                                                  | DIAMETER_ERROR_PROXIMITY_UNAUTHORIZED            |             |
+| 5634                                                                                  | DIAMETER_ERROR_PROXIMITY_REJECTED                |             |
+| 5635                                                                                  | DIAMETER_ERROR_NO_PROXIMITY_REQUEST              |             |
+| 5636                                                                                  | DIAMETER_ERROR_UNAUTHORIZED_SERVICE_IN_THIS_PLMN |             |
+| 5637                                                                                  | DIAMETER_ERROR_PROXIMITY_CANCELLED               |             |
+| 5638                                                                                  | DIAMETER_ERROR_INVALID_TARGET_PDUID              |             |
+| 5639                                                                                  | DIAMETER_ERROR_INVALID_TARGET_RPAUID             |             |
+| 5640                                                                                  | DIAMETER_ERROR_NO_ASSOCIATED_RESTRICTED_CODE     |             |
+| 5641                                                                                  | DIAMETER_ERROR_INVALID_DISCOVERY_TYPE            |             |
+| Note: The Experimental Result Codes from 5642 to 5649 are reserved for the TS 29.345. |                                                  |             |
+| 5650                                                                                  | DIAMETER_ERROR_REQUESTED_LOCATION_NOT_SERVED     | 29.128 [36] |
+| 5651                                                                                  | DIAMETER_ERROR_INVALID_EPS_BEARER                |             |
+| 5652                                                                                  | DIAMETER_ERROR_NIDD_CONFIGURATION_NOT_AVAILABLE  |             |
+| 5653                                                                                  | DIAMETER_ERROR_USER_TEMPORARILY_UNREACHABLE      |             |
+| Note: The Experimental Result Codes from 5654 to 5669 are reserved for the TS 29.128. |                                                  |             |
+| 5670                                                                                  | DIAMETER_ERROR_UNKNOWN_DATA                      | 29.283 [39] |
+| 5671                                                                                  | DIAMETER_ERROR_REQUIRED_KEY_NOT_PROVIDED         |             |
+| Note: The Experimental Result Codes from 5672 to 5689 are reserved for the TS 29.128. |                                                  |             |
+| 5690                                                                                  | DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION          | 29.388 [40] |
+| 5691                                                                                  | DIAMETER_ERROR_V2X_NOT_ALLOWED                   |             |
+| Note: The Experimental Result Codes from 5692 to 5709 are reserved for the TS 29.388. |                                                  |             |
+
+# --- Annex A (informative): Assignment of the Diameter codes and identifiers in 3GPP
+
+This annex defines the recommended assignment procedure of Diameter codes and identifiers within the 3GPP.
+
+## --- A.1 Application identifiers
+
+If a working group detects it will require a new application identifier, it should contact the 3GPP TSG-CN WG 4 via a Liaison Statement. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will then request the application identifier from IANA. When the application identifier is received, the corresponding working group will be informed by 3GPP TSG-CN WG 4 and the table 4.1 in this specification will be updated.
+
+According to RFC 3588 the creation of a new application should be avoided if at all possible and therefore it is recommended to use the existing application identifiers whenever possible.
+
+## --- A.2 Command codes
+
+If a working group detects there is a need for a new command code(s) from the 3GPP's range, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the reference to the 3GPP TS, which specifies the command(s). The 3GPP TSG-CN WG 4 will inform the assigned command code(s) to the corresponding working group and the table 5.1 in this specification will be updated.
+
+It should be noted that the standard command codes allocated for 3GPP are scarce resource and getting new ones would require IETF specification work to be done. Therefore it is recommended to use the existing command codes whenever possible.
+
+## --- A.3 AVP codes
+
+If a working group detects a Diameter application needs new 3GPP specific AVP codes, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will allocate a range of 100 AVP codes for the application. The range will be informed to the corresponding working group and the table 7.1 will be updated in this specification to show the reserved range. The working group can use the allocated range as a working assumption when defining the actual AVPs.
+
+When the corresponding working group has specified the AVPs, and the specification has been approved and is under CR control, it should inform the AVPs to the 3GPP TSG-CN WG 4 via an LS. The LS should list the used AVP codes in the form of the table 7.1.
+
+If there will be defined new AVPs for a Diameter application through the CR procedure, the assigned AVP range can be used, but the 3GPP TSG-CN WG 4 should be also informed about the new AVP codes via an LS.
+
+Re-using of the existing AVPs is recommended, but special attention should be paid on the use of enumerated AVPs. Defining new values for an enumerated AVP should be agreed case by case with the working group responsible of the particular enumerated AVP. 3GPP TSG-CN WG 4 shall be informed via an LS about the new values assigned to the enumerated AVP.
+
+## --- A.4 Result codes
+
+If a working group detects a Diameter application needs new 3GPP specific result codes, it should contact the 3GPP TSG-CN WG 4 via an LS. The LS shall contain the name of the Diameter application and a reference to the corresponding 3GPP TS. The 3GPP TSG-CN WG 4 will allocate a range of 20 result codes from each required result
+
+code group for the application. The ranges will be informed to the corresponding working group and the tables in the chapter 8 of this specification will be updated to show the reserved ranges. The working group can use the allocated ranges as a working assumption when defining the actual result codes.
+
+When the corresponding working group has specified the result codes, and the specification has been approved and is under CR control, it should convey the codes to the 3GPP TSG-CN WG 4 via an LS. The LS should list the used result codes in the form of the tables in chapter 8.
+
+If there will be defined new result codes for a Diameter application through the CR procedure, the assigned result code ranges can be used, but the 3GPP TSG-CN WG 4 should be also informed about the new result codes via an LS.
+
+Re-using of the existing result codes is recommended.
+
+# Annex B (informative): Change history
+
+| Date    | TSG # | TSG Doc.  | CR   | Rev | Ca<br>t | Subject/Comment                                                                                           | New   |
+|---------|-------|-----------|------|-----|---------|-----------------------------------------------------------------------------------------------------------|-------|
+| 2004-06 | CN#24 | NP-040292 |      |     |         | Version 2.0.0 presented for information and approval                                                      | 6.0.0 |
+| 2004-09 | CN#25 | NP-040401 | 001  |     |         | Correction of Charging application reference                                                              | 6.1.0 |
+| 2004-09 | CN#25 | NP-040401 | 002  |     |         | Correction of the Application-Id code                                                                     | 6.1.0 |
+| 2004-09 | CN#25 | NP-040401 | 003  |     |         | Removal of User Data Request Type AVP                                                                     | 6.1.0 |
+| 2004-09 | CN#25 | NP-040412 | 004  | 1   |         | Re-numbering of 3GPP specific AVP codes.                                                                  | 6.1.0 |
+| 2004-12 | CN#26 | NP-040579 | 006  |     |         | Inclusion of missing Cx AVPs                                                                              | 6.2.0 |
+| 2004-12 | CN#26 | NP-040580 | 007  | 1   |         | Reservation of command code 310                                                                           | 6.2.0 |
+| 2004-12 | CN#26 | NP-040579 | 009  | 1   |         | Addition of Gmb interface                                                                                 | 6.2.0 |
+| 2004-12 | CN#26 | NP-040600 | 010  | 2   |         | Documenting the Reuse of the 3GPP specific application identifier of Ro for Re on the Charging Interfaces | 6.2.0 |
+| 2004-12 | CN#26 | NP-040579 | 011  |     |         | Gq interface allocations                                                                                  | 6.2.0 |
+| 2004-12 | CN#26 | NP-040579 | 012  |     |         | Addition of Gx interface                                                                                  | 6.2.0 |
+| 2005-03 | CN#27 | NP-050047 | 040  | 1   |         | WLAN Diameter AVP and result codes                                                                        | 6.3.0 |
+|         |       | NP-050039 | 043  |     |         | Allocations for Gx interface                                                                              |       |
+|         |       | NP-050039 | 045  |     |         | Allocations for Gmb interface                                                                             |       |
+|         |       | NP-050039 | 046  |     |         | Allocations for MMS, MM10 Interface                                                                       |       |
+| 2005-06 | CT#28 | CP-050088 | 0050 |     |         | Gx interface allocation correction                                                                        | 6.4.0 |
+|         |       | CP-050196 | 0051 | 1   |         | Addition of Maximum-Number-Accesses AVP                                                                   |       |
+| 2005-09 | CT#29 | CP-050440 | 0052 | 1   |         | Private identities on the Cx                                                                              | 6.5.0 |
+|         |       | CP-050310 | 0053 |     |         | Addition of Pr reference point to TS 29.230                                                               |       |
+|         |       | CP-050310 | 0054 |     |         | Error code cleanup                                                                                        |       |
+|         |       | CP-050310 | 0056 |     |         | Addition of Rx ref. point and renaming of Experimental Result Codes                                       |       |
+| 2005-09 | CT#29 | CP-050317 | 0055 |     |         | Addition of GUSS timestamp AVP                                                                            | 7.0.0 |
+| 2005-12 | CT#30 | CP-050624 | 0058 |     |         | Addition of GBA-Type AVP                                                                                  | 7.1.0 |
+|         |       | CP-050612 | 0063 |     |         | Additional Gmb AVP Allocation                                                                             |       |
+|         |       | CP-050612 | 0065 |     |         | Reservation of AVP codes for 32.299                                                                       |       |
+|         |       | CP-050625 | 0066 |     |         | Management of Sh subscriptions                                                                            |       |
+| 2006-03 | CT#31 | CP-060073 | 0069 |     |         | Adding data type of some of WLAN-related AVPs                                                             | 7.2.0 |
+|         |       | CP-060084 | 0071 |     |         | User-Data in the response to Sh-Subs-Notif                                                                |       |
+|         |       | CP-060084 | 0072 | 1   |         | New error indications for the Sh-Subs-Notif procedure                                                     |       |
+| 2006-06 | CT#32 | CP-060302 | 0075 |     |         | S-CSCF reselection removal                                                                                | 7.3.0 |
+| 2006-09 | CT#33 | CP-060417 | 0077 | 3   |         | New AVP Code                                                                                              | 7.4.0 |
+|         |       | CP-060417 | 0080 |     |         | Errors to be sent in response to Sh-Notif                                                                 |       |
+|         |       | CP-060417 | 0081 |     |         | Definition of specific Diameter codes for DSAI                                                            |       |
+| 2006-12 | CT#34 | CP-060566 | 0085 | 1   |         | Optimization of handling of Wildcarded PSIs                                                               | 7.5.0 |
+|         |       | CP-060562 | 0086 |     |         | Addition of Diameter Error Code for Emergency Purposes                                                    |       |
+|         |       | CP-060555 | 0087 |     |         | Allocation of new AVP codes for Gmb                                                                       |       |
+|         |       | CP-060555 | 0089 |     |         | AVP code allocations for Rf and Ro interfaces                                                             |       |
+|         |       | CP-060566 | 0091 |     |         | Allocation of Success Result Code Range for Gi Interface                                                  |       |
+| 2007-03 | CT#35 | CP-070020 | 0093 |     |         | C3 requested addition of new AVP code values to 3GPP TS 29.230                                            | 7.6.0 |
+|         |       | CP-070020 | 0093 |     |         | Allocation of new AVP code for DSAI-Tag AVP                                                               |       |
+|         |       | CP-070020 | 0093 |     |         | Allocation of Experimental-Result-Code AVP for Gi Interface                                               |       |
+| 2007-06 | CT#36 | CP-070318 | 0096 |     |         | Diameter application ID for the Rel-7 Rx interface                                                        | 7.7.0 |
+|         |       | CP-070312 | 0098 |     |         | Experimental-Result-Codes for Gmb interface                                                               |       |
+|         |       | CP-070312 | 0100 |     |         | Correction of Diameter AVP code allocation                                                                |       |
+| 2007-09 | CT#37 | CP-070527 | 0102 |     |         | Application ID for Gx protocol                                                                            | 7.8.0 |
+| 2007-12 | CT#38 | CP-070743 | 0104 |     |         | AVP code reservation for 32.299 in Rel-7                                                                  | 7.9.0 |
+|         |       |           | 0105 |     |         | Allocation of 3GPP specific AVP codes and Experimental Result Codes for Gx protocol                       |       |
+| 2007-12 | CT#38 | CP-070755 | 0101 | 4   |         | AVP assignments to support SIP Digest Authentication                                                      | 8.0.0 |
+|         |       |           | 0103 |     |         | AVP code reservation for 32.299 in Rel-8                                                                  |       |
+| 2008-03 | CT#39 | CP-080015 | 0109 |     |         | Correction of reference to TS 29.140                                                                      | 8.1.0 |
+|         |       | CP-080019 | 0111 |     |         | AVP code reservation for TS 32.299 in Rel-8                                                               |       |
+|         |       | CP-080019 | 0107 |     |         | Wildcarded Public User Identities                                                                         |       |
+|         |       | CP-080191 | 0112 | 1   |         | Correction on AVP code allocation reservation for TS 32.299 in Rel-7                                      |       |
+|         |       | CP-080204 | 0113 | 1   |         | Correction on AVP code allocation reservation for TS 32.299                                               |       |
+| 2008-06 | CT#40 | CP-080267 | 0117 | 1   |         | A new Diameter Permanent Failure Code for Gx                                                              | 8.2.0 |
+| 2008-09 | CT#41 | CP-080456 | 0119 |     |         | Emergency Public User Identity Removal                                                                    | 8.3.0 |
+
+|         |       |           |      |   |  |                                                                            |        |
+|---------|-------|-----------|------|---|--|----------------------------------------------------------------------------|--------|
+| 2008-09 | CT#41 | CP-080460 | 0121 | 1 |  | Support of "Loose-Route" indication from HSS                               |        |
+|         |       | CP-080460 | 0122 | 1 |  | STaMIP Application Id                                                      |        |
+|         |       | CP-080463 | 0123 |   |  | Cx Impacts of IMS Restoration Procedures (New AVP Codes Assignment)        |        |
+|         |       | CP-080463 | 0124 |   |  | New AVP Code Assignment for Forking Service Restoration                    | 8.3.0  |
+| 2008-12 | CT#42 | CP-080691 | 0127 | 2 |  | Diameter Protocol Codes Assignments for S6a/S6d/S13                        | 8.4.0  |
+|         |       | CP-080691 | 0128 | 1 |  | Diameter code assignments for 3GPP TS 29.273                               | 8.4.0  |
+| 2009-03 | CT#43 | CP-090044 | 0130 | 1 |  | Update for ReadyForSM                                                      | 8.5.0  |
+|         |       | CP-090044 | 0131 | 1 |  | Handling LCS Subscription Data                                             | 8.5.0  |
+|         |       | CP-090026 | 0132 |   |  | Update for Restoration                                                     | 8.5.0  |
+|         |       | CP-090024 | 0133 |   |  | AppIds for Gxx and S9                                                      | 8.5.0  |
+|         |       | CP-090033 | 0134 | 2 |  | AppId and command code for Zpn                                             | 8.5.0  |
+|         |       | CP-090024 | 0137 | 1 |  | AVP codes for S9 protocol                                                  | 8.5.0  |
+|         |       | CP-090024 | 0138 | 1 |  | Diameter AVP Code allocation                                               | 8.5.0  |
+|         |       | CP-090024 | 0140 | 1 |  | Location of Permanent Failure result code range for the S9 application     | 8.5.0  |
+|         |       | CP-090024 | 0141 |   |  | AVPs for TS 29.273                                                         | 8.5.0  |
+|         |       | CP-090024 | 0142 | 1 |  | Error code allocation for authentication failure                           | 8.5.0  |
+| 2009-06 | CT#44 | CP-090299 | 0129 | 4 |  | Update of the AVP Codes                                                    | 8.6.0  |
+|         |       | CP-090299 | 0143 |   |  | AVP code reservation for TS 32.299                                         |        |
+|         |       | CP-090299 | 0145 |   |  | Diameter Command Codes for S6a/S6d/S13/S13'                                |        |
+|         |       | CP-090299 | 0146 |   |  | Removal of Requesting Node Type from AIR                                   |        |
+|         |       | CP-090299 | 0147 |   |  | S6b Application ID                                                         |        |
+| 2009-09 | CT#45 | CP-090530 | 0149 |   |  | Allocation of Experimental-Result-Codes for S9 protocol                    | 8.7.0  |
+|         |       | CP-090530 | 0152 |   |  | AVP code allocation for TS 29.212                                          |        |
+|         |       | CP-090531 | 0150 |   |  | Update of the AVP type for the User-Id                                     |        |
+|         |       | CP-090531 | 0153 |   |  | Trace Depth per session                                                    |        |
+| 2009-09 | CT#45 | CP-090557 | 0148 |   |  | AVP code range for charging                                                | 9.0.0  |
+| 2009-12 | CT#46 | CP-090800 | 0154 | 1 |  | ICS-Flag                                                                   | 9.1.0  |
+|         |       | CP-091032 | 0156 |   |  | From GMLC-Address to GMLC-Number                                           |        |
+|         |       |           | 0160 |   |  | Session-Priority AVP                                                       |        |
+|         |       |           | 0163 | 2 |  | Introduction of SLh application related AVPs and Experimental Result codes |        |
+|         |       |           | 0166 |   |  | Missing AVP error codes                                                    |        |
+|         |       | CP-090797 | 0167 | 1 |  | Introduction of SLg application related AVPs and Application Identifier    |        |
+| 2010-03 | CT#47 | CP-100031 | 0158 | 1 |  | Wildcarded Public Identity                                                 | 9.2.0  |
+|         |       | CP-100034 | 0168 | 1 |  | Correction on AVP code allocation reservation for TS 32.299 in Rel-9       |        |
+|         |       | CP-100046 | 0169 | 1 |  | AVP code allocation for 29.172                                             |        |
+|         |       | CP-100036 | 0172 |   |  | GPL_U support in TS 29.109                                                 |        |
+|         |       | CP-100046 | 0173 |   |  | Error codes in 29.172 for SLg                                              |        |
+|         |       | CP-100048 | 0174 | 1 |  | AVPs in 29.272 for TADS support                                            |        |
+|         |       | CP-100040 | 0175 |   |  | Error codes in 29.272 for Unknown MME                                      |        |
+|         |       | CP-100236 | 0176 | 4 |  | EPS Subscriber State and Location Information Request                      |        |
+|         |       | CP-100033 | 0180 |   |  | One time notification AVP allocation                                       |        |
+|         |       | CP-100046 | 0181 |   |  | Addition of the LCS-QoS-Class attribute value                              |        |
+|         |       | CP-100175 | 0182 |   |  | Introduction of the LCS-Capabilities-Sets AVP in SLh interface             |        |
+| 2010-06 | CT#48 | CP-100263 | 0188 | 1 |  | AVP Codes for PCC                                                          | 9.3.0  |
+|         |       |           | 0183 |   |  | EPS state and location retrieval                                           |        |
+|         |       | CP-100287 | 0186 |   |  | SGmb Application ID                                                        |        |
+|         |       | CP-100277 | 0190 | 1 |  | New AVPs in S6a protocol                                                   |        |
+| 2010-09 | CT#49 | CP-100463 | 0197 | 1 |  | Addition of Diameter codes and identifiers for the SLg and SLh interfaces  | 9.4.0  |
+|         |       | CP-100464 | 0196 |   |  | AVP Codes Allocation for PCC                                               |        |
+| 2010-09 | CT#49 | CP-100465 | 0193 | 1 |  | SIPTO Permission Indicator                                                 | 10.0.0 |
+|         |       | CP-100466 | 0198 | 2 |  | Location data including only serving node address                          |        |
+|         |       | CP-100466 | 0199 | 1 |  | AVP for Update-Eff feature                                                 |        |
+| 2010-12 | CT#50 | CP-100699 | 0205 |   |  | Enhanced SRVCC Subscriber Data                                             | 10.1.0 |
+|         |       | CP-100687 | 0201 | 1 |  | Allocate codes for AVPs on eMPS                                            |        |
+|         |       | CP-100683 | 0200 | 1 |  | Allocate codes for AVPs on LIPA                                            |        |
+|         |       | CP-100688 | 0206 | 1 |  | Periodic TAU/RAU timer in HSS subscription                                 |        |
+|         |       | CP-100846 | 0203 | 1 |  | S6a Error Diagnostic                                                       |        |
+| 2011-03 | CT#51 | CP-110051 | 0212 |   |  | PDP-Address correction                                                     | 10.2.0 |
+|         |       | CP-110054 | 0215 |   |  | Essential correction on the value type of the ELP Application AVPs         |        |
+|         |       | CP-110087 | 0207 | 2 |  | Minimization of Drive Tests (MDT)                                          |        |
+|         |       | CP-110088 | 0209 | 1 |  | Relay Node Indicator AVPs                                                  |        |
+| 2011-06 | CT#52 | CP-110349 | 0219 | 2 |  | Handling of RTR for Emergency Registration                                 | 10.3.0 |
+|         |       | CP-110347 | 0231 | 1 |  | Add AVPs from QSPEC cleanup                                                |        |
+|         |       | CP-110359 | 0226 |   |  | MIPv4 security parameters on the STa and S6b interfaces                    |        |
+|         |       | CP-110380 | 0216 |   |  | MDT user consent                                                           |        |
+
+|         |       |           |      |   |  |                                                                                   |        |
+|---------|-------|-----------|------|---|--|-----------------------------------------------------------------------------------|--------|
+|         |       | CP-110370 | 0223 |   |  | AVP Code Allocation for Pre-paging                                                |        |
+|         |       | CP-110375 | 0227 | 1 |  | PUR-Flags AVP                                                                     |        |
+| 2011-09 | CT#53 | CP-110559 | 0236 | 1 |  | AVP code alignment with 29.212                                                    | 10.4.0 |
+|         |       | CP-110555 | 0239 | 1 |  | AVP code alignment with 32.299                                                    |        |
+|         |       | CP-110554 | 0244 | 1 |  | AVP code alignment with 29.214                                                    |        |
+|         |       | CP-110552 | 0249 |   |  | Experimental Result Code Alignment with 29.061                                    |        |
+|         |       | CP-110555 | 0252 |   |  | Failure code and AVP code alignment with 29.212                                   |        |
+|         |       | CP-110722 | 0257 | 2 |  | Privileged sender                                                                 |        |
+| 2011-09 | CT#53 | CP-110584 | 0234 | 1 |  | Add vSRVCC updates to the Diameter AVP code table                                 | 11.0.0 |
+|         |       | CP-110579 | 0240 |   |  | AVP code alignment with 32.299                                                    |        |
+|         |       | CP-110555 | 0253 |   |  | AVP code reservation for 29.212                                                   |        |
+| 2011-12 | CT#54 | CP-110812 | 0258 | 1 |  | SWx Restoration AVPs                                                              | 11.1.0 |
+|         |       | CP-110812 | 0259 |   |  | Sy and Sd Application IDs                                                         |        |
+|         |       | CP-110775 | 0262 |   |  | New AVP codes for MBMS IP unicast encapsulation                                   |        |
+|         |       | CP-110775 | 0265 |   |  | New AVP codes for MBMS IP multicast encapsulation                                 |        |
+|         |       | CP-110786 | 0271 | 1 |  | MME-Realm AVP code allocation                                                     |        |
+|         |       | CP-110811 | 0277 |   |  | Equivalent PLMN CSG Subscription Request                                          |        |
+|         |       | CP-110781 | 0281 | 1 |  | Restoration of Wildcarded-IMPU AVP                                                |        |
+|         |       | CP-120025 | 0286 | 1 |  | Codes Allocation for AVPs on Initial Attach                                       |        |
+| 2012-03 | CT#55 | CP-120038 | 0288 |   |  | New AVP codes for Absolute Time of MBMS Data Transfer over SGmb                   | 11.2.0 |
+|         |       | CP-120038 | 0291 | 1 |  | Allocating Diameter AVP codes for TS 29.219 and TS 29.212                         |        |
+|         |       | CP-120240 | 0287 | 5 |  | Codes Allocation for AVPs on NPLI                                                 |        |
+| 2012-06 | CT#56 | CP-120238 | 0294 | 1 |  | Adding new Diameter AVPs to Diameter table to support Trusted WLAN Access feature | 11.3.0 |
+|         |       | CP-120225 | 0296 | 1 |  | Trust Relationship Indication                                                     |        |
+|         |       | CP-120251 | 0297 | 1 |  | Corrections to reference titles                                                   |        |
+|         |       | CP-120251 | 0298 | 1 |  | Diameter Code Allocation for TS 29.219                                            |        |
+|         |       | CP-120247 | 0300 | - |  | Network Name AVP codes                                                            |        |
+|         |       | CP-120219 | 0304 | - |  | Duplicated AVP names                                                              |        |
+|         |       | CP-120481 | 0289 | 3 |  | PS additional number allocation                                                   |        |
+| 2012-09 | CT#57 | CP-120473 | 0293 | 4 |  | SMS in MME/SGSN                                                                   | 11.4.0 |
+|         |       | CP-120461 | 0299 | 2 |  | AAA Failure Recovery AVP codes                                                    |        |
+|         |       | CP-120474 | 0305 | - |  | Transport Access Type AVP for BBAI                                                |        |
+|         |       | CP-120480 | 0307 | 1 |  | Local Time Zone                                                                   |        |
+|         |       | CP-120472 | 0308 | - |  | Allocating Application Identifier and command code for Tsp interface              |        |
+|         |       | CP-120472 | 0309 | - |  | Application Identifier, Command Codes and AVP range for S6m interface             |        |
+|         |       | CP-120667 | 0312 | 1 |  | GMLC-Name                                                                         |        |
+|         |       | CP-120667 | 0313 | 1 |  | Reference list correction to align with the corrected TS 29.212 title             |        |
+|         |       | CP-120731 | 0315 | 2 |  | T4 device triggering via IMS                                                      |        |
+|         |       | CP-120731 | 0318 | 1 |  | Codes and Identifier Allocation for T4 Specification                              |        |
+| 2012-12 | CT#58 | CP-120731 | 0324 | - |  | AVP Code Allocation for 29.336                                                    | 11.5.0 |
+|         |       | CP-120731 | 0329 | - |  | Diameter AVP code value allocation in TS 29.368                                   |        |
+|         |       | CP-120732 | 0319 | 2 |  | Application Identifier, Command Codes and AVP codes for SGd, S6c                  |        |
+|         |       | CP-120716 | 0324 | 1 |  | AVP name modification in TS 32.299                                                |        |
+|         |       | CP-120742 | 0325 | - |  | UE Time Zone AVP                                                                  |        |
+|         |       | CP-120741 | 0328 | 1 |  | Use of Flag instead of Enumerated AVPs                                            |        |
+|         |       | CP-120741 | 0332 | - |  | Use of Flag instead of Enumerated AVPs                                            |        |
+|         |       | CP-120743 | 0330 | - |  | PSI direct routing with restoration procedures                                    |        |
+|         |       | CP-120743 | 0333 | - |  | EPS LocationInformation Support                                                   |        |
+|         |       | CP-130026 | 0334 | 1 |  | Diameter error code for TS 29.219                                                 |        |
+|         |       | CP-130026 | 0336 | - |  | MDT parameters                                                                    |        |
+| 2013-03 | CT#59 | CP-130156 | 0337 | 1 |  | New AVPs for Lgd interface                                                        | 12.0.0 |
+|         |       | CP-130030 | 0341 | - |  | Validity Time of Short Message                                                    |        |
+| 2013-06 | CT#60 | CP-130288 | 0362 | 1 |  | Add new DER-S6b-flag AVP                                                          | 12.1.0 |
+|         |       | CP-130298 | 0360 | - |  | Failure Result Codes Allocation for TS 29.219                                     |        |
+|         |       | CP-130292 | 0358 | - |  | Diameter AVP codes for new TS 32.299 AVPs                                         |        |
+|         |       | CP-130279 | 0354 | 1 |  | Definition of SS Status for Call Barring                                          |        |
+|         |       | CP-130380 | 0363 | - |  | New SGs-MME-Identity AVP                                                          |        |
+|         |       | CP-130291 | 0348 | 2 |  | New AVPs for deferred MT-LR and periodic MO-LR TTTP procedures over Lgd interface |        |
+|         |       | CP-130297 | 0347 | 1 |  | Application Port Identifier                                                       |        |
+|         |       | CP-130374 | 0345 | 1 |  | MTRR on Sh                                                                        |        |
+|         |       | CP-130295 | 0344 | - |  | Restoration Priority during SGW and PGW restoration procedures                    |        |
+|         |       | CP-130378 | 0349 | 1 |  | SIPTO permission for Local Network enhancements                                   |        |
+|         |       | CP-130454 | 0364 | 2 |  | New MBMS flag for eMBMS restoration                                               |        |
+|         |       | CP-130461 | 0366 | - |  | AVP code reservation for TS 32.299 Rel-12                                         |        |
+|         |       | CP-130460 | 0368 | - |  | Allocation of Diameter codes and identifiers for 29.212 and 29.215                |        |
+| 2013-09 | CT#61 | CP-130454 | 0364 | 2 |  | New MBMS flag for eMBMS restoration                                               | 12.2.0 |
+|         |       | CP-130461 | 0366 | - |  | AVP code reservation for TS 32.299 Rel-12                                         |        |
+|         |       | CP-130460 | 0368 | - |  | Allocation of Diameter codes and identifiers for 29.212 and 29.215                |        |
+
+|         |       |           |      |   |  |                                                                                                                       |        |
+|---------|-------|-----------|------|---|--|-----------------------------------------------------------------------------------------------------------------------|--------|
+| 2013-09 |       |           |      | - |  | Vendor-specific command code for Trigger-Establishment-Request/Answer corrected                                       | 12.2.1 |
+| 2013-12 | CT#62 | CP-130624 | 0369 | - |  | New AVP for optimized LCS procedure for combined MME/SGSN                                                             | 12.3.0 |
+|         |       | CP-130631 | 0370 | 1 |  | Adding E-SMLC provided Cell info and Cell Portion                                                                     |        |
+|         |       | CP-130800 | 0371 | - |  | New AVPs for SMS for IMS UE without MSISDN in TS 29.338                                                               |        |
+|         |       | CP-130600 | 0376 | 1 |  | Allocation of Diameter codes for 32.299                                                                               |        |
+|         |       | CP-130605 | 0378 | - |  | Allocation of Diameter codes for 29.212                                                                               |        |
+|         |       | CP-130639 | 0380 | - |  | SGSN CAMEL Subscription Indication                                                                                    |        |
+| 2014-03 | CT#63 | CP-140180 | 0381 | 2 |  | Protocol enhancements for the support of device replace procedure                                                     | 12.4.0 |
+|         |       | CP-140035 | 0384 | - |  | New AVP for the support of combined MME/SGSN                                                                          |        |
+|         |       | CP-140023 | 0383 | 1 |  | Definition of WLAN-related AVPs                                                                                       |        |
+| 2014-06 | CT#64 | CP-140211 | 0385 | 1 |  | Protocol enhancements to indicate support of device recall and replace by SMS-SC                                      | 12.5.0 |
+|         |       | CP-140251 | 0402 | 1 |  | AVP allocation for Error handling, MTC error diagnostic                                                               |        |
+|         |       | CP-140257 | 0391 | 1 |  | SS-Status AVP Definition                                                                                              |        |
+|         |       | CP-140252 | 0392 | - |  | Definition of AVPs for Network Location in TWLAN                                                                      |        |
+|         |       | CP-140236 | 0399 | - |  | TWAN-BSSID AVP re-naming                                                                                              |        |
+|         |       | CP-140247 | 0397 | - |  | New AVPs for Trusted WLAN access                                                                                      |        |
+|         |       | CP-140231 | 0390 | 1 |  | Adding Codes for 29.214                                                                                               |        |
+| 2014-09 | CT#65 | CP-140515 | 0403 | 1 |  | T-GRUU restoration                                                                                                    | 12.6.0 |
+|         |       | CP-140517 | 0404 | 1 |  | MB2-C codes                                                                                                           |        |
+|         |       | CP-140505 | 0405 | 1 |  | New AVPs for Trusted WLAN access                                                                                      |        |
+|         |       | CP-140506 | 0406 | 1 |  | P-CSCF Restoration indication                                                                                         |        |
+|         |       | CP-140516 | 0407 | 2 |  | Closing TS 29.234 and reused AVP in TS 29.273                                                                         |        |
+|         |       | CP-140513 | 0408 | - |  | Identification of the HSS                                                                                             |        |
+|         |       |           |      |   |  | Editorial: WLAN-offloadability AVP codes added as in CR C4-141648.                                                    |        |
+| 2014-12 | CT#66 | CP-140785 | 0409 | 1 |  | New AVP for MBMS restoration                                                                                          | 12.7.0 |
+|         |       |           | 0430 | - |  | New Diagnostic-Info AVP for MBMS restoration                                                                          |        |
+|         |       |           | 0410 | 1 |  | WLCP key for WLCP signalling protection                                                                               |        |
+|         |       |           | 0411 | - |  | Reset-ID                                                                                                              |        |
+|         |       |           | 0416 | 1 |  | Code definitions for 32.299                                                                                           |        |
+|         |       |           | 0428 | - |  | Removal of I-WLAN AVPs                                                                                                |        |
+|         |       |           | 0429 | 1 |  | Reference correction                                                                                                  |        |
+|         |       |           | 0433 | - |  | Code allocation for 29.212                                                                                            |        |
+|         |       |           | 0418 | - |  | MDT PLMN List                                                                                                         |        |
+|         |       |           | 0422 | 1 |  | Codes Allocation for PC2 Protocol                                                                                     |        |
+|         |       |           | 0423 | 4 |  | Codes Allocation for PC4a Protocol                                                                                    |        |
+|         |       |           | 0431 | 3 |  | Allocation of values for Application ID, Command codes, AVP codes and Experimental-Result codes used in the TS 29.345 |        |
+|         |       |           | 0434 | 1 |  | Command Code and Error Code for ProSe Initial Location Information Retrieval                                          |        |
+|         |       |           | 0425 | - |  | Corrections of the type of some AVPs                                                                                  |        |
+|         |       |           | 0426 | 1 |  | OFR-Flags AVP code                                                                                                    |        |
+|         |       |           | 0427 | 1 |  | P-CSCF Restoration mechanism new error                                                                                |        |
+| 2015-03 | CT#67 | CP-150015 | 0447 | - |  | Renaming of Location-Type AVP                                                                                         | 12.8.0 |
+|         |       |           | 0437 | 1 |  | Location reporting in emergency 1xSRVCC                                                                               |        |
+|         |       |           | 0435 | - |  | AVP codes for GCSE MB2-C                                                                                              |        |
+|         |       |           | 0442 | 1 |  | New AVPs and range of transient failure result codes in TS 29.214                                                     |        |
+|         |       |           | 0438 | 1 |  | Allocation of code for Authorized-Discovery-Range AVP (TS 29.344)                                                     |        |
+|         |       |           | 0440 | 2 |  | Location Update Trigger                                                                                               |        |
+|         |       |           | 0441 | 1 |  | AVP codes allocation for Validity related AVPs for TS 29.345                                                          |        |
+|         |       |           | 0443 | - |  | Allocation of codes for the Integrity Checks. Aspect AVPs                                                             |        |
+| 2015-03 | CT#67 | CP-150039 | 0439 | 1 |  | Diameter Application Identifier for Np protocol                                                                       | 13.0.0 |
+| 2015-06 | CT#68 | CP-150257 | 0450 | 1 |  | AVP code allocation for Match Refresh Timer AVP in TS 29.345                                                          | 13.1.0 |
+|         |       | CP-150247 | 0457 | - |  | Wrong CR implementation of CR 0416r1                                                                                  |        |
+|         |       | CP-150249 | 0459 | 1 |  | AVP code allocation for 32.299                                                                                        |        |
+|         |       | CP-150263 | 0452 | 1 |  | AVP codes for Access Restriction Data per PLMN                                                                        |        |
+|         |       | CP-150372 | 0461 | - |  | IP-SM-GW-Realm                                                                                                        |        |
+| 2015-09 | CT#69 | CP-150454 | 0462 | - |  | Subscription data for extended buffering at the SGW                                                                   | 13.2.0 |
+|         |       | CP-150442 | 0463 | - |  | Overlapping transaction over S6b                                                                                      |        |
+|         |       | CP-150453 | 0464 | 2 |  | Addition of IMSI Group Id AVP definition                                                                              |        |
+|         |       | CP-150449 | 0465 | 3 |  | Addition of CP parameter AVP definition                                                                               |        |
+|         |       | CP-150431 | 0470 | 1 |  | AVP codes for TS 29.212                                                                                               |        |
+|         |       | CP-150456 | 0471 | 3 |  | AVP definition for S6t                                                                                                |        |
+| 2015-12 | CT#70 | CP-150761 | 0473 | - |  | Addition of MBMS-Cell-List AVP                                                                                        | 13.3.0 |
+
+|         |       |           |      |   |  |                                                                                                                                |        |
+|---------|-------|-----------|------|---|--|--------------------------------------------------------------------------------------------------------------------------------|--------|
+|         |       | CP-150778 | 0474 | - |  | S6t Application ID and Command Codes                                                                                           |        |
+|         |       | CP-150778 | 0474 | 1 |  | Bitmask to inform the SCEF of the Monitoring capabilities                                                                      |        |
+|         |       | CP-150778 | 0490 | 1 |  | AVP codes for MONTE T6a/b interface                                                                                            |        |
+|         |       | CP-150778 | 0491 | 1 |  | Correction to SCEF-Reference-ID and SCEF-Reference-ID-For-Deletion data types                                                  |        |
+|         |       | CP-150778 | 0494 | 2 |  | Definition of AVP for deletion of all Monitoring events assigned to a subscriber (UE)                                          |        |
+|         |       | CP-150778 | 0501 | 1 |  | Definition of AVP SCEF-ID                                                                                                      |        |
+|         |       | CP-150778 | 0502 | 2 |  | Service result per Event configuration                                                                                         |        |
+|         |       | CP-150770 | 0475 | 1 |  | Emergency PDN connection over untrusted WLAN access                                                                            |        |
+|         |       | CP-150776 | 0476 | - |  | EPC-MT-LR and PS-MT-LR procedure for UEs transiently not reachable due to power saving                                         |        |
+|         |       | CP-150776 | 0497 | 1 |  | Mobile Terminating SMS handling for extended Idle mode DRX                                                                     |        |
+|         |       | CP-150776 | 0498 | 1 |  | Mobile Terminating SMS handling for extended Idle mode DRX – Additional Option                                                 |        |
+|         |       | CP-150777 | 0477 | 3 |  | Commands and codes for Np protocol                                                                                             |        |
+|         |       | CP-150772 | 0479 | 1 |  | Definition of ProSe-Metadata-Index-Mask                                                                                        |        |
+|         |       | CP-150772 | 0489 | - |  | Addition of AVPs and result-codes                                                                                              |        |
+|         |       | CP-150772 | 0500 | - |  | Addition of AVP used in match report procedure for eProSe-Ext-CT                                                               |        |
+|         |       | CP-150754 | 0481 | 1 |  | Allowed WAF and/or WWSF Identities                                                                                             |        |
+|         |       | CP-150773 | 0482 | - |  | Add the default access type to 3GPP specific AVP                                                                               |        |
+|         |       | CP-150781 | 0484 | 1 |  | AVP code allocation for "UE Usage Type"                                                                                        |        |
+|         |       | CP-150755 | 0486 | - |  | Metadata in Match-Report                                                                                                       |        |
+|         |       | CP-150755 | 0488 | - |  | New Group AVP for ProSe direct discovery procedures                                                                            |        |
+|         |       | CP-150771 | 0492 | 1 |  | Definition of AVP for AESE-CT                                                                                                  |        |
+|         |       | CP-150771 | 0496 | 1 |  | Command codes and AVP range for TS 29.154 and TS 29.153                                                                        |        |
+|         |       | CP-150776 | 0495 | 1 |  | AVP codes for Indoor Positioning support in SLg/Lgd                                                                            |        |
+| 2016-03 | CT#71 | CP-160041 | 0503 | - |  | Application ID for St                                                                                                          | 13.4.0 |
+|         |       | CP-160041 | 0506 | 1 |  | Correction on TS numbers                                                                                                       |        |
+|         |       | CP-160041 | 0510 | - |  | AVPs for the Rx Diameter application                                                                                           |        |
+|         |       | CP-160041 | 0514 | 2 |  | AVP code reservation for 32.299                                                                                                |        |
+|         |       | CP-160041 | 0518 | 1 |  | Codes for 29.212                                                                                                               |        |
+|         |       | CP-160029 | 0505 | 3 |  | New AVP assignment for MONTE                                                                                                   |        |
+|         |       | CP-160029 | 0509 | - |  | Change of type of Monitoring-Duration AVP to represent an absolute time                                                        |        |
+|         |       | CP-160035 | 0507 | - |  | Remove the default access AVP                                                                                                  |        |
+|         |       | CP-160035 | 0508 | - |  | Specific AVP codes for NBIFOM                                                                                                  |        |
+|         |       | CP-160030 | 0511 | - |  | Alert procedure from MME/SGSN to SMS-GMSC for MT SMS to UE using eDRX                                                          |        |
+|         |       | CP-160037 | 0512 | - |  | ePDG retrieval of WLAN Location Information                                                                                    |        |
+|         |       | CP-160033 | 0513 | 2 |  | Definition of AVP Authorization of NIDD                                                                                        |        |
+|         |       | CP-160033 | 0520 | 2 |  | New PDN-Type for Cellular IoT                                                                                                  |        |
+|         |       | CP-160036 | 0517 | 1 |  | Monitoring update and Reporting of update result                                                                               |        |
+|         |       | CP-160036 | 0519 | 3 |  | Allocation of new Diameter Application ID and commands code for PC2 protocol                                                   |        |
+| 2016-03 | CT#71 | CP-160018 | 0515 | 1 |  | AVP code reservation for 32.299                                                                                                | 14.0.0 |
+| 2016-06 | CT#72 | CP-160236 | 0526 | 1 |  | Command Codes for 29.212                                                                                                       | 14.1.0 |
+| 2016-06 | CT#72 | CP-160236 | 0543 | - |  | AVP code range 3900-3999                                                                                                       | 14.1.0 |
+| 2016-06 | CT#72 | CP-160236 | 0557 | 1 |  | New AVPs in TS 29.214                                                                                                          | 14.1.0 |
+| 2016-06 | CT#72 | CP-160236 | 0565 | - |  | AVP codes for 29.212                                                                                                           | 14.1.0 |
+| 2016-06 | CT#72 | CP-160232 | 0528 | 2 |  | AVP Codes for 29.343                                                                                                           | 14.1.0 |
+| 2016-06 | CT#72 | CP-160232 | 0533 | 3 |  | Addition of new AVPs for ProSe direct discovery security and open ProSe direct discovery with application-controlled extension | 14.1.0 |
+| 2016-06 | CT#72 | CP-160232 | 0540 | - |  | Reserved Experimental Result Codes for TS 29.343                                                                               | 14.1.0 |
+| 2016-06 | CT#72 | CP-160232 | 0549 | - |  | Assignment of application ID and command code for PC2 reference point                                                          | 14.1.0 |
+| 2016-06 | CT#72 | CP-160228 | 0531 | - |  | IANA Command Code Registration                                                                                                 | 14.1.0 |
+| 2016-06 | CT#72 | CP-160228 | 0541 | 1 |  | CIoT new commands and Diameter error                                                                                           | 14.1.0 |
+| 2016-06 | CT#72 | CP-160228 | 0550 | - |  | NIDD authorisation update                                                                                                      | 14.1.0 |
+| 2016-06 | CT#72 | CP-160228 | 0560 | 3 |  | Serving PLMN Rate Control                                                                                                      | 14.1.0 |
+| 2016-06 | CT#72 | CP-160228 | 0563 | - |  | New AVP for APN Rate Control                                                                                                   | 14.1.0 |
+| 2016-06 | CT#72 | CP-160233 | 0537 | 1 |  | Renaming of Validity-Time AVP                                                                                                  | 14.1.0 |
+| 2016-06 | CT#72 | CP-160233 | 0562 | 1 |  | New AVPs allocated for 29.153 and 29.154                                                                                       | 14.1.0 |
+| 2016-06 | CT#72 | CP-160225 | 0545 | 3 |  | SCEF Realm                                                                                                                     | 14.1.0 |
+| 2016-06 | CT#72 | CP-160225 | 0548 | - |  | Cleanup up on MONTE AVP's                                                                                                      | 14.1.0 |
+| 2016-06 | CT#72 | CP-160227 | 0546 | - |  | IANA assigned application Id and command code values                                                                           | 14.1.0 |
+| 2016-06 | CT#72 | CP-160227 | 0547 | 2 |  | Allocation of AVP codes and Experimental Result codes for Diameter Data Management application                                 | 14.1.0 |
+| 2016-06 | CT#72 | CP-160231 | 0553 | 1 |  | 3GPP specific AVP for NBIFOM                                                                                                   | 14.1.0 |
+| 2016-06 | CT#72 | CP-160222 | 0555 | 1 |  | Shared Subscription data update                                                                                                | 14.1.0 |
+
+|         |       |           |      |   |  |                                                                   |        |
+|---------|-------|-----------|------|---|--|-------------------------------------------------------------------|--------|
+| 2016-09 | CT#73 | CP-160424 | 0570 | 1 |  | Missing AVP codes and Experimental-Result codes for T6a           | 14.2.0 |
+| 2016-09 | CT#73 | CP-160424 | 0574 | 1 |  | Allocate of AVP Handling of Exception Reports in the Core Network | 14.2.0 |
+| 2016-09 | CT#73 | CP-160419 | 0572 | 1 |  | AVP codes for 32.299                                              | 14.2.0 |
+| 2016-09 | CT#73 | CP-160419 | 0576 | 1 |  | AVP code for 29.214                                               | 14.2.0 |
+| 2016-09 | CT#73 | CP-160419 | 0578 | 1 |  | AVP code for 29.212                                               | 14.2.0 |
+| 2016-09 | CT#73 | CP-160436 | 0568 | 1 |  | STa and SWm extensions for IMEI check                             | 14.2.0 |
+| 2016-12 | CT#74 | CP-160650 | 0582 | - |  | AVP code alignment with 29.272                                    | 14.3.0 |
+| 2016-12 | CT#74 | CP-160679 | 0579 | 1 |  | AVPs for Handover of Emergency PDN Connections                    | 14.3.0 |
+| 2016-12 | CT#74 | CP-160678 | 0583 | 1 |  | New Diameter Application Code, AVP and Result Code for V2X        | 14.3.0 |
+| 2016-12 | CT#74 | CP-160653 | 0585 | 1 |  | Renaming of Emergency-Indication AVP                              | 14.3.0 |
+| 2016-12 | CT#74 | CP-160670 | 0586 | 2 |  | New AVPs for TS 29.214                                            | 14.3.0 |
+| 2016-12 | CT#74 | CP-160660 | 0590 | - |  | S6t-HSS-Cause                                                     | 14.3.0 |
+| 2016-12 | CT#74 | CP-160669 | 0591 | - |  | AVP codes for 29.468                                              | 14.3.0 |
+| 2017-03 | CT#75 | CP-170039 | 0592 | 1 |  | Enhanced Coverage                                                 | 14.4.0 |
+| 2017-03 | CT#75 | CP-170039 | 0593 | 1 |  | Inter-RAT PDN-Continuity                                          | 14.4.0 |
+| 2017-03 | CT#75 | CP-170039 | 0595 | 1 |  | NIDD Authorization revocation                                     | 14.4.0 |
+| 2017-03 | CT#75 | CP-170036 | 0594 | 1 |  | Loss Of Connectivity Reason                                       | 14.4.0 |
+| 2017-03 | CT#75 | CP-170036 | 0602 | 1 |  | Subscription parameters for eDRX                                  | 14.4.0 |
+| 2017-03 | CT#75 | CP-170036 | 0607 | 1 |  | Support of long and short Macro eNodeB IDs                        | 14.4.0 |
+| 2017-03 | CT#75 | CP-170025 | 0597 | - |  | AVP codes for 32.299                                              | 14.4.0 |
+| 2017-03 | CT#75 | CP-170043 | 0598 | 1 |  | New AVP for UE-PC5-AMBR                                           | 14.4.0 |
+| 2017-03 | CT#75 | CP-170043 | 0603 | 1 |  | Correct Diameter Result Code Allocated for V2X                    | 14.4.0 |
+| 2017-03 | CT#75 | CP-170049 | 0601 | 1 |  | AVPs for ERP in 29.273                                            | 14.4.0 |
+| 2017-03 | CT#75 | CP-170052 | 0605 | - |  | Update of the name of MCPTT-User-Profile-Data AVP                 | 14.4.0 |
+| 2017-03 | CT#75 | CP-170045 | 0606 | - |  | Support of MCVideo and MCData Services                            | 14.4.0 |
+| 2017-06 | CT#76 | CP-171029 | 0600 | 4 |  | New AVP for Group Based MONTE Event Configuration via HSS         | 14.5.0 |
+| 2017-06 | CT#76 | CP-171017 | 0609 | - |  | New AVPs in 29.272 for MBSFN MDT                                  | 14.5.0 |
+| 2017-06 | CT#76 | CP-171026 | 0610 | - |  | AVP codes for 29.212                                              | 14.5.0 |
+| 2017-06 | CT#76 | CP-171026 | 0611 | - |  | AVP codes for 29.214                                              | 14.5.0 |
+| 2017-06 | CT#76 | CP-171030 | 0612 | 1 |  | AVP code allocation for 29.172 for Location Services for C IoT    | 14.5.0 |
+| 2017-06 | CT#76 | CP-171030 | 0613 | - |  | Addition of APN-Validity-Time AVP                                 | 14.5.0 |
+| 2017-06 | CT#76 | CP-171026 | 0615 | - |  | AVP codes for 32.299                                              | 14.5.0 |
+| 2017-09 | CT#77 | CP-172018 | 0616 | 1 |  | Reliable Data Service Success cause                               | 14.6.0 |
+| 2017-09 | CT#77 | CP-172018 | 0617 | 1 |  | Reliable Data Service                                             | 14.6.0 |
+| 2017-09 | CT#77 | CP-172026 | 0618 | 1 |  | Enhancements for NAPs                                             | 15.0.0 |
+| 2017-12 | CT#78 | CP-173011 | 0625 | - |  | AVP codes for TS 29.219, TS 29.212 and TS 29.214                  | 15.1.0 |
+| 2017-12 | CT#78 | CP-173033 | 0619 | 1 |  | Suggested Network Configuration Request                           | 15.1.0 |
+| 2017-12 | CT#78 | CP-173028 | 0620 | - |  | Monitoring Event Report Status                                    | 15.1.0 |
+| 2017-12 | CT#78 | CP-173028 | 0626 | - |  | AVP code for PLMN-ID-Requested in S6t                             | 15.1.0 |
+| 2017-12 | CT#78 | CP-173032 | 0627 | - |  | New AVP for PC5-tech for WLAN based ProSe Direct Discovery        | 15.1.0 |
+| 2018-03 | CT#79 | CP-180021 | 0628 | 1 |  | Service Gap Time AVP                                              | 15.2.0 |
+| 2018-03 | CT#79 | CP-180020 | 0629 | 1 |  | AVP codes for 32.299                                              | 15.2.0 |
+| 2018-03 | CT#79 | CP-180025 | 0630 | - |  | IMSI-Group-Id retrieval                                           | 15.2.0 |
+| 2018-06 | CT#80 | CP-181120 | 0631 | 1 |  | Supported-Services and Supported-Monitoring-Events                | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0632 | 1 |  | New AVPs in TS 29.212 for eVoLP                                   | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0633 | 1 |  | Reserve Diameter codes for TS 29.561                              | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0635 | - |  | Application ID for Diameter Nta                                   | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0636 | 1 |  | AVP codes for TS 29.154                                           | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0637 | 1 |  | New AVP for subscription for Aerial UE in 3GPP system             | 15.3.0 |
+| 2018-06 | CT#80 | CP-181120 | 0639 | 1 |  | AVP codes for 32.299                                              | 15.3.0 |
+| 2018-06 | CT#80 | CP-181124 | 0640 | 1 |  | Subscription data for ciphering keys                              | 15.3.0 |
+| 2018-06 | CT#80 | CP-181127 | 0634 | - |  | AVP code for NIR-Flags                                            | 15.3.0 |
+| 2018-09 | CT#81 | CP-182080 | 0642 | - |  | AVP code for TS 29.214                                            | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0643 | - |  | AVP codes for TS 29.468                                           | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0644 | - |  | Update tables due to N6                                           | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0645 | 1 |  | Change of value type of Maximum Packet Loss Rate                  | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0646 | 1 |  | Subscribed PTW length                                             | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0647 | 1 |  | Policy Update when UE suspends                                    | 15.4.0 |
+| 2018-09 | CT#81 | CP-182073 | 0648 | 1 |  | Command Codes for Nta Diameter Application                        | 15.4.0 |
+| 2018-09 | CT#81 | CP-182084 | 0649 | - |  | Core Network Restrictions                                         | 15.4.0 |
+| 2018-09 | CT#81 | CP-182071 | 0651 | - |  | DSR-Flag for eDRX-Cycle-Length                                    | 15.4.0 |
+| 2018-12 | CT#82 | CP-183092 | 0653 | 1 |  | Interworking-5GS-Indicator AVP definition                         | 15.5.0 |
+| 2018-12 | CT#82 | CP-183095 | 0652 | 1 |  | Monitoring event report                                           | 15.5.0 |
+| 2018-12 | CT#82 | CP-183102 | 0654 | - |  | Wrong AVP type in Access-Restriction-Data                         | 15.5.0 |
+| 2018-12 | CT#82 | CP-183102 | 0655 | - |  | NIDD group authorization                                          | 15.5.0 |
+| 2019-03 | CT#83 | CP-190036 | 0656 | 1 |  | New AVP for MB2                                                   | 15.6.0 |
+| 2019-03 | CT#83 | CP-190036 | 0657 | 1 |  | RTR-Flags                                                         | 15.6.0 |
+
+|         |        |           |      |   |   |                                                          |        |
+|---------|--------|-----------|------|---|---|----------------------------------------------------------|--------|
+| 2019-03 | CT#83  | CP-190037 | 0658 | 1 |   | Handling of multiple external IDs for the same UE        | 15.6.0 |
+| 2019-09 | CT#85  | CP-192125 | 0662 | - |   | Add P-CSCF subscription info to Restoration information  | 16.0.0 |
+| 2019-09 | CT#85  | CP-192122 | 0661 | 1 |   | Event type PDN Connectivity Status                       | 16.0.0 |
+| 2019-09 | CT#85  | CP-192122 | 0664 | - |   | Ethernet PDN Type AVP                                    | 16.0.0 |
+| 2019-09 | CT#85  | CP-192121 | 0663 | 1 |   | Communication pattern enhancement                        | 16.0.0 |
+| 2019-12 | CT#86  | CP-193035 | 0669 | 1 |   | UE Status Suspend                                        | 16.1.0 |
+| 2019-12 | CT#86  | CP-103038 | 0666 | 1 |   | New Error Code for TS 29.336                             | 16.1.0 |
+| 2019-12 | CT#86  | CP-103038 | 0671 | - |   | Subscribed ARPI AVP                                      | 16.1.0 |
+| 2019-12 | CT#86  | CP-103038 | 0672 | - |   | Network Parameter Configuration Reporting AVP            | 16.1.0 |
+| 2019-12 | CT#86  | CP-103038 | 0673 | 2 |   | New AVP defined in TS 29.214 for Callee-Information      | 16.1.0 |
+| 2019-12 | CT#86  | CP-193040 | 0667 | - |   | S-CSCF restoration after registration timer expiry       | 16.1.0 |
+| 2019-12 | CT#86  | CP-193052 | 0665 | 1 |   | Battery Indication for Communication pattern enhancement | 16.1.0 |
+| 2020-03 | CT#87e | CP-200041 | 0676 | 1 |   | AVP codes for 32,299                                     | 16.2.0 |
+| 2020-03 | CT#87e | CP-200041 | 0678 | - |   | New AVPs in TS 29.214                                    | 16.2.0 |
+| 2020-03 | CT#87e | CP-200027 | 0677 | 3 |   | Addition of AVP code for IAB-Node-Information AVP        | 16.2.0 |
+| 2020-03 | CT#87e | CP-200036 | 0679 | - |   | Subscription data for NR V2X                             | 16.2.0 |
+| 2020-03 | CT#87e | CP-200050 | 0680 | - |   | Reachability Cause                                       | 16.2.0 |
+| 2020-06 | CT#88e | CP-201016 | 0685 | - |   | SMSF Address                                             | 16.3.0 |
+| 2020-06 | CT#88e | CP-201049 | 0681 | - |   | Authorized PLMNs and RATs for V2X                        | 16.3.0 |
+| 2020-06 | CT#88e | CP-201049 | 0682 | - |   | Subscribed PC5 QoS Parameters for NR V2X                 | 16.3.0 |
+| 2020-09 | CT#89e | CP-202094 | 0687 | 1 |   | AVP Codes for TS 29.214                                  | 16.4.0 |
+| 2020-12 | CT#90e | CP-203032 | 0688 | - |   | Extended Reference ID                                    | 16.5.0 |
+| 2021-03 | CT#90e | CP-210057 | 0689 | - |   | Default APN for Ethernet PDN types                       | 16.6.0 |
+| 2021-09 | CT#93e | CP-212073 | 0690 | 1 | F | APN Rate Control Status                                  | 16.7.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29311/raw.md b/marked/Rel-16/29_series/29311/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..253493556c93e882dda8ae94a70dfca5c5cd5ea6
--- /dev/null
+++ b/marked/Rel-16/29_series/29311/raw.md
@@ -0,0 +1,1627 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                                                                                                                                                                       |    |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword ..........................................................................................................................................................................                                                                   | 6  |
+| 1 Scope.......................................................................................................................................................................                                                                        | 7  |
+| 2 References...............................................................................................................................................................                                                                           | 7  |
+| 3 Definitions and abbreviations .................................................................................................................................                                                                                     | 8  |
+| 3.1 Definitions.........................................................................................................................................................                                                                              | 8  |
+| 3.2 Abbreviations ....................................................................................................................................................                                                                                | 9  |
+| 4 Overview of service level interworking for messaging services ............................................................................                                                                                                          | 9  |
+| 4.1 Introduction .......................................................................................................................................................                                                                              | 9  |
+| 4.2 Service level interworking between SM and IM................................................................................................                                                                                                      | 9  |
+| 4.3 Interaction with transport layer interworking....................................................................................................                                                                                                 | 9  |
+| 4.4 Service level interworking between SM and Chat Session..............................................................................                                                                                                              | 10 |
+| 5 Functional entities .................................................................................................................................................                                                                               | 10 |
+| 5.1 Application Server (AS)..................................................................................................................................                                                                                         | 10 |
+| 6 Roles......................................................................................................................................................................                                                                         | 10 |
+| 6.1 IP-Short-Message-Gateway (IP-SM-GW) ......................................................................................................                                                                                                        | 10 |
+| 6.1.1 General ........................................................................................................................................................                                                                                | 10 |
+| 6.1.2 Notification about registration status and UE capabilities ..........................................................................                                                                                                           | 11 |
+| 6.1.3 Handling of routing information .................................................................................................................                                                                                               | 12 |
+| 6.1.3.1 Answering routing information query .................................................................................................                                                                                                         | 12 |
+| 6.1.3.2 Querying of routing information..........................................................................................................                                                                                                     | 12 |
+| 6.1.4 Delivering Short Message(s) as an Instant Message ...................................................................................                                                                                                           | 12 |
+| 6.1.4.1 General.................................................................................................................................................                                                                                      | 12 |
+| 6.1.4.2 Receiving of SMS-DELIVER ..............................................................................................................                                                                                                       | 13 |
+| 6.1.4.3 Sending of Instant Message .................................................................................................................                                                                                                  | 13 |
+| 6.1.4.3.1 Sending of the Instant Message in a SIP MESSAGE request.........................................................                                                                                                                            | 13 |
+| 6.1.4.3.2 Sending of a large Instant Message..................................................................................................                                                                                                        | 14 |
+| 6.1.4.4 Sending of SMS-DELIVER-REPORT .................................................................................................                                                                                                               | 14 |
+| 6.1.4.4.1 Common Procedures ........................................................................................................................                                                                                                  | 14 |
+| 6.1.4.4.2 Sending of SMS-DELIVER-REPORT after Short Message(s) delivered in a SIP MESSAGE request ................................................................................................................................................... | 16 |
+| 6.1.4.4.3 Sending of SMS-DELIVER-REPORT after concatenated Short Messages delivered in a large Instant Message....................................................................................................................................    | 16 |
+| 6.1.4.5 Procedure when delivery of a Short Message as Instant Message is not allowed ...................................                                                                                                                              | 17 |
+| 6.1.4.6 Retry after unsuccessful delivery of Short Message.............................................................................                                                                                                               | 17 |
+| 6.1.5 Delivering an Instant Message as a (concatenated) Short Message in the terminating network.................                                                                                                                                     | 17 |
+| 6.1.5.1 General.................................................................................................................................................                                                                                      | 17 |
+| 6.1.5.2 Receiving of the Instant Message in a SIP MESSAGE request ..........................................................                                                                                                                          | 17 |
+| 6.1.5.3 Sending of SMS-DELIVER (over CS/PS or IP) ..................................................................................                                                                                                                  | 18 |
+| 6.1.5.3.1 General .............................................................................................................................................                                                                                       | 18 |
+| 6.1.5.3.2 Common Procedures ........................................................................................................................                                                                                                  | 18 |
+| 6.1.5.3.3 Sending of SMS-DELIVER over CS/PS ..........................................................................................                                                                                                                | 19 |
+| 6.1.5.3.4 Sending of SMS-DELIVER over IP .................................................................................................                                                                                                            | 19 |
+| 6.1.5.4 Receiving of SMS-DELIVER-REPORT (over CS/PS or IP)...............................................................                                                                                                                             | 19 |
+| 6.1.5.4.1 Receiving of SMS-DELIVER-REPORT over CS/PS.......................................................................                                                                                                                           | 19 |
+| 6.1.5.4.2 Receiving of SMS-DELIVER-REPORT over IP..............................................................................                                                                                                                       | 20 |
+| 6.1.5.5 Sending of IMDN ................................................................................................................................                                                                                              | 21 |
+| 6.1.5.5.1 Sending of IMDN after a (concatenated) Short Message delivery over CS/PS..............................                                                                                                                                      | 21 |
+| 6.1.5.5.2 Sending of IMDN after a (concatenated) Short Message delivery over IP.....................................                                                                                                                                  | 21 |
+| 6.1.5.6 Retry after unsuccessful delivery of Short Message.............................................................................                                                                                                               | 22 |
+| 6.1.5.7 Error handling when interworking from Instant Message to Short Message is not possible ...............                                                                                                                                        | 22 |
+| 6.1.5.8 Partial interworking from Instant Message to Short Message .............................................................                                                                                                                      | 22 |
+| 6.1.6 Submitting an Instant Message as a (concatenated) Short Message in the originating network...............                                                                                                                                       | 22 |
+| 6.1.6.1 General.................................................................................................................................................                                                                                      | 22 |
+| 6.1.6.2 Receiving of the Instant Message in a SIP MESSAGE request ..........................................................                                                                                                                          | 22 |
+| 6.1.6.3 Sending of SMS-SUBMIT over CS/PS ...............................................................................................                                                                                                              | 23 |
+
+|            |                                                                                                                                       |    |
+|------------|---------------------------------------------------------------------------------------------------------------------------------------|----|
+| 6.1.6.4    | Receiving of SMS-SUBMIT-REPORT.....                                                                                                   | 24 |
+| 6.1.6.5    | Receiving of SMS-STATUS-REPORT.....                                                                                                   | 24 |
+| 6.1.6.6    | Sending of IMDN (both for SUBMIT-REPORT and STATUS-REPORT).....                                                                       | 25 |
+| 6.1.6.7    | Error handling when interworking from Instant Message to Short Message is not possible .....                                          | 25 |
+| 6.1.6.8    | Partial interworking from Instant Message to Short Message.....                                                                       | 25 |
+| 6.1.7      | Receiving of the Chat Session invitation request in the terminating network.....                                                      | 26 |
+| 6.1.7.1    | Receiving of the Chat Session SIP INVITE request.....                                                                                 | 26 |
+| 6.1.7.2    | Sending of the SMS-DELIVER (over CS/PS or IP).....                                                                                    | 26 |
+| 6.1.7.3    | Receiving of SMS-DELIVER-REPORT (over CS/PS or IP).....                                                                               | 26 |
+| 6.1.7.3.1  | Receiving of SMS-DELIVER-REPORT over CS/PS.....                                                                                       | 26 |
+| 6.1.7.3.2  | Receiving of SMS-DELIVER-REPORT over IP.....                                                                                          | 27 |
+| 6.1.7.4    | Receiving of the SMS-DELIVER as a response to the Chat Session SIP INVITE request.....                                                | 27 |
+| 6.1.7.5    | Sending of the Chat Session SIP 200 (OK) response as a result of the response from the SMS user.....                                  | 27 |
+| 6.1.8      | Receiving of the Chat Session invitation request in the originating network .....                                                     | 27 |
+| 6.1.8.1    | Receiving of the Chat Session SIP INVITE request.....                                                                                 | 27 |
+| 6.1.8.2    | Sending of the SMS-SUBMIT.....                                                                                                        | 28 |
+| 6.1.8.3    | Receiving of SMS-SUBMIT-REPORT.....                                                                                                   | 28 |
+| 6.1.8.4    | Receiving of the SMS-DELIVER as a response to the Chat Session invitation .....                                                       | 28 |
+| 6.1.8.5    | Sending automatic Chat Session SIP 200 (OK) response.....                                                                             | 28 |
+| 6.1.9      | Delivering a Short Message as an MSRP SEND in an ongoing Chat Session anchored in the terminating network.....                        | 29 |
+| 6.1.9.1    | Receiving of SMS-DELIVER when recipient is an MSISDN assigned by the IP-SM-GW on the terminating side.....                            | 29 |
+| 6.1.9.2    | Sending of MSRP SEND request .....                                                                                                    | 29 |
+| 6.1.9.3    | Sending of SMS-DELIVER-REPORT.....                                                                                                    | 29 |
+| 6.1.10     | Delivering a Short Message as an MSRP SEND request in an ongoing Chat Session anchored in the originating network .....               | 30 |
+| 6.1.10.1   | Receiving of SMS-DELIVER when recipient address is actual MSISDN of recipient .....                                                   | 30 |
+| 6.1.10.2   | Receiving of SMS-DELIVER when recipient is an MSISDN assigned by the IP-SM-GW on the originating side .....                           | 31 |
+| 6.1.10.3   | Sending of MSRP SEND request .....                                                                                                    | 31 |
+| 6.1.10.4   | Sending of SMS-DELIVER-REPORT .....                                                                                                   | 31 |
+| 6.1.11     | Delivering an MSRP SEND request in an ongoing Chat Session anchored in the terminating network as a (concatenated) Short Message..... | 31 |
+| 6.1.11.1   | Receiving of the MSRP SEND request .....                                                                                              | 31 |
+| 6.1.11.2   | Sending of the SMS-DELIVER (over CS/PS or IP).....                                                                                    | 31 |
+| 6.1.11.3   | Receiving of SMS-DELIVER-REPORT (over CS/PS or IP).....                                                                               | 32 |
+| 6.1.11.3.1 | Receiving of SMS-DELIVER-REPORT over CS/PS.....                                                                                       | 32 |
+| 6.1.11.3.2 | Receiving of SMS-DELIVER-REPORT over IP.....                                                                                          | 33 |
+| 6.1.11.4   | Sending of the MSRP REPORT request.....                                                                                               | 33 |
+| 6.1.12     | Submitting an MSRP SEND request in an ongoing Chat Session anchored in the originating network as a (concatenated) Short Message..... | 34 |
+| 6.1.12.1   | Receiving of the MSRP SEND request .....                                                                                              | 34 |
+| 6.1.12.2   | Sending of the SMS-SUBMIT.....                                                                                                        | 34 |
+| 6.1.12.3   | Receiving of SMS-SUBMIT-REPORT (over CS/PS or IP).....                                                                                | 34 |
+| 6.1.12.4   | Sending of the MSRP REPORT request.....                                                                                               | 34 |
+| 6.1.13     | Handling of the Chat Session teardown request received as a Short Message in the terminating network.....                             | 34 |
+| 6.1.13.1   | General.....                                                                                                                          | 34 |
+| 6.1.13.2   | Receiving of SMS-DELIVER containing a Chat Session teardown request.....                                                              | 35 |
+| 6.1.14     | Handling of the Chat Session teardown request received as a Chat Session BYE in the terminating network.....                          | 35 |
+| 6.1.14.1   | Receiving of the Chat Session BYE request.....                                                                                        | 35 |
+| 6.1.14.2   | Sending of the SMS-DELIVER (over CS/PS or IP).....                                                                                    | 35 |
+| 6.1.14.3   | Receiving of SMS-DELIVER-REPORT (over CS/PS or IP).....                                                                               | 36 |
+| 6.1.14.3.1 | Receiving of SMS-DELIVER-REPORT over CS/PS.....                                                                                       | 36 |
+| 6.1.14.3.2 | Receiving of SMS-DELIVER-REPORT over IP.....                                                                                          | 36 |
+| 6.1.14.4   | Sending of the SIP 200 (OK) response to a BYE request for a Chat Session .....                                                        | 36 |
+| 6.1.15     | Handling of the Chat Session teardown request received as a Short Message in the originating network .....                            | 36 |
+
+|                               |                                                                                                               |           |
+|-------------------------------|---------------------------------------------------------------------------------------------------------------|-----------|
+| 6.1.16                        | Handling of the Chat Session teardown request received as a Chat Session BYE in the originating network ..... | 36        |
+| 6.1.16.1                      | Receiving of the Chat Session BYE request.....                                                                | 36        |
+| 6.1.16.2                      | Sending of the SMS-SUBMIT .....                                                                               | 36        |
+| 6.1.16.3                      | Receiving of SMS-SUBMIT-REPORT (over CS/PS or IP).....                                                        | 37        |
+| 6.1.17                        | Handling of Participant Information .....                                                                     | 37        |
+| 6.1.17.1                      | General .....                                                                                                 | 37        |
+| 6.1.17.2                      | Subscribing to Participant Information.....                                                                   | 37        |
+| 6.1.17.3                      | Receiving of a Participant Information Notification .....                                                     | 37        |
+| 6.1.17.4                      | Sending Participant Information as SMS-Deliver when interworking in the terminating network .....             | 37        |
+| 6.1.17.5                      | Sending Participant Information as SMS-SUBMIT when interworking in the originating network ....               | 38        |
+| 6.1.18                        | Common procedures for chat session interworking .....                                                         | 38        |
+| 6.1.18.1                      | Determining if a received Short Message is associated to a Chat Session .....                                 | 38        |
+| 6.1.18.2                      | Leaving a Chat Session.....                                                                                   | 38        |
+| 6.1.18.3                      | Sending SMS-DELIVER – common procedures .....                                                                 | 38        |
+| 6.1.18.3.1                    | General .....                                                                                                 | 38        |
+| 6.1.18.3.2                    | Sending of SMS-DELIVER over CS/PS .....                                                                       | 39        |
+| 6.1.18.3.3                    | Sending of SMS-DELIVER over IP .....                                                                          | 39        |
+| 6.1.18.4                      | Sending SMS-SUBMIT – common procedures .....                                                                  | 39        |
+| 6.1.18.5                      | Sending SMS-DELIVER-REPORT .....                                                                              | 40        |
+| <b>Annex A (normative):</b>   | <b>Impacts of TP parameters in a Short Message on service level interworking .....</b>                        | <b>41</b> |
+| A.1                           | Scope.....                                                                                                    | 41        |
+| A.2                           | TP-Data-Coding-Scheme (TP-DCS).....                                                                           | 41        |
+| A.3                           | TP-User-Data Header Information Elements (UDH-IE) .....                                                       | 43        |
+| A.4                           | TP-Protocol-Identifier (TP-PID).....                                                                          | 45        |
+| <b>Annex B (normative):</b>   | <b>Anonymous SMS .....</b>                                                                                    | <b>46</b> |
+| B.1                           | Scope.....                                                                                                    | 46        |
+| B.2                           | Anonymous address in SMS .....                                                                                | 46        |
+| <b>Annex C (informative):</b> | <b>Change history.....</b>                                                                                    | <b>46</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the protocol details of service level interworking between Instant Message (OMA-TS-SIMPLE\_IM [4]) or Chat Session (OMA-TS-CPM\_Conv\_Fnct [17]) using the 3GPP IP Multimedia CN subsystem and the Short Message Service over both legacy CS/PS network as specified in the 3GPP TS 23.040 [2] and a generic IP Connectivity Access Network (IP-CAN) as specified in the 3GPP TS 24.341 [5]. These include:
+
+- Procedures to implement service level interworking between IM and SM;
+- Procedures to implement service level interworking between CPM and SM;
+- Enhancement of the IP-SM-GW as an Application Server to support service selection, authorization and mapping between IM or CPM and SM protocols; and
+- Interaction between service level interworking and transport layer interworking.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".
+- [3] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
+- [4] OMA OMA-TS-SIMPLE\_IM-V1\_0: "Instant Messaging using SIMPLE", <http://www.openmobilealliance.org/>.
+- [5] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3".
+- [6] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
+- [7] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [8] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
+- [9] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
+- [10] IETF RFC 3261: "SIP: Session Initiation Protocol".
+- [11] 3GPP TS 23.002: "Network architecture".
+- [12] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2".
+- [13] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)".
+- [14] 3GPP TS 23.042: "Compression algorithm for text messaging services".
+- [15] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
+
+- [16] 3GPP TS 26.141: "IP Multimedia System (IMS) Messaging and Presence; Media formats and codecs".
+- [17] OMA OMA-TS-CPM\_Conv\_Fnct-V1\_0: "CPM Conversation Functions", <http://www.openmobilealliance.org/>.
+- [18] IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State".
+- [19] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)".
+- [20] OMA OMA-TS-CPM\_System\_Description-V1\_0: "Converged IP Messaging System Description", <http://www.openmobilealliance.org/>.
+- [21] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
+- [22] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface".
+- [23] IETF RFC 822: "Standard for the Format of ARPA Internet Text Messages".
+- [24] 3GPP TS 23.038: "Alphabets and language-specific information".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.204 [6], subclause 3.1 apply:
+
+**SMSIP MESSAGE**  
+**Instant Message**
+
+For the purposes of the present document, the following terms and definitions given in RFC 3261 [10] apply.
+
+**Header**  
+**Header field**  
+**Request**  
+**Response**  
+**Status-Code** (see RFC 3261 [10], subclause 7.2)
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.002 [11], subclauses 4.1.1.1 and 4a.7 apply:
+
+**Home Subscriber Server (HSS)**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.040 [2] apply:
+
+**WVG Object**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [12], subclauses 4.3.3.1, 4.3.6 and 4.6 apply:
+
+**Serving-CSCF (S-CSCF)**
+
+For the purposes of the present document, the following terms and definitions given in OMA-TS-CPM\_Conv\_Fnct [17] apply:
+
+**Participant Information**
+
+For the purposes of the present document, the following term and definition applies:
+
+**Chat Session:** A session established between two or more participants that is used for exchanging messages.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|          |                                          |
+|----------|------------------------------------------|
+| AS       | Application Server                       |
+| CPIM     | Common Profile for Instant Messaging     |
+| CPM      | Converged IP Messaging                   |
+| IM       | Instant Message                          |
+| IMDN     | Instant Message Disposition Notification |
+| IP-SM-GW | IP-Short-Message-Gateway                 |
+| MSRP     | Message Session Relay Protocol           |
+| SM       | Short Message                            |
+| UDH      | User Data Header                         |
+| WVG      | Wireless Vector Graphics                 |
+
+# --- 4 Overview of service level interworking for messaging services
+
+## 4.1 Introduction
+
+The service level interworking for messaging services provides the interworking function between Instant Message or Chat Sessions and the Short Message to enable the communication between SM UE and Instant Message or CPM UE. The architecture for service level interworking is specified in 3GPP TS 23.204 [6].
+
+## 4.2 Service level interworking between SM and IM
+
+In order to provide the service level interworking between SM and IM, the following protocol mapping functionalities defined in 3GPP TS 23.204 [6] shall be supported:
+
+- Instant Message mapped to Short Message over CS/PS;
+- Instant Message mapped to Short Message over IP; and
+- Short Message mapped to Instant Message.
+
+## 4.3 Interaction with transport layer interworking
+
+Both transport layer interworking and service level interworking shall be provided by IP-SM-GW. The interaction between transport layer interworking and service level interworking depends on the user subscription and authorization, on the UE capabilities, and on operator policy.
+
+If a user only subscribes to either transport layer interworking or to service level interworking, only procedures defined for the subscribed interworking shall be performed by the IP-SM-GW.
+
+If a user subscribes to both transport layer interworking and service level interworking, but the user is only authorised for one of the interworking when the message is processed, only the authorised interworking shall be performed by the IP-SM-GW.
+
+If a user subscribes to both transport layer interworking and service level interworking, and is authorised for both, the behaviour of the IP-SM-GW depends on the specific scenario, on the registered capabilities of the UE, and finally is defined by operator policy and user preferences.
+
+## 4.4 Service level interworking between SM and Chat Session
+
+In order to provide the service level interworking between SM and Chat Session, the following protocol mapping functionalities defined in 3GPP TS 23.204 [6] shall be supported:
+
+- Chat Session invitation request mapped to Short Message;
+- Short Message mapped to Chat Session MSRP SEND request;
+- Chat Session MSRP SEND request mapped to Short Message;
+- Short Message mapped to Chat Session teardown request;
+- Chat Session teardown request mapped to Short Message; and
+- Event package for conference state information specified in IETF RFC 4575 [18] mapped to Short Message.
+
+# --- 5 Functional entities
+
+## 5.1 Application Server (AS)
+
+An AS may implement the role of an IP-SM-GW (see subclause 6.1).
+
+# --- 6 Roles
+
+## 6.1 IP-Short-Message-Gateway (IP-SM-GW)
+
+### 6.1.1 General
+
+An IP-SM-GW is an entity that provides the service level interworking for:
+
+- delivering a Short Message or concatenated Short Messages as an Instant Message;
+- delivering concatenated Short Messages as a large Instant Message;
+- delivering an Instant Message as a (concatenated) Short Message in the terminating network;
+- submitting an Instant Message as a (concatenated) Short Message in the originating network;
+- delivering a Chat Session invitation as a Short Message;
+- sending a Chat Session invitation response based on the contents of the received Short Message;
+- delivering a Short Message as Chat Session MSRP SEND request;
+- delivering a Chat Session MSRP SEND request as a Short Message;
+- sending a Chat Session teardown request based on the contents of the received Short Message;
+- delivering a Chat Session teardown request as a Short Message; and
+- delivering information about Chat Session changes to the SMS user.
+
+In addition to the procedures specified in subclause 6.1, the IP-SM-GW shall support the procedures specified in subclause 5.7 of 3GPP TS 24.229 [3].
+
+The IP-SM-GW handles the following messages for SM to IM interworking:
+
+- receiving a SIP REGISTER request, as described in subclause 6.1.2;
+- receiving a routing information query as described in subclause 6.1.3.1;
+- receiving an SMS-DELIVER (MT-FORWARD-SHORT-MESSAGE) as described in subclause 6.1.4.2;
+
+- sending a SIP MESSAGE request as described in subclause 6.1.4.3.1;
+- sending a SIP INVITE request as described in subclause 6.1.4.3.2; and
+- sending an SMS-DELIVER-REPORT as described in subclause 6.1.4.4.
+
+The IP-SM-GW handles the following messages for IM to SM interworking:
+
+- sending MAP-SEND-ROUTING-INFO-FOR-SM as described in subclause 6.1.3.2;
+- receiving a SIP MESSAGE request as described in subclause 6.1.5.2 and subclause 6.1.6.2;
+- sending an SMS-DELIVER (MT-FORWARD-SHORT-MESSAGE) as described in subclause 6.1.5.3;
+- sending an SMS-SUBMIT (MO-FORWARD-SHORT-MESSAGE) as described in subclause 6.1.6.3;
+- receiving an SMS-DELIVER-REPORT as described in subclause 6.1.5.4;
+- receiving an SMS-SUBMIT-REPORT (MO-FORWARD-SHORT-MESSAGE-ACK) as described in subclause 6.1.6.4;
+- receiving an SMS-STATUS-REPORT (MT-FORWARD-SHORT-MESSAGE) as described in subclause 6.1.6.5; and
+- sending a SIP MESSAGE request containing an IMDN as described in subclause 6.1.5.5 and subclause 6.1.6.6.
+
+The IP-SM-GW handles the following messages for Chat Session to SM interworking:
+
+- receiving a SIP INVITE request as described in subclauses 6.1.7 and 6.1.8;
+- sending an SMS-DELIVER (MT-FORWARD-SHORT-MESSAGE) and receiving of SMS-DELIVER-REPORT as described in subclauses 6.1.7.2, 6.1.7.3, 6.1.14.2 and 6.1.14.3;
+- receiving an SMS-DELIVER (MT-FORWARD-SHORT-MESSAGE) and sending of an SMS-DELIVER-REPORT as described in subclauses 6.1.9, 6.1.10, 6.1.13 and 6.1.15;
+- sending an SMS-SUBMIT (MO-FORWARD-SHORT-MESSAGE) and receiving an SMS-SUBMIT-REPORT (MO-FORWARD-SHORT-MESSAGE) as described in subclauses 6.1.8 and 6.1.16;
+- sending an MSRP SEND request as described in subclauses 6.1.9.2 and 6.1.10.3;
+- receiving an MSRP SEND request as described in subclause 6.1.11;
+- receiving an SMS-STATUS-REPORT (MT-FORWARD-SHORT-MESSAGE) as described in subclause 6.1.12;
+- sending an MSRP Success or Failure REPORT as described in subclauses 6.1.11 and 6.1.12;
+- sending a SIP BYE request as described in subclauses 6.1.13, 6.1.15 and 6.1.18.2;
+- receiving a SIP BYE request as described in subclauses 6.1.14.1 and 6.1.16.1; and
+- sending a SIP SUBSCRIBE request and receiving a SIP NOTIFY request as described in subclause 6.1.17.
+
+### 6.1.2 Notification about registration status and UE capabilities
+
+Upon receipt of a third-party SIP REGISTER request, the IP-SM-GW shall:
+
+- send a SIP 200 (OK) response for the SIP REGISTER request;
+- subscribe to the registration event package for the public user identity registered at the user's registrar (S-CSCF) as described in 3GPP TS 24.229 [3]; and
+- if the MSISDN is received in the message body of the SIP REGISTER request within the <service-info> XML element, then store the MSISDN.
+
+Upon receipt of a SIP NOTIFY request the IP-SM-GW shall store the information about the UE registration status and its ability for receiving Instant Messages, i.e. if the public user identity has a contact registered with the ability to receive Instant Messages.
+
+NOTE 1: The ability of an UE to receive Instant Messages is included in the Contact header field of the SIP REGISTER request as described in OMA-TS-SIMPLE\_IM [4].
+
+NOTE 2: The IP-SM-GW will also receive information about the ability of the UE to receive Short Messages over IP as defined in 3GPP TS 24.341 [5].
+
+### 6.1.3 Handling of routing information
+
+#### 6.1.3.1 Answering routing information query
+
+The IP-SM-GW shall answer the routing information query which is received from the HSS/HLR as described in 3GPP TS 24.341 [5].
+
+#### 6.1.3.2 Querying of routing information
+
+To retrieve the routing information needed for routing the translated Short Message(s) to the servicing MSC or SGSN, the IP-SM-GW shall send the MAP-SEND-ROUTING-INFO-FOR-SM message to HSS/HLR as described in 3GPP TS 29.002 [7]. The IP-SM-GW shall include the following information in the MAP-SEND-ROUTING-INFO-FOR-SM message:
+
+- a) Invoke-ID parameter set in accordance with 3GPP TS 29.002 [7];
+- b) MSISDN parameter set to the address of the associated SIP MESSAGE request receiver retrieved as part of the subscriber data from the HSS at registration by the IP-SM-GW or locally configured in the IP-SM-GW;
+- c) SM-RP-PRI parameter set in accordance with 3GPP TS 29.002 [7];
+- d) Service Centre Address parameter set to the address of the IP-SM-GW;
+- e) SM-RP-MTI parameter set to 0 (SMS Deliver);
+- f) SM-RP-SMEA parameter set based on the value of the P-Asserted-Identity header field in the Instant Message if the P-Asserted-Identity header field contains a E.164 address; and
+- g) GPRS Support Indicator parameter set to indicate that IP-SM-GW supports GPRS specific procedure of combine delivery of Short Message via MSC and/or via the SGSN in accordance with 3GPP TS 29.002 [7].
+
+### 6.1.4 Delivering Short Message(s) as an Instant Message
+
+#### 6.1.4.1 General
+
+This section describes the procedure when the IP-SM-GW located in the terminating network interworks Short Message(s) to an Instant Message.
+
+IP-SM-GW procedures at the reception of the Short Message are described in subclause 6.1.4.2.
+
+The creation of the IM is described in subclause 6.1.4.3.
+
+The creation of the Short Message delivery report is described in subclause 6.1.4.4.
+
+#### 6.1.4.2 Receiving of SMS-DELIVER
+
+When the IP-SM-GW in the terminating networks receives a Short Message from the SMS-GMSC, it shall:
+
+- 1) determine if service level interworking is needed for the served user (in SM-RP-DA), i.e. if the served user is subscribed for service level interworking and if multiple options are available to deliver the Short Message, then user preference or operator policy indicates priority to receive a Short Messages as an Instant Message; and
+- 2) determine if service level interworking is allowed for the received Short Message. Annex A specifies the transfer protocol level criteria that disallow service level interworking.
+
+The procedure when service level interworking is not allowed is described in subclause 6.1.4.5
+
+If service level interworking for the received SM is not needed, the IP-SM-GW shall:
+
+- a) attempt to deliver the Short Message over CS/PS;
+
+- b) perform transport level interworking, as described in 3GPP TS 24.341 [5]; or
+- c) create a delivery report indicating failure.
+
+If the received Short Message is the first segment of the concatenated Short Message and the IP-SM-GW decides to use service level interworking, the IP-SM-GW shall store and acknowledge all segments except the last segment of the concatenated Short Message. When the IP-SM-GW receives the last segment of the concatenated Short Message and the full length of the received concatenated Short Message in Instant Message format is less than the allowed message length of an Instant Message, the IP-SM-GW shall create an Instant Message that includes the concatenated Short Message in accordance with subclause 6.1.4.3.1.
+
+NOTE: The allowed message length of an Instant Message is defined in IETF RFC 3428 [8].
+
+If the message length of the user generated Short Messages in IM format is greater than the allowed message length of an Instant Message and the IM user has registered the capability to receive Instant Messages, the procedure shall be in accordance with subclause 6.1.4.3.2.
+
+#### 6.1.4.3 Sending of Instant Message
+
+##### 6.1.4.3.1 Sending of the Instant Message in a SIP MESSAGE request
+
+After receiving either a single Short Message within a MT\_FORWARD\_SHORT\_MESSAGE or a full set of concatenated Short Messages not exceeding the size limit of a SIP MESSAGE request based Instant Message that is to be delivered as an Instant Message, the IP-SM-GW shall send a SIP MESSAGE request applying the related procedures for an AS acting as an originating UA as defined in subclause 5.7.3 in 3GPP TS 24.229 [3]. In addition, the IP-SM-GW shall include in the SIP MESSAGE request:
+
+- a) the Request URI set to a Tel URI or a SIP URI corresponding to the MSISDN of the recipient. The IMSI received in the SM-RP-DA in the MT\_FORWARD\_SHORT\_MESSAGE which corresponds to the MT Correlation ID previously created when the SRI message was received, is used to obtain the MSISDN;
+- b) the P-Asserted Identity header field set to a Tel URI based on TP-OA parameter received in MT\_FORWARD\_SHORT\_MESSAGE (SMS-DELIVER);
+- c) the appropriate MIME type(s) in the Content-Type header field;
+- d) an Accept-Contact header field with the IM feature-tag "+g.oma.sip-im";
+- e) a User-Agent header field to indicate the IM release version as specified in OMA-TS-SIMPLE\_IM [4];
+- f) a Request-Disposition header field with the value "no-queue", as specified in IETF RFC 3841 [13], in order to ensure the SIP MESSAGE request is not queued for delivery if the recipient is temporarily unreachable; and
+- g) the contents of the Body set to the contents of the Short Message(s) formatted in appropriate MIME type based on received content in SM.
+
+The IP-SM-GW shall send the SIP MESSAGE request to the S-CSCF.
+
+##### 6.1.4.3.2 Sending of a large Instant Message
+
+After receiving a full set of concatenated Short Messages exceeding the size limit of a SIP MESSAGE request based Instant Message, the IP-SM-GW shall send a SIP INVITE request applying the related procedures for an AS acting as an originating UA as defined in subclause 5.7.3 in 3GPP TS 24.229 [3]. In addition, the IP-SM-GW shall include in the SIP INVITE request:
+
+- a) an Accept-Contact header field with the IM feature-tags "+g.oma.sip-im" and "+g.oma.sip-im.large-message";
+- b) a User-Agent header field to indicate the IM release version as specified in OMA-TS-SIMPLE\_IM [4];
+- c) in the Contact header field, the IM feature-tag "+g.oma.sip-im";
+- d) the Request-URI set to the public user identity deduced from the information in SM-RP-DA;
+- e) the P-Asserted Identity header field set to a Tel URI based on TP-OA parameter received in MT\_FORWARD\_SHORT\_MESSAGE;
+
+- f) a Request-Disposition header field with the value "no-queue", as specified in IETF RFC 3841 [13], in order to ensure that the SIP INVITE request is not queued for delivery if the recipient is temporarily unreachable; and
+- g) in the SDP, the direction attribute set to a=sendonly as described in OMA-TS-SIMPLE\_IM [4].
+
+The IP-SM-GW shall send the SIP INVITE request to the S-CSCF.
+
+Upon receipt of a SIP 2xx response to the SIP INVITE request, the IP-SM-GW shall send MSRP SEND request(s) containing the content of the concatenated Short Messages as described in OMA-TS-SIMPLE\_IM [4].
+
+Upon receipt of corresponding response for the last chunk of the MSRP SEND request, e.g. a MSRP 200, the IP-SM-GW shall generate a SIP BYE request to release the session as in 3GPP TS 24.229 [3].
+
+#### 6.1.4.4 Sending of SMS-DELIVER-REPORT
+
+##### 6.1.4.4.1 Common Procedures
+
+If the IP-SM-GW decided to send SMS-DELIVER-REPORT, it shall send the MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC in accordance with 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2] with the following information:
+
+- Invoke Id parameter set in accordance with 3GPP TS 29.002 [7];
+- if the received SIP response is not a SIP 2xx response, then the value of the User error parameter shall be mapped from the SIP response Status Code as described in Table 6.1.4.4.1.1;
+
+NOTE 1: If the received SIP response is a SIP 2xx response then the User error parameter is not contained in the MT-FORWARD-SHORT-MESSAGE-ACK message.
+
+**Table 6.1.4.4.1.1: Mapping from Status Code to User error parameter**
+
+| <b>SIP response Status Code</b>     | <b>Value of the user error parameter</b>                                                                                                  |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| 3xx                                 | System Failure                                                                                                                            |
+| 5xx                                 | System Failure                                                                                                                            |
+| 400 Bad Request                     | System Failure                                                                                                                            |
+| 401 Unauthorized                    | Illegal Subscriber indicates that delivery of the mobile terminated Short Message failed because the mobile station failed authentication |
+| 402 Payment Required                | System Failure                                                                                                                            |
+| 403 Forbidden                       | System Failure                                                                                                                            |
+| 404 Not Found                       | Unidentified subscriber                                                                                                                   |
+| 405 Method Not Allowed              | System Failure                                                                                                                            |
+| 406 Not Acceptable                  | System Failure                                                                                                                            |
+| 407 Proxy authentication required   | Illegal Subscriber indicates that delivery of the mobile terminated Short Message failed because the mobile station failed authentication |
+| 408 Request Timeout                 | System Failure                                                                                                                            |
+| 410 Gone                            | System Failure                                                                                                                            |
+| 413 Request Entity too long         | System Failure                                                                                                                            |
+| 414 Request-URI too long            | System Failure                                                                                                                            |
+| 415 Unsupported Media type          | System Failure                                                                                                                            |
+| 416 Unsupported URI scheme          | System Failure                                                                                                                            |
+| 420 Bad Extension                   | System Failure                                                                                                                            |
+| 421 Extension required              | System Failure                                                                                                                            |
+| 423 Interval Too Brief              | System Failure                                                                                                                            |
+| 433 Anonymity Disallowed.           | System Failure                                                                                                                            |
+| 480 Temporarily Unavailable         | Absent Subscriber SM                                                                                                                      |
+| 481 Call/Transaction does not exist | System Failure                                                                                                                            |
+| 482 Loop detected                   | System Failure                                                                                                                            |
+| 483 Too many hops                   | System Failure                                                                                                                            |
+| 484 Address Incomplete              | System Failure                                                                                                                            |
+| 485 Ambiguous                       | System Failure                                                                                                                            |
+| 486 Busy Here                       | Subscriber busy for MT SMS                                                                                                                |
+| 487 Request terminated              | System Failure                                                                                                                            |
+| 488 Not acceptable here             | System Failure                                                                                                                            |
+| 493 Undecipherable                  | System Failure                                                                                                                            |
+| 600 Busy Everywhere                 | Subscriber busy for MT SMS                                                                                                                |
+| 603 Decline                         | Subscriber busy for MT SMS                                                                                                                |
+| 604 Does not exist anywhere         | Unidentified subscriber                                                                                                                   |
+| 606 Not acceptable                  | System Failure                                                                                                                            |
+
+- SM-RP-UI set to SMS-DELIVER-REPORT; and
+- the elements of the SMS-DELIVER-REPORT shall be set as described in 3GPP TS 23.040 [2] with the following information:
+  - a) TP-MTI element set to 00 (SMS-DELIVER-REPORT);
+  - b) TP-PI element set in accordance with 3GPP TS 23.040 [2];
+  - c) TP-PID element set to 00000000 (SME-to-SME protocol);
+  - d) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+  - e) TP-UDL element set in accordance with 3GPP TS 23.040 [2];
+  - f) TP-UD element set in accordance with 3GPP TS 23.040 [2]; and
+  - g) If the received SIP response is not a SIP 2xx response, then the value of the TP-FCS element shall be mapped from the SIP response Status Code as described in Table 6.1.4.4.1.2.
+
+NOTE 2: If the received SIP response is a SIP 2xx response then the TP-FCS element is not contained in the SMS-DELIVER-REPORT.
+
+**Table 6.1.4.4.1.2: Mapping from Status Code to TP-FCS element**
+
+| <b>SIP response Status Code</b>     | <b>Value of the TP-FCS element</b> |
+|-------------------------------------|------------------------------------|
+| 3xx                                 | FF Unspecified error cause         |
+| 5xx                                 | FF Unspecified error cause         |
+| 400 Bad Request                     | FF Unspecified error cause         |
+| 401 Unauthorized                    | FF Unspecified error cause         |
+| 402 Payment Required                | FF Unspecified error cause         |
+| 403 Forbidden                       | FF Unspecified error cause         |
+| 404 Not Found                       | FF Unspecified error cause         |
+| 405 Method Not Allowed              | FF Unspecified error cause         |
+| 406 Not Acceptable                  | FF Unspecified error cause         |
+| 407 Proxy authentication required   | FF Unspecified error cause         |
+| 408 Request Timeout                 | FF Unspecified error cause         |
+| 410 Gone                            | FF Unspecified error cause         |
+| 413 Request Entity too long         | FF Unspecified error cause         |
+| 414 Request-URI too long            | FF Unspecified error cause         |
+| 415 Unsupported Media type          | FF Unspecified error cause         |
+| 416 Unsupported URI scheme          | FF Unspecified error cause         |
+| 420 Bad Extension                   | FF Unspecified error cause         |
+| 421 Extension required              | FF Unspecified error cause         |
+| 423 Interval Too Brief              | FF Unspecified error cause         |
+| 433 Anonymity Disallowed.           | FF Unspecified error cause         |
+| 480 Temporarily Unavailable         | FF Unspecified error cause         |
+| 481 Call/Transaction does not exist | FF Unspecified error cause         |
+| 482 Loop detected                   | FF Unspecified error cause         |
+| 483 Too many hops                   | FF Unspecified error cause         |
+| 484 Address Incomplete              | FF Unspecified error cause         |
+| 485 Ambiguous                       | FF Unspecified error cause         |
+| 486 Busy Here                       | D2 Error in MS                     |
+| 487 Request terminated              | FF Unspecified error cause         |
+| 488 Not acceptable here             | FF Unspecified error cause         |
+| 493 Undecipherable                  | FF Unspecified error cause         |
+| 600 Busy Everywhere                 | D2 Error in MS                     |
+| 603 Decline                         | D2 Error in MS                     |
+| 604 Does not exist anywhere         | FF Unspecified error cause         |
+| 606 Not acceptable                  | FF Unspecified error cause         |
+
+##### 6.1.4.4.2 Sending of SMS-DELIVER-REPORT after Short Message(s) delivered in a SIP MESSAGE request
+
+Upon receipt of a 2xx SIP response for the SIP MESSAGE request sent as described in subclause 6.1.4.3.1, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC.
+
+Upon receipt of a non-2xx SIP response for the SIP INVITE request sent as described in subclause 6.1.4.3.1, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.4.6. If all retries fail, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC.
+
+##### 6.1.4.4.3 Sending of SMS-DELIVER-REPORT after concatenated Short Messages delivered in a large Instant Message
+
+Upon receipt of a non-2xx SIP response for the SIP INVITE request sent as described in subclause 6.1.4.3.2, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.4.6. If all retries fail, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message for the last segment of the concatenated Short Messages to the SMS-GMSC.
+
+Upon receipt of a non-200 MSRP response to the MSRP SEND request sent as described in subclause 6.1.4.3.2, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.4.6. If all retries fail, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message for the last segment of the concatenated Short Messages to the SMS-GMSC. In addition, the User error parameter shall be set to "System Failure" and in SMS-DELIVER-REPORT the TP-FCS element shall be set to "FF Unspecified error cause".
+
+Upon receipt of a 2xx SIP response for the BYE request sent as described in subclause 6.1.4.3.2, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message for the last segment of the concatenated Short Messages to the SMS-GMSC.
+
+Upon receipt of a non-2xx SIP response for the the BYE request sent as described in subclause 6.1.4.3.2, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.4.6. If all retries fail, the IP-SM-GW shall apply the procedures defined in subclause 6.1.4.4.1 to send the MT-FORWARD-SHORT-MESSAGE-ACK message for the last segment of the concatenated Short Messages to the SMS-GMSC.
+
+#### 6.1.4.5 Procedure when delivery of a Short Message as Instant Message is not allowed
+
+If any one of the criteria specified in annex A indicate that service level interworking of a Short Message is not allowed then the IP-SM-GW shall:
+
+- send an MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC in accordance with 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2] and a REPORT-SM-DELIVERY- STATUS message to the HLR/HSS as described in 3GPP TS 29.002 [7], if the service level interworking was the last option to for Short Message delivery; or
+- attempt to deliver the Short Message without applying service level interworking according to operator policy, as described in 3GPP TS 23.040 [2] and 3GPP TS 24.341 [5].
+
+#### 6.1.4.6 Retry after unsuccessful delivery of Short Message
+
+If the IP-SM-GW receives an error response when delivering a Short Message in one domain (circuit switched domain, packet switched domain or IMS domain), then based on operator policy, the IP-SM-GW shall attempt to deliver the Short Message in the next domain in its sequence of priority for retries.
+
+If all retries fail, the IP-SM-GW shall send a MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC in accordance with 3GPP TS 29.002 [7] and 3GPP TS 23.040[2] and a REPORT-SM-DELIVERY- STATUS message to the HLR/HSS as described in 3GPP TS 29.002 [7].
+
+### 6.1.5 Delivering an Instant Message as a (concatenated) Short Message in the terminating network
+
+#### 6.1.5.1 General
+
+This section describes the procedure when the IP-SM-GW located in the terminating network interworks an Instant Message to Short Message(s).
+
+IP-SM-GW procedures at the reception of the IM are described in subclause 6.1.5.2.
+
+The creation and the delivery of a Short Message or concatenated Short Messages are described in subclause 6.1.5.3.
+
+IP-SM-GW procedures at the reception of the Short Message delivery report are described in subclause 6.1.5.4.
+
+The creation of delivery notification is described in subclause 6.1.5.5.
+
+NOTE: Interworking for Large Message mode messaging as defined in OMA-TS-SIMPLE\_IM [4] is out of scope of this specification.
+
+#### 6.1.5.2 Receiving of the Instant Message in a SIP MESSAGE request
+
+Upon receipt of a SIP MESSAGE request including an Instant Message in the terminating side, the IP-SM-GW shall:
+
+- 1) check the recipient user's preferences, the current UE capability and operator policy before delivering the message. If operator policy mandates interworking or the recipient's preference is to receive an Instant Message as a Short Message over CS/PS, the IP-SM-GW shall deliver the Instant Message as a Short Message over CS/PS. If the UE of the Instant Message recipient is capable of accepting SMSIP MESSAGE as defined in 3GPP TS 24.341 [5] and operator policy mandates interworking or the recipient's preference is to receive the message as a Short Message as a Short Message over IMS, the IP-SM-GW shall deliver the Instant Message as a Short Message over IMS; and
+
+- 2) check if it is possible to interwork the IM to an SM.
+
+If the IP-SM-GW decided to interwork the IM to a Short Message (or concatenated Short Messages) the IP-SM-GW shall:
+
+- 1) if the CPIM body of the received SIP MESSAGE request includes a Disposition-Notification header field with value "positive-delivery" or "negative-delivery" (i.e. the IM sender requests the Instant Message Delivery Notification) then store the values of the MESSAGE-ID Header contained in the CPIM body; and
+- 2) proceed as described in subclause 6.1.5.3.
+
+#### 6.1.5.3 Sending of SMS-DELIVER (over CS/PS or IP)
+
+##### 6.1.5.3.1 General
+
+Upon receipt of an Instant Message that is to be delivered as a Short Message over CS/PS, the IP-SM-GW shall query the routing information from HSS as described in subclause 6.1.3.2 then send the MT\_FORWARD\_SHORT\_MESSAGE to the MSC or SGSN as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. The MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in subclauses 6.1.5.3.2 and 6.1.5.3.3.
+
+Upon receipt of an Instant Message that is to be delivered as a Short Message over IMS, the IP-SM-GW shall send the SMSIP MESSAGE containing RP-DATA message in the body to the S-CSCF as described in 3GPP TS 24.341 [5] and 3GPP TS 24.011 [9]. The SMSIP MESSAGE shall be set as described in subclauses 6.1.5.3.2 and 6.1.5.3.4.
+
+##### 6.1.5.3.2 Common Procedures
+
+Both the SM-RP-UI parameter of the MT\_FORWARD\_SHORT\_MESSAGE and the RP-User Data element of the RP-DATA message in the SMSIP MESSAGE body shall be set to SMS-DELIVER. And the elements of SMS-DELIVER message shall be set in accordance with 3GPP TS 23.040 [2], with the following information:
+
+- a) TP-MTI element set to 00 (SMS-DELIVER);
+
+- b) TP-MMS element set in accordance with 3GPP TS 23.040 [2];
+
+NOTE 1: For example, for concatenated Short Messages, TP-MMS would be set to 0 while there are more messages to send.
+
+- c) TP-RP element set to 0 (TP-Reply-Path parameter is not set in this SMS-DELIVER);
+
+- d) TP-UDHI element set in accordance with 3GPP TS 23.040 [2];
+
+- e) TP-SRI element shall be set to 1, if the SIP MESSAGE request contains in a CPIM body a Disposition-Notification header field with the value of "positive-delivery" or "negative-delivery" (i.e. the SIP MESSAGE request sender requests the Instant Message Delivery Notification). Otherwise, the TP-SRI element shall be set to 0;
+
+- f) if the SIP MESSAGE request contains the privacy header with "header" or "user" or "id" and the operator policy allows sending of anonymous SMS, the value of TP-OA element set to an anonymous value. Setting an address field to an anonymous value is described in annex B. If the SIP MESSAGE request does not contain the privacy header, the value of the TP-OA element set based on the value of the P-Asserted-Identity header field in the Instant Message if the P-Asserted-Identity header field contains a E.164 address;
+
+NOTE 2: If no E.164 address is present in the P-Asserted-Identity header field, the value of the TP-OA element will be implementation dependant.
+
+- g) TP-PID element set to 00000000 (SME-to-SME protocol);
+
+- h) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+
+- i) TP-SCTS element set to time when the IP-SM-GW received the Instant Message;
+
+- j) TP-UDL element set in accordance with 3GPP TS 23.040 [2]; and
+
+- k) TP-UD element set based on the content of Instant Message body.
+
+If the content of the body in Short Message format is greater than the allowed message length of a Short Message, then the IP-SM-GW shall send concatenated Short Messages.
+
+NOTE 3: In case of receiving MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, containing the User error parameter for one segment of the concatenated Short Message, the default action of the IP-SM-GW is not to send any remaining segment.
+
+3GPP TS 23.040 [2] specifies that a Short Message supports GSM 7-bit and UCS2 encoded text while an Instant Message may support different text types as defined in 3GPP TS 26.141 [16]. The IP-SM-GW shall reformat the received Instant Message text into an appropriate text type supported for Short Messages.
+
+##### 6.1.5.3.3 Sending of SMS-DELIVER over CS/PS
+
+The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in 3GPP TS 29.002 [7], with the following information:
+
+- Invoke-ID parameter set in accordance with 3GPP TS 29.002 [7];
+- SM-RP-DA element set to the address associated with the SIP MESSAGE request receiver;
+- SM-RP-OA element set to the address of the IP-SM-GW;
+- More Messages To Send parameter set in accordance with 3GPP TS 29.002 [7]; and
+
+NOTE: For example, for concatenated Short Messages, More Messages To Send would be set to 0 while there are more messages to send.
+
+- SM-RP-UI parameter set to SMS-DELIVER.
+
+##### 6.1.5.3.4 Sending of SMS-DELIVER over IP
+
+The IP-SM-GW shall send the SMSIP MESSAGE as described in 3GPP TS 24.341 [5] with the following exceptions:
+
+- the Request-URI mapped from the Request-URI of the associated SIP MESSAGE request; and
+- the body of the request shall contain an RP-DATA message. The elements of the RP-DATA message shall be set as described in 3GPP TS 24.011 [9], with the following information:
+  - a) RP-Message Type element set to 001 (network to MS);
+  - b) RP-Message Reference element set in accordance with 3GPP TS 24.011 [9];
+  - c) RP-Originator Address element set to the address of the IP-SM-GW; and
+  - d) RP-User Data set to SMS-DELIVER.
+
+#### 6.1.5.4 Receiving of SMS-DELIVER-REPORT (over CS/PS or IP)
+
+##### 6.1.5.4.1 Receiving of SMS-DELIVER-REPORT over CS/PS
+
+Upon receipt of MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated SIP MESSAGE request received before was delivered as a single Short Message, the IP-SM-GW shall
+
+- send a SIP 200 (OK) response to the associated SIP MESSAGE request sender, if the MT\_FORWARD\_SHORT\_MESSAGE\_ACK message does not contain the User error parameter. If the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "positive-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "delivered" indication to the associated SIP MESSAGE request sender; or
+- attempt deliver the Short Message in the next domains as specified in subclause 6.1.5.6, if the MT\_FORWARD\_SHORT\_MESSAGE\_ACK message contains the User error parameter. If all retry fail, the IP-SM-GW shall send a SIP 4xx or SIP 5xx response. The Status code to be sent is determined by examining the value of the User error parameter. Table 6.1.5.4.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to SIP response status codes.
+
+Upon receipt of MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated SIP MESSAGE request received before was delivered as concatenated Short Messages, the IP-SM-GW shall wait for the last MT\_FORWARD\_SHORT\_MESSAGE\_ACK message. Then the IP-SM-GW shall:
+
+- send a SIP 200 (OK) response to the associated SIP MESSAGE request sender, if none of the MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "positive-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "delivered" indication to the associated SIP MESSAGE request sender; or
+- attempt deliver the Short Message in the next domains as specified in subclause 6.1.5.6, if at least one of MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If all retries fail, the IP-SM-GW shall send a SIP 4xx or SIP 5xx response to the associated SIP MESSAGE request sender. The Status code to be sent is determined by examining the value of the User error parameter. Table 6.1.5.4.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to SIP response status codes.
+
+**Table 6.1.5.4.1.1: Mapping from User error parameter to Status code**
+
+| <b>Value of the User error parameter</b>                                                                                                                                 | <b>SIP response Status code</b> |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Unidentified subscriber                                                                                                                                                  | 404 Not Found                   |
+| Absent Subscriber SM                                                                                                                                                     | 480 Temporarily unavailable     |
+| Subscriber busy for MT SMS                                                                                                                                               | 486 Busy Here                   |
+| Facility Not Supported                                                                                                                                                   | 500 Server Internal error       |
+| Illegal Subscriber indicates that delivery of the mobile terminated Short Message failed because the mobile station failed authentication                                | 500 Server Internal error       |
+| Illegal equipment indicates that delivery of the mobile terminated Short Message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed; | 500 Server Internal error       |
+| System Failure                                                                                                                                                           | 500 Server Internal error       |
+| SM Delivery Failure with cause "memory capacity exceeded in the mobile equipment"                                                                                        | 480 Temporarily unavailable     |
+| SM Delivery Failure with cause "protocol error"                                                                                                                          | 500 Server Internal error       |
+| SM Delivery Failure with cause "mobile equipment does not support the mobile terminated Short Message service"                                                           | 500 Server Internal error       |
+| Unexpected Data Value                                                                                                                                                    | 500 Server Internal error       |
+| Data Missing                                                                                                                                                             | 500 Server Internal error       |
+
+##### 6.1.5.4.2 Receiving of SMS-DELIVER-REPORT over IP
+
+Upon receipt of an SMSIP MESSAGE with RP-ACK or RP-ERROR message in the body, the IP-SM-GW shall respond with a SIP 202 (Accepted) response in accordance with 3GPP TS 24.341 [5].
+
+If the SMSIP MESSAGE contains RP-ACK message in the body, and the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "positive-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "delivered" indication to the associated SIP MESSAGE request sender. If the associated SIP MESSAGE request received before was delivered as concatenated Short Messages and all the SMSIP MESSAGE contains RP-ACK message in the body for the concatenated Short Messages, the IP-SM-GW shall send the Instant Message Delivery Notification with a "delivered" indication to the associated SIP MESSAGE request sender.
+
+If the SMSIP MESSAGE contains RP-ERROR message in the body, the IP-SM-GW shall attempt deliver the Short Message in the next domains as specified in subclause 6.1.5.6. If all retries fail and the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "negative-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "failed" indication to the associated SIP
+
+MESSAGE request sender. If the associated SIP MESSAGE request received before was delivered as concatenated Short Messages and at least one of the SMSIP MESSAGES contains RP-ERROR message in the body for the concatenated Short Messages, the IP-SM-GW shall send the Instant Message Delivery Notification with a "failed" indication to the associated SIP MESSAGE request sender.
+
+#### 6.1.5.5 Sending of IMDN
+
+##### 6.1.5.5.1 Sending of IMDN after a (concatenated) Short Message delivery over CS/PS
+
+If the IP-SM-GW decided to send an Instant Message Delivery Notification, it shall act as an originating UA as defined in subclause 5.7.3 in 3GPP TS 24.229 [3] to send a SIP MESSAGE request with the following exceptions:
+
+- a) the Request-URI shall contain a public user identity of the stored sender identity of the associated SIP MESSAGE request;
+- b) a User-Agent header field shall indicate the IM release version as specified in OMA-TS-SIMPLE\_IM [4];
+- c) the P-Asserted-Identity header field shall be mapped from the stored Request-URI of the associated SIP MESSAGE request;
+- d) an Accept-Contact header field shall contain the IM feature-tag "+g.oma.sip-im";
+- e) the Content-Type header field shall contain "message/imdn+xml"; and
+- f) the body of the request shall contain a CPIM message as defined in OMA-TS-SIMPLE\_IM [4], including the following information:
+  - the <message-id> XML element of the IMDN payload shall be set to the value of the stored Message-ID Header in the CPIM body of the associated SIP MESSAGE request; and
+  - the <disposition> XML element of the IMDN payload shall be set to <delivery/>.
+
+##### 6.1.5.5.2 Sending of IMDN after a (concatenated) Short Message delivery over IP
+
+If the IP-SM-GW decided to send an Instant Message Delivery Notification, it shall act as a Routeing B2BUA Application Server (AS) as defined in subclause 5.7.5 in 3GPP TS 24.229 [3] to send a SIP MESSAGE request with the following exceptions:
+
+- a) the Request-URI shall contain a public user identity of the stored sender identity of the associated SIP MESSAGE request;
+- b) the P-Asserted-Identity header field shall be set to the value of the stored Request-URI of the associated SIP MESSAGE request;
+- c) the Accept-Contact header field shall contain the IM feature tag "+g.oma.sip-im";
+- d) the User-Agent header field shall indicate the IM release version as specified in OMA-TS-SIMPLE\_IM [4];
+- e) the Content-Type header field shall contain "message/imdn+xml"; and
+- f) the body of the request shall contain a CPIM message as defined in OMA-TS-SIMPLE\_IM [4], including the following information:
+  - the <message-id> XML element of the IMDN payload which shall be set to the value of the stored Message-ID Header in the CPIM body of the associated SIP MESSAGE request; and
+  - the <disposition> XML element of the IMDN payload which shall be set to <delivery/>.
+
+#### 6.1.5.6 Retry after unsuccessful delivery of Short Message
+
+If the IP-SM-GW receives an error response when delivering a Short Message in one domain (circuit switched domain, packet switched domain or IMS domain), then based on operator policy, the IP-SM-GW shall attempt to deliver the Short Message in the next domain in its sequence of priority for retries.
+
+If all retries fail, the IP-SM-GW shall send a REPORT-SM-DELIVERY-STATUS message to the HLR/HSS as described in 3GPP TS 29.002 [7].
+
+#### 6.1.5.7 Error handling when interworking from Instant Message to Short Message is not possible
+
+When interworking is needed but is not possible, the IP-SM-GW shall send one of the following error responses to the sender of the Instant Message:
+
+- If the error is because none of the content in the SIP MESSAGE request is interworkable to a Short Message, then the IP-SM-GW shall send a SIP 415 (Unsupported Media Type) response and shall include an Accept header field listing the types of text media supported by SM as described in 3GPP TS 26.141 [16]. For service level interworking of Instant Message to Short Message, only text shall be supported.
+- Otherwise a SIP 488 (Not Acceptable Here) response shall be returned.
+
+#### 6.1.5.8 Partial interworking from Instant Message to Short Message
+
+If an Instant Message contains other media than text content, the IP-SM-GW may remove the unsupported content.
+
+Based on Operator policy the IP-SM-GW may insert text warning the receiver that non-text content has been removed from the message.
+
+### 6.1.6 Submitting an Instant Message as a (concatenated) Short Message in the originating network
+
+#### 6.1.6.1 General
+
+This section describes the procedure when the IP-SM-GW located in the originating network interworks an Instant Message to a Short Message.
+
+IP-SM-GW procedures at the reception of the IM are described in subclause 6.1.6.2.
+
+The creation of a (concatenated) Short Message is described in subclause 6.1.6.3.
+
+IP-SM-GW procedures at the reception of the Short Message submit report are described in subclause 6.1.6.4.
+
+IP-SM-GW procedures at the reception of the Short Message status report are described in subclause 6.1.6.5.
+
+The creation of delivery notification is described in subclause 6.1.6.6.
+
+NOTE: Interworking for Large Message mode messaging as defined in OMA-TS-SIMPLE\_IM [4] is out of scope of this specification.
+
+#### 6.1.6.2 Receiving of the Instant Message in a SIP MESSAGE request
+
+Upon receipt of a SIP MESSAGE request including an Instant Message, the IP-SM-GW shall attempt service level interworking if operator policy mandates interworking or the IP-SM-GW cannot find a SIP address for the recipient.
+
+If IP-SM-GW determined that service level interworking needed, then the IP-SM-GW shall:
+
+- 1) check if the message originator is authorized for service level interworking; and
+
+NOTE: It can be assumed that all subscribers are authorized for service level interworking if interworking is mandated by operator policy.
+
+- 2) check if the service level interworking is possible.
+
+If IP-SM-GW decided to submit the Instant Message as a Short Message, then the IP-SM-GW shall:
+
+- 1) respond with a SIP 202 (Accepted) response in accordance with 3GPP TS 24.229 [3];
+- 2) store the values of the Request-URI, the P-Asserted-Identity header field and the MESSAGE-ID Header contained in the CPIM body, if the received SIP MESSAGE request includes a CPIM body and a Disposition-Notification header field with value "positive-delivery" or "negative-delivery" (i.e. the SIP MESSAGE request sender requests the Instant Message Delivery Notification); and
+- 3) proceed as described in subclause 6.1.6.3.
+
+#### 6.1.6.3 Sending of SMS-SUBMIT over CS/PS
+
+To submit a Short Message to the SC, the IP-SM-GW shall send MO\_FORWARD\_SHORT\_MESSAGE as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. In addition, for the information elements listed below, the following interworking procedures shall apply:
+
+- Invoke-ID parameter set in accordance with 3GPP TS 29.002 [7];
+- SM-RP-DA parameter set to the address of user's home network Service Centre configured in the IP-SM-GW, or retrieved as part of the subscriber data from the HSS at registration by the IP-SM-GW;
+- if the SIP MESSAGE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows sending of anonymous Short Message, the value of SM-RP-OA parameter shall be set to an anonymous value. Setting an address field to an anonymous value is described in annex B. If the SIP MESSAGE request does not contain the Privacy header field, the value of the SM-RP-OA parameter shall be set based on the value of the P-Asserted-Identity header field or the address retrieved as part of the subscriber data from the HSS at registration by the IP-SM-GW;
+- SM-RP-UI parameter set to SMS-SUBMIT; and
+- the elements of the SMS-SUBMIT message shall be set as described in 3GPP TS 23.040 [2] subclause 9.2.2, with the following information:
+  - a) TP-MTI element set to 01 (SMS-SUBMIT);
+  - b) TP-RD element set to 1 (Instruct the SC to reject an SMS SUBMIT for an SM still held in the SC which has the same TP MR and the same TP DA as the previously submitted SM from the same OA.);
+  - c) if the SIP MESSAGE request contains an Expires header field with a non-zero value, the value of TP VPF element shall be set according to the TP VP element. Otherwise, the value of TP VPF element shall be set to 00 (TP VP field not present);
+  - d) TP VP element set based on the Expires header field value and the optional Date header field value;
+  - e) TP-UDHI element set in accordance with 3GPP TS 23.040 [2];
+  - f) if the SIP MESSAGE request contains in a CPIM body a Disposition-Notification header field with the value of "positive-delivery" or "negative-delivery" (i.e. the SIP MESSAGE request sender requests the Instant Message Delivery Notification), the value of TP SRR element shall be set to 1 (A status report is requested), Otherwise, the value of TP-SRR element shall be set to 0 (A status report is not requested);
+  - g) TP-MR element set in accordance with 3GPP TS 23.040 [2];
+  - h) TP-RP element set to 0 (TP Reply Path parameter is not set in this SMS SUBMIT);
+  - i) TP-DA element set based on the value of the Request-URI in the Instant Message as long as the Request-URI contains a E.164 address;
+  - j) TP-PI element set to 00000000 (SME-to-SME protocol);
+  - k) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+  - l) TP-UDL element set in accordance with 3GPP TS 23.040 [2]; and
+  - m) TP-UD element set based on the content of Instant Message body.
+
+If the content of the body in Short Message format is greater than the allowed message length of a Short Message, then the IP-SM-GW shall send concatenated Short Messages.
+
+NOTE: In case of receiving MO\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing the User error parameter for one segment of the concatenated Short Message, the default action of the IP-SM-GW is not to send any remaining segment.
+
+3GPP TS 23.040 [2] specifies that a Short Message supports GSM 7-bit and UCS2 encoded text while an Instant Message may support different text types as defined in 3GPP TS 26.141 [16]. The IP-SM-GW shall reformat the received Instant Message text into an appropriate text type supported for Short Messages.
+
+#### 6.1.6.4 Receiving of SMS-SUBMIT-REPORT
+
+Upon receipt of MO\_FORWARD\_SHORT\_MESSAGE\_ACK with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, not containing the User error parameter, and if the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "positive-delivery" or "negative-delivery" (i.e. the SIP MESSAGE request sender requests the Instant Message Delivery Notification), the IP-SM-GW shall store the value of TP Service Centre Time Stamp element.
+
+Upon receipt of MO\_FORWARD\_SHORT\_MESSAGE\_ACK with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing the User error parameter, and if the associated SIP MESSAGE request received before contains in a CPIM body a Disposition-Notification header field with value "negative-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "failed" indication to the associated SIP MESSAGE request sender. If the associated SIP MESSAGE request received before was delivered as concatenated Short Messages as described in subclause 6.1.6.3, and one of the MO\_FORWARD\_SHORT\_MESSAGE\_ACK for the concatenated Short Messages contains the User error parameter, the IP-SM-GW shall send the Instant Message Delivery Notification with a "failed" indication to the associated SIP MESSAGE request sender.
+
+#### 6.1.6.5 Receiving of SMS-STATUS-REPORT
+
+Upon receipt of a MT\_FORWARD\_SHORT\_MESSAGE with the SM-RP-UI parameter set to value of SMS-STATUS-REPORT, the IP-SM-GW shall:
+
+- retrieve the TP-Service-Centre-Time-Stamp and TP-Recipient-Address, then find the associated SIP MESSAGE request instance containing the stored TP-Service-Center-Time-Stamp and SM-RP-Originating Address element with the same value; and
+- if the SMS-STATUS-REPORT matchs one associated SIP MESSAGE request, send an Instant Message Delivery Notification or discard the SMS-STATUS-REPORT as described in Table 6.1.6.5.1; or
+- wait for the last SMS-STATUS-REPORT, if the associated SIP MESSAGE request was delivered as concatenated Short Messages as described in subclause 6.1.6.3. If all SMS-STATUS-REPORTs for concatenated Short Messages contains the TP-Status element set to "00000000" and the associated SIP MESSAGE request contains in a CPIM body a Disposition-Notification header field with value "positive-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "delivered" indication to the associated SIP MESSAGE request sender. If at least one of SMS-STATUS-REPORT for concatenated Short Messages contains the TP-Status element set between "00000001" and "00011111" or between "01000000" and "11111111", and the associated SIP MESSAGE request contains in a CPIM body a Disposition-Notification header field with value "negative-delivery", the IP-SM-GW shall send the Instant Message Delivery Notification with a "failed" indication to the associated SIP MESSAGE request sender.
+
+**Table 6.1.6.5.1: Process of the received SMS-STATUS-REPORT**
+
+| <b>The value of TP-Status element of SMS-STATUS-REPORT</b> | <b>The parameter of the Disposition-Notification header field in the CPIM body of the associated SIP MESSAGE request</b> | <b>Process of the IP-SM-GW</b>                                                                |
+|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|
+| "00000000"                                                 | Include "positive-delivery"                                                                                              | Shall send Instant Message Delivery Notification to the associated SIP MESSAGE request sender |
+| "00000001" to "00011111" or<br>"01000000" to "11111111"    | Include "negative-delivery"                                                                                              | Shall send Instant Message Delivery Notification to the associated SIP MESSAGE request sender |
+| "00100000" to "00111111"                                   | Include "positive-delivery" or "negative-delivery"                                                                       | May discard the SMS-STATUS-REPORT                                                             |
+| "00000000"                                                 | Not include "positive-delivery"                                                                                          | May discard the SMS-STATUS-REPORT                                                             |
+| "00000001" to "00011111" or<br>"01000000" to "11111111"    | Not include "negative-delivery"                                                                                          | May discard the SMS-STATUS-REPORT                                                             |
+
+#### 6.1.6.6 Sending of IMDN (both for SUBMIT-REPORT and STATUS-REPORT)
+
+If the IP-SM-GW decided to send an Instant Message Delivery Notification, it shall act as an originating UA as defined in subclause 5.7.3 in 3GPP TS 24.229 [3] to send a SIP MESSAGE request with the following exceptions:
+
+- a) the Request-URI shall contain a public user identity of the stored sender identity of the associated SIP MESSAGE request;
+- b) the P-Asserted-Identity header field shall be set to the value of the stored Request-URI of the associated SIP MESSAGE request;
+- c) the Accept-Contact header field shall be set with the IM feature tag "+g.oma.sip-im";
+- d) the User-Agent header field which shall be set with the IM release version as specified in OMA-TS-SIMPLE\_IM [4];
+- e) the Content-Type header field shall contain "message/imdn+xml"; and
+- f) the body of the request shall contain a CPIM message as defined in OMA-TS-SIMPLE\_IM [4], including the following information:
+  - the <message-id> XML element of the IMDN payload shall be set to the value of the stored Message-ID Header in the CPIM body of the associated SIP MESSAGE request; and
+  - the <disposition> XML element of the IMDN payload shall be set to <delivery/>.
+
+#### 6.1.6.7 Error handling when interworking from Instant Message to Short Message is not possible
+
+When interworking is needed but is not possible, the IP-SM-GW shall send one of the following error responses to the sender of the Instant Message:
+
+- If the error is because none of the content in the SIP MESSAGE request is interworkable to a Short Message, then the IP-SM-GW shall send a SIP 415 (Unsupported Media Type) response and shall also include an Accept header field listing the types of text media supported by SM as described in 3GPP TS 26.141 [16]. For service level interworking of Instant Message to Short Message, only text shall be supported.
+- Otherwise a SIP 488 (Not Acceptable Here) response shall be returned.
+
+#### **6.1.6.8 Partial interworking from Instant Message to Short Message**
+
+If an Instant Message contains other media than text content, the IP-SM-GW may remove the unsupported content.
+
+Based on Operator policy the IP-SM-GW may insert text warning the receiver that non-text content has been removed from the message.
+
+### 6.1.7 Receiving of the Chat Session invitation request in the terminating network
+
+#### **6.1.7.1 Receiving of the Chat Session SIP INVITE request**
+
+Upon receipt of a SIP INVITE request addressed to an SMS user, the IP-SM-GW shall assign an MSISDN to be used by the SMS user for the duration of this Chat session to reach the sender of the SIP INVITE request.
+
+If the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this, the originator's identity shall not be revealed to the SMS user for this Chat Session.
+
+If operator policy mandates the SMS user to be informed of the Chat Session invitation, the IP-SM-GW shall proceed with the procedures in subclauses 6.1.7.2, 6.1.7.3 and 6.1.7.4. Otherwise the IP-SM-GW shall proceed with the procedures in subclause 6.1.7.5.
+
+#### **6.1.7.2 Sending of the SMS-DELIVER (over CS/PS or IP)**
+
+Upon receipt of a SIP INVITE request that is to be delivered as a Short Message, the IP-SM-GW:
+
+- 1) may attempt to deliver Chat Session invitation request as SMS over IP, if operator policy sets SMS over IP as highest priority for delivery attempts. If this attempt succeeds, then the IP-SM-GW shall skip subsequent steps;
+- 2) shall query the routing information from HSS as described in subclause 6.1.3.2; and
+
+- 3) if routing information is available (SGSN and/or MSC address), the IP-SM-GW shall attempt the delivery of a Short Message over IP, over CS, and PS. The priority order of these attempts is an operator policy.
+
+For the delivery of a Chat Session invitation request as a Short Message over CS/PS, the IP-SM-GW shall send a MT\_FORWARD\_SHORT\_MESSAGE to the MSC or SGSN as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.2.
+
+For the delivery of a Chat Session invitation request as a Short Message over IP, the IP-SM-GW shall send an SMSIP MESSAGE containing RP-DATA message in the body to the S-CSCF as described in 3GPP TS 24.341 [5] and 3GPP TS 24.011 [9]. In addition parameters of the SMSIP MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.7.2.4.
+
+For every attempt the TP-UD element shall contain operator defined data that should convey information to the SMS user that he is invited to send and receive messages in the context of a Chat Session, and include for example, instructions on how to accept, reject and leave the session. Since the TP-OA element is set to an MSISDN assigned by the IP-SM-GW the MSISDN of the original sender shall be included in the information sent to the SMS user unless the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this. For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP INVITE request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+#### 6.1.7.3 Receiving of SMS-DELIVER-REPORT (over CS/PS or IP)
+
+##### 6.1.7.3.1 Receiving of SMS-DELIVER-REPORT over CS/PS
+
+Upon receipt of an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated SIP INVITE request received before was delivered as a single Short Message, the IP-SM-GW shall:
+
+- proceed with the procedures in subclause 6.1.7.4; or
+- attempt deliver the Short Message in the next domains as specified in subclause 6.1.7.2, if the MT\_FORWARD\_SHORT\_MESSAGE\_ACK message contains the User error parameter. If all retries fail, the IP-SM-GW shall send a SIP 4xx or SIP 5xx response to the associated SIP INVITE request. The SIP response to be sent is determined by examining the value of the User error parameter. Table 6.1.5.4.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to SIP response Status-Codes. If the IP-SM-GW associated a specific MSISDN for the Chat Session, then the IP-SM-GW shall release that MSISDN.
+
+Upon receipt of an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated SIP INVITE request received before was delivered as concatenated Short Messages, the IP-SM-GW shall wait for the last MT\_FORWARD\_SHORT\_MESSAGE\_ACK message. Then the IP-SM-GW shall:
+
+- proceed with the procedures in subclause 6.1.7.4, if none of the MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter; or
+- attempt to deliver the Short Message in the next domains as specified in subclause 6.1.7.2, if at least one of the MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If all retries fail, the IP-SM-GW shall send a SIP 4xx or SIP 5xx response to the associated SIP INVITE request. The SIP response to be sent is determined by examining the value of the User error parameter. Table 6.1.5.4.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to SIP response Status-Codes. If the IP-SM-GW associated a specific MSISDN for the Chat Session, then the IP-SM-GW shall release that MSISDN.
+
+##### 6.1.7.3.2 Receiving of SMS-DELIVER-REPORT over IP
+
+Upon receipt of an SMSIP MESSAGE with RP-ACK or RP-ERROR message in the body, the IP-SM-GW shall respond with a SIP 202 (Accepted) response in accordance with 3GPP TS 24.341 [5].
+
+If the SMSIP MESSAGE contains an RP-ERROR message in the body, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.7.2. If all retries fail, the IP-SM-GW shall send a SIP 480 (Temporarily Unavailable) response to the associated SIP INVITE request received before and release the specific MSISDN assigned for this Chat Session.
+
+If the associated SIP INVITE request received before was delivered as concatenated Short Messages and at least one of the SMSIP MESSAGES contains an RP-ERROR message in the body for the concatenated Short Messages, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.7.2, if at least one of the MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If all retries fail, the IP-SM-GW shall send a SIP 480 (Temporarily Unavailable) response to the associated SIP INVITE request and release the specific MSISDN assigned for this Chat Session.
+
+#### 6.1.7.4 Receiving of the SMS-DELIVER as a response to the Chat Session SIP INVITE request
+
+After receiving a Short Message within an MT\_FORWARD\_SHORT\_MESSAGE associated to the Chat Session where the Short Message contains the operator defined answer to the Chat Session invitation and
+
+- if the answer indicates that the user accepts the Chat Session invitation, the IP-SM-GW shall send a SIP 200 (OK) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3]. Otherwise
+- the IP-SM-GW shall send a SIP 603 (Decline) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3]. If the IP-SM-GW associated a specific MSISDN for the Chat Session, then the IP-SM-GW shall release that MSISDN.
+
+#### 6.1.7.5 Sending of the Chat Session SIP 200 (OK) response as a result of the response from the SMS user
+
+The IP-SM-GW shall send a SIP 200 (OK) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3].
+
+### 6.1.8 Receiving of the Chat Session invitation request in the originating network
+
+#### 6.1.8.1 Receiving of the Chat Session SIP INVITE request
+
+Upon receipt of a SIP INVITE request addressed to an SMS user, the IP-SM-GW shall assign an MSISDN to be used by the SMS user for the duration of this Chat session to reach the sender of the SIP INVITE request. Either a specific MSISDN shall be selected for this Chat Session or the MSISDN reflecting the identity of the originator shall be used. A specific MSISDN shall always be selected for group Chat Sessions, but whether or not a specific MSISDN shall be selected for one-to-one Chat Sessions depends on operator policy.
+
+If the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this, a specific MSISDN shall be assigned, and the originator's identity shall not be revealed to the SMS user for this Chat Session.
+
+If operator policy mandates the SMS user to be informed of the Chat Session invitation, the IP-SM-GW shall proceed with the procedures in subclauses 6.1.8.2, 6.1.8.3 and 6.1.8.4. Otherwise the IP-SM-GW shall proceed with the procedures in subclause 6.1.8.5.
+
+#### 6.1.8.2 Sending of the SMS-SUBMIT
+
+The IP-SM-GW shall submit a Short Message to the SC as described in subclause 6.1.18.4 with the following addition:
+
+- TP-UD element shall contain operator defined data that should convey information to the SMS user that he is invited to send and receive messages in the context of a Chat Session, and include for example, instructions on how to accept, reject and leave the session. When the TP-OA element is set to an MSISDN assigned by the IP-SM-GW the MSISDN of the original sender shall be included in the information sent to the SMS user unless the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this. For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP INVITE request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+#### 6.1.8.3 Receiving of SMS-SUBMIT-REPORT
+
+Upon receipt of an MO\_FORWARD\_SHORT\_MESSAGE\_ACK with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing the User error parameter, the IP-SM-GW shall send a SIP 480 (Temporarily
+
+Unavailable) response to the associated SIP INVITE request and release the specific MSISDN assigned for this Chat Session if one had been assigned.
+
+If the associated SIP INVITE request was delivered as concatenated Short Messages as described in subclause 6.1.8.2, and one of the MO\_FORWARD\_SHORT\_MESSAGE\_ACKs for the concatenated Short Messages contains the User error parameter, the IP-SM-GW shall send a SIP 480 (Temporarily Unavailable) response to the associated SIP INVITE request and release the specific MSISDN assigned for this Chat Session if one had been assigned.
+
+#### 6.1.8.4 Receiving of the SMS-DELIVER as a response to the Chat Session invitation
+
+After receiving a Short Message within an MT\_FORWARD\_SHORT\_MESSAGE associated to the Chat Session where the Short Message contains the operator defined answer to the Chat Session invitation, then the IP-SM-GW shall acknowledge the Short Message as described in subclause 6.1.18.5 and
+
+- if the answer indicates that the user accepts the Chat Session invitation, the IP-SM-GW shall send a SIP 200 (OK) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3]. Otherwise
+- the IP-SM-GW shall send a SIP 603 (Decline) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3].
+
+#### 6.1.8.5 Sending automatic Chat Session SIP 200 (OK) response
+
+The IP-SM-GW shall send a SIP 200 (OK) response to the associated SIP INVITE request according to 3GPP TS 24.229 [3].
+
+### 6.1.9 Delivering a Short Message as an MSRP SEND in an ongoing Chat Session anchored in the terminating network
+
+#### 6.1.9.1 Receiving of SMS-DELIVER when recipient is an MSISDN assigned by the IP-SM-GW on the terminating side
+
+When the IP-SM-GW receives a Short Message from the SMS-GMSC where the recipient address in SM-RP-DA was associated with a Chat Session, it shall:
+
+- 1) determine if the Chat Session associated with the recipient address in SM-RP-DA is still active; and
+- 2) determine if service level interworking is allowed for the received Short Message. Annex A specifies the transfer protocol level criteria that disallows service level interworking.
+
+If the Chat Session associated with the recipient address in SM-RP-DA is not available anymore, the IP-SM-GW shall create an SMS-Deliver-Report indicating that messages to this recipient cannot be delivered. The procedures described in subclause 6.1.13 ensure that the SMS user is informed that this Chat Session is not available anymore.
+
+The procedure when service level interworking is not allowed is described in subclause 6.1.4.5.
+
+If the received Short Message is a segment of a concatenated Short Message, the IP-SM-GW shall store and acknowledge all segments except the last segment of the concatenated Short Message.
+
+After receiving either a single Short Message within one MT\_FORWARD\_SHORT\_MESSAGE or a full set of concatenated Short Messages that is to be delivered as a Chat Session message, the IP-SM-GW shall proceed with the procedures in subclause 6.1.9.2.
+
+#### 6.1.9.2 Sending of MSRP SEND request
+
+After receiving either a single Short Message within one MT\_FORWARD\_SHORT\_MESSAGE or a full set of concatenated Short Messages that is to be delivered as a Chat Session message, the IP-SM-GW shall send an MSRP SEND request according to the procedures defined in IETF RFC 4975 [19]. In addition, the IP-SM-GW shall include in the MSRP SEND request:
+
+- a) the To-path set to the MSRP address received in the SDP offer described in subclause 6.1.7;
+- b) the From-path set to the MSRP address from the SDP answer described in subclause 6.1.7;
+- c) the Message-ID generated according to the rules in IETF RFC 4975 [19];
+
+- d) the Content-Type set to "message/cpim";
+- f) Success-Report set to "no" and Failure-Report set to "yes"; and
+- g) the body set to the contents of the Short Message(s) formatted in the appropriate MIME type based on received content in the Short Message.
+
+#### 6.1.9.3 Sending of SMS-DELIVER-REPORT
+
+When the final delivery outcome of the MSRP SEND request is known from either a negative or a positive MSRP response, the IP-SM-GW shall create an SMS-Deliver-Report and the IP-SM-GW shall send the MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC in accordance with 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2] with the following information:
+
+- Invoke Id parameter set in accordance with 3GPP TS 29.002 [7];
+- If the received MSRP response code is not a MSRP 2xx response, then the value of the User error parameter shall be mapped from the MSRP Response Code as described in Table 6.1.9.3.1;
+
+NOTE 1: If the received MSRP response code is a MSRP 2xx response then the User error parameter is not contained in the MT-FORWARD-SHORT-MESSAGE-ACK message.
+
+**Table 6.1.9.3.1: Mapping from MSRP response code to User error parameter**
+
+| <b>MSRP response code</b>                 | <b>Value of the user error parameter</b> |
+|-------------------------------------------|------------------------------------------|
+| 400 - Request Unintelligible              | System Failure                           |
+| 403 - Action not allowed                  | System Failure                           |
+| 408 - Request Timeout                     | System Failure                           |
+| 413 - MSRP Undesired Message              | System Failure                           |
+| 415 - Unsupported Media type              | System Failure                           |
+| 423 - MSRP parameter out of bounds        | System Failure                           |
+| 481 - MSRP session does not exist         | System Failure                           |
+| 501 - Request Method not understood       | System Failure                           |
+| 506 - Session bound to another connection | System Failure                           |
+
+- SM-RP-UI set to SMS-DELIVER-REPORT; and
+- the elements of the SMS-DELIVER-REPORT shall be set as described in 3GPP TS 23.040 [2] with the following information:
+  - a) TP-MTI element set to 00 (SMS-DELIVER-REPORT);
+  - b) TP-PI element set in accordance with 3GPP TS 23.040 [2];
+  - c) TP-PID element set to 00000000 (SME-to-SME protocol);
+  - d) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+  - e) TP-UDL element set in accordance with 3GPP TS 23.040 [2];
+  - f) TP-UD element set in accordance with 3GPP TS 23.040 [2]; and
+  - g) If the received MSRP response code is not a MSRP 2xx response, then the value of the TP-FCS element shall be mapped from the MSRP response code as described in Table 6.1.9.3.2.
+
+NOTE 2: If the received MSRP response code is a MSRP 2xx response then the TP-FCS element is not contained in the SMS-DELIVER-REPORT.
+
+**Table 6.1.9.3.2: Mapping from MSRP response code to TP-FCS element**
+
+| <b>MSRP response code</b>                 | <b>Value of the TP-FCS element</b> |
+|-------------------------------------------|------------------------------------|
+| 400 - Request Unintelligable              | FF Unspecified error cause         |
+| 403 - Action not allowed                  | FF Unspecified error cause         |
+| 408 - Request Timeout                     | FF Unspecified error cause         |
+| 413 - MSRP Undesired Message              | FF Unspecified error cause         |
+| 415 - Unsupported Media type              | FF Unspecified error cause         |
+| 423 - MSRP parameter out of bounds        | FF Unspecified error cause         |
+| 481 - MSRP session does not exist         | FF Unspecified error cause         |
+| 501 - Request Method not understood       | FF Unspecified error cause         |
+| 506 - Session bound to another connection | FF Unspecified error cause         |
+
+### 6.1.10 Delivering a Short Message as an MSRP SEND request in an ongoing Chat Session anchored in the originating network
+
+#### 6.1.10.1 Receiving of SMS-DELIVER when recipient address is actual MSISDN of recipient
+
+For one-to-one Chat Sessions anchored in the originating network, the procedures described in subclause 6.1.8 have the option to inform the SMS user that this user should use the actual MSISDN of the CPM user to send messages to this Chat Session. The IP-SM-GW shall be able to recognize that such an MSISDN is associated with a Chat Session.
+
+The procedure for receiving a Short Message from an SMS-GMSC are otherwise identical for Chat Sessions anchored in the originating network and for Chat Sessions anchored in the terminating network; the IP-SM-GW shall follow the procedure described in subclause 6.1.9.1.
+
+#### 6.1.10.2 Receiving of SMS-DELIVER when recipient is an MSISDN assigned by the IP-SM-GW on the originating side
+
+The procedure for receiving a Short Message from an SMS-GMSC are identical for Chat Sessions anchored in the originating network and for Chat Sessions anchored in the terminating network; the IP-SM-GW shall follow the procedure described in subclause 6.1.9.1.
+
+#### 6.1.10.3 Sending of MSRP SEND request
+
+The procedure for sending of MSRP SEND requests are identical for Chat Sessions anchored in the originating network and for Chat Sessions anchored in the terminating network; the IP-SM-GW shall follow the procedure described in subclause 6.1.9.2.
+
+#### 6.1.10.4 Sending of SMS-DELIVER-REPORT
+
+The procedure for sending of SMS-DELIVER-REPORT are identical for Chat Sessions anchored in the originating network and for Chat Sessions anchored in the terminating network; the IP-SM-GW shall follow the procedure described in subclause 6.1.9.3.
+
+### 6.1.11 Delivering an MSRP SEND request in an ongoing Chat Session anchored in the terminating network as a (concatenated) Short Message
+
+#### 6.1.11.1 Receiving of the MSRP SEND request
+
+This subclause describes the procedure when the IP-SM-GW located in the terminating network receives an MSRP SEND request as part of an ongoing Chat Session.
+
+Upon receipt of one or more MSRP SEND requests, which constitute one chat message, the IP-SM-GW shall proceed with the procedures in subclauses 6.1.11.2, 6.1.11.3 and 6.1.11.4.
+
+#### 6.1.11.2 Sending of the SMS-DELIVER (over CS/PS or IP)
+
+Upon receipt of one or more MSRP SEND request(s), which constitute one chat message that is to be delivered as a Short Message, the IP-SM-GW:
+
+- 1) may attempt to deliver the MSRP SEND request(s) as SMS over IP, if operator policy sets SMS over IP as highest priority for delivery attempts. If this attempt succeeds, then the IP-SM-GW shall skip subsequent steps;
+- 2) shall query the routing information from HSS as described in subclause 6.1.3.2; and,
+- 3) if routing information is available (SGSN and/or MSC address), the IP-SM-GW shall attempt the delivery of a Short Message over IP, over CS, and PS. The priority order of these attempts is an operator policy.
+
+For the delivery of a chat message, received in one or more MSRP SEND requests as a Short Message over CS/PS, the IP-SM-GW shall send a MT\_FORWARD\_SHORT\_MESSAGE to the MSC/SGSN as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.2.
+
+And in addition, the TP-UD element shall contain the content of the MSRP SEND request(s). When the TP-OA element is set to an MSISDN assigned by the IP-SM-GW, the MSISDN of the original sender shall be included in the information sent to the SMS user (unless the Chat Session SIP request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this). For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+For the delivery of a chat message, received in one or more MSRP SEND requests, as a Short Message over IP, the IP-SM-GW shall send one or more SIP MESSAGE request(s) containing RP-DATA message in the body to the S-CSCF as described in 3GPP TS 24.341 [5] and 3GPP TS 24.011 [9]. Each SMSIP MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.3.
+
+#### 6.1.11.3 Receiving of SMS-DELIVER-REPORT (over CS/PS or IP)
+
+##### 6.1.11.3.1 Receiving of SMS-DELIVER-REPORT over CS/PS
+
+Upon receipt of an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated MSRP SEND request received before was delivered as a single Short Message, the IP-SM-GW shall:
+
+- send an MSRP 200 response to the associated MSRP SEND request sender, if the MT\_FORWARD\_SHORT\_MESSAGE\_ACK message does not contain the User error parameter. If the associated MSRP SEND request received before contains a request for Success-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender; or
+- attempt to deliver the Short Message in the next domains as specified in subclause 6.1.5.6, if the MT\_FORWARD\_SHORT\_MESSAGE\_ACK message contains the User error parameter. If all retries fail, the IP-SM-GW shall send an MSRP SEND error response. The response code to be sent is determined by examining the value of the User error parameter. Table 6.1.11.3.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to MSRP SEND response codes. If the associated MSRP SEND request received before contains a request for Failure-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender.
+
+Upon receipt of MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, and if the associated MSRP SEND request received before was delivered as concatenated Short Messages, the IP-SM-GW shall wait for the last MT\_FORWARD\_SHORT\_MESSAGE\_ACK message. Then the IP-SM-GW shall:
+
+- send an MSRP 200 response to the associated MSRP SEND request sender, if none of the MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If the associated MSRP SEND request received before contains a request for Success-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender; or
+- attempt to deliver the Short Message in the next domains as specified in subclause 6.1.5.6, if at least one of MT\_FORWARD\_SHORT\_MESSAGE\_ACK messages contains the User error parameter. If all retries fail, the IP-SM-GW shall send an MSRP error response to the associated MSRP SEND request sender. The MSRP response code to be sent is determined by examining the value of the User error parameter. Table 6.1.11.3.1.1 specifies the mapping of the User error parameter as described in 3GPP TS 29.002 [7], to MSRP response codes. If the associated MSRP SEND request received before contains a request for Failure-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender.
+
+**Table 6.1.11.3.1.1: Mapping from User error parameter to MSRP response**
+
+| <b>Value of the User error parameter</b>                                                                                                                                 | <b>MSRP response code</b> |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Unidentified subscriber                                                                                                                                                  | 413                       |
+| Absent Subscriber SM                                                                                                                                                     | 408                       |
+| Subscriber busy for MT SMS                                                                                                                                               | 408                       |
+| Facility Not Supported                                                                                                                                                   | 501                       |
+| Illegal Subscriber indicates that delivery of the mobile terminated Short Message failed because the mobile station failed authentication                                | 501                       |
+| Illegal equipment indicates that delivery of the mobile terminated Short Message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed; | 501                       |
+| System Failure                                                                                                                                                           | 501                       |
+| SM Delivery Failure with cause memory capacity exceeded in the mobile equipment                                                                                          | 408                       |
+| SM Delivery Failure with cause protocol error                                                                                                                            | 501                       |
+| SM Delivery Failure with cause mobile equipment does not support the mobile terminated Short Message service                                                             | 501                       |
+| Unexpected Data Value                                                                                                                                                    | 501                       |
+| Data Missing                                                                                                                                                             | 501                       |
+
+##### 6.1.11.3.2 Receiving of SMS-DELIVER-REPORT over IP
+
+Upon receipt of an SMSIP MESSAGE with RP-ACK or RP-ERROR message in the body, the IP-SM-GW shall respond with a SMSIP 202 (Accepted) response in accordance with 3GPP TS 24.341 [5].
+
+If the SMSIP MESSAGE contains an RP-ACK message in the body, and the associated MSRP SEND request received before contains a request for Success-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender. If the associated MSRP SEND request received before was delivered as concatenated Short Messages and all the SMSIP MESSAGES contain RP-ACK message in the body for the concatenated Short Messages, and the associated MSRP SEND request received before contains a request for a Success-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender.
+
+If the SMSIP MESSAGE contains an RP-ERROR message in the body, the IP-SM-GW shall attempt to deliver the Short Message in the next domains as specified in subclause 6.1.5.6. If all retries fail and the associated MSRP SEND request received before contains a request for a Failure-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender. If the associated MSRP SEND request received before was delivered as concatenated Short Messages and at least one of the SMSIP MESSAGES contains RP-ERROR message in the body for the concatenated Short Messages, and the associated MSRP SEND request received before contains a request for a Failure-Report, a REPORT shall be sent according to subclause 6.1.11.4 to the associated MSRP SEND request sender.
+
+#### 6.1.11.4 Sending of the MSRP REPORT request
+
+If a positive SMS-DELIVER-REPORT has been received and an MSRP Success REPORT was requested in the MSRP SEND, then the IP-SM-GW shall send a Success REPORT in accordance with RFC 4975 [19].
+
+If a negative SMS-DELIVER-REPORT has been received and an MSRP Failure REPORT was requested in the MSRP SEND, then the IP-SM-GW shall send a Failure REPORT in accordance with RFC 4975 [19].
+
+### 6.1.12 Submitting an MSRP SEND request in an ongoing Chat Session anchored in the originating network as a (concatenated) Short Message
+
+#### 6.1.12.1 Receiving of the MSRP SEND request
+
+This subclause describes the procedure when the IP-SM-GW located in the originating network receives an MSRP SEND request as part of an ongoing Chat Session.
+
+Upon receipt of one or more MSRP SEND requests, which constitute one chat message, the IP-SM-GW shall proceed with the procedures in subclauses 6.1.12.2, 6.1.12.3 and 6.1.12.4.
+
+#### 6.1.12.2 Sending of the SMS-SUBMIT
+
+The IP-SM-GW shall submit a Short Message to the SMS-SC as described in subclause 6.1.18.4 with the following addition:
+
+- TP-UD element shall contain the content of the MSRP SEND request(s). When the TP-OA element is set to an MSISDN assigned by the IP-SM-GW the MSISDN of the original sender shall be included in the information sent to the SMS user (unless the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this). For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+#### 6.1.12.3 Receiving of SMS-SUBMIT-REPORT (over CS/PS or IP)
+
+Upon receipt of an MO\_FORWARD\_SHORT\_MESSAGE\_ACK with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing a positive SMS-SUBMIT-REPORT, and if the associated MSRP SEND request received before contains a request for a Success-Report, a REPORT shall be sent according to subclause 6.1.12.4 to the associated MSRP SEND request sender.
+
+Upon receipt of an MO\_FORWARD\_SHORT\_MESSAGE\_ACK with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing the User error parameter, and if the associated MSRP SEND request received before contains a request for a Failure-Report, a REPORT shall be sent according to subclause 6.1.12.4 to the associated MSRP SEND request sender. If the associated MSRP SEND request received before was delivered as concatenated Short Messages as described in subclause 6.1.6.3, and one of the MO\_FORWARD\_SHORT\_MESSAGE\_ACK for the concatenated Short Messages contains the User error parameter, and if the associated MSRP SEND request received before contains a request for a Failure-Report, a REPORT shall be sent according to subclause 6.1.12.4 to the associated MSRP SEND request sender.
+
+#### 6.1.12.4 Sending of the MSRP REPORT request
+
+If a positive SMS-SUBMIT-REPORT has been received and an MSRP Success REPORT was requested in the MSRP SEND, then the IP-SM-GW shall send a Success REPORT in accordance with RFC 4975 [19].
+
+If a negative SMS-SUBMIT-REPORT has been received and an MSRP Failure REPORT was requested in the MSRP SEND, then the IP-SM-GW shall send a Failure REPORT in accordance with RFC 4975 [19].
+
+### 6.1.13 Handling of the Chat Session teardown request received as a Short Message in the terminating network
+
+#### 6.1.13.1 General
+
+This subclause describes the procedure when the IP-SM-GW located in the terminating network interworks a Short Message requesting to leave a Chat Session to a Chat Session BYE request.
+
+IP-SM-GW procedures at the reception of the Short Message are described in subclause 6.1.13.2.
+
+The creation of the Short Message delivery report is described in subclause 6.1.13.3.
+
+IP-SM-GW procedures to send a BYE request to the Chat Session are described in subclause 6.1.18.2.
+
+#### 6.1.13.2 Receiving of SMS-DELIVER containing a Chat Session teardown request
+
+When the IP-SM-GW in the terminating networks receives a Short Message from the SMS-GMSC it shall determine if the message from a served SM user is a Chat Session teardown request, i.e. the SM user intends to leave a group Chat Session or to tear down a one-to-one Chat Session. The received Short Message is a Chat Session teardown request if:
+
+- 1) the Short Message is sent to a Chat Session where the SM user participates as described in subclause 6.1.18.1; and
+- 2) the Short Message contains operator defined text indicating a teardown request.
+
+If the received Short Message is a Chat Session teardown request, then the IP-SM-GW shall acknowledge the Short Message as described in subclause 6.1.18.5 and leave the Chat Session as described in subclause 6.1.18.2.
+
+### 6.1.14 Handling of the Chat Session teardown request received as a Chat Session BYE in the terminating network
+
+#### 6.1.14.1 Receiving of the Chat Session BYE request
+
+This subclause describes the procedure when the IP-SM-GW located in the terminating network receives a Chat Session SIP BYE request to tear down a Chat Session.
+
+If operator policy mandates the SMS user to be informed of the Chat Session teardown, then the IP-SM-GW shall proceed with the procedures in subclauses 6.1.14.2, 6.1.14.3 and 6.1.14.4. Otherwise the IP-SM-GW shall proceed with the procedures in subclause 6.1.14.4.
+
+#### 6.1.14.2 Sending of the SMS-DELIVER (over CS/PS or IP)
+
+Upon receipt of a Chat Session teardown request as a SIP BYE request that is to be delivered as a Short Message, the IP-SM-GW:
+
+- 1) may attempt to deliver Chat Session teardown request as SMS over IP, if operator policy sets SMS over IP as highest priority for delivery attempts. If this attempt succeeds, then the IP-SM-GW shall skip subsequent steps;
+- 2) shall query the routing information from HSS as described in subclause 6.1.3.2; and,
+- 3) if routing information is available (SGSN and/or MSC address), the IP-SM-GW shall attempt the delivery of a Short Message over IP, over CS, and PS. The priority order of these attempts is an operator policy.
+
+For the delivery of a Chat Session teardown request as a Short Message over CS/PS, the IP-SM-GW shall send a MT\_FORWARD\_SHORT\_MESSAGE to the MSC/SGSN as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.2.
+
+For the delivery of a Chat Session teardown request as a Short Message over IP, the IP-SM-GW shall send an SMSIP MESSAGE containing RP-DATA message in the body to the S-CSCF as described in 3GPP TS 24.341 [5] and 3GPP TS 24.011 [9]. The SMSIP MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.3.
+
+For every attempt the TP-UD element shall contain operator defined data that should convey information to the SMS user that (s)he is removed from a Chat Session. Since the TP-OA element is set to an MSISDN assigned by the IP-SM-GW the MSISDN of the original sender shall be included in the information sent to the SMS user (unless the Chat Session SIP request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this). For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+#### 6.1.14.3 Receiving of SMS-DELIVER-REPORT (over CS/PS or IP)
+
+##### 6.1.14.3.1 Receiving of SMS-DELIVER-REPORT over CS/PS
+
+Upon receipt of an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT the IP-SM-GW shall proceed with the procedures in subclause 6.1.14.4.
+
+NOTE: It is assumed that the associated SIP BYE request received before was delivered as a single Short Message.
+
+##### 6.1.14.3.2 Receiving of SMS-DELIVER-REPORT over IP
+
+Upon receipt of an SMSIP MESSAGE with RP-ACK or RP-ERROR message in the body, the IP-SM-GW shall respond with a SIP 202 (Accepted) response in accordance with 3GPP TS 24.341 [5].
+
+NOTE: It is assumed that the associated SIP BYE request received before was delivered as a single Short Message.
+
+#### 6.1.14.4 Sending of the SIP 200 (OK) response to a BYE request for a Chat Session
+
+The IP-SM-GW shall send a SIP 200 (OK) response to the SIP BYE request. If the IP-SM-GW associated a specific MSISDN for the Chat Session, then the IP-SM-GW shall release that MSISDN.
+
+### 6.1.15 Handling of the Chat Session teardown request received as a Short Message in the originating network
+
+This section describes the procedure when the IP-SM-GW located in the originating network interworks a Short Message requesting to leave a Chat Session to a Chat Session BYE request.
+
+IP-SM-GW procedures at the reception of the Short Message are described in subclause 6.1.13.2.
+
+The creation of the Short Message delivery report is described in subclause 6.1.13.3.
+
+IP-SM-GW procedures to send a BYE request to the Chat Session are described in subclause 6.1.18.2.
+
+### 6.1.16 Handling of the Chat Session teardown request received as a Chat Session BYE in the originating network
+
+#### 6.1.16.1 Receiving of the Chat Session BYE request
+
+This section describes the procedure when the IP-SM-GW located in the originating network receives a Chat Session BYE request to tear down a Chat Session.
+
+If operator policy mandates the SMS user to be informed of the Chat Session teardown, then the IP-SM-GW shall proceed with the procedures in subclauses 6.1.16.2, 6.1.16.3 and 6.1.14.4. Otherwise the IP-SM-GW shall proceed with the procedures in subclause 6.1.14.4.
+
+#### 6.1.16.2 Sending of the SMS-SUBMIT
+
+The IP-SM-GW shall submit a Short Message to the SC as described in subclause 6.1.18.4 with the following addition:
+
+- TP-UD element shall contain operator defined data that should convey information to the SMS user that (s)he is removed from a Chat Session. When the TP-OA element is set to an MSISDN assigned by the IP-SM-GW the MSISDN of the original sender shall be included in the information sent to the SMS user (unless the SIP INVITE request contains the Privacy header field with "header" or "user" or "id" and the operator policy allows this). For a one-to-one Chat Session, the original sender is carried in the P-Asserted-Identity header field of the SIP request, and for a group Chat Session, the original sender is carried in the Referred-By header field.
+
+#### 6.1.16.3 Receiving of SMS-SUBMIT-REPORT (over CS/PS or IP)
+
+Upon receipt of an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT the IP-SM-GW shall proceed with the procedures in subclause 6.1.14.4.
+
+NOTE: It is assumed that the associated SIP BYE request received before was delivered as a single Short Message.
+
+### 6.1.17 Handling of Participant Information
+
+#### 6.1.17.1 General
+
+When a group Chat Session has been established and operator policy mandates that the SMS user is informed of changes in the participation of group Chat Sessions then the IP-SM-GW shall follow the procedures:
+
+- in subclause 6.1.17.2, 6.1.17.3 and 6.1.17.4 when interworking in the terminating network; or
+
+- in subclause 6.1.17.2, 6.1.17.3 and 6.1.17.5 when interworking in the originating network.
+
+#### 6.1.17.2 Subscribing to Participant Information
+
+The IP-SM-GW, acting as CPM Client on behalf of the SMS user, shall subscribe to receive Participant Information as described in OMA-TS-CPM\_Conv\_Fnc [17].
+
+#### 6.1.17.3 Receiving of a Participant Information Notification
+
+When the IP-SM-GW receives a SIP NOTIFY request that is part of the same SIP dialog as the previously sent SIP SUBSCRIBE request for subscribing to Participant Information, the IP-SM-GW shall follow the procedures in OMA-TS-CPM\_Conv\_Fnc [17] with the following exception:
+
+- to display the current Participant Information of the group Chat Session to the SMS user the IP-SM-GW shall proceed with the procedure in subclause 6.1.17.4 when interworking in the terminating network; and
+- to display the current Participant Information of the group Chat Session to the SMS user the IP-SM-GW shall proceed with the procedures in subclause 6.1.17.5 when interworking in the originating network.
+
+The frequency of sending Participant Information to the SMS user is subject to operator policy.
+
+#### 6.1.17.4 Sending Participant Information as SMS-Deliver when interworking in the terminating network
+
+To deliver Participant Information to the SMS user when interworking in the terminating network the IP-SM-GW:
+
+- 1) may attempt to deliver the Participant Information as SMS over IP, if operator policy sets SMS over IP as highest priority for delivery attempts. If this attempt succeeds, then the IP-SM-GW shall skip subsequent steps;
+- 2) shall query the routing information from HSS as described in subclause 6.1.3.2; and
+- 3) if routing information is available (SGSN and/or MSC address), the IP-SM-GW shall attempt the delivery of a Short Message over IP, over CS, and PS. The priority order of these attempts is an operator policy.
+
+For the delivery Participant Information as a Short Message over CS/PS, the IP-SM-GW shall send a MT\_FORWARD\_SHORT\_MESSAGE to the MSC or SGSN as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.2. In addition the TP-UD element shall contain operator defined data that conveys Participant Information (e.g. users who have joined or left) to the SMS user.
+
+For the delivery of Participant Information as a Short Message over IP, the IP-SM-GW shall send a SIP MESSAGE request containing RP-DATA message in the body to the S-CSCF as described in 3GPP TS 24.341 [5] and 3GPP TS 24.011 [9]. In addition parameters of the SMSIP MESSAGE shall be set as described in subclauses 6.1.18.3.1 and 6.1.18.3.3. In addition the TP-UD element shall contain operator defined data that conveys Participant Information (e.g. users who have joined or left) to the SMS user.
+
+The IP-SM-GW shall proceed with receiving of an SMS-DELIVER-REPORT in accordance with 3GPP TS 23.040 [2]. If this MT\_FORWARD\_SHORT\_MESSAGE\_ACK contains the User error parameter the IP-SM-GW shall attempt to deliver in the next domains as specified in subclause 6.1.7.3 for a Chat Session INVITE request. No further procedures are defined on reception of the SMS-DELIVER-REPORT as interworking of this message is not required for Participant Information.
+
+#### 6.1.17.5 Sending Participant Information as SMS-SUBMIT when interworking in the originating network
+
+To deliver Participant Information to the SMS user when interworking in the originating network the IP-SM-GW shall submit a Short Message to the SMS-SC as described in subclause 6.1.18.4. In addition the TP-UD element shall contain operator defined data that conveys Participant Information (e.g. users who have joined or left) to the SMS user.
+
+The IP-SM-GW shall proceed with receiving of an SMS-SUBMIT-REPORT in accordance with 3GPP TS 23.040 [2]. No further procedures are defined on reception of the SMS-SUBMIT-REPORT as interworking of this message is not required for Participant Information.
+
+### 6.1.18 Common procedures for chat session interworking
+
+#### 6.1.18.1 Determining if a received Short Message is associated to a Chat Session
+
+When the IP-SM-GW receives a Short Message from the SMS-GMSC, it shall determine if the message is associated with a Chat Session. The received Short Message is associated with a Chat Session if:
+
+- 1) the Short Message is addressed to the MSISDN assigned to the Chat Session, as described in subclauses 6.1.7.1 and 6.1.8.1; and
+- 2) the originator of the Short Message is the SM user invited to the Chat Session using that MSISDN.
+
+#### 6.1.18.2 Leaving a Chat Session
+
+After sending the SMS-DELIVER-REPORT for the Chat Session teardown request the IP-SM-GW shall send a SIP BYE request to leave a group Chat Session or to tear down a one-to-one Chat Session as described in OMA-TS-CPM\_System\_Description [20].
+
+If the IP-SM-GW associated a specific MSISDN for the Chat Session, then the IP-SM-GW shall release that MSISDN.
+
+#### 6.1.18.3 Sending SMS-DELIVER – common procedures
+
+##### 6.1.18.3.1 General
+
+Both the SM-RP-UI parameter of the MT\_FORWARD\_SHORT\_MESSAGE and the RP-User Data element of the RP-DATA message in the SMSIP MESSAGE body shall be set to SMS-DELIVER. The elements of SMS-DELIVER message shall be set in accordance with 3GPP TS 23.040 [2], with the following information:
+
+- a) TP-MTI element set to 00 (SMS-DELIVER);
+  - b) TP-MMS element set in accordance with 3GPP TS 23.040 [2];
+- NOTE 1: For example, for concatenated Short Messages, TP-MMS would be set to 0 while there are more messages to send.
+- c) TP-RP element set to 0 (TP-Reply-Path parameter is not set in this SMS-DELIVER);
+  - d) TP-UDHI element set in accordance with 3GPP TS 23.040 [2];
+  - e) TP-SRI element shall be set to 0;
+  - f) TP-OA element set to the E.164 address used by the IP-SM-GW for the duration of the Chat Session;
+  - g) TP-PID element set to 00000000 (SME-to-SME protocol);
+  - h) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+  - i) TP-SCTS element set to time when the IP-SM-GW received the SIP INVITE request; and
+  - j) TP-UDL element set in accordance with 3GPP TS 23.040 [2].
+
+NOTE 2: Contents of the TP-UD element defined separately for each procedure.
+
+If the content of the operator defined text or chat message to be sent in Short Message format is greater than the allowed message length of a Short Message, then the IP-SM-GW shall send concatenated Short Messages.
+
+NOTE 3: In the case of receiving an MT\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-DELIVER-REPORT, containing the User error parameter for one segment of the concatenated Short Message, the default action of the IP-SM-GW is not to send any remaining segments.
+
+3GPP TS 23.040 [2] specifies that a Short Message supports GSM 7-bit and UCS2 encoded text. The IP-SM-GW shall ensure the operator defined text is encoded using the appropriate data coding scheme.
+
+##### 6.1.18.3.2 Sending of SMS-DELIVER over CS/PS
+
+The parameters of the MT\_FORWARD\_SHORT\_MESSAGE shall be set as described in 3GPP TS 29.002 [7], with the following information:
+
+- Invoke-ID parameter set in accordance with 3GPP TS 29.002 [7];
+- SM-RP-DA element set to the address associated with the SIP INVITE request receiver;
+- SM-RP-OA element set to the address of the IP-SM-GW;
+- More Messages To Send parameter set in accordance with 3GPP TS 29.002 [7]; and
+
+NOTE: For example, for concatenated Short Messages, More Messages To Send would be set to 0 while there are more messages to send.
+
+- SM-RP-UI parameter set to SMS-DELIVER.
+
+##### 6.1.18.3.3 Sending of SMS-DELIVER over IP
+
+The IP-SM-GW shall send the SMSIP MESSAGE as described in 3GPP TS 24.341 [5] with the following exceptions:
+
+- the Request-URI mapped from the Request-URI of the associated SIP INVITE request; and
+- the body of the request shall contain an RP-DATA message. The elements of the RP-DATA message shall be set as described in 3GPP TS 24.011 [9], with the following information:
+  - a) RP-Message Type element set to 001 (network to MS);
+  - b) RP-Message Reference element set in accordance with 3GPP TS 24.011 [9];
+  - c) RP-Originator Address element set to the address of the IP-SM-GW;
+  - d) RP-Destination Address element shall be set to the MSISDN of the associated SIP INVITE request receiver, retrieved by the IP-SM-GW as part of the subscriber data from the HSS at registration; and
+  - e) RP-User Data set to SMS-DELIVER.
+
+#### 6.1.18.4 Sending SMS-SUBMIT – common procedures
+
+NOTE 1: The sender is either the MSISDN of the CPM user or an MSISDN assigned by the IP-SM-GW for this particular Chat Session as described in subclause 6.1.8.1.
+
+To submit a Short Message to the SC, the IP-SM-GW shall send MO\_FORWARD\_SHORT\_MESSAGE as described in 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2]. In addition, for the information elements listed below, the following interworking procedures shall apply:
+
+- Invoke-ID parameter set in accordance with 3GPP TS 29.002 [7];
+- SM-RP-DA parameter set to the address of user's home network Service Centre configured in the IP-SM-GW, or retrieved as part of the subscriber data from the HSS at registration by the IP-SM-GW;
+- SM-RP-OA parameter set based on the MSISDN assigned in section 6.1.8.1;
+- SM-RP-UI parameter set to SMS-SUBMIT; and
+- the elements of the SMS-SUBMIT message shall be set as described in 3GPP TS 23.040 [2] subclause 9.2.2, with the following information:
+  - a) TP-MTI element set to 01 (SMS-SUBMIT);
+  - b) TP-RD element set to 1 (Instruct the SC to reject an SMS SUBMIT for an SM still held in the SC which has the same TP MR and the same TP DA as the previously submitted SM from the same OA.);
+  - c) TP VPF element set to 00 (TP VP field not present);
+  - d) TP-UDHI element set in accordance with 3GPP TS 23.040 [2];
+
+- e) TP-SRR element shall be set to 0 (A status report is not requested);
+- f) TP-MR element set in accordance with 3GPP TS 23.040 [2];
+- g) TP-RP element set to 0 (TP Reply Path parameter is not set in this SMS SUBMIT);
+- h) TP-DA element set based on the value of the Request-URI in the SIP INVITE request as long as the Request-URI contains an E.164 address;
+- i) TP-PI element set to 00000000 (SME-to-SME protocol);
+- j) TP-DCS element set in accordance with 3GPP TS 23.040 [2]; and
+- k) TP-UDL element set in accordance with 3GPP TS 23.040 [2].
+
+NOTE 2: Contents of the TP-UD element defined separately for each procedure.
+
+If the content of the operator defined text or chat message to be sent in Short Message format is greater than the allowed message length of a Short Message, then the IP-SM-GW shall send concatenated Short Messages.
+
+NOTE 3: In the case of receiving an MO\_FORWARD\_SHORT\_MESSAGE\_ACK message with the SM-RP-UI parameter set to value SMS-SUBMIT-REPORT, containing the User error parameter for one segment of the concatenated Short Message, the default action of the IP-SM-GW is not to send any remaining segments.
+
+3GPP TS 23.040 [2] specifies that a Short Message supports GSM 7-bit and UCS2 encoded text. The IP-SM-GW shall ensure the operator defined text is encoded into an appropriate data coding scheme supported for Short Messages.
+
+#### 6.1.18.5 Sending SMS-DELIVER-REPORT
+
+If the IP-SM-GW decided to send an SMS-DELIVER-REPORT, the IP-SM-GW shall send the MT-FORWARD-SHORT-MESSAGE-ACK message to the SMS-GMSC in accordance with 3GPP TS 29.002 [7] and 3GPP TS 23.040 [2] with the following information:
+
+- Invoke Id parameter set in accordance with 3GPP TS 29.002 [7];
+
+NOTE 1: The User error parameter is not contained in the MT-FORWARD-SHORT-MESSAGE-ACK message.
+
+- SM-RP-UI set to SMS-DELIVER-REPORT; and
+- the elements of the SMS-DELIVER-REPORT shall be set as described in 3GPP TS 23.040 [2] with the following information:
+  - a) TP-MTI element set to 00 (SMS-DELIVER-REPORT);
+  - b) TP-PI element set in accordance with 3GPP TS 23.040 [2];
+  - c) TP-PID element set to 00000000 (SME-to-SME protocol);
+  - d) TP-DCS element set in accordance with 3GPP TS 23.040 [2];
+  - e) TP-UDL element set in accordance with 3GPP TS 23.040 [2]; and
+  - f) TP-UD element set in accordance with 3GPP TS 23.040 [2].
+
+NOTE 2: The TP-FCS element is not contained in the SMS-DELIVER-REPORT.
+
+# --- Annex A (normative): Impacts of TP parameters in a Short Message on service level interworking
+
+## A.1 Scope
+
+The present annex defines how the TP parameters in a short message impact the possibility of service level interworking. If any of the criteria defined in this annex indicate that service level interworking is not allowed then the procedure in subclause 6.1.4.5 shall be followed.
+
+## --- A.2 TP-Data-Coding-Scheme (TP-DCS)
+
+Table A.2.1 describes whether or not service level interworking is allowed based on the value of the TP-DCS parameter of a Short Message.
+
+**Table A.2.1: Impact of the TP-DCS parameter on service level interworking**
+
+| <b>TP-DCS Coding Group</b> | <b>TP-DCS Description</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |       |                                                                | <b>Service Level Interworking allowed<br/>(Y/N)</b> |
+|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|----------------------------------------------------------------|-----------------------------------------------------|
+|                            | Depends on the use of TP-DCS bits 3..0                                                                                                                                                                                                                                                                                                                                                                                                                                                       |       |                                                                |                                                     |
+| TP-DCS Bits 7..4           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |       |                                                                | <b>(Y/N)</b>                                        |
+| 00xx                       | General Data Coding indication<br>Bits 5..0 indicate the following:<br><br>Bit 5, if set to 0, indicates the text is uncompressed<br>Bit 5, if set to 1, indicates the text is compressed using the compression algorithm defined in 3GPP TS 23.042 [14]                                                                                                                                                                                                                                     |       |                                                                | n/a                                                 |
+|                            | Bit 4, if set to 0, indicates that bits 1 to 0 are reserved and have no message class meaning                                                                                                                                                                                                                                                                                                                                                                                                |       |                                                                | Y                                                   |
+|                            | Bit 4, if set to 1, indicates that bits 1 to 0 have a message class meaning::                                                                                                                                                                                                                                                                                                                                                                                                                |       |                                                                |                                                     |
+|                            | Bit 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Bit 0 | Message Class                                                  |                                                     |
+|                            | 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0     | Class 0                                                        | Y                                                   |
+|                            | 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 1     | Class 1 Default meaning: ME-specific.                          | Y                                                   |
+|                            | 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0     | Class 2 (U)SIM specific message                                | N                                                   |
+|                            | 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 1     | Class 3 Default meaning: TE specific (see 3GPP TS 27.005 [15]) | Y                                                   |
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |       |                                                                |                                                     |
+|                            | Bits 3 and 2 indicate the character set being used, as follows :                                                                                                                                                                                                                                                                                                                                                                                                                             |       |                                                                |                                                     |
+|                            | Bit 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Bit2  | Character set:                                                 |                                                     |
+|                            | 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0     | GSM 7 bit default alphabet                                     | Y                                                   |
+|                            | 0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 1     | 8 bit data                                                     | N                                                   |
+|                            | 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0     | UCS2 (16bit)                                                   | Y                                                   |
+|                            | 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 1     | Reserved                                                       | n/a                                                 |
+|                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |       |                                                                |                                                     |
+|                            | NOTE: The special case of bits 7..0 being 0000 0000 indicates the GSM 7 bit default alphabet with no message class                                                                                                                                                                                                                                                                                                                                                                           |       |                                                                | Y                                                   |
+| 01xx                       | Message Marked for Automatic Deletion Group<br><br>This group can be used by the SM originator to mark the message ( stored in the ME or (U)SIM ) for deletion after reading irrespective of the message class.<br>The way the ME will process this deletion should be manufacturer specific but shall be done without the intervention of the End User or the targeted application. The mobile manufacturer may optionally provide a means for the user to prevent this automatic deletion. |       |                                                                | See Group 00xx                                      |
+|                            | Bit 5..0 are coded exactly the same as Group 00xx                                                                                                                                                                                                                                                                                                                                                                                                                                            |       |                                                                |                                                     |
+| 1000..1011                 | Reserved coding groups                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |       |                                                                | n/a                                                 |
+
+| TP-DCS Coding Group<br><br>TP-DCS Bits 7..4 | TP-DCS Description<br><br>Depends on the use of TP-DCS bits 3..0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Service Level Interworking allowed<br><br>(Y/N) |
+|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|
+| 1100                                        | <p>Message Waiting Indication Group: Discard Message</p> <p>The specification for this group is exactly the same as for Group 1101, except that:</p> <ul style="list-style-type: none"> <li>- after presenting an indication and storing the status, the ME may discard the contents of the message.</li> </ul> <p>The ME shall be able to receive, process and acknowledge messages in this group, irrespective of memory availability for other types of Short Message.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | N                                               |
+| 1101                                        | <p>Message Waiting Indication Group: Store Message</p> <p>This Group defines an indication to be provided to the user about the status of types of message waiting on systems connected to the GSM/UMTS PLMN. The ME should present this indication as an icon on the screen, or other MMI indication. The ME shall update the contents of the Message Waiting Indication Status on the SIM (see 3GPP TS 51.011 [22]) or USIM (see 3GPP TS 31.102 [21]) when present or otherwise should store the status in the ME. In case there are multiple records of EF<sub>MWIS</sub> this information shall be stored within the first record. The contents of the Message Waiting Indication Status should control the ME indicator. For each indication supported, the mobile may provide storage for the Origination Address. The ME may take note of the Origination Address for messages in this group and group 1100.</p> <p>Text included in the user data is coded in the GSM 7 bit default alphabet. Where a message is received with bits 7..4 set to 1101, the mobile shall store the text of the SMS message in addition to setting the indication. The indication setting should take place irrespective of memory availability to store the Short Message.</p> <p>Bits 3 indicates Indication Sense:</p> <p>Bit 3<br/> 0 Set Indication Inactive<br/> 1 Set Indication Active</p> <p>Bit 2 is reserved, and set to 0</p> <p>Bit 1 Bit 0 Indication Type:<br/> 0 0 Voicemail Message Waiting<br/> 0 1 Fax Message Waiting<br/> 1 0 Electronic Mail Message Waiting<br/> 1 1 Other Message Waiting*</p> <p>* Mobile manufacturers may implement the "Other Message Waiting" indication as an additional indication without specifying the meaning.</p> | N                                               |
+| 1110                                        | <p>Message Waiting Indication Group: Store Message</p> <p>The coding of bits 3..0 and functionality of this feature are the same as for the Message Waiting Indication Group above, (bits 7..4 set to 1101) with the exception that the text included in the user data is coded in the uncompressed UCS2 character set.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | N                                               |
+
+## A.3 TP-User-Data Header Information Elements (UDH-IE)
+
+If a Short Message contains a Header in the TP-User-Data field, then the Header may include multiple Information Elements. Table A.3.1 describes whether or not service level interworking is allowed based on the occurrence of different Information Elements. The Information Elements are listed by Information Element Identifier in the table.
+
+**Table A.3.1: Impact of the TP-UDH information elements on service level interworking**
+
+| <b>UDH-IEI Value (hex)</b> | <b>UDH-IE Description</b>                                   | <b>Service Level Interworking allowed (Y/N)</b> |
+|----------------------------|-------------------------------------------------------------|-------------------------------------------------|
+| 00                         | Concatenated Short Messages, 8-bit reference number         | Y                                               |
+| 01                         | Special SMS Message Indication                              | N                                               |
+| 02                         | Reserved                                                    | n/a                                             |
+| 03                         | Value not used to avoid misinterpretation as <LF> character | n/a                                             |
+| 04                         | Application port addressing scheme, 8 bit address           | N                                               |
+| 05                         | Application port addressing scheme, 16 bit address          | N                                               |
+| 06                         | SMSC Control Parameters                                     | Y                                               |
+| 07                         | UDH Source Indicator                                        | Y                                               |
+| 08                         | Concatenated Short Message, 16-bit reference number         | Y                                               |
+| 09                         | Wireless Control Message Protocol                           | N                                               |
+| 0A                         | Text Formatting                                             | Y                                               |
+| 0B                         | Predefined Sound                                            | Y                                               |
+| 0C                         | User Defined Sound (iMelody max 128 bytes)                  | Y                                               |
+| 0D                         | Predefined Animation                                        | Y                                               |
+| 0E                         | Large Animation (16*16 times 4 = 32*4 =128 bytes)           | Y                                               |
+| 0F                         | Small Animation (8*8 times 4 = 8*4 =32 bytes)               | Y                                               |
+| 10                         | Large Picture (32*32 = 128 bytes)                           | Y                                               |
+| 11                         | Small Picture (16*16 = 32 bytes)                            | Y                                               |
+| 12                         | Variable Picture                                            | Y                                               |
+| 13                         | User prompt indicator                                       | Y                                               |
+| 14                         | Extended Object                                             | Y                                               |
+| 15                         | Reused Extended Object                                      | Y                                               |
+| 16                         | Compression Control                                         | Y                                               |
+| 17                         | Object Distribution Indicator                               | Y                                               |
+| 18                         | Standard WVG object                                         | Y                                               |
+| 19                         | Character Size WVG object                                   | Y                                               |
+| 1A                         | Extended Object Data Request Command                        | Y                                               |
+| 1B-1F                      | Reserved for future EMS features (see subclause 3.10)       | n/a                                             |
+| 20                         | IETF RFC 822 [23] E-Mail Header                             | N                                               |
+| 21                         | Hyperlink format element                                    | Y                                               |
+| 22                         | Reply Address Element                                       | N                                               |
+| 23                         | Enhanced Voice Mail Information                             | N                                               |
+| 24 – 6F                    | Reserved for future use                                     | n/a                                             |
+| 70 – 7F                    | (U)SIM Toolkit Security Headers                             | N                                               |
+| 80 – 9F                    | SME to SME specific use                                     | N                                               |
+| A0 – BF                    | Reserved for future use                                     | n/a                                             |
+| C0 – DF                    | SC specific use                                             | N                                               |
+| E0 – FF                    | Reserved for future use                                     | n/a                                             |
+
+## A.4 TP-Protocol-Identifier (TP-PID)
+
+Table A.4.1 describes whether or not service level interworking is allowed based on the value of the TP-PID parameter in an SMS-DELIVER.
+
+**Table A.4.1: Impact of the TP-PID parameter on service level interworking**
+
+| TP-PID Bits 76 | TP-PID Description                                                                                                                                                                                                                                                                                                                   |                                     | Service Level Interworking Allowed (Y/N) |
+|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|------------------------------------------|
+| 00             | bit 5 indicates telematic interworking:<br><br>If bit 5 has value 1 in an SMS-DELIVER PDU, it indicates that the SME is a telematic device of a type which is indicated in bits 4..0.<br><br>If bit 5 has value 0 in an SMS-DELIVER PDU, the value in bits 4..0 identifies the SM-AL protocol being used between the SME and the MS. |                                     | Y                                        |
+| 01             | bits 5..0 are used as defined below                                                                                                                                                                                                                                                                                                  |                                     |                                          |
+|                | Bit 5..0                                                                                                                                                                                                                                                                                                                             |                                     |                                          |
+|                | 000000                                                                                                                                                                                                                                                                                                                               | Short Message Type 0                | Y                                        |
+|                | 000001                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 1        | Y                                        |
+|                | 000010                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 2        | Y                                        |
+|                | 000011                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 3        | Y                                        |
+|                | 000100                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 4        | Y                                        |
+|                | 000101                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 5        | Y                                        |
+|                | 000110                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 6        | Y                                        |
+|                | 000111                                                                                                                                                                                                                                                                                                                               | Replace Short Message Type 7        | Y                                        |
+|                | 001000..011101                                                                                                                                                                                                                                                                                                                       | Reserved                            | n/a                                      |
+|                | 011110                                                                                                                                                                                                                                                                                                                               | Enhanced Message Service (Obsolete) | n/a                                      |
+|                | 011111                                                                                                                                                                                                                                                                                                                               | Return Call Message                 | Y                                        |
+|                | 100000..111011                                                                                                                                                                                                                                                                                                                       | Reserved                            | n/a                                      |
+|                | 111100                                                                                                                                                                                                                                                                                                                               | ANSI-136 R-DATA                     | N                                        |
+|                | 111101                                                                                                                                                                                                                                                                                                                               | ME Data download                    | N                                        |
+|                | 111110                                                                                                                                                                                                                                                                                                                               | ME De-personalization Short Message | N                                        |
+|                | 111111                                                                                                                                                                                                                                                                                                                               | (U)SIM Data download                | N                                        |
+| 10             | reserved                                                                                                                                                                                                                                                                                                                             |                                     | n/a                                      |
+| 11             | Assigns bit 0-5 for SC specific use                                                                                                                                                                                                                                                                                                  |                                     | undefined                                |
+
+# Annex B (normative): Anonymous SMS
+
+## B.1 Scope
+
+The present annex defines how the sending party's address (SM-RP-OA parameter in case of SMS-SUBMIT, TP-OA element in case of SMS-DELIVER), which is mandatory in SMS, is set to anonymise the sender's identity and to clearly indicate that for the receiver of the SMS at the same time.
+
+## B.2 Anonymous address in SMS
+
+To indicate anonymous sender the address field representing the SM-RP-OA parameter in case of an SMS-SUBMIT or the TP-OA element in case of SMS-DELIVER should be set as follows:
+
+- length of address is set to 18;
+- type of number is set to alphanumerical;
+- numbering plan identification is set to ISDN/telephone numbering plan; and
+- the address value is set to "Anonymous" with the 7 bit character representation, as the default alphabet defined in 3GPP TS 23.038 [24].
+
+As an alternative, country specific text may be defined with the only restriction that it must fit to the 10 character limit of the alphanumerical type.
+
+The recommended encoding of the "Anonymous" alphanumeric address is shown in Figure B.2-1.
+
+| Octet # | bit 7 | bit 6 | bit 5 | bit 4 | bit 3 | bit 2 | bit 1 | bit 0 | Explanation                                  |                                           |                                                                 |
+|---------|-------|-------|-------|-------|-------|-------|-------|-------|----------------------------------------------|-------------------------------------------|-----------------------------------------------------------------|
+| 1       | 0     | 0     | 0     | 1     | 0     | 0     | 0     | 0     | length of address parameter (16 semi octets) |                                           |                                                                 |
+| 2       | 1     | 1     | 0     | 1     | 0     | 0     | 0     | 1     | ext                                          | type of number 101 indicates alphanumeric | Numbering plan id: 0001 indicates ISDN/telephone numbering plan |
+| 3       | 0     | 1     | 0     | 0     | 0     | 0     | 0     | 1     | x41 for ASCII 65 of "A"                      |                                           |                                                                 |
+| 4       | 1     | 1     | 1     | 1     | 0     | 1     | 1     | 1     | "o" x6E for ASCII 110 of "n"                 |                                           |                                                                 |
+| 5       | 1     | 1     | 0     | 1     | 1     | 0     | 1     | 1     | 110 of "n" x6F for ASCII 111 of              |                                           |                                                                 |
+| 6       | 1     | 0     | 0     | 1     | 1     | 1     | 0     | 1     | ASCII 121 of "y" x6E for ASCII               |                                           |                                                                 |
+| 7       | 0     | 1     | 1     | 0     | 1     | 1     | 1     | 1     | ASCII 109 of "m" x79 for                     |                                           |                                                                 |
+| 8       | 1     | 0     | 1     | 1     | 1     | 1     | 1     | 1     | x6F for ASCII 111 of "o" x6D for             |                                           |                                                                 |
+| 9       | 1     | 1     | 1     | 0     | 1     | 0     | 1     | 1     | x75 for ASCII 117 of "u"                     |                                           |                                                                 |
+| 10      | 0     | 1     | 1     | 1     | 0     | 0     | 1     | 1     | x73 for ASCII 115 of "s"                     |                                           |                                                                 |
+
+Figure B.2-1: Address field with "Anonymous" alphanumeric value
+
+# Annex C (informative): Change history
+
+| Change history |       |          |    |     |                                                                                                     |       |       |
+|----------------|-------|----------|----|-----|-----------------------------------------------------------------------------------------------------|-------|-------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment                                                                                     | Old   | New   |
+| 2008-04        |       |          |    |     | Rapporteur input for the skeleton                                                                   | -     | 0.0.0 |
+| 2008-05        |       |          |    |     | Implemented C3-080683, C3-080684, C3-080685, C3-080687, C3-080689, C3-080776, C3-080777, C3-080692. | 0.0.0 | 0.1.0 |
+| 2008-06        |       |          |    |     | New TS Number TS 29.311 assigned after CT#40                                                        | 0.1.0 | 0.1.1 |
+| 2008-06        |       |          |    |     | Implemented C3-081088, C3-081089, C3-081193, C3-081094, C3-081092, C3-081194, C3-081195, C3-081091. | 0.1.1 | 0.2.0 |
+
+| 2008-08        |        |           |     |     | Implemented C3-081555, C3-081554, C3-081556, C3-081557, C3-081558, C3-081559, C3-081561, C3-081312, C3-081562, C3-081314, C3-081563, C3-081564, C3-081565, C3-081566, C3-081567, C3-081568.                       | 0.2.0                                   | 0.3.0  |
+|----------------|--------|-----------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|--------|
+| 2008-09        |        |           |     |     | Version 1.0.0 created for presentation to TSG by MCC                                                                                                                                                              | 0.3.0                                   | 1.0.0  |
+| 2008-10        |        |           |     |     | Implemented C3-081961, C3-081956, C3-081957, C3-082108, C3-081959, C3-081960, C3-082109, C3-081963, C3-081972, C3-081973, C3-081974, C3-081975, C3-081816, C3-081976, C3-081818, C3-081819, C3-081977, C3-081978. | 1.0.0                                   | 1.1.0  |
+| 2008-11        |        |           |     |     | Implemented C3-082250, C3-082251, C3-082256, C3-082291, C3-082421, C3-082422, C3-082423, C3-082424.                                                                                                               | 1.1.0                                   | 1.2.0  |
+| 2008-11        |        |           |     |     | v2.0.0 was produced by MCC for Approval in CT#42                                                                                                                                                                  | 1.2.0                                   | 2.0.0  |
+| 2008-12        | TSG#42 |           |     |     | v8.0.0 was produced by MCC                                                                                                                                                                                        | 2.0.0                                   | 8.0.0  |
+| 2009-03        | TSG#43 | CP-090091 | 001 | 1   | Cleanup of editor's notes                                                                                                                                                                                         | 8.0.0                                   | 8.1.0  |
+| 2009-12        | TSG#46 |           |     |     | Automatic upgrade from previous Release                                                                                                                                                                           | 8.1.0                                   | 9.0.0  |
+| 2010-03        | TSG#47 | CP-100092 | 002 | 1   | Miscellaneous correction and alignments                                                                                                                                                                           | 9.0.0                                   | 10.0.0 |
+| 2010-03        | TSG#47 | CP-100092 | 006 | 2   | Modifications to the general sections                                                                                                                                                                             | 9.0.0                                   | 10.0.0 |
+| 2010-03        | TSG#47 | CP-100092 | 013 | 1   | CPM-SMS interworking                                                                                                                                                                                              | 9.0.0                                   | 10.0.0 |
+| 2010-06        | TSG#48 | CP-100324 | 014 |     | Terminology alignment for SMSIP MESSAGE                                                                                                                                                                           | 10.0.0                                  | 10.1.0 |
+| 2010-06        | TSG#48 | CP-100324 | 015 | 1   | Correction of references                                                                                                                                                                                          | 10.0.0                                  | 10.1.0 |
+| 2010-06        | TSG#48 | CP-100324 | 016 | 1   | Handling of Session Information during Chat Session                                                                                                                                                               | 10.0.0                                  | 10.1.0 |
+| 2010-06        | TSG#48 | CP-100324 | 017 |     | Miscellaneous corrections                                                                                                                                                                                         | 10.0.0                                  | 10.1.0 |
+| 2010-06        | TSG#48 | CP-100324 | 018 |     | Missing continuation in 6.1.9.1                                                                                                                                                                                   | 10.0.0                                  | 10.1.0 |
+| 2010-06        | TSG#48 | CP-100324 | 019 |     | MSRP SEND mapping to Short Message during Chat Session                                                                                                                                                            | 10.0.0                                  | 10.1.0 |
+| 2010-09        | TSG#49 | CP-100560 | 020 | 2   | Correcting errors in 3GPP TS 29.311                                                                                                                                                                               | 10.1.0                                  | 10.2.0 |
+| 2010-09        | TSG#49 | CP-100560 | 021 |     | Removal of an editor's note about cpim                                                                                                                                                                            | 10.1.0                                  | 10.2.0 |
+| 2011-03        | TSG#51 | CP-110115 | 022 |     | Minor corrections                                                                                                                                                                                                 | 10.2.0                                  | 10.3.0 |
+| 2011-03        | TSG#51 | CP-110115 | 023 |     | Remove unexplained NOTEs                                                                                                                                                                                          | 10.2.0                                  | 10.3.0 |
+| 2011-09        | TSG#53 | CP-110606 | 026 |     | Correction of SMS delivery creation in IP-SM-GW                                                                                                                                                                   | 10.3.0                                  | 10.4.0 |
+| 2011-09        | TSG#53 | CP-110606 | 029 | 1   | Anonymous SMS                                                                                                                                                                                                     | 10.3.0                                  | 10.4.0 |
+| 2012-09        | TSG#57 |           |     |     | Automatic upgrade from previous Release version 10.4.0                                                                                                                                                            | 10.4.0                                  | 11.0.0 |
+| 2013-06        | TSG#60 | CP-130314 | 033 |     | Correcting an invalid reference                                                                                                                                                                                   | 11.0.0                                  | 11.1.0 |
+| 2014-10        |        |           |     |     | Automatic upgrade from previous Release                                                                                                                                                                           | 11.1.0                                  | 12.0.0 |
+| 2015-03        | TSG#67 | CP-150096 | 038 | 2   | Bugfix: do not send negative-delivery IMDN after sending SIP 4xx/5xx response                                                                                                                                     | 12.0.0                                  | 12.1.0 |
+| 2015-12        |        |           |     |     | Automatic upgrade from previous Release                                                                                                                                                                           | 12.1.0                                  | 13.0.0 |
+| Change history |        |           |     |     |                                                                                                                                                                                                                   |                                         |        |
+| Date           | TSG #  | TSG Doc.  | CR  | Rev | Cat                                                                                                                                                                                                               | Subject/Comment                         | New    |
+| 2017-03        | CT#75  |           |     |     |                                                                                                                                                                                                                   | Automatic upgrade from previous Release | 14.0.0 |
+| 2018-06        | SA#80  | -         | -   | -   |                                                                                                                                                                                                                   | Automatic upgrade from previous Release | 15.0.0 |
+| 2020-07        | SA#88e | -         | -   | -   |                                                                                                                                                                                                                   | Update to Rel-16 version (MCC)          | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29328/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-16/29_series/29328/052543d8c9c0643b05b3ce45c6decca1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7fd65499203ce5bce819b57fcc62072ef22cf54
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/052543d8c9c0643b05b3ce45c6decca1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30f030ac2bcd353c6dc23033861fb04f41628bc43c5f68ff6a7d6b857c704ba8
+size 168501
diff --git a/marked/Rel-16/29_series/29328/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/29_series/29328/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f7082fabac7a1b45097c97755e922a4dbd2710d
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e409a938fa592b08d59cd242c07f87699b61e4cb14aae5f57424fb1a237e0f70
+size 48664
diff --git a/marked/Rel-16/29_series/29328/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29328/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be43590c9213c553f0ed1ccd7e3ff6ebbe2c5940
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e452389c939c338236c794ea0752a4780b1be452abc5d9f26133722f5605ad62
+size 7671
diff --git a/marked/Rel-16/29_series/29328/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/29_series/29328/61a7f401eb46fe99a71f27bc37493f04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdd55c1331c333225e7d1b19f732025be966a220
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/61a7f401eb46fe99a71f27bc37493f04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0ec073aa46448ecb7287ce61e1a83ba6a9c531abaf91bb57ab9091fd36e19a8
+size 140449
diff --git a/marked/Rel-16/29_series/29328/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29328/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aef171bf20f563dba8a15f595d2a47dedab95d9c
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9810247fac8f6e401b6795edf66a0a68ce1f46e4b4049ba7d2ff85d97a172af1
+size 5785
diff --git a/marked/Rel-16/29_series/29328/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-16/29_series/29328/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6b4dd7fc1cdd4696bcd22c0faaae7062cef8301
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41690405ee6cd9a99ddc99fba15dec365ad01f54ebd64a5a998867d87adf9f81
+size 54443
diff --git a/marked/Rel-16/29_series/29328/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/29_series/29328/aeb2a26a07219661191294dba528067a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6ce11051b3c21ec274ad06a98ecbf40ca79fa9cc
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/aeb2a26a07219661191294dba528067a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dea23767218b6ddd1ad78d32e703c35c575bc644c123d97076d08267e72a72ae
+size 133535
diff --git a/marked/Rel-16/29_series/29328/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/29_series/29328/db39acbd11df5eb7e79ab84562fb8f74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..65c17fc51d638cf8c4cd77594892e3aa2761e7ba
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/db39acbd11df5eb7e79ab84562fb8f74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:436dbb214525dd6a1106c47d4e40815a56ba0a308879f4b710d374599aee2f20
+size 120000
diff --git a/marked/Rel-16/29_series/29328/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/29_series/29328/e2c120be98ede6deb60dd341f5a9803b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56d592e2e83aa251a1047aa0a58bd4c85b702c19
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/e2c120be98ede6deb60dd341f5a9803b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bea157fae20d58074e2f131f4bff3aee89c8f112b54aeaef49b1011a61efe37
+size 144547
diff --git a/marked/Rel-16/29_series/29328/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/29_series/29328/fcc757566216206ceddbd6c775e8db02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3cc82b295571fcb0683b22bc24333525435df248
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/fcc757566216206ceddbd6c775e8db02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c63c1d16fca1cad3367e1b5b585a302ba384fc4afb540e730ed190a91cd6fe85
+size 138643
diff --git a/marked/Rel-16/29_series/29328/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-16/29_series/29328/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..727ee22accebd38d278ff3872ba88cb2cd76c1bb
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a5396e00ecf968d4fad1078a8bb1a95e82ec522d2101af17d341ed2d0709ada
+size 83996
diff --git a/marked/Rel-16/29_series/29328/raw.md b/marked/Rel-16/29_series/29328/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb0404d3ca7233b1899856937034f8f56f26f358
--- /dev/null
+++ b/marked/Rel-16/29_series/29328/raw.md
@@ -0,0 +1,2724 @@
+
+
+# 3GPP TS 29.328 V16.2.0 (2020-12)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;  
+Technical Specification Group Core Network and Terminals;  
+IP Multimedia (IM) Subsystem Sh interface;  
+Signalling flows and message contents;  
+(Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring a stylized '5G' with a green signal wave icon above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized font with a red signal wave icon below the 'P'.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                  |    |
+|------------------------------------------------------------------|----|
+| Foreword .....                                                   | 6  |
+| 1 Scope.....                                                     | 7  |
+| 2 References.....                                                | 7  |
+| 3 Definitions, symbols and abbreviations.....                    | 9  |
+| 3.1 Definitions.....                                             | 9  |
+| 3.2 Abbreviations .....                                          | 9  |
+| 4 Main Concept.....                                              | 9  |
+| 5 General Architecture .....                                     | 10 |
+| 5.1 Functional requirements of network entities .....            | 10 |
+| 5.1.1 Functional Requirements of the Application Server .....    | 10 |
+| 5.1.2 Functional requirements of HSS .....                       | 10 |
+| 5.1.3 Functional Requirements of the Presence Network Agent..... | 10 |
+| 5.2 Functional classification of Sh interface procedures.....    | 10 |
+| 6 Procedure Descriptions .....                                   | 10 |
+| 6.1 User data handling procedures .....                          | 11 |
+| 6.1.1 Data read (Sh-Pull) .....                                  | 11 |
+| 6.1.1.1 Detailed behaviour.....                                  | 13 |
+| 6.1.2 Data Update (Sh-Update) .....                              | 16 |
+| 6.1.2.1 Detailed behaviour.....                                  | 18 |
+| 6.1.3 Subscription to notifications (Sh-Subs-Notif) .....        | 21 |
+| 6.1.3.1 Detailed behaviour.....                                  | 23 |
+| 6.1.4 Notifications (Sh-Notif).....                              | 25 |
+| 6.1.4.1 Detailed behaviour.....                                  | 26 |
+| 6.2 AS permissions list.....                                     | 27 |
+| 6.3 Void.....                                                    | 27 |
+| 6.4 Void.....                                                    | 27 |
+| 6.5 User identity to HSS resolution.....                         | 27 |
+| 7 Information element contents.....                              | 29 |
+| 7.1 User Identity.....                                           | 29 |
+| 7.1.1 IMS Public User Identity / Public Service Identity .....   | 29 |
+| 7.1.2 MSISDN .....                                               | 29 |
+| 7.1.3 External Identifier .....                                  | 29 |
+| 7.1A Wildcarded PSI .....                                        | 29 |
+| 7.1B Wildcarded Public User Identity .....                       | 29 |
+| 7.2 Requested Domain .....                                       | 29 |
+| 7.2A Requested Nodes.....                                        | 30 |
+| 7.2B Serving Node Indication.....                                | 30 |
+| 7.3 Requested Data.....                                          | 30 |
+| 7.4 Service Indication.....                                      | 30 |
+| 7.5 Result.....                                                  | 30 |
+| 7.6 Data .....                                                   | 30 |
+| 7.6.1 Repository Data .....                                      | 32 |
+| 7.6.2 IMSPublicIdentity .....                                    | 32 |
+| 7.6.3 IMS User State .....                                       | 33 |
+| 7.6.4 S-CSCF Name .....                                          | 33 |
+| 7.6.5 Initial Filter Criteria.....                               | 33 |
+| 7.6.6 Location Information.....                                  | 34 |
+| 7.6.6.1 Location information for CS.....                         | 34 |
+| 7.6.6.2 Location information for GPRS.....                       | 35 |
+| 7.6.6.3 Location information for EPS.....                        | 35 |
+| 7.6.6.4 Location Information for TWAN .....                      | 36 |
+| 7.6.6.5 Location Information for 5GS .....                       | 36 |
+| 7.6.7 User state .....                                           | 37 |
+
+|                               |                                                                  |           |
+|-------------------------------|------------------------------------------------------------------|-----------|
+| 7.6.8                         | Charging information .....                                       | 37        |
+| 7.6.9                         | MSISDN .....                                                     | 38        |
+| 7.6.9A                        | Extended MSISDN .....                                            | 38        |
+| 7.6.10                        | PSIActivation .....                                              | 38        |
+| 7.6.11                        | DSAI.....                                                        | 38        |
+| 7.6.12                        | Void .....                                                       | 39        |
+| 7.6.13                        | Service Level Trace Information.....                             | 39        |
+| 7.6.14                        | IP address secure binding information .....                      | 39        |
+| 7.6.15                        | Service Priority Level.....                                      | 39        |
+| 7.6.15A                       | Extended Priority .....                                          | 39        |
+| 7.6.16                        | SMSRegistrationInfo .....                                        | 39        |
+| 7.6.17                        | UE reachability for IP .....                                     | 39        |
+| 7.6.18                        | T-ADS Information .....                                          | 40        |
+| 7.6.19                        | Private Identity .....                                           | 40        |
+| 7.6.20                        | STN-SR .....                                                     | 40        |
+| 7.6.21                        | UE SRVCC Capability .....                                        | 40        |
+| 7.6.21A                       | UE 5G SRVCC Capability .....                                     | 40        |
+| 7.6.22                        | CSRN.....                                                        | 40        |
+| 7.6.23                        | Reference Location Information.....                              | 41        |
+| 7.6.24                        | IMSI.....                                                        | 41        |
+| 7.6.25                        | IMSPrivateUserIdentity .....                                     | 41        |
+| 7.6.26                        | IMEISV .....                                                     | 41        |
+| 7.7                           | Subscription request type .....                                  | 41        |
+| 7.8                           | Current Location .....                                           | 41        |
+| 7.9                           | Application Server Identity .....                                | 41        |
+| 7.10                          | Application Server Name .....                                    | 41        |
+| 7.11                          | Requested Identity Set.....                                      | 41        |
+| 7.12                          | Expiry Time.....                                                 | 41        |
+| 7.13                          | Send Data Indication .....                                       | 42        |
+| 7.14                          | DSAI Tag .....                                                   | 42        |
+| 7.15                          | Session-Priority .....                                           | 42        |
+| 7.16                          | One Time Notification .....                                      | 42        |
+| 7.17                          | Repository Data ID.....                                          | 42        |
+| 7.18                          | Pre-paging Supported .....                                       | 42        |
+| 7.19                          | Local Time Zone Indication.....                                  | 42        |
+| 7.20                          | UDR Flags.....                                                   | 42        |
+| 7.21                          | Call Reference Info .....                                        | 43        |
+| 7.22                          | Call Reference Number.....                                       | 43        |
+| 7.23                          | AS-Number .....                                                  | 43        |
+| 8                             | Protocol version identification.....                             | 43        |
+| 9                             | Operational Aspects .....                                        | 43        |
+| <b>Annex A (normative):</b>   | <b>Mapping of Sh operations and terminology to Diameter.....</b> | <b>44</b> |
+| A.1                           | Introduction .....                                               | 44        |
+| A.2                           | Sh message to Diameter command mapping .....                     | 44        |
+| A.3                           | Void.....                                                        | 44        |
+| <b>Annex B (informative):</b> | <b>Message flow .....</b>                                        | <b>45</b> |
+| B.1                           | Message flows.....                                               | 45        |
+| B.1.1                         | Data Update, Registration, Notification Subscription.....        | 45        |
+| <b>Annex C (informative):</b> | <b>UML model of the data downloaded over Sh interface .....</b>  | <b>47</b> |
+| C.1                           | General description .....                                        | 47        |
+| C.2                           | PublicIdentifiers .....                                          | 50        |
+
+|                                                                               |                              |           |
+|-------------------------------------------------------------------------------|------------------------------|-----------|
+| C.3                                                                           | Sh-IMS-Data .....            | 52        |
+| <b>Annex D (normative): XML schema for the Sh interface user profile.....</b> |                              | <b>54</b> |
+| <b>Annex E (informative): T-ADS request handling in the HSS.....</b>          |                              | <b>64</b> |
+| <b>Annex F (normative): Diameter overload control mechanism .....</b>         |                              | <b>72</b> |
+| F.1                                                                           | General .....                | 72        |
+| F.2                                                                           | HSS behaviour.....           | 72        |
+| F.3                                                                           | AS behaviour.....            | 72        |
+| <b>Annex G (Informative): Diameter overload node behaviour .....</b>          |                              | <b>73</b> |
+| G.1                                                                           | Message prioritization ..... | 73        |
+| <b>Annex H (Informative): Data shared among multiple subscribers .....</b>    |                              | <b>73</b> |
+| H.1                                                                           | General .....                | 73        |
+| <b>Annex I (normative): Diameter message priority mechanism .....</b>         |                              | <b>73</b> |
+| I.1                                                                           | General .....                | 73        |
+| I.2                                                                           | Sh/Dh interface.....         | 74        |
+| I.2.1                                                                         | General .....                | 74        |
+| I.2.2                                                                         | AS/OSA SCS behaviour.....    | 74        |
+| I.2.3                                                                         | HSS/SLF behaviour.....       | 74        |
+| I.2.4                                                                         | Interactions .....           | 75        |
+| <b>Annex J (normative): Diameter load control mechanism .....</b>             |                              | <b>75</b> |
+| J.1                                                                           | General .....                | 75        |
+| J.2                                                                           | HSS behaviour.....           | 75        |
+| J.3                                                                           | AS behaviour.....            | 75        |
+| <b>Annex K (informative): Change history.....</b>                             |                              | <b>76</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+This 3GPP Technical Specification (TS) specifies:
+
+1. The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and between the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point.
+2. The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS and the SLF. This interface is referred to as the Dh reference point.
+
+The IP Multimedia (IM) Core Network Subsystem stage 2 is specified in 3GPP TS 23.228 [1] and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in 3GPP TS 24.228 [2].
+
+The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in 3GPP TS 23.218 [4].
+
+This document addresses the signalling flows and message contents for the protocol at the Sh and Dh interface.
+
+This document also addresses how the functionality of Ph interface is accomplished.
+
+The Presence Service Stage 2 description (architecture and functional solution) is specified in 3GPP TS 23.141 [18].
+
+# --- 2 References
+
+- [1] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – Stage 2".
+- [2] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP (Release 5)".
+- [3] 3GPP TS 23.002: "Network architecture".
+- [4] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model".
+- [5] 3GPP TS 29.329: "Sh Interface based on Diameter – Protocol details".
+- [6] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements".
+- [7] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol ; Protocol details".
+- [8] Void.
+- [9] ITU-T recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
+- [10] 3GPP TS 23.018: "Basic Call Handling; Technical realization".
+- [11] 3GPP TS 23.003: "Numbering, Addressing and Identification".
+- [12] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+- [13] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+
+- [14] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2".
+- [15] IETF RFC 2045: "Multipart Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
+- [16] IETF RFC 3261: "SIP: Session Initiation Protocol".
+- [17] IETF RFC 3966: "The tel URI for Telephone Numbers".
+- [18] 3GPP TS 23.141: "Presence Service; Architecture and Functional Description".
+- [19] 3GPP TS 23.012: "Location Management Procedures".
+- [20] ANSI X3.4: "Coded Character Set - 7-bit American Standard Code for Information Interchange"
+- [21] Void
+- [22] 3GPP TS 33.203: "Access Security for IP-based services".
+- [23] IETF RFC 791: "Internet Protocol".
+- [24] IETF RFC 4291: "IP Version 6 Addressing Architecture".
+- [25] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)".
+- [26] 3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol".
+- [27] 3GPP TS 23.008: "Organization of subscriber data".
+- [28] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
+- [29] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2".
+- [30] 3GPP TS 29.118: "SGs interface specification".
+- [31] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol".
+- [32] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
+- [33] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2".
+- [34] 3GPP TS 29.273: "3GPP EPS AAA interfaces".
+- [35] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information".
+- [36] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [37] ETSI ES 283 034: "e4 interface based on the DIAMETER protocol".
+- [38] 3GPP TS 22.153: "Multimedia Priority Service".
+- [39] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" – stage 3.
+- [40] 3GPP TS 29.364: "IP Multimedia Subsystem (IMS) Application Server (AS) service data description for AS interoperability".
+- [41] IETF RFC 5952: "A Recommendation for IPv6 Address Text Representation".
+- [42] IETF RFC 7944: "Diameter Routing Message Priority".
+- [43] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [44] IETF RFC 6733: "Diameter Base Protocol".
+
+- [45] 3GPP TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)".
+- [46] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [47] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
+- [48] 3GPP TS 23.632: "User data interworking, coexistence and migration; Stage 2".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**IP Multimedia session:** IP Multimedia session and IP Multimedia call are treated as equivalent in this specification.
+
+**Transparent data:** Data that is understood syntactically but not semantically by the HSS. It is data that an AS may store in the HSS to support its service logic. One example is data that an AS stores in the HSS, using it as a repository.
+
+**Non-transparent data:** Data that is understood both syntactically and semantically by the HSS.
+
+**AS (Application Server):** a term used to denote either of a SIP Application Server or an OSA Service Capability Server.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|        |                                    |
+|--------|------------------------------------|
+| AS     | Application Server                 |
+| C      | Conditional                        |
+| CSCF   | Call Session Control Function      |
+| CSG    | Closed Subscriber Group            |
+| DRMP   | Diameter Routing Message Priority  |
+| DSCP   | Differentiated Services Code Point |
+| GIBA   | GPRS-IMS-Bundled-Authentication    |
+| HSS    | Home Subscriber Server             |
+| IE     | Information Element                |
+| IP     | Internet Protocol                  |
+| IM     | IP Multimedia                      |
+| IMS    | IP Multimedia Subsystem            |
+| M      | Mandatory                          |
+| O      | Optional                           |
+| SIP    | Session Initiation Protocol        |
+| SLF    | Subscription Locator Function      |
+| S-CSCF | Serving CSCF                       |
+
+# --- 4 Main Concept
+
+This document presents the Sh interface related functional requirements of the communicating entities.
+
+It gives a functional classification of the procedures and describes the procedures and message parameters.
+
+Error handling flows, protocol version identification, etc. procedures are also included.
+
+# --- 5 General Architecture
+
+This clause further specifies the architectural assumptions associated with the Sh reference point, building on 3GPP TS 23.228 [1], 3GPP TS 23.218 [4] and also the Ph reference point building upon 3GPP TS 23.141 [18].
+
+## 5.1 Functional requirements of network entities
+
+### 5.1.1 Functional Requirements of the Application Server
+
+The Application Server may communicate with the HSS over the Sh interface.
+
+For functionality of the Application Server refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4].
+
+### 5.1.2 Functional requirements of HSS
+
+The HSS may communicate with the Application Server over the Sh interface and with the Presence Network Agent over the Ph interface. The functionality of the Ph interface shall be the same as the functionality of the Sh interface.
+
+For functionality of the HSS refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4].
+
+### 5.1.3 Functional Requirements of the Presence Network Agent
+
+The Presence Network Agent may communicate with the HSS over the Ph interface. In this case, all references to an Application Server in this specification apply also to a Presence Network Agent.
+
+## 5.2 Functional classification of Sh interface procedures
+
+Operations on the Sh interface are classified in functional groups:
+
+1. Data handling procedures
+  - The download of data from the HSS to an AS.
+  - The update of data in the HSS.
+2. Subscription/notification procedures
+  - An AS can subscribe to receive notifications from the HSS of changes in data.
+  - The HSS can notify an AS of changes in data for which the AS previously had subscribed.
+
+# --- 6 Procedure Descriptions
+
+In the tables that describe the Information Elements transported by each command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional.
+
+- A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element.
+- A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled.
+  - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER\_MISSING\_AVP. This message shall also include a Failed-AVP AVP containing the
+
+missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element.
+
+- If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER\_AVP\_NOT\_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message.
+- An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver.
+
+When a procedure is required to determine the Public Identity used for an identity lookup in HSS and SLF, the HSS and SLF shall derive the Public Identity from the SIP URI or Tel URI contained in the Public-Identity AVP, if not already in canonical form as per 3GPP TS 23.003 [11], as described below:
+
+- If the Public-Identity AVP contains a SIP URI, the HSS and SLF shall follow rules for conversion of SIP URI into canonical form as specified in IETF RFC 3261 [16] chapter 10.3.
+- If the Public-Identity AVP contains a Tel URI in E.164 format, the HSS and SLF shall remove visual separators and remove all URI parameters.
+
+When a command contains a ServiceData XML element with or without content (i.e. <ServiceData></ ServiceData>), the Service Data element is defined as present in the clauses 6.1 to 6.4.
+
+Unknown permanent failure error codes shall be treated in the same way as DIAMETER\_UNABLE\_TO\_COMPLY. For unknown transient failure error codes the request may be repeated, or handled in the same way as DIAMETER\_UNABLE\_TO\_COMPLY.
+
+## 6.1 User data handling procedures
+
+### 6.1.1 Data read (Sh-Pull)
+
+This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:
+
+- To read transparent and/or non-transparent data for a specified user from the HSS.
+
+This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.1.1 and 6.1.1.2 detail the involved information elements.
+
+Table 6.1.1.1: Sh-Pull
+
+| Information element name                   | Mapping to Diameter AVP    | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Identity (See 7.1)                    | User-Identity              | M    | IMS Public User Identity, Public Service Identity, MSISDN or External Identifier of the user for whom the data is required.<br>See clause 7.1 for the content of this AVP.                                                                                                                                                                                                                                                                                                                                                   |
+| Wildcarded PSI (See 7.1A)                  | Wildcarded-Public-Identity | O    | If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.<br><br>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.<br><br>If this information element is present, Wildcarded Public User Identity shall not be present.                                |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU            | O    | If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.<br><br>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.<br><br>If this information element is present, Wildcarded PSI shall not be present. |
+| Requested data (See 7.3)                   | Data-Reference             | M    | This information element indicates the reference to the requested information. The set of valid reference values are defined in 7.6.                                                                                                                                                                                                                                                                                                                                                                                         |
+| Requested Identity set (See 7.11)          | Identity-Set               | O    | If Data-Reference indicates that IMS Public Identities is the requested data set to be downloaded, this information element should be included and it indicates the information to be downloaded. See clause 7.6.2.                                                                                                                                                                                                                                                                                                          |
+| Requested domain (See 7.2)                 | Requested-Domain           | C    | This information element indicates the domain to which the operation is applicable. Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                                                                                          |
+| Requested nodes (See 7.2A)                 | Requested-Nodes            | O    | This information element indicates the Node Types to which the operation is applicable. Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                                                                                      |
+| Current Location (See 7.8)                 | Current-Location           | C    | This information element indicates whether an active location retrieval has to be initiated or not. It shall be present if Location Information is requested.<br>If this information element takes the value InitiateActiveLocationRetrieval (1) the HSS shall indicate to the MSC/VLR and/or SGSN and/or MME the need to initiate an active location retrieval.<br>Check table 7.6.1 to see when it is applicable.                                                                                                          |
+| Service Indication (See 7.4)               | Service-Indication         | C    | IE that identifies, together with the User Identity included in the User-Identity AVP and Data-Reference, the set of service related transparent data that is being requested.<br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                            |
+| Application Server Identity (See 7.9)      | Origin-Host                | M    | IE that identifies the AS originator of the request and that is used to check the AS permission list.                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Application Server Name (See 7.10)         | Server-Name                | C    | IE that is used, together with the User Identity included in the User-Identity AVP and Data-Reference, as key to identify the filter criteria.<br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                            |
+| DSAI Tag (See 7.14)                        | DSAI-Tag                   | C    | IE that is used, together with the User Identity included in the User-Identity AVP and Data-Reference, as key to identify the instance of Dynamic Service Activation Info (DSAI) requested.<br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                               |
+| Session Priority (see 7.15)                | Session-Priority           | O    | This information element, if present, shall indicate the session's priority to the HSS.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Private Identity (see 7.6.19)              | User-Name                  | C    | Private Identity of the user for whom the data is required.<br><br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Serving Node Indication (See 7.2B)         | Serving-Node-Indication    | O    | This information element shall indicate that only the serving node address/identity associated to the location data is required.<br><br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                                      |
+
+|                                       |                            |   |                                                                                                                                                                                                                                                                               |
+|---------------------------------------|----------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Pre-paging Supported (See 7.18)       | Pre-paging-Supported       | O | This information element shall indicate whether the AS supports pre-paging or not.<br>It indicates by its absence that the AS does not support pre-paging. For details see 3GPP TS 23.018 [10].                                                                               |
+| Local Time Zone Indication (See 7.19) | Local-Time-Zone-Indication | O | This information element shall indicate whether the Local Time Zone is requested and shall indicate whether only the Local Time Zone is required or the Local Time Zone is required together with other location data.<br><br>Check table 7.6.1 to see when it is applicable. |
+| UDR Flags (See 7.20)                  | UDR-Flags                  | O | This Information Element contains a bit mask. See 7.x for the meaning of the bits.                                                                                                                                                                                            |
+| Call-Reference-Info (See 7.21)        | Call-Reference-Info        | O | This Information Element contains a Call Reference Number and the AS-Number. May be present when Data Reference is CSRN. It allows a later retry of the call setup in the context of MTRR. See 3GPP TS 23.292 [33]                                                            |
+
+Table 6.1.1.2: Sh-Pull Resp
+
+| Information element name                   | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                          |
+|--------------------------------------------|-----------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 7.5)                           | Result-Code / Experimental_Result | M    | Result of the request.<br><br>Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).<br><br>Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.                                                             |
+| Wildcarded PSI (See 7.1A)                  | Wildcarded-Public-Identity        | O    | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded PSI was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI.                                                                 |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU                   | O    | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. |
+| Data (See 7.6)                             | User-Data                         | C    | Requested data. This information element shall be present if the requested data exists in the HSS and the AS has permissions to read it.                                                                                                                                                                                                                                                             |
+
+#### 6.1.1.1 Detailed behaviour
+
+The HSS may prioritise the received request message according to priority level received within the Session-Priority AVP.
+
+NOTE 1: Refer to Annex I for HSS procedures associated with the handling of both the Session-Priority AVP and DRMP AVP received in the request message.
+
+The conditions for the inclusion of Requested-Domain and Requested-Node as an additional key to the requested data are described in table 7.6.1. If repository data is requested, Service-Indication shall be present in the request. If initial filter criteria are requested, the Server-Name AVP shall contain the SIP URL of the AS that initiates the request; requests for initial filter criteria are limited to those initial filter criteria which are relevant to the requesting AS. If DSAI information is requested, the DSAI-Tag AVP shall be present.
+
+Upon reception of the Sh-Pull request, the HSS shall, in the following order:
+
+1. In the AS permission list (see clause 6.2) check that the requested user data is allowed to be read (Sh-Pull) by this AS by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference.
+
+If one or more Data References in the request are not allowed to be read, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_READ in the Sh-Pull Response.
+
+2. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Pull Response.
+- 2a. Check if the Private Identity (if received) corresponds to IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH.
+3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity, MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Notif-Eff is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Pull Response.
+- 3a. If data-reference is IPAddressSecureBindingInformation (22) and the User Identity is an IMS Public User Identity that is shared between multiple Private User Identities, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Pull Response.
+4. Check whether or not the data that is requested to be downloaded by the AS is currently being updated by another entity. If there is an update of the data in progress, the HSS may delay the Sh-Pull-Resp message until the update has been completed. The HSS shall ensure that the data returned is not corrupted by this conflict. If HSS is not able to delay the Sh-Pull-Resp message e.g. due to timeout the Experimental-Result-Code shall be set to DIAMETER\_USER\_DATA\_NOT\_AVAILABLE.
+- 4a. If T-ADS Information is requested, the HSS/UDM shall take into account information possibly received from MME, SGSN, and/or AMF during the registration, location update or notification procedure, in order to decide whether MME, SGSN and/or AMF need to be contacted before a response is sent to the AS.
+  - The HSS/UDM shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes. The HSS/UDM shall provide the Access Type and RAT type, if available. The HSS/UDM may also provide the last UE activity time, if available which should include a specific timezone. See Annex E.
+
+NOTE 2: The last UE activity time without a specific timezone can result in IMS receiving unexpected time if timezone is not included, especially for roaming to PLMN with different timezone.
+
+- If all serving nodes need to be contacted, and if at least one serving node does not support T-ADS Data Retrieval or did not successfully answer to the T-ADS request from the HSS, the HSS shall indicate that IMS Voice over PS Sessions support is unknown, i.e., the HSS shall not indicate support, or non-support, of IMS Voice over PS Sessions unless all registered serving nodes have provided indication of their support, non-support, or detached status.
+- If the HSS/UDM knows that one of the registered serving nodes is a Gn/Gp-SGSN, the HSS/UDM shall not contact the MME for T-ADS Data Retrieval, and shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the Gn/Gp-SGSN and/or the AMF. If the Gn/Gp-SGSN needs to be contacted and it does not support T-ADS Data Retrieval, the HSS shall indicate IMS Voice over PS Sessions support is unknown.
+
+NOTE 3: If the UE is registered with both MME and SGSN, and the HSS knows that the SGSN is a Gn/Gp-SGSN, the HSS does not need to know if the MME supports IMS Voice over PS Sessions or not. The HSS can determine that the SGSN registered is a Gn/Gp-SGSN by different ways, e.g. by configuration, or according to the information (e.g. EPS Subscription Data Not Needed Indicator) received in MAP\_UpdateGPRSLocation request.
+
+NOTE 4: If the UE is registered with both MME and SGSN, and the HSS is unable to know that the SGSN is a Gn/Gp-SGSN, the HSS will indicate IMS Voice over PS Sessions support as unknown if the MME does not support T-ADS Data Retrieval or did not successfully answer to the T-ADS request from the HSS, even if the Gn/Gp-SGSN indicated IMS Voice over PS Sessions is supported.
+
+- If the serving node answers successfully to the T-ADS data request, but it does not include any of the T-ADS Information Elements (IMS Voice over PS Sessions Supported, Access Type, RAT Type and Last UE Activity Time), the HSS shall indicate IMS Voice over PS Sessions support is not supported, unless the subscriber is attached in another node that indicates support (if applicable).
+
+- If at least one serving node provided T-ADS data to the HSS, the HSS may also provide the received last UE activity time which should include a specific timezone, Access Type and RAT type. If all serving nodes successfully answer to the T-ADS request from the HSS, the HSS shall provide the most recent IMS Voice over PS Sessions support indication as indicated by the serving nodes.
+
+NOTE 5: The last UE activity time without a specific timezone can result in IMS receiving unexpected time if timezone is not included, especially for roaming to PLMN with different timezone.
+
+- 4b. If CSRN is requested but roaming number retrieval from the MSC/VLR fails, the HSS shall include an empty CSRN element in the xml document returned to the AS. In addition, if MTRR is applicable (see 3GPP TS 23.018 [10]), the HSS shall set an MTRR-Indication in the xml document. See 3GPP TS 23.292 [33].
+
+- 5. The HSS shall include the data pertinent to the requested Data Reference in the User-Data AVP. The HSS shall set the Result-Code to DIAMETER\_SUCCESS. This includes cases where the data is not available to the HSS. The pertinent data included shall refer to the received IMPU/MSISDN/External Identifier and Private Identity (if present).
+
+NOTE 6: Data referred to a Private Identity (e.g. IMS Private User Identity) implies that only the data (e.g. Location Information) specific for that Private Identity is included, regardless of the type of User Identity received (e.g. IMS Public User Identity shared by multiple IMS Private User Identities).
+
+If both the AS and the HSS have determined via mutual feature evaluation to not support the Notif-Eff feature and in the case that requested data is not available to the HSS, the HSS shall not include the User-Data AVP in the Sh-Pull Response.
+
+If both the AS and the HSS support the Notif-Eff feature, the HSS shall include the data pertinent to all the requested Data References, Service Indications and Identity Sets in the User-Data AVP. The following applies:
+
+- If none of the requested data is available to the HSS, the HSS shall not include the User-Data AVP in the Sh-Pull Response.
+- If some of the requested data is not available to the HSS, it shall be indicated as follows:
+  - Empty repository data shall be indicated with the RepositoryData element that contains a Service Indication and a Sequence Number but does not contain a ServiceData element (i.e. ServiceData is not present).
+  - Unavailable Public Identifiers shall be indicated with an empty PublicIdentifiers element.
+  - Unavailable location information shall be indicated by an empty CSLocationInformation and/or an empty PSLocationInformation element and/or an empty EPSLocationInformation element.
+  - Unavailable CS-UserState shall be indicated by a missing CSUserState element.
+  - Unavailable PS-UserState shall be indicated by a missing PSUserState element.
+  - Unavailable EPS-UserState shall be indicated by a missing EPSUserState element.
+  - Unavailable elements of Sh IMS Data shall be indicated as follows:
+    - An unavailable S-CSCF name shall be indicated with empty SCSCFName element.
+    - An unavailable IP Address Secure Binding Information shall be indicated with empty IPv4address element or empty IPv6prefix element.
+    - If all iFCs for the user that are relevant for the AS are unavailable it shall be indicated with empty IFCs element.
+    - Not available UE SRVCC capability shall be indicated with missing UE-SRVCC-Capability element.
+    - Not available UE 5G SRVCC capability shall be indicated with missing UE-5G-SRVCC-Capability element.
+    - Not available STN-SR shall be indicated with empty STN-SR element.
+
+NOTE 7: If the HSS supports interworking with UDM, the HSS can also take into account the availability of the STN-SR from the UDM as described in 3GPP TS 23.632 [48].
+
+- Not available CSRN shall be indicated with empty CSRN element.
+- Not available IMSI shall be indicated with empty IMSI element.
+
+NOTE 8: If there is no available STN-SR in the HSS, it indicates that the user is not SRVCC subscribed and if there is no available STN-SR from the UDM, it indicates that the user is not 5G-SRVCC subscribed, as described in 3GPP TS 23.008 [27] and 3GPP TS 23.632 [48].
+
+If there is an error in any of the above steps, then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7] for an explanation of the error codes).
+
+If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or empty mandatory data elements, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. Result-Code DIAMETER\_SUCCESS is used also if the requested data does not exist in the HSS i.e. when the HSS is indicating valid empty data elements.
+
+### 6.1.2 Data Update (Sh-Update)
+
+This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:
+
+- To allow the AS to update the transparent (repository) data stored at the HSS for each IMS Public User Identity (for Public User Identities matching a Wildcarded Public User Identity, the transparent data shall be stored per Wildcarded Public User Identity, and not for each specific Public User Identity matching that Wildcarded Public User Identity) or Public Service Identity (for Public Service Identities matching a Wildcarded PSI, the transparent data shall be stored per Wildcarded PSI, and not for each specific Public Service Identity matching that Wildcarded PSI).
+- To allow the AS to update the PSI Activation State of a distinct Public Service Identity in the HSS.
+- To allow the AS to update the Dynamic Service Activation Info stored at the HSS.
+- To allow the AS to update the Short Message Service Registration Info stored at the HSS.
+- To allow the AS to update the STN-SR stored at the HSS and/or the STN-SR stored at the UDM.
+
+NOTE: In accordance with 3GPP TS 23.632 [48], if there is only an STN-SR available in the UDM, the STN-SR in the UDM is updated. If there is only an STN-SR available in the HSS, the STN-SR in the HSS is updated. If there is an STN-SR available in the UDM and in the HSS, the STN-SR in the UDM and the HSS are updated.
+
+This procedure is mapped to the commands Profile-Update-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.2.1 and 6.1.2.2 detail the involved information elements.
+
+Table 6.1.2.1: Sh-Update
+
+| Information element name                   | Mapping to Diameter AVP    | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Identity (See 7.1)                    | User-Identity              | M    | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which data is updated.<br>See clause 7.1 for the content of this AVP.                                                                                                                                                                                                                                                                                                                                                               |
+| Wildcarded PSI (See 7.1A)                  | Wildcarded-Public-Identity | O    | If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.<br><br>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.<br><br>If this information element is present, Wildcarded Public User Identity shall not be present.                                |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU            | O    | If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.<br><br>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.<br><br>If this information element is present, Wildcarded PSI shall not be present. |
+| Requested data (See 7.3)                   | Data-Reference             | M    | This information element includes the reference to the data on which updates are required (possible values of the Data Reference are defined in Table 7.6.1).                                                                                                                                                                                                                                                                                                                                                                |
+| Data (See 7.6)                             | User-Data                  | M    | Updated data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Application Server Identity (See 7.9)      | Origin-Host                | M    | IE that identifies the AS originator of the request and that is used to check the AS permission list.                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| Private identity (see 7.6.19)              | User-Name                  | C    | Private Identity of the user for whom the data is required.<br><br>Check table 7.6.1 to see when it is applicable.                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+**Table 6.1.2.2: Sh-Update Resp**
+
+| Information element name                   | Mapping to Diameter AVP              | Cat. | Description                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------------------------|--------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result<br>(See 7.5)                        | Result-Code /<br>Experimental-Result | M    | Result of the update of data in the HSS.<br><br>Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).<br><br>Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.  |
+| Wildcarded PSI<br>(See 7.1A)               | Wildcarded-Public-Identity           | O    | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded-PSI was not included in the request, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI.                                                                 |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU                      | O    | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. |
+| Repository Data ID (See 7.17)              | Repository-Data-ID                   | O    | If the HSS and the AS support the Update-Eff feature or the Update-Eff-Enhance feature and if a Sh-Update Request with multiple repository data fails, this information element shall include the service indication and the sequence number of the repository data instance that has generated the error.                                                  |
+| Requested data<br>(See 7.3)                | Data-Reference                       | O    | If the HSS and the AS support the Update-Eff-Enhance feature and if an Sh-Update Request with multiple data references fails, this information element shall include the Data reference for the data instance that has generated the error.                                                                                                                 |
+
+#### 6.1.2.1 Detailed behaviour
+
+Within the Sh-Update Request, the keys to determine the updated data are part of the information element Data (See 7.6). When data in the repository is updated (i.e. added, modified or removed) Service-Indication and Sequence-Number are also sent as part of the information element Data.
+
+Newly added transparent data shall be associated with a Sequence Number of 0 in the Sh-Update Request. Sequence Number value 0 is reserved exclusively for indication of newly added transparent data.
+
+Modified and removed transparent data shall be associated within the Sh-Update Request with a Sequence Number of  $n+1$  where  $n$  is the original Sequence Number associated with the transparent data before modification or removal. If  $n$  equals 65535, then the next modification or deletion of that transparent data shall be associated with a Sequence Number of 1.
+
+Upon reception of the Sh-Update request, the HSS shall, in the following order:
+
+1. In the AS permission list (see clause 6.2) check that the data that is requested to be updated (Sh-Update) by this AS, is allowed to be updated by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference.
+  - If the data is not allowed to be updated, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_MODIFIED in the Sh-Update Response.
+2. Check that the User Identity in the request exists in the HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Update Response.
+- 2a. Check if the Private User Identity (if received) corresponds to the IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH.
+3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity or MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Update-Eff-Enhance
+
+is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response.
+
+4. If Data-Reference is PSIActivation (18), then the HSS shall check that the User Identity contains a distinct Public Service Identity. If it does, then the HSS shall update the corresponding PSI Activation State and return the Result-Code AVP set to DIAMETER\_SUCCESS. If it does not, then the Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response.
+
+The change of a Public Service Identity from ACTIVE to INACTIVE shall trigger the network initiated deregistration of the Public Service Identity in the HSS.
+
+- 4a. If Data-Reference is DSAI (19), check whether or not, for the Public Identity, there is an instance of DSAI matching the DSAI-Tag contained in the Sh-Update command. If so, then the HSS shall update the DSAI value and return the Result-Code AVP set to DIAMETER\_SUCCESS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_DSAI\_NOT\_AVAILABLE.
+
+The changes of DSAI value shall trigger the procedures described in clause 7.14 in order to determine which initial filter criteria should be masked or unmasked. If these procedures change the set of unmasked initial filter criteria, the HSS should behave as if the initial filter criteria had been administratively changed, which implies e.g. sending Sh-Notif or Cx-Update\_Subscr\_Data messages (see 3GPP TS 29.228 [6]).
+
+- 4b. If Data-Reference is SMSRegistrationInfo (24), check whether or not, for the IMS Public User Identity or MSISDN or External Identifier, IP-SM-GW number element contained in the Sh-Update command is empty. If it is empty, then the HSS shall delete the stored registered IP-SM-GW number (if any) and the stored registered IP-SM-GW Diameter Identity (if any), and return the Result-Code AVP set to DIAMETER\_SUCCESS. A preconfigured IP-SM-GW number and preconfigured IP-SM-GW Diameter Identity shall not be deleted.
+
+If it is not empty, the HSS shall store/update the registered IP-SM-GW number and, if S6c is supported, the IP-SM-GW Diameter Identity as received within the Origin-Host and Origin-Realm AVPs, and return the Result-Code AVP set to DIAMETER\_SUCCESS. A preconfigured IP-SM-GW number and preconfigured IP-SM-GW Diameter Identity shall not be overwritten.
+
+The Service Centre Address in the HSS shall not be updated by this operation.
+
+NOTE 1: The address of the Short Message Service Centre as defined in 7.6.16 is only applicable to Sh-Pull operation.
+
+- 4c. If the Data-Reference indicates that repository data is present, and if the HSS and the AS supports the Update- Eff feature, check whether there are multiple repository data instances. If so, then repeat the steps 5 and 6 below for each instance of repository data ensuring that no repository data is changed until the checks done in the steps 5 and 6 have been successful for all the repository data instances.
+
+- 4d. If the Data-Reference is STN-SR (27) and if the STN-SR is different from the one previously stored or provisioned in the HSS, the HSS shall overwrite the STN-SR. If the Data-Reference is STN-SR (27), the HSS supports interworking with the UDM (see in 3GPP TS 23.632 [48]), and if the STN-SR is different from the one previously stored or provisioned in the UDM, the UDM shall overwrite the STN-SR. If the Data-Reference is STN-SR (27), and if there is no stored STN-SR in the HSS and there is no stored STN-SR in the UDM, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Update Response.
+
+NOTE 2: If there is no stored STN-SR in the HSS, it indicates that the user is not SRVCC subscribed and if there is no stored STN-SR in the UDM, it indicates that the user is not 5G-SRVCC subscribed, as described in 3GPP TS 23.008 [27].
+
+5. Check whether or not the data that is requested to be updated by the AS, as identified by the Service-Indication, is currently being updated by another entity. If there is an update of the data in progress, Experimental-Result shall be set to DIAMETER\_PRIOR\_UPDATE\_IN\_PROGRESS in the Sh-Update Response.
+6. Check whether or not there is any repository data stored at the HSS already for the specified Service-Indication and the associated IMS Public User Identity (or group if the IMS Public User Identity is alias) or Public Service Identity.
+  - If repository data identified by the Service-Indication is stored at the HSS for the specified IMS Public User Identity, IMS Public User Identity group or Public Service Identity, check the following premises:
+
+1. Sequence\_Number\_in\_Sh\_Update is not equal to 0
+2. (Sequence\_Number\_in\_Sh\_Update - 1) is equal to (Sequence\_Number\_In\_HSS modulo 65535)
+  - If either of the above premises is false then Experimental-Result shall be set to DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC in the Sh-Update Response.
+  - If both of the above premises are true, then check whether or not Service Data is received within the Sh-Update Req.
+    - If Service Data element is present in the Sh-Update Req, check whether or not the size of the data is greater than that which the HSS is prepared to accept.
+      - If there is more data than the HSS is prepared to accept then Experimental-Result shall be set to DIAMETER\_ERROR\_TOO\_MUCH\_DATA and the new data shall be discarded.
+      - If the HSS is prepared to accept the data, then the repository data stored at the HSS shall be updated with the repository data sent in the Sh-Update Req and the Sequence Number associated with that repository data shall be updated with that sent in the Sh-Update Req. This triggers the sending of Sh-Notif messages to any other ASs that are subscribed to Notifications for updates to the service data for that IMS Public User Identity or Public Service Identity. This also triggers the sending of Sh-Notif messages for an alias of that IMS Public User Identity to any AS that is subscribed to Notifications for updates to the service data for that alias of the received IMS Public User Identity (see clause 6.1.4).
+    - If Service Data element is not present in the Sh-Update Req, the data stored in the repository at the HSS shall be removed, and as a consequence the Service Indication and the Sequence Number associated with the removed data shall also be removed. This triggers the sending of Sh-Notif messages with that Service Indication and Sequence Number to be deleted but with an absent Service Data element, to any other ASs that are subscribed to Notifications for updates to the service data for that IMS Public User Identity or Public Service identity (see 6.1.4). After sending Sh-Notif messages, the subscriptions to Notifications for the removed Repository Data shall be deleted.
+  - If repository data identified by the Service-Indication is not stored for the IMS Public User Identity, IMS Public User Identity group or Public Service Identity i.e. the Sh-Update Req intends to create a new repository data, check whether or not the Sequence Number in the Sh-Update Req is 0.
+    - If the sequence number is not set to 0, Experimental-Result shall be set to DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC
+    - If the sequence number is set to 0 check whether Service Data is included within the Sh-Update Req.
+      - If Service Data is not present in the Sh-Update Req, then Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED and the operation shall be ignored by the HSS.
+      - If Service Data element is present in the Sh-Update Req, check whether or not the size of the data is greater than that which the HSS is prepared to accept.
+        - If there is more data than the HSS is prepared to accept then Experimental-Result shall be set to DIAMETER\_ERROR\_TOO\_MUCH\_DATA and the new data shall be discarded.
+        - If the HSS is prepared to accept the data included in the Sh-Update Req, then the data shall be stored in the data repository in the HSS.
+
+If the HSS receives a request to update data other than Repository Data while a previous update request of the same data for the same user identity is still in progress, the HSS should stop processing the later request and set the Experimental-Result-Code to DIAMETER\_PRIOR\_UPDATE\_IN\_PROGRESS.
+
+NOTE 3: If the HSS receives a request to update data other than Repository Data while a previous update request of the same data for the same user identity is still in progress, it identifies either an AS or network misbehavior. If the HSS processed those requests it could cause a network unexpected behaviour.
+
+If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7] for an explanation of the error codes).
+
+If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+If the HSS and the AS support the Update-Eff feature, the Sh Update is successful only if it is successful for the update of all the repository data instances in the request. Otherwise the HSS shall keep or restore all the stored repository data as they were before receiving the Sh Update request. If the error occurs during the steps 5 or 6 and if there were several repository data instances in the request, the Sh Update response shall contain a Repository Data ID indicating the service indication and the sequence number of (one of) the repository data instance(s) for which an error occurred.
+
+If the HSS and the AS support the Update-Eff-Enhance feature, the Sh Update is successful only if it is successful for the update of all the data instances in the request. Otherwise the HSS shall keep or restore all the stored data as they were before receiving the Sh Update request. If an error occurs during the steps 5 or 6 with any of the data instance in the request, the Sh Update response shall contain the corresponding Data Reference indicating the first data instance for which an error occurred. If there were several repository data instances in the request, the HSS shall behave the same as specified for Update-Eff feature.
+
+Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS.
+
+NOTE 4: When an AS receives DIAMETER\_ERROR\_TRANSPARENT\_DATA\_OUT\_OF\_SYNC the AS may attempt to resolve the inconsistency between the version of the repository data that it holds and that stored at the HSS. It may execute a Sh-Pull to retrieve the current version of the data from the HSS or it may wait to receive a subsequent Sh-Notif message from the HSS for the affected repository data.
+
+### 6.1.3 Subscription to notifications (Sh-Subs-Notif)
+
+This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:
+
+- To subscribe to Notifications for when particular transparent and/or non-transparent data for a specified IMS Public User Identity or Public Service Identity is updated, from the HSS.
+- Optionally to request the user data from the HSS in the same operation.
+
+This procedure is mapped to the commands Subscribe-Notifications-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.3.1 and 6.1.3.2 detail the information elements involved.
+
+Table 6.1.3.1: Sh-Subs-Notif
+
+| Information element name                              | Mapping to Diameter AVP    | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|-------------------------------------------------------|----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Identity (See 7.1)                               | User-Identity              | M    | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which notifications of data changes are requested. See clause 7.1 for the content of this AVP.                                                                                                                                                                                                                                                                                                                                             |
+| Wildcarded PSI (See 7.1A)                             | Wildcarded-Public-Identity | O    | <p>If the request refers to a Wildcarded PSI, the AS may include the corresponding Wildcarded PSI in this information element.</p> <p>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.</p> <p>If this information element is present, Wildcarded Public User Identity shall not be present.</p>                                |
+| Wildcarded Public User Identity (See 7.1B)            | Wildcarded-IMPU            | O    | <p>If the request refers to a Wildcarded Public User Identity, the AS may include the corresponding Wildcarded Public User Identity in this information element.</p> <p>If this information element is present, it should be used by the HSS to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.</p> <p>If this information element is present, Wildcarded PSI shall not be present.</p> |
+| Requested Data (See 7.3)                              | Data-Reference             | M    | This information element includes the reference to the data on which notifications of change are required (valid reference values are defined in 7.6).                                                                                                                                                                                                                                                                                                                                                                              |
+| Subscription request type (See 7.7)                   | Subs-Req-Type              | M    | This information element indicates the action requested on subscription to notifications.                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Send Data Indication (See 7.13)                       | Send-Data-Indication       | O    | <p>This information element requests that the data is sent in the response.</p> <p>Send Data Indication is not applicable to one time subscriptions to UE reachability for IP.</p>                                                                                                                                                                                                                                                                                                                                                  |
+| Service Indication (See 7.4)                          | Service-Indication         | C    | <p>IE that identifies, together with the User Identity and Data-Reference, the set of service related transparent data for which notifications of changes are requested.</p> <p>Check table 7.6.1 to see when it is applicable.</p>                                                                                                                                                                                                                                                                                                 |
+| Application Server Identity (See 7.9)                 | Origin-Host                | M    | IE that identifies the AS originator of the request and that is used to check the AS permission list.                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| Application Server Name (See 7.10)                    | Server-Name                | C    | <p>IE that is used, together with the User Identity and Data-Reference, as key to identify the filter criteria.</p> <p>Check table 7.6.1 to see when it is applicable.</p>                                                                                                                                                                                                                                                                                                                                                          |
+| Expiry Time (See 7.12)                                | Expiry-Time                | O    | Gives the absolute time requested at which the subscription expires.                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Dynamic Service Activation Information Tag (see 7.14) | DSAI-Tag                   | C    | <p>IE that identifies, together with the User Identity and Data-Reference, the instance of Dynamic Service Activation Info (DSAI) requested.</p> <p>Check table 7.6.1 to see when it is applicable.</p>                                                                                                                                                                                                                                                                                                                             |
+| Requested Identity set (See 7.11)                     | Identity-Set               | C    | <p>If Data-Reference indicates that IMS Public Identities is the requested data set, this information element shall be included and it indicates the information to be subscribed to (and optionally to be downloaded).</p> <p>See clause 7.6.2.</p>                                                                                                                                                                                                                                                                                |
+| One time notification (See 7.16)                      | One-Time-Notification      | C    | <p>This information element indicates if subscription shall be ended by the HSS after sending the first notification.</p> <p>This IE shall be present for UE reachability for IP.</p>                                                                                                                                                                                                                                                                                                                                               |
+| Private identity (see 7.6.19)                         | User-Name                  | O    | <p>Private Identity of the user for whom the data is required.</p> <p>Check table 7.6.1 to see when it is applicable.</p>                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+Table 6.1.3.2: Sh-Subs-Notif Resp
+
+| Information element name                   | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                 |
+|--------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Expiry Time (See 7.12)                     | Expiry-Time                       | O    | Acknowledges the absolute time at which the subscription expires.                                                                                                                                                                                                                                                                                           |
+| Data (See 7.6)                             | User-Data                         | O    | Current values of the data for which notifications have been requested.<br><br>It should be present if the Send-Data-Indication AVP is set to value USER_DATA_REQUESTED.                                                                                                                                                                                    |
+| Wildcarded PSI (See 7.1A)                  | Wildcarded-Public-Identity        | O    | If the request refers to a specific PSI matching a Wildcarded PSI and the Wildcarded PSI was not included in the request and is not included in the User-Data AVP, the HSS may include the corresponding Wildcarded PSI in this information element. This information may be used by the AS to identify the affected Wildcarded PSI.                        |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU                   | O    | If the request refers to a Public User Identity matching a Wildcarded Public User Identity and the Wildcarded-IMPU AVP was not included in the request, the HSS may include the corresponding Wildcarded Public User Identity in this information element. This information may be used by the AS to identify the affected Wildcarded Public User Identity. |
+| Result (See 7.5)                           | Result-Code / Experimental-Result | M    | Result of the request.<br><br>Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).<br><br>Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.                    |
+
+#### 6.1.3.1 Detailed behaviour
+
+The HSS shall take note of the subscription request on the data identified by User Identity and Data-Reference. If notifications on changes of repository data are requested, Service-Indication shall be present in the request. If notifications on changes of filter criteria are requested, the Server-Name AVP shall be used as key to the filter criteria. If the request contains a specific Public Service Identity matching a Wildcarded PSI, the HSS shall interpret that the subscription refers to the information associated to the Wildcarded PSI. The Server-Name AVP shall contain the SIP URL of the AS sending the request. If notifications on changes of DSAI are requested, the DSAI-Tag AVP shall be used as key of the DSAI whose changes are to be monitored.
+
+Upon reception of the Sh-Subs-Notif request, the HSS shall, in the following order (if there is an error in any of the following steps the HSS shall stop processing and return the corresponding error code, see 3GPP TS 29.329 [5] and 3GPP TS 29.229 [7]), process the hereafter steps that, unless otherwise stated, apply both for the Subscription request type information element indicating the request is to subscribe or to unsubscribe:
+
+1. In the AS permission list (see clause 6.2) the HSS shall check that the AS is allowed to subscribe to notifications (Sh-Subs-Notif) for the requested data by checking the combination of the identity of the AS sending the request (identified by the Origin-Host AVP) and the supplied Data-Reference.
+  - If this AS does not have Sh-Subs-Notif permission for the data referenced, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_NOTIFIED in the Sh-Subs-Notif Response.
+2. The HSS shall check that the User Identity in the request exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Sh-Subs-Notif Response.
+- 2a. Check if the Private Identity (if received) corresponds to IMPU/MSISDN/External Identifier received in User-Identity. If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH.
+3. If the type of the User Identity (i.e. IMS Public User Identity or Public Service Identity or MSISDN or External Identifier) does not apply according to Table 7.6.1 as access key for the Data-Reference (if Notif-Eff is in use: for all the Data-References) indicated in the request, Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Sh-Subs-Notif Response.
+
+- 3a. If Data-Reference is DSAI (19), check whether or not, for the Public Identity, there is an instance of DSAI matching the DSAI-Tag contained in the Sh-Subs-Notif command. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_DSAI\_NOT\_AVAILABLE.
+4. If the Sh-Subs-Notif Request contains an Expiry Time, the HSS should also include in the Sh-Subs-Notif Response an Expiry Time IE with the absolute time at which the subscription expires in the case of a successful subscription. This time may be earlier than the requested expiry time. If the HSS includes this IE, then no notification shall be sent to the AS after the expiration time. If the HSS receives a Sh-Subs-Notif Request without the Expiry Time IE, the HSS should treat it as a request for an unlimited subscription.
+
+If the HSS does not include this IE in the response, that indicates an unlimited subscription.
+
+If a subsequent request is received by the HSS where the Expiry Time IE is present but different from what the HSS has previously stored, the HSS should replace the stored expiration time with what was received in the request.
+
+5. If Data-Reference is RepositoryData(0) and the transparent data associated with the Service Indication does not exist in the HSS (i.e. Service Data is not present), then Experimental-Result shall be set to DIAMETER\_ERROR\_SUBS\_DATA\_ABSENT.
+6. If the Subscription request type information element indicates that this is a request to subscribe, the HSS shall associate the Application Server Identity with the list of entities that need to be notified when the data identified by the request is modified and set the Result-Code to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If the Subscription request type information element indicates that this is a request to unsubscribe, the HSS shall remove the association of the Application Server Identity with the same list. In this last case, the Result-Code shall be set to DIAMETER\_SUCCESS if the operation is successful or if the Application Server Identity was not present in the list.
+7. If the HSS and AS supports the Notif-Eff feature and if multiple Data-Reference AVPs occur in the Sh-Subs-Notif Request, each Data-Reference shall be treated as a request to establish a separate notification request. When multiple notification requests are requested, and all of them succeed, the HSS shall set the Result-Code to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error indication and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request.
+8. If the HSS and the AS supports the Notif-Eff feature and if multiple Service-Indication AVPs occur in the Sh-Subs-Notif Request, each Service-Indication shall be treated as a request to establish a separate notification request for change of Transparent data. When multiple notification requests are requested, and all of them are successful, the HSS shall return the Result-Code set to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error value and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request.
+- 8a. If the HSS and the AS supports the Notif-Eff feature and if different Identity-Set AVPs occur in the Sh-Subs-Notif Request, each Identity-Set shall be treated as a request to establish a separate notification request. When multiple notification requests are requested, and all of them are successful, the HSS shall return the Result-Code set to DIAMETER\_SUCCESS in the Sh-Subs-Notify response. If one of them is unsuccessful, the HSS shall return the Result code with the relevant Diameter error value and come back to the situation regarding to subscriptions as before the reception of the Sh-Subs-Notif Request.
+9. If the Send Data Indication information element is present in the request and the HSS supports the return of the User-Data in this request, check whether or not the data that is requested to be downloaded by the AS is currently being updated by another entity. If there is an update of the data in progress, the HSS may delay the response until the update has been completed. The HSS shall ensure that the data returned is not corrupted by this conflict.
+10. If the Send Data Indication information element is present in the request, the HSS should include the data pertinent to the requested Data Reference in the User-Data AVP and if the HSS supports the Notif-Eff feature, the HSS should include the data pertinent to all the requested Data References in the User-Data AVP. The HSS shall set the Result-Code to DIAMETER\_SUCCESS. This includes cases where the data is not available to the HSS and an empty tag is included as follows.
+  - Unavailable elements of Sh IMS Data shall be indicated as follows.
+    - An unavailable S-CSCF name shall be indicated with empty SCSCFName element.
+
+- If all iFCs for the user that are relevant for the AS are unavailable it shall be indicated with empty IFCs element.
+- Similarly for PSI activation information.
+
+If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+### 6.1.4 Notifications (Sh-Notif)
+
+This procedure is used between the HSS and the AS. The procedure is invoked by the HSS and is used:
+
+- To inform the AS of changes in transparent and/or non-transparent data to which the AS has previously subscribed to receive Notifications for, using Sh-Subs-Notif (see 6.1.3).
+
+This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in 3GPP TS 29.329 [5]. Tables 6.1.4.1 and 6.1.4.2 detail the involved information elements.
+
+**Table 6.1.4.1: Sh-Notif**
+
+| Information element name                   | Mapping to Diameter AVP    | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Identity (See 7.1)                    | User-Identity              | M    | IMS Public User Identity or Public Service Identity or MSISDN or External Identifier for which data has changed.<br>If the request refers to a Wildcarded PSI, the HSS may include any PSI matching the corresponding Wildcarded PSI in this information element. The AS shall find the corresponding Wildcarded PSI with this information. See clause 7.1 for the content of this AVP.                                                                                                                                                                    |
+| Wildcarded PSI (See 7.1A)                  | Wildcarded-Public-Identity | O    | If the request refers to a Wildcarded PSI, the HSS shall include the corresponding Wildcarded PSI in this information element.<br><br>If this information element is present, it shall be used by the AS instead of the User Identity to identify the identity affected by the request. If that is the case, the terms User Identity or Public Service Identity in the detailed behaviour refer to the Wildcarded PSI.<br><br>If this information element is present, Wildcarded Public User Identity shall not be present.                                |
+| Wildcarded Public User Identity (See 7.1B) | Wildcarded-IMPU            | O    | If the request refers to a Wildcarded Public User Identity, the HSS shall include the corresponding Wildcarded Public User Identity in this information element.<br><br>If this information element is present, it shall be used by the AS instead of the User Identity to identify the identity affected by the request. If that is the case, the terms User Identity or Public User Identity in the detailed behaviour refer to the Wildcarded Public User Identity.<br><br>If this information element is present, Wildcarded PSI shall not be present. |
+| Data (See 7.6)                             | User-Data                  | M    | Changed data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| Private Identity (see 7.6.19)              | User-Name                  | C    | Private Identity of the user for whom the data is required.<br>This information element shall be present only if the associated request included the Private Identity.                                                                                                                                                                                                                                                                                                                                                                                     |
+
+**Table 6.1.4.2: Sh-Notif Resp**
+
+| Information element name | Mapping to Diameter AVP              | Cat. | Description                                                                                                                                                                                                                                                                                                                                     |
+|--------------------------|--------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result<br>(See 7.5)      | Result-Code /<br>Experimental-Result | M    | <p>Result of the request.</p> <p>Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [44]).</p> <p>Experimental-Result AVP shall be used for Sh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.</p> |
+
+#### 6.1.4.1 Detailed behaviour
+
+The keys to the updated data are part of the information element User-Data AVP. When data repository is updated Service-Indication and Sequence Number shall also be part of the information element User-Data.
+
+Since authentication pending is a transient state of normally very short duration, notification of an IMS user's state change, to and from the authentication pending state shall not be sent to Application Servers, when the previous state before authentication pending and next state after authentication pending are the same. If the states are different before the authentication pending state is entered and after the authentication pending state is left then notification is sent to the AS of this new state.
+
+If the HSS and AS supports the Notif-Eff feature and if multiple subscriptions to notifications are associated with a Public User Identity, the HSS may combine the notifications for multiple Data References and Service Indications into a single notification message.
+
+If the HSS supports the Update-Eff and Notif-Eff features, the HSS may generate only one notification message to be sent to the AS(s) supporting the Notif-eff feature, grouping the data changes notifications according to the subscribed notifications and the resulting successful achievement of a Sh-Update procedure with multiple repository data instances, from an AS that supports the Update-Eff feature. This notification message may also include other notifications as described with the Notif-Eff feature.
+
+Removal of the subscribed data is indicated with the content of User-Data AVP. The content shall be compliant with the XML-schema defined in Annex D. Removed repository data shall be indicated with RepositoryData element that does not contain ServiceData element. Removed S-CSCF name shall be indicated with empty SCSCFName element. Removed IP Address Secure Binding Information shall be indicated with empty IPv4Addres, or IPv6Prefix and/ or IPv6 interface element respectively. If all iFCs for the user that are relevant for the AS have been removed it shall be indicated with empty IFCs element.
+
+Removal of Public Identity for which the AS has any active subscription shall be indicated in the DeletedIdentities element.
+
+If One-Time-Notification AVP was included by the AS in Sh-Subs-Notif, the HSS shall remove the related subscription information after sending Sh-Notif, i.e. no subsequent notifications shall be sent to AS.
+
+Notifications shall include the data updated for the received IMPU/MSISDN/External Identifier and Private Identity (if present).
+
+**NOTE:** Data referred to a Private Identity (e.g. IMS Private User Identity) implies that only the data (e.g. UE reachability) specific for that Private Identity is included, regardless of the type of User Identity received (e.g. IMS Public User Identity shared by multiple IMS Private User Identities).
+
+Table 6.1.4.1 details the valid result codes that the AS can return in the response.
+
+**Table 6.1.4.1.1: Sh-Notif response valid result codes**
+
+| Result-Code AVP value                   | Condition                                                                                                                                             |
+|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| DIAMETER_SUCCESS                        | The request succeeded.                                                                                                                                |
+| DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED | The request failed. The AS informs the HSS that the received user information contained information, which was not recognized or supported by the AS. |
+| DIAMETER_ERROR_USER_UNKNOWN             | The request failed because the Public Identity or MSISDN or External Identifier is not found in the AS.                                               |
+| DIAMETER_ERROR_TOO_MUCH_DATA            | The request failed. The AS informs the HSS that it tried to push too much data into the AS.                                                           |
+| DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA  | The request failed. The AS informs the HSS that the notification refers to information to which the AS is not subscribed.                             |
+| DIAMETER_UNABLE_TO_COMPLY               | The request failed.                                                                                                                                   |
+
+If DIAMETER\_ERROR\_USER\_UNKNOWN is received in the Sh-Notif response, the HSS shall remove all of the subscription to notification information subscribed by the AS related to the specific User Identity.
+
+## 6.2 AS permissions list
+
+In table 7.6.1, the contents of the Data-AVP are described. Some of the individual elements carried within Data-AVP may be requested by the AS from the HSS using the Sh-Pull command (see clause 6.1.1) or may be updated at the HSS by the AS using the Sh-Update command (see clause 6.1.2). The AS may also request that the HSS notifies the AS of changes to specific elements within the Data-AVP using the Sh-Subs-Notif command (see clause 6.1.3). The HSS will only allow these operations to take place if the element of the Data-AVP is permitted to be included in the specific command requested by the AS, as indicated in table 7.6.1.
+
+To manage whether an AS may request each element of Data-AVP with a specific command, the HSS shall maintain a list of AS permissions (the 'AS Permissions List'). AS permissions are identified by AS identity and Data Reference with the possible permissions associated with each Data Reference being Sh-Pull, Sh-Update, Sh-Subs-Notif or any combination of these permissions (see table 7.6.1 for details of which permissions are allowed for each Data Reference). The permissions apply to all users served by the HSS, they are not user specific. When an AS requests Sh-Pull, Sh-Update or Sh-Subs-Notif the HSS shall check permissions and return an error result if the AS does not have the required permission. If the AS permissions change in a later stage, i.e. the AS does not longer have the required permission, the HSS shall remove all the subscription to notifications for the AS for which required permissions have been prohibited.
+
+## 6.3 Void
+
+## 6.4 Void
+
+## 6.5 User identity to HSS resolution
+
+The User identity to HSS resolution mechanism enables the AS to find the identity of the HSS that holds the subscriber data for a given IMS Public User Identity or Public Service Identity when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilise a single HSS or when an AS is configured to use pre-defined HSS.
+
+The resolution mechanism described in 3GPP TS 23.228 [1] shall use a Subscription Locator Function (SLF) or a Diameter Proxy Agent.
+
+The AS accesses the SLF via the Dh interface. The Dh interface shall always be used in conjunction with the Sh interface. The Dh interface shall be based on the Diameter base protocol as specified in IETF RFC 6733 [44]. The SLF functionality shall use the routing mechanism provided by an enhanced Diameter redirect agent.
+
+The SLF or the Diameter Proxy Agent shall be to determine the HSS identity.
+
+To get the HSS identity the AS shall send the Sh request normally destined to the HSS to a pre-configured Diameter address/name.
+
+- If this Sh Request is received by an SLF (acting as a Diameter redirect agent), the SLF shall determine the HSS address and shall send to the AS a notification of redirection towards the HSS identity, in response to the Sh request. Multiple HSS identities may be included in the response, as specified in IETF RFC 6733 [44]. In such a case, the AS shall send the Sh Request to the first HSS identity in the ordered list received in the Sh Response from the SLF. If the AS does not receive a successful response to the Sh Request, the AS shall send a Sh Request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received.
+- If this Sh Request is received by the Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity based on the provided user identity and - if the Diameter load control mechanism is supported (see IETF RFC 8583 [43]) - optionally also based on previously received load values from Load AVPs of type HOST. The Diameter Proxy Agent shall then forward the Sh request directly to the determined HSS. The AS shall determine the HSS identity from the response to the Sh request received from the HSS.
+
+The AS should store the HSS identity/name/Realm and shall use it in further Sh requests associated to the same IMS Public Identity.
+
+In networks where the use of the user identity to HSS resolution mechanism is required and the AS is not configured to use a predefined HSS, each AS shall be configured with the pre-configured address/name of the SLF or the Diameter Proxy Agent to enable use of these resolution mechanisms.
+
+# 7 Information element contents
+
+## 7.1 User Identity
+
+This information element contains an IMS Public User Identity, Public Service Identity, MSISDN or External Identifier according to the conditions described in table 7.1.1.
+
+**Table 7.1.1: User Identity content**
+
+| Information element name                                       | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                                                                                                                                        |
+|----------------------------------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMS Public User Identity / Public Service Identity (See 7.1.1) | Public-Identity         | C    | IMS Public User Identity or Public Service Identity for which data is required. If the MSISDN and External Identifier are not included in the User-Identity AVP, the Public-Identity AVP shall be included in Sh messages only for allowed Data References as described in Table 7.6.1.            |
+| MSISDN (See 7.1.2)                                             | MSISDN                  | C    | MSISDN for which data is required. If the Public-Identity AVP and External Identifier are not included in the User-Identity AVP, the MSISDN AVP shall be included in the Sh-Pull or Sh-Subs-Notif or Sh-Update messages only for allowed Data References as described in Table 7.6.1.              |
+| External Identifier (See 7.1.3)                                | External-Identifier     | C    | External Identifier for which data is required. If the Public-Identity AVP and MSISDN are not included in the User-Identity AVP, the External Identifier AVP shall be included in the Sh-Pull or Sh-Subs-Notif or Sh-Update messages only for allowed Data References as described in Table 7.6.1. |
+
+### 7.1.1 IMS Public User Identity / Public Service Identity
+
+This information element contains an IMS Public User Identity / Public Service Identity (either SIP URI or tel URI). See 3GPP 23.003 [11].
+
+### 7.1.2 MSISDN
+
+This information element contains the MSISDN, or the Basic MSISDN if multinumbering is used (see 3GPP TS 23.012 [19]).
+
+### 7.1.3 External Identifier
+
+This information element contains the External Identifier (see 3GPP TS 23.003 [11]).
+
+### 7.1A Wildcarded PSI
+
+This information element contains a Wildcarded PSI that is hosted by an application server. For definition of a Wildcarded PSI, see 3GPP TS 23.003 [11].
+
+#### 7.1B Wildcarded Public User Identity
+
+This information element contains a Wildcarded Public User Identity that is stored in the HSS. For definition of a Wildcarded Public User Identity, see 3GPP TS 23.003 [11].
+
+## 7.2 Requested Domain
+
+This information element details the access domains for which certain data (e.g. user state, location information) are requested. See 3GPP TS 29.329 [5] for the list of possible values.
+
+### 7.2A Requested Nodes
+
+This information element details the access node types for which certain data (e.g. user state, location information) are requested. See 3GPP TS 29.329 [5] for the list of possible values.
+
+### 7.2B Serving Node Indication
+
+This information element indicates that the sender does not require any location information other than the serving node address/identity (i.e. MME name and/or SGSN number, or VLR number) for the requested domain and the requested nodes (if included). Other location information (e.g. Global Cell ID, Tracking Area ID) may be absent.
+
+This information element is only applicable to Location Information.
+
+## 7.3 Requested Data
+
+- Reference to the data that an AS is requesting from the HSS.
+- Reference to the data which, an AS wants to be notified of, when changed.
+- Reference to data for which subscription to notification of change is rejected.
+- Reference to data for which updates are required.
+- Reference to data for which update fails.
+
+See clause 7.6.
+
+## 7.4 Service Indication
+
+Identifier of one set of service related transparent data, which is stored in an HSS in an operator network per Public Identity. The HSS shall allocate memory space to implement a data repository to store transparent data per IMS Public User Identity or Public Service Identity and value of Service Indication with a Sequence Number for verification. For Public Service Identities matching a Wildcarded Public Service Identity, the repository data shall be stored per Wildcarded Public Service Identity and not for each specific Public Service Identity.
+
+## 7.5 Result
+
+This information element contains the result code of the operation. See 3GPP TS 29.329 [5] for the list of possible values.
+
+## 7.6 Data
+
+This information element contains an XML document conformant to the XML schema defined in Annex D.
+
+Annex C specifies the UML logical model of the data downloaded via the Sh interface.
+
+Table 7.6.1 defines the data reference values and tags, access key and recommended AS permissions (as described in clause 6.2) for the operation(s) on data accessible via the Sh interface, i.e. the listed operation(s) in the Operations column are the only ones allowed to be used with this Data Ref value. It is a matter of operator policy to further restrict the AS permission rights defined in table 7.6.1.
+
+An access key between square brackets is considered as optional, while when more than one access key is separated by logical OR and included between brackets, it means that one (and only one) of these access keys is mandatory.
+
+Table 7.6.1: Data accessible via Sh interface
+
+| Data Ref. | XML tag                               | Defined in | Access key                                                                                                                                                                                                                                                                        | Operations                                                |
+|-----------|---------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| 0         | RepositoryData                        | 7.6.1      | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity )<br>+ Service Indication                                                                                                                                                                               | Sh-Pull<br>Sh-Update<br>Sh-Subs-Notif<br>(Note 1, Note 3) |
+| 10        | IMSPublicIdentity                     | 7.6.2      | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity OR MSISDN OR External Identifier )<br>+ [ Requested Identity Set ]                                                                                                                                      | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 11        | IMSUserState                          | 7.6.3      | Data Reference<br>+ IMS Public User Identity                                                                                                                                                                                                                                      | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 12        | S-CSCFName                            | 7.6.4      | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity )                                                                                                                                                                                                       | Sh-Pull<br>Sh-Subs-Notif<br>(Note 1)                      |
+| 13        | InitialFilterCriteria                 | 7.6.5      | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity )<br>+ Application Server Name                                                                                                                                                                          | Sh-Pull<br>Sh-Subs-Notif<br>(Note 1)                      |
+| 14        | LocationInformation                   | 7.6.6      | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )<br>+ [ Private Identity ]<br>+ Requested Domain<br>+ Current Location<br>+ [ Serving Node Indication ]<br>+ [ Requested Nodes ]<br>+ [ Local Time Zone Indication ]<br>+ [ RAT-Type Requested ] | Sh-Pull<br>(Note 5)<br>(Note 6)<br>(Note 7)               |
+| 15        | UserState                             | 7.6.7      | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )<br>+ [ Private Identity ]<br>+ Requested Domain<br>+ [ Requested Nodes ]                                                                                                                        | Sh-Pull<br>(Note 5)<br>(Note 7)                           |
+| 16        | Charging information                  | 7.6.8      | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity OR MSISDN OR External Identifier )                                                                                                                                                                      | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 17        | MSISDN or MSISDN<br>+ExtendedMSISDN   | 7.6.9      | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )<br>+ [ Private Identity ]                                                                                                                                                                       | Sh-Pull<br>(Note 4)                                       |
+| 18        | PSIActivation                         | 7.6.10     | Data Reference<br>+ IMS Public Service Identity                                                                                                                                                                                                                                   | Sh-Pull<br>Sh-Update<br>Sh-Subs-Notif<br>(Note 1)         |
+| 19        | DSAI                                  | 7.6.11     | Data Reference<br>+ ( IMS Public User Identity OR Public Service Identity )<br>+ DSAI Tag<br>+ Application Server Name                                                                                                                                                            | Sh-Pull<br>Sh-Update<br>Sh-Subs-Notif<br>(Note 1)         |
+| 20        | Reserved                              |            |                                                                                                                                                                                                                                                                                   |                                                           |
+| 21        | ServiceLevelTraceInfo                 | 7.6.13     | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )                                                                                                                                                                                                 | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 22        | IP Address Secure Binding Information | 7.6.14     | Data Reference<br>+ IMS Public User Identity                                                                                                                                                                                                                                      | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 23        | Service Priority Level                | 7.6.15     | Data Reference<br>+ IMS Public User Identity                                                                                                                                                                                                                                      | Sh-Pull<br>Sh-Subs-Notif                                  |
+| 24        | SMSRegistrationInfo                   | 7.6.16     | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )<br>+ [ Private Identity ]                                                                                                                                                                       | Sh-Pull<br>Sh-Update<br>(Note 5)                          |
+| 25        | UE reachability for IP                | 7.6.17     | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR External Identifier )<br>+ [ Private Identity ]                                                                                                                                                                       | Sh-Subs-Notif<br>(Note 5)                                 |
+| 26        | T-ADS Information                     | 7.6.18     | Data Reference<br>+ ( IMS Public User Identity OR MSISDN )<br>+ [ Private Identity ]                                                                                                                                                                                              | Sh-Pull<br>(Note 5)                                       |
+| 27        | STN-SR                                | 7.6.20     | Data Reference<br>+ ( IMS Public User Identity OR MSISDN )<br>+ [ Private Identity ]                                                                                                                                                                                              | Sh-Pull<br>Sh-Update<br>(Note 5)                          |
+
+|         |                                                                                                                                                                                                                                                                                                                                                     |         |                                                                                                                |                                      |
+|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| 28      | UE-SRVCC-Capability                                                                                                                                                                                                                                                                                                                                 | 7.6.21  | Data Reference<br>+ ( IMS Public User Identity OR MSISDN )<br>+ [ Private Identity ]                           | Sh-Pull<br>Sh-Subs-Notif<br>(Note 5) |
+| 29      | ExtendedPriority                                                                                                                                                                                                                                                                                                                                    | 7.6.15A | Data Reference<br>+ IMS Public User Identity                                                                   | Sh-Pull<br>Sh-Subs-Notif             |
+| 30      | CSRN                                                                                                                                                                                                                                                                                                                                                | 7.6.22  | Data Reference<br>+ ( IMS Public User Identity OR MSISDN )<br>+ [ Private Identity ]                           | Sh-Pull<br>(Note 5)                  |
+| 31      | Reference Location Information                                                                                                                                                                                                                                                                                                                      | 7.6.23  | Data Reference<br>+ IMS Public User Identity<br>+ [ Private Identity ]                                         | Sh-Pull<br>(Note 5)                  |
+| 32      | IMSI                                                                                                                                                                                                                                                                                                                                                | 7.6.24  | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR<br>External Identifier )<br>+ [ Private Identity ] | Sh-Pull<br>(Note 5)<br>(Note 8)      |
+| 33      | IMSPrivateUserIdentity                                                                                                                                                                                                                                                                                                                              | 7.6.25  | Data Reference<br>+ IMS Public User Identity                                                                   | Sh-Pull<br>Sh-Subs-Notif<br>(Note 8) |
+| 34      | IMEISV                                                                                                                                                                                                                                                                                                                                              | 7.6.26  | Data Reference<br>+ ( IMS Public User Identity OR MSISDN OR<br>External Identifier )<br>+ [ Private Identity ] | Sh-Pull<br>(Note 5)                  |
+| 35      | UE-5G-SRVCC-Capability                                                                                                                                                                                                                                                                                                                              | 7.6.21A | Data Reference<br>+ ( IMS Public User Identity OR MSISDN )<br>+ [ Private Identity ]                           | Sh-Pull<br>Sh-Subs-Notif<br>(Note 5) |
+| Note 1: | If an AS subscribes to a Specific PSI matching a Wildcarded PSI, the notification shall be sent as if the subscription was made to the corresponding Wildcarded PSI.<br>If an AS requires reading for a Specific PSI matching a Wildcarded PSI, the response shall be sent as if the request was made to the corresponding Wildcarded PSI.          |         |                                                                                                                |                                      |
+| Note 2: | If not specified otherwise Public User Identity and Public Service Identity refer also to the wildcarded identities.                                                                                                                                                                                                                                |         |                                                                                                                |                                      |
+| Note 3: | Any IMS Public User Identity in an Alias Public User Identity Set may be used as a key for the repository data of the group. All IMS Public User Identities within the same set shall be considered alias of each other and shall share the same transparent data. See 3GPP TS 23.008 [27] for the definition of an Alias Public User Identity Set. |         |                                                                                                                |                                      |
+| Note 4: | If several MSISDNs are associated to the Public identity, an AS shall be required to indicate the IMS Private User Identity to fetch the C-MSISDN. See 3GPP TS 23.003 [11] and 3GPP TS 23.237 [32] for the definition of C-MSISDN. ExtendedMSISDN is returned in addition to MSISDN when Additional-MSISDN feature is enabled                       |         |                                                                                                                |                                      |
+| Note 5: | If a Sh procedure refers to a specific Private Identity within a set of multiple Private identities associated to an IMS Public User Identity or MSISDN, the corresponding Sh request shall include this Private Identity as part of the access key.                                                                                                |         |                                                                                                                |                                      |
+| Note 6: | Serving Node Indication is optionally included only if Current Location takes the value DoNotNeedInitiateActiveLocationRetrieval                                                                                                                                                                                                                    |         |                                                                                                                |                                      |
+| Note 7: | Requested Nodes is only applicable when Requested Domain is PS                                                                                                                                                                                                                                                                                      |         |                                                                                                                |                                      |
+| Note 8: | IMSI and IMS Private User Identity may be considered sensitive data, which not all ASs may be permitted to retrieve. See clause 6.2.                                                                                                                                                                                                                |         |                                                                                                                |                                      |
+| Note 9: | If Data Reference and External Identifier are used as access key, Private Identity is not applicable as additional access key.                                                                                                                                                                                                                      |         |                                                                                                                |                                      |
+
+### 7.6.1 Repository Data
+
+This information element contains transparent data. A data repository may be shared by more than one AS implementing the same service.
+
+### 7.6.2 IMSPublicIdentity
+
+This data contents included in the Sh-Pull Resp, Sh-Subs-Notif Resp or Sh-Notif depends on whether Requested Identity Set information element was included in the Sh-Pull or Sh-Subs-Notif, as follows:
+
+- When this information element takes the value IMPLICIT\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities that belong to the same implicit registration set as the IMS Public Identity included in the message in the User-Identity AVP. The MSISDN and External Identifier within the User-Identity AVP are not applicable for this value. If the User Identity is a Public Service Identity, the HSS shall return only the User Identity received in the request.
+- When this information element takes the value ALIAS\_IDENTITIES, the HSS shall provide all non-barred IMS Public User Identities that are in the same Alias Public User Identity Set as the IMS Public User Identity included in the message in the User-Identity AVP (see 3GPP TS 23.008 [27] for the definition of Alias Public User Identity Set). The MSISDN, the Public Service Identity and the External Identifier within the User-Identity AVP are not applicable for this value.
+- When this information element takes the value REGISTERED\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities whose state is registered, belonging to all Private Identities that the IMS Public
+
+Identity or MSISDN or External Identifier in the User-Identity AVP is associated with. If the User Identity is a Public Service Identity, the HSS shall return no identities in the response.
+
+- When this information element takes the value ALL\_IDENTITIES, the HSS shall provide all non-barred IMS Public Identities, belonging to all Private Identities that the User Identity is associated with.
+- When this information element is not included, the HSS shall download the set of IMS Public Identities that would be downloaded if the value of this information element had been ALL\_IDENTITIES.
+
+An IMS Public Identity would be either:
+
+- associated with the same Private User Identity or Private Service Identity as the User Identity included in the request or
+- associated with the MSISDN present in the request or
+- associated with an External Identifier present in the request.
+
+Multiple instances of this information element may be included in the message.
+
+### 7.6.3 IMS User State
+
+This information element contains the IMS User State of the public identifier referenced. Its possible values are:
+
+- REGISTERED,
+- NOT\_REGISTERED,
+- AUTHENTICATION\_PENDING,
+- REGISTERED\_UNREG\_SERVICES.
+
+If the IMS Public User Identity is shared between multiple Private User Identities, HSS shall indicate the most registered state of the shared IMS Public User Identity to an AS. The most registered state of a shared IMS Public User Identity is defined as follows:
+
+- If the shared IMS Public User Identity is registered with any of the Private User Identities, the most registered state of the shared IMS Public User Identity is REGISTERED.
+- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, but it is in state REGISTERED\_UNREG\_SERVICES, then the most registered state of the shared IMS Public User Identity is REGISTERED\_UNREG\_SERVICES.
+- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, and it is not in state REGISTERED\_UNREG\_SERVICES, but it is in the process of being authenticated with any of the Private User Identities, then the most registered state of the shared IMS Public User Identity is AUTHENTICATION\_PENDING.
+- If the shared IMS Public User Identity is not currently registered with any of the Private User Identities, and it is not in state REGISTERED\_UNREG\_SERVICES, and it is not in the process of being authenticated with any of the Private User Identities, then the most registered state of the shared IMS Public User Identity is NOT\_REGISTERED.
+
+### 7.6.4 S-CSCF Name
+
+This information element contains the name of the S-CSCF assigned to the IMS Subscription.
+
+### 7.6.5 Initial Filter Criteria
+
+This information element contains the triggering information for a service.
+
+For a more detailed description, refer to 3GPP TS 23.218 [4] and 3GPP TS 29.228 [6].
+
+### 7.6.6 Location Information
+
+This information element contains either:
+
+- the location of the served subscriber in the MSC/VLR if the requested domain is CS, or
+- the location of the served subscriber in the SGSN if the requested domain is PS and either the requested node is solely SGSN or the requested node is not present, or
+- the location of the served subscriber in the MME if the requested domain is PS and the requested nodes is solely MME, or
+- the locations of the served subscriber in the 3GPP AAA Server for TWAN if the requested domain is PS and the requested nodes is solely 3GPP AAA SERVER for TWAN, or
+- the location of the served subscriber in the AMF (for 3GPP access) if the requested domain is PS and the requested nodes is solely AMF.
+- the locations of the served subscriber in the MME and the SGSN and 3GPP AAA Server for TWAN and AMF if the requested domain is PS and the requested nodes are all of MME and SGSN and 3GPP AAA SERVER for TWAN and AMF, or
+- the locations of the served subscriber in any of the two or three serving nodes among the MME, the SGSN, the 3GPP AAA Server for TWAN and the AMF if the requested domain is PS and the requested nodes indicates the corresponding nodes for which the location are to be requested.
+
+If the HSS has to communicate with the MSC/VLR or SGSN and/or MME and/or 3GPP AAA Server and/or AMF (via UDM) to retrieve location information, it shall make use of the service MAP-PROVIDE-SUBSCRIBER-INFO or S6a/S6d-IDR or SWx-PPR or make use (via UDM) of the Namf Service-Based Interface services. This information element shall contain the location information as received from the access nodes.
+
+If the HSS or HSS/UDM cannot communicate with the VLR or SGSN or MME or AMF (e.g., because the UE is purged), or if the HSS or HSS/UDM cannot retrieve the location information from the serving nodes because they do not support such feature, the HSS shall provide locally stored location information if available (e.g., serving node name, Visited PLMN ID) received in a previous Update Location message, and the last known UE's location if available e.g. as received in the Purge message from VLR or SGSN or MME or AMF.
+
+If the Serving Node Indication was present in the request, the location information shall contain the serving node address(es) as stored in the HSS, according to the requested domain and the requested nodes (if received). Other location information may be absent, in order to eliminate unnecessary communication with the MSC/VLR or SGSN and/or MME and/or 3GPP AAA Server and/or AMF when the AS does not require these information elements.
+
+For both Location Information for CS and Location Information for GPRS, the considerations described in 3GPP TS 23.078 [14] apply.
+
+#### 7.6.6.1 Location information for CS
+
+This information element consists of the following subordinate information elements:
+
+- Location number: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 apply [10].
+- Service area ID: defined in 3GPP TS 23.003 [11].
+- Cell Global ID: defined in 3GPP TS 23.003 [11].
+- Location area ID: defined in 3GPP TS 23.003 [11].
+- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- VLR Number: defined in 3GPP TS 23.003 [11].
+
+- MSC Number: defined in 3GPP TS 23.003 [11].
+- Age of location information: defined in 3GPP TS 23.018 [10].
+- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the MS is in idle state or when the location was provided if the MS is in active state.
+- User CSG information: defined in 3GPP TS 23.060 [29].
+- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11].
+- Tracking Area ID: defined in 3GPP TS 23.003 [11].
+- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26].
+
+NOTE: When the MSC receives the location information via SGs interface as specified in 3GPP TS 29.118 [30], the E-UTRAN Cell Global ID and Tracking Area ID are included, rather than Location number, Service area ID, Cell Global ID and Location area ID.
+
+#### 7.6.6.2 Location information for GPRS
+
+This information element consists of the following subordinate information elements:
+
+- Service area ID: defined in 3GPP TS 23.003 [11].
+- Cell Global ID: defined in 3GPP TS 23.003 [11].
+- Location area ID: defined in 3GPP TS 23.003 [11].
+- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- SGSN Number: defined in 3GPP TS 23.003 [11].
+- Routing Area ID: defined in 3GPP TS 23.003 [11].
+- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode.
+- Age of location information: defined in 3GPP TS 23.018 [10].
+- User CSG information: defined in 3GPP TS 23.060 [29].
+- Visited PLMN ID: defined in 3GPP TS 23.003 [11].
+- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26].
+- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31.
+
+#### 7.6.6.3 Location information for EPS
+
+This information element consists of the following subordinate information elements:
+
+- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11].
+- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+
+- Geodetic Information: defined in ITU-T Recommendation Q.763 [9]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- MME Name: Diameter Identity of the MME as received by the HSS within the S6a ULR Origin-Host AVP; see 3GPP TS 29.272 [31].
+- Tracking Area ID: defined in 3GPP TS 23.003 [11].
+- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode.
+- Age of location information: defined in 3GPP TS 23.018 [10].
+- Visited PLMN ID: defined in 3GPP TS 23.003 [11].
+- User CSG information: defined in 3GPP TS 23.060 [29].
+- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26]. .
+- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31.
+
+#### 7.6.6.4 Location Information for TWAN
+
+This information element consists of the following subordinate information elements:
+
+- TWAN SSID: defined in 3GPP TS 29.273 [34].
+- TWAN BSSID: defined in 3GPP TS 29.273 [34].
+- TWAN PLMN ID: defined in clause 12.1 of 3GPP TS 23.003 [11] for PLMN Identifier.
+- Civic Address: defined in clause 3.1 of IETF RFC 4776 [35] excluding the first 3 octets.
+- TWAN Operator Name: defined in clause 19.8 of 3GPP TS 23.003 [11].
+- Local Time Zone: the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26].
+- Logical Access ID defined in ETSI ES 283 034 [37].
+
+NOTE: The location information defined for EPS in clause 7.6.6.3 is not relevant to the TWAN location information.
+
+#### 7.6.6.5 Location Information for 5GS
+
+This information element consists of the following subordinate information elements:
+
+- NR Cell Global ID: defined in 3GPP TS 23.003 [11].
+- E-UTRAN Cell Global ID: defined in 3GPP TS 23.003 [11].
+- Geographical Information: defined in 3GPP TS 23.032 [12]. Considerations described in 3GPP TS 23.018 [10] and 3GPP TS 29.002 [13] apply.
+- AMF Address: Identity of the serving AMF (for 3GPP access).
+- SMSF Address: Identity of the serving SMSF (for 3GPP access).
+- Tracking Area ID: defined in 3GPP TS 23.003 [11].
+- Current Location Retrieved: shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval if the UE is in idle mode or when the location was provided if the UE is in connected mode.
+
+- Age of location information: defined in 3GPP TS 23.018 [10].
+- Visited PLMN ID: defined in 3GPP TS 23.003 [11].
+- Local Time Zone: Time zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached, as defined in 3GPP TS 29.272 [26].
+- RAT type: the possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31.
+
+### 7.6.7 User state
+
+This information element indicates the state of the User Identity in the domain/node indicated by the Requested-Domain/Requested-Node (see 7.2), with the values specified in 3GPP TS 23.078 [14] for Subscriber State and PS Domain Subscriber State, and with the values specified in 3GPP TS 29.272 [31] for EPS User State and 3GPP TS 29.518 [47] for the 5GS User State.
+
+- The HSS shall make use of the operation MAP-PROVIDE-SUBSCRIBER-INFO towards the MSC/VLR to obtain this information if the requested domain is CS.
+- The HSS shall make use of the operation S6a-IDR towards the MME to obtain this information if the requested domain is PS and the requested node is MME.
+- The HSS shall make use of the operation MAP-PROVIDE-SUBSCRIBER-INFO or S6d-IDR towards the SGSN to obtain this information if the requested domain is PS and either the requested node is SGSN or the requested node is not present.
+- The HSS shall make use of the operation S6a-IDR towards the MME and MAP-PROVIDE-SUBSCRIBER-INFO or S6d-IDR towards the SGSN to obtain this information if the requested domain is PS and the Requested Nodes is MME and SGSN.
+- The UDM+HSS shall make use of the Namf\_EventExposure Subscribe Service Operation towards the AMF to obtain this information if the requested domain is PS and the requested node is AMF.
+
+This information element shall contain the information as received from the access nodes. The UDM+HSS may retrieve the User States from the MME, SGSN or AMF within one procedure.
+
+The UDM+HSS shall include the value "NotProvidedFromSGSN or MME or AMF" in the "EPSUserState" / "PSUserState" / "Sh-5GSUserState" fields, if the MME, SGSN or AMF does not support the retrieval of User State over S6a/S6d-IDR/ Namf\_EventExposure Service, or it did not provide any information on subscriber state even though it was requested by UDM+HSS.
+
+### 7.6.8 Charging information
+
+This information element contains the addresses of the charging functions: primary Online Charging Function (PrimaryEventChargingFunctionName), secondary Online Charging Function (SecondaryEventChargingFunctionName), primary Charging Data Function (PrimaryChargingCollectionFunctionName), and secondary Charging Data Function (SecondaryChargingCollectionFunctionName). When a clash occurs between the charging function address(es) received over the ISC interface and those received over the Sh interface, the address(es) received over the ISC interface should take precedence.
+
+- NOTE: The use of the Sh interface to retrieve charging function addresses is not intended as a general-purpose alternative to receiving charging function addresses from the ISC interfaces. Rather, it is meant to address a special case where the AS needs to interact with the charging system before initiating a request to a user when the AS has not received the third party REGISTER for that user.
+
+The AS shall extract the FQDN of the DiameterURI in these information elements and may use it as content of the Destination-Host AVP for the Diameter accounting requests. The parent domain of the FQDN in the DiameterURI shall be used as Destination-Realm. The number of labels used for the Destination-Realm shall be determined before the Charging Information is provisioned and may be a configuration option.
+
+- NOTE: A FQDN is an absolute domain name including a subdomain and its parent domain. The subdomain and the parent domain contain one or more labels separated by dots.
+
+### 7.6.9 MSISDN
+
+This information element contains the MSISDN, or the Basic MSISDN if multnumbering is used, that is associated with the User Identity present in the request. See 3GPP TS 23.012 [19] for Basic MSISDN definition.
+
+Multiple instances of this information element shall only occur if the Public User Identity is shared and no Private Identity was included in the request, otherwise only one instance shall be included in the message.
+
+If Additional-MSISDN feature is supported by the HSS but the AS has indicated that it does not support it, it is up to operator policy to decide what information is returned by the HSS, either what is provisioned in MSISDN or in Additional MSISDN (A-MSISDN).
+
+#### 7.6.9A Extended MSISDN
+
+This information element is returned in addition to MSISDN if Additional-MSISDN feature is supported by the HSS, the AS has indicated as well its support and an Additional MSISDN (A-MSISDN) is provisioned..
+
+It contains the Additional-MSISDN that is associated with the User Identity present in the request.
+
+All valid instances of this information element shall be included in the message.
+
+### 7.6.10 PSIActivation
+
+This information element contains the activation state of the Public Service Identity present in the request. Its possible values are:
+
+- ACTIVE,
+- INACTIVE.
+
+### 7.6.11 DSAI
+
+When a service is provisioned but not active, an Application Server is typically involved through the ISC interface in sessions where the Application Server is not supposed to perform any task but to proxy incoming transactions.
+
+In order to avoid this disoptimization, a mechanism is provided for the Application Server to signal the HSS that a set of initial filter criteria should be "masked" for a specific Public User Identity or Public Service Identity. This is, from the Application Server's perspective, just an indication, and an Application Server must be prepared to be involved in sessions even if the trigger that caused its involvement has been masked by that Application Server.
+
+This information element contains the activation state of a Service (identified by its DSAI-tag, see clause 7.14, for a specific user identified by a Public User Identity or of a Service identified by its PSI). Its possible values are:
+
+- ACTIVE,
+- INACTIVE.
+
+In the HSS the DSAI can also be associated to a wildcarded PSI. In that case, there is a set of identities matching a specific wildcarded PSI and all the identities in the set share the same DSAIs. Any change in these DSAIs masked from a single identity of the set will apply to all the identities associated to that wildcarded PSI.
+
+Each DSAI is implicitly bound to a list of (at least one) initial filter criteria. The binding is not exclusive, i.e. one instance of initial filter criteria may be bound to zero or more DSAIs, however all the iFCs bound to a given DSAI should trigger to the same AS (i.e. they should share the same ServerName), which is the only one allowed to update it.
+
+An instance of initial filter criteria shall be included into the Service-Profile sent through the Cx Interface according to the operations described in 3GPP TS 29.228 [6] if at least one of the following conditions applies:
+
+- No DSAI is bound to those initial filter criteria;
+- At least one of the DSAIs bound to those initial filter criteria is set to ACTIVE.
+
+### 7.6.12 Void
+
+### 7.6.13 Service Level Trace Information
+
+This information element contains the Service Level Tracing Information (see 3GPP TS 24.323 [45]) that is related to a specific Public Identifier. If the ServiceLevelTraceInfo is present, service level tracing shall be enabled in the Application Server for the related Public Identifier according to the configuration data received. If the ServiceLevelTraceInfo is not present, service level tracing is disabled in the Application Server for the related Public Identifier.
+
+### 7.6.14 IP address secure binding information
+
+This information element contains the IP address (or the prefix in the case of IPv6 stateless autoconfiguration) at any given time. See 3GPP TS 33.203 [22], Annex T.
+
+### 7.6.15 Service Priority Level
+
+This information element contains the Priority Level allowed for the Public Identity for Priority Service. If the ServicePriority Level is present, priority services are allowed for the Public Identity. See IETF RFC 4412 [25].
+
+#### 7.6.15A Extended Priority
+
+This information element contains the following information elements:
+
+- The PriorityNamespace information element provides the namespace as specified in IETF RFC 4412 [25] and to which the Extended Priority refers.
+- The PriorityLevel information element provides the Priority Level allowed for the Public User Identity for a given PriorityNamespace.
+
+### 7.6.16 SMSRegistrationInfo
+
+This information element contains an IP-SM-GW number and the address of a Short Message Service Centre. For the definition of an IP-SM-GW number and Service Centre Address, see 3GPP TS 23.008[27].
+
+### 7.6.17 UE reachability for IP
+
+This information element reflects the change of URRP-MME and/or URRP-SGSN parameters and indicates whether the UE has become reachable, i.e. when the URRP-MME and/or URRP-SGSN parameters was set and has been cleared due to UE activity notification from the MME and/or the SGSN, see 3GPP TS 29.272 [26].
+
+This information element also indicates whether the UE has become reachable at the AMF for 3GPP access and/or at the AMF for non 3GPP access.
+
+It consists of the following subordinate information elements:
+
+- UE-IP-REACHABILITY-MME. Its possible values are:
+  - REACHABLE (0)
+- UE-IP-REACHABILITY-SGSN. Its possible values are:
+  - REACHABLE (0)
+- UE-IP-REACHABILITY-AMF-3GPP. Its possible values are:
+  - REACHABLE (0)
+- UE-IP-REACHABILITY-AMF-NON-3GPP. Its possible values are:
+  - REACHABLE (0)
+
+### 7.6.18 T-ADS Information
+
+This information element indicates the RAT type that is serving the UE and whether or not IMS voice over PS Session is supported at the current Routing Area/Tracking Area.
+
+The HSS shall make use of the appropriate S6a operation towards the MME and/or S6d/MAP operation towards the SGSN to retrieve the T-ADS information. The UDM/HSS shall make use of appropriate Namf service operation towards the AMF to retrieve the T-ADS information.
+
+The possible values for IMS voice over PS Session support are:
+
+- IMS-VOICE-OVER-PS-NOT-SUPPORTED (0)
+- IMS-VOICE-OVER-PS-SUPPORTED (1)
+- IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN (2)
+
+The possible values of RAT type are specified in 3GPP TS 29.212 [28], clause 5.3.31.
+
+### 7.6.19 Private Identity
+
+This information element contains the IMS Private User Identity or the IMSI. See 3GPP TS 23.003 [17]).
+
+### 7.6.20 STN-SR
+
+This information element indicates the Session Transfer Number for SRVCC or 5G-SRVCC (see 3GPP TS 23.003 [11]).
+
+When STN-SR is updated, the HSS shall make use of the service S6a/S6d-IDR to update the STN-SR in the MME/SGSN and, if the HSS supports interworking with the UDM (see in 3GPP TS 23.632 [48]), the UDM shall make use of the Nudm\_MT\_Update operation to update the STN-SR in the AMF.
+
+### 7.6.21 UE SRVCC Capability
+
+This information element indicates the SRVCC capability of the UE.
+
+The possible values for the UE-SRVCC capability are:
+
+- UE-SRVCC-CAPABILITY-NOT-SUPPORTED (0)
+- UE-SRVCC-CAPABILITY-SUPPORTED (1)
+
+### 7.6.21A UE 5G SRVCC Capability
+
+This information element indicates the 5G SRVCC capability of the UE.
+
+The possible values for the UE-5G-SRVCC capability are:
+
+- UE-5G-SRVCC-CAPABILITY-NOT-SUPPORTED (0)
+- UE-5G-SRVCC-CAPABILITY-SUPPORTED (1)
+
+### 7.6.22 CSRN
+
+This information element contains a CS Domain Routing Number (see 3GPP TS 23.003) associated to the user identity of the request.
+
+The HSS shall make use of the operation MAP-PROVIDE-ROAMING-NUMBER towards the MSC/VLR to obtain this information and shall indicate the Suppression of Announcement to the MSC/VLR.
+
+This information element is requested by AS when all terminating services have been already executed, then HSS is only interested in the CSRN received from MSC/VLR.
+
+### 7.6.23 Reference Location Information
+
+This information element contains the reference location of the user, e.g. the physical location of the fixed line in the case of a fixed line access, that is associated with the User Identity and Private Identity (if present) in the request. See 3GPP TS 23.008 [27].
+
+### 7.6.24 IMSI
+
+This information element contains the IMSI that is associated with the IMS Public User Identity present in the request. See 3GPP TS 23.003 [11] for IMSI definition.
+
+### 7.6.25 IMSPrivateUserIdentity
+
+This information element contains all IMS Private User Identities associated with the IMS Public User Identity present in the request. See 3GPP TS 23.003 [11] for Private User Identity definition.
+
+### 7.6.26 IMEISV
+
+This information element contains the IMEI or IMEISV (see 3GPP TS 23.003 [11]) of the UE employed by the user identity of the request, during the attach to the access network.
+
+## 7.7 Subscription request type
+
+This information element indicates the action requested for subscription to notifications. See 3GPP TS 29.329 [5] for the list of valid values.
+
+## 7.8 Current Location
+
+This information element indicates whether an active location retrieval has to be initiated or not when an AS requested location information. See 3GPP TS 29.329 [5] for the list of possible values.
+
+## 7.9 Application Server Identity
+
+This information element contains the identity of the Application Server. It is used for the AS permission check (see 6.2).
+
+## 7.10 Application Server Name
+
+This information element indicates application server's SIP URI. See 3GPP TS 29.229 [7] for the detailed definition of the AVP.
+
+## 7.11 Requested Identity Set
+
+This information element indicates the set of IMS Public Identities that the AS wishes to download. See 3GPP TS 29.329 [5] for the detailed definition of the AVP.
+
+## 7.12 Expiry Time
+
+This information element indicates the expiry time of the subscription to notifications in the HSS. See 3GPP TS 29.329 [5] for the detailed definition of this AVP.
+
+## 7.13 Send Data Indication
+
+This information element indicates the request that the User Data is sent in the response. See 3GPP TS 29.329 [5] for the detailed definition of this AVP.
+
+## 7.14 DSAI Tag
+
+An instance of Dynamic Service Activation Info is uniquely identified by the Public User/Service Identity and a DSAI tag. The same DSAI tag may be used for all the user profiles when indicating the same type of information, but not all the user profiles may contain the same set of tags.
+
+Application Servers shall signal that they are not interested in being involved in new sessions by manipulating Dynamic Service Activation Info (DSAI) inside of dynamic service information data, see clause 7.6.11.
+
+## 7.15 Session-Priority
+
+This information element indicates the session's priority level to the HSS. See 3GPP TS 29.229 [7].
+
+## 7.16 One Time Notification
+
+This information element indicates that the sender requests to be notified only one time. After the notification, the HSS shall remove the subscription. See 3GPP TS 29.329 [5] for the list of possible values.
+
+## 7.17 Repository Data ID
+
+This information element includes the service indication and the sequence number of a repository data. See 3GPP TS 29.329 [5] for the detailed definition of this AVP.
+
+## 7.18 Pre-paging Supported
+
+This information element indicates whether Pre-paging is supported by the AS. See 3GPP TS 29.329 [5] for the detailed definition of this AVP.
+
+## 7.19 Local Time Zone Indication
+
+This information element indicates that the Local Time Zone information (Time Zone and Daylight Saving Time) of the location in the visited network where the UE is attached for the requested domain and the requested nodes (if included) is requested and indicates whether only the Local Time Zone is required or the Local Time Zone is required together with other location data. If only the Local Time Zone is required, other location information (e.g. Global Cell ID, Tracking Area ID) may be absent.
+
+This information element is only applicable to Location Information.
+
+## 7.20 UDR Flags
+
+This information element carries the following indications (see 3GPP 29.329 [5] for coding details):
+
+Table 7.20/1: UDR Flags
+
+| Name                               | Description                                                                                                                                                                                                                                                                                                     |
+|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location-Information-EPS-Supported | Location Information EPS Supported shall be only applicable if CS Location Information is requested.<br>It indicates that EPS Location Information may be sent to the AS when CS Location Information is requested.<br>When set, the HSS shall indicate to the MSC/VLR the support of Location Information EPS. |
+| RAT-Type-Requested                 | RAT Type Requested shall be only applicable if PS or EPS Location Information is requested<br>When set, it indicates that RAT Type is requested as part of the PS or EPS Location Information.                                                                                                                  |
+
+## 7.21 Call Reference Info
+
+This information element contains information used for MTRR (see 3GPP TS 23.018 [10]):
+
+- Call Reference Number (see 7.22)
+- AS-Number (see 7.23)
+
+The HSS uses this information to populate the parameters callReferenceNumber and gmsc-Address within MAP-Provide-Roaming-Number.
+
+## 7.22 Call Reference Number
+
+This information element contains a temporary reference number identifying the call in progress (see 3GPP TS 23.018 [10]).
+
+## 7.23 AS-Number
+
+This information element contains the Application Server's E.164 Number.
+
+# --- 8 Protocol version identification
+
+See 3GPP TS 29.329 [5].
+
+# --- 9 Operational Aspects
+
+See 3GPP TS 29.329 [5].
+
+# --- Annex A (normative): Mapping of Sh operations and terminology to Diameter
+
+## A.1 Introduction
+
+This appendix gives mappings from Sh to Diameter protocol elements. Diameter protocol elements are defined in 3GPP TS 29.329 [5].
+
+## --- A.2 Sh message to Diameter command mapping
+
+The following table defines the mapping between stage 2 operations and Diameter commands:
+
+**Table A.2.1: Sh message to Diameter command mapping**
+
+| Sh message         | Source | Destination | Command-Name                    | Abbreviation |
+|--------------------|--------|-------------|---------------------------------|--------------|
+| Sh-Pull            | AS     | HSS         | User-Data-Request               | UDR          |
+| Sh-Pull Resp       | HSS    | AS          | User-Data-Answer                | UDA          |
+| Sh-Update          | AS     | HSS         | Profile-Update-Request          | PUR          |
+| Sh-Update Resp     | HSS    | AS          | Profile-Update-Answer           | PUA          |
+| Sh-Subs-Notif      | AS     | HSS         | Subscribe-Notifications-Request | SNR          |
+| Sh-Subs-Notif Resp | HSS    | AS          | Subscribe-Notifications-Answer  | SNA          |
+| Sh-Notif           | HSS    | AS          | Push-Notification-Request       | PNR          |
+| Sh-Notif Resp      | AS     | HSS         | Push-Notification-Answer        | PNA          |
+
+## --- A.3 Void
+
+# Annex B (informative): Message flow
+
+## B.1 Message flows
+
+The following message flows give examples regarding which Diameter messages shall be sent in scenarios described in 3GPP TS 23.218 [4].
+
+### B.1.1 Data Update, Registration, Notification Subscription.
+
+![Sequence diagram showing message flows between S-CSC, HSS, and AS within a Home Network. The diagram illustrates three scenarios: 1. Service provisioning (AS to HSS), 2. User registration (External to S-CSC), and 3. Data updates and notifications between AS and HSS.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg)
+
+Home Network
+
+```
+
+sequenceDiagram
+    participant External
+    participant S-CSC
+    participant HSS
+    participant AS
+
+    Note right of AS: 1. Sh-Update
+    AS->>HSS: 1. Sh-Update
+    HSS-->>AS: 2. Sh-Update Resp
+    External->>S-CSC: 3. REGISTER
+    Note right of S-CSC: 4. User Profile Downloading
+    S-CSC-->>External: 5. 200 OK
+    Note right of AS: 6. REGISTER (Third Party)
+    AS->>S-CSC: 6. REGISTER (Third Party)
+    S-CSC-->>AS: 7. 200 OK
+    Note right of HSS: 8. Sh-Subs_Notif + Send data Ind.
+    HSS->>AS: 8. Sh-Subs_Notif + Send data Ind.
+    AS-->>HSS: 9. Sh-Subs_Notif Resp + User-Data
+    Note right of AS: At some point, the AS decides to update certain data in the HSS
+    AS->>HSS: 10. Sh-Update
+    HSS-->>AS: 11. Sh-Update Resp
+    Note right of HSS: At some point, the HSS sends updates to the AS (that previously subscribed)
+    HSS->>AS: 12. Sh-Notif
+    AS-->>HSS: 13. Sh-Notif Resp
+  
+```
+
+Sequence diagram showing message flows between S-CSC, HSS, and AS within a Home Network. The diagram illustrates three scenarios: 1. Service provisioning (AS to HSS), 2. User registration (External to S-CSC), and 3. Data updates and notifications between AS and HSS.
+
+**Figure B.1.1: Data Update, Registration, Notification Subscription**
+
+1. A user subscribes to a new service. The operator provisions the service in an AS. The AS stores some service data for a user in the HSS, Sh-Update (user identity, updated data) e.g. repository data.
+2. HSS confirms the data is updated
+3. Some time later, user registers with the network
+
+4. S-CSCF downloads the data from the HSS (during the procedure S-CSCF Registration Notification on Cx interface). Filter criteria specify that the AS wants to be notified that the end user is registered.
+5. 200 OK
+6. S-CSCF sends third party registration message to the application server to notify that user is registered.
+7. 200 OK
+8. The AS subscribes to notifications and downloads data needed for providing service from HSS, by means of Sh-Subs-Notif (user identity, requested data, service information and send data indication).
+9. HSS confirms the subscription request and sends data to AS
+10. At some moment, the AS decides to update user's service data e.g. repository data in the HSS, by means of Sh-Update (user identity, updated data).
+11. The HSS confirms the service data is updated.
+12. At some moment, user data is updated in the HSS. As the AS subscribed to notifications (step 8), the HSS sends to the AS the requested updates, by means of Sh-Notif (user identity, updated data).
+13. The AS acknowledges the notification.
+
+# Annex C (informative): UML model of the data downloaded over Sh interface
+
+The purpose of this UML model is to define in an abstract level the structure of the data downloaded over the Sh interface and describe the purpose of the different information classes included in it.
+
+## C.1 General description
+
+The following picture gives an outline of the UML model of the user profile, which is exchanged between the HSS and an AS:
+
+![UML Class Diagram of Sh-Data structure](052543d8c9c0643b05b3ce45c6decca1_img.jpg)
+
+```
+
+classDiagram
+    class ShData {
+        CSUserState: enumerated
+        PSUserState: enumerated
+        EPSUserState: enumerated
+        Sh-5GSUserState: enumerated
+        IMSI: string
+        IMSPrivateUserIdentity: string
+        IMEISV: string
+    }
+    class PublicIdentifiers
+    class RegisteredIdentities
+    class ImplicitIdentities
+    class AllIdentities
+    class AliasIdentities
+    class DeletedIdentities
+    class RepositoryData {
+        ServiceIndication
+        SequenceNumber
+        ServiceData
+    }
+    class UE_reachability {
+        URRP-MME
+        URRP-SGSN
+    }
+    class TADS_information {
+        IMSVoiceOverPSSessionSupport
+        RATtype
+    }
+    class CSLocationInformation {
+        CellGlobalId
+        ServiceAreaId
+        LocationAreaId
+        LocationNumber
+        GeodeticInformation
+        GeographicalInformation
+        AgeOfLocationInformation
+        VLRNumber
+        CurrentLocationRetrieved
+        MSCNumber
+        UserCSGInformation
+        E-UTRANCellGlobalId
+        TrackingAreaId
+        LocalTimeZone
+    }
+    class PSLocationInformation {
+        CellGlobalId
+        ServiceAreaId
+        LocationAreaId
+        RoutingAreaId
+        GeodeticInformation
+        GeographicalInformation
+        AgeOfLocationInformation
+        CurrentLocationRetrieved
+        SGSNNumber
+        UserCSGInformation
+        VisitedPLMNID
+        LocalTimeZone
+        RATtype
+    }
+    class EPSLocationInformation {
+        E-UTRANCellGlobalId
+        TrackingAreaId
+        GeographicalInformation
+        GeodeticInformation
+        AgeOfLocationInformation
+        CurrentLocationRetrieved
+        MMENName
+        UserCSGInformation
+        VisitedPLMNID
+        LocalTimeZone
+        RATtype
+    }
+    class TWANLocationInformation {
+        TWAN-SSID
+        TWAN-BSSID
+        TWAN-PLMNID
+        CivicAddress
+        TWANOperatorName
+        LocalTimeZone
+        LogicalAccessID
+    }
+    class GSLocationInformation {
+        NRCellGlobalId
+        E-UTRANCellGlobalId
+        TrackingAreaId
+        GeographicalInformation
+        AMFAddress
+        SMSFAddress
+        CurrentLocationRetrieved
+        AgeOfLocationInformation
+        VisitedPLMNID
+        LocalTimeZone
+        RATtype
+    }
+    class ShIMSData {
+    }
+
+    ShData "1" *-- "0..1" PublicIdentifiers
+    ShData "1" *-- "0..n" RepositoryData
+    ShData "1" *-- "0..1" UE_reachability
+    ShData "1" *-- "0..1" TADS_information
+    ShData "1" *-- "0..1" ImplicitIdentities
+    ShData "1" *-- "0..1" CSLocationInformation
+    ShData "1" *-- "0..1" PSLocationInformation
+    ShData "1" *-- "0..1" EPSLocationInformation
+    ShData "1" *-- "0..1" TWANLocationInformation
+    ShData "1" *-- "0..1" GSLocationInformation
+    ShData "1" *-- "0..1" AllIdentities
+    ShData "1" *-- "0..1" AliasIdentities
+    ShData "1" *-- "0..1" DeletedIdentities
+    ShData "1" *-- "0..1" RegisteredIdentities
+    ShData "1" *-- "0..1" ShIMSData
+  
+```
+
+The diagram illustrates the UML model of the data downloaded over the Sh interface. At the top is the **Sh Data** class, which contains attributes: CSUserState (enumerated), PSUserState (enumerated), EPSUserState (enumerated), Sh-5GSUserState (enumerated), IMSI (string), IMSPrivateUserIdentity (string), and IMEISV (string). This class has a composition relationship with several other classes. On the left, it is associated with **PublicIdentifiers** (0..1), **RegisteredIdentities** (0..1), **ImplicitIdentities** (0..1), **AllIdentities** (0..1), **AliasIdentities** (0..1), **DeletedIdentities** (0..1), and **Sh-IMS-Data** (0..1). To the right, it is associated with **RepositoryData** (0..n), **UE reachability** (0..1), and **TADS information** (0..1). Below these, it is associated with five location information classes: **CSLocationInformation** (0..1), **PSLocationInformation** (0..1), **EPSLocationInformation** (0..1), **TWANLocationInformation** (0..1), and **5GSLocationInformation** (0..1). Each of these location classes contains a set of specific attributes related to their respective network types (CS, PS, EPS, TWAN, 5GS).
+
+UML Class Diagram of Sh-Data structure
+
+Figure C.1.1: Sh-Data
+
+Class Sh-Data contains the following attributes:
+
+- An optional instance of CSUserState attribute.
+- An optional instance of PSUserState attribute.
+
+- An optional instance of IMSI attribute.
+- Zero or more instances of IMSPrivateUserIdentity attribute.
+- An optional instance of IMEISV attribute.
+
+Class Sh-Data contains the following classes:
+
+- An optional instance of the class PublicIdentifiers.
+- Zero or more instances of the class RepositoryData.
+- An optional instance of the class Sh-IMS-Data.
+- An optional instance of the class CSLocationInformation.
+- An optional instance of the class PSLocationInformation.
+- An optional instance of the class RegisteredIdentities.
+- An optional instance of the class ImplicitIdentities.
+- An optional instance of the class AllIdentities.
+- An optional instance of the class AliasIdentities.
+- An optional instance of the class DeletedIdentities.
+
+If the AS and the HSS both support the Notif-Eff feature and the AS requires to read more than one Identity Sets of a Public Identity, or regardless whether or not the Notif-Eff feature is supported, the AS has subscribed to be notified of changes to IMSPublicIdentity for more than one Identity Sets (see table 7.6.1), the class PublicIdentifiers shall not be used to convey IMS Public Identities (it shall however still be used to convey the MSISDNs if so requested). Instead the classes RegisteredIdentities, ImplicitIdentities, AllIdentities and AliasIdentities shall be used and they contain the REGISTERED\_IDENTITIES, IMPLICIT\_IDENTITIES, ALL\_IDENTITIES and ALIAS\_IDENTITIES associated with the IMS Public Identity included in the request respectively. See clause 7.6.2 for the detailed information. The class PublicIdentifiers or the one among the four which may be used to contain the corresponding identity set can both be used to convey IMS Public Identities when AS requires only one identity set of a public identity.
+
+If Public Identity(ies) are deleted and the AS has any subscription active for the deleted identity(ies), the HSS shall notify the AS of the deletion of the identity(ies) using the class DeletedIdentities.
+
+Class RepositoryData contains repository data (transparent data) for a given service that are associated to a Public user Identity or a group of alias Public User Identities. It has attributes ServiceIndication, SequenceNumber and ServiceData.
+
+Class CSUserState contains the state of a user in the CS domain. Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7.
+
+Class PSUserState contains the state of a user in the PS domain (SGSN). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7.
+
+NOTE: the fact that attribute State is an enumeration is a difference from what can be carried in the MAP protocol.
+
+Class EPSUserState contains the state of a user in the PS domain (MME). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7. .
+
+Class Sh-5GSUserState contains the state of a user in the PS domain (AMF). Its only attribute, State, is an enumeration whose possible values are defined in clause 7.6.7.
+
+Class CSLocationInformation has the attributes LocationNumber, ServiceAreaID, CellGlobalId, LocationAreaId, GeographicalInformation, GeodeticInformation, VLRNumber, MSCNumber, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, TrackingAreaId, E-UTRANCellGlobalId and LocalTimeZone. They are defined in 7.6.
+
+Class PSLocationInformation has the attributes ServiceAreaId, CellGlobalId, LocationAreaID, RoutingAreaID, GeographicalInformation, GeodeticInformation, SGSNNumber, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6.
+
+Class EPSLocationInformation has the attributes E-UTRANCellGlobalId, TrackingAreaID, GeographicalInformation, GeodeticInformation, MMENAME, AgeOfLocationInformation, CurrentLocationRetrieved, UserCSGInformation, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6.
+
+Class TWANLocationInformation has the attributes TWAN-SSID, TWAN-BSSID, TWAN-PLMNID, CivicAddress, TWANOperatorName, LocalTimeZone and LogicalAccessID. They are defined in 7.6.
+
+Class Sh-5GSLocationInformation has the attributes NRCellGlobalId, E-UTRANCellGlobalId, TrackingAreaID, GeographicalInformation, AMFAddress, SMSFAddress, AgeOfLocationInformation, CurrentLocationRetrieved, VisitedPLMNID, LocalTimeZone and RATtype. They are defined in 7.6.
+
+Class DeletedIdentities contains Public Identities (IMS Public User Identities or Public Service Identities) removed from the HSS.
+
+Class UEReachabilityForIP contains the UE reachability for IP. Its attributes, UEIPReachabilityMME, UEIPReachabilitySGSN, UEIPReachabilityAMF3GPP and UEIPReachabilityAMFnon3GPP are enumerations whose possible values are defined in clause 7.6.17.
+
+Class IMSVoiceOverPSSessionsSupport contains the support of IMS voice over PS at the current access. Its only attribute, SupportIndication, is an enumeration whose possible values are defined in clause 7.6.18.
+
+Class IMSI contains the UE's IMSI. See clause 7.6.24.
+
+Class IMSPrivateUserIdentity contains an IMS Private Identity associated with the IMS Public Identity included in the request.
+
+## C.2 PublicIdentifiers
+
+The following picture details the UML model of the class PublicIdentifiers:
+
+![UML Class Diagram of PublicIdentifiers](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg)
+
+```
+
+classDiagram
+    class PublicIdentifiers {
+        IMSPublicIdentity: SIP URL or Tel_URL
+        IdentityType: enumerated
+        WildcardedPSI: anyURI
+        WildcardedIMPU: anyURI
+        MSISDN: string
+    }
+    class EnhancedIMSPublicIdentifiers {
+        IMSPublicIdentity: SIP URL or Tel_URL
+        IdentityType: enumerated
+    }
+    class ExtendedMSISDN {
+        MSISDN: string
+        MSISDNType: enumerated
+    }
+    PublicIdentifiers "1" *-- "0..n" EnhancedIMSPublicIdentifiers
+    PublicIdentifiers "1" *-- "0..n" ExtendedMSISDN
+  
+```
+
+The diagram shows a UML class model for **PublicIdentifiers**. The **PublicIdentifiers** class is at the top and contains the following attributes: **IMSPublicIdentity** (SIP URL or Tel\_URL), **IdentityType** (enumerated), **WildcardedPSI** (anyURI), **WildcardedIMPU** (anyURI), and **MSISDN** (string). Below it, **EnhancedIMSPublicIdentifiers** and **ExtendedMSISDN** are shown as subclasses, connected by inheritance (indicated by a hollow diamond). **EnhancedIMSPublicIdentifiers** contains **IMSPublicIdentity** (SIP URL or Tel\_URL) and **IdentityType** (enumerated). **ExtendedMSISDN** contains **MSISDN** (string) and **MSISDNType** (enumerated). Both subclasses have a multiplicity of **0..n** at their ends of the inheritance lines.
+
+UML Class Diagram of PublicIdentifiers
+
+**Figure C.2.1: The UML model of the class PublicIdentifiers**
+
+Class **PublicIdentifiers** contains the following attributes:
+
+- Zero or more instances of **IMSPublicIdentity** attribute. Each instance is a Public Identity. See clause 7.6.2 for information about contents.
+- An optional instance of **IdentityType** attribute. If only one instance of **IMSPublicIdentity** attribute is included, then this attribute identifies the identity type in the **IMSPublicIdentity** attribute, it could be either:
+  - A distinct Public User Identity
+  - A distinct Public Service Identity
+
+If more than one instance of **IMSPublicIdentity** attribute is included, this attribute is assumed to apply to all of them.
+
+If **IdentityType** attribute is not present, it is assumed to be a distinct Public User Identity.
+
+If more than one instance of **IMSPublicIdentity** shall be returned, if the identities are of different types the **EnhancedIMSPublicIdentifiers** class should be used instead.
+
+- An optional instance of **WildcardedPSI** attribute, if the Public Service Identity in the request matches a Wildcarded PSI.
+
+NOTE: This attribute can be omitted if this information is conveyed including Wildcarded PSI information element in the response. See clause 6.1.1 and 6.1.3.
+
+- An optional instance of **WildcardedIMPU** attribute, if the Public User Identity in the request matches a Wildcarded IMPU.
+
+NOTE: This attribute can be omitted if this information is conveyed including Wildcarded Public User Identity information element in the response. See clause 6.1.1 and 6.1.3.
+
+- Zero or more instances of **MSISDN** attribute, that contains an MSISDN.
+
+Class **PublicIdentifiers** contains the following classes:
+
+- Zero to more instances of EnhancedIMSPublicIdentifiers. This class is required when more than one instance of IMSPublicIdentity shall be returned and the identities are of different types. See clause 7.6.2 for more information about contents. It includes the following attributes:
+  - One instance of IMSPublicIdentity attribute that contains a Public Identity.
+  - One instance of the IdentityType attribute that identifies the identity type in the IMSPublicIdentity attribute, it could be either:
+    - A distinct Public User Identity
+    - A distinct Public Service Identity
+    - A Wildcarded Public Service Identity
+    - A Wildcarded Public User Identity
+- Zero or more instances of ExtendedMSISDN, only when Additional-MSISDN feature is enabled. It includes the following attributes:
+  - One instance of MSISDN attribute that contains an MSISDN.
+  - One instance of MSISDNType attribute that indicates the MSISDN Type.
+
+**Figure C.2.2: Void**
+
+## C.3 Sh-IMS-Data
+
+The following picture details the UML model of the class Sh-IMS-Data.
+
+![UML Class Diagram for Sh-IMS-Data class structure and its components.](aeb2a26a07219661191294dba528067a_img.jpg)
+
+```
+
+classDiagram
+    class ShIMSData["Sh-IMS-Data"]
+    class SCSCFName["S-CSCFName"] {
+        ServerName: SIP_URL
+    }
+    class IFCs {
+        IFCs: tIFCs
+    }
+    class IMSUserState {
+        IMSState: enumerated
+    }
+    class ChargingInformation["Charging Information"] {
+        Charging Information : tChargingInformation
+    }
+    class DSAI {
+        DSAI Tag: string
+        DSAI Value: enumerated
+    }
+    class ServiceLevelTraceInfo["Service Level Trace Information"] {
+        ServiceLevelTraceInfo: string
+    }
+    class PSIActivation {
+        PSlState: enumerated
+    }
+    class IPAddrSecureBindingInfo["IP Address Secure Binding Information"] {
+        IPv4Address: tIPv4Address
+        IPv6Prefix: tIPv6Prefix
+        IPv6InterfaceIdentifier: tIPv6InterfaceIdentifier
+    }
+    class ServicePriorityLevel["Service Priority Level"] {
+        ServicePriorityLevel: enumerated
+    }
+    class ExtendedPriority {
+        PriorityNamespace: string
+        PriorityLevel: string
+    }
+    class EnhancedSRVCC {
+        STN-SR: tMSISDN
+        UE-SRVCC-Capability: tUE-SRVCC-Capability
+    }
+    class ReferenceLocationInformation["ReferenceLocationInformation"] {
+        AccessType: string
+        AccessInfo: string
+        AccessValue: string
+    }
+    class SMSRegistrationInfo {
+        IP-SM-GW-Number: string
+        SCAddress: tSCAddress
+    }
+    class 5GSRVCC {
+        UE-5G-SRVCC-Capability: tUE-5G-SRVCC-Capability
+    }
+
+    ShIMSData *-- "0..1" SCSCFName
+    ShIMSData *-- "0..1" IFCs
+    ShIMSData *-- "0..1" IMSUserState
+    ShIMSData *-- "0..1" ChargingInformation
+    ShIMSData *-- "0..1" PSIActivation
+    ShIMSData *-- "0..n" DSAI
+    ShIMSData *-- "0..1" ServiceLevelTraceInfo
+    ShIMSData *-- "0..1" IPAddrSecureBindingInfo
+    ShIMSData *-- "0..1" ServicePriorityLevel
+    ShIMSData *-- "0..n" ExtendedPriority
+    ShIMSData *-- "0..1" EnhancedSRVCC
+    ShIMSData *-- "0..1" ReferenceLocationInformation
+    ShIMSData *-- "0..1" SMSRegistrationInfo
+    ShIMSData *-- "0..1" 5GSRVCC
+  
+```
+
+UML Class Diagram for Sh-IMS-Data class structure and its components.
+
+**Figure C.3.1: Sh-IMS-Data**
+
+Each instance of the class Sh-IMS-Data contains 0 or 1 instance of the class S-CSCFName, 0 to 1 instance of the class IFCs, 0 or 1 instance of the class IMSUserState, 0 or 1 instance of the class ChargingInformation, 0 or 1 instance of the class PSIActivation, 0 to n instances of the class DSAI, 0 or 1 instance of the class ServiceLevelTraceInfo, 0 or 1 instance of the class IPAddressSecureBindingInformation, and 0 or 1 instance of the class ReferenceLocationInformation.
+
+Class S-CSCFName contains a SIP URI. See clause 7.6.4 for further details.
+
+Class IFCs contains 0 to n instances of the initial filter criteria of the multimedia public identity that the AS included in the request. The initial filter criteria is defined in 3GPP TS 29.228 [6].
+
+Class IMSUserState contains the registration state of the identity given by the attribute of class Sh-IMS-Data. See clause 7.6 for possible values.
+
+Class Charging Information contains the online and offline charging function addresses. See clause 7.6 for possible values.
+
+Class PSIActivation contains the activation state of the Public Service Identity given by the attribute of class Sh-IMS-Data. See clause 7.6 for possible values.
+
+Class DSAI contains the DSAI Tag and a DSAI Value (reflecting the activation state) for services the user is subscribed to. See clause 7.14 for contents and usage.
+
+Class ServiceLevelTraceInfo contains the Service Level Trace configuration information to enable the Application Server to perform service level tracing related to a specific Public Identifier. See clause 7.6.13 for contents and usage.
+
+Class IPAddressSecureBindingInformation contains either 0 or one IPv4 address, either 0 or one IPv6 prefix and/or IPv6 interface identifier. See clause 7.6.14 for contents and usage.
+
+Class ServicePriorityLevel contains the Service Priority Level allowed for the Public Identity to be used for priority services. See clause 7.6.15 for contents and usage.
+
+Class SMSRegistrationInfo contains the IP-SM-GW-Number and the Service Centre Address. See clause 7.6.16 for further details.
+
+Class Enhanced SRVCC contains the Session Transfer Number (see 3GPP TS 23.003 [11]) and the SRVCC Capability of the UE (see 3GPP TS 23.237 [32]). See clauses 7.6.20 and 7.6.21 respectively for further details.
+
+Class 5G SRVCC contains the 5G SRVCC Capability of the UE (see 3GPP TS 23.237 [32]). See clause 7.6.21A for further details.
+
+Class ExtendedPriority contains the PriorityNamespace and the PriorityLevel information elements. See Clause 7.6.15A for further details.
+
+Class Reference Location Information contains zero or one attribute AccessType, zero or one attribute AccessInfo, and zero or one attribute AccessValue, see 3GPP TS 29.228 [6].
+
+# Annex D (normative): XML schema for the Sh interface user profile
+
+The file ShDataType\_Rel15.xsd, attached to this specification, contains the XML schema for the user profile that is sent over the Sh interface. The user profile XML schema defines the data types that are used in the user profile XML.
+
+The data that is allowed to be sent in the user profile may vary depending on the features supported by the Diameter end points, see 3GPP TS 29.329 [5]. The user profile XML schema file is intended to be used by an XML parser.
+
+The version of the Sh application sending the user profile XML shall be the same as the version of the sent user profile XML and thus it implies the version of the user profile XML schema to be used to validate it.
+
+Tables D.1 and D.2 describe the data types and the dependencies among them that configure the user profile XML schema.
+
+**Table D.1: XML schema for the Sh user profile interface: simple data types**
+
+| Data type             | Tag                  | Base type  | Comments                                                                                                                                                                                                                                                                                           |
+|-----------------------|----------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| tPriority             | Priority             | integer    | >= 0                                                                                                                                                                                                                                                                                               |
+| tProfilePartIndicator | ProfilePartIndicator | enumerated | Possible values:<br>0 (REGISTERED)<br>1 (UNREGISTERED)                                                                                                                                                                                                                                             |
+| tGroupID              | Group                | integer    | >= 0                                                                                                                                                                                                                                                                                               |
+| tRegistrationType     | RegistrationType     | enumerated | Possible values:<br>0 (INITIAL_REGISTRATION)<br>1 (RE-REGISTRATION)<br>2 (DE-REGISTRATION)                                                                                                                                                                                                         |
+| tDefaultHandling      | DefaultHandling      | enumerated | Possible values:<br>0 (SESSION_CONTINUED)<br>1 (SESSION_TERMINATED)                                                                                                                                                                                                                                |
+| tDirectionOfRequest   | SessionCase          | enumerated | Possible values:<br>0 (ORIGINATING_SESSION)<br>1 (TERMINATING_SESSION)<br>2 (TERMINATING_UNREGISTERED)<br>3 (ORIGINATING_UNREGISTERED)<br>4 (ORIGINATING_CDIV)                                                                                                                                     |
+| tIMSUState            | IMSUState            | Enumerated | Possible values:<br>0 (NOT_REGISTERED)<br>1 (REGISTERED)<br>2 (REGISTERED_UNREG_SERVICES)<br>3 (AUTHENTICATION_PENDING)                                                                                                                                                                            |
+| tCSUState             | CSUState             | Enumerated | Possible values (as defined in 3GPP TS 23.078 [14]):<br>0 (CAMELBusy)<br>1 (NetworkDeterminedNotReachable)<br>2 (AssumedIdle)<br>3 (NotProvidedfromVLR)                                                                                                                                            |
+| tPSUState             | PSUState             | Enumerated | Possible values (as defined in 3GPP TS 23.078 [14]):<br>0 (Detached)<br>1 (AttachedNotReachableForPaging)<br>2 (AttachedReachableForPaging)<br>3 (ConnectedNotReachableForPaging)<br>4 (ConnectedReachableForPaging)<br>5 (NotProvidedFromSGSN or MME or AMF)<br>6 (NetworkDeterminedNotReachable) |
+| tLocationNumber       | LocationNumber       | string     | Syntax described in ITU-T Q.763 [9] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length >=4 and <=16 (multiples of 4).                                                                                                                                                                     |
+| tCellGlobalId         | CellGlobalId         | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 12.                                                                                                                                                                                          |
+| tServiceAreaId        | ServiceAreaId        | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 12.                                                                                                                                                                                          |
+
+|                           |                                                                                                  |            |                                                                                                                                                               |
+|---------------------------|--------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| tLocationAreaId           | LocationAreaId                                                                                   | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 8.                                                      |
+| tRoutingAreaId            | RoutingAreaId                                                                                    | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 8.                                                      |
+| tGeographicalInformation  | GeographicalInformation                                                                          | string     | Syntax described in 3GPP TS 29.002 (base 64 encoded according to IETF RFC 2045).<br>Length = 12.                                                              |
+| tGeodeticInformation      | GeodeticInformation                                                                              | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 16.                                                     |
+| tAgeOfLocationInformation | AgeOfLocationInformation                                                                         | integer    | >=0, <=32767                                                                                                                                                  |
+| tCSGId                    | CSGId                                                                                            | string     | Syntax described in 3GPP TS 29.002 [13] i.e. 5 octets BER encoded value of 27-bit BIT STRING (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 8. |
+| tAccessMode               | AccessMode                                                                                       | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 4.                                                      |
+| tTrackingAreaId           | TrackingAreaId                                                                                   | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 8.                                                      |
+| tE-UTRANCellGlobalId      | E-UTRANCellGlobalId                                                                              | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length = 12.                                                     |
+| tNRCellGlobalId           | NRCellGlobalId                                                                                   | string     | Concatenation of MCC, MNC and NrCellId. NrCellId syntax is described in 3GPP TS 29.571 [46].<br>Length = 14 or 15.                                            |
+| tAddressString            | Address                                                                                          | string     | Syntax described in 3GPP TS 29.002 [13] (Base64 encoded according to IETF RFC 2045 [15]).<br>Length >= 4 and <=28 (multiples of 4).                           |
+| tMSISDN                   | MSISDN, STN-SR, CSRN                                                                             | string     | Number structure described in 3GPP TS 23.003 [11]. ASCII encoded according to ANSI X3.4 [20].                                                                 |
+| tSIP_URL                  | IMSPublicIdentity                                                                                | anyURI     | Syntax described in IETF RFC 3261 [16]. Wildcarded IMPU and Wildcarded PSI syntax described in 3GPP TS 23.003.                                                |
+| tTEL_URL                  | IMSPublicIdentity                                                                                | anyURI     | Syntax described in IETF RFC 3966 [17]. Wildcarded IMPU and Wildcarded PSI syntax described in 3GPP TS 23.003.                                                |
+| tDiameterURI              | DiameterURI                                                                                      | string     | Syntax of a Diameter URI as described in IETF RFC 6733 [44]                                                                                                   |
+| tIMSPublicIdentity        | IMSPublicIdentity                                                                                | (union)    | Union of tSIP_URL and tTEL_URL                                                                                                                                |
+| tIdentityType             | IdentityType                                                                                     | enumerated | Possible values:<br>0 (PUBLIC_USER_IDENTITY)<br>1 (DISTINCT_PSI)<br>2 (WILDCARDED_PSI)<br>3 (WILDCARDED_IMPU)                                                 |
+| tWildcardedPSI            | WildcardedPSI                                                                                    | anyURI     | Syntax described in 3GPP TS 23.003 [11].                                                                                                                      |
+| tWildcardedIMPU           | WildcardedIMPU                                                                                   | anyURI     | Syntax described in 3GPP TS 23.003 [11].                                                                                                                      |
+| tServiceInfo              | ServiceInfo                                                                                      | string     |                                                                                                                                                               |
+| tDSA-Tag                  | DSA-Tag                                                                                          | string     |                                                                                                                                                               |
+| tString                   | RequestURI, Method, Header, Content, Line, MMENName, AccessType, AccessInfo, AccessValue, IMEISV | string     |                                                                                                                                                               |
+| tBool                     | ConditionTypeCNF, ConditionNegated                                                               | boolean    | Possible values:<br>0 (false)<br>1 (true)                                                                                                                     |
+| tSequenceNumber           | SequenceNumber                                                                                   | integer    | >=0, <=65535                                                                                                                                                  |
+| tPSIActivation            | PSIActivation                                                                                    | enumerated | Possible Values:<br>0 (INACTIVE)<br>1 (ACTIVE)                                                                                                                |
+
+|                               |                              |            |                                                                                                                                                                                                                                                                 |
+|-------------------------------|------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| tDSAI-Value                   | DSAI-Value                   | enumerated | Possible values are:<br>0 (ACTIVE)<br>1 (INACTIVE)                                                                                                                                                                                                              |
+| tServiceLevelTraceInfo        | ServiceLevelTraceInfo        | String     | Syntax described in 3GPP TS 24.323 [45]                                                                                                                                                                                                                         |
+| tIPv4Address                  | IPv4Address                  | String     | IPv4 address is represented in dotted-decimal notation (a sequence of four decimal numbers in the range 0 to 255, separated by ".", for example 192.168.1.1.                                                                                                    |
+| tIPv6Prefix                   | IPv6Prefix                   | String     | ASCII encoded for the text representation of the address prefix. Syntax described in IETF RFC 4291 [24] and IETF RFC 5952 [41].                                                                                                                                 |
+| tIPv6InterfaceIdentifier      | IPv6InterfaceIdentifier      | String     | ASCII encoded for the text representation of the address. Syntax described in IETF RFC 4291 [24] and IETF RFC 5952 [41].                                                                                                                                        |
+| tServicePriorityLevel         | ServicePriorityLevel         | enumerated | Possible values:<br>0 (Highest priority)<br>1<br>2<br>3<br>4 (Lowest priority)                                                                                                                                                                                  |
+| tUEIPReachabilityMME          | UEIPReachabilityMME          | enumerated | Possible values:<br>0 (REACHABLE)                                                                                                                                                                                                                               |
+| tUEIPReachabilitySGSN         | UEIPReachabilitySGSN         | enumerated | Possible values:<br>0 (REACHABLE)                                                                                                                                                                                                                               |
+| tUEIPReachabilityAMF3GPP      | UEIPReachabilityAMF3GPP      | enumerated | Possible values:<br>0 (REACHABLE)                                                                                                                                                                                                                               |
+| tUEIPReachabilityAMFnon3GPP   | UEIPReachabilityAMFnon3GPP   | enumerated | Possible values:<br>0 (REACHABLE)                                                                                                                                                                                                                               |
+| tIP-SM-GW-Number              | IP-SM-GW-Number              | String     | IP-SM-GW is an E.164 address where the digits are ASCII encoded according to ANSI X3.4 [20]. Leading indicators for the nature of address and the numbering plan shall not be included.                                                                         |
+| tIMSVoiceOverPSSessionSupport | IMSVoiceOverPSSessionSupport | enumerated | Possible Values:<br>0 (IMS-VOICE-OVER-PS-NOT-SUPPORTED)<br>1 (IMS-VOICE-OVER-PS-SUPPORTED)<br>2 (IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN)                                                                                                                             |
+| tRATtype                      | RATtype                      | enumerated | Possible Values are defined in 3GPP TS 29.212 [28], clause 5.3.31                                                                                                                                                                                               |
+| tAccessType                   | AccessType                   | enumerated | Possible Values:<br>0 (3GPP-ACCESS)<br>1 (NON-3GPP-ACCESS)                                                                                                                                                                                                      |
+| tDateTime                     | LastUEActivityTime           | dateTime   |                                                                                                                                                                                                                                                                 |
+| tUE-SRVCC-Capability          | UE-SRVCC-Capability          | enumerated | Possible Values:<br>0 (UE-SRVCC-CAPABILITY-NOT-SUPPORTED)<br>1 (UE-SRVCC-CAPABILITY-SUPPORTED)                                                                                                                                                                  |
+| tPriorityNamespace            | PriorityNamespace            | string     | Possible values are those of the namespaces that are defined in IETF RFC 4412 [25] or defined according to the IANA registration procedure described in IETF RFC 4412 [25] for Resource-Priority Namespaces.                                                    |
+| tPriorityLevel                | PriorityLevel                | string     | Possible values depend on the PriorityNamespace and are specified with the associated namespace that is defined in IETF RFC 4412 [25] or defined according to the IANA registration procedure described in IETF RFC 4412 [25] for Resource-Priority Namespaces. |
+
+|                         |                        |              |                                                                                                                                                                                          |
+|-------------------------|------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| tSCAddress              | SCAddress              | string       | SCAddress is an E.164 address where the digits are ASCII encoded according to ANSI X3.4 [20]. Leading indicators for the nature of address and the numbering plan shall not be included. |
+| tVisitedPLMNID          | VisitedPLMNID          | string       | Consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) as described in 3GPP TS 23.003 [11]. It is a string with 3 digits MCC and 2 or 3 digits MNC.                         |
+| tTimeZone               | TimeZone               | string       | Syntax described in 3GPP TS 29.272 [26]                                                                                                                                                  |
+| tDaylightSavingTime     | DaylightSavingTime     | enumerated   | Possible values are defined in 3GPP TS 29.272 [26].                                                                                                                                      |
+| tMSISDNType             | MSISDNType             | enumerated   | Possible values:<br>0 (BASIC)<br>1 (ADDITIONAL)<br>See 3GPP TS 23.003 [11] for the definition of Additional-MSISDN.                                                                      |
+| tIMSI                   | IMSI                   | string       | Number structure described in 3GPP TS 23.003 [11]. ASCII encoded according to ANSI X3.4 [20].                                                                                            |
+| tTWAN-SSID              | TWAN-SSID              | string       | Syntax described in 3GPP TS 29.273 [34].                                                                                                                                                 |
+| tTWAN-BSSID             | TWAN-BSSID             | string       | Syntax described in 3GPP TS 29.273 [34].                                                                                                                                                 |
+| tTWANOperatorName       | TWANOperatorName       | string       | Syntax described in 3GPP TS 23.003 [11].                                                                                                                                                 |
+| tCivicAddress           | CivicAddress           | base64Binary | Syntax described in clause 3.1 of IETF RFC 4776 [35] excluding the first 3 octets (Base64 encoded according to IETF RFC 2045 [15]).                                                      |
+| tLogicalAccessID        | LogicalAccessID        | string       | Syntax described in ETSI ES 283 034 [37].                                                                                                                                                |
+| tIMSPrivateUserIdentity | IMSPrivateUserIdentity | string       | Syntax described in 3GPP TS 23.003 [11]                                                                                                                                                  |
+| tUE-5G-SRVCC-Capability | UE-5G-SRVCC-Capability | enumerated   | Possible Values:<br>0 (UE-5G-SRVCC-CAPABILITY-NOT-SUPPORTED)<br>1 (UE-5G-SRVCC-CAPABILITY-SUPPORTED)                                                                                     |
+
+Table D.2: XML schema for the Sh user profile interface: complex data types
+
+| Data type           | Tag            | Compound of               |                          |             |
+|---------------------|----------------|---------------------------|--------------------------|-------------|
+|                     |                | Tag                       | Type                     | Cardinality |
+| tSh-Data            | Sh-Data        | PublicIdentifiers         | tPublicIdentity          | 0 to 1      |
+|                     |                | RepositoryData            | tTransparentData         | 0 to n      |
+|                     |                | Sh-IMS-Data               | tShIMSData               | 0 to 1      |
+|                     |                | CSLocationInformation     | tCSLocationInformation   | 0 to 1      |
+|                     |                | PSLocationInformation     | tPSLocationInformation   | 0 to 1      |
+|                     |                | CSUserState               | tCSUserState             | 0 to 1      |
+|                     |                | PSUserState               | tPSUserState             | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension       | 0 to 1      |
+| tSh-Data-Extension  | Extension      | RegisteredIdentites       | tPublicIdentity          | 0 to 1      |
+|                     |                | ImplicitIdentities        | tPublicIdentity          | 0 to 1      |
+|                     |                | AllIdentities             | tPublicIdentity          | 0 to 1      |
+|                     |                | AliasIdentities           | tPublicIdentity          | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension2      | 0 to 1      |
+| tSh-Data-Extension2 | Extension      | DeletedIdentities         | tPublicIdentity          | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension3      | 0 to 1      |
+| tSh-Data-Extension3 | Extension      | TADSinformation           | tTADSinformation         | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension4      | 0 to 1      |
+| tSh-Data-Extension4 | Extension      | EPSUserState              | tPSUserState             | 0 to 1      |
+|                     |                | EPSLocationInformation    | tEPSLocationInformation  | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension5      | 0 to 1      |
+| tSh-Data-Extension5 | Extension      | IMSI                      | tIMSI                    | 0 to 1      |
+|                     |                | TWANLocationInformation   | tTWANLocationInformation | 0 to 1      |
+|                     |                | IMSPPrivateUserIdentity   | tIMSPPrivateUserIdentity | 0 to n      |
+|                     |                | Extension                 | tSh-Data-Extension6      | 0 to 1      |
+| tSh-Data-Extension6 | Extension      | IMEISV                    | tString (NOTE 6)         | 0 to 1      |
+|                     |                | Extension                 | tSh-Data-Extension7      | 0 to 1      |
+| tSh-Data-Extension7 | Extension      | Sh-5GSLocationInformation | t5GSLocationInformation  | 0 to 1      |
+|                     |                | Sh-5GSUserState           | tPSUserState             | 0 to 1      |
+| tTransparentData    | RepositoryData | ServiceIndication         | string                   | 1           |
+|                     |                | SequenceNumber            | tSequenceNumber          | 1           |
+|                     |                | ServiceData               | tServiceData             | 0 to 1      |
+| tServiceData        | any            | any                       | any                      | 1           |
+| tIFCs               | IFCs           | InitialFilterCriteria     | tInitialFilterCriteria   | 0 to n      |
+| tShIMSData          | Sh-IMS-Data    | SCSCFName                 | tSIP_URL                 | 0 to 1      |
+|                     |                | IFCs                      | tIFCs                    | 0 to 1      |
+|                     |                | IMSUserState              | tIMSUserState            | 0 to 1      |
+
+|                      |           |                              |                               |                    |
+|----------------------|-----------|------------------------------|-------------------------------|--------------------|
+| tShIMSDataExtension  | Extension | ChargingInformation          | tChargingInformation          | 0 to 1             |
+|                      |           | Extension                    | tShIMSDataExtension           | (0 to 1)           |
+| tShIMSDataExtension2 | Extension | PSIActivation                | tPSIActivation                | (0 to 1)           |
+|                      |           | Extension                    | tShIMSDataExtension2          | 0 to 1             |
+| tShIMSDataExtension3 | Extension | DSAI                         | tDSAI                         | 0 to n             |
+|                      |           | Extension                    | tShIMSDataExtension3          | (0 to 1)           |
+|                      |           | ServiceLevelTraceInfo        | tServiceLevelTraceInfo        | (0 to 1)           |
+|                      |           | IPv4Address                  | tIPv4Address                  | 0 to 1             |
+|                      |           | IPv6Prefix                   | tIPv6Prefix                   | 0 to 1             |
+|                      |           | IPv6InterfaceIdentifier      | tIPv6InterfaceIdentifier      | 0 to 1             |
+|                      |           | ServicePriorityLevel         | tServicePriorityLevel         | 0 to 1             |
+|                      |           | UEReachabilityForIP          | tUEReachabilityForIP          | 0 to 1             |
+|                      |           | SMSRegistrationInfo          | tSMSRegistrationInfo          | 0 to 1             |
+| tShIMSDataExtension4 | Extension | Extension                    | tShIMSDataExtension4          | 0 to 1             |
+|                      |           | STN-SR                       | tMSISDN                       | 0 to 1             |
+|                      |           | UE-SRVCC-Capability          | tUE-SRVCC-Capability          | 0 to 1             |
+|                      |           | ExtendedPriority             | tExtendedPriority             | 0 to n             |
+|                      |           | CSRN                         | tMSISDN                       | 0 to 1             |
+| tShIMSDataExtension5 | Extension | Extention                    | tShIMSDataExtension5          | 0 to 1             |
+|                      |           | ReferenceLocationInformation | tReferenceLocationInformation | 0 to n<br>(NOTE 7) |
+|                      |           | Extension                    | tShIMSDataExtension6          | 0 to 1             |
+
+|                                   |                                  |                          |                                   |        |
+|-----------------------------------|----------------------------------|--------------------------|-----------------------------------|--------|
+| tShIMSDDataExtension6             | Extension                        | MTRRIndication           | tBool                             | 0 to 1 |
+|                                   |                                  | Extension                | tShIMSDDataExtension7             | 0 to 1 |
+| tShIMSDDataExtension7             | Extension                        | UE-5G-SRVCC-Capability   | tUE-5G-SRVCC-Capability           | 0 to 1 |
+| tReferenceLocationInformation     | ReferenceLocationInformation     | AccessType               | tString (NOTE 3)                  | 0 to 1 |
+|                                   |                                  | AccessInfo               | tString (NOTE 3)                  | 0 to 1 |
+|                                   |                                  | AccessValue              | tString (NOTE 3)                  | 0 to 1 |
+| tCSLocationInformation            | CSLocationInformation            | LocationNumber           | tLocationNumber                   | 0 to 1 |
+|                                   |                                  | CellGlobalId             | tCellGlobalId                     | 0 to 1 |
+|                                   |                                  | ServiceAreaId            | tServiceAreaId                    | 0 to 1 |
+|                                   |                                  | LocationAreaId           | tLocationAreaId                   | 0 to 1 |
+|                                   |                                  | GeographicalInformation  | tGeographicalInformation          | 0 to 1 |
+|                                   |                                  | GeodeticInformation      | tGeodeticInformation              | 0 to 1 |
+|                                   |                                  | VLRNumber                | tISDNAddress                      | 0 to 1 |
+|                                   |                                  | MSCNumber                | tISDNAddress                      | 0 to 1 |
+|                                   |                                  | CurrentLocationRetrieved | tBool                             | 0 to 1 |
+|                                   |                                  | AgeOfLocationInformation | tAgeOfLocationInformation         | 0 to 1 |
+|                                   |                                  | Extension                | tCSLocationInformation-Extension  | 0 to 1 |
+| tCSLocationInformation-Extension  | CSLocationInformation-Extension  | UserCSGInformation       | tUserCSGInformation               | 0 to 1 |
+|                                   |                                  | Extension                | tCSLocationInformation-Extension2 | 0 to 1 |
+| tCSLocationInformation-Extension2 | CSLocationInformation-Extension2 | E-UTRANCellGlobalId      | tE-UTRANCellGlobalId              | 0 to 1 |
+|                                   |                                  | TrackingAreaId           | tTrackingAreaId                   | 0 to 1 |
+|                                   |                                  | Extension                | tCSLocationInformation-Extension3 | 0 to 1 |
+| tCSLocationInformation-Extension3 | CSLocationInformation-Extension3 | LocalTimeZone            | tLocalTimeZone                    | 0 to 1 |
+| tPSLocationInformation            | PSLocationInformation            | CellGlobalId             | tCellGlobalId                     | 0 to 1 |
+|                                   |                                  | ServiceAreaId            | tServiceAreaId                    | 0 to 1 |
+|                                   |                                  | LocationAreaId           | tLocationAreaId                   | 0 to 1 |
+|                                   |                                  | RoutingAreaId            | tRoutingAreaId                    | 0 to 1 |
+|                                   |                                  | GeographicalInformation  | tGeographicalInformation          | 0 to 1 |
+|                                   |                                  | GeodeticInformation      | tGeodeticInformation              | 0 to 1 |
+|                                   |                                  | SGSNNNumber              | tISDNAddress                      | 0 to 1 |
+|                                   |                                  | CurrentLocationRetrieved | tBool                             | 0 to 1 |
+|                                   |                                  | AgeOfLocationInformation | tAgeOfLocationInformation         | 0 to 1 |
+|                                   |                                  | Extension                | tPSLocationInformation-Extension  | 0 to 1 |
+| tPSLocationInformation-Extension  | PSLocationInformation-Extension  | UserCSGInformation       | tUserCSGInformation               | 0 to 1 |
+|                                   |                                  | Extension                | tPSLocationInformation-Extension2 | 0 to 1 |
+| tPSLocationInformation-Extension2 | PSLocationInformation-Extension2 | VisitedPLMNID            | tVisitedPLMNID                    | 0 to 1 |
+|                                   |                                  | LocalTimeZone            | tLocalTimeZone                    | 0 to 1 |
+|                                   |                                  | RATtype                  | tRATtype                          | 0 to 1 |
+
+|                                    |                                   |                              |                                    |        |
+|------------------------------------|-----------------------------------|------------------------------|------------------------------------|--------|
+| tLocalTimeZone                     | LocalTimeZone                     | TimeZone                     | tTimeZone                          | 1      |
+|                                    |                                   | DaylightSavingTime           | tDaylightSavingTime                | 1      |
+| tEPSLocationInformation            | EPSLocationInformation            | E-UTRANCellGlobalId          | tE-UTRANCellGlobalId               | 0 to 1 |
+|                                    |                                   | TrackingAreaId               | tTrackingAreaId                    | 0 to 1 |
+|                                    |                                   | GeographicalInformation      | tGeographicalInformation           | 0 to 1 |
+|                                    |                                   | GeodeticInformation          | tGeodeticInformation               | 0 to 1 |
+|                                    |                                   | MMENName                     | tString                            | 0 to 1 |
+|                                    |                                   | CurrentLocationRetrieved     | tBool                              | 0 to 1 |
+|                                    |                                   | AgeOfLocationInformation     | tAgeOfLocationInformation          | 0 to 1 |
+|                                    |                                   | UserCSGInformation           | tUserCSGInformation                |        |
+|                                    |                                   | Extension                    | tEPSLocationInformation-Extension  | 0 to 1 |
+| tEPSLocationInformation-Extension  | EPSLocationInformation-Extension  | VisitedPLMNID                | tVisitedPLMNID                     | 0 to 1 |
+|                                    |                                   | LocalTimeZone                | tLocalTimeZone                     | 0 to 1 |
+|                                    |                                   | Extension                    | tEPSLocationInformation-Extension2 | 0 to 1 |
+| tEPSLocationInformation-Extension2 | EPSLocationInformation-Extension2 | RATtype                      | tRATtype                           | 0 to 1 |
+| tSh-5GSLocationInformation         | Sh-5GSLocationInformation         | NRCellGlobalId               | tNRCellGlobalId                    | 0 to 1 |
+|                                    |                                   | E-UTRANCellGlobalId          | tE-UTRANCellGlobalId               | 0 to 1 |
+|                                    |                                   | TrackingAreaId               | tTrackingAreaId                    | 0 to 1 |
+|                                    |                                   | GeographicalInformation      | tGeographicalInformation           | 0 to 1 |
+|                                    |                                   | AMFAddress                   | tString                            | 0 to 1 |
+|                                    |                                   | SMSFAddress                  | tString                            | 0 to 1 |
+|                                    |                                   | CurrentLocationRetrieved     | tBool                              | 0 to 1 |
+|                                    |                                   | AgeOfLocationInformation     | tAgeOfLocationInformation          | 0 to 1 |
+|                                    |                                   | VisitedPLMNID                | tVisitedPLMNID                     | 0 to 1 |
+|                                    |                                   | LocalTimeZone                | tLocalTimeZone                     | 0 to 1 |
+| tUserCSGInformation                | UserCSGInformation                | RATtype                      | tRATtype                           | 0 to 1 |
+|                                    |                                   | CSGId                        | tCSGId                             | 1      |
+| tUserCSGInformation-Extension      | UserCSGInformation-Extension      | Extension                    | tUserCSGInformation-Extension      | 0 to 1 |
+|                                    |                                   | AccessMode                   | tAccessMode                        | 0 to 1 |
+|                                    |                                   | CMI                          | tBool                              | 0 to 1 |
+| tTADSInformation                   | TADSInformation                   | IMSVoiceOverPSSessionSupport | tIMSVoiceOverPSSessionSupport      | 1      |
+|                                    |                                   | RATtype                      | tRATtype                           | 0 to 1 |
+|                                    |                                   | Extension                    | tTADSInformationExtension          | 0 to 1 |
+| tTWANLocationInformation           | TWANLocationInformation           | TWAN-SSID                    | tTWAN-SSID                         | 0 to 1 |
+|                                    |                                   | TWAN-BSSID                   | tTWAN-BSSID                        | 0 to 1 |
+|                                    |                                   | TWAN-PLMNID                  | tVisitedPLMNID                     | 0 to 1 |
+|                                    |                                   | CivicAddress                 | tCivicAddress                      | 0 to n |
+|                                    |                                   | TWANOperatorName             | tTWANOperatorName                  | 0 to 1 |
+|                                    |                                   | LocalTimeZone                | tLocalTimeZone                     | 0 to 1 |
+|                                    |                                   | LogicalAccessID              | tLogicalAccessID                   | 0 to 1 |
+| tTADSInformationExtension          | TADSInformationExtension          | LastUEActivityTime           | tDateTime                          | 0 to 1 |
+|                                    |                                   | Extension                    | tTADSInformationExtension2         | 0 to 1 |
+| tTADSInformationExtension2         | TADSInformationExtension2         | AccessType                   | tAccessType                        | 0 to 1 |
+| tISDNAddress                       | SGSNNumber, VLRNumber, MSCNumber  | Address                      | tAddressString                     | 1      |
+
+|                            |                                                                                                                |                                          |                             |                    |
+|----------------------------|----------------------------------------------------------------------------------------------------------------|------------------------------------------|-----------------------------|--------------------|
+| tPublicIdentity            | PublicIdentifiers, RegisteredIdentities, ImplicitIdentities, AllIdentities, AliasIdentities, DeletedIdentities | IMSPublicIdentity                        | tIMSPublicIdentity          | 0 to n             |
+|                            |                                                                                                                | MSISDN                                   | tMSISDN                     | 0 to n             |
+|                            |                                                                                                                | Extension                                | tPublicIdentityExtension    | 0 to 1)            |
+| tPublicIdentityExtension   | Extension                                                                                                      | IdentityType                             | tIdentityType               | (0 to 1)           |
+|                            |                                                                                                                | WildcardedPSI                            | tWildcardedPSI              | (0 to 1)           |
+|                            |                                                                                                                | Extension                                | tPublicIdentityExtension2   | (0 to 1)           |
+| tPublicIdentityExtension2  | Extension                                                                                                      | WildcardedIMPU                           | tWildcardedIMPU             | (0 to 1)           |
+|                            |                                                                                                                | Extension                                | tPublicIdentityExtension3   | 0 to 1             |
+| tPublicIdentityExtension3  | Extension                                                                                                      | ExtendedMSISDN                           | tExtendedMSISDN             | 0 to n<br>(NOTE 5) |
+|                            |                                                                                                                | Extension                                | tPublicIdentityExtension4   | 0 to 1             |
+| tEnhancedIMSPublicIdentity | EnhancedIMSPublicIdentifiers                                                                                   | EnhancedIMSPublicIdentifiers             | tEnhancedIMSPublicIdentity  | 0 to n             |
+|                            |                                                                                                                | IMSPublicIdentity                        | tIMSPublicIdentity          | 1                  |
+| tInitialFilterCriteria     | InitialFilterCriteria                                                                                          | IdentityType                             | tIdentityType               | 1                  |
+|                            |                                                                                                                | Priority                                 | tPriority                   | 1                  |
+|                            |                                                                                                                | TriggerPoint                             | tTrigger                    | 0 to 1             |
+|                            |                                                                                                                | ApplicationServer                        | tApplicationServer          | 1                  |
+| tTrigger                   | TriggerPoint                                                                                                   | ProfilePartIndicator                     | tProfilePartIndicator       | 0 to 1             |
+|                            |                                                                                                                | ConditionTypeCNF                         | tBool                       | 1                  |
+| tSePoTri                   | SPT                                                                                                            | SPT                                      | tSePoTri                    | 1 to n             |
+|                            |                                                                                                                | ConditionNegated                         | tBool                       | 0 to 1             |
+|                            |                                                                                                                | Group                                    | tGroupID                    | 1 to n             |
+|                            |                                                                                                                | RequestURI                               | tString                     | 1                  |
+|                            |                                                                                                                | Method                                   | tString                     | 1                  |
+|                            |                                                                                                                | SIPHeader                                | tHeader                     | 1                  |
+|                            |                                                                                                                | SessionCase                              | tDirectionOfRequest         | 1                  |
+|                            |                                                                                                                | SessionDescription                       | tSessionDescription         | 1                  |
+| tSePoTriExtension          | Extension                                                                                                      | Extension                                | tSePoTriExtension           | (0 to 1)           |
+|                            |                                                                                                                | RegistrationType                         | tRegistrationType           | (0 to 2)           |
+| tHeader                    | SIPHeader                                                                                                      | Header                                   | tString                     | 1                  |
+|                            |                                                                                                                | Content                                  | tString                     | 0 to 1             |
+| tSessionDescription        | SessionDescription                                                                                             | Line                                     | tString                     | 1                  |
+|                            |                                                                                                                | Content                                  | tString                     | 0 to 1             |
+| tApplicationServer         | ApplicationServer                                                                                              | ServerName                               | tSIP_URL                    | 1                  |
+|                            |                                                                                                                | DefaultHandling                          | tDefaultHandling            | 0 to 1             |
+|                            |                                                                                                                | ServiceInfo                              | tServiceInfo                | 0 to 1             |
+|                            |                                                                                                                | Extension                                | tApplicationServerExtension | 0 to 1             |
+| tIncludeRegisterRequest    | IncludeRegisterRequest                                                                                         | IncludeRegisterRequest                   | tIncludeRegisterRequest     | 0 to 1             |
+|                            |                                                                                                                | IncludeRegisterResponse                  | tIncludeRegisterResponse    | 0 to 1             |
+| tChargingInformation       | ChargingInformation                                                                                            | (NOTE 4)                                 | (NOTE 4)                    | 0 to 1             |
+|                            |                                                                                                                | (NOTE 4)                                 | (NOTE 4)                    | 0 to 1             |
+|                            |                                                                                                                | PrimaryEventChargingFunctionName         | tDiameterURI                | 0 to 1<br>(NOTE 2) |
+|                            |                                                                                                                | SecondaryEventChargingFunctionName       | tDiameterURI                | 0 to 1             |
+|                            |                                                                                                                | PrimaryCharging CollectionFunctionName   | tDiameterURI                | 0 to 1<br>(NOTE 2) |
+|                            |                                                                                                                | SecondaryCharging CollectionFunctionName | tDiameterURI                | 0 to 1             |
+
+|                                |                              |                            |                                |          |
+|--------------------------------|------------------------------|----------------------------|--------------------------------|----------|
+| tDSAI                          | DSAI                         | DSAI-Tag                   | tDSAI-Tag                      | 1        |
+|                                |                              | DSAI-Value                 | tDSAI-Value                    | 1        |
+| tUEReachabilityForIP           | UEReachabilityForIP          | UEIPReachabilityMME        | tUEIPReachabilityMME           | (0 to 1) |
+|                                |                              | Extension                  | tUEReachabilityForIPExtension  | (0 to 1) |
+| tUEReachabilityForIPExtension  | Extension                    | UEIPReachabilitySGSN       | tUEIPReachabilitySGSN          | (0 to 1) |
+|                                |                              | Extension                  | tUEReachabilityForIPExtension2 | (0 to 1) |
+| tUEReachabilityForIPExtension2 | Extension                    | UEIPReachabilityAMF3GPP    | tUEIPReachabilityAMF3GPP       | (0 to 1) |
+|                                |                              | UEIPReachabilityAMFnon3GPP | tUEIPReachabilityAMFnon3GPP    | (0 to 1) |
+| tSMSRegistrationInfo           | SMSRegistrationInfo          | IP-SM-GW-Number            | tIP-SM-GW-Number               | 1        |
+|                                |                              | Extension                  | tSMSRegistrationInfoExtension  | (0 to 1) |
+| tSMSRegistrationInfoExtension  | SMSRegistrationInfoExtension | SCAddress                  | tSCAddress                     | (0 to 1) |
+| tExtendedPriority              | ExtendedPriority             | PriorityNamespace          | tPriorityNamespace             | 1        |
+|                                |                              | PriorityLevel              | tPriorityLevel                 | 1        |
+| tExtendedMSISDN                | ExtendedMSISDN               | MSISDN                     | tMSISDN                        | 1        |
+|                                |                              | MSISDNType                 | tMSISDNType                    | 1        |
+
+NOTE 1: "n" shall be interpreted as non-bounded.  
+NOTE 2: At least one of these two information elements (PrimaryEventChargingFunctionName or PrimaryChargingCollectionFunctionName) shall be present.  
+NOTE 3: The syntax of AccessType, AccessInfo and AccessValue is as described in 3GPP TS 29.228 [6].  
+NOTE 4: empty cells shall be interpreted as complex XML elements without defined content.  
+NOTE 5: PublicIdentifiers contains ExtendedMSISDN in addition to MSISDN when Additional-MSISDN feature is enabled.  
+NOTE 6: Syntax described in 3GPP TS 23.003 [11]; it shall contain either an IMEI value (a string of 14 digits) or an IMEISV value (a string of 16 digits).  
+NOTE 7: The HSS shall not send more than one instance of ReferenceLocationInformation and if the Application Server receives more than one instance of ReferenceLocationInformation it may arbitrarily pick one for further processing.
+
+# --- Annex E (informative): T-ADS request handling in the HSS
+
+E.1 T-ADS request handling in the HSS The following figure shows a possible detailed handling of T-ADS Information request in the HSS:
+
+![Flowchart for T-ADS request handling in the HSS.](61a7f401eb46fe99a71f27bc37493f04_img.jpg)
+
+Procedure in the HSS to handle T-ADS requests from the AS via Sh or MAP-J
+
+Signals to/from the left are to/from the MME or SGSN  
+ Signals to/from the right are to/from the AS
+
+```
+
+    graph TD
+        Idle1([Idle]) --> TADS[T-ADS request]
+        TADS --> MMEReg{MME  
+registered}
+        
+        MMEReg -- no --> SGSNReg1{SGSN  
+registered}
+        MMEReg -- yes --> SGSNReg2{SGSN  
+registered}
+        
+        SGSNReg1 -- no --> NOTSUP[NOT  
+SUPPORTED]
+        NOTSUP --> Idle2([Idle])
+        
+        SGSNReg1 -- yes --> HomogSGSN{Homog.  
+Support/  
+Non-  
+support in  
+SGSN}
+        HomogSGSN -- yes --> QuerySuppSGSN{Query  
+supported  
+in SGSN}
+        HomogSGSN -- no --> QuerySuppSGSN
+        
+        QuerySuppSGSN -- no --> UNKNOWN1[UNKNOWN]
+        QuerySuppSGSN -- yes --> QuerySGSN[Query SGSN]
+        QuerySGSN --> WaitSGSN([Wait for  
+SGSN])
+        WaitSGSN --> RespSGSN[Response from  
+SGSN]
+        RespSGSN --> RespAS1[Response to AS]
+        RespAS1 --> Idle3([Idle])
+        UNKNOWN1 --> Idle3
+
+        SGSNReg2 -- no --> HomogMME{Homog.  
+Support/  
+Non-  
+support in  
+MME}
+        SGSNReg2 -- yes --> GnGp{Gn/Gp-  
+SGSN}
+        
+        GnGp -- yes --> HomogSGSN
+        GnGp -- "no / unknown" --> MMEComb{MME and  
+SGSN are  
+combined}
+        
+        MMEComb -- yes --> C((C))
+        MMEComb -- no --> both((both))
+        
+        HomogMME -- yes --> QuerySuppMME{Query  
+supported  
+in MME}
+        HomogMME -- no --> QuerySuppMME
+        
+        QuerySuppMME -- no --> UNKNOWN2[UNKNOWN]
+        QuerySuppMME -- yes --> QueryMME[Query MME]
+        QueryMME --> WaitMME([Wait for MME])
+        WaitMME --> RespMME[Response from  
+MME]
+        RespMME --> RespAS2[Response to AS]
+        RespAS2 --> Idle4([Idle])
+        UNKNOWN2 --> Idle4
+    
+```
+
+Flowchart for T-ADS request handling in the HSS.
+
+![Flowchart for Homogeneous Support in MME and SGSN](fcc757566216206ceddbd6c775e8db02_img.jpg)
+
+This flowchart determines the homogeneous support status based on MME and SGSN capabilities. It starts with a 'both' connector and branches based on 'Homog. Support in MME' and 'Homog. Support in SGSN' checks. If both are 'yes', it results in 'SUPPORTED' and an 'Idle' state. If 'Homog. Support in MME' is 'no', it checks 'Homog. Non-support in MME'. If 'yes', it goes to connector 'A'; if 'no', it goes to connector 'B'. If 'Homog. Support in SGSN' is 'no', it checks 'Homog. Non-support in SGSN'. If 'yes', it proceeds to 'Query supported in SGSN'. If 'no', it proceeds to another 'Query supported in SGSN' node. Both 'Query supported in SGSN' nodes lead to a 'Query supported in MME' check. If 'yes', it leads to 'Query SGSN', then 'Query MME', then 'Wait for SGSN and MME', then 'Responses from SGSN and MME', then 'Most recent result', and finally 'Idle'. If 'no', it leads to 'Query SGSN', then 'Wait for SGSN support', which then branches into 'Support from SGSN' (leading to 'SUPPORTED' and 'Idle'), 'Other response' (leading to 'UNKNOWN' and 'Idle'), or 'Empty response' (leading to 'NOT SUPPORTED' and 'Idle').
+
+```
+graph TD; both((both)) --> HSM{Homog. Support in MME}; HSM -- yes --> HS{Homog. Support in SGSN}; HSM -- no --> HNM{Homog. Non-support in MME}; HS -- yes --> SUPPORTED[SUPPORTED]; HS -- no --> HNS{Homog. Non-support in SGSN}; HNM -- yes --> A((A)); HNM -- no --> B((B)); SUPPORTED --> Idle1([Idle]); HNS -- yes --> QS1{Query supported in SGSN}; HNS -- no --> QS2{Query supported in SGSN}; QS1 -- yes --> QM1{Query supported in MME}; QS1 -- no --> QM2{Query supported in MME}; QS2 -- yes --> QM2; QS2 -- no --> QS3{Query supported in SGSN}; QM1 -- yes --> QS4[Query SGSN]; QM1 -- no --> QM2; QS4 --> QM3[Query MME]; QM3 --> WSM[Wait for SGSN and MME]; WSM --> RSM[Responses from SGSN and MME]; RSM --> MRJ[Most recent result]; MRJ --> Idle2([Idle]); QM2 -- yes --> QS5[Query SGSN]; QM2 -- no --> QM3; QS5 --> WSS[Wait for SGSN support]; WSS --> SS[Support from SGSN]; WSS --> OR[Other response]; WSS --> ER[Empty response]; SS --> SUPPORTED2[SUPPORTED]; SUPPORTED2 --> Idle3([Idle]); OR --> UNKNOWN1[UNKNOWN]; UNKNOWN1 --> Idle3; ER --> NOTS[NOT SUPPORTED]; NOTS --> Idle3;
+```
+
+Flowchart for Homogeneous Support in MME and SGSN
+
+
+
+![Flowchart for Homogeneous Non-Support in SGSN handling. It starts at point A, checks for homogeneous non-support in SGSN. If yes, it's NOT SUPPORTED and Idle. If no, it checks for homogeneous support in SGSN. If yes, it checks if supported in SGSN and then MME. If no to either, it's UNKNOWN and Idle. If yes to both, it queries SGSN and MME, waits for responses, takes the most recent result, and becomes Idle. If no to homogeneous support in SGSN, it checks if supported in SGSN. If yes, it checks MME. If no to MME, it queries SGSN, waits for non-support response, and becomes NOT SUPPORTED and Idle. If no to SGSN support, it queries SGSN, waits for non-support response, and becomes UNKNOWN and Idle.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg)
+
+```
+graph TD; A((A)) --> HNS{Homog. Non-Support in SGSN}; HNS -- yes --> NS[NOT SUPPORTED]; NS --> Idle1([Idle]); HNS -- no --> HS{Homog. support in SGSN}; HS -- yes --> QS1{Query supported in SGSN}; HS -- no --> QS2{Query supported in SGSN}; QS1 -- yes --> QM{Query supported in MME}; QS1 -- no --> UNKNOWN1[UNKNOWN]; QM -- yes --> QuerySGSN1[Query SGSN]; QM -- no --> UNKNOWN1; QuerySGSN1 --> QueryMME[Query MME]; QueryMME --> WaitSM([Wait for SGSN and MME]); WaitSM --> Res[Responses from SGSN and MME]; Res --> MostRecent[Most recent result]; MostRecent --> Idle2([Idle]); QS2 -- yes --> QM2{Query supported in MME}; QS2 -- no --> QuerySGSN2[Query SGSN]; QM2 -- yes --> QuerySGSN2; QM2 -- no --> WaitNS([Wait for SGSN non-support]); QuerySGSN2 --> WaitNS; WaitNS --> NSR[Non-Support from SGSN]; WaitNS --> ER[Empty response]; WaitNS --> OR[Other response]; NSR --> NS2[NOT SUPPORTED]; OR --> UNKNOWN2[UNKNOWN]; NS2 --> Idle3([Idle]); UNKNOWN2 --> Idle3;
+```
+
+Flowchart for Homogeneous Non-Support in SGSN handling. It starts at point A, checks for homogeneous non-support in SGSN. If yes, it's NOT SUPPORTED and Idle. If no, it checks for homogeneous support in SGSN. If yes, it checks if supported in SGSN and then MME. If no to either, it's UNKNOWN and Idle. If yes to both, it queries SGSN and MME, waits for responses, takes the most recent result, and becomes Idle. If no to homogeneous support in SGSN, it checks if supported in SGSN. If yes, it checks MME. If no to MME, it queries SGSN, waits for non-support response, and becomes NOT SUPPORTED and Idle. If no to SGSN support, it queries SGSN, waits for non-support response, and becomes UNKNOWN and Idle.
+
+![Flowchart for B (Service Request handling)](e2c120be98ede6deb60dd341f5a9803b_img.jpg)
+
+```
+graph TD; B((B)) --> Q1{Query supported in MME}; Q1 -- yes --> Q2{Query supported in SGSN}; Q1 -- no --> UNKNOWN1[UNKNOWN]; UNKNOWN1 --> Idle1([Idle]); Q2 -- yes --> QuerySGSN[Query SGSN]; Q2 -- no --> HomogSupport{Homog. Support in SGSN}; QuerySGSN --> QueryMME1[Query MME]; QueryMME1 --> WaitSGSNMME([Wait for SGSN and MME]); WaitSGSNMME --> Responses[Responses from SGSN and MME]; Responses --> MostRecent[Most recent result]; MostRecent --> Idle2([Idle]); HomogSupport -- yes --> QueryMME2[Query MME]; HomogSupport -- no --> HomogNonSupport{Homog. Non-Support in SGSN}; QueryMME2 --> WaitMME[([Wait For MME support])]; WaitMME --> SupportFromMME[Support From MME]; WaitMME --> EmptyResponse1[Empty response]; WaitMME --> OtherResponse1[Other response]; SupportFromMME --> SUPPORTED[SUPPORTED]; SUPPORTED --> Idle3([Idle]); EmptyResponse1 --> NOT_SUPPORTED1[NOT SUPPORTED]; NOT_SUPPORTED1 --> UNKNOWN2[UNKNOWN]; OtherResponse1 --> UNKNOWN3[UNKNOWN]; HomogNonSupport -- yes --> QueryMME3[Query MME]; HomogNonSupport -- no --> UNKNOWN4[UNKNOWN]; UNKNOWN4 --> Idle4([Idle]); QueryMME3 --> WaitMMENonSupport[([Wait For MME non support])]; WaitMMENonSupport --> NonSupportFromMME[Non-Support From MME]; WaitMMENonSupport --> EmptyResponse2[Empty response]; WaitMMENonSupport --> OtherResponse2[Other response]; NonSupportFromMME --> NOT_SUPPORTED2[NOT SUPPORTED]; NOT_SUPPORTED2 --> Idle5([Idle]); EmptyResponse2 --> UNKNOWN5[UNKNOWN]; OtherResponse2 --> UNKNOWN6[UNKNOWN];
+```
+
+The flowchart illustrates the logic for handling a service request, starting from point 'B'. It first checks if the service is supported in the MME. If 'yes', it proceeds to check if it's supported in the SGSN. If 'yes' there, it queries the SGSN, then the MME, waits for responses, and uses the most recent result to determine if the service is supported, leading to an 'Idle' state. If 'no' at the SGSN check, it evaluates 'Homog. Support in SGSN'. If 'yes', it queries the MME, waits for support, and based on the response (Support, Empty, or Other), determines if the service is SUPPORTED, NOT SUPPORTED, or UNKNOWN, leading to an 'Idle' state or UNKNOWN. If 'no' at 'Homog. Support in SGSN', it evaluates 'Homog. Non-Support in SGSN'. If 'yes', it queries the MME, waits for non-support, and based on the response (Non-Support, Empty, or Other), determines if the service is NOT SUPPORTED, UNKNOWN, or UNKNOWN, leading to an 'Idle' state or UNKNOWN. If 'no' at 'Homog. Non-Support in SGSN', it leads to UNKNOWN and then Idle. If 'no' at the initial MME check, it leads to UNKNOWN and then Idle.
+
+Flowchart for B (Service Request handling)
+
+![Flowchart of T-ADS request handling in the HSS. The process starts at connector 'C', proceeds to a decision 'Homog. Support/ Non-support in combined node'. If 'no', it goes to 'Query supported in combined node'. If 'yes', it goes to 'Response to AS'. From 'Query supported in combined node', if 'no', it goes to 'UNKNOWN'. If 'yes', it goes to 'Query combined node', then 'Wait for combined node', then 'Response from combined node'. Both 'UNKNOWN' and 'Response from combined node' lead to 'Response to AS', which finally leads to 'Idle'.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg)
+
+```
+graph TD; C((C)) --> D{Homog. Support/ Non-support in combined node}; D -- no --> E{Query supported in combined node}; D -- yes --> F[/Response to AS/]; E -- no --> G[/UNKNOWN/]; E -- yes --> H[Query combined node]; H --> I([Wait for combined node]); I --> J[/Response from combined node/]; G --> F; J --> F; F --> K([Idle]);
+```
+
+Flowchart of T-ADS request handling in the HSS. The process starts at connector 'C', proceeds to a decision 'Homog. Support/ Non-support in combined node'. If 'no', it goes to 'Query supported in combined node'. If 'yes', it goes to 'Response to AS'. From 'Query supported in combined node', if 'no', it goes to 'UNKNOWN'. If 'yes', it goes to 'Query combined node', then 'Wait for combined node', then 'Response from combined node'. Both 'UNKNOWN' and 'Response from combined node' lead to 'Response to AS', which finally leads to 'Idle'.
+
+When receiving a T-ADS request from an Application Server, the HSS checks whether serving nodes (i.e. SGSN and/or MME) are registered (i.e. GPRS services and/or EPS services are actually subscribed, serving node addresses are stored and not marked as purged).
+
+If neither MME nor SGSN is registered, a response indicating that IMS voice over PS sessions is not supported is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+If both MME and SGSN are registered but the registered SGSN is a Gn/Gp-SGSN, the HSS treats the MME as not registered in the following T-ADS request handling.
+
+Otherwise,
+
+if in the previous ULR(s) the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was received from all the registered serving nodes with the same value (either with SUPPORTED or NOT\_SUPPORTED), a response
+
+with the received value is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+if in previous ULRs the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was received from all the registered serving nodes but with different values, the HSS continues processing as follows:
+
+if MME or SGSN (or both) did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+otherwise the HSS retrieves T-ADS Data from MME and from SGSN. After retrieval, the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported.
+
+if in the previous ULR(s) the AVP Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions was not received from at least one of the registered serving nodes, the HSS continues processing as follows:
+
+if at least one of the registered serving nodes that did not send an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+otherwise the HSS retrieves T-ADS Data from all the registered serving nodes that did not send an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR. When all responses are received the HSS continues processing as follows:
+
+if two T-ADS Data responses were received (one from MME and one from SGSN), the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported.
+
+if one T-ADS Data response was received (from MME or SGSN) and the other serving node (SGSN or MME) was not registered, the HSS returns a response to the Application Server indicating the response from responding serving node. UE Activity Time and the Last RAT Type are also reported.
+
+if one T-ADS Data response was received (from MME or SGSN) and the other serving node (SGSN or MME) has sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR, the HSS continues processing as follows:
+
+if information about support / non-support of IMS voice over PS sessions from both serving nodes are identical, the HSS returns this information to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+if information about support / non-support of IMS voice over PS sessions from both serving nodes are not identical, the HSS continues processing as follows:
+
+if the serving node that sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR did not indicate support of T-ADS Data Retrieval within the previous ULR, a response indicating IMS-VOICE-OVER-PS-SUPPORT-UNKNOWN is returned to the Application Server. UE Activity Time and the Last RAT Type are not reported.
+
+otherwise the HSS retrieves T-ADS Data from the serving node that sent an Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP within the previous ULR. When the response is received, the HSS returns a response to the Application Server indicating the response from MME or SGSN whichever reported the most recent UE Activity Time. UE Activity Time and the Last RAT Type are also reported.
+
+# --- Annex F (normative): Diameter overload control mechanism
+
+## F.1 General
+
+Diameter overload control mechanism is an optional feature.
+
+IETF RFC 7683 [36] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 7683 [36] on the Sh interface where, when applied, the AS shall behave as a reacting node and the HSS as a reporting node.
+
+Depending on regional/national requirements and network operator policy, priority traffic (e.g. MPS as described in 3GPP TS 22.153 [38]) shall be exempted from throttling due to Diameter overload control up to the point where requested traffic reduction cannot be achieved without throttling the priority traffic.
+
+## F.2 HSS behaviour
+
+The HSS requests traffic reduction from the AS when the HSS is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [36].
+
+The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the Sh interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc.
+
+The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means.
+
+## F.3 AS behaviour
+
+The AS applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [36].
+
+The AS achieves requested traffic reduction by implementation specific means. For example, the AS may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed.
+
+Diameter requests related to priority traffic (e.g. MPS) and emergency, detected via the presence of priority information (e.g., Resource-Priority header field for MPS) in SIP messages as described in 3GPP TS 24.229 [39], have the highest priority. Depending on regional/national regulatory and operator policies, these Diameter requests shall be the last to be throttled, when the AS has to apply traffic reduction. Relative priority amongst various priority traffic (e.g. MPS) and emergency traffic is subject to regional/national regulatory and operator policies.
+
+# --- Annex G (Informative): Diameter overload node behaviour
+
+## G.1 Message prioritization
+
+This clause describes possible behaviours of the AS regarding message prioritization in an informative purpose.
+
+The AS may take the following into account when making throttling decisions:
+
+- Identification of the procedures that can be deferred (e.g. Subscription to notification of Data Update), so to avoid to drop non deferrable procedures;
+- Prioritization of certain types of request (e.g. between PUR and SNR) according to the context of their use, in particular:
+  - Higher prioritization of commands for AS that are related to a registered user for a service, so to avoid the interruption of the registered service for the user.
+  - Lower prioritization of commands for AS that are related to massive subscription data update due to provisioning.
+  - Priority level of a priority user (e.g., MPS user).
+
+# --- Annex H (Informative): Data shared among multiple subscribers
+
+## H.1 General
+
+This clause applies only to Repository Data.
+
+As defined by this specification, Repository Data is updated using a Sh-Update procedure per subscriber and Service Indication. This means that when Repository Data needs to be modified, it requires an update operation per subscriber, even if the same Repository Data is also part of other subscribers' data set.
+
+If Repository Data for a specific Service Indication is shared by a large amount of subscribers, it implies a large amount of update operations, which may trigger a large amount of notifications if any AS subscribed to changes for these corresponding subscribers.
+
+See 3GPP TS 29.364 [40] for a description of a solution to avoid this massive amount of update operations. However, it is important to remark that there may be other implementation specific solutions that handle data sharing among multiple individual subscribers.
+
+# --- Annex I (normative): Diameter message priority mechanism
+
+## I.1 General
+
+IETF draft-ietf-drmp-02 [42] specifies a Diameter message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied.
+
+## I.2 Sh/Dh interface
+
+### I.2.1 General
+
+The Diameter message priority mechanism is an optional feature.
+
+It is recommended to make use of IETF draft-ietf-drmp-02 [42] over the Sh/Dh interface of an operator network when the overload control defined in Annex F is applied on this Sh/Dh interface.
+
+### I.2.2 AS/OSA SCS behaviour
+
+When the AS/OSA SCS supports the Diameter message priority mechanism, the AS/OSA SCS shall comply with IETF RFC 7944 [42].
+
+The AS/OSA SCS sending a request shall determine the required priority according to its policies. When priority is required, the AS/OSA SCS shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to priority level received.
+
+When the AS/OSA SCS receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request.
+
+When the AS/OSA SCS receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response.
+
+If:
+
+- the AS/OSA SCS supports using the Diameter message priority mechanism for DSCP marking purposes,
+- the transport network utilizes DSCP marking, and
+- message-dependant DSCP marking is possible for the protocol stack transporting Diameter,
+
+then the AS/OSA SCS shall set the DSCP marking for transport of the request or response according to the required priority level.
+
+Diameter requests related to priority traffic (e.g. MPS as identified by the AS through SIP procedures, emergency) shall contain a DRMP AVP with a high priority of which the level value is operator dependent.
+
+When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific.
+
+### I.2.3 HSS/SLF behaviour
+
+When the HSS/SLF supports the Diameter message priority mechanism, the HSS/SLF shall comply with IETF RFC 7944 [42].
+
+The HSS/SLF sending a request shall determine the required priority according to its policies. When priority is required, the HSS/SLF shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level.
+
+When the HSS/SLF receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request.
+
+When the HSS/SLF receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response.
+
+If:
+
+- the HSS/SLF supports using the Diameter message priority mechanism for DSCP marking purposes,
+- the transport network utilizes DSCP marking, and
+- message-dependant DSCP marking is possible for the protocol stack transporting Diameter,
+
+then the HSS/SLF shall set the DSCP marking for transport of the request or response according to the required priority level.
+
+When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific.
+
+### I.2.4 Interactions
+
+If the HSS/SLF supporting the Diameter message priority mechanism receives the request message containing both the Session-Priority AVP and DRMP AVP, the HSS/SLF shall prioritize the request according to priority level received within the DRMP AVP.
+
+# --- Annex J (normative): Diameter load control mechanism
+
+## J.1 General
+
+Diameter load control mechanism is an optional feature.
+
+It is recommended to make use of IETF RFC 8583 [43] on the Sh interface where, when applied, the AS shall behave as reacting nodes and the HSS as a reporting node.
+
+## J.2 HSS behaviour
+
+The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [43].
+
+The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the Sh interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc.
+
+The HSS determines when to send Load AVPs of type HOST by implementation specific means.
+
+## J.3 AS behaviour
+
+When performing next hop Diameter Agent selection for requests that are routed based on realm, the AS may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [43].
+
+# Annex K (informative): Change history
+
+| Date      | TSG # | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                      | New   |
+|-----------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------------|-------|
+| Jun 2002  | CN#16 | NP-020277 |      |     | Version 2.0.0 approved at CN#16                                                                      | 5.0.0 |
+| Sep 2002  | CN#17 | NP-020450 | 1    | 1   | The Correction of Clause 7 Numbering and internal referencing                                        | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 2    | 1   | Correction of handling of subscriptions to notifications                                             | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 3    | 1   | Definition of User Location for Sh interface                                                         | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 4    | 1   | Definition of User State for Sh interface                                                            | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 5    | -   | Missing references to XML schema for Sh interface                                                    | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 6    | -   | Extensibility of XML schema for Sh interface                                                         | 5.1.0 |
+| Dec 2002  | CN#18 | NP-020592 | 007  | -   | Removal of upper bounds in Sh i/f user profile and correction of mistake in XML schema documentation | 5.2.0 |
+| Dec 2002  | CN#18 | NP-020593 | 008  | 1   | Clarification on update of repository data                                                           | 5.2.0 |
+| Dec 2002  | CN#18 | NP-020593 | 009  | 1   | Removing the DDF dependencies from Sh interface                                                      | 5.2.0 |
+| Dec 2002  | CN#18 | NP-020592 | 013  | 2   | Error handling in HSS when being updated with too much data                                          | 5.2.0 |
+| Dec 2002  | CN#18 | NP-020591 | 014  | -   | Correction of the SPI                                                                                | 5.2.0 |
+| Jan 2003  |       |           |      |     | Restoration of Annex E                                                                               | 5.2.1 |
+| Mar 2003  | CN#19 | NP-030102 | 012  | 3   | Initial Filter Criteria                                                                              | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 015  | -   | Deletion of Annex E                                                                                  | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 016  | 2   | Update after Diameter has become RFC                                                                 | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 017  | 1   | Correction to application server identity                                                            | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 018  | 2   | Clarification on Sh interface for charging purposes                                                  | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030101 | 019  | 2   | Change of SPI to SPT                                                                                 | 5.3.0 |
+| Apr 2003  |       |           |      |     | ShDataType.xsd - file attached                                                                       | 5.3.1 |
+| Apr 2003  |       |           |      |     | Updated ShDataType.xsd - file attached                                                               | 5.3.2 |
+| Jun 2003  | CN#20 | NP-030216 | 022  | 1   | Co-ordination of Update of Repository Data                                                           | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 023  | 1   | Enhanced description of Sh-Pull Request and Response                                                 | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 024  | 2   | Enhanced description of Sh-Notif and Sh-Notif-Subs Request and Response                              | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 025  | 2   | A range of editorial changes and corrections and additions of references                             | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 027  | -   | Discrepancy between XML schema of Cx and Sh interface                                                | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 029  | -   | Correction to the use of User-Identity                                                               | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 030  | -   | Clarification on the handling of the "Charging Information" via the Sh interface                     | 5.4.0 |
+| Sep 2003  | CN#21 | NP-030384 | 032  | 2   | Correction of message flow                                                                           | 5.5.0 |
+| Sep 2003  | CN#21 | NP-030384 | 033  | 2   | Correction of Sh data definition in Annex C and D                                                    | 5.5.0 |
+| Sep 2003  | CN#21 | NP-030384 | 035  | 2   | Mistakes in the XML schema                                                                           | 5.5.0 |
+| Dec 2003  | CN#22 | NP-030501 | 038  | -   | XML Schema Correction                                                                                | 5.6.0 |
+| Dec 2003  | CN#22 | NP-030501 | 041  | -   | The extensibility of the XML schema                                                                  | 5.6.0 |
+| Dec 2003  | CN#22 | NP-030518 | 042  | -   | Clarification of inclusion of elements in Charging Information                                       | 5.6.0 |
+| Dec 2003  | CN#22 |           |      |     | Reference [8] updated                                                                                | 5.6.0 |
+| Dec 2003  | CN#22 | NP-030510 | 026  | 3   | Introduction of Presence Stage 3 (Ph) to the Sh interface                                            | 6.0.0 |
+| Mar 2004  | CN#23 | NP-040055 | 036  | 2   | Dh interface                                                                                         | 6.1.0 |
+| Mar 2004  | CN#23 | NP-040055 | 043  | 2   | Clarification of the AS Permissions List and its relevance to table 7.6.1                            | 6.1.0 |
+| Mar 2004  | CN#23 | NP-040135 | 045  | 3   | Clarification of which Public Identities are downloaded                                              | 6.1.0 |
+| June 2004 | CN#24 | NP-040220 | 0085 | 2   | Mapping to Diameter AVP for Requested Identity Set                                                   | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040401 | 094  | 1   | Triggering initial REGISTER messages                                                                 | 6.3.0 |
+| Sep 2004  | CN#25 | NP-040401 | 088  | 1   | XML versioning                                                                                       | 6.3.0 |
+| Dec 2004  | CN#26 | NP-040531 | 097  | 2   | Removal of Notification of the Authentication Pending State upon Registration                        | 6.4.0 |
+| Dec 2004  | CN#26 | NP-040531 | 102  | 2   | Only One Error Required for the AS Permissions Table Checking Procedure                              | 6.4.0 |
+| Dec 2004  | CN#26 | NP-040531 | 103  | -   | Default Handling of Error Cases                                                                      | 6.4.0 |
+| Dec 2004  | CN#26 | NP-040578 | 104  | -   | Access Key for Charging Information                                                                  | 6.4.0 |
+| Dec 2004  | CN#26 | NP-040578 | 108  | 2   | Handling of Information Element marked as (M), (C) or (O)                                            | 6.4.0 |
+| Dec 2004  | CN#26 | NP-040531 | 101  | 1   | Sh-Pull Data Download                                                                                | 6.4.0 |
+| Mar 2005  | CN#27 | NP-050031 | 099  | 5   | Sh-Update needs to include Data-Reference to be future proof                                         | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050038 | 111  | 1   | Clarification on requested identity set                                                              | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050031 | 113  | -   | Align UML Model and the XML schema for Public Identity                                               | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050031 | 116  | 1   | Conditional Service indication in Sh-Subs-Notif                                                      | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050031 | 118  | -   | Sh Diameter AVP Mapping Correction                                                                   | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050031 | 121  | 2   | Clarification of Sh Access Keys                                                                      | 6.5.0 |
+| Mar 2005  | CN#27 | NP-050038 | 122  | 2   | Multiple Terminals in Sh                                                                             | 6.5.0 |
+| Jun 2005  | CT#28 | CP-050082 | 127  | -   | Sh user-data correction                                                                              | 6.6.0 |
+| Jun 2005  | CT#28 | CP-050087 | 130  | 1   | Sh procedures applicable to Public Service Identity                                                  | 6.6.0 |
+
+|          |       |           |      |   |                                                                                   |       |
+|----------|-------|-----------|------|---|-----------------------------------------------------------------------------------|-------|
+| Jun 2005 | CT#28 | CP-050082 | 134  | 1 | Behavior of HSS when it accepts Sh-Subs-Notif message                             | 6.6.0 |
+| Jun 2005 | CT#28 | CP-050087 | 137  | 1 | Editorial corrections                                                             | 6.6.0 |
+| Jun 2005 | CT#28 | CP-050082 | 139  | - | XML correction for iFC                                                            | 6.6.0 |
+| Sep 2005 | CT#29 | CP-050283 | 146  | - | Correction to Sh-IMS-Data for Initial Filter Criteria                             | 6.7.0 |
+| Sep 2005 | CT#29 | CP-050283 | 152  | 1 | ISDN-address correction                                                           | 6.7.0 |
+| Sep 2005 | CT#29 | CP-050424 | 154  | - | Update of the IETF RFC for tel URI                                                | 6.7.0 |
+| Sep 2005 | CT#29 | CP-050294 | 155  | 2 | PSI Activation                                                                    | 6.7.0 |
+| Sep 2005 | CT#29 | CP-050282 | 160  | - | Charging-Information correction                                                   | 6.7.0 |
+| Dec 2005 | CT#30 | CP-050604 | 144  | 5 | XML syntax correction                                                             | 6.8.0 |
+| Dec 2005 | CT#30 | CP-050611 | 161  | 2 | Correction of the use of Data Reference 10 for Public Service Identities          | 6.8.0 |
+| Dec 2005 | CT#30 | CP-050605 | 167  | - | PSUserState correction                                                            | 6.8.0 |
+| Dec 2005 | CT#30 | CP-050625 | 162  | 3 | Notification Efficiency                                                           | 7.0.0 |
+| Dec 2005 | CT#30 | CP-050625 | 163  | 3 | Management of Sh subscriptions                                                    | 7.0.0 |
+| Mar 2006 | CT#31 | CP-060084 | 0168 | 2 | User-Data in the response to Sh-Subs-Notif                                        | 7.1.0 |
+| Mar 2006 | CT#31 | CP-060084 | 0169 | 1 | New error indications for the Sh-Subs-Notif procedure                             | 7.1.0 |
+| Mar 2006 | CT#31 | CP-060065 | 0172 | 2 | Handling of unknown errors                                                        | 7.1.0 |
+| Mar 2006 | CT#31 | CP-060154 | 0176 | 2 | PSI Activation                                                                    | 7.1.0 |
+| Jun 2006 | CT#32 | CP-060319 | 0178 | 2 | Returning Null Data                                                               | 7.2.0 |
+| Jun 2006 | CT#32 | CP-060319 | 0181 | 2 | Modify description of clause 6.1.3 Subscription to notifications                  | 7.2.0 |
+| Jun 2006 | CT#32 | CP-060319 | 0182 | 2 | Sh interface efficiency improvement                                               | 7.2.0 |
+| Jun 2006 | CT#32 | CP-060319 | 0183 | 2 | Sh result-code correction                                                         | 7.2.0 |
+| Jun 2006 | CT#32 | CP-060308 | 0186 | 1 | PSI Activation schema correction                                                  | 7.2.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0188 | 3 | Definition of Activation State Information for IMS (DSAI)                         | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0190 | - | Applying ORIGINATING_UNREGISTERED state to Sh                                     | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0191 | 2 | Sh-Subs-Notif without Expiry Time                                                 | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0195 | 4 | S-CSCF name in Sh                                                                 | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0196 | 1 | Public User Identity Grouping Information                                         | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060399 | 0198 | 2 | Correction of the relationship between Repository Data and Public Identities      | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0199 | - | Error to be sent if the identity can not be used for data reference               | 7.3.0 |
+| Sep 2006 | CT#33 | CP-060417 | 0200 | 1 | Errors to be sent in response to Sh-Notif                                         | 7.3.0 |
+| Dec 2006 | CT#34 | CP-060555 | 0204 | 1 | Activation Status of a PSI                                                        | 7.4.0 |
+| Dec 2006 | CT#34 | CP-060566 | 0207 | 1 | UDA correction for the case that data does not exist in the HSS                   | 7.4.0 |
+| Dec 2006 | CT#34 | CP-060566 | 0208 | - | Grouping identities update                                                        | 7.4.0 |
+| Dec 2006 | CT#34 | CP-060735 | 0209 | 3 | Clarification regarding URI canonicalization – 29.328                             | 7.4.0 |
+| Mar 2007 | CT#35 | CP-070020 | 0211 | - | CurrentLocation is a required Access Key for LocationInformation DataRef          | 7.5.0 |
+| Mar 2007 | CT#35 | CP-070020 | 0212 | - | Clarification on interaction between DSAI and wildcarded PSI                      | 7.5.0 |
+| Mar 2007 | CT#35 | CP-070020 | 0215 | - | Presence of Information Elements in Sh-Subs-Notif                                 | 7.5.0 |
+| Mar 2007 | CT#35 | CP-070020 | 0219 | 1 | Restriction in the instances of repository data                                   | 7.5.0 |
+| Jun 2007 | CT#36 | CP-070309 | 0221 | - | Correction of XML schema                                                          | 7.6.0 |
+| Jun 2007 | CT#36 | CP-070318 | 0224 | - | Adding the Ability to Notify an AS with Charging Information                      | 7.6.0 |
+| Jun 2007 | CT#36 | CP-070318 | 0227 | 1 | Application Server subscription for Implicit Identities                           | 7.6.0 |
+| Sep 2007 | CT#37 | CP-070527 | 0231 | 1 | Handling of Empty Repository Data                                                 | 7.7.0 |
+| Sep 2007 | CT#37 | CP-070527 | 0234 | - | Handling of Charging Data by the HSS                                              | 7.7.0 |
+| Sep 2007 | CT#37 | CP-070527 | 0235 | 1 | Wildcarded PSI as key in the Sh Interface                                         | 7.7.0 |
+| Sep 2007 | CT#37 | CP-070522 | 0238 | 1 | Repository Data and Subscriptions for Wildcarded PSIs                             | 7.7.0 |
+| Sep 2007 | CT#37 | CP-070527 | 0239 | 1 | Aliases definition alignment with 23.228                                          | 7.7.0 |
+| Nov 2007 | CT#38 | CP-070743 | 0241 | - | PNR for Subscriptions to Notifications for all Identity Sets                      | 7.8.0 |
+| Mar 2008 | CT#39 | CP-080019 | 0243 | - | Wildcarded Public User Identities                                                 | 8.0.0 |
+| Jun 2008 | CT#40 | CP-080267 | 0246 | - | DSAI Corrections                                                                  | 8.1.0 |
+| Jun 2008 | CT#40 | CP-080261 | 0249 | 1 | Realm and Host to be used for Charging                                            | 8.1.0 |
+| Sep 2008 | CT#41 | CP-080460 | 0247 | 4 | Adding the Deletion Notification of a Public Identity to the AS                   | 8.2.0 |
+| Sep 2008 | CT#41 | CP-080460 | 0257 | 1 | Removal of subscription data related to AS permission which has been prohibited   | 8.2.0 |
+| Dec 2008 | CT#42 | CP-080708 | 0258 | 2 | Usage of Public Identity Deleted Notification                                     | 8.3.0 |
+|          |       | CP-080707 | 0260 | - | Support for IMS Service Level Trace                                               | 8.3.0 |
+|          |       | CP-080696 | 0261 | 3 | Diameter Proxy Agent - an alternative User Identity to HSS resolution mechanism   | 8.3.0 |
+| Mar 2009 | CT#43 | CP-090036 | 0266 | 3 | HSS Addresses                                                                     | 8.4.0 |
+|          |       | CP-090028 | 0267 | 4 | Support for GPRS IMS Bundled Authentication (GIBA) in Sh                          | 8.4.0 |
+|          |       | CP-090042 | 0268 | 3 | Alias grouping handling                                                           | 8.4.0 |
+| Jun 2009 | CT#44 | CP-090305 | 0271 | 1 | IP address secure binding information shall not be allowed for shared IMPUs       | 8.5.0 |
+|          |       | CP-090302 | 0272 | 1 | Correction for choice of CGI, SAI or LAI                                          | 8.5.0 |
+| Sep 2009 | CT#44 | CP-090525 | 0280 | 1 | Correction of the XML schema                                                      | 8.6.0 |
+|          |       | CP-090546 | 0277 | 1 | CR implementation correction                                                      | 8.6.0 |
+|          |       | CP-090553 | 0274 | - | Indication that GIBA information is not available in Sh-Pull when using Notif-Eff | 8.6.0 |
+| Dec 2009 | CT#46 | CP-090778 | 0285 | 2 | Session-Priority AVP                                                              | 8.7.0 |
+| Dec 2009 | CT#46 | CP-090790 | 0288 | - | Correction on Identity Set for PSI                                                | 9.0.0 |
+
+|          |       |           |      |   |                                                                                    |        |
+|----------|-------|-----------|------|---|------------------------------------------------------------------------------------|--------|
+| Mar 2010 | CT#47 | CP-100033 | 0293 | 1 | Priority service attribute in Sh                                                   | 9.1.0  |
+|          |       | CP-100033 | 0295 | 1 | IP-SM-GW UE reachability handling over Sh.                                         |        |
+|          |       |           | 0300 | 1 | SMS Registration Information                                                       |        |
+|          |       | CP-100048 | 0286 | 1 | Sh handling of T-ADS                                                               |        |
+|          |       | CP-100017 | 0303 | 1 | Correction of MSISDN as Access Key via Sh Interface                                |        |
+|          |       | CP-100029 | 0310 | 1 | User CSG Information                                                               |        |
+|          |       | CP-100217 | 0311 | 5 | EPS Subscriber State and Location Information Request                              |        |
+| May 2010 |       |           |      |   | Xml-file corrected                                                                 | 9.1.1  |
+| Jun 2010 | CT#48 | CP-100412 | 0317 | 1 | Update of IETF Reference                                                           | 9.2.0  |
+|          |       | CP-100275 | 0314 |   | EPS state and location retrieval                                                   |        |
+|          |       | CP-100279 | 0322 | 1 | URRP for SGSN                                                                      |        |
+| Sep 2010 | CT#49 | CP-100447 | 0331 |   | Correction to the Values of Data-Reference AVP                                     | 9.3.0  |
+|          |       | CP-100454 | 0333 |   | Sh-Subs-Notif procedure clarification                                              |        |
+|          |       | CP-100442 | 0336 | 1 | Correction to Access IMSPublicIdentity Data using MSISDN via Sh Interface          |        |
+| Sep 2010 | CT#49 | CP-100522 | 0327 | 3 | Usage of IMSI and IMPI for user identification over Sh                             | 10.0.0 |
+|          |       | CP-100466 | 0332 | 3 | Sh-Update with multiple Repository Data                                            |        |
+|          |       | CP-100466 | 0337 | 1 | Location data including only serving node address                                  |        |
+| Dec 2010 | CT#50 | CP-100699 | 0340 | 4 | SRVCC Enhancements                                                                 | 10.1.0 |
+|          |       | CP-100697 | 0342 | 1 | Update the Reference of Alias                                                      |        |
+|          |       | CP-100671 | 0345 | 1 | C-MSISDN over Sh                                                                   |        |
+|          |       | CP-100671 | 0359 |   | SMS Registration with MSISDN                                                       |        |
+|          |       | CP-100677 | 0351 | 1 | IE Requested Nodes is optional for backward compatibility reasons                  |        |
+| Jan 2011 |       |           |      |   | Attached xml-file "tShIMSDataExtension4" part corrected.                           | 10.1.1 |
+| Mar 2011 | CT#51 | CP-110044 | 0366 |   | Originating CDIV included as new Session Case                                      | 10.2.0 |
+|          |       | CP-110044 | 0374 |   | Cardinality and extensions corrections in XML schema                               |        |
+|          |       | CP-110060 | 0349 | 3 | MPS over Sh                                                                        |        |
+|          |       | CP-110075 | 0360 | 3 | Retrieval of CSRN from HSS                                                         |        |
+|          |       | CP-110075 | 0363 | 4 | Correction on Access Keys for data accessible via Sh and table format improvements |        |
+|          |       | CP-110082 | 0371 |   | SRVCC Subscription and STN-SR                                                      |        |
+|          |       | CP-110066 | 0375 | 1 | Enhancements of T-ADS data retrieval via Sh                                        |        |
+|          |       | CP-110075 | 0376 | 1 | Requested Identity Set updated                                                     |        |
+|          |       | CP-110075 | 0378 | 1 | Fix backwards incompatible change for Serving Node Indication                      |        |
+|          |       | CP-110356 | 0384 | 1 | Sh-Update with MSISDN                                                              |        |
+| Jun 2011 | CT#52 | CP-110370 | 0380 | 3 | SC Address in IP-SM-GW Register Response                                           | 10.3.0 |
+|          |       | CP-110370 | 0381 | 2 | Pre-paging Support Indicator for CSRN                                              |        |
+| Jun 2011 | CT#52 | CP-110383 | 0377 | 4 | Reference Location over Sh interface                                               | 11.0.0 |
+| Sep 2011 | CT#53 | CP-110576 | 0393 | 2 | Clarification on Receiving Sh-Notif Error Response                                 | 11.1.0 |
+| Dec 2011 | CT#54 | CP-110781 | 0397 | 1 | Class ApplicationServerExtension in Sh XML Schema                                  | 11.2.0 |
+|          |       | CP-110781 | 0405 | 1 | Correction on Wildcarded Public Identity                                           |        |
+|          |       | CP-110781 | 0408 | 2 | Service Data with empty content in Sh                                              |        |
+|          |       | CP-110809 | 0406 | 1 | UE Reachability for IP attributes                                                  |        |
+| Mar 2012 | CT#55 | CP-120019 | 0421 |   | MME-Name reference                                                                 | 11.3.0 |
+|          |       | CP-120027 | 0418 |   | Missing tags in MSISDN type description                                            |        |
+|          |       | CP-120027 | 0423 | 1 | CSRN inconsistency between XML and text                                            |        |
+|          |       | CP-120035 | 0415 | 2 | Update of Multiple Data Instances in Sh-Update                                     |        |
+| Jun 2012 | CT#56 | CP-120222 | 0427 |   | CSG-Id length                                                                      | 11.4.0 |
+|          |       | CP-120240 | 0416 | 4 | Local Time for NPLI                                                                |        |
+| Sep 2012 | CT#57 | CP-120446 | 0437 | 2 | T-ADS clarification                                                                | 11.5.0 |
+|          |       | CP-120445 | 0435 |   | RAT-type coding                                                                    |        |
+|          |       | CP-120445 | 0440 |   | Base64 coding                                                                      |        |
+|          |       | CP-120460 | 0441 | 2 | Clarification on T-ADS Information                                                 |        |
+|          |       | CP-120481 | 0442 | 3 | A-MSISDN handling over Sh                                                          |        |
+|          |       | CP-120481 | 0443 | 2 | Local Time Zone                                                                    |        |
+|          |       | CP-120656 | 0444 | 1 | Reference list correction to align with the corrected TS 29.212 title              |        |
+| Dec 2012 | CT#58 | CP-120743 | 0446 | - | Applicability of Send Data Indication                                              | 11.6.0 |
+|          |       | CP-120743 | 0450 | 1 | Unavailable Data Handling                                                          |        |
+|          |       | CP-120743 | 0453 | 2 | PS LocationInformation Support                                                     |        |
+|          |       | CP-120720 | 0449 | 1 | UserCSGInformation in EPS Location Info                                            |        |
+| Feb 2013 |       |           |      |   | The version numbers in a history table corrected                                   | 11.6.1 |
+| Mar 2013 | CT#59 | CP-130018 | 0458 | 1 | Private Identity as additional access key                                          | 11.7.0 |
+|          |       | CP-130020 | 0461 | 3 | PS Location Info request with RAT-type                                             |        |
+| Mar 2013 | CT#59 | CP-130031 | 0459 | 3 | Sh IMSI retrieval                                                                  | 12.0.0 |
+| Jun 2013 | CT#60 | CP-130374 | 0466 | - | IMPU As Access Key for User State and Location Information                         | 12.1.0 |
+|          |       | CP-130374 | 0463 | 2 | MTRR on Sh                                                                         |        |
+|          |       | CP-130380 | 0464 | 1 | Storing Last known Location Information of purged UE in HSS                        |        |
+|          |       | CP-130410 | 0469 | 1 | HSS handling of T-ADS for detached subscriber                                      |        |
+| Sep 2013 | CT#61 | CP-130441 | 0476 | 1 | XML definitions for CS Location Information Extension                              | 12.2.0 |
+|          |       | CP-130448 | 0471 | 1 | Missing tags                                                                       |        |
+|          |       | CP-130461 | 0472 | - | Correction on Wrong Implementation of CR                                           |        |
+
+|          |       |           |      |   |                                                                                 |        |
+|----------|-------|-----------|------|---|---------------------------------------------------------------------------------|--------|
+|          |       | CP-130461 | 0477 | - | tISDNAddress                                                                    |        |
+| Dec 2013 | CT#62 | CP-130614 | 0479 | 3 | T-ADS Information Retrieval for Gn/Gp-SGSN                                      | 12.3.0 |
+|          |       | CP-130627 | 0480 | - | Annex D alignment with .xsd file                                                |        |
+|          |       | CP-140027 | 0483 | - | Notification of UE SRVCC Capability Update                                      |        |
+| Mar 2014 | CT#63 | CP-140027 | 0484 | 1 | Clarification on Current Location Retrieved                                     | 12.4.0 |
+|          |       | CP-140027 | 0485 | 1 | Clarification to Notif-Eff                                                      |        |
+|          |       | CP-140027 | 0486 | 2 | Suppression of Announcement Indication                                          |        |
+|          |       | CP-140238 | 0491 | - | IP-SM-GW address handling clarification                                         |        |
+| Jun 2014 | CT#64 | CP-140238 | 0493 | 1 | Extended priority is missing in UML model                                       | 12.5.0 |
+|          |       | CP-140252 | 0487 | 5 | Retrieval of TWAN-Id over Sh                                                    |        |
+|          |       | CP-140262 | 0489 | 2 | Private User Identity retrieval                                                 |        |
+|          |       | CP-140503 | 0497 | - | Repository data retrieval                                                       |        |
+| Sep 2014 | CT#65 | CP-140515 | 0495 | 1 | Unsuccessful multiple repository data update                                    | 12.6.0 |
+|          |       | CP-140509 | 0498 | 1 | Diameter Overload Control Over Sh                                               |        |
+|          |       | CP-140519 | 0499 | 1 | Add Logical Access ID for Sh                                                    |        |
+|          |       | CP-140755 | 0502 | 2 | Access Key for Service Priority Level                                           |        |
+| Dec 2014 | CT#66 | CP-140766 | 0501 | - | tMSISDN Type                                                                    | 12.7.0 |
+|          |       | CP-140790 | 0503 | 1 | Priority Consideration for Diameter Overload Control                            |        |
+|          |       | CP-140790 | 0509 | - | DOIC reference update                                                           |        |
+|          |       | CP-140773 | 0508 | 1 | T-ADS Clarification                                                             |        |
+|          |       | CP-150023 | 0510 | 1 | HSS access keys for multiple data references                                    |        |
+| Mar 2015 | CT#67 | CP-150040 | 0511 | 2 | IMS service data shared among multiple subscribers                              | 12.8.0 |
+| Mar 2015 | CT#67 | CP-150038 | 0512 | - | T-ADS clarification                                                             | 13.0.0 |
+| Jun 2015 | CT#68 | CP-150243 | 0524 | 1 | iFC XML alignment with Cx                                                       | 13.1.0 |
+|          |       | CP-150246 | 0527 | - | Location info XML Corrections                                                   |        |
+|          |       | CP-150251 | 0514 | - | Sh-Notif when the HSS supports both Update-Eff and Notif-Eff                    |        |
+|          |       | CP-150273 | 0515 | 1 | Only Repository Data can be shared among multiple subscribers                   |        |
+|          |       | CP-150264 | 0518 | - | STN-SR Sh-Update introduction clarification                                     |        |
+|          |       | CP-150264 | 0525 | 1 | IP-SM-GW registration with Diameter                                             |        |
+|          |       | CP-150264 | 0526 | - | Access key for ExtendedPriority                                                 |        |
+| Sep 2015 | CT#69 | CP-150444 | 0529 | - | Update-Eff-Enhance                                                              | 13.2.0 |
+| Dec 2015 | CT#70 | CP-150743 | 0535 | 1 | Correction on the Encoding of IP Addresses                                      | 13.3.0 |
+|          |       | CP-150759 | 0539 | 1 | Update reference to DOIC new IETF RFC                                           |        |
+|          |       | CP-150750 | 0536 | 1 | Only either WPSI or WIMPU present in requests                                   |        |
+|          |       | CP-150750 | 0537 | 1 | DSAI class multiplicity clarification                                           |        |
+|          |       | CP-150848 | 0540 | 4 | DRMP AVP Procedures over Sh/Dh                                                  |        |
+| Mar 2016 | CT#71 | CP-160014 | 0555 | 1 | Encoding of SC Address                                                          | 13.4.0 |
+|          |       | CP-160046 | 0543 | 2 | Data returned in IMSPublicIdentity correction                                   |        |
+|          |       | CP-160013 | 0551 | 1 | Encoding of IP-SM-GW Number                                                     |        |
+|          |       | CP-160046 | 0544 | 2 | Local Time Zone for CS retrieval                                                |        |
+|          |       | CP-160046 | 0556 | 1 | Length correction for tVPLMNID and tTimeZone                                    |        |
+|          |       | CP-160213 | 0560 | - | One time notification mandatory in Sh-Subs-Notif for UE reachability for IP     |        |
+| Jun 2016 | CT#72 | CP-160239 | 0557 | 1 | Location information alignment with XML                                         | 13.5.0 |
+| Jun 2016 | CT#72 | CP-160215 | 0562 | 1 | Diameter requests for priority traffic during overload control mechanism        | 13.5.0 |
+| 2016-09  | CT#73 | CP-160415 | 0565 | 1 | Notification of changes to RepositoryData for an Alias Public User Identity Set | 13.6.0 |
+| 2016-09  | CT#73 | CP-160431 | 566  | 1 | Request to update data while a previous update request is in progress           | 14.0.0 |
+| 2016-12  | CT#74 | CP-160672 | 0574 | 1 | Notif-Eff in Sh-Pull                                                            | 14.1.0 |
+| 2016-12  | CT#74 | CP-160649 | 0583 | - | Xsd syntax correction                                                           | 14.1.0 |
+| 2016-12  | CT#74 | CP-160649 | 0584 | 1 | RAT type included in EPS location information                                   | 14.1.0 |
+| 2016-12  | CT#74 | CP-160681 | 0585 | 1 | Load Control                                                                    | 14.1.0 |
+| 2016-12  | CT#74 | CP-160664 | 0587 | - | Correction to change IETF drmp draft version to official RFC 7944               | 14.1.0 |
+| 2017-03  | CT#75 | CP-170035 | 0589 | - | Notif-Eff feature corrections in relation to Identity Set                       | 14.2.0 |
+| 2017-03  | CT#75 | CP-170035 | 0591 | 1 | Notification of changes to concurrent subscriptions to multiple Identity Sets   | 14.2.0 |
+| 2017-03  | CT#75 | CP-170035 | 0592 | 1 | DeletedIdentities for IMSPublicIdentities                                       | 14.2.0 |
+| 2017-03  | CT#75 | CP-170035 | 0594 | - | UDR flag description                                                            | 14.2.0 |
+| 2017-03  | CT#75 | CP-170048 | 0593 | 1 | Update of reference for the Diameter base protocol                              | 14.2.0 |
+| 2017-06  | CT#76 | CP-171028 | 0595 | 2 | Handling of EPS Location Information Retrieval                                  | 14.3.0 |
+| 2017-06  | CT#76 | CP-171034 | 0598 | 1 | IMS Trace (ISAT) Reference Updates                                              | 14.3.0 |
+| 2017-06  | CT#76 | CP-171018 | 0602 | 2 | Support for signaling transport level packet marking                            | 14.3.0 |
+| 2017-06  | CT#76 | CP-171040 | 0596 | 1 | External Identifier on Sh                                                       | 15.0.0 |
+| 2017-06  | CT#76 | CP-171040 | 0597 | 1 | IMEI retrieval over Sh                                                          | 15.0.0 |
+| 2017-09  | CT#77 | CP-172016 | 0604 | - | Cardinality of Reference Location Information                                   | 15.1.0 |
+| 2017-09  | CT#77 | CP-172013 | 0607 | - | Correction of DRMP Procedures                                                   | 15.1.0 |
+| 2017-12  | CT#78 | CP-173015 | 0610 | - | Incorrect Implementation of CR#588 (C4-166303)                                  | 15.2.0 |
+| 2018-06  | CT#80 | CP-181131 | 0612 | - | Sh Location Information in 5GS                                                  | 15.3.0 |
+| 2018-09  | CT#81 | CP-182069 | 0613 | 2 | T-ADS info retrieval                                                            | 15.4.0 |
+| 2018-09  | CT#81 | CP-182069 | 0614 | 1 | UE reachability in 5GC                                                          | 15.4.0 |
+| 2018-09  | CT#81 | CP-182069 | 0615 | 2 | Sh User State in 5GS                                                            | 15.4.0 |
+
+|         |        |           |      |   |                                                                                    |        |
+|---------|--------|-----------|------|---|------------------------------------------------------------------------------------|--------|
+| 2018-12 | CT#82  | CP-183094 | 0618 | 2 | Time offset for last UE activity time via Sh                                       | 15.5.0 |
+| 2018-12 | CT#82  | CP-183094 | 0619 | 2 | Clarification on TADS procedure                                                    | 15.5.0 |
+| 2018-12 | CT#82  | CP-183094 | 0617 |   | Sh-IMSI retrieval                                                                  | 15.5.0 |
+| 2019-03 | CT#83  | CP-190048 | 0620 | - | NR Cell Global ID                                                                  | 15.6.0 |
+| 2019-03 | CT#83  | CP-190035 | 0621 | 1 | SMSF address in 5GS Location Information                                           | 15.6.0 |
+| 2019-03 | CT#83  | CP-190048 | 0622 | 1 | Clean up and clarification on transmission of the T-ADS information towards the AS | 15.6.0 |
+| 2019-03 | CT#83  | CP-190164 | 0623 | - | Sh XML schema correction                                                           | 15.6.0 |
+| 2019-09 | CT#85  | CP-192094 | 0626 | 2 | draft-ietf-dime-load published as RFC 8583                                         | 15.7.0 |
+| 2019-09 | CT#85  | CP-192125 | 0624 | 1 | 5GS User State                                                                     | 15.7.0 |
+| 2019-12 | CT#86  | CP-193020 | 0630 | - | Implementation error of CR#0564                                                    | 15.8.0 |
+| 2020-03 | CT#87e | CP-200022 | 0631 | 2 | Introduce support for accessing 5G SRVCC data via Sh                               | 16.0.0 |
+| 2020-06 | CT#88e | CP-201038 | 0623 | 1 | Introduce support for 5G SRVCC support indication                                  | 16.1.0 |
+| 2020-06 | CT#88e | CP-201036 | 0634 | - | Remove Editor's Note regarding obtaining 4G SRVCC capability from UDM              | 16.1.0 |
+| 2020-12 | CT#90e | CP-203022 | 0641 | 1 | Incomplete implemented CR                                                          | 16.2.0 |
+| 2020-12 | CT#90e | CP-203026 | 0637 | 1 | 5G Location Information retrieval                                                  | 16.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29329/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29329/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05354e34c68187d04d6ffd4acecff33c61010c03
--- /dev/null
+++ b/marked/Rel-16/29_series/29329/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:563bccfb68dfd4e48f24ac8ef641d8790a527ea81a54a21f2722f6f19c2b1573
+size 7716
diff --git a/marked/Rel-16/29_series/29329/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29329/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..979ab5ed2f141a80a6573663c4391398b6f02798
--- /dev/null
+++ b/marked/Rel-16/29_series/29329/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c1f097b70375dc7ee19ecdb77df186c7991bc929cad5d5f4263ab827dc7ece02
+size 5806
diff --git a/marked/Rel-16/29_series/29329/raw.md b/marked/Rel-16/29_series/29329/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5236f618ba80cbbaa79c0f61c7e528e3545026b3
--- /dev/null
+++ b/marked/Rel-16/29_series/29329/raw.md
@@ -0,0 +1,1196 @@
+
+
+# 3GPP TS 29.329 V16.2.0 (2021-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Sh Interface based on the Diameter protocol; Protocol details (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "P" is larger and has a red signal wave icon at its base.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                  |    |
+|------------------------------------------------------------------|----|
+| Foreword .....                                                   | 5  |
+| 1 Scope.....                                                     | 6  |
+| 2 References.....                                                | 6  |
+| 3 Definitions, symbols and abbreviations .....                   | 7  |
+| 3.1 Definitions.....                                             | 7  |
+| 3.2 Abbreviations .....                                          | 7  |
+| 4 General .....                                                  | 7  |
+| 5 Use of the Diameter base protocol.....                         | 8  |
+| 6 Diameter application for Sh interface .....                    | 8  |
+| 6.1 Command-Code values .....                                    | 8  |
+| 6.1.1 User-Data-Request (UDR) Command.....                       | 8  |
+| 6.1.2 User-Data-Answer (UDA) Command.....                        | 9  |
+| 6.1.3 Profile-Update-Request (PUR) Command .....                 | 10 |
+| 6.1.4 Profile-Update-Answer (PUA) Command .....                  | 10 |
+| 6.1.5 Subscribe-Notifications-Request (SNR) Command.....         | 11 |
+| 6.1.6 Subscribe-Notifications-Answer (SNA) Command .....         | 11 |
+| 6.1.7 Push-Notification-Request (PNR) Command .....              | 12 |
+| 6.1.8 Push-Notifications-Answer (PNA) Command .....              | 12 |
+| 6.2 Result-Code AVP values.....                                  | 13 |
+| 6.2.1 Success .....                                              | 13 |
+| 6.2.2 Permanent Failures .....                                   | 13 |
+| 6.2.2.1 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100).....      | 13 |
+| 6.2.2.2 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) .....        | 13 |
+| 6.2.2.3 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102).....      | 13 |
+| 6.2.2.4 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103) ..... | 13 |
+| 6.2.2.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104) ..... | 13 |
+| 6.2.2.6 DIAMETER_ERROR_TOO_MUCH_DATA (5008) .....                | 13 |
+| 6.2.2.7 DIAMETER_ERROR_TRANSPARENT_DATA OUT_OF_SYNC (5105) ..... | 13 |
+| 6.2.2.8 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011) .....          | 13 |
+| 6.2.2.9 DIAMETER_ERROR_SUBS_DATA_ABSENT (5106).....              | 13 |
+| 6.2.2.10 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107).....      | 14 |
+| 6.2.2.11 DIAMETER_ERROR_DSAI_NOT_AVAILABLE (5108) .....          | 14 |
+| 6.2.2.12 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002) .....       | 14 |
+| 6.2.3 Transient Failures .....                                   | 14 |
+| 6.2.3.1 DIAMETER_USER_DATA_NOT_AVAILABLE (4100).....             | 14 |
+| 6.2.3.2 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101) .....           | 14 |
+| 6.3 AVPs .....                                                   | 15 |
+| 6.3.1 User-Identity AVP.....                                     | 16 |
+| 6.3.2 MSISDN AVP .....                                           | 16 |
+| 6.3.3 User-Data AVP.....                                         | 16 |
+| 6.3.4 Data-Reference AVP.....                                    | 16 |
+| 6.3.5 Service-Indication AVP.....                                | 17 |
+| 6.3.6 Subs-Req-Type AVP.....                                     | 17 |
+| 6.3.7 Requested-Domain AVP .....                                 | 18 |
+| 6.3.7A Requested-Nodes AVP.....                                  | 18 |
+| 6.3.8 Current-Location AVP .....                                 | 18 |
+| 6.3.9 Server-Name AVP.....                                       | 18 |
+| 6.3.10 Identity-Set AVP .....                                    | 18 |
+| 6.3.11 Supported-Features AVP.....                               | 18 |
+| 6.3.12 Feature-List-ID AVP.....                                  | 19 |
+| 6.3.13 Feature-List AVP.....                                     | 19 |
+| 6.3.14 Supported-Applications AVP.....                           | 19 |
+| 6.3.15 Public-Identity AVP .....                                 | 19 |
+
+|                                                   |                                           |           |
+|---------------------------------------------------|-------------------------------------------|-----------|
+| 6.3.16                                            | Expiry-Time AVP .....                     | 19        |
+| 6.3.17                                            | Send-Data-Indication AVP.....             | 19        |
+| 6.3.18                                            | DSAI-Tag AVP .....                        | 19        |
+| 6.3.19                                            | Wildcarded-Public-Identity AVP .....      | 19        |
+| 6.3.20                                            | Wildcarded-IMPU AVP .....                 | 19        |
+| 6.3.21                                            | Session-Priority AVP .....                | 19        |
+| 6.3.22                                            | One-Time-Notification AVP .....           | 19        |
+| 6.3.23                                            | Serving-Node-Indication AVP .....         | 20        |
+| 6.3.24                                            | Repository-Data-ID AVP .....              | 20        |
+| 6.3.25                                            | Sequence-Number AVP .....                 | 20        |
+| 6.3.26                                            | Pre-paging-Supported AVP.....             | 20        |
+| 6.3.27                                            | Local-Time-Zone-Indication AVP .....      | 20        |
+| 6.3.28                                            | UDR-Flags.....                            | 20        |
+| 6.3.29                                            | Call-Reference-Info AVP.....              | 21        |
+| 6.3.30                                            | Call-Reference-Number AVP.....            | 21        |
+| 6.3.31                                            | AS-Number AVP.....                        | 21        |
+| 6.3.32                                            | OC-Supported-Features .....               | 21        |
+| 6.3.33                                            | OC-OLR .....                              | 21        |
+| 6.3.34                                            | DRMP AVP.....                             | 21        |
+| 6.3.35                                            | Load.....                                 | 21        |
+| 6.4                                               | Use of namespaces .....                   | 21        |
+| 6.4.1                                             | AVP codes .....                           | 21        |
+| 6.4.2                                             | Experimental-Result-Code AVP values ..... | 22        |
+| 6.4.3                                             | Command Code values.....                  | 22        |
+| 6.4.4                                             | Application-ID value .....                | 22        |
+| 7                                                 | Special Requirements.....                 | 23        |
+| 7.1                                               | Version Control.....                      | 23        |
+| <b>Annex A (informative): Change history.....</b> |                                           | <b>24</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document defines a transport protocol for use in the IP multimedia (IM) Core Network (CN) subsystem based on the Diameter base protocol as specified in IETF RFC 6733 [15].
+
+The present document is applicable to:
+
+- The Sh interface between an AS and the HSS.
+- The Sh interface between an SCS and the HSS.
+
+Whenever it is possible this document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter base protocol as specified in IETF RFC 6733 [15]. Where this is not possible, extensions to the Diameter base protocol as specified in IETF RFC 6733 [15] are defined within this document.
+
+# --- 2 References
+
+The following documents contain provisions, which through reference in this text constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 29.328 "IP Multimedia (IM) Subsystem Sh interface; signalling flows and message contents".
+- [2] 3GPP TS 33.210 "3G Security; Network Domain Security; IP Network Layer Security".
+- [3] IETF RFC 2960 "Stream Control Transmission Protocol".
+- [4] Void.
+- [5] IETF RFC 2234 "Augmented BNF for syntax specifications".
+- [6] 3GPP TS 29.229 "Cx and Dx Interfaces based on the Diameter protocol; protocol details".
+- [7] IETF RFC 3589 "Diameter Command Codes for Third Generation Partnership Project (3GPP) Release 5".
+- [8] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- [9] 3GPP TR 33.978 "Security aspects of early IP Multimedia Subsystem (IMS) (Release 6)".
+- [10] 3GPP TS 29.364 "IMS Application Server Service Data Descriptions for AS interoperability".
+
+- [11] 3GPP TS 29.002 "Mobile Application Part (MAP) specification".
+- [12] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [13] IETF RFC 7944: "Diameter Routing Message Priority".
+- [14] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [15] IETF RFC 6733: "Diameter Base Protocol".
+- [16]] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+Refer to IETF RFC 6733 [15] for the definitions of some terms used in this document.
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Attribute-Value Pair:** see IETF RFC 6733 [15], it corresponds to an Information Element in a Diameter message.
+
+**Server:** SIP-server.
+
+**User data:** user profile data.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                              |
+|------|----------------------------------------------|
+| AAA  | Authentication, Authorization and Accounting |
+| AS   | Application Server                           |
+| ABNF | Augmented Backus-Naur Form                   |
+| AVP  | Attribute-Value Pair                         |
+| CN   | Core Network                                 |
+| DRMP | Diameter Routing Message Priority            |
+| DSCP | Differentiated Services Code Point           |
+| HSS  | Home Subscriber Server                       |
+| IANA | Internet Assigned Numbers Authority          |
+| IETF | Internet Engineering Task Force              |
+| IMS  | IP Multimedia Subsystem                      |
+| NDS  | Network Domain Security                      |
+| RFC  | Request For Comment                          |
+| SCTP | Stream Control Transport Protocol            |
+| UCS  | Universal Character Set                      |
+| URL  | Uniform Resource Locator                     |
+| UTF  | UCS Transformation Formats                   |
+
+# --- 4 General
+
+he Diameter base protocol as specified in IETF RFC 6733 [15] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 6 of this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified.
+
+# 5 Use of the Diameter base protocol
+
+The same clarifications of clause 5 of 3GPP TS 29.229 [6] shall apply to the Sh interface. An exception is that the application identifier for this application is defined in chapter 6.
+
+# 6 Diameter application for Sh interface
+
+This clause specifies a Diameter application that allows a Diameter server and a Diameter client:
+
+- to download and update transparent and non-transparent user data
+- to request and send notifications on changes on user data
+
+The Sh interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP ( <http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the Sh interface application is 16777217 (allocated by IANA).
+
+## 6.1 Command-Code values
+
+This clause defines Command-Code values for this Diameter application.
+
+Every command is defined by means of the ABNF syntax (as defined in RFC 2234 [5]), according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [15]. Whenever the definition and use of an AVP is not specified in this document, what is stated in 3GPP TS 29.229 [6] shall apply.
+
+NOTE: As the Diameter commands described in this specification have been defined based on the former specification of the Diameter base protocol, the Vendor-Specific-Application-Id AVP is still listed as a required AVP (an AVP indicated as {AVP}) in the command code format specifications defined in this specification to avoid backward compatibility issues, even if the use of this AVP has been deprecated in the new specification of the Diameter base protocol (IETF RFC 6733 [15]).
+
+The command codes for the Sh interface application are taken from the range allocated by IANA in IETF RFC 3589 [7] as assigned in this specification. For these commands, the Application-ID field shall be set to 16777217 (application identifier of the Sh interface application, allocated by IANA).
+
+The following Command Codes are defined in this specification:
+
+**Table 6.1.1: Command-Code values**
+
+| Command-Name                    | Abbreviation | Code | Clause |
+|---------------------------------|--------------|------|--------|
+| User-Data-Request               | UDR          | 306  | 6.1.1  |
+| User-Data-Answer                | UDA          | 306  | 6.1.2  |
+| Profile-Update-Request          | PUR          | 307  | 6.1.3  |
+| Profile-Update-Answer           | PUA          | 307  | 6.1.4  |
+| Subscribe-Notifications-Request | SNR          | 308  | 6.1.5  |
+| Subscribe-Notifications-Answer  | SNA          | 308  | 6.1.6  |
+| Push-Notification-Request       | PNR          | 309  | 6.1.7  |
+| Push-Notification-Answer        | PNA          | 309  | 6.1.8  |
+
+### 6.1.1 User-Data-Request (UDR) Command
+
+The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the 'R' bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data.
+
+Message Format
+
+```
+< User-Data -Request> ::= < Diameter Header: 306, REQ, PXY, 16777217>
+< Session-Id >
+```
+
+```
+
+[ DRMP ]
+{ Vendor-Specific-Application-Id }
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+{ Destination-Realm }
+    *[ Supported-Features ]
+    { User-Identity }
+    [ Wildcarded-Public-Identity ]
+    [ Wildcarded-IMPU ]
+    [ Server-Name ]
+    *[ Service-Indication ]
+    *{ Data-Reference }
+    *[ Identity-Set ]
+    [ Requested-Domain ]
+    [ Current-Location ]
+    *[ DSAI-Tag ]
+    [ Session-Priority ]
+    [ User-Name ]
+    [ Requested-Nodes ]
+    [ Serving-Node-Indication ]
+    [ Pre-paging-Supported ]
+    [ Local-Time-Zone-Indication ]
+    [ UDR-Flags ]
+    [ Call-Reference-Info ]
+    [ OC-Supported-Features ]
+
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.1.2 User-Data-Answer (UDA) Command
+
+The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the User-Data-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2 or in 3GPP TS 29.229 [6].
+
+#### Message Format
+
+```
+
+< User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777217 >
+    < Session-Id >
+    [ DRMP ]
+    { Vendor-Specific-Application-Id }
+    [ Result-Code ]
+        [ Experimental-Result ]
+        { Auth-Session-State }
+        { Origin-Host }
+        { Origin-Realm }
+        *[ Supported-Features ]
+        [ Wildcarded-Public-Identity ]
+        [ Wildcarded-IMPU ]
+        [ User-Data ]
+        [ OC-Supported-Features ]
+        [ OC-OLR ]
+        *[ Load ]
+        *[ AVP ]
+        [ Failed-AVP ]
+        *[ Proxy-Info ]
+
+*[ Route-Record ]
+
+```
+
+### 6.1.3 Profile-Update-Request (PUR) Command
+
+The Profile-Update-Request (PUR) command, indicated by the Command-Code field set to 307 and the 'R' bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to update user data in the server.
+
+#### Message Format
+
+```
+< Profile-Update-Request > ::= < Diameter Header: 307, REQ, PXY, 16777217 >
+    < Session-Id >
+    [ DRMP ]
+    { Vendor-Specific-Application-Id }
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    *[ Supported-Features ]
+    { User-Identity }
+    [ Wildcarded-Public-Identity ]
+    [ Wildcarded-IMPU ]
+    [ User-Name ]
+    *{ Data-Reference }
+    { User-Data }
+    [ OC-Supported-Features ]
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+NOTE: More than one Data-Reference AVP may be present in the message only if both the AS and the HSS support the Update-Eff-Enhance feature. How the AS knows whether the HSS supports the Update-Eff-Enhance feature is implementation issue, e.g. the AS can get the information from a previous PUA message.
+
+### 6.1.4 Profile-Update-Answer (PUA) Command
+
+The Profile-Update-Answer (PUA) command, indicated by the Command-Code field set to 307 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Profile-Update-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2 or in 3GPP TS 29.229 [6].
+
+#### Message Format
+
+```
+< Profile-Update-Answer > ::= < Diameter Header: 307, PXY, 16777217 >
+    < Session-Id >
+    [ DRMP ]
+    { Vendor-Specific-Application-Id }
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Wildcarded-Public-Identity ]
+    [ Wildcarded-IMPU ]
+    [ Repository-Data-ID ]
+    [ Data-Reference ]
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    [ OC-OLR ]
+    *[ Load ]
+    *[ AVP ]
+    [ Failed-AVP ]
+    *[ Proxy-Info ]
+```
+
+\*[ Route-Record ]
+
+NOTE: The Data-Reference AVP may be present in the message only if both the AS and the HSS support the Update-Eff-Enhance feature.
+
+### 6.1.5 Subscribe-Notifications-Request (SNR) Command
+
+The Subscribe-Notifications-Request (SNR) command, indicated by the Command-Code field set to 308 and the 'R' bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request notifications of changes in user data.
+
+Message Format
+
+```
+< Subscribe-Notifications-Request > ::= < Diameter Header: 308, REQ, PXY, 16777217 >
+    < Session-Id >
+    [ DRMP ]
+    { Vendor-Specific-Application-Id }
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    *[ Supported-Features ]
+    { User-Identity }
+    [ Wildcarded-Public-Identity ]
+    [ Wildcarded-IMPU ]
+    *[ Service-Indication ]
+    [ Send-Data-Indication ]
+    [ Server-Name ]
+    { Subs-Req-Type }
+    *[ Data-Reference ]
+    *[ Identity-Set ]
+    [ Expiry-Time ]
+    *[ DSAI-Tag ]
+    [One-Time-Notification]
+    [ User-Name ]
+    [ OC-Supported-Features ]
+
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.1.6 Subscribe-Notifications-Answer (SNA) Command
+
+The Subscribe-Notifications-Answer command, indicated by the Command-Code field set to 308 and the 'R' bit cleared in the Command Flags field, is sent by a server in response to the Subscribe-Notifications-Request command. The Result-Code or Experimental-Result AVP may contain one of the values defined in clause 6.2 or in 3GPP TS 29.229 [6].
+
+Message Format
+
+```
+< Subscribe-Notifications-Answer > ::= < Diameter Header: 308, PXY, 16777217 >
+    < Session-Id >
+    [ DRMP ]
+    { Vendor-Specific-Application-Id }
+    { Auth-Session-State }
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Origin-Host }
+    { Origin-Realm }
+    [ Wildcarded-Public-Identity ]
+```
+
+```
+
+[ Wildcarded-IMPU ]
+*[ Supported-Features ]
+[ User-Data ]
+[ Expiry-Time ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.1.7 Push-Notification-Request (PNR) Command
+
+The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the 'R' bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the user data in the server.
+
+#### Message Format
+
+```
+
+< Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777217 >
+< Session-Id >
+[ DRMP ]
+{ Vendor-Specific-Application-Id }
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+{ Destination-Host }
+{ Destination-Realm }
+*[ Supported-Features ]
+{ User-Identity }
+[ Wildcarded-Public-Identity ]
+[ Wildcarded-IMPU ]
+[ User-Name ]
+{ User-Data }
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.1.8 Push-Notifications-Answer (PNA) Command
+
+The Push-Notifications-Answer (PNA) command, indicated by the Command-Code field set to 309 and the 'R' bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request command. The Experimental-Result AVP may contain one of the values defined in clause 6.2 or in 3GPP TS 29.229 [6].
+
+#### Message Format
+
+```
+
+< Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777217 >
+< Session-Id >
+[ DRMP ]
+{ Vendor-Specific-Application-Id }
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ Supported-Features ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+## 6.2 Result-Code AVP values
+
+This clause defines new result code values that must be supported by all Diameter implementations that conform to this specification. The result codes defined in 3GPP TS 29.229 [6] are also applicable. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent.
+
+### 6.2.1 Success
+
+Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed.
+
+No result codes within this category have been defined so far.
+
+### 6.2.2 Permanent Failures
+
+Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again.
+
+#### 6.2.2.1 DIAMETER\_ERROR\_USER\_DATA\_NOT\_RECOGNIZED (5100)
+
+The data received by the AS is not supported or recognized.
+
+#### 6.2.2.2 DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED (5101)
+
+The requested operation is not allowed for the user
+
+#### 6.2.2.3 DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_READ (5102)
+
+The requested user data is not allowed to be read.
+
+#### 6.2.2.4 DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_MODIFIED (5103)
+
+The requested user data is not allowed to be modified.
+
+#### 6.2.2.5 DIAMETER\_ERROR\_USER\_DATA\_CANNOT\_BE\_NOTIFIED (5104)
+
+The requested user data is not allowed to be notified on changes.
+
+#### 6.2.2.6 DIAMETER\_ERROR\_TOO\_MUCH\_DATA (5008)
+
+The size of the data pushed to the receiving entity exceeds its capacity. This error code is defined in 3GPP TS 29.229 [6].
+
+#### 6.2.2.7 DIAMETER\_ERROR\_TRANSPARENT\_DATA OUT\_OF\_SYNC (5105)
+
+The request to update the repository data at the HSS could not be completed because the requested update is based on an out-of-date version of the repository data. That is, the sequence number in the Sh-Update Request message, does not match with the immediate successor of the associated sequence number stored for that repository data at the HSS. It is also used where an AS tries to create a new set of repository data when the identified repository data already exists in the HSS.
+
+#### 6.2.2.8 DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED (5011)
+
+See 3GPP TS 29.229 [6] clause 6.2.2.11.
+
+#### 6.2.2.9 DIAMETER\_ERROR\_SUBS\_DATA\_ABSENT (5106)
+
+The Application Server requested to subscribe to changes to Repository Data that is not present in the HSS.
+
+#### 6.2.2.10 DIAMETER\_ERROR\_NO\_SUBSCRIPTION\_TO\_DATA (5107)
+
+The AS received a notification of changes of some information to which it is not subscribed.
+
+#### 6.2.2.11 DIAMETER\_ERROR\_DSAI\_NOT\_AVAILABLE (5108)
+
+The Application Server addressed a DSAI not configured in the HSS.
+
+#### 6.2.2.12 DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH (5002)
+
+See 3GPP TS 29.229 [6]
+
+### 6.2.3 Transient Failures
+
+Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future.
+
+#### 6.2.3.1 DIAMETER\_USER\_DATA\_NOT\_AVAILABLE (4100)
+
+The requested user data is not available at this time to satisfy the requested operation.
+
+#### 6.2.3.2 DIAMETER\_PRIOR\_UPDATE\_IN\_PROGRESS (4101)
+
+The request to update data at the HSS could not be completed for one of the following reasons:
+
+- If the Data Reference is Repository Data, then the related Repository Data is currently being updated by another entity;
+- If the Data Reference is other than Repository Data, then the related data is currently being updated.
+
+## 6.3 AVPs
+
+The following table describes the Diameter AVPs defined for the Sh interface protocol, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted.
+
+**Table 6.3.1: Diameter Multimedia Application AVPs**
+
+| Attribute Name             | AVP Code      | Clause defined | Value Type  | AVP Flag rules |     |            |          |             |
+|----------------------------|---------------|----------------|-------------|----------------|-----|------------|----------|-------------|
+|                            |               |                |             | Must           | May | Should not | Must not | May Encrypt |
+| User-Identity              | 700           | 6.3.1          | Grouped     | M, V           |     |            |          | No          |
+| MSISDN                     | 701           | 6.3.2          | OctetString | M, V           |     |            |          | No          |
+| User-Data                  | 702           | 6.3.3          | OctetString | M, V           |     |            |          | No          |
+| Data-Reference             | 703           | 6.3.4          | Enumerated  | M, V           |     |            |          | No          |
+| Service-Indication         | 704           | 6.3.5          | OctetString | M, V           |     |            |          | No          |
+| Subs-Req-Type              | 705           | 6.3.6          | Enumerated  | M, V           |     |            |          | No          |
+| Requested-Domain           | 706           | 6.3.7          | Enumerated  | M, V           |     |            |          | No          |
+| Current-Location           | 707           | 6.3.8          | Enumerated  | M, V           |     |            |          | No          |
+| Identity-Set               | 708           | 6.3.10         | Enumerated  | V              |     |            | M        | No          |
+| Expiry-Time                | 709           | 6.3.16         | Time        | V              |     |            | M        | No          |
+| Send-Data-Indication       | 710           | 6.3.17         | Enumerated  | V              |     |            | M        | No          |
+| Server-Name                | 602           | 6.3.9          | UTF8String  | M, V           |     |            |          | No          |
+| Supported-Features         | 628           | 6.3.11         | Grouped     | V              | M   |            |          | No          |
+| Feature-List-ID            | 629           | 6.3.12         | Unsigned32  | V              |     |            | M        | No          |
+| Feature-List               | 630           | 6.3.13         | Unsigned32  | V              |     |            | M        | No          |
+| Supported-Applications     | 631           | 6.3.14         | Grouped     | V              |     |            | M        | No          |
+| Public-Identity            | 601           | 6.3.15         | UTF8String  | M, V           |     |            |          | No          |
+| DSAI-Tag                   | 711           | 6.3.18         | OctetString | M, V           |     |            |          | No          |
+| Wildcarded-Public-Identity | 634           | 6.3.19         | UTF8String  | V              |     |            | M        | No          |
+| Wildcarded-IMPU            | 636           | 6.3.20         | UTF8String  | V              |     |            | M        | No          |
+| Session-Priority           | 650           | 6.3.21         | Enumerated  | V              |     |            | M        | No          |
+| One-Time-Notification      | 712           | 6.3.22         | Enumerated  | V              |     |            | M        | No          |
+| Requested-Nodes            | 713           | 6.3.7A         | Unsigned32  | V              |     |            | M        | No          |
+| Serving-Node-Indication    | 714           | 6.3.23         | Enumerated  | V              |     |            | M        | No          |
+| Repository-Data-ID         | 715           | 6.3.24         | Grouped     | V              |     |            | M        | No          |
+| Sequence-Number            | 716           | 6.3.25         | Unsigned32  | V              |     |            | M        | No          |
+| Pre-paging-Supported       | 717           | 6.3.26         | Enumerated  | V              |     |            | M        | No          |
+| Local-Time-Zone-Indication | 718           | 6.3.27         | Enumerated  | V              |     |            | M        | No          |
+| UDR-Flags                  | 719           | 6.3.28         | Unsigned32  | V              |     |            | M        | No          |
+| Call-Reference-Info        | 720           | 6.3.29         | Grouped     | V              |     |            | M        | No          |
+| Call-Reference-Number      | 721           | 6.3.30         | OctetString | V              |     |            | M        | No          |
+| AS-Number                  | 722           | 6.3.31         | OctetString | V              |     |            | M        | No          |
+| OC-Supported-Features      | 621<br>NOTE 3 | 6.3.32         | Grouped     |                |     |            | M, V     | No          |
+| OC-OLR                     | 623<br>NOTE 3 | 6.3.33         | Grouped     |                |     |            | M, V     | No          |
+| DRMP                       | 301<br>NOTE 4 | 6.3.34         | Enumerated  |                |     |            | M, V     | No          |
+| Load                       | NOTE 5        | 6.3.35         | Grouped     |                |     |            | M, V     | No          |
+
+NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see 3GPP TS 29.229 [6].
+
+NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
+
+NOTE 3: The value of these attributes is defined in IETF RFC 7683 [12].
+
+NOTE 4: The value of this attribute is defined in IETF RFC 7944 [13].
+
+NOTE 5: The value of this attribute is defined in IETF RFC 8583 [14].
+
+The following table specifies the Diameter AVPs re-used by the Sh interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within Sh.
+
+**Table 6.3/2: Sh re-used Diameter AVPs**
+
+| Attribute Name                                                                                                                                                                                                                                                                                                                                                                         | Reference           | Comments | M-bit    |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------|----------|
+| External-Identifier                                                                                                                                                                                                                                                                                                                                                                    | 3GPP TS 29.336 [16] |          | Must set |
+| NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies.                                                                                                                                                     |                     |          |          |
+| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. |                     |          |          |
+
+### 6.3.1 User-Identity AVP
+
+The User-Identity AVP is of type Grouped. This AVP contains either a Public- Identity AVP or an MSISDN AVP or an External-Identifier AVP.
+
+AVP format
+
+User-Identity ::= <AVP header: 700 10415>
+
+[Public-Identity]
+
+[MSISDN]
+
+[External-Identifier]
+
+\*[AVP]
+
+### 6.3.2 MSISDN AVP
+
+The MSISDN AVP is of type OctetString. This AVP contains an MSISDN, in international number format as described in ITU-T Rec E.164 [8], encoded as a TBCD-string, i.e. digits from 0 through 9 are encoded 0000 to 1001; 1111 is used as a filler when there is an odd number of digits; bits 8 to 5 of octet n encode digit 2n; bits 4 to 1 of octet n encode digit 2(n-1)+1.
+
+### 6.3.3 User-Data AVP
+
+The User-Data AVP is of type OctetString. This AVP contains the user data requested in the UDR/UDA, SNR/SNA and PNR/PNA operations and the data to be modified in the PUR/PUA operation. The exact content and format of this AVP is described in 3GPP TS 29.328 [1] Annex C as Sh-Data.
+
+### 6.3.4 Data-Reference AVP
+
+The Data-Reference AVP is of type Enumerated, and indicates the type of the requested user data in the operation UDR and SNR. Its exact values and meaning is defined in 3GPP TS 29.328 [1]. The following values are defined (more details are given in 3GPP TS 29.328 [1]):
+
+RepositoryData (0)
+
+IMSPublicIdentity (10)
+
+IMSUUserState (11)
+
+S-CSCFName (12)
+
+InitialFilterCriteria (13)
+
+This value is used to request initial filter criteria relevant to the requesting AS
+
+LocationInformation (14)
+
+UserState (15)
+
+ChargingInformation (16)
+
+MSISDN (17)
+
+PSIActivation (18)
+
+DSAI (19)
+
+ServiceLevelTraceInfo (21)
+
+IPAddressSecureBindingInformation (22)
+
+ServicePriorityLevel (23)
+
+SMSRegistrationInfo (24)
+
+UEReachabilityForIP (25)
+
+TADSinformation (26)
+
+STN-SR (27)
+
+UE-SRVCC-Capability (28)
+
+ExtendedPriority (29)
+
+CSRN (30)
+
+ReferenceLocationInformation (31)
+
+IMSI (32)
+
+IMSPrivateUserIdentity (33)
+
+IMEISV (34)
+
+UE-5G-SRVCC-Capability (35)
+
+NOTE: Value 20 is reserved.
+
+### 6.3.5 Service-Indication AVP
+
+The Service-Indication AVP is of type OctetString. This AVP contains the Service Indication that identifies a service or a set of services in an AS and the related repository data in the HSS. Standardized values of Service-Indication identifying a standardized service or set of services in the AS and standardized format of the related repository data are defined in 3GPP TS 29.364 [10].
+
+### 6.3.6 Subs-Req-Type AVP
+
+The Subs-Req-Type AVP is of type Enumerated, and indicates the type of the subscription-to-notifications request. The following values are defined:
+
+Subscribe (0)
+
+This value is used by an AS to subscribe to notifications of changes in data.
+
+Unsubscribe (1)
+
+This value is used by an AS to unsubscribe to notifications of changes in data.
+
+### 6.3.7 Requested-Domain AVP
+
+The Requested-Domain AVP is of type Enumerated, and indicates the access domain for which certain data (e.g. user state) are requested. The following values are defined:
+
+CS-Domain (0)
+
+The requested data apply to the CS domain.
+
+PS-Domain (1)
+
+The requested data apply to the PS domain.
+
+### 6.3.7A Requested-Nodes AVP
+
+The Requested-Nodes AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.7A/1:
+
+**Table 6.3.7A/1: Requested-Nodes**
+
+| Bit | Name                 | Description                                              |
+|-----|----------------------|----------------------------------------------------------|
+| 0   | MME                  | The requested data apply to the MME                      |
+| 1   | SGSN                 | The requested data apply to the SGSN                     |
+| 2   | 3GPP-AAA-SERVER-TWAN | The requested data apply to the 3GPP AAA Server for TWAN |
+| 3   | AMF                  | The requested data apply to the AMF (for 3GPP access)    |
+
+### 6.3.8 Current-Location AVP
+
+The Current-Location AVP is of type Enumerated, and indicates whether an active location retrieval has to be initiated or not:
+
+DoNotNeedInitiateActiveLocationRetrieval (0)
+
+The request indicates that the initiation of an active location retrieval is not required.
+
+InitiateActiveLocationRetrieval (1)
+
+It is requested that an active location retrieval is initiated.
+
+### 6.3.9 Server-Name AVP
+
+The Server-Name contains a SIP-URL used to identify an AS. See 3GPP TS 29.229 [6] for further description of this AVP.
+
+### 6.3.10 Identity-Set AVP
+
+The Identity-Set AVP is of type Enumerated and indicates the requested set of IMS Public Identities. The following values are defined:
+
+ALL\_IDENTITIES (0)
+
+REGISTERED\_IDENTITIES (1)
+
+IMPLICIT\_IDENTITIES (2)
+
+ALIAS\_IDENTITIES (3)
+
+### 6.3.11 Supported-Features AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.29.
+
+### 6.3.12 Feature-ID AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.30.
+
+### 6.3.13 Feature-List AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.31.
+
+### 6.3.14 Supported-Applications AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.32.
+
+### 6.3.15 Public-Identity AVP
+
+The Public-Identity AVP contains a Public User Identity. See 3GPP TS 29.229 [6] for the definition of this AVP.
+
+### 6.3.16 Expiry-Time AVP
+
+The Expiry-Time AVP is of type Time. This AVP contains the expiry time of subscriptions to notifications in the HSS.
+
+### 6.3.17 Send-Data-Indication AVP
+
+The Send-Data-Indication AVP is of type Enumerated. If present it indicates that the sender requests the User-Data. The following values are defined:
+
+USER\_DATA\_NOT\_REQUESTED (0)
+
+USER\_DATA\_REQUESTED (1)
+
+### 6.3.18 DSAI-Tag AVP
+
+The DSAI-Tag AVP is of type OctetString. This AVP contains the DSAI-Tag identifying the instance of the Dynamic Service Activation Information being accessed for the Public Identity.
+
+### 6.3.19 Wildcarded-Public-Identity AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.35 for the definition of the Wildcarded-Public-Identity AVP. This AVP only contains a Wildcarded PSI over Sh interface.
+
+### 6.3.20 Wildcarded-IMPU AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.43.
+
+### 6.3.21 Session-Priority AVP
+
+See 3GPP TS 29.229 [6] clause 6.3.56.
+
+### 6.3.22 One-Time-Notification AVP
+
+The One-Time-Notification AVP is of type Enumerated. If present it indicates that the sender requests to be notified only one time. The following values are defined:
+
+ONE\_TIME\_NOTIFICATION\_REQUESTED (0)
+
+This AVP is only applicable to UE reachability for IP (25)
+
+### 6.3.23 Serving-Node-Indication AVP
+
+The Serving-Node-Indication AVP is of type Enumerated. If present it indicates that the sender does not require any location information other than the Serving Node Addresses/Identities requested (e.g. MME name, VLR number). Other location information (e.g. Global Cell ID, Tracking Area ID) may be absent. The following values are defined:
+
+ONLY\_SERVING\_NODES\_REQUIRED (0)
+
+### 6.3.24 Repository-Data-ID AVP
+
+The Repository-Data-ID AVP is of type Grouped. This AVP shall contain a Service-Indication AVP and a Sequence-Number AVP.
+
+AVP format
+
+```
+Repository-Data-ID ::= <AVP header: 715 10415>
+    {Service-Indication}
+    {Sequence-Number}
+    *[AVP]
+```
+
+### 6.3.25 Sequence-Number AVP
+
+The Sequence-Number AVP is of type Unsigned32. This AVP contains a number associated to a repository data.
+
+### 6.3.26 Pre-paging-Supported AVP
+
+The Pre-paging-Supported AVP is of type Enumerated. It indicates whether the sender supports pre-paging or not. The following values are defined:
+
+PREPAGING\_NOT\_SUPPORTED (0)
+
+PREPAGING\_SUPPORTED (1)
+
+If this AVP is not present in the command, the default value is PREPAGING\_NOT\_SUPPORTED (0).
+
+### 6.3.27 Local-Time-Zone-Indication AVP
+
+The Local-Time-Zone-Indication AVP is of type Enumerated. If present it indicates that the Local Time Zone information (time zone and daylight saving time) of the visited network where the UE is attached is requested with or without other location information. The following values are defined:
+
+ONLY\_LOCAL\_TIME\_ZONE\_REQUESTED (0)
+
+LOCAL\_TIME\_ZONE\_WITH\_LOCATION\_INFO\_REQUESTED (1)
+
+### 6.3.28 UDR-Flags
+
+The UDR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in 3GPP TS 29.328 [1].
+
+**Table 6.3.28/1: UDR-Flags**
+
+| Bit   | Name                                                                                                                       |
+|-------|----------------------------------------------------------------------------------------------------------------------------|
+| 0     | Location-Information-EPS-Supported                                                                                         |
+| 1     | RAT-Type-Requested                                                                                                         |
+| NOTE: | Bits not defined in this table shall be cleared by the sender of the request and discarded by the receiver of the request. |
+
+### 6.3.29 Call-Reference-Info AVP
+
+The Call-Reference-Info AVP is of type Grouped. This AVP shall contain a Call-Reference-Number AVP and an AS-Number AVP.
+
+AVP format
+
+```
+Call-Reference-Info ::= <AVP header: 720 10415>
+                        {Call-Reference-Number}
+                        {AS-Number}
+                        *[AVP]
+```
+
+### 6.3.30 Call-Reference-Number AVP
+
+The Call-Reference-Number AVP is of type OctetString. The exact content and format of this AVP is described in 3GPP TS 29.002 [11].
+
+### 6.3.31 AS-Number AVP
+
+The AS-Number AVP is of type OctetString. The exact content and format of this AVP corresponds to the gmsc-address parameter described in 3GPP TS 29.002 [11].
+
+### 6.3.32 OC-Supported-Features
+
+The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism.
+
+### 6.3.33 OC-OLR
+
+The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism.
+
+### 6.3.34 DRMP AVP
+
+The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [13]. This AVP allows the HSS/SLF and the AS/OSA SCS to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.
+
+### 6.3.35 Load
+
+The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [14]. This AVP is used to support the Diameter load control mechanism.
+
+## 6.4 Use of namespaces
+
+This clause contains the namespaces that have either been created in this specification, or the values assigned to existing namespaces managed by IANA.
+
+### 6.4.1 AVP codes
+
+This specification assigns the AVP values from the AVP Code namespace managed by 3GPP for its Diameter vendor-specific applications. See clause 6.3 for the assignment of the namespace in this specification.
+
+### 6.4.2 Experimental-Result-Code AVP values
+
+This specification has assigned Experimental-Result-Code AVP values 4100-4101 and 5100-5105. See clause 6.2.
+
+### 6.4.3 Command Code values
+
+This specification assigns the values 306-309 from the range allocated by IANA to 3GPP in IETF RFC 3589 [7].
+
+### 6.4.4 Application-ID value
+
+IANA has allocated the value 16777217 for the 3GPP Sh interface application.
+
+# 7 Special Requirements
+
+## 7.1 Version Control
+
+The version control mechanisms specified in 3GPP TS 29.229 [6] clauses 7.1, 7.2 and 7.3 apply to this specification.
+
+The following table of features shall apply to the Sh interface.
+
+**Table 7.1.1: Features of feature list 1 used in Sh**
+
+| Feature bit                                                                                                                                                                                                                                                                                                                                | Feature            | M/O | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                                                                                                                                                                                                                                                          | Notif-Eff          | M   | This feature is applicable to the UDR/UDA, SNR/SNA and PNR/PNA command pairs. It requires support in both the HSS and the AS.<br>If multiple subscriptions to notifications are associated with a Public User Identity, the HSS may combine the notifications for multiple Data References and/or Service Indications and/or Identity Sets into a single Push-Notification-Request message.<br>The User-Data-Request / Answer and the Subscribe-Notifications-Request / Answer allow multiple Data References, Service Indications and Identity Sets.<br>The User-Data-Answer and Push-Notification-Request allow combining multiple DataReference items resulting in the User Data AVP including a single XML document with the separable XML clauses populated. |
+| 1                                                                                                                                                                                                                                                                                                                                          | Update-Eff         | O   | This feature is applicable to the PUR/PUA commands. If both the HSS and the AS support this feature, a PUR command where the Data reference type is Repository Data, may contain an XML document with several Repository Data instances.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| 2                                                                                                                                                                                                                                                                                                                                          | Update-Eff-Enhance | O   | This feature is an enhancement of the Update-Eff feature and requires Update-Eff is supported. It is applicable to the PUR/PUA commands. If both the HSS and the AS support this feature, a PUR command may contain an XML document with several Data instances.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| 3                                                                                                                                                                                                                                                                                                                                          | Additional-MSISDN  | O   | This feature is applicable to UDR/UDA commands. It requires support in both HSS and AS.<br>If enabled, it extends the information returned with DataReference=17. Instead of returning only MSISDN, it includes ExtendedMSISDN. See 3GPP TS 29.328 [1] for more information.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".<br>Feature: A short name that can be used to refer to the bit and to the feature, e.g. "MOM".<br>M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").<br>Description: A clear textual description of the feature. |                    |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+
+The following table shall apply to the Sh interface; the column Application identifier lists the used application identifiers on Sh and 3GPP.
+
+**Table 7.1.2: Application identifiers used in Sh**
+
+| Application identifier | First applied |
+|------------------------|---------------|
+| 16777217               | 3GPP Rel-5    |
+
+# Annex A (informative): Change history
+
+| Date      | TSG # | TSG Doc.  | CR#  | Rev | Subject/Comment                                                                            | Out   |
+|-----------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------|-------|
+| June 2002 | CN#16 | NP-020266 |      |     | Version 2.0.1 present in CN#16 for approval                                                | 5.0.0 |
+| Sep 2002  | CN#17 | NP-020450 | 2    | 1   | Cancellation of subscriptions to notifications                                             | 5.1.0 |
+| Sep 2002  | CN#17 | NP-020450 | 3    | 1   | Addition of AVPs to User-Data-Request                                                      | 5.1.0 |
+| Dec 2002  | CN#18 | NP-020592 | 6    | -   | Error handling in HSS when being updated with too much data                                | 5.2.0 |
+| Mar 2003  | CN#19 | NP-030102 | 005  | 1   | Initial Filter Criteria                                                                    | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 007  | 2   | Update after Diameter has become RFC                                                       | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 011  | -   | Missing code-point in Data-Reference AVP                                                   | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 013  | -   | Registration State Alignment                                                               | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 008  | -   | Correction of the Application Server Identification type for Initial Filter Criteria usage | 5.3.0 |
+| Mar 2003  | CN#19 | NP-030102 | 009  | -   | Clarification on Sh interface for charging purposes                                        | 5.3.0 |
+| Jun 2003  | CN#20 | NP-030216 | 014  | 1   | Co-ordination of Update of Repository Data                                                 | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 015  | 1   | Command code correction for UDA plus editorial corrections                                 | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 016  | -   | Correction on Current-Location AVP values                                                  | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 018  | -   | Correction to the use of User-Identity                                                     | 5.4.0 |
+| Jun 2003  | CN#20 | NP-030216 | 019  | 1   | Correction to the use of Data-Reference                                                    | 5.4.0 |
+| Dec 2003  | CN#22 |           |      |     | Editorial changes in application IDs and references [4] and [7].                           | 5.4.1 |
+| Mar 2004  | CN#23 | NP-040135 | 031  | 1   | Add MSISDN to set of Data that may be downloaded                                           | 5.5.0 |
+| Mar 2004  | CN#23 | NP-040055 | 032  | 2   | Introduction of 'Identity-Set' AVP                                                         | 6.0.0 |
+| Jun 2004  | CN#24 | NP-040216 | 037  | -   | Correction to description of Data Reference AVP value 10                                   | 6.1.0 |
+| Jun 2004  | CN#24 | NP-040216 | 035  | 1   | Correction of reference for definition of MSISDN                                           | 6.1.0 |
+| Sep 2004  | CN#25 | NP-040394 | 043  | -   | Incorrect Data-Reference AVP in Subscriber Notification Answer Command                     | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040395 | 046  | 1   | Application version control                                                                | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040394 | 041  | 1   | Public-Identity is unspecified for the Sh interface                                        | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040395 | 045  | 1   | Single Public Identity required in Grouped User-Identity AVP                               | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040394 | 049  | -   | Correction of the Application-Id code                                                      | 6.2.0 |
+| Sep 2004  | CN#25 | NP-040412 | 051  | 1   | Re-numbering of 3GPP specific AVP codes                                                    | 6.2.0 |
+| Dec 2004  | CN#26 | NP-040578 | 053  | -   | Sh ABNF corrections                                                                        | 6.3.0 |
+| Mar 2005  | CN#27 | NP-050031 | 057  | 1   | Introduction of Failed AVP                                                                 | 6.4.0 |
+| Mar 2005  | CN#27 | NP-050031 | 064  | -   | Sh-Update needs to include Data-Reference to be future proof                               | 6.4.0 |
+| Jun 2005  | CT#28 | CP-050216 | 069  | -   | Sh UDR correction                                                                          | 6.5.0 |
+| Jun 2005  | CT#28 | CP-050087 | 070  | -   | Correction of references                                                                   | 6.5.0 |
+| Jun 2005  | CT#28 | CP-050087 | 071  | 1   | Corrections to message parameters                                                          | 6.5.0 |
+| Jun 2005  | CT#28 | CP-050087 | 072  | 1   | Miscellaneous Corrections                                                                  | 6.5.0 |
+| Jun 2005  | CT#28 | CP-050216 | 074  | -   | Correction to allow realm based routing                                                    | 6.5.0 |
+| Sep 2005  | CT#29 | CP-050424 | 075  | -   | Identity-Set correction                                                                    | 6.6.0 |
+| Sep 2005  | CT#29 | CP-050422 | 095  | 1   | State the condition for encryption of the Data Reference                                   | 6.6.0 |
+| Sep 2005  | CT#29 | CP-050423 | 097  | 1   | Early IMS Security based protection for the Ut interface                                   | 6.6.0 |
+| Dec 2005  | CT#30 | CP-050625 | 098  | 3   | Notification & Query Efficiency                                                            | 7.0.0 |
+| Dec 2005  | CT#30 | CP-050625 | 099  | 1   | Management of subscriptions                                                                | 7.0.0 |
+| Mar 2006  | CT#31 | CP-060084 | 0100 | 1   | User-Data in the response to Sh-Subs-Notif                                                 | 7.1.0 |
+| Mar 2006  | CT#31 | CP-060084 | 0101 | 3   | New error indications for the Sh-Subs-Notif procedure                                      | 7.1.0 |
+| Jun 2006  | CT#32 | CP-060319 | 0105 | 2   | Sh interface efficiency improvement                                                        | 7.2.0 |
+| Sep 2006  | CT#33 | CP-060417 | 0107 | 2   | Introduction of Activation State Information for IMS (DSAI)                                | 7.3.0 |
+| Sep 2006  | CT#33 | CP-060417 | 0108 | -   | Addition of AVPs in SNR and SNA                                                            | 7.3.0 |
+| Sep 2006  | CT#33 | CP-060417 | 0110 | 1   | Public User Identity Grouping Information                                                  | 7.3.0 |
+| Sep 2006  | CT#33 | CP-060405 | 0112 | -   | Missing Data Reference value                                                               | 7.3.0 |
+| Sep 2006  | CT#33 | CP-060417 | 0113 | 1   | Errors to be sent in response to Sh-Notif                                                  | 7.3.0 |
+| Sep 2007  | CT#37 | CP-070527 | 0118 | -   | Define User-Data AVP                                                                       | 7.4.0 |
+| Sep 2007  | CT#37 | CP-070527 | 0119 | 1   | Wildcarded PSI as key in the Sh Interface                                                  | 7.4.0 |
+| Nov 2007  | CT#38 | CP-070743 | 0120 | -   | ABNF correction for UDR and SNR                                                            | 7.5.0 |
+| Nov 2007  | CT#38 | CP-070743 | 0121 | 1   | PNR for Subscriptions to Notifications for all Identity Sets                               | 7.5.0 |
+| Mar 2008  | CT#39 | CP-080019 | 0122 | -   | Wildcarded Public User Identities                                                          | 8.0.0 |
+| Jun 2008  | CT#40 | CP-080267 | 0123 | 1   | DSAI Corrections                                                                           | 8.1.0 |
+| Jun 2008  | CT#40 | CP-080702 | 0130 | 1   | Service Indication for standardized services                                               | 8.2.0 |
+| Jun 2008  | CT#40 | CP-080883 | 0132 | 1   | Correction of Identity-Set AVP                                                             | 8.2.0 |
+| Mar 2009  | CT#43 | CP-090042 | 0134 | 1   | AliasesRepositoryData removal                                                              | 8.3.0 |
+| Jun 2009  | CT#44 | CP-090305 | 0136 | -   | Missing data-reference for GIBA                                                            | 8.4.0 |
+| Dec 2009  | CT#46 | CP-090778 | 0138 | -   | Session-Priority AVP                                                                       | 8.5.0 |
+| Dec 2009  | CT#46 |           |      |     | Upgraded unchanged from Rel-8                                                              | 9.0.0 |
+| Mar 2010  | CT#47 | CP-100033 | 0143 | 1   | IP-SM-GW UE reachability handling over Sh                                                  | 9.1.0 |
+| Mar 2010  | CT#47 | CP-100048 | 0144 | 1   | Sh handling of T-ADS                                                                       | 9.1.0 |
+| Mar 2010  | CT#47 | CP-100206 | 0148 | 3   | EPS Subscriber State and Location Information Request                                      | 9.1.0 |
+| Jun 2010  | CT#48 | CP-100275 | 0149 | -   | EPS state and location retrieval                                                           | 9.2.0 |
+
+|          |        |           |      |   |                                                                       |        |
+|----------|--------|-----------|------|---|-----------------------------------------------------------------------|--------|
+| Jun 2010 | CT#48  | CP-100279 | 0154 | 1 |                                                                       | 9.2.0  |
+| Sep 2010 | CT#49  | CP-100447 | 0157 | 1 | Correction to the Value of Data-Reference AVP                         | 9.3.0  |
+| Sep 2010 | CT#49  | CP-100454 | 0160 | 1 | Correction on Requested-Domain                                        | 9.3.0  |
+| Sep 2010 | CT#49  | CP-100466 | 0158 | 2 | Usage of IMSI and IMPI for user identification over Sh                | 10.0.0 |
+| Sep 2010 | CT#49  | CP-100466 | 0159 | 3 | Location data including only serving node address                     | 10.0.0 |
+| Sep 2010 | CT#49  | CP-100466 | 0163 | 3 | Update-Eff feature                                                    | 10.0.0 |
+| Dec 2010 | CT#50  | CP-100699 | 0164 | 2 | Enhanced SRVCC                                                        | 10.1.0 |
+| Mar 2011 | CT#51  | CP-110257 | 0168 | 2 | MPS over Sh                                                           | 10.2.0 |
+| Mar 2011 | CT#51  | CP-110075 | 0170 | 2 | Retrieval of CSRN from HSS                                            | 10.2.0 |
+| Jun 2011 | CT#52  | CP-110370 | 0175 | 1 | Pre-paging Support Indicator for CSRN                                 | 10.3.0 |
+| Jun 2011 | CT#52  | CP-110370 | 0176 | 1 | Clarification on Notif-Eff description for SNR/SNA                    | 10.3.0 |
+| Jun 2011 | CT#52  | CP-110370 | 0177 | - | Missing Repository-Data-ID AVP in PUA                                 | 10.3.0 |
+| Jun 2011 | CT#52  | CP-110383 | 0173 | 2 | Reference Location over Sh interface                                  | 11.0.0 |
+| Dec 2011 | CT#54  | CP-110781 | 0189 | - | Correction on Wildcarded Public Identity                              | 11.1.0 |
+| Mar 2012 | CT#55  | CP-120035 | 0194 | 2 | Update of Multiple Data Instances in Sh-Update                        | 11.2.0 |
+| Jun 2012 | CT#56  | CP-120240 | 0195 | 3 | Local Time for NPLI                                                   | 11.3.0 |
+| Sep 2012 | CT#57  | CP-120481 | 0197 |   | A-MSISDN handling over Sh                                             | 11.4.0 |
+| Sep 2012 | CT#57  | CP-120481 | 0198 | 1 | Local Time Zone                                                       | 11.4.0 |
+| Dec 2012 | CT#58  | CP-120743 | 0202 | 1 | EPS LocationInformation Support                                       | 11.5.0 |
+| Mar 2013 | CT#59  | CP-130020 | 0208 | 1 | PS Location Info request with RAT-type                                | 11.6.0 |
+| Mar 2013 | CT#59  | CP-130020 | 0210 | 1 | Pre-paging-Supported and Local-Time-Zone-Indication AVPs              | 11.6.0 |
+| Mar 2013 | CT#59  | CP-130031 | 0200 | 1 | Sh IMSI retrieval                                                     | 12.0.0 |
+| Jun 2013 | CT#60  | CP-130374 | 0211 | 1 | MTRR on Sh                                                            | 12.1.0 |
+| Mar 2014 | CT#63  | CP-140027 | 0214 | 1 | Multiple notification due to the Update-Eff feature                   | 12.2.0 |
+| Jun 2014 | CT#64  | CP-140262 | 0217 | - | Private User Identity retrieval                                       | 12.3.0 |
+| Jun 2014 | CT#64  | CP-140262 | 0218 | - | UE Reachability for IP                                                | 12.3.0 |
+| Sep 2014 | CT#65  | CP-140515 | 0219 | - | Session-Priority reference                                            | 12.4.0 |
+| Sep 2014 | CT#65  | CP-140509 | 0220 | 1 | Diameter Overload Control Over Sh                                     | 12.4.0 |
+| Dec 2014 | CT#66  | CP-140773 | 0222 | - | M-bit clarification                                                   | 12.5.0 |
+| Dec 2014 | CT#66  | CP-140779 | 0223 | - | Retrieval of TWAN-Id over Sh                                          | 12.5.0 |
+| Dec 2014 | CT#66  | CP-140790 | 0224 | - | DOIC reference update                                                 | 12.5.0 |
+| Dec 2015 | CT#70  | CP-150759 | 0226 | 1 | Update reference to DOIC new IETF RFC                                 | 12.6.0 |
+| Dec 2015 | CT#70  | CP-150849 | 0227 | 4 | Support of the DRMP AVP over Sh/Dh                                    | 13.0.0 |
+| 2016-09  | CT#73  | CP-160431 | 0228 | 1 | Request to update data while a previous update request is in progress | 14.0.0 |
+| 2016-12  | CT#74  | CP-160649 | 0236 | 1 | RAT type included in EPS location information                         | 14.1.0 |
+| 2016-12  | CT#74  | CP-160681 | 0237 | 1 | Load Control                                                          | 14.1.0 |
+| 2016-12  | CT#74  | CP-160664 | 0239 | 1 | Correction to change IETF drmp draft version to official RFC 7944     | 14.1.0 |
+| 2017-03  | CT#75  | CP-170035 | 0241 | - | Notif-Eff feature description correction                              | 14.2.0 |
+| 2017-03  | CT#75  | CP-170035 | 0245 | 1 | UDR flag description                                                  | 14.2.0 |
+| 2017-03  | CT#75  | CP-170048 | 0243 | 1 | Update of reference for the Diameter base protocol                    | 14.2.0 |
+| 2017-03  | CT#75  | CP-170048 | 0244 | - | Cardinality of the Failed-AVP AVP in answer                           | 14.2.0 |
+| 2017-06  | CT#76  | CP-171018 | 0248 | 1 | Support for signaling transport level packet marking                  | 14.3.0 |
+| 2017-06  | CT#76  | CP-171040 | 0246 | 1 | External Identifier on Sh                                             | 15.0.0 |
+| 2018-06  | CT#80  | CP-181131 | 0249 | - | Requested Node AMF                                                    | 15.1.0 |
+| 2019-09  | CT#85  | CP-192094 | 0251 | 2 | draft-ietf-dime-load published as RFC 8583                            | 15.2.0 |
+| 2020-07  | CT#88e | -         | -    | - | Update to Rel-16 version (MCC)                                        | 16.0.0 |
+| 2020-12  | CT#91e | CP-203022 | 0253 | 1 | Incomplete implemented CR                                             | 16.1.0 |
+| 2021-03  | CT#91e | CP-210044 | 0354 | - | IMEISV and 5G SRVCC Capability missing in Data Reference AVP          | 16.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29343/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/29_series/29343/00504fc688ebcf131ccbeff94dfc9939_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc266c22fd8a02a3ab2a5f178dbdc47ec75a7b1c
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/00504fc688ebcf131ccbeff94dfc9939_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b895e70ecfc7c35588602826151b23b26ebee8497fc4b6629125198df88986d2
+size 29682
diff --git a/marked/Rel-16/29_series/29343/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/29_series/29343/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b456558b5598826c73c932fcc0b6cf1cd9974a0
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:91c6e6e2add67ec86c98d625764a926968204eae0b1b23bdd431d3b61030f973
+size 28977
diff --git a/marked/Rel-16/29_series/29343/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-16/29_series/29343/20136850feb70fd71c7d41cdae203ebb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87b87f6b5a153be8320874f7c8c07d7d3ef09f73
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/20136850feb70fd71c7d41cdae203ebb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93206669a9a8087efe4c36a065b76eec6f7754ad4c93ad89538055f48c5421d0
+size 35400
diff --git a/marked/Rel-16/29_series/29343/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/29_series/29343/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..27e6bfdb7a1473e0e6503c03bb1b901c0898c75d
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af86eeea7164535db2f671a3ce85b8ed617c12a66d519f42998ed59e01dc07df
+size 28131
diff --git a/marked/Rel-16/29_series/29343/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/29_series/29343/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8b5af68e1c05bf4ab0d18adcee701e014ef1cf4
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09ac4c225ba33e6c79b7823020c4cbbc31bfee6553aaa8c9e923eedb3ad9dbd8
+size 34029
diff --git a/marked/Rel-16/29_series/29343/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/29_series/29343/4af57aad638888edf2062306f8a54a6c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..367b1c82b6c63e1053b53cf3d565b9b9deef04af
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/4af57aad638888edf2062306f8a54a6c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:207e35d7c799d15e966c4c9a1e83c9aff59341cd08b514fcf5d9fc38dc46f137
+size 31426
diff --git a/marked/Rel-16/29_series/29343/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-16/29_series/29343/55136bc716146672fc680fa05989f1d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49b17e642b1fbc4d1923114f6c8d970626980b47
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/55136bc716146672fc680fa05989f1d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17f48474d717acaa8c09b2ee4c7a4b52a610ff9dde2a8c339a20221cdae24b2f
+size 32277
diff --git a/marked/Rel-16/29_series/29343/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/29_series/29343/6e15fc9ea763541c5913d26f85072ae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff8780312879b503e67f1485d94339c81450e179
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/6e15fc9ea763541c5913d26f85072ae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a129368ae4ccc1be1691c476616e4f63f03bbf25c5b6704f95c4f7d18fc529e9
+size 28360
diff --git a/marked/Rel-16/29_series/29343/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/29_series/29343/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d18f78d5927d8fb00eef43976273f68353195d03
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16e9a1da7ad8aee2a05ad8a6652062461be4c02353c199bcc069cfff70169824
+size 24552
diff --git a/marked/Rel-16/29_series/29343/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-16/29_series/29343/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c5b759b4954b5eabbb1fbc380742ab02afd66a6
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:78ddf87e6f7cd84255679eab0b383d2928832d3dd6de4714c4ee2333402fc8f3
+size 31756
diff --git a/marked/Rel-16/29_series/29343/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-16/29_series/29343/a1890b9a9b85f13e67ed59bbad623659_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..466f7c5e10b8209ea62fab9f0b0738b801f51a56
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/a1890b9a9b85f13e67ed59bbad623659_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7b5dac31ad33f2c1c544850e61d50d1721e54cdc4c6d6c49c2367dc82a6a225
+size 32467
diff --git a/marked/Rel-16/29_series/29343/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/29_series/29343/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff7eeb49784508c59a5aa7d2078dcf41d6c3a709
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4b38f15af8734344ac35e830f4554ddeed7202d2bc731ec0ad629fa6497b3da
+size 21155
diff --git a/marked/Rel-16/29_series/29343/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/29_series/29343/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f785b7dcbc8b255cd584fa6d726a32fcd1f35c64
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c17faeb830c942d7af0e287f971b0ed55d09fcc417322752f882bd4db7a68251
+size 30935
diff --git a/marked/Rel-16/29_series/29343/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-16/29_series/29343/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39e24d6b6e0952274ee78d9690898f21e3922513
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0cb3b2af36774654cbd5948f8170bb472d2981650a978b944bf2c81832a3a621
+size 30092
diff --git a/marked/Rel-16/29_series/29343/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/29_series/29343/dd5771673aececa53d42ece89218299d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..057bc1ef8bb6b4c2171da9d6a9d4e6c29408596b
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/dd5771673aececa53d42ece89218299d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f7b362bcc64cbe83aea818a4bf821a2252475c2fce0774ea75f99bc2370f773
+size 30092
diff --git a/marked/Rel-16/29_series/29343/raw.md b/marked/Rel-16/29_series/29343/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..46f0c7f3883273374cf67338ada6506d7ad21f0b
--- /dev/null
+++ b/marked/Rel-16/29_series/29343/raw.md
@@ -0,0 +1,1463 @@
+
+
+
+
+Error! No  
+text of
+
+Error! No text of specified style in  
+document.
+
+# Contents
+
+|                                                                                                |    |
+|------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                 | 6  |
+| 1 Scope.....                                                                                   | 7  |
+| 2 References.....                                                                              | 7  |
+| 3 Definitions and abbreviations .....                                                          | 7  |
+| 3.1 Definitions.....                                                                           | 7  |
+| 3.2 Abbreviations .....                                                                        | 8  |
+| 4 PC2 reference point.....                                                                     | 8  |
+| 4.1 PC2 reference model.....                                                                   | 8  |
+| 4.2 Functional elements.....                                                                   | 9  |
+| 4.2.1 ProSe Function .....                                                                     | 9  |
+| 4.2.2 ProSe Application Server .....                                                           | 9  |
+| 5 PC2 procedures .....                                                                         | 10 |
+| 5.1 EPC-level ProSe discovery .....                                                            | 10 |
+| 5.1.1 Application registration for ProSe .....                                                 | 10 |
+| 5.1.1.1 General Description .....                                                              | 10 |
+| 5.1.1.2 Detailed description of the application registration for ProSe procedure.....          | 10 |
+| 5.1.2 Proximity map request.....                                                               | 10 |
+| 5.1.2.1 General.....                                                                           | 10 |
+| 5.1.2.2 Detailed description of the proximity map request procedure.....                       | 10 |
+| 5.2 Restricted ProSe direct discovery .....                                                    | 11 |
+| 5.2.1 Overview .....                                                                           | 11 |
+| 5.2.2 Authorization for Announce Request (model A) .....                                       | 11 |
+| 5.2.2.1 General Description .....                                                              | 11 |
+| 5.2.2.2 Detailed description of the procedure.....                                             | 11 |
+| 5.2.3 Authorization for Announce Request with Application-controlled extension (model A) ..... | 11 |
+| 5.2.3.1 General Description .....                                                              | 11 |
+| 5.2.3.2 Detailed description of the procedure.....                                             | 12 |
+| 5.2.4 Authorization for Monitor Request (model A).....                                         | 12 |
+| 5.2.4.1 General Description .....                                                              | 12 |
+| 5.2.4.2 Detailed description of the procedure.....                                             | 12 |
+| 5.2.5 Authorization for Monitor Request with Application-controlled Extension (model A) .....  | 13 |
+| 5.2.5.1 General Description .....                                                              | 13 |
+| 5.2.5.2 Detailed description of the procedure.....                                             | 13 |
+| 5.2.6 Authorization for Discovery Permission (model A) .....                                   | 13 |
+| 5.2.6.1 General.....                                                                           | 13 |
+| 5.2.6.2 Detailed description of the procedure.....                                             | 14 |
+| 5.2.7 Authorization for Match Report (model A/model B).....                                    | 14 |
+| 5.2.7.1 General Description .....                                                              | 14 |
+| 5.2.7.2 Detailed description of the procedure.....                                             | 14 |
+| 5.2.8 Authorization for Discoveree Request (model B).....                                      | 15 |
+| 5.2.8.1 General Description .....                                                              | 15 |
+| 5.2.8.2 Detailed description of the procedure.....                                             | 15 |
+| 5.2.9 Authorization for Discoverer Request (model B).....                                      | 15 |
+| 5.2.9.1 General Description .....                                                              | 15 |
+| 5.2.9.2 Detailed description of the procedure.....                                             | 15 |
+| 5.2.10 Authorization for Discovery Permission (model B).....                                   | 15 |
+| 5.2.10.1 General Description .....                                                             | 15 |
+| 5.2.10.2 Detailed description of the procedure.....                                            | 15 |
+| 5.2.11 Discovery Authorization Update.....                                                     | 15 |
+| 5.2.11.1 General Description .....                                                             | 15 |
+| 5.2.11.2 Detailed description of the discovery authorization update procedure.....             | 15 |
+| 5.3 Open ProSe direct discovery .....                                                          | 16 |
+| 5.3.1 Authorization for Announce Request with Application-controlled extension.....            | 16 |
+| 5.3.1.1 General Description .....                                                              | 16 |
+| 5.3.1.2 Detailed description of the procedure.....                                             | 16 |
+
+|          |                                                                              |    |
+|----------|------------------------------------------------------------------------------|----|
+| 5.3.2    | Authorization for Monitor Request with Application-controlled Extension..... | 17 |
+| 5.3.2.1  | General Description .....                                                    | 17 |
+| 5.3.2.2  | Detailed description of the procedure.....                                   | 17 |
+| 6        | PC2 protocol .....                                                           | 17 |
+| 6.1      | Protocol Support.....                                                        | 17 |
+| 6.1.1    | Use of Diameter base protocol .....                                          | 17 |
+| 6.1.2    | Transport protocol .....                                                     | 18 |
+| 6.1.3    | Advertising Application Support.....                                         | 18 |
+| 6.2      | Initialization and maintenance of connection and session .....               | 18 |
+| 6.3      | Security over PC2 reference point .....                                      | 18 |
+| 6.4      | PC2 specific AVPs.....                                                       | 18 |
+| 6.4.1    | General .....                                                                | 18 |
+| 6.4.2    | Origin-App-Layer-User-Id AVP .....                                           | 19 |
+| 6.4.3    | Target-App-Layer-User-Id AVP .....                                           | 19 |
+| 6.4.4    | ProSe-Function-ID AVP .....                                                  | 19 |
+| 6.4.5    | ProSe-Request-Type AVP.....                                                  | 19 |
+| 6.4.6    | PDUID AVP.....                                                               | 20 |
+| 6.4.7    | Application-Data AVP .....                                                   | 20 |
+| 6.4.8    | Allowed-Suffixes-Number AVP .....                                            | 21 |
+| 6.4.9    | Monitor-Target AVP .....                                                     | 21 |
+| 6.4.10   | ProSe- Code-Suffix-Mask AVP .....                                            | 21 |
+| 6.4.11   | Suffix-Code AVP .....                                                        | 21 |
+| 6.4.12   | Suffix-Mask AVP .....                                                        | 21 |
+| 6.4.13   | Void .....                                                                   | 21 |
+| 6.4.14   | Void .....                                                                   | 21 |
+| 6.4.15   | Void .....                                                                   | 21 |
+| 6.4.16   | Void .....                                                                   | 21 |
+| 6.4.17   | Banned-User-Target AVP .....                                                 | 21 |
+| 6.4.18   | Metadata-Indicator AVP .....                                                 | 22 |
+| 6.5      | PC2 re-used AVPs.....                                                        | 22 |
+| 6.6      | PC2 messages.....                                                            | 23 |
+| 6.6.1    | Command-Code Values.....                                                     | 23 |
+| 6.6.2    | ProXimity-Action-Request (PXR) command.....                                  | 23 |
+| 6.6.3    | ProXimity-Action-Answer (PXA) command.....                                   | 24 |
+| 6.6.4    | ProXimity-Application-Request (XAR) command.....                             | 24 |
+| 6.6.5    | ProXimity-Application-Answer (XAA) command .....                             | 25 |
+| 6.7      | PC2 specific Experimental-Result-Code AVP values .....                       | 25 |
+| 6.7.1    | General .....                                                                | 25 |
+| 6.7.2    | Success .....                                                                | 25 |
+| 6.7.3    | Failures .....                                                               | 25 |
+| 6.7.3.1  | DIAMETER_ERROR_ORIGIN_ALUID_UNKNOWN (5590) .....                             | 25 |
+| 6.7.3.2  | DIAMETER_ERROR_TARGET_ALUID_UNKNOWN (5591) .....                             | 26 |
+| 6.7.3.3  | DIAMETER_ERROR_PPID_UNKNOWN (5592).....                                      | 26 |
+| 6.7.3.4  | DIAMETER_ERROR_APP_REGISTER_REJECT (5593) .....                              | 26 |
+| 6.7.3.5  | DIAMETER_ERROR_PROSE_MAP_REQUEST_DISALLOWED (5594) .....                     | 26 |
+| 6.7.3.6  | DIAMETER_ERROR_MAP_REQUEST_REJECT (5595).....                                | 26 |
+| 6.7.3.7  | DIAMETER_ERROR_REQUESTING_RPAUID_UNKNOWN (5596).....                         | 26 |
+| 6.7.3.8  | DIAMETER_ERROR_UNKNOWN_OR_INVALID_TARGET_SET (5597).....                     | 26 |
+| 6.7.3.9  | DIAMETER_ERROR_MISSING_APPLICATION_DATA (5598).....                          | 26 |
+| 6.7.3.10 | DIAMETER_ERROR_AUTHORIZATION_REJECT (5599).....                              | 26 |
+| 6.7.3.11 | DIAMETER_ERROR_DISCOVERY_NOT_PERMITTED (5600) .....                          | 26 |
+| 6.7.3.12 | DIAMETER_ERROR_TARGET_RPAUID_UNKNOWN (5601).....                             | 26 |
+| 6.7.3.13 | DIAMETER_ERROR_INVALID_APPLICATION_DATA (5602).....                          | 26 |
+
+# **Annex A (informative): Call Flows over PC2..... 27**
+
+|       |                                                    |    |
+|-------|----------------------------------------------------|----|
+| A.1   | EPC-Level ProSe discovery.....                     | 27 |
+| A.1.1 | Application registration for ProSe.....            | 27 |
+| A.1.2 | Proximity map request .....                        | 28 |
+| A.2   | Restricted ProSe direct discovery .....            | 28 |
+| A.2.1 | Authorization for Announce Request (model A) ..... | 28 |
+
+A.2.2 Authorization for Restricted Discovery Announce Request with Application-controlled extension (model A) ..... 29
+
+A.2.3 Authorization for Monitor Request (model A) ..... 30
+
+A.2.4 Authorization for Restricted Discovery Monitor Request with Application-controlled extension (model A)..... 30
+
+A.2.5 Authorization for Discovery Permission (model A) ..... 31
+
+A.2.6 Authorization for Match Report (model A/model B)..... 32
+
+A.2.7 Authorization for Discoveree Request (model B)..... 33
+
+A.2.8 Authorization for Discoverer Request (model B) ..... 33
+
+A.2.9 Authorization for Discovery Permission (model B) ..... 34
+
+A.2.10 Discovery Authorization Update..... 35
+
+A.2.11 Authorization for Open Discovery Announce Request with Application-controlled extension..... 35
+
+A.2.12 Authorization for Open Discovery Monitor Request with Application-controlled extension..... 36
+
+B.1 General ..... 37
+
+B.2 ProSe Function behaviour ..... 37
+
+B.3 ProSe Application Server behaviour ..... 38
+
+Annex C (informative): Change history..... 39
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+This document provides the stage 3 specification of the PC2 reference point. The functional requirements and the stage 2 procedures of the PC2 reference point are contained in 3GPP TS 23.303 [2]. The PC2 reference point lies between the ProSe Function and ProSe Application Server.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".
+- [3] Void.
+- [4] IETF RFC 791: "Transmission Control Protocol".
+- [5] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [6] 3GPP TS 33.303: "Proximity-based Services (ProSe); Security aspects".
+- [7] 3GPP TS 29.345: "Inter-Proximity-services (ProSe) Function signalling aspects; Stage 3".
+- [8] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
+- [9] IETF RFC 2234: "Augmented BNF for syntax specifications".
+- [10] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
+- [11] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [12] IETF RFC 6733: "Diameter Base Protocol".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. The term definition in the present document has a reference to that in 3GPP TS 23.303 [2].
+
+**Announcing UE:** The UE that announces certain information that could be monitored by UEs in proximity that have permission to discover.
+
+**Discoveree UE:** The UE that receives the request message and responds with certain information related to the discoverer UE's request.
+
+**Discoverer UE:** The UE that transmits a request containing certain information about what it is interested to discover.
+
+**Monitoring UE:** The UE that monitors certain information of interest in proximity of announcing UEs.
+
+**EPC-level ProSe Discovery:** A ProSe Discovery procedure by which the EPC determines the proximity of two ProSe-enabled UEs and informs them of their proximity.
+
+**Model A:** involves one UE announcing "I am here" in restricted ProSe direct discovery.
+
+**Model B:** involves one UE asking "who is there" and/or "are you there" in restricted ProSe direct discovery.
+
+**ProSe Discovery:** A process that identifies that a UE that is ProSe-enabled is in proximity of another, using E-UTRA (with or without E-UTRAN) or EPC.
+
+**ProSe Discovery UE ID:** A temporary identifier assigned by the ProSe Function in the HPLMN to the UE for the restricted direct discovery service. It includes the PLMN ID and a temporary identifier that uniquely identifies the UE in the HPLMN.
+
+**ProSe Function ID:** An FQDN that identifies a ProSe Function.
+
+**Restricted ProSe Application User ID:** An identifier associated with the Application Layer User ID in the ProSe Application Server in order to hide/protect the application level user identity from the 3GPP layer. It unambiguously identifies the user within a given application. The format of this identifier is outside the scope of 3GPP.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                      |
+|--------|--------------------------------------|
+| ACE    | Application-Controlled Extension     |
+| ALUID  | Application Layer User ID            |
+| AVP    | Attribute-Value Pair                 |
+| EPUID  | EPC ProSe User ID                    |
+| PDUID  | ProSe Discovery UE ID                |
+| PFID   | ProSe Function ID                    |
+| ProSe  | Proximity-based Services             |
+| RPAUID | Restricted ProSe Application User ID |
+
+# --- 4 PC2 reference point
+
+## 4.1 PC2 reference model
+
+Proximity Services (ProSe) are services that can be provided by the 3GPP system based on UEs being in proximity to each other. The PC2 reference point is located between the ProSe Application Server and the ProSe Function. It is used to define the interaction between ProSe Application Server and ProSe functionality provided by the 3GPP EPS via ProSe Function (e.g. name translation) for open ProSe direct discovery, restricted ProSe direct discovery and EPC-level ProSe discovery.
+
+The stage 2 level requirements for the PC2 reference point are defined in 3GPP TS 23.303 [2]. The relationships between the functional entities are depicted in Figure 4.1.1.
+
+NOTE: For EPC-level ProSe discovery the roaming architecture is not specified in this release.
+
+![Diagram of ProSe Architecture showing the PC2 reference point. A UE A with a ProSe application connects to a ProSe Function via PC3. The ProSe Function connects to a ProSe Application Server via PC2. The ProSe Application Server connects to an HSS via PC4a and to an SLP via PC4b. A line labeled PC1 connects the UE A directly to the ProSe Application Server.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+
+graph LR
+    UE_A[UE A] -- PC3 --> PF[ProSe Function]
+    PF -- PC2 --> PAS[ProSe Application Server]
+    PAS -- PC4a --> HSS[HSS]
+    PAS -- PC4b --> SLP[SLP]
+    UE_A -- PC1 --> PAS
+  
+```
+
+Diagram of ProSe Architecture showing the PC2 reference point. A UE A with a ProSe application connects to a ProSe Function via PC3. The ProSe Function connects to a ProSe Application Server via PC2. The ProSe Application Server connects to an HSS via PC4a and to an SLP via PC4b. A line labeled PC1 connects the UE A directly to the ProSe Application Server.
+
+Figure 4.1.1: PC2 reference point in ProSe Architecture
+
+## 4.2 Functional elements
+
+### 4.2.1 ProSe Function
+
+The ProSe Function is the logical function that is used for network related actions required for ProSe. The ProSe Function plays different roles for each of the features of ProSe. In this version of the specification it is assumed that there is only one logical ProSe Function in each PLMN that supports Proximity Services.
+
+Over PC2 reference point, the ProSe Function supports EPC-level discovery by the following functionality:
+
+- Storage of a list of applications that are authorized to use EPC-level ProSe Discovery.
+- Handling of EPC ProSe User IDs and Application Layer User IDs;
+- Exchange of signalling with 3<sup>rd</sup> party Application Servers for application registration and identifier mapping;
+
+The ProSe Function also supports open ProSe direct discovery and restricted ProSe direct discovery by the following functionality:
+
+- Generates and maintains the ProSe Discovery UE ID (PDUID) for restricted ProSe direct discovery.
+- Initiates authorization of the discovery requests over PC2 reference point.
+
+The ProSe Function provides the necessary charging and security functionality for usage of ProSe via the EPC.
+
+### 4.2.2 ProSe Application Server
+
+The ProSe Application Server supports the following functionality:
+
+- Storage of EPC ProSe User IDs, ProSe Function IDs, ProSe Discovery UE ID, metadata and RPAUIDs;
+- Mapping of Application Layer User IDs and EPC ProSe User IDs.
+- Mapping of RPAUID and PDUID for restricted ProSe direct discovery.
+- Maintaining permission information for the restricted ProSe direct discovery using RPAUIDs;
+- Allocation of the ProSe Restricted Code Suffix pool, if restricted direct discovery with application-controlled extension is used;
+- Allocation of the mask(s) for ProSe Restricted Code Suffix, if restricted direct discovery with application-controlled extension is used;
+- Allocation of the mask(s) for ProSe Application Code Suffix, if open direct discovery with application-controlled extension is used.
+
+# 5 PC2 procedures
+
+## 5.1 EPC-level ProSe discovery
+
+### 5.1.1 Application registration for ProSe
+
+#### 5.1.1.1 General Description
+
+The application registration procedure is used by a ProSe Function serving the originating UE to request the ProSe Application Server to register the UE's Application Layer User ID (ALUID) with an EPC ProSe User ID (EPUID).
+
+This procedure uses the Diameter commands ProXimity-Action-Request (PXR) and ProXimity-Action-Answer (PXA) in the Diameter application as specified in clause 6.
+
+#### 5.1.1.2 Detailed description of the application registration for ProSe procedure
+
+The ProSe Function of the UE triggering the ProSe EPC-level discovery application registration procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific application requested by the UE in its initial Application Registration message. The ProSe Function shall include in the request the ProSe-Request-Type AVP with the value APPLICATION\_REGISTRATION\_FOR\_PROSE (0), the Requesting-EPUID AVP with the EPC ProSe User ID of the originating UE, the Origin-App-Layer-User-Id AVP with the Application Layer User Identity of the originating UE, and the ProSe-Function-ID AVP with the ProSe Function Identity of the originating UE.
+
+When receiving a PXR command for application registration from a ProSe Function, the ProSe Application Server shall process the request and respond to the ProSe Function with a PXA command.
+
+If the ProSe Application Server accepts the PXR command, it acknowledges the reception of the PXR command for ProSe application registration and sets the Result-Code AVP to "SUCCESS" in the PXA command. When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function notifies the originating UE, according to the ProSe EPC-level discovery application registration procedure as specified in clause 7.2.3 of 3GPP TS 24.334 [10]. In case of an unsuccessful application registration request, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+### 5.1.2 Proximity map request
+
+#### 5.1.2.1 General
+
+The Proximity map request procedure may be used by the ProSe Function to request the EPC ProSe User identity for a targeted application user for which the originating UE shall get alerts when in proximity of the targeted UE, and the identity of the ProSe Function for this targeted UE as well. The identity of the ProSe Function is used in the execution of the Proximity Request procedure described in 3GPP TS 29.345 [7].
+
+#### 5.1.2.2 Detailed description of the proximity map request procedure
+
+To apply this procedure, the ProSe Function shall send a ProXimity-Action-Request (PXR) command including the ProSe-Request-Type AVP with the value PROSE\_MAP\_REQUEST (1), the Origin-App-Layer-User-ID AVP indicating the application layer user identity of the originating UE and the Target-App-Layer-User-ID AVP indicating the application layer user identity of the targeted UE.
+
+Upon reception of a PXR command including the Origin-App-Layer-User-ID AVP and the Target-App-Layer-User-ID AVP, the ProSe Application Server shall determine whether the originating UE is allowed to discover the targeted UE.
+
+The ProSe Application Server shall then send a ProXimity-Action-Answer (PXA) command including the Targeted-EPUID AVP and ProSe-Function-ID AVP indicating the targeted UE and the corresponding ProSe Function ID respectively.
+
+In case of an unsuccessful proximity map request, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+## 5.2 Restricted ProSe direct discovery
+
+### 5.2.1 Overview
+
+Restricted ProSe direct discovery is a process that a UE detects and identifies another UE in proximity using E-UTRA direct radio signals with explicit permission of the UE that is being discovered. Detailed description of ProSe direct discovery refers to 3GPP TS 23.303 [2] clause 5.3. There are two models that restricted ProSe direct discovery applies:
+
+Model A ("I am here")
+
+Two roles of ProSe-enabled UEs are involved in this model: Announcing UE and Monitoring UE. The announcing UE broadcasts discovery messages at pre-defined discovery intervals and the monitoring UEs that are interested in these messages read them and process them.
+
+Model B ("who is there?" / "are you there?")
+
+Two roles of ProSe-enabled UEs are involved in this model: Discoverer UE and Discoveree UE. It is equivalent to "who is there/are you there" since the discoverer UE sends information about other UEs that would like to receive responses from, e.g. the information can be about a ProSe Application Identity corresponding to a group and the members of the group can respond.
+
+### 5.2.2 Authorization for Announce Request (model A)
+
+#### 5.2.2.1 General Description
+
+The announce authorization procedure (model A) is used by the ProSe Function serving the originating UE to obtain announce authorization information related to restricted ProSe direct discovery. The procedure is invoked by the ProSe Function and is used for the following purposes:
+
+- to request the ProSe Application Server to map the UE's Restricted ProSe Application User ID (RPAUID) to the corresponding ProSe Discovery UE ID(s) (PDUID(s)) .
+
+#### 5.2.2.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function of the UE triggering the restricted ProSe direct discovery announce request procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific application requested by the UE in its initial request message. The ProSe Function shall include in the request the ProSe-Request-Type AVP with the value AUTHORIZATION\_ANNOUNCE (2) and the Requesting-RPAUID AVP with the RPAUID assigned for this application to the originating UE.
+
+When receiving a PXR command for announce authorization for restricted ProSe direct discovery, the ProSe Application Server shall acknowledge the reception of the PXR command and shall send a PXA command with the Result-Code AVP set to "SUCCESS", with one or more PDUID AVPs set to each PDUID associated with the requesting RPAUID. In case of an unsuccessful announce authorization request for restricted ProSe direct discovery, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.2.3 Authorization for Announce Request with Application-controlled extension (model A)
+
+#### 5.2.3.1 General Description
+
+The announce authorization procedure (model A) with application-controlled extension is used by the ProSe Function serving the originating UE to obtain announce authorization information related to restricted ProSe direct discovery. The procedure is invoked by the ProSe Function and is used for the following purposes:
+
+- to request the ProSe Application Server to map the UE's Restricted ProSe Application User ID (RPAUID) to the corresponding ProSe Discovery UE ID(s) (PDUID(s));
+
+- to request the ProSe Application Server to allocate ProSe Restricted Code Suffix(es) for the RPAUID based on application layer information provided by the UE.
+
+#### 5.2.3.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function of the UE triggering the restricted ProSe direct discovery announce request procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific application requested by the UE in its initial request message, the PXR command shall include the ProSe-Request-Type AVP with the value AUTHORIZATION\_ANNOUNCE\_ACE (3), the Requesting-RPAUID AVP with the RPAUID assigned for this application to the originating UE, the Application-Data AVP with the data contained in the Application Level Container parameter in the initial request message from the originating UE, and the Allowed-Suffix-Number AVP with the allowed number of suffixes provisioned based on operator policy for this application.
+
+When receiving a PXR command for announce authorization for restricted ProSe direct discovery with application controlled extension, the ProSe Application Server shall first check if the application supports application-controlled extension. If yes, the ProSe Application Server shall assign the ProSe Restricted Code Suffix(es) for the requesting RPAUID based on the Application-Data AVP. The number of ProSe Restricted Code Suffixes allocated shall not exceed the value in Allowed-Suffix-Number AVP in the PXR command. The ProSe Application Server shall then send a ProXimity-Action-Answer (PXA) command including the PDUID(s) associated with the requesting RPAUID in one or more PDUID AVP(s), and one or more ProSe-Restricted-Code-Suffix-Range AVP(s) indicating the assigned ProSe Restricted Code Suffix(es). In case of an unsuccessful announce authorization request for restricted ProSe direct discovery with application-controlled extension, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.2.4 Authorization for Monitor Request (model A)
+
+#### 5.2.4.1 General Description
+
+The authorization for monitor request procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to restricted ProSe direct discovery. The procedure is invoked by the ProSe Function and is used:
+
+- to request the ProSe Application Server to select eligible target RPAUIDs from the application layer data enclosed in the monitoring request from the originating UE and provide the corresponding PDUIDs for those target RPAUIDs .
+
+#### 5.2.4.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function serving the monitoring UE shall send a ProXimity-Action-Request (PXR) command including the ProSe-Request-Type AVP with the value AUTHORIZATION\_MONITOR (4), the Requesting-RPAUID AVP indicating the restricted ProSe Application User ID of the monitoring UE, and the Application-Data AVP with the data contained in the Application Level Container parameter in the initial request message from the originating UE.
+
+When receiving a PXR command for monitor authorization for restricted ProSe direct discovery, the ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions. The ProSe Application Server shall then acknowledge the reception via a PXA command, set the Result-Code AVP to "SUCCESS" in the PXA command, include the PDUID(s) associated with the requesting RPAUID in PDUID AVP(s) in the PXA command, and one or more Monitor-Target AVP(s), each of which contains the target RPAUID that the requesting RPAUID is allowed to discover as well as the corresponding PDUID. If there is metadata associated with a target RPAUID, the ProSe Application Server shall also include the Metadata-Indicator in the corresponding Monitor-Target AVP. The ProSe Function shall include the Application-Data AVP with the successfully authenticated Target RPAUID(s), too. In case of an unsuccessful monitor authorization request for restricted ProSe direct discovery, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.2.5 Authorization for Monitor Request with Application-controlled Extension (model A)
+
+#### 5.2.5.1 General Description
+
+The authorization for monitor request with application-controlled extension procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to restricted ProSe direct discovery with application-controlled extension. The procedure is invoked by the ProSe Function and is used:
+
+- to request the ProSe Application Server to select eligible target RPAUIDs from the application layer data enclosed in the monitoring request from the originating UE and provide the corresponding PDUIDs for those target RPAUIDs; and
+- to request the ProSe Application Server to allocate "masks" for the ProSe Restricted Code Suffix for the target RPAUID based on application layer information provided by the originating UE, if restricted discovery with application-controlled extension is used .
+
+#### 5.2.5.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function serving the monitoring UE shall send a ProXimity-Action-Request (PXR) command including the ProSe-Request-Type AVP with the value AUTHORIZATION\_MONITOR\_ACE (5), the Requesting-RPAUID AVP with the RPAUID assigned for this application to the originating UE, and the Application-Data AVP with the data contained in the Application Level Container parameter in the initial request message from the originating UE.
+
+When receiving a PXR command for monitor authorization for restricted ProSe direct discovery with application-controlled extension, the ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions. The ProSe Application Server shall then acknowledge the reception via a PXA command, sets the Result-Code AVP to "SUCCESS" in the PXA command, include the PDUID associated with the requesting RPAUID in PDUID AVP in the PXA command, and one or more Monitor-Target AVP(s), each of which contains the target RPAUID that the requesting RPAUID is allowed to discover as well as the corresponding PDUID. If there is metadata associated with a target RPAUID, the ProSe Application Server shall also include the Metadata-Indicator in the corresponding Monitor-Target AVP. The ProSe Application Server shall also include the ProSe Restricted Code Suffix Masks in each Monitor-Target AVP. The ProSe Function shall include the Application-Data AVP with the successfully authenticated Target RPAUID(s), too. In case of an unsuccessful monitor authorization request for restricted ProSe direct discovery, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.2.6 Authorization for Discovery Permission (model A)
+
+#### 5.2.6.1 General
+
+The discovery permission authorization procedure is used by the ProSe Function to verify the application layer permission for restricted discovery model A between a requesting application user and a target application user, which are represented, respectively, by the requesting RPAUID and the target RPAUID.
+
+#### 5.2.6.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function shall send a PXR command including the ProSe-Request-Type AVP with the value RESTRICTED\_DISCOVERY\_MONITOR\_PERMISSION (6), the Requesting-RPAUID AVP indicating, respectively, the RPAUID of the originating UE and the Target-RPAUID AVP indicating the RPAUID of the targeted UE.
+
+Upon reception of a PXR command including the Requesting-RPAUID AVP and the Target-RPAUID AVP, the ProSe Application Server shall determine whether the application user of the originating UE is allowed to discover the application user of the targeted UE. If it is allowed, the ProSe Application Server shall then acknowledge the reception of the PXR command by sending the PXA command with the Result-Code AVP set to "SUCCESS" and the target-PDUID AVP(s) set to the PDUID(s) of the targeted application user. In case of an unsuccessful permission authorization request, an applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function notifies the ProSe Function of the originating UE, according to the procedure specified in 3GPP TS 29.345 [7].
+
+### 5.2.7 Authorization for Match Report (model A/model B)
+
+#### 5.2.7.1 General Description
+
+This procedure is used by the ProSe Function serving the monitoring UE (in model A) or discoverer UE (in model B) to obtain authorization information related to Match Report in restricted ProSe Direct Discovery.
+
+#### 5.2.7.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function shall send a ProXimity-Action-Request (PXR) command including the ProSe-Request-Type AVP with the value AUTHORIZATION\_MATCH\_REPORT (9), the Requesting-RPAAUID AVP indicating the restricted ProSe Application User ID of the requesting UE and the Target-RPAAUID AVP indicating the target restricted ProSe Application User ID.
+
+Upon reception of the PXR command, the ProSe Application Server shall determine whether the restricted ProSe Application User ID within Requesting-RPAAUID AVP is allowed to discover the target restricted ProSe Application User ID within Target-RPAAUID AVP.
+
+The ProSe Application Server shall then send a ProXimity-Action-Answer (PXA) command including the PDUID AVP(s) indicating the PDUID(s) associated with the RPAAUID of the requesting UE, the Target-PDUID AVP(s) indicating the PDUID(s) associated with the target RPAAUID, and optionally the ProSe-Application-Metadata AVP indicating certain metadata corresponding to the target RPAAUID, such as welcome message.
+
+In case of an unsuccessful authorization for Match Report Request, an applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+NOTE: The application logic in the ProSe Application Server triggered by the Diameter PXR command in this procedure is out of the scope of 3GPP.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function shall verify that there exists one received PDUID belonging to the requesting UE, and the target PDUID(s) are the same as the stored target PDUID(s) for the target RPAAUID. If the ProSe-Application-Metadata AVP has been included in the PXA command, and the Metadata -Indicator (see subclauses 5.2.4.2 and 5.2.5.2) associated with the target RPAAUID indicates METADATA\_UPDATE\_ALLOWED, the ProSe Function shall not cache the received metadata as the latest metadata for this target RPAAUID. If the check of PDUID(s) is successful, ProSe Function notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.2.8 Authorization for Discoveree Request (model B)
+
+#### 5.2.8.1 General Description
+
+This procedure may be used by the ProSe Function serving the Discoveree UE to obtain authorization information of the Discoveree UE related to Discoveree Request in restricted ProSe direct discovery.
+
+#### 5.2.8.2 Detailed description of the procedure
+
+The procedure in clause 5.2.4.2 shall be applied, with the only exception that the ProSe-Request-Type AVP included in PXR and PXA messages shall be set with the value AUTHORIZATION\_RESPONSE (7).
+
+### 5.2.9 Authorization for Discoverer Request (model B)
+
+#### 5.2.9.1 General Description
+
+This procedure is used by the ProSe Function serving the Discoverer UE to obtain authorization information of the Discoverer UE related to Discoverer Request in restricted ProSe Direct Discovery.
+
+#### 5.2.9.2 Detailed description of the procedure
+
+The procedure in clause 5.2.4.2 shall be applied, with the only exception that the ProSe-Request-Type AVP included in PXR and PXA messages shall be set with the value AUTHORIZATION\_QUERY (8).
+
+### 5.2.10 Authorization for Discovery Permission (model B)
+
+#### 5.2.10.1 General Description
+
+The discovery permission authorization procedure is used by the ProSe Function to verify the application layer permission for restricted discovery model B between a requesting application user and a target application user, which are represented, respectively, by the requesting RPAUID and the target RPAUID.
+
+#### 5.2.10.2 Detailed description of the procedure
+
+The procedure in clause 5.2.6.2 shall be applied, with the only exception that the ProSe-Request-Type AVP included in PXR and PXA messages shall be set with the value QUERY\_PERMISSION (10).
+
+### 5.2.11 Discovery Authorization Update
+
+#### 5.2.11.1 General Description
+
+The discovery authorization update procedure is used by the ProSe Application Server to request the ProSe Function serving the UE which has revoked permissions related to other users, to take actions to update the ProSe Restricted Code or Restricted Discovery Filters to prevent the banned users (users whose permissions have been revoked) from discovering the announcing user.
+
+This procedure uses the Diameter commands ProXimity-Application-Request (XAR)/ProXimity-Application-Answer (XAA), and ProXimity-Action-Request (PXR)/ProXimity-Action-Answer (PXA) in the respective Diameter applications as specified in subclause 6.
+
+#### 5.2.11.2 Detailed description of the discovery authorization update procedure
+
+The ProSe Application Server shall send the ProXimity-Application-Request (XAR) command to the ProSe Function serving the UE which has announced the RPAUID whose discovery permissions related to other users has been revoked. The identity of this ProSe Function is found by the ProSe Application Server by mapping the RPAUID to a PDUID. If multiple PDUIDs have been found to be used for this RPAUID, the procedure shall be invoked multiple times, for each ProSe Function to which the PDUID belongs.
+
+The ProSe Application Server shall include in the request the ProSe-Request-Type AVP with the value AUTHORIZATION\_UPDATE (11), the Requesting-RPAUID AVP with the RPAUID which originated this application-layer permission change, and one or more Banned-User-Target AVP identifying the RPAUID(s) whose discovery permissions have been revoked and the corresponding PDUID(s).
+
+When receiving an XAR command for authorization update for restricted ProSe direct discovery, the ProSe Function shall examine the RPAUID AVP and locate the UE context which stores the allocated ProSe Restricted Code for this RPAUID. If this check is successful, the ProSe Function shall then acknowledge the reception of the XAR command, set the Result-Code AVP to "SUCCESS" in the XAA command, and include the ProSe-Request Type AVP set to the same value as that included in the XAR command. In case of an unsuccessful request, an applicable value defined in subclause 6.7.3 shall be used to indicate the cause.
+
+Then the ProSe Function shall check the Banned-User-Target AVP(s) (i.e. , blacklist users) and compare it with all RPAUIDs which are currently authorized for monitoring the RPAUID being announced (i.e. , white-list users). If the black-list users and white-list users have no overlapping, the procedure is completed and no further action needs to be taken. Otherwise, the ProSe Function shall either allocate a new ProSe Restricted Code and notify the still-eligible white-list users, or revoke the Restricted Discovery Filters for the white-list users who have been banned. Depending on the action, the corresponding procedures described in 3GPP TS 29.345 [7] are to be invoked.
+
+When receiving XAA from the ProSe Function, the ProSe Application Server shall check if the Result-Code AVP indicates SUCCESS. If it indicates SUCCESS, the ProSe Application Server shall wait for the result of this discovery authorization update.
+
+After a time configured by the operator, the ProSe Function of the UE announcing the requesting RPAUID shall send the ProXimity-Action-Request (PXR) command to notify the ProSe Application Server of the specific application
+
+requested by the UE in its initial request message, about the result of discovery update process. The ProSe Function shall include in the request the ProSe-Request-Type AVP with the value AUTHORIZATION\_UPDATE (11) and the Requesting-RPAUID AVP with the RPAUID of the announcing UE involved in this discovery authorization update, and one or more Banned-User-Target AVPs including the RPAUID-PDRID pairs which have been successfully banned from discovering the requesting RPAUID.
+
+When receiving a PXR command for discovery authorization update for restricted ProSe direct discovery, the ProSe Application Server shall acknowledge the reception of the PXR command and shall send a PXA command with the Result-Code AVP set to "SUCCESS". In case of an unsuccessful discovery authorization update result notification for restricted ProSe direct discovery, applicable value defined in subclause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function checks the Result-Code AVP to see if it indicates SUCCESS.
+
+## 5.3 Open ProSe direct discovery
+
+### 5.3.1 Authorization for Announce Request with Application-controlled extension
+
+#### 5.3.1.1 General Description
+
+The announce authorization procedure with application-controlled extension is used by the ProSe Function serving the originating UE to obtain announce authorization information related to open ProSe direct discovery. The procedure is invoked by the ProSe Function and to request the ProSe Application Server to allocate ProSe Application Code Suffix(es) for the ProSe Application ID based on application layer information provided by the UE.
+
+#### 5.3.1.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function of the UE triggering the open ProSe direct discovery announce request procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific application requested by the UE in its initial request message, the PXR command shall include the ProSe-Request-Type AVP with the value AUTHORIZATION\_ANNOUNCE\_ACE\_OPEN (12), the ProSe-Application-ID AVP with the ProSe Application ID requested by the application in the originating UE, the Application-Data AVP with the data contained in the Application Level Container parameter in the initial request message from the originating UE, and the Allowed-Suffix-Number AVP with the allowed number of suffixes provisioned based on operator policy for this application.
+
+When receiving a PXR command for announce authorization for open ProSe direct discovery with application-controlled extension, the ProSe Application Server shall first check if the application supports application-controlled extension. If yes, the ProSe Application Server shall assign the ProSe Application Code Suffix(es) for the requesting ProSe Application ID based on the Application-Data AVP. The number of ProSe Application Code Suffixes allocated shall not exceed the value in Allowed-Suffix-Number AVP in the PXR command. The ProSe Application Server shall then send a ProXimity-Action-Answer (PXA) command including one or more ProSe-Application-Code-Suffix-Range AVP(s) indicating the assigned ProSe Application Code Suffix(es). In case of an unsuccessful announce authorization request for open ProSe direct discovery with application-controlled extension, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+### 5.3.2 Authorization for Monitor Request with Application-controlled Extension
+
+#### 5.3.2.1 General Description
+
+The authorization for monitor request with application-controlled extension procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to open ProSe direct discovery with application-controlled extension. The procedure is invoked by the ProSe Function and is used to request the ProSe Application Server to allocate "masks" for the ProSe Application Code Suffix for the monitored ProSe Application ID based on application layer information provided by the originating UE, if open discovery with application-controlled extension is used.
+
+#### 5.3.2.2 Detailed description of the procedure
+
+To apply this procedure, the ProSe Function serving the monitoring UE shall send a ProXimity-Action-Request (PXR) command including the ProSe-Request-Type AVP with the value AUTHORIZATION\_MONITOR\_ACE\_OPEN (13), the ProSe Application ID AVP with the ProSe Application ID requested by the application in the originating UE, and the Application-Data AVP with the data contained in the Application Level Container parameter in the initial request message from the originating UE.
+
+When receiving a PXR command for monitor authorization for open ProSe direct discovery with application-controlled extension, the ProSe Application Server shall examine the Application-Data AVP and determine proper ProSe Application Code Suffix Masks matching the data enclosed in the Application-Data AVP. Then, the ProSe Application Server shall then acknowledge the reception via a PXA command, sets the Result-Code AVP to "SUCCESS" in the PXA command, include one or more ProSe Application Code Suffix Masks in ProSe-Code-Suffix-Mask AVP(s). In case of an unsuccessful monitor authorization request for open ProSe direct discovery, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
+
+When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it indicates SUCCESS, the ProSe Function notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
+
+# --- 6 PC2 protocol
+
+## 6.1 Protocol Support
+
+### 6.1.1 Use of Diameter base protocol
+
+The Diameter base protocol as specified in IETF RFC 6733 [12] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures specified in IETF RFC 6733 [12] (including error handling and unrecognised information handling) shall be used unmodified. Only commands related to peer-to-peer connection are re-used from the Diameter base protocol (IETF RFC 6733 [12]), i.e. Capabilities-Exchange-Request (CER), Capabilities-Exchange-Answer (CEA), Disconnect-Peer-Request (DPR), Disconnect-Peer-Answer (DPA), Device-Watchdog-Request (DWR) and Device-Watchdog-Answer (DWA).
+
+With regards to the Diameter protocol defined over the PC2 interface, the ProSe Application Server shall act as the Diameter server, in the sense that it is the network element that handles action requests. The ProSe Function shall act as the Diameter client, in the sense that it is the network element requesting actions.
+
+A Diameter routing table entry can have a different destination based on the application identifier of the command. The application identifier stored in the command header must match the value of any application identifier AVPs in the command body. Diameter agents (relay, proxy, redirection, translation agents) should use the application identifier in the command header to route to a suitable destination.
+
+### 6.1.2 Transport protocol
+
+Diameter messages over the PC2 interface shall make use of TCP IETF RFC 791 [4] or SCTP IETF RFC 4960 [5].
+
+### 6.1.3 Advertising Application Support
+
+The Diameter application identifier assigned to the PC2 interface application in the present release is 16777350.
+
+NOTE: The PC2 interface application identifier 16777337 is used in Release 12 document where only the usage PXR/PXA is specified. For backward compatibility, the ProSe Application Server in releases later than Rel-12 is encouraged to also support the Rel-12 version of this specification and the old application ID 16777337.
+
+The ProSe Application Server and ProSe Function shall advertise support of the Diameter PC2 applications by including the value of the PC2 application identifiers in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the CER and CEA commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the CER and CEA commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the CER and CEA commands.
+
+The Vendor-Id AVP included in CER and CEA commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [12].
+
+## 6.2 Initialization and maintenance of connection and session
+
+A peer-to-peer connection is a connection between ProSe Application Server and ProSe Function.
+
+A PC2 Diameter session shall consist of a single request and answer pair. The PC2 Diameter session is terminated after each request and answer pair interaction. In order to indicate that the session state is not to be maintained, the Diameter client and server shall include the Auth-Session-State AVP with the value set to NO\_STATE\_MAINTAINED (1), in the request and in the answer messages (see IETF RFC 6733 [12]).
+
+## 6.3 Security over PC2 reference point
+
+Security aspects of ProSe PC2 reference point are defined in 3GPP TS 33.303 [6].
+
+## 6.4 PC2 specific AVPs
+
+### 6.4.1 General
+
+Table 6.4.1-1 describes the Diameter AVPs defined for the PC2 reference point, their AVP Code values, types and possible flag values. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415).
+
+**Table 6.4.1-1: PC2 specific Diameter AVPs**
+
+| Attribute Name           | AVP Code | Clause defined | Value Type  | AVP Flag rules (Note) |     |            |          |
+|--------------------------|----------|----------------|-------------|-----------------------|-----|------------|----------|
+|                          |          |                |             | Must                  | May | Should not | Must not |
+| Origin-App-Layer-User-Id | 3600     | 6.4.2          | UTF8String  | M,V                   | P   |            |          |
+| Target-App-Layer-User-Id | 3601     | 6.4.3          | UTF8String  | M,V                   | P   |            |          |
+| ProSe-Function-ID        | 3602     | 6.4.4          | OctetString | M,V                   | P   |            |          |
+| ProSe-Request-Type       | 3603     | 6.4.5          | Unsigned32  | M,V                   | P   |            |          |
+| PDUID                    | 3604     | 6.4.6          | OctetString | V                     | P   |            | M        |
+| Application-Data         | 3605     | 6.4.7          | UTF8String  | V                     | P   |            | M        |
+| Allowed-Suffixes-Number  | 3606     | 6.4.8          | Unsigned32  | V                     | P   |            | M        |
+| Monitor-Target           | 3607     | 6.4.9          | Grouped     | V                     | P   |            | M        |
+| ProSe-Code-Suffix-Mask   | 3608     | 6.4.10         | Grouped     | V                     | P   |            | M        |
+| Suffix-Code              | 3609     | 6.4.11         | OctetString | V                     | P   |            | M        |
+| Suffix-Mask              | 3610     | 6.4.12         | OctetString | V                     | P   |            | M        |
+| Banned-User-Target       | 3611     | 6.4.17         | Grouped     | V                     | P   |            | M        |
+| Metadata-Indicator       | 3612     | 6.4.18         | Unsigned32  | V                     | P   |            | M        |
+
+NOTE : The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [12].
+
+### 6.4.2 Origin-App-Layer-User-Id AVP
+
+The Origin-App-Layer-User-Id AVP (AVP code 3600) is of type UTF8String, and it contains an identity identifying an origin user within the context of a specific application (e.g. alice@social.net).
+
+### 6.4.3 Target-App-Layer-User-Id AVP
+
+The Target-App-Layer-User-Id AVP (AVP code 3601) is of type UTF8String, and it contains an identity identifying a target user within the context of a specific application (e.g. tommy@social.net).
+
+### 6.4.4 ProSe-Function-ID AVP
+
+The ProSe-Function-ID AVP (AVP code 3602) is of type OctetString, and it indicates an FQDN that identifies a ProSe Function.
+
+### 6.4.5 ProSe-Request-Type AVP
+
+The ProSe-Request-Type AVP (AVP code 3603) is of type Unsigned32, and contains the reason for sending the PX-Request message or XA-Request message.
+
+The following values are defined:
+
+#### 0 (APPLICATION\_REGISTRATION\_FOR\_PROSE):
+
+The ProXimity-Action-Request message is sent to initiate an application registration for ProSe procedure.
+
+#### 1 (PROSE\_MAP\_REQUEST):
+
+The ProXimity-Action-Request message is sent to initiate a Proximity map request procedure.
+
+#### 2 (AUTHORIZATION\_ANNOUNCE):
+
+The ProXimity-Action-Request message is sent to initiate an announce authorization procedure for restricted discovery.
+
+#### 3 (AUTHORIZATION\_ANNOUNCE\_ACE):
+
+The ProXimity-Action-Request message is sent to initiate an announce authorization procedure for restricted discovery with application-controlled extension.
+
+#### 4 (AUTHORIZATION\_MONITOR):
+
+The ProXimity-Action-Request message is sent to initiate a monitor authorization procedure for restricted discovery.
+
+#### 5 (AUTHORIZATION\_MONITOR\_ACE):
+
+The ProXimity-Action-Request message is sent to initiate a monitor authorization procedure for restricted discovery with application-controlled extension.
+
+#### 6 (MONITOR\_PERMISSION):
+
+The ProXimity-Action-Request message is sent to initiate an inquiry for the discovery permissions between two RPAUIDs used in restricted ProSe direct discovery monitoring model A.
+
+#### 7 (AUTHORIZATION\_RESPONSE):
+
+The ProXimity-Action-Request message is sent to initiate an authorization for Discoveree Request procedure.
+
+#### 8 (AUTHORIZATION\_QUERY):
+
+The ProXimity-Action-Request message is sent to initiate an authorization for Discoverer Request procedure.
+
+#### 9 (AUTHORIZATION\_MATCH\_REPORT):
+
+The ProXimity-Action-Request message is sent to initiate an authorization for Match Report procedure in model A or model B.
+
+#### 10 (QUERY\_PERMISSION)
+
+The ProXimity-Action-Request message is sent to initiate an inquiry for the discovery permissions between two RPAUIDs used in restricted ProSe direct discovery model B discoverer operation.
+
+#### 11 (AUTHORIZATION\_UPDATE)
+
+The ProXimity-Action-Request message or ProXimity-Application-Request message is sent for the purpose of discovery authorization update.
+
+#### 12 (AUTHORIZATION\_ANNOUNCE\_ACE\_OPEN):
+
+The ProXimity-Action-Request message is sent to initiate an announce authorization procedure for open discovery with application-controlled extension.
+
+#### 13 (AUTHORIZATION\_MONITOR\_ACE\_OPEN):
+
+The ProXimity-Action-Request message is sent to initiate a monitor authorization procedure for open discovery with application-controlled extension.
+
+### 6.4.6 PDUID AVP
+
+The PDUID AVP (AVP code 3604) is of type OctetString, and it indicates a ProSe Discovery UE ID that identifies a UE identity used in restricted ProSe direct discovery.
+
+### 6.4.7 Application-Data AVP
+
+The Application-Data AVP (AVP code 3605) is of type UTF8String, and it contains
+
+- a list of target RPAUIDs of UEs in restricted ProSe Direct Discovery for monitoring or query requests.
+- information related to suffix allocation for an announcing UE when application-controlled extension is used.
+- a list of successfully authenticated target RPAUIDs of UEs in restricted ProSe Direct Discovery.
+
+### 6.4.8 Allowed-Suffixes-Number AVP
+
+The Allowed-Suffixes-Number AVP (AVP code 3606) is of type Unsigned32, and it indicates the maximum number of suffix codes which are used as part of ProSe Application Code or ProSe Restricted Code that the ProSe Application Server can assign to the UE for a ProSe Application ID or an RPAUID.
+
+### 6.4.9 Monitor-Target AVP
+
+The Monitor-Target AVP (AVP code 3607) is of type Grouped. It contains a Target-RPAUID, a PDUID and zero or more ProSe Code Suffix Mask(s).
+
+The AVP format shall conform to:
+
+```
+Monitor-Target ::= <AVP header:3607>
+                  { Target-RPAUID }
+                  { PDUID }
+                  [ Metadata-Indicator ]
+                  *[ ProSe-Code-Suffix-Mask ]
+                  *[AVP]
+```
+
+If the Metadata-Indicator value is "0 (NO\_METADATA)", the Metadata-Indicator AVP may be omitted.
+
+### 6.4.10 ProSe- Code-Suffix-Mask AVP
+
+The ProSe-Code-Suffix-Mask AVP (AVP code 3608) is of type Grouped. It contains a suffix code and one or more suffix mask(s), each of which has the same size as the suffix code.
+
+The AVP format shall conform to:
+
+```
+ProSe-Code-Suffix-Mask ::= <AVP header:3608>
+                          { Suffix-Code }
+                          1*{ Suffix-Mask }
+                          *[AVP]
+```
+
+### 6.4.11 Suffix-Code AVP
+
+The Suffix-Code AVP (AVP code 3609) is of type OctetString. It contains a suffix code which shall be used as either the allocated ProSe Application Code Suffix or ProSe Restricted Code Suffix, or a matching target for the suffix part of a ProSe Application Code or ProSe Restricted Code.
+
+### 6.4.12 Suffix-Mask AVP
+
+The Suffix-Mask AVP (AVP code 3610) is of type OctetString. It contains a suffix mask which shall be used as a bitmask for matching the target suffix code in the suffix part of a ProSe Application Code or ProSe Restricted Code.
+
+### 6.4.13 Void
+
+### 6.4.14 Void
+
+### 6.4.15 Void
+
+### 6.4.16 Void
+
+### 6.4.17 Banned-User-Target AVP
+
+The Banned-User-Target AVP (AVP code 3611) is of type Grouped. It contains a Target-RPAUID and a Target-PDUID.
+
+The AVP format shall conform to:
+
+```
+Banned-User-Target ::= <AVP header:3611>
+                       { Target-RPAUID }
+                       { Target-PDUID }
+                       * [AVP]
+```
+
+### 6.4.18 Metadata-Indicator AVP
+
+The Metadata-Indicator AVP (AVP code 3612) is of type Unsigned32, and contains the options for metadata associated with a particular target RPAUID. The following values are defined:
+
+#### 0 (NO\_METADATA):
+
+This value may be used to indicate that there is no metadata associated with the target RPAUID. This is the default value applicable if this AVP is not supplied.
+
+#### 1 (METADATA\_UPDATE\_DISALLOWED):
+
+This value shall be used to indicate that there exists metadata associated with the target RPAUID, but the metadata is not allowed to be updated.
+
+#### 2 (METADATA\_UPDATE\_ALLOWED):
+
+This value shall be used to indicate that there exists metadata associated with the target RPAUID, and the metadata is allowed to be updated.
+
+## 6.5 PC2 re-used AVPs
+
+Table 6.5.1-1 lists the Diameter AVPs re-used by the PC2 reference point from existing Diameter Applications, reference to their respective specifications and a short description of their usage within the PC2 reference point. Other AVPs from existing Diameter Applications, except for the AVPs from the Diameter base protocol specified in IETF RFC 6733 [12], do not need to be supported. The AVPs from the Diameter base protocol specified in IETF RFC 6733 [12] are not included in Table 6.5.1-1, but they are re-used for the PC2 reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings.
+
+**Table 6.5.1-1: PC2 re-used Diameter AVPs**
+
+| Attribute Name                      | Reference          | Description                                                                                                                                                       |
+|-------------------------------------|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Load                                | IETF RFC 8583 [11] | The AVP used to convey load information between Diameter nodes. This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared.                     |
+| Requesting-EPUID                    | 3GPP TS 29.345 [7] | Contains an identifier for EPC-level ProSe Discovery that uniquely identifies a UE registered for ProSe triggering a Proximity request.                           |
+| Targeted-EPUID                      | 3GPP TS 29.345 [7] | Contains an identifier for EPC-level ProSe Discovery that uniquely identifies a UE registered for ProSe targeted by a Proximity request.                          |
+| ProSe-Restricted-Code-Suffix-Range  | 3GPP TS 29.345 [7] | Contains a range of suffixes which can be used for restricted ProSe direct discovery announcing when application-controlled extension is used.                    |
+| ProSe-Application-Code-Suffix-Range | 3GPP TS 29.345 [7] | Contains a range of suffixes which can be used for open ProSe direct discovery announcing when application-controlled extension is used.                          |
+| ProSe-App-Id                        | 3GPP TS 29.345 [7] | Contains an ProSe Application ID associated with the announcing or monitoring request for open ProSe direct discovery with application-controlled extension.      |
+| Requesting-RPAUID                   | 3GPP TS 29.345 [7] | Contains a Restricted ProSe Application User ID associated with the requesting UE for the announcing or monitoring request for restricted ProSe direct discovery. |
+| Target-RPAUID                       | 3GPP TS 29.345 [7] | Contains a Restricted ProSe Application User ID of the target UE associated with the monitoring request for restricted ProSe direct discovery.                    |
+| Target-PDUID                        | 3GPP TS 29.345 [7] | Contains a ProSe Discovery User ID of the target UE associated with the monitoring request for restricted ProSe direct discovery.                                 |
+| ProSe-Application-Metadata          | 3GPP TS 29.345 [7] | Contains the metadata corresponding to the target RPAUID for restricted ProSe direct discovery, such as welcome message.                                          |
+
+## 6.6 PC2 messages
+
+### 6.6.1 Command-Code Values
+
+This section defines the Command-Code values for the PC2 interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [8]. Every command is defined by means of the ABNF syntax in IETF RFC 2234 [9], and according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [12].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.6.1.1: Command-Code values for PC2**
+
+| Command-Name                  | Abbreviation | Code    | Section |
+|-------------------------------|--------------|---------|---------|
+| ProXimity-Action-Request      | PXR          | 8388676 | 6.6.2   |
+| ProXimity-Action-Answer       | PXA          | 8388676 | 6.6.3   |
+| ProXimity-Application-Request | XAR          | 8388727 | 6.6.4   |
+| ProXimity-Application-Answer  | XAA          | 8388727 | 6.6.5   |
+
+### 6.6.2 ProXimity-Action-Request (PXR) command
+
+The PXR command, indicated by the Command-Code field set to 8388676 and the 'R' bit set in the Command Flags field, is sent by the ProSe Function to the ProSe Application Server as part of the procedures specified for EPC-level ProSe discovery and ProSe direct discovery in clause 5.
+
+Message Format:
+
+```
+<PX-Request> ::= <Diameter Header: 8388676, REQ, PXY >
+                 < Session-Id >
+```
+
+```
+
+    { Auth-Application-Id }
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    { Destination-Realm }
+    [ Destination-Host ]
+    [ Origin-State-Id ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+    { ProSe-Request-Type }
+    [ Origin-App-Layer-User-Id ]
+    [ Target-App-Layer-User-Id ]
+    [ Requesting-EPUID ]
+    [ ProSe-Function-ID ]
+    [ Requesting-RPAUID ]
+    [ ProSe-App-Id ]
+    [ Application-Data ]
+    [ Allowed-Suffix-Number ]
+    [ Target-RPAUID ]
+    *[ Banned-User-Target ]
+    *[ AVP ]
+
+```
+
+### 6.6.3 ProXimity-Action-Answer (PXA) command
+
+The PXA command, indicated by the Command-Code field set to 8388676 and the 'R' bit cleared in the Command Flags field, is sent by the ProSe Application Server to the ProSe Function in response to the PXR command as part of the procedures specified for EPC-level ProSe discovery and ProSe direct discovery in clause 5.
+
+Message Format:
+
+```
+
+<PX-Answer> ::= < Diameter Header: 8388676, PXY >
+                < Session-Id >
+                { Auth-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+                [ Error-Message ]
+                [ Error-Reporting-Host ]
+                [ Failed-AVP ]
+                [ Origin-State-Id ]
+                *[ Redirect-Host ]
+                [ Redirect-Host-Usage ]
+                [ Redirect-Max-Cache-Time ]
+                *[ Proxy-Info ]
+                { ProSe-Request-Type }
+                [ Targeted-EPUID ]
+                [ ProSe-Function-ID ]
+                *[ PDUID ]
+                *[ ProSe-Restricted-Code-Suffix-Range ]
+                *[ ProSe-Application-Code-Suffix-Range ]
+                *[ ProSe-Code-Suffix-Mask ]
+                *[ Monitor-Target ]
+                *[ Target-PDUID ]
+                [ProSe-Application-Metadata ]
+                [Application-Data ]
+                *[ Load ]
+                *[ AVP ]
+
+```
+
+### 6.6.4 ProXimity-Application-Request (XAR) command
+
+The XAR command, indicated by the Command-Code field set to 8388727 and the 'R' bit set in the Command Flags field, is sent by the ProSe Application Server to the ProSe Function as part of the discovery authorization update procedure.
+
+Message Format:
+
+```
+
+<XA-Request> ::= < Diameter Header: 8388727, REQ, PXY >
+                < Session-Id >
+                { Auth-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+
+```
+
+```
+
+    { Origin-Realm }
+    { Destination-Realm }
+    [ Destination-Host ]
+    [ Origin-State-Id ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+    { ProSe-Request-Type }
+    [ Requesting-RPAUID ]
+    *[ Banned-User-Target ]
+    *[ AVP ]
+
+```
+
+### 6.6.5 ProXimity-Application-Answer (XAA) command
+
+The XAA command, indicated by the Command-Code field set to 8388727 and the 'R' bit cleared in the Command Flags field, is sent by the ProSe Function to the ProSe Application Server in response to the XAR command as part of the discovery authorization update procedure.
+
+Message Format:
+
+```
+
+<XA-Answer> ::= < Diameter Header: 8388727, PXY >
+                < Session-Id >
+                { Auth-Application-Id }
+                { Auth-Session-State }
+                { Origin-Host }
+                { Origin-Realm }
+                [ Result-Code ]
+                [ Experimental-Result ]
+                [ Error-Message ]
+                [ Error-Reporting-Host ]
+                [ Failed-AVP ]
+                [ Origin-State-Id ]
+                *[ Redirect-Host ]
+                [ Redirect-Host-Usage ]
+                [ Redirect-Max-Cache-Time ]
+                *[ Proxy-Info ]
+                { ProSe-Request-Type }
+                *[ AVP ]
+
+```
+
+## 6.7 PC2 specific Experimental-Result-Code AVP values
+
+### 6.7.1 General
+
+This clause defines result code values that shall be supported by Diameter implementations that conform to this specification.
+
+### 6.7.2 Success
+
+Result Codes that fall into the Success category are used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in the Diameter base protocol (IETF RFC 6733 [12]) are applied.
+
+### 6.7.3 Failures
+
+Errors that fall into the Failures category shall be used to inform the peer that the request has failed. The Result-Code AVP values defined in Diameter base protocol (IETF RFC 6733 [12]) are applied. When one of the result codes as defined below is included in the PXA command, it is included in an Experimental-Result AVP and the Result-Code AVP is absent.
+
+#### 6.7.3.1 DIAMETER\_ERROR\_ORIGIN\_ALUID\_UNKNOWN (5590)
+
+This result code indicates that there is no valid context associated to the origin ALUID received in the request.
+
+#### 6.7.3.2 DIAMETER\_ERROR\_TARGET\_ALUID\_UNKNOWN (5591)
+
+This result code indicates that there is no valid context associated to the target ALUID received in the request.
+
+#### 6.7.3.3 DIAMETER\_ERROR\_PPID\_UNKNOWN (5592)
+
+This result code indicates that there is no valid ProSe Function associate to the PPID received in the request.
+
+#### 6.7.3.4 DIAMETER\_ERROR\_APP\_REGISTER\_REJECT (5593)
+
+This result code indicates that the ProSe Application Server cannot accept the application registration request for an unspecific reason.
+
+#### 6.7.3.5 DIAMETER\_ERROR\_PROSE\_MAP\_REQUEST\_DISALLOWED (5594)
+
+This result code indicates that the ProSe Application Server cannot accept the map request because the targeted application user is not allowed to be discovered by the originating application user.
+
+#### 6.7.3.6 DIAMETER\_ERROR\_MAP\_REQUEST\_REJECT (5595)
+
+This result code indicates that the ProSe Application Server cannot accept the map request for an unspecific reason.
+
+#### 6.7.3.7 DIAMETER\_ERROR\_REQUESTING\_RPAUID\_UNKNOWN (5596)
+
+This result code indicates that the ProSe Application Server cannot find the requesting RPAUID included in the restricted discovery authorization request.
+
+#### 6.7.3.8 DIAMETER\_ERROR\_UNKNOWN\_OR\_INVALID\_TARGET\_SET (5597)
+
+This result code indicates that the ProSe Application Server cannot authorize the request because all target RPAUID(s) provided in the request are either unknown to the ProSe Application Server, or not eligible to be discovered by the requesting RPAUID.
+
+#### 6.7.3.9 DIAMETER\_ERROR\_MISSING\_APPLICATION\_DATA (5598)
+
+This result code indicates that there is no application data provided so the ProSe Application Server cannot process the corresponding discovery request.
+
+#### 6.7.3.10 DIAMETER\_ERROR\_AUTHORIZATION\_REJECT (5599)
+
+This result code indicates that for the particular requesting type of restricted discovery, the ProSe Application Server found that the requesting RPAUID is not authorized.
+
+#### 6.7.3.11 DIAMETER\_ERROR\_DISCOVERY\_NOT\_PERMITTED (5600)
+
+This result code indicates that the requesting RPAUID is not allowed to discover the target RPAUID.
+
+#### 6.7.3.12 DIAMETER\_ERROR\_TARGET\_RPAUID\_UNKNOWN (5601)
+
+This result code indicates that there is no valid target RPAUID received in the request.
+
+#### 6.7.3.13 DIAMETER\_ERROR\_INVALID\_APPLICATION\_DATA (5602)
+
+This result code indicates that there is invalid application data provided so the ProSe Application Server cannot process the corresponding discovery request.
+
+# Annex A (informative): Call Flows over PC2
+
+## A.1 EPC-Level ProSe discovery
+
+### A.1.1 Application registration for ProSe
+
+The Application registration for ProSe procedure is used by the UE to register an application with the ProSe Function to activate ProSe features e.g. EPC-level ProSe discovery for a specific application.
+
+![Sequence diagram for Application registration for ProSe Procedure](20136850feb70fd71c7d41cdae203ebb_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2.Validate UE.
+    Note left of ProSe Function: 4.Indicate to UE registration successful (or not)
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 3. PXA
+```
+
+The diagram illustrates the sequence of messages for application registration. It starts with the ProSe Function sending a '1. PXR' message to the ProSe Application Server. The server then performs an internal '2.Validate UE.' step. Next, it sends a '3. PXA' message back to the ProSe Function. Finally, the ProSe Function sends a response '4.Indicate to UE registration successful (or not)' to the originating UE.
+
+Sequence diagram for Application registration for ProSe Procedure
+
+**Figure A.1.1: Application registration for ProSe Procedure**
+
+1. When the ProSe Function have received an application registration request, as defined in 3GPP TS 24.334 [10], from the originating UE and the requested application is on the stored list of authorised Application IDs, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in clause 5.1.1.
+2. The ProSe Application Server determines whether the registration can be accepted for the originating UE.
+3. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in clause 5.1.1.
+4. The ProSe Function send a response message to the originating UE indicating that the registration was successful (or not) as defined in 3GPP TS 24.334 [10].
+
+### A.1.2 Proximity map request
+
+The proximity map request procedure is used by the ProSe Function to request the identity of the ProSe Function for the targeted UE for which the originating UE shall get alerts when in proximity of the targeted UE.
+
+![Sequence diagram of the Proximity map request procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: 1. PXR (ProSe Function to ProSe Application Server), 2. Validate UE map request. (ProSe Application Server), 3. PXA (ProSe Application Server to ProSe Function), 4. Initialize proximity request procedure. (ProSe Function).](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2.Validate UE map request.
+    Note left of ProSe Function: 4.Initialize proximity request procedure.
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 3. PXA
+```
+
+Sequence diagram of the Proximity map request procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: 1. PXR (ProSe Function to ProSe Application Server), 2. Validate UE map request. (ProSe Application Server), 3. PXA (ProSe Application Server to ProSe Function), 4. Initialize proximity request procedure. (ProSe Function).
+
+**Figure A.2.1: Proximity map request procedure**
+
+1. When the ProSe Function have received a proximity request, as defined in 3GPP TS 24.334 [10], from the UE the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in clause 5.1.2.
+2. The ProSe Application Server determines whether the originating UE is allowed to discover the targeted UE.
+3. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in clause 5.1.2.
+4. If the mapping is successful, the ProSe Function initialize the proximity request procedure as defined in 3GPP TS 29.345 [7].
+
+## A.2 Restricted ProSe direct discovery
+
+### A.2.1 Authorization for Announce Request (model A)
+
+The authorization for announce request procedure is used by the ProSe Function serving the originating UE to obtain announce authorization information related to restricted ProSe direct discovery.
+
+![Sequence diagram for Figure A.2.1: Authorization for announce request procedure. Lifelines: ProSe Function and ProSe Application Server. Step 1: PXR from ProSe Function to ProSe Application Server. Step 2: PXA from ProSe Application Server to ProSe Function. Step 3: Verify PDUID and notify the originating UE (internal to ProSe Function).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 2. PXA
+    Note left of ProSe Function: 3. Verify PDUID and  
+notify the originating UE
+  
+```
+
+Sequence diagram for Figure A.2.1: Authorization for announce request procedure. Lifelines: ProSe Function and ProSe Application Server. Step 1: PXR from ProSe Function to ProSe Application Server. Step 2: PXA from ProSe Application Server to ProSe Function. Step 3: Verify PDUID and notify the originating UE (internal to ProSe Function).
+
+**Figure A.2.1: Authorization for announce request procedure**
+
+1. When the ProSe Function has received an announce request, as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for restricted ProSe direct discovery model A announcing, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.2.
+2. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.2.
+3. The ProSe Function verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.2 Authorization for Restricted Discovery Announce Request with Application-controlled extension (model A)
+
+The announce authorization procedure with application-controlled extension is used by the ProSe Function serving the originating UE to obtain announce authorization information related to restricted ProSe direct discovery.
+
+![Sequence diagram for Figure A.2.2: Authorization for restricted discovery announce request with application-controlled extension procedure. Lifelines: ProSe Function and ProSe Application Server. Step 1: PXR from ProSe Function to ProSe Application Server. Step 2: Check application capability (internal to ProSe Application Server). Step 3: PXA from ProSe Application Server to ProSe Function. Step 4: Verify PDUID and notify the originating UE (internal to ProSe Function).](4af57aad638888edf2062306f8a54a6c_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    ProSe Function->>ProSe Application Server: 1. PXR
+    Note right of ProSe Application Server: 2. Check application  
+capability
+    ProSe Application Server-->>ProSe Function: 3. PXA
+    Note left of ProSe Function: 4. Verify PDUID and notify  
+the originating UE
+  
+```
+
+Sequence diagram for Figure A.2.2: Authorization for restricted discovery announce request with application-controlled extension procedure. Lifelines: ProSe Function and ProSe Application Server. Step 1: PXR from ProSe Function to ProSe Application Server. Step 2: Check application capability (internal to ProSe Application Server). Step 3: PXA from ProSe Application Server to ProSe Function. Step 4: Verify PDUID and notify the originating UE (internal to ProSe Function).
+
+**Figure A.2.2: Authorization for restricted discovery announce request with application-controlled extension procedure**
+
+1. When the ProSe Function has received an announce request with application-controlled extension, as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is
+
+authorized for restricted ProSe direct discovery model A announcing, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.3.
+
+2. The ProSe Application Server shall check if the application supports application-controlled extension.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.3.
+4. The ProSe Function verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.3 Authorization for Monitor Request (model A)
+
+The authorization for monitor request procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to restricted ProSe direct discovery.
+
+![Sequence diagram for Authorization for Monitor request (model A)](55136bc716146672fc680fa05989f1d2_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2. Verify the Application Level Container
+    Note left of ProSe Function: 4. Verify PDUID and notify the originating UE
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server->>ProSe Function: 3. PXA
+```
+
+The diagram is a sequence diagram illustrating the authorization for a monitor request. It features two main lifelines: 'ProSe Function' on the left and 'ProSe Application Server' on the right. The interaction consists of three numbered steps: 1. A 'PXR' message is sent from the ProSe Function to the ProSe Application Server. 2. Inside the ProSe Application Server, a box labeled '2. Verify the Application Level Container' indicates an internal processing step. 3. A 'PXA' message is sent from the ProSe Application Server back to the ProSe Function. 4. Inside the ProSe Function, a box labeled '4. Verify PDUID and notify the originating UE' indicates another internal processing step.
+
+Sequence diagram for Authorization for Monitor request (model A)
+
+**Figure A.2.3: Authorization for Monitor request**
+
+1. When the ProSe Function has received a monitor request as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for restricted ProSe direct discovery model A monitoring, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.4.
+2. The ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.4.
+4. The ProSe Function verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.4 Authorization for Restricted Discovery Monitor Request with Application-controlled extension (model A)
+
+The authorization for monitor request with application-controlled extension procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to restricted ProSe direct discovery with application-controlled extension.
+
+![Sequence diagram showing the authorization for restricted discovery monitor request with application-controlled extension procedure. The diagram involves two lifelines: ProSe Function and ProSe Application Server. The sequence of messages is: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the Application Data (internal message on ProSe Application Server); 3. PXA from ProSe Application Server to ProSe Function; 4. Verify PDUID and notify the originating UE (internal message on ProSe Function).](dd5771673aececa53d42ece89218299d_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2. Verify the Application Data
+    Note left of ProSe Function: 4. Verify PDUID and notify the originating UE
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 3. PXA
+```
+
+Sequence diagram showing the authorization for restricted discovery monitor request with application-controlled extension procedure. The diagram involves two lifelines: ProSe Function and ProSe Application Server. The sequence of messages is: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the Application Data (internal message on ProSe Application Server); 3. PXA from ProSe Application Server to ProSe Function; 4. Verify PDUID and notify the originating UE (internal message on ProSe Function).
+
+**Figure A.2.4: Authorization for restricted discovery monitor request with application-controlled extension procedure**
+
+1. When the ProSe Function has received a monitor request with application-controlled extension as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for restricted ProSe direct discovery model A monitoring, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.5.
+2. The ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions.
+3. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.5.
+4. The ProSe Function verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.5 Authorization for Discovery Permission (model A)
+
+The discovery permission authorization procedure is used by the ProSe Function to verify the application layer permission for restricted discovery model A between an originating application user and a target application user, which are represented, respectively, by the requesting RPAUID and the target RPAUID.
+
+![Sequence diagram for Figure A.2.5: Authorization for discovery permission procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the originating UE (internal to ProSe Application Server); 3. PXA from ProSe Application Server to ProSe Function; 4. Notify the ProSe Function originating UE (internal to ProSe Function).](00504fc688ebcf131ccbeff94dfc9939_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    ProSe Function->>ProSe Application Server: 1. PXR
+    Note right of ProSe Application Server: 2. Verify the  
+originating UE
+    ProSe Application Server-->>ProSe Function: 3. PXA
+    Note left of ProSe Function: 4. Notify the ProSe  
+Function originating UE
+  
+```
+
+Sequence diagram for Figure A.2.5: Authorization for discovery permission procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the originating UE (internal to ProSe Application Server); 3. PXA from ProSe Application Server to ProSe Function; 4. Notify the ProSe Function originating UE (internal to ProSe Function).
+
+**Figure A.2.5: Authorization for discovery permission procedure**
+
+1. When the ProSe Function has received a monitor request as defined in 3GPP TS 29.345 [7], from the ProSe Function of the origination UE and the ProSe Restricted Code has been retrieved, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.6.
+2. The ProSe Application Server shall determine whether the originating UE is allowed to discover the targeted UE.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.6.
+4. The ProSe Function sends a response message to the ProSe Function of the originating UE as defined in 3GPP TS 29.345 [7].
+
+### A.2.6 Authorization for Match Report (model A/model B)
+
+This authorization for match report procedure is used by the ProSe Function serving the monitoring UE (in model A) or discoverer UE (in model B) to obtain authorization information related to Match Report in restricted ProSe Direct Discovery.
+
+![Sequence diagram for Figure A.2.6: Authorization for Match report procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: PXR from ProSe Function to ProSe Application Server; Application Level authorization check (internal to ProSe Application Server); PXA from ProSe Application Server to ProSe Function; Verify PDUID and notify the originating UE (internal to ProSe Function).](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    ProSe Function->>ProSe Application Server: PXR
+    Note right of ProSe Application Server: Application Level  
+authorization check
+    ProSe Application Server-->>ProSe Function: PXA
+    Note left of ProSe Function: Verify PDUID and notify  
+the originating UE
+  
+```
+
+Sequence diagram for Figure A.2.6: Authorization for Match report procedure. Lifelines: ProSe Function and ProSe Application Server. Steps: PXR from ProSe Function to ProSe Application Server; Application Level authorization check (internal to ProSe Application Server); PXA from ProSe Application Server to ProSe Function; Verify PDUID and notify the originating UE (internal to ProSe Function).
+
+**Figure A.2.6: Authorization for Match report procedure**
+
+1. When the ProSe Function has received a match report from the originating UE and the originating UE is authorized for restricted discovery, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.7.
+
+2. The ProSe Application Server shall determine whether the originating UE is allowed to discover the target restricted ProSe Application User.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.7.
+4. The ProSe Function verifies that the received PDUID belongs to the originating UE and and the target PDUID is the same as the stored target PDUID, then sends a response message to the originating UE.
+
+### A.2.7 Authorization for Discoveree Request (model B)
+
+This authorization for discoveree request procedure is used by the ProSe Function serving the Discoveree UE to obtain authorization information of the Discoveree UE related to Discoveree Request in restricted ProSe direct discovery.
+
+![Sequence diagram for Authorization for Discoveree request (model B). The diagram shows three lifelines: ProSe Function, ProSe Application Server, and a box for 'Verify the Application Level Container'. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server interacts with the 'Verify the Application Level Container' box. The ProSe Application Server then sends a PXA message to the ProSe Function. The ProSe Function then interacts with a box for 'Verify PDUID and notify the originating UE'.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: Verify the Application Level Container
+    Note left of ProSe Function: Verify PDUID and notify the originating UE
+    ProSe Function->>ProSe Application Server: PXR
+    ProSe Application Server->>Note right of ProSe Application Server: 
+    Note right of ProSe Application Server-->>ProSe Application Server: 
+    ProSe Application Server->>ProSe Function: PXA
+    ProSe Function->>Note left of ProSe Function: 
+    Note left of ProSe Function-->>ProSe Function: 
+```
+
+Sequence diagram for Authorization for Discoveree request (model B). The diagram shows three lifelines: ProSe Function, ProSe Application Server, and a box for 'Verify the Application Level Container'. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server interacts with the 'Verify the Application Level Container' box. The ProSe Application Server then sends a PXA message to the ProSe Function. The ProSe Function then interacts with a box for 'Verify PDUID and notify the originating UE'.
+
+**Figure A.2.7: Authorization for Discoveree request**
+
+1. When the ProSe Function have received a discoveree request as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for restricted ProSe direct discovery model B discoveree operation, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.8.
+2. The ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.8.
+4. The ProSeF unction verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.8 Authorization for Discoverer Request (model B)
+
+This authorization for discoverer procedure is used by the ProSe Function serving the Discoverer UE to obtain authorization information of the Discoverer UE related to Discoverer Request in restricted ProSe Direct Discovery.
+
+![Sequence diagram for Figure A.2.8: Authorization for Discoverer request. Lifelines: ProSe Function, ProSe Application Server. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server calls 'Verify the Application Level Container'. It then sends a PXA message back to the ProSe Function. The ProSe Function calls 'Verify PDUID and notify the originating UE'.](b5335262987c819d7f71ce40f99cb71b_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: Verify the Application Level Container
+    ProSe Function->>ProSe Application Server: PXR
+    ProSe Application Server-->>ProSe Function: PXA
+    Note left of ProSe Function: Verify PDUID and notify the originating UE
+```
+
+Sequence diagram for Figure A.2.8: Authorization for Discoverer request. Lifelines: ProSe Function, ProSe Application Server. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server calls 'Verify the Application Level Container'. It then sends a PXA message back to the ProSe Function. The ProSe Function calls 'Verify PDUID and notify the originating UE'.
+
+**Figure A.2. 8: Authorization for Discoverer request**
+
+1. When the ProSe Function have received a discoverer request as defined in 3GPP TS 24.334 [10], from the origination UE and the application represented by the Application ID is authorized for restricted ProSe direct discovery model B discoverer operation, t he ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.9.
+2. The ProSe Application Server shall examine the Application-Data AVP and determine which target RPAUID(s) the requesting RPAUID is allowed to discover based on application-specific permissions.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.9.
+4. The ProSe Function verifies that the received PDUID belongs to the originating UE and sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.9 Authorization for Discovery Permission (model B)
+
+The discovery permission authorization procedure is used by the ProSe Function to verify the application layer permission for restricted discovery model B between an originating application user and a target application user, which are represented, respectively, by the requesting RPAUID and the target RPAUID.
+
+![Sequence diagram for Figure A.2.9: Authorization for discovery permission procedure. Lifelines: ProSe Function, ProSe Application Server. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server calls 'Verify the originating UE'. It then sends a PXA message back to the ProSe Function. The ProSe Function calls 'Notify the ProSe Function originating UE'.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: Verify the originating UE
+    ProSe Function->>ProSe Application Server: PXR
+    ProSe Application Server-->>ProSe Function: PXA
+    Note left of ProSe Function: Notify the ProSe Function originating UE
+```
+
+Sequence diagram for Figure A.2.9: Authorization for discovery permission procedure. Lifelines: ProSe Function, ProSe Application Server. The ProSe Function sends a PXR message to the ProSe Application Server. The ProSe Application Server calls 'Verify the originating UE'. It then sends a PXA message back to the ProSe Function. The ProSe Function calls 'Notify the ProSe Function originating UE'.
+
+**Figure A.2.9: Authorization for discovery permission procedure**
+
+1. When the ProSe Function have received a discovery request as defined in 3GPP TS 29.345 [7], from the ProSe Function of the originating UE and the ProSe Restricted Code has been retrieved. The ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.10.
+2. The ProSe Application Server shall determine whether the originating UE is allowed to discover the targeted UE.
+- 3 The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.2.10.
+4. The ProSe Function sends a response message to the ProSe Function of the originating UE as defined in 3GPP TS 29.345 [7].
+
+### A.2.10 Discovery Authorization Update
+
+The discovery authorization update procedure is used by ProSe Application Server to revoke discovery permissions without a delay while a specific originating user revokes the discovery permissions relating to some other users in the ProSe Application Server.
+
+![Sequence diagram for Discovery authorization update showing interactions between ProSe Function and ProSe Application Server.](a1890b9a9b85f13e67ed59bbad623659_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ProSe Application Server
+    participant ProSe Function
+    Note left of ProSe Function: 3. Determine to trigger update procedure to the affected UE
+    ProSe Application Server->>ProSe Function: 1. XAR
+    ProSe Function-->>ProSe Application Server: 2. XAA
+    Note left of ProSe Function: 3. Determine to trigger update procedure to the affected UE
+    ProSe Function->>ProSe Application Server: 4. PXR
+    ProSe Application Server-->>ProSe Function: 5. PXA
+  
+```
+
+Sequence diagram for Discovery authorization update showing interactions between ProSe Function and ProSe Application Server.
+
+Figure A.2.10: Discovery authorization update
+
+1. When the ProSe Application Server has received authorization update request from the UE, the ProSe Application Server sends a XAR command to the ProSe Function including the parameters as defined in subclause 5.2.11;
+2. The ProSe Function acknowledges the XAR command and sends the XAA command to the ProSe Application Server including the parameters as defined in subclause 5.2.11.
+3. The ProSe Function determines to trigger the discovery update procedure to the affected UE(s) based on the received update information from the ProSe Application.
+4. After a time configured by the operator, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.2.11 for reporting the authorization update result.
+5. The ProSe Application Server acknowledges the PXR Command and sends the PXA command back to the ProSe Function.
+
+### A.2.11 Authorization for Open Discovery Announce Request with Application-controlled extension
+
+The announce authorization procedure with application-controlled extension is used by the ProSe Function serving the originating UE to obtain announce authorization information related to open ProSe direct discovery.
+
+![Sequence diagram for Figure A.2.11: Authorization for open discovery announce request with application-controlled extension procedure. The diagram shows four steps: 1. PXR from ProSe Function to ProSe Application Server; 2. Check application capability within ProSe Application Server; 3. PXA from ProSe Application Server to ProSe Function; 4. notify the originating UE from ProSe Function.](6e15fc9ea763541c5913d26f85072ae1_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2. Check application capability
+    Note left of ProSe Function: 4. notify the originating UE
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 3. PXA
+```
+
+Sequence diagram for Figure A.2.11: Authorization for open discovery announce request with application-controlled extension procedure. The diagram shows four steps: 1. PXR from ProSe Function to ProSe Application Server; 2. Check application capability within ProSe Application Server; 3. PXA from ProSe Application Server to ProSe Function; 4. notify the originating UE from ProSe Function.
+
+**Figure A.2.11: Authorization for open discovery announce request with application-controlled extension procedure**
+
+1. When the ProSe Function has received an announce request with application-controlled extension, as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for open ProSe direct discovery announcing, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.3.1.
+2. The ProSe Application Server shall check if the application supports application-controlled extension and allocate ProSe Application Code suffix(es).
+3. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.3.1.
+4. The ProSe Function sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+### A.2.12 Authorization for Open Discovery Monitor Request with Application-controlled extension
+
+The authorization for monitor request with application-controlled extension procedure is used by the ProSe Function serving the originating UE to obtain monitor authorization information related to open ProSe direct discovery with application-controlled extension.
+
+![Sequence diagram showing the authorization for open discovery monitor request with application-controlled extension procedure. The diagram involves three lifelines: ProSe Function, ProSe Application Server, and the originating UE. The sequence of messages is: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the Application Data (internal message on the ProSe Application Server lifeline); 3. PXA from ProSe Application Server to ProSe Function; 4. notify the originating UE (internal message on the ProSe Function lifeline).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg)
+
+```
+sequenceDiagram
+    participant ProSe Function
+    participant ProSe Application Server
+    Note right of ProSe Application Server: 2. Verify the Application Data
+    Note left of ProSe Function: 4. notify the originating UE
+    ProSe Function->>ProSe Application Server: 1. PXR
+    ProSe Application Server-->>ProSe Function: 3. PXA
+```
+
+Sequence diagram showing the authorization for open discovery monitor request with application-controlled extension procedure. The diagram involves three lifelines: ProSe Function, ProSe Application Server, and the originating UE. The sequence of messages is: 1. PXR from ProSe Function to ProSe Application Server; 2. Verify the Application Data (internal message on the ProSe Application Server lifeline); 3. PXA from ProSe Application Server to ProSe Function; 4. notify the originating UE (internal message on the ProSe Function lifeline).
+
+**Figure A.2.12: Authorization for open discovery monitor request with application-controlled extension procedure**
+
+1. When the ProSe Function has received a monitor request with application-controlled extension as defined in 3GPP TS 24.334 [10], from the originating UE and the application represented by the Application ID is authorized for open ProSe direct discovery monitoring, the ProSe Function sends a PXR command to the ProSe Application Server including the parameters as defined in subclause 5.3.2.
+2. The ProSe Application Server shall check if the application supports application-controlled extension and examine the Application-Data AVP and determine the suffix masks to be used to monitor the information represented by the Application Data.
+3. The ProSe Application Server sends a PXA command to the ProSe Function including the parameters as defined in subclause 5.3.2.
+4. The ProSe Function sends a response message to the originating UE as defined in 3GPP TS 24.334 [10].
+
+# Annex B (normative): Diameter load control mechanism
+
+## B.1 General
+
+IETF RFC 8583 [11] specifies the Diameter load control mechanism. This includes the definition of Diameter Load AVP and the Diameter load related behaviour.
+
+The Diameter load control mechanism on the PC2 interface is optional for the ProSe Function and the ProSe Application Server.
+
+NOTE: The Diameter Load AVP will simply be ignored by peers not supporting Diameter load control.
+
+If the ProSe Function and the ProSe Application Server support the Diameter load control mechanism, they shall apply the procedures in the present Annex.
+
+## B.2 ProSe Function behaviour
+
+The ProSe Function shall act as a reacting node as defined in IETF RFC 8583 [11] and may use the load information in an implementation dependent manner, e.g. when deciding where to route requests for new Diameter sessions.
+
+## B.3 ProSe Application Server behaviour
+
+The ProSe Application Server shall act as endpoint reporting node as defined IETF RFC 8583 [11]. The ProSe Application Server shall include load information in the the Load AVP within ProXimity-Action-Answer messages.
+
+When and in which frequency to include the Load AVP is implementation dependent and based on operator policy.
+
+How the ProSe Application Server determines the specific contents of the Load-Value AVP within the Load AVP is implementation dependent and based on operator policy.
+
+# Annex C (informative): Change history
+
+| Change history |        |           |          |     |                                                                           |                                                                                                |        |        |
+|----------------|--------|-----------|----------|-----|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.  | CR       | Rev | Subject/Comment                                                           |                                                                                                | Old    | New    |
+| 2014-09        |        | CP-140557 |          |     | Raised to v.12.0.0 following one-step-approval                            |                                                                                                | 1.0.0  | 12.0.0 |
+| 2014-12        | CT-66  | CP-140921 | 000<br>1 | 1   | Resource allocation of PC2 Diameter protocol                              |                                                                                                | 12.0.0 | 12.1.0 |
+| 2015-03        | CT-67  | CP-150116 | 000<br>2 | 1   | Roaming applicability in EPC-level ProSe discovery                        |                                                                                                | 12.1.0 | 12.2.0 |
+| 2015-09        | CT-69  | CP-150474 | 000<br>8 | -   | Correction to the PXR command                                             |                                                                                                | 12.2.0 | 12.3.0 |
+| 2015-09        | CT-69  | CP-150481 | 000<br>4 | 1   | Addition of ProSe discovery authorization for restricted discovery        |                                                                                                | 12.3.0 | 13.0.0 |
+| 2015-09        | CT-69  | CP-150481 | 000<br>5 | 1   | Add functional description on Rel-13 eProSe-Ext features                  |                                                                                                | 12.3.0 | 13.0.0 |
+| 2015-09        | CT-69  | CP-150481 | 000<br>6 | 3   | General introduction to restricted ProSe direct discovery                 |                                                                                                | 12.3.0 | 13.0.0 |
+| 2015-12        | CT-70  | CP-150633 | 000<br>9 | 1   | Support multiple PDUIDs in response of the announce request authorization |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>0 |     | Correction of UE definitions for restricted discovery                     |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>1 | 2   | Call flows for authorization in Model A                                   |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>2 | 2   | Call flows for authorization in Model B                                   |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>3 | 1   | Call flow for match report in Model A/Model B                             |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>5 | 2   | Call flow for discovery authorization update                              |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>6 | 2   | Addition of ProSe discovery authorization update for restricted discovery |                                                                                                | 13.0.0 | 13.1.0 |
+| 2015-12        | CT-70  | CP-150633 | 001<br>7 | 3   | Invalid Application Data AVP Failure                                      |                                                                                                | 13.0.0 | 13.1.0 |
+| Change history |        |           |          |     |                                                                           |                                                                                                |        |        |
+| Date           | TSG #  | TSG Doc.  | CR       | Rev | Cat                                                                       | Subject/Comment                                                                                | Old    | New    |
+| 2016-03        | CT#71  | CP-160092 | 0018     | 2   | F                                                                         | Metadata indicator for restricted discovery monitor request procedure                          |        | 13.2.0 |
+| 2016-03        | CT#71  | CP-160092 | 0019     | 1   | F                                                                         | Open discovery procedures in PC2 interface for application-controlled extension                |        | 13.2.0 |
+| 2016-03        | CT#71  | CP-160092 | 0020     | 1   | F                                                                         | Correction to wrong Experimental-Result-Code values for PC2 interface                          |        | 13.2.0 |
+| 2016-06        | CT#72  | CP-160254 | 0021     | 3   | F                                                                         | Add command code and application ID for PC2 protocol                                           |        | 13.3.0 |
+| 2016-06        | CT#72  | CP-160254 | 0022     | -   | F                                                                         | Successfully authenticated Targeted RPAUIDs for restricted discovery monitor request procedure |        | 13.3.0 |
+| 2016-06        | CT#72  | CP-160254 | 0023     | 1   | F                                                                         | Reuse AVPs defined in PC6/PC7 interface                                                        |        | 13.3.0 |
+| 2016-06        | CT#72  | CP-160254 | 0024     | 1   | F                                                                         | Inconsistency about the ProSe discovery support in PC2 interface                               |        | 13.3.0 |
+| 2016-09        | CT#73  | CP-160454 | 0025     | 1   | F                                                                         | Correction of the inconsistent AVP definition                                                  |        | 13.4.0 |
+| 2016-12        | CT#74  | CP-160615 | 0026     | -   | B                                                                         | Diameter Load Control Mechanism                                                                |        | 14.0.0 |
+| 2017-03        | CT#75  | CP-170076 | 0027     | 1   | F                                                                         | Update of reference for the Diameter base protocol                                             |        | 14.1.0 |
+| 2017-06        | CT#76  | CP-171119 | 0028     | 3   | F                                                                         | Reference update for draft-ietf-dime-load                                                      |        | 14.2.0 |
+| 2018-06        | CT#80  |           |          |     |                                                                           | Automatic upgrade from previous Release                                                        |        | 15.0.0 |
+| 2019-09        | CT#85  | CP-192154 | 0030     | 1   | A                                                                         | draft-ietf-dime-load published as RFC 8583                                                     |        | 15.1.0 |
+| 2020-06        | CT#88e | CP-201246 | 0031     | 1   | F                                                                         | Correct open ProSe direct discovery                                                            |        | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29344/raw.md b/marked/Rel-16/29_series/29344/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f8e59c8bfef394c9baa625a09f8514b174e4945
--- /dev/null
+++ b/marked/Rel-16/29_series/29344/raw.md
@@ -0,0 +1,1179 @@
+
+
+
+
+Error! No  
+text of
+
+Error! No text of specified style in  
+document.
+
+# Contents
+
+|                                                                       |    |
+|-----------------------------------------------------------------------|----|
+| Foreword .....                                                        | 5  |
+| 1 Scope.....                                                          | 6  |
+| 2 References.....                                                     | 6  |
+| 3 Definitions, symbols and abbreviations .....                        | 7  |
+| 3.1 Definitions.....                                                  | 7  |
+| 3.2 Abbreviations .....                                               | 7  |
+| 4 General Description .....                                           | 7  |
+| 4.1 Introduction .....                                                | 7  |
+| 5 Procedure Descriptions .....                                        | 7  |
+| 5.1 Introduction .....                                                | 7  |
+| 5.2 ProSe Subscriber Information Retrieval .....                      | 8  |
+| 5.2.1 General .....                                                   | 8  |
+| 5.2.2 Detailed Behaviour of the ProSe Function.....                   | 8  |
+| 5.2.3 Detailed Behaviour of the HSS .....                             | 9  |
+| 5.3 Update ProSe Subscriber Data .....                                | 9  |
+| 5.3.1 General .....                                                   | 9  |
+| 5.3.2 Detailed behaviour of the ProSe Function.....                   | 10 |
+| 5.3.3 Detailed behaviour of the HSS .....                             | 11 |
+| 5.4 Notification Procedure .....                                      | 11 |
+| 5.4.1 General .....                                                   | 11 |
+| 5.4.2 Detailed Behaviour of the ProSe Function.....                   | 12 |
+| 5.4.3 Detailed Behaviour of the HSS .....                             | 12 |
+| 5.5 Reset.....                                                        | 13 |
+| 5.5.1 General .....                                                   | 13 |
+| 5.5.2 Detailed behaviour of the ProSe Function.....                   | 13 |
+| 5.5.3 Detailed behaviour of the HSS .....                             | 14 |
+| 5.6 Initial Location Information Retrieval .....                      | 14 |
+| 5.6.1 General .....                                                   | 14 |
+| 5.6.2 Detailed Behaviour of the ProSe Function.....                   | 15 |
+| 5.6.3 Detailed Behaviour of the HSS .....                             | 15 |
+| 6 Protocol Specification and Implementations .....                    | 16 |
+| 6.1 Introduction .....                                                | 16 |
+| 6.1.1 Use of Diameter Base Protocol .....                             | 16 |
+| 6.1.2 Securing Diameter Messages .....                                | 16 |
+| 6.1.3 Accounting Functionality .....                                  | 16 |
+| 6.1.4 Use of Sessions.....                                            | 16 |
+| 6.1.5 Transport Protocol.....                                         | 16 |
+| 6.1.6 Routing Considerations .....                                    | 16 |
+| 6.1.7 Advertising Application Support.....                            | 17 |
+| 6.1.8 Diameter Application Identifier.....                            | 17 |
+| 6.1.9 Use of the Supported-Features AVP .....                         | 17 |
+| 6.2 Commands.....                                                     | 17 |
+| 6.2.1 Introduction .....                                              | 17 |
+| 6.2.2 Command-Code Values.....                                        | 17 |
+| 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command.....         | 18 |
+| 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command .....         | 18 |
+| 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command .....        | 19 |
+| 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command .....         | 19 |
+| 6.2.7 ProSe-Notify-Request (PNR) Command .....                        | 20 |
+| 6.2.8 ProSe-Notify-Answer (PNA) Command.....                          | 20 |
+| 6.2.9 Reset-Request (RSR) Command .....                               | 20 |
+| 6.2.10 Reset-Answer (RSA) Command .....                               | 21 |
+| 6.2.11 ProSe-Initial-Location-Information-Request (PSR) Command ..... | 21 |
+| 6.2.12 ProSe-Initial-Location-Information-Answer (PSA) Command .....  | 21 |
+| 6.3 AVPs .....                                                        | 22 |
+
+|                                                                       |                                                          |           |
+|-----------------------------------------------------------------------|----------------------------------------------------------|-----------|
+| 6.3.1                                                                 | General .....                                            | 22        |
+| 6.3.2                                                                 | ProSe-Subscription-Data .....                            | 23        |
+| 6.3.3                                                                 | ProSe-Permission .....                                   | 23        |
+| 6.3.4                                                                 | ProSe-Allowed-PLMN .....                                 | 24        |
+| 6.3.5                                                                 | ProSe-Direct-Allowed .....                               | 24        |
+| 6.3.6                                                                 | UPR-Flags .....                                          | 25        |
+| 6.3.7                                                                 | PNR-Flags .....                                          | 25        |
+| 6.3.8                                                                 | Feature-List AVP for the PC4a application.....           | 26        |
+| 6.3.9                                                                 | ProSe-Initial-Location-Information.....                  | 26        |
+| 6.3.10                                                                | MME-Name.....                                            | 27        |
+| 6.3.11                                                                | OC-Supported-Features .....                              | 27        |
+| 6.3.12                                                                | OC-OLR .....                                             | 27        |
+| 6.3.13                                                                | Authorized-Discovery-Range.....                          | 27        |
+| 6.3.14                                                                | DRMP.....                                                | 27        |
+| 6.3.15                                                                | Load.....                                                | 27        |
+| 6.4                                                                   | Result-Code AVP and Experimental-Result AVP Values ..... | 27        |
+| 6.4.1                                                                 | General .....                                            | 27        |
+| 6.4.2                                                                 | Success .....                                            | 27        |
+| 6.4.3                                                                 | Permanent Failures .....                                 | 27        |
+| 6.4.3.1                                                               | General.....                                             | 27        |
+| 6.4.3.2                                                               | DIAMETER_ERROR_USER_UNKNOWN (5001) .....                 | 28        |
+| 6.4.3.3                                                               | DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION (5610).....    | 28        |
+| 6.4.3.4                                                               | DIAMETER_ERROR_PROSE_NOT_ALLOWED (5611) .....            | 28        |
+| 6.4.3.5                                                               | DIAMETER_ERROR_UE_LOCATION_UNKNOWN (5612).....           | 28        |
+| <b>Annex A (normative): Diameter overload control mechanism .....</b> |                                                          | <b>29</b> |
+| A.1                                                                   | General .....                                            | 29        |
+| A.2                                                                   | HSS behaviour.....                                       | 29        |
+| A.3                                                                   | ProSe Function behaviour .....                           | 29        |
+| <b>Annex B (Informative): Diameter overload node behaviour .....</b>  |                                                          | <b>29</b> |
+| B.1                                                                   | Message prioritization .....                             | 29        |
+| <b>Annex C (normative): Diameter message priority mechanism.....</b>  |                                                          | <b>30</b> |
+| C.1                                                                   | General .....                                            | 30        |
+| C.2                                                                   | PC4a interface .....                                     | 30        |
+| C.2.1                                                                 | General .....                                            | 30        |
+| C.2.2                                                                 | HSS and ProSe Function behaviour .....                   | 30        |
+| <b>Annex D (normative): Diameter load control mechanism .....</b>     |                                                          | <b>31</b> |
+| D.1                                                                   | General .....                                            | 31        |
+| D.2                                                                   | HSS behaviour.....                                       | 31        |
+| D.3                                                                   | ProSe Function behaviour .....                           | 31        |
+| Annex E (informative): Change history .....                           |                                                          | 31        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document describes the Diameter-based PC4a interface between the Proximity-based Services (ProSe) Function and the Home Subscriber Server (HSS) defined for ProSe.
+
+This specification defines the Diameter application for PC4a reference point between the ProSe Function and the HSS. The interactions between the ProSe Function and the HSS are specified.
+
+The stage 2 description for Proximity-based Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [2].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.303: "Proximity based services; Stage 2".
+- [3] Void.
+- [4] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
+- [5] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
+- [7] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [8] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
+- [9] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements".
+- [10] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol".
+- [11] 3GPP TS 23.007: "Restoration procedures".
+- [12] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol".
+- [13] void
+- [14] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS".
+- [15] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [16] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
+- [17] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO); Stage 3".
+- [18] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
+
+- [19] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging".
+- [20] 3GPP TS 32.298: "Charging Management; CDR parameter description".
+- [21] IETF RFC 7944: "Diameter Routing Message Priority".
+- [22] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [23] IETF RFC 6733: "Diameter Base Protocol".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                                    |
+|-------|------------------------------------|
+| DRMP  | Diameter Routing Message Priority  |
+| DSCP  | Differentiated Services Code Point |
+| ProSe | Proximity-based Services           |
+
+# --- 4 General Description
+
+## 4.1 Introduction
+
+The PC4a reference point between the ProSe Function and the HSS is defined in the 3GPP TS 23.303 [2].
+
+This document describes the PC4a interface related procedures, message parameters and protocol specifications.
+
+The PC4a interface allows the ProSe Function to retrieve ProSe related subscription data in order to authorise access from the UE for ProSe.
+
+# --- 5 Procedure Descriptions
+
+## 5.1 Introduction
+
+This clause describes the Diameter-based PC4a interface related procedures and information elements exchanged between the ProSe Function and the HSS.
+
+In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [9].
+
+## 5.2 ProSe Subscriber Information Retrieval
+
+### 5.2.1 General
+
+This procedure shall be used between the ProSe Function and the HSS for authorization of the UE for ProSe. The procedure shall be invoked by the ProSe Function and is used:
+
+- to request ProSe related subscription data.
+
+This procedure is mapped to the commands ProSe-Subscriber-Information-Request/Answer (PIR/PIA) in the Diameter application specified in clause 6. Tables 5.2.1-1 and 5.2.1-2 detail the involved information elements.
+
+**Table 5.2.1-1: ProSe Subscriber Information Retrieval Request**
+
+| Information Element Name                    | Mapping to Diameter AVP            | Cat. | Description                                                                                                  |
+|---------------------------------------------|------------------------------------|------|--------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name (See IETF RFC 6733 [23]) | M    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                 | O    | If present, this information element shall contain the list of features supported by the origin host.        |
+
+**Table 5.2.1-2: ProSe Subscriber Information Retrieval Answer**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 6)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).<br>The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- Unknown ProSe Subscription<br>- ProSe Not Allowed |
+| ProSe Subscription Data (See 6.3.2)         | ProSe-Subscription-Data           | C    | This information element shall contain the ProSe Subscription Data that gives the user permission to use ProSe.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| MSISDN (See 3GPP TS 29.329 [12])            | MSISDN                            | C    | This information element shall contain the user MSISDN, formatted according to 3GPP TS 29.329 [12]. It shall be present if available.                                                                                                                                                                                                                                                                                                                                                                             |
+| Visited PLMN Id (See 3GPP TS 29.272 [10])   | Visited-PLMN-Id                   | C    | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7].<br>It shall be present if the UE is roaming in a PLMN different from the Home PLMN.                                                                                                                                                                                                                                                                                                                     |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Reset-IDs (See 3GPP TS 29.272 [10])         | Reset-ID                          | O    | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers.                                                                                                                                                                                                                                                              |
+
+### 5.2.2 Detailed Behaviour of the ProSe Function
+
+The ProSe Function shall make use of this procedure to request ProSe related subscription data.
+
+If the ProSe Function retrieved the ProSe related subscription data, the ProSe Function shall perform the authorisation for ProSe as described in the 3GPP TS 23.303 [2].
+
+### 5.2.3 Detailed Behaviour of the HSS
+
+When receiving a ProSe Subscriber Information Retrieval Request the HSS shall check if the IMSI for whom data is requested exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If the IMSI exists but there is not any ProSe subscription data for the IMSI, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION.
+
+If the UE is not allowed to use ProSe in the visited PLMN, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_PROSE\_NOT\_ALLOWED. Otherwise, the HSS shall return a Result-Code of DIAMETER\_SUCCESS and shall store ProSe Function identity (the ProSe Function identity is received within the Origin-Host AVP) and download the ProSe subscription data to the ProSe Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN.
+
+## 5.3 Update ProSe Subscriber Data
+
+### 5.3.1 General
+
+The Update ProSe Subscriber Data procedure shall be used between the ProSe Function and the HSS to update the subscriber related data downloaded by means of the ProSe Subscriber Information Retrieval operation (see clause 5.2) and stored in the ProSe Function.
+
+It shall be used to update subscriber related data in the ProSe Function due to administrative changes of the user data in the HSS, i.e. if the user was given a subscription and the subscription has changed. It shall be used at least to perform the following:
+
+- update of all of ProSe subscription data of the subscriber,
+- update of a subset of the ProSe subscription data of the subscriber,
+- deletion of the ProSe subscription data of the subscriber.
+
+The procedure will also be triggered when the VPLMN has changed.
+
+This procedure is mapped to the commands Update-ProSe-Subscriber-Data-Request/Answer (UPR/UPA) in the Diameter application specified in clause 6.
+
+Table 5.3.1-1 specifies the involved information elements for the request.
+
+Table 5.3.1-2 specifies the involved information elements for the answer.
+
+**Table 5.3.1-1: Update ProSe Subscriber Data Request**
+
+| Information element name                     | Mapping to Diameter AVP             | Cat. | Description                                                                                                                                                                                                                                          |
+|----------------------------------------------|-------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMSI                                         | User-Name (See IETF RFC 673 3 [23]) | M    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2.                                                                                                                                         |
+| Supported Features (See 3GPP TS 29.2 29 [6]) | Supported-Features                  | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                |
+| ProSe Subscription Data (See 6.3.2)          | ProSe-Subscription-Data             | C    | This information element shall contain the ProSe Subscription Data that gives the user permission to use ProSe.                                                                                                                                      |
+| Visited PLMN Id (See 3GPP TS 29.2 72 [10])   | Visited-PLMN-Id                     | C    | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7]. It shall be present if the UE is roaming in a PLMN different from the Home PLMN.                                                           |
+| UPR Flags                                    | UPR-Flags                           | M    | This Information Element shall contain a bit mask. See clause 6.3.6 for the meaning of the bits.                                                                                                                                                     |
+| Reset-IDs (See 3GPP TS 29.2 72 [10])         | Reset-ID                            | O    | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. |
+
+**Table 5.3.1-2: Update ProSe Subscriber Data Answer**
+
+| Information element name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                                   |
+| Result (See 6.4)                            | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).<br>The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable in this case:<br>- User Unknown<br>- Unknown ProSe Subscription |
+
+### 5.3.2 Detailed behaviour of the ProSe Function
+
+When receiving a Update ProSe Subscriber Data request, the ProSe Function shall check whether the IMSI is known.
+
+If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If it is known, the ProSe Function shall update the corresponding data according to the indication as sent in the request, and acknowledge the Update ProSe Subscriber Data message by returning an Update ProSe Subscriber Data Answer. If the UPR-Flags indicates that the ProSe subscription data is to be deleted, the ProSe Function shall delete the associated ProSe UE context if it has been stored before.
+
+If the update of the subscription data succeeds in the ProSe Function, the Result-Code shall be set to DIAMETER\_SUCCESS.
+
+If the ProSe Function cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. In this case, the ProSe Function shall mark the subscription record "Subscriber data to be restored in the HSS".
+
+### 5.3.3 Detailed behaviour of the HSS
+
+The HSS shall make use of this procedure to update the relevant subscriber related data in the the ProSe Function to replace a specific part of the user data stored in the ProSe Function with the data sent.
+
+If the ProSe related subscription data is updated or revoked, the HSS sends the updated ProSe subscription data to the ProSe Function. The HSS shall include the UPR-Flags to indicate which part of the data is updated. If all of the ProSe subscription data is to be removed, the HSS shall set the "Removal of all ProSe Subscription Data" bit of the UPR-Flags, and the HSS shall delete the ProSe Function Identity if it is stored for this subscriber.
+
+## 5.4 Notification Procedure
+
+### 5.4.1 General
+
+This procedure shall be used between the ProSe Function and the HSS when the HSS needs to be notified about:
+
+- revocation of authorization for ProSe direct service on one PLMN.
+- removal of the subscription data from the ProSe Function either by an MMI interaction or automatically.
+
+This procedure is mapped to the commands ProSe-Notify-Request/Answer (PNR/PNA) in the Diameter application specified in clause 6. Tables 5.4.1-1 and 5.4.1-2 detail the involved information elements.
+
+**Table 5.4.1-1: ProSe Notify Request**
+
+| Information Element Name                    | Mapping to Diameter AVP            | Cat. | Description                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name (See IETF RFC 6733 [23]) | C    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. It shall be present if the revocation is for a specific UE.                                                                                                          |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                 | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                             |
+| PLMN ID (see 3GPP TS 29.272 [10])           | Visited-PLMN-Id                    | C    | This information element shall contain the MCC and the MNC of the PLMN where the UE's authorization for ProSe direct service is revoked, see 3GPP TS 23.003 [7]. It shall be present if the ProSe Function revokes the authorization for ProSe direct service in a specific PLMN. |
+| PNR Flags (see 6.3.7)                       | PNR-Flags                          | C    | This Information Element shall contain a bit mask. See 6.3.7 for the meaning of the bits.                                                                                                                                                                                         |
+
+**Table 5.4.1-2: ProSe Notify Answer**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|---------------------------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 6)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable:<br>- User Unknown<br>- Unknown ProSe Subscription |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                             |
+
+### 5.4.2 Detailed Behaviour of the ProSe Function
+
+The ProSe Function shall make use of this procedure to revoke authorization for ProSe direct service.
+
+The ProSe Function shall make use of this procedure to inform the HSS when the subscription data is deleted from the ProSe Function database due to MMI interaction or automatically.
+
+The ProSe Function shall send the updated ProSe Permission and the PLMN ID for which the ProSe Permission is to be updated. If the revocation is for a single UE in the indicated PLMN, the ProSe Function shall include IMSI in the request.
+
+### 5.4.3 Detailed Behaviour of the HSS
+
+When receiving a ProSe Notify Request the HSS shall check if the IMSI, if present in the message, exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If the IMSI exists but there is not any ProSe subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION.
+
+If the PNR-Flags indicates revocation of authorization for ProSe direct service, and
+
+- if the IMSI exists and there is ProSe subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall revoke ProSe direct service as indicated by the PNR Flags received in the request on that PLMN for the user and update the ProSe Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS.
+
+- if IMSI is not present in the message, the HSS shall check if there are any users subscribed to ProSe subscription for the PLMN as indicated by the Visited-PLMN-Id AVP in the request, and if yes, revoke ProSe direct service as indicated by the PNR Flags received in the request on that PLMN for all the impacted users and update their ProSe Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS.
+
+If the PNR Flags indicates the subscription data is deleted from the ProSe Function, the HSS shall remove the ProSe Function Identity for the subscriber and set the result code to DIAMETER\_SUCCESS.
+
+For any other reasons if the HSS cannot fulfil the received request, e.g. due to a database error, it shall set the result code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+## 5.5 Reset
+
+### 5.5.1 General
+
+The Reset Procedure shall be used by the HSS, after a restart, to indicate to the ProSe Function that a failure has occurred.
+
+The Reset Procedure may also be used by the HSS as part of operation and maintenance actions e.g. to allow planned HSS outage without service interruption.
+
+This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the Diameter application specified in clause 6.
+
+Table 5.5.1-1 specifies the involved information elements for the request.
+
+Table 5.5.1-2 specifies the involved information elements for the answer.
+
+**Table 5.5.1-1: Reset Request**
+
+| Information element name                        | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                                                                                                                                                                                                              |
+|-------------------------------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Id List<br>(See 3GPP TS 29.2 72 [10])      | User-Id                 | O    | This IE shall contain a list of ProSe User-Ids where a ProSe User-Id comprises the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN) and it shall identify the set of subscribers whose IMSIs begin with the User-Id. The HSS may include this information element if the occurred failure is limited to subscribers identified by one or more User-Ids. |
+| Supported Features<br>(See 3GPP TS 29.2 29 [6]) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                    |
+| Reset-IDs<br>(See 3GPP TS 29.2 72 [10])         | Reset-ID                | O    | If present, this information element identifies together with the HSS's realm the set of impacted subscribers.                                                                                                                                                                                                                                                           |
+
+**Table 5.5.1-2: Reset Answer**
+
+| Information element name                        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|-------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features<br>(See 3GPP TS 29.2 29 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                   |
+| Result<br>(See 6.4)                             | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).<br>The Experimental-Result AVP shall be used for PC4a errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>There are no Experimental-Result codes applicable for this command. |
+
+### 5.5.2 Detailed behaviour of the ProSe Function
+
+When receiving a Reset message the ProSe Function shall mark all impacted subscriber records "Subscriber DataConfirmed in HSS" as "Not Confirmed", as defined in 3GPP TS 23.007 [11]. If the Reset-IDs IE is supported and received, the ProSe Function shall make use of the Reset-IDs (together with the HSS's realm) in order to determine which subscriber records are impacted (i.e. check whether at least one received Reset-ID is associated with the subscriber, and the HSS's realm identity received in the Origin-Realm AVP matches the value stored after successful ProSe-Subscriber-Information retrieval); otherwise the ProSe Function shall make use of the HSS Identity received in the Origin-Host AVP (by comparing it with the value stored after successful ProSe-Subscriber-Information retrieval) and may make use of the received User-Id-List (if any) in order to determine which subscriber records are impacted.
+
+### 5.5.3 Detailed behaviour of the HSS
+
+The HSS shall make use of this procedure in order to indicate to all relevant ProSe Functions that the HSS has restarted and may have lost the current ProSe Function Identity of some of its subscribers who may be currently roaming in the ProSe Function Area and that the HSS, therefore, cannot send an Update ProSe Subscriber Data messages when needed.
+
+If the Reset-ID feature is not supported by the ProSe Function and the HSS, the HSS may include a list of User Ids identifying a subset of subscribers served by the HSS, if the occurred failure is limited to those subscribers.
+
+If the Reset-ID feature is supported by the ProSe Function, the HSS optionally may include one (or several) Reset-ID AVPs identifying e.g. failed hardware components if the occurred failure is limited to those subscribers associated with e.g. the identified failed hardware components.
+
+## 5.6 Initial Location Information Retrieval
+
+### 5.6.1 General
+
+This procedure shall be used between the ProSe Function and the HSS for retrieving the initial location information of the UE for EPC-level ProSe discovery. The procedure shall be invoked by the ProSe Function and is used:
+
+- to request the initial location information of the UE.
+
+This procedure is mapped to the commands ProSe-Initial-Location-Information-Request/Answer (PLR/PLA) in the Diameter application specified in clause 6.
+
+Table 5.4.1/1 specifies the involved information elements for the request.
+
+Table 5.4.1/2 specifies the involved information elements for the answer.
+
+**Table 5.6.1/1: ProSe Initial Location Information Request**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                  |
+|---------------------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name (See ETF RFC 6733 [23]) | M    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [7], clause 2.2. |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.        |
+
+**Table 5.6.1/2: ProSe Initial Location Information Answer**
+
+| Information Element Name                          | Mapping to Diameter AVP                    | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+|---------------------------------------------------|--------------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result<br>(See 6)                                 | Result-Code /<br>Experimental-<br>Result   | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]).<br>The Experimental-Result AVP shall be used for PC4a errors.<br>This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- UE Location Unknown |
+| ProSe Initial Location Information<br>(See 6.3.9) | ProSe-Initial-<br>Location-<br>Information | C    | This information element shall contain the location information of the UE.                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Visited PLMN Id<br>(See 3GPP TS 29.272 [10])      | Visited-PLMN-Id                            | C    | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [7].<br>It shall be present if the UE is roaming in a PLMN different from the Home PLMN.                                                                                                                                                                                                                                                                                          |
+| Supported Features<br>(See 3GPP TS 29.229 [6])    | Supported-<br>Features                     | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                  |
+
+### 5.6.2 Detailed Behaviour of the ProSe Function
+
+To request the initial location information of the targeted UE, the ProSe Function shall include the corresponding IMSI in the user profile of the targeted user in ProSe Initial Location Information Request.
+
+NOTE: The user profile for the targeted user is stored in the ProSe Function according to clause 7.2.2.3 of 3GPP TS 24.334 [16].
+
+### 5.6.3 Detailed Behaviour of the HSS
+
+When receiving a ProSe Initial Location Information Request the HSS shall check whether the IMSI is known.
+
+If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If it is known and the MME is not the serving node currently registered in HSS for the UE, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UE\_LOCATION\_UNKNOWN. If it is known and the MME is the serving node currently registered in HSS for the UE, the HSS shall return a Result-Code of DIAMETER\_SUCCESS and provide the location information of the UE to the ProSe Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN.
+
+NOTE: When requesting the UE location via S6a, the HSS does not set the "Current Location Request" bit in the IDR-Flags in the Insert Subscriber Data Request message.
+
+# --- 6 Protocol Specification and Implementations
+
+## 6.1 Introduction
+
+### 6.1.1 Use of Diameter Base Protocol
+
+The Diameter base protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.
+
+### 6.1.2 Securing Diameter Messages
+
+For secure transport of Diameter messages, see 3GPP TS 33.210 [4]
+
+### 6.1.3 Accounting Functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the PC4a interface.
+
+### 6.1.4 Use of Sessions
+
+Between the ProSe Function and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.
+
+The Diameter base protocol specified in IETF RFC 6733 [23] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [23]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+### 6.1.5 Transport Protocol
+
+Diameter messages over the PC4a interface shall make use of SCTP, see IETF RFC 4960 [5].
+
+### 6.1.6 Routing Considerations
+
+This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
+
+The PC4a reference point is defined as an intra-operator interface, and both the ProSe Function and the HSS are located in the home PLMN of the UE that requests ProSe. If the ProSe Function knows the address/name of the HSS for a certain user, both the Destination-Realm and Destination-Host AVPs shall be present in the request. Otherwise, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by the ProSe Function.
+
+The HSS obtains the Destination-Host AVP to use in requests towards the ProSe Function, from the Origin-Host AVP received in previous requests from the ProSe Function. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the HSS.
+
+If the Vendor-Specific-Application-ID AVP is received in any of the commands, it shall be ignored by the receiving node, and it shall not be used for routing purposes.
+
+### 6.1.7 Advertising Application Support
+
+The ProSe Function and the HSS shall advertise support of the Diameter PC4a Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [23].
+
+### 6.1.8 Diameter Application Identifier
+
+The PC4a interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the PC4a interface application is 16777336 (allocated by IANA).
+
+### 6.1.9 Use of the Supported-Features AVP
+
+When new functionality is introduced on the PC4a interface, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the PC4a interface is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [6].
+
+When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+## 6.2 Commands
+
+### 6.2.1 Introduction
+
+This clause defines the Command code values and related ABNF for each command described in this specification.
+
+### 6.2.2 Command-Code Values
+
+This clause defines Command-Code values for the PC4a interface application as allocated by IANA.
+
+Every command is defined by means of the ABNF syntax IETF RFC 5234 [8], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [23]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [23] shall apply.
+
+The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
+
+NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [23].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.2.2-1: Command-Code values for PC4a**
+
+| <b>Command-Name</b>                        | <b>Abbreviation</b> | <b>Code</b> | <b>Clause</b> |
+|--------------------------------------------|---------------------|-------------|---------------|
+| ProSe-Subscriber-Information-Request       | PIR                 | 8388664     | 6.2.3         |
+| ProSe-Subscriber-Information-Answer        | PIA                 | 8388664     | 6.2.4         |
+| Update-ProSe-Subscriber-Data-Request       | UPR                 | 8388665     | 6.2.5         |
+| Update-ProSe-Subscriber-Data-Answer        | UPA                 | 8388665     | 6.2.6         |
+| ProSe-Notify-Request                       | PNR                 | 8388666     | 6.2.7         |
+| ProSe-Notify-Answer                        | PNA                 | 8388666     | 6.2.8         |
+| Reset-Request                              | RSR                 | 322         | 6.2.9         |
+| Reset-Answer                               | RSA                 | 322         | 6.2.10        |
+| ProSe-Initial-Location-Information-Request | PSR                 | 8388713     | 6.2.11        |
+| ProSe-Initial-Location-Information-Answer  | PSA                 | 8388713     | 6.2.12        |
+
+For these commands, the Application-ID field shall be set to 16777336 (application identifier of the PC4a interface application, allocated by IANA).
+
+### 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command
+
+The ProSe-Subscriber-Information-Request (PIR) command, indicated by the Command-Code field set to 8388664 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS.
+
+#### Message Format
+
+```
+< ProSe-Subscriber-Information-Request > ::= < Diameter Header: 8388664, REQ, PXY, 16777336 >
+  < Session-Id >
+  [ DRMP ]
+  [ Vendor-Specific-Application-Id ]
+  { Auth-Session-State }
+  { Origin-Host }
+  { Origin-Realm }
+  [ Destination-Host ]
+  { Destination-Realm }
+  { User-Name }
+  *[ Supported-Features ]
+  [ OC-Supported-Features ]
+  *[ AVP ]
+  *[ Proxy-Info ]
+  *[ Route-Record ]
+```
+
+### 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command
+
+The ProSe-Subscriber-Information-Answer (PIA) command, indicated by the Command-Code field set to 8388664 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function.
+
+#### Message Format
+
+```
+< ProSe-Subscriber-Information-Answer > ::= < Diameter Header: 8388664, PXY, 16777336 >
+  < Session-Id >
+  [ DRMP ]
+  [ Vendor-Specific-Application-Id ]
+  [ Result-Code ]
+  [ Experimental-Result ]
+  { Auth-Session-State }
+  { Origin-Host }
+  { Origin-Realm }
+  [ ProSe-Subscription-Data ]
+```
+
+```
+
+[ MSISDN ]
+[ Visited-PLMN-Id ]
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+*[ AVP ]
+*[ Reset-ID ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command
+
+The Update-ProSe Subscriber Data-Request (UPR) command, indicated by the Command-Code field set to 8388665 and the 'R' bit set in the Command Flags field, is sent from the HSS to the ProSe Function.
+
+Message Format when used over the PC4a application:
+
+```
+
+< Update-ProSe-Subscriber-Data-Request > ::= < Diameter Header: 8388665, REQ, PXY, 16777336 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+{ Destination-Host }
+{ Destination-Realm }
+{ User-Name }
+*[ Supported-Features ]
+[ ProSe Subscription-Data ]
+[ Visited-PLMN-Id ]
+{ UPR-Flags }
+*[ Reset-ID ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command
+
+The Update-ProSe Subscriber Data-Answer (UPA) command, indicated by the Command-Code field set to 8388665 and the 'R' bit cleared in the Command Flags field, is sent from the ProSe Function to the HSS.
+
+Message Format when used over the PC4a application:
+
+```
+
+< Update-ProSe-Subscriber-Data-Answer > ::= < Diameter Header: 8388665, PXY, 16777336 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+*[ Supported-Features ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.7 ProSe-Notify-Request (PNR) Command
+
+The ProSe-Notify-Request (PNR) command, indicated by the Command-Code field set to 8388666 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS.
+
+Message Format
+
+```
+< ProSe-Notify-Request > ::= < Diameter Header: 8388666, REQ, PXY, 16777336 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    [ User-Name ]
+    [ ProSe-Permission ]
+    [ Visited-PLMN-Id ]
+    [ PNR-Flags ]
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.8 ProSe-Notify-Answer (PNA) Command
+
+The ProSe-Notify-Answer (PNA) command, indicated by the Command-Code field set to 8388666 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function.
+
+Message Format
+
+```
+< ProSe-Notify-Answer > ::= < Diameter Header: 8388666, PXY, 16777336 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    [ OC-OLR ]
+    *[ Load ]
+    *[ AVP ]
+    [ Failed-AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.9 Reset-Request (RSR) Command
+
+The Reset-Request (RSR) command, indicated by the Command-Code field set to 322 and the 'R' bit set in the Command Flags field, is sent from HSS to the ProSe Function.
+
+Message Format when used over the PC4a application:
+
+```
+< Reset-Request > ::= < Diameter Header: 322, REQ, PXY, 16777336 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    { Origin-Host }
+```
+
+```
+
+{ Origin-Realm }
+{ Destination-Host }
+{ Destination-Realm }
+*[ Supported-Features ]
+*[ User-Id ]
+*[ Reset-ID ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.10 Reset-Answer (RSA) Command
+
+The Reset-Answer (RSA) command, indicated by the Command-Code field set to 322 and the 'R' bit cleared in the Command Flags field, is sent from ProSe Function to HSS.
+
+Message Format when used over the PC4a application:
+
+```
+
+< Reset-Answer > ::= < Diameter Header: 322, PXY, 16777336 >
+                    < Session-Id >
+                    [ DRMP ]
+                    [ Vendor-Specific-Application-Id ]
+                    *[ Supported-Features ]
+                    [ Result-Code ]
+                    [ Experimental-Result ]
+                    { Auth-Session-State }
+                    { Origin-Host }
+                    { Origin-Realm }
+                    *[ AVP ]
+                    [ Failed-AVP ]
+                    *[ Proxy-Info ]
+                    *[ Route-Record ]
+
+```
+
+### 6.2.11 ProSe-Initial-Location-Information-Request (PSR) Command
+
+The ProSe-Initial-Location-Information-Request (PSR) command, indicated by the Command-Code field set to 8388713 and the "R" bit set in the Command Flags field, is sent from the ProSe Function to the HSS.
+
+Message Format
+
+```
+
+< ProSe-Subscriber-Information-Request > ::= < Diameter Header: 8388713, REQ, PXY, 16777336 >
+                    < Session-Id >
+                    [ DRMP ]
+                    [ Vendor-Specific-Application-Id ]
+                    { Auth-Session-State }
+                    { Origin-Host }
+                    { Origin-Realm }
+                    [ Destination-Host ]
+                    { Destination-Realm }
+                    { User-Name }
+                    *[ Supported-Features ]
+                    *[ AVP ]
+                    *[ Proxy-Info ]
+                    *[ Route-Record ]
+
+```
+
+### 6.2.12 ProSe-Initial-Location-Information-Answer (PSA) Command
+
+The ProSe-Initial-Location-Information-Answer (PSA) command, indicated by the Command-Code field set to 8388713 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the ProSe Function.
+
+Message Format
+
+```
+
+< ProSe-Subscriber-Information-Answer > ::= < Diameter Header: 8388713, PXY, 16777336 >
+                    < Session-Id >
+
+```
+
+```
+
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ ProSe-Initial-Location-Information ]
+[ Visited-PLMN-Id ]
+*[ Supported-Features ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+## 6.3 AVPs
+
+### 6.3.1 General
+
+The following table specifies the Diameter AVPs defined for the PC4a interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).
+
+**Table 6.3.1-1: PC4a specific Diameter AVPs**
+
+| Attribute Name                                                                                                                                                                                                                                                                                                                                                                         | AVP Code | Clause defined | Value Type | AVP Flag rules |     |            |          |           |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------|----------------|-----|------------|----------|-----------|
+|                                                                                                                                                                                                                                                                                                                                                                                        |          |                |            | Must           | May | Should not | Must not | May Encr. |
+| ProSe-Subscription-Data                                                                                                                                                                                                                                                                                                                                                                | 3701     | 6.3.2          | Grouped    | M,V            |     |            |          | No        |
+| ProSe-Permission                                                                                                                                                                                                                                                                                                                                                                       | 3702     | 6.3.3          | Unsigned32 | M,V            |     |            |          | No        |
+| ProSe-Allowed-PLMN                                                                                                                                                                                                                                                                                                                                                                     | 3703     | 6.3.4          | Grouped    | M,V            |     |            |          | No        |
+| ProSe-Direct-Allowed                                                                                                                                                                                                                                                                                                                                                                   | 3704     | 6.3.5          | Unsigned32 | M,V            |     |            |          | No        |
+| UPR-Flags                                                                                                                                                                                                                                                                                                                                                                              | 3705     | 6.3.6          | Unsigned32 | M,V            |     |            |          | No        |
+| PNR-Flags                                                                                                                                                                                                                                                                                                                                                                              | 3706     | 6.3.7          | Unsigned32 | M,V            |     |            |          | No        |
+| ProSe-Initial-Location-Information                                                                                                                                                                                                                                                                                                                                                     | 3707     | 6.3.9          | Grouped    | M,V            |     |            |          | No        |
+| NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23].                                                                                                                              |          |                |            |                |     |            |          |           |
+| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. |          |                |            |                |     |            |          |           |
+
+The following table specifies the Diameter AVPs re-used by the PC4a interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within PC4a.
+
+Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol, do not need to be supported. The AVPs from Diameter Base Protocol are not included in table 6.3.1-2, but they may be re-used for the PC4a protocol.
+
+**Table 6.3.1-2: PC4a re-used Diameter AVPs**
+
+| Attribute Name                | Reference           | Comments                                                                                                                                                          | M-bit        |
+|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|
+| Visited-PLMN-Id               | 3GPP TS 29.272 [10] |                                                                                                                                                                   |              |
+| Supported-Features            | 3GPP TS 29.229 [6]  |                                                                                                                                                                   |              |
+| Feature-List-ID               | 3GPP TS 29.229 [6]  |                                                                                                                                                                   |              |
+| Feature-List                  | 3GPP TS 29.229 [6]  |                                                                                                                                                                   |              |
+| User-Id                       | 3GPP TS 29.272 [10] | See clause 6.3.8                                                                                                                                                  |              |
+| Reset-ID                      | 3GPP TS 29.272 [10] |                                                                                                                                                                   |              |
+| MSISDN                        | 3GPP TS 29.329 [12] |                                                                                                                                                                   |              |
+| MME-Name                      | 3GPP TS 29.173 [14] | See clause 6.3.10                                                                                                                                                 |              |
+| E-UTRAN-Cell-Global-Identity  | 3GPP TS 29.272 [10] |                                                                                                                                                                   |              |
+| Tracking-Area-Identity        | 3GPP TS 29.272 [10] |                                                                                                                                                                   |              |
+| Age-Of-Location-Information   | 3GPP TS 29.272 [10] |                                                                                                                                                                   |              |
+| 3GPP-Charging-Characteristics | 3GPP TS 29.061 [18] | See 3GPP TS 32.251 [19] Annex A and 3GPP TS 32.298 [20] clause 5.1.2.2.7. This attribute holds the ProSe-related Charging Characteristics for a ProSe subscriber. | Must set     |
+| OC-Supported-Features         | IETF RFC 7683 [15]  | See clause 6.3.11                                                                                                                                                 | Must set     |
+| OC-OLR                        | IETF RFC 7683 [15]  | See clause 6.3.12                                                                                                                                                 | Must set     |
+| DRMP                          | IETF RFC 7944 [21]  | see clause 6.3.14                                                                                                                                                 | Must not set |
+| Load                          | IETF RFC 8583 [22]  | See clause 6.3.15                                                                                                                                                 | Must not set |
+
+NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies.
+
+NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
+
+### 6.3.2 ProSe-Subscription-Data
+
+The ProSe-Subscription-Data AVP is of type Group. It shall contain the ProSe related subscription data.
+
+AVP format
+
+ProSe-Subscription-Data ::= <AVP header: 3701 10415>
+
+```
+{ ProSe-Permission }
+*[ ProSe-Allowed-PLMN ]
+[ 3GPP-Charging-Characteristics ]
+*[AVP]
+```
+
+### 6.3.3 ProSe-Permission
+
+The ProSe-Permission AVP is of type Unsigned32 and it shall contain a bit mask that indicates the permissions for ProSe subscribed by the user. The meaning of the bits shall be as defined in table 6.3.3/1:
+
+**Table 6.3.3-1: ProSe-Permission**
+
+| Bit   | Name                                                                                                      | Description                                                                                                        |
+|-------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| 0     | ProSe Direct Discovery                                                                                    | This bit, when set, indicates that the user is allowed to use ProSe Direct Discovery.                              |
+| 1     | EPC-level ProSe Discovery                                                                                 | This bit, when set, indicates that the user is allowed to use EPC-level ProSe Discovery.                           |
+| 2     | EPC support WLAN Direct Discovery and Communication                                                       | This bit, when set, indicates that the user is allowed to use EPC support WLAN Direct Discovery and Communication. |
+| 3     | one-to-many ProSe Direct Communication                                                                    | This bit, when set, indicates that the user is allowed to use one-to-many ProSe Direct Communication.              |
+| 4     | one-to-one ProSe Direct Communication                                                                     | This bit, when set, indicates that the user is allowed to use one-to-one ProSe Direct Communication.               |
+| 5     | UE-to-Network Relay                                                                                       | This bit, when set, indicates that the user is allowed to act as a UE-to-Network relay.                            |
+| 6     | Remote-UE-access                                                                                          | This bit, when set, indicates that the user is allowed to act as a Remote-UE.                                      |
+| 7     | Restricted ProSe Direct Discovery                                                                         | This bit, when set, indicates that the user is allowed to use restricted ProSe Direct Discovery.                   |
+| NOTE: | Bits not defined in this table shall be cleared by the HSS and discarded by the receiving ProSe Function. |                                                                                                                    |
+
+### 6.3.4 ProSe-Allowed-PLMN
+
+The ProSe-Allowed-PLMN AVP is of type Group. It shall contain the PLMN where the UE is authorised to announce or monitor or both for ProSe Discovery or to use ProSe direct communication.
+
+AVP format
+
+ProSe-Allowed-PLMN ::= <AVP header: 3703 10415>
+
+[ Visited-PLMN-Id ]
+
+[ Authorized-Discovery-Range ]
+
+[ ProSe-Direct-Allowed ]
+
+\*[AVP]
+
+The Authorized-Discovery-Range Information Element should only be present if the Visited-PLMN-Id is the PLMN-Id of the HPLMN; otherwise it should be absent.
+
+### 6.3.5 ProSe-Direct-Allowed
+
+The ProSe-Direct-Allowed AVP is of type Unsigned32 and it shall contain a bit mask that indicates the services the UE is authorised to use for ProSe Direct functionalities in a specific PLMN. The meaning of the bits shall be as defined in table 6.3.5-1:
+
+**Table 6.3.5-1: ProSe-Direct-Allowed**
+
+| <b>Bit</b>                                                                                                      | <b>Name</b>                      | <b>Description</b>                                                                                                                                                           |
+|-----------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                               | Announce                         | This bit, when set, indicates that the user is allowed to announce in the corresponding PLMN for open ProSe Discovery.                                                       |
+| 1                                                                                                               | Monitor                          | This bit, when set, indicates that the user is allowed to monitor in the corresponding PLMN for open ProSe Discovery.                                                        |
+| 2                                                                                                               | Communication                    | This bit, when set, indicates that the user is allowed for ProSe direct one to many communication in the corresponding PLMN.                                                 |
+| 3                                                                                                               | One-to-one Communication         | This bit, when set, indicates that the user is allowed to perform one-to-one ProSe Direct Communication.                                                                     |
+| 4                                                                                                               | Discoverer                       | This bit, when set, indicates that the user is allowed to perform discoverer operation in the corresponding PLMN for ProSe Discovery Model B.                                |
+| 5                                                                                                               | Discoveree                       | This bit, when set, indicates that the user is allowed to perform discoveree operation in the corresponding PLMN for ProSe Discovery Model B.                                |
+| 6                                                                                                               | Restricted-announce              | This bit, when set, indicates that the user is allowed to announce in the corresponding PLMN for restricted ProSe Discovery.                                                 |
+| 7                                                                                                               | Restricted-monitoring            | This bit, when set, indicates that the user is allowed to monitor in the corresponding PLMN for restricted ProSe Discovery.                                                  |
+| 8                                                                                                               | Application-controlled extension | This bit, when set, indicates that the user is allowed to announce or monitor with application-controlled extension in the corresponding PLMN for restricted ProSe Discovery |
+| 9                                                                                                               | On-demand announcing             | This bit, when set, indicates that the user is allowed to perform on-demand announcing in the corresponding PLMN for restricted ProSe Discovery                              |
+| NOTE: Bits not defined in this table shall be cleared by the HSS and discarded by the receiving ProSe Function. |                                  |                                                                                                                                                                              |
+
+### 6.3.6 UPR-Flags
+
+The UPR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 6.3.6-1:
+
+**Table 6.3.6-1: UPR-Flags**
+
+| <b>Bit</b>                                                                                                              | <b>Name</b>      | <b>Description</b>                                                                       |
+|-------------------------------------------------------------------------------------------------------------------------|------------------|------------------------------------------------------------------------------------------|
+| 0                                                                                                                       | Update           | This bit, when set, indicates that the ProSe subscriber related data are updated.        |
+| 1                                                                                                                       | Removal          | This bit, when set, indicates that all of the ProSe subscriber related data are removed. |
+| 2                                                                                                                       | Reset-ID Update  | This bit, when set, indicates that the complete list on Reset-IDs is updated.            |
+| 3                                                                                                                       | Reset-ID Removal | This bit, when set, indicates that the complete list on Reset-IDs is removed.            |
+| NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving ProSe Function. |                  |                                                                                          |
+
+### 6.3.7 PNR-Flags
+
+The PNR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.7-1:
+
+**Table 6.3.7-1: PNR-Flags**
+
+| bit                                                                                                                                                                                                                                                                           | name                         | Description                                                                                                                                 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                                                                                                                                                                                             | Direct Discovery Revoked     | This bit, when set, shall indicate to the HSS that the authorization for ProSe direct discovery is to be revoked on the indicated PLMN.     |
+| 1                                                                                                                                                                                                                                                                             | Direct Communication Revoked | This bit, when set, shall indicate to the HSS that the authorization for ProSe direct communication is to be revoked on the indicated PLMN. |
+| 2                                                                                                                                                                                                                                                                             | Purged UE                    | This bit, when set, shall indicate to the HSS that the subscriber's data has been deleted from the ProSe Function.                          |
+| NOTE 1: Bits not defined in this table shall be cleared by the sending ProSe Function and discarded by the receiving HSS.<br>NOTE 2: If Purged UE bit is set, all other bits in this table shall be cleared by the sending ProSe Function and discarded by the receiving HSS. |                              |                                                                                                                                             |
+
+### 6.3.8 Feature-List AVP for the PC4a application
+
+The syntax of this AVP is defined in 3GPP TS 29.229 [6].
+
+For the PC4a application, the meaning of the bits shall be as defined in table 6.3.8/1 for the Feature-List-ID 1.
+
+**Table 6.3.8/1: Features of Feature-List-ID 1 used in PC4a**
+
+| Feature bit                                                                                                                                                                                                                                                                                                                                          | Feature   | M/O | Description                                                                                                                                                                                                                                                                                                     |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                                                                                                                                                                                                                                                                    | Reset-IDs | O   | Support of Reset-IDs<br>This feature is applicable to the PIR/PIA and UPR/UPA and RSR/RSA command pairs over the PC4a interface.<br>If the ProSe Function indicates in the PIR command that it does not support Reset-IDs, the HSS shall not include Reset-ID AVPs in RSR commands sent to that ProSe Function. |
+| Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".<br>Feature: A short name that can be used to refer to the bit and to the feature, e.g. "ODB-HPLMN-APN".<br>M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").<br>Description: A clear textual description of the feature. |           |     |                                                                                                                                                                                                                                                                                                                 |
+
+Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message.
+
+### 6.3.9 ProSe-Initial-Location-Information
+
+The ProSe-Initial-Location-Information AVP is of type Grouped. This AVP shall contain the location information of the UE.
+
+AVP format
+
+ProSe-Initial-Location-Information ::= <AVP header: 3707 10415>
+
+[MME-Name]
+
+[E-UTRAN-Cell-Global-Identity]
+
+[Tracking-Area-Identity]
+
+[Age-Of-Location-Information]
+
+\*[AVP]
+
+### 6.3.10 MME-Name
+
+The MME-Name AVP is of type DiameterIdentity. This AVP shall contain the Diameter identity of the serving MME and is specified in 3GPP TS 29.173 [14] clause 6.4.4.
+
+### 6.3.11 OC-Supported-Features
+
+The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.12 OC-OLR
+
+The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [15]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.13 Authorized-Discovery-Range
+
+The Authorized-Discovery-Range AVP is of type Unsigned32 and it shall contain a value that indicates the authorised announcing range (short/medium/long) at which the UE is allowed to announce in the given PLMN according to the defined announcing authorisation policy for this UE. Refer to 3GPP TS 24.334 [16] for the policy handling and to 3GPP TS 24.333 [17] for the possible values of the range.
+
+### 6.3.14 DRMP
+
+The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [21]. This AVP allows the HSS and the ProSe Function to indicate the relative priority of Diameter messages over the PC4a interface. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.
+
+### 6.3.15 Load
+
+The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [22]. This AVP is used to support Diameter load control mechanism, see Annex D for more information.
+
+## 6.4 Result-Code AVP and Experimental-Result AVP Values
+
+### 6.4.1 General
+
+This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification.
+
+### 6.4.2 Success
+
+Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied.
+
+### 6.4.3 Permanent Failures
+
+#### 6.4.3.1 General
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in Diameter base protocol specified in IETF RFC 6733 [23] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+#### 6.4.3.2 DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+This result code shall be sent by the HSS to indicate that the user identified by the IMSI is unknown. This error code is defined in 3GPP TS 29.229 [6].
+
+#### 6.4.3.3 DIAMETER\_ERROR\_UNKNOWN\_PROSE\_SUBSCRIPTION (5610)
+
+This result code shall be sent by the HSS to indicate that no ProSe subscription is associated with the IMSI.
+
+#### 6.4.3.4 DIAMETER\_ERROR\_PROSE\_NOT\_ALLOWED (5611)
+
+This result code shall be sent by the HSS to indicate that ProSe is not allowed to be used in the specific PLMN where the UE is registered.
+
+#### 6.4.3.5 DIAMETER\_ERROR\_UE\_LOCATION\_UNKNOWN (5612)
+
+This result code shall be sent by the HSS to indicate that the initial location of the UE is unknown.
+
+# --- Annex A (normative): Diameter overload control mechanism
+
+## A.1 General
+
+Diameter overload control mechanism is an optional feature.
+
+IETF RFC 7683 [15] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 7683 [15] on the PC4a interface where, when applied, the ProSe Function shall behave as reacting nodes and the HSS as a reporting node.
+
+## A.2 HSS behaviour
+
+The HSS requests traffic reduction from the ProSe Function when it is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [15].
+
+The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the PC4a interface or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc.
+
+The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means.
+
+## A.3 ProSe Function behaviour
+
+The ProSe Function applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [15].
+
+The ProSe Function achieves requested traffic reduction by implementation specific means. For example, the ProSe Function may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed. As a result of the need to throttle traffic, the ProSe Function may reject Registration Request, Discovery Request, Proximity Requests initiated by UEs. The possible related error messages used over PC3 are described in the 3GPP TS 24.334 [16].
+
+# --- Annex B (Informative): Diameter overload node behaviour
+
+## B.1 Message prioritization
+
+This clause describes possible behaviours of the ProSe Function regarding message prioritisation in an informative purpose.
+
+The ProSe Function may take the following into account when making throttling decisions:
+
+- Identification of the procedures that can be deferred (e.g. Proximity Requests), so to avoid to drop non deferrable procedures;
+- Prioritisation of certain types of request (e.g. between ProSe-Subscriber-Information-Request (PIR) and ProSe-Notify-Request (PNR)) according to the context of their use, in particular:
+- Higher prioritisation for commands that are related to a registered user for a service, so to avoid the interruption of the registered service for the user.
+
+# Annex C (normative): Diameter message priority mechanism
+
+## C.1 General
+
+IETF RFC 7944 [21] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied.
+
+## C.2 PC4a interface
+
+### C.2.1 General
+
+The Diameter message priority mechanism is an optional feature.
+
+It is recommended to make use of IETF RFC 7944 [21] over the PC4a interface of an operator network when the overload control defined in Annex A is applied on this PC4a interface.
+
+### C.2.2 HSS and ProSe Function behaviour
+
+When the HSS or the ProSe Function support the Diameter message priority mechanism over the PC4a interface, the HSS or the ProSe Function shall comply with IETF RFC 7944 [21].
+
+The HSS or the ProSe Function sending a request shall determine the required priority according to its policies. When priority is required, the HSS or the ProSe Function shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level.
+
+When the HSS or the ProSe Function receive the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request.
+
+When the HSS or the ProSe Function receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, the HSS or the ProSe Function may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, the HSS or the ProSe Function shall include the DRMP AVP in the response.
+
+The HSS and the ProSe Function decisions for a required priority and for the priority level value are implementation specific.
+
+If:
+
+- the HSS and the ProSe Function supports using the Diameter message priority mechanism for DSCP marking purposes,
+- the transport network utilizes DSCP marking, and
+- message-dependant DSCP marking is possible for the protocol stack transporting Diameter,
+
+then the HSS and the ProSe Function shall set the DSCP marking for transport of the request or response according to the required priority level.
+
+Diameter requests related to high priority traffic shall contain a DRMP AVP with a high priority of which the level value is operator dependent.
+
+# Annex D (normative): Diameter load control mechanism
+
+## D.1 General
+
+Diameter load control mechanism is an optional feature.
+
+IETF RFC 8583 [22] specifies a Diameter load control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF draft-ietf-dime-load-03 [22] on the PC4a interface where, when applied, the ProSe Function shall behave as reacting node and the HSS as a reporting node.
+
+## D.2 HSS behaviour
+
+The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [22].
+
+The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the PC4a interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc.
+
+The HSS determines when to send Load AVPs of type HOST by implementation specific means.
+
+## D.3 ProSe Function behaviour
+
+When performing next hop Diameter Agent selection for requests that are routed based on realm, the ProSe Function may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [22].
+
+# Annex E (informative): Change history
+
+| Date    | TSG #     | TSG Doc.  | CR   | Rev | Subject/Comment                                              | New    |
+|---------|-----------|-----------|------|-----|--------------------------------------------------------------|--------|
+| 2014-04 | CT4#64bis |           |      |     | Implementation of C4-140706, C4-140707                       | 0.1.0  |
+| 2014-05 | CT4#65    | C4-141169 |      |     | Implementation of C4-140917, C4-141072, C4-141159, C4-141077 | 0.2.0  |
+| 2014-07 | CT4#66    | C4-141668 |      |     | Implementation of C4-141504, C4-141507, C4-141510, C4-141636 | 0.3.0  |
+| 2014-09 | CT#65     | CP-140497 |      |     | Presented for information and approval                       | 1.0.0  |
+| 2014-09 | CT#65     |           |      |     | Approved at CT#65                                            | 12.0.0 |
+| 2014-12 | CT#66     | CP-140778 | 0004 | 1   | Purge Procedure                                              | 12.1.0 |
+|         |           | CP-140778 | 0005 | 2   | MSISDN over PC4a                                             |        |
+|         |           | CP-140778 | 0006 | 2   | Reset-ID                                                     |        |
+|         |           | CP-140778 | 0007 | 3   | ProSe Initial Location Information Retrieval                 |        |
+|         |           | CP-140778 | 0008 | 2   | Update of AVP naming                                         |        |
+|         |           | CP-140778 | 0009 | 2   | Diameter Overload Control over PC4a                          |        |
+|         |           | CP-140778 | 0010 | 2   | Codes Assignment for PC4a                                    |        |
+| 2015-03 | CT#67     | CP-150028 | 0011 | 1   | Correction of references                                     | 12.2.0 |
+
+|         |        |           |      |   |                                                                         |        |
+|---------|--------|-----------|------|---|-------------------------------------------------------------------------|--------|
+|         |        | CP-150028 | 0012 | 2 | Introduction of Authorized Discovery Range Indication for announcing UE |        |
+| 2015-06 | CT#68  | CP-150257 | 0013 | 6 | Correction and Clean-up on PC4a                                         | 12.3.0 |
+|         |        | CP-150257 | 0015 | 4 | Addition of Charging Characteristics in ProSe Subscriber data for PC4a  |        |
+| 2015-12 | CT#70  | CP-150759 | 0017 | 1 | Reference to DOIC updated with IETF RFC 7683                            | 12.4.0 |
+| 2015-12 | CT#70  | CP-150760 | 0016 | 3 | Enhancements to subscription data                                       | 13.0.0 |
+| 2016-03 | CT#71  | CP-160023 | 0018 | 1 | Diameter message priority over PC4a                                     | 13.1.0 |
+| 2016-12 | CT#74  | CP-160664 | 0020 | - | Correction to change IETF drmp draft version to official RFC 7944       | 13.2.0 |
+| 2016-12 | CT#74  | CP-160681 | 0019 | 1 | Load Control                                                            | 14.0.0 |
+| 2017-03 | CT#75  | CP-170048 | 0021 | - | Update of reference for the Diameter base protocol                      | 14.1.0 |
+| 2017-03 | CT#75  | CP-170048 | 0022 | 1 | Handling of the Vendor-Specific-Application-Id AVP                      | 14.1.0 |
+| 2017-03 | CT#75  | CP-170048 | 0023 | 1 | Cardinality of the Failed-AVP AVP in answer                             | 14.1.0 |
+| 2017-06 | CT#76  | CP-171018 | 0025 | 1 | Support for signaling transport level packet marking                    | 14.2.0 |
+| 2017-09 | CT#77  | CP-172013 | 0027 | - | Correction of DRMP Procedures                                           | 14.3.0 |
+| 2018-06 | CT#80  |           |      |   | Update to Rel-15 version (MCC)                                          | 15.0.0 |
+| 2019-09 | CT#85  | CP192094  | 0029 | 1 | draft-ietf-dime-load published as RFC 8583                              | 15.1.0 |
+| 2018-06 | CT#88e |           |      |   | Update to Rel-16 version (MCC)                                          | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29345/raw.md b/marked/Rel-16/29_series/29345/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..435483ca9e021e88e639dd7142d688d00b6e7aa7
--- /dev/null
+++ b/marked/Rel-16/29_series/29345/raw.md
@@ -0,0 +1,2546 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                  |    |
+|----------------------------------------------------------------------------------|----|
+| Foreword .....                                                                   | 7  |
+| 1 Scope.....                                                                     | 8  |
+| 2 References.....                                                                | 8  |
+| 3 Definitions, symbols and abbreviations .....                                   | 9  |
+| 3.1 Definitions.....                                                             | 9  |
+| 3.2 Abbreviations .....                                                          | 9  |
+| 4 General Description .....                                                      | 10 |
+| 4.1 Introduction .....                                                           | 10 |
+| 5 Procedures Description .....                                                   | 10 |
+| 5.1 introduction .....                                                           | 10 |
+| 5.2 ProSe Service Authorization .....                                            | 10 |
+| 5.2.1 General .....                                                              | 10 |
+| 5.2.2 Detailed behaviour of the ProSe Function in the HPLMN.....                 | 11 |
+| 5.2.3 Detailed behaviour of the ProSe Function in the Local PLMN or VPLMN .....  | 12 |
+| 5.3 ProSe Direct Discovery Authorization.....                                    | 12 |
+| 5.3.1 General .....                                                              | 12 |
+| 5.3.2 Detailed behaviour of the HPLMN ProSe Function.....                        | 13 |
+| 5.3.3 Detailed behaviour of the ProSe Function in the Local PLMN or VPLMN .....  | 15 |
+| 5.4 ProSe Match Report .....                                                     | 17 |
+| 5.4.1 General .....                                                              | 17 |
+| 5.4.2 Detailed behaviour of the HPLMN ProSe Function.....                        | 18 |
+| 5.4.3 Detailed behaviour of the ProSe Function in the local PLMN.....            | 18 |
+| 5.5 ProSe Match Report info.....                                                 | 19 |
+| 5.5.1 General .....                                                              | 19 |
+| 5.5.2 Detailed behaviour of the requesting ProSe Function .....                  | 20 |
+| 5.5.3 Detailed behaviour of the receiving ProSe Function.....                    | 20 |
+| 5.6 ProSe Proximity Request .....                                                | 21 |
+| 5.6.1 General .....                                                              | 21 |
+| 5.6.2 Detailed behaviour of the ProSe Function of the requesting UE .....        | 22 |
+| 5.6.3 Detailed behaviour of the ProSe Function of the targeted UE .....          | 22 |
+| 5.7 ProSe Location Update.....                                                   | 23 |
+| 5.7.1 General .....                                                              | 23 |
+| 5.7.2 Detailed behaviour of the ProSe Function of the requesting UE .....        | 24 |
+| 5.7.3 Detailed behaviour of the ProSe Function of the targeted UE .....          | 24 |
+| 5.8 ProSe Cancellation .....                                                     | 24 |
+| 5.8.1 General .....                                                              | 24 |
+| 5.8.2 Detailed behaviour of the ProSe Function of the requesting UE .....        | 25 |
+| 5.8.3 Detailed behaviour of the ProSe Function of the targeted UE .....          | 25 |
+| 5.9 ProSe Proximity Alert .....                                                  | 25 |
+| 5.9.1 General .....                                                              | 25 |
+| 5.9.2 Detailed behaviour of the ProSe Function of the targeted UE .....          | 26 |
+| 5.9.3 Detailed behaviour of the ProSe Function of the requesting UE .....        | 26 |
+| 5.10 ProSe Direct Discovery Authorization Update .....                           | 27 |
+| 5.10.1 General .....                                                             | 27 |
+| 5.10.2 Detailed behaviour of the HPLMN ProSe Function.....                       | 28 |
+| 5.10.3 Detailed behaviour of the ProSe Function in the local PLMN or VPLMN ..... | 28 |
+| 5.11 ProSe Direct Discovery Authorization Update Result.....                     | 28 |
+| 5.11.1 General .....                                                             | 28 |
+| 5.11.2 Detailed behaviour of the ProSe Function in the local PLMN.....           | 29 |
+| 5.11.3 Detailed behaviour of the HPLMN ProSe Function.....                       | 29 |
+| 6 Protocol Specification and Implementation .....                                | 30 |
+| 6.1 Introduction .....                                                           | 30 |
+| 6.1.1 Use of Diameter base protocol .....                                        | 30 |
+| 6.1.2 Securing Diameter Messages .....                                           | 30 |
+| 6.1.3 Accounting functionality .....                                             | 30 |
+
+|        |                                                     |    |
+|--------|-----------------------------------------------------|----|
+| 6.1.4  | Use of sessions .....                               | 30 |
+| 6.1.5  | Transport protocol .....                            | 30 |
+| 6.1.6  | Routing considerations .....                        | 30 |
+| 6.1.7  | Advertising Application Support.....                | 31 |
+| 6.1.8  | Diameter Application Identifier.....                | 31 |
+| 6.1.9  | Use of the Supported-Features AVP .....             | 31 |
+| 6.2    | Commands.....                                       | 31 |
+| 6.2.1  | Introduction .....                                  | 31 |
+| 6.2.2  | Command-Code values .....                           | 32 |
+| 6.2.3  | ProSe-Authorization-Request (PAR) Command.....      | 32 |
+| 6.2.4  | ProSe-Authorization-Answer (PAA) Command .....      | 33 |
+| 6.2.5  | ProSe-Discovery-Request (PDR) Command .....         | 33 |
+| 6.2.6  | ProSe-Discovery-Answer (PDA) Command.....           | 34 |
+| 6.2.7  | ProSe-Match-Request (PMR) Command.....              | 34 |
+| 6.2.8  | ProSe-Match-Answer (PMA) Command .....              | 34 |
+| 6.2.9  | ProSe-Match-Report-Info-Request (PIR) Command ..... | 35 |
+| 6.2.10 | ProSe-Match-Report-Info-Answer (PIA) Command .....  | 35 |
+| 6.2.11 | ProSe-Proximity-Request (PRR) Command .....         | 36 |
+| 6.2.12 | ProSe-Proximity-Answer (PRA) Command .....          | 36 |
+| 6.2.13 | ProSe-Location-Update-Request (PLR) Command .....   | 37 |
+| 6.2.14 | ProSe-Location-Update-Answer (PLA) Command.....     | 37 |
+| 6.2.15 | ProSe-Alert-Request (ALR) Command .....             | 38 |
+| 6.2.16 | ProSe-Alert-Answer (ALA) Command.....               | 38 |
+| 6.2.17 | ProSe-Cancellation-Request (PCR) Command.....       | 38 |
+| 6.2.18 | ProSe-Cancellation-Answer (PCA) Command .....       | 39 |
+| 6.3    | Information Elements .....                          | 39 |
+| 6.3.1  | General .....                                       | 39 |
+| 6.3.2  | App-Layer-User-Id .....                             | 42 |
+| 6.3.3  | Assistance-info .....                               | 42 |
+| 6.3.4  | Assistance-Info-Validity-Timer .....                | 43 |
+| 6.3.5  | Discovery-Type .....                                | 43 |
+| 6.3.6  | EAP-Master-Session-Key.....                         | 43 |
+| 6.3.7  | Feature-List-ID AVP .....                           | 44 |
+| 6.3.8  | Feature-List AVP.....                               | 44 |
+| 6.3.9  | Filter-Id.....                                      | 44 |
+| 6.3.10 | Location-Estimate.....                              | 44 |
+| 6.3.11 | MAC-Address.....                                    | 44 |
+| 6.3.12 | Match-Report.....                                   | 44 |
+| 6.3.13 | MSISDN .....                                        | 45 |
+| 6.3.14 | Operating-Channel .....                             | 45 |
+| 6.3.15 | P2P-Features .....                                  | 45 |
+| 6.3.16 | ProSe-App-Code.....                                 | 45 |
+| 6.3.17 | ProSe-App-Id.....                                   | 45 |
+| 6.3.18 | ProSe-App-Mask .....                                | 45 |
+| 6.3.19 | ProSe-Direct-Allowed .....                          | 45 |
+| 6.3.20 | ProSe-Discovery-Filter .....                        | 45 |
+| 6.3.21 | PRR-Flags.....                                      | 46 |
+| 6.3.22 | ProSe-Validity-Timer .....                          | 46 |
+| 6.3.23 | Requesting-EPUID .....                              | 46 |
+| 6.3.24 | Supported-Features .....                            | 46 |
+| 6.3.25 | SSID .....                                          | 46 |
+| 6.3.26 | Targeted-EPUID.....                                 | 46 |
+| 6.3.27 | Time-Window.....                                    | 46 |
+| 6.3.28 | User-Identifier .....                               | 47 |
+| 6.3.29 | Visited-PLMN-Id .....                               | 47 |
+| 6.3.30 | WiFi-P2P-Assistance-Info.....                       | 47 |
+| 6.3.31 | WLAN-Assistance-Info.....                           | 47 |
+| 6.3.32 | WLAN-Link-Layer-Id .....                            | 47 |
+| 6.3.33 | WLAN-Link-Layer-Id-List .....                       | 48 |
+| 6.3.34 | OC-Supported-Features .....                         | 48 |
+| 6.3.35 | OC-OLR .....                                        | 48 |
+| 6.3.36 | Validity-Time-Announce .....                        | 48 |
+
+|          |                                                               |    |
+|----------|---------------------------------------------------------------|----|
+| 6.3.37   | Validity-Time-Monitor.....                                    | 48 |
+| 6.3.38   | Validity-Time-Communication .....                             | 48 |
+| 6.3.39   | ProSe-App-Code-Info.....                                      | 48 |
+| 6.3.40   | MIC.....                                                      | 48 |
+| 6.3.41   | UTC-based-Counter .....                                       | 49 |
+| 6.3.42   | Location-Update-Trigger.....                                  | 49 |
+| 6.3.43   | Location-Update-Event-Type.....                               | 49 |
+| 6.3.44   | Change-Of-Area-Type.....                                      | 49 |
+| 6.3.45   | Location-Update-Event-Trigger .....                           | 50 |
+| 6.3.46   | Report-Cardinality .....                                      | 50 |
+| 6.3.47   | Minimum-Interval-Time.....                                    | 50 |
+| 6.3.48   | Periodic-Location-Type.....                                   | 50 |
+| 6.3.49   | Location-Report-Interval-Time .....                           | 51 |
+| 6.3.50   | Total-Number-Of-Reports.....                                  | 51 |
+| 6.3.51   | Authorized-Discovery-Range.....                               | 51 |
+| 6.3.52   | ProSe-Match-Refresh-Timer .....                               | 51 |
+| 6.3.53   | Discovery-Auth-Request.....                                   | 51 |
+| 6.3.54   | Discovery-Auth-Response.....                                  | 52 |
+| 6.3.55   | Match-Request.....                                            | 53 |
+| 6.3.56   | Match-Report-Info.....                                        | 54 |
+| 6.3.57   | PMR-Flags.....                                                | 54 |
+| 6.3.58   | ProSe-Application-Metadata .....                              | 54 |
+| 6.3.59   | Discovery-Entry-ID .....                                      | 54 |
+| 6.3.60   | ProSe-Metadata-Index-Mask.....                                | 54 |
+| 6.3.61   | App-Identifier .....                                          | 54 |
+| 6.3.62   | OS-ID .....                                                   | 55 |
+| 6.3.63   | OS-App-ID .....                                               | 55 |
+| 6.3.64   | Requesting-RPAUID.....                                        | 55 |
+| 6.3.65   | Target-RPAUID .....                                           | 55 |
+| 6.3.66   | Target-PDUID .....                                            | 55 |
+| 6.3.67   | ProSe-Restricted-Code .....                                   | 55 |
+| 6.3.68   | ProSe-Restricted-Code-Suffix-Range .....                      | 55 |
+| 6.3.69   | Beginning-Suffix .....                                        | 55 |
+| 6.3.70   | Ending-Suffix .....                                           | 56 |
+| 6.3.71   | Match-Timestamp.....                                          | 56 |
+| 6.3.72   | DRMP.....                                                     | 56 |
+| 6.3.73   | Banned-RPAUID.....                                            | 56 |
+| 6.3.74   | Banned-PDUID .....                                            | 56 |
+| 6.3.75   | Code-Receiving-Security-Material.....                         | 56 |
+| 6.3.76   | Code-Sending-Security-Material.....                           | 56 |
+| 6.3.77   | DUSK .....                                                    | 57 |
+| 6.3.78   | DUIK .....                                                    | 57 |
+| 6.3.79   | DUCK.....                                                     | 57 |
+| 6.3.80   | MIC-Check-Indicator .....                                     | 57 |
+| 6.3.81   | Encrypted-Bitmask .....                                       | 57 |
+| 6.3.82   | ProSe-App-Code-Suffix-Range.....                              | 57 |
+| 6.3.83   | Load.....                                                     | 58 |
+| 6.3.84   | PC5-tech .....                                                | 58 |
+| 6.4      | Result-Code and Experimental-Result Values.....               | 58 |
+| 6.4.1    | General .....                                                 | 58 |
+| 6.4.2    | Success .....                                                 | 58 |
+| 6.4.3    | Permanent Failures .....                                      | 58 |
+| 6.4.3.1  | DIAMETER_ERROR_USER_UNKNOWN (5001) .....                      | 58 |
+| 6.4.3.2  | DIAMETER_ERROR_UNAUTHORIZED_SERVICE (5511).....               | 58 |
+| 6.4.3.3  | DIAMETER_ERROR_NO_ASSOCIATED_DISCOVERY_FILTER (5630).....     | 58 |
+| 6.4.3.4  | DIAMETER_ERROR_ANNOUNCING_UNAUTHORIZED_IN_PLMN (5631).....    | 58 |
+| 6.4.3.5  | DIAMETER_ERROR_INVALID_APPLICATION_CODE (5632).....           | 58 |
+| 6.4.3.6  | DIAMETER_ERROR_PROXIMITY_UNAUTHORIZED (5633).....             | 59 |
+| 6.4.3.7  | DIAMETER_ERROR_PROXIMITY_REJECTED (5634).....                 | 59 |
+| 6.4.3.8  | DIAMETER_ERROR_NO_PROXIMITY_REQUEST (5635).....               | 59 |
+| 6.4.3.9  | DIAMETER_ERROR_UNAUTHORIZED_SERVICE_IN_THIS_PLMN (5636) ..... | 59 |
+| 6.4.3.10 | DIAMETER_ERROR_PROXIMITY_CANCELLED (5637).....                | 59 |
+
+6.4.3.11 DIAMETER\_ERROR\_INVALID\_DISCOVERY\_TYPE (5641) ..... 59
+
+6.4.3.12 DIAMETER\_ERROR\_INVALID\_TARGET\_PDUID (5638) ..... 59
+
+6.4.3.13 DIAMETER\_ERROR\_INVALID\_TARGET\_RPAUID (5639) ..... 59
+
+6.4.3.14 DIAMETER\_ERROR\_NO\_ASSOCIATED\_RESTRICTED\_CODE (5640) ..... 59
+
+6.4.3.15 DIAMETER\_ERROR\_REVOCATION\_FAILURE (56x1)..... 59
+
+6.4.3.16 DIAMETER\_ERROR\_ALREADY\_BANNED (56x2)..... 59
+
+6.4.4 Transient Failures ..... 59
+
+**Annex A (normative): Diameter overload control mechanism ..... 61**
+
+A.1 General ..... 61
+
+A.2 Responding ProSe Function behaviour ..... 61
+
+A.3 Requesting ProSe Function behaviour ..... 61
+
+**Annex B (Informative): Diameter overload node behaviour ..... 62**
+
+B.1 Message prioritization ..... 62
+
+**Annex C (normative): Diameter message priority mechanism ..... 62**
+
+C.1 General ..... 62
+
+C.2 PC6/PC7 interfaces ..... 62
+
+C.2.1 General ..... 62
+
+C.2.2 ProSe Function behaviour ..... 62
+
+**Annex D (normative): Diameter load control mechanism ..... 63**
+
+D.1 General ..... 63
+
+D.2 Responding ProSe Function behaviour ..... 63
+
+D.3 Requesting ProSe Function behaviour ..... 63
+
+Annex E (informative): Change history..... 64
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document describes the Diameter-based interfaces between the Proximity Services (ProSe) Function in the HPLMN and the ProSe Function in a local PLMN (PC6 interface) or between the Proximity Services (ProSe) Function in the HPLMN and the ProSe Function in a visited PLMN (PC7 interface).
+
+This specification defines the Diameter application for PC6/PC7 reference points between the ProSe Functions. The interactions between the ProSe Functions are specified.
+
+The stage 2 description for Proximity Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [2].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23 303: "Proximity-based services (ProSe); Stage 2".
+- [3] 3GPP TS 29 228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
+- [4] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [5] 3GPP TS 29.329: "Sh interface based on the Diameter protocol; Protocol details".
+- [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+- [7] Void.
+- [8] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
+- [9] IETF RFC 4960: "Stream Control Transport Protocol".
+- [10] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; protocol details".
+- [11] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
+- [12] IETF RFC 4072: "Diameter Extensible Authentication Protocol (EAP) Application".
+- [13] 3GPP TS 32.299: "Charging management; Diameter charging applications".
+- [14] 3GPP TS 29.344: "Proximity-services (Prose) Function to Home Subscriber Server (HSS) aspects (PC4); Stage 3".
+- [15] 3GPP TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
+- [16] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
+- [17] Wi-Fi Alliance Technical Committee P2P Task Group, "Wi-Fi Peer-to-Peer (P2P) Technical Specification", Version 1.1.
+- [18] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
+
+- [19] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
+- [20] IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
+- [21] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [22] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
+- [23] 3GPP TS 33.303: "Proximity-based Services (ProSe); Security aspects".
+- [24] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
+- [25] Open Mobile Alliance, OMA AD SUPL: "Secure User Plane Location Architecture", (<http://www.openmobilealliance.org>).
+- [26] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)".
+- [27] IETF RFC 7944: "Diameter Routing Message Priority".
+- [28] IETF RFC 8583: "Diameter Load Information Conveyance".
+- [29] IETF RFC 6733: "Diameter Base Protocol".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.303 [2] apply:
+
+**Local PLMN**
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                      |
+|--------|--------------------------------------|
+| ALUID  | Application Layer User ID            |
+| DRMP   | Diameter Routing Message Priority    |
+| DSCP   | Differentiated Services Code Point   |
+| DUCK   | Discovery User Confidentiality Key   |
+| DUIK   | Discovery User Integrity Key         |
+| DUSK   | Discovery User Scrambling Key        |
+| EPUID  | EPC ProSe User ID                    |
+| MIC    | Message Integrity Check              |
+| PDUID  | ProSe Discovery UE ID                |
+| ProSe  | Proximity-based Services             |
+| RPAUID | Restricted ProSe Application User ID |
+| UTC    | Universal Time Coordinated           |
+| WLLID  | WLAN Link Layer ID                   |
+
+# --- 4 General Description
+
+## 4.1 Introduction
+
+The PC6 reference point is defined between a ProSe Function in the HPLMN and a ProSe Function in a local PLMN.
+
+The PC7 reference point is defined between ProSe Function in the HPLMN and a ProSe Function in a visited PLMN.
+
+The definition of the PC6/PC7 reference points and related functionalities are given in 3GPP TS 23.303 [2].
+
+As defined in 3GPP TS 23.303 [2], the PC6/PC7 reference points are used for:
+
+- HPLMN control of service authorization for ProSe;
+- Authorization of ProSe Direct Discovery requests;
+- Retrieval of Discovery Filter(s) corresponding ProSe Application ID name(s);
+- Translation of ProSe Application Code(s) to the associated ProSe Application Name.
+
+# --- 5 Procedures Description
+
+## 5.1 introduction
+
+This clause describes the Diameter-based PC6 and PC7 interfaces related procedures and Information elements exchanged between functional entities.
+
+In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [3].
+
+## 5.2 ProSe Service Authorization
+
+### 5.2.1 General
+
+The ProSe Service Authorization Procedure shall be used between the ProSe Function in the HPLMN and the ProSe Function in Local PLMN or VPLMN to obtain service authorization information for ProSe Direct Discovery, ProSe Direct Communication or both. The procedure shall be invoked by the ProSe Function in the HPLMN by the UE and is used:
+
+- to request service authorization information for ProSe related to the UE from the ProSe Function in the local PLMN or VPLMN;
+- to provide the ProSe Function in the local PLMN or VPLMN with the UE identity (IMSI or MSISDN) in order to allow to perform charging;
+
+This procedure is mapped to the commands ProSe-Authorization-Request/Answer (PAR/PAA) in the Diameter application specified in clause 6.
+
+Table 5.2.1-1 specifies the involved information elements for the request.
+
+Table 5.2.1-2 specifies the involved information elements for the answer.
+
+**Table 5.2.1-1: ProSe Service Authorization Request**
+
+| Information element name           | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                        |
+|------------------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UE Identity<br>(See 6.3.28)        | User-Identifier         | M    | This information element shall contain either the user IMSI, formatted according to 3GPP TS 23.003 [4], clause 2.2, or the user MSISDN, formatted according to 3GPP TS 29.329 [5]. |
+| PLMN Id<br>(See 6.3.29)            | Visited-PLMN-Id         | M    | This IE shall contain the PLMN-Id (3GPP TS 23.003 [4]) of the network in which the ProSe Function is located.                                                                      |
+| Supported Features<br>(See 6.3.24) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                              |
+
+**Table 5.2.1-2: ProSe Service Authorization Answer**
+
+| Information element name                                | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features<br>(See 6.3.24)                      | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                                 |
+| Result<br>(See 6.4)                                     | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- Unauthorized Service<br>- Unauthorized Service in this PLMN |
+| ProSe Direct Allowed<br>(See 6.3.42)                    | ProSe-Direct-Allowed              | C    | This Information Element shall contain the ProSe authorization information of the user. It shall be present if success is reported.                                                                                                                                                                                                                                                                                                                                                                   |
+| Validity Time of Announcing<br>(see 6.3.36)             | Validity-Time-Announce            | C    | This Information Element shall contain the validity time for a UE authorization to perform ProSe direct discovery announcing in this PLMN. It shall be present if success is reported.                                                                                                                                                                                                                                                                                                                |
+| Validity Time of Monitoring<br>(see 6.3.37)             | Validity-Time-Monitor             | C    | This Information Element shall contain the validity time for a UE authorization to perform ProSe direct discovery monitoring in this PLMN. It shall be present if success is reported.                                                                                                                                                                                                                                                                                                                |
+| Validity Time of Communication<br>(see 6.3.38)          | Validity-Time-Communication       | C    | This Information Element shall contain the validity time for a UE authorization to perform ProSe direct communication in this PLMN. It shall be present if success is reported.                                                                                                                                                                                                                                                                                                                       |
+| Authorized Discovery Range<br>(See 3GPP TS 29.344 [14]) | Authorized-Discovery-Range        | C    | This information element shall contain the authorised range (short/medium/long) at which the UE is allowed to announce in the given PLMN according to the defined announcing authorisation policy for this UE. It shall be present if the discovery authorization type is for announcing. Otherwise it shall be absent.                                                                                                                                                                               |
+
+### 5.2.2 Detailed behaviour of the ProSe Function in the HPLMN
+
+The ProSe Function in the HPLMN shall make use of this procedure to request service authorization information for ProSe related to the UE from the ProSe Function in local PLMN or VPLMN. The ProSe Function shall include in the request the UE identity (IMSI or MSISDN) and the PLMN-Id identifying the PLMN of the requesting ProSe Function.
+
+When receiving a ProSe Service Authorization response from the ProSe Function in the local PLMN or VPLMN, the ProSe Function in the HPLMN shall check the result code. If it indicates SUCCESS, the ProSe Function shall merge with its own policy.
+
+### 5.2.3 Detailed behaviour of the ProSe Function in the Local PLMN or VPLMN
+
+When receiving a ProSe Service Authorization request, the ProSe Function in the local PLMN or VPLMN shall, in the following order:
+
+1. Check whether the UE Identity (IMSI or MSISDN) exists. If not, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+2. Check whether ProSe is authorized for this UE Identity. If not, a Result Code of DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE shall be returned.
+
+If there is an error in any of the above steps then the ProSe Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+Otherwise, when the UE is authorized to use ProSe Direct Discovery or ProSe Direct Communication in this PLMN, the ProSe Function shall return the authorization data in the response, according to the supported/unsupported features of the ProSe Function in the Local PLMN or VPLMN, and the authorised announcing range (short/medium/long) at which and if the UE is allowed to announce in the VPLMN according to the defined announcing authorisation policy for this UE (see 3GPP TS 24.333 [26] for the possible values of the range) and shall set the Result Code to "DIAMETER\_SUCCESS".
+
+## 5.3 ProSe Direct Discovery Authorization
+
+### 5.3.1 General
+
+The ProSe Direct Discovery Authorization Procedure shall be used between the ProSe Function in the HPLMN and the ProSe Function in a Local PLMN or VPLMN to obtain authorization for access to the discovery resources and perform ProSe Direct Discovery. The procedure shall be invoked by the ProSe Function in the HPLMN and is used:
+
+- to request the ProSe Function in the VPLMN or Local PLMN for the authorization for ProSe Direct Discovery announcing when the announcing UE is roaming in the VPLMN or announcing in a Local PLMN;
+- to perform the resolution ProSe Application ID Name to ProSe Application Code and/or ProSe Application Mask when the ProSe Application ID has PLMN-specific scope for open ProSe Direct discovery;
+- to notify the ProSe Function in Local PLMN that the previously allocated ProSe Discovery Filter for a ProSe Application ID which has PLMN-specific scope is no longer monitored by a monitoring UE of the HPLMN;
+- to perform the resolution of a target RPAUID to a ProSe Restricted Code or ProSe Restricted Code Prefix for restricted ProSe Direct Discovery;
+- to provide the ProSe Function in the Local PLMN or VPLMN with the application identity in order to allow it to perform charging;
+- to provide the ProSe Function in the Local PLMN or VPLMN with the UE identity (i.e. IMSI or MSISDN) in order to allow to perform charging;
+- to provide the ProSe Function in VPLMN with the allocated ProSe Application Code, ProSe Restricted Code or ProSe Restricted Code Prefix/Suffix Pool, and the corresponding validity timer, or a notification of the termination or change of the allocated ProSe-related codes, in order to allow to perform charging.
+- to provide the ProSe Function in VPLMN with the allocated ProSe Query Code or ProSe Response Code and the corresponding validity timer when such a code is announced in restricted ProSe Direct Discovery model B procedure, in order to allow to perform charging.
+- to provide the ProSe Function in VPLMN/Local PLMN with the allocated ProSe Query Code, ProSe Response Code and associated validity timer for a given RPAUID using restricted ProSe Direct Discovery model B.
+
+- to provide the ProSe Function in the Local PLMN or VPLMN with the PC5 radio technology that the UE is using.
+
+This procedure is mapped to the commands ProSe-Discovery-Request/Answer (PDR/PDA) in the Diameter application specified in clause 6.
+
+Table 5.3.1-1 specifies the involved information elements for the request.
+
+Table 5.3.1-2 specifies the involved information elements for the answer.
+
+**Table 5.3.1-1: ProSe Direct Discovery Authorization Request**
+
+| Information element name                     | Mapping to Diameter AVP | Cat. | Description                                                                                                                                          |
+|----------------------------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Discovery Authorization Request (See 6.3.53) | Discovery-Auth-Request  | M    | This information element shall contain the information elements used in discovery authorization request.                                             |
+| Supported Features (See 6.3.24)              | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                |
+| Discovery Entry ID (See 6.3.59)              | Discovery-Entry-ID      | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request. |
+
+**Table 5.3.1-2: ProSe Direct Discovery Authorization Answer**
+
+| Information element name                      | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24)               | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                 |
+| Result (See 6.4)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Announcing Not Authorized<br>- No Associated Discovery Filter |
+| Discovery Authorization Response (See 6.3.54) | Discovery-Auth-Response           | C    | This information element shall contain the information elements used in discovery authorization response. This information element shall be present if the Result Code AVP is DIAMETER_SUCCESS.                                                                                                                                                                                                                                                                                       |
+| Discovery Entry ID (See 6.3.59)               | Discovery-Entry-ID                | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request.                                                                                                                                                                                                                                                                                                                                  |
+
+### 5.3.2 Detailed behaviour of the HPLMN ProSe Function
+
+The ProSe Function in the HPLMN shall make use of this procedure to request the ProSe Function in VPLMN or a PLMN other than the HPLMN/VPLMN for ProSe Direct Discovery announcing authorisation for an announcing UE roaming in the VPLMN or announcing in a Local PLMN.
+
+- For open ProSe Direct Discovery, the HPLMN ProSe Function shall include in the request the Discovery Entry ID and shall include in the Discovery Authorization Request the Discovery Type set to "ANNOUNCING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the ProSe Application ID corresponding to the request from the announcing UE and the ProSe Application Code or ProSe Application Code Prefix/Suffix(es) assigned for this request. The Discovery Authorization Request shall include the UE identity (i.e., IMSI or MSISDN) and the ProSe Validity Timer corresponding to ProSe Application Code in order to allow the ProSe Function in VPLMN or the Local PLMN to perform charging. If the announcing UE's original announce request is for updating the metadata, the updated metadata shall also be included. If the announcing UE's original announce request is for stopping the announcing operation, the ProSe Function shall
+
+not include any ProSe Application Code(s) or ProSe Validity Timer. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+
+- For restricted ProSe Direct Discovery, the HPLMN ProSe Function shall include in the Discovery Authorization Request the Discovery Entry ID and the Discovery Type set to "ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, RPAUID corresponding to the announcing UE, the ProSe Restricted Code assigned for this request. The Discovery Authorization Request shall also include the UE identity (i.e., IMSI or MSISDN) and the ProSe Validity Timer corresponding to ProSe Restricted Code in order to allow the ProSe Function in VPLMN or the Local PLMN to perform charging. For restricted ProSe Direct Discovery using application-controlled extension, the ProSe Function shall include a ProSe Restricted Code Prefix and one or more ProSe Restricted Code Suffix Range in the Discovery Authorization Request. If the announcing UE's original announce request is for stopping the announcing operation, the ProSe Function shall not include any ProSe Restricted Code or ProSe Restricted Code Prefix or ProSe Restricted Code Suffix Range(s), or ProSe Validity Timer. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+- For restricted ProSe Direct Discovery model B discoverer operation, the HPLMN ProSe Function shall include in the Discovery Authorization Request the Discovery Entry ID and the Discovery Type set to "DISCOVERER\_ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, RPAUID corresponding to the discoverer UE as well as the ProSe Query Code assigned for this request. The Discovery Authorization Request shall also include the UE identity (i.e., IMSI or MSISDN) and the ProSe Validity Timer corresponding to ProSe Query Code in order to allow the ProSe Function in VPLMN or the Local PLMN to perform charging. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+- For restricted ProSe Direct Discovery model B discoveree operation, the HPLMN ProSe Function shall include in the Discovery Authorization Request the Discovery Entry ID and the Discovery Type set to "DISCOVEREE\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, RPAUID corresponding to the discoverer UE as well as the ProSe Response Code assigned for this request. The Discovery Authorization Request shall also include the UE identity (i.e., IMSI or MSISDN) and the ProSe Validity Timer corresponding to ProSe Query Code in order to allow the ProSe Function in VPLMN or the Local PLMN to perform charging. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+
+The ProSe Function in the HPLMN shall make use of this procedure to retrieve from the ProSe Function in the Local PLMN the Discovery Filter for monitoring in open ProSe Direct Discovery or to retrieve parameters needed to create a Restricted Discovery Filter, or ProSe Response Filter associated with the monitored/queried application-layer identity for restricted ProSe Direct Discovery.
+
+- For open ProSe Direct Discovery, the HPLMN ProSe Function shall include in the request the Discovery Entry ID and shall include in the Discovery Authorization Request the Discovery Type set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the ProSe Application ID name corresponding to the request from the monitoring UE. The Discovery Authorization Request shall also include the UE identity (i.e., IMSI or MSISDN) in order to allow the ProSe Function in Local PLMN to perform charging. If the monitoring UE's original announce request is for stopping the monitoring operation or the allocated Discovery Filter has been revoked by the ProSe Function, the ProSe Function shall not include the ProSe Application ID name. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+- For restricted ProSe Direct Discovery, the HPLMN ProSe Function shall include in the Discovery Authorization Request the Discovery Entry ID and the Discovery Type set to "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, the requesting RPAUID, target RPAUID and target PDUID of a monitoring target. The Discovery Authorization Request shall also include the UE identity (i.e., IMSI or MSISDN) in order to allow the ProSe Function in Local PLMN to perform charging. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+- For restricted ProSe Direct Discovery model B discoveree operation, the HPLMN ProSe Function shall include in the Discovery Authorization Request the Discovery Entry ID and the Discovery Type set to the indicate "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, the requesting RPAUID, target RPAUID and target PDUID of a monitoring target. The request shall include the UE identity (IMSI or MSISDN) and the Discovery Entry ID in order to allow the ProSe Function in Local
+
+PLMN to perform charging. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+
+When receiving the ProSe Direct Discovery Authorization response with the Result Code set to "DIAMETER\_SUCCESS" for a request with the Discovery Type set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the HPLMN ProSe Function shall check whether a ProSe Discovery Filter is received for each ProSe Application ID Name sent in the request. If a ProSe Discovery Filter is missing for one ProSe Application ID Name, the ProSe Function shall consider that there is no valid ProSe Discovery Filter the ProSe associated with this ProSe Application ID Name in the ProSe Function in the Local PLMN or VPLMN.
+
+When receiving the ProSe Direct Discovery Authorization response with the Result Code set to "DIAMETER\_SUCCESS" for a request with the Discovery Type set to "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY" or "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the HPLMN ProSe Function shall enclose the information in Code Receiving Security Material parameter in the discovery filter created for the target RPAUID. If a DUIK parameter is included in the response message, the ProSe Function shall store the DUIK in order to verify the MIC field, as specified in 3GPP TS 24.334 [22].
+
+### 5.3.3 Detailed behaviour of the ProSe Function in the Local PLMN or VPLMN
+
+When receiving a ProSe Direct Discovery Authorization request, the ProSe Function in the Local PLMN or VPLMN shall check the value of the Discovery Type.
+
+- If the value is "ANNOUNCING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check if the UE is authorized to announce in the PLMN for the specified PC5 radio technology.
+  - If the UE is not authorized, the experimental result code shall be set to "DIAMETER\_ERROR\_ANNOUNCING\_UNAUTHORIZED\_IN\_PLMN" in the response sent by the ProSe Function.
+  - If the UE is authorized, the result code shall be set to "DIAMETER\_SUCCESS" in the response sent by the ProSe Function. The ProSe Function shall store the UE identity (i.e., IMSI or MSISDN) in order to perform charging. In addition, the ProSe Function in the VPLMN or the Local PLMN shall store the ProSe Validity Timer corresponding to ProSe Application Code or ProSe Application Code Prefix/Suffix(es) in order to perform charging. If no ProSe Application Code is included in the request, the ProSe Function shall remove the discovery entry associated with the Discovery Entry ID for the requesting UE.
+- If the value is "ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether the UE is authorized to announce in the PLMN for restricted discovery model A for the specified PC5 radio technology.
+  - If the UE is not authorized, the experimental result code shall be set to "DIAMETER\_ERROR\_ANNOUNCING\_NOT\_AUTHORIZED" in the response sent by the ProSe Function.
+  - If the UE is authorized, the result code shall be set to "DIAMETER\_SUCCESS" in the response sent by the ProSe Function. The ProSe Function in the VPLMN or the Local PLMN shall store the UE identity (IMSI or MSISDN) in order to perform charging;
+  - ProSe Function in the VPLMN or the Local PLMN shall store the Application Identity, and the ProSe Validity Timer corresponding to ProSe Restricted Code or ProSe Restricted Code Prefix and ProSe Restricted Code Suffix(es) in order to perform charging. If no ProSe Restricted Code or ProSe Restricted Code Prefix is included in the request, the ProSe Function shall remove the discovery entry associated with the Discovery Entry ID for the requesting UE.
+- If the value is "DISCOVEREE\_ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether the UE is authorized to announce in the PLMN for restricted discovery model B discoveree operation for the specified PC5 radio technology.
+
+- If the UE is not authorized, the experimental result code shall be set to "DIAMETER\_ERROR\_ANNOUNCING\_UNAUTHORIZED\_IN\_PLMN" in the response sent by the ProSe Function.
+- If the UE is authorized, the result code shall be set to "DIAMETER\_SUCCESS" in the response sent by the ProSe Function. The ProSe Function in the VPLMN or the Local PLMN shall store the UE identity (IMSI or MSISDN) in order to perform charging;
+- ProSe Function in the VPLMN or the Local PLMN shall store the Application Identity, and the ProSe Validity Timer corresponding to ProSe Response Code in order to perform charging.
+- If the value is "DISCOVERER\_ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether the UE is authorized to announce in the PLMN for restricted discovery model B discoverer operation for the specified PC5 radio technology.
+- If the UE is not authorized, the experimental result code shall be set to "DIAMETER\_ERROR\_ANNOUNCING\_UNAUTHORIZED\_IN\_PLMN" in the response sent by the ProSe Function.
+- If the UE is authorized, the result code shall be set to "DIAMETER\_SUCCESS" in the response sent by the ProSe Function. The ProSe Function in the VPLMN or the Local PLMN shall store the UE identity (IMSI or MSISDN), the Application Identity and the ProSe Validity Timer corresponding to ProSe Query Code in order to perform charging;
+- If the value is "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether one or more Discovery Filter(s) exist for each ProSe Application ID name received in the request.
+  - If there is no valid Discovery Filter associated to the ProSe Application ID name in the request, the experimental result code shall be set to "DIAMETER\_ERROR\_NO\_ASSOCIATED\_DISCOVERY\_FILTER" in the response sent by the ProSe Function.
+- If no ProSe Application ID is included in the request, the ProSe Function shall remove the discovery entry associated with the Discovery Entry ID for the requesting UE. If there exists one or more valid Discovery Filters related to the ProSe Application ID name, the ProSe Function shall return the Discovery Authorization Response including the Discovery Filter(s) along with the Discovery Entry ID and set the result code to "DIAMETER\_SUCCESS" in the response. If the announcing UE is roaming, the PLMN-Id of the VPLMN shall be included in the Discovery Authorization Response.
+- If the value is "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall process the request in the following order to check if the monitoring is authorized.
+  - The ProSe function shall check whether the target PDUID is known and belongs to its own PLMN. If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_PDUID" in the response sent by the ProSe Function.
+  - The ProSe function may check whether the requesting RPAUID is allowed to discover the target RPAUID. If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_RPAUID" in the response sent by the ProSe Function.
+  - The ProSe function shall check whether a valid ProSe Restricted Code or ProSe Restricted Code Prefix exists for the target RPAUID included in the request.
+    - If not, the experimental result code shall be set to "DIAMETER\_ERROR\_NO\_ASSOCIATED\_RESTRICTED\_CODE" in the response sent by the ProSe Function.
+    - Otherwise, the ProSe Function shall set the result code to "DIAMETER\_SUCCESS" in the response. The ProSe Function shall return the Discovery Authorization Response including the ProSe Restricted Code or ProSe Restricted Code Prefix associated with the target RPAUID, and the corresponding Code Receiving Security Material and optionally a DUIK, and its corresponding Validity Timer. If the announcing UE is roaming, the PLMN-Id of the VPLMN shall be also included in the response.
+
+- If the value is "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall process the request in the following order to check whether the monitoring is authorized.
+  - The ProSe function shall check if the target PDUID is known and belongs to its own PLMN. If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_PDUID" in the response sent by the ProSe Function.
+  - The ProSe function may check if the requesting RPAUID is allowed to discovery the target RPAUID. If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_RPAUID" in the response sent by the ProSe Function.
+  - The ProSe function shall check if both ProSe Query Code and ProSe Response Code exist for the target RPAUID included in the request.
+    - If not, the experimental result code shall be set to "DIAMETER\_ERROR\_NO\_ASSOCIATED\_RESTRICTED\_CODE" in the response sent by the ProSe Function.
+    - Otherwise, the ProSe Function shall set the result code to "DIAMETER\_SUCCESS" in the response. The ProSe Function shall return the Discovery Authorization Response including the ProSe Query Code and the corresponding Code Sending Security Material and ProSe Response Code Code associated with the target RPAUID, and the corresponding Code Receiving Security Material and optionally a DUIK, and its corresponding Validity Timer. If the discoverer UE is roaming or announcing in a Local PLMN, the PLMN-Id of the VPLMN or the Local PLMN shall be also included in the response.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+## 5.4 ProSe Match Report
+
+### 5.4.1 General
+
+The ProSe Match Report Procedure shall be used between the ProSe Function in the HPLMN and the ProSe Function in the local PLMN identified by the PLMN-Id contained in the ProSe Application Code(s) discovered by the monitoring UE. The procedure shall be invoked by the ProSe Function in the HPLMN and is used:
+
+- to confirm that the ProSe Application Code(s) is authorized to be transmitted on the monitored PLMN;
+- to retrieve the ProSe Application ID(s), associated validity timer(s) and associated match report refresh timer(s) corresponding to the ProSe Application Code(s) as well metadata associated with the ProSe Application ID if available and requested by the UE; and
+- to provide the ProSe Function in the local PLMN with the identity (IMSI or MSISDN) of the monitoring UE in order to allow to perform charging.
+- to provide the ProSe Function in the Local PLMN with the PC5 radio technology that the UE is using.
+
+This procedure is mapped to the commands ProSe-Match-Request/Answer (PMR/PMA) in the Diameter application specified in clause 6.
+
+Table 5.4.1-1 specifies the involved information elements for the request.
+
+Table 5.4.1-2 specifies the involved information elements for the answer.
+
+**Table 5.4.1-1: ProSe Match Report Request**
+
+| Information element name        | Mapping to Diameter AVP | Cat. | Description                                                                                           |
+|---------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------|
+| Match Request (See 6.3.55)      | Match-Request           | M    | This information element shall contain the information elements used in discovery match request.      |
+| Supported Features (See 6.3.24) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host. |
+| PMR Flags (See 6.3.57)          | PMR-Flags               | C    | This Information Element contains a bit mask. See 6.3.57 for the meaning of the bits.                 |
+
+**Table 5.4.1-2: ProSe Match Report Answer**
+
+| Information element name        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|---------------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                   |
+| Result (See 6.4)                | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Announcing Not Authorized in PLMN<br>- Invalid Application Code |
+| Match Report (See 6.3.12)       | Match-Report                      | C    | This Information Element shall contain the information elements in response to the discovery match request. This Information Element shall be present only when the Result-Code AVP is DIAMETER_SUCCESS.<br>Multiple instances of this Information Element may be present in the message.                                                                                                                                                                                               |
+
+### 5.4.2 Detailed behaviour of the HPLMN ProSe Function
+
+The ProSe Function in the HPLMN shall make use of this procedure to retrieve from the ProSe Function in the local PLMN (identified by the PLMN-Id contained in the Prose Application Code) the ProSe Application ID(s) that correspond to ProSe Application Code(s) discovered by the monitoring UE. The HPLMN ProSe Function shall include in the Match Request the Discovery Type set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the discovered ProSe Application Code(s) corresponding to the request from the monitoring UE as well as the MIC and UTC-based counter associated with the discovered ProSe Application Code. The request shall include the UE identity (i.e. IMSI or MSISDN) in order to allow the ProSe Function in the local PLMN to perform charging of the monitoring UE. If the metadata information associated with the ProSe Application ID is requested by the UE, the flag "Metadata Requested" shall be set in the PMR Flags. The HPLMN ProSe Function may also include the PC5-tech set to the PC5 radio technology that the UE is using.
+
+When receiving the ProSe Match Report response from the ProSe Function in the local PLMN with the Result Code set to "DIAMETER\_SUCCESS", the HPLMN ProSe Function shall check whether a Match Report is received for each ProSe Application Code sent in the request. If a Match Report is missing for one ProSe Application Code, this ProSe Application Code shall be considered as invalid by the ProSe Function.
+
+### 5.4.3 Detailed behaviour of the ProSe Function in the local PLMN
+
+When receiving a ProSe Match Report request, the ProSe Function in the local PLMN shall check the value of the Discovery Type contained in the Match Request.
+
+- If the value indicated in the Discovery Type is not supported, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_DISCOVERY\_TYPE" in the response.
+
+- If the value is "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether that the ProSe Application Code received is authorized to be announced in the monitored PLMN for the specified PC5 radio technology.
+- If not, the experimental result code shall be set to "DIAMETER\_ERROR\_ANNOUNCING\_UNAUTHORIZED\_IN\_PLMN" in the response.
+- If the ProSe Code is authorized to be announced, the ProSe Function shall check the validity of the ProSe Application Code(s) discovered by the monitoring UE, i.e. a ProSe Application ID name is associated and the validity timer has not expired, and the MIC value associated with the ProSe Application Code is valid when verified based on the associated UTC-based counter as defined in 3GPP TS 33.303 [23].
+- If none of the ProSe Application Code(s) is valid in the ProSe Function, i.e. either no ProSe Application Code exists, the validity timer(s) has expired, or MIC check(s) for the ProSe Application Code(s) has failed, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_APPLICATION\_CODE" in the response sent by the ProSe Function.
+- Otherwise, when at least one ProSe Application Code is valid, the ProSe Function shall return the Match Report and set the result code to "DIAMETER\_SUCCESS" in the response. For each valid ProSe Application code, the Match Report shall contain the matched ProSe Application Code, the ProSe Application ID Name, the validity timer and the match report refresh timer. The Match Report may include metadata associated with the ProSe Application ID if requested and available. The ProSe Function may store the monitoring UE identity (i.e. IMSI or MSISDN) in order to perform charging.
+
+If there is an error in any of the above steps then the ProSe Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+If the ProSe Application Code contains a metadata index, a ProSe-Metadata-Index-Mask AVP shall be provided for this ProSe Application Code.
+
+## 5.5 ProSe Match Report info
+
+### 5.5.1 General
+
+For open discovery, the ProSe Match Report Info Procedure shall be used by the ProSe Function in the HPLMN of the monitoring UE to provide a match report information to the ProSe Function of the visited PLMN in which the announcing UE is roaming. For restricted discovery, the ProSe Match Report Info Procedure shall also be used by the ProSe Function in the HPLMN of the monitoring UE or discoverer UE to provide a match report information to the ProSe Function of the HPLMN of the announcing UE or discoveree UE.
+
+This procedure is mapped to the commands ProSe-Match-Report-Info-Request/Answer (PIR/PIA) in the Diameter application specified in clause 6.
+
+Table 5.5.1-1 specifies the involved information elements for the request.
+
+Table 5.5.1-2 specifies the involved information elements for the answer.
+
+**Table 5.5.1-1: ProSe Match Report Info Request**
+
+| Information element name              | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                                                                         |
+|---------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Match Report Information (See 6.3.56) | Match-Report-Info       | C    | This information element shall contain the information elements used in discovery match report info request. This information element shall be present if the Discovery Type is MONITORING_REQUEST_FOR_OPEN_PROSE_DIRECT_DISCOVERY. |
+| Supported Features (See 6.3.24)       | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                               |
+
+**Table 5.5.1-2: ProSe Match Report Info Answer**
+
+| Information element name        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                |
+| Result (See 6.4)                | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Unknown User |
+
+### 5.5.2 Detailed behaviour of the requesting ProSe Function
+
+When the monitored PLMN-Id provided by the monitoring UE during the Match Report procedure (see clause 5.4) is different from the PLMN-Id contained in the ProSe Application Code discovered by the monitoring UE, i.e. the announcing UE is roaming in a visited PLMN, the monitoring UE's ProSe Function in the HPLMN may make use of this procedure to send a match report information to the ProSe Function in the visited PLMN in which the announcing UE is roaming.. In such case, the HPLMN ProSe Function shall include in the Match Report Information the Discovery Type set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY" as well as the ProSe Application ID and the identity of the monitoring UE (i.e. IMSI or MSISDN).
+
+When the HPLMN ProSe Function of the monitoring UE processes a match report for a discovered ProSe Restricted Code from the UE, and finds that the target PDUID for the corresponding discovery entry contains a PLMN-Id different from the PLMN of the ProSe Function, the monitoring UE's ProSe Function in the HPLMN may make use of this procedure to send a match report information to the ProSe Function to which the announcing UE belongs. In such case, the HPLMN ProSe Function shall include in the Match Report Information the Discovery Type set to "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Restricted Code, the RPAUID, the target RPAUID and the identity of the monitoring UE (i.e. IMSI or MSISDN). The ProSe Function may also include the timestamp of the match event in the Match Report Information.
+
+When the HPLMN ProSe Function of the discoverer UE processes a match report for a discovered ProSe Response Code from the discoverer UE, and finds that the target PDUID for the corresponding discovery entry contains a PLMN-Id different from the PLMN of the ProSe Function, the discoverer UE's ProSe Function in the HPLMN may make use of this procedure to send a match report information to the ProSe Function to which the discoverer UE belongs. In such case, the HPLMN ProSe Function shall include in the Match Report Information the Discovery Type set to "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Response Code, the RPAUID, the target RPAUID and the identity of the discoverer UE (i.e. IMSI or MSISDN). The ProSe Function may also include the timestamp of the match event in the Match Report Information.
+
+### 5.5.3 Detailed behaviour of the receiving ProSe Function
+
+When receiving a ProSe Match Report Info request, the ProSe Function shall check the value of the Discovery Type contained in the Match Report Information.
+
+- If the value indicated in the Discovery Type is not supported, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_DISCOVERY\_TYPE" in the response.
+- If the value is "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY" or "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the ProSe Function shall check whether the UE Identity (i.e. IMSI or MSISDN) exists.
+- If not, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+- Otherwise, it shall acknowledge the reception of the Match Report info and set the Result Code to "DIAMETER\_SUCCESS" in the response.
+
+If the ProSe Function in the VPLMN cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY" in the response.
+
+## 5.6 ProSe Proximity Request
+
+### 5.6.1 General
+
+The ProSe Proximity Request Procedure shall be used by a ProSe Function in charge of the requesting UE to request the ProSe Function in charge of another UE to indicate when two UEs will enter into proximity within a requested time window.
+
+This procedure is mapped to the commands ProSe-Proximity-Request/Answer (PRR/PRA) in the Diameter application specified in clause 6.
+
+Table 5.6.1-1 specifies the involved information elements for the request.
+
+Table 5.6.1-2 specifies the involved information elements for the answer.
+
+**Table 5.6.1-1: ProSe Proximity Request**
+
+| Information element name               | Mapping to Diameter AVP | Cat. | Description                                                                                                                          |
+|----------------------------------------|-------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------|
+| Requesting EPUID<br>(See 6.3.23)       | Requesting-EPUID        | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the UE triggering the Proximity Request.                     |
+| Targeted EPUID<br>(See 6.3.26)         | Targeted-EPUID          | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the UE targeted by the Proximity Request.                    |
+| Time Window<br>(See 6.3.27)            | Time-Window             | M    | This Information Element shall contain the time period during which the Proximity request is valid                                   |
+| Requesting UE Location<br>(See 6.3.10) | Location-Estimate       | M    | This Information Element shall contain the current location of the requesting UE expressed in GAD shapes defined in TS 23.032 [6]    |
+| Location Update Trigger<br>(See 6.3.a) | Location-Update-Trigger | O    | If present, this Information Element shall contain the trigger that will cause the location updates performed by the ProSe Function. |
+| Supported Features<br>(See 6.3.24)     | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                |
+| PRR Flags<br>(See 6.3.21)              | PRR-Flags               | M    | This Information Element contains a bit mask. See 6.3.21 for the meaning of the bits.                                                |
+
+**Table 5.6.1/2: ProSe Proximity Answer**
+
+| Information element name          | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+|-----------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24)   | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                             |
+| Result (See 6.4)                  | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- EPUID unknown<br>- Proximity request rejected<br>- Proximity unauthorized |
+| Targeted UE Location (See 6.3.10) | Location-estimate                 | C    | This Information Element shall contain the current location of the targeted UE expressed in GAD shapes defined in TS 23.032 [6]. This information shall be present when the Result Code is "DIAMETER_SUCCESS" and the location of the targeted UE is known.                                                                                                                                                                                                                                       |
+| WLAN Link Layer ID (See 6.3.32)   | WLAN-Link-Layer-Id                | C    | This Information shall contain the permanent link layer identity used by the targeted UE for WLAN direct discovery and/or WLAN direct communication. It shall be present if the requesting UE has requested EPC support for WLAN direct discovery and if the targeted UE has a permanent WLAN Link Layer ID for communication (e.g. permanent MAC address).                                                                                                                                       |
+
+### 5.6.2 Detailed behaviour of the ProSe Function of the requesting UE
+
+The ProSe Function of the UE triggering the Proximity request shall make use of this procedure to propagate the Proximity request to the ProSe Function of the targeted UE. The ProSe Function shall include in the request the EPC ProSe User Identities of the requesting and targeted UEs, the location of the requesting UE, the validity period of the Proximity request and, the location update trigger. If the requesting UE has requested EPC support for WLAN direct discovery and communication with the targeted UE, the PRR-Flag "WLAN Indication" shall be set.
+
+NOTE: The location update trigger enable the ProSe Function of the targeted UE to configure SUPL reporting in targeted UE using the ""Inside" trigger with Repeated Reporting" mechanism as defined in OMA AD SUPL [25].
+
+When receiving a ProSe Proximity response from the ProSe Function of the targeted UE, the ProSe Function of the requesting UE shall check the result code. If it indicates SUCCESS, the ProSe Function shall create and manage a context associated with the Proximity request, including the EPUIDs of the UEs, the validity period of this Proximity request and the WLAN indication received in the Proximity request until the execution of the Proximity Alert procedure, the Proximity Request Cancellation procedure or until the expiry of the time window during which the request is valid.
+
+### 5.6.3 Detailed behaviour of the ProSe Function of the targeted UE
+
+When receiving a ProSe Proximity request, the ProSe Function of the targeted UE, shall, in the following order:
+
+1. Check whether the EPC ProSe User Identity of the targeted UE exists. If not, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+2. Check whether the proximity request is authorized by the user. If not, the Proximity request is not authorized by the user, a Result Code of DIAMETER\_ERROR\_PROXIMITY\_UNAUTHORIZED shall be returned.
+3. Check the location of the requesting UE and the time window received in the request and determine whether UEs are likely to enter into proximity based the last known location of the targeted UE. If it is unlikely that UEs enter into proximity for the received time window, a Result Code of DIAMETER\_ERROR\_PROXIMITY\_REJECTED shall be returned in the response.
+
+If there is an error in any of the above steps then the ProSe Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+Otherwise, the ProSe Function shall acknowledge the reception of the Proximity and set the Result Code to "DIAMETER\_SUCCESS" in the response. The message may include the last known location of the targeted UE, if available. The message may also include the permanent WLAN Link Layer ID (e.g. MAC address) of the targeted UE if available and if the PRR-Flag "WLAN Indication" was set in the request. The ProSe Function shall create and manage a context associated with the Proximity request, including the identity of ProSe Function triggering the Proximity request, the EPUIDs of the UEs, the validity period of this Proximity request, the WLAN indication, the location update periodicity and/or location update trigger received in the Proximity request until the execution of the Proximity Alert procedure, the Proximity Request Cancellation procedure or until the expiry of the time window during which the request is valid.
+
+## 5.7 ProSe Location Update
+
+### 5.7.1 General
+
+The ProSe Location Update Procedure shall be used by a ProSe Function to forward the location of UE to the ProSe Function triggering the Proximity Request and in charge of determining the proximity of two UEs.
+
+This procedure is mapped to the commands ProSe-Location-Update-Request/Answer (PLR/PLA) in the Diameter application specified in clause 6.
+
+Table 5.7.1-1 specifies the involved information elements for the request.
+
+Table 5.7.1-2 specifies the involved information elements for the answer.
+
+**Table 5.7.1-1: ProSe Location Update Request**
+
+| Information element name             | Mapping to Diameter AVP | Cat. | Description                                                                                                                      |
+|--------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------|
+| Targeted EPUID<br>(See 6.3.26)       | Targeted-EPUID          | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the UE targeted by the Proximity Request.                |
+| Targeted UE Location<br>(See 6.3.10) | Location-Estimate       | M    | This Information Element shall contain the current location of the targeted UE expressed in GAD shapes defined in TS 23.032 [6]. |
+| Supported Features<br>(See 6.3.24)   | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                            |
+
+**Table 5.7.1-2: ProSe Location Update Answer**
+
+| Information element name           | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features<br>(See 6.3.24) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                         |
+| Result<br>(See 6.4)                | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- Proximity Cancelled |
+
+### 5.7.2 Detailed behaviour of the ProSe Function of the requesting UE
+
+The ProSe Function of the UE targeted by the Proximity request shall make use of this procedure to periodically update the targeted UE's location in the ProSe Function in charge of Proximity request. The ProSe Function shall include in the request the EPC ProSe User Identity and the location of the targeted UE.
+
+### 5.7.3 Detailed behaviour of the ProSe Function of the targeted UE
+
+When receiving a ProSe Location Update request, the ProSe Function in charge of the Proximity request shall, in the following order:
+
+1. Check whether a proximity request exists for the EPC ProSe User Identity received in the request. If there is no pending Proximity request for this EPUID, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+2. Check the location of the requesting UE and the time window indicated by the requesting UE and determine whether UEs are likely to enter into proximity based the last known location of the targeted UE. If it is unlikely that UEs enter into proximity for the received time window, a Result Code of DIAMETER\_ERROR\_PROXIMITY\_CANCELLED shall be returned in the response.
+
+If there is an error in any of the above steps then the ProSe Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+Otherwise, the ProSe Function shall acknowledge the reception of the ProSe Location Update and set the Result Code to "DIAMETER\_SUCCESS" in the response.
+
+## 5.8 ProSe Cancellation
+
+### 5.8.1 General
+
+The ProSe Cancellation Procedure shall be used between the ProSe Function in the HPLMN and the ProSe Function in the local/visited PLMN. The procedure shall be invoked by the ProSe Function in HPLMN and is used:
+
+- to indicate that the service authorization for ProSe Direct Discovery and ProSe Direct Communication is revoked for this UE.
+- to indicate that the Proximity Request sent earlier is cancelled.
+
+This procedure is mapped to the commands ProSe-Cancellation-Request/Answer (PCR/PCA) in the Diameter application specified in clause 6.
+
+Table 5.8.1-1 specifies the involved information elements for the request.
+
+Table 5.8.1-2 specifies the involved information elements for the answer.
+
+**Table 5.8.1-1: ProSe Cancellation Request**
+
+| Information element name           | Mapping to Diameter AVP | Cat. | Description                                                                                                       |
+|------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------|
+| Requesting EPUID<br>(See 6.3.23)   | Requesting-EPUID        | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the UE triggering the Proximity Request.  |
+| Targeted EPUID<br>(See 6.3.26)     | Targeted-EPUID          | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the UE targeted by the Proximity Request. |
+| Supported Features<br>(See 6.3.24) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.             |
+
+**Table 5.8.1-2: ProSe Cancellation Answer**
+
+| Information element name        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|---------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                        |
+| Result (See 6.4)                | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- No proximity request |
+
+### 5.8.2 Detailed behaviour of the ProSe Function of the requesting UE
+
+The ProSe Function of the requesting UE shall make use of this procedure to cancel a Proximity Request sent earlier to the ProSe Function in charge of the targeted UE (e.g. due to change in the location of one of the UEs, termination of corresponding application or due to completion of certain event). The ProSe Function shall include in the request the EPC ProSe User Identities of the requesting and targeted UEs.
+
+### 5.8.3 Detailed behaviour of the ProSe Function of the targeted UE
+
+When receiving a ProSe Cancellation request, the ProSe Function of the targeted UE shall check whether there is a context associated with EPC ProSe User Identities included in the request. If not, the Result Code of DIAMETER\_ERROR\_NO\_PROXIMITY\_REQUEST shall be returned. Otherwise, the ProSe Function shall cancel the Proximity request and set the Result Code to "DIAMETER\_SUCCESS" in the response
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+## 5.9 ProSe Proximity Alert
+
+### 5.9.1 General
+
+The ProSe Proximity Alert Procedure shall be used by a ProSe Function in charge of Proximity request to indicate to the ProSe Function of the UE targeted by the Proximity request that UEs enter into proximity and that a Proximity Alert should be sent to the targeted UE.
+
+This procedure is mapped to the commands ProSe-Alert-Request/Answer (ALR/ALA) in the Diameter application specified in clause 6.
+
+Table 5.9.1-1 specifies the involved information elements for the request.
+
+Table 5.9.1-2 specifies the involved information elements for the answer.
+
+**Table 5.9.1-1: ProSe Proximity Alert Request**
+
+| Information element name              | Mapping to Diameter AVP   | Cat. | Description                                                                                                                             |
+|---------------------------------------|---------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Application Layer User ID (See 6.3.2) | Application-Layer-User-Id | M    | This Information Element shall contain the Application Layer User ID of the requesting UE entering into proximity.                      |
+| Targeted EPUID (See 6.3.26)           | Targeted-EPUID            | M    | This Information Element shall contain the EPC ProSe User ID (EPUID) of the targeted UE to which the Proximity Alert shall be sent.     |
+| Assistance Information (See 6.3.3)    | Assistance-Info           | O    | If present, this Information Element shall contain the assistance information for WLAN direct discovery and communications if required. |
+| Supported Features (See 6.3.24)       | Supported-Features        | O    | If present, this information element shall contain the list of features supported by the origin host.                                   |
+
+**Table 5.9.1-2: ProSe Proximity Alert Answer**
+
+| Information element name        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                      |
+| Result (See 6.4)                | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Announcing Not Authorized<br>- No Discovery Filter |
+
+### 5.9.2 Detailed behaviour of the ProSe Function of the targeted UE
+
+The ProSe Function in charge of the Proximity request shall make use of this procedure to indicate to the ProSe Function in charge of the targeted UE that the UEs enter into proximity and a Proximity Alert should be sent to the targeted UE. The ProSe Function shall include in the request the Application Layer User ID and the EPUID of the requesting UE entering into proximity. It may include assistance information for WLAN direct discovery and communications if required the WLAN indication was included in the Proximity request.
+
+### 5.9.3 Detailed behaviour of the ProSe Function of the requesting UE
+
+When receiving a ProSe Proximity Alert request, the ProSe Function of the targeted UE, shall, in the following order:
+
+1. Check whether the EPC ProSe User Identity of the targeted UE exists. If not, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+2. Check whether the proximity request is authorized by the user. If not, the Proximity request is not authorized by the user, a Result Code of DIAMETER\_ERROR\_PROXIMITY\_UNAUTHORIZED shall be returned.
+
+If there is an error in any of the above steps then the ProSe Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+Otherwise, the ProSe Function shall acknowledge the reception of the ProSe Proximity Alert request and shall set the Result Code to "DIAMETER\_SUCCESS" in the response. The ProSe Function shall forward the Proximity Alert to the requesting UE.
+
+## 5.10 ProSe Direct Discovery Authorization Update
+
+### 5.10.1 General
+
+The ProSe Direct Discovery Authorization Update Procedure shall be used between the ProSe Function in the HPLMN and the ProSe Function in a local PLMN or VPLMN to update authorization for access to the discovery resources and perform ProSe Direct Discovery. The procedure shall be invoked by the ProSe Function in the HPLMN and is used:
+
+- to provide the ProSe Function in Local PLMN with an update for banned users.
+
+This procedure is mapped to the commands ProSe-Discovery-Request/Answer (PDR/PDA) in the Diameter application specified in clause 6.
+
+Table 5.10.1-1 specifies the involved information elements for the request.
+
+Table 5.10.1-2 specifies the involved information elements for the answer.
+
+**Table 5.10.1-1: ProSe Direct Discovery Authorization Update Request**
+
+| Information element name                     | Mapping to Diameter AVP | Cat. | Description                                                                                                                                          |
+|----------------------------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Discovery Authorization Request (See 6.3.53) | Discovery-Auth-Request  | M    | This information element shall contain the information elements used in discovery authorization request.                                             |
+| Supported Features (See 6.3.24)              | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                |
+| Discovery Entry ID (See 6.3.59)              | Discovery-Entry-ID      | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request. |
+
+**Table 5.10.1-2: ProSe Direct Discovery Authorization Update Answer**
+
+| Information element name                      | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24)               | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                 |
+| Result (See 6.4)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Announcing Not Authorized<br>- No Associated Discovery Filter |
+| Discovery Authorization Response (See 6.3.53) | Discovery-Auth-Response           | C    | This information element shall contain the information elements used in discovery authorization response. This information element shall be present if the Result Code AVP is DIAMETER_SUCCESS.                                                                                                                                                                                                                                                                                       |
+| Discovery Entry ID (See 6.3.59)               | Discovery-Entry-ID                | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request.                                                                                                                                                                                                                                                                                                                                  |
+
+### 5.10.2 Detailed behaviour of the HPLMN ProSe Function
+
+The ProSe Function in the HPLMN shall make use of this procedure to revoke permissions to discover a ProSe Restricted Code given to users served by the ProSe Function located in a Local PLMN. The HPLMN ProSe Function shall include in the request the Discovery Entry ID and shall include in the Discovery Authorization Request the Discovery Type set to "MONITORING\_UPDATE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, the ProSe-restricted-Code, Banned RPAUID and Banned PDUID of a monitoring target. When
+
+receiving the ProSe Direct Discovery Authorization Update response with the Result Code set to "DIAMETER\_SUCCESS" for a request with the Discovery Type set to "MONITORING\_UPDATE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the HPLMN ProSe Function shall start a timer to wait for the ProSe Function in Local PLMN/VPLMN to report the result of the Direct Discovery Authorization Update procedure for the monitoring operation, i.e., whether the ProSe Discovery Filter(s) for monitoring this ProSe Restricted Code has been successfully revoked in the banned UE.
+
+### 5.10.3 Detailed behaviour of the ProSe Function in the local PLMN or VPLMN
+
+When receiving a ProSe Direct Discovery Authorization Update request, the ProSe Function in the local PLMN or VPLMN shall process the request in the following order to check whether the monitoring is authorized.
+
+- The ProSe function shall check if the Banned PDUID belongs to its own PLMN.
+  - If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_PDUID" in the response sent by the ProSe Function.
+  - If the Banned PDUID belongs to its own PLMN, the ProSe function may check if the requesting RPAUID is allowed to discover the Banned RPAUID.
+    - If not, the experimental result code shall be set to "DIAMETER\_ERROR\_INVALID\_TARGET\_RPAUID" in the response sent by the ProSe Function;
+    - Otherwise, the ProSe Function shall set the result code to "DIAMETER\_SUCCESS" in the response.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+## 5.11 ProSe Direct Discovery Authorization Update Result
+
+### 5.11.1 General
+
+The ProSe Direct Discovery Authorization Update Result Procedure shall be used between the ProSe Function in the local PLMN and the ProSe Function in the HPLMN to report the result of ProSe Direct Discovery Authorization Update in Local PLMN to the the ProSe Function in the HPLMN. In this case the procedure shall be invoked by the ProSe Function in the local PLMN and is used:
+
+- to report the result of Direct Discovery Authorization Update procedure initiated by the ProSe Function in the HPLMN.
+
+This procedure is mapped to the commands ProSe-Discovery-Request/Answer (PDR/PDA) in the Diameter application specified in clause 6.
+
+Table 5.11.1-1 specifies the involved information elements for the request.
+
+Table 5.11.1-2 specifies the involved information elements for the answer.
+
+**Table 5.11.1-1: ProSe Direct Discovery Authorization Update Result Request**
+
+| Information element name                     | Mapping to Diameter AVP | Cat. | Description                                                                                                                                          |
+|----------------------------------------------|-------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Discovery Authorization Request (See 6.3.53) | Discovery-Auth-Request  | M    | This information element shall contain the information elements used in discovery authorization request.                                             |
+| Supported Features (See 6.3.24)              | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                |
+| Discovery Entry ID (See 6.3.59)              | Discovery-Entry-ID      | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request. |
+
+**Table 5.11.1-2: ProSe Direct Discovery Authorization Update Result Answer**
+
+| Information element name                      | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-----------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 6.3.24)               | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                 |
+| Result (See 6.4)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for PC6/PC7 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- Announcing Not Authorized<br>- No Associated Discovery Filter |
+| Discovery Authorization Response (See 6.3.53) | Discovery-Auth-Response           | C    | This information element shall contain the information elements used in discovery authorization response. This information element shall be present if the Result Code AVP is DIAMETER_SUCCESS.                                                                                                                                                                                                                                                                                       |
+| Discovery Entry ID (See 6.3.59)               | Discovery-Entry-ID                | C    | This Information Element contains the discovery entry ID used by the sending ProSe Function to identify the discovery entry related to this request.                                                                                                                                                                                                                                                                                                                                  |
+
+### 5.11.2 Detailed behaviour of the ProSe Function in the local PLMN
+
+The ProSe Function in the local PLMN shall make use of this procedure to report to the ProSe Function in HPLMN the result of the ProSe Direct Discovery Authorization Update for restricted ProSe Direct Discovery. The local PLMN ProSe Function shall include in the Discovery Authorization Update Result Request the Discovery Entry ID and the Discovery Type set to "MONITORING\_RESPONSE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the application identity, the ProSe-Restricted-Code, Banned RPAUID and Banned PDUID of a monitoring target, result of the monitoring update operation.
+
+### 5.11.3 Detailed behaviour of the HPLMN ProSe Function
+
+When receiving a ProSe Direct Discovery Authorization Update Result request (Discovery Type set to "MONITORING\_RESPONSE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY" in the PDR command), the ProSe Function in the HPLMN shall check whether there exists a discovery entry matching the Discovery Entry ID included in the request. If yes, then the ProSe Function shall update the result for the given ProSe Restricted Code or ProSe Restricted Code Prefix in this entry regarding the revocation operation for banned RPAUID and banned PDUID indicated in the request message.
+
+- If not, the experimental result code shall be set to "DIAMETER\_ERROR\_NO\_ASSOCIATED\_RESTRICTED\_CODE" in the response sent by the ProSe Function.
+- If it exists, the ProSe Function shall set the result code to "DIAMETER\_SUCCESS" in the Discovery Authorization Update Result response and shall store the outcome of the operation provided to be able to forward this to the UE.
+
+If the ProSe Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+# 6 Protocol Specification and Implementation
+
+## 6.1 Introduction
+
+### 6.1.1 Use of Diameter base protocol
+
+The Diameter Base Protocol as specified in IETF RFC 6733 [29] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.
+
+### 6.1.2 Securing Diameter Messages
+
+For secure transport of Diameter messages, see 3GPP TS 33.210 [8].
+
+### 6.1.3 Accounting functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the PC6/PC7 interfaces.
+
+### 6.1.4 Use of sessions
+
+Between the ProSe Functions, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.
+
+The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [29]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+### 6.1.5 Transport protocol
+
+Diameter messages over the PC6/PC7 interfaces shall make use of SCTP IETF RFC 4960 [9].
+
+### 6.1.6 Routing considerations
+
+This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
+
+The Destination-Realm AVP shall contain the network domain name of the targeted ProSe Function. The network domain name is either known by the sending ProSe Function or derived from the PLMN-Id of the targeted ProSe Function to construct the EPC Home Network Realm/Domain, as indicated in 3GPP TS 23.003 [4], clause 19.2.
+
+If a ProSe Function knows the address/name of the ProSe Function in charge of a given UE, and the associated network domain name, both the Destination-Realm and Destination-Host AVPs shall be present in the request.
+
+If a ProSe Function knows only the network domain name, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node.
+
+Consequently, the Destination-Realm AVP is declared as mandatory and the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a ProSe Function.
+
+If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes.
+
+### 6.1.7 Advertising Application Support
+
+The ProSe Functions shall advertise support of the Diameter Inter ProSe Functions Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [29].
+
+### 6.1.8 Diameter Application Identifier
+
+The Diameter Inter ProSe Functions Application protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the Diameter Inter ProSe Functions application is 16777340 (allocated by IANA). The same Diameter application identifier is used over the PC6 interface and the PC7 interface.
+
+### 6.1.9 Use of the Supported-Features AVP
+
+When new functionality is introduced on the PC6/PC7 interfaces, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the PC6/PC7 interfaces is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [10].
+
+When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in 3GPP TS 29.229 [10], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+## 6.2 Commands
+
+### 6.2.1 Introduction
+
+This clause defines the Command code values and related ABNF for each command described in this specification.
+
+### 6.2.2 Command-Code values
+
+This csublause defines Command-Code values for the Diameter Inter ProSe Functions application used over the PC6/PC7 interfaces as allocated by IANA.
+
+Every command is defined by means of the ABNF syntax IETF RFC 5234 [11], according to the Command Code Format (CCF) specification defined in IETF RFC 6733 [29]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [29] shall apply.
+
+The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
+
+**NOTE:** The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with IETF RFC 6733 [29].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.2.2-1: Command-Code values for Diameter ProSe Inter Functions Application**
+
+| Command-Name                    | Abbreviation | Code    | Clause |
+|---------------------------------|--------------|---------|--------|
+| ProSe-Authorization-Request     | PAR          | 8388668 | 6.2.3  |
+| ProSe-Authorization-Answer      | PAA          | 8388668 | 6.2.4  |
+| ProSe-Discovery-Request         | PDR          | 8388669 | 6.2.5  |
+| ProSe-Discovery-Answer          | PDA          | 8388669 | 6.2.6  |
+| ProSe-Match-Request             | PMR          | 8388670 | 6.2.7  |
+| ProSe-Match-Answer              | PMA          | 8388670 | 6.2.8  |
+| ProSe-Match-Report-Info-Request | PIR          | 8388671 | 6.2.9  |
+| ProSe-Match-Report-Info-Answer  | PIA          | 8388671 | 6.2.10 |
+| ProSe-Proximity-Request         | PRR          | 8388672 | 6.2.11 |
+| ProSe-Proximity-Answer          | PRA          | 8388672 | 6.2.12 |
+| ProSe-Location-Update-Request   | PLR          | 8388673 | 6.2.13 |
+| ProSe-Location-Update-Answer    | PLA          | 8388673 | 6.2.14 |
+| ProSe-Alert-Request             | ALR          | 8388674 | 6.2.15 |
+| ProSe-Alert-Answer              | ALA          | 8388674 | 6.2.16 |
+| ProSe-Cancellation-Request      | PCR          | 8388675 | 6.2.17 |
+| ProSe-Cancellation-Answer       | PCA          | 8388675 | 6.2.18 |
+
+For these commands, the Application-ID field shall be set to 16777340 (application identifier of the Diameter Inter ProSe Functions interface application, allocated by IANA).
+
+### 6.2.3 ProSe-Authorization-Request (PAR) Command
+
+The ProSe-Authorization-Request (PAR) Command, indicated by the Command-Code field set to 8388668 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function in Local PLMN/VPLMN.
+
+Message Format
+
+```
+< ProSe-Authorization-Request > ::= < Diameter Header: 8388668, REQ, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ Destination-Host ]
+{ Destination-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+{ User-Identity }
+{ Visited-PLMN-Id }
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+```
+
+### 6.2.4 ProSe-Authorization-Answer (PAA) Command
+
+The ProSe-Authorization-Answer (PAA) Command, indicated by the Command-Code field set to 8388668 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in Local PLMN/VPLMN to the ProSe Function in the HPLMN.
+
+Message Format
+
+```
+< ProSe-Authorization-Answer > ::= < Diameter Header: 8388668, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+```
+
+```
+
+        [ Vendor-Specific-Application-Id ]
+        [ Result-Code ]
+        [ Experimental-Result ]
+        { Auth-Session-State }
+        { Origin-Host }
+        { Origin-Realm }
+        *[ Supported-Features ]
+        [ OC-Supported-Features ]
+        [ OC-OLR ]
+        *[ Load ]
+        [ ProSe-Direct-Allowed ]
+        [ Validity-Time-Announce ]
+        [ Validity-Time-Monitor ]
+        [ Validity-Time-Communication ]
+        [ Authorized-Discovery-Range ]
+        *[ AVP ]
+        [ Failed-AVP ]
+        *[ Proxy-Info ]
+    *[ Route-Record ]
+
+```
+
+### 6.2.5 ProSe-Discovery-Request (PDR) Command
+
+The ProSe-Discovery-Request (PDR) Command, indicated by the Command-Code field set to 8388669 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function in Local PLMN.
+
+#### Message Format
+
+```
+
+< ProSe-Discovery-Request > ::= < Diameter Header: 8388669, REQ, PXY, 16777340 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    { Discovery-Auth-Request }
+    [ Discovery-Entry-ID ]
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+
+```
+
+### 6.2.6 ProSe-Discovery-Answer (PDA) Command
+
+The ProSe-Discovery-Answer (PDA) Command, indicated by the Command-Code field set to 8388669 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in Local PLMN to the ProSe Function in the HPLMN.
+
+#### Message Format
+
+```
+
+< ProSe-Discovery-Answer > ::= < Diameter Header: 8388669, PXY, 16777340 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+
+```
+
+```
+
+[ OC-OLR ]
+*[ Load ]
+[ Discovery-Auth-Response ]
+[ Discovery-Entry-ID ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.7 ProSe-Match-Request (PMR) Command
+
+The ProSe-Match-Request (PMR) Command, indicated by the Command-Code field set to 8388670 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function in Local PLMN.
+
+Message Format
+
+```
+
+< ProSe-Match-Request > ::= < Diameter Header: 8388670, REQ, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ Destination-Host ]
+{ Destination-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+{ Match-Request }
+[ PMR-Flags ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.8 ProSe-Match-Answer (PMA) Command
+
+The ProSe-Match-Answer (PMA) Command, indicated by the Command-Code field set to 8388670 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in Local PLMN to the ProSe Function in the HPLMN.
+
+Message Format
+
+```
+
+< ProSe-Match-Answer > ::= < Diameter Header: 8388670, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+*[ Match-Report ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.9 ProSe-Match-Report-Info-Request (PIR) Command
+
+The ProSe-Match-Report-Info-Request (PIR) Command, indicated by the Command-Code field set to 8388671 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN of the monitoring UE to the ProSe Function of the PLMN in which the announcing UE is roaming.
+
+#### Message Format
+
+```
+< ProSe-Match-Report-Info-Request > ::= < Diameter Header: 8388671, REQ, PXY, 16777340 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    { Match-Report-Info }
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.10 ProSe-Match-Report-Info-Answer (PIA) Command
+
+The ProSe-Match-Report-Info-Answer (PIA) Command, indicated by the Command-Code field set to 8388671 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function of the PLMN in which the announcing UE is roaming to the ProSe Function in the HPLMN of the monitoring UE.
+
+#### Message Format
+
+```
+< ProSe-Match-Report-Info-Answer > ::= < Diameter Header: 8388671, PXY, 16777340 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    [ OC-OLR ]
+    *[ Load ]
+    *[ AVP ]
+    [ Failed-AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.11 ProSe-Proximity-Request (PRR) Command
+
+The ProSe-Proximity-Request (PRR) Command, indicated by the Command-Code field set to 8388672 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+#### Message Format
+
+```
+< ProSe-Proximity-Request > ::= < Diameter Header: 8388672, REQ, PXY, 16777340 >
+    < Session-Id >
+```
+
+```
+
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ Destination-Host ]
+{ Destination-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+{ PRR-Flags }
+{ Requesting-EPUID }
+{ Targeted-EPUID }
+{ Time-Window }
+{ Location-Estimate }
+[ Location-Update-Trigger ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.12 ProSe-Proximity-Answer (PRA) Command
+
+The ProSe-Proximity-Answer (PRA) Command, indicated by the Command-Code field set to 8388672 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+#### Message Format
+
+```
+
+< ProSe-Proximity-Answer > ::= < Diameter Header: 8388672, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+[ Location-Estimate ]
+[ WLAN-Link-Layer-Id ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.13 ProSe-Location-Update-Request (PLR) Command
+
+The ProSe-Location-Update-Request (PLR) Command, indicated by the Command-Code field set to 8388673 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+#### Message Format
+
+```
+
+< ProSe-Location-Update-Request > ::= < Diameter Header: 8388673, REQ, PXY, 16777340 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+
+```
+
+[ Destination-Host ]  
+{ Destination-Realm }  
+\*[ Supported-Features ]  
+[ OC-Supported-Features ]  
+{ Targeted-EPUID }  
+{ Location-Estimate }  
+\*[ AVP ]  
+\*[ Proxy-Info ]  
+\*[ Route-Record ]
+
+### 6.2.14 ProSe-Location-Update-Answer (PLA) Command
+
+The ProSe-Location-Update-Answer (PLA) Command, indicated by the Command-Code field set to 8388673 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+#### Message Format
+
+< ProSe-Location-Update-Answer > ::= < Diameter Header: 8388673, PXY, 16777340 >  
+< Session-Id >  
+[ DRMP ]  
+[ Vendor-Specific-Application-Id ]  
+[ Result-Code ]  
+[ Experimental-Result ]  
+{ Auth-Session-State }  
+{ Origin-Host }  
+{ Origin-Realm }  
+\*[ Supported-Features ]  
+[ OC-Supported-Features ]  
+[ OC-OLR ]  
+\*[ Load ]  
+\*[ AVP ]  
+[ Failed-AVP ]  
+\*[ Proxy-Info ]  
+\*[ Route-Record ]
+
+### 6.2.15 ProSe-Alert-Request (ALR) Command
+
+The ProSe-Alert-Request (ALR) Command, indicated by the Command-Code field set to 8388674 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+#### Message Format
+
+< ProSe-Alert-Request > ::= < Diameter Header: 8388674, REQ, PXY, 16777340 >  
+< Session-Id >  
+[ DRMP ]  
+[ Vendor-Specific-Application-Id ]  
+{ Auth-Session-State }  
+{ Origin-Host }  
+{ Origin-Realm }  
+[ Destination-Host ]  
+{ Destination-Realm }  
+\*[ Supported-Features ]  
+[ OC-Supported-Features ]  
+{ App-Layer-User-Id }  
+{ Targeted-EPUID }  
+[ Assistance-Info ]  
+\*[ AVP ]  
+\*[ Proxy-Info ]  
+\*[ Route-Record ]
+
+### 6.2.16 ProSe-Alert-Answer (ALA) Command
+
+The ProSe-Alert-Answer (ALA) Command, indicated by the Command-Code field set to 8388674 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function of another PLMN.
+
+Message Format
+
+```
+< ProSe-Alert-Answer > ::= < Diameter Header: 8388674, PXY, 16777340 >
+                        < Session-Id >
+                        [ DRMP ]
+                        [ Vendor-Specific-Application-Id ]
+                        [ Result-Code ]
+                        [ Experimental-Result ]
+                        { Auth-Session-State }
+                        { Origin-Host }
+                        { Origin-Realm }
+                        *[ Supported-Features ]
+                        [ OC-Supported-Features ]
+                        [ OC-OLR ]
+                        *[ Load ]
+                        *[ AVP ]
+                        [ Failed-AVP ]
+                        *[ Proxy-Info ]
+                        *[ Route-Record ]
+```
+
+### 6.2.17 ProSe-Cancellation-Request (PCR) Command
+
+The ProSe-Cancellation-Request (PCR) Command, indicated by the Command-Code field set to 8388675 and the "R" bit set in the Command Flags field, is sent from the ProSe Function in the HPLMN to the ProSe Function in a local/visited PLMN.
+
+Message Format
+
+```
+< ProSe-Cancellation-Request > ::= < Diameter Header: 8388675, REQ, PXY, 16777340 >
+                        < Session-Id >
+                        [ DRMP ]
+                        [ Vendor-Specific-Application-Id ]
+                        { Auth-Session-State }
+                        { Origin-Host }
+                        { Origin-Realm }
+                        [ Destination-Host ]
+                        { Destination-Realm }
+                        *[ Supported-Features ]
+                        [ OC-Supported-Features ]
+                        { Requesting-EPUID }
+                        { Targeted-EPUID }
+                        *[ AVP ]
+                        *[ Proxy-Info ]
+                        *[ Route-Record ]
+```
+
+### 6.2.18 ProSe-Cancellation-Answer (PCA) Command
+
+The ProSe-Cancellation-Answer (PCA) Command, indicated by the Command-Code field set to 8388675 and the "R" bit cleared in the Command Flags field, is sent from the ProSe Function in a local/visited PLMN to the ProSe Function in the HPLMN.
+
+Message Format
+
+```
+< ProSe-Cancellation-Answer > ::= < Diameter Header: 8388675, PXY, 16777340 >
+                        < Session-Id >
+                        [ DRMP ]
+```
+
+[ Vendor-Specific-Application-Id ]  
+[ Result-Code ]  
+[ Experimental-Result ]  
+{ Auth-Session-State }  
+{ Origin-Host }  
+{ Origin-Realm }  
+\*[ Supported-Features ]  
+[ OC-Supported-Features ]  
+[ OC-OLR ]  
+\*[ Load ]  
+\*[ AVP ]  
+[ Failed-AVP ]  
+\*[ Proxy-Info ]  
+\*[ Route-Record ]
+
+## 6.3 Information Elements
+
+### 6.3.1 General
+
+The following table (table 6.3.1-1) specifies the Diameter AVPs defined for the PC6/PC7 interfaces, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).
+
+For all AVPs which contain bit masks and are of the type Unsigned32 e.g., PRR-Flags, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 shall be used.
+
+**Table 6.3.1-1: PC6/PC7 specific Diameter AVPs**
+
+| Attribute Name                     | AVP Code | Clause defined | Value Type  | AVP Flag rules |     |            |          |           |
+|------------------------------------|----------|----------------|-------------|----------------|-----|------------|----------|-----------|
+|                                    |          |                |             | Must           | May | Should not | Must not | May Encr. |
+| App-Layer-User-Id                  | 3801     | 6.3.2          | UTF8String  | M, V           |     |            |          | No        |
+| Assistance-info                    | 3802     | 6.3.3          | Grouped     | M, V           |     |            |          | No        |
+| Assistance-Info-Validity-Timer     | 3803     | 6.3.4          | Unsigned32  | M, V           |     |            |          | No        |
+| Discovery-Type                     | 3804     | 6.3.5          | Unsigned32  | M, V           |     |            |          | No        |
+| Filter-Id                          | 3805     | 6.3.9          | OctetString | M, V           |     |            |          | No        |
+| MAC-Address                        | 3806     | 6.3.11         | UTF8String  | M, V           |     |            |          | No        |
+| Match-Report                       | 3807     | 6.3.12         | Grouped     | M, V           |     |            |          | No        |
+| Operating-Channel                  | 3808     | 6.3.14         | Unsigned32  | M, V           |     |            |          | No        |
+| P2P-Features                       | 3809     | 6.3.15         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-App-Code                     | 3810     | 6.3.16         | OctetString | M, V           |     |            |          | No        |
+| ProSe-App-Id                       | 3811     | 6.3.17         | UTF8String  | M, V           |     |            |          | No        |
+| ProSe-App-Mask                     | 3812     | 6.3.18         | OctetString | M, V           |     |            |          | No        |
+| ProSe-Discovery-Filter             | 3813     | 6.3.20         | Grouped     | M, V           |     |            |          | No        |
+| PRR-Flags                          | 3814     | 6.3.21         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-Validity-Timer               | 3815     | 6.3.22         | Unsigned32  | M, V           |     |            |          | No        |
+| Requesting-EPUID                   | 3816     | 6.3.23         | UTF8String  | M, V           |     |            |          | No        |
+| Targeted-EPUID                     | 3817     | 6.3.26         | UTF8String  | M, V           |     |            |          | No        |
+| Time-Window                        | 3818     | 6.3.27         | Unsigned32  | M, V           |     |            |          | No        |
+| WiFi-P2P-Assistance-Info           | 3819     | 6.3.30         | Grouped     | M, V           |     |            |          | No        |
+| WLAN-Assistance-Info               | 3820     | 6.3.31         | Grouped     | M, V           |     |            |          | No        |
+| WLAN-Link-Layer-Id                 | 3821     | 6.3.32         | OctetString | M, V           |     |            |          | No        |
+| WLAN-Link-Layer-Id-List            | 3822     | 6.3.33         | Grouped     | M, V           |     |            |          | No        |
+| Location-Update-Trigger            | 3823     | 6.3.42         | Grouped     | M, V           |     |            |          | No        |
+| Location-Update-Event-Type         | 3824     | 6.3.43         | Unsigned32  | M, V           |     |            |          | No        |
+| Change-Of-Area-Type                | 3825     | 6.3.44         | Grouped     | M, V           |     |            |          | No        |
+| Location-Update-Event-Trigger      | 3826     | 6.3.45         | Unsigned32  | M, V           |     |            |          | No        |
+| Report-Cardinality                 | 3827     | 6.3.46         | Enumerated  | M, V           |     |            |          | No        |
+| Minimum-Interval-Time              | 3828     | 6.3.47         | Unsigned32  | M, V           |     |            |          | No        |
+| Periodic-Location-Type             | 3829     | 6.3.48         | Grouped     | M, V           |     |            |          | No        |
+| Location-Report-Interval-Time      | 3830     | 6.3.49         | Unsigned32  | M, V           |     |            |          | No        |
+| Total-Number-Of-Reports            | 3831     | 6.3.50         | Unsigned32  | M, V           |     |            |          | No        |
+| Validity-Time-Announce             | 3832     | 6.3.36         | Unsigned32  | M, V           |     |            |          | No        |
+| Validity-Time-Monitor              | 3833     | 6.3.37         | Unsigned32  | M, V           |     |            |          | No        |
+| Validity-Time-Communication        | 3834     | 6.3.38         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-App-Code-Info                | 3835     | 6.3.39         | Grouped     | M, V           |     |            |          | No        |
+| MIC                                | 3836     | 6.3.40         | OctetString | M, V           |     |            |          | No        |
+| UTC-based-Counter                  | 3837     | 6.3.41         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-Match-Refresh-Timer          | 3838     | 6.3.52         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-Metadata-Index-Mask          | 3839     | 6.3.60         | OctetString | V              |     |            | M        | No        |
+| App-Identifier                     | 3840     | 6.3.61         | Group       | V              |     |            | M        | No        |
+| OS-ID                              | 3841     | 6.3.62         | OctetString | V              |     |            | M        | No        |
+| OS-App-ID                          | 3842     | 6.3.63         | UTF8String  | V              |     |            | M        | No        |
+| Requesting-RPAUID                  | 3843     | 6.3.64         | UTF8String  | V              |     |            | M        | No        |
+| Target-RPAUID                      | 3844     | 6.3.65         | UTF8String  | V              |     |            | M        | No        |
+| Target-PDUID                       | 3845     | 6.3.66         | OctetString | V              |     |            | M        | No        |
+| ProSe-Restricted-Code              | 3846     | 6.3.67         | OctetString | V              |     |            | M        | No        |
+| ProSe-Restricted-Code-Suffix-Range | 3847     | 6.3.68         | OctetString | V              |     |            | M        | No        |
+| Beginning-Suffix                   | 3848     | 6.3.69         | OctetString | V              |     |            | M        | No        |
+| Ending-Suffix                      | 3849     | 6.3.70         | OctetString | V              |     |            | M        | No        |
+| Discovery-Entry-ID                 | 3850     | 6.3.59         | Unsigned32  | V              |     |            | M        | No        |
+| Match-Timestamp                    | 3851     | 6.3.71         | Time        | V              |     |            | M        | No        |
+| PMR-Flags                          | 3852     | 6.3.57         | Unsigned32  | M, V           |     |            |          | No        |
+| ProSe-Application-Metadata         | 3853     | 6.3.58         | UTF8String  | M, V           |     |            |          | No        |
+| Discovery-Auth-Request             | 3854     | 6.3.53         | Grouped     | M, V           |     |            |          | No        |
+| Discovery-Auth-Response            | 3855     | 6.3.54         | Grouped     | M, V           |     |            |          | No        |
+| Match-Request                      | 3856     | 6.3.55         | Grouped     | M, V           |     |            |          | No        |
+| Match-Report-Info                  | 3857     | 6.3.56         | Grouped     | M, V           |     |            |          | No        |
+| Banned-RPAUID                      | 3858     | 6.3.73         | UTF8String  | V              |     |            | M        | No        |
+| Banned-PDUID                       | 3859     | 6.3.74         | OctetString | V              |     |            | M        | No        |
+| Code-Receiving-Security-Material   | 3860     | 6.3.75         | Grouped     | V              |     |            | M        | No        |
+
+| Attribute Name                                                                                                                                                                                                                                                                                                                                                                         | AVP Code | Clause defined | Value Type  | AVP Flag rules |     |            |          |           |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|-------------|----------------|-----|------------|----------|-----------|
+|                                                                                                                                                                                                                                                                                                                                                                                        |          |                |             | Must           | May | Should not | Must not | May Encr. |
+| Code-Sending-Security-Material                                                                                                                                                                                                                                                                                                                                                         | 3861     | 6.3.76         | Grouped     | V              |     |            | M        | No        |
+| DUSK                                                                                                                                                                                                                                                                                                                                                                                   | 3862     | 6.3.77         | OctetString | V              |     |            | M        | No        |
+| DUIK                                                                                                                                                                                                                                                                                                                                                                                   | 3863     | 6.3.78         | OctetString | V              |     |            | M        | No        |
+| DUCK                                                                                                                                                                                                                                                                                                                                                                                   | 3864     | 6.3.79         | OctetString | V              |     |            | M        | No        |
+| MIC-Check-indicator                                                                                                                                                                                                                                                                                                                                                                    | 3865     | 6.3.80         | Unsigned32  | V              |     |            | M        | No        |
+| Encrypted-Bitmask                                                                                                                                                                                                                                                                                                                                                                      | 3866     | 6.3.81         | OctetString | V              |     |            | M        | No        |
+| ProSe-App-Code-Suffix-Range                                                                                                                                                                                                                                                                                                                                                            | 3867     | 6.3.82         | OctetString | V              |     |            | M        | No        |
+| PC5-tech                                                                                                                                                                                                                                                                                                                                                                               | 3868     | 6.3.84         | OctetString | V              |     |            | M        | No        |
+| NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [29].                                                                                                                               |          |                |             |                |     |            |          |           |
+| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. |          |                |             |                |     |            |          |           |
+
+The following table (table 6.3.1-2) specifies the Diameter AVPs re-used by the PC6/PC7 interfaces from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within PC6/PC7 interfaces.
+
+Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter Base Protocol, do not need to be supported. The AVPs from Diameter Base Protocol are not included in table 6.3.1-2.
+
+Table 6.3.1-2: PC6/PC7 re-used Diameter AVPs
+
+| Attribute Name             | Reference           | Comments          | M-bit        |
+|----------------------------|---------------------|-------------------|--------------|
+| Supported-Features         | 3GPP TS 29.229 [10] |                   |              |
+| EAP-Master-Session-Key     | IETF RFC 4072 [12]  |                   |              |
+| Feature-List-ID            | 3GPP TS 29.229 [10] |                   |              |
+| Feature-List               | 3GPP TS 29.229 [10] | See clause 7.3.10 |              |
+| MSISDN                     | 3GPP TS 29.329 [5]  |                   |              |
+| User-Name                  | IETF RFC 6733 [29]  |                   |              |
+| Location-Estimate          | 3GPP TS 32.299 [13] |                   |              |
+| ProSe-Direct-Allowed       | 3GPP TS 29.344 [14] |                   |              |
+| Authorized-Discovery-Range | 3GPP TS 29.344 [14] |                   |              |
+| SSID                       | 3GPP TS 29.273 [15] |                   |              |
+| Visited-PLMN-Id            | 3GPP TS 29.272 [16] |                   |              |
+| User-Identifier            | 3GPP TS 29.336 [18] |                   |              |
+| OC-Supported-Features      | IETF RFC 7683 [21]  | See clause 6.3.34 | Must set     |
+| OC-OLR                     | IETF RFC 7683 [21]  | See clause 6.3.35 | Must set     |
+| DRMP                       | IETF RFC 7944 [27]  | see clause 6.3.72 | Must not set |
+| Service-Result             | 3GPP TS 29.336 [18] |                   |              |
+| Load                       | IETF RFC 8583 [28]  | See clause 6.3.83 | Must not set |
+
+NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies.
+
+NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
+
+### 6.3.2 App-Layer-User-Id
+
+The App-Layer-User-Id AVP is of type UTF8String. This AVP contains an identity identifying a user within the context of a specific application (e.g. alice@social.net).
+
+### 6.3.3 Assistance-info
+
+The Assistance-Info AVP is of type Grouped. It shall contain the information for direct discovery and communications between UEs.
+
+The AVP format shall conform to:
+
+```
+Assistance-Info ::= <AVP header: 3802 10415>
+                    [ WLAN-Assistance-Info ]
+                    *[AVP]
+```
+
+### 6.3.4 Assistance-Info-Validity-Timer
+
+The Assistance-Info-Validity-Timer AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of the provided assistance information.
+
+### 6.3.5 Discovery-Type
+
+The Discovery-Type AVP is of type Unsigned32 and contains a 32-bit address space representing types of Direct Discovery Authorization Request. The following values are defined:
+
+#### ANNOUNCING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY (0)
+
+This value is used when the Direct Discovery Authorization Request message is sent for a UE requesting authorization for announcing in open Prose Direct Discovery (Model A).
+
+#### MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY (1)
+
+This value is used when the Direct Discovery Authorization Request message is sent for a UE requesting authorization for monitoring in open Prose Direct Discovery (Model A).
+
+#### ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (2)
+
+This value is used when the Direct Discovery Authorization Request message is sent for a UE requesting authorization for announcing in restricted Prose Direct Discovery (Model A).
+
+#### MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (3)
+
+This value is used when the Direct Discovery Authorization Request message is sent for a UE requesting authorization for monitoring in restricted Prose Direct Discovery (Model A).
+
+#### DISCOVEREE\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (4)
+
+This value is used when the Direct Discovery Authorization Request message is sent for a discoveree UE requesting authorization for monitoring in restricted Prose Direct Discovery (Model B).
+
+#### DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (5)
+
+This value is used when the Direct Discovery Authorization Request message is sent to the ProSe Function in local PLMN for a discoverer UE requesting authorization for announcing in restricted Prose Direct Discovery (Model B).
+
+#### DISCOVERER\_ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (6)
+
+This value is used when the Direct Discovery Authorization Request message is sent to the ProSe Function in the visited PLMN for a discoverer UE requesting authorization for announcing in restricted Prose Direct Discovery (Model B).
+
+#### MONITORING\_UPDATE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (7)
+
+This value is used when the Direct Discovery Authorization Request message is sent for the ProSe Function requesting to ban a user of an authorization for monitoring in restricted Prose Direct Discovery (Model A).
+
+#### MONITORING\_RESPONSE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY (8)
+
+This value is used when the Direct Discovery Authorization Request message is sent for the ProSe Function reporting the result of an authorization for monitoring in restricted Prose Direct Discovery (Model A).
+
+### 6.3.6 EAP-Master-Session-Key
+
+The EAP-Master-Session-Key AVP is of type OctetString and it shall contain keying material for protecting the communications between UEs. This AVP is defined in the IETF RFC 4072 [12]
+
+### 6.3.7 Feature-List-ID AVP
+
+The syntax of this AVP is defined in 3GPP TS 29.229 [10]. For this release, the Feature-List-ID AVP value shall be set to 1.
+
+### 6.3.8 Feature-List AVP
+
+The syntax of this AVP is defined in 3GPP TS 29.229 [10]. A null value indicates that there is no feature used by the application.
+
+NOTE: There is no feature defined for this release.
+
+### 6.3.9 Filter-Id
+
+The Filter-Id AVP is of type OctetString. This AVP shall contain the identifier of a Discovery Filter.
+
+### 6.3.10 Location-Estimate
+
+The Location-Estimate AVP is of type OctetString and it shall contain an estimate of the location of an MS in universal coordinates and the accuracy of the estimate. This AVP is defined in the 3GPP TS 32.299 [13].
+
+### 6.3.11 MAC-Address
+
+The MAC-Address AVP is of type UTF8String and it shall contain a 6-octet MAC address used as link layer identifier for discovery and communication. It shall be encoded in upper-case ASCII characters with the octet values separated by dash characters. It shall contain a string of 17 octets. Example: "00-10-A4-23-19-C0".
+
+### 6.3.12 Match-Report
+
+The Match-Report AVP is of type Grouped. It shall contain the information elements used in ProSe Match Report answer.
+
+The AVP format shall conform to:
+
+```
+Match-Report ::= <AVP header: 3807 10415>
+                { Discovery-Type }
+                [ ProSe-App-Code ]
+                [ ProSe-Metadata-Index-Mask ]
+                [ ProSe-App-Id ]
+                [ ProSe-Validity-Timer ]
+                [ ProSe-Match-Refresh-Timer ]
+                [ ProSe-Application-Metadata ]
+                [ PC5-tech ]
+                *[AVP]
+```
+
+The valid value for Discovery-Type for Match-Report AVP is:  
+"MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY",
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Match-Report shall contain a ProSe Application Code, the associated ProSe Application ID Name, the validity time for which the ProSe Application Code is valid, the associated match report refresh timer and optionally the PC5 radio technology that the UE is using.
+
+If the ProSe Application Code contains a metadata index, a ProSe-Metadata-Index-Mask AVP shall be provided for this ProSe Application Code.
+
+### 6.3.13 MSISDN
+
+The MSISDN AVP is of type OctetString. This AVP contains an MSISDN, in international number format as described in ITU-T Rec E.164 [19]. This AVP is defined in the 3GPP TS 29.329 [5].
+
+### 6.3.14 Operating-Channel
+
+The Operating-Channel AVP is of type Unsigned32 and it shall contain the operating channel in MHz on which Wi-Fi P2P discovery and communication should take place.
+
+### 6.3.15 P2P-Features
+
+The P2P-Features AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.15-1:
+
+**Table 6.3.15-1: P2P-Features**
+
+| Bit   | Name                                                                                                                         | Description                                                                                                                                                                                                                                                                           |
+|-------|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0     | Group Owner Indication                                                                                                       | This bit, when set, shall indicate that the UE should implement the Group Owner (GO) functionality specified in the Wi-Fi P2P specification [17]. When not set, this bit shall indicate the UE should behave as a Wi-Fi P2P client that attempts to discover and associate with a GO. |
+| NOTE: | Bits not defined in this table shall be cleared by the sending ProSe Function and discarded by the receiving ProSe Function. |                                                                                                                                                                                                                                                                                       |
+
+### 6.3.16 ProSe-App-Code
+
+The ProSe-App-Code AVP is of type OctetString. This AVP contains a ProSe Application Code or ProSe Application Code Prefix (see 3GPP TS 23.003 [4]) is associated with a ProSe Application ID.
+
+### 6.3.17 ProSe-App-Id
+
+The ProSe-App-Id AVP is of type UTF8String. This AVP contains a ProSe Application ID (see 3GPP TS 23.003 [4]).
+
+### 6.3.18 ProSe-App-Mask
+
+The ProSe-App-Mask AVP is of type OctetString. This AVP contains a ProSe Application Mask (see 3GPP TS 24.334 [22]).
+
+### 6.3.19 ProSe-Direct-Allowed
+
+The ProSe-Direct-Allowed AVP is of type Unsigned32 and it shall contain a bit mask that indicates the permissions for ProSe direct services for the UE in the PLMN of the responding ProSe Function. This AVP is defined in the 3GPP TS 29.344 [14].
+
+### 6.3.20 ProSe-Discovery-Filter
+
+The ProSe-Discovery-Filter AVP is of type Grouped. It shall contain a Filter ID, a ProSe Application ID name, a validity timer, a ProSe Application Code and zero or more ProSe Application Masks.
+
+The AVP format shall conform to:
+
+```
+ProSe-Discovery-Filter ::= <AVP header: 3813 10415>
+                        { Filter-Id }
+                        { ProSe-App-Id }
+                        { ProSe-Validity-Timer }
+                        { ProSe-App-Code }
+```
+
+\*[ ProSe-App-Mask ]
+
+\*[AVP]
+
+### 6.3.21 PRR-Flags
+
+The PRR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.21-1:
+
+**Table 6.3.21-1: PRR-Flags**
+
+| Bit   | Name                                                                                                                         | Description                                                                                                    |
+|-------|------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| 0     | WLAN Indication                                                                                                              | This bit, when set, shall indicate the UE is requested EPC support for WLAN direct discovery and communication |
+| NOTE: | Bits not defined in this table shall be cleared by the sending ProSe Function and discarded by the receiving ProSe Function. |                                                                                                                |
+
+### 6.3.22 ProSe-Validity-Timer
+
+The ProSe-Validity-Timer AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of a ProSe Application Code or a ProSe Discovery Filter.
+
+### 6.3.23 Requesting-EPUID
+
+The Requesting-EPUID AVP is of type UTF8String. This AVP contains an identifier for EPC-level ProSe Discovery and EPC support for WLAN direct communication that uniquely identifies a UE registered for ProSe triggering a Proximity request.
+
+### 6.3.24 Supported-Features
+
+The Supported-Features AVP is of type Grouped and it informs the destination host about the features that the origin host supports for the application. This AVP is defined in the 3GPP TS 29.229 [10].
+
+### 6.3.25 SSID
+
+The SSID AVP is of type UTF8String and it shall contain the Service Set Identifier which identifies a specific 802.11 extended service set (see IEEE Std 802.11-2012 [20]). This AVP is defined in the 3GPP TS 29.273 [15].
+
+### 6.3.26 Targeted-EPUID
+
+The Targeted-EPUID AVP is of type UTF8String. This AVP contains an identifier for EPC-level ProSe Discovery and EPC support for WLAN direct communication that uniquely identifies a UE registered for ProSe targeted by a Proximity request.
+
+### 6.3.27 Time-Window
+
+The Time-Window AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of the Proximity request.
+
+### 6.3.28 User-Identifier
+
+The User-Identifier AVP is of type Grouped. It shall contain the UE identity used as identifier of a Proximity-based service subscribed by the user (i.e. IMSI or MSISDN). This AVP is defined in the 3GPP TS 29.336 [18].
+
+### 6.3.29 Visited-PLMN-Id
+
+The Visited-PLMN-Id AVP is of type OctetString. This AVP shall contain the concatenation of MCC and MNC. This AVP is defined in the 3GPP TS 29.272 [16].
+
+### 6.3.30 WiFi-P2P-Assistance-Info
+
+The WiFi-P2P-Assistance-Info AVP is of type Grouped. It shall contain information to assist WLAN direct discovery and communication as required by the Wi-Fi P2P technology.
+
+The AVP format shall conform to:
+
+```
+WiFi-P2P-Assistance-Info ::= <AVP header: 3819 10415>
+    [ SSID ]
+    [ EAP-Master-Session-Key ]
+    [ P2P-Features ]
+    [ WLAN-Link-Layer-Id-List ]
+    [ WLAN-Link-Layer-Id-List ]
+    [ Operating-Channel ]
+    [ Assistance-Info-Validity-Timer ]
+    *[AVP]
+```
+
+### 6.3.31 WLAN-Assistance-Info
+
+The WLAN-Assistance-Info AVP is of type Grouped. It shall contain information to assist WLAN direct discovery and communication required for WLAN direct discovery and communication between UEs.
+
+The AVP format shall conform to:
+
+```
+WLAN-Assistance-Info ::= <AVP header: 3820 10415>
+    [ WiFi-P2P-Assistance-Info ]
+    *[AVP]
+```
+
+### 6.3.32 WLAN-Link-Layer-Id
+
+The WLAN-Link-Layer-Id AVP is of type Grouped. It shall contain a link layer identity used for WLAN direct discovery and/or WLAN direct communication.
+
+The AVP format shall conform to:
+
+```
+WLAN-Link-Layer-Id ::= <AVP header: 3821 10415>
+    [ MAC-Address ]
+    *AVP
+```
+
+### 6.3.33 WLAN-Link-Layer-Id-List
+
+The WLAN-Link-Layer-Id-List AVP is of type Grouped. It shall contain a list of WLAN Link Layer IDs provided to a UE implementing the Group Owner functionality in a Wi-Fi P2P group.
+
+The AVP format shall conform to:
+
+```
+WLAN-Link-Layer-Id-List ::= <AVP header: 3822 10415>
+    *[ WLAN-Link-Layer-Id ]
+    *AVP
+```
+
+### 6.3.34 OC-Supported-Features
+
+The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [21]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.35 OC-OLR
+
+The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [21]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.36 Validity-Time-Announce
+
+The Validity-Time-Announce AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of a ProSe announcing authorization policy.
+
+### 6.3.37 Validity-Time-Monitor
+
+The Validity-Time-Monitor AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of a ProSe monitoring authorization policy.
+
+### 6.3.38 Validity-Time-Communication
+
+The Validity-Time-Communication AVP is of type Unsigned32 and it shall contain the maximum number of seconds of validity of a ProSe communication authorization policy.
+
+### 6.3.39 ProSe-App-Code-Info
+
+The ProSe-App-Code-Info AVP is of type Grouped. It shall contain a ProSe Application Code, the associated MIC and the associated UTC-based counter.
+
+The AVP format shall conform to:
+
+```
+ProSe-App-Code-Info ::= <AVP header: 3835 10415>
+                        { ProSe-App-Code }
+                        { MIC }
+                        { UTC-based-Counter }
+                        *[AVP]
+```
+
+### 6.3.40 MIC
+
+The MIC AVP is of type OctetString and shall contain a MIC (Message Integrity Check) associated with a discovered ProSe Application Code, as defined in 3GPP TS 33.303 [23].
+
+### 6.3.41 UTC-based-Counter
+
+The UTC-based-Counter AVP is of type Unsigned32 and it shall contain the UTC-based counter (in seconds) associated with a discovered ProSe Application Code as defined in 3GPP TS 24.334 [22].
+
+### 6.3.42 Location-Update-Trigger
+
+The Location-Update-Trigger AVP is of type Grouped. It shall contain the type of event that will trigger a locate update procedure to forward the location of UE to the ProSe Function initiating the Proximity Request.
+
+The AVP format shall conform to:
+
+```
+Location-Update-Trigger ::= <AVP header: 3823 10415>
+                          { Location-Update-Event-Type }
+                          [ Change-Of-Area-Type ]
+```
+
+[ Periodic-Location-Type ]  
+\*[AVP]
+
+The Change-Of-Area-Type AVP shall be present if the Location-Update-Event-Type AVP value is set to CHANGE\_OR\_AREA (1). Otherwise, it shall be absent.
+
+The Periodic-Location-Type AVP shall be present if the Location-Update-Event-Type AVP value is set to PERIODIC\_LOCATION (2). Otherwise, it shall be absent.
+
+### 6.3.43 Location-Update-Event-Type
+
+The Location-Update-Event-Type AVP is of type Unsigned32 and contains an 32-bit address space representing types of events that will trigger a location update. The following values are defined:
+
+UE\_AVAILABLE (0)
+
+This value shall be used to indicate that the location update trigger is any event in which the MSC/SGSN/MME has established a contact with the UE.
+
+CHANGE\_OF\_AREA (1)
+
+This value shall be used to indicate that the location update trigger is an event where the UE enters or leaves a pre-defined geographical area or if the UE is currently within the pre-defined geographical area.
+
+PERIODIC\_LOCATION (2)
+
+This value shall be used to indicate that the location update trigger is an event where a defined periodic timer expires in the UE and activates a location report or a location request
+
+The types of event listed above are defined in the clause 4.4.2.1 of the 3GPP TS 23.271 [24]
+
+### 6.3.44 Change-Of-Area-Type
+
+The Change-Of-Area-Type AVP is of type Grouped. It shall contain the information related to the type of event that will trigger a locate update procedure to forward the location of UE to the ProSe Function initiating the Proximity Request.
+
+The AVP format shall conform to:
+
+Change-Of-Area-Type ::= <AVP header: 3825 10415>  
+                          { Location-Update-Event-Trigger }  
+                          { Report-Cardinality }  
+                          [ Minimum-Interval-Time ]  
+                          \*[AVP]
+
+The Minimum-Interval-Time AVP may be present only if the Report-Cardinality AVP value is set to MULTIPLE (1).
+
+### 6.3.45 Location-Update-Event-Trigger
+
+The Location-Update-Event-Type AVP is of type Unsigned32 and contains a 32-bit address space representing the possible change of area events i.e. UE enters, leaves or is within requested target area. The following values are defined:
+
+UE\_ENTRY (0)
+
+This value shall be used to indicate the event trigger is the UE entering a pre-defined geographical area.
+
+UE\_EXIT (1)
+
+This value shall be used to indicate the event trigger is the UE leaving a pre-defined geographical area
+
+#### UE\_PRESENCE (2)
+
+This value shall be used to indicate the event trigger is the current presence of the UE within a pre-defined geographical area.
+
+The types of change of area event listed above are defined in the clause 4.4.2.1 of the 3GPP TS 23.271 [24].
+
+### 6.3.46 Report-Cardinality
+
+The Report-Cardinality AVP is of type Enumerated. The following values are defined:
+
+#### SINGLE (0)
+
+This value shall be used to indicate the change of area event shall be reported one time only.
+
+#### MULTIPLE (1)
+
+This value shall be used to indicate the change of area event may be reported several times.
+
+### 6.3.47 Minimum-Interval-Time
+
+The Minimum-Interval-Time AVP is of type Unsigned32 and shall contain the minimum number of seconds between area event reports.
+
+### 6.3.48 Periodic-Location-Type
+
+The Periodic-Location-Type AVP is of type Grouped. It shall contain the time interval between successive location reports and the total number of reports.
+
+The AVP format shall conform to:
+
+Periodic-Location-Type ::= <AVP header: 3829 10415>  
+                                    { Location-Report-Interval-Time }  
+                                    { Total-Number-Of-Reports }  
+                                    \*[AVP]
+
+### 6.3.49 Location-Report-Interval-Time
+
+The Location-Report-Interval-Time AVP is of type Unsigned32 and shall contain the number of seconds between successive location reports.
+
+### 6.3.50 Total-Number-Of-Reports
+
+The Total-Number-Of-Reports AVP is of type Unsigned32 and shall indicate the maximum number of requested location reports.
+
+### 6.3.51 Authorized-Discovery-Range
+
+The Authorized-Discovery-Range AVP is of type Unsigned32 and it shall contain a value that indicates the authorised announcing range (short/medium/long) at which the UE is allowed to announce in the given PLMN according to the defined announcing authorisation policy for this UE. This AVP is defined in the 3GPP TS 29.344 [14].
+
+### 6.3.52 ProSe-Match-Refresh-Timer
+
+The ProSe-Match-Refresh-Timer AVP is of type Unsigned32 and it shall contain the number of seconds indicating how long the UE shall wait before sending a new Match Report for the associated ProSe Application Code.
+
+### 6.3.53 Discovery-Auth-Request
+
+The Discovery-Auth-Request is of type Grouped. It shall contain the information elements used in ProSe direct discovery authorization request.
+
+The AVP format shall conform to:
+
+```
+
+Discovery-Auth-Request ::= <AVP header: 3854 10415>
+    { Discovery-Type }
+    [ User-Identity ]
+    [ ProSe-App-ID ]
+    [ ProSe-App-Code ]
+    [ ProSe-App-Code-Suffix-Range ]
+    [ ProSe-Validity-Timer ]
+    [ App-Identifier ]
+    [ Requesting-RPAAUID ]
+    [ Target-RPAAUID ]
+    [ Target-PDUID ]
+    [ ProSe-Restricted-Code ]
+    [ ProSe-Query-Code ]
+    [ ProSe-Response-Code ]
+    *[ ProSe-Restricted-Code-Suffix-Range ]
+    [ Banned-RPAAUID ]
+    [ Banned-PDUID ]
+    [ Service-Result ]
+    [ PC5-tech ]
+    *[AVP]
+
+```
+
+When the Discovery-Type is set to "ANNOUNCING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, a ProSe Application ID, a ProSe Application Code and optionally one or more ProSe Restricted Code Suffix-Range, ProSe Validity Timer and the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, a ProSe Application ID and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, an Application Identifier, the Requesting RPAAUID, ProSe Restricted Code and optionally one or more ProSe Restricted Code Suffix-Range, a ProSe Validity Timer and the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, an Application Identifier, Requesting RPAAUID, Target RPAAUID, Target PDUID and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "DISCOVEREE\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, an Application Identifier, Requesting RPAAUID, a ProSe Response Code and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, an Application Identifier, Requesting RPAUID, Target RPAUID, Target PDUID and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "DISCOVERER\_ANNOUNCING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain a UE identity, an Application Identifier, Requesting RPAUID, a ProSe Query Code and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "MONITORING\_UPDATE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain an Application Identifier, a ProSe Restricted Code, a Banned RPAUID, a Banned PDUID and optionally the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "MONITORING\_RESPONSE\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Request shall contain an Application Identifier, ProSe-Restricted-Code, Banned RPAUID, Banned PDUID, Result and optionally the PC5 radio technology that the UE is using.
+
+### 6.3.54 Discovery-Auth-Response
+
+The Discovery-Auth-Response is of type Grouped. It shall contain the information elements used in ProSe direct discovery authorization answer.
+
+The AVP format shall conform to:
+
+```
+
+Discovery-Auth-Response ::= <AVP header: 3855 10415>
+    { Discovery-Type }
+    *[ ProSe-Discovery-Filter ]
+    [ Visited-PLMN-Id ]
+    [ ProSe-Restricted-Code ]
+    [ ProSe-Query-Code ]
+    [ ProSe-Response-Code ]
+    [ ProSe-Validity Timer ]
+    [ Code-Sending-Security-Material ]
+    [ Code-Receiving-Security-Material ]
+    [ DUIK ]
+    [ PC5-tech ]
+    *[AVP]
+
+```
+
+When the Discovery-Type is set to "ANNOUNCING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Response shall contain no other parameters.
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Response shall contain one or more ProSe Discovery Filters, optionally a PLMN ID and the PC5 radio technology that the UE is using.
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Response shall contain a ProSe Restricted Code, a Code Receiving Security Material, optionally a DUIK, a ProSe Validity Timer and the PC5 radio technology that the UE is using. The DUIK parameter shall be included in Discovery-Auth-Response only if the Code-Receiving-Security-Material contains a MIC Check Indicator set to MIC\_CHECK\_BY\_PROSE\_FUNCTION.
+
+When the Discovery-Type is set to
+
+"DISCOVERER\_REQUEST\_FOR\_RESTRICTED\_PROSE\_DIRECT\_DISCOVERY", the Discovery-Auth-Response shall contain a ProSe Query Code, a Code Sending Security Material, a ProSe Response Code, a Code Receiving Security Material, optionally a DUIK, a ProSe Validity Timer and the PC5 radio technology that the UE is using. The DUIK parameter shall be included in Discovery-Auth-Response only if the Code-Receiving-Security-Material contains a MIC Check Indicator set to MIC\_CHECK\_BY\_PROSE\_FUNCTION.
+
+### 6.3.55 Match-Request
+
+The Match-Request is of type Grouped. It shall contain the information elements used in ProSe Match Report request.
+
+The AVP format shall conform to:
+
+```
+Match-Request ::= <AVP header: 3856 10415>
+                  { Discovery-Type }
+                  [ User Identity ]
+                  [ Visited-PLMN-ID ]
+                  *[ ProSe-App-Code-Info ]
+                  [ PC5-tech ]
+                  *[AVP]
+```
+
+The valid value for Discovery-Type for Match-Report AVP is:
+
+"MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY",
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Match-Request shall contain one UE Identity, one Visited PLMN ID, one or more ProSe App Code Info and optionally the PC5 radio technology that the UE is using.
+
+### 6.3.56 Match-Report-Info
+
+The Match-Report-Info is of type Grouped. It shall contain the information elements used in ProSe Match Report Info request.
+
+The AVP format shall conform to:
+
+```
+Match-Report-Info ::= <AVP header: 3857 10415>
+                      { Discovery-Type }
+                      [ User-Identity ]
+                      *[ ProSe-App-ID ]
+                      *[AVP]
+```
+
+The valid value for Discovery-Type for Match-Report-Info AVP is:
+
+"MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY",
+
+When the Discovery-Type is set to "MONITORING\_REQUEST\_FOR\_OPEN\_PROSE\_DIRECT\_DISCOVERY", the Match-Report-Info shall contain one User Identity and one or more ProSe Application IDs.
+
+### 6.3.57 PMR-Flags
+
+The PMR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.57/1:
+
+**Table 6.3.57/1: PMR-Flags**
+
+| Bit                                                                                                                                          | Name               | Description                                                                                                     |
+|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                                                            | Metadata Requested | This bit, when set, indicates that metadata information associated with the ProSe Application ID are requested. |
+| NOTE: Bits not defined in this table shall be cleared by the sending Prose Function and discarded by the receiving receiving ProSe function. |                    |                                                                                                                 |
+
+### 6.3.58 ProSe-Application-Metadata
+
+The ProSe-Application-Metadata AVP is of type UTF8String. This AVP shall contain the metadata associated with the ProSe Application ID contained in the Match Report. As defined in 3GPP TS 24.334 [22], the length and contents of the metadata formatted as UTF8-encoded string are out of scope of 3GPP.
+
+### 6.3.59 Discovery-Entry-ID
+
+The Discovery-Entry-ID is of type Unsigned32. It shall contain the discovery Entry ID used to identify the discovery entry in the UE context related to the discovery authorization request in the requesting ProSe Function.
+
+### 6.3.60 ProSe-Metadata-Index-Mask
+
+The ProSe-Metadata-Index-Mask AVP is of type OctetString. This AVP contains a ProSe metadata index mask (see 3GPP TS 24.334 [22]).
+
+### 6.3.61 App-Identifier
+
+The App-Identifier AVP is of type Grouped. It shall contain an OS ID and OS Application ID name.
+
+The AVP format shall conform to:
+
+```
+App-Identifier ::= <AVP header: 3840 10415>
+                 { OS-ID }
+                 { OS-App-ID }
+                 *[AVP]
+```
+
+### 6.3.62 OS-ID
+
+The OS-ID AVP is of type OctetString. It shall contain an identifier of the operating system as defined in clause 12.2.2.5 in 3GPP TS 24.334 [22].
+
+### 6.3.63 OS-App-ID
+
+The OS-App-ID AVP is of type UTF8String. It shall contain an OS specific application as defined in clause 12.2.2.5 in 3GPP TS 24.334 [22].
+
+### 6.3.64 Requesting-RPAUID
+
+The Requesting-RPAUID AVP is of type UTF8String. This AVP contains an identifier for restricted ProSe direct discovery that uniquely identifies an application user originating a restricted ProSe direct discovery request.
+
+### 6.3.65 Target-RPAUID
+
+The Target-RPAUID AVP is of type UTF8String. This AVP contains an identifier for restricted ProSe direct discovery that uniquely identifies an application user targeted by a restricted ProSe direct discovery request.
+
+### 6.3.66 Target-PDUID
+
+The Target-PDUID AVP is of type OctetString. It shall contain the ProSe Discovery UE ID which uniquely identifies the UE targeted by a restricted ProSe direct discovery request.
+
+### 6.3.67 ProSe-Restricted-Code
+
+The ProSe-Restricted-Code AVP is of type OctetString. This AVP contains a ProSe Restricted Code (see 3GPP TS 23.003 [4]) which is associated with a RPAUID.
+
+### 6.3.68 ProSe-Restricted-Code-Suffix-Range
+
+The ProSe-Restricted-Code-Suffix-Range AVP is of type Grouped. It contains a range of consecutive ProSe Restricted Code Suffixes that can be appended to a ProSe Restricted Code Prefix. It shall contain a Beginning Suffix and may contain an Ending Suffix. If the Ending Suffix is not present, the only ProSe Restricted Code Suffix included in the ProSe Restricted Code Suffix Range is equal to the Beginning Suffix.
+
+The AVP format shall conform to:
+
+```
+ProSe-Restricted-Code-Suffix-Range ::= <AVP header: 3847 10415>
+    { Beginning-Suffix }
+    [ Ending-Suffix ]
+    *[AVP]
+```
+
+Beginning Suffix and Ending Suffix shall have the same length.
+
+### 6.3.69 Beginning-Suffix
+
+The Beginning-Suffix AVP is of type OctetString. This AVP shall contain the lowest ProSe Restricted Code Suffix in a consecutive sequence of ProSe Restricted Code suffixes, or the lowest ProSe Application Code Suffix in a consecutive sequence of ProSe Application Code Suffixes. The format of ProSe Restricted Code Suffix or ProSe Application Code Suffix is defined in 3GPP TS 23.003 [4]. The size of this suffix shall align with octet boundary.
+
+### 6.3.70 Ending-Suffix
+
+The Ending-Suffix AVP is of type OctetString. This AVP shall contain the highest ProSe Restricted Code Suffix in a consecutive sequence of ProSe Restricted Code suffixes or the highest ProSe Application Code Suffix in a consecutive sequence of ProSe Application Code Suffixes. The format of ProSe Restricted Code Suffix or ProSe Application Code Suffix is defined in 3GPP TS 23.003 [4]. The size of this suffix shall align with octet boundary.
+
+### 6.3.71 Match-Timestamp
+
+The Match-Timestamp AVP is of type Time and it shall contain the UTC time identifying when the discovery match event occurred.
+
+### 6.3.72 DRMP
+
+The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [27]. This AVP allows the Prose Function to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.
+
+### 6.3.73 Banned-RPAUID
+
+The Banned-RPAUID AVP is of type UTF8String. This AVP contains an identifier for restricted ProSe direct discovery that uniquely identifies an application user banned by a restricted ProSe direct discovery request.
+
+### 6.3.74 Banned-PDUID
+
+The Banned-PDUID AVP is of type OctetString. It shall contain the ProSe Discovery UE ID which uniquely identifies the UE Banned by a restricted ProSe direct discovery request.
+
+### 6.3.75 Code-Receiving-Security-Material
+
+The Code-Receiving-Security-Material AVP is of type Grouped. It shall contain security parameters used to indicate to a UE how a received restricted ProSe direct discovery message is protected. The Code Receiving Security Material may
+
+contain a DUSK and may contain either a DUIK or an indication whether to use Match Reports for MIC checking. It may also contain both a DUCK and a corresponding Encrypted Bitmask.
+
+The AVP format shall conform to:
+
+```
+Code-Receiving-Security-Material ::= <AVP header: 3847 10415>
+    [ DUSK ]
+    [ DUIK ]
+    [ MIC-Check-Indicator ]
+    [ DUCK ]
+    [ Encrypted-Bitmask ]
+    *[AVP]
+```
+
+### 6.3.76 Code-Sending-Security-Material
+
+The Code-Sending-Security-Material AVP is of type Grouped. It shall contain security parameters used to indicate to a UE how to protect the transmission of restricted ProSe direct discovery message. The Code Sending Security Material may contain a DUSK and may contain a DUIK. It may also contain both a DUCK and a corresponding Encrypted Bitmask.
+
+The AVP format shall conform to:
+
+```
+Code-Sending-Security-Material ::= <AVP header: 3847 10415>
+    [ DUSK ]
+    [ DUIK ]
+    [ DUCK ]
+    [ Encrypted-Bitmask ]
+    *[AVP]
+```
+
+### 6.3.77 DUSK
+
+The DUSK AVP is of type OctetString. It shall contain the Discovery User Scrambling Key used to scramble or unscramble the restricted ProSe direct discovery message containing the ProSe Restricted Code, ProSe Query Code or ProSe Response Code. The format of the DUSK is defined in 3GPP TS 33.303 [23].
+
+### 6.3.78 DUIK
+
+The DUIK AVP is of type OctetString. It shall contain the Discovery User Integrity Key used to compute the MIC of the restricted ProSe direct discovery message containing the ProSe Restricted Code, ProSe Query Code or ProSe Response Code. The format of the DUIK is defined in 3GPP TS 33.303 [23].
+
+### 6.3.79 DUCK
+
+The DUCK AVP is of type OctetString. It shall contain the Discovery User Confidentiality Key used to encrypt and decrypt a portion in restricted ProSe direct discovery message. The format of the DUCK is defined in 3GPP TS 33.303 [23].
+
+### 6.3.80 MIC-Check-Indicator
+
+The MIC-Check-Indicator AVP is of type Unsigned32. It shall contain the indication of whether the UE shall use the ProSe Function to verify the MIC field of the received discovery message. The following values are defined:
+
+MIC\_CHECK\_BY\_PROSE\_FUNCTION (1)
+
+This value is used when the MIC check is required to be done by the ProSe Function.
+
+### 6.3.81 Encrypted-Bitmask
+
+The Encrypted-Bitmask AVP is of type OctetString. It shall contain a 184-bit bitmask which uses bit "1" to mark the positions of the bits of a ProSe Restricted Code, ProSe Query Code or ProSe Response Code, for which the DUCK encryption is applied.
+
+### 6.3.82 ProSe-App-Code-Suffix-Range
+
+The ProSe-App-Code-Suffix-Range AVP is of type Grouped. It contains a range of consecutive ProSe Application Code Suffixes that can be appended to a ProSe Application Code Prefix. It shall contain a Beginning Suffix and may contain an Ending Suffix. If the Ending Suffix is not present, the only ProSe Application Code Suffix included in the ProSe Application Code Suffix Range is equal to the Beginning Suffix.
+
+The AVP format shall conform to:
+
+```
+ProSe-App-Code-Suffix-Range ::= <AVP header: 3847 10415>
+    { Beginning-Suffix }
+    [ Ending-Suffix ]
+    *[AVP]
+```
+
+Beginning Suffix and Ending Suffix shall have the same length.
+
+### 6.3.83 Load
+
+The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [28]. This AVP is used to support Diameter load control mechanism, see Annex D for more information.
+
+### 6.3.84 PC5-tech
+
+The PC5-tech AVP is of type OctetString. It shall contain an identifier of the PC5 radio technology as defined in clause 12.2.2.71 in 3GPP TS 24.334 [22].
+
+## 6.4 Result-Code and Experimental-Result Values
+
+### 6.4.1 General
+
+This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification.
+
+### 6.4.2 Success
+
+Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in the Diameter base protocol (IETF RFC 6733 [29]) shall be applied.
+
+### 6.4.3 Permanent Failures
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in the Diameter base protocol (IETF RFC 6733 [29]) shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+#### 6.4.3.1 DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+This result code shall be sent by the ProSe Function in the HPLMN to indicate that the user identified by the UE identity is unknown
+
+#### 6.4.3.2 DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE (5511)
+
+This result code shall be sent by the ProSe Function in the HPLMN to indicate that no ProSe subscription is associated with the UE.
+
+#### 6.4.3.3 DIAMETER\_ERROR\_NO\_ASSOCIATED\_DISCOVERY\_FILTER (5630)
+
+This result code shall be sent by the ProSe Function in the local/visited PLMN to indicate that there is no valid Discovery Filter associated to the ProSe Application ID name received in the request.
+
+#### 6.4.3.4 DIAMETER\_ERROR\_ANNOUNCING\_UNAUTHORIZED\_IN\_PLMN (5631)
+
+This result code shall be sent by the ProSe Function in the local/visited PLMN to indicate that the UE is not authorized to announce in this PLMN.
+
+#### 6.4.3.5 DIAMETER\_ERROR\_INVALID\_APPLICATION\_CODE (5632)
+
+This result code shall be sent by the ProSe Function in the local PLMN to indicate that none of the ProSe Application Code(s) received in the request is valid.
+
+#### 6.4.3.6 DIAMETER\_ERROR\_PROXIMITY\_UNAUTHORIZED (5633)
+
+This result code shall be sent by the ProSe Function in the serving PLMN to indicate that the Proximity request is not authorized by the user.
+
+#### 6.4.3.7 DIAMETER\_ERROR\_PROXIMITY\_REJECTED (5634)
+
+This result code shall be sent by the ProSe Function in the serving PLMN to indicate that it is unlikely that UEs enter into proximity for the received time window.
+
+#### 6.4.3.8 DIAMETER\_ERROR\_NO\_PROXIMITY\_REQUEST (5635)
+
+This result code shall be sent by the ProSe Function in the serving PLMN to indicate that there is no context associated with EPC ProSe User Identities included in the request.
+
+#### 6.4.3.9 DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE\_IN\_THIS\_PLMN (5636)
+
+This result code shall be sent by the ProSe Function HPLMN to indicate that ProSe is not authorized to announce in this PLMN.
+
+#### 6.4.3.10 DIAMETER\_ERROR\_PROXIMITY\_CANCELLED (5637)
+
+This result code shall be sent by the ProSe Function triggering the Proximity Request to indicate that the cancellation of the Proximity Request procedure as it determines that the UEs are unlikely to enter proximity within the requested time window.
+
+#### 6.4.3.11 DIAMETER\_ERROR\_INVALID\_DISCOVERY\_TYPE (5641)
+
+This result code shall be sent by the ProSe Function to indicate that the Discovery Type in the request message is not supported.
+
+#### 6.4.3.12 DIAMETER\_ERROR\_INVALID\_TARGET\_PDUID (5638)
+
+This result code shall be sent by the ProSe Function to indicate that the PDUID is not belonging to this ProSe Function.
+
+### 6.4.3.13 DIAMETER\_ERROR\_INVALID\_TARGET\_RPAUID (5639)
+
+This result code shall be sent by the ProSe Function to indicate that the target RPAUID is not allowed to be discovered.
+
+#### 6.4.3.14 DIAMETER\_ERROR\_NO\_ASSOCIATED\_RESTRICTED\_CODE (5640)
+
+This result code shall be sent by the ProSe Function to indicate that there is no allocated ProSe Restricted Code for the requested target.
+
+#### 6.4.3.15 DIAMETER\_ERROR\_REVOCATION\_FAILURE (56x1)
+
+This value is used to indicate that the ProSe Function was unable to successfully complete the revocation procedure (in an operator-configured time period).
+
+#### 6.4.3.16 DIAMETER\_ERROR\_ALREADY\_BANNED (56x2)
+
+This value is used to indicate that the ProSe Function has determined that the revocation is not necessary because the target RPAUID has already been banned for discovery.
+
+### 6.4.4 Transient Failures
+
+Result codes that fall within the transient failures category shall be used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. The Result-Code AVP values defined in the Diameter base protocol specified in IETF RFC 6733 [29] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+---
+
+# Annex A (normative): Diameter overload control mechanism
+
+## A.1 General
+
+Diameter overload control mechanism is an optional feature.
+
+IETF RFC 7683 [21] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 7683 [21] on the PC6/PC7 interface where, when applied, the requesting ProSe Function shall behave as a reacting node and the responding ProSe Function as a reporting node.
+
+## A.2 Responding ProSe Function behaviour
+
+The responding ProSe Function requests traffic reduction from requesting ProSe Function when it is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [21].
+
+The ProSe Function identifies that it is in an overload situation by implementation specific means. For example, the ProSe Function may take into account the traffic over the PC6/PC7 interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc.
+
+The ProSe Function determines the specific contents of OC-OLR AVP in overload reports and the ProSe Function decides when to send OC-OLR AVPs by implementation specific means.
+
+## A.3 Requesting ProSe Function behaviour
+
+The requesting ProSe Function applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [21].
+
+Requested traffic reduction is achieved by the requesting ProSe Function by implementation specific means. For example, it may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed.
+
+As a result of the need to throttle traffic, the requesting ProSe Function may reject Registration Request, Discovery Request, Match Report Requests initiated by UEs. The possible related error messages used over PC3 are described in the 3GPP TS 24.334 [22].
+
+---
+
+## Annex B (Informative): Diameter overload node behaviour
+
+### B.1 Message prioritization
+
+This clause describes possible behaviours of the requesting ProSe Function receiving an overload indication from the responding ProSe Function, regarding message prioritisation in an informative purpose.
+
+The requesting ProSe Function may take the following into account when making throttling decisions:
+
+- Identification of the procedures that can be deferred (e.g. Proximity Requests), so to avoid to drop non deferrable procedures;
+- Prioritisation of certain types of request (e.g. between ProSe-Proximity-Request (PRR) and ProSe-Location-Update-Request (PLR)) according to the context of their use, in particular:
+  - Higher prioritisation for commands that are related to a registered user for a service, so to avoid the interruption of the registered service for the user.
+
+---
+
+## Annex C (normative): Diameter message priority mechanism
+
+### C.1 General
+
+IETF RFC 7944 [27] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied.
+
+### C.2 PC6/PC7 interfaces
+
+#### C.2.1 General
+
+The Diameter message priority mechanism is an optional feature.
+
+It is recommended to make use of IETF RFC 7944 [27] over the PC6/PC7 interfaces of an operator network when the overload control defined in Annex A is applied on these PC6/7 interfaces.
+
+#### C.2.2 ProSe Function behaviour
+
+When the ProSe Function supports the Diameter message priority mechanism over the PC6 or the PC7 interface, the ProSe Function shall comply with IETF RFC 7944 [27].
+
+The ProSe Function sending a request shall determine the required priority according to its policies. When priority is required, the ProSe Function shall include the DRMP AVP indicating the required priority level in the requests it sends, and shall prioritise the request according to the required priority level.
+
+When the ProSe Function receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request.
+
+When the ProSe Function receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, the ProSe Function may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response.
+
+If:
+
+- the ProSe Function supports using the Diameter message priority mechanism for DSCP marking purposes,
+
+- the transport network utilizes DSCP marking, and
+- message-dependant DSCP marking is possible for the protocol stack transporting Diameter,
+
+then the ProSe Function shall set the DSCP marking for transport of the request or response according to the required priority level.
+
+The ProSe Function decisions for a required priority and for the priority level value are implementation specific.
+
+Diameter requests related to high priority traffic shall contain a DRMP AVP with a high priority of which the level value is operator dependent.
+
+---
+
+## Annex D (normative): Diameter load control mechanism
+
+### D.1 General
+
+Diameter load control mechanism is an optional feature.
+
+IETF RFC 8583 [28] specifies a Diameter load control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 8583 [28] on the PC6/PC7 interface where, when applied, the requesting ProSe Function shall behave as a reacting node and the responding ProSe Function as a reporting node.
+
+### D.2 Responding ProSe Function behaviour
+
+The responding ProSe Function may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [28].
+
+The responding ProSe Function calculates its current load by implementation specific means. For example, the responding ProSe Function may take into account the traffic over the PC6/PC7 interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc.
+
+The responding ProSe Function determines when to send Load AVPs of type HOST by implementation specific means.
+
+### D.3 Requesting ProSe Function behaviour
+
+When performing next hop Diameter Agent selection for requests that are routed based on realm, the requesting ProSe Function may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [28].
+
+## Annex E (informative): Change history
+
+| Date    | TSG #         | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                  | New    |
+|---------|---------------|-----------|------|-----|--------------------------------------------------------------------------------------------------|--------|
+| 2014-04 | CT4#64b<br>is | C4-140705 |      |     | TR Skeleton                                                                                      | 0.1.0  |
+| 2014-05 | CT4#65        | C4-141079 |      |     | Proposed text for clause "Scope"                                                                 | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141080 |      |     | General Description of TS 29.345                                                                 | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141081 |      |     | Description of the ProSe Service Authorization Procedure                                         | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141082 |      |     | Description of the Direct Discovery Authorization procedure                                      | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141084 |      |     | Description of the Match Report Procedure                                                        | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141086 |      |     | Description of the Proximity request Procedure                                                   | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141087 |      |     | Description of the Location Update procedure                                                     | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141088 |      |     | Description of the Cancellation procedure                                                        | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141089 |      |     | Description of Protocol Specification and Implementation                                         | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141090 |      |     | Description of the Proximity Alert Procedure                                                     | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141091 |      |     | Description of Information Elements                                                              | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141092 |      |     | Description of Commands                                                                          | 0.2.0  |
+| 2014-05 | CT4#65        | C4-141175 |      |     | Description of Result Codes                                                                      | 0.2.0  |
+| 2014-07 | CT4#66        | C4-141266 |      |     | Editorial corrections                                                                            | 0.3.0  |
+| 2014-07 | CT4#66        | C4-141422 |      |     | Removal of the Cancellation-Type AVP                                                             | 0.3.0  |
+| 2014-07 | CT4#66        | C4-141423 |      |     | Domain Name used for ProSe related Diameter Applications                                         | 0.3.0  |
+| 2014-07 | CT4#66        | C4-141511 |      |     | Description of the Match Report Info procedure                                                   | 0.3.0  |
+| 2014-07 | CT4#66        | C4-141512 |      |     | Correction of the User-Identifier AVP                                                            | 0.3.0  |
+| 2014-07 | CT4#66        | C4-141641 |      |     | Correction of the Discovery-Filter AVP                                                           | 0.3.0  |
+| 2014-09 | CT#65         | CP-140498 |      |     | Presented for information and approval                                                           | 1.0.0  |
+| 2014-09 | CT#65         |           |      |     | Approved at CT#65                                                                                | 12.0.0 |
+| 2014-12 | CT#66         | CP-140778 | 0006 | 1   | ProSe Validity Timer to VPLMN                                                                    | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0003 | 1   | Overload Control management                                                                      | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0007 | 1   | Wrong P-CR implementations                                                                       | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0005 |     | Clarification in the ProSe Direct Discovery Authorization Procedure                              | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0001 | 4   | Clarification on ProSe Application Code and Discovery Filter IE Formats                          | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0009 | 1   | Deletion of the unused AVP                                                                       | 12.1.0 |
+| 2014-12 | CT#66         | CP-140778 | 0010 | 1   | Updates of the values for Application ID, Command codes, AVP codes and Experimental-Result codes | 12.1.0 |
+| 2015-03 | CT#67         | CP-150028 | 0012 | 2   | Correction on ProSe Service Authorization Procedures in PC6/PC7 interface                        | 12.2.0 |
+| 2015-03 | CT#67         | CP-150028 | 0014 | 2   | Addition of Integrity Check aspects to ProSe Match Report procedure                              | 12.2.0 |
+| 2015-03 | CT#67         | CP-150028 | 0016 | 1   | Correction in the Discovery Type description                                                     | 12.2.0 |
+| 2015-03 | CT#67         | CP-150028 | 0020 | 2   | Location Update Trigger                                                                          | 12.2.0 |
+
+|         |        |           |      |   |                                                                                                                               |        |
+|---------|--------|-----------|------|---|-------------------------------------------------------------------------------------------------------------------------------|--------|
+| 2015-03 | CT#67  | CP-150149 | 0015 | 4 | Introduction of Authorized Discovery Range Indication for announcing UE                                                       | 12.2.0 |
+| 2015-03 | CT#67  | CP-150031 | 0021 | 1 | Update of the reference for IETF draft-ietf-dime-ovli                                                                         | 12.2.0 |
+| 2015-06 | CT#68  | CP-150257 | 0022 | 1 | Addition of Match Report Refresh Timer in PMA command                                                                         | 12.3.0 |
+| 2015-06 | CT#68  | CP-150257 | 0024 | 1 | Corrections of errors and inconsistencies in TS 29.345                                                                        | 12.3.0 |
+| 2015-06 | CT#68  | CP-150257 | 0025 | 2 | Ambiguity in the definition of Prose-Discovery-Filter AVP                                                                     | 12.3.0 |
+| 2015-06 | CT#68  | CP-150257 | 0027 | 2 | Clarification on ProSe Validity Timer                                                                                         | 12.3.0 |
+| 2015-06 | CT#68  | CP-150257 | 0028 | 2 | Alignment on using ProSe service and ProSe                                                                                    | 12.3.0 |
+| 2015-12 | CT#70  | CP-150755 | 0032 | 4 | Correction of AVP and message definitions to allow Diameter command reuse                                                     | 12.4.0 |
+| 2015-12 | CT#70  | CP-150755 | 0033 | 1 | Metadata in Match-Report                                                                                                      | 12.4.0 |
+| 2015-12 | CT#70  | CP-150759 | 0035 | 1 | Reference to DOIC updated with IETF RFC 7683                                                                                  | 12.4.0 |
+| 2015-12 | CT#70  | CP-150772 | 0029 | 5 | Addition of ProSe discovery service authorization for restricted discovery                                                    | 13.0.0 |
+| 2015-12 | CT#70  | CP-150772 | 0030 | 2 | ProSe Open Discovery for Dynamic Metadata                                                                                     | 13.0.0 |
+| 2015-12 | CT#70  | CP-150772 | 0031 | 2 | AVP and Message format changes for new ProSe procedures                                                                       | 13.0.0 |
+| 2015-12 | CT#70  | CP-150772 | 0034 | 2 | Addition of ProSe match report info for restricted discovery                                                                  | 13.0.0 |
+| 2016-03 | CT#71  | CP-160023 | 0041 |   | Diameter message priority over PC6/PC7                                                                                        | 13.1.0 |
+| 2016-03 | CT#71  | CP-160036 | 0036 | 3 | Monitoring update and Reporting of update result                                                                              | 13.1.0 |
+| 2016-03 | CT#71  | CP-160036 | 0037 | 1 | Inter-PLMN discovery transmission support                                                                                     | 13.1.0 |
+| 2016-03 | CT#71  | CP-160036 | 0038 | 1 | Adding security related parameters for restricted ProSe direct discovery authorization                                        | 13.1.0 |
+| 2016-03 | CT#71  | CP-160036 | 0039 | 1 | Support open discovery with application-controlled extension                                                                  | 13.1.0 |
+| 2016-03 | CT#71  | CP-160036 | 0040 | - | Discovery update for open and restricted ProSe direct discovery                                                               | 13.1.0 |
+| 2016-06 | CT#72  | CP-160232 | 0042 | 2 | Update of AVP codes for ProSe direct discovery security and open ProSe direct discovery with application-controlled extension | 13.2.0 |
+| 2016-06 | CT#72  | CP-160232 | 0043 | 1 | Clarification of local PLMN usage in direct discovery authorization                                                           | 13.2.0 |
+| 2016-12 | CT#74  | CP-160664 | 0045 | - | Correction to change IETF drmp draft version to official RFC 7944                                                             | 13.3.0 |
+| 2016-12 | CT#74  | CP-160681 | 0044 | 1 | Load Control                                                                                                                  | 14.0.0 |
+| 2017-03 | CT#75  | CP-170048 | 0046 | 1 | Update of reference for the Diameter base protocol                                                                            | 14.1.0 |
+| 2017-03 | CT#75  | CP-170048 | 0047 | 1 | Handling of the Vendor-Specific-Application-Id AVP                                                                            | 14.1.0 |
+| 2017-03 | CT#75  | CP-170048 | 0048 | 1 | Cardinality of the Failed-AVP AVP in answer                                                                                   | 14.1.0 |
+| 2017-06 | CT#76  | CP-171018 | 0050 | 1 | Support for signaling transport level packet marking                                                                          | 14.2.0 |
+| 2017-09 | CT#77  | CP-172013 | 0052 | - | Correction of DRMP Procedures                                                                                                 | 14.3.0 |
+| 2017-12 | CT#78  | CP-173032 | 0053 | 1 | Updates for WLAN based ProSe Direct Discovery                                                                                 | 15.0.0 |
+| 2019-09 | CT#85  | CP-192094 | 0055 | 1 | draft-ietf-dime-load published as RFC 8583                                                                                    | 15.1.0 |
+| 2020-07 | CT#88e | -         | -    | - | Update to Rel-16 version (MCC)                                                                                                | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29380/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/29_series/29380/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f3112d1d66bde0ae8df07ae3c22d3de17bca9da
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37be79efa144e6bc809c51b0f97ac87d363e0283bfe298d6d26b2092a11e0100
+size 146559
diff --git a/marked/Rel-16/29_series/29380/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/29_series/29380/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5df2852e77b126a14b577a362e348146bb1f79f
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:056eda2bcf935f43fe8616074948dff313407b1ec8a7a9205042783aedf3e557
+size 40510
diff --git a/marked/Rel-16/29_series/29380/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/29_series/29380/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba31d698531fe6977054f157a7b3932745ce342e
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc4f2d61cf97890589ad9419e83f1d97ae3b0f2462c4b8dced2a6c9a35a29b35
+size 148194
diff --git a/marked/Rel-16/29_series/29380/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29380/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6e64a85c75c3d19ed3d5f153329c16aab3dae78
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f7a0b98e100a435dfc115dfdf125ee92bae88c40aafc0fbf7bb41e54e37fdfd0
+size 9232
diff --git a/marked/Rel-16/29_series/29380/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29380/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d54b5b6ae870a9adb78ff51f06049fc780866939
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0da881c84289a2b452b4b8c27e22bce7eea4294f0ad3a5c1bbd1e0efa5b1383
+size 5783
diff --git a/marked/Rel-16/29_series/29380/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/29_series/29380/7ed5d5770331f31ade15439a21c31425_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8c08a0683800034502532695bf52820ead4d4fe3
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/7ed5d5770331f31ade15439a21c31425_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32c1488e97d1bfdecd6a62f9c0cfb049335d1dcb3b51e616fc57b67f4708986f
+size 81356
diff --git a/marked/Rel-16/29_series/29380/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Rel-16/29_series/29380/a26e142d3df5bef41a84a9dd099d7825_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ad888bc8966b3a5babf4126169b716dad7a3bb0
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/a26e142d3df5bef41a84a9dd099d7825_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4da5c9a729566d6220cd9941c29211c7fbdbf2d82fe929cdedd8b26843794af1
+size 86392
diff --git a/marked/Rel-16/29_series/29380/b701cd8c436a2857a615a76a868a3bb7_img.jpg b/marked/Rel-16/29_series/29380/b701cd8c436a2857a615a76a868a3bb7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5b6ed5a82de4865dd3f361962ff9bcc8d8c3dc5e
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/b701cd8c436a2857a615a76a868a3bb7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:495ff19c7612264e04922b737b1f50e7eac78208da63af5f7372549dd45cdf05
+size 67190
diff --git a/marked/Rel-16/29_series/29380/raw.md b/marked/Rel-16/29_series/29380/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bee97e9d3c4d5ad0ca850d658c345d5e7b6c9124
--- /dev/null
+++ b/marked/Rel-16/29_series/29380/raw.md
@@ -0,0 +1,3407 @@
+
+
+# 3GPP TS 29.380 V16.0.0 (2019-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mission Critical Push To Talk (MCPTT) media plane control interworking with Land Mobile Radio (LMR) systems; Stage 3 (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                               |    |
+|-----------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                | 8  |
+| 1 Scope.....                                                                                  | 10 |
+| 2 References.....                                                                             | 10 |
+| 3 Definitions of terms, symbols and abbreviations.....                                        | 11 |
+| 3.1 Terms.....                                                                                | 11 |
+| 3.2 Abbreviations .....                                                                       | 12 |
+| 4 General.....                                                                                | 13 |
+| 4.1 Overview .....                                                                            | 13 |
+| 4.1.1 Floor Control .....                                                                     | 13 |
+| 4.1.1.1 General.....                                                                          | 13 |
+| 4.1.1.2 On-network floor control.....                                                         | 13 |
+| 4.1.1.3 Off-network floor control .....                                                       | 13 |
+| 4.1.1.4 Determine effective priority.....                                                     | 13 |
+| 4.1.1.5 Determine off-network effective priority .....                                        | 13 |
+| 4.1.2 Pre-established session call control .....                                              | 14 |
+| 4.1.3 MBMS subchannel control.....                                                            | 14 |
+| 4.2 Internal structure of media plane control entities.....                                   | 14 |
+| 4.2.0 General .....                                                                           | 14 |
+| 4.2.1 Controlling MCPTT function.....                                                         | 14 |
+| 4.2.2 MCPTT client.....                                                                       | 16 |
+| 4.2.3 Participating MCPTT function.....                                                       | 16 |
+| 4.2.3.1 General.....                                                                          | 16 |
+| 4.2.3.2 Internal structure of the IWF performing the participating role .....                 | 16 |
+| 4.2.4 Non-controlling MCPTT function of an MCPTT group.....                                   | 17 |
+| 4.3 The media plane control channel .....                                                     | 17 |
+| 4.3.1 General .....                                                                           | 17 |
+| 4.3.2 Control channel realization.....                                                        | 17 |
+| 4.3.3 Establishing a media plane control channel .....                                        | 17 |
+| 4.3.3.1 General.....                                                                          | 17 |
+| 5 Roles.....                                                                                  | 18 |
+| 5.1 General .....                                                                             | 18 |
+| 5.2 Client.....                                                                               | 18 |
+| 5.3 IWF performing the controlling role.....                                                  | 18 |
+| 5.4 IWF performing the participating role .....                                               | 18 |
+| 5.5 IWF performing the non-controlling role.....                                              | 19 |
+| 6 Floor control.....                                                                          | 19 |
+| 6.1 General .....                                                                             | 19 |
+| 6.2 Floor participant procedures.....                                                         | 19 |
+| 6.3 Floor control server procedures.....                                                      | 19 |
+| 6.3.1 General .....                                                                           | 19 |
+| 6.3.2 IWF performing the controlling role procedures at MCPTT call initialization .....       | 20 |
+| 6.3.2.1 General.....                                                                          | 20 |
+| 6.3.2.2 Initial procedures .....                                                              | 20 |
+| 6.3.2.3 Switching from a non-controlling to a controlling role .....                          | 20 |
+| 6.3.3 Floor control procedures at MCPTT call release.....                                     | 21 |
+| 6.3.4 Floor control server state transition diagram for general floor control operation ..... | 21 |
+| 6.3.4.1 General.....                                                                          | 21 |
+| 6.3.4.2 State: 'Start-stop' .....                                                             | 23 |
+| 6.3.4.2.1 General .....                                                                       | 23 |
+| 6.3.4.2.2 MCPTT call initialization.....                                                      | 23 |
+| 6.3.4.3 State: 'G: Floor Idle' .....                                                          | 23 |
+| 6.3.4.3.1 General .....                                                                       | 23 |
+| 6.3.4.3.2 Enter the 'G: Floor Idle' state.....                                                | 23 |
+| 6.3.4.3.3 Receive Floor Request message (R: Floor Request).....                               | 25 |
+
+|            |                                                                                                                     |    |
+|------------|---------------------------------------------------------------------------------------------------------------------|----|
+| 6.3.4.3.3a | IWF floor participant grant (I: IWF Floor Participant Grant) .....                                                  | 25 |
+| 6.3.4.3.4  | Timer T7 (Floor Idle) expired .....                                                                                 | 25 |
+| 6.3.4.3.5  | Timer T4 (Inactivity) expired.....                                                                                  | 26 |
+| 6.3.4.3.6  | Receive an implicit floor request (R: Implicit floor request) .....                                                 | 26 |
+| 6.3.4.4    | State: 'G: Floor Taken' .....                                                                                       | 26 |
+| 6.3.4.4.1  | General .....                                                                                                       | 26 |
+| 6.3.4.4.2  | Enter the 'G: Floor Taken' state .....                                                                              | 27 |
+| 6.3.4.4.3  | Timer T1 (End of RTP media) expired .....                                                                           | 27 |
+| 6.3.4.4.4  | Timer T2 (Stop talking) expired.....                                                                                | 27 |
+| 6.3.4.4.5  | Receive RTP media packets (R: RTP media) .....                                                                      | 28 |
+| 6.3.4.4.6  | Receive Floor Release message (R: Floor Release).....                                                               | 28 |
+| 6.3.4.4.6a | IWF floor participant release (I: IWF floor participant release) .....                                              | 28 |
+| 6.3.4.4.7  | Receive Floor Request message with pre-emptive priority (R: pre-emptive Floor Request) .....                        | 28 |
+| 6.3.4.4.7a | Receive Floor Request message multi-talker (R: multi-talker Floor Request) .....                                    | 29 |
+| 6.3.4.4.8  | Receive Floor request message from MCPTT floor participant (R: Floor Request) .....                                 | 29 |
+| 6.3.4.4.9  | Timer T20 (Floor Granted) expired .....                                                                             | 29 |
+| 6.3.4.4.10 | Timer T20 (Floor Granted) expired N times.....                                                                      | 29 |
+| 6.3.4.4.11 | MCPTT media endpoint release (R: client release) .....                                                              | 30 |
+| 6.3.4.4.12 | Receive an implicit floor request (R: Implicit floor request) .....                                                 | 30 |
+| 6.3.4.5    | State: 'G: pending Floor Revoke' .....                                                                              | 30 |
+| 6.3.4.5.1  | General .....                                                                                                       | 30 |
+| 6.3.4.5.2  | Enter the 'G: pending Floor Revoke' state.....                                                                      | 30 |
+| 6.3.4.5.3  | Receive RTP media packets (R: RTP media) .....                                                                      | 31 |
+| 6.3.4.5.4  | Receive Floor Release message (R: Floor Release).....                                                               | 31 |
+| 6.3.4.5.5  | Timer T3 (Stop talking grace) expired.....                                                                          | 31 |
+| 6.3.4.5.6  | Timer T1 (End of RTP media) expired .....                                                                           | 31 |
+| 6.3.4.6    | In any state .....                                                                                                  | 32 |
+| 6.3.4.6.1  | General .....                                                                                                       | 32 |
+| 6.3.4.6.2  | Receive MCPTT call release - 1 .....                                                                                | 32 |
+| 6.3.4.6.3  | Receive an instruction to merge group calls (R: Merge) .....                                                        | 32 |
+| 6.3.4.7    | State: 'Releasing' .....                                                                                            | 32 |
+| 6.3.4.7.1  | General .....                                                                                                       | 32 |
+| 6.3.4.7.2  | Receive MCPTT call release - 2 .....                                                                                | 32 |
+| 6.3.4.8    | State: 'G: Floor Initialising' .....                                                                                | 32 |
+| 6.3.4.8.1  | General .....                                                                                                       | 32 |
+| 6.3.4.8.2  | Enter the 'G: Initialising' state .....                                                                             | 32 |
+| 6.3.4.8.3  | Receiving a floor request from a constituent MCPTT group (R: mcptt-floor-request) .....                             | 33 |
+| 6.3.4.8.4  | All final SIP responses received (R: final SIP responses) .....                                                     | 33 |
+| 6.3.5      | Floor control server state transition diagram for basic floor control operation towards the floor participant ..... | 34 |
+| 6.3.5.1    | General .....                                                                                                       | 34 |
+| 6.3.5.2    | State: 'Start-stop' .....                                                                                           | 36 |
+| 6.3.5.2.1  | General .....                                                                                                       | 36 |
+| 6.3.5.2.2  | SIP Session initiated.....                                                                                          | 36 |
+| 6.3.5.3    | State: 'U: not permitted and Floor Idle' .....                                                                      | 39 |
+| 6.3.5.3.1  | General .....                                                                                                       | 39 |
+| 6.3.5.3.2  | Enter state 'U: not permitted and Floor Idle' .....                                                                 | 39 |
+| 6.3.5.3.3  | Send Floor Taken message (S: Floor Taken).....                                                                      | 40 |
+| 6.3.5.3.4  | Receive Floor Request message (R: Floor Request).....                                                               | 40 |
+| 6.3.5.3.5  | Send Floor Grant message (S: Floor Grant).....                                                                      | 40 |
+| 6.3.5.3.6  | Send Floor Deny message (S: Floor Deny).....                                                                        | 41 |
+| 6.3.5.3.7  | Receive Floor Release message (R: Floor Release).....                                                               | 41 |
+| 6.3.5.3.8  | Receive RTP media packets (R: media).....                                                                           | 41 |
+| 6.3.5.3.9  | Receive an implicit floor request (R: Implicit floor request) .....                                                 | 42 |
+| 6.3.5.3.10 | Send Floor Idle message (S: Floor Idle).....                                                                        | 42 |
+| 6.3.5.4    | State 'U: not permitted and Floor Taken' .....                                                                      | 42 |
+| 6.3.5.4.1  | General .....                                                                                                       | 42 |
+| 6.3.5.4.2  | Enter state 'U: not permitted and Floor Taken'.....                                                                 | 42 |
+| 6.3.5.4.3  | Send Floor Idle message (S: Floor Idle).....                                                                        | 43 |
+| 6.3.5.4.4  | Receive Floor Request message (R: Floor Request).....                                                               | 43 |
+| 6.3.5.4.5  | Receive Floor Release message (R: Floor Release).....                                                               | 46 |
+| 6.3.5.4.6  | Receive RTP media packets (R: media).....                                                                           | 47 |
+
+|            |                                                                                                                                 |    |
+|------------|---------------------------------------------------------------------------------------------------------------------------------|----|
+| 6.3.5.4.7  | Send Floor Queue Position Info message (R: Floor Queue Position Request).....                                                   | 48 |
+| 6.3.5.4.8  | Receive an implicit floor request (R: Implicit floor request) .....                                                             | 48 |
+| 6.3.5.4.9  | Send Floor Granted message (S: Floor Granted) .....                                                                             | 48 |
+| 6.3.5.4.10 | Send Floor Taken message (S: Floor Taken).....                                                                                  | 49 |
+| 6.3.5.4.11 | Send Floor Release Multi Talker message (S: Floor Release Multi Talker) .....                                                   | 49 |
+| 6.3.5.5    | State: 'U: permitted'.....                                                                                                      | 49 |
+| 6.3.5.5.1  | General .....                                                                                                                   | 49 |
+| 6.3.5.5.2  | Enter state 'U: permitted' .....                                                                                                | 49 |
+| 6.3.5.5.3  | Receive Floor Release message (R: Floor Release).....                                                                           | 49 |
+| 6.3.5.5.4  | Send Floor Idle message (S: Floor Idle).....                                                                                    | 50 |
+| 6.3.5.5.5  | Send Floor Revoke message (S: Floor Revoke).....                                                                                | 50 |
+| 6.3.5.5.6  | Receive RTP media packets (R: media).....                                                                                       | 50 |
+| 6.3.5.5.7  | Receive Floor Request message (R: Floor Request).....                                                                           | 50 |
+| 6.3.5.5.8  | Send RTP Media (S: media).....                                                                                                  | 51 |
+| 6.3.5.5.9  | Send Floor Taken message (S: Floor Taken).....                                                                                  | 51 |
+| 6.3.5.5.10 | Send Floor Release Multi Talker message (S: Floor Release Multi Talker) .....                                                   | 51 |
+| 6.3.5.6    | State: 'U: pending Floor Revoke' .....                                                                                          | 51 |
+| 6.3.5.6.1  | General .....                                                                                                                   | 51 |
+| 6.3.5.6.2  | Enter state 'U pending Floor Revoke'.....                                                                                       | 51 |
+| 6.3.5.6.3  | Timer T8 (media Revoke) expired.....                                                                                            | 52 |
+| 6.3.5.6.4  | Receive RTP media packets (R: media).....                                                                                       | 52 |
+| 6.3.5.6.5  | Receive Floor Release message (R: Floor Release).....                                                                           | 52 |
+| 6.3.5.6.6  | Send Floor Idle message (S: Floor Idle).....                                                                                    | 53 |
+| 6.3.5.6.7  | Send Floor Taken message (S: Floor Taken).....                                                                                  | 53 |
+| 6.3.5.6.8  | Send Floor Release Multi Talker message (S: Floor Release Multi Talker) .....                                                   | 53 |
+| 6.3.5.7    | State 'U: not permitted but sends media'.....                                                                                   | 53 |
+| 6.3.5.7.1  | General .....                                                                                                                   | 53 |
+| 6.3.5.7.2  | Enter state 'U: not permitted but sends media' .....                                                                            | 53 |
+| 6.3.5.7.3  | Timer T8 (Floor Revoke) expired.....                                                                                            | 54 |
+| 6.3.5.7.4  | Receive Floor Release message (R: Floor Release).....                                                                           | 54 |
+| 6.3.5.7.5  | Send Floor Taken message (S: Floor Taken).....                                                                                  | 55 |
+| 6.3.5.7.6  | Send Floor Release Multi Talker message (S: Floor Release Multi Talker) .....                                                   | 55 |
+| 6.3.5.8    | In any state .....                                                                                                              | 55 |
+| 6.3.5.8.1  | General .....                                                                                                                   | 55 |
+| 6.3.5.8.2  | Receive MCPTT call release – 1.....                                                                                             | 55 |
+| 6.3.5.8.3  | Receiving a merging instruction (R: Merge).....                                                                                 | 55 |
+| 6.3.5.9    | State: 'Releasing' .....                                                                                                        | 56 |
+| 6.3.5.9.1  | General .....                                                                                                                   | 56 |
+| 6.3.5.9.2  | Receive MCPTT call release - 2 .....                                                                                            | 56 |
+| 6.3.5.10   | State: 'U: not permitted and initiating' .....                                                                                  | 56 |
+| 6.3.5.10.1 | General .....                                                                                                                   | 56 |
+| 6.3.5.10.2 | Enter the 'U: not permitted and initiating' state .....                                                                         | 56 |
+| 6.3.5.10.3 | Send Floor Taken message (S: Floor Taken).....                                                                                  | 56 |
+| 6.3.5.10.4 | Send Floor Idle message (S: Floor Idle).....                                                                                    | 56 |
+| 6.3.5.10.5 | Receive Floor Request message (R: Floor Request).....                                                                           | 57 |
+| 6.3.5.10.6 | Send Floor Granted message (S: Floor Granted) .....                                                                             | 57 |
+| 6.3.5.10.7 | Receive a Floor Release message (S: Floor Release) .....                                                                        | 57 |
+| 6.3.5.10.8 | Send Floor Release Multi Talker message (S: Floor Release Multi Talker) .....                                                   | 58 |
+| 6.3.6      | Dual floor control .....                                                                                                        | 58 |
+| 6.3.6.1    | General.....                                                                                                                    | 58 |
+| 6.3.6.2    | State: 'Start-stop' .....                                                                                                       | 59 |
+| 6.3.6.2.1  | General .....                                                                                                                   | 59 |
+| 6.3.6.2.2  | Receive Floor Request message with overriding pre-emptive floor priority (R: Floor Request) ....                                | 60 |
+| 6.3.6.2.2A | Floor Grant to IWF floor participant with overriding pre-emptive floor priority (I: Floor Grant to IWF floor participant) ..... | 60 |
+| 6.3.6.3    | State: 'D: Floor Taken' .....                                                                                                   | 60 |
+| 6.3.6.3.1  | General .....                                                                                                                   | 60 |
+| 6.3.6.3.2  | Enter state 'D: Floor Taken'.....                                                                                               | 60 |
+| 6.3.6.3.3  | Timer T11 (End of RTP dual) expired.....                                                                                        | 61 |
+| 6.3.6.3.4  | Timer T12 (Stop talking dual) expired.....                                                                                      | 62 |
+| 6.3.6.3.5  | Receive RTP media packets (R: media).....                                                                                       | 63 |
+| 6.3.6.3.6  | Receive Floor Release message (R: Floor Release).....                                                                           | 63 |
+
+|            |                                                                                               |    |
+|------------|-----------------------------------------------------------------------------------------------|----|
+| 6.3.6.3.6A | IWF Floor Release (I: Floor release by IWF floor participant) .....                           | 64 |
+| 6.3.6.3.7  | Receive Floor request message from permitted MCPTT floor participant (R: Floor Request) ..... | 64 |
+| 6.3.6.3.8  | Permitted MCPTT participant release.....                                                      | 64 |
+| 6.3.6.3.8A | Permitted IWF participant release (I: Call release by IWF floor participant).....             | 65 |
+| 6.3.6.3.9  | Receive Terminate (Terminate) .....                                                           | 65 |
+| 6.3.6.4    | In any state .....                                                                            | 65 |
+| 6.3.6.4.1  | General .....                                                                                 | 65 |
+| 6.3.6.4.2  | Receive MCPTT call release - 1 .....                                                          | 65 |
+| 6.3.6.5    | State: 'Releasing' .....                                                                      | 66 |
+| 6.3.6.5.1  | General .....                                                                                 | 66 |
+| 6.3.6.5.2  | Receive MCPTT call release - 2 .....                                                          | 66 |
+| 6.4        | IWF performing the participating role floor control procedures.....                           | 66 |
+| 6.4.1      | General .....                                                                                 | 66 |
+| 6.4.2      | IWF floor participant procedures at MCPTT session initialization .....                        | 66 |
+| 6.4.2.1    | General.....                                                                                  | 66 |
+| 6.4.2.2    | MCPTT call initiated, IWF originating .....                                                   | 66 |
+| 6.4.2.3    | MCPTT call established, IWF terminating.....                                                  | 67 |
+| 6.4.3      | IWF floor participant procedures at MCPTT call release .....                                  | 67 |
+| 6.4.4      | IWF floor participant floor message handing.....                                              | 67 |
+| 6.4.4.1    | Receive Floor Idle message .....                                                              | 67 |
+| 6.4.4.2    | Receive Floor Taken message .....                                                             | 67 |
+| 6.4.4.3    | Receive RTP media packets .....                                                               | 67 |
+| 6.4.4.4    | Send Floor Request message .....                                                              | 68 |
+| 6.4.4.5    | Receive Floor Granted message .....                                                           | 68 |
+| 6.4.4.6    | Receive Floor Deny message.....                                                               | 68 |
+| 6.4.4.7    | Send Floor Release message.....                                                               | 68 |
+| 6.4.4.8    | Receive Floor Queue Position Info message .....                                               | 69 |
+| 6.4.4.9    | Receive Floor Revoke message .....                                                            | 69 |
+| 6.4.4.10   | Receive MCPTT call release .....                                                              | 69 |
+| 6.5        | IWF performing the non-controlling role of an MCPTT group.....                                | 69 |
+| 6.5.4      | Floor control server interface procedures.....                                                | 69 |
+| 6.5.4.1    | General.....                                                                                  | 69 |
+| 6.5.4.2    | Receiving a Floor Request message .....                                                       | 69 |
+| 6.5.4.2A   | IWF sends a Floor Request message .....                                                       | 70 |
+| 6.5.4.3    | Receive Floor Release message .....                                                           | 70 |
+| 6.5.4.3A   | IWF sends a Floor Release message.....                                                        | 71 |
+| 6.5.4.4    | Receive Floor Queue Position Request message .....                                            | 71 |
+| 6.5.4.4A   | IWF sends Floor Queue Position Request message.....                                           | 71 |
+| 6.5.4.5    | Receive Floor Ack message.....                                                                | 71 |
+| 6.5.4.5A   | IWF sends Floor Ack message .....                                                             | 72 |
+| 6.5.4.6    | Receive Floor Granted message .....                                                           | 72 |
+| 6.5.4.6A   | IWF grants floor.....                                                                         | 73 |
+| 6.5.4.17   | Receive Floor Release Multi Talker message.....                                               | 73 |
+| 6.5.5      | Floor participant interface procedures.....                                                   | 73 |
+| 6.5.5.1    | General .....                                                                                 | 73 |
+| 6.5.5.2    | State: 'Start-Stop' .....                                                                     | 74 |
+| 6.5.5.2.1  | General .....                                                                                 | 74 |
+| 6.5.5.2.2  | Participant invited to session.....                                                           | 75 |
+| 6.5.5.3    | State: 'P: has no permission'.....                                                            | 75 |
+| 6.5.5.3.1  | General .....                                                                                 | 75 |
+| 6.5.5.3.2  | Receive Floor Idle message (R: Floor Idle) .....                                              | 75 |
+| 6.5.5.3.3  | Receive Floor Taken message (R: Floor Taken).....                                             | 75 |
+| 6.5.5.3.4  | Receive Floor Request message (R: Floor Request).....                                         | 75 |
+| 6.5.5.3.5  | Receive Floor Granted message (R: Floor Granted) .....                                        | 75 |
+| 6.5.5.3.6  | Receive Floor Deny message (R: Floor Deny) .....                                              | 76 |
+| 6.5.5.3.7  | Receive Floor Queue Position Info message (R: Floor Queue Position Info) .....                | 76 |
+| 6.5.5.3.8  | Receive Floor Queue Position Request message (R: Floor Queue Position Request).....           | 76 |
+| 6.5.5.3.9  | Receive RTP media packets (R: RTP media) .....                                                | 76 |
+| 6.5.5.3.10 | Receive Floor Release message (R: Floor Release).....                                         | 76 |
+| 6.5.5.3.11 | Receive split instruction (R: Split) .....                                                    | 77 |
+| 6.5.5.3.12 | Receive Floor Release Multi Talker message (R: Floor Release Multi-talker) .....              | 77 |
+| 6.5.5.4    | State: 'P: has permission'.....                                                               | 77 |
+
+|                        |                                                                                  |    |
+|------------------------|----------------------------------------------------------------------------------|----|
+| 6.5.5.4.1              | General .....                                                                    | 77 |
+| 6.5.5.4.2              | Receive RTP media packets.....                                                   | 77 |
+| 6.5.5.4.3              | Receive Floor Release message (R: Floor Release).....                            | 78 |
+| 6.5.5.4.4              | Receive Floor Ack message (R: Floor Ack) .....                                   | 78 |
+| 6.5.5.4.5              | Receive Floor Idle message (R: Floor Idle) .....                                 | 78 |
+| 6.5.5.4.6              | Receive Floor Taken message (R: Floor Taken).....                                | 78 |
+| 6.5.5.4.7              | Receive Floor Revoke message (R: Floor Revoke).....                              | 78 |
+| 6.5.5.4.8              | Receive split instruction (R: Split).....                                        | 78 |
+| 6.5.5.4.9              | Receive Floor Release Multi Talker message (R: Floor Release Multi-talker) ..... | 79 |
+| 6.5.5.5                | In any state .....                                                               | 79 |
+| 6.5.5.5.1              | General .....                                                                    | 79 |
+| 6.5.5.5.2              | Receive Floor Ack message (R: Floor Ack) .....                                   | 79 |
+| 6.5.5.5.3              | MCPTT session release step 1 (MCPTT call release - 1).....                       | 79 |
+| 6.5.5.6                | State: 'P: Releasing'.....                                                       | 80 |
+| 6.5.5.6.1              | General .....                                                                    | 80 |
+| 6.5.5.6.2              | MCPTT session release step 2 (MCPTT call release - 2).....                       | 80 |
+| 7                      | Off-network floor control.....                                                   | 80 |
+| 8                      | Coding .....                                                                     | 80 |
+| 8.1                    | Introduction .....                                                               | 80 |
+| 8.2                    | Floor control.....                                                               | 80 |
+| 8.3                    | Pre-established session call control.....                                        | 80 |
+| 8.4                    | MBMS subchannel control.....                                                     | 81 |
+| 8.5                    | MBMS notifications.....                                                          | 81 |
+| 9                      | Call setup control over pre-established session .....                            | 81 |
+| 10                     | MBMS procedures .....                                                            | 81 |
+| 11                     | Configurable parameters .....                                                    | 81 |
+| 11.1                   | Timers.....                                                                      | 81 |
+| 11.2                   | Counters .....                                                                   | 81 |
+| 12                     | Extensions within the present document.....                                      | 81 |
+| 13                     | Media plane security .....                                                       | 81 |
+| 13.1                   | General .....                                                                    | 81 |
+| 13.2                   | Derivation of SRTP/SRTCP master keys.....                                        | 83 |
+| 13.3.1                 | General .....                                                                    | 83 |
+| 13.3.2                 | The IWF performing the participating role .....                                  | 83 |
+| 13.3.3                 | The IWF media endpoint.....                                                      | 84 |
+| 13.3.4                 | The IWF performing the controlling role.....                                     | 85 |
+| 13.3.5                 | The IWF performing the non-controlling role.....                                 | 86 |
+| 14                     | SDP offer/ answer procedures.....                                                | 87 |
+| 14.1                   | General .....                                                                    | 87 |
+| 14.2                   | Generating an SDP offer .....                                                    | 87 |
+| 14.3                   | Generating the SDP answer.....                                                   | 87 |
+| 14.4                   | Offeror processing of the SDP answer.....                                        | 87 |
+| 14.5                   | Modifying the media plane control channel.....                                   | 87 |
+| 14.6                   | The use of SDP offer / answer procedures in off-network mode.....                | 87 |
+| Annex A (informative): | Change history.....                                                              | 88 |
+
+---
+
+## Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, certain modal verbs have the following meanings:
+
+**shall** indicates a mandatory requirement to do something
+
+**shall not** indicates an interdiction (prohibition) to do something
+
+NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+**should** indicates a recommendation to do something
+
+**should not** indicates a recommendation not to do something
+
+**may** indicates permission to do something
+
+**need not** indicates permission not to do something
+
+NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+**can** indicates that something is possible
+
+**cannot** indicates that something is impossible
+
+NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not".
+
+**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+NOTE 5: The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document specifies the media plane control protocols and interactions with the media needed to support a Mission Critical Push To Talk (MCPTT) system interworking with a Land Mobile Radio (LMR) system. This interworking includes both the signalling and the media planes between the MCPTT system and the LMR system. The function between the MCPTT system and the LMR system is referred to as an Interworking Function (IWF).
+
+The IWF supports the basic group and other features as specified in 3GPP TS 23.283 [24].
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification".
+- [3] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications".
+- [4] 3GPP TS 24.483: "Mission Critical Services (MCS) Management Object (MO)".
+- [5] 3GPP TS 23.379: "Functional architecture and information flows to support mission critical communication services; Stage 2".
+- [6] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 Reference Point; Stage 3".
+- [7] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port".
+- [8] Void.
+- [9] 3GPP TS 25.446: "MBMS synchronization protocol (SYNC)".
+- [10] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
+- [11] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network protocols; Stage 3".
+- [12] 3GPP TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
+- [13] 3GPP TS 24.484: "Mission Critical Services (MCS) configuration management protocol specification".
+- [14] Void.
+- [15] IETF RFC 3830: "MIKEY: Multimedia Internet KEYing".
+- [16] IETF RFC 3711: "The Secure Real-time Protocol (SRTP)".
+- [17] IETF RFC 6509: "MIKEY-SAKKE: Sakai-Kashar Key Encryption in Multimedia Internet KEYing (MIKEY)".
+- [18] 3GPP TS 33.180: "Security of the mission critical service".
+- [19] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+
+- [20] IETF RFC 5795: "The Robust Header Compression (ROHC) Framework".
+- [21] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed".
+- [22] IETF RFC 5225: "RObust Header Compression Version 2 (ROHCv2): Profiles for RTP, UDP, IP, ESP and UDP-Lite".
+- [23] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
+- [24] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems".
+- [25] 3GPP TS 24.380: "Mission Critical Push To Talk (MCPTT) media plane control".
+- [26] 3GPP TS 29.379: "Mission Critical Push To Talk (MCPTT) call control interworking with LMR systems".
+- [27] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT) Stage 1".
+
+---
+
+## 3 Definitions of terms, symbols and abbreviations
+
+### 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Floor participant:** The floor participant functional entity is responsible for floor requests. In the present document this term can be a floor participant that can be in either an MCPTT system (ref. 3GPP TS 23.379 [5]) or in an IWF.
+
+**IWF floor control server:** A floor control server that is in the IWF.
+
+**IWF floor participant:** A floor participant that is in the IWF.
+
+**IWF media endpoint:** A media endpoint that is in the IWF.
+
+**Media endpoint:** The end producer or consumer of media and floor control traffic (see also "IWF media endpoint").
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.379 [5] apply:
+
+- Floor control**
+- Floor participant**
+- Floor control server**
+- Group call**
+- MCPTT call**
+- Mission critical push to talk**
+- Private call**
+- SIP core**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.283 [24] apply:
+
+- Interworking Function (IWF)**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 29.379 [26] apply:
+
+- IWF performing the controlling role**
+- IWF performing the non-controlling**
+- IWF performing the participating role**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.380 [25] apply:
+
+- Active floor request queue**
+- Conversation**
+- Effective priority**
+- Media burst**
+
+**Media plane control protocols  
+Passive floor request queue**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.180 [18] apply:
+
+**Group Master Key (GMK)  
+Group Master Key Identifier (GMK-ID)  
+Private Call Key (PCK)  
+Private Call Key Identifier (PCK-ID)  
+Signalling Protection Key (SPK)  
+Signalling Protection Key Identifier (SPK-ID)**
+
+For the purposes of the present document, the following terms and definitions given in IETF RFC 3711 [16] apply:
+
+**SRTP master key (SRTP-MK)  
+SRTP master key identifier (SRTP-MKI)  
+SRTP master salt (SRTP-MS)**
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|          |                                            |
+|----------|--------------------------------------------|
+| GMK      | Group Management Key                       |
+| GMK-ID   | Group Master Key Identifier                |
+| GMS      | Group Management Server                    |
+| GUK-ID   | Group User Key Identifier                  |
+| IP       | Internet Protocol                          |
+| MBMS     | Multimedia Broadcast and Multicast Service |
+| MCPTT    | Mission Critical Push To Talk              |
+| PCK      | Private Call Key                           |
+| PCK-ID   | Private Call Key Identifier                |
+| PTT      | Push-To-Talk                               |
+| RFC      | Request For Comment                        |
+| RTCP     | RTP Control Protocol                       |
+| RTP      | Real-time Transport Protocol               |
+| SPK      | Signalling Protection Key                  |
+| SPK-ID   | Signalling Protection Key Identifier       |
+| SRTCP    | Secure RTCP                                |
+| SRTP     | Secure RTP                                 |
+| SRTP-MK  | SRTP master key                            |
+| SRTP-MKI | SRTP master key identifier                 |
+| SRTP-MS  | SRTP master salt                           |
+| SSRC     | Synchronization SouRCe                     |
+| UE       | User Equipment                             |
+
+---
+
+## 4 General
+
+### 4.1 Overview
+
+#### 4.1.1 Floor Control
+
+##### 4.1.1.1 General
+
+In an MCPTT group call after the call is setup, at a given time only a single group member is allowed to talk, and all other affiliated group members listen to this talker. The control action for obtaining this mode of operation is known as floor control. The direct actors of floor control are the floor participants and the floor control server. A floor participant does the floor control related actions in MCPTT media endpoints and IWF media endpoints. The floor control server is the decision maker of the floor control. The floor control server is in the IWF when it is performing the controlling role.
+
+#### 4.1.1.2 On-network floor control
+
+For a general overview of floor control not specific to the IWF, see 3GPP TS 24.380 [25]. In that description, the IWF fulfills all of the described roles as a peer to the MCPTT server. The following features mentioned in 3GPP TS 24.380 [25] are not fully supported in the present document: cut-in, ambient listening and multi-talker.
+
+#### 4.1.1.3 Off-network floor control
+
+Off-network is not applicable to the IWF.
+
+#### 4.1.1.4 Determine effective priority
+
+The floor control server can determine how to handle a received Floor Request message using a number of input parameters. Examples of input parameters that the floor control server can use are:
+
+1. the floor priority, using the value of the Floor Priority field in the Floor Request message;
+2. the <user-priority> element as specified in 3GPP TS 24.481 [12];
+3. the participant type, using the <participant-type> element specified in 3GPP TS 24.481 [12] or, in case a non-controlling MCPTT function is attached to a group call, the <Participant Type> value in the Track Info field in the Floor Request message;
+4. the type of call indicated in the Floor Indicator field;
+5. the effective priority of the floor participant with the permission to send media, and the current type of the call (e.g. normal, imminent-peril, emergency, broadcast); and
+6. any other information in the group document specified in 3GPP TS 24.481 [12] or information stored in the IWF outside the scope of the present document.
+
+Using a local policy and the above input parameters the floor control server can determine that a floor request is:
+
+1. pre-emptive such that the current talker is overridden;
+2. pre-emptive such that the current talker is revoked;
+3. not pre-emptive and put in the floor request queue, if queueing was negotiated; or
+4. not-pre-emptive and rejected, if queueing was not negotiated.
+
+#### 4.1.1.5 Determine off-network effective priority
+
+Off-network is not applicable to the IWF.
+
+### 4.1.2 Pre-established session call control
+
+Pre-established session call control is not applicable to the IWF.
+
+### 4.1.3 MBMS subchannel control
+
+MBMS is not applicable to the IWF.
+
+## 4.2 Internal structure of media plane control entities
+
+### 4.2.0 General
+
+For clarity, the present document describes media plane aspects of the IWF-1 reference point using the structure shown in 3GPP TS 24.380 [25] and further detailed in clause 4.2.1. The IWF need not implement the structure of media plane control entities given in the present document, but the resulting IWF behaviour on the IWF-1 interface must be as specified in the present document.
+
+The floor control interface towards LMR entities is out of scope of the present document.
+
+## 4.2.1 Controlling MCPTT function
+
+According to 3GPP TS 23.379 [5], the controlling MCPTT function is divided into a floor control server and a media distribution function. In the present document an example of an internal structure of the IWF performing the controlling role is illustrated in figure 4.2-1.
+
+![Diagram of the internal structure of floor control in the IWF performing the controlling role. The diagram shows a hierarchy within the IWF. At the top is the 'Application and signalling plane'. Below it is the 'Floor control server', which contains 'Floor control interface towards the MCPTT client', 'Floor control arbitration logic', and 'Floor request queue'. Below the floor control server is the 'Media distribution function', which contains 'Network media interface' and 'Media distributor'. External connections labeled 'IWF-1' are shown on the left, connecting to the floor control interface and the network media interface.](a26e142d3df5bef41a84a9dd099d7825_img.jpg)
+
+```
+
+graph TD
+    subgraph IWF [IWF performing the controlling role]
+        direction TB
+        subgraph APS [Application and signalling plane]
+        end
+        subgraph FCS [Floor control server]
+            direction TB
+            FCI[Floor control interface towards the MCPTT client]
+            FCL[Floor control arbitration logic]
+            FQ[Floor request queue]
+            FCI --- FCL
+            FCI --- FQ
+            FCL --- FQ
+        end
+        subgraph MDF [Media distribution function]
+            direction TB
+            NMI[Network media interface]
+            MD[Media distributor]
+            NMI --- MD
+        end
+        APS --- FCS
+        FCS --- MDF
+    end
+    IWF1_1[IWF-1] --- FCI
+    IWF1_2[IWF-1] --- NMI
+  
+```
+
+Diagram of the internal structure of floor control in the IWF performing the controlling role. The diagram shows a hierarchy within the IWF. At the top is the 'Application and signalling plane'. Below it is the 'Floor control server', which contains 'Floor control interface towards the MCPTT client', 'Floor control arbitration logic', and 'Floor request queue'. Below the floor control server is the 'Media distribution function', which contains 'Network media interface' and 'Media distributor'. External connections labeled 'IWF-1' are shown on the left, connecting to the floor control interface and the network media interface.
+
+NOTE: The real internal structure of the IWF is implementation specific but a possible internal structure is shown to illustrate the procedures.
+
+**Figure 4.2.1-1: Internal structure of floor control in the IWF performing the controlling role**
+
+All entities in the IWF performing the controlling role are assumed to have a direct communication interface to the application and signalling plane. The interface to the application and signaling plane carries information about SIP session initialisation and SIP session release, SDP content, etc.
+
+The reference point IWF-1 is described in 3GPP TS 23.283 [24]. The floor control interface towards the MCPTT media endpoint receives and transmits the floor control messages from and to the MCPTT media endpoint via the participating MCPTT function or non-controlling MCPTT function. The procedures are controlled by a state machine described in clause 6.3.5. One state machine is needed for each MCPTT media endpoint participating in an MCPTT call. A non-controlling MCPTT function is seen by the floor control interface towards the MCPTT client as an MCPTT media endpoint.
+
+The floor control arbitration logic performs the floor control. The floor control arbitration logic is controlled by a state machine described in clause 6.3.4. One state machine is needed per MCPTT call.
+
+The floor request queue is accessible both by the floor control interface towards the MCPTT client for all MCPTT media endpoint in the call and the floor control arbitration logic.
+
+The network media interface receives and sends media from and to the associated MCPTT media endpoint via the participating MCPTT function or non-controlling MCPTT function. The network media interface is out of scope of the present document. One network media interface is needed for each MCPTT media endpoint participating in an MCPTT call. A non-controlling MCPTT function is seen by the network media interface as an MCPTT media endpoint.
+
+The media distributor is controlled by the floor control arbitration logic. The media distributor is out of scope of the present document. One media distributor is needed per MCPTT call.
+
+The internal interfaces are assumed to transport the following types of information.
+
+1. The interface between the network media interface and the floor control interface towards the MCPTT client:
+    - a. Indication that the network media interface has started to receive media packets from the associated MCPTT media endpoint or that media packets are no longer received from the associated MCPTT media endpoint.
+- NOTE: It is an implementation option whether an indication e.g. is sent for every received RTP media packet or only when the first packet is received and then when no more RTP packets are received.
+2. The interface between the floor control interface towards the MCPTT media endpoint and the floor control arbitration logic:
+    - a. Floor control messages to and from the associated MCPTT media endpoint, requests to create or delete the state machine instance for the associated MCPTT media endpoint. The floor control messages to the floor control arbitration logic are limited to floor control messages that will change the state of the floor.
+  3. The interface between the network media interface and the media distributor:
+    - a. Media to and from associated MCPTT media endpoint. This interface is out of scope of the present document.
+  4. The interface between the floor control arbitration logic and the media distributor:
+    - a. Requests to start or stop distributing media to floor participants in the MCPTT call. Indication that the media distributor has started to receive media packets from the network media interface associated with the MCPTT media endpoint with the permission to send media or that media packets are no longer received from the network media interface from the associated MCPTT media endpoint.
+  5. The interface between the floor control interface towards the MCPTT client and the floor request queue:
+    - a. Requests to store received Floor Request messages in the queue or requests to remove Floor Request messages from the queue and the queue content for building the Floor Queue Position Info message.
+  6. The interface between the floor control arbitration logic and the floor request queue:
+    - a. Requests to store received Floor Request messages in the queue or requests to remove Floor Request messages from the queue. Indications that the queue is modified.
+
+## 4.2.2 MCPTT client
+
+A user homed in the IWF is represented as an "IWF media endpoint". Actions relative to an IWF media endpoint are described as appropriate in the procedures of this present document for the IWF performing the participating, controlling, and non-controlling roles.
+
+## 4.2.3 Participating MCPTT function
+
+### 4.2.3.1 General
+
+The IWF performing the participating role uses media plane control (non-SIP) messages when taking part in the floor control procedures as specified in clause 6.
+
+The following clauses describe the assumed internal structure of the IWF performing the participating role and its role in the floor control procedures.
+
+### 4.2.3.2 Internal structure of the IWF performing the participating role
+
+In the present document the internal structure of the IWF performing the participating role is illustrated in figure 4.2.3.2-1.
+
+![Diagram of the internal structure of the IWF performing the participating role.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+The diagram illustrates the internal structure of the IWF performing the participating role. It consists of a large outer rectangle labeled "IWF performing the participating role". Inside this rectangle, there are two nested rectangles. The top nested rectangle is labeled "Application and signalling plane". The bottom nested rectangle is labeled "IWF media endpoint". Inside the "IWF media endpoint" rectangle, there is a third nested rectangle labeled "IWF floor participant". A horizontal line labeled "IWF-1" extends from the left side of the outer rectangle.
+
+Diagram of the internal structure of the IWF performing the participating role.
+
+NOTE: The real internal structure of the IWF performing the participating role is implementation specific, but a possible internal structure is shown to illustrate the logic and the procedures.
+
+**Figure 4.2.3.2-1: Internal structure of the IWF performing the participating role**
+
+All entities in the IWF performing the participating role have a direct communication interface to the application and signalling plane. The interface to the application and signalling plane carries information about SIP session initialisation and SIP session release, SDP content, etc.
+
+The reference point IWF-1 is described in 3GPP TS 23.283 [24].
+
+The IWF floor participant in the IWF performing the participating role manages media sessions on behalf of users homed in the IWF for cases where the session is homed in the MCPTT system. The specifications for the IWF performing the participating role related to the floor control are in clause 6.4 for media and media plane control delivery.
+
+#### 4.2.4 Non-controlling MCPTT function of an MCPTT group
+
+According to 3GPP TS 24.379 [2] subclause 5.3 the MCPTT server can act in a non-controlling MCPTT function of an MCPTT group role. In the present document the internal structure of the non-controlling MCPTT function of the IWF of an MCPTT group is illustrated in figure 4.2.4-1.
+
+### 4.3 The media plane control channel
+
+#### 4.3.1 General
+
+The media plane control channel is used for transport of messages associated with the floor control protocol.
+
+### 4.3.2 Control channel realization
+
+The media plane control channel is realized by sending RTCP APP packets on top of UDP/IP. RTCP APP packets are defined in IETF RFC 3550 [3]. The MCPTT specific coding of the RTCP APP packets is defined in clause 8 of the present document.
+
+### 4.3.3 Establishing a media plane control channel
+
+#### 4.3.3.1 General
+
+The IWF uses the SDP offer/answer mechanism in order to negotiate the establishment of the media plane control channel. The SDP offer/answer procedures for negotiating media plane control channel capabilities are specified in clause 14. The ABNF is defined in clause 12.
+
+The media description ("m=" line) associated with the media plane control channel shall have the values as described in table 4.3.3.1-1.
+
+**Table 4.3.3.1-1: Media plane control channel media description**
+
+| Media description element | Value         |
+|---------------------------|---------------|
+| <media>                   | "application" |
+| <port>                    | RTCP port     |
+| <proto>                   | "udp"         |
+| <fmt>                     | "MCPTT"       |
+
+The port used for RTCP messages associated with the media plane control channel shall be different than ports used for RTCP messages associated with other "m=" lines (e.g. RTP) in the SDP.
+
+NOTE 1: As RTCP is used to transport messages on the media plane control channel, the "m=" line port value indicates an RTCP port. This is different from cases where an "m=" line is associated with an RTP-based stream, and the "m=" line port value indicates an RTP port.
+
+NOTE 2: In the case where the media plane control channel uses a different IP address than other media described in the SDP, a media plane control channel specific "c=" line also needs to be associated with the "m=" line associated with the media plane control channel.
+
+The format of the optional SDP fmtp attribute, when associated with the media plane control channel, is described in clause 12.
+
+The example below shows an SDP media description for a media plane control channel.
+
+```
+m=application 20032 udp MCPTT
+a=fmtp:MCPTT mc_queueing;mc_priority=5;mc_granted
+```
+
+## 5 Roles
+
+### 5.1 General
+
+This clause associates the IWF with the MCPTT roles described in the stage 2 architecture document (see 3GPP TS 23.379 [5]).
+
+### 5.2 Client
+
+The IWF acts on behalf of all users homed in the IWF. There are no client procedures specified in the present document and specific client handling within the LMR system is out of scope.
+
+### 5.3 IWF performing the controlling role
+
+An IWF performing the controlling role shall:
+
+1. support the role of a controlling MCPTT function as specified in 3GPP TS 23.379 [5];
+2. support negotiating media plane control channel media level attributes as specified in clause 4.3;
+3. provide floor control arbitration logic with an interface to MCPTT clients as described in clause 4.2.1 and support the related procedures as specified in clause 6.3;
+4. provide a network media interface as described in clause 4.2.1 and support associated procedures as specified in clause 6.3;
+5. provide a media distributor with a floor control interface towards the MCPTT clients as described in 3GPP TS 24.380 [25] clause 4.2.1 and support associated procedures in clause 6.3;
+6. support the on-network mode floor control protocol elements as specified in clause 8; and
+7. support media plane security as specified in clause 13.
+
+An IWF performing the controlling role may:
+
+1. provide a floor request queue as described in clause 4.2.1 and support the related procedures as specified in clause 6.3 and clause 4.3.
+
+## 5.4 IWF performing the participating role
+
+An IWF performing the participating role shall:
+
+1. support the role of a participating MCPTT function;
+2. distribute floor control messages as described in clause 6.3 and support associated procedures as specified in clause 6.4;
+3. perform endpoint floor control signalling as the floor participant on behalf of users homed in the IWF; and
+
+NOTE: Floor control is modelled as a floor participant that is part of the IWF performing the participating role, and sits "behind" the participating role. This is for modelling purposes only and does not impose any particular structure or implementation on the IWF.
+
+4. support media plane security as specified in clause 13.
+
+## 5.5 IWF performing the non-controlling role
+
+An IWF performing the non-controlling role of an MCPTT group shall:
+
+1. support floor control involving groups from multiple MCPTT systems as specified in 3GPP TS 29.379 [26];
+2. provide a floor control interface towards the controlling MCPTT function as described in clause 4.2.4 and support the related procedures as specified in clause 6.5;
+3. provide a media interface towards the controlling MCPTT function as described in clause 4.2.4 and support the related procedure as specified in clause 6.5;
+4. provide a media distributor as described in clause 4.2.4 and the related procedures as specified in clause 6.5; and
+5. support media plane security as specified in clause 13.
+
+---
+
+# 6 Floor control
+
+## 6.1 General
+
+This clause provides:
+
+1. the IWF floor participant in clause 6.2;
+
+2. the IWF floor control server procedures in clause 6.3;
+3. the IWF performing the participating floor control procedures in clause 6.4; and
+4. the IWF performing the non-controlling role of an MCPTT group in clause 6.5.
+
+If media plane security is required, the IWF shall perform the additional procedures in clause 13.
+
+NOTE: It is possible that in a group re-group operation, the IWF can be performing both the controlling role for the re-grouped groups and the non-controlling role for one or more constituent groups. The actual implementation and internal communication among aspects of the IWF is out of scope.
+
+**Editor's Note:** The procedures of the IWF performing the non-controlling role are FFS.
+
+## 6.2 Floor participant procedures
+
+Procedures for IWF floor participants are addressed in the following:
+
+- the IWF performing the controlling role procedures in clause 6.3.4; and
+- the IWF performing the participating role procedures in clause 6.4.
+
+**Editor's Note:** The IWF performing the non-controlling role is FFS.
+
+## 6.3 Floor control server procedures
+
+### 6.3.1 General
+
+The floor control server arbitration logic in the IWF floor control server shall support the procedures in clauses 6.3.2 and 6.3.3 and shall behave according to the floor control server state transition diagram for 'general floor control operation' in clause 6.3.4.
+
+The floor control interface towards the MCPTT client in the IWF floor control server shall behave according to the floor control server state transition diagram for 'basic floor control operation towards the floor participant' as specified in clause 6.3.5.
+
+### 6.3.2 IWF performing the controlling role procedures at MCPTT call initialization
+
+#### 6.3.2.1 General
+
+Clause 6.3.2.2 describes the initial procedures when a new SIP session is establishing a group session or a private session with floor control.
+
+Clause 6.3.2.3 describes the procedures when the IWF performing the non-controlling role switches from the non-controlling role to the controlling role.
+
+#### 6.3.2.2 Initial procedures
+
+When an MCPTT call is established a new instance of the floor control server state machine for 'general floor control operation' is created.
+
+For each MCPTT media endpoint added to the MCPTT call, a new instance of the floor control server state machine for 'basic floor control operation towards the floor participant' is added.
+
+If the optional "mc\_queueing" feature is supported and has been negotiated as specified in clause 14, the IWF floor control server could queue the implicit floor control request for the MCPTT media endpoint.
+
+For cases where a SIP request originates in the MCPTT system, the initial SIP INVITE request or SIP REFER request to establish an MCPTT chat group call or to rejoin an ongoing MCPTT call is not handled as an implicit floor control request message by the IWF floor control server unless explicitly stated in the SIP INVITE request or in the SIP REFER request.
+
+The permission to send media to the inviting MCPTT media endpoint due to implicit floor control request is applicable to both confirmed indication and unconfirmed indication.
+
+When the first unconfirmed indication is received from the invited participating MCPTT function (see 3GPP TS 29.379 [26]) the IWF floor control server optionally can give an early indication to send RTP media packets, to the inviting MCPTT media endpoint.
+
+Before the IWF floor control server sends the first floor control message in the MCPTT call, the IWF floor control server has to assign itself an SSRC identifier to be included in media floor control messages and quality feedback messages if the IWF is supporting that option. A suitable algorithm to generate the SSRC identifier is described in IETF RFC 3550 [3].
+
+The MCPTT floor participant and the IWF floor control server can negotiate the maximum priority level that the floor participant is permitted to request. The IWF floor control server can pre-empt the current sender based on the negotiated maximum priority level that the MCPTT floor participant is permitted to request, and the priority level included in the Floor Request message.
+
+NOTE: The maximum priority level that an MCPTT floor participant can use is negotiated as specified in clause 14.3.3 and is based on group configuration data retrieved by the IWF performing the controlling role from the group management server as described in 3GPP TS 24.481 [12] and local policies applied by the IWF performing the controlling role.
+
+The MCPTT floor participant and the IWF floor control server can negotiate queueing of floor requests using the "mc\_queueing" fmtp attribute as described in clause 14. If queueing is supported and negotiated, the IWF floor control server queues the floor control request if a Floor Request message is received when another floor participant has the floor and the priority of the current speaker is the same or higher.
+
+### 6.3.2.3 Switching from a non-controlling to a controlling role
+
+**Editor's Note:** The IWF non-controlling role procedures are FFS.
+
+### 6.3.3 Floor control procedures at MCPTT call release
+
+When an MCPTT media endpoint leaves an MCPTT call and the MCPTT call remains ongoing with the other media endpoints, the IWF floor control server follows a two-step procedure.
+
+- Step 1 The IWF stops sending floor control messages and RTP media packets to the MCPTT media endpoint leaving the MCPTT call and, the IWF discards floor control messages and RTP media packets received from the MCPTT media endpoint leaving the MCPTT call.
+- Step 2 When the application and signalling plane has determined that the MCPTT call with this MCPTT floor participant has been released, the corresponding instance of the IWF floor control server state machine for 'basic floor control operation towards the floor participant' is released.
+
+When an MCPTT call is released, the IWF floor control server follows a two-step procedure.
+
+- Step 1 The IWF stops sending floor control messages and RTP media packets to all floor participants in the MCPTT call.
+- Step 2 When the application and signalling plane has determined that the MCPTT call has been released, the corresponding instance of the floor control server state machine for 'general floor control operation' are also terminated, along with any 'basic floor control operation towards the floor participant' state machines for the floor participants of this call.
+
+The floor control server state machine for general floor control operation initiates the MCPTT call release depending on the release policy specified in 3GPP TS 29.379 [26].
+
+## 6.3.4 Floor control server state transition diagram for general floor control operation
+
+### 6.3.4.1 General
+
+The floor control server arbitration logic in the floor control server in the IWF shall behave according to the state diagram in Figure 6.3.4.1-1 and state transitions specified in this clause. The present clause is applicable for floor control of groups homed in the IWF.
+
+![Floor control server state transition diagram for 'general floor control operation'](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Any state
+    Any state --> Start-stop : R: Merge
+    Any state --> Releasing : R: MCPTT call release - 1
+    Start-stop --> Releasing : R: MCPTT call release - 2
+    Start-stop --> G: Initialising : MCPTT call initialization
+    Start-stop --> G: Floor Idle : MCPTT call initialization
+    G: Initialising --> G: Floor Idle : R: final SIP responses
+    G: Initialising --> G: Floor Taken : R: final SIP responses
+    G: Floor Idle --> G: Initialising : MCPTT call initialization
+    G: Floor Idle --> G: Floor Taken : T1 (end of RTP media) expired OR T3 (Stop talking grace) expired OR R: Floor Release
+    G: Floor Idle --> G: Pending Floor Revoke : T7 (Floor Idle) expired OR R: Floor Request OR T4 (inactivity) expired OR R: Implicit Floor request
+    G: Floor Taken --> G: Floor Idle : R: Floor Request OR Floor request queued not_empty OR R: Implicit floor request I: IWF Floor Participant Grant
+    G: Floor Taken --> G: Pending Floor Revoke : T2 (stop talking) expired OR R: pre-emptive Floor request OR R: Implicit floor request
+    G: Pending Floor Revoke --> G: Floor Taken : R: Floor Release OR T3 (Stop talking grace) expired
+    G: Pending Floor Revoke --> G: Floor Idle : R: RTP Media OR T1 (end of RTP media) expired
+    G: Pending Floor Revoke --> G: Floor Taken : R: RTP Media OR R: Floor Request OR T20 (Floor Granted) expired OR T20 (Floor Granted expired N times OR R: pre-emptive Floor Request OR T1 (end of RTP media) expired, OR R: Floor Release OR R: client release
+  
+```
+
+The state transition diagram illustrates the floor control server's state transitions for general floor control operation. It begins with an 'Any state' initial state, which transitions to 'Start-stop' via 'R: Merge' or to 'Releasing' via 'R: MCPTT call release - 1'. From 'Start-stop', a transition to 'Releasing' occurs via 'R: MCPTT call release - 2', while 'MCPTT call initialization' leads to either 'G: Initialising' or 'G: Floor Idle'. 'G: Initialising' transitions to 'G: Floor Idle' or 'G: Floor Taken' via 'R: final SIP responses'. 'G: Floor Idle' transitions to 'G: Initialising' via 'MCPTT call initialization', to 'G: Floor Taken' via 'T1 (end of RTP media) expired OR T3 (Stop talking grace) expired OR R: Floor Release', and to 'G: Pending Floor Revoke' via 'T7 (Floor Idle) expired OR R: Floor Request OR T4 (inactivity) expired OR R: Implicit Floor request'. 'G: Floor Taken' transitions to 'G: Floor Idle' via 'R: Floor Request OR Floor request queued not\_empty OR R: Implicit floor request I: IWF Floor Participant Grant', to 'G: Pending Floor Revoke' via 'T2 (stop talking) expired OR R: pre-emptive Floor request OR R: Implicit floor request', and back to itself via 'R: RTP Media OR R: Floor Request OR T20 (Floor Granted) expired OR T20 (Floor Granted expired N times OR R: pre-emptive Floor Request OR T1 (end of RTP media) expired, OR R: Floor Release OR R: client release'. 'G: Pending Floor Revoke' transitions to 'G: Floor Taken' via 'R: Floor Release OR T3 (Stop talking grace) expired', to 'G: Floor Idle' via 'R: RTP Media OR T1 (end of RTP media) expired', and to 'G: Floor Taken' via 'R: RTP Media OR R: Floor Request OR T20 (Floor Granted) expired OR T20 (Floor Granted expired N times OR R: pre-emptive Floor Request OR T1 (end of RTP media) expired, OR R: Floor Release OR R: client release'.
+
+Floor control server state transition diagram for 'general floor control operation'
+
+Figure 6.3.4.1-1: Floor control server state transition diagram for 'general floor control operation'
+
+The floor control arbitration logic in the floor control server shall keep one instance of the 'general floor control operation' state machine per MCPTT call.
+
+If floor control messages or RTP media packets arrives in a state where there is no procedure specified in the following clauses the floor control arbitration logic in the IWF floor control server:
+
+1. shall discard the floor control message;
+2. shall request the media distributor in the IWF to discard any received RTP media packet; and
+3. shall remain in the current state.
+
+State details are explained in the following clauses.
+
+#### 6.3.4.2 State: 'Start-stop'
+
+##### 6.3.4.2.1 General
+
+When a new instance of the 'general floor control operation' state machine is initiated, before any floor control related input is applied, the state machine is in 'Start-stop' state. Similarly, when the call is released the state machine shall return to the 'Start-stop' state or the related MCPTT call is released.
+
+##### 6.3.4.2.2 MCPTT call initialization
+
+When an MCPTT call is initiated as specified in 3GPP TS 29.379 [26] and
+
+1. if a confirmed indication is required and at least one invited media endpoint has accepted the invitation;
+2. if a confirmed indication is not required; or
+3. if the initialised MCPTT call is a temporary group session;
+
+NOTE: An MCPTT group call is a temporary group session when the <on-network-temporary> element is present in the <list-service> element as specified in 3GPP TS 24.481 [12].
+
+then the floor control arbitration logic in the floor control server:
+
+1. shall create an instance of the 'general floor control operation' state machine;
+2. shall wait for the 'basic floor control operation towards the floor participant' to be initialized before continuing the following steps;
+3. when the 'basic floor control operation towards the floor participant' state machine is initialized, and the initialised session is not a temporary group session:
+  - a. if the "mc\_granted" fmtp attribute is not negotiated as specified in clause 14:
+    - i. if the floor control server is granting an implicit floor request at MCPTT call establishment, shall act as if a Floor Request message was received and perform the actions specified in clause 6.3.4.3.3; or
+    - ii. if the floor control server is not granting an implicit floor request at MCPTT call establishment, shall enter the 'G: Floor Idle' state as specified in clause 6.3.4.3.2; or
+  - b. if the "mc\_granted" fmtp attribute is negotiated as specified in clause 14, shall enter the 'G: Floor Taken' state as specified in clause 6.3.4.4.2; and
+4. if the 'basic floor control operation towards the floor participant' state machine is initialized, and the initialised session is a temporary group session, shall enter the 'G: Initialising' state as specified in the clause 6.3.4.8.1.
+
+#### 6.3.4.3 State: 'G: Floor Idle'
+
+##### 6.3.4.3.1 General
+
+The floor control arbitration logic in the IWF floor control server is in this state when no floor participant currently has permission to send media.
+
+Timer T4 (Inactivity) and timer T7 (Floor Idle) can be running when the floor control arbitration logic in the IWF floor control server is in this state.
+
+#### 6.3.4.3.2 Enter the 'G: Floor Idle' state
+
+When entering this state from any state except the 'Start-stop' state and if no MCPTT media endpoint negotiated support of queueing floor requests as described in clause 14, and the IWF does not require queueing for its IWF floor participants, and the state machine specified in clause 6.3.6 does not exist, the floor control arbitration logic in the IWF floor control server:
+
+1. if there is a Track Info field associated with the floor control server state transition diagram for 'general floor control operation' stored, shall remove the Track Info field from the storage;
+2. if the active floor request queue is empty the IWF floor control server:
+  - a. shall send Floor Idle message to all MCPTT floor participants. The Floor Idle message:
+    - i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+    - ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+NOTE 1: How the IWF informs IWF media endpoints of the idle floor is out of scope of the present document.
+
+- b. shall start timer T7 (Floor Idle) and initialise counter C7 (Floor Idle) to 1;
+  - c. shall start timer T4 (Inactivity); and
+  - d. shall set the general state to the 'G: Floor Idle' state; and
+3. if the active floor request queue is not empty the IWF floor control server:
+  - a. shall select a queued floor request from the top of the active floor request queue;
+  - b. shall remove that queued floor request from the active floor request queue;
+  - c. if the queued floor request includes a Track Info field, shall store the Track Info field and associate it with the floor control server state transition diagram for 'general floor control operation'; and
+  - d. shall enter the 'G: Floor Taken' state as specified in the clause 6.3.4.4.2 with respect to that floor participant.
+
+When entering this state from any state except the 'Start-stop' state and the state machine specified in clause 6.3.6 exists, the floor control arbitration logic in the IWF floor control server:
+
+1. if there is a Track Info field associated with the floor control server state transition diagram for 'general floor control operation' stored, shall remove the Track Info field from the storage;
+2. shall send Floor Idle message to all MCPTT floor participants which are configured to listen to the overridden participant. The Floor Idle message:
+  - a. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+NOTE 2: How the IWF informs IWF media endpoints of the idle floor is out of scope of the present document.
+
+3. shall send Floor Taken message to MCPTT floor participants which are configured to listen only to the overridden participant. The Floor Taken message:
+  - a. if privacy is not requested, shall include the granted MCPTT user's (overriding participant) MCPTT ID in the Granted Party's Identity field;
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+
+- c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+NOTE 3: How the IWF informs IWF media endpoints of the taken floor is out of scope of the present document.
+
+- 4. shall set the general state to the 'G: Floor Taken' state; and
+- 5. shall send the termination instruction to the 'dual floor control operation' state machine.
+
+#### 6.3.4.3.3 Receive Floor Request message (R: Floor Request)
+
+Upon receiving a floor request message (from an MCPTT floor participant that is permitted to make a floor request) the floor control arbitration logic in the IWF floor control server:
+
+- 1. shall reject the request if one of the following conditions is fulfilled:
+  - a. if there is only one media endpoint in the MCPTT call; and
+  - b. <on-network-recvonly> element is present in the <entry> element as specified 3GPP TS 24.481 [12] for the associated floor participant;
+- 2. if the floor request is rejected the IWF floor control server:
+  - a. shall send the Floor Deny message. The Floor Deny message:
+    - i. shall include in the Reject Cause field the <Reject Cause> value:
+      - A. cause #3 (Only one participant), if there is only one media endpoint in the MCPTT call; or
+      - B. cause #5 (Receive only), if the <on-network-recvonly> element is present in the <entry> element as specified in 3GPP TS 24.481 [12] for the associated MCPTT floor participant;
+    - ii. may include an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value of the Reject Cause field; and
+    - iii. if the Floor Request included a Track Info field, shall include the received Track Info field;
+  - b. shall remain in the 'G: Floor Idle' state; and
+- 3. if the floor request is granted the IWF floor control server:
+  - a. shall stop timer T4 (Inactivity);
+  - b. shall stop timer T7 (Floor Idle);
+  - c. if the floor is being granted to an MCPTT floor participant, and if a Track Info field is included in the Floor Request message, shall store the received Track Info field, and
+  - d. shall enter the 'G: Floor Taken' state as specified in the clause 6.3.4.4.2.
+
+#### 6.3.4.3.3a IWF floor participant grant (I: IWF Floor Participant Grant)
+
+To grant floor to an IWF floor participant, the floor control arbitration logic in the IWF floor control server:
+
+- 1. shall stop timer T4 (Inactivity);
+- 2. shall stop timer T7 (Floor Idle);
+- 3. if the floor is being granted to an IWF floor participant,
+  - a. shall generate and store an SSRC; otherwise
+  - b. shall store the SSRC of the IWF floor participant granted the permission to send media until the floor is released associated to that floor request; and
+- 4. shall enter the 'G: Floor Taken' state as specified in the clause 6.3.4.4.2.
+
+#### 6.3.4.3.4 Timer T7 (Floor Idle) expired
+
+On expiry of timer T7 (Floor Idle) the floor control arbitration logic in the IWF floor control server:
+
+1. shall restart timer T7 (Floor Idle) and increment counter C7 (Floor Idle) by 1 if counter C7 (Floor Idle) has not reached its upper limit;
+2. shall send a Floor Idle message to all MCPTT floor participants in the MCPTT call if counter C7 (Floor Idle) has not reached its upper limit. The Floor Idle message:
+  - a. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+
+NOTE: How the IWF informs IWF media endpoints of the idle floor is out of scope of the present document.
+
+3. shall remain in the 'G: Floor Idle' state.
+
+#### 6.3.4.3.5 Timer T4 (Inactivity) expired
+
+On expiry of timer T4 (Inactivity) the floor control arbitration logic in the IWF floor control server based on a configurable service provider policy either:
+
+1. shall indicate to the application and signalling plane that timer T4 (Inactivity) has expired;
+2. if the application and signalling planes initiates MCPTT call release, shall enter the 'Releasing' state; and
+3. if the application and signalling planes do not initiate MCPTT call release:
+  - a. should restart the T4 (Inactivity) timer; and
+  - b. shall remain in the 'G: Floor Idle' state.
+
+#### 6.3.4.3.6 Receive an implicit floor request (R: Implicit floor request)
+
+Upon receiving an implicit floor request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the floor control arbitration logic in the IWF floor control server:
+
+1. shall reject the request if there is only one media endpoint in the MCPTT call;
+2. if the floor request is rejected the IWF floor control server:
+  - a. shall send the Floor Deny message. The Floor Deny message:
+    - i. shall include in the Reject Cause field the <Reject Cause> value cause #3 (Only one participant); and
+    - ii. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value; and
+  - b. shall remain in the 'G: Floor Idle' state; and
+3. if the floor request is granted the IWF floor control server:
+  - a. shall stop the timer T4 (Inactivity);
+  - b. shall stop the timer T7 (Floor Idle); and
+  - c. shall enter the 'G: Floor Taken' state as specified in the clause 6.3.4.4.2.
+
+#### 6.3.4.4 State: 'G: Floor Taken'
+
+##### 6.3.4.4.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state when it has permitted one or more media endpoints in the MCPTT call to send media.
+
+Timer T1 (End of RTP media) is running when the floor control server is in this state.
+
+Timer T2 (End talking) can be running when the IWF floor control server is in this state.
+
+Timer T20 (Floor Granted) is running to guarantee reliable delivery of the Floor Granted message, if the granted floor request was queued.
+
+#### 6.3.4.4.2 Enter the 'G: Floor Taken' state
+
+When entering this state, the floor control arbitration logic in the IWF floor control server:
+
+1. shall send a Floor Granted message to the MCPTT floor participant to which the floor is granted. The Floor Granted message:
+  - a. shall include the value of timer T2 (Stop talking) in the Duration field;
+  - b. shall include the granted priority in the Floor priority field;
+  - c. if a Track Info field associated with the floor control server state transition diagram for 'general floor control operation' is stored, shall include the stored Track Info field; and
+  - d. if a group call is a broadcast group call, system call, emergency call, an imminent peril call or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+2. shall start timer T20 (Floor Granted) if the floor request was queued for the participant to which the floor is granted and initialise the counter C20 (Floor Granted) to 1;
+3. shall send Floor Taken message to all MCPTT floor participants. The Floor Taken message:
+  - a. shall include the granted user's MCPTT ID in the Granted Party's Identity field, if privacy is not requested;
+  - b. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1;
+  - c. if the session is a broadcast group call, shall include the Permission to Request the Floor field set to '0';
+  - d. if the session is not a broadcast group call, may include the Permission to Request the Floor field set to '1'; and
+  - e. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+NOTE: How the IWF informs IWF media endpoints of the taken floor is out of scope of the present document.
+
+4. shall start timer T1 (End of RTP media) for the participant to which the floor is granted; and
+5. shall set the general state to 'G: Floor Taken' state.
+
+#### 6.3.4.4.3 Timer T1 (End of RTP media) expired
+
+On expiry of timer T1 (End of RTP media), the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop the timer T2 (Stop talking) for the participant to which the floor is granted; if running;
+2. shall stop timer T20 (Granted re-send) for the participant to which the floor is granted, if running;
+3. shall request the media distributor to stop distributing RTP media packets received from the participant for which T1 (End of RTP media) has expired (with the exception of RTP media packets already in the buffer (if RTP media buffering is ongoing)) to other media endpoints; and
+4. shall enter the 'G: Floor Idle' state as specified in the clause 6.3.4.3.2;
+
+#### 6.3.4.4.4 Timer T2 (Stop talking) expired
+
+On expiry of timer T2 (Stop talking), the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop timer T1 (End of RTP media) for the MCPTT participant for which timer T2 has expired;
+2. shall include the Reject Cause field with the <Reject Cause> value set to #2 (Media burst too long) in the Floor Revoke message sent in clause 6.3.4.5.2; and
+3. shall enter the 'G: pending Floor Revoke' state as specified in the clause 6.3.4.5.2.
+
+#### 6.3.4.4.5 Receive RTP media packets (R: RTP media)
+
+Upon receiving an indication from the media distributor that RTP media packets are received from the MCPTT media endpoint, the floor control arbitration logic in the IWF floor control server:
+
+1. shall start timer T2 (Stop talking) for the MCPTT media endpoint from which the RTP packet has been received, if not running;
+2. shall restart timer T1 (End of RTP media) for the participant from which the RTP packet has been received;
+3. shall stop timer T20 (Floor Granted) for the participant from which the RTP packet has been received, if running;
+4. shall forward the RTP media packets to media endpoints according to local policy; and
+
+NOTE: If dual floor control is ongoing as described in clause 6.3.6, the list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
+
+5. shall remain in the 'G: Floor Taken' state.
+
+#### 6.3.4.4.6 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message or upon determining that a user homed in the IWF has released the floor, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor to stop forwarding RTP media packets received from the participant that sent the Floor Release message;
+2. shall stop timer T2 (Stop talking) for the participant that sent the Floor Release message, if running;
+3. shall stop timer T20 (Granted re-send) for the participant that sent the Floor Release message, if running; and
+4. shall enter the 'G: Floor Idle' state as specified in the clause 6.3.4.3.2;
+
+#### 6.3.4.4.6a IWF floor participant release (I: IWF floor participant release)
+
+Upon deciding to release the floor, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor to stop forwarding RTP media packets; and
+2. shall enter the 'G: Floor Idle' state as specified in the clause 6.3.4.3.2.
+
+#### 6.3.4.4.7 Receive Floor Request message with pre-emptive priority (R: pre-emptive Floor Request)
+
+NOTE: This procedure is also invoked from the clause 6.3.5.4.4.
+
+On receipt of a floor request message with effective priority indicating pre-emptive priority, and if the effective priority of the floor participant with permission to send media is not the pre-emptive priority, the floor control arbitration logic in the IWF floor control server:
+
+1. based on local policy, select one of the following options:
+  - a. revoke the current speaker; or
+  - b. allow media from both the current speaker and from the participant now requesting floor with a pre-emptive floor priority;
+2. if revoking current speaker is selected:
+  - a. shall stop timer T1 (End of RTP media), if running;
+  - b. shall stop timer T20 (Floor Granted), if running;
+  - c. shall include a Reject Cause field with the <Reject Cause> value set to #4 (Media Burst pre-empted) in the Floor Revoke message sent in clause 6.3.4.5.2;
+
+- d. shall enter the 'G: pending Floor Revoke' state as specified in the clause 6.3.4.5.2;
+  - e. shall insert the MCPTT floor participant into the active floor request queue to the position in front of all queued requests, if not inserted yet or update the position of the floor participant in the active floor request queue to the position in front of all other queued requests, if already inserted; and
+  - f. shall send a Floor Queue Position Info message to the requesting MCPTT floor participant, if negotiated support of queueing of floor requests as specified in clause 14. The Floor Queue Position Info message:
+    - i. include the queue position and floor priority in the Queue Info field; and
+    - ii. if the Floor Request message included a Track Info field, shall include the received Track Info field; and
+3. if allow media from both the current speaker and from the participant now requesting floor with a pre-emptive priority is selected:
+- a. shall perform the actions specified in the clause 6.3.6.2.2.
+
+#### 6.3.4.4.7a        Receive Floor Request message multi-talker (R: multi-talker Floor Request)
+
+The multi-talker feature is not supported in this version of the present document.
+
+#### 6.3.4.4.8        Receive Floor request message from MCPTT floor participant (R: Floor Request)
+
+Upon receiving a floor request message from the MCPTT floor participant that has been granted permission to send media, the floor control arbitration logic in the IWF floor control server:
+
+- 1. shall send a Floor Granted message to the previously granted MCPTT floor participant. The Floor Granted message:
+  - a. shall include the value of timer T2 (Stop talking) running for this MCPTT floor participant in the Duration field;
+  - b. shall include the granted priority in the Floor priority field; and
+- c. if the Floor Request message included a Track Info field, shall include the received Track Info field; and
+- 2. shall remain in the 'G: Floor Taken' state.
+
+#### 6.3.4.4.9        Timer T20 (Floor Granted) expired
+
+On expiry of timer T20 (Floor Granted), the floor control arbitration logic in the IWF floor control server:
+
+- 1. shall send a Floor Granted message to the granted floor participant if counter C20 (Floor Granted) has not reached its upper limit: The Floor Granted message:
+  - a. shall include the value of timer T2 (Stop talking) in the Duration field;
+  - b. shall include the granted priority in the Floor priority field; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+- 2. shall start timer T20 (Floor Granted) and increment counter C20 (Floor Granted) by 1 if counter C20 (Floor Granted) has not reached its upper limit; and
+- 3. shall remain in the 'G: Floor Taken' state.
+
+#### 6.3.4.4.10       Timer T20 (Floor Granted) expired N times
+
+When timer T20 (Floor Granted) expires and counter C20 (Floor Granted) reaches its upper limit, the floor control arbitration logic in the IWF floor control server:
+
+- 1. shall remain in the 'G: Floor Taken' state.
+
+#### 6.3.4.4.11 MCPTT media endpoint release (R: client release)
+
+If the IWF floor control server receives an indication from the floor control interface towards the MCPTT client that the MCPTT media endpoint has started to disconnect from the MCPTT call, or the IWF decides to release the floor, the floor control arbitration logic in the floor control server:
+
+1. shall enter the 'G: Floor Idle' state as specified in the clause 6.3.4.3.2.
+
+#### 6.3.4.4.12 Receive an implicit floor request (R: Implicit floor request)
+
+Upon receiving an implicit floor request due to an upgrade to an emergency group call or due to an upgrade to imminent peril call, the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop timer T1 (End of RTP media), if running;
+2. shall stop timer T20 (Floor Granted), if running;
+3. shall set the Reject Cause field in the Floor Revoke message to #4 (Media Burst pre-empted);
+4. shall enter the 'G: pending Floor Revoke' state as specified in the clause 6.3.4.5.2;
+5. shall insert the MCPTT floor participant into the active floor request queue to the position in front of all queued requests, if not inserted yet or update the position of the floor participant in the active floor request queue to the position in front of all other queued requests, if already inserted; and
+6. shall send a Floor Queue Position Info message to the requesting MCPTT floor participant, if negotiated support of queueing floor requests as specified in clause 14. The Floor Queue Position Request message:
+  - a. shall include the queue position and floor priority in the Queue Info field; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications.
+
+#### 6.3.4.5 State: 'G: pending Floor Revoke'
+
+##### 6.3.4.5.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state after having sent a Floor Revoke message to the MCPTT floor participant.
+
+Timer T3 (Stop talking grace) is running when the floor control arbitration logic in the IWF floor control server is in this state.
+
+In this state, the IWF forwards RTP media packets to the MCPTT media endpoints in the MCPTT call.
+
+##### 6.3.4.5.2 Enter the 'G: pending Floor Revoke' state
+
+When entering this state, the floor control arbitration logic in the IWF floor control server:
+
+1. shall send the Floor Revoke message to the MCPTT floor participant. The Floor Revoke message:
+  - a. shall include the reason for sending the Floor Revoke message in the <Reject Cause> value in the Reject Cause field; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+2. shall start timer T3 (Stop talking grace) for which a Floor Revoke message has been sent; and
+3. shall set the general state to 'G: pending Floor Revoke'.
+
+##### 6.3.4.5.3 Receive RTP media packets (R: RTP media)
+
+Upon receiving an indication from the media distributor that RTP media packets are received from the permitted floor participant the IWF floor control server:
+
+1. shall restart timer T1 (End of RTP media);
+
+NOTE 1: If the upper limit for timer T3 (Stop talking grace) is less than the upper limit of timer T1 (End of RTP media) then timer T1 (End of RTP media) will not expire.
+
+2. shall instruct the media distributor to forward the RTP media packets to MCPTT media endpoints according to local policy; and
+
+NOTE 2: If dual floor control is ongoing as described in clause 6.3.6, the list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
+
+3. shall remain in the 'G: pending Floor Revoke' state.
+
+#### 6.3.4.5.4 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message for which a Floor Revoke message has been sent, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor to stop forwarding RTP media packets;
+2. shall stop timer T1 (End of RTP media) , if running;
+3. shall stop timer T3 (Stop talking grace);
+4. if the active floor request queue is not empty the IWF floor control server shall enter the 'G: Idle' state as specified in the clause 6.3.4.3.2; and
+5. if the active floor request queue is empty the IWF floor control server shall enter the 'G: Idle' state as specified in the clause 6.3.4.3.2.
+
+#### 6.3.4.5.5 Timer T3 (Stop talking grace) expired
+
+On expiry of timer T3 (Stop talking grace) for which a Floor Revoke message has been sent, the floor control arbitration logic in the IWF floor control server:
+
+1. shall indicate to the interface towards the MCPTT client that the general state machine is now 'G: Floor Idle'; and
+2. shall enter the 'G: Idle' state as specified in the clause 6.3.4.3.2.
+
+#### 6.3.4.5.6 Timer T1 (End of RTP media) expired
+
+On expiry of timer T1 (End of RTP media) assigned to the MCPTT floor participant for which a Floor Revoke message has been sent, the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop timer T3 (Stop talking grace); and
+2. if the floor is now empty; shall enter the 'G: Floor Idle' state as specified in the clause 6.3.4.3.2.
+
+On expiry of timer T1 (End of RTP media) assigned to a participant different than the MCPTT floor participant for which a Floor Revoke message has been sent, the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop forwarding related RTP media packets;
+2. shall stop timer T2 (Stop talking) for the MCPTT floor participant for which timer T1 (End of RTP media) expired, if running; and
+3. shall stop timer T20 (Granted re-send) for the participant, if running.
+
+#### 6.3.4.6 In any state
+
+##### 6.3.4.6.1 General
+
+This clause describes the actions to be taken in all states defined for the general state diagram with the exception of the 'Start-stop' state.
+
+##### 6.3.4.6.2 Receive MCPTT call release - 1
+
+This clause is used by the floor control arbitration logic in the IWF floor control server when an MCPTT call is released.
+
+Upon receiving an MCPTT call release step 1 request from the application and signalling plane or upon determining that a user homed in the IWF has released the call, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor to stop sending RTP media packets to MCPTT media endpoints; and
+2. shall enter the 'Releasing' state.
+
+#### 6.3.4.6.3 Receive an instruction to merge group calls (R: Merge)
+
+Upon receiving an instruction from the application and signalling plane to merge the ongoing group call with other group calls, the IWF floor control server:
+
+1. shall perform the actions in clause 6.5.2.3; and
+2. shall enter the 'Start-stop' state.
+
+#### 6.3.4.7 State: 'Releasing'
+
+##### 6.3.4.7.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state while waiting for the application and signalling plane to finalize the disconnection of an MCPTT call.
+
+##### 6.3.4.7.2 Receive MCPTT call release - 2
+
+Upon receiving an MCPTT call release step 2 request from the application and signalling plane, the floor control arbitration logic in the IWF floor control server:
+
+1. shall release all resources reserved in the media plane including the instances used for the 'Floor control server state transition diagram for general floor control operation', and 'Floor control server state transition diagram for basic floor control operation towards the floor participant' state machines and any running timers associated with the state machines; and
+2. shall enter the 'Start-stop' state.
+
+#### 6.3.4.8 State: 'G: Floor Initialising'
+
+##### 6.3.4.8.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state while waiting for all invited constituent MCPTT groups to reply with a final SIP response.
+
+There are no timers running in this state. The floor control arbitration logic is relying on SIP timers in the signalling and application plane.
+
+##### 6.3.4.8.2 Enter the 'G: Initialising' state
+
+When entering this state, the floor control arbitration logic:
+
+1. shall set the general state to the 'G: Initialising' state.
+
+##### 6.3.4.8.3 Receiving a floor request from a constituent MCPTT group (R: mcptt-floor-request)
+
+Upon receiving an indication from the application and signalling plane that a floor request is received from one of the invited constituent MCPTT groups in an application/vnd.3gpp.mcptt-floor-request+xml MIME body, the floor control arbitration logic:
+
+1. shall cache the application/vnd.3gpp.mcptt-floor-request+xml MIME body; and
+2. remain in the 'G: Initialising' state.
+
+##### 6.3.4.8.4 All final SIP responses received (R: final SIP responses)
+
+Upon receiving an indication from the application and signalling plane that all invited constituent MCPTT groups have sent a final SIP response, the floor control arbitration logic:
+
+1. if at least one application/vnd.3gpp.mcptt-floor-request+xml MIME body exists with the <floor-type> element set to "general":
+  - a. shall select the floor participant with the highest priority as described in clause 4.1.1.4:
+    - i. among the cached application/vnd.3gpp.mcptt-floor-request+xml MIME bodies with the <floor-type> element set to "general"; and
+    - ii. the floor participant initialising the temporary group session as described in clause 4.1.1.4, if the floor participant initialising the temporary group session negotiated implicit floor request as specified in clause 14;
+  - b. shall send a Floor Revoke message to all MCPTT floor participants in the cached application/vnd.3gpp.mcptt-floor-request+xml MIME body with the <floor-type> element set to "general" that are not granted the permission to send media. The Floor Revoke message:
+    - i. shall include the <Reject Cause> value set to '4' (Media Burst pre-empted) in the Reject Cause field;
+    - ii. shall include information taken from the <track-info> element in the cached application/vnd.3gpp.mcptt-floor-request+xml MIME body with the <floor-type> element set to "general" in the Track Info field; and
+    - iii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+
+NOTE 1: How the IWF informs IWF media endpoints of the floor revoke is out of scope of the present document.
+
+- c. if the floor participant selected to be granted the floor is in one of invited constituent MCPTT groups:
+  - i. shall convert the <track-info> element to a format of a Track Info field and cache the Track Info field associated with the floor control server state transition diagram for 'general floor control operation'; and
+  - ii. shall enter the 'G: Taken' state as specified in the clause 6.3.4.4.2 using the selected floor participant as the requesting floor participant;
+2. if at least one application/vnd.3gpp.mcptt-floor-request+xml MIME body exists with the <floor-type> element set to "dual":
+  - a. shall select the floor participant with the highest priority as described in clause 4.1.1.4 among the cached application/vnd.3gpp.mcptt-floor-request+xml MIME bodies with the <floor-type> element set to "dual"; and
+  - b. shall send a Floor Revoke message to all floor participants in the cached application/vnd.3gpp.mcptt-floor-request+xml MIME body with the <floor-type> element set to "dual" that are not granted the permission to send media. The Floor Revoke message:
+    - i. shall include the <Reject Cause> value set to '4' (Media Burst pre-empted) in the Reject Cause field;
+    - ii. shall include information taken from the <track-info> element in the cached application/vnd.3gpp.mcptt-floor-request+xml MIME body with the <floor-type> element set to "general" in the Track Info field;
+    - iii. shall include the Floor Indicator with the G-bit set to '1' (Dual floor);
+    - iv. shall convert the <track-info> element to a format of a Track Info field and cache the Track Info field associated with floor control server state transition diagram for 'dual floor control operation'; and
+    - v. shall enter the 'D: Floor Taken' state as specified in the clause 6.3.6.3.2 using the selected floor participant as the requesting floor participant; and
+
+NOTE 2: How the IWF informs IWF media endpoints of the floor revoke is out of scope of the present document.
+
+3. if no cached application/vnd.3gpp.mcptt-floor-request+xml MIME with the <floor-type> element set to "general" body exists:
+  - a. if an implicit floor request is negotiated as described in clause 14 when the temporary group session was established, shall enter the 'G: Taken' state as specified in the clause 6.3.4.4.2; and
+  - b. if an implicit floor request is not negotiated as described in clause 14 when the temporary group session was established, shall enter the 'G: Idle' state as specified in the clause 6.3.4.3.2.
+
+## 6.3.5 Floor control server state transition diagram for basic floor control operation towards the floor participant
+
+### 6.3.5.1 General
+
+The floor control interface towards the MCPTT client in the IWF floor control server shall behave according to the state diagram and state transitions specified in this clause.
+
+**Editor's Note:** procedures for the IWF performing the non-controlling role are FFS.
+
+The description of the floor control interface towards an IWF media endpoint is part of the general floor control server state diagram and state transitions specified in clause 6.3.4.
+
+Figure 6.3.5.1-1 shows the states and state transitions for an associated floor participant in the floor control server.
+
+![State transition diagram for floor control. States include: Any state, Start-stop state, Releasing, U: not permitted and initiating, U: permitted, U: pending Floor Revoke, U: not permitted and Floor Idle, U: not permitted and Floor Taken, U: not permitted but sends media. Transitions are triggered by SIP Session initiated, R: Floor Request, S: Floor Granted, R: Floor Release, S: Floor Idle, S: Floor Taken, R: RTP media, S: Floor Revoke, T8 (Floor Revoke) expired, R: Merge, R: MCPTT session release - 1, R: MCPTT session release - 2.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Start-stop state : R: Merge
+    [*] --> Releasing : R: MCPTT session release - 1
+    Releasing --> Start-stop state : R: MCPTT session release - 2
+    Start-stop state --> U: not permitted and initiating : SIP Session initiated
+    Start-stop state --> U: not permitted and Floor Idle : S: Floor Idle
+    Start-stop state --> U: permitted : [SIP session initiated AND implicit floor request]
+    Start-stop state --> U: not permitted and Floor Taken : S: Floor Taken
+    U: not permitted and initiating --> U: permitted : S: Floor Granted
+    U: not permitted and initiating --> U: not permitted and Floor Idle : R: Floor Request OR R: Floor Release
+    U: not permitted and initiating --> U: permitted : R: Floor Request OR R: RTP media OR R: Floor Release
+    U: permitted --> U: not permitted and Floor Idle : S: Floor Idle
+    U: permitted --> U: not permitted and Floor Taken : S: Floor Taken
+    U: permitted --> U: pending Floor Revoke : S: Floor Revoke
+    U: permitted --> U: not permitted and Floor Taken : S: Floor Taken
+    U: permitted --> U: not permitted and Floor Idle : R: Floor Request OR S: Floor Granted
+    U: pending Floor Revoke --> U: permitted : T8 (Floor Revoke) expired OR R: RTP media OR R: Floor Release
+    U: pending Floor Revoke --> U: not permitted and Floor Idle : S: Floor Idle
+    U: pending Floor Revoke --> U: not permitted and Floor Taken : S: Floor Taken
+    U: not permitted and Floor Idle --> U: permitted : S: Floor Idle
+    U: not permitted and Floor Idle --> U: not permitted and Floor Taken : S: Floor Taken
+    U: not permitted and Floor Idle --> U: not permitted but sends media : R: RTP media
+    U: not permitted and Floor Idle --> U: not permitted and Floor Taken : R: Floor Release
+    U: not permitted and Floor Idle --> U: not permitted and Floor Idle : Floor Request OR Floor Release OR R: Media OR S: Floor Deny OR R: Implicit floor request OR S: Floor Idle
+    U: not permitted and Floor Taken --> U: permitted : S: Floor Idle
+    U: not permitted and Floor Taken --> U: not permitted and Floor Idle : S: Floor Idle
+    U: not permitted and Floor Taken --> U: not permitted but sends media : R: RTP media
+    U: not permitted and Floor Taken --> U: not permitted and Floor Taken : Floor Request OR R: Floor Release OR R: Floor Queue Position Request OR R: Implicit floor request OR S: Floor Taken
+    U: not permitted but sends media --> U: not permitted and Floor Idle : R: Floor Release
+    U: not permitted but sends media --> U: not permitted and Floor Taken : R: Floor Release
+    U: not permitted but sends media --> U: not permitted but sends media : T8 (Floor Revoke) expired
+  
+```
+
+State transition diagram for floor control. States include: Any state, Start-stop state, Releasing, U: not permitted and initiating, U: permitted, U: pending Floor Revoke, U: not permitted and Floor Idle, U: not permitted and Floor Taken, U: not permitted but sends media. Transitions are triggered by SIP Session initiated, R: Floor Request, S: Floor Granted, R: Floor Release, S: Floor Idle, S: Floor Taken, R: RTP media, S: Floor Revoke, T8 (Floor Revoke) expired, R: Merge, R: MCPTT session release - 1, R: MCPTT session release - 2.
+
+**Figure 6.3.5.1-1: Floor control server state transition diagram for basic floor control operation towards the floor participant**
+
+The floor control interface towards the MCPTT client in the IWF floor control server shall create one instance of the 'basic floor control operations' state machine towards the MCPTT client for every floor participant served by the IWF floor control server as follows:
+
+1. For pre-arranged group call in case of an originating MCPTT call, the 'basic floor control operation towards the floor participant' state machine shall be created when the MCPTT server sends the SIP 200 (OK) response towards the originating MCPTT client.
+2. For pre-arranged group call in case of a terminating MCPTT call, the 'basic floor control operation towards the floor participant' state machine shall be created when the IWF floor control server receives the SIP 200 (OK) response.
+3. For chat group call the 'basic floor control operation state machine towards the floor participant' shall be created when the MCPTT server sends the SIP 200 (OK) response to the received initial SIP INVITE request.
+
+The floor participant associated to the 'basic floor control operation towards the floor participant' state machine is here referred to as the "associated floor participant".
+
+The external inputs to the state machine are:
+
+1. directives coming from the floor control arbitration logic;
+2. floor messages sent by the floor participants;
+3. media; and
+4. in certain cases, SIP messages used for call handling.
+
+If floor control messages or RTP media packets arrives in a state where there is no procedure specified in the following clauses, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall discard the floor control message;
+2. shall request the network media interface in the MCPTT server to discard any received RTP media packet; and
+3. shall remain in the current state.
+
+State details are explained in the following clauses.
+
+### 6.3.5.2 State: 'Start-stop'
+
+#### 6.3.5.2.1 General
+
+When a new instance of the 'basic floor control operations towards the floor participant' state machine is created, before any floor control related input is applied, the state machine is in the 'Start-stop' state. Similarly, when the call is released the state machine shall return to the Start-Stop state.
+
+An association between the IWF floor control server and a floor participant in the MCPTT client is created, when the state machine is created; and
+
+1. in case of an originating MCPTT call, when the MCPTT server sends the SIP 200 (OK) response to the originating MCPTT client; and
+2. in case of a terminating MCPTT call, when the IWF floor control server receives the SIP 200 (OK) response sent from the terminating MCPTT client.
+
+#### 6.3.5.2.2 SIP Session initiated
+
+When a SIP Session is established and if:
+
+1. the session is not a temporary group call session; or
+
+2. the session is a temporary group call session and the associated floor participant is an invited MCPTT client (i.e. not a constituent MCPTT group);
+
+then:
+
+NOTE 1: A MCPTT group call is a temporary group session when the <on-network-temporary> element is present in the <list-service> element as specified in 3GPP TS 24.481 [12].
+
+1. if an MCPTT client initiates an MCPTT call with an implicit floor request, and the MCPTT call does not exist yet, the floor control interface towards the MCPTT client in the IWF floor control server:
+  - a. shall initialize a general state machine as specified in clause 6.3.4.2.2; and
+
+NOTE 2: In the clause 6.3.4.2.2 the 'general floor control operation' state machine will continue with the initialization of the 'general floor control operation' state machine.
+
+- b. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;
+2. if the associated MCPTT client rejoins an ongoing MCPTT call without an implicit floor request or initiates or joins a chat group call without an implicit floor request or attempts to initiate an already existing MCPTT call without an implicit floor request, and
+
+- a. if an MCPTT call already exists but no MCPTT client has the permission to send a media, the floor control interface towards the MCPTT client in the IWF floor control server:
+  - i. should send a Floor Idle message to the MCPTT client. The Floor Idle message:
+    - A. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+    - B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - ii. shall enter the state 'U: not permitted and Floor Idle' as specified in the clause 6.3.5.5.2;
+- b. if an MCPTT call is initiated, the floor control interface towards the MCPTT client in the IWF floor control server:
+  - i. shall enter the state 'U: not permitted and Floor Idle' as specified in the clause 6.3.5.5.2; and
+  - ii. shall initialize a general state machine as specified in clause 6.3.4.2.2; and
+
+NOTE 3: In the clause 6.3.4.2.2 the general state machine will continue with the initialization of the general state machine.
+
+- c. if another MCPTT client has the permission to send a media, the floor control interface towards the MCPTT client in the IWF floor control server:
+  - i. should send a Floor Taken message to the MCPTT client. The Floor Taken message:
+    - A. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+    - B. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1;
+    - C. if the session is a broadcast group call, shall include the Permission to Request the floor field set to '0';
+    - D. if the session is not a broadcast group call, may include the Permission to Request the floor field set to '1'; and
+    - E. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications
+  - ii. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2;
+
+3. if the associated floor participant attempts to initiate an already existing MCPTT call with an implicit floor request, and
+    - a. if no MCPTT client has the permission to send media, the floor control interface towards the MCPTT client in the IWF floor control server:
+      - i. shall process the implicit floor request as if a Floor Request message was received as specified in clause 6.3.4.3.3; and
+      - ii. shall enter the state 'U: permitted' as specified in the clause 6.3.5.5.2;
+    - b. if the MCPTT client negotiated support of queueing floor requests as specified in clause 14 and if another MCPTT client has the permission to send media, the floor control interface towards the MCPTT client in the IWF floor control server:
+      - i. shall set the priority level to the negotiated maximum priority level that the MCPTT client is permitted to request, except for pre-emptive priority, when high priority is used;
+- NOTE 4: The maximum floor priority the floor participant is permitted to request is negotiated in the "mc\_priority" fmtp attribute as specified in clause 14.
+- NOTE 5: The initial implicit floor request will not result in pre-emption when an MCPTT client is joining an ongoing MCPTT call. If the MCPTT client wants to pre-empt the current MCPTT client that is sending media, an explicit floor request with pre-emptive floor priority is required.
+- ii. shall insert the MCPTT client into the active floor request queue to the position immediately following all queued floor requests with the same floor priority;
+  - iii. shall send a Floor Queue Position Info message to the MCPTT client. The Floor Queue Position Info message:
+    - A shall include the queue position and floor priority in the Queue Info field; and
+    - B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+  - iv. should send a Floor Queue Position Info message with the updated status to the MCPTT clients in the active floor request queue which negotiated queueing of floor requests as specified in clause 14, which have requested the queue status, whose queue position has been changed since the previous Floor Queue Position Info message and which is not the joining MCPTT client. The Floor Queue Position Info message:
+    - A shall include the queue position and floor priority in the Queue Info field; and
+    - B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - v. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2; and
+- c. if the MCPTT client did not negotiate queueing of floor requests and if another MCPTT client has the permission to send a media, the floor control interface towards the MCPTT client in the IWF floor control server:
+    - i. shall send a Floor Taken message to the MCPTT client. The Floor Taken message:
+      - A. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+      - B. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1;
+      - C. if the session is a broadcast group call, shall include the Permission to Request the floor field set to '0';
+      - D. if the session is not a broadcast group call, may include the Permission to Request the floor field set to '1'; and
+
+- E. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - ii. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2; and
+4. if the MCPTT client is invited to the MCPTT call and
+- a. if another MCPTT client has permission to send a media, the floor control interface towards the MCPTT client in the IWF floor control server:
+    - i. should send a Floor Taken message to the MCPTT client. The Floor Taken message:
+      - A. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+      - B. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1;
+      - C. if the session is a broadcast group call, shall include the Permission to Request the floor field set to '0';
+      - D. if the session is not a broadcast group call, may include the Permission to Request the floor field set to '1'; and
+      - E. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - ii. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2; and
+  - b. if no other MCPTT client has the permission to send a media; the floor control interface towards the MCPTT client in the IWF floor control server:
+    - i. should send a Floor Idle message to the MCPTT client. The Floor Idle message:
+      - A. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+      - B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - ii. shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2.
+
+When a SIP Session is established and if the session is a temporary group call session and,
+
+- 1. if the associated floor participant is a constituent MCPTT group; or
+- 2. if the associated floor participant is the initiator of the temporary group session;
+
+then the floor control interface towards the MCPTT client:
+
+- 1. shall initialize a general state machine as specified in clause 6.3.4.2.2, if not already initiated; and
+- 2. shall enter the 'U: not permitted and initiating' state as specified in clause 6.3.5.10.2.
+
+### 6.3.5.3 State: 'U: not permitted and Floor Idle'
+
+#### 6.3.5.3.1 General
+
+The floor control interface towards the MCPTT client in the IWF floor control server uses this state when the associated floor participant is not permitted to send media.
+
+#### 6.3.5.3.2 Enter state 'U: not permitted and Floor Idle'
+
+When entering this state, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. if a Track Info field is stored, shall remove the Track Info field from the storage; and
+- 2. shall set the state for the associated floor participant to 'U: not permitted and Floor Idle'.
+
+#### 6.3.5.3.3 Send Floor Taken message (S: Floor Taken)
+
+When a Floor Taken message is received from the floor control server arbitration logic, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Taken message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Taken message to '1' (Acknowledgment is required) as described in clause 8.3.2, and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2.
+
+#### 6.3.5.3.4 Receive Floor Request message (R: Floor Request)
+
+Upon receiving a Floor Request message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the session is not a broadcast group call or if the session is a broadcast group call and the associated floor participant is the initiator of the broadcast group call, shall forward the Floor Request message to the floor control server arbitration logic;
+
+NOTE 1: The Floor Request message can contain a Floor Indicator field indicating that the floor request is an attempt to upgrade a group call to a broadcast group call. If the floor control arbitration logic accepts the floor request, the ongoing group call will be upgraded accordingly by the Floor Granted message and, for other participants, by the Floor Taken message.
+
+NOTE 2: Initiating a broadcast group call is done in the application and signalling plane using SIP. Initiating or upgrading a call to an emergency call or an imminent peril call is done in the application and signalling plane using SIP.
+
+2. if the session is a broadcast group call and the associated floor participant is not the initiator of the broadcast group call, shall send a Floor Deny message to the associated floor participant. The Floor Deny message:
+
+- a. shall include in the Reject Cause field the <Reject Cause> value cause #5 (Receive only);
+- b. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value;
+- c. may set the first bit in the subtype of the Floor Deny message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 3: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+
+3. shall remain in the 'U: not permitted and Floor Idle' state.
+
+#### 6.3.5.3.5 Send Floor Grant message (S: Floor Grant)
+
+When a Floor Granted message is received from the floor control arbitration logic in the IWF, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Granted messages to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Granted message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the state 'U: permitted' as specified in clause 6.3.5.5.2.
+
+#### 6.3.5.3.6 Send Floor Deny message (S: Floor Deny)
+
+When a Floor Deny message is received from the floor control arbitration logic in the IWF, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Deny messages to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Deny message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall remain in the 'U: not permitted and Floor Idle' state.
+
+#### 6.3.5.3.7 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+
+- a. shall include the Message Type field set to '4' (Floor Release); and
+- b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+
+2. shall send a Floor Idle message to the associated floor participant. The Floor Idle message:
+
+- a. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1;
+- b. may set the first bit in the subtype of the Floor Idle message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+3. if a Track Info field is included in the Floor Release message, shall use the topmost <Participant Reference> value and the SSRC in the received Floor Release message to check if the floor participant has a queued floor request;
+
+4. if a no Track Info field is included in the Floor Release message, shall use the SSRC in the received Floor Release message to check if the floor participant has a queued floor request;
+
+5. if the floor participant has a floor request in the queue, shall remove the queued floor request from the queue; and
+
+6. shall remain in the state 'U: not permitted and Floor Idle' state.
+
+#### 6.3.5.3.8 Receive RTP media packets (R: media)
+
+Upon receiving an indication from the network media interface that RTP media packets are received with payload from the associated floor participant and if Floor Release message was received in the previous 'U: permitted' state, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+NOTE: Reception of unauthorized RTP media packets can only happen if the associated floor participant is in an MCPTT client. If the associated floor participant is a floor control server interface in a non-controlling MCPTT function of an MCPTT group, the unauthorized RTP media packets are handled in the non-controlling MCPTT function.
+
+1. shall request the network media interface in the MCPTT server to not forward the received RTP media packets to the media distributor in the MCPTT server;
+2. shall send a Floor Revoke message to the associated floor participant. The Floor Revoke message:
+
+- a. shall include the Reject Cause field with the <Reject Cause> value set to #3 (No permission to send a Media Burst); and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+3. shall enter the 'U: not permitted but sends media' state as specified in the clause 6.3.5.7.2.
+
+#### 6.3.5.3.9 Receive an implicit floor request (R: Implicit floor request)
+
+When an ongoing session is upgraded to an emergency group call and when the application and signalling plane indicates that a subsequent SDP offer included the "mc\_implicit\_request" fmtp attribute as described in clause 14, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall indicate to the floor control server arbitration logic that an implicit floor request is received due to an upgrade to an emergency group call; and
+2. shall remain in the 'U: not permitted and Floor Idle' state.
+
+#### 6.3.5.3.10 Send Floor Idle message (S: Floor Idle)
+
+When receiving a Floor Idle message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Idle message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Idle message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall remain in the 'U: not permitted and Floor Idle' state.
+
+#### 6.3.5.4 State 'U: not permitted and Floor Taken'
+
+##### 6.3.5.4.1 General
+
+The floor control interface towards the MCPTT client in the IWF floor control server uses this state when another MCPTT client (i.e. not the associated floor participant) has been given permission to send media.
+
+In this state RTP media packets received from the media distributor in the MCPTT server are forwarded to the associated floor participant by the network media interface in the MCPTT server.
+
+##### 6.3.5.4.2 Enter state 'U: not permitted and Floor Taken'
+
+When entering this state, the IWF floor control server:
+
+1. if a Track Info field is stored, shall remove the Track Info field from the storage; and
+2. shall set the state to 'U: not permitted and Floor Taken'.
+
+##### 6.3.5.4.3 Send Floor Idle message (S: Floor Idle)
+
+When receiving a Floor Idle message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Idle message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Idle message to '1' (Acknowledgment is required) as described in clause 8.3.2;
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. if an indication is stored that the participant is listening to media from two sources, i.e. dual floor control is applied,
+
+- a. shall remain in the 'U: not permitted and Floor Taken' state; and
+  - b. shall remove the indication that a participant is listening to media from two sources; and
+4. if an indication for dual floor control is not stored, shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2.
+
+#### 6.3.5.4.4 Receive Floor Request message (R: Floor Request)
+
+Upon receiving a Floor Request message from the associated floor participant, if the group is configured for audio cut-in floor control, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Request message to the floor control server arbitration logic; and
+2. shall remain in the 'U: not permitted and Floor Taken' state.
+
+Upon receiving a Floor Request message, without a Floor Indicator field or with the Floor Indicator field included where the D-bit (Emergency call) and the E-bit (Imminent peril call) are set to '0', from the associated floor participant, and if the MCPTT client did not negotiate queueing of floor requests or did not include a priority in the "mc\_priority" fmtp attribute as specified in clause 14, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send a Floor Deny message to the associated floor participant. The Floor Deny message:
+  - a. shall include in the Reject Cause field the <Reject Cause> value cause #1 (Another MCPTT client has permission);
+  - b. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value;
+  - c. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+  - d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+2. may set the first bit in the subtype of the Floor Deny message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 1: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall remain in the 'U: not permitted and Floor Taken' state.
+
+Upon receiving a Floor Request message from the associated floor participant and the session is a broadcast group call, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send a Floor Deny message to the associated floor participant. The Floor Deny message:
+  - a. shall include in the Reject Cause field the <Reject Cause> value cause #5 (Receive only);
+  - b. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+2. may set the first bit in the subtype of the Floor Deny message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 2: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall remain in the 'U: not permitted and Floor Taken' state.
+
+Upon receiving a Floor Request message from the associated floor participant and if the MCPTT client negotiated support of queueing of floor requests or included a floor priority in the "mc\_priority" or both as described in specified in
+
+clause 14 and according to local policy, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall determine the effective priority level as described in clause 4.1.1.4 by using the following parameters:
+  - a. the floor priority shall be:
+    - i. the lower of the floor priority included in Floor Request message and the negotiated maximum floor priority that the MCPTT client is permitted to request, if the MCPTT client negotiated floor priority "mc\_priority" and floor priority is included in the Floor Request message;
+    - ii. the receive only floor priority, if the MCPTT client negotiated floor priority in the "mc\_priority" fmtp attribute and if the negotiated maximum floor priority that the MCPTT client is permitted to request is "receive only";
+    - iii. the default priority, if the MCPTT client negotiated floor priority in the "mc\_priority" fmtp attribute, if the negotiated maximum floor priority that the MCPTT client is permitted to request is not receive only and if the floor priority is not included in the Floor Request message; and
+    - iv. the default priority, if the MCPTT client did not negotiate floor priority in the "mc\_priority" fmtp attribute; and
+  - b. the type of the call shall be
+    - i. if the Floor Indicator field is included in the message and the D-bit (Emergency call bit) is set to '1', determined to be an emergency call;
+    - ii. if the Floor Indicator field is included in the message and the E-bit (Imminent peril call) is set to '1', determined to be an imminent peril call; and
+    - iii. if the Floor Indicator field is not included in the message or the Floor Indicator field is included and neither the D-bit (Emergency call bit) nor the E-bit (Imminent peril call) is set to '1', determined to be a normal call;
+2. if the effective priority is "receive only", the floor control interface towards the MCPTT client in the IWF floor control server:
+  - a. shall send a Floor Deny message to the floor participant. The Floor Deny message:
+    - i. shall include in the Reject Cause field the <Reject Cause> value cause #5 (Receive only) ;
+    - ii. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value;
+    - iii. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+    - iv. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - b. shall remain in the 'U: not permitted and Floor Taken' state;
+3. if
+  - a. a Track Info field is included in the Floor Request message, shall use the topmost <Participant Reference> value and the SSRC in the received Floor Request message to check if the floor participant has a queued floor request; or
+  - b. a Track Info field is not included in the Floor Request message, shall use the SSRC in the received Floor Request message to check if the floor participant has a queued floor request;
+4. if the floor participant already has a queued floor request with the same effective priority level, the floor control interface towards the MCPTT client in the IWF floor control server:
+  - a. shall send a Floor Queue Position Info message to the requesting MCPTT client, if the MCPTT client negotiated support of queueing of floor requests as specified in clause 14. The Floor Queue Position Info message:
+
+- i. shall include the queue position and floor priority in the Queue Info field;
+    - ii. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+    - iii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - b. shall remain in the 'U: not permitted and Floor Taken' state
+5. if the effective priority level is pre-emptive and there are no other pre-emptive requests in the active floor request queue and the effective priority level of the current MCPTT client with permission to send a media is not the pre-emptive priority, the floor control interface towards the MCPTT client in the IWF floor control server:
+- a. shall forward the Floor Request message to the floor control server arbitration logic indicating that a Floor Request message with pre-emptive priority is received; and
+  - b. shall remain in the 'U: not permitted and Floor Taken' state
+- NOTE 3: The Floor control server arbitration logic initiates revoking the permission to send media towards the current MCPTT client with the permission to send media as specified in the clause 6.3.4.4.7;
+6. if the MCPTT client did not negotiate support of queueing of floor requests as specified in clause 14, the effective priority level is pre-emptive and either other pre-emptive request is queued or the effective priority level of the current MCPTT client with permission to send a media is the pre-emptive priority, the floor control interface towards the MCPTT client in the IWF floor control server:
+- a. shall send a Floor Deny message to the associated floor participant. The Floor Deny message:
+    - i. shall include in the Reject Cause field the <Reject Cause> value cause #1 (Another MCPTT client has permission);
+    - ii. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value;
+    - iii. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+    - iv. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - b. shall remain in the 'U: not permitted and Floor Taken' state;
+7. if the MCPTT client did not negotiate "queueing" and the effective priority level is not pre-emptive, the floor control interface towards the MCPTT client in the IWF floor control server:
+- a. shall send a Floor Deny message to the associated floor participant. The Floor Deny message:
+    - i. shall include in the Reject Cause field the <Reject Cause> value cause #1 (Another MCPTT client has permission);
+    - ii. may include in the Reject Cause field an additional text string explaining the reason for rejecting the floor request in the <Reject Phrase> value;
+    - iii. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+    - iv. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - b. shall remain in the 'U: not permitted and Floor Taken' state; and
+8. if the MCPTT client negotiated support of queueing of floor requests as specified in clause 14 and the effective priority level is not pre-emptive, the floor control interface towards the MCPTT client in the IWF floor control server:
+- a. shall insert the MCPTT client into the active floor request queue, if not inserted yet, or update the position of the MCPTT client in the active floor request queue, if already inserted, to the position immediately following all queued requests at the same effective priority level;
+
+- b. the IWF floor control server shall send a Floor Queue Position Info message to the floor participant. The Floor Queue Position Info message:
+  - i. shall include the queue position and floor priority in the Queue Info field;
+  - ii. if the Floor Request included a Track Info field, shall include the received Track Info field; and
+  - iii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+- c. shall remain in the 'U: not permitted and Floor Taken' state; and
+- d. may set the first bit in the subtype of the Floor Queue Position message to '1' (Acknowledgment is required) as described in clause 8.3.2.
+
+NOTE 4: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+#### 6.3.5.4.5 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message from the associated floor participant and if the MCPTT client did not negotiate support of queueing of floor requests or included a floor priority in the "mc\_priority" fmtp attribute as specified in clause 14, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '4' (Floor Release); and
+  - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+- 2. shall send a Floor Taken message to the associated floor participant. The Floor Taken message:
+  - a. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1;
+  - c. shall include the Permission to Request the floor field set to '0', if the floor participants are not allowed to request the floor;
+  - d. if the Floor Release message included a Track Info field, shall include the received Track Info field;
+  - e. may set the first bit in the subtype of the Floor Taken message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 1: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+- 3. shall remain in the 'U: not permitted and Floor Taken' state.
+
+Upon receiving a Floor Release message from the associated floor participant and if the MCPTT client negotiated support of queueing of floor requests as specified in clause 14, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '4' (Floor Release); and
+  - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+- 2. if
+
+- a. a Track Info field is included in the Floor Release message, shall use the topmost <Participant Reference> value and the SSRC in the received Floor Release message to check if the floor participant has a queued floor request; or
+    - b. if a Track Info field is not included in the Floor Release message, shall use the SSRC in the received Floor Release message to check if the floor participant has a queued floor request;
+  3. shall remove the MCPTT client from the active floor request queue, if the MCPTT client was in the active floor request queue;
+  4. shall send a Floor Taken message to the associated floor participant. The Floor Taken message:
+    - a. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+    - b. if the session is a broadcast group call, shall include the Permission to Request the floor field set to '0';
+    - c. if the session is not a broadcast group call, may include the Permission to Request the floor field set to '1';
+    - d. if a Track Info field is included in the Floor Release message, shall include the received Track Info field;
+    - e. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+    - f. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+  5. may set the first bit in the subtype of the Floor Taken message is set to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+- NOTE 2: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+6. shall remain in the 'U: not permitted and Floor Taken' state.
+
+#### 6.3.5.4.6 Receive RTP media packets (R: media)
+
+Upon receiving an indication from the network media interface in the MCPTT server that RTP media packets with payload are received from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+NOTE: Reception of unauthorized RTP media packets can only happen if the associated floor participant is in an MCPTT client. If the associated floor participant is a floor control server interface in a non-controlling MCPTT function of an MCPTT group, the unauthorized RTP media packets are handled in the non-controlling MCPTT function.
+
+1. shall request the network media interface to not forward the RTP media packets to the media distributor in the MCPTT server;
+2. shall send a Floor Revoke message to the associated floor participant. The Floor Revoke message:
+  - a. shall include the Reject Cause field with the Reject Cause value set to #3 (No permission to send a Media Burst); and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+3. shall enter the 'U: not permitted but sends media' state as specified in the clause 6.3.5.7.2.
+
+#### 6.3.5.4.7 Send Floor Queue Position Info message (R: Floor Queue Position Request)
+
+Upon receiving a Floor Queue Position Request message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send the Floor Queue Position Info message. The Floor Queue Position Info message:
+  - a. shall include the queue position and floor priority in the Queue Info field;
+
+- b. if a Track Info field is included in the Floor Queue Position Info message, shall include the received Track Info field;
+- c. may include the first bit in the subtype of the Floor Queue Position Info message set to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+
+- 3. shall remain in the 'U: not permitted and Floor Taken' state.
+
+#### 6.3.5.4.8 Receive an implicit floor request (R: Implicit floor request)
+
+When an ongoing session is upgraded to an emergency group call and when the application and signalling plane indicates that a subsequent SDP offer included the "mc\_implicit\_request" fmtp attribute as specified in clause 14, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. shall indicate to the floor control server arbitration logic that an implicit floor request is received due to an upgrade to an emergency group call; and
+- 2. shall remain in the 'U: not permitted and Floor Taken' state.
+
+#### 6.3.5.4.9 Send Floor Granted message (S: Floor Granted)
+
+When a Floor Granted message is received from the floor control arbitration logic in the IWF, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. shall forward the Floor Granted messages to the associated floor participant;
+- 2. may set the first bit in the subtype of the Floor Granted message to '1' (Acknowledgment is required) as described in clause 8.3.2;
+
+NOTE 1: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- 3. if the G-bit in the Floor Indicator is set to '1' (Dual floor) shall store an indication that the participant is overriding without revoke; and
+
+NOTE 2: The G-bit in the Floor Indicator is set to '1' as specified in clause 6.3.6.3.2.
+
+- 4. shall enter the state 'U: permitted' as specified in clause 6.3.5.5.2.
+
+#### 6.3.5.4.10 Send Floor Taken message (S: Floor Taken)
+
+When a Floor Taken message is received from the floor control arbitration logic in the IWF, if the G-bit in the Floor Indicator is set to '1' (Dual floor) the floor control interface towards the MCPTT client in the IWF floor control server:
+
+- 1. shall forward the Floor Taken message to the associated floor participant;
+- 2. may set the first bit in the subtype of the Floor Taken message to '1' (Acknowledgment is required) as described in clause 8.3.2;
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- 3. shall store an indication that the participant is listening to media from two sources; and
+- 4. shall remain in the 'U: not permitted and Floor Taken' state.
+
+#### 6.3.5.4.11 Send Floor Release Multi Talker message (S: Floor Release Multi Talker)
+
+Multi-talker is not supported in the present document.
+
+### 6.3.5.5 State: 'U: permitted'
+
+#### 6.3.5.5.1 General
+
+The floor control interface towards the MCPTT client in the IWF floor control server uses this state when the associated floor participant has been given permission to send media.
+
+#### 6.3.5.5.2 Enter state 'U: permitted'
+
+When entering this state, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall set the state for the associated floor participant to 'U: permitted'.
+
+#### 6.3.5.5.3 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '4' (Floor Release); and
+  - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+2. if an indication that the participant is overriding without revoke is stored,
+  - a. shall forward the Floor Release message to the 'dual floor control operation' state machine of the floor control arbitration logic in the IWF with the first bit in the subtype of the Floor Release message set to '0' (Acknowledgment is not required), if not already set;
+  - b. shall remove the indication that the participant is overriding without revoke; and
+  - c. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2;
+3. if an indication that the participant is overridden without revoke is stored,
+  - a. shall forward the Floor Release message to the general floor control operation state machine of the floor control arbitration logic in the IWF with the first bit in the subtype of the Floor Release message set to '0' (Acknowledgment is not required), if not already set;
+  - b. shall remove the indication that the participant is overridden without revoke; and
+  - c. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2; and
+4. if no indication is stored:
+  - a. shall forward the Floor Release message to the general floor control operation state machine of the floor control arbitration logic in the IWF with the first bit in the subtype of the Floor Release message set to '0' (Acknowledgment is not required), if not already set; and
+  - b. shall remain in the 'U: permitted' state.
+
+#### 6.3.5.5.4 Send Floor Idle message (S: Floor Idle)
+
+Upon receiving the Floor Idle message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the G-bit in the Floor Indicator is set to '1' (Dual Floor) and an indication that the participant is overridden without revoke is stored
+  - a. shall send Floor Idle message to the associated floor participant;
+  - b. shall remove the indication that a participant is overridden without revoke; and
+  - c. shall remain in 'U: permitted state';
+
+2. if no indication is stored shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2; and
+3. if an indication that the participant is overriding without revoke is stored
+  - a. shall send Floor Idle message to the associated floor participant;
+  - b. shall remove the indication that a participant is overriding without revoke; and
+  - c. shall remain in 'U: permitted state'.
+
+#### 6.3.5.5.5 Send Floor Revoke message (S: Floor Revoke)
+
+When receiving the Floor Revoke message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Revoke message to the floor participant;
+2. if the Floor Revoke message includes the Track Info field, shall store the Track Info field; and
+3. shall enter the state 'U pending Floor Revoke' as specified in the clause 6.3.5.6.2.
+
+#### 6.3.5.5.6 Receive RTP media packets (R: media)
+
+Upon receiving an indication from the network media interface in the MCPTT server that RTP media packets with payload are received from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if an indication that the participant is overriding without revoke is not stored,
+  - a. shall request the network media interface in the MCPTT server to forward RTP media packets to the media distributor in the MCPTT server.
+
+#### 6.3.5.5.7 Receive Floor Request message (R: Floor Request)
+
+Upon receiving a Floor Request message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the Floor Request message to the floor control server arbitration logic in the MCPTT server; and
+  - b. shall instruct the media distributor to act as in clause 6.3.4.4.5.
+2. if an indication that the participant is overriding without revoke is stored,
+  - a. shall request the network media interface in the MCPTT server to forward RTP media packets to the media distributor in the MCPTT server; and
+  - b. shall instruct the media distributor to act as in clause 6.3.6.3.5; and
+3. shall remain in the 'U: permitted' state.
+
+#### 6.3.5.5.8 Send RTP Media (S: media)
+
+When RTP packets are received from the media distributor, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward the RTP packet to the associated floor participant if the indication that the participant is overridden without revoke is stored;
+2. shall forward the RTP packet to the associated floor participant if the indication that the participant is overriding without revoke is stored; and
+3. shall remain in the 'U: permitted' state.
+
+#### 6.3.5.5.9 Send Floor Taken message (S: Floor Taken)
+
+When receiving the Floor Taken message from the floor control server arbitration logic in the MCPTT server with the G-bit in the Floor Indicator set to '1' (Dual Floor), the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send the Floor Taken message to the associated floor participant;
+2. shall store an indication that the participant is overridden without revoke; and
+3. shall remain in the 'U: permitted' state.
+
+When receiving the Floor Taken message from the floor control server arbitration logic in the MCPTT server with the G-bit in the Floor Indicator set to '0' (Not dual floor), the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send the Floor Taken message to the associated floor participant; and
+2. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2.
+
+#### 6.3.5.5.10 Send Floor Release Multi Talker message (S: Floor Release Multi Talker)
+
+Multi-talker is not supported in the present document.
+
+#### 6.3.5.6 State: 'U: pending Floor Revoke'
+
+##### 6.3.5.6.1 General
+
+The floor control interface towards the MCPTT client in the floor control server uses this state during the grace period after sending the Floor Revoke message.
+
+In this state timer T8 (Floor Revoke) is running.
+
+##### 6.3.5.6.2 Enter state 'U pending Floor Revoke'
+
+When entering this state, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall start timer T8 (Floor Revoke); and
+2. shall enter the state 'U: pending Floor Revoke'.
+
+##### 6.3.5.6.3 Timer T8 (media Revoke) expired
+
+On expiry of timer T8 (Floor Revoke) the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall retransmit the Floor Revoke message to the associated floor participant. The Floor Revoke message:
+  - a. shall include the same Rejection Cause field and the same Floor Indicator field as in the previous sent Floor Revoke message;
+2. shall start timer T8 (Floor Revoke); and
+3. shall remain in the 'U: pending Floor Revoke' state.
+
+NOTE: The number of times the IWF floor control server retransmits the Floor Revoke message and the action to take when the IWF floor control server gives up is an implementation option. However, it is recommended that the MCPTT client is disconnected from the MCPTT call when the IWF floor control server gives up.
+
+##### 6.3.5.6.4 Receive RTP media packets (R: media)
+
+Upon receiving an RTP media packet with payload from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall forward RTP media packets to the media distributor; and
+
+2. shall remain in the 'U: pending Floor Revoke' state.
+
+#### 6.3.5.6.5 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message from the associated floor participant, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '4' (Floor Release); and
+  - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+2. if the G-bit in the Floor Indicator is set to '1' (Dual floor):
+  - a. if the state in the 'general floor control operation' state machine is 'G: Taken':
+    - i. shall send a Floor Taken message to the associated floor participant. The Floor Taken message:
+      - A. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field of the permitted MCPTT client if privacy is not requested; and
+      - B. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - ii. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2; and
+  - b. if the state in the 'general floor control operation' state machine is 'G: Idle':
+    - i. shall send a Floor Idle message to the associated floor participant;
+    - ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - iii. shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2; and
+3. if the G-bit in the Floor Indicator is set to '0':
+  - a. shall forward the Floor Release message to the floor control server arbitration logic; and
+  - b. shall remain in the state 'U: pending Floor Revoke'.
+
+#### 6.3.5.6.6 Send Floor Idle message (S: Floor Idle)
+
+Upon receiving a Floor Idle message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+NOTE 1: The Floor Idle message is sent when timer T3 (Stop talking grace) expires and when timer T1 (End of RTP media) expires and when there are no queued floor requests.
+
+1. shall send the Floor Idle message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Idle message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 2: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2.
+
+#### 6.3.5.6.7 Send Floor Taken message (S: Floor Taken)
+
+Upon receiving a Floor Taken message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+NOTE 1: The Floor Taken message is sent when timer T3 (Stop talking grace) expires or when timer T1 (End of RTP media) expires and if there are queued floor requests.
+
+1. shall send the Floor Taken message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Taken message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE 2: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.3.2.
+
+#### 6.3.5.6.8 Send Floor Release Multi Talker message (S: Floor Release Multi Talker)
+
+Multi-talker is not supported in the present document.
+
+#### 6.3.5.7 State 'U: not permitted but sends media'
+
+##### 6.3.5.7.1 General
+
+The floor control interface towards the MCPTT client in the floor control server uses this state when it receives RTP media packets from the MCPTT client and the MCPTT client is not permitted to send media.
+
+Timer T8 (Floor Revoke) is running in this state.
+
+##### 6.3.5.7.2 Enter state 'U: not permitted but sends media'
+
+When entering this state, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall start timer T8 (Floor Revoke); and
+2. shall enter the state 'U: not permitted but sends media'.
+
+In this state the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall not request the network media interface in the MCPTT server to forward RTP media packets from the MCPTT client to the media distributor in the MCPTT server.
+
+##### 6.3.5.7.3 Timer T8 (Floor Revoke) expired
+
+On expiry of timer T8 (Floor Revoke), the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall send a Floor Revoke message to the associated floor participant. The Floor Revoke message:
+  - a. shall include in the Rejection Cause field the <Rejection Cause> value set to #3 (No permission to send a Media Burst); and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+2. shall restart timer T8 (Floor Revoke); and
+3. shall remain in the 'U: not permitted but sends media' state.
+
+NOTE: The number of times the IWF floor control server retransmits the Floor Revoke message and the action to take when the IWF floor control server gives up is an implementation option. However, the recommended action is that the MCPTT client is disconnected from the MCPTT call.
+
+##### 6.3.5.7.4 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+
+- a. shall include the Message Type field set to '4' (Floor Release); and
+    - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+  2. if the general state is 'G: Floor Idle', the floor control interface towards the MCPTT client in the IWF floor control server:
+    - a. shall send the Floor Idle message. The Floor Idle message:
+      - i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+      - ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - b. shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2; and
+  3. if the general state is 'G: Floor Taken', the floor control interface towards the MCPTT client in the IWF floor control server:
+    - a. shall send a Floor Taken message. The Floor Taken message:
+      - i. shall include the granted MCPTT user's MCPTT ID in the Granted Party's Identity field if privacy is not requested;
+      - ii. if the session is a broadcast group call, shall include the Permission to Request the floor field set to '0';
+      - iii. if the session is not a broadcast group call, may include the Permission to Request the floor field set to '1';
+      - iv. may include the first bit in the subtype of the Floor Taken message set to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+- NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+- v. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+    - c. shall enter the 'U: not permitted and Floor Taken' state as specified in the clause 6.3.5.4.2.
+
+#### 6.3.5.7.5 Send Floor Taken message (S: Floor Taken)
+
+Receiving the Floor Taken message from the floor control server arbitration logic in the MCPTT server with the I-bit in the Floor Indicator set to '1' (multi-talker) is not supported in the present document.
+
+#### 6.3.5.7.6 Send Floor Release Multi Talker message (S: Floor Release Multi Talker)
+
+Multi-talker is not supported in the present document.
+
+#### 6.3.5.8 In any state
+
+##### 6.3.5.8.1 General
+
+This clause describes the actions to be taken in all states defined for the basic state diagram with the exception of the 'Start-stop' and 'Releasing' states.
+
+##### 6.3.5.8.2 Receive MCPTT call release – 1
+
+Upon receiving an MCPTT call release step 1 request from the application and signalling plane e.g. when the MCPTT call is going to be released or when the MCPTT client leaves the MCPTT call, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall stop sending floor control messages to the associated floor participant;
+2. shall request the network media interface to stop sending RTP media packets towards to the associated MCPTT client;
+
+3. shall ignore any floor control messages received from the associated floor participant;
+4. shall request the network media interface to stop forwarding RTP media packets from the associated MCPTT client to the media distributor in the MCPTT server;
+5. shall indicate to the floor control server arbitration logic in the MCPTT server that the MCPTT client has started to disconnect from the MCPTT call; and
+6. shall enter the 'Releasing' state.
+
+#### 6.3.5.8.3 Receiving a merging instruction (R: Merge)
+
+Upon receipt of an instruction to merge with another group due to the group regrouping function, the floor control interface towards the MCPTT client:
+
+1. shall create an instance of the 'floor participant interface state transition' as specified in clause 6.5.5;
+2. shall move information associated with the instance used for 'floor participant interface state transition' to the 'basic floor control operation towards the floor participant' state machine;
+
+NOTE: Which information that needs to be moved is an implementation option.
+
+3. shall enter the 'Start-stop' state and terminate the 'basic floor control operation towards the floor participant' state machine associated with this floor participant and this MCPTT call;
+4. if the state was 'U: not permitted and Floor Idle', 'U: not permitted Floor Taken', 'U: pending Floor Revoke', 'U: not permitted and initiating' or 'U: not permitted but sends media':
+  - a. shall enter the 'P: has no permission' state as specified in clause 6.5.5; and
+  - b. shall perform actions specified in clause 6.5.5.3; and
+5. if the state was 'U: permitted':
+  - a. shall enter the 'P: has permission' state; and
+  - b. shall perform actions specified in clause 6.5.5.4.
+
+#### 6.3.5.9 State: 'Releasing'
+
+##### 6.3.5.9.1 General
+
+The floor control interface towards the MCPTT client in the IWF floor control server uses this state while waiting for the application and signalling plane to finalize the release of the MCPTT call or finalizing the removal of the MCPTT client from the MCPTT call.
+
+##### 6.3.5.9.2 Receive MCPTT call release - 2
+
+Upon receiving an MCPTT call release step 2 request from the application and signalling plane, the floor control interface towards the MCPTT client in the IWF floor control server:
+
+1. shall request the network media interface to release all resources associated with this MCPTT client for this MCPTT call; and
+2. shall enter the 'Start-stop' state and terminate the 'basic floor control operation towards the floor participant' state machine associated with this floor participant and this MCPTT call.
+
+#### 6.3.5.10 State: 'U: not permitted and initiating'
+
+##### 6.3.5.10.1 General
+
+The floor control interface towards the MCPTT client uses this state when waiting for the floor control arbitration logic to finalize the initialisation of the state machine to be used for a temporary group session.
+
+During this state Floor Request messages can be received from the non-controlling MCPTT function. Any Floor Request message received will be added to the queue according to the priority of the floor request determine as described in clause 4.1.1.4.
+
+#### 6.3.5.10.2 Enter the 'U: not permitted and initiating' state
+
+The floor control interface towards the MCPTT client:
+
+1. shall set the state for the associated floor participant to 'U: not permitted and Initiating'.
+
+#### 6.3.5.10.3 Send Floor Taken message (S: Floor Taken)
+
+When a Floor Taken message is received from the floor control arbitration logic in the IWF, the floor control interface towards the MCPTT client:
+
+1. shall forward the Floor Taken messages to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Taken message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the state 'U: not permitted and Floor Taken' as specified in clause 6.3.5.4.2.
+
+#### 6.3.5.10.4 Send Floor Idle message (S: Floor Idle)
+
+When receiving a Floor Idle message from the floor control server arbitration logic in the MCPTT server, the floor control interface towards the MCPTT client:
+
+1. shall forward the Floor Idle message to the associated floor participant;
+2. may set the first bit in the subtype of the Floor Idle message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. shall enter the 'U: not permitted and Floor Idle' state as specified in the clause 6.3.5.3.2.
+
+#### 6.3.5.10.5 Receive Floor Request message (R: Floor Request)
+
+Upon receipt of a Floor Request message, the floor control interface towards the MCPTT client:
+
+1. shall determine the effective priority level as described in clause 4.1.1.4;
+2. shall put the Floor Request message in the floor request queue according to the determined effective priority level;
+3. if the <Queueing Capability> value in the Track Info field is set to '1' (the floor participant in the MCPTT client supports queueing), shall send a Floor Queue Position Info message to the requesting non-Controlling MCPTT function, The Floor Queue Position Info message:
+  - a. shall include the queue position and floor priority in the Queue Info field;
+  - b. shall include the received Track Info field; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+4. if the <Queueing Capability> value in the Track Info field is set to '0' (the floor participant in the MCPTT client does not support queueing), shall send the Floor Deny message. The floor Deny message:
+
+NOTE: A Floor Request from a MCPTT client in a constituent group can be received without the queueing capability if a floor participant in an ongoing constituent MCPTT group request floor while the floor was idle during the merging process.
+
+- a. shall include in the Reject Cause field the <Reject Cause> value cause '1' (Another MCPTT client has permission);
+  - b. shall include the received Track Info field; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+5. shall remain in the 'U: not permitted and initiating' state.
+
+#### 6.3.5.10.6 Send Floor Granted message (S: Floor Granted)
+
+When a Floor Granted message is received from the floor control arbitration logic, the floor control interface towards the MCPTT client:
+
+- 1. shall forward the Floor Granted messages to the associated floor participant;
+- 2. may set the first bit in the subtype of the Floor Granted message to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+- 3. shall enter the state 'U: permitted' as specified in clause 6.3.5.5.2.
+
+#### 6.3.5.10.7 Receive a Floor Release message (S: Floor Release)
+
+Upon receiving a Floor Release message from the associated floor participant, the floor control interface towards the MCPTT client:
+
+- 1. if the first bit in the subtype of the Floor Release message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '4' (Floor Release); and
+  - b. shall include the Source field set to '2' (the controlling MCPTT function is the source);
+- 2. shall use the topmost <Participant Reference> value and the SSRC in the Track Info field of the received Floor Release message to check if the floor participant has a queued floor request and if not, check if there is a floor request in one of the cached application/vnd.3gpp.mcptt-floor-request+xml MIME bodies;
+- 3. shall remove the MCPTT client from the active floor request queue or the cached application/vnd.3gpp.mcptt-floor-request+xml MIME body, if the MCPTT client was in the active floor request queue or in the application/vnd.3gpp.mcptt-floor-request+xml MIME body; and
+- 4. shall remain in the 'U: not permitted and initiating' state.
+
+#### 6.3.5.10.8 Send Floor Release Multi Talker message (S: Floor Release Multi Talker)
+
+Multi-talker is not supported in the present document.
+
+### 6.3.6 Dual floor control
+
+#### 6.3.6.1 General
+
+**Editor's Note:** The procedures of the IWF performing the non-controlling role are FFS.
+
+Dual floor control is used when a floor participant requests floor with a pre-emptive floor priority allowing the floor control in clause 6.3.4 to continue without revoking the floor from the floor participant permitted to send media as specified in 3GPP TS 23.379 [5] clause 10.9.1.3.2.2.
+
+The floor control server arbitration logic in the IWF floor control server shall behave according to the state diagram and state transitions specified in this clause.
+
+Figure 6.3.6.1-1 shows the 'dual floor control operation' states (D states) and the state transition diagram.
+
+![Floor control server state transition diagram for 'dual floor control operation' showing states: Releasing, Start-stop, Any state, and D: Floor Taken with their respective transitions.](7ed5d5770331f31ade15439a21c31425_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Start-stop
+    Start-stop --> Releasing : R: MCPTT call release - 2
+    Releasing --> Start-stop
+    Releasing --> Any state : R: MCPTT call release - 1
+    Start-stop --> D: Floor Taken : R: Floor Request OR I: Floor grant to IWF floor participant
+    D: Floor Taken --> Start-stop : T11 (End of RTP dual) expired OR T12 (Stop talking dual) expired OR R: Floor Release OR R: Termination instruction from the floor control arbitration logic OR I: Floor release by IWF floor participant OR I: Call release by IWF floor participant
+    D: Floor Taken --> Releasing : R: RTP media OR R: Floor Request
+  
+```
+
+The diagram illustrates the state transitions for a 'dual floor control operation' state machine. It consists of four states: 'Start-stop' (initial state), 'Releasing', 'Any state', and 'D: Floor Taken'. Transitions are triggered by specific events or receive (R) and IWF determined (I) messages. A legend box defines 'R' as 'Receive' and 'I' as 'IWF determined event'.
+
+Floor control server state transition diagram for 'dual floor control operation' showing states: Releasing, Start-stop, Any state, and D: Floor Taken with their respective transitions.
+
+Figure 6.3.6.1-1: Floor control server state transition diagram for 'dual floor control operation'
+
+The floor control arbitration logic in the IWF floor control server shall keep one instance of the 'dual floor control operation' state machine for a floor participant with pre-emptive floor priority where this MCPTT user or user homed in the IWF is allowed to talk without revoking a current speaker with lower floor priority.
+
+NOTE: Only one media endpoint with this type of pre-emptive floor priority can exist within an MCPTT call.
+
+The floor participant associated to the 'dual floor control operation' state machine is in the following clauses referred to as the overriding media endpoint.
+
+If floor control messages or RTP media packets arrive in a state where there is no procedure specified in the following clauses the floor control arbitration logic in the IWF floor control server:
+
+1. shall discard the floor control message;
+2. shall request the media distributor in the IWF to discard any received RTP media packet; and
+3. shall remain in the current state.
+
+State details are explained in the following clauses.
+
+### 6.3.6.2 State: 'Start-stop'
+
+#### 6.3.6.2.1 General
+
+When a new instance of the 'dual floor control operation' state machine is initiated, before any floor control related input is applied, the state machine is in 'Start-stop' state. Similarly, when the media burst is released the state machine shall return to the 'Start-Stop' state or the related MCPTT call is released.
+
+#### 6.3.6.2.2 Receive Floor Request message with overriding pre-emptive floor priority (R: Floor Request)
+
+When an MCPTT floor participant that requests the floor with an overriding pre-emptive priority is granted the floor the floor control arbitration logic in the IWF floor control server:
+
+1. shall create one instance of the 'dual floor control operation' state machine;
+2. shall store the SSRC of the floor participant;
+3. if a Track Info field is included in the Floor Request message, shall store the received Track Info field associated with the floor control server state transition diagram for 'dual floor control operation', and
+- 4 shall enter the state 'D: Floor Taken' as specified in the clause 6.3.6.3.2.
+
+#### 6.3.6.2.2A Floor Grant to IWF floor participant with overriding pre-emptive floor priority (I: Floor Grant to IWF floor participant)
+
+When the IWF determines that an IWF floor participant with an overriding pre-emptive priority is to be granted the floor the floor control arbitration logic in the IWF floor control server:
+
+1. shall create one instance of the 'dual floor control operation' state machine;
+2. shall determine an SSRC for the IWF floor participant and shall store the SSRC of the IWF floor participant; and
+- 3 shall enter the state 'D: Floor Taken' as specified in the clause 6.3.6.3.2.
+
+### 6.3.6.3 State: 'D: Floor Taken'
+
+#### 6.3.6.3.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state when it has permitted one floor participant to override a current speaker in an MCPTT call to send media.
+
+Timer T11 (End of RTP dual) can be running when the IWF floor control server is in this state.
+
+Timer T12 (Stop talking dual) can be running when the IWF floor control server is in this state.
+
+#### 6.3.6.3.2 Enter state 'D: Floor Taken'
+
+When entering this state, the floor control arbitration logic in the IWF floor control server:
+
+1. if the requesting floor participant is an MCPTT floor participant, shall send a Floor Granted message to the requesting MCPTT floor participant. The Floor Granted message:
+  - a. shall include the value of the T12 (Stop talking dual) timer in the Duration field;
+  - b. shall include the granted priority in the Floor priority field;
+  - c. if a Track Info field associated with the floor control server state transition diagram for 'dual floor control operation' state machine is stored, shall include the stored Track Info field;
+  - d. shall include the Floor Indicator field with the G-bit set to '1' (Dual floor);
+  - e. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+  - f. if non-controlling MCPTT functions are involved, shall include the SSRC of the granted floor participant;
+2. shall send a Floor Idle message to any non-controlling MCPTT functions involved in the session and to those MCPTT floor participants controlled by the IWF performing the controlling role that will only listen to RTP media from the overriding media endpoint according to local policy. The Floor Idle message:
+
+NOTE 1: The non-controlling MCPTT function will send the Floor Idle message to those MCPTT floor participants controlled by the non-controlling MCPTT function that will only listen to RTP media from the overriding media endpoint according to local policy when the non-controlling MCPTT function receives the Floor Taken with the G-bit set to '1' (Dual floor) in the Floor Indicator field.
+
+- i. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+  - ii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+3. shall send a Floor Taken message to any non-controlling MCPTT functions involved and to MCPTT floor participants controlled by the IWF performing the controlling role that will listen to the RTP media from the overriding media endpoint according to local policy. The Floor Taken message:
+
+NOTE 2: The media endpoint overridden by the overriding media endpoint is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
+
+- a. shall include the granted floor participant's MCPTT ID in the Granted Party's Identity field, if privacy is not requested;
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1;
+  - c. shall include the Floor Indicator field with the G-bit set to '1' (Dual floor); and
+  - d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+4. shall start the T11 (End of RTP dual) timer; and
+  5. shall enter the state 'D: Floor Taken'.
+
+### 6.3.6.3.3 Timer T11 (End of RTP dual) expired
+
+On expiry of timer T11 (End of RTP dual), the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop the T12 (Stop talking dual) timer; if running;
+2. shall request the media distributor in the IWF to stop distributing RTP media packets received from the overriding media endpoint to other media endpoints;
+
+NOTE: If dual floor control is ongoing as described in clause 6.3.6, the list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
+
+3. shall release all resources reserved in the media plane including the instances used for the 'dual floor control operation' state machine and any running timers associated with the state machine;
+4. shall send a Floor Idle message to any non-controlling MCPTT functions and to those MCPTT floor participants controlled by the IWF performing the controlling role receiving RTP media from the overriding media endpoint. The Floor Idle message:
+  - a. shall include a Floor Indicator field with the G-bit set to '1' (Dual floor);
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+5. if the state in the 'general floor control operation' state machine is 'G: Taken';
+  - a. shall send a Floor Taken message to any non-controlling MCPTT functions and to those MCPTT floor participants controlled by the IWF performing the controlling role that only received RTP media from the overriding media endpoint. The Floor Taken message:
+
+- i. shall include the granted floor participant's MCPTT ID in the Granted Party's Identity field, if privacy is not requested;
+  - ii. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - iii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+6. if the state in the 'general floor control operation' state machine is 'G: Idle', shall send a Floor Idle message to all MCPTT floor participants. The Floor Idle message:
+  - a. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+7. shall enter the 'Start-stop' state.
+
+#### 6.3.6.3.4 Timer T12 (Stop talking dual) expired
+
+On expiry of the T12 (Stop talking dual) timer the floor control arbitration logic in the IWF floor control server:
+
+1. shall stop the T11 (End of RTP dual) timer;
+2. shall request the media distributor in the IWF to stop distributing RTP media packets to other media endpoints;
+3. if the floor participant is an MCPTT floor participant, shall send the Floor Revoke message to the permitted MCPTT floor participant. The Floor Revoke message:
+  - a. shall include the Reject Cause field with the <Reject Cause> value set to #2 (Media burst too long) in the Floor Revoke message sent in clause 6.3.4.5.2;
+  - b. shall include the Floor Indicator with the G-bit set to '1' (Dual floor);
+  - c. if a Track Info field associated with the dual floor is stored, shall include the stored Track Info field; and
+  - d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+4. shall remove the stored Track info field associated with the dual floor;
+5. if the state in the 'general floor control operation' state machine is 'G: Taken';
+  - a. shall send a Floor Taken message to all non-controlling MCPTT functions (if the session is a temporary group session involving non-controlling MCPTT functions) and to those MCPTT floor participants that only received RTP media from the overriding media endpoint. The Floor Taken message:
+    - i. shall include the granted floor participant's MCPTT ID in the Granted Party's Identity field, if privacy is not requested; and
+    - ii. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1;
+6. if the state in the 'general floor control operation' state machine is 'G: Idle', shall send a Floor Idle message to all MCPTT floor participants. The Floor Idle message:
+  - a. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+7. shall release all resources reserved in the media plane including the instances used for the Floor control server state transition diagram for 'dual floor control operation'; and
+
+8. shall enter the 'Start-stop' state.
+
+#### 6.3.6.3.5 Receive RTP media packets (R: media)
+
+Upon receiving an indication from the media distributor in the IWF that RTP media packets are received from the permitted media endpoint, the floor control arbitration logic in the IWF floor control server:
+
+1. if the media endpoint is an MCPTT media endpoint, shall start the T12 (Stop talking dual) timer, if not already running;
+2. shall restart the T11 (End of RTP dual) timer;
+3. shall instruct the media distributor to forward the received RTP media packets to any non-controlling MCPTT functions, to the overridden media endpoint and to those media endpoints receiving RTP media from the overriding media endpoint controlled by the IWF performing the controlling role according to local policy; and
+
+NOTE 1: The RTP media is sent to the media endpoints subjected to the maximum number of simultaneous transmissions received in one group call for override (N7) as indicated in 3GPP TS 23.379 [5].
+
+NOTE 2: The IWF performing the non-controlling role will forward the RTP media packets to media endpoints receiving RTP media from the overriding media endpoint according to local policy in the IWF performing the non-controlling role.
+
+4. shall remain in the 'D: Floor Taken' state.
+
+#### 6.3.6.3.6 Receive Floor Release message (R: Floor Release)
+
+Upon receiving a Floor Release message from the overriding MCPTT media endpoint or upon determining that the floor has been released by an overriding IWF media endpoint, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor in the IWF to stop distributing RTP media packets received from the overriding media endpoint to other media endpoints;
+2. shall stop the T12 (Stop talking dual) timer, if running;
+3. shall stop the T11 (End of RTP dual) timer;
+4. shall release all resources reserved in the media plane including the instances used for the Floor control server state transition diagram for 'dual floor control operation' and any running timers associated with the state machine;
+5. if a Floor Release message has been received from an MCPTT media endpoint and if the first bit in the subtype of the Floor Release message is set to '1' (acknowledgement is required) as specified in clause 8.2.2:
+  - a. shall send a Floor Ack message. The Floor Ack message:
+    - i. shall set the Source field to the value '2' (the IWF performing the controlling role is the source); and
+    - ii. shall set the Message Type field to the value '4' (Floor Release);
+6. shall send a Floor Idle message to any non-controlling MCPTT functions, to the overridden participant if it is an MCPTT floor participant and to those MCPTT floor participants controlled by the IWF performing the controlling role receiving RTP media from the overriding media endpoint. The Floor Idle message:
+  - a. shall include an Floor Indicator field with the G-bit set to '1' (Dual floor);
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+7. if the state in the 'general floor control operation' state machine is 'G: Taken',
+  - a. shall send a Floor Taken message to any non-controlling MCPTT functions and to those MCPTT floor participants that only received RTP media from the overriding media endpoint. The Floor Taken message:
+
+- i. shall include the granted floor participant's MCPTT ID in the Granted Party's Identity field, if privacy is not requested;
+  - ii. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+  - iii. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+8. if the state in the 'general floor control operation' state machine is 'G: Idle', shall send a Floor Idle message to all MCPTT floor participants. The Floor Idle message:
+  - a. shall include a Message Sequence Number field with a Message Sequence Number value increased with 1; and
+  - b. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+9. shall enter the 'Start-stop' state.
+
+#### 6.3.6.3.6A IWF Floor Release (I: Floor release by IWF floor participant)
+
+The procedures in clause 6.3.6.3.6 are followed.
+
+#### 6.3.6.3.7 Receive Floor request message from permitted MCPTT floor participant (R: Floor Request)
+
+Upon receiving a Floor Request message from the MCPTT floor participant that has been granted permission to send overriding media, the floor control arbitration logic in the IWF floor control server:
+
+1. shall send a Floor Granted message to the previously granted MCPTT floor participant. The Floor Granted message:
+  - a. shall include the value of the T12 (Stop talking dual) timer in the Duration field;
+  - b. shall include the granted priority in the Floor priority field;
+  - c. if the Floor Request message included a Track Info field, shall include the received Track Info field; and
+  - d. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications; and
+2. shall remain in the 'D: Floor Taken' state.
+
+#### 6.3.6.3.8 Permitted MCPTT participant release
+
+If the IWF floor control server receives an indication from the floor control interface towards the MCPTT client that the overriding MCPTT media endpoint has started to disconnect from the MCPTT call, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor in the IWF to stop distributing RTP media packets received from the overriding MCPTT media endpoint to other media endpoints;
+2. shall send a Floor Idle message to any non-controlling MCPTT functions and to those MCPTT floor participants controlled by the IWF performing the controlling role receiving RTP media from the overriding MCPTT media endpoint. The Floor Idle message:
+  - a. shall include an Floor Indicator field with the G-bit set to '1' (Dual floor);
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+
+3. shall release all resources reserved in the media plane including the instances used for the Floor control server state transition diagram for 'dual floor control operation' and any running timers associated with the state machine; and
+4. shall enter the 'Start-stop' state.
+
+#### 6.3.6.3.8A Permitted IWF participant release (I: Call release by IWF floor participant)
+
+If the IWF floor control server determines that the overriding IWF media endpoint has started to disconnect from the MCPTT call, the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor in the IWF to stop distributing RTP media packets received from the overriding IWF media endpoint to other media endpoints;
+2. shall send a Floor Idle message to any non-controlling MCPTT functions and to those MCPTT floor participants controlled by the IWF performing the controlling role receiving RTP media from the overriding IWF media endpoint. The Floor Idle message:
+  - a. shall include an Floor Indicator field with the G-bit set to '1' (Dual floor);
+  - b. shall include a Message Sequence Number field with a <Message Sequence Number> value increased with 1; and
+  - c. if a group call is a broadcast group call, a system call, an emergency call, an imminent peril call, or a temporary group session, shall include the Floor Indicator field with appropriate indications;
+3. shall release all resources reserved in the media plane including the instances used for the Floor control server state transition diagram for 'dual floor control operation' and any running timers associated with the state machine; and
+4. shall enter the 'Start-stop' state.
+
+#### 6.3.6.3.9 Receive Terminate (Terminate)
+
+Upon receiving the termination instruction, the floor control arbitration logic in the IWF floor control server:
+
+1. shall set the value of timer T1 (End of RTP media) to the value of timer T11 (End of RTP dual) and start timer T1, if timer T11 (End of RTP dual) is running;
+2. shall set the value of timer T2 (Stop talking) to the value of timer T12 (Stop talking dual) and start timer T2, if timer T12 (Stop talking dual) is running;
+3. shall release all resources reserved in the media plane including the instances used for the dual floor control operation' state machine and stop any running timers associated with the state machine; and
+4. shall enter the 'Start-stop' state.
+
+NOTE: The overriding participant continues to have the floor until its current talk burst is terminated.
+
+#### 6.3.6.4 In any state
+
+##### 6.3.6.4.1 General
+
+This clause describes the actions to be taken in all states defined for the general state diagram with the exception of the 'Start-stop' state.
+
+##### 6.3.6.4.2 Receive MCPTT call release - 1
+
+This clause is used by the floor control arbitration logic in the IWF floor control server when an MCPTT call is released.
+
+Upon receiving an MCPTT call release step 1 request from the application and signalling plane the floor control arbitration logic in the IWF floor control server:
+
+1. shall request the media distributor in the IWF to stop sending RTP media packets to media endpoints; and
+
+2. shall enter the 'Releasing' state.
+
+### 6.3.6.5 State: 'Releasing'
+
+#### 6.3.6.5.1 General
+
+The floor control arbitration logic in the IWF floor control server uses this state while waiting for the application and signalling plane to finalize the disconnection of an MCPTT call.
+
+#### 6.3.6.5.2 Receive MCPTT call release - 2
+
+Upon receiving an MCPTT call release step 2 request from the application and signalling plane, the floor control arbitration logic in the IWF floor control server:
+
+1. shall release all resources reserved in the media plane including the instances used for the dual floor control operation' state machine and any running timers associated with the state machine; and
+2. shall enter the 'Start-stop' state.
+
+## 6.4 IWF performing the participating role floor control procedures
+
+### 6.4.1 General
+
+The IWF performing the participating role performs the procedures in this clause on behalf of each IWF media endpoint.
+
+### 6.4.2 IWF floor participant procedures at MCPTT session initialization
+
+#### 6.4.2.1 General
+
+Based on the negotiations during the call establishment specified in 3GPP TS 29.379 [26], a new instance of a media session shall be created for this call.
+
+The SIP INVITE request sent by the application and signalling plane:
+
+1. shall be regarded an implicit floor request when an implicit floor request is negotiated; and
+2. shall not be regarded as an implicit floor request in case of a rejoin to an already on-going group call.
+
+NOTE: The IWF floor participant can negotiate the use of prioritization of the Floor Request message. In that case, the floor participant can request permission to send media at a priority level that is either the same as or lower than the highest priority that was permitted to the participant in the MCPTT call initialization. If a floor participant is authorized for pre-emptive priority in the MCPTT call it is good practise to always request permission to send RTP media packets at a priority level that is lower than pre-emptive priority unless the IWF explicitly needs to pre-empt the current RTP media packets' sender. In any case pre-emptive priority will have no effect for audio cut-in floor control.
+
+#### 6.4.2.2 MCPTT call initiated, IWF originating
+
+When a call is initiated as described in 3GPP TS 29.379 [26], the IWF floor participant:
+
+1. shall create a media session;
+2. if the originating IWF floor participant receives a floor control message before it receives the SIP 200 (OK) response, shall store the floor control message; and
+
+NOTE: The originating IWF floor participant might receive a floor control message before the SIP 200 (OK) response when initiating, joining or rejoining a call because of processing delays of the SIP 200 (OK) response in the SIP core.
+
+3. if a floor control message is received after a SIP INVITE request with implicit floor request and before the reception of the SIP 200 (OK), shall act upon the floor control message.
+
+### 6.4.2.3 MCPTT call established, IWF terminating
+
+When an MCPTT call is established, the terminating IWF floor participant shall create an instance of a media session.
+
+NOTE: From an IWF floor participant perspective the MCPTT call is established when the application and signalling plane sends the SIP 200 (OK) response.
+
+## 6.4.3 IWF floor participant procedures at MCPTT call release
+
+The MCPTT call release can be initiated by the IWF floor participant or the MCPTT floor control server. The following steps are performed:
+
+1. The IWF floor participant stops sending floor control messages and stops sending RTP media packets.
+2. When the application and signalling plane has determined that the MCPTT call is released, the corresponding instance of the media session is terminated.
+
+The user plane can initiate release step 1, but the application and signalling plane always initiates release step 2.
+
+NOTE: A badly formatted RTP packet or floor control message received is ignored by the IWF floor participant.
+
+## 6.4.4 IWF floor participant floor message handling
+
+### 6.4.4.1 Receive Floor Idle message
+
+Upon receiving a Floor Idle message, the IWF floor participant:
+
+1. if the first bit in the subtype of the Floor Idle message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '5' (Floor Idle); and
+  - b. shall include the Source field set to '0' (the IWF floor participant is the source).
+
+### 6.4.4.2 Receive Floor Taken message
+
+Upon receiving the Floor Taken message, the IWF floor participant:
+
+1. if the first bit in the subtype of the Floor Taken message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '2' (Floor Taken); and
+  - b. shall include the Source field set to '0' (the IWF floor participant is the source).
+
+### 6.4.4.3 Receive RTP media packets
+
+The IWF can expect to receive RTP media packets at any time during a media session except after releasing a media session.
+
+NOTE: RTP media packets can be received from multiple sources when dual floor control is applied by the floor control server (see 3GPP TS 24.380 [25], clause 6.3.6). The IWF can differentiate between the different sources using the SSRC in the received RTP media packets. How the IWF mixes the different RTP media stream sources is out of scope of the present document.
+
+### 6.4.4.4 Send Floor Request message
+
+Upon deciding to request permission to send media, the IWF floor participant:
+
+1. shall send the Floor Request message toward the MCPTT floor control server; The Floor Request message:
+  - a. if a different priority than the normal priority is required, shall include the Floor Priority field with the priority not higher than negotiated with the floor control server as specified in clause 14.3.3; and
+  - b. if the floor request is a broadcast group call, system call, emergency call or an imminent peril call, shall include a Floor Indicator field indicating the relevant call types.
+
+#### 6.4.4.5 Receive Floor Granted message
+
+Upon receiving a Floor Granted message from the floor control server or a floor granted indication in a SIP 200 (OK) response in the application and signalling layer, the IWF floor participant:
+
+1. if the first bit in the subtype of the Floor Granted message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '1' (Floor Granted); and
+  - b. shall include the Source field set to '0' (the IWF floor participant is the source);
+2. may send a Floor Release message at any time, even before sending any media; and
+3. shall start encoding and forwarding media to the MCPTT server.
+
+#### 6.4.4.6 Receive Floor Deny message
+
+Upon receiving a Floor Deny message, the IWF floor participant:
+
+1. if the first bit in the subtype of the Floor Deny message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '3' (Floor Deny); and
+  - b. shall include the Source field set to '0' (the IWF floor participant is the source); and
+2. shall not encode and forward voice packets.
+
+#### 6.4.4.7 Send Floor Release message
+
+Upon deciding to release permission to send media, the IWF floor participant:
+
+1. shall send a Floor Release message towards the floor control server;
+  - a. if the session is a broadcast call and if the session was established as a normal call, shall include the Floor Indicator with the A-bit set to '1' (Normal call);
+2. may include the first bit in the subtype of the Floor Release message set to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. if the Floor Granted message included the G-bit set to '1' (Dual floor), shall include the Floor Indicator with the G-bit set to '1' (Dual floor).
+
+#### 6.4.4.8 Receive Floor Queue Position Info message
+
+Upon receiving a Floor Queue Position Info message, the IWF floor participant:
+
+1. if the first bit in the subtype of the Floor Queue Position Info message is set to '1' (Acknowledgment is required) as described in clause 8.3.2, shall send a Floor Ack message. The Floor Ack message:
+  - a. shall include the Message Type field set to '9' (Floor Queue Position Info); and
+  - b. shall include the Source field set to '0' (the IWF floor participant is the source).
+
+NOTE: While in the queue, the IWF floor participant can receive RTP Media packets and the IWF floor participant can send and receive floor control messages.
+
+#### 6.4.4.9 Receive Floor Revoke message
+
+Upon receiving a Floor Revoke message, the IWF floor participant:
+
+1. shall discard any remaining buffered RTP media packets and to stop forwarding encoded voice to the MCPTT server;
+
+2. shall send a Floor Release message. In the Floor Release message:
+  - a. shall include the Floor Indicator with the G-bit set to the value of the G-bit in the Floor Revoke message; and
+  - b. may set the first bit in the subtype to '1' (Acknowledgment is required) as described in clause 8.3.2.
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+#### 6.4.4.10 Receive MCPTT call release
+
+Upon receiving an MCPTT call release request from the application and signalling plane when the MCPTT call is going to be released or when the IWF floor participant is leaving the MCPTT call, the IWF floor participant:
+
+1. shall stop sending floor control messages; and
+2. shall stop sending RTP media packets.
+
+### 6.5 IWF performing the non-controlling role of an MCPTT group
+
+#### 6.5.4 Floor control server interface procedures
+
+##### 6.5.4.1 General
+
+The floor control server interface is stateless with regards to the floor control message received and sent.
+
+The following subclauses specify what the floor control server interface shall do when receiving a floor control message sent by the controlling MCPTT function or received at the floor participant interface or initiated internally for an IWF media endpoint and how the floor control server controls the media distribution function in the non-controlling MCPTT function.
+
+**Editor's Note:** Existing clauses 6.3.5 and 6.3.6 should be evaluated for updates now that we support regroup. Search for "non-controlling" in TS 24.380 and TS 29.380.
+
+##### 6.5.4.2 Receiving a Floor Request message
+
+Upon receiving a Floor Request message from one floor participant interface, the floor control server interface:
+
+1. shall
+  - a. forward the Floor Request message to the controlling MCPTT function if the controlling function is in the MCPTT system; or
+  - b. forward to the floor control server in the IWF if the controlling function is in the IWF.
+
+The Floor Request message:
+
+- a. shall include all fields included by the floor participant;
+  - b. if a Track Info field is included, shall include the temporary identifier at the end of the <Floor Participant Reference> value item; and
+  - c. if a Track Info field is not included, shall include a Track Info field populated as follows:
+    - i. shall include the "mc\_queueing" fmtp attribute value negotiated as specified in clause 14 in the <Queueing Capability> value;
+    - ii. shall include a <Participant Type> value based on the <participant-type> element specified in 3GPP TS 24.481 [12], if value in the <participant-type> element is available, otherwise set the <Participant Type> value to "unknown"; and
+    - iii. shall include the temporary identifier as the first <Floor Participant Reference> value; and
+2. if the value of the <Queueing Capability> in the Track Info is '1' (the floor participant in the MCPTT client supports queueing), shall store the outgoing Floor Request message in the passive floor request queue.
+
+#### 6.5.4.2A IWF sends a Floor Request message
+
+Upon deciding to request permission to send media when the controlling function is in the MCPTT system, the IWF:
+
+1. shall send the Floor Request message toward the MCPTT floor control server in the MCPTT system. The Floor Request message:
+  - a. if a different priority than the normal priority is required, shall include the Floor Priority field with the priority not higher than negotiated with the floor control server as specified in clause 14.3.3; and
+  - b. if the floor request is a broadcast group call, system call, emergency call or an imminent peril call, shall include a Floor Indicator field indicating the relevant call types.
+
+#### 6.5.4.3 Receive Floor Release message
+
+Upon receiving a Floor Release message from one floor participant interface, the floor control server interface:
+
+NOTE: A Floor Release message can be received from the permitted floor participant and from any participant that is queued in the floor control server.
+
+1. shall forward a Floor Release message to the controlling MCPTT function if the controlling function is in the MCPTT system or to the floor control server state transition diagram for basic floor control operation towards the floor participant in the IWF if the controlling function is in the IWF. The Floor Release message:
+  - a. shall include all fields included by the floor participant in the Floor Release message;
+  - b. if a Track Info field is included, shall include the temporary identifier at the end of the <Floor Participant Reference> value item; and
+  - c. if a Track Info field is not included, shall include a Track Info field as follows:
+    - i. shall include the "mc\_queueing" fmtp attribute value negotiated as specified in clause 14 in the <Queueing Capability> value; and
+    - ii. shall include the temporary identifier as the first <Floor Participant Reference> value; and
+2. if a Floor Request message received from this floor participant is in the passive floor request queue, shall remove the floor request from the passive floor request queue.
+
+#### 6.5.4.3A IWF sends a Floor Release message
+
+Upon deciding to release permission to send media when the controlling function is in the MCPTT system, the IWF floor participant:
+
+1. shall send a Floor Release message towards the floor control server in the MCPTT system;
+  - a. if the session is a broadcast call and if the session was established as a normal call, shall include the Floor Indicator with the A-bit set to '1' (Normal call);
+2. may include the first bit in the subtype of the Floor Release message set to '1' (Acknowledgment is required) as described in clause 8.3.2; and
+
+NOTE: It is an implementation option to handle the receipt of the Floor Ack message and what action to take if the Floor Ack message is not received.
+
+3. if the Floor Granted message included the G-bit set to '1' (Dual floor), shall include the Floor Indicator with the G-bit set to '1' (Dual floor).
+
+#### 6.5.4.4 Receive Floor Queue Position Request message
+
+Upon receiving a Floor Queue Position Request message from one floor participant interface, the floor control server interface:
+
+1. shall forward the Floor Queue Position Request message to the controlling MCPTT function if the controlling function is in the MCPTT system or to the floor control server state transition diagram for basic floor control
+
+operation towards the floor participant in the IWF if the controlling function is in the IWF. The Floor Queue Position Request message:
+
+- a. shall include all fields included by the floor participant;
+- b. if a Track Info field is included, shall include the temporary identifier at the end of the <Floor Participant Reference> value item; and
+- c. if a Track Info field is not included, shall include a Track Info field as follows:
+  - i. shall include the "mc\_queueing" fmtp attribute value negotiated as specified in clause 14 in the <Queueing Capability> value; and
+  - ii. shall include the temporary identifier as the first <Floor Participant Reference> value.
+
+#### 6.5.4.4A IWF sends Floor Queue Position Request message
+
+Upon deciding to request the queue position, when the controlling function is in the MCPTT system, the IWF:
+
+1. shall send the Floor Ack message towards the floor control server in the MCPTT system. The Floor Ack message:
+  - a. shall include the Message Type field set to '2' (Floor Taken);
+  - b. shall include the Source field set to '0' (the floor participant is the source); and
+  - c. shall include a Track Info field as follows:
+    - i. shall include the "mc\_queueing" fmtp attribute value negotiated as specified in clause 14 in the <Queueing Capability> value; and
+    - ii. shall include the temporary identifier as the first <Floor Participant Reference> value.
+
+#### 6.5.4.5 Receive Floor Ack message
+
+Upon receiving a Floor Ack message from one floor participant interface the floor control server interface:
+
+1. shall send the Floor Ack message towards the controlling MCPTT function if the controlling function is in the MCPTT system or to the floor control server state transition diagram for basic floor control operation towards the floor participant in the IWF if the controlling function is in the IWF. The Floor Ack message:
+  - a. shall include all fields included by the floor participant in the Floor Ack message;
+  - b. if Track Info field is included, shall include the temporary identifier at the end of the <Floor Participant Reference> value item; and
+  - c. if a Track Info field is not included, shall include a Track Info field with temporary identifier as the first <Floor Participant Reference>.
+
+#### 6.5.4.5A IWF sends Floor Ack message
+
+Upon deciding to send a Floor Ack message, when the controlling function is in the MCPTT system, the IWF:
+
+1. shall send the Floor Ack message towards the floor control server in the MCPTT system. The Floor Ack message shall include a Track Info field as follows:
+  - a. shall include the temporary identifier as the first <Floor Participant Reference> value.
+
+#### 6.5.4.6 Receive Floor Granted message
+
+Upon receiving a Floor Granted message sent from the controlling MCPTT function, the floor control server interface:
+
+1. shall send the Floor Granted to the floor participant interface identified by the <Participant Reference> value at the end of the Track Info field. The Floor Granted message:
+  - a. shall include the fields as received with the following exceptions:
+
+- i. if the Track Info field only contains one <Participant Reference> value, shall remove the Track Info field from the outgoing Floor Granted message; and
+    - ii. if the Track Info field contains more than one <Participant Reference> value, shall remove the last <Participant Reference> value from the Track Info field from the outgoing Floor Granted message; and
+  - b if the Floor Indicator field is included in the Floor Granted message and the G-bit is set to '1' (Dual floor), shall store the SSRC of granted floor participant and associate the stored value with dual floor;
+2. if:
+    - a. the SSRC of the granted floor participant associated with dual floor is not stored, shall send a Floor Taken message populated as specified in step d. below to all participant interfaces with the exception of the floor participant interface to which the Floor Granted message is sent;
+    - b. the SSRC of the granted floor participant associated with dual floor is stored and if the Floor Indicator field is not included in the Floor Granted message or if the Floor Indicator field is included in the Floor Granted message and the G-bit is set to '0' (Not dual floor), shall send a Floor Taken message populated as specified in step d. below to all participant interfaces with the exception of:
+      - i. the floor participant interface to which the Floor Granted message is sent; and
+      - ii. the floor participants only listening to the overriding floor participant;
+    - c. the Floor Indicator field is included in the Floor Granted message and the G-bit is set to '1' (Dual floor):
+      - i. shall send a Floor Taken message populated as specified in step d. below to floor participants that will listen to the RTP media from the overriding MCPTT client according to local policy;
+
+NOTE 1: The floor participant overridden by the overriding floor participant is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration.
+
+d. The Floor Taken message:
+
+- i. shall include the granted user's MCPTT ID in the Granted Party's Identity field if privacy is not requested by the granted floor participant when the floor participant was invited to the session;
+
+NOTE 2: The privacy request was stored for each invited floor participant when the floor participant accepted the invitation as specified in subclause 6.5.2.
+
+- ii. shall include in the Message Sequence Number field the local <Message Sequence Number> value increased with 1;
+- iii. shall include the Permission to Request Floor field to '0', if the group call is a broadcast group call;
+- iv. may include the Permission to Request the Floor field set to '1', if the group call is not a broadcast group call; and
+- v. shall set the first bit in the subtype of the Floor Taken message to '0' (acknowledgement is not required); and
+
+NOTE 3: A Floor Taken message sent to all participants does not require acknowledgement.
+
+- e. if the Floor Indicator field was included in the Floor Granted message, shall include the received Floor Indicator field; and
+3. if the Floor Request message received from the floor participant is in the passive floor request queue, shall remove the floor request from the passive floor request queue; and
+- 4 if the Floor Indicator field is included in the Floor Granted message and the G-bit is set to '1' (Dual floor), shall send a Floor Idle message to those floor participants that will only listen to RTP media from the overriding MCPTT client. The Floor Idle message:
+  - a. shall include the Floor Indicator field as received in the Floor Granted message with the G-bit set to '0' (Not dual floor); and
+
+- b. shall include in the Message Sequence Number field the local <Message Sequence Number> value increased with 1.
+
+### 6.5.4.6A IWF grants floor
+
+Upon deciding to grant floor, where the controlling function is in the IWF, the IWF floor control server interface:
+
+*Editor's Note: Need to create a grant message for internally generated requests, need to also consider floor requests coming from IWF CF that originated in MCPTT, how do those make it here? Does IWF CF call this nCF?*
+
+*Editor's note: Need to add procedures for clauses 6.5.4.7 thru 6.5.4.16.*
+
+### 6.5.4.17 Receive Floor Release Multi Talker message
+
+Upon receiving a Floor Release Multi Talker message sent from the controlling MCPTT function, the IWF floor control server interface shall ignore the Floor Release Multi Talker message.
+
+NOTE: The multi-taker feature is not supported in the present document.
+
+## 6.5.5 Floor participant interface procedures
+
+### 6.5.5.1 General
+
+The floor participant interface toward the MCPTT client shall behave according to the state diagram and state transitions specified in this clause.
+
+Figure 6.5.5.1-1 shows the general floor control operation states (P states) and the state transition diagram.
+
+![State transition diagram for floor participant interface. States: Start-stop, Releasing, Any state, P: has permission, P: has no permission. Transitions include R: MCPTT call release - 1, R: MCPTT call release - 2, R: Floor Ack, Participant invited to session, R: Split, R: Floor Idle OR R: Floor Taken, R: Floor Granted, R: RTP media OR R: Floor Release OR R: Floor Ack OR R: Floor Revoke OR R: Floor Taken OR R: Floor Release Multi-talker.](b701cd8c436a2857a615a76a868a3bb7_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> Start-stop
+    Start-stop --> Releasing : R: MCPTT call release - 2
+    Releasing --> Start-stop
+    Releasing --> Any state : R: MCPTT call release - 1
+    Any state --> Start-stop : R: Floor Ack
+    Start-stop --> P: has permission : Participant invited to session
+    P: has permission --> Start-stop : R: Split
+    P: has permission --> P: has no permission : R: Floor Idle OR R: Floor Taken
+    P: has no permission --> Start-stop : R: Split
+    P: has no permission --> P: has permission : R: Floor Granted
+    P: has permission --> [*] : R: RTP media OR R: Floor Release OR R: Floor Ack OR R: Floor Revoke OR R: Floor Taken OR R: Floor Release Multi-talker
+    P: has no permission --> [*] : R: Floor Idle OR R: Floor Taken OR R: Floor Request OR R: Floor Deny OR R: Floor Queue Position Info OR R: Floor Queue Position Request OR R: RTP media OR R: Floor Release OR R: Floor Release Multi-talker
+  
+```
+
+State transition diagram for floor participant interface. States: Start-stop, Releasing, Any state, P: has permission, P: has no permission. Transitions include R: MCPTT call release - 1, R: MCPTT call release - 2, R: Floor Ack, Participant invited to session, R: Split, R: Floor Idle OR R: Floor Taken, R: Floor Granted, R: RTP media OR R: Floor Release OR R: Floor Ack OR R: Floor Revoke OR R: Floor Taken OR R: Floor Release Multi-talker.
+
+Figure 6.5.5.1-1: The 'floor participant interface toward the MCPTT client state transition' state diagram
+
+The floor participant interface toward the MCPTT client shall keep one instance of the 'floor participant interface toward the MCPTT client state transition' state machine per MCPTT client in a session. The interface and procedures toward IWF media endpoints are out of scope of the present document.
+
+The floor participant associated to the 'floor participant interface toward the MCPTT client state transition' state machine is in the following clauses referred to as the MCPTT floor participant.
+
+If floor control messages or RTP media packets arrives in a state where there is no procedure specified in the following clauses the floor participant interface toward the MCPTT client:
+
+1. shall discard the floor control message;
+2. shall request the network media interface to discard any received RTP media packet; and
+3. shall remain in the current state.
+
+State details are explained in the following clauses.
+
+### 6.5.5.2 State: 'Start-Stop'
+
+#### 6.5.5.2.1 General
+
+When a new instance of the 'Floor participant interface toward the MCPTT client state transition' state machine is initiated, before any floor control related input is applied, the state machine is in 'Start-stop' state. Similarly, when the session is released the state machine shall return to the 'Start-stop' state.
+
+#### 6.5.5.2.2 Participant invited to session
+
+When the floor participant interface toward the MCPTT client receives an indication from the floor control server interface that an MCPTT client has accepted the invitation to a session (i.e. when the SIP 200 (OK) response to the initial SIP INVITE request is received as specified in 3GPP TS 24.379 [2]) , the floor participant interface toward the MCPTT client:
+
+1. shall enter the 'P: has no permission' state.
+
+### 6.5.5.3 State: 'P: has no permission'
+
+#### 6.5.5.3.1 General
+
+The floor participant interface toward the MCPTT client uses this state when the MCPTT floor participant is not permitted to send media.
+
+#### 6.5.5.3.2 Receive Floor Idle message (R: Floor Idle)
+
+When the floor participant interface toward the MCPTT client receives a Floor Idle message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Idle message to the MCPTT floor participant;
+2. if the first bit in the subtype of the Floor Idle message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, shall store an indication that a Floor Ack message to a Floor Idle messages is expected; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.3 Receive Floor Taken message (R: Floor Taken)
+
+When the floor participant interface toward the MCPTT client receives a Floor Taken message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Taken message to the MCPTT floor participant;
+2. if the first bit in the subtype of the Floor Taken message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, shall store an indication that a Floor Ack message to a Floor Taken messages is expected; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.4 Receive Floor Request message (R: Floor Request)
+
+When the floor participant interface toward the MCPTT client receives a Floor Request message from the MCPTT floor participant, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Request message to the floor control server interface; and
+2. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.5 Receive Floor Granted message (R: Floor Granted)
+
+When the floor participant interface toward the MCPTT client receives a Floor Granted message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Granted message to the MCPTT floor participant;
+2. if the first bit in the subtype of the Floor Granted message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, shall store an indication that a Floor Ack message to a Floor Granted messages is expected; and
+3. shall enter the 'P: has permission' state.
+
+#### 6.5.5.3.6 Receive Floor Deny message (R: Floor Deny)
+
+When the floor participant interface toward the MCPTT client receives a Floor Deny message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Deny message to the MCPTT floor participant toward the MCPTT client;
+2. if the first bit in the subtype of the Floor Deny message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, shall store an indication that a Floor Ack message to a Floor Deny messages is expected; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.7 Receive Floor Queue Position Info message (R: Floor Queue Position Info)
+
+When the floor participant interface toward the MCPTT client receives a Floor Queue Position Info message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Queue Position Info message to the MCPTT floor participant;
+2. if the first bit in the subtype of the Floor Queue Position Info message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, shall store an indication that a Floor Ack message to a Floor Queue Position Info messages is expected; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.8 Receive Floor Queue Position Request message (R: Floor Queue Position Request)
+
+When the floor participant interface toward the MCPTT client receives a Floor Queue Position Request message from the MCPTT floor participant, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Queue Position Request message to the floor control server interface; and
+2. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.9 Receive RTP media packets (R: RTP media)
+
+When the floor participant interface toward the MCPTT client receives an indication from the network media interface that RTP media packets are received from the media distributor, the floor participant interface toward the MCPTT client:
+
+1. shall instruct the network media interface to send the received RTP media packets towards the MCPTT client; and
+2. shall remain in the 'P: has no permission' state.
+
+When the floor participant interface toward the MCPTT client receives an indication from the network media interface that RTP media packets are received from the MCPTT client, the floor participant interface toward the MCPTT client:
+
+1. shall send a Floor Revoke message to the MCPTT floor participant. The Floor Revoke message:
+  - a. shall include the Reject Cause field with the <Reject Cause> value set to #3 (No permission to send a Media Burst);
+2. shall store that a Floor Release message is expected from the MCPTT floor participant; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.10 Receive Floor Release message (R: Floor Release)
+
+When the floor participant interface toward the MCPTT client receives a Floor Release message from the MCPTT floor participant, the floor participant interface toward the MCPTT client:
+
+1. if a Floor Release message is not expected from the MCPTT floor participant:
+  - a. if the first bit in the subtype of the Floor Release message is set to '1' (acknowledgement is required) as specified in clause 8.2.2, based on local policy:
+    - i. shall send a Floor Ack message to the MCPTT floor participant and set the first bit in the subtype of the Floor Release message to '0' (acknowledgement is not required) in the outgoing Floor Release message; or
+    - ii. wait for the Floor Ack from the floor control server; and
+  - b. shall forward the Floor Release message to the floor control server interface;
+2. if a Floor Release message is expected from the MCPTT floor participant:
+  - a. if the first bit in the subtype of the Floor Release message is set to '1' (acknowledgement is required) as specified in clause 8.2.2:
+    - i. shall send a Floor Ack message to the MCPTT floor participant; and
+  - b. shall remove that a Floor Release message is expected from the floor participant; and
+3. shall remain in the 'P: has no permission' state.
+
+#### 6.5.5.3.11 Receive split instruction (R: Split)
+
+Upon receiving an instruction to split the ongoing MCPTT call, to the floor participant interface toward the MCPTT client:
+
+1. shall create a new instance of the 'basic floor control operation towards the floor participant' state machine;
+  2. shall move information associated with the instance used for 'floor participant interface toward the MCPTT client state transition' to the 'basic floor control operation towards the floor participant' state machine;
+- NOTE: Which information that needs to be moved is an implementation option.
+3. shall enter the 'Start-stop' state and terminate the 'floor participant state transition' state machine associated with this MCPTT floor participant and this session;
+  4. if the state in 'general floor control operation' state machine is 'G: Floor Idle' state; shall enter the 'U: not permitted and Floor Idle' state as specified in clause 6.3.5.3.2; and
+  5. if the state in 'general floor control operation' state machine is 'G: Floor Taken' state; shall enter the 'U: not permitted and Floor Taken' state as specified in clause 6.3.5.4.2.
+
+#### 6.5.5.3.12 Receive Floor Release Multi Talker message (R: Floor Release Multi-talker)
+
+When the floor participant interface toward the MCPTT client receives a Floor Release Multi Talker message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall remain in the 'P: has no permission' state.
+
+NOTE: The multi-talker feature is not supported in the present document.
+
+#### 6.5.5.4 State: 'P: has permission'
+
+##### 6.5.5.4.1 General
+
+The floor participant interface toward the MCPTT client uses this state when the floor participant has permission to send media
+
+##### 6.5.5.4.2 Receive RTP media packets
+
+When the floor participant interface toward the MCPTT client receives an indication from the network media interface that RTP media packets are received from the MCPTT client, the floor participant interface toward the MCPTT client:
+
+1. shall instruct the media interface to forward received RTP media packets towards the media distributor; and
+2. shall remain in the 'P: has permission' state.
+
+##### 6.5.5.4.3 Receive Floor Release message (R: Floor Release)
+
+When the floor participant interface toward the MCPTT client receives a Floor Release message from the floor participant, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Release message to the floor control server interface; and
+3. shall remain in the 'P: has permission' state.
+
+##### 6.5.5.4.4 Receive Floor Ack message (R: Floor Ack)
+
+When the floor participant interface toward the MCPTT client receives a Floor Ack message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Ack message to the floor participant; and
+2. shall remain in the 'P: has permission' state.
+
+##### 6.5.5.4.5 Receive Floor Idle message (R: Floor Idle)
+
+When the floor participant interface toward the MCPTT client receives a Floor Idle message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Idle message to the floor participant;
+2. if the first bit in the subtype of the Floor Idle message is set to '1' (acknowledgement is required), shall store an indication that a Floor Ack message to a Floor Idle messages is expected; and
+3. shall enter the 'P: has no permission' state.
+
+##### 6.5.5.4.6 Receive Floor Taken message (R: Floor Taken)
+
+When the floor participant interface toward the MCPTT client receives a Floor Taken message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Taken message to the floor participant;
+2. if the first bit in the subtype of the Floor Taken message is set to '1' (acknowledgement is required), shall store an indication that a Floor Ack message to a Floor Taken messages is expected; and
+3. shall enter the 'P: has no permission' state.
+
+##### 6.5.5.4.7 Receive Floor Revoke message (R: Floor Revoke)
+
+When the floor participant interface toward the MCPTT client receives a Floor Revoke message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Revoke message to the MCPTT floor participant;
+2. if the first bit in the subtype of the Floor Revoke message is set to '1' (acknowledgement is required), shall store an indication that a Floor Ack message to a Floor Revoke messages is expected; and
+3. shall remain in the 'P: has permission' state.
+
+#### 6.5.5.4.8 Receive split instruction (R: Split)
+
+Upon receiving an instruction to split the ongoing MCPTT call, the floor participant interface toward the MCPTT client:
+
+1. shall create a new instance of the 'basic floor control operation towards the floor participant' state machine as specified in clause 6.3.5;
+2. shall move information associated with the instance used for 'floor participant interface toward the MCPTT client state transition' to the 'basic floor control operation towards the floor participant' state machine;
+
+NOTE: Which information that needs to be moved is an implementation option.
+
+3. shall enter the 'Start-stop' state and terminate the 'floor participant state transition' state machine associated with this MCPTT floor participant and this session; and
+4. shall enter the 'U: permitted' state as specified in clause 6.3.5.5.2.
+
+#### 6.5.5.4.9 Receive Floor Release Multi Talker message (R: Floor Release Multi-talker)
+
+When the floor participant interface toward the MCPTT client receives a Floor Release Multi Talker message from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall remain in the 'P: has permission' state.
+
+NOTE: The multi-talker feature is not supported in the present document.
+
+### 6.5.5.5 In any state
+
+#### 6.5.5.5.1 General
+
+This clause describes the actions to be taken in all states defined for the 'floor participant state transition' diagram with the exception of the 'Start-stop' and 'Releasing' states.
+
+#### 6.5.5.5.2 Receive Floor Ack message (R: Floor Ack)
+
+If a Floor Ack message is received from the MCPTT floor participant, the floor participant interface toward the MCPTT client:
+
+1. if an indication exists that a Floor Ack message is expected for the message in the Message Type field;
+  - a. shall forward the Floor Ack message to the floor control server interface; and
+  - b. shall remove the indication that a Floor Ack message is expected for the message in the Message Type field; and
+
+NOTE: It is an implementation option what action to take if an indication exists that a Floor Ack message is expected for the message in the Message Type field, but the Floor Ack message is not received
+
+2. shall remain in the current state.
+
+If a Floor Ack message is received from the floor control server interface, the floor participant interface toward the MCPTT client:
+
+1. shall send the Floor Ack message to the MCPTT floor participant; and
+2. shall remain in the current state.
+
+#### 6.5.5.5.3 MCPTT session release step 1 (MCPTT call release - 1)
+
+Upon receiving an MCPTT call release step 1 request from the application and signalling plane e.g. when the session is going to be released or when the MCPTT client leaves the session, the floor participant interface toward the MCPTT client:
+
+1. shall stop sending floor control messages to the MCPTT floor participant;
+2. shall request the network media interface to stop sending RTP media packets towards to the MCPTT client;
+3. shall ignore any floor control messages received from the MCPTT floor participant;
+4. shall request the network media interface to stop forwarding RTP media packets from the MCPTT client to the media distributor;
+5. shall indicate to the floor control server interface that the MCPTT client has started to disconnect from the session; and
+6. shall enter the 'P: Releasing' state.
+
+#### 6.5.5.6 State: 'P: Releasing'
+
+##### 6.5.5.6.1 General
+
+The floor participant interface toward the MCPTT client uses this state while waiting for the application and signalling plane to finalize the release of the session or finalizing the removal of the MCPTT client from the session.
+
+##### 6.5.5.6.2 MCPTT session release step 2 (MCPTT call release - 2)
+
+Upon receiving an MCPTT call release step 2 request from the application and signalling plane, the floor participant interface toward the MCPTT client:
+
+1. shall request the network media interface to release all resources associated with this MCPTT client for this MCPTT call; and
+2. shall enter the 'Start-stop' state and terminate the 'floor participant state transition' state machine associated with this MCPTT floor participant and this session.
+
+---
+
+## 7 Off-network floor control
+
+Off-network floor control is not applicable to an IWF.
+
+---
+
+## 8 Coding
+
+### 8.1 Introduction
+
+The message and field formats specified in 3GPP TS 24.380 [25] clause 8.1 shall be used.
+
+### 8.2 Floor control
+
+The procedures specified in 3GPP TS 24.380 [25] clause 8.2 shall be used with the following clarification.
+
+The field formats specified in 3GPP TS 24.380 [25] clause 8.2 shall be supported except for fields and field values used for the following features:
+
+- multi-talker;
+- ambient listening; and
+- functional alias.
+
+## 8.3 Pre-established session call control
+
+Pre-established session call control is not applicable to the IWF.
+
+## 8.4 MBMS subchannel control
+
+MBMS subchannel control is not applicable to the IWF.
+
+## 8.5 MBMS notifications
+
+MBMS notifications are not applicable to the IWF.
+
+---
+
+# 9 Call setup control over pre-established session
+
+Call setup control over a pre-established session is not applicable to the IWF.
+
+---
+
+# 10 MBMS procedures
+
+MBMS procedures are not applicable to the IWF.
+
+---
+
+# 11 Configurable parameters
+
+## 11.1 Timers
+
+## 11.2 Counters
+
+---
+
+# 12 Extensions within the present document
+
+No extensions are defined in the present document.
+
+The IWF shall support the session description types defined in 3GPP TS 24.380 [25] clause 12.1.
+
+---
+
+# 13 Media plane security
+
+## 13.1 General
+
+Media plane security provides integrity and confidentiality protection of individual media streams and media plane control messages in MCPTT sessions.
+
+The media plane security is based on the 3GPP MCPTT security solution including key management and end-to-end media and floor control messages protection as defined in 3GPP TS 33.180 [18].
+
+Various keys and associated key identifiers protect:
+
+1. RTP transported media;
+2. RTCP transported media control messages (i.e. RTCP SR packets, RTCP RR packets, RTCP SDES packets); and
+3. RTCP APP transported floor control messages.
+
+In an on-network group call of an MCPTT group which is not a constituent MCPTT group of a temporary MCPTT group:
+
+1. if protection of media is negotiated, the GMK and the GMK-ID of the MCPTT group protect the media sent and received by MCPTT clients and users homed in the IWF;
+
+2. if protection of floor control messages between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the floor control messages sent and received between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function; and
+3. if protection of media control messages between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the media control messages sent and received between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function.
+
+In an on-network group call of an MCPTT group which is a constituent MCPTT group of a temporary MCPTT group:
+
+1. if protection of media is negotiated, the GMK and the GMK-ID of the temporary MCPTT group protect the media sent and received by an MCPTT client and a user homed in the IWF;
+2. if protection of floor control messages between the IWF performing the participating role and the non-controlling MCPTT function or between the IWF performing the non-controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the floor control messages sent and received between the IWF performing the participating role and the non-controlling MCPTT function or between the IWF performing the non-controlling role and participating MCPTT function;
+3. if protection of floor control messages between the IWF performing the non-controlling role and the controlling MCPTT function or between the IWF performing the controlling role and the non-controlling MCPTT function is negotiated, the SPK and the SPK-ID protect the floor control messages sent and received between the IWF performing the non-controlling role and the controlling MCPTT function or between the IWF performing the controlling role and the non-controlling MCPTT function;
+4. if protection of media control messages between the IWF performing the participating role and the non-controlling MCPTT function or between the IWF performing the non-controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the media control messages sent and received between the IWF performing the participating role and the non-controlling MCPTT function or between the IWF performing the non-controlling role and the participating MCPTT function; and
+5. if protection of media control messages between the IWF performing the non-controlling role and the controlling MCPTT function or between the IWF performing the controlling role and the non-controlling MCPTT function is negotiated, the SPK and the SPK-ID protect the media control messages sent and received between the IWF performing the non-controlling role and the controlling MCPTT function or between the IWF performing the controlling role and the non-controlling MCPTT function.
+
+In an on-network private call:
+
+1. if protection of media is negotiated, the PCK and the PCK-ID protect media sent and received by the MCPTT client and the user homed in the IWF;
+2. if protection of floor control messages between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the floor control messages sent and received between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function; and
+3. if protection of media control messages between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function is negotiated, the SPK and the SPK-ID protect the media control messages sent and received between the IWF performing the participating role and the controlling MCPTT function or between the IWF performing the controlling role and the participating MCPTT function.
+
+The GMK and the GMK-ID are distributed to the MCPTT clients using the group document subscription and notification procedure specified in 3GPP TS 24.481 [12].
+
+The GMK and the GMK-ID are distributed to the IWF by the MCPTT GMS per the procedures specified in 3GPP TS 24.481 [12] for distribution of the GMK and GMK-ID to an MCPTT server.
+
+How the GMK and the GMK-ID are distributed to floor participants homed in the IWF is out of scope of the present document.
+
+The SPK and the SPK-ID are configured in the IWF for all the roles it performs.
+
+If a private call that passes through the IWF is initiated by an MCPTT client, the PCK and the PCK-ID are generated by the MCPTT client initiating the private call and provided to the IWF using SIP signalling according to 3GPP TS 24.379 [2], using the Connect message described in clause 8.3.4.
+
+If a private call that passes through the IWF is initiated by a user homed in the IWF, the PCK and the PCK-ID are generated by the IWF and provided to the MCPTT client receiving the private call using SIP signalling according to 3GPP TS 24.379 [2], using the Connect message described in clause 8.3.4.
+
+NOTE: The distribution and provisioning of LMR keys by the LMR system to entities in the MCPTT system is out of scope.
+
+## 13.2 Derivation of SRTP/SRTCP master keys
+
+Each key (i.e. GMK, PCK, SPK) and its associated key identifier (i.e. GMK-ID, PCK-ID, SPK-ID) described in clause 13.1 are used to derive SRTP-MK, SRTP-MS and SRTP-MKI.
+
+SRTP-MK, SRTP-MS and SRTP-MKI are used in encryption of media or floor control messages in SRTP as specified in IETF RFC 3711 [16] and 3GPP TS 33.180 [18].
+
+### 13.3.1 General
+
+Void.
+
+### 13.3.2 The IWF performing the participating role
+
+The IWF performing the participating role:
+
+1. if protection of media is negotiated, shall be transparent to RTP media streams and shall forward encrypted RTP media streams without decrypting the payload;
+2. if protection of floor control messages between the IWF performing the participating role and the controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the participating role:
+  - A) shall encrypt floor control messages sent to the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) shall decrypt floor control messages received from the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+3. if protection of floor control messages between the IWF performing the participating role and the non-controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the participating role:
+  - A) shall encrypt floor control messages sent to the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) shall decrypt floor control messages received from the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+4. if protection of media control messages between the IWF performing the participating role and the controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the participating role:
+
+- A) shall encrypt media control messages sent to the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) shall decrypt media control messages received from the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+- 5. if protection of media control messages between the IWF performing the participating role and the non-controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the participating role:
+    - A) shall encrypt media control messages sent to the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - B) shall decrypt media control messages received from the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2.
+
+### 13.3.3 The IWF media endpoint
+
+The IWF media endpoint:
+
+- 1. in an on-network group call of an MCPTT group which is not a constituent MCPTT group of a temporary MCPTT group:
+  - A) if protection of media is negotiated and the GMK and the GMK-ID of the MCPTT group were received using the group document subscription and notification procedure specified in 3GPP TS 24.481 [12] for the MCPTT group:
+    - i) shall encrypt sent media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the GMK and GMK-ID as specified in clause 13.2; and
+    - ii) shall decrypt received media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the GMK and GMK-ID as specified in clause 13.2;
+- 2. in an on-network group call of an MCPTT group which is a constituent MCPTT group of a temporary MCPTT group:
+  - A) if protection of media is negotiated and the GMK and the GMK-ID of the temporary MCPTT group were received using the group document subscription and notification procedure specified in 3GPP TS 24.481 [12] for the constituent MCPTT group:
+    - i) shall encrypt sent media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the GMK and GMK-ID of the temporary MCPTT group as specified in clause 13.2; and
+    - ii) shall decrypt received media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the GMK and GMK-ID of the temporary MCPTT group as specified in clause 13.2; and
+- 3. in an on-network private call:
+  - A) if:
+    - i) protection of media is negotiated in an originating call and the PCK and the PCK-ID were sent to the remote MCPTT client using SIP signalling according to 3GPP TS 24.379 [2]; or
+    - ii) protection of media is negotiated in a terminating call and the PCK and the PCK-ID were received from the remote MCPTT client using SIP signalling according to 3GPP TS 24.379 [2];
+
+then:
+
+  - i) shall encrypt sent media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the PCK and PCK-ID as specified in clause 13.2; and
+
+- ii) shall decrypt received media according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the PCK and PCK-ID as specified in clause 13.2.
+
+### 13.3.4 The IWF performing the controlling role
+
+The IWF performing the controlling role:
+
+1. if protection of media is negotiated, shall be transparent to RTP media streams and shall forward encrypted RTP media streams without decrypting the payload;
+2. in an on-network group call of an MCPTT group which is not a constituent MCPTT group of a temporary MCPTT group:
+  - A) if protection of floor control messages between the IWF performing the controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+    - i) shall encrypt floor control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - ii) shall decrypt floor control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) if protection of media control messages between the IWF performing the controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+    - i) shall encrypt media control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - ii) shall decrypt media control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+3. in an on-network group call of an MCPTT group which is a constituent MCPTT group of a temporary MCPTT group:
+  - A) if protection of floor control messages between the IWF performing the controlling role and the non-controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+    - i) shall encrypt floor control messages sent to the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - ii) shall decrypt floor control messages received from the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) if protection of media control messages between the IWF performing the controlling role and the non-controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+    - i) shall encrypt media control messages sent to the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - ii) shall decrypt media control messages received from the non-controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+4. in an on-network private call:
+
+- A) if protection of floor control messages between the IWF performing the controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+  - i) shall encrypt floor control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - ii) shall decrypt floor control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+- B) if protection of media control messages between the IWF performing the controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the controlling role:
+  - i) shall encrypt media control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+  - ii) shall decrypt media control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2.
+
+### 13.3.5 The IWF performing the non-controlling role
+
+The IWF performing the non-controlling role:
+
+- 1. if protection of media is negotiated, shall be transparent to RTP media streams and shall forward encrypted RTP media streams without decrypting the payload;
+- 2. if protection of floor control messages between the IWF performing the non-controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the non-controlling role:
+  - A) shall encrypt floor control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) shall decrypt floor control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+- 3. if protection of floor control messages between the IWF performing the non-controlling role and the controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the non-controlling role:
+  - A) shall encrypt floor control messages sent to the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+  - B) shall decrypt floor control messages received from the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2;
+- 4) if protection of media control messages between the IWF performing the non-controlling role and the participating MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the non-controlling role:
+  - A) shall encrypt media control messages sent to the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+
+- B) shall decrypt media control messages received from the participating MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+- 5) if protection of media control messages between the IWF performing the non-controlling role and the controlling MCPTT function is negotiated and the SPK and the SPK-ID are configured in the IWF, then the IWF performing the non-controlling role:
+    - A) shall encrypt media control messages sent to the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2; and
+    - B) shall decrypt media control messages received from the controlling MCPTT function according to IETF RFC 3711 [16] and 3GPP TS 33.180 [18] using SRTP-MK, SRTP-MS and SRTP-MKI generated using the SPK and SPK-ID as specified in clause 13.2.
+
+---
+
+## 14 SDP offer/ answer procedures
+
+### 14.1 General
+
+The IWF shall operate per 3GPP TS 24.380 [25] clause 14.1.
+
+### 14.2 Generating an SDP offer
+
+The IWF shall generate an SDP offer per 3GPP TS 24.380 [25] clause 14.2.
+
+### 14.3 Generating the SDP answer
+
+The IWF shall generate an SDP answer per 3GPP TS 24.380 [25] clause 14.3.
+
+### 14.4 Offeror processing of the SDP answer
+
+The IWF shall process an SDP answer per 3GPP TS 24.380 [25] clause 14.4.
+
+### 14.5 Modifying the media plane control channel
+
+The IWF shall support modification of the media plane control channel per 3GPP TS 24.380 [25] clause 14.5.
+
+### 14.6 The use of SDP offer / answer procedures in off-network mode
+
+The use of SDP offer / answer procedures in off-network mode is not applicable to the IWF.
+
+## Annex A (informative): Change history
+
+| Change history |         |           |    |     |     |                                                                                                                                                                                                      |             |
+|----------------|---------|-----------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR | Rev | Cat | Subject/Comment                                                                                                                                                                                      | New version |
+| 2019-05        |         |           |    |     |     | Initial version                                                                                                                                                                                      | 0.0.0       |
+| 2019-05        |         |           |    |     |     | Contains agreed P-CRs from CT1#117: C1-193602<br>C1-193273, C1-193644, C1-193645, C1-193647, C1-193648,<br>C1-193650, C1-193651, C1-193653, C1-193656, C1-193657,<br>C1-193678, C1-193679, C1-193681 | 0.1.0       |
+| 2019-08        |         |           |    |     |     | Contains agreed P-CRs from CT1#119: C1-194210, C1-194212,<br>C1-194213, C1-194805, C1-194806, C1-194807, C1-194808,<br>C1-194809, C1-194811, C1-194812                                               | 0.2.0       |
+| 2019-09        | CT#85   | CP-192084 |    |     |     | Presentation for information at TSG CT                                                                                                                                                               | 1.0.0       |
+| 2019-10        |         |           |    |     |     | Contains agreed P-CRs from CT1#120: C1-196629, C1-196818,<br>C1-196819                                                                                                                               | 1.1.0       |
+| 2019-12        | CT#86   | CP-193162 |    |     |     | Presentation for approval at TSG CT                                                                                                                                                                  | 2.0.0       |
+| 2019-12        | CT#86   | CP-193297 |    |     |     | A title updated                                                                                                                                                                                      | 2.0.1       |
+| 2019-12        | CT#86   |           |    |     |     | Version 16.0.0 created after approval                                                                                                                                                                | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29388/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29388/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c098a7358516e499b2ee04d9ea963d1e3ae9ccc0
--- /dev/null
+++ b/marked/Rel-16/29_series/29388/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b42d0e749df1882863c13a7dbf79c6c5ef42cdf1c8ae2f5e39d9e6ce3482e430
+size 9613
diff --git a/marked/Rel-16/29_series/29388/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29388/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3f00881c49ab5ac402a64cb89fb71bf7266d43b
--- /dev/null
+++ b/marked/Rel-16/29_series/29388/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b45d31bfa82b865a03925111f9ff056e69d14b5fdebac19b29a5068e7069690d
+size 6492
diff --git a/marked/Rel-16/29_series/29388/raw.md b/marked/Rel-16/29_series/29388/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c28b2cf5e870eea799d63bd5be7cea66e04ebc8
--- /dev/null
+++ b/marked/Rel-16/29_series/29388/raw.md
@@ -0,0 +1,1033 @@
+
+
+# 3GPP TS 29.388 V16.0.0 (2020-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; V2X Control Function to Home Subscriber Server (HSS) aspects (V4); Stage 3 (Release 16)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is a green signal icon with three bars. To the right of the 'e' are the words 'Advanced Pro' in a smaller font. A small 'TM' symbol is at the bottom right of the 'e'.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. The '3' and 'G' are connected at the top. Below the 'P' is a red signal icon with three bars. To the right of the 'P' is a small 'TM' symbol. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                |    |
+|----------------------------------------------------------------|----|
+| Foreword .....                                                 | 5  |
+| 1 Scope.....                                                   | 6  |
+| 2 References.....                                              | 6  |
+| 3 Definitions and abbreviations .....                          | 7  |
+| 3.1 Definitions.....                                           | 7  |
+| 3.2 Abbreviations .....                                        | 7  |
+| 4 General Description .....                                    | 7  |
+| 4.1 Introduction .....                                         | 7  |
+| 5 Procedure Description.....                                   | 7  |
+| 5.1 Introduction .....                                         | 7  |
+| 5.2 V2X Subscriber Information Retrieval .....                 | 8  |
+| 5.2.1 General .....                                            | 8  |
+| 5.2.2 Detailed Behaviour of the V2X Control Function .....     | 8  |
+| 5.2.3 Detailed Behaviour of the HSS .....                      | 9  |
+| 5.3 Update V2X Subscriber Data.....                            | 9  |
+| 5.3.1 General .....                                            | 9  |
+| 5.3.2 Detailed behaviour of the V2X Control Function .....     | 10 |
+| 5.3.3 Detailed behaviour of the HSS .....                      | 11 |
+| 5.4 Notification Procedure .....                               | 11 |
+| 5.4.1 General .....                                            | 11 |
+| 5.4.2 Detailed Behaviour of the V2X Control Function .....     | 12 |
+| 5.4.3 Detailed Behaviour of the HSS .....                      | 12 |
+| 5.5 Reset.....                                                 | 13 |
+| 5.5.1 General .....                                            | 13 |
+| 5.5.2 Detailed behaviour of the V2X Control Function .....     | 13 |
+| 5.5.3 Detailed behaviour of the HSS .....                      | 14 |
+| 6 Protocol Specification and Implementations .....             | 14 |
+| 6.1 Introduction .....                                         | 14 |
+| 6.1.1 Use of Diameter base protocol .....                      | 14 |
+| 6.1.2 Securing Diameter Messages .....                         | 14 |
+| 6.1.3 Accounting Functionality .....                           | 14 |
+| 6.1.4 Use of Sessions.....                                     | 14 |
+| 6.1.5 Transport Protocol.....                                  | 14 |
+| 6.1.6 Routing Considerations .....                             | 15 |
+| 6.1.7 Advertising Application Support.....                     | 15 |
+| 6.1.8 Diameter Application Identifier.....                     | 15 |
+| 6.1.9 Use of the Supported-Features AVP .....                  | 15 |
+| 6.2 Commands.....                                              | 16 |
+| 6.2.1 Introduction .....                                       | 16 |
+| 6.2.2 Command-Code Values.....                                 | 16 |
+| 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command.....  | 16 |
+| 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command .....  | 17 |
+| 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command ..... | 17 |
+| 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command .....  | 18 |
+| 6.2.7 ProSe-Notify-Request (PNR) Command .....                 | 18 |
+| 6.2.8 ProSe-Notify-Answer (PNA) Command.....                   | 18 |
+| 6.2.9 Reset-Request (RSR) Command.....                         | 19 |
+| 6.2.10 Reset-Answer (RSA) Command .....                        | 19 |
+| 6.3 AVPs .....                                                 | 20 |
+| 6.3.1 General .....                                            | 20 |
+| 6.3.2 V2X-Subscription-Data .....                              | 21 |
+| 6.3.3 V2X-PC5-Allowed-PLMN.....                                | 21 |
+| 6.3.4 V2X-Update-Flags .....                                   | 21 |
+
+|                               |                                                         |           |
+|-------------------------------|---------------------------------------------------------|-----------|
+| 6.3.5                         | V2X-Notify-Flags.....                                   | 21        |
+| 6.3.6                         | OC-Supported-Features .....                             | 22        |
+| 6.3.7                         | OC-OLR .....                                            | 22        |
+| 6.3.8                         | DRMP.....                                               | 22        |
+| 6.3.9                         | Load.....                                               | 22        |
+| 6.3.10                        | PLMN-Allowed-PC5-RATs.....                              | 22        |
+| 6.3.11                        | PC5-RAT-Type .....                                      | 22        |
+| 6.4                           | Result-Code AVP and Experimental-Result AVP Values..... | 23        |
+| 6.4.1                         | General .....                                           | 23        |
+| 6.4.2                         | Success .....                                           | 23        |
+| 6.4.3                         | Permanent Failures .....                                | 23        |
+| 6.4.3.1                       | General.....                                            | 23        |
+| 6.4.3.2                       | DIAMETER_ERROR_USER_UNKNOWN (5001) .....                | 23        |
+| 6.4.3.3                       | DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION (5690) .....    | 23        |
+| 6.4.3.4                       | DIAMETER_ERROR_V2X_NOT_ALLOWED (5691).....              | 23        |
+| <b>Annex A (normative):</b>   | <b>Diameter overload control mechanism.....</b>         | <b>24</b> |
+| A.1                           | General .....                                           | 24        |
+| A.2                           | HSS behaviour.....                                      | 24        |
+| A.3                           | V2X Control Function behaviour.....                     | 24        |
+| <b>Annex B (Informative):</b> | <b>Diameter overload node behaviour .....</b>           | <b>25</b> |
+| B.1                           | Message prioritization.....                             | 25        |
+| <b>Annex C (normative):</b>   | <b>Diameter message priority mechanism.....</b>         | <b>26</b> |
+| C.1                           | General .....                                           | 26        |
+| C.2                           | V4 interface .....                                      | 26        |
+| C.2.1                         | General .....                                           | 26        |
+| C.2.2                         | HSS and V2X Control Function behaviour.....             | 26        |
+| D.1                           | General .....                                           | 26        |
+| D.2                           | HSS behaviour.....                                      | 26        |
+| D.3                           | V2X Control Function behaviour.....                     | 27        |
+| <b>Annex E (informative):</b> | <b>Change history .....</b>                             | <b>28</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document describes the Diameter-based V4 interface between the V2X Control Function and the Home Subscriber Server (HSS) defined for V2X services.
+
+This specification defines the Diameter application for V4 reference point between the V2X Control Function and the HSS. The interactions between the V2X Control Function and the HSS are specified.
+
+The stage 2 description for V2X service features in EPS is specified in 3GPP TS 23.285 [2].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.285: "Architecture enhancements for V2X services; Stage 2".
+- [3] IETF RFC 6733: "Diameter Base Protocol".
+- [4] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
+- [5] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
+- [7] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
+- [8] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [9] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements".
+- [10] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol".
+- [11] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol".
+- [12] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [13] IETF RFC 7944: "Diameter Routing Message Priority".
+
+- [14] 3GPP TS 23.007: "Restoration procedures".
+- [15] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects".
+- [16] IETF RFC 8583: "Diameter Load Information Conveyance".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                          |
+|-------|--------------------------|
+| ProSe | Proximity-based Services |
+| V2X   | Vehicle-to-Everything    |
+
+# --- 4 General Description
+
+## 4.1 Introduction
+
+The V4 reference point between the V2X Control Function and the HSS is defined in the 3GPP TS 23.285 [2].
+
+This document describes the V4 interface related procedures, message parameters and protocol specifications.
+
+The V4 interface allows the V2X Control Function to retrieve V2X related subscription data in order to authorise access from the UE for V2X services.
+
+# --- 5 Procedure Description
+
+## 5.1 Introduction
+
+This clause describes the Diameter-based V4 interface related procedures and information elements exchanged between the V2X Control Function and the HSS.
+
+In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [9].
+
+## 5.2 V2X Subscriber Information Retrieval
+
+### 5.2.1 General
+
+This procedure shall be used between the V2X Control Function and the HSS for authorization of the UE for V2X services. The procedure shall be invoked by the V2X Control Function and is used:
+
+- to request V2X related subscription data.
+
+This procedure is mapped to the commands ProSe-Subscriber-Information-Request/Answer (PIR/PIA) in the Diameter application specified in clause 6. Table 5.2.1-1 and table 5.2.1-2 detail the involved information elements.
+
+**Table 5.2.1-1: V2X Subscriber Information Retrieval Request**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                  |
+|---------------------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name (See IETF RFC 6733 [3]) | M    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [8], clause 2.2. |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.        |
+
+**Table 5.2.1-2: V2X Subscriber Information Retrieval Answer**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------------------------|-----------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 6)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol. The Experimental-Result AVP shall be used for V4 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable: <ul style="list-style-type: none"> <li>- User Unknown</li> <li>- Unknown V2X Subscription</li> <li>- V2X Not Allowed</li> </ul> |
+| V2X Subscription Data (See 6.3.2)           | V2X-Subscription-Data             | C    | This information element shall contain the V2X Subscription Data that gives the user permission to use V2X.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| MSISDN (See 3GPP TS 29.329 [11])            | MSISDN                            | C    | This information element shall contain the user MSISDN, formatted according to 3GPP TS 29.329 [11]. It shall be present if available.                                                                                                                                                                                                                                                                                                                                                                                                |
+| Visited PLMN Id (See 3GPP TS 29.272 [10])   | Visited-PLMN-Id                   | C    | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [8]. It shall be present if the UE is roaming in a PLMN different from the Home PLMN.                                                                                                                                                                                                                                                                                                                                           |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Reset-IDs (See 3GPP TS 29.272 [10])         | Reset-ID                          | O    | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers.                                                                                                                                                                                                                                                                                 |
+
+### 5.2.2 Detailed Behaviour of the V2X Control Function
+
+The V2X Control Function shall make use of this procedure to request V2X related subscription data.
+
+If the V2X Control Function retrieved the V2X related subscription data, the V2X Control Function shall perform the authorisation for V2X as described in the 3GPP TS 23.285 [2].
+
+### 5.2.3 Detailed Behaviour of the HSS
+
+When receiving a V2X Subscriber Information Retrieval Request the HSS shall check if the IMSI for whom data is requested exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If the IMSI exists but there is not any V2X subscription data for the IMSI, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_V2X\_SUBSCRIPTION.
+
+If the UE is not allowed to use V2X in the visited PLMN, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_V2X\_NOT\_ALLOWED. Otherwise, the HSS shall return a Result-Code of DIAMETER\_SUCCESS and shall store V2X Control Function identity (the V2X Control Function identity is received within the Origin-Host AVP) and download the V2X subscription data to the V2X Control Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN.
+
+## 5.3 Update V2X Subscriber Data
+
+### 5.3.1 General
+
+The Update V2X Subscriber Data procedure shall be used between the V2X Control Function and the HSS to update the subscriber related data downloaded by means of the V2X Subscriber Information Retrieval operation (see clause 5.2) and stored in the V2X Control Function.
+
+It shall be used to update subscriber related data in the V2X Control Function due to administrative changes of the user data in the HSS, i.e. if the user was given a subscription and the subscription has changed. It shall be used at least to perform the following:
+
+- update of all of V2X subscription data of the subscriber,
+- update of a subset of the V2X subscription data of the subscriber,
+- deletion of the V2X subscription data of the subscriber.
+
+The procedure will also be triggered when the VPLMN has changed.
+
+This procedure is mapped to the commands Update-ProSe-Subscriber-Data-Request/Answer (UPR/UPA) in the Diameter application specified in clause 6.
+
+Table 5.3.1-1 specifies the involved information elements for the request.
+
+Table 5.3.1-2 specifies the involved information elements for the answer.
+
+Table 5.3.1-1: Update V2X Subscriber Data Request
+
+| Information element name                     | Mapping to Diameter AVP            | Cat. | Description                                                                                                                                                                                                                                          |
+|----------------------------------------------|------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMSI                                         | User-Name (See IETF RFC 673 3 [3]) | M    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [8], clause 2.2.                                                                                                                                         |
+| Supported Features (See 3GPP TS 29.2 29 [6]) | Supported-Features                 | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                |
+| V2X Subscription Data (See 6.3.2)            | V2X-Subscription-Data              | C    | This information element shall contain the V2X Subscription Data that gives the user permission to use V2X service.                                                                                                                                  |
+| Visited PLMN Id (See 3GPP TS 29.2 72 [10])   | Visited-PLMN-Id                    | C    | This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPP TS 23.003 [8].<br>It shall be present if the UE is roaming in a PLMN different from the Home PLMN.                                                        |
+| V2X Update Flags (See 6.3.4)                 | V2X-Update-Flags                   | M    | This Information Element shall contain a bit mask. See clause 6.3.6 for the meaning of the bits.                                                                                                                                                     |
+| Reset-IDs (See 3GPP TS 29.2 72 [10])         | Reset-ID                           | O    | The Reset-ID uniquely identifies a fallible resource in the HSS's realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. |
+
+Table 5.3.1-2: Update V2X Subscriber Data Answer
+
+| Information element name                     | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|----------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features (See 3GPP TS 29.2 29 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                      |
+| Result (See 6.4)                             | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol.<br>The Experimental-Result AVP shall be used for V4 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable in this case:<br>- User Unknown<br>- Unknown V2X Subscription |
+
+### 5.3.2 Detailed behaviour of the V2X Control Function
+
+When receiving an Update V2X Subscriber Data request, the V2X Control Function shall check whether the IMSI is known.
+
+If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If it is known, the V2X Control Function shall update the corresponding data according to the indication as sent in the request, and acknowledge the Update V2X Subscriber Data message by returning an Update V2X Subscriber Data Answer. If the V2X-Update-Flags indicates that the V2X subscription data is to be deleted, the V2X Control Function shall delete the associated V2X UE context if it has been stored before.
+
+If the update of the subscription data succeeds in the V2X Control Function, the Result-Code shall be set to DIAMETER\_SUCCESS.
+
+If the V2X Control Function cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. In this case, the V2X Control Function shall mark the subscription record "Subscriber data to be restored in the HSS".
+
+### 5.3.3 Detailed behaviour of the HSS
+
+The HSS shall make use of this procedure to update the relevant subscriber related data in the V2X Control Function to replace a specific part of the user data stored in the V2X Control Function with the data sent.
+
+If the V2X related subscription data is updated or revoked, the HSS sends the updated V2X subscription data to the V2X Control Function. The HSS shall include the V2X-Update-Flags to indicate which part of the data is updated. If all of the V2X subscription data is to be removed, the HSS shall set the "Removal of all V2X Subscription Data" bit of the V2X-Update-Flags, and the HSS shall delete the V2X Control Function Identity if it is stored for this subscriber.
+
+## 5.4 Notification Procedure
+
+### 5.4.1 General
+
+This procedure shall be used between the V2X Control Function and the HSS when the HSS needs to be notified about:
+
+- revocation of authorization for V2X service on one PLMN.
+- removal of the subscription data from the V2X Control Function either by an MMI interaction or automatically.
+
+This procedure is mapped to the commands ProSe-Notify-Request/Answer (PNR/PNA) in the Diameter application specified in clause 6. Table 5.4.1-1 and table 5.4.1-2 detail the involved information elements.
+
+**Table 5.4.1-1: V2X Notify Request**
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                           |
+|---------------------------------------------|-----------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| IMSI                                        | User-Name (See IETF RFC 6733 [3]) | C    | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [8], clause 2.2. It shall be present if the revocation is for a specific UE.                                                                                              |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                 |
+| PLMN ID (see 3GPP TS 29.272 [10])           | Visited-PLMN-Id                   | C    | This information element shall contain the MCC and the MNC of the PLMN where the UE's authorization for V2X service is revoked, see 3GPP TS 23.285 [2]. It shall be present if the V2X Control Function revokes the authorization for V2X service in a specific PLMN. |
+| V2X Notify Flags (see 6.3.5)                | V2X-Notify-Flags                  | C    | This Information Element shall contain a bit mask. See 6.3.7 for the meaning of the bits.                                                                                                                                                                             |
+
+Table 5.4.1-2: V2X Notify Answer
+
+| Information Element Name                    | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|---------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result (See 6)                              | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol.<br>The Experimental-Result AVP shall be used for V4 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- Unknown V2X Subscription |
+| Supported Features (See 3GPP TS 29.229 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                         |
+
+### 5.4.2 Detailed Behaviour of the V2X Control Function
+
+The V2X Control Function shall make use of this procedure to revoke authorization for V2X service.
+
+The V2X Control Function shall make use of this procedure to inform the HSS when the subscription data is deleted from the V2X Function database due to MMI interaction or automatically.
+
+The V2X Control Function shall send the updated V2X Permission and the PLMN ID for which the V2X Permission is to be updated. If the revocation is for a single UE in the indicated PLMN, the V2X Function shall include IMSI in the request.
+
+### 5.4.3 Detailed Behaviour of the HSS
+
+When receiving a V2X Notify Request the HSS shall check if the IMSI, if present in the message, exists in the HSS. If not, an Experimental-Result of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+
+If the IMSI exists but there is not any V2X subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall return an Experimental-Result of DIAMETER\_ERROR\_UNKNOWN\_V2X\_SUBSCRIPTION.
+
+If the V2X-Notify-Flags indicates revocation of authorization for V2X service, and
+
+- if the IMSI exists and there is V2X subscription data for the IMSI and the PLMN ID as indicated by the Visited-PLMN-Id AVP in the request, the HSS shall revoke V2X service as indicated by the VNR Flags received in the request on that PLMN for the user and update the V2X Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS.
+- if IMSI is not present in the message, the HSS shall check if there are any users subscribed to V2X subscription for the PLMN as indicated by the Visited-PLMN-Id AVP in the request, and if yes, revoke V2X service as indicated by the VNR Flags received in the request on that PLMN for all the impacted users and update their V2X Subscription data accordingly. The HSS shall set the result code to DIAMETER\_SUCCESS.
+
+If the VNR Flags indicates the subscription data is deleted from the V2X Control Function, the HSS shall remove the V2X Function Identity for the subscriber and set the result code to DIAMETER\_SUCCESS.
+
+For any other reasons if the HSS cannot fulfil the received request, e.g. due to a database error, it shall set the result code to DIAMETER\_UNABLE\_TO\_COMPLY.
+
+## 5.5 Reset
+
+### 5.5.1 General
+
+The Reset Procedure shall be used by the HSS, after a restart, to indicate to the V2X Control Function that a failure has occurred.
+
+The Reset Procedure may also be used by the HSS as part of operation and maintenance actions e.g. to allow planned HSS outage without service interruption.
+
+This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the Diameter application specified in clause 6.
+
+Table 5.5.1-1 specifies the involved information elements for the request.
+
+Table 5.5.1-2 specifies the involved information elements for the answer.
+
+**Table 5.5.1-1: Reset Request**
+
+| Information element name                        | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                                                                                                                                                                                                           |
+|-------------------------------------------------|-------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| User Id List<br>(See 3GPP TS 29.2 72 [10])      | User-Id                 | O    | This IE shall contain a list of V2X User-Ids where an V2X User-Id comprises the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN) and it shall identify the set of subscribers whose IMSIs begin with the User-Id. The HSS may include this information element if the occurred failure is limited to subscribers identified by one or more User-Ids. |
+| Supported Features<br>(See 3GPP TS 29.2 29 [6]) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                 |
+| Reset-IDs<br>(See 3GPP TS 29.2 72 [10])         | Reset-ID                | O    | If present, this information element identifies together with the HSS's realm the set of impacted subscribers.                                                                                                                                                                                                                                                        |
+
+**Table 5.5.1-2: Reset Answer**
+
+| Information element name                        | Mapping to Diameter AVP           | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|-------------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported Features<br>(See 3GPP TS 29.2 29 [6]) | Supported-Features                | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                        |
+| Result<br>(See 6.4)                             | Result-Code / Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for V4 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>There are no Experimental-Result codes applicable for this command. |
+
+### 5.5.2 Detailed behaviour of the V2X Control Function
+
+When receiving a Reset message the V2X Control Function shall mark all impacted subscriber records "Subscriber Data Confirmed in HSS" as "Not Confirmed", as defined in 3GPP TS 23.007 [14]. If the Reset-IDs IE is supported and received, the V2X Control Function shall make use of the Reset-IDs (together with the HSS's realm) in order to determine which subscriber records are impacted (i.e. check whether at least one received Reset-ID is associated with the subscriber, and the HSS's realm identity received in the Origin-Realm AVP matches the value stored after successful V2X-Subscriber-Information retrieval); otherwise the V2X Control Function shall make use of the HSS
+
+Identity received in the Origin-Host AVP (by comparing it with the value stored after successful V2X-Subscriber-Information retrieval) and may make use of the received User-Id-List (if any) in order to determine which subscriber records are impacted.
+
+### 5.5.3 Detailed behaviour of the HSS
+
+The HSS shall make use of this procedure in order to indicate to all relevant V2X Control Functions that the HSS has restarted and may have lost the current V2X Control Function Identity of some of its subscribers who may be currently roaming in the V2X Control Function Area and that the HSS, therefore, cannot send an Update V2X Subscriber Data messages when needed.
+
+If the Reset-ID feature is not supported by the V2X Control Function and the HSS, the HSS may include a list of User Ids identifying a subset of subscribers served by the HSS, if the occurred failure is limited to those subscribers.
+
+If the Reset-ID feature is supported by the V2X Control Function, the HSS optionally may include one (or several) Reset-ID AVPs identifying e.g. failed hardware components if the occurred failure is limited to those subscribers associated with e.g. the identified failed hardware components.
+
+# --- 6 Protocol Specification and Implementations
+
+## 6.1 Introduction
+
+### 6.1.1 Use of Diameter base protocol
+
+The Diameter Base Protocol as specified in IETF RFC 6733 [3] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified as specified in IETF RFC 6733 [3].
+
+### 6.1.2 Securing Diameter Messages
+
+For secure transport of Diameter messages, see 3GPP TS 33.210 [4].
+
+### 6.1.3 Accounting Functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the V4 interface.
+
+### 6.1.4 Use of Sessions
+
+Between the V2X Control Function and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.
+
+The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [3]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+### 6.1.5 Transport Protocol
+
+Diameter messages over the V4 interface shall make use of SCTP, see IETF RFC 4960 [5].
+
+### 6.1.6 Routing Considerations
+
+This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
+
+The V4 reference point is defined as an intra-operator interface, and both the V2X Control Function and the HSS are located in the home PLMN of the UE that requests V2X. If the V2X Control Function knows the address/name of the HSS for a certain user, both the Destination-Realm and Destination-Host AVPs shall be present in the request. Otherwise, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by the V2X Control Function.
+
+The HSS obtains the Destination-Host AVP to use in requests towards the V2X Control Function, from the Origin-Host AVP received in previous requests from the V2X Control Function. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the HSS.
+
+If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes.
+
+### 6.1.7 Advertising Application Support
+
+The V2X Control Function and the HSS shall advertise support of the Diameter V4 Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [3].
+
+### 6.1.8 Diameter Application Identifier
+
+The V4 interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the V4 interface application is 16777355 (allocated by IANA).
+
+### 6.1.9 Use of the Supported-Features AVP
+
+When new functionality is introduced on the V4 interface, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the V4 interface is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [6].
+
+When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+## 6.2 Commands
+
+### 6.2.1 Introduction
+
+This clause defines the Command code values and related ABNF for each command described in this specification.
+
+### 6.2.2 Command-Code Values
+
+This clause defines Command-Code values for the V4 interface application as allocated by IANA.
+
+Every command is defined by means of the ABNF syntax IETF RFC 5234 [7], according to the rules in IETF RFC 6733 [3]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [3] shall apply.
+
+The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
+
+NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [3].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.2.2-1: Command-Code values for V4**
+
+| Command-Name                         | Abbreviation | Code    | Clause |
+|--------------------------------------|--------------|---------|--------|
+| ProSe-Subscriber-Information-Request | PIR          | 8388664 | 6.2.3  |
+| ProSe-Subscriber-Information-Answer  | PIA          | 8388664 | 6.2.4  |
+| Update-ProSe-Subscriber-Data-Request | UPR          | 8388665 | 6.2.5  |
+| Update-ProSe-Subscriber-Data-Answer  | UPA          | 8388665 | 6.2.6  |
+| ProSe-Notify-Request                 | PNR          | 8388666 | 6.2.7  |
+| ProSe-Notify-Answer                  | PNA          | 8388666 | 6.2.8  |
+| Reset-Request                        | RSR          | 322     | 6.2.9  |
+| Reset-Answer                         | RSA          | 322     | 6.2.10 |
+
+For these commands, the Application-ID field shall be set to 16777355 (application identifier of the V4 interface application, allocated by IANA).
+
+### 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command
+
+The ProSe-Subscriber-Information-Request (PIR) command, indicated by the Command-Code field set to 8388664 and the "R" bit set in the Command Flags field, is sent from the V2X Control Function to the HSS. The ProSe-Subscriber-Information-Request (PIR) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+< ProSe-Subscriber-Information-Request > ::= < Diameter Header: 8388664, REQ, PXY, 16777355 >
+  < Session-Id >
+  [ DRMP ]
+  [ Vendor-Specific-Application-Id ]
+  { Auth-Session-State }
+  { Origin-Host }
+  { Origin-Realm }
+  [ Destination-Host ]
+  { Destination-Realm }
+  { User-Name }
+```
+
+```
+
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+*[ AVP ]
+
+```
+
+### 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command
+
+The ProSe-Subscriber-Information-Answer (PIA) command, indicated by the Command-Code field set to 8388664 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the V2X Control Function. The ProSe-Subscriber-Information-Answer (PIA) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+
+< ProSe-Subscriber-Information-Answer > ::= < Diameter Header: 8388664, PXY, 16777355 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ V2X-Subscription-Data ]
+[ MSISDN ]
+[ Visited-PLMN-Id ]
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+*[ Reset-ID ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command
+
+The Update-ProSe-Subscriber-Data-Request (UPR) command, indicated by the Command-Code field set to 8388665 and the 'R' bit set in the Command Flags field, is sent from the HSS to the V2X Control Function. The Update-ProSe-Subscriber-Data-Request (UPR) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+
+< Update-ProSe-Subscriber-Data-Request > ::= < Diameter Header: 8388665, REQ, PXY, 16777355 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+{ Destination-Host }
+{ Destination-Realm }
+{ User-Name }
+*[ Supported-Features ]
+[ V2X-Subscription-Data ]
+[ Visited-PLMN-Id ]
+{ V2X-Update-Flags }
+*[ Reset-ID ]
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command
+
+The Update-ProSe-Subscriber-Data-Answer (UPA) command, indicated by the Command-Code field set to 8388665 and the 'R' bit cleared in the Command Flags field, is sent from the V2X Control Function to the HSS. The Update-ProSe-Subscriber-Data-Answer (UPA) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+< Update-ProSe-Subscriber-Data-Answer > ::= < Diameter Header: 8388665, PXY, 16777355 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    *[ Supported-Features ]
+    [ Result-Code ]
+    [ Experimental-Result ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    *[ AVP ]
+    [ Failed-AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.7 ProSe-Notify-Request (PNR) Command
+
+The ProSe-Notify-Request (PNR) command, indicated by the Command-Code field set to 8388666 and the "R" bit set in the Command Flags field, is sent from the V2X Control Function to the HSS. The ProSe-Notify-Request (PNR) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+< ProSe-Notify-Request > ::= < Diameter Header: 8388666, REQ, PXY, 16777355 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    { Auth-Session-State }
+    { Origin-Host }
+    { Origin-Realm }
+    [ Destination-Host ]
+    { Destination-Realm }
+    [ User-Name ]
+    [ Visited-PLMN-Id ]
+    [ V2X-Notify-Flags ]
+    *[ Supported-Features ]
+    [ OC-Supported-Features ]
+    *[ AVP ]
+    *[ Proxy-Info ]
+    *[ Route-Record ]
+```
+
+### 6.2.8 ProSe-Notify-Answer (PNA) Command
+
+The ProSe-Notify-Answer (PNA) command, indicated by the Command-Code field set to 8388666 and the "R" bit cleared in the Command Flags field, is sent from the HSS to the V2X Control Function. The ProSe-Notify-Answer (PNA) is originally defined in 3GPP TS 29.344 [15].
+
+Message Format when used over the V4 application:
+
+```
+< ProSe-Notify-Answer > ::= < Diameter Header: 8388666, PXY, 16777355 >
+    < Session-Id >
+    [ DRMP ]
+    [ Vendor-Specific-Application-Id ]
+    [ Result-Code ]
+```
+
+```
+
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+[ OC-OLR ]
+*[ Load ]
+*[ AVP ]
+[ Failed-AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+
+```
+
+### 6.2.9 Reset-Request (RSR) Command
+
+The Reset-Request (RSR) command, indicated by the Command-Code field set to 322 and the 'R' bit set in the Command Flags field, is sent from HSS to the V2X Control Function.
+
+Message Format when used over the V4 application:
+
+```
+
+< Reset-Request > ::= < Diameter Header: 322, REQ, PXY, 16777355 >
+                      < Session-Id >
+                      [ DRMP ]
+                      [ Vendor-Specific-Application-Id ]
+                      { Origin-Host }
+                      { Origin-Realm }
+                      { Destination-Host }
+                      { Destination-Realm }
+                      *[ Supported-Features ]
+                      *[ User-Id ]
+                      *[ Reset-ID ]
+                      *[ AVP ]
+                      *[ Proxy-Info ]
+                      *[ Route-Record ]
+
+```
+
+### 6.2.10 Reset-Answer (RSA) Command
+
+The Reset-Answer (RSA) command, indicated by the Command-Code field set to 322 and the 'R' bit cleared in the Command Flags field, is sent from V2X Control Function to HSS.
+
+Message Format when used over the V4 application:
+
+```
+
+< Reset-Answer > ::= < Diameter Header: 322, PXY, 16777355 >
+                    < Session-Id >
+                    [ DRMP ]
+                    [ Vendor-Specific-Application-Id ]
+                    *[ Supported-Features ]
+                    [ Result-Code ]
+                    [ Experimental-Result ]
+                    { Auth-Session-State }
+                    { Origin-Host }
+                    { Origin-Realm }
+                    *[ AVP ]
+                    [ Failed-AVP ]
+                    *[ Proxy-Info ]
+                    *[ Route-Record ]
+
+```
+
+## 6.3 AVPs
+
+### 6.3.1 General
+
+The following table specifies the Diameter AVPs defined for the V4 interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).
+
+**Table 6.3.1-1: V4 specific Diameter AVPs**
+
+| Attribute Name        | AVP Code | Clause defined | Value Type | AVP Flag rules |     |            |          |           |
+|-----------------------|----------|----------------|------------|----------------|-----|------------|----------|-----------|
+|                       |          |                |            | Must           | May | Should not | Must not | May Encr. |
+| V2X-PC5-Allowed-PLMN  | 4600     | 6.3.3          | Grouped    | M,V            |     |            |          | No        |
+| V2X-Update-Flags      | 4601     | 6.3.4          | Unsigned32 | M,V            |     |            |          | No        |
+| V2X-Notify-Flags      | 4602     | 6.3.5          | Unsigned32 | M,V            |     |            |          | No        |
+| PLMN-Allowed-PC5-RATs | 4603     | 6.3.10         | Grouped    | V              |     |            | M        | No        |
+| PC5-RAT-Type          | 4604     | 6.3.11         | Enumerated | V              |     |            | M        | No        |
+
+NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [3].
+
+NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
+
+The following table specifies the Diameter AVPs re-used by the V4 interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within V4.
+
+Any other AVPs from existing Diameter Applications, except for the AVPs from the Diameter base protocol, do not need to be supported. The AVPs from the Diameter base protocol are not included in table 6.3.1-2, but they may be re-used for the V4 protocol.
+
+**Table 6.3.1-2: V4 re-used Diameter AVPs**
+
+| Attribute Name        | Reference           | Comments          | M-bit        |
+|-----------------------|---------------------|-------------------|--------------|
+| V2X-Subscription-Data | 3GPP TS 29.272 [10] | See clause 6.3.2. |              |
+| Visited-PLMN-Id       | 3GPP TS 29.272 [10] |                   |              |
+| User-Name             | IETF RFC 6733 [3]   |                   |              |
+| User-Id               | 3GPP TS 29.272 [10] |                   |              |
+| Reset-ID              | 3GPP TS 29.272 [10] |                   |              |
+| MSISDN                | 3GPP TS 29.329 [11] |                   |              |
+| Supported-Features    | 3GPP TS 29.229 [6]  |                   |              |
+| Feature-List-ID       | 3GPP TS 29.229 [6]  |                   |              |
+| Feature-List          | 3GPP TS 29.229 [6]  |                   |              |
+| OC-Supported-Features | IETF RFC 7683 [12]  | See clause 6.3.6  | Must set     |
+| OC-OLR                | IETF RFC 7683 [12]  | See clause 6.3.7  | Must set     |
+| DRMP                  | IETF RFC 7944 [13]  | See clause 6.3.8  | Must not set |
+| Load                  | IETF RFC 8583 [16]  | See clause 6.3.9  | Must not set |
+
+NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies.
+
+NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.
+
+### 6.3.2 V2X-Subscription-Data
+
+The V2X-Subscription-Data AVP is of type Group. It shall contain the V2X related subscription data. The V2X-Subscription-Data is originally defined in 3GPP TS 29.272 [10].
+
+AVP format when used over V4 interface:
+
+```
+V2X-Subscription-Data ::= <AVP header: 1688 10415>
+    [ V2X-PC5-Allowed-PLMN ]
+    *[AVP]
+```
+
+### 6.3.3 V2X-PC5-Allowed-PLMN
+
+The V2X-PC5-Allowed-PLMN AVP is of type Grouped. It shall contain the PLMN where the UE is authorised to use V2X communication over PC5, and for each indicated PLMN, the RAT(s) over which the UE is authorized to perform V2X communication over PC5 reference point.
+
+AVP format
+
+```
+V2X-PC5-Allowed-PLMN ::= <AVP header: 4600 10415>
+    *[ Visited-PLMN-Id ]
+    *[ PLMN-Allowed-PC5-RATs ]
+    *[AVP]
+```
+
+If the Visited-PLMN-Id AVP is absent, the PLMN-Allowed-PC5-RATs AVP shall be absent.
+
+### 6.3.4 V2X-Update-Flags
+
+The V2X-Update-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 6.3.4-1:
+
+**Table 6.3.4-1: V2X-Update-Flags**
+
+| Bit   | Name                                                                                                                    | Description                                                                            |
+|-------|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|
+| 0     | Update                                                                                                                  | This bit, when set, indicates that the V2X subscriber related data are updated.        |
+| 1     | Removal                                                                                                                 | This bit, when set, indicates that all of the V2X subscriber related data are removed. |
+| 2     | Reset-ID Update                                                                                                         | This bit, when set, indicates that the complete list on Reset-IDs is updated.          |
+| 3     | Reset-ID Removal                                                                                                        | This bit, when set, indicates that the complete list on Reset-IDs is removed.          |
+| NOTE: | Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving V2X Control Function. |                                                                                        |
+
+### 6.3.5 V2X-Notify-Flags
+
+The V2X-Notify-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.5-1:
+
+**Table 6.3.5-1: V2X-Notify-Flags**
+
+| bit                                                                                                                                                    | name                               | Description                                                                                                                                 |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| 0                                                                                                                                                      | V2X communication over PC5 Revoked | This bit, when set, shall indicate to the HSS that the authorization for V2X communication over PC5 is to be revoked on the indicated PLMN. |
+| 1                                                                                                                                                      | Purged UE                          | This bit, when set, shall indicate to the HSS that the subscriber's data has been deleted from the V2X Control Function.                    |
+| NOTE 1: Bits not defined in this table shall be cleared by the sending V2X Control Function and discarded by the receiving HSS.                        |                                    |                                                                                                                                             |
+| NOTE 2: If Purged UE bit is set, all other bits in this table shall be cleared by the sending V2X Control Function and discarded by the receiving HSS. |                                    |                                                                                                                                             |
+
+### 6.3.6 OC-Supported-Features
+
+The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.7 OC-OLR
+
+The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.8 DRMP
+
+The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [13]. This AVP allows the HSS and the V2X Control Function to indicate the relative priority of Diameter messages over the V4 interface.
+
+### 6.3.9 Load
+
+The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [16]. This AVP is used to support Diameter load control mechanism, see Annex D for more information.
+
+### 6.3.10 PLMN-Allowed-PC5-RATs
+
+The PLMN-Allowed-PC5-RATs AVP is of type Grouped. It shall contain the RAT(s) over the indicated PLMN where the UE is authorized to perform V2X communication over PC5 reference point.
+
+AVP format
+
+```
+V2X-PC5-Allowed-PLMN ::= <AVP header: 4603 10415>
+  { Visited-PLMN-Id }
+  1*{ PC5-RAT-Type }
+  *[AVP]
+```
+
+### 6.3.11 PC5-RAT-Type
+
+The PC5-RAT-Type AVP (AVP code 4604) is of type Enumerated, it is used to identify the PC5 radio technology to perform V2X communication over PC5 reference point.
+
+The following values are defined:
+
+LTE (0)
+
+This value shall be used to indicate that the RAT is PC5 LTE.
+
+NR (1)
+
+This value shall be used to indicate that the RAT is PC5 NR.
+
+## 6.4 Result-Code AVP and Experimental-Result AVP Values
+
+### 6.4.1 General
+
+This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification.
+
+### 6.4.2 Success
+
+Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in the Diameter base protocol IETF RFC 6733 [3] shall be applied.
+
+### 6.4.3 Permanent Failures
+
+#### 6.4.3.1 General
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in the Diameter base protocol IETF RFC 6733 [3] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+#### 6.4.3.2 DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+This result code shall be sent by the HSS to indicate that the user identified by the IMSI is unknown. This error code is defined in 3GPP TS 29.229 [6].
+
+#### 6.4.3.3 DIAMETER\_ERROR\_UNKNOWN\_V2X\_SUBSCRIPTION (5690)
+
+This result code shall be sent by the HSS to indicate that no V2X subscription is associated with the IMSI.
+
+#### 6.4.3.4 DIAMETER\_ERROR\_V2X\_NOT\_ALLOWED (5691)
+
+This result code shall be sent by the HSS to indicate that V2X is not allowed to be used in the specific PLMN where the UE is registered.
+
+# --- Annex A (normative): Diameter overload control mechanism
+
+## A.1 General
+
+Diameter overload control mechanism is an optional feature.
+
+IETF RFC 7683 [12] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 7683 [12] on the V4 interface where, when applied, the V2X Control Function shall behave as reacting nodes and the HSS as a reporting node.
+
+## A.2 HSS behaviour
+
+The HSS requests traffic reduction from the V2X Control Function when it is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [12].
+
+The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the V4 interface or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc.
+
+The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means.
+
+## A.3 V2X Control Function behaviour
+
+The V2X Control Function applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [12].
+
+The V2X Control Function achieves requested traffic reduction by implementation specific means. For example, the V2X Control Function may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed.
+
+# Annex B (Informative): Diameter overload node behaviour
+
+## B.1 Message prioritization
+
+This clause describes possible behaviours of the V2X Control Function regarding message prioritisation in an informative purpose.
+
+The V2X Control Function may take the following into account when making throttling decisions:
+
+- Identification of the procedures that can be deferred, so to avoid to drop non deferrable procedures;
+- Prioritisation of certain types of request (e.g. between V2X-Subscriber-Information-Request (PIR) and V2X-Notify-Request (PNR)) according to the context of their use, in particular:
+  - Higher prioritisation for commands that are related to a registered user for a service, so to avoid the interruption of the registered service for the user.
+
+# --- Annex C (normative): Diameter message priority mechanism
+
+## C.1 General
+
+IETF RFC 7944 [13] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation and also abatement decisions when overload control is applied.
+
+## C.2 V4 interface
+
+### C.2.1 General
+
+The Diameter message priority mechanism is an optional feature.
+
+It is recommended to make use of IETF RFC 7944 [13] over the V4 interface of an operator network when the overload control defined in Annex A is applied on this V4 interface.
+
+### C.2.2 HSS and V2X Control Function behaviour
+
+When the HSS and the V2X Control Function support the Diameter message priority mechanism over the V4 interface, the HSS and the V2X Control Function shall comply with IETF RFC 7944 [13]. In particular, when priority is required, the HSS and the V2X Control Function shall include the DRMP AVP indicating a priority level in the requests it sends, and prioritise received requests according to the priority level received within the DRMP AVP. They shall prioritise received answers according to the priority level received within the DRMP AVP if present, otherwise according to the priority level of the corresponding request. They shall include the DRMP AVP in the answer to a received request if the required priority of the answer is different from the one of the request. The HSS and the V2X Control Function decisions for a required priority and for the priority level value are implementation specific.
+
+Diameter requests related to high priority traffic should contain a DRMP AVP with a high priority of which the level value is operator dependent.
+
+## D.1 General
+
+Diameter load control mechanism is an optional feature.
+
+IETF RFC 8583 [16] specifies a Diameter load control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF draft-ietf-dime-load-08 [16] on the V4 interface where, when applied, the V2X Control Function shall behave as reacting node and the HSS as a reporting node.
+
+## D.2 HSS behaviour
+
+The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [16].
+
+The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the V4 interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc.
+
+The HSS determines when to send Load AVPs of type HOST by implementation specific means.
+
+## D.3 V2X Control Function behaviour
+
+When performing next hop Diameter Agent selection for requests that are routed based on realm, the V2X Control Function may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [16].
+
+# Annex E (informative): Change history
+
+| Date    | TSG #     | TSG Doc.  | CR   | Rev | Subject/Comment                                               | New    |
+|---------|-----------|-----------|------|-----|---------------------------------------------------------------|--------|
+| 2016-10 | CT4#74bis |           |      |     | Skeleton, Implementation of C4-165230, C4-165231              | 0.1.0  |
+| 2016-10 | CT4#74bis |           |      |     | Editorial correction to the numbering of clauses              | 0.1.1  |
+| 2016-11 | CT4#75    |           |      |     | Implementation of C4-166239, C4-166242                        | 0.2.0  |
+| 2017-02 | CT4#76    |           |      |     | Implementation of C4-171299, C4-171301, C4-171303, C4-171305. | 0.3.0  |
+| 2017-03 | CT#75     | CP-170014 |      |     | Presented for information and approval                        | 1.0.0  |
+| 2017-03 | CT#75     |           |      |     | 3GPP TS approved in CT#75                                     | 14.0.0 |
+| 2017-06 | CT#76     | CP-171032 | 0001 | 1   | Load Control                                                  | 14.1.0 |
+| 2018-06 | CT#80     | -         | -    | -   | Update to Rel-15 version (MCC)                                | 15.0.0 |
+| 2019-09 | CT#85     | CP-192094 | 0002 | 1   | draft-ietf-dime-load published as RFC 8583                    | 15.1.0 |
+| 2020-06 | CT#88e    | CP-201049 | 0004 | -   | Authorized PLMNs and RATs for V2X                             | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29389/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29389/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c098a7358516e499b2ee04d9ea963d1e3ae9ccc0
--- /dev/null
+++ b/marked/Rel-16/29_series/29389/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b42d0e749df1882863c13a7dbf79c6c5ef42cdf1c8ae2f5e39d9e6ce3482e430
+size 9613
diff --git a/marked/Rel-16/29_series/29389/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29389/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..498eb1effd3de023207c8579eae2d46fb99284d3
--- /dev/null
+++ b/marked/Rel-16/29_series/29389/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:051f116e69a0bb629346cd377bba04f049a03703a2a759cad9f364084a932037
+size 6504
diff --git a/marked/Rel-16/29_series/29389/raw.md b/marked/Rel-16/29_series/29389/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e862c47b768336d874ddef491f392a59fbc9079
--- /dev/null
+++ b/marked/Rel-16/29_series/29389/raw.md
@@ -0,0 +1,683 @@
+
+
+# 3GPP TS 29.389 V16.0.0 (2020-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Inter-V2X Control Function Signalling aspects (V6); Stage 3 (Release 16)**
+
+![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is the text 'Advanced Pro' in a smaller font. To the right of the 'e' is a green signal icon with three bars.
+
+LTE Advanced Pro logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon with three bars. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, uppercase font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                         |           |
+|-------------------------------------------------------------------------|-----------|
+| Foreword .....                                                          | 5         |
+| 1 Scope.....                                                            | 6         |
+| 2 References.....                                                       | 6         |
+| 3 Definitions and abbreviations .....                                   | 7         |
+| 3.1 Definitions.....                                                    | 7         |
+| 3.3 Abbreviations .....                                                 | 7         |
+| 4 General Description .....                                             | 7         |
+| 4.1 Introduction .....                                                  | 7         |
+| 5 Procedure Description.....                                            | 7         |
+| 5.1 Introduction .....                                                  | 7         |
+| 5.2 V2X Service Authorization.....                                      | 8         |
+| 5.2.1 General .....                                                     | 8         |
+| 5.2.2 Detailed behaviour of the V2X Control Function in the HPLMN ..... | 9         |
+| 5.2.3 Detailed behaviour of the V2X Control Function in the VPLMN ..... | 9         |
+| 6 Protocol Specification and Implementations .....                      | 10        |
+| 6.1 Introduction .....                                                  | 10        |
+| 6.1.1 Use of Diameter base protocol .....                               | 10        |
+| 6.1.2 Securing Diameter Messages .....                                  | 10        |
+| 6.1.3 Accounting functionality .....                                    | 10        |
+| 6.1.4 Use of sessions .....                                             | 10        |
+| 6.1.5 Transport protocol .....                                          | 10        |
+| 6.1.6 Routing considerations .....                                      | 10        |
+| 6.1.7 Advertising Application Support.....                              | 11        |
+| 6.1.8 Diameter Application Identifier.....                              | 11        |
+| 6.1.9 Use of the Supported-Features AVP .....                           | 11        |
+| 6.2 Commands.....                                                       | 11        |
+| 6.2.1 Introduction .....                                                | 11        |
+| 6.2.2 Command-Code values .....                                         | 11        |
+| 6.2.3 ProSe-Authorization-Request (PAR) Command.....                    | 12        |
+| 6.2.4 ProSe-Authorization-Answer (PAA) Command .....                    | 12        |
+| 6.3 Information Elements.....                                           | 13        |
+| 6.3.1 General .....                                                     | 13        |
+| 6.3.2 V2X-Authorization-Data .....                                      | 14        |
+| 6.3.3 V2X-Permission-in-VPLMN .....                                     | 14        |
+| 6.3.4 V2X-Application-Server .....                                      | 15        |
+| 6.3.5 Application-Server .....                                          | 15        |
+| 6.3.6 Geographical-Information .....                                    | 15        |
+| 6.3.7 OC-Supported-Features .....                                       | 15        |
+| 6.3.8 OC-OLR .....                                                      | 15        |
+| 6.3.9 DRMP.....                                                         | 15        |
+| 6.3.10 Load.....                                                        | 15        |
+| 6.3.11 PC5-RAT-Type .....                                               | 16        |
+| 6.4 Result-Code AVP and Experimental-Result AVP Values.....             | 16        |
+| 6.4.1 General .....                                                     | 16        |
+| 6.4.2 Success .....                                                     | 16        |
+| 6.4.3 Permanent Failures .....                                          | 16        |
+| 6.4.3.1 General.....                                                    | 16        |
+| 6.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) .....                        | 16        |
+| 6.4.3.3 DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION (5690) .....            | 16        |
+| 6.4.3.4 DIAMETER_ERROR_V2X_NOT_ALLOWED (5691).....                      | 16        |
+| <b>Annex A (normative): Diameter overload control mechanism .....</b>   | <b>17</b> |
+| A.1 General .....                                                       | 17        |
+
+|                               |                                                  |           |
+|-------------------------------|--------------------------------------------------|-----------|
+| A.2                           | Responding V2X Control Function behaviour.....   | 17        |
+| A.3                           | Requesting V2X Control Function behaviour.....   | 17        |
+| <b>Annex B (Informative):</b> | <b>Diameter overload node behaviour .....</b>    | <b>19</b> |
+| B.1                           | Message prioritization.....                      | 19        |
+| <b>Annex C (normative):</b>   | <b>Diameter message priority mechanism .....</b> | <b>20</b> |
+| C.1                           | General .....                                    | 20        |
+| C.2                           | V6 interfaces .....                              | 20        |
+| C.2.1                         | General .....                                    | 20        |
+| C.2.2                         | V2X Control Function behaviour.....              | 20        |
+| D.1                           | General .....                                    | 20        |
+| D.2                           | Responding V2X Control Function behaviour.....   | 20        |
+| D.3                           | Requesting V2X Control Function behaviour.....   | 21        |
+| <b>Annex E (informative):</b> | <b>Change history.....</b>                       | <b>22</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document describes the Diameter-based interfaces between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN (V6 interface).
+
+This specification defines the Diameter application for V6 reference points between the V2X Control Functions. The interactions between the V2X Control Functions are specified.
+
+The stage 2 description for V2X service features in EPS is specified in 3GPP TS 23.285 [2].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.285: "Architecture enhancements for V2X services; Stage 2".
+- [3] IETF RFC 6733: "Diameter Base Protocol".
+- [4] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
+- [5] IETF RFC 4960: "Stream Control Transmission Protocol".
+- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
+- [7] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
+- [8] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [9] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements".
+- [10] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol".
+- [11] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol".
+- [12] IETF RFC 7683: "Diameter Overload Indication Conveyance".
+- [13] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
+
+- [14] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications".
+- [15] IETF RFC 7944: "Diameter Routing Message Priority".
+- [16] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)".
+- [17] 3GPP TS 29.345: "Inter-Proximity-services (ProSe) Function signalling aspects".
+- [18] IETF RFC 8583: "Diameter Load Information Conveyance".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                          |
+|-------|--------------------------|
+| ProSe | Proximity-based Services |
+| V2X   | Vehicle-to-Everything    |
+
+# --- 4 General Description
+
+## 4.1 Introduction
+
+The V6 reference point is defined between a V2X Control Function in the HPLMN and a V2X Control Function in the VPLMN.
+
+The definition of the V6 reference points and related functionalities are given in 3GPP TS 23.285 [2].
+
+As defined in 3GPP TS 23.285 [2], the V6 reference point is used for:
+
+- HPLMN control of service authorization for V2X.
+
+# --- 5 Procedure Description
+
+## 5.1 Introduction
+
+This clause describes the Diameter-based V6 interface related procedures and Information elements exchanged between functional entities.
+
+In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [9].
+
+## 5.2 V2X Service Authorization
+
+### 5.2.1 General
+
+The V2X Service Authorization Procedure shall be used between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN to obtain service authorization information for V2X services. The procedure shall be invoked by the V2X Control Function in the HPLMN of the UE and is used:
+
+- to request service authorization information for V2X related to the UE from the V2X Control Function in the VPLMN;
+- to provide the V2X Control Function in the VPLMN with the UE identity (IMSI or MSISDN) in order to allow to perform charging;
+
+This procedure is mapped to the commands ProSe-Authorization-Request/Answer (PAR/PAA) in the Diameter application specified in clause 6.
+
+Table 5.2.1-1 specifies the involved information elements for the request.
+
+Table 5.2.1-2 specifies the involved information elements for the answer.
+
+**Table 5.2.1-1: V2X Service Authorization Request**
+
+| Information element name                       | Mapping to Diameter AVP | Cat. | Description                                                                                                                                                                         |
+|------------------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UE Identity<br>(See 3GPP TS 29.336 [13])       | User-Identifier         | M    | This information element shall contain either the user IMSI, formatted according to 3GPP TS 23.003 [8], clause 2.2, or the user MSISDN, formatted according to 3GPP TS 29.329 [11]. |
+| PLMN Id<br>(See 3GPP TS 29.272 [10])           | Visited-PLMN-Id         | M    | This IE shall contain the PLMN-Id (3GPP TS 23.003 [8]) of the network in which the V2X Control Function is located.                                                                 |
+| Supported Features<br>(See 3GPP TS 29.229 [6]) | Supported-Features      | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                               |
+
+**Table 5.2.1-2: V2X Service Authorization Answer**
+
+| Information element name                        | Mapping to Diameter AVP              | Cat. | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|-------------------------------------------------|--------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Result<br>(See 6.4)                             | Result-Code /<br>Experimental-Result | M    | This IE shall contain the result of the operation.<br>The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.<br>The Experimental-Result AVP shall be used for V6 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.<br>The following errors are applicable:<br>- User Unknown<br>- Unauthorized Service<br>- Unauthorized Service in this PLMN |
+| Supported Features<br>(See 3GPP TS 29.2 29 [6]) | Supported-Features                   | O    | If present, this information element shall contain the list of features supported by the origin host.                                                                                                                                                                                                                                                                                                                                                                                            |
+| V2X Authorization Data<br>(See 6.3.2)           | V2X-Authorization-Data               | C    | This Information Element shall contain the V2X authorization information of the user. It shall be present if success is reported.                                                                                                                                                                                                                                                                                                                                                                |
+
+### 5.2.2 Detailed behaviour of the V2X Control Function in the HPLMN
+
+The V2X Control Function in the HPLMN shall make use of this procedure to request service authorization information for V2X related to the UE from the V2X Control Function in the VPLMN. The V2X Control Function shall include in the request the UE identity (IMSI or MSISDN) and the PLMN-Id identifying the PLMN of the requesting V2X Control Function.
+
+When receiving a V2X Service Authorization response from the V2X Control Function in the VPLMN, the V2X Control Function in the HPLMN shall check the result code. If it indicates SUCCESS, the V2X Control Function shall merge with its own policy.
+
+### 5.2.3 Detailed behaviour of the V2X Control Function in the VPLMN
+
+When receiving a V2X Service Authorization request, the V2X Control Function in the VPLMN shall, in the following order:
+
+1. Check whether the UE Identity (IMSI or MSISDN) exists. If not, a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned.
+2. Check whether V2X is authorized for this UE Identity. If not, a Result Code of DIAMETER\_ERROR\_UNAUTHORIZED\_SERVICE shall be returned.
+
+If there is an error in any of the above steps then the V2X Control Function shall stop processing the request and shall return the error code specified in the respective step.
+
+If the V2X Control Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to "DIAMETER\_UNABLE\_TO\_COMPLY".
+
+Otherwise, when the UE is authorized to use V2X over PC5 or V2X over MBMS in this PLMN, the V2X Control Function shall include the V2X-Authorization-Data AVP in the response to return V2X permissions and the V2X Application Server information, and shall set the Result Code to "DIAMETER\_SUCCESS".
+
+# 6 Protocol Specification and Implementations
+
+## 6.1 Introduction
+
+### 6.1.1 Use of Diameter base protocol
+
+The Diameter base protocol as specified in IETF RFC 6733 [3] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.
+
+### 6.1.2 Securing Diameter Messages
+
+For secure transport of Diameter messages, see 3GPP TS 33.210 [4].
+
+### 6.1.3 Accounting functionality
+
+Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the V6 interface.
+
+### 6.1.4 Use of sessions
+
+Between the V2X Control Functions, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.
+
+The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.
+
+The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [3]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.
+
+### 6.1.5 Transport protocol
+
+Diameter messages over the V6 interface shall make use of SCTP IETF RFC 4960 [5].
+
+### 6.1.6 Routing considerations
+
+This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.
+
+The Destination-Realm AVP shall contain the network domain name of the targeted V2X Control Function. The network domain name is either known by the sending V2X Control Function or derived from the PLMN-Id of the targeted V2X Control Function to construct the EPC Home Network Realm/Domain, as indicated in 3GPP TS 23.003 [8], clause 19.2.
+
+If a V2X Control Function knows the address/name of the V2X Control Function in charge of a given UE, and the associated network domain name, both the Destination-Realm and Destination-Host AVPs shall be present in the request.
+
+If a V2X Control Function knows only the network domain name, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node.
+
+Consequently, the Destination-Realm AVP is declared as mandatory and the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a V2X Control Function.
+
+If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes.
+
+### 6.1.7 Advertising Application Support
+
+The V2X Control Functions shall advertise support of the Diameter Inter V2X Control Functions Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.
+
+The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [3].
+
+### 6.1.8 Diameter Application Identifier
+
+The Diameter Inter V2X Control Functions Application protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (<http://www.iana.org/assignments/enterprise-numbers>) is 10415.
+
+The Diameter application identifier assigned to the Diameter Inter V2X Control Functions application is 16777356 (allocated by IANA). The Diameter application identifier is used over the V6 interface.
+
+### 6.1.9 Use of the Supported-Features AVP
+
+When new functionality is introduced on the V6 interface, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the V6 interface is consistent with the procedures for the dynamic discovery of supported features as defined in clause 7.2 of 3GPP TS 29.229 [6].
+
+When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF.
+
+As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.
+
+## 6.2 Commands
+
+### 6.2.1 Introduction
+
+This clause defines the Command code values and related ABNF for each command described in this specification.
+
+### 6.2.2 Command-Code values
+
+This csublause defines Command-Code values for the Diameter Inter V2X Control Functions application used over the V6 interface as allocated by IANA.
+
+Every command is defined by means of the ABNF syntax IETF RFC 5234 [7], according to the rules in IETF RFC 6733 [3]. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETF RFC 6733 [3] shall apply.
+
+The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.
+
+NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with IETF RFC 6733 [3].
+
+The following Command Codes are defined in this specification:
+
+**Table 6.2.2-1: Command-Code values for Diameter V2X Inter Control Functions Application**
+
+| Command-Name                | Abbreviation | Code    | Clause |
+|-----------------------------|--------------|---------|--------|
+| ProSe-Authorization-Request | PAR          | 8388668 | 6.2.3  |
+| ProSe-Authorization-Answer  | PAA          | 8388668 | 6.2.4  |
+
+For these commands, the Application-ID field shall be set to 16777356 (application identifier of the Diameter Inter V2X Control Functions interface application, allocated by IANA).
+
+### 6.2.3 ProSe-Authorization-Request (PAR) Command
+
+The ProSe-Authorization-Request (PAR) Command, indicated by the Command-Code field set to 8388668 and the "R" bit set in the Command Flags field, is sent from the V2X Control Function in the HPLMN to the V2X Control Function in the VPLMN. The ProSe-Authorization- Request (PAR) is originally defined in 3GPP TS 29.345 [17].
+
+Message Format when used over the V6 application:
+
+```
+< ProSe-Authorization-Request > ::= < Diameter Header: 8388668, REQ, PXY, 16777356 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+[ Destination-Host ]
+{ Destination-Realm }
+*[ Supported-Features ]
+[ OC-Supported-Features ]
+{ User-Identifier }
+{ Visited-PLMN-Id }
+*[ AVP ]
+*[ Proxy-Info ]
+*[ Route-Record ]
+```
+
+### 6.2.4 ProSe-Authorization-Answer (PAA) Command
+
+The ProSe-Authorization-Answer (PAA) Command, indicated by the Command-Code field set to 8388668 and the "R" bit cleared in the Command Flags field, is sent from the V2X Control Function in the VPLMN to the V2X Control Function in the HPLMN. The ProSe-Authorization- Answer (PAA) is originally defined in 3GPP TS 29.345 [17].
+
+Message Format when used over the V6 application:
+
+```
+< ProSe-Authorization-Answer > ::= < Diameter Header: 8388668, PXY, 16777356 >
+< Session-Id >
+[ DRMP ]
+[ Vendor-Specific-Application-Id ]
+[ Result-Code ]
+[ Experimental-Result ]
+{ Auth-Session-State }
+{ Origin-Host }
+{ Origin-Realm }
+```
+
+\*[ Supported-Features ]  
+ [ OC-Supported-Features ]  
+ [ OC-OLR ]  
+ \*[ Load ]  
+ [ V2X-Authorization-Data ]  
+ \*[ AVP ]  
+ [ Failed-AVP ]  
+ \*[ Proxy-Info ]  
+ \*[ Route-Record ]
+
+## 6.3 Information Elements
+
+### 6.3.1 General
+
+The following table (table 6.3.1-1) specifies the Diameter AVPs defined for the V6 interface, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).
+
+For all AVPs which contain bit masks and are of the type Unsigned32 e.g., PRR-Flags, bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 shall be used.
+
+**Table 6.3.1-1: V6 specific Diameter AVPs**
+
+| Attribute Name                                                                                                                                                                                                                                                                                                                                                                         | AVP Code | Clause defined | Value Type | AVP Flag rules |     |            |          |           |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------|------------|----------------|-----|------------|----------|-----------|
+|                                                                                                                                                                                                                                                                                                                                                                                        |          |                |            | Must           | May | Should not | Must not | May Encr. |
+| V2X-Authorization-Data                                                                                                                                                                                                                                                                                                                                                                 | 4700     | 6.3.2          | Grouped    |                |     |            |          |           |
+| V2X-Permission-in-VPLMN                                                                                                                                                                                                                                                                                                                                                                | 4701     | 6.3.3          | Unsigned32 |                |     |            |          |           |
+| V2X-Application-Server                                                                                                                                                                                                                                                                                                                                                                 | 4702     | 6.3.4          | Grouped    |                |     |            |          |           |
+| NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [3].                                                                                                                                |          |                |            |                |     |            |          |           |
+| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. |          |                |            |                |     |            |          |           |
+
+The following table (table 6.3.1-2) specifies the Diameter AVPs re-used by the V6 interface from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within V6 interface.
+
+Any other AVPs from existing Diameter Applications, except for the AVPs from the Diameter base protocol, do not need to be supported. The AVPs from the Diameter base protocol are not included in table 6.3.1-2.
+
+**Table 6.3.1-2: V6 re-used Diameter AVPs**
+
+| Attribute Name                                                                                                                                                                                                                                                                                                                                                                         | Reference           | Comments          | M-bit        |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|-------------------|--------------|
+| Application-Server                                                                                                                                                                                                                                                                                                                                                                     | 3GPP TS 32.299 [14] | See clause 6.3.5  |              |
+| Geographical-Information                                                                                                                                                                                                                                                                                                                                                               | 3GPP TS 29.272 [10] | See clause 6.3.6  |              |
+| Visited-PLMN-Id                                                                                                                                                                                                                                                                                                                                                                        | 3GPP TS 29.272 [10] |                   |              |
+| User-Identifier                                                                                                                                                                                                                                                                                                                                                                        | 3GPP TS 29.336 [13] |                   |              |
+| User-Name                                                                                                                                                                                                                                                                                                                                                                              | IETF RFC 6733 [3]   |                   |              |
+| MSISDN                                                                                                                                                                                                                                                                                                                                                                                 | 3GPP TS 29.329 [11] |                   |              |
+| Supported-Features                                                                                                                                                                                                                                                                                                                                                                     | 3GPP TS 29.229 [6]  |                   |              |
+| Feature-List-ID                                                                                                                                                                                                                                                                                                                                                                        | 3GPP TS 29.229 [6]  |                   |              |
+| Feature-List                                                                                                                                                                                                                                                                                                                                                                           | 3GPP TS 29.229 [6]  |                   |              |
+| OC-Supported-Features                                                                                                                                                                                                                                                                                                                                                                  | IETF RFC 7683 [12]  | See clause 6.3.7  | Must set     |
+| OC-OLR                                                                                                                                                                                                                                                                                                                                                                                 | IETF RFC 7683 [12]  | See clause 6.3.8  | Must set     |
+| DRMP                                                                                                                                                                                                                                                                                                                                                                                   | IETF RFC 7944 [15]  | See clause 6.3.9  | Must not set |
+| Load                                                                                                                                                                                                                                                                                                                                                                                   | IETF RFC 8583 [18]  | See clause 6.3.10 | Must not set |
+| PC5-RAT-Type                                                                                                                                                                                                                                                                                                                                                                           | 3GPP TS 29.388 [16] | See clause 6.3.11 | Must not set |
+| NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies.                                                                                                                                                     |                     |                   |              |
+| NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. |                     |                   |              |
+
+### 6.3.2 V2X-Authorization-Data
+
+The V2X-Authorization-Data AVP is of type Group. It shall contain the V2X related authorization data.
+
+AVP format
+
+V2X-Authorization-Data ::= <AVP header: 4700 10415>
+
+[ V2X-Permission-in-VPLMN ]
+
+\*[ PC5-RAT-Type ]
+
+\*[ V2X-Application-Server ]
+
+\*[AVP]
+
+If the V2X-Permission-in-VPLMN AVP indicates V2X communication over PC5 Allowed, the PC5-RAT-Type AVPs may be present to indicate allowed PC5 RAT types to perform communication over PC5 reference point.
+
+If the V2X-Permission-in-VPLMN AVP indicates V2X communication over PC5 Allowed and PC5-RAT-Type AVP is absent, it indicates that all the PC5 RAT types (e.g. PC5 LTE, PC5 NR) are allowed to perform V2X communication over PC5 reference point.
+
+### 6.3.3 V2X-Permission-in-VPLMN
+
+The V2X-Permission-in-VPLMN AVP is of type Unsigned32 and it shall contain a bit mask that indicates the permissions for V2X service in the visited PLMN for a user. The meaning of the bits shall be as defined in table 6.3.3-1:
+
+**Table 6.3.3-1: V2X-Permission-in-VPLMN**
+
+| Bit   | Name                                                                                                                                             | Description                                                                                                    |
+|-------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| 0     | V2X communication over PC5 Allowed                                                                                                               | This bit, when set, indicates that the user is allowed to use V2X communication over PC5 in the visited PLMN.  |
+| 1     | V2X communication over MBMS Allowed                                                                                                              | This bit, when set, indicates that the user is allowed to use V2X communication over MBMS in the visited PLMN. |
+| NOTE: | Bits not defined in this table shall be cleared by the V2X Control Function in the VPLMN and discarded by the V2X Control Function in the HPLMN. |                                                                                                                |
+
+### 6.3.4 V2X-Application-Server
+
+The V2X-Application-Server AVP is of type Group. It shall contain the identifier of V2X Application Server (e.g. FQDN or IP address), and may contain a list of served geographical area which are associated with the given V2X Application Server.
+
+AVP format
+
+```
+V2X-Application-Server ::= <AVP header: 4702 10415>
+    { Application-Server }
+    *[ Geographical-Information ]
+    *[AVP]
+```
+
+### 6.3.5 Application-Server
+
+The Application-Server AVP is of type UTF8String which is originally defined in 3GPP TS 32.299 [14]. It shall contain the identifier of V2X Application Server (e.g. FQDN or IP address).
+
+### 6.3.6 Geographical-Information
+
+The Geographical-Information AVP is of type UTF8String which is originally defined in 3GPP TS 29.272 [10]. It shall contain the served geographical area which is associated with a V2X Application Server.
+
+### 6.3.7 OC-Supported-Features
+
+The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.8 OC-OLR
+
+The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [12]. This AVP is used to support Diameter overload control mechanism, see Annex A for more information.
+
+### 6.3.9 DRMP
+
+The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [15]. This AVP allows the V2X Control Function to indicate the relative priority of Diameter messages.
+
+### 6.3.10 Load
+
+The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [18]. This AVP is used to support Diameter load control mechanism, see Annex D for more information.
+
+### 6.3.11 PC5-RAT-Type
+
+The PC5-RAT-Type AVP (AVP code 4604) is of type Enumerated, it is used to indicate the PC5 radio technology to perform V2X communication over PC5 reference point.
+
+It is defined in 3GPP TS 29.388 [16].
+
+## 6.4 Result-Code AVP and Experimental-Result AVP Values
+
+### 6.4.1 General
+
+This clause defines result code values that shall be supported by all Diameter implementations that conform to this specification.
+
+### 6.4.2 Success
+
+Result codes that fall within the Success category shall be used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in the Diameter base protocol IETF RFC 6733 [3] shall be applied.
+
+### 6.4.3 Permanent Failures
+
+#### 6.4.3.1 General
+
+Errors that fall within the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. The Result-Code AVP values defined in the Diameter base protocol IETF RFC 6733 [3] shall be applied. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent.
+
+#### 6.4.3.2 DIAMETER\_ERROR\_USER\_UNKNOWN (5001)
+
+This result code shall be sent by the HSS to indicate that the user identified by the IMSI is unknown. This error code is defined in 3GPP TS 29.229 [6].
+
+#### 6.4.3.3 DIAMETER\_ERROR\_UNKNOWN\_V2X\_SUBSCRIPTION (5690)
+
+This result code shall be sent by the HSS to indicate that no V2X subscription is associated with the IMSI. This error code is defined in 3GPP TS 29.388 [16].
+
+#### 6.4.3.4 DIAMETER\_ERROR\_V2X\_NOT\_ALLOWED (5691)
+
+This result code shall be sent by the HSS to indicate that V2X is not allowed to be used in the specific PLMN where the UE is registered. This error code is defined in 3GPP TS 29.388 [16].
+
+# --- Annex A (normative): Diameter overload control mechanism
+
+## A.1 General
+
+Diameter overload control mechanism is an optional feature.
+
+IETF RFC 7683 [12] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 7683 [12] on the V6 interface where, when applied, the requesting V2X Control Function shall behave as a reacting node and the responding V2X Control Function as a reporting node.
+
+## A.2 Responding V2X Control Function behaviour
+
+The responding V2X Control Function requests traffic reduction from requesting V2X Control Function when it is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [12].
+
+The V2X Control Function identifies that it is in an overload situation by implementation specific means. For example, the V2X Control Function may take into account the traffic over the V6 interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc.
+
+The V2X Control Function determines the specific contents of OC-OLR AVP in overload reports and the V2X Control Function decides when to send OC-OLR AVPs by implementation specific means.
+
+## A.3 Requesting V2X Control Function behaviour
+
+The requesting V2X Control Function applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [12].
+
+Requested traffic reduction is achieved by the requesting V2X Control Function by implementation specific means. For example, it may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed.
+
+
+
+# --- Annex B (Informative): Diameter overload node behaviour
+
+## B.1 Message prioritization
+
+This clause describes possible behaviours of the requesting V2X Control Function receiving an overload indication from the responding V2X Control Function, regarding message prioritisation in an informative purpose.
+
+The message prioritization on V6 interface is not applicable in this release.
+
+# --- Annex C (normative): Diameter message priority mechanism
+
+## C.1 General
+
+IETF RFC 7944 [15] specifies a Diameter routing message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation and also abatement decisions when overload control is applied.
+
+## C.2 V6 interfaces
+
+### C.2.1 General
+
+The Diameter message priority mechanism is an optional feature.
+
+It is recommended to make use of IETF RFC 7944 [15] over the V6 interface of an operator network when the overload control defined in Annex A is applied on the V6 interface.
+
+### C.2.2 V2X Control Function behaviour
+
+When the V2X Control Function supports the Diameter message priority mechanism over the V6 interface, the V2X Control Function shall comply with IETF RFC 7944 [15]. In particular, when priority is required, the V2X Control Function shall include the DRMP AVP indicating a priority level in the requests it sends, and prioritise received requests according to the priority level received within the DRMP AVP. It shall prioritise received answers according to the priority level received within the DRMP AVP if present, otherwise according to the priority level of the corresponding request. It shall include the DRMP AVP in the answer to a received request if the required priority of the answer is different from the one of the request. The V2X Control Function decisions for a required priority and for the priority level value are implementation specific.
+
+Diameter requests related to high priority traffic should contain a DRMP AVP with a high priority of which the level value is operator dependent.
+
+## D.1 General
+
+Diameter load control mechanism is an optional feature.
+
+IETF RFC 8583 [18] specifies a Diameter load control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes.
+
+It is recommended to make use of IETF RFC 8583 [18] on the V6 interface where, when applied, the requesting V2X Control Function shall behave as a reacting node and the responding V2X Control Function as a reporting node.
+
+## D.2 Responding V2X Control Function behaviour
+
+The responding V2X Control Function may report its current load by including a Load AVP of type HOST in answer commands as described in IETF RFC 8583 [18].
+
+The responding V2X Control Function calculates its current load by implementation specific means. For example, the responding V2X Control Function may take into account the traffic over the V6 interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc.
+
+The responding V2X Control Function determines when to send Load AVPs of type HOST by implementation specific means.
+
+## D.3 Requesting V2X Control Function behaviour
+
+When performing next hop Diameter Agent selection for requests that are routed based on realm, the requesting V2X Control Function may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF RFC 8583 [18].
+
+# Annex E (informative): Change history
+
+| Date    | TSG #     | TSG Doc.  | CR   | Rev | Subject/Comment                                              | New    |
+|---------|-----------|-----------|------|-----|--------------------------------------------------------------|--------|
+| 2016-10 | CT4#74bis |           |      |     | Skeleton, implementation of C4-165232, C4-165233             | 0.1.0  |
+| 2016-10 | CT4#74bis |           |      |     | Editorial correction to the numbering of clauses             | 0.1.1  |
+| 2016-11 | CT4#75    |           |      |     | Implementation of C4-166240                                  | 0.2.0  |
+| 2017-02 | CT4#76    |           |      |     | Implementation of C4-171300, C4-171302, C4-171304, C4-171036 | 0.3.0  |
+| 2017-03 | CT#75     | CP-170015 |      |     | Presented for information and approval                       | 1.0.0  |
+| 2017-03 | CT#75     |           |      |     | 3GPP TS approved in CT#75                                    | 14.0.0 |
+| 2017-06 | CT#76     | CP-171032 | 0001 | 1   | Load Control                                                 | 14.1.0 |
+| 2017-06 | CT#76     | CP-171032 | 0002 | 1   | Remove Editor's Note on V2X Charging                         | 14.1.0 |
+| 2018-06 | CT#80     | -         | -    | -   | Update to Rel-15 version (MCC)                               | 15.0.0 |
+| 2019-09 | CT#85     | CP-192094 | 0004 | 1   | draft-ietf-dime-load published as RFC 8583                   | 15.1.0 |
+| 2020-06 | CT#88e    | CP-201049 | 0005 | -   | Authorized PLMNs and RATs for V2X                            | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29515/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/29_series/29515/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f131fd2a99777d82887ef53b888a8e3516977749
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62a6f89971c56966489e6d975cc42900e7f8fdc2e7956f5804d5c55230d3db26
+size 40611
diff --git a/marked/Rel-16/29_series/29515/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-16/29_series/29515/5dfc130b129ace4df375839020a5700d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..62c6506c83bda5efa6ec56ae6b35c302c29e929b
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/5dfc130b129ace4df375839020a5700d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a837dd20f66fc41b712db8770f21ac66517c6ad7134386e88209722e7d7833d
+size 29815
diff --git a/marked/Rel-16/29_series/29515/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29515/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4cbb5140b059bd363563b9e7e1e9917c3b906d2e
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfd2054c531610546579e3459da19418a35413c766e11c71de98d9ef63e86f84
+size 7703
diff --git a/marked/Rel-16/29_series/29515/63e0c22852c26699d0bd095a2d796bab_img.jpg b/marked/Rel-16/29_series/29515/63e0c22852c26699d0bd095a2d796bab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad1e3339e8a2fd99eac51e6369af8a8d9e46ba34
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/63e0c22852c26699d0bd095a2d796bab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:153368753d17e33a70166765996a62105972a79bbba4d0d1191a792d95a1efde
+size 30436
diff --git a/marked/Rel-16/29_series/29515/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29515/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae6b6493863d9ad65401ba78862e15db5e87036b
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d5a5f076bbd31cd4613be2d19e63d3b42ebdd585cd3f796349a37ce61ec6703
+size 5796
diff --git a/marked/Rel-16/29_series/29515/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/marked/Rel-16/29_series/29515/a92b1fdf37a74b707e9f03087c8f1377_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3c4561f350cbb8b4916461d53cc9d9debea3b65
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/a92b1fdf37a74b707e9f03087c8f1377_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:432b6e28006904764744f1a46ebfdc5402e9f1c1853ae244b045214fc5ba76ef
+size 30419
diff --git a/marked/Rel-16/29_series/29515/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/Rel-16/29_series/29515/b0211cee4b20034939d883ac0d70f696_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e3075815b9ea13ba42fa2012b7e21857ac1acf5a
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/b0211cee4b20034939d883ac0d70f696_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:322eb29911ba38f8acc794de2ca4882eba984f1948c5c822e27e6bcc4ec177ec
+size 31014
diff --git a/marked/Rel-16/29_series/29515/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-16/29_series/29515/c036e2540a94b31357ceb0002f0cacab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..043e813641bd4a282ad6512723eb910e4bd50043
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/c036e2540a94b31357ceb0002f0cacab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:248ec78c652304bb9bb4e2bc81ebb4bcd4dda5dda75e06b1d9dda3599af37c1a
+size 31025
diff --git a/marked/Rel-16/29_series/29515/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-16/29_series/29515/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c959d2c83e46d05be4680823aa6a89d51d88f87
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e7db26927c733dad68333e7581dd1089b98068bc013d2a5c95162989472cb169
+size 29261
diff --git a/marked/Rel-16/29_series/29515/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/29_series/29515/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fd6b139e57799d56aa7115ece38f6449a9541a4
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5be0c1fcfa01542fbb42f19d103f190d5f917d6396b8824d2d8e0b586a2ab31
+size 30333
diff --git a/marked/Rel-16/29_series/29515/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/29_series/29515/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..395d0c2eb2c4e1e206e419177613c2b74ddcee09
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:382c6ebd5f3ca08da6cabfbc4d67f7abcd9d24fd5248b78697af54120a7494a5
+size 18131
diff --git a/marked/Rel-16/29_series/29515/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/29_series/29515/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ad72173cbe15cd5c90d0fae5ba39d03d1cf9be05
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b3596c3fbe05b0a6ba3c37bd3e2a7b403a11a2c6b80753e671cd0f509f18941b
+size 26828
diff --git a/marked/Rel-16/29_series/29515/raw.md b/marked/Rel-16/29_series/29515/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb53187b9e98e5e7cb4abd4dc57142885c7a3b6c
--- /dev/null
+++ b/marked/Rel-16/29_series/29515/raw.md
@@ -0,0 +1,2293 @@
+
+
+# 3GPP TS 29.515 V16.7.0 (2021-12)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;  
+Technical Specification Group Core Network and Terminals;  
+5G System;  
+Gateway Mobile Location Services;  
+Stage 3  
+(Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, stylized font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon at its base.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                            |    |
+|------------------------------------------------------------|----|
+| Foreword .....                                             | 5  |
+| 1 Scope.....                                               | 6  |
+| 2 References.....                                          | 6  |
+| 3 Definitions of terms, symbols and abbreviations .....    | 7  |
+| 3.1 Terms.....                                             | 7  |
+| 3.2 Symbols.....                                           | 7  |
+| 3.3 Abbreviations .....                                    | 7  |
+| 4 Overview.....                                            | 7  |
+| 5 Services offered by the GMLC .....                       | 8  |
+| 5.1 Introduction .....                                     | 8  |
+| 5.2 Ngmlc_Location Service.....                            | 8  |
+| 5.2.1 Service Description .....                            | 8  |
+| 5.2.2 Service Operations.....                              | 9  |
+| 5.2.2.1 Introduction.....                                  | 9  |
+| 5.2.2.2 ProvideLocation.....                               | 9  |
+| 5.2.2.2.1 General .....                                    | 9  |
+| 5.2.2.2.2 Provide Location of a single UE .....            | 9  |
+| 5.2.2.2.3 Provide Locations of a group of UEs .....        | 10 |
+| 5.2.2.3 LocationUpdate.....                                | 10 |
+| 5.2.2.3.1 General .....                                    | 10 |
+| 5.2.2.4 CancelLocation .....                               | 11 |
+| 5.2.2.4.1 General .....                                    | 11 |
+| 5.2.2.5 EventNotify.....                                   | 12 |
+| 5.2.2.5.1 General .....                                    | 12 |
+| 5.2.2.5.2 EventNotify for a single UE.....                 | 12 |
+| 5.2.2.5.3 EventNotify for the UEs in a target group .....  | 12 |
+| 5.2.2.6 LocationUpdateNotify .....                         | 13 |
+| 5.2.2.6.1 General .....                                    | 13 |
+| 5.2.2.7 LocationUpdateSubscribe.....                       | 14 |
+| 5.2.2.7.1 General .....                                    | 14 |
+| 6 API Definitions .....                                    | 14 |
+| 6.1 Ngmlc_Location Service API .....                       | 14 |
+| 6.1.1 Introduction .....                                   | 14 |
+| 6.1.2 Usage of HTTP.....                                   | 15 |
+| 6.1.2.1 General.....                                       | 15 |
+| 6.1.2.2 HTTP standard headers.....                         | 15 |
+| 6.1.2.2.1 General .....                                    | 15 |
+| 6.1.2.2.2 Content type .....                               | 15 |
+| 6.1.2.3 HTTP custom headers.....                           | 15 |
+| 6.1.2.3.1 General .....                                    | 15 |
+| 6.1.3 Custom Operations without associated resources ..... | 15 |
+| 6.1.3.1 Overview.....                                      | 15 |
+| 6.1.3.2 Operation: provide-location .....                  | 16 |
+| 6.1.3.2.1 Description .....                                | 16 |
+| 6.1.3.2.2 Operation Definition .....                       | 16 |
+| 6.1.3.3 Operation: cancel-location.....                    | 18 |
+| 6.1.3.3.1 Description .....                                | 18 |
+| 6.1.3.3.2 Operation Definition .....                       | 18 |
+| 6.1.3.4 Operation: location-update .....                   | 19 |
+| 6.1.3.4.1 Description .....                                | 19 |
+| 6.1.3.4.2 Operation Definition .....                       | 19 |
+| 6.1.3.5 Operation: loc-update-subs .....                   | 20 |
+| 6.1.3.5.1 Description .....                                | 20 |
+| 6.1.3.5.2 Operation Definition .....                       | 21 |
+
+|                                                         |                                           |           |
+|---------------------------------------------------------|-------------------------------------------|-----------|
+| 6.1.4                                                   | Notifications .....                       | 22        |
+| 6.1.4.1                                                 | General .....                             | 22        |
+| 6.1.4.2                                                 | Eventnotify.....                          | 22        |
+| 6.1.4.2.1                                               | Description .....                         | 22        |
+| 6.1.4.2.2                                               | Notification Definition .....             | 22        |
+| 6.1.4.2.3                                               | Notification Standard Methods .....       | 22        |
+| 6.1.4.2.3.1                                             | POST .....                                | 22        |
+| 6.1.4.3                                                 | LocationUpdateNotify .....                | 23        |
+| 6.1.4.3.1                                               | Description .....                         | 23        |
+| 6.1.4.3.2                                               | Notification Definition .....             | 23        |
+| 6.1.4.3.3                                               | Notification Standard Methods .....       | 24        |
+| 6.1.4.3.3.1                                             | POST .....                                | 24        |
+| 6.1.5                                                   | Data Model .....                          | 25        |
+| 6.1.5.1                                                 | General .....                             | 25        |
+| 6.1.5.2                                                 | Structured data types.....                | 26        |
+| 6.1.5.2.1                                               | Introduction .....                        | 26        |
+| 6.1.5.2.2                                               | Type: InputData.....                      | 27        |
+| 6.1.5.2.3                                               | Type: LocationData.....                   | 29        |
+| 6.1.5.2.4                                               | Type: CancelLocData.....                  | 31        |
+| 6.1.5.2.5                                               | Type: LocUpdateData .....                 | 32        |
+| 6.1.5.2.6                                               | Type: EventNotifyData .....               | 33        |
+| 6.1.5.2.7                                               | Type: UePrivacyRequirements .....         | 34        |
+| 6.1.5.2.8                                               | Void.....                                 | 34        |
+| 6.1.5.2.9                                               | Type: LocUpdateNotification .....         | 34        |
+| 6.1.5.2.10                                              | Type: LocUpdateSubs.....                  | 35        |
+| 6.1.5.2.11                                              | Type: EventNotifyDataAdditionalInfo ..... | 35        |
+| 6.1.5.2.12                                              | Type: EventNotifyDataExt.....             | 35        |
+| 6.1.5.2.13                                              | Type: AreaEventInfoAddition.....          | 35        |
+| 6.1.5.2.14                                              | Type: AreaEventInfoExt .....              | 36        |
+| 6.1.5.3                                                 | Simple data types and enumerations.....   | 36        |
+| 6.1.5.3.1                                               | Introduction .....                        | 36        |
+| 6.1.5.3.2                                               | Simple data types .....                   | 36        |
+| 6.1.5.3.3                                               | Enumeration: PseudonymIndicator .....     | 36        |
+| 6.1.5.3.4                                               | Enumeration: LocationRequestType.....     | 36        |
+| 6.1.5.3.5                                               | Enumeration: LocationTypeRequested .....  | 37        |
+| 6.1.5.3.6                                               | Enumeration: EventNotifyDataType.....     | 37        |
+| 6.1.5.3.7                                               | Enumeration: FailureCause .....           | 37        |
+| 6.1.5.3.8                                               | Enumeration: SuccessType .....            | 37        |
+| 6.1.6                                                   | Error Handling .....                      | 38        |
+| 6.1.6.1                                                 | General .....                             | 38        |
+| 6.1.6.2                                                 | Protocol Errors .....                     | 38        |
+| 6.1.6.3                                                 | Application Errors.....                   | 38        |
+| 6.1.7                                                   | Feature negotiation .....                 | 38        |
+| 6.1.8                                                   | Security .....                            | 38        |
+| 6.1.9                                                   | HTTP redirection.....                     | 39        |
+| <b>Annex A (normative): OpenAPI specification .....</b> |                                           | <b>40</b> |
+| A.1                                                     | General .....                             | 40        |
+| A.2                                                     | Ngmlc_Location API .....                  | 40        |
+| <b>Annex B (informative): Change history .....</b>      |                                           | <b>50</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Ngmlc Service Based Interface. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the Ngmlc.
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 23.273: "5G System Location Services (LCS)".
+- [5] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [7] OpenAPI Initiative, "OpenAPI 3.0.0 Specification", <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md>.
+- [8] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+- [9] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [10] IETF RFC 7807: "Problem Details for HTTP APIs".
+- [11] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [12] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
+- [13] ITU Recommendation E.164: "The international public telecommunication numbering plan".
+- [14] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
+- [15] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+
+- [16] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [17] 3GPP TS 29.510: "Network Function Repository Services; Stage 3".
+- [18] 3GPP TS 22.071: "Location Services (LCS); Service description; Stage 1".
+- [19] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [20] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
+- [21] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+Void
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                                         |
+|-------|-----------------------------------------|
+| 5GC   | 5G Core Network                         |
+| AMF   | Access and Mobility Management Function |
+| GAD   | Geographical Area Description           |
+| GMLC  | Gateway Mobile Location Centre          |
+| GPSI  | Generic Public Subscription Identifier  |
+| LCS   | Location Services                       |
+| LDR   | Location Deferred Request               |
+| MO-LR | Mobile Originated Location Request      |
+| MT-LR | Mobile Terminated Location Request      |
+| NEF   | Network Exposure Function               |
+| NI-LR | Network Induced Location Request        |
+| NRF   | Network Repository Function             |
+| SUPI  | Subscription Permanent Identifier       |
+
+# --- 4 Overview
+
+The Gateway Mobile Location Centre (GMLC) is the network entity in the 5G Core Network (5GC) supporting Location Services (LCS). Within the 5GC, the GMLC offers services to the AMF, GMLC and NEF via the Ngmlc service based interface (see 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]).
+
+Figure 4-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the GMLC:
+
+![Figure 4-1: Reference model – GMLC. The diagram shows three network functions (AMF, NEF, and GMLC) on the left connected to a central GMLC on the right. The AMF is connected via the NL2 interface, the NEF via the NL5 interface, and the GMLC via the NL3 interface. All three interfaces converge at a point labeled Ngmlc, which is connected to the GMLC.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+```
+
+graph LR
+    AMF[AMF] -- NL2 --> Ngmlc((Ngmlc))
+    NEF[NEF] -- NL5 --> Ngmlc
+    GMLC_L[GMLC] -- NL3 --> Ngmlc
+    Ngmlc --> GMLC_R[GMLC]
+  
+```
+
+Figure 4-1: Reference model – GMLC. The diagram shows three network functions (AMF, NEF, and GMLC) on the left connected to a central GMLC on the right. The AMF is connected via the NL2 interface, the NEF via the NL5 interface, and the GMLC via the NL3 interface. All three interfaces converge at a point labeled Ngmlc, which is connected to the GMLC.
+
+Figure 4-1: Reference model – GMLC
+
+The functionalities supported by the GMLC are listed in clause 4.3.3 of 3GPP TS 23.273 [4].
+
+# 5 Services offered by the GMLC
+
+## 5.1 Introduction
+
+The table 5.1-1 shows the GMLC Services and GMLC Service Operations:
+
+Table 5.1-1: List of GMLC Services
+
+| Service Name   | Service Operations   | Operation Semantics | Example Consumer(s) |
+|----------------|----------------------|---------------------|---------------------|
+| Ngmlc_Location | ProvideLocation      | Request/Response    | H-GMLC, NEF         |
+|                | LocationUpdate       | Request/Response    | AMF, V-GMLC         |
+|                | LocationUpdateNotify | Notify              | NEF                 |
+|                | CancelLocation       | Request/Response    | H-GMLC, NEF         |
+|                | EventNotify          | Notify              | H-GMLC, NEF         |
+
+Table 5.1-2 summarizes the corresponding APIs defined for this specification.
+
+Table 5.1-2: API Descriptions
+
+| Service Name   | Clause | Description            | OpenAPI Specification File  | apiName   | Annex |
+|----------------|--------|------------------------|-----------------------------|-----------|-------|
+| Ngmlc_Location | 6.1    | Ngmlc Location Service | TS29515_Ngmlc_Location.yaml | ngmlc-loc | A.2   |
+
+## 5.2 Ngmlc\_Location Service
+
+### 5.2.1 Service Description
+
+The Ngmlc\_Location service enables an NF to request location determination (current geodetic and optionally civic location) for a target UE. The following are the key functionalities of this NF service.
+
+- Allow the consumer NF to request the current geodetic and optionally civic location of a target UE.
+- Allow the consumer NF to subscribe/unsubscribe the geodetic and optionally civic location of a target UE for some certain events.
+
+- Allow the consumer NF to cancel an on-going periodic or triggered location request of a target UE.
+- Allow the consumer NF to get notified about the geodetic and optionally civic location of a target UE when some certain events are detected.
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+The service operations defined for the Ngmlc\_Location services are as follows:
+
+- ProvideLocation
+- LocationUpdate
+- LocationUpdateSubscribe- LocationUpdateNotify
+- CancelLocation
+- EventNotify
+
+#### 5.2.2.2 ProvideLocation
+
+##### 5.2.2.2.1 General
+
+The following procedures are supported using the "ProvideLocation" service operation:
+
+- Provide Location of a single UE
+- Provide Locations of a group of UEs
+
+##### 5.2.2.2.2 Provide Location of a single UE
+
+The service operation is used during the procedures:
+
+- 5GC-MT-LR Procedure for the commercial location service (see 3GPP TS 23.273 [4], clause 6.1.2)
+- Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1)
+
+The ProvideLocation service operation is invoked by a NF Service Consumer, e.g. a NEF or GMLC, towards the GMLC to request to provide the location information (geodetic location and, optionally, civic location) for a target UE or to subscribe to periodic or triggered deferred location for a target UE. See Figure 5.2.2.2.2-1.
+
+![Sequence diagram showing the interaction between an NF Service Consumer and a GMLC for a ProvideLocation request. The consumer sends a POST request to the GMLC, which responds with either a 200 OK with location data or an error status (4xx/5xx or 3xx).](a92b1fdf37a74b707e9f03087c8f1377_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant GMLC
+    Note left of NF Service Consumer: 
+    NF Service Consumer->>GMLC: 1. POST ../provide-location (InputData)
+    Note right of GMLC: 
+    GMLC-->>NF Service Consumer: 2a. 200 OK (LocationData)
+    Note right of GMLC: 
+    GMLC-->>NF Service Consumer: 2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the interaction between an NF Service Consumer and a GMLC for a ProvideLocation request. The consumer sends a POST request to the GMLC, which responds with either a 200 OK with location data or an error status (4xx/5xx or 3xx).
+
+**Figure 5.2.2.2.2-1: ProvideLocation Request/Response for a target UE**
+
+1. The NF Service Consumer shall send an HTTP POST request to the URI associated with the "provide-location" custom operation. The input parameters for the request (the target UE identification (SUPI or GPSI), required QoS, supported GAD shapes, LCS client type, external Service Identity, Codeword, service coverage, LDR type, serving AMF address, LDR reference) should be included in the HTTP POST request body, H-GMLC Callback URI may be included in the HTTP POST request body to V-GMLC (eventually to AMF) for implicit subscription of EventNotify provided by AMF, and NEF Callback URI may be included in the HTTP POST request body to GMLC/H-GMLC for implicit subscription of EventNotify provided by GMLC/H-GMLC.
+
+- 2a. On success, "200 OK" shall be returned. The response body shall contain the parameters related to the determined position of the UE if any (geodetic position, civic location, positioning methods...).
+
+If geographic area(s) are received in the request for area event, the GMLC (or V-GMLC when roaming) shall convert the received geographic area(s) into a corresponding list of cell and/or tracking area identities when invoking AMF location services.
+
+- 2b On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.2-2 may be returned. For a 4xx/5xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.3.2.2-2.
+
+##### 5.2.2.2.3 Provide Locations of a group of UEs
+
+The service operation is used during the procedures:
+
+- Bulk Operation of LCS Service Request Targeting to Multiple UEs (see 3GPP TS 23.273 [4], clause 6.8)
+
+The ProvideLocation service operation is invoked by a NF Service Consumer, e.g. a NEF, towards the GMLC (e.g. (H)GMLC when roaming) to request to provide the location informations (geodetic location and, optionally, civic location) for a target group of UEs or to subscribe to periodic or triggered deferred location for a target group of UEs. See Figure 5.2.2.2.3-1.
+
+![Sequence diagram showing the interaction between an NF Service Consumer and a GMLC. The NF Service Consumer sends a POST request to the GMLC. The GMLC responds with either a 200 OK (LocationData) or a 4xx (ProblemDetails) or 3xx response.](b0211cee4b20034939d883ac0d70f696_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant GMLC
+    Note left of NF Service Consumer: 
+    NF Service Consumer->>GMLC: 1. POST .../provide-location (InputData)
+    Note right of GMLC: 
+    GMLC-->>NF Service Consumer: 2a. 200 OK (LocationData)
+    GMLC-->>NF Service Consumer: 2b. 4xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the interaction between an NF Service Consumer and a GMLC. The NF Service Consumer sends a POST request to the GMLC. The GMLC responds with either a 200 OK (LocationData) or a 4xx (ProblemDetails) or 3xx response.
+
+**Figure 5.2.2.2.3-1: ProvideLocation Request/Response for a target group**
+
+1. The NF Service Consumer shall send an HTTP POST request to the URI associated with the "provide-location" custom operation. The input parameters the target group indentification (the External Group ID or the Internal Group ID), LCS client type, eventNotificationUri shall be included in the HTTP POST request body, LDR type, LDR reference shall be also included in the request if requesting the deferred LCS service, the required QoS, supported GAD shapes, external Service Identity, service coverage should be included in the request.
+
+GMLC shall translate the target group indentification into the list of the UE identifications which belong to the target group by invoking the related service provided by UDM, then for each UE in the list, GMLC initiates following steps of procedures of the 5GC-MT-LR or Deferred 5GC-MT-LR as defined in 3GPP TS 23.273 [4] clause 6.8.
+
+If geographic area(s) are received in the request for area event, the GMLC (or V-GMLC when roaming) shall convert the received geographic area(s) into a corresponding list of cell and/or tracking area identities when invoking AMF location services.
+
+- 2a. On success, "200 OK" shall be returned. The response body shall contain the success type.
+- 2b On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.2-2 may be returned. For a 4xx/5xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application error listed in Table 6.1.3.2.2-2.
+
+#### 5.2.2.3 LocationUpdate
+
+##### 5.2.2.3.1 General
+
+The service operation is used during the procedure:
+
+- 5GC-MO-LR Procedure (see 3GPP TS 23.273 [4], clause 6.2)
+
+The LocationUpdate enables the NF consumer (e.g. AMF) to update UE location information towards the GMLC. See Figure 5.2.2.3.1-1.
+
+![Sequence diagram for Figure 5.2.2.3.1-1: LocationUpdate Request/Response. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'GMLC' on the right. A solid arrow labeled '1. POST ../location-update (LocUpdateData)' points from the NF Service Consumer to the GMLC. A return arrow from the GMLC to the NF Service Consumer is labeled with two options: '2a. 204 No Content' and '2b. 4xx (ProblemDetails)'.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+```
+sequenceDiagram
+    participant NF Service Consumer
+    participant GMLC
+    Note left of NF Service Consumer: 1. POST ../location-update (LocUpdateData)
+    NF Service Consumer->>GMLC: 1. POST ../location-update (LocUpdateData)
+    Note right of GMLC: 2a. 204 No Content
+    Note right of GMLC: 2b. 4xx (ProblemDetails)
+    GMLC-->>NF Service Consumer: 2a. 204 No Content
+    GMLC-->>NF Service Consumer: 2b. 4xx (ProblemDetails)
+```
+
+Sequence diagram for Figure 5.2.2.3.1-1: LocationUpdate Request/Response. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'GMLC' on the right. A solid arrow labeled '1. POST ../location-update (LocUpdateData)' points from the NF Service Consumer to the GMLC. A return arrow from the GMLC to the NF Service Consumer is labeled with two options: '2a. 204 No Content' and '2b. 4xx (ProblemDetails)'.
+
+**Figure 5.2.2.3.1-1: LocationUpdate Request/Response**
+
+1. The NF Service Consumer shall send an HTTP POST request to the URI associated with the "location-update" custom operation. The request body shall contain a LocUpdateData object..
+- 2a. On success, "204 No content" shall be returned by the GMLC.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.4.2-2 may be returned. For a 4xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.4.2-2.
+
+#### 5.2.2.4 CancelLocation
+
+##### 5.2.2.4.1 General
+
+The service operation is used during the procedure:
+
+- Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.3)
+
+The CancelLocation enables the consumer NF to use the service operation to cancel a deferred 5GC-MT-LR procedure for periodic or triggered location for a single UE or for a group. See Figure 5.2.2.4.1-1.
+
+![Sequence diagram for Figure 5.2.2.4.1-1: CancelLocation Request/Response. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'GMLC' on the right. A solid arrow labeled '1. POST ../cancel-location (CancelLocData)' points from the NF Service Consumer to the GMLC. A return arrow from the GMLC to the NF Service Consumer is labeled with two options: '2a. 204 No Content' and '2b. 4xx(ProblemDetails) or 3xx'.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg)
+
+```
+sequenceDiagram
+    participant NF Service Consumer
+    participant GMLC
+    Note left of NF Service Consumer: 1. POST ../cancel-location (CancelLocData)
+    NF Service Consumer->>GMLC: 1. POST ../cancel-location (CancelLocData)
+    Note right of GMLC: 2a. 204 No Content
+    Note right of GMLC: 2b. 4xx(ProblemDetails) or 3xx
+    GMLC-->>NF Service Consumer: 2a. 204 No Content
+    GMLC-->>NF Service Consumer: 2b. 4xx(ProblemDetails) or 3xx
+```
+
+Sequence diagram for Figure 5.2.2.4.1-1: CancelLocation Request/Response. The diagram shows two lifelines: 'NF Service Consumer' on the left and 'GMLC' on the right. A solid arrow labeled '1. POST ../cancel-location (CancelLocData)' points from the NF Service Consumer to the GMLC. A return arrow from the GMLC to the NF Service Consumer is labeled with two options: '2a. 204 No Content' and '2b. 4xx(ProblemDetails) or 3xx'.
+
+**Figure 5.2.2.4.1-1: CancelLocation Request/Response**
+
+1. The NF Service Consumer shall send an HTTP POST request to the URI associated with the "cancel-location" custom operation. The input parameters for the request ((H-)GMLC contact address, LDR reference number, LMF identification, serving AMF address) should be included in the HTTP POST request body.
+- 2a. On success, "204 No Content" shall be returned.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.2-2 may be returned. For a 4xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.3.2-2.
+
+#### 5.2.2.5 EventNotify
+
+##### 5.2.2.5.1 General
+
+The following procedures are supported using the "EventNotify" service operation:
+
+- EventNotify for a single UE
+- EventNotify for the UEs in a target group
+
+##### 5.2.2.5.2 EventNotify for a single UE
+
+The service operation is used during the procedure:
+
+- Deferred 5GC-MT-LR Procedure for Periodic, Triggered and UE Available Location Events (see 3GPP TS 23.273 [4], clause 6.3.1 or clause 6.3.2)
+
+The EventNotify for a single UE enables the consumer NF (e.g. (H)GMLC, NEF) to get notified about the geodetic and optionally civic location, the completion or activation of deferred location, mobility to a different AMF/MME of a UE with deferred location for a target UE when some certain events are detected. See Figure 5.2.2.5.2-1.
+
+![Sequence diagram showing the EventNotify notification for a single UE. The GMLC sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No Content or a 4xx ProblemDetails or 3xx status code.](63e0c22852c26699d0bd095a2d796bab_img.jpg)
+
+```
+
+sequenceDiagram
+    participant GMLC
+    participant NFSC as NF Service Consumer
+    Note left of GMLC: 1. POST {locationNotificationUri} (EventNotifyData)
+    GMLC->>NFSC: Request
+    Note right of NFSC: 2a. 204 No Content
+    NFSC-->>GMLC: Response 2a
+    Note right of NFSC: 2b. 4xx ProblemDetails or 3xx
+    NFSC-->>GMLC: Response 2b
+  
+```
+
+Sequence diagram showing the EventNotify notification for a single UE. The GMLC sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No Content or a 4xx ProblemDetails or 3xx status code.
+
+**Figure 5.2.2.5.2-1: EventNotify Notification for a single UE**
+
+1. The GMLC shall send an HTTP POST to the locationNotificationUri to send a notification. The input parameters for the notification (Notification Correlation ID, UE (SUPI and if available GPSI), Type of location related event (e.g. deferred location for the UE available event, activation of location for periodic or triggered location, mobility of a target UE to a new AMF or MME for a deferred location, Geodetic Location, Civic Location, Position Methods Used, serving LMF identification etc.) should be included in the HTTP POST request body. The locationNotificationUri shall be set to:
+
+If the notification is sent from (V)GMLC to (H)GMLC when roaming with (V)GMLC used,
+
+- the hgmlcCallBackURI received from the AMF/LMF;
+
+If the notification is sent from (H)GMLC to NEF,
+
+- the callback URI of NEF provided by NEF during requesting the ProvideLocation service operation for the periodic or triggered deferred location for a target UE or ;
+- the callback URI of NEF locally provisioned in the (H)GMLC.
+
+- 2a. If the notification is received, the NF Service Consumer shall reply with the status code 204 indicating the notification is received, in the response message.
+
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.4.2.3.1-2 may be returned. For a 4xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.4.2.3.1-2.
+
+##### 5.2.2.5.3 EventNotify for the UEs in a target group
+
+The service operation is used during the procedure:
+
+- Bulk Operation of LCS Service Request Targeting to Multiple UEs (see 3GPP TS 23.273 [4], clause 6.8)
+
+The EventNotify for the UEs in a target group enables the consumer NF (e.g. NEF) to get notified about the geodetic and optionally civic locations (immediate locations or deferred locations) for the UEs in target group, the failures of requesting location for the UEs in the target group, completion or activation of deferred location for the UEs in the target group. See Figure 5.2.2.5.3-1.
+
+![Sequence diagram showing EventNotify Notification for the UEs in a target group. GMLC sends a POST request to NF Service Consumer, which responds with 204 No Content or an error code.](cab0834804fb031b43865554cc8d06ab_img.jpg)
+
+```
+
+sequenceDiagram
+    participant GMLC
+    participant NF Service Consumer
+    GMLC->>NF Service Consumer: 1. POST {locationNotificationUri} (EventNotifyData)
+    NF Service Consumer-->>GMLC: 2a. 204 No Content
+    NF Service Consumer-->>GMLC: 2b. 4xx ProblemDetails or 3xx
+  
+```
+
+Sequence diagram showing EventNotify Notification for the UEs in a target group. GMLC sends a POST request to NF Service Consumer, which responds with 204 No Content or an error code.
+
+**Figure 5.2.2.5.3-1: EventNotify Notification for the UEs in a target group**
+
+1. The GMLC/(H)GMLC shall send an HTTP POST to the locationNotificationUri to send a notification. The Request body shall contain event report(s) for one or more UEs in the group. The event report for each UE shall include the LDR Reference, UE identifier (SUPI or GPSI), location data (location data for immediate location service request or location data for deferred location service request) or failure cause of positioning. The locationNotificationUri shall be set to:
+  - the callback URI of NEF provided by NEF during requesting the ProvideLocation service operation for a target group of UEs or;
+  - the callback URI of NEF locally provisioned in the GMLC/(H)GMLC.
+- 2a. If the notification is received, the NF Service Consumer shall reply with the status code 204 indicating the notification is received, in the response message.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.4.2.3.1-2 may be returned. For a 4xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.4.2.3.1-2.
+
+#### 5.2.2.6 LocationUpdateNotify
+
+##### 5.2.2.6.1 General
+
+The service operation is used during the procedure:
+
+- 5GC-MO-LR Procedure (see 3GPP TS 23.273 [4], clause 6.2)
+
+The LocationUpdateNotify enables the NF consumer (e.g. NEF) to get notified about the UE location information update. See Figure 5.2.2.6.1-1.
+
+![Sequence diagram showing LocationUpdateNotify Notification. GMLC sends a POST request to NF Service Consumer, which responds with 204 No Content or an error code.](5dfc130b129ace4df375839020a5700d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant GMLC
+    participant NF Service Consumer
+    GMLC->>NF Service Consumer: 1. POST {callbackUri} (LocUpdateNotification)
+    NF Service Consumer-->>GMLC: 2a. 204 No Content
+    NF Service Consumer-->>GMLC: 2b. 4xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing LocationUpdateNotify Notification. GMLC sends a POST request to NF Service Consumer, which responds with 204 No Content or an error code.
+
+**Figure 5.2.2.6.1-1: LocationUpdateNotify Notification**
+
+1. The GMLC shall send an HTTP POST request to the callback URI of the NF consumer (e.g. NEF). The response body shall contain a LocUpdateNotification object.
+
+The callback URI (e.g. NEF address for callback) is locally configured on GMLC or discovered via NRF.
+
+- 2a. On success, "204 No content" shall be returned by the NF consumer.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.4.3.3.1-2 may be returned. For a 4xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.4.3.3.1-2.
+
+#### 5.2.2.7 LocationUpdateSubscribe
+
+##### 5.2.2.7.1 General
+
+This service operation is used by a NF Service Consumer (e.g. NEF) to trigger a subscription to notifications on UE location information update for the 5GC-MO-LR Procedure (see 3GPP TS 23.273 [4], clause 6.2). See Figure 5.2.2.6A.1-1.
+
+NOTE: This service operation is not used by the current stage 2 specifications in 3GPP TS 23.273 [4], i.e. the subscription to notifications on UE location information update is implicit.
+
+![Sequence diagram showing the subscription to UE location information update. An NF service consumer sends a POST request to the GMLC. The GMLC responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (failure/redirection).](c036e2540a94b31357ceb0002f0cacab_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF service consumer
+    participant GMLC
+    Note left of NF service consumer: NF service consumer
+    NF service consumer->>GMLC: 1. POST.../loc-update-subs (LocUpdateSubs)
+    Note right of GMLC: GMLC
+    GMLC-->>NF service consumer: 2a. 204 No Content
+    GMLC-->>NF service consumer: 2b. 4xx / 5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the subscription to UE location information update. An NF service consumer sends a POST request to the GMLC. The GMLC responds with either a 204 No Content (success) or a 4xx/5xx (ProblemDetails) or 3xx (failure/redirection).
+
+Figure 5.2.2.7.1-1: Subscription to UE location information update
+
+1. The NF service consumer (e.g. NEF) sends a POST request to the parent resource, i.e. collection of subscriptions (.../loc-update-subs), to create a subscription to UE location information update for the 5GC-MO-LR Procedure, as provided in LocUpdateSubs information conveyed in the message body.
+- 2a. On success, "204 No content" shall be returned by the GMLC.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.4.2-2 may be returned. For a 4xx/5xx response, the message body may contain a ProblemDetails structure with the "cause" attribute set to one of the application errors listed in Table 6.1.3.4.2-2.
+
+# 6 API Definitions
+
+## 6.1 Ngmlc\_Location Service API
+
+### 6.1.1 Introduction
+
+The Ngmlc\_Location service shall use the Ngmlc\_Location API.
+
+The API URI of the Ngmlc\_Location API shall be:
+
+**{apiRoot}</apiName>/<apiVersion>/**
+
+The request URIs used in HTTP requests from the NF service consumer towards the NF service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [6], i.e.:
+
+**{apiRoot}</apiName>/<apiVersion>/<apiSpecificResourceUriPart>**
+
+with the following components:
+
+- The {apiRoot} shall be set as described in 3GPP TS 29.501 [6].
+- The <apiName> shall be "ngmlc-loc".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.1.2.1 General
+
+HTTP/2, as defined in IETF RFC 7540 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [5].
+
+HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [5].
+
+HTTP/2, as defined in IETF RFC 7540 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [5].
+
+HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [5].
+
+HTTP messages and bodies for the Ngmlc\_Location service shall comply with the OpenAPI [7] specification contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+##### 6.1.2.2.2 Content type
+
+The following content types shall be supported:
+
+- JSON, as defined in IETF RFC 8259 [9], shall be used as content type of the HTTP bodies specified in the present specification as indicated in clause 5.4 of 3GPP TS 29.500 [5].
+- The Problem Details JSON Object (IETF RFC 7807 [10]). The use of the Problem Details JSON object in a HTTP response body shall be signalled by the content type "application/problem+json".
+
+#### 6.1.2.3 HTTP custom headers
+
+##### 6.1.2.3.1 General
+
+The following HTTP custom headers shall be supported:
+
+- 3gpp-Sbi-Message-Priority: See 3GPP TS 29.500 [5], clause 5.2.3.2.2.
+
+This API does not define any new HTTP custom headers.
+
+### 6.1.3 Custom Operations without associated resources
+
+#### 6.1.3.1 Overview
+
+The structure of the custom operation URIs of the Ngmlc\_Location service is shown in Figure 6.1.3.1-1.
+
+![Diagram showing the custom operation URI structure of the Ngmlc_Location API. The root URI is {apiRoot}/ngmlc-loc/<apiVersion>. It branches into four sub-URIs: /provide-location, /cancel-location, /location-update, and /loc-update-subs. Each sub-URI is enclosed in a dashed box.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/ngmlc-loc/<apiVersion>"]
+    Root --- P1["/provide-location"]
+    Root --- P2["/cancel-location"]
+    Root --- P3["/location-update"]
+    Root --- P4["/loc-update-subs"]
+    style P1 stroke-dasharray: 5 5
+    style P2 stroke-dasharray: 5 5
+    style P3 stroke-dasharray: 5 5
+    style P4 stroke-dasharray: 5 5
+  
+```
+
+Diagram showing the custom operation URI structure of the Ngmlc\_Location API. The root URI is {apiRoot}/ngmlc-loc/. It branches into four sub-URIs: /provide-location, /cancel-location, /location-update, and /loc-update-subs. Each sub-URI is enclosed in a dashed box.
+
+**Figure 6.1.3.1-1: Custom operation URI structure of the Ngmlc\_Location API**
+
+Table 6.1.3.1-1 provides an overview of the custom operations and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Custom operations**
+
+| Custom operation URI                              | Mapped HTTP method | Description                                                                                             |
+|---------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------|
+| {apiRoot}/ngmlc-loc/<apiVersion>/provide-location | POST               | Request or Subscribe the geodetic and optionally civic location of a target UE or a target group of UEs |
+| {apiRoot}/ngmlc-loc/<apiVersion>/cancel-location  | POST               | Cancel an on-going periodic or triggered location request of a target UE or a target group of UEs       |
+| {apiRoot}/ngmlc-loc/<apiVersion>/location-update  | POST               | Enable the UE to update UE location information towards the consumer NF                                 |
+| {apiRoot}/ngmlc-loc/<apiVersion>/loc-update-subs  | POST               | Enable a NF service consumer (e.g. NEF) to subscribe to UE location information                         |
+
+#### 6.1.3.2 Operation: provide-location
+
+##### 6.1.3.2.1 Description
+
+This clause will describe the custom operation and what it is used for, and the custom operations URI.
+
+##### 6.1.3.2.2 Operation Definition
+
+The operation shall support the response data structures and response codes specified in tables 6.1.3.2.2-1 and 6.1.3.2.2-2.
+
+Table 6.1.3.2.2-1: Data structures supported by the POST Request Body on this resource
+
+| Data type | P | Cardinality | Description                                          |
+|-----------|---|-------------|------------------------------------------------------|
+| InputData | M | 1           | Input parameters to the "Provide-Location" operation |
+
+Table 6.1.3.2.2-2: Data structures supported by the POST Response Body on this resource
+
+| Data type        | P | Cardinality | Response codes            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+|------------------|---|-------------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| LocationData     | M | 1           | 200 OK                    | <p>This case represents the successful retrieval of the location of the UE or successful subscription of periodic or triggered location of the UE, or represents completely or partially accept of the requesting locations for a target group.</p> <p>Upon success, a response body is returned containing the different parameters of the location data if obtained, such as:</p> <ul style="list-style-type: none"> <li>- Geographic Area</li> <li>- Civic Location</li> <li>- Age of Location</li> <li>- Accuracy of Location</li> <li>- Positioning methods</li> </ul> |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect    | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set.                                                                                                                                                                                                            |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect    | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set.                                                                                                                                                                                                            |
+| ProblemDetails   | O | 0..1        | 403 Forbidden             | <p>The "cause" attribute may be used to indicate one of the following application errors:</p> <ul style="list-style-type: none"> <li>- POSITIONING_DENIED</li> <li>- UNSPECIFIED</li> <li>- UNSUPPORTED_BY_UE</li> <li>- DETACHED_USER</li> </ul> <p>See table 6.1.6.3-1 for the description of these errors.</p>                                                                                                                                                                                                                                                           |
+| ProblemDetails   | O | 0..1        | 500 Internal Server Error | <p>The "cause" attribute may be used to indicate the following application error:</p> <ul style="list-style-type: none"> <li>- POSITIONING_FAILED</li> </ul> <p>See table 6.1.6.3-1 for the description of these errors.</p>                                                                                                                                                                                                                                                                                                                                                |
+| ProblemDetails   | O | 0..1        | 504 Gateway Timeout       | <p>The "cause" attribute may be used to indicate the following application error:</p> <ul style="list-style-type: none"> <li>- UNREACHABLE_USER</li> <li>- PEER_NOT_RESPONDING</li> </ul> <p>See table 6.1.6.3-1 for the description of this error.</p>                                                                                                                                                                                                                                                                                                                     |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [5]).
+
+**Table 6.1.3.2.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+**Table 6.1.3.2.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+#### 6.1.3.3 Operation: cancel-location
+
+##### 6.1.3.3.1 Description
+
+This clause will describe the custom operation and what it is used for, and the custom operation's URI.
+
+##### 6.1.3.3.2 Operation Definition
+
+This operation shall support the request and response data structures and response codes specified in table 6.1.3.3.2-1 and table 6.1.3.3.2-2.
+
+**Table 6.1.3.3.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type     | P | Cardinality | Description                                                                                |
+|---------------|---|-------------|--------------------------------------------------------------------------------------------|
+| CancelLocData | M | 1           | The information is used to cancel deferred 5GC-MT-LR for a single UE or for a group of UE. |
+
+**Table 6.1.3.3.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                      |
+|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | This case represents successful cancellation of location.                                                                                                                                                                                                                                                                                                        |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | The "cause" attribute may be used to indicate one of the following application errors:<br>- UNSPECIFIED<br>- LOCATION_SESSION_UNKNOWN<br><br>See table 6.1.6.3-1 for the description of this error.                                                                                                                                                              |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [5]).
+
+**Table 6.1.3.3.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+**Table 6.1.3.3.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+#### 6.1.3.4 Operation: location-update
+
+##### 6.1.3.4.1 Description
+
+This clause will describe the custom operation and what it is used for, and the custom operation's URI.
+
+##### 6.1.3.4.2 Operation Definition
+
+This operation shall support the request and response data structures and response codes specified in table 6.1.3.4.2-1 and table 6.1.3.4.2-2.
+
+**Table 6.1.3.4.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type     | P | Cardinality | Description                                         |
+|---------------|---|-------------|-----------------------------------------------------|
+| LocUpdateData | M | 1           | Input parameters to the "location-update" operation |
+
+**Table 6.1.3.4.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                      |
+|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | This case represents successful update of location.                                                                                                                                                                                                                                                                                                              |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNSPECIFIED</li> <li>- UNREQUESTED_BY_UE</li> <li>- UNKNOWN_EXTERNAL_CLIENT_OR_AF</li> <li>- UNREACHABLE_EXTERNAL_CLIENT_OR_AF</li> </ul> See table 6.1.6.3-1 for the description of this error.                                 |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [5]).
+
+**Table 6.1.3.4.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+**Table 6.1.3.4.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+#### 6.1.3.5 Operation: loc-update-subs
+
+##### 6.1.3.5.1 Description
+
+This clause will describe the custom operation and what it is used for, and the custom operations URI.
+
+##### 6.1.3.5.2 Operation Definition
+
+The operation shall support the request and response data structures and response codes specified in tables 6.1.3.5.2-1 and 6.1.3.5.2-2.
+
+**Table 6.1.3.5.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type     | P | Cardinality | Description                                                                        |
+|---------------|---|-------------|------------------------------------------------------------------------------------|
+| LocUpdateSubs | M | 1           | Contains the subscription to UE location update information that is to be created. |
+
+**Table 6.1.3.5.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                      |
+|------------------|---|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | This case represents the successful UE location information subscription creation.                                                                                                                                                                                                                                                                               |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | The "cause" attribute may be used to indicate one of the following application errors:<br>- UNSPECIFIED<br>- UNREQUESTED_BY_UE<br><br>See table 6.1.6.3-1 for the description of these errors.                                                                                                                                                                   |
+
+NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply.
+
+**Table 6.1.3.5.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+**Table 6.1.3.5.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                            |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same GMLC or GMLC (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                              |
+
+### 6.1.4 Notifications
+
+#### 6.1.4.1 General
+
+#### 6.1.4.2 Eventnotify
+
+##### 6.1.4.2.1 Description
+
+The EventNotify operation is used to the occurrence of periodic or triggered location event for a target UE to a consumer NF (e.g. (H)GMLC, NEF) or used to report the locations (e.g. the immediate locations or deferred locations) for the UEs in a target group to a consumer NF (e.g. NEF).
+
+##### 6.1.4.2.2 Notification Definition
+
+Call-back URI: {locationNotificationUri}
+
+See clause 5.2.2.5 for the description of how the GMLC obtains the Call-back URI of the NF Service Consumer.
+
+##### 6.1.4.2.3 Notification Standard Methods
+
+###### 6.1.4.2.3.1 POST
+
+This method sends a Location event notify to the NF Service Consumer.
+
+This method shall support the request and response data structures and response codes specified in table 6.1.4.2.3.1-1 and table 6.1.4.2.3.1-2.
+
+**Table 6.1.4.2.3.1-1: Data structures supported by the POST Request Body**
+
+| Data type          | P | Cardinality | Description                                      |
+|--------------------|---|-------------|--------------------------------------------------|
+| EventNotifyDataExt | M | 1           | Input parameters to the "Event Notify" operation |
+
+**Table 6.1.4.2.3.1-2: Data structures supported by the POST Response Body**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | This case represents successful notification of the event.                                                                                                                                                                                                                                                                                                                                                                            |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | The "cause" attribute may be used to indicate one of the following application errors:<br>- UNSPECIFIED<br>- LOCATION_SESSION_UNKNOWN<br><br>See table 6.1.6.3-1 for the description of this error.                                                                                                                                                                                                                                   |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [5]).
+
+**Table 6.1.4.2.3.1-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                    |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected |
+
+**Table 6.1.4.2.3.1-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                    |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected |
+
+#### 6.1.4.3 LocationUpdateNotify
+
+##### 6.1.4.3.1 Description
+
+The LocationUpdateNotify operation is used to deliver the location update for a UE to a consumer NF (e.g. NEF).
+
+##### 6.1.4.3.2 Notification Definition
+
+Call-back URI: {locationUpdateCallbackUri}
+
+##### 6.1.4.3.3 Notification Standard Methods
+
+###### 6.1.4.3.3.1 POST
+
+This method sends a Location update notification to the NF Service Consumer.
+
+This method shall support the request and response data structures and response codes specified in table 6.1.4.3.3.1-1 and table 6.1.4.3.3.1-2.
+
+**Table 6.1.4.3.3.1-1: Data structures supported by the POST Request Body**
+
+| Data type             | P | Cardinality | Description                                                    |
+|-----------------------|---|-------------|----------------------------------------------------------------|
+| LocUpdateNotification | M | 1           | Input parameters to the "LocationUpdateNotification" operation |
+
+**Table 6.1.4.3.3.1-2: Data structures supported by the POST Response Body**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | This case represents successful notification of the event.                                                                                                                                                                                                                                                                                                                                                                            |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+| ProblemDetails   | O | 0..1        | 403 Forbidden          | The "cause" attribute may be used to indicate one of the following application errors: <ul style="list-style-type: none"> <li>- UNSPECIFIED</li> <li>- UNKNOWN_EXTERNAL_CLIENT_OR_AF</li> <li>- UNREACHABLE_EXTERNAL_CLIENT_OR_AF</li> </ul> See table 6.1.6.3-1 for the description of this error.                                                                                                                                   |
+
+NOTE 1: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] other than those specified in the table above also apply, with a ProblemDetails data type when needed (see clause 5.2.7 of 3GPP TS 29.500 [5]).
+
+**Table 6.1.4.3.3.1-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                    |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected |
+
+**Table 6.1.4.3.3.1-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                    |
+|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected |
+
+### 6.1.5 Data Model
+
+#### 6.1.5.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.5.1-1 specifies the data types defined for the Ngmlc\_Location service based interface protocol.
+
+**Table 6.1.5.1-1: Ngmlc\_Location specific Data Types**
+
+| Data type                       | Clause defined | Description                                                                                             | Applicability |
+|---------------------------------|----------------|---------------------------------------------------------------------------------------------------------|---------------|
+| InputData                       | 6.1.5.2.2      | the input parameters in ProvideLocation service operation                                               |               |
+| LocationData                    | 6.1.5.2.3      | the response parameters in ProvideLocation service operation                                            |               |
+| CancelLocData                   | 6.1.5.2.4      | the input parameters in CancelLocation service operation                                                |               |
+| LocUpdateData                   | 6.1.5.2.5      | the input parameters in LocationUpdate service operation                                                |               |
+| EventNotifyData                 | 6.1.5.2.6      | the input parameters for the target UE in EventNotify Notification service operation                    |               |
+| UePrivacyRequirements           | 6.1.5.2.7      | UE privacy requirements from (H)GMLC to the serving AMF or VGMLC(in the roaming case) for the target UE |               |
+| LocUpdateNotification           | 6.1.5.2.9      | Location Update Notification                                                                            |               |
+| LocUpdateSubs                   | 6.1.5.2.10     | UE location information subscription                                                                    |               |
+| AreaEventInfoAddition           | 6.1.5.2.13     | Additional information for Extended Area event information                                              |               |
+| AreaEventInfoExt                | 6.1.5.2.14     | Extended Area Event Information                                                                         |               |
+| ServiceIdentity                 | 6.1.5.3.2      | service identity                                                                                        |               |
+| CodeWord                        | 6.1.5.3.2      | codeword                                                                                                |               |
+| ExternalClientIdIdentification  | 6.1.5.3.2      | external client identification                                                                          |               |
+| E164CountryCodeOfGeographicArea | 6.1.5.3.2      | E.164 country codes for geographic areas                                                                |               |
+| LcsServiceTypeId                | 6.1.5.3.2      | LCS Service Type Id                                                                                     |               |
+| PseudonymIndicator              | 6.1.5.3.3      | It defines if a pseudonym is requested                                                                  |               |
+| LocationRequestType             | 6.1.5.3.4      | NI-LR, MT-LR or MO-LR                                                                                   |               |
+| LocationTypeRequested           | 6.1.5.3.5      | the location type requested by the LCS client                                                           |               |
+| EventNotifyDataType             | 6.1.5.3.6      | the type of event that triggers event notification                                                      |               |
+| EventNotifyDataAdditionalInfo   | 6.1.5.2.11     | Additional information to Event Notify Data                                                             |               |
+| EventNotifyDataExt              | 6.1.5.2.12     | Extended Event Notify Data for UEs of a target group                                                    |               |
+| FailureCause                    | 6.1.5.3.7      | Positioning failure cause                                                                               |               |
+| SuccessType                     | 6.1.5.3.8      | Success Type to indicate full or partial success                                                        |               |
+
+Table 6.1.5.1-2 specifies data types re-used by the Ngmlc\_Location service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Ngmlc\_Location service based interface.
+
+Table 6.1.5.1-2: Ngmlc\_Location re-used Data Types
+
+| Data type                     | Reference           | Comments                  | Applicability |
+|-------------------------------|---------------------|---------------------------|---------------|
+| Gpsi                          | 3GPP TS 29.571 [11] |                           |               |
+| Supi                          | 3GPP TS 29.571 [11] |                           |               |
+| Uri                           | 3GPP TS 29.571 [11] |                           |               |
+| Amfld                         | 3GPP TS 29.571 [11] |                           |               |
+| NfInstanceId                  | 3GPP TS 29.571 [11] |                           |               |
+| ExternalClientType            | 3GPP TS 29.572 [12] |                           |               |
+| LocationQoS                   | 3GPP TS 29.572 [12] |                           |               |
+| LcsQoSClass                   | 3GPP TS 29.572 [12] |                           |               |
+| SupportedGADShapes            | 3GPP TS 29.572 [12] |                           |               |
+| PeriodicEventInfo             | 3GPP TS 29.572 [12] |                           |               |
+| AreaEventInfo                 | 3GPP TS 29.572 [12] |                           |               |
+| MotionEventInfo               | 3GPP TS 29.572 [12] |                           |               |
+| LdrType                       | 3GPP TS 29.572 [12] |                           |               |
+| LdrReference                  | 3GPP TS 29.572 [12] |                           |               |
+| AgeOfLocationEstimate         | 3GPP TS 29.572 [12] |                           |               |
+| PositioningMethod             | 3GPP TS 29.572 [12] |                           |               |
+| AccuracyFulfilmentIndicator   | 3GPP TS 29.572 [12] |                           |               |
+| LmflIdentification            | 3GPP TS 29.572 [12] |                           |               |
+| LcsServiceType                | 3GPP TS 29.572 [12] |                           |               |
+| VelocityRequested             | 3GPP TS 29.572 [12] |                           |               |
+| LcsPriority                   | 3GPP TS 29.572 [12] |                           |               |
+| VelocityEstimate              | 3GPP TS 29.572 [12] |                           |               |
+| TerminationCause              | 3GPP TS 29.572 [12] |                           |               |
+| PositioningMethodAndUsage     | 3GPP TS 29.572 [12] |                           |               |
+| GnssPositioningMethodAndUsage | 3GPP TS 29.572 [12] |                           |               |
+| LcsServiceAuth                | 3GPP TS 29.571 [11] |                           |               |
+| Ecgi                          | 3GPP TS 29.571 [11] |                           |               |
+| Ncgi                          | 3GPP TS 29.571 [11] |                           |               |
+| Altitude                      | 3GPP TS 29.572 [12] | Altitude                  |               |
+| BarometricPressure            | 3GPP TS 29.572 [12] | Barometric pressure       |               |
+| LocationPrivacyVerResult      | 3GPP TS 29.518 [20] |                           |               |
+| ExternalGroupId               | 3GPP TS 29.571 [11] | External Group Identifier |               |
+| GroupId                       | 3GPP TS 29.571 [11] | Group Identifier          |               |
+| CivicAddress                  | 3GPP TS 29.572 [12] | Civic Address             |               |
+| GeographicArea                | 3GPP TS 29.572 [12] | Geographic Area           |               |
+| RedirectResponse              | 3GPP TS 29.571 [11] |                           |               |
+
+#### 6.1.5.2 Structured data types
+
+##### 6.1.5.2.1 Introduction
+
+This clause defines the structures to be used in resource representations.
+
+##### 6.1.5.2.2 Type: InputData
+
+Table 6.1.5.2.2-1: Definition of type InputData
+
+| Attribute name       | Data type                              | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                        | Applicability |
+|----------------------|----------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi                 | Gpsi                                   | O | 0..1        | Generic Public Subscription Identifier (NOTE 3).                                                                                                                                                                                                                                                                                   |               |
+| supi                 | Supi                                   | O | 0..1        | Subscription Permanent Identifier (NOTE 3).                                                                                                                                                                                                                                                                                        |               |
+| extGroupId           | ExternalGroupId                        | O | 0..1        | This IE may be present when requesting LCS service for a group of target UEs, if present this IE shall contain the External Group ID (NOTE 3).                                                                                                                                                                                     |               |
+| intGroupId           | GroupId                                | O | 0..1        | This IE may be present when requesting LCS service for a group of target UEs, if present this IE shall contain the Internal Group ID (NOTE 3).                                                                                                                                                                                     |               |
+| externalClientType   | ExternalClientType                     | M | 1           | This IE shall contain LCS client type                                                                                                                                                                                                                                                                                              |               |
+| locationQoS          | LocationQoS                            | O | 0..1        | Requested location QoS                                                                                                                                                                                                                                                                                                             |               |
+| supportedGADShapes   | array(SupportedGADShapes)              | O | 1..N        | Supported Geographical Area Description shapes                                                                                                                                                                                                                                                                                     |               |
+| serviceIdentity      | ServiceIdentity                        | O | 0..1        | Service identity                                                                                                                                                                                                                                                                                                                   |               |
+| serviceCoverage      | array(E164CountryCodeOfGeographicArea) | O | 1..N        | A list of E.164 country codes for geographic areas (see ITU Recommendation E.164 [13]) where the LCS client is permitted to request and receive UE location information.                                                                                                                                                           |               |
+| ldrType              | LdrType                                | C | 0..1        | Location deferred request event type                                                                                                                                                                                                                                                                                               |               |
+| periodicEventInfo    | PeriodicEventInfo                      | C | 0..1        | Periodic event information of the location request for a target UE                                                                                                                                                                                                                                                                 |               |
+| areaEventInfo        | AreaEventInfoExt                       | C | 0..1        | Area event information of the location request for a target UE                                                                                                                                                                                                                                                                     |               |
+| motionEventInfo      | MotionEventInfo                        | C | 0..1        | Motion event information of the location request for a target UE                                                                                                                                                                                                                                                                   |               |
+| ldrReference         | LdrReference                           | C | 0..1        | Notification correlation ID<br>It shall be present in the request from NEF if it is allocated by NEF for the Deferred 5GC-MT-LR procedure.<br>It shall be present in the request from NEF for requesting location service for a group of UEs.<br>It shall be present in the request to VGMLC for the Deferred 5GC-MT-LR procedure. |               |
+| hgmlcCallBackUri     | Uri                                    | O | 0..1        | Notification target address for HGMLC                                                                                                                                                                                                                                                                                              |               |
+| eventNotificationUri | Uri                                    | O | 0..1        | The call-back Uri of NF service consumer (i.e. NEF) for implicit subscription to notification of Eventnotify.<br>This IE should be included and is used to receive the location information for UEs in the group when requesting LCS service for a group of target UEs or requesting deferred 5GC MT LCS service for a single UE.  |               |
+| externalClientId     | ExternalClientId                       | O | 0..1        | External LCS client identification                                                                                                                                                                                                                                                                                                 |               |
+
+|                                                                                                                                                                                                                                                                                                                            |                       |   |      |                                                                                                                                                                                                                                 |  |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+| fication                                                                                                                                                                                                                                                                                                                   | entification          |   |      |                                                                                                                                                                                                                                 |  |
+| aflId                                                                                                                                                                                                                                                                                                                      | string                | O | 0..1 | The identification of AF that initiated location request                                                                                                                                                                        |  |
+| uePrivacyRequirements                                                                                                                                                                                                                                                                                                      | UePrivacyRequirements | O | 0..1 | UE privacy requirement                                                                                                                                                                                                          |  |
+| lcsServiceType                                                                                                                                                                                                                                                                                                             | LcsServiceType        | O | 0..1 | LCS service type<br><br>This IE may be present when being sent from HGMLC to VGMLC.<br><br>When present, it shall contain the LCS service type, which is mapped from attribute serviceIdentity of the LCS Request by the HGMLC. |  |
+| velocityRequested                                                                                                                                                                                                                                                                                                          | VelocityRequested     | O | 0..1 | Velocity of the target UE is requested                                                                                                                                                                                          |  |
+| priority                                                                                                                                                                                                                                                                                                                   | LcsPriority           | O | 0..1 | Priority of the location request                                                                                                                                                                                                |  |
+| locationTypeRequested                                                                                                                                                                                                                                                                                                      | LocationTypeRequested | O | 0..1 | Requested type of location, applicable to location immediate request (NOTE 2)                                                                                                                                                   |  |
+| maximumAgeOfLocationEstimate                                                                                                                                                                                                                                                                                               | AgeOfLocationEstimate | O | 0..1 | Requested maximum age of the location estimate                                                                                                                                                                                  |  |
+| amfId                                                                                                                                                                                                                                                                                                                      | AmfId                 | O | 0..1 | The identification of serving AMF                                                                                                                                                                                               |  |
+| codeWord                                                                                                                                                                                                                                                                                                                   | CodeWord              | O | 0..1 | Code word (NOTE 1)                                                                                                                                                                                                              |  |
+| NOTE 1: Checking of the Codeword in UE applies only when the Codeword parameter is present and when the codeWordCheck parameter (specified in clause 6.1.5.2.7) is present and set to TRUE.                                                                                                                                |                       |   |      |                                                                                                                                                                                                                                 |  |
+| NOTE 2: If the LocationTypeRequested parameter is set to value "NOTIFICATION_VERIFICATION_ONLY", then the lcsServiceAuthInfo attribute in the uePrivacyRequirements IE, if present, shall be set to either "NOTIFICATION_ONLY" or "NOTIFICATION_AND_VERIFICATION_ONLY".                                                    |                       |   |      |                                                                                                                                                                                                                                 |  |
+| NOTE 3: If retrieving the location for a target UE, the UE identification (attributes gsi and/or supi) shall be included, if retrieving the UE locations for a target group, the group identification (attributes extGroupId and/or intGroupId), UE identification and group identification shall be included exclusively. |                       |   |      |                                                                                                                                                                                                                                 |  |
+
+##### 6.1.5.2.3 Type: LocationData
+
+Table 6.1.5.2.3-1: Definition of type LocationData
+
+| Attribute name              | Data type                            | P | Cardinality | Description                                                                                                                                                                                                                                                                                                           | Applicability |
+|-----------------------------|--------------------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| gpsi                        | Gpsi                                 | O | 0..1        | Generic Public Subscription Identifier                                                                                                                                                                                                                                                                                |               |
+| supi                        | Supi                                 | O | 0..1        | Subscription Permanent Identifier                                                                                                                                                                                                                                                                                     |               |
+| locationEstimate            | GeographicArea                       | O | 0..1        | Geographic area of the target UE                                                                                                                                                                                                                                                                                      |               |
+| civicAddress                | CivicAddress                         | O | 0..1        | Civic address of the target UE                                                                                                                                                                                                                                                                                        |               |
+| ageOfLocationEstimate       | AgeOfLocationEstimate                | O | 0..1        | Age of location estimate                                                                                                                                                                                                                                                                                              |               |
+| positioningDataList         | array(PositioningMethodAndUsage)     | O | 1..N        | If present, this IE shall indicate the usage of each non-GNSS positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully.                                                                                                                                        |               |
+| gnssPositioningDataList     | array(GNSSPositioningMethodAndUsage) | O | 1..N        | If present, this IE shall indicate the usage of each GNSS positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully.                                                                                                                                            |               |
+| accuracyFulfilmentIndicator | AccuracyFulfilmentIndicator          | O | 0..1        | The indication whether the obtained location estimate satisfies the requested accuracy or not                                                                                                                                                                                                                         |               |
+| ueVelocity                  | VelocityEstimate                     | O | 0..1        | Responded UE velocity, if requested and available                                                                                                                                                                                                                                                                     |               |
+| ldrReference                | LdrReference                         | C | 0..1        | Notification correlation ID<br>It shall be present in the response to NEF if it is allocated by HGMLC for the the Deferred 5GC-MT-LR procedure.                                                                                                                                                                       |               |
+| altitude                    | Altitude                             | C | 0..1        | If present, this IE indicates the altitude of the positioning estimate.<br>This IE shall be sent from (V)GMLC to (H)GMLC if received by VGMLC from AMF when roaming.                                                                                                                                                  |               |
+| servingLMFIdentification    | LMFIdentification                    | C | 0..1        | If present, this IE contains the identification of a serving LMF for periodic or triggered location.<br>This IE shall be sent from (V)GMLC to (H)GMLC if received by VGMLC from AMF when roaming.                                                                                                                     |               |
+| locationPrivacyVerResult    | LocationPrivacyVerResult             | C | 0..1        | If present, this IE contains the result of location privacy verification by UE.<br>The IE shall be included from (V)GMLC to (H)GMLC if received from the serving AMF by (V)GMLC when roaming and a location request with notification and privacy verification only indication is sent to the serving AMF via (V)GMLC |               |
+
+|             |             |   |      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |  |
+|-------------|-------------|---|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+|             |             |   |      | by (H)GMLC during location request procedure..                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |  |
+| successType | SuccessType | C | 0..1 | <p>This IE is only used for requesting LCS service for a group, and shall be present to indicate one of the following value.</p> <ul style="list-style-type: none"> <li>- SUCCESS_COMPLETELY</li> <li>- SUCCESS_PARTIALLY</li> </ul> <p>The value "SUCCESS_COMPLETELY" indicates that requesting/subscribing to LCS service is successful for all the UE(s) within the group identified by the external/internal group ID.</p> <p>The value "SUCCESS_PARTIALLY" indicates that requesting/subscribing to LCS service is only successful for a part of the UE(s) within the group identified by the external/internal group ID.</p> <p>The default value of this attribute is "SUCCESS_COMPLETELY" if this IE is not present.</p> |  |
+
+##### 6.1.5.2.4 Type: CancelLocData
+
+Table 6.1.5.2.4-1: Definition of type CancelLocData
+
+| Attribute name                                                                                                                                                                                                                                                                                                            | Data type         | P | Cardinality | Description                                                                                                                                                                                            | Applicability |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi                                                                                                                                                                                                                                                                                                                      | Supi              | O | 0..1        | This IE may be present when requesting cancellation of LCS service for a single UE.<br><br>When present, this IE shall contain the Subscription Permanent Identifier of the target UE.<br>(NOTE).      |               |
+| gpsi                                                                                                                                                                                                                                                                                                                      | Gpsi              | O | 0..1        | This IE may be present when requesting cancellation of LCS service for a single UE.<br><br>When present, this IE shall contain the Generic Public Subscription identifier of the target UE.<br>(NOTE). |               |
+| extGroupId                                                                                                                                                                                                                                                                                                                | ExternalGroupId   | O | 0..1        | This IE may be present when requesting cancellation of LCS service for a group of target UEs.<br><br>When present this IE shall contain the External Group ID<br>(NOTE).                               |               |
+|                                                                                                                                                                                                                                                                                                                           |                   | O | 0..1        | This IE may be present when requesting cancellation of LCS service for a group of target UEs.<br><br>When present this IE shall contain the Internal Group ID<br>(NOTE).                               |               |
+| hgmLcCallbackUri                                                                                                                                                                                                                                                                                                          | Uri               | M | 1           | Notification target address                                                                                                                                                                            |               |
+| ldrReference                                                                                                                                                                                                                                                                                                              | LdrReference      | M | 1           | LDR Reference                                                                                                                                                                                          |               |
+| lmfIdentification                                                                                                                                                                                                                                                                                                         | LmfIdentification | O | 0..1        | The latest LMF identification received                                                                                                                                                                 |               |
+| amfId                                                                                                                                                                                                                                                                                                                     | AmfId             | O | 0..1        | The identification of the serving AMF                                                                                                                                                                  |               |
+| NOTE: If cancelling the location for a target UE, the UE identification (attributes gpsi and/or supi) shall be included, if cancelling the UE locations for a target group, the group identification (attributes extGroupId and/or intGroupId), UE identification and group identification shall be included exclusively. |                   |   |             |                                                                                                                                                                                                        |               |
+
+##### 6.1.5.2.5 Type: LocUpdateData
+
+Table 6.1.5.2.5-1: Definition of type LocUpdateData
+
+| Attribute name               | Data type                    | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                                                                                          | Applicability |
+|------------------------------|------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi                         | Supi                         | O | 0..1        | Subscription Permanent Identifier                                                                                                                                                                                                                                                                                                                                                                    |               |
+| gpsi                         | Gpsi                         | O | 0..1        | Generic Public Subscription identifier                                                                                                                                                                                                                                                                                                                                                               |               |
+| pseudonymIndicator           | PseudonymIndicator           | O | 0..1        | Pseudonym indicator                                                                                                                                                                                                                                                                                                                                                                                  |               |
+| locationRequestType          | LocationRequestType          | M | 1           | Event causing the location estimate (5GC-MO-LR)                                                                                                                                                                                                                                                                                                                                                      |               |
+| locationEstimate             | GeographicArea               | M | 1           | Geographic area of the target UE                                                                                                                                                                                                                                                                                                                                                                     |               |
+| ageOfLocationEstimate        | AgeOfLocationEstimate        | M | 1           | Age of location estimate                                                                                                                                                                                                                                                                                                                                                                             |               |
+| accuracyFulfillmentIndicator | AccuracyFulfillmentIndicator | M | 1           | The indication whether the obtained location estimate satisfies the requested accuracy or not                                                                                                                                                                                                                                                                                                        |               |
+| civicAddress                 | CivicAddress                 | O | 0..1        | Civic address of the target UE                                                                                                                                                                                                                                                                                                                                                                       |               |
+| lcsQosClass                  | LcsQosClass                  | M | 1           | The LCS QoS Class requested by the target UE                                                                                                                                                                                                                                                                                                                                                         |               |
+| externalClientId             | ExternalClientId             | O | 0..1        | Identity of the LCS client                                                                                                                                                                                                                                                                                                                                                                           |               |
+| aflid                        | string                       | O | 0..1        | Identity of the AF                                                                                                                                                                                                                                                                                                                                                                                   |               |
+| gmlcNumber                   | string                       | C | 0..1        | This IE shall be included by the AMF in the request to V-GMLC, if the "mlc-number" IE is received in MO request from the UE.<br><br>When present, this IE shall contain the GMLC Number (in E.164 international number format) indicated in the "mlc-number" IE of the MO request from the UE. The V-GMLC may query NRF to obtain the H-GMLC using the GMLC Number.<br><br>Pattern: "^[0-9]{5,15}\$" |               |
+| lcsServiceType               | LcsServiceTypeId             | O | 0..1        | When present, this IE shall contain the LCS Service Type received from the UE, as specified in clause 6.2 of 3GPP TS 23.273 [4].<br><br>When received, the H-GMLC shall map the received LCS Service Type to the Service Identity in Location Update Notification.                                                                                                                                   |               |
+
+##### 6.1.5.2.6 Type: EventNotifyData
+
+Table 6.1.5.2.6-1: Definition of type EventNotifyData
+
+| Attribute name              | Data type                            | P | Cardinality | Description                                                                                                                                                                                                                                            | Applicability |
+|-----------------------------|--------------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi                        | Supi                                 | O | 0..1        | Subscription Permanent Identifier                                                                                                                                                                                                                      |               |
+| gpsi                        | Gpsi                                 | O | 0..1        | Generic Public Subscription Identifier                                                                                                                                                                                                                 |               |
+| ldrReference                | LdrReference                         | M | 1           | LDR Reference                                                                                                                                                                                                                                          |               |
+| eventNotifyDataType         | EventNotifyDataType                  | M | 1           | The type of event that triggers event notification                                                                                                                                                                                                     |               |
+| locationEstimate            | GeographicArea                       | O | 0..1        | Geographic area of the target UE                                                                                                                                                                                                                       |               |
+| civicAddress                | CivicAddress                         | O | 0..1        | Civic address of the target UE                                                                                                                                                                                                                         |               |
+| ageOfLocationEstimate       | AgeOfLocationEstimate                | O | 0..1        | Age of location estimate                                                                                                                                                                                                                               |               |
+| positioningDataList         | array(PositioningMethodAndUsage)     | O | 1..N        | If present, this IE shall indicate the usage of each non-GNSS positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully.                                                                         |               |
+| gnssPositioningDataList     | array(GNSSPositioningMethodAndUsage) | O | 1..N        | If present, this IE shall indicate the usage of each GNSS positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully.                                                                             |               |
+| lmfIdentification           | LmfIdentification                    | O | 0..1        | LMF identification that stores the location context of the target UE                                                                                                                                                                                   |               |
+| amfld                       | Amfld                                | O | 0..1        | The identification of AMF that is serving the target UE                                                                                                                                                                                                |               |
+| terminationCause            | TerminationCause                     | C | 0..1        | The IE shall be included if event reporting has been terminated                                                                                                                                                                                        |               |
+| velocityEstimate            | VelocityEstimate                     | C | 0..1        | If present, this IE contain an estimate of the velocity of the target UE, composed by horizontal speed, vertical speed, and their respective uncertainty.<br>This IE shall be sent from (V)GMLC to (H)GMLC if received by VGMLC from AMF when roaming. |               |
+| altitude                    | Altitude                             | C | 0..1        | If present, this IE indicates the altitude of the positioning estimate.<br>This IE shall be sent from (V)GMLC to (H)GMLC if received by VGMLC from AMF when roaming.                                                                                   |               |
+| targetNode                  | NfInstanceId                         | C | 0..1        | For mobility of a UE with periodic or triggered location, this IE contains the address of the new serving node and shall be sent from (V)GMLC to (H)GMLC if received by VGMLC from AMF when roaming.                                                   |               |
+| accuracyFulfilmentIndicator | AccuracyFulfilmentIndicator          | O | 0..1        | The indication whether the obtained location estimate satisfies the requested                                                                                                                                                                          |               |
+
+|              |              |   |      |                                                                                                                                                             |  |
+|--------------|--------------|---|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+|              |              |   |      | accuracy or not                                                                                                                                             |  |
+| failureCause | FailureCause | C | 0..1 | This IE shall contain the failure cause for the UE if present.<br>The IE shall be included if positioning has failed for the target UE in the target group. |  |
+
+##### 6.1.5.2.7 Type: UePrivacyRequirements
+
+**Table 6.1.5.2.7-1: Definition of type UePrivacyRequirements**
+
+| Attribute name     | Data type      | P | Cardinality | Description                                                                                                                                                                                                              | Applicability |
+|--------------------|----------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| lcsServiceAuthInfo | LcsServiceAuth | O | 0..1        | When present, this IE shall contain an indication of privacy related notification or verification for the target UE.<br>The default value of this parameter if not presents is "LOCATION_ALLOWED_W ITHOUT_NOTIFICATION". |               |
+| codeWordCheck      | boolean        | O | 0..1        | When present, it shall indicate whether the Codeword parameter shall be checked in UE. (NOTE)                                                                                                                            |               |
+
+NOTE: Checking of the Codeword in UE applies only when the Codeword parameter (specified in clause 6.1.5.2.2) is present and when the codeWordCheck parameter is present and set to TRUE.
+
+##### 6.1.5.2.8 Void
+
+##### 6.1.5.2.9 Type: LocUpdateNotification
+
+**Table 6.1.5.2.9-1: Definition of type LocUpdateNotification**
+
+| Attribute name              | Data type                    | P | Cardinality | Description                                                                                                                                                  | Applicability |
+|-----------------------------|------------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi                        | Supi                         | O | 0..1        | Subscription Permanent Identifier                                                                                                                            |               |
+| gpsi                        | Gpsi                         | O | 0..1        | Generic Public Subscription identifier                                                                                                                       |               |
+| locationRequestType         | LocationRequestTy pe         | M | 1           | Event causing the location estimate (5GC-MO-LR)                                                                                                              |               |
+| locationEstimate            | GeographicArea               | M | 1           | geographic area of the target UE                                                                                                                             |               |
+| ageOfLocationEstimate       | AgeOfLocationEsti mate       | M | 1           | Age of location estimate                                                                                                                                     |               |
+| accuracyFulfilmentIndicator | AccuracyFulfilmentI ndicator | M | 1           | The indication whether the obtained location estimate satisfies the requested accuracy or not                                                                |               |
+| civicAddress                | CivicAddress                 | O | 0..1        | Civic address of the target UE                                                                                                                               |               |
+| lcsQosClass                 | LcsQosClass                  | M | 1           | The LCS QoS Class requested by the target UE                                                                                                                 |               |
+| aflid                       | string                       | O | 0..1        | Identity of the AF                                                                                                                                           |               |
+| serviceIdentity             | ServiceIdentity              | O | 0..1        | When present, this IE shall contain Service Identity mapped from the LCS Service Type specified by the UE, as specified in clause 6.2 of 3GPP TS 23.273 [4]. |               |
+
+##### 6.1.5.2.10 Type: LocUpdateSubs
+
+Table 6.1.5.2.10-1: Definition of type LocUpdateSubs
+
+| Attribute name | Data type    | P | Cardinality | Description                                                                                                            | Applicability |
+|----------------|--------------|---|-------------|------------------------------------------------------------------------------------------------------------------------|---------------|
+| nfInstanceId   | NfInstanceId | M | 1           | Identity of the NF Instance creating the subscription.                                                                 |               |
+| notifUri       | Uri          | M | 1           | The URI via which the NF service consumer wants to receive notifications related to this subscription.                 |               |
+| supi           | Supi         | C | 0..1        | SUPI of the UE concerned by the subscription.<br>This attribute shall be present if the gpsi attribute is not present. |               |
+| gpsi           | Gpsi         | C | 0..1        | GPSI of the UE concerned by the subscription.<br>This attribute shall be present if the supi attribute is not present. |               |
+
+##### 6.1.5.2.11 Type: EventNotifyDataAdditionalInfo
+
+Table 6.1.5.2.11-1: Definition of type EventNotifyDataAdditionalInfo
+
+| Attribute name   | Data type              | P | Cardinality | Description                                                                                                           | Applicability |
+|------------------|------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------|---------------|
+| addEventDataList | array(EventNotifyData) | O | 1..N        | When present, this IE shall include a list of event reports of the additional UE(s) which belong to the target group. |               |
+
+##### 6.1.5.2.12 Type: EventNotifyDataExt
+
+Table 6.1.5.2.12-1: Definition of type EventNotifyDataExt as a list of to be combined data
+
+| Data type                     | Cardinality | Description                                           | Applicability |
+|-------------------------------|-------------|-------------------------------------------------------|---------------|
+| EventNotifyData               | 1           | Event Notification Data                               |               |
+| EventNotifyDataAdditionalInfo | 1           | Additional information of the Event Notification Data |               |
+
+##### 6.1.5.2.13 Type: AreaEventInfoAddition
+
+Table 6.1.5.2.13-1: Definition of type AreaEventInfoAddition
+
+| Attribute name   | Data type             | P | Cardinality | Description                                                                                                                                                                                                                            |
+|------------------|-----------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| geoAreaList      | array(GeographicArea) | O | 1..N        | One or more geographic areas for location reporting event                                                                                                                                                                              |
+| ignoreAreaDefInd | boolean               | O | 0..1        | Indicating whether the "areaDefinition" IE in AreaEventInfoExt combined data type shall be ignored or not:<br><br>- true: the "areaDefinition" IE shall be ignored.<br>- false (default) the "areaDefinition" IE shall not be ignored. |
+
+##### 6.1.5.2.14 Type: AreaEventInfoExt
+
+Table 6.1.5.2.14-1: Definition of type AreaEventInfoExt as a list of to be combined data
+
+| Data type             | Cardinality | Description                                              | Applicability |
+|-----------------------|-------------|----------------------------------------------------------|---------------|
+| AreaEventInfo         | 1           | Area Event Information                                   |               |
+| AreaEventInfoAddition | 1           | Addition information for Extended Area Event Information |               |
+
+#### 6.1.5.3 Simple data types and enumerations
+
+##### 6.1.5.3.1 Introduction
+
+This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
+
+##### 6.1.5.3.2 Simple data types
+
+The simple data types defined in table 6.1.5.3.2-1 shall be supported.
+
+Table 6.1.5.3.2-1: Simple data types
+
+| Type Name                       | Type Definition | Description                                                                                                                                          | Applicability |
+|---------------------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| ServiceIdentity                 | string          | Service identity                                                                                                                                     |               |
+| ExternalClientIdIdentification  | string          | External LCS client identification                                                                                                                   |               |
+| CodeWord                        | string          | codeword                                                                                                                                             |               |
+| E164CountryCodeOfGeographicArea | string          | The combination of one, two or three digits identifying a specific country, countries in an integrated numbering plan, or a specific geographic area |               |
+| LcsServiceTypeId                | integer         | LCS Service Type Id, as specified clause 7.6.11.15 of 3GPP TS 29.002 [xx].<br>Minimum = 0. Maximum = 127                                             |               |
+
+##### 6.1.5.3.3 Enumeration: PseudonymIndicator
+
+The enumeration PseudonymIndicator represents whether pseudonym should be used as the identity of the target UE. It shall comply with the provisions defined in table 6.1.5.3.3-1.
+
+Table 6.1.5.3.3-1: Enumeration PseudonymIndicator
+
+| Enumeration value         | Description                  | Applicability |
+|---------------------------|------------------------------|---------------|
+| "PSEUDONYM_REQUESTED"     | A pseudonym is requested     |               |
+| "PSEUDONYM_NOT_REQUESTED" | A pseudonym is not requested |               |
+
+##### 6.1.5.3.4 Enumeration: LocationRequestType
+
+The enumeration LocationRequestType represents how the location request is triggered. It shall comply with the provisions defined in table 6.1.5.3.4-1.
+
+Table 6.1.5.3.4-1: Enumeration LocationRequestType
+
+| Enumeration value | Description                        | Applicability |
+|-------------------|------------------------------------|---------------|
+| "NI-LR"           | Network induced location request   |               |
+| "MT-LR"           | Mobile terminated location request |               |
+| "MO-LR"           | Mobile originated location request |               |
+
+##### 6.1.5.3.5 Enumeration: LocationTypeRequested
+
+The enumeration LocationTypeRequested represents the requested type of location which is only applicable to location immediate request. It shall comply with the provisions defined in table 6.1.5.3.5-1.
+
+**Table 6.1.5.3.5-1: Enumeration LocationTypeRequested**
+
+| Enumeration value                | Description                                                    | Applicability |
+|----------------------------------|----------------------------------------------------------------|---------------|
+| "CURRENT_LOCATION"               | Requesting the current location of the target UE               |               |
+| "CURRENT_OR_LAST_KNOWN_LOCATION" | Requesting the current or last known location of the target UE |               |
+| "INITIAL_LOCATION"               | Requesting the initial location of the target UE               |               |
+| "NOTIFICATION_VERIFICATION_ONLY" | Requesting notification verification only                      |               |
+
+##### 6.1.5.3.6 Enumeration: EventNotifyDataType
+
+The enumeration EventNotifyDataType represents the type of event notification. It shall comply with the provisions defined in table 6.1.5.3.6-1.
+
+**Table 6.1.5.3.6-1: Enumeration EventNotifyDataType**
+
+| Enumeration value                   | Description                                                                                                                   | Applicability |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------|
+| "UE_AVAILABLE"                      | UE available event                                                                                                            |               |
+| "PERIODIC"                          | Periodic event                                                                                                                |               |
+| "ENTERING_INTO_AREA"                | Entering area event                                                                                                           |               |
+| "LEAVING_FROM_AREA"                 | Leaving area event                                                                                                            |               |
+| "BEING_INSIDE_AREA"                 | Being inside area event                                                                                                       |               |
+| "MOTION"                            | Motion event                                                                                                                  |               |
+| "MAXIMUM_INTERVAL_EXPIRATION_EVENT" | Expiration of maximum reporting interval event                                                                                |               |
+| "LOCATION_CANCELLATION_EVENT"       | Cancellation of location reporting event                                                                                      |               |
+| "ACTIVATION_OF_DEFERRED_LOCATION"   | A confirmation that periodic or triggered location was successfully activated in the target UE                                |               |
+| "UE_MOBILITY_FOR_DEFERRED_LOCATION" | Mobility of the target UE to a different NF                                                                                   |               |
+| "5GC_MT_LR"                         | Report of immediate 5GC mobile terminated location.<br>It is used for 5GC_MT_LR request targeting to a group of UE procedure. |               |
+
+##### 6.1.5.3.7 Enumeration: FailureCause
+
+The enumeration FailureCause represents the cause of positioning failure. It shall comply with the provisions defined in table 6.1.5.3.7-1.
+
+**Table 6.1.5.3.7-1: Enumeration FailureCause**
+
+| Enumeration value    | Description                        | Applicability |
+|----------------------|------------------------------------|---------------|
+| "POSITIONING_DENIED" | Positioning is denied              |               |
+| "UNSUPPORTED_BY_UE"  | Positioning is not supported by UE |               |
+| "NOT_REGISTERED_UE"  | UE doesn't register                |               |
+| "UNSPECIFIED"        | Unspecified                        |               |
+
+##### 6.1.5.3.8 Enumeration: SuccessType
+
+The enumeration SuccessType represents the type of success. It shall comply with the provisions defined in table 6.1.5.3.8-1.
+
+**Table 6.1.5.3.8-1: Enumeration SuccessType**
+
+| Enumeration value    | Description                  | Applicability |
+|----------------------|------------------------------|---------------|
+| "SUCCESS COMPLETELY" | It is completely successful. |               |
+| "SUCCESS PARTIALLY"  | It is partially successful.  |               |
+
+### 6.1.6 Error Handling
+
+#### 6.1.6.1 General
+
+HTTP error handling shall be supported as specified in clause 5.2.4 of 3GPP TS 29.500 [5].
+
+#### 6.1.6.2 Protocol Errors
+
+Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [5].
+
+#### 6.1.6.3 Application Errors
+
+The application errors defined for the Ngmlc\_Location service are listed in Table 6.1.6.3-1.
+
+**Table 6.1.6.3-1: Application errors**
+
+| Application Error                 | HTTP status code          | Description                                                                                                                                                                                              |
+|-----------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| POSITIONING_DENIED                | 403 Forbidden             | the positioning procedure was denied.                                                                                                                                                                    |
+| UNSPECIFIED                       | 403 Forbidden             | the request is rejected due to unspecified reasons.                                                                                                                                                      |
+| UNSUPPORTED_BY_UE                 | 403 Forbidden             | the position request for periodic or triggered location is not supported by the target UE                                                                                                                |
+| LOCATION_SESSION_UNKNOWN          | 403 Forbidden             | the location context was not found                                                                                                                                                                       |
+| UNREQUESTED_BY_UE                 | 403 Forbidden             | the UE did not request transfer of its location to an LCS Client or AF                                                                                                                                   |
+| UNKNOWN_EXTERNAL_CLIENT_OR_AF     | 403 Forbidden             | the external LCS client or AF is unknown                                                                                                                                                                 |
+| UNREACHABLE_EXTERNAL_CLIENT_OR_AF | 403 Forbidden             | the external LCS client or AF is unreachable                                                                                                                                                             |
+| DETACHED_USER                     | 403 Forbidden             | the user is deregistered in the AMF                                                                                                                                                                      |
+| POSITIONING_FAILED                | 500 Internal Server Error | the positioning procedure failed                                                                                                                                                                         |
+| UNREACHABLE_USER                  | 504 Gateway Timeout       | the user could not be reached in order to perform positioning procedure                                                                                                                                  |
+| PEER_NOT_RESPONDING               | 504 Gateway Timeout       | No response is received from a remote peer, i.e.,<br>1) The response from the serving AMF wasn't received by (V)GMLC, or;<br>2) (V)GMLC received HTTP status code 504 with PEER_NOT_RESPONDING from AMF. |
+
+### 6.1.7 Feature negotiation
+
+The optional features in table 6.1.7-1 are defined for the Ngmlc\_Location API.
+
+**Table 6.1.7-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+### 6.1.8 Security
+
+As indicated in 3GPP TS 33.501 [15], the access to the Ngmlc\_Location API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [16]), using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [17]) plays the role of the authorization server.
+
+If Oauth2 authorization is used, an NF Service Consumer, prior to consuming services offered by the Ngmlc\_Location API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [17], clause 5.4.2.2.
+
+NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Ngmlc\_Location service.
+
+The Ngmlc\_Location API defines scopes for OAuth2 authorization as specified in 3GPP TS 33.501 [15]; it defines a single scope consisting on the name of the service (i.e., "ngmlc-loc"), and it does not define any additional scopes at resource or operation level.
+
+### 6.1.9 HTTP redirection
+
+An HTTP request may be redirected to a different GMLC service instance, within the same GMLC or a different GMLC of an GMLC set, e.g. when an GMLC service instance is part of an GMLC (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different GMLC producer instance will return the NF Instance ID of the new GMLC producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
+
+If an GMLC within an GMLC set redirects a service request to a different GMLC of the set using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new GMLC towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the Ngmlc\_Location service. It consists of OpenAPI 3.0.0 specifications, in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository, that uses the GitLab software version control system (see 3GPP TS 29.501 [6] clause 5.3.1 and 3GPP TR 21.900 [19] clause 5B).
+
+## A.2 Ngmlc\_Location API
+
+```
+openapi: 3.0.0
+info:
+  version: '1.0.6'
+  title: Ngmlc_Location
+  description: |
+    Ngmlc_Location Service.
+    © 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.515 V16.7.0; 5G System; Gateway Mobile Location Services; Stage 3
+  url: 'http://www.3gpp.org/ftp/Specs/archive/29_series/29.515/'
+
+servers:
+  - url: '{apiRoot}/ngmlc-loc/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - ngmlc-loc
+
+paths:
+  /provide-location:
+    post:
+      summary: Request Location of an UE
+      operationId: RequestLocation
+      tags:
+        - Request Location
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/InputData'
+        required: true
+      responses:
+        '200':
+          description: Expected response to a valid request
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LocationData'
+        '307':
+          $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+        '308':
+          $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+```
+
+```
+'400':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+'401':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+'403':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+'404':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+'411':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+'413':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+'415':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+'429':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+'503':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+'504':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+default:
+  $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+callbacks:
+  EventNotify:
+    '{ $request.body#/htmlCallbackUri }':
+      post:
+        requestBody:
+          description: UE Event Notification
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/EventNotifyDataExt'
+        responses:
+          '204':
+            description: Expected response to a valid notification
+          '307':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+          '308':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+          '400':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+          '401':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+          '403':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+          '404':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+          '411':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+          '413':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+          '415':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+          '429':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+          '500':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+          '503':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+          '504':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+          default:
+            $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+  EventNotifyNef:
+    '{ $request.body#/eventNotificationUri }':
+      post:
+        requestBody:
+          description: UE Event Notification
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/EventNotifyData'
+        responses:
+          '204':
+            description: Expected response to a valid notification
+          '307':
+```
+
+```
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+      '504':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+      default:
+        $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/cancel-location:
+  post:
+    summary: request cancellation of periodic or triggered location
+    operationId: CancelLocation
+    tags:
+      - Cancel Location
+    requestBody:
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/CancelLocData'
+    required: true
+    responses:
+      '204':
+        description: Expected response to a successful cancellation
+      '307':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+      '504':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+      default:
+        $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/location-update:
+  post:
+    summary: update UE location information
+    operationId: UpdateLocation
+    tags:
+      - Update Location
+    requestBody:
+      content:
+```
+
+```
+    application/json:
+      schema:
+        $ref: '#/components/schemas/LocUpdateData'
+    required: true
+    responses:
+      '204':
+        description: Expected response to successful location context transfer
+      '307':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+      '504':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+      default:
+        $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+/loc-update-subs:
+  post:
+    summary: subscribe to notifications of UE location information
+    operationId: LocationUpdateSubscribe
+    tags:
+      - UE location information Subscription creation
+    requestBody:
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/LocUpdateSubs'
+    required: true
+    responses:
+      '204':
+        description: Expected response to successful UE location information subscription
+      '307':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+      '504':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+      default:
+        $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+```
+
+```
+
+callbacks:
+  LocationUpdateNotify:
+    '{$request.body#/notifUri}':
+      post:
+        requestBody:
+          description: Location Update Notification
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LocUpdateNotification'
+        responses:
+          '204':
+            description: Expected response to a valid notification
+          '307':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+          '308':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+          '400':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+          '401':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+          '403':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+          '404':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+          '411':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+          '413':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+          '415':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+          '429':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+          '500':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+          '503':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+          '504':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/504'
+          default:
+            $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            ngmlc-loc: Access to the Ngmlc_Location API
+
+schemas:
+#
+# COMPLEX TYPES
+#
+  InputData:
+    type: object
+    required:
+      - externalClientType
+    properties:
+      gpsi:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+      supi:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+      extGroupId:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/ExternalGroupId'
+      intGroupId:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId'
+      externalClientType:
+        $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/ExternalClientType'
+      locationQoS:
+        $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LocationQoS'
+      supportedGADShapes:
+        type: array
+        items:
+          $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/SupportedGADShapes'
+        minItems: 1
+
+```
+
+```
+serviceIdentity:
+  $ref: '#/components/schemas/ServiceIdentity'
+serviceCoverage:
+  type: array
+  items:
+    $ref: '#/components/schemas/E164CountryCodeOfGeographicArea'
+  minItems: 1
+ldrType:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrType'
+periodicEventInfo:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/PeriodicEventInfo'
+areaEventInfo:
+  $ref: '#/components/schemas/AreaEventInfoExt'
+motionEventInfo:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/MotionEventInfo'
+ldrReference:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrReference'
+hgmlcCallbackUri:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+eventNotificationUri:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+externalClientIdentification:
+  $ref: '#/components/schemas/ExternalClientIdentification'
+afId:
+  type: string
+uePrivacyRequirements:
+  $ref: '#/components/schemas/UePrivacyRequirements'
+lcsServiceType:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LcsServiceType'
+velocityRequested:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/VelocityRequested'
+priority:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LcsPriority'
+locationTypeRequested:
+  $ref: '#/components/schemas/LocationTypeRequested'
+maximumAgeOfLocationEstimate:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AgeOfLocationEstimate'
+amfId:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/AmfId'
+codeWord:
+  $ref: '#/components/schemas/CodeWord'
+
+LocationData:
+  type: object
+  properties:
+    gsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    locationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea'
+    civicAddress:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress'
+    ageOfLocationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AgeOfLocationEstimate'
+    positioningDataList:
+      type: array
+      items:
+        $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/PositioningMethodAndUsage'
+      minItems: 1
+    gnssPositioningDataList:
+      type: array
+      items:
+        $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GnssPositioningMethodAndUsage'
+      minItems: 1
+    accuracyFulfilmentIndicator:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AccuracyFulfilmentIndicator'
+    ueVelocity:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/VelocityEstimate'
+    ldrReference:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrReference'
+    altitude:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Altitude'
+    servingLMFIdentification:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LMFIdentification'
+    locationPrivacyVerResult:
+      $ref: 'TS29518_Namf_Location.yaml#/components/schemas/LocationPrivacyVerResult'
+```
+
+```
+successType:
+  $ref: '#/components/schemas/SuccessType'
+CancelLocData:
+  type: object
+  required:
+    - hgmlcCallBackUri
+    - ldrReference
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    extGroupId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/ExternalGroupId'
+    intGroupId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId'
+    hgmlcCallBackUri:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    ldrReference:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrReference'
+    lmfIdentification:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LMFIdentification'
+    amfId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/AmfId'
+
+LocUpdateData:
+  type: object
+  required:
+    - locationRequestType
+    - locationEstimate
+    - ageOfLocationEstimate
+    - accuracyFulfilmentIndicator
+    - lcsQosClass
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    pseudonymIndicator:
+      $ref: '#/components/schemas/PseudonymIndicator'
+    locationRequestType:
+      $ref: '#/components/schemas/LocationRequestType'
+    locationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea'
+    ageOfLocationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AgeOfLocationEstimate'
+    accuracyFulfilmentIndicator:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AccuracyFulfilmentIndicator'
+    civicAddress:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress'
+    lcsQosClass:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LcsQosClass'
+    externalClientIdentification:
+      $ref: '#/components/schemas/ExternalClientIdentification'
+    afd:
+      type: string
+    gmlcNumber:
+      type: string
+      pattern: '^[0-9]{5,15}$'
+    lcsServiceType:
+      $ref: '#/components/schemas/LcsServiceTypeId'
+
+EventNotifyData:
+  type: object
+  required:
+    - eventNotifyDataType
+    - ldrReference
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    ldrReference:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LdrReference'
+    eventNotifyDataType:
+      $ref: '#/components/schemas/EventNotifyDataType'
+    locationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea'
+```
+
+```
+civicAddress:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress'
+ageOfLocationEstimate:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AgeOfLocationEstimate'
+positioningDataList:
+  type: array
+  items:
+    $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/PositioningMethodAndUsage'
+  minItems: 1
+gnssPositioningDataList:
+  type: array
+  items:
+    $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GnssPositioningMethodAndUsage'
+  minItems: 1
+lmfIdentification:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LMFIdentification'
+amfId:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/AmfId'
+terminationCause:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/TerminationCause'
+velocityEstimate:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/VelocityEstimate'
+altitude:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/Altitude'
+targetNode:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId'
+accuracyFulfilmentIndicator:
+  $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AccuracyFulfilmentIndicator'
+failureCause:
+  $ref: '#/components/schemas/FailureCause'
+
+UePrivacyRequirements:
+  type: object
+  properties:
+    lcsServiceAuthInfo:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/LcsServiceAuth'
+    codeWordCheck:
+      type: boolean
+
+LocUpdateNotification:
+  type: object
+  required:
+    - locationRequestType
+    - locationEstimate
+    - ageOfLocationEstimate
+    - accuracyFulfilmentIndicator
+    - lcsQosClass
+  properties:
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    locationRequestType:
+      $ref: '#/components/schemas/LocationRequestType'
+    locationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea'
+    ageOfLocationEstimate:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AgeOfLocationEstimate'
+    accuracyFulfilmentIndicator:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AccuracyFulfilmentIndicator'
+    civicAddress:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/CivicAddress'
+    lcsQosClass:
+      $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/LcsQosClass'
+    afId:
+      type: string
+    serviceIdentity:
+      $ref: '#/components/schemas/ServiceIdentity'
+
+LocUpdateSubs:
+  type: object
+  required:
+    - nfInstanceId
+    - notifURI
+  properties:
+    nfInstanceId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId'
+    notifURI:
+```
+
+```
+
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+
+EventNotifyDataExt:
+  allOf:
+    - $ref: '#/components/schemas/EventNotifyData'
+    - $ref: '#/components/schemas/EventNotifyDataAdditionalInfo'
+
+EventNotifyDataAdditionalInfo:
+  type: object
+  properties:
+    addEventDataList:
+      type: array
+      items:
+        $ref: '#/components/schemas/EventNotifyData'
+      minItems: 1
+
+AreaEventInfoAddition:
+  type: object
+  properties:
+    geoAreaList:
+      type: array
+      items:
+        $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/GeographicArea'
+      minItems: 1
+    ignoreAreaDefInd:
+      type: boolean
+      default: false
+
+AreaEventInfoExt:
+  allOf:
+    - $ref: 'TS29572_Nlmf_Location.yaml#/components/schemas/AreaEventInfo'
+    - $ref: '#/components/schemas/AreaEventInfoAddition'
+
+#
+# SIMPLE TYPES
+#
+ServiceIdentity:
+  type: string
+ExternalClientIdentification:
+  type: string
+CodeWord:
+  type: string
+E164CountryCodeOfGeographicArea:
+  type: string
+LcsServiceTypeId:
+  description: LCS Service Type Id.
+  type: integer
+  minimum: 0
+  maximum: 127
+
+#
+# ENUMS
+#
+PseudonymIndicator:
+  anyOf:
+    - type: string
+      enum:
+        - PSEUDONYM_REQUESTED
+        - PSEUDONYM_NOT_REQUESTED
+    - type: string
+LocationRequestType:
+  anyOf:
+    - type: string
+      enum:
+        - NI_LR
+        - MT_LR
+        - MO_LR
+    - type: string
+LocationTypeRequested:
+  anyOf:
+    - type: string
+      enum:
+        - CURRENT_LOCATION
+        - CURRENT_OR_LAST_KNOWN_LOCATION
+
+```
+
+- INITIAL\_LOCATION
+- NOTIFICATION\_VERIFICATION\_ONLY
+- type: string
+
+EventNotifyDataType:
+
+- anyOf:
+  - type: string
+  - enum:
+    - UE\_AVAILABLE
+    - PERIODIC
+    - ENTERING\_INTO\_AREA
+    - LEAVING\_FROM\_AREA
+    - BEING\_INSIDE\_AREA
+    - MOTION
+    - MAXIMUM\_INTERVAL\_EXPIRATION\_EVENT
+    - LOCATION\_CANCELLATION\_EVENT
+    - ACTIVATION\_OF\_DEFERRED\_LOCATION
+    - UE\_MOBILITY\_FOR\_DEFERRED\_LOCATION
+    - 5GC\_MT\_LR
+  - type: string
+
+FailureCause:
+
+- anyOf:
+  - type: string
+  - enum:
+    - POSITIONING\_DENIED
+    - UNSUPPORTED\_BY\_UE
+    - NOT\_REGISTERED\_UE
+    - UNSPECIFIED
+  - type: string
+
+SuccessType:
+
+- anyOf:
+  - type: string
+  - enum:
+    - SUCCESS\_COMPLETELY
+    - SUCCESS\_PARTIALLY
+  - type: string
+
+# Annex B (informative): Change history
+
+| Change history |         |                                                                  |      |     |     |                                                                                          |             |
+|----------------|---------|------------------------------------------------------------------|------|-----|-----|------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc                                                             | CR   | Rev | Cat | Subject/Comment                                                                          | New version |
+| 2019-04        | CT4#90  | C4-191340                                                        |      |     |     | Initial Draft of Gateway Mobile Location Services                                        | 0.1.0       |
+| 2019-05        | CT4#91  | C4-192485                                                        |      |     |     | V0.2.0                                                                                   | 0.2.0       |
+| 2019-09        | CT4#93  | C4-193845                                                        |      |     |     | Implementation of pCRs agreed at CT4#93                                                  | 0.3.0       |
+| 2019-10        | CT4#94  | C4-194555                                                        |      |     |     | Implementation of pCRs agreed at CT4#94                                                  | 0.4.0       |
+| 2019-11        | CT4#95  | C4-195413, C4-195409, C4-195296                                  |      |     |     | Implementation of pCRs agreed at CT4#95                                                  | 0.5.0       |
+| 2019-12        | CT#86   | CP-193065                                                        |      |     |     | TS presented for information                                                             | 1.0.0       |
+| 2020-03        | CT4#96e | C4-200725, C4-200727, C4-200943, C4-200993, C4-200995, C4-201286 |      |     |     | Implementation of pCRs agreed at CT4#96e                                                 | 1.1.0       |
+| 2020-03        | CT#87e  | CP-200060                                                        |      |     |     | TS presented for approval                                                                | 2.0.0       |
+| 2020-03        | CT#87e  |                                                                  |      |     |     | Approved at CT87e                                                                        | 16.0.0      |
+| 2020-04        | CT#87e  | C4-202409                                                        | 0001 | 1   | F   | Correct the errors                                                                       | 16.1.0      |
+| 2020-04        | CT#87e  | C4-202325                                                        | 0003 | -   | F   | Miscellaneous corrections on TS 29.515                                                   | 16.1.0      |
+| 2020-04        | CT#87e  | C4-202326                                                        | 0004 | -   | F   | Removing pseudonym of UE                                                                 | 16.1.0      |
+| 2020-04        | CT#87e  | C4-202532                                                        | 0005 | 1   | F   | UE Privacy Requirements Corrections                                                      | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203181                                                        | 0006 | -   | F   | Error corrections                                                                        | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203540                                                        | 0007 | 1   | F   | Storage of YAML files in ETSI Forge                                                      | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203524                                                        | 0008 | 1   | F   | Correct the Example Consumer(s) in Table 5.1-1                                           | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203269                                                        | 0010 | -   | F   | LDRreference                                                                             | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203360                                                        | 0003 | 1   | F   | Miscellaneous corrections on TS 29.515                                                   | 16.1.0      |
+| 2020-06        | CT#88e  | C4-203645                                                        | 0011 | -   | F   | 3GPP TS 29.515 API Version Update                                                        | 16.1.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0012 | 1   | F   | API name correction                                                                      | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0014 | 1   | F   | Correction of CodeWord Checking for UE Notification and Verification                     | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0015 | 1   | F   | Correction of Notification or Verification only for UE Positioning                       | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0016 | 1   | F   | Corrections on EventNotify service operation                                             | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0017 | 1   | F   | Corrections on Application Errors in provide-location response                           | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202112                                                        | 0018 | 1   | F   | Corrections on LocationData                                                              | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202139                                                        | 0020 | 2   | F   | Essential correction to OpenAPI specification for LocationUpdateNotify service operation | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202096                                                        | 0021 | -   | F   | API version and External doc update                                                      | 16.2.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0022 | 1   | F   | CancelLocation for a group of UEs                                                        | 16.3.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0023 | 2   | F   | EventNotify for UEs in a group                                                           | 16.3.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0024 | 1   | F   | Provide Locations of a group of UEs                                                      | 16.3.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0028 | -   | F   | Essential corrections                                                                    | 16.3.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0029 | -   | F   | Storage of YAML files in 3GPP Forge                                                      | 16.3.0      |
+| 2020-11        | CT#90e  | CP-203050                                                        | 0030 | -   | F   | API version and External doc update                                                      | 16.3.0      |
+| 2021-03        | CT#91e  | CP-210037                                                        | 0033 | 1   | F   | HTTP 3xx redirection                                                                     | 16.4.0      |
+| 2021-03        | CT#91e  | CP-210041                                                        | 0032 | 1   | F   | Geographic Area                                                                          | 16.4.0      |
+| 2021-03        | CT#91e  | CP-210054                                                        | 0035 | -   | F   | 29.515 Rel-16 API version and External doc update                                        | 16.4.0      |
+| 2021-06        | CT#92e  | CP-211059                                                        | 0039 | 1   | F   | 3xx description correction for SCP                                                       | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211059                                                        | 0045 | 1   | F   | Redirect Responses                                                                       | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211063                                                        | 0037 | 1   | F   | LCS Service Type and External Client Type                                                | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211063                                                        | 0043 | -   | F   | Remove LcsServiceType                                                                    | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211063                                                        | 0049 | -   | F   | Wrong data type name                                                                     | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211073                                                        | 0051 | -   | F   | 29.515 Rel-16 API version and External doc update                                        | 16.5.0      |
+| 2021-09        | CT#93e  | C4-214711                                                        | 0055 | 1   | F   | LCS Service Type                                                                         | 16.6.0      |
+| 2021-09        | CT#93e  | C4-214788                                                        | 0058 | -   | F   | 29.515 Rel-16 API version and External doc update                                        | 16.6.0      |
+| 2021-12        | CT#94e  | C4-216163                                                        | 0062 | -   | F   | Correct the table name of SuccessType                                                    | 16.7.0      |
+| 2021-12        | CT#94e  | C4-216519                                                        | 0064 | 1   | F   | Add the missing pseudonymIndicator IE in OpenAPI                                         | 16.7.0      |
+| 2021-12        | CT#94e  | C4-216533                                                        | 0066 | 1   | F   | Information for HGMLC Discovery                                                          | 16.7.0      |
+| 2021-12        | CT#94e  | CP-213173                                                        | 0068 | 2   | F   | LCS Service Type in MO-LR                                                                | 16.7.0      |
+| 2021-12        | CT#94e  | C4-216498                                                        | 0071 | -   | F   | 29.515 Rel-16 API version and External doc update                                        | 16.7.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29523/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/29_series/29523/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a052829593c935aeb3815b547a33f349be5824f6
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41dee6ecac8c40de8d57423eb6e54ecf2ee8e80ef97cd839c0e04d28cf3d0614
+size 29495
diff --git a/marked/Rel-16/29_series/29523/2eab0ce7f9d9891a9f83f538ebd892f7_img.jpg b/marked/Rel-16/29_series/29523/2eab0ce7f9d9891a9f83f538ebd892f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b976f0b3faef6714299fad08080fa99b27065844
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/2eab0ce7f9d9891a9f83f538ebd892f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e50c0e2211cb3f50f19875e8f79e68105576b40b6e294713660e6f60144e53c
+size 17627
diff --git a/marked/Rel-16/29_series/29523/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-16/29_series/29523/5dfc130b129ace4df375839020a5700d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..803d42a978c50ce713a02ee217e93a87bfd3c101
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/5dfc130b129ace4df375839020a5700d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0fa9425eb8f8c2149b192acab9ac3afcd55e002aecd757a5a645d23768cc877c
+size 32538
diff --git a/marked/Rel-16/29_series/29523/6f119d066b5e51370df585ce69c94fb4_img.jpg b/marked/Rel-16/29_series/29523/6f119d066b5e51370df585ce69c94fb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f91a63fcfbb3b0ca5ed7911d915c936d317a388
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/6f119d066b5e51370df585ce69c94fb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc360905db1a2d23d7888396cbdfbb021e7f42eda42544875c3b2148a62f9b1d
+size 10309
diff --git a/marked/Rel-16/29_series/29523/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/29_series/29523/853f59c89931a666c07903b31d098277_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6bcf4be8aafeef094097a86f7819d1dc84b101f
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/853f59c89931a666c07903b31d098277_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bc96cdfb863f34cd5efbc5ce90d0f6459bb6ebb9acbc93344b0e7a55637a1c6
+size 30465
diff --git a/marked/Rel-16/29_series/29523/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/29_series/29523/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b2253933f1bf6d908a9ee198e8f0b7ad2f139b8
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4af8d1b840f105c681fa62b42f8b3e3e731e903590daff8e49bf72f5da78d5fe
+size 5272
diff --git a/marked/Rel-16/29_series/29523/ee8536b235eb6aad21e2048fd5308900_img.jpg b/marked/Rel-16/29_series/29523/ee8536b235eb6aad21e2048fd5308900_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0e37d23493a57cb5c3dbdae5f283d939d72de0d9
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/ee8536b235eb6aad21e2048fd5308900_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5223beea5f03abd72b043b9815710863a8361dd96e6fad0865c2833834b1ed84
+size 29776
diff --git a/marked/Rel-16/29_series/29523/raw.md b/marked/Rel-16/29_series/29523/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f02a60e134be573c0ede66ff1a3df8e5b3c0d889
--- /dev/null
+++ b/marked/Rel-16/29_series/29523/raw.md
@@ -0,0 +1,1707 @@
+
+
+
+
+Error! No  
+text of
+
+Error! No text of specified style in  
+document.
+
+# Contents
+
+|                                                                               |    |
+|-------------------------------------------------------------------------------|----|
+| Foreword .....                                                                | 5  |
+| 1 Scope.....                                                                  | 6  |
+| 2 References.....                                                             | 6  |
+| 3 Definitions, symbols and abbreviations.....                                 | 7  |
+| 3.1 Definitions.....                                                          | 7  |
+| 3.2 Abbreviations .....                                                       | 7  |
+| 4 Npcf_EventExposure Service .....                                            | 8  |
+| 4.1 Service Description .....                                                 | 8  |
+| 4.1.1 Overview .....                                                          | 8  |
+| 4.1.2 Service Architecture .....                                              | 8  |
+| 4.1.3 Network Functions .....                                                 | 9  |
+| 4.1.3.1 Policy Control Function (PCF) .....                                   | 9  |
+| 4.1.3.2 NF Service Consumers .....                                            | 9  |
+| 4.2 Service Operations .....                                                  | 9  |
+| 4.2.1 Introduction .....                                                      | 9  |
+| 4.2.2 Npcf_EventExposure_Subscribe service operation.....                     | 10 |
+| 4.2.2.1 General.....                                                          | 10 |
+| 4.2.2.2 Creating a new subscription.....                                      | 10 |
+| 4.2.2.3 Modifying an existing subscription .....                              | 12 |
+| 4.2.3 Npcf_EventExposure_UnSubscribe service operation.....                   | 13 |
+| 4.2.3.1 General.....                                                          | 13 |
+| 4.2.3.2 Unsubscription from event notifications.....                          | 13 |
+| 4.2.4 Npcf_EventExposure_Notify service operation.....                        | 14 |
+| 4.2.4.1 General.....                                                          | 14 |
+| 4.2.4.2 Notification about subscribed events.....                             | 14 |
+| 5 Npcf_EventExposure Service API.....                                         | 16 |
+| 5.1 Introduction .....                                                        | 16 |
+| 5.2 Usage of HTTP.....                                                        | 16 |
+| 5.2.1 General .....                                                           | 16 |
+| 5.2.2 HTTP standard headers .....                                             | 16 |
+| 5.2.2.1 General.....                                                          | 16 |
+| 5.2.2.2 Content type .....                                                    | 16 |
+| 5.2.3 HTTP custom headers .....                                               | 16 |
+| 5.2.3.1 General.....                                                          | 16 |
+| 5.3 Resources .....                                                           | 17 |
+| 5.3.1 Resource Structure.....                                                 | 17 |
+| 5.3.2 Resource: Policy Control Events Subscriptions (Collection).....         | 17 |
+| 5.3.2.1 Description.....                                                      | 17 |
+| 5.3.2.2 Resource definition.....                                              | 17 |
+| 5.3.2.3 Resource Standard Methods .....                                       | 17 |
+| 5.3.2.3.1 POST .....                                                          | 17 |
+| 5.3.2.4 Resource Custom Operations.....                                       | 18 |
+| 5.3.3 Resource: Individual Policy Control Events Subscription (Document)..... | 18 |
+| 5.3.3.1 Description.....                                                      | 18 |
+| 5.3.3.2 Resource definition.....                                              | 18 |
+| 5.3.3.3 Resource Standard Methods .....                                       | 18 |
+| 5.3.3.3.1 GET .....                                                           | 18 |
+| 5.3.3.3.2 PUT .....                                                           | 19 |
+| 5.3.3.3.3 DELETE.....                                                         | 20 |
+| 5.3.3.4 Resource Custom Operations.....                                       | 21 |
+| 5.4 Custom Operations without associated resources .....                      | 21 |
+| 5.5 Notifications.....                                                        | 21 |
+| 5.5.1 General .....                                                           | 21 |
+| 5.5.2 Policy Control Event Notification .....                                 | 22 |
+| 5.5.2.1 Description.....                                                      | 22 |
+| 5.5.2.2 Target URI .....                                                      | 22 |
+
+5.5.2.3 Standard Methods ..... 22
+
+5.5.2.3.1 POST ..... 22
+
+5.6 Data Model..... 23
+
+5.6.1 General ..... 23
+
+5.6.2 Structured data types ..... 24
+
+5.6.2.1 Introduction..... 24
+
+5.6.2.2 Type PcEventExposureSubsc ..... 25
+
+5.6.2.3 Type PcEventExposureNotif ..... 25
+
+5.6.2.4 Type ReportingInformation ..... 26
+
+5.6.2.5 Type ServiceIdentification..... 26
+
+5.6.2.6 Type EthernetFlowInfo ..... 27
+
+5.6.2.7 Type IpFlowInfo ..... 27
+
+5.6.2.8 Type PcEventNotification..... 28
+
+5.6.2.9 Type PduSessionInformation..... 29
+
+5.6.3 Simple data types and enumerations ..... 29
+
+5.6.3.1 Introduction..... 29
+
+5.6.3.2 Simple data types ..... 29
+
+5.6.3.3 Enumeration: PcEvent ..... 29
+
+5.7 Error handling ..... 29
+
+5.7.1 General ..... 29
+
+5.7.2 Protocol Errors..... 30
+
+5.7.3 Application Errors ..... 30
+
+5.8 Feature negotiation..... 30
+
+5.9 Security..... 30
+
+**Annex A (normative): OpenAPI specification ..... 31**
+
+A.1 General..... 31
+
+A.2 Npcf\_EventExposure API..... 31
+
+Annex B (informative): Change history..... 38
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Policy Control Event Exposure Service of the 5G System. It provides stage 3 protocol definitions, message flows and specifies the API for the Npcf Event Exposure service.
+
+The 5G System stage 2 architecture and the procedures are specified in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4].
+
+The 5G System stage 3 call flows are provided in 3GPP TS 29.513 [8].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [5] and 3GPP TS 29.501 [6].
+
+The Policy Control Event Exposure Service is provided by the Policy Control Function (PCF). This service exposes policy control events observed at the PCF.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
+- [5] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [7] OpenAPI: "OpenAPI 3.0.0 Specification", <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md>.
+- [8] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3".
+- [9] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
+- [10] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
+- [11] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3".
+- [12] 3GPP TS 29.514: "5G System; Policy Authorization Service; Stage 3".
+- [13] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
+- [14] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [15] 3GPP TS 29.508: "5G System; Session Management Event Exposure Service; Stage 3".
+- [16] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+
+- [17] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [18] IETF RFC 7807: "Problem Details for HTTP APIs".
+- [19] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [20] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [21] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [22] 3GPP TR 21.900: "Technical Specification Group working methods".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|         |                                                       |
+|---------|-------------------------------------------------------|
+| AF      | Application Function                                  |
+| AMF     | Access and Mobility Management Function               |
+| API     | Application Programming Interface                     |
+| ATSSS   | Access Traffic Steering, Switching and Splitting      |
+| DNN     | Data Network Name                                     |
+| ePDG    | evolved Packet Data Gateway                           |
+| GPSI    | Generic Public Subscription Identifier                |
+| HTTP    | Hypertext Transfer Protocol                           |
+| MA      | Multi-Access                                          |
+| NEF     | Network Exposure Function                             |
+| NID     | Network Identifier                                    |
+| NF      | Network Function                                      |
+| NRF     | Network Repository Function                           |
+| NWDAF   | Network Data Analytics Function                       |
+| OAM     | Operation And Maintenance                             |
+| PCF     | Policy Control Function                               |
+| RFSP    | RAT Frequency Selection Priority                      |
+| S-NSSAI | Single Network Slice Selection Assistance Information |
+| SMF     | Session Management Function                           |
+| SNPN    | Stand-alone Non-Public Network                        |
+| SUPI    | Subscription Permanent Identifier                     |
+| UDM     | Unified Data Management                               |
+| UDR     | Unified Data Repository                               |
+| URSP    | UE Route Selection Policy                             |
+
+# 4 Npcf\_EventExposure Service
+
+## 4.1 Service Description
+
+### 4.1.1 Overview
+
+The Policy Event Exposure Service, as defined in 3GPP TS 23.502 [3] and 3GPP TS 23.503 [4], is provided by the Policy Control Function (PCF).
+
+This service:
+
+- allows NF service consumers to subscribe, modify and unsubscribe from policy control events; and
+- notifies NF service consumers with a corresponding subscription about observed events on the PCF.
+
+The types of observed events include:
+
+- PLMN identifier notification; and
+- Access type change.
+
+The target of the event reporting may include a group of UE(s) or any UE (i.e. all UEs). When an event occurs, to which the NF service consumer has subscribed, the PCF reports the requested information to the NF service consumer based on the event reporting information definition requested by the NF service consumer (see 3GPP TS 23.502 [3], subclause 4.15.1).
+
+### 4.1.2 Service Architecture
+
+The 5G System Architecture is defined in 3GPP TS 23.501 [2]. The Policy and Charging related 5G architecture and signalling flows are also described in 3GPP TS 29.513 [8].
+
+The Policy Event Exposure Service (Npcf\_EventExposure) is part of the Npcf service-based interface exhibited by the Policy Control Function (PCF).
+
+The only known NF service consumer of the Npcf\_EventExposure service is the Network Exposure Function (NEF).
+
+The Npcf\_EventExposure service is provided by the PCF and consumed by NF service consumers (e.g. NEF), as shown in figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for reference point representation model.
+
+![Diagram of Npcf_EventExposure service Architecture, SBI representation. It shows a PCF box containing an Npcf oval, connected by a vertical line labeled Npcf_EventExposure to an NEF box.](6f119d066b5e51370df585ce69c94fb4_img.jpg)
+
+```
+graph TD; subgraph PCF; Npcf((Npcf)); end; Npcf --- NEF[NEF]; style PCF fill:none,stroke:none; style Npcf fill:none,stroke:none; style NEF fill:none,stroke:none;
+```
+
+Diagram of Npcf\_EventExposure service Architecture, SBI representation. It shows a PCF box containing an Npcf oval, connected by a vertical line labeled Npcf\_EventExposure to an NEF box.
+
+Figure 4.1.2-1: Npcf\_EventExposure service Architecture, SBI representation
+
+![Diagram showing the Npcf_EventExposure service Architecture, reference point representation. It consists of two rectangular boxes, PCF at the top and NEF at the bottom, connected by a vertical line labeled N30.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+graph TD; PCF[PCF] --- N30((N30)); N30 --- NEF[NEF];
+```
+
+Diagram showing the Npcf\_EventExposure service Architecture, reference point representation. It consists of two rectangular boxes, PCF at the top and NEF at the bottom, connected by a vertical line labeled N30.
+
+**Figure 4.1.2-2: Npcf\_EventExposure service Architecture, reference point representation**
+
+NOTE: The NWDAF can be a consumer of the Npcf\_EventExposure service to perform data collection. However, there is no data collected from the PCF by the NWDAF defined in this release of the specification.
+
+### 4.1.3 Network Functions
+
+#### 4.1.3.1 Policy Control Function (PCF)
+
+The PCF (Policy Control Function) is a functional element that encompasses policy control decision and flow based charging control functionalities as defined in 3GPP TS 29.512 [9], access and mobility policy decisions for the control of the UE Service Area Restrictions and RAT/RFSP control as defined in 3GPP TS 29.507 [10] and UE Policy decisions for the control of Access network discovery and selection policy and UE Route Selection Policy (URSP) as defined in 3GPP TS 29.525 [11].
+
+The policy control decision and flow based charging control functionalities enable the PCF to provide network control regarding the service data flow detection, gating, QoS and flow based charging (except credit management) towards the SMF/UPF. The PCF offers these capabilities to the NF service consumers (e.g. the AF and NEF) as defined in 3GPP TS 29.514 [12] and 3GPP TS 29.214 [13].
+
+The Policy Event Exposure Service enables the PCF to report policy control events observed in one or more PCF services to NF service consumers.
+
+#### 4.1.3.2 NF Service Consumers
+
+As indicated in subclause 4.1.2 above, the only known NF service consumer of the Npcf\_EventExposure service is the Network Exposure Function (NEF).
+
+The Network Exposure Function (NEF) is a functional element that supports the following functionalities:
+
+- The NEF securely exposes network capabilities and events provided by 3GPP NFs to AF.
+- The NEF provides a means for the AF to securely provide information to 3GPP network and can authenticate, authorize and assist in throttling the AF.
+- The NEF translates the information received from the AF to the one sent to internal 3GPP NFs, and vice versa.
+- The NEF supports exposing information (collected from other 3GPP NFs) to the AF.
+
+## 4.2 Service Operations
+
+### 4.2.1 Introduction
+
+Service operations defined for the Npcf\_EventExposure Service are shown in table 4.2.1-1.
+
+**Table 4.2.1-1: Npcf\_EventExposure Service Operations**
+
+| Service Operation Name         | Description                                                                                                                                                                                    | Initiated by              |
+|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| Npcf_EventExposure_Subscribe   | This service operation is used by an NF service consumer to subscribe for event notifications on a specified policy control event for a group of UE(s) or any UE, or to modify a subscription. | NF service consumer (NEF) |
+| Npcf_EventExposure_Unsubscribe | This service operation is used by an NF service consumer to unsubscribe from event notifications.                                                                                              | NF service consumer (NEF) |
+| Npcf_EventExposure_Notify      | This service operation is used by the PCF to report UE related policy control event(s) to the NF service consumer which has subscribed to the event report service.                            | PCF                       |
+
+### 4.2.2 Npcf\_EventExposure\_Subscribe service operation
+
+#### 4.2.2.1 General
+
+This service operation is used by an NF service consumer to subscribe for policy events notifications on a specified context for a group of UE(s) or any UE, or to modify an existing subscription.
+
+The following are the types of events for which a subscription can be made:
+
+- PLMN identifier notification; and
+- Change of Access Type.
+
+The following procedures using the Npcf\_EventExposure\_Subscribe service operation are supported:
+
+- creating a new subscription;
+- modifying an existing subscription.
+
+#### 4.2.2.2 Creating a new subscription
+
+Figure 4.2.2.2-1 illustrates the creation of a subscription.
+
+![Sequence diagram showing the creation of a subscription. An NF service consumer sends a POST request to the PCF, and the PCF responds with a 201 Created status.](ee8536b235eb6aad21e2048fd5308900_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF service consumer
+    participant PCF
+    Note right of NF service consumer: 1. POST .../subscriptions/
+    NF service consumer->>PCF: Request
+    Note left of PCF: 2. "201 Created"
+    PCF-->>NF service consumer: Response
+  
+```
+
+Sequence diagram showing the creation of a subscription. An NF service consumer sends a POST request to the PCF, and the PCF responds with a 201 Created status.
+
+**Figure 4.2.2.2-1: Creation of a subscription**
+
+To subscribe to event notifications, the NF service consumer shall send an HTTP POST request with: "{apiRoot}/npcf-eventexposure/v1/subscriptions/" as request URI as shown in figure 4.2.2.2-1, step 1, and the "PcEventExposureSubsc" data structure as request body.
+
+The "PcEventExposureSubsc" data structure shall include:
+
+- identification of the policy events to subscribe as "eventSubs" attribute;
+- indication of the UEs to which the subscription applies via:
+
+- a) identification of a group of UE(s) via a "groupId" attribute; or
+  - b) identification of any UE by omitting the "groupId" attribute.
+- a URI where to receive the requested notifications as "notifUri" attribute; and
+  - a Notification Correlation Identifier assigned by the NF service consumer for the requested notifications as "notifId" attribute.
+
+The "PcEventExposureSubsc" data structure also may include:
+
+- description of the event reporting information as "eventsRepInfo", which may include:
+  - a) event notification method (periodic, one time, on event detection) as "notifMethod" attribute;
+  - b) Maximum Number of Reports as "maxReportNbr" attribute;
+  - c) Monitoring Duration as "monDur" attribute;
+  - d) repetition period for periodic reporting as "repPeriod" attribute;
+  - e) immediate reporting indication as "immRep" attribute;
+  - f) sampling ratio as "sampRatio" attribute; and/or
+  - g) group reporting guard time as "grpRepTime" attribute.
+- if the supported feature "ExtendedSessionInformation" is supported, to filter the AF sessions for which the policy event report shall occur, the identification of the services one or more AF sessions may belong to as "filterServices" attribute, which may include per service identification:
+  - a) a list of ethernet flows in the "servEthFlows" attribute; or
+  - b) a list of IP flows in the "servIpFlows" attribute; and/or
+  - c) an AF application identifier in the "afAppId" attribute.
+- to filter the DNNs for which the policy event report shall occur, the identification of the DNNs in the "filterDnns" attribute; and
+- to filter the S-NSSAIs for which the policy event report shall occur, the identification of the S-NSSAIs in the "filterSnsais" attribute.
+
+If the PCF cannot successfully fulfil the received HTTP POST request due to an internal PCF error or an error in the HTTP POST request, the PCF shall send an HTTP error response as specified in subclause 5.7.
+
+Upon successful reception of the HTTP POST request with "{apiRoot}/npcf-eventexposure/v1/subscriptions/" as request URI and "PcEventExposureSubsc" data structure as request body, the PCF shall create a new "Individual Policy Events Subscription" resource, store the subscription and send a HTTP "201 Created" response as shown in figure 4.2.2.2-1, step 2. The PCF shall include in the "201 Created" response:
+
+- a Location header field; and
+- an "PcEventExposureSubsc" data type in the payload body.
+
+The Location header field shall contain the URI of the created individual application session context resource i.e. "{apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}".
+
+The "PcEventExposureSubsc" data type payload body shall contain the representation of the created "Individual Policy Events Subscription".
+
+When the "monDur" attribute is included in the response, it represents a server selected expiry time that is equal or less than a possible expiry time in the request.
+
+When the "immRep" attribute is included in the subscription and the subscribed policy control events are available, the PCF shall immediately notify the NF service consumer using the Npcf\_EventExposure\_Notify service operation, as described in subclause 4.2.4.2.
+
+When the sampling ratio as the "sampRatio" attribute is included in the subscription, the PCF shall select a random subset of UEs among the target UEs according to the sampling ratio and only report the event(s) related to the selected subset of UEs.
+
+When the group reporting guard time as the "grpRepTime" attribute is included in the subscription, the PCF shall accumulate all the event reports for the target UEs until the group reporting guard time expires. Then the PCF shall notify the NF service consumer using the Npcf\_EventExposure\_Notify service operation, as described in subclause 4.2.4.2.
+
+#### 4.2.2.3 Modifying an existing subscription
+
+Figure 4.2.2.3-1 illustrates the modification of an existing subscription.
+
+![Sequence diagram showing a PUT request from an NF service consumer to a PCF, followed by a 200 OK response.](853f59c89931a666c07903b31d098277_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF service consumer
+    participant PCF
+    NF service consumer->>PCF: 1. PUT .../subscriptions/{subscriptionId}
+    PCF->>NF service consumer: 2. "200 OK"
+
+```
+
+Sequence diagram showing a PUT request from an NF service consumer to a PCF, followed by a 200 OK response.
+
+**Figure 4.2.2.3-1: Modification of an existing subscription**
+
+To modify an existing subscription to event notifications, the NF service consumer shall send an HTTP PUT request with: "{apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}" as request URI, as shown in figure 4.2.2.3-1, step 1, where "{subscriptionId}" is the subscription correlation ID of the existing subscription. The "PcEventExposureSubsc" data structure is included as request body as described in subclause 4.2.2.2.
+
+NOTE 1: An alternate NF service consumer than the one that requested the generation of the subscription resource can send the PUT.
+
+NOTE 2: The "notifUri" attribute within the PcEventExposureSubsc data structure can be modified to request that subsequent notifications are sent to a new NF service consumer.
+
+If the PCF cannot successfully fulfil the received HTTP PUT request due to an internal PCF error or an error in the HTTP PUT request, the PCF shall send an HTTP error response as specified in subclause 5.7.
+
+If the feature "ES3XX" is supported, and the PCF determines the received HTTP PUT request needs to be redirected, the PCF shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [5].
+
+Upon successful reception of an HTTP PUT request with: "{apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}" as request URI and "PcEventExposureSubsc" data structure as request body, the PCF shall store the subscription and send an HTTP "200 OK" response with the "PcEventExposureSubsc" data structure as response body, as shown in figure 4.2.2.3-1, step 2.
+
+The "PcEventExposureSubsc" data structure payload body shall contain the representation of the modified "Individual Policy Events Subscription".
+
+When the "monDur" attribute is included in the response, it represents a NF service producer selected expiry time that is equal or less than a possible expiry time received in the request.
+
+When the "immRep" attribute is included in the updated subscription and the subscribed policy control events are available, the PCF shall immediately notify the NF service consumer using the Npcf\_EventExposure\_Notify service operation, as described in subclause 4.2.4.2.
+
+When the sampling ratio as the "sampRatio" attribute is included in the subscription, the PCF shall select a random subset of UEs among the target UEs according to the sampling ratio and only report the event(s) related to the selected subset of UEs.
+
+When the group reporting guard time as the "grpRepTime" attribute is included in the subscription, the PCF shall accumulate all the event reports for the target UEs until the group reporting guard time expires. Then the PCF shall notify the NF service consumer using the Npcf\_EventExposure\_Notify service operation, as described in subclause 4.2.4.2.
+
+### 4.2.3 Npcf\_EventExposure\_UnSubscribe service operation
+
+#### 4.2.3.1 General
+
+This service operation is used by an NF service consumer to unsubscribe from event notifications.
+
+The following procedure using the Npcf\_EventExposure\_UnSubscribe service operation is supported:
+
+- unsubscription from event notifications.
+
+#### 4.2.3.2 Unsubscription from event notifications
+
+Figure 4.2.3.2-1 illustrates the unsubscription from event notifications.
+
+![Sequence diagram showing the interaction between an NF service consumer and a PCF for unsubscription. Step 1: The consumer sends a DELETE request to the PCF. Step 2: The PCF responds with a 204 No Content status.](5dfc130b129ace4df375839020a5700d_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF service consumer
+    participant PCF
+    Note right of NF service consumer: 1. DELETE .../subscriptions/{subscriptionId}
+    NF service consumer->>PCF: Request
+    Note right of PCF: 2. "204 No Content"
+    PCF-->>NF service consumer: Response
+  
+```
+
+Sequence diagram showing the interaction between an NF service consumer and a PCF for unsubscription. Step 1: The consumer sends a DELETE request to the PCF. Step 2: The PCF responds with a 204 No Content status.
+
+Figure 4.2.3.2-1: Unsubscription from event notifications
+
+To unsubscribe from event notifications, the NF service consumer shall send an HTTP DELETE request with: "{apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}" as request URI, as shown in figure 4.2.3.2-1, step 1, where "{subscriptionId}" is the subscription correlation identifier of the existing resource subscription that is to be deleted.
+
+If the PCF cannot successfully fulfil the received HTTP DELETE request due to an internal PCF error or due to an error in the HTTP DELETE request, the PCF shall send the HTTP error response as specified in subclause 5.7.
+
+If the feature "ES3XX" is supported, and the PCF determines the received HTTP DELETE request needs to be redirected, the PCF shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [5].
+
+Upon successful reception of the HTTP DELETE request with: "{apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}" as request URI, the PCF shall remove the corresponding subscription and send an HTTP "204 No Content" response as shown in figure 4.2.3.2-1, step 2.
+
+### 4.2.4 Npcf\_EventExposure\_Notify service operation
+
+#### 4.2.4.1 General
+
+The Npcf\_EventExposure\_Notify service operation enables the PCF to notify the NF service consumers that the previously subscribed policy control event occurred.
+
+The following procedure using the Npcf\_EventExposure\_Notify service operation is supported:
+
+- notification about subscribed events.
+
+#### 4.2.4.2 Notification about subscribed events
+
+Figure 4.2.4.2-1 illustrates the notification about subscribed events.
+
+![Sequence diagram showing the notification about subscribed events between PCF and NF service consumer. Step 1: PCF sends a POST {notifUri} request to the NF service consumer. Step 2: The NF service consumer responds with a 204 No Content message.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+```
+
+sequenceDiagram
+    participant PCF
+    participant NF as NF service consumer
+    Note right of PCF: 1. POST {notifUri}
+    PCF->>NF: 1. POST {notifUri}
+    Note left of NF: 2. "204 No Content"
+    NF-->>PCF: 2. "204 No Content"
+  
+```
+
+Sequence diagram showing the notification about subscribed events between PCF and NF service consumer. Step 1: PCF sends a POST {notifUri} request to the NF service consumer. Step 2: The NF service consumer responds with a 204 No Content message.
+
+**Figure 4.2.4.2-1: Notification about subscribed events**
+
+If the PCF observes policy control related event(s) for which an NF service consumer has subscribed, the PCF shall send an HTTP POST request as shown in figure 4.2.4.2-1, step 1, with the "{notifUri}" as request URI containing the value previously provided by the NF service consumer within the corresponding subscription, and the "PcEventExposureNotif" data structure.
+
+The "PcEventExposureNotif" data structure shall include:
+
+- The notification correlation ID provided by the NF service consumer during the subscription as "notifId" attribute; and
+- information about the observed event(s) within the "eventNotifs" attribute that shall contain for each observed event an "PcEventNotification" data structure that shall include:
+  1. the Policy Control event as "event" attribute;
+  2. for an access type change:
+    - a) new access type as "accType" attribute;
+    - b) the new RAT type as "ratType" attribute, if applicable for the notified access type; and
+    - c) if the "ATSSS" feature is supported:
+      - i. if it is the first access type report for a PDU session, and both, 3GPP and non-3GPP access information is available, the "addAccessInfo" attribute. The "addAccessInfo" attribute contains the additional access type information, where the access type is encoded in the "accessType" attribute, and the RAT type is encoded in the "ratType" attribute when applicable for the notified access type;
+      - ii. if it is a subsequent access type change report:
+        - if a new access type is added to the MA PDU session, the "addAccessInfo" attribute with the added access type encoded in the "accessType" attribute, and the RAT type encoded in the "ratType" attribute when applicable for the notified access type;
+        - if an access type is released in the MA PDU session, the "relAccessInfo" attribute with the released access type encoded in the "accessType" attribute, and the RAT type encoded in the "ratType" attribute when applicable for the notified access type; and
+
+NOTE: For a MA PDU session, if the "ATSSS" feature is not supported by the AF, the PCF includes the "accessType" attribute and the "ratType" attribute with a currently active combination of access type and RAT type (if applicable for the notified access type). When both 3GPP and non-3GPP accesses are available, the PCF includes the information corresponding to the 3GPP access.
+
+- d) for EPC interworking scenarios, the ePDG address as "anGwAddr" attribute, if applicable for the notified access type;
+- 3. for a PLMN change:
+    - a) new network identity containing the PLMN Identifier and, if available, the NID in the "plmnId" attribute;
+  - 4. the identity of the affected UE in the "supi" attribute and, if available, in the "gpsi" attribute;
+  - 5. the time at which the event was observed encoded as "timeStamp" attribute;
+  - 6. if available, and if the feature "ExtendedSessionInformation" is supported, information about the PDU session involved in the reported event in the "pduSessInfo" attribute, that shall include:
+    - a) the S-NSSAI of the PDU session in the "snssai" attribute;
+    - b) the DNN of the PDU session in the "dnn" attribute; and
+    - c) the IPv4 address in the "ueIpv4" attribute and/or the IPv6 prefix in the "ueIpv6" attribute, or the Ethernet MAC address in the "ueMac" attribute; and
+
+if the IPv4 address is included in the "ueIpv4" attribute, may include the IP domain in the "ipDomain" attribute;
+  - 7. if available, and if the feature "ExtendedSessionInformation" is supported, information about the services involved in the reported event in the indicated PDU session in the "repServices" attribute, which may include per identified service:
+    - a) a list of Ethernet flows in the "servEthFlows" attribute which contains an impacted Ethernet flow number within the "flowNumber" attribute in each EthernetFlowInfo data structure; or
+    - b) a list of IP flows in the "servIpFlows" attribute which contains an impacted IP flow number within the "flowNumber" attribute in each IpFlowInfo data structure; and/or
+    - c) an AF application identifier in the "afAppId" attribute.
+
+If the NF service consumer cannot successfully fulfil the received HTTP POST request due to an internal error or an error in the HTTP POST request, the NF service consumer shall send an HTTP error response as specified in subclause 5.7.
+
+If the feature "ES3XX" is supported, and the NF service consumer determines the received HTTP POST request needs to be redirected, the NF service consumer shall send an HTTP redirect response as specified in subclause 6.10.9 of 3GPP TS 29.500 [5].
+
+Upon successful reception of the HTTP POST request with "{notifUri}" as request URI and a "PcEventExposureNotif" data structure as request body, the NF service consumer shall send a "204 No Content" HTTP response, as shown in figure 4.2.4.2-1, step 2, for a successful processing.
+
+# 5 Npcf\_EventExposure Service API
+
+## 5.1 Introduction
+
+The Npcf\_EventExposure Service shall use the Npcf\_EventExposure API.
+
+The API URI of the Npcf\_EventExposure API shall be:
+
+**{apiRoot}</apiName></apiVersion>/**
+
+The request URIs used in HTTP requests from the NF service consumer towards the PCF shall have the Resource URI structure defined in subclause 4.4.1 of 3GPP TS 29.501 [6], i.e.:
+
+**{apiRoot}</apiName></apiVersion></apiSpecificResourceUriPart>**
+
+with the following components:
+
+- The {apiRoot} shall be set as described in 3GPP TS 29.501 [6].
+- The <apiName> shall be "npcf-eventexposure".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in subclause 5.3.
+
+## 5.2 Usage of HTTP
+
+### 5.2.1 General
+
+HTTP/2, IETF RFC 7540 [16], shall be used as specified in subclause 5.2 of 3GPP TS 29.500 [5].
+
+HTTP/2 shall be transported as specified in subclause 5.3 of 3GPP TS 29.500 [5].
+
+The OpenAPI [7] specification of HTTP messages and content bodies for the Npcf\_EventExposure is contained in Annex A.
+
+### 5.2.2 HTTP standard headers
+
+#### 5.2.2.1 General
+
+See subclause 5.2.2 of 3GPP TS 29.500 [5] for the usage of HTTP standard headers.
+
+#### 5.2.2.2 Content type
+
+JSON, IETF RFC 8259 [17], shall be used as content type of the HTTP bodies specified in the present specification as specified in subclause 5.4 of 3GPP TS 29.500 [5]. The use of the JSON format shall be signalled by the content type "application/json".
+
+"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [18].
+
+### 5.2.3 HTTP custom headers
+
+#### 5.2.3.1 General
+
+The mandatory HTTP custom header fields specified in subclause 5.2.3.2 of 3GPP TS 29.500 [5] shall be applicable.
+
+In this Release of the specification, no specific custom headers are defined for the Npcf\_EventExposure API.
+
+## 5.3 Resources
+
+### 5.3.1 Resource Structure
+
+![Diagram showing the resource URI structure of the Npcf_EventExposure API. The root URI is {apiRoot}/npcf-eventexposure/v1. It branches to /subscriptions, which further branches to/{subscriptionId}.](2eab0ce7f9d9891a9f83f538ebd892f7_img.jpg)
+
+```
+graph TD; Root["{apiRoot}/npcf-eventexposure/v1"] --> Subscriptions["/subscriptions"]; Subscriptions --> SubscriptionId["/{subscriptionId}"];
+```
+
+Diagram showing the resource URI structure of the Npcf\_EventExposure API. The root URI is {apiRoot}/npcf-eventexposure/v1. It branches to /subscriptions, which further branches to/{subscriptionId}.
+
+**Figure 5.3.1-1: Resource URI structure of the Npcf\_EventExposure API**
+
+Table 5.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 5.3.1-1: Resources and methods overview**
+
+| Resource name                                 | Resource URI                    | HTTP method or custom operation | Description                                                                                                                       |
+|-----------------------------------------------|---------------------------------|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| Policy Control Events Subscriptions           | /subscriptions                  | POST                            | Subscription to notifications of policy control events and creation of an Individual Policy Control Events Subscription resource. |
+| Individual Policy Control Events Subscription | /subscriptions/{subscriptionId} | GET                             | Reads an Individual Policy Control Events Subscription resource.                                                                  |
+|                                               |                                 | PUT                             | Modifies an Individual Policy Control Events Subscription.                                                                        |
+|                                               |                                 | DELETE                          | Cancels an individual subscription to notifications of policy control events.                                                     |
+
+### 5.3.2 Resource: Policy Control Events Subscriptions (Collection)
+
+#### 5.3.2.1 Description
+
+The Policy Control Events Subscriptions resource represents all subscriptions of the Npcf\_EventExposure service at a given PCF.
+
+#### 5.3.2.2 Resource definition
+
+Resource URI: {apiRoot}/npcf-eventexposure/v1/subscriptions/
+
+This resource shall support the resource URI variables defined in table 5.3.2.2-1.
+
+**Table 5.3.2.2-1: Resource URI variables for this resource**
+
+| Name    | Data type | Definition        |
+|---------|-----------|-------------------|
+| apiRoot | string    | See subclause 5.1 |
+
+#### 5.3.2.3 Resource Standard Methods
+
+##### 5.3.2.3.1 POST
+
+This method shall support the URI query parameters specified in table 5.3.2.3.1-1.
+
+**Table 5.3.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 5.3.2.3.1-2 and the response data structures and response codes specified in table 5.3.2.3.1-3.
+
+**Table 5.3.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type             | P | Cardinality | Description                                                                                                |
+|-----------------------|---|-------------|------------------------------------------------------------------------------------------------------------|
+| PcEventExposure Subsc | M | 1           | Contains the information required for the creation of a new individual policy control events subscription. |
+
+**Table 5.3.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                   | P | Cardinality | Response codes | Description                                                                                |
+|-----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------|
+| PcEventExposure Subsc                                                                                                       | M | 1           | 201 Created    | Contains the representation of the Individual Policy Control Events Subscription resource. |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply. |   |             |                |                                                                                            |
+
+**Table 5.3.2.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                                |
+|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId} |
+
+#### 5.3.2.4 Resource Custom Operations
+
+None.
+
+### 5.3.3 Resource: Individual Policy Control Events Subscription (Document)
+
+#### 5.3.3.1 Description
+
+The Individual Policy Control Events Subscription resource represents a single subscription of the Npcf\_EventExposure service at a given PCF.
+
+#### 5.3.3.2 Resource definition
+
+Resource URI: {apiRoot}/npcf-eventexposure/v1/subscriptions/{subscriptionId}
+
+This resource shall support the resource URI variables defined in table 5.3.3.2-1.
+
+**Table 5.3.3.2-1: Resource URI variables for this resource**
+
+| Name           | Data type | Definition                                                |
+|----------------|-----------|-----------------------------------------------------------|
+| apiRoot        | string    | See subclause 5.1                                         |
+| subscriptionId | string    | Identif a subscription to the PCF event exposure service. |
+
+#### 5.3.3.3 Resource Standard Methods
+
+##### 5.3.3.3.1 GET
+
+This method shall support the URI query parameters specified in table 5.3.3.3.1-1.
+
+**Table 5.3.3.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 5.3.3.3.1-2 and the response data structures and response codes specified in table 5.3.3.3.1-3.
+
+**Table 5.3.3.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 5.3.3.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                 |
+|--------------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PcEventExposureSubs<br>c | M | 1           | 200 OK                 | A representation of the Individual Policy Control Events Subscription is returned.                                                                                                                                                                          |
+| RedirectResponse         | O | 0..1        | 307 Temporary Redirect | Temporary redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance.<br>Applicable if the feature "ES3XX" is supported. |
+| RedirectResponse         | O | 0..1        | 308 Permanent Redirect | Permanent redirection, during subscription retrieval. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance.<br>Applicable if the feature "ES3XX" is supported. |
+
+NOTE: The mandatory HTTP error status codes for the GET method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply.
+
+**Table 5.3.3.3.1-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+**Table 5.3.3.3.1-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+##### 5.3.3.3.2 PUT
+
+This method shall support the URI query parameters specified in table 5.3.3.3.2-1.
+
+**Table 5.3.3.3.2-1: URI query parameters supported by the PUT method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 5.3.3.3.2-2 and the response data structures and response codes specified in table 5.3.3.3.2-3.
+
+**Table 5.3.3.3.2-2: Data structures supported by the PUT Request Body on this resource**
+
+| Data type                | P | Cardinality | Description                                                                   |
+|--------------------------|---|-------------|-------------------------------------------------------------------------------|
+| PcEventExposureSubs<br>c | M | 1           | Modifies the existing Individual Policy Control Events Subscription resource. |
+
+**Table 5.3.3.3.2-3: Data structures supported by the PUT Response Body on this resource**
+
+| Data type                | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                 |
+|--------------------------|---|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PcEventExposureSubs<br>c | M | 1           | 200 OK                 | Successful case: The Individual Policy Control Events Subscription was modified and a representation is returned.                                                                                                                                           |
+| RedirectResponse         | O | 0..1        | 307 Temporary Redirect | Temporary redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
+| RedirectResponse         | O | 0..1        | 308 Permanent Redirect | Permanent redirection, during subscription modification. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance. Applicable if the feature "ES3XX" is supported. |
+
+NOTE: The mandatory HTTP error status codes for the PUT method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply.
+
+**Table 5.3.3.3.2-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+**Table 5.3.3.3.2-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+##### 5.3.3.3.3 DELETE
+
+This method shall support the URI query parameters specified in table 5.3.3.3.3-1.
+
+**Table 5.3.3.3.3-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 5.3.3.3.3-2 and the response data structures and response codes specified in table 5.3.3.3.3-3.
+
+**Table 5.3.3.3.3-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 5.3.3.3-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                   |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | Successful case: The Individual Policy Control Events Subscription resource matching the subscriptionId was deleted.                                                                                                                                          |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance.<br>Applicable if the feature "ES3XX" is supported. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection, during subscription termination. The response shall include a Location header field containing an alternative URI of the resource located in an alternative PCF (service) instance.<br>Applicable if the feature "ES3XX" is supported. |
+
+NOTE: The mandatory HTTP error status code for the DELETE method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [5] also apply.
+
+**Table 5.3.3.3-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+**Table 5.3.3.3-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                            |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located in an alternative PCF (service) instance.   |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the request is redirected |
+
+#### 5.3.3.4 Resource Custom Operations
+
+None.
+
+## 5.4 Custom Operations without associated resources
+
+None.
+
+## 5.5 Notifications
+
+### 5.5.1 General
+
+Notifications shall comply with subclause 6.2 of 3GPP TS 29.500 [5] and subclause 4.6.2.3 of 3GPP TS 29.501 [6].
+
+**Table 5.5.1-1: Notifications overview**
+
+| Notification                      | Callback URI | HTTP method or custom operation | Description (service operation)                 |
+|-----------------------------------|--------------|---------------------------------|-------------------------------------------------|
+| Policy Control Event Notification | {notifUri}   | POST                            | Notification of policy control event reporting. |
+
+### 5.5.2 Policy Control Event Notification
+
+#### 5.5.2.1 Description
+
+The Policy Control Event Notification is used by the PCF to report one or several observed policy control events to the NF service consumer that has subscribed to such notifications via the Individual Policy Control Events Subscription resource.
+
+#### 5.5.2.2 Target URI
+
+The Callback URI "{notifUri}" shall be used with the callback URI variables defined in table 5.5.2.2-1.
+
+**Table 5.5.2.2-1: Callback URI variables**
+
+| Name     | Data type | Definition                                                                                                                                                                           |
+|----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| notifUri | Uri       | The Notification Uri as assigned by the NF service consumer during the subscription service operation and described within the PcEventExposureSubsc data type (see table 5.6.2.2-1). |
+
+#### 5.5.2.3 Standard Methods
+
+##### 5.5.2.3.1 POST
+
+This method shall support the URI query parameters specified in table 5.5.2.3.1-1.
+
+**Table 5.5.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 5.5.2.3.1-2 and the response data structures and response codes specified in table 5.5.2.3.1-3.
+
+**Table 5.5.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type            | P | Cardinality | Description                                               |
+|----------------------|---|-------------|-----------------------------------------------------------|
+| PcEventExposureNotif | M | 1           | Provides Information about observed policy control events |
+
+**Table 5.5.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                                                | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                              |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a                                                                                                                                                      |   |             | 204 No Content         | The receipt of the Notification is acknowledged.                                                                                                                                                                                                                                                         |
+| RedirectResponse                                                                                                                                         | O | 0..1        | 307 Temporary Redirect | Temporary redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.<br>Applicable if the feature "ES3XX" is supported. |
+| RedirectResponse                                                                                                                                         | O | 0..1        | 308 Permanent Redirect | Permanent redirection, during event notification. The response shall include a Location header field containing an alternative URI representing the end point of an alternative NF consumer (service) instance where the notification should be sent.<br>Applicable if the feature "ES3XX" is supported. |
+| NOTE: In addition, the HTTP status codes which are specified as mandatory in table 5.2.7.1-1 of 3GPP TS 29.500 [5] for the POST method shall also apply. |   |             |                        |                                                                                                                                                                                                                                                                                                          |
+
+**Table 5.5.2.3.1-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                         |
+|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the notification request is redirected                                                 |
+
+**Table 5.5.2.3.1-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                         |
+|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI representing the end point of an alternative NF consumer (service) instance towards which the notification should be redirected. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance towards which the notification request is redirected                                                 |
+
+## 5.6 Data Model
+
+### 5.6.1 General
+
+This subclause specifies the application data model supported by the API.
+
+Table 5.6.1-1 specifies the data types defined for the Npcf\_EventExposure service based interface protocol.
+
+**Table 5.6.1-1: Npcf\_EventExposure specific Data Types**
+
+| Data type             | Section defined | Description                                                                                                             | Applicability              |
+|-----------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| EthernetFlowInfo      | 5.6.2.6         | Identification of an UL/DL ethernet flow.                                                                               | ExtendedSessionInformation |
+| IpFlowInfo            | 5.6.2.7         | Identification of an UL/DL IP flow.                                                                                     | ExtendedSessionInformation |
+| PcEvent               | 5.6.3.3         | Policy Control Events.                                                                                                  |                            |
+| PcEventExposureSubsc  | 5.6.2.2         | Represents an Individual Policy Events Subscription resource.                                                           |                            |
+| PcEventExposureNotif  | 5.6.2.3         | Describes notifications about Policy Control events that occurred in an Individual Policy Events Subscription resource. |                            |
+| PcEventNotification   | 5.6.2.8         | Represents the information reported for a Policy Control event.                                                         |                            |
+| PduSessionInformation | 5.6.2.9         | Represents PDU session identification information.                                                                      | ExtendedSessionInformation |
+| ReportingInformation  | 5.6.2.4         | Represents the type of reporting the subscription requires.                                                             |                            |
+| ServiceIdentification | 5.6.2.5         | Identification of the service to which the subscription applies.                                                        | ExtendedSessionInformation |
+
+Table 5.6.1-2 specifies data types re-used by the Npcf\_EventExposure service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Npcf\_EventExposure service based interface.
+
+**Table 5.6.1-2: Npcf\_EventExposure re-used Data Types**
+
+| <b>Data type</b>     | <b>Reference</b>    | <b>Comments</b>                                                                                  | <b>Applicability</b>       |
+|----------------------|---------------------|--------------------------------------------------------------------------------------------------|----------------------------|
+| AccessType           | 3GPP TS 29.571 [14] | Access Type.                                                                                     |                            |
+| AdditionalAccessInfo | 3GPP TS 29.512 [9]  | Indicates the combination of additional Access Type and RAT Type for MA PDU session              | ATSSS                      |
+| AfAppId              | 3GPP TS 29.514 [12] | AF application Identifier.                                                                       | ExtendedSessionInformation |
+| AnGwAddress          | 3GPP TS 29.514 [12] | Carries the control plane address of the EPC untrusted non-3GPP access network gateway. (NOTE 1) |                            |
+| DateTime             | 3GPP TS 29.571 [14] | Time stamp.                                                                                      |                            |
+| Dnn                  | 3GPP TS 29.571 [14] | Identifies a DNN.                                                                                |                            |
+| DurationSec          | 3GPP TS 29.571 [14] | Seconds of duration.                                                                             |                            |
+| EthFlowDescription   | 3GPP TS 29.514 [12] | Identifies an ethernet flow description. (NOTE 2)                                                | ExtendedSessionInformation |
+| FlowDescription      | 3GPP TS 29.514 [12] | Identifies an IP flow description.                                                               | ExtendedSessionInformation |
+| Gpsi                 | 3GPP TS 29.571 [14] | Generic Public Subscription Identifier.                                                          |                            |
+| GroupId              | 3GPP TS 29.571 [14] | Identifies a group of UEs.                                                                       |                            |
+| MacAddr48            | 3GPP TS 29.571 [14] | Mac Address of the UE.                                                                           | ExtendedSessionInformation |
+| NotificationMethod   | 3GPP TS 29.508 [15] | Represents the Notification Method.                                                              |                            |
+| PlmnIdNid            | 3GPP TS 29.571 [14] | Identifies the network: the PLMN Identifier and, for an SNPN, also the NID.                      |                            |
+| RatType              | 3GPP TS 29.571 [14] | RAT Type.                                                                                        |                            |
+| RedirectResponse     | 3GPP TS 29.571 [14] | Contains redirection related information.                                                        | ES3XX                      |
+| SamplingRatio        | 3GPP TS 29.571 [14] | Sampling Ratio.                                                                                  |                            |
+| Snssai               | 3GPP TS 29.571 [14] | Identifies a S-NSSAI                                                                             |                            |
+| Supi                 | 3GPP TS 29.571 [14] | Identifies the SUPI of the UE.                                                                   |                            |
+| SupportedFeatures    | 3GPP TS 29.571 [14] | Used to negotiate the applicability of the optional features defined in subclause 5.8.           |                            |
+| Uinteger             | 3GPP TS 29.571 [14] | Unsigned integer.                                                                                |                            |
+
+NOTE 1: "AnGwAddress" data structure is only used to encode the ePDG address and is only applicable to the 5GS and EPC/E-UTRAN interworking scenario as defined in 3GPP TS 29.512 [9], Annex B.
+
+NOTE 2: In order to support a set of MAC addresses with a specific range in the traffic filter, feature MacAddressRange as specified in clause 5.8 shall be supported.
+
+### 5.6.2 Structured data types
+
+#### 5.6.2.1 Introduction
+
+This subclause defines the structures to be used in resource representations.
+
+#### 5.6.2.2 Type PcEventExposureSubsc
+
+**Table 5.6.2.2-1: Definition of type PcEventExposureSubsc**
+
+| Attribute name | Data type                  | P | Cardinality | Description                                                                                                                                                                                                                      | Applicability              |
+|----------------|----------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| eventSubs      | array(PcEvent)             | M | 1..N        | Subscribed Policy Control events.                                                                                                                                                                                                |                            |
+| eventsReplInfo | ReportingInformation       | O | 0..1        | Represents the reporting requirements of the subscription.                                                                                                                                                                       |                            |
+| groupId        | GroupId                    | C | 0..1        | Represents an internal group identifier and identifies a group of UEs. It shall be present when the subscription is targeting a Group of UE(s).                                                                                  |                            |
+| filterDnns     | array(Dnn)                 | O | 1..N        | Represents the DNNs for which the policy event report shall apply. Each DNN is a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. If omitted it represents any DNN. |                            |
+| filterSnssais  | array(Snssai)              | O | 1..N        | Represents the S-NSSAIs for which the policy event report shall apply. If omitted it represents any S-NSSAI.                                                                                                                     |                            |
+| filterServices | array(ServiceIdentication) | O | 1..N        | Represents the services for which the policy event report shall apply. If omitted, the policy event report shall apply for all the active services.                                                                              | ExtendedSessionInformation |
+| notifUri       | Uri                        | M | 1           | Notification URI for Policy Control event reporting.                                                                                                                                                                             |                            |
+| notifId        | string                     | M | 1           | Notification Correlation ID assigned by the NF service consumer.                                                                                                                                                                 |                            |
+| suppFeat       | SupportedFeatures          | C | 0..1        | This IE represents a list of Supported features used as described in subclause 5.8. Shall be present in the HTTP POST request/response. (NOTE)                                                                                   |                            |
+
+NOTE: In the HTTP request, it represents the set of features supported by the NF service consumer. In the HTTP response, it represents the set of features supported by both the NF service consumer and the PCF.
+
+#### 5.6.2.3 Type PcEventExposureNotif
+
+**Table 5.6.2.3-1: Definition of type PcEventExposureNotif**
+
+| Attribute name | Data type                  | P | Cardinality | Description                                                                                                                         | Applicability |
+|----------------|----------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| notifId        | string                     | M | 1           | Notification Correlation ID assigned by the NF service consumer.                                                                    |               |
+| eventNotifs    | array(PcEventNotification) | M | 1..N        | Represents the Policy Control Events to be reported according to the subscription corresponding to the Notification Correlation ID. |               |
+
+#### 5.6.2.4 Type ReportingInformation
+
+**Table 5.6.2.4-1: Definition of type ReportingInformation**
+
+| Attribute name | Data type          | P | Cardinality | Description                                                                                                                                                                                                                                                | Applicability |
+|----------------|--------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| immRep         | boolean            | O | 0..1        | Indication of immediate reporting. If included, when it is set to true it indicates immediate reporting of the subscribed events, if available. Otherwise, reporting will occur when the event is met.                                                     |               |
+| notifMethod    | NotificationMethod | O | 0..1        | Represents the notification method (periodic, one time, on event detection). If "notifMethod" attribute is not supplied, the default value "ON_EVENT_DETECTION" applies.                                                                                   |               |
+| maxReportNbr   | UInteger           | O | 0..1        | Represents the maximum number of reports, after which the subscription ceases to exist (i.e., the reporting ends). It may be present for the "PERIODIC" and on "ON_EVENT_DETECTION" notification methods. If omitted, there is no limit.                   |               |
+| monDur         | DateTime           | C | 0..1        | Represents the time at which the subscription ceases to exist (i.e the subscription becomes invalid and the reporting ends). If omitted, there is no time limit. If present in the subscription request, it shall be present in the subscription response. |               |
+| repPeriod      | DurationSec        | O | 0..1        | Indicates the time interval between successive event notifications. It is supplied for notification method "PERIODIC".                                                                                                                                     |               |
+| sampRatio      | SamplingRatio      | O | 0..1        | Indicates the ratio of the random subset to target UEs, event reports only relates to the subset.                                                                                                                                                          |               |
+| grpRepTime     | DurationSec        | O | 0..1        | Indicates the time during which the the event reports detected for the concerned UEs are aggregated in a group, in order to be reported together to the NF service consumer.                                                                               |               |
+
+#### 5.6.2.5 Type ServiceIdentification
+
+**Table 5.6.2.5-1: Definition of type ServiceIdentification**
+
+| Attribute name                                                                                                                                                                                             | Data type               | P | Cardinality | Description                            | Applicability              |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---|-------------|----------------------------------------|----------------------------|
+| servEthFlows                                                                                                                                                                                               | array(EthernetFlowInfo) | C | 1..N        | Ethernet flows of a service.           | ExtendedSessionInformation |
+| servIpFlows                                                                                                                                                                                                | array(IpFlowInfo)       | C | 1..N        | IP flows of a service                  | ExtendedSessionInformation |
+| afAppId                                                                                                                                                                                                    | AfAppId                 | O | 0..1        | Contains an AF application identifier. | ExtendedSessionInformation |
+| NOTE: At least one of the "servEthFlows", "servIpFlows" or "afAppId" attributes shall be present. The "servEthFlows" attribute and the "servIpFlows" attribute shall not be both present at the same time. |                         |   |             |                                        |                            |
+
+#### 5.6.2.6 Type EthernetFlowInfo
+
+**Table 5.6.2.6-1: Definition of type EthernetFlowInfo**
+
+| Attribute name | Data type                 | P | Cardinality | Description                                                                                                                   | Applicability              |
+|----------------|---------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| ethFlows       | array(EthFlowDescription) | C | 1..2        | Contains the flow description for the Uplink and/or Downlink Ethernet flows. It shall be present in the subscription request. | ExtendedSessionInformation |
+| flowNumber     | integer                   | M | 1           | Identifies the ordinal number of the Ethernet flow.                                                                           | ExtendedSessionInformation |
+
+#### 5.6.2.7 Type IpFlowInfo
+
+**Table 5.6.2.7-1: Definition of type IpFlowInfo**
+
+| Attribute name | Data type              | P | Cardinality | Description                                                                                                            | Applicability              |
+|----------------|------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| ipFlows        | array(FlowDescription) | C | 1..2        | Contains the flow description for the Uplink and/or Downlink IP flows. It shall be present in the subscription request | ExtendedSessionInformation |
+| flowNumber     | integer                | M | 1           | Identifies the ordinal number of the IP flow.                                                                          | ExtendedSessionInformation |
+
+#### 5.6.2.8 Type PcEventNotification
+
+**Table 5.6.2.8-1: Definition of type PcEventNotification**
+
+| Attribute name | Data type             | P | Cardinality | Description                                                                                                                                                                                                 | Applicability              |
+|----------------|-----------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| event          | PcEvent               | M | 1..N        | Reported Policy Control event.                                                                                                                                                                              |                            |
+| accType        | AccessType            | C | 0..1        | Access Type. It shall be included when the reported PcEvent is "AC_TY_CH".                                                                                                                                  |                            |
+| addAccessInfo  | AdditionalAccessInfo  | O | 0..1        | Indicates the additional combination of Access Type and RAT Type available for MA PDU session. It may be present when the notified event is "AC_TY_CH" and the PDU session is a Multi-Access PDU session.   | ATSSS                      |
+| relAccessInfo  | AdditionalAccessInfo  | O | 0..1        | Indicates the release of a combination of Access Type and RAT Type available for MA PDU session. It may be present when the notified event is "AC_TY_CH" and the PDU session is a Multi-Access PDU session. | ATSSS                      |
+| anGwAddr       | AnGwAddress           | O | 0..1        | ePDG address. It shall be included if applicable when the reported PcEvent is "AC_TY_CH".                                                                                                                   |                            |
+| ratType        | RatType               | O | 0..1        | RAT Type. It shall be included if applicable when the reported PcEvent is "AC_TY_CH".                                                                                                                       |                            |
+| plmnId         | PlmnIdNid             | C | 0..1        | PLMN Identifier and, for an SNPN, also the NID. It shall be included when the reported PcEvent is "PLMN_CH".                                                                                                |                            |
+| supi           | Supi                  | C | 0..1        | SUPI of the UE. It shall be present if available.                                                                                                                                                           |                            |
+| gpsi           | Gpsi                  | O | 0..1        | Gpsi shall contain either an External Id or an MSISDN.                                                                                                                                                      |                            |
+| timeStamp      | DateTime              | M | 1           | Time at which the event is observed.                                                                                                                                                                        |                            |
+| pduSessionInfo | PduSessionInformation | O | 0..1        | Represents PDU session information related to the observed event.                                                                                                                                           | ExtendedSessionInformation |
+| repServices    | ServiceIdentification | O | 0..1        | Represents service information related to the observed event.                                                                                                                                               | ExtendedSessionInformation |
+
+#### 5.6.2.9 Type PduSessionInformation
+
+**Table 5.6.2.9-1: Definition of type PduSessionInformation**
+
+| Attribute name | Data type  | P | Cardinality | Description                                                                                                                             | Applicability              |
+|----------------|------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| snssai         | Snssai     | M | 1           | S-NSSAI of the PDU session.                                                                                                             | ExtendedSessionInformation |
+| dnn            | Dnn        | M | 1..N        | Dnn of the PDU session, a full DNN with both the Network Identifier and Operator Identifier, or a DNN with the Network Identifier only. | ExtendedSessionInformation |
+| uelpv4         | Ipv4Addr   | C | 0..1        | The IPv4 address of the served UE.<br>(NOTE 1)                                                                                          | ExtendedSessionInformation |
+| uelpv6         | Ipv6Prefix | C | 0..1        | The IPv6 prefix of the served UE.<br>(NOTE 1)                                                                                           | ExtendedSessionInformation |
+| ipDomain       | string     | O | 0..1        | Identifies the IP domain.<br>(NOTE 2)                                                                                                   | ExtendedSessionInformation |
+| ueMac          | MacAddr48  | C | 0..1        | UE MAC address.<br>(NOTE 1)                                                                                                             | ExtendedSessionInformation |
+
+NOTE 1: Either the served UE IP address (an Ipv4Addr or Ipv6Prefix or both if available) or UE MAC address shall be present.  
+NOTE 2: An "ipDomain" attribute, may be provided in combination with a "uelpv4" attribute.
+
+### 5.6.3 Simple data types and enumerations
+
+#### 5.6.3.1 Introduction
+
+This subclause defines simple data types and enumerations that can be referenced from data structures defined in the previous subclauses.
+
+#### 5.6.3.2 Simple data types
+
+The simple data types defined in table 5.6.3.2-1 shall be supported.
+
+**Table 5.6.3.2-1: Simple data types**
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+|           |                 |             |               |
+
+#### 5.6.3.3 Enumeration: PcEvent
+
+The enumeration PcEvent represents the policy control events that can be subscribed. It shall comply with the provisions defined in table 5.6.3.3-1.
+
+**Table 5.6.3.3-1: Enumeration PcEvent**
+
+| Enumeration value | Description        | Applicability |
+|-------------------|--------------------|---------------|
+| AC TY CH          | Access Type Change |               |
+| PLMN CH           | PLMN Change        |               |
+
+## 5.7 Error handling
+
+### 5.7.1 General
+
+HTTP error handling shall be supported as specified in subclause 5.2.4 of 3GPP TS 29.500 [5].
+
+For the Npcf\_EventExposure API, HTTP error responses shall be supported as specified in subclause 4.8 of 3GPP TS 29.501 [6].
+
+Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [5] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [5].
+
+In addition, the requirements in the following subclauses are applicable for the Npcf\_EventExposure API.
+
+### 5.7.2 Protocol Errors
+
+In this Release of the specification, there are no service specific protocol errors applicable for the Npcf\_EventExposure API.
+
+### 5.7.3 Application Errors
+
+The application errors defined for the Npcf\_EventExposure service are listed in table 5.7.3-1.
+
+**Table 5.7.3-1: Application errors**
+
+| Application Error | HTTP status code | Description |
+|-------------------|------------------|-------------|
+|                   |                  |             |
+
+## 5.8 Feature negotiation
+
+The optional features in table 5.8-1 are defined for the Npcf\_EventExposure API. They shall be negotiated using the extensibility mechanism defined in subclause 6.6 of 3GPP TS 29.500 [5].
+
+**Table 5.8-1: Supported Features**
+
+| Feature number | Feature Name               | Description                                                                                                                                                                                                                                                                                                                                                    |
+|----------------|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1              | ExtendedSessionInformation | Indicates the support of additional session information in the subscription and report of policy control event.                                                                                                                                                                                                                                                |
+| 2              | MacAddressRange            | Indicates the support of a set of MAC addresses with a specific range in the traffic filter.                                                                                                                                                                                                                                                                   |
+| 3              | ATSSS                      | Indicates the support of the report of the multiple access types of a MA PDU session.                                                                                                                                                                                                                                                                          |
+| 4              | ES3XX                      | Extended Support for 3xx redirections. This feature indicates the support of redirection for any service operation, according to Stateless NF procedures as specified in subclauses 6.5.3.2 and 6.5.3.3 of 3GPP TS 29.500 [5] and according to HTTP redirection principles for indirect communication, as specified in subclause 6.10.9 of 3GPP TS 29.500 [5]. |
+
+## 5.9 Security
+
+As indicated in 3GPP TS 33.501 [19] and 3GPP TS 29.500 [5], the access to the Npcf\_EventExposure API, based on local configuration, may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [20]), using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [21]) plays the role of the authorization server.
+
+If OAuth2 authorization is used, an NF Service Consumer, prior to consuming services offered by the Nnrf\_NFManagement API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [21], subclause 5.4.2.2.
+
+NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF where the NF Service Consumer invoked the discovery of the Npcf\_EventExposure service.
+
+The Npcf\_EventExposure API defines a single scope "npcf-eventexposure" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+The present Annex contains an OpenAPI [7] specification of HTTP messages and content bodies used by the Npcf\_EventExposure API.
+
+This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API.
+
+NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5B of the 3GPP TR 21.900 [22] and subclause 5.3.1 of the 3GPP TS 29.501 [6] for further information).
+
+## A.2 Npcf\_EventExposure API
+
+```
+openapi: 3.0.0
+info:
+  version: 1.1.2
+  title: Npcf_EventExposure
+  description: |
+    PCF Event Exposure Service.
+    © 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.523 V16.5.0; 5G System; Policy Control Event Exposure Service; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.523/
+
+servers:
+  - url: '{apiRoot}/npcf-eventexposure/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in subclause 4.4 of 3GPP TS 29.501
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - npcf-eventexposure
+
+paths:
+  /subscriptions:
+    post:
+      summary: Creates a new Individual Policy Control Events Subscription resource
+      operationId: PostPcEventExposureSubsc
+      tags:
+        - Policy Control Events Subscription (Collection)
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PcEventExposureSubsc'
+      responses:
+        '201':
+          description: Success
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/PcEventExposureSubsc'
+          headers:
+            Location:
+```
+
+```
+
+description: 'Contains the URI of the created individual policy control events
+subscription resource, according to the structure: {apiRoot}/npcf-
+eventexposure/v1/subscriptions/{subscriptionId}'
+required: true
+schema:
+  type: string
+'400':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+'401':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+'403':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+'404':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+'411':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+'413':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+'415':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+'429':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+'503':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+default:
+  $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+callbacks:
+  PcEventNotification:
+    '{ $request.body#/notifUri }':
+      post:
+        requestBody:
+          required: true
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/PcEventExposureNotif'
+responses:
+  '204':
+    description: No Content, Notification was successful
+  '307':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+  '308':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+  '400':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+  '401':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+  '403':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+  '404':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+  '411':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+  '413':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+  '415':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+  '429':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+/subscriptions/{subscriptionId}:
+  get:
+    summary: "Reads an existing Individual Policy Control Events Subscription"
+    operationId: GetPcEventExposureSubsc
+    tags:
+      - Individual Policy Control Events Subscription (Document)
+    parameters:
+      - name: subscriptionId
+        in: path
+        description: Policy Control Event Subscription ID
+        required: true
+
+```
+
+```
+
+    schema:
+      type: string
+  responses:
+    '200':
+      description: OK. Resource representation is returned
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/PcEventExposureSubsc'
+    '307':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+    '308':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '406':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/406'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+  put:
+    summary: "Modifies an existing Individual Policy Control Events Subscription "
+    operationId: PutPcEventExposureSubsc
+    tags:
+      - Individual Policy Control Events Subscription (Document)
+    requestBody:
+      required: true
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/PcEventExposureSubsc'
+    parameters:
+      - name: subscriptionId
+        in: path
+        description: Policy Control Event Subscription ID
+        required: true
+        schema:
+          type: string
+    responses:
+      '200':
+        description: OK. Resource was successfully modified and representation is returned
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/PcEventExposureSubsc'
+      '204':
+        description: No Content. Resource was successfully modified
+      '307':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+
+```
+
+-----
+
+-----
+
+```
+
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+delete:
+  summary: "Cancels an existing Individual Policy Control Events Subscription "
+  operationId: DeletePcEventExposureSubsc
+  tags:
+    - Individual Policy Control Events Subscription (Document)
+  parameters:
+    - name: subscriptionId
+      in: path
+      description: Policy Control Event Subscription ID
+      required: true
+      schema:
+        type: string
+  responses:
+    '204':
+      description: No Content. Resource was successfully deleted
+    '307':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+    '308':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            npcf-eventexposure: Access to the Npcf_EventExposure API.
+
+schemas:
+
+  PcEventExposureNotif:
+    type: object
+    properties:
+      notifId:
+        type: string
+      eventNotifs:
+        type: array
+        items:
+          $ref: '#/components/schemas/PcEventNotification'
+        minItems: 1
+    required:
+      - notifId
+      - eventNotifs
+
+  PcEventExposureSubsc:
+    type: object
+    properties:
+      eventSubs:
+        type: array
+        items:
+          $ref: '#/components/schemas/PcEvent'
+        minItems: 1
+
+```
+
+-----
+
+-----
+
+```
+eventsRepInfo:
+  $ref: '#/components/schemas/ReportingInformation'
+groupId:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId'
+filterDnns:
+  type: array
+  items:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
+  minItems: 1
+filterSnssais:
+  type: array
+  items:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai'
+  minItems: 1
+filterServices:
+  type: array
+  items:
+    $ref: '#/components/schemas/ServiceIdentification'
+  minItems: 1
+notifUri:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+notifId:
+  type: string
+suppFeat:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+required:
+- eventSubs
+- notifId
+- notifUri
+```
+
+### **ReportingInformation:**
+
+```
+type: object
+properties:
+  immRep:
+    type: boolean
+  notifMethod:
+    $ref: 'TS29508_Nsmf_EventExposure.yaml#/components/schemas/NotificationMethod'
+  maxReportNbr:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/UInteger'
+  monDur:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+  repPeriod:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
+  sampRatio:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/SamplingRatio'
+  grpRepTime:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
+```
+
+### **ServiceIdentification:**
+
+```
+type: object
+properties:
+  servEthFlows:
+    type: array
+    items:
+      $ref: '#/components/schemas/EthernetFlowInfo'
+    minItems: 1
+  servIpFlows:
+    type: array
+    items:
+      $ref: '#/components/schemas/IpFlowInfo'
+    minItems: 1
+  afAppId:
+    $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AfAppId'
+# All conditions in allOf must be met
+allOf:
+# First condition is that servEthFlows and servIpFlows are mutually exclusive
+- not:
+  required: [servEthFlows, servIpFlows]
+# Second condition is that at least one the servEthFlows, servIpFlows and afAppId shall be
+present
+- anyOf:
+- required: [servEthFlows]
+- required: [servIpFlows]
+- required: [afAppId]
+```
+
+### **EthernetFlowInfo:**
+
+```
+type: object
+properties:
+```
+
+```
+ethFlows:
+  type: array
+  items:
+    $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription'
+  minItems: 1
+  maxItems: 2
+  flowNumber:
+    type: integer
+  required:
+    - flowNumber
+
+IpFlowInfo:
+  type: object
+  properties:
+    ipFlows:
+      type: array
+      items:
+        $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/FlowDescription'
+      minItems: 1
+      maxItems: 2
+      flowNumber:
+        type: integer
+    required:
+      - flowNumber
+
+PcEventNotification:
+  type: object
+  properties:
+    event:
+      $ref: '#/components/schemas/PcEvent'
+    accType:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType'
+    addAccessInfo:
+      $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/AdditionalAccessInfo'
+    relAccessInfo:
+      $ref: 'TS29512_Npcf_SMPolicyControl.yaml#/components/schemas/AdditionalAccessInfo'
+    anGwAddr:
+      $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AnGwAddress'
+    ratType:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType'
+    plmnId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid'
+    supi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+    gsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    timeStamp:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+    pduSessionInfo:
+      $ref: '#/components/schemas/PduSessionInformation'
+    repServices:
+      $ref: '#/components/schemas/ServiceIdentification'
+    required:
+      - event
+      - timeStamp
+
+PduSessionInformation:
+  type: object
+  properties:
+    snssai:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SNSSAI'
+    dnn:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
+    ueIpv4:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr'
+    ueIpv6:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix'
+    ipDomain:
+      type: string
+    ueMac:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48'
+    required:
+      - snssai
+      - dnn
+    oneOf:
+      - required: [ueMac]
+      - anyOf:
+          - required: [ueIpv4]
+```
+
+- required: [ueIpv6]
+
+###### # Simple data types and Enumerations
+
+```
+
+    PcEvent:
+      anyOf:
+        - type: string
+          enum:
+            - AC_TY_CH
+            - PLMN_CH
+        - type: string
+    
+```
+
+# Annex B (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                       |             |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                       | New version |
+| 2018-11        |         |           |      |     |     | TS skeleton of Policy Event Exposure Service specification            | 0.0.0       |
+| 2018-11        | CT3#99  | C3-187718 |      |     |     | API Introduction and Usage of HTTP for new PCF TS                     | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187416 |      |     |     | Npcf_EventExposure Resources Definition and Error handling            | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187419 |      |     |     | Npcf_EventExposure, Policy Control Event Notification                 | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187675 |      |     |     | Npcf_EventExposure Service Description                                | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187717 |      |     |     | Npcf_EventExposure Service Operations and Data Structures             | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187734 |      |     |     | Npcf_EventExposure, OpenAPI                                           | 1.0.0       |
+| 2018-11        | CT3#99  | C3-187677 |      |     |     | Npcf_EventExposure, Security                                          | 1.0.0       |
+| 2018-12        | CT#82   | CP-183131 |      |     |     | TS sent to plenary for information and approval                       | 1.0.0       |
+| 2018-12        | CT#82   | CP-183166 |      |     |     | Npcf_EventExposure, OpenAPI                                           | 1.1.0       |
+| 2018-12        | CT#82   | CP-183251 |      |     |     | TS number assigned in the plenary for approval                        | 1.1.0       |
+| 2018-12        | CT#82   | CP-183253 |      |     |     | TS approved by plenary                                                | 15.0.0      |
+| 2019-03        | CP#83   | CP-190112 | 0001 | 1   | F   | Handling of IPdomain and UE addresses in Npcf_EventExposure service   | 15.1.0      |
+| 2019-03        | CT#83   | CP-190160 | 0002 | 3   | F   | Correction on Presence conditions for ServiceIdentification data type | 15.1.0      |
+| 2019-03        | CT#83   | CP-190112 | 0003 | 1   | F   | Handling of UE identities in Npcf_EventExposure service               | 15.1.0      |
+| 2019-03        | CP#83   | CP-190112 | 0004 | -   | F   | Correction on the handling of access type change                      | 15.1.0      |
+| 2019-03        | CT#83   | CP-190112 | 0005 | -   | F   | Correction of OpenAPI errors                                          | 15.1.0      |
+| 2019-03        | CP#83   | CP-190161 | 0006 | 1   | F   | OpenAPI Version number updates                                        | 15.1.0      |
+| 2019-06        | CT#84   | CP-191081 | 0007 | 1   | F   | Report ePDG address                                                   | 15.2.0      |
+| 2019-06        | CT#84   | CP-191081 | 0008 |     | F   | Storage of OpenAPI specification file                                 | 15.2.0      |
+| 2019-06        | CT#84   | CP-191081 | 0009 | 2   | F   | Correction to the notification procedure                              | 15.2.0      |
+| 2019-06        | CT#84   | CP-191081 | 0010 |     | F   | Correction on PCF event exposure service                              | 15.2.0      |
+| 2019-06        | CT#84   | CP-191081 | 0011 | 2   | F   | Precedence of OpenAPI file                                            | 15.2.0      |
+| 2019-06        | CT#84   | CP-191182 | 0012 | 2   | F   | Copyright note in YAML file                                           | 15.2.0      |
+| 2019-06        | CT#84   | CP-191081 | 0013 | 1   | F   | OpenAPI Version number update                                         | 15.2.0      |
+| 2019-09        | CT#85   | CP-192156 | 0014 | 1   | B   | Support of a set of MAC addresses in traffic filter                   | 16.0.0      |
+| 2019-09        | CT#85   | CP-192157 | 0015 | 1   | B   | Enhancement of event reporting information                            | 16.0.0      |
+| 2019-09        | CT#85   | CP-192173 | 0016 |     | F   | OpenAPI version update                                                | 16.0.0      |
+| 2020-03        | CT#87e  | CP-200207 | 0018 |     | B   | DNN Clarification                                                     | 16.1.0      |
+| 2020-06        | CT#88e  | CP-201252 | 0019 |     | B   | Adding support of NID                                                 | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201229 | 0020 | 3   | B   | Access Type Report for a MA PDU session                               | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201244 | 0021 | 1   | F   | Storage of YAML files in ETSI Forge                                   | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201256 | 0022 | 1   | F   | URI of the Npcf_EventExposure service                                 | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201223 | 0024 | 1   | A   | suppFeat within PcEventExposureSubsc                                  | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201244 | 0025 | 1   | F   | Supported headers, Resource Data type                                 | 16.2.0      |
+| 2020-06        | CT#88e  | CP-201255 | 0027 |     | F   | Update of OpenAPI version and TS version in externalDocs Field        | 16.2.0      |
+| 2020-09        | CT#89e  | CP-202055 | 0031 | 1   | A   | Resource URI for individual subscription                              | 16.3.0      |
+| 2020-12        | CT#90e  | CP-203075 | 0032 | 2   | F   | Essential corrections and alignments                                  | 16.4.0      |
+| 2020-12        | CT#90e  | CP-203139 | 0034 | 1   | F   | Storage of YAML files in ETSI Forge                                   | 16.4.0      |
+| 2020-12        | CT#90e  | CP-203110 | 0038 | 1   | F   | Correction to support Stateless NFs                                   | 16.4.0      |
+| 2020-12        | CT#90e  | CP-203152 | 0040 | -   | F   | Update of OpenAPI version and TS version in externalDocs field        | 16.4.0      |
+| 2021-06        | CT#92e  | CP-211200 | 0050 | 1   | F   | Redirect responses with "application/json" media type                 | 16.5.0      |
+| 2021-06        | CT#92e  | CP-211264 | 0054 | -   | F   | Update of OpenAPI version and TS version in externalDocs field        | 16.5.0      |
+| 2021-12        | CT#94e  | CP-213226 | 0062 | -   | F   | Corrections in PCF event exposure NF service consumers                | 16.6.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29524/raw.md b/marked/Rel-16/29_series/29524/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b988d4cc28f0496cf5777161b3178c04ee17a133
--- /dev/null
+++ b/marked/Rel-16/29_series/29524/raw.md
@@ -0,0 +1,393 @@
+Error! No  
+text of
+
+Error! No text of specified style in  
+document.
+
+# Contents
+
+|                                                                                                   |    |
+|---------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                    | 4  |
+| 1 Scope.....                                                                                      | 5  |
+| 2 References.....                                                                                 | 5  |
+| 3 Definitions, symbols and abbreviations.....                                                     | 6  |
+| 3.1 Abbreviations .....                                                                           | 6  |
+| 4 Mapping between 5GC interfaces causes and 5GMM Cause Codes by AMF .....                         | 6  |
+| 4.1 General .....                                                                                 | 6  |
+| 4.2 Mapping between Nausf services causes and 5GMM causes .....                                   | 6  |
+| 4.2.1 General .....                                                                               | 6  |
+| 4.3 Mapping between Nsmf services causes and 5GMM causes.....                                     | 8  |
+| 4.3.1 General .....                                                                               | 8  |
+| 4.3.2 Mapping between Nsmf_PDUSession service causes on N11 and 5GMM causes .....                 | 8  |
+| 4.3.2.1 General.....                                                                              | 8  |
+| 4.3.2.2 Mapping from HTTP to 5GMM Cause Values .....                                              | 8  |
+| 4.4 Mapping between Nudm services causes and 5GMM causes.....                                     | 9  |
+| 4.4.1 General .....                                                                               | 9  |
+| 4.4.2 Mapping between Nudm_UEContextManagement service causes on N8 and 5GMM causes.....          | 9  |
+| 4.4.2.1 General.....                                                                              | 9  |
+| 4.4.2.1 Mapping from HTTP to NAS cause values – Request rejected by UDM.....                      | 9  |
+| 4.5 Mapping between Neir services causes and 5GMM causes .....                                    | 9  |
+| 4.5.1 General .....                                                                               | 9  |
+| 4.5.2 Mapping between N5g-eir_EquipmentIdentityCheck Service causes on N17 and 5GMM causes .....  | 10 |
+| 4.5.2.1 General.....                                                                              | 10 |
+| 4.5.2.2 Mapping from HTTP to NAS cause values – Request accepted by EIR.....                      | 10 |
+| 4.6 Mapping between Nnssf services causes and 5GMM causes .....                                   | 10 |
+| 4.6.1 General .....                                                                               | 10 |
+| 4.6.2 Mapping between Nnssf_NSSelection service causes on N22 and 5GMM causes .....               | 10 |
+| 4.6.2.1 General.....                                                                              | 10 |
+| 4.6.2.2 Mapping from HTTP to 5GMM Cause Values .....                                              | 10 |
+| 5 Mapping between 5GC interfaces causes and 5GSM Cause Codes by SMF .....                         | 10 |
+| 5.1 General .....                                                                                 | 10 |
+| 5.2 Mapping between Npcf service causes on N7 and 5GSM causes.....                                | 11 |
+| 5.2.1 General .....                                                                               | 11 |
+| 5.2.2 Mapping between Npcf_SMSPolicyControl Service causes on N7 and 5GSM causes .....            | 11 |
+| 5.2.2.1 General.....                                                                              | 11 |
+| 5.2.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by PCF.....                     | 11 |
+| 5.3 Mapping between Nudm service causes on N10 and 5GSM causes.....                               | 11 |
+| 5.3.1 General .....                                                                               | 11 |
+| 5.3.2 Mapping between Nudm_UEContextManagement service causes on N10 and 5GSM causes .....        | 11 |
+| 5.3.2.1 General.....                                                                              | 11 |
+| 5.3.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures..... | 12 |
+| 5.4.1 General .....                                                                               | 12 |
+| 5.4.2 Mapping from N4 to 5GSM cause values .....                                                  | 12 |
+| Annex A (informative): Change history.....                                                        | 13 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document specifies the mapping:
+
+- performed by the AMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to the AMF and 5GMM Cause values sent to UEs;
+- performed by the SMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to SMF and 5GSM Cause values sent to UEs;
+- performed by the SMF between N4 errors returned by the UPF and 5GSM Cause values sent to UEs.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane Nodes".
+- [3] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+- [4] 3GPP TS 29.531: "5G System; Network Slice Selection Services; Stage 3".
+- [5] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
+- [6] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
+- [7] 3GPP TS 29.509: "5G System; Authentication Server Services; Stage 3".
+- [8] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3".
+- [9] 3GPP TS 29.508: "5G System, Session Management Event Exposure Service; Stage 3".
+- [10] 3GPP TS 29.540: "5G System; SMS Services; Stage3 ".
+- [11] 3GPP TS 29.511: "5G System; Equipment Identity Register Services; Stage 3".
+- [12] 3GPP TS 29.507: "5G System; Access and Mobility Policy Control Service; Stage 3".
+- [13] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3"
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|     |                 |
+|-----|-----------------|
+| 5GC | 5G Core Network |
+|-----|-----------------|
+
+|      |                                         |
+|------|-----------------------------------------|
+| AMF  | Access and Mobility Management Function |
+| HTTP | Hypertext Transfer Protocol             |
+| NF   | Network Function                        |
+| NSSF | Network Slice Selection Function        |
+| PCF  | Policy Control Function                 |
+| SMF  | Session Management Function             |
+| UDM  | Unified Data Management                 |
+
+# --- 4 Mapping between 5GC interfaces causes and 5GMM Cause Codes by AMF
+
+## 4.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by NF services contacted by the AMF and the 5GMM cause values sent to UEs.
+
+No mapping is required for:
+
+- the Nsmf\_SMService\_Activate, Nsmf\_SMService\_Deactivate and Nsmf\_SMService\_UplinkSMS operations described in 3GPP TS 29.540 [10].
+- the Npcf\_AMPolicyControl service operations described in 3GPP TS 29.507 [12].
+- the Npcf\_UEPolicyControl service operations described in 3GPP TS 29.525 [13].
+
+## 4.2 Mapping between Nausf services causes and 5GMM causes
+
+### 4.2.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by AUSF services to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.2.2 Mapping between Nausf\_UEAuthentication service causes on N12 and 5GMM causes
+
+#### 4.2.2.1. General
+
+This clause defines the mapping for the Nausf\_UEAuthentication service (see 3GPP TS 29.509 [7]). It also contains the mapping in case of a 200 OK is returned but the Authentication has failed.
+
+#### 4.2.2.2 Mapping from HTTP to 5GMM causes values – Request rejected by AUSF
+
+**Table .4.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by AUSF**
+
+| <b>HTTP status code on N12</b> | <b>Protocol or Application Error</b> | <b>5GMM cause to UE</b>                                                                                                                                                          |
+|--------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden                  | SERVING_NETWORK_NOT_AUTHORIZED       | Cause #11 – PLMN not allowed<br>Cause #73 – Serving network not authorized<br>Cause #12 – Tracking area not allowed<br>Cause #15 – No suitable cells in tracking area<br>(NOTE1) |
+|                                | AUTHENTICATION_REJECTED              | N/A (NOTE 2)                                                                                                                                                                     |
+|                                | INVALID_HN_PUBLIC_KEY_IDENTIFIER     | N/A (NOTE 2)                                                                                                                                                                     |
+|                                | INVALID_HN_PUBLIC_KEY_IDENTIFIER     | N/A (NOTE 2)                                                                                                                                                                     |
+| 404 Not Found                  | CONTEXT_NOT_FOUND                    | N/A (NOTE 2)                                                                                                                                                                     |
+|                                | USER_NOT_FOUND                       |                                                                                                                                                                                  |
+| 504 Gateway Timeout            | UPSTREAM_SERVER_ERROR                | N/A (NOTE 2)                                                                                                                                                                     |
+|                                | NETWORK_FAILURE                      | N/A (NOTE 2)                                                                                                                                                                     |
+| 500 Internal Server Error      | AV_GENERATION_PROBLEM                | N/A (NOTE 2)                                                                                                                                                                     |
+| 501 Not Implemented            | UNSUPPORTED_PROTECTION_SCHEME        | N/A (NOTE 2)                                                                                                                                                                     |
+
+NOTE 1: One of these 5GMM causes may be used.  
+NOTE 2: There is no corresponding mapping since the Authentication is rejected and the Authentication Reject message does not have a 5GMM cause.
+
+#### 4.2.2.3 Mapping from HTTP to 5GMM cause values – Request accepted by AUSF
+
+**Table .4.2.2.3-1: Mapping from HTTP to 5GMM cause values – Request accepted by AUSF**
+
+| <b>HTTP status code on N12</b> | <b>Protocol or Application Error</b>                                                                                            | <b>5GMM cause to UE</b> |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| 200 OK                         | The "authResult" in "ConfirmationDataResponse" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]). | Cause #3 – Illegal UE   |
+|                                | The "authResult" in "EapSession" is set to "AUTHENTICATION_FAILURE" (see clause 6.1.6.2.8 of 3GPP TS 29.509 [7]).               | Cause #3 – Illegal UE   |
+
+## 4.3 Mapping between Nsmf services causes and 5GMM causes
+
+### 4.3.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by SMF services to the AMF and the 5GMM cause values sent to UEs.
+
+The AMF may invoke SMF service operations upon receipt of:
+
+- 5GSM messages (e.g. PDU Session establishment request) piggybacked in 5GMM UL NAS TRANSPORT message;
+- 5GMM Service Request or Registration Request messages, to establish the user-plane resources of a PDU session.
+
+A 5GMM cause is defined in:
+
+- the DL NAS TRANSPORT message;
+- the PDU session reactivation result error cause IE of a REGISTRATION ACCEPT or SERVICE ACCEPT message;
+- the REGISTRATION REJECT or SERVICE REJECT message.
+
+The AMF shall support mapping the status code and/or Protocol or Application Error received from the SMF to a 5GMM cause code, where 3GPP TS 24.501 [3] requires a 5GMM Cause to be included in the 5GMM message sent to the UE.
+
+NOTE: REGISTRATION REJECT and SERVICE REJECT messages are rejected only due to 5GMM-specific reasons, i.e. not for problems specific to session management.
+
+### 4.3.2 Mapping between Nsmf\_PDUSession service causes on N11 and 5GMM causes
+
+#### 4.3.2.1 General
+
+This clause defines the mapping for the Nsmf\_PDUSession service (see 3GPP TS 29.502 [8]).
+
+#### 4.3.2.2 Mapping from HTTP to 5GMM Cause Values
+
+**Table 4.3.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by SMF**
+
+| HTTP status code on N11 | Protocol or Application Error                                                                                                                       | 5GMM cause to UE                                            |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
+| 200 OK                  | The upCnxState IE is set to DEACTIVATED and the Cause IE set to "INSUFFICIENT_UP_RESOURCES" (see clause 5.2.2.3.2.2 of 3GPP TS 29.502 [8]) (NOTE 2) | #92 - Insufficient user-plane resources for the PDU session |
+| 403 Forbidden           | OUT_OF_LADN_SERVICE_AREA                                                                                                                            | #43 - LADN not available                                    |
+| 403 Forbidden           | PRIORITIZED_SERVICES_ONLY                                                                                                                           | #28 - Restricted service area                               |
+| 404 Not Found           | CONTEXT_NOT_FOUND                                                                                                                                   | N/A (NOTE 1)                                                |
+|                         |                                                                                                                                                     |                                                             |
+|                         |                                                                                                                                                     |                                                             |
+|                         |                                                                                                                                                     |                                                             |
+| 504 Gateway Timeout     | NETWORK_FAILURE                                                                                                                                     | N/A (NOTE 1)                                                |
+
+NOTE 1: An N1 SM cause is included by the SMF in the HTTP error response in this case.  
+NOTE 2: This corresponds to the scenario where NG-RAN cannot establish user plane resources during the activation of the User Plane connection of a PDU session.
+
+## 4.4 Mapping between Nudm services causes and 5GMM causes
+
+### 4.4.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status codes and Protocol or Application Errors) returned by UDM services to AMF and the 5GMM cause values sent to UEs.
+
+### 4.4.2 Mapping between Nudm\_UEContextManagement service causes on N8 and 5GMM causes
+
+#### 4.4.2.1 General
+
+This clause defines the mapping for the Nudm\_UEContextManagement service is described in 3GPP TS 29.503 [5]).
+
+#### 4.4.2.1 Mapping from HTTP to NAS cause values – Request rejected by UDM
+
+**Table 4.4.2.1-1: Mapping from HTTP to 5GMM cause values – Request rejected by UDM**
+
+| HTTP status code on N8                                                                          | Protocol or Application Error | 5GMM cause to UE                                                                                                                              |
+|-------------------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden                                                                                   | UNKNOWN_5GS_SUBSCRIPTION      | #27 – N1 mode not allowed                                                                                                                     |
+|                                                                                                 | ACCESS_NOT_ALLOWED            | #15 "No suitable cells in tracking area", or<br>#12 "Tracking area not allowed" or<br>#72 – Non-3GPP access to 5GCN not allowed (NOTE)        |
+|                                                                                                 | RAT_NOT_ALLOWED               | #15 "No suitable cells in tracking area", or<br>#13 "Roaming not allowed in this tracking area", or<br>#12 "Tracking area not allowed" (NOTE) |
+|                                                                                                 | NO_PS_SUBSCRIPTION            | #7 – 5GS services not allowed                                                                                                                 |
+|                                                                                                 | ROAMING_NOT_ALLOWED           | #11 "PLMN not allowed" or<br>#13 "Roaming not allowed in this tracking area", (NOTE)                                                          |
+| 404 Not Found                                                                                   | CONTEXT_NOT_FOUND             | #9 "UE identity cannot be derived by the network"                                                                                             |
+| 404 Not Found                                                                                   | USER_NOT_FOUND                | #3 "Illegal UE"                                                                                                                               |
+| 422 Unprocessable Entity                                                                        | UNPROCESSABLE_REQUEST         | #111 protocol error unspecified                                                                                                               |
+| NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice. |                               |                                                                                                                                               |
+
+## 4.5 Mapping between Neir services causes and 5GMM causes
+
+### 4.5.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (status code and Protocol or Application Errors) returned by the EIR to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.5.2 Mapping between N5g-eir\_EquipmentIdentityCheck Service causes on N17 and 5GMM causes
+
+#### 4.5.2.1 General
+
+This clause defines the mapping for the N5g-eir\_EquipmentIdentityCheck service (see 3GPP TS 29.511 [11]).
+
+#### 4.5.2.2 Mapping from HTTP to NAS cause values – Request accepted by EIR
+
+**Table 4.5.2.2-1: Mapping from HTTP to 5GMM cause values – Request accepted by EIR**
+
+| HTTP Status on N17 | Protocol or Application information      | 5GMM cause to UE |
+|--------------------|------------------------------------------|------------------|
+| 200 OK             | Equipment Status is set to "BLACKLISTED" | #6 "Illegal ME"  |
+
+## 4.6 Mapping between Nnssf services causes and 5GMM causes
+
+### 4.6.1 General
+
+This clause defines the mapping performed by the AMF between HTTP responses (Status Code and Protocol or Application Errors) returned by the NSSF to the AMF and the 5GMM cause values sent to UEs.
+
+### 4.6.2 Mapping between Nnssf\_NSSelection service causes on N22 and 5GMM causes
+
+#### 4.6.2.1 General
+
+This clause defines the mapping for the Nnssf\_NSSelection service (see 3GPP TS 29.531 [4]).
+
+#### 4.6.2.2 Mapping from HTTP to 5GMM Cause Values
+
+**Table 4.6.2.2-1: Mapping from HTTP to 5GMM cause values – Request rejected by NSSF**
+
+| HTTP status code on N22 | Protocol or Application Error | 5GMM cause to UE                  |
+|-------------------------|-------------------------------|-----------------------------------|
+| 403 Forbidden           | SNSSAI NOT SUPPORTED          | #62 – No Network Slices available |
+
+# --- 5 Mapping between 5GC interfaces causes and 5GSM Cause Codes by SMF
+
+## 5.1 General
+
+This clause describes the mapping performed by the SMF between HTTP responses (status Code and Protocol or Application Errors) returned by NF services contacted by the SMF and the corresponding 5GSM cause values sent to UEs (in5GSMmessages).
+
+No mapping is required for the Nsmf\_PDUSession service over N11 since the SMF includes the 5GSM cause in 5GSM messages sent in N1 SM Information (see 3GPP TS 29.502 [5]).
+
+No mapping is required for the Nsmf\_PDUSession service over N16 since the 5GSM cause is generated at the H-SMF and provided to the V-SMF in N1 SM Information (see 3GPP TS 29.502 [9]).
+
+No mapping is required for the Nsmf\_EventExposure service specified in 3GPP TS 29.508 [9]
+
+## 5.2 Mapping between Npcf service causes on N7 and 5GSM causes
+
+### 5.2.1 General
+
+This clause defines the mapping performed by the SMF between HTTP responses (status code and Protocol or Application Errors) returned by the PCF to the SMF and the 5GSM causes sent to UEs.
+
+### 5.2.2 Mapping between Npcf\_SMPolicyControl Service causes on N7 and 5GSM causes
+
+#### 5.2.2.1 General
+
+This clause defines the mapping for the Npcf\_SMPolicyControl service (see 3GPP TS 29.512 [6]).
+
+#### 5.2.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by PCF
+
+**Table 5.2.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by PCF**
+
+| HTTP status code on N7 | Protocol or Application Error       | 5GSM cause to UE                                               |
+|------------------------|-------------------------------------|----------------------------------------------------------------|
+| 400 Bad Request        | USER_UNKNOWN                        | Cause #29 - User authentication or authorization failed        |
+|                        | ERROR_INITIAL_PARAMETERS            | Cause #31 - Request rejected, unspecified                      |
+|                        | ERROR_TRIGGER_EVENT                 | Cause #31 - Request rejected, unspecified                      |
+| 403 Forbidden          | ERROR_TRAFFIC_MAPPING_INFO_REJECTED | Cause #29 - User authentication or authorization failed        |
+|                        | ERROR_CONFLICTING_REQUEST           | Cause #67 - insufficient resources for specific slice and DNN  |
+|                        | POLICY_CONTEXT_DENIED               | Cause #29 - User authentication or authorization failed (NOTE) |
+|                        | VALIDATION_CONDITION_NOT_MET        | Cause #29 - User authentication or authorization failed        |
+
+NOTE: Upon receiving the cause POLICY CONTEXT DENIED, the SMF may reject the request, or it may accept the request based on the local policy.
+
+## 5.3 Mapping between Nudm service causes on N10 and 5GSM causes
+
+### 5.3.1 General
+
+This clause defines the mapping performed by the SMF between HTTP responses (status codes and Protocol or Application Errors) returned by the UDM to the SMF and the 5GSM causes sent to UEs.
+
+### 5.3.2 Mapping between Nudm\_UEContextManagement service causes on N10 and 5GSM causes
+
+#### 5.3.2.1 General
+
+This clause defines the mapping for the Nudm\_UEContextManagement service (see 3GPP TS 29.503 [5]).
+
+#### 5.3.2.2 Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures
+
+**Table 5.3.2.2-1: Mapping from HTTP to 5GSM cause values – Request rejected by UDM due to N10 failures**
+
+| HTTP status code on N10 | Protocol or Application Error | 5GSM cause to UE                                                                                                                                |
+|-------------------------|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| 403 Forbidden           | ROAMING_NOT_ALLOWED           | #29 "User authentication or authorization failed"                                                                                               |
+|                         | DNN_NOT_ALLOWED               | #27 "Missing or unknown DNN" or<br>#67 "Insufficient resources for specific slice and DNN"<br>#70 "Missing or unknown DNN in a slice"<br>(NOTE) |
+| 404 Not Found           | USER NOT FOUND                | #29 "User authentication or authorization failed"                                                                                               |
+
+NOTE: Any of those NAS Cause Code values may be sent to the UE, depending on operator's choice.
+
+## 5.4 Mapping between N4 causes and 5GSM causes
+
+### 5.4.1 General
+
+N4 error handling and cause codes are defined in 3GPP TS 29.244 [2].
+
+The receipt of an N4 error may trigger error handling in SMF. This clause defines the mapping performed by the SMF between when an error received on N4 interface cannot be resolved by SMF and results in the SMF sending a 5GSM message to the UE.
+
+### 5.4.2 Mapping from N4 to 5GSM cause values
+
+**Table 5.4.2-1: Mapping from N4 to 5GSM cause values – Request rejected by SMF due to N4 failures**
+
+| N4 Cause Code          |                                            | 5GSM cause to UE         |                                                                                                                                                      |
+|------------------------|--------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Cause value<br>Decimal | Error description                          | Cause value              | Error description                                                                                                                                    |
+| 64                     | Request rejected<br>(reason not specified) | #31                      | Request rejected,<br>unspecified                                                                                                                     |
+| 74                     | PFCP entity in<br>congestion               | #26<br>#38<br>#69<br>#67 | Insufficient resources<br>Network Failure<br>Insufficient resources<br>for specific slice<br>Insufficient resources<br>for specific slice and<br>DNN |
+| 77                     | System failure                             | #31                      | Request rejected,<br>unspecified                                                                                                                     |
+
+# Annex A (informative): Change history
+
+| Change history |           |           |      |     |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |             |
+|----------------|-----------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting   | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | New version |
+| 2018-10        | CT4#86Bis |           |      |     |     | First version of this new TS including:<br>C4-187375 (Skeleton)<br>C4-187378 (N11 – 5GMM)<br>C4-187391 (N8 – 5GMM – Request rejected)<br>C4-187589 (Scope)<br>C4-187390 (N4 – 5GMM)                                                                                                                                                                                                                                                                                                             | 0.1.0       |
+| 2018-12        | CT4#87    |           |      |     |     | The following agreed documents are included:<br>C4-188418 (NSSF)<br>C4-188484 (Nsmf_PDUSession N11 and N16)<br>C4-188486 (Cause 5GMM)<br>C4-188609 (N4)<br>C4-188637 (N8 and 5GMM)<br>C4-188638 (EIR)<br>C4-188640 (N10 and 5GSM)<br>C4-188641 (N7)<br>C4-188642 (Nausf)<br>C4-188643 (N11 5GMM)<br>C4-188647 (Clean-up) (Conclusion from C4-188384 was wrongly reported to be included in 5GSM General Clause while it applied to 5GMM – corrected by Rapporteur).<br>C4-188648 (General 5GSM) | 0.2.0       |
+| 2018-12        | CT#82     | CP-183104 |      |     |     | Sent for information and approval                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 1.0.0       |
+| 2018-12        | CT#82     | CP-183104 |      |     |     | Approved in CT#82                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 15.0.0      |
+| 2019-03        | CT#83     | CP-190031 | 0001 | 2   | F   | Corrections on cause mapping in clause 4                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 003  | 1   | F   | Mapping between N11 causes and 5GMM causes                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 0008 | 1   | F   | Remove EN's in 5.2.2.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 15.1.0      |
+| 2019-03        | CT#83     | CP-190031 | 0004 | 2   | F   | Corrections to 5GMM and 5GSM causes mappings                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 15.1.0      |
+| 2019-06        | CT#84     | CP-191037 | 0012 | -   | F   | Cause mapping updates                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0013 | 1   | F   | Correction on cause mapping regarding no subscription                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0014 | 2   | F   | Essential Correction on Error mapping for NSSF Services                                                                                                                                                                                                                                                                                                                                                                                                                                         | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0015 | 1   | F   | Essential Correction on mapping for N4 to SBI                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0016 | 1   | F   | Cause mapping corrections                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 15.2.0      |
+| 2019-06        | CT#84     | CP-191037 | 0017 | 1   | F   | Add a mapping for N10                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 15.2.0      |
+| 2019-12        | CT#86     | CP-193036 | 0019 | 2   | F   | Add new mapping towards Cause #62 (No Network Slices available)                                                                                                                                                                                                                                                                                                                                                                                                                                 | 16.0.0      |
+| 2020-06        | CT#88e    | CP-201034 | 0020 | 1   | F   | Correction of the mapping between PCF service causes and 5GSM causes                                                                                                                                                                                                                                                                                                                                                                                                                            | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29541/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29541/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76c3b4a2898b19581d250c9c72e8856a3dc00d27
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1fdf15e12d03ae7af5278b526469e9b41919e8d0c916e360f5e9347532a9cff1
+size 9861
diff --git a/marked/Rel-16/29_series/29541/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29541/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d10e2b7de598ed61deb6e3f940d3e1ab57ee6315
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49b6365ab2eff61ec185430cf7e00ac636e1f74febaf81c44331e0e6fe9cbac6
+size 5846
diff --git a/marked/Rel-16/29_series/29541/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg b/marked/Rel-16/29_series/29541/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b20fcabb4bf34b75842a705df4de88201390c9c8
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/9283a3f6b39120df9dc9aee4712b3a0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0903aee7812cde397d8aeac597beb8c879d2ed89624a2d7135c10d64f3faf145
+size 34055
diff --git a/marked/Rel-16/29_series/29541/990567efebf979be51f56d1150012c9d_img.jpg b/marked/Rel-16/29_series/29541/990567efebf979be51f56d1150012c9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66f99b359372a8d69a9de136209bde854960496c
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/990567efebf979be51f56d1150012c9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e57097a884e33915bd5aeac2f5e9d26ea86e22c1fcdb3a18be2831964a92f358
+size 12157
diff --git a/marked/Rel-16/29_series/29541/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/29_series/29541/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6955a0d6104c020f16b67bb2c11a7af0bc1d9675
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0332322b47cd96e9782ec7f26fd189418dfc2eaa0e31d48c2f8124dec8235c9f
+size 26818
diff --git a/marked/Rel-16/29_series/29541/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-16/29_series/29541/af6be343f0c0a8f155f965dcf337b8af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf6ffee30db4b361ea3f96b028d5955f3ca69def
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/af6be343f0c0a8f155f965dcf337b8af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0025f5345b22305f3a38a33bb6a4f9441359b76d140cf1b0d9d12ee7c0f42891
+size 35039
diff --git a/marked/Rel-16/29_series/29541/b3c108e7145f2017957569d06ea359cb_img.jpg b/marked/Rel-16/29_series/29541/b3c108e7145f2017957569d06ea359cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5de2758b2b0ce30cf1f4341efeb6c4f6cc947b1f
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/b3c108e7145f2017957569d06ea359cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:861397fc1288babf34e1ed13e539f3a424a7b7312b08db04724c574f0e5f939b
+size 31780
diff --git a/marked/Rel-16/29_series/29541/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Rel-16/29_series/29541/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aaeccd43d89cc48736ae74e3364b04261363b8a8
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:171a0e72089e8e3a8275890707417de336d4e0e57e821b2f4ae5c68a8fe62013
+size 40468
diff --git a/marked/Rel-16/29_series/29541/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/Rel-16/29_series/29541/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2874ae1be30ad9a0d8bd6550fd6b264b9b006348
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c18e523dff73e4147aa470f36256f238514f7974eb116670dd0332347252d5a
+size 34591
diff --git a/marked/Rel-16/29_series/29541/raw.md b/marked/Rel-16/29_series/29541/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a149bbf29980bcaee5cc1d899f108e5871456e03
--- /dev/null
+++ b/marked/Rel-16/29_series/29541/raw.md
@@ -0,0 +1,1783 @@
+
+
+# 3GPP TS 29.541 V16.5.0 (2021-09)
+
+*Technical Specification*
+
+**3rd Generation Partnership Project;  
+Technical Specification Group Core Network and Terminals;  
+5G System; Network Exposure (NE) function services for Non-  
+IP Data Delivery (NIDD);  
+Stage 3  
+(Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+
+Valbonne - FRANCE
+
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                                                                                                       |    |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword .......................................................................................................................................................................... 5 | 5  |
+| 1 Scope.................................................................................................................................................................. 6           | 6  |
+| 2 References.......................................................................................................................................................... 6              | 6  |
+| 3 Definitions, symbols and abbreviations ............................................................................................................. 7                              | 7  |
+| 3.1 Terms.................................................................................................................................................................. 7         | 7  |
+| 3.2 Symbols.............................................................................................................................................................. 7           | 7  |
+| 3.3 Abbreviations ..................................................................................................................................................... 7             | 7  |
+| 4 Overview............................................................................................................................................................ 7              | 7  |
+| 4.1 Introduction ........................................................................................................................................................ 7           | 7  |
+| 5 Services offered by the NEF for NIDD ............................................................................................................. 8                                | 8  |
+| 5.1 Introduction ........................................................................................................................................................ 8           | 8  |
+| 5.2 Nnef_SMContext Service .................................................................................................................................. 9                       | 9  |
+| 5.2.1 Service Description ............................................................................................................................................ 9              | 9  |
+| 5.2.2 Service Operations.............................................................................................................................................. 9              | 9  |
+| 5.2.2.1 Introduction......................................................................................................................................................... 9       | 9  |
+| 5.2.2.2 Create Service Operation.................................................................................................................................... 9                | 9  |
+| 5.2.2.2.1 General ................................................................................................................................................................ 9  | 9  |
+| 5.2.2.3 Delete Service Operation.................................................................................................................................. 10                 | 10 |
+| 5.2.2.3.1 General .............................................................................................................................................................. 10   | 10 |
+| 5.2.2.4 Status Notify Service Operation ....................................................................................................................... 11                    | 11 |
+| 5.2.2.4.1 General .............................................................................................................................................................. 11   | 11 |
+| 5.2.2.4.2 Notify of Individual SM Context Release (Nnef_SMContext_DeleteNotify)................................................. 12                                                   | 12 |
+| 5.2.2.5 Update Service Operation.................................................................................................................................. 12                 | 12 |
+| 5.2.2.5.1 General .............................................................................................................................................................. 12   | 12 |
+| 5.2.2.6 Deliver Service Operation ................................................................................................................................ 12                 | 12 |
+| 5.2.2.6.1 General .............................................................................................................................................................. 12   | 12 |
+| 6 API Definitions ................................................................................................................................................ 14                 | 14 |
+| 6.1 Nnef_SMContext Service API.......................................................................................................................... 14                           | 14 |
+| 6.1.1 Introduction ...................................................................................................................................................... 14          | 14 |
+| 6.1.2 Usage of HTTP................................................................................................................................................. 14               | 14 |
+| 6.1.2.1 General.............................................................................................................................................................. 14      | 14 |
+| 6.1.2.2 HTTP standard headers..................................................................................................................................... 14                 | 14 |
+| 6.1.2.2.1 General .............................................................................................................................................................. 14   | 14 |
+| 6.1.2.2.2 Content type ...................................................................................................................................................... 14      | 14 |
+| 6.1.2.3 HTTP custom headers....................................................................................................................................... 14                 | 14 |
+| 6.1.3 Resources.......................................................................................................................................................... 15          | 15 |
+| 6.1.3.1 Overview........................................................................................................................................................... 15        | 15 |
+| 6.1.3.2 Resource: SM Contexts Collection................................................................................................................... 15                        | 15 |
+| 6.1.3.2.1 Description ........................................................................................................................................................ 15     | 15 |
+| 6.1.3.2.2 Resource Definition........................................................................................................................................... 16           | 16 |
+| 6.1.3.2.3 Resource Standard Methods.............................................................................................................................. 16                  | 16 |
+| 6.1.3.2.3.1 POST ................................................................................................................................................................. 16 | 16 |
+| 6.1.3.2.4 Resource Custom Operations............................................................................................................................ 17                   | 17 |
+| 6.1.3.3 Resource: Individual SM Context..................................................................................................................... 17                       | 17 |
+| 6.1.3.3.1 Description ........................................................................................................................................................ 17     | 17 |
+| 6.1.3.3.2 Resource Definition........................................................................................................................................... 17           | 17 |
+| 6.1.3.3.3 Resource Standard Methods.............................................................................................................................. 17                  | 17 |
+| 6.1.3.3.4 Resource Custom Operations............................................................................................................................ 17                   | 17 |
+| 6.1.3.3.4.1 Overview ........................................................................................................................................................... 17   | 17 |
+| 6.1.3.3.4.2 Operation: release.............................................................................................................................................. 18       | 18 |
+| 6.1.3.3.4.2.1 Description......................................................................................................................................................... 18 | 18 |
+| 6.1.3.3.4.2.2 Operation Definition........................................................................................................................................... 18      | 18 |
+| 6.1.3.3.4.3 Operation: update .............................................................................................................................................. 19       | 19 |
+
+|                                                                                                                                                              |                                                                                                                                                                  |           |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|
+| 6.1.3.3.4.3.1                                                                                                                                                | Description...................................................................................................................................................   | 19        |
+| 6.1.3.3.4.3.2                                                                                                                                                | Operation Definition ...................................................................................................................................         | 19        |
+| 6.1.3.3.4.4                                                                                                                                                  | Operation: deliver........................................................................................................................................       | 20        |
+| 6.1.3.3.4.4.1                                                                                                                                                | Description...................................................................................................................................................   | 20        |
+| 6.1.3.3.4.4.2                                                                                                                                                | Operation Definition ...................................................................................................................................         | 20        |
+| 6.1.5                                                                                                                                                        | Notifications ...............................................................................................................................................    | 21        |
+| 6.1.5.1                                                                                                                                                      | General......................................................................................................................................................... | 21        |
+| 6.1.5.2                                                                                                                                                      | Status Notification ......................................................................................................................................       | 22        |
+| 6.1.5.2.1                                                                                                                                                    | Description ..................................................................................................................................................   | 22        |
+| 6.1.5.2.2                                                                                                                                                    | Target URI...................................................................................................................................................    | 22        |
+| 6.1.5.2.3                                                                                                                                                    | Standard Methods........................................................................................................................................         | 22        |
+| 6.1.5.2.3.1                                                                                                                                                  | POST ........................................................................................................................................................... | 22        |
+| 6.1.6                                                                                                                                                        | Data Model .................................................................................................................................................     | 23        |
+| 6.1.6.1                                                                                                                                                      | General......................................................................................................................................................... | 23        |
+| 6.1.6.2                                                                                                                                                      | Structured data types....................................................................................................................................        | 24        |
+| 6.1.6.2.1                                                                                                                                                    | Introduction .................................................................................................................................................   | 24        |
+| 6.1.6.2.2                                                                                                                                                    | Type: SmContextCreateData.......................................................................................................................                 | 25        |
+| 6.1.6.2.3                                                                                                                                                    | Type: SmContextCreatedData.....................................................................................................................                  | 26        |
+| 6.1.6.2.4                                                                                                                                                    | Type: SmContextReleaseData.....................................................................................................................                  | 26        |
+| 6.1.6.2.5                                                                                                                                                    | Type: SmContextReleasedData...................................................................................................................                   | 27        |
+| 6.1.6.2.6                                                                                                                                                    | Type: SmContextStatusNotification ...........................................................................................................                    | 27        |
+| 6.1.6.2.7                                                                                                                                                    | Type: NiddInformation ...............................................................................................................................            | 27        |
+| 6.1.6.2.8                                                                                                                                                    | Type: SmContextConfiguration ..................................................................................................................                  | 28        |
+| 6.1.6.2.9                                                                                                                                                    | Type: SmallDataRateControl ......................................................................................................................                | 28        |
+| 6.1.6.2.10                                                                                                                                                   | Type: SmContextUpdateData .....................................................................................................................                  | 29        |
+| 6.1.6.2.11                                                                                                                                                   | Type: DeliverReqData.................................................................................................................................            | 29        |
+| 6.1.6.3                                                                                                                                                      | Simple data types and enumerations............................................................................................................                   | 29        |
+| 6.1.6.3.1                                                                                                                                                    | Introduction .................................................................................................................................................   | 29        |
+| 6.1.6.3.2                                                                                                                                                    | Simple data types ........................................................................................................................................       | 29        |
+| 6.1.6.3.3                                                                                                                                                    | Enumeration: SmContextStatus ..................................................................................................................                  | 29        |
+| 6.1.6.3.4                                                                                                                                                    | Enumeration: SmallDataRateControlTimeUnit ..........................................................................................                             | 30        |
+| 6.1.6.3.5                                                                                                                                                    | Enumeration: ReleaseCause........................................................................................................................                | 30        |
+| 6.1.7                                                                                                                                                        | Error Handling ............................................................................................................................................      | 30        |
+| 6.1.7.1                                                                                                                                                      | General......................................................................................................................................................... | 30        |
+| 6.1.7.2                                                                                                                                                      | Protocol Errors ............................................................................................................................................     | 30        |
+| 6.1.7.3                                                                                                                                                      | Application Errors.......................................................................................................................................        | 30        |
+| 6.1.8                                                                                                                                                        | Feature negotiation .....................................................................................................................................        | 31        |
+| 6.1.9                                                                                                                                                        | Security ....................................................................................................................................................... | 31        |
+| 6.1.10                                                                                                                                                       | HTTP redirection.........................................................................................................................................        | 31        |
+| <b>Annex A (normative): OpenAPI specification ....................................................................................................</b>       |                                                                                                                                                                  | <b>32</b> |
+| A.1                                                                                                                                                          | General ........................................................................................................................................................ | 32        |
+| A.2                                                                                                                                                          | Nnef_SMContext API ................................................................................................................................              | 32        |
+| <b>Annex B (informative): Change history ...............................................................................................................</b> |                                                                                                                                                                  | <b>39</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the stage 3 protocol and data model for the Nnef Service Based South-Bound Interfaces for NIDD. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the NEF.
+
+The 5G System stage 2 architecture and procedures are specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
+
+The Technical Realization of the Service Based Architecture and the Principles and Guidelines for Services Definition are specified in 3GPP TS 29.500 [4] and 3GPP TS 29.501 [5].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
+- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
+- [4] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [5] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [6] OpenAPI: "OpenAPI 3.0.0 Specification", <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md>.
+- [7] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [8] 3GPP TS 33.501: "Security architecture and procedures for 5G system".
+- [9] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [10] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3".
+- [11] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+- [12] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [13] IETF RFC 7807: "Problem Details for HTTP APIs".
+
+- [14] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+- [15] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
+- [16] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
+- [17] 3GPP TS 29.542: "5G System; Session management services for Non-IP Data Delivery (NIDD); Stage 3".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Terms
+
+Void.
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|       |                                                |
+|-------|------------------------------------------------|
+| DNN   | Data Network Name                              |
+| MO    | Mobile Originated                              |
+| NEF   | Network Exposure Function                      |
+| NIDD  | Non-IP Data Delivery                           |
+| SM    | Session Management                             |
+| SMF   | Session Management Function                    |
+| NSSAI | Network Slice Selection Assistance Information |
+| RDS   | Reliable Data Service                          |
+| SUPI  | Subscription Permanent Identifier              |
+
+# --- 4 Overview
+
+## 4.1 Introduction
+
+Within the 5GC, the NEF offers NIDD services to the NF (e.g. SMF) via the Nnef service based southbound interface (see 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3]).
+
+Figure 4.1-1 provides the reference model (in service based interface representation and in reference point representation), with focus on the NEF and the scope of the present specification.
+
+![Figure 4.1-1: Reference model – NEF. The diagram shows two entities, SMF and AF, connected to an NEF. SMF is connected via an N29 interface, and AF is connected via an N33 interface. Both interfaces lead to a single point on the NEF labeled 'Nnef'.](990567efebf979be51f56d1150012c9d_img.jpg)
+
+```
+
+graph LR
+    SMF[SMF] -- N29 --> Nnef((Nnef))
+    AF[AF] -- N33 --> Nnef
+    Nnef --- NEF[NEF]
+  
+```
+
+Figure 4.1-1: Reference model – NEF. The diagram shows two entities, SMF and AF, connected to an NEF. SMF is connected via an N29 interface, and AF is connected via an N33 interface. Both interfaces lead to a single point on the NEF labeled 'Nnef'.
+
+Figure 4.1-1: Reference model – NEF
+
+The functionalities supported by the NEF are listed in clause 6.2.5 of 3GPP TS 23.501 [2].
+
+# 5 Services offered by the NEF for NIDD
+
+## 5.1 Introduction
+
+The table 5.1-1 shows the NEF Services and Service Operations for NIDD:
+
+Table 5.1-1 List of NEF Services for NIDD
+
+| Service Name   | Service Operations | Operation Semantics | Example Consumer(s) | Mapped Service Operation           |
+|----------------|--------------------|---------------------|---------------------|------------------------------------|
+| Nnef_SMContext | Create             | Request/Response    | SMF                 | Nnef_SMContext_Create              |
+|                | Delete             | Request/Response    | SMF                 | Nnef_SMContext_Delete              |
+|                | Status Notify      | Subscribe/Notify    | SMF                 | Nnef_SMContext_DeleteNotify (NOTE) |
+|                | Update             | Request/Response    | SMF                 |                                    |
+|                | Delivery           | Request/Response    | SMF                 | Nnef_SMContext_Delivery            |
+
+NOTE: The Status Notify service operation models the Nnef\_SMContext\_DeleteNotify service operation specified in 3GPP TS 23.502 [3] (see clause 5.2.2.4.2).
+
+Table 5.1-2 summarizes the corresponding APIs defined for this specification.
+
+Table 5.1-2: API Descriptions
+
+| Service Name   | Clause | Description            | OpenAPI Specification File  | apiName        | Annex |
+|----------------|--------|------------------------|-----------------------------|----------------|-------|
+| Nnef_SMContext | 6.1    | Nnef_SMContext Service | TS29541_Nnef_SMContext.yaml | nnef-smcontext | A.2   |
+
+## 5.2 Nnef\_SMContext Service
+
+### 5.2.1 Service Description
+
+The service allows a NF to manage the SM Contexts on NEF for NIDD. A NF as service consumer (e.g. SMF) can create, update or release SM Contexts for NIDD on NEF. A created SM Context for NIDD may also be released by NEF.
+
+### 5.2.2 Service Operations
+
+#### 5.2.2.1 Introduction
+
+The Nnef\_SMContext service supports following service operations:
+
+- Create
+- Delete
+- StatusNotify
+- Update
+- Deliver
+
+#### 5.2.2.2 Create Service Operation
+
+##### 5.2.2.2.1 General
+
+The Create service operation is used during the following procedure:
+
+- SMF-NEF Connection Establishment procedure (see 3GPP TS 23.502 [3], clause 4.25.2)
+
+The Create service operation is invoked by a NF Service Consumer (e.g. a SMF) towards the NEF, when the SMF received a PDU Session establishment request from the UE with PDU Session type of "Unstructured", and the subscription information corresponding to the UE requested DNN includes the "NEF Identity for NIDD". There shall be only one individual SM context per PDU session.
+
+The NF Service Consumer (e.g. the SMF) shall create the SM Context for NIDD on NEF by sending the HTTP POST request towards the SM Contexts Collection resource as shown in Figure 5.2.2.2.1-1.
+
+![Sequence diagram showing the Create Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 201 Created status or a 4xx/5xx error status.](9283a3f6b39120df9dc9aee4712b3a0a_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant NEF
+    Note left of NF Service Consumer: SMF-NEF Connection Establishment procedure
+    NF Service Consumer->>NEF: 1. POST .../sm-contexts (SmContextCreateData)
+    NEF-->>NF Service Consumer: -2a. 201 Created (SmContextCreatedData)
+    NEF-->>NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx
+  
+```
+
+Sequence diagram showing the Create Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 201 Created status or a 4xx/5xx error status.
+
+**Figure 5.2.2.2.1-1: Create Service Operation**
+
+1. The NF Service Consumer shall send a POST request to the resource representing the SM Contexts Collection resource of the NEF with a "SmContextCreateData" object in request body, including:
+  - SUPI of the UE;
+  - PDU session ID;
+  - S-NSSAI associated with the PDU session;
+
+- DNN of the PDU session;
+- NIDD information, such as GPSI, AF ID, etc.;
+- NEF ID, indicating the provisioned identity for NIDD service;
+- URI of the Individual PDU session resource for downlink data delivery (see clause 6.1.3.2 of 3GPP TS 29.542 [17]);
+- Notification URI to receive the SM Context notifications;
+- optionally the indication of UE capability to support Reliable Data Service (RDS);
+- optionally the configuration parameters, e.g. serving PLMN rate control, small data rate control, etc.;
+- optionally small data rate control status, if small data rate control is previously enabled and to be resumed
+
+2a. On success, "201 Created" shall be returned and the "Location" header shall be present and shall contain the URI of the created Individual SM Context resource.
+
+The payload body of the POST response shall contain a "SmContextCreatedData" object, including:
+
+- SUPI of the UE;
+- PDU session ID;
+- S-NSSAI associated with the PDU session;
+- DNN of the PDU session;
+- NEF ID, indicating the provisioned identity for NIDD service;
+- optionally the indication of NEF capability to support Reliable Data Service (RDS);
+- optionally the indication of NEF capability to support Extended Buffering;
+- optionally Maximum Packet Size in bytes for NIDD data packet.
+
+2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.2.3.1-3 shall be returned, the response body should contain a "ProblemDetails" object with "cause" attribute set to one of the application errors listed in Table 6.1.3.2.3.1-3.
+
+#### 5.2.2.3 Delete Service Operation
+
+##### 5.2.2.3.1 General
+
+The Delete service operation is used during the following procedure:
+
+- SMF Initiated SMF-NEF Connection Release procedure (see 3GPP TS 23.502 [3], clause 4.25.7)
+
+The Delete service operation is invoked by a NF Service Consumer (e.g. a SMF) towards the NEF, when the PDU Session Release is initiated and a SM context for NIDD has been previously created on NEF for the PDU session.
+
+The NF Service Consumer (e.g. the SMF) shall delete the SM Context for NIDD on NEF by invoking the "release" custom operation on the Individual SM Context resource as shown in Figure 5.2.2.3.1-1.
+
+![Sequence diagram for Delete Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content / 200 OK (SmContextReleasedData) or an error status code (4xx/5xx or 3xx).](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant NEF
+    Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/release (SmContextReleaseData)
+    NF Service Consumer->>NEF: Request
+    Note right of NEF: -2a. 204 No Content / 200 OK (SmContextReleasedData)
+    NEF-->>NF Service Consumer: Success Response
+    Note right of NEF: -2b. 4xx/5xx (ProblemDetails) or 3xx
+    NEF-->>NF Service Consumer: Error Response
+  
+```
+
+Sequence diagram for Delete Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content / 200 OK (SmContextReleasedData) or an error status code (4xx/5xx or 3xx).
+
+Figure 5.2.2.3.1-1: Delete Service Operation
+
+- The NF Service Consumer shall send a HTTP POST request towards the URI of "release" custom operation on the Individual SM Context resource received from the "Location" header during a successful Create service operation invocation (See clause 5.2.2.2). The request body shall contain a "SmContextReleaseData" object.
+- On success, "204 No Content" shall be returned if no information is to be returned to the NF service consumer; otherwise "200 OK" shall be returned with a "SmContextReleasedData" object in response body including necessary information to the NF service consumer, e.g.:
+  - Small Data Rate Control status, if Small Data Rate Control is enforced;
+  - APN Rate Status, if APN Rate Control is enforced
+- On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.2-2 shall be returned, the response body should contain a "ProblemDetails" object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.2-2.
+
+#### 5.2.2.4 Status Notify Service Operation
+
+##### 5.2.2.4.1 General
+
+The Status Notify service operation is used during the following procedure:
+
+- NEF Initiated SMF-NEF Connection Release procedure (see 3GPP TS 23.502 [3], clause 4.25.8)
+
+The Status Notify service operation is invoked by the NEF to inform a NF Service Consumer (e.g. a SMF), when the status of the Individual SM Context has changed.
+
+The NEF shall inform the status change of the Individual SM Context resource by sending the HTTP POST method towards the Notification URI as shown in Figure 5.2.2.4.1-1.
+
+![Sequence diagram for Status Notify Service Operation. The NEF sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No content or an error status code (4xx/5xx or 3xx).](b3c108e7145f2017957569d06ea359cb_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NEF
+    participant NF Service Consumer
+    Note right of NEF: 1. POST {notificationUri} (SmContextStatusNotification)
+    NEF->>NF Service Consumer: Request
+    Note left of NF Service Consumer: -2a. 204 No content
+    NF Service Consumer-->>NEF: Success Response
+    Note left of NF Service Consumer: -2b. 4xx/5xx (ProblemDetails) or 3xx
+    NF Service Consumer-->>NEF: Error Response
+  
+```
+
+Sequence diagram for Status Notify Service Operation. The NEF sends a POST request to the NF Service Consumer. The NF Service Consumer responds with either a 204 No content or an error status code (4xx/5xx or 3xx).
+
+Figure 5.2.2.4.1-1: Status Notify Service Operation
+
+- The NEF shall send a POST request towards the Notification URI received in the Create service operation request (See clause 5.2.2.2). The request body shall contain a "SmContextStatusNotification" object indicating the changed status of the Individual SM Context resource. The "smContextId" attribute shall contain the URI of the SM Context resource that triggers the notification.
+- On success, "204 No content" shall be returned without response body.
+- On failure or redirection, one of the HTTP status code listed in Table 6.1.5.2.3.1-2 shall be returned, the response body should contain a "ProblemDetails" object.
+
+##### 5.2.2.4.2 Notify of Individual SM Context Release (Nnef\_SMContext\_DeleteNotify)
+
+During NEF initiated SMF-NEF connection release procedure (see 3GPP TS 23.502 [3], clause 4.25.8), the NEF shall send Status Notification to inform the NF service consumer that the Individual SM Context is released.
+
+The requirements in clause 5.2.2.4.1 shall be applied, with following additions:
+
+1. Same as step 1 of Figure 5.2.2.4.1-1, the NEF shall set the value of "status" attribute in the request body to "RELEASED".
+  - If Small Data Rate Control is enforced, the response body should include the Small Data Rate Control status.
+  - If APN Rate Control is enforced, the response body should include the APN Rate Status.
+
+#### 5.2.2.5 Update Service Operation
+
+##### 5.2.2.5.1 General
+
+The Update service operation is invoked by a NF Service Consumer, e.g. a SMF, towards the NEF, when the SMF detects that some of the configurations of the PDU session has changed and the related SM Context for NIDD needs to be updated accordingly.
+
+The NF Service Consumer (e.g. the SMF) shall update the SM Context for NIDD on NEF by invoking the "update" custom operation of the Individual SM Context resource as shown in Figure 5.2.2.5.1-1.
+
+![Sequence diagram for Update Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content or an error status code (4xx/5xx or 3xx).](af6be343f0c0a8f155f965dcf337b8af_img.jpg)
+
+```
+
+sequenceDiagram
+    participant NF Service Consumer
+    participant NEF
+    Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/update (SmContextUpdateData)
+    NF Service Consumer->>NEF: Request
+    Note right of NEF: 2a. 204 No Content
+    NEF-->>NF Service Consumer: Response
+    Note right of NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx
+    NEF-->>NF Service Consumer: Response
+  
+```
+
+Sequence diagram for Update Service Operation. The NF Service Consumer sends a POST request to the NEF. The NEF responds with either a 204 No Content or an error status code (4xx/5xx or 3xx).
+
+Figure 5.2.2.5.1-1: Update Service Operation
+
+1. The NF Service Consumer shall send a POST request to the URI of "update" custom operation on an Individual SM Context resource, with a "SmContextUpdateData" object in request body containing the attributes to be updated, e.g.:
+  - URI of the resource to receive downlink data delivery for NIDD;
+  - Notification URI to receive the SM Context notifications;
+  - modified configuration parameters, e.g. serving PLMN rate control, small data rate control, etc.
+- 2a. On success, "204 No Content" shall be returned.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.3.2-2 shall be returned, the response body should contain a ProblemDetails object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.3.2-2.
+
+#### 5.2.2.6 Deliver Service Operation
+
+##### 5.2.2.6.1 General
+
+The Deliver service operation is invoked by a NF Service Consumer, e.g. a SMF, to transport Mobile Originated data packet via NEF.
+
+The NF Service Consumer (e.g. the SMF) shall deliver Mobile Originate data via NEF by invoking the "deliver" custom operation of the Individual SM Context resource as shown in Figure 5.2.2.6.1-1.
+
+![Sequence diagram of Deliver Service Operation between NF Service Consumer and NEF.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg)
+
+```
+sequenceDiagram
+    participant NF Service Consumer
+    participant NEF
+    Note left of NF Service Consumer: 1. POST ../sm-contexts/{smContextId}/deliver (DeliverReqData)
+    NF Service Consumer->>NEF: Request
+    Note right of NEF: 2a. 204 No Content
+    NEF-->>NF Service Consumer: Success Response
+    Note right of NEF: 2b. 4xx/5xx (ProblemDetails) or 3xx
+    NEF-->>NF Service Consumer: Error/Redirect Response
+```
+
+The diagram illustrates the interaction between an NF Service Consumer and an NEF. The NF Service Consumer sends a POST request (step 1) to the URI `../sm-contexts/{smContextId}/deliver` with a `DeliverReqData` body. The NEF responds with either a 204 No Content (step 2a) on success or a 4xx/5xx (ProblemDetails) or 3xx (step 2b) on failure or redirection.
+
+Sequence diagram of Deliver Service Operation between NF Service Consumer and NEF.
+
+**Figure 5.2.2.5.6-1: Deliver Service Operation**
+
+1. The NF Service Consumer shall send a POST request to the URI of "deliver" custom operation on an Individual SM Context resource, with the request body containing:
+  - the MO data as binary body part with content type set as "application/octet-stream"; and
+  - a "DeliverReqData" object as another body part with "data" attribute refer to the MO data binary part.
+- 2a. On success, "204 No Content" shall be returned.
+- 2b. On failure or redirection, one of the HTTP status code listed in Table 6.1.3.3.4.4.2-2 shall be returned. The response body should contain a ProblemDetails object with "cause" attribute set to one of the application errors listed in Table 6.1.3.3.4.4.2-2.
+
+# --- 6 API Definitions
+
+## 6.1 Nnef\_SMContext Service API
+
+### 6.1.1 Introduction
+
+The Nnef\_SMContext service shall use the Nnef\_SMContext service API.
+
+The request URI used in HTTP request from the NF service consumer towards the NF service producer shall have the structure defined in clause 4.4.1 of 3GPP TS 29.501 [5], i.e.:
+
+**{apiRoot}/<apiName>/<apiVersion>/<apiSpecificResourceUriPart>**
+
+with the following components:
+
+- The {apiRoot} shall be set as described in 3GPP TS 29.501 [5].
+- The <apiName> shall be "nnef-smcontext".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificResourceUriPart> shall be set as described in clause 6.1.3.
+
+### 6.1.2 Usage of HTTP
+
+#### 6.1.2.1 General
+
+HTTP/2, IETF RFC 7540 [11], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].
+
+HTTP/2 shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].
+
+The OpenAPI [6] specification of HTTP messages and content bodies for the Nnef\_SMContext API is contained in Annex A.
+
+#### 6.1.2.2 HTTP standard headers
+
+##### 6.1.2.2.1 General
+
+See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.
+
+##### 6.1.2.2.2 Content type
+
+JSON, IETF RFC 8259 [12], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".
+
+"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [13].
+
+#### 6.1.2.3 HTTP custom headers
+
+The mandatory HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] shall be applicable. In this release of the specification, no specific custom headers are defined for the Nnef\_SMContext service.
+
+### 6.1.3 Resources
+
+#### 6.1.3.1 Overview
+
+Figure 6.1.3.1-1 describes the resource URI structure of the Nnef\_SMContext API.
+
+![Diagram showing the resource URI structure of the Nnef_SMContext API. The root is {apiRoot}/nnef-smcontext/<apiVersion>. It branches to /sm-contexts, which then branches to /{smContextId}. From /{smContextId}, three sub-resources are shown: /update, /release, and /deliver, each in a dashed box.](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/nnef-smcontext/<apiVersion>"] --> SmContexts["/sm-contexts"]
+    SmContexts --> SmContextId["/{smContextId}"]
+    SmContextId --> Update["/update"]
+    SmContextId --> Release["/release"]
+    SmContextId --> Deliver["/deliver"]
+    style Update stroke-dasharray: 5 5
+    style Release stroke-dasharray: 5 5
+    style Deliver stroke-dasharray: 5 5
+  
+```
+
+Diagram showing the resource URI structure of the Nnef\_SMContext API. The root is {apiRoot}/nnef-smcontext/. It branches to /sm-contexts, which then branches to /{smContextId}. From /{smContextId}, three sub-resources are shown: /update, /release, and /deliver, each in a dashed box.
+
+**Figure 6.1.3.1-1: Resource URI structure of the Nnef\_SMContext API**
+
+Table 6.1.3.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 6.1.3.1-1: Resources and methods overview**
+
+| Resource name          | Resource URI                                                            | HTTP method or custom operation | Description                                |
+|------------------------|-------------------------------------------------------------------------|---------------------------------|--------------------------------------------|
+| SM Contexts Collection | {apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts                       | POST                            | Creates an Individual SM Context resource. |
+| Individual SM Context  | {apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts/{smContextId}/release | release (POST)                  | Deletes an Individual SM Context resource. |
+|                        | {apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts/{smContextId}/update  | update (POST)                   | Updates an Individual SM Context resource. |
+|                        | {apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts/{smContextId}/deliver | deliver (POST)                  | Delivers Mobile Originated data packet.    |
+
+#### 6.1.3.2 Resource: SM Contexts Collection
+
+##### 6.1.3.2.1 Description
+
+This resource represents the collection of the Individual SM Context resources created in the NEF.
+
+This resource is modelled with the Collection resource archetype (see clause C.2 of 3GPP TS 29.501 [5]).
+
+##### 6.1.3.2.2 Resource Definition
+
+Resource URI: **{apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts**
+
+This resource shall support the resource URI variables defined in table 6.1.3.2.2-1.
+
+**Table 6.1.3.2.2-1: Resource URI variables for this resource**
+
+| Name       | Definition       |
+|------------|------------------|
+| apiRoot    | See clause 6.1.1 |
+| apiVersion | See clause 6.1.1 |
+
+##### 6.1.3.2.3 Resource Standard Methods
+
+###### 6.1.3.2.3.1 POST
+
+This method creates an Individual SM Context resource in the SM Context Collection.
+
+This method shall support the URI query parameters specified in table 6.1.3.2.3.1-1.
+
+**Table 6.1.3.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description | Applicability |
+|------|-----------|---|-------------|-------------|---------------|
+| n/a  |           |   |             |             |               |
+
+This method shall support the request data structures specified in table 6.1.3.2.3.1-2 and the response data structures and response codes specified in table 6.1.3.2.3.1-3.
+
+**Table 6.1.3.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type           | P | Cardinality | Description                                                |
+|---------------------|---|-------------|------------------------------------------------------------|
+| SmContextCreateData | M | 1           | Representation of the Individual SM context to be created. |
+
+**Table 6.1.3.2.3.1-3: Data structures supported by the <method 1> Response Body on this resource**
+
+| Data type            | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                    |
+|----------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SmContextCreatedData | M | 1           | 201 Created            | Successful creation of an Individual SM context.                                                                                                                                                                                                                                                                                                               |
+| RedirectResponse     | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| RedirectResponse     | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| ProblemDetails       | O | 1           | 403 Forbidden          | The "cause" attribute may be used to indicate the following application errors:<br>- USER_UNKNOWN<br>- NIDD_CONFIGURATION_NOT_AVAILABLE<br><br>See table 6.1.7.3-1 for the description of these errors.                                                                                                                                                        |
+
+NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]).
+
+**Table 6.1.3.2.3.1-4: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+**Table 6.1.3.2.3.1-5: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+##### 6.1.3.2.4 Resource Custom Operations
+
+None.
+
+#### 6.1.3.3 Resource: Individual SM Context
+
+##### 6.1.3.3.1 Description
+
+This resource represents an Individual SM Context resource in the NEF.
+
+This resource is modelled with the Document resource archetype (see clause C.2 of 3GPP TS 29.501 [5]).
+
+##### 6.1.3.3.2 Resource Definition
+
+Resource URI: {apiRoot}/nnef-smcontext/<apiVersion>/sm-contexts/{smContextId}
+
+This resource shall support the resource URI variables defined in table 6.1.3.3.2-1.
+
+**Table 6.1.3.3.2-1: Resource URI variables for this resource**
+
+| Name        | Definition                                                                     |
+|-------------|--------------------------------------------------------------------------------|
+| apiRoot     | See clause 6.1.1                                                               |
+| apiVersion  | See clause 6.1.1                                                               |
+| smContextId | SM context identifier assigned by the NEF during the Create service operation. |
+
+##### 6.1.3.3.3 Resource Standard Methods
+
+There is no standard HTTP method supported by this resource.
+
+##### 6.1.3.3.4 Resource Custom Operations
+
+##### 6.1.3.3.4.1 Overview
+
+This resource supports custom operation(s) as specified in table 6.1.3.3.4.1-1.
+
+**Table 6.1.3.3.4.1-1: Custom operations**
+
+| Custom operaration URI | Mapped HTTP method | Description               |
+|------------------------|--------------------|---------------------------|
+| {resourceUri}/release  | POST               | Delete service operation. |
+| {resourceUri}/update   | POST               | Update service operation. |
+| {resourceUri}/deliver  | POST               | Deliver service operation |
+
+###### 6.1.3.3.4.2 Operation: release
+
+###### 6.1.3.3.4.2.1 Description
+
+This custom operation releases an Individual SM Context resource previously created in the NEF.
+
+###### 6.1.3.3.4.2.2 Operation Definition
+
+This operation shall support the request data structures specified in table 6.1.3.2.4.2.2-1 and the response data structure and response codes specified in table 6.1.3.2.4.2.2-2.
+
+**Table 6.1.3.3.4.2.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type            | P | Cardinality | Description                                                             |
+|----------------------|---|-------------|-------------------------------------------------------------------------|
+| SmContextReleaseData | M | 1           | Representation of the information to release the Individual SM context. |
+
+**Table 6.1.3.3.4.2.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                                                                                                                                                                               | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                    |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SmContextReleasedData                                                                                                                                                                                                                                                                   | M | 1           | 200 OK                 | Successful release of an Individual SM context with information sent to the NF service consumer.                                                                                                                                                                                                                                                               |
+| n/a                                                                                                                                                                                                                                                                                     |   |             | 204 No Content         | Successful release of an Individual SM context without information sent to the NF service consumer.                                                                                                                                                                                                                                                            |
+| RedirectResponse                                                                                                                                                                                                                                                                        | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| RedirectResponse                                                                                                                                                                                                                                                                        | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| ProblemDetails                                                                                                                                                                                                                                                                          | O | 1           | 404 Not Found          | The "cause" attribute may be used to indicate the following application errors:<br>- CONTEXT_NOT_FOUND<br><br>See table 6.1.7.3-1 for the description of these errors.                                                                                                                                                                                         |
+| NOTE: The manadatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |   |             |                        |                                                                                                                                                                                                                                                                                                                                                                |
+
+**Table 6.1.3.3.4.2.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+**Table 6.1.3.3.4.2.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+###### 6.1.3.3.4.3 Operation: update
+
+###### 6.1.3.3.4.3.1 Description
+
+This custom operation updates an individual SM Context resource.
+
+###### 6.1.3.3.4.3.2 Operation Definition
+
+This operation shall support the request data structures specified in table 6.1.3.3.4.3.2-1 and the response data structure and response codes specified in table 6.1.3.3.4.3.2-2.
+
+**Table 6.1.3.3.4.3.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type            | P | Cardinality | Description                                                          |
+|----------------------|---|-------------|----------------------------------------------------------------------|
+| SmContextUpdate Data | M | 1           | Representation of the updates to apply to the Individual SM context. |
+
+**Table 6.1.3.3.4.3.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                    |
+|------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | Successful update of the Individual SM context, when the NEF does not need to return information in the response.                                                                                                                                                                                                                                              |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| ProblemDetails   | O | 1           | 404 Not Found          | The "cause" attribute may be used to indicate the following application errors:<br>- CONTEXT_NOT_FOUND<br><br>See table 6.1.7.3-1 for the description of these errors.                                                                                                                                                                                         |
+
+NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]).
+
+**Table 6.1.3.3.4.3.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+**Table 6.1.3.3.4.3.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+###### 6.1.3.3.4.4 Operation: deliver
+
+###### 6.1.3.3.4.4.1 Description
+
+This custom operation transports Mobile Originated data packet via NEF.
+
+###### 6.1.3.3.4.4.2 Operation Definition
+
+This operation shall support the request data structures specified in table 6.1.3.3.4.4.2-1 and the response data structure and response codes specified in table 6.1.3.3.4.4.2-2.
+
+**Table 6.1.3.3.4.4.2-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type      | P | Cardinality | Description                                                                                         |
+|----------------|---|-------------|-----------------------------------------------------------------------------------------------------|
+| DeliverReqData | M | 1           | The data for Deliver service request, including the Mobile Originated data to be delivered via NEF. |
+
+**Table 6.1.3.3.4.4.2-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                                                                                                                                                                              | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                    |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a                                                                                                                                                                                                                                                                                    |   |             | 204 No Content         | Successful delivery of Mobile Originate data via NEF.                                                                                                                                                                                                                                                                                                          |
+| RedirectResponse                                                                                                                                                                                                                                                                       | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| RedirectResponse                                                                                                                                                                                                                                                                       | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The response shall include a Location header field containing a different URI, or the same URI if a request is redirected to the same target resource via a different SCP. In the former case, the URI shall be an alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. |
+| ProblemDetails                                                                                                                                                                                                                                                                         | O | 1           | 404 Not Found          | The "cause" attribute may be used to indicate the following application errors:<br>- CONTEXT_NOT_FOUND<br><br>See table 6.1.7.3-1 for the description of these errors.                                                                                                                                                                                         |
+| NOTE: The mandatory HTTP error status code for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] other than those specified in the table above also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]). |   |             |                        |                                                                                                                                                                                                                                                                                                                                                                |
+
+**Table 6.1.3.3.4.4.2-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+**Table 6.1.3.3.4.4.2-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                                                                                                                                          |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | An alternative URI of the resource located on an alternative service instance within the same NEF or NEF (service) set. Or the same URI, if a request is redirected to the same target resource via a different SCP. |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the request is redirected                                                                                                                            |
+
+### 6.1.5 Notifications
+
+#### 6.1.5.1 General
+
+This clause specifies the notifications provided by the Nnef\_SMContext service.
+
+Notifications shall comply to clause 6.2 of 3GPP TS 29.500 [4] and clause 4.6.2.3 of 3GPP TS 29.501 [5].
+
+#### 6.1.5.2 Status Notification
+
+##### 6.1.5.2.1 Description
+
+If the NF Service Consumer (e.g. the SMF) has provided the Notification URI for getting notified about change of SM Context status, the NEF shall notify the NF Service Consumer when the SM Context status is updated.
+
+##### 6.1.5.2.2 Target URI
+
+The Notification URI "{notificationUri}" shall be used with the resource URI variables defined in table 6.1.5.2.2-1.
+
+**Table 6.1.5.2.2-1: Resource URI variables for this resource**
+
+| Name            | Definition                                        |
+|-----------------|---------------------------------------------------|
+| notificationUri | String formatted as URI with the Notification Uri |
+
+##### 6.1.5.2.3 Standard Methods
+
+###### 6.1.5.2.3.1 POST
+
+This method shall support the request data structures specified in table 6.1.5.2.3.1-1 and the response data structures and response codes specified in table 6.1.5.2.3.1-2.
+
+**Table 6.1.5.2.3.1-1: Data structures supported by the POST Request Body on this resource**
+
+| Data type                   | P | Cardinality | Description                                           |
+|-----------------------------|---|-------------|-------------------------------------------------------|
+| SmContextStatusNotification | M | 1           | Representation of the SM Context status notification. |
+
+**Table 6.1.5.2.3.1-2: Data structures supported by the POST Response Body on this resource**
+
+| Data type        | P | Cardinality | Response codes         | Description                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------|---|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| n/a              |   |             | 204 No Content         | Successful notification of the SM context status change                                                                                                                                                                                                                                                                                                                                                                               |
+| RedirectResponse | O | 0..1        | 307 Temporary Redirect | Temporary redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+| RedirectResponse | O | 0..1        | 308 Permanent Redirect | Permanent redirection. The NF service consumer shall generate a Location header field containing a URI pointing to the endpoint of another NF service consumer to which the notification should be sent.<br>If an SCP redirects the message to another SCP then the location header field shall contain the same URI or a different URI pointing to the endpoint of the NF service consumer to which the notification should be sent. |
+
+NOTE: The mandatory HTTP error status codes for the POST method listed in Table 5.2.7.1-1 of 3GPP TS 29.500 [4] also apply, with response body containing an object of ProblemDetails data type (see clause 5.2.7 of 3GPP TS 29.500 [4]).
+
+**Table 6.1.5.2.3.1-3: Headers supported by the 307 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                        |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of the NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected     |
+
+**Table 6.1.5.2.3.1-4: Headers supported by the 308 Response Code on this resource**
+
+| Name                  | Data type | P | Cardinality | Description                                                                                        |
+|-----------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------|
+| Location              | string    | M | 1           | A URI pointing to the endpoint of the NF service consumer to which the notification should be sent |
+| 3gpp-Sbi-Target-Nf-Id | string    | O | 0..1        | Identifier of the target NF (service) instance ID towards which the notification is redirected     |
+
+### 6.1.6 Data Model
+
+#### 6.1.6.1 General
+
+This clause specifies the application data model supported by the API.
+
+Table 6.1.6.1-1 specifies the data types defined for the Nnef\_SMContext service based interface protocol.
+
+**Table 6.1.6.1-1: Nnef\_SMContext specific Data Types**
+
+| Data type                    | Clause defined | Description                                                                  | Applicability |
+|------------------------------|----------------|------------------------------------------------------------------------------|---------------|
+| SmContextCreateData          | 6.1.6.2.2      | Information within Create SM Context Request                                 |               |
+| SmContextCreatedData         | 6.1.6.2.3      | Information within Create SM Context Response                                |               |
+| SmContextReleaseData         | 6.1.6.2.4      |                                                                              |               |
+| SmContextReleasedData        | 6.1.6.2.5      |                                                                              |               |
+| SmContextStatusNotification  | 6.1.6.2.6      | Information within Notify SM Context Status Request                          |               |
+| NiddInformation              | 6.1.6.2.7      | NIDD information associated to the SM Context                                |               |
+| SmContextConfiguration       | 6.1.6.2.8      | NIDD related configurations that should be applied for the SM Context on NEF |               |
+| SmAllDataRateControl         | 6.1.6.2.9      | Data rate control information                                                |               |
+| SmContextUpdateData          | 6.1.6.2.10     | Information within Update SM Context Request                                 |               |
+| DeliverReqData               | 6.1.6.2.11     | Information within Deliver Service Operation Request                         |               |
+| SmContextStatus              | 6.1.6.3.3      | Enumeration of the status for an Individual SM Context                       |               |
+| SmAllDataRateControlTimeUnit | 6.1.6.3.4      | Enumeration of the time units that are applied to data rate control          |               |
+| ReleaseCause                 | 6.1.6.3.5      | Enumeration of causes for SM Context release                                 |               |
+
+Table 6.1.6.1-2 specifies data types re-used by the Nnef\_SMContext service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the N<sub><NF></sub> service based interface.
+
+**Table 6.1.6.1-2: Nnef\_SMContext re-used Data Types**
+
+| <b>Data type</b>    | <b>Reference</b>    | <b>Comments</b>                                       | <b>Applicability</b> |
+|---------------------|---------------------|-------------------------------------------------------|----------------------|
+| Uri                 | 3GPP TS 29.571 [14] | Uniform Resource Identifier                           |                      |
+| Supi                | 3GPP TS 29.571 [14] | Subscription Permanent Identifier                     |                      |
+| Gpsi                | 3GPP TS 29.571 [14] | General Public Subscription Identifier                |                      |
+| SupportedFeatures   | 3GPP TS 29.571 [14] | Supported features                                    |                      |
+| PduSessionId        | 3GPP TS 29.571 [14] | PDU Session Identifier                                |                      |
+| Dnn                 | 3GPP TS 29.571 [14] | Data Network Name                                     |                      |
+| Snssai              | 3GPP TS 29.571 [14] | Single Network Slice Selection Assistance Information |                      |
+| ProblemDetails      | 3GPP TS 29.571 [14] | Error description                                     |                      |
+| SmallDataRateStatus | 3GPP TS 29.571 [14] | Small Data Rate Control Status                        |                      |
+| ExternalGroupId     | 3GPP TS 29.571 [14] | External Group Identifier                             |                      |
+| RefToBinaryData     | 3GPP TS 29.571 [14] | Reference to binary data part                         |                      |
+| RedirectResponse    | 3GPP TS 29.571 [14] | Redirect Response                                     |                      |
+
+#### 6.1.6.2 Structured data types
+
+##### 6.1.6.2.1 Introduction
+
+This clause defines the structures to be used in resource representations.
+
+##### 6.1.6.2.2 Type: SmContextCreateData
+
+Table 6.1.6.2.2-1: Definition of type SmContextCreateData
+
+| Attribute name    | Data type              | P | Cardinality | Description                                                                                                                                                                                            | Applicability |
+|-------------------|------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi              | Supi                   | M | 1           | This IE shall contain the subscriber permanent identify of the UE.                                                                                                                                     |               |
+| pduSessionId      | PduSessionId           | M | 1           | This IE shall contain the PDU Session ID indicating the PDU session associated with the SM Context for NIDD to be created.                                                                             |               |
+| dnn               | Dnn                    | M | 1           | This IE shall contain the requested DNN.                                                                                                                                                               |               |
+| snssai            | Snssai                 | M | 1           | This IE shall contain the requested S-NSSAI for the home PLMN.                                                                                                                                         |               |
+| nefld             | string                 | M | 1           | This IE shall contain the NEF ID of the target NEF (see clause 6.1.6.2.48 of 3GPP TS 29.510 [10]).                                                                                                     |               |
+| dlNiddEndPoint    | Uri                    | M | 1           | This IE shall contain the URI of the Individual PDU session resource (see clause 6.1.3.2 of 3GPP TS 29.542 [17]) provided by the NF service consumer to handle downlink NIDD data delivery.            |               |
+| notificationUri   | Uri                    | M | 1           | This IE shall contain the URI to receive SM Context Status Notifications sent by the NEF.                                                                                                              |               |
+| niddInfo          | NiddInformation        | O | 0..1        | When present, this IE shall contain the information used for the SM Context.                                                                                                                           |               |
+| rdsSupport        | boolean                | O | 0..1        | When present, this IE shall indicate the UE capability to support RDS.<br><br>The value of this IE shall be set as following:<br>- true: UE supports RDS<br>- false (default): UE does not support RDS |               |
+| smContextConfig   | SmContextConfiguration | O | 0..1        | When present, this IE shall contain the configuration for the NIDD.                                                                                                                                    |               |
+| supportedFeatures | SupportedFeatures      | C | 0..1        | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.                                                                                                        |               |
+
+##### 6.1.6.2.3 Type: SmContextCreatedData
+
+Table 6.1.6.2.3-1: Definition of type SmContextCreatedData
+
+| Attribute name    | Data type         | P | Cardinality | Description                                                                                                                                                                                                                          | Applicability |
+|-------------------|-------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| supi              | Supi              | M | 1           | This IE shall contain the subscriber permanent identify of the UE.                                                                                                                                                                   |               |
+| pduSessionId      | PduSessionId      | M | 1           | This IE shall contain the PDU Session ID indicating the PDU session associated with the SM Context for NIDD to be created.                                                                                                           |               |
+| dnn               | Dnn               | M | 1           | This IE shall contain the requested DNN.                                                                                                                                                                                             |               |
+| snssai            | Snssai            | M | 1           | This IE shall contain the requested S-NSSAI for the home PLMN.                                                                                                                                                                       |               |
+| nefId             | string            | M | 1           | This IE shall contain the NEF ID of the target NEF (see clause 6.1.6.2.48 of 3GPP TS 29.510 [10]).                                                                                                                                   |               |
+| rdsSupport        | boolean           | O | 0..1        | When present, this IE shall indicate the NEF capability to support RDS.<br><br>The value of this IE shall be set as following:<br>- true: NEF supports RDS<br>- false (default): NEF does not support RDS                            |               |
+| extBufSupport     | boolean           | O | 0..1        | When present, this IE shall indicate whether Extended Buffering applies or not.<br><br>The value of this IE shall be set as following:<br>- true: Extended Buffering applies<br>- false (default): Extended Buffering does not apply |               |
+| supportedFeatures | SupportedFeatures | C | 0..1        | This IE shall be present if at least one optional feature defined in clause 6.1.8 is supported.                                                                                                                                      |               |
+| maxPacketSize     | integer           | O | 0..1        | Maximum Packet Size in bytes for NIDD data packet.<br>When received from the NEF, SMF shall inform the UE of the Maximum Packet Size in the PCO in the PDU Session Establishment Accept message.                                     |               |
+
+##### 6.1.6.2.4 Type: SmContextReleaseData
+
+Table 6.1.6.2.4-1: Definition of type SmContextReleaseData
+
+| Attribute name | Data type    | P | Cardinality | Description                         | Applicability |
+|----------------|--------------|---|-------------|-------------------------------------|---------------|
+| cause          | ReleaseCause | M | 1           | The cause to release the SM Context |               |
+
+##### 6.1.6.2.5 Type: SmContextReleasedData
+
+Table 6.1.6.2.5-1: Definition of type SmContextReleasedData
+
+| Attribute name      | Data type           | P | Cardinality | Description                                                                                                                                                                                                                   | Applicability |
+|---------------------|---------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| smallDataRateStatus | SmallDataRateStatus | C | 0..1        | This IE shall be present if the Small Data Rate Control is enabled for the SM Context.<br><br>When present, this IE shall contain the Small Data Rate Control Status, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2]. |               |
+| apnRateStatus       | ApnRateStatus       | C | 0..1        | This IE shall be present if the APN Rate Control is enabled for the SM Context.<br><br>When present, this IE shall contain the APN Rate Status, as specified in clause 5.4.4.40 of 3GPP TS 29.571 [14].                       |               |
+
+##### 6.1.6.2.6 Type: SmContextStatusNotification
+
+Table 6.1.6.2.6-1: Definition of type SmContextStatusNotification
+
+| Attribute name      | Data type           | P | Cardinality | Description                                                                                                                                                                                                                                              | Applicability |
+|---------------------|---------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| status              | SmContextStatus     | M | 1           | This IE shall contain the current status of the SM Context                                                                                                                                                                                               |               |
+| smContextId         | Uri                 | M | 1           | This IE shall contain the URI of the SM Context resource that triggers the notification.                                                                                                                                                                 |               |
+| cause               | ReleaseCause        | M | 1           | The cause to release the SM Context                                                                                                                                                                                                                      |               |
+| smallDataRateStatus | SmallDataRateStatus | C | 0..1        | This IE shall be present if the SM Context is released and Small Data Rate Control is enabled for the SM Context.<br><br>When present, this IE shall contain the Small Data Rate Control Status, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2]. |               |
+| apnRateStatus       | ApnRateStatus       | C | 0..1        | This IE shall be present if the APN Rate Control is enabled for the SM Context.<br><br>When present, this IE shall contain the APN Rate Status, as specified in clause 5.4.4.40 of 3GPP TS 29.571 [14].                                                  |               |
+
+##### 6.1.6.2.7 Type: NiddInformation
+
+Table 6.1.6.2.7-1: Definition of type NiddInformation
+
+| Attribute name | Data type       | P | Cardinality | Description                                                                                                                                                                 | Applicability |
+|----------------|-----------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| extGroupId     | ExternalGroupId | O | 0..1        | When present, this IE shall contain the External group Id of the UE.                                                                                                        |               |
+| gpsi           | Gpsi            | O | 0..1        | When present, this IE shall contain the GPSI of the UE.                                                                                                                     |               |
+| aflid          | string          | O | 0..1        | The string identifying the AF as the owner of associated NIDD Configuration, which is received from Nidd Information in UDM (See clause 6.1.6.2.35 of 3GPP TS 29.503 [16]). |               |
+
+NOTE: At least one of the attributes in the table shall be present.
+
+##### 6.1.6.2.8 Type: SmContextConfiguration
+
+Table 6.1.6.2.8-1: Definition of type SmContextConfiguration
+
+| Attribute name      | Data type            | P | Cardinality | Description                                                                                                                                                                                                                                                                                                                       | Applicability |
+|---------------------|----------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| smalDataRateControl | SmallDataRateControl | O | 0..1        | When present, this IE shall contain the configured Small Data Rate Control for downlink data, as specified in clause 5.31.14.3 of 3GPP TS 23.501 [2].                                                                                                                                                                             |               |
+| smallDataRateStatus | SmallDataRateStatus  | C | 0..1        | This IE shall contain the Small Data Rate Status if the Small Data Rate Status is available (see clause 5.31.14.3 of 3GPP TS 23.501 [2]).                                                                                                                                                                                         |               |
+| servPlmnDataRateCtl | integer              | O | 0..1        | When present, this IE shall contain the maximum allowed number of Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified in clause 5.31.14.2 of 3GPP TS 23.501 [2].<br><br>In Update service operation, this IE may be set to null value indicating the Serving PLMN Rate Control is disabled.<br><br>Minimum: 10 |               |
+
+NOTE: At least one of the attributes in the table shall be present.
+
+##### 6.1.6.2.9 Type: SmallDataRateControl
+
+Table 6.1.6.2.8-1: Definition of type SmallDataRateControl
+
+| Attribute name            | Data type                    | P | Cardinality | Description                                                                                                                               | Applicability |
+|---------------------------|------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| timeUnit                  | SmallDataRateControlTimeUnit | M | 1           | This IE shall indicate the time unit for which the data rate control is applied.                                                          |               |
+| maxPacketRateUI           | integer                      | O | 0..1        | If present, this IE shall indicate the maximum number of uplink packets allowed to be sent within the time unit.<br>(NOTE 1)              |               |
+| maxPacketRateDI           | integer                      | O | 0..1        | If present, this IE shall indicate the maximum number of downlink packets allowed to be sent within the time unit.<br>(NOTE 1)            |               |
+| maxAdditionalPacketRateUI | integer                      | O | 0..1        | If present, this IE shall indicate the additional maximum number of uplink packets allowed to be sent within the time unit.<br>(NOTE 2)   |               |
+| maxAdditionalPacketRateDI | integer                      | O | 0..1        | If present, this IE shall indicate the additional maximum number of downlink packets allowed to be sent within the time unit.<br>(NOTE 3) |               |
+
+NOTE 1: At least one of parameters maxPacketRateUI, or maxPacketRateDI should be included.
+
+NOTE 2: Parameter maxAdditionalPacketRateUI should be absent if parameter maxPacketRateUI is absent.
+
+NOTE 3: Parameter maxAdditionalPacketRateDI should be absent if parameter maxPacketRateDI is absent.
+
+##### 6.1.6.2.10 Type: SmContextUpdateData
+
+Table 6.1.6.2.10-1: Definition of type SmContextUpdateData
+
+| Attribute name                                                      | Data type              | P | Cardinality | Description                                                                                                                                                                                                                                                                         | Applicability |
+|---------------------------------------------------------------------|------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| dlNiddEndPoint                                                      | Uri                    | O | 0..1        | When present, this IE shall contain a new URI of Individual PDU session resource (see clause 6.1.3.2 of 3GPP TS 29.542 [17]) handling downlink NIDD data delivery.<br><br>The NEF shall send downlink data to the resource identified by the new URI after the update is completed. |               |
+| notificationUri                                                     | Uri                    | O | 0..1        | When present, this IE shall contain a new URI to receive SM Context Status Notifications sent by the NEF.<br><br>The NEF shall send SM Context Status Notification to this new URI after the update is completed.                                                                   |               |
+| smContextConfig                                                     | SmContextConfiguration | O | 0..1        | When present, this IE shall contain the configuration for the NIDD.                                                                                                                                                                                                                 |               |
+| NOTE: At least one of the attributes in the table shall be present. |                        |   |             |                                                                                                                                                                                                                                                                                     |               |
+
+##### 6.1.6.2.11 Type: DeliverReqData
+
+Table 6.1.6.2.12-1: Definition of type DeliverReqData
+
+| Attribute name | Data type       | P | Cardinality | Description                                                                            |
+|----------------|-----------------|---|-------------|----------------------------------------------------------------------------------------|
+| data           | RefToBinaryData | M | 1           | This IE shall contain the reference to Mobile Originated data to be delivered via NEF. |
+
+#### 6.1.6.3 Simple data types and enumerations
+
+##### 6.1.6.3.1 Introduction
+
+This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
+
+##### 6.1.6.3.2 Simple data types
+
+The simple data types defined in table 6.1.6.3.2-1 shall be supported.
+
+Table 6.1.6.3.2-1: Simple data types
+
+| Type Name | Type Definition | Description | Applicability |
+|-----------|-----------------|-------------|---------------|
+|           |                 |             |               |
+
+##### 6.1.6.3.3 Enumeration: SmContextStatus
+
+The enumeration SmContextStatus represents status of Individual SM Context in the NEF. It shall comply with the provisions defined in table 6.1.5.3.3-1.
+
+**Table 6.1.6.3.3-1: Enumeration SmContextStatus**
+
+| Enumeration value | Description                                                    | Applicability |
+|-------------------|----------------------------------------------------------------|---------------|
+| "RELEASED"        | Indicates that the Individual SM Context for NIDD is released. |               |
+
+##### 6.1.6.3.4 Enumeration: SmallDataRateControlTimeUnit
+
+The enumeration SmallDataRateControlTimeUnit represents the allowed time unit. It shall comply with the provisions defined in table 6.1.5.3.3-1.
+
+**Table 6.1.6.3.4-1: Enumeration SmallDataRateControlTimeUnit**
+
+| Enumeration value | Description                                          | Applicability |
+|-------------------|------------------------------------------------------|---------------|
+| "MINUTE"          | Indicates the rate control is applied per minute.    |               |
+| "HOUR"            | Indicates the rate control is applied per hour.      |               |
+| "DAY"             | Indicates the rate control is applied per day.       |               |
+| "WEEK"            | Indicates the rate control is applied per week.      |               |
+| "6MINUTES"        | Indicates the rate control is applied per 6 minutes. |               |
+
+##### 6.1.6.3.5 Enumeration: ReleaseCause
+
+The enumeration ReleaseCause represents cause for release of the SM Context in the NEF. It shall comply with the provisions defined in table 6.1.6.3.5-1.
+
+**Table 6.1.6.3.5-1: Enumeration ReleaseCause**
+
+| Enumeration value      | Description                                                                              | Applicability |
+|------------------------|------------------------------------------------------------------------------------------|---------------|
+| "PDU_SESSION_RELEASED" | Indicates the SM Context is to be released due to corresponding PDU Session is released. |               |
+
+### 6.1.7 Error Handling
+
+#### 6.1.7.1 General
+
+For the Nnef\_SMContext API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [5]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [4] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [4].
+
+In addition, the requirements in the following clauses are applicable for the Nnef\_SMContext API.
+
+#### 6.1.7.2 Protocol Errors
+
+Protocol errors handling shall be supported as specified in clause 5.2.7 of 3GPP TS 29.500 [4]. No specific procedures for the Nnef\_SMContext service are specified.
+
+#### 6.1.7.3 Application Errors
+
+The application errors defined for the Nnef\_SMContext service are listed in Table 6.1.7.3-1.
+
+**Table 6.1.7.3-1: Application errors**
+
+| <b>Application Error</b>           | <b>HTTP status code</b> | <b>Description</b>                                                                                                                                                                                                                                  |
+|------------------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| "USER_UNKNOWN"                     | 403                     | This application error indicates that the User Identity does not exist in the NEF.                                                                                                                                                                  |
+| "NIDD_CONFIGURATION_NOT_AVAILABLE" | 403                     | This application error indicates that there is no valid NIDD configuration exists for the requested SM Context in the NEF, and NIDD configuration triggered by the NEF (see clause 4.4.12.2 of 3GPP TS 29.522 [15]) is not supported or has failed. |
+| "CONTEXT_NOT_FOUND"                | 404                     | This application error indicates that the SM Context referred by the requested resource URI does not exist in the NEF.                                                                                                                              |
+
+### 6.1.8 Feature negotiation
+
+The optional features in table 6.1.8-1 are defined for the Nnef\_SMContext API. They shall be negotiated using the extensibility mechanism defined in clause 6.6 of 3GPP TS 29.500 [4].
+
+**Table 6.1.8-1: Supported Features**
+
+| <b>Feature number</b> | <b>Feature Name</b> | <b>Description</b> |
+|-----------------------|---------------------|--------------------|
+|                       |                     |                    |
+
+### 6.1.9 Security
+
+As indicated in 3GPP TS 33.501 [8] and 3GPP TS 29.500 [4], the access to the Nnef\_SMContext API may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [9]), based on local configuration, using the "Client Credentials" authorization grant, where the NRF (see 3GPP TS 29.510 [10]) plays the role of the authorization server.
+
+If OAuth2 is used, an NF Service Consumer, prior to consuming services offered by the Nnef\_SMContext API, shall obtain a "token" from the authorization server, by invoking the Access Token Request service, as described in 3GPP TS 29.510 [10], clause 5.4.2.2.
+
+NOTE: When multiple NRFs are deployed in a network, the NRF used as authorization server is the same NRF that the NF Service Consumer used for discovering the Nnef\_SMContext service.
+
+The Nnef\_SMContext API defines a single scope "nnef-smcontext" for the entire service, and it does not define any additional scopes at resource or operation level.
+
+### 6.1.10 HTTP redirection
+
+An HTTP request may be redirected to a different NEF service instance, within the same NEF or a different NEF of an NEF set, e.g. when an NEF service instance is part of an NEF (service) set or when using indirect communications (see 3GPP TS 29.500 [4]).
+
+An SCP that reselects a different NEF producer instance will return the NF Instance ID of the new NEF producer instance in the 3gpp-Sbi-Producer-Id header, as specified in clause 6.10.3.4 of 3GPP TS 29.500 [4].
+
+If an NEF within an NEF set redirects a service request to a different NEF of the set using an 307 Temporary Redirect or 308 Permanent Redirect status code, the identity of the new NEF towards which the service request is redirected shall be indicated in the 3gpp-Sbi-Target-Nf-Id header of the 307 Temporary Redirect or 308 Permanent Redirect response as specified in clause 6.10.9.1 of 3GPP TS 29.500 [4].
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This Annex specifies the formal definition of the Nnef\_SMContext API. It consists of OpenAPI 3.0.0 specifications in YAML format.
+
+This Annex takes precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API(s).
+
+NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification files contained in this 3GPP Technical Specification are available on a Git-based repository, that uses the GitLab software version control system (see 3GPP TS 29.501 [5] clause 5.3.1 and 3GPP TR 21.900 [7] clause 5B).
+
+## A.2 Nnef\_SMContext API
+
+```
+openapi: 3.0.0
+
+info:
+  title: Nnef_SMContext
+  version: 1.0.2
+  description: |
+    Nnef SMContext Service.
+    © 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.541 V16.4.0; 5G System; Session Management Services for Non-IP Data
+    Delivery (NIDD).
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.541/
+
+servers:
+  - url: '{apiRoot}/nnef-smcontext/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+security:
+  - {}
+  - oAuth2ClientCredentials:
+    - nnef-smcontext
+
+paths:
+  /sm-contexts:
+    post:
+      summary: Create SM Context
+      operationId: Create
+      tags:
+        - SM Contexts Collection (Collection)
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SmContextCreateData'
+      responses:
+        '201':
+          description: Success
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SmContextCreatedData'
+          headers:
+```
+
+```
+
+Location:
+  description: >
+    'Contains the URI of the newly created Individual SM Context resource, according to
+the structure:
+    {apiRoot}/nnef-smcontext/<version>/sm-contexts/{smContextId}'
+  required: true
+  schema:
+    type: string
+'307':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+'308':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+'400':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+'403':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/403'
+'411':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+'413':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+'415':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+'429':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+'503':
+  $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+default:
+  $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+callbacks:
+  StatusNotify:
+    '{ $request.body#/notificationUri }':
+      post:
+        requestBody:
+          required: true
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SmContextStatusNotification'
+        responses:
+          '204':
+            description: No Content, Notification was successful
+          '307':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+          '308':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+          '400':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+          '411':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/411'
+          '413':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/413'
+          '415':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/415'
+          '429':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+          '500':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+          '503':
+            $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+          default:
+            $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/sm-contexts/{smContextId}/release:
+  post:
+    summary: Delete SM Context
+    operationId: Delete
+    tags:
+      - Individual SM Context (Document)
+    parameters:
+      - name: smContextId
+        in: path
+        description: SM Context Resource ID
+        required: true
+        schema:
+          type: string
+    requestBody:
+
+```
+
+```
+
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: '#/components/schemas/SmContextReleaseData'
+  responses:
+    '200':
+      description: OK. Resource representation is returned
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/SmContextReleasedData'
+    '204':
+      description: No Content.
+    '307':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+    '308':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+    '400':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+    '404':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+    '406':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/406'
+    '429':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/sm-contexts/{smContextId}/update:
+  post:
+    summary: Update SM Context
+    operationId: Update
+    tags:
+      - Individual SM Context (Document)
+    parameters:
+      - name: smContextId
+        in: path
+        description: SM Context Resource ID
+        required: true
+        schema:
+          type: string
+    requestBody:
+      required: true
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/SmContextUpdateData'
+    responses:
+      '204':
+        description: No Content.
+      '307':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+      '308':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+      '400':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+      '404':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+      '406':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/406'
+      '429':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+/sm-contexts/{smContextId}/deliver:
+  post:
+    summary: Deliver Uplink MO Data
+    operationId: Deliver
+
+```
+
+```
+
+tags:
+  - Individual SM Context (Document)
+parameters:
+  - name: smContextId
+    in: path
+    description: SM Context Resource ID
+    required: true
+    schema:
+      type: string
+requestBody:
+  required: true
+  content:
+    multipart/related: # message with binary body part(s)
+      schema:
+        type: object
+        properties: # Request parts
+          jsonData:
+            $ref: '#/components/schemas/DeliverReqData'
+          binaryMoData:
+            type: string
+            format: binary
+      encoding:
+        jsonData:
+          contentType: application/json
+        binaryMoData:
+          contentType: application/octet-stream
+          headers:
+            Content-Id:
+              schema:
+                type: string
+responses:
+  '204':
+    description: No Content.
+  '307':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/307'
+  '308':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/308'
+  '400':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/400'
+  '404':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/404'
+  '406':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/406'
+  '429':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29571_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29571_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{nrfApiRoot}/oauth2/token'
+          scopes:
+            nnef-smcontext: Access to the Nnef_SMContext API
+
+schemas:
+#
+# Structured Data Types
+#
+  SmContextCreateData:
+    type: object
+    properties:
+      supi:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+      pduSessionId:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId'
+      dnn:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
+      snssai:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai'
+      nefId:
+
+```
+
+```
+type: string
+description: This IE shall contain the NEF ID of the target NEF.
+dlNiddEndPoint:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+notificationUri:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+niddInfo:
+  $ref: '#/components/schemas/NiddInformation'
+rdsSupport:
+  type: boolean
+  description: |
+    When present, this IE shall indicate the UE capability to support RDS.
+    The value of this IE shall be set as following
+    - true  UE supports RDS
+    - false (default)  UE does not support RDS
+smContextConfig:
+  $ref: '#/components/schemas/SmContextConfiguration'
+supportedFeatures:
+  $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+required:
+- supi
+- pduSessionId
+- dnn
+- snssai
+- nefId
+- dlNiddEndPoint
+- notificationUri
+
+SmContextCreatedData:
+type: object
+properties:
+  supi:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi'
+  pduSessionId:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId'
+  dnn:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'
+  snssai:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/SNSSAI'
+  nefId:
+    type: string
+    description: This IE shall contain the NEF ID of the target NEF.
+  rdsSupport:
+    type: boolean
+    default: false
+    description: |
+      When present, this IE shall indicate the NEF capability to support RDS.
+      The value of this IE shall be set as following
+      - true  NEF supports RDS
+      - false (default)  NEF does not support RDS
+  extBufSupport:
+    type: boolean
+    default: false
+    description: |
+      When present, this IE shall indicate whether Extended Buffering applies or not.
+      The value of this IE shall be set as following
+      - true  Extended Buffering applies
+      - false (default)  Extended Buffering does not apply
+  supportedFeatures:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+  maxPacketSize:
+    type: integer
+required:
+- supi
+- pduSessionId
+- dnn
+- snssai
+- nefId
+
+SmContextReleaseData:
+type: object
+properties:
+  cause:
+    $ref: '#/components/schemas/ReleaseCause'
+required:
+- cause
+
+SmContextReleasedData:
+```
+
+```
+
+    type: object
+    properties:
+      smallDataRateStatus:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus'
+      apnRateStatus:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/ApnRateStatus'
+
+SmContextStatusNotification:
+  type: object
+  properties:
+    status:
+      $ref: '#/components/schemas/SmContextStatus'
+    smContextId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    cause:
+      $ref: '#/components/schemas/ReleaseCause'
+    smallDataRateStatus:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus'
+    apnRateStatus:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/ApnRateStatus'
+  required:
+    - status
+    - smContextId
+
+NiddInformation:
+  type: object
+  properties:
+    extGroupId:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/ExternalGroupId'
+    gpsi:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi'
+    afId:
+      type: string
+      description: When present, this IE shall contain the AF Id used for the SM Context.
+
+SmContextConfiguration:
+  type: object
+  properties:
+    smalDataRateControl:
+      $ref: '#/components/schemas/SmallDataRateControl'
+    smallDataRateStatus:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SmallDataRateStatus'
+    servPlmnDataRateCtl:
+      type: integer
+      minimum: 10
+      nullable: true
+      description: >
+        When present, this IE shall contain the maximum allowed number of
+        Downlink NAS Data PDUs per deci hour of the serving PLMN, as specified
+        in subclause 5.31.14.2 of 3GPP TS 23.501 [2].
+        Minimum 10
+
+SmallDataRateControl:
+  type: object
+  properties:
+    timeUnit:
+      $ref: '#/components/schemas/SmallDataRateControlTimeUnit'
+    maxPacketRateUl:
+      type: integer
+    maxPacketRateDl:
+      type: integer
+    maxAdditionalPacketRateUl:
+      type: integer
+    maxAdditionalPacketRateDl:
+      type: integer
+  required:
+    - timeUnit
+
+SmContextUpdateData:
+  type: object
+  properties:
+    dlNiddEndPoint:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    notificationUri:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    smContextConfig:
+      $ref: '#/components/schemas/SmContextConfiguration'
+```
+
+```
+DeliverReqData:
+  type: object
+  properties:
+    data:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/RefToBinaryData'
+  required:
+    - data
+
+#
+# Simple Data Types
+#
+
+#
+# Enumeration Data Types
+#
+
+SmContextStatus:
+  anyOf:
+    - type: string
+      enum:
+        - RELEASED
+    - type: string
+      description: >
+        This string provides forward-compatibility with future
+        extensions to the enumeration but is not used to encode
+        content defined in the present version of this API.
+      description: >
+        Possible values are
+        - RELEASED: Indicates that the Individual SM Context for NIDD is released.
+
+SmallDataRateControlTimeUnit:
+  anyOf:
+    - type: string
+      enum:
+        - MINUTE
+        - HOUR
+        - DAY
+        - WEEK
+        - 6MINUTES
+    - type: string
+      description: >
+        This string provides forward-compatibility with future
+        extensions to the enumeration but is not used to encode
+        content defined in the present version of this API.
+      description: >
+        Possible values are
+        - MINUTE: Indicates the rate control is applied per minute.
+        - HOUR: Indicates the rate control is applied per hour.
+        - DAY: Indicates the rate control is applied per day.
+        - WEEK: Indicates the rate control is applied per week.
+        - 6MINUTES: Indicates the rate control is applied per 6 minutes.
+
+ReleaseCause:
+  anyOf:
+    - type: string
+      enum:
+        - PDU_SESSION_RELEASED
+    - type: string
+      description: >
+        This string provides forward-compatibility with future
+        extensions to the enumeration but is not used to encode
+        content defined in the present version of this API.
+      description: >
+        The cause to release the SM Context. Possible values are
+        - PDU_SESSION_RELEASED: Indicates that the Individual SM Context for NIDD is released.
+```
+
+# Annex B (informative): Change history
+
+| Change history |          |           |      |     |     |                                                                                                                    |  |             |
+|----------------|----------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                    |  | New version |
+| 2019-09        | CT4#93   | C4-193889 |      |     |     | Initial Draft.                                                                                                     |  | 0.1.0       |
+| 2019-10        | CT4#94   | C4-194527 |      |     |     | Incorporated pCRs agreed on CT4#94, including: C4-194208, C4-194440, C4-194441, C4-194442, C4-194443.              |  | 0.2.0       |
+| 2019-11        | CT4#95   | C4-195642 |      |     |     | Incorporated pCRs agreed on CT4#95, including: C4-195283, C4-195284, C4-195295.                                    |  | 0.3.0       |
+| 2019-12        | CT#86    | CP-193072 |      |     |     | TS presented for information                                                                                       |  | 1.0.0       |
+| 2020-03        | CT4#96-e | C4-201265 |      |     |     | Incorporated pCRs agreed on CT4#96-e, including: C4-200588, C4-200589, C4-200744, C4-200944, C4-200985, C4-201156. |  | 1.1.0       |
+| 2020-03        | CT#87e   | CP-200061 |      |     |     | Presented for approval                                                                                             |  | 2.0.0       |
+| 2020-03        | CT#87e   |           |      |     |     | Approved at CT#87e                                                                                                 |  | 16.0.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0001 | 2   | B   | Add Extended Buffering                                                                                             |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201071 | 0002 |     | F   | Storage of YAML files in ETSI Forge                                                                                |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0003 |     | F   | Revert MO Exception Data Indication                                                                                |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0004 | 1   | F   | Parameter supplement to Create Service                                                                             |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0005 | 1   | F   | Parameter supplement to Delete Service                                                                             |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0006 | 1   | F   | Parameter supplement to Status Notify Service                                                                      |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201046 | 0008 | 1   | F   | Miscellaneous Corrections                                                                                          |  | 16.1.0      |
+| 2020-06        | CT#88e   | CP-201073 | 0009 |     | F   | 29.541 Rel-16 API version and External doc update                                                                  |  | 16.1.0      |
+| 2020-12        | CT#90e   | CP-203032 | 0010 |     | F   | YAML files in 3GPP Forge                                                                                           |  | 16.2.0      |
+| 2021-03        | CT#91e   | CP-210037 | 0011 | 1   | F   | HTTP 3xx redirection                                                                                               |  | 16.3.0      |
+| 2021-03        | CT#91e   | CP-210078 | 0012 | -   | F   | 29.541 Rel-16 API version and External doc update                                                                  |  | 16.3.0      |
+| 2021-06        | CT#92e   | CP-210059 | 0016 | 1   | F   | Redirect Response                                                                                                  |  | 16.4.0      |
+| 2021-06        | CT#92e   | CP-210073 | 0018 | -   | F   | 29.541 Rel-16 API version and External doc update                                                                  |  | 16.4.0      |
+| 2021-09        | CT#93e   | CP-212060 | 0019 | -   | F   | 3xx description correction for SCP                                                                                 |  | 16.5.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29549/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-16/29_series/29549/030c758fd425016b03290c8f11bef69d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c306b6cb3b7f8701d04366502e1c39f7a93762c9
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/030c758fd425016b03290c8f11bef69d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a735b1410bda72b1605936487c570d885a334637f74f6116ed364594a5e1a4d8
+size 29055
diff --git a/marked/Rel-16/29_series/29549/294444660b1376c49aeca748b8184e77_img.jpg b/marked/Rel-16/29_series/29549/294444660b1376c49aeca748b8184e77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f6950bdb9b37f66ad68a0f4c13aa2fe6ba850898
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/294444660b1376c49aeca748b8184e77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:879006af1b46fdf4d6cfbae944391a9ed2b0b98179673c3e6f4e9bc8101e852f
+size 11633
diff --git a/marked/Rel-16/29_series/29549/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29549/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cfa7bea10484c8241f0c79fac199a1e797713c5
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1dbc5d3adb935545c3bde1cb4ac0d739ee6ef69af0b377e7b6f8f5cad4757d5
+size 9282
diff --git a/marked/Rel-16/29_series/29549/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29549/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75c42d7c11c8998deabe996404ae0a9606a484dc
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:468137148f5fedf1a756cb4c2414909a33dfb8c8680d5b3815b36f47bb3b91e2
+size 5780
diff --git a/marked/Rel-16/29_series/29549/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/29_series/29549/a4b963a07cc368283154762c4b156fe7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43bf26c28e1d27bb91c88e289b280f0db50491f4
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/a4b963a07cc368283154762c4b156fe7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cc839ecbbedaf17f03eedda5759d0c88d4c3dc5428722fa361e97bb7cb5b20d
+size 16726
diff --git a/marked/Rel-16/29_series/29549/c468d53e877568cd7d8c5ba1632c2e65_img.jpg b/marked/Rel-16/29_series/29549/c468d53e877568cd7d8c5ba1632c2e65_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b626ae9216a2d1aa0a41dd489bb3f6983463df5
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/c468d53e877568cd7d8c5ba1632c2e65_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f0ea6ccd0e504a5e17a9a5cf026b766bd28b561c8306f51c6eb761d2e0b8144
+size 12069
diff --git a/marked/Rel-16/29_series/29549/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-16/29_series/29549/df1966d80c74bc127f159a48f38b13ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da128ccd21deb6639be9b834cd64af8103af3257
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/df1966d80c74bc127f159a48f38b13ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e818316f3d6dc2f769b348917d3d66f6b058af3700824d0f019cbb5cae72dfec
+size 17033
diff --git a/marked/Rel-16/29_series/29549/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/29_series/29549/ead623e6a8ec701df64567695a57d01c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54413153a8266732a0fa4207825b50d8db4f95dd
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/ead623e6a8ec701df64567695a57d01c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec56836e71254461a425db2fd1189497d37ca4348f146117e0fbf3abd694c6c6
+size 18279
diff --git a/marked/Rel-16/29_series/29549/raw.md b/marked/Rel-16/29_series/29549/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..551742ee9c82ba53f386c7258b9f32fac4781453
--- /dev/null
+++ b/marked/Rel-16/29_series/29549/raw.md
@@ -0,0 +1,4507 @@
+
+
+# 3GPP TS 29.549 V16.6.0 (2022-12)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage 3 (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                                                                    |    |
+|----------------------------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                                                     | 9  |
+| 1 Scope.....                                                                                                                                       | 11 |
+| 2 References.....                                                                                                                                  | 11 |
+| 3 Definitions of terms and abbreviations .....                                                                                                     | 12 |
+| 3.1 Terms.....                                                                                                                                     | 12 |
+| 3.2 Abbreviations .....                                                                                                                            | 12 |
+| 4 Overview.....                                                                                                                                    | 13 |
+| 5 Services offered by the SEAL servers .....                                                                                                       | 13 |
+| 5.1 Introduction of SEAL services.....                                                                                                             | 13 |
+| 5.2 Location management APIs .....                                                                                                                 | 15 |
+| 5.2.1 SS_LocationReporting API .....                                                                                                               | 15 |
+| 5.2.1.1 Service Description.....                                                                                                                   | 15 |
+| 5.2.1.1.1 Overview .....                                                                                                                           | 15 |
+| 5.2.1.2 Service Operations.....                                                                                                                    | 15 |
+| 5.2.1.2.1 Introduction .....                                                                                                                       | 15 |
+| 5.2.1.2.2 Create_Trigger_Location_Reporting .....                                                                                                  | 15 |
+| 5.2.1.2.2.1 General .....                                                                                                                          | 15 |
+| 5.2.1.2.2.2 VAL server providing trigger configuration using Create_Trigger_Location_Reporting service operation.....                              | 15 |
+| 5.2.1.2.3 Fetch_Location_Report_Trigger.....                                                                                                       | 16 |
+| 5.2.1.2.3.1 General .....                                                                                                                          | 16 |
+| 5.2.1.2.3.2 VAL server fetching trigger configuration using Fetch_Location_Report_Trigger service operation.....                                   | 16 |
+| 5.2.1.2.4 Update_Trigger_Location_Reporting .....                                                                                                  | 16 |
+| 5.2.1.2.4.1 General .....                                                                                                                          | 16 |
+| 5.2.1.2.4.2 VAL server providing trigger configuration using Update_Trigger_Location_Reporting service operation.....                              | 16 |
+| 5.2.1.2.5 Cancel_Trigger_Location_Reporting.....                                                                                                   | 16 |
+| 5.2.1.2.5.1 General .....                                                                                                                          | 16 |
+| 5.2.1.2.5.2 VAL server providing trigger configuration using Cancel_Trigger_Location_Reporting service operation.....                              | 17 |
+| 5.2.2 SS_LocationInfoEvent API.....                                                                                                                | 17 |
+| 5.2.3 SS_LocationInfoRetrieval API.....                                                                                                            | 17 |
+| 5.3 Group management APIs .....                                                                                                                    | 17 |
+| 5.3.1 SS_GroupManagement API .....                                                                                                                 | 17 |
+| 5.3.1.1 Service Description.....                                                                                                                   | 17 |
+| 5.3.1.1.1 Overview .....                                                                                                                           | 17 |
+| 5.3.1.2 Service Operations.....                                                                                                                    | 17 |
+| 5.3.1.2.1 Introduction .....                                                                                                                       | 17 |
+| 5.3.1.2.2 Query_Group_Info .....                                                                                                                   | 18 |
+| 5.3.1.2.2.1 General .....                                                                                                                          | 18 |
+| 5.3.1.2.2.2 VAL server fetching VAL group documents, group membership and configuration information using Query_Group_Info service operation ..... | 18 |
+| 5.3.1.2.3 Update_Group_Info .....                                                                                                                  | 18 |
+| 5.3.1.2.3.1 General .....                                                                                                                          | 18 |
+| 5.3.1.2.3.2 VAL server modifying group membership and configuration using Update_Group_Info service operation.....                                 | 19 |
+| 5.3.1.2.4 Create_Group .....                                                                                                                       | 19 |
+| 5.3.1.2.4.1 General .....                                                                                                                          | 19 |
+| 5.3.1.2.4.2 VAL server creating new group using Create_Group service operation.....                                                                | 19 |
+| 5.3.1.2.5 Delete_Group .....                                                                                                                       | 19 |
+| 5.3.1.2.5.1 General .....                                                                                                                          | 19 |
+| 5.3.1.2.5.2 VAL server deleting VAL group using Delete_Group service operation .....                                                               | 19 |
+| 5.3.2 SS_GroupManagementEvent API.....                                                                                                             | 20 |
+
+|             |                                                                                                              |    |
+|-------------|--------------------------------------------------------------------------------------------------------------|----|
+| 5.4         | Configuration management APIs.....                                                                           | 20 |
+| 5.4.1       | SS_UserProfileRetrieval API .....                                                                            | 20 |
+| 5.4.1.1     | Service Description.....                                                                                     | 20 |
+| 5.4.1.1.1   | Overview .....                                                                                               | 20 |
+| 5.4.1.2     | Service Operations.....                                                                                      | 20 |
+| 5.4.1.2.1   | Introduction .....                                                                                           | 20 |
+| 5.4.1.2.2   | Obtain_User_Profile.....                                                                                     | 20 |
+| 5.4.1.2.2.1 | General .....                                                                                                | 20 |
+| 5.4.1.2.2.2 | VAL server retrieving VAL user profile information using Obtain_User_Profile service operation .....         | 20 |
+| 5.4.2       | SS_UserProfileEvent API .....                                                                                | 21 |
+| 5.5         | Network resource management APIs.....                                                                        | 21 |
+| 5.5.1       | SS_Network_Resource_Adaptation API.....                                                                      | 21 |
+| 5.5.1.1     | Service Description.....                                                                                     | 21 |
+| 5.5.1.1.1   | Overview .....                                                                                               | 21 |
+| 5.5.1.2     | Service Operations.....                                                                                      | 21 |
+| 5.5.1.2.1   | Introduction .....                                                                                           | 21 |
+| 5.5.1.2.2   | Reserve_Network_Resource .....                                                                               | 21 |
+| 5.5.1.2.2.1 | General .....                                                                                                | 21 |
+| 5.5.1.2.2.2 | VAL server requesting for network resource adaptation using Reserve_Network_Resource service operation.....  | 21 |
+| 5.5.1.2.3   | Request_Unicast_Resource.....                                                                                | 22 |
+| 5.5.1.2.3.1 | General .....                                                                                                | 22 |
+| 5.5.1.2.3.2 | VAL server requesting for unicast resource using Request_Unicast_Resource service operation.....             | 22 |
+| 5.5.1.2.4   | Update_Unicast_Resource .....                                                                                | 22 |
+| 5.5.1.2.4.1 | General .....                                                                                                | 22 |
+| 5.5.1.2.4.2 | VAL server requesting for updating the unicast resource using Update_Unicast_Resource service operation..... | 22 |
+| 5.5.1.2.5   | Request_Multicast_Resource.....                                                                              | 22 |
+| 5.5.1.2.5.1 | General .....                                                                                                | 22 |
+| 5.5.1.2.5.2 | VAL server requesting for multicast resource using Request_Multicast_Resource service operation.....         | 22 |
+| 5.5.1.2.6   | Notify_UP_Delivery_Mode .....                                                                                | 23 |
+| 5.5.1.2.6.1 | General .....                                                                                                | 23 |
+| 5.5.1.2.6.2 | Notifying user plane events using Notify_UP_Delivery_Mode service operation .....                            | 23 |
+| 5.6         | Events APIs.....                                                                                             | 23 |
+| 5.6.1       | SS_Events API .....                                                                                          | 23 |
+| 5.6.1.1     | Service Description.....                                                                                     | 23 |
+| 5.6.1.1.1   | Overview .....                                                                                               | 23 |
+| 5.6.1.2     | Service Operations.....                                                                                      | 23 |
+| 5.6.1.2.1   | Introduction .....                                                                                           | 23 |
+| 5.6.1.2.2   | Subscribe_Event.....                                                                                         | 23 |
+| 5.6.1.2.2.1 | General .....                                                                                                | 23 |
+| 5.6.1.2.2.2 | Subscribing to SEAL events using Subscribe_Event service operation.....                                      | 24 |
+| 5.6.1.2.3   | Notify_Event .....                                                                                           | 24 |
+| 5.6.1.2.3.1 | General .....                                                                                                | 24 |
+| 5.6.1.2.3.2 | Notifying SEAL events using Notify_Event service operation.....                                              | 24 |
+| 5.6.1.2.4   | Unsubscribe_Event.....                                                                                       | 24 |
+| 5.6.1.2.4.1 | General .....                                                                                                | 24 |
+| 5.6.1.2.4.2 | Unsubscribing from SEAL events using Unsubscribe_Event service operation .....                               | 24 |
+| 5.7         | Key management APIs.....                                                                                     | 24 |
+| 5.7.1       | SS_KeyInfoRetrieval API .....                                                                                | 25 |
+| 5.7.1.1     | Service Description.....                                                                                     | 25 |
+| 5.7.1.1.1   | Overview .....                                                                                               | 25 |
+| 5.7.1.2     | Service Operations.....                                                                                      | 25 |
+| 5.7.1.2.1   | Introduction .....                                                                                           | 25 |
+| 5.7.1.2.2   | Obtain_Key_Info.....                                                                                         | 25 |
+| 5.7.1.2.2.1 | General .....                                                                                                | 25 |
+| 5.7.1.2.2.2 | VAL server obtaining VAL service specific key material using Obtain_Key_Info service operation .....         | 25 |
+
+|               |                                                                 |    |
+|---------------|-----------------------------------------------------------------|----|
+| 6             | SEAL Design Aspects Common for All APIs .....                   | 25 |
+| 6.1           | General .....                                                   | 25 |
+| 6.2           | Data Types.....                                                 | 26 |
+| 6.2.1         | General .....                                                   | 26 |
+| 6.2.2         | Referenced structured data types.....                           | 26 |
+| 6.2.3         | Referenced Simple data types and enumerations .....             | 26 |
+| 6.3           | Usage of HTTP.....                                              | 26 |
+| 6.4           | Content type .....                                              | 27 |
+| 6.5           | URI structure .....                                             | 27 |
+| 6.6           | Notifications .....                                             | 27 |
+| 6.7           | Error Handling.....                                             | 28 |
+| 6.8           | Feature negotiation.....                                        | 28 |
+| 6.9           | HTTP headers.....                                               | 28 |
+| 6.10          | Conventions for Open API specification files.....               | 28 |
+| 7             | SEAL API Definitions .....                                      | 28 |
+| 7.1           | Location management APIs .....                                  | 28 |
+| 7.1.1         | SS_LocationReporting API .....                                  | 28 |
+| 7.1.1.1       | API URI .....                                                   | 28 |
+| 7.1.1.2       | Resources .....                                                 | 29 |
+| 7.1.1.2.1     | Overview .....                                                  | 29 |
+| 7.1.1.2.2     | Resource: SEAL Location Reporting Configurations.....           | 29 |
+| 7.1.1.2.2.1   | Description .....                                               | 29 |
+| 7.1.1.2.2.2   | Resource Definition.....                                        | 29 |
+| 7.1.1.2.2.3   | Resource Standard Methods .....                                 | 30 |
+| 7.1.1.2.2.3.1 | POST.....                                                       | 30 |
+| 7.1.1.2.2.4   | Resource Custom Operations .....                                | 30 |
+| 7.1.1.2.3     | Resource: Individual SEAL Location Reporting Configuration..... | 30 |
+| 7.1.1.2.3.1   | Description .....                                               | 30 |
+| 7.1.1.2.3.2   | Resource Definition.....                                        | 30 |
+| 7.1.1.2.3.3   | Resource Standard Methods .....                                 | 31 |
+| 7.1.1.2.3.3.1 | GET.....                                                        | 31 |
+| 7.1.1.2.3.3.2 | PUT.....                                                        | 31 |
+| 7.1.1.2.3.3.3 | DELETE .....                                                    | 32 |
+| 7.1.1.2.3.4   | Resource Custom Operations .....                                | 32 |
+| 7.1.1.3       | Notifications.....                                              | 32 |
+| 7.1.1.4       | Data Model .....                                                | 32 |
+| 7.1.1.4.1     | General .....                                                   | 32 |
+| 7.1.1.4.2     | Structured data types .....                                     | 33 |
+| 7.1.1.4.2.1   | Introduction .....                                              | 33 |
+| 7.1.1.4.2.2   | Type: LocationReportConfiguration .....                         | 33 |
+| 7.1.1.4.3     | Simple data types and enumerations .....                        | 33 |
+| 7.1.1.5       | Error Handling .....                                            | 33 |
+| 7.1.1.6       | Feature negotiation .....                                       | 33 |
+| 7.2           | Group management APIs .....                                     | 34 |
+| 7.2.1         | SS_GroupManagement API .....                                    | 34 |
+| 7.2.1.1       | API URI .....                                                   | 34 |
+| 7.2.1.2       | Resources .....                                                 | 34 |
+| 7.2.1.2.1     | Overview .....                                                  | 34 |
+| 7.2.1.2.2     | Resource: VAL Group Documents .....                             | 35 |
+| 7.2.1.2.2.1   | Description .....                                               | 35 |
+| 7.2.1.2.2.2   | Resource Definition.....                                        | 35 |
+| 7.2.1.2.2.3   | Resource Standard Methods .....                                 | 35 |
+| 7.2.1.2.2.3.1 | POST.....                                                       | 35 |
+| 7.2.1.2.2.3.2 | GET.....                                                        | 36 |
+| 7.2.1.2.2.4   | Resource Custom Operations .....                                | 36 |
+| 7.2.1.2.3     | Resource: Individual VAL Group Document .....                   | 37 |
+| 7.2.1.2.3.1   | Description .....                                               | 37 |
+| 7.2.1.2.3.2   | Resource Definition.....                                        | 37 |
+| 7.2.1.2.3.3   | Resource Standard Methods .....                                 | 37 |
+| 7.2.1.2.3.3.1 | GET.....                                                        | 37 |
+| 7.2.1.2.3.3.2 | PUT.....                                                        | 38 |
+
+|               |                                                   |    |
+|---------------|---------------------------------------------------|----|
+| 7.2.1.2.3.3.3 | DELETE .....                                      | 38 |
+| 7.2.1.2.3.4   | Resource Custom Operations .....                  | 39 |
+| 7.2.1.3       | Notifications.....                                | 39 |
+| 7.2.1.4       | Data Model .....                                  | 39 |
+| 7.2.1.4.1     | General .....                                     | 39 |
+| 7.2.1.4.2     | Structured data types .....                       | 40 |
+| 7.2.1.4.2.1   | Introduction .....                                | 40 |
+| 7.2.1.4.2.2   | Type: VALGroupDocument.....                       | 40 |
+| 7.2.1.4.3     | Simple data types and enumerations .....          | 40 |
+| 7.2.1.5       | Error Handling .....                              | 40 |
+| 7.2.1.6       | Feature negotiation .....                         | 40 |
+| 7.3           | Configuration management APIs.....                | 41 |
+| 7.3.1         | SS_UserProfileRetrieval API.....                  | 41 |
+| 7.3.1.1       | API URI .....                                     | 41 |
+| 7.3.1.2       | Resources .....                                   | 41 |
+| 7.3.1.2.1     | Overview .....                                    | 41 |
+| 7.3.1.2.2     | Resource: VAL Services.....                       | 41 |
+| 7.3.1.2.2.1   | Description .....                                 | 41 |
+| 7.3.1.2.2.2   | Resource Definition.....                          | 41 |
+| 7.3.1.2.2.3   | Resource Standard Methods .....                   | 42 |
+| 7.3.1.2.2.3.1 | GET.....                                          | 42 |
+| 7.3.1.2.2.4   | Resource Custom Operations .....                  | 42 |
+| 7.3.1.3       | Notifications.....                                | 42 |
+| 7.3.1.4       | Data Model .....                                  | 42 |
+| 7.3.1.4.1     | General .....                                     | 42 |
+| 7.3.1.4.2     | Structured data types .....                       | 43 |
+| 7.3.1.4.2.1   | Introduction .....                                | 43 |
+| 7.3.1.4.2.2   | Type: ProfileDoc .....                            | 43 |
+| 7.3.1.4.2.3   | Type: ValTargetUe.....                            | 43 |
+| 7.3.1.4.3     | Simple data types and enumerations .....          | 43 |
+| 7.3.1.5       | Error Handling .....                              | 43 |
+| 7.3.1.6       | Feature negotiation .....                         | 43 |
+| 7.4           | Network resource management APIs.....             | 44 |
+| 7.4.1         | SS_Network_Resource_Adaptation API.....           | 44 |
+| 7.4.1.1       | API URI .....                                     | 44 |
+| 7.4.1.2       | Resources .....                                   | 44 |
+| 7.4.1.2.1     | Overview .....                                    | 44 |
+| 7.4.1.2.2     | Resource: Multicast Subscriptions .....           | 45 |
+| 7.4.1.2.2.1   | Description .....                                 | 45 |
+| 7.4.1.2.2.2   | Resource Definition.....                          | 45 |
+| 7.4.1.2.2.3   | Resource Standard Methods .....                   | 45 |
+| 7.4.1.2.2.3.1 | POST.....                                         | 45 |
+| 7.4.1.2.2.4   | Resource Custom Operations .....                  | 46 |
+| 7.4.1.2.3     | Resource: Individual Multicast Subscription ..... | 46 |
+| 7.4.1.2.3.1   | Description .....                                 | 46 |
+| 7.4.1.2.3.2   | Resource Definition.....                          | 46 |
+| 7.4.1.2.3.3   | Resource Standard Methods .....                   | 46 |
+| 7.4.1.2.3.3.1 | GET.....                                          | 46 |
+| 7.4.1.2.3.3.2 | DELETE .....                                      | 47 |
+| 7.4.1.2.3.4   | Resource Custom Operations .....                  | 47 |
+| 7.4.1.2.4     | Resource: Unicast Subscriptions.....              | 47 |
+| 7.4.1.2.4.1   | Description .....                                 | 47 |
+| 7.4.1.2.4.2   | Resource Definition.....                          | 47 |
+| 7.4.1.2.4.3   | Resource Standard Methods .....                   | 48 |
+| 7.4.1.2.4.3.1 | POST.....                                         | 48 |
+| 7.4.1.2.4.4   | Resource Custom Operations .....                  | 48 |
+| 7.4.1.2.5     | Resource: Individual Unicast Subscription .....   | 48 |
+| 7.4.1.2.5.1   | Description .....                                 | 48 |
+| 7.4.1.2.5.2   | Resource Definition.....                          | 48 |
+| 7.4.1.2.5.3   | Resource Standard Methods .....                   | 49 |
+| 7.4.1.2.5.3.1 | GET.....                                          | 49 |
+| 7.4.1.2.5.3.2 | DELETE .....                                      | 49 |
+
+|               |                                                     |    |
+|---------------|-----------------------------------------------------|----|
+| 7.4.1.2.5.4   | Resource Custom Operations .....                    | 49 |
+| 7.4.1.3       | Notifications.....                                  | 50 |
+| 7.4.1.3.1     | General .....                                       | 50 |
+| 7.4.1.3.2     | Notify_UP_Delivery_Mode .....                       | 50 |
+| 7.4.1.3.2.1   | Description .....                                   | 50 |
+| 7.4.1.3.2.2   | Notification definition .....                       | 50 |
+| 7.4.1.4       | Data Model .....                                    | 50 |
+| 7.4.1.4.1     | General .....                                       | 50 |
+| 7.4.1.4.2     | Structured data types .....                         | 52 |
+| 7.4.1.4.2.1   | Introduction .....                                  | 52 |
+| 7.4.1.4.2.2   | Type: MulticastSubscription .....                   | 52 |
+| 7.4.1.4.2.3   | Type: UnicastSubscription .....                     | 53 |
+| 7.4.1.4.2.4   | Type: UserPlaneNotification.....                    | 53 |
+| 7.4.1.4.2.5   | Type: NrmEventNotification.....                     | 53 |
+| 7.4.1.4.3     | Simple data types and enumerations .....            | 54 |
+| 7.4.1.4.3.1   | Enumeration: ServiceAnnouncementMode.....           | 54 |
+| 7.4.1.4.3.2   | Enumeration: DeliveryMode .....                     | 54 |
+| 7.4.1.4.3.3   | Enumeration: NrmEvent.....                          | 54 |
+| 7.4.1.5       | Error Handling .....                                | 54 |
+| 7.4.1.6       | Feature negotiation .....                           | 54 |
+| 7.5           | Event APIs.....                                     | 54 |
+| 7.5.1         | SS_Events API .....                                 | 54 |
+| 7.5.1.1       | API URI .....                                       | 54 |
+| 7.5.1.2       | Resources.....                                      | 55 |
+| 7.5.1.2.1     | Overview .....                                      | 55 |
+| 7.5.1.2.2     | Resource: SEAL Events Subscriptions .....           | 55 |
+| 7.5.1.2.2.1   | Description .....                                   | 55 |
+| 7.5.1.2.2.2   | Resource Definition.....                            | 55 |
+| 7.5.1.2.2.3   | Resource Standard Methods .....                     | 55 |
+| 7.5.1.2.2.3.1 | POST.....                                           | 55 |
+| 7.5.1.2.2.4   | Resource Custom Operations .....                    | 56 |
+| 7.5.1.2.3     | Resource: Individual SEAL Events Subscription ..... | 56 |
+| 7.5.1.2.3.1   | Description .....                                   | 56 |
+| 7.5.1.2.3.2   | Resource Definition.....                            | 56 |
+| 7.5.1.2.3.3   | Resource Standard Methods .....                     | 57 |
+| 7.5.1.2.3.3.1 | DELETE .....                                        | 57 |
+| 7.5.1.2.3.4   | Resource Custom Operations .....                    | 57 |
+| 7.5.1.3       | Notifications.....                                  | 57 |
+| 7.5.1.3.1     | General .....                                       | 57 |
+| 7.5.1.3.2     | SEAL Event Notification .....                       | 57 |
+| 7.5.1.3.2.1   | Description .....                                   | 57 |
+| 7.5.1.3.2.2   | Notification definition .....                       | 58 |
+| 7.5.1.4       | Data Model .....                                    | 58 |
+| 7.5.1.4.1     | General .....                                       | 58 |
+| 7.5.1.4.2     | Structured data types .....                         | 60 |
+| 7.5.1.4.2.1   | Introduction .....                                  | 60 |
+| 7.5.1.4.2.2   | SEALEventSubscription.....                          | 60 |
+| 7.5.1.4.2.3   | SEALEventNotification .....                         | 60 |
+| 7.5.1.4.2.4   | EventSubscription.....                              | 61 |
+| 7.5.1.4.2.5   | SEALEventDetail .....                               | 61 |
+| 7.5.1.4.2.6   | VALGroupFilter .....                                | 61 |
+| 7.5.1.4.2.7   | IdentityFilter .....                                | 62 |
+| 7.5.1.4.2.8   | LMInformation .....                                 | 62 |
+| 7.5.1.4.3     | Simple data types and enumerations .....            | 62 |
+| 7.5.1.4.3.1   | Introduction .....                                  | 62 |
+| 7.5.1.4.3.2   | Simple data types.....                              | 62 |
+| 7.5.1.4.3.3   | Enumeration: SEALEvent .....                        | 62 |
+| 7.5.1.5       | Error Handling .....                                | 62 |
+| 7.5.1.6       | Feature Negotiation.....                            | 63 |
+| 7.6           | Key management APIs.....                            | 63 |
+| 7.6.1         | SS_KeyInfoRetrieval API .....                       | 63 |
+| 7.6.1.1       | API URI .....                                       | 63 |
+
+|                             |                                          |           |
+|-----------------------------|------------------------------------------|-----------|
+| 7.6.1.2                     | Resources .....                          | 63        |
+| 7.6.1.2.1                   | Overview .....                           | 63        |
+| 7.6.1.2.2                   | Resource: Key Records .....              | 64        |
+| 7.6.1.2.2.1                 | Description .....                        | 64        |
+| 7.6.1.2.2.2                 | Resource Definition .....                | 64        |
+| 7.6.1.2.2.3                 | Resource Standard Methods .....          | 64        |
+| 7.6.1.2.2.3.1               | GET .....                                | 64        |
+| 7.6.1.2.2.4                 | Resource Custom Operations .....         | 65        |
+| 7.6.1.3                     | Notifications .....                      | 65        |
+| 7.6.1.4                     | Data Model .....                         | 65        |
+| 7.6.1.4.1                   | General .....                            | 65        |
+| 7.6.1.4.2                   | Structured Data Types .....              | 66        |
+| 7.6.1.4.2.1                 | Introduction .....                       | 66        |
+| 7.6.1.4.2.2                 | ValKeyInfo .....                         | 66        |
+| 7.6.1.4.3                   | Simple data types and enumerations ..... | 66        |
+| 7.6.1.5                     | Error Handling .....                     | 66        |
+| 7.6.1.6                     | Feature Negotiation .....                | 66        |
+| 8                           | Using Common API Framework .....         | 66        |
+| 8.1                         | General .....                            | 66        |
+| 8.2                         | Security .....                           | 67        |
+| 9                           | Security .....                           | 67        |
+| 9.1                         | General .....                            | 67        |
+| 9.2                         | SEAL-S security .....                    | 67        |
+| <b>Annex A (normative):</b> | <b>OpenAPI specification .....</b>       | <b>68</b> |
+| A.1                         | General .....                            | 68        |
+| A.2                         | SS_LocationReporting API .....           | 68        |
+| A.3                         | SS_GroupManagement API .....             | 71        |
+| A.4                         | SS_UserProfileRetrieval API .....        | 74        |
+| A.5                         | SS_NetworkResourceAdaptation API .....   | 76        |
+| A.6                         | SS_Events API .....                      | 82        |
+| A.7                         | SS_KeyInfoRetrieval API .....            | 86        |
+| Annex B (informative):      | Change history .....                     | 88        |
+
+## Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present specification describes the APIs for the Service Enabler Architecture Layer for Verticals (SEAL). The SEAL and related stage 2 architecture, functional requirements and information flows are specified in 3GPP TS 23.434 [2].
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
+- [3] 3GPP TS 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
+- [4] IETF RFC 6455: "The Websocket Protocol".
+- [5] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
+- [6] IETF RFC 7231: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content".
+- [7] IETF RFC 7232: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests".
+- [8] IETF RFC 7233: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests".
+- [9] IETF RFC 7234: "Hypertext Transfer Protocol (HTTP/1.1): Caching".
+- [10] IETF RFC 7235: "Hypertext Transfer Protocol (HTTP/1.1): Authentication".
+- [11] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".
+- [12] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)".
+- [13] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format".
+- [14] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
+- [15] Open API Initiative, "OpenAPI 3.0.0 Specification", <https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md>.
+- [16] 3GPP TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
+- [17] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
+- [18] 3GPP TS 33.122: "Security Aspects of Common API Framework for 3GPP Northbound APIs".
+- [19] IETF RFC 6749: "The OAuth 2.0 Authorization Framework".
+- [20] 3GPP TS 29.523: "5G System; Policy Control Event Exposure Service; Stage 3".
+- [21] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
+
+- [22] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
+- [23] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3".
+- [24] 3GPP TR 21.900: "Technical Specification Group working methods".
+- [25] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
+- [26] 3GPP TS 33.434: "Service Enabler Architecture Layer for Verticals (SEAL); Security Aspects".
+
+---
+
+## 3 Definitions of terms and abbreviations
+
+### 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**VAL service:** A generic name for any service offered by the VAL service provider to their VAL users.
+
+**SEAL service:** A generic name for a common service (e.g. group management, configuration management, location management) that can be utilized by multiple vertical applications.
+
+**SEAL provider:** Provider of SEAL service(s).
+
+**VAL server:** A generic name for the server application function of a specific VAL service.
+
+**SEAL server:** An entity that provides the server side functionalities corresponding to the specific SEAL service.
+
+**VAL system:** The collection of applications, services, and enabling capabilities required to support a VAL service.
+
+**VAL group:** A defined set of VAL UEs or VAL users configured for specific purpose in a VAL service.
+
+NOTE: The set could be of either VAL UEs or VAL users depending on the specific VAL service.
+
+**VAL group home system:** The VAL system where the VAL group is defined.
+
+**VAL group member:** A VAL service user, whose VAL user ID is listed in a particular VAL group.
+
+**Vertical application:** An application catering to a specific vertical.
+
+### 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                                  |
+|--------|--------------------------------------------------|
+| 5GS    | 5G System                                        |
+| AEF    | API Exposing Function                            |
+| API    | Application Programming Interface                |
+| JSON   | JavaScript Object Notation                       |
+| NDS    | Network Domain Security                          |
+| NDS/IP | NDS for IP based protocols                       |
+| PLMN   | Public Land Mobile Network                       |
+| REST   | Representational State Transfer                  |
+| SCEF   | Service Capability Exposure Function             |
+| SCS    | Service Capability Server                        |
+| SEAL   | Service Enabler Architecture Layer for Verticals |
+| TMGI   | Temporary Mobile Group Identity                  |
+| UE     | User Equipment                                   |
+| VAL    | Vertical Application Layer                       |
+
+---
+
+## 4 Overview
+
+3GPP has considered in 3GPP TS 23.434 [2] the development of Service enabler architecture layer for verticals (SEAL) over 3GPP networks to support vertical applications (e.g. V2X applications). It specifies the functional architecture for SEAL and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP systems. To ensure efficient use and deployment of vertical applications over 3GPP systems, SEAL services includes, group management, configuration management, location management, identity management, key management and network resource management.
+
+3GPP TS 23.434 [2], clause 6 specifies the functional entities and domains of the functional model, reference points descriptions and SEAL APIs for SEAL services.
+
+The present document specifies the APIs needed to support SEAL.
+
+---
+
+## 5 Services offered by the SEAL servers
+
+### 5.1 Introduction of SEAL services
+
+The table 5.1-1 lists the SEAL server APIs below the service name. A service description clause for each API gives a general description of the related API.
+
+Table 5.1-1: List of SEAL Service APIs
+
+| Service Name                                                                                                                                                       | Service Operations                | Operation Semantics | Consumer(s) |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|---------------------|-------------|
+| SS_LocationReporting                                                                                                                                               | Create_Trigger_Location_Reporting | Request/ Response   | VAL server  |
+|                                                                                                                                                                    | Fetch_Location_Report_Trigger     | Request/Response    | VAL server  |
+|                                                                                                                                                                    | Update_Trigger_Location_Reporting | Request/ Response   | VAL server  |
+|                                                                                                                                                                    | Cancel_Trigger_Location_Reporting | Request/ Response   | VAL server  |
+| SS_LocationInfoEvent                                                                                                                                               | Subscribe_Location_Info           | Subscribe/Notify    | VAL server  |
+|                                                                                                                                                                    | Notify_Location_Info              |                     | VAL server  |
+| SS_LocationInfoRetrieval                                                                                                                                           | Obtain_Location_Info              | Request/ Response   | VAL server  |
+| SS_GroupManagement                                                                                                                                                 | Query_Group_Info                  | Request/ Response   | VAL server  |
+|                                                                                                                                                                    | Update_Group_Info                 | Request/ Response   | VAL server  |
+|                                                                                                                                                                    | Create_Group                      | Request/ Response   | VAL server  |
+|                                                                                                                                                                    | Delete_Group                      | Request/Response    | VAL server  |
+| SS_GroupManagementEvent                                                                                                                                            | Subscribe_Group_Info_Modification | Subscribe/Notify    | VAL server  |
+|                                                                                                                                                                    | Notify_Group_Info_Modification    |                     | VAL server  |
+|                                                                                                                                                                    | Notify_Group_Creation             |                     | VAL server  |
+| SS_UserProfileRetrieval                                                                                                                                            | Obtain_User_Profile               | Request/ Response   | VAL server  |
+| SS_UserProfileEvent                                                                                                                                                | Subscribe_User_Profile_Update     | Subscribe/Notify    | VAL server  |
+|                                                                                                                                                                    | Notify_User_Profile_Update        |                     | VAL server  |
+| SS_NetworkResourceAdaptation                                                                                                                                       | Reserve_Network_Resource          | Request/Response    | VAL server  |
+|                                                                                                                                                                    | Request_Unicast_Resource          | Request/Response    | VAL server  |
+|                                                                                                                                                                    | Update_Unicast_Resource           | Request/Response    | VAL server  |
+|                                                                                                                                                                    | Request_Multicast_Resource        | Request/Response    | VAL server  |
+|                                                                                                                                                                    | Notify_UP_Delivery_Mode           | Subscribe/Notify    | VAL server  |
+| SS_Events                                                                                                                                                          | Subscribe_Event                   | Subscribe/Notify    | VAL server  |
+|                                                                                                                                                                    | Notify_Event                      |                     | VAL server  |
+|                                                                                                                                                                    | Unsubscribe_Event                 |                     | VAL server  |
+| SS_KeyInfoRetrieval                                                                                                                                                | Obtain_Key_Info                   | Request/Response    | VAL server  |
+| NOTE: The service operations of SS_Events API are reused by the SS_LocationInfoEvent, SS_GroupManagementEvent and SS_UserProfileEvent for events related services. |                                   |                     |             |
+
+Table 5.1-2 summarizes the corresponding APIs defined in this specification.
+
+Table 5.1-2: API Descriptions
+
+| Service Name | Clause | Description | OpenAPI Specification File | apiName | Annex |
+|--------------|--------|-------------|----------------------------|---------|-------|
+|--------------|--------|-------------|----------------------------|---------|-------|
+
+|                                |     |                                      |                                           |           |     |
+|--------------------------------|-----|--------------------------------------|-------------------------------------------|-----------|-----|
+| SS_LocationReporting           | 7.1 | Report Location Information Service. | TS29549_SS_LocationReporting.yaml         | ss-lr     | A.2 |
+| SS_GroupManagement             | 7.2 | Group Management Service             | TS29549_SS_GroupManagement.yaml           | ss-gm     | A.3 |
+| SS_UserProfileRetrieval        | 7.3 | User Profile Retrieval Service       | TS29549_SS_UserProfileRetrieval.yaml      | ss-upr    | A.4 |
+| SS_Network_Resource_Adaptation | 7.4 | Network Resource Adaptation Service  | TS29549_SS_NetworkResourceAdaptation.yaml | ss-nra    | A.5 |
+| SS_Events                      | 7.5 | Events Notify Service                | TS29549_SS_Events.yaml                    | ss-events | A.6 |
+| SS_KeyInfoRetrieval            | 7.6 | Key Information Retrieval Service    | TS29549_SS_KeyInfoRetrieval.yaml          | ss-kir    | A.7 |
+
+## 5.2 Location management APIs
+
+### 5.2.1 SS\_LocationReporting API
+
+#### 5.2.1.1 Service Description
+
+##### 5.2.1.1.1 Overview
+
+The SS\_LocationReporting API, as defined 3GPP TS 23.434 [2], allows VAL server via LM-S reference point to configure reporting trigger of location information to the location management server.
+
+#### 5.2.1.2 Service Operations
+
+##### 5.2.1.2.1 Introduction
+
+The service operation defined for SS\_LocationReporting API is shown in the table 5.2.1.2.1-1.
+
+**Table 5.2.1.2.1-1: Operations of the SS\_LocationReporting API**
+
+| Service operation name            | Description                                                                                          | Initiated by |
+|-----------------------------------|------------------------------------------------------------------------------------------------------|--------------|
+| Create_Trigger_Location_Reporting | This service operation is used by VAL server to create the trigger to report location information.   | VAL server   |
+| Fetch_Location_Report_Trigger     | This service operation is used by VAL server to retrieve the location reporting trigger information. | VAL server   |
+| Update_Trigger_Location_Reporting | This service operation is used by VAL server to update the trigger to report location information.   | VAL server   |
+| Cancel_Trigger_Location_Reporting | This service operation is used by VAL server to cancel the trigger to report location information.   | VAL server   |
+
+##### 5.2.1.2.2 Create\_Trigger\_Location\_Reporting
+
+###### 5.2.1.2.2.1 General
+
+This service operation is used by a VAL server to create the trigger to report location information.
+
+###### 5.2.1.2.2.2 VAL server providing trigger configuration using Create\_Trigger\_Location\_Reporting service operation
+
+To create the reporting trigger configuration, the VAL server shall send HTTP POST request message to location management server. The body of the HTTP POST message shall include the LocationReportConfiguration data type, as specified in the clause 7.1.1.2.2.3.1.
+
+Upon receiving the HTTP POST message as described above, the location management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to provide the trigger;
+2. if the VAL server is authorized to provide the triggers, the location management server shall;
+
+- a. create a new resource for Individual SEAL Location Reporting Configuration as specified in clause 7.1.1.2.1; and
+- b. return the SEAL Resource URI in the response message.
+
+#### 5.2.1.2.3 Fetch\_Location\_Report\_Trigger
+
+##### 5.2.1.2.3.1 General
+
+This service operation is used by VAL server to retrieve an individual location reporting configuration information.
+
+##### 5.2.1.2.3.2 VAL server fetching trigger configuration using Fetch\_Location\_Report\_Trigger service operation
+
+To fetch the location report trigger configuration, the VAL server shall send HTTP GET request message to location management server on the resource URI representing the individual SEAL location reporting configuration, as specified in 7.1.1.2.3.3.1.
+
+Upon receiving the HTTP GET message as described above, the location management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to fetch the trigger information;
+2. if the VAL server is authorized to fetch the trigger information, the location management server shall;
+  - a. return the location report trigger configuration in LocationReportConfiguration data type, as specified in clause 7.1.1.2.1.
+
+#### 5.2.1.2.4 Update\_Trigger\_Location\_Reporting
+
+##### 5.2.1.2.4.1 General
+
+This service operation is used by a VAL server to update the trigger to report location information.
+
+##### 5.2.1.2.4.2 VAL server providing trigger configuration using Update\_Trigger\_Location\_Reporting service operation
+
+To modify the reporting trigger configuration, the VAL server shall send HTTP PUT message to the location management server to the Resource URI identifying the individual SEAL location reporting configuration resource representation, as specified in the clause 7.1.1.2.3.3.2. Upon receiving the HTTP PUT message, the location management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to modify the configuration information;
+2. if the VAL server is authorized to modify the information, then the location management server shall;
+  - a. if the configuration information in the request is valid, update the resource identified by the Resource URI of the configuration received in the request;
+  - b. return the updated location reporting configuration information in the response
+
+#### 5.2.1.2.5 Cancel\_Trigger\_Location\_Reporting
+
+##### 5.2.1.2.5.1 General
+
+This service operation is used by a VAL server to cancel the trigger to report location information.
+
+##### 5.2.1.2.5.2 VAL server providing trigger configuration using Cancel\_Trigger\_Location\_Reporting service operation
+
+To delete the reporting trigger configuration, the VAL server shall send an HTTP DELETE message to the resource representing Individual SEAL Location Reporting Configuration as specified in clause 7.1.1.2.3.3.3.
+
+Upon receiving the HTTP DELETE message, the location management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to delete the configuration information; and
+
+2. if the VAL server is authorized to delete the configuration information, the location management server shall delete the resource pointed by the Resource URI for Individual SEAL Location Reporting Configuration.
+
+## 5.2.2 SS\_LocationInfoEvent API
+
+The SS\_LocationInfoEvent API, as defined 3GPP TS 23.434 [2], allows a VAL server via LM-S reference point to subscribe for and receive notifications of location information from the location management server. The SS\_LocationInfoEvent API supports this via the event "LM\_LOCATION\_INFO\_CHANGE" of the SS\_Events API as specified in clause 7.5.
+
+## 5.2.3 SS\_LocationInfoRetrieval API
+
+The SS\_LocationInfoRetrieval API, as defined 3GPP TS 23.434 [2], enables the VAL server via LM-S reference point to obtain location information from the location management server. The SS\_LocationInfoRetrieval API supports this via the event "LM\_LOCATION\_INFO\_CHANGE" of the SS\_Events API by setting the "immRep" attribute to true and setting the "notifMethod" attribute to "ONE\_TIME" within the "eventReq" attribute, as specified in clause 7.5.
+
+Upon receipt of the immediate reporting indication in the "immRep" attribute within the "eventReq" attribute sets to true in the HTTP POST request, the location management server shall ignore the "notificationDestination" attribute within the SEALEventSubscription data type and include the event details in the "eventDetails" attribute, if available, in the HTTP POST response.
+
+# 5.3 Group management APIs
+
+## 5.3.1 SS\_GroupManagement API
+
+### 5.3.1.1 Service Description
+
+#### 5.3.1.1.1 Overview
+
+The SS\_GroupManagement API, as defined 3GPP TS 23.434 [2], allows VAL server via GM-S reference point to create, fetch, update and delete VAL group membership and configuration information.
+
+### 5.3.1.2 Service Operations
+
+#### 5.3.1.2.1 Introduction
+
+The service operation defined for SS\_GroupManagement API is shown in the table 5.3.1.2.1-1.
+
+**Table 5.3.1.2.1-1: Operations of the SS\_GroupManagement API**
+
+| Service operation name | Description                                                                                                                         | Initiated by |
+|------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------|
+| Query_Group_Info       | This service operation is used by VAL server to query for VAL group documents, group membership list and configuration information. | VAL Server   |
+| Update_Group_Info      | This service operation is used by VAL server to modify group membership and configuration information.                              | VAL server   |
+| Create_Group           | This service operation is used by VAL server to configure new VAL group.                                                            | VAL server   |
+| Delete_Group           | This service operation is used by the VAL server to delete the VAL group.                                                           | VAL server   |
+
+### 5.3.1.2.2 Query\_Group\_Info
+
+#### 5.3.1.2.2.1 General
+
+This service operation is used by a VAL server to obtain VAL group documents, group membership and configuration information.
+
+#### 5.3.1.2.2.2 VAL server fetching VAL group documents, group membership and configuration information using Query\_Group\_Info service operation
+
+To obtain membership, configuration information of a VAL group, the VAL server shall send a HTTP GET message to the group management server, on VAL group document's resource representation URI as specified in clause 7.2.1.2.3.3.1. The GET message may include the following query parameters: membership list, group configuration. To obtain VAL groups information, the VAL server shall send a HTTP GET message to the group management server, on VAL group documents collection resource representation URI as specified in clause 7.2.1.2.2.3.2. The GET message may include the following query parameters: VAL Group ID, VAL Service ID.
+
+Upon receiving the HTTP GET message as described above, the group management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to fetch the VAL group information;
+2. if the VAL server is authorized to obtain the group information, the group management server shall;
+  - a. if the request to VAL group document's resource representation URI includes query parameters, then, return in the response message with VAL group information which includes, group membership list information if the request includes membership list query, group configuration information if the request includes group configuration query and VAL group identifier;
+  - b. if the request to VAL group document's resource representation URI does not include query parameter, then, return the VAL group document resource in the response message;
+  - c. in the request to VAL group documents collection resource representation URI, return the VAL group documents matching the query parameters in the response message.
+
+### 5.3.1.2.3 Update\_Group\_Info
+
+#### 5.3.1.2.3.1 General
+
+This service operation is used by a VAL server to modify group membership and configuration information.
+
+#### 5.3.1.2.3.2 VAL server modifying group membership and configuration using Update\_Group\_Info service operation
+
+To modify group information of a VAL group, the VAL server shall send HTTP PUT message to the group management server to the Resource URI identifying the VAL group document resource representation, as specified in the clause 7.2.1.2.3.3.2. This request shall not replace valGroupId property in the existing resource. Upon receiving the HTTP PUT message, the group management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to modify VAL group information;
+2. verify that valGroupId in the request is same as valGroupId of the VAL group document resource;
+3. if the VAL server is authorized to modify the group information and the valGroupId matches, then the group management server shall;
+  - a. if the group configuration information in the request is valid, update the resource identified by the Resource URI of the group document with group members list and group configuration information received in the request;
+  - b. return the updated VAL group document in the response
+
+#### 5.3.1.2.4 Create\_Group
+
+##### 5.3.1.2.4.1 General
+
+This service operation is used by a VAL server to create VAL group.
+
+##### 5.3.1.2.4.2 VAL server creating new group using Create\_Group service operation
+
+To create a VAL group, the VAL server shall send a HTTP POST message to the group management server. The body of the POST message shall include VAL group document information as specified in clause 7.2.1.2.2.3.1. Upon receiving HTTP POST message, the group management server shall
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to create VAL group document;
+2. if the VAL group document information in the request includes location criteria, shall obtain the list of VAL users or VAL UEs within the requested location criteria information from the Location Management server and include them in VAL group members of the new VAL group;
+3. if the VAL server is authorized to create VAL group document, shall create a new resource as defined in 7.2.1.2.2.3.1 and return the VAL group document and its Resource URI in the response message.
+
+#### 5.3.1.2.5 Delete\_Group
+
+##### 5.3.1.2.5.1 General
+
+This service operation is used by a VAL server to delete a VAL group.
+
+##### 5.3.1.2.5.2 VAL server deleting VAL group using Delete\_Group service operation
+
+To delete a VAL group, the VAL server shall send a HTTP DELETE message to the Group Management server to its resource representation in the Group Management server as specified in clause 7.2.1.2.3.3.3. Upon receiving HTTP DELETE message, the Group Management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to delete the VAL group document;
+2. if the VAL server is authorized to delete the VAL group document, the Group Management server shall
+  - a. delete the resource representation pointed by the group document resource identifier.
+
+### 5.3.2 SS\_GroupManagementEvent API
+
+The SS\_GroupManagementEvent API, as defined 3GPP TS 23.434 [2], allows a VAL server via GM-S reference point to subscribe for and receive notifications from Group Management server on new VAL group creations and on modifications to VAL Group membership and configuration information. The SS\_GroupManagementEvent API supports this via the "GM\_GROUP\_CREATE" and "GM\_GROUP\_INFO\_CHANGE" events of SS\_Events API as specified in clause 7.5. In order to authorize the VAL servers that have to be notified of a GM\_GROUP\_CREATE event, the Group Management server shall identify the VAL services (VAL Service IDs) allowed for the VAL server by the "subscriberId" attribute and shall notify the VAL server if the VAL services enabled for the created VAL group are allowed for the VAL server.
+
+Upon the receipt of the VAL group document from the group management server during Create\_Group service operation, if the VAL server is interested in receiving the notifications about newly registered or de-registered VAL UE IDs to the VAL group, then the VAL server may subscribe to "GM\_GROUP\_INFO\_CHANGE" event using the SS\_Events API as specified in clause 7.5.1, to receive any VAL group membership update notifications.
+
+## 5.4 Configuration management APIs
+
+### 5.4.1 SS\_UserProfileRetrieval API
+
+#### 5.4.1.1 Service Description
+
+##### 5.4.1.1.1 Overview
+
+The SS\_UserProfileRetrieval API, as defined in 3GPP TS 23.434 [2], allows VAL server via CM-S reference point to obtain user profile from the configuration management server.
+
+#### 5.4.1.2 Service Operations
+
+##### 5.4.1.2.1 Introduction
+
+The service operation defined for SS\_UserProfileRetrieval API is shown in the table 5.4.1.2.1-1.
+
+**Table 5.4.1.2.1-1: Operations of the SS\_UserProfileRetrieval API**
+
+| Service operation name | Description                                                          | Initiated by |
+|------------------------|----------------------------------------------------------------------|--------------|
+| Obtain_User_Profile    | This service operation is used by VAL server to obtain user profile. | VAL server   |
+
+##### 5.4.1.2.2 Obtain\_User\_Profile
+
+###### 5.4.1.2.2.1 General
+
+This service operation is used by a VAL server to obtain VAL user profile information.
+
+###### 5.4.1.2.2.2 VAL server retrieving VAL user profile information using Obtain\_User\_Profile service operation
+
+To obtain a VAL user's profile, the VAL server shall send HTTP GET request message to configuration management server, on VAL service's resource representation URI, with query parameters VAL user ID or VAL UE ID and optionally VAL service ID, as specified in 7.3.1.2.2.3.1.
+
+Upon receiving the HTTP GET message as described above, the configuration management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to fetch the VAL user profile information;
+2. if the VAL server is authorized to obtain the requested VAL user profile information, the configuration management server shall;
+  - a. return in the response message with profile information corresponding to the query parameters that was sent in the request message.
+
+### 5.4.2 SS\_UserProfileEvent API
+
+The SS\_UserProfileEvent API, as defined in 3GPP TS 23.434 [2], allows a VAL server via CM-S reference point to subscribe for and receive notifications from the Configuration Management server on profile updates to VAL User or VAL UE. The SS\_UserProfileEvent API supports this via the "CM\_USER\_PROFILE\_CHANGE" event in SS\_Events API as specified in clause 7.5.
+
+## 5.5 Network resource management APIs
+
+### 5.5.1 SS\_Network\_Resource\_Adaptation API
+
+#### 5.5.1.1 Service Description
+
+##### 5.5.1.1.1 Overview
+
+The SS\_NetworkResourceAdaptation API, as defined 3GPP TS 23.434 [2], allows VAL server via NRM-S reference point to communicate with the network resource management server for network resource adaptation including reserving network resource, requesting and subscribing for unicast and multicast resources.
+
+#### 5.5.1.2 Service Operations
+
+##### 5.5.1.2.1 Introduction
+
+The service operation defined for SS\_NetworkResourceAdaptation API is shown in the table 5.5.1.2.1-1.
+
+**Table 5.5.1.2.1-1: Operations of the SS\_NetworkResourceAdaptation API**
+
+| Service operation name     | Description                                | Initiated by |
+|----------------------------|--------------------------------------------|--------------|
+| Reserve_Network_Resource   | Requesting for network resource adaptation | VAL server   |
+| Request_Unicast_Resource   | Requesting unicast resource                | VAL server   |
+| Update_Unicast_Resource    | Updating unicast resource                  | VAL server   |
+| Request_Multicast_Resource | Requesting multicast resource              | VAL server   |
+| Notify_UP_Delivery_Mode    | Notifying the user plane delivery mode     | NRM server   |
+
+##### 5.5.1.2.2 Reserve\_Network\_Resource
+
+###### 5.5.1.2.2.1 General
+
+This service operation is used by a VAL server to request for network resource adaptation.
+
+###### 5.5.1.2.2.2 VAL server requesting for network resource adaptation using Reserve\_Network\_Resource service operation
+
+The VAL server shall send a HTTP POST message to the NRM server. The body of the POST message shall include VAL UE(s) or VAL group information and the VAL service QoS requirement. Upon receiving HTTP POST message, the NRM server shall
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to request for network resource adaptation;
+2. if the VAL server is authorized, the NRM server shall determine the QoS requirements for each VAL UE based on the VAL UE(s) or VAL group information;
+3. for each VAL UE, the NRM server initiates the PCC procedures; and
+4. the NRM server provides result and optionally includes the accepted value for the QoS requirements based on the outcome of the PCC procedure in the response message
+
+##### 5.5.1.2.3 Request\_Unicast\_Resource
+
+###### 5.5.1.2.3.1 General
+
+This service operation is used by a VAL server to request for unicast resource.
+
+#### 5.5.1.2.3.2 VAL server requesting for unicast resource using Request\_Unicast\_Resource service operation
+
+The VAL server shall send a HTTP POST message to the NRM server. The body of the POST message shall include VAL user or UE information and the VAL service requirement. Upon receiving HTTP POST message, the NRM server shall
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to request for unicast resource;
+2. if the VAL server is authorized, the NRM server evaluates the need for network resources and use of resource sharing;
+3. for the VAL user or UE, the NRM server initiates interaction via SIP core;
+4. the NRM server creates a unicast subscription as specified in clause 7.4.1.2.4.3.1; and
+5. the NRM server provides result in the response message.
+
+#### 5.5.1.2.4 Update\_Unicast\_Resource
+
+##### 5.5.1.2.4.1 General
+
+Void.
+
+#### 5.5.1.2.4.2 VAL server requesting for updating the unicast resource using Update\_Unicast\_Resource service operation
+
+Void.
+
+#### 5.5.1.2.5 Request\_Multicast\_Resource
+
+##### 5.5.1.2.5.1 General
+
+This service operation is used by a VAL server to request for multicast resource.
+
+#### 5.5.1.2.5.2 VAL server requesting for multicast resource using Request\_Multicast\_Resource service operation
+
+The VAL server shall send a HTTP POST message to the NRM server. The body of the POST message shall include VAL group information, service announcement mode, QoS information, Broadcast area and VAL server notification endpoint address information. Upon receiving HTTP POST message, the NRM server shall
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to request for multicast resource;
+2. if the VAL server is authorized, the NRM server decides to establish an MBMS bearer in EPS using the procedures defined in 3GPP TS 29.468 [23];
+3. the NRM server creates a multicast subscription as specified in clause 7.4.1.2.2.3.1;
+4. the NRM server provides the result in the response message.
+
+#### 5.5.1.2.6 Notify\_UP\_Delivery\_Mode
+
+##### 5.5.1.2.6.1 General
+
+This service operation is used by the NRM server to send user plane notifications to the VAL server.
+
+#### 5.5.1.2.6.2 Notifying user plane events using Notify\_UP\_Delivery\_Mode service operation
+
+To notify the user plane events, the NRM server shall send an HTTP POST message using the Notification Destination URI received in the multicast resource request. The body of the HTTP POST message shall include an UserPlaneNotification as specified in clause 7.4.1.3.2.
+
+Upon receiving the HTTP POST message, the VAL server shall process the Event Notification.
+
+## 5.6 Events APIs
+
+### 5.6.1 SS\_Events API
+
+#### 5.6.1.1 Service Description
+
+##### 5.6.1.1.1 Overview
+
+The SS\_Events API, allows a VAL server via LM-S, GM-S, CM-S reference points to subscribe and unsubscribe from SEAL events and to receive notifications from the Location Management Server, Group Management Server and Configuration Management Server respectively.
+
+#### 5.6.1.2 Service Operations
+
+##### 5.6.1.2.1 Introduction
+
+The service operations defined for the SS\_Events API are shown in the table 5.6.1.2.1-1.
+
+**Table 5.6.1.2.1-1: Operations of the SS\_Events API**
+
+| Service operation name | Description                                                                                 | Initiated by                                                                    |
+|------------------------|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| Subscribe_Event        | This service operation is used by VAL server to subscribe for events from SEAL servers.     | VAL Server                                                                      |
+| Unsubscribe_Event      | This service operation is used by VAL server to unsubscribe for events from SEAL servers.   | VAL Server                                                                      |
+| Notify_Event           | This service operation is used by SEAL servers to send the notifications to the VAL server. | SEAL servers (Location Management, Group Management, Configuration Management). |
+
+##### 5.6.1.2.2 Subscribe\_Event
+
+###### 5.6.1.2.2.1 General
+
+This service operation is used by a VAL server to subscribe to the SEAL events.
+
+###### 5.6.1.2.2.2 Subscribing to SEAL events using Subscribe\_Event service operation
+
+To subscribe to SEAL events, the VAL server shall send an HTTP POST message to the SEAL server. The body of the HTTP POST message shall include VAL Server Identifier, Event Type, Event Filters, Reporting Requirements and a Notification Destination URI as specified in clause 7.5.1.2.2.3.1.
+
+Upon receiving the above described HTTP POST message, the SEAL server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to subscribe to the SEAL events mentioned in the HTTP POST message;
+2. if the VAL server is authorized to subscribe to the SEAL events, the SEAL server shall:
+  - a. create a new resource as specified in clause 7.5.1.2.1; and
+  - b. return the SEAL Resource URI in the response message.
+
+##### 5.6.1.2.3 Notify\_Event
+
+###### 5.6.1.2.3.1 General
+
+This service operation is used by the SEAL servers to send notifications to the VAL server.
+
+#### 5.6.1.2.3.2 Notifying SEAL events using Notify\_Event service operation
+
+To notify the SEAL events, the SEAL server shall send an HTTP POST message using the Notification Destination URI received in the subscription request. The body of the HTTP POST message shall include an Event Notification and SEAL Resource URI.
+
+Upon receiving the HTTP POST message, the VAL server shall process the Event Notification.
+
+#### 5.6.1.2.4 Unsubscribe\_Event
+
+##### 5.6.1.2.4.1 General
+
+This service operation is used by a VAL server to un-subscribe from the SEAL events.
+
+##### 5.6.1.2.4.2 Unsubscribing from SEAL events using Unsubscribe\_Event service operation
+
+To unsubscribe from SEAL events, the VAL server shall send an HTTP DELETE message to the resource representing the event in the SEAL server as specified in clause 7.5.1.2.3.3.1.
+
+Upon receiving the HTTP DELETE message, the SEAL sever shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to Unsubscribe from the SEAL event associated with the SEAL Resource URI; and
+2. if the VAL server is authorized to unsubscribe from the SEAL events, the SEAL server shall delete the resource pointed by the SEAL Resource URI
+
+## 5.7 Key management APIs
+
+### 5.7.1 SS\_KeyInfoRetrieval API
+
+#### 5.7.1.1 Service Description
+
+##### 5.7.1.1.1 Overview
+
+As specified in 3GPP TS 33.434 [26], the SS\_KeyInfoRetrieval API, allows the VAL server via KM-S reference point to obtain the VAL service specific key management information from the key management server.
+
+#### 5.7.1.2 Service Operations
+
+##### 5.7.1.2.1 Introduction
+
+The service operation defined for SS\_KeyInfoRetrieval API is shown in the table 5.7.1.2.1-1.
+
+**Table 5.7.1.2.1-1: Operations of the SS\_ KeyInfoRetrieval API**
+
+| Service operation name | Description                                                                        | Initiated by |
+|------------------------|------------------------------------------------------------------------------------|--------------|
+| Obtain_Key_Info        | This service operation is used by VAL server to obtain key management information. | VAL server   |
+
+##### 5.7.1.2.2 Obtain\_Key\_Info
+
+##### 5.7.1.2.2.1 General
+
+This service operation is used by the VAL server to obtain VAL service specific key management information.
+
+#### 5.7.1.2.2.2 VAL server obtaining VAL service specific key material using Obtain\_Key\_Info service operation
+
+To obtain key management information specific to VAL service, the VAL server shall send HTTP GET request message to key management server, on Key records resource collection URI, with query parameters VAL service ID and optionally VAL user ID or VAL UE ID, as specified in 7.6.1.2.2.3.1.
+
+Upon receiving the HTTP GET message as described above, the key management server shall:
+
+1. verify the identity of the VAL server and check if the VAL server is authorized to obtain key management information specific to VAL service, VAL user or VAL UE, the URI in the request is of target SEAL KMS and date/time of the request is in recent time window;
+2. if the VAL server is authorized to obtain the requested key management information, the key management server shall;
+  - a. return in the response message with key management information corresponding to the query parameters that were sent in the request message.
+
+## 6 SEAL Design Aspects Common for All APIs
+
+### 6.1 General
+
+SEAL APIs allow secure access to the capabilities provided by SEAL.
+
+This document specifies the procedures triggered at different functional entities as a result of API invocation requests and event notifications. The stage-2 level requirements and signalling flows are defined in 3GPP TS 23.434 [2].
+
+Several design aspects, as mentioned in the following clauses, are specified in 3GPP TS 29.122 [3] and referenced by this specification.
+
+### 6.2 Data Types
+
+#### 6.2.1 General
+
+This clause defines structured data types, simple data types and enumerations that are applicable to several APIs defined in the present specification and can be referenced from data structures defined in the subsequent clauses.
+
+In addition, data types that are defined in OpenAPI 3.0.0 Specification [15] can also be referenced from data structures defined in the subsequent clauses.
+
+NOTE: As a convention, data types names in the present specification are with an upper-case letter in the beginning. Parameters are with a lower-case letter in the beginning. As an exception, data types that are also defined in OpenAPI 3.0.0 Specification [15] can use a lower-case case letter in the beginning for consistency.
+
+Table 6.2.1-1 specifies data types re-used by the SEAL from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the SEAL.
+
+**Table 6.2.1-1: Re-used Data Types**
+
+| Data type          | Reference          | Comments                                                                                                 |
+|--------------------|--------------------|----------------------------------------------------------------------------------------------------------|
+| Uri                | 3GPP TS 29.122 [3] |                                                                                                          |
+| TestNotification   | 3GPP TS 29.122 [3] | Following clarifications apply:<br>- The SCEF is the SEAL server; and<br>- The SCS/AS is the VAL server. |
+| WebsockNotifConfig | 3GPP TS 29.122 [3] | Following clarifications apply:<br>- The SCEF is the SEAL server; and<br>- The SCS/AS is the VAL server. |
+
+## 6.2.2 Referenced structured data types
+
+Table 6.2.2-1 lists structured data types defined in this specification referenced by multiple services:
+
+**Table 6.2.2-1: Referenced Structured Data Types**
+
+| Data type        | Reference          | Description                             |
+|------------------|--------------------|-----------------------------------------|
+| VALGroupDocument | Clause 7.2.1.4.2.2 | VAL Group document information.         |
+| ProfileDoc       | Clause 7.3.1.4.2.2 | VAL User or VAL UE profile information. |
+
+## 6.2.3 Referenced Simple data types and enumerations
+
+Following simple data types defined in Table 6.2.3-1 are applicable to several APIs in this document:
+
+**Table 6.2.3-1: Simple data types applicable to several APIs**
+
+| Type name | Reference | Description |
+|-----------|-----------|-------------|
+|           |           |             |
+
+## 6.3 Usage of HTTP
+
+For SEAL APIs, support of HTTP/1.1 (IETF RFC 7230 [5], IETF RFC 7231 [6], IETF RFC 7232 [7], IETF RFC 7233 [8], IETF RFC 7234 [9] and IETF RFC 7235 [10]) over TLS (IETF RFC 5246 [11]) is mandatory and support of HTTP/2 (IETF RFC 7540 [12]) over TLS (IETF RFC 5246 [11]) is recommended.
+
+A functional entity desiring to use HTTP/2 shall use the HTTP upgrade mechanism to negotiate applicable HTTP version as described in IETF RFC 7540 [12].
+
+Usage of HTTP over TLS and the TLS profiles shall be as specified in clause 5.1.1.4 of 3GPP TS 33.434 [26].
+
+## 6.4 Content type
+
+The bodies of HTTP request and successful HTTP responses shall be encoded in JSON format (see IETF RFC 8259 [13]).
+
+The MIME media type that shall be used within the related Content-Type header field is "application/json", as defined in IETF RFC 8259 [13].
+
+NOTE: This release only supports the content type JSON.
+
+## 6.5 URI structure
+
+### 6.5.1 Resource URI structure
+
+All API URIs of SEAL APIs shall be:
+
+**{apiRoot}</apiName>/<apiVersion>/**
+
+"apiRoot" is configured by means outside the scope of the present document. It includes the scheme ("https"), host and optional port, and an optional prefix string. "apiName" and "apiVersion" shall be set dependent on the API, as defined in the corresponding clauses below.
+
+All resource URIs in the clauses below are defined relative to the above root API URI.
+
+NOTE 1: The "apiVersion" will only be increased if the new API version contains backward incompatible changes. Otherwise, the supported feature mechanism defined in clause 6.8 can be used to negotiate extensions.
+
+NOTE 2: A different root structure can be used when the resource URI is preconfigured in the API invoking entity.
+
+The root structure may be followed by "apiSpecificSuffixes" that are dependent on the API and are defined separately for each API as resource URI where they apply:
+
+{apiRoot}</apiName></apiVersion></apiSpecificSuffixes>
+
+## 6.5.2 Custom operations URI structure
+
+The custom operation definition is in Annex C of 3GPP TS 29.501 [14].
+
+The URI of a custom operation which is associated with a resource shall have the following structure:
+
+{apiRoot}</apiName></apiVersion></apiSpecificResourceUriPart></custOpName>
+
+Custom operations can also be associated with the service instead of a resource. The URI of a custom operation which is not associated with a resource shall have the following structure:
+
+{apiRoot}</apiName></apiVersion></custOpName>
+
+In the above URI structures, "apiRoot", "apiName", "apiVersion" and "apiSpecificResourceUriPart" are as defined in clause 6.5.1 and "custOpName" represents the name of the custom operation as defined in clause 5.1.3.2 of 3GPP TS 29.501 [14]
+
+## 6.6 Notifications
+
+The functional entities
+
+- shall support the delivery of notifications using a separate HTTP connection towards an address;
+- may support testing delivery of notifications; and
+- may support the delivery of notification using WebSocket protocol (see IETF RFC 6455 [4]),
+
+as described in 3GPP TS 29.122 [3], with the following clarifications:
+
+- the SCEF is the SEAL server; and
+- the SCS/AS is the Subscriber.
+
+## 6.7 Error Handling
+
+Response bodies for error handling, as described in 3GPP TS 29.122 [3], are applicable to all APIs in the present specification unless specified otherwise, with the following clarifications:
+
+- the SCEF is the SEAL server; and
+- the SCS/AS is the functional entity invoking an API.
+
+## 6.8 Feature negotiation
+
+The functional entity invoking an API (i.e. the VAL server) and the SEAL server use feature negotiation procedures defined in 3GPP TS 29.122 [3] to negotiate the supported features, with the following clarifications:
+
+- description of the SCEF applies to the SEAL server; and
+- description of the SCS/AS applies to the functional entity invoking an API.
+
+## 6.9 HTTP headers
+
+The HTTP headers described in 3GPP TS 29.122 [3] are applicable to all APIs in this document.
+
+## 6.10 Conventions for Open API specification files
+
+The conventions for Open API specification files as specified in clause 5.2.9 of 3GPP TS 29.122 [3] shall be applicable for all APIs in this document.
+
+## 7 SEAL API Definitions
+
+### 7.1 Location management APIs
+
+#### 7.1.1 SS\_LocationReporting API
+
+##### 7.1.1.1 API URI
+
+The SS\_LocationReporting service shall use the SS\_LocationReporting API.
+
+The request URIs used in HTTP requests from the VAL server towards the location management server shall have the Resource URI structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-lr".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> shall be set as described in clause 7.1.1.2.
+
+##### 7.1.1.2 Resources
+
+###### 7.1.1.2.1 Overview
+
+{apiRoot}/ss-lr/{apiVersion}
+
+![Diagram showing the resource URI structure for the SS_LocationReporting API. The root URI is {apiRoot}/ss-lr/{apiVersion}. A line branches from this root to a box containing /trigger-configurations. From the bottom of this box, another line branches to a box containing /{configurationId}.](ead623e6a8ec701df64567695a57d01c_img.jpg)
+
+```
+graph TD; Root["{apiRoot}/ss-lr/{apiVersion}"] --- Trigger["/trigger-configurations"]; Trigger --- ConfigId["/{configurationId}"];
+```
+
+Diagram showing the resource URI structure for the SS\_LocationReporting API. The root URI is {apiRoot}/ss-lr/{apiVersion}. A line branches from this root to a box containing /trigger-configurations. From the bottom of this box, another line branches to a box containing /{configurationId}.
+
+**Figure 7.1.1.2.1-1: Resource URI structure of the SS\_LocationReporting API**
+
+Table 7.1.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+Table 7.1.1.2.1-1: Resources and methods overview
+
+| Resource name                                    | Resource URI                              | HTTP method or custom operation | Description                                                                                                |
+|--------------------------------------------------|-------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------|
+| SEAL Location Reporting Configurations           | /trigger-configurations                   | POST                            | Creates a new Individual SEAL Location Reporting Configuration information.                                |
+| Individual SEAL Location Reporting Configuration | /trigger-configurations/{configurationId} | GET                             | Retrieves an Individual SEAL Location Reporting Configuration information identified by {configurationId}. |
+|                                                  |                                           | PUT                             | Updates an Individual SEAL Location Reporting Configuration information identified by {configurationId}.   |
+|                                                  |                                           | DELETE                          | Delete an Individual SEAL Location Reporting Configuration information identified by {configurationId}.    |
+
+## 7.1.1.2.2 Resource: SEAL Location Reporting Configurations
+
+### 7.1.1.2.2.1 Description
+
+The resource allows the VAL server to request to create a new individual SEAL location reporting configuration information at the location management server.
+
+### 7.1.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-lr/<apiVersion>/trigger-configurations
+
+This resource shall support the resource URI variables defined in the table 7.1.1.2.2.2-1.
+
+Table 7.1.1.2.2.2-1: Resource URI variables for this resource
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 6.5     |
+| apiVersion | string    | See clause 7.1.1.1 |
+
+### 7.1.1.2.2.3 Resource Standard Methods
+
+#### 7.1.1.2.2.3.1 POST
+
+Table 7.1.1.2.2.3.1-1: URI query parameters supported by the POST method on this resource
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.1.1.2.2.3.1-2 and the response data structures and response codes specified in table 7.1.1.2.2.3.1-3.
+
+Table 7.1.1.2.2.3.1-2: Data structures supported by the POST Request Body on this resource
+
+| Data type                      | P | Cardinality | Description                                   |
+|--------------------------------|---|-------------|-----------------------------------------------|
+| LocationReportingConfiguration | M | 1           | Location reporting configuration information. |
+
+**Table 7.1.1.2.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                 | P | Cardinality | Response codes | Description                                               |
+|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-----------------------------------------------------------|
+| LocationReportConfiguration                                                                                               | M | 1           | 201 Created    | Location reporting configuration is created successfully. |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                           |
+
+**Table 7.1.1.2.2.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                                       |
+|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/ss-lr/<apiVersion>/trigger-configurations/{configurationId} |
+
+#### 7.1.1.2.2.4 Resource Custom Operations
+
+None.
+
+#### 7.1.1.2.3 Resource: Individual SEAL Location Reporting Configuration
+
+##### 7.1.1.2.3.1 Description
+
+The resource represents an individual SEAL location reporting configuration that is created at the location management server.
+
+##### 7.1.1.2.3.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-lr/<apiVersion>/trigger-configurations/{configurationId}
+
+This resource shall support the resource URI variables defined in the table 7.1.1.2.3.2-1.
+
+**Table 7.1.1.2.3.2-1: Resource URI variables for this resource**
+
+| Name            | Data Type | Definition                                                               |
+|-----------------|-----------|--------------------------------------------------------------------------|
+| apiRoot         | string    | See clause 6.5                                                           |
+| apiVersion      | string    | See clause 7.1.1.1                                                       |
+| configurationId | string    | Represents an individual SEAL location reporting configuration resource. |
+
+##### 7.1.1.2.3.3 Resource Standard Methods
+
+###### 7.1.1.2.3.3.1 GET
+
+This operation retrieves an individual SEAL location reporting configuration information. This method shall support the URI query parameters specified in table 7.1.1.2.3.3.1-1.
+
+**Table 7.1.1.2.3.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.1.1.2.3.3.1-2 and the response data structures and response codes specified in table 7.1.1.2.3.3.1-3.
+
+**Table 7.1.1.2.3.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.1.1.2.3.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                       |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|---------------------------------------------------|
+| LocationReportConfiguration                                                                                              | M | 1           | 200 OK         | The location reporting configuration information. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                   |
+
+#### 7.1.1.2.3.3.2 PUT
+
+This operation updates the individual SEAL location reporting configuration. This method shall support the URI query parameters specified in table 7.1.1.2.3.3.2-1.
+
+**Table 7.1.1.2.3.3.2-1: URI query parameters supported by the PUT method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.1.1.2.3.3.2-2 and the response data structures and response codes specified in table 7.1.1.2.3.3.2-3.
+
+**Table 7.1.1.2.3.3.2-2: Data structures supported by the PUT Request Body on this resource**
+
+| Data type                   | P | Cardinality | Description                                              |
+|-----------------------------|---|-------------|----------------------------------------------------------|
+| LocationReportConfiguration | M | 1           | Updated details of the location reporting configuration. |
+
+**Table 7.1.1.2.3.3.2-3: Data structures supported by the PUT Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                                   |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------|
+| LocationReportConfiguration                                                                                              | M | 1           | 200 OK         | The configuration is updated successfully and the updated configuration information returned in the response. |
+| NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                               |
+
+#### 7.1.1.2.3.3.3 DELETE
+
+This operation deletes the individual SEAL location reporting configuration. This method shall support the URI query parameters specified in table 7.1.1.2.3.3.3-1.
+
+**Table 7.1.1.2.3.3.3-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.1.1.2.3.3.3-2 and the response data structures and response codes specified in table 7.1.1.2.3.3.3-3.
+
+**Table 7.1.1.2.3.3.3-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.1.1.2.3.3.3-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type                                                                                                                   | P | Cardinality | Response codes | Description                                                           |
+|-----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-----------------------------------------------------------------------|
+| n/a                                                                                                                         |   |             | 204 No Content | The individual configuration matching the configurationId is deleted. |
+| NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                       |
+
+#### 7.1.1.2.3.4 Resource Custom Operations
+
+None.
+
+#### 7.1.1.3 Notifications
+
+None.
+
+#### 7.1.1.4 Data Model
+
+##### 7.1.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API.
+
+Table 7.1.1.4.1-1 specifies the data types defined specifically for the SS\_LocationReporting API service.
+
+**Table 7.1.1.4.1-1: SS\_LocationReporting API specific Data Types**
+
+| Data type                   | Section defined | Description | Applicability |
+|-----------------------------|-----------------|-------------|---------------|
+| LocationReportConfiguration | 7.1.1.4.2.2     |             |               |
+
+Table 7.1.1.4.1-2 specifies data types re-used by the SS\_LocationReporting API service.
+
+**Table 7.1.1.4.1-2: SS\_LocationReporting API Re-used Data Types**
+
+| Data type         | Reference           | Comments                                                                               | Applicability |
+|-------------------|---------------------|----------------------------------------------------------------------------------------|---------------|
+| Accuracy          | 3GPP TS 29.122 [3]  |                                                                                        |               |
+| DateTime          | 3GPP TS 29.571 [21] |                                                                                        |               |
+| DurationSec       | 3GPP TS 29.571 [21] |                                                                                        |               |
+| SupportedFeatures | 3GPP TS 29.571 [21] | Used to negotiate the applicability of optional features defined in table 7.1.1.6-1.   |               |
+| ValTargetUe       | Clause 7.3.1.4.2.3  | Used to indicate either VAL User ID or VAL UE ID, to which location reporting applies. |               |
+
+### 7.1.1.4.2 Structured data types
+
+#### 7.1.1.4.2.1 Introduction
+
+#### 7.1.1.4.2.2 Type: LocationReportConfiguration
+
+**Table 7.1.1.4.2.2-1: Definition of type LocationReportConfiguration**
+
+| Attribute name | Data type         | P | Cardinality | Description                                                                                                                                                                                            | Applicability |
+|----------------|-------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| valServerId    | string            | M | 1           | Represents the VAL server identifier.                                                                                                                                                                  |               |
+| valTgtUe       | ValTargetUe       | M | 1           | Represents the VAL User ID or VAL UE ID to which the location reporting applies.                                                                                                                       |               |
+| immRep         | boolean           | O | 0..1        | Indication of immediate reporting. If included, when it is set to true it indicates immediate reporting of the subscribed events, if available. Otherwise, reporting will occur when the event is met. |               |
+| monDur         | DateTime          | O | 0..1        | Represents the time at which the subscription ceases to exist (i.e the reporting trigger becomes invalid). If omitted, there is no time limit.                                                         |               |
+| repPeriod      | DurationSec       | O | 0..1        | Indicates the time interval between successive location reports.                                                                                                                                       |               |
+| accuracy       | Accuracy          | O | 0..1        | Represents the desired level of accuracy of the requested location information.                                                                                                                        |               |
+| suppFeat       | SupportedFeatures | O | 0..1        | Used to negotiate the supported features of the API as defined in clause 7.1.1.6. This attribute shall be provided in the HTTP POST request and in the response of successful resource creation.       |               |
+
+### 7.1.1.4.3 Simple data types and enumerations
+
+### 7.1.1.5 Error Handling
+
+General error responses are defined in clause 6.7.
+
+### 7.1.1.6 Feature negotiation
+
+General feature negotiation procedures are defined in clause 6.8.
+
+**Table 7.1.1.6-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+## 7.2 Group management APIs
+
+### 7.2.1 SS\_GroupManagement API
+
+#### 7.2.1.1 API URI
+
+The SS\_GroupManagement service shall use the SS\_GroupManagement API.
+
+The request URIs used in HTTP requests from the VAL server towards the Group management server shall have the Resource URI structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-gm".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> shall be set as described in clause 7.2.1.2
+
+## 7.2.1.2 Resources
+
+## 7.2.1.2.1 Overview
+
+![Diagram showing the resource URI structure of the SS_GroupManagement API. The root URI is {apiRoot}/ss-gm/<apiVersion>. A line branches from this root to a box containing /group-documents. From this box, another line branches down to a box containing /{groupDocId}.](a4b963a07cc368283154762c4b156fe7_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/ss-gm/<apiVersion>"] --> GroupDocs["/group-documents"]
+    GroupDocs --> GroupDocId["/{groupDocId}"]
+  
+```
+
+Diagram showing the resource URI structure of the SS\_GroupManagement API. The root URI is {apiRoot}/ss-gm/. A line branches from this root to a box containing /group-documents. From this box, another line branches down to a box containing /{groupDocId}.
+
+**Figure 7.2.1.2.1-1: Resource URI structure of the SS\_GroupManagement API**
+
+Table 7.2.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 7.2.1.2.1-1: Resources and methods overview**
+
+| Resource name                 | Resource URI                  | HTTP method or custom operation | Description                                                                                                                                                                                                                                                   |
+|-------------------------------|-------------------------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| VAL Group Documents           | /group-documents              | POST                            | Create a new VAL group document.                                                                                                                                                                                                                              |
+|                               |                               | GET                             | Retrieve VAL group documents according to the query parameters. If there are no query parameters, do not fetch any VAL group document.                                                                                                                        |
+| Individual VAL Group Document | /group-documents/{groupDocId} | GET                             | Retrieve an individual VAL group's membership and configuration information according to query parameter on the resource identified by {groupDocId}. If there are no query parameter, fetch the whole VAL group document resource identified by {groupDocId}. |
+|                               |                               | PUT                             | Update an individual VAL group's membership and configuration information identified by {groupDocId}.                                                                                                                                                         |
+
+## 7.2.1.2.2 Resource: VAL Group Documents
+
+## 7.2.1.2.2.1 Description
+
+The VAL Group Documents resource represents all the VAL group documents that are created at a given group management server.
+
+## 7.2.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-gm/<apiVersion>/group-documents
+
+This resource shall support the resource URI variables defined in the table 7.2.1.2.2.2-1.
+
+**Table 7.2.1.2.2.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 6.5     |
+| apiVersion | string    | See clause 7.2.1.1 |
+
+### 7.2.1.2.2.3 Resource Standard Methods
+
+#### 7.2.1.2.2.3.1 POST
+
+This method shall support the URI query parameters specified in table 7.2.1.2.2.3.1-1.
+
+**Table 7.2.1.2.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.2.1.2.2.3.1-2 and the response data structures and response codes specified in table 7.2.1.2.2.3.1-3.
+
+**Table 7.2.1.2.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type        | P | Cardinality | Description                                        |
+|------------------|---|-------------|----------------------------------------------------|
+| VALGroupDocument | M | 1           | Details of the VAL group that needs to be created. |
+
+**Table 7.2.1.2.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                 | P | Cardinality | Response codes | Description                                                                                                             |
+|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------|
+| VALGroupDocument                                                                                                          | M | 1           | 201 Created    | VAL group created successfully.<br><br>The URI of the created resource shall be returned in the “Location” HTTP header. |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                         |
+
+**Table 7.2.1.2.2.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                           |
+|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/ss-gm/<apiVersion>/group-documents/{groupDocId} |
+
+#### 7.2.1.2.2.3.2 GET
+
+This operation retrieves VAL group documents satisfying filter criteria. This method shall support the URI query parameters specified in table 7.2.1.2.2.3.2-1.
+
+**Table 7.2.1.2.2.3.2-1: URI query parameters supported by the GET method on this resource**
+
+| Name           | Data type | P | Cardinality | Description                         |
+|----------------|-----------|---|-------------|-------------------------------------|
+| val-group-id   | string    | O | 0..1        | String identifying the VAL group.   |
+| val-service-id | string    | O | 0..1        | String identifying the VAL service. |
+
+This method shall support the request data structures specified in table 7.2.1.2.2.3.2-2 and the response data structures and response codes specified in table 7.2.1.2.2.3.2-3.
+
+**Table 7.2.1.2.2.3.2-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.2.1.2.2.3.2-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                                                         |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------|
+| array(VALGroup Document)                                                                                                 | M | 0..N        | 200 OK         | List of VAL group documents. This response shall include VAL group documents matching the query parameters provided in the request. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                                     |
+
+#### 7.2.1.2.2.4 Resource Custom Operations
+
+None.
+
+#### 7.2.1.2.3 Resource: Individual VAL Group Document
+
+##### 7.2.1.2.3.1 Description
+
+The Individual VAL Group Document resource represents an individual group document that is created at a given group management server.
+
+##### 7.2.1.2.3.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-gm/<apiVersion>/group-documents/{groupDocId}
+
+This resource shall support the resource URI variables defined in the table 7.2.1.2.3.2-1.
+
+**Table 7.2.1.2.3.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition                                        |
+|------------|-----------|---------------------------------------------------|
+| apiRoot    | string    | See clause 6.5                                    |
+| apiVersion | string    | See clause 7.2.1.1                                |
+| groupDocId | string    | Represents an individual group document resource. |
+
+##### 7.2.1.2.3.3 Resource Standard Methods
+
+###### 7.2.1.2.3.3.1 GET
+
+This operation retrieves VAL group information satisfying filter criteria. This method shall support the URI query parameters specified in table 7.2.1.2.3.3.1-1.
+
+**Table 7.2.1.2.3.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name                | Data type | P | Cardinality | Description                                                                                                                                             |
+|---------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| group-members       | boolean   | O | 0..1        | When set to 'true', it indicates the group management server to send the members list information of the VAL group. Set to false or omitted otherwise.  |
+| group-configuration | boolean   | O | 0..1        | When set to 'true', it indicates the group management server to send the configuration information of the VAL group. Set to false or omitted otherwise. |
+
+This method shall support the request data structures specified in table 7.2.1.2.3.3.1-2 and the response data structures and response codes specified in table 7.2.1.2.3.3.1-3.
+
+**Table 7.2.1.2.3.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.2.1.2.3.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| VALGroupDocument                                                                                                         | M | 1           | 200 OK         | The VAL group information based on the request from the VAL server. This response shall include VAL group members list if group-members flag is set to true in the request, VAL group configuration information if the group-configuration flag is set to true in the request, VAL group identifier, whole VAL group document resource if both group-members and group-configuration flags are omitted/set to false in the request. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+#### 7.2.1.2.3.3.2 PUT
+
+This operation updates the VAL group document. This method shall support the URI query parameters specified in table 7.2.1.2.3.3.2-1.
+
+**Table 7.2.1.2.3.3.2-1: URI query parameters supported by the PUT method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.2.1.2.3.3.2-2 and the response data structures and response codes specified in table 7.2.1.2.3.3.2-3.
+
+**Table 7.2.1.2.3.3.2-2: Data structures supported by the PUT Request Body on this resource**
+
+| Data type        | P | Cardinality | Description                                |
+|------------------|---|-------------|--------------------------------------------|
+| VALGroupDocument | M | 1           | Updated details of the VAL group document. |
+
+**Table 7.2.1.2.3.3.2-3: Data structures supported by the PUT Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                              |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------|
+| VALGroupDocument                                                                                                         | M | 1           | 200 OK         | The VAL group document updated successfully and the updated VAL group document returned in the response. |
+| NOTE: The mandatory HTTP error status codes for the PUT method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                          |
+
+#### 7.2.1.2.3.3.3 DELETE
+
+This operation deletes the VAL group document. This method shall support the URI query parameters specified in table 7.2.1.2.3.3.3-1.
+
+**Table 7.2.1.2.3.3.3-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.2.1.2.3.3.3-2 and the response data structures and response codes specified in table 7.2.1.2.3.3.3-3.
+
+**Table 7.2.1.2.3.3.3-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.2.1.2.3.3.3-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type                                                                                                                   | P | Cardinality | Response codes | Description                                                           |
+|-----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-----------------------------------------------------------------------|
+| n/a                                                                                                                         |   |             | 204 No Content | The individual VAL group document matching the groupDocId is deleted. |
+| NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                       |
+
+#### 7.2.1.2.3.4 Resource Custom Operations
+
+None.
+
+#### 7.2.1.3 Notifications
+
+None.
+
+#### 7.2.1.4 Data Model
+
+##### 7.2.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API
+
+Table 7.2.1.4.1-1 specifies the data types defined specifically for the SS\_GroupManagement API service.
+
+**Table 7.2.1.4.1-1: SS\_GroupManagement API specific Data Types**
+
+| Data type        | Section defined | Description                 | Applicability |
+|------------------|-----------------|-----------------------------|---------------|
+| VALGroupDocument | 7.2.1.4.2.2     | VAL group document details. |               |
+
+Table 7.2.1.4.1-2 specifies data types re-used by the SS\_GroupManagement API service.
+
+**Table 7.2.1.4.1-2: Re-used Data Types**
+
+| Data type         | Reference           | Comments                                                                               | Applicability |
+|-------------------|---------------------|----------------------------------------------------------------------------------------|---------------|
+| SupportedFeatures | 3GPP TS 29.571 [21] | Used to negotiate the applicability of optional features defined in table 7.2.1.6-1.   |               |
+| LocationInfo      | 3GPP TS 29.122 [3]  | The location information related to VAL group.                                         |               |
+| ValTargetUe       | Clause 7.3.1.4.2.3  | Used to indicate either VAL User ID or VAL UE ID, to which location reporting applies. |               |
+| LocationArea5G    | 3GPP TS 29.122 [3]  | The locations information related to the VAL group.                                    |               |
+
+## 7.2.1.4.2 Structured data types
+
+### 7.2.1.4.2.1 Introduction
+
+### 7.2.1.4.2.2 Type: VALGroupDocument
+
+**Table 7.2.1.4.2.2-1: Definition of type VALGroupDocument**
+
+| Attribute name | Data type          | P | Cardinality | Description                                                                                                                                                                                                | Applicability |
+|----------------|--------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| valGroupId     | string             | M | 1           | This is VAL group identity (VAL group ID) as per TS 23.434 [2], which is a unique identifier within the VAL service that represents a VAL group, set of VAL users or VAL UEs according to the VAL service. |               |
+| grpDesc        | string             | O | 0..1        | Text description of the VAL group.                                                                                                                                                                         |               |
+| members        | array(ValTargetUe) | O | 1..N        | List of VAL User IDs or VAL UE IDs, which are members of the VAL group.                                                                                                                                    |               |
+| valGrpConf     | string             | O | 0..1        | Configuration data for the VAL group. Shall be present in HTTP POST request message from VAL server to Group Management server.                                                                            |               |
+| valServiceIds  | array(string)      | O | 1..N        | List of VAL services whose communications enabled on the group.                                                                                                                                            |               |
+| suppFeat       | Supported Features | O | 0..1        | Used to negotiate the supported optional features of the API as described in clause 6.8.<br>This attribute shall be provided in the HTTP POST request and in the response of successful resource creation. |               |
+| resUri         | Uri                | O | 0..1        | The URI for individual VAL group document resource. (NOTE)                                                                                                                                                 |               |
+| locInfo        | LocationInfo       | O | 0..1        | The location information related to the VAL group. This information is used to determine the members of the group.                                                                                         |               |
+| addLocInfo     | LocationArea5G     | O | 0..1        | The additional location information related to the VAL group. This information is used to determine the members of the group.                                                                              |               |
+
+NOTE: The "resUri" attribute is not modifiable by the VAL server.
+
+## 7.2.1.4.3 Simple data types and enumerations
+
+None.
+
+## 7.2.1.5 Error Handling
+
+General error responses are defined in clause 6.7.
+
+## 7.2.1.6 Feature negotiation
+
+General feature negotiation procedures are defined in clause 6.8.
+
+**Table 7.2.1.6-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+## 7.3 Configuration management APIs
+
+### 7.3.1 SS\_UserProfileRetrieval API
+
+#### 7.3.1.1 API URI
+
+The SS\_UserProfileRetrieval service shall use the SS\_UserProfileRetrieval API.
+
+The request URIs used in HTTP requests from the VAL server towards the Configuration management server shall have the Resource URI structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-upr".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> shall be set as described in clause 7.3.1.2.
+
+#### 7.3.1.2 Resources
+
+##### 7.3.1.2.1 Overview
+
+![Diagram showing the resource URI structure for the SS_UserProfileRetrieval API. The root URI is {apiRoot}/ss-upr/<apiVersion>. A line branches from this root to a box containing /val-services. From the bottom of this box, another line branches down to the placeholder /{valServiceId}.](c468d53e877568cd7d8c5ba1632c2e65_img.jpg)
+
+```
+
+    graph TD
+      Root["{apiRoot}/ss-upr/<apiVersion>"] --> Box[ /val-services ]
+      Box --> Id[ /{valServiceId} ]
+  
+```
+
+Diagram showing the resource URI structure for the SS\_UserProfileRetrieval API. The root URI is {apiRoot}/ss-upr/. A line branches from this root to a box containing /val-services. From the bottom of this box, another line branches down to the placeholder /{valServiceId}.
+
+**Figure 7.3.1.2.1-1: Resource URI structure of the SS\_UserProfileRetrieval API**
+
+Table 7.3.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 7.3.1.2.1-1: Resources and methods overview**
+
+| Resource name | Resource URI  | HTTP method or custom operation | Description                                        |
+|---------------|---------------|---------------------------------|----------------------------------------------------|
+| VAL Services  | /val-services | GET                             | Retrieve VAL User or VAL UE's profile information. |
+
+#### 7.3.1.2.2 Resource: VAL Services
+
+##### 7.3.1.2.2.1 Description
+
+The VAL Services resource represents all the VAL services that are created at a given configuration management server.
+
+##### 7.3.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-upr/<apiVersion>/val-services
+
+This resource shall support the resource URI variables defined in the table 7.3.1.2.2.2-1.
+
+**Table 7.3.1.2.2.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 6.5     |
+| apiVersion | string    | See clause 7.3.1.1 |
+
+### 7.3.1.2.2.3 Resource Standard Methods
+
+#### 7.3.1.2.2.3.1 GET
+
+This operation retrieves VAL User or VAL UE profile information satisfying the filter criteria. This method shall support the URI query parameters specified in table 7.3.1.2.2.3.1-1.
+
+**Table 7.3.1.2.2.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name           | Data type   | P | Cardinality | Description                       |
+|----------------|-------------|---|-------------|-----------------------------------|
+| val-tgt-ue     | ValTargetUe | M | 1           | Identifying a VAL target UE.      |
+| val-service-id | string      | O | 0..1        | String identifying a VAL service. |
+
+This method shall support the request data structures specified in table 7.3.1.2.2.3.2-2 and the response data structures and response codes specified in table 7.3.1.2.2.3.2-3.
+
+**Table 7.3.1.2.2.3.2-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.3.1.2.2.3.2-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                                                                              |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| array(ProfileDoc)                                                                                                        | M | 0..N        | 200 OK         | List of VAL User / VAL UE profile documents. This response shall include user profile information matching the query parameters provided in the request. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                                                          |
+
+### 7.3.1.2.2.4 Resource Custom Operations
+
+None.
+
+## 7.3.1.3 Notifications
+
+None.
+
+## 7.3.1.4 Data Model
+
+### 7.3.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API
+
+Table 7.3.1.4.1-1 specifies the data types defined specifically for the SS\_UserProfileRetrieval API service.
+
+**Table 7.3.1.4.1-1: SS\_UserProfileRetrieval API specific Data Types**
+
+| Data type   | Section defined | Description                                                   | Applicability |
+|-------------|-----------------|---------------------------------------------------------------|---------------|
+| ProfileDoc  | 7.3.1.4.2.2     | Profile information associated with VAL user ID or VAL UE ID. |               |
+| ValTargetUe | 7.3.1.4.2.3     | Information identifying a VAL user ID or VAL UE ID.           |               |
+
+Table 7.3.1.4.1-2 specifies data types re-used by the SS\_UserProfileRetrieval API service.
+
+**Table 7.3.1.4.1-2: Re-used Data Types**
+
+| Data type | Reference | Comments | Applicability |
+|-----------|-----------|----------|---------------|
+| n/a       |           |          |               |
+
+### 7.3.1.4.2 Structured data types
+
+#### 7.3.1.4.2.1 Introduction
+
+#### 7.3.1.4.2.2 Type: ProfileDoc
+
+**Table 7.3.1.4.2.2-1: Definition of type ProfileDoc**
+
+| Attribute name     | Data type   | P | Cardinality | Description                                   | Applicability |
+|--------------------|-------------|---|-------------|-----------------------------------------------|---------------|
+| profileInformation | string      | M | 1           | Profile information associated with valTgtUe. |               |
+| valTgtUe           | ValTargetUe | M | 1           | Unique identifier of a VAL user or a VAL UE.  |               |
+
+#### 7.3.1.4.2.3 Type: ValTargetUe
+
+**Table 7.3.1.4.2.3-1: Definition of type ValTargetUe**
+
+| Attribute name                                           | Data type | P | Cardinality | Description                      | Applicability |
+|----------------------------------------------------------|-----------|---|-------------|----------------------------------|---------------|
+| valUserId                                                | string    | O | 0..1        | Unique identifier of a VAL user. |               |
+| valUeId                                                  | string    | O | 0..1        | Unique identifier of a VAL UE.   |               |
+| NOTE: Either "valUserId" or "valUeId" shall be provided. |           |   |             |                                  |               |
+
+### 7.3.1.4.3 Simple data types and enumerations
+
+None.
+
+### 7.3.1.5 Error Handling
+
+General error responses are defined in clause 6.7.
+
+### 7.3.1.6 Feature negotiation
+
+General feature negotiation procedures are defined in clause 6.8.
+
+**Table 7.3.1.6-1: Supported Features**
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+## 7.4 Network resource management APIs
+
+### 7.4.1 SS\_Network\_Resource\_Adaptation API
+
+#### 7.4.1.1 API URI
+
+The SS\_Network\_Resource\_Adaptation service shall use the SS\_Network\_Resource\_Adaptation API.
+
+The request URIs used in HTTP requests from the VAL server towards the NRM server shall have the Resource URI structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-nra".
+- The <apiVersion> shall be "v1".
+
+- The <apiSpecificSuffixes> shall be set as described in clause 7.4.1.2
+
+## 7.4.1.2 Resources
+
+### 7.4.1.2.1 Overview
+
+![Resource URI structure diagram showing the hierarchy of the SS_NetworkResourceAdaptation API. The root is {apiRoot}/ss-nra/<apiVersion>. It branches into /multicast-subscriptions and /unicast-subscriptions. /multicast-subscriptions further branches into /{multiSubId}. /unicast-subscriptions further branches into /{uniSubId}.](030c758fd425016b03290c8f11bef69d_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/ss-nra/<apiVersion>"] --> Multicast["/multicast-subscriptions"]
+    Root --> Unicast["/unicast-subscriptions"]
+    Multicast --> MultiSubId["/{multiSubId}"]
+    Unicast --> UniSubId["/{uniSubId}"]
+  
+```
+
+Resource URI structure diagram showing the hierarchy of the SS\_NetworkResourceAdaptation API. The root is {apiRoot}/ss-nra/. It branches into /multicast-subscriptions and /unicast-subscriptions. /multicast-subscriptions further branches into /{multiSubId}. /unicast-subscriptions further branches into /{uniSubId}.
+
+**Figure 7.4.1.2.1-1: Resource URI structure of the SS\_NetworkResourceAdaptation API**
+
+Table 7.4.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 7.4.1.2.1-1: Resources and methods overview**
+
+| Resource name                     | Resource URI                          | HTTP method or custom operation | Description                                              |
+|-----------------------------------|---------------------------------------|---------------------------------|----------------------------------------------------------|
+| Multicast Subscriptions           | /multicast-subscriptions              | POST                            | Create a new Individual Multicast Subscription resource. |
+| Individual Multicast Subscription | /multicast-subscriptions/{multiSubId} | GET                             | Read an Individual Multicast Subscription resource.      |
+|                                   |                                       | DELETE                          | Remove an Individual Multicast Subscription resource.    |
+| Unicast Subscriptions             | /unicast-subscriptions                | POST                            | Create a new Individual Unicast Subscription resource.   |
+| Individual Unicast Subscription   | /unicast-subscriptions/{uniSubId}     | GET                             | Read an Individual Unicast Subscription resource.        |
+|                                   |                                       | DELETE                          | Remove an Individual Unicast Subscription resource.      |
+
+### 7.4.1.2.2 Resource: Multicast Subscriptions
+
+#### 7.4.1.2.2.1 Description
+
+#### 7.4.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-nra/<apiVersion>/multicast-subscriptions
+
+This resource shall support the resource URI variables defined in table 7.4.1.2.2.2-1.
+
+**Table 7.4.1.2.2.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 7.4.1.1 |
+| apiVersion | string    | See clause 7.4.1.1 |
+
+#### 7.4.1.2.2.3 Resource Standard Methods
+
+##### 7.4.1.2.2.3.1 POST
+
+**Table 7.4.1.2.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+|      |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.2.3.1-2 and the response data structures and response codes specified in table 7.4.1.2.2.3.1-3.
+
+**Table 7.4.1.2.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type             | P | Cardinality | Description |
+|-----------------------|---|-------------|-------------|
+| MulticastSubscription | M | 1           |             |
+
+**Table 7.4.1.2.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                          | P | Cardinality | Response codes | Description |
+|------------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------|
+| MulticastSubscription                                                                                                              | M | 1           | 201 Created    |             |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |             |
+
+**Table 7.4.1.2.2.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                                    |
+|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/ss-nra/<apiVersion>/multicast-subscriptions/{multiSubId} |
+
+#### 7.4.1.2.2.4 Resource Custom Operations
+
+None.
+
+### 7.4.1.2.3 Resource: Individual Multicast Subscription
+
+#### 7.4.1.2.3.1 Description
+
+#### 7.4.1.2.3.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-nra/<apiVersion>/multicast-subscriptions/{multiSubId}
+
+This resource shall support the resource URI variables defined in table 7.4.1.2.3.2-1.
+
+**Table 7.4.1.2.3.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition                             |
+|------------|-----------|----------------------------------------|
+| apiRoot    | string    | See clause 7.4.1.1.                    |
+| apiVersion | string    | See clause 7.4.1.1.                    |
+| multiSubId | string    | The multicast subscription identifier. |
+
+#### 7.4.1.2.3.3 Resource Standard Methods
+
+##### 7.4.1.2.3.3.1 GET
+
+**Table 7.4.1.2.3.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.3.3.1-2 and the response data structures and response codes specified in table 7.4.1.2.3.3.1-3.
+
+**Table 7.4.1.2.3.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.4.1.2.3.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                         | P | Cardinality | Response codes | Description |
+|-----------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------|
+| MulticastSubscription                                                                                                             | M | 1           | 200 OK         |             |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |             |
+
+##### 7.4.1.2.3.3.2 DELETE
+
+**Table 7.4.1.2.3.3.2-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.3.3.2-2 and the response data structures and response codes specified in table 7.4.1.2.3.3.2-3.
+
+**Table 7.4.1.2.3.3.2-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.4.1.2.3.3.2-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type                                                                                                                         | P | Cardinality | Response codes | Description                                                                  |
+|-----------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|------------------------------------------------------------------------------|
+| n/a                                                                                                                               |   |             | 204 No Content | Successful case. The Individual Multicast Subscription resource was deleted. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |                                                                              |
+
+#### 7.4.1.2.3.4 Resource Custom Operations
+
+None.
+
+#### 7.4.1.2.4 Resource: Unicast Subscriptions
+
+##### 7.4.1.2.4.1 Description
+
+##### 7.4.1.2.4.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-nra/{apiVersion}/unicast-subscriptions
+
+This resource shall support the resource URI variables defined in table 7.4.1.2.4.2-1.
+
+**Table 7.4.1.2.4.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 7.4.1.1 |
+| apiVersion | string    | See clause 7.4.1.1 |
+
+#### 7.4.1.2.4.3 Resource Standard Methods
+
+##### 7.4.1.2.4.3.1 POST
+
+**Table 7.4.1.2.4.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+|      |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.4.3.1-2 and the response data structures and response codes specified in table 7.4.1.2.4.3.1-3.
+
+**Table 7.4.1.2.4.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type           | P | Cardinality | Description |
+|---------------------|---|-------------|-------------|
+| UnicastSubscription | M | 1           |             |
+
+**Table 7.4.1.2.4.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                          | P | Cardinality | Response codes | Description |
+|------------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------|
+| UnicastSubscription                                                                                                                | M | 1           | 201 Created    |             |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |             |
+
+**Table 7.4.1.2.4.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                                |
+|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/ss-nra/<apiVersion>/unicast-subscriptions/{uniSubId} |
+
+#### 7.4.1.2.4.4 Resource Custom Operations
+
+None.
+
+### 7.4.1.2.5 Resource: Individual Unicast Subscription
+
+#### 7.4.1.2.5.1 Description
+
+#### 7.4.1.2.5.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-nra/<apiVersion>/unicast-subscriptions/{uniSubId}
+
+This resource shall support the resource URI variables defined in table 7.4.1.2.5.2-1.
+
+**Table 7.4.1.2.5.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition                           |
+|------------|-----------|--------------------------------------|
+| apiRoot    | string    | See clause 7.4.1.1.                  |
+| apiVersion | string    | See clause 7.4.1.1.                  |
+| uniSubId   | string    | The unicast subscription identifier. |
+
+#### 7.4.1.2.5.3 Resource Standard Methods
+
+##### 7.4.1.2.5.3.1 GET
+
+**Table 7.4.1.2.5.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.5.3.1-2 and the response data structures and response codes specified in table 7.4.1.2.5.3.1-3.
+
+**Table 7.4.1.2.5.3.1-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.4.1.2.5.3.1-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                         | P | Cardinality | Response codes | Description |
+|-----------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------|
+| UnicastSubscription                                                                                                               | M | 1           | 200 OK         |             |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |             |
+
+##### 7.4.1.2.5.3.2 DELETE
+
+**Table 7.4.1.2.5.3.2-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.2.5.3.2-2 and the response data structures and response codes specified in table 7.4.1.2.5.3.2-3.
+
+**Table 7.4.1.2.5.3.2-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.4.1.2.5.3.2-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type                                                                                                                         | P | Cardinality | Response codes | Description                                                                |
+|-----------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|----------------------------------------------------------------------------|
+| n/a                                                                                                                               |   |             | 204 No Content | Successful case. The Individual Unicast Subscription resource was deleted. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] shall also apply. |   |             |                |                                                                            |
+
+#### 7.4.1.2.5.4 Resource Custom Operations
+
+None.
+
+### 7.4.1.3 Notifications
+
+#### 7.4.1.3.1 General
+
+**Table 7.4.1.3.1-1: Notifications overview**
+
+| Notification            | Callback URI | HTTP method or custom operation | Description (service operation) |
+|-------------------------|--------------|---------------------------------|---------------------------------|
+| Notify_UP_Delivery_Mode | {notifUri}   | POST                            | Report User Plane notification  |
+
+#### 7.4.1.3.2 Notify\_UP\_Delivery\_Mode
+
+##### 7.4.1.3.2.1 Description
+
+##### 7.4.1.3.2.2 Notification definition
+
+Callback URI: {notifUri}
+
+This method shall support the URI query parameters specified in table 7.4.1.3.2.2-1.
+
+**Table 7.4.1.3.2.2-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.4.1.3.2.2-2 and the response data structures and response codes specified in table 7.4.1.3.2.2-3.
+
+**Table 7.4.1.3.2.2-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type             | P | Cardinality | Description |
+|-----------------------|---|-------------|-------------|
+| UserPlaneNotification | M | 1           |             |
+
+**Table 7.4.1.3.2.2-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                    | P | Cardinality | Response codes | Description                                      |
+|------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------|
+| n/a                                                                                                                          |   |             | 204 No Content | The receipt of the Notification is acknowledged. |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.7.1-1 of 3GPP TS 29.500 [22] also apply. |   |             |                |                                                  |
+
+### 7.4.1.4 Data Model
+
+#### 7.4.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API
+
+Table 7.4.1.4.1-1 specifies the data types defined specifically for the SS\_NetworkResourceAdaptation API service.
+
+**Table 7.4.1.4.1-1: SS\_NetworkResourceAdaptation API specific Data Types**
+
+| Data type               | Section defined | Description | Applicability |
+|-------------------------|-----------------|-------------|---------------|
+| DeliveryMode            | 7.4.1.4.3.2     |             |               |
+| MulticastSubscription   | 7.4.1.4.2.2     |             |               |
+| NrmEvent                | 7.4.1.4.3.3     |             |               |
+| NrmEventNotification    | 7.4.1.4.2.5     |             |               |
+| ServiceAnnouncementMode | 7.4.1.4.3.1     |             |               |
+| UserPlaneNotification   | 7.4.1.4.2.4     |             |               |
+| UnicastSubscription     | 7.4.1.4.2.3     |             |               |
+
+Table 7.4.1.4.1-2 specifies data types re-used by the SS\_NetworkResourceAdaptation API service.
+
+**Table 7.4.1.4.1-2: Re-used Data Types**
+
+| Data type          | Reference           | Comments                                              | Applicability |
+|--------------------|---------------------|-------------------------------------------------------|---------------|
+| DateTime           | 3GPP TS 29.571 [21] |                                                       |               |
+| MbmsLocArea        | 3GPP TS 29.122 [3]  |                                                       |               |
+| SupportedFeatures  | 3GPP TS 29.571 [21] |                                                       |               |
+| Uint32             | 3GPP TS 29.571 [21] |                                                       |               |
+| Uri                | 3GPP TS 29.571 [21] |                                                       |               |
+| WebsockNotifConfig | 3GPP TS 29.122 [3]  |                                                       |               |
+| ValTargetUe        | 7.3.1.4.2.3         | Used to identify either a VAL User ID or a VAL UE ID. |               |
+| Ipv4Addr           | 3GPP TS 29.571 [21] |                                                       |               |
+| Ipv6Addr           | 3GPP TS 29.571 [21] |                                                       |               |
+| Port               | 3GPP TS 29.122 [3]  |                                                       |               |
+
+## 7.4.1.4.2 Structured data types
+
+## 7.4.1.4.2.1 Introduction
+
+## 7.4.1.4.2.2 Type: MulticastSubscription
+
+Table 7.4.1.4.2.2-1: Definition of type MulticastSubscription
+
+| Attribute name | Data type               | P | Cardinality | Description                                                                                                                                                                                                                                                                                                             | Applicability           |
+|----------------|-------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| valGroupId     | string                  | M | 1           | The identity of the group that the MBMS bearer is requested for.                                                                                                                                                                                                                                                        |                         |
+| annncMode      | ServiceAnnouncementMode | M | 1           | Indicates whether the service announcement is sent by NRM server or by the VAL server.                                                                                                                                                                                                                                  |                         |
+| multiQosReq    | string                  | M | 1           | The QoS requirement for the multicast.                                                                                                                                                                                                                                                                                  |                         |
+| locArea        | MbmsLocArea             | O | 0..1        | Indicate the area where the MBMS bearer is requested for.                                                                                                                                                                                                                                                               |                         |
+| duration       | DateTime                | O | 0..1        | Identifies the absolute time at which the subscription resource is considered to expire. When omitted in the request, it indicates the resource is requested to be valid forever by the VAL server. When omitted in the response, it indicates the resource is set to valid forever by the VAL server.                  |                         |
+| tmgi           | Uint32                  | O | 0..1        | TMGI.<br>Shall be provided by the NRM server if announcement mode is set to VAL.                                                                                                                                                                                                                                        |                         |
+| notifUri       | Uri                     | M | 1           | Identifies the notification URI where the NRM notification shall be sent to.                                                                                                                                                                                                                                            |                         |
+| reqTestNotif   | boolean                 | O | 0..1        | Set to true by the NF service consumer to request the VAE server to send a test notification as defined in clause 6.3.5.3. Set to false or omitted otherwise.                                                                                                                                                           | Notification_test_event |
+| wsNotifCfg     | WebsockNotifConfig      | O | 0..1        | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 6.3.5.4.                                                                                                                                                                                                          | Notification_websocket  |
+| suppFeat       | SupportedFeatures       | C | 0..1        | Used to negotiate the applicability of optional features defined in table 7.4.1.6-1.<br>This parameter may be supplied by the VAL server in the POST request that requests the creation of a Multicast Subscription resource and shall be supplied in the corresponding POST response if it was present in the request. |                         |
+| upIpv4Addr     | Ipv4Addr                | O | 0..1        | Ipv4address of the user plane. (NOTE)                                                                                                                                                                                                                                                                                   |                         |
+| upIpv6Addr     | Ipv6Addr                | O | 0..1        | Ipv6address of the user plane. (NOTE)                                                                                                                                                                                                                                                                                   |                         |
+| upPortNum      | Port                    | O | 0..1        | UDP port number of the user plane.                                                                                                                                                                                                                                                                                      |                         |
+| radioFreqs     | array(Uint32)           | O | 1..N        | The radio frequencies which may be provided by the NRM server.                                                                                                                                                                                                                                                          |                         |
+
+NOTE: At least one of upIpv4Addr or upIpv6Addr shall be provided by the NRM server.
+
+## 7.4.1.4.2.3 Type: UnicastSubscription
+
+Table 7.4.1.4.2.3-1: Definition of type UnicastSubscription
+
+| Attribute name | Data type          | P | Cardinality | Description                                                                                                                                                                                                                                                                                            | Applicability           |
+|----------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| valTgtUe       | ValTargetUe        | M | 1           | The identity of the VAL user or VAL UE that the unicast bearer is requested for.                                                                                                                                                                                                                       |                         |
+| uniQosReq      | string             | O | 0..1        | The QoS requirement for the unicast.                                                                                                                                                                                                                                                                   |                         |
+| duration       | DateTime           | O | 0..1        | Identifies the absolute time at which the subscription resource is considered to expire. When omitted in the request, it indicates the resource is requested to be valid forever by the VAL server. When omitted in the response, it indicates the resource is set to valid forever by the VAL server. |                         |
+| notifUri       | Uri                | M | 1           | Identifies the notification URI where the NRM notification shall be sent to.                                                                                                                                                                                                                           |                         |
+| reqTestNotif   | Boolean            | O | 0..1        | Set to true by the NF service consumer to request the VAE server to send a test notification as defined in clause 6.3.5.3. Set to false or omitted otherwise.                                                                                                                                          | Notification_test_event |
+| wsNotifCfg     | WebsockNotifConfig | O | 0..1        | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 6.3.5.4.                                                                                                                                                                                         | Notification_websocket  |
+| suppFeat       | SupportedFeatures  | O | 1           | This parameter may be supplied by VAL server in the POST request that request the creation of a Unicast Subscription resource and may be supplied in the reply of corresponding request.                                                                                                               |                         |
+
+## 7.4.1.4.2.4 Type: UserPlaneNotification
+
+Table 7.4.1.4.2.4-1: Definition of type UserPlaneNotification
+
+| Attribute name | Data type                   | P | Cardinality | Description                                                          | Applicability |
+|----------------|-----------------------------|---|-------------|----------------------------------------------------------------------|---------------|
+| notifId        | Uri                         | M | 1           | The subscription resource Uri to which this notification is related. |               |
+| eventNotifs    | array(NrmEventNotification) | M | 1..N        | Notifications about Individual Events                                |               |
+
+## 7.4.1.4.2.5 Type: NrmEventNotification
+
+Table 7.4.1.4.2.5-1: Definition of type NrmEventNotification
+
+| Attribute name | Data type     | P | Cardinality | Description                                                                                                                                              | Applicability |
+|----------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| event          | NrmEvent      | M | 1           | Event that is notified.                                                                                                                                  |               |
+| ts             | DateTime      | M | 1           | Time at which the event is observed.                                                                                                                     |               |
+| deliveryMode   | DeliveryMode  | C | 0..1        | Indicates delivery of the user data to the UE(s) via unicast mode or multicast mode.<br>Shall be present if event is UP_DELIVERY_MODE.                   |               |
+| streamIds      | array(string) | O | 1..N        | Indicates the media streams (unicast or multicast) to be used.<br>May be present if event is UP_DELIVERY_MODE and NRM already has the streams available. |               |
+
+#### 7.4.1.4.3 Simple data types and enumerations
+
+##### 7.4.1.4.3.1 Enumeration: ServiceAnnouncementMode
+
+**Table 7.4.1.4.3.1-1: Enumeration ServiceAnnouncementMode**
+
+| Enumeration value | Description                                   | Applicability |
+|-------------------|-----------------------------------------------|---------------|
+| NRM               | NRM server performs the service announcement. |               |
+| VAL               | VAL server performs the service announcement. |               |
+
+##### 7.4.1.4.3.2 Enumeration: DeliveryMode
+
+**Table 7.4.1.4.3.2-1: Enumeration DeliveryMode**
+
+| Enumeration value | Description        | Applicability |
+|-------------------|--------------------|---------------|
+| UNICAST           | Unicast delivery   |               |
+| MULTICAST         | Multicast delivery |               |
+
+##### 7.4.1.4.3.3 Enumeration: NrmEvent
+
+**Table 7.4.1.4.3.3-1: Enumeration NrmEvent**
+
+| Enumeration value | Description               | Applicability |
+|-------------------|---------------------------|---------------|
+| UP_DELIVERY_MODE  | User Plane delivery mode. |               |
+
+#### 7.4.1.5 Error Handling
+
+#### 7.4.1.6 Feature negotiation
+
+**Table 7.4.1.6-1: Supported Features**
+
+| Feature number | Feature Name            | Description                                                                                                                                                          |
+|----------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1              | Notification_test_event | The testing of notification connection is supported according to clause 6.6.                                                                                         |
+| 2              | Notification_websocket  | The delivery of notifications over Websocket is supported according to clause 6.6. This feature requires that the Notification_test_event feature is also supported. |
+
+### 7.5 Event APIs
+
+#### 7.5.1 SS\_Events API
+
+##### 7.5.1.1 API URI
+
+The SS\_Events service shall use the SS\_Events API.
+
+The request URIs used in HTTP requests from the VAL server towards the SEAL server shall have the Resource URI structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-events".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> shall be set as described in clause 7.5.1.2.
+
+## 7.5.1.2 Resources
+
+### 7.5.1.2.1 Overview
+
+![Diagram showing the resource URI structure of the SS_Events API. The root path is {apiRoot}/ss-events/<apiVersion>. A callout box points to the /subscriptions path, which in turn points to a box containing /{subscriptionId}.](df1966d80c74bc127f159a48f38b13ee_img.jpg)
+
+{apiRoot}/ss-events/<apiVersion>
+
+```
+
+graph TD
+    Root["{apiRoot}/ss-events/<apiVersion>"] --> Subscriptions["/subscriptions"]
+    Subscriptions --> SubscriptionId["/{subscriptionId}"]
+  
+```
+
+Diagram showing the resource URI structure of the SS\_Events API. The root path is {apiRoot}/ss-events/. A callout box points to the /subscriptions path, which in turn points to a box containing /{subscriptionId}.
+
+**Figure 7.5.1.2.1-1: Resource URI structure of the SS\_Events API**
+
+Table 7.5.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+**Table 7.5.1.2.1-1: Resources and methods overview**
+
+| Resource name                       | Resource URI                    | HTTP method or custom operation | Description                                                                     |
+|-------------------------------------|---------------------------------|---------------------------------|---------------------------------------------------------------------------------|
+| SEAL Events Subscriptions           | /subscriptions                  | POST                            | Creates a new individual SEAL Event Subscription.                               |
+| Individual SEAL Events Subscription | /subscriptions/{subscriptionId} | DELETE                          | Deletes an individual SEAL Event Subscription identified by the subscriptionId. |
+
+### 7.5.1.2.2 Resource: SEAL Events Subscriptions
+
+#### 7.5.1.2.2.1 Description
+
+The SEAL Events Subscriptions represents all event subscriptions on the SEAL server.
+
+#### 7.5.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-events/<apiVersion>/subscriptions
+
+This resource shall support the resource URI variables defined in the table 7.5.1.2.2.2-1.
+
+**Table 7.5.1.2.2.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 6.5     |
+| apiVersion | string    | See clause 7.5.1.1 |
+
+#### 7.5.1.2.2.3 Resource Standard Methods
+
+##### 7.5.1.2.2.3.1 POST
+
+This method shall support the URI query parameters specified in the table 7.5.1.2.2.3.1-1.
+
+**Table 7.5.1.2.2.3.1-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.5.1.2.2.3.1-2 and the response data structures and response codes specified in table 7.5.1.2.2.3.1-3.
+
+**Table 7.5.1.2.2.3.1-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type             | P | Cardinality | Description                                                |
+|-----------------------|---|-------------|------------------------------------------------------------|
+| SEALEventSubscription | M | 1           | Create a new individual SEAL Events Subscription resource. |
+
+**Table 7.5.1.2.2.3.1-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                 | P | Cardinality | Response codes | Description                                                                                                                                |
+|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| SEALEventSubscription                                                                                                     | M | 1           | 201<br>Created | SEAL Events Subscription resource created successfully.<br>The URI of the created resource shall be returned in the "Location" HTTP header |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                                            |
+
+**Table 7.5.1.2.2.3.1-4: Headers supported by the 201 Response Code on this resource**
+
+| Name     | Data type | P | Cardinality | Description                                                                                                                                 |
+|----------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| Location | string    | M | 1           | Contains the URI of the newly created resource, according to the structure: {apiRoot}/ss-events/<apiVersion>/subscriptions/{subscriptionId} |
+
+#### 7.5.1.2.2.4 Resource Custom Operations
+
+None.
+
+#### 7.5.1.2.3 Resource: Individual SEAL Events Subscription
+
+##### 7.5.1.2.3.1 Description
+
+The Individual SEAL Events Subscription resource represents an individual event subscription of a VAL server.
+
+##### 7.5.1.2.3.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-events/<apiVersion>/subscriptions/{subscriptionId}
+
+This resource shall support the resource URI variables defined in the table 7.5.1.2.3.2-1.
+
+**Table 7.5.1.2.3.2-1: Resource URI variables for this resource**
+
+| Name           | Data Type | Definition                                   |
+|----------------|-----------|----------------------------------------------|
+| apiRoot        | string    | See clause 6.5                               |
+| apiVersion     | string    | See clause 7.5.1.1                           |
+| SubscriptionId | string    | Identifies an Individual Events Subscription |
+
+##### 7.5.1.2.3.3 Resource Standard Methods
+
+###### 7.5.1.2.3.3.1 DELETE
+
+This method shall support the URI query parameters specified in table 7.5.1.2.3.3.1-1.
+
+**Table 7.5.1.2.3.3.1-1: URI query parameters supported by the DELETE method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.5.1.2.3.3.1-2 and the response data structures and response codes specified in table 7.5.1.2.3.3.1-3.
+
+**Table 7.5.1.2.3.3.1-2: Data structures supported by the DELETE Request Body on this resource**
+
+| Data type | P | Cardinality | Description |  |
+|-----------|---|-------------|-------------|--|
+| n/a       |   |             |             |  |
+
+**Table 7.5.1.2.3.3.1-3: Data structures supported by the DELETE Response Body on this resource**
+
+| Data type                                                                                                                   | P | Cardinality | Response codes | Description                                                                     |
+|-----------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|---------------------------------------------------------------------------------|
+| n/a                                                                                                                         |   |             | 204 No Content | The individual SEAL Events Subscription matching the subscriptionId is deleted. |
+| NOTE: The mandatory HTTP error status codes for the DELETE method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                 |
+
+#### 7.5.1.2.3.4 Resource Custom Operations
+
+None.
+
+### 7.5.1.3 Notifications
+
+#### 7.5.1.3.1 General
+
+The delivery of notifications shall conform to clause 6.6.
+
+**Table 7.5.1.3.1-1: Notifications overview**
+
+| Notification            | Callback URI              | HTTP method or custom operation | Description (service operation)     |
+|-------------------------|---------------------------|---------------------------------|-------------------------------------|
+| SEAL Event Notification | {notificationDestination} | POST                            | Notifies subscriber of a SEAL Event |
+
+#### 7.5.1.3.2 SEAL Event Notification
+
+##### 7.5.1.3.2.1 Description
+
+SEAL Event Notification is used by the SEAL server notify a VAL server of an Event. The VAL server shall be subscribed to such SEAL Event Notifications via the Individual SEAL Events Subscription Resource.
+
+##### 7.5.1.3.2.2 Notification definition
+
+The POST method shall be used for the event notification and the callback URI shall be the one provided by the VAL server during the subscription to the event.
+
+Callback URI: {notificationDestination}
+
+This method shall support the URI query parameters specified in table 7.5.1.3.2.2-1.
+
+**Table 7.5.1.3.2.2-1: URI query parameters supported by the POST method on this resource**
+
+| Name | Data type | P | Cardinality | Description |
+|------|-----------|---|-------------|-------------|
+| n/a  |           |   |             |             |
+
+This method shall support the request data structures specified in table 7.5.1.3.2.2-2 and the response data structures and response codes specified in table 7.5.1.3.2.2-3.
+
+**Table 7.5.1.3.2.2-2: Data structures supported by the POST Request Body on this resource**
+
+| Data type             | P | Cardinality | Description                              |
+|-----------------------|---|-------------|------------------------------------------|
+| SEALEventNotification | M | 1           | Notification information of a SEAL Event |
+
+**Table 7.5.1.3.2.2-3: Data structures supported by the POST Response Body on this resource**
+
+| Data type                                                                                                                 | P | Cardinality | Response codes | Description                                      |
+|---------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------|
+| n/a                                                                                                                       |   |             | 204 No Content | The receipt of the Notification is acknowledged. |
+| NOTE: The mandatory HTTP error status codes for the POST method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                  |
+
+## 7.5.1.4 Data Model
+
+### 7.5.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API.
+
+Table 7.5.1.4.1-1 specifies the data types defined specifically for the SS\_Events API service.
+
+**Table 7.5.1.4.1-1: SS\_Events API specific Data Types**
+
+| Data type             | Section defined | Description                                                                 | Applicability |
+|-----------------------|-----------------|-----------------------------------------------------------------------------|---------------|
+| SEALEventSubscription | 7.5.1.4.2.2     | Represents an individual SEAL Event Subscription resource                   |               |
+| SEALEventNotification | 7.5.1.4.2.3     | Represents an individual SEAL Event Subscription Notification               |               |
+| EventSubscription     | 7.5.1.4.2.4     | Represents the subscription to a single SEAL event.                         |               |
+| SEALEventDetail       | 7.5.1.4.2.5     | Represents the SEAL event detail                                            |               |
+| VALGroupFilter        | 7.5.1.4.2.6     | Represents a filter of VAL group identifiers belonging to a VAL service.    |               |
+| IdentityFilter        | 7.5.1.4.2.7     | Represents a filter of VAL User / UE identities belonging to a VAL service. |               |
+| SEALEvent             | 7.5.1.4.3.3     | Represents the type of SEAL events that can be subscribed.                  |               |
+| LMInformation         | 7.5.1.4.2.8     | The location information for a VAL User ID or a VAL UE ID.                  |               |
+
+Table 7.5.1.4.1-2 specifies data types re-used by the SS\_Events API service:
+
+Table 7.5.1.4.1-2: Re-used Data Types
+
+| Data type            | Reference           | Comments                                                                                                                                                                                                                                             | Applicability |
+|----------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| ReportingInformation | 3GPP TS 29.523 [20] | Used to indicate the reporting requirement, only the following information are applicable for SEAL: <ul style="list-style-type: none"> <li>- immRep</li> <li>- notifMethod</li> <li>- maxReportNbr</li> <li>- monDur</li> <li>- repPeriod</li> </ul> |               |
+| SupportedFeatures    | 3GPP TS 29.571 [21] | Used to negotiate the applicability of optional features defined in table 7.5.1.6-1.                                                                                                                                                                 |               |
+| TestNotification     | 3GPP TS 29.122 [3]  | Following differences apply: <ul style="list-style-type: none"> <li>- The SCEF is the SEAL server; and</li> <li>- The SCS/AS is the subscribing VAL server.</li> </ul>                                                                               |               |
+| Uri                  | 3GPP TS 29.122 [3]  |                                                                                                                                                                                                                                                      |               |
+| WebsockNotifConfig   | 3GPP TS 29.122 [3]  | Following differences apply: <ul style="list-style-type: none"> <li>- The SCEF is the CAPIF core function; and</li> <li>- The SCS/AS is the Subscribing functional entity.</li> </ul>                                                                |               |
+| VALGroupDocument     | Clause 7.2.1.4.2.2  | Used to send VAL group document as part of event detail in the event notification.                                                                                                                                                                   |               |
+| ProfileDoc           | Clause 7.3.1.4.2.2  | Used to send VAL User or VAL UE profile information as part of event detail in the event notification.                                                                                                                                               |               |
+| LocationInfo         | 3GPP TS 29.122 [3]  | Location information                                                                                                                                                                                                                                 |               |
+| ValTargetUe          | 7.3.1.4.2.3         | Used to identify a VAL user ID or a VAL UE ID.                                                                                                                                                                                                       |               |
+
+## 7.5.1.4.2 Structured data types
+
+### 7.5.1.4.2.1 Introduction
+
+### 7.5.1.4.2.2 SEALEventSubscription
+
+**Table 7.5.1.4.2.2-1: Definition of type SEALEventSubscription**
+
+| Attribute name          | Data type                | P | Cardinality | Description                                                                                                                                                                                                                                     | Applicability           |
+|-------------------------|--------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
+| subscriberId            | string                   | M | 1           | String identifying the subscriber of the event.                                                                                                                                                                                                 |                         |
+| eventSubs               | array(EventSubscription) | M | 1..N        | Subscribed events.                                                                                                                                                                                                                              |                         |
+| eventReq                | ReportingInformation     | M | 1           | Represents the reporting requirements of the event subscription.                                                                                                                                                                                |                         |
+| notificationDestination | Uri                      | M | 1           | URI where the notification should be delivered to.                                                                                                                                                                                              |                         |
+| requestTestNotification | boolean                  | O | 0..1        | Set to true by Subscriber to request the SEAL server to send a test notification as defined in clause 6.6. Set to false or omitted otherwise.                                                                                                   | Notification_test_event |
+| websocketNotifConfig    | WebsocketNotifConfig     | O | 0..1        | Configuration parameters to set up notification delivery over Websocket protocol as defined in clause 6.6.                                                                                                                                      | Notification_websocket  |
+| eventDetails            | array(SEALEventDetail)   | C | 1..N        | Detailed information of individual Events. Shall only be present in the response from the server if the immediate reporting indication in the "immRep" attribute within the "eventReq" attribute is set to true, and the reports are available. |                         |
+| suppFeat                | Supported Features       | O | 0..1        | Used to negotiate the supported optional features of the API as described in clause 6.8. This attribute shall be provided in the HTTP POST request and in the response of successful resource creation.                                         |                         |
+
+### 7.5.1.4.2.3 SEALEventNotification
+
+**Table 7.5.1.4.2.3-1: Definition of type SEALEventNotification**
+
+| Attribute name | Data type              | P | Cardinality | Description                                                                                             | Applicability |
+|----------------|------------------------|---|-------------|---------------------------------------------------------------------------------------------------------|---------------|
+| subscriptionId | string                 | M | 1           | Identifier of the subscription resource to which the notification is related – SEAL resource identifier |               |
+| eventDetails   | array(SEALEventDetail) | M | 1..N        | Detailed notifications of individual Events.                                                            |               |
+
+## 7.5.1.4.2.4 EventSubscription
+
+Table 7.5.1.4.2.4-1: Definition of type EventSubscription
+
+| Attribute name | Data type             | P | Cardinality | Description                                                                                                                                                                                                                                                                      | Applicability                               |
+|----------------|-----------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|
+| eventId        | SEALEvent             | M | 1           | Subscribed event                                                                                                                                                                                                                                                                 |                                             |
+| valGroups      | array(VALGroupFilter) | C | 1..N        | Each element of the array represents the VAL group identifier(s) of a VAL service that the subscriber wants to know in the interested event.<br>This parameter shall be present only if the event subscribed is "GM_GROUP_INFO_CHANGE".                                          | GM_GroupInfoChange                          |
+| identities     | array(IdentityFilter) | C | 1..N        | Each element of the array represents the VAL User / UE IDs of a VAL service that the event subscriber wants to know in the interested event.<br>This parameter shall be present only if the event subscribed is "CM_USER_PROFILE_CHANGE" or "LM_LOCATION_INFO_CHANGE".<br>(NOTE) | CM_UserProfileChange, LM_LocationInfoChange |
+
+NOTE: The "valSvcId" attribute within IdentityFilter is not applicable for the event "LM\_LOCATION\_INFO\_CHANGE".
+
+## 7.5.1.4.2.5 SEALEventDetail
+
+Table 7.5.1.4.2.5-1: Definition of type SEALEventDetail
+
+| Attribute name    | Data type               | P | Cardinality | Description                                                                                                                                                                                                                                   | Applicability                      |
+|-------------------|-------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|
+| eventId           | SEALEvent               | M | 1           | Event that is notified                                                                                                                                                                                                                        |                                    |
+| lmInfos           | array(LMInformation)    | C | 1..N        | The location information for the interested VAL User IDs or VAL UE IDs.<br>This parameter shall be present only if the event in event notification is "LM_LOCATION_INFO_CHANGE".                                                              | LM_LocationInfoChange              |
+| valGroupDocuments | array(VALGroupDocument) | C | 1..N        | Newly created VAL group documents or the VAL groups documents with modified membership and configuration information. This parameter shall be present only if the event in event notification is "GM_GROUP_INFO_CHANGE" or "GM_GROUP_CREATE". | GM_GroupInfoChange, GM_GroupCreate |
+| profileDocs       | array(ProfileDoc)       | C | 1..N        | Updated profile information associated with VAL Users or VAL UEs.<br>This parameter shall be present only if the event in event notification is "CM_USER_PROFILE_CHANGE".                                                                     | CM_UserProfileChange               |
+
+## 7.5.1.4.2.6 VALGroupFilter
+
+Table 7.5.1.4.2.6-1: Definition of type VALGroupFilter
+
+| Attribute name | Data type     | P | Cardinality | Description                                                                            | Applicability |
+|----------------|---------------|---|-------------|----------------------------------------------------------------------------------------|---------------|
+| valSvcId       | string        | O | 0..1        | Identity of the VAL Service that the subscriber is interested in.                      |               |
+| valGrpIds      | array(string) | M | 1..N        | VAL Group identifiers that the event subscriber wants to know in the interested event. |               |
+
+## 7.5.1.4.2.7 IdentityFilter
+
+Table 7.5.1.4.2.7-1: Definition of type IdentityFilter
+
+| Attribute name | Data type          | P | Cardinality | Description                                                                                                                                                                                                   | Applicability |
+|----------------|--------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
+| valSvcId       | string             | O | 0..1        | Identity of the VAL Service that the subscriber is interested in.                                                                                                                                             |               |
+| valTgtUes      | array(ValTargetUe) | C | 1..N        | VAL User IDs or VAL UE IDs that the event subscriber wants to know in the interested event. This parameter shall be present if the event subscribed is "CM_USER_PROFILE_CHANGE" or "LM_LOCATION_INFO_CHANGE". |               |
+
+## 7.5.1.4.2.8 LMInformation
+
+Table 7.5.1.4.2.8-1: Definition of type LMInformation
+
+| Attribute name | Data type    | P | Cardinality | Description                                                                           | Applicability |
+|----------------|--------------|---|-------------|---------------------------------------------------------------------------------------|---------------|
+| valTgtUe       | ValTargetUe  | M | 1           | VAL User ID or UE ID that the event subscriber wants to know in the interested event. |               |
+| locInfo        | LocationInfo | M | 1           | The location information associated with the valTgtUe.                                |               |
+
+## 7.5.1.4.3 Simple data types and enumerations
+
+## 7.5.1.4.3.1 Introduction
+
+This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses.
+
+## 7.5.1.4.3.2 Simple data types
+
+None.
+
+## 7.5.1.4.3.3 Enumeration: SEALEvent
+
+Table 7.5.1.4.3.3-1: Enumeration SEALEvent
+
+| Enumeration value       | Description                                                                                                                | Applicability         |
+|-------------------------|----------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| LM_LOCATION_INFO_CHANGE | Events related to the location information of VAL Users or VAL UEs from the Location Management Server.                    | LM_LocationInfoChange |
+| GM_GROUP_INFO_CHANGE    | Events related to the modification of VAL group membership and configuration information from the Group Management Server. | GM_GroupInfoChange    |
+| CM_USER_PROFILE_CHANGE  | Events related to update of user profile information from the Configuration Management Server.                             | CM_UserProfileChange  |
+| GM_GROUP_CREATE         | Events related to creation of new VAL groups from the Group Management Server.                                             | GM_GroupCreate        |
+
+## 7.5.1.5 Error Handling
+
+General error responses are defined in clause 6.7.
+
+## 7.5.1.6 Feature Negotiation
+
+General feature negotiation procedures are defined in clause 6.8. Table 7.5.1.6-1 lists the supported features for SS\_Events API.
+
+Table 7.5.1.6-1: Supported Features
+
+| Feature number | Feature Name            | Description                                                                                                                                                          |
+|----------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1              | Notification_test_event | Testing of notification connection is supported according to clause 6.6.                                                                                             |
+| 2              | Notification_websocket  | The delivery of notifications over Websocket is supported according to clause 6.6. This feature requires that the Notification_test_event feature is also supported. |
+| 3              | LM_LocationInfoChange   | This feature supports the location information change event.                                                                                                         |
+| 4              | GM_GroupInfoChange      | This feature supports the group information change event.                                                                                                            |
+| 5              | CM_UserProfileChange    | This feature supports the user profile change event.                                                                                                                 |
+| 6              | GM_GroupCreate          | This feature supports the group creation event.                                                                                                                      |
+
+## 7.6 Key management APIs
+
+### 7.6.1 SS\_KeyInfoRetrieval API
+
+#### 7.6.1.1 API URI
+
+The request URI used in each HTTP request from the VAL server towards the Key management server shall have the structure as defined in clause 6.5 with the following clarifications:
+
+- The <apiName> shall be "ss-kir".
+- The <apiVersion> shall be "v1".
+- The <apiSpecificSuffixes> shall be set as described in clause 7.6.1.2.
+
+#### 7.6.1.2 Resources
+
+##### 7.6.1.2.1 Overview
+
+![Diagram showing the resource URI structure for the SS_KeyInfoRetrieval API. The root URI is {apiRoot}/ss-kir/<apiVersion>. A line branches down to a box containing /key-records. From this box, another line branches down to /{keyRecordId}.](294444660b1376c49aeca748b8184e77_img.jpg)
+
+```
+
+graph TD
+    Root["{apiRoot}/ss-kir/<apiVersion>"] --> KeyRecords["/key-records"]
+    KeyRecords --> KeyRecordId["/{keyRecordId}"]
+  
+```
+
+Diagram showing the resource URI structure for the SS\_KeyInfoRetrieval API. The root URI is {apiRoot}/ss-kir/. A line branches down to a box containing /key-records. From this box, another line branches down to /{keyRecordId}.
+
+Figure 7.6.1.2.1-1: Resource URI structure of the SS\_KeyInfoRetrieval API
+
+Table 7.6.1.2.1-1 provides an overview of the resources and applicable HTTP methods.
+
+Table 7.6.1.2.1-1: Resources and methods overview
+
+| Resource name | Resource URI | HTTP method or custom operation | Description                                                                                 |
+|---------------|--------------|---------------------------------|---------------------------------------------------------------------------------------------|
+| Key records   | /key-records | GET                             | Retrieve key management information uniquely applicable to VAL service, VAL user or VAL UE. |
+
+### 7.6.1.2.2 Resource: Key Records
+
+#### 7.6.1.2.2.1 Description
+
+The Key Records resource represents the key management information of all VAL services that are created at a given key management server.
+
+#### 7.6.1.2.2.2 Resource Definition
+
+Resource URI: {apiRoot}/ss-kir/<apiVersion>/key-records
+
+This resource shall support the resource URI variables defined in the table 7.6.1.2.2.2-1.
+
+**Table 7.6.1.2.2.2-1: Resource URI variables for this resource**
+
+| Name       | Data Type | Definition         |
+|------------|-----------|--------------------|
+| apiRoot    | string    | See clause 6.5     |
+| apiVersion | string    | See clause 7.6.1.1 |
+
+#### 7.6.1.2.2.3 Resource Standard Methods
+
+##### 7.6.1.2.2.3.1 GET
+
+This operation retrieves VAL service key management information satisfying the filter criteria. This method shall support the URI query parameters specified in table 7.6.1.2.2.3.1-1.
+
+**Table 7.6.1.2.2.3.1-1: URI query parameters supported by the GET method on this resource**
+
+| Name           | Data type   | P | Cardinality | Description                         |
+|----------------|-------------|---|-------------|-------------------------------------|
+| val-tgt-ue     | ValTargetUe | O | 0..1        | Identifying a VAL user or a VAL UE. |
+| val-service-id | string      | M | 1           | String identifying a VAL service.   |
+
+This method shall support the request data structures specified in table 7.6.1.2.2.3.2-2 and the response data structures and response codes specified in table 7.6.1.2.2.3.2 -3.
+
+**Table 7.6.1.2.2.3.2-2: Data structures supported by the GET Request Body on this resource**
+
+| Data type | P | Cardinality | Description |
+|-----------|---|-------------|-------------|
+| n/a       |   |             |             |
+
+**Table 7.6.1.2.2.3.2-3: Data structures supported by the GET Response Body on this resource**
+
+| Data type                                                                                                                | P | Cardinality | Response codes | Description                                                                                                                                                                           |
+|--------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| ValKeyInfo                                                                                                               | M | 1           | 200 OK         | Key management information specific to VAL service, VAL user or VAL UE. This response shall include key management information matching the query parameters provided in the request. |
+| NOTE: The mandatory HTTP error status codes for the GET method listed in table 5.2.6-1 of 3GPP TS 29.122 [3] also apply. |   |             |                |                                                                                                                                                                                       |
+
+#### 7.6.1.2.2.4 Resource Custom Operations
+
+None.
+
+### 7.6.1.3 Notifications
+
+None.
+
+## 7.6.1.4 Data Model
+
+### 7.6.1.4.1 General
+
+This clause specifies the application data model supported by the API. Data types listed in clause 6.2 apply to this API.
+
+Table 7.6.1.4.1-1 specifies the data types defined specifically for the SS\_KeyInfoRetrieval API service.
+
+**Table 7.6.1.4.1-1: SS\_KeyInfoRetrieval API specific Data Types**
+
+| Data type  | Section defined | Description                                                                | Applicability |
+|------------|-----------------|----------------------------------------------------------------------------|---------------|
+| ValKeyInfo | 7.6.1.4.2.3     | Key management information associated with VAL server, VAL user or VAL UE. |               |
+
+Table 7.6.1.4.1-2 specifies data types re-used by the SS\_KeyInfoRetrieval API service.
+
+**Table 7.6.1.4.1-2: Re-used Data Types**
+
+| Data type   | Reference          | Comments                                                                              | Applicability |
+|-------------|--------------------|---------------------------------------------------------------------------------------|---------------|
+| ValTargetUe | Clause 7.3.1.4.2.3 | Used to identify a VAL User ID or VAL UE ID applicable to key management information. |               |
+
+### 7.6.1.4.2 Structured Data Types
+
+#### 7.6.1.4.2.1 Introduction
+
+#### 7.6.1.4.2.2 ValKeyInfo
+
+**Table 7.6.1.4.2.3-1: Definition of type ValKeyInfo**
+
+| Attribute name | Data type   | P | Cardinality | Description                                                                                                    | Applicability |
+|----------------|-------------|---|-------------|----------------------------------------------------------------------------------------------------------------|---------------|
+| userUri        | Uri         | M | 1           | URI of the user for which the response is intended.                                                            |               |
+| skmsId         | string      | O | 0..1        | String identifying the SEAL key management server, sending the response.                                       |               |
+| valService     | string      | M | 1           | String identifying the VAL service. This attribute shall be same as in the HTTP GET request.                   |               |
+| valTgtUe       | ValTargetUe | O | 0..1        | String identifying a VAL user or VAL UE. This value depends on the value that was in the HTTP GET request.     |               |
+| keyInfo        | string      | M | 1           | Key management information uniquely applicable to the requested VAL service, VAL user or VAL UE or VAL client. |               |
+
+### 7.6.1.4.3 Simple data types and enumerations
+
+None.
+
+## 7.6.1.5 Error Handling
+
+General error responses are defined in clause 6.7.
+
+## 7.6.1.6 Feature Negotiation
+
+General feature negotiation procedures are defined in clause 6.8.
+
+Table 7.6.1.6-1: Supported Features
+
+| Feature number | Feature Name | Description |
+|----------------|--------------|-------------|
+|                |              |             |
+
+## 8 Using Common API Framework
+
+### 8.1 General
+
+When CAPIF is used with a SEAL service, the SEAL server shall support the following as defined in 3GPP TS 29.222 [16]:
+
+- the API exposing function and related APIs over CAPIF-2/2e and CAPIF-3/3e reference points;
+- the API publishing function and related APIs over CAPIF-4/4e reference point;
+- the API management function and related APIs over CAPIF-5/5e reference point; and
+- at least one of the security methods for authentication and authorization, and related security mechanisms.
+
+In a centralized deployment as defined in 3GPP TS 23.222 [17], where the CAPIF core function and API provider domain functions are co-located, the interactions between the CAPIF core function and API provider domain functions may be independent of CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e reference points.
+
+When CAPIF is used with a SEAL service, the SEAL server shall register all the features for northbound APIs in the CAPIF Core Function.
+
+### 8.2 Security
+
+When CAPIF is used for external exposure, before invoking the API exposed by the SEAL server, the VAL server as API invoker shall negotiate the security method (PKI, TLS-PSK or OAUTH2) with CAPIF core function and ensure the SEAL server has enough credential to authenticate the VAL server (see 3GPP TS 29.222 [16], clause 5.6.2.2 and clause 6.2.2.2).
+
+If PKI or TLS-PSK is used as the selected security method between the VAL server and the SEAL server, upon API invocation, the SEAL server shall retrieve the authorization information from the CAPIF core function as described in 3GPP TS 29.222 [16], clause 5.6.2.4.
+
+As indicated in 3GPP TS 33.122 [18], the access to the SEAL APIs may be authorized by means of the OAuth2 protocol (see IETF RFC 6749 [19]), using the "Client Credentials" authorization grant, where the CAPIF core function (see 3GPP TS 29.222 [16]) plays the role of the authorization server.
+
+NOTE 1: In this release, only "Client Credentials" authorization grant is supported.
+
+If OAuth2 is used as the selected security method between the VAL server and the SEAL server, the VAL server, prior to consuming services offered by the SEAL APIs, shall obtain a "token" from the authorization server, by invoking the Obtain\_Authorization service, as described in 3GPP TS 29.222 [16], clause 5.6.2.3.2.
+
+The SEAL APIs do not define any scopes for OAuth2 authorization. It is the SEAL server responsibility to check whether the VAL server is authorized to use an API based on the "token". Once the SEAL server verifies the "token", it shall check whether the SEAL server identifier in the "token" matches its own published identifier, and whether the API name in the "token" matches its own published API name. If those checks are passed, the VAL server has full authority to access any resource or operation for the invoked API
+
+NOTE 2: For aforementioned security methods, the SEAL server needs to apply admission control according to access control policies after performing the authorization checks.
+
+---
+
+## 9 Security
+
+### 9.1 General
+
+The security aspects of SEAL reference points are specified in 3GPP TS 33.434 [26].
+
+### 9.2 SEAL-S security
+
+As specified in clause 5.1.1.8 of 3GPP TS 33.434 [26], the protection of SEAL-S reference point shall be supported according to NDS/IP as specified in 3GPP TS 33.210 [25].
+
+When CAPIF is used, the security mechanisms described in clause 8.2 shall be applied.
+
+# Annex A (normative): OpenAPI specification
+
+## A.1 General
+
+This annex is based on the OpenAPI 3.0.0 specification [15] and provides corresponding representations of all APIs defined in the present specification in YAML format.
+
+This Annex shall take precedence when being discrepant to other parts of the specification with respect to the encoding of information elements and methods within the API.
+
+NOTE: The semantics and procedures, as well as conditions, e.g. for the applicability and allowed combinations of attributes or values, not expressed in the OpenAPI definitions but defined in other parts of the specification also apply.
+
+Informative copies of the OpenAPI specification file contained in this 3GPP Technical Specification are available on a Git-based repository that uses the GitLab software version control system (see clause 5B of the 3GPP TR 21.900 [24] and clause 5.3.1 of the 3GPP TS 29.501 [14] for further information).
+
+## A.2 SS\_LocationReporting API
+
+```
+openapi: 3.0.0
+info:
+  title: SS_LocationReporting
+  description: |
+    API for SEAL Location Reporting Configuration.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+  version: "1.0.0"
+externalDocs:
+  description: 3GPP TS 29.549 V16.0.0 Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+servers:
+  - url: '{apiRoot}/ss-lr/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 6.5 of 3GPP TS 29.549
+paths:
+  /trigger-configurations:
+    post:
+      description: Creates a new location reporting configuration.
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LocationReportConfiguration'
+      responses:
+        '201':
+          description: location reporting configuration resource is created successfully.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/LocationReportConfiguration'
+          headers:
+            Location:
+              description: 'Contains the URI of the newly created resource'
+              required: true
+              schema:
+                type: string
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+```
+
+```
+'403':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+'404':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+'411':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+'413':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+'415':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+'429':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+'500':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+'503':
+  $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+default:
+  $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+/trigger-configurations/{configurationId}:
+  get:
+    description: Retrieves an individual SEAL location reporting configuration information
+    parameters:
+    - name: configurationId
+      in: path
+      description: String identifying an individual configuration resource
+      required: true
+      schema:
+        type: string
+    responses:
+      '200':
+        description: The location reporting configuration information.
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LocationReportConfiguration'
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '406':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+  put:
+    description: Updates an individual SEAL location reporting configuration.
+    parameters:
+    - name: configurationId
+      in: path
+      description: String identifying an individual configuration resource
+      required: true
+      schema:
+        type: string
+    requestBody:
+      description: configuration information to be updated in location management server.
+      required: true
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/LocationReportConfiguration'
+    responses:
+      '200':
+        description: the configuration is updated successfully
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/LocationReportConfiguration'
+      '400':
+```
+
+```
+      $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '411':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+      '413':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+      '415':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+delete:
+  description: Deletes an individual SEAL location reporting configuration.
+  parameters:
+  - name: configurationId
+    in: path
+    description: String identifying an individual configuration resource
+    required: true
+    schema:
+      type: string
+  responses:
+    '204':
+      description: The individual configuration matching configurationId is deleted.
+    '400':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+    '429':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{tokenUrl}'
+          scopes: {}
+
+schemas:
+  LocationReportConfiguration:
+    type: object
+    properties:
+      valServerId:
+        type: string
+      valTgtUe:
+        $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+      immRep:
+        type: boolean
+      monDur:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+      repPeriod:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'
+      accuracy:
+        $ref: 'TS29122_MonitoringEvent.yaml#/components/schemas/Accuracy'
+      suppFeat:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+    required:
+```
+
+- valServerId
+- valTgtUe
+
+## A.3 SS\_GroupManagement API
+
+```
+
+openapi: 3.0.0
+info:
+  title: SS_GroupManagement
+  description: |
+    API for SEAL Group management.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+  version: "1.0.1"
+externalDocs:
+  description: 3GPP TS 29.549 V16.2.0 Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+servers:
+  - url: '{apiRoot}/ss-gm/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 6.5 of 3GPP TS 29.549
+paths:
+  /group-documents:
+    post:
+      description: Creates a new VAL group document.
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/VALGroupDocument'
+      responses:
+        '201':
+          description: VAL group created successfully.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/VALGroupDocument'
+          headers:
+            Location:
+              description: 'Contains the URI of the newly created resource'
+              required: true
+              schema:
+                type: string
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '411':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+        '413':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+        '415':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+        '503':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+        default:
+          $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+    get:
+      description: Retrieves VAL group documents satisfying filter criteria
+      parameters:
+        - name: val-group-id
+
+```
+
+```
+
+      in: query
+      description: String identifying the VAL group.
+      schema:
+        type: string
+    - name: val-service-id
+      in: query
+      description: String identifying the Val service.
+      schema:
+        type: string
+  responses:
+    '200':
+      description: List of VAL group documents matching the query parameters in the request.
+      content:
+        application/json:
+          schema:
+            type: array
+            items:
+              $ref: '#/components/schemas/VALGroupDocument'
+            minItems: 0
+    '400':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+    '406':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+    '429':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+/group-documents/{groupDocId}:
+  get:
+    description: Retrieves VAL group information satisfying filter criteria
+    parameters:
+    - name: groupDocId
+      in: path
+      description: String identifying an individual VAL group document resource
+      required: true
+      schema:
+        type: string
+    - name: group-members
+      in: query
+      description: When set to true indicates the group management server to send the members
+list information of the VAL group.
+      schema:
+        type: boolean
+    - name: group-configuration
+      in: query
+      description: When set to true indicates the group management server to send the group
+configuration information of the VAL group.
+      schema:
+        type: boolean
+    responses:
+      '200':
+        description: The VAL group information based on the request from the VAL server. Includes
+VAL group members list if group-members flag is set to true in the request, VAL group configuration
+information if the group-configuration flag is set to true in the request, VAL group identifier,
+whole VAL group document resource if both group-members and group-configuration flags are
+omitted/set to false in the request.
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/VALGroupDocument'
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+
+```
+
+```
+$ref: 'TS29122_CommonData.yaml#/components/responses/404'
+'406':
+$ref: 'TS29122_CommonData.yaml#/components/responses/404'
+'429':
+$ref: 'TS29122_CommonData.yaml#/components/responses/429'
+'500':
+$ref: 'TS29122_CommonData.yaml#/components/responses/500'
+'503':
+$ref: 'TS29122_CommonData.yaml#/components/responses/503'
+default:
+$ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+put:
+description: Updates an individual VAL group document.
+parameters:
+- name: groupDocId
+  in: path
+  description: String identifying an individual VAL group document resource
+  required: true
+  schema:
+    type: string
+requestBody:
+description: VAL group document to be updated in Group management server.
+required: true
+content:
+  application/json:
+    schema:
+      $ref: '#/components/schemas/VALGroupDocument'
+responses:
+'200':
+  description: VAL group document updated successfully
+  content:
+    application/json:
+      schema:
+        $ref: '#/components/schemas/VALGroupDocument'
+'400':
+$ref: 'TS29122_CommonData.yaml#/components/responses/400'
+'401':
+$ref: 'TS29122_CommonData.yaml#/components/responses/401'
+'403':
+$ref: 'TS29122_CommonData.yaml#/components/responses/403'
+'404':
+$ref: 'TS29122_CommonData.yaml#/components/responses/404'
+'411':
+$ref: 'TS29122_CommonData.yaml#/components/responses/411'
+'413':
+$ref: 'TS29122_CommonData.yaml#/components/responses/413'
+'415':
+$ref: 'TS29122_CommonData.yaml#/components/responses/415'
+'429':
+$ref: 'TS29122_CommonData.yaml#/components/responses/429'
+'500':
+$ref: 'TS29122_CommonData.yaml#/components/responses/500'
+'503':
+$ref: 'TS29122_CommonData.yaml#/components/responses/503'
+default:
+$ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+delete:
+description: Deletes a VAL Group.
+parameters:
+- name: groupDocId
+  in: path
+  description: String identifying an individual VAL group document resource
+  required: true
+  schema:
+    type: string
+responses:
+'204':
+  description: The individual VAL group matching groupDocId was deleted.
+'400':
+$ref: 'TS29122_CommonData.yaml#/components/responses/400'
+'401':
+$ref: 'TS29122_CommonData.yaml#/components/responses/401'
+'403':
+$ref: 'TS29122_CommonData.yaml#/components/responses/403'
+'404':
+$ref: 'TS29122_CommonData.yaml#/components/responses/404'
+'429':
+```
+
+```
+
+      $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+          tokenUrl: '{tokenUrl}'
+          scopes: {}
+  schemas:
+    VALGroupDocument:
+      type: object
+      properties:
+        valGroupId:
+          type: string
+          description: The VAL group identity.
+        grpDesc:
+          type: string
+          description: The text description of the VAL group.
+        members:
+          type: array
+          description: The list of VAL User IDs or VAL UE IDs, which are members of the VAL group.
+          items:
+            $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+          minItems: 1
+        valGrpConf:
+          type: string
+          description: Configuration data for the VAL group.
+        valServiceIds:
+          type: array
+          description: The list of VAL services enabled on the group.
+          items:
+            type: string
+          minItems: 1
+        suppFeat:
+          $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+        resUri:
+          $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri'
+        locInfo:
+          $ref: 'TS29122_MonitoringEvent.yaml#/components/schemas/LocationInfo'
+        addLocInfo:
+          $ref: 'TS29122_CommonData.yaml#/components/schemas/LocationArea5G'
+      required:
+        - valGroupId
+
+```
+
+## A.4 SS\_UserProfileRetrieval API
+
+```
+
+openapi: 3.0.0
+info:
+  title: SS_UserProfileRetrieval
+  description: |
+    API for SEAL User Profile Retrieval.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+  version: "1.0.0"
+externalDocs:
+  description: 3GPP TS 29.549 V16.0.0 Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+servers:
+  - url: '{apiRoot}/ss-upr/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 6.5 of 3GPP TS 29.549
+paths:
+
+```
+
+```
+/val-services:
+  get:
+    description: Retrieve VAL User or VAL UE profile information.
+    parameters:
+    - name: val-service-id
+      in: query
+      description: String identifying an individual VAL service
+      required: false
+      schema:
+        type: string
+    - name: val-tgt-ue
+      in: query
+      description: Identifying a VAL target UE.
+      required: true
+      schema:
+        $ref: '#/components/schemas/ValTargetUe'
+    responses:
+      '200':
+        description: The Profile information of the VAL User or VAL UE.
+        content:
+          application/json:
+            schema:
+              type: array
+              items:
+                $ref: '#/components/schemas/ProfileDoc'
+              minItems: 0
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '406':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+  components:
+    securitySchemes:
+      oAuth2ClientCredentials:
+        type: oauth2
+        flows:
+          clientCredentials:
+            tokenUrl: '{tokenUrl}'
+            scopes: {}
+  schemas:
+    ProfileDoc:
+      type: object
+      properties:
+        profileInformation:
+          type: string
+          description: Profile information associated with the valUserId or valUeId.
+        valTgtUe:
+          $ref: '#/components/schemas/ValTargetUe'
+      required:
+      - profileInformation
+      - valTgtUe
+    ValTargetUe:
+      type: object
+      properties:
+        valUserId:
+          type: string
+          description: Unique identifier of a VAL user.
+        valUeId:
+          type: string
+          description: Unique identifier of a VAL UE.
+      oneOf:
+      - required: [valUserId]
+      - required: [valUeId]
+```
+
+## A.5 SS\_NetworkResourceAdaptation API
+
+```
+
+openapi: 3.0.0
+info:
+  version: 1.0.1
+  title: SS_NetworkResourceAdaptation
+  description: |
+    SS Network Resource Adaptation Service.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+
+externalDocs:
+  description: 3GPP TS 29.549 V16.1.0; Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+
+servers:
+  - url: '{apiRoot}/ss-nra/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 4.4 of 3GPP TS 29.501
+
+paths:
+  /multicast-subscriptions:
+    post:
+      summary: Creates a new Individual Multicast Subscription resource
+      operationId: CreateMulticastSubscription
+      tags:
+        - Multicast Subscriptions (Collection)
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MulticastSubscription'
+      responses:
+        '201':
+          description: Success
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/MulticastSubscription'
+          headers:
+            Location:
+              description: 'Contains the URI of the created individual multicast subscription
+resource'
+              required: true
+              schema:
+                type: string
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '411':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+        '413':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+        '415':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+        '503':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+        default:
+          $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+      callbacks:
+
+```
+
+```
+UserPlaneNotification:
+  { $request.body#/notifUri }':
+  post:
+    requestBody:
+      required: true
+      content:
+        application/json:
+          schema:
+            $ref: '#/components/schemas/UserPlaneNotification'
+  responses:
+    '204':
+      description: No Content, Notification was successfull
+    '400':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+    '411':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+    '413':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+    '415':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+    '429':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+/multicast-subscriptions/{multiSubId}:
+  get:
+    summary: "Reads an existing Individual Multicast Subscription"
+    operationId: GetMulticastSubscription
+    tags:
+      - Individual Multicast Subscription (Document)
+    parameters:
+      - name: multiSubId
+        in: path
+        description: Multicast Subscription ID
+        required: true
+        schema:
+          type: string
+    responses:
+      '200':
+        description: OK. Resource representation is returned
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MulticastSubscription'
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '406':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/406'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+  delete:
+    summary: "Delete an existing Individual Multicast Subscription"
+    operationId: DeleteMulticastSubscription
+    tags:
+      - Individual Multicast Subscription (Document)
+    parameters:
+```
+
+```
+
+      - name: multiSubId
+        in: path
+        description: Multicast Subscription ID
+        required: true
+        schema:
+          type: string
+      responses:
+        '204':
+          description: No Content. Resource was successfully deleted
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+        '503':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+        default:
+          $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+  /unicast-subscriptions:
+    post:
+      summary: Creates a new Individual Unicast Subscription resource
+      operationId: CreateUnicastSubscription
+      tags:
+        - Unicast Subscriptions (Collection)
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/UnicastSubscription'
+      responses:
+        '201':
+          description: Success
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/UnicastSubscription'
+          headers:
+            Location:
+              description: 'Contains the URI of the created individual unicast subscription resource'
+              required: true
+              schema:
+                type: string
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '411':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+        '413':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+        '415':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+        '503':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+        default:
+          $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+    callbacks:
+      UserPlaneNotification:
+        '{$request.body#/notifUri}':
+          post:
+            requestBody:
+
+```
+
+```
+    required: true
+    content:
+      application/json:
+        schema:
+          $ref: '#/components/schemas/UserPlaneNotification'
+  responses:
+    '204':
+      description: No Content, Notification was successfull
+    '400':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+    '401':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+    '403':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+    '404':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+    '411':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+    '413':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+    '415':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+    '429':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+    '500':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+    '503':
+      $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+    default:
+      $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+/unicast-subscriptions/{uniSubId}:
+  get:
+    summary: "Reads an existing Individual Unicast Subscription"
+    operationId: GetUnicastSubscription
+    tags:
+      - Individual Unicast Subscription (Document)
+    parameters:
+      - name: uniSubId
+        in: path
+        description: Unicast Subscription ID
+        required: true
+        schema:
+          type: string
+    responses:
+      '200':
+        description: OK. Resource representation is returned
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/UnicastSubscription'
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '406':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/406'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+  delete:
+    summary: "Delete an existing Individual Unicast Subscription"
+    operationId: DeleteUnicastSubscription
+    tags:
+      - Individual Unicast Subscription (Document)
+    parameters:
+      - name: uniSubId
+        in: path
+        description: Unicast Subscription ID
+        required: true
+```
+
+```
+    schema:
+      type: string
+    responses:
+      '204':
+        description: No Content. Resource was successfully deleted
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+    components:
+      securitySchemes:
+        oAuth2ClientCredentials:
+          type: oauth2
+          flows:
+            clientCredentials:
+              tokenUrl: '{tokenUrl}'
+              scopes: {}
+
+    schemas:
+      MulticastSubscription:
+        type: object
+        properties:
+          valGroupId:
+            type: string
+          anncMode:
+            $ref: '#/components/schemas/ServiceAnnouncementMode'
+          multiQosReq:
+            type: string
+          locArea:
+            $ref: 'TS29122_GMDviaMBMSbyMB2.yaml#/components/schemas/MbmsLocArea'
+          duration:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+          tmgi:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Uint32'
+          notifUri:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+          reqTestNotif:
+            type: boolean
+          wsNotifCfg:
+            $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig'
+          suppFeat:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+          upIpv4Addr:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr'
+          upIpv6Addr:
+            $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr'
+          upPortNum:
+            $ref: 'TS29122_CommonData.yaml#/components/schemas/Port'
+          radioFreqs:
+            type: array
+            items:
+              $ref: 'TS29571_CommonData.yaml#/components/schemas/Uint32'
+            minItems: 1
+        required:
+          - valGroupId
+          - anncMode
+          - multiQosReq
+          - notifUri
+      UnicastSubscription:
+        type: object
+        properties:
+          valTgtUe:
+            $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+          uniQosReq:
+            type: string
+          duration:
+```
+
+```
+
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+    notifUri:
+    $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+    reqTestNotif:
+      type: boolean
+    wsNotifCfg:
+      $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig'
+    suppFeat:
+      $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+    required:
+    - valTgtUe
+    - notifUri
+  UserPlaneNotification:
+    type: object
+    properties:
+      notifId:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri'
+      eventNotifs:
+        type: array
+        items:
+          $ref: '#/components/schemas/NrmEventNotification'
+        minItems: 1
+    required:
+    - notifId
+    - eventNotifs
+  NrmEventNotification:
+    type: object
+    properties:
+      event:
+        $ref: '#/components/schemas/NrmEvent'
+      ts:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'
+      deliveryMode:
+        $ref: '#/components/schemas/DeliveryMode'
+      streamIds:
+        type: array
+        items:
+          type: string
+        minItems: 1
+    required:
+    - event
+    - ts
+
+```
+
+#### # Simple data types and Enumerations
+
+```
+
+ServiceAnnouncementMode:
+  anyOf:
+  - type: string
+    enum:
+    - NRM
+    - VAL
+  - type: string
+    description: >
+      This string provides forward-compatibility with future
+      extensions to the enumeration but is not used to encode
+      content defined in the present version of this API.
+  description: >
+    Possible values are
+    - NRM: NRM server performs the service announcement.
+    - VAL: VAL server performs the service announcement.
+DeliveryMode:
+  anyOf:
+  - type: string
+    enum:
+    - UNICAST
+    - MULTICAST
+  - type: string
+    description: >
+      This string provides forward-compatibility with future
+      extensions to the enumeration but is not used to encode
+      content defined in the present version of this API.
+  description: >
+    Possible values are
+    - UNICAST: Unicast delivery.
+    - MULTICAST: Multicast delivery.
+NrmEvent:
+  anyOf:
+
+```
+
+```
+
+- type: string
+enum:
+- UP_DELIVERY_MODE
+- type: string
+description: >
+  This string provides forward-compatibility with future
+  extensions to the enumeration but is not used to encode
+  content defined in the present version of this API.
+description: >
+  Possible values are
+- UP_DELIVERY_MODE: User Plane delivery mode.
+
+```
+
+## A.6 SS\_Events API
+
+```
+
+openapi: 3.0.0
+info:
+  title: SS_Events
+  description: |
+    API for SEAL Events management.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+  version: "1.0.1"
+externalDocs:
+  description: 3GPP TS 29.549 V16.2.0 Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+security:
+- {}
+- oAuth2ClientCredentials: []
+servers:
+- url: '{apiRoot}/ss-events/v1'
+  variables:
+    apiRoot:
+      default: https://example.com
+      description: apiRoot as defined in clause 6.5 of 3GPP TS 29.549
+paths:
+  /subscriptions:
+    post:
+      description: Creates a new individual SEAL Event Subscription.
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SEALEventSubscription'
+      callbacks:
+        notificationDestination:
+          '{request.body#/notificationDestination}':
+            post:
+              requestBody: # contents of the callback message
+                required: true
+                content:
+                  application/json:
+                    schema:
+                      $ref: '#/components/schemas/SEALEventNotification'
+      responses:
+        '204':
+          description: No Content (successful notification)
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '411':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+        '413':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+        '415':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+
+```
+
+```
+
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+responses:
+  '201':
+    description: SEAL Events subscription resource created successfully.
+    content:
+      application/json:
+        schema:
+          $ref: '#/components/schemas/SEALEventSubscription'
+    headers:
+      Location:
+        description: 'Contains the URI of the newly created resource'
+        required: true
+        schema:
+          type: string
+  '400':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+  '401':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+  '403':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+  '404':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+  '411':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/411'
+  '413':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/413'
+  '415':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/415'
+  '429':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+  '500':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+  '503':
+    $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+  default:
+    $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+/subscriptions/{subscriptionId}:
+  delete:
+    description: Deletes an individual SEAL Event Subscription.
+    parameters:
+      - name: subscriptionId
+        in: path
+        description: Identifier of an individual Events Subscription
+        required: true
+        schema:
+          type: string
+    responses:
+      '204':
+        description: The individual SEAL Events Subscription matching the subscriptionId is
+deleted.
+      '400':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+      '401':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+      '403':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+      '404':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+      '429':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+      '500':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+      '503':
+        $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+      default:
+        $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+      flows:
+        clientCredentials:
+```
+
+```
+    tokenUrl: '{tokenUrl}'
+    scopes: {}
+schemas:
+  SEALEventSubscription:
+    type: object
+    properties:
+      subscriberId:
+        type: string
+        description: String identifying the subscriber of the event.
+      eventSubs:
+        type: array
+        items:
+          $ref: '#/components/schemas/EventSubscription'
+        minItems: 1
+        description: Subscribed events.
+      eventReq:
+        $ref: 'TS29523_Npcf_EventExposure.yaml#/components/schemas/ReportingInformation'
+      notificationDestination:
+        $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri'
+      requestTestNotification:
+        type: boolean
+        description: Set to true by Subscriber to request the SEAL server to send a test
+notification. Set to false or omitted otherwise.
+      websocketNotifConfig:
+        $ref: 'TS29122_CommonData.yaml#/components/schemas/WebsockNotifConfig'
+      eventDetails:
+        type: array
+        items:
+          $ref: '#/components/schemas/SEALEventDetail'
+        minItems: 1
+      suppFeat:
+        $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures'
+    required:
+      - subscriberId
+      - eventSubs
+      - eventReq
+      - notificationDestination
+  SEALEventNotification:
+    type: object
+    properties:
+      subscriptionId:
+        type: string
+        description: Identifier of the subscription resource.
+      eventDetails:
+        type: array
+        items:
+          $ref: '#/components/schemas/SEALEventDetail'
+        minItems: 1
+        description: Detailed notifications of individual events.
+    required:
+      - subscriptionId
+      - eventDetails
+  EventSubscription:
+    type: object
+    properties:
+      eventId:
+        $ref: '#/components/schemas/SEALEvent'
+      valGroups:
+        type: array
+        items:
+          $ref: '#/components/schemas/VALGroupFilter'
+        minItems: 1
+        description: Each element of the array represents the VAL group identifier(s) of a VAL
+service that the subscriber wants to know in the interested event.
+      identities:
+        type: array
+        items:
+          $ref: '#/components/schemas/IdentityFilter'
+        minItems: 1
+        description: Each element of the array represents the VAL User / UE IDs of a VAL service
+that the event subscriber wants to know in the interested event.
+    required:
+      - eventId
+  SEALEventDetail:
+    type: object
+    properties:
+      eventId:
+        $ref: '#/components/schemas/SEALEvent'
+```
+
+```
+lmInfos:
+  type: array
+  items:
+    $ref: '#/components/schemas/LMInformation'
+  minItems: 1
+valGroupDocuments:
+  type: array
+  items:
+    $ref: 'TS29549_SS_GroupManagement.yaml#/components/schemas/VALGroupDocument'
+  minItems: 1
+  description: The VAL groups documents with modified membership and configuration
+information.
+profileDocs:
+  type: array
+  items:
+    $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ProfileDoc'
+  minItems: 1
+  description: Updated profile information associated with VAL Users or VAL UEs.
+required:
+- eventId
+VALGroupFilter:
+  type: object
+  properties:
+    valSvcId:
+      type: string
+      description: Identity of the VAL service
+    valGrpIds:
+      type: array
+      items:
+        type: string
+      minItems: 1
+      description: VAL group identifiers that event subscriber wants to know in the interested
+event.
+required:
+- valGrpIds
+IdentityFilter:
+  type: object
+  properties:
+    valSvcId:
+      type: string
+      description: Identity of the VAL service
+    valTgtUes:
+      type: array
+      items:
+        $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+      minItems: 1
+      description: VAL User IDs or VAL UE IDs that the event subscriber wants to know in the
+interested event.
+LMInformation:
+  type: object
+  properties:
+    valTgtUe:
+      $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+    locInfo:
+      $ref: 'TS29122_MonitoringEvent.yaml#/components/schemas/LocationInfo'
+required:
+- locInfo
+- valTgtUe
+SEALEvent:
+  anyOf:
+  - type: string
+    enum:
+    - LM_LOCATION_INFO_CHANGE
+    - GM_GROUP_INFO_CHANGE
+    - CM_USER_PROFILE_CHANGE
+    - GM_GROUP_CREATE
+  - type: string
+    description: >
+      This string provides forward-compatibility with future
+      extensions to the enumeration but is not used to encode
+      content defined in the present version of this API.
+    description: >
+      Possible values are
+    - LM_LOCATION_INFO_CHANGE: Events related to the location information of VAL Users or VAL
+UEs from the Location Management Server.
+    - GM_GROUP_INFO_CHANGE: Events related to the modification of VAL group membership and
+configuration information from the Group Management Server.
+```
+
+- CM\_USER\_PROFILE\_CHANGE: Events related to update of user profile information from the Configuration Management Server.
+- GM\_GROUP\_CREATE: Events related to creation of new VAL groups from the Group Management Server.
+
+## A.7 SS\_KeyInfoRetrieval API
+
+```
+
+openapi: 3.0.0
+info:
+  title: SS_KeyInfoRetrieval
+  description: |
+    API for SEAL Key Information Retrieval.
+    © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
+    All rights reserved.
+  version: "1.0.1"
+externalDocs:
+  description: 3GPP TS 29.549 V16.1.0 Service Enabler Architecture Layer for Verticals (SEAL);
+    Application Programming Interface (API) specification; Stage 3.
+  url: http://www.3gpp.org/ftp/Specs/archive/29_series/29.549/
+security:
+  - {}
+  - oAuth2ClientCredentials: []
+servers:
+  - url: '{apiRoot}/ss-kir/v1'
+    variables:
+      apiRoot:
+        default: https://example.com
+        description: apiRoot as defined in clause 6.5 of 3GPP TS 29.549
+paths:
+  /key-records:
+    get:
+      description: Retrieve Key management information specific to VAL service.
+      parameters:
+        - name: val-service-id
+          in: query
+          description: String identifying an individual VAL service
+          required: true
+          schema:
+            type: string
+        - name: val-tgt-ue
+          in: query
+          description: Identifying a VAL target.
+          required: false
+          schema:
+            $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+      responses:
+        '200':
+          description: The key management information of the VAL service, VAL User or VAL UE.
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ValKeyInfo'
+        '400':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/400'
+        '401':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/401'
+        '403':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/403'
+        '404':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '406':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/404'
+        '429':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/429'
+        '500':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/500'
+        '503':
+          $ref: 'TS29122_CommonData.yaml#/components/responses/503'
+        default:
+          $ref: 'TS29122_CommonData.yaml#/components/responses/default'
+components:
+  securitySchemes:
+    oAuth2ClientCredentials:
+      type: oauth2
+
+```
+
+```
+flows:
+  clientCredentials:
+    tokenUrl: '{tokenUrl}'
+    scopes: {}
+schemas:
+  ValKeyInfo:
+    type: object
+    properties:
+      userUri:
+        $ref: 'TS29122_CommonData.yaml#/components/schemas/Uri'
+      skmsId:
+        type: string
+        description: String identifying the key management server.
+      valService:
+        type: string
+        description: Unique identifier of a VAL Service.
+      valTgtUe:
+        $ref: 'TS29549_SS_UserProfileRetrieval.yaml#/components/schemas/ValTargetUe'
+      keyInfo:
+        type: string
+        description: Key management information specific to VAL service, VAL User or VAL UE.
+    required:
+      - userUri
+      - valService
+      - keyInfo
+```
+
+## Annex B (informative): Change history
+
+| Change history |          |           |      |     |     |                                                                                                                                                                                                                        |             |
+|----------------|----------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                                                        | New version |
+| 2019-10        | CT3#106  |           |      |     |     | TS skeleton for Services Enabler Architecture Layer for Verticals Application Programming Interface specification.                                                                                                     | 0.0.0       |
+| 2019-10        | CT3#106  | C3-194418 |      |     |     | Inclusion of TS skeleton document with clauses reflecting SEAL service APIs, agreed in the meeting CT3#106: C3-194418                                                                                                  | 0.1.0       |
+| 2019-10        | CT3#106  | C3-194314 |      |     |     | Inclusion of documents agreed in CT3#106: C3-194297, C3-194298, C3-194299, C3-194300                                                                                                                                   | 0.2.0       |
+| 2019-11        | CT3#107  | C3-195307 |      |     |     | Inclusion of documents agreed in CT3#107: C3-195157, C3-195260, C3-195441, C3-195262, C3-195263, C3-195264, C3-195185                                                                                                  | 0.3.0       |
+| 2019-12        | CT#86    | CP-193176 |      |     |     | Sent to plenary for Information                                                                                                                                                                                        | 1.0.0       |
+| 2020-03        | CT3#108e |           |      |     |     | Inclusion of documents agreed in CT3#108e meeting: C3-201346, C3-201347, C3-201348, C3-201349, C3-201350, C3-201456, C3-201457, C3-201351, C3-201352, C3-201271                                                        | 1.1.0       |
+| 2020-04        | CT3#109e | C3-202444 |      |     |     | Inclusion of documents agreed in CT3#109e meeting: C3-202241, C3-202275, C3-202334, C3-202335, C3-202336, C3-202337, C3-202338, C3-202339, C3-202340, C3-202341, C3-202342, C3-202343, C3-202481                       | 1.2.0       |
+| 2020-06        | CT3#110e | C3-203459 |      |     |     | Inclusion of documents agreed in CT3#110e meeting: C3-203233, C3-203317, C3-203409, C3-203411, C3-203412, C3-203413, C3-203414, C3-203415, C3-203416, C3-203417, C3-203418, C3-203419, C3-203530, C3-203587, C3-203634 | 1.3.0       |
+| 2020-06        | CT#88e   | CP-201209 |      |     |     | TS sent to plenary for approval                                                                                                                                                                                        | 2.0.0       |
+| 2020-06        | CT#88e   | CP-201334 |      |     |     | Implementation errors fixed. TS sent to plenary for approval                                                                                                                                                           | 2.0.1       |
+| 2020-06        | CT#88e   | CP-201334 |      |     |     | TS approved by plenary                                                                                                                                                                                                 | 16.0.0      |
+| 2020-09        | CT#89e   | CP-202074 | 0001 |     | F   | Correct apiVersion notation                                                                                                                                                                                            | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202074 | 0002 | 1   | F   | Corrections to API and Event names                                                                                                                                                                                     | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202074 | 0003 |     | F   | Correct Identity filter in Events API                                                                                                                                                                                  | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202087 | 0004 | 1   | F   | SS_KeyInfoRetrieval API correction                                                                                                                                                                                     | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202074 | 0005 |     | F   | Key Management API description                                                                                                                                                                                         | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202074 | 0006 | 1   | F   | UnicastSubscription attribute presence correction                                                                                                                                                                      | 16.1.0      |
+| 2020-09        | CT#89e   | CP-202084 | 0009 |     | F   | Update of OpenAPI version and TS version in externalDocs field                                                                                                                                                         | 16.1.0      |
+| 2020-12        | CT#90e   | CP-203139 | 0010 | 1   | F   | Essential corrections and alignments                                                                                                                                                                                   | 16.2.0      |
+| 2020-12        | CT#90e   | CP-203142 | 0011 | 1   | F   | Immediate reporting                                                                                                                                                                                                    | 16.2.0      |
+| 2020-12        | CT#90e   | CP-203139 | 0012 | 1   | F   | Storage of YAML files in 3GPP Forge                                                                                                                                                                                    | 16.2.0      |
+| 2020-12        | CT#90e   | CP-203142 | 0013 | 1   | F   | SEAL Group configuration corrections                                                                                                                                                                                   | 16.2.0      |
+| 2020-12        | CT#90e   | CP-203152 | 0014 |     | F   | Update of OpenAPI version and TS version in externalDocs field                                                                                                                                                         | 16.2.0      |
+| 2021-06        | CT#92e   | CP-211235 | 0024 |     | F   | Notification URI                                                                                                                                                                                                       | 16.3.0      |
+| 2021-12        | CT#94e   | CP-213240 | 0053 |     | F   | Remove procedure lacking API support                                                                                                                                                                                   | 16.4.0      |
+| 2022-06        | CT#96    | CP-221156 | 0086 |     | F   | SEAL-S security update                                                                                                                                                                                                 | 16.5.0      |
+| 2022-06        | CT#96    | CP-221156 | 0090 |     | F   | Correcting the ValTargetUe data type name in two occurrences                                                                                                                                                           | 16.5.0      |
+| 2022-12        | CT#98e   | CP-223193 | 0126 |     | F   | Correction of the presence and cardinality of the "suppFeat" attribute within the MulticastSubscription data structure in the SS_NetworkResourceAdaptation API                                                         | 16.6.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29582/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg b/marked/Rel-16/29_series/29582/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..840ec80e2deb90866e3c2c35e17b218be0fc8d79
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/1a74cf06fd2a1f8dcf7932224b617c57_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b179f319b29d8618667082170ea1d88f2fa1e0c48d30ad16dee6438acecd420b
+size 9415
diff --git a/marked/Rel-16/29_series/29582/42e18c25bfd455a5a57f207bacfcb970_img.jpg b/marked/Rel-16/29_series/29582/42e18c25bfd455a5a57f207bacfcb970_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..507a48485a16f415e93b263698ff9ebe5ebc9e05
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/42e18c25bfd455a5a57f207bacfcb970_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56177a863658bec46a2bf20fd29b6a7009514975f916e8e54a89b7b76ce4f8fc
+size 21192
diff --git a/marked/Rel-16/29_series/29582/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29582/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca14e3aa62ef2e019a3a49b9003e5b4f423f3f98
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da9344cee148e7e79c57773ce8fc88cf4e34adbf583c30727689f75a9459b601
+size 7625
diff --git a/marked/Rel-16/29_series/29582/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29582/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4074eb2148617c3041a7d4a8b585759f3bad9b1
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64f0958b56960ec38ba378c80d097d14a8504ab506e76f1b1da9e96f248d390d
+size 5809
diff --git a/marked/Rel-16/29_series/29582/adc59ed6840bcb2d392ea323abfccedc_img.jpg b/marked/Rel-16/29_series/29582/adc59ed6840bcb2d392ea323abfccedc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2c595e1bcdce70b51d1cdfba2c422819e87b2cf
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/adc59ed6840bcb2d392ea323abfccedc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7356e3b7a26df6a8a08bc063832a98b99b729c1531124f8e86d28929f5038ca2
+size 10464
diff --git a/marked/Rel-16/29_series/29582/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg b/marked/Rel-16/29_series/29582/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48392489d341c07ac0325f98676b36a9eeb927c1
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/f0eaca8e167a863864b4ad9adb7ef16f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4962e9416e35117381bd9167c8657c8cb822e82cbc23654ee76efb5f17eeea0
+size 13950
diff --git a/marked/Rel-16/29_series/29582/raw.md b/marked/Rel-16/29_series/29582/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9a3e94fe8f22780c8c41fd4c6d5a4db9461517c4
--- /dev/null
+++ b/marked/Rel-16/29_series/29582/raw.md
@@ -0,0 +1,2131 @@
+
+
+# 3GPP TS 29.582 V16.5.0 (2023-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mission Critical Data (MCData) interworking with Land Mobile Radio (LMR) systems; Stage 3 (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines of increasing height, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. The "P" and "P" are also connected at the top by a single horizontal line. Below the "G" and the first "P" is a small red graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+
+Valbonne - FRANCE
+
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                       |    |
+|---------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                        | 7  |
+| Introduction .....                                                                    | 8  |
+| 1 Scope.....                                                                          | 9  |
+| 2 References.....                                                                     | 9  |
+| 3 Definitions of terms, symbols and abbreviations .....                               | 10 |
+| 3.1 Terms.....                                                                        | 10 |
+| 3.2 Abbreviations .....                                                               | 11 |
+| 4 General.....                                                                        | 11 |
+| 4.1 MCData overview .....                                                             | 11 |
+| 4.2 Identity, URI and address assignments .....                                       | 12 |
+| 4.2.1 Public Service identities .....                                                 | 12 |
+| 4.2.2 MCData session identity.....                                                    | 12 |
+| 4.2.3 MCData client ID .....                                                          | 12 |
+| 4.3 Emergency alerts.....                                                             | 12 |
+| 4.4 MCData protocol.....                                                              | 12 |
+| 4.5 Protection of sensitive XML application data.....                                 | 12 |
+| 4.6 Protection of TLV signalling and media content .....                              | 13 |
+| 4.7 Warning Header Field.....                                                         | 14 |
+| 4.7.1 General .....                                                                   | 14 |
+| 4.7.2 Warning texts.....                                                              | 14 |
+| 5 Roles.....                                                                          | 14 |
+| 5.1 Introduction .....                                                                | 14 |
+| 5.2 IWF.....                                                                          | 14 |
+| 5.2.1 General .....                                                                   | 14 |
+| 5.2.1A SIP failure case .....                                                         | 15 |
+| 6 Common procedures .....                                                             | 15 |
+| 6.1 Introduction .....                                                                | 15 |
+| 6.2 IWF performing the participating role procedures.....                             | 15 |
+| 6.2.1 Void.....                                                                       | 15 |
+| 6.2.2 MCData conversation items .....                                                 | 15 |
+| 6.2.2.1 IWF generating an SDS Message .....                                           | 15 |
+| 6.2.3 Disposition Notifications.....                                                  | 17 |
+| 6.2.3.1 Generating an SDS Notification .....                                          | 17 |
+| 6.2.4 Sending SIP requests and receiving SIP responses .....                          | 18 |
+| 6.2.4.1 Generating a SIP MESSAGE request towards the controlling MCData function..... | 18 |
+| 6.3 Server role procedures.....                                                       | 18 |
+| 6.3.0 Introduction .....                                                              | 18 |
+| 6.3.1 Distinction of requests at the IWF.....                                         | 18 |
+| 6.3.1.1 SIP MESSAGE request .....                                                     | 18 |
+| 6.3.1.2 SIP INVITE request.....                                                       | 19 |
+| 6.3.2 Sending SIP requests and receiving SIP responses .....                          | 19 |
+| 6.3.2.1 Generating a SIP MESSAGE request towards the terminating MCData client .....  | 19 |
+| 6.3.3 Groups homed in the IWF .....                                                   | 19 |
+| 6.3.4 Void.....                                                                       | 20 |
+| 6.3.5 Affiliation check.....                                                          | 20 |
+| 6.4 Handling of MIME bodies in a SIP message.....                                     | 20 |
+| 6.5 Confidentiality and Integrity Protection of sensitive XML content.....            | 20 |
+| 6.5.1 General .....                                                                   | 20 |
+| 6.5.1.1 Applicability and exclusions.....                                             | 20 |
+| 6.5.1.2 Performing XML content encryption .....                                       | 20 |
+| 6.5.1.3 Performing integrity protection on an XML body.....                           | 20 |
+| 6.5.2 Confidentiality Protection .....                                                | 20 |
+| 6.5.2.2 Keys used in confidentiality protection procedures.....                       | 20 |
+
+|           |                                                                                                                      |    |
+|-----------|----------------------------------------------------------------------------------------------------------------------|----|
+| 6.5.2.3   | Procedures for sending confidentiality protected content.....                                                        | 21 |
+| 6.5.2.3.2 | IWF performing the role of an MCData server.....                                                                     | 21 |
+| 6.5.2.5   | IWF copying received XML content.....                                                                                | 21 |
+| 6.5.3     | Integrity Protection of XML documents .....                                                                          | 22 |
+| 6.5.3.2   | Keys used in integrity protection procedures .....                                                                   | 22 |
+| 6.5.3.3   | Sending integrity protected content .....                                                                            | 22 |
+| 6.5.3.3.2 | Integrity protection at the IWF.....                                                                                 | 22 |
+| 6.6       | Confidentiality and integrity protection of TLV messages.....                                                        | 22 |
+| 6.6.1     | General .....                                                                                                        | 22 |
+| 6.6.2     | Derivation of master keys for media and media control .....                                                          | 23 |
+| 6.6.3     | Protection of MCData signalling and MCData messages .....                                                            | 23 |
+| 6.6.3.1   | General.....                                                                                                         | 23 |
+| 7         | Registration and service authorisation .....                                                                         | 23 |
+| 7.1       | Server procedures.....                                                                                               | 23 |
+| 8         | Affiliation.....                                                                                                     | 23 |
+| 8.1       | General .....                                                                                                        | 23 |
+| 8.2       | IWF performing the participating role procedures.....                                                                | 24 |
+| 8.3       | Server procedures.....                                                                                               | 24 |
+| 8.3.1     | General .....                                                                                                        | 24 |
+| 8.3.2     | Procedures of the IWF performing the participating role.....                                                         | 24 |
+| 8.3.2.1   | General.....                                                                                                         | 24 |
+| 8.3.2.2   | Stored information .....                                                                                             | 24 |
+| 8.3.2.3   | Receiving affiliation status change from a user homed in the IWF procedure.....                                      | 25 |
+| 8.3.2.4   | Receiving subscription to affiliation status procedure.....                                                          | 25 |
+| 8.3.2.5   | Sending notification of change of affiliation status procedure .....                                                 | 25 |
+| 8.3.2.6   | Sending affiliation status change towards MCData server owning MCData group procedure .....                          | 25 |
+| 8.3.2.7   | Affiliation status retrieval from IWF performing the role of the MCData server owning MCData group procedure .....   | 26 |
+| 8.3.2.8   | Procedure for authorising affiliation status change request in negotiated mode sent to a user homed in the IWF ..... | 29 |
+| 8.3.2.9   | Forwarding affiliation status change towards an MCData user procedure.....                                           | 29 |
+| 8.3.2.10  | Forwarding subscription to affiliation status towards an MCData user procedure .....                                 | 29 |
+| 8.3.2.11  | Affiliation status determination .....                                                                               | 29 |
+| 8.3.2.12  | Affiliation status change by implicit affiliation .....                                                              | 30 |
+| 8.3.2.13  | Implicit affiliation status change completion.....                                                                   | 31 |
+| 8.3.2.14  | Implicit affiliation status change cancellation .....                                                                | 31 |
+| 8.3.2.15  | Automatic affiliation to configured groups procedure .....                                                           | 31 |
+| 8.3.3     | Procedures of the IWF performing the controlling role .....                                                          | 31 |
+| 8.3.3.1   | General.....                                                                                                         | 31 |
+| 8.3.3.2   | Stored information .....                                                                                             | 32 |
+| 8.3.3.3   | Receiving group affiliation status change procedure.....                                                             | 32 |
+| 8.3.3.4   | Receiving subscription to affiliation status procedure.....                                                          | 33 |
+| 8.3.3.5   | Sending notification of change of affiliation status procedure .....                                                 | 34 |
+| 8.3.3.6   | Implicit affiliation eligibility check procedure .....                                                               | 35 |
+| 8.3.3.7   | Affiliation status change by implicit affiliation procedure .....                                                    | 35 |
+| 8.4       | Coding.....                                                                                                          | 36 |
+| 9         | IWF Short Data Service (SDS).....                                                                                    | 36 |
+| 9.1       | General .....                                                                                                        | 36 |
+| 9.2       | On-network SDS .....                                                                                                 | 36 |
+| 9.2.1     | General .....                                                                                                        | 36 |
+| 9.2.2     | Standalone SDS using signalling control plane.....                                                                   | 36 |
+| 9.2.2.1   | General.....                                                                                                         | 36 |
+| 9.2.2.2   | Procedures used by the IWF for users homed in the IWF.....                                                           | 37 |
+| 9.2.2.2.1 | Originating procedures.....                                                                                          | 37 |
+| 9.2.2.2.2 | Terminating procedures.....                                                                                          | 37 |
+| 9.2.2.3   | IWF performing the participating MCData function procedures .....                                                    | 38 |
+| 9.2.2.3.1 | Originating participating MCData function procedures.....                                                            | 38 |
+| 9.2.2.3.2 | IWF performing the terminating participating MCData role procedures .....                                            | 38 |
+| 9.2.2.4   | Controlling IWF MCData procedures .....                                                                              | 39 |
+| 9.2.2.4.1 | Originating controlling IWF procedures .....                                                                         | 39 |
+
+|           |                                                                                              |    |
+|-----------|----------------------------------------------------------------------------------------------|----|
+| 9.2.2.4.2 | Terminating controlling MCData function procedures .....                                     | 40 |
+| 9.2.3     | Standalone SDS using media plane .....                                                       | 42 |
+| 9.2.4     | SDS session .....                                                                            | 42 |
+| 9.3       | Off-network SDS .....                                                                        | 42 |
+| 10        | File Distribution (FD) .....                                                                 | 42 |
+| 11        | Transmission and reception control .....                                                     | 42 |
+| 11.1      | General .....                                                                                | 42 |
+| 11.2      | Auto-receive for File Distribution .....                                                     | 42 |
+| 11.3      | Accessing list of deferred data group communications .....                                   | 43 |
+| 12        | Dispositions and Notifications .....                                                         | 43 |
+| 12.1      | General .....                                                                                | 43 |
+| 12.2      | Disposition notifications .....                                                              | 43 |
+| 12.2.1    | IWF performing the MCData participating role .....                                           | 43 |
+| 12.2.1.1  | Participating IWF procedures .....                                                           | 43 |
+| 12.2.1.2  | Sending a disposition notification message .....                                             | 43 |
+| 12.2.1.3  | Participating IWF receives disposition notification from a controlling MCData function ..... | 44 |
+| 12.2.2    | IWF performing the MCData controlling role .....                                             | 44 |
+| 12.3      | On-network disposition notifications .....                                                   | 46 |
+| 13        | Communication Release .....                                                                  | 46 |
+| 14        | Enhanced Status (ES) .....                                                                   | 46 |
+| 14.1      | General .....                                                                                | 46 |
+| 14.2      | On-network ES .....                                                                          | 46 |
+| 14.2.1    | Void .....                                                                                   | 46 |
+| 14.2.2    | IWF performing the participating MCData role procedures .....                                | 46 |
+| 14.2.2.1  | Originating participating MCData function procedures .....                                   | 46 |
+| 14.2.2.2  | Terminating participating MCData function procedures .....                                   | 47 |
+| 14.2.3    | IWF performing the controlling MCData role procedures .....                                  | 47 |
+| 14.2.3.1  | Originating controlling MCData function procedures .....                                     | 47 |
+| 14.2.3.2  | Terminating controlling MCData function procedures .....                                     | 47 |
+| 15        | Message Formats .....                                                                        | 47 |
+| 15.1      | IWF message functional definitions and contents .....                                        | 47 |
+| 15.1.1    | General .....                                                                                | 47 |
+| 15.1.2    | SDS SIGNALLING PAYLOAD message .....                                                         | 48 |
+| 15.1.2.1  | Message definition .....                                                                     | 48 |
+| 15.1.3    | FD SIGNALLING PAYLOAD message .....                                                          | 48 |
+| 15.1.4    | DATA PAYLOAD message .....                                                                   | 48 |
+| 15.1.4.1  | Message definition .....                                                                     | 48 |
+| 15.1.5    | SDS NOTIFICATION message .....                                                               | 49 |
+| 15.1.5.1  | Message definition .....                                                                     | 49 |
+| 15.1.6    | FD NOTIFICATION message .....                                                                | 49 |
+| 15.1.7    | SDS OFF-NETWORK MESSAGE .....                                                                | 49 |
+| 15.1.8    | SDS OFF-NETWORK NOTIFICATION message .....                                                   | 50 |
+| 15.1.9    | FD NETWORK NOTIFICATION message .....                                                        | 50 |
+| 15.1.10   | COMMUNICATION RELEASE message .....                                                          | 50 |
+| 15.1.10.1 | Message definition .....                                                                     | 50 |
+| 15.1.11   | DEFERRED DATA REQUEST message .....                                                          | 50 |
+| 15.1.12   | DEFERRED DATA RESPONSE message .....                                                         | 50 |
+| 15.1.13   | FD HTTP TERMINATION .....                                                                    | 50 |
+| 15.2      | General message format and information elements coding .....                                 | 50 |
+| 15.2.1    | General .....                                                                                | 50 |
+| 15.2.2    | Message type .....                                                                           | 51 |
+| 15.2.3    | Void .....                                                                                   | 51 |
+| 15.2.4    | Void .....                                                                                   | 51 |
+| 15.2.5    | Void .....                                                                                   | 51 |
+| 15.2.6    | Void .....                                                                                   | 51 |
+| 15.2.7    | Void .....                                                                                   | 51 |
+| 15.2.8    | Void .....                                                                                   | 51 |
+| 15.2.9    | Conversation ID .....                                                                        | 51 |
+
+|                                                     |                                                                                      |           |
+|-----------------------------------------------------|--------------------------------------------------------------------------------------|-----------|
+| 15.2.10                                             | Message ID .....                                                                     | 52        |
+| 15.2.11                                             | Void .....                                                                           | 53        |
+| 15.2.12                                             | Void .....                                                                           | 53        |
+| 15.2.13                                             | Payload .....                                                                        | 53        |
+| 16                                                  | Media plane.....                                                                     | 54        |
+| 17                                                  | Handling of Interworking Security Data messages.....                                 | 54        |
+| 17.1                                                | IWF.....                                                                             | 54        |
+| 17.1.1                                              | IWF originates Interworking Security Data message.....                               | 54        |
+| 17.1.2                                              | IWF receives Interworking Security Data message .....                                | 55        |
+| 17.2                                                | Interworking Security Data message payload.....                                      | 55        |
+| 17.2.1                                              | Message definition.....                                                              | 55        |
+| 17.2.2                                              | External network type.....                                                           | 55        |
+| <b>Annex A (informative): Signalling flows.....</b> |                                                                                      | <b>56</b> |
+| <b>Annex B (normative): Timers .....</b>            |                                                                                      | <b>57</b> |
+| <b>Annex C (normative): Counters.....</b>           |                                                                                      | <b>58</b> |
+| <b>Annex D (normative): XML schemas.....</b>        |                                                                                      | <b>59</b> |
+| D.1                                                 | XML schema for transporting MCData identities and general services information ..... | 59        |
+| D.1.1                                               | General .....                                                                        | 59        |
+| D.1.2                                               | XML schema.....                                                                      | 59        |
+| <b>Annex E (informative): Change history .....</b>  |                                                                                      | <b>60</b> |
+
+# Foreword
+
+This Technical Specification/Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- Introduction
+
+The present document has been produced as an aspect of work to realise the stage 3 protocols to implement the stage 2 functionality for Interworking between Mission Critical systems and Land Mobile Radio systems as described in 3GPP TS 23.283 [80]. Early stage 3 study work is documented in 3GPP TR 24.883 [90] which covers both MCPTT and MCData interworking.
+
+The document structure describes functionality modelled on 3GPP TS 24.282 [49] because the behaviour of an Interworking Function (IWF) for LMR MCData interworking is modelled on that of an MCData server, and the clause numbering is also based on that used in 3GPP TS 24.282 [49] in order to aid comparison between the two specifications and identification of any behavioural changes.
+
+The reference numbering is based on that used in 3GPP TR 24.883 [90] and so may not be sequential.
+
+# 1 Scope
+
+The present document specifies the protocols needed to support a Mission Critical Data (MCData) system interworking with a Land Mobile Radio (LMR) system based on the IWF-2 interface between an MCData server and an Interworking Function (IWF) as described in 3GPP TS 23.283 [80].
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [4] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
+- [5] 3GPP TS 23.379: "Functional architecture and information flows to support mission critical communication services; Stage 2".
+- [6] IETF RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
+- [9] IETF RFC 6050 (November 2010): "A Session Initiation Protocol (SIP) Extension for the Identification of Services".
+- [16] IETF RFC 3711: "The Secure Real-time Protocol (SRTP)".
+- [20] IETF RFC 5366 (October 2008): "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
+- [24] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol".
+- [26] IETF RFC 6665 (July 2012): "SIP-Specific Event Notification".
+- [31] 3GPP TS 24.481: "Mission Critical Services (MCS) group management Protocol specification".
+- [33] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
+- [37] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event State Publication".
+- [46] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax".
+- [49] 3GPP TS 24.482: "Mission Critical Services (MCS) identity management Protocol specification".
+- [50] 3GPP TS 24.484: "Mission Critical Services (MCS) configuration management Protocol specification".
+- [51] IETF RFC 3856 (August 2004): "A Presence Event Package for the Session Initiation Protocol (SIP)".
+- [67] IETF RFC 4122 (July 2005): "A Universally Unique Identifier (UUID) URN Namespace".
+
+- [78] 3GPP TS 33.180: "Security of the mission critical service".
+- [80] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2".
+- [81] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; protocol specification;".
+- [82] 3GPP TS 24.282: " Mission Critical Data (MCData) signalling control; Protocol specification;"
+- [85] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification".
+- [86] IETF RFC 1738 (December 1994): "Uniform Resource Locators (URL)".
+- [87] 3GPP TS 29.379: "Mission Critical Push To Talk (MCPTT) call control interworking with LMR systems; Protocol specification".
+- [89] IETF RFC 4826 (May 2007): "Extensible Markup Language (XML) Formats for Representing Resource Lists".
+- [90] 3GPP TR 24.883: "Mission Critical Systems Connection to LMR".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.379 [5] apply:
+
+- Group call**
+- MCPTT call**
+- Mission critical push to talk**
+- Private call**
+- SIP core**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.283 [28] apply:
+
+- Interworking Function (IWF)**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 29.379 [26] apply:
+
+- IWF performing the controlling role**
+- IWF performing the non-controlling**
+- IWF performing the participating role**
+
+For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.180 [18] apply:
+
+- Group Master Key (GMK)**
+- Group Master Key Identifier (GMK-ID)**
+- Private Call Key (PCK)**
+- Private Call Key Identifier (PCK-ID)**
+- Signalling Protection Key (SPK)**
+- Signalling Protection Key Identifier (SPK-ID)**
+
+For the purposes of the present document, the following terms and definitions given in IETF RFC 3711 [16] apply:
+
+- SRTP master key (SRTP-MK)**
+- SRTP master key identifier (SRTP-MKI)**
+- SRTP master salt (SRTP-MS)**
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|          |                                      |
+|----------|--------------------------------------|
+| GMK      | Group Management Key                 |
+| GMK-ID   | Group Master Key Identifier          |
+| GMS      | Group Management Server              |
+| GUK-ID   | Group User Key Identifier            |
+| IP       | Internet Protocol                    |
+| MCData   | Mission Critical Data                |
+| PCK      | Private Call Key                     |
+| PCK-ID   | Private Call Key Identifier          |
+| RFC      | Request For Comment                  |
+| RTCP     | RTP Control Protocol                 |
+| RTP      | Real-time Transport Protocol         |
+| SPK      | Signalling Protection Key            |
+| SPK-ID   | Signalling Protection Key Identifier |
+| SRTCP    | Secure RTCP                          |
+| SRTP     | Secure RTP                           |
+| SRTP-MK  | SRTP master key                      |
+| SRTP-MKI | SRTP master key identifier           |
+| SRTP-MS  | SRTP master salt                     |
+| SSRC     | Synchronization SouRCe               |
+| UE       | User Equipment                       |
+
+# --- 4 General
+
+## 4.1 MCData overview
+
+The MCData service supports communication between a pair of users (i.e. one-to-one communication) and several users (i.e. group communication), where each user has the ability to share data using Short Data Service (SDS).
+
+The present document provides the signalling control protocol enhancements to support the MCData architectural procedures for MCData SDS interworking between on-network Mission Critical users and users homed in the IWF, as specified in 3GPP TS 23.283[80].
+
+The present document makes use of the existing IMS procedures specified in 3GPP TS 24.229 [4].
+
+The procedures in this document allow an on-network MCData user to:
+
+- send a standalone SDS using signalling control plane to a user homed in the IWF or to a group including at least one user homed in the IWF; and
+- send a standalone SDS using media plane to a user homed in the IWF or to a group including at least one user homed in the IWF.
+
+The procedures in this document allow a user homed in the IWF to:
+
+- send a standalone SDS using signalling control plane to an on-network MCData user or to a group of on-network MCData users; and
+- send a standalone SDS using media plane to an on-network MCData user or to a group of on-network MCData users.
+
+The present document does not support the interworking of SDS sessions with users homed in the IWF.
+
+The MCData procedures provided by the present document refer to:
+
+- the media plane procedures defined in 3GPP TS 24.582 [85];
+
+- the group management procedures defined in 3GPP TS 24.481 [31];
+- the identity management procedures defined in 3GPP TS 24.482 [49]; and
+- the security procedures defined in 3GPP TS 33.180 [78].
+
+The following procedures are provided within this document:
+
+- common procedures are specified in clause 6;
+- procedures for registration in the IM CN subsystem and service authorisation are specified in clause 7;
+- procedures for affiliation are specified in clause 8;
+- procedures for SDS are specified in clause 9;
+- procedures for transmission and reception control are specified in clause 11;
+- procedures for dispositions and notifications are specified in clause 12;
+- procedures for communication release are specified in clause 13; and
+- procedures for enhanced status are specified in clause 14.
+
+The IWF acts on behalf of all users homed in the IWF. There are no client procedures specified in the present document and specific client handling within the LMR system is out of scope.
+
+## 4.2 Identity, URI and address assignments
+
+### 4.2.1 Public Service identities
+
+In order to support MCData interworking with LMR, the following URI and address assignments are assumed:
+
+- 1) the IWF performing the participating role is configured to be reachable using a public service identity.
+- 2) the IWF performing the controlling role is configured to be reachable using a public service identity.
+
+### 4.2.2 MCData session identity
+
+There is no MSRP session used at the IWF to support the short data service (SDS).
+
+### 4.2.3 MCData client ID
+
+The MCData client ID is described in 3GPP TS 24.282 [82] clause 4.8.
+
+## 4.3 Emergency alerts
+
+## 4.4 MCData protocol
+
+Clause 15 describes the TLV based message formats used in MCData communications.
+
+Annex I of 3GPP TS 24.379 [81] describes the standard format of the messages and the encoding rules for each type of information element.
+
+## 4.5 Protection of sensitive XML application data
+
+In certain deployments, for example, in the case that the MCData operator uses the underlying SIP core infrastructure from the carrier operator, the MCData operator can prevent certain sensitive application data from being exposed to the SIP layer. The following data are classified as sensitive application data:
+
+- MCData ID;
+- MCData group ID;
+- alert indicator;
+- access token (containing the MCData ID); and
+- MCData client ID.
+
+The above data is transported as XML content in SIP messages, in XML elements or XML attributes.
+
+NOTE: SIP layer protection terminates at the IWF.
+
+Data is transported in attributes in the following circumstances in the procedures in the present document:
+
+- an MCData ID, an MCData Group ID, and an MCData client ID in an XML document published in SIP PUBLISH request for affiliation according to IETF RFC 3856 [51];
+- an MCData ID or an MCData Group ID in XML document notified in a SIP NOTIFY request for affiliation according to IETF RFC 3856 [51]; and
+- an MCData ID in application/resource-lists+xml document included in a SIP MESSAGE or SIP INVITE request for one-to-one SDS, according to IETF RFC 5366 [20];
+
+3GPP TS 33.180 [78] describes a method to provide confidentiality protection of sensitive application data in elements by using XML encryption (i.e. xmlenc) and in attributes by using an attribute confidentiality protection scheme described in 3GPP TS 24.282 [82] clause 6.6.2.3. Integrity protection can also be provided by using XML signatures (i.e. xmlsig).
+
+Protection of the data relies on a shared XML protection key (XPK) used to encrypt and sign data:
+
+- between MCData servers and an IWF, the XPK is a signalling protection key (SPK).
+
+The SPK (XPK) and a key-id SPK-ID (XPK-ID) are directly provisioned in the MCData server and IWF.
+
+Configuration in the MCData client, IWF and MCData server is used to determine whether one or both of confidentiality protection and integrity protection are required.
+
+3GPP TS 24.282 [82] clause 4.6 provides examples of confidentiality and integrity protection applied to application data.
+
+## 4.6 Protection of TLV signalling and media content
+
+The protection of TLV signalling and media content is based on 3GPP MCData security solution as defined in 3GPP TS 33.180 [78].
+
+For different security requirements of different information elements of a MCData message, the information elements of MCData messages are bifurcated in the following components:
+
+- **MCData Data signalling payload:** information elements necessary for identification and management of the MCData messages e.g. conversation identifiers, session identifiers, transaction identifiers, disposition requests, etc. This payload is confidentiality and integrity protected between the MCData server and the IWF.
+- **MCData Data payload:** the actual user payload for MCData user or application consumption. This payload is confidentiality and integrity protected between the MCData client and the IWF.
+
+An SDS message can be sent over the signalling plane or the media plane. When an SDS message is sent using the signalling plane, the body included in the SIP MESSAGE request, which carries the MCData Data signalling payload, is protected separately between each pair of entities if protection is applied. On the other hand, the body included in the SIP MESSAGE request which carries the MCData data payload is protected between the MCData client and the IWF. The procedures for the protection of the SDS messages over the signalling plane are specified in clause 6.6. Protection of SDS messages over the media control plane is specified in 3GPP TS 24.582 [85].
+
+NOTE: The method by which SDS messages are protected between the IWF and the user homed in the IWF is outside the scope of the present document.
+
+## 4.7 Warning Header Field
+
+### 4.7.1 General
+
+An IWF can include a free text string in a SIP response to a SIP request. When the IWF includes a free text string in a response to a SIP MESSAGE or SIP INVITE request the free text string is included in a Warning header field as specified in IETF RFC 3261 [24]. The IWF includes the Warning code set to 399 (miscellaneous warning) and includes the host name set to the host name of the IWF.
+
+EXAMPLE: Warning: 399 example.domain.com "200 user not authorised to transmit data"
+
+### 4.7.2 Warning texts
+
+Warning texts specified in table 4.7.2-1 for interworking are used, in conjunction with existing warning texts as specified in 3GPP TS 24.282 [82].
+
+**Table 4.7.2-1: Warning texts for interworking defined for the Warning header field**
+
+| Code | Explanatory text                                                               | Description                                                                                                                           |
+|------|--------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| 300  | LMR system does not support requested application                              | An application has been requested that is not supported in the LMR system.                                                            |
+| 301  | LMR system does not support disposition notification for requested application | A disposition notification has been requested for an application for which the LMR system does not support disposition notifications. |
+
+# 5 Roles
+
+## 5.1 Introduction
+
+This clause describes the functional roles for an IWF to support the MCData service.
+
+## 5.2 IWF
+
+### 5.2.1 General
+
+When referring to the procedures in the present document for the IWF acting as a participating MCData server for the user homed in the IWF, the term "IWF performing the participating role" is used.
+
+When referring to the procedures in the present document for the IWF acting as a controlling MCData server for the user homed in the IWF, the term "IWF performing the controlling role" is used.
+
+An IWF can perform the controlling role for short data service as defined in the present document.
+
+An IWF can perform the participating role for short data service as defined in the present document.
+
+An IWF in the participating role can serve an originating user homed in the IWF.
+
+An IWF in the participating role can serve a terminating user homed in the IWF.
+
+To be compliant with the procedures in the present document, an IWF shall:
+
+- support the MCData server procedures defined in 3GPP TS 23.283 [80];
+
+- implement the role of an AS performing 3rd party call control acting as a routing B2BUA as defined in 3GPP TS 24.229 [4];
+- generate SDP offer and SDP answer in accordance with 3GPP TS 24.229 [4] and 3GPP TS 24.282 [82] clause 9.2.3 and 3GPP TS 24.282 [82] clause 9.2.4 for short data service;
+- for registration and service authorisation, implement the procedures specified in 3GPP TS 24.282 [82] clause 7.3;
+- for affiliation, implement the procedures specified in clause 9.2.2;
+- for short data service (SDS) functionality implement the MCData server procedures specified in:
+  - a) clause 9.2; and
+  - b) clause 6 of 3GPP TS 24.582 [85];
+- for transmission and reception control functionality implement the MCData server procedures specified in clause 11;
+- for disposition notification functionality implement the MCData server procedures specified in clause 12.2; and
+- for communication release functionality implement the MCData server procedures specified in clause 13.2.
+
+To be compliant with the procedures for confidentiality protection of XML elements in the present document, the IWF shall implement the procedures specified in clause 6.5.2.
+
+To be compliant with the procedures for integrity protection of XML MIME bodies in the present document, the IWF shall implement the procedures specified in clause 6.5.3.
+
+### 5.2.1A SIP failure case
+
+When initiating a SIP failure response to any received SIP request, depending on operator policy, the IWF may insert a SIP Response-Source header field in accordance with the procedures in clause 5.7.1.0 of 3GPP TS 24.229 [4], where the "role" header field parameter is set to "pf-mcdata-server" or "cf-mcdata-server" depending on the current role endorsed by the MCData server.
+
+# --- 6 Common procedures
+
+## 6.1 Introduction
+
+This clause describes the IWF procedures for MCData.
+
+## 6.2 IWF performing the participating role procedures
+
+### 6.2.1 Void
+
+### 6.2.2 MCData conversation items
+
+#### 6.2.2.1 IWF generating an SDS Message
+
+In order to generate an SDS message, the IWF performing the participating role:
+
+- 1) shall generate an SDS SIGNALLING PAYLOAD message as specified in clause 15.1.2;
+- 2) shall generate a DATA PAYLOAD message as specified in clause 15.1.4;
+
+- 3) shall include in the SIP request, the SDS SIGNALLING PAYLOAD message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in 3GPP TS 24.282 [82] clause E.1; and
+- 4) shall include in the SIP request, the DATA PAYLOAD message in an application/vnd.3gpp.mcdata-payload MIME body as specified in 3GPP TS 24.282 [82] clause E.2.
+
+When generating an SDS SIGNALLING PAYLOAD message as specified in clause 15.1.2, the IWF performing the participating role:
+
+- 1) shall set the Date and time IE to the current time as specified in 3GPP TS 24.282 [82] clause 15.2.8;
+- 2) if the SDS message starts a new conversation, shall set the Conversation ID IE to a newly generated Conversation ID value as specified in clause 15.2.9;
+- 3) if the SDS message continues an existing unfinished conversation, shall, if available, set the Conversation ID IE to the Conversation ID value of the existing conversation as specified in clause 15.2.9, or shall set the Conversation ID IE to the Conversation ID value "UNKNOWN CONVERSATION" as specified in clause 15.2.9;
+- 4) shall set the Message ID IE to a newly generated Message ID value as specified in clause 15.2.10;
+- 5) if the SDS message is in reply to a previously received SDS message shall include the InReplyTo message ID IE with the Message ID value:
+  - i) set to the Message ID value in the previously received SDS message;
+  - ii) set to the Message ID value "LMR MESSAGE ID" as specified in clause 15.2.10, with the value of octet 16 of the LMR MESSAGE ID set to the value of octet 16 of the Message ID in the previously received SDS message; and
+  - iii) set to the Message ID value "UNKNOWN ORIGINATING MESSAGE ID" as specified in clause 15.2.10;
+- 6) if the SDS message is for user consumption, shall not include an Application ID IE as specified in 3GPP TS 24.282 [82] clause 15.2.7 and shall not include an Extended application ID IE as specified in 3GPP TS 24.282 [82] clause 15.2.24;
+- 7) if the SDS message is intended for an application on the terminating MCData client, shall include:
+  - a) an Application ID IE with a Application ID value representing the intended application as specified in 3GPP TS 24.282 [82] clause 15.2.7; or
+  - b) an Extended application ID IE with an Extended application ID value representing the intended application as specified in 3GPP TS 24.282 [82] clause 15.2.24;
+
+NOTE: The value chosen for the Application ID value is decided by the mission critical organisation.
+
+- 8) if only a delivery disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY" as specified in 3GPP TS 24.282 [82] clause 15.2.3;
+- 9) if only a read disposition notification is required shall include a SDS disposition request type IE set to "READ" as specified in 3GPP TS 24.282 [82] clause 15.2.3; and
+- 10) if both a delivery and read disposition notification is required shall include a SDS disposition request type IE set to "DELIVERY AND READ" as specified in 3GPP TS 24.282 [82] clause 15.2.3.
+
+When generating a DATA PAYLOAD message for SDS as specified in clause 15.1.4, the IWF performing the participating role:
+
+- 1) shall set the Number of payloads IE to the number of Payload IEs that need to be encoded, as specified in clause 15.2.12;
+- 2) if end-to-end security is required for a one-to-one communication, shall include the Security parameters and Payload IE with security parameters as described in 3GPP TS 33.180 [78]. Otherwise, if end-to-end security is not required for a one-to-one communication, shall include the Payload IE as specified in clause 15.1.4; and
+- 3) for each Payload IE included:
+
+- a) if the payload is text, shall set the Payload content type as "TEXT" as specified in clause 15.2.13;
+- b) if the payload is binary data, shall set the Payload content type as "BINARY" as specified in clause 15.2.13;
+- c) if the payload is hyperlinks, shall set the Payload content type as "HYPERLINKS" as specified in clause 15.2.13;
+- d) if the payload is location, shall set the Payload content type as "LOCATION" as specified in clause 15.2.13;
+- e) if payload is enhanced status for a group, shall set the Payload content type as "ENHANCED STATUS" as specified in clause 15.2.13;
+- f) if payload is a native LMR message, shall set the Payload content type as "LMR MESSAGE" as specified in clause 15.2.13; and
+- g) shall include the data to be sent in the Payload data.
+
+### 6.2.3 Disposition Notifications
+
+#### 6.2.3.1 Generating an SDS Notification
+
+In order to generate an SDS notification, the IWF performing the participating role:
+
+- 1) shall generate an SDS NOTIFICATION message as specified in clause 15.1.5; and
+- 2) shall include in the SIP request, the SDS NOTIFICATION message in an application/vnd.3gpp.mcdata-signalling MIME body as specified in 3GPP TS 24.282 [82] clause E.1.
+
+When generating an SDS NOTIFICATION message as specified in clause 15.1.5, the IWF performing the participating role:
+
+- 1) if sending a delivered notification, shall set the SDS disposition notification type IE as "DELIVERED" as specified in 3GPP TS 24.282 [82] clause 15.2.5;
+- 2) if sending a read notification, shall set the SDS disposition notification type IE as "READ" as specified in 3GPP TS 24.282 [82] clause 15.2.5;
+- 3) if sending a delivered and read notification, shall set the SDS disposition notification type IE as "DELIVERED AND READ" as specified in 3GPP TS 24.282 [82] clause 15.2.5;
+- 4) if the SDS message could not be delivered, shall set the SDS disposition notification type IE as "UNDELIVERED" as specified in 3GPP TS 24.282 [82] clause 15.2.5;
+- 5) if SDS disposition notification was prevented by the LMR system, shall set the SDS disposition notification type IE as "DISPOSITION PREVENTED BY SYSTEM" as specified in 3GPP TS 24.282 [82] clause 15.2.5;
+- 6) shall set the Date and time IE to the current time to as specified in 3GPP TS 24.282 [82] clause 15.2.8;
+- 7) shall set the Conversation ID to the value of the Conversation ID that was received in the SDS message as specified in clause 15.2.9;
+- 8) shall set the Message ID to the value of the Message ID that was received in the SDS message as specified in clause 15.2.10;
+- 9) if the SDS message was destined for the user, shall not include an Application ID IE (as specified in 3GPP TS 24.282 [82] clause 15.2.7) and shall not include an Extended application ID IE (as specified in 3GPP TS 24.282 [82] clause 15.2.24); and
+- 10) if the SDS message was destined for an application, shall include:
+  - a) an Application ID IE set to the value of the Application ID that was included in the SDS message as specified in 3GPP TS 24.282 [82] clause 15.2.3; or
+  - b) an Extended application ID IE set to the value of the Extended application ID that was included in the SDS message as specified in 3GPP TS 24.282 [82] clause 15.2.24.
+
+### 6.2.4 Sending SIP requests and receiving SIP responses
+
+#### 6.2.4.1 Generating a SIP MESSAGE request towards the controlling MCData function
+
+This clause is referenced from other procedures.
+
+In a SIP MESSAGE request, the IWF performing the participating role:
+
+- 1) when sending SDS messages or SDS disposition notifications:
+  - a) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
+  - b) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6]; and
+  - c) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [4]), in a P-Preferred-Service header field according to IETF RFC 6050 [9] in the SIP MESSAGE request;
+- 2) may include a P-Preferred-Identity header field in the SIP MESSAGE request containing a public user identity as specified in 3GPP TS 24.229 [4]; and
+- 3) shall set the Request-URI to the public service identity of the controlling MCData function.
+
+## 6.3 Server role procedures
+
+### 6.3.0 Introduction
+
+The IWF performs the MCData server role when exchanging SDS messages with MCData servers within the MC system. The IWF does not communicate directly with MCData clients. The IWF does not support the FD service. Clause 6.3 describes the IWF operating as a controlling and participating MCData server.
+
+### 6.3.1 Distinction of requests at the IWF
+
+#### 6.3.1.1 SIP MESSAGE request
+
+The IWF shall perform the role of an MCData server in distinguishing between the following SIP MESSAGE requests for originations and terminations from 3GPP TS 24.282 [82] clause 6.3.1.1 as described below:
+
+- SIP MESSAGE request routed to the IWF performing the terminating participating MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field. Such requests are known as "SIP MESSAGE request for standalone SDS for terminating participating MCData function";
+- SIP MESSAGE request routed to IWF performing the MCData server role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field, and with an application/vnd.3gpp.mcdata-signalling MIME body containing an SDS NOTIFICATION message. Such requests are known as "SIP MESSAGE request for SDS disposition notification for MCData server";
+- SIP MESSAGE request routed to the IWF performing the controlling MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field. Such requests are known as "SIP MESSAGE request for standalone SDS for controlling MCData function"; and
+
+- SIP MESSAGE requests routed to the IWF performing the terminating participating role as a result of initial filter criteria with the Request-URI set to the public service identity of the IWF performing the participating role and containing a Content-Type header field set to "application/vnd.3gpp.mcdata-info+xml" and includes an XML body containing a <mcdatainfo> root element with a <mcdata-Params> element containing an <anyExt> element with the <request-type> element set to a value of "Interworking Security Data message". Such requests are known as "SIP MESSAGE request for Interworking Security Data message for participating function".
+
+If a SIP MESSAGE request is received at the IWF that is not in accordance with the SIP MESSAGE requests listed above, then the IWF shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response.
+
+#### 6.3.1.2 SIP INVITE request
+
+The IWF shall perform the role of an MCData server in distinguishing between the following SIP INVITE requests for originations and terminations from 3GPP TS 24.282 [82] clause 6.3.1.2 as described below:
+
+- SIP INVITE request routed to the IWF performing the terminating participating MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field and a <request-type> element set to "one-to-one-sds" or "group-sds" contained in an application/vnd.3gpp.mcdata-info+xml MIME body. Such requests are known as "SIP INVITE request for standalone SDS over media plane for terminating participating MCData function";
+- SIP INVITE request routed to the IWF performing the controlling MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field and a <request-type> element set to "one-to-one-sds" or "group-sds" contained in an application/vnd.3gpp.mcdata-info+xml MIME body. Such requests are known as "SIP INVITE request for controlling MCData function for standalone SDS over media plane";
+- SIP INVITE request routed to the IWF performing the terminating participating MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field and a <request-type> element set to "one-to-one-sds-session" or "group-sds-session" contained in an application/vnd.3gpp.mcdata-info+xml MIME body. Such requests are known as "SIP INVITE request for SDS session for terminating participating MCData function"; and
+- SIP INVITE request routed to the IWF performing the controlling MCData role with an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", and an ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" in a P-Asserted-Service header field and a <request-type> element set to "one-to-one-sds-session" or "group-sds-session" contained in an application/vnd.3gpp.mcdata-info+xml MIME body. Such requests are known as "SIP INVITE request for controlling MCData function for SDS session".
+
+### 6.3.2 Sending SIP requests and receiving SIP responses
+
+#### 6.3.2.1 Generating a SIP MESSAGE request towards the terminating MCData client
+
+This clause is referenced from other procedures. Refer to 3GPP TS 24.282 [82] clause 6.3.2.1.
+
+### 6.3.3 Groups homed in the IWF
+
+How information about groups homed in the IWF is stored and retrieved by the IWF is out of scope of the present document. The procedures to perform these actions are supported by the IWF but are not defined.
+
+### 6.3.4 Void
+
+### 6.3.5 Affiliation check
+
+The IWF shall determine that the MCData user, with MCData ID, is affiliated to the MCData group, with MCData Group ID, at the MCData client, with MCData client ID, if the elements, as described in clause 8.3.3.2, exist with their expected values, as below:
+
+- 1) an MCData group information entry with MCData group ID same as the MCData group ID under consideration;
+- 2) in the MCData group information entry found in 1, an MCData user information entry with the MCData ID same as the MCData ID under consideration;
+- 3) in the MCData user information entry found in 2, an MCData client information entry with MCData Client ID same as the MCData client ID under consideration; and
+- 4) in the MCData user information entry found in 2, an expiration time, which has not expired.
+
+NOTE: How the IWF determines which users homed in the IWF are affiliated to the MCData group is out of scope of the present document.
+
+## 6.4 Handling of MIME bodies in a SIP message
+
+The IWF shall support MIME bodies in SIP requests and SIP responses according to 3GPP TS 24.282 [82] clause 6.4.
+
+## 6.5 Confidentiality and Integrity Protection of sensitive XML content
+
+### 6.5.1 General
+
+#### 6.5.1.1 Applicability and exclusions
+
+The procedures in clause 6.5 apply in general to all procedures described in clause 9, clause 12 and clause 13 with the exception that the confidentiality and integrity protection procedures for the registration and service authorisation procedures are described in clause 7.
+
+#### 6.5.1.2 Performing XML content encryption
+
+Whenever the IWF includes XML elements or attributes pertaining to the data specified in clause 4.6 in SIP requests or SIP responses, the IWF shall perform the procedures in clause 6.5.2.3.2, with the exception that when the IWF receives a SIP request with XML elements or attributes in an MIME body that need to be copied from the incoming SIP request to an outgoing SIP request without modification, the IWF shall perform the procedures specified in clause 6.5.2.5.
+
+#### 6.5.1.3 Performing integrity protection on an XML body
+
+The IWF shall perform the procedures in clause 6.5.3.3.2 just prior to sending a SIP request or SIP response.
+
+### 6.5.2 Confidentiality Protection
+
+#### 6.5.2.2 Keys used in confidentiality protection procedures
+
+Confidentiality protection uses an XPK to encrypt the data which is an SPK as specified in clause 4.5. In the case of an IWF as a server sending or receiving to another server this key will be an SPK. An SPK-ID is used to key the SPK. It is assumed that before the procedures in this clause are called, the SPK/SPK-ID are available on the sender and recipient of the encrypted content as described in 3GPP TS 24.282 [82] clause 4.6.
+
+The procedures in clause 6.5.2.3 and 3GPP TS 24.282 [82] clause 6.5.2.4 are used with an XPK equal to the SPK and a XPK-ID equal to the SPK-ID when the IWF sends confidentiality protected content to an MCData server.
+
+#### 6.5.2.3 Procedures for sending confidentiality protected content
+
+##### 6.5.2.3.2 IWF performing the role of an MCData server
+
+If the IWF performing the role of an MCData server determines locally that it needs to confidentially protect content to an MCData server, then sending confidentially protected content between MCData servers is enabled.
+
+When sending confidentiality protected content, the IWF:
+
+- 1) shall use the appropriate keying information specified in clause 6.5.2.2;
+- 2) shall perform the procedures in 3GPP TS 24.282 [82] clause 6.5.2.3.3 to confidentiality protect XML elements containing the content described in clause 4.5; and
+- 3) shall perform the procedures in 3GPP TS 24.282 [82] clause 6.5.2.3.4 to confidentiality protect URIs in XML attributes for URIs described in clause 4.5.
+
+If the IWF determines locally that it does not need to confidentiality protect content sent to an MCData server, then sending confidentiality protected content between MCData servers is disabled, and the content is included in XML elements and attributes without encryption.
+
+#### 6.5.2.5 IWF copying received XML content
+
+The following procedure is executed when an IWF receives a SIP request containing XML MIME bodies, where the content needs to be copied from the incoming SIP request to the outgoing SIP request.
+
+The IWF:
+
+- 1) shall copy the XML elements from the XML MIME body of the incoming SIP request that do not contain a <EncryptedData> XML element, to the same XML body in the outgoing SIP request;
+- 2) for each encrypted XML element in the XML MIME body of the incoming SIP request as determined by 3GPP TS 24.282 [82] clause 6.5.2.4.1:
+  - a) shall use the keying information described in clause 6.5.2.2 to decrypt the content within the XML element by following the procedures specified in 3GPP TS 24.282 [82] clause 6.5.2.4.2, and shall continue with the steps below if the encrypted XML element was successfully decrypted;
+  - b) if confidentiality protection is enabled as specified in clause 6.5.2.3.2, then for each decrypted XML element:
+    - i) shall re-encrypt the content within the XML element using the keying information described in clause 6.5.2.2 and by following the procedures specified in 3GPP TS 24.282 [82] clause 6.5.2.3.3; and
+    - ii) shall include the re-encrypted content into the same XML MIME body of the outgoing SIP request; and
+  - c) if confidentiality protection is disabled as specified in clause 6.5.2.3.2, shall include the decrypted content in the same XML MIME body of the outgoing SIP request; and
+- 3) for each encrypted XML URI attribute in the XML MIME body of the incoming SIP request as determined by 3GPP TS 24.282 [82] clause 6.5.2.4.1:
+  - a) shall use the keying information described in clause 6.5.2.2 to decrypt the URI value of the XML attribute by following the procedures specified in 3GPP TS 24.282 [82] clause 6.5.2.4.3, and shall continue with the steps below if the encrypted XML attribute value was successfully decrypted;
+  - b) if confidentiality protection is enabled as specified in clause 6.5.2.3.2, then for each decrypted XML element:
+    - i) shall re-encrypt the URI value of the XML attribute using the keying information described in clause 6.5.2.2 and by following the procedures specified in 3GPP TS 24.282 [82] clause 6.5.2.3.4; and
+    - ii) shall include the re-encrypted attribute value into the same XML MIME body of the outgoing SIP request; and
+
+- c) if confidentiality protection is disabled as specified in clause 6.5.2.3.2, shall include the decrypted value in the same XML MIME body of the outgoing SIP request.
+
+### 6.5.3 Integrity Protection of XML documents
+
+#### 6.5.3.2 Keys used in integrity protection procedures
+
+Integrity protection uses an XPK to sign the data which is an SPK as specified in clause 4.5. In the case of an IWF as a server sending or receiving to another server this key will be an SPK. An SPK-ID is used to key the SPK. It is assumed that before the procedures in clause 6.5.3.3 and 3GPP TS 24.282 [82] clauses 6.5.3.3.1, 6.5.3.3.3 and 6.5.3.4 are called, the SPK/SPK-ID are available on the sender and recipient of the integrity protected content, as described in clause 4.5.
+
+The procedure in clause 6.5.3.3 and 3GPP TS 24.282 [82] clause 6.5.3.4 shall be used with a XPK equal to the SPK and a XPK-ID equal to the SPK-ID when the IWF sends integrity protected content to an MCData server
+
+#### 6.5.3.3 Sending integrity protected content
+
+##### 6.5.3.3.2 Integrity protection at the IWF
+
+The IWF determines locally whether sending integrity protected content from the IWF to an MCData server is enabled.
+
+When sending integrity protected content, the IWF shall use the appropriate keying information specified in clause 6.5.3.2 and shall perform the procedures in 3GPP TS 24.282 [82] clause 6.5.3.3.3 to integrity protect XML MIME bodies.
+
+NOTE: Each XML MIME body is integrity protected separately.
+
+## 6.6 Confidentiality and integrity protection of TLV messages
+
+### 6.6.1 General
+
+Signalling plane provides confidentiality and integrity protection for the MCData data signalling and MCData data messages sent over the signalling plane. Signalling plane security also provides the authentication of MCData data messages.
+
+The signalling plane security is based on 3GPP MCData security solution including key management and end-to-end protection as defined in 3GPP TS 33.180 [78].
+
+Various keys and associated key identifiers protect the MCData data signalling and MCData data messages carried on the signalling plane.
+
+The MCData signalling messages sent and received by an IWF are on-network communications and do not include FD.
+
+The MCData data signalling messages may be:
+
+1. SDS SIGNALLING PAYLOAD;
+2. SDS NOTIFICATION; or
+3. COMMUNICATION RELEASE.
+
+The MCData data messages may be:
+
+1. DATA PAYLOAD.
+
+In an on-network MCData communication for an MCData group, if protection of MCData data messages is negotiated, the GMK and the GMK-ID of the MCData group protect the MCData data messages sent and received by the IWF acting on behalf of users homed in the IWF.
+
+In an on-network one-to-one MCData communications, if protection of MCData data messages is negotiated, the PCK and the PCK-ID protect the MCData data messages sent and received by the IWF acting on behalf of MCData clients
+
+homed in the IWF. The IWF acts as termination point for protection of one-to-one MCData data messages that are sent and received by the IWF acting on behalf of MCData clients homed in the IWF.
+
+The protection of MCData communications between the user homed in the IWF and the IWF acting on behalf of the user homed in the IWF is outside the scope of the present document.
+
+If protection of MCData data signalling messages between the IWF and another MCData function acting in a participating or controlling role is configured, the SPK and the SPK-ID protect the MCData data signalling messages sent and received between the IWF and that MCData function.
+
+The GMK and the GMK-ID are distributed to the IWF acting on behalf of users homed in the IWF using the group document subscription and notification procedure specified in 3GPP TS 24.481 [31].
+
+The PCK and the PCK-ID are generated by the IWF initiating the standalone SDS using signalling control plane.
+
+The SPK and the SPK-ID are configured in the IWF if it is acting as the participating MCData function or if it is acting as the controlling MCData function.
+
+The key material for creating and verifying the authentication signature (SSK, PVT and KPAK) is provisioned to the MCData clients by the KMS as specified in 3GPP TS 33.180 [78].
+
+### 6.6.2 Derivation of master keys for media and media control
+
+On-network MCData services employing the media plane are not supported by the IWF.
+
+### 6.6.3 Protection of MCData signalling and MCData messages
+
+#### 6.6.3.1 General
+
+The MCData messages may be encrypted and integrity protected between the IWF and the MCData system. When encryption is applied the media shall be encrypted as specified in 3GPP TS 33.180 [78].
+
+Both unprotected MCData messages and MCData messages that are encrypted and/or integrity protected can also be end-to-end encrypted for interworking between an MCData client and the IWF.
+
+NOTE: LMR end to end encryption is independent of 3GPP encryption and is out of scope of the present document.
+
+# --- 7 Registration and service authorisation
+
+## 7.1 Server procedures
+
+How users homed in the IWF are registered and service authorized is out of scope of the present document.
+
+# --- 8 Affiliation
+
+## 8.1 General
+
+Clause 8.2 describes the procedures for explicit affiliation by a user homed in the IWF.
+
+Clause 8.3 contains the IWF procedures for handling explicit affiliation by:
+
+- an MCData client to a group homed in the IWF; and
+- an IWF on behalf of a user homed in the IWF towards an MCData server owning an MCData group.
+
+Clause 8.3 contains the IWF procedures for handling implicit affiliation by:
+
+- an MCData client to a group homed in the IWF; and
+- an IWF on behalf of a user homed in the IWF towards an MCData server owning an MCData group.
+
+The procedures for implicit affiliation in this clause are triggered at the IWF performing the participating role in the following circumstances:
+
+- when generating a SIP MESSAGE request on behalf of a user homed in the IWF to initiate an MCData emergency alert targeted to an MCData group and the user homed in the IWF is not already affiliated to that MCData group.
+
+The procedures for implicit affiliation in this clause are triggered at the IWF performing the controlling role in the following circumstances:
+
+- on receipt of a SIP MESSAGE request from the participating MCData function when the MCData user initiates an MCData emergency alert targeted to an MCData group and the MCData client is not already affiliated to the MCData group.
+
+Clause 8.4 describes the coding used for explicit affiliation.
+
+## 8.2 IWF performing the participating role procedures
+
+The IWF acts on behalf of all users homed in the IWF. There are no client procedures specified in the present document and specific client handling within the LMR system is out of scope.
+
+## 8.3 Server procedures
+
+### 8.3.1 General
+
+The procedures performed by the IWF in the role of the MCData server consist of:
+
+- procedures of the IWF performing the participating role; and
+- procedures of the IWF performing the controlling role.
+
+### 8.3.2 Procedures of the IWF performing the participating role
+
+#### 8.3.2.1 General
+
+The procedures of the IWF serving users homed in the IWF provide:
+
+- sending affiliation status change towards the MCData server owning an MCData group in clause 8.3.2.6;
+- affiliation status retrieval from the MCData server owning an MCData group in clause 8.3.2.7;
+- authorizing affiliation status change request in negotiated mode sent to a user homed in the IWF in clause 8.3.2.8;
+- affiliation status determination in clause 8.3.2.11;
+- affiliation status change by implicit affiliation in clause 8.3.2.12;
+- implicit affiliation status change completion in clause 8.3.2.13;
+- implicit affiliation status change cancellation in clause 8.3.2.14; and
+- automatic affiliation to configured groups in clause 8.3.2.15.
+
+#### 8.3.2.2 Stored information
+
+The IWF maintains information equivalent to that defined in 3GPP TS 24.282 [82] clause 8.3.2.2.
+
+NOTE: The virtual data structure referenced in this clause is for information only. Implementors may choose other means to track affiliation status for users homed in the IWF. References to the elements of this virtual data structure are made in other clauses with the understanding that implementors choosing not to use this virtual data structure will take other appropriate actions.
+
+#### 8.3.2.3 Receiving affiliation status change from a user homed in the IWF procedure
+
+Any notification of the IWF by users homed in the IWF of changes in their affiliation status is out of scope of 3GPP.
+
+#### 8.3.2.4 Receiving subscription to affiliation status procedure
+
+Any notification of users homed in the IWF of their affiliation status is out of scope of 3GPP.
+
+#### 8.3.2.5 Sending notification of change of affiliation status procedure
+
+Any notification of users homed in the IWF of their affiliation status is out of scope of 3GPP.
+
+#### 8.3.2.6 Sending affiliation status change towards MCData server owning MCData group procedure
+
+NOTE 1: Usage of one SIP PUBLISH request to carry information about change of affiliation state of several users homed in the IWF served by the same IWF is not supported in this version of the specification.
+
+In order:
+
+- to send an affiliation request of a served MCData ID to a handled MCData group ID;
+- to send an de-affiliation request of a served MCData ID from a handled MCData group ID; or
+- to send an affiliation request of a served MCData ID to a handled MCData group ID due to near expiration of the previously published information;
+
+the IWF performing the participating role shall generate a SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51]. In the SIP PUBLISH request, the IWF performing the participating role:
+
+- 1) shall set the Request-URI to the public service identity of the controlling MCData function associated with the handled MCData group ID;
+- 2) shall include an application/vnd.3gpp.mcdata-info+xml MIME body. In the application/vnd.3gpp.mcdata-info+xml MIME body, the MCData server:
+  - a) shall include the <mcdata-request-uri> element set to the handled MCData group ID; and
+  - b) shall include the <mcdata-calling-user-id> element set to the served MCData ID;
+- 3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
+- 4) if sending an affiliation request, shall set the Expires header field according to IETF RFC 3903 [37], to 4294967295;
+
+NOTE 2: 4294967295, which is equal to  $2^{32}-1$ , is the highest value defined for Expires header field in IETF RFC 3261 [24].
+
+- 5) if sending a de-affiliation request, shall set the Expires header field according to IETF RFC 3903 [37] to zero;
+- 6) shall include a P-Asserted-Identity header field set to the public service identity of the IWF performing the role of the MCData server according to 3GPP TS 24.229 [4];
+- 7) shall set the current p-id to a globally unique value;
+- 8) shall consider an MCData user information entry such that:
+
+- a) the MCData user information entry is in the list of MCData user information entries described in clause 8.3.2.2; and
+  - b) the MCData ID of the MCData user information entry is equal to the served MCData ID;
+- as the served MCData user information entry;
+- 9) for each MCData group information entry such that:
+    - a) the MCData group information entry has the "affiliating" affiliation status, the MCData group ID set to the handled MCData group ID, the expiration time has not expired yet and the affiliating p-id is not set;
+    - b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry; and
+    - c) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry;
+
+shall set the affiliating p-id of the MCData group information entry to the current p-id; and
+
+- 10) shall include an application/pidf+xml MIME body indicating per-group affiliation information constructed according to TS 24.282 [82] clause 8.4.1. The IWF performing the role of the MCData server shall indicate all served MCData client IDs, such that:
+  - a) the affiliation status is set to "affiliating" or "affiliated", and the expiration time has not expired yet in an MCData group information entry with the MCData group ID set to the handled MCData group;
+  - b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry;
+  - c) the MCData client information entry has the MCData client ID set to the served MCData client ID; and
+  - d) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry.
+
+The IWF performing the participating role shall set the <p-id> child element of the <presence> root element to the current p-id.
+
+The IWF performing the participating role shall not include the "expires" attribute in the <affiliation> element.
+
+The IWF performing the participating role shall send the SIP PUBLISH request according to 3GPP TS 24.229 [4].
+
+If timer F expires for the SIP PUBLISH request sent for a (de)affiliation request of served MCData ID to the MCData group ID or upon receiving a SIP 3xx, 4xx, 5xx or 6xx response to the SIP PUBLISH request, the IWF performing the participating role:
+
+- 1) shall remove each MCData group ID entry such that:
+  - a) the MCData group information entry has the MCData group ID set to the handled MCData group ID;
+  - b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry; and
+  - c) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry.
+
+#### 8.3.2.7 Affiliation status retrieval from IWF performing the role of the MCData server owning MCData group procedure
+
+NOTE 1: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCData users served by the same IWF performing the role of the MCData server is not supported in this version of the specification.
+
+In order to discover whether a served user homed in the IWF was successfully affiliated to a handled MCData group in the MCData server owning the handled MCData group, the IWF performing the role of the MCData server shall
+
+generate an initial SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26].
+
+In the SIP SUBSCRIBE request, the IWF performing the role of the MCData server:
+
+- 1) shall set the Request-URI to the public service identity of the controlling MCData function associated with the handled MCData group ID;
+- 2) shall include an application/vnd.3gpp.mcdata-info+xml MIME body. In the application/vnd.3gpp.mcdata-info+xml MIME body, the IWF performing the role of the MCData server:
+  - a) shall include the <mcdata-request-uri> element set to the handled MCData group ID; and
+  - b) shall include the <mcdata-calling-user-id> element set to the served MCData ID;
+- 3) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
+- 4) if the IWF performing the role of the MCData server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
+
+NOTE 2: 4294967295, which is equal to  $2^{32}-1$ , is the highest value defined for Expires header field in IETF RFC 3261 [24].
+
+- 5) if the IWF performing the role of the MCData server wants to fetch the current state only, shall set the Expires header field according to IETF RFC 6665 [26], to zero;
+- 6) shall include an Accept header field containing the application/pidf+xml MIME type; and
+- 7) shall include an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to 3GPP TS 24.282 [82] clause 8.4.2, indicating the served MCData ID.
+
+In order to re-subscribe or de-subscribe, the IWF performing the role of MCData server shall generate an in-dialog SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26]. In the SIP SUBSCRIBE request, the IWF performing the role of the MCData server:
+
+- 1) if the IWF performing the role of the MCData server wants to receive the current status and later notification, shall set the Expires header field according to IETF RFC 6665 [26], to 4294967295;
+
+NOTE 3: 4294967295, which is equal to  $2^{32}-1$ , is the highest value defined for Expires header field in IETF RFC 3261 [24].
+
+- 2) if the IWF performing the role of the MCData server wants to de-subscribe, shall set the Expires header field according to IETF RFC 6665 [26], to zero; and
+- 3) shall include an Accept header field containing the application/pidf+xml MIME type.
+
+Upon receiving a SIP NOTIFY request according to 3GPP TS 24.229 [4], IETF RFC 3856 [51], and IETF RFC 6665 [26], if SIP NOTIFY request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to 3GPP TS 24.282 [82], clause 8.4.1, then the IWF performing the role of the MCData server:
+
+- 1) for each served MCData ID and served MCData client ID such that the application/pidf+xml MIME body of SIP NOTIFY request contains:
+  - a) a <tuple> element of the root <presence> element;
+  - b) the "id" attribute of the <tuple> element indicating the served MCData ID;
+  - c) an <affiliation> child element of the <status> element of the <tuple> element;
+  - d) the "client" attribute of the <affiliation> element indicating the served MCData client ID; and
+  - d) the "expires" attribute of the <affiliation> element indicating expiration of affiliation;perform the following:
+
+- a) if an MCData group information entry exists such that:
+  - i) the MCData group information entry has the "affiliating" affiliation status, the MCData group ID set to the handled MCData group ID, and the expiration time has not expired yet;
+  - ii) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry with the MCData client ID set to the served MCData client ID;
+  - iii) the MCData client information entry is in the list of the MCData client information entries of a served MCData user information entry with the MCData ID set to the served MCData ID; and
+  - iv) the MCData user information entry is in the list of MCData user information entries described in clause 8.3.2.2; and
+
+shall set the affiliation status of the MCData group information entry to "affiliated"; and
+
+shall set the next publishing time of the MCData group information entry to the current time and half of the time between the current time and the expiration of affiliation; and
+
+2) for each MCData group information entry such that:
+
+- a) the MCData group information entry has the "affiliated" affiliation status or the "deaffiliating" affiliation status, the MCData group ID set to the handled MCData group ID, and the expiration time has not expired yet;
+- b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry with the MCData client ID set to a served MCData client ID;
+- c) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry with the MCData ID set to a served MCData ID; and
+- d) the MCData user information entry is in the list of MCData user information entries described in clause 8.3.2.2; and
+
+for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
+
+- a) a <tuple> element of the root <presence> element;
+- b) the "id" attribute of the <tuple> element indicating the served MCData ID;
+- c) an <affiliation> child element of the <status> child element of the <tuple> element; and
+- d) the "client" attribute of the <affiliation> element indicating the served MCData client ID.
+
+perform the following:
+
+- a) shall set the affiliation status of the MCData group information entry to "deaffiliated"; and
+- b) shall set the expiration time of the MCData group information entry to the current time; and
+
+3) if a <p-id> element is included in the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request, then for each MCData group information entry such that:
+
+- a) the MCData group information entry has the "affiliating" affiliation status, the MCData group ID set to the handled MCData group ID, the expiration time has not expired yet and with the affiliating p-id set to the value of the <p-id> element;
+- b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry with the MCData client ID set to a served MCData client ID;
+- c) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry with the MCData ID set to a served MCData ID; and
+- d) the MCData user information entry is in the list of MCData user information entries described in clause 8.3.2.2; and
+
+for which the application/pidf+xml MIME body of SIP NOTIFY request does not contain:
+
+- a) a <tuple> element of the root <presence> element;
+- b) the "id" attribute of the <tuple> element indicating the served MCData ID;
+- c) an <affiliation> child element of the <status> child element of the <tuple> element; and
+- d) the "client" attribute of the <affiliation> element indicating the served MCData client ID;
+
+perform the following:
+
+- a) shall set the affiliation status of the MCData group information entry to "deaffiliated"; and
+- b) shall set the expiration time of the MCData group information entry to the current time.
+
+#### 8.3.2.8 Procedure for authorising affiliation status change request in negotiated mode sent to a user homed in the IWF
+
+Authorising affiliation status change request in negotiated mode sent to a user homed in the IWF is not supported in the present document.
+
+#### 8.3.2.9 Forwarding affiliation status change towards an MCData user procedure
+
+The procedure for forwarding affiliation status change towards an MCData user is not supported in the present specification.
+
+#### 8.3.2.10 Forwarding subscription to affiliation status towards an MCData user procedure
+
+The procedure for forwarding a subscription to affiliation status towards an MCData user is not supported in the present specification.
+
+#### 8.3.2.11 Affiliation status determination
+
+This clause is referenced from other procedures.
+
+If the IWF performing the participating role needs to determine the affiliation status of an user homed in the IWF to an MCData group, the IWF performing the participating role:
+
+- 1) shall find the user information entry in the list of MCData user information entries described in clause 8.3.2.2 such that the MCData ID of the MCData user information entry is equal to the MCData ID associated with the user homed in the IWF;
+  - a) if the applicable MCData user information entry cannot be found, then the IWF performing the participating role shall determine that the user homed in the IWF is not affiliated to the MCData group and skip the rest of the steps;
+- 2) shall find the MCData client information entry in the list of MCData client information entries of MCData user information entry found in step 1) in which the MCData client ID matches the MCData client ID associated with the user homed in the IWF;
+  - a) if the applicable MCData client information entry cannot be found, then the IWF performing the participating role shall determine that the user homed in the IWF is not affiliated to the MCData group and skip the rest of the steps; and
+- 3) shall find the MCData group information entry in the list of MCData group information entries of MCData client information entry found in step 2 such that the MCData group identity matches the value of the identity of the targeted MCData group;
+  - a) if the applicable MCData group information entry was found in step 3) and the affiliation status of the MCData group information entry is "affiliating" or "affiliated", shall determine that the user homed in the IWF is affiliated to the targeted MCData group and skip the rest of the steps;
+
+- b) if the applicable MCData group information entry was found in step 3) and the affiliation status of the MCData group information entry is "deaffiliating" or "deaffiliated", shall determine that the user homed in the IWF is not affiliated to the targeted MCData group and skip the rest of the steps; or
+- c) if the applicable MCData group information entry was not found in step 3), shall determine that the user homed in the IWF is not affiliated to the targeted MCData group.
+
+#### 8.3.2.12 Affiliation status change by implicit affiliation
+
+This clause is referenced from other procedures.
+
+Upon determining that implicit affiliation of a user homed in the IWF is required to an MCData group, the IWF performing the participating role:
+
+- 1) shall determine the MCData client ID of the user homed in the IWF;
+- 2) shall determine the MCData group ID to which the user homed in the IWF is to be affiliated;
+- 3) shall determine the MCData ID associated with the user homed in the IWF;
+- 4) shall consider an MCData user information entry such that:
+  - a) the MCData user information entry is in the list of MCData user information entries described in clause 8.3.2.2;
+  - b) the MCData ID of the MCData user information entry is equal to the MCData ID determined in step 3; as the served MCData user information entry;
+- 5) shall consider an MCData client information entry such that:
+  - a) the MCData client information entry is in the list of MCData client information entries of the served MCData user information entry; and
+  - b) the MCData client ID of the MCData client information entry is equal to the served MCData client ID; as the served MCData client information entry;
+- 6) shall consider a copy of the list of the MCData group information entries of the served MCData client information entry as the served list of the MCData group information entries;
+- 7) shall construct the candidate list of the MCData group information entries as follows:
+  - a) for each MCData group ID which has an MCData group information entry in the served list of the MCData group information entries shall copy the MCData group information entry into a new MCData group information entry of the candidate list of the MCData group information entries; and
+  - b) if the determined MCData group ID does not have an MCData group information entry in the served list of the MCData group information entries or has an MCData group information entry in the served list of the MCData group information entries, such that the expiration time of the MCData group information entry has already expired:
+    - i) shall add a new MCData group information entry in the candidate list of the MCData group information list for the determined MCData group ID;
+    - ii) shall set the affiliation status of the new MCData group information entry to the "affiliating" state; and
+    - iii) shall set the expiration time of the new MCData group information entry to the current time increased with the candidate expiration interval;
+- 8) determine the candidate number of MCData group IDs as the number of different MCData group IDs which have an MCData group information entry:
+  - a) in the candidate list of the MCData group information entries; or
+  - b) in the list of the MCData group information entries of an MCData client information entry such that:
+
+- i) the MCData client information entry is in the list of the MCData client information entries of the served MCData user information entry; and
+- ii) the MCData client ID of the MCData client information entry is not equal to the served MCData client ID;
+
+with the affiliation status set to the "affiliating" state or the "affiliated" state and with the expiration time which has not expired yet; and
+
+- 9) if the candidate number of MCData group IDs is bigger than a maximum limit associated by the IWF to the user homed in the IWF, shall, based on MCData service provider policy, reduce the candidate MCData group IDs to that maximum value;
+- 10) if the determined MCData group ID cannot be added to the the candidate list of the MCData group information entries due to exceeding the maximum limit associated with the user homed in the IWF, shall discard the candidate list of the MCData group information entries and skip the remaining steps of the current procedure; and
+- 11) shall replace the list of the MCData group information entries stored in the served MCData client information entry with the candidate list of the MCData group information entries.
+
+#### 8.3.2.13 Implicit affiliation status change completion
+
+This clause is referenced from other procedures.
+
+If the IWF performing the participating role has received a SIP 2xx response from the controlling MCData function to a SIP request that had triggered performing the procedures of clause 8.3.2.12, the IWF performing the participating role:
+
+- 1) shall set the affiliation status of the MCData group information entry added to the candidate list of the MCData group information entries by the procedures of clause 8.3.2.12 to "affiliated".
+
+#### 8.3.2.14 Implicit affiliation status change cancellation
+
+This clause is referenced from other procedures.
+
+If the IWF performing the participating role receives a SIP 4xx, 5xx or 6xx response from the controlling MCData function for an implicit affiliation status change operation, the IWF performing the participating role:
+
+- 1) shall remove the MCData group ID entry added by the procedures of clause 8.3.2.12 such that:
+  - a) the MCData group information entry has the MCData group ID set to the MCData group ID of the MCData group associated with the received SIP 4xx, 5xx, or 6xx response;
+  - b) the MCData group information entry is in the list of the MCData group information entries of an MCData client information entry containing the MCData client ID determined in the execution of the procedure in clause 8.3.2.12; and
+  - c) the MCData client information entry is in the list of the MCData client information entries of the MCData user information entry containing the MCData ID associated with the user homed in the IWF.
+
+#### 8.3.2.15 Automatic affiliation to configured groups procedure
+
+This clause is referenced from other procedures.
+
+When the IWF performing the participating role determines that automatic affiliation of a user homed in the IWF to configured groups is needed, the IWF shall perform the procedures specified in clause 8.3.2.6 for the served MCData ID and each configured MCData group ID.
+
+### 8.3.3 Procedures of the IWF performing the controlling role
+
+#### 8.3.3.1 General
+
+The procedures of the IWF performing the controlling role consist of:
+
+- receiving group affiliation status change procedure;
+- receiving subscription to affiliation status procedure;
+- sending notification of change of affiliation status procedure;
+- implicit affiliation eligibility check procedure; and
+- affiliation status change by implicit affiliation procedure.
+
+#### 8.3.3.2 Stored information
+
+The IWF maintains information equivalent to that defined in 3GPP TS 24.282 [82], clause 8.3.3.2.
+
+NOTE: The virtual data structure referenced in this clause is for information only. Implementors can choose other means to track affiliation status for users homed in the IWF. References to the elements of this virtual data structure are made in other clauses with the understanding that implementors choosing not to use this virtual data structure will take other appropriate actions.
+
+#### 8.3.3.3 Receiving group affiliation status change procedure
+
+Upon receiving a SIP PUBLISH request such that:
+
+- 1) Request-URI of the SIP PUBLISH request contains the public service identity of the IWF performing the controlling role associated with the served MCData group;
+- 2) the SIP PUBLISH request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the <mcdata-request-uri> element and the <mcdata-calling-user-identity> element;
+- 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
+- 4) the Event header field of the SIP PUBLISH request contains the "presence" event type; and
+- 5) SIP PUBLISH request contains an application/pidf+xml MIME body indicating per-group affiliation information constructed according to clause 8.4.1;
+
+then the IWF performing the controlling role:
+
+- 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request;
+- 2) shall identify the handled MCData ID in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP PUBLISH request;
+- 3) if the Expires header field of the SIP PUBLISH request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP PUBLISH request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
+- 4) if an MCData group for the served MCData group ID is not available to the IWF performing the controlling role, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
+- 5) if the handled MCData ID is not a member of the MCData group identified by the served MCData group ID, shall reject the SIP PUBLISH request with SIP 403 (Forbidden) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
+- 6) shall respond with SIP 200 (OK) response to the SIP PUBLISH request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37]. In the SIP 200 (OK) response, the IWF performing the controlling role:
+  - a) shall set the Expires header field according to IETF RFC 3903 [37], to the selected expiration time;
+- 7) if the "entity" attribute of the <presence> element of the application/pidf+xml MIME body of the SIP PUBLISH request is different than the served MCData group ID, shall not continue with the rest of the steps;
+
+- 8) if the handled MCData ID is different from the MCData ID in the "id" attribute of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request, shall not continue with the rest of the steps;
+- 9) shall consider an MCData group information entry such that:
+  - a) the MCData group information entry is in the list of MCData group information entries described in clause 8.3.3.2; and
+  - b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID; as the served MCData group information entry;
+- 10) if the selected expiration time is zero:
+  - a) shall remove the MCData user information entry such that:
+    - i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and
+    - ii) the MCData user information entry has the MCData ID set to the served MCData ID;
+- 11) if the selected expiration time is not zero:
+  - a) shall consider an MCData user information entry such that:
+    - i) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and
+    - ii) the MCData ID of the MCData user information entry is equal to the handled MCData ID; as the served MCData user information entry;
+  - b) if the MCData user information entry does not exist:
+    - i) shall insert an MCData user information entry with the MCData ID set to the handled MCData ID into the list of the MCData user information entries of the served MCData group information entry; and
+    - ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and
+  - c) shall set the following information in the served MCData user information entry:
+    - i) set the MCData client ID list according to the "client" attributes of the <affiliation> elements of the <status> element of the <tuple> element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
+    - ii) set the expiration time according to the selected expiration time;
+- 12) shall identify the handled p-id in the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP PUBLISH request; and
+- 13) shall perform the procedures specified in clause 8.3.3.5 for the served MCData group ID.
+
+#### 8.3.3.4 Receiving subscription to affiliation status procedure
+
+NOTE: Usage of one SIP SUBSCRIBE request to subscribe for notification about change of affiliation state of several MCData users served by the same MCData server is not supported in this version of the specification.
+
+Upon receiving a SIP SUBSCRIBE request such that:
+
+- 1) Request-URI of the SIP SUBSCRIBE request contains the public service identity of the IWF performing the controlling role associated with the served MCData group;
+- 2) the SIP SUBSCRIBE request contains an application/vnd.3gpp.mcdata-info+xml MIME body containing the <mcdata-request-uri> element and the <mcdata-calling-user-identity> element;
+
+- 3) the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service header field according to IETF RFC 6050 [9];
+- 4) the Event header field of the SIP SUBSCRIBE request contains the "presence" event type; and
+- 5) the SIP SUBSCRIBE request contains an application/simple-filter+xml MIME body indicating per-user restrictions of presence event package notification information according to clause 8.4.2 indicating the same MCData ID as in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request;
+
+then the IWF performing the controlling role:
+
+- 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request;
+- 2) shall identify the handled MCData ID in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP SUBSCRIBE request;
+- 3) if the Expires header field of the SIP SUBSCRIBE request is not included or has nonzero value lower than 4294967295, shall send a SIP 423 (Interval Too Brief) response to the SIP SUBSCRIBE request, where the SIP 423 (Interval Too Brief) response contains a Min-Expires header field set to 4294967295, and shall not continue with the rest of the steps;
+- 4) if an MCData group for the served MCData group ID is not available to the IWF performing the controlling role, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps;
+- 5) if the handled MCData ID is not a member of the MCData group identified by the served MCData group ID, shall reject the SIP SUBSCRIBE request with SIP 403 (Forbidden) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 3903 [37] and IETF RFC 3856 [51] and skip the rest of the steps; and
+- 6) shall generate a SIP 200 (OK) response to the SIP SUBSCRIBE request according to 3GPP TS 24.229 [4], IETF RFC 6665 [26].
+
+For the duration of the subscription, the IWF shall notify subscriber about changes of the information of the served MCData ID, as described in clause 8.3.3.5.
+
+#### 8.3.3.5 Sending notification of change of affiliation status procedure
+
+In order to notify the subscriber identified by the handled MCData ID about changes of the affiliation status of the served MCData group ID, the IWF:
+
+- 1) shall consider an MCData group information entry such that:
+  - a) the MCData group information entry is in the list of MCData group information entries described in clause 8.3.3.2; and
+  - b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID;
+- 2) shall consider an MCData user information entry such:
+  - a) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and
+  - b) the MCData ID of the MCData user information entry is equal to the handled MCData ID;as the served MCData user information entry;
+- 3) shall generate an application/pidf+xml MIME body indicating per-group affiliation information according to clause 8.4.1 and the served list of the served MCData user information entry of the MCData group information entry with following clarifications:
+  - a) the IWF shall include the "expires" attribute in the <affiliation> element; and
+
+- b) if this procedure is invoked by procedure in clause 8.3.3.3 where the handled p-id was identified, the IWF shall set the <p-id> child element of the <presence> root element of the application/pidf+xml MIME body of the SIP NOTIFY request to the handled p-id value; and
+- 4) send a SIP NOTIFY request according to 3GPP TS 24.229 [4], and IETF RFC 6665 [26] for the subscription created in clause 8.3.3.4. In the SIP NOTIFY request, the IWF shall include the generated application/pidf+xml MIME body indicating per-group affiliation information.
+
+#### 8.3.3.6 Implicit affiliation eligibility check procedure
+
+This clause is referenced from other procedures.
+
+Upon receiving a SIP request for an MCData group that the MCData user is not currently affiliated to and that requires the IWF performing the controlling role to check on the eligibility of the MCData user to be implicitly affiliated to the MCData group, the IWF performing the controlling role:
+
+- 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request;
+- 2) shall identify the handled MCData ID in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request;
+- 3) if an MCData group for the served MCData group ID is not available to the IWF performing the controlling role, shall consider the MCData user to be ineligible for implicit affiliation and skip the rest of the steps;
+- 4) if the handled MCData ID is not a member of the MCData group identified by the served MCData group ID, shall consider the MCData user to be ineligible for implicit affiliation and skip the rest of the steps;
+- 5) if there is no MCData group information entry in the list of MCData group information entries described in clause 8.3.3.2 with an MCData group identity matching the served MCData group ID, then shall consider the MCData user to be ineligible for implicit affiliation and skip the rest of the steps; or
+- 6) shall consider the MCData user to be eligible for implicit affiliation.
+
+#### 8.3.3.7 Affiliation status change by implicit affiliation procedure
+
+This clause is referenced from other procedures.
+
+Upon receiving a SIP request for an MCData group that the MCData user is not currently affiliated to and that requires the IWF performing the controlling role to perform an implicit affiliation to, the IWF performing the controlling role:
+
+- 1) shall identify the served MCData group ID in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request;
+- 2) shall identify the handled MCData ID in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP request;
+- 3) shall consider an MCData group information entry such that:
+  - a) the MCData group information entry is in the list of MCData group information entries described in clause 8.3.3.2; and
+  - b) the MCData group ID of the MCData group information entry is equal to the served MCData group ID;as the served MCData group information entry;
+- 4) shall consider an MCData user information entry such that:
+  - a) the MCData user information entry is in the list of the MCData user information entries of the served MCData group information entry; and
+  - b) the MCData ID of the MCData user information entry is equal to the handled MCData ID;as the served MCData user information entry;
+
+- c) if the MCData user information entry does not exist:
+    - i) shall insert an MCData user information entry with the MCData ID set to the handled MCData ID into the list of the MCData user information entries of the served MCData group information entry; and
+    - ii) shall consider the inserted MCData user information entry as the served MCData user information entry; and
+  - d) shall make the following modifications in the served MCData user information entry:
+    - i) add the MCData client ID derived from the received SIP request to the MCData client ID list if not already present; and
+    - ii) set the expiration time as determined by local policy; and
+- 5) shall perform the procedures specified in clause 8.3.3.5 for the served MCData group ID.
+
+## 8.4 Coding
+
+The IWF shall support the coding specified in 3GPP TS 24.282 [82] clause 8.4.
+
+# --- 9 IWF Short Data Service (SDS)
+
+## 9.1 General
+
+The group administrator can disable the SDS service on a MCData group by setting the <mcdata-allow-short-data-service> element under the <list-service> element, in the group document as defined in 3GPP TS 24.481 [31], to "false".
+
+If the <mcdata-allow-short-data-service> element under the <list-service> element, in the group document, is set to "false" for an MCData group:
+
+- an IWF shall not send an SDS to the said MCData group; and
+- an IWF performing the terminating MCData controlling role shall reject a request to send SDS to the said MCData group.
+
+## 9.2 On-network SDS
+
+### 9.2.1 General
+
+On-network SDS employing the media plane is not supported by the IWF in the present document.
+
+### 9.2.2 Standalone SDS using signalling control plane
+
+#### 9.2.2.1 General
+
+The procedures in the subsequent clauses of clause 9.2.2 are used by the IWF to send or receive:
+
+- a one-to-one standalone SDS message using the signalling control plane; or
+- a group standalone SDS message using the signalling control plane.
+
+#### 9.2.2.2 Procedures used by the IWF for users homed in the IWF
+
+##### 9.2.2.2.1 Originating procedures
+
+The IWF shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
+
+The IWF:
+
+- 1) if a one-to-one standalone SDS message is to be sent, shall insert in the SIP MESSAGE request:
+    - a) an application/resource-lists+xml MIME body with the MCData ID of the target MCData user, according to rules and procedures of IETF RFC 4826 [89];
+    - b) an application/vnd.3gpp.mcdata-info+xml MIME body with a <request-type> element set to a value of "one-to-one-sds"; and
+    - c) if end-to-end security is required and the security context does not exist or if the existing security context has expired, an application/mikey MIME body with the MIKEY-SAKKE I\_MESSAGE as specified in 3GPP TS 33.180 [78]. The IWF:
+      - i) if necessary, shall determine keying material from the key management server;
+- NOTE: How the IWF obtains the keying material is out of scope of the present document.
+- ii) shall use the keying material to generate a PCK as described in 3GPP TS 33.180 [78];
+    - iii) shall use the PCK to generate a PCK-ID with the four most significant bits set to "0001" to indicate that the purpose of the PCK is to protect one-to-one communications and with the remaining twenty eight bits being randomly generated as described in 3GPP TS 33.180 [78];
+    - iv) shall encrypt the PCK to a UID associated to the MCData client using the MCData ID of the invited user and a time related parameter as described in 3GPP TS 33.180 [78];
+    - v) shall generate a MIKEY-SAKKE I\_MESSAGE using the encapsulated PCK and PCK-ID as specified in 3GPP TS 33.180 [78];
+    - vi) shall add the MCData ID associated with the originating user homed in the IWF to the initiator field (IDRi) of the I\_MESSAGE as described in 3GPP TS 33.180 [78];
+    - vii) shall sign the MIKEY-SAKKE I\_MESSAGE using the originating signing key determined by the IWF performing the role of an MCData server provided in the keying material together with a time related parameter; and
+    - viii) shall include the MIKEY-SAKKE I\_MESSAGE in an application/mikey MIME body as specified in 3GPP TS 33.180 [78];
+- 2) if a group standalone SDS message is to be sent:
+    - a) shall insert in the SIP MESSAGE request an application/vnd.3gpp.mcdata-info+xml MIME body with:
+      - i) the <request-type> element set to a value of "group-sds";
+      - ii) the <mcdata-request-uri> element set to the MCData group identity; and
+      - iii) the <mcdata-client-id> element set to the MCData client ID associated with the originating user homed in the IWF; and
+- 3) shall generate a standalone SDS message as specified in clause 6.2.2.1.
+
+##### 9.2.2.2.2 Terminating procedures
+
+Upon receipt of an SDS intended for a user homed in the IWF, the IWF processes the message according to the procedures in clause 9.2.2.3.2.
+
+#### 9.2.2.3 IWF performing the participating MCData function procedures
+
+##### 9.2.2.3.1 Originating participating MCData function procedures
+
+If the IWF acting in a participating MCData role determines that it needs to send an SDS message:
+
+- 1) shall determine the MCData ID of the originating user;
+- 2) shall determine the public service identity of the controlling MCData function associated with the requested SDS message:
+  - a) if the SDS message to be sent is a group SDS message the public service identity is that of the controlling MCData function associated with the MCData group identity of the destination group; or
+  - b) if the SDS message to be sent is a one-to-one SDS message the public service identity is that of the controlling MCData function hosting the one-to-one standalone SDS service for the calling user;
+
+NOTE 1: How the IWF determines the public service identity of the controlling MCData function is out of scope of the present document.
+
+- 3) if unable to identify the controlling MCData function for standalone SDS shall complete any further actions to notify the user homed in the IWF, and shall not continue with any of the remaining steps;
+- 4) shall ensure that the payload size of the message is not larger than a configured value compatible with the MCData service;
+
+NOTE 2: The term "payload size" refers to the "Length of Payload contents" of the payload IE of the DATA PAYLOAD message transported in the SIP MESSAGE request, minus 1 (to account for the added "Payload content type" field).
+
+NOTE 3: The configured value for maximum payload size should not be larger than the value contained in the <max-payload-size-sds-cplane-bytes> element in the MCData service configuration document as specified in 3GPP TS 24.484 [50]. How the IWF determines the value to configure is out of scope of the present document.
+
+- 5) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
+- 6) shall set the Request-URI of the outgoing SIP MESSAGE request to the public service identity of the controlling MCData function as determined by step 2) in this clause;
+- 7) shall include MIME bodies in to the outgoing SIP MESSAGE request according to clause 9.2.2.2.1;
+- 8) shall include the MCData ID of the originating user in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request;
+- 9) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" (coded as specified in 3GPP TS 24.229 [4]), into the P-Asserted-Service header field of the outgoing SIP MESSAGE request;
+- 10) shall set the P-Asserted-Identity in the outgoing SIP MESSAGE request to the public service identity of the IWF; and
+- 11) shall send the SIP MESSAGE request as specified in 3GPP TS 24.229 [4].
+
+Upon receipt of a SIP response in response to the SIP MESSAGE request in step 11) the IWF completes any further actions needed to handle the response – e.g. notify the user homed in the IWF.
+
+##### 9.2.2.3.2 IWF performing the terminating participating MCData role procedures
+
+Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the IWF performing the participating role:
+
+- 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The IWF may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24] and skip the rest of the steps;
+
+- 2) shall use the MCData ID present in the <mcdata-request-uri> element of the application/vnd.3gpp.mcdata-info+xml MIME body of the incoming SIP MESSAGE request to identify the user homed in the IWF;
+  - 3) if the user homed in the IWF does not exist, then the participating IWF may reject the SIP MESSAGE request with a SIP 404 (Not Found) response, and shall skip the remaining steps;
+  - 4) if the SIP MESSAGE request contains an application/mikey MIME body containing a MIKEY-SAKKE I\_MESSAGE and decryption of the content of the MIME body is to occur at the IWF, then the IWF:
+    - a) shall extract the MCData ID of the originating MCData user from the initiator field (IDRi) of the I\_MESSAGE as described in 3GPP TS 33.180 [78];
+    - b) shall convert the MCData ID to a UID as described in 3GPP TS 33.180 [78];
+    - c) shall use the UID to validate the signature of the MIKEY-SAKKE I\_MESSAGE as described in 3GPP TS 33.180 [78];
+    - d) if authentication verification of the MIKEY-SAKKE I\_MESSAGE fails, shall reject the SIP MESSAGE request with a SIP 606 (Not Acceptable) response, and include warning text set to "136 authentication of the MIKEY-SAKKE I\_MESSAGE failed" in a Warning header field as specified in clause 4.7 and not continue with rest of the steps in this clause; and
+    - e) if the signature of the MIKEY-SAKKE I\_MESSAGE was successfully validated:
+      - i) shall extract and decrypt the encapsulated PCK using the terminating user's (KMS provisioned) UID key as described in 3GPP TS 33.180 [78]; and
+      - ii) shall extract the PCK-ID, from the payload as specified in 3GPP TS 33.180 [78]; and
+- NOTE: Any trans-encryption between the IWF and the user homed in the IWF is out of scope of the present document.
+- 5) takes any further steps necessary to handle the message – e.g. notify the user homed in the IWF.
+
+If the IWF determines that a SIP 200 (OK) response shall be sent on behalf of a user homed in the IWF in response to the SIP message request, the IWF shall send a SIP 200 (OK) response to the controlling MCData function according to 3GPP TS 24.229 [4].
+
+If the IWF determines that a SIP 4xx, 5xx or 6xx response shall be sent on behalf of a user homed in the IWF in response to the SIP message request, the IWF shall send said SIP 4xx, 5xx or 6xx response to the controlling MCData function according to 3GPP TS 24.229 [4]:
+
+- 1) shall determine which Warning header field(s) to place in the SIP response; and
+- 2) shall send the SIP response to the controlling MCData function according to 3GPP TS 24.229 [4].
+
+#### 9.2.2.4 Controlling IWF MCData procedures
+
+##### 9.2.2.4.1 Originating controlling IWF procedures
+
+This clause describes the procedures for sending a SIP MESSAGE from the IWF performing the controlling role and is initiated by the IWF performing the role of a controlling MCData function as a result of an action in clause 9.2.2.4.2 or upon the determination by the IWF performing the controlling role that a SIP MESSAGE is to be sent on behalf of a user homed in the IWF.
+
+The controlling MCData function:
+
+- 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
+- 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6] in the outgoing SIP MESSAGE request;
+
+- 3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdta.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [6] in the outgoing SIP MESSAGE request;
+- 4) if the SIP MESSAGE is to be sent as the result of receiving a SIP MESSAGE originated by an MCData client, shall copy the following MIME bodies in the received SIP MESSAGE request into the outgoing SIP MESSAGE request by following the guidelines in clause 6.4; otherwise, if the SIP MESSAGE is to be sent on behalf of a user homed in the IWF, shall create the following MIME bodies in the outgoing SIP MESSAGE request by following the guidelines in clause 306.4 and the procedures in clause 9.2.2.2.1:
+  - a) application/vnd.3gpp.mcdta-info+xml MIME body;
+  - b) application/vnd.3gpp.mcdta-signalling MIME body; and
+  - c) application/vnd.3gpp.mcdta-payload MIME body
+- 5) in the application/vnd.3gpp.mcdta-info+xml MIME body:
+  - a) shall set the <mcdta-request-uri> element set to the MCData ID of the terminating user; and
+  - b) if the SIP MESSAGE is to be sent as the result of receiving a SIP MESSAGE originated by an MCData client, then if the <request-type> element in the application/vnd.3gpp.mcdta-info+xml MIME body of the incoming SIP MESSAGE request was set to a value of "group-sds", or if the SIP MESSAGE is to be sent on behalf of a user homed in the IWF and the IWF performing the controlling role determines that the outgoing SIP MESSAGE is associated with a group,
+    - i) shall set the <mcdta-calling-group-id> element to the group identity;
+- 6) shall set the Request-URI to the public service identity of the terminating participating MCData function associated to the MCData user to be invited;
+- 7) shall insert its own public service identity into the P-Asserted-Identity header field of the outgoing SIP MESSAGE request;
+- 8) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdta.sds"; and
+- 9) shall send the SIP MESSAGE request according to according to rules and procedures of 3GPP TS 24.229 [4].
+
+##### 9.2.2.4.2 Terminating controlling MCData function procedures
+
+Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the IWF performing the controlling role:
+
+- 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The IWF performing the controlling role may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
+- 2) if the SIP MESSAGE does not contain:
+  - a) an application/vnd.3gpp.mcdta-info+xml MIME body;
+  - b) an application/vnd.3gpp.mcdta-signalling MIME body; and
+  - c) an application/vnd.3gpp.mcdta-payload MIME body;shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response, with warning text set to "199 expected MIME bodies not in the request" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps in this clause;
+- 3) shall decode the contents of the application/vnd.3gpp.mcdta-signalling MIME body contained in the SIP MESSAGE;
+- 4) if the application/vnd.3gpp.mcdta-signalling MIME body contains a SDS SIGNALLING PAYLOAD message with a SDS disposition request type IE, shall store the value of the Conversation ID IE and the value of the Message ID IE in the SDS SIGNALLING PAYLOAD message;
+
+NOTE: The IWF performing the controlling role uses the Conversation ID and Message ID for correlation with disposition notifications.
+
+- 5) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "one-to-one-sds" and:
+  - a) the conditions in clause 11.1 indicate that the MCData user is not allowed to send SDS communications due to message size as determined by step 3) of clause 11.1, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "218 user not authorised for one-to-one SDS communications due to message size" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps in this clause; and
+  - b) the SIP MESSAGE request:
+    - i) does not contain an application/resource-lists MIME body or contains an application/resource-lists MIME body with more than one <entry> element, shall return a SIP 403 (Forbidden) response with the warning text set to "204 unable to determine targeted user for one-to-one SDS" in a Warning header field as specified in clause 4.7, and skip the rest of the steps below; and
+    - ii) contains an application/resource-lists MIME body with exactly one <entry> element, shall send a SIP MESSAGE request to the MCData user identified in the <entry> element of the MIME body, as specified in clause 9.2.2.4.1, or if the MCData user identified in the <entry> element of the MIME body indicates a user homed in the IWF, the processes used by IWF performing the controlling role to handle the incoming SIP MESSAGE request are out of scope;
+- 6) if the <request-type> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the SIP MESSAGE request is set to a value of "group-sds":
+  - a) shall retrieve the group document associated with the group identity in the SIP MESSAGE request by following the procedures in clause 6.3.3, and shall continue with the remaining steps if the procedures in clause 6.3.3 were successful;
+  - b) if the <on-network-disabled> element is present in the group document, shall send a SIP 403 (Forbidden) response with the warning text set to "115 group is disabled" in a Warning header field as specified in clause 4.7 and shall not continue with the rest of the steps;
+  - c) if the <entry> element of the <list> element of the <list-service> element in the group document does not contain an <mcdata-mcdata-id> element with a "uri" attribute matching the MCData ID of the originating user contained in the <mcdata-calling-user-identity> element of the application/vnd.3gpp.mcdata-info+xml MIME body in the SIP MESSAGE request, shall send a SIP 403 (Forbidden) response with the warning text set to "116 user is not part of the MCData group" in a Warning header field as specified in clause 4.7 and shall not continue with the rest of the steps;
+  - d) if the <list-service> element contains a <mcdata-allow-short-data-service> element in the group document set to a value of "false", shall send a SIP 403 (Forbidden) response with the warning text set to "206 short data service not allowed for this group" in a Warning header field as specified in clause 4.7 and shall not continue with the rest of the steps;
+  - e) if the <supported-services> element is not present in the group document or is present and contains a <service> element containing an "enabler" attribute which is not set to the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds", shall send a SIP 488 (Not Acceptable) response with the warning text set to "207 SDS services not supported for this group" in a Warning header field as specified in clause 4.7 and shall not continue with the rest of the steps;
+  - f) if the group SDS procedures in clause 11.1 indicate that the user identified by the MCData ID:
+    - i) is not allowed to send group MCData communications on this group identity as determined by step 2) of clause 11.1, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response, with warning text set to "201 user not authorised to transmit data on this group identity" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps in this clause;
+    - ii) is not allowed to send group MCData communications on this group identity due to exceeding the maximum amount of data that can be sent in a single request as determined by step 8) of clause 11.1, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "208 user not authorised for MCData communications on this group identity due
+
+to exceeding the maximum amount of data that can be sent in a single request" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps in this clause; and
+
+- iii) is not allowed to send SDS communications on this group identity due to message size as determined by step 5) of clause 11.1, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response to the SIP MESSAGE request, with warning text set to "217 user not authorised for SDS communications on this group identity due to message size" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps in this clause;
+  - g) the originating user identified by the MCData ID is not affiliated to the group identity contained in the SIP MESSAGE request, as specified in clause 6.3.5, shall return a SIP 403 (Forbidden) response with the warning text set to "120 user is not affiliated to this group" in a Warning header field as specified in clause 4.7, and skip the rest of the steps below;
+  - h) shall determine targeted group members for MCData communications by following the procedures in clause 6.3.3;
+  - i) if the procedures in clause 6.3.3 result in no affiliated members found in the selected MCData group, shall return a SIP 403 (Forbidden) response with the warning text set to "198 no users are affiliated to this group" in a Warning header field as specified in clause 4.7, and skip the rest of the steps below; and
+  - j) shall send SIP MESSAGE requests to the targeted MCData group members identified in step h) above by following the procedure in clause 9.2.2.4.1;
+- 7) shall generate a SIP 202 (Accepted) response in response to the "SIP MESSAGE request for standalone SDS for controlling MCData function"; and
+- 8) shall send the SIP 202 (Accepted) response towards the originating participating MCData function according to 3GPP TS 24.229 [4].
+
+### 9.2.3 Standalone SDS using media plane
+
+The IWF does not support standalone SDS using the media plane in the present document.
+
+### 9.2.4 SDS session
+
+The IWF does not support an SDS session in the present document.
+
+## 9.3 Off-network SDS
+
+Off-network SDS is not applicable to interworking.
+
+# --- 10 File Distribution (FD)
+
+File distribution is not supported by the IWF in the present document.
+
+# --- 11 Transmission and reception control
+
+## 11.1 General
+
+How the IWF determines authorisation of a user homed in the IWF to initiate MCData communications is out of scope.
+
+## 11.2 Auto-receive for File Distribution
+
+File distribution is not supported by the IWF in the present document.
+
+## 11.3 Accessing list of deferred data group communications
+
+Accessing list of deferred data group communication is associated with file distribution which is not supported by the IWF in the present document.
+
+# --- 12 Dispositions and Notifications
+
+## 12.1 General
+
+The procedures in clause 12 describe:
+
+- the on-network procedures for generating out-of-band dispositions for on-network SDS.
+
+The IWF acting on behalf of a participant homed in the IWF can send a disposition notification as a direct result of receiving an MCData message (e.g. delivery notification) or can send a disposition notification at a later time (e.g. read notification). In certain circumstances the delivery and read notification can be delivered in one notification message.
+
+## 12.2 Disposition notifications
+
+### 12.2.1 IWF performing the MCData participating role
+
+#### 12.2.1.1 Participating IWF procedures
+
+If the IWF performing the MCData participating role decides to send a disposition notification
+
+the IWF shall follow the procedures of clause 12.2.1.2.
+
+Upon receipt of a SIP 202 (Accepted) response in response to the SIP MESSAGE request, the IWF:
+
+- 1) can perform internal actions to process the response.
+
+Upon receipt of a SIP 200 (OK) response in response to the SIP MESSAGE request, the IWF:
+
+- 1) can perform internal actions to process the response.
+
+Upon receipt of a SIP 4xx, 5xx or 6xx response to the SIP MESSAGE request, the IWF:
+
+- 1) can perform internal actions to process the response.
+
+#### 12.2.1.2 Sending a disposition notification message
+
+The IWF performing the participating role may follow the procedures in this clause to:
+
+- indicate to an MCData client that an SDS message was delivered, read or delivered and read when the originating client requested a delivery, read or delivery and read report;
+- indicate to the participating MCData function serving the MCData user that an SDS message was undelivered; or
+- indicate to the participating MCData function serving the MCData user that disposition notification has been prevented for an SDS message intended for users homed in the LMR system.
+
+Before sending a disposition notification the IWF performing the participating role needs to determine:
+
+- the group identity related to an SDS message request received as part of a group communication. The IWF performing the participating role determines the group identity from the contents of the <mcdatcalling-group-id> element contained in the application/vnd.3gpp.mcdat-info+xml MIME body of the incoming SDS message request; and
+
+- the MCData user targeted for the disposition notification. The IWF performing the participating role determines the targetted MCData user from the contents of the <mcdatcalling-user-id> element contained in the application/vnd.3gpp.mcdat-info+xml MIME body of the incoming SDS message request.
+
+The IWF performing the participating role generates a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33] with the clarifications given below.
+
+The IWF performing the participating role:
+
+- 1) shall build the SIP MESSAGE request as specified in clause 6.2.4.1;
+- 2) shall follow the rules specified in clause 6.4 for the handling of MIME bodies in a SIP message when processing the remaining steps in this clause;
+- 3) shall insert in the SIP MESSAGE request an application/resource-lists+xml MIME body containing the MCData ID of the targeted MCData user, according to rules and procedures of IETF RFC 5366 [20];
+- 4) if sending a disposition notification in response to an MCData group data request, shall include an <mcdatcalling-group-id> element set to the MCData group identity in the application/vnd.3gpp.mcdat-info+xml MIME body;
+- 5) if sending an SDS notification, shall generate an SDS NOTIFICATION message and include it in the SIP MESSAGE request as specified in clause 6.2.3.1; and
+- 6) shall send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
+
+#### 12.2.1.3 Participating IWF receives disposition notification from a controlling MCData function
+
+Upon receipt of a:
+
+- "SIP MESSAGE request for SDS disposition notification for terminating MCData client ";
+
+The IWF:
+
+- 1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The IWF may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [4] and skip the rest of the steps;
+- 2) shall use the MCData ID present in the <mcdat-request-uri> element of the application/vnd.3gpp.mcdat-info+xml MIME body of the incoming SIP MESSAGE request to identify the user homed in the IWF;
+- 3) if the identity of the user homed in the IWF does not exist, then the participating IWF shall reject the SIP MESSAGE request with a SIP 404 (Not Found) response. Otherwise, continue with the rest of the steps; and
+- 4) can perform internal actions to process the message.
+
+If the IWF determines that a SIP 2xx response shall be sent on behalf of a user homed in the IWF in response to the SIP MESSAGE requests, the IWF shall send a SIP 2xx response to the controlling MCData function.
+
+If the IWF determines that a SIP 4xx, 5xx or 6xx response shall be sent on behalf of a user homed in the IWF in response to the SIP MESSAGE request, the IWF shall send the response to the controlling MCData function.
+
+### 12.2.2 IWF performing the MCData controlling role
+
+When triggered by:
+
+- receipt of a "SIP MESSAGE request for SDS disposition notification for MCData server"; or
+- the IWF determining that it shall send an SDS disposition notification
+
+the IWF performing the MCData controlling role:
+
+- 1) if the IWF has received the SIP MESSAGE;
+
+- a) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) response. The IWF may include a Retry-After header field to the SIP 500 (Server Internal Error) response as specified in IETF RFC 3261 [24]. Otherwise, continue with the rest of the steps;
+  - b) shall reject the SIP request with a SIP 403 (Forbidden) response and not process the remaining steps if an Accept-Contact header field does not include the g.3gpp.icsi-ref media feature tag containing the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds";
+  - c) if the incoming SIP MESSAGE request does not contain an application/resource-lists MIME body or contains an application/resource-lists MIME body with more than one <entry> element, shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "145 unable to determine called party" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps;
+  - d) shall attempt to correlate the disposition notification to the original SDS request using the values contained in the Conversation ID and Message ID of the SDS NOTIFICATION message contained in the application/vnd.3gpp.mcdata-signalling MIME body of the SIP MESSAGE; and
+  - e) if unable to correlate the disposition notification as determined by step d), shall reject the SIP MESSAGE request with a SIP 403 (Forbidden) response including warning text set to "216 unable to correlate the disposition notification" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps;
+- 2) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
+  - 3) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6] in the outgoing SIP MESSAGE request;
+  - 4) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" along with parameters "require" and "explicit" according to IETF RFC 3841 [6] in the outgoing SIP MESSAGE request;
+  - 5) shall set the Request-URI to the public service identity of the terminating participating MCData function associated with the MCData user to be invited ;
+
+NOTE 1: How the IWF finds the public service identity of the terminating MCData participating function is out of the scope of the present document.
+
+- 6) shall include a P-Asserted-Service header field with the value "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds";
+- 7) shall copy the MCData ID of the MCData user listed in the MIME resources body of the incoming SIP MESSAGE request, or the MCData ID of the participant homed in the IWF, into the <mcdata-request-uri> element in the application/vnd.3gpp.mcdata-info+xml MIME body of the outgoing SIP MESSAGE request;
+- 8) if an incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body with an <mcdata-calling-group-id> element:
+  - a) shall retrieve the group document for the MCData group id contained in the <mcdata-calling-group-id> element from the group management server, if not already cached, and identify the group members;
+
+NOTE 2: How the IWF obtains the group document is out scope of the present document.
+
+- b) shall verify that the MCData ID contained in the <mcdata-calling-user-identity> element matches to a group member. If there is no match, the IWF shall reject the SIP request with a SIP 403 (Forbidden) response including warning text set to "116 user is not part of the MCData group" in a Warning header field as specified in clause 4.7, and shall not continue with the rest of the steps;
+- c) if MCData disposition notifications need to be aggregated and an aggregated disposition notification has not yet been sent:
+  - i) if timer TDC1 (disposition aggregation timer) is not running, shall start timer TDC1 (disposition aggregation timer) with the timer value as specified in 3GPP TS 24.282 [82] clause F.2.2;
+
+- ii) shall copy the application/vnd.3gpp.mcdata-signalling MIME body in the received SIP MESSAGE request to the outgoing SIP MESSAGE request;
+
+NOTE 3: If the aggregated MCData disposition notifications do not fit into one SIP MESSAGE request, then the IWF needs to generate a new SIP MESSAGE request for the remaining disposition notifications.
+
+- iii) on expiry of timer TDC1 (disposition aggregation timer) shall continue with step 9; and
+  - iv) if all MCData disposition notifications have been received from all group members shall continue with step 9; and
+- d) if MCData disposition notifications do not need to be aggregated, shall copy the application/vnd.3gpp.mcdata-signalling MIME body in the received SIP MESSAGE request to the outgoing SIP MESSAGE request and shall continue with step 9;
+- 9) if an incoming SIP MESSAGE request contains an application/vnd.3gpp.mcdata-info+xml MIME body without an <mcdata-calling-group-id> element shall copy the application/vnd.3gpp.mcdata-signalling MIME body in the received SIP MESSAGE request to the outgoing SIP MESSAGE request;
+- 10) when notifying other users:
+    - a) shall send the SIP MESSAGE request to those users homed in the MCData system according to rules and procedures of 3GPP TS 24.229 [4]; and
+  - 11) when acknowledging the triggering event:
+    - a) shall generate a SIP 202 (Accepted) response in response to any
+      - "SIP MESSAGE request for SDS disposition notification for MCData server".
+
+## 12.3 On-network disposition notifications
+
+# --- 13 Communication Release
+
+The IWF shall handle communication release with the MCData system by behaving as a peer MCData server towards the MCData system as specified in 3GPP TS 24.282 [82] clauses 13.2.2.2.3, 13.2.2.2.4, 13.2.3 and 13.2.4.
+
+Communication release in the LMR system is out of scope of 3GPP.
+
+# --- 14 Enhanced Status (ES)
+
+## 14.1 General
+
+## 14.2 On-network ES
+
+### 14.2.1 Void
+
+### 14.2.2 IWF performing the participating MCData role procedures
+
+#### 14.2.2.1 Originating participating MCData function procedures
+
+If the IWF performing the participating MCData role determines that an Enhanced Status message needs to be sent on behalf of a participant homed in the IWF then it:
+
+- 1) shall use the "id" attribute of the selected operation value from <mcdata-enhanced-status-operational-values> element under <list-service> element as defined in 3GPP TS 24.481 [31], to generate a group standalone SDS message using the procedures described in clause 9.2.2.3.1.
+
+#### 14.2.2.2 Terminating participating MCData function procedures
+
+Upon receipt of a "SIP MESSAGE request for standalone SDS for terminating participating MCData function", the IWF performing the participating MCData role should follow the procedure described in clause 9.2.2.3.2.
+
+### 14.2.3 IWF performing the controlling MCData role procedures
+
+#### 14.2.3.1 Originating controlling MCData function procedures
+
+If the IWF performing the controlling MCData role determines that an Enhanced Status message needs to be sent on behalf of a participant homed in the IWF then it follows the procedure described in clause 9.2.2.4.1.
+
+#### 14.2.3.2 Terminating controlling MCData function procedures
+
+Upon receipt of a "SIP MESSAGE request for standalone SDS for controlling MCData function", the IWF performing the controlling MCData role should follow the procedure described in clause 9.2.2.4.2.
+
+# --- 15 Message Formats
+
+## 15.1 IWF message functional definitions and contents
+
+### 15.1.1 General
+
+The following clauses describe the MCData message functional definitions and contents. Each message consists of a series of information elements. The standard format of an MCData message and the encoding rules for each type of
+
+information element follow that defined for the MCPTT Off-Network Protocol (MONP) as documented in annex I of 3GPP TS 24.379 [81].
+
+### 15.1.2 SDS SIGNALLING PAYLOAD message
+
+#### 15.1.2.1 Message definition
+
+This message is sent by the MCData client towards a participant homed in the IWF via the network and from the IWF towards MCData clients when sending an SDS data payload. This message provides the signalling content related to the SDS data payload. For the contents of the message see Table 15.1.2.1-1.
+
+Message type: SDS SIGNALLING PAYLOAD
+
+Direction: MCData server to IWF and IWF to MCData server
+
+**Table 15.1.2.1-1: SDS SIGNALLING PAYLOAD message content**
+
+| IEI | Information Element                     | Type/Reference                                                 | Presence | Format | Length |
+|-----|-----------------------------------------|----------------------------------------------------------------|----------|--------|--------|
+|     | SDS signalling payload message identity | Message type 15.2.2                                            | M        | V      | 1      |
+|     | Date and time                           | Date and time 3GPP TS 24.282 [82] clause 15.2.8                | M        | V      | 5      |
+|     | Conversation ID                         | Conversation ID 3GPP TS 24.282 [82] clause 15.2.9              | M        | V      | 16     |
+|     | Message ID                              | Message ID 15.2.10                                             | M        | V      | 16     |
+| 21  | InReplyTo message ID                    | InReplyTo message ID 3GPP TS 24.282 [82] clause 15.2.11        | O        | TV     | 17     |
+| 22  | Application ID                          | Application ID 3GPP TS 24.282 [82] clause 15.2.7               | O        | TV     | 2      |
+| 8-  | SDS disposition request type            | SDS disposition request type 3GPP TS 24.282 [82] clause 15.2.3 | O        | TV     | 1      |
+| 7D  | Extended application ID                 | Extended application ID 3GPP TS 24.282 [82] clause 15.2.24     | O        | TLV-E  | 3-x    |
+
+### 15.1.3 FD SIGNALLING PAYLOAD message
+
+The IWF does not support the FD SIGNALLING PAYLOAD message.
+
+### 15.1.4 DATA PAYLOAD message
+
+#### 15.1.4.1 Message definition
+
+This message is sent by the MCData client towards a participant homed in the IWF via the network and from the IWF towards MCData clients when sending an SDS data payload. This message provides the data to be delivered to the user or application. For the contents of the message see Table 15.1.4.1-1.
+
+Message type: DATA PAYLOAD
+
+Direction: MCData server to IWF and IWF to MCData server
+
+**Table 15.1.4.1-1: DATA PAYLOAD message content**
+
+| IEI | Information Element             | Type/Reference                                           | Presence | Format | Length |
+|-----|---------------------------------|----------------------------------------------------------|----------|--------|--------|
+|     | Data payload message identity   | Message type<br>15.2.2                                   | M        | V      | 1      |
+|     | Number of payloads              | Number of payloads<br>3GPP TS 24.282 [82] clause 15.2.12 | M        | V      | 1      |
+| 7A  | Security parameters and Payload | MCData Protected Payload message<br>3GPP TS 33.180 [78]  | O        | TLV-E  | 32-x   |
+| 78  | Payload                         | Payload<br>15.2.13                                       | O        | TLV-E  | 3-x    |
+
+NOTE 1: The Number of payloads IE dictates the number of Payload IEs that are included in the message by the sender. Multiple Payload IEs can be part of Security parameters and Payload IE if end-to-end security is required.
+
+NOTE 2: If end-to-end security is required for a one-to-one communication, Security parameters and Payload IE is included. Otherwise, if end-to-end security is not required for a one-to-one communication, Payload IE is included. For group communication, Payload IE is included.
+
+NOTE 3: Formatting of payloads as part of the Security parameters and Payload IE is specified in clause 15.2.13.
+
+### 15.1.5 SDS NOTIFICATION message
+
+#### 15.1.5.1 Message definition
+
+This message is sent by the MCData client towards a participant homed in the IWF via the network and from the IWF towards MCData clients to share SDS disposition information. For the contents of the message see Table 15.1.5.1-1.
+
+Message type: SDS NOTIFICATION
+
+Direction: MCData server to IWF and IWF to MCData server
+
+**Table 15.1.5.1-1: SDS NOTIFICATION message content**
+
+| IEI | Information Element               | Type/Reference                                                         | Presence | Format | Length |
+|-----|-----------------------------------|------------------------------------------------------------------------|----------|--------|--------|
+|     | SDS notification message identity | Message type<br>15.2.2                                                 | M        | V      | 1      |
+|     | SDS disposition notification type | SDS disposition notification type<br>3GPP TS 24.282 [82] clause 15.2.5 | M        | V      | 1      |
+|     | Date and time                     | Date and time<br>3GPP TS 24.282 [82] clause 15.2.8                     | M        | V      | 5      |
+|     | Conversation ID                   | Conversation ID<br>3GPP TS 24.282 [82] clause 15.2.9                   | M        | V      | 16     |
+|     | Message ID                        | Message ID<br>15.2.10                                                  | M        | V      | 16     |
+| 22  | Application ID                    | Application ID<br>3GPP TS 24.282 [82] clause 15.2.7                    | O        | TV     | 2      |
+| 7D  | Extended application ID           | Extended application ID<br>3GPP TS 24.282 [82] clause 15.2.24          | O        | TLV-E  | 3-x    |
+
+### 15.1.6 FD NOTIFICATION message
+
+The IWF does not support the FD NOTIFICATION message.
+
+### 15.1.7 SDS OFF-NETWORK MESSAGE
+
+The IWF does not support the SDS OFF-NETWORK MESSAGE.
+
+### 15.1.8 SDS OFF-NETWORK NOTIFICATION message
+
+The IWF does not support the SDS OFF-NETWORK NOTIFICATION message.
+
+### 15.1.9 FD NETWORK NOTIFICATION message
+
+The IWF does not support the FD NETWORK NOTIFICATION message.
+
+### 15.1.10 COMMUNICATION RELEASE message
+
+#### 15.1.10.1 Message definition
+
+In this clause the term "MCData server" can apply to an MCData server or an IWF performing the role of an MCData server.
+
+This message is sent by the MCData server to an MCData client or a participant homed in the IWF to indicate about an intention to release the MCData communication. This message is also sent by the MCData client or the IWF to the MCData server to request extension for the MCData communication. The MCData server responds back to the request using this message. For the contents of the message see Table 15.1.10.1-1.
+
+Message type: COMMUNICATION RELEASE
+
+Direction: MCData server to the IWF and IWF to MCData server
+
+**Table 15.1.10.1-1: COMMUNICATION RELEASE message content**
+
+| IEI | Information Element           | Type/Reference                                                      | Presence | Format | Length |
+|-----|-------------------------------|---------------------------------------------------------------------|----------|--------|--------|
+|     | Comm Release message identity | Message type<br>15.2.2                                              | M        | V      | 1      |
+|     | Comm Release Information type | Comm Release Information type<br>3GPP TS 24.282 [82] clause 15.2.20 | M        | V      | 1      |
+| B-  | Data query type               | Data query type<br>3GPP TS 24.282 [82] clause 15.2.19               | O        | TV     | 1      |
+| C-  | Extension response type       | Extension response type<br>3GPP TS 24.282 [82] clause 15.2.21       | O        | TV     | 1      |
+
+### 15.1.11 DEFERRED DATA REQUEST message
+
+The IWF does not support the DEFERRED DATA REQUEST message.
+
+### 15.1.12 DEFERRED DATA RESPONSE message
+
+The IWF does not support the DEFERRED DATA RESPONSE message.
+
+### 15.1.13 FD HTTP TERMINATION
+
+The IWF does not support the FD HTTP TERMINATION message.
+
+## 15.2 General message format and information elements coding
+
+### 15.2.1 General
+
+The message format and bit ordering used within the present document are as defined in clause 15.2.1 of 3GPP TS 24.282 [82].
+
+### 15.2.2 Message type
+
+The purpose of the Message type information element is to identify the type of the message.
+
+The IWF shall support the following Message types as defined in clause 15.2.2 of 3GPP TS 24.282 [82]:
+
+- SDS SIGNALING PAYLOAD;
+- DATA PAYLOAD;
+- SDS NOTIFICATION;
+- COMMUNICATION RELEASE.
+
+### 15.2.3 Void
+
+### 15.2.4 Void
+
+### 15.2.5 Void
+
+### 15.2.6 Void
+
+### 15.2.7 Void
+
+### 15.2.8 Void
+
+### 15.2.9 Conversation ID
+
+The Conversation ID information element uniquely identifies the conversation.
+
+The Conversation ID information element is coded as shown in Figure 15.2.9-1 and Table 15.2.9-1.
+
+The Conversation ID information element is a type 3 information element with a length of 16 octets.
+
+![](1a74cf06fd2a1f8dcf7932224b617c57_img.jpg)
+
+|                       |   |   |   |   |   |   |   |                            |
+|-----------------------|---|---|---|---|---|---|---|----------------------------|
+| 8                     | 7 | 6 | 5 | 4 | 3 | 2 | 1 |                            |
+| Conversation ID value |   |   |   |   |   |   |   | octet 1<br>...<br>octet 16 |
+
+**Figure 15.2.9-1: Conversation ID value**
+
+**Table 15.2.9-1: Conversation ID value**
+
+|                                                                                                                                                                                                                                                                            |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Conversation identifier value (octet 1 to 16)                                                                                                                                                                                                                              |
+| The Conversation ID contains a number uniquely identifying the conversation. The value is a universally unique identifier as specified in IETF RFC 4122 [67] with the exception of the following designated value shown in Table 15.2.9-2, denoted "UNKNOWN CONVERSATION". |
+
+**Table 15.2.9-2: Conversation ID value "UNKNOWN CONVERSATION"**
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |          |
+|---|---|---|---|---|---|---|---|----------|
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 1  |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ...      |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 16 |
+
+### 15.2.10 Message ID
+
+The Message ID information element uniquely identifies a message within a conversation.
+
+The Message ID information element is coded as shown in Figure 15.2.10-1 and Table 15.2.10-1.
+
+The Message ID information element is a type 3 information element with a length of 16 octets.
+
+![Figure 15.2.10-1: Message ID value diagram showing 16 octets, each with 8 bits (8 to 1).](adc59ed6840bcb2d392ea323abfccedc_img.jpg)
+
+The diagram shows a rectangular box representing the Message ID value. Above the box, bits are numbered 8, 7, 6, 5, 4, 3, 2, 1 from left to right. Inside the box, the text "Message ID value" is centered. To the right of the box, the text "octet 1" is at the top, followed by "..." and "octet 16" at the bottom.
+
+Figure 15.2.10-1: Message ID value diagram showing 16 octets, each with 8 bits (8 to 1).
+
+**Figure 15.2.10-1: Message ID value**
+
+**Table 15.2.10-1: Message ID value**
+
+|                                                                                                                                                                                                                                                                                                                                   |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Message ID value (octet 1 to 16)                                                                                                                                                                                                                                                                                                  |
+| The Message ID contains a number uniquely identifying a message. The value is a universally unique identifier as specified in IETF RFC 4122 [67] with the exception of the designated value "UNKNOWN ORIGINATING MESSAGE ID" and "LMR MESSAGE ID" shown in Tables 15.2.10-2 and 15.2.10-3, where 'x' represents a variable value. |
+
+**Table 15.2.10-2: Message ID value "UNKNOWN ORIGINATING MESSAGE ID"**
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |          |
+|---|---|---|---|---|---|---|---|----------|
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 1  |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | ...      |
+| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 16 |
+
+**Table 15.2.10-3: Message ID value "LMR MESSAGE ID"**
+
+| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |          |
+|---|---|---|---|---|---|---|---|----------|
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | octet 1  |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ...      |
+| 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | octet 15 |
+| x | x | x | x | x | x | x | x | octet 16 |
+
+### 15.2.11 Void
+
+### 15.2.12 Void
+
+### 15.2.13 Payload
+
+The Payload information element contains the payload intended for the recipient user or application;
+
+The Payload information element is coded as shown in Figure 15.2.13-1, Table 15.2.13-1, Table 15.2.13-2, Table 15.2.13-3 and Table 15.2.13-4.
+
+The Payload information element is a type 6 information element.
+
+![](42e18c25bfd455a5a57f207bacfcb970_img.jpg)
+
+| 8                          | 7 | 6 | 5 | 4 | 3 | 2 | 1 |         |
+|----------------------------|---|---|---|---|---|---|---|---------|
+| Payload IEI                |   |   |   |   |   |   |   | octet 1 |
+| Length of Payload contents |   |   |   |   |   |   |   | octet 2 |
+|                            |   |   |   |   |   |   |   | octet 3 |
+|                            |   |   |   |   |   |   |   | octet 4 |
+| Payload contents           |   |   |   |   |   |   |   | octet n |
+
+**Figure 15.2.13-1: Payload information element**
+
+**Table 15.2.13-1: Payload contents**
+
+![](f0eaca8e167a863864b4ad9adb7ef16f_img.jpg)
+
+| 8                    | 7 | 6 | 5 | 4 | 3 | 2 | 1 |         |
+|----------------------|---|---|---|---|---|---|---|---------|
+| Payload content type |   |   |   |   |   |   |   | octet 4 |
+|                      |   |   |   |   |   |   |   | octet 5 |
+| Payload data         |   |   |   |   |   |   |   | octet n |
+
+**Table 15.2.13-2: Payload content type**
+
+| Bits |   |   |   |   |   |   |   |                 |
+|------|---|---|---|---|---|---|---|-----------------|
+| 8    | 7 | 6 | 5 | 4 | 3 | 2 | 1 |                 |
+| 0    | 0 | 0 | 0 | 0 | 0 | 0 | 1 | TEXT            |
+| 0    | 0 | 0 | 0 | 0 | 0 | 1 | 0 | BINARY          |
+| 0    | 0 | 0 | 0 | 0 | 0 | 1 | 1 | HYPERLINKS      |
+| 0    | 0 | 0 | 0 | 0 | 1 | 0 | 0 | FILEURL         |
+| 0    | 0 | 0 | 0 | 0 | 1 | 0 | 1 | LOCATION        |
+| 0    | 0 | 0 | 0 | 0 | 1 | 1 | 0 | ENHANCED STATUS |
+| 0    | 0 | 0 | 0 | 0 | 1 | 1 | 1 | LMR MESSAGE     |
+
+All other values are reserved.  
+NOTE: The LMR MESSAGE format identifies the payload content as a native LMR format message for transport between LMR aware endpoints as per 3GPP TS 23.283 [80]
+
+**Table 15.2.13-3: Payload data**
+
+Payload data is included in octet 5 to octet n; Max value of 65535 octets.
+
+Payload data contains the payload destined for the user or application.
+
+A file URL is encoded as specified in IETF RFC 1738 [86].
+
+The length of location information payload content is 6 bytes. First 3 bytes contain the latitude information and next 3 bytes contain the longitude information.
+
+If the Payload content type is "LMR MESSAGE" then the first octet of the payload data is encoded as specified in Table 15.2.13-4.
+
+**Table 15.2.13-4: First octet of Payload data for LMR MESSAGE Payload content type**
+
+| Bits                           |   |   |   |   |   |   |   |  |       |
+|--------------------------------|---|---|---|---|---|---|---|--|-------|
+| 8                              | 7 | 6 | 5 | 4 | 3 | 2 | 1 |  |       |
+| 0                              | 0 | 0 | 0 | 0 | 0 | 0 | 1 |  | P25   |
+| 0                              | 0 | 0 | 0 | 0 | 0 | 1 | 0 |  | TETRA |
+| All other values are reserved. |   |   |   |   |   |   |   |  |       |
+
+# 16 Media plane
+
+No media plane procedures are specified in the present document.
+
+# 17 Handling of Interworking Security Data messages
+
+## 17.1 IWF
+
+### 17.1.1 IWF originates Interworking Security Data message
+
+Upon deciding to send an Interworking Security Data message, the IWF:
+
+- 1) shall generate a SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC 3428 [33];
+- 2) shall include an Accept-Contact header field containing the g.3gpp.mcdata.sds media feature tag along with the "require" and "explicit" header field parameters according to IETF RFC 3841 [6];
+- 3) shall include an Accept-Contact header field with the media feature tag g.3gpp.icsi-ref with the value of "urn:urn-7:3gpp-service.ims.icsi.mcdata" along with parameters "require" and "explicit" according to IETF RFC 3841 [6];
+- 4) shall include an application/vnd.3gpp.mcdata-info+xml MIME body with the <mcdatainfo> element containing the <mcdata-Params> element with the <mcdata-request-uri> element set to the value of the MCData ID of the targeted MCData user; and
+- 5) shall include the ICSI value "urn:urn-7:3gpp-service.ims.icsi.mcdata" (coded as specified in 3GPP TS 24.229 [4]), in a P-Asserted-Service-Id header field according to IETF RFC 6050 [9];
+- 6) shall set the Request-URI to the address of the terminating participating function associated with the MC service ID of the targeted MC service user;
+- 7) shall include a P-Asserted-Identity header field set to the public service identity of the IWF;
+
+- 8) shall include an application/vnd.3gpp.interworking-data MIME body with the Interworking Security Data message payload as defined in clause 17.2.1;
+- 9) if a security context between the MCData client and the IWF needs to be established and the security context does not exist or if the existing security context has expired, procedures in clause 11.2.2 in 3GPP TS 33.180 [78] shall be followed; and
+- 10) send the SIP MESSAGE request according to rules and procedures of 3GPP TS 24.229 [4].
+
+### 17.1.2 IWF receives Interworking Security Data message
+
+Upon receiving a "SIP MESSAGE request for Interworking Security Data message for participating function", the actions performed by the IWF are out of scope of the present document. The received message, described in clause 17.2, contains an opaque payload, the contents of which are out of scope of the present document.
+
+## 17.2 Interworking Security Data message payload
+
+### 17.2.1 Message definition
+
+This clause specifies the payload to be used when sending an Interworking Security Data message between the IWF and MCData clients. The Interworking Security Data (InterSD) message is defined as a MONP message.
+
+Message type: InterSD-MESSAGE
+
+Direction: IWF to MCData client, MCData client to IWF
+
+**Table 17.2.1-1: Interworking Security Data message content**
+
+| IEI | Information Element                         | Type/Reference                                                                | Presence | Format | Length |
+|-----|---------------------------------------------|-------------------------------------------------------------------------------|----------|--------|--------|
+|     | SDS signalling payload message identity     | Message type<br>3GPP TS 24.282 [82]                                           | M        | V      | 1      |
+|     | External network type                       | 17.2.2                                                                        | M        | V      | 1      |
+| 7D  | URI of LMR key management functional entity | URI encoded as specified in IETF RFC 3986 [46]                                | O        | TLV-E  | 3-x    |
+| 78  | Payload                                     | 3GPP TS 24.282 [82], clause 15.2.13 with Payload content type set to 'BINARY' | O        | TLV-E  | 3-x    |
+
+### 17.2.2 External network type
+
+The purpose of the external network type information element is to identify the type of the network represented by the IWF.
+
+The value part of the external network type information element is coded as shown in Table 17.2.2-1.
+
+The external network type information element is a type 3 information element with a length of 1 octet.
+
+**Table 17.2.2-1: External network type**
+
+| Bits                           |   |   |   |   |   |   |   |       |
+|--------------------------------|---|---|---|---|---|---|---|-------|
+| 8                              | 7 | 6 | 5 | 4 | 3 | 2 | 1 |       |
+| 0                              | 0 | 0 | 0 | 0 | 0 | 0 | 1 | P25   |
+| 0                              | 0 | 0 | 0 | 0 | 0 | 1 | 0 | TETRA |
+| All other values are reserved. |   |   |   |   |   |   |   |       |
+
+# --- Annex A (informative): Signalling flows
+
+# --- Annex B (normative): Timers
+
+# --- Annex C (normative): Counters
+
+# --- Annex D (normative): XML schemas
+
+## D.1 XML schema for transporting MCData identities and general services information
+
+### D.1.1 General
+
+This clause defines XML schema and MIME type for transporting MCData identities and general services information. The XML schema elements and behaviour defined in this clause extend those in 3GPP TS 24.282 [82] or other 3GPP technical specifications as noted.
+
+### D.1.2 XML schema
+
+This schema is as described in 3GPP TS 24.282 [82] Annex D.1.2.
+
+### D.1.3 Semantic
+
+The semantic is as described in 3GPP TS 24.282 [82] Annex D.1.3 with the following modifications:
+
+If the <mcdatainfo> contains the <mcdata-Params> element then:
+
+- 1) the <request-type> can be included with:
+  - a) a value of "one-to-one-sds" to indicate that the MCData client wants to initiate a one-to-one SDS request;
+  - b) a value of "group-sds" to indicate the MCData client wants to initiate a group SDS request;
+  - c) a value of "notify" when the controlling MCData function needs to send a notification to the MCData client.
+- 2) the <anyExt> element of the <mcdata-Params> element can be included with the following element in addition to those specified in 3GPP TS 24.282 [82] Annex D.1.3:
+  - a) a <request-type> of type "xs:string": set to value of "Interworking Security Data message" when requesting an Interworking Security Data message.
+
+# Annex E (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                                                                                                                                                                                                                                                                                                                                                |  |             |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                |  | New version |
+| 2019-05        |         |           |      |     |     | Initial version                                                                                                                                                                                                                                                                                                                                                                                                                |  | 0.0.1       |
+| 2019-10        |         |           |      |     |     | Implementation of the following P-CR from CT1#120:<br>C1-196237, C1-196247, C1-196250, C1-196251,<br>C1-196252, C1-196253, C1-196633, C1-196636,<br>C1-196637, C1-196638, C1-196639, C1-196643,<br>C1-196644, C1-196645, C1-196647, C1-196648,<br>C1-196670, C1-196673, C1-196676, C1-196820,<br>C1-196821, C1-196822, C1-196824, C1-196825,<br>C1-196826, C1-196828, C1-196830, C1-196831,<br>C1-196868, C1-196869, C1-196871 |  | 0.1.0       |
+| 2019-11        |         |           |      |     |     | Implementation of the following P-CR from CT1#121:<br>C1-198514                                                                                                                                                                                                                                                                                                                                                                |  | 0.2.0       |
+| 2019-12        | CT-86   | CP-193158 |      |     |     | Presentation for information at TSG CT                                                                                                                                                                                                                                                                                                                                                                                         |  | 1.0.0       |
+| 2019-12        | CT#86   | CP-193291 |      |     |     | A title updated                                                                                                                                                                                                                                                                                                                                                                                                                |  | 1.0.1       |
+| 2020-03        |         |           |      |     |     | Implementation of the following pCRs from CT1#122e:<br>C1-200369, C1-200370, C1-200371, C1-200912, C1-200913, C1-200946, C1-200948                                                                                                                                                                                                                                                                                             |  | 1.1.0       |
+| 2020-03        | CT-87e  | CP-200175 |      |     |     | Presentation for approval at TSG CT                                                                                                                                                                                                                                                                                                                                                                                            |  | 2.0.0       |
+| 2020-03        | CT-87e  |           |      |     |     | Version 16.0.0 created after approval                                                                                                                                                                                                                                                                                                                                                                                          |  | 16.0.0      |
+| 2020-06        | CT-88e  | CP-201120 | 0001 | 1   | D   | Editorial corrections                                                                                                                                                                                                                                                                                                                                                                                                          |  | 16.1.0      |
+| 2020-09        | CT-89e  | CP-202161 | 0002 | 1   | F   | Introduction of text for Scope clause                                                                                                                                                                                                                                                                                                                                                                                          |  | 16.2.0      |
+| 2020-12        | CT-90e  | CP-203195 | 0006 | 1   | F   | Identifying LMR type in MCData SDS interworking                                                                                                                                                                                                                                                                                                                                                                                |  | 16.3.0      |
+| 2022-03        | CT-90e  | CP-220230 | 0016 | 1   | F   | Correction to Disposition Notification handling when LMR system temporarily disables Disposition Notification                                                                                                                                                                                                                                                                                                                  |  | 16.4.0      |
+| 2022-06        | CT-100  | CP-231254 | 0020 | 1   | F   | Warning codes & warning text to handle interworking application mismatch                                                                                                                                                                                                                                                                                                                                                       |  | 16.5.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37106/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37106/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..98d413dd9e8b31a31c1d0a6688853d87247c3096
--- /dev/null
+++ b/marked/Rel-16/37_series/37106/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f50a9d65f3fe7199439ffa4d6d1f8de6baed744a8cc106953439d53ad08c3e5
+size 9698
diff --git a/marked/Rel-16/37_series/37106/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37106/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b298eb631aa8ce631dfe61f8ba0d2a6c5b946dd0
--- /dev/null
+++ b/marked/Rel-16/37_series/37106/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:557f166794cbc85288db7a837b0042a75220e94b38bd28b2b90c8cace0ada0c0
+size 5781
diff --git a/marked/Rel-16/37_series/37106/raw.md b/marked/Rel-16/37_series/37106/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..9bf2f3c5ba4177baeb6985ee1f075c19ee96db74
--- /dev/null
+++ b/marked/Rel-16/37_series/37106/raw.md
@@ -0,0 +1,193 @@
+
+
+# 3GPP TS 37.106 V16.1.0 (2020-09) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) requirements for shared spectrum channel access (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon below it. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+---
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                          |          |
+|--------------------------------------------------------------------------|----------|
+| Foreword .....                                                           | 4        |
+| 1 Scope.....                                                             | 5        |
+| 2 References.....                                                        | 5        |
+| 3 Definitions, symbols and abbreviations .....                           | 5        |
+| 3.1 Definitions.....                                                     | 5        |
+| 3.2 Symbols.....                                                         | 5        |
+| 3.3 Abbreviations .....                                                  | 6        |
+| 4 General.....                                                           | 6        |
+| 4.1 Relationship between minimum requirements and test requirements..... | 6        |
+| 4.2 Applicability of minimum requirements .....                          | 6        |
+| 5 Channel access procedures.....                                         | 6        |
+| 5.1 Uplink channel access procedure .....                                | 6        |
+| 5.1.1 Channel access parameters .....                                    | 6        |
+| 5.1.2 Minimum requirement.....                                           | 7        |
+| <b>Annex A (informative): Change history.....</b>                        | <b>7</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document establishes the minimum UE RF characteristics for shared spectrum channel access.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [3] Void
+- [4] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception".
+- [5] 3GPP TS 36.521-1 : "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing".
+- [6] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access".
+- [7] 3GPP TS 38.521-1: "NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**Channel bandwidth:** The RF bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                       |                   |
+|-----------------------|-------------------|
+| BW <sub>Channel</sub> | Channel bandwidth |
+|-----------------------|-------------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                            |
+|--------|--------------------------------------------|
+| BS     | Base Station                               |
+| E-UTRA | Evolved Universal Terrestrial Radio Access |
+| NR     | New Radio                                  |
+| PUSCH  | Physical Uplink Shared Channel             |
+| UE     | User Equipment                             |
+
+# --- 4 General
+
+## 4.1 Relationship between minimum requirements and test requirements
+
+The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 36.521-1 [5] Annex F defines Test Tolerances for E-UTRA, and the test specification TS 38.521-1 [7] Annex F defines Test Tolerances for NR. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements.
+
+The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle.
+
+The Shared Risk principle is defined in ITU-R M.1545 [2].
+
+## 4.2 Applicability of minimum requirements
+
+- In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios
+- For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements.
+- The requirements in this specification for E-UTRA TDD operating bands apply for downlink and uplink operations using Frame Structure Type 3.
+
+# --- 5 Channel access procedures
+
+## 5.1 Uplink channel access procedure
+
+For uplink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PUSCH transmission as described in TS 37.213 [6], Clause 4.2.1 is specified.
+
+### 5.1.1 Channel access parameters
+
+Channel access related parameters for PUSCH are listed in Table 5.1.1-1.
+
+**Table 5.1.1-1: Channel access parameters for PUSCH**
+
+| Parameter                      | Unit         | Value |     |
+|--------------------------------|--------------|-------|-----|
+| LBT measurement bandwidth (BW) | MHz          | 20    | 10  |
+| Energy detection threshold     | dBm/BW       | -72   | -75 |
+| Detection timing               | microseconds | 25    |     |
+
+### 5.1.2 Minimum requirement
+
+The UE shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1.
+
+# --- Annex A (informative): Change history
+
+| Change history |         |            |      |     |     |                                                                    |             |
+|----------------|---------|------------|------|-----|-----|--------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc       | CR   | Rev | Cat | Subject/Comment                                                    | New version |
+| 2018-02        | RAN4#86 | R4-1801547 |      |     |     | TS skeleton                                                        | 0.0.1       |
+| 2018-06        | RAN#80  | RP-181030  |      |     |     | v1.0.0 submitted for plenary approval                              | 1.0.0       |
+| 2018-06        | RAN#80  |            |      |     |     | Approved by plenary – Rel-15 spec under change control             | 15.0.0      |
+| 2020-06        | RAN#88  | -          | -    | -   | -   | Update to Rel-16 version (MCC)                                     | 16.0.0      |
+| 2020-09        | RAN#89  | RP-201512  | 0003 |     | A   | CR to TS 37.106 with correction to referencies to TS 37.213 Rel-16 | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201915  | 0004 |     | B   | CR to TS 37.106 with introduction of NR-U feature                  | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37107/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37107/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c236f567aba973aabc1871554d7a0284069ee689
--- /dev/null
+++ b/marked/Rel-16/37_series/37107/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b54f750426473af71a7919811ddc7d6c26d11acc315bd476e4dc349d40a323d
+size 10070
diff --git a/marked/Rel-16/37_series/37107/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37107/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26fd53abef53f6006c18b37e7980ad7d9fc921af
--- /dev/null
+++ b/marked/Rel-16/37_series/37107/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c809a272a0875e9ab4896d0496e46dd775d4ff800da817a9e1c51203f5d3c05
+size 5792
diff --git a/marked/Rel-16/37_series/37107/raw.md b/marked/Rel-16/37_series/37107/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4e7c718cd5f24ca2354611597b63014c92fd91a
--- /dev/null
+++ b/marked/Rel-16/37_series/37107/raw.md
@@ -0,0 +1,310 @@
+
+
+# 3GPP TS 37.107 V16.3.0 (2021-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Base Station (BS) requirements and conformance tests for shared spectrum channel access (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                          |           |
+|--------------------------------------------------------------------------|-----------|
+| Foreword .....                                                           | 4         |
+| 1 Scope.....                                                             | 6         |
+| 2 References.....                                                        | 6         |
+| 3 Definitions, symbols and abbreviations .....                           | 6         |
+| 3.1 Definitions.....                                                     | 6         |
+| 3.2 Symbols.....                                                         | 6         |
+| 3.3 Abbreviations .....                                                  | 6         |
+| 4 General.....                                                           | 8         |
+| 4.1 Relationship between minimum requirements and test requirements..... | 8         |
+| 5 Channel access procedures (core part).....                             | 8         |
+| 5.1 Downlink channel access procedure .....                              | 8         |
+| 5.1.1 Channel access parameters .....                                    | 8         |
+| 5.1.2 Minimum requirement.....                                           | 8         |
+| 6 Channel access procedures (performance part) .....                     | 9         |
+| 6.1 Downlink channel access procedure .....                              | 9         |
+| 6.1.1 Definition and applicability .....                                 | 9         |
+| 6.1.2 Minimum requirement.....                                           | 9         |
+| 6.1.3 Test purpose.....                                                  | 9         |
+| 6.1.4 Method of test.....                                                | 9         |
+| 6.1.4.1 Initial conditions for band 46 and band 49 .....                 | 9         |
+| 6.1.4.1a Initial conditions for band n46 and band n96 .....              | 9         |
+| 6.1.4.2 Procedure .....                                                  | 9         |
+| 6.1.5 Test Requirements .....                                            | 10        |
+| <b>Annex A (informative): Change history.....</b>                        | <b>11</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the minimum Radio Frequency (RF) characteristics, minimum performance requirements, and the RF test methods and conformance requirements for E-UTRA with LAA Base Stations (BS) and for NR-U Base Stations (BS).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing".
+- [3] ITU-R Recommendation M.1545: "Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000".
+- [4] Void.
+- [5] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access".
+- [6] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                            |
+|--------|--------------------------------------------|
+| BS     | Base Station                               |
+| E-UTRA | Evolved Universal Terrestrial Radio Access |
+| NR     | New Radio                                  |
+
+|       |                                  |
+|-------|----------------------------------|
+| LBT   | Listen-Before-Talk               |
+| PDSCH | Physical Downlink Shared Channel |
+| RF    | Radio Frequency                  |
+
+# 4 General
+
+## 4.1 Relationship between minimum requirements and test requirements
+
+The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 36.141 [2] Annex G defines Test Tolerances for E-UTRA, and the test specification TS 38.141-1 [6] Annex C defines Test Tolerances for NR. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in this specification to create Test Requirements.
+
+The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by the shared risk principle.
+
+The Shared Risk principle is defined in ITU-R M.1545 [3].
+
+# 5 Channel access procedures (core part)
+
+## 5.1 Downlink channel access procedure
+
+For downlink operation in Band 46, Band 49, Band n46 and Band n96, a channel access procedure for PDSCH transmission as described in TS 37.213 [5], Clause 4.1.1 is specified.
+
+### 5.1.1 Channel access parameters
+
+Channel access related parameters for PDSCH are listed in Table 5.1.1-1.
+
+**Table 5.1.1-1: Channel access parameters for PDSCH**
+
+| Parameter                                             | Unit      | Value                        |
+|-------------------------------------------------------|-----------|------------------------------|
+| LBT measurement bandwidth                             | MHz       | 10, 20                       |
+| Energy detection threshold                            | dBm/20MHz | -72<br>or<br>X (Note)<br>-75 |
+|                                                       | dBm/10MHz |                              |
+| Maximum channel occupancy time                        | ms        | 8                            |
+| NOTE: The specific value X is declared by the vendor. |           |                              |
+
+### 5.1.2 Minimum requirement
+
+The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 5.1.1-1.
+
+# 6 Channel access procedures (performance part)
+
+## 6.1 Downlink channel access procedure
+
+### 6.1.1 Definition and applicability
+
+Channel access procedure for downlink operation in band 46, band 49, band n46 and band n96 for PDSCH transmission is described in TS 37.213 [5], Clause 4.
+
+### 6.1.2 Minimum requirement
+
+The minimum requirement is in clause 5.1.
+
+### 6.1.3 Test purpose
+
+The test purpose is to verify the accuracy of the energy detection threshold, maximum channel occupancy time (MCOT) and minimum idle time under normal conditions for all band 46 and band 49 transmitters in the BS.
+
+### 6.1.4 Method of test
+
+#### 6.1.4.1 Initial conditions for band 46 and band 49
+
+Test environment: normal; see Annex D.2 of TS 36.141 [2].
+
+RF channels to be tested for single carrier: B, M and T; see clause 4.7 of TS 36.141 [2].
+
+Connect the signal analyzer to the base station antenna connector as shown in Annex I of TS 36.141 [2].
+
+#### 6.1.4.1a Initial conditions for band n46 and band n96
+
+Test environment: Normal, see annex B.2 of TS 38.141-1 [6].
+
+RF channels to be tested: M; see clause 4.9.1 of TS 38.141-1 [6].
+
+Set the channel set-up of the connector under as shown in annex D.1 for BS type 1-C and annex D.3 for BS type 1-H in [6].
+
+#### 6.1.4.2 Procedure
+
+##### MCOT and minimum idle time
+
+- 1) Set the base station to transmit a signal according to E-TM 1.1 at manufacturer's declared rated output power with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) for band 46 and 49, or
+
+Set the base station to transmit a signal according to NR-FR1-TM1.1 at manufacturer's declared rated output power with corresponding channel bandwidth i.e. 10 MHz (only for band n46) or 20 MHz for band n46 or n96.
+
+- 2) Measure the transmitter ON period during the continuous transmission (after the first channel access).
+- 3) Measure the transmitter OFF period between two consecutive transmitter ON periods.
+- 4) Verify minimum idle time as follows:
+
+The transmitter OFF period between two consecutive transmitter ON periods shall not be less than 25  $\mu\text{s}$ .
+
+- 5) Verify maximum channel occupancy time (MCOT) as follows:
+
+- a) The duration of each transmitter ON period continuous transmission shall not exceed the maximum channel occupancy time (MCOT) requirement specified in clause 6.1.5.
+
+##### Energy detection accuracy
+
+- 6) Generate the interfering signal of AWGN with corresponding channel bandwidth (i.e. 10 MHz or 20 MHz) at the same centre frequency as the tested channel. The interfering signal shall be at a level as specified in table 6.1.5-1. The base station shall stop transmission on the current operating channel and will not resume normal transmissions as long as the interference signal is present.
+- 7) The step 6) is repeated multiple times considering the following sub-steps:
+  - Interferer ON: if the interfering signal is present, the interfering signal should be present for 10ms.
+  - Interferer OFF: if the interfering signal is removed, the interfering signal should be absent for 10ms.
+  - The total number of interferer ON duration is assumed to be N and the total number of interferer OFF duration is assumed to be M. The value N, M and the sequence of interferer ON/OFF pattern shall be generated randomly for the test.
+- 8) In the test, a counter is maintained with initial value set to 0 when the test starts.
+- 9) For every 10ms Interferer ON period, the counter is increased by 1 if there is either an ON/OFF transition or no transmission by the DUT. To pass the test, the counter shall not be less than  $N * 0.9$ .
+
+### 6.1.5 Test Requirements
+
+In normal conditions, the measurement result shall meet channel access related test requirements for PDSCH as listed in Table 6.1.5-1.
+
+**Table 6.1.5-1: Channel access test requirements for PDSCH**
+
+| Parameter                                             | Unit      | Value                             |
+|-------------------------------------------------------|-----------|-----------------------------------|
+| LBT measurement bandwidth                             | MHz       | 10, 20                            |
+| Maximum energy detection threshold                    | dBm/20MHz | -72 + 4dB<br>or<br>X + 4dB (Note) |
+|                                                       | dBm/10MHz | -75 + 4dB                         |
+| Maximum channel occupancy time                        | ms        | 8                                 |
+| NOTE: The specific value X is declared by the vendor. |           |                                   |
+
+The Base Station shall be able to assess whether the medium is busy or idle with at least 90% probability, using a channel access procedure with the parameters in Table 6.1.5-1.
+
+# Annex A (informative): Change history
+
+| Change history |         |            |      |     |     |                                                                                                                                  |             |
+|----------------|---------|------------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc       | CR   | Rev | Cat | Subject/Comment                                                                                                                  | New version |
+| 2018-03        | RAN4#86 | R4-1802453 |      |     |     | TS skeleton created from 3GPP TS template.                                                                                       | 0.0.1       |
+| 2018-05        | RAN4#87 | R4-1807758 |      |     |     | Updated TS draft for 37.107 with core part and corrections                                                                       | 0.1.0       |
+| 2018-06        | RAN#80  | RP-181132  |      |     |     | v1.0.0 submitted for plenary approval                                                                                            | 1.0.0       |
+| 2018-06        | RAN#80  |            |      |     |     | Approved by plenary – Rel-15 spec under change control                                                                           | 15.0.0      |
+| 2018-09        | RAN#81  | RP-181901  | 0001 |     | F   | Moving Section 9 from 36.141 to 37.107                                                                                           | 15.1.0      |
+| 2020-06        | RAN#88  | RP-200989  | 0002 | 1   | F   | CR to TS 37.107 with correction to interfering signal for conformance test for energy detection accuracy to align with TS 37.213 | 15.2.0      |
+| 2020-06        | SA#88   | -          | -    | -   | -   | Update to Rel-16 version (MCC)                                                                                                   | 16.0.0      |
+| 2020-09        | RAN#89  | RP-201512  | 0005 |     | A   | CR to 37.107 with correction of references to TS 37.213 Rel-16                                                                   | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201914  | 0007 |     | B   | CR to TS 37.107 with introduction of NR-U feature – core part                                                                    | 16.1.0      |
+| 2020-12        | RAN#90  | RP-202499  | 0009 |     | A   | CR to 37.107 with update of EDT level                                                                                            | 16.2.0      |
+| 2021-06        | RAN#92  | RP-211094  | 0010 |     | B   | CR to TS 37.107 with NR-U introduction for performance part                                                                      | 16.3.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37113/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/marked/Rel-16/37_series/37113/18442e4e239480f0c3c95b547aa8fde2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..31111cc80f3b23ffee9d84b6d6d03fffa04550a9
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/18442e4e239480f0c3c95b547aa8fde2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72438ed8f69ccf1aff6d3f5ad70e1c226e77be59db587071441bf91849fc7617
+size 11053
diff --git a/marked/Rel-16/37_series/37113/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-16/37_series/37113/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2775978ff97c7d227580627e35760b1c06a77516
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7c88b7745a3facea90078c5342a811dace7ea05b96892bc81b845c4b056d3ab
+size 22817
diff --git a/marked/Rel-16/37_series/37113/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37113/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6715f0444077a91e2c59cfb7d6e403465ac0f808
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7650448e24536177762aed0b0e9e34c40ad910d87e448d27e115f31d01c6cfdc
+size 7730
diff --git a/marked/Rel-16/37_series/37113/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37113/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c319fd7333a7ddf0646c03bff25266fbd7f96b36
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69c56c2736d5566c4ed500a4cb4952f38fd6298b7dacb1562e658530fa1ea111
+size 5899
diff --git a/marked/Rel-16/37_series/37113/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/37_series/37113/c78c2eefd86269d1740ab85a916f24f2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c5b1853e2294772c77a0f3f8ba1ebbadaaddd85
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/c78c2eefd86269d1740ab85a916f24f2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b5368abe2c053206c4a9c51858613a91e60729f05b66b0d3da66b02f46490b3
+size 29828
diff --git a/marked/Rel-16/37_series/37113/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-16/37_series/37113/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08e453a2b31012d9764100c99569ee248dbe8c54
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:50d3f8183fe99f428b1a4afd78c669eea6cb949314fe683cf21b5957a031e604
+size 22257
diff --git a/marked/Rel-16/37_series/37113/raw.md b/marked/Rel-16/37_series/37113/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d3b2d4e39ad7db483b0047630b9d833724ac2e9
--- /dev/null
+++ b/marked/Rel-16/37_series/37113/raw.md
@@ -0,0 +1,1422 @@
+
+
+# 3GPP TS 37.113 V16.4.0 (2023-06)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon at its base.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                |    |
+|--------------------------------------------------------------------------------|----|
+| Foreword .....                                                                 | 5  |
+| 1 Scope.....                                                                   | 7  |
+| 2 References.....                                                              | 7  |
+| 3 Definitions, symbols and abbreviations .....                                 | 9  |
+| 3.1 Definitions.....                                                           | 9  |
+| 3.2 Symbols.....                                                               | 12 |
+| 3.3 Abbreviations .....                                                        | 12 |
+| 4 Test conditions .....                                                        | 13 |
+| 4.1 General .....                                                              | 13 |
+| 4.2 Arrangements for establishing a communication link.....                    | 13 |
+| 4.2.1 Multiple enclosure BS solution .....                                     | 14 |
+| 4.3 Narrow band responses on receivers.....                                    | 14 |
+| 4.4 Exclusion bands.....                                                       | 14 |
+| 4.4.1 Transmitter exclusion band .....                                         | 14 |
+| 4.4.2 Receiver exclusion band.....                                             | 14 |
+| 4.5 BS test configurations .....                                               | 15 |
+| 5 Performance assessment .....                                                 | 19 |
+| 5.1 General .....                                                              | 19 |
+| 5.2 Assessment of performance in Downlink .....                                | 19 |
+| 5.3 Assessment of performance in Uplink .....                                  | 19 |
+| 5.4 Ancillary equipment.....                                                   | 20 |
+| 6 Performance criteria.....                                                    | 20 |
+| 6.1 Performance criteria for continuous phenomena for BS.....                  | 20 |
+| 6.1.1 E-UTRA performance criteria .....                                        | 20 |
+| 6.1.2 UTRA performance criteria.....                                           | 21 |
+| 6.1.3 GSM/EDGE performance criteria .....                                      | 21 |
+| 6.1.3.1 GSM/EDGE downlink .....                                                | 21 |
+| 6.1.3.2 GSM/EDGE uplink.....                                                   | 21 |
+| 6.1.4 NB-IoT performance criteria.....                                         | 22 |
+| 6.1.5 NR performance criteria .....                                            | 22 |
+| 6.2 Performance criteria for transient phenomena for BS.....                   | 22 |
+| 6.3 Performance criteria for continuous phenomena for Ancillary equipment..... | 23 |
+| 6.4 Performance criteria for transient phenomena for Ancillary equipment.....  | 23 |
+| 7 Applicability overview.....                                                  | 24 |
+| 7.1 Emission.....                                                              | 24 |
+| 7.2 Immunity .....                                                             | 24 |
+| 8 Emission.....                                                                | 25 |
+| 8.1 Test configurations.....                                                   | 25 |
+| 8.2 Radiated emission from Base Station and ancillary equipment.....           | 25 |
+| 8.2.1 Radiated emission for Base Stations .....                                | 25 |
+| 8.2.1.1 Definition .....                                                       | 25 |
+| 8.2.1.2 Test method.....                                                       | 25 |
+| 8.2.1.3 Limits .....                                                           | 26 |
+| 8.2.1.4 Interpretation of the measurement results.....                         | 26 |
+| 8.2.2 Radiated emission, ancillary equipment.....                              | 27 |
+| 8.2.2.1 Definition .....                                                       | 27 |
+| 8.2.2.2 Test method.....                                                       | 27 |
+| 8.2.2.3 Limits .....                                                           | 27 |
+| 8.3 Conducted emission DC power input/output port.....                         | 27 |
+| 8.3.1 Definition.....                                                          | 28 |
+| 8.3.2 Test method .....                                                        | 28 |
+| 8.3.3 Limits.....                                                              | 28 |
+
+|                                                              |                                                                                    |           |
+|--------------------------------------------------------------|------------------------------------------------------------------------------------|-----------|
+| 8.4                                                          | Conducted emissions, AC mains power input/output port.....                         | 28        |
+| 8.4.1                                                        | Definition.....                                                                    | 28        |
+| 8.4.2                                                        | Test method .....                                                                  | 28        |
+| 8.4.3                                                        | Limits.....                                                                        | 28        |
+| 8.5                                                          | Harmonic current emissions (AC mains input port) .....                             | 29        |
+| 8.6                                                          | Voltage fluctuations and flicker (AC mains input port).....                        | 29        |
+| 8.7                                                          | Telecommunication ports.....                                                       | 29        |
+| 8.7.1                                                        | Definition.....                                                                    | 29        |
+| 8.7.2                                                        | Test method .....                                                                  | 29        |
+| 8.7.3                                                        | Limits.....                                                                        | 29        |
+| 9                                                            | Immunity .....                                                                     | 30        |
+| 9.1                                                          | Test configurations.....                                                           | 30        |
+| 9.2                                                          | RF electromagnetic field (80 MHz - 6000 MHz).....                                  | 31        |
+| 9.2.1                                                        | Definition.....                                                                    | 31        |
+| 9.2.2                                                        | Test method and level.....                                                         | 31        |
+| 9.2.3                                                        | Performance criteria .....                                                         | 31        |
+| 9.3                                                          | Electrostatic discharge.....                                                       | 31        |
+| 9.3.1                                                        | Definition.....                                                                    | 31        |
+| 9.3.2                                                        | Test method and level.....                                                         | 31        |
+| 9.3.3                                                        | Performance criteria .....                                                         | 32        |
+| 9.4                                                          | Fast transients common mode.....                                                   | 32        |
+| 9.4.1                                                        | Definition.....                                                                    | 32        |
+| 9.4.2                                                        | Test method and level.....                                                         | 32        |
+| 9.4.3                                                        | Performance criteria .....                                                         | 32        |
+| 9.5                                                          | RF common mode (0,15 MHz - 80 MHz).....                                            | 32        |
+| 9.5.1                                                        | Definition.....                                                                    | 33        |
+| 9.5.2                                                        | Test method and level.....                                                         | 33        |
+| 9.5.3                                                        | Performance criteria .....                                                         | 33        |
+| 9.6                                                          | Voltage dips and interruptions .....                                               | 33        |
+| 9.6.1                                                        | Definition.....                                                                    | 33        |
+| 9.6.2                                                        | Test method and level.....                                                         | 34        |
+| 9.6.3                                                        | Performance criteria .....                                                         | 34        |
+| 9.7                                                          | Surges, common and differential mode.....                                          | 34        |
+| 9.7.1                                                        | Definition.....                                                                    | 34        |
+| 9.7.2                                                        | Test method and level.....                                                         | 34        |
+| 9.7.2.1                                                      | Test method for telecommunication ports directly connected to outdoor cables ..... | 35        |
+| 9.7.2.2                                                      | Test method for telecommunication ports connected to indoor cables.....            | 35        |
+| 9.7.2.3                                                      | Test method for AC power ports .....                                               | 35        |
+| 9.7.3                                                        | Performance criteria .....                                                         | 35        |
+| <b>Annex A (normative): BER assessment for GSM/EDGE.....</b> |                                                                                    | <b>36</b> |
+| A.1                                                          | Assessment of BER at the output of a transmitter .....                             | 36        |
+| A.1.1                                                        | Assessment of BER using static layer 1 functions.....                              | 36        |
+| A.1.2                                                        | Assessment of BER using RXQUAL.....                                                | 36        |
+| A.2                                                          | Assessment of BER at the output of a receiver.....                                 | 36        |
+| A.2.1                                                        | Assessment of BER using RXQUAL.....                                                | 36        |
+| A.2.2                                                        | Assessment of BER using reported BER.....                                          | 36        |
+| <b>Annex B (informative): Change history .....</b>           |                                                                                    | <b>37</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document covers the assessment of NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio (MSR) Base Stations and associated ancillary equipment in respect of Electromagnetic Compatibility (EMC).
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Base Stations and associated ancillary equipment in one of the following categories:
+
+- Multi-Standard Radio (MSR) Base Stations for NR, E-UTRA, UTRA and GSM/EDGE meeting the requirements of TS 37.104 [6], with conformance demonstrated by compliance to TS 37.141 [11].
+
+NOTE: For NR, scope of this specification is limited to *BS type 1-C*. For EMC requirements of the MSR BS for *BS type 1-H* and *BS type 1-O*, refer to TS 37.114 [39].
+
+- *BS type 1-C* for NR meeting the requirements of TS 38.104 [35], with conformance demonstrated by compliance to TS 38.141-1 [36]
+- Base Stations for E-UTRA meeting the requirements of TS 36.104 [4], with conformance demonstrated by compliance to TS 36.141 [9].
+- Base Stations for UTRA FDD meeting the requirements of TS 25.104 [2], with conformance demonstrated by compliance to TS 25.141 [7].
+- Base Stations for UTRA TDD meeting the requirements of TS 25.105 [3], with conformance demonstrated by compliance to TS 25.142 [8].
+- Base Stations for GSM/EDGE meeting the requirements of TS 45.005 [5], with conformance demonstrated by compliance to TS 51.021 [10].
+- Base Stations for NB-IoT meeting the requirements of TS 36.104 [4], with conformance demonstrated by compliance to TS 36.141 [9].
+
+In addition to MSR base stations, the present document covers other BS supporting more than one RAT.
+
+Technical requirements related to the antenna port of Base Stations are not included in the present document. These are found in the relevant product standards [2-11, 35, 36].
+
+The environment classification used in the present document refers to the residential, commercial, and light industrial environment classification used in IEC 61000-6-1 [12] and IEC 61000-6-3 [13].
+
+The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+
+- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)".
+- [4] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception ".
+- [5] 3GPP TS 45.005: "Radio transmission and reception".
+- [6] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception".
+- [7] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)".
+- [8] 3GPP TS 25.142: "Base Station (BS) conformance testing (TDD)".
+- [9] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing".
+- [10] 3GPP TS 51.021: "Base Station System (BSS) equipment specification; Radio aspects".
+- [11] 3GPP TS 37.141: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing".
+- [12] IEC 61000-6-1: 2005: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards – Immunity for residential, commercial and light-industrial environments".
+- [13] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards – Emission standard for residential, commercial and light-industrial environments".
+- [14] IEC 60050-161: "International Electrotechnical Vocabulary (IEV) - Part 161: Electromagnetic compatibility".
+- [15] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain".
+- [16] ITU-R Recommendation SM.1539-1 (2001): "Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329".
+- [17] Void
+- [18] Void
+- [19] IEC 61000-3-2 (2004): "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current  $\leq 16$  A)".
+- [20] IEC 61000-3-12 (2005): "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic current produced by equipment connected to public low-voltage system with input current  $>16$  A and  $\leq 75$  A".
+- [21] IEC 61000-3-3 (2002): "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 16$  A".
+- [22] IEC 61000-3-11 (2000): "Electromagnetic compatibility (EMC) - Part 3-11: Limits – Limitation of voltage fluctuations and flicker in low-voltage supply systems for equipment with rated current  $\leq 75$  A and subject to conditional connections".
+- [23] IEC 61000-4-3: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency electromagnetic field immunity test".
+- [24] IEC 61000-4-2: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test".
+- [25] IEC 61000-4-4: "Electromagnetic compatibility (EMC) - Part 4-4: Testing and measurement techniques - Electrical fast transient/burst immunity test".
+- [26] IEC 61000-4-6: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to contacted disturbances, induced by radio frequency fields".
+
+- [27] IEC 61000-4-11: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations. Immunity tests".
+- [28] IEC 61000-4-5: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test".
+- [29] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [30] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [31] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [32] 3GPP TS 45.008: "Radio subsystem link control".
+- [33] 3GPP TS 51.010-1: " Mobile Station (MS) conformance specification; Part 1: Conformance specification".
+- [34] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements".
+- [35] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
+- [36] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformance testing".
+- [37] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing; Part 2: Radiated conformance testing".
+- [38] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements".
+- [39] 3GPP TS 37.114: "Active Antenna System (AAS) Base Station (BS), Electromagnetic Compatibility (EMC)".
+- [40] IEC 61000-4-21: "Electromagnetic Compatibility (EMC) Part 4-21: Testing And Measurement Techniques Reverberation Chamber Test Methods".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Ancillary equipment:** Equipment (apparatus), used in connection with a receiver, transmitter or transceiver is considered as an ancillary equipment (apparatus) if:
+
+- the equipment is intended for use in conjunction with a receiver, transmitter or transceiver to provide additional operational and/or control features to the radio equipment, (e.g. to extend control to another position or location); and
+- the equipment cannot be used on a stand-alone basis to provide user functions independently of a receiver, transmitter or transceiver; and
+- the receiver, transmitter or transceiver to which it is connected, is capable of providing some intended operation such as transmitting and/or receiving without the ancillary equipment (i.e. it is not a sub-unit of the main equipment essential to the main equipment basic functions).
+
+**antenna connector:** connector at the conducted interface of the *BS type I-C*
+
+**Band category:** group of operating bands for which the same MSR scenarios apply
+
+**Base Station equipment:** Radio and/or ancillary equipment intended for operation at a fixed location and powered directly or indirectly (e.g. via an AC/DC converter or power supply) by AC mains network, or an extended local DC mains network.
+
+**Base Station RF bandwidth:** The bandwidth in which a Base Station transmits and/or receives multiple carriers and/or RATs simultaneously.
+
+**Base Station RF bandwidth edge:** The frequency of one of the edges of the Base Station RF bandwidth.
+
+**BS type 1-C:** NR base station operating at FR1 with requirements set consisting only of conducted requirements defined at individual *antenna connectors*.
+
+**Channel bandwidth:** The RF bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
+
+**Continuous phenomena (continuous disturbance):** Electromagnetic disturbance, the effects of which on a particular device or equipment cannot be resolved into a succession of distinct effects (IEC 60050-161 [14]).
+
+**Lower RF bandwidth edge:** The frequency of the lower edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements.
+
+**Maximum Base Station RF bandwidth:** The maximum RF bandwidth supported by a BS within an operating band.
+
+**Maximum throughput:** The maximum achievable throughput for a reference measurement channel.
+
+**MB-MSR Base Station:** MSR Base Station characterized by the ability of its transmitter and/or receiver to process two or more carriers in common active RF components simultaneously, where at least one carrier is configured at a different non-overlapping operating band than the other carrier(s).
+
+**MSR Base station:** Base Station characterized by the ability of its receiver and transmitter to process two or more carriers in common active RF components simultaneously in a declared RF bandwidth, where at least one carrier is of a different RAT than the other carrier(s).
+
+NOTE: A Base Station where receiver or transmitter processes carriers of different RATs simultaneously, but not through common active RF components, is not an MSR BS according to the above definition. Such a BS is in the present specification referred to as "other BS supporting more than one RAT".
+
+**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier.
+
+**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band.
+
+**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+**Radio communications equipment:** Telecommunications equipment which includes one or more transmitters and/or receivers and/or parts thereof for use in a fixed, mobile or portable application. It can be operated with ancillary equipment but if so, is not dependent on it for basic functionality.
+
+**Radio equipment:** Equipment which contains Radio digital unit and Radio unit.
+
+**Radio digital unit:** Equipment which contains base band and functionality for controlling Radio unit.
+
+**Radio unit:** Equipment which contains transmitter and/or receiver.
+
+**Port:** A particular interface, of the specified equipment (apparatus), with the electromagnetic environment. For example, any connection point on an equipment intended for connection of cables to or from that equipment is considered as a port (see figure 3.1.1).
+
+**Receiver exclusion band:** The receiver exclusion band is the band of frequencies over which no tests of radiated immunity of a receiver are made. The exclusion band for receivers is expressed relative to the base station receive band.
+
+**Signal and control port:** Port which carries information or control signals, excluding antenna ports.
+
+**Telecommunication port:** Ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks.
+
+**Throughput:** The number of payload bits successfully received per second for a reference measurement channel in a specified reference condition.
+
+**Transient phenomena:** Pertaining to or designating a phenomena or a quantity which varies between two consecutive steady states during a time interval short compared with the time-scale of interest (IEC 60050-161 [14]).
+
+**Transmitter exclusion band:** The transmitter exclusion band is the band of frequencies over which no tests of radiated immunity of a transmitter are made. The exclusion band for transmitters is expressed relative to the carrier frequencies used (the carrier frequencies of the base stations activated transmitter(s)).
+
+**Upper RF bandwidth edge:** The frequency of the upper edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements.
+
+![Diagram of an Apparatus showing various ports.](c78c2eefd86269d1740ab85a916f24f2_img.jpg)
+
+The diagram shows a central rectangle labeled "Apparatus" enclosed within a larger rectangle labeled "Enclosure Port". On the left side of the "Apparatus" rectangle, three lines extend to the left, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". On the right side of the "Apparatus" rectangle, three lines extend to the right, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port".
+
+Diagram of an Apparatus showing various ports.
+
+Figure 3.1-1: Examples of ports
+
+![Diagram of BS Equipment with a single enclosure solution.](18442e4e239480f0c3c95b547aa8fde2_img.jpg)
+
+The diagram shows a large rectangle labeled "BS Equipment". Inside this rectangle, on the right side, is a smaller rectangle labeled "Radio Equipment".
+
+Diagram of BS Equipment with a single enclosure solution.
+
+Figure 3.1-2: BS with single enclosure solution
+
+![Diagram of BS Equipment with a multiple enclosure solution.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg)
+
+The diagram shows a large rectangle labeled "BS Equipment". Inside this rectangle, on the left, is a rectangle labeled "Radio digital unit". To the right of the "Radio digital unit" is another rectangle labeled "Radio unit". Both the "Radio digital unit" and the "Radio unit" are enclosed within a dashed rectangle labeled "Radio Equipment".
+
+Diagram of BS Equipment with a multiple enclosure solution.
+
+Figure 3.1-3: BS with multiple enclosure solution
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                          |                                                                                                                                                                       |
+|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BW <sub>Channel</sub>    | Channel bandwidth                                                                                                                                                     |
+| F <sub>C,high</sub>      | Center frequency of the highest transmitted/received carrier.                                                                                                         |
+| F <sub>C,low</sub>       | Center frequency of the lowest transmitted/received carrier.                                                                                                          |
+| F <sub>DL_high</sub>     | The highest frequency of the downlink operating band                                                                                                                  |
+| F <sub>DL_low</sub>      | The lowest frequency of the downlink operating band                                                                                                                   |
+| f <sub>offset</sub>      | Frequency offset used for discovering narrowband response for receivers                                                                                               |
+| F <sub>offset, RAT</sub> | Frequency offset from F <sub>C,high</sub> to the <i>upper RF bandwidth edge</i> or F <sub>C,low</sub> to the <i>lower RF bandwidth edge</i> for a specific <i>RAT</i> |
+| F <sub>UL_high</sub>     | The highest frequency of the uplink operating band                                                                                                                    |
+| F <sub>UL_low</sub>      | The lowest frequency of the uplink operating band                                                                                                                     |
+| Δf <sub>OBUE</sub>       | Maximum offset of the operating band unwanted emissions mask from the operating band edge                                                                             |
+| Δf <sub>OOB</sub>        | Maximum offset of the out-of-band boundary from the uplink operating band edge                                                                                        |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|          |                                                 |
+|----------|-------------------------------------------------|
+| AC       | Alternating Current                             |
+| AMN      | Artificial Mains Network                        |
+| ARFCN    | Absolute Radio Frequency Channel Number         |
+| BC       | Band Category                                   |
+| BER      | Bit Error Ratio                                 |
+| BLER     | Block Error Ratio                               |
+| CDN      | Coupling/Decoupling Network                     |
+| CS       | Capability Set                                  |
+| DC       | Direct Current                                  |
+| E-UTRA   | Evolved Universal Terrestrial Radio Access      |
+| EARFCN   | E-UTRA Absolute Radio Frequency Channel Number  |
+| EMC      | Electromagnetic Compatibility                   |
+| EPC      | Evolved Packet Core                             |
+| ESD      | Electrostatic discharge                         |
+| EUT      | Equipment Under Test                            |
+| FR       | Frequency Range                                 |
+| FRC      | Fixed Reference Channel                         |
+| MB-MSR   | Multi-Band Multi-Standard Radio                 |
+| MSR      | Multi-Standard Radio                            |
+| NB-IoT   | Narrowband – Internet of Things                 |
+| NR       | New Radio                                       |
+| NR-ARFCN | NR Absolute Radio Frequency Channel Number      |
+| NTC      | Test Configuration for Non-contiguous operation |
+| RAT      | Radio Access Technology                         |
+| RF       | Radio frequency                                 |
+| rms      | root mean square                                |
+| TC       | Test Configuration                              |
+| UARFCN   | UTRA Absolute Radio Frequency Channel Number    |
+| UTRA     | Universal Terrestrial Radio Access              |
+
+# 4 Test conditions
+
+## 4.1 General
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.141 [11]. The test conditions shall be recorded in the test report.
+
+For a EUT which contains more than one BS, it is sufficient to perform tests relating to each type of port of each representative type of the BS forming part of the EUT. For an MSR BS or other BS supporting more than one RAT, tests shall be performed with RATs activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test. For other BS supporting more than one RAT however (other than MSR BS), tests relating to the antenna port(s) shall always be performed for each supported RAT.
+
+For BS capable of multi-band operation, the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the test configuration in subclause 4.5. Tests shall be performed relating to each type of port and all RATs per band shall be assessed during the tests.
+
+The manufacturer shall declare the supported operating band(s) according to subclause 4.4 of TS 37.141 [11]. Requirements apply only for the declared operating band and corresponding Band Category.
+
+The manufacturer shall declare the supported capability set(s) according to subclause 4.7 of TS 37.141 [11]. Tests performed on a Base Station according to a declared Capability Set cover all single RAT and multi-RAT configurations included in the declared Capability Set.
+
+## 4.2 Arrangements for establishing a communication link
+
+The wanted RF signal nominal frequency shall be selected by setting the channel number according to the following:
+
+- The NR Absolute Radio Frequency Channel Number (NR-ARFCN) for NR carrier,
+- The Absolute Radio Frequency Channel Number (EARFCN) for E-UTRA carrier,
+- The Absolute Radio Frequency Channel Number (UARFCN) for UTRA carrier,
+- The Absolute Radio Frequency Channel Number (ARFCN) for GSM/EDGE carrier,
+- NB-IoT Narrowband – Internet of Things
+
+A communication link shall be set up with a suitable test system capable of evaluating the required performance criteria (hereafter called "the test system") at the radio interface and telecommunication port/ports (the S1/Iub/Abis interface). The test system shall be located outside of the test environment.
+
+When the EUT is required to be in the transmit/receive mode, the following conditions shall be met:
+
+- The EUT shall be commanded to operate at maximum rated transmit power;
+- Adequate measures shall be taken to avoid the effect of the unwanted signal on the measuring equipment;
+- The wanted RF input signal level shall be set to a level where the performance is not limited by the receiver noise floor or strong signal effects.
+
+NOTE: 15 dB above the reference sensitivity level has been used as an example of the wanted input signal level in UTRA TDD, UTRA FDD, E-UTRA or NB-IoT EMC specifications for establishing a stable communication link. The RAT-specific reference sensitivity levels are specified in:
+
+- TS 25.142 [8] for UTRA TDD,
+- TS 25.141 [7] for UTRA FDD,
+- TS 36.141 [9] for E-UTRA or for NB-IoT,
+
+- TS 38.141-1 [36] for NR.
+- For GSM/EDGE the wanted receiver input signal level shall be set to a nominal value of -47 dBm.
+
+For immunity tests subclause 4.3 shall additionally apply.
+
+### 4.2.1 Multiple enclosure BS solution
+
+For a BS with multiple enclosures, the BS part with Radio digital unit and the Radio unit may be tested separately. Communication link shall be set up in the same way as if they are in single BS enclosure. The Radio Digital unit and the Radio unit shall communicate over an interface enabling establishment of a communication link.
+
+## 4.3 Narrow band responses on receivers
+
+Responses on receivers or duplex transceivers occurring during the immunity test at discrete frequencies which are narrow band responses (spurious responses), are identified by the following method:
+
+- if during an immunity test the quantity being monitored goes outside the specified tolerances (clause 6), it is necessary to establish whether the deviation is due to a narrow band response or to a wide band (EMC) phenomenon. Therefore, the test shall be repeated with the unwanted signal frequency first increased, and then decreased by an offset  $f_{\text{offset}}$ , where:
+  - For E-UTRA or for NR,  $f_{\text{offset}} = 2 \times BW_{\text{Channel}}$ , where  $BW_{\text{Channel}}$  is the channel bandwidth as defined in TS 36.104 [9] for E-UTRA, or in TS 38.104 [35] for NR;
+  - For UTRA,  $f_{\text{offset}} = 10 \text{ MHz}$
+  - For GSM/EDGE,  $f_{\text{offset}} = 400 \text{ kHz}$
+  - For NB-IoT,  $f_{\text{offset}} = 400 \text{ kHz}$
+- if the deviation disappears in either or both of the above offset cases, then the response is considered as a narrow band response;
+- if the deviation does not disappear, this may be due to the fact that the offset has made the frequency of the unwanted signal correspond to the frequency of another narrow band response. Under these circumstances the procedure is repeated with the increase and decrease of the frequency of the unwanted signal set to  $1.25 \times f_{\text{offset}}$ ;
+- if the deviation does not disappear with the increased and/or decreased frequency, the phenomenon is considered wide band and therefore an EMC problem and the equipment fails the test.
+
+Narrow band responses are disregarded.
+
+For an MSR BS or other BS supporting more than one RAT, the method above shall be applied for each RAT supported. For BS capable of multi-band operation, all supported operating bands shall be considered for narrowband responses.
+
+## 4.4 Exclusion bands
+
+An exclusion band is a band of frequencies over which no tests of radiated immunity are made.
+
+### 4.4.1 Transmitter exclusion band
+
+For testing of radiated immunity there shall be no transmitter exclusion band.
+
+### 4.4.2 Receiver exclusion band
+
+The receiver exclusion band for Base Stations is the band of frequencies over which no tests of radiated immunity of a receiver are made.
+
+The range of the exclusion band shall be:
+
+$$F_{UL\_low} - \Delta f_{OOB} < f < F_{UL\_high} + \Delta f_{OOB}$$
+
+Where:
+
+The value of  $F_{UL\_low}$  and  $F_{UL\_high}$  are defined for each operating band for NR, E-UTRA, UTRA and GSM/EDGE in TS 37.104 [6].
+
+The values of  $\Delta f_{OOB}$  are defined in table 4.4.2-1.
+
+**Table 4.4.2-1: Maximum  $\Delta f_{OOB}$  offset outside the uplink operating band**
+
+| <b>Operating band characteristics</b>                               | <b><math>\Delta f_{OOB}</math> (MHz)</b> |
+|---------------------------------------------------------------------|------------------------------------------|
+| $200 \text{ MHz} \geq F_{UL\_high} - F_{UL\_low}$                   | 20                                       |
+| $200 \text{ MHz} < F_{UL\_high} - F_{UL\_low} \leq 900 \text{ MHz}$ | 60                                       |
+
+For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by the BS.
+
+**Table 4.4-2: Void**
+
+**Table 4.4-3: Void**
+
+## 4.5 BS test configurations
+
+The present clause defines the BS test configurations that shall be used for demonstrating conformance. This is specified in table 4.5-1, 4.5-1a, 4.5-1b, and 4.5-1c for multi-RAT capable MSR Base Stations, in table 4.5-2 for single-RAT capable BS and in table 4.5-3 for multi-band capable BS. For other BS supporting more than one RAT (other than MSR BS), table 4.5-2 applies separately for each RAT supported.
+
+The test configurations apply according to the declared RAT Capability Set (CS) of the MSR Base Station according to subclause 4.7 of TS 37.141 [11] and the Band Category of the declared operating band (BC1, BC2 or BC3), as listed in the heading of each table.
+
+The test configurations (TCx) are defined in TS 37.141 [11], subclause 4.8.
+
+For a BS declared to be capable of contiguous operation only, the test configuration(s) in tables 4.5-1 and 4.5-2 denoted by a "C" shall be used for testing.
+
+For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacturer's declaration according to subclause 4.7.2 of TS 37.141 [11] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used.
+
+For a BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacturer's declaration according to subclause 4.7.2 of TS 37.141 [11] are not identical for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing.
+
+For a BS declared to support NB-IoT operating in-band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NI" shall be used for testing.
+
+For a BS declared to support NB-IoT operating in guard band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NG" shall be used for testing.
+
+For a BS declared to support NB-IoT operating in guard band and in-band, the test configuration(s) in table 4.5-1 and 4.5-2 denoted by "NG" or/and "NI" shall be used for testing.
+
+For a BS declared to support NB-IoT standalone, the test configuration(s) in table 4.5-1a, 4.5-1b and 4.5-2 and entries that refer to single-RAT specifications shall be used for testing.
+
+For immunity tests:
+
+- The communication link for the RAT(s) listed in the table shall be established according to subclause 4.2.
+
+- Tests for ports relating to the RAT(s) supported shall be performed according to subclause 4.1.
+
+**Table 4.5-1: Test configurations for single-band Multi-RAT capable MSR BS (CS3-6)**
+
+| Capability Set | UTRA + E-UTRA.<br>NB-IoT in-band,<br>NB-IoT guard band<br>(Note 2, Note 3) (CS 3) |                                                                              |                                 | GSM+<br>UTRA<br>(CS 4)                              | GSM +<br>E-UTRA,<br>NB-IoT in-<br>band,<br>NB-IoT<br>guard<br>band<br>(Note 2,<br>Note 3)<br>(CS 5) | GSM +<br>UTRA + E-<br>UTRA,<br>(CS 6)                | GSM+UTRA/<br>E-UTRA, UTRA+<br>E-UTRA,<br>NB-IoT in-band,<br>NB-IoT guard band<br>(Note 2,<br>Note 3)<br>(CS7)                                                                                                                   |
+|----------------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BS test case   | BC1                                                                               | BC2                                                                          | BC3                             | BC2                                                 | BC2                                                                                                 | BC2                                                  | BC2                                                                                                                                                                                                                             |
+| Emission tests | C: TC3a<br>CNC:<br>NTC3<br>C/NC:<br>TC3a and<br>NTC3<br>NI: TC16<br>NG: TC19      | C: TC3a<br>CNC:<br>NTC3<br>C/NC:<br>TC3a and<br>NTC3<br>NI: TC16<br>NG: TC19 | C: TC3b<br>NI: TC16<br>NG: TC19 | C: TC4a<br>CNC:<br>NTC4a<br>C/NC: TC4a<br>and NTC4a | C: TC4b<br>CNC:<br>NTC4b<br>C/NC:<br>TC4b and<br>NTC4b<br>NI: TC15<br>NG: TC18                      | C: TC4c<br>CNC:<br>NTC4c<br>C/NC: TC4c<br>and NTC4c  | C: (TC4a, TC3a)<br>(Note 4), TC4b<br><br>CNC: (NTC4a,<br>NTC3) (Note 4),<br>NTC4b<br><br>C/NC: (TC4a,<br>NTC4a, TC3a,<br>NTC3) (Note 4),<br>TC4b, NTC4b<br><br>NI: TC15, (TC16)<br>(Note 4)<br><br>NG: TC18, (TC19)<br>(Note 4) |
+| Immunity tests | C: TC3a<br>CNC:<br>NTC3<br>C/NC:<br>TC3a,<br>NTC3<br>NI: TC16<br>NG: TC19         | C: TC3a<br>CNC:<br>NTC3<br>C/NC:<br>TC3a,<br>NTC3<br>NI: TC16<br>NG: TC19    | C: TC3b<br>NI: TC16<br>NG: TC19 | C: TC5a<br>CNC:<br>NTC5a<br>C/NC:<br>TC5a,<br>NTC5a | C: TC5b<br>CNC:<br>NTC5b<br>C/NC:<br>TC5b,<br>NTC5b<br>NI: TC15<br>NG: TC18                         | C: TC5b<br>CNC:<br>NTC5c,<br>C/NC:<br>TC5b,<br>NTC5c | C: TC5b<br>CNC: NTC5b<br>C/NC: TC5b,<br>NTC5b<br>NI: TC15<br>NG: TC18                                                                                                                                                           |
+
+NOTE 1: Void
+
+NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing.
+
+NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing.
+
+NOTE 4: For Band 3, the test configuration is only applicable if UTRA is declared to be supported in Band 3.
+
+**Table 4.5-1a: Test configurations for single-band Multi-RAT capable MSR BS (CS9-13)**
+
+| Capability Set | GSM+NB-IoT<br>standalone<br>(CS 9) | UTRA +<br>NB-IoT<br>standalone (CS<br>10) |      | E-UTRA + NB-IoT<br>standalone<br>(CS 11) |      |      | GSM+UTRA+NB-<br>IoT standalone<br>(CS 12) | GSM+ E-UTRA+<br>NB-IoT<br>standalone<br>(CS 13) |
+|----------------|------------------------------------|-------------------------------------------|------|------------------------------------------|------|------|-------------------------------------------|-------------------------------------------------|
+| BS test case   | BC2                                | BC1                                       | BC2  | BC1                                      | BC2  | BC3  | BC2                                       | BC2                                             |
+| Emission tests | TC9                                | TC10                                      | TC10 | TC11                                     | TC11 | TC11 | TC12                                      | TC13                                            |
+| Immunity tests | TC9                                | TC10                                      | TC10 | TC11                                     | TC11 | TC11 | TC12                                      | TC13                                            |
+
+Table 4.5-1b: Test configurations for single-band Multi-RAT capable MSR BS (CS14-17)
+
+| Capability Set | UTRA + E-UTRA + NB-IoT standalone (CS 14) |      |      | GSM + UTRA + E-UTRA + NB-IoT standalone (CS 15) | NR + E-UTRA NB-IoT in-band(Note2) NB-IoT guard band(Note3) (CS 16)             |                                                                                | NR + NB-IoT standalone + E-UTRA NB-IoT in-band(Note2) NB-IoT guard band(Note3) (CS 17) |                                 |
+|----------------|-------------------------------------------|------|------|-------------------------------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|---------------------------------|
+| BS test case   | BC1                                       | BC2  | BC3  | BC2                                             | BC1 and BC2                                                                    | BC3                                                                            | BC1 and BC2                                                                            | BC3                             |
+| Emission tests | TC14                                      | TC14 | TC14 | TC13, (TC12, TC13) (NOTE4)                      | C, NI, NG: TC21<br>CNC, NCNI, NCNG: NTC21<br>C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21<br>CNC, NCNI, NCNG: NTC21<br>C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22<br>NI: TC22<br>NG: TC22                                                        | C: TC22<br>NI: TC22<br>NG: TC22 |
+| Immunity tests | TC14                                      | TC14 | TC14 | TC13                                            | C, NI, NG: TC21<br>CNC, NCNI, NCNG: NTC21<br>C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C, NI, NG: TC21<br>CNC, NCNI, NCNG: NTC21<br>C/NC, C/NCNI, C/NCNG: NTC21, TC21 | C: TC22<br>NI: TC22<br>NG: TC22                                                        | C: TC22<br>NI: TC22<br>NG: TC22 |
+
+NOTE 1: Void
+
+NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing.
+
+NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing.
+
+NOTE 4: For Band 3, the test configuration is only applicable if UTRA is declared to be supported in Band 3.
+
+**Table 4.5-1c: Test configurations for single-band Multi-RAT capable MSR BS (CS18-19)**
+
+| Capability Set | GSM + NR + E-UTRA<br>NB-IoT in-band (NOTE 2)<br>NB-IoT guard band (NOTE 3)<br>(CS 18) | UTRA + NR + E-UTRA<br>NB-IoT in-band (NOTE 2)<br>NB-IoT guard band (NOTE 3)<br>(CS19) |
+|----------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|
+| BS test case   | BC2                                                                                   | BC2                                                                                   |
+| Emission tests | C, NI, NG: TC21a<br>CNC, NCNI, NCNG: NTC21a<br>C/NC, C/NCNI, C/NCNG: NTC21a, TC21a    | C, NI, NG: TC21b<br>CNC, NCNI, NCNG: NTC21b<br>C/NC, C/NCNI, C/NCNG: NTC21b, TC21b    |
+| Immunity tests | C, NI, NG: TC21a<br>CNC, NCNI, NCNG: NTC21a<br>C/NC, C/NCNI, C/NCNG: NTC21a, TC21a    | C, NI, NG: TC21b<br>CNC, NCNI, NCNG: NTC21b<br>C/NC, C/NCNI, C/NCNG: NTC21b, TC21b    |
+
+NOTE 1: Void  
+NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing.  
+NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing.
+
+**Table 4.5-2: Test configurations for single-band Single-RAT multi-carrier capable BS**
+
+| Capability Set | UTRA (MC) capable BS (CS1)                    |                                               |         | E-UTRA (MC) capable BS (CS2)<br>NB-IoT in-band,<br>NB-IoT guard band<br>(Note 2, Note 3) |                                                                   |                                                                   | NB-IoT (MC)<br>capable BS (CS8) |     |     |
+|----------------|-----------------------------------------------|-----------------------------------------------|---------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-------------------------------------------------------------------|---------------------------------|-----|-----|
+| BS test case   | BC1                                           | BC2                                           | BC3     | BC1                                                                                      | BC2                                                               | BC3                                                               | BC1                             | BC2 | BC3 |
+| Emission tests | C: TC1a<br>CNC: NTC1a<br>C/NC: TC1a and NTC1a | C: TC1a<br>CNC: NTC1a<br>C/NC: TC1a and NTC1a | C: TC1b | C: TC2<br>CNC: NTC2<br>C/NC: TC2 and NTC2<br>NI: TC17<br>NG: TC20                        | C: TC2<br>CNC: NTC2<br>C/NC: TC2 and NTC2<br>NI: TC17<br>NG: TC20 | C: TC2<br>CNC: NTC2<br>C/NC: TC2 and NTC2<br>NI: TC17<br>NG: TC20 | TC8                             | TC8 | TC8 |
+| Immunity tests | C: TC1a<br>CNC: NTC1a<br>C/NC: TC1a, NTC1a    | C: TC1a<br>CNC: NTC1a<br>C/NC: TC1a, NTC1a    | C: TC1b | C: TC2<br>CNC: NTC2<br>C/NC: TC2, NTC2<br>NI: TC17<br>NG: TC20                           | C: TC2<br>CNC: NTC2<br>C/NC: TC2, NTC2<br>NI: TC17<br>NG: TC20    | C: TC2<br>CNC: NTC2<br>C/NC: TC2, NTC2<br>NI: TC17<br>NG: TC20    | TC8                             | TC8 | TC8 |
+
+NOTE 1: Void  
+NOTE 2: The support of NB-IoT in-band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NI" shall not be used for testing.  
+NOTE 3: The support of NB-IoT guard band operation is optional and declared by the manufacturer. If not supported, the test configurations denoted by "NG" shall not be used for testing.
+
+**Table 4.5-3: Test configurations for multi-band capable BS (CS1-CS7, CS16 and CS18-CS19)**
+
+| Capability Set | Multi-band testing |      |
+|----------------|--------------------|------|
+| BS test case   | BC1/BC2            | BC3  |
+| Emission tests | TC7b               | TC7b |
+| Immunity tests | TC7b               | TC7b |
+
+# 5 Performance assessment
+
+## 5.1 General
+
+The following information shall be recorded in or annexed to the test report:
+
+- the primary functions of the radio equipment to be tested during and after the EMC testing;
+- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment;
+- the method to be used to verify that a communications link is established and maintained;
+- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress;
+- the ancillary equipment to be combined with the radio equipment for testing (where applicable);
+- the information about ancillary equipment intended to be used with the radio equipment;
+- information about the common and/or RAT-specific active RF components and other HW blocks for a communication link in MSR BS or other BS supporting more than one RAT
+- information about the common and/or band-specific active RF components and other HW blocks for a communication link in BS capable of multi-band operation;
+- an exhaustive list of ports, classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+Performance assessment of a BS with multiple enclosures may be done separately for the BS part with the Radio digital unit and the Radio unit respectively, according to the manufacturer's choice.
+
+A communication link used by more than one RAT or more than one operating band, shall be assessed on all RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability.
+
+## 5.2 Assessment of performance in Downlink
+
+In the immunity tests, the output of the transmitter shall be connected to equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following:
+
+- Throughput assessment in TS 38.101-4 [38] in case of NR
+- Throughput assessment in TS 36.101 [31] in case of E-UTRA
+- BLER assessment in TS 25.101 [29] in case of UTRA FDD
+- BLER assessment in TS 25.102 [30] in case of UTRA TDD
+- BER assessment in annex A.1 in case of GSM/EDGE
+- Throughput assessment in TS 36.101 [31] in case of NB-IoT
+
+Power control shall be OFF during the immunity testing.
+
+## 5.3 Assessment of performance in Uplink
+
+In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following:
+
+- The value of the throughput shall be monitored in case of E-UTRA, and/or in case of NR
+
+- The value of the BLER shall be monitored in case of UTRA FDD and UTRA TDD
+- The value of the BER shall be monitored in case of GSM/EDGE (see annex A.2)
+- The value of the throughput shall be monitored in case of NB-IoT
+
+## 5.4 Ancillary equipment
+
+At the manufacturer's discretion the test may be performed on the ancillary equipment separately or on a representative configuration of the combination of radio and ancillary equipment. In each case EUT is tested against all applicable immunity and emission clauses of the present document and in each case, compliance enables the ancillary equipment to be used with different radio equipment.
+
+# 6 Performance criteria
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT below. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report.
+
+## 6.1 Performance criteria for continuous phenomena for BS
+
+### 6.1.1 E-UTRA performance criteria
+
+The throughput in table 6.1.1-1 is stated relative to the maximum throughput of the FRC. The maximum throughput for an FRC is equal to the payload size \* the number of uplink subframes per second.
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.1-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop then the criteria is two times the throughput reduction shown in table 6.1.1-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 6.1.1-1: E-UTRA BS Performance criteria for continuous phenomena for BS**
+
+| E-UTRA channel bandwidth (MHz) | Bearer information data rate                                                    | Performance criteria (Note 1, Note 2)   |
+|--------------------------------|---------------------------------------------------------------------------------|-----------------------------------------|
+| 1.4                            | FRC A1-1 in Annex A.1 in TS 36.104 [2]                                          | Throughput > 95 %<br>No loss of service |
+| 3                              | FRC A1-2 in Annex A.1 in TS 36.104 [2]                                          |                                         |
+| 3                              | FRC A1-6 in Annex A.1 in TS 36.104 [2] for E-UTRA with NB-IoT in-band operation |                                         |
+| 5                              | FRC A1-3 in Annex A.1 in TS 36.104 [2]                                          |                                         |
+| 5                              | FRC A1-7 in Annex A.1 in TS 36.104 [2] for E-UTRA with NB-IoT in-band operation |                                         |
+| 10                             | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3)                                 |                                         |
+| 15                             | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3)                                 |                                         |
+| 20                             | FRC A1-3 in Annex A.1 in TS 36.104 [2] (Note 3)                                 |                                         |
+
+- NOTE 1: The performance criteria, "Throughput > 95 % / No loss of service", applies also if a bearer with another characteristics is used in the test.
+- NOTE 2: The performance criteria, "Throughput > 90 % / No loss of service", applies instead if the Uplink and Downlink paths are evaluated as a one loop.
+- NOTE 3: This is the information data rate of a single instance of the bearer mapped to 25 resource blocks. The performance criteria shall be met for each consecutive application of a single instance of the bearer mapped to disjoint frequency ranges with a width of 25 resource blocks each.
+
+### 6.1.2 UTRA performance criteria
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.2-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the value shown in table 6.1.2-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 6.1.2-1: UTRA BS performance criteria for continuous phenomena for BS**
+
+| Bearer information data rate | Performance criteria                   |
+|------------------------------|----------------------------------------|
+| 12.2 kbps                    | BLER < $10^{-2}$<br>No loss of service |
+| 64 kbps                      |                                        |
+| 144 kbps                     |                                        |
+| 384 kbps                     |                                        |
+
+- NOTE: The performance criteria, "BLER <  $10^{-2}$  / No loss of service", applies also if a bearer with another characteristics is used in the test.
+
+### 6.1.3 GSM/EDGE performance criteria
+
+#### 6.1.3.1 GSM/EDGE downlink
+
+The BER of the downlink shall be assessed during the test according to one of the test methods of Annex A.1.
+
+If the test method of Annex A.1.1 is used, the measured BER of the class 2 bits of TCH/FS shall not exceed 1,6 % during the test.
+
+- NOTE: This BER is the upper limit in TS 45.008 [32] for RXQUAL = 3.
+
+If the test method of Annex A.1.2 is used, the value of RXQUAL shall not exceed 3 during the test.
+
+At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data, and the communication link shall have been maintained.
+
+#### 6.1.3.2 GSM/EDGE uplink
+
+The BER of the uplink shall be assessed during the test according to one of the test methods of Annex A.2.
+
+If the test method of Annex A.2.1 is used, the value of RXQUAL shall not exceed 3 during the test.
+
+If the test method of Annex A.2.2 is used, the measured BER of the class 2 bits of TCH/FS shall not exceed 1,6 % during the test.
+
+- NOTE: This BER is the upper limit in TS 45.008 [32] for RXQUAL = 3.
+
+For a base station, the RXQUAL of the uplink shall not exceed three (3) measured during the test sequence.
+
+At the conclusion of the test the EUT shall operate as intended with no loss of user control functions or stored data, and the communication link shall have been maintained.
+
+### 6.1.4 NB-IoT performance criteria
+
+The throughput in table 6.1.4-1 is stated relative to the maximum throughput of the FRC. The Maximum throughput for an FRC equals the Payload size / (Number of Resource Unit \* time to send one Resource Unit).
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.4-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the throughput reduction shown in table 6.1.4-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 6.1.4-1: NB-IoT BS Performance criteria for continuous phenomena for BS**
+
+| <b>NB-IoT Sub-carrier spacing [kHz]</b> | <b>Reference measurement channel</b>     | <b>Performance criteria (Note 1, Note 2)</b> |
+|-----------------------------------------|------------------------------------------|----------------------------------------------|
+| 15                                      | FRC A14-1 in Annex A.14 in TS 36.104 [2] | Throughput > 95 %<br>No loss of service      |
+| 3.75                                    | FRC A14-2 in Annex A.14 in TS 36.104 [2] |                                              |
+
+NOTE 1: The performance criteria, "Throughput > 95 % / No loss of service", applies also if a bearer with another characteristics is used in the test.
+
+NOTE 2: The performance criteria, "Throughput > 90 % / No loss of service", applies instead if the Uplink and Downlink paths are evaluated as a one loop.
+
+### 6.1.5 NR performance criteria
+
+The throughput in table 6.1.5-1 is stated relative to the maximum throughput of the FRC. The maximum throughput for an FRC is equal to the [payload size \* the number of uplink subframes per second].
+
+The BS Uplink and Downlink paths shall each meet the performance criteria defined in table 6.1.5-1 during the test. If the Uplink and Downlink paths are evaluated as a one loop, then the criterion is two times the throughput reduction shown in table 6.1.5-1. After each test case BS shall operate as intended with no loss of user control function, stored data and the communication link shall be maintained.
+
+**Table 6.1.5-1: NR BS performance criteria for continuous phenomena for BS**
+
+| <b>NR channel bandwidth (MHz)</b>       | <b>Sub-carrier spacing (kHz)</b> | <b>Bearer information data rate (as in TS 38.104 [35], annex A.1)</b> | <b>Performance criteria (Note1, Note 2)</b> |
+|-----------------------------------------|----------------------------------|-----------------------------------------------------------------------|---------------------------------------------|
+| 5, 10, 15                               | 15                               | G-FR1-A1-1                                                            | Throughput > 95 %,<br>No loss of service    |
+| 10, 15                                  | 30                               | G-FR1-A1-2                                                            |                                             |
+| 10, 15                                  | 60                               | G-FR1-A1-3                                                            |                                             |
+| 20, 25, 30, 40, 50                      | 15                               | G-FR1-A1-4                                                            |                                             |
+| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 30                               | G-FR1-A1-5                                                            |                                             |
+| 20, 25, 30, 40, 50, 60, 70, 80, 90, 100 | 60                               | G-FR1-A1-6                                                            |                                             |
+
+NOTE 1: The performance criteria, throughput > 95 %, no loss of service, applies also if a bearer with another characteristics is used in the test.
+
+NOTE 2: The performance criteria, throughput > 90 %, no loss of service, applies instead if the uplink and downlink paths are evaluated as a one loop.
+
+## 6.2 Performance criteria for transient phenomena for BS
+
+At the conclusion of each exposure the EUT shall operate with no user noticeable loss of the communication link.
+
+At the conclusion of the total test comprising the series of individual exposures the EUT shall operate as intended with no loss of user control functions or stored data, as declared by the manufacturer, and the communication link shall have been maintained.
+
+The below characteristics should be chosen based on manufacture declaration and are defined as:
+
+- The E-UTRA channel bandwidth and bearer information data rate are defined in table 6.1.1-1.
+- The UTRA bearer information data rate are defined in table 6.1.2-1.
+- The GSM/EDGE the test BER assessment are defined in subclause 6.1.3.1 for downlink and subclase 6.1.3.2 for uplink, while the criteria is defined in subclause 6.2.
+- The NB-IoT sub-carrier spacing and reference measurement channel are defined in table 6.1.4-1.
+- The NR channel bandwidth, sub-carrier spacing and bearer information data rate are defined in table 6.1.5-1.
+
+## 6.3 Performance criteria for continuous phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended during and after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+## 6.4 Performance criteria for transient phenomena for Ancillary equipment
+
+The apparatus shall continue to operate as intended after the test. No degradation of performance or loss of function is allowed below the performance level specified by the manufacturer, when the apparatus is used as intended. The performance level may be replaced by a permissible performance loss. During the test, degradation of performance is however allowed. If the minimum performance level or the permissible performance loss is not specified by the manufacturer, either of these may be derived from the product description and documentation and what the user may reasonably expect from the apparatus if used as intended.
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+Table 7.1-1: Emission applicability
+
+| Phenomenon                       | Application                | Equipment test requirement |                     | Reference subclause in the present document | Reference standard                        |
+|----------------------------------|----------------------------|----------------------------|---------------------|---------------------------------------------|-------------------------------------------|
+|                                  |                            | BS equipment               | Ancillary equipment |                                             |                                           |
+| Radiated emission (NOTE)         | Enclosure                  | applicable                 |                     | 8.2.1                                       | ITU-R SM.329 [15]                         |
+| Radiated emission                | Enclosure                  |                            | applicable          | 8.2.2                                       | CISPR 32 [34]                             |
+| Conducted emission               | DC power input/output port | applicable                 | applicable          | 8.3                                         | CISPR 32 [34]                             |
+| Conducted emission               | AC mains input/output port | applicable                 | applicable          | 8.4                                         | CISPR 32 [34]                             |
+| Harmonic current emissions       | AC mains input port        | applicable                 | applicable          | 8.5                                         | IEC 61000-3-2 [19] or IEC 61000-3-12 [20] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                 | applicable          | 8.6                                         | IEC 61000-3-3 [21] or IEC 61000-3-11 [22] |
+| Conducted emission               | Telecommunication port     | applicable                 | applicable          | 8.7                                         | CISPR 32 [34]                             |
+
+NOTE: The radiated emissions requirement for the BS equipment covers radiated emissions in the spurious domain. For GSM/EDGE, it corresponds to the "Radiated spurious emissions" requirement in TS 51.021 [10] for radio aspects.
+
+## 7.2 Immunity
+
+Table 7.2-1: Immunity applicability
+
+| Phenomenon                               | Application                                                               | Equipment test requirement |                     | Reference subclause in the present document | Reference Standard  |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------|---------------------------------------------|---------------------|
+|                                          |                                                                           | BS equipment               | Ancillary equipment |                                             |                     |
+| RF electromagnetic field (80 - 6000 MHz) | Enclosure                                                                 | applicable                 | applicable          | 9.2                                         | IEC 61000-4-3 [23]  |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | applicable          | 9.3                                         | IEC 61000-4-2 [24]  |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | 9.4                                         | IEC 61000-4-4 [25]  |
+| RF common mode 0,15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | applicable          | 9.5                                         | IEC 61000-4-6 [26]  |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | applicable          | 9.6                                         | IEC 61000-4-11 [27] |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | applicable          | 9.7                                         | IEC 61000-4-5 [28]  |
+
+# 8 Emission
+
+## 8.1 Test configurations
+
+This subclause defines the configurations for emission tests as follows:
+
+- the equipment shall be tested under normal test conditions as specified in the functional standards;
+- the test configuration shall be as close to normal intended use as possible;
+- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- the test conditions, test configuration and mode of operation shall be recorded in the test report;
+- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- the test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.2 Radiated emission from Base Station and ancillary equipment
+
+### 8.2.1 Radiated emission for Base Stations
+
+This test is applicable to BS, except for BS that are only single-RAT GSM/EDGE capable. This test shall be performed on a representative configuration of the BS.
+
+For BS that are only single-RAT GSM/EDGE capable, the test method and limits in clause 8 of TS 51.021 [10] apply.
+
+#### 8.2.1.1 Definition
+
+This test assesses the ability of BS to limit unwanted emission from the enclosure port.
+
+#### 8.2.1.2 Test method
+
+- a) A test site fulfilling the requirements of ITU-R SM. 329 [15] shall be used. The BS shall be placed on a non-conducting support and shall be operated from a power source via a RF filter to avoid radiation from the power leads.
+
+Mean power of any spurious components shall be detected by the test antenna and measuring receiver (e.g. a spectrum analyser). At each frequency at which a component is detected, the BS shall be rotated and the height of the test antenna adjusted to obtain maximum response, and the effective radiated power (e.r.p.) of that component determined by a substitution measurement. The measurement shall be repeated with the test antenna in the orthogonal polarization plane.
+
+NOTE: Effective radiated power (e.r.p.) refers to the radiation of a half wave tuned dipole instead of an isotropic antenna. There is a constant difference of 2,15 dB between e.i.r.p. and e.r.p.
+
+$$\text{e.r.p. (dBm)} = \text{e.i.r.p. (dBm)} - 2,15 \text{ Ref: ITU-R SM.329 ANNEX 1 [15].}$$
+
+- b) The BS shall transmit with rated power declared by the manufacturer with all transmitters active. Set the BS to transmit a signal as stated in subclause 4.5.
+- c) The received power shall be measured over the frequency range from  $30 \text{ MHz}$  to  $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}}$  and from  $F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$  up to  $12.75 \text{ GHz}$ . The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least  $1 \text{ MHz}$ . Unless otherwise stated, all measurements are done as mean power (RMS).  $\Delta f_{\text{OBUE}}$  is defined in table 8.2.1.3-2.
+
+#### 8.2.1.3 Limits
+
+The frequency boundary and reference bandwidths for the detailed transitions of the limits between the requirements for out of band emissions and spurious emissions are based on ITU-R Recommendations SM.329 [10] and SM.1539 [23].
+
+The BS shall meet the limits below:
+
+**Table 8.2.1.3-1: Limits for radiated emissions from BS**
+
+| Frequency range                                                                                                                | Minimum requirement (e.r.p.)/Reference bandwidth |
+|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|
+| $30 \text{ MHz} \leq f < 1000 \text{ MHz}$                                                                                     | -36 dBm/ 100 kHz                                 |
+| $1 \text{ GHz} \leq f < 12.75 \text{ GHz}$                                                                                     | -30 dBm/ 1MHz                                    |
+| $F_{\text{DL\_low}} - \Delta f_{\text{OBUE}} < f < F_{\text{DL\_high}} + \Delta f_{\text{OBUE}}$ (NOTE)                        | Not defined                                      |
+| NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply. |                                                  |
+
+**Table 8.2.1.3-2: Maximum offset of OBUE outside the downlink operating band**
+
+| Operating band characteristics                                                    | $\Delta f_{\text{OBUE}}$ (MHz) |
+|-----------------------------------------------------------------------------------|--------------------------------|
+| $F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 200 \text{ MHz}$                   | 10                             |
+| $200 \text{ MHz} < F_{\text{DL\_high}} - F_{\text{DL\_low}} \leq 900 \text{ MHz}$ | 40                             |
+
+#### 8.2.1.4 Interpretation of the measurement results
+
+The interpretation of the results recorded in a test report for the radiated emission measurements described in the present document shall be as follows:
+
+- the measured value related to the corresponding limit will be used to decide whether an equipment meets the requirements of the present document;
+- the value of the measurement uncertainty for the measurement of each parameter shall be included in the test report;
+- the recorded value of the measurement uncertainty shall be, for each measurement, equal to or lower than the figures in table 8.2.1.4-1 for BS.
+
+Table 8.2.2 specifies the Maximum measurement uncertainty of the Test System. The Test System shall enable the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated.
+
+A confidence level of 95% is the measurement uncertainty tolerance interval for a specific measurement that contains 95% of the performance of a population of test equipment.
+
+**Table 8.2.1.4-1: Maximum measurement uncertainty (BS)**
+
+| Parameter                                                                                                                                 | Uncertainty for EUT dimension $\leq 1$ m | Uncertainty for EUT dimension $> 1$ m |
+|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------------------------|
+| Effective radiated RF power between 30 MHz to 180 MHz                                                                                     | $\pm 6$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 180 MHz to 4 GHz                                                                                      | $\pm 4$ dB                               | $\pm 6$ dB                            |
+| Effective radiated RF power between 4 GHz to 12,75 GHz                                                                                    | $\pm 6$ dB                               | $\pm 9$ dB (NOTE)                     |
+| NOTE: This value may be reduced to $\pm 6$ dB when further information on the potential radiation characteristic of the EUT is available. |                                          |                                       |
+
+NOTE: If the Test System for a test is known to have a measurement uncertainty greater than that specified in table 8.2.2, this equipment can still be used, provided that an adjustment is made follows:
+
+Any additional uncertainty in the Test System over and above that specified in table 8.2.1.4-1 is used to tighten the Test Requirements - making the test harder to pass. This procedure will ensure that a Test System not compliant with table 8.2.1.4-1 does not increase the probability of passing a EUT that would otherwise have failed a test if a Test System compliant with table 8.2.1.4-1 had been used.
+
+### 8.2.2 Radiated emission, ancillary equipment
+
+This test is applicable to ancillary equipment. This test shall be performed on a representative configuration of the ancillary equipment.
+
+#### 8.2.2.1 Definition
+
+This test assesses the ability of ancillary equipment to limit unwanted emission from the enclosure port.
+
+#### 8.2.2.2 Test method
+
+The test method shall be in accordance with CISPR 32 [34].
+
+#### 8.2.2.3 Limits
+
+The ancillary equipment shall meet the limits according to CISPR 32 [34] table A.4 and table A.5.
+
+For the referred limit values, the following shall apply:
+
+- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency.
+- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency.
+
+**Table 8.2.2.3-1: Void****Table 8.2.2.3-2: Void**
+
+Alternatively, for *ancillary equipment* intended to be used in telecommunication centres only, the class A limits given in CISPR 32 [34], annex A, table A.2 and table A.3 may be used.
+
+## 8.3 Conducted emission DC power input/output port
+
+This test is applicable to equipment which may have DC cables longer than 3 m.
+
+If the DC power cable of the radio equipment is intended to be less than 3 m in length and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.4.
+
+This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.3.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the DC power input/output ports.
+
+### 8.3.2 Test method
+
+The test method shall be in accordance with CISPR 32 [34] and the Artificial Mains Network (AMN) shall be connected to a DC power source.
+
+In the case of DC output ports, the ports shall be connected via an AMN to a load drawing the rated current of the source.
+
+A measuring receiver shall be connected to each AMN measurement port in turn and the conducted emission recorded.
+
+The equipment shall be installed with a ground plane as defined in CISPR 32 [34]. The reference earth point of the AMNs shall be connected to the reference ground plane with a conductor as short as possible.
+
+The measurement receiver shall be in accordance with the requirements of CISPR 32 [34].
+
+### 8.3.3 Limits
+
+The equipment shall meet the limits according to CISPR 32 [11] table A.9, which are defined for average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+Where there is a step in the referred limit values, the lower value shall be applied at the transition frequency.
+
+**Table 8.3.3-1: Void**
+
+## 8.4 Conducted emissions, AC mains power input/output port
+
+This test is applicable to equipment powered by the AC mains.
+
+This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT.
+
+This test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 8.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to limit internal noise from the AC mains power input/output ports.
+
+### 8.4.2 Test method
+
+The test method shall be in accordance with CISPR 32 [34].
+
+### 8.4.3 Limits
+
+The equipment shall meet the limits according to CISPR 32 [11] table A.10, which are defined the average detector receiver and for quasi-peak detector receiver. If the average limit is met when using a quasi-peak detector, the equipment shall be deemed to meet both limits and measurement with the average detector receiver is not necessary.
+
+For the referred limit values following shall apply:
+
+- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency.
+
+- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency.
+
+##### **Table 8.4.3-1: Void**
+
+Alternatively, for equipment intended to be used in telecommunication centres the limits given in CISPR 32 [11] table A.9 shall be used.
+
+##### **Table 8.4.3-2: Void**
+
+## 8.5 Harmonic current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [19] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [20] applies.
+
+## 8.6 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [21] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [20] applies.
+
+## 8.7 Telecommunication ports
+
+This test is applicable for radio equipment and/or ancillary equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment, the associated ancillary equipment, or a representative configuration of the combination of radio and ancillary equipment.
+
+### 8.7.1 Definition
+
+This test assesses the EUT unwanted emission present at the telecommunication ports.
+
+### 8.7.2 Test method
+
+The test method shall be in accordance with CISPR 32 [34].
+
+The measurement frequency range extends from 150 kHz to 30 MHz.
+
+### 8.7.3 Limits
+
+The telecommunication ports shall meet the limits according to CISPR 32 [34] table A.12, clause A12.2.
+
+For the referred limit values, following shall apply:
+
+- Where the limits value varies over a given frequency range, it changes linearly with respect to the logarithm of the frequency.
+- Where there is a step in the relevant limit, the lower value shall be applied at the transition frequency.
+
+###### **Table 8.7.3-1: Void**
+
+Alternatively, for equipment intended to be used in telecommunication centres only, the limits given in CISPR 32 [11] table A.11 clause A11.2 shall be used.
+
+Table 8.7.3-2: Void
+
+# 9 Immunity
+
+## 9.1 Test configurations
+
+This subclause defines the configurations for immunity tests as follows:
+
+- the equipment shall be tested under normal test conditions as specified in the functional standards;
+- the test configuration shall be as close to normal intended use as possible;
+- if the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- if the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- the test conditions, test configuration and mode of operation shall be recorded in the test report;
+- ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- Immunity tests on the entire base station shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub/ Abis interface (e.g. with an RNC/EPC/BSC simulator) and evaluating the BLER/throughput/BER (see Figure 9.1-1);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub/ Abis interface. BLER/throughput/BER evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the radio interface or S1/Iub/ Abis interface. In case of looping is used care have to be taken that the BLER/throughput/BER information doesn't change due to looping.
+- For BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each RAT and/or operating band.
+
+![Diagram of communication link setup for BS immunity measurement](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg)
+
+The diagram illustrates the communication link setup for BS immunity measurement. It features three main components: a 'Mobile simulator' on the left, a 'Base station' in the center, and an 'EPC/RNC/BSC simulator' on the right. The Base station is divided into three sections: 'TX' (Transmitter) at the top, 'RX 1' (Receiver 1) in the middle, and 'RX 2 (terminated)' (Receiver 2, terminated) at the bottom. Arrows indicate the flow of communication: from the Mobile simulator to the Base station TX, from the Base station TX to the EPC/RNC/BSC simulator, from the EPC/RNC/BSC simulator to the Base station RX 1, and from the Base station RX 2 to the Mobile simulator.
+
+Diagram of communication link setup for BS immunity measurement
+
+Figure 9.1-1: Communication link set up for BS immunity measurement
+
+## 9.2 RF electromagnetic field (80 MHz - 6000 MHz)
+
+The test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.2.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure.
+
+### 9.2.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-3 [23], which specifies test methodology based on anechoic chamber. The use of reverberation chamber test method according to IEC 61000-4-21 [40], clause 6.1 and Annex D as alternative method is allowed.
+
+The following requirements shall apply:
+
+- the test level shall be 3 V/m amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 1 % of the momentary frequency;
+- the test shall be performed over the frequency range 80 MHz - 6000 MHz with the exception of the exclusion band for receivers (see subclause 4.4);
+- responses in stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies selected during the test shall be recorded in the test report.
+
+### 9.2.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.3 shall apply.
+
+## 9.3 Electrostatic discharge
+
+The test shall be performed on a representative configuration of the radio equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.3.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of an electrostatic discharge.
+
+### 9.3.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-2 [24]:
+
+- for contact discharge, the equipment shall pass at  $\pm 4$  kV;
+- for air discharge shall pass at  $\pm 8$  kV;
+- electrostatic discharge shall be applied to all exposed surfaces of the EUT except where the user documentation specially indicates a requirement for appropriate protective measures.
+
+NOTE: Ensure that the EUT is fully discharged between each ESD exposure.
+
+### 9.3.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+## 9.4 Fast transients common mode
+
+The test shall be performed on AC mains power input ports.
+
+This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.4.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the event of fast transients present on one of the input/output ports.
+
+### 9.4.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-4 [25]:
+
+- the test level for signal ports, telecommunication ports and control ports shall be 0,5 kV open circuit voltage as given in IEC 61000-4-4 [25];
+- the test level for DC power input/output ports shall be 0.5 kV open circuit voltage as given in IEC 61000-4-4 [25];
+- the test level for AC mains power input ports shall be 1 kV open circuit voltage as given in IEC 61000-4-4 [25].
+
+For AC and DC power input ports the transients shall be applied (in parallel) to all the conductors in the cable with reference to the cabinet reference earth (true common mode) and the source impedance shall be 50 Ω.
+
+### 9.4.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+## 9.5 RF common mode (0,15 MHz - 80 MHz)
+
+The test shall be performed on AC mains power input/output ports.
+
+This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [26].
+
+### 9.5.1 Definition
+
+This test assesses the ability of radio equipment and ancillary equipment to operate as intended in the presence of a radio frequency electromagnetic disturbance.
+
+### 9.5.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-6 [26]:
+
+- the test signal shall be amplitude modulated to a depth of 80 % by a sinusoidal audio signal of 1 kHz;
+- the stepped frequency increments shall be 50 kHz in the frequency range 150 kHz to 5 MHz and 1% frequency increment of the momentary frequency in the frequency range 5 MHz to 80 MHz;
+- the test level shall be severity level 2 as given in IEC 61000-4-6 [26] corresponding to 3 V rms, at a transfer impedance of 150 Ω;
+- the test shall be performed over the frequency range 150 kHz - 80 MHz;
+- the injection method to be used shall be selected according to the basic standard IEC 61000-4-6 [26];
+- responses of stand-alone receivers or receivers which are part of transceivers occurring at discrete frequencies which are narrow band responses, shall be disregarded, see subclause 4.3;
+- the frequencies of the immunity test signal selected and used during the test shall be recorded in the test report.
+
+### 9.5.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.1 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.3 shall apply.
+
+## 9.6 Voltage dips and interruptions
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.6.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+### 9.6.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-11 [27], where the test levels shall be:
+
+- Voltage dip: 0 % residual voltage for 0.5 cycle;
+- Voltage dip: 0 % residual voltage for 1 cycle;
+- Voltage dip: 70 % residual voltage for 25/30 cycles (at 50/60 Hz);
+- Voltage interruption: 0 % residual voltage for 250/300 cycles (at 50/60 Hz).
+
+### 9.6.3 Performance criteria
+
+For a 0 % residual voltage dip test, the performance criteria for transient phenomena shall be applied:
+
+- Criteria 6.2 for base station
+- Criteria 6.4 for ancillary equipment
+
+For a 70% residual voltage dip test and for voltage interruption test, the following applies:
+
+1. In the case where the equipment is fitted with or connected to a battery back-up, the following performance criteria shall be applied:
+  - Criteria 6.2 for base station
+  - Criteria 6.4 for ancillary equipment
+2. In the case where the equipment is powered solely from the AC mains supply (without the use of a parallel battery back-up) volatile user data may have been lost and if applicable the communication link need not to be maintained and lost functions should be recoverable by user or operator:
+  - No unintentional responses shall occur at the end of the test, when the voltage is restored to nominal
+  - In the event of loss of communications link or in the event of loss of user data, this fact shall be recorded in the test report
+
+## 9.7 Surges, common and differential mode
+
+The tests shall be performed on AC mains power input ports.
+
+This test shall be additionally performed on telecommunication ports.
+
+These tests shall be performed on a representative configuration of the equipment, the associated ancillary equipment, or representative configuration of the combination of radio and ancillary equipment.
+
+### 9.7.1 Definition
+
+These tests assess the ability of radio equipment and ancillary equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+### 9.7.2 Test method and level
+
+The test method shall be in accordance with IEC 61000-4-5 [28].
+
+The requirements and evaluation of test results given in subclause 9.7.2.1 (telecommunication ports, outdoor cables), subclause 9.7.2.2 (telecommunication ports, indoor cables) and subclause 9.7.2.3 (AC power ports) shall apply, but no test shall be required where normal functioning cannot be achieved, because of the impact of the CDN on the EUT.
+
+#### 9.7.2.1 Test method for telecommunication ports directly connected to outdoor cables
+
+The test level for telecommunications ports, intended to be directly connected to the telecommunications network via outdoor cables, shall be 1 kV line to ground as given in IEC 61000-4-5 [28]. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [28].
+
+The test generator shall provide the 1,2/50  $\mu\text{s}$  pulse as defined in IEC 61000-4-5 [28].
+
+#### 9.7.2.2 Test method for telecommunication ports connected to indoor cables
+
+The test level for telecommunication ports, intended to be connected to indoor cables (longer than 10 m) shall be 0,5 kV line to ground. In this case the total output impedance of the surge generator shall be in accordance with the basic standard IEC 61000-4-5 [28].
+
+The test generator shall provide the 1,2/50  $\mu\text{s}$  pulse as defined in IEC 61000-4-5 [28].
+
+#### 9.7.2.3 Test method for AC power ports
+
+The test level for AC power input ports shall be 2 kV line to ground, and 1 kV line to line, with the output impedance of the surge generator as given in IEC 61000-4-5 [28].
+
+In telecommunication centres 1 kV line to ground and 0,5 kV line to line shall be used.
+
+The test generator shall provide the 1,2/50  $\mu\text{s}$  pulse as defined in IEC 61000-4-5 [28].
+
+### 9.7.3 Performance criteria
+
+#### Base station:
+
+The performance criteria of subclause 6.2 shall apply.
+
+#### Ancillary equipment:
+
+The performance criteria of subclause 6.4 shall apply.
+
+# --- Annex A (normative): BER assessment for GSM/EDGE
+
+## A.1 Assessment of BER at the output of a transmitter
+
+The BER at the output of the transmitter may be assessed using either of the techniques described below.
+
+### A.1.1 Assessment of BER using static layer 1 functions
+
+The transmitter under test shall be operated according to the test case of TS 51.021 [10], subclause 6.1.2.
+
+The bit sequence from the output of the transmitter shall be monitored by the test system according to the test case of TS 51.021 [10], subclause 7.1.2, and the BER of the class 2 bits for TCH/FS assessed. The BER shall not exceed the values specified in subclause 6.1 of the present document.
+
+If the EUT does not support TCH/FS, the manufacturer shall declare the logical channel for which the performance shall be assessed, and the corresponding performance criteria.
+
+### A.1.2 Assessment of BER using RXQUAL
+
+The output of the transmitter shall be connected to an equipment which meets the requirements of TS 51.010-1 [33] for the assessment of RXQUAL. The level of the signal supplied to the equipment should be within the range for which the assessment of RXQUAL is not impaired. The RXQUAL shall be monitored during the test. The RXQUAL shall not exceed the values specified in subclause 6.1 of the present document.
+
+NOTE: This equipment can be a GSM mobile station with suitable provision for the monitoring of RXQUAL.
+
+## --- A.2 Assessment of BER at the output of a receiver
+
+The BER at the output of the receiver may be assessed using either of the techniques described below.
+
+### A.2.1 Assessment of BER using RXQUAL
+
+The value of the RXQUAL reported by the BTS or BSS shall be monitored using suitable test equipment.
+
+### A.2.2 Assessment of BER using reported BER
+
+The BER of the class 2 bits at the output of the receiver shall be assessed using suitable test equipment.
+
+If the EUT does not support TCH/FS, the manufacturer shall declare the logical channel for which the performance shall be assessed, and the corresponding performance criteria.
+
+NOTE: This can be performed by a "test loopback" which uses the transmitter of the BTS to return the data which has been decoded by the receiver back to the test equipment which generated the bit sequence. For immunity tests of signal ports, the "test loopback" includes an external connection between signal ports.
+
+# Annex B (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |             |  |
+|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | New version |  |
+| 2010-02        | R4#54   | R4-100572 |      |     |     | Specification skeleton                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 0.0.1       |  |
+| 2010-04        | R4#55   | R4-101577 |      |     |     | E-mail approved Text Proposals after RAN4 AH#2:<br>R4-101189, "TS 37.113: TP on References, Definitions, symbols and abbreviations (TS ch 2 and 3) "<br>R4-101190, "TS 37.113: TP on Test conditions (TS ch 4)"<br>R4-101191, "TS 37.113: TP on Performance assessment (TS ch 5)"<br>R4-101192, "TS 37.113: TP on Performance Criteria (TS ch 6)"<br>R4-101193, "TS 37.113: TP on Applicability overview (TS ch 7)"<br>R4-101194, "TS 37.113: TP on Emission (TS ch 8)"<br>R4-101195, "TS 37.113: TP on Immunity (TS ch 9)" | 0.1.0       |  |
+| 2010-06        | RP#48   | RP-100581 |      |     |     | Presentation to TSG RAN.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 1.0.0       |  |
+| 2010-06        | RP#48   | RP-100581 |      |     |     | Approval by TSG RAN.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 9.0.0       |  |
+| 2010-09        | RP-49   | RP-100923 | 002  | 1   |     | EMC updates for multi-RAT operation                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 9.1.0       |  |
+| 2010-09        | RP-49   | RP-100923 | 003  |     |     | Clarification of radiated emissions requirement                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 9.1.0       |  |
+| 2010-09        | RP-49   | RP-100927 | 001  |     |     | CR LTE_TDD_2600_US spectrum band definition additions for MSR BS to TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                               | 10.0.0      |  |
+| 2010-12        | RP-50   | RP-101345 | 010  |     |     | Band XII/12 frequency range                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 10.1.0      |  |
+| 2010-12        | RP-50   | RP-101346 | 006  |     |     | MSR test configuration for EMC                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 10.1.0      |  |
+| 2010-12        | RP-50   | RP-101346 | 008  |     |     | Correction of CR implementation in clause 6.2 of TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | 10.1.0      |  |
+| 2010-12        | RP-50   | RP-101356 | 004  | 1   |     | Band 42 and 43 parameters for UMTS/LTE 3500 (TDD) for TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 10.1.0      |  |
+| 2011-06        | RP-52   | RP-110812 | 014  | 1   |     | Add 2GHz S-Band (Band 23) in 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 10.2.0      |  |
+| 2011-09        | RP-53   | RP-111255 | 017  |     |     | Add Band 22/XXII for LTE/UMTS 3500 (FDD) to TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 10.3.0      |  |
+| 2011-12        | RP-54   | RP-111734 | 018  | 1   |     | Removal of references to operating bands i) and h)                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 10.4.0      |  |
+| 2011-12        | RP-54   | RP-111735 | 019  | 1   |     | EMC requirements for MSR-NC                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 10.4.0      |  |
+| 2012-03        | RP-55   | RP-120305 | 020  |     |     | Add Extending 850 MHz Upper Band (814 - 849 MHz) to TS37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                | 11.0.0      |  |
+| 2012-06        | RP-56   | RP-120793 | 023  |     |     | Introduction of APAC700(FDD) into TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 11.1.0      |  |
+| 2012-06        | RP-56   | RP-120793 | 024  |     |     | Introduction of APAC700(TDD) into TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 11.1.0      |  |
+| 2012-06        | RP-56   | RP-120791 | 025  |     |     | Introduction of e850_LB (Band 27) to TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 11.1.0      |  |
+| 2013-06        | RP-60   | RP-130792 | 026  |     |     | Introduction of Band 30 in TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 12.0.0      |  |
+| 2013-06        | RP-60   | RP-130790 | 027  |     |     | Introduction of LTE 450 into TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 12.0.0      |  |
+| 2014-06        | RP-64   | RP-140914 | 033  |     |     | Introduction of band 29 in TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 12.1.0      |  |
+| 2014-06        | RP-64   | RP-140926 | 029  |     |     | Introduction of Band 32/XXXII in TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | 12.1.0      |  |
+| 2014-09        | RP-65   | RP-141562 | 0036 | 1   |     | Update of definitions to support supplemental DL in TS37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                | 12.2.0      |  |
+| 2014-12        | RP-66   | RP-142146 | 038  |     |     | EMC testing of multi-band operation for MSR BS                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 12.3.0      |  |
+| 2015-12        | RP-70   | RP-152171 | 0039 |     |     | Introduction of Band 65                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 13.0.0      |  |
+| 2015-12        | RP-70   | RP-152172 | 0040 |     |     | Introduction of Band 66                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 13.0.0      |  |
+| 2015-12        | RP-70   | RP-152157 | 0041 |     |     | Introduction of Band 67                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | 13.0.0      |  |
+| 2015-12        | RP-70   | RP-152173 | 0042 |     |     | Introduction of 1447-1467MHz Band into 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 13.0.0      |  |
+| 2016-03        | RP-71   | RP-160483 | 0043 |     | B   | Introduction of Band 68 into 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 13.1.0      |  |
+| 2016-03        | RP-71   | RP-160490 | 0044 |     | F   | Introduction of Band 46 in TS 37.113                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 13.1.0      |  |
+
+|         |         |           |      |   |   |                                                                                                                                        |        |
+|---------|---------|-----------|------|---|---|----------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 2016-06 | RP-72   | RP-161142 | 0047 | - | F | Clarification in EMC environmental conditions references                                                                               | 13.2.0 |
+| 2016-06 | RP-72   | RP-161141 | 0052 | - | F | Necessary updates in 37.113 on receiver exclusion bands                                                                                | 13.2.0 |
+| 2016-06 | RP-72   | RP-161125 | 0045 | - | B | Introduction of Band 70 to 37.113                                                                                                      | 14.0.0 |
+| 2016-06 | RP-72   | RP-161124 | 0048 | - | B | CR to 37.113 on receiver exclusion band update due to Band 69                                                                          | 14.0.0 |
+| 2016-12 | RP-74   | RP-162379 | 0054 | - | A | CR to TS 37.113 – Introduction of NB-IoT                                                                                               | 14.1.0 |
+| 2016-12 | RP-74   | RP-162405 | 0055 | - | B | Introduction of Band 48                                                                                                                | 14.1.0 |
+| 2017-06 | RP-76   | RP-171285 | 0068 | - | A | CR on eLAA BS for TS 37.113                                                                                                            | 14.2.0 |
+| 2017-09 | RP-77   | RP-171948 | 0070 | - | B | Introduction of the FDD L-band (Band 74) into TS 37.113                                                                                | 15.0.0 |
+| 2017-09 | RP-77   | RP-171952 | 0071 | - | B | CR to 37.113: Introduction of Band 71                                                                                                  | 15.0.0 |
+| 2017-09 | RP-77   | RP-171950 | 0073 | - | B | CR to 37.113: Introduction of B75 and B76                                                                                              | 15.0.0 |
+| 2017-09 | RP-77   | RP-171946 | 0074 | - | B | Introduction of Band 72 into TS37.113                                                                                                  | 15.0.0 |
+| 2017-09 | RP-77   | RP-171949 | 0075 | 1 | B | Introduction of TDD L-band into TS 37.113                                                                                              | 15.0.0 |
+| 2017-12 | RAN#78  | RP-172593 | 0076 | - | B | Introduction of Band 73 into TS 37.113                                                                                                 | 15.1.0 |
+| 2018-03 | RAN#79  | RP-180279 | 0078 | - | B | CR to 37.113: Introduction of Band 85                                                                                                  | 15.2.0 |
+| 2018-03 | RAN#79  | RP-180282 | 0079 | 1 | F | CR to TS 37.113: correction of the CISPR reference and ESD levels                                                                      | 15.2.0 |
+| 2018-03 | RAN#79  | RP-180278 | 0080 | - | B | Introduction of TDD 3.3-3.4GHz band (band 52)                                                                                          | 15.2.0 |
+| 2018-06 | RAN#80  | RP-181075 | 0082 | 1 | B | CR to TS 37.113 (MSR EMC): NR EMC Core Requirements updates                                                                            | 15.3.0 |
+| 2018-09 | RAN#81  | RP-181896 | 0084 | 1 | F | CR to TS 37.113: correction of the exclusion band for BS radiated emission test (8.2.1)                                                | 15.4.0 |
+| 2018-09 | RAN#81  | RP-181896 | 0085 | - | F | CR to TS 37.113: CISPR32 requirements tables correction                                                                                | 15.4.0 |
+| 2018-12 | RAN#82  | RP-182362 | 0088 | 1 | B | Update the title to add NR of TS 37.113                                                                                                | 15.5.0 |
+| 2018-12 | RAN#82  | RP-182361 | 0089 | 1 | F | CR to TS 37.113 (subclause 2 and 8.4.2 )                                                                                               | 15.5.0 |
+| 2018-12 | RAN#82  | RP-182362 | 0092 | - | B | CR to TS 37.113: introduction of the NR to MSR EMC specification                                                                       | 15.5.0 |
+| 2019-06 | RAN#84  | RP-191236 | 0094 | 1 | F | CR to TS 37.113 subclause 4.5                                                                                                          | 15.6.0 |
+| 2019-09 | RAN#85  | RP-192019 | 0095 | 1 | F | CR to TS 37.113 Correction on CISPR 16-1-1 for DC conducted Emission(clause 7.1 and subclause 8.3.2 )                                  | 15.7.0 |
+| 2019-09 | RAN#85  | RP-192019 | 0096 | - | F | CR to TS 37.113 Correction on NR performance criteria(subclause 6.1.5 )                                                                | 15.7.0 |
+| 2019-09 | RAN#85  | RP-192019 | 0097 | - | F | CR to TS 37.113 Correction on surge test level for outdoor telecommunication ports(subclause 9.7.2.1 )                                 | 15.7.0 |
+| 2019-09 | RAN#85  | RP-192019 | 0098 | - | F | CR to TS 37.113 subclause 4.5<br>- Implementation comment: The proposed changes in this CR are already captured in the latest version. | 15.7.0 |
+| 2019-09 | RAN#85  | RP-192046 | 0100 | 1 | F | CR to 37.113 Editorial Corrections                                                                                                     | 15.7.0 |
+| 2019-12 | RAN#86  | RP-193002 | 0105 | - | F | CR to TS 37.113 Correction on definitions subclause 3.1                                                                                | 15.8.0 |
+| 2019-12 | RAN#86  | RP-193002 | 0106 | - | F | CR to TS 37.113 Correction on radiated emission subclause 8.2                                                                          | 15.8.0 |
+| 2019-12 | RAN#86  | RP-193002 | 0107 | - | F | CR to TS 37.113 Correction on transient phenomena performance criteria subclause6.2                                                    | 15.8.0 |
+| 2020-06 | RAN#88  | RP-200984 | 0109 | 1 | F | Draft CR to 37.113 Introducing Reverberation Chamber                                                                                   | 15.9.0 |
+| 2020-06 | RAN#88  | -         | -    | - | - | Update to Rel-16 version (MCC)                                                                                                         | 16.0.0 |
+| 2020-12 | RAN#90  | RP-202489 | 0111 | 1 | A | CR to TS 37.113 on Voltage dips and interruptions, Release 16                                                                          | 16.1.0 |
+| 2021-06 | RAN#92  | RP-211086 | 0113 | - | A | CR to TS 37.113: Radiated emission, ancillary equipment                                                                                | 16.2.0 |
+| 2023-03 | RAN#99  | RP-230502 | 0117 | - | F | CR to TS 37.113 MSR base station test configuration R16                                                                                | 16.3.0 |
+| 2023-03 | RAN#99  | RP-230505 | 0120 | - | A | TS 37.113: Corrections in clause 9 Immunity                                                                                            | 16.3.0 |
+| 2023-06 | RAN#100 | RP-231357 | 0125 | - | A | CR on TS 37.113 MSR base station test configuration R16                                                                                | 16.4.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37114/2a0f333f04f8e672bebf288c511c1db5_img.jpg b/marked/Rel-16/37_series/37114/2a0f333f04f8e672bebf288c511c1db5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..456cb13f1395ec1c467a287a4771baf69b547214
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/2a0f333f04f8e672bebf288c511c1db5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba114720a35de942986dfe9697873799a7cf79329db508f9f0c908ecf3b2f643
+size 24104
diff --git a/marked/Rel-16/37_series/37114/5a24ac755b962fd5f0183f13de0726de_img.jpg b/marked/Rel-16/37_series/37114/5a24ac755b962fd5f0183f13de0726de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c92653b41504b67ecd299aab8cfd9e1b1f8e3d89
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/5a24ac755b962fd5f0183f13de0726de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f302242df2af4df0e403d13e9f22a0d3e4a64b1dc4f37b03b303a127a3224a14
+size 25608
diff --git a/marked/Rel-16/37_series/37114/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37114/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1336537ea24b263d6e72d4c0b08c151e2fd17d38
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d8d2ca43f7a92e6b2e4e5ad7020fd87ab1bd2a0801cc5a15e7402b2fa644ec5
+size 9571
diff --git a/marked/Rel-16/37_series/37114/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37114/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..867dc5f3f69a5cb9bf3ea58b2a74cb8664670150
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fcb20591424549462c9c254dceac1944e768f4b84cac6f6ba07715b3ecc79151
+size 5802
diff --git a/marked/Rel-16/37_series/37114/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/37_series/37114/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26b9418ae88096f9d712dc504d4e6fe2d502b27d
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf18191939c2f1fe0ea5b0721a5fdaa15d3985be7f2b6060c3b40818ae89eecd
+size 30766
diff --git a/marked/Rel-16/37_series/37114/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-16/37_series/37114/d9c0a780cd22626253dab4aa41699e2f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba47abaf9c89c22dd64f8ee31ab5e299396c39fd
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/d9c0a780cd22626253dab4aa41699e2f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:567eaad4c7fac3be7477e03f83f521f7330559ff98d48af25e88ff8e41423053
+size 13658
diff --git a/marked/Rel-16/37_series/37114/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/37_series/37114/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a8465d5979015553dc574aaadfbceb9f93b191a
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4ece28d6c332790daf5856cb5e234eb9155c34aed624a08c335c9c268447f43
+size 15384
diff --git a/marked/Rel-16/37_series/37114/raw.md b/marked/Rel-16/37_series/37114/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5d01895e4d45a81cb75983ee6696bc524b552e8
--- /dev/null
+++ b/marked/Rel-16/37_series/37114/raw.md
@@ -0,0 +1,931 @@
+
+
+# 3GPP TS 37.114 V16.1.0 (2023-03)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis
+
+Valbonne - FRANCE
+
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 223, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                 |           |
+|-----------------------------------------------------------------|-----------|
+| Foreword .....                                                  | 4         |
+| 1 Scope.....                                                    | 6         |
+| 2 References.....                                               | 6         |
+| 3 Definitions, symbols and abbreviations .....                  | 8         |
+| 3.1 Definitions.....                                            | 8         |
+| 3.2 Symbols.....                                                | 10        |
+| 3.3 Abbreviations .....                                         | 10        |
+| 4 Test conditions .....                                         | 11        |
+| 4.1 Exclusion bands.....                                        | 12        |
+| 4.1.1 Transmitter exclusion band .....                          | 12        |
+| 4.1.2 Receiver exclusion band.....                              | 12        |
+| 4.2 Arrangements for establishing a communication link.....     | 13        |
+| 4.3 Narrow band responses on receivers.....                     | 13        |
+| 4.4 BS test configurations .....                                | 13        |
+| 5 Performance assessment .....                                  | 17        |
+| 5.1 General .....                                               | 17        |
+| 5.2 Assessment of performance in Downlink .....                 | 17        |
+| 5.3 Assessment of performance in Uplink .....                   | 18        |
+| 6 Performance criteria.....                                     | 18        |
+| 7 Applicability overview.....                                   | 19        |
+| 7.1 Emission.....                                               | 19        |
+| 7.2 Immunity .....                                              | 19        |
+| 8 Emission.....                                                 | 19        |
+| 8.1 Test configurations.....                                    | 19        |
+| 8.2 Radiated emission from base station.....                    | 20        |
+| 8.2.1 Radiated emission, hybrid AAS BS .....                    | 20        |
+| 8.2.2 Radiated emission, OTA AAS BS.....                        | 20        |
+| 8.3 Conducted emissions, DC power input/output port .....       | 21        |
+| 8.4 Conducted emissions, AC mains power input/output port.....  | 21        |
+| 8.5 Harmonic current emissions (AC mains input port) .....      | 21        |
+| 8.6 Voltage fluctuations and flicker (AC mains input port)..... | 21        |
+| 8.7 Conducted emissions, telecommunication ports .....          | 21        |
+| 9 Immunity .....                                                | 22        |
+| 9.1 Test configurations.....                                    | 22        |
+| 9.2 RF electromagnetic field (80 MHz - 6000 MHz).....           | 23        |
+| 9.2.1 RF electromagnetic field, hybrid AAS BS .....             | 23        |
+| 9.2.2 RF electromagnetic field, OTA AAS BS .....                | 23        |
+| 9.3 Electrostatic discharge.....                                | 24        |
+| 9.4 Fast transients common mode.....                            | 24        |
+| 9.5 RF common mode (0.15 MHz - 80 MHz).....                     | 25        |
+| 9.6 Voltage dips and interruptions .....                        | 25        |
+| 9.7 Surges, common and differential mode.....                   | 25        |
+| <b>Annex A (informative): Change history.....</b>               | <b>26</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document covers the assessment of UTRA TDD, UTRA FDD, E-UTRA, NR and Multi-Standard Radio (MSR) Active Antenna Systems Base Stations in respect of Electromagnetic Compatibility (EMC).
+
+NOTE 1: Whenever the AAS BS in *single RAT UTRA operation*, or AAS BS in *MSR operation* using UTRA is referred in this specification, UTRA TDD and UTRA FDD shall be considered, unless otherwise stated.
+
+NOTE 2: For NR, scope of this specification is limited to *BS type 1-H* and *BS type 1-O*. For EMC requirements of the MSR BS for *BS type 1-C*, refer to TS 37.113 [4].
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- Active Antenna System Base Station for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3],
+- Active Antenna System Base Station for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10].
+
+Technical requirements related to the TAB connector are not included in the present document. These are found in the relevant product standards [2, 3, 10].
+
+The present document does not cover ancillary equipment requirements, where ancillary equipment is not incorporated in the radio equipment and can be assessed on a stand-alone basis, as declared by the manufacturer. Ancillary equipment EMC requirements are still applicable to the AAS BS and are covered by other EMC specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30].
+
+The present document does not specify test conditions, performance assessment and performance criteria for the Narrow-Band Internet of Things (NB-IoT) in band, NB-IoT guard band, or standalone NB-IoT operation, for AAS BS in *single RAT E-UTRA operation* as defined in TS 36.113 [6], or for AAS BS in *MSR operation* using E-UTRA as defined in TS 37.113 [4].
+
+The present document does not specify test conditions, performance assessment and performance criteria for Band 46 operation as it is not supported by AAS BS.
+
+The scope of the present document is twofold:
+
+- Requirement, procedures and values of a *hybrid AAS BS* with *TAB connectors* for every transceiver unit at the *transceiver array boundary* (TAB), subject to conducted requirements,
+
+NOTE 3: *hybrid AAS BS* in the single RAT NR operation is equivalent to *BS type 1-H* defined in NR BS specification TS 38.104 [31].
+
+- Requirements, procedures and values of an OTA AAS BS without *TAB connectors* and relying in the radiated interface, subject to radiated requirements.
+
+NOTE 4: OTA AAS BS in the single RAT NR operation is equivalent to *BS type 1-O* defined in NR BS specification TS 38.104 [31].
+
+The electromagnetic environment classification used in the present document refers to the residential, commercial and light industrial environment classification used in IEC 61000-6-1 [7] and IEC 61000-6-3 [8].
+
+The EMC requirements have been selected to ensure an adequate level of compatibility for apparatus at residential, commercial and light industrial environments. The levels, however, do not cover extreme cases which may occur in any location but with low probability of occurrence.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception".
+- [3] 3GPP TS 37.145-1: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 1: Conducted conformance testing".
+- [4] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [5] 3GPP TS 25.113: "Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [6] 3GPP TS 36.113: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)".
+- [7] IEC 61000-6-1: 2016: "Electromagnetic compatibility (EMC) - Part 6-1: Generic standards - Immunity standard for residential, commercial and light-industrial environments".
+- [8] IEC 61000-6-3: 2006/AMD1:2010: "Electromagnetic compatibility (EMC) - Part 6-3: Generic standards - Emission standard for residential, commercial and light-industrial environments".
+- [9] Void.
+- [10] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: radiated conformance testing".
+- [11] IEC 61000-3-2: 2014: "Electromagnetic compatibility (EMC) - Part 3-2: Limits - Limits for harmonic current emissions (equipment input current  $\leq 16$  A per phase)".
+- [12] IEC 61000-3-3: 2013: "Electromagnetic compatibility (EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems, for equipment with rated current  $\leq 16$  A per phase and not subject to conditional connection".
+- [13] IEC 61000-3-11: 2017 "Electromagnetic compatibility (EMC) - Part 3-11: Limits - Limitation of voltage changes, voltage fluctuations and flicker in public low-voltage supply systems - Equipment with rated current  $\leq 75$  A and subject to conditional connection".
+- [14] IEC 61000-3-12: 2011: "Electromagnetic compatibility (EMC) - Part 3-12: Limits - Limits for harmonic currents produced by equipment connected to public low-voltage systems with input current  $>16$  A and  $\leq 75$  A per phase".
+- [15] IEC 61000-4-2: 2008: "Electromagnetic compatibility (EMC) - Part 4-2: Testing and measurement techniques - Electrostatic discharge immunity test".
+- [16] IEC 61000-4-3: 2006+AMD1:2007+AMD2:2010: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test".
+- [17] IEC 61000-4-4: 2012: "Electromagnetic compatibility (EMC) – Part 4-4: Testing and measurement techniques – Electrical fast transient/burst immunity test".
+- [18] IEC 61000-4-5: 2014+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-5: Testing and measurement techniques - Surge immunity test".
+- [19] IEC 61000-4-6: 2013: "Electromagnetic compatibility (EMC) - Part 4-6: Testing and measurement techniques - Immunity to conducted disturbances, induced by radio-frequency fields".
+
+- [20] IEC 61000-4-11: 2004+AMD1:2017: "Electromagnetic compatibility (EMC) - Part 4-11: Testing and measurement techniques - Voltage dips, short interruptions and voltage variations immunity tests".
+- [21] ETSI EN 301 489-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 1: Common technical requirements".
+- [22] Void
+- [23] Void
+- [24] ITU-R SM.329-10: "Unwanted emissions in the spurious domain".
+- [25] ETSI EN 301 489-50, v2.1.0: "ElectroMagnetic Compatibility (EMC) standard for radio equipment and services; Part 50: Specific conditions for Cellular Communication Base Station (BS), repeater and ancillary equipment; Harmonised Standard covering the essential requirements of article 3.1(b) of Directive 2014/53/EU".
+- [26] 3GPP TS 25.102: "User Equipment (UE) radio transmission and reception (TDD)".
+- [27] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [28] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [29] CISPR 32: "Electromagnetic compatibility of multimedia equipment - Emission requirements".
+- [30] 3GPP TS 38.113: "NR; Base Station (BS) ElectroMagnetic Compatibility (EMC)".
+- [31] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".
+- [32] Void
+- [33] 3GPP TS 37.104: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) radio transmission and reception".
+- [34] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception; Part 4: Performance requirements".
+- [35] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 37.113 [4] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TS 37.113 [4].
+
+NOTE: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are printed in their entirety.
+
+**active antenna system base station:** BS system which combines an *antenna array* with a transceiver unit array and a *radio distribution network*.
+
+**antenna array:** group of radiating elements characterized by the geometry and the properties of the *array elements*.
+
+**antenna port:** RF interface at the *transceiver array boundary*, specifically the *TAB connectors*.
+
+**BS type 1-H:** NR base station operating at FR1 with a requirement set consisting of conducted requirements defined at individual *TAB connectors* and OTA requirements defined at RIB.
+
+**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB.
+
+**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set*.
+
+**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)* (including any of UTRA, E-UTRA and/or NR operation as single RAT or multi-RAT based on TS 37.104 [33]).
+
+**NB-IoT In-band operation:** NB-IoT is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier.
+
+**NB-IoT guard band operation:** NB-IoT is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band.
+
+**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+**OTA AAS BS:** AAS BS which has  $\geq 8$  *transceiver units* for E-UTRA or MSR and  $\geq 4$  *transceiver units* for UTRA per cell and has a radiated RF interface only and conforms to the *OTA requirements set*.
+
+**OTA requirements set:** complete set of OTA requirements applied to an OTA AAS BS.
+
+**port:** particular interface of EUT used for EMC requirements testing purposes.
+
+NOTE: Any connection point on EUT intended for connection of cables to or from EUT during the EMC testing is considered as a port.
+
+EXAMPLE 1: Examples of ports for *hybrid AAS BS* are as presented in figure 3.1-1:
+
+![Diagram of a hybrid AAS BS showing various ports.](5a24ac755b962fd5f0183f13de0726de_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" enclosed within a larger rectangular frame labeled "Enclosure Port" at the top. On the left side of the "Apparatus" box, three horizontal lines extend to the left, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". On the right side of the "Apparatus" box, three horizontal lines extend to the right, labeled from top to bottom: "Antenna port", "Signal/control port", and "Telecommunication port".
+
+Diagram of a hybrid AAS BS showing various ports.
+
+**Figure 3.1-1: Examples of ports for *hybrid AAS BS***
+
+EXAMPLE 2: Examples of ports for OTA AAS BS (i.e. with no antenna ports) are as presented in figure 3.1-2:
+
+![Diagram of an OTA AAS BS showing various ports, with no antenna port.](2a0f333f04f8e672bebf288c511c1db5_img.jpg)
+
+The diagram shows a central rectangular box labeled "Apparatus" enclosed within a larger rectangular frame labeled "Enclosure Port" at the top. On the left side of the "Apparatus" box, three horizontal lines extend to the left, labeled from top to bottom: "AC power port", "DC power port", and "Earth port". On the right side of the "Apparatus" box, two horizontal lines extend to the right, labeled from top to bottom: "Signal/control port" and "Telecommunication port". The "Antenna port" shown in Figure 3.1-1 is absent.
+
+Diagram of an OTA AAS BS showing various ports, with no antenna port.
+
+**Figure 3.1-2: Examples of ports for OTA AAS BS**
+
+**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply.
+
+**radio distribution network:** linear passive network which distributes the RF power generated by the transceiver unit array to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the transceiver unit array.
+
+NOTE: In the case when the active transceiver units are physically integrated with the *array elements* of the *antenna array*, the *radio distribution network* is a one-to-one mapping.
+
+**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the operating band.
+
+NOTE: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation.
+
+**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the operating band.
+
+**spatial exclusion zone:** range of angles where no tests of radiated immunity are made for *OTA AAS BS* (i.e. half sphere around the EUT's radiating direction).
+
+**TAB connector:** *transceiver array boundary* connector.
+
+**transceiver array boundary:** conducted interface between the transceiver unit array and the composite antenna.
+
+**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters.
+
+**telecommunication port:** ports which are intended to be connected to telecommunication networks (e.g. public switched telecommunication networks, integrated services digital networks), local area networks (e.g. Ethernet, Token Ring) and similar networks.
+
+NOTE: ETSI EN 301 489-1 [21] calls *telecommunication port* as the "wired network port".
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                                |                                                                                                                                                   |
+|--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+| $BW_{\text{Channel}}$          | Channel bandwidth                                                                                                                                 |
+| $f_{\text{offset}}$            | Frequency offset used for discovering narrowband response for receivers                                                                           |
+| $F_{\text{UL\_high}}$          | The highest frequency of the uplink operating band                                                                                                |
+| $F_{\text{UL\_low}}$           | The lowest frequency of the uplink operating band                                                                                                 |
+| $\Delta f_{\text{OoB}}$        | Maximum offset of the out-of-band boundary from the uplink operating band edge                                                                    |
+| $\Delta f_{\text{Rexclusion}}$ | Maximum offset of the Radiated Immunity exclusion band from the uplink operating band edge for test without <i>spatial exclusion zone</i> applied |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply.
+
+An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|        |                                                 |
+|--------|-------------------------------------------------|
+| AAS    | Active Antenna System                           |
+| AAS BS | AAS Base Station                                |
+| CSA    | Capability Set supported by the AAS BS          |
+| EMC    | ElectroMagnetic Compatibility                   |
+| EUT    | Equipment Under Test                            |
+| FR1    | Frequency Range 1                               |
+| MSR    | Multi-Standard Radio                            |
+| NB-IoT | Narrowband – Internet of Things                 |
+| NR     | New Radio                                       |
+| RCSA   | Radiated Capability Set supported by the AAS BS |
+| RDN    | Radio Distribution Network                      |
+| RF     | Radio Frequency                                 |
+
+|     |                             |
+|-----|-----------------------------|
+| RIB | Radiated Interface Boundary |
+| TAB | Transceiver Array Boundary  |
+
+# 4 Test conditions
+
+The equipment shall be tested in normal test environment defined in base station conformance testing specification TS 37.145-1 [3], or TS 37.145-2 [10]. The test conditions shall be recorded in the test report.
+
+For an AAS BS supporting more than one RAT, tests shall be performed with RATs activated according to the test configurations in subclause 4.4. Tests shall be performed relating to each type of port and RIB, and need not be repeated for each RAT if operating RATs are assessed simultaneously during the test.
+
+For AAS BS supporting only single RAT operation only, tests relating to the *antenna port(s)* and RIBs shall be performed for each supported RAT.
+
+For AAS BS capable of multi-band operation, the requirements in the present document apply for each supported operating band unless otherwise stated. Operating bands and RATs shall be activated according to the respective test configurations in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4], or TS 38.113 [30]. Tests shall be performed relating to each type of port and RIB, and all RATs per band shall be assessed during the tests.
+
+Requirements apply only for the declared operating band and corresponding Band Categories as per CSA and/or RCSA capability sets and manufacturer's declarations of the AAS BS in TS 37.145-1 [3] and TS 37.145-2 [10].
+
+The manufacturer shall declare the supported capability set(s) according to TS 37.145-1 [3] and TS 37.145-2 [10]. Tests performed on an AAS BS according to a declared capability set(s) cover all single RAT and multi-RAT configurations included in the declared capability set.
+
+NOTE 1: *TAB connector* capability sets (CSA) for *hybrid AAS BS* are defined in TS 37.145-1 [3] and declared in D6.12 declaration.
+
+NOTE 2: Radiated capability sets (RCSA) for *hybrid AAS BS* and OTA AAS BS are defined in TS 37.145-2 [10] and declared by D9.25 declaration.
+
+Where the *hybrid AAS BS* has multiple *TAB connectors* which are declared to be equivalent then it is sufficient to perform EMC tests on a single representative *TAB connector*. For the definition of the *TAB connector* equivalence declaration (D6.70), refer to TS 37.145-1 [3].
+
+EMC test shall not be performed with the AAS BS *antenna array* radiating, all *TAB connectors* shall be disconnected from the *radio distribution network* (RDN)/antenna array as specified in TS 37.105 [2] and terminated in an appropriate load impedance. For the description of the general AAS BS radio architecture and relations between the RDN/*antenna array* and the Transceiver Array Boundary, refer to TS 37.105 [2].
+
+Depending on RAT capability sets supported by the AAS BS, the following test conditions shall be referred and applied for the BS test configurations:
+
+- For AAS BS in *single RAT UTRA operation* the test conditions from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation* the test conditions from TS 36.113 [6] apply.
+- For AAS BS in single RAT NR operation the test conditions from TS 38.113 [30] apply.
+- For AAS BS in *MSR operation* the test conditions from TS 37.113 [4] apply.
+
+Whenever ports are considered for the emissions and immunity testing in the referred TS 25.113 [5], TS 36.113 [6] and TS 37.113 [4] specifications, special considerations shall be taken to test conditions specification for OTA AAS BS due to lack of *antenna ports*.
+
+NOTE 3: The receiver exclusion bands defined in E-UTRA and MSR specifications for Band 46 operation are not applicable for AAS BS, as the Band 46 operation is not supported by AAS BS.
+
+NOTE 4: The NB-IoT operation is not supported by AAS BS.
+
+## 4.1 Exclusion bands
+
+### 4.1.1 Transmitter exclusion band
+
+The *transmitter exclusion band* for BS is the frequency range over which no tests of radiated immunity of a transmitter are made. The *transmitter exclusion band* only applies to OTA AAS BS.
+
+The *transmitter exclusion band* is defined as:
+
+$$F_{DL,low} - \Delta f_{OBUE} < f < F_{DL,high} + \Delta f_{OBUE}$$
+
+Where:
+
+The value of  $\Delta f_{OBUE}$ ,  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* for NR, E-UTRA, UTRA in TS 37.105 [2].
+
+NOTE: For BS capable of multi-band operation, the frequency ranges relating to the RF bandwidths of all supported bands apply.
+
+### 4.1.2 Receiver exclusion band
+
+An exclusion band is a band of frequencies over which no tests of radiated immunity are made.
+
+In case the spatial exclusion (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is used during the EMC RI testing, the receiver exclusion band for OTA AAS BS is defined as:
+
+$$F_{UL,low} - \Delta f_{OOB} < f < F_{UL,high} + \Delta f_{OOB}$$
+
+Where:
+
+- Values of  $F_{UL,low}$  and  $F_{UL,high}$  are defined for each *operating band* in TS 37.104 [33].
+- The values of  $\Delta f_{OOB}$  are defined in table 4.1.2-1.
+
+**Table 4.1.2-1: Maximum  $\Delta f_{OOB}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>                             | $\Delta f_{OOB}$ (MHz) |
+|-------------------------------------------------------------------|------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$                   | 20                     |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low} \leq 900 \text{ MHz}$ | 60                     |
+
+In case the *spatial exclusion zone* (as discussed in subclause 9.2.2 and depicted in figure 9.2.2-1) is not used during the EMC RI testing, the receiver exclusion band for OTA AAS BS and *BS type 1-O* is defined as:
+
+$$F_{UL,low} - \Delta f_{R exclusion} < f < F_{UL,high} + \Delta f_{R exclusion}$$
+
+Where the values of  $\Delta f_{R exclusion}$  are defined in table 4.1.2-2.
+
+**Table 4.1.2-2: Maximum  $\Delta f_{R exclusion}$  offset outside the uplink operating band**
+
+| <i>Operating band characteristics</i>           | $\Delta f_{R exclusion}$ (MHz) |
+|-------------------------------------------------|--------------------------------|
+| $100 \text{ MHz} \geq F_{UL,high} - F_{UL,low}$ | 60                             |
+| $100 \text{ MHz} < F_{UL,high} - F_{UL,low}$    | 200                            |
+
+For BS capable of multi-band operation, the total receiver exclusion band shall be the combination of the exclusion bands for each operating band supported by AAS BS.
+
+NOTE 1: The receiver exclusion bands do not apply for SDL bands.
+
+NOTE 2: Void
+
+## 4.2 Arrangements for establishing a communication link
+
+Depending on RAT capability sets supported by the AAS BS, the following arrangements for establishing a communication link shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the arrangements for establishing a communication link from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the arrangements for establishing a communication link from TS 36.113 [6] apply.
+- For AAS BS in MSR operation, the arrangements for establishing a communication link from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for establishing a communication link from TS 38.113 [30] apply.
+
+## 4.3 Narrow band responses on receivers
+
+Depending on RAT capability sets supported by the AAS BS, the following narrow band responses on receivers shall be referred and applied:
+
+- For AAS BS in single RAT UTRA operation, the narrow band responses on receivers from TS 25.113 [5] apply.
+- For AAS BS in single RAT E-UTRA operation, the narrow band responses on receivers from TS 36.113 [6] apply.
+- For AAS BS in MSR operation the arrangements for narrow band responses on receivers from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the arrangements for narrow band responses on receivers from TS 38.113 [30] apply.
+
+## 4.4 BS test configurations
+
+The present document specifies the applicable test conditions, performance assessment and performance criteria for base stations in the following categories:
+
+- AAS BS for UTRA TDD, UTRA FDD, E-UTRA, NR and MSR meeting the conducted requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-1 [3]. In this case, the EMC test configuration are listed in tables 4.4-1, 4.4-3, 4.4-5, 4.4-7, 4.4-9, 4.4-11 respectively.
+- AAS BS for UTRA FDD, E-UTRA, NR and MSR meeting the OTA requirements of TS 37.105 [2], with conformance demonstrated by compliance to TS 37.145-2 [10]. In this case, the EMC test configuration are listed in table 4.4-2, 4.4-4, 4.4-6, 4.4-8, 4.4-10, 4.4-12 respectively.
+
+The test configurations apply according to the declared RAT capability sets (i.e. CSA or RCSA) of the AAS BS according to subclause 4.9 of TS 37.145-1 [3] and TS 37.145-2 [10] and the Band Category of the declared operating band (i.e. BC1, BC2 or BC3).
+
+The AAS BS test configurations are defined as ATCx in TS 37.145-1 [3] and ATCRx in TS 37.145-2[10], subclause 4.11.
+
+- For AAS BS declared to be capable of contiguous operation only, the test configuration(s) in tables 4.4-1, 4.4-2 and 4.4-3, 4.4-4 denoted by a "C" shall be used for testing.
+- For AAS BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacture's declaration according to subclause 4.10 of TS 37.145-1 [3] and TS 37.145-2 [10] are identical for contiguous and non-contiguous operation, the test configurations denoted by "CNC" shall be used.
+- For AAS BS declared to be capable of contiguous and non-contiguous operation and where the parameters in the manufacture's declaration according to subclause 4.10 of TS 37.145-1 [3] and TS 37.145-2 [10] are not identical
+
+for contiguous and non-contiguous operation, the test configurations denoted by "C/NC" shall be used for testing.
+
+For immunity tests:
+
+- The communication link for the RAT(s) listed in the table shall be established according to subclause 4.2.
+- Tests for ports relating to the RAT(s) supported shall be performed according to subclause 4.1.
+
+**Table 4.4-1: Test configuration applicability to requirements and capability sets for TAB connectors supporting MSR operation**
+
+| TAB connector test case | UTRA + E-UTRA (CSA3)                       |                                            |          | E-UTRA + NR (CSA3A)                      |                                          |                                          | UTRA + E-UTRA + NR (CSA3B)               |
+|-------------------------|--------------------------------------------|--------------------------------------------|----------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|
+|                         | BC1                                        | BC2                                        | BC3      | BC1                                      | BC2                                      | BC3                                      | BC1,BC2                                  |
+| Emission tests          | C: ATC3a<br>CNC: ANT3<br>C/NC: ATC3a, ANT3 | C: ATC3a<br>CNC: ANT3<br>C/NC: ATC3a, ANT3 | C: ATC3b | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC8<br>CNC: ANT8<br>C/NC: ANT8, ATC8 |
+| Immunity tests          | C: ATC3a<br>CNC: ANT3<br>C/NC: ATC3a, ANT3 | C: ATC3a<br>CNC: ANT3<br>C/NC: ATC3a, ANT3 | C: ATC3b | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC6<br>CNC: ANT6<br>C/NC: ATC6, ANT6 | C: ATC8<br>CNC: ANT8<br>C/NC: ANT8, ATC8 |
+
+**Table 4.4-2: Test configuration applicability to requirements and capability sets for AAS BS supporting MSR operation**
+
+| Test case      | UTRA + E-UTRA (RCSA 3)                       |                                              |     | E-UTRA + NR (RCSA 3A)                      |                                            |                                            | UTRA + E-UTRA + NR (RCSA 3B)               |
+|----------------|----------------------------------------------|----------------------------------------------|-----|--------------------------------------------|--------------------------------------------|--------------------------------------------|--------------------------------------------|
+|                | BC1                                          | BC2                                          | BC3 | BC1                                        | BC2                                        | BC3                                        | BC1,BC2                                    |
+| Emission tests | C: ATCR3a<br>CNC: ANT3<br>C/NC: ATCR3a, ANT3 | C: ATCR3a<br>CNC: ANT3<br>C/NC: ATCR3a, ANT3 | N/A | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR9<br>CNC: ANT9<br>C/NC: ATCR9, ANT9 |
+| Immunity tests | C: ATCR3a<br>CNC: ANT3<br>C/NC: ATCR3a, ANT3 | C: ATCR3a<br>CNC: ANT3<br>C/NC: ATCR3a, ANT3 | N/A | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR7<br>CNC: ANT7<br>C/NC: ATCR7, ANT7 | C: ATCR9<br>CNC: ANT9<br>C/NC: ATCR9, ANT9 |
+
+**Table 4.4-3: Test configuration applicability to requirements and capability sets for TAB connectors supporting one RAT only MSR operation**
+
+| Capability set          | UTRA (MC) capable BS (CSA1)                       |                                                   |          | E-UTRA (MC) capable BS (CSA2)                |                                              |                                                 |
+|-------------------------|---------------------------------------------------|---------------------------------------------------|----------|----------------------------------------------|----------------------------------------------|-------------------------------------------------|
+| TAB connector test case | BC1                                               | BC2                                               | BC3      | BC1                                          | BC2                                          | BC3                                             |
+| Emission tests          | C: ATC1a<br>CNC: ANTC1a<br>C/NC: ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2    |
+| Immunity tests          | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1a CNC:<br>ANTC1a C/NC:<br>ATC1a,<br>ANTC1a | C: ATC1b | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a CNC:<br>ANTC2 C/NC:<br>ATC2a, ANTC2 | C: ATC2a<br>CNC: ANTC2<br>C/NC: ATC2a,<br>ANTC2 |
+
+**Table 4.4-4: Test configuration applicability to requirements and capability sets for operating bands supporting one RAT only MSR operation**
+
+| Capability set | UTRA (MC) capable BS (RCSA1)                                |                                                             |     | E-UTRA (MC) capable BS (RCSA2)                         |                                                        |                                                        |
+|----------------|-------------------------------------------------------------|-------------------------------------------------------------|-----|--------------------------------------------------------|--------------------------------------------------------|--------------------------------------------------------|
+| Test case      | BC1                                                         | BC2                                                         | BC3 | BC1                                                    | BC2                                                    | BC3                                                    |
+| Emission tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+| Immunity tests | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | C: ATCR1a<br>CNC:<br>ANTCR1a<br>C/NC:<br>ATCR1a,<br>ANTCR1a | N/A | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 | C: ATCR2a<br>CNC: ANTCR2<br>C/NC:<br>ATCR2a,<br>ANTCR2 |
+
+**Table 4.4-5: Test configurations for a TAB connector supporting single-RAT UTRA operation**
+
+| TAB connector test case | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C capable only | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable TAB connector (CSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC capable TAB connector (CSA4) C capable only |
+|-------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+| Emission tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+| Immunity tests          | ATC1a                                                              | ANTC1                                                                                          | ATC1a, ANTC1                                                                                   | ATC1b                                                              |
+
+**Table 4.4-6: Test configurations for an AAS BS supporting single-RAT UTRA operation**
+
+| Test case      | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C capable only | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with identical parameters | Single-RAT UTRA FDD MC capable AAS BS operating band (RCSA4) C and NC capable with different parameters | Single-RAT UTRA TDD MC AAS BS operating band (RCSA4) C capable only |
+|----------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
+| Emission tests | ATC1a                                                                       | ANTC1                                                                                                   | ATC1a, ANTC1                                                                                            | N/A                                                                 |
+| Immunity tests | ATCR1a                                                                      | ANTCR1                                                                                                  | ATCR1a, ANTCR1                                                                                          | N/A                                                                 |
+
+**Table 4.4-7: Test configurations for a *TAB connector* supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| <i>TAB connector</i> test case | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C capable only | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with identical parameters (CNC) | Single-RAT E-UTRA MC capable <i>TAB connector</i> (CSA5)<br>C and NC capable BS with different parameters (CNC) |
+|--------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
+| Emission tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+| Immunity tests                 | ATC2a                                                                      | ANTC2                                                                                                           | ATC2a, ANTC2                                                                                                    |
+
+**Table 4.4-8: Test configurations for an AAS BS supporting single-RAT E-UTRA operation capable of both contiguous and non-contiguous spectrum in multi-carrier and/or CA operation in single band**
+
+| Test case      | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C capable only | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with identical parameters | Single-RAT E-UTRA MC capable AAS BS operating band (RCSA5)<br>C and NC capable BS with different parameters |
+|----------------|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|
+| Emission tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+| Immunity tests | ATCR2a                                                                       | ANTCR2                                                                                                      | ATCR2a, ANTCR2                                                                                              |
+
+**Table 4.4-9: Test configuration for *multi-band TAB connectors* supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |       |
+|--------------------------------|----------------------------|-------|
+|                                | BC1/BC2                    | BC3   |
+| Emission tests                 | ATC5b                      | ATC5b |
+| Immunity tests                 | ATC5b                      | ATC5b |
+
+**Table 4.4-10: Test configuration for AAS BS operating bands containing beams with multi-band dependencies supporting MSR operation**
+
+| <i>TAB connector</i> test case | Test configuration for MBT |        |
+|--------------------------------|----------------------------|--------|
+|                                | BC1/BC2                    | BC3    |
+| Emission tests                 | ATCR5b                     | ATCR5b |
+| Immunity tests                 | ATCR5b                     | ATCR5b |
+
+**Table 4.4-11: Test configuration for *multi-band TAB connectors* supporting Single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                 | UTRA TDD CSA4         | E-UTRA Test CSA5               |
+|--------------------------------|-------------------------------|-----------------------|--------------------------------|
+| Emission test                  | ATC1a/ANTC1 (note 1)<br>ATC5b | ATC1b (note 2), ATC5a | ATC2a/ANTC2 (note 3),<br>ATC5b |
+| Immunity test                  | ATC5b                         | ATC5a                 | ATC5b                          |
+
+NOTE 1: ATC1a and/or ANTC1 shall be applied in each supported operating band according to table 4.4-3a.
+
+NOTE 2: ATC1b shall be applied in each supported operating band according to table 4.4-3a.
+
+NOTE 3: ATC2 and/or ANTC2 shall be applied in each supported operating band according to table 4.4-4a.
+
+**Table 4.4-12: Test configuration for AAS BS operating bands with multi-band dependencies supporting single-RAT only**
+
+| <i>TAB connector</i> test case | UTRA FDD CSA4                    | UTRA TDD CSA4 | E-UTRA Test CSA5                  |
+|--------------------------------|----------------------------------|---------------|-----------------------------------|
+| Emission test                  | ATCR1a/ANTCR1 (note 1)<br>ATCR5b | N/A           | ATCR2a/ANTCR2 (note 2),<br>ATCR5b |
+| Immunity test                  | ATCR5b                           | N/A           | ATCR5b                            |
+
+NOTE 1: ATCR1a and/or ANTCR1 shall be applied in each supported operating band according to table 4.4-3b.
+
+NOTE 2: ATCR2 and/or ANTCR2 shall be applied in each supported operating band according to table 4.4-4b.
+
+# 5 Performance assessment
+
+## 5.1 General
+
+The following information shall be recorded in or annexed to the test report:
+
+- the primary functions of the radio equipment to be tested during and after the EMC testing;
+- the intended functions of the radio equipment which shall be in accordance with the documentation accompanying the equipment;
+- the method to be used to verify that a communications link is established and maintained;
+- the user-control functions and stored data that are required for normal operation and the method to be used to assess whether these have been lost after EMC stress;
+- the ancillary equipment to be combined with the radio equipment for testing (where applicable);
+- the information about ancillary equipment intended to be used with the radio equipment;
+- information about the common and/or RAT-specific active RF components and other HW blocks for a communication link in AAS BS supporting more than one RAT;
+- information about the common and/or band-specific active RF components and other HW blocks for a communication link in AAS BS capable of multi-band operation;
+- an exhaustive list of ports (and RIBs), classified as either power or signal/control. Power ports shall further be classified as AC or DC power.
+
+A communication link used by more than one RAT or more than one operating band, shall be assessed on all RATs and operating bands. Communication link(s) and/or radio performance parameters for the RATs and operating bands can during the test be assessed simultaneously or separately for each RAT and band, depending on the test environment capability.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance assessment the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+## 5.2 Assessment of performance in Downlink
+
+In the immunity tests, the output of the transmitter shall be connected (via port for hybrid AAS BS, or via RIB for OTA AAS BS) to test equipment which meets the requirements for the performance assessment of RAT and bearer used in the immunity tests according to the following:
+
+- BLER assessment in TS 25.102 [26] in case of UTRA TDD
+- BLER assessment in TS 25.101 [27] in case of UTRA FDD
+- Throughput assessment in TS 36.101 [28] in case of E-UTRA
+- Throughput assessment in TS 38.101-4 [34] in case of NR
+
+The level of the signal supplied to the equipment should be within the range for which the assessment of throughput is not impaired. Power control shall be OFF during the immunity testing.
+
+## 5.3 Assessment of performance in Uplink
+
+In the immunity tests, the performance in the uplink shall be monitored at a telecommunications port(s) by using suitable test equipment according to the following:
+
+- The value of the throughput shall be monitored in case of E-UTRA or in case of NR
+- The value of the BLER shall be monitored in case of UTRA FDD or in case of UTRA TDD
+
+# --- 6 Performance criteria
+
+The test should, where possible, be performed using a bearer with the characteristics of data rate and performance criteria defined for UTRA TDD, UTRA FDD, E-UTRA, or NR. If the test is not performed using one of these bearers (for example, if none of them are supported by the BS) the characteristics of the bearer used shall be recorded in the test report.
+
+Depending on RAT capability sets supported by the AAS BS, the following performance criteria for continuous or for transient phenomena shall be referred and applied:
+
+- For AAS BS in *single RAT UTRA operation*, the performance criteria from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the performance criteria from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the performance criteria from TS 37.113 [4] apply.
+- For AAS BS in single RAT NR operation, the performance criteria from TS 38.113 [30] apply.
+
+NOTE 1: The present document does not cover ancillary equipment requirements. However, the ancillary equipment EMC requirements are still applicable to the AAS BS and for the ancillary equipment performance criteria the appropriate non-AAS specifications in TS 25.113 [5], TS 36.113 [6], TS 37.113 [4] or TS 38.113 [30] shall be referred.
+
+NOTE 2: The NB-IoT operation is not supported by AAS BS.
+
+# 7 Applicability overview
+
+## 7.1 Emission
+
+Table 7.1-1: Emission requirements applicability
+
+| Phenomenon                       | Application                | Equipment test requirement                 | Reference subclause in the present document | Reference standard                              |
+|----------------------------------|----------------------------|--------------------------------------------|---------------------------------------------|-------------------------------------------------|
+|                                  |                            | BS equipment                               |                                             |                                                 |
+| Radiated emission                | Enclosure                  | applicable for <i>hybrid AAS BS</i> (Note) | 8.2.1                                       | ITU-R SM.329 [24]                               |
+| Conducted emission               | DC power input/output port | applicable                                 | 8.3                                         | CISPR 32 [29]                                   |
+| Conducted emission               | AC mains input/output port | applicable                                 | 8.4                                         | CISPR 32 [29]                                   |
+| Conducted emission               | Telecommunication port     | applicable                                 | 8.5                                         | CISPR 32 [29]                                   |
+| Harmonic current emissions       | AC mains input port        | applicable                                 | 8.6                                         | IEC 61000-3-2 [11]<br>or<br>IEC 61000-3-12 [14] |
+| Voltage fluctuations and flicker | AC mains input port        | applicable                                 | 8.7                                         | IEC 61000-3-3 [12]<br>or<br>IEC 61000-3-11 [13] |
+
+NOTE: The EMC radiated emissions requirements for the OTA AAS BS are covered by the RF radiated emissions requirement in TS 37.105 [2], conforming to the TS 37.145-2 [10].
+
+## 7.2 Immunity
+
+Table 7.2-1: Immunity requirements applicability
+
+| Phenomenon                               | Application                                                               | Equipment test requirement | Reference subclause in the present document | Reference standard  |
+|------------------------------------------|---------------------------------------------------------------------------|----------------------------|---------------------------------------------|---------------------|
+|                                          |                                                                           | BS equipment               |                                             |                     |
+| RF electromagnetic field (80 – 6000 MHz) | Enclosure                                                                 | applicable                 | 9.2                                         | IEC 61000-4-3 [16]  |
+| Electrostatic discharge                  | Enclosure                                                                 | applicable                 | 9.3                                         | IEC 61000-4-2 [15]  |
+| Fast transients common mode              | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.4                                         | IEC 61000-4-4 [17]  |
+| RF common mode 0.15 - 80 MHz             | Signal, telecommunications and control ports, DC and AC power input ports | applicable                 | 9.5                                         | IEC 61000-4-6 [19]  |
+| Voltage dips and interruptions           | AC mains power input ports                                                | applicable                 | 9.6                                         | IEC 61000-4-11 [20] |
+| Surges, common and differential mode     | AC power input ports and telecommunications port                          | applicable                 | 9.7                                         | IEC 61000-4-5 [18]  |
+
+# 8 Emission
+
+## 8.1 Test configurations
+
+This subclause defines the configurations for emission tests as follows:
+
+- The equipment shall be tested under normal test conditions as specified in the functional standards;
+
+- The test configuration shall be as close to normal intended use as possible;
+- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- The test conditions, test configuration and mode of operation shall be recorded in the test report;
+- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS without Radio Frequency (RF) input/output ports but intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup suitable for the radiated power;
+- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- The test arrangements for transmitter and receiver clauses of the transceiver are described separately for the sake of clarity. However, where possible the test of the transmitter clause and receiver clause of the EUT may be carried out simultaneously to reduce test time.
+
+## 8.2 Radiated emission from base station
+
+### 8.2.1 Radiated emission, hybrid AAS BS
+
+This test is applicable to *hybrid AAS BS*. This test shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+Depending on RAT capability sets supported by the *hybrid AAS BS*, the following radiated emission requirements apply:
+
+- For *hybrid AAS BS* in *single RAT UTRA operation*, the base stations radiated emission requirements from TS 25.113 [5] apply.
+- For *hybrid AAS BS* in *single RAT E-UTRA operation* the base stations radiated emission requirements from TS 36.113 [6] apply.
+- For *hybrid AAS BS* in *MSR operation*, the base stations radiated emission requirements from TS 37.113 [4] apply.
+- For *hybrid AAS BS* in *single RAT NR operation*, the *BS type I-H* radiated emission requirements from TS 38.113 [30] apply.
+
+### 8.2.2 Radiated emission, OTA AAS BS
+
+This test is applicable to OTA AAS BS. This test shall be performed on a representative configuration of the OTA AAS BS.
+
+For OTA AAS BS, the radiated emission requirement is covered by RF radiated spurious emission requirement in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10].
+
+- NOTE: As the EMC radiated emissions of the OTA AAS BS cannot be distinguished between the intended emissions (nor to any spurious emissions related to these intentional transmissions) a single radiated emissions requirement is used for the OTA AAS BS.
+
+## 8.3 Conducted emissions, DC power input/output port
+
+This test is applicable to equipment which may have DC cables longer than 3 m.
+
+If the DC power cable of the radio equipment is intended to be less than 3 m in length, and intended only for direct connection to a dedicated AC to DC power supply, then the measurement shall be performed only on the AC power input of that power supply as specified in subclause 8.4.
+
+This test shall be performed on a representative configuration of the radio equipment.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the DC power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the DC power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the DC power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the DC power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.4 Conducted emissions, AC mains power input/output port
+
+This test is applicable to equipment powered by the AC mains.
+
+This test is not applicable to AC output ports which are connected directly (or via a circuit breaker) to the AC power port of the EUT.
+
+This test shall be performed on a representative configuration of the radio equipment.
+
+Depending on RAT capability sets supported by the BS, the following conducted emission requirements apply:
+
+- For AAS BS in *single RAT UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 25.113 [5] apply.
+- For AAS BS in *single RAT E-UTRA operation*, the AC mains power input/output port conducted emissions requirements from TS 36.113 [6] apply.
+- For AAS BS in *MSR operation*, the AC mains power input/output port conducted emissions requirements from TS 37.113 [4] apply.
+- For AAS BS in *single RAT NR operation*, the AC mains power input/output port conducted emissions requirements from TS 38.113 [30] apply.
+
+## 8.5 Harmonic current emissions (AC mains input port)
+
+The requirements of IEC 61000-3-2 [11] for harmonic current emission apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-12 [14] applies.
+
+## 8.6 Voltage fluctuations and flicker (AC mains input port)
+
+The requirements of IEC 61000-3-3 [12] for voltage fluctuations and flicker apply for equipment covered by the scope of the present document. For equipment with an input current of greater than 16 A per phase, IEC 61000-3-11 [13] applies.
+
+## 8.7 Conducted emissions, telecommunication ports
+
+This test is applicable for radio equipment for fixed use which have telecommunication ports.
+
+This test shall be performed on a representative configuration of radio equipment.
+
+The test method and limits shall be in accordance with CISPR 32 [29], as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# --- 9 Immunity
+
+## 9.1 Test configurations
+
+This subclause defines the configurations for immunity tests as follows:
+
+- The equipment shall be tested under normal test conditions as specified in the functional standards;
+- During test, the RF output power may be reduced to a power level sufficient for establishing and maintaining the required communication link;
+- The test configuration shall be as close to normal intended use as possible;
+- If the equipment is part of a system, or can be connected to ancillary equipment, then it shall be acceptable to test the equipment while connected to the minimum configuration of ancillary equipment necessary to exercise the ports;
+- If the equipment has a large number of ports, then a sufficient number shall be selected to simulate actual operation conditions and to ensure that all the different types of termination are tested;
+- The test conditions, test configuration and mode of operation shall be recorded in the test report;
+- Ports which in normal operation are connected shall be connected to an ancillary equipment or to a representative piece of cable correctly terminated to simulate the input/output characteristics of the ancillary equipment. In case of *hybrid AAS BS*, Radio Frequency (RF) input/output ports shall be correctly terminated;
+- For OTA AAS BS intentionally radiating through the *antenna array*, the equipment shall be placed in a test setup capable to reduce the power to a level sufficient for establishing and maintaining the communication link;
+- Ports which are not connected to cables during normal operation, e.g. service connectors, programming connectors, temporary connectors etc. shall not be connected to any cables for the purpose of EMC testing. Where cables have to be connected to these ports, or interconnecting cables have to be extended in length in order to exercise the EUT, precautions shall be taken to ensure that the evaluation of the EUT is not affected by the addition or extension of these cables;
+- Immunity tests on the entire AAS BS shall be performed by establishing communication links at the radio interface (e.g. with the mobile simulator) and the S1/Iub interface (e.g. with an RNC/EPC simulator) and evaluating the BLER/throughput (see figures 9.1-1 and 9.1-2);
+- Immunity tests shall be performed on both the Uplink and Downlink paths. The tests shall also include both the radio interface and the S1/Iub interface. BLER/throughput evaluation may be carried out at either interface, where appropriate, and the measurements for the Uplink and Downlink paths may be carried out as a single path looped at either the radio interface or S1/Iub interface. In case of looping is used care have to be taken that the BLER/throughput information doesn't change due to looping;
+- For AAS BS capable of multi-RAT and/or multi-band operation, communication links shall be established in such a way that all RATs and operating band(s) are activated during the test according to the applicable test configurations in subclause 4.5. Performance assessment may be done separately for each RAT and/or operating band.
+
+![Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+```
+
+graph LR
+    UE[UE simulator] <--> BS[hybrid AAS BS  
+(TAB connectors terminated)]
+    BS <--> EPC[EPC / RNC simulator]
+  
+```
+
+Figure 9.1-1: Communication link set up for hybrid AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, a 'hybrid AAS BS (TAB connectors terminated)' in the center, and an 'EPC / RNC simulator' on the right. Arrows indicate bidirectional communication links between the UE simulator and the hybrid AAS BS, and between the hybrid AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-1: Communication link set up for *hybrid AAS BS* immunity measurement**
+
+![Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.](d9c0a780cd22626253dab4aa41699e2f_img.jpg)
+
+```
+
+graph LR
+    UE[UE simulator] <-->|OTA link| BS[OTA AAS BS]
+    BS <--> EPC[EPC / RNC simulator]
+  
+```
+
+Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement. The diagram shows three main components: a 'UE simulator' on the left, an 'OTA AAS BS' in the center, and an 'EPC / RNC simulator' on the right. A bidirectional arrow labeled 'OTA link' connects the UE simulator and the OTA AAS BS. A bidirectional arrow also connects the OTA AAS BS and the EPC / RNC simulator.
+
+**Figure 9.1-2: Communication link set up for OTA AAS BS immunity measurement**
+
+## 9.2 RF electromagnetic field (80 MHz - 6000 MHz)
+
+### 9.2.1 RF electromagnetic field, hybrid AAS BS
+
+This test assesses the ability of radio equipment to operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. This test is applicable to *hybrid AAS BS* and shall be performed on a representative configuration of the *hybrid AAS BS*.
+
+The test method and levels shall be in accordance with IEC 61000-4-3 [16] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively. The use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+### 9.2.2 RF electromagnetic field, OTA AAS BS
+
+This test assesses the ability of radio equipment operate as intended in the presence of a radio frequency electromagnetic field disturbance at the enclosure. The OTA AAS BS includes an antenna which is an intentional radiator and does not form part of the EMC enclosure, application of RF electromagnetic fields in these directions may damage the BS receivers unintentionally.
+
+In the operational range of angles of the OTA AAS BS antenna receivers are protected by the RF blocking requirements defined in TS 37.105 [2], conforming to the test requirement in TS 37.145-2 [10] and are not part of the EMC RF electromagnetic field immunity requirement.
+
+In the range of angles except the operational range of angles of the OTA AAS BS antenna (i.e. except for the half sphere around the DUT radiating direction as depicted on figure 9.2.2-1) and for the frequency range above 690 MHz (according to ETSI EN 301 489-50 [25]), the EMC RF electromagnetic field immunity requirement with a level of 10 V/m applies on the non-radiating faces of the OTA AAS BS, as depicted on figure 9.2.2-1.
+
+When no spatial exclusion is implemented the use of reverberation chamber test method according to IEC 61000-4-21 [35], clause 6.1 and Annex D as alternative method is allowed.
+
+![Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+Diagram illustrating the EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS. The diagram shows a Device Under Test (DUT) represented by a semi-circular shape on the left. A dashed rectangular box labeled 'Spatial exclusion zone' is positioned to the right of the DUT. Three arrows indicate testing directions: 'RI testing direction' from the top pointing down towards the DUT, 'RI testing direction' from the bottom pointing up towards the DUT, and 'DUT radiating direction' from the DUT pointing horizontally to the right. Another 'RI testing direction' arrow points horizontally from the left towards the DUT.
+
+**Figure 9.2.2-1** EMC RF electromagnetic field immunity requirement testing directions for OTA AAS BS (horizontal plane depicted) with the *spatial exclusion zone* applied
+
+Depending on RAT capability sets supported by the OTA AAS BS, the following RF electromagnetic field requirements apply over the range of angles covered by the EMC RF electromagnetic field immunity requirement:
+
+- For OTA AAS BS in *single RAT UTRA operation*, the RF electromagnetic field immunity requirements from TS 25.113 [5] apply.
+- For OTA AAS BS in *single RAT E-UTRA operation*, the RF electromagnetic field immunity requirements from TS 36.113 [6] apply.
+- For OTA AAS BS in *MSR operation*, the RF electromagnetic field immunity requirements from TS 37.113 [4] apply.
+- For OTA AAS BS in *single RAT NR operation*, the *BS type I-O* requirements for the RF electromagnetic field immunity from TS 38.113 [30] apply.
+
+## 9.3 Electrostatic discharge
+
+This test assesses the ability of radio equipment to operate as intended in the event of an electrostatic discharge.
+
+The test shall be performed on a representative configuration of the radio equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-2 [15] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.4 Fast transients common mode
+
+The test shall be performed on AC mains power input ports.
+
+This test shall be performed on signal ports, telecommunication ports, control ports and DC power input/output ports if the cables may be longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than 3 m, a list of ports which were not tested for this reason shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-4 [17] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.5 RF common mode (0.15 MHz - 80 MHz)
+
+The test shall be performed on AC mains power input/output ports.
+
+This test shall be performed on signal ports, telecommunication ports, control and DC power input/output ports, which may have cables longer than 3 m.
+
+Where this test is not carried out on a port or any other ports because the manufacturer declares that it is not intended to be used with cables longer than stated above, a list of ports which were not tested shall be included in the test report.
+
+This test shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-6 [19] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+NOTE: This test can also be performed using the clamp injection method, where appropriate, see IEC 61000-4-6 [19].
+
+## 9.6 Voltage dips and interruptions
+
+These tests assess the ability of radio equipment to operate as intended in the event of voltage dips and interruptions present on the AC mains power input ports.
+
+The tests shall be performed on AC mains power input ports.
+
+These tests shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-11 [20] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+## 9.7 Surges, common and differential mode
+
+These tests assess the ability of radio equipment to operate as intended in the event of surges being present at the AC mains power input ports and telecommunication ports.
+
+The tests shall be performed on AC mains power input ports.
+
+This test shall be additionally performed on telecommunication ports.
+
+These tests shall be performed on a representative configuration of the equipment.
+
+The test method and levels shall be in accordance with IEC 61000-4-5 [18] as captured in TS 25.113 [5], TS 36.113 [6], TS 38.113 [30] and TS 37.113 [4] for UTRA, E-UTRA, NR and MSR, respectively.
+
+# Annex A (informative): Change history
+
+| Change history |         |           |      |     |     |                                                                                                  |  |               |
+|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------|--|---------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                  |  | New version   |
+| 2016-02        | RAN4#78 | R4-161123 |      |     |     | First version of TS                                                                              |  | 0.1.0         |
+| 2016-03        | RAN#71  | RP-160401 |      |     |     | Presented to RAN for approval.<br>Editorial corrections recommended by ETSI editHelp             |  | 1.0.0         |
+| 2016-03        | RP-71   |           |      |     |     | TR approved by RAN plenary                                                                       |  | 13.0.0        |
+| 2016/06        | RP-72   | RP-161142 | 0002 | 1   | F   | Clarification in EMC environmental conditions references                                         |  | 13.1.0        |
+| 2017/03        | RP-75   | RP-170586 | 0004 | -   | F   | CR to TS 37.114: Clarification of the EMC specification's scope                                  |  | 13.2.0        |
+| 2017-03        | RP-75   | -         | -    | -   | -   | Update to Rel-14 version (MCC)                                                                   |  | 14.0.0        |
+| 2017/06        | RP-76   | RP-171306 | 0009 |     | A   | CR to TS 37.114: Isolation of Band 46 and NB-IoT from the AAS BS specification                   |  | 14.1.0        |
+| 2017-12        | RAN#78  | RP-172599 | 0059 | 1   | B   | Big CR to TS 37.114: eAAS EMC specification, v15.0.0                                             |  | 15.0.0        |
+| 2018-03        | RAN#79  | RP-180282 | 0064 |     | F   | CR to TS37.114                                                                                   |  | 15.1.0        |
+| 2018-06        | RAN#80  | RP-181075 | 0067 | 1   | B   | CR to TS 37.114: NR introduction into AAS EMC specification                                      |  | 15.2.0        |
+| 2018-12        | RAN#82  | RP-182362 | 0071 | 2   | B   | CR to TS 37.114: Clarification on Exclusion Bands for Radiated Immunity Test in FR2              |  | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0073 | 1   | F   | CR to TS 37.114: additional inputs for introduction of NR to the AAS EMC specification           |  | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0074 |     | F   | CR to TS 37.114: RAT-specific AAS BS operation terminology corrections                           |  | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0075 | 1   | B   | CR to TS 37.114: Consideration of the narrowband responses and communication link                |  | 15.3.0        |
+| 2018-12        | RAN#82  | RP-182386 | 0076 |     | F   | CR to TS 37.114: clarification on CSA and RCSA capability sets                                   |  | 15.3.0        |
+| 2019-03        | RAN#83  | RP-190401 | 0077 | 1   | B   | Draft CR to TS 37.114 Exclusion Bands for Radiated                                               |  | 15.4.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0078 | 1   | F   | CR to TS 37.114: Updates for Rx exclusion zone size and terminology for EMC RI testing purposes  |  | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0080 | 1   | F   | CR to TS 37.114 subclause 4.2                                                                    |  | 15.5.0        |
+| 2019-06        | RAN#84  | RP-191262 | 0084 |     | F   | CR to 37.114 Subsections index in Section 4.1                                                    |  | 15.5.0        |
+| 2019-09        | RAN#85  | RP-192019 | 0085 |     | F   | CR to TS 37.114 Correction on CISPR 16-1-1 for DC conducted Emission(clause 2 and subclause 7.1) |  | 15.6.0        |
+| 2019-09        | RAN#85  | RP-192053 | 0087 | 1   | F   | CR to 37.114 Editorial Corrections                                                               |  | 15.6.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0093 |     | F   | CR to TS 37.114 Correction on definitions subclause 3.1                                          |  | 15.7.0        |
+| 2019-12        | RAN#86  | RP-193002 | 0094 |     | F   | CR to TS 37.114 Correction on notes in subclause 7.1                                             |  | 15.7.0        |
+| 2020-03        | RAN#87  | RP-200393 | 0095 | 1   | F   | CR to TS 37.114 Add the transmitter exclusion band for MSR BS(subclause 4.1)                     |  | 15.8.0        |
+| 2020-06        | RAN#88  | RP-201005 | 0096 |     | F   | CR to TS 37.114: internal TR reference corrections, Rel-15                                       |  | 15.9.0        |
+| 2020-06        | RAN#88  | RP-200984 | 0097 | 1   | F   | [R15]CR to TS 37.114 Add the reverberation chamber for radiated immunity testing (clause 2)      |  | 15.9.0        |
+| 2020-06        | RAN#88  | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                                   |  | <b>16.0.0</b> |
+| 2023-03        | RAN#99  |           |      |     |     |                                                                                                  |  | 16.1.0        |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37144/raw.md b/marked/Rel-16/37_series/37144/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..66f1978691cb07db62ddb7d32ed9084177724a59
--- /dev/null
+++ b/marked/Rel-16/37_series/37144/raw.md
@@ -0,0 +1,2037 @@
+
+
+# 3GPP TS 37.144 V16.0.0 (2020-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) and Mobile Station (MS) GSM, UTRA and E-UTRA over the air performance requirements (Release 16)** ---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+---
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                             |    |
+|---------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                              | 6  |
+| 1 Scope.....                                                                                | 7  |
+| 2 References.....                                                                           | 7  |
+| 3 Definitions, symbols and abbreviations.....                                               | 8  |
+| 3.1 Definitions.....                                                                        | 8  |
+| 3.2 Symbols.....                                                                            | 8  |
+| 3.3 Abbreviations .....                                                                     | 8  |
+| 4 General.....                                                                              | 8  |
+| 4.1 Minimum requirements for roaming bands.....                                             | 8  |
+| 4.2 Relationship between minimum requirements for roaming bands and test requirements ..... | 8  |
+| 4.3 Terminal classes.....                                                                   | 9  |
+| 4.3.1 Mechanical modes .....                                                                | 9  |
+| 4.4 UTRA chip rates.....                                                                    | 9  |
+| 5 Frequency bands .....                                                                     | 9  |
+| 5.1 GSM frequency bands.....                                                                | 9  |
+| 5.2 UTRA FDD frequency bands.....                                                           | 9  |
+| 5.3 UTRA TDD frequency bands .....                                                          | 10 |
+| 5.4 E-UTRA FDD frequency bands.....                                                         | 10 |
+| 5.5 E-UTRA TDD frequency bands.....                                                         | 10 |
+| 6 Transmitter total radiated power .....                                                    | 11 |
+| 6.1 Minimum requirement for roaming bands for handheld UE.....                              | 11 |
+| 6.1.1 Beside the head phantom position.....                                                 | 11 |
+| 6.1.1.1 GSM.....                                                                            | 11 |
+| 6.1.1.2 UTRA FDD.....                                                                       | 12 |
+| 6.1.1.3 UTRA LCR TDD.....                                                                   | 12 |
+| 6.1.2 Beside the head and hand phantom position .....                                       | 12 |
+| 6.1.2.1 UTRA FDD.....                                                                       | 12 |
+| 6.1.2.2 UTRA LCR TDD.....                                                                   | 13 |
+| 6.1.2.3 E-UTRA FDD.....                                                                     | 13 |
+| 6.1.2.4 E-UTRA TDD.....                                                                     | 13 |
+| 6.1.3 Hand phantom browsing mode position.....                                              | 13 |
+| 6.1.3.1 UTRA FDD.....                                                                       | 13 |
+| 6.1.3.2 UTRA LCR TDD.....                                                                   | 14 |
+| 6.1.3.3 E-UTRA FDD.....                                                                     | 14 |
+| 6.1.3.4 E-UTRA TDD.....                                                                     | 14 |
+| 6.2 Minimum requirement for roaming bands for LME .....                                     | 14 |
+| 6.2.1 GSM .....                                                                             | 15 |
+| 6.2.2 UTRA FDD .....                                                                        | 15 |
+| 6.2.3 UTRA LCR TDD .....                                                                    | 15 |
+| 6.2.4 E-UTRA FDD .....                                                                      | 16 |
+| 6.2.5 E-UTRA TDD .....                                                                      | 16 |
+| 6.3 Minimum requirement for roaming bands for LEE .....                                     | 16 |
+| 6.3.1 GSM .....                                                                             | 16 |
+| 6.3.2 UTRA FDD.....                                                                         | 17 |
+| 6.3.3 UTRA LCR TDD .....                                                                    | 18 |
+| 6.3.4 E-UTRA FDD .....                                                                      | 18 |
+| 6.3.5 E-UTRA TDD .....                                                                      | 19 |
+| 7 Receiver total radiated sensitivity .....                                                 | 19 |
+| 7.1 Minimum requirement for roaming bands for handheld UE.....                              | 19 |
+| 7.1.1 Beside the head phantom position.....                                                 | 19 |
+| 7.1.1.1 GSM.....                                                                            | 19 |
+| 7.1.1.2 UTRA FDD.....                                                                       | 20 |
+| 7.1.1.3 UTRA LCR TDD.....                                                                   | 20 |
+| 7.1.2 Beside the head and hand phantoms position.....                                       | 21 |
+
+|                               |                                                            |           |
+|-------------------------------|------------------------------------------------------------|-----------|
+| 7.1.2.1                       | UTRA FDD.....                                              | 21        |
+| 7.1.2.2                       | UTRA LCR TDD.....                                          | 21        |
+| 7.1.2.3                       | E-UTRA FDD.....                                            | 22        |
+| 7.1.2.4                       | E-UTRA TDD.....                                            | 22        |
+| 7.1.3                         | Hand phantom browsing mode position.....                   | 22        |
+| 7.1.3.1                       | UTRA FDD.....                                              | 22        |
+| 7.1.3.2                       | UTRA LCR TDD.....                                          | 22        |
+| 7.1.3.3                       | E-UTRA FDD.....                                            | 23        |
+| 7.1.3.4                       | E-UTRA TDD.....                                            | 23        |
+| 7.2                           | Minimum requirement for roaming bands for LME .....        | 23        |
+| 7.2.1                         | GSM .....                                                  | 23        |
+| 7.2.2                         | UTRA FDD .....                                             | 23        |
+| 7.2.3                         | UTRA LCR TDD .....                                         | 24        |
+| 7.2.4                         | E-UTRA FDD .....                                           | 24        |
+| 7.2.5                         | E-UTRA TDD .....                                           | 24        |
+| 7.3                           | Minimum requirement for roaming bands for LEE .....        | 24        |
+| 7.3.1                         | GSM .....                                                  | 25        |
+| 7.3.2                         | UTRA FDD .....                                             | 25        |
+| 7.3.3                         | UTRA LCR TDD .....                                         | 26        |
+| 7.3.4                         | E-UTRA FDD .....                                           | 26        |
+| 7.3.5                         | E-UTRA TDD .....                                           | 27        |
+| 8                             | Receiver total radiated multi-antenna sensitivity.....     | 27        |
+| 8.1                           | Minimum requirement for roaming bands for handheld UE..... | 27        |
+| 8.1.1                         | Free Space .....                                           | 27        |
+| 8.1.1.1                       | E-UTRA FDD.....                                            | 28        |
+| 8.1.1.2                       | E-UTRA TDD.....                                            | 28        |
+| <b>Annex A (normative):</b>   | <b>Environmental conditions.....</b>                       | <b>30</b> |
+| A.1                           | General.....                                               | 30        |
+| A.2                           | Environmental requirements.....                            | 30        |
+| A.2.2                         | Temperature .....                                          | 30        |
+| A.2.3                         | Voltage .....                                              | 30        |
+| <b>Annex B (informative):</b> | <b>Recommended performance.....</b>                        | <b>31</b> |
+| B.1                           | General.....                                               | 31        |
+| B.2                           | Transmitter total radiated power .....                     | 31        |
+| B.2.1                         | Recommended performance for handheld UE.....               | 31        |
+| B.2.1.1                       | Beside the head phantom position.....                      | 31        |
+| B.2.1.1.1                     | GSM.....                                                   | 31        |
+| B.2.1.1.2                     | UTRA FDD.....                                              | 31        |
+| B.2.1.1.3                     | UTRA LCR TDD.....                                          | 32        |
+| B.2.1.2                       | Beside the head and hand phantoms position.....            | 32        |
+| B.2.1.2.1                     | UTRA FDD.....                                              | 32        |
+| B.2.1.2.2                     | UTRA LCR TDD.....                                          | 32        |
+| B.2.1.2.3                     | E-UTRA FDD.....                                            | 33        |
+| B.2.1.2.4                     | E-UTRA TDD.....                                            | 33        |
+| B.2.1.3                       | Hand phantom browsing mode position.....                   | 33        |
+| B.2.1.3.1                     | UTRA FDD.....                                              | 33        |
+| B.2.1.3.2                     | UTRA LCR TDD.....                                          | 33        |
+| B.2.1.3.3                     | E-UTRA FDD.....                                            | 34        |
+| B.2.1.3.4                     | E-UTRA TDD.....                                            | 34        |
+| B.2.2                         | Recommended performance for LME.....                       | 34        |
+| B.2.2.1                       | GSM .....                                                  | 34        |
+| B.2.2.2                       | UTRA FDD .....                                             | 34        |
+| B.2.2.3                       | UTRA LCR TDD .....                                         | 34        |
+| B.2.2.4                       | E-UTRA FDD .....                                           | 35        |
+| B.2.2.5                       | E-UTRA TDD .....                                           | 35        |
+| B.2.3                         | Recommended performance for LEE.....                       | 35        |
+| B.2.3.1                       | GSM .....                                                  | 35        |
+
+|                               |                                                 |           |
+|-------------------------------|-------------------------------------------------|-----------|
+| B.2.3.2                       | UTRA FDD .....                                  | 36        |
+| B.2.3.3                       | UTRA LCR TDD .....                              | 36        |
+| B.2.3.4                       | E-UTRA FDD .....                                | 37        |
+| B.2.3.5                       | E-UTRA TDD .....                                | 37        |
+| B.3                           | Receiver total radiated sensitivity .....       | 37        |
+| B.3.1                         | Recommended performance for handheld UE.....    | 37        |
+| B.3.1.1                       | Beside the head phantom position.....           | 37        |
+| B.3.1.1.1                     | GSM.....                                        | 37        |
+| B.3.1.1.2                     | UTRA FDD.....                                   | 38        |
+| B.3.1.1.3                     | UTRA LCR TDD.....                               | 38        |
+| B.3.1.2                       | Beside the head and hand phantoms position..... | 39        |
+| B.3.1.2.1                     | UTRA FDD.....                                   | 39        |
+| B.3.1.2.2                     | UTRA LCR TDD.....                               | 39        |
+| B.3.1.2.3                     | E-UTRA FDD.....                                 | 40        |
+| B.3.1.2.4                     | E-UTRA TDD.....                                 | 40        |
+| B.3.1.3                       | Hand phantom browsing mode position.....        | 40        |
+| B.3.1.3.1                     | UTRA FDD.....                                   | 40        |
+| B.3.1.3.2                     | UTRA LCR TDD.....                               | 40        |
+| B.3.1.3.3                     | E-UTRA FDD.....                                 | 41        |
+| B.3.1.3.4                     | E-UTRA TDD.....                                 | 41        |
+| B.3.2                         | Recommended performance for LME.....            | 41        |
+| B.3.2.1                       | GSM .....                                       | 41        |
+| B.3.2.2                       | UTRA FDD .....                                  | 41        |
+| B.3.2.3                       | UTRA LCR TDD .....                              | 41        |
+| B.3.2.4                       | E-UTRA FDD .....                                | 42        |
+| B.3.2.5                       | E-UTRA TDD .....                                | 42        |
+| B.3.3                         | Recommended performance for LEE.....            | 42        |
+| B.3.3.1                       | GSM .....                                       | 42        |
+| B.3.3.2                       | UTRA FDD .....                                  | 42        |
+| B.3.3.3                       | UTRA LCR TDD .....                              | 43        |
+| B.3.3.4                       | E-UTRA FDD .....                                | 44        |
+| B.3.3.5                       | E-UTRA TDD .....                                | 44        |
+| <b>Annex C (informative):</b> | <b>Change history.....</b>                      | <b>45</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document establishes over the air antenna minimum requirements for user equipment (UE) and mobile station (MS).
+
+Handheld UE requirements are defined for roaming bands for the speech position (beside the head and beside the head and hand) and hand phantom browsing mode position. Laptop mounted equipment requirements are defined for roaming bands for the data transfer position (laptop ground plane phantom). Laptop embedded equipment requirements are defined for roaming bands for the data transfer position (free space).
+
+All bands are potential roaming bands, and the requirements for roaming bands shall therefore be fulfilled for all bands supported by a UE/MS.
+
+Requirements for operating bands are dependent on how the network has been built and are thus operator specific and cannot be specified here. Recommended performance values for operating bands (Annex B) are however included in this specification for information. It should be recognised that the ability to meet the recommended performance values depends on the number of frequency bands supported by the UE/MS.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25 101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [3] 3GPP TS 45.005: "Radio transmission and reception".
+- [4] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing".
+- [5] ETSI ETR 273: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [6] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode"
+- [7] 3GPP TR 37.977: "Verification of radiated multi-antenna reception performance of User Equipment (UE)"
+- [8] 3GPP TR 37.902: "Measurements of User Equipment (UE) radio performances for LTE/UMTS terminals; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology"
+- [9] 3GPP TS 36.521-1: "User Equipment (UE) conformance specification Radio transmission and reception; Part 1: Conformance Testing;"
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TR 37.977 [7] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TR 37.977 [7].
+
+**primary mechanical mode:** the mode that is most often used during a call beside the head. Other mechanical modes are secondary. Every terminal has at least one primary mechanical mode.
+
+**speech position:** UE used close to head phantom (specific anthropomorphic mannequin).
+
+**data transfer position:** UE used away from the user's head, applicable for LME and LEE devices.
+
+**FS:** UE used in a free space configuration.
+
+**LME:** Laptop mounted equipment (such as plug-in devices like USB dongles).
+
+**LEE:** Laptop embedded equipment (such as embedded module card embedded in notebooks).
+
+## 3.2 Symbols
+
+|                 |                                                                                          |
+|-----------------|------------------------------------------------------------------------------------------|
+| $TRP_{average}$ | the average measured total radiated power of low, mid and high channel                   |
+| $TRP_{min}$     | the lowest measured total radiated power of each channel within an operating band        |
+| $TRS_{average}$ | the average measured total radiated sensitivity of low, mid and high channel             |
+| $TRS_{max}$     | the highest measured total radiated sensitivity of each channel within an operating band |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1], TR 37.977 [7] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] or TR 37.977 [7].
+
+|      |                                          |
+|------|------------------------------------------|
+| DUT  | Device Under Test                        |
+| OTA  | Over The Air                             |
+| TRMS | Total Radiated Multi-antenna Sensitivity |
+| TRP  | Total Radiated Power                     |
+| TRS  | Total Radiated Sensitivity               |
+
+# 4 General
+
+## 4.1 Minimum requirements for roaming bands
+
+The minimum requirements for roaming bands apply only to the primary mechanical mode in the environmental conditions specified in Annex A. All bands are potential roaming bands, and a UE/MS shall fulfil the minimum requirements for roaming bands for all bands supported by the UE/MS.
+
+## 4.2 Relationship between minimum requirements for roaming bands and test requirements
+
+The minimum requirements for roaming bands given in this specification make no allowance for measurement uncertainty. The test specification 34.114 [4] Annex F defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements.
+
+The measurement results returned by the test system are compared - without any modification - against the test requirements as defined by the shared risk principle.
+
+The shared risk principle is defined in ETR 273 [5] Part 1 sub-part 2 section 6.5.
+
+## 4.3 Terminal classes
+
+### 4.3.1 Mechanical modes
+
+The mechanical modes of a device under test (DUT) are declared by the manufacturer. A DUT shall have at least one mechanical mode. If only one mode is supported, then this is defined as the primary.
+
+## 4.4 UTRA chip rates
+
+The requirements defined in this specification for UTRA are based on a chip rate of 3.84 Mcps (FDD) and 1.28 Mcps (TDD).
+
+NOTE: Other chip rates may be considered in future releases.
+
+# 5 Frequency bands
+
+## 5.1 GSM frequency bands
+
+The requirements defined in this specification for GSM apply to the frequency bands defined in Table 5.1-1.
+
+**Table 5.1-1: GSM frequency bands**
+
+| Operating band | UL frequencies<br>MS transmit, BTS receive | DL frequencies<br>MS receive, BTS transmit |
+|----------------|--------------------------------------------|--------------------------------------------|
+| GSM 850        | 824 - 849 MHz                              | 869 - 894 MHz                              |
+| P-GSM 900      | 890 - 915 MHz                              | 935 - 960 MHz                              |
+| E-GSM 900      | 880 - 915 MHz                              | 925 - 960 MHz                              |
+| DCS 1800       | 1710 - 1785 MHz                            | 1805 - 1880 MHz                            |
+| PCS 1900       | 1850 - 1910 MHz                            | 1930 - 1990 MHz                            |
+
+## 5.2 UTRA FDD frequency bands
+
+The requirements defined in this specification for UTRA FDD apply to the frequency bands defined in Table 5.2-1.
+
+**Table 5.2-1: UTRA FDD frequency bands**
+
+| Operating Band | UL frequencies<br>UE transmit, Node B receive | DL frequencies<br>UE receive, Node B transmit |
+|----------------|-----------------------------------------------|-----------------------------------------------|
+| I              | 1920 - 1980 MHz                               | 2110 - 2170 MHz                               |
+| II             | 1850 - 1910 MHz                               | 1930 - 1990 MHz                               |
+| III            | 1710 - 1785 MHz                               | 1805 - 1880 MHz                               |
+| IV             | 1710 - 1755 MHz                               | 2110 - 2155 MHz                               |
+| V              | 824 - 849 MHz                                 | 869 - 894 MHz                                 |
+| VI             | 830 - 840 MHz                                 | 875 - 885 MHz                                 |
+| VII            | 2500 - 2570 MHz                               | 2620 - 2690 MHz                               |
+| VIII           | 880 - 915 MHz                                 | 925 - 960 MHz                                 |
+| IX             | 1749,9 - 1784,9 MHz                           | 1844,9 - 1879,9 MHz                           |
+| XIX            | 830 - 845 MHz                                 | 875 - 890 MHz                                 |
+
+Deployment in other frequency bands is not precluded
+
+## 5.3 UTRA TDD frequency bands
+
+The requirements defined in this specification for UTRA TDD apply to the frequency bands defined in Table 5.3-1.
+
+**Table 5.3-1: UTRA LCR TDD frequency bands**
+
+| Operating Band | Frequencies                        |
+|----------------|------------------------------------|
+| a              | 1900 - 1920 MHz<br>2010 - 2025 MHz |
+| b*             | 1850 - 1910 MHz<br>1930 - 1990 MHz |
+| c*             | 1910 - 1930 MHz                    |
+| d**            | 2570 - 2620 MHz                    |
+| e              | 2300 - 2400 MHz                    |
+| f              | 1880 - 1920 MHz                    |
+
+NOTE: Deployment in other frequency bands is not precluded.
+
+\* Used in ITU Region 2
+
+\*\* Used in ITU Region 1
+
+## 5.4 E-UTRA FDD frequency bands
+
+The requirements defined in this specification for E-UTRA FDD apply to the frequency bands defined in Table 5.4-1.
+
+**Table 5.4-1 E-UTRA FDD operating bands**
+
+| E-UTRA Operating Band | Uplink (UL) operating band                 | Downlink (DL) operating band               | Duplex Mode      |
+|-----------------------|--------------------------------------------|--------------------------------------------|------------------|
+|                       | BS receive<br>UE transmit                  | BS transmit<br>UE receive                  |                  |
+|                       | F <sub>UL_low</sub> – F <sub>UL_high</sub> | F <sub>DL_low</sub> – F <sub>DL_high</sub> |                  |
+| 1                     | 1920 MHz – 1980 MHz                        | 2110 MHz – 2170 MHz                        | FDD              |
+| 2                     | 1850 MHz – 1910 MHz                        | 1930 MHz – 1990 MHz                        | FDD              |
+| 3                     | 1710 MHz – 1785 MHz                        | 1805 MHz – 1880 MHz                        | FDD              |
+| 4                     | 1710 MHz – 1755 MHz                        | 2110 MHz – 2155 MHz                        | FDD              |
+| 5                     | 824 MHz – 849 MHz                          | 869 MHz – 894 MHz                          | FDD              |
+| 7                     | 2500 MHz – 2570 MHz                        | 2620 MHz – 2690 MHz                        | FDD              |
+| 8                     | 880 MHz – 915 MHz                          | 925 MHz – 960 MHz                          | FDD              |
+| 12                    | 699 MHz – 716 MHz                          | 729 MHz – 746 MHz                          | FDD              |
+| 13                    | 777 MHz – 787 MHz                          | 746 MHz – 756 MHz                          | FDD              |
+| 19                    | 830 MHz – 845 MHz                          | 875 MHz – 890 MHz                          | FDD              |
+| 20                    | 832 MHz – 862 MHz                          | 791 MHz – 821 MHz                          | FDD              |
+| 21                    | 1447.9 MHz – 1462.9 MHz                    | 1495.9 MHz – 1510.9 MHz                    | FDD              |
+| 28                    | 703 MHz – 748 MHz                          | 758 MHz – 803 MHz                          | FDD              |
+| 32                    | N/A                                        | 1452 MHz – 1496 MHz                        | FDD <sup>1</sup> |
+
+NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell.
+
+Deployment in other frequency bands is not precluded.
+
+## 5.5 E-UTRA TDD frequency bands
+
+The requirements defined in this specification for E-UTRA TDD apply to the frequency bands defined in Table 5.5-1.
+
+Table 5.5-1 E-UTRA TDD operating bands
+
+| E-UTRA Operating Band | Uplink (UL) operating band<br>BS receive<br>UE transmit |                  | Downlink (DL) operating band<br>BS transmit<br>UE receive |                  | Duplex Mode        |
+|-----------------------|---------------------------------------------------------|------------------|-----------------------------------------------------------|------------------|--------------------|
+|                       | $F_{UL\_low}$                                           | $- F_{UL\_high}$ | $F_{DL\_low}$                                             | $- F_{DL\_high}$ |                    |
+| 38                    | 2570 MHz                                                | – 2620 MHz       | 2570 MHz                                                  | – 2620 MHz       | TDD                |
+| 39                    | 1880 MHz                                                | – 1920 MHz       | 1880 MHz                                                  | – 1920 MHz       | TDD                |
+| 40                    | 2300 MHz                                                | – 2400 MHz       | 2300 MHz                                                  | – 2400 MHz       | TDD                |
+| 41                    | 2496 MHz                                                | – 2690 MHz       | 2496 MHz                                                  | – 2690 MHz       | TDD                |
+| 42                    | 3400 MHz                                                | – 3600 MHz       | 3400 MHz                                                  | – 3600 MHz       | TDD                |
+| 46                    | 5150 MHz                                                | – 5925 MHz       | 5150 MHz                                                  | – 5925 MHz       | TDD <sup>1,2</sup> |
+
+NOTE 1: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3
+
+NOTE 2: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured.
+
+Deployment in other frequency bands is not precluded.
+
+# 6 Transmitter total radiated power
+
+## 6.1 Minimum requirement for roaming bands for handheld UE
+
+The average measured total radiated power (TRP) of low, mid and high channel for handheld UE shall be higher than the average TRP requirement specified in subclauses 6.1.1, 6.1.2 and 6.1.3. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head in case of beside the head phantom and beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+$$TRP_{average} = 10 \log \left[ \frac{10^{P_{left\_low}/10} + 10^{P_{left\_mid}/10} + 10^{P_{left\_high}/10} + 10^{P_{right\_low}/10} + 10^{P_{right\_mid}/10} + 10^{P_{right\_high}/10}}{6} \right]$$
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in subclauses 6.1.1, 6.1.2 and 6.1.3. Minimum TRP requirement is shown in the column “Min” on the requirement tables.
+
+$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+### 6.1.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2.
+
+#### 6.1.1.1 GSM
+
+Handheld MS TRP minimum performance requirements for GMSK in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.1-1.
+
+Table 6.1.1.1-1: Handheld UE TRP minimum performance requirement for GSM roaming bands in beside the head phantom position and the primary mechanical mode
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |      | Power class 5 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|------|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |      | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min  | Average       | Min |
+| GSM 850        |               |     |               |     |               |     | 19,5          | 17,5 |               |     |
+| GSM 900        |               |     |               |     |               |     | 20,5          | 18,5 |               |     |
+| DCS 1800       | 21            | 19  |               |     |               |     |               |      |               |     |
+| PCS 1900       | 21            | 19  |               |     |               |     |               |      |               |     |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+#### 6.1.1.2 UTRA FDD
+
+Handheld UE TRP minimum performance requirements for UTRA FDD in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.2-1.
+
+**Table 6.1.1.2-1: Handheld UE TRP minimum performance requirement for UTRA FDD roaming bands in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |      | Power class 3bis |      | Power class 4 |      |
+|----------------|---------------|---------------|---------------|------|------------------|------|---------------|------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)      |      | Power (dBm)   |      |
+|                |               |               | Average       | Min  | Average          | Min  | Average       | Min  |
+| I              | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| II             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| III            | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| IV             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| V              | -             | -             | +11           | +9   | +11              | +9   | +9            | +7   |
+| VI             | -             | -             | +11           | +9   | +11              | +9   | +9            | +7   |
+| VII            | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| VIII           | -             | -             | +12           | +10  | +12              | +10  | +10           | +8   |
+| IX             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| XIX            | -             | -             | +11,5         | +9,5 | +11,5            | +9,5 | +9,5          | +7,5 |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+#### 6.1.1.3 UTRA LCR TDD
+
+Handheld UE TRP minimum performance requirements for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode are defined in Table 6.1.1.3-1.
+
+**Table 6.1.1.3-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | +15           | +13 | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | +15           | +13 | -             | -   | -             | -   |
+| f              | -             | -   | +15           | +13 | -             | -   | -             | -   |
+
+NOTE: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+### 6.1.2 Beside the head and hand phantom position
+
+Beside the head and hand phantom position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.6.
+
+#### 6.1.2.1 UTRA FDD
+
+Handheld UE TRP minimum performance requirements for UTRA FDD in beside the head and hand phantom position and the primary mechanical mode are defined in Table 6.1.2.1-1.
+
+**Table 6.1.2.1-1: Handheld UE TRP minimum performance requirement for FDD roaming bands in beside the head and hand phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |     | Power class 3bis |     | Power class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+| I              | -             | -             | 13,25         | TBD | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | 13,25         | TBD | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | 9,40          | TBD | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | 9,40          | TBD | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | 9,40          | TBD | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | 9,40          | TBD | TBD              | TBD | TBD           | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914.
+
+NOTE 3: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation).
+
+#### 6.1.2.2 UTRA LCR TDD
+
+Handheld UE TRP minimum performance requirements for UTRA LCR TDD in beside the head and hand phantom position and the primary mechanical mode are defined in Table 6.1.2.2-1.
+
+**Table 6.1.2.2-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands beside the head and hand phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE: Applicable for dual-mode GSM /UTRA LCR TDD.
+
+#### 6.1.2.3 E-UTRA FDD
+
+#### 6.1.2.4 E-UTRA TDD
+
+### 6.1.3 Hand phantom browsing mode position
+
+Hand phantom browsing mode position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.7.
+
+#### 6.1.3.1 UTRA FDD
+
+Handheld UE TRP minimum performance requirements for UTRA FDD in hand phantom browsing mode position are defined in Table 6.1.3.1-1.
+
+**Table 6.1.3.1-1: Handheld UE TRP minimum performance requirement for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |     | Power class 3bis |     | Power class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+| I              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+#### 6.1.3.2 UTRA LCR TDD
+
+Handheld UE TRP minimum performance requirements for UTRA LCR TDD UE in hand phantom browsing mode position are defined in Table 6.1.3.2-1.
+
+**Table 6.1.3.2-1: Handheld UE TRP minimum performance requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |     | Power class 4 |     |         |     |
+|----------------|---------------|---------------|---------------|-----|---------------|-----|---------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)   |     |         |     |
+|                | Average       | Min           | Average       | Min | Average       | Min | Average | Min |
+| a              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+| b              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+| c              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+| d              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+| e              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+| f              | -             | -             | TBD           | TBD | -             | -   | -       | -   |
+
+NOTE: Applicable for dual-mode GSM /UTRA LCR TDD.
+
+#### 6.1.3.3 E-UTRA FDD
+
+#### 6.1.3.4 E-UTRA TDD
+
+## 6.2 Minimum requirement for roaming bands for LME
+
+The average measured TRP of low, mid and high channel for laptop mounted equipment shall be higher than the average TRP requirement specified in this subclause. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in this subclause. Minimum TRP requirement is shown in the column “Min” on the requirement tables.
+
+$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$
+
+LME requirements in this clause are defined to be measured with laptop ground plane phantom as defined in TR 25.914 [6] subclauses 5.1.3 and 5.1.4.
+
+### 6.2.1 GSM
+
+LME TRP minimum performance requirements for GSM with laptop ground plane phantom in data transfer position are defined in Table 6.2.1-1.
+
+**Table 6.2.1-1: LME TRP minimum performance requirement for GSM in the data transfer position**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     | Power class 5 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| GSM 850        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| GSM 900        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| DCS 1800       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+| PCS 1900       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for USB plug-in devices.
+
+### 6.2.2 UTRA FDD
+
+LME TRP minimum performance requirements for UTRA FDD with laptop ground plane phantom in data transfer position are defined in Table 6.2.2-1.
+
+**Table 6.2.2-1: LME TRP minimum performance requirement for UTRA FDD in the data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |     | Power class 3bis |     | Power class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+| I              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| XIX            |               |               | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for USB plug-in devices.
+
+### 6.2.3 UTRA LCR TDD
+
+LME TRP minimum performance requirements for UTRA LCR TDD with laptop ground plane phantom in data transfer position are defined in Table 6.2.3-1.
+
+**Table 6.2.3-1: LME TRP minimum performance requirement for UTRA LCR TDD in the data transfer position**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM /UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+### 6.2.4 E-UTRA FDD
+
+### 6.2.5 E-UTRA TDD
+
+## 6.3 Minimum requirement for roaming bands for LEE
+
+The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in this subclause. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in this subclause. Minimum TRP requirement is shown in the column “Min” on the requirement tables.
+
+$$TRP_{min} = 10 \log \left[ \min \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$
+
+LEE requirements in this clause are defined to be measured as defined in TR 25.914 [6]: subclause 5.3.1 applies to notebook devices, and subclause 5.3.2 applies to tablet devices.
+
+### 6.3.1 GSM
+
+LEE TRP minimum performance requirements for GSM are defined in Tables 6.3.1-1 and 6.3.1-2.
+
+**Table 6.3.1-1: Notebook TRP minimum performance requirement for GSM in the data transfer position**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     | Power class 5 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| GSM 850        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| GSM 900        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| DCS 1800       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+| PCS 1900       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for notebook devices.
+
+Table 6.3.1-2: Tablet TRP minimum performance requirement for GSM in the data transfer position
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     | Power class 5 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| GSM 850        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| GSM 900        | -             | -   | -             | -   | -             | -   | TBD           | TBD | -             | -   |
+| DCS 1800       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+| PCS 1900       | TBD           | TBD | -             | -   | -             | -   | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices.
+
+### 6.3.2 UTRA FDD
+
+LEE TRP minimum performance requirements for UTRA FDD are defined in Tables 6.3.2-1 and 6.3.2-2.
+
+Table 6.3.2-1: Notebook TRP minimum performance requirement for UTRA FDD in the data transfers position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |      | Power class 3bis |     | Power class 4 |     |
+|----------------|---------------|---------------|---------------|------|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min  | Average          | Min | Average       | Min |
+| I              | -             | -             | 19,0          | 17,5 | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | 18,5          | 16,5 | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | 18,5          | 16,5 | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | 18,5          | 16,5 | TBD              | TBD | TBD           | TBD |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRP minimum performance requirements in table 6.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+Table 6.3.2-2: Tablet TRP minimum performance requirement for UTRA FDD in the data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 |      | Power class 3bis |     | Power class 4 |     |
+|----------------|---------------|---------------|---------------|------|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min  | Average          | Min | Average       | Min |
+| I              | -             | -             | 19            | 17,5 | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | 17            | 15,0 | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD  | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | 17            | 15,0 | TBD              | TBD | TBD           | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices with two antennas.
+
+### 6.3.3 UTRA LCR TDD
+
+LEE TRP minimum performance requirements for UTRA LCR TDD are defined in Tables 6.3.3-1 and 6.3.3-2.
+
+**Table 6.3.3-1: Notebook TRP minimum performance requirement for UTRA LCR TDD in the data transfer position**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM /UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+**Table 6.3.3-2: Tablet TRP minimum performance requirement for UTRA LCR TDD in the data transfer position**
+
+| Operating band | Power class 1 |     | Power class 2 |     | Power class 3 |     | Power class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM /UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+### 6.3.4 E-UTRA FDD
+
+LEE TRP minimum performance requirements for E-UTRA FDD are defined in Table 6.3.4-1 for Tablet devices.
+
+Table 6.3.4-1: Tablet TRP minimum requirements for E-UTRA FDD in the data transfer position
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |      | Power Class 4 |
+|----------------|---------------|---------------|---------------|------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)   |
+|                |               |               | Average       | Min  |               |
+| 1              |               |               | 18.5          | 17.0 |               |
+| 2              |               |               |               |      |               |
+| 3              |               |               | 18.5          | 17.0 |               |
+| 4              |               |               |               |      |               |
+| 5              |               |               |               |      |               |
+| 7              |               |               | 18.0          | 16.5 |               |
+| 8              |               |               |               |      |               |
+| 12             |               |               |               |      |               |
+| 13             |               |               |               |      |               |
+| 19             |               |               | 17.5          | 15.5 |               |
+| 20             |               |               | 17.5          | 15.5 |               |
+| 21             |               |               | 17.5          | 16.0 |               |
+| 28             |               |               |               |      |               |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+### 6.3.5 E-UTRA TDD
+
+# 7 Receiver total radiated sensitivity
+
+## 7.1 Minimum requirement for roaming bands for handheld UE
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in subclauses 7.1.1, 7.1.2 and 7.1.3. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head in case of beside the head phantom and beside the head and hand phantom positions. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+$$TRS_{average} = 10 \log \left[ 6 / \left( \frac{1}{10^{P_{left\_low}/10}} + \frac{1}{10^{P_{left\_mid}/10}} + \frac{1}{10^{P_{left\_high}/10}} + \frac{1}{10^{P_{right\_low}/10}} + \frac{1}{10^{P_{right\_mid}/10}} + \frac{1}{10^{P_{right\_high}/10}} \right) \right]$$
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in subclauses 7.1.1, 7.1.2 and 7.1.3. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+### 7.1.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2.
+
+#### 7.1.1.1 GSM
+
+Handheld MS TRS minimum performance requirements for GMSK in beside the head phantom position and the primary mechanical mode for TCH/FS at 2% class II (RBER) [3] are defined in Table 7.1.1.1-1.
+
+**Table 7.1.1.1-1: Handheld UE TRS minimum requirements for GSM roaming bands in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Unit | <REF <sub>10</sub> > |       |
+|----------------|------|----------------------|-------|
+|                |      | Average              | Max   |
+| GSM 850        | dBm  | -98                  | -95   |
+| GSM 900        | dBm  | -97                  | -94   |
+| DCS 1800       | dBm  | -99,5                | -96,5 |
+| PCS 1900       | dBm  | -98,5                | -95,5 |
+
+NOTE 1: For power class 1 and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.
+
+#### 7.1.1.2 UTRA FDD
+
+Handheld UE TRS minimum performance requirements for UTRA FDD in beside the head phantom position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.1.2-1.
+
+**Table 7.1.1.2-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>10</sub> > |     |
+|----------------|--------------|----------------------|-----|
+|                |              | Average              | Max |
+| I              | dBm/3,84 MHz | -101                 | -98 |
+| II             | dBm/3,84 MHz | -99                  | -96 |
+| III            | dBm/3,84 MHz | -98                  | -95 |
+| IV             | dBm/3,84 MHz | -101                 | -98 |
+| V              | dBm/3,84 MHz | -96                  | -93 |
+| VI             | dBm/3,84 MHz | -96                  | -93 |
+| VII            | dBm/3,84 MHz | -99                  | -96 |
+| VIII           | dBm/3,84 MHz | -96                  | -93 |
+| IX             | dBm/3,84 MHz | -100                 | -97 |
+| XIX            | dBm/3,84 MHz | -96                  | -93 |
+
+NOTE 1: For Power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF<sub>10</sub>> [average and min] shall apply for Band IX.  
+NOTE 3: Applicable for dual-mode GSM/UMTS.  
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>10</sub>> level of -98 dBm/3,84 MHz and max <REF<sub>10</sub>> level of -95 dBm/3,84 MHz shall apply for Band II.  
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>10</sub>> level of -100 dBm/3,84 MHz and max <REF<sub>10</sub>> level of -97 dBm/3,84 MHz shall apply for Band IV.
+
+#### 7.1.1.3 UTRA LCR TDD
+
+Handheld UE TRS minimum performance requirements for UTRA LCR FDD in beside the head phantom position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.1.3-1.
+
+**Table 7.1.1.3-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in beside the head phantom position and the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REF <sub>ior</sub> > |      |
+|--------------------------------------------------|--------------|-----------------------|------|
+|                                                  |              | Average               | Max  |
+| a                                                | dBm/1,28 MHz | -101                  | -100 |
+| b                                                | dBm/1,28 MHz | TBD                   | TBD  |
+| c                                                | dBm/1,28 MHz | TBD                   | TBD  |
+| d                                                | dBm/1,28 MHz | TBD                   | TBD  |
+| e                                                | dBm/1,28 MHz | -101                  | -100 |
+| f                                                | dBm/1,28 MHz | -101                  | -100 |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                       |      |
+
+### 7.1.2 Beside the head and hand phantoms position
+
+Beside the head and hand phantom position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.6.
+
+#### 7.1.2.1 UTRA FDD
+
+Handheld UE TRS minimum performance requirements for UTRA FDD in beside the head and hand phantoms position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.2.1-1.
+
+**Table 7.1.2.1-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band                                                                                                                                                                                           | Unit         | <REF <sub>ior</sub> > |     |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|-----|
+|                                                                                                                                                                                                          |              | Average               | Max |
+| I                                                                                                                                                                                                        | dBm/3,84 MHz | -101,00               | TBD |
+| II                                                                                                                                                                                                       | dBm/3,84 MHz | -99,00                | TBD |
+| III                                                                                                                                                                                                      | dBm/3,84 MHz | TBD                   | TBD |
+| IV                                                                                                                                                                                                       | dBm/3,84 MHz | TBD                   | TBD |
+| V                                                                                                                                                                                                        | dBm/3,84 MHz | -96,75                | TBD |
+| VI                                                                                                                                                                                                       | dBm/3,84 MHz | -96,75                | TBD |
+| VII                                                                                                                                                                                                      | dBm/3,84 MHz | TBD                   | TBD |
+| VIII                                                                                                                                                                                                     | dBm/3,84 MHz | -96,75                | TBD |
+| IX                                                                                                                                                                                                       | dBm/3,84 MHz | TBD                   | TBD |
+| XIX                                                                                                                                                                                                      | dBm/3,84 MHz | -96,75                | TBD |
+| NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.                                                                                                                |              |                       |     |
+| NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF <sub>ior</sub> > [average and min] shall apply for Band IX.                   |              |                       |     |
+| NOTE 3: Applicable for dual-mode GSM/UMTS.                                                                                                                                                               |              |                       |     |
+| NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>ior</sub> > level of -98 dBm/3,84 MHz and max <REF <sub>ior</sub> > level of -95 dBm/3,84 MHz shall apply for Band II.  |              |                       |     |
+| NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>ior</sub> > level of -100 dBm/3,84 MHz and max <REF <sub>ior</sub> > level of -97 dBm/3,84 MHz shall apply for Band IV. |              |                       |     |
+| NOTE 6: Applicable for devices narrower than 72mm as defined in TR 25.914.                                                                                                                               |              |                       |     |
+| NOTE 7: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation).                                                                            |              |                       |     |
+
+#### 7.1.2.2 UTRA LCR TDD
+
+Handheld UE TRS minimum performance requirements for UTRA LCR TDD in beside the head and hand phantoms position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.2.2-1.
+
+**Table 7.1.2.2-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REF $\hat{I}_{or}$ > |     |
+|--------------------------------------------------|--------------|-----------------------|-----|
+|                                                  |              | Average               | Max |
+| a                                                | dBm/1,28 MHz | TBD                   | TBD |
+| b                                                | dBm/1,28 MHz | TBD                   | TBD |
+| c                                                | dBm/1,28 MHz | TBD                   | TBD |
+| d                                                | dBm/1,28 MHz | TBD                   | TBD |
+| e                                                | dBm/1,28 MHz | TBD                   | TBD |
+| f                                                | dBm/1,28 MHz | TBD                   | TBD |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                       |     |
+
+#### 7.1.2.3 E-UTRA FDD
+
+#### 7.1.2.4 E-UTRA TDD
+
+### 7.1.3 Hand phantom browsing mode position
+
+Hand phantom browsing mode position is defined in TR 25.914 [6] subclauses 5.1.5 and 5.1.7.
+
+#### 7.1.3.1 UTRA FDD
+
+Handheld UE TRS minimum performance requirements for UTRA FDD in hand phantom browsing mode position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.3.1-1.
+
+**Table 7.1.3.1-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band                                                                                                                                                                                                  | Unit         | <REF $\hat{I}_{or}$ > |     |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|-----|
+|                                                                                                                                                                                                                 |              | Average               | Max |
+| I                                                                                                                                                                                                               | dBm/3,84 MHz | TBD                   | TBD |
+| II                                                                                                                                                                                                              | dBm/3,84 MHz | TBD                   | TBD |
+| III                                                                                                                                                                                                             | dBm/3,84 MHz | TBD                   | TBD |
+| IV                                                                                                                                                                                                              | dBm/3,84 MHz | TBD                   | TBD |
+| V                                                                                                                                                                                                               | dBm/3,84 MHz | TBD                   | TBD |
+| VI                                                                                                                                                                                                              | dBm/3,84 MHz | TBD                   | TBD |
+| VII                                                                                                                                                                                                             | dBm/3,84 MHz | TBD                   | TBD |
+| VIII                                                                                                                                                                                                            | dBm/3,84 MHz | TBD                   | TBD |
+| IX                                                                                                                                                                                                              | dBm/3,84 MHz | TBD                   | TBD |
+| XIX                                                                                                                                                                                                             | dBm/3,84 MHz | TBD                   | TBD |
+| <b>NOTE 1:</b> For power class 3, 3bis and 4 this shall be achieved at the maximum output power.                                                                                                                |              |                       |     |
+| <b>NOTE 2:</b> For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF $\hat{I}_{or}$ > [average and min] shall apply for Band IX.                   |              |                       |     |
+| <b>NOTE 3:</b> Applicable for dual-mode GSM/UMTS.                                                                                                                                                               |              |                       |     |
+| <b>NOTE 4:</b> For the UE which supports DB-DC-HSDPA configuration 2, average <REF $\hat{I}_{or}$ > level of -98 dBm/3,84 MHz and max <REF $\hat{I}_{or}$ > level of -95 dBm/3,84 MHz shall apply for Band II.  |              |                       |     |
+| <b>NOTE 5:</b> For the UE which supports DB-DC-HSDPA configuration 2, average <REF $\hat{I}_{or}$ > level of -100 dBm/3,84 MHz and max <REF $\hat{I}_{or}$ > level of -97 dBm/3,84 MHz shall apply for Band IV. |              |                       |     |
+
+#### 7.1.3.2 UTRA LCR TDD
+
+Handheld UE TRS minimum performance requirements for UTRA LCR TDD in hand phantom browsing mode position and the primary mechanical mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.1.3.2-1.
+
+**Table 7.1.3.2-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band                                   | Unit         | <REF <sub>ior</sub> > |     |
+|--------------------------------------------------|--------------|-----------------------|-----|
+|                                                  |              | Average               | Max |
+| a                                                | dBm/1,28 MHz | TBD                   | TBD |
+| b                                                | dBm/1,28 MHz | TBD                   | TBD |
+| c                                                | dBm/1,28 MHz | TBD                   | TBD |
+| d                                                | dBm/1,28 MHz | TBD                   | TBD |
+| e                                                | dBm/1,28 MHz | TBD                   | TBD |
+| f                                                | dBm/1,28 MHz | TBD                   | TBD |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                       |     |
+
+#### 7.1.3.3 E-UTRA FDD
+
+#### 7.1.3.4 E-UTRA TDD
+
+## 7.2 Minimum requirement for roaming bands for LME
+
+The average measured TRS of low, mid and high channel for laptop mounted equipment shall be lower than average TRS requirement specified in this subclause. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+$$TRS_{average} = 10 \log \left[ 3 / \left( \frac{1}{10^{P_{low}/10}} + \frac{1}{10^{P_{mid}/10}} + \frac{1}{10^{P_{high}/10}} \right) \right]$$
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in this subclause. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$
+
+### 7.2.1 GSM
+
+LME TRS minimum performance requirements for GPRS PDTCH/CS1 at 10% BLER [3] with laptop ground plane phantom in data transfer position are defined in Table 7.2.1-1.
+
+**Table 7.2.1-1: LME TRS minimum requirements for GSM in data transfer position**
+
+| Operating band                                                                                                                                                                   | Unit | <REF <sub>ior</sub> > |     |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----------------------|-----|
+|                                                                                                                                                                                  |      | Average               | Max |
+| GSM 850                                                                                                                                                                          | dBm  | TBD                   | TBD |
+| GSM 900                                                                                                                                                                          | dBm  | TBD                   | TBD |
+| DCS 1800                                                                                                                                                                         | dBm  | TBD                   | TBD |
+| PCS 1900                                                                                                                                                                         | dBm  | TBD                   | TBD |
+| NOTE 1: For power class 1 and 4 this shall be achieved at the maximum output power.<br>NOTE 2: Applicable for dual-mode GSM/UMTS.<br>NOTE 3: Applicable for USB plug-in devices. |      |                       |     |
+
+### 7.2.2 UTRA FDD
+
+LME TRS minimum performance requirements for UTRA FDD with laptop ground plane phantom in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.2.2-1. [The values in the tables are  $\hat{I}_{or}$  with no interference.]
+
+Table 7.2.2-1: LME TRS minimum requirements for UTRA FDD in data transfer position
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| I              | dBm/3,84 MHz | TBD                   | TBD |
+| II             | dBm/3,84 MHz | TBD                   | TBD |
+| III            | dBm/3,84 MHz | TBD                   | TBD |
+| IV             | dBm/3,84 MHz | TBD                   | TBD |
+| V              | dBm/3,84 MHz | TBD                   | TBD |
+| VI             | dBm/3,84 MHz | TBD                   | TBD |
+| VII            | dBm/3,84 MHz | TBD                   | TBD |
+| VIII           | dBm/3,84 MHz | TBD                   | TBD |
+| IX             | dBm/3,84 MHz | TBD                   | TBD |
+| XIX            | dBm/3,84 MHz | TBD                   | TBD |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for USB plug-in devices.
+
+### 7.2.3 UTRA LCR TDD
+
+LME TRS minimum performance requirements for UTRA LCR TDD with laptop ground plane phantom in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Table 7.2.3-1. [The values in the tables are  $\hat{I}or$  with no interference.]
+
+Table 7.2.3-1: LME TRS minimum requirements for UTRA LCR TDD in data transfer position
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| a              | dBm/1,28 MHz | TBD                   | TBD |
+| b              | dBm/1,28 MHz | TBD                   | TBD |
+| c              | dBm/1,28 MHz | TBD                   | TBD |
+| d              | dBm/1,28 MHz | TBD                   | TBD |
+| e              | dBm/1,28 MHz | TBD                   | TBD |
+| f              | dBm/1,28 MHz | TBD                   | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+### 7.2.4 E-UTRA FDD
+
+### 7.2.5 E-UTRA TDD
+
+## 7.3 Minimum requirement for roaming bands for LEE
+
+The average measured TRS of low, mid and high channel for laptop embedded equipment shall be lower than average TRS requirements specified in this subclause. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+$$TRS_{average} = 10 \log \left[ 3 / \left( \frac{1}{10^{P_{low}/10}} + \frac{1}{10^{P_{mid}/10}} + \frac{1}{10^{P_{high}/10}} \right) \right]$$
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in this subclause. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{low}/10}, 10^{P_{mid}/10}, 10^{P_{high}/10} \right) \right]$$
+
+### 7.3.1 GSM
+
+LEE TRS minimum performance requirements for GPRS PDTCH/CS1 at 10% BLER [3] are defined in Tables 7.3.1-1 and 7.3.1-2.
+
+**Table 7.3.1-1: Notebook TRS minimum requirements for GSM in data transfer position**
+
+| Operating band | Unit | <REF $\hat{I}_{or}$ > |     |
+|----------------|------|-----------------------|-----|
+|                |      | Average               | Max |
+| GSM 850        | dBm  | TBD                   | TBD |
+| GSM 900        | dBm  | TBD                   | TBD |
+| DCS 1800       | dBm  | TBD                   | TBD |
+| PCS 1900       | dBm  | TBD                   | TBD |
+
+NOTE 1: For power class 1 and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for notebook devices.
+
+**Table 7.3.1-2: Tablet TRS minimum requirements for GSM in data transfer position**
+
+| Operating band | Unit | <REF $\hat{I}_{or}$ > |     |
+|----------------|------|-----------------------|-----|
+|                |      | Average               | Max |
+| GSM 850        | dBm  | TBD                   | TBD |
+| GSM 900        | dBm  | TBD                   | TBD |
+| DCS 1800       | dBm  | TBD                   | TBD |
+| PCS 1900       | dBm  | TBD                   | TBD |
+
+NOTE 1: For power class 1 and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for tablet devices.
+
+### 7.3.2 UTRA FDD
+
+LEE TRS minimum performance requirements for UTRA FDD in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Tables 7.3.2-1 and 7.3.3-2. [The values in the tables are  $\hat{I}_{or}$  with no interference.]
+
+**Table 7.3.2-1: Notebook TRS minimum requirements for UTRA FDD in data transfer position**
+
+| Operating band | Unit         | <REF $\hat{I}_{or}$ > |        |
+|----------------|--------------|-----------------------|--------|
+|                |              | Average               | Max    |
+| I              | dBm/3,84 MHz | -103,5                | -102,0 |
+| II             | dBm/3,84 MHz | TBD                   | TBD    |
+| III            | dBm/3,84 MHz | TBD                   | TBD    |
+| IV             | dBm/3,84 MHz | TBD                   | TBD    |
+| V              | dBm/3,84 MHz | TBD                   | TBD    |
+| VI             | dBm/3,84 MHz | -101,5                | -99,5  |
+| VII            | dBm/3,84 MHz | TBD                   | TBD    |
+| VIII           | dBm/3,84 MHz | -101,5                | -99,5  |
+| IX             | dBm/3,84 MHz | TBD                   | TBD    |
+| XIX            | dBm/3,84 MHz | -101,5                | -99,5  |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 3: Applicable for notebook devices.
+
+NOTE: TRS minimum performance requirements in table 7.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table 7.3.2-2: Tablet TRS minimum requirements for UTRA FDD in data transfer position**
+
+| Operating band | Unit         | <REFÎ <sub>or</sub> > |         |
+|----------------|--------------|-----------------------|---------|
+|                |              | Average               | Max     |
+| I              | dBm/3,84 MHz | -105,75               | -104,25 |
+| II             | dBm/3,84 MHz | TBD                   | TBD     |
+| III            | dBm/3,84 MHz | TBD                   | TBD     |
+| IV             | dBm/3,84 MHz | TBD                   | TBD     |
+| V              | dBm/3,84 MHz | -103                  | -101,0  |
+| VI             | dBm/3,84 MHz | TBD                   | TBD     |
+| VII            | dBm/3,84 MHz | TBD                   | TBD     |
+| VIII           | dBm/3,84 MHz | TBD                   | TBD     |
+| IX             | dBm/3,84 MHz | TBD                   | TBD     |
+| XIX            | dBm/3,84 MHz | -103                  | -101,0  |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for tablet devices with two antennas.
+
+### 7.3.3 UTRA LCR TDD
+
+LEE TRS minimum performance requirements for UTRA LCR TDD in data transfer position mode for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of [2] are defined in Tables 7.3.3-1 and 7.3.2-2. [The values in the tables are for with no interference.]
+
+**Table 7.3.3-1: LEE TRS minimum requirements for UTRA LCR TDD in data transfer position**
+
+| Operating band | Unit         | <REFÎ <sub>or</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| a              | dBm/1,28 MHz | TBD                   | TBD |
+| b              | dBm/1,28 MHz | TBD                   | TBD |
+| c              | dBm/1,28 MHz | TBD                   | TBD |
+| d              | dBm/1,28 MHz | TBD                   | TBD |
+| e              | dBm/1,28 MHz | TBD                   | TBD |
+| f              | dBm/1,28 MHz | TBD                   | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+**Table 7.3.3-2: Tablet TRS minimum requirements for UTRA LCR TDD in data transfer position**
+
+| Operating band | Unit         | <REFÎ <sub>or</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| a              | dBm/1,28 MHz | TBD                   | TBD |
+| b              | dBm/1,28 MHz | TBD                   | TBD |
+| c              | dBm/1,28 MHz | TBD                   | TBD |
+| d              | dBm/1,28 MHz | TBD                   | TBD |
+| e              | dBm/1,28 MHz | TBD                   | TBD |
+| f              | dBm/1,28 MHz | TBD                   | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+### 7.3.4 E-UTRA FDD
+
+LEE TRS minimum performance requirements for E-UTRA FDD in data transfer position mode for throughput  $\geq 95\%$  of the maximum throughput of the reference measurement channels as specified in section 7.3 of TS 36.521-1 [9] and Annex A of TS 36.521-1 [9] are defined in Table 7.3.4-1 for Tablet devices.
+
+Table 7.3.4-1: Tablet TRS minimum requirements for E-UTRA FDD in data transfer position
+
+| Operating band | Channel bandwidth | Sensitivity (dBm) |        |
+|----------------|-------------------|-------------------|--------|
+|                |                   | Average           | Max    |
+| 1              | 10 MHz            | -93.75            | -92.25 |
+| 2              | 10 MHz            |                   |        |
+| 3              | 10 MHz            | -95.0             | -93.5  |
+| 4              | 10 MHz            |                   |        |
+| 5              | 10 MHz            |                   |        |
+| 7              | 10 MHz            | -93.5             | -92.0  |
+| 8              | 10 MHz            |                   |        |
+| 12             | 10 MHz            |                   |        |
+| 13             | 10 MHz            |                   |        |
+| 19             | 10 MHz            | -91.5             | -89.5  |
+| 20             | 10 MHz            | -92.5             | -90.5  |
+| 21             | 15 MHz            | -90.0             | -88.5  |
+| 28             | 10 MHz            |                   |        |
+| 32             | 10 MHz            |                   |        |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+### 7.3.5 E-UTRA TDD
+
+# 8 Receiver total radiated multi-antenna sensitivity
+
+## 8.1 Minimum requirement for roaming bands for handheld UE
+
+### 8.1.1 Free Space
+
+Requirements in this section are stated for the free space configuration, are applicable to handheld devices, and are not applicable to wrist-worn devices.
+
+For the reference MPAC methodology and the harmonized RTS methodology defined in [7], the average TRMS of free space data mode portrait (FS\_DMP), free space data mode landscape (FSDML), and free space data mode screen up (FS\_DMSU), as defined in Annex E of TR 37.977 [7], when measured at the mid channel shall be lower than the average TRMS requirements specified in subclauses 8.1.1.1 and 8.1.1.2. The averaging shall be done in linear scale for the TRMS results at these DUT positions. Two average TRMS quantities are calculated from sensitivity measurements at 70% and 95% throughput, respectively. Average TRMS requirement are shown in the column “Average, 70” and “Average, 95” on the requirement tables.
+
+$$TRMS_{average,70} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,70/10}}} + \frac{1}{10^{S_{FS\_DML,70/10}}} + \frac{1}{10^{S_{FS\_DMSU,70/10}}} \right) \right]$$
+
+$$TRMS_{average,95} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,95/10}}} + \frac{1}{10^{S_{FS\_DML,95/10}}} + \frac{1}{10^{S_{FS\_DMSU,95/10}}} \right) \right]$$
+
+Where
+
+$$S_{MODE,x} = 10\log \left[ 12 / \left( \frac{1}{10^{P_{MODE,x,0/10}}} + \frac{1}{10^{P_{MODE,x,1/10}}} + \dots + \frac{1}{10^{P_{MODE,x,11/10}}} \right) \right]$$
+
+Such that *MODE* is one of {*FS\_DMP*, *FS\_DML*, *FS\_DMSU*}, *x* is one of {70, 95}, and {*P<sub>MODE,x,0</sub>*, ..., *P<sub>MODE,x,11</sub>*} are the measured sensitivity values at each azimuth position.
+
+For the reference MPAC methodology and the harmonized RTS methodology defined in [7], if 1 azimuth position does not result in a defined measured sensitivity at 70% or 95% throughput, *S<sub>MODE,70</sub>* or *S<sub>MODE,95</sub>* are calculated using the 11 measured sensitivities and the maximum downlink RS-EPRE *P<sub>RS-EPRE-MAX</sub>* (substitution approach) for the one missing
+
+result. If 2 azimuth positions do not result in a defined measured sensitivity at 95% throughput,  $S_{MODE,95}$  is calculated using the 10 measured sensitivities and  $P_{RS-EPRE-MAX}$  for the two missing results. If more azimuth positions result in undefined values for measured sensitivity at the 70% and/or 95% throughput, then the TRMS requirement for the corresponding throughput levels has not been met by such a device.  $P_{RS-EPRE-MAX}$  is defined as -80 dBm/15 kHz and is the maximum downlink RS-EPRE supported by the test system.
+
+#### 8.1.1.1 E-UTRA FDD
+
+Handheld UE TRMS minimum performance requirements for E-UTRA FDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [7] are defined in Table 8.1.1.1-1.
+
+**Table 8.1.1.1-1: Handheld UE TRMS minimum requirements for E-UTRA FDD roaming bands in free space and the primary mechanical mode**
+
+|                                               |            | Test 1                |             |
+|-----------------------------------------------|------------|-----------------------|-------------|
+| Channel Model as defined in clause 8.2 in [7] |            | SCME urban micro-cell |             |
+| Operating band                                | Unit       | <REFI <sub>or</sub> > |             |
+|                                               |            | Average, 70           | Average, 95 |
+| 1                                             | dBm/15 kHz | -94.75                | -92.75      |
+| 2                                             | dBm/15 kHz | TBD                   | TBD         |
+| 3                                             | dBm/15 kHz | -93.75                | -91.75      |
+| 4                                             | dBm/15 kHz | TBD                   | TBD         |
+| 5                                             | dBm/15 kHz | -91.5                 | -89.5       |
+| 7                                             | dBm/15 kHz | -92.5                 | -90.5       |
+| 8                                             | dBm/15 kHz | TBD                   | TBD         |
+| 12                                            | dBm/15 kHz | TBD                   | TBD         |
+| 13                                            | dBm/15 kHz | TBD                   | TBD         |
+| 19                                            | dBm/15 kHz | -91.5                 | -89.5       |
+| 20                                            | dBm/15 kHz | TBD                   | TBD         |
+| 28                                            | dBm/15 kHz | TBD                   | TBD         |
+| 32 (1)                                        | dBm/15 kHz | TBD                   | TBD         |
+
+NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell.
+
+NOTE 2: Applicability for devices supporting 4-receiver architectures is not confirmed.
+
+#### 8.1.1.2 E-UTRA TDD
+
+Handheld UE TRMS minimum performance requirements for E-UTRA TDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [7] are defined in Table 8.1.1.2-1.
+
+**Table 8.1.1.2-1: Handheld UE TRMS minimum requirements for E-UTRA TDD roaming bands in free space and the primary mechanical mode**
+
+|                                                      |             | <b>Test 1</b>                    |                    |
+|------------------------------------------------------|-------------|----------------------------------|--------------------|
+| <b>Channel Model as defined in clause 8.2 in [7]</b> |             | <b>SCME urban micro-cell</b>     |                    |
+| <b>Operating band</b>                                | <b>Unit</b> | <b>&lt;REF<sub>ior</sub>&gt;</b> |                    |
+|                                                      |             | <b>Average, 70</b>               | <b>Average, 95</b> |
+| 38                                                   | dBm/15 kHz  | -95.5                            | -93.5              |
+| 39                                                   | dBm/15 kHz  | TBD                              | TBD                |
+| 40                                                   | dBm/15 kHz  | TBD                              | TBD                |
+| 41                                                   | dBm/15 kHz  | -95.5                            | -93.5              |
+| 42                                                   | dBm/15 kHz  | TBD                              | TBD                |
+| 46 (1,2)                                             | dBm/15 kHz  | TBD                              | TBD                |
+
+NOTE 1: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3
+
+NOTE 2: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured.
+
+NOTE 3: Applicability for devices supporting 4-receiver architectures is not confirmed.
+
+# --- Annex A (normative): Environmental conditions
+
+## A.1 General
+
+This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled.
+
+---
+
+## A.2 Environmental requirements
+
+The requirements in this clause apply to all types of UE(s) and MS(s).
+
+### A.2.2 Temperature
+
+All the OTA requirements are applicable in room temperature e.g. 25°C.
+
+### A.2.3 Voltage
+
+The UE or MS shall be equipped with a real battery that is fully charged (in the beginning of the Test).
+
+# Annex B (informative): Recommended performance
+
+## B.1 General
+
+This annex introduces the concept of recommended OTA performance for operating bands. This requirement is not mandatory but is recommended.
+
+The concept of recommended performance is to ensure that UE/MS OTA performance is maximised in order to improve user experience and network performance. It is recognised that the ability to meet the recommended performance depends on the number of frequency bands supported by the UE/MS.
+
+## B.2 Transmitter total radiated power
+
+The OTA TRP performance for GSM, UTRA and E-UTRA should be greater or equal than the recommended values in this clause.
+
+### B.2.1 Recommended performance for handheld UE
+
+#### B.2.1.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2.
+
+##### B.2.1.1.1 GSM
+
+**Table B.2.1.1.1-1: Handheld UE TRP recommended performance for GSM in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 4 | Power class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | Average       | Average       | Average       | Average       | Average       |
+| GSM 850        | -             | -             | -             | 24            | -             |
+| GSM 900        | -             | -             | -             | 24            | -             |
+| DCS 1800       | 24            | -             | -             | -             | -             |
+| PCS 1900       | 24            | -             | -             | -             | -             |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+##### B.2.1.1.2 UTRA FDD
+
+**Table B.2.1.1.2-1: Handheld UE TRP recommended performance for UTRA FDD in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | +18           | +18              | +16           |
+| II             | -             | -             | +18           | +18              | +16           |
+| III            | -             | -             | +18           | +18              | +16           |
+| IV             | -             | -             | +18           | +18              | +16           |
+| V              | -             | -             | +14           | +14              | +12           |
+| VI             | -             | -             | +14,5         | +14,5            | +12,5         |
+| VII            | -             | -             | +18           | +18              | +16           |
+| VIII           | -             | -             | +15           | +15              | +13           |
+| IX             | -             | -             | +18           | +18              | +16           |
+| XIX            | -             | -             | +14,5         | +14,5            | +12,5         |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+##### B.2.1.1.3 UTRA LCR TDD
+
+**Table B.2.1.1.3-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | +18           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | +18           | -             | -                | -             |
+| f              | -             | +18           | -             | -                | -             |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+#### B.2.1.2 Beside the head and hand phantoms position
+
+##### B.2.1.2.1 UTRA FDD
+
+**Table B.2.1.2.1-1: Handheld UE TRP recommended performance for UTRA FDD beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               |               | Average       | Average          | Average       |
+| I              | -             | -             | 16,25         | TBD              | TBD           |
+| II             | -             | -             | 16,25         | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | 12,40         | TBD              | TBD           |
+| VI             | -             | -             | 12,40         | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | 12,40         | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 12,40         | TBD              | TBD           |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914.  
+NOTE 3: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation).
+
+##### B.2.1.2.2 UTRA LCR TDD
+
+**Table B.2.1.2.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               | Average       |               |                  |               |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+##### B.2.1.2.3 E-UTRA FDD
+
+##### B.2.1.2.4 E-UTRA TDD
+
+#### B.2.1.3 Hand phantom browsing mode position
+
+##### B.2.1.3.1 UTRA FDD
+
+Table B.2.1.3.1-1: Handheld UE TRP recommended performance for UTRA FDD in the hand phantom browsing mode position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               |               | Average       | Average          | Average       |
+| I              | -             | -             | TBD           | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | TBD           | TBD              | TBD           |
+| VI             | -             | -             | TBD           | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | TBD           | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | TBD           | TBD              | TBD           |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+##### B.2.1.3.2 UTRA LCR TDD
+
+Table B.2.1.3.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in the hand phantom browsing mode position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               | Average       |               |                  |               |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+Note : Applicable for dual-mode GSM/UTRA LCR TDD.
+
+##### B.2.1.3.3 E-UTRA FDD
+
+##### B.2.1.3.4 E-UTRA TDD
+
+### B.2.2 Recommended performance for LME
+
+#### B.2.2.1 GSM
+
+Table B.2.2.1-1: LME TRP recommended performance for GSM in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 4 | Power class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | Average       | Average       | Average       | Average       | Average       |
+| GSM 850        | -             | -             | -             | TBD           | -             |
+| GSM 900        | -             | -             | -             | TBD           | -             |
+| DCS 1800       | TBD           | -             | -             | -             | -             |
+| PCS 1900       | TBD           | -             | -             | -             | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for USB plug-in devices.
+
+#### B.2.2.2 UTRA FDD
+
+Table B.2.2.2-1: LME TRP recommended performance for UTRA FDD in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | TBD           | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | TBD           | TBD              | TBD           |
+| VI             | -             | -             | TBD           | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | TBD           | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | TBD           | TBD              | TBD           |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for USB plug-in devices.
+
+#### B.2.2.3 UTRA LCR TDD
+
+Table B.2.2.3-1: LME TRP recommended performance for UTRA LCR TDD in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+#### B.2.2.4 E-UTRA FDD
+
+Table B.2.2.4-1: Tablet TRP recommended performance for E-UTRA FDD in the data transfer position
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 | Power Class 4 |
+|----------------|---------------|---------------|---------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | Average       |               |               |               |
+| 1              |               |               | 21.0          |               |
+| 2              |               |               |               |               |
+| 3              |               |               | 20.5          |               |
+| 4              |               |               |               |               |
+| 5              |               |               |               |               |
+| 7              |               |               | 20.0          |               |
+| 8              |               |               |               |               |
+| 12             |               |               |               |               |
+| 13             |               |               |               |               |
+| 19             |               |               | 20.0          |               |
+| 20             |               |               | 19.5          |               |
+| 21             |               |               | 20.0          |               |
+| 28             |               |               |               |               |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+#### B.2.2.5 E-UTRA TDD
+
+### B.2.3 Recommended performance for LEE
+
+#### B.2.3.1 GSM
+
+Table B.2.3.1-1: Notebook TRP recommended performance for GSM in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 4 | Power class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | Average       | Average       | Average       | Average       | Average       |
+| GSM 850        | -             | -             | -             | TBD           | -             |
+| GSM 900        | -             | -             | -             | TBD           | -             |
+| DCS 1800       | TBD           | -             | -             | -             | -             |
+| PCS 1900       | TBD           | -             | -             | -             | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for notebook devices.
+
+Table B.2.3.1-2: Tablet TRP recommended performance for GSM in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 4 | Power class 5 |
+|----------------|---------------|---------------|---------------|---------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | Average       | Average       | Average       | Average       | Average       |
+| GSM 850        | -             | -             | -             | TBD           | -             |
+| GSM 900        | -             | -             | -             | TBD           | -             |
+| DCS 1800       | TBD           | -             | -             | -             | -             |
+| PCS 1900       | TBD           | -             | -             | -             | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices.
+
+#### B.2.3.2 UTRA FDD
+
+**Table B.2.3.2-1: Notebook TRP recommended performance for UTRA FDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | 21,5          | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | TBD           | TBD              | TBD           |
+| VI             | -             | -             | 21,0          | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | 21,0          | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 21,0          | TBD              | TBD           |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRP minimum performance requirements in table B.2.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table B.2.3.2-2: Tablet TRP recommended performance for UTRA FDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | 21,5          | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | 19,5          | TBD              | TBD           |
+| VI             | -             | -             | TBD           | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | TBD           | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 19,5          | TBD              | TBD           |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices with two antennas.
+
+#### B.2.3.3 UTRA LCR TDD
+
+**Table B.2.3.3-1: Notebook TRP recommended performance for UTRA LCR TDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+Table B.2.3.3-2: Tablet TRP recommended performance for UTRA LCR TDD in data transfer position
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+#### B.2.3.4 E-UTRA FDD
+
+#### B.2.3.5 E-UTRA TDD
+
+## B.3 Receiver total radiated sensitivity
+
+The OTA TRS performance for GSM, UTRA and E-UTRA should be lower or equal than the recommended values shown in this clause.
+
+### B.3.1 Recommended performance for handheld UE
+
+#### B.3.1.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in TR 25.914 [6] subclauses 5.1.1 and 5.1.2.
+
+##### B.3.1.1.1 GSM
+
+Table B.3.1.1.1-1: Handheld UE TRS recommended performance for GSM in beside the head phantom position and the primary mechanical mode.
+
+| Operating band | Unit | <REF <sub>1or</sub> ><br>Average |
+|----------------|------|----------------------------------|
+| GSM 850        | dBm  | -100,5                           |
+| GSM 900        | dBm  | -100,5                           |
+| DCS 1800       | dBm  | -103,5                           |
+| PCS 1900       | dBm  | -103,5                           |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+##### B.3.1.1.2 UTRA FDD
+
+Table B.3.1.1.2-1: Handheld UE TRS recommended performance for FDD in beside the head phantom position for the primary mechanical mode
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |
+|----------------|--------------|-----------------------|
+| I              | dBm/3,84 MHz | -104                  |
+| II             | dBm/3,84 MHz | -102                  |
+| III            | dBm/3,84 MHz | -101                  |
+| IV             | dBm/3,84 MHz | -104                  |
+| V              | dBm/3,84 MHz | -99,5                 |
+| VI             | dBm/3,84 MHz | -101                  |
+| VII            | dBm/3,84 MHz | -102                  |
+| VIII           | dBm/3,84 MHz | -100                  |
+| IX             | dBm/3,84 MHz | -103                  |
+| XIX            | dBm/3,84 MHz | -101                  |
+
+NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -101 dBm/3.84 shall apply for Band II.
+
+NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -103 dBm/3.84 MHz shall apply for Band IV.
+
+##### B.3.1.1.3 UTRA LCR TDD
+
+Table B.3.1.1.3-1: Handheld UE TRS recommended performance for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode.
+
+| Operating band | Unit         | <REF <sub>ior</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| a              | dBm/1,28 MHz | -105                             |
+| b              | dBm/1,28 MHz | TBD                              |
+| c              | dBm/1,28 MHz | TBD                              |
+| d              | dBm/1,28 MHz | TBD                              |
+| e              | dBm/1,28 MHz | -105                             |
+| f              | dBm/1,28 MHz | -105                             |
+
+NOTE: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+#### B.3.1.2 Beside the head and hand phantoms position
+
+##### B.3.1.2.1 UTRA FDD
+
+**Table B.3.1.2.1-1: TRS recommended performance for UTRA FDD in the beside the head and hand phantoms position for the primary mechanical mode**
+
+| Operating band                                                                                                                                   | Unit         | <REF <sub>ior</sub> ><br>Average |
+|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------|
+| I                                                                                                                                                | dBm/3,84 MHz | -104,00                          |
+| II                                                                                                                                               | dBm/3,84 MHz | -102,00                          |
+| III                                                                                                                                              | dBm/3,84 MHz | TBD                              |
+| IV                                                                                                                                               | dBm/3,84 MHz | TBD                              |
+| V                                                                                                                                                | dBm/3,84 MHz | -99,75                           |
+| VI                                                                                                                                               | dBm/3,84 MHz | TBD                              |
+| VII                                                                                                                                              | dBm/3,84 MHz | TBD                              |
+| VIII                                                                                                                                             | dBm/3,84 MHz | -99,75                           |
+| IX                                                                                                                                               | dBm/3,84 MHz | TBD                              |
+| XIX                                                                                                                                              | dBm/3,84 MHz | TBD                              |
+| NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>ior</sub> > level of -101 dBm/3,84 shall apply for Band II.     |              |                                  |
+| NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>ior</sub> > level of -103 dBm/3,84 MHz shall apply for Band IV. |              |                                  |
+| NOTE 3: Applicable for devices narrower than 72mm as defined in TR 25.914                                                                        |              |                                  |
+| NOTE 4: Not applicable for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation)                     |              |                                  |
+
+##### B.3.1.2.2 UTRA LCR TDD
+
+**Table B.3.1.2.2-1: TRS recommended performance for UTRA LCR TDD in the beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REF <sub>ior</sub> ><br>Average |
+|--------------------------------------------------|--------------|----------------------------------|
+| a                                                | dBm/1,28 MHz | TBD                              |
+| b                                                | dBm/1,28 MHz | TBD                              |
+| c                                                | dBm/1,28 MHz | TBD                              |
+| d                                                | dBm/1,28 MHz | TBD                              |
+| e                                                | dBm/1,28 MHz | TBD                              |
+| f                                                | dBm/1,28 MHz | TBD                              |
+| NOTE: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                                  |
+
+##### B.3.1.2.3 E-UTRA FDD
+
+##### B.3.1.2.4 E-UTRA TDD
+
+#### B.3.1.3 Hand phantom browsing mode position
+
+##### B.3.1.3.1 UTRA FDD
+
+Table B.3.1.3.1-1: TRS recommended performance for UTRA FDD in hand phantom browsing mode position
+
+| Operating band | Unit         | <REF <sub>flor</sub> ><br>Average |
+|----------------|--------------|-----------------------------------|
+| I              | dBm/3,84 MHz | TBD                               |
+| II             | dBm/3,84 MHz | TBD                               |
+| III            | dBm/3,84 MHz | TBD                               |
+| IV             | dBm/3,84 MHz | TBD                               |
+| V              | dBm/3,84 MHz | TBD                               |
+| VI             | dBm/3,84 MHz | TBD                               |
+| VII            | dBm/3,84 MHz | TBD                               |
+| VIII           | dBm/3,84 MHz | TBD                               |
+| IX             | dBm/3,84 MHz | TBD                               |
+| XIX            | dBm/3,84 MHz | TBD                               |
+
+NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>flor</sub>> level of -101 dBm/3,84 shall apply for Band II.
+
+NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>flor</sub>> level of -103 dBm/3,84 MHz shall apply for Band IV.
+
+##### B.3.1.3.2 UTRA LCR TDD
+
+Table B.3.1.3.2-1: TRS recommended performance for UTRA LCR TDD in hand phantom browsing mode position
+
+| Operating band | Unit         | <REF <sub>flor</sub> ><br>Average |
+|----------------|--------------|-----------------------------------|
+| a              | dBm/1,28 MHz | TBD                               |
+| b              | dBm/1,28 MHz | TBD                               |
+| c              | dBm/1,28 MHz | TBD                               |
+| d              | dBm/1,28 MHz | TBD                               |
+| e              | dBm/1,28 MHz | TBD                               |
+| f              | dBm/1,28 MHz | TBD                               |
+
+NOTE: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+##### B.3.1.3.3 E-UTRA FDD
+
+##### B.3.1.3.4 E-UTRA TDD
+
+### B.3.2 Recommended performance for LME
+
+#### B.3.2.1 GSM
+
+Table B.3.2.1-1: LME TRS recommended performance for GSM in the data transfer position
+
+| Operating band | Unit | <REFI <sub>or</sub> ><br>Average |
+|----------------|------|----------------------------------|
+| GSM 850        | dBm  | TBD                              |
+| GSM 900        | dBm  | TBD                              |
+| DCS 1800       | dBm  | TBD                              |
+| PCS 1900       | dBm  | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for USB plug-in devices.
+
+#### B.3.2.2 UTRA FDD
+
+Table B.3.2.2-1: LME TRS recommended performance for UTRA FDD in the data transfer position
+
+| Operating band | Unit         | <REFI <sub>or</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| I              | dBm/3,84 MHz | TBD                              |
+| II             | dBm/3,84 MHz | TBD                              |
+| III            | dBm/3,84 MHz | TBD                              |
+| IV             | dBm/3,84 MHz | TBD                              |
+| V              | dBm/3,84 MHz | TBD                              |
+| VI             | dBm/3,84 MHz | TBD                              |
+| VII            | dBm/3,84 MHz | TBD                              |
+| VIII           | dBm/3,84 MHz | TBD                              |
+| IX             | dBm/3,84 MHz | TBD                              |
+| XIX            | dBm/3,84 MHz | TBD                              |
+
+NOTE: Applicable for USB plug-in devices.
+
+#### B.3.2.3 UTRA LCR TDD
+
+Table B.3.2.3-1: LME TRS recommended performance for UTRA LCR TDD in the data transfer position
+
+| Operating band | Unit         | <REFI <sub>or</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| a              | dBm/1,28 MHz | TBD                              |
+| b              | dBm/1,28 MHz | TBD                              |
+| c              | dBm/1,28 MHz | TBD                              |
+| d              | dBm/1,28 MHz | TBD                              |
+| e              | dBm/1,28 MHz | TBD                              |
+| f              | dBm/1,28 MHz | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+#### B.3.2.4 E-UTRA FDD
+
+#### B.3.2.5 E-UTRA TDD
+
+### B.3.3 Recommended performance for LEE
+
+#### B.3.3.1 GSM
+
+Table B.3.3.1-1: Notebook TRS recommended performance for GSM in the data transfer position
+
+| Operating band | Unit | <REFI <sub>or</sub> ><br>Average |
+|----------------|------|----------------------------------|
+| GSM 850        | dBm  | TBD                              |
+| GSM 900        | dBm  | TBD                              |
+| DCS 1800       | dBm  | TBD                              |
+| PCS 1900       | dBm  | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for notebook devices.
+
+Table B.3.3.1-2: Tablet TRS recommended performance for GSM in the data transfer position
+
+| Operating band | Unit | <REFI <sub>or</sub> ><br>Average |
+|----------------|------|----------------------------------|
+| GSM 850        | dBm  | TBD                              |
+| GSM 900        | dBm  | TBD                              |
+| DCS 1800       | dBm  | TBD                              |
+| PCS 1900       | dBm  | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices.
+
+#### B.3.3.2 UTRA FDD
+
+Table B.3.3.2-1: Notebook TRS recommended performance for UTRA FDD in the data transfer position
+
+| Operating band | Unit         | <REFI <sub>or</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| I              | dBm/3,84 MHz | -106.5                           |
+| II             | dBm/3,84 MHz | TBD                              |
+| III            | dBm/3,84 MHz | TBD                              |
+| IV             | dBm/3,84 MHz | TBD                              |
+| V              | dBm/3,84 MHz | TBD                              |
+| VI             | dBm/3,84 MHz | -104.5                           |
+| VII            | dBm/3,84 MHz | TBD                              |
+| VIII           | dBm/3,84 MHz | -104.5                           |
+| IX             | dBm/3,84 MHz | TBD                              |
+| XIX            | dBm/3,84 MHz | -104.5                           |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRS minimum performance requirements in table B.3.3.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+Table B.3.3.2-2: Tablet TRS recommended performance for UTRA FDD in the data transfer position
+
+| Operating band | Unit         | <REF <sub>lor</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| I              | dBm/3,84 MHz | -108,75                          |
+| II             | dBm/3,84 MHz | TBD                              |
+| III            | dBm/3,84 MHz | TBD                              |
+| IV             | dBm/3,84 MHz | TBD                              |
+| V              | dBm/3,84 MHz | -106,0                           |
+| VI             | dBm/3,84 MHz | TBD                              |
+| VII            | dBm/3,84 MHz | TBD                              |
+| VIII           | dBm/3,84 MHz | TBD                              |
+| IX             | dBm/3,84 MHz | TBD                              |
+| XIX            | dBm/3,84 MHz | -106,0                           |
+
+NOTE: Applicable for tablet devices with two antennas.
+
+#### B.3.3.3 UTRA LCR TDD
+
+Table B.3.3.3-1: Notebook TRS recommended performance for UTRA LCR TDD in the data transfer position
+
+| Operating band | Unit         | <REF <sub>lor</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| a              | dBm/1,28 MHz | TBD                              |
+| b              | dBm/1,28 MHz | TBD                              |
+| c              | dBm/1,28 MHz | TBD                              |
+| d              | dBm/1,28 MHz | TBD                              |
+| e              | dBm/1,28 MHz | TBD                              |
+| f              | dBm/1,28 MHz | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+Table B.3.3.3-2: Tablet TRS recommended performance for UTRA LCR TDD in the data transfer position
+
+| Operating band | Unit         | <REF <sub>lor</sub> ><br>Average |
+|----------------|--------------|----------------------------------|
+| a              | dBm/1,28 MHz | TBD                              |
+| b              | dBm/1,28 MHz | TBD                              |
+| c              | dBm/1,28 MHz | TBD                              |
+| d              | dBm/1,28 MHz | TBD                              |
+| e              | dBm/1,28 MHz | TBD                              |
+| f              | dBm/1,28 MHz | TBD                              |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+#### B.3.3.4 E-UTRA FDD
+
+Table B.3.3.4-1: Tablet TRS recommended performance for E-UTRA FDD in data transfer position
+
+| Operating band | Channel bandwidth | Sensitivity (dBm) |
+|----------------|-------------------|-------------------|
+|                |                   | Average           |
+| 1              | 10 MHz            | -96.0             |
+| 2              | 10 MHz            |                   |
+| 3              | 10 MHz            | -97.0             |
+| 4              | 10 MHz            |                   |
+| 5              | 10 MHz            |                   |
+| 7              | 10 MHz            | -95.75            |
+| 8              | 10 MHz            |                   |
+| 12             | 10 MHz            |                   |
+| 13             | 10 MHz            |                   |
+| 19             | 10 MHz            | -94.5             |
+| 20             | 10 MHz            | -94.5             |
+| 21             | 15 MHz            | -93.0             |
+| 28             | 10 MHz            |                   |
+| 32             | 10 MHz            |                   |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.
+
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+#### B.3.3.5 E-UTRA TDD
+
+# Annex C (informative): Change history
+
+| Change history |             |           |      |     |     |                                                                                                                                |               |
+|----------------|-------------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------|---------------|
+| Date           | Meeting     | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                | New version   |
+| 2014-03        | RAN4#70 bis | R4-141169 |      |     |     | TP to TS37.144 on adding tables of performance requirements for tablet devices                                                 | 0.1.0         |
+| 2015-04        | RAN4#74 bis | R4-151168 |      |     |     | TP to TS 37.144 on adding UTRA FDD LEE TRP/TRS requirements for Bands I and VIII                                               | 0.2.0         |
+| 2015-04        | RAN4#74 bis | R4-151215 |      |     |     | TP to TS 37.144 on a skeleton for MIMO OTA requirements                                                                        | 0.2.0         |
+| 2015-05        | RAN4#75     | R4-152459 |      |     |     | LEE requirement for UMTS Band VI and XIX                                                                                       | 0.3.0         |
+| 2016-02        | RAN4#78     | R4-161467 |      |     |     | TP for TS 37.144 Introduction of new TRP/TRS requirements                                                                      | 1.0.0         |
+| 2016-04        | RAN4#78 bis | R4-163122 |      |     |     | Addition of missing Tablet requirements                                                                                        | 1.1.0         |
+| 2016-05        | RAN4#79     | R4-164969 |      |     |     | TP to TS 37.144 UTRA handheld TRP/TRS agreements                                                                               | 2.0.0         |
+| 2016-06        | RAN#72      | R4-164811 |      |     |     | TP to TS 37.144 on MIMO OTA performance requirement structure                                                                  | 2.1.0         |
+| 2016-06        | RAN#72      | R4-164812 |      |     |     | TP to TS 37.144 on MIMO OTA test case parameters                                                                               | 2.1.0         |
+| 2016-06        | RAN#72      |           |      |     |     | TR approved by RAN plenary                                                                                                     | 13.0.0        |
+| 2016-08        | RAN#72      |           |      |     |     | Automatic upgrade to Rel-14 (Accidentally approved as Rel-13 at RAN#72, and later promoted with no technical change to Rel-14) | 14.0.0        |
+| 2016-09        | RP-73       | RP-161620 | 0001 | 1   | F   | Applicability of UTRA Requirements                                                                                             | 14.1.0        |
+| 2016-12        | RP-74       | RP-162397 | 0003 | -   | F   | Introduction of UTRA BHH TRP and TRS Requirements for Band VI and XIX                                                          | 14.2.0        |
+| 2016-12        | RP-74       | RP-162389 | 0004 | -   | F   | Correction of TRMS test case parameters                                                                                        | 14.2.0        |
+| 2017-06        | RP-76       | RP-171271 | 0005 | 1   | B   | Finalization of LTE Tablet TRP/TRS for bands 1, 3, 7, 19, 20, 21                                                               | 14.3.0        |
+| 2017-09        | RP-77       | RP-171931 | 0008 | 1   | F   | CR on maximum RS-EPRE level                                                                                                    | 14.4.0        |
+| 2017-09        | RP-77       | RP-171931 | 0011 |     | B   | MIMO OTA TRMS requirements for PS1                                                                                             | 14.4.0        |
+| 2017-12        | RAN#78      | RP-172583 | 0013 | 1   | F   | CR to 37.144 on handset TRMS                                                                                                   | 14.5.0        |
+| 2018-03        | RAN#79      | RP-180295 | 0014 | 1   | F   | Inclusion of TDD RTS as harmonized method in 37.144                                                                            | 14.6.0        |
+| 2018-06        | RAN#80      | RP-181115 | 0015 | 1   | F   | Inclusion of FDD RTS as harmonized method in 37.144                                                                            | 14.7.0        |
+| 2018-06        | SA#80       | -         | -    | -   | -   | Update to Rel-15 version (MCC)                                                                                                 | 15.0.0        |
+| 2020-06        | SA#88       | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                                                                 | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37171/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/Rel-16/37_series/37171/0019f09403376d6444ee323591fa2e98_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d1f378f6d8c9529fc5f6696c11375c31c76d540b
--- /dev/null
+++ b/marked/Rel-16/37_series/37171/0019f09403376d6444ee323591fa2e98_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3c371d8028a7a9d84cf8de4e384c7c4bc6a36a3881454703713b7b71b304953
+size 41021
diff --git a/marked/Rel-16/37_series/37171/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/37_series/37171/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6715f0b96a0f7454106a615e535ca532af69334
--- /dev/null
+++ b/marked/Rel-16/37_series/37171/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:411f742657614f5a583231bf458e23f3d285b83bb976dc61ed72898e47ee2bbc
+size 44606
diff --git a/marked/Rel-16/37_series/37171/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37171/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..43a92d4656c8cd42727409c30172b7d2437f1c9d
--- /dev/null
+++ b/marked/Rel-16/37_series/37171/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4af2e190722f87b7816621c0b4f22640b94114021716ea87dbb53c95cdb1daf3
+size 9376
diff --git a/marked/Rel-16/37_series/37171/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37171/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40e8e84b547ff4b72d19da92d24286bc7ee65c70
--- /dev/null
+++ b/marked/Rel-16/37_series/37171/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fa8755922fd37e8507acab0dbd78893f6367b37ee792cb9f06081cae21446db
+size 5829
diff --git a/marked/Rel-16/37_series/37171/raw.md b/marked/Rel-16/37_series/37171/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5e3aefb2002f9e4ccdb2a6723ce7d6976af128c
--- /dev/null
+++ b/marked/Rel-16/37_series/37171/raw.md
@@ -0,0 +1,1225 @@
+
+
+# 3GPP TS 37.171 V16.1.0 (2020-09)
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) performance requirements for Radio Access Technology (RAT) Independent Positioning Enhancements (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines of increasing length, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a red graphic element consisting of three curved lines of increasing length, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+# **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association  
+Bluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its members
+
+
+
+# Contents
+
+|                                                                          |    |
+|--------------------------------------------------------------------------|----|
+| Foreword .....                                                           | 5  |
+| 1 Scope.....                                                             | 7  |
+| 2 References.....                                                        | 7  |
+| 3 Definitions, abbreviations and test tolerances.....                    | 8  |
+| 3.1 Definitions.....                                                     | 8  |
+| 3.2 Abbreviations .....                                                  | 8  |
+| 3.3 Test tolerances.....                                                 | 8  |
+| 4 General.....                                                           | 8  |
+| 4.1 Introduction .....                                                   | 8  |
+| 4.2 MBS Measurements.....                                                | 8  |
+| 4.2.1 General .....                                                      | 8  |
+| 4.2.2 MBS measurement parameters.....                                    | 9  |
+| 4.2.3 MBS Measurement time.....                                          | 9  |
+| 4.2.4 RRC states for MBS measurements .....                              | 10 |
+| 4.2.5 MBS Measurement Error Definitions .....                            | 10 |
+| 4.3.2 WLAN Access Point Measurements.....                                | 10 |
+| 4.3.2.1 E-UTRAN FDD-WLAN Access Point Measurements .....                 | 10 |
+| 4.3.2.1.1 Introduction .....                                             | 10 |
+| 4.3.2.1.2 Measurement Requirements.....                                  | 11 |
+| 4.3.2.1.3 Measurement Reporting Delay.....                               | 11 |
+| 4.3.2.2 E-UTRAN TDD-WLAN Access Point Measurements.....                  | 11 |
+| 4.3.2.2.1 Introduction .....                                             | 11 |
+| 4.3.2.2.2 Measurement Requirements.....                                  | 11 |
+| 4.3.2.2.3 Measurement Reporting Delay.....                               | 12 |
+| 4.3.2.3 NR WLAN Access Point Measurements.....                           | 12 |
+| 4.3.2.3.1 Introduction .....                                             | 12 |
+| 4.3.2.3.2 Measurement Requirements.....                                  | 12 |
+| 4.3.2.3.3 Measurement Reporting Delay.....                               | 12 |
+| 4.4 Bluetooth Measurements.....                                          | 12 |
+| 4.4.1 General .....                                                      | 12 |
+| 4.4.2.1 Introduction.....                                                | 12 |
+| 4.4.2.2 Measurement Requirements .....                                   | 12 |
+| 4.4.2.3 Measurement Reporting Delay .....                                | 13 |
+| 4.4.2.4 NR Measurement Requirements.....                                 | 13 |
+| 4.4.2.5 NR Measurement Reporting Delay.....                              | 13 |
+| 5 MBS minimum performance requirements.....                              | 13 |
+| 5.1 General .....                                                        | 13 |
+| 5.2 Sensitivity.....                                                     | 13 |
+| 5.3 Nominal Accuracy.....                                                | 13 |
+| 5.4 Dynamic Range.....                                                   | 14 |
+| 5.5 Multipath.....                                                       | 14 |
+| 6 Bluetooth performance requirements.....                                | 15 |
+| 6.1 Introduction .....                                                   | 15 |
+| 6.1.1 Bluetooth RSSI Measurement .....                                   | 15 |
+| 6.1.1.1 Measurement Accuracy .....                                       | 15 |
+| 7 WLAN Access Point Identification minimum performance requirements..... | 15 |
+| 7.1 General .....                                                        | 15 |
+| 7.2 WLAN Access Point Identification under Sensitivity conditions.....   | 15 |
+| 7.3 WLAN Access Point Identification under Nominal conditions.....       | 15 |
+| 7.4 WLAN Access Point Identification under Dynamic Range conditions..... | 16 |
+
+|                               |                                                                                               |           |
+|-------------------------------|-----------------------------------------------------------------------------------------------|-----------|
+| <b>Annex A (normative):</b>   | <b>Test Case Requirements .....</b>                                                           | <b>17</b> |
+| A.1                           | Purpose of annex .....                                                                        | 17        |
+| A.2                           | Requirement classification for statistical testing .....                                      | 17        |
+| A.3                           | UE Measurement Procedures .....                                                               | 17        |
+| A.3.1                         | MBS Measurement reporting delay test case .....                                               | 17        |
+| A.3.1.1                       | Test Purpose and Environment .....                                                            | 17        |
+| A.3.1.2                       | Test Requirements .....                                                                       | 18        |
+| A.3.2                         | WLAN Access Point Identification and Reporting Delay .....                                    | 18        |
+| A.3.2.1                       | Void .....                                                                                    | 19        |
+| A.3.2.2                       | LTE-FDD: WLAN AP Identification and reporting delay under nominal conditions test .....       | 19        |
+| A.3.2.2.1                     | Test purpose and Environment .....                                                            | 19        |
+| A.3.2.2.2                     | Test Requirements .....                                                                       | 20        |
+| A.3.2.3                       | LTE-TDD: WLAN AP Identification and reporting delay under nominal conditions test .....       | 21        |
+| A.3.2.3.1                     | Test purpose and Environment .....                                                            | 21        |
+| A.3.2.3.2                     | Test Requirements .....                                                                       | 22        |
+| A.3.2.4                       | LTE-FDD: WLAN AP Identification and reporting delay under dynamic range conditions test ..... | 23        |
+| A.3.2.4.1                     | Test purpose and Environment .....                                                            | 23        |
+| A.3.2.4.2                     | Test Requirements .....                                                                       | 25        |
+| A.3.2.5                       | LTE-TDD: WLAN AP Identification and reporting delay under dynamic range conditions test ..... | 25        |
+| A.3.2.5.1                     | Test purpose and Environment .....                                                            | 25        |
+| A.3.2.5.2                     | Test Requirements .....                                                                       | 27        |
+| A.3.3                         | Bluetooth Measurement Requirements .....                                                      | 27        |
+| A.3.3.1                       | E-UTRAN FDD Bluetooth identification .....                                                    | 27        |
+| A.3.3.1.1                     | Test Purpose and Environment .....                                                            | 27        |
+| A.3.3.1.2                     | Test Requirements .....                                                                       | 28        |
+| A.3.3.2                       | E-UTRAN TDD Bluetooth identification .....                                                    | 29        |
+| A.3.3.2.1                     | Test Purpose and Environment .....                                                            | 29        |
+| A.3.3.2.2                     | Test Requirements .....                                                                       | 30        |
+| A.4                           | Measurement Performance Requirements .....                                                    | 31        |
+| A.4.1                         | General .....                                                                                 | 31        |
+| A.4.2                         | MBS Code Phase Measurement Accuracy Requirements in AWGN .....                                | 31        |
+| A.4.2.1                       | Test Purpose and Environment .....                                                            | 31        |
+| A.4.2.2                       | Test Requirements .....                                                                       | 32        |
+| A.4.3                         | MBS Code Phase Measurement Accuracy Requirements in Multipath .....                           | 32        |
+| A.4.3.1                       | Test Purpose and Environment .....                                                            | 32        |
+| A.4.3.2                       | Test Requirements .....                                                                       | 33        |
+| <b>Annex B (normative):</b>   | <b>Assistance data required for testing (Release 14 and beyond) .....</b>                     | <b>34</b> |
+| B.1                           | Introduction .....                                                                            | 34        |
+| B.2                           | MBS Assistance Data .....                                                                     | 34        |
+| <b>Annex C (informative):</b> | <b>Change history .....</b>                                                                   | <b>35</b> |
+
+# Foreword
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+- might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document establishes the minimum performance requirements for RAT-Independent Positioning Enhancements for FDD and TDD mode of UTRA, FDD and TDD mode of E-UTRA, and NR for the User Equipment (UE).
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [3] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)".
+- [4] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE)".
+- [5] 3GPP TS 36.942: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system scenarios".
+- [6] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
+- [7] ATIS-0500027: "Recommendations for Establishing Wide Scale Indoor Location Performance", May 2015.
+- [8] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions ".
+- [9] 3GPP TS 37.571-1: " User Equipment (UE) conformance specification for UE positioning; Part 1: Conformance test specification ".
+- [10] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Conformance testing".
+- [11] Void.
+- [12] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)".
+- [13] Bluetooth Special Interest Group: "Bluetooth Core Specification version 4.2", December 2014.
+- [14] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification".
+- [15] IEEE Standard 802.11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.
+
+[16] 3GPP TS 38.509: "5GS; Special conformance testing functions for User Equipment (UE)".
+
+# --- 3 Definitions, abbreviations and test tolerances
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                       |
+|--------|---------------------------------------|
+| AWGN   | Additive White Gaussian Noise         |
+| EPA    | Extended Pedestrian A                 |
+| E-UTRA | Evolved UMTS Terrestrial Radio Access |
+| FDD    | Frequency Division Duplex             |
+| LMF    | Location Management Function          |
+| LPP    | LTE Positioning Protocol              |
+| MBS    | Metropolitan Beacon System            |
+| NR     | New Radio Access                      |
+| RRC    | Radio Resource Control                |
+| RSSI   | Received Signal Strength Indicator    |
+| SS     | System Simulator                      |
+| TDD    | Time Division Duplex                  |
+| UE     | User Equipment                        |
+| UTRA   | UMTS Terrestrial Radio Access         |
+| WLAN   | Wireless Local Area Network           |
+
+## 3.3 Test tolerances
+
+The requirements given in the present document make no allowance for measurement uncertainty. The test specification 3GPP TS 37.571 -1 [9] will define test tolerances. These test tolerances are individually calculated for each test. The test tolerances are then added to the limits in the present document to create test limits. The measurement results are compared against the test limits as defined by the shared risk principle.
+
+Shared Risk is defined in ETSI TR 102 273-1-2 [2], subclause 6.5.
+
+# --- 4 General
+
+## 4.1 Introduction
+
+The present document defines the minimum performance requirements for UEs that support RAT Independent positioning technologies.
+
+## 4.2 MBS Measurements
+
+### 4.2.1 General
+
+Clause 4.2 describes the measurements performed by the UE for MBS positioning.
+
+### 4.2.2 MBS measurement parameters
+
+The measurement parameters are the MBS code phase measurements contained in the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION [3] by NR UE, the *TBS-MeasurementInformation* IE provided in LPP message of type PROVIDE LOCATION INFORMATION [3] by LTE UE, and the *UE Positioning AddPos measured results* IE in the MEASUREMENT REPORT message by UTRA UE [6].
+
+### 4.2.3 MBS Measurement time
+
+For NR, MBS measurement time is defined as the time starting from the moment that the UE has received the LPP [3] message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. For tests that involve sending MBS assistance data to the UE, the assistance data is sent prior to the REQUEST LOCATION INFORMATION message. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 38.509 [16] clause 5.6 for the purpose of deleting this information.
+
+For LTE, MBS measurement time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. For tests that involve sending MBS assistance data to the UE, the assistance data is sent prior to the REQUEST LOCATION INFORMATION message. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 36.509 [4] clause 6.9 for the purpose of deleting this information.
+
+For UTRA, MBS measurement time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the MBS measured results, and ending when the UE starts sending the measurement report containing the measured result on the Uu interface. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not reuse any information on measurements or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 34.109 [8] clause 5.4 for the purpose of deleting this information.
+
+The measurements for n MBS beacons, enabled across the slots of an MBS transmission period [7], shall be available at the UE by  $T_{\text{MBS\_meas}}$ , where  $T_{\text{MBS\_meas}}$  can be expressed as:
+
+$$T_{\text{MBS\_meas}} = \tau + 10 \times \text{ceil}(n/10) \times T_{\text{MBS\_TP}} + T_{\text{Proc}} \quad \text{ms}$$
+
+where
+
+$T_{\text{MBS\_meas}}$  is the total time for detecting and measuring n beacons
+
+$\tau$  is the elapsed time from the trigger of the measurement to the start of the first MBS transmission period
+
+$T_{\text{MBS\_TP}}$  is the MBS transmission period (1 second)
+
+$T_{\text{Proc}}$  is the processing time, an upper-bound for which can be given as  $10 \times \text{ceil}(n/10) \times T_{\text{MBS\_slot}}$  where  $T_{\text{MBS\_slot}}$  is the duration of a MBS slot (100 ms) with continuous MBS transmissions
+
+![Figure 4.2.3-1: MBS Measurement Time. A timeline diagram showing the sequence of events for MBS measurement. It starts with 'The last location request received by higher layers' (blue bar) and 'The last location request received by MBS physical layer' (red bar). A '1 sec boundary' is marked. Slot 1 contains 'Beacon 1' and Slot 2 contains 'Beacon 2'. The time between the start of Slot 1 and Slot 2 is 100 ms. The time between the start of Slot 2 and the next slot is also 100 ms. The time between the start of Slot 1 and the start of the n-th slot is n * T_MBS_TP. The time between the start of Slot 1 and the start of the measurement is T_MBS_meas. The time between the start of the measurement and the start of processing is T_Proc.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+The diagram illustrates the timing for MBS measurements. It shows a sequence of slots, Slot 1 and Slot 2, each containing a beacon (Beacon 1 and Beacon 2 respectively). A '1 sec boundary' is indicated. The time interval between the start of Slot 1 and Slot 2 is 100 ms. The time interval between the start of Slot 2 and the start of the next slot is also 100 ms. The time interval between the start of Slot 1 and the start of the n-th slot is labeled as  $n \cdot T_{MBS\_TP}$ . The time interval between the start of Slot 1 and the start of the measurement is labeled as  $T_{MBS\_meas}$ . The time interval between the start of the measurement and the start of processing is labeled as  $T_{Proc}$ . The time interval between the start of Slot 1 and the start of the next slot is also labeled as  $T_{MBS\_TP}$  (1 sec). The time interval between the start of Slot 1 and the start of the measurement is also labeled as  $T_{MBS\_meas}$ .
+
+Figure 4.2.3-1: MBS Measurement Time. A timeline diagram showing the sequence of events for MBS measurement. It starts with 'The last location request received by higher layers' (blue bar) and 'The last location request received by MBS physical layer' (red bar). A '1 sec boundary' is marked. Slot 1 contains 'Beacon 1' and Slot 2 contains 'Beacon 2'. The time between the start of Slot 1 and Slot 2 is 100 ms. The time between the start of Slot 2 and the next slot is also 100 ms. The time between the start of Slot 1 and the start of the n-th slot is n \* T\_MBS\_TP. The time between the start of Slot 1 and the start of the measurement is T\_MBS\_meas. The time between the start of the measurement and the start of processing is T\_Proc.
+
+Figure 4.2.3-1: MBS Measurement Time
+
+For this requirement, the assumption is that there is zero frequency offset for the beacons and the UEs have a minimum of 13 parallel correlators.
+
+The test case for MBS Measurement time requirements are specified in clause A.3.1.
+
+### 4.2.4 RRC states for MBS measurements
+
+For NR, the minimum MBS performance requirements specified in clause 5 apply for RRC\_CONNECTED state.
+
+For LTE, the minimum MBS performance requirements specified in clause 5 apply for RRC\_CONNECTED state.
+
+For UTRA, the minimum MBS performance requirements specified in clause 5 apply for different RRC states that include Cell\_DCH and Cell\_FACH.
+
+### 4.2.5 MBS Measurement Error Definitions
+
+The code phase measurement error is defined as the difference between the actual code phase for a given MBS beacon, and the estimated code phase for that beacon, as reported in the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION by NR UE [3], the *TBS-MeasurementInformation* IE provided in the LPP message of type PROVIDE LOCATION INFORMATION by LTE UE [3], and the *UE Positioning AddPos measured results* IE in the MEASUREMENT REPORT message by UTRA UE [6]. This difference has to then be adjusted for the measurement bias introduced by the UE clock to provide the final code phase measurement error.
+
+## 4.3 WLAN Measurements
+
+### 4.3.1 General
+
+Clause 4.3 defines the measurement requirements for the measurements performed by the UE for WLAN based positioning.
+
+### 4.3.2 WLAN Access Point Measurements
+
+Editor's note: In the WLAN requirements for NR, the NR clauses are separate from LTE, but it is FFS whether separate clauses are needed for SA NR and non-SA NR.
+
+#### 4.3.2.1 E-UTRAN FDD-WLAN Access Point Measurements
+
+##### 4.3.2.1.1 Introduction
+
+The requirements defined in section 4.3.2.1 shall apply provided the E-UTRA FDD UE has received *WLAN-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12].
+
+##### 4.3.2.1.2 Measurement Requirements
+
+The measurement delay reporting requirements for WLAN are defined in section 4.3.2.1.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7.
+
+##### 4.3.2.1.3 Measurement Reporting Delay
+
+For LTE, WLAN measurement time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response times specified for all test cases are based on new measurements unless otherwise stated, i.e. the UE shall not re use any information on measurements or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message 'RESET UE POSITIONING STORED INFORMATION' has been defined in TS 36.509 [4] clause 6.9 for the purpose of deleting this information. No WLAN assistance data is provided to the UE.
+
+The signals from the WLAN APs shall be available at the UE for the duration of the measurement time. Each WLAN AP transmits a beacon signal with a beacon interval smaller or equal to 102.4 ms. The beacon frames from different access points shall be transmitted in different time slots or non-overlapping frequency channels. The beacon frames have variable time duration of ~1ms.
+
+The WLAN Measurement Reporting Delay is given as:
+
+$$T_{\text{WLAN\_meas}} = \tau + 20 \text{ sec}$$
+
+where
+
+$T_{\text{WLAN\_meas}}$  is the total time for detecting and measuring the WLAN Access Points
+
+$\tau$  is the elapsed time from the trigger of the measurement to the start of the first WLAN transmission period and is shown in Figure 4.3.2.1.3-1.
+
+![Figure 4.3.2.1.3-1: WLAN Measurement Time diagram. The diagram shows a timeline starting with two triggers: 'The last location request received by higher layers' (blue bar) and 'The last location request received by WLAN physical layer' (red bar). The time interval from the red bar to the start of 'Time Slot 1' is labeled τ. 'Time Slot 1' contains 'Beacon 1, Chan.A' and 'Beacon 1, Chan.B'. 'Time Slot 2' contains 'Beacon 2, Chan.A' and 'Beacon 2, Chan.B'. A horizontal double-headed arrow between the start of Time Slot 1 and the start of Time Slot 2 is labeled '20 s'. A long horizontal double-headed arrow at the bottom, spanning from the start of Time Slot 1 to the end of the shown period, is labeled T_WLAN_meas.](0019f09403376d6444ee323591fa2e98_img.jpg)
+
+Figure 4.3.2.1.3-1: WLAN Measurement Time diagram. The diagram shows a timeline starting with two triggers: 'The last location request received by higher layers' (blue bar) and 'The last location request received by WLAN physical layer' (red bar). The time interval from the red bar to the start of 'Time Slot 1' is labeled τ. 'Time Slot 1' contains 'Beacon 1, Chan.A' and 'Beacon 1, Chan.B'. 'Time Slot 2' contains 'Beacon 2, Chan.A' and 'Beacon 2, Chan.B'. A horizontal double-headed arrow between the start of Time Slot 1 and the start of Time Slot 2 is labeled '20 s'. A long horizontal double-headed arrow at the bottom, spanning from the start of Time Slot 1 to the end of the shown period, is labeled T\_WLAN\_meas.
+
+Figure 4.3.2.1.3-1: WLAN Measurement Time
+
+#### 4.3.2.2 E-UTRAN TDD-WLAN Access Point Measurements
+
+##### 4.3.2.2.1 Introduction
+
+The requirements defined in section 4.3.2.2 shall apply provided the E-UTRA TDD UE has received *WLAN-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12].
+
+##### 4.3.2.2.2 Measurement Requirements
+
+The measurement reporting delay requirements for WLAN are defined in section 4.3.2.2.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7.
+
+##### 4.3.2.2.3 Measurement Reporting Delay
+
+Same as 4.3.2.1.3.
+
+#### 4.3.2.3 NR WLAN Access Point Measurements
+
+##### 4.3.2.3.1 Introduction
+
+The requirements defined in section 4.3.2.3 shall apply provided the NR UE has received *WLAN-RequestLocationInformation* message from LMF via LPP requesting the UE to report WLAN measurement for one or more WLAN Access Points [12].
+
+##### 4.3.2.3.2 Measurement Requirements
+
+The measurement reporting delay requirements for WLAN are defined in section 4.3.2.3.3. The WLAN Access Point identification minimum performance requirements are defined in clause 7.
+
+##### 4.3.2.3.3 Measurement Reporting Delay
+
+Same as 4.3.2.1.3.
+
+## 4.4 Bluetooth Measurements
+
+### 4.4.1 General
+
+Clause 4.4 defines the measurement requirements for the measurements performed by the UE for Bluetooth based positioning.
+
+### 4.4.2 Bluetooth Access Point Measurements
+
+#### 4.4.2.1 Introduction
+
+The requirements defined in sections 4.4.2 for E-UTRA shall apply provided the UE has received *BT-RequestLocationInformation* message from E-SMLC via LPP requesting the UE to report Bluetooth measurements for one or more Bluetooth Access Points [12].
+
+The requirements defined in sections 4.4.2 for NR shall apply provided the UE has received *BT-RequestLocationInformation* message from LMF via LPP requesting the UE to report Bluetooth measurements for one or more Bluetooth Access Points [12].
+
+Editor's note: In the Bluetooth access point measurement requirements for NR, the NR clauses are separate from LTE, but it is FFS whether separate clauses are needed for SA NR and non-SA NR.
+
+#### 4.4.2.2 Measurement Requirements
+
+For E-UTRA, in the RRC\_CONNECTED state the measurement period for Bluetooth Access Point identification shall be  $T_{BT\_meas}$ . The value of  $T_{BT\_meas}$  is 10.24 s, and can be extended to 40.96 s if extended inquiry is allowed, provided that the following conditions are met [13]:
+
+- At least one Bluetooth beacon signal is transmitted on one of the Bluetooth advertising channels with a broadcast interval of 100 ms.
+
+$T_{BT\_meas}$  defined in this section shall apply when no DRX cycle is configured or when any DRX cycle defined in [14] is configured.
+
+The UE physical layer shall be capable of reporting Bluetooth Access Point(s) measurements to higher layers within the measurement period of  $T_{BT\_meas}$ .
+
+The Bluetooth RSSI measurement accuracy for all measured access points shall be fulfilled according to the accuracy as specified in the clause 6.
+
+#### 4.4.2.3 Measurement Reporting Delay
+
+For E-UTRA, this requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is:  $2 \times \text{TTI}_{\text{DCCH}}$ . This measurement reporting delay excludes any delay caused by no UL resources for UE to send the measurement report.
+
+#### 4.4.2.4 NR Measurement Requirements
+
+Same as 4.4.2.2.
+
+#### 4.4.2.5 NR Measurement Reporting Delay
+
+Same as 4.4.2.3.
+
+# 5 MBS minimum performance requirements
+
+## 5.1 General
+
+The minimum performance requirements specified in clause 5 apply for UEs that support MBS. This section applies to requirements for NR, UTRA, and E-UTRA.
+
+The code phase accuracy requirements in this clause are statistical in nature and pertain to the 90<sup>th</sup> percentile of the distribution.
+
+The measurement time for each requirement shall be  $T_{\text{MBS\_meas}}$  as described in clause 4.2.3. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.
+
+## 5.2 Sensitivity
+
+A Sensitivity requirement is essential for verifying the performance of MBS receiver in weak signal conditions. In order to test the most stringent signal levels for the beacons the Sensitivity test case is performed in AWGN channel. This test case verifies the UE MBS performance at the lowest expected signal levels.
+
+In MBS deployments, target sensitivity levels of -130 dBm (at the UE antenna connector, across the signal bandwidth) are used.
+
+The minimum requirements for Sensitivity are shown in Table 5.2-1.
+
+**Table 5.2-1: Requirements for Sensitivity**
+
+| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms)       |
+|-------------------|-----------------------|--------------------------------------------|
+| TB1 (2 MHz) [7]   | -130                  | $1.66 \times 10^{-4}$                      |
+| TB1 (5 MHz) [7]   | -130                  | $6.64 \times 10^{-5}$ (Release 14 onwards) |
+
+The test case requirements for Sensitivity measurement accuracy can be found in clause A.4.2.
+
+## 5.3 Nominal Accuracy
+
+The Nominal Accuracy requirement verifies the UE MBS performance under ideal conditions. The primary aim of the test is to ensure good accuracy when the MBS signal conditions allow it.
+
+In this requirement AWGN channel model is used and the signal level is above the noise floor.
+
+The minimum requirements for Nominal are shown in Table 5.3-1.
+
+**Table 5.3-1: Requirements for Nominal Accuracy**
+
+| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms)      |
+|-------------------|-----------------------|-------------------------------------------|
+| TB1 (2 MHz) [7]   | -30                   | $5.0 \times 10^{-5}$                      |
+| TB2 (5 MHz) [7]   | -30                   | $2.0 \times 10^{-5}$ (Release 14 onwards) |
+
+The test case requirements for Nominal measurement accuracy can be found in clause A.4.2.
+
+## 5.4 Dynamic Range
+
+The Dynamic Range requirement is targeted at testing the performance of the MBS receiver under time varying signal conditions. This test case is important for a system such as MBS where the time slotting of beacons is used.
+
+The maximum signal level of a MBS beacon is expected to be -30 dBm (at the UE antenna connector). This can be shown theoretically by assuming a TX power of +40 dBm and a minimum coupling loss between the transmitter and the UE of 70 dB [5].
+
+For this requirement, the power level of the MBS beacons shall be alternated between the strongest and the weakest expected levels across consecutive slots in the MBS transmission period.
+
+The minimum requirements for Dynamic Range are shown in Table 5.4-1.
+
+**Table 5.4-1: Requirements for Dynamic Range**
+
+| MBS Configuration | Signal Strength (dBm) | Code phase measurement accuracy (ms)       |
+|-------------------|-----------------------|--------------------------------------------|
+| TB1 (2 MHz) [7]   | -30                   | $5.0 \times 10^{-5}$                       |
+|                   | -130                  | $1.66 \times 10^{-4}$                      |
+| TB2 (5 MHz) [7]   | -30                   | $2.0 \times 10^{-5}$ (Release 14 onwards)  |
+|                   | -130                  | $6.64 \times 10^{-5}$ (Release 14 onwards) |
+
+The test case requirements for Dynamic Range measurement accuracy can be found in clause A.4.2.
+
+## 5.5 Multipath
+
+The purpose of the test case is to verify the receiver's tolerance to multipath.
+
+The pedestrian channel model used in TS 37.571-1 [9], captured in Annex B of TS 36.521-1 [10] is used for assessing the MBS performance under the multipath scenario, specifically the Extended Pedestrian A (EPA) with a maximum Doppler frequency of 5 Hz (EPA 5Hz).
+
+The minimum requirements for the Multipath scenario are shown in Table 5.5-1.
+
+**Table 5.5-1: Requirements for Multipath scenario**
+
+| MBS Configuration | Direct Path Signal Strength (dBm) | Code phase measurement accuracy (ms) |
+|-------------------|-----------------------------------|--------------------------------------|
+| TB1 (2 MHz) [7]   | -30                               | $1.66 \times 10^{-4}$                |
+
+The test case requirements for Multipath measurement accuracy can be found in clause A.4.3.
+
+# 6 Bluetooth performance requirements
+
+## 6.1 Introduction
+
+The requirements in this clause are valid for terminals capable of Bluetooth.
+
+### 6.1.1 Bluetooth RSSI Measurement
+
+#### 6.1.1.1 Measurement Accuracy
+
+The Bluetooth RSSI metric is an absolute receiver signal strength value in dBm. The measured Bluetooth RSSI shall be accurate within  $\pm 6$  dB as defined in [13].
+
+The reporting range of Bluetooth RSSI is defined in section 6.5.7.2 [12].
+
+# 7 WLAN Access Point Identification minimum performance requirements
+
+## 7.1 General
+
+The minimum performance requirements specified in clause 7 apply for UEs that support WLAN positioning. This section applies to requirements for E-UTRA and NR.
+
+The measurement requirements in this clause are statistical in nature and pertain to the 90<sup>th</sup> percentile of the distribution.
+
+The measurement time for each requirement shall be  $T_{\text{WLAN\_meas}}$  as described in clause 4.3.2.1.2 for E-UTRA FDD, clause 4.3.2.2.3 for E-UTRA TDD, and TBD for NR. These requirements do not include nor consider delays occurring in the various signalling interfaces of the network.
+
+## 7.2 WLAN Access Point Identification under Sensitivity conditions
+
+The sensitivity conditions for a WLAN receiver are defined by IEEE in [15].
+
+The UE shall be able to identify at least 6 WLAN Access Points if the WLAN beacons are received at the sensitivity power level. In order to test the most stringent signal levels for the beacons the Sensitivity test case is performed in AWGN channel. This test case verifies the UE capability to identify and report WLAN AP at the lowest expected signal levels but it does not evaluate measurement accuracy.
+
+**Table 7.2-1: Requirements for WLAN Access Point Identification under Sensitivity conditions**
+
+| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points |
+|--------------------|-----------------------|-----------------------------|
+| 6                  | See [15]              | 90                          |
+
+## 7.3 WLAN Access Point Identification under Nominal conditions
+
+The WLAN Access Point identification under nominal conditions verifies the UE capability to identify and report WLAN APs when the WLAN signal conditions are ideal.
+
+In this requirement AWGN channel model is used and the signal level is above the noise floor.
+
+The minimum requirements for Nominal are shown in Table 7.3-1.
+
+**Table 7.3-1: Requirements for WLAN Access Point Identification under Nominal conditions**
+
+| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points |
+|--------------------|-----------------------|-----------------------------|
+| 6                  | -60                   | 90                          |
+
+## 7.4 WLAN Access Point Identification under Dynamic Range conditions
+
+The WLAN Access Point identification under dynamic range conditions verifies the UE capability to identify and report WLAN APs when the received power difference between WLAN APs is large. The power difference between APs follows the adjacent channel rejection criteria defined by IEEE in [15].
+
+The UE shall be able to identify at least 3 WLAN AP located in 3 adjacent channels where the separation between channels is  $\geq 20$  MHz and the middle channel is received with high power and the side channels are received with low power.
+
+**Table 7.4-1: Requirements for WLAN Access Point Identification under Dynamic Range conditions**
+
+| Number of WLAN APs | Signal Strength (dBm) | % of reported Access Points |
+|--------------------|-----------------------|-----------------------------|
+| 3                  | See [15]              | 100                         |
+
+# --- Annex A (normative): Test Case Requirements ---
+
+## A.1 Purpose of annex
+
+This Annex specifies test specific parameters for some of the functional requirements in clause 5. The tests provide additional information to how the requirements should be interpreted for the purpose of conformance testing. The tests in this Annex are described such that one functional requirement may be tested in one or several tests and one test may verify several requirements. Some requirements may lack a test.
+
+The conformance tests are specified in clauses A.3 and A.4. Statistical interpretation of the requirements is described in clause A.2.
+
+Editor's Note: Based on the E-UTRA test cases specified in A.3.2 and A.3.3, additional WLAN and Bluetooth test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements.
+
+## --- A.2 Requirement classification for statistical testing
+
+Requirements in the present document are either expressed as absolute requirements with a single value stating the requirement, or expressed as a success rate. There are no provisions for the statistical variations that will occur when the parameter is tested.
+
+Annex A outlines the tests in more detail and lists the test parameters needed. The test will result in an outcome of a test variable value for the device under test (DUT) inside or outside the test limit. Overall, the probability of a "good" DUT being inside the test limit(s) and the probability of a "bad" DUT being outside the test limit(s) should be as high as possible. For this reason, when selecting the test variable and the test limit(s), the statistical nature of the test is accounted for.
+
+The statistical nature depends on the type of requirement. Some have large statistical variations, while others are not statistical in nature at all. When testing a parameter with a statistical nature, a confidence level is set. This establishes the probability that a DUT passing the test actually meets the requirements and determines how many times a test has to be repeated and what the pass and fail criteria are. Those aspects are not covered by TS 37.171. The details of the tests on how many times to run it and how to establish confidence in the tests are described in TS 37.571-1 [9]. This Annex establishes the variable to be used in the test and whether it can be viewed as statistical in nature or not.
+
+## --- A.3 UE Measurement Procedures
+
+### A.3.1 MBS Measurement reporting delay test case
+
+#### A.3.1.1 Test Purpose and Environment
+
+The purpose of the test is to verify that the MBS measurements meet the measurement time requirements specified in clause 4.2.3 in an environment with fading propagation conditions (EPA 5 Hz). This test can be used for NR, UTRA, and E-UTRA testing.
+
+In this test case there is one beacon transmitted in one beacon slots in the MBS beacon transmission period (see Figure 4.2.3-1). The position of the beacon in the beacon transmission period is static for the duration of the test. In other slots there are no simulated beacons. The beacon has centre frequency of 925.977 MHz or set using the network assistance data in Release 14. The beacon has transmitted signal strength of -30 dBm. The beacon is transmitted with code phase (delay) of  $1.6678 \times 10^{-4}$  ms, corresponding to 50 m.
+
+The UE shall perform and report the MBS measurements for the beacon within 12000 ms, starting from the receipt of the location request.
+
+NOTE: The MBS measurement time in the test is derived from the following expression:
+
+$$T_{\text{MBS\_meas}} = \tau + 10 \times \text{ceil}(n/10) \times T_{\text{MBS\_TP}} + T_{\text{Proc}} \text{ ms, where } n=1, \tau \text{ is one second, } T_{\text{MBS\_TP}} \text{ is one second and } T_{\text{Proc}} \text{ is one second.}$$
+
+The beacon is of type TB1 (2 MHz) specified in clause 9 of the MBS ICD [7] and the data transmitted is in Type 2 packets specified in clause 9.6.3 of the MBS ICD [7] with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros [7].
+
+The beacon shall use a PN code chosen from the PN code list for TB1 [7].
+
+If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A.
+
+**Table A.3.1.1-1: General test parameters for measurement reporting delay**
+
+| Parameter                             | Unit    | Value                                | Comment                                                                |
+|---------------------------------------|---------|--------------------------------------|------------------------------------------------------------------------|
+| Centre Frequency                      | MHz     | 925.977                              |                                                                        |
+| RF Channel                            | N/A     | EPA 5 Hz                             |                                                                        |
+| MBS Beacon Configuration              | N/A     | TB1 (2 MHz)                          |                                                                        |
+| MBS Data Packet Type                  | N/A     | Type 2                               |                                                                        |
+| Beacon PN Code                        | Integer | Chosen from the PN code list for TB1 |                                                                        |
+| Beacon transmitted Code Phase (delay) | ms      | $1.6678 \times 10^{-4}$              | Corresponds to 50 m. Constant per beacon for the duration of the test. |
+| Beacon Signal Strength                | dBm     | -30                                  |                                                                        |
+
+**Table A.3.1.1-2: MBS Beacon Payload fields for measurement reporting delay**
+
+| Parameter        | Unit    | Value                | Comment |
+|------------------|---------|----------------------|---------|
+| TxID             | Integer | Equal to Slot number |         |
+| Slot Index       | Integer | Equal to Slot number |         |
+| All other fields | N/A     | 0                    |         |
+
+#### A.3.1.2 Test Requirements
+
+The MBS measurement reporting delay shall fulfil the requirements in clause 4.2.3.
+
+### A.3.2 WLAN Access Point Identification and Reporting Delay
+
+Editor's Note: Based on the E-UTRA test cases specified in this section, additional WLAN test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements.
+
+#### A.3.2.1 Void
+
+#### A.3.2.2 LTE-FDD: WLAN AP Identification and reporting delay under nominal conditions test
+
+##### A.3.2.2.1 Test purpose and Environment
+
+The purpose of this test is to verify the requirements in Clause 7.3 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message).
+
+In this test, there are cell1 (E-UTRAN FDD) and 6 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There are 2 APs in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2.
+
+**Table A.3.2.2.1-1: General WLAN AP test parameters  
+for WLAN AP Identification and reporting delay under nominal conditions test**
+
+| Parameter               | Unit | Value | Comment                                                 |
+|-------------------------|------|-------|---------------------------------------------------------|
+| Number of Access Points | N/A  | 6     | AP1-AP6                                                 |
+| Time Slot 1             | ms   | 1     | AP1, AP2                                                |
+| Time Slot 2             | ms   | 1     | AP3, AP4                                                |
+| Time Slot 3             | ms   | 1     | AP5                                                     |
+| Time Slot 4             | ms   | 1     | AP6                                                     |
+| T1                      | s    | 5     | During this time the WLAN signal is not transmitted     |
+| T2                      | s    | 25    | UE shall report WLAN measurement information within 20s |
+
+**Table A.3.2.2.1-2: E-UTRAN TDD Cell specific and WLAN AP specific test parameters for WLAN AP Identification and reporting delay under nominal conditions test**
+
+| Parameter                                                                                                                                                                                                                        | Unit       | Cell 1   |      | AP 1, 4                                              |     | AP 2, 5                                              |     | AP 3, 6                                              |     |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|------|------------------------------------------------------|-----|------------------------------------------------------|-----|------------------------------------------------------|-----|
+|                                                                                                                                                                                                                                  |            | T1       | T2   | T1                                                   | T2  | T1                                                   | T2  | T1                                                   | T2  |
+| E-UTRA RF Channel Number                                                                                                                                                                                                         |            | 1        |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| WLAN Channel Number                                                                                                                                                                                                              |            | N/A      |      | 1                                                    |     | 2                                                    |     | 3                                                    |     |
+| BW <sub>channel</sub>                                                                                                                                                                                                            |            | 10MHz    |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| WLAN Channel spacing                                                                                                                                                                                                             |            | N/A      |      | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     |
+| PDSCH parameters:<br>DL Reference Measurement Channel                                                                                                                                                                            |            | R.0 FDD  |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PCFICH/PDCCH/PHICH parameters:<br>DL Reference Measurement Channel                                                                                                                                                               |            | R.6 FDD  |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| OCNG Patterns                                                                                                                                                                                                                    |            | OP.1 FDD |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PBCH_RA                                                                                                                                                                                                                          | dB         | 0        |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PBCH_RB                                                                                                                                                                                                                          | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PSS_RA                                                                                                                                                                                                                           | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| SSS_RA                                                                                                                                                                                                                           | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PCFICH_RB                                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PHICH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PHICH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDCCH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDCCH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDSCH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDSCH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| OCNG_RA <sup>Note 1</sup>                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| OCNG_RB <sup>Note 1</sup>                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| N <sub>oc1</sub> <sup>Note 2</sup>                                                                                                                                                                                               | dBm/15 KHz | -98      |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| N <sub>oc2</sub> <sup>Note 3</sup>                                                                                                                                                                                               | dBm/20 MHz | N/A      |      | -75                                                  |     | -75                                                  |     | -75                                                  |     |
+| $\hat{E}_s/N_{oc1}$                                                                                                                                                                                                              | dB         | 3        | 3    | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| $\hat{E}_s/I_{ot}$ <sup>Note 4</sup>                                                                                                                                                                                             | dB         | 3        | 3    |                                                      |     |                                                      |     |                                                      |     |
+| RSRP <sup>Note 4</sup>                                                                                                                                                                                                           | dBm/15 kHz | -95      | -95  |                                                      |     |                                                      |     |                                                      |     |
+| SCH_RP <sup>Note 4</sup>                                                                                                                                                                                                         | dBm/15 kHz | -95      | -95  |                                                      |     |                                                      |     |                                                      |     |
+| I <sub>o</sub> <sup>Note 3</sup>                                                                                                                                                                                                 | dBm/Ch BW  | -        | -    |                                                      |     |                                                      |     |                                                      |     |
+|                                                                                                                                                                                                                                  |            | 65.5     | 65.5 |                                                      |     |                                                      |     |                                                      |     |
+| WLAN Received Power Level                                                                                                                                                                                                        | dBm        | N/A      | N/A  | - inf                                                | -60 | - inf                                                | -60 | - inf                                                | -60 |
+| WLAN SNR <sup>Note 4</sup>                                                                                                                                                                                                       | dB         | N/A      |      | 15                                                   |     | 15                                                   |     | 15                                                   |     |
+| Propagation Condition                                                                                                                                                                                                            |            | AWGN     |      |                                                      |     |                                                      |     |                                                      |     |
+| Antenna Configuration                                                                                                                                                                                                            |            | 1x2      |      | -                                                    |     | -                                                    |     | -                                                    |     |
+| Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.                                                                     |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.   |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled. |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 4: $E_s/I_{ot}$ , RSRP, SCH_RP, I <sub>o</sub> and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves.                                                  |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 5: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.                                                                                                                       |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+
+##### A.3.2.2.2 Test Requirements
+
+The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.3. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases.
+
+#### A.3.2.3 LTE-TDD: WLAN AP Identification and reporting delay under nominal conditions test
+
+##### A.3.2.3.1 Test purpose and Environment
+
+The purpose of this test is to verify the requirements in Clause 7.3 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message).
+
+In this test, there are cell1 (E-UTRAN TDD) and 6 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There are 2 APs in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2.
+
+**Table A.3.2.3.1-1: General WLAN AP test parameters  
+for WLAN AP Identification and reporting delay under nominal conditions test**
+
+| Parameter               | Unit | Value | Comment                                                 |
+|-------------------------|------|-------|---------------------------------------------------------|
+| Number of Access Points | N/A  | 6     | AP1-AP6                                                 |
+| Time Slot 1             | ms   | 1     | AP1, AP2                                                |
+| Time Slot 2             | ms   | 1     | AP3, AP4                                                |
+| Time Slot 3             | ms   | 1     | AP5                                                     |
+| Time Slot 4             | ms   | 1     | AP6                                                     |
+| T1                      | s    | 5     | During this time the WLAN signal is not transmitted     |
+| T2                      | s    | 25    | UE shall report WLAN measurement information within 20s |
+
+**Table A.3.2.3.1-2: E-UTRAN TDD Cell specific and WLAN AP specific test parameters for WLAN AP Identification and reporting delay under nominal conditions test**
+
+| Parameter                                                                                                                                                                                                                        | Unit       | Cell 1   |      | AP 1, 4                                              |     | AP 2, 5                                              |     | AP 3, 6                                              |     |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|------|------------------------------------------------------|-----|------------------------------------------------------|-----|------------------------------------------------------|-----|
+|                                                                                                                                                                                                                                  |            | T1       | T2   | T1                                                   | T2  | T1                                                   | T2  | T1                                                   | T2  |
+| E-UTRA RF Channel Number                                                                                                                                                                                                         |            | 1        |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| WLAN Channel Number                                                                                                                                                                                                              |            | N/A      |      | 1                                                    |     | 2                                                    |     | 3                                                    |     |
+| BW <sub>channel</sub>                                                                                                                                                                                                            |            | 10MHz    |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| WLAN Channel spacing                                                                                                                                                                                                             |            | N/A      |      | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |     |
+| PDSCH parameters:<br>DL Reference Measurement Channel                                                                                                                                                                            |            | R.0 TDD  |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PCFICH/PDCCH/PHICH parameters:<br>DL Reference Measurement Channel                                                                                                                                                               |            | R.6 TDD  |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| OCNG Patterns                                                                                                                                                                                                                    |            | OP.1 TDD |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PBCH_RA                                                                                                                                                                                                                          | dB         | 0        |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| PBCH_RB                                                                                                                                                                                                                          | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PSS_RA                                                                                                                                                                                                                           | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| SSS_RA                                                                                                                                                                                                                           | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PCFICH_RB                                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PHICH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PHICH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDCCH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDCCH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDSCH_RA                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| PDSCH_RB                                                                                                                                                                                                                         | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| OCNG_RA <sup>Note 1</sup>                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| OCNG_RB <sup>Note 1</sup>                                                                                                                                                                                                        | dB         |          |      |                                                      |     |                                                      |     |                                                      |     |
+| N <sub>oc1</sub> <sup>Note 2</sup>                                                                                                                                                                                               | dBm/15 KHz | -98      |      | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| N <sub>oc2</sub> <sup>Note 3</sup>                                                                                                                                                                                               | dBm/20 MHz | N/A      |      | -75                                                  |     | -75                                                  |     | -75                                                  |     |
+| $\hat{E}_s/N_{oc1}$                                                                                                                                                                                                              | dB         | 3        | 3    | N/A                                                  |     | N/A                                                  |     | N/A                                                  |     |
+| $\hat{E}_s/I_{ot}$ <sup>Note 4</sup>                                                                                                                                                                                             | dB         | 3        | 3    |                                                      |     |                                                      |     |                                                      |     |
+| RSRP <sup>Note 4</sup>                                                                                                                                                                                                           | dBm/15 kHz | -95      | -95  |                                                      |     |                                                      |     |                                                      |     |
+| SCH_RP <sup>Note 4</sup>                                                                                                                                                                                                         | dBm/15 kHz | -95      | -95  |                                                      |     |                                                      |     |                                                      |     |
+| I <sub>o</sub> <sup>Note 3</sup>                                                                                                                                                                                                 | dBm/Ch BW  | -        | -    |                                                      |     |                                                      |     |                                                      |     |
+|                                                                                                                                                                                                                                  |            | 65.5     | 65.5 |                                                      |     |                                                      |     |                                                      |     |
+| WLAN Received Power Level                                                                                                                                                                                                        | dBm        | N/A      | N/A  | - inf                                                | -60 | - inf                                                | -60 | - inf                                                | -60 |
+| WLAN SNR <sup>Note 4</sup>                                                                                                                                                                                                       | dB         | N/A      |      | 15                                                   |     | 15                                                   |     | 15                                                   |     |
+| Propagation Condition                                                                                                                                                                                                            |            | AWGN     |      |                                                      |     |                                                      |     |                                                      |     |
+| Antenna Configuration                                                                                                                                                                                                            |            | 1x2      |      | -                                                    |     | -                                                    |     | -                                                    |     |
+| Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.                                                                     |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.   |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled. |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 4: $E_s/I_{ot}$ , RSRP, SCH_RP, I <sub>o</sub> and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves.                                                  |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+| Note 5: The resources for uplink transmission are assigned to the UE prior to the start of time period T2.                                                                                                                       |            |          |      |                                                      |     |                                                      |     |                                                      |     |
+
+##### A.3.2.3.2 Test Requirements
+
+The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.3. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases.
+
+#### A.3.2.4 LTE-FDD: WLAN AP Identification and reporting delay under dynamic range conditions test
+
+##### A.3.2.4.1 Test purpose and Environment
+
+The purpose of this test is to verify the requirements in Clause 7.4 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message).
+
+In this test, there are cell1 (E-UTRAN FDD) and 3 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There is 1 AP in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2.
+
+**Table A.3.2.4.1-1: General test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test**
+
+| Parameter               | Unit | Value | Comment                                                 |
+|-------------------------|------|-------|---------------------------------------------------------|
+| Number of Access Points | N/A  | 3     | AP1-AP3                                                 |
+| Time Slot 1             | ms   | 1     | AP1, AP2, AP3                                           |
+| T1                      | s    | 5     | During this time the WLAN signal is not transmitted     |
+| T2                      | s    | 25    | UE shall report WLAN measurement information within 20s |
+
+**Table A.3.2.4.1-2: E-UTRAN FDD Cell specific test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test**
+
+| Parameter                                                       | Unit                                                                                                                                                                                                                     | Cell 1   |       | AP 1                                                 |                                                | AP 2                                                 |                                                | AP 3                                                 |                                                |
+|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|
+|                                                                 |                                                                                                                                                                                                                          | T1       | T2    | T1                                                   | T2                                             | T1                                                   | T2                                             | T1                                                   | T2                                             |
+| E-UTRA RF Channel Number                                        |                                                                                                                                                                                                                          | 1        |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| WLAN Channel Number                                             |                                                                                                                                                                                                                          | N/A      |       | 1                                                    |                                                | 2                                                    |                                                | 3                                                    |                                                |
+| BW <sub>channel</sub>                                           |                                                                                                                                                                                                                          | 10MHz    |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| WLAN Channel spacing                                            |                                                                                                                                                                                                                          | N/A      |       | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                |
+| PDSCH parameters:<br>DL Reference Measurement Channel           |                                                                                                                                                                                                                          | R.0 FDD  |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PCFICH/PDCCH/PHICH parameters: DL Reference Measurement Channel |                                                                                                                                                                                                                          | R.6 FDD  |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| OCNG Patterns                                                   |                                                                                                                                                                                                                          | OP.1 FDD |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PBCH_RA                                                         | dB                                                                                                                                                                                                                       | 0        |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PBCH_RB                                                         | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PSS_RA                                                          | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| SSS_RA                                                          | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PCFICH_RB                                                       | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PHICH_RA                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PHICH_RB                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDCCH_RA                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDCCH_RB                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDSCH_RA                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDSCH_RB                                                        | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| OCNG_RA <sup>Note 1</sup>                                       | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| OCNG_RB <sup>Note 1</sup>                                       | dB                                                                                                                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| N <sub>oc1</sub> <sup>Note 2</sup>                              | dBm/15 KHz                                                                                                                                                                                                               | -98      |       | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| N <sub>oc2</sub> <sup>Note 3</sup>                              | dBm/20 MHz                                                                                                                                                                                                               | N/A      |       | -85                                                  |                                                | -85                                                  |                                                | -85                                                  |                                                |
+| $\hat{E}_s/N_{oc1}$                                             | dB                                                                                                                                                                                                                       | 3        | 3     | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| $\hat{E}_s/I_{ot}$ <sup>Note 4</sup>                            | dB                                                                                                                                                                                                                       | 3        | 3     |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| RSRP <sup>Note 4</sup>                                          | dBm/15 kHz                                                                                                                                                                                                               | -95      | -95   |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| SCH_RP <sup>Note 4</sup>                                        | dBm/15 kHz                                                                                                                                                                                                               | -95      | -95   |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| I <sub>o</sub> <sup>Note 3</sup>                                | dBm/Ch BW                                                                                                                                                                                                                | -65.5    | -65.5 |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+|                                                                 |                                                                                                                                                                                                                          |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| WLAN Received Power Level                                       | dBm                                                                                                                                                                                                                      | N/A      | N/A   | -inf                                                 | WLAN 2.4 GHz band: -74<br>WLAN 5 GHz band: -79 | -inf                                                 | WLAN 2.4 GHz band: -39<br>WLAN 5 GHz band: -63 | -inf                                                 | WLAN 2.4 GHz band: -74<br>WLAN 5 GHz band: -79 |
+| WLAN SNR <sup>Note 4</sup>                                      | dB                                                                                                                                                                                                                       | N/A      |       | WLAN 2.4 GHz band: 11<br>WLAN 5 GHz band: 6          |                                                | WLAN 2.4 GHz band: 46<br>WLAN 5 GHz band: 22         |                                                | WLAN 2.4 GHz band: 11<br>WLAN 5 GHz band: 6          |                                                |
+| Propagation Condition                                           |                                                                                                                                                                                                                          | AWGN     |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Antenna Configuration                                           |                                                                                                                                                                                                                          | 1x2      |       | -                                                    |                                                | -                                                    |                                                | -                                                    |                                                |
+| Note 1:                                                         | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.                                                                     |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Note 2:                                                         | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.   |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Note 3:                                                         | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled. |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Note 4:                                                         | E <sub>s</sub> /I <sub>ot</sub> , RSRP, SCH_RP, I <sub>o</sub> and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves.                               |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Note 5:                                                         | The resources for uplink transmission are assigned to the UE prior to the start of time period T2.                                                                                                                       |          |       |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+
+##### A.3.2.4.2 Test Requirements
+
+The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.4. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases.
+
+#### A.3.2.5 LTE-TDD: WLAN AP Identification and reporting delay under dynamic range conditions test
+
+##### A.3.2.5.1 Test purpose and Environment
+
+The purpose of this test is to verify the requirements in Clause 7.4 for WLAN AP measurements. The UE shall send *wlan-MeasurementInformation* IE including WLAN measurements for each AP indicating at least *wlan-AP-Identifier* (BSSID) and *rssi* (if reporting of RSSI is supported by the UE as indicated by the UE in the LPP PROVIDE CAPABILITIES message).
+
+In this test, there are cell1 (E-UTRAN TDD) and 3 WLAN APs transmitting beacon signals at least every 102.4 ms. There is an active LTE connection between the SS and the UE and the measurements are performed in RRC\_CONNECTED state. The beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band. The APs are transmitting in 3 non-overlapping frequency channels in the same WLAN Frequency Band. There is 1 AP in every channel. The test consists of two successive time periods, with duration of T1 and T2, respectively. *WLAN-RequestLocationInformation* message shall be provided to the UE during T1. WLAN Access Points only transmit signal during T2.
+
+**Table A.3.2.5.1-1: General test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test**
+
+| Parameter               | Unit | Value | Comment                                                 |
+|-------------------------|------|-------|---------------------------------------------------------|
+| Number of Access Points | N/A  | 3     | AP1-AP3                                                 |
+| Time Slot 1             | ms   | 1     | AP1, AP2, AP3                                           |
+| T1                      | s    | 5     | During this time the WLAN signal is not transmitted     |
+| T2                      | s    | 25    | UE shall report WLAN measurement information within 20s |
+
+**Table A.3.2.5.1-2: E-UTRAN TDD Cell specific test parameters for WLAN AP Identification and reporting delay under dynamic range conditions test**
+
+| Parameter                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Unit       | Cell 1   |      | AP 1                                                 |                                                | AP 2                                                 |                                                | AP 3                                                 |                                                |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|------------------------------------------------------|------------------------------------------------|
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |            | T1       | T2   | T1                                                   | T2                                             | T1                                                   | T2                                             | T1                                                   | T2                                             |
+| E-UTRA RF Channel Number                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |            | 1        |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| WLAN Channel Number                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |            | N/A      |      | 1                                                    |                                                | 2                                                    |                                                | 3                                                    |                                                |
+| BW <sub>channel</sub>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            | 10MHz    |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| WLAN Channel spacing                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |            | N/A      |      | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                | WLAN 2.4 GHz band: 25 MHz<br>WLAN 5 GHz band: 20 MHz |                                                |
+| PDSCH parameters:<br>DL Reference Measurement Channel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            | R.0 TDD  |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PCFICH/PDCCH/PHICH parameters: DL Reference Measurement Channel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |            | R.6 TDD  |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| OCNG Patterns                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |            | OP.1 TDD |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PBCH_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | dB         | 0        |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| PBCH_RB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PSS_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| SSS_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PCFICH_RB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PHICH_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PHICH_RB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDCCH_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDCCH_RB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDSCH_RA                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| PDSCH_RB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| OCNG_RA <sup>Note 1</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| OCNG_RB <sup>Note 1</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | dB         |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| N <sub>oc1</sub> <sup>Note 2</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | dBm/15 KHz | -98      |      | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| N <sub>oc2</sub> <sup>Note 3</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | dBm/20 MHz | N/A      |      | -85                                                  |                                                | -85                                                  |                                                | -85                                                  |                                                |
+| $\hat{E}_s/N_{oc1}$                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | dB         | 3        | 3    | N/A                                                  |                                                | N/A                                                  |                                                | N/A                                                  |                                                |
+| $\hat{E}_s/I_{ot}$ <sup>Note 4</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | dB         | 3        | 3    |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| RSRP <sup>Note 4</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | dBm/15 kHz | -95      | -95  |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| SCH_RP <sup>Note 4</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | dBm/15 kHz | -95      | -95  |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| I <sub>o</sub> <sup>Note 3</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | dBm/Ch BW  | -        | -    |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |            | 65.5     | 65.5 |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| WLAN Received Power Level                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | dBm        | N/A      | N/A  | -inf                                                 | WLAN 2.4 GHz band: -74<br>WLAN 5 GHz band: -79 | -inf                                                 | WLAN 2.4 GHz band: -39<br>WLAN 5 GHz band: -63 | -inf                                                 | WLAN 2.4 GHz band: -74<br>WLAN 5 GHz band: -79 |
+| WLAN SNR <sup>Note 4</sup>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | dB         | N/A      |      | WLAN 2.4 GHz band: 11<br>WLAN 5 GHz band: 6          |                                                | WLAN 2.4 GHz band: 46<br>WLAN 5 GHz band: 22         |                                                | WLAN 2.4 GHz band: 11<br>WLAN 5 GHz band: 6          |                                                |
+| Propagation Condition                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            | AWGN     |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+| Antenna Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |            | 1x2      |      | -                                                    |                                                | -                                                    |                                                | -                                                    |                                                |
+| Note 1: OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.<br>Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.<br>Note 3: Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled.<br>Note 4: E <sub>s</sub> /I <sub>ot</sub> , RSRP, SCH_RP, I <sub>o</sub> and WLAN SNR have been derived from other parameters for information purposes. They are not settable parameters themselves.<br>Note 5: The resources for uplink transmission are assigned to the UE prior to the start of time period T2. |            |          |      |                                                      |                                                |                                                      |                                                |                                                      |                                                |
+
+##### A.3.2.5.2 Test Requirements
+
+The WLAN Response Time shall fulfil the requirements in section 4.3 and the WLAN AP report shall fulfil the requirements in section 7.4. This test is, as stated in Clause 7, statistical in nature and the UE shall meet the corresponding requirement for at least 90% of the reported cases.
+
+### A.3.3 Bluetooth Measurement Requirements
+
+Editor’s Note: Based on the E-UTRA test cases specified in section, additional Bluetooth test parameters for EN-DC and NR SA operations shall be defined separately. The LTE and NR cell specific parameters for EN-DC and NR SA tests are FFS and shall be aligned with the NR requirements.
+
+#### A.3.3.1 E-UTRAN FDD Bluetooth identification
+
+##### A.3.3.1.1 Test Purpose and Environment
+
+The purpose of this test is to verify that the UE correctly identify and report Bluetooth Low Energy devices within the requirements stated in clause 4.4.
+
+The test parameters are given in Tables A.3.3.1.1-1 and A.3.3.1.1-2 below. In the tests there are cell1 (E-UTRAN FDD) and 6 Bluetooth low energy (BLE) devices. The test consists of two successive time periods, with duration of T1 and T2, respectively. *BT-RequestLocationInformation* message shall be provided to the UE during T1. BLE devices only transmit signal during T2.
+
+**Table A.3.3.1.1-1: General test parameters for E-UTRAN FDD Bluetooth measurement under AWGN in non-DRX**
+
+| Parameter                                  | Unit | Value                                                               | Comment                                                                                                                                                                                                     |
+|--------------------------------------------|------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Active cell                                |      | Cell 1                                                              | Cell 1 is on E-UTRA RF channel number 1.                                                                                                                                                                    |
+| Bluetooth Low Energy (BLE) Devices         |      | BLE 1, BLE 2, BLE3, BLE4, BLE5 and BLE6                             | BLE 1 and BLE2 are on Bluetooth Advertising Channel 1 (2402 MHz).<br>BLE 3 and BLE4 are on Bluetooth Advertising Channel 2 (2426 MHz).<br>BLE 5 and BLE6 are on Bluetooth Advertising Channel 3 (2480 MHz). |
+| CP length                                  |      | Normal                                                              | Applicable to cell 1                                                                                                                                                                                        |
+| E-UTRA RF Channel Number                   |      | 1                                                                   | One E-UTRA FDD carrier frequency is used.                                                                                                                                                                   |
+| Bluetooth Advertising Channel Number       |      | Channel 1: 2402 MHz,<br>Channel 2: 2426 MHz,<br>Channel 3: 2480 MHz | Bluetooth advertising channels (2402, 2426, 2480 MHz)                                                                                                                                                       |
+| Bluetooth beacon signal broadcast interval | ms   | 100 ms                                                              |                                                                                                                                                                                                             |
+| DRX                                        |      | OFF                                                                 |                                                                                                                                                                                                             |
+| T1                                         | s    | 5                                                                   | During this time the cell1 shall be known to the UE; but cell2 shall be unknown to the UE.                                                                                                                  |
+| T2                                         | s    | 15                                                                  | UE should report Bluetooth measurement information within 10.24s.                                                                                                                                           |
+
+**Table A.3.3.1.1-2: Cell specific test parameters for E-UTRAN FDD-WLAN event triggered reporting under AWGN in non-DRX**
+
+| Parameter | Unit | Cell 1 |    | BLE1, BLE2 |    | BLE3, BLE4 |    | BLE5, BLE6 |    |
+|-----------|------|--------|----|------------|----|------------|----|------------|----|
+|           |      | T1     | T2 | T1         | T2 | T1         | T2 | T1         | T2 |
+
+|                                                                    |                                                                                                                                                                                                                          |          |       |           |       |           |      |           |      |
+|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|-----------|-------|-----------|------|-----------|------|
+| E-UTRA RF Channel Number                                           |                                                                                                                                                                                                                          | 1        | N/A   | N/A       | N/A   |           |      |           |      |
+| Bluetooth Advertising Channel Number                               |                                                                                                                                                                                                                          | N/A      | 1     | 2         | 3     |           |      |           |      |
+| BW <sub>channel</sub>                                              |                                                                                                                                                                                                                          | 10MHz    | 2 MHz | 2 MHz     | 2 MHz |           |      |           |      |
+| PDSCH parameters:<br>DL Reference Measurement Channel              |                                                                                                                                                                                                                          | R.0 FDD  | N/A   | N/A       | N/A   |           |      |           |      |
+| PCFICH/PDCCH/PHICH parameters:<br>DL Reference Measurement Channel |                                                                                                                                                                                                                          | R.6 FDD  | N/A   | N/A       | N/A   |           |      |           |      |
+| OCNG Patterns                                                      |                                                                                                                                                                                                                          | OP.1 FDD | N/A   | N/A       | N/A   |           |      |           |      |
+| PBCH_RA                                                            | dB                                                                                                                                                                                                                       | 0        | N/A   | N/A       | N/A   |           |      |           |      |
+| PBCH_RB                                                            | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PSS_RA                                                             | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| SSS_RA                                                             | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PCFICH_RB                                                          | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PHICH_RA                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PHICH_RB                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PDCCH_RA                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PDCCH_RB                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PDSCH_RA                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| PDSCH_RB                                                           | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| OCNG_RA <sup>Note 1</sup>                                          | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| OCNG_RB <sup>Note 1</sup>                                          | dB                                                                                                                                                                                                                       |          |       |           |       |           |      |           |      |
+| N <sub>oc1</sub> <sup>Note 2</sup>                                 | dBm/15 KHz                                                                                                                                                                                                               | -98      | N/A   | N/A       | N/A   |           |      |           |      |
+| N <sub>oc2</sub> <sup>Note 3</sup>                                 | dBm/2MHz                                                                                                                                                                                                                 | N/A      | -84   | -84       | -84   |           |      |           |      |
+| E <sub>s</sub> /N <sub>oc1</sub>                                   | dB                                                                                                                                                                                                                       | 3        | 3     | N/A       |       |           |      |           |      |
+| E <sub>s</sub> /I <sub>ot</sub> <sup>Note 4</sup>                  | dB                                                                                                                                                                                                                       | 3        | 3     |           |       |           |      |           |      |
+| RSRP <sup>Note 4</sup>                                             | dBm/15 kHz                                                                                                                                                                                                               | -95      | -95   |           |       |           |      |           |      |
+| SCH_RP <sup>Note 4</sup>                                           | dBm/15 kHz                                                                                                                                                                                                               | -95      | -95   |           |       |           |      |           |      |
+| I <sub>o</sub> <sup>Note 3</sup>                                   | dBm/Ch BW                                                                                                                                                                                                                | -65.5    | -65.5 |           |       |           |      |           |      |
+| Bluetooth RSSI <sup>Note 4</sup>                                   | dBm/2 MHz                                                                                                                                                                                                                | N/A      | N/A   | -infinity | -60   | -infinity | -60  | -infinity | -60  |
+| SINR <sup>Note 4</sup>                                             | dB                                                                                                                                                                                                                       | N/A      | N/A   | -infinity | 63.2  | -infinity | 63.2 | -infinity | 63.2 |
+| Propagation Condition                                              |                                                                                                                                                                                                                          | AWGN     |       |           |       |           |      |           |      |
+| Antenna Configuration                                              |                                                                                                                                                                                                                          | 1x2      | -     | -         | -     |           |      |           |      |
+| Note 1:                                                            | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.                                                                     |          |       |           |       |           |      |           |      |
+| Note 2:                                                            | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.   |          |       |           |       |           |      |           |      |
+| Note 3:                                                            | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled. |          |       |           |       |           |      |           |      |
+| Note 4:                                                            | E <sub>s</sub> /I <sub>ot</sub> , RSRP, SCH_RP, I <sub>o</sub> and Bluetooth RSSI have been derived from other parameters for information purposes. They are not settable parameters themselves.                         |          |       |           |       |           |      |           |      |
+| Note 5:                                                            | The resources for uplink transmission are assigned to the UE prior to the start of time period T2.                                                                                                                       |          |       |           |       |           |      |           |      |
+
+##### A.3.3.1.2 Test Requirements
+
+The UE shall send *BT-ProvideLocationInformation*, with a measurement reporting delay less than 10.24s from the beginning of time period T2.
+
+The rate of correct events observed during repeated tests shall be at least 90% for each of the events.
+
+NOTE: The actual overall delays measured in the tests may be up to  $2 \times \text{TTI}_{\text{DCCH}}$  higher than the measurement reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
+
+#### A.3.3.2 E-UTRAN TDD Bluetooth identification
+
+##### A.3.3.2.1 Test Purpose and Environment
+
+The purpose of this test is to verify that the UE correctly identify and report Bluetooth Low Energy devices within the requirements stated in clause 4.4.
+
+The test parameters are given in Tables A.3.3.2.1-1 and A.3.3.2.1-2 below. In the tests there are cell1 (E-UTRAN FDD) and 6 Bluetooth low energy (BLE) devices. The test consists of two successive time periods, with duration of T1 and T2, respectively. BT-RequestLocationInformation message shall be provided to the UE during T1. BLE devices only transmit signal during T2.
+
+**Table A.3.3.2.1-1: General test parameters for E-UTRAN TDD Bluetooth measurement under AWGN in non-DRX**
+
+| Parameter                                  | Unit | Value                                                      | Comment                                                                                                                                                                                                     |
+|--------------------------------------------|------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Active cell                                |      | Cell 1                                                     | Cell 1 is on E-UTRA RF channel number 1.                                                                                                                                                                    |
+| Bluetooth Low Energy (BLE) Devices         |      | BLE 1, BLE 2, BLE3, BLE4, BLE5 and BLE6                    | BLE 1 and BLE2 are on Bluetooth Advertising Channel 1 (2402 MHz).<br>BLE 3 and BLE4 are on Bluetooth Advertising Channel 2 (2426 MHz).<br>BLE 5 and BLE6 are on Bluetooth Advertising Channel 3 (2480 MHz). |
+| CP length                                  |      | Normal                                                     | Applicable to cell 1                                                                                                                                                                                        |
+| E-UTRA RF Channel Number                   |      | 1                                                          | One E-UTRA FDD carrier frequency is used.                                                                                                                                                                   |
+| Bluetooth Advertising Channel Number       |      | Channel 1:2402 MHz, Channel 2:2426 MHz, Channel 3:2480 MHz | Bluetooth advertising channels (2402, 2426, 2480 MHz)                                                                                                                                                       |
+| Bluetooth beacon signal broadcast interval | ms   | 100 ms                                                     |                                                                                                                                                                                                             |
+| DRX                                        |      | OFF                                                        |                                                                                                                                                                                                             |
+| Special subframe configuration             |      | 6                                                          | As specified in table 4.2-1 in TS 36.211 [16].<br>The same configuration applies to all cells.                                                                                                              |
+| Uplink-downlink configuration              |      | 1                                                          | As specified in table 4.2-2 in TS 36.211 [16].<br>The same configuration applies to all cells                                                                                                               |
+| T1                                         | s    | 5                                                          | During this time the cell1 shall be known to the UE; but cell2 shall be unknown to the UE.                                                                                                                  |
+| T2                                         | s    | 15                                                         | UE should report Bluetooth measurement information within 10.24s.                                                                                                                                           |
+
+**Table A.3.3.2.1-2: Cell specific test parameters for E-UTRAN TDD-WLAN event triggered reporting under AWGN in non-DRX**
+
+| Parameter | Unit | Cell 1 |    | BLE1, BLE2 |    | BLE3, BLE4 |    | BLE5, BLE6 |    |
+|-----------|------|--------|----|------------|----|------------|----|------------|----|
+|           |      | T1     | T2 | T1         | T1 | T1         | T2 | T1         | T2 |
+
+|                                                                    |                                                                                                                                                                                                                          |           |          |          |          |
+|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|----------|----------|----------|
+| E-UTRA RF Channel Number                                           |                                                                                                                                                                                                                          | 1         | N/A      | N/A      | N/A      |
+| Bluetooth Advertising Channel Number                               |                                                                                                                                                                                                                          | N/A       | 1        | 2        | 3        |
+| BW <sub>channel</sub>                                              |                                                                                                                                                                                                                          | 10MHz     | 2 MHz    | 2 MHz    | 2 MHz    |
+| PDSCH parameters:<br>DL Reference Measurement Channel              |                                                                                                                                                                                                                          | R.0 TDD   | N/A      | N/A      | N/A      |
+| PCFICH/PDCCH/PHICH parameters:<br>DL Reference Measurement Channel |                                                                                                                                                                                                                          | R.6 TDD   | N/A      | N/A      | N/A      |
+| OCNG Patterns                                                      |                                                                                                                                                                                                                          | OP.1 TDD  | N/A      | N/A      | N/A      |
+| PBCH_RA                                                            | dB                                                                                                                                                                                                                       | 0         | N/A      | N/A      | N/A      |
+| PBCH_RB                                                            | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PSS_RA                                                             | dB                                                                                                                                                                                                                       |           |          |          |          |
+| SSS_RA                                                             | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PCFICH_RB                                                          | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PHICH_RA                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PHICH_RB                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PDCCH_RA                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PDCCH_RB                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PDSCH_RA                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| PDSCH_RB                                                           | dB                                                                                                                                                                                                                       |           |          |          |          |
+| OCNG_RA <sup>Note 1</sup>                                          | dB                                                                                                                                                                                                                       |           |          |          |          |
+| OCNG_RB <sup>Note 1</sup>                                          | dB                                                                                                                                                                                                                       |           |          |          |          |
+| N <sub>oc1</sub> <sup>Note 2</sup>                                 | dBm/15 KHz                                                                                                                                                                                                               | -98       | N/A      | N/A      | N/A      |
+| N <sub>oc2</sub> <sup>Note 3</sup>                                 | dBm/2 MHz                                                                                                                                                                                                                | N/A       | -84      | -84      | -84      |
+| E <sub>s</sub> /N <sub>oc1</sub>                                   | dB                                                                                                                                                                                                                       | 3         | N/A      | N/A      | N/A      |
+| E <sub>s</sub> /I <sub>ot</sub> <sup>Note 4</sup>                  | dB                                                                                                                                                                                                                       | 3         |          |          |          |
+| RSRP <sup>Note 4</sup>                                             | dBm/15 kHz                                                                                                                                                                                                               | -95       |          |          |          |
+| SCH_RP <sup>Note 4</sup>                                           | dBm/15 kHz                                                                                                                                                                                                               | -95       |          |          |          |
+| I <sub>o</sub> <sup>Note 3</sup>                                   | dBm/Ch BW                                                                                                                                                                                                                | -<br>65.5 |          |          |          |
+| Bluetooth RSSI <sup>Note 4</sup>                                   | dBm/2 MHz                                                                                                                                                                                                                | N/A       | -        | -        | -        |
+|                                                                    |                                                                                                                                                                                                                          |           | infinity | -60      |          |
+|                                                                    |                                                                                                                                                                                                                          |           |          | infinity | -60      |
+|                                                                    |                                                                                                                                                                                                                          |           |          |          | infinity |
+|                                                                    |                                                                                                                                                                                                                          |           |          |          | -60      |
+| SINR <sup>Note 4</sup>                                             | dB                                                                                                                                                                                                                       | N/A       | -        | -        | -        |
+|                                                                    |                                                                                                                                                                                                                          |           | infinity | 63.2     |          |
+|                                                                    |                                                                                                                                                                                                                          |           |          | infinity | 63.2     |
+|                                                                    |                                                                                                                                                                                                                          |           |          |          | infinity |
+|                                                                    |                                                                                                                                                                                                                          |           |          |          | 63.2     |
+| Propagation Condition                                              |                                                                                                                                                                                                                          | AWGN      |          |          |          |
+| Antenna Configuration                                              |                                                                                                                                                                                                                          | 1x2       | -        | -        | -        |
+| Note 1:                                                            | OCNG shall be used such that all cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols.                                                                     |           |          |          |          |
+| Note 2:                                                            | Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for N <sub>oc1</sub> to be fulfilled.   |           |          |          |          |
+| Note 3:                                                            | Interference from other cells and noise sources not specified in the test is assumed to be constant over the bandwidth and time and shall be modelled as AWGN of appropriate power for N <sub>oc2</sub> to be fulfilled. |           |          |          |          |
+| Note 4:                                                            | Es/Iot, RSRP, SCH_RP, Io and WLAN RSSI have been derived from other parameters for information purposes. They are not settable parameters themselves.                                                                    |           |          |          |          |
+| Note 5:                                                            | The resources for uplink transmission are assigned to the UE prior to the start of time period T2.                                                                                                                       |           |          |          |          |
+
+##### A.3.3.2.2 Test Requirements
+
+The UE shall send *BT-ProvideLocationInformation*, with a measurement reporting delay less than 10.24s from the beginning of time period T2.
+
+The rate of correct events observed during repeated tests shall be at least 90% for each of the events.
+
+NOTE: The actual overall delays measured in the tests may be up to  $2 \times \text{TTI}_{\text{DCCH}}$  higher than the measurement reporting delays above because of TTI insertion uncertainty of the measurement report in DCCH.
+
+## A.4 Measurement Performance Requirements
+
+### A.4.1 General
+
+Unless explicitly stated otherwise:
+
+- Reported measurements shall be within defined range of accuracy limits defined in clause 5 for at least 90 % of the reported cases. If multiple measurement performance requirements are verified in the same test, the reported measurements for each requirement shall be within defined range of accuracy limits of the corresponding requirement defined in clause 5 for at least 90% of the reported cases.
+- Measurements are performed in RRC\_CONNECTED state.
+
+### A.4.2 MBS Code Phase Measurement Accuracy Requirements in AWGN
+
+#### A.4.2.1 Test Purpose and Environment
+
+The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits. This single test will verify the requirements in clauses 5.2, 5.3 and 5.4 for MBS measurements. The channel type for this test is AWGN, as specified in the appropriate sub-clause of clause 5. This test can be used for NR, UTRA and E-UTRA testing.
+
+In each test, there is one beacon transmitted in each of four consecutive beacon slots. The position of first of the four consecutive beacons in the beacon transmission period can be any slot, but it is static for the duration of the test. In other slots there are no simulated beacons. All beacons are in the same time slotted RF channel, with centre frequency of 925.977 MHz or set using the network assistance data. All beacons are of type TB1 (2 MHz) [7], or set using the network assistance data in Release 14, and the data transmitted is in Type 2 packets with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros.
+
+In the four slots containing beacon transmissions, every other slot shall contain a beacon with the higher signal strength beacon, and the other slots shall contain a beacon with the lower signal strength.
+
+The higher power beacons (-30 dBm) shall have code phase delay of  $1.6678 \times 10^{-4}$  ms (corresponding to 50 m) and the lower power beacons (-130 dBm) shall have code phase delay of  $5.00346 \times 10^{-3}$  ms (corresponding to 1500 m).
+
+Each of the beacons shall use a unique PN code chosen from the PN code list for TB1 [7].
+
+If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A.
+
+**Table A.4.2.1-1: General test parameters for Code Phase measurement Accuracy**
+
+| Parameter                                      | Unit    | Value                                | Comment                                                                  |
+|------------------------------------------------|---------|--------------------------------------|--------------------------------------------------------------------------|
+| Centre Frequency                               | MHz     | 925.977                              |                                                                          |
+| RF Channel                                     | N/A     | AWGN                                 |                                                                          |
+| MBS Beacon Configuration                       | N/A     | TB1 (2 MHz)                          |                                                                          |
+| MBS Packet Type                                | N/A     | Type 2                               |                                                                          |
+| Beacon PN Code                                 | Integer | Chosen from the PN code list for TB1 |                                                                          |
+| -30 dBm beacon transmitted Code Phase (delay)  | ms      | $1.6678 \times 10^{-4}$              | Corresponds to 50 m. Constant per beacon for the duration of the test.   |
+| -130 dBm beacon transmitted Code Phase (delay) | ms      | $5.00346 \times 10^{-3}$             | Corresponds to 1500 m. Constant per beacon for the duration of the test. |
+| $T_{\text{MBS\_meas}}$                         | ms      | 12000                                |                                                                          |
+
+**Table A.4.2.1-2: MBS Beacon Payload fields for Code Phase measurement Accuracy**
+
+| Parameter        | Unit    | Value                | Comment |
+|------------------|---------|----------------------|---------|
+| TxID             | Integer | Equal to Slot number |         |
+| Slot Index       | Integer | Equal to Slot number |         |
+| All other fields | N/A     | 0                    |         |
+
+#### A.4.2.2 Test Requirements
+
+The MBS Code Phase measurement accuracy shall fulfil the requirements in clauses 5.2, 5.3 and 5.4.
+
+### A.4.3 MBS Code Phase Measurement Accuracy Requirements in Multipath
+
+#### A.4.3.1 Test Purpose and Environment
+
+The purpose of this test is to verify that the MBS Code Phase measurement accuracy is within the specified limits. This test will verify the requirements in clause 5.5 for MBS measurements. The channel type for the test is specified in clause 5.5. This test can be used for NR, UTRA and E-UTRA testing.
+
+In this test, there is one beacon transmitted in each of two chosen slots. The position of the beacons in the beacon transmission period is static for the duration of the test. In other slots there are no simulated beacons. Both beacons are in the same time slotted RF channel, with centre frequency of 925.977 MHz or set using the network assistance data. All beacons are of type TB1 (2 MHz) [7], or set using the network assistance data in Release 14, and the data transmitted is in Type 2 packets with the following data fields: The MBS Transmitter ID and the Slot Index shall be set to the MBS slot number; All other beacon payload data shall be populated with zeros.
+
+Both beacon slots shall contain a beacon with the signal strength listed in clause 5.5.
+
+The beacons shall have code phase delay of  $1.6678 \times 10^{-4}$  ms (corresponding to 50 m).
+
+Each of the beacons shall use a unique PN code chosen from the PN code list for TB1 [7].
+
+If the UE supports MBS assistance data, the UE will receive the MBS assistance data for each beacon via LPP, according to Annex A.
+
+**Table A.4.3.1-1: General test parameters for Code Phase measurement Accuracy in Multipath**
+
+| Parameter                                     | Unit    | Value                                | Comment                                                                |
+|-----------------------------------------------|---------|--------------------------------------|------------------------------------------------------------------------|
+| Centre Frequency                              | MHz     | 925.977                              |                                                                        |
+| RF Channel                                    | N/A     | EPA 5 Hz                             |                                                                        |
+| MBS Beacon Configuration                      | N/A     | TB1 (2 MHz)                          |                                                                        |
+| MBS Packet Type                               | N/A     | Type 2                               |                                                                        |
+| Beacon PN Code                                | Integer | Chosen from the PN code list for TB1 |                                                                        |
+| -30 dBm beacon transmitted Code Phase (delay) | ms      | $1.6678 \times 10^{-4}$              | Corresponds to 50 m. Constant per beacon for the duration of the test. |
+| $T_{\text{MBS\_meas}}$                        | ms      | 12000                                |                                                                        |
+
+**Table A.4.3.1-2: MBS Beacon Payload fields for Code Phase measurement Accuracy**
+
+| Parameter        | Unit    | Value                | Comment |
+|------------------|---------|----------------------|---------|
+| TxID             | Integer | Equal to Slot number |         |
+| Slot Index       | Integer | Equal to Slot number |         |
+| All other fields | N/A     | 0                    |         |
+
+#### A.4.3.2 Test Requirements
+
+The MBS Code Phase measurement accuracy shall fulfil the requirements in clause 5.5.
+
+# --- Annex B (normative): Assistance data required for testing (Release 14 and beyond)
+
+## --- B.1 Introduction
+
+This annex defines the assistance data IEs available at the SS in all test cases where the UE supports MBS acquisition assistance data. Almanac assistance data will not be provided since there are only performance requirements for UE-Assisted mode. The acquisition assistance data shall be provided for all beacons.
+
+The information elements are given with reference to 3GPP TS 36.355 [3], where the details are defined.
+
+## --- B.2 MBS Assistance Data
+
+Table B.2-1 defines the acquisition assistance data elements which shall be provided to the UE. Assistance data IEs supported by the UE but not listed in Table B.2-1 shall not be sent.
+
+**Table B.2-1: Assistance Data to be provided to the UE for each beacon**
+
+| MBS Acquisition Assistance Data IE | Measurement reporting delay test case | MBS Code Phase Measurement accuracy test cases |
+|------------------------------------|---------------------------------------|------------------------------------------------|
+| transmitterID-r14                  | Yes                                   | Yes                                            |
+| mbsConfiguration-r14               | Yes                                   | Yes                                            |
+| pnCodeIndex-r14                    | Yes                                   | Yes                                            |
+| freq-r14                           | Yes                                   | Yes                                            |
+
+# Annex C (informative): Change history
+
+| Change history |             |           |      |     |     |                                                                                                                                                                                             |             |
+|----------------|-------------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting     | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                             | New version |
+| 2016-04        | RAN4#78 bis | R4-162662 |      |     |     | TS skeleton created from 3GPP TS template.                                                                                                                                                  | 0.0.1       |
+| 2016-05        | RAN4#78 bis | R4-164435 |      |     |     | The text proposal in R4-162662 agreed at RAN4#78bis is included.                                                                                                                            | 0.1.0       |
+| 2016-05        | RAN4#78 bis | R4-164777 |      |     |     | The test proposals in R4-164437, R4-164646 and R4-164647 are included.                                                                                                                      | 0.2.0       |
+| 2016-06        | RAN#72      | RP-160891 |      |     |     | TS agreed in R4-164777, with the version number incremented to 1.0.0, the date and Table of Contents updated and the change history updated. Editorial changes from MCC were also included. | 1.0.0       |
+| 2016-06        | RAN#72      |           |      |     |     | TR approved by RAN plenary                                                                                                                                                                  | 13.0.0      |
+| 2016-12        | RP-74       | RP-162396 | 0001 | 2   | F   | Removal of square brackets from MBS measurement accuracy requirements                                                                                                                       | 13.1.0      |
+| 2016-12        | RP-74       | RP-162396 | 0002 | -   | B   | R on Bluetooth Wifi requirement for indoor positioning                                                                                                                                      | 14.0.0      |
+| 2016-12        | RP-74       | RP-162396 | 0003 | -   | B   | Requirements for WLAN RSSI Measurement for Positioning                                                                                                                                      | 14.0.0      |
+| 2017-03        | RP-75       | RP-170564 | 0006 |     | B   | Addition of MBS Assistance Data related requirements for Further Indoor Positioning Enhancements                                                                                            | 14.1.0      |
+| 2017-06        | RP-76       | RP-171270 | 0008 |     | F   | InDoPos: WLAN requirements (Rel-14)                                                                                                                                                         | 14.2.0      |
+| 2017-06        | RP-76       | RP-171270 | 0012 |     | F   | InDoPos: Corrections to BT-LE requirements (Rel-14)                                                                                                                                         | 14.2.0      |
+| 2017-06        | RP-76       | RP-171270 | 0013 | 2   | F   | InDoPos: New WLAN delay test case in nominal conditions with LTE FDD and TDD (Rel-14)                                                                                                       | 14.2.0      |
+| 2017-06        | RP-76       | RP-171270 | 0014 | 1   | F   | InDoPos: New WLAN delay test case in dynamic range conditions with LTE FDD and TDD (Rel-14)                                                                                                 | 14.2.0      |
+| 2017-06        | RP-76       | RP-171270 | 0016 | 4   | B   | CR on test case for Bluetooth identification                                                                                                                                                | 14.2.0      |
+| 2017-09        | RP-77       | RP-171943 | 0017 | 1   | F   | InDoPos: Correction to WLAN positioning requirements and test (Rel-14)                                                                                                                      | 14.3.0      |
+| 2017-12        | RAN#78      | RP-172581 | 0018 |     | F   | LBS InDoPos: Removal of remaining square brackets from BT-LE requirements and test cases (Rel-14)                                                                                           | 14.4.0      |
+| 2018-03        | RAN#79      | RP-180297 | 0019 | 1   | F   | Change WLAN measurement reporting delay to 20 seconds<br>This CR was partially implemented as it clashed with CR#0024.                                                                      | 14.5.0      |
+| 2018-03        | RAN#79      | RP-180297 | 0020 |     | F   | Delete WLAN beacon interval test value                                                                                                                                                      | 14.5.0      |
+| 2018-03        | RAN#79      | RP-180297 | 0022 |     | F   | Clarification concerning assistance data for WLAN requirements                                                                                                                              | 14.5.0      |
+| 2018-03        | RAN#79      | RP-180297 | 0023 |     | F   | Deletion of optional IEs from WLAN test cases                                                                                                                                               | 14.5.0      |
+| 2018-03        | RAN#79      | RP-180297 | 0024 |     | F   | Clarifications to WLAN measurement requirements                                                                                                                                             | 14.5.0      |
+| 2018-06        | RAN#80      | RP-181116 | 0025 |     | F   | Editorial: corrections to 20 second reporting time in WLAN test cases                                                                                                                       | 14.6.0      |
+| 2018-06        | RAN#80      | RP-181116 | 0026 |     | F   | Additions and corrections to WLAN test cases for 2.4GHz and 5GHz WLAN bands                                                                                                                 | 14.6.0      |
+| 2018-06        | RAN#80      | RP-181116 | 0027 | 1   | F   | Clarification to RSSI reporting in WLAN test cases                                                                                                                                          | 14.6.0      |
+| 2018-06        | SA#80       |           |      |     |     | Update to Rel-15 version (MCC)                                                                                                                                                              | 15.0.0      |
+| 2018-12        | RAN#82      | RP-182361 | 0028 | 4   | F   | NR Revisions for Positioning Performance Requirements                                                                                                                                       | 15.1.0      |
+| 2019-03        | RAN#83      | RP-190402 | 0029 | 1   | F   | CR on WLAN and BT in 37.171                                                                                                                                                                 | 15.2.0      |
+| 2020-03        | RAN#87      | RP-200409 | 0032 |     | F   | Editorial change to TS 37.571-1 title                                                                                                                                                       | 15.3.0      |
+| 2020-06        | RAN#88      | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                                                                                                                                              | 16.0.0      |
+| 2020-09        | RAN#89      | RP-201512 | 0036 |     | A   | Changes to TS 37.171 title removing references to individual RATs                                                                                                                           | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37320/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/37_series/37320/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23768d8fc1c7b8063ea9dc0c44cec88740ab58c6
--- /dev/null
+++ b/marked/Rel-16/37_series/37320/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:16a378145040f338b838cc20837e252804d621ecff058df7e4edbd07a56a444c
+size 18625
diff --git a/marked/Rel-16/37_series/37320/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37320/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2cc39561648c33b20b5087884bc7e7e9daa5d05f
--- /dev/null
+++ b/marked/Rel-16/37_series/37320/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc4a6c118a3e003fc37f6f8ca2b7940b45ca469ef648d0270dad04cd4646ee24
+size 8225
diff --git a/marked/Rel-16/37_series/37320/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37320/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e17965f434b448b62c01a0ae74c96718f9e6b357
--- /dev/null
+++ b/marked/Rel-16/37_series/37320/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:898e1f88db795529aeb243f465b0abb43ad585b12af349ec0bf10e23947aa5b4
+size 5543
diff --git a/marked/Rel-16/37_series/37320/raw.md b/marked/Rel-16/37_series/37320/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ac040791f94af0542776e82ba15e8cc918e730c
--- /dev/null
+++ b/marked/Rel-16/37_series/37320/raw.md
@@ -0,0 +1,1120 @@
+
+
+# 3GPP TS 37.320 V16.8.0 (2022-03) ---
+
+*Technical Specification*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2 (Release 16)** ---
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is the tagline "A GLOBAL INITIATIVE" in a smaller, all-caps, sans-serif font. To the right of the "3GPP" text is a small "TM" symbol.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                     |    |
+|---------------------------------------------------------------------|----|
+| Foreword .....                                                      | 5  |
+| 1 Scope.....                                                        | 6  |
+| 2 References.....                                                   | 6  |
+| 3 Definitions, symbols and abbreviations .....                      | 7  |
+| 3.1 Definitions.....                                                | 7  |
+| 3.2 Symbols.....                                                    | 7  |
+| 3.3 Abbreviations .....                                             | 7  |
+| 4 Main concept and requirements .....                               | 9  |
+| 4.1 General .....                                                   | 9  |
+| 5 Functions and procedures.....                                     | 10 |
+| 5.1 General procedures.....                                         | 10 |
+| 5.1.1 Logged MDT procedures .....                                   | 10 |
+| 5.1.1.1 Measurement configuration .....                             | 10 |
+| 5.1.1.1.1 Configuration parameters.....                             | 11 |
+| 5.1.1.1.2 Configuration effectiveness.....                          | 12 |
+| 5.1.1.2 Measurement collection.....                                 | 13 |
+| 5.1.1.3 Measurement reporting.....                                  | 14 |
+| 5.1.1.3.1 Availability Indicator .....                              | 14 |
+| 5.1.1.3.2 Report retrieval.....                                     | 15 |
+| 5.1.1.3.3 Reporting parameters .....                                | 15 |
+| 5.1.1.4 MDT context handling.....                                   | 17 |
+| 5.1.2 Immediate MDT procedures.....                                 | 17 |
+| 5.1.2.1 Measurement configuration.....                              | 17 |
+| 5.1.2.2 Measurement reporting.....                                  | 18 |
+| 5.1.2.3 MDT context handling during handover .....                  | 18 |
+| 5.1.3 MDT Initiation.....                                           | 18 |
+| 5.1.4 UE capabilities.....                                          | 19 |
+| 5.1.5 Void.....                                                     | 20 |
+| 5.1.6 Accessibility measurements .....                              | 20 |
+| 5.2 E-UTRAN solutions.....                                          | 21 |
+| 5.2.1 RRC_CONNECTED.....                                            | 21 |
+| 5.2.1.1 Measurements and reporting triggers for Immediate MDT ..... | 21 |
+| 5.2.1.2 Enhancement to Radio Link Failure report.....               | 22 |
+| 5.2.1.3 Detailed Location Information.....                          | 23 |
+| 5.2.2 RRC_IDLE .....                                                | 23 |
+| 5.3 UTRAN solutions.....                                            | 23 |
+| 5.3.1 UTRA RRC Connected .....                                      | 23 |
+| 5.3.1.1 Measurements and reporting events for Immediate MDT .....   | 23 |
+| 5.3.1.2 Detailed Location Information.....                          | 25 |
+| 5.3.2 UTRA Idle .....                                               | 25 |
+| 5.4 NR solutions.....                                               | 25 |
+| 5.4.0 General .....                                                 | 25 |
+| 5.4.1 RRC_CONNECTED.....                                            | 25 |
+| 5.4.1.1 Measurements and reporting triggers for Immediate MDT ..... | 25 |
+| 5.4.1.2 Radio Link Failure report .....                             | 26 |
+| 5.4.1.3 Immediate MDT for MR-DC.....                                | 27 |
+| 5.4.2 RRC_IDLE & RRC_INACTIVE.....                                  | 27 |
+
+**Annex A (informative): Coverage use cases ..... 29**
+
+**Annex B (informative): QoS verification use cases ..... 30**
+
+**Annex C (informative): Measurements..... 31**
+
+**Annex D (informative): MBSFN use cases..... 32**
+
+**Annex E (informative): Change history ..... 33**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document provides an overview and overall description of the minimization of drive tests functionality.
+
+The document describes functions and procedures to support collection of UE-specific measurements for MDT using Control Plane architecture, for UTRAN, E-UTRAN and NR.
+
+Details of the signalling procedures for single-RAT operation are specified in the appropriate radio interface protocol specification. Network operation and overall control of MDT is described in OAM specifications.
+
+NOTE: The focus is on conventional macro cellular network deployments. In the current release no specific support is provided for H(e)NB deployments.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)".
+- [3] 3GPP TS 36.133: "Requirements for support of radio resource management (FDD)".
+- [4] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
+- [5] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
+- [6] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and configuration management".
+- [7] 3GPP TS 25.215: "Physical Layer; Measurements (FDD)".
+- [8] 3GPP TS 25.225: "Physical Layer; Measurements (TDD)".
+- [9] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer; Measurements".
+- [10] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC); Protocol Specification".
+- [11] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures".
+- [12] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2".
+- [13] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 – Measurements".
+- [14] 3GPP TS 25.321: "Medium Access Control (MAC) Protocol Specification".
+- [15] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
+
+- [16] 3GPP TS 38.133: "NR; Requirements for support of radio resource management".
+- [17] 3GPP TS 28.552: "Technical Specification Group Services and System Aspects; Management and orchestration; 5G performance measurements".
+- [18] 3GPP TS 38.314: "NR; Layer 2 Measurements".
+- [19] 3GPP TS 38.215: " NR; Physical layer measurements".
+- [20] 3GPP TS 38.213: " NR; Physical layer procedures for control".
+- [21] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
+- [22] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply.
+
+**Immediate MDT:** MDT functionality involving measurements performed by the UE in CONNECTED state and reporting of the measurements to RAN available at the time of reporting condition as well as measurements by the network for MDT purposes.
+
+**Logged MDT:** MDT functionality involving measurement logging by UE in IDLE mode, INACTIVE state, CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used (when UE is in UTRA) for reporting to eNB/RNC/gNB at a later point in time, and logging of MBSFN measurements by E-UTRA UE in IDLE and CONNECTED modes.
+
+**Management Based MDT PLMN List:** MDT PLMN List applicable to management based MDT.
+
+**MDT measurements:** Measurements determined for MDT.
+
+**MDT PLMN List:** A list of PLMNs where MDT is allowed for a user. It is a subset of the EPLMN list and RPLMN at the time when MDT is initiated.
+
+**Signalling Based MDT PLMN List:** MDT PLMN List applicable to signalling based MDT.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |               |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|       |                               |
+|-------|-------------------------------|
+| ACK   | Acknowledgement               |
+| AICH  | Acquisition Indicator CHannel |
+| BLER  | Block Error Rate              |
+| BSSID | Basic Service Set Identifier  |
+| CA    | Carrier Aggregation           |
+| CDMA  | Code Division Multiple Access |
+| CN    | Core Network                  |
+| CPICH | Common Pilot CHannel          |
+| DCH   | Dedicated CHannel             |
+
+|         |                                                          |
+|---------|----------------------------------------------------------|
+| DL      | Downlink                                                 |
+| DRX     | Discontinuous Reception                                  |
+| ECGI    | E-UTRAN Cell Global Identifier                           |
+| E-CID   | Enhanced Cell-ID (positioning method)                    |
+| E-DCH   | Enhanced Uplink DCH                                      |
+| EDGE    | Enhanced Data rates for GSM Evolution                    |
+| E-RUCCH | E-DCH Random Access Uplink Control CHannel               |
+| eNB     | Evolved NodeB                                            |
+| EPLMN   | Equivalent PLMN                                          |
+| E-UTRA  | Evolved UTRA                                             |
+| E-UTRAN | Evolved UTRAN                                            |
+| FACH    | Forward Access CHannel                                   |
+| FDD     | Frequency Division Duplex                                |
+| FIFO    | First Input First Output                                 |
+| FPACH   | Fast Physical Access CHannel                             |
+| GERAN   | GSM EDGE Radio Access Network                            |
+| gNB     | Next Generation Node B                                   |
+| GNSS    | Global Navigation Satellite System                       |
+| HESSID  | Homogenous Extended Service Set Identifier               |
+| HOF     | Handover Failure                                         |
+| IMEI-SV | International Mobile Equipment Identity Software Version |
+| IMSI    | International Mobile Subscriber Identity                 |
+| IP      | Internet Protocol                                        |
+| ISCP    | Interference on Signal Code Power                        |
+| LA      | Location Area                                            |
+| LTE     | Long Term Evolution                                      |
+| MAC     | Medium Access Control                                    |
+| MBMS    | Multimedia Broadcast Multicast Service                   |
+| MBSFN   | MBMS Single Frequency Network                            |
+| MDT     | Minimization of Drive-Tests                              |
+| NG-RAN  | Next Generation RAN                                      |
+| NR      | New Radio                                                |
+| OAM     | Operation and Maintenance                                |
+| P-CCPCH | Primary Physical Common Control CHannel                  |
+| PCH     | Paging CHannel                                           |
+| PCI     | Physical Cell Id                                         |
+| PDCP    | Packet Data Convergence Protocol                         |
+| PH      | Power Headroom                                           |
+| PLMN    | Public Land Mobile Network                               |
+| PS      | Packet Switched                                          |
+| QCI     | QoS Class Identifier                                     |
+| QoS     | Quality of Service                                       |
+| RA      | Routing Area                                             |
+| RAB     | Radio Access Bearer                                      |
+| RAT     | Radio Access Technology                                  |
+| RB      | Radio Bearer                                             |
+| RF      | Radio Frequency                                          |
+| RLC     | Radio Link Control                                       |
+| RLF     | Radio Link Failure                                       |
+| RNC     | Radio Network Controller                                 |
+| RPLMN   | Registered PLMN                                          |
+| RRC     | Radio Resource Control                                   |
+| RRM     | Radio Resource Management                                |
+| RSCP    | Received Signal Code Power                               |
+| RSRP    | Reference Signal Received Power                          |
+| RSRQ    | Reference Signal Received Quality                        |
+| RSSI    | Received Signal Strength Indicator                       |
+| RTT     | Round Trip Time                                          |
+| RTWP    | Received Total Wideband Power                            |
+| SCell   | Secondary Cell                                           |
+| SIR     | Signal to Interference Ratio                             |
+| SINR    | Signal to Noise plus Interference Ratio                  |
+
+|       |                                            |
+|-------|--------------------------------------------|
+| SNR   | Signal to Noise Ratio                      |
+| SON   | Self Organizing/Optimizing Network         |
+| SRB   | Signalling Radio Bearer                    |
+| SRNC  | Serving RNC                                |
+| SSB   | Synchronization Signal Block               |
+| SSID  | Service Set Identifier                     |
+| TA    | Tracking Area                              |
+| TCE   | Trace Collection Entity                    |
+| TDD   | Time Division Duplex                       |
+| UE    | User Equipment                             |
+| UL    | Uplink                                     |
+| UMTS  | Universal Mobile Telecommunication System  |
+| UPH   | Uplink PH                                  |
+| URA   | UTRAN Registration Area                    |
+| UTRA  | Universal Terrestrial Radio Access         |
+| UTRAN | Universal Terrestrial Radio Access Network |
+
+# --- 4 Main concept and requirements
+
+## 4.1 General
+
+The general principles and requirements guiding the definition of functions for Minimization of drive tests are the following:
+
+### 1. MDT mode
+
+There are two modes for the MDT measurements: Logged MDT and Immediate MDT. There are also cases of measurement collection not specified as either immediate or logged MDT, such as Accessibility measurements.
+
+### 2. UE measurement configuration
+
+It is possible to configure MDT measurements for the UE logging purpose independently from the network configurations for normal RRM purposes. However, in most cases, the availability of measurement results is conditionally dependent on the UE RRM configuration.
+
+### 3. UE measurement collection and reporting
+
+UE MDT measurement logs consist of multiple events and measurements taken over time. The time interval for measurement collection and reporting is decoupled in order to limit the impact on the UE battery consumption and network signalling load.
+
+### 4. Geographical scope of measurement logging
+
+It is possible to configure the geographical area where the defined set of measurements shall be collected.
+
+### 5. Location information
+
+The measurements shall be linked to available location information and/or other information or measurements that can be used to derive location information.
+
+### 6. Time information
+
+The measurements in measurement logs shall be linked to a time stamp.
+
+### 7. Sensor information
+
+The measurements can be linked to available sensor information that can be used to derive UE orientation in a global coordinate system, the uncompensated barometric pressure and the UE speed.
+
+### 8. UE capability information
+
+The network may use UE capabilities to select terminals for MDT measurements.
+
+### 9. Dependency on SON
+
+The solutions for MDT are able to work independently from SON support in the network. Relation between measurements/solution for MDT and UE side SON functions shall be established in a way that re-use of functions is achieved where possible.
+
+### 10. Dependency on TRACE
+
+The subscriber/cell trace functionality is reused and extended to support MDT. If the MDT is initiated towards a specific UE (e.g. based on IMSI, IMEI-SV, etc.), the signalling based trace procedure is used, otherwise the management based trace procedure (or cell traffic trace procedure) is used. Network signalling and overall control of MDT is described in TS 32.422 [6].
+
+The solutions for MDT shall take into account the following constraints:
+
+### 1. UE measurements
+
+The UE measurement logging mechanism is an optional feature. In order to limit the impact on UE power consumption and processing, the UE measurement logging should as much as possible rely on the measurements that are available in the UE according to radio resource management enforced by the access network.
+
+### 2. Location information
+
+The availability of location information is subject to UE capability and/or UE implementation. Solutions requiring location information shall take into account power consumption of the UE due to the need to run its positioning components.
+
+# --- 5 Functions and procedures
+
+## 5.1 General procedures
+
+### 5.1.1 Logged MDT procedures
+
+Support of Logged MDT complies with the principles for IDLE and INACTIVE state measurements in the UE specified in TS 25.133[2], TS 36.133 [3] and TS 38.133 [16] and principles for IDLE and CONNECTED mode MBSFN measurements in the UE specified in TS 36.133 [3].
+
+NOTE: It should be noted the established principles may result in different logged information in different UEs.
+
+Furthermore, measurement logging is differentiated based on UE states in idle mode i.e. camped normally, any cell selection or camped on any cell. The UE shall perform measurement logging in "camped normally" state and "any cell selection" state. In "camped on any cell" state the UE is not required to perform MDT measurement logging (including time and location information).
+
+For Logged MDT, the configuration will always be done in cells of the same RAT type. However, measurements included in the logged MDT report comprises of measurements from the same RAT type (serving cell measurements, intra-frequency and inter-frequency neighbor cell measurements) and different RAT types (inter-RAT neighbor cell measurements).
+
+Logging of MBSFN measurements is only applicable to E-UTRA.
+
+#### 5.1.1.1 Measurement configuration
+
+Logged MDT measurements are configured with a MDT Measurement Configuration procedure, as shown in Figure 5.1.1.1-1.
+
+![Sequence diagram showing the MDT measurement configuration for Logged MDT. A box labeled '(E-)UTRAN or NR' sends a message labeled 'LoggedMeasurementConfiguration' to a box labeled 'UE'.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant Network as (E-)UTRAN or NR
+    Note right of Network: LoggedMeasurementConfiguration
+    Network->>UE: LoggedMeasurementConfiguration
+  
+```
+
+Sequence diagram showing the MDT measurement configuration for Logged MDT. A box labeled '(E-)UTRAN or NR' sends a message labeled 'LoggedMeasurementConfiguration' to a box labeled 'UE'.
+
+**Figure 5.1.1.1-1: MDT measurement configuration for Logged MDT**
+
+Network initiates the procedure to UE in RRC Connected by sending *LoggedMeasurementConfiguration* message, which is used to transfer configuration parameters for Logged MDT. This is a unidirectional RRC signalling procedure.
+
+A release operation for logged measurement configuration in the UE is realized only by configuration replacement when the configuration is overwritten or by configuration clearance in case a duration timer stopping or expiration condition is met.
+
+##### 5.1.1.1.1 Configuration parameters
+
+The logged measurement configuration consists of:
+
+- configuration of downlink pilot strength measurements logging for (E-)UTRA and NR.
+- configuration of MBSFN measurement logging for E-UTRA.
+- configuration of the triggering of logging events:
+  - for (E-)UTRAN only periodic measurement trigger is supported, for which the logging interval is configurable. The parameter specifies the periodicity for storing MDT measurement results. It should be configured in seconds in multiples of the applied IDLE mode DRX, i.e. multiples of 1.28s which is either a factor or multiple of the IDLE mode DRX. The UE behaviour is unspecified when the UE is configured with a DRX cycle larger than the logging interval.
+  - for NR:
+    - periodic measurement trigger is supported, for which the logging interval is configurable. The parameter specifies the periodicity for storing MDT measurement results.
+    - event-based trigger is supported, for which the logging interval is configurable, which determines periodical logging of available data (e.g. time stamp, location information), and the following two types of events are supported:
+      - measurement quantity-based event L1, for which the event threshold, hysteresis, and time to trigger are configurable. If the configured time to trigger is not a multiple of the DRX cycle, then the UE uses the next multiple of DRX cycle duration that is larger than the time to trigger for evaluating the event L1;
+      - out-of-coverage detection trigger.
+
+NOTE: The logging configuration for event-based and periodical DL pilot strength logged measurements can be configured independently. Only one type of event can be configured to the UE.
+
+- configuration of the logging duration. This configuration parameter defines a timer activated at the moment of configuration, that continues independent of state changes, RAT or RPLMN change. When the timer expires the logging is stopped and the configuration is cleared (except for the parameters that are required for further reporting e.g. network absolute time stamp, trace reference, trace recording session reference and TCE Id).
+
+- network absolute time stamp to be used as a time reference to UE.
+- Trace Reference parameter as indicated by the OAM configuration as specified in TS 32.422 [6].
+- Trace Recording Session Reference as indicated by the OAM configuration as specified in TS 32.422 [6].
+- TCE Id as indicated by the OAM configuration as specified in TS 32.422 [6].
+- (optionally) MDT PLMN List, indicating the PLMNs where measurement collection and log reporting is allowed. It is either the Management Based MDT PLMN List or the Signalling Based MDT PLMN List, depending on how the Logged MDT task was initiated (see 5.1.3).
+- (optionally) configuration of a logging area. A UE will log measurements as long as it is within the configured logging area. The scope of the logging area may consist of one of:
+  - a list of up to 32 global cell identities. If this list is configured, the UE will only log measurements when camping in any of these cells
+  - a list of up to 8 TAs or 8 LAs or 8 RAs. If this list is configured, the UE will only log measurements when camping in any cell belonging to the preconfigured TA/LA/RAs.
+- The configured logging area can span PLMNs in the MDT PLMN List. If no area is configured, the UE will log measurements throughout the PLMNs of the MDT PLMN list.
+- (optionally) for NR, configuration of a list of neighbouring frequencies and/or cells, indicating the UE to include neighbouring cell's measurements as indicated in the list in the logged MDT report.
+- (optionally) for E-UTRA, configuration of target MBSFN area(s) for MBSFN measurement logging. If target MBSFN area(s) is configured, UE applies it in addition to other restrictions such as the logging area. The UE will log measurements as long as it receives MBMS service from an indicated target MBSFN area and is within the configured logging area. The target MBSFN area(s) is defined by a list of up to 8 entries, where each entry indicates a carrier frequency and optionally indicates a specific MBSFN area on a carrier frequency.
+- (optionally) configuration of the WLAN access point names, indicating the UE to attempt to obtain WLAN measurements associated to these access points.
+- (optionally) configuration of the Bluetooth beacon names, indicating the UE to attempt to obtain Bluetooth measurements associated to these beacons.
+- (optionally) for NR, configuration of the sensor names, indicating the UE to attempt to obtain sensor measurements.
+
+##### 5.1.1.1.2 Configuration effectiveness
+
+The logged measurement configuration is provided in a cell by dedicated control while UE is in CONNECTED and implies:
+
+- logged measurement configuration for downlink pilot strength measurements (or events) logging is active
+  - in IDLE UE state in E-UTRAN, or
+  - in IDLE mode, CELL\_PCH and URA\_PCH states in UTRAN, or
+  - in CELL\_FACH state when second DRX cycle is used in UTRAN, or
+  - in IDLE and INACTIVE states in NR
+  - until logging duration timer expires or stops
+- logged measurement configuration for MBSFN measurement logging is active
+  - in IDLE and CONNECTED UE states in E-UTRAN
+  - until logging duration timer expires or stops
+
+- logged measurement configuration and logs are maintained when the UE is in any state as described above, despite multiple periods interrupted by UE state transitions, e.g. for downlink pilot strength measurements when the UE is in CONNECTED state for E-UTRAN and NR and CELL\_DCH, CELL\_FACH state when second DRX cycle is not used in UTRAN
+- logged measurement configuration and logs are maintained when the UE is in any state as described above in that RAT, despite multiple periods interrupted by UE presence in another RAT
+
+There is only one RAT-specific logged measurement configuration for Logged MDT in the UE. When the network provides a configuration, any previously configured logged measurement configuration will be entirely replaced by the new one. Moreover, logged measurements corresponding to the previous configuration will be cleared at the same time. It is left up to the network to retrieve any relevant data before providing a new configuration.
+
+NOTE: The network may have to do inter-RAT coordination.
+
+When a logging area is configured, logged MDT measurements are performed as long as the UE is within this logging area. For NR, when determining whether a cell is part of the logging area, only the first entry of the *plmn-IdentityList* in the first entry of the *PLMN-IdentityInfoList* (in SIB1), and cellIdentity and TAC corresponding to the first entry of the *PLMN-IdentityInfoList* are considered. If no logging area is configured, logged MDT measurements are performed as long as the RPLMN is part of the MDT PLMN list. When the UE is not in the logging area or RPLMN is not part of the MDT PLMN list, the logging is suspended, i.e. the logged measurement configuration and the log are kept but measurement results are not logged. In addition, for MBSFN logged measurements, logged MDT measurements are performed in logging intervals when the UE receives MBMS service from a MBSFN area according to the target MBSFN area(s) configuration. When the UE is not in the logging area or does not receive MBMS service from a MBSFN area that matches the target MBSFN area(s) configuration in the logging interval the logged measurement configuration and the log are kept but measurement results are not logged.
+
+NOTE: The logging duration timer continues.
+
+In case the new PLMN that does not belong to the MDT PLMN list provides a logged measurement configuration any previously configured logged measurement configuration and corresponding log are cleared and overwritten without being retrieved.
+
+#### 5.1.1.2 Measurement collection
+
+In "camped normally" state, a UE shall perform logging as per the logged measurement configuration. This state includes a period between cell selection criteria not being met and UE entering "any cell selection" state, i.e. 10 s for E-UTRA (See TS 36.133 [3]) or 12 s for UTRA (See TS 25.133 [2]) or 10s for NR (See TS 38.133 [16]).
+
+In "any cell selection" state, a UE shall perform logging of available information (i.e. at least indicator 'anyCellSelectionDetected', time stamp, and the available location information). In "camped on any cell" state, the periodic logging stops. However, it should be noted that the duration timer is kept running. When the UE re-enters "camped normally" state and the duration timer has not expired, the periodic logging is restarted based on new DRX and logging resumes automatically (with a leap in time stamp).
+
+When an E-UTRA UE detects an in-device coexistence problem that may affect the logged measurement results, the UE shall stop measurement logging, indicate in the log that an in-device coexistence problem has occurred, and keep the duration timer running. When the in-device coexistence problem is no longer present, and the duration timer has not expired, the logging resumes, with a leap in time stamp.
+
+For E-UTRA MBSFN measurement logging, the UE shall perform MBSFN measurements only when receiving MBMS service, and measurement logging is performed only for logging intervals for which MBSFN measurements are available. The UE shall perform MBSFN measurements and MBSFN measurement logging in both IDLE and CONNECTED modes.
+
+NOTE: the UE is only required to perform MBSFN measurements when receiving MBMS service of the MBSFN area(s) targeted for logging.
+
+For WLAN measurement logging and Bluetooth measurement logging, the UE shall perform WLAN and Bluetooth measurements, respectively, only when indicated in the corresponding configuration. The measurement logging is performed only for logging intervals for which WLAN and Bluetooth measurements are available, respectively.
+
+The measurement quantities for downlink pilot strength measurement logging are fixed and consist of both RSRP and RSRQ for EUTRA, both RSCP and Ec/No for UTRA FDD, P-CCPCH RSCP for UTRA 1.28 Mcps TDD, Rxlev for
+
+GERAN, and Pilot Pn Phase and Pilot Strength for CDMA2000 if the serving cell is EUTRAN cell, and both RSRP and RSRQ for NR.
+
+For NR, in addition to the logged measurement quantities of the camped cell, the best beam index (SSB Index) as along with the best beam RSRP/RSRQ are logged as well as the 'number of good beams' (the number of SSBs that are above the configured threshold i.e., *absThreshSS-BlocksConsolidation*, if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. Sensor measurements are logged if available.
+
+The measurement quantities for E-UTRA MBSFN measurement logging are fixed and consist of MBSFN RSRP, MBSFN RSRQ, BLER for signalling and BLER for data per MCH, in addition to the measurement quantities for downlink pilot strength measurements.
+
+The measurement quantities for WLAN measurement logging are fixed and consist of BSSID, SSID, HESSID of WLAN APs. If configured by the network, optionally available RSSI and RTT can be included.
+
+The measurement quantity for Bluetooth measurement logging is fixed and consists of MAC address of Bluetooth beacons. If configured by the network, optionally available RSSI can be included.
+
+UE collects MDT measurements and continues logging according to the logged measurement configuration until UE memory reserved for MDT is full. In this case the UE stops logging, stops the log duration timer and starts the 48 hour timer.
+
+#### 5.1.1.3 Measurement reporting
+
+##### 5.1.1.3.1 Availability Indicator
+
+A UE configured to perform Logged MDT downlink pilot strength measurements indicates the availability of Logged MDT measurements, by means of a one bit, in RRCConnectionSetupComplete or RRCSsetupComplete or RRCConnectionResumeComplete or RRCResumeComplete message during connection establishment. Furthermore, the indicator (possibly updated) shall be provided within:
+
+- E-UTRAN handover and re-establishment;
+- UTRAN procedures involving the change of SRNC (SRNC relocation), CELL UPDATE, URA UPDATE messages as well as MEASUREMENT REPORT message in case of state transition to CELL\_FACH without CELL UPDATE;
+- NR re-establishment, reconfiguration.
+
+The UE includes the indication in one of these messages at every transition to RRC Connected mode even though the logging period has not ended, upon connection to RAT which configured the UE to perform Logged MDT measurements and RPLMN which is equal to a PLMN in the MDT PLMN list.
+
+A E-UTRA UE configured to perform Logged MDT MBSFN measurements indicates the availability of Logged MDT MBSFN measurements, by means of an indicator, in RRCConnectionSetupComplete message during connection establishment. The indicator (possibly updated) shall be provided within E-UTRAN also at handover and re-establishment, except when the logged measurement configuration is active in CONNECTED mode, i.e. except when the logging campaign is still ongoing.
+
+A E-UTRA UE configured to perform Logged MDT WLAN measurements indicates the availability of Logged MDT WLAN measurements, by means of an indicator, in RRCConnectionSetupComplete message or RRCConnectionResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCConnectionReconfigurationComplete message, RRCConnectionReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended.
+
+A E-UTRA UE configured to perform Logged MDT Bluetooth measurements indicates the availability of Logged MDT Bluetooth measurements, by means of an indicator, in RRCConnectionSetupComplete message or RRCConnectionResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCConnectionReconfigurationComplete message, RRCConnectionReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended.
+
+A NR UE configured to perform Logged MDT WLAN measurements indicates the availability of Logged MDT WLAN measurements, by means of an indicator, in RRCSetupComplete message or RRCResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCReconfigurationComplete message, RRCReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended.
+
+A NR UE configured to perform Logged MDT Bluetooth measurements indicates the availability of Logged MDT Bluetooth measurements, by means of an indicator, in RRCSetupComplete message or RRCResumeComplete message during connection establishment. Furthermore, the indicator can be included in some uplink RRC messages, i.e., RRCReconfigurationComplete message, RRCReestablishmentComplete message, or UEInformationResponse message, at every transition to RRC Connected mode even though the logging period has not ended.
+
+An indicator shall be also provided in UEInformationResponse message during MDT report retrieval in case the UE has not transferred the total log in one RRC message in order to indicate the remaining data availability.
+
+The UE will not indicate the availability of MDT measurements in another RAT or in a PLMN that is not in the MDT PLMN list.
+
+The network may decide to retrieve the logged measurements based on this indication. In case Logged MDT measurements are retrieved before the completion of the pre-defined logging duration, the reported measurement results are deleted, but MDT measurement logging will continue according to ongoing logged measurement configuration.
+
+In case the network does not retrieve Logged MDT measurements, UE should store non-retrieved measurements for 48 hours from the moment the duration timer for logging expired. There is no requirement to store non-retrieved data beyond 48 hours. In addition, all logged measurement configuration and the log shall be removed by the UE at switch off or detach.
+
+##### 5.1.1.3.2 Report retrieval
+
+For Logged MDT the measurement reporting is triggered by an on-demand mechanism, i.e. the UE is asked by the network to send the collected measurement logs via RRC signalling. UE Information procedure defined in TS 25.331 [4] and TS 36.331 [5] and TS 38.331 [15] is used to request UE to send the collected measurement logs. The reporting may occur in different cells than which the logged measurement configuration is signalled.
+
+Transport of Logged MDT reports in multiple RRC messages is supported. With every request, the network may receive a part of the total UE log. To indicate the reported data is a segment, the UE shall include data availability indicator in UEInformationResponse message to convey the information that further measurement information is available, as specified in 5.1.1.3.1. In multiple RRC transmissions for segmented Logged MDT reporting, FIFO order is followed, i.e. the UE should provide oldest available measurement entries in earliest message. There is no requirement specified on the size of particular reporting parts. However, each reported part should be "self-decodable", i.e. interpretable even in case all the other parts are not available.
+
+The UE shall send an empty report when retrieval is attempted and the RPLMN is not in the MDT PLMN list.
+
+##### 5.1.1.3.3 Reporting parameters
+
+For downlink pilot strength measurements, the logged measurement report consists of measurement results for the serving cell (the measurement quantity), available UE measurements performed in idle or inactive for intra-frequency/inter-frequency/inter-RAT, time stamp and location information.
+
+For E-UTRA MBSFN measurements logging, the logged measurement report consists of MBSFN measurement results from target MBSFN area(s), if configured, and available downlink pilot strength measurement results. Inter-RAT downlink pilot strength measurements are not required to be logged.
+
+For WLAN and Bluetooth measurement logging, the logged measurement reports consist of WLAN and Bluetooth measurement results, respectively.
+
+The number of neighbouring cells to be logged is limited by a fixed upper limit per frequency for each category below. The UE should log the measurement results for the neighbouring cells, if available, up to:
+
+- 6 for intra-frequency neighbouring cells;
+- 3 for inter-frequency neighbouring cells per frequency;
+
+- 3 for GERAN neighbouring cells per frequency;
+- 3 for UTRAN (if non-serving) neighbouring cells per frequency;
+- 3 for E-UTRAN (if non-serving) neighbouring cells per frequency;
+- 3 for NR (if non-serving) neighbouring cells per frequency;
+- 3 for CDMA2000 (if serving is E-UTRA) neighbouring cells per frequency;
+- 32 for WLAN APs;
+- 32 for Bluetooth Beacons.
+
+NOTE: UE in NR IDLE or INACTIVE state will not log measurements from UMTS or GSM.
+
+The measurement reports for neighbour cells consist of:
+
+- Physical cell identity of the logged cell;
+- Carrier frequency;
+- RSRP and RSRQ for EUTRA and NR;
+- RSCP and Ec/No for UTRA FDD,
+- P-CCPCH RSCP for UTRA 1.28 Mcps TDD;
+- Rxlev for GERAN;
+- Pilot Pn Phase and Pilot Strength for CDMA2000;
+- RSSI and RTT for WLAN APs;
+- RSSI for Bluetooth Beacons.
+
+For any logged cell (serving or neighbour), latest available measurement result made for cell reselection purposes is included in the log only if it has not already been reported.
+
+While logging neighbour cells measurements, the UE shall determine a fixed number of best cells based on the measurement quantity used for ranking during cell reselection per frequency or RAT.
+
+The MBSFN measurement results consist of, per MBSFN area where MBMS service is received:
+
+- MBSFN area identity;
+- Carrier frequency;
+- MBSFN RSRP;
+- MBSFN RSRQ;
+- MCH BLER for signalling;
+- MCH BLER for data, and related MCH index.
+
+The WLAN measurement results consist of, per wireless network served by the WLAN AP:
+
+- BSSID, SSID and HESSID;
+- RSSI for WLAN;
+- RTT.
+
+The Bluetooth measurement results consist of, per wireless network served by the Bluetooth beacon:
+
+- MAC address;
+- RSSI for Bluetooth.
+
+Measurements are performed in accordance with requirements defined in TS 25.133 [2] and TS 36.133 [3] and TS 38.133 [16].
+
+The measurement report is self contained, i.e. the RAN node is able to interpret the Logged MDT reporting results even if it does not have access to the logged measurement configuration. Each measurement report also contains the necessary parameters for the network to be able to route the reports to the correct TCE and for OAM to identify what is reported. The parameters are sent to the UE in the logged configuration message, see clause 5.1.1.1.1.
+
+For each MDT measurement the UE includes a relative time stamp. The base unit for time information in the Logged MDT reports is the second. In the log associated to periodical logging configuration, the time stamp indicates the point in time when periodic logging timer expires. The time stamp is counted in seconds from the moment the logged measurement configuration is received at the UE, relative to the absolute time stamp received within the configuration. The absolute time stamp is the current network time at the point when Logged MDT is configured to the UE. The UE echoes back this absolute reference time. The time format for Logged MDT report is: *YY-MM-DD HH:MM:SS*.
+
+Location information is based on available location information in the UE. Thus, the Logged MDT measurements are tagged by the UE with location data in the following manner:
+
+- ECGI, Cell-Id or NCGI in TS 38.300 [22] of the serving cell when the measurement was taken is always included in E-UTRAN, UTRAN or NR respectively;
+- Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included. UE tags available detailed location information only once with upcoming measurement sample, and then the detailed location information is discarded, i.e. the validity of detailed location information is implicitly assumed to be one logging interval;
+- For NR, sensor information (i.e. uncompensated barometric pressure measurement, UE speed and UE orientation) can be included, if available in the UE when the measurement was taken.
+
+NOTE: The neighbour cell measurement information that is provided by the UE may be used to determine the UE location (RF fingerprint).
+
+Depending on location information availability, measurement log/report consists of:
+
+- time information, RF measurements, RF fingerprints; or
+  - time information, RF measurements, detailed location information (e.g. GNSS location information);
+- time information, RF measurements, detailed location information, sensor information.
+
+#### 5.1.1.4 MDT context handling
+
+For Logged MDT in IDLE, CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used and INACTIVE, no need is identified to transfer an MDT context (any related configuration information about measurement and reporting) between (e/g)NBs/RNCs if corresponding MDT configuration has already been configured to UE. In addition, MDT context is assumed to be released in the RAN nodes when the UE is in IDLE and INACTIVE if corresponding MDT configuration has already been configured to UE.
+
+For UE in INACTIVE, the MDT context handling during cell reselection as described in 5.4.2 apply.
+
+### 5.1.2 Immediate MDT procedures
+
+#### 5.1.2.1 Measurement configuration
+
+For Immediate MDT, RAN measurements and UE measurements can be configured. The configuration for UE measurements is based on the existing RRC measurement procedures for configuration and reporting with some extensions for location information.
+
+NOTE: No extensions related to time stamp are expected for Immediate MDT i.e. time stamp is expected to be provided by eNB/RNC/gNB.
+
+If area scope is included in the MDT configuration provided to the RAN, the UE is configured with respective measurement when the UE is connected to a cell that is part of the configured area scope.
+
+#### 5.1.2.2 Measurement reporting
+
+For Immediate MDT, the UE provides detailed location information (e.g. GNSS location information) if available. The UE also provides available neighbour cell measurement information that may be used to determine the UE location (RF fingerprint). ECGI, Cell-Id, or CellIdentity of the serving cell when the measurement was taken is always assumed known in E-UTRAN, UTRAN or NR respectively.
+
+The location information which comes with UE radio measurements for MDT can be correlated with other MDT measurements, e.g. RAN measurements. For MDT measurements where UE location information is provided separately, it is assumed that the correlation of location information and MDT measurements should be done in the TCE based on time-stamps.
+
+#### 5.1.2.3 MDT context handling during handover
+
+The measurements configured in the UE for Immediate MDT should fully comply with the transferring and reconfiguration principles for the current measurements configured in the UE for RRM purpose during handover (including conformance with Rel-8 and Rel-9).
+
+The target node releases the measurements configured in the UE for immediate MDT which are no longer needed based on any MDT trace configuration it receives or does not receive.
+
+In addition, MDT configuration handling during handover depends on MDT initiation from OAM defined in clause 5.1.3:
+
+- The MDT configuration configured by management based trace function will not propagate during handover.
+- For LTE, the MDT configuration received by signalling based trace messages for a specific UE will propagate during intra-PLMN handover, and may propagate during inter-PLMN handover if the Signalling Based MDT PLMN List is available and includes the target PLMN. This behaviour applies also for MDT configuration that includes area scope, regardless of whether the source or target cell is part of the configured area scope. This behaviour applies also for Xn inter-RAT handover.
+- For UMTS, the MDT configuration received by signalling based trace messages for a specific UE will continue during intra-PLMN handover, and may continue during inter-PLMN handover if the Signalling Based MDT PLMN List is available and includes the target PLMN, except for the case of SRNS relocation.
+- For NR, the MDT configuration received by signalling based trace messages for a specific UE will propagate during intra-PLMN handover, and may propagate during inter-PLMN handover if the Signalling Based MDT PLMN List is available and includes the target PLMN. This behaviour applies also for MDT configuration that includes area scope, regardless of whether the source or target cell is part of the configured area scope. This behaviour applies also for Xn inter-RAT handover.
+
+NOTE: In the case of SRNS relocation, MDT may be reactivated by the Core Network following a successful relocation.
+
+### 5.1.3 MDT Initiation
+
+There are two cases that RAN should initiate a MDT measurements collection task. One is that the MDT task is initiated without targeting a specific UE by the cell traffic trace, i.e. management based trace function from OAM. The other is that the MDT task is initiated towards a specific UE by the signalling trace activation messages from CN nodes, i.e. the Initial Context Setup message, the Trace Start message or the Handover request message in E-UTRAN or NR, the CN Invoke Trace message in UTRAN. The detailed procedures to transfer the MDT configurations to RAN are specified in TS 32.422 [6].
+
+For signalling based MDT, the CN shall not initiate MDT towards a particular user unless it is allowed.
+
+For management based MDT, the CN indicates to the RAN whether MDT is allowed to be configured by the RAN for this user considering e.g. user consent and roaming status (see TS 32.422 [6]), by providing management based MDT allowed information. For E-UTRAN/UTRAN, the MDT allowed information consists of the Management Based MDT Allowed indication and optionally the Management Based MDT PLMN List. For NR, the MDT allowed information
+
+only consists of the Management Based MDT PLMN List. The management based MDT allowed information propagates during inter-PLMN handover if the Management Based MDT PLMN List is available and includes the target PLMN.
+
+A UE is configured with an MDT PLMN List only if user consent is valid for the RPLMN.
+
+### 5.1.4 UE capabilities
+
+MDT relevant UE capabilities are component of radio access UE capabilities. Thus, the procedures used for handling UE radio capabilities over (E-)UTRAN and NR apply.
+
+For (E-)UTRAN:
+
+- The UE indicates one capability bit for support for Logged MDT, which indicates that the UE supports logging of downlink pilot strength measurements. The UE may also indicate capability for stand-alone GNSS positioning.
+- The E-UTRA UE may indicate a capability for RX-TX time difference measurement for E-CID positioning for MDT.
+- The E-UTRA UE may indicate a capability for support of logging of MBMSFN measurements.
+- The E-UTRA UE may indicate a capability for support of UL PDCP delay measurement when the UE is not configured with MR-DC.
+- The E-UTRA UE may indicate a capability for support of UL PDCP Packet Average Delay measurement when the UE is configured with EN-DC.
+- The E-UTRA UE may indicate a capability for support of Bluetooth measurements in RRC idle mode.
+- The E-UTRA UE may indicate a capability for support of WLAN measurements in RRC idle mode.
+- The E-UTRA UE may indicate a capability for support of Bluetooth measurements in RRC connected mode.
+- The E-UTRA UE may indicate a capability for support of WLAN measurements in RRC connected mode.
+- For UMTS support of the Accessibility measurements is an optional UE feature.
+
+For NR:
+
+- The UE indicates one capability bit for support for Logged MDT in RRC idle and inactive mode, to indicate that the UE supports logging of downlink pilot strength measurements, periodical logging and event-triggered logging.
+- The UE may indicate capability for stand-alone GNSS positioning.
+- The NR UE may indicate a capability for support of UL PDCP packet average delay measurement.
+- The NR UE may indicate a capability for support of Bluetooth measurements in RRC idle and inactive mode.
+- The NR UE may indicate a capability for support of WLAN measurements in RRC idle and inactive mode.
+- The NR UE may indicate a capability for support of Bluetooth measurements in RRC connected state.
+- The NR UE may indicate a capability for support of WLAN measurements in RRC connected state.
+- The NR UE may indicate a capability for support of barometer measurements.
+- The NR UE may indicate a capability for support of orientation measurements.
+- The NR UE may indicate a capability for support of speed measurements.
+
+### 5.1.5 Void
+
+### 5.1.6 Accessibility measurements
+
+The UE logs failed RRC connection establishments for LTE, UMTS and NR, i.e. a log is created when the RRC connection establishment procedure fails. For NR, UE logs any failed connection establishment attempt, i.e. a log is created when the RRC setup or resume procedure fails. The UE logs failed RRC connection establishments without the need for prior configuration by the network.
+
+The UE stores the Selected PLMN on the RRC connection establishment failure or RRC resume procedure failure. Only if that PLMN is the same as the RPLMN, the UE may report the log.
+
+NOTE: There is no expected performance degradation for networks using EPLMNs.
+
+The trigger for creating a log related to a failed RRC connection establishment is for NR when timer T300 expires, for LTE when timer T300 expires and for UMTS when V300 is greater than N300. The trigger for creating log related to a failed RRC resume procedure is for NR when timer T319 expires.
+
+The UE can store the following information related to the failed RRC connection establishment or failed RRC resume procedure:
+
+- Time stamp, which is the elapsed time between logging and reporting the log.
+- The global cell identity of the serving cell when the RRC connection establishment or resume fails, i.e. the cell which the UE attempted to access.
+- The latest available radio measurements for any frequency or RAT
+- The latest detailed location information, if available.
+- For LTE:
+  - Number of Random Access Preambles transmitted;
+  - Indication whether the maximum transmission power was used;
+  - Contention detected;
+  - The latest WLAN measurement results, if available;
+  - The latest Bluetooth measurement results, if available.
+- For UMTS FDD:
+  - Number of RRC Connection Request attempts (e.g. T300 expiry after receiving ACK and AICH)
+- For UMTS 1.28 Mcps TDD:
+  - Number of RRC Connection Request attempts.
+  - Whether the FPACH is received or whether the maximum number Mmax of synchronisation attempts is reached.
+  - Failure indication of the E-RUCCH transmission. It is only applied when common E-DCH is supported by UE and network.
+- For NR:
+  - SSB index of the downlink beams of serving cell;
+  - The latest number of consecutive connection failures in the last failed cell the UE has experienced independent of RRC state transitions;
+  - RACH failure report:
+
+- Tried SSB index and number of Random Access Preambles transmitted for each tried SSB in chronological order of attempts;
+- Contention detected as per RACH attempt;
+- Indication whether the selected SSB is above or below the rsrp-ThresholdSSB threshold, as per RACH attempt;
+- TAC of the cell in which the UE performs the RA procedure;
+- The latest WLAN measurement results, if available;
+- The latest Bluetooth measurement results, if available;
+- The latest sensor information, if available.
+
+In addition, the CEF report may include additional information required for RACH Optimization solutions, as specified in TS 38.300 [22].
+
+## 5.2 E-UTRAN solutions
+
+### 5.2.1 RRC\_CONNECTED
+
+UE in RRC Connected does not support Logged MDT in this release of the specification, except for the case of logged MDT for MBSFN measurements as described in clause 5.1.1. In order to support Immediate MDT where MDT measurements are executed in the UE, the existing RRC measurement configuration and reporting procedures apply. Some extensions are used to carry location information.
+
+#### 5.2.1.1 Measurements and reporting triggers for Immediate MDT
+
+Measurements to be performed for Immediate MDT purposes involve reporting triggers and criteria utilized for RRM. An MDT specific UE-based measurement for UL PDCP delay is applied for QoS verification purpose. In addition, there are measurements performed in eNB.
+
+In particular, the following measurements shall be supported for Immediate MDT performance:
+
+Measurements:
+
+- M1: RSRP, RSRQ and SINR measurement by UE, see TS 36.214 [9].
+- M2: Power Headroom measurement by UE, see TS 36.213 [11].
+- M3: Received Interference Power measurement by eNB, see TS 36.214 [9]. This is a cell measurement. One sample is logged each measurement collection period, where one sample corresponds to a measurement period as specified in TS 36.133 [3].
+- M4: Data Volume measurement separately for DL and UL, per QCI per UE, by eNB, see TS 36.314 [13].
+- M5: Scheduled IP Throughput for MDT measurement separately for DL and UL, per RAB per UE and per UE for the DL, per UE for the UL, by eNB, see TS 36.314 [13]. QCI values of the RABs that have contributed to a measurement value are logged with the measurement values.
+- M6: Packet Delay measurement, separately for DL and UL, per QCI per UE, see UL PDCP Delay, by the UE, and Packet Delay in the DL per QCI, by the eNB, TS 36.314 [13].
+
+NOTE 1: If the UE does not detect any UL PDCP delay based on the delay threshold and delay report interval configured by the network, the UE does not report any UL PDCP delay measurement within that period.
+
+NOTE 2: A UE in EN-DC mode of operation can be configured with UL PDCP Packet Average Delay (*ul-DelayValueConfig*), if UE is capable of performing the UL average PDCP queueing delay.
+
+- M7: Packet Loss rate measurement, separately for DL and UL per QCI per UE, by the eNB, see Packet Loss rate in the UL and Packet Uu Loss rate in the DL TS 36.314 [13].
+
+- M8: RSSI measurement by UE, see TS 36.331 [5].
+- M9: RTT measurement by UE, see TS 36.331 [5].
+
+Measurement collection triggers:
+
+- For M1:
+  - Event-triggered measurement reports according to existing RRM configuration for events A1, A2, A3, A4, A5 A6, B1 or B2
+  - Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration.
+- For M2:
+  - Reception of Power Headroom Report (PHR) according to existing RRM configuration.
+
+NOTE 3: PHR is carried by MAC signalling. Thus, the existing mechanism of PHR transmission applies, see TS 36.321 [10].
+
+- For M3:
+  - End of measurement collection period
+- For M4:
+  - End of measurement collection period.
+- For M5:
+  - End of measurement collection period.
+- For M6:
+  - End of measurement collection period.
+- For M7:
+  - End of measurement collection period.
+- For M8:
+  - Associated to M1 and/or M6 related measurement reporting triggers.
+- For M9:
+  - Associated to M1 and/or M6 related measurement reporting triggers.
+
+#### 5.2.1.2 Enhancement to Radio Link Failure report
+
+The Radio Link Failure report contains information related to the latest connection failure experienced by the UE. The connection failure can be Radio Link Failure (RLF) or Handover Failure (HOF). The contents of the RLF report and the procedure for retrieving it by an eNB are described in TS 36.300 [12].
+
+RLF reports can be collected by OAM. Upon RLF/HOF detection in the UE, *RLFReport* defined in TS 36.331 [5] also includes available location information on where RLF occurred, i.e. if detailed location information (e.g. GNSS location information) is available the reported location information in *RLFReport* consists of:
+
+- Latitude, longitude (mandatory)
+- Altitude (conditional on availability)
+- Velocity (conditional on availability)
+- Uncertainty (conditional on availability)
+
+- Confidence (conditional on availability)
+- Direction (conditional on availability).
+
+As an indication of impact to MMTEL calls the UE indicates in the radio link failure report whether a radio bearer with QCI 1 was established when radio link failure was detected.
+
+RLF reports may also include available WLAN measurement results and/or Bluetooth measurement results for calculating UE location.
+
+If available, the UE can indicate NR neighbor cell measurements in measurements results.
+
+#### 5.2.1.3 Detailed Location Information
+
+The M1 measurements are tagged by the UE with location data in the following manner:
+
+- Detailed location information (e.g. GNSS location information) is included if available in the UE when the measurement was taken. If detailed location information is available, the reporting shall consist of latitude and longitude. Depending on availability, altitude, uncertainty and confidence may be also additionally included. The UE should include the available detailed location information only once. If the detailed location information is obtained by GNSS positioning method, GNSS time information shall be included. For both event based and periodic reporting (see 5.2.1.1), the detailed location information is included if the report is transmitted within the validity time after the detailed location information was obtained. The validity evaluation of detailed location information is left to UE implementation.
+- To support UE location information in SCG failure, the location information (i.e. commonLocationInfo, see TS 38.331 [15] and WLAN and BT information, if available) is included in *SCGFailureInformation* message, see TS 36.331 [5].
+
+For immediate MDT, the eNB can request the UE to attempt to make GNSS location information available. Standalone GNSS is used as the default baseline. It is desired that the UE provides fresh location information with each immediate MDT measurement report. The details how this is achieved is up to UE implementation.
+
+The eNB may use an Enhanced Cell ID mechanism for location. The eNB forwards the raw E-CID specific measurements to the TCE. When E-CID positioning is requested, the eNB may choose to not use E-CID positioning for collected measurement for which the UE provides detailed location information.
+
+### 5.2.2 RRC\_IDLE
+
+For UE in RRC\_IDLE state Logged MDT procedures as described in 5.1.1 apply.
+
+Logged MDT measurements are sent on Signalling Radio Bearer SRB2 in RRC\_CONNECTED state.
+
+## 5.3 UTRAN solutions
+
+### 5.3.1 UTRA RRC Connected
+
+In CELL\_PCH, URA\_PCH states and CELL\_FACH state when second DRX cycle is used, UE supports Logged MDT as described in 5.1.1. In CELL\_DCH state UE supports Immediate MDT as described in 5.1.2. In CELL\_FACH state when second DRX cycle is not used, MDT is not supported in the current release.
+
+#### 5.3.1.1 Measurements and reporting events for Immediate MDT
+
+The solutions for Immediate MDT in UTRAN are only applicable for UEs in CELL\_DCH state. Measurements to be performed for Immediate MDT purposes involve normal UTRAN reporting triggers and criteria utilized for controlling the RRC connection. In addition, there are measurements defined that are performed in UTRAN. In particular, the following measurements shall be supported for Immediate MDT:
+
+Measurements:
+
+- M1: CPICH RSCP and CPICH Ec/No measurement (FDD) by UE, see TS 25.215 [7].
+
+- M2: P-CCPCH RSCP and Timeslot ISCP for UTRA 1.28 Mcps TDD by UE, see TS 25.225 [8].
+- M3: SIR and SIR error (FDD) by NodeB, see TS 25.215 [7] and TS 25.225 [8].
+- M4: UE power headroom (UPH) by the UE, applicable for E-DCH transport channels, see TS 25.215 [7] and TS 25.225 [8].
+- M5: Received total wideband power (RTWP) by Node B, see TS 25.215 [7] TS 25.225 [8], and TS 25.133 [2]. This is a cell measurement.
+- M6: Data Volume measurement, separately for DL and UL, per QoS class per UE, by RNC.
+- M7: Throughput measurement, separately for DL and UL, per RAB per UE and per UE, by RNC. Traffic class and Traffic Handling Priority for interactive RABs for the RABs that have contributed to a measurement value are logged with the measurement values.
+
+##### Measurement collection triggers:
+
+- For M1:
+  - Event triggered measurement reports according to existing RRM configuration, for measurement types intra-frequency measurement, inter-frequency measurement and inter-RAT measurement.
+  - Periodic, or 1F event-triggered measurement report, primary CPICH becomes worse than an absolute threshold, according to MDT specific measurement configuration.
+- For M2:
+  - Event triggered measurement reports according to existing RRM configuration, for measurement types intra-frequency measurement, inter-frequency measurement and inter-RAT measurement.
+  - Periodic, or 1I event-triggered measurement report, timeslot ISCP above a certain threshold (TDD), according to MDT specific measurement configuration.
+- For M3:
+  - When available
+- For M4:
+  - Reception of UPH according to existing RRM configuration
+  - Provided by the UE according to RRM configuration.
+  - UPH samples may be collected and logged:
+    - always
+    - periodic, one sample per period.
+    - periodic, one sample per period, when measurement value < threshold.
+- For M5:
+  - When available.
+  - End of measurement collection period.
+- For M6:
+  - End of measurement collection period.
+- For M7:
+  - End of measurement collection period.
+
+#### 5.3.1.2 Detailed Location Information
+
+For Immediate MDT, existing procedures for UE Location information are used to obtain detailed location information.
+
+### 5.3.2 UTRA Idle
+
+For UEs in UTRA Idle mode Logged MDT procedures as described in 5.1.1 apply.
+
+Logged MDT measurements are sent on Signalling Radio Bearer SRB4 in RRC Connected mode.
+
+## 5.4 NR solutions
+
+### 5.4.0 General
+
+The management-based MDT configuration should not overwrite signalling based MDT configuration in all the single connection scenarios and EN-DC scenario.
+
+### 5.4.1 RRC\_CONNECTED
+
+In RRC\_CONNECTED state UE supports Immediate MDT as described in 5.1.2. In order to support Immediate MDT, the existing RRC measurement configuration and reporting procedures apply. Some extensions are used to carry location information.
+
+#### 5.4.1.1 Measurements and reporting triggers for Immediate MDT
+
+Measurements to be performed for Immediate MDT purposes involve reporting triggers and criteria utilized for RRM. In addition, there are associated network performance measurements performed in the gNB.
+
+In particular, the following measurements shall be supported for Immediate MDT performance:
+
+Measurements:
+
+- M1: DL signal quantities measurement results for the serving cell and for intra-frequency/Inter-frequency/inter-RAT neighbour cells, including cell/beam level measurement for NR cells only, TS 38.215 [19].
+- M2: Power Headroom measurement by UE, TS 38.213 [20].
+- M3: Void.
+- M4: PDCP SDU Data Volume measurement separately for DL and UL, per DRB per UE, see TS 28.552 [17].
+- M5: Average UE throughput measurement separately for DL and UL, per DRB per UE and per UE for the DL, per DRB per UE and per UE for the UL, by gNB, see TS 28.552 [17].
+- M6: Packet Delay measurement separately for DL and UL, per DRB per UE, TS 28.552 [17] and TS 38.314 [18].
+- M7: Packet loss rate measurement separately for DL and UL, per DRB per UE, TS 28.552 [17] and TS 38.314 [18].
+- M8: RSSI measurement by UE (for WLAN/Bluetooth measurement) see TS 38.331 [15].
+- M9: RTT Measurement by UE (for WLAN measurement) see TS 38.331 [15].
+
+NOTE 1: M5 ~ M7 do not apply to EN-DC SN terminated MCG/split bearers and MN terminated SCG/split bearers in Rel-16.
+
+Measurement collection triggers:
+
+- For M1:
+
+- Event-triggered measurement reports according to existing RRM configuration for events A1, A2, A3, A4, A5, A6, B1 or B2.
+- Periodic, A2 event-triggered, or A2 event triggered periodic measurement report according to MDT specific measurement configuration.
+- For M2:
+  - Reception of Power Headroom Report (PHR) according to existing RRM configuration.
+
+NOTE 2: PHR is carried by MAC signalling. Thus, the existing mechanism of PHR transmission applies, see TS 38.321 [21].
+
+- For M3:
+  - End of measurement collection period.
+- For M4:
+  - End of measurement collection period.
+- For M5:
+  - End of measurement collection period.
+
+NOTE 3: If transmission of a data burst is ongoing at the boundary of the measurement collection period, T1 and T2 in throughput evaluations are set to the end and the start of the measurement period, respectively.
+
+- For M6:
+  - End of measurement collection period.
+- For M7:
+  - End of measurement collection period.
+- For M8:
+  - Associated to M1 and/or M6 related measurement reporting triggers.
+- For M9:
+  - Associated to M1 and/or M6 related UE measurement reporting triggers.
+
+#### 5.4.1.2 Radio Link Failure report
+
+The Radio Link Failure report contains information related to the latest connection failure experienced by the UE. The connection failure can be Radio Link Failure (RLF) or Handover Failure (HOF). The contents of the RLF report and the procedure for retrieving it by a gNB are specified in TS 38.331 [15].
+
+NR RLF report content required for MDT includes:
+
+- Latest radio measurement results of the serving and neighbouring cells, including SSB/CSI-RS index and associated measurements in the serving and neighbouring cells;
+
+NOTE: The measure quantities are sorted through the same RS type depending on the availability, according to the following priority: RSRP, RSRQ, SINR.
+
+- WLAN and Bluetooth measurement results, if were configured prior RLF and are available for reporting;
+- "No suitable cell is found" flag when T311 expires;
+- Indication per SSB/CSI-RS beams reporting whether it is configured to RLM purpose;
+- Available sensor information;
+- Available detailed location information;
+
+- RACH failure report (in case, the cause for RLF is random access problem or Beam Failure Recovery failure):
+  - Tried SSB/CSI-RS index and number of Random Access Preambles transmitted for each tried SSB/CSI-RS in chronological order of attempts;
+  - Contention detected as per RACH attempt;
+  - Indication whether the selected SSB is above or below the rsrp-ThresholdSSB threshold, as per RACH attempt;
+  - TAC of the cell in which the UE performs the RA procedure;
+  - Frequency location related information of the RA resources used by the UE as specified in TS 38.331 [15].
+
+If detailed location information (e.g. GNSS location information) is available the reported location information in *rlf-Report* consists of:
+
+- Latitude, longitude (mandatory);
+- Altitude (conditional on availability);
+- Velocity (conditional on availability);
+- Uncertainty (conditional on availability);
+- Confidence (conditional on availability);
+- Direction (conditional on availability).
+
+If sensor information is available, the sensor information may convey uncompensated barometric pressure, UE speed, and UE orientation.
+
+In addition, the RLF report may include additional information required for MRO solutions, as specified in TS 38.300 [22].
+
+#### 5.4.1.3 Immediate MDT for MR-DC
+
+Immediate MDT is supported for EN-DC scenario.
+
+In signalling based immediate MDT, MME provides MDT configuration for both MN and SN towards MN including multi RAT SN configuration, specifically E-UTRA and NR MDT configuration. MN then forwards the NR MDT configuration towards SN (EN-DC scenario, SN is always NR).
+
+In management-based immediate MDT, OAM provides the MDT configuration to both MN and SN independently. For both MN and SN, Management based MDT should not overwrite signalling based MDT.
+
+For immediate MDT configuration, MN and SN can independently configure and receive measurement from the UE.
+
+### 5.4.2 RRC\_IDLE & RRC\_INACTIVE
+
+For UE in RRC\_IDLE and RRC\_INACTIVE states Logged MDT procedures as described in 5.1.1 apply.
+
+For Logged MDT measurement collection for RRC\_INACTIVE UEs, the actual process of logging within the UE, takes place in RRC\_INACTIVE state and may be continued in RRC\_IDLE state; or vice versa.
+
+The logged measurement stored in UE during RRC\_INACTIVE and RRC\_IDLE state are kept for a given common period before they are deleted as in LTE MDT.
+
+If the signalling based logged or immediate MDT configuration received by the NG-RAN when UE is in RRC\_INACTIVE:
+
+- The NG-RAN stores the MDT configuration in the UE context;
+- When the UE resumes the RRC connection in the last serving NG-RAN, the NG-RAN can configure the MDT configuration for the UE;
+
+- When the UE resumes the RRC connection in one new NG-RAN, the new NG-RAN can configure the MDT configuration for the UE, only if the signalling based logged MDT was received by the new NG-RAN from the previous NG-RAN or AMF.
+
+If the management based MDT configuration is received by the NG-RAN when UE is in RRC\_INACTIVE,
+
+- No requirement for the NG-RAN to store the MDT configuration in the UE context;
+- When the UE resumes the RRC connection in the last serving NG-RAN, the NG-RAN can configure the MDT configuration for the UE;
+- When the UE resumes the RRC connection in another NG-RAN, the source NG-RAN will not propagate the management based MDT configuration. The source NG-RAN should inform the target NG-RAN of UE consents.
+
+Logged MDT measurements are sent on Signalling Radio Bearer SRB2 in RRC\_CONNECTED state.
+
+# Annex A (informative): Coverage use cases
+
+The MDT data reported from UEs and the RAN may be used to monitor and detect coverage problems in the network. Some examples of use cases of coverage problem monitoring and detection are described in the following:
+
+- **Coverage hole:** A coverage hole is an area where the signal level SNR (or SINR) of both serving and allowed neighbor cells is below the level needed to maintain basic service (SRB & DL common channels), i.e. coverage of PDCCH. Coverage holes are usually caused by physical obstructions such as new buildings, hills, or by unsuitable antenna parameters, or just inadequate RF planning. UE in coverage hole will suffer from call drop and radio link failure. Multi-band and/or Multi-RAT UEs may go to other network layer instead.
+- **Weak coverage:** Weak coverage occurs when the signal level SNR (or SINR) of serving cell is below the level needed to maintain a planned performance requirement (e.g. cell edge bit-rate).
+- **Pilot Pollution:** In areas where coverage of different cells overlap a lot, interference levels are high, power levels are high, energy consumption is high and cell performance may be low. This problem phenomenon has been called "pilot pollution", and the problem can be addressed by reducing coverage of cells. Typically in this situation UEs may experience high SNR to more than one cell and high interference levels.
+- **Overshoot coverage:** Overshoot occurs when coverage of a cell reaches far beyond what is planned. It can occur as an "island" of coverage in the interior of another cell, which may not be a direct neighbor. Reasons for overshoot may be reflections in buildings or across open water, lakes etc. UEs in this area may suffer call drops or high interference. Possible actions to improve the situation include changing the coverage of certain cells and mobility blacklisting of certain cells.
+- **Coverage mapping:** There should be knowledge about the signal levels in the cell areas in order to get a complete view for the coverage and be able to assess the signal levels that can be provided in the network. This means that there should be measurements collected in all parts of the network, and not just in the areas where there are potential coverage issues.
+- **UL coverage:** Poor UL coverage might impact user experience in terms of call setup failure / call drop / poor UL voice quality. Therefore, coverage should be balanced between uplink and downlink connections. Possible UL coverage optimization comprises adapting the cellular coverage by changing the site configuration (antennas) but also about adjusting the UL related parameters in the way that they allow optimized usage of UL powers in different environments.
+- **Cell boundary mapping:** There should be knowledge about the location of (intra/inter RAT) cell boundaries in order to compare to the expected/planned network setting. Poor handover performance may be caused by changed cell boundaries due to changes in the physical condition of the surrounding area, e.g., construction of new buildings, bridge or tunnel near the handover area.
+- **Coverage mapping for pico cell in CA scenario:** As a realization of CA scenario 4 in TS 36.300 [12], pico cell may be deployed in area where high traffic occurs. The location where a pico cell is available to be added as an SCell may show whether the deployment of pico cell is according to the needs of capacity increase.
+
+# --- Annex B (informative): QoS verification use cases
+
+The MDT data reported from UEs and the RAN may be used to verify Quality of Service, assess user experience from RAN perspective, and to assist network capacity extension. Use cases are described in the following:
+
+- **Traffic Location:** MDT functionality to obtain information of where data traffic is transferred within a cell.
+- **User QoS Experience:** MDT functionality to assess the QoS experience for a specific UE together with location information.
+  - Data Throughput measurements can be collected, aiming to reflect QoS for bandwidth limited traffic.
+  - For E-UTRA, Data Loss and Latency measurements can be collected, aiming to reflect QoS for conversational traffic.
+
+# --- Annex C (informative): Measurements
+
+This annex provides information on measurements that are used for MDT and are not specified elsewhere.
+
+**Throughput measurement for UMTS.** The throughput is measured on PDCP or RLC level. A measurement value for a UE and each RAB of the UE is provided each measurement period, except if the value is zero. The measurement is performed separately for UL and DL, and is performed for PS RABs. Idle periods shall not be taken into account, when there is no data buffered or no data being transmitted.
+
+**Data Volume measurement for UMTS.** Data Volume is measured on PDCP or RLC (without Layer 2 overhead). A measurement value for a QoS class for a UE is provided each measurement period, except if the value is zero, where the QoS class is one of conversational, interactive, streaming or background. The measurement is performed separately for UL and DL, and is performed for PS RABs.
+
+# --- Annex D (informative): MBSFN use cases
+
+The MDT data reported from UEs may be used to verify signal strength, signal quality and block error rates for MBSFN reception, to support network verification, re-planning of MBSFN areas, and optimization of MBSFN operation parameters.
+
+# --- Annex E (informative): Change history
+
+| Change history |          |           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |       |       |
+|----------------|----------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date           | WG #     | WG Doc.   | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Old   | New   |
+| 2010/01        | R2#68bis | R2-100845 | Skeleton TS endorsed                                                                                                                                                                                                                                                                                                                                                                                                                                               | 0.0.0 | 0.1.0 |
+| 2010/01        | R2#68bis | R2-100846 | Initial content provided                                                                                                                                                                                                                                                                                                                                                                                                                                           | 0.1.0 | 0.2.0 |
+| 2010/02        | R2#69    | R2-101800 | Logged and Immediate MDT definitions added<br>Requirements introduced<br>Measurement Configuration/Reporting principles clarified                                                                                                                                                                                                                                                                                                                                  | 0.2.0 | 0.2.1 |
+| 2010/02        | R2#69    | R2-101891 | RAN2 approved TS v0.3.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0.2.1 | 0.3.0 |
+| 2010/04        | R2#69bis | R2-102623 | - General principles for support of Logged MDT included<br>- Location Information principles for Logged MDT introduced<br>- MDT Context handling for Logged MDT introduced<br>- Report availability indicator added to 5.1.3<br>- Annex A                                                                                                                                                                                                                          | 0.3.0 | 0.3.1 |
+| 2010/04        | R2#69bis | R2-102656 | - Editorial changes                                                                                                                                                                                                                                                                                                                                                                                                                                                | 0.3.1 | 0.3.2 |
+| 2010/04        | R2#69bis | R2-102667 | RAN2 approved TS v0.4.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0.3.2 | 0.4.0 |
+| 2010/05        | R2#70    | R2-103400 | Logged MDT configuration and reporting principles added<br>Periodical measurement configuration rules for Logged MDT added<br>SRB for Logged MDT identified<br>Measurements and triggers for Immediate MDT identified                                                                                                                                                                                                                                              | 0.4.0 | 0.4.1 |
+| 2010/05        | R2#70    | R2-103456 | RAN2 approved TS v0.5.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0.4.1 | 0.5.0 |
+| 2010/06        | R2#70bis | R2-103991 | Editorial changes:<br>- New text organization in 5.1: split in two clauses for Logged MDT and Immediate MDT<br>- MDT Reporting mode in 4.1 update to clarify the requirement on feature support<br>- FFS on extension across RAT aligned to RAN#69 agreement<br>- Retrieved data removal requirement aligned to RAN2#70 agreement                                                                                                                                  | 0.5.0 | 0.5.1 |
+| 2010/06        | R2#70bis | R2-104073 | RAN2 approved TS v0.6.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0.5.1 | 0.6.0 |
+| 2010/06        | R2#70bis | R2-104074 | - Logged MDT configuration message sequence added in 5.1.1.1<br>- Measurement area scope identified<br>- Time stamping principles added<br>- MDT configuration/log handling at PLMN change introduced<br>- Validity timer for non-retrieved data defined<br>- GNSS location information details defined<br>- RLF enhancements on location information defined<br>- MDT applicability for UTRA states added                                                         | 0.6.0 | 0.6.1 |
+| 2010/06        | R2#70bis | R2-104206 | Clarification on sending availability indicator in another RAT added                                                                                                                                                                                                                                                                                                                                                                                               | 0.6.1 | 0.6.2 |
+| 2010/06        | R2#70bis | R2-104212 | RAN2 approved TS v0.7.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 0.6.2 | 0.7.0 |
+| 2010/08        | R2#71    | R2-104950 | Agreed text proposal in R2-104303 on clarification on logged MDT data retrieval added<br>MDT applicability for particular UE states clarified in corresponding clauses<br>Time stamp details included in 5.1.1.3.3<br>MDT handling during handover added in 5.1.2.3<br>Agreed text proposal in R2-104678 to address SA5 progress added in 5.1.3<br>Assumptions on memory size limit capability added in 5.1.4<br>Further RLF enhancements listed as FFS in 5.2.1.2 | 0.7.0 | 0.7.1 |
+| 2010/08        | R2#71    | R2-105238 | Clarification on idle logging applicability to "camped normally" state in 5.1.1.2. added<br>FFS on logged data clearance in shared network scenarios added<br>Submitted to TSG RAN for information                                                                                                                                                                                                                                                                 | 0.7.1 | 1.0.0 |
+| 2010/10        | R2#71b   | R2-105787 | Editorial and formatting changes                                                                                                                                                                                                                                                                                                                                                                                                                                   | 1.0.0 | 1.0.1 |
+| 2010/10        | R2#71b   | R2-105877 | Logged MDT reports details on neighbours details added<br>Accurate location information validity clarified<br>UE memory size reserved for Logged MDT added<br>Transport of MDT logs using multiple RRC messages defined<br>Logging handling at PLMN change clarified                                                                                                                                                                                               | 1.0.1 | 1.0.2 |
+| 2010/10        | R2#71b   | R2-106018 | RAN2 approved TS v1.1.0                                                                                                                                                                                                                                                                                                                                                                                                                                            | 1.0.2 | 1.1.0 |
+
+|         |       |           |                                                                                                                                                             |       |       |
+|---------|-------|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| 2010/11 | R2#72 | R2-106682 | Requirement on Dependency on Trace added<br>Validity time for accurate location information in Immediate MDT added<br>Introduction of UTRA 1.28 TDD metrics | 1.1.0 | 1.1.1 |
+| 2010/11 | R2#72 | R2-106936 | RAN2 approved TS v2.0.0                                                                                                                                     | 1.1.1 | 2.0.0 |
+
+| Change history |       |           |      |     |     |                                                                            |             |
+|----------------|-------|-----------|------|-----|-----|----------------------------------------------------------------------------|-------------|
+| Date           | TSG # | TSG Doc.  | CR   | Rev | Cat | Subject/Comment                                                            | New version |
+| 2010-12        | RP-50 | RP-101162 | -    | -   |     | TS 37.320 approved b RAN #50                                               | 10.0.0      |
+| 2011-03        | RP-51 | RP-110282 | 0001 | -   |     | Clarifications on MDT initiation                                           | 10.1.0      |
+|                | RP-51 | RP-110282 | 0002 | -   |     | Clear MDT configuration and logs when the UE is not registered             | 10.1.0      |
+|                | RP-51 | RP-110282 | 0003 | 1   |     | MDT stage 2 clarifications                                                 | 10.1.0      |
+|                | RP-51 | RP-110282 | 0004 | -   |     | On memory size limitation for Logged MDT                                   | 10.1.0      |
+|                | RP-51 | RP-110282 | 0005 | -   |     | UE Capabilities for MDT                                                    | 10.1.0      |
+|                | RP-51 | RP-110282 | 0006 | -   |     | Validity time for location information in Immediate MDT                    | 10.1.0      |
+|                | RP-51 | RP-110282 | 0008 | -   |     | Correction to include CDMA2000 reporting for neighbouring cells            | 10.1.0      |
+|                | RP-51 | RP-110282 | 0012 | -   |     | Small Clarifications and Corrections to 37.320                             | 10.1.0      |
+|                | RP-51 | RP-110282 | 0013 | -   |     | Trace parameters for MDT configuration                                     | 10.1.0      |
+| 2011-06        | RP-52 | RP-110843 | 0014 | -   |     | Clarification for logged MDT measurement configuration effectiveness       | 10.2.0      |
+|                | RP-52 | RP-110843 | 0015 | -   |     | Correction of log availability reporting                                   | 10.2.0      |
+|                | RP-52 | RP-110843 | 0016 | -   |     | Immediate MDT context handling during inter-PLMN handover                  | 10.2.0      |
+|                | RP-52 | RP-110843 | 0017 | 1   |     | MDT UL network measurements                                                | 10.2.0      |
+|                | RP-52 | RP-110843 | 0018 | -   |     | Signalling based Immediate MDT initiation with area scope configuration    | 10.2.0      |
+|                | RP-52 | RP-110843 | 0019 | -   |     | TCE ID parameter for logged MDT                                            | 10.2.0      |
+|                | RP-52 | RP-110843 | 0020 | -   |     | Miscellaneous corrections to 37.320                                        | 10.2.0      |
+|                | RP-52 | RP-110843 | 0025 | 1   |     | MDT Stage-2 Cleanup                                                        | 10.2.0      |
+|                | RP-52 | RP-110843 | 0026 | 1   |     | Introduction of the User consent                                           | 10.2.0      |
+|                | RP-52 | RP-110843 | 0027 | -   |     | CR to 37.320 to clean up description of RLF Reporting                      | 10.2.0      |
+| 2011-09        | RP-53 | RP-111285 | 0033 | -   |     | Immediate MDT context handling during inter-PLMN handover                  | 10.3.0      |
+|                | RP-53 | RP-111285 | 0034 | -   |     | Miscellaneous corrections to 37.320                                        | 10.3.0      |
+|                | RP-53 | RP-111285 | 0037 | -   |     | Editorial corrections                                                      | 10.3.0      |
+| 2011-12        | RP-54 | RP-111714 | 0038 | -   |     | CR to 37.320 on Immediate MDT handling at handover                         | 10.4.0      |
+|                | RP-54 | RP-111714 | 0039 | -   |     | Small Corrections to 37.320                                                | 10.4.0      |
+| 2012-06        | RP-56 | RP-120819 | 0045 | 1   |     | Introduction of MDT enhancements                                           | 11.0.0      |
+| 2012-09        | RP-57 | RP-121370 | 0046 | 1   |     | Updates for MDT enhancements                                               | 11.1.0      |
+| 2012-12        | RP-58 | RP-121946 | 0051 | -   |     | MDT Open Issues Resolutions                                                | 11.2.0      |
+|                | RP-58 | RP-121946 | 0052 | -   |     | Removing the IE Contention Detected in Accessibility Measurement(option 3) | 11.2.0      |
+|                | RP-58 | RP-121946 | 0054 | -   |     | Stage-2 update for MDT enhancements                                        | 11.2.0      |
+|                | RP-58 | RP-121730 | 0055 | -   |     | Multi-PLMN MDT                                                             | 11.2.0      |
+| 2013-03        | RP-59 | RP-130240 | 0056 | -   |     | Miscellaneous MDT corrections                                              | 11.3.0      |
+|                | RP-59 | RP-130240 | 0057 | -   |     | Correction to E-CID positioning for MDT                                    | 11.3.0      |
+|                | RP-59 | RP-130240 | 0058 | -   |     | Corrections for multi-PLMN MDT                                             | 11.3.0      |
+| 2014-03        | RP-63 | RP-140347 | 0061 | -   |     | Introduction of Cell FACH with Second DRX to 3G Logged MDT                 | 12.0.0      |
+| 2014-06        | RP-64 | RP-140889 | 0062 | 1   |     | Introduction of MBMS operations Support for E-UTRA                         | 12.1.0      |
+| 2014-09        | RP-65 | RP-141507 | 0066 | -   |     | Minor corrections to MDT Stage-2                                           | 12.2.0      |
+|                | RP-65 | RP-141496 | 0064 | 1   |     | Reporting and measurement collection triggers for immediate MDT            | 12.2.0      |
+| 2015-12        | RP-70 | RP-152082 | 0067 | 1   |     | Further Enhancements of MDT for E-UTRA                                     | 13.0.0      |
+| 2016-03        | RP-71 | RP-160470 | 0069 | -   |     | Reporting of UL PDCP delay measurements for FeMDT                          | 13.1.0      |
+| 2017-03        | RP-75 |           |      |     |     | Upgrade to Rel-14, no technical change                                     | 14.0.0      |
+| 2018-06        | RP-80 | RP-181227 | 0071 | 2   | B   | 37.320 CR to introduce BT and WLAN in MDT                                  | 15.0.0      |
+|                | RP-80 | RP-181228 | 0072 | -   | B   | Support for logging of 'Any cell selection' state                          | 15.0.0      |
+| 2020-03        | RP-87 | RP-200354 | 0077 | 2   | B   | CR to Introduce NR MDT                                                     | 16.0.0      |
+| 2020-07        | RP-88 | RP-201184 | 0085 | 2   | F   | CR to 37.320 to support NR MDT                                             | 16.1.0      |
+| 2020-09        | RP-89 | RP-201931 | 0090 | -   | F   | Corrections to TS37.320                                                    | 16.2.0      |
+| 2020-12        | RP-90 | RP-202776 | 0098 | 1   | F   | Merged Corrections for TS37.320                                            | 16.3.0      |
+| 2021-03        | RP-91 | RP-210693 | 0103 | -   | F   | Merged Corrections to TS 37.320                                            | 16.4.0      |
+| 2021-06        | RP-92 | RP-211471 | 0107 | 2   | F   | Merged Corrections to TS 37.320                                            | 16.5.0      |
+| 2021-09        | RP-93 | RP-212443 | 0110 | 1   | F   | On UL delay configuration in LTE                                           | 16.6.0      |
+| 2021-12        | RP-94 | RP-213344 | 0112 | -   | F   | TS37.320 title update                                                      | 16.7.0      |
+| 2022-03        | RP-95 | RP-220835 | 0116 | -   | F   | Immediate MDT configurations for UE in inactive                            | 16.8.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37324/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-16/37_series/37324/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af669883f783eda420a6e5fc4db7543fe4a26b71
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89ec67f7c43740a2bca69df9998111ca5ac789cb142943aecdaab841e092b2a8
+size 17802
diff --git a/marked/Rel-16/37_series/37324/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37324/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fdb50970ef05f8e852ef8a9c354119d771f2c8c5
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbf84264bf4aa599ee69407ee721bf1fd7aab4f4eebcad67ff730ea984576b35
+size 8142
diff --git a/marked/Rel-16/37_series/37324/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37324/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aea8038fb0a5fa7e9b6de984fde5fa4eb43912c0
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c71fc34b4a5ebd9a8c46f523fda07e039161470050077da9b1488ec516cf730a
+size 5440
diff --git a/marked/Rel-16/37_series/37324/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-16/37_series/37324/704082cc3e11776bda29595c76411362_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9951dcda87dc2e1ca43e5441ec5ec5e73e3fca1b
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/704082cc3e11776bda29595c76411362_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77ecf21f03bf1b7a633cdb0dd6606e469b5180d20445b9ef18ee79f0da5506b0
+size 17085
diff --git a/marked/Rel-16/37_series/37324/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/37_series/37324/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b080a9eb2569432d1ccebaceb6167d30deedb178
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ab61e07c6e2924bff79d958738739e40f60edb7e9cbe0c15301552b38cf1609
+size 18629
diff --git a/marked/Rel-16/37_series/37324/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/37_series/37324/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddc63963782124d317af64bb5ebf4457f1302875
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12c96a23b0e14579afedd9d9dcaece4d21b5bda5cd8e60e2cdb7ccd186151b96
+size 11484
diff --git a/marked/Rel-16/37_series/37324/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/37_series/37324/bffdddb47fced140f8d17fdc2a29f592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..82e3bb86c0816c0b8a49a04bed0f21e9bc8d01ce
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/bffdddb47fced140f8d17fdc2a29f592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0ab785d122928b85a22e5ec1da41394b5f10b1dd36711faccbaac47f64ff47f
+size 7746
diff --git a/marked/Rel-16/37_series/37324/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-16/37_series/37324/e1a0d046fbe7f28f5e93a47091851747_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7588d273017d4c0497a44b750463825e870b2905
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/e1a0d046fbe7f28f5e93a47091851747_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:083af864c303d3a96742b863f2972279f40a964f2671223115eba435bf96bacd
+size 98006
diff --git a/marked/Rel-16/37_series/37324/e2c1c672349c10dccb2563eff6d8260e_img.jpg b/marked/Rel-16/37_series/37324/e2c1c672349c10dccb2563eff6d8260e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19226049a10509ac18ece55aa2e93ac5e4dbe9a0
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/e2c1c672349c10dccb2563eff6d8260e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58d21b59c201cd4516b818b8b5495e14ae2632f274666e6d4839ff4afcc3af87
+size 73561
diff --git a/marked/Rel-16/37_series/37324/raw.md b/marked/Rel-16/37_series/37324/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc7ef4edb1b09b2b447b15ce830ff8e4edd7d380
--- /dev/null
+++ b/marked/Rel-16/37_series/37324/raw.md
@@ -0,0 +1,582 @@
+
+
+# 3GPP TS 37.324 V16.3.0 (2021-06) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 16)** ---
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                    |    |
+|------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                     | 5  |
+| 1 Scope.....                                                                       | 6  |
+| 2 References.....                                                                  | 6  |
+| 3 Definitions, symbols and abbreviations .....                                     | 6  |
+| 3.1 Definitions.....                                                               | 6  |
+| 3.2 Abbreviations .....                                                            | 6  |
+| 4 General.....                                                                     | 7  |
+| 4.1 Introduction .....                                                             | 7  |
+| 4.2 SDAP architecture.....                                                         | 7  |
+| 4.2.1 SDAP structure .....                                                         | 7  |
+| 4.2.2 SDAP entities .....                                                          | 8  |
+| 4.3 Services .....                                                                 | 9  |
+| 4.3.1 Services provided to upper layers.....                                       | 9  |
+| 4.3.2 Services expected from lower layers.....                                     | 9  |
+| 4.4 Functions .....                                                                | 9  |
+| 5 SDAP procedures.....                                                             | 9  |
+| 5.1 SDAP entity handling.....                                                      | 9  |
+| 5.1.1 SDAP entity establishment.....                                               | 9  |
+| 5.1.2 SDAP entity release.....                                                     | 9  |
+| 5.2 Data transfer .....                                                            | 10 |
+| 5.2.1 Uplink.....                                                                  | 10 |
+| 5.2.2 Downlink.....                                                                | 10 |
+| 5.2.3 SL transmission .....                                                        | 10 |
+| 5.2.4 SL reception.....                                                            | 11 |
+| 5.3 QoS flow to DRB mapping .....                                                  | 11 |
+| 5.3.1 Configuration.....                                                           | 11 |
+| 5.3.2 Reflective mapping.....                                                      | 11 |
+| 5.3.3 DRB release.....                                                             | 12 |
+| 5.4 RQI handling.....                                                              | 12 |
+| 5.5 PC5 QoS flow to SL-DRB mapping .....                                           | 12 |
+| 5.5.1 Configuration.....                                                           | 12 |
+| 5.5.2 SL-DRB release.....                                                          | 13 |
+| 6 Protocol data units, formats, and parameters .....                               | 13 |
+| 6.1 Protocol data units.....                                                       | 13 |
+| 6.1.1 Data PDU.....                                                                | 13 |
+| 6.1.2 Control PDU .....                                                            | 13 |
+| 6.2 Formats.....                                                                   | 13 |
+| 6.2.1 General .....                                                                | 13 |
+| 6.2.2 Data PDU.....                                                                | 13 |
+| 6.2.2.1 Data PDU without SDAP header.....                                          | 13 |
+| 6.2.2.2 DL Data PDU with SDAP header.....                                          | 14 |
+| 6.2.2.3 UL Data PDU with SDAP header.....                                          | 14 |
+| 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication..... | 14 |
+| 6.2.3 End-Marker Control PDU .....                                                 | 15 |
+| 6.3 Parameters .....                                                               | 15 |
+| 6.3.1 General .....                                                                | 15 |
+| 6.3.2 Data.....                                                                    | 15 |
+| 6.3.3 D/C .....                                                                    | 15 |
+| 6.3.4 QFI.....                                                                     | 15 |
+| 6.3.5 R .....                                                                      | 16 |
+| 6.3.6 RQI.....                                                                     | 16 |
+| 6.3.7 RDI.....                                                                     | 16 |
+| 6.3.8 PQFI .....                                                                   | 16 |
+
+**Annex A (informative): Change history................................................................................................................ 17**
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Service Data Adaptation Protocol (SDAP) for a UE with connection to the 5G-CN or for a UE in NR sidelink communication.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.300: "NG Radio Access Network; Overall description".
+- [3] 3GPP TS 38.331: "NR Radio Resource Control (RRC); Protocol Specification".
+- [4] 3GPP TS 23.501: "System Architecture for the 5G System".
+- [5] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
+- [6] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**PC5 QoS flow to SL-DRB mapping rule:** a mapping rule determining on which SL-DRB packets of a PC5 QoS flow shall be carried.
+
+**QoS flow to DRB mapping rule:** a mapping rule determining on which DRB packets of a QoS flow shall be carried.
+
+**Reflective QoS flow to DRB mapping:** a QoS flow to DRB mapping scheme where a UE monitors the QoS flow to DRB mapping rule in the DL, and applies it to in the UL.
+
+**NR sidelink communication:** AS functionality enabling at least V2X communication as defined in TS 23.287 [5], between two or more nearby UEs, using NR technology but not traversing any network node.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|      |                 |
+|------|-----------------|
+| PQFI | PC5 QoS Flow ID |
+|------|-----------------|
+
+|        |                                               |
+|--------|-----------------------------------------------|
+| QFI    | QoS Flow ID                                   |
+| RDI    | Reflective QoS flow to DRB mapping Indication |
+| RQI    | Reflective QoS Indication                     |
+| SDAP   | Service Data Adaptation Protocol              |
+| SL     | Sidelink                                      |
+| SL-DRB | Sidelink Data Radio Bearer                    |
+
+# 4 General
+
+## 4.1 Introduction
+
+The objective is to describe the SDAP architecture and the SDAP entity from a functional point of view. The specified functionality only applies to UE with connection to the 5G-CN and UE in NR sidelink communication.
+
+## 4.2 SDAP architecture
+
+### 4.2.1 SDAP structure
+
+Figure 4.2.1-1 illustrates one possible structure for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2].
+
+![Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities.](e2c1c672349c10dccb2563eff6d8260e_img.jpg)
+
+The diagram illustrates the SDAP sublayer structure. At the top, multiple 'QoS Flows' are shown, each connected to an 'SDAP-SAP' (Service Access Point). These SAPs are part of the 'SDAP sublayer', which contains two 'SDAP entity' blocks. Below the SDAP sublayer, there is a layer for 'Radio Bearers'. Arrows point from the SDAP entities to the Radio Bearers, indicating data flow. Between the SDAP sublayer and the Radio Bearers, there are labels for 'SDAP - PDU' (Protocol Data Unit) and 'PDCP - SDU' (Service Data Unit). Below the Radio Bearers, there is another layer for 'PDCP sublayer', which contains four 'PDCP entity' blocks. Each PDCP entity is connected to an 'SDAP-SAP' (or 'PDCP-SAP' as labeled in the diagram) and receives data from the Radio Bearers.
+
+Diagram of SDAP sublayer structure showing QoS Flows, SDAP entities, Radio Bearers, and PDCP entities.
+
+Figure 4.2.1-1: SDAP sublayer, structure view
+
+The SDAP sublayer is configured by RRC (TS 38.331 [3]). The SDAP sublayer maps QoS flows to DRBs. One or more QoS flows may be mapped onto one DRB. One QoS flow is mapped onto only one DRB at a time in the UL.
+
+In NR sidelink communication, the SDAP sublayer maps PC5 QoS flows to SL-DRBs. One or more PC5 QoS flows may be mapped onto one SL-DRB. One PC5 QoS flow is mapped onto only one SL-DRB at a time in the NR sidelink for transmission.
+
+### 4.2.2 SDAP entities
+
+The SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session for NR Uu. For NR sidelink, SDAP entity is configured per Destination Layer-2 ID and cast type in the UE.
+
+An SDAP entity receives/delivers SDAP SDUs from/to upper layers and submits/receives SDAP data PDUs to/from its peer SDAP entity via lower layers.
+
+- At the transmitting side, when an SDAP entity receives an SDAP SDU from upper layers, it constructs the corresponding SDAP data PDU and submits it to lower layers;
+- At the receiving side, when an SDAP entity receives an SDAP data PDU from lower layers, it retrieves the corresponding SDAP SDU and delivers it to upper layers.
+
+Figure 4.2.2-1 illustrates the functional view of the SDAP entity for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2].
+
+![Figure 4.2.2-1: SDAP layer, functional view. This diagram illustrates the functional view of the SDAP layer for both the User Equipment (UE) and the NG-RAN. It shows the flow of QoS flows through the SDAP entity, including mapping to DRBs/SL-DRBs and the handling of SDAP headers. The diagram is split into two main vertical sections: UE/NG-RAN/UEA on the left and NG-RAN/UE/UEB on the right, connected by a 'Radio Interface (Uu/PC5)' at the bottom. On the UE side (left), a 'QoS flow' enters a 'Transmitting SDAP entity'. It first goes to 'Mapping of QoS flow to a DRB/SL DRB'. From there, two paths emerge: one where 'SDAP header is configured' leads to 'Adding SDAP header' before exiting the entity, and another where 'SDAP header is not configured' exits the entity directly. On the NG-RAN side (right), a 'QoS flow' exits the 'Receiving SDAP entity'. It first goes to 'Removing SDAP header'. From there, two paths emerge: one where 'SDAP header is configured' leads to 'Reflective QoS flow to DRB mapping' (shown in a dashed box) before exiting, and another where 'SDAP header is not configured' exits the entity directly. The 'Radio Interface (Uu/PC5)' is shown as a thick horizontal bar at the bottom with arrows indicating bidirectional data flow between the SDAP entities and the interface.](e1a0d046fbe7f28f5e93a47091851747_img.jpg)
+
+Figure 4.2.2-1: SDAP layer, functional view. This diagram illustrates the functional view of the SDAP layer for both the User Equipment (UE) and the NG-RAN. It shows the flow of QoS flows through the SDAP entity, including mapping to DRBs/SL-DRBs and the handling of SDAP headers. The diagram is split into two main vertical sections: UE/NG-RAN/UEA on the left and NG-RAN/UE/UEB on the right, connected by a 'Radio Interface (Uu/PC5)' at the bottom. On the UE side (left), a 'QoS flow' enters a 'Transmitting SDAP entity'. It first goes to 'Mapping of QoS flow to a DRB/SL DRB'. From there, two paths emerge: one where 'SDAP header is configured' leads to 'Adding SDAP header' before exiting the entity, and another where 'SDAP header is not configured' exits the entity directly. On the NG-RAN side (right), a 'QoS flow' exits the 'Receiving SDAP entity'. It first goes to 'Removing SDAP header'. From there, two paths emerge: one where 'SDAP header is configured' leads to 'Reflective QoS flow to DRB mapping' (shown in a dashed box) before exiting, and another where 'SDAP header is not configured' exits the entity directly. The 'Radio Interface (Uu/PC5)' is shown as a thick horizontal bar at the bottom with arrows indicating bidirectional data flow between the SDAP entities and the interface.
+
+**Figure 4.2.2-1: SDAP layer, functional view**
+
+Reflective QoS flow to DRB mapping is performed at UE, as specified in the clause 5.3.2, if DL SDAP header is configured.
+
+For NR sidelink communication, reflective PC5 QoS flow to SL-DRB mapping is not supported.
+
+## 4.3 Services
+
+### 4.3.1 Services provided to upper layers
+
+The SDAP sublayer provides its service to the user plane upper layers. The following services are provided by SDAP to upper layers:
+
+- transfer of user plane data.
+
+### 4.3.2 Services expected from lower layers
+
+An SDAP entity expects the following services from lower layers:
+
+- user plane data transfer service;
+- in-order delivery except when out of order delivery is configured by RRC (TS 38.331 [3]).
+
+## 4.4 Functions
+
+The SDAP sublayer supports the following functions:
+
+- transfer of user plane data;
+- mapping between a QoS flow and a DRB for both DL and UL;
+- mapping between a PC5 QoS flow and a SL-DRB for NR sidelink communication;
+- marking QoS flow ID in both DL and UL packets;
+- marking PC5 QoS flow ID in unicast of NR sidelink communication packets;
+- reflective QoS flow to DRB mapping for the UL SDAP data PDUs.
+
+# --- 5 SDAP procedures
+
+## 5.1 SDAP entity handling
+
+### 5.1.1 SDAP entity establishment
+
+When RRC (TS 38.331 [3]) requests an SDAP entity establishment, the UE shall:
+
+- establish an SDAP entity;
+- follow the procedures in clause 5.2.1 and 5.2.2.
+
+When RRC (TS 38.331 [3]) requests establishment of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall:
+
+- establish an SDAP entity;
+- follow the procedures in clauses 5.2.3 and 5.2.4.
+
+### 5.1.2 SDAP entity release
+
+When RRC (TS 38.331 [3]) requests an SDAP entity release, the UE shall:
+
+- release the SDAP entity.
+
+When RRC (TS 38.331 [3]) requests release of an SDAP entity for unicast, groupcast or broadcast of NR sidelink communication, the UE shall:
+
+- release the SDAP entity.
+
+## 5.2 Data transfer
+
+### 5.2.1 Uplink
+
+At the reception of an SDAP SDU from upper layer for a QoS flow, the transmitting SDAP entity shall:
+
+- if there is no stored QoS flow to DRB mapping rule for the QoS flow as specified in the clause 5.3:
+  - map the SDAP SDU to the default DRB;
+- else:
+  - map the SDAP SDU to the DRB according to the stored QoS flow to DRB mapping rule;
+- if the DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header,
+  - construct the UL SDAP data PDU as specified in the clause 6.2.2.3;
+- else:
+  - construct the UL SDAP data PDU as specified in the clause 6.2.2.1;
+- submit the constructed UL SDAP data PDU to the lower layers.
+
+NOTE 1: UE behaviour is not defined if there is neither a default DRB nor a stored QoS flow to DRB mapping rule for the QoS flow.
+
+NOTE 2: Default DRB is always configured with UL SDAP header (TS 38.331 [3]).
+
+### 5.2.2 Downlink
+
+At the reception of an SDAP data PDU from lower layers for a QoS flow, the receiving SDAP entity shall:
+
+- if the DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - perform reflective QoS flow to DRB mapping as specified in the clause 5.3.2;
+  - perform RQI handling as specified in the clause 5.4;
+  - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.2.
+- else:
+  - retrieve the SDAP SDU from the DL SDAP data PDU as specified in the clause 6.2.2.1;
+- deliver the retrieved SDAP SDU to the upper layer.
+
+### 5.2.3 SL transmission
+
+At the reception of an SDAP SDU from upper layer for a PC5 QoS flow, the transmitting SDAP entity shall:
+
+- if there is no stored PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow as specified in the clause 5.5:
+  - map the SDAP SDU to the default SL-DRB;
+- else:
+
+- map the SDAP SDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule;
+- if the SL-DRB to which the SDAP SDU is mapped is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - construct the SL SDAP data PDU as specified in the clause 6.2.2.4;
+- else:
+  - construct the SL SDAP data PDU as specified in the clause 6.2.2.1;
+- submit the constructed SL SDAP data PDU to the lower layers.
+
+### 5.2.4 SL reception
+
+At the reception of an SDAP data PDU from lower layers for a PC5 QoS flow, the receiving SDAP entity shall:
+
+- if the SL-DRB from which this SDAP data PDU is received is configured by RRC (TS 38.331 [3]) with the presence of SDAP header:
+  - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.4;
+- else:
+  - retrieve the SDAP SDU from the SL SDAP data PDU as specified in the clause 6.2.2.1;
+- deliver the retrieved SDAP SDU to the upper layer.
+
+## 5.3 QoS flow to DRB mapping
+
+### 5.3.1 Configuration
+
+When RRC (TS 38.331 [3]) configures an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
+
+- if the SDAP entity has already been established and there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the default DRB;
+  - submit the end-marker control PDU to the lower layers.
+- if the stored UL QoS flow to DRB mapping rule is different from the configured QoS flow to DRB mapping rule for the QoS flow and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;
+  - submit the end-marker control PDU to the lower layers.
+- store the configured UL QoS flow to DRB mapping rule for the QoS flow.
+
+When RRC (TS 38.331 [3]) releases an UL QoS flow to DRB mapping rule for a QoS flow, the SDAP entity shall:
+
+- remove the UL QoS flow to DRB mapping rule for the QoS flow.
+
+### 5.3.2 Reflective mapping
+
+For each received DL SDAP data PDU with RDI set to 1, the SDAP entity shall:
+
+- process the QFI field in the SDAP header and determine the QoS flow;
+
+- if there is no stored QoS flow to DRB mapping rule for the QoS flow and a default DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the default DRB;
+  - submit the end-marker control PDU to the lower layers;
+- if the stored QoS flow to DRB mapping rule for the QoS flow is different from the QoS flow to DRB mapping of the DL SDAP data PDU and the DRB according to the stored QoS flow to DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of UL SDAP header:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the QoS flow;
+  - map the end-marker control PDU to the DRB according to the stored QoS flow to DRB mapping rule;
+  - submit the end-marker control PDU to the lower layers;
+- store the QoS flow to DRB mapping of the DL SDAP data PDU as the QoS flow to DRB mapping rule for the UL.
+
+### 5.3.3 DRB release
+
+When RRC (TS 38.331 [3]) indicates that a DRB is released, the SDAP entity shall:
+
+- remove all QoS flow to DRB mappings associated with the released DRB based on the clauses 5.3.1 and 5.3.2.
+
+## 5.4 RQI handling
+
+For each received DL SDAP data PDU with RQI set to 1, the SDAP entity shall:
+
+- inform the NAS layer of the RQI and QFI.
+
+## 5.5 PC5 QoS flow to SL-DRB mapping
+
+### 5.5.1 Configuration
+
+When RRC (TS 38.331 [3]) configures a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall:
+
+- for unicast of NR sidelink communication, if the SDAP entity has already been established and there is no stored SL-DRB mapping rule for the PC5 QoS flow and a default SL-DRB is configured:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow;
+  - map the end-marker control PDU to the default SL-DRB;
+  - submit the end-marker control PDU to the lower layers;
+- for unicast of NR sidelink communication, if the stored PC5 QoS flow to SL-DRB mapping rule is different from the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow and the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule is configured by RRC (TS 38.331 [3]) with the presence of SL SDAP header:
+  - construct an end-marker control PDU, as specified in the clause 6.2.3, for the PC5 QoS flow;
+  - map the end-marker control PDU to the SL-DRB according to the stored PC5 QoS flow to SL-DRB mapping rule;
+  - submit the end-marker control PDU to the lower layers;
+- store the configured PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow.
+
+When RRC (TS 38.331 [3]) releases a PC5 QoS flow to SL-DRB mapping rule for a PC5 QoS flow, the SDAP entity shall:
+
+- remove the PC5 QoS flow to SL-DRB mapping rule for the PC5 QoS flow.
+
+### 5.5.2 SL-DRB release
+
+When RRC (TS 38.331 [3]) indicates that an SL-DRB is released, the SDAP entity shall:
+
+- remove all PC5 QoS flow to SL-DRB mappings associated with the released SL-DRB based on the clause 5.5.1.
+
+# --- 6 Protocol data units, formats, and parameters
+
+## 6.1 Protocol data units
+
+### 6.1.1 Data PDU
+
+The SDAP Data PDU is used to convey one or more of followings:
+
+- SDAP header;
+- user plane data.
+
+### 6.1.2 Control PDU
+
+#### a) End-Marker Control PDU
+
+End-Marker control PDU is used by the SDAP entity at UE to indicate that it stops the mapping of the SDAP SDU of the QoS flow indicated by the QFI/PQFI to the DRB/SL-DRB on which the End-Marker control PDU is transmitted.
+
+## 6.2 Formats
+
+### 6.2.1 General
+
+A SDAP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6.2, bit strings are represented by tables in which the first and most significant bit is the left most bit of the first line of the table, the last and least significant bit is the rightmost bit of the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines.
+
+SDAP SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. An SDAP SDU is included into a SDAP PDU from the first bit onward.
+
+For groupcast and broadcast of NR sidelink communication, only SDAP data PDU without SDAP header is supported.
+
+### 6.2.2 Data PDU
+
+#### 6.2.2.1 Data PDU without SDAP header
+
+An SDAP PDU consists only of a data field and does not consist of any SDAP header, as described in Figure 6.2.2.1-1.
+
+![Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data', followed by an ellipsis '....', and the bottom block is labeled 'Oct N'. To the right of the top block is 'Oct 1'.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Diagram of SDAP Data PDU format without SDAP header. It shows a vertical stack of data blocks. The top block is labeled 'Data', followed by an ellipsis '....', and the bottom block is labeled 'Oct N'. To the right of the top block is 'Oct 1'.
+
+Figure 6.2.2.1-1: SDAP Data PDU format without SDAP header
+
+#### 6.2.2.2 DL Data PDU with SDAP header
+
+Figure 6.2.2.2 – 1 shows the format of SDAP Data PDU of DL with SDAP header being configured.
+
+![Diagram of DL SDAP Data PDU format with SDAP header. The header is divided into three fields: RDI, RQI, and QFI. Below the header are data blocks labeled 'Data', '...', and 'Data'. To the right, the header is labeled 'Oct 1', the first data block 'Oct 2', and the last data block 'Oct N'.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg)
+
+Diagram of DL SDAP Data PDU format with SDAP header. The header is divided into three fields: RDI, RQI, and QFI. Below the header are data blocks labeled 'Data', '...', and 'Data'. To the right, the header is labeled 'Oct 1', the first data block 'Oct 2', and the last data block 'Oct N'.
+
+Figure 6.2.2.2-1: DL SDAP Data PDU format with SDAP header
+
+#### 6.2.2.3 UL Data PDU with SDAP header
+
+Figure 6.2.2.3 – 1 shows the format of SDAP Data PDU of UL with SDAP header being configured.
+
+![Diagram of UL SDAP Data PDU format with SDAP header. The header is divided into three fields: D/C, R, and QFI. Below the header are data blocks labeled 'Data', '...', and 'Data'. To the right, the header is labeled 'Oct 1', the first data block 'Oct 2', and the last data block 'Oct N'.](704082cc3e11776bda29595c76411362_img.jpg)
+
+Diagram of UL SDAP Data PDU format with SDAP header. The header is divided into three fields: D/C, R, and QFI. Below the header are data blocks labeled 'Data', '...', and 'Data'. To the right, the header is labeled 'Oct 1', the first data block 'Oct 2', and the last data block 'Oct N'.
+
+Figure 6.2.2.3-1: UL SDAP Data PDU format with SDAP header
+
+#### 6.2.2.4 SL Data PDU with SDAP header for unicast of NR sidelink communication
+
+Figure 6.2.2.4–1 shows the format of SDAP Data PDU for unicast of NR sidelink communication with SDAP header being configured.
+
+![Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a vertical stack of octets. Oct 1 contains three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Oct 2 contains 'Data'. Oct N contains 'Data'. An ellipsis (...) is shown between Oct 2 and Oct N.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication. The diagram shows a vertical stack of octets. Oct 1 contains three fields: D/C (1 bit), R (1 bit), and PQFI (6 bits). Oct 2 contains 'Data'. Oct N contains 'Data'. An ellipsis (...) is shown between Oct 2 and Oct N.
+
+Figure 6.2.2.4-1: SL SDAP Data PDU format with SDAP header for unicast of NR sidelink communication
+
+### 6.2.3 End-Marker Control PDU
+
+Figure 6.2.3-1 shows the format of End-Marker Control PDU.
+
+![Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits).](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+Figure 6.2.3-1: End-Marker Control PDU. The diagram shows a single octet (Oct 1) divided into three fields: D/C (1 bit), R (1 bit), and QFI/PQFI (6 bits).
+
+Figure 6.2.3-1: End-Marker Control PDU
+
+## 6.3 Parameters
+
+### 6.3.1 General
+
+If not otherwise mentioned in the definition of each field, then the bits in the parameters shall be interpreted as follows: the left most bit is the first and most significant bit and the right most bit is the last and least significant bit.
+
+Unless otherwise mentioned, integers are encoded in standard binary encoding for unsigned integers. In all cases the bits appear ordered from MSB to LSB when read in the PDU.
+
+### 6.3.2 Data
+
+Length: Variable
+
+This field includes the SDAP SDU.
+
+### 6.3.3 D/C
+
+Length: 1 bit,
+
+The D/C bit indicates whether the SDAP PDU is an SDAP Data PDU or an SDAP Control PDU.
+
+Table 6.3.3-1: D/C field
+
+| Bit | Description |
+|-----|-------------|
+| 0   | Control PDU |
+| 1   | Data PDU    |
+
+### 6.3.4 QFI
+
+Length: 6 bits
+
+The QFI field indicates the ID of the QoS flow (TS 23.501 [4]) to which the SDAP PDU belongs.
+
+### 6.3.5 R
+
+Length: 1 bit
+
+Reserved. In this version of the specification reserved bits shall be set to 0. Reserved bits shall be ignored by the receiver.
+
+### 6.3.6 RQI
+
+Length: 1 bit,
+
+The RQI bit indicates whether NAS should be informed of the updated of SDF to QoS flow mapping rules (TS 23.501 [4]).
+
+**Table 6.3.6-1: RQI field**
+
+| Bit | Description                             |
+|-----|-----------------------------------------|
+| 0   | No action                               |
+| 1   | To inform NAS that RQI bit is set to 1. |
+
+### 6.3.7 RDI
+
+Length: 1 bit,
+
+The RDI bit indicates whether QoS flow to DRB mapping rule should be updated.
+
+**Table 6.3.7-1: RDI field**
+
+| Bit | Description                            |
+|-----|----------------------------------------|
+| 0   | No action                              |
+| 1   | To store QoS flow to DRB mapping rule. |
+
+### 6.3.8 PQFI
+
+Length: 6 bits
+
+The PQFI field indicates the ID of the PC5 QoS flow (as specified in TS 24.587[6]) to which the SDAP PDU belongs.
+
+# Annex A (informative): Change history
+
+| Change history |             |           |      |     |     |                                                                                     |  |             |
+|----------------|-------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting     | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                     |  | New version |
+| 06/2017        | RAN2 NR AH  |           | -    | -   | -   | First version                                                                       |  | 0.1.0       |
+| 08/2017        | RAN2#99     |           | -    | -   | -   | To capture agreements made in RAN2#99                                               |  | 0.2.0       |
+| 09/2017        | RAN#77      |           | -    | -   | -   | Presented to RAN#77 for information                                                 |  | 1.0.0       |
+| 10/2017        | RAN2#99 bis |           |      |     |     | To capture agreements made in RAN2#99bis                                            |  | 1.1.0       |
+| 11/2017        | RAN2#100    |           |      |     |     | To remove editor's notes.                                                           |  | 1.2.0       |
+| 01/2018        | RAN2 NR AH  |           |      |     |     | To capture agreements made in RAN2 NR AH                                            |  | 1.3.0       |
+| 04/2018        | RAN2#101bis |           |      |     |     | To capture agreements made in RAN2#101                                              |  | 1.4.0       |
+|                | RAN2#101bis |           |      |     |     | To capture agreements made in RAN2#101bis                                           |  | 1.5.0       |
+| 05/2018        | RAN2#102    |           |      |     |     | To capture agreements made in RAN2#102                                              |  | 1.6.0       |
+| 06/2018        | RP-80       | RP-181256 |      |     |     | Provided to RAN #80 for approval                                                    |  | 2.0.1       |
+|                | RP-80       | RP-181266 |      |     |     | Provided to RAN #80 for approval (update as RP-181256 was misused for another Tdoc) |  | 2.0.2       |
+|                |             |           |      |     |     | Upgraded to Rel-15 after the plenary approval                                       |  | 15.0.0      |
+| 09/2018        | RP-81       | RP-181940 | 0006 | 1   | F   | Miscellaneous corrections for SDAP                                                  |  | 15.1.0      |
+|                | RP-81       | RP-181939 | 0007 | -   | D   | Miscellaneous corrections to SDAP                                                   |  | 15.1.0      |
+|                | RP-81       | RP-181942 | 0008 | 1   | F   | Correction on flow remapping from default DRB                                       |  | 15.1.0      |
+| 03/2020        | RP-87       | RP-200346 | 0014 | 1   | B   | Introduction of 5G V2X_NRSL to 37.324                                               |  | 16.0.0      |
+| 07/2020        | RP-88       | RP-201176 | 0016 | 1   | F   | Capture latest agreements on SDAP                                                   |  | 16.1.0      |
+| 09/2020        | RP-89       | RP-201927 | 0019 | -   | F   | 37.324 corrections on Sidelink                                                      |  | 16.2.0      |
+| 06/2021        | RP-92       | RP-211470 | 0020 | 2   | F   | Correction of PQFI terminology in SDAP                                              |  | 16.3.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37460/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/37_series/37460/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..962daa0dda7d689bd2591bed6eb9551055d932fc
--- /dev/null
+++ b/marked/Rel-16/37_series/37460/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcef1632d5456cd51229cf2a854d4f12875707f24061f1e95cbd6194d0d76247
+size 43320
diff --git a/marked/Rel-16/37_series/37460/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/37_series/37460/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..318ddc5301798514fd3220f72d6e260d0c753903
--- /dev/null
+++ b/marked/Rel-16/37_series/37460/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8975ab94f7040e61c488e971d93c0b64a7d169f1b1a2b709abbc9f59968d8b0a
+size 24754
diff --git a/marked/Rel-16/37_series/37460/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/37_series/37460/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ccc20c5a9a7ef0ca2f4399eb5b3c53f4a66a40a0
--- /dev/null
+++ b/marked/Rel-16/37_series/37460/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f9af37ab4cfa534442ac88c3ba908cb2c24adf5a99beb24cda3093a0f9092fb
+size 23233
diff --git a/marked/Rel-16/37_series/37460/raw.md b/marked/Rel-16/37_series/37460/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c9b1fef8023fa37d940536eb556abe913b81680
--- /dev/null
+++ b/marked/Rel-16/37_series/37460/raw.md
@@ -0,0 +1,262 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                      |           |
+|----------------------------------------------------------------------|-----------|
+| Foreword .....                                                       | 4         |
+| 1 Scope.....                                                         | 5         |
+| 2 References.....                                                    | 5         |
+| 3 Abbreviations .....                                                | 5         |
+| 4 General aspects .....                                              | 6         |
+| 4.1 Introduction .....                                               | 6         |
+| 4.2 Iuant interface general principles .....                         | 6         |
+| 4.3 Iuant interface specification objectives .....                   | 6         |
+| 4.4 Iuant interface characteristics.....                             | 6         |
+| 5 Functions of the Iuant interface protocols.....                    | 7         |
+| 5.1 Physical layer functions .....                                   | 7         |
+| 5.2 Data link layer functions .....                                  | 7         |
+| 5.3 Application layer functions .....                                | 8         |
+| 5.3.1 Control of RET antennas .....                                  | 8         |
+| 5.3.2 Application software and configuration data download.....      | 8         |
+| 5.3.3 Alarm reporting .....                                          | 8         |
+| 5.3.4 Operator specific data storage .....                           | 8         |
+| 5.3.5 Control of Tower Mounted Amplifiers (TMAs) .....               | 8         |
+| 6 Other Iuant interface specifications .....                         | 9         |
+| 6.1 Iuant interface: Layer 1 (TS 37.461).....                        | 9         |
+| 6.2 Iuant interface: Signalling Transport (TS 37.462) .....          | 9         |
+| 6.3 Void.....                                                        | 9         |
+| 6.4 Summary of Iuant interface Technical Specifications .....        | 9         |
+| 6.5 Iuant interface: Application part specification (TS 37.466)..... | 9         |
+| <b>Annex A (informative): OSI model overview .....</b>               | <b>10</b> |
+| Annex B (informative): Change History .....                          | 11        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TS 25.401: "UTRAN Overall Description".
+- [2] 3GPP TS 37.461: "Iuant Interface: Layer 1".
+- [3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport".
+- [4] void
+- [5] ISO/IEC 13239 (2nd Edition, March 2000): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures".
+- [6] 3GPP TS 25.442: "UTRAN implementation-specific O&M transport".
+- [7] 3GPP TS 37.466: "Iuant interface: Application Part".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                            |
+|---------|--------------------------------------------|
+| HDLC    | High-Level Data Link Control               |
+| IP      | Internet Protocol                          |
+| O&M     | Operations & Maintenance                   |
+| OSI     | Open Systems Interconnection               |
+| RET     | Remote Electrical Tilting                  |
+| RETAP   | Remote Electrical Tilting Application Part |
+| TMA     | Tower Mounted Amplifier                    |
+| TMAAP   | Tower Mounted Amplifier application part   |
+| UMTS    | Universal Mobile Telecommunications System |
+| E-UTRAN | Evolved UTRAN                              |
+
+# --- 4 General aspects
+
+## 4.1 Introduction
+
+The Iuant interface for the control of RET antennas or TMAs is a logical part of the RAN Node as shown for a Node B in figure 9 of TS 25.401 [1] for UTRAN. Therefore, no new RAN element for the RET antennas or TMAs and no new
+
+RAN element manager is needed. The existing Implementation Specific O&M transport (see TS 25.442 [6] for UMTS) is used for the connection between the RET antennas or TMAs control unit and the Node B element manager.
+
+The Iuant interface between the Implementation Specific O&M function and the RET antenna control unit function is specified in detail in the specifications for layer 1, signalling transport and RET application part (TS 37.461 [2], TS 37.462 [3], TS 37.466 [7]).
+
+## 4.2 Iuant interface general principles
+
+The Iuant interface for the RET antenna control is based on a three-layer protocol model. The three-layer model is a compact form of the OSI seven-layer reference model and includes only layers 1, 2 and 7:
+
+- The Physical Layer (Layer 1) defines the signalling levels and basic data characteristics including the data rates;
+- The Data Link Layer (Layer 2) for the Signalling Transport uses a specific class of the HDLC standard as defined in ISO/IEC 13239 [5];
+- The Application Layer (Layer 7) defines the data payload format and the required command set. This layer is called the "Iuant: Application Part".
+
+This compact model for the control interface provides an efficient protocol stack suitable for implementation on a single embedded micro-controller.
+
+## 4.3 Iuant interface specification objectives
+
+The Iuant interface specifications shall facilitate the following:
+
+- Controlling the tilting of RET antennas remotely from the O&M Network and locally from the Node B;
+- Indicating of TMA alarms and optionally controlling the gain of TMAs remotely from the O&M Network and locally from the Node B;
+- Interfacing a mix of RET antennas, TMAs and RAN Node from different vendors;
+- Providing RET or TMAs functionality accompanied by an appropriate set of signalling commands and control parameters;
+- Support of error and alarm handling.
+
+## 4.4 Iuant interface characteristics
+
+The Iuant interface has a protocol structure as shown below in figure 4.4.1.
+
+![Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack is for the RAN Node and consists of three layers: 'Implementation specific O&M function' at the top, 'HDLC' in the middle, and 'PHY' at the bottom. The 'Implementation specific O&M function' layer is further divided into 'See Reference [6]' (blue) and two sub-functions 'RETAP' and 'TMAAP' (yellow). The right stack is for a secondary device and consists of 'RETAP' and 'TMAAP' (yellow) at the top, 'HDLC' in the middle, and 'PHY' at the bottom. The 'PHY' layers of both stacks are connected to the 'Iuant' interface line. The label 'RAN Node' is placed below the 'Iuant' line.](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+Figure 4.4.1: Protocol structure for Iuant interface. The diagram shows two protocol stacks separated by a vertical line labeled 'Iuant'. The left stack is for the RAN Node and consists of three layers: 'Implementation specific O&M function' at the top, 'HDLC' in the middle, and 'PHY' at the bottom. The 'Implementation specific O&M function' layer is further divided into 'See Reference [6]' (blue) and two sub-functions 'RETAP' and 'TMAAP' (yellow). The right stack is for a secondary device and consists of 'RETAP' and 'TMAAP' (yellow) at the top, 'HDLC' in the middle, and 'PHY' at the bottom. The 'PHY' layers of both stacks are connected to the 'Iuant' interface line. The label 'RAN Node' is placed below the 'Iuant' line.
+
+**Figure 4.4.1: Protocol structure for Iuant interface**
+
+As the Iuant and the Implementation Specific O&M are different interfaces with e.g. different addressing schemes a mediation function is needed. This mediation function uses on one side a protocol that uses the implementation specific O&M bearer (e.g. IP) and on the other side the Iuant protocol.
+
+# 5 Functions of the Iuant interface protocols
+
+## 5.1 Physical layer functions
+
+The physical layer provides a multi drop broadcast link between the primary device (RAN Node) and all secondary devices (RET antennas or TMAs). Any message transmitted will be received by all other devices. If two devices transmit at the same time, their messages will be garbled.
+
+The connection requires a half duplex communication, which requires an appropriate scheme for the timing and access control of the connection.
+
+## 5.2 Data link layer functions
+
+The data link layer provides:
+
+- A data packet communication format;
+- An addressing scheme;
+- A master/slave relationship whereby the primary device controls the half duplex timing;
+- A message checksum scheme to protect from transmission errors;
+- A message sequence numbering scheme which protects layer 7 from:
+
+- Duplicated messages;
+- Deleted messages;
+- Receiving messages in the wrong order.
+- A flow control mechanism protecting each device from being overrun by messages.
+
+These functions provide layer 7 with a safe full-duplex connection between the primary device and any secondary device. This full duplex connection allows both the primary and secondary device to transmit layer 7 messages to the opposite device of the connection, whenever they need to. Actual delivery time on layer 2 will depend on the layer 2 polling frequency, which is chosen by the primary device.
+
+## 5.3 Application layer functions
+
+The list of functions on the Iuant interface is the following:
+
+- Control of RET antennas;
+- Application software and configuration data download;
+- Alarm Reporting;
+- Operator specific data storage;
+- Control of Tower Mounted Amplifiers (TMAs).
+
+### 5.3.1 Control of RET antennas
+
+A RET device provides means to adjust the electrical tilt of one or multiple antennas. The set of procedures to control RET antennas provides means to control the electrical tilt of one or more RET antennas remotely. The procedures are defined in TS 37.466 [7].
+
+### 5.3.2 Application software and configuration data download
+
+The interface provides means for downloading new application software and configuration data to a secondary device.
+
+The support of application software download to a secondary device is optional. If a secondary device supports application software download, it shall reset itself and start running the new application software automatically after the completed download. Further details on the software download procedure (e.g. the different states of the secondary device and the supported elementary procedures in these states) are described in subclause 6.1 of TS 37.466 [7].
+
+### 5.3.3 Alarm reporting
+
+The secondary device reports every change in error status after subscription for alarm reporting by transmitting alarm messages to the primary device. Alarm information can also be interrogated in the application layer.
+
+### 5.3.4 Operator specific data storage
+
+The secondary device provides means for storage of operator specific data, e.g. inventory information.
+
+### 5.3.5 Control of Tower Mounted Amplifiers (TMAs)
+
+The TMA device provides means to indicate alarms and optionally to adjust the gain of TMAs. The set of procedures to control TMAs are defined in TS 37.466 [7].
+
+# --- 6 Other Iuant interface specifications
+
+## 6.1 Iuant interface: Layer 1 (TS 37.461)
+
+TS 37.461 [2] specifies the standards allowed for implementation of Layer 1 (physical layer) on the Iuant interface.
+
+## 6.2 Iuant interface: Signalling Transport (TS 37.462)
+
+TS 37.462 [3] specifies the signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface.
+
+## 6.3 Void
+
+## 6.4 Summary of Iuant interface Technical Specifications
+
+The relationship between the technical specifications that define the Iuant interface is shown in figure 6.4.1.
+
+![Diagram showing the relationship between technical specifications for the Iuant interface across three layers: Radio Network Layer (RETAP TMAAP, TS 37.466), Transport Layer (Iuant Transport, TS 37.462), and Physical Layer (TS 37.461).](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+The diagram illustrates the technical specifications for the Iuant interface across three layers, enclosed in a dashed rectangular box. The layers are stacked vertically:
+
+- Radio Network Layer:** Contains the text "RETAP TMAAP" and "TS 37.466".
+- Transport Layer:** Contains the text "Iuant Transport" and "TS 37.462".
+- Physical Layer:** Contains the text "TS 37.461".
+
+Diagram showing the relationship between technical specifications for the Iuant interface across three layers: Radio Network Layer (RETAP TMAAP, TS 37.466), Transport Layer (Iuant Transport, TS 37.462), and Physical Layer (TS 37.461).
+
+**Figure 6.4.1: Iuant Interface Technical Specifications**
+
+## 6.5 Iuant interface: Application part specification (TS 37.466)
+
+TS 37.466 [7] specifies protocols for application part to be used over the Iuant interface.
+
+# Annex A (informative): OSI model overview
+
+![Diagram illustrating the OSI model layers and communication paths between two devices. The diagram shows two stacks of layers. The left stack has four layers, and the right stack has four layers. Vertical arrows within each stack indicate data flow between adjacent layers. Horizontal dashed arrows connect corresponding layers between the two stacks (Layer 1 to Layer 1, Layer 2 to Layer 2, Layer 3 to Layer 3). A solid horizontal arrow connects the bottom layer of the left stack to the bottom layer of the right stack. Below the stacks, a legend shows a solid arrow pointing to a series of vertical bars, and a dashed arrow pointing to a series of vertical bars.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg)
+
+Diagram illustrating the OSI model layers and communication paths between two devices. The diagram shows two stacks of layers. The left stack has four layers, and the right stack has four layers. Vertical arrows within each stack indicate data flow between adjacent layers. Horizontal dashed arrows connect corresponding layers between the two stacks (Layer 1 to Layer 1, Layer 2 to Layer 2, Layer 3 to Layer 3). A solid horizontal arrow connects the bottom layer of the left stack to the bottom layer of the right stack. Below the stacks, a legend shows a solid arrow pointing to a series of vertical bars, and a dashed arrow pointing to a series of vertical bars.
+
+**Figure A.1: Relevant OSI model layers**
+
+Figure A.1 shows the relevant OSI model layers and the communication paths between the primary and secondary device.
+
+The two important aspects of the OSI model are:
+
+- It defines a layered structure for the communication software;
+- It provides each layer with an apparent direct link to the same layer at the other device.
+
+However, in real life, the only actual message path between the two devices is through the physical connection between the two layer 1 entities.
+
+The layer 2 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path:
+
+- Layer 2 at the first device passes the message down to Layer 1;
+- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device;
+- Layer 1 at the second device passes the message up to Layer 2 at the second device.
+
+Likewise, layer 7 entities appear to communicate directly. In actual fact, a message passed from the first device to the second device takes the following path:
+
+- Layer 7 at the first device passes the message down to Layer 2;
+- Layer 2 at the first device passes the message down to Layer 1;
+- Layer 1 transmits the message across the physical connection (for instance a wire) to layer 1 at the second device;
+- Layer 1 at the second device passes the message up to Layer 2 at the second device;
+- Layer 2 at the second device passes the message up to Layer 7 at the second device.
+
+# --- Annex B (informative): Change History
+
+| Change history |          |           |      |     |     |                                                                     |             |
+|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103   | R3-190079 |      |     |     | Text transferred from 25.460 v15.0.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83   | RP-190582 |      |     |     | Specification approved by RAN plenary                               | 15.1.0      |
+| 2019-12        | RP-86    | RP-192915 | 0001 | 5   | F   | Correction for luant                                                | 15.2.0      |
+| 2020-07        | RAN#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37461/1640ec1dfae8bdfa5af950db7623febc_img.jpg b/marked/Rel-16/37_series/37461/1640ec1dfae8bdfa5af950db7623febc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3af5e10bd024f7e9562ed7ef9169c105c3c3075a
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/1640ec1dfae8bdfa5af950db7623febc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:772536a8ae9823ce90ad911ea06d3bf8b6ab6f8d39a4a0025f6fc68f04b7da5d
+size 40217
diff --git a/marked/Rel-16/37_series/37461/252ea48d02dce93965b91746fb376f35_img.jpg b/marked/Rel-16/37_series/37461/252ea48d02dce93965b91746fb376f35_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..181b6e9dd842d7a0a0b150da3274c251a815d39d
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/252ea48d02dce93965b91746fb376f35_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b32c8d47f806394138f35d84e80729caac5aeb04837719f0b46ebb7530567be
+size 54127
diff --git a/marked/Rel-16/37_series/37461/3084f66c81a49b6225666f212179642c_img.jpg b/marked/Rel-16/37_series/37461/3084f66c81a49b6225666f212179642c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7bcd8d0834c4e24466dba1df8db2291f5cd2850e
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/3084f66c81a49b6225666f212179642c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db2760aadd652337aaa2ad2d265c94a6939bc803c7d40a402ad09d02afd1fd10
+size 26247
diff --git a/marked/Rel-16/37_series/37461/8b79f5ec940d107c246612c2a2ec519f_img.jpg b/marked/Rel-16/37_series/37461/8b79f5ec940d107c246612c2a2ec519f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..72f9e3e17ab82dd0cda6af548090ef40313dbf83
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/8b79f5ec940d107c246612c2a2ec519f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a35e45c8856be8225367b4f79524ffeb9c8fa3b0f2086af132228219dab102f
+size 24437
diff --git a/marked/Rel-16/37_series/37461/a6a8016b231533e7f34b550f4676afc6_img.jpg b/marked/Rel-16/37_series/37461/a6a8016b231533e7f34b550f4676afc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3dc5995cc94ade42ab9cc46aa04bf6597671c321
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/a6a8016b231533e7f34b550f4676afc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84c432101af411e34f57c47d405f7ad3930084b5363084d2f1acb99a0859abfb
+size 50977
diff --git a/marked/Rel-16/37_series/37461/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/37_series/37461/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d40a353121450780eab5d072aff61ca43f286a9
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8374cbce12e39e6995dd03e3186d05cb638fa3de41fe26475677912106a57512
+size 36622
diff --git a/marked/Rel-16/37_series/37461/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/37_series/37461/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11a1af3d11499c2524b1c932f7f1feb96c8be719
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:809de1933e1fa47f8e60cd0510bbb275e857dfc216f22b20d57a3b989b3f6b31
+size 47905
diff --git a/marked/Rel-16/37_series/37461/f519a5be118c846f631c992412353fb9_img.jpg b/marked/Rel-16/37_series/37461/f519a5be118c846f631c992412353fb9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..61515019c357f2c3c04729f4227c6a6317d4b014
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/f519a5be118c846f631c992412353fb9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00eee8aceb33c552b8199626c48e84d537aa825c8fb6c4edce6a26157f22e02f
+size 32534
diff --git a/marked/Rel-16/37_series/37461/raw.md b/marked/Rel-16/37_series/37461/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ec17efe4fbc76fbfa981ac7371fff40898df7c8
--- /dev/null
+++ b/marked/Rel-16/37_series/37461/raw.md
@@ -0,0 +1,492 @@
+
+
+# 3GPP TS 37.461 V16.1.0 (2022-06) ---
+
+*Technical Specification*
+
+## **3<sup>rd</sup> Generation Partnership Project; Technical Specification Group Radio Access Network; Iuant interface: Layer 1 (Release 16)** ---
+
+The present document has been developed within the 3<sup>rd</sup> Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## --- **Keywords**
+
+radio, EMC, power supply, antenna
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                         |           |
+|---------------------------------------------------------|-----------|
+| Foreword .....                                          | 4         |
+| 1 Scope.....                                            | 5         |
+| 2 References.....                                       | 5         |
+| 3 Definitions and abbreviations .....                   | 5         |
+| 3.1 Definitions.....                                    | 5         |
+| 3.2 Abbreviations .....                                 | 5         |
+| 4 Iuant layer 1 .....                                   | 6         |
+| 4.1 General .....                                       | 6         |
+| 4.2 RS485 option.....                                   | 7         |
+| 4.3 Modem option .....                                  | 7         |
+| 4.3.1 Interference with existing systems .....          | 9         |
+| 4.3.1.1 Carrier frequency and frequency stability ..... | 9         |
+| 4.3.1.2 Modem isolation and modem emissions.....        | 9         |
+| 4.3.1.3 Modem intermodulation attenuation.....          | 10        |
+| 4.3.2 Recovery time.....                                | 10        |
+| 4.3.3 Impedance.....                                    | 10        |
+| 4.3.4 Modulator characteristics .....                   | 11        |
+| 4.3.4.1 Levels.....                                     | 11        |
+| 4.3.4.2 Spectrum emission mask .....                    | 11        |
+| 4.3.5 Demodulator characteristics .....                 | 11        |
+| 4.3.6 Duty cycle variation .....                        | 11        |
+| 4.3.7 Operating bands.....                              | 12        |
+| 4.3.8 Time delay and accuracy .....                     | 12        |
+| 4.3.9 Insertion Loss .....                              | 12        |
+| 4.3.10 DC port isolation .....                          | 13        |
+| 4.3.11 RET control unit spurious emission .....         | 13        |
+| 4.3.12 Control unit spurious emission.....              | 13        |
+| 4.4 DC power supply.....                                | 14        |
+| 4.4.1 Power consumption .....                           | 14        |
+| 4.4.2 Conducted emission.....                           | 14        |
+| 4.4.3 Power-up characteristics.....                     | 14        |
+| <b>Annex A (normative): Test procedures .....</b>       | <b>16</b> |
+| <b>Annex B (informative): Change history .....</b>      | <b>17</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the standards allowed to implement layer 1 on the Iuant interface for UTRA, E-UTRA and NR.
+
+The specification of transmission delay requirements and O&M requirements are not in the scope of the present document.
+
+The modem option of Iuant layer 1 specification in clause 4.3 applies to UTRA, E-UTRA BS and NR BS type 1-C.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TS 37.462: "UTRAN Iuant interface: Signalling transport".
+- [2] ISO/IEC 8482 (1993-12): "Information technology - Telecommunications and information exchange between systems - Twisted pair multipoint interconnections".
+- [3] TIA/EIA TSB89: "Application guidelines for TIA/EIA-485-A".
+- [4] 3GPP TS 25.101: "Technical Specification Group Radio Access Network; User Equipment (UE) radio transmission and reception (FDD)"
+- [5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception"
+- [6] 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception (FDD)"
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**On-Off-Keying:** A modulation system in which a carrier is switched between two states, ON and OFF.
+
+**Common feeder cable:** Feeder cable where some antenna line devices (e.g. RET, TMA) are connected via the same feeder cable.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|    |              |
+|----|--------------|
+| BS | Base Station |
+|----|--------------|
+
+|      |                                            |
+|------|--------------------------------------------|
+| DC   | Direct Current                             |
+| DL   | Downlink                                   |
+| FDD  | Frequency Division Duplex                  |
+| ISB  | Idle-State Biasing                         |
+| OOK  | On-Off-Keying                              |
+| RET  | Remote Electrical Tilting                  |
+| RF   | Radio Frequency                            |
+| TMA  | Tower Mounted Amplifier                    |
+| UE   | User Equipment                             |
+| UL   | Uplink                                     |
+| UMTS | Universal Mobile Telecommunications System |
+| UTRA | UMTS Terrestrial Radio Access              |
+
+# --- 4 Iuant layer 1
+
+## 4.1 General
+
+There are two layer 1 options:
+
+- RS485 option: A screened multicore cable, which supports a conventional RS485 serial multi-drop bus.
+- Modem option: A connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals.
+
+Both layer 1 options support the connection of two-way serial data and DC power to the RET and/or TMA antenna device.
+
+At least one of these two layer 1 options shall be supported.
+
+The default data rate for both layer 1 options shall be 9.6 kbps. Higher data rates of 38.4 kbps for both layer 1 options and 115.2 kbps only for the RS485 layer 1 option may optionally be supported. Each unit communicates on one of the three data rates, but different units on the same interface may use different data rates.
+
+After a reset, a secondary device shall alternate between supported data rates. When alternating between data rates, the data rate shall be held constant for 300 ms. After every correctly received device scan command (see TS 37.462 [1]) independent of whether it matches or not, at one of the supported data rates, that data rate shall be held constant for 1.5 seconds. After successful reception of an address assignment frame, the secondary device shall use that data rate until it is reset.
+
+Data rates:
+
+- 9.6 kbps  $\pm$  3 %
+- 38.4 kbps  $\pm$  3 %
+- 115.2 kbps  $\pm$  3 %
+
+The format of the data octet shall be as shown in figure 4.1.1:
+
+![Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of 8 bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. This is followed by a 'Stop bit (1)' (Logical 1, Carrier Off), which returns the signal to the 'Idle' state.](a6a8016b231533e7f34b550f4676afc6_img.jpg)
+
+The figure illustrates the signal format for data transmission. The vertical axis represents the voltage difference  $V_b - V_a$ , with two levels marked: 'Logical 1 Carrier Off' (positive) and 'Logical 0 Carrier On' (negative). The horizontal axis represents 'Time'. The signal begins at the 'Idle' state (Logical 1). It then drops to the 'Logical 0' level to form a 'Startbit (0)'. Following the start bit, 8 bits of data are transmitted, starting with the 'Least significant bit' and ending with the 'Most significant bit'. After the data bits, a 'Stop bit (1)' is transmitted, returning the signal to the 'Idle' state.
+
+Figure 4.1.1: Format and order of transmitted data. The diagram shows a voltage level (Vb-Va) on the vertical axis and Time on the horizontal axis. The signal starts at an 'Idle' state (Logical 1, Carrier Off). It then transitions to a 'Startbit (0)' (Logical 0, Carrier On). This is followed by a sequence of 8 bits, with the 'Least significant bit' at the beginning and the 'Most significant bit' at the end. This is followed by a 'Stop bit (1)' (Logical 1, Carrier Off), which returns the signal to the 'Idle' state.
+
+Figure 4.1.1: Format and order of transmitted data
+
+## 4.2 RS485 option
+
+This option is constituted by a two wire bi-directional multi-drop configuration conforming to ISO/IEC 8482 [2]. The mapping of mark/space to logical one and zero as referred to in ISO/IEC 8482 [2] shall be according to figure 4.1.1.
+
+The use of ISB, also called idle-line failsafe in TIA/EIA TSB89 [3], is mandatory. The bias voltages shall be applied only by the primary device to any separate RS485 bus. The polarity of the idle-state bias is defined as a transmitted 1.
+
+The RS485 transmitter shall be set to drive the bus before the first start bit is sent and held active until the last stop bit is sent. The RS485 transmitter shall stop driving the bus within 20 bit-times after the last stop bit is sent.
+
+If an antenna modem is used ISB shall be implemented by the antenna modem.
+
+## 4.3 Modem option
+
+The connection to a RET and/or a TMA control unit by way of a coaxial cable which is shared with DC supply and RF signals is provided by two modems, a BS modem and an antenna modem. The BS modem shall be either connected to the antenna connector of the BS or integrated in the BS. It provides signal transmission to the antenna modem and signal reception from the antenna modem over the antenna feeder cable. The antenna modem is located between the antenna feeder cable and the antenna. Modem configurations and reference points for modem characteristics are specified in figure 4.3.1 and figure 4.3.2. Unless otherwise stated, requirements in this section apply to both BS modem and antenna modem.
+
+![Diagram showing modem configuration and reference points for a BS without BS modem. It includes an antenna, antenna modem, BS modem, and BS without BS modem connected by an antenna feeder cable (Iuant). Reference points 1-6 are marked at various interfaces.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The diagram illustrates the modem configuration and reference points for a BS without BS modem. It consists of three main components connected vertically: an Antenna at the top, an Antenna modem, a BS modem, and a BS without BS modem at the bottom. The Antenna is connected to the Antenna modem. The Antenna modem is connected to the BS modem via an Antenna feeder cable (Iuant). The BS modem is connected to the BS without BS modem. Reference points are marked at various interfaces: Reference point 4 is at the top of the Antenna modem; Reference point 3 is at the top of the Antenna feeder cable; Reference point 2 is at the bottom of the Antenna feeder cable; Reference point 1 (BS antenna connector) is at the top of the BS without BS modem; Reference point 5 is at the bottom of the Antenna modem; and Reference point 6 is at the bottom of the BS modem. Control data and DC power are shown entering the Antenna modem and the BS modem.
+
+Diagram showing modem configuration and reference points for a BS without BS modem. It includes an antenna, antenna modem, BS modem, and BS without BS modem connected by an antenna feeder cable (Iuant). Reference points 1-6 are marked at various interfaces.
+
+Reference point 6, DC power to the BS modem,  
+ is optional and does not exist if the BS modem  
+ has integrated power supply.
+
+**Figure 4.3.1: Modem configuration and modem reference points for a BS without BS modem**
+
+![Diagram of modem configuration and modem reference points for a BS with integrated BS modem. The diagram shows an 'Antenna modem' connected to an antenna at the top and a 'BS with integrated BS modem' at the bottom via an 'Antenna feeder cable'. Reference point 4 is at the antenna connection to the antenna modem. Reference point 3 is at the top of the antenna feeder cable. Reference point 2 (BS antenna connector) is at the bottom of the antenna feeder cable. Reference point 5 is on the side of the antenna modem, with 'Control data' and 'DC power' inputs. The current 'Iuant' is indicated on the feeder cable.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+Diagram of modem configuration and modem reference points for a BS with integrated BS modem. The diagram shows an 'Antenna modem' connected to an antenna at the top and a 'BS with integrated BS modem' at the bottom via an 'Antenna feeder cable'. Reference point 4 is at the antenna connection to the antenna modem. Reference point 3 is at the top of the antenna feeder cable. Reference point 2 (BS antenna connector) is at the bottom of the antenna feeder cable. Reference point 5 is on the side of the antenna modem, with 'Control data' and 'DC power' inputs. The current 'Iuant' is indicated on the feeder cable.
+
+**Figure 4.3.2: Modem configuration and modem reference points for a BS with integrated BS modem**
+
+### 4.3.1 Interference with existing systems
+
+The modem circuit shall be capable of managing its transmitting characteristic according to subclause 4.3.5.
+
+#### 4.3.1.1 Carrier frequency and frequency stability
+
+The following carrier frequency shall be used for this application:
+
+$2.176 \text{ MHz} \pm 100 \text{ ppm}$
+
+#### 4.3.1.2 Modem isolation and modem emissions
+
+The external BS modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 2 and reference point 1 to protect the BS from emissions of the antenna modem.
+
+External BS modem emissions at reference point 1 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect the BS from emissions of the BS modem.
+
+The antenna modem shall provide minimum attenuation according to figure 4.3.1.2.1 between reference point 3 and reference point 4 to protect other radio systems from emission of the BS modem.
+
+Antenna modem emissions at reference point 4 shall be attenuated at least according to the modem attenuation in figure 4.3.1.2.1 below the levels specified for the modem spectrum emission mask in subclause 4.3.4.2 to protect other radio systems from emission of the antenna modem.
+
+![Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis represents frequency with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis represents attenuation in dB. Key points on the graph: 10 dB flat from 9 kHz to 1 MHz; a steep rise to 21 dB and then 41 dB at 1 MHz; a peak of 42 dB at center frequency f0; a symmetrical drop on the other side with 41 dB and 21 dB markers; a flat section at 10 dB between 10 MHz and 20 MHz; and a final drop to 0 dB at 30 MHz. Horizontal double-headed arrows indicate bandwidths: 400 kHz and 1 MHz centered around f0. A 200 kHz offset is also marked from f0.](f519a5be118c846f631c992412353fb9_img.jpg)
+
+Figure 4.3.1.2.1: Modem attenuation. A graph showing attenuation in dB versus frequency. The x-axis represents frequency with markers at 9 kHz, 1 MHz, 10 MHz, 20 MHz, and 30 MHz. The y-axis represents attenuation in dB. Key points on the graph: 10 dB flat from 9 kHz to 1 MHz; a steep rise to 21 dB and then 41 dB at 1 MHz; a peak of 42 dB at center frequency f0; a symmetrical drop on the other side with 41 dB and 21 dB markers; a flat section at 10 dB between 10 MHz and 20 MHz; and a final drop to 0 dB at 30 MHz. Horizontal double-headed arrows indicate bandwidths: 400 kHz and 1 MHz centered around f0. A 200 kHz offset is also marked from f0.
+
+**Figure 4.3.1.2.1: Modem attenuation**
+
+#### 4.3.1.3 Modem intermodulation attenuation
+
+The modem intermodulation attenuation is specified in terms of the power in intermodulation products of WCDMA modulated carriers present at reference point 1 or reference point 3.
+
+For 2 downlink carriers of 43 dBm the power of third order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed:
+
+- – 130 dBm/100 kHz for frequencies  $< 1$  GHz
+- – 120 dBm/1 MHz for frequencies  $\geq 1$  GHz
+
+NOTE: Using the modem with higher power than 43 dBm and or with more carriers than 2 carriers at 43dBm/carrier may increase intermodulation products and may degrade the receiver sensitivity of the BS if these intermodulation products fall at BS receive frequencies.
+
+For the worst input configuration of power and number of carriers declared by the modem manufacturer the power of any intermodulation product for the external BS modem and antenna modem shall not exceed:
+
+- – 98dBm/100kHz
+
+In addition, for the worst input configuration of power and number of carriers declared by the modem manufacturer the power of fifth or higher order intermodulation products in the UL operating bands for the external BS modem and antenna modem shall not exceed:
+
+- – 135 dBm/100 kHz for frequencies  $< 1$  GHz
+- – 125 dBm/1 MHz for frequencies  $\geq 1$  GHz
+
+### 4.3.2 Recovery time
+
+A minimum recovery time shall be allowed between receiving and transmitting messages on the bus. For this reason a minimum permitted response time is specified in subclause 4.5 in TS 37.462 [1].
+
+### 4.3.3 Impedance
+
+The modem transceiver shall provide constant impedance in both transmitting and receiving modes:
+
+- Nominal impedance  $Z_0$ : 50  $\Omega$ ;
+- Return loss at modem carrier frequency  $\pm 0.1$  MHz  $> 10$  dB;
+- Return loss in external BS and antenna modem operating bands  $> 20$  dB.
+
+### 4.3.4 Modulator characteristics
+
+#### 4.3.4.1 Levels
+
+ON-Level:  $+3 \text{ dBm} \pm 2 \text{ dB}$
+
+OFF-Level:  $\leq -40 \text{ dBm}$
+
+#### 4.3.4.2 Spectrum emission mask
+
+The modem spectrum emission mask is specified in figure 4.3.4.2.1. Intermediate values may be obtained by linear interpolation between the points shown. The corresponding measurement bandwidths are specified in table 4.3.4.2.1. For modem configurations according to figure 4.3.1 the BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2. For modem configurations according to figure 4.3.2 the BS with integrated BS modem emissions shall not exceed the limits of the spectrum emission mask at reference point 2 only for frequencies below 20 MHz. Antenna modem emissions shall not exceed the limits of the spectrum emission mask at reference point 3.
+
+![Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis has labels at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis shows power levels: -36 dBm (below 1 MHz), -25 dBm (at 1 MHz), -5 dBm (at 200 kHz offset from f0), +5 dBm (at f0), -5 dBm (at 200 kHz offset from f0), -25 dBm (at 1 MHz), -36 dBm (at 10 MHz), and -67 dBm (at 30 MHz and above). A 1 MHz bandwidth is centered at f0. A 'Note 1' label is present at the 12.75 GHz end.](1640ec1dfae8bdfa5af950db7623febc_img.jpg)
+
+Figure 4.3.4.2.1: Modem spectrum emission mask. The graph shows power density in dBm versus frequency. The x-axis has labels at 9 kHz, 1 MHz, 10 MHz, 20 MHz, 30 MHz, 400 MHz, and 12.75 GHz. The y-axis shows power levels: -36 dBm (below 1 MHz), -25 dBm (at 1 MHz), -5 dBm (at 200 kHz offset from f0), +5 dBm (at f0), -5 dBm (at 200 kHz offset from f0), -25 dBm (at 1 MHz), -36 dBm (at 10 MHz), and -67 dBm (at 30 MHz and above). A 1 MHz bandwidth is centered at f0. A 'Note 1' label is present at the 12.75 GHz end.
+
+Figure 4.3.4.2.1: Modem spectrum emission mask.
+
+Note 1: For frequencies  $< 1 \text{ GHz}$  the general emission limit is  $-108 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is  $-135 \text{ dBm}$ .  
+For frequencies  $\geq 1 \text{ GHz}$  the general emission limit is  $-98 \text{ dBm}$ , except modem operating band UL frequencies where the emission limit is  $-125 \text{ dBm}$ .
+
+Table 4.3.4.2.1: Modem spectrum emission mask measurement bandwidth
+
+| Band              | Measurement Bandwidth |
+|-------------------|-----------------------|
+| 9 kHz - 150 kHz   | 1 kHz                 |
+| 150 kHz - 30 MHz  | 10 kHz                |
+| 30 MHz - 1 GHz    | 100 kHz               |
+| 1 GHz - 12.75 GHz | 1 MHz                 |
+
+### 4.3.5 Demodulator characteristics
+
+The demodulator shall fulfil the requirement in subclause 4.3.6 for a carrier ON-Level within  $+5 \text{ dBm}$  to  $-12 \text{ dBm}$  and a carrier OFF-Level less than  $-18 \text{ dBm}$ . The levels within  $-12 \text{ dBm}$  to  $-18 \text{ dBm}$  are undefined.
+
+### 4.3.6 Duty cycle variation
+
+In order to guarantee proper transmission of data bits through the processes of modulation and demodulation, the following limit shall be met for the duty cycle variation:
+
+$$\Delta DC_{\text{SYSTEM}} = |DC_{\text{RX}} - DC_{\text{TX}}| \leq 10 \%$$
+
+Where:  $\Delta DC_{SYSTEM}$  is the difference between the duty cycles of the transmitted and received bit streams,  
+ $DC_{TX}$  = Duty cycle for the input bit stream, and  
+ $DC_{RX}$  = Duty cycle for the output bit stream.
+
+![Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The top waveform shows a bit stream with '1' and '0' levels, a 50% duty cycle line, a bit period t_BS, and a frame period T. The bottom waveform shows an OOK modulated subcarrier with a 50% duty cycle line, an on-period t_OOK, and a frame period T.](252ea48d02dce93965b91746fb376f35_img.jpg)
+
+Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier. The top waveform shows a bit stream with '1' and '0' levels, a 50% duty cycle line, a bit period t\_BS, and a frame period T. The bottom waveform shows an OOK modulated subcarrier with a 50% duty cycle line, an on-period t\_OOK, and a frame period T.
+
+Duty cycle for bit stream =  $t_{BS}/T$ ; duty cycle for OOK =  $T_{OOK}/T$
+
+**Figure 4.3.6.1: Duty cycles of the bit stream and OOK modulated subcarrier**
+
+For transmission through a coaxial cable, two converters are required, one from a bit stream to OOK (modulator) and one from OOK back to a bit stream (demodulator). Therefore half of the total duty cycle tolerance is available for each converter.
+
+For an input bit stream with a duty ratio of 50 %, the cascaded modulator and demodulator shall provide an output bit stream with a duty ratio within the limits 40 % - 60 %, measured in each case at 0.5 times peak amplitude (see figure 4.3.6.1).
+
+### 4.3.7 Operating bands
+
+A UTRA/FDD BS, UTRA/TDD BS, E-UTRA BS, NR BS or antenna modem is designed to operate in one or several of the operating bands defined in 3GPP TS 25.101 [4], 3GPP TS 36.101 [5] and 3GPP TS 38.101 [6].
+
+**Table 4.3.7.1: Void**
+
+The operating bands of the BS modem or antenna modem shall be declared by the manufacturer.
+
+### 4.3.8 Time delay and accuracy
+
+The time delay in the operating bands shall be declared by the manufacturer with  $\pm 1$  ns accuracy. The time delay shall not exceed 30 ns. This requirement is only applicable to external BS modem and antenna modem.
+
+### 4.3.9 Insertion Loss
+
+The insertion loss in the external BS modem or antenna modem operating band shall be  $\leq 0.3$  dB.
+
+The actual insertion loss shall be declared by the manufacturer.
+
+### 4.3.10 DC port isolation
+
+The isolation between DC port and RF ports shall meet the minimum values in figure 4.3.10.1 and 4.3.10.2. Figure 4.3.10.1 is valid for antenna modems between reference point 5 and 4 as well as 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2 as well as 6 and 1. Figure 4.3.10.2 is valid as additional requirement for antenna modems between reference point 5 and 3 and for BS modems without integrated power supply between reference point 6 and 2.
+
+![Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz.](8b79f5ec940d107c246612c2a2ec519f_img.jpg)
+
+This graph shows the DC port isolation in dB across a frequency range from 9 kHz to 3 GHz. The isolation levels are defined in several segments:
+ 
+
+- From 9 kHz to 150 kHz: 10 dB
+- From 150 kHz to 1 MHz: 16 dB
+- From 1 MHz to 30 MHz: 16 dB (Note 3 applies here)
+- From 30 MHz to 400 MHz: 21 dB
+- From 400 MHz to 1 GHz: 21 dB (Note 1 applies here)
+- From 1 GHz to 2.57 GHz: 21 dB (Note 2 applies here)
+- From 2.57 GHz to 3 GHz: 20 dB
+
+Figure 4.3.10.1: DC port isolation graph showing isolation levels across a wide frequency range from 9 kHz to 3 GHz.
+
+Note 1: 38 dB, except for UL and DL operating bands where it is 65 dB
+
+Note 2: 38 dB, except for UL and DL operating bands where it is 65 dB
+
+Note 3: 16 dB. Between reference point 5 and 3 as well as 6 and 2 see figure 4.3.10.2.
+
+Figure 4.3.10.1: DC port isolation
+
+![Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around a specific frequency f0.](3084f66c81a49b6225666f212179642c_img.jpg)
+
+This graph provides a detailed view of the DC port isolation around a specific frequency  $f_0$ . The isolation levels are:
+ 
+
+- Below 1 MHz: 16 dB
+- At 1 MHz, the isolation begins to rise.
+- At a distance of 200 kHz from  $f_0$ , the isolation is 35 dB.
+- At a distance of 400 kHz from  $f_0$ , the isolation is 36 dB.
+- At the center frequency  $f_0$ , the isolation is 36 dB.
+- At a distance of 400 kHz from  $f_0$  on the other side, the isolation is 36 dB.
+- At a distance of 200 kHz from  $f_0$  on the other side, the isolation is 35 dB.
+- Above 1 MHz (specifically from 1 MHz to 10 MHz), the isolation is 16 dB.
+- From 10 MHz to 20 MHz: 16 dB
+- From 20 MHz to 30 MHz: 16 dB
+
+Figure 4.3.10.2: DC port isolation graph showing a detailed view of the isolation around a specific frequency f0.
+
+Figure 4.3.10.2: DC port isolation
+
+### 4.3.11 RET control unit spurious emission
+
+Void.
+
+### 4.3.12 Control unit spurious emission
+
+The control unit, or a combination of control units, shall not generate spurious emission, at reference point 5, above a level that will violate the spectrum emission mask requirement according to chapter 4.3.4.2. The DC port isolation according to chapter 4.3.10 shall be taken into account.
+
+## 4.4 DC power supply
+
+### 4.4.1 Power consumption
+
+The DC supply requirements refers to reference points 3 and 5 in subclause 4.3.
+
+BS modem and an antenna modem shall be able to operate with a DC supply voltage range of 10 V – 30 V.
+
+Power consumption modes are specified in table 4.4.1.1. and table 4.4.1.2.
+
+**Table 4.4.1.1: Power consumption modes for RET**
+
+| RET Power mode | Maximum power consumption |
+|----------------|---------------------------|
+| High           | < 13 W                    |
+| Low            | < 2 W                     |
+
+**Table 4.4.1.2: Power consumption modes for TMA**
+
+| TMA Type       | Maximum power consumption |
+|----------------|---------------------------|
+| Single Unit    | < 7,5 W                   |
+| Multi Unit (N) | < N * 7,5 W               |
+
+BS modem and antenna modem maximum power consumption shall be < 2 W.
+
+BS modem and antenna modem shall impose a voltage drop less than 2 V between reference point 3 and 5.
+
+A Single Unit considers one RF amplifier in one TMA. A Multi Unit considers N RF amplifiers in equal or less than N TMAs.
+
+### 4.4.2 Conducted emission
+
+The levels of generated conducted noise and ripple on DC Power supply shall be within the limits given in table 4.4.2.1.
+
+**Table 4.4.2.1: Noise and ripple**
+
+| Item                   | Limit               | Frequency     | Remarks                                                   |
+|------------------------|---------------------|---------------|-----------------------------------------------------------|
+| RET power mode High    | 70 mV <sub>pp</sub> | 0.15 - 30 MHz | Only one operating unit a time                            |
+| RET power mode Low     | 20 mV <sub>pp</sub> | 0.15 - 30 MHz |                                                           |
+| TMA                    | 20 mV <sub>pp</sub> | 0.15 - 30 MHz |                                                           |
+| Antenna modem, RF port | 15 mV <sub>pp</sub> | 0.15 - 30 MHz | Generated Noise and Ripple at RF feeder (in RX mode)      |
+| Antenna modem, DC port | 20 mV <sub>pp</sub> | 0.15 - 30 MHz | Allowed Noise and Ripple at external DC port (in TX mode) |
+
+All units connected to a DC supply bus shall exhibit full performance up to the limit of 112 mV<sub>pp</sub> total noise and ripple within 0.15 - 30 MHz.
+
+### 4.4.3 Power-up characteristics
+
+A BS modem, antenna modem or RET/TMA control units shall have a power-up period of 3 s.
+
+During the power-up period a BS modem, antenna modem or a RET control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 400 mA in parallel with a capacitor of maximum 0.5 µF.
+
+During the power-up period the TMA control unit shall exhibit the circuit equivalent of a DC power consumer with a current consumption of maximum 1A in parallel with a capacitor of maximum 0.5 µF.
+
+After the power-up period, the unit shall be fully functional and the power consumption requirement as described in subclause 4.4.1 applies.
+
+# --- Annex A (normative): Test procedures
+
+## Test pattern
+
+Spectrum mask and emission requirement shall be tested both with a consecutive series of "0" and an alternating sequence of "0" and "1".
+
+## Emission requirement below noise floor
+
+As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy and sensitivity when measuring close to or below the noise floor, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth.
+
+## Conversion between modulated and CW for IM measurement
+
+The requirement for IM3 below 1 GHz shall be relaxed 15 dB and tested with CW interferers at the specified levels.  
+The requirement for IM3 above 1 GHz shall be relaxed 5 dB and tested with CW interferers at the specified levels.
+
+The requirement for IM5 or higher below 1 GHz shall be relaxed 10 dB and tested with CW interferers at the specified levels.
+
+The requirement for IM5 or higher above 1 GHz shall be relaxed 0 dB and tested with CW interferers at the specified levels.
+
+Example: A –130 dBm/100 kHz requirement below 1 GHz with two WCDMA-modulated carriers at 43 dBm is converted to a –115 dBm requirement with two CW carriers at 43 dBm.
+
+# Annex B (informative): Change history
+
+| Change history |          |           |      |     |     |                                                                     |             |
+|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103   | R3-190087 |      |     |     | Text transferred from 25.461 v15.3.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83   | RP-190590 |      |     |     | Specification approved by RAN plenary                               | 15.4.0      |
+| 2020-07        | RAN#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
+| 2022-06        | RAN#96   | RP-221155 | 0002 | 1   | A   | CR on clarification scope on luant modem                            | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37462/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg b/marked/Rel-16/37_series/37462/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..24ab4263493d395049e1568181895f4c832ccdcc
--- /dev/null
+++ b/marked/Rel-16/37_series/37462/78d5774278a3f4a614f8c0ae485ce8d9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc64f15a1781c823d6a025b4f19b18c8570f0c673228c545800fc141600e422b
+size 39253
diff --git a/marked/Rel-16/37_series/37462/raw.md b/marked/Rel-16/37_series/37462/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4da63e10f1378248cb8b0292340449641fe6925b
--- /dev/null
+++ b/marked/Rel-16/37_series/37462/raw.md
@@ -0,0 +1,658 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                        |           |
+|------------------------------------------------------------------------|-----------|
+| Foreword .....                                                         | 4         |
+| 1 Scope.....                                                           | 5         |
+| 2 References.....                                                      | 5         |
+| 3 Definitions and abbreviations .....                                  | 5         |
+| 3.1 Definitions.....                                                   | 5         |
+| 3.2 Abbreviations .....                                                | 6         |
+| 4 Iuant data link layer.....                                           | 6         |
+| 4.1 Invalid receptions .....                                           | 6         |
+| 4.2 Frame lengths .....                                                | 6         |
+| 4.3 Default address.....                                               | 7         |
+| 4.4 Window size.....                                                   | 7         |
+| 4.5 Message timing .....                                               | 7         |
+| 4.6 State model.....                                                   | 7         |
+| 4.7 Device types .....                                                 | 7         |
+| 4.8 XID negotiation.....                                               | 8         |
+| 4.8.1 HDLC parameters.....                                             | 8         |
+| 4.8.2 Protocol version .....                                           | 8         |
+| 4.8.3 Address assignment.....                                          | 8         |
+| 4.8.4 Device scan.....                                                 | 9         |
+| 4.8.5 Reset device.....                                                | 9         |
+| 4.9 Link establishment .....                                           | 10        |
+| 4.10 Link timeout .....                                                | 10        |
+| <b>Annex A (informative): HDLC description .....</b>                   | <b>11</b> |
+| A.1 Basic structure .....                                              | 11        |
+| A.2 UNC commands.....                                                  | 12        |
+| A.2.1 Set Normal Response Mode (SNRM) .....                            | 12        |
+| A.2.2 Disconnect (DISC) .....                                          | 12        |
+| A.2.3 Unnumbered Acknowledge (UA).....                                 | 12        |
+| A.2.4 Disconnected Mode (DM).....                                      | 12        |
+| A.2.5 Receiver Ready (RR).....                                         | 12        |
+| A.2.6 Receiver Not Ready (RNR).....                                    | 12        |
+| A.2.7 Information (I) .....                                            | 12        |
+| A.2.8 Frame Reject (FRMR).....                                         | 12        |
+| A.3 Option 1.....                                                      | 13        |
+| A.4 Option 4.....                                                      | 13        |
+| A.5 Option 15.1.....                                                   | 13        |
+| A.6 Link safety.....                                                   | 13        |
+| A.7 Full duplex link .....                                             | 13        |
+| <b>Annex B (informative): HDLC parameter negotiation .....</b>         | <b>15</b> |
+| <b>Annex C (informative): HDLC parameter negotiation example .....</b> | <b>16</b> |
+| <b>Annex D (informative): Address assignment example.....</b>          | <b>17</b> |
+| D.1 Address assignment command .....                                   | 17        |
+| D.2 Address assignment response .....                                  | 17        |
+| <b>Annex E (informative): Device scan example .....</b>                | <b>18</b> |
+| Annex F (informative): Change History .....                            | 20        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the signalling transport related to RETAP and TMAAP signalling to be used across the Iuant interface for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas and between the implementation specific O&M function and the TMA control unit function.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void
+- [2] ISO/IEC 13239 (3rd Edition, 2002-07): "Information Technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures".
+- [3] 3GPP TS 37.461: "Iuant Interface: Layer 1".
+- [4] Antenna Interface Standards Group: "Control Interface for Antenna Line Devices", Standard No. AISG v2.0
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**ASCII character:** A character forming part of the International Reference Version of the 7-bit character set defined in ISO/IEC 646:1991 represented as one octet
+
+**Octet:** 8 bits as used in ISO/IEC 13239 [2]
+
+**Device type:** One octet identifying the type of a device
+
+**Unique ID:** A concatenation of the vendor code (2 octets) and a 1 to 17 octets long unit specific code (e.g. serial number) exclusive for each secondary device from the vendor to whom the vendor code is assigned. The vendor code is placed in the left-most (most significant) position of the unique ID. The vendor to whom the vendor code is assigned is responsible for ensuring the uniqueness of the unique ID for each device.
+
+**Vendor code:** A unique ASCII 2-character code assigned to each vendor in AISG v2.0 [4].
+
+**Reset:** A process by which the device is put in the state it reaches after a completed power-up
+
+**SecondaryPayloadTransmitLength:** The maximum length of the INFO field of an HDLC I-frame in the direction secondary device to primary device.
+
+**SecondaryPayloadReceiveLength:** The maximum length of the INFO field of an HDLC I-frame in the direction primary device to secondary device.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                 |
+|-------|-------------------------------------------------|
+| ADDR  | Address                                         |
+| ACK   | Acknowledgment                                  |
+| CRC   | Cyclic Redundancy Check                         |
+| DISC  | Disconnect (frame type)                         |
+| DM    | Disconnected Mode (frame type)                  |
+| FCS   | Frame Checking Sequence                         |
+| FI    | Format Identifier                               |
+| FRMR  | Frame Reject (frame type)                       |
+| GI    | Group Identifier                                |
+| GL    | Group Length                                    |
+| HDLC  | High-Level Data Link Control                    |
+| I     | Information (frame type)                        |
+| ID    | Identifier                                      |
+| INFO  | Information (field name)                        |
+| NAK   | Non Acknowledgment                              |
+| NRM   | Normal Response Mode                            |
+| P/F   | Poll/Final                                      |
+| PI    | Parameter Identifier                            |
+| PL    | Parameter Length                                |
+| PV    | Parameter Value                                 |
+| RET   | Remote Electrical Tilting                       |
+| RETAP | Remote Electrical Tilting Application Part      |
+| RNR   | Receive Not Ready (frame type)                  |
+| RR    | Receive Ready (frame type)                      |
+| SNRM  | Set Normal Response Mode (frame type)           |
+| TMA   | Tower Mounted Amplifier                         |
+| TMAAP | Tower Mounted Amplifier Application Part        |
+| TWA   | Two Way Alternate                               |
+| UA    | Unnumbered Acknowledgement (frame type)         |
+| UNC   | Unbalanced Operation Normal Response Mode Class |
+| XID   | Exchange ID (frame type)                        |
+
+# --- 4 Iuant data link layer
+
+The Data Link Layer uses HDLC Class UNC1,15.1 TWA (see 6.10 in ISO/IEC 13239 [2]) according to ISO/IEC 13239 [2].
+
+## 4.1 Invalid receptions
+
+Frames shall be discarded if a framing error or data overrun occurs.
+
+## 4.2 Frame lengths
+
+HDLC frame lengths may vary between 4 and N octets.
+
+All secondary devices shall support an N of 78 octets. A secondary device may, after XID negotiation, support a larger N.
+
+## 4.3 Default address
+
+After reset, a secondary device shall use the no-device address (0x00). While it has the no-device address, it may only respond to device scan and address assignment messages, but any broadcast messages shall be evaluated without response.
+
+## 4.4 Window size
+
+All devices shall support a window size of 1. A device may, after XID negotiation, support any window size up to 7.
+
+## 4.5 Message timing
+
+A minimum of 3 ms shall elapse between receiving and transmitting messages.
+
+A secondary device shall, after reception of a command with the P/F bit set, start transmitting a response within 10 ms from the time the final flag octet of that command frame was received.
+
+The transmission of the response shall be finalised within the time  $t = n \cdot 10^4 / \text{datarate}$  where  $n$  is the number of octets in the response frame including all HDLC framing overhead. The maximum gap time between two consecutive octets shall not exceed the time  $t = 3 \cdot 10^4 / \text{datarate}$ . This corresponds to a 25% utilisation of the Data Link Layer.
+
+The data rate is specified in TS 37.461 [3].
+
+## 4.6 State model
+
+The connection state model for the layer 2 of the secondary device is shown in figure 4.1. The events written in *italic* are procedures from higher levels e.g. link establishment. The HDLC frames that correspond to the events are written in bold as **command / response** messages.
+
+![Figure 4.6.1: Connection state model. A state transition diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and result in HDLC frames (bold).](78d5774278a3f4a614f8c0ae485ce8d9_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> NoAddress : Reset (reset, power on, watchdog etc.)
+    NoAddress --> NoAddress : Link Timeout
+    NoAddress --> AddressAssigned : Address Configuration  
+XID/XID
+    AddressAssigned --> Connected : Link Establishment  
+SNRM/UA
+    Connected --> NoAddress : Link Disconnection  
+DISC/UA
+
+```
+
+Figure 4.6.1: Connection state model. A state transition diagram showing three states: NoAddress, AddressAssigned, and Connected. Transitions are triggered by events (italic) and result in HDLC frames (bold).
+
+Figure 4.6.1: Connection state model
+
+## 4.7 Device types
+
+Three device types are defined and identified by the assigned 1-octet unsigned integer code.
+
+Table 4.7.1: Device types and codes
+
+| Device Type                   | 1-octet unsigned integer code |
+|-------------------------------|-------------------------------|
+| Single-Antenna RET Device     | 0x01                          |
+| Multi-Antenna RET Device      | 0x11                          |
+| Tower mounted amplifier (TMA) | 0x02                          |
+
+## 4.8 XID negotiation
+
+XID negotiation shall use the standard format (see 5.5.3.1-5.5.3.2.3.2 in ISO/IEC 13239 [2]). See Annex B for a brief description of XID negotiation and Annex C to E for examples of XID negotiations. All GL fields have a size of 1 octet.
+
+Any parameter combination of 4.8.1 (HDLC parameter), 4.8.2 (Protocol Version) and 4.8.3 (Address assignment) in an XID command shall be supported by all secondary devices.
+
+### 4.8.1 HDLC parameters
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0x80. All secondary devices shall support the following parameters:
+
+**Table 4.8.1.1: HDLC parameters for secondary devices**
+
+| PI | PL | Description of PV                                  |
+|----|----|----------------------------------------------------|
+| 5  | 4  | Maximum information field length – transmit (bits) |
+| 6  | 4  | Maximum information field length – receive (bits)  |
+| 7  | 1  | Window size – transmit (frames)                    |
+| 8  | 1  | Window size – receive (frames)                     |
+
+The SecondaryPayloadTransmitLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger.
+
+The SecondaryPayloadReceiveLength shall be 74 octets by default. It can be increased via XID negotiation, but shall always be 74 octets or larger.
+
+### 4.8.2 Protocol version
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter:
+
+**Table 4.8.2.1: HDLC parameter for protocol version**
+
+| PI | PL | Description of PV |
+|----|----|-------------------|
+| 5  | 1  | 3GPP Release ID   |
+
+### 4.8.3 Address assignment
+
+The primary device broadcasts the XID commands. The secondary device(s) which match shall respond. The primary shall ensure that only one secondary matches the supplied parameter(s). See below for details.
+
+Format Identifier (FI) shall be 0x81 and Group Identifier (GI) shall be 0xF0. All secondary devices shall support the following parameters:
+
+**Table 4.8.3.1: HDLC parameters for address assignment and device scan**
+
+| PI | PL      | Description of PV                                 |
+|----|---------|---------------------------------------------------|
+| 1  | 0 to 19 | Unique ID                                         |
+| 2  | 1       | HDLC Address                                      |
+| 3  | 0 to 19 | Bit Mask (for Unique ID), indicates a device scan |
+| 4  | 1       | Device Type (see table 4.7.1)                     |
+| 6  | 2       | Vendor Code as given in AISG v2.0 [4]             |
+
+The XID message can be used to assign HDLC addresses or to scan for devices.
+
+An address assignment XID command shall contain at least PI=2 (HDLC Address) and shall not contain PI=3 (Bit Mask). During an address assignment all secondary devices first assume a match and then carry out the following steps:
+
+- If PI=1 (Unique ID) is supplied, the right-most PL octets of the secondary devices Unique ID are compared to the Unique ID in the XID command. If they are different, the secondary device does not match, and the message is ignored. If the Unique ID in the XID command is longer than the secondary devices Unique ID, the secondary device does not match, and the message is ignored.
+- If PI=4 (Device Type) is supplied, the device type of the secondary device is compared to the device type in the XID command. If they are different, the secondary device does not match, and the message is ignored.
+- If PI=6 (Vendor Code) is supplied, the vendor code of the secondary device is compared to the vendor code in the XID command. If they are different, the secondary device does not match, and the message is ignored.
+
+If the secondary device still matches after these steps, the secondary device sets its HDLC address to the address specified in PI=2 and responds with an XID response which contains PI=1 and PI=4.
+
+NOTE: Unlike the normal XID negotiation, in this XID negotiation, the XID response message returns a different set of parameters than the XID command message.
+
+### 4.8.4 Device scan
+
+The device scan messages may be utilised by the primary to identify all secondary stations in the NoAddress state on an interface .
+
+A device scan XID command shall only contain PI=1 (Unique ID) and PI=3 (Bit Mask), see table 4.8.3.1. PI=1 and PI=3 shall be of equal length PL octets.
+
+If in the NoAddress state, the secondary device masks the  $\min(PL,2)$  left-most octets of its own unique ID with the  $\min(PL,2)$  left-most octets of the bit mask in the XID command and compares the result with the  $\min(PL,2)$  left-most octets the unique ID supplied in the XID command. If they match, the secondary device masks the  $\max(0,PL-2)$  right-most octets of its own unique ID with the  $\max(0,PL-2)$  right-most octets of the bit mask in the XID command and compares the result with the  $\max(0,PL-2)$  right-most octets of the unique ID supplied in the XID command. If they also match, the secondary device transmits an XID response message with its own identification data in the fields PI=1 (complete unique ID), PI=4 (device type) and PI=6 (vendor code).
+
+For the device scan comparison, the unique ID of the secondary device shall be padded with NUL characters (character code 0x00) between the second and third left-most positions to a length of 19 octets.
+
+The scan command with zero length ( $PL=0$ ) of the Unique ID (PI=1) and the Bit Mask (PI=3) shall match all secondary devices in the NoAddress state.
+
+Only matching secondary devices in the NoAddress state shall respond to the device scan messages.
+
+### 4.8.5 Reset device
+
+Format identifier (FI) shall be 0x81 and group identifier (GI) shall be 0xF0. All secondary devices shall support the following parameter:
+
+**Table 4.8.5.1: HDLC parameters for reset of secondary devices**
+
+| PI | PL | Description of PV |
+|----|----|-------------------|
+| 7  | 0  | Reset device      |
+
+If the XID command reset device is received as a broadcast (0xFF) by the secondary device, the secondary device shall reset without responding, otherwise the addressed secondary device shall reset after responding.
+
+The reset device parameter shall not be combined with other parameters in an XID command.
+
+NOTE: There is no PV in the XID command Reset device.
+
+## 4.9 Link establishment
+
+Once the secondary device has been assigned an HDLC address, the primary device initiates the link establishment by sending the SNRM command frame. The secondary device responds with an UA frame and enters the state *Connected*.
+
+## 4.10 Link timeout
+
+Whenever a secondary device receives an HDLC frame addressed to itself, i.e. not an all-device address (0xFF), it shall restart a 3 minute timer. If this 3 minute timer expires, the secondary device shall be reset.
+
+# Annex A (informative): HDLC description
+
+HDLC is defined in ISO/IEC 13239 [2]. This description only covers the aspects of HDLC which are used by this TS.
+
+The HDLC definition “UNC1,15.1, TWA” can be broken down to:
+
+- UNC;
+  - The “U” means Unbalanced operation (master slave operation);
+  - The “N” means Normal response mode (sequence numbers used in data frames);
+  - The “C” means Class.
+- Options supported;
+  - “1” means use of XID negotiation;
+  - “15.1” means use of start/stop transmission with basic transparency;
+  - Two Way Alternate (TWA) is the HDLC term for half duplex.
+
+## A.1 Basic structure
+
+In unbalanced operation, there is one primary station (master) which controls the bus and a number of secondary stations (slaves) which only are allowed to transmit when the primary station gives them permission to do so.
+
+All messages are transmitted as frames with the layout shown in table A.1.1:
+
+**Table A.1.1: Format of an HDLC frame**
+
+| Flag<br>1 octet | ADDR<br>1 octet           | Control<br>1 octet | INFO<br>N octets | FCS<br>2 octets | Flag<br>1 octet |
+|-----------------|---------------------------|--------------------|------------------|-----------------|-----------------|
+| 0x7E            | Secondary Station Address | Control bits       | Variable length  | CRC             | 0x7E            |
+
+HDLC frames begin and end with a Flag (0x7E) (see A.5 for details).
+
+The transmitting station calculates a Frame Check Sequence (CRC16) on all octets which follow the starting flag but not including the FCS octets. The checksum is transmitted as FCS in little endian order and is followed by the closing flag.
+
+The receiving station calculates the checksum on all octets between the flags. When it finds the closing flag, it compares the checksum to 0xF0B8. If it is a match, the HDLC frame is processed.
+
+The address field contains the HDLC address of the secondary station. If the primary station sends the message, it is called a command and the address field contains the address of the secondary station as destination. If the secondary station sends the message, it is called a response and the address field contains the address of the secondary station as source. Secondary stations cannot communicate directly to each other.
+
+The control field defines one of three frame types:
+
+- I frames contain data as well as a send and receive counter;
+- S frames contain a receive counter;
+- U frames contain unnumbered commands.
+
+The INFO field is only present in I frames and XID frames. The INFO field in an I frame contains the layer 7 payload.
+
+## A.2 UNC commands
+
+According to 6.6.2.1 in ISO/IEC 13239 [2] the following commands in shall be supported in UNC mode:
+
+**Table A.2.1: Commands supported in UNC mode**
+
+| Commands<br>(Primary Station) | Responses<br>(Secondary Station) |
+|-------------------------------|----------------------------------|
+| Frame type I                  | Frame type I                     |
+| Frame type RR                 | Frame type RR                    |
+| Frame type RNR                | Frame type RNR                   |
+| Frame type SNRM               | Frame type UA                    |
+| Frame type DISC               | Frame type DM                    |
+|                               | Frame type FRMR                  |
+
+### A.2.1 Set Normal Response Mode (SNRM)
+
+This command is used to set the secondary station in connected mode and reset its sequence number variables.
+
+### A.2.2 Disconnect (DISC)
+
+This command is used to terminate the connection.
+
+### A.2.3 Unnumbered Acknowledge (UA)
+
+This response is used to confirm that the secondary station received and acted on an SNRM or DISC command.
+
+### A.2.4 Disconnected Mode (DM)
+
+This response is used to inform the primary station that the secondary station is disconnected.
+
+### A.2.5 Receiver Ready (RR)
+
+This command and response is used to inform the opposite station (primary or secondary) that the transmitting station has empty buffers, i.e. is ready to receive an I frame. This aspect is used for flow control.
+
+It also contains the sequence number of the next frame the transmitting station expects to see. This works both as an ACK and a NAK depending on the value.
+
+### A.2.6 Receiver Not Ready (RNR)
+
+Just like RR, except it informs the opposite station that the transmitting station does not have empty buffers, i.e. that it is not ready to receive an I frame. This aspect is used for flow control.
+
+### A.2.7 Information (I)
+
+This command and response is used to transfer a block of data together with its sequence number. The command also includes the sequence number of the next frame the transmitting station expects to see. This way, it works as an RR. Like RR, it enables transmission of I frames from the opposite side.
+
+### A.2.8 Frame Reject (FRMR)
+
+This response is used to indicate an error condition. The two most likely error conditions are:
+
+- Invalid command;
+- Sequence number problem.
+
+The latter is used when the primary station has requested retransmission of a sequence number which it has already acknowledged.
+
+## A.3 Option 1
+
+Option 1 means the addition of the XID command/response, which is used for parameter negotiation.
+
+## A.4 Option 4
+
+Option 4 means the addition of the UI command/response, which is used to transfer information without changing the sequence numbers used by I frames.
+
+## A.5 Option 15.1
+
+Option 15.1 means that the serial link is not synchronous and start/stop flags are used (asynchronous serial link). The flags are coded as 0x7E and basic transparency is used.
+
+This means that all octets between the flags are part of the frame and shall not be transmitted as 0x7E. Since the frame may contain 0x7E, basic transparency is used, which means that 0x7E is transmitted as 0x7D 0x5E and 0x7D is transmitted as 0x7D 0x5D. The receiving station converts back on reception.
+
+All checksum calculations are done on unconverted data.
+
+## A.6 Link safety
+
+HDLC provides the upper layer with a safe link between two stations.
+
+Unless excessive frame lengths are used, the CRC16 checksum provides excellent protection against transmission errors. At worst,  $10^{-5}$  of the bit errors will not be detected. The likelihood of an undetected error in a frame can be calculated by multiplying  $10^{-5}$  with the Bit Error Rate (at least  $10^{-9}$  for a reasonable link) and the frame length.
+
+The sequence numbers provide protection against:
+
+- Message duplication;
+- Message deletion;
+- Message re-ordering.
+
+Without sequence numbers, the protection is only given by a checksum and some sort of ACK.
+
+If the original message is lost, there will be no ACK and a timeout will cause retransmission which solves the problem.
+
+If the original message is not lost, but the ACK is lost, the same timeout will cause a retransmission.
+
+With sequence numbers, the message is retransmitted, but the receiving station sees that the sequence number is the same, i.e. that the message is a retransmission, and throws it away without processing it further. It does send an ACK which informs the transmitting station that the message got through.
+
+## A.7 Full duplex link
+
+The upper layer sees the HDLC link as a full duplex link, although the actual transmissions on layer 1 are half duplex. The reason for this is that the upper layer is not aware of any restrictions on transmissions or receptions between layer 2 and layer 1 or between the stations.
+
+Whenever the upper layer wants to transmit, it places a message on the queue to layer 2. The message will not be transmitted until the primary station does a poll.
+
+NOTE: This applies to both the primary and the secondary station.
+
+The same applies to reception. The upper layer will either be told by layer 2 when a message has arrived, or it will periodically check to see if a message has arrived at layer 2. Neither of these two methods will in any way influence the reception of a message. That only depends on when the primary does a poll.
+
+NOTE This still applies to both the primary and the secondary station.
+
+A poll is a command frame from the primary station where the P/F (Poll/Final) bit in the control field is set to 1. This informs the secondary that it is allowed to transmit response frames.
+
+U frames set the P/F bit, which means that they are polls. However, since the U frames used in UNC 1,4 require a specific U frame response, they are not used for I frame transmission, which is what the upper layer messages depend upon.
+
+An I, RR or RNR frame type with the P/F bit set constitutes a poll as used above. An RNR frame prevents transmission of I frames, so it does not really apply.
+
+NOTE: Whenever an I or RR poll occurs, the secondary station may transmit whatever I frame it wishes (as long as the window size is not exceeded, i.e. previous messages have been acknowledged). This means that the secondary station does not have to transmit a reply to a layer 7 instruction. It is free to transmit an alarm instruction, if an alarm has occurred. It is also free to transmit any valid reply to an earlier layer 7 instruction, if it has received (acknowledged) more than one.
+
+# Annex B (informative): HDLC parameter negotiation
+
+See also sections 5.5.3.1 – 5.5.3.2.3.2 in ISO/IEC 13239 [2].
+
+**Table B.1: Format of XID parameters**
+
+|           |           |           |           |           |           |           |           |           |
+|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|
+| <b>FI</b> | <b>GI</b> | <b>GL</b> | <b>PI</b> | <b>PL</b> | <b>PV</b> | <b>PI</b> | <b>PL</b> | <b>PV</b> |
+|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|
+
+XID parameter negotiation uses a specific format (see table C.1) to transfer parameters.
+
+The parameters are identified by a one octet Format Identifier (FI) code and a one octet Group Identifier (GI) code. The Group Length (GL) is a one octet unsigned integer giving the length in octets of the parameters following it.
+
+The parameters are a sequence of PI/PL/PV values. The Parameter Identifier (PI) is a one octet code identifying the parameter. Parameter Length (PL) is a one octet unsigned integer giving the length in octets of the Parameter Value. The parameter order is not defined.
+
+The HDLC parameter negotiation is initiated by the primary station. The primary station transmits an XID frame with the values it suggests. The secondary station can either accept these or lower them. Regardless, it responds with an XID frame with the appropriate values.
+
+Generally this means that the primary station initially uses whatever its maximum limit is for each parameter. If the secondary can accept this, it responds with the same values. If it cannot support that, it lowers the values.
+
+Maximum information field length is a good example. If the primary station suggests using an information field length of 28000 bits (3500 octets), the secondary station can respond with 28000 bits, if it can use that much or even more, or respond with a lower number of e.g. 592 bits (74 octets) if that is its maximum supported information field length.
+
+The same applies to the Release ID. If a release 7 primary station attempts to communicate with a release 6 secondary station, the initial message will suggest release 7 and the response will be release 6.
+
+On the other hand, if a release 6 primary station attempts to communicate with a release 7 secondary station, the initial message will suggest release 6 and the response will release 6.
+
+Regardless, the primary station will have the final decision, since it can refuse to communicate with a station that does not support whatever parameter values it suggests. It can always repeat the XID negotiation with a new value.
+
+# Annex C (informative): HDLC parameter negotiation example
+
+XID Frame from primary station:
+
+**Table C.1: XID frame from primary station**
+
+| Field | Content | Description                                  |
+|-------|---------|----------------------------------------------|
+| ADDR  | 12      | Station address                              |
+| CTRL  | XID     | Command                                      |
+| FI    | 0x81    | Format identifier                            |
+| GI    | 0x80    | HDLC Parameter set                           |
+| GL    | 18      | Length of the parameter field (PI) in octets |
+| PI    | 5       | Maximum I Field length Transmit              |
+| PL    | 4       | Length of the PV field in octets             |
+| PV    | 341040  | Maximum I Field length Transmit in bits      |
+| PI    | 6       | Maximum I Field length Receive               |
+| PL    | 4       | Length of the PV field in octets             |
+| PV    | 224000  | Maximum I Field length Receive in bits       |
+| PI    | 7       | Maximum window size Transmit                 |
+| PL    | 1       | Length of the PV field in octets             |
+| PV    | 7       | Maximum window size Transmit                 |
+| PI    | 8       | Maximum window size Receive                  |
+| PL    | 1       | Length of the PV field in octets             |
+| PV    | 3       | Maximum window size Receive                  |
+
+Response from secondary station:
+
+**Table C.2: XID frame from secondary station**
+
+| Field | Content | Description                             |
+|-------|---------|-----------------------------------------|
+| ADDR  | 12      | Station address                         |
+| CTRL  | XID     | Command                                 |
+| FI    | 0x81    | Format identifier                       |
+| GI    | 0x80    | HDLC Parameters set                     |
+| GL    | 16      | Length of the parameter field in octets |
+| PI    | 5       | Maximum I field length Transmit         |
+| PL    | 2       | Length of the PV field (octets)         |
+| PV    | 3200    | Maximum I field length Transmit in bits |
+| PI    | 6       | Maximum I field length Receive          |
+| PL    | 4       | Length of the PV field (octets)         |
+| PV    | 341040  | Maximum I field length Receive in bits  |
+| PI    | 7       | Maximum window size Transmit            |
+| PL    | 1       | Length of the PV field (octets)         |
+| PV    | 3       | Maximum window size Transmit            |
+| PI    | 8       | Maximum window size Receive             |
+| PL    | 1       | Length of the PV field (octets)         |
+| PV    | 1       | Maximum window size Receive             |
+
+# Annex D (informative): Address assignment example
+
+## D.1 Address assignment command
+
+**Table D.1: Format of the XID frame originated by the primary station**
+
+| Field | Content                               | Description                                                                                           |
+|-------|---------------------------------------|-------------------------------------------------------------------------------------------------------|
+| ADDR  | 0xFF                                  | All-station address (Broadcast)                                                                       |
+| CTRL  | 0xBF                                  | XID command                                                                                           |
+| FI    | 0x81                                  | Format identifier                                                                                     |
+| GI    | 0xF0                                  | User defined parameter set                                                                            |
+| GL    | 0x10                                  | Length of the parameter field (rest of the message) in octets                                         |
+| PI    | 0x01                                  | Unique ID                                                                                             |
+| PL    | 0x07                                  | Length of PV field in octets                                                                          |
+| PV    | 0x58 0x59 0x7B 0x20<br>0x41 0x42 0x43 | Unique ID of the secondary station                                                                    |
+| PI    | 0x02                                  | HDLC address                                                                                          |
+| PL    | 0x01                                  | Length of PV field in octets                                                                          |
+| PV    | 0x17                                  | Assigned HDLC address                                                                                 |
+| PI    | 0x06                                  | Vendor code as given in AISG v2.0 [4]                                                                 |
+| PL    | 0x02                                  | Length of PV field in octets                                                                          |
+| PV    | 0x58 0x59                             | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" used in this example) |
+
+## D.2 Address assignment response
+
+**Table D.2: Format of Address Assignment Response by the secondary station**
+
+| Field | Content                                  | Description                                                |
+|-------|------------------------------------------|------------------------------------------------------------|
+| ADDR  | 0x17                                     | HDLC address of the station                                |
+| CTRL  | 0xBF                                     | XID command                                                |
+| FI    | 0x81                                     | Format identifier                                          |
+| GI    | 0xF0                                     | User defined parameter set                                 |
+| GL    | 0x0C                                     | Length of parameter field (rest of the message) in octets. |
+| PI    | 0x01                                     | Unique ID                                                  |
+| PL    | 0x07                                     | Length of PV field in octets                               |
+| PV    | 0x58 0x59 0x7B<br>0x20 0x41 0x42<br>0x43 | Unique ID of the secondary station                         |
+| PI    | 0x04                                     | Device type                                                |
+| PL    | 0x01                                     | Length of PV field in octets                               |
+| PV    | 0x01                                     | Device type as defined in table 4.7.1                      |
+
+NOTE: In this address assignment example messages the virtual vendor code "XY", the unique ID 0x58 0x59 0x7B 0x20 0x41 0x42 0x43, the HDLC address 0x17 and the device type 0x01 for a single-antenna device are used.
+
+# Annex E (informative): Device scan example
+
+In some situations it may be found that the Unique ID of a bus device is unknown or has been inaccurately recorded. This HDLC command exchange is used by the primary station to perform a binary tree scan of the bus, in order to identify all connected and disconnected devices.
+
+Table E.1: Primary device scan command (XID Frame)
+
+| Field | Content        | Description                                                                                                 |
+|-------|----------------|-------------------------------------------------------------------------------------------------------------|
+| ADDR  | 0xFF           | All-station address (Broadcast)                                                                             |
+| CTRL  | 0xBF           | XID command                                                                                                 |
+| FI    | 0x81           | Format identifier                                                                                           |
+| GI    | 0xF0           | User defined parameter set                                                                                  |
+| GL    | 0x0A           | Length in octets for the rest of the message                                                                |
+| PI    | 0x01           | Unique ID                                                                                                   |
+| PL    | 0x03           | Length of PV field in octets                                                                                |
+| PV    | 0x58 0x11 0x15 | Unique ID supplied by the primary station for masked comparison with the unique ID of the secondary station |
+| PI    | 0x03           | Bit mask                                                                                                    |
+| PL    | 0x03           | Length of PV field in octets (same as for PI=1)                                                             |
+| PV    | 0xFF 0x17 0xFF | Bit mask to be applied                                                                                      |
+
+NOTE: The parameters may occur in any order in the XID command.
+
+## Device Scan Response
+
+When each secondary station in the NoAddress state receives the command it masks its Unique ID with the bit mask and compares the result with the Unique ID supplied as described in clause 4.8.4. If they match, the secondary station responds using XID format frame according to table 8 of section 5.5 of ISO/IEC 13239 [2].
+
+**Table E.2: Secondary device scan response (XID Frame) in case of a match**
+
+| Field | Content                          | Description                                                                                              |
+|-------|----------------------------------|----------------------------------------------------------------------------------------------------------|
+| ADDR  | 0x00                             | No station address                                                                                       |
+| CTRL  | 0xBF                             | XID command                                                                                              |
+| FI    | 0x81                             | Format identifier                                                                                        |
+| GI    | 0xF0                             | User defined parameter set                                                                               |
+| GL    | 0x0F                             | Length in octets for the rest of the message                                                             |
+| PI    | 0x01                             | Unique ID                                                                                                |
+| PL    | 0x06                             | Length of PV field in octets                                                                             |
+| PV    | 0x58 0x59 0x07 0x5B<br>0xCD 0x15 | Unique ID of the secondary station                                                                       |
+| PI    | 0x06                             | Vendor code                                                                                              |
+| PL    | 0x02                             | Length of PV field in octets                                                                             |
+| PV    | 0x58 0x59                        | Unique assigned vendor code as given in AISG v2.0 [4] (virtual vendor code "XY" is used in this example) |
+| PI    | 0x04                             | Device type                                                                                              |
+| PL    | 0x01                             | Length of PV field in octets                                                                             |
+| PV    | 0x01                             | Single-antenna RET device type as defined in table 4.7.1                                                 |
+
+NOTE1: In this device scan example, the virtual vendor code "XY", the unique ID "0x58 0x59 0x07 0x5B 0xCD 0x15", and the device type 0x01 for a single-antenna RET device are used.
+
+NOTE2: The parameters may occur in any order in the response.
+
+It is recommended that the response of individual devices is subject to a random delay (within the permitted response time) to aid collision detection at the primary station.
+
+If there is no response, the primary station knows that no secondary station had those bits in its Unique ID or that the secondary stations having those bits in their unique ID already have assigned addresses, so the tree scan can be truncated at that branch.
+
+If multiple secondary stations respond, the responses might garble each other, unless one secondary station is close enough to overpower the signal from the other(s).
+
+If any response arrives, a single frame, multiple frames or frames with incorrect checksums or framing errors, the branch of the tree is inhabited.
+
+# --- Annex F (informative): Change History
+
+| Change history |          |           |      |     |     |                                                                     |             |
+|----------------|----------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103   | R3-190095 |      |     |     | Text transferred from 25.462 v15.0.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83   | RP-190598 |      |     |     | Specification approved by RAN plenary                               | 15.1.0      |
+| 2019-12        | RP-86    | RP-192915 | 0001 | 6   | F   | Correction for luant                                                | 15.2.0      |
+| 2020-07        | RAN#88-e | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37466/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/37_series/37466/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ae7f578f2af4baa1f68ae153f78d25842191fa7
--- /dev/null
+++ b/marked/Rel-16/37_series/37466/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49774a1526d46f0e1c1b0452a572e29cab86564628c78b3a121bc8711eb3ad0a
+size 61519
diff --git a/marked/Rel-16/37_series/37466/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/37_series/37466/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..931c11b67f434513cccda625d669d9a6afa5ec23
--- /dev/null
+++ b/marked/Rel-16/37_series/37466/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79d784eb078bacb854232eaba7da78342f96ddc9620f27f44dcdd4fe37904407
+size 73364
diff --git a/marked/Rel-16/37_series/37466/bf862ae9378286aa6f9daa4346e7ed8d_img.jpg b/marked/Rel-16/37_series/37466/bf862ae9378286aa6f9daa4346e7ed8d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a4be6fdca8b33fded11d649ccc93bdcd5638737e
--- /dev/null
+++ b/marked/Rel-16/37_series/37466/bf862ae9378286aa6f9daa4346e7ed8d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fa8e82d58a61161388012762e31e234db47e40a7a47fb5ddf1ccb3c67606708
+size 5306
diff --git a/marked/Rel-16/37_series/37466/raw.md b/marked/Rel-16/37_series/37466/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..5813c019c906acd7d29029131ccfea221822a32e
--- /dev/null
+++ b/marked/Rel-16/37_series/37466/raw.md
@@ -0,0 +1,2309 @@
+
+
+
+
+
+
+# Contents
+
+|                                                    |    |
+|----------------------------------------------------|----|
+| Foreword .....                                     | 5  |
+| 1 Scope.....                                       | 6  |
+| 2 References.....                                  | 6  |
+| 3 Definitions and abbreviations .....              | 6  |
+| 3.1 Definitions.....                               | 6  |
+| 3.2 Abbreviations .....                            | 8  |
+| 4 General.....                                     | 8  |
+| 4.1 Procedure specification principles .....       | 8  |
+| 4.2 Forwards and backwards compatibility.....      | 8  |
+| 4.3 Multi-antenna units .....                      | 9  |
+| 4.4 Integer representation.....                    | 9  |
+| 4.5 TMA Subunits .....                             | 9  |
+| 5 Services expected from signalling transport..... | 9  |
+| 5.1 Elementary procedure format.....               | 9  |
+| 5.1.1 Initiating message.....                      | 9  |
+| 5.1.2 Response message .....                       | 9  |
+| 6 Control elementary procedures.....               | 10 |
+| 6.1 State model.....                               | 10 |
+| 6.2 General procedure handling .....               | 11 |
+| 6.2.1 Alarms .....                                 | 11 |
+| 6.2.2 Procedure message interpretation.....        | 11 |
+| 6.2.3 Parallel procedure handling.....             | 11 |
+| 6.3 Overview of elementary procedures .....        | 12 |
+| 6.4 Description of elementary procedures.....      | 14 |
+| 6.5 Common elementary procedures.....              | 15 |
+| 6.5.1 Reset Software.....                          | 15 |
+| 6.5.2 Get Alarm Status .....                       | 16 |
+| 6.5.3 Get Information .....                        | 16 |
+| 6.5.4 Clear Active Alarms .....                    | 17 |
+| 6.5.5 Alarm Subscribe .....                        | 18 |
+| 6.5.6 Self Test.....                               | 18 |
+| 6.5.7 Void.....                                    | 19 |
+| 6.5.8 Void.....                                    | 19 |
+| 6.5.9 Read User Data.....                          | 19 |
+| 6.5.10 Write User Data.....                        | 20 |
+| 6.5.11 Download Start.....                         | 21 |
+| 6.5.12 Download Application.....                   | 21 |
+| 6.5.13 Download End.....                           | 22 |
+| 6.5.14 Vendor specific procedure.....              | 23 |
+| 6.6 Single-antenna elementary procedures.....      | 23 |
+| 6.6.1 Calibrate .....                              | 23 |
+| 6.6.2 Send Configuration Data .....                | 24 |
+| 6.6.3 Set Tilt .....                               | 25 |
+| 6.6.4 Get Tilt.....                                | 26 |
+| 6.6.5 Alarm Indication.....                        | 26 |
+| 6.6.6 Set Device Data .....                        | 27 |
+| 6.6.7 Get Device Data .....                        | 27 |
+| 6.7 Multi-antenna elementary procedures.....       | 28 |
+| 6.7.1 Antenna Calibrate.....                       | 28 |
+| 6.7.2 Antenna Set Tilt.....                        | 29 |
+| 6.7.3 Antenna Get Tilt.....                        | 30 |
+| 6.7.4 Antenna Set Device Data.....                 | 30 |
+| 6.7.5 Antenna Get Device Data.....                 | 31 |
+| 6.7.6 Antenna Alarm Indication .....               | 32 |
+| 6.7.7 Antenna Clear Active Alarms .....            | 32 |
+
+|                                                                                                     |                                                     |           |
+|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------|-----------|
+| 6.7.8                                                                                               | Antenna Get Alarm Status .....                      | 33        |
+| 6.7.9                                                                                               | Antenna Get Number Of Antennas .....                | 34        |
+| 6.7.10                                                                                              | Antenna Send Configuration Data.....                | 34        |
+| 6.8                                                                                                 | TMAAP Elementary procedures for TMA .....           | 35        |
+| 6.8.1                                                                                               | TMA Set Mode.....                                   | 35        |
+| 6.8.2                                                                                               | TMA Get Mode .....                                  | 36        |
+| 6.8.3                                                                                               | TMA Get Supported Functions .....                   | 36        |
+| 6.8.4                                                                                               | TMA Set Gain .....                                  | 37        |
+| 6.8.5                                                                                               | TMA Get Gain.....                                   | 38        |
+| 6.8.6                                                                                               | TMA Set Device Data .....                           | 39        |
+| 6.8.7                                                                                               | TMA Get Device Data.....                            | 40        |
+| 6.8.8                                                                                               | TMA Alarm Indication.....                           | 40        |
+| 6.8.8.1                                                                                             | Further requirements .....                          | 41        |
+| 6.8.9                                                                                               | TMA Clear Active Alarms .....                       | 41        |
+| 6.8.10                                                                                              | TMA Get Alarm Status .....                          | 42        |
+| 6.8.11                                                                                              | TMA Get Number of Subunits .....                    | 42        |
+| 6.8.12                                                                                              | 3GPP Clear Active Alarms and Get Alarm Status ..... | 43        |
+| 6.8.13                                                                                              | TMA Get Supported Non-Linear Gain Values.....       | 43        |
+| 7                                                                                                   | Unknown elementary procedures.....                  | 44        |
+| <b>Annex A (normative): Return codes for secondary devices .....</b>                                |                                                     | <b>45</b> |
+| <b>Annex B (normative): Assigned fields for additional data .....</b>                               |                                                     | <b>46</b> |
+| <b>Annex C (normative): Procedure sequence for download of software to a secondary device .....</b> |                                                     | <b>49</b> |
+| <b>Annex D (informative): Overview of elementary procedures.....</b>                                |                                                     | <b>50</b> |
+| <b>Annex E (informative): I-frame and INFO-field format .....</b>                                   |                                                     | <b>52</b> |
+| <b>Annex F (Informative): Assigned fields for additional data coding for operating bands .....</b>  |                                                     | <b>53</b> |
+| <b>Annex G (informative): Change History.....</b>                                                   |                                                     | <b>56</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is an introduction to the 3GPP TS 37.46x series of Technical Specifications that define the Iuant Interface. The Iuant interface is applicable for UTRAN, E-UTRAN and NG-RAN. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". The logical Iuant interface is an interface internal to the RAN Node and defined to reside between the implementation specific O&M function and the RET antennas together with the TMAs control unit function of the RAN Node.
+
+The present document is applicable for UTRAN, E-UTRAN and NG-RAN and specifies the *Remote Electrical Tilting Application Part (RETAP)* and the *Tower Mounted Amplifier Application Part (TMAAP)*. In this specification UTRAN, E-UTRAN and NG-RAN are denoted as "RAN", whereas the corresponding network entities Node B, eNB, en-gNB and NG-RAN node are denoted as "RAN Node". RETAP supports the functions of the Iuant interface between the implementation specific O&M transport function and the RET Antenna Control unit function, TMAAP supports the functions of the Iuant interface between the implementation specific O&M transport function and the TMA control function.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] Void
+- [2] Void
+- [3] 3GPP TS 37.462: "Iuant Interface: Signalling Transport".
+- [4] 3GPP TS 37.461: "Iuant Interface: Layer 1".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**Active alarm:** An alarm which has an alarm state that has been raised, but not cleared
+
+**Alarm:** Persistent indication of a fault
+
+**Alarm code:** A code that identifies a specific alarm. The alarm code set is a subset of the return code set. The alarm codes are listed in annex A of this TS
+
+**Alarm state:** A condition or state in the existence of an alarm. Alarm states are raised and cleared
+
+**ASCII character:** A character forming part of the International Reference Version of the 7-bit character set defined in ISO/IEC 646:1991
+
+**Calibrate:** Exercise the antenna drive unit over its entire range of travel to ensure fault-free operation and synchronise the measured and actual beam tilt of the antenna
+
+**Configuration data:** A stored table or function defining the relationship between the physical position of the drive and electrical beam tilt
+
+**Data type:** A definition determining the value range and interpretation of a series of octets. The following specified data types are used in this TS:
+
+| Name:         | Definition:                                                                                  |
+|---------------|----------------------------------------------------------------------------------------------|
+| AlarmCode     | 1 octet unsigned enumerated code<br>All AlarmCode values are listed in annex A of this TS    |
+| FieldNumber   | 1 octet unsigned enumerated code<br>All field number values are listed in annex B of this TS |
+| ProcedureCode | 1 octet unsigned enumerated code                                                             |
+| ReturnCode    | 1 octet unsigned enumerated code<br>All ReturnCode values are listed in annex A of this TS   |
+| TextString    | Octets with integer values in the range of 32 to 126 to be interpreted as ASCII characters   |
+
+**Elementary procedure:** The RETAP and TMAAP protocol consists of elementary procedures (EPs). An elementary procedure is a unit of interaction between the primary device (RAN Node) and the secondary devices (RET or TMAs devices)
+
+An EP consists of an initiating message and possibly a response message.
+
+Two kinds of EPs are used:
+
+- **Class 1:** Elementary procedures with response (success or failure).
+- **Class 2:** Elementary procedures without response.
+
+For **Class 1** EPs, the types of responses can be as follows:
+
+Successful
+
+- A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response.
+
+Unsuccessful
+
+- A signalling message explicitly indicates that the EP failed.
+
+**Class 2** EPs are considered always successful.
+
+**Error:** Deviation of a system from normal operation
+
+**Fault:** Lasting error condition
+
+**Little endian:** The order of transmission in which the least-significant octets of a multi-octet representation of a number are transmitted first. Little endian only applies to binary integer representations
+
+**MaxDataReceiveLength:** SecondaryPayloadReceiveLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3])
+
+**MaxDataTransmitLength:** SecondaryPayloadTransmitLength minus 3 octets (see subclause 4.8.1 in TS 37.462 [3])
+
+**Procedure code:** A code identifying an elementary procedure
+
+**Reset:** A process by which the device is put in the state it reaches after a completed power-up
+
+**Return code:** A code which defines information about the outcome of an elementary procedure execution
+
+**Tilt (also downtilt, tilt angle, beamtilt):** The elevation angle between the direction orthogonal to the antenna element axis and the maximum of its main beam in the elevation plane. A positive electrical tilt angle means that the antenna beam is directed below the direction orthogonal to the antenna axis. An antenna has separate values for electrical and mechanical tilt. The mechanical tilt is fixed by the geometry of the installation. In this TS the tilt referred to is always the electrical tilt unless otherwise stated
+
+**Tilt value:** A signed integer used in elementary procedures to define the electrical tilt setting of the antenna. The tilt value is 10 times the antenna electrical tilt angle in degrees.
+
+**TMA:** A TMA comprises a low noise amplifier together with its control and monitoring electronics and optional antenna modem.
+
+**TMA subunit:** A TMA may comprise more than one TMA subunit. All TMA subunits within one TMA have the same HDLC address and are addressable by an index via the application layer procedures.
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                            |
+|-------|--------------------------------------------|
+| EP    | Elementary Procedure                       |
+| HDLC  | High-Level Data Link Control               |
+| RET   | Remote Electrical Tilting                  |
+| TMA   | Tower Mounted Amplifier                    |
+| RETAP | Remote Electrical Tilting Application Part |
+| TMAAP | Tower Mounted Amplifier Application Part   |
+| TCP   | Time-Consuming Procedure                   |
+
+# --- 4 General
+
+## 4.1 Procedure specification principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the RET antenna control unit and TMA Subunits exactly and completely. The RAN Node functional behaviour is left unspecified.
+
+The following specification principles have been applied for the procedure text in clause 6:
+
+- The procedure text discriminates between:
+
+- 1) Functionality which "shall" be executed
+
+The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+
+- 2) Functionality which "shall, if supported" be executed
+
+The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+
+## 4.2 Forwards and backwards compatibility
+
+The forwards and backwards compatibility of all versions of the protocol shall be assured by a mechanism in which all current and further messages will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+New functionalities are added into the specification by introducing new procedures and thus the existing messages are not changed in the future.
+
+## 4.3 Multi-antenna units
+
+The RETAP elementary procedures are split into a single-antenna oriented part, a multi-antenna oriented part and a common part for both device types in order to support RET units controlling single- or multi-antenna devices. The RET unit responds, upon request, the number of antennas it controls. All multi-antenna oriented elementary procedures include a parameter stating which antenna the elementary procedure addresses. Antennas are numbered 1 and upwards.
+
+## 4.4 Integer representation
+
+Multi-octet integer values are transmitted in little endian order. Signed integers are represented as 2-complement values.
+
+## 4.5 TMA Subunits
+
+TMA subunits shall be numbered starting with 1 and proceeding upwards. The error message format for TMA procedures follows that of multiple RET devices.
+
+# 5 Services expected from signalling transport
+
+RETAP and TMAAP requires an assured in-sequence delivery service from the signalling transport and notification if the assured in-sequence delivery service is no longer available.
+
+## 5.1 Elementary procedure format
+
+Layer 2 provides a full-duplex link for the transmission of RETAP and TMAAP messages.
+
+There are two types of RETAP and TMAAP elementary procedures:
+
+**Class 1:** Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary device, in order to initiate some action within the receiving device. The other device sends a response message completing the procedure.
+
+**Class 2:** Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary device. No response message is expected.
+
+All RETAP and TMAAP messages use the same basic format:
+
+**Table 5.1.1: Basic format for all RETAP and TMAAP messages**
+
+| Elementary procedure | Number of data octets | Data                                              |
+|----------------------|-----------------------|---------------------------------------------------|
+| 1 octet              | 2 octets              | MaxDataReceiveLength or<br>MaxDataTransmitLength. |
+
+NOTE: Response messages have the same basic format as initiating messages. The elementary procedure code shall be the same in the response message as in the associated initiating message.
+
+### 5.1.1 Initiating message
+
+The data part of an initiating message may contain parameters as specified in clause 6 of this TS.
+
+### 5.1.2 Response message
+
+Elementary procedures shall, unless otherwise specified, provide a response message within 1 second. The response time is measured from the time the message frame was received by the transport layer to the time the response message is ready for transfer by the transport layer.
+
+If the class1 elementary procedure requested by the initiating message was successfully executed, the response message data part from a single-antenna device shall contain return code <OK>. Additional information may follow in the data part. The response message data part from a multi-antenna device starts with the antenna number followed by return code <OK> and optional additional information.
+
+If the elementary procedure requested by the initiating message was not successfully executed, the response message data part from a single-antenna device shall contain return code <FAIL>.
+
+The following octet shall contain a second return code which describes why the execution of the requested procedure failed. The response message data part from a multi-antenna device starts with the antenna number followed by return code <FAIL> and a second return code which describes why the execution of the requested procedure failed.
+
+In some situations an initiating message can cause a change of operating conditions, for instance a SetTilt procedure might cause a RET device to discover that an adjuster is jammed or that a previously jammed adjuster works normally again. In these cases an alarm procedure reporting the change of operating conditions shall be used in addition to the regular <OK> or <FAIL> return codes in response message.
+
+A complete annotated table of all return codes with their corresponding hexadecimal numbers is provided in annex A of this TS.
+
+Return codes marked with an X in the Alarm column of annex A in this TS are used to report operating conditions in alarm procedures (see subclauses 6.6.5 and 6.7.6 for details).
+
+# 6 Control elementary procedures
+
+## 6.1 State model
+
+The state model describing the secondary device is shown in figure 6.1 with procedures written in *italic*.
+
+The relation to the connection state model for layer 2 can be found in TS 37.462 [3].
+
+![State model diagram for the Secondary device showing two states: DownloadMode and OperatingMode. Transitions include Link Establishment, Application software availability, DownloadStart, DownloadEnd/ResetSoftware, GetInformation/DownloadStart/DownloadApplication, and All other Elementary Procedures.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> DownloadMode : Link Establishment from state AddressAssigned, see ref. [3]
+    [*] --> OperatingMode : Application software is available
+    DownloadMode --> [*] : DownloadEnd or ResetSoftware to state NoAddress, see ref. [3]
+    DownloadMode --> DownloadMode : GetInformation, DownloadStart or DownloadApplication
+    OperatingMode --> DownloadMode : DownloadStart
+    OperatingMode --> OperatingMode : All other Elementary Procedures except for DownloadApplication and DownloadEnd
+  
+```
+
+The diagram illustrates the state model for the Secondary device. It consists of two main states: **DownloadMode** and **OperatingMode**. The initial state is a solid black circle. Transitions from the initial state are labeled *Link Establishment from state AddressAssigned, see ref. [3]* to **DownloadMode** and *Application software is available* to **OperatingMode**. From **DownloadMode**, a self-loop transition is labeled *GetInformation, DownloadStart or DownloadApplication*, and a transition to the final state (a bullseye symbol) is labeled *DownloadEnd or ResetSoftware to state NoAddress, see ref. [3]*. From **OperatingMode**, a transition to **DownloadMode** is labeled *DownloadStart*, and a self-loop transition is labeled *All other Elementary Procedures except for DownloadApplication and DownloadEnd*.
+
+State model diagram for the Secondary device showing two states: DownloadMode and OperatingMode. Transitions include Link Establishment, Application software availability, DownloadStart, DownloadEnd/ResetSoftware, GetInformation/DownloadStart/DownloadApplication, and All other Elementary Procedures.
+
+**Figure 6.1: State model for the Secondary device**
+
+If an application software is not missing the secondary device enters the state **OperatingMode**.
+
+If an application software is missing, the secondary device enters the state **DownloadMode**. In this state only software download functionality is supported in order to restore the application software.
+
+The primary device will be notified that the secondary device has entered the state **DownloadMode** when a procedure which only is supported in the state **OperatingMode** fails with the return code **WorkingSoftwareMissing**.
+
+If no software download functionality is supported, then only the state **OperatingMode** for the secondary device is supported.
+
+## 6.2 General procedure handling
+
+### 6.2.1 Alarms
+
+When a fault is detected, the corresponding alarm state shall be changed to state *raised* by the secondary device. When the fault no longer exists, the corresponding alarm state shall be changed to state *cleared* by the secondary device. Alarm changes are reported through the **AlarmIndication** or **AntennaAlarmIndication** elementary procedures. Whenever an **AlarmIndication** or **AntennaAlarmIndication** elementary procedure message is transmitted, it shall contain all the alarm states changed that have not yet been reported as described in subclauses 6.6.5 and 6.7.6.
+
+All alarm states shall be cleared by any type of reset.
+
+### 6.2.2 Procedure message interpretation
+
+The following message interpretation rules shall apply to a secondary device in the order mentioned:
+
+- Any message shorter than 3 octets shall be disregarded. In case of Multi-Antenna-Procedures or TMA-Procedures, which uses a subunit field, any messages shorter than 4 octets shall be disregarded;
+- If a message has a length inconsistent with its "Number of data octets" field value it shall be responded with a failure message stating "FormatError" as the cause of failure. The response message shall be to the initiating message identified by the procedure code;
+- If a secondary device in the OperatingMode state receives a procedure message which is undefined for this device type, it shall respond with "Unknown Procedure";
+- If a secondary device in the OperatingMode state is receiving a procedure message of an optional procedure not supported, it shall respond with a failure message stating "UnsupportedProcedure" as the cause of failure;
+- If a secondary device receives a procedure message, part of the software download procedure sequence described in Annex C, without having received the previous procedure messages in that sequence it shall respond with a failure message stating "InvalidProcedureSequence" as the cause of failure;
+- If a secondary device in the DownloadMode state is receiving a procedure message not supported in that state it shall respond with a failure message stating "WorkingSoftwareMissing" as the cause of failure;
+- If a message has a length inconsistent with the defined message length in the procedure definition it shall be responded with a failure message stating "FormatError" as the cause of failure. The response message shall be to the initiating message identified by the procedure code;
+- If a secondary device in the OperatingMode state is receiving a procedure message which addressed device subunit does not exist "FormatError" shall be returned.
+
+### 6.2.3 Parallel procedure handling
+
+The secondary device shall support parallel execution of in maximum one additional EP only in parallel to one of the Time-Consuming Procedures defined in table 6.2.3.1:
+
+**Table 6.2.3.1: Definition of TCPs and the execution of procedures in parallel to a TCP**
+
+| Elementary Procedure                | TCP             | Execution in parallel to a TCP |
+|-------------------------------------|-----------------|--------------------------------|
+| <b>Common Procedure Set</b>         |                 |                                |
+| (Reserved)                          |                 |                                |
+| Reset Software                      | No              | mandatory                      |
+| Get Alarm Status                    | No              | mandatory                      |
+| Get Information                     | No              | mandatory                      |
+| Clear Active Alarms                 | No              | disallowed                     |
+| Read User Data                      | No              | optional                       |
+| Write User Data                     | No              | optional                       |
+| Alarm Subscribe                     | No              | optional                       |
+| Self Test                           | Yes             | disallowed                     |
+| Download Start                      | No              | disallowed                     |
+| Download Application                | No              | disallowed                     |
+| Download End                        | No              | disallowed                     |
+| Vendor specific procedure           | vendor specific | optional                       |
+| <b>Single-Antenna Procedure Set</b> |                 |                                |
+| Set Device Data                     | No              | optional                       |
+| Get Device Data                     | No              | optional                       |
+| Calibrate                           | Yes             | disallowed                     |
+| Send Configuration Data             | No              | disallowed                     |
+| Set Tilt                            | Yes             | disallowed                     |
+| Get Tilt                            | No              | optional                       |
+| Alarm Indication                    | No              | optional                       |
+| <b>Multi-Antenna Procedure Set</b>  |                 |                                |
+| Antenna Calibrate                   | Yes             | optional                       |
+| Antenna Send Configuration Data     | No              | disallowed                     |
+| Antenna Set Tilt                    | Yes             | optional                       |
+| Antenna Get Tilt                    | No              | optional                       |
+| Antenna Set Device Data             | No              | optional                       |
+| Antenna Get Device Data             | No              | optional                       |
+| Antenna Alarm Indication            | No              | optional                       |
+| Antenna Clear Active Alarms         | No              | disallowed                     |
+| Antenna Get Alarm Status            | No              | mandatory                      |
+| Antenna Get Number of Antennas      | No              | mandatory                      |
+
+"yes" in the "TCP" column indicates that the procedure is a TCP, "no" in the "TCP" column indicates that the procedure is not a TCP. "mandatory" in the "Execution in parallel to a TCP" column indicates that the procedure shall be executed in parallel to an ongoing TCP. "optional" in this column indicates, that the support of the execution of the procedure in parallel to an ongoing TCP is optional and "disallowed" indicates that the procedure shall not be executed in parallel to a TCP.
+
+If a secondary device receives an initiating message for an EP which cannot be executed due to the ongoing execution of other EPs, the secondary device shall respond with a failure message stating "Busy" as the cause of failure.
+
+Parallel execution of one TCP marked "optional" in the "Execution in parallel to a TCP" column in table 6.2.3.1 may be supported for each antenna by the secondary device. The EPs AntennaSetTilt and AntennaCalibrate shall be executed in parallel only for different antenna numbers. If more than one TCP is executed, ResetSoftware shall be executed anyway and never be responded with "Busy".
+
+If the EPs Get Tilt and Antenna GetTilt are executed in parallel with a TCP, their response message shall deliver a tilt value sampled during their execution.
+
+TMAAP doesn't define any TCPs. Therefore parallel procedure handling is not supported by TMAAP.
+
+## 6.3 Overview of elementary procedures
+
+The set of elementary procedures for RET antennas and TMAs control provides procedure-oriented instructions. An overview of the procedures is given in annex D. Table 6.3.1 lists all common elementary procedures described in subclause 6.5. Table 6.3.2 lists all RETAP elementary procedures specific for single-antenna device types described in subclause 6.6. Table 6.3.3 lists all RETAP elementary procedures specific for multi-antenna device types described in
+
+subclause 6.7. Table 6.3.4 lists all TMAAP elementary procedures specific for TMA device types described in subclause 6.8. Subclause 6.4 describes how to interpret the elementary procedure definitions in subclauses 6.5 to 6.8.
+
+Some elementary procedures shall be performed in sequence as described in Annex C for the software download.
+
+**Table 6.3.1: Common elementary procedure set for all device types**
+
+| <b>Elementary procedure</b> | <b>Requirement</b> | <b>Comment</b>                                                            |
+|-----------------------------|--------------------|---------------------------------------------------------------------------|
+| Reset Software              | Mandatory          |                                                                           |
+| Get Alarm Status            | Mandatory          |                                                                           |
+| Get Information             | Mandatory          |                                                                           |
+| Clear Active Alarms         | Mandatory          |                                                                           |
+| Alarm Subscribe             | Mandatory          |                                                                           |
+| Read User Data              | Mandatory          |                                                                           |
+| Write User Data             | Mandatory          |                                                                           |
+| Self Test                   | Mandatory          |                                                                           |
+| Download Start              | Optional           | This procedure is mandatory if the software download feature is supported |
+| Download Application        | Optional           | This procedure is mandatory if the software download feature is supported |
+| Download End                | Optional           | This procedure is mandatory if the software download feature is supported |
+| Vendor specific procedure   | Optional           |                                                                           |
+
+**Table 6.3.2: RETAP Elementary procedure set for single-antenna device type**
+
+| <b>Elementary procedure</b> | <b>Requirement</b> | <b>Comment</b> |
+|-----------------------------|--------------------|----------------|
+| Calibrate                   | Mandatory          |                |
+| Send Configuration Data     | Mandatory          |                |
+| Set Tilt                    | Mandatory          |                |
+| Get Tilt                    | Mandatory          |                |
+| Alarm Indication            | Mandatory          |                |
+| Set Device Data             | Mandatory          |                |
+| Get Device Data             | Mandatory          |                |
+
+**Table 6.3.3: RETAP Elementary procedure set for multi-antenna device type**
+
+| <b>Elementary procedure</b>     | <b>Requirement</b> | <b>Comment</b> |
+|---------------------------------|--------------------|----------------|
+| Antenna Calibrate               | Mandatory          |                |
+| Antenna Send Configuration Data | Mandatory          |                |
+| Antenna Set Tilt                | Mandatory          |                |
+| Antenna Get Tilt                | Mandatory          |                |
+| Antenna Set Device Data         | Mandatory          |                |
+| Antenna Get Device Data         | Mandatory          |                |
+| Antenna Alarm Indication        | Mandatory          |                |
+| Antenna Clear Active Alarms     | Mandatory          |                |
+| Antenna Get Alarm Status        | Mandatory          |                |
+| Antenna Get Number Of Antennas  | Mandatory          |                |
+
+**Table 6.3.4: TMAAP elementary procedure set for TMA devices**
+
+| <b>Elementary procedure</b>        | <b>Requirement</b> | <b>Comment</b>                                                                          |
+|------------------------------------|--------------------|-----------------------------------------------------------------------------------------|
+| TMASetMode                         | Optional           | Shall only be supported if the TMA subunit supports bypass mode                         |
+| TMAGetMode                         | Mandatory          |                                                                                         |
+| TMAGetSupportedFunctions           | Mandatory          |                                                                                         |
+| TMASetGain                         | Optional           | Shall only be supported if the TMA subunit supports variable gain                       |
+| TMAGetGain                         | Mandatory          |                                                                                         |
+| TMASetDeviceData                   | Mandatory          |                                                                                         |
+| TMAGetDeviceData                   | Mandatory          |                                                                                         |
+| TMAAlarmIndication                 | Mandatory          |                                                                                         |
+| TMAClearActiveAlarms               | Mandatory          |                                                                                         |
+| TMAGetAlarmStatus                  | Mandatory          |                                                                                         |
+| TMAGetNumberOfSubunits             | Mandatory          |                                                                                         |
+| TMAGetSupportedNonLinearGainValues | Optional           | Shall only be supported if the TMA subunit supports variable gain with non-linear steps |
+
+## 6.4 Description of elementary procedures
+
+**Table 6.4.1: Description of elementary procedures**
+
+|                                                                                     |                                                         |                                               |                                                                                                           |                                                                                                                                                      |
+|-------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Name:</b><br>The name used to refer to the elementary procedure                  |                                                         |                                               |                                                                                                           |                                                                                                                                                      |
+| <b>Code:</b><br>The code is defined here. All other code references are informative | <b>Issued by:</b><br>Primary device or secondary device | <b>Procedure class:</b><br>Class 1 or Class 2 | <b>DownloadMode state:</b><br>Defines whether the procedure shall be supported in the DownloadMode state. | <b>Power mode:</b><br>Defines the secondary device power consumption as described in TS 37.461 [4] during the execution of the elementary procedure. |
+
+**Table 6.4.2: Initiating and response message parameters and format**
+
+| <b>Number</b>                                                                                               | <b>Length</b>                                                 | <b>Type</b>                          | <b>Description</b>            |
+|-------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------|-------------------------------|
+| The enumerated order in which the parameter occurs in the data field of the message. The first number is 1. | The length of the parameter, in number of octets, if defined. | The data type used in the parameter. | Description of the parameter. |
+
+**Table 6.4.3: Response message parameters and format for common class 1 elementary procedures upon error**
+
+| <b>Number</b> | <b>Length</b> | <b>Type</b> | <b>Description</b> |
+|---------------|---------------|-------------|--------------------|
+| 1             | 1 octet       | ReturnCode  | Return code FAIL   |
+| 2             | 1 octet       | ReturnCode  | Reason for failure |
+
+**Table 6.4.4: Response message parameters and format for single-antenna class 1 elementary procedures upon error**
+
+| <b>Number</b> | <b>Length</b> | <b>Type</b> | <b>Description</b> |
+|---------------|---------------|-------------|--------------------|
+| 1             | 1 octet       | ReturnCode  | Return code FAIL   |
+| 2             | 1 octet       | ReturnCode  | Reason for failure |
+
+Table 6.4.5: Response message parameters and format for multi-antenna class 1 and TMA subunit class 1 elementary procedures upon error
+
+| Number | Length  | Type             | Description                          |
+|--------|---------|------------------|--------------------------------------|
+| 1      | 1 octet | Unsigned integer | Antenna number or TMA subunit number |
+| 2      | 1 octet | ReturnCode       | Return code FAIL                     |
+| 3      | 1 octet | ReturnCode       | Reason for failure                   |
+
+NOTE 1: The response message in the elementary procedure AntennaGetAntennaNumber, has the format given in table 6.4.4, although it is defined as a multi-antenna class 1 elementary procedure.
+
+NOTE 2: The response message in the elementary procedure TMAGetNumberOfSubunits has the format given in table 6.4.4 as class 1 elementary procedure.
+
+Table 6.4.6: Return codes
+
+| OK                                                                                                                                                                    | FAIL                                                                                                                                                                | Comment                               |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|
+| All return codes applicable in a response message to a successful procedure, except "OK", are listed here. The return codes are listed by name as defined in annex A. | All return codes applicable in a response message to a failing procedure, except "FAIL" are listed here. The return codes are listed by name as defined in annex A. | Any comment needed for clarification. |
+
+## 6.5 Common elementary procedures
+
+### 6.5.1 Reset Software
+
+Table 6.5.1.1: Elementary procedure Reset Software
+
+| Name:<br>ResetSoftware |                |                  |                     |             |
+|------------------------|----------------|------------------|---------------------|-------------|
+| Code:                  | Issued by:     | Procedure class: | DownloadMode state. | Power mode: |
+| 0x03                   | Primary device | 1                | Yes                 | Low         |
+
+Table 6.5.1.2: Initiating message parameters and format for Reset Software
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.1.3: Response message parameters and format for Reset Software
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On the receipt of the initiating message the secondary device shall reset the application. All alarm states shall be cleared.
+
+If the initiating message is received in the OperatingMode state, the transport layer shall remain unaffected.
+
+If the initiating message is received in the DownloadMode state, the ResetSoftware procedure shall reset the entire device without activating any new application software downloaded since entering the DownloadMode state.
+
+The device shall not execute the reset procedure before transport layer acknowledgement through sequence number update is received for the response.
+
+Table 6.5.1.4: Return codes for Reset Software
+
+| OK | FAIL        | Comment                                                              |
+|----|-------------|----------------------------------------------------------------------|
+|    | FormatError | In case of format error, the procedure code validity is not secured. |
+
+### 6.5.2 Get Alarm Status
+
+Table 6.5.2.1: Elementary procedure Get Alarm Status
+
+|                                |                                     |                              |                                  |                           |
+|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>GetAlarmStatus</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x04</b>           | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.2.2: Initiating message parameters and format for Get Alarm Status
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.2.3: Response message parameters and format for Get Alarm Status
+
+| Number | Length  | Type       | Description           |
+|--------|---------|------------|-----------------------|
+| 1      | 1 octet | ReturnCode | Return code OK        |
+| i + 1  | 1 octet | AlarmCode  | Active alarm number i |
+
+i = 1 ... N
+
+#### Description:
+
+On receipt of the initiating message the secondary device reports the alarm codes of the active alarms.
+
+Table 6.5.2.4: Return codes for Get Alarm Status
+
+| OK                                                     | FAIL                                  | Comment |
+|--------------------------------------------------------|---------------------------------------|---------|
+| All return codes marked as used for alarms in Annex A. | FormatError<br>WorkingSoftwareMissing |         |
+
+### 6.5.3 Get Information
+
+Table 6.5.3.1: Elementary procedure Get Information
+
+|                                |                                     |                              |                                   |                           |
+|--------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------|
+| Name:<br><b>GetInformation</b> |                                     |                              |                                   |                           |
+| Code:<br><b>0x05</b>           | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>Yes</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.3.2: Initiating message parameters and format for Get Information
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.3.3: Response message parameters and format for Get Information
+
+| Number | Length  | Type             | Description                               |
+|--------|---------|------------------|-------------------------------------------|
+| 1      | 1 octet | ReturnCode       | Return code OK                            |
+| 2      | 1 octet | Unsigned integer | Length of parameter 3 in number of octets |
+| 3      |         | TextString       | Product number                            |
+| 4      | 1 octet | Unsigned integer | Length of parameter 5 in number of octets |
+| 5      |         | TextString       | Serial number                             |
+| 6      | 1 octet | Unsigned integer | Length of parameter 7 in number of octets |
+| 7      |         | TextString       | Hardware Version                          |
+| 8      | 1 octet | Unsigned integer | Length of parameter 9 in number of octets |
+| 9      |         | TextString       | Software Version                          |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall return the product number ProdNr and the serial number SerNr of the secondary device. If known, also the hardware version and the software version may be returned. The software version should indicate the version number of the currently executed software.
+
+The parameters HWVersion and SWVersion in the response message refer to the version designators of the hardware and installed software of the secondary device. If the application is missing or no HW or SW version number is found, then an empty string shall be returned as the HW or SW version number. The empty string is represented as a length field equals 0 and no octets in the TextString field.
+
+The response message length shall be less than or equal to the minimum SecondaryPayloadTransmitLength as given in subclause 4.8.1 in TS 37.462 [3].
+
+Table 6.5.3.4: Return codes for Get Information
+
+| OK | FAIL        | Comment |
+|----|-------------|---------|
+|    | FormatError |         |
+
+### 6.5.4 Clear Active Alarms
+
+Table 6.5.4.1: Elementary procedure Clear Active Alarms
+
+|                                   |                                     |                              |                                  |                           |
+|-----------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>ClearActiveAlarms</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x06</b>              | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.4.2: Initiating message parameters and format for Clear Active Alarms
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.4.3: Response message parameters and format for Clear Active Alarms
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall first clear all stored alarm information and then return a procedure response message.
+
+Table 6.5.4.4: Return codes for Clear Active Alarms
+
+| OK | FAIL                                          | Comment |
+|----|-----------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+### 6.5.5 Alarm Subscribe
+
+Table 6.5.5.1: Elementary procedure Alarm Subscribe
+
+|                                |                                     |                              |                                  |                           |
+|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AlarmSubscribe</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x12</b>           | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.5.2: Initiating message parameters and format for Alarm Subscribe
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.5.3: Response message parameters and format for Alarm Subscribe
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall start reporting alarms to the primary device.
+
+Table 6.5.5.4: Return codes for Alarm Subscribe
+
+| OK | FAIL                                          | Comment |
+|----|-----------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+### 6.5.6 Self Test
+
+Table 6.5.6.1: Elementary procedure Self Test
+
+|                          |                                     |                              |                                  |                            |
+|--------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------|
+| Name:<br><b>SelfTest</b> |                                     |                              |                                  |                            |
+| Code:<br><b>0x0A</b>     | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>High</b> |
+
+Table 6.5.6.2: Initiating message parameters and format for Self Test
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.6.3: Response message parameters and format for Self Test
+
+| Number | Length  | Type       | Description                                       |
+|--------|---------|------------|---------------------------------------------------|
+| 1      | 1 octet | ReturnCode | Return code OK                                    |
+| i + 1  | 1 octet | AlarmCode  | Alarm code for alarm i detected during self test. |
+
+i = 1 ... N
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall execute a test procedure which may include a check of physical and processor functions. The specific tests to be performed are implementation specific, and may include the movement of the adjuster, which shall not exceed  $\pm 5\%$  of total available tilting range starting from the current adjuster position.
+
+The response message of the secondary device on the procedure provides information on detected faults or, if no fault is detected, with confidence that the operation of the device is normal in all respects.
+
+During the test the operational parameters of the device shall not change beyond operationally acceptable limits and on completion all parameters shall be returned to their initial values.
+
+In the normal response message, after the self test was executed successfully, the return codes are set to report possible detected faults during the self test. If no faults are detected, this shall be signalled by no return codes following the return code <OK>.
+
+In the case of a failure response message, the self test could not be executed successfully and the reported return code relates to the inability of the device to perform the requested self-test operation.
+
+Table 6.5.6.4: Return codes for Self Test
+
+| OK                                            | FAIL                                                                        | Comment |
+|-----------------------------------------------|-----------------------------------------------------------------------------|---------|
+| All return codes marked as alarms in annex A. | FormatError<br>Busy<br>WorkingSoftwareMissing<br>NotCalibrated<br>NotScaled |         |
+
+### 6.5.7 Void
+
+### 6.5.8 Void
+
+### 6.5.9 Read User Data
+
+Table 6.5.9.1: Elementary procedure Read User Data
+
+|                              |                                     |                              |                                  |                           |
+|------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>ReadUserData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x10</b>         | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.9.2: Initiating message parameters and format for Read User Data
+
+| Number | Length   | Type             | Description              |
+|--------|----------|------------------|--------------------------|
+| 1      | 2 octets | Unsigned integer | Memory offset            |
+| 2      | 1 octet  | Unsigned integer | Number of octets to read |
+
+NOTE: Number of octets to read shall be less than, or equal to MaxDataTransmit Length minus 1.
+
+Table 6.5.9.3: Response message parameters and format for Read User Data
+
+| Number | Length                                                          | Type          | Description    |
+|--------|-----------------------------------------------------------------|---------------|----------------|
+| 1      | 1 octet                                                         | ReturnCode    | Return code OK |
+| 2      | Number of octets given by parameter 2 of the initiating message | User specific | User data      |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall send back user specific data stored in a user data area to the primary device.
+
+The user data area is intended for storage of user defined data, e.g. inventory information.
+
+Table 6.5.9.4: Return codes for Read User Data
+
+| OK | FAIL                                                | Comment                                                                                                   |
+|----|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------|
+|    | FormatError<br>WorkingSoftwareMissing<br>OutOfRange | The return code OutOfRange is used, if the given memory address range is outside the valid address space. |
+
+### 6.5.10 Write User Data
+
+Table 6.5.10.1: Elementary procedure Write User Data
+
+|                               |                                     |                              |                                  |                           |
+|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>WriteUserData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x11</b>          | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.10.2: Initiating message parameters and format for Write User Data
+
+| Number | Length                                 | Type             | Description               |
+|--------|----------------------------------------|------------------|---------------------------|
+| 1      | 2 octets                               | Unsigned integer | Memory offset             |
+| 2      | 1 octet                                | Unsigned integer | Number of octets to write |
+| 3      | Message specific, given by parameter 2 | User specific    | Data to write             |
+
+NOTE: Number of octets to write shall be less than, or equal to MaxDataReceiveLength minus 3.
+
+Table 6.5.10.3: Response message parameters and format for Write User Data
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall store user data in non-volatile memory. The user data is stored in the user data area using the relative memory address offset given in the initiating message and starting with zero.
+
+The user data area is intended for storage of user defined data, e.g. inventory information.
+
+Table 6.5.10.4: Return codes for Write User Data
+
+| OK | FAIL                                                                         | Comment                                                                                                  |
+|----|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>HardwareError<br>OutOfRange | The return code OutOfRange is used if the given memory address range is outside the valid address space. |
+
+### 6.5.11 Download Start
+
+Table 6.5.11.1: Elementary procedure Download Start
+
+|                               |                                     |                              |                                   |                           |
+|-------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------|
+| Name:<br><b>DownloadStart</b> |                                     |                              |                                   |                           |
+| Code:<br><b>0x40</b>          | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>Yes</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.11.2: Initiating message parameters and format for Download Start
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.11.3: Response message parameters and format for Download Start
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### **Description:**
+
+On receipt of this initiating message the software download process shall be initiated. Following transition to the DownloadMode state, the secondary device sends return code <OK>. Previous subscription of alarms by use of the AlarmSubscribe procedure is cancelled.
+
+Table 6.5.11.4: Return codes for Download Start
+
+| OK | FAIL                                        | Comment |
+|----|---------------------------------------------|---------|
+|    | FormatError<br>Busy<br>UnsupportedProcedure |         |
+
+### 6.5.12 Download Application
+
+Table 6.5.12.1: Elementary procedure Download Application
+
+|                                     |                                     |                              |                                   |                           |
+|-------------------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------|
+| Name:<br><b>DownloadApplication</b> |                                     |                              |                                   |                           |
+| Code:<br><b>0x41</b>                | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>Yes</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.12.2: Initiating message parameters and format for Download Application
+
+| Number | Length                                      | Type            | Description   |
+|--------|---------------------------------------------|-----------------|---------------|
+| 1      | Less than, or equal to MaxDataReceiveLength | Vendor specific | Software data |
+
+Table 6.5.12.3: Response message parameters and format for Download Application
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### **Description:**
+
+This elementary procedure is used once or several times to transfer software data from the primary device to the secondary device.
+
+Table 6.5.12.4: Return codes for Download Application
+
+| OK | FAIL                                                                                   | Comment |
+|----|----------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>InvalidFileContent<br>InvalidProcedureSequence |         |
+
+### 6.5.13 Download End
+
+**Table 6.5.13.1: Elementary procedure Download End**
+
+|                             |                                     |                              |                                   |                           |
+|-----------------------------|-------------------------------------|------------------------------|-----------------------------------|---------------------------|
+| Name:<br><b>DownloadEnd</b> |                                     |                              |                                   |                           |
+| Code:<br><b>0x42</b>        | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>Yes</b> | Power mode:<br><b>Low</b> |
+
+Table 6.5.13.2: Initiating message parameters and format for Download End
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.5.13.3: Response message parameters and format for Download End
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+This elementary procedure signals the end of a multi-message data transfer to the secondary device. The secondary device shall respond after verifying the received data. The secondary device shall reset autonomously after completion of the layer 2 response and activate the new application software.
+
+Table 6.5.13.4: Return codes for Download End
+
+| OK | FAIL                                                                                                    | Comment |
+|----|---------------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>ChecksumError<br>InvalidFileContent<br>InvalidProcedureSequence |         |
+
+### 6.5.14 Vendor specific procedure
+
+**Table 6.5.14.1: Elementary procedure Vendor Specific Procedure**
+
+|                                         |                                      |                                            |                                               |                                       |
+|-----------------------------------------|--------------------------------------|--------------------------------------------|-----------------------------------------------|---------------------------------------|
+| Name:<br><b>VendorSpecificProcedure</b> |                                      |                                            |                                               |                                       |
+| Code:<br><b>0x90</b>                    | Issued by:<br><b>Vendor specific</b> | Procedure class:<br><b>Vendor specific</b> | DownloadMode state:<br><b>Vendor specific</b> | Power mode:<br><b>Vendor specific</b> |
+
+Table 6.5.14.2: Initiating message parameters and format for Vendor Specific Procedure
+
+| Number | Length          | Type            | Description |
+|--------|-----------------|-----------------|-------------|
+| 1      | 2 octets        | ASCII           | Vendor code |
+| 1 + i  | Vendor specific | Vendor specific |             |
+
+i = 1 ... N
+
+Table 6.5.14.3: Response message parameters and format for Vendor Specific Procedure
+
+| Number | Length          | Type            | Description     |
+|--------|-----------------|-----------------|-----------------|
+| 1      | Vendor specific | Vendor specific | Vendor specific |
+
+i = 1 ... N
+
+#### Description:
+
+The vendor specific procedure is intended for vendor specific purposes like e.g. testing.
+
+Table 6.5.14.4: Return codes for vendor specific procedure
+
+| OK | FAIL                                | Comment                                                                                                                     |
+|----|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
+|    | FormatError<br>UnsupportedProcedure | If the Vendor code in the initiating message does not match that of the RET device, UnsupportedProcedure shall be returned. |
+
+## 6.6 Single-antenna elementary procedures
+
+### 6.6.1 Calibrate
+
+Table 6.6.1.1: Elementary procedure Calibrate
+
+|                           |                                     |                              |                                  |                            |
+|---------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------|
+| Name:<br><b>Calibrate</b> |                                     |                              |                                  |                            |
+| Code:<br><b>0x31</b>      | Issued by:<br><b>Primary Device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>High</b> |
+
+Table 6.6.1.2: Initiating message parameters and format for Calibrate
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.6.1.3: Response message parameters and format for Calibrate
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall perform a calibration of the RET antenna where the actuator is driven through its whole tilt range.
+
+The response time to this Calibrate procedure shall be less than 4 minutes.
+
+Table 6.6.1.4: Return codes for Calibrate
+
+| OK | FAIL                                                                                                                               | Comment |
+|----|------------------------------------------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>MotorJam<br>ActuatorJam<br>NotConfigured<br>UnsupportedProcedure |         |
+
+### 6.6.2 Send Configuration Data
+
+Table 6.6.2.1: Elementary procedure Send Configuration Data
+
+|                                       |                                     |                              |                                  |                           |
+|---------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>SendConfigurationData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x32</b>                  | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.6.2.2: Initiating message parameters and format for Send Configuration Data
+
+| Number | Length                                      | Type            | Description        |
+|--------|---------------------------------------------|-----------------|--------------------|
+| 1      | Less than, or equal to MaxDataReceiveLength | Vendor specific | Configuration data |
+
+Table 6.6.2.3: Response message parameters and format for Send Configuration Data
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall store the provided vendor and antenna specific configuration data for the relationship between the movement of the drive system and the beam tilt position of the antenna.
+
+If the configuration data exceeds MaxDataReceiveLength, the data shall be split into a number of MaxDataReceiveLength segments and one final segment with whatever is left. The primary device transmits the segments in order. The layer 2 sequence numbers guarantee that no segment will be lost or received out of order.
+
+Table 6.6.2.4: Return codes for Send Configuration Data
+
+| OK | FAIL                                                                                                                          | Comment |
+|----|-------------------------------------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>ChecksumError<br>InvalidFileContent<br>UnsupportedProcedure |         |
+
+### 6.6.3 Set Tilt
+
+Table 6.6.3.1: Elementary procedure Set Tilt
+
+|                         |                                     |                              |                                  |                            |
+|-------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------|
+| Name:<br><b>SetTilt</b> |                                     |                              |                                  |                            |
+| Code:<br><b>0x33</b>    | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>High</b> |
+
+Table 6.6.3.2: Initiating message parameters and format for Set Tilt
+
+| Number | Length   | Type           | Description |
+|--------|----------|----------------|-------------|
+| 1      | 2 octets | Signed integer | Tilt value  |
+
+Table 6.6.3.3: Response message parameters and format for Set Tilt
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall set the electrical tilt in increments of 0.1°.
+
+The secondary device shall respond to the initiating message in less than 2 minutes.
+
+The tilt value corresponding to the actual tilt angle shall not go outside of the range between the tilt value corresponding to the current tilt angle and the tilt value corresponding to the requested tilt angle by more than 5 during this operation.
+
+The format of the value of parameter 1 is given in subclause 3.1.
+
+Table 6.6.3.4: Return codes for Set Tilt
+
+| OK | FAIL                                                                                                                                                              | Comment |
+|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>MotorJam<br>ActuatorJam<br>NotConfigured<br>NotCalibrated<br>OutOfRange<br>UnsupportedProcedure |         |
+
+### 6.6.4 Get Tilt
+
+Table 6.6.4.1: Elementary procedure Get Tilt
+
+|                         |                                     |                              |                                  |                           |
+|-------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>GetTilt</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x34</b>    | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.6.4.2: Initiating message parameters and format for Get Tilt
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.6.4.3: Response message parameters and format for Get Tilt
+
+| Number | Length   | Type           | Description    |
+|--------|----------|----------------|----------------|
+| 1      | 1 octet  | ReturnCode     | Return code OK |
+| 2      | 2 octets | Signed integer | Tilt value     |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall return the current tilt value.
+
+The returned tilt value is given in the format specified in subclause 3.1.
+
+Table 6.6.4.4: Return codes for Get Tilt
+
+| OK | FAIL                                                                                                                     | Comment                                                                  |
+|----|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>NotCalibrated<br>NotConfigured<br>UnsupportedProcedure | HardwareError shall only be used, if error is detected in tilt detector. |
+
+### 6.6.5 Alarm Indication
+
+Table 6.6.5.1: Elementary procedure Alarm Indication
+
+|                                 |                                       |                              |                                  |                           |
+|---------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AlarmIndication</b> |                                       |                              |                                  |                           |
+| Code:<br><b>0x07</b>            | Issued by:<br><b>Secondary device</b> | Procedure class:<br><b>2</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.6.5.2: Initiating message parameters and format for Alarm Indication
+
+| Number  | Length  | Type             | Description                |
+|---------|---------|------------------|----------------------------|
+| 2 i – 1 | 1 octet | Unsigned integer | Return code i; see annex A |
+| 2 i     | 1 octet | Unsigned integer | State flag i               |
+
+i = 1 ... N
+
+#### Description:
+
+The secondary device uses this procedure to report alarm state changes to the primary device. This procedure shall only be performed if the secondary has performed an AlarmSubscribe procedure since its latest reset.
+
+For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred during the period of time since the last reported state. An AlarmIndication procedure shall be performed if at least one alarm shall be reported. The first AlarmIndication procedure after the AlarmSubscribe procedure shall report the active alarms.
+
+Alarm state changes are considered as reported at the time the message is passed to the transport layer.
+
+State flag = 0 represents alarm state *cleared*.
+
+State flag = 1 represents alarm state *raised*.
+
+### 6.6.6 Set Device Data
+
+Table 6.6.6.1: Elementary procedure Set Device Data
+
+|                               |                                     |                              |                                  |                           |
+|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>SetDeviceData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x0E</b>          | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.6.6.2: Initiating message parameters and format for Set Device Data
+
+| Number | Length      | Type             | Description               |
+|--------|-------------|------------------|---------------------------|
+| 1      | 1 octet     | Unsigned integer | Field number, see annex B |
+| 2      | See annex B | See annex B      | Data to write             |
+
+Table 6.6.6.3: Response message parameters and format for Set Device Data
+
+| Number | Length  | Type       | Description    |
+|--------|---------|------------|----------------|
+| 1      | 1 octet | ReturnCode | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall write the data given in the parameters of the initiating message into the fields optionally provided for configuration data and listed in annex B of this TS. If an attempt is made to write to fields which are designated as read only, the return code *ReadOnly* is returned and the data for those fields is ignored. If an attempt is made to write to fields which are not supported by the device the return code *UnknownParameter* is returned and the data for those fields is ignored.
+
+Table 6.6.6.4: Return codes for Set Device Data
+
+| OK | FAIL                                                                                           | Comment |
+|----|------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>HardwareError<br>ReadOnly<br>UnknownParameter |         |
+
+### 6.6.7 Get Device Data
+
+**Table 6.6.7.1: Elementary procedure Get Device Data**
+
+|                               |                                     |                              |                                  |                           |
+|-------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>GetDeviceData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x0F</b>          | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.6.7.2: Initiating message parameters and format for Get Device Data
+
+| Number | Length  | Type             | Description               |
+|--------|---------|------------------|---------------------------|
+| 1      | 1 octet | Unsigned integer | Field number; see annex B |
+
+Table 6.6.7.3: Response message parameters and format for Get Device Data
+
+| Number | Length      | Type        | Description    |
+|--------|-------------|-------------|----------------|
+| 1      | 1 octet     | ReturnCode  | Return code OK |
+| 2      | See annex B | See annex B | Field value    |
+
+#### Description:
+
+In this procedure the secondary device shall return the data stored in the field for configuration data specified by the field number in the procedure and listed in annex B of this TS.
+
+Table 6.6.7.4: Return codes for Get Device Data
+
+| OK | FAIL                                                              | Comment |
+|----|-------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>UnknownParameter |         |
+
+## 6.7 Multi-antenna elementary procedures
+
+### 6.7.1 Antenna Calibrate
+
+**Table 6.7.1.1: Elementary procedure Antenna Calibrate**
+
+|                                  |                                     |                              |                                  |                            |
+|----------------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------|
+| Name:<br><b>AntennaCalibrate</b> |                                     |                              |                                  |                            |
+| Code:<br><b>0x80</b>             | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>High</b> |
+
+Table 6.7.1.2: Initiating message parameters and format for Antenna Calibrate
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+
+Table 6.7.1.3: Response message parameters and format for Antenna Calibrate
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall perform a calibration of the antenna addressed by the antenna number. During calibration the actuator is driven through the whole tilt range of the antenna.
+
+The response time to this Antenna Calibrate procedure shall be less than 4 minutes.
+
+Table 6.7.1.4: Return codes for Antenna Calibrate
+
+| OK | FAIL                                                                                                                               | Comment                                                            |
+|----|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>MotorJam<br>ActuatorJam<br>NotConfigured<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.2 Antenna Set Tilt
+
+Table 6.7.2.1: Elementary procedure Antenna Set Tilt
+
+|                                |                                     |                              |                                  |                            |
+|--------------------------------|-------------------------------------|------------------------------|----------------------------------|----------------------------|
+| Name:<br><b>AntennaSetTilt</b> |                                     |                              |                                  |                            |
+| Code:<br><b>0x81</b>           | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>High</b> |
+
+Table 6.7.2.2: Initiating message parameters and format for Antenna Set Tilt
+
+| Number | Length   | Type             | Description    |
+|--------|----------|------------------|----------------|
+| 1      | 1 octet  | Unsigned integer | Antenna number |
+| 2      | 2 octets | Signed integer   | Tilt value     |
+
+Table 6.7.2.3: Response message parameters and format for Antenna Set Tilt
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall set the electrical tilt of the antenna addressed by the antenna number in increments of 0.1°.
+
+The secondary device shall respond to the initiating message in less than 2 minutes.
+
+The tilt value corresponding to the actual tilt angle shall not go outside of the range between the tilt value corresponding to the current tilt angle and the tilt value corresponding to the requested tilt angle by more than 5 during this operation.
+
+The format of the value of parameter 2 is given in subclause 3.1.
+
+Table 6.7.2.4: Return codes for Antenna Set Tilt
+
+| OK | FAIL                                                                                                                                                              | Comment                                                            |
+|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>MotorJam<br>ActuatorJam<br>NotConfigured<br>NotCalibrated<br>OutOfRange<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.3 Antenna Get Tilt
+
+**Table 6.7.3.1: Elementary procedure Antenna Get Tilt**
+
+|                                |                                     |                              |                                  |                           |
+|--------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaGetTilt</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x82</b>           | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.3.2: Initiating message parameters and format for Antenna Get Tilt
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+
+Table 6.7.3.3: Response message parameters and format for Antenna Get Tilt
+
+| Number | Length   | Type             | Description    |
+|--------|----------|------------------|----------------|
+| 1      | 1 octet  | Unsigned integer | Antenna number |
+| 2      | 1 octet  | ReturnCode       | Return code OK |
+| 3      | 2 octets | Signed integer   | Tilt value     |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall return the current tilt value of the antenna addressed by the antenna number.
+
+The returned tilt value is in the format specified in subclause 3.1.
+
+Table 6.7.3.4: Return codes for Antenna Get Tilt
+
+| OK | FAIL                                                                                                                     | Comment                                                                                                                                           |
+|----|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>NotConfigured<br>NotCalibrated<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned.<br>HardwareError shall only be used, if an error is detected in tilt detector. |
+
+### 6.7.4 Antenna Set Device Data
+
+**Table 6.7.4.1: Elementary procedure Antenna Set Device Data**
+
+|                                      |                                     |                              |                                  |                           |
+|--------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaSetDeviceData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x83</b>                 | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.4.2: Initiating message parameters and format for Antenna Set Device Data
+
+| Number | Length      | Type             | Description               |
+|--------|-------------|------------------|---------------------------|
+| 1      | 1 octet     | Unsigned integer | Antenna number            |
+| 2      | 1 octet     | Unsigned integer | Field number; see annex B |
+| 3      | See annex B | See annex B      | Data to write             |
+
+Table 6.7.4.3: Response message parameters and format for Antenna Set Device Data
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall write the provided data for the antenna addressed by the antenna number into the fields optionally provided for configuration data and listed in annex B of this TS. If an attempt is made to write to fields which are designated as read only for the addressed antenna the return code ReadOnly is returned and the data for those fields is ignored. If an attempt is made to write to fields which are not supported for the addressed antenna the return code UnknownParameter is returned and the data for those fields is ignored.
+
+Table 6.7.4.4: Return codes for Antenna Set Device Data
+
+| OK | FAIL                                                                                                                   | Comment                                                            |
+|----|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>ReadOnly<br>UnknownParameter<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.5 Antenna Get Device Data
+
+Table 6.7.5.1: Elementary procedure Antenna Get Device Data
+
+|                                      |                                     |                              |                                  |                           |
+|--------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaGetDeviceData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x84</b>                 | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.5.2: Initiating message parameters and format for Antenna Get Device Data
+
+| Number | Length  | Type             | Description                       |
+|--------|---------|------------------|-----------------------------------|
+| 1      | 1 octet | Unsigned integer | Antenna number                    |
+| 2      | 1 octet | Unsigned integer | Field number to read; see annex B |
+
+Table 6.7.5.3: Response message parameters and format for Antenna Get Device Data
+
+| Number | Length      | Type             | Description    |
+|--------|-------------|------------------|----------------|
+| 1      | 1 octet     | Unsigned integer | Antenna number |
+| 2      | 1 octet     | ReturnCode       | Return code OK |
+| 3      | See annex B | See annex B      | Field value    |
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall return the data stored for the addressed antenna in the field for configuration data specified by the field number in the initiating message and listed in annex B of this TS.
+
+Table 6.7.5.4: Return codes for Antenna Get Device Data
+
+| OK | FAIL                                                                                      | Comment                                                            |
+|----|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>UnsupportedProcedure<br>UnknownParameter | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.6 Antenna Alarm Indication
+
+Table 6.7.6.1: Elementary procedure Antenna Alarm Indication
+
+|                                        |                                       |                              |                                  |                           |
+|----------------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaAlarmIndication</b> |                                       |                              |                                  |                           |
+| Code:<br><b>0x85</b>                   | Issued by:<br><b>Secondary device</b> | Procedure class:<br><b>2</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.6.2: Initiating message parameters and format for Antenna Alarm Indication
+
+| Number | Length  | Type             | Description                |
+|--------|---------|------------------|----------------------------|
+| 1      | 1 octet | Unsigned integer | Antenna number             |
+| 2 i    | 1 octet | Unsigned integer | Return code i; see annex A |
+| 2 i +1 | 1 octet | Unsigned integer | State flag i               |
+
+i = 1 ... N
+
+#### Description:
+
+The multi-antenna secondary device uses this procedure to report antenna alarm state changes to the primary device. This procedure shall only be performed if the secondary has performed an AlarmSubscribe procedure since its latest reset. Multi-antenna devices shall use this AntennaAlarmIndication procedure only for multi-antenna specific alarms and the AlarmIndication procedure in subclause 6.6.5 for the other alarms.
+
+For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred during the period of time since the last reported state. An AntennaAlarmIndication procedure shall be performed if at least one multi-antenna specific alarm shall be reported. The first AntennaAlarmIndication procedure after the AlarmSubscribe procedure shall report the active alarms.
+
+Alarm state changes are considered as reported at the time the message is passed to the transport layer.
+
+State flag = 0 represents alarm state *cleared*.
+
+State flag = 1 represents alarm state *raised*.
+
+### 6.7.7 Antenna Clear Active Alarms
+
+Table 6.7.7.1: Elementary procedure Antenna Clear Active Alarms
+
+|                                          |                                       |                              |                                  |                           |
+|------------------------------------------|---------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaClearActiveAlarms</b> |                                       |                              |                                  |                           |
+| Code:<br><b>0x86</b>                     | Issued by:<br><b>Secondary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.7.2: Initiating message parameters and format for Antenna Clear Active Alarms
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+
+Table 6.7.7.3: Response message parameters and format for Antenna Clear Active Alarms
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall first clear all stored alarm information for the addressed antenna and then return a procedure response message.
+
+Table 6.7.7.4: Return codes for Antenna Clear Active Alarms
+
+| OK | FAIL                                                                  | Comment                                                            |
+|----|-----------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.8 Antenna Get Alarm Status
+
+Table 6.7.8.1: Elementary procedure Antenna Get Alarm Status
+
+|                                       |                                     |                              |                                  |                           |
+|---------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaGetAlarmStatus</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x87</b>                  | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.8.2: Initiating message parameters and format for Antenna Get Alarm Status
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+
+Table 6.7.8.3: Response message parameters and format for Antenna Get Alarm Status
+
+| Number | Length  | Type             | Description           |
+|--------|---------|------------------|-----------------------|
+| 1      | 1 octet | Unsigned integer | Antenna number        |
+| 2      | 1 octet | ReturnCode       | Return code OK        |
+| i + 2  | 1 octet | AlarmCode        | Active alarm number i |
+
+i = 1 ... N
+
+#### **Description:**
+
+On receipt of the initiating message the secondary device shall report the alarm codes of the active alarms for the addressed antenna.
+
+Table 6.7.8.4: Return codes for Antenna Get Alarm Status
+
+| OK                                                    | FAIL                                                          | Comment                                                            |
+|-------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------|
+| All return codes marked as used for alarms in Annex A | FormatError<br>WorkingSoftwareMissing<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+### 6.7.9 Antenna Get Number Of Antennas
+
+**Table 6.7.9.1: Elementary procedure Antenna Get Number Of Antennas**
+
+|                                            |                                     |                              |                                  |                           |
+|--------------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaGetNumberOfAntennas</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x88</b>                       | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.9.2: Initiating message parameters and format for Antenna Get Number Of Antennas
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+Table 6.7.9.3: Response message parameters and format for Antenna Get Number Of Antennas
+
+| Number | Length  | Type             | Description        |
+|--------|---------|------------------|--------------------|
+| 1      | 1 octet | ReturnCode       | Return code OK     |
+| 2      | 1 octet | Unsigned integer | Number of antennas |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall return the number of antennas it controls.
+
+Table 6.7.9.4: Return codes for Antenna Get Number Of Antennas
+
+| OK | FAIL                                                          | Comment |
+|----|---------------------------------------------------------------|---------|
+|    | FormatError<br>WorkingSoftwareMissing<br>UnsupportedProcedure |         |
+
+### 6.7.10 Antenna Send Configuration Data
+
+**Table 6.7.10.1: Elementary procedure Antenna Send Configuration Data**
+
+|                                              |                                     |                              |                                  |                           |
+|----------------------------------------------|-------------------------------------|------------------------------|----------------------------------|---------------------------|
+| Name:<br><b>AntennaSendConfigurationData</b> |                                     |                              |                                  |                           |
+| Code:<br><b>0x89</b>                         | Issued by:<br><b>Primary device</b> | Procedure class:<br><b>1</b> | DownloadMode state:<br><b>No</b> | Power mode:<br><b>Low</b> |
+
+Table 6.7.10.2: Initiating message parameters and format for Antenna Send Configuration Data
+
+| Number | Length                                                    | Type             | Description        |
+|--------|-----------------------------------------------------------|------------------|--------------------|
+| 1      | 1 octet                                                   | Unsigned Integer | Antenna number     |
+| 2      | Less than, or equal to<br>MaxDataReceiveLength<br>minus 1 | Vendor specific  | Configuration data |
+
+Table 6.7.10.3: Response message parameters and format for Antenna Send Configuration Data
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Antenna number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+#### Description:
+
+On receipt of the initiating message the secondary device shall store the provided vendor and antenna specific configuration data for the relationship between the movement of the drive system and the beam tilt position of the addressed antenna.
+
+If the configuration data exceeds MaxDataReceiveLength minus 1, the data shall be split into a number of MaxDataReceiveLength minus 1 segments and one final segment with whatever is left. The primary device transmits the segments in order. The layer 2 sequence numbers guarantee that no segment will be lost or received out of order.
+
+Table 6.7.10.4: Return codes for Antenna Send Configuration Data
+
+| OK | FAIL                                                                                                                          | Comment                                                            |
+|----|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>ChecksumError<br>InvalidFileContent<br>UnsupportedProcedure | If the addressed antenna is not existing, FormatError is returned. |
+
+## 6.8 TMAAP Elementary procedures for TMA
+
+### 6.8.1 TMA Set Mode
+
+The TMA Set Mode procedure shall only be supported if the TMA subunit can be set in bypass mode. On receipt of the initiating message, the secondary device shall first set the TMA subunit in the appropriate mode as indicated by the mode state flag, and then return a response message. If a TMA subunit in bypass mode receives the elementary procedure TMASetMode to Bypass, the TMA subunit shall remain in the Bypass mode and the response OK shall be returned.
+
+Mode state flag = 0 represents *Normal mode*.
+
+Mode state flag = 1 represents *Bypass mode*.
+
+Table 6.8.1.1: Elementary procedure TMA Set Mode
+
+| Name: TMA Set Mode |                |                  |                     |             |
+|--------------------|----------------|------------------|---------------------|-------------|
+| Code:              | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x70               | Primary device | 1                | No                  | n/a         |
+
+Table 6.8.1.2: Initiating message parameters and format TMA Set Mode
+
+| Number | Length  | Type             | Description     |
+|--------|---------|------------------|-----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number  |
+| 2      | 1 octet | Unsigned integer | Mode state flag |
+
+Table 6.8.1.3: Response message parameters and format for TMA Set Mode
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+**Table 6.8.1.4: Return codes for TMA Set Mode**
+
+| <b>OK</b> | <b>FAIL</b>            | <b>Comment</b>                                                                                                                                              |
+|-----------|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|           | FormatError            |                                                                                                                                                             |
+|           | Busy                   |                                                                                                                                                             |
+|           | HardwareError          | HardwareError shall refer to a detected inability to switch mode.                                                                                           |
+|           | WorkingSoftwareMissing |                                                                                                                                                             |
+|           | UnsupportedProcedure   | UnsupportedProcedure shall be returned if set mode is not supported by the TMA subunit.                                                                     |
+|           | OutOfRange             | OutOfRange shall be returned if the mode state flag has another value than those listed in the procedure description.                                       |
+|           | MajorTMAFault          | MajorTMAFault shall be returned if the TMA subunit is in bypass mode due to a major TMA fault and TMASetMode to Normal is received and not possible to set. |
+|           | MinorTMAFault          | MinorTMAFault shall be returned if the TMA subunit is in bypass mode due to a minor TMA fault and TMASetMode to Normal is received and not possible to set. |
+
+### 6.8.2 TMA Get Mode
+
+On receipt of the initiating message, the secondary device shall respond with the mode state flag indicating whether the TMA subunit is in normal mode or in bypass mode. TMA subunits which do not support bypass mode shall return Normal mode.
+
+Mode state flag = 0x00 represents *Normal mode*.
+
+Mode state flag = 0x01 represents *Bypass mode*.
+
+**Table 6.8.2.1: Elementary procedure TMA Get Mode**
+
+| Name: TMA Get Mode |                   |                         |                            |                    |
+|--------------------|-------------------|-------------------------|----------------------------|--------------------|
+| <b>Code:</b>       | <b>Issued by:</b> | <b>Procedure class:</b> | <b>DownloadMode state:</b> | <b>Power mode:</b> |
+| 0x71               | Primary device    | 1                       | No                         | n/a                |
+
+**Table 6.8.2.2: Initiating message parameters and format for TMA Get Mode**
+
+| <b>Number</b> | <b>Length</b> | <b>Type</b>      | <b>Description</b> |
+|---------------|---------------|------------------|--------------------|
+| 1             | 1 octet       | Unsigned integer | Subunit number     |
+
+**Table 6.8.2.3: Response message parameters and format for TMA Get Mode**
+
+| <b>Number</b> | <b>Length</b> | <b>Type</b>      | <b>Description</b> |
+|---------------|---------------|------------------|--------------------|
+| 1             | 1 octet       | Unsigned integer | Subunit number     |
+| 2             | 1 octet       | ReturnCode       | Return code OK     |
+| 3             | 1 octet       | Unsigned integer | Mode state flag    |
+
+**Table 6.8.2.4: Return codes TMA Get Mode**
+
+| <b>OK</b> | <b>FAIL</b>                                   | <b>Comment</b> |
+|-----------|-----------------------------------------------|----------------|
+|           | FormatError<br>Busy<br>WorkingSoftwareMissing |                |
+
+### 6.8.3 TMA Get Supported Functions
+
+On receipt of the initiating message, the secondary device shall respond with the function flags and parameters indicating the supported functionality of the addressed TMA subunit.
+
+**Table 6.8.3.1: Elementary procedure TMAGetSupportedFunctions**
+
+| Name: TMA Get Supported Functions |                |                  |                     |             |
+|-----------------------------------|----------------|------------------|---------------------|-------------|
+| Code:                             | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x7A                              | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.3.2: Initiating message parameters and format for TMAGetSupportedFunctions**
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+
+**Table 6.8.3.3: Response message parameters and format for TMAGetSupportedFunctions**
+
+| Number | Length  | Type             | Description                               |
+|--------|---------|------------------|-------------------------------------------|
+| 1      | 1 octet | Unsigned integer | Subunit number                            |
+| 2      | 1 octet | ReturnCode       | Return code OK                            |
+| 3      | 1 octet | Unsigned integer | Function flags                            |
+| 4      | 1 octet | Unsigned integer | Min Gain capability (expressed in dB/4)   |
+| 5      | 1 octet | Unsigned integer | Max Gain capability (expressed in dB/4)   |
+| 6      | 1 octet | Unsigned integer | Resolution capability (expressed in dB/4) |
+
+#### **Description:**
+
+1. A fixed gain TMA subunit shall have min and max gain as the same value.
+2. If the resolution is zero, then non linear gain steps are supported (e.g. 3dB and 6dB and 12dB).
+
+NOTE: These parameters represent absolute fixed physical data. Any change of the corresponding parameter in the additional data will not have any operational impact on the TMA.
+
+**Table 6.8.3.4: Return codes TMAGetSupportedFunctions**
+
+| OK | FAIL                                          | Comment |
+|----|-----------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+Function flags:
+
+| Bit      | 7 to 1 | 0           |
+|----------|--------|-------------|
+| Function | Spare  | Bypass Mode |
+
+- Bits are numbered from 0...7, bit number 0 set to 1 represents the value 0x01
+- Bit value 0 represents function is not supported
+- Bit value 1 represents function is supported
+- Spare bits shall be set to 0
+
+### 6.8.4 TMA Set Gain
+
+The procedure TMASetGain shall only be supported if the TMA subunit gain can be adjusted. On receipt of the initiating message, the secondary device shall first set the addressed TMA subunit to the gain determined by the TMA gain figure parameter, and then return the response message. The TMA gain figure parameter is calculated as 4 times the required gain expressed in dB. (This method of specification allows the gain to be set with a resolution of 0.25 dB while using an integer parameter.)
+
+If the TMA subunit is set in bypass mode by TMASetMode, and TMASetGain is received, then the procedure shall be performed and bypass mode shall be retained.
+
+If any alarm state flag is set then the status has to be validated and the result has to be responded.
+
+Gain shall be accepted if  $G_{min} \leq G_{demanded} \leq G_{max}$
+
+For linear steps:  $G_{demanded} = (G_{min} + n * G_{resolution})$  where n is a non-negative integer
+
+For non-linear steps:  $G_{demanded}$  must be equal to a supported value.
+
+$G_{min}$ ,  $G_{max}$  and  $G_{resolution}$  are reported by TMAGetSupportedFunctions. The supported values for non-linear steps are reported by TMAGetSupportedNonLinearGainValues.
+
+For all other values of  $G_{demanded}$ , the TMA subunit shall respond UnsupportedValue.
+
+**Table 6.8.4.1: Elementary procedure TMA Set Gain**
+
+| Name: TMA Set Gain |                |                  |                     |             |
+|--------------------|----------------|------------------|---------------------|-------------|
+| Code:              | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x72               | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.4.2: Initiating message parameters and format TMA Set Gain**
+
+| Number | Length  | Type             | Description     |
+|--------|---------|------------------|-----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number  |
+| 2      | 1 octet | Unsigned integer | TMA gain figure |
+
+**Table 6.8.4.3: Response message parameters and format for TMA Set Gain**
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+**Table 6.8.4.4: Return codes for TMA Set Gain**
+
+| OK | FAIL                   | Comment                                                                                                                                                |
+|----|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+|    | FormatError            |                                                                                                                                                        |
+|    | Busy                   |                                                                                                                                                        |
+|    | HardwareError          | HardwareError shall refer to the detected inability to set the gain according to the instruction, although it is within the TMA gain adjustment range. |
+|    | WorkingSoftwareMissing |                                                                                                                                                        |
+|    | UnsupportedProcedure   | UnsupportedProcedure shall be returned if gain adjustment is not supported by the TMA subunit.                                                         |
+|    | UnsupportedValue       | The requested value is not supported.                                                                                                                  |
+|    | MajorTMAFault          |                                                                                                                                                        |
+|    | MinorTMAFault          |                                                                                                                                                        |
+
+### 6.8.5 TMA Get Gain
+
+On receipt of the initiating message, the secondary device shall return the set gain of the TMA subunit. Fixed gain TMA subunits shall return their fixed gain value. The TMA gain figure is calculated as 4 times the set gain expressed in dB.
+
+**Table 6.8.5.1: Elementary procedure TMA Get Gain**
+
+| Name: TMA Get Gain |                |                  |                     |             |
+|--------------------|----------------|------------------|---------------------|-------------|
+| Code:              | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x73               | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.5.2: Initiating message parameters and format TMA Get Gain**
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+
+**Table 6.8.5.3: Response message parameters and format for TMA Get Gain**
+
+| Number | Length  | Type             | Description     |
+|--------|---------|------------------|-----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number  |
+| 2      | 1 octet | Return Code      | Return code OK  |
+| 3      | 1 octet | Unsigned integer | TMA gain figure |
+
+**Table 6.8.5.4: Return codes for TMA Get Gain**
+
+| OK | FAIL                   | Comment                                                                                          |
+|----|------------------------|--------------------------------------------------------------------------------------------------|
+|    | FormatError            |                                                                                                  |
+|    | Busy                   |                                                                                                  |
+|    | WorkingSoftwareMissing |                                                                                                  |
+|    | MajorTMAFault          |                                                                                                  |
+|    | MinorTMAFault          |                                                                                                  |
+|    | BypassMode             | BypassMode shall be returned if the TMA subunit is in bypass mode due to a TMASetMode procedure. |
+
+### 6.8.6 TMA Set Device Data
+
+On receipt of the initiating message the secondary device shall first write the provided data for the TMA subunit addressed by the subunit number into the fields provided for device data (and listed in Annex C of this document) and then return the response message. If an attempt is made to write to a field which is implemented as read only for the addressed TMA subunit, the return code *ReadOnly* is returned and the data for that field is ignored. If an attempt is made to write to a field which is not supported for the addressed TMA subunit the return code *UnknownParameter* is returned and the data for that field is ignored.
+
+**Table 6.8.6.1: Elementary procedure TMA Set Device Data**
+
+| Name: TMASetDeviceData |                |                  |                     |             |
+|------------------------|----------------|------------------|---------------------|-------------|
+| Code:                  | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x74                   | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.6.2: Initiating message parameters and format for TMA Set Device Data**
+
+| Number | Length      | Type             | Description               |
+|--------|-------------|------------------|---------------------------|
+| 1      | 1 octet     | Unsigned integer | Subunit number            |
+| 2      | 1 octet     | Unsigned integer | Field number; see annex C |
+| 3      | See annex C | See annex C      | Data to write             |
+
+Table 6.8.6.3: Response message parameters and format for TMA Set Device Data
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+Table 6.8.6.4: Return codes for TMA Set Device Data
+
+| OK | FAIL                                                                                           | Comment |
+|----|------------------------------------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>HardwareError<br>WorkingSoftwareMissing<br>ReadOnly<br>UnknownParameter |         |
+
+### 6.8.7 TMA Get Device Data
+
+On receipt of the initiating message the secondary device shall return the data stored for the addressed TMA subunit in the field for additional device data specified by the field number in the initiating message and listed in Annex C of this document.
+
+Table 6.8.7.1: Elementary procedure TMA Get Device Data
+
+| Name: TMAGetDeviceData |                |                  |                     |             |
+|------------------------|----------------|------------------|---------------------|-------------|
+| Code:                  | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x75                   | Primary device | 1                | No                  | n/a         |
+
+Table 6.8.7.2: Initiating message parameters and format for TMA Get Device Data
+
+| Number | Length  | Type             | Description                          |
+|--------|---------|------------------|--------------------------------------|
+| 1      | 1 octet | Unsigned integer | Subunit number                       |
+| 2      | 1 octet | Unsigned integer | Field number to be read; see Annex C |
+
+Table 6.8.7.3: Response message parameters and format for TMA Get Device Data
+
+| Number | Length      | Type             | Description    |
+|--------|-------------|------------------|----------------|
+| 1      | 1 octet     | Unsigned integer | Subunit number |
+| 2      | 1 octet     | Return Code      | Return code OK |
+| 3      | See Annex C | See Annex C      | Field value    |
+
+Table 6.8.7.4: Return codes for TMA Get Device Data
+
+| OK | FAIL                                                              | Comment |
+|----|-------------------------------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing<br>UnknownParameter |         |
+
+### 6.8.8 TMA Alarm Indication
+
+TMAs use this procedure to report TMA alarm state changes to the primary device. This procedure shall only be performed if the TMA has performed an AlarmSubscribe procedure since its latest reset.
+
+**Table 6.8.8.1: Elementary procedure TMA Alarm Indication**
+
+| Name: TMAAlarmIndication |                  |                  |                     |             |
+|--------------------------|------------------|------------------|---------------------|-------------|
+| Code:                    | Issued by:       | Procedure class: | DownloadMode state: | Power mode: |
+| 0x76                     | Secondary device | 2                | No                  | n/a         |
+
+Table 6.8.8.2: Initiating message parameters and format for TMA Alarm Indication
+
+| Number | Length  | Type             | Description                |
+|--------|---------|------------------|----------------------------|
+| 1      | 1 octet | Unsigned integer | Subunit number             |
+| 2* i   | 1 octet | Unsigned integer | Return code i; see Annex A |
+| 2*i +1 | 1 octet | Unsigned integer | State flag i               |
+
+i = 1 ... N
+
+#### 6.8.8.1 Further requirements
+
+For each alarm, the current alarm state and alarm code shall be reported if and only if any change in its state has occurred since the last reported state.
+
+A TMA Alarm Indication procedure shall be performed if at least one TMA alarm shall be reported for the TMA subunit. The first TMA Alarm Indication procedure after the Alarm Subscribe procedure shall report the active alarms.
+
+Alarm state changes are considered as reported at the time the message is passed to the transport layer.
+
+State flag = 0x00 represents alarm state *cleared*.
+
+State flag = 0x01 represents alarm state *raised*.
+
+### 6.8.9 TMA Clear Active Alarms
+
+On receipt of the initiating message the secondary device shall first clear all stored alarm information for the addressed TMA subunit and then return a procedure response message. In the event that the cause of the alarm persists the alarm shall be re-raised and a new TMA Alarm Indication procedure shall be performed.
+
+**Table 6.8.9.1: Elementary procedure TMA Clear Active Alarms**
+
+| Name: TMAClearActiveAlarms |                |                  |                     |             |
+|----------------------------|----------------|------------------|---------------------|-------------|
+| Code:                      | Issued by      | Procedure class: | DownloadMode state: | Power mode: |
+| 0x77                       | Primary device | 1                | No                  | n/a         |
+
+Table 6.8.9.2: Initiating message parameters and format for TMA Clear Active Alarms
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+
+Table 6.8.9.3: Response message parameters and format for TMA Clear Active Alarms
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+| 2      | 1 octet | ReturnCode       | Return code OK |
+
+Table 6.8.9.4: Return codes for TMA Clear Active Alarms
+
+| OK | FAIL                                          | Comment |
+|----|-----------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+### 6.8.10 TMA Get Alarm Status
+
+On receipt of the initiating message the secondary device shall report the alarm codes of the active alarms for the addressed TMA subunit.
+
+**Table 6.8.10.1: Elementary procedure TMA Get Alarm Status**
+
+| Name: TMAGetAlarmStatus |                |                  |                     |             |
+|-------------------------|----------------|------------------|---------------------|-------------|
+| Code:                   | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x78                    | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.10.2: Initiating message parameters and format for TMA Get Alarm Status**
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+
+**Table 6.8.10.3: Response message parameters and format for TMA Get Alarm Status**
+
+| Number | Length  | Type             | Description                   |
+|--------|---------|------------------|-------------------------------|
+| 1      | 1 octet | Unsigned integer | Subunit number                |
+| 2      | 1 octet | ReturnCode       | Return code OK                |
+| 2 + i  | 1 octet | AlarmCode        | Alarm code for alarm number i |
+
+i = 1 ... N
+
+**Table 6.8.10.4: Return codes for TMA Get Alarm Status**
+
+| OK                                                    | FAIL                                          | Comment |
+|-------------------------------------------------------|-----------------------------------------------|---------|
+| All return codes marked as used for alarms in Annex A | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+### 6.8.11 TMA Get Number of Subunits
+
+On receipt of the initiating message the secondary device shall return the number of subunits it controls.
+
+**Table 6.8.11.1: Elementary procedure TMAGetNumberOfSubunits**
+
+| Name: TMAGetNumberOfSubunits |                |                  |                     |             |
+|------------------------------|----------------|------------------|---------------------|-------------|
+| Code:                        | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x79                         | Primary device | 1                | No                  | n/a         |
+
+**Table 6.8.11.2: Initiating message parameters and format for TMAGetNumberOfSubunits**
+
+| Number | Length   | Type | Description     |
+|--------|----------|------|-----------------|
+| None   | 0 octets | None | No data carried |
+
+**Table 6.8.11.3: Response message parameters and format for TMAGetNumberOfSubunits**
+
+| Number | Length  | Type             | Description        |
+|--------|---------|------------------|--------------------|
+| 1      | 1 octet | ReturnCode       | Return code OK     |
+| 2      | 1 octet | Unsigned integer | Number of subunits |
+
+Table 6.8.11.4: Return codes for TMAGetNumberOfSubunits
+
+| OK | FAIL                                          | Comment |
+|----|-----------------------------------------------|---------|
+|    | FormatError<br>Busy<br>WorkingSoftwareMissing |         |
+
+### 6.8.12 3GPP Clear Active Alarms and Get Alarm Status
+
+When an TMA receives ClearActiveAlarms, it shall perform the procedure for all subunits of the TMA and then return a single procedure response message.
+
+When an TMA receives GetAlarmStatus, it shall in a single procedure response message report the union of the alarm codes of all active alarms for all subunits, i.e. the same alarm codes shall be reported only once.
+
+### 6.8.13 TMA Get Supported Non-Linear Gain Values
+
+On receipt of the initiating message, the secondary device shall respond with a message containing a list of supported values in numerical order, preceded by the number (N) of such values contained in the list.
+
+Table 6.8.13.1: Elementary procedure TMAGetSupportedNonLinearGainValues
+
+| Name: TMAGetSupportedNonLinearGainValues |                |                  |                     |             |
+|------------------------------------------|----------------|------------------|---------------------|-------------|
+| Code:                                    | Issued by:     | Procedure class: | DownloadMode state: | Power mode: |
+| 0x7B                                     | Primary device | 1                | No                  | n/a         |
+
+Table 6.8.13.2: Initiating message parameters and format for TMAGetSupportedNonLinearGainValues
+
+| Number | Length  | Type             | Description    |
+|--------|---------|------------------|----------------|
+| 1      | 1 octet | Unsigned integer | Subunit number |
+
+Table 6.8.13.3: Response message parameters and format for TMAGetSupportedNonLinearGainValues
+
+| Number | Length  | Type             | Description                                                  |
+|--------|---------|------------------|--------------------------------------------------------------|
+| 1      | 1 octet | Unsigned integer | Subunit number                                               |
+| 2      | 1 octet | ReturnCode       | Return code OK                                               |
+| 3      | 1 octet | Unsigned integer | Number of non linear gain values supported (N)               |
+| 3 + i  | 1 octet | Unsigned integer | Non linear gain supported value number i (expressed in dB/4) |
+
+i=1 .. N
+
+Table 6.8.13.4: Return codes TMAGetSupportedNonLinearGainValues
+
+| OK | FAIL                   | Comment                                                                                  |
+|----|------------------------|------------------------------------------------------------------------------------------|
+|    | FormatError            |                                                                                          |
+|    | Busy                   |                                                                                          |
+|    | WorkingSoftwareMissing |                                                                                          |
+|    | UnsupportedProcedure   | UnsupportedProcedure shall be returned if the TMA does not support non-linear gain steps |
+
+# --- 7 Unknown elementary procedures
+
+Void.
+
+# Annex A (normative): Return codes for secondary devices
+
+**Table A.1: Return Codes for Secondary Devices**
+
+| Code | Name                     | Comment                                                                                                                                                                           | Alarm | DownloadMode state |
+|------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------------------|
+| 0x00 | OK                       | Normal response                                                                                                                                                                   |       | X                  |
+| 0x02 | Motor Jam                | Motor cannot move                                                                                                                                                                 | X     |                    |
+| 0x03 | ActuatorJam              | Actuator jam has been detected. No movement of the actuator, but movement of the motor was detected                                                                               | X     |                    |
+| 0x05 | Busy                     | The device is busy and cannot execute the procedure until an ongoing activity is completed                                                                                        |       |                    |
+| 0x06 | ChecksumError            | Checksum incorrect for otherwise valid data..                                                                                                                                     |       |                    |
+| 0x0B | FAIL                     | Abnormal response. Indicates that a procedure has not been executed successfully                                                                                                  |       | X                  |
+| 0x0E | NotCalibrated            | The device has not completed a calibration operation, or calibration has been lost                                                                                                | X     |                    |
+| 0x0F | NotConfigured            | Actuator configuration data is missing                                                                                                                                            | X     |                    |
+| 0x11 | HardwareError            | Any hardware error which cannot be classified. May not be reported as an alarm until the fault is likely to be persistent                                                         | X     | X                  |
+| 0x13 | OutOfRange               | A parameter given by an operator (e.g. tilt value or memory offset) is out of range                                                                                               |       |                    |
+| 0x19 | UnknownProcedure         | Received procedure code is not defined                                                                                                                                            |       | X                  |
+| 0x1D | ReadOnly                 | Invalid device data parameter usage                                                                                                                                               |       | X                  |
+| 0x1E | UnknownParameter         | Specified parameter is not supported for the used procedure                                                                                                                       |       | X                  |
+| 0x21 | WorkingSoftwareMissing   | The unit is inDownloadMode state. Returned upon unsupported procedure when in DownloadMode state                                                                                  |       | X                  |
+| 0x22 | InvalidFileContent       | The data being downloaded is detected to be of wrong format or size                                                                                                               |       | X                  |
+| 0x24 | FormatError              | Procedure message is inconsistent or if an addressed field or antenna is invalid or the data parameter field length is inconsistent with the corresponding field length parameter |       | X                  |
+| 0x25 | UnsupportedProcedure     | The procedure is optional and not supported or the procedure does not apply to this device type                                                                                   |       |                    |
+| 0x26 | InvalidProcedureSequence | Procedure sequence as described in annex C is expected but not experienced by the secondary device                                                                                |       |                    |
+| 0x27 | ActuatorInterference     | An actuator movement outside the control of the RET unit has been detected. Probable cause is manual interference                                                                 | X     |                    |
+| 0x1A | MinorTMAFault            | A fault in the TMA subunit is detected which reduces the gain performance but maintains its function.                                                                             | x     |                    |
+| 0x1B | MajorTMAFault            | A fault in the TMA subunit is detected. The fault prevents the function of the TMA subunit.                                                                                       | x     |                    |
+| 0x1C | UnsupportedValue         | The requested value is not supported.                                                                                                                                             |       |                    |
+| 0x1F | BypassMode               | The TMA subunit is in bypass mode and cannot report a correct gain value.                                                                                                         | x     |                    |
+
+NOTE: A TMA subunit with a fault which is causing it to switch to bypass mode will report both the fault and the BypassMode alarm.
+
+# Annex B (normative): Assigned fields for additional data
+
+The following standard fields have no operational impact and are used by the procedures SetDeviceData, GetDeviceData, AntennaSetDeviceData and AntennaGetDeviceData. Little endian order is used for storage of multiple-octet numbers. Where ASCII variables are shorter than the assigned field lengths the characters are right aligned and leading blanks are filled with null characters (0x00). Unused or not initialized parameter shall return the value 0x00 for the GetDeviceData, AntennaGetDeviceData and TMAGetDeviceData procedure.
+
+**Table B.1: Assigned fields for additional data of RETAP**
+
+| Field No. | Length (octets) | Format              | Description                                                                                                                                                                                                      |
+|-----------|-----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0x01      | 15              | ASCII               | Antenna model number                                                                                                                                                                                             |
+| 0x02      | 17              | ASCII               | Antenna serial number                                                                                                                                                                                            |
+| 0x03      | 2               | 16-bit unsigned     | Antenna operating band(s): Not supported in this release                                                                                                                                                         |
+| 0x08      | 2               | 16-bit unsigned     | Antenna operating band(s): Not supported in this release                                                                                                                                                         |
+| 0x09      | 2               | 16-bit unsigned     | Antenna operating band(s): Not supported in this release                                                                                                                                                         |
+| 0x0A      | 2               | 16-bit unsigned     | Antenna operating band(s): Not supported in this release                                                                                                                                                         |
+| 0x0B      | 2               | 16-bit unsigned     | Antenna operating band(s): Not supported in this release                                                                                                                                                         |
+| 0x04      | 8               | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg), beginning with lowest band. The lowest band is transmitted within the first 16-bit value.<br>Not supported in this release                                |
+| 0x05      | 4               | 4 x 8-bit unsigned  | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value<br>Not supported in this release |
+| 0x06      | 2               | 16-bit signed       | Maximum supported electrical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1                                                                                                         |
+| 0x07      | 2               | 16-bit signed       | Minimum supported electrical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1                                                                                                         |
+| 0x21      | 6               | ASCII               | Installation date                                                                                                                                                                                                |
+| 0x22      | 5               | ASCII               | Installer's ID                                                                                                                                                                                                   |
+| 0x23      | 32              | ASCII               | Base station ID                                                                                                                                                                                                  |
+| 0x24      | 32              | ASCII               | Sector ID                                                                                                                                                                                                        |
+| 0x25      | 2               | 16-bit unsigned     | Antenna bearing [degree], in the range of 0 – 359,9 degree, expressed as bearing value times 10                                                                                                                  |
+| 0x26      | 2               | 16-bit signed       | Installed mechanical tilt [degree], expressed in tilt value times 10, format as in subclause 3.1                                                                                                                 |
+
+**Table B.2: Void**
+
+**Table B.2-1: Void**
+
+**Table B.2-2: Void**
+
+**Table B.2-3: Void**
+
+**Table B.2-4: Void**
+
+The operating bands are defined in subclause 4.3.7 in TS 37.461 [4], an example of operating bands coding is provided in Annex F.
+
+**Table B.3: Assigned fields for additional data of TMAAP**
+
+| Field No. | Length (octets) | Format                    | Description                                                                                                                                                                                                    |
+|-----------|-----------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0x01      | 15              | ASCII                     | Antenna model number                                                                                                                                                                                           |
+| 0x02      | 17              | ASCII                     | Antenna serial number                                                                                                                                                                                          |
+| 0x03      | 2               | 16-bit unsigned           | Antenna operating band(s): Not supported in this release                                                                                                                                                       |
+| 0x08      | 2               | 16-bit unsigned           | Antenna operating band(s): Not supported in this release                                                                                                                                                       |
+| 0x09      | 2               | 16-bit unsigned           | Antenna operating band(s): Not supported in this release                                                                                                                                                       |
+| 0x0A      | 2               | 16-bit unsigned           | Antenna operating band(s): Not supported in this release                                                                                                                                                       |
+| 0x0B      | 2               | 16-bit unsigned           | Antenna operating band(s): Not supported in this release                                                                                                                                                       |
+| 0x04      | 8               | 4 x 16-bit unsigned       | Beamwidth for each operating band in band order (deg) beginning with lowest band. The lowest band is transmitted within the first 16-bit value. Not supported in this release                                  |
+| 0x05      | 4               | 4 x 8-bit unsigned        | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value. Not supported in this release |
+| 0x21      | 6               | ASCII                     | Installation date                                                                                                                                                                                              |
+| 0x22      | 5               | ASCII                     | Installer's ID                                                                                                                                                                                                 |
+| 0x23      | 32              | ASCII                     | Base station ID                                                                                                                                                                                                |
+| 0x24      | 32              | ASCII                     | Sector ID                                                                                                                                                                                                      |
+| 0x25      | 2               | 16-bit unsigned           | Antenna bearing                                                                                                                                                                                                |
+| 0x26      | 2               | 16-bit signed             | Installed mechanical tilt (degrees * 10)                                                                                                                                                                       |
+| 0x13      | 1               | 8-bit unsigned            | TMA subunit type (see table B.4)                                                                                                                                                                               |
+| 0x14      | 4               | 2x16-bit unsigned integer | TMA subunit receive frequency band (see Table B.5)                                                                                                                                                             |
+| 0x15      | 4               | 2x16-bit unsigned integer | TMA subunit transmit frequency band (see Table B.5)                                                                                                                                                            |
+| 0x16      | 1               | Unsigned integer          | Maximum supported gain given as gain figure expressed in dB/4                                                                                                                                                  |
+| 0x17      | 1               | Unsigned integer          | Minimum supported gain given as gain figure expressed in dB/4                                                                                                                                                  |
+| 0x18      | 1               | Unsigned integer          | Gain resolution given as the gain resolution figure expressed in dB/4                                                                                                                                          |
+
+**Table B.4: Field 0x13 interpretation**
+
+| Bit number       | 7... 2 | 1                     | 0      |
+|------------------|--------|-----------------------|--------|
+| TMA subunit type | Spare  | Reserved for AISG use | Bypass |
+
+Bits are numbered from 0...7, bit numbered 0 set to 1 represents the value 0x01.
+
+Bit value 0 represents TMA subunit type is not supported.
+
+Bit value 1 represents TMA subunit type is supported.
+
+Spare bits and Bit 1 shall be set to 0.
+
+Example: 0000 0001 = Bypass
+
+**Table B.5: Field 0x14 and 0x15 interpretation**
+
+| Octet number | Description     |
+|--------------|-----------------|
+| 0            | fmin low octet  |
+| 1            | fmin high octet |
+| 2            | fmax low octet  |
+| 3            | fmax high octet |
+
+fmin and fmax are expressed in 100kHz steps from 0kHz.
+
+Example: For 850MHz, low octet = 0x34, high octet = 0x21.
+
+# Annex C (normative): Procedure sequence for download of software to a secondary device
+
+![Sequence diagram showing the procedure for software download between a Primary Device and a Secondary Device.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg)
+
+```
+sequenceDiagram
+    participant Primary Device
+    participant Secondary Device
+    Note left of Primary Device: Repeat until all application software is downloaded
+    Primary Device->>Secondary Device: DownloadStart
+    Secondary Device-->>Primary Device: Response: DownloadStart
+    Primary Device->>Secondary Device: DownloadApplication
+    Secondary Device-->>Primary Device: Response: DownloadApplication
+    Primary Device->>Secondary Device: DownloadEnd
+    Secondary Device-->>Primary Device: Response: DownloadEnd
+```
+
+The diagram illustrates a sequence of messages between a Primary Device and a Secondary Device for a software download. The sequence starts with the Primary Device sending a **DownloadStart** message to the Secondary Device. The Secondary Device responds with **Response: DownloadStart**. Next, the Primary Device sends a **DownloadApplication** message, which is responded to by **Response: DownloadApplication**. A loop indicated by a box labeled "Repeat until all application software is downloaded" surrounds these two messages. Finally, the Primary Device sends a **DownloadEnd** message, which is responded to by **Response: DownloadEnd**.
+
+Sequence diagram showing the procedure for software download between a Primary Device and a Secondary Device.
+
+**Figure C.1: Procedure sequence for Software Download**
+
+The erasure of the secondary device application software shall not be done before the reception of the Download Application message. The data content of the Download Application message is implementation specific but it is recommended to support an application software validity feature that shall minimise the risk of downloading faulty or invalid application software.
+
+# Annex D (informative): Overview of elementary procedures
+
+**Table D.1: Elementary Procedures and Procedure Codes**
+
+| Elementary Procedure                                | Procedure Code | Issued by        | DownloadMode state |
+|-----------------------------------------------------|----------------|------------------|--------------------|
+| <u>Common Procedure Set</u>                         |                |                  |                    |
+| (Reserved)                                          | 0x01           |                  |                    |
+| Reset Software                                      | 0x03           | primary device   | Yes                |
+| Get Alarm Status                                    | 0x04           | primary device   | No                 |
+| Get Information                                     | 0x05           | primary device   | Yes                |
+| Clear Active Alarms                                 | 0x06           | primary device   | No                 |
+| Read User Data                                      | 0x10           | primary device   | No                 |
+| Write User Data                                     | 0x11           | primary device   | No                 |
+| Alarm Subscribe                                     | 0x12           | primary device   | No                 |
+| Self Test                                           | 0x0A           | primary device   | No                 |
+| Download Start                                      | 0x40           | primary device   | Yes                |
+| Download Application                                | 0x41           | primary device   | Yes                |
+| Download End                                        | 0x42           | primary device   | Yes                |
+| Vendor Specific Procedure                           | 0x90           | primary device   | Vendor specific    |
+| <u>RETAP Single-Antenna Procedure Set</u>           |                |                  |                    |
+| Set Device Data                                     | 0x0E           | primary device   | No                 |
+| Get Device Data                                     | 0x0F           | primary device   | No                 |
+| Calibrate                                           | 0x31           | primary device   | No                 |
+| Send Configuration Data                             | 0x32           | primary device   | No                 |
+| Set Tilt                                            | 0x33           | primary device   | No                 |
+| Get Tilt                                            | 0x34           | primary device   | No                 |
+| Alarm Indication                                    | 0x07           | secondary device | No                 |
+| <u>RETAP Multi-Antenna Procedure Set</u>            |                |                  |                    |
+| Antenna Calibrate                                   | 0x80           | primary device   | No                 |
+| Antenna Send Configuration Data                     | 0x89           | primary device   | No                 |
+| Antenna Set Tilt                                    | 0x81           | primary device   | No                 |
+| Antenna Get Tilt                                    | 0x82           | primary device   | No                 |
+| Antenna Set Device Data                             | 0x83           | primary device   | No                 |
+| Antenna Get Device Data                             | 0x84           | primary device   | No                 |
+| Antenna Alarm Indication                            | 0x85           | secondary device | No                 |
+| Antenna Clear Active Alarms                         | 0x86           | primary device   | No                 |
+| Antenna Get Alarm Status                            | 0x87           | primary device   | No                 |
+| Antenna Get Number of Antennas                      | 0x88           | primary device   | No                 |
+| <u>TMAAP Procedure Set for multi and single TMA</u> |                |                  |                    |
+| TMASetMode                                          | 0x70           | primary device   | No                 |
+| TMAGetMode                                          | 0x71           | primary device   | No                 |
+| TMAGetSupportedFunctions                            | 0x7A           | primary device   | No                 |
+| TMASetGain                                          | 0x72           | primary device   | No                 |
+| TMAGetGain                                          | 0x73           | primary device   | No                 |
+| TMASetDeviceData                                    | 0x74           | primary device   | No                 |
+| TMAGetDeviceData                                    | 0x75           | primary device   | No                 |
+| TMAAlarmIndication                                  | 0x76           | secondary device | No                 |
+| TMAClearActiveAlarms                                | 0x77           | primary device   | No                 |
+| TMAGetAlarmStatus                                   | 0x78           | primary device   | No                 |
+| TMAGetNumberOfSubunits                              | 0x79           | primary device   | No                 |
+| TMAGetSupportedNonLinearGainValues                  | 0x7B           | primary device   | No                 |
+
+NOTE: The notion "yes" in the DownloadMode state column indicates that the listed procedures are mandatory if the DownloadMode state can be entered by the secondary device.
+
+# Annex E (informative): I-frame and INFO-field format
+
+The I-frame and INFO-field formats for both primary and secondary stations are illustrated. To transfer elementary procedures, the INFO-field of the I-frame is used.
+
+**Table E.1: HDLC-Frame:**
+
+| Flag<br>1 octet | ADR<br>1 octet | Control<br>1 octet | INFO<br>N octets                                                         | CRC<br>2 octets   |                    | Flag<br>1 octet |
+|-----------------|----------------|--------------------|--------------------------------------------------------------------------|-------------------|--------------------|-----------------|
+| 0x7E            | Device Address | Control bits       | Variable length<br>(must support a maximum length of at least 74 octets) | CRC1<br>Low Octet | CRC2<br>high octet | 0x7E            |
+
+![Diagram showing the INFO field structure with dashed lines connecting the INFO field in the HDLC-Frame table to this table.](bf862ae9378286aa6f9daa4346e7ed8d_img.jpg)
+
+| Procedure ID | Number of data octets |            | Data octets                                                              |
+|--------------|-----------------------|------------|--------------------------------------------------------------------------|
+| 1 octet      | low octet             | high octet | Variable length<br>(must support a maximum length of at least 71 octets) |
+
+## Format of the I-Frame and INFO Field
+
+Devices shall support the following data length:
+
+Mandatory:  $0 \leq \text{data octets} \leq 71$
+
+Optional:  $0 \leq \text{data octets} < 65,536$  octets
+
+# Annex F (Informative): Assigned fields for additional data coding for operating bands
+
+NOTE: This Annex is not updated in Rel-16 and onwards.
+
+**Table F.1: Band related fields for additional data of RETAP**
+
+| Field No. | Length (octets) | Format              | Description                                                                                                                                                                                                                       |
+|-----------|-----------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0x03      | 2               | 16-bit unsigned     | Antenna operating band(s): see Table F.2 below                                                                                                                                                                                    |
+| 0x08      | 2               | 16-bit unsigned     | Antenna operating band(s): see Table F.2-1 below                                                                                                                                                                                  |
+| 0x09      | 2               | 16-bit unsigned     | Antenna operating band(s): see Table F.2-2 below                                                                                                                                                                                  |
+| 0x0A      | 2               | 16-bit unsigned     | Antenna operating band(s): see Table F.2-3 below                                                                                                                                                                                  |
+| 0x0B      | 2               | 16-bit unsigned     | Antenna operating band(s): see Table F.2-4 below                                                                                                                                                                                  |
+| 0x04      | 8               | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg), beginning with lowest band. The lowest band is transmitted within the first 16-bit value.<br>(example: width for band I, width for band III)                               |
+| 0x05      | 4               | 4 x 8-bit unsigned  | Gain [dBi] for each operating band in band order , expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value<br>(example: gain for band I, gain for band III) |
+
+**Table F.2: Coding for operating bands in field 0x03**
+
+| Bit no                | 15      | 14      | 13  | 12   | 11  | 10 | 9  | 8  | 7    | 6   | 5 | 4  | 3   | 2  | 1 | 0  |
+|-----------------------|---------|---------|-----|------|-----|----|----|----|------|-----|---|----|-----|----|---|----|
+| Operating band UTRA   | Ext. 09 | Ext. 08 | XIV | XIII | XII | XI | X  | IX | VIII | VII | I | II | III | IV | V | VI |
+| Operating band E-UTRA | Ext. 09 | Ext. 08 | 14  | 13   | 12  | 11 | 10 | 9  | 8    | 7   | 1 | 2  | 3   | 4  | 5 | 6  |
+
+Bit 14 set to "1" indicates that field 0x08 is defined.
+
+Bit 15 set to "1" indicates that field 0x09 is defined.
+
+**Table F.2-1: Coding for operating bands in field 0x08**
+
+| Bit no                | 15 | 14 | 13 | 12 | 11   | 10  | 9  | 8  | 7    | 6   | 5  | 4   | 3     | 2    | 1    | 0    |
+|-----------------------|----|----|----|----|------|-----|----|----|------|-----|----|-----|-------|------|------|------|
+| Operating band UTRA   | -  | -  | -  | -  | XXVI | XXV | -  | -  | XXII | XXI | XX | XIX | XVIII | XVII | Res. | Res. |
+| Operating band E-UTRA | 30 | 29 | 28 | 27 | 26   | 25  | 24 | 23 | 22   | 21  | 20 | 19  | 18    | 17   | Res. | Res. |
+
+**Table F.2-2: Coding for operating bands in field 0x09**
+
+| Bit no                | 15     | 14 | 13    | 12 | 11 | 10 | 9  | 8  | 7  | 6  | 5  | 4  | 3    | 2    | 1    | 0    |
+|-----------------------|--------|----|-------|----|----|----|----|----|----|----|----|----|------|------|------|------|
+| Operating band UTRA   | Ext 0A | -  | XXXII | -  | -  | -  | -  | -  | e  | f  | d  | c  | b)36 | b)35 | a)34 | a)33 |
+| Operating band E-UTRA | Ext 0A | 65 | 32    | 31 | 44 | 43 | 42 | 41 | 40 | 39 | 38 | 37 | 36   | 35   | 34   | 33   |
+
+Bit 15 set to "1" indicates that field 0x0A is defined.
+
+**Table F.2-3: Coding for operating bands in field 0x0A**
+
+| Bit no                | 15     | 14 | 13 | 12 | 11 | 10 | 9  | 8  | 7  | 6  | 5  | 4  | 3  | 2  | 1  | 0  |
+|-----------------------|--------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|
+| Operating band UTRA   | Ext 0B | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  | -  |
+| Operating band E-UTRA | Ext 0B | 75 | 74 | 72 | 71 | 49 | 51 | 50 | 48 | 69 | 70 | 46 | 68 | 45 | 67 | 66 |
+
+Bit 15 set to "1" indicates that field 0x0B is defined.
+
+**Table F.2-4: Coding for operating bands in field 0x0B**
+
+| Bit no                | 15   | 14     | 13     | 12     | 11     | 10     | 9      | 8      | 7      | 6      | 5      | 4      | 3  | 2  | 1  | 0  |
+|-----------------------|------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|----|----|----|----|
+| Operating band UTRA   | Res. | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | -  | -  | -  | -  |
+| Operating band E-UTRA | Res. | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | Spar e | 85 | 52 | 73 | 76 |
+
+The operating bands are defined in subclause 4.3.7 in TS 37.461 [4]. In Table F.2-2, the notation a)33 is equivalent to E-UTRA band 33.
+
+Bits are numbered from 0 to 15, bit no 0 set=1 represents the value 0x0001.
+
+Bit set=1 represents operating band is supported.
+
+Bit set=0 represents operating band is not supported.
+
+Spare bits shall be set=0.
+
+Unused Beamwidth and Gain octets shall be set to 0x0000.
+
+Examples of operating bands: 0000 0000 0001 0000 = Operating band II
+
+0000 0000 0011 1000 = Operating band I, II and III
+
+**Table F.3: Band related fields for additional data of TMAAP**
+
+| <b>Field No.</b> | <b>Length (octets)</b> | <b>Format</b>       | <b>Description</b>                                                                                                                                                                                                            |
+|------------------|------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0x03             | 2                      | 16-bit unsigned     | Antenna operating band(s): see Table F.2 above                                                                                                                                                                                |
+| 0x08             | 2                      | 16-bit unsigned     | Antenna operating band(s): see Table F.2-1 above                                                                                                                                                                              |
+| 0x09             | 2                      | 16-bit unsigned     | Antenna operating band(s): see Table F.2-2 above                                                                                                                                                                              |
+| 0x0A             | 2                      | 16-bit unsigned     | Antenna operating band(s): see Table F.2-3 above                                                                                                                                                                              |
+| 0x0B             | 2                      | 16-bit unsigned     | Antenna operating band(s): see Table F.2-4 above                                                                                                                                                                              |
+| 0x04             | 8                      | 4 x 16-bit unsigned | Beamwidth for each operating band in band order (deg) beginning with lowest band. The lowest band is transmitted within the first 16-bit value.                                                                               |
+| 0x05             | 4                      | 4 x 8-bit unsigned  | Gain [dBi] for each operating band in band order, expressed in gain value times 10, beginning with the lowest band. The lowest band is transmitted within the first 8-bit value (example: gain for band I, gain for band III) |
+
+# --- Annex G (informative): Change History
+
+| Change history |                         |           |      |     |     |                                                                     |             |
+|----------------|-------------------------|-----------|------|-----|-----|---------------------------------------------------------------------|-------------|
+| Date           | Meeting                 | TDoc      | CR   | Rev | Cat | Subject/Comment                                                     | New version |
+| 2019-02        | R3-103                  | R3-190103 |      |     |     | Text transferred from 25.466 v15.3.0 (changes shown with rev marks) | 1.15.0      |
+| 2019-04        | RAN#83                  | RP-190606 |      |     |     | Specification approved by RAN plenary                               | 15.4.0      |
+| 2019-12        | RP-86                   | RP-192915 | 0001 | 5   | F   | Correction for luant                                                | 15.5.0      |
+| 2020-07        | <a href="#">SA#88-e</a> | -         | -    | -   | -   | Update to Rel-16 version (MCC)                                      | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37470/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37470/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c7f509ce3f085cdeb2789f7ca44f41f983b5dbc
--- /dev/null
+++ b/marked/Rel-16/37_series/37470/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e9a5ab23be1ef6c9f881daad437d0b75b78458681b4b76a111a804e60b92388
+size 9284
diff --git a/marked/Rel-16/37_series/37470/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37470/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75c42d7c11c8998deabe996404ae0a9606a484dc
--- /dev/null
+++ b/marked/Rel-16/37_series/37470/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:468137148f5fedf1a756cb4c2414909a33dfb8c8680d5b3815b36f47bb3b91e2
+size 5780
diff --git a/marked/Rel-16/37_series/37470/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/37_series/37470/7f17c430b9598e4d748a8041457810b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c836eb49ba57f4f5f4d811d09c0229dd7ab1afe4
--- /dev/null
+++ b/marked/Rel-16/37_series/37470/7f17c430b9598e4d748a8041457810b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4568b087ca216792bb09ea84054e54cef0d3973e7d227afd9621b53f4c412f48
+size 23071
diff --git a/marked/Rel-16/37_series/37470/d0c9888da9078a08d93712fd0e113a88_img.jpg b/marked/Rel-16/37_series/37470/d0c9888da9078a08d93712fd0e113a88_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6112a464eef615e31608d4b594d53a53b7fc4f56
--- /dev/null
+++ b/marked/Rel-16/37_series/37470/d0c9888da9078a08d93712fd0e113a88_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:038960b0bde92bfb2b2e621baf7de2d8f4d9191cccf268355e753e81880139c8
+size 22062
diff --git a/marked/Rel-16/37_series/37470/raw.md b/marked/Rel-16/37_series/37470/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb989b96b2071d103d8ec7a0a45308451b34f08e
--- /dev/null
+++ b/marked/Rel-16/37_series/37470/raw.md
@@ -0,0 +1,481 @@
+
+
+# 3GPP TS 37.470 V16.2.0 (2020-07) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; General aspects and principles (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon below it. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                              |    |
+|------------------------------------------------------------------------------|----|
+| Foreword .....                                                               | 4  |
+| 1 Scope.....                                                                 | 6  |
+| 2 References.....                                                            | 6  |
+| 3 Definitions of terms, symbols and abbreviations .....                      | 6  |
+| 3.1 Terms.....                                                               | 6  |
+| 3.2 Symbols.....                                                             | 6  |
+| 3.3 Abbreviations .....                                                      | 7  |
+| 4 General aspects .....                                                      | 7  |
+| 4.0 General .....                                                            | 7  |
+| 4.1 W1 interface general principles.....                                     | 7  |
+| 4.2 W1 interface specification objectives .....                              | 8  |
+| 4.3 W1 interface capabilities.....                                           | 8  |
+| 4.4 W1 interface characteristics .....                                       | 8  |
+| 5 Functions of the W1 interface.....                                         | 8  |
+| 5.1 General .....                                                            | 8  |
+| 5.2 W1-C functions .....                                                     | 8  |
+| 5.2.1 Interface management function .....                                    | 8  |
+| 5.2.2 System Information management function .....                           | 9  |
+| 5.2.3 Paging function.....                                                   | 9  |
+| 5.2.4 UE context management function .....                                   | 9  |
+| 5.2.5 RRC message transfer function .....                                    | 10 |
+| 5.2.6 Warning messages information transfer function.....                    | 10 |
+| 5.3 W1-U functions.....                                                      | 10 |
+| 5.3.1 Transfer of user data.....                                             | 10 |
+| 5.3.2 Flow control function .....                                            | 10 |
+| 6 Procedures of the W1 interface.....                                        | 10 |
+| 6.1 Control plane procedures .....                                           | 10 |
+| 6.1.1 Interface Management procedures.....                                   | 10 |
+| 6.1.2 Context Management procedures.....                                     | 10 |
+| 6.1.3 RRC Message Transfer procedures .....                                  | 11 |
+| 6.1.3A Void.....                                                             | 11 |
+| 6.1.4 Warning Message Transmission procedures .....                          | 11 |
+| 6.1.5 Paging procedures .....                                                | 11 |
+| 6.2 User plane procedures .....                                              | 11 |
+| 6.2.1 User Data Transfer .....                                               | 11 |
+| 6.2.2 Flow Control.....                                                      | 11 |
+| 7 W1 interface protocol structure.....                                       | 12 |
+| 7.1 W1 Control Plane Protocol (W1-C).....                                    | 12 |
+| 7.2 W1 User Plane Protocol (W1-U) .....                                      | 12 |
+| 8 Other W1 interface specifications.....                                     | 12 |
+| 8.0 General .....                                                            | 12 |
+| 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471) .....         | 13 |
+| 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472) .....       | 13 |
+| 8.3 E-UTRAN and NG-RAN; W1 application protocol (WIAP) (3GPP TS 37.473)..... | 13 |
+| 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425) .....                    | 13 |
+| Annex A (informative): Change history.....                                   | 14 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document is an introduction to the 3GPP TS 37.4xx series of technical specifications that define the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within an NG-RAN.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.425: "NR user plane protocol".
+- [3] 3GPP TS 38.300: "NR; Overall description; Stage-2"
+- [4] 3GPP TS 37.471: "E-UTRAN and NG-RAN; W1 interface: layer 1".
+- [5] 3GPP TS 37.472: "E-UTRAN and NG-RAN; W1 signalling transport".
+- [6] 3GPP TS 37.473: "E-UTRAN and NG-RAN; W1 application protocol (W1AP)".
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**W1:** interface between an ng-eNB-CU and an ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU.
+
+**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU.
+
+**ng-eNB-CU:** a logical node hosting RRC, SDAP and PDCP protocols of the ng-eNB that controls the operation of one or more ng-eNB-DUs. The ng-eNB-CU terminates the W1 interface connected with the ng-eNB-DU.
+
+**ng-eNB-DU:** a logical node hosting RLC, MAC and PHY layers of the ng-eNB, and its operation is partly controlled by ng-eNB-CU. One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU. The ng-eNB-DU terminates the W1 interface connected with the ng-eNB-CU.
+
+**ng-eNB:** as defined in TS 38.300 [3].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                      |
+|--------|--------------------------------------|
+| DRB    | Data Radio Bearers                   |
+| W1-U   | W1 User plane interface              |
+| W1-C   | W1 Control plane interface           |
+| W1AP   | W1 Application Protocol              |
+| GTP-U  | GPRS Tunnelling Protocol             |
+| IP     | Internet Protocol                    |
+| NR-MIB | NR-Master Information Block          |
+| O&M    | Operation and Maintenance            |
+| PA     | Paging Area                          |
+| PF     | Paging Frame                         |
+| PO     | Paging Occasion                      |
+| QoS    | Quality of Service                   |
+| RRC    | Radio Resource Control               |
+| SCTP   | Stream Control Transmission Protocol |
+| SRB    | Signalling Radio Bearers             |
+| SIB1   | System Information Block 1           |
+| TNL    | Transport Network Layer              |
+
+# --- 4 General aspects
+
+## 4.0 General
+
+This clause captures the W1 interface principles and characteristics.
+
+## 4.1 W1 interface general principles
+
+The general principles for the specification of the W1 interface are as follows:
+
+- An ng-eNB may consist of an ng-eNB-CU and ng-eNB-DUs. An ng-eNB-CU and an ng-eNB-DU is connected via W1 logical interface.
+- One ng-eNB-CU controls one or more ng-eNB-DUs.
+- One ng-eNB-DU supports one or multiple cells. One cell is supported by only one ng-eNB-DU.
+- ng-eNB-DU ID is used to identify ng-eNB-DU only over W1AP procedures, ng-eNB-DU ID is not connected to cell identifier.
+- The ng-eNB-CU terminates W1 interface connected with the ng-eNB-DU.
+- The ng-eNB-DU terminates W1 interface connected with the ng-eNB-CU.
+- The W1 interface shall separate Radio Network Layer and Transport Network Layer.
+- The W1 interface shall enable exchange of UE associated information and non-UE associated information.
+- The W1 interface is open;
+- From a logical standpoint, the W1 is a point-to-point interface between an ng-eNB-CU and an ng-eNB-DU.
+
+NOTE: A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints.
+
+- The W1 interface supports control plane and user plane separation;
+- The W1 interface enables exchange of UE associated information and non-UE associated information;
+
+- The standard should not prevent to separated CP and UP.
+
+## 4.2 W1 interface specification objectives
+
+The W1 interface specifications facilitate the following:
+
+- inter-connection of an ng-eNB-CU and an ng-eNB-DU supplied by different manufacturers.
+
+## 4.3 W1 interface capabilities
+
+The W1 interface supports:
+
+- procedures to establish, maintain and release radio bearers for the NG-RAN part of PDU sessions and for E-UTRAN Radio Access Bearers;
+- the separation of each UE on the protocol level for user specific signalling management;
+- the transfer of RRC signalling messages between the UE and the ng-eNB-CU.
+
+## 4.4 W1 interface characteristics ---
+
+# 5 Functions of the W1 interface
+
+## 5.1 General
+
+The following clauses describe the functions supported over W1-C and W1-U.
+
+## 5.2 W1-C functions
+
+### 5.2.1 Interface management function
+
+The W1 setup function allows to exchange application level data needed for the ng-eNB-DU and ng-eNB-CU to interoperate correctly on the W1 interface. The W1 setup is initiated by the ng-eNB-DU.
+
+The ng-eNB-CU Configuration Update and ng-eNB-DU Configuration Update functions allow to update application level configuration data needed between ng-eNB-CU and ng-eNB-DU to interoperate correctly over the W1 interface, and may activate or deactivate cells.
+
+For NG-RAN, the W1 setup and ng-eNB-DU Configuration Update functions allow to inform the S-NSSAI(s) supported by the ng-eNB-DU.
+
+The error indication function is used by the ng-eNB-DU or ng-eNB-CU to indicate to the ng-eNB-CU or ng-eNB-DU that an error has occurred.
+
+The reset function is used to initialize the peer entity after node setup and after a failure event occurred. This procedure can be used by both the ng-eNB-DU and the ng-eNB-CU.
+
+The W1 resource coordination function is used to transfer information about frequency resource sharing between ng-eNB-CU and ng-eNB-DU.
+
+The ng-eNB-DU status indication function allows the ng-eNB-DU to indicate overload status to ng-eNB-CU.
+
+### 5.2.2 System Information management function
+
+Scheduling of system broadcast information is carried out in the ng-eNB-DU. The ng-eNB-DU is responsible for transmitting the system information according to the scheduling parameters available.
+
+The ng-eNB-DU is responsible for the encoding of ng-eNB-MIB. In case broadcast of SIB1 and other SI messages is needed, the ng-eNB-DU is responsible for assembling SIB1, SIB2, SIB3, SIB8 and SIB16 and the ng-eNB-CU is responsible for assembling other SIBs.
+
+### 5.2.3 Paging function
+
+The ng-eNB-DU is responsible for transmitting the paging information.
+
+The ng-eNB-CU provides paging information to enable the ng-eNB-DU to calculate the exact PO and PF. The ng-eNB-CU determines the PA. The ng-eNB-DU consolidates all the paging records for a particular PO, PF and PA, and encodes the final RRC message and broadcasts the paging message on the respective PO, PF in the PA.
+
+### 5.2.4 UE context management function
+
+The W1 UE context management function supports the establishment and modification of the necessary overall UE context.
+
+The establishment of the W1 UE context is initiated by the ng-eNB-CU and accepted or rejected by the ng-eNB-DU based on admission control criteria (e.g., resource not available).
+
+The modification of the W1 UE context can be initiated by either ng-eNB-CU or ng-eNB-DU. The receiving node can accept or reject the modification. The W1 UE context management function also supports the release of the context previously established in the ng-eNB-DU. The release of the context is triggered by the ng-eNB-CU either directly or following a request received from the ng-eNB-DU. The ng-eNB-CU requests the ng-eNB-DU to remove the UE Context when the UE enters RRC\_IDLE or RRC\_INACTIVE.
+
+This function can be also used to manage DRBs and SRBs, i.e., establishing, modifying and releasing DRB and SRB resources. The establishment and modification of DRB resources are triggered by the ng-eNB-CU and accepted/rejected by the ng-eNB-DU based on resource reservation information and QoS information to be provided to the ng-eNB-DU. For each DRB to be setup or modified, the S-NSSAI may be provided by ng-eNB-CU to the ng-eNB-DU in the UE Context Setup procedure and the UE Context Modification procedure.
+
+For NG-RAN, the mapping between QoS flows and radio bearers is performed by ng-eNB-CU and the granularity of bearer related management over W1 is radio bearer level, and the ng-eNB-CU decides an aggregated DRB QoS profile for each radio bearer based on received QoS flow profile, and provides both aggregated DRB QoS profile and QoS flow profile to the ng-eNB-DU, and the ng-eNB-DU either accepts the request or rejects it with appropriate cause value.
+
+With this function, ng-eNB-DU could also notify ng-eNB-CU whether the QoS for already established DRBs is not fulfilled any longer or it is fulfilled again.
+
+The UE Inactivity Notification function is initiated by the ng-eNB-DU to indicate the UE activity event.
+
+The Notify function is to enable the ng-eNB-DU to inform the ng-eNB-CU that the QoS of an already established GBR DRB cannot be fulfilled any longer or that it can be fulfilled again.
+
+With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit.
+
+With this function, the ng-eNB-CU indicates the UL UE AMBR limit to the ng-eNB-DU, and the ng-eNB-DU enforces the indicated limit.
+
+With this function, ng-eNB-CU requests the ng-eNB-DU to setup or change of the SpCell for the UE, and the ng-eNB-DU either accepts or rejects the request with appropriate cause value.
+
+With this function, the ng-eNB-CU requests the setup of the SCell(s) at the ng-eNB-DU side, and the ng-eNB-DU accepts all, some or none of the SCell(s) and replies to the ng-eNB-CU. The ng-eNB-CU requests the removal of the SCell(s) for the UE.
+
+With this function, the ng-eNB-DU indicates that a bearer, or a UE is inactive or active. The ng-eNB-CU consolidates all the serving ng-eNB-DUs for the UE and takes further action.
+
+### 5.2.5 RRC message transfer function
+
+This function allows to transfer RRC messages between ng-eNB-CU and ng-eNB-DU. RRC messages are transferred over W1-C. The ng-eNB-CU is responsible for the encoding of the dedicated RRC message with assistance information provided by ng-eNB-DU. This function also allows ng-eNB-DU to report to ng-eNB-CU if the downlink RRC message has been successfully delivered to UE or not.
+
+### 5.2.6 Warning messages information transfer function
+
+This function allows to cooperate with the warning message transmission procedures over NG interface. The ng-eNB-CU is responsible for encoding the warning related SI message and sending it together with other warning related information for the ng-eNB-DU to broadcast over the radio interface.
+
+## 5.3 W1-U functions
+
+### 5.3.1 Transfer of user data
+
+This function allows to transfer of user data between ng-eNB-CU and ng-eNB-DU.
+
+### 5.3.2 Flow control function
+
+This function allows to control the downlink user data flow to the ng-eNB-DU. The detailed protocol is specified in TS 38.425 [2]
+
+# --- 6 Procedures of the W1 interface
+
+## 6.1 Control plane procedures
+
+### 6.1.1 Interface Management procedures
+
+The W1 Interface management procedures are listed below:
+
+- Reset procedure
+- Error Indication procedure
+- W1 Setup procedure
+- ng-eNB-DU Configuration Update procedure
+- ng-eNB-CU Configuration Update procedure
+- ng-eNB-DU Resource Coordination procedure
+- ng-eNB-DU Status Indication procedure
+
+### 6.1.2 Context Management procedures
+
+The W1 Context management procedures are listed below:
+
+- UE Context Setup procedure
+- UE context Release Request (ng-eNB-DU initiated) procedure
+- UE context Release (ng-eNB-CU initiated) procedure
+- UE Context Modification (ng-eNB-CU initiated) procedure
+- UE Context Modification Required (ng-eNB-DU initiated) procedure
+- UE Inactivity Notification procedure
+- Notify procedure
+
+### 6.1.3 RRC Message Transfer procedures
+
+The W1 RRC message transfer procedures are listed below:
+
+- Initial UL RRC Message Transfer procedure
+
+- UL RRC Message Transfer procedure
+- DL RRC Message Transfer procedure
+- RRC Delivery Report procedure
+
+### 6.1.3A Void
+
+### 6.1.4 Warning Message Transmission procedures
+
+The W1 Warning message transmission procedures are listed below:
+
+- Write-Replace Warning procedure
+- PWS Cancel procedure
+- PWS Restart Indication procedure
+- PWS Failure Indication procedure
+
+### 6.1.5 Paging procedures
+
+The W1 Paging procedures are listed below:
+
+- Paging
+
+## 6.2 User plane procedures
+
+### 6.2.1 User Data Transfer
+
+Void
+
+### 6.2.2 Flow Control
+
+Void
+
+# --- 7 W1 interface protocol structure
+
+## 7.1 W1 Control Plane Protocol (W1-C)
+
+Figure 7.1-1 shows the protocol structure for W1-C. The TNL is based on IP transport, comprising the SCTP on top of IP. The application layer signalling protocol is referred to as W1AP (W1 Application Protocol).
+
+![Diagram of the W1-C control plane protocol stack. The stack is divided into two main sections by a horizontal line with an oval in the center. The top section is labeled 'Control Plane' and contains the 'W1AP' block. The bottom section is labeled 'Radio Network Layer' on the left and 'Transport Network Layer' on the left. The bottom section contains four stacked blocks: 'SCTP', 'IP', 'Data link layer', and 'Physical layer'.](d0c9888da9078a08d93712fd0e113a88_img.jpg)
+
+The diagram illustrates the protocol stack for the W1-C control plane. At the top, the 'Control Plane' section contains the 'W1AP' (W1 Application Protocol) block. Below this, a horizontal line with an oval in the center separates it from the lower layers. The lower layers are grouped under the 'Radio Network Layer' (on the left) and 'Transport Network Layer' (on the left). These layers consist of four stacked blocks: 'SCTP' (Stream Control Transmission Protocol), 'IP' (Internet Protocol), 'Data link layer', and 'Physical layer'.
+
+Diagram of the W1-C control plane protocol stack. The stack is divided into two main sections by a horizontal line with an oval in the center. The top section is labeled 'Control Plane' and contains the 'W1AP' block. The bottom section is labeled 'Radio Network Layer' on the left and 'Transport Network Layer' on the left. The bottom section contains four stacked blocks: 'SCTP', 'IP', 'Data link layer', and 'Physical layer'.
+
+Figure 7.1-1: Interface protocol structure for W1-C
+
+## 7.2 W1 User Plane Protocol (W1-U)
+
+Figure 7.2-1 shows the protocol structure for W1-U. The TNL is based on IP transport, comprising the UDP and GTP-U on top of IP.
+
+![Figure 7.2-1: Interface protocol structure for W1-U. The diagram shows a stack of protocols. At the top is the 'User Plane' block. Below it is the 'Radio Network Layer' block, separated by a horizontal line with an oval in the center. Below the Radio Network Layer is a stack of five blocks: 'GTP-U', 'UDP', 'IP', 'Data link layer', and 'Physical layer'. The 'Transport Network Layer' label is to the left of the 'IP', 'Data link layer', and 'Physical layer' blocks, with a bracket grouping them.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+The diagram illustrates the protocol stack for the W1-U interface. At the top is the 'User Plane'. Below it is the 'Radio Network Layer'. A horizontal line with an oval in the center separates the Radio Network Layer from the Transport Network Layer. The Transport Network Layer consists of five stacked blocks: 'GTP-U', 'UDP', 'IP', 'Data link layer', and 'Physical layer'. The 'Transport Network Layer' label is positioned to the left of the 'IP', 'Data link layer', and 'Physical layer' blocks, with a bracket grouping them.
+
+Figure 7.2-1: Interface protocol structure for W1-U. The diagram shows a stack of protocols. At the top is the 'User Plane' block. Below it is the 'Radio Network Layer' block, separated by a horizontal line with an oval in the center. Below the Radio Network Layer is a stack of five blocks: 'GTP-U', 'UDP', 'IP', 'Data link layer', and 'Physical layer'. The 'Transport Network Layer' label is to the left of the 'IP', 'Data link layer', and 'Physical layer' blocks, with a bracket grouping them.
+
+Figure 7.2-1: Interface protocol structure for W1-U
+
+# 8 Other W1 interface specifications
+
+## 8.0 General
+
+This clause contains the description of the other related 3GPP specifications.
+
+## 8.1 E-UTRAN and NG-RAN; W1 interface: layer 1 (3GPP TS 37.471)
+
+3GPP TS 37.471 [4] specifies the physical layer technologies that may be used to support the W1 interface.
+
+## 8.2 E-UTRAN and NG-RAN; W1 signalling transport (3GPP TS 37.472)
+
+3GPP TS 37.472 [5] specifies the signalling bearers for the W1AP for the W1-C interface.
+
+## 8.3 E-UTRAN and NG-RAN; W1 application protocol (W1AP) (3GPP TS 37.473)
+
+3GPP TS 37.473 [6] specifies the F1AP protocol for radio network control plane signalling over the W1 interface.
+
+## 8.4 NG-RAN; NR user plane protocol (3GPP TS 38.425)
+
+3GPP TS 38.425 [2] specifies the user plane protocol being used over the W1-U interface.
+
+# Annex A (informative): Change history
+
+| Change history |              |           |      |     |     |                                                                                                                                     |             |
+|----------------|--------------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                     | New version |
+| 2018-05        | RAN3#100     | R3-183552 |      |     |     | BL TS submission for approval.                                                                                                      |             |
+| 2018-06        | RAN3#100     | R3-183602 |      |     |     | Merging the agreements in R3-183571 and R3-183552.                                                                                  |             |
+| 2018-11        | RAN3#102     | R3-187270 |      |     |     | Add definition of functions and procedure for the W1AP.                                                                             |             |
+| 2019-02        | RAN3#103     | R3-191163 |      |     |     | Add definition of functions and procedure for the W1AP.                                                                             |             |
+| 2019-04        | RAN3#103bis  | R3-191970 |      |     |     | Add procedure definition of Interface Management procedures and UE Context Management procedures.                                   |             |
+| 2019-05        | RAN3#104     | R3-193174 |      |     |     | Add Some descriptions and procedures                                                                                                | 0.4.0       |
+| 2019-08        | RAN3#105     | R3-194676 |      |     |     | Add the description of procedure for the W1AP                                                                                       | 0.4.0       |
+| 2019-08        | RAN3#105     | R3-194562 |      |     |     | Add the description related to SpCell and SCell management                                                                          | 0.4.0       |
+| 2019-10        | RAN3#105-Bis | R3-196138 |      |     |     | Added the description of References, Definitions and abbreviations<br>,General aspects, - QoS notification, inactivity notification | 0.4.0       |
+| 2019-12        | RP-86        | RP-192951 |      |     |     | TS submission to TSG RAN plenary for approval                                                                                       | 1.2.0       |
+| 2019-12        | RP-86        |           |      |     |     | TS approved by TSG RAN plenary                                                                                                      | 16.0.0      |
+| 2020-03        | RP-87-e      | RP-200429 | 0001 |     | F   | Miscellaneous corrections to 37.470                                                                                                 | 16.1.0      |
+| 2020-07        | RP-88-e      | RP-201084 | 0002 | 1   | F   | Miscellaneous corrections to 37.470                                                                                                 | 16.2.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37471/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37471/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f6ebb3997e2a8eef5b10c0c1e771f34de26b4a0
--- /dev/null
+++ b/marked/Rel-16/37_series/37471/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d87b0fffa88133163771a7d2012e5048c19510ea515ec04ed54b048eff13b895
+size 9284
diff --git a/marked/Rel-16/37_series/37471/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37471/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75c42d7c11c8998deabe996404ae0a9606a484dc
--- /dev/null
+++ b/marked/Rel-16/37_series/37471/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:468137148f5fedf1a756cb4c2414909a33dfb8c8680d5b3815b36f47bb3b91e2
+size 5780
diff --git a/marked/Rel-16/37_series/37471/raw.md b/marked/Rel-16/37_series/37471/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..e1dcacaf7a1cfb75b7fc0c4cce7ee47ebc334ac2
--- /dev/null
+++ b/marked/Rel-16/37_series/37471/raw.md
@@ -0,0 +1,179 @@
+
+
+# 3GPP TS 37.471 V16.1.0 (2020-03) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; Layer 1 (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                        |   |
+|--------------------------------------------------------|---|
+| Foreword .....                                         | 4 |
+| 1 Scope.....                                           | 6 |
+| 2 References.....                                      | 6 |
+| 3 Definitions of terms, symbols and abbreviations..... | 6 |
+| 3.1 Terms.....                                         | 6 |
+| 3.2 Symbols.....                                       | 6 |
+| 3.3 Abbreviations .....                                | 6 |
+| 4 Introduction.....                                    | 6 |
+| Annex A (informative): Change history.....             | 7 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the standards allowed to implement Layer 1 on the W1 interface. The W1 interface provides means for interconnecting an ng-eNB-CU and an ng-eNB-DU of an ng-eNB within NG-RAN.
+
+The specification of transmission delay requirements and O&M requirements are not in the scope of the present document.
+
+In the following 'Layer 1' and 'Physical Layer' are assumed to be synonymous.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+- [3] 3GPP TS 38.411: "NG-RAN; NG layer 1".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+ng-eNB: as defined in 3GPP TS 38.300 [2].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1], in TS 38.411 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Introduction
+
+The W1 Layer 1 shall comply with the requirements of clauses 4 through 6 in 3GPP TS 38.411 [3].
+
+# Annex A (informative): Change history
+
+| Change history |          |           |      |     |     |                                                           |             |
+|----------------|----------|-----------|------|-----|-----|-----------------------------------------------------------|-------------|
+| Date           | Meeting  | TDoc      | CR   | Rev | Cat | Subject/Comment                                           | New version |
+| 2018-05        | RAN3#100 | R3-183553 |      |     |     | BL TS submission for approval.                            |             |
+| 2018-06        | RAN3#100 | R3-183603 |      |     |     | Agree to add editor's note in scope in R3-183603.         | 0.1.0       |
+| 2019-11        | RAN3#106 | R3-197488 |      |     |     | Submission to RAN3 in in R3-197488: Change S1 to NG stead | 1.1.0       |
+| 2019-12        | RP-86    | RP-192954 |      |     |     | TS submitted to TSG RAN plenary for approval              | 1.3.0       |
+| 2019-12        | RP-86    |           |      |     |     | TS approved by TSG RAN plenary                            | 16.0.0      |
+| 2020-03        | RP-87-e  | RP-200429 | 0001 | -   | F   | Miscellaneous corrections to 37.471                       | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37472/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37472/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1c7f509ce3f085cdeb2789f7ca44f41f983b5dbc
--- /dev/null
+++ b/marked/Rel-16/37_series/37472/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e9a5ab23be1ef6c9f881daad437d0b75b78458681b4b76a111a804e60b92388
+size 9284
diff --git a/marked/Rel-16/37_series/37472/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37472/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d54b5b6ae870a9adb78ff51f06049fc780866939
--- /dev/null
+++ b/marked/Rel-16/37_series/37472/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0da881c84289a2b452b4b8c27e22bce7eea4294f0ad3a5c1bbd1e0efa5b1383
+size 5783
diff --git a/marked/Rel-16/37_series/37472/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-16/37_series/37472/c9d8a18a6137ad054b841d7a614afb48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d116c7a53281c2a7e3a5bb4ef575d7266fd6602
--- /dev/null
+++ b/marked/Rel-16/37_series/37472/c9d8a18a6137ad054b841d7a614afb48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4fe664e3c3d67c2ed4d04ec49e40819817937f00bf504396143d0550de7349bb
+size 19228
diff --git a/marked/Rel-16/37_series/37472/raw.md b/marked/Rel-16/37_series/37472/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..412bbf7b1183bb6fe419a79b036f8eaea51c7a8f
--- /dev/null
+++ b/marked/Rel-16/37_series/37472/raw.md
@@ -0,0 +1,268 @@
+
+
+# 3GPP TS 37.472 V16.2.0 (2020-09) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; Signalling transport (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring a stylized '5G' in black with three green curved lines above the '5'.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters '3GPP' in a stylized black font with a red signal icon below the 'G'. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, all-caps font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+---
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                        |   |
+|--------------------------------------------------------|---|
+| Foreword .....                                         | 4 |
+| 1 Scope.....                                           | 6 |
+| 2 References.....                                      | 6 |
+| 3 Definitions of terms, symbols and abbreviations..... | 6 |
+| 3.1 Terms.....                                         | 6 |
+| 3.2 Symbols.....                                       | 6 |
+| 3.3 Abbreviations .....                                | 7 |
+| 4. WI-C signalling bearer .....                        | 7 |
+| 4.1 Function and protocol stack .....                  | 7 |
+| 5 Data link layer.....                                 | 7 |
+| 6 IP layer.....                                        | 7 |
+| 7 Transport layer.....                                 | 8 |
+| Annex A (informative): Change History.....             | 9 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document specifies the standards for Signalling Transport to be used across the W1 interface. The W1 interface provides means for interconnecting a ng-eNB-CU and a ng-eNB-DU of a ng-eNB within a NG-RAN. The present document describes how the W1AP signalling messages are transported over W1.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification".
+- [3] IETF RFC 791 (1981-09): "Internet Protocol".
+- [4] IETF RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
+- [5] IETF RFC 4960 (2007-09): "Stream Control Transmission Protocol".
+- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**ng-eNB:** as defined in 3GPP TS 38.300 [6]
+
+**SCTP association:** as defined in IETF RFC 4960 (2007-09) [5]
+
+**SCTP endpoint:** as defined in IETF RFC 4960 (2007-09) [5]
+
+**W1:** interface between a ng-eNB-CU and a ng-eNB-DU, providing an interconnection point between the ng-eNB-CU and the ng-eNB-DU.
+
+**W1-C:** Reference point for the control plane protocol between ng-eNB-CU and ng-eNB-DU.
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|          |                                      |
+|----------|--------------------------------------|
+| DiffServ | Differentiated Service               |
+| IANA     | Internet Assigned Number Authority   |
+| IP       | Internet Protocol                    |
+| PPP      | Point to Point Protocol              |
+| SCTP     | Stream Control Transmission Protocol |
+
+# 4.W1-C signalling bearer
+
+## 4.1 Function and protocol stack
+
+The W1-C signalling bearer provides the following functions:
+
+- Provision of reliable transfer of W1AP messages over the W1-C interface.
+- Provision of networking and routing function.
+- Provision of redundancy in the signalling network.
+- Support for flow control and congestion control.
+
+The protocol stack for W1-C Signalling Bearer is shown in figure 4.1-1 and details on each protocol are described in the following clauses.
+
+![Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer containing the W1AP block. Below it is a horizontal line with an oval symbol representing the interface. Below the interface is the Transport Network Layer, which contains a stack of four blocks: SCTP, IP, Data link layer, and Physical layer.](c9d8a18a6137ad054b841d7a614afb48_img.jpg)
+
+```
+
+graph TD
+    subgraph RNL [Radio Network Layer]
+        W1AP[W1AP]
+    end
+    W1AP --- Interface(( ))
+    subgraph TNL [Transport Network Layer]
+        SCTP[SCTP]
+        IP[IP]
+        DLL[Data link layer]
+        PL[Physical layer]
+    end
+    Interface --- SCTP
+  
+```
+
+Figure 4.1-1: W1-C signalling bearer protocol stack diagram. The diagram shows a vertical stack of protocol layers. At the top is the Radio Network Layer containing the W1AP block. Below it is a horizontal line with an oval symbol representing the interface. Below the interface is the Transport Network Layer, which contains a stack of four blocks: SCTP, IP, Data link layer, and Physical layer.
+
+Figure 4.1-1: W1-C signalling bearer protocol stack
+
+The Transport Network Layer is based on IP transport, comprising SCTP on top of IP.
+
+# 5 Data link layer
+
+The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.
+
+# 6 IP layer
+
+The ng-eNB-CU and ng-eNB-DU shall support IPv6 (IETF RFC 8200 [2]) and/or IPv4 (IETF RFC 791 [3]).
+
+The IP layer of W1-C only supports point-to-point transmission for delivering W1AP message.
+
+The ng-eNB-CU and ng-eNB-DU shall support the Diffserv Code Point marking as described in IETF RFC 2474 [4].
+
+# 7 Transport layer
+
+SCTP (IETF RFC 4960 [5]) shall be supported as the transport layer of W1-C signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol W1AP is 73.
+
+SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.
+
+The ng-eNB-DU and ng-eNB-CU shall support a configuration with a single SCTP association per ng-eNB-DU/ng-eNB-CU pair.
+
+The ng-eNB-DU shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for W1AP is 37472.
+
+Within the set of SCTP associations established between one ng-eNB-CU and ng-eNB-DU pair, a single SCTP association shall be employed for W1AP elementary procedures that utilize non-UE-associated signalling with the possibility of fail-over to a new association to enable robustness.
+
+Between one ng-eNB-CU and ng-eNB-DU pair:
+
+- A single pair of stream identifiers shall be reserved over an SCTP association for the sole use of W1AP elementary procedures that utilize non UE-associated signalling.
+- At least one pair of stream identifiers over one or several SCTP associations shall be reserved for the sole use of W1AP elementary procedures that utilize UE-associated signalling. However, a few pairs (i.e. more than one) should be reserved.
+- For a single UE-associated signalling, the ng-eNB-DU shall use one SCTP association and one SCTP stream, and the association/stream should not be changed during the communication of the UE-associated signalling unless TNL binding update is performed.
+
+Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from a ng-eNB-CU or ng-eNB-DU, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960[5] in sub clause 5.2.
+
+The SCTP congestion control may, using an implementation specific mechanism, initiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages.
+
+# Annex A (informative): Change History
+
+| Change history |               |           |      |     |     |                                                                           |             |
+|----------------|---------------|-----------|------|-----|-----|---------------------------------------------------------------------------|-------------|
+| Date           | Meeting       | TDoc      | CR   | Rev | Cat | Subject/Comment                                                           | New version |
+| 2018-05        | RAN3#100      | R3-183554 |      |     |     | BL TS submission for approval.                                            |             |
+| 2019-08        | RAN3#105      | R3-194678 |      |     |     | Add the description of procedure for the W1 signalling transport protocol | 0.1.0       |
+| 2019-10        | RAN3#105 -Bis | R3-196134 |      |     |     | Add the description of References, Definitions and abbreviations.         | 0.1.0       |
+| 2019-11        | RAN3#106 -Bis | R3-197634 |      |     |     | Change the version number to 0.2.0.                                       | 0.2.0       |
+| 2019-12        | RP-86         | RP-192954 |      |     |     | TS submitted to TSG RAN plenary for approval                              | 1.3.0       |
+| 2019-12        | RP-86         |           |      |     |     | TS approved by TSG RAN plenary                                            | 16.0.0      |
+| 2020-07        | RP-88-e       | RP-201236 | 0002 | -   | F   | SCTP Payload Protocol Identifier for W1AP                                 | 16.1.0      |
+| 2020-09        | RP-89-e       | RP-201948 | 0003 | -   | F   | SCTP port number allocatd by IANA                                         | 16.2.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37473/02d0c8a07c481d880b73a25d02050fad_img.jpg b/marked/Rel-16/37_series/37473/02d0c8a07c481d880b73a25d02050fad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd8a6aeb19dc5b7d11a5f9f81fcc78623164fbe4
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/02d0c8a07c481d880b73a25d02050fad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:933a88198c3001a0715a300e3953e486f1436f3c2e16de0691feda037900aaf2
+size 14273
diff --git a/marked/Rel-16/37_series/37473/0803a098adb6b6c817a7bee221179e16_img.jpg b/marked/Rel-16/37_series/37473/0803a098adb6b6c817a7bee221179e16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fe66e6dbe73b61c9ba89ae0d768f8051bf5cf4e
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/0803a098adb6b6c817a7bee221179e16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4261e5462bd64fd748be21a04687b747cea27f858b18c723ee8dc0b8cca556cd
+size 16978
diff --git a/marked/Rel-16/37_series/37473/0977b81510f7649846289ee785d20e74_img.jpg b/marked/Rel-16/37_series/37473/0977b81510f7649846289ee785d20e74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e35199e6d086dd829eea6cece9f514085b29fd66
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/0977b81510f7649846289ee785d20e74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a07676632bca5ec1997cbc6dd7a3d75f976c17035a24c3467bddc9a8a298d3b0
+size 17796
diff --git a/marked/Rel-16/37_series/37473/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-16/37_series/37473/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef79e03b0153dc8dc1844a3b8f68ba8506319c79
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/09955ff8214ffb6947951fc0f60eb6ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2f4f082cc020a808b6c941ddf742c2bc12d447b3a905d025db2bda9d3e8c031
+size 28394
diff --git a/marked/Rel-16/37_series/37473/10781f43062bf3e9601a1e086710556c_img.jpg b/marked/Rel-16/37_series/37473/10781f43062bf3e9601a1e086710556c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f9fa775784ae8042d99318c9be8875a6ebdc440
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/10781f43062bf3e9601a1e086710556c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e40ad50d9f68add9bbf2a0fdcfde04838909f15b42df72a168d0c69e7df62d5f
+size 22180
diff --git a/marked/Rel-16/37_series/37473/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-16/37_series/37473/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91609e1d637a3df676566d9adcc18328a3d2f07c
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02e912ae35bd6f98a810fd168564e86282b7e3775aab2f4f2204aaf50e4eae6b
+size 24563
diff --git a/marked/Rel-16/37_series/37473/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/37_series/37473/315bdbeafb39026e19b77c26b19d9d1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33c3df5aa8ad8ae70978bf76f9f2d2cfc6010273
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/315bdbeafb39026e19b77c26b19d9d1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:874ea1ce0da272bb35e45935f86f195ff1bf615c47961b8381975de129e1d5ae
+size 17318
diff --git a/marked/Rel-16/37_series/37473/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/37_series/37473/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc96de6a326e91670bd1cbf63dadc0460fbdd946
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00db12ed717290f4ca6261894bac4def8b07fe4e8d5ef2e7570f722520ed7401
+size 21460
diff --git a/marked/Rel-16/37_series/37473/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/37_series/37473/41a438d7e4adc17c3a4005e7c9500091_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1e2daa3a214b4aa840e247be92825378acdabcaf
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/41a438d7e4adc17c3a4005e7c9500091_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cdc16efac16fdf4aa98fffd7907a4d9cd9ac15238983c181bfef18927b2bcbd
+size 17374
diff --git a/marked/Rel-16/37_series/37473/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/37_series/37473/43837b056625d3d6ce615e4c02f163bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec660fbfa9e7766b5b8756cf6a9bb0dac4293001
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/43837b056625d3d6ce615e4c02f163bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4730c0d0c7a28a89f9980b153ef8cce87c0ca19f59466fad34765b781fc198b9
+size 13782
diff --git a/marked/Rel-16/37_series/37473/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/37_series/37473/474a819357587e34949a3e110ff19b30_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c21df4291b36c3ffdfca994fb0ac6b0cb185bdf
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/474a819357587e34949a3e110ff19b30_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4432306de34996f77569040362e1b5fd9a0edcde063ef9e78ab29b97c0b96253
+size 24771
diff --git a/marked/Rel-16/37_series/37473/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-16/37_series/37473/4b87467ad9642943235f48f7d4b59449_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93c5d2d16654970b683ae9dd1e4a4154a2cf9b34
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/4b87467ad9642943235f48f7d4b59449_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a429729fafb70e86cadb8146a2c8344e43005e447d1f81d6fda687342c72e85
+size 24322
diff --git a/marked/Rel-16/37_series/37473/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-16/37_series/37473/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a260ae7f9552e72cc477d1b2ff36bdc8cc10cc5a
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/58f4167687de8d7339594e5f6fbe0bc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5b7b0e4861fdb583e1386fa77a5d618b4831bd661d3a7f90481adec49458443
+size 17033
diff --git a/marked/Rel-16/37_series/37473/5c6787bac31274e2dc992efeca74b303_img.jpg b/marked/Rel-16/37_series/37473/5c6787bac31274e2dc992efeca74b303_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..854bdd5419134ff5ac71a3ac48f58275cc679154
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/5c6787bac31274e2dc992efeca74b303_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:205a796df64fc18976c9c45f08664484d35b59e1dd98a87fac399ddc5b9e91a0
+size 26453
diff --git a/marked/Rel-16/37_series/37473/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37473/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c04ce1419b9cee40b0eb9081e440fe2afbabd968
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d578b34a830f5d4f0dfaf370fd44a8ed7c071295ade053914f3ff8f9dfef43be
+size 9275
diff --git a/marked/Rel-16/37_series/37473/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37473/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4a84fde2a5b7331353965e562a2611060a5fdd1
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2f08ae62a0581efc176528c25a76098c7f466ef0369017e2cb7c9f724f71adf
+size 5819
diff --git a/marked/Rel-16/37_series/37473/6929132b4964d52244da61d4614bc4d6_img.jpg b/marked/Rel-16/37_series/37473/6929132b4964d52244da61d4614bc4d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f7b254ddd612101f6f8cec49ce5d053de67863c
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/6929132b4964d52244da61d4614bc4d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1de3ddd4a2e33d42a9ec111833a9cb8273ad54dece0df8261d76f06219a2970e
+size 24440
diff --git a/marked/Rel-16/37_series/37473/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/Rel-16/37_series/37473/70de8885bd7de15723aaad5eb5c5febf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a40b5e5b1c7a1a7876edcb6cc82f7cb151a8f05
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/70de8885bd7de15723aaad5eb5c5febf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b09070629921b386edab183ea56b380ee1a566c4e4767b8aafda91398853d89c
+size 16811
diff --git a/marked/Rel-16/37_series/37473/718be1eb075833deb7a3b80729a06264_img.jpg b/marked/Rel-16/37_series/37473/718be1eb075833deb7a3b80729a06264_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50d17a9d0a061f3b4f9abafc255680dfc1fbec86
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/718be1eb075833deb7a3b80729a06264_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dd411162ca35a029d0e20b6f83658447e395ed8e29f0a6b8b308f574e0cdb8a5
+size 17330
diff --git a/marked/Rel-16/37_series/37473/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/37_series/37473/73dff6b45b2b9ffd384bab3235f869af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3a16a5d02fef7c2e310ef3590197caca9733814
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/73dff6b45b2b9ffd384bab3235f869af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9e098a79d58d314a7116ccba54807c3c598f6246c7a87d7a047f6b437d35b662
+size 28512
diff --git a/marked/Rel-16/37_series/37473/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/37_series/37473/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6d72e2ad85838bf6f44bfd988775f55c73f413e8
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/744acfe8d4e31bcf03f95714c2f6e567_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb1a32778a60e51fea4539f7a76dc41d51a2ca75858623fd560f5e9230faa917
+size 26213
diff --git a/marked/Rel-16/37_series/37473/7728e2dd44c95d109debb1eb59e9b411_img.jpg b/marked/Rel-16/37_series/37473/7728e2dd44c95d109debb1eb59e9b411_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe452eb19320b809143768e4a178eac4ee8f28ee
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/7728e2dd44c95d109debb1eb59e9b411_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:199abb0de8055b19bf6be34b969cbb2c0f9361171f2ce2eed051fc81b9b21b18
+size 26255
diff --git a/marked/Rel-16/37_series/37473/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-16/37_series/37473/86b4670fc1a5a694821ee92b99c1209a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d1929264ce410e9b5ca57c883474da76051e3e0
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/86b4670fc1a5a694821ee92b99c1209a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9353d2251aa83e3135142703fc8c3d9d1bfe4d6dad34255dcf342752f2a3a121
+size 18766
diff --git a/marked/Rel-16/37_series/37473/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-16/37_series/37473/875c6f4f441fdd3ca7e1908fd1582983_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cab2daf373e542369141527a345df6150d6063c5
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/875c6f4f441fdd3ca7e1908fd1582983_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8f6bebdf5c52097038288faf4556d323b22c902f0b34d6cc943454abba77dd4
+size 21777
diff --git a/marked/Rel-16/37_series/37473/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/marked/Rel-16/37_series/37473/90ee16ccc0ad16aeca48087797d7b07f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d4d972f9b60876421ea82edcb13f4aa0bd6be50
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/90ee16ccc0ad16aeca48087797d7b07f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f9495e233c3ee219e305881da3313f4e61b25ca75be69d3904cd001adbfccf2
+size 13968
diff --git a/marked/Rel-16/37_series/37473/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Rel-16/37_series/37473/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7df3fa54d89bf21e67337ed3e8f8170e69c83a5
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:473da9c7be141c6298e21060aad9691ce45e33361c8b7e03bf1fa57d08d4f664
+size 18437
diff --git a/marked/Rel-16/37_series/37473/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg b/marked/Rel-16/37_series/37473/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8140b1535988952f587cc89bc4cc8c81ee2270bf
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/b0d322b2e75c75e1f21bfc0df841beaa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2221d5b15ace64b968eeed0cd27e5c941a2201e3b856fd60943d90154fdc3fdb
+size 22571
diff --git a/marked/Rel-16/37_series/37473/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/37_series/37473/b51423b6c049f5b5fcde42e50b58f18b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d9be3cd11c66ed449cf373033c66198a42fcfd98
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/b51423b6c049f5b5fcde42e50b58f18b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34f35d6126300ca7f88d9be56fa8ae2ed663f632704b87d38fe7b3379add1b32
+size 26136
diff --git a/marked/Rel-16/37_series/37473/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/marked/Rel-16/37_series/37473/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ef8007890a3d53bb8eba7dff2927cf88bb1025d
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:480f1665becec315fafc5e421e6ea493369430ff2cdbec7108e0007b1097a48f
+size 30886
diff --git a/marked/Rel-16/37_series/37473/db7cb51aac8519daab50e2171cecae82_img.jpg b/marked/Rel-16/37_series/37473/db7cb51aac8519daab50e2171cecae82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5c97854d24996cb50163043ecd23052d44aed08
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/db7cb51aac8519daab50e2171cecae82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38b4e45a65a627040176857dc4154130a7cc9000e8482f2bce03b6f05ac6f8e6
+size 29229
diff --git a/marked/Rel-16/37_series/37473/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-16/37_series/37473/dfaa8b98082261913dac00eae86b2889_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ba391d4581c712177410b5a5d6b029aaf3e7903
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/dfaa8b98082261913dac00eae86b2889_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bb890cad2d6b3d93300a261743dc73d7e675e406b9d6a1bb6d8874fc0f21498
+size 17371
diff --git a/marked/Rel-16/37_series/37473/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/Rel-16/37_series/37473/fc0735d325f0ebd9214171975c68a888_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff35c94362c4d154e447c538fff79f0a342e402e
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/fc0735d325f0ebd9214171975c68a888_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:903f666fe3cf687a2512a1ab696cc93c07a9bf7b63b065097af4ed4594839364
+size 13442
diff --git a/marked/Rel-16/37_series/37473/raw.md b/marked/Rel-16/37_series/37473/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0748d25867edee5373aad8d416e23b20161d9a76
--- /dev/null
+++ b/marked/Rel-16/37_series/37473/raw.md
@@ -0,0 +1,7723 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; W1 interface; Application Protocol (W1AP) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. Below the "G" is a red signal wave icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- ***Copyright Notification*** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                              |    |
+|--------------------------------------------------------------|----|
+| Foreword .....                                               | 8  |
+| 1 Scope.....                                                 | 10 |
+| 2 References.....                                            | 10 |
+| 3 Definitions of terms, symbols and abbreviations .....      | 11 |
+| 3.1 Terms.....                                               | 11 |
+| 3.2 Symbols.....                                             | 12 |
+| 3.3 Abbreviations .....                                      | 12 |
+| 4 General.....                                               | 12 |
+| 4.1 Procedure specification principles .....                 | 12 |
+| 4.2 Forwards and backwards compatibility.....                | 13 |
+| 4.3 Specification notations .....                            | 13 |
+| 5 W1AP services.....                                         | 13 |
+| 6 Services expected from signalling transport.....           | 13 |
+| 7 Functions of W1AP.....                                     | 13 |
+| 8 W1AP procedures .....                                      | 14 |
+| 8.1 List of W1AP Elementary procedures .....                 | 14 |
+| 8.2 Interface Management procedures .....                    | 15 |
+| 8.2.1 Reset.....                                             | 15 |
+| 8.2.1.1 General.....                                         | 15 |
+| 8.2.1.2 Successful Operation .....                           | 15 |
+| 8.2.1.2.1 Reset Procedure Initiated from the ng-eNB-CU ..... | 15 |
+| 8.2.1.2.2 Reset Procedure Initiated from the ng-eNB-DU ..... | 16 |
+| 8.2.1.3 Abnormal Conditions.....                             | 16 |
+| 8.2.2 Error Indication .....                                 | 17 |
+| 8.2.2.1 General.....                                         | 17 |
+| 8.2.2.2 Successful Operation .....                           | 17 |
+| 8.2.2.3 Abnormal Conditions.....                             | 17 |
+| 8.2.3 W1 Setup .....                                         | 18 |
+| 8.2.3.1 General.....                                         | 18 |
+| 8.2.3.2 Successful Operation .....                           | 18 |
+| 8.2.3.3 Unsuccessful Operation .....                         | 19 |
+| 8.2.3.4 Abnormal Conditions.....                             | 19 |
+| 8.2.4 ng-eNB-DU Configuration Update .....                   | 19 |
+| 8.2.4.1 General.....                                         | 19 |
+| 8.2.4.2 Successful Operation .....                           | 19 |
+| 8.2.4.3 Unsuccessful Operation .....                         | 20 |
+| 8.2.4.4 Abnormal Conditions.....                             | 20 |
+| 8.2.5 ng-eNB-CU Configuration Update.....                    | 21 |
+| 8.2.5.1 General.....                                         | 21 |
+| 8.2.5.2 Successful Operation .....                           | 21 |
+| 8.2.5.3 Unsuccessful Operation .....                         | 22 |
+| 8.2.5.4 Abnormal Conditions.....                             | 22 |
+| 8.2.6 ng-eNB-DU Resource Coordination .....                  | 22 |
+| 8.2.6.1 General.....                                         | 22 |
+| 8.2.6.2 Successful Operation .....                           | 22 |
+| 8.2.7 ng-eNB-DU Status Indication .....                      | 23 |
+| 8.2.7.1 General.....                                         | 23 |
+| 8.2.7.2 Successful Operation .....                           | 23 |
+| 8.2.7.3 Abnormal Conditions.....                             | 23 |
+| 8.3 UE Context Management procedures .....                   | 23 |
+| 8.3.1 UE Context Setup .....                                 | 23 |
+| 8.3.1.1 General.....                                         | 23 |
+
+|         |                                                             |    |
+|---------|-------------------------------------------------------------|----|
+| 8.3.1.2 | Successful Operation .....                                  | 24 |
+| 8.3.1.3 | Unsuccessful Operation .....                                | 25 |
+| 8.3.1.4 | Abnormal Conditions.....                                    | 25 |
+| 8.3.2   | UE Context Release Request (ng-eNB-DU initiated) .....      | 25 |
+| 8.3.2.1 | General.....                                                | 25 |
+| 8.3.2.2 | Successful Operation .....                                  | 26 |
+| 8.3.2.3 | Abnormal Conditions.....                                    | 26 |
+| 8.3.3   | UE Context Release (ng-eNB-CU initiated) .....              | 26 |
+| 8.3.3.1 | General.....                                                | 26 |
+| 8.3.3.2 | Successful Operation .....                                  | 26 |
+| 8.3.3.4 | Abnormal Conditions.....                                    | 27 |
+| 8.3.4   | UE Context Modification (ng-eNB-CU initiated).....          | 27 |
+| 8.3.4.1 | General.....                                                | 27 |
+| 8.3.4.2 | Successful Operation .....                                  | 27 |
+| 8.3.4.3 | Unsuccessful Operation .....                                | 29 |
+| 8.3.4.4 | Abnormal Conditions.....                                    | 29 |
+| 8.3.5   | UE Context Modification Required (ng-eNB-DU initiated)..... | 29 |
+| 8.3.5.1 | General.....                                                | 29 |
+| 8.3.5.2 | Successful Operation .....                                  | 29 |
+| 8.3.5.3 | Unsuccessful Operation .....                                | 30 |
+| 8.3.5.4 | Abnormal Conditions.....                                    | 30 |
+| 8.3.6   | UE Inactivity Notification .....                            | 30 |
+| 8.3.6.1 | General.....                                                | 30 |
+| 8.3.6.2 | Successful Operation .....                                  | 30 |
+| 8.3.6.3 | Abnormal Conditions.....                                    | 30 |
+| 8.3.7   | Notify.....                                                 | 31 |
+| 8.3.7.1 | General.....                                                | 31 |
+| 8.3.7.2 | Successful Operation .....                                  | 31 |
+| 8.3.7.3 | Abnormal Conditions.....                                    | 31 |
+| 8.4     | RRC Message Transfer procedures.....                        | 31 |
+| 8.4.1   | Initial UL RRC Message Transfer.....                        | 31 |
+| 8.4.1.1 | General.....                                                | 31 |
+| 8.4.1.2 | Successful operation .....                                  | 32 |
+| 8.4.1.3 | Abnormal Conditions.....                                    | 32 |
+| 8.4.2   | DL RRC Message Transfer .....                               | 32 |
+| 8.4.2.1 | General.....                                                | 32 |
+| 8.4.2.2 | Successful operation .....                                  | 32 |
+| 8.4.2.3 | Abnormal Conditions.....                                    | 33 |
+| 8.4.3   | UL RRC Message Transfer .....                               | 33 |
+| 8.4.3.1 | General.....                                                | 33 |
+| 8.4.3.2 | Successful operation .....                                  | 33 |
+| 8.4.3.3 | Abnormal Conditions.....                                    | 33 |
+| 8.4.4   | RRC Delivery Report .....                                   | 33 |
+| 8.5     | Warning Message Transmission Procedures.....                | 33 |
+| 8.5.1   | Write-Replace Warning.....                                  | 33 |
+| 8.5.1.1 | General.....                                                | 33 |
+| 8.5.1.2 | Successful Operation .....                                  | 34 |
+| 8.5.1.3 | Unsuccessful Operation .....                                | 34 |
+| 8.5.1.4 | Abnormal Conditions.....                                    | 34 |
+| 8.5.2   | PWS Cancel.....                                             | 35 |
+| 8.5.2.1 | General.....                                                | 35 |
+| 8.5.2.2 | Successful Operation .....                                  | 35 |
+| 8.5.2.3 | Unsuccessful Operation .....                                | 35 |
+| 8.5.3   | PWS Restart Indication .....                                | 36 |
+| 8.5.3.1 | General.....                                                | 36 |
+| 8.5.3.2 | Successful Operation .....                                  | 36 |
+| 8.5.3.3 | Abnormal Conditions.....                                    | 36 |
+| 8.5.4   | PWS Failure Indication .....                                | 36 |
+| 8.5.4.1 | General.....                                                | 36 |
+| 8.5.4.2 | Successful Operation .....                                  | 36 |
+| 8.5.4.3 | Abnormal Conditions.....                                    | 37 |
+| 8.6     | Paging procedures .....                                     | 37 |
+
+|          |                                                  |    |
+|----------|--------------------------------------------------|----|
+| 8.6.1    | Paging .....                                     | 37 |
+| 8.6.1.1  | General .....                                    | 37 |
+| 8.6.1.2  | Successful Operation .....                       | 37 |
+| 8.6.1.3  | Abnormal Conditions .....                        | 37 |
+| 9        | Elements for W1AP Communication .....            | 37 |
+| 9.1      | General .....                                    | 37 |
+| 9.2      | Message Functional Defintion and Content .....   | 38 |
+| 9.2.1    | Interface Management messages .....              | 38 |
+| 9.2.1.1  | RESET .....                                      | 38 |
+| 9.2.1.2  | RESET ACKNOWLEDGE .....                          | 38 |
+| 9.2.1.3  | ERROR INDICATION .....                           | 39 |
+| 9.2.1.4  | W1 SETUP REQUEST .....                           | 39 |
+| 9.2.1.5  | W1 SETUP RESPONSE .....                          | 40 |
+| 9.2.1.6  | W1 SETUP FAILURE .....                           | 41 |
+| 9.2.1.7  | NG-ENB-DU CONFIGURATION UPDATE .....             | 41 |
+| 9.2.1.8  | NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE ..... | 42 |
+| 9.2.1.9  | NG-ENB-DU CONFIGURATION UPDATE FAILURE .....     | 43 |
+| 9.2.1.10 | NG-ENB-CU CONFIGURATION UPDATE .....             | 43 |
+| 9.2.1.11 | NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE ..... | 44 |
+| 9.2.1.12 | NG-ENB-CU CONFIGURATION UPDATE FAILURE .....     | 45 |
+| 9.2.1.13 | NG-ENB-DU RESOURCE COORDINATION REQUEST .....    | 45 |
+| 9.2.1.14 | NG-ENB-DU RESOURCE COORDINATION RESPONSE .....   | 45 |
+| 9.2.1.15 | NG-ENB-DU STATUS INDICATION .....                | 46 |
+| 9.2.2    | UE Context Management messages .....             | 46 |
+| 9.2.2.1  | UE CONTEXT SETUP REQUEST .....                   | 46 |
+| 9.2.2.2  | UE CONTEXT SETUP RESPONSE .....                  | 49 |
+| 9.2.2.3  | UE CONTEXT SETUP FAILURE .....                   | 51 |
+| 9.2.2.4  | UE CONTEXT RELEASE REQUEST .....                 | 51 |
+| 9.2.2.5  | UE CONTEXT RELEASE COMMAND .....                 | 51 |
+| 9.2.2.6  | UE CONTEXT RELEASE COMPLETE .....                | 52 |
+| 9.2.2.7  | UE CONTEXT MODIFICATION REQUEST .....            | 52 |
+| 9.2.2.8  | UE CONTEXT MODIFICATION RESPONSE .....           | 56 |
+| 9.2.2.9  | UE CONTEXT MODIFICATION FAILURE .....            | 58 |
+| 9.2.2.10 | UE CONTEXT MODIFICATION REQUIRED .....           | 58 |
+| 9.2.2.11 | UE CONTEXT MODIFICATION CONFIRM .....            | 59 |
+| 9.2.2.12 | UE CONTEXT MODIFICATION REFUSE .....             | 60 |
+| 9.2.2.13 | UE INACTIVITY NOTIFICATION .....                 | 60 |
+| 9.2.2.14 | NOTIFY .....                                     | 61 |
+| 9.2.3    | RRC Message Transfer messages .....              | 61 |
+| 9.2.3.1  | INITIAL UL RRC MESSAGE TRANSFER .....            | 61 |
+| 9.2.3.2  | DL RRC MESSAGE TRANSFER .....                    | 62 |
+| 9.2.3.3  | UL RRC MESSAGE TRANSFER .....                    | 62 |
+| 9.2.4    | Warning Message Transmission Messages .....      | 63 |
+| 9.2.4.1  | WRITE-REPLACE WARNING REQUEST .....              | 63 |
+| 9.2.4.2  | WRITE-REPLACE WARNING RESPONSE .....             | 63 |
+| 9.2.4.3  | PWS CANCEL REQUEST .....                         | 64 |
+| 9.2.4.4  | PWS CANCEL RESPONSE .....                        | 64 |
+| 9.2.4.5  | PWS RESTART INDICATION .....                     | 65 |
+| 9.2.4.6  | PWS FAILURE INDICATION .....                     | 66 |
+| 9.2.5    | Paging messages .....                            | 66 |
+| 9.2.5.1  | PAGING .....                                     | 66 |
+| 9.3      | Information Element Definitions .....            | 67 |
+| 9.3.1    | Radio Network Layer Related IEs .....            | 67 |
+| 9.3.1.1  | Message Type .....                               | 67 |
+| 9.3.1.2  | Cause .....                                      | 67 |
+| 9.3.1.3  | PWS System Information .....                     | 69 |
+| 9.3.1.4  | ng-eNB-CU UE W1AP ID .....                       | 69 |
+| 9.3.1.5  | ng-eNB-DU UE W1AP ID .....                       | 69 |
+| 9.3.1.6  | RRC-Container .....                              | 70 |
+| 9.3.1.7  | SRB ID .....                                     | 70 |
+| 9.3.1.8  | DRB ID .....                                     | 70 |
+
+|          |                                                     |    |
+|----------|-----------------------------------------------------|----|
+| 9.3.1.9  | ng-eNB-DU ID .....                                  | 70 |
+| 9.3.1.10 | Served Cell Information.....                        | 70 |
+| 9.3.1.11 | Transmission Action Indicator.....                  | 72 |
+| 9.3.1.12 | E-UTRAN CGI .....                                   | 72 |
+| 9.3.1.13 | Repetition Period .....                             | 72 |
+| 9.3.1.14 | PLMN Identity .....                                 | 73 |
+| 9.3.1.15 | Transmission Bandwidth .....                        | 73 |
+| 9.3.1.16 | Void .....                                          | 73 |
+| 9.3.1.17 | E-UTRAN Frequency Info .....                        | 73 |
+| 9.3.1.18 | ng-eNB-DU System Information.....                   | 74 |
+| 9.3.1.19 | E-UTRAN QoS.....                                    | 74 |
+| 9.3.1.20 | Allocation and Retention Priority .....             | 74 |
+| 9.3.1.21 | GBR QoS Information .....                           | 75 |
+| 9.3.1.22 | Bit Rate .....                                      | 75 |
+| 9.3.1.23 | Transaction ID .....                                | 76 |
+| 9.3.1.24 | DRX Cycle.....                                      | 76 |
+| 9.3.1.25 | RLC Mode .....                                      | 76 |
+| 9.3.1.26 | 5GS TAC .....                                       | 76 |
+| 9.3.1.27 | Void .....                                          | 76 |
+| 9.3.1.28 | RRC Reconfiguration Complete Indicator .....        | 76 |
+| 9.3.1.29 | C-RNTI .....                                        | 77 |
+| 9.3.1.30 | RAT-Frequency Priority Information .....            | 77 |
+| 9.3.1.31 | Slice Support List.....                             | 77 |
+| 9.3.1.32 | S-NSSAI .....                                       | 77 |
+| 9.3.1.33 | ng-eNB-CU System Information .....                  | 77 |
+| 9.3.1.34 | QoS Flow Level QoS Parameters .....                 | 78 |
+| 9.3.1.35 | GBR QoS Flow Information.....                       | 78 |
+| 9.3.1.36 | Dynamic 5QI Descriptor.....                         | 79 |
+| 9.3.1.37 | NG-RAN Allocation and Retention Priority .....      | 79 |
+| 9.3.1.38 | Non Dynamic 5QI Descriptor.....                     | 80 |
+| 9.3.1.39 | Maximum Packet Loss Rate .....                      | 81 |
+| 9.3.1.40 | Packet Delay Budget.....                            | 81 |
+| 9.3.1.41 | Packet Error Rate .....                             | 81 |
+| 9.3.1.42 | Averaging Window .....                              | 81 |
+| 9.3.1.43 | Maximum Data Burst Volume.....                      | 82 |
+| 9.3.1.44 | Notification Control.....                           | 82 |
+| 9.3.1.45 | RAN Area Code.....                                  | 82 |
+| 9.3.1.46 | QoS Flow Identifier .....                           | 82 |
+| 9.3.1.47 | Available PLMN List.....                            | 82 |
+| 9.3.1.48 | Service Status.....                                 | 82 |
+| 9.3.1.49 | RLC Status.....                                     | 83 |
+| 9.3.1.50 | Void .....                                          | 83 |
+| 9.3.1.51 | QoS Flow Mapping Indication .....                   | 83 |
+| 9.3.1.52 | Resource Coordination Transfer Information .....    | 83 |
+| 9.3.1.53 | E-UTRA PRACH Configuration.....                     | 83 |
+| 9.3.1.54 | Resource Coordination E-UTRA Cell Information ..... | 84 |
+| 9.3.1.55 | Extended Available PLMN List .....                  | 86 |
+| 9.3.1.56 | void .....                                          | 86 |
+| 9.3.1.57 | CU to DU RRC Information.....                       | 86 |
+| 9.3.1.58 | DU to CU RRC Information.....                       | 86 |
+| 9.3.1.59 | E-UTRA Transmission Bandwidth.....                  | 87 |
+| 9.3.1.60 | Number of Broadcasts Requested.....                 | 87 |
+| 9.3.1.61 | Criticality Diagnostics .....                       | 87 |
+| 9.3.1.62 | Cell Type.....                                      | 88 |
+| 9.3.1.63 | UE Identity Index value .....                       | 88 |
+| 9.3.1.64 | RAN UE Paging identity .....                        | 88 |
+| 9.3.1.65 | CN UE Paging Identity .....                         | 89 |
+| 9.3.1.66 | Paging DRX.....                                     | 89 |
+| 9.3.1.67 | Message Identifier.....                             | 89 |
+| 9.3.1.68 | Serial Number .....                                 | 89 |
+| 9.3.1.69 | Additional SIB Message List.....                    | 89 |
+| 9.3.1.70 | Paging Origin.....                                  | 90 |
+
+|                                                    |                                                                    |            |
+|----------------------------------------------------|--------------------------------------------------------------------|------------|
+| 9.3.2                                              | Transport Network Layer Related IEs.....                           | 90         |
+| 9.3.2.1                                            | UP Transport Layer Information .....                               | 90         |
+| 9.3.2.2                                            | GTP-TEID .....                                                     | 90         |
+| 9.3.2.3                                            | Transport Layer Address .....                                      | 90         |
+| 9.4                                                | Message and Information Element Abstract Syntax (with ASN.1) ..... | 91         |
+| 9.4.1                                              | General .....                                                      | 91         |
+| 9.4.2                                              | Usage of private message mechanism for non-standard use .....      | 91         |
+| 9.4.3                                              | Elementary Procedure Definitions.....                              | 91         |
+| 9.4.4                                              | PDU Definitions .....                                              | 96         |
+| 9.4.5                                              | Information Element Definitions.....                               | 116        |
+| 9.4.6                                              | Common Definitions .....                                           | 138        |
+| 9.4.7                                              | Constant Definitions .....                                         | 138        |
+| 9.4.8                                              | Container Definitions .....                                        | 141        |
+| 9.5                                                | Message Transfer Syntax .....                                      | 143        |
+| 9.6                                                | Timers.....                                                        | 143        |
+| 10                                                 | Handling of unknown, unforeseen and erroneous protocol data .....  | 144        |
+| <b>Annex A (informative): Change History .....</b> |                                                                    | <b>145</b> |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# --- 1 Scope
+
+The present document specifies the 5G radio network layer signalling protocol for the W1 interface. The W1 interface provides means for interconnecting a ng-eNB-CU and a ng-eNB-DU of a ng-eNB within an NG-RAN. The W1 Application Protocol (W1AP) supports the functions of W1 interface by signalling procedures defined in the present document. W1AP is developed in accordance to the general principles stated in TS 38.401 [4] and TS 37.470 [5].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRAN); Radio Resource Control (RRC) Protocol Specification".
+- [3] 3GPP TS 36.401: "E-UTRAN Architecture Description".
+- [4] 3GPP TS 38.401: "NG-RAN; Architecture Description".
+- [5] 3GPP TS 37.470: "E-UTRAN and NG-RAN; W1 general aspects and principles".
+- [6] 3GPP TS 38.300: "NR; Overall description; Stage-2".
+- [7] 3GPP TS 38.423: "NG-RAN; Xn application protocol (XnAP)".
+- [8] 3GPP TS 23.501: "System Architecture for the 5G System (5GS)".
+- [9] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
+- [10] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
+- [11] 3GPP TS 23.203: "Policy and charging control architecture".
+- [12] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)".
+- [13] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation".
+- [14] 3GPP TS 36.104: "Base Station (BS) radio transmission and reception".
+- [15] 3GPP TS 36.321: " Evolved Universal Terrestrial Radio Access (E-UTRAN); Medium Access Control (MAC) protocol specification".
+- [16] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
+- [17] 3GPP TS 29.281: "General Packet Radio System (GPRS); Tunnelling Protocol User Plane (GTPv1-U) ".
+- [18] 3GPP TS 38.414: "NG-RAN; NG data transport".
+
+- [19] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
+- [20] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA), User Equipment (UE) procedures in idle mode".
+- [21] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)".
+- [22] ITU-T Recommendation X.680 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation".
+- [23] ITU-T Recommendation X.681 (07/2002): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification".
+
+# 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**elementary procedure:** WIAP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between ng-eNB-CU and ng-eNB-DU. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone procedures, which can be active in parallel. The usage of several WIAP EPs together is specified in stage 2 specifications (e.g., TS 37.470 [5]).
+
+An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
+
+- **Class 1:** Elementary Procedures with response (success and/or failure).
+- **Class 2:** Elementary Procedures without response.
+
+For Class 1 EPs, the types of responses can be as follows:
+
+Successful:
+
+- A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.
+
+Unsuccessful:
+
+- A signalling message explicitly indicates that the EP failed.
+- On time supervision expiry (i.e., absence of expected response).
+
+Successful and Unsuccessful:
+
+- One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome.
+
+Class 2 EPs are considered always successful.
+
+**NGEN-DC operation:** Used in the present document when the WIAP is applied for **ng-eNB-CU** and **ng-eNB-DU** in NG-RAN.
+
+**ng-eNB:** As defined in TS 38.300 [6].
+
+**ng-eNB-CU:** As defined in TS 37.470 [5].
+
+**ng-eNB-DU:** As defined in TS 37.470 [5].
+
+**ng-eNB-CU UE W1AP ID:** As defined in TS 38.401 [4].
+
+**ng-eNB-DU UE W1AP ID:** As defined in TS 38.401 [4].
+
+**UE-associated signalling:** When W1AP messages associated to one UE uses the UE-associated logical W1-connection for association of the message to the UE in ng-eNB-DU and ng-eNB-CU.
+
+**UE-associated logical W1-connection:** The UE-associated logical W1-connection uses the identities *ng-eNB-CU UE W1AP ID* and *ng-eNB-DU UE W1AP ID* according to the definition in TS 38.401 [4]. For a received UE associated W1AP message the ng-eNB-CU identifies the associated UE based on the *ng-eNB-CU UE W1AP ID* IE and the ng-eNB-DU identifies the associated UE based on the *ng-eNB-DU UE W1AP ID* IE. The UE-associated logical W1-connection may exist before the W1 UE context is setup in ng-eNB-DU.
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply.
+
+An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|         |                                                       |
+|---------|-------------------------------------------------------|
+| 5GC     | 5G Core Network                                       |
+| 5QI     | 5G QoS Identifier                                     |
+| AMF     | Access and Mobility Management Function               |
+| CN      | Core Network                                          |
+| CG      | Cell Group                                            |
+| CGI     | Cell Global Identifier                                |
+| DL      | Downlink                                              |
+| EN-DC   | E-UTRA-NR Dual Connectivity                           |
+| NE-DC   | NR-E-UTRA Dual Connectivity                           |
+| NGEN-DC | NG-RAN E-UTRA-NR Dual Connectivity                    |
+| NSSAI   | Network Slice Selection Assistance Information        |
+| RANAC   | RAN Area Code                                         |
+| RRC     | Radio Resource Control                                |
+| S-NSSAI | Single Network Slice Selection Assistance Information |
+| TAC     | Tracking Area Code                                    |
+| TAI     | Tracking Area Identity                                |
+
+# 4 General
+
+## 4.1 Procedure specification principles
+
+The principle for specifying the procedure logic is to specify the functional behaviour of the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system.
+
+The following specification principles have been applied for the procedure text in clause 8:
+
+- The procedure text discriminates between:
+  - 1) Functionality which "shall" be executed.
+
+The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
+
+- 2) Functionality which "shall, if supported" be executed.
+
+The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
+
+- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including *Criticality Diagnostics* IE, see clause 10.
+
+## 4.2 Forwards and backwards compatibility
+
+The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.
+
+## 4.3 Specification notations
+
+For the purposes of the present document, the following notations apply:
+
+|                |                                                                                                                                                                                                                                                                           |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure      | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. Handover Preparation procedure.                                          |
+| Message        | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. HANDOVER REQUEST message.                                                                                     |
+| IE             | When referring to an information element (IE) in the specification the <i>Information Element Name</i> is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. <i>E-RAB ID</i> IE. |
+| Value of an IE | When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in the specification enclosed by quotation marks, e.g. "Value".                                                                                 |
+
+# --- 5 W1AP services
+
+W1AP provides the signalling service between ng-eNB-DU and the ng-eNB-CU that is required to fulfil the W1AP functions described in clause 7. W1AP services are divided into two groups:
+
+|                             |                                                                                                                                                                             |
+|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Non UE-associated services: | They are related to the whole W1 interface instance between the ng-eNB-DU and ng-eNB-CU utilising a non UE-associated signalling connection.                                |
+| UE-associated services:     | They are related to one UE. W1AP functions that provide these services are associated with a UE-associated signalling connection that is maintained for the UE in question. |
+
+Unless explicitly indicated in the procedure specification, at any instance in time one protocol endpoint shall have a maximum of one ongoing W1AP procedure related to a certain UE.
+
+# --- 6 Services expected from signalling transport
+
+The signalling connection shall provide in sequence delivery of W1AP messages. W1AP shall be notified if the signalling connection breaks.
+
+# --- 7 Functions of W1AP
+
+The functions of W1AP are described in TS 37.470 [5].
+
+# 8 W1AP procedures
+
+## 8.1 List of W1AP Elementary procedures
+
+In the following tables, all EPs are divided into Class 1 and Class 2 EPs:
+
+**Table 8.1-1: Class 1 procedures**
+
+| Elementary Procedure                                   | Initiating Message                      | Successful Outcome                         | Unsuccessful Outcome                   |
+|--------------------------------------------------------|-----------------------------------------|--------------------------------------------|----------------------------------------|
+|                                                        |                                         | Response message                           | Response message                       |
+| Reset                                                  | RESET                                   | RESET ACKNOWLEDGE                          |                                        |
+| W1 Setup                                               | W1 SETUP REQUEST                        | W1 SETUP RESPONSE                          | W1 SETUP FAILURE                       |
+| ng-eNB-DU Configuration Update                         | NG-ENB-DU CONFIGURATION UPDATE          | NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE | NG-ENB-DU CONFIGURATION UPDATE FAILURE |
+| ng-eNB-CU Configuration Update                         | NG-ENB-CU CONFIGURATION UPDATE          | NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE | NG-ENB-CU CONFIGURATION UPDATE FAILURE |
+| UE Context Setup                                       | UE CONTEXT SETUP REQUEST                | UE CONTEXT SETUP RESPONSE                  | UE CONTEXT SETUP FAILURE               |
+| UE Context Release (ng-eNB-CU initiated)               | UE CONTEXT RELEASE COMMAND              | UE CONTEXT RELEASE COMPLETE                |                                        |
+| UE Context Modification (ng-eNB-CU initiated)          | UE CONTEXT MODIFICATION REQUEST         | UE CONTEXT MODIFICATION RESPONSE           | UE CONTEXT MODIFICATION FAILURE        |
+| UE Context Modification Required (ng-eNB-DU initiated) | UE CONTEXT MODIFICATION REQUIRED        | UE CONTEXT MODIFICATION CONFIRM            | UE CONTEXT MODIFICATION REFUSE         |
+| Write-Replace Warning                                  | WRITE-REPLACE WARNING REQUEST           | WRITE-REPLACE WARNING RESPONSE             |                                        |
+| PWS Cancel                                             | PWS CANCEL REQUEST                      | PWS CANCEL RESPONSE                        |                                        |
+| NG-ENB-DU RESOURCE COORDINATION                        | NG-ENB-DU RESOURCE COORDINATION REQUEST | NG-ENB-DU RESOURCE COORDINATION RESPONSE   |                                        |
+
+**Table 8.2-2: Class 2 procedures**
+
+| Elementary Procedure                             | Message                             |
+|--------------------------------------------------|-------------------------------------|
+| Error Indication                                 | ERROR INDICATION                    |
+| UE Context Release Request (ng-eNB-DU initiated) | UE CONTEXT RELEASE REQUEST          |
+| Initial UL RRC Message Transfer                  | INITIAL UL RRC MESSAGE TRANSFER     |
+| DL RRC Message Transfer                          | DL RRC MESSAGE TRANSFER             |
+| UL RRC Message Transfer                          | UL RRC MESSAGE TRANSFER             |
+| UE Inactivity Notification                       | UE INACTIVITY NOTIFICATION          |
+| System Information Delivery                      | SYSTEM INFORMATION DELIVERY COMMAND |
+| Paging                                           | PAGING                              |
+| Notify                                           | NOTIFY                              |
+| PWS Restart Indication                           | PWS RESTART INDICATION              |
+| PWS Failure Indication                           | PWS FAILURE INDICATION              |
+| ng-eNB-DU Status Indication                      | NG-ENB-DU STATUS INDICATION         |
+| RRC Delivery Report                              | RRC DELIVERY REPORT                 |
+
+## 8.2 Interface Management procedures
+
+### 8.2.1 Reset
+
+#### 8.2.1.1 General
+
+The purpose of the Reset procedure is to initialise or re-initialise the WIAP UE-related contexts, in the event of a failure in the ng-eNB-CU or ng-eNB-DU. This procedure does not affect the application level configuration data exchanged during, e.g., the W1 Setup procedure.
+
+The procedure uses non-UE associated signalling.
+
+#### 8.2.1.2 Successful Operation
+
+##### 8.2.1.2.1 Reset Procedure Initiated from the ng-eNB-CU
+
+![Sequence diagram showing the Reset procedure initiated from the ng-eNB-CU. The ng-eNB-CU sends a RESET message to the ng-eNB-DU, and the ng-eNB-DU responds with a RESET ACKNOWLEDGE message.](70de8885bd7de15723aaad5eb5c5febf_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: Initiate Reset
+    ng-eNB-CU->>ng-eNB-DU: RESET
+    Note right of ng-eNB-DU: Release resources
+    ng-eNB-DU->>ng-eNB-CU: RESET ACKNOWLEDGE
+  
+```
+
+Sequence diagram showing the Reset procedure initiated from the ng-eNB-CU. The ng-eNB-CU sends a RESET message to the ng-eNB-DU, and the ng-eNB-DU responds with a RESET ACKNOWLEDGE message.
+
+**Figure 8.2.1.2.1-1: Reset procedure initiated from the ng-eNB-CU. Successful operation**
+
+In the event of a failure at the ng-eNB-CU, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the ng-eNB-DU.
+
+At reception of the RESET message the ng-eNB-DU shall release all allocated resources on W1 and radio resources related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the indicated UE contexts including WIAP ID.
+
+After the ng-eNB-DU has released all assigned W1 resources and the UE WIAP IDs for all indicated UE associations which can be used for new UE-associated logical W1-connections over the W1 interface, the ng-eNB-DU shall respond with the RESET ACKNOWLEDGE message. The ng-eNB-DU does not need to wait for the release of radio resources to be completed before returning the RESET ACKNOWLEDGE message.
+
+If the RESET message contains the *UE-associated logical W1-connection list* IE, then:
+
+- The ng-eNB-DU shall use the *ng-eNB-CU UE WIAP ID* IE and/or the *ng-eNB-DU UE WIAP ID* IE to explicitly identify the UE association(s) to be reset.
+- The ng-eNB-DU shall include in the RESET ACKNOWLEDGE message, for each UE association to be reset, the *UE-associated logical W1-connection Item* IE in the *UE-associated logical W1-connection list* IE. The *UE-associated logical W1-connection Item* IEs shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical W1-connections. Empty *UE-associated logical W1-connection Item* IEs, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message.
+- If the *ng-eNB-CU UE WIAP ID* IE is included in the *UE-associated logical W1-connection Item* IE for a UE association, the ng-eNB-DU shall include the *ng-eNB-CU UE WIAP ID* IE in the corresponding *UE-associated logical W1-connection Item* IE in the RESET ACKNOWLEDGE message.
+- If the *ng-eNB-DU UE WIAP ID* IE is included in the *UE-associated logical W1-connection Item* IE for a UE association, the ng-eNB-DU shall include the *ng-eNB-DU UE WIAP ID* IE in the corresponding *UE-associated logical W1-connection Item* IE in the RESET ACKNOWLEDGE message.
+
+###### Interactions with other procedures:
+
+If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same W1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted.
+
+##### 8.2.1.2.2 Reset Procedure Initiated from the ng-eNB-DU
+
+![Sequence diagram showing the Reset procedure initiated from the ng-eNB-DU. The ng-eNB-DU sends a RESET message to the ng-eNB-CU, and the ng-eNB-CU responds with a RESET ACKNOWLEDGE message.](41a438d7e4adc17c3a4005e7c9500091_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: RESET
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: RESET ACKNOWLEDGE
+    Note left of ng-eNB-DU: 
+  
+```
+
+Sequence diagram showing the Reset procedure initiated from the ng-eNB-DU. The ng-eNB-DU sends a RESET message to the ng-eNB-CU, and the ng-eNB-CU responds with a RESET ACKNOWLEDGE message.
+
+**Figure 8.2.1.2.2-1: Reset procedure initiated from the ng-eNB-DU. Successful operation**
+
+In the event of a failure at the ng-eNB-DU, which has resulted in the loss of some or all transaction reference information, a RESET message shall be sent to the ng-eNB-CU.
+
+At reception of the RESET message the ng-eNB-CU shall release all allocated resources on W1 related to the UE association(s) indicated explicitly or implicitly in the RESET message and remove the WIAP ID for the indicated UE associations.
+
+After the ng-eNB-CU has released all assigned W1 resources and the UE WIAP IDs for all indicated UE associations which can be used for new UE-associated logical W1-connections over the W1 interface, the ng-eNB-CU shall respond with the RESET ACKNOWLEDGE message.
+
+If the RESET message contains the *UE-associated logical W1-connection list IE*, then:
+
+- The ng-eNB-CU shall use the *ng-eNB-CU UE WIAP ID IE* and/or the *ng-eNB-DU UE WIAP ID IE* to explicitly identify the UE association(s) to be reset.
+- The ng-eNB-CU shall in the RESET ACKNOWLEDGE message include, for each UE association to be reset, the *UE-associated logical W1-connection Item IE* in the *UE-associated logical W1-connection list IE*. The *UE-associated logical W1-connection Item IE* shall be in the same order as received in the RESET message and shall include also unknown UE-associated logical W1-connections. Empty *UE-associated logical W1-connection Item IE*s, received in the RESET message, may be omitted in the RESET ACKNOWLEDGE message.
+- If the *ng-eNB-CU UE WIAP ID IE* is included in the *UE-associated logical W1-connection Item IE* for a UE association, the ng-eNB-CU shall include the *ng-eNB-CU UE WIAP ID IE* in the corresponding *UE-associated logical W1-connection Item IE* in the RESET ACKNOWLEDGE message.
+- If the *ng-eNB-DU UE WIAP ID IE* is included in a *UE-associated logical W1-connection Item IE* for a UE association, the ng-eNB-CU shall include the *ng-eNB-DU UE WIAP ID IE* in the corresponding *UE-associated logical W1-connection Item IE* in the RESET ACKNOWLEDGE message.
+
+###### Interactions with other procedures:
+
+If the RESET message is received, any other ongoing procedure (except for another Reset procedure) on the same W1 interface related to a UE association, indicated explicitly or implicitly in the RESET message, shall be aborted.
+
+#### 8.2.1.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.2.2 Error Indication
+
+#### 8.2.2.1 General
+
+The Error Indication procedure is initiated by a node in order to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message.
+
+If the error situation arises due to reception of a message utilising UE associated signalling, then the Error Indication procedure uses UE associated signalling. Otherwise the procedure uses non-UE associated signalling.
+
+#### 8.2.2.2 Successful Operation
+
+![Sequence diagram showing the Error Indication procedure originating from the ng-eNB-CU to the ng-eNB-DU.](43837b056625d3d6ce615e4c02f163bb_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU->>ng-eNB-DU: ERROR INDICATION
+```
+
+A sequence diagram illustrating the Error Indication procedure. It features two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. Each lifeline has a solid black horizontal bar at its base. A horizontal arrow labeled "ERROR INDICATION" points from the ng-eNB-CU lifeline to the ng-eNB-DU lifeline.
+
+Sequence diagram showing the Error Indication procedure originating from the ng-eNB-CU to the ng-eNB-DU.
+
+Figure 8.2.2.2-1: Error Indication procedure, ng-eNB-CU originated. Successful operation
+
+![Sequence diagram showing the Error Indication procedure originating from the ng-eNB-DU to the ng-eNB-CU.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    Note right of ng-eNB-CU: 
+    ng-eNB-DU->>ng-eNB-CU: ERROR INDICATION
+```
+
+A sequence diagram illustrating the Error Indication procedure. It features two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. Each lifeline has a solid black horizontal bar at its base. A horizontal arrow labeled "ERROR INDICATION" points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline.
+
+Sequence diagram showing the Error Indication procedure originating from the ng-eNB-DU to the ng-eNB-CU.
+
+Figure 8.2.2.2-2: Error Indication procedure, ng-eNB-DU originated. Successful operation
+
+When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node.
+
+The ERROR INDICATION message shall contain at least the *Cause* IE. In case the Error Indication procedure is triggered by utilising UE associated signalling the *ng-eNB-CU UE WIAP ID* IE and *ng-eNB-DU UE WIAP ID* IE shall be included in the ERROR INDICATION message. If one or both of the *ng-eNB-CU UE WIAP ID* IE and the *ng-eNB-DU UE WIAP ID* IE are not correct, the cause shall be set to appropriate value, e.g., "Unknown or already allocated ng-eNB-CU UE WIAP ID", "Unknown or already allocated ng-eNB-DU UE WIAP ID" or "Unknown or inconsistent pair of UE WIAP ID".
+
+#### 8.2.2.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.2.3 W1 Setup
+
+#### 8.2.3.1 General
+
+The purpose of the W1 Setup procedure is to exchange application level data needed for the ng-eNB-DU and the ng-eNB-CU to correctly interoperate on the W1 interface. The procedure uses non-UE associated signalling. This procedure shall be the first WIAP procedure triggered for the W1-C interface instance after a TNL association has become operational.
+
+The procedure uses non-UE associated signalling.
+
+This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also re-initialises the WIAP UE-related contexts (if any) and erases all related signalling connections in the two nodes like a Reset procedure would do.
+
+#### 8.2.3.2 Successful Operation
+
+![Sequence diagram of the W1 Setup procedure showing a request from ng-eNB-DU to ng-eNB-CU and a response back.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: W1 SETUP REQUEST
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: W1 SETUP RESPONSE
+    Note left of ng-eNB-DU: 
+```
+
+Sequence diagram of the W1 Setup procedure showing a request from ng-eNB-DU to ng-eNB-CU and a response back.
+
+Figure 8.2.3.2-1: W1 Setup procedure: Successful Operation
+
+The ng-eNB-DU initiates the procedure by sending a W1 SETUP REQUEST message including the appropriate data to the ng-eNB-CU. The ng-eNB-CU responds with a W1 SETUP RESPONSE message including the appropriate data.
+
+The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the W1 interface is operational and other W1 messages may be exchanged.
+
+If the W1 SETUP REQUEST message contains the *ng-eNB-DU Served Cells List IE*, the ng-eNB-CU shall take into account as specified in TS 38.401 [4].
+
+If *ng-eNB-DU System Information IE* is included in the W1 SETUP REQUEST message, the ng-eNB-CU shall take into account, and the ng-eNB-CU may include the *ng-eNB-CU System Information IE* in the W1 SETUP RESPONSE message. The ng-eNB-DU shall include the *TAI Slice Support List IE* in the W1 SETUP REQUEST message.
+
+The ng-eNB-CU may include the *Cells to be Activated List IE* in the W1 SETUP RESPONSE message. The *Cells to be Activated List IE* includes a list of cells that the ng-eNB-CU requests the ng-eNB-DU to activate. The ng-eNB-DU shall activate the cells included in the *Cells to be Activated List IE* and reconfigure the physical cell identity for cells for which the *E-UTRAN PCI IE* is included.
+
+If the *RAN Area Code IE* is included in the W1 SETUP REQUEST message, the ng-eNB-CU may use it according to TS 38.300 [6].
+
+The ng-eNB-CU may include *Available PLMN List IE*, and optionally also *Extended Available PLMN List IE*, if the available PLMN(s) are different from what ng-eNB-DU has provided in W1 SETUP REQUEST message, ng-eNB-DU shall take this into account and only broadcast the PLMN(s) included in the received Available PLMN list(s).
+
+#### 8.2.3.3 Unsuccessful Operation
+
+![Sequence diagram for W1 Setup procedure: Unsuccessful Operation](10781f43062bf3e9601a1e086710556c_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: W1 SETUP REQUEST
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: W1 SETUP FAILURE
+    Note left of ng-eNB-DU: 
+```
+
+The diagram illustrates the W1 Setup procedure resulting in an unsuccessful operation. It features two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. The ng-eNB-DU sends a 'W1 SETUP REQUEST' message to the ng-eNB-CU. The ng-eNB-CU responds with a 'W1 SETUP FAILURE' message. Both lifelines have a thick horizontal bar at their base, indicating the start of the sequence.
+
+Sequence diagram for W1 Setup procedure: Unsuccessful Operation
+
+**Figure 8.2.3.3-1: W1 Setup procedure: Unsuccessful Operation**
+
+If the ng-eNB-CU cannot accept the setup, it should respond with a W1 SETUP FAILURE and appropriate cause value.
+
+#### 8.2.3.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.2.4 ng-eNB-DU Configuration Update
+
+#### 8.2.4.1 General
+
+The purpose of the ng-eNB-DU Configuration Update procedure is to update application level configuration data needed for the ng-eNB-DU and the ng-eNB-CU to interoperate correctly on the W1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.
+
+#### 8.2.4.2 Successful Operation
+
+![Sequence diagram for ng-eNB-DU Configuration Update procedure: Successful Operation](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: NG-ENB-DU CONFIGURATION UPDATE
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE
+    Note left of ng-eNB-DU: 
+```
+
+The diagram illustrates the ng-eNB-DU Configuration Update procedure resulting in a successful operation. It features two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. The ng-eNB-DU sends a 'NG-ENB-DU CONFIGURATION UPDATE' message to the ng-eNB-CU. The ng-eNB-CU responds with a 'NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE' message. Both lifelines have a thick horizontal bar at their base, indicating the start of the sequence.
+
+Sequence diagram for ng-eNB-DU Configuration Update procedure: Successful Operation
+
+**Figure 8.2.4.2-1: ng-eNB-DU Configuration Update procedure: Successful Operation**
+
+The ng-eNB-DU initiates the procedure by sending an ng-eNB-DU CONFIGURATION UPDATE message to the ng-eNB-CU including an appropriate set of updated configuration data that it has just taken into operational use. The ng-eNB-CU responds with NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall interpret that the corresponding configuration data is not changed and shall continue to operate the W1-C interface with the existing related configuration data.
+
+The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed.
+
+If *Served Cells To Add Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall add cell information according to the information in the *Served Cell Information* IE. If the ng-eNB-DU
+
+*System Information* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall store and replace any previously provided system info if any, and may include the *ng-eNB-CU System Information* IE in the NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message. The *SIB type to Be Updated List* IE shall contain the full list of SIBs to be broadcast.
+
+If *Served Cells To Modify Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall modify information of cell indicated by *Old E-UTRAN CGI* IE according to the information in the *Served Cell Information* IE and overwrite the served cell information for the affected served cell. Further, if the *ng-eNB-DU System Information* IE is present the ng-eNB-CU shall store and replace any previous information received.
+
+If *Served Cells To Delete Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall delete information of cell indicated by *Old E-UTRAN CGI* IE.
+
+If *Cells Status Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall update the information about the cells, as described in TS 38.401 [4].
+
+If *Cells to be Activated List Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the ng-eNB-DU shall activate the cell indicated by *E-UTRAN CGI* IE and reconfigure the physical cell identity for cells for which the *E-UTRAN PCI* IE is included.
+
+If *Cells to be Activated List Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message and the indicated cells are already activated, the ng-eNB-DU shall update the cell information received in *Cells to be Activated List Item* IE.
+
+If *Cells to be Deactivated List Item* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the ng-eNB-DU shall deactivate all the cells with E-UTRAN CGI listed in the IE.
+
+If the *RAN Area Code* IE is contained in the NG-ENB-DU CONFIGURATION UPDATE message, the ng-eNB-CU shall store and replace any previously provided *RAN Area Code* IE by the received *RAN Area Code* IE.
+
+If *Available PLMN List* IE, and optionally also *Extended Available PLMN List* IE, is contained in NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the ng-eNB-DU shall overwrite the whole available PLMN list and update the corresponding system information.
+
+#### 8.2.4.3 Unsuccessful Operation
+
+![Sequence diagram showing the Unsuccessful Operation of the ng-eNB-DU Configuration Update procedure. The ng-eNB-DU sends an NG-ENB-DU CONFIGURATION UPDATE message to the ng-eNB-CU, and the ng-eNB-CU responds with an NG-ENB-DU CONFIGURATION UPDATE FAILURE message.](5c6787bac31274e2dc992efeca74b303_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: NG-ENB-DU CONFIGURATION UPDATE
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: NG-ENB-DU CONFIGURATION UPDATE FAILURE
+    Note left of ng-eNB-DU: 
+```
+
+Sequence diagram showing the Unsuccessful Operation of the ng-eNB-DU Configuration Update procedure. The ng-eNB-DU sends an NG-ENB-DU CONFIGURATION UPDATE message to the ng-eNB-CU, and the ng-eNB-CU responds with an NG-ENB-DU CONFIGURATION UPDATE FAILURE message.
+
+Figure 8.2.4.3-1: ng-eNB-DU Configuration Update procedure: Unsuccessful Operation
+
+If the ng-eNB-CU cannot accept the update, it shall respond with an ng-eNB-DU CONFIGURATION UPDATE FAILURE message and appropriate cause value.
+
+#### 8.2.4.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.2.5 ng-eNB-CU Configuration Update
+
+#### 8.2.5.1 General
+
+The purpose of the ng-eNB-CU Configuration Update procedure is to update application level configuration data needed for the ng-eNB-DU and ng-eNB-CU to interoperate correctly on the W1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling.
+
+#### 8.2.5.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the ng-eNB-CU Configuration Update procedure. The ng-eNB-CU sends an NG-ENB-CU CONFIGURATION UPDATE message to the ng-eNB-DU, and the ng-eNB-DU responds with an NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE message.](73dff6b45b2b9ffd384bab3235f869af_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: 
+    ng-eNB-CU->>ng-eNB-DU: NG-ENB-CU CONFIGURATION UPDATE
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU-->>ng-eNB-CU: NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram showing the successful operation of the ng-eNB-CU Configuration Update procedure. The ng-eNB-CU sends an NG-ENB-CU CONFIGURATION UPDATE message to the ng-eNB-DU, and the ng-eNB-DU responds with an NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE message.
+
+Figure 8.2.5.2-1: ng-eNB-CU Configuration Update procedure: Successful Operation
+
+The ng-eNB-CU initiates the procedure by sending an ng-eNB-CU CONFIGURATION UPDATE message including the appropriate updated configuration data to the ng-eNB-DU. The ng-eNB-DU responds with an ng-eNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. If an information element is not included in the NG-ENB-CU CONFIGURATION UPDATE message, the ng-eNB-DU shall interpret that the corresponding configuration data is not changed and shall continue to operate the W1-C interface with the existing related configuration data.
+
+The updated configuration data shall be stored in the respective node and used as long as there is an operational TNL association or until any further update is performed.
+
+If *Cells to be Activated List Item* IE is contained in the NG-ENB-CU CONFIGURATION UPDATE message, the ng-eNB-DU shall activate the cell indicated by *E-UTRAN CGI* IE and reconfigure the physical cell identity for which the *E-UTRAN PCI* IE is included.
+
+If *Cells to be Deactivated List Item* IE is contained in the NG-ENB-CU CONFIGURATION UPDATE message, the ng-eNB-DU shall deactivate the cell indicated by *E-UTRAN CGI* IE.
+
+If *Cells to be Activated List Item* IE is contained in the NG-ENB-CU CONFIGURATION UPDATE message and the indicated cells are already activated, the ng-eNB-DU shall update the cell information received in *Cells to be Activated List Item* IE.
+
+If the *ng-eNB-CU System Information* IE is contained in the NG-ENB-CU CONFIGURATION UPDATE message, the ng-eNB-DU shall store and replace any previously provided system info if any. The *SIB type to Be Updated List* IE shall contain the full list of SIBs to be broadcast.
+
+If *Available PLMN List* IE, and optionally also *Extended Available PLMN List* IE, is contained in NG-ENB-CU CONFIGURATION UPDATE message, the ng-eNB-DU shall overwrite the whole available PLMN list and update the corresponding system information.
+
+If *Cells Failed to be Activated Item* IE is contained in the NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the ng-eNB-CU shall consider that the indicated cells are out-of-service as defined in TS 38.401 [4].
+
+#### 8.2.5.3 Unsuccessful Operation
+
+![Sequence diagram for Unsuccessful Operation of ng-eNB-CU Configuration Update](09955ff8214ffb6947951fc0f60eb6ab_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: NG-ENB-CU CONFIGURATION UPDATE
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU-->>ng-eNB-CU: NG-ENB-CU CONFIGURATION UPDATE FAILURE
+    Note right of ng-eNB-CU: 
+```
+
+The diagram shows a sequence of messages between an ng-eNB-CU and an ng-eNB-DU. The ng-eNB-CU sends an NG-ENB-CU CONFIGURATION UPDATE message to the ng-eNB-DU. The ng-eNB-DU responds with an NG-ENB-CU CONFIGURATION UPDATE FAILURE message. Both entities are represented by boxes with lifelines extending downwards, and the messages are shown as horizontal arrows between them.
+
+Sequence diagram for Unsuccessful Operation of ng-eNB-CU Configuration Update
+
+Figure 8.2.5.3-1: ng-eNB-CU Configuration Update: Unsuccessful Operation
+
+If the ng-eNB-DU cannot accept the update, it shall respond with an ng-eNB-CU CONFIGURATION UPDATE FAILURE message and appropriate cause value.
+
+#### 8.2.5.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.2.6 ng-eNB-DU Resource Coordination
+
+#### 8.2.6.1 General
+
+The purpose of the ng-eNB-DU Resource Coordination procedure is to enable coordination of radio resource allocation between an ng-eNB-CU and an ng-eNB-DU for the purpose of spectrum sharing between E-UTRA and NR. This procedure is to be used only for the purpose of spectrum sharing between E-UTRA and NR.
+
+The procedure uses non-UE-associated signalling.
+
+#### 8.2.6.2 Successful Operation
+
+![Sequence diagram for Successful Operation of ng-eNB-DU Resource Coordination](db7cb51aac8519daab50e2171cecae82_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-NB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-NB-CU: NG-ENB-DU RESOURCE COORDINATION REQUEST
+    Note right of ng-NB-CU: 
+    ng-NB-CU-->>ng-eNB-DU: NG-ENB-DU RESOURCE COORDINATION RESPONSE
+    Note right of ng-eNB-DU: 
+```
+
+The diagram shows a sequence of messages between an ng-eNB-DU and an ng-NB-CU. The ng-eNB-DU sends an NG-ENB-DU RESOURCE COORDINATION REQUEST message to the ng-NB-CU. The ng-NB-CU responds with an NG-ENB-DU RESOURCE COORDINATION RESPONSE message. Both entities are represented by boxes with lifelines extending downwards, and the messages are shown as horizontal arrows between them.
+
+Sequence diagram for Successful Operation of ng-eNB-DU Resource Coordination
+
+Figure 8.2.6.2-1: ng-eNB-DU Resource Coordination, successful operation
+
+An ng-eNB-CU initiates the procedure by sending the NG-ENB-DU RESOURCE COORDINATION REQUEST message to an ng-eNB-DU over the W1 interface.
+
+The ng-eNB-DU extracts the *E-UTRA – NR Cell Resource Coordination Request Container* IE and it replies by sending the NG-ENB-DU RESOURCE COORDINATION RESPONSE message.
+
+In case of NR-initiated ng-eNB-DU Resource Coordination procedure, the *Ignore Coordination Request Container* IE shall be present and set to "yes" and the *E-UTRA – NR Cell Resource Coordination Request Container* IE in the NG-ENB-DU RESOURCE COORDINATION REQUEST message shall be ignored.
+
+### 8.2.7 ng-eNB-DU Status Indication
+
+#### 8.2.7.1 General
+
+The purpose of the ng-eNB-DU Status Indication procedure is informing the ng-eNB-CU that the ng-eNB-DU is overloaded so that overload reduction actions can be applied. The procedure uses non-UE associated signalling.
+
+#### 8.2.7.2 Successful Operation
+
+![Sequence diagram of the ng-eNB-DU Status Indication procedure. It shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'NG-ENB-DU STATUS INDICATION' points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline. Both lifelines end with a thick horizontal bar at the bottom.](86b4670fc1a5a694821ee92b99c1209a_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: NG-ENB-DU STATUS INDICATION
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram of the ng-eNB-DU Status Indication procedure. It shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'NG-ENB-DU STATUS INDICATION' points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+Figure 8.2.7.2-1: ng-eNB-DU Status Indication procedure
+
+If the *ng-eNB-DU Overload Information* IE in the NG-ENB-DU STATUS INDICATION message indicates that the ng-eNB-DU is overloaded, the ng-eNB-CU shall apply overload reduction actions until informed, with a new NG-ENB-DU STATUS INDICATION message, that the overload situation has ceased.
+
+The detailed overload reduction policy is up to ng-eNB-CU implementation.
+
+#### 8.2.7.3 Abnormal Conditions
+
+Void.
+
+## 8.3 UE Context Management procedures
+
+### 8.3.1 UE Context Setup
+
+#### 8.3.1.1 General
+
+The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, and DRB configuration. The procedure uses UE-associated signalling.
+
+#### 8.3.1.2 Successful Operation
+
+![Sequence diagram illustrating the UE Context Setup Request procedure for successful operation. The diagram shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'UE CONTEXT SETUP REQUEST' points from the ng-eNB-CU to the ng-eNB-DU. A horizontal arrow labeled 'UE CONTEXT SETUP RESPONSE' points from the ng-eNB-DU to the ng-eNB-CU. Both lifelines end with a thick horizontal bar at the bottom.](4b87467ad9642943235f48f7d4b59449_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: 
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT SETUP REQUEST
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU-->>ng-eNB-CU: UE CONTEXT SETUP RESPONSE
+    Note right of ng-eNB-CU: 
+  
+```
+
+Sequence diagram illustrating the UE Context Setup Request procedure for successful operation. The diagram shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'UE CONTEXT SETUP REQUEST' points from the ng-eNB-CU to the ng-eNB-DU. A horizontal arrow labeled 'UE CONTEXT SETUP RESPONSE' points from the ng-eNB-DU to the ng-eNB-CU. Both lifelines end with a thick horizontal bar at the bottom.
+
+**Figure 8.3.1.2-1: UE Context Setup Request procedure: Successful Operation**
+
+The ng-eNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the ng-eNB-DU. If the ng-eNB-DU succeeds to establish the UE context, it replies to the ng-eNB-CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical W1-connection exists, the UE-associated logical W1-connection shall be established as part of the procedure.
+
+If the *SCell To Be Setup List* IE is included in the UE CONTEXT SETUP REQUEST message, the ng-eNB-DU shall act as specified in TS 38.401 [4].
+
+If the *DRX Cycle* IE is contained in the UE CONTEXT SETUP REQUEST message, the ng-eNB-DU shall use the provided value from the ng-eNB-CU.
+
+If the *SRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the ng-eNB-DU shall act as specified in TS 38.401 [4].
+
+If the *DRB To Be Setup List* IE is contained in the UE CONTEXT SETUP REQUEST message, the ng-eNB-DU shall act as specified in TS 38.401 [4].
+
+The ng-eNB-DU shall report to the ng-eNB-CU, in the UE CONTEXT SETUP RESPONSE message, the result for all the requested DRBs and SRBs in the following way:
+
+- A list of DRBs which are successfully established shall be included in the *DRB Setup List* IE;
+- A list of DRBs which failed to be established shall be included in the *DRB Failed to Setup List* IE;
+- A list of SRBs which failed to be established shall be included in the *SRB Failed to Setup List* IE.
+
+When the ng-eNB-DU reports the unsuccessful establishment of a DRB or SRB, the cause value should be precise enough to enable the ng-eNB-CU to know the reason for the unsuccessful establishment.
+
+The ng-eNB-CU shall include in the UE CONTEXT SETUP REQUEST the *DRB Information* IE.
+
+If the *SCell Failed To Setup List* IE is contained in the UE CONTEXT SETUP RESPONSE message, the ng-eNB-CU shall regard the corresponding SCell(s) failed to be established with an appropriate cause value for each SCell failed to setup.
+
+If the *C-RNTI* IE is included in the UE CONTEXT SETUP RESPONSE, the ng-eNB-CU shall consider that the C-RNTI has been allocated by the ng-eNB-DU for this UE context.
+
+The UE Context Setup Procedure is not used to configure SRB0.
+
+If the UE CONTEXT SETUP REQUEST message contains the *RRC-Container* IE, the ng-eNB-DU shall send the corresponding RRC message to the UE via SRB1.
+
+If the *UL PDU Session Aggregate Maximum Bit Rate* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT SETUP REQUEST message, the ng-eNB-DU shall store the received UL PDU Session Aggregate Maximum Bit Rate and use it when enforcing uplink traffic policing for non-GBR Bearers for the concerned UE as specified in TS 23.501 [8].
+
+The ng-eNB-DU shall store the received ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink and use it for non-GBR Bearers for the concerned UE.
+
+If the *PDCP Terminating Node DL Transport Layer Address* IE is included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT SETUP REQUEST message, then the ng-eNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.
+
+#### 8.3.1.3 Unsuccessful Operation
+
+![Sequence diagram showing the Unsuccessful Operation of the UE Context Setup Request procedure. The ng-eNB-CU sends a UE CONTEXT SETUP REQUEST to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT SETUP FAILURE.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT SETUP REQUEST
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU-->>ng-eNB-CU: UE CONTEXT SETUP FAILURE
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram showing the Unsuccessful Operation of the UE Context Setup Request procedure. The ng-eNB-CU sends a UE CONTEXT SETUP REQUEST to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT SETUP FAILURE.
+
+Figure 8.3.1.3-1: UE Context Setup Request procedure: unsuccessful Operation
+
+If the ng-eNB-DU is not able to establish a W1 UE context, or cannot even establish one bearer it shall consider the procedure as failed and reply with the UE CONTEXT SETUP FAILURE message.
+
+If the ng-eNB-DU is not able to accept the *SpCell ID* IE in UE CONTEXT SETUP REQUEST message, it shall reply with the UE CONTEXT SETUP FAILURE message with an appropriate cause value. Further, if the *Candidate SpCell List* IE is included in the UE CONTEXT SETUP REQUEST message and the ng-eNB-DU is not able to accept the *SpCell ID* IE, the ng-eNB-DU shall, if supported, include the *Potential SpCell List* IE in the UE CONTEXT SETUP FAILURE message and the ng-eNB-CU should take this into account for selection of an opportune SpCell. The ng-eNB-DU shall include the cells in the *Potential SpCell List* IE in a priority order, where the first cell in the list is the one most desired and the last one is the one least desired (e.g., based on load conditions). If the *Potential SpCell List* IE is present but no *Potential SpCell Item* IE is present, the ng-eNB-CU should assume that none of the cells in the *Candidate SpCell List* IE are acceptable for the ng-eNB-DU.
+
+#### 8.3.1.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.2 UE Context Release Request (ng-eNB-DU initiated)
+
+#### 8.3.2.1 General
+
+The purpose of the UE Context Release Request procedure is to enable the ng-eNB-DU to request the ng-eNB-CU to release the UE-associated logical W1-connection. The procedure uses UE-associated signalling.
+
+#### 8.3.2.2 Successful Operation
+
+![Sequence diagram for UE Context Release (ng-eNB-DU initiated) procedure. The ng-eNB-DU sends a UE CONTEXT RELEASE REQUEST message to the ng-eNB-CU.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE CONTEXT RELEASE REQUEST
+    Note right of ng-eNB-CU: 
+    Note left of ng-eNB-DU: 
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram for UE Context Release (ng-eNB-DU initiated) procedure. The ng-eNB-DU sends a UE CONTEXT RELEASE REQUEST message to the ng-eNB-CU.
+
+**Figure 8.3.2.2-1: UE Context Release (ng-eNB-DU initiated) procedure. Successful operation**
+
+The ng-eNB-DU controlling a UE-associated logical W1-connection initiates the procedure by generating a UE CONTEXT RELEASE REQUEST message towards the affected ng-eNB-CU node.
+
+The UE CONTEXT RELEASE REQUEST message shall indicate the appropriate cause value.
+
+##### Interactions with UE Context Release procedure:
+
+The UE Context Release procedure may be initiated upon reception of a UE CONTEXT RELEASE REQUEST message.
+
+#### 8.3.2.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.3 UE Context Release (ng-eNB-CU initiated)
+
+#### 8.3.3.1 General
+
+The purpose of the UE Context Release procedure is to enable the ng-eNB-CU to order the release of the UE-associated logical connection. The procedure uses UE-associated signalling.
+
+#### 8.3.3.2 Successful Operation
+
+![Sequence diagram for UE Context Release (ng-eNB-CU initiated) procedure. The ng-eNB-CU sends a UE CONTEXT RELEASE COMMAND message to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT RELEASE COMPLETE message.](b0d322b2e75c75e1f21bfc0df841beaa_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT RELEASE COMMAND
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE CONTEXT RELEASE COMPLETE
+    Note left of ng-eNB-CU: 
+    Note right of ng-eNB-DU: 
+```
+
+Sequence diagram for UE Context Release (ng-eNB-CU initiated) procedure. The ng-eNB-CU sends a UE CONTEXT RELEASE COMMAND message to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT RELEASE COMPLETE message.
+
+**Figure 8.3.3.2-1: UE Context Release (ng-eNB-CU initiated) procedure. Successful operation**
+
+The ng-eNB-CU initiates the procedure by sending the UE CONTEXT RELEASE COMMAND message to the ng-eNB-DU.
+
+Upon reception of the UE CONTEXT RELEASE COMMAND message, the ng-eNB-DU shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message.
+
+If the *old ng-eNB-DU UE WIAP ID* IE is included in the UE CONTEXT RELEASE COMMAND message, the ng-eNB-DU shall additionally release the UE context associated with the old ng-eNB-DU UE WIAP ID.
+
+##### Interactions with UE Context Setup procedure:
+
+The UE Context Release procedure may be performed before the UE Context Setup procedure to release an existing UE-associated logical W1-connection and related resources in the ng-eNB-DU, e.g. when ng-eNB-CU rejects UE access it shall trigger UE Context Release procedure with the cause value of UE rejection.
+
+#### 8.3.3.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.4 UE Context Modification (ng-eNB-CU initiated)
+
+#### 8.3.4.1 General
+
+The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio resources. This procedure is also used to command the ng-eNB-DU to stop data transmission for the UE for mobility (see TS 38.401 [4]). The procedure uses UE-associated signalling.
+
+#### 8.3.4.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the UE Context Modification procedure. The ng-eNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE.](6929132b4964d52244da61d4614bc4d6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: UE Context Modification procedure. Successful operation
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT MODIFICATION REQUEST
+    ng-eNB-DU-->>ng-eNB-CU: UE CONTEXT MODIFICATION RESPONSE
+  
+```
+
+Sequence diagram showing the successful operation of the UE Context Modification procedure. The ng-eNB-CU sends a UE CONTEXT MODIFICATION REQUEST to the ng-eNB-DU, and the ng-eNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE.
+
+Figure 8.3.4.2-1: UE Context Modification procedure. Successful operation
+
+The UE CONTEXT MODIFICATION REQUEST message is initiated by the ng-eNB-CU.
+
+Upon reception of the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message.
+
+If the *SpCell ID* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 36.331 [2]. If the *ServCellIndex* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall take this into account for the indicated SpCell.
+
+If the *SCell To Be Setup List* IE or *SCell To Be Removed List* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall act as specified in TS 38.401 [4]. If the *SCell To Be Setup List* IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the ng-eNB-DU shall replace any previously received value.
+
+If the *DRX Cycle* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall use the provided value from the ng-eNB-CU.
+
+If the *SRB To Be Setup List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall act as specified in the TS 38.401 [4], and replace any previously received value.
+
+If the *DRB To Be Setup List* IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall act as specified in the TS 38.401 [4].
+
+If the UE CONTEXT MODIFICATION REQUEST message contains the *RRC-Container* IE, the ng-eNB-DU shall send the corresponding RRC message to the UE.
+
+The ng-eNB-CU shall include the *DRB Information* IE in the UE CONTEXT MODIFICATION REQUEST message.
+
+The ng-eNB-DU shall report to the ng-eNB-CU, in the UE CONTEXT MODIFICATION RESPONSE message, the result for all the requested or modified DRBs and SRBs in the following way:
+
+- A list of DRBs which are successfully established shall be included in the *DRB Setup List* IE;
+- A list of DRBs which failed to be established shall be included in the *DRB Failed to be Setup List* IE;
+- A list of DRBs which are successfully modified shall be included in the *DRB Modified List* IE;
+- A list of DRBs which failed to be modified shall be included in the *DRB Failed to be Modified List* IE;
+- A list of SRBs which failed to be established shall be included in the *SRB Failed to be Setup List* IE.
+
+When the ng-eNB-DU reports the unsuccessful establishment of a DRB or SRB, the cause value should be precise enough to enable the ng-eNB-CU to know the reason for the unsuccessful establishment.
+
+If the *SCell Failed To Setup List* IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the ng-eNB-CU shall regard the corresponding SCell(s) failed to be established with an appropriate cause value for each SCell failed to setup.
+
+If the *C-RNTI* IE is included in the UE CONTEXT MODIFICATION RESPONSE, the ng-eNB-CU shall consider that the C-RNTI has been allocated by the ng-eNB-DU for this UE context.
+
+The UE Context Modify Procedure is not used to configure SRB0.
+
+If the *UL PDU Session Aggregate Maximum Bit Rate* IE is included in the *QoS Flow Level QoS Parameters* IE contained in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall replace the received UL PDU Session Aggregate Maximum Bit Rate and use it as specified in TS 23.501 [8].
+
+If the *ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink* IE is included in the UE CONTEXT MODIFICATION REQUEST message, the ng-eNB-DU shall:
+
+- replace the previously provided ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink with the new received ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink;
+- use the received ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink for non-GBR Bearers for the concerned UE.
+
+The *UL PDU Session Aggregate Maximum Bit Rate* IE shall be sent if *DRB to Be Setup List* IE is included and the ng-eNB-CU has not previously sent it. The ng-eNB-DU shall store and use the received ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink.
+
+For MN in NGEN-DC, if the *SCG Indicator* IE is included in the UE CONTEXT MODIFICATION REQUEST message and it is set to “released”, the ng-eNB-DU shall, if applicable, consider the SCG is removed.
+
+If the Source Transport Layer Address IE is included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT MODIFICATION REQUEST message, then the ng-eNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.
+
+#### 8.3.4.3 Unsuccessful Operation
+
+![Sequence diagram for Unsuccessful Operation of UE Context Modification procedure.](474a819357587e34949a3e110ff19b30_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT MODIFICATION REQUEST
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE CONTEXT MODIFICATION FAILURE
+    Note right of ng-eNB-CU: 
+```
+
+The diagram shows a sequence of messages between the ng-eNB-CU and the ng-eNB-DU. The ng-eNB-CU sends a 'UE CONTEXT MODIFICATION REQUEST' message to the ng-eNB-DU. The ng-eNB-DU responds with a 'UE CONTEXT MODIFICATION FAILURE' message. Both entities are represented by vertical lines with horizontal bars at the bottom.
+
+Sequence diagram for Unsuccessful Operation of UE Context Modification procedure.
+
+**Figure 8.3.4.3-1: UE Context Modification procedure. Unsuccessful operation**
+
+In case none of the requested modifications of the UE context can be successfully performed, the ng-eNB-DU shall respond with the UE CONTEXT MODIFICATION FAILURE message with an appropriate cause value.
+
+If the ng-eNB-DU is not able to accept the *SpCell ID* IE in UE CONTEXT MODIFICATION REQUEST message, it shall reply with the UE CONTEXT MODIFICATION FAILURE message.
+
+#### 8.3.4.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.5 UE Context Modification Required (ng-eNB-DU initiated)
+
+#### 8.3.5.1 General
+
+The purpose of the UE Context Modification Required procedure is to modify the established UE Context, e.g., modifying and releasing radio bearer resources. The procedure uses UE-associated signalling.
+
+#### 8.3.5.2 Successful Operation
+
+![Sequence diagram for Successful Operation of UE Context Modification Required procedure.](7728e2dd44c95d109debb1eb59e9b411_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE CONTEXT MODIFICATION REQUIRED
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU->>ng-eNB-DU: UE CONTEXT MODIFICATION CONFIRM
+    Note right of ng-eNB-DU: 
+```
+
+The diagram shows a sequence of messages between the ng-eNB-DU and the ng-eNB-CU. The ng-eNB-DU sends a 'UE CONTEXT MODIFICATION REQUIRED' message to the ng-eNB-CU. The ng-eNB-CU responds with a 'UE CONTEXT MODIFICATION CONFIRM' message. Both entities are represented by vertical lines with horizontal bars at the bottom.
+
+Sequence diagram for Successful Operation of UE Context Modification Required procedure.
+
+**Figure 8.3.5.2-1: UE Context Modification Required procedure. Successful operation**
+
+The WIAP UE CONTEXT MODIFICATION REQUIRED message is initiated by the ng-eNB-DU.
+
+The ng-eNB-CU reports the successful update of the UE context in the UE CONTEXT MODIFICATION CONFIRM message.
+
+#### 8.3.5.3 Unsuccessful Operation
+
+![Sequence diagram for UE Context Modification Required procedure. Unsuccessful operation.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE CONTEXT MODIFICATION REQUIRED
+    Note right of ng-eNB-CU: 
+    ng-eNB-CU-->>ng-eNB-DU: UE CONTEXT MODIFICATION REFUSE
+    Note left of ng-eNB-DU: 
+```
+
+The diagram shows a sequence of messages between an ng-eNB-DU and an ng-eNB-CU. The ng-eNB-DU sends a 'UE CONTEXT MODIFICATION REQUIRED' message to the ng-eNB-CU. The ng-eNB-CU responds with a 'UE CONTEXT MODIFICATION REFUSE' message. Both entities are represented by vertical lines with a horizontal bar at the bottom.
+
+Sequence diagram for UE Context Modification Required procedure. Unsuccessful operation.
+
+**Figure 8.3.5.2A-1: UE Context Modification Required procedure. Unsuccessful operation.**
+
+In case none of the requested modifications of the UE context can be successfully performed, the ng-eNB-CU shall respond with the UE CONTEXT MODIFICATION REFUSE message with an appropriate cause value.
+
+#### 8.3.5.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.6 UE Inactivity Notification
+
+#### 8.3.6.1 General
+
+This procedure is initiated by the ng-eNB-DU to indicate the UE activity event.
+
+The procedure uses UE-associated signalling.
+
+#### 8.3.6.2 Successful Operation
+
+![Sequence diagram for UE Inactivity Notification procedure.](718be1eb075833deb7a3b80729a06264_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UE INACTIVITY NOTIFICATION
+    Note right of ng-eNB-CU: 
+    Note left of ng-eNB-DU: 
+```
+
+The diagram shows a sequence of messages between an ng-eNB-DU and an ng-eNB-CU. The ng-eNB-DU sends a 'UE INACTIVITY NOTIFICATION' message to the ng-eNB-CU. Both entities are represented by vertical lines with a horizontal bar at the bottom.
+
+Sequence diagram for UE Inactivity Notification procedure.
+
+**Figure 8.3.6.2-1: UE Inactivity Notification procedure.**
+
+The ng-eNB-DU initiates the procedure by sending the UE INACTIVITY NOTIFICATION message to the ng-eNB-CU.
+
+If the *DRB ID* IE is included in the *DRB Activity Item* IE in the UE INACTIVITY NOTIFICATION message, the *DRB Activity* IE shall also be included
+
+#### 8.3.6.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.3.7 Notify
+
+#### 8.3.7.1 General
+
+The purpose of the Notify procedure is to enable the ng-eNB-DU to inform the ng-eNB-CU that the QoS of an already established GBR DRB cannot be fulfilled any longer or that it can be fulfilled again. The procedure uses UE-associated signalling.
+
+#### 8.3.7.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the Notify procedure. The ng-eNB-DU sends a NOTIFY message to the ng-eNB-CU.](fc0735d325f0ebd9214171975c68a888_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: NOTIFY
+    Note right of ng-eNB-CU: 
+```
+
+The diagram illustrates the successful operation of the Notify procedure. It features two vertical lifelines: 'ng-eNB-DU' on the left and 'ng-eNB-CU' on the right. Each lifeline has a rectangular box at the top and a thick horizontal bar at the bottom. A single horizontal arrow labeled 'NOTIFY' points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline.
+
+Sequence diagram showing the successful operation of the Notify procedure. The ng-eNB-DU sends a NOTIFY message to the ng-eNB-CU.
+
+**Figure 8.3.7.2-1: Notify procedure. Successful operation.**
+
+The ng-eNB-DU initiates the procedure by sending a NOTIFY message.
+
+The NOTIFY message shall contain the list of the GBR DRBs associated with notification control for which the QoS is not fulfilled anymore or for which the QoS is fulfilled again by the ng-eNB-DU.
+
+Upon reception of the NOTIFY message, the ng-eNB-CU may identify which are the affected PDU sessions and QoS flows. The ng-eNB-CU may inform the 5GC that the QoS for these PDU sessions or QoS flows is not fulfilled any longer or it is fulfilled again.
+
+#### 8.3.7.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.4 RRC Message Transfer procedures
+
+### 8.4.1 Initial UL RRC Message Transfer
+
+#### 8.4.1.1 General
+
+The purpose of the Initial UL RRC Message Transfer procedure is to transfer the initial RRC message to the ng-eNB-CU. The procedure uses non-UE-associated signaling.
+
+#### 8.4.1.2 Successful operation
+
+![Sequence diagram for Initial UL RRC Message Transfer procedure](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg)
+
+A sequence diagram showing the interaction between an ng-eNB-DU and an ng-eNB-CU. The ng-eNB-DU is on the left and the ng-eNB-CU is on the right. A horizontal arrow labeled "Initial UL RRC MESSAGE TRANSFER" points from the ng-eNB-DU to the ng-eNB-CU. Both entities are represented by vertical lines with a thick horizontal bar at the bottom.
+
+Sequence diagram for Initial UL RRC Message Transfer procedure
+
+Figure 8.4.1.2-1: Initial UL RRC Message Transfer procedure
+
+The establishment of the UE-associated logical W1-connection shall be initiated as part of the procedure.
+
+#### 8.4.1.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.4.2 DL RRC Message Transfer
+
+#### 8.4.2.1 General
+
+The purpose of the DL RRC Message Transfer procedure is to transfer an RRC message. The procedure uses UE-associated signalling.
+
+#### 8.4.2.2 Successful operation
+
+![Sequence diagram for DL RRC Message Transfer procedure](0977b81510f7649846289ee785d20e74_img.jpg)
+
+A sequence diagram showing the interaction between an ng-eNB-CU and an ng-eNB-DU. The ng-eNB-CU is on the right and the ng-eNB-DU is on the left. A horizontal arrow labeled "DL RRC MESSAGE TRANSFER" points from the ng-eNB-CU to the ng-eNB-DU. Both entities are represented by vertical lines with a thick horizontal bar at the bottom.
+
+Sequence diagram for DL RRC Message Transfer procedure
+
+Figure 8.4.2.2-1: DL RRC Message Transfer procedure
+
+If a UE-associated logical W1-connection exists, the DL RRC MESSAGE TRANSFER message shall contain the *ng-eNB-DU UE W1AP ID* IE, which should be used by ng-eNB-DU to lookup the stored UE context. If no UE-associated logical W1-connection exists, the UE-associated logical W1-connection shall be established at reception of the DL RRC MESSAGE TRANSFER message.
+
+The DL RRC MESSAGE TRANSFER message shall include, if available, the *old ng-eNB-DU UE W1AP ID* IE so that the ng-eNB-DU can retrieve the existing UE context in RRC connection reestablishment procedure, as defined in TS 38.401 [4].
+
+If the ng-eNB-DU identifies the UE-associated logical W1-connection by the *ng-eNB-DU UE W1AP ID* IE in the DL RRC MESSAGE TRANSFER message and the *old ng-eNB-DU UE W1AP ID* IE is included, it shall release the old ng-eNB-DU UE W1AP ID and the related configurations associated with the old ng-eNB-DU UE W1AP ID.
+
+#### 8.4.2.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.4.3 UL RRC Message Transfer
+
+#### 8.4.3.1 General
+
+The purpose of the UL RRC Message Transfer procedure is to transfer an uplink RRC message as UL RLC SDU to the ng-eNB-CU. The procedure uses UE-associated signalling.
+
+#### 8.4.3.2 Successful operation
+
+![Sequence diagram showing the UL RRC Message Transfer procedure. A vertical line on the left represents the ng-eNB-DU, and a vertical line on the right represents the ng-eNB-CU. A horizontal arrow labeled 'UL RRC MESSAGE TRANSFER' points from the ng-eNB-DU to the ng-eNB-CU. Both vertical lines have a thick horizontal bar at the bottom.](dfaa8b98082261913dac00eae86b2889_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: UL RRC MESSAGE TRANSFER
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram showing the UL RRC Message Transfer procedure. A vertical line on the left represents the ng-eNB-DU, and a vertical line on the right represents the ng-eNB-CU. A horizontal arrow labeled 'UL RRC MESSAGE TRANSFER' points from the ng-eNB-DU to the ng-eNB-CU. Both vertical lines have a thick horizontal bar at the bottom.
+
+Figure 8.4.3.2-1: UL RRC Message Transfer procedure
+
+When the ng-eNB-DU has received from the radio interface an RRC message to which a UE-associated logical W1-connection for the UE exists, the ng-eNB-DU shall send the UL RRC MESSAGE TRANSFER message to the ng-eNB-CU including the RRC message as a *RRC-Container* IE.
+
+#### 8.4.3.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.4.4 RRC Delivery Report
+
+Void
+
+## 8.5 Warning Message Transmission Procedures
+
+### 8.5.1 Write-Replace Warning
+
+#### 8.5.1.1 General
+
+The purpose of Write-Replace Warning procedure is to start or overwrite the broadcasting of warning messages. The procedure uses non UE-associated signalling.
+
+#### 8.5.1.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the Write-Replace Warning procedure. The ng-eNB-CU sends a WRITE-REPLACE WARNING REQUEST message to the ng-eNB-DU, and the ng-eNB-DU responds with a WRITE-REPLACE WARNING RESPONSE message.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg)
+
+```
+
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: 
+    ng-eNB-CU->>ng-eNB-DU: WRITE-REPLACE WARNING REQUEST
+    Note right of ng-eNB-DU: 
+    ng-eNB-DU-->>ng-eNB-CU: WRITE-REPLACE WARNING RESPONSE
+    Note right of ng-eNB-CU: 
+  
+```
+
+Sequence diagram showing the successful operation of the Write-Replace Warning procedure. The ng-eNB-CU sends a WRITE-REPLACE WARNING REQUEST message to the ng-eNB-DU, and the ng-eNB-DU responds with a WRITE-REPLACE WARNING RESPONSE message.
+
+**Figure 8.5.1.2-1: Write-Replace Warning procedure: successful operation**
+
+The ng-eNB-CU initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the ng-eNB-DU.
+
+Upon receipt of the WRITE-REPLACE WARNING REQUEST message, the ng-eNB-DU shall prioritise its resources to process the warning message.
+
+The ng-eNB-DU acknowledges the WRITE-REPLACE WARNING REQUEST message by sending a WRITE-REPLACE WARNING RESPONSE message to the ng-eNB-CU.
+
+If the *Notification Information* IE is included in the *PWS System Information* IE in the WRITE-REPLACE WARNING REQUEST message, the ng-eNB-DU shall use this information to avoid that duplications trigger new broadcast or replace existing broadcast.
+
+If the ng-eNB-DU receives a WRITE-REPLACE WARNING REQUEST message with the *Notification Information* IE in the *PWS System Information* IE which are different from those of ongoing broadcast warning messages, and if the *SIB Type* IE is set to "12", the ng-eNB-DU shall broadcast the received warning message concurrently with other ongoing messages.
+
+If the ng-eNB-DU receives a WRITE-REPLACE WARNING REQUEST message with the *Notification Information* IE in the *PWS System Information* IE which are different from those of ongoing broadcast warning messages, and if the *SIB Type* IE is set to the value other than "12", the ng-eNB-DU shall use the newly received one to replace the ongoing broadcast warning message with the same value of *SIB Type* IE.
+
+If the *SIB Type* IE in the *PWS System Information* IE in the WRITE-REPLACE WARNING REQUEST message is set to "12" and if a value "0" is received in the *Number of Broadcast Requested* IE and if the *Repetition Period* IE is different from "0", the ng-eNB-DU shall broadcast the received warning message indefinitely.
+
+If *Additional SIB Message List* IE is included in *PWS System Information* IE, the ng-eNB-DU shall store all SIB message(s) in *PWS System Information* IE, and consider that the first segment of public warning message is included in *SIB message* IE, and the remaining segments are listed in *Additional SIB Message List* IE in segmentation sequence order.
+
+#### 8.5.1.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.5.1.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.5.2 PWS Cancel
+
+#### 8.5.2.1 General
+
+The purpose of the PWS Cancel procedure is to cancel an already ongoing broadcast of a warning message. The procedure uses non UE-associated signalling.
+
+#### 8.5.2.2 Successful Operation
+
+![Sequence diagram of the PWS Cancel procedure: successful operation. The diagram shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'PWS CANCEL REQUEST' points from the ng-eNB-CU lifeline to the ng-eNB-DU lifeline. A horizontal arrow labeled 'PWS CANCEL RESPONSE' points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline. Both lifelines end with a thick horizontal bar at the bottom.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: PWS CANCEL REQUEST
+    ng-eNB-DU-->>ng-eNB-CU: PWS CANCEL RESPONSE
+    Note right of ng-eNB-CU: 
+```
+
+Sequence diagram of the PWS Cancel procedure: successful operation. The diagram shows two vertical lifelines: ng-eNB-DU on the left and ng-eNB-CU on the right. A horizontal arrow labeled 'PWS CANCEL REQUEST' points from the ng-eNB-CU lifeline to the ng-eNB-DU lifeline. A horizontal arrow labeled 'PWS CANCEL RESPONSE' points from the ng-eNB-DU lifeline to the ng-eNB-CU lifeline. Both lifelines end with a thick horizontal bar at the bottom.
+
+Figure 8.5.2.2-1: PWS Cancel procedure: successful operation
+
+The ng-eNB-CU initiates the procedure by sending a PWS CANCEL REQUEST message to the ng-eNB-DU.
+
+The ng-eNB-DU shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message.
+
+If the *Cancel-All Warning Messages Indicator* IE is present in the PWS CANCEL REQUEST message, then the ng-eNB-DU shall stop broadcasting and discard all warning messages for the area as indicated in the *Cell Broadcast To Be Cancelled List* IE or in all the cells of the ng-eNB-DU if the *Cell Broadcast To Be Cancelled List* IE is not included. The ng-eNB-DU shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message, and shall, if there is area to report where an ongoing broadcast was stopped successfully, include the *Cell Broadcast Cancelled List* IE with the *Number of Broadcasts* IE set to 0.
+
+If the *Cell Broadcast To Be Cancelled List* IE is not included in the PWS CANCEL REQUEST message, the ng-eNB-DU shall stop broadcasting and discard the warning message identified by the *Message Identifier* IE and the *Serial Number* IE in the *Notification Information* IE in all of the cells in the ng-eNB-DU.
+
+If an area included in the *Cell Broadcast To Be Cancelled List* IE in the PWS CANCEL REQUEST message does not appear in the *Cell Broadcast Cancelled List* IE in the PWS CANCEL RESPONSE, the ng-eNB-CU shall consider that the ng-eNB-DU had no ongoing broadcast to stop for the public warning message identified, if present, by the *Notification Information* IE in that area.
+
+If the *Cell Broadcast Cancelled List* IE is not included in the PWS CANCEL RESPONSE message, the ng-eNB-CU shall consider that the ng-eNB-DU had no ongoing broadcast to stop for the public warning message identified by the *Notification Information* IE.
+
+#### 8.5.2.3 Unsuccessful Operation
+
+Not applicable.
+
+#### 8.5.2.4 Abnormal Conditions
+
+Not applicable.
+
+### 8.5.3 PWS Restart Indication
+
+#### 8.5.3.1 General
+
+The purpose of PWS Restart Indication procedure is to inform the ng-eNB-CU that PWS information for some or all cells of the ng-eNB-DU are available for reloading from the CBC if needed. The procedure uses non UE-associated signalling.
+
+#### 8.5.3.2 Successful Operation
+
+![Sequence diagram for PWS restart indication](315bdbeafb39026e19b77c26b19d9d1f_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: PWS RESTART INDICATION
+    Note right of ng-eNB-CU: 
+```
+
+A sequence diagram showing the interaction between an ng-eNB-DU and an ng-eNB-CU. The ng-eNB-DU is on the left and the ng-eNB-CU is on the right. A horizontal arrow labeled "PWS RESTART INDICATION" points from the ng-eNB-DU to the ng-eNB-CU. Both entities have a vertical lifeline with a thick horizontal bar at the bottom.
+
+Sequence diagram for PWS restart indication
+
+Figure 8.5.3.2-1: PWS restart indication
+
+The ng-eNB-DU initiates the procedure by sending a PWS RESTART INDICATION message to the ng-eNB-CU.
+
+#### 8.5.3.3 Abnormal Conditions
+
+Not applicable.
+
+### 8.5.4 PWS Failure Indication
+
+#### 8.5.4.1 General
+
+The purpose of the PWS Failure Indication procedure is to inform the ng-eNB-CU that ongoing PWS operation for one or more cells of the ng-eNB-DU has failed. The procedure uses non UE-associated signalling.
+
+#### 8.5.4.2 Successful Operation
+
+![Sequence diagram for PWS failure indication](0803a098adb6b6c817a7bee221179e16_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-DU
+    participant ng-eNB-CU
+    Note left of ng-eNB-DU: 
+    ng-eNB-DU->>ng-eNB-CU: PWS FAILURE INDICATION
+    Note right of ng-eNB-CU: 
+```
+
+A sequence diagram showing the interaction between an ng-eNB-DU and an ng-eNB-CU. The ng-eNB-DU is on the left and the ng-eNB-CU is on the right. A horizontal arrow labeled "PWS FAILURE INDICATION" points from the ng-eNB-DU to the ng-eNB-CU. Both entities have a vertical lifeline with a thick horizontal bar at the bottom.
+
+Sequence diagram for PWS failure indication
+
+Figure 8.5.4.2-1: PWS failure indication
+
+The ng-eNB-DU initiates the procedure by sending a PWS FAILURE INDICATION message to the ng-eNB-CU.
+
+#### 8.5.4.3 Abnormal Conditions
+
+Not applicable.
+
+## 8.6 Paging procedures
+
+### 8.6.1 Paging
+
+#### 8.6.1.1 General
+
+The purpose of the Paging procedure is used to provide the paging information to enable the ng-eNB-DU to page a UE. The procedure uses non-UE associated signalling.
+
+#### 8.6.1.2 Successful Operation
+
+![Sequence diagram showing the successful operation of the paging procedure. The ng-eNB-CU sends a PAGING message to the ng-eNB-DU.](02d0c8a07c481d880b73a25d02050fad_img.jpg)
+
+```
+sequenceDiagram
+    participant ng-eNB-CU
+    participant ng-eNB-DU
+    Note left of ng-eNB-CU: 
+    Note right of ng-eNB-DU: 
+    ng-eNB-CU->>ng-eNB-DU: PAGING
+    Note right of ng-eNB-DU: 
+```
+
+Sequence diagram showing the successful operation of the paging procedure. The ng-eNB-CU sends a PAGING message to the ng-eNB-DU.
+
+Figure 8.6.1.2-1: Paging procedure. Successful operation.
+
+The ng-eNB-CU initiates the procedure by sending a PAGING message.
+
+The *Paging DRX* IE may be included in the PAGING message, and if present the ng-eNB-DU may use it to determine the final paging cycle for the UE.
+
+At the reception of the PAGING message, the ng-eNB-DU shall perform paging of the UE in cells which belong to cells as indicated in the *Paging Cell List* IE.
+
+The *Paging Origin* IE may be included in the PAGING message, and if present the ng-eNB-DU shall transfer it to the UE.
+
+##### 8.6.1.3 Abnormal Conditions
+
+Not applicable.
+
+---
+
+## 9 Elements for W1AP Communication
+
+### 9.1 General
+
+Clauses 9.2 and 9.3 present the W1AP message and IE definitions in tabular format. The corresponding ASN.1 definition is presented in clause 9.4. In case there is contradiction between the tabular format and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence.
+
+The messages have been defined in accordance to the guidelines specified in TR 25.921 [21].
+
+When specifying IEs which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits:
+
+- The first bit (leftmost bit) contains the most significant bit (MSB);
+- The last bit (rightmost bit) contains the least significant bit (LSB);
+- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information;
+
+The following attributes are used for the tabular description of the messages and information elements: Presence, Range, Criticality and Assigned Criticality. Their definition and use can be found in TS 38.413 [19].
+
+## 9.2 Message Functional Definition and Content
+
+### 9.2.1 Interface Management messages
+
+#### 9.2.1.1 RESET
+
+This message is sent by both the ng-eNB-CU and the ng-eNB-DU and is used to request that the W1 interface, or parts of the W1 interface, to be reset.
+
+Direction: ng-eNB-CU → ng-eNB-DU and ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                               | Presence | Range                                        | IE type and reference      | Semantics description | Criticality | Assigned Criticality |
+|---------------------------------------------|----------|----------------------------------------------|----------------------------|-----------------------|-------------|----------------------|
+| Message Type                                | M        |                                              | 9.3.1.1                    |                       | YES         | reject               |
+| Transaction ID                              | M        |                                              | 9.3.1.23                   |                       | YES         | reject               |
+| Cause                                       | M        |                                              | 9.3.1.2                    |                       | YES         | ignore               |
+| <b>CHOICE Reset Type</b>                    | M        |                                              |                            |                       | YES         | reject               |
+| >W1 interface                               |          |                                              |                            |                       |             |                      |
+| >>Reset All                                 | M        |                                              | ENUMERATED (Reset all,...) |                       | -           |                      |
+| >Part of W1 interface                       |          |                                              |                            |                       |             |                      |
+| >>UE-associated logical W1-connection list  |          | 1                                            |                            |                       | -           |                      |
+| >>>UE-associated logical W1-connection Item |          | 1 .. <maxnoofIndividualW1ConnectionsToReset> |                            |                       | EACH        | reject               |
+| >>>> ng-eNB-CU UE W1AP ID                   | O        |                                              | 9.3.1.4                    |                       | -           |                      |
+| >>>> ng-eNB-DU UE W1AP ID                   | O        |                                              | 9.3.1.5                    |                       | -           |                      |
+
+| Range bound                           | Explanation                                                                                          |
+|---------------------------------------|------------------------------------------------------------------------------------------------------|
+| maxnoofIndividualW1ConnectionsToReset | Maximum no. of UE-associated logical W1-connections allowed to reset in one message. Value is 65536. |
+
+#### 9.2.1.2 RESET ACKNOWLEDGE
+
+This message is sent by both the ng-eNB-CU and the ng-eNB-DU as a response to a RESET message.
+
+Direction: ng-eNB-DU → ng-eNB-CU and ng-eNB-CU → ng-eNB-DU.
+
+| IE/Group Name                                   | Presence | Range                                        | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|----------------------------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type                                    | M        |                                              | 9.3.1.1               |                       | YES         | reject               |
+| Transaction ID                                  | M        |                                              | 9.3.1.23              |                       | YES         | reject               |
+| <b>UE-associated logical W1-connection list</b> |          | 0..1                                         |                       |                       | YES         | ignore               |
+| >UE-associated logical W1-connection Item       |          | 1 .. <maxnoofIndividualW1ConnectionsToReset> |                       |                       | EACH        | ignore               |
+| >>ng-eNB-CU UE W1AP ID                          | O        |                                              | 9.3.1.4               |                       | -           |                      |
+| >>ng-eNB-DU UE W1AP ID                          | O        |                                              | 9.3.1.5               |                       | -           |                      |
+| Criticality Diagnostics                         | O        |                                              | 9.3.1.61              |                       | YES         | ignore               |
+
+| Range bound                           | Explanation                                                                                          |
+|---------------------------------------|------------------------------------------------------------------------------------------------------|
+| maxnoofIndividualW1ConnectionsToReset | Maximum no. of UE-associated logical W1-connections allowed to reset in one message. Value is 65536. |
+
+### 9.2.1.3 ERROR INDICATION
+
+This message is sent by both the ng-eNB-CU and the ng-eNB-DU and is used to indicate that some error has been detected in the node.
+
+Direction: ng-eNB-CU → ng-eNB-DU and ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description                                                     | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                                                                           | YES         | ignore               |
+| Transaction ID          | M        |       | 9.3.1.23              | This IE shall be ignored if received in UE associated signalling message. | YES         | reject               |
+| ng-eNB-CU UE W1AP ID    | O        |       | 9.3.1.4               |                                                                           | YES         | ignore               |
+| ng-eNB-DU UE W1AP ID    | O        |       | 9.3.1.5               |                                                                           | YES         | ignore               |
+| Cause                   | M        |       | 9.3.1.2               |                                                                           | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                                                                           | YES         | ignore               |
+
+### 9.2.1.4 W1 SETUP REQUEST
+
+This message is sent by the ng-eNB-DU to transfer information associated to a W1-C interface instance.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                          | Presence | Range                       | IE type and reference | Semantics description                                    | Criticality | Assigned Criticality |
+|----------------------------------------|----------|-----------------------------|-----------------------|----------------------------------------------------------|-------------|----------------------|
+| Message Type                           | M        |                             | 9.3. 1.1              |                                                          | YES         | reject               |
+| Transaction ID                         | M        |                             | 9.3.1.23              |                                                          | YES         | reject               |
+| ng-eNB-DU ID                           | M        |                             | 9.3.1.9               |                                                          | YES         | reject               |
+| <b>ng-eNB-DU Served Cells List</b>     |          | 0.. 1                       |                       | List of cells configured in the ng-eNB-DU                | YES         | reject               |
+| <b>&gt;ng-eNB-DU Served Cells Item</b> |          | 1..<br><maxCellinng-eNB-DU> |                       |                                                          | EACH        | reject               |
+| >>Served Cell Information              | M        |                             | 9.3.1.10              | Information about the cells configured in the ng-eNB-DU  | -           |                      |
+| >>ng-eNB-DU System Information         | O        |                             | 9.3.1.18              | RRC container with system information owned by ng-eNB-DU | -           |                      |
+
+| Range bound        | Explanation                                                         |
+|--------------------|---------------------------------------------------------------------|
+| maxCellinng-eNB-DU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.1.5 W1 SETUP RESPONSE
+
+This message is sent by the ng-eNB-CU to transfer information associated to a W1-C interface instance.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                     | Presence | Range                      | IE type and reference | Semantics description                                                                                                       | Criticality | Assigned Criticality |
+|-----------------------------------|----------|----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                      | M        |                            | 9.3.1.1               |                                                                                                                             | YES         | reject               |
+| Transaction ID                    | M        |                            | 9.3.1.23              |                                                                                                                             | YES         | reject               |
+| <b>Cells to be Activated List</b> |          | 0.. 1                      |                       |                                                                                                                             | YES         | reject               |
+| >Cells to be Activated List Item  |          | 1..<br><maxCellinng-eNBDU> |                       | List of cells to be activated                                                                                               | EACH        | reject               |
+| >> E-UTRAN CGI                    | M        |                            | 9.3.1.12              |                                                                                                                             | -           |                      |
+| >> E-UTRAN PCI                    | O        |                            | INTEGER (0..503)      | Physical Cell ID                                                                                                            | -           |                      |
+| >>ng-eNB-CU System Information    | O        |                            | 9.3.1.33              | RRC container with system information owned by ng-eNB-CU                                                                    | YES         | reject               |
+| >>Available PLMN List             | O        |                            | 9.3.1.47              |                                                                                                                             | YES         | ignore               |
+| >>Extended Available PLMN List    | O        |                            | 9.3.1.55              | This is included if <i>Available PLMN List</i> IE is included and if more than 6 <i>Available PLMNs</i> is to be signalled. | YES         | ignore               |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.1.6 W1 SETUP FAILURE
+
+This message is sent by the ng-eNB-CU to indicate W1 Setup failure.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| Transaction ID          | M        |       | 9.3.1.23              |                       | YES         | reject               |
+| Cause                   | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+### 9.2.1.7 NG-ENB-DU CONFIGURATION UPDATE
+
+This message is sent by the ng-eNB-DU to transfer updated information associated to a W1-C interface instance.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                   | Presence | Range | IE type and reference | Semantics description                                | Criticality | Assigned Criticality |
+|---------------------------------|----------|-------|-----------------------|------------------------------------------------------|-------------|----------------------|
+| Message Type                    | M        |       | 9.3.1.1               |                                                      | YES         | reject               |
+| Transaction ID                  | M        |       | 9.3.1.23              |                                                      | YES         | reject               |
+| <b>Served Cells To Add List</b> |          | 0..1  |                       | Complete list of added cells served by the ng-eNB-DU | YES         | reject               |
+
+|                                        |   |                                 |                         |                                                          |      |        |
+|----------------------------------------|---|---------------------------------|-------------------------|----------------------------------------------------------|------|--------|
+| <b>&gt;Served Cells To Add Item</b>    |   | 1 ..<br><maxCellinn<br>g-eNBDU> |                         |                                                          | EACH | reject |
+| >>Served Cell Information              | M |                                 | 9.3.1.10                | Information about the cells configured in the ng-eNB-DU  | -    |        |
+| >>ng-eNB-DU System Information         | O |                                 | 9.3.1.18                | RRC container with system information owned by ng-eNB-DU | -    |        |
+| <b>Served Cells To Modify List</b>     |   | 0..1                            |                         | Complete list of modified cells served by the ng-eNB-DU  | YES  | reject |
+| <b>&gt;Served Cells To Modify Item</b> |   | 1 ..<br><maxCellinn<br>g-eNBDU> |                         |                                                          | EACH | reject |
+| >>Old E-UTRAN CGI                      | M |                                 | E-UTRAN CGI<br>9.3.1.12 |                                                          | -    |        |
+| >>Served Cell Information              | M |                                 | 9.3.1.10                | Information about the cells configured in the ng-eNB-DU  | -    |        |
+| >>ng-eNB-DU System Information         | O |                                 | 9.3.1.18                | RRC container with system information owned by ng-eNB-DU | -    |        |
+| <b>Served Cells To Delete List</b>     |   | 0..1                            |                         | Complete list of deleted cells served by the ng-eNB-DU   | YES  | reject |
+| <b>&gt;Served Cells To Delete Item</b> |   | 1..<br><maxCellinn<br>g-eNBDU>  |                         |                                                          | EACH | reject |
+| >>Old E-UTRAN CGI                      | M |                                 | E-UTRAN CGI<br>9.3.1.12 |                                                          | -    |        |
+| <b>Cells Status List</b>               |   | 0..1                            |                         | Complete list of active cells                            | YES  | reject |
+| <b>&gt; Cells Status Item</b>          |   | 0 ..<br><maxCellinn<br>g-eNBDU> |                         |                                                          | EACH | reject |
+| >> E-UTRAN CGI                         | M |                                 | 9.3.1.12                |                                                          | -    |        |
+| >> Service Status                      | M |                                 | 9.3.1.48                |                                                          | -    |        |
+| ng-eNB-DU ID                           | O |                                 | 9.3.1.9                 |                                                          | YES  | reject |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.1.8 NG-ENB-DU CONFIGURATION UPDATE ACKNOWLEDGE
+
+This message is sent by an ng-eNB-CU to an ng-eNB-DU to acknowledge update of information associated to a W1-C interface instance.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                           | Presence | Range                              | IE type and reference | Semantics description                                                                                                                      | Criticality | Assigned Criticality |
+|-----------------------------------------|----------|------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                            | M        |                                    | 9.3.1.1               |                                                                                                                                            | YES         | reject               |
+| Transaction ID                          | M        |                                    | 9.3.1.23              |                                                                                                                                            | YES         | reject               |
+| <b>Cells to be Activated List</b>       |          | 0.. 1                              |                       | List of cells to be activated                                                                                                              | YES         | reject               |
+| >Cells to be Activated List Item        |          | 1..<br><maxCell<br>inng-<br>eNBDU> |                       |                                                                                                                                            | EACH        | reject               |
+| >> E-UTRAN CGI                          | M        |                                    | 9.3.1.12              |                                                                                                                                            | -           |                      |
+| >> E-UTRAN PCI                          | O        |                                    | INTEGER<br>(0..503)   | Physical Cell ID                                                                                                                           | -           |                      |
+| >> ng-eNB-CU<br>System Information      | O        |                                    | 9.3.1.33              | RRC container<br>with system<br>information<br>owned by ng-<br>eNB-CU                                                                      | YES         | reject               |
+| >>Available PLMN<br>List                | O        |                                    | 9.3.1.47              |                                                                                                                                            | YES         | ignore               |
+| >>Extended Available<br>PLMN List       | O        |                                    | 9.3.1.55              | This is included<br>if <i>Available<br/>PLMN List</i> IE is<br>included and if<br>more than 6<br>Available<br>PLMNs is to be<br>signalled. | YES         | ignore               |
+| <b>Cells to be Deactivated<br/>List</b> |          | 0.. 1                              |                       | List of cells to<br>be deactivated                                                                                                         | YES         | reject               |
+| >Cells to be<br>Deactivated List Item   |          | 1..<br><maxCell<br>inng-<br>eNBDU> |                       |                                                                                                                                            | EACH        | reject               |
+| >> E-UTRAN CGI                          | M        |                                    | 9.3.1.12              |                                                                                                                                            | -           | -                    |
+| Criticality Diagnostics                 | O        |                                    | 9.3.1.61              |                                                                                                                                            | YES         | ignore               |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellInng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.1.9 NG-ENB-DU CONFIGURATION UPDATE FAILURE
+
+This message is sent by the ng-eNB-CU to indicate ng-eNB-DU Configuration Update failure.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| Transaction ID          | M        |       | 9.3.1.23              |                       | YES         | reject               |
+| Cause                   | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+### 9.2.1.10 NG-ENB-CU CONFIGURATION UPDATE
+
+This message is sent by the ng-eNB-CU to transfer updated information associated to a W1-C interface instance.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                              | Presence | Range                      | IE type and reference | Semantics description                                                                                                | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|----------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                               | M        |                            | 9.3.1.1               |                                                                                                                      | YES         | reject               |
+| Transaction ID                             | M        |                            | 9.3.1.23              |                                                                                                                      | YES         | reject               |
+| <b>Cells to be Activated List</b>          |          | 0..1                       |                       | List of cells to be activated or modified                                                                            | YES         | reject               |
+| > <b>Cells to be Activated List Item</b>   |          | 1..<br><maxCellinng-eNBDU> |                       |                                                                                                                      | EACH        | reject               |
+| >> E-UTRAN CGI                             | M        |                            | 9.3.1.12              |                                                                                                                      | -           |                      |
+| >> E-UTRAN PCI                             | O        |                            | INTEGER (0..503)      | Physical Cell ID                                                                                                     | -           |                      |
+| >> ng-eNB-CU System Information            | O        |                            | 9.3.1.33              | RRC container with system information owned by ng-eNB-CU                                                             | YES         | reject               |
+| >>Available PLMN List                      | O        |                            | 9.3.1.47              |                                                                                                                      | YES         | ignore               |
+| >>Extended Available PLMN List             | O        |                            | 9.3.1.55              | This is included if <i>Available PLMN List</i> IE is included and if more than 6 Available PLMNs is to be signalled. | YES         | ignore               |
+| <b>Cells to be Deactivated List</b>        |          | 0..1                       |                       | List of cells to be deactivated                                                                                      | YES         | reject               |
+| > <b>Cells to be Deactivated List Item</b> |          | 1..<br><maxCellinng-eNBDU> |                       |                                                                                                                      | EACH        | reject               |
+| >> E-UTRAN CGI                             | M        |                            | 9.3.1.12              |                                                                                                                      | -           |                      |
+
+| Range bound       | Explanation                                                               |
+|-------------------|---------------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum number of cells that can be served by an ng-eNB-DU. Value is 512. |
+
+## 9.2.1.11 NG-ENB-CU CONFIGURATION UPDATE ACKNOWLEDGE
+
+This message is sent by an ng-eNB-DU to an ng-eNB-CU to acknowledge update of information associated to a W1-C interface instance.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                            | Presence | Range                   | IE type and reference | Semantics description                          | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------------------------|-----------------------|------------------------------------------------|-------------|----------------------|
+| Message Type                             | M        |                         | 9.3.1.1               |                                                | YES         | reject               |
+| Transaction ID                           | M        |                         | 9.3.1.23              |                                                | YES         | reject               |
+| <b>Cells Failed to be Activated List</b> |          | 0..1                    |                       | List of cells which are failed to be activated | YES         | reject               |
+| >Cells Failed to be Activated Item       |          | 1.. <maxCellinng-eNBDU> |                       |                                                | EACH        | reject               |
+| >> E-UTRAN CGI                           | M        |                         | 9.3.1.12              |                                                | -           |                      |
+| >>Cause                                  | M        |                         | 9.3.1.2               |                                                | -           |                      |
+| Criticality Diagnostics                  | O        |                         | 9.3.1.61              |                                                | YES         | ignore               |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+## 9.2.1.12 NG-ENB-CU CONFIGURATION UPDATE FAILURE
+
+This message is sent by the ng-eNB-DU to indicate ng-eNB-CU Configuration Update failure.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| Transaction ID          | M        |       | 9.3.1.23              |                       | YES         | reject               |
+| Cause                   | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+## 9.2.1.13 NG-ENB-DU RESOURCE COORDINATION REQUEST
+
+This message is sent by an ng-eNB-CU to an ng-eNB-DU, to express the desired resource allocation for data traffic, for the sake of resource coordination.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                                            | Presence | Range | IE type and reference              | Semantics description                                                                                                    | Criticality | Assigned Criticality |
+|----------------------------------------------------------|----------|-------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                                             | M        |       | 9.3.1.1                            |                                                                                                                          | YES         | reject               |
+| Transaction ID                                           | M        |       | 9.3.1.23                           |                                                                                                                          | YES         | reject               |
+| Request type                                             | M        |       | ENUMERATED (offer, execution, ...) |                                                                                                                          | YES         | reject               |
+| E-UTRA – NR Cell Resource Coordination Request Container | M        |       | OCTET STRING                       | Includes the XNAP E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message as defined in clause 9.1.2.23 in TS 38.423 [7]. | YES         | reject               |
+| Ignore Resource Coordination Request Container           | O        |       | ENUMERATED (yes, ...)              |                                                                                                                          | YES         | reject               |
+
+### 9.2.1.14 NG-ENB-DU RESOURCE COORDINATION RESPONSE
+
+This message is sent by an ng-eNB-DU to an ng-eNB-CU, to express the desired resource allocation for data traffic, as a response to the NG-ENB-DU RESOURCE COORDINATION REQUEST.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                                             | Presence | Range | IE type and reference | Semantics description                                                                                                     | Criticality | Assigned Criticality |
+|-----------------------------------------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                                              | M        |       | 9.3.1.1               |                                                                                                                           | YES         | reject               |
+| Transaction ID                                            | M        |       | 9.3.1.23              |                                                                                                                           | YES         | reject               |
+| E-UTRA – NR Cell Resource Coordination Response Container | M        |       | OCTET STRING          | Includes the XNAP E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message as defined in clause 9.1.2.24 in TS 38.423 [7]. | YES         | reject               |
+
+### 9.2.1.15 NG-ENB-DU STATUS INDICATION
+
+This message is sent by the ng-eNB-DU to indicate to the ng-eNB-CU its status of overload.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                  | Presence | Range | IE type and reference                   | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|-----------------------------------------|-----------------------|-------------|----------------------|
+| Message Type                   | M        |       | 9.3.1.1                                 |                       | YES         | ignore               |
+| Transaction ID                 | M        |       | 9.3.1.23                                |                       | YES         | reject               |
+| ng-eNB-DU Overload Information | M        |       | ENUMERATED (overloaded, not-overloaded) |                       | YES         | reject               |
+
+## 9.2.2 UE Context Management messages
+
+### 9.2.2.1 UE CONTEXT SETUP REQUEST
+
+This message is sent by the ng-eNB-CU to request the setup of a UE context.
+
+Direction: ng-eNB-CU → ng-eNB-DU.
+
+| IE/Group Name               | Presence | Range                          | IE type and reference | Semantics description                                                                                     | Criticality | Assigned Criticality |
+|-----------------------------|----------|--------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                | M        |                                | 9.3.1.1               |                                                                                                           | YES         | reject               |
+| ng-eNB-CU UE W1AP ID        | M        |                                | 9.3.1.4               |                                                                                                           | YES         | reject               |
+| ng-eNB-DU UE W1AP ID        | O        |                                | 9.3.1.5               |                                                                                                           | YES         | ignore               |
+| CU to DU RRC Information    | M        |                                | 9.3.1.57              |                                                                                                           | YES         | reject               |
+| DRX Cycle                   | O        |                                | DRX Cycle 9.3.1.24    |                                                                                                           | YES         | ignore               |
+| SpCell ID                   | M        |                                | ECGI 9.3.1.12         | Special Cell as defined in TS 36.321 [15]. For handover case, this IE shall be considered as target cell. | YES         | reject               |
+| ServCellIndex               | M        |                                | INTEGER (0..31,...)   |                                                                                                           | YES         | reject               |
+| Candidate SpCell List       |          | 0..1                           |                       |                                                                                                           | YES         | ignore               |
+| >Candidate SpCell Item IEs  |          | 1 .. <maxnoofCandidateSpCells> |                       |                                                                                                           | EACH        | ignore               |
+| >>Candidate SpCell ID       | M        |                                | ECGI 9.3.1.12         | Special Cell as defined in TS 36.321 [15]                                                                 | -           |                      |
+| SCell To Be Setup List      |          | 0..1                           |                       |                                                                                                           | YES         | ignore               |
+| >SCell to Be Setup Item IEs |          | 1.. <maxnoofSCells>            |                       |                                                                                                           | EACH        | ignore               |
+| >>SCell ID                  | M        |                                | ECGI 9.3.1.12         | SCell Identifier in ng-eNB                                                                                | -           |                      |
+| >>SCellIndex                | M        |                                | INTEGER (1..31)       |                                                                                                           | -           |                      |
+| SRB to Be Setup List        |          | 0..1                           |                       |                                                                                                           | YES         | reject               |
+| >SRB to Be Setup Item IEs   |          | 1 .. <maxnoofSRBs>             |                       |                                                                                                           | EACH        | reject               |
+| >>SRB ID                    | M        |                                | 9.3.1.7               |                                                                                                           | -           |                      |
+| DRB to Be Setup List        |          | 0..1                           |                       |                                                                                                           | YES         | reject               |
+| >DRB to Be Setup Item IEs   |          | 1 .. <maxnoofDRBs>             |                       |                                                                                                           | EACH        | reject               |
+| >>DRB ID                    | M        |                                | 9.3.1.8               |                                                                                                           | -           |                      |
+| >>>CHOICE QoS Information   | M        |                                |                       |                                                                                                           | -           |                      |
+| >>>E-UTRAN QoS              | M        |                                | 9.3.1.19              | Shall be used for DC case to convey E-RAB Level QoS Parameters                                            | -           |                      |
+| >>>DRB Information          |          | 1                              |                       | Shall be used for NG-RAN cases                                                                            | YES         | ignore               |
+| >>>>DRB QoS                 | M        |                                | 9.3.1.34              |                                                                                                           | -           |                      |
+| >>>>S-NSSAI                 | M        |                                | 9.3.1.32              |                                                                                                           | -           |                      |
+| >>>>Notification Control    | O        |                                | 9.3.1.44              |                                                                                                           | -           |                      |
+
+| IE/Group Name                                  | Presence     | Range                  | IE type and reference                  | Semantics description                                                                                         | Criticality | Assigned Criticality |
+|------------------------------------------------|--------------|------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>Flows Mapped to DRB Item                   |              | 1 .. <maxnoofQoSFlows> |                                        |                                                                                                               | -           |                      |
+| >>>>>QoS Flow Identifier                       | M            |                        | 9.3.1.46                               |                                                                                                               | -           |                      |
+| >>>>>QoS Flow Level<br>QoS Parameters          | M            |                        | 9.3.1.34                               |                                                                                                               | -           |                      |
+| >>>>>QoS Flow Mapping Indication               | O            |                        | 9.3.1.51                               |                                                                                                               | YES         | ignore               |
+| >>UL UP TNL Information                        | M            |                        | UP Transport Layer Information 9.3.2.1 | ng-eNB-CU endpoint of the W1 transport bearer. For delivery of UL PDUs.                                       | -           |                      |
+| >> RLC Mode                                    | M            |                        | 9.3.1.25                               |                                                                                                               | -           |                      |
+| >>DL PDCP SN length                            | M            |                        | ENUMERATE D (12bits, 18bits, ...)      |                                                                                                               | YES         | ignore               |
+| >>UL PDCP SN length                            | O            |                        | ENUMERATE D (12bits, 18bits, ...)      |                                                                                                               | YES         | ignore               |
+| Inactivity Monitoring Request                  | O            |                        | ENUMERATE D (true, ...)                |                                                                                                               | YES         | reject               |
+| RAT-Frequency Priority Information             | O            |                        | 9.3.1.30                               |                                                                                                               | YES         | reject               |
+| RRC-Container                                  | O            |                        | 9.3.1.6                                | Includes the <i>DL-DCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2], encapsulated in a PDCP PDU. | YES         | ignore               |
+| Serving PLMN                                   | O            |                        | PLMN ID 9.3.1.14                       | Indicates the PLMN serving the UE.                                                                            | YES         | ignore               |
+| ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink | C-ifDRBSetup |                        | Bit Rate 9.3.1.22                      | The ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the ng-eNB-DU.                        | YES         | ignore               |
+| Resource Coordination Transfer Information     | O            |                        | 9.3.1.52                               |                                                                                                               | YES         | ignore               |
+
+| Range bound             | Explanation                                                                    |
+|-------------------------|--------------------------------------------------------------------------------|
+| maxnoofSCells           | Maximum no. of SCells allowed towards one UE, the maximum value is 32.         |
+| maxnoofSRBs             | Maximum no. of SRB allowed towards one UE, the maximum value is 4.             |
+| maxnoofDRBs             | Maximum no. of DRB allowed towards one UE, the maximum value is 32.            |
+| maxnoofCandidateSpCells | Maximum no. of SpCells allowed towards one UE, the maximum value is 64.        |
+| maxnoofQoSFlows         | Maximum no. of flows allowed to be mapped to one DRB, the maximum value is 64. |
+
+| Condition  | Explanation                                                                     |
+|------------|---------------------------------------------------------------------------------|
+| ifDRBSetup | This IE shall be present only if the <i>DRB to Be Setup List</i> IE is present. |
+
+## 9.2.2.2 UE CONTEXT SETUP RESPONSE
+
+This message is sent by the ng-eNB-DU to confirm the setup of a UE context.
+
+Direction: ng-eNB-DU → ng-eNB-CU.
+
+| IE/Group Name                            | Presence | Range                | IE type and reference                  | Semantics description                                                                                                   | Criticality | Assigned Criticality |
+|------------------------------------------|----------|----------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                             | M        |                      | 9.3.1.1                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-CU UE W1AP ID                     | M        |                      | 9.3.1.4                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-DU UE W1AP ID                     | M        |                      | 9.3.1.5                                |                                                                                                                         | YES         | reject               |
+| DU To CU RRC Information                 | M        |                      | 9.3.1.58                               |                                                                                                                         | YES         | reject               |
+| C-RNTI                                   | O        |                      | 9.3.1.29                               | C-RNTI allocated at the ng-eNB-DU                                                                                       | YES         | ignore               |
+| Resource Coordination Transfer Container | O        |                      | OCTET STRING                           | Includes the <i>MR-DC Resource Coordination Information</i> IE as defined in TS 38.423 [7] for NGEN-DC and NE-DC cases. | YES         | ignore               |
+| <b>DRB Setup List</b>                    |          | 0..1                 |                                        | The List of DRBs which are successfully established.                                                                    | YES         | ignore               |
+| >DRB Setup Item list                     |          | 1 .. <maxnoofDRBs>   |                                        |                                                                                                                         | EACH        | ignore               |
+| >>DRB ID                                 | M        |                      | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>DL UP TNL Information                  | M        |                      | UP Transport Layer Information 9.3.2.1 | ng-eNB-DU endpoint of the W1 transport bearer. For delivery of DL PDUs.                                                 | -           |                      |
+| <b>SRB Failed to Setup List</b>          |          | 0..1                 |                                        |                                                                                                                         | YES         | ignore               |
+| >SRB Failed to Setup Item                |          | 1 .. <maxnoofSRBs>   |                                        |                                                                                                                         | EACH        | ignore               |
+| >>SRB ID                                 | M        |                      | 9.3.1.7                                |                                                                                                                         | -           |                      |
+| >>Cause                                  | O        |                      | 9.3.1.2                                |                                                                                                                         | -           |                      |
+| <b>DRB Failed to Setup List</b>          |          | 0..1                 |                                        |                                                                                                                         | YES         | ignore               |
+| >DRB Failed to Setup Item                |          | 1 .. <maxnoofDRBs>   |                                        |                                                                                                                         | EACH        | ignore               |
+| >>DRB ID                                 | M        |                      | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>Cause                                  | O        |                      | 9.3.1.2                                |                                                                                                                         | -           |                      |
+| <b>SCell Failed To Setup List</b>        |          | 0..1                 |                                        |                                                                                                                         | YES         | ignore               |
+| >SCell Failed to Setup Item              |          | 1 .. <maxnoofSCells> |                                        |                                                                                                                         | EACH        | ignore               |
+| >>SCell ID                               | M        |                      | E-UTRAN CGI 9.3.1.12                   | SCell Identifier in ng-eNB                                                                                              | -           |                      |
+| >>Cause                                  | O        |                      | 9.3.1.2                                |                                                                                                                         | -           |                      |
+| Inactivity Monitoring Response           | O        |                      | ENUMERATED (not-supported, ...)        |                                                                                                                         | YES         | reject               |
+| <b>SRB Setup List</b>                    |          | 0..1                 |                                        |                                                                                                                         | YES         | ignore               |
+| >SRB Setup Item                          |          | 1 .. <maxnoofSRBs>   |                                        |                                                                                                                         | EACH        | ignore               |
+| >>SRB ID                                 | M        |                      | 9.3.1.7                                |                                                                                                                         | -           |                      |
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+| Range bound   | Explanation                                                            |
+|---------------|------------------------------------------------------------------------|
+| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. |
+| maxnoofSRBs   | Maximum no. of SRB allowed towards one UE, the maximum value is 4.     |
+| maxnoofDRBs   | Maximum no. of DRB allowed towards one UE, the maximum value is 32.    |
+
+### 9.2.2.3 UE CONTEXT SETUP FAILURE
+
+This message is sent by the ng-eNB-DU to indicate that the setup of the UE context was unsuccessful.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                | Presence | Range                            | IE type and reference   | Semantics description                    | Criticality | Assigned Criticality |
+|------------------------------|----------|----------------------------------|-------------------------|------------------------------------------|-------------|----------------------|
+| Message Type                 | M        |                                  | 9.3.1.1                 |                                          | YES         | reject               |
+| ng-eNB-CU UE W1AP ID         | M        |                                  | 9.3.1.4                 |                                          | YES         | reject               |
+| ng-eNB-DU UE W1AP ID         | O        |                                  | 9.3.1.5                 |                                          | YES         | ignore               |
+| Cause                        | M        |                                  | 9.3.1.2                 |                                          | YES         | ignore               |
+| <b>Potential SpCell List</b> |          | 0..1                             |                         |                                          | YES         | ignore               |
+| >Potential SpCell Item IEs   |          | 0..<br><maxnoofPotentialSpCells> |                         |                                          | EACH        | ignore               |
+| >>Potential SpCell ID        | M        |                                  | E-UTRAN CGI<br>9.3.1.12 | Special Cell as defined in TS 38.321 [9] | -           |                      |
+| Criticality Diagnostics      | O        |                                  | 9.3.1.61                |                                          | YES         | ignore               |
+
+| Range bound             | Explanation                                                             |
+|-------------------------|-------------------------------------------------------------------------|
+| maxnoofPotentialSpCells | Maximum no. of SpCells allowed towards one UE, the maximum value is 64. |
+
+### 9.2.2.4 UE CONTEXT RELEASE REQUEST
+
+This message is sent by the ng-eNB-DU to request the ng-eNB-CU to release the UE-associated logical W1.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name        | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|----------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type         | M        |       | 9.3.1.1               |                       | YES         | ignore               |
+| ng-eNB-CU UE W1AP ID | M        |       | 9.3.1.4               |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID | M        |       | 9.3.1.5               |                       | YES         | reject               |
+| Cause                | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+
+### 9.2.2.5 UE CONTEXT RELEASE COMMAND
+
+This message is sent by the ng-eNB-CU to request the ng-eNB-DU to release the UE-associated logical W1 connection.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name            | Presence | Range | IE type and reference | Semantics description                                                                                                                                                                    | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type             | M        |       | 9.3.1.1               |                                                                                                                                                                                          | YES         | reject               |
+| ng-eNB-CU UE W1AP ID     | M        |       | 9.3.1.4               |                                                                                                                                                                                          | YES         | reject               |
+| ng-eNB-DU UE W1AP ID     | M        |       | 9.3.1.5               |                                                                                                                                                                                          | YES         | reject               |
+| Cause                    | M        |       | 9.3.1.2               |                                                                                                                                                                                          | YES         | ignore               |
+| RRC-Container            | O        |       | 9.3.1.6               | Includes the <i>DL-DCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2] encapsulated in a PDCP PDU, or the <i>DL-CCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2]. | YES         | ignore               |
+| SRB ID                   | O        |       | 9.3.1.7               | It shall be included if the <i>RRC-Container</i> IE is present. The ng-eNB-DU shall send the RRC message on the indicated SRB.                                                           | YES         | ignore               |
+| old ng-eNB-DU UE W1AP ID | O        |       | 9.3.1.5               | Include it if RRCReestablishmentRequest is not accepted                                                                                                                                  | YES         | ignore               |
+
+### 9.2.2.6 UE CONTEXT RELEASE COMPLETE
+
+This message is sent by the ng-eNB-DU to confirm the release of the UE-associated logical W1 connection.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| ng-eNB-CU UE W1AP ID    | M        |       | 9.3.1.4               |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID    | M        |       | 9.3.1.5               |                       | YES         | reject               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+### 9.2.2.7 UE CONTEXT MODIFICATION REQUEST
+
+This message is sent by the ng-eNB-CU to provide UE Context information changes to the ng-eNB-DU.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                            | Presence | Range                   | IE type and reference   | Semantics description                                                                                                   | Criticality | Assigned Criticality |
+|------------------------------------------|----------|-------------------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                             | M        |                         | 9.3.1.1                 |                                                                                                                         | YES         | reject               |
+| ng-eNB-CU UE W1AP ID                     | M        |                         | 9.3.1.4                 |                                                                                                                         | YES         | reject               |
+| ng-eNB-DU UE W1AP ID                     | M        |                         | 9.3.1.5                 |                                                                                                                         | YES         | reject               |
+| SpCell ID                                | O        |                         | E-UTRAN CGI<br>9.3.1.12 | Special Cell as defined in TS 38.321 [9]. For handover case, this IE shall be considered as target cell.                | YES         | ignore               |
+| ServCellIndex                            | O        |                         | INTEGER<br>(0..31, ...) |                                                                                                                         | YES         | reject               |
+| DRX Cycle                                | O        |                         | DRX Cycle<br>9.3.1.24   |                                                                                                                         | YES         | ignore               |
+| CU to DU RRC Information                 | O        |                         | 9.3.1.57                |                                                                                                                         | YES         | reject               |
+| Transmission Action Indicator            | O        |                         | 9.3.1.11                |                                                                                                                         | YES         | ignore               |
+| Resource Coordination Transfer Container | O        |                         | OCTET STRING            | Includes the <i>MR-DC Resource Coordination Information</i> IE as defined in TS 38.423 [7] for NGEN-DC and NE-DC cases. | YES         | ignore               |
+| RRC Reconfiguration Complete Indicator   | O        |                         | 9.3.1.28                |                                                                                                                         | YES         | ignore               |
+| RRC-Container                            | O        |                         | 9.3.1.6                 | Includes the <i>RRCConnectionReconfiguration</i> message as defined in TS 36.331 [2], encapsulated in a PDCP PDU.       | YES         | reject               |
+| <b>SCell To Be Setup List</b>            |          | 0..1                    |                         |                                                                                                                         | YES         | ignore               |
+| >SCell to Be Setup Item IEs              |          | 1..<br><maxnoof SCells> |                         |                                                                                                                         | EACH        | ignore               |
+| >>SCell ID                               | M        |                         | E-UTRAN CGI<br>9.3.1.12 | SCell Identifier in ng-eNB                                                                                              | -           |                      |
+| >>SCellIndex                             | M        |                         | INTEGER (1..31)         |                                                                                                                         | -           |                      |
+| <b>SCell To Be Removed List</b>          |          | 0..1                    |                         |                                                                                                                         | YES         | ignore               |
+| >SCell to Be Removed Item IEs            |          | 1..<br><maxnoof SCells> |                         |                                                                                                                         | EACH        | ignore               |
+| >>SCell ID                               | M        |                         | E-UTRAN CGI<br>9.3.1.12 | SCell Identifier in ng-eNB                                                                                              | -           |                      |
+| <b>SRB to Be Setup List</b>              |          | 0..1                    |                         |                                                                                                                         | YES         | reject               |
+| >SRB to Be Setup Item IEs                |          | 1..<br><maxno ofSRBs>   |                         |                                                                                                                         | EACH        | reject               |
+| >>SRB ID                                 | M        |                         | 9.3.1.7                 |                                                                                                                         | -           |                      |
+| <b>DRB to Be Setup List</b>              |          | 0..1                    |                         |                                                                                                                         | YES         | reject               |
+
+| IE/Group Name                                   | Presence | Range                   | IE type and reference                  | Semantics description                                                                                                  | Criticality | Assigned Criticality |
+|-------------------------------------------------|----------|-------------------------|----------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>&gt;DRB to Be Setup Item IEs</b>             |          | 1 .. <maxnoof DRBs>     |                                        |                                                                                                                        | EACH        | reject               |
+| >>DRB ID                                        | M        |                         | 9.3.1.18                               |                                                                                                                        | -           |                      |
+| <b>&gt;&gt;CHOICE QoS Information</b>           | M        |                         |                                        |                                                                                                                        | -           |                      |
+| >>>E-UTRAN QoS                                  | M        |                         | 9.3.1.19                               | Shall be used for EN-DC case to convey E-RAB Level QoS Parameters. This IE is not used in the version of this release. |             |                      |
+| <b>&gt;&gt;&gt;DRB Information</b>              |          | 1                       |                                        | Shall be used for NG-RAN cases                                                                                         | YES         | ignore               |
+| >>>>DRB QoS                                     | M        |                         | 9.3.1.34                               |                                                                                                                        | -           |                      |
+| >>>>S-NSSAI                                     | M        |                         | 9.3.1.32                               |                                                                                                                        | -           |                      |
+| >>>>Notification Control                        | O        |                         | 9.3.1.44                               |                                                                                                                        | -           |                      |
+| <b>&gt;&gt;&gt;&gt;Flows Mapped to DRB Item</b> |          | 1 .. <maxnoof QoSFlows> |                                        |                                                                                                                        | -           |                      |
+| >>>>>QoS Flow Identifier                        | M        |                         | 9.3.1.46                               |                                                                                                                        | -           |                      |
+| >>>>>QoS Flow Level QoS Parameters              | M        |                         | 9.3.1.34                               |                                                                                                                        | -           |                      |
+| >>>>>QoS Flow Mapping Indication                | O        |                         | 9.3.1.51                               |                                                                                                                        | YES         | ignore               |
+| >>UL UP TNL Information                         | M        |                         | UP Transport Layer Information 9.3.2.1 | ng-eNB-CU endpoint of the W1 transport bearer. For delivery of UL PDUs.                                                | -           |                      |
+| >> RLC Mode                                     | M        |                         | 9.3.1.25                               |                                                                                                                        | -           |                      |
+| >>DL PDCP SN length                             | O        |                         | ENUMERATED (12bits, 18bits, ...)       |                                                                                                                        | YES         | ignore               |
+| >>UL PDCP SN length                             | O        |                         | ENUMERATED (12bits, 18bits, ...)       |                                                                                                                        | YES         | ignore               |
+| <b>DRB to Be Modified List</b>                  |          | 0..1                    |                                        |                                                                                                                        | YES         | reject               |
+| <b>&gt;DRB to Be Modified Item IEs</b>          |          | 1 .. <maxnoof DRBs>     |                                        |                                                                                                                        | EACH        | reject               |
+| >>DRB ID                                        | M        |                         | 9.3.1.18                               |                                                                                                                        | -           |                      |
+| <b>&gt;&gt;CHOICE QoS Information</b>           | O        |                         |                                        |                                                                                                                        | -           |                      |
+| >>>E-UTRAN QoS                                  | M        |                         | 9.3.1.19                               | Shall be used for EN-DC case to convey E-RAB Level QoS Parameters. This IE is not used in the version of this release. | -           |                      |
+| <b>&gt;&gt;&gt;DRB Information</b>              |          | 1                       |                                        | Shall be used for NG-RAN cases                                                                                         | YES         | ignore               |
+| >>>>DRB QoS                                     | M        |                         | 9.3.1.34                               |                                                                                                                        | -           |                      |
+
+| IE/Group Name                                  | Presence | Range                   | IE type and reference                  | Semantics description                                                                  | Criticality | Assigned Criticality |
+|------------------------------------------------|----------|-------------------------|----------------------------------------|----------------------------------------------------------------------------------------|-------------|----------------------|
+| >>>>S-NSSAI                                    | M        |                         | 9.3.1.32                               |                                                                                        | -           |                      |
+| >>>>Notification Control                       | O        |                         | 9.3.1.44                               |                                                                                        | -           |                      |
+| >>>>Flows Mapped to DRB Item                   |          | 1 .. <maxnoof QoSFlows> |                                        |                                                                                        | -           |                      |
+| >>>>>QoS Flow Identifier                       | M        |                         | 9.3.1.46                               |                                                                                        | -           |                      |
+| >>>>>QoS Flow Level QoS Parameters             | M        |                         | 9.3.1.34                               |                                                                                        | -           |                      |
+| >>>>>QoS Flow Mapping Indication               | O        |                         | 9.3.1.51                               |                                                                                        | YES         | ignore               |
+| >>UL UP TNL Information                        | M        |                         | UP Transport Layer Information 9.3.2.1 | ng-eNB-CU endpoint of the W1 transport bearer. For delivery of UL PDUs.                | -           |                      |
+| >>DL PDCP SN length                            | O        |                         | ENUMERATED(12bits, 18 bits, ...)       |                                                                                        | YES         | ignore               |
+| >>UL PDCP SN length                            | O        |                         | ENUMERATED(12bits, 18bits, ...)        |                                                                                        | YES         | ignore               |
+| >>Bearer Type Change                           | O        |                         | ENUMERATED(true, ...)                  |                                                                                        | YES         | ignore               |
+| >> RLC Mode                                    | O        |                         | 9.3.1.25                               |                                                                                        | YES         | ignore               |
+| <b>SRB To Be Released List</b>                 |          | 0..1                    |                                        |                                                                                        | YES         | reject               |
+| >SRB To Be Released Item IEs                   |          | 1.. <maxnoof SRBs>      |                                        |                                                                                        | EACH        | reject               |
+| >>SRB ID                                       | M        |                         | 9.3.1.7                                |                                                                                        |             |                      |
+| <b>DRB to Be Released List</b>                 |          | 0..1                    |                                        |                                                                                        | YES         | reject               |
+| >DRB to Be Released Item IEs                   |          | 1 .. <maxnoof DRBs>     |                                        |                                                                                        | EACH        | reject               |
+| >>DRB ID                                       | M        |                         | 9.3.1.8                                |                                                                                        | -           |                      |
+| Inactivity Monitoring Request                  | O        |                         | ENUMERATED(true, ...)                  |                                                                                        | YES         | reject               |
+| ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink | O        |                         | Bit Rate 9.3.1.22                      | The ng-eNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the ng-eNB-DU. | YES         | ignore               |
+| RAT-Frequency Priority Information             | O        |                         | 9.3.1.30                               |                                                                                        | YES         | reject               |
+| Resource Coordination Transfer Information     | O        |                         | 9.3.1.52                               |                                                                                        | YES         | ignore               |
+
+| IE/Group Name | Presence | Range | IE type and reference      | Semantics description | Criticality | Assigned Criticality |
+|---------------|----------|-------|----------------------------|-----------------------|-------------|----------------------|
+| SCG Indicator | O        |       | ENUMERATED (released, ...) |                       | YES         | ignore               |
+
+| Range bound     | Explanation                                                                    |
+|-----------------|--------------------------------------------------------------------------------|
+| maxnoofSCells   | Maximum no. of SCells allowed towards one UE, the maximum value is 32.         |
+| maxnoofSRBs     | Maximum no. of SRB allowed towards one UE, the maximum value is 4.             |
+| maxnoofDRBs     | Maximum no. of DRB allowed towards one UE, the maximum value is 32.            |
+| maxnoofQoSFlows | Maximum no. of flows allowed to be mapped to one DRB, the maximum value is 64. |
+
+### 9.2.2.8 UE CONTEXT MODIFICATION RESPONSE
+
+This message is sent by the ng-eNB-DU to confirm the modification of a UE context.
+
+Direction: ng-eNB-DU → ng-eNB-CU.
+
+| IE/Group Name                            | Presence | Range              | IE type and reference                  | Semantics description                                                                                                   | Criticality | Assigned Criticality |
+|------------------------------------------|----------|--------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                             | M        |                    | 9.3.1.1                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-CU UE W1AP ID                     | M        |                    | 9.3.1.4                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-DU UE W1AP ID                     | M        |                    | 9.3.1.5                                |                                                                                                                         | YES         | reject               |
+| Resource Coordination Transfer Container | O        |                    | OCTET STRING                           | Includes the <i>MR-DC Resource Coordination Information</i> IE as defined in TS 38.423 [7] for NGEN-DC and NE-DC cases. | YES         | ignore               |
+| DU To CU RRC Information                 | O        |                    | 9.3.1.58                               |                                                                                                                         | YES         | reject               |
+| <b>DRB Setup List</b>                    |          | 0..1               |                                        | The List of DRBs which are successfully established.                                                                    | YES         | ignore               |
+| >DRB Setup Item IEs                      |          | 1 .. <maxnootDRBs> |                                        |                                                                                                                         | EACH        | ignore               |
+| >>DRB ID                                 | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>DL UP TNL Information                  | M        |                    | UP Transport Layer Information 9.3.2.1 | ng-eNB-DU endpoint of the W1 transport bearer. For delivery of DL PDUs.                                                 | -           |                      |
+| <b>DRB Modified List</b>                 |          | 0..1               |                                        | The List of DRBs which are successfully modified.                                                                       | YES         | ignore               |
+| >DRB Modified Item IEs                   |          | 1 .. <maxnootDRBs> |                                        |                                                                                                                         | EACH        | ignore               |
+| >>DRB ID                                 | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>DL UP TNL Information                  | M        |                    | UP Transport Layer Information 9.3.2.1 | ng-eNB-DU endpoint of the W1 transport bearer. For delivery of DL PDUs.                                                 | -           |                      |
+| >>RLC Status                             | O        |                    | 9.3.1.49                               | Indicates the RLC has been re-established at the ng-eNB-DU.                                                             | YES         | ignore               |
+| <b>SRB Failed to be Setup List</b>       |          | 0..1               |                                        | The List of SRBs which are failed to be established.                                                                    | YES         | ignore               |
+| >SRB Failed to be Setup Item IEs         |          | 1 .. <maxnootSRBs> |                                        |                                                                                                                         | EACH        | ignore               |
+| >>SRB ID                                 | M        |                    | 9.3.1.7                                |                                                                                                                         | -           |                      |
+| >>Cause                                  | O        |                    | 9.3.1.2                                |                                                                                                                         | -           |                      |
+| <b>DRB Failed to be Setup List</b>       |          | 0..1               |                                        | The List of DRBs which are failed to be setup.                                                                          | YES         | ignore               |
+| >DRB Failed to be Setup Item IEs         |          | 1 .. <maxnootDRBs> |                                        |                                                                                                                         | EACH        | ignore               |
+| >>DRB ID                                 | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>Cause                                  | O        |                    | 9.3.1.2                                |                                                                                                                         | -           |                      |
+
+| IE/Group Name                         | Presence | Range                       | IE type and reference                   | Semantics description                                      | Criticality | Assigned Criticality |
+|---------------------------------------|----------|-----------------------------|-----------------------------------------|------------------------------------------------------------|-------------|----------------------|
+| <b>SCell Failed To Setup List</b>     |          | 0..1                        |                                         |                                                            | YES         | ignore               |
+| >SCell Failed to Setup Item           |          | 1 ..<br><maxnoo<br>fSCells> |                                         |                                                            | EACH        | ignore               |
+| >>SCell ID                            | M        |                             | E-UTRAN CGI<br>9.3.1.12                 | SCell Identifier<br>in ng-eNB                              | -           |                      |
+| >>Cause                               | O        |                             | 9.3.1.2                                 |                                                            | -           |                      |
+| <b>DRB Failed to be Modified List</b> |          | 0..1                        |                                         | The List of<br>DRBs which are<br>failed to be<br>modified. | YES         | ignore               |
+| >DRB Failed to be Modified Item IEs   |          | 1 ..<br><maxnoo<br>fDRBs>   |                                         |                                                            | EACH        | ignore               |
+| >>DRB ID                              | M        |                             | 9.3.1.8                                 |                                                            | -           |                      |
+| >>Cause                               | O        |                             | 9.3.1.2                                 |                                                            | -           |                      |
+| Inactivity Monitoring Response        | O        |                             | ENUMERATE<br>D (Not-<br>supported, ...) |                                                            | YES         | reject               |
+| C-RNTI                                | O        |                             | 9.3.1.29                                | C-RNTI<br>allocated at the<br>ng-eNB-DU                    | YES         | ignore               |
+| <b>SRB Setup List</b>                 |          | 0..1                        |                                         |                                                            | YES         | ignore               |
+| >SRB Setup Item                       |          | 1 ..<br><maxnoo<br>fSRBs>   |                                         |                                                            | EACH        | ignore               |
+| >>SRB ID                              | M        |                             | 9.3.1.7                                 |                                                            | -           |                      |
+| <b>SRB Modified List</b>              |          | 0..1                        |                                         |                                                            | YES         | ignore               |
+| >SRB Modified Item                    |          | 1 ..<br><maxnoo<br>fSRBs>   |                                         |                                                            | EACH        | ignore               |
+| >>SRB ID                              | M        |                             | 9.3.1.7                                 |                                                            | -           |                      |
+| Criticality Diagnostics               | O        |                             | 9.3.1.61                                |                                                            | YES         | ignore               |
+
+| Range bound   | Explanation                                                            |
+|---------------|------------------------------------------------------------------------|
+| maxnoofSRBs   | Maximum no. of SRB allowed towards one UE, the maximum value is 4.     |
+| maxnoofDRBs   | Maximum no. of DRB allowed towards one UE, the maximum value is 32.    |
+| maxnoofSCells | Maximum no. of SCells allowed towards one UE, the maximum value is 32. |
+
+### 9.2.2.9 UE CONTEXT MODIFICATION FAILURE
+
+This message is sent by the ng-eNB-DU to indicate a context modification failure.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| ng-eNB-CU UE W1AP ID    | M        |       | 9.3.1.4               |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID    | M        |       | 9.3.1.5               |                       | YES         | reject               |
+| Cause                   | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+### 9.2.2.10 UE CONTEXT MODIFICATION REQUIRED
+
+This message is sent by the ng-eNB-DU to request the modification of a UE context.
+
+Direction: ng-eNB-DU → ng-eNB-CU.
+
+| IE/Group Name                              | Presence | Range              | IE type and reference                  | Semantics description                                                                                                   | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|--------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                               | M        |                    | 9.3.1.1                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-CU UE W1AP ID                       | M        |                    | 9.3.1.4                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-DU UE W1AP ID                       | M        |                    | 9.3.1.5                                |                                                                                                                         | YES         | reject               |
+| Resource Coordination Transfer Container   | O        |                    | OCTET STRING                           | Includes the <i>MR-DC Resource Coordination Information</i> IE as defined in TS 38.423 [7] for NGEN-DC and NE-DC cases. | YES         | ignore               |
+| DU To CU RRC Information                   | O        |                    | 9.3.1.58                               |                                                                                                                         | YES         | reject               |
+| <b>DRB Required to Be Modified List</b>    |          | 0..1               |                                        |                                                                                                                         | YES         | reject               |
+| >DRB Required to Be Modified Item IEs      |          | 1 .. <maxnoofDRBs> |                                        |                                                                                                                         | EACH        | reject               |
+| >>DRB ID                                   | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| >>DL UP TNL Information                    | M        |                    | UP Transport Layer Information 9.3.2.1 | ng-eNB-DU endpoint of the W1 transport bearer. For delivery of DL PDUs.                                                 | -           |                      |
+| >>RLC Status                               | O        |                    | 9.3.1.49                               | Indicates the RLC has been re-established at the ng-eNB-DU.                                                             | YES         | ignore               |
+| <b>SRB Required to be Released List</b>    |          | 0..1               |                                        |                                                                                                                         | YES         | reject               |
+| >SRB Required to be Released List Item IEs |          | 1 .. <maxnoofSRBs> |                                        |                                                                                                                         | EACH        | reject               |
+| >>SRB ID                                   | M        |                    | 9.3.1.7                                |                                                                                                                         | -           |                      |
+| <b>DRB Required to be Released List</b>    |          | 0..1               |                                        |                                                                                                                         | YES         | reject               |
+| >DRB Required to be Released List Item IEs |          | 1 .. <maxnoofDRBs> |                                        |                                                                                                                         | EACH        | reject               |
+| >>DRB ID                                   | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| Cause                                      | M        |                    | 9.3.1.2                                |                                                                                                                         | YES         | ignore               |
+
+| Range bound | Explanation                                                         |
+|-------------|---------------------------------------------------------------------|
+| maxnoofSRBs | Maximum no. of SRB allowed towards one UE, the maximum value is 4.  |
+| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
+
+### 9.2.2.11 UE CONTEXT MODIFICATION CONFIRM
+
+This message is sent by the ng-eNB-CU to inform the ng-eNB-DU the successful modification.
+
+Direction: ng-eNB-CU → ng-eNB-DU.
+
+| IE/Group Name                              | Presence | Range              | IE type and reference                  | Semantics description                                                                                                   | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|--------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                               | M        |                    | 9.3.1.1                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-CU UE W1AP ID                       | M        |                    | 9.3.1.4                                |                                                                                                                         | YES         | reject               |
+| ng-eNB-DU UE W1AP ID                       | M        |                    | 9.3.1.5                                |                                                                                                                         | YES         | reject               |
+| Resource Coordination Transfer Container   | O        |                    | OCTET STRING                           | Includes the <i>MR-DC Resource Coordination Information</i> IE as defined in TS 38.423 [7] for NGEN-DC and NE-DC cases. | YES         | ignore               |
+| <b>DRB Modified List</b>                   |          | 0..1               |                                        | The List of DRBs which are successfully modified.                                                                       | YES         | ignore               |
+| <b>&gt;DRB Modified Item IEs</b>           |          | 1 .. <maxnoofDRBs> |                                        |                                                                                                                         | EACH        | ignore               |
+| <b>&gt;&gt;DRB ID</b>                      | M        |                    | 9.3.1.8                                |                                                                                                                         | -           |                      |
+| <b>&gt;&gt;UL UP TNL Information</b>       | M        |                    | UP Transport Layer Information 9.3.2.1 | ng-eNB-DU endpoint of the W1 transport bearer. For delivery of UL PDUs.                                                 | -           |                      |
+| RRC-Container                              | O        |                    | 9.3.1.6                                | Includes the <i>RRCConnectionReconfiguration</i> message as defined in TS 36.331 [2], encapsulated in a PDCP PDU.       | YES         | ignore               |
+| Resource Coordination Transfer Information | O        |                    | 9.3.1.52                               |                                                                                                                         | YES         | ignore               |
+| Criticality Diagnostics                    | O        |                    | 9.3.1.61                               |                                                                                                                         | YES         | ignore               |
+
+| Range bound | Explanation                                                         |
+|-------------|---------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
+
+### 9.2.2.12 UE CONTEXT MODIFICATION REFUSE
+
+This message is sent by the ng-eNB-CU to indicate the UE context modification was unsuccessful.
+
+Direction: ng-eNB-CU → ng-eNB-DU.
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|-------------------------|----------|-------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type            | M        |       | 9.3.1.1               |                       | YES         | reject               |
+| ng-eNB-CU UE W1AP ID    | M        |       | 9.3.1.4               |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID    | M        |       | 9.3.1.5               |                       | YES         | reject               |
+| Cause                   | M        |       | 9.3.1.2               |                       | YES         | ignore               |
+| Criticality Diagnostics | O        |       | 9.3.1.61              |                       | YES         | ignore               |
+
+### 9.2.2.13 UE INACTIVITY NOTIFICATION
+
+This message is sent by the ng-eNB-DU to provide information about the UE activity to the ng-eNB-CU.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name              | Presence | Range              | IE type and reference           | Semantics description | Criticality | Assigned Criticality |
+|----------------------------|----------|--------------------|---------------------------------|-----------------------|-------------|----------------------|
+| Message Type               | M        |                    | 9.3.1.1                         |                       | YES         | ignore               |
+| ng-eNB-CU UE W1AP ID       | M        |                    | 9.3.1.4                         |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID       | M        |                    | 9.3.1.5                         |                       | YES         | reject               |
+| <b>DRB Activity List</b>   |          | 1                  |                                 |                       | YES         | reject               |
+| > <b>DRB Activity Item</b> |          | 1 .. <maxnoofDRBs> |                                 |                       | EACH        | reject               |
+| >>DRB ID                   | M        |                    | 9.3.1.8                         |                       | -           |                      |
+| >>DRB Activity             | O        |                    | ENUMERATED (Active, Not active) |                       | -           |                      |
+
+| Range bound | Explanation                                                         |
+|-------------|---------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
+
+### 9.2.2.14 NOTIFY
+
+This message is sent by the ng-eNB-DU to notify the ng-eNB-CU that the QoS for already established DRBs associated with notification control is not fulfilled any longer or it is fulfilled again.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                | Presence | Range              | IE type and reference                      | Semantics description | Criticality | Assigned Criticality |
+|------------------------------|----------|--------------------|--------------------------------------------|-----------------------|-------------|----------------------|
+| Message Type                 | M        |                    | 9.3.1.1                                    |                       | YES         | ignore               |
+| ng-eNB-CU UE W1AP ID         | M        |                    | 9.3.1.4                                    |                       | YES         | reject               |
+| ng-eNB-DU UE W1AP ID         | M        |                    | 9.3.1.5                                    |                       | YES         | reject               |
+| <b>DRB Notify List</b>       |          | 1                  |                                            |                       | YES         | reject               |
+| > <b>DRB Notify Item IEs</b> |          | <1 .. maxnoofDRBs> |                                            |                       | EACH        | reject               |
+| >>DRB ID                     | M        |                    | 9.3.1.8                                    |                       | -           |                      |
+| >>Notification Cause         | M        |                    | ENUMERATED (Fulfilled, Not-Fulfilled, ...) |                       | -           |                      |
+
+| Range bound | Explanation                                                         |
+|-------------|---------------------------------------------------------------------|
+| maxnoofDRBs | Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
+
+## 9.2.3 RRC Message Transfer messages
+
+### 9.2.3.1 INITIAL UL RRC MESSAGE TRANSFER
+
+This message is sent by the ng-eNB-DU to transfer the initial layer 3 message to the ng-eNB-CU over the W1 interface.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name          | Presence | Range | IE type and reference | Semantics description                                                                                                              | Criticality | Assigned Criticality |
+|------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type           | M        |       | 9.3.1.1               |                                                                                                                                    | YES         | ignore               |
+| Transaction ID         | M        |       | 9.3.1.23              |                                                                                                                                    | YES         | ignore               |
+| ng-eNB-DU UE W1AP ID   | M        |       | 9.3.1.5               |                                                                                                                                    | YES         | reject               |
+| E-UTRAN CGI            | M        |       | 9.3.1.12              | NG-RAN Cell Global Identifier                                                                                                      | YES         | reject               |
+| C-RNTI                 | M        |       | 9.3.1.29              | C-RNTI allocated at the ng-eNB-DU                                                                                                  | YES         | reject               |
+| RRC-Container          | M        |       | 9.3.1.6               | Includes the <i>UL-CCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2].                                                  | YES         | reject               |
+| DU to CU RRC Container | O        |       | OCTET STRING          | <i>RadioResourceConfigDedicated</i> IE as defined in clause 6.3.2 in TS 36.331 [2]. Required at least to carry SRB1 configuration. | YES         | reject               |
+
+### 9.2.3.2 DL RRC MESSAGE TRANSFER
+
+This message is sent by the ng-eNB-CU to transfer the layer 3 message to the ng-eNB-DU over the W1 interface.
+
+Direction: ng-eNB-CU →ng-eNB-DU
+
+| IE/Group Name            | Presence | Range | IE type and reference | Semantics description                                                                                                                                                                    | Criticality | Assigned Criticality |
+|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type             | M        |       | 9.3.1.1               |                                                                                                                                                                                          | YES         | ignore               |
+| ng-eNB-CU UE W1AP ID     | M        |       | 9.3.1.4               |                                                                                                                                                                                          | YES         | reject               |
+| ng-eNB-DU UE W1AP ID     | M        |       | 9.3.1.5               |                                                                                                                                                                                          | YES         | reject               |
+| old ng-eNB-DU UE W1AP ID | O        |       | 9.3.1.5               | Include it if RRCConnectionReestablishment is included in RRC-Container                                                                                                                  | YES         | reject               |
+| SRB ID                   | M        |       | 9.3.1.7               |                                                                                                                                                                                          | YES         | reject               |
+| RRC-Container            | M        |       | 9.3.1.6               | Includes the <i>DL-DCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2] encapsulated in a PDCP PDU, or the <i>DL-CCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2]. | YES         | reject               |
+
+### 9.2.3.3 UL RRC MESSAGE TRANSFER
+
+This message is sent by the ng-eNB-DU to transfer the layer 3 message to the ng-eNB-CU over the W1 interface.
+
+Direction: ng-eNB-DU →ng-eNB-CU
+
+| IE/Group Name        | Presence | Range | IE type and reference | Semantics description                                                                                         | Criticality | Assigned Criticality |
+|----------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type         | M        |       | 9.3.1.1               |                                                                                                               | YES         | ignore               |
+| ng-eNB-CU UE W1AP ID | M        |       | 9.3.1.4               |                                                                                                               | YES         | reject               |
+| ng-eNB-DU UE W1AP ID | M        |       | 9.3.1.5               |                                                                                                               | YES         | reject               |
+| SRB ID               | M        |       | 9.3.1.7               |                                                                                                               | YES         | reject               |
+| RRC-Container        | M        |       | 9.3.1.6               | Includes the <i>UL-DCCH-Message</i> IE as defined in clause 6.2 of TS 36.331 [2], encapsulated in a PDCP PDU. | YES         | reject               |
+
+## 9.2.4 Warning Message Transmission Messages
+
+### 9.2.4.1 WRITE-REPLACE WARNING REQUEST
+
+This message is sent by the ng-eNB-CU to request the start or overwrite of the broadcast of a warning message.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                    | Presence | Range                               | IE type and reference | Semantics description                                                                    | Criticality | Assigned Criticality |
+|----------------------------------|----------|-------------------------------------|-----------------------|------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                     | M        |                                     | 9.3.1.1               |                                                                                          | YES         | reject               |
+| Transaction ID                   | M        |                                     | 9.3.1.23              |                                                                                          | YES         | reject               |
+| PWS System Information           | M        |                                     | 9.3.1.3               | This IE includes the system information for public warning, as defined in TS 36.331 [2]. | YES         | reject               |
+| Repetition Period                | M        |                                     | 9.3.1.13              |                                                                                          | YES         | reject               |
+| Number of Broadcasts Requested   | M        |                                     | 9.3.1.60              |                                                                                          | YES         | reject               |
+| <b>Cell To Be Broadcast List</b> |          | 0..1                                |                       |                                                                                          | YES         | reject               |
+| >Cell to Be Broadcast Item IEs   |          | 1..<br><maxCelli<br>nng-<br>eNBIDU> |                       |                                                                                          | EACH        | reject               |
+| >>E-UTRAN CGI                    | M        |                                     | 9.3.1.12              |                                                                                          | -           |                      |
+
+| Range bound        | Explanation                                                         |
+|--------------------|---------------------------------------------------------------------|
+| maxCellinng-eNBIDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.4.2 WRITE-REPLACE WARNING RESPONSE
+
+This message is sent by the ng-eNB-DU to acknowledge the ng-eNB-CU on the start or overwrite request of a warning message.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                        | Presence | Range                      | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|--------------------------------------|----------|----------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type                         | M        |                            | 9.3.1.1               |                       | YES         | reject               |
+| Transaction ID                       | M        |                            | 9.3.1.23              |                       | YES         | reject               |
+| <b>Cell Broadcast Completed List</b> |          | 0..1                       |                       |                       | YES         | reject               |
+| >Cell Broadcast Completed Item IEs   |          | 1..<br><maxCellInng-eNBDU> |                       |                       | EACH        | reject               |
+| >>E-UTRAN CGI                        | M        |                            | 9.3.1.12              |                       | -           |                      |
+| Criticality Diagnostics              | O        |                            | 9.3.1.61              |                       | YES         | ignore               |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellInng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.4.3 PWS CANCEL REQUEST
+
+This message is forwarded by the ng-eNB-CU to ng-eNB-DU to cancel an already ongoing broadcast of a warning message
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name                              | Presence | Range                      | IE type and reference | Semantics description                                                                  | Criticality | Assigned Criticality |
+|--------------------------------------------|----------|----------------------------|-----------------------|----------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                               | M        |                            | 9.3.1.1               |                                                                                        | YES         | reject               |
+| Transaction ID                             | M        |                            | 9.3.1.23              |                                                                                        | YES         | reject               |
+| <b>Cell Broadcast To Be Cancelled List</b> |          | 0..1                       |                       |                                                                                        | YES         | reject               |
+| >Cell Broadcast to Be Cancelled Item IEs   |          | 1..<br><maxCellInng-eNBDU> |                       |                                                                                        | EACH        | reject               |
+| >>E-UTRAN CGI                              | M        |                            | 9.3.1.12              |                                                                                        | -           |                      |
+| Cancel-all Warning Messages Indicator      | O        |                            |                       | ENUMERATED (true, ...)                                                                 | YES         | reject               |
+| <b>Notification Information</b>            | M        |                            |                       | This IE is ignored If the <i>Cancel-all Warning Messages Indicator</i> IE is included. | YES         | reject               |
+| >Message Identifier                        | M        |                            | 9.3.1.67              |                                                                                        |             |                      |
+| >Serial Number                             | M        |                            | 9.3.1.68              |                                                                                        |             |                      |
+
+| Range bound       | Explanation                                                         |
+|-------------------|---------------------------------------------------------------------|
+| maxCellInng-eNBDU | Maximum no. cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.4.4 PWS CANCEL RESPONSE
+
+This message is sent by the ng-eNB-DU to indicate the list of warning areas where cancellation of the broadcast of the identified message was successful and unsuccessful.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                        | Presence | Range                      | IE type and reference | Semantics description                                                                                                             | Criticality | Assigned Criticality |
+|--------------------------------------|----------|----------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type                         | M        |                            | 9.3.1.1               |                                                                                                                                   | YES         | reject               |
+| Transaction ID                       | M        |                            | 9.3.1.23              |                                                                                                                                   | YES         | reject               |
+| <b>Cell Broadcast Cancelled List</b> |          | 0..1                       |                       |                                                                                                                                   | YES         | reject               |
+| >Cell Broadcast Cancelled Item IEs   |          | 1..<br><maxCellinng-eNBDU> |                       |                                                                                                                                   | EACH        | reject               |
+| >>E-UTRAN CGI                        | M        |                            | 9.3.1.12              |                                                                                                                                   | -           |                      |
+| >>Number of Broadcasts               | M        |                            | INTEGER<br>(0..65535) | This IE is set to '0' if valid results are not known or not available. It is set to 65535 if the counter results have overflowed. | -           |                      |
+| Criticality Diagnostics              | O        |                            | 9.3.1.61              |                                                                                                                                   | YES         | ignore               |
+
+| Range bound       | Explanation                                                            |
+|-------------------|------------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum no. of cells that can be served by an ng-eNB-DU. Value is 512. |
+
+#### 9.2.4.5 PWS RESTART INDICATION
+
+This message is sent by the ng-eNB-DU to inform the ng-eNB-CU that PWS information for some or all cells of the ng-eNB-DU are available if needed.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                            | Presence | Range                      | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------------|----------|----------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type                             | M        |                            | 9.3.1.1               |                       | YES         | ignore               |
+| Transaction ID                           | M        |                            | 9.3.1.23              |                       | YES         | reject               |
+| <b>E-UTRAN CGI List for Restart List</b> |          | 1                          |                       |                       | YES         | reject               |
+| > E-UTRAN CGI List for Restart Item IEs  |          | 1..<br><maxCellinng-eNBDU> |                       |                       | EACH        | reject               |
+| >>E-UTRAN CGI                            | M        |                            | 9.3.1.12              |                       | -           |                      |
+
+| Range bound       | Explanation                                                            |
+|-------------------|------------------------------------------------------------------------|
+| maxCellinng-eNBDU | Maximum no. of cells that can be served by an ng-eNB-DU. Value is 512. |
+
+### 9.2.4.6 PWS FAILURE INDICATION
+
+This message is sent by the ng-eNB-DU to inform the ng-eNB-CU that ongoing PWS operation for one or more cells of the ng-eNB-DU has failed.
+
+Direction: ng-eNB-DU → ng-eNB-CU
+
+| IE/Group Name                      | Presence | Range                   | IE type and reference | Semantics description | Criticality | Assigned Criticality |
+|------------------------------------|----------|-------------------------|-----------------------|-----------------------|-------------|----------------------|
+| Message Type                       | M        |                         | 9.3.1.1               |                       | YES         | ignore               |
+| Transaction ID                     | M        |                         | 9.3.1.23              |                       | YES         | reject               |
+| <b>PWS failed E-UTRAN CGI List</b> |          | 0..1                    |                       |                       | YES         | reject               |
+| >PWS failed E-UTRAN CGI Item IEs   |          | 1..<maxCellinng-eNBDDU> |                       |                       | EACH        | reject               |
+| >>E-UTRAN CGI                      | M        |                         | 9.3.1.12              |                       | -           |                      |
+
+| Range bound        | Explanation                                                            |
+|--------------------|------------------------------------------------------------------------|
+| maxCellinng-eNBDDU | Maximum no. of cells that can be served by an ng-eNB-DU. Value is 512. |
+
+## 9.2.5 Paging messages
+
+### 9.2.5.1 PAGING
+
+This message is sent by the ng-eNB-CU and is used to request the ng-eNB-DU to page UEs.
+
+Direction: ng-eNB-CU → ng-eNB-DU
+
+| IE/Group Name           | Presence | Range                     | IE type and reference | Semantics description                                                           | Criticality | Assigned Criticality |
+|-------------------------|----------|---------------------------|-----------------------|---------------------------------------------------------------------------------|-------------|----------------------|
+| Message Type            | M        |                           | 9.3.1.1               |                                                                                 | YES         | ignore               |
+| UE Identity Index value | M        |                           | 9.3.1.63              |                                                                                 | YES         | reject               |
+| CHOICE Paging Identity  | M        |                           |                       |                                                                                 | YES         | reject               |
+| >RAN UE Paging identity | M        |                           | 9.3.1.64              |                                                                                 | -           |                      |
+| >CN UE paging identity  | M        |                           | 9.3.1.65              |                                                                                 | -           |                      |
+| Paging DRX              | O        |                           | 9.3.1.66              | It is defined as the minimum between the RAN UE Paging DRX and CN UE Paging DRX | YES         | ignore               |
+| <b>Paging Cell List</b> |          | 1                         |                       |                                                                                 | YES         | ignore               |
+| >Paging Cell Item IEs   |          | 1 .. <maxnoofPagingCells> |                       |                                                                                 | EACH        | ignore               |
+| >> E-UTRAN CGI          | M        |                           | 9.3.1.12              |                                                                                 | -           |                      |
+| Paging Origin           | O        |                           | 9.3.1.70              |                                                                                 | YES         | ignore               |
+
+| Range bound        | Explanation                                            |
+|--------------------|--------------------------------------------------------|
+| maxnoofPagingCells | Maximum no. of paging cells, the maximum value is 512. |
+
+## 9.3 Information Element Definitions
+
+### 9.3.1 Radio Network Layer Related IEs
+
+#### 9.3.1.1 Message Type
+
+The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages.
+
+| IE/Group Name       | Presence | Range | IE type and reference                                                      | Semantics description |
+|---------------------|----------|-------|----------------------------------------------------------------------------|-----------------------|
+| <b>Message Type</b> |          |       |                                                                            |                       |
+| >Procedure Code     | M        |       | INTEGER (0..255)                                                           |                       |
+| >Type of Message    | M        |       | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) |                       |
+
+#### 9.3.1.2 Cause
+
+The purpose of the *Cause* IE is to indicate the reason for a particular event for the WIAP protocol.
+
+| IE/Group Name               | Presence | Range | IE Type and Reference                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Semantics Description |
+|-----------------------------|----------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|
+| <b>CHOICE Cause Group</b>   | M        |       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| >Radio Network Layer        |          |       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| >>Radio Network Layer Cause | M        |       | ENUMERATED<br>(Unspecified, RL failure-RLC, Unknown or already allocated ng-eNB-CU UE W1AP ID, Unknown or already allocated ng-eNB-DU UE W1AP ID, Unknown or inconsistent pair of UE W1AP ID, Interaction with other procedure, Not supported QCI Value, Action Desirable for Radio Reasons, No Radio Resources Available, Procedure cancelled, Normal Release, Cell not available, RL failure-others, UE rejection, Resources not available for the slice, AMF initiated abnormal release, Release due to Pre-Emption, Multiple DRB ID Instances, Unknown DRB ID, ...) |                       |
+| >Transport Layer            |          |       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| >>Transport Layer Cause     | M        |       | ENUMERATED<br>(Unspecified, Transport Resource Unavailable, ...)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |                       |
+| >Protocol                   |          |       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| >>Protocol Cause            | M        |       | ENUMERATED<br>(Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), Unspecified, ...)                                                                                                                                                                                                                                                                                                                     |                       |
+| >Misc                       |          |       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |                       |
+| >>Miscellaneous Cause       | M        |       | ENUMERATED<br>(Control Processing Overload, Not enough User Plane Processing Resources, Hardware Failure, O&M Intervention, Unspecified, ...)                                                                                                                                                                                                                                                                                                                                                                                                                           |                       |
+
+The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action.
+
+| Radio Network Layer cause                         | Meaning                                                                                                                                                                         |
+|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Unspecified                                       | Sent for radio network layer cause when none of the specified cause values applies.                                                                                             |
+| RL Failure-RLC                                    | The action is due to an RL failure caused by exceeding the maximum number of ARQ retransmissions.                                                                               |
+| Unknown or already allocated ng-eNB-CU UE W1AP ID | The action failed because the ng-eNB-CU UE W1AP ID is either unknown, or (for a first message received at the ng-eNB-CU) is known and already allocated to an existing context. |
+| Unknown or already allocated ng-eNB-DU UE W1AP ID | The action failed because the ng-eNB-DU UE W1AP ID is either unknown, or (for a first message received at the ng-eNB-DU) is known and already allocated to an existing context. |
+| Unknown or inconsistent pair of UE W1AP ID        | The action failed because both UE W1AP IDs are unknown, or are known but do not define a single UE context.                                                                     |
+| Interaction with other procedure                  | The action is due to an ongoing interaction with another procedure.                                                                                                             |
+| Not supported QCI Value                           | The action failed because the requested QCI is not supported.                                                                                                                   |
+| Action Desirable for Radio Reasons                | The reason for requesting the action is radio related.                                                                                                                          |
+| No Radio Resources Available                      | The cell(s) in the requested node don't have sufficient radio resources available.                                                                                              |
+| Procedure cancelled                               | The sending node cancelled the procedure due to other urgent actions to be performed.                                                                                           |
+| Normal Release                                    | The action is due to a normal release of the UE (e.g. because of mobility) and does not indicate an error.                                                                      |
+| Cell Not Available                                | The action failed due to no cell available in the requested node.                                                                                                               |
+| RL Failure-others                                 | The action is due to an RL failure caused by other radio link failures than exceeding the maximum number of ARQ retransmissions.                                                |
+| UE rejection                                      | The action is due to ng-eNB-CU's rejection of a UE access request.                                                                                                              |
+| Resources not available for the slice             | The requested resources are not available for the slice.                                                                                                                        |
+| AMF initiated abnormal release                    | The release is triggered by an error in the AMF or in the NAS layer.                                                                                                            |
+| Release due to Pre-Emption                        | Release is initiated due to pre-emption.                                                                                                                                        |
+| Multiple DRB ID Instances                         | The action failed because multiple instances of the same DRB had been provided.                                                                                                 |
+| Unknown DRB ID                                    | The action failed because the DRB ID is unknown.                                                                                                                                |
+
+| Transport Layer cause          | Meaning                                                                                                  |
+|--------------------------------|----------------------------------------------------------------------------------------------------------|
+| Unspecified                    | Sent when none of the above cause values applies but still the cause is Transport Network Layer related. |
+| Transport Resource Unavailable | The required transport resources are not available.                                                      |
+
+| Protocol cause                                      | Meaning                                                                                                              |
+|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| Transfer Syntax Error                               | The received message included a transfer syntax error.                                                               |
+| Abstract Syntax Error (Reject)                      | The received message included an abstract syntax error and the concerning criticality indicated "reject".            |
+| Abstract Syntax Error (Ignore And Notify)           | The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". |
+| Message Not Compatible With Receiver State          | The received message was not compatible with the receiver state.                                                     |
+| Semantic Error                                      | The received message included a semantic error.                                                                      |
+| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences.                         |
+| Unspecified                                         | Sent when none of the above cause values applies but still the cause is Protocol related.                            |
+
+| Miscellaneous cause                                  | Meaning                                                                                                                                                          |
+|------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Control Processing Overload                          | Control processing overload.                                                                                                                                     |
+| Not Enough User Plane Processing Resources Available | No enough resources are available related to user plane processing.                                                                                              |
+| Hardware Failure                                     | Action related to hardware failure.                                                                                                                              |
+| O&M Intervention                                     | The action is due to O&M intervention.                                                                                                                           |
+| Unspecified Failure                                  | Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. |
+
+### 9.3.1.3 PWS System Information
+
+This IE contains the system information used for public warning.
+
+| IE/Group Name                   | Presence | Range | IE type and reference | Semantics description                                                                                                                      | Criticality | Assigned Criticality |
+|---------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| SIB type                        | M        |       | INTEGER (10..12, ...) | Indicates a certain SIB block for public warning message, e.g. 10 means sibType10, 11 for sibType11, etc.                                  | -           |                      |
+| SIB message                     | M        |       | OCTET STRING          | SIB message for public warning, as defined in TS 36.331 [2].                                                                               | -           |                      |
+| <b>Notification Information</b> | M        |       |                       |                                                                                                                                            | YES         | ignore               |
+| >Message Identifier             | M        |       | 9.3.1.67              |                                                                                                                                            | -           |                      |
+| >Serial Number                  | M        |       | 9.3.1.68              |                                                                                                                                            | -           |                      |
+| Additional SIB Message List     | O        |       | 9.3.1.69              | Additional SIB messages containing different segments of a public warning message if segmentation is applied, as defined in TS 36.331 [2]. | Yes         | reject               |
+
+### 9.3.1.4 ng-eNB-CU UE W1AP ID
+
+The ng-eNB-CU UE W1AP ID uniquely identifies the UE association over the W1 interface within the ng-eNB-CU.
+
+| IE/Group Name        | Presence | Range | IE type and reference             | Semantics description |
+|----------------------|----------|-------|-----------------------------------|-----------------------|
+| ng-eNB-CU UE W1AP ID | M        |       | INTEGER (0 .. 2 <sup>32</sup> -1) |                       |
+
+### 9.3.1.5 ng-eNB-DU UE W1AP ID
+
+The ng-eNB-DU UE W1AP ID uniquely identifies the UE association over the W1 interface within the ng-eNB-DU.
+
+| IE/Group Name        | Presence | Range | IE type and reference             | Semantics description |
+|----------------------|----------|-------|-----------------------------------|-----------------------|
+| ng-eNB-DU UE W1AP ID | M        |       | INTEGER (0 .. 2 <sup>32</sup> -1) |                       |
+
+### 9.3.1.6 RRC-Container
+
+This information element contains a ng-eNB-CU→UE or a UE → ng-eNB-CU message that is transferred without interpretation in the ng-eNB-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RRC-Container | M        |       | OCTET STRING          |                       |
+
+### 9.3.1.7 SRB ID
+
+This IE uniquely identifies a SRB for a UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                            |
+|---------------|----------|-------|-----------------------|------------------------------------------------------------------|
+| SRB ID        | M        |       | INTEGER (0..3, ...)   | Corresponds to the <i>SRB-Identity</i> defined in TS 36.331 [2]. |
+
+### 9.3.1.8 DRB ID
+
+This IE uniquely identifies a DRB for a UE.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                           |
+|---------------|----------|-------|-----------------------|-----------------------------------------------------------------|
+| DRB ID        | M        |       | INTEGER (1..32, ...)  | Corresponds to the <i>DRB-Identity</i> defined in TS 36.331[2]. |
+
+### 9.3.1.9 ng-eNB-DU ID
+
+The ng-eNB-DU ID uniquely identifies the ng-eNB-DU at least within an ng-eNB-CU.
+
+| IE/Group Name | Presence | Range | IE type and reference             | Semantics description                                                                                                             |
+|---------------|----------|-------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| ng-eNB-DU ID  | M        |       | INTEGER (0 .. 2 <sup>36</sup> -1) | The ng-eNB-DU ID is independently configured from cell identifiers, i.e. no connection between ng-eNB-DU ID and cell identifiers. |
+
+### 9.3.1.10 Served Cell Information
+
+This IE contains cell configuration information of a cell in the ng-eNB-DU.
+
+| IE/Group Name                    | Presence | Range               | IE type and reference           | Semantics description                                                                           | Criticality | Assigned Criticality |
+|----------------------------------|----------|---------------------|---------------------------------|-------------------------------------------------------------------------------------------------|-------------|----------------------|
+| E-UTRAN CGI                      | M        |                     | 9.3.1.12                        |                                                                                                 | -           |                      |
+| E-UTRAN PCI                      | M        |                     | INTEGER (0..503)                | Physical Cell ID                                                                                | -           |                      |
+| 5GS TAC                          | O        |                     | 9.3.1.26                        | 5GS Tracking Area Code                                                                          | -           |                      |
+| <b>Served PLMNs</b>              |          | 1..<maxno ofBPLMNs> |                                 | Broadcast PLMNs in SIB1 associated to the E-UTRAN cell Identity in the E-UTRAN CGI IE.          | -           |                      |
+| >PLMN Identity                   | M        |                     | 9.3.1.14                        |                                                                                                 | -           |                      |
+| >TAI Slice Support List          | O        |                     | Slice Support List 9.3.1.31     | Supported S-NSSAIs per TA.                                                                      | YES         | ignore               |
+| CHOICE E-UTRAN-Mode-Info         | M        |                     |                                 |                                                                                                 | -           |                      |
+| >FDD                             |          |                     |                                 |                                                                                                 | -           |                      |
+| >>FDD Info                       |          | 1                   |                                 |                                                                                                 | -           |                      |
+| >>>UL FreqInfo                   | M        |                     | E-UTRAN Frequency Info 9.3.1.17 |                                                                                                 | -           |                      |
+| >>>DL FreqInfo                   | M        |                     | E-UTRAN Frequency Info 9.3.1.17 |                                                                                                 | -           |                      |
+| >>>UL Transmission Bandwidth     | M        |                     | Transmission Bandwidth 9.3.1.15 |                                                                                                 | -           |                      |
+| >>>DL Transmission Bandwidth     | M        |                     | Transmission Bandwidth 9.3.1.15 |                                                                                                 | -           |                      |
+| >TDD                             |          |                     |                                 |                                                                                                 | -           |                      |
+| >>TDD Info                       |          | 1                   |                                 |                                                                                                 | -           |                      |
+| >>> E-UTRAN FreqInfo             | M        |                     | E-UTRAN Frequency Info 9.3.1.17 |                                                                                                 | -           |                      |
+| >>> Transmission Bandwidth       | M        |                     | Transmission Bandwidth 9.3.1.15 |                                                                                                 | -           |                      |
+| Measurement Timing Configuration | M        |                     | OCTET STRING                    | Contains the <i>MeasurementTimingConfiguration</i> inter-node message defined in TS 36.331 [2]. | -           |                      |
+| RANAC                            | O        |                     | RAN Area Code 9.3.1.45          |                                                                                                 | YES         | ignore               |
+| Cell Type                        | O        |                     | 9.3.1.62                        |                                                                                                 | YES         | ignore               |
+
+|                                          |   |                                  |                              |                                                                                                                                                                                                                                                                                                    |     |        |
+|------------------------------------------|---|----------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--------|
+| <b>Broadcast PLMN Identity Info List</b> |   | <i>0..&lt;maxno ofBPLMNs&gt;</i> |                              | This IE corresponds to the <i>cellAccessRelatedInfoList-5GC</i> IE in <i>SIB1</i> as specified in TS 36.331 [2]. All PLMN Identities and associated information contained in the <i>cellAccessRelatedInfoList-5GC</i> IE are included and provided in the same order as broadcast in <i>SIB1</i> . | YES | ignore |
+| >PLMN Identity List                      | M |                                  | Available PLMN List 9.3.1.47 | Broadcast PLMN IDs in <i>SIB1</i> associated to the <i>E-UTRAN Cell Identity</i> IE.                                                                                                                                                                                                               | -   |        |
+| >5GS-TAC                                 | O |                                  | OCTET STRING (3)             |                                                                                                                                                                                                                                                                                                    | -   |        |
+| >E-UTRAN Cell Identity                   | M |                                  | BIT STRING (28)              |                                                                                                                                                                                                                                                                                                    | -   |        |
+| >RANAC                                   | O |                                  | RAN Area Code 9.3.1.45       |                                                                                                                                                                                                                                                                                                    | -   |        |
+
+| Range bound   | Explanation                                    |
+|---------------|------------------------------------------------|
+| maxnoofBPLMNs | Maximum no. of Broadcast PLMN Ids. Value is 6. |
+
+### 9.3.1.11 Transmission Action Indicator
+
+This IE indicates actions for the ng-eNB-DU for the data transmission to the UE.
+
+| IE/Group Name                 | Presence | Range | IE type and reference           | Semantics description |
+|-------------------------------|----------|-------|---------------------------------|-----------------------|
+| Transmission Action Indicator | M        |       | ENUMERATED (stop, ..., restart) |                       |
+
+### 9.3.1.12 E-UTRAN CGI
+
+This information element is used to globally identify a cell (see TS 36.401 [3]).
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                            |
+|---------------|----------|-------|-----------------------|------------------------------------------------------------------|
+| PLMN Identity | M        |       | 9.3.1.14              |                                                                  |
+| Cell Identity | M        |       | BIT STRING (SIZE(28)) | The leftmost bits of the Cell Identity correspond to the eNB ID. |
+
+### 9.3.1.13 Repetition Period
+
+This IE indicates the periodicity of the warning message to be broadcast.
+
+| IE/Group Name     | Presence | Range | IE type and reference           | Semantics description                                  |
+|-------------------|----------|-------|---------------------------------|--------------------------------------------------------|
+| Repetition Period | M        |       | INTEGER (0..2 <sup>17</sup> -1) | The unit of value 1 to 2 <sup>17</sup> -1 is [second]. |
+
+### 9.3.1.14 PLMN Identity
+
+This information element indicates the PLMN Identity.
+
+| IE/Group Name | Presence | Range | IE type and reference  | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|---------------|----------|-------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| PLMN Identity | M        |       | OCTET STRING (SIZE(3)) | <ul style="list-style-type: none"> <li>- digits 0 to 9, encoded 0000 to 1001,</li> <li>- 1111 used as filler digit,</li> <li>two digits per octet,</li> <li>- bits 4 to 1 of octet n encoding digit 2n-1</li> <li>- bits 8 to 5 of octet n encoding digit 2n</li> </ul><br><ul style="list-style-type: none"> <li>-The PLMN identity consists of 3 digits from MCC followed by either</li> <li>-a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or</li> <li>-3 digits from MNC (in case of a 3 digit MNC).</li> </ul> |
+
+### 9.3.1.15 Transmission Bandwidth
+
+The *Transmission Bandwidth* IE is used to indicate the UL or DL transmission bandwidth.
+
+| IE/Group Name | Presence | Range | IE Type and Reference                                      | Semantics Description                                                                                                                                                                                                                              |
+|---------------|----------|-------|------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| NRB           | M        |       | ENUMERATED (mbw6, mbw15, mbw25, mbw50, mbw75, mbw100, ...) | This IE is used to indicate the UL or DL transmission bandwidth expressed in units of resource blocks "N <sub>RB</sub> " (TS 36.104 [14]). The values mbw6, mbw15, etc. correspond to the number of resource blocks "N <sub>RB</sub> " 6, 15, etc. |
+
+### 9.3.1.16 Void
+
+Reserved for future use.
+
+### 9.3.1.17 E-UTRAN Frequency Info
+
+The E-UTRAN Frequency Info defines the carrier frequency used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD.
+
+| IE/Group Name              | Presence | Range                         | IE Type and Reference        | Semantics Description                                |
+|----------------------------|----------|-------------------------------|------------------------------|------------------------------------------------------|
+| E-UTRAN ARFCN              | M        |                               | INTEGER (0..maxE-UTRANARFCN) | RF Reference Frequency as defined in TS 36.104 [14]. |
+| <b>Frequency Band List</b> |          | 1                             |                              |                                                      |
+| >Frequency Band Item       |          | 1..<maxnoofE-UTRAN CellBands> |                              |                                                      |
+| >>E-UTRAN Frequency Band   | M        |                               | INTEGER (1..maxBandsEUTRA)   | Operating Band as defined in TS 36.104 [14].         |
+
+| Range bound             | Explanation                                                               |
+|-------------------------|---------------------------------------------------------------------------|
+| maxE-UTRANARFCN         | Maximum value of E-UTRAN ARFCNs. Value is 262143.                         |
+| maxnoofE-UTRANCellBands | Maximum no. of frequency bands supported for an E-UTRAN cell. Value is 8. |
+| maxBandsEUTRA           | Maximum value of E-UTRAN Bands. Value is 256.                             |
+
+### 9.3.1.18 ng-eNB-DU System Information
+
+This IE contains the system information generated by the ng-eNB-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                       |
+|---------------|----------|-------|-----------------------|---------------------------------------------|
+| MIB message   | M        |       | OCTET STRING          | MIB message, as defined in TS 36.331 [2].   |
+| SIB1 message  | M        |       | OCTET STRING          | SIB1 message, as defined in TS 36.331 [2].  |
+| SIB2 message  | M        |       | OCTET STRING          | SIB2 message, as defined in TS 36.331 [2].  |
+| SIB3 message  | M        |       | OCTET STRING          | SIB3 message, as defined in TS 36.331 [2].  |
+| SIB8 message  | M        |       | OCTET STRING          | SIB8 message, as defined in TS 36.331 [2].  |
+| SIB16 message | M        |       | OCTET STRING          | SIB16 message, as defined in TS 36.331 [2]. |
+
+### 9.3.1.19 E-UTRAN QoS
+
+This IE defines the QoS to be applied to a DRB for DC case.
+
+| IE/Group Name                     | Presence | Range | IE type and reference | Semantics description                                                                                    |
+|-----------------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------------|
+| QCI                               | M        |       | INTEGER (0..255)      | QoS Class Identifier defined in TS 23.401 [10].<br>Logical range and coding specified in TS 23.203 [20]. |
+| Allocation and Retention Priority | M        |       | 9.3.1.20              |                                                                                                          |
+| GBR QoS Information               | O        |       | 9.3.1.21              | This IE applies to GBR bearers only and shall be ignored otherwise.                                      |
+
+### 9.3.1.20 Allocation and Retention Priority
+
+This IE specifies the relative importance compared to other E-RABs for allocation and retention of the E-UTRAN Radio Access Bearer.
+
+| IE/Group Name             | Presence | Range | IE type and reference                                              | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                         |
+|---------------------------|----------|-------|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Priority Level            | M        |       | INTEGER (0..15)                                                    | <p><b>Desc.:</b> This IE should be understood as "priority of allocation and retention" (see TS 23.401 [10]).</p> <p><b>Usage:</b><br/>Value 15 means "no priority".<br/>Values between 1 and 14 are ordered in decreasing order of priority, i.e. 1 is the highest and 14 the lowest.<br/>Value 0 shall be treated as a logical error if received.</p>                                                                                       |
+| Pre-emption Capability    | M        |       | ENUMERATED(shall not trigger pre-emption, may trigger pre-emption) | <p><b>Desc.:</b> This IE indicates the pre-emption capability of the request on other E-RABs</p> <p><b>Usage:</b><br/>The E-RAB shall not pre-empt other E-RABs or, the E-RAB may pre-empt other E-RABs<br/>The Pre-emption Capability indicator applies to the allocation of resources for an E-RAB and as such it provides the trigger to the pre-emption procedures/processes of the eNB.</p>                                              |
+| Pre-emption Vulnerability | M        |       | ENUMERATED(not pre-emptable, pre-emptable)                         | <p><b>Desc.:</b> This IE indicates the vulnerability of the E-RAB to pre-emption of other E-RABs.</p> <p><b>Usage:</b><br/>The E-RAB shall not be pre-empted by other E-RABs or the E-RAB may be pre-empted by other RABs.<br/>Pre-emption Vulnerability indicator applies for the entire duration of the E-RAB, unless modified, and as such indicates whether the E-RAB is a target of the pre-emption procedures/processes of the eNB.</p> |
+
+### 9.3.1.21 GBR QoS Information
+
+This IE indicates the maximum and guaranteed bit rates of a GBR E-RAB for downlink and uplink.
+
+| IE/Group Name                      | Presence | Range | IE type and reference | Semantics description                                                                                                                    |
+|------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| E-RAB Maximum Bit Rate Downlink    | M        |       | Bit Rate 9.3.1.22     | Maximum Bit Rate in DL (i.e. from EPC to E-UTRAN) for the bearer. Details in TS 23.401 [10].                                             |
+| E-RAB Maximum Bit Rate Uplink      | M        |       | Bit Rate 9.3.1.22     | Maximum Bit Rate in UL (i.e. from E-UTRAN to EPC) for the bearer. Details in TS 23.401 [10].                                             |
+| E-RAB Guaranteed Bit Rate Downlink | M        |       | Bit Rate 9.3.1.22     | Guaranteed Bit Rate (provided that there is data to deliver) in DL (i.e. from EPC to E-UTRAN) for the bearer. Details in TS 23.401 [10]. |
+| E-RAB Guaranteed Bit Rate Uplink   | M        |       | Bit Rate 9.3.1.22     | Guaranteed Bit Rate (provided that there is data to deliver) in UL (i.e. from E-UTRAN to EPC) for the bearer. Details in TS 23.401 [10]. |
+
+### 9.3.1.22 Bit Rate
+
+This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a GBR QoS flow, or an aggregated maximum bit rate.
+
+| IE/Group Name | Presence | Range | IE type and reference                  | Semantics description |
+|---------------|----------|-------|----------------------------------------|-----------------------|
+| Bit Rate      | M        |       | INTEGER (0..<br>4,000,000,000,000,...) | The unit is: bit/s    |
+
+### 9.3.1.23 Transaction ID
+
+The *Transaction ID* IE uniquely identifies a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer. Messages belonging to the same procedure shall use the same Transaction ID. The Transaction ID is determined by the initiating peer of a procedure.
+
+| IE/Group Name  | Presence | Range | IE type and reference | Semantics description |
+|----------------|----------|-------|-----------------------|-----------------------|
+| Transaction ID | M        |       | INTEGER (0..255, ...) |                       |
+
+### 9.3.1.24 DRX Cycle
+
+The *DRX Cycle* IE is to indicate the desired DRX cycle.
+
+| IE/Group Name          | Presence | Range | IE Type and Reference                                                                                                          | Semantics Description               |
+|------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|
+| Long DRX Cycle Length  | M        |       | ENUMERATED (sf10, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320, sf512, sf640, sf1024, sf1280, sf2048, sf2560, ...) | This IE is defined in TS 36.331 [2] |
+| Short DRX Cycle Length | O        |       | ENUMERATED (sf2, sf5, sf8, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf256, sf320, sf512, sf640, ...)            | This IE is defined in TS 36.331 [2] |
+| Short DRX Cycle Timer  | O        |       | INTEGER (1..16)                                                                                                                | This IE is defined in TS 36.331 [2] |
+
+### 9.3.1.25 RLC Mode
+
+The *RLC Mode* IE indicates the RLC Mode used for a DRB.
+
+| IE/Group Name | Presence | Range | IE Type and Reference                                                                               | Semantics Description |
+|---------------|----------|-------|-----------------------------------------------------------------------------------------------------|-----------------------|
+| RLC Mode      |          |       | ENUMERATED ( RLC-AM, RLC-UM-Bidirectional, RLC-UM-Unidirectional-UL, RLC-UM-Unidirectional-DL, ...) |                       |
+
+### 9.3.1.26 5GS TAC
+
+This information element is used to identify Tracking Area Code.
+
+| IE/Group Name | Presence | Range | IE type and reference   | Semantics description |
+|---------------|----------|-------|-------------------------|-----------------------|
+| 5GS TAC       | M        |       | OCTET STRING (SIZE (3)) |                       |
+
+### 9.3.1.27 Void
+
+### 9.3.1.28 RRC Reconfiguration Complete Indicator
+
+This IE indicates the result of the reconfiguration performed towards the UE.
+
+| IE/Group Name                          | Presence | Range | IE type and reference           | Semantics description |
+|----------------------------------------|----------|-------|---------------------------------|-----------------------|
+| RRC Reconfiguration Complete Indicator | M        |       | ENUMERATED (true, ..., failure) |                       |
+
+### 9.3.1.29 C-RNTI
+
+This IE contains the C-RNTI information.
+
+| IE/Group Name | Presence | Range | IE type and reference   | Semantics description               |
+|---------------|----------|-------|-------------------------|-------------------------------------|
+| C-RNTI        | M        |       | INTEGER (0..65535, ...) | C-RNTI as defined in TS 36.331 [2]. |
+
+### 9.3.1.30 RAT-Frequency Priority Information
+
+The RAT-Frequency Priority Information contains either the *Subscriber Profile ID for RAT/Frequency priority* IE or the *Index to RAT/Frequency Selection Priority* IE. These parameters are used to define local configuration for RRM strategies.
+
+| IE/Group Name                                      | Presence | Range | IE type and reference | Semantics description                               |
+|----------------------------------------------------|----------|-------|-----------------------|-----------------------------------------------------|
+| CHOICE RAT-Frequency Priority Information          | M        |       |                       |                                                     |
+| >EN-DC                                             |          |       |                       |                                                     |
+| >>Subscriber Profile ID for RAT/Frequency priority | M        |       | INTEGER (1..256, ...) | This IE is not used in the version of this release. |
+| >NG-RAN                                            |          |       |                       |                                                     |
+| >>Index to RAT/Frequency Selection Priority        | M        |       | INTEGER (1..256, ...) |                                                     |
+
+### 9.3.1.31 Slice Support List
+
+This IE indicates the list of supported slices.
+
+| IE/Group Name          | Presence | Range                | IE type and reference | Semantics description |
+|------------------------|----------|----------------------|-----------------------|-----------------------|
+| Slice Support Item IEs |          | 1..<maxnooSlicItems> |                       |                       |
+| >S-NSSAI               | M        |                      | 9.3.1.32              |                       |
+
+| Range bound     | Explanation                                                  |
+|-----------------|--------------------------------------------------------------|
+| maxnooSlicItems | Maximum no. of signalled slice support items. Value is 1024. |
+
+### 9.3.1.32 S-NSSAI
+
+This IE indicates the S-NSSAI.
+
+| IE/Group Name | Presence | Range | IE type and reference  | Semantics description |
+|---------------|----------|-------|------------------------|-----------------------|
+| SST           | M        |       | OCTET STRING (SIZE(1)) |                       |
+| SD            | O        |       | OCTET STRING (SIZE(3)) |                       |
+
+### 9.3.1.33 ng-eNB-CU System Information
+
+This IE contains the system information encoded by the ng-eNB-CU.
+
+| IE/Group Name                            | Presence | Range                     | IE type and reference   | Semantics description                                                                                                                                     |
+|------------------------------------------|----------|---------------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>SIB type to Be Updated List</b>       |          | 1                         |                         |                                                                                                                                                           |
+| > <b>SIB type to Be Updated Item IEs</b> |          | 1...<br><maxnoofSIBTypes> |                         |                                                                                                                                                           |
+| >>SIB type                               | M        |                           | INTEGER<br>(2..32, ...) | Indicates a certain SIB block, e.g. 2 means sibType2, 3 for sibType3, etc. Values 2, 3, 8 and 16 are not applicable in this version of the specification. |
+| >>SIB message                            | M        |                           | OCTET STRING            | SIB message containing SIB as defined in TS 36.331 [2].                                                                                                   |
+| >>Value Tag                              | M        |                           | INTEGER<br>(0..31, ...) |                                                                                                                                                           |
+
+### 9.3.1.34 QoS Flow Level QoS Parameters
+
+This IE defines the QoS to be applied to a QoS flow or to a DRB.
+
+| IE/Group Name                                    | Presence | Range | IE type and reference              | Semantics description                                                                                                      | Criticality | Assigned Criticality |
+|--------------------------------------------------|----------|-------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| <b>CHOICE QoS Characteristics</b>                | M        |       |                                    |                                                                                                                            | -           |                      |
+| > <i>Non-dynamic 5QI</i>                         |          |       |                                    |                                                                                                                            | -           |                      |
+| >>Non Dynamic 5QI Descriptor                     | M        |       | 9.3.1.38                           |                                                                                                                            | -           |                      |
+| > <i>Dynamic 5QI</i>                             |          |       |                                    |                                                                                                                            | -           |                      |
+| >>Dynamic 5QI Descriptor                         | M        |       | 9.3.1.36                           |                                                                                                                            | -           |                      |
+| NG-RAN Allocation and Retention Priority         | M        |       | 9.3.1.37                           |                                                                                                                            | -           |                      |
+| GBR QoS Flow Information                         | O        |       | 9.3.1.35                           | This IE shall be present for GBR QoS Flows only.                                                                           | -           |                      |
+| Reflective QoS Attribute                         | O        |       | ENUMERATED<br>(subject to, ...)    | Details in TS 23.501 [8]. This IE applies to non-GBR flows only and shall be ignored otherwise.                            | -           |                      |
+| PDU Session ID                                   | O        |       | INTEGER<br>(0..255)                | As specified in TS 23.501 [8].                                                                                             | YES         | ignore               |
+| UL PDU Session Aggregate Maximum Bit Rate        | O        |       | Bit Rate<br>9.3.1.22               | The PDU session Aggregate Maximum Bit Rate Uplink which is associated with the involved PDU session.                       | YES         | ignore               |
+| PDCP Terminating Node DL Transport Layer Address | O        |       | Transport Layer Address<br>9.3.2.3 | DL Transport Layer Address of node terminating PDCP. Included for MN-terminated SCG bearers and SN-terminated MCG bearers. | -           |                      |
+
+### 9.3.1.35 GBR QoS Flow Information
+
+This IE indicates QoS parameters for a GBR QoS flow or GBR bearer for downlink and uplink.
+
+| IE/Group Name                     | Presence | Range | IE type and reference                | Semantics description                                                                                                  |
+|-----------------------------------|----------|-------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------|
+| Maximum Flow Bit Rate Downlink    | M        |       | Bit Rate<br>9.3.1.22                 | Maximum Bit Rate in DL. Details in TS 23.501 [8].                                                                      |
+| Maximum Flow Bit Rate Uplink      | M        |       | Bit Rate<br>9.3.1.22                 | Maximum Bit Rate in UL. Details in TS 23.501 [8].                                                                      |
+| Guaranteed Flow Bit Rate Downlink | M        |       | Bit Rate<br>9.3.1.22                 | Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [8].                               |
+| Guaranteed Flow Bit Rate Uplink   | M        |       | Bit Rate<br>9.3.1.22                 | Guaranteed Bit Rate (provided there is data to deliver). Details in TS 23.501 [8].                                     |
+| Maximum Packet Loss Rate Downlink | O        |       | Maximum Packet Loss Rate<br>9.3.1.39 | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [8]. |
+| Maximum Packet Loss Rate Uplink   | O        |       | Maximum Packet Loss Rate<br>9.3.1.39 | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [8].   |
+
+### 9.3.1.36 Dynamic 5QI Descriptor
+
+This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink.
+
+| IE/Group Name             | Presence    | Range | IE type and reference                           | Semantics description                                                                                                                               |
+|---------------------------|-------------|-------|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
+| QoS Priority Level        | M           |       | INTEGER (1..127)                                | For details see TS 23.501 [8].                                                                                                                      |
+| Packet Delay Budget       | M           |       | 9.3.1.40                                        | For details see TS 23.501 [8].                                                                                                                      |
+| Packet Error Rate         | M           |       | 9.3.1.41                                        | For details see TS 23.501 [8].                                                                                                                      |
+| 5QI                       | O           |       | INTEGER (0..255,...)                            | This IE contains the dynamically assigned 5QI as specified in TS 23.501 [8].                                                                        |
+| Delay Critical            | C-ifGBRflow |       | ENUMERATED (delay critical, non-delay critical) | For details see TS 23.501 [8].                                                                                                                      |
+| Averaging Window          | C-ifGBRflow |       | 9.3.1.42                                        | For details see TS 23.501 [8].                                                                                                                      |
+| Maximum Data Burst Volume | O           |       | 9.3.1.43                                        | For details see TS 23.501 [8]. This IE shall be included if the <i>Delay Critical</i> IE is set to "delay critical" and shall be ignored otherwise. |
+
+| Condition | Explanation                                                                                                                   |
+|-----------|-------------------------------------------------------------------------------------------------------------------------------|
+| ifGBRflow | This IE shall be present if the <i>GBR QoS Flow Information</i> IE is present in the <i>QoS Flow Level QoS Parameters</i> IE. |
+
+### 9.3.1.37 NG-RAN Allocation and Retention Priority
+
+This IE specifies the relative importance of a QoS flow or a DRB compared to other QoS flows or DRBs for allocation and retention of NG-RAN resources.
+
+| IE/Group Name             | Presence | Range | IE type and reference                                               | Semantics description                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|---------------------------|----------|-------|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Priority Level            | M        |       | INTEGER (0..15)                                                     | <p><b>Desc.:</b> This IE defines the relative importance of a resource request (see TS 23.501 [8]).</p> <p><b>Usage:</b> Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority. Further usage is defined in TS 23.501 [8].</p>                                                                                                                                                                            |
+| Pre-emption Capability    | M        |       | ENUMERATED (shall not trigger pre-emption, may trigger pre-emption) | <p><b>Desc.:</b> This IE indicates the pre-emption capability of the request on other QoS flows.</p> <p><b>Usage:</b> The QoS flow shall not pre-empt other QoS flows or, the QoS flow may pre-empt other QoS flows. The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the NG-RAN node.</p>                                                        |
+| Pre-emption Vulnerability | M        |       | ENUMERATED (not pre-emptable, pre-emptable)                         | <p><b>Desc.:</b> This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows.</p> <p><b>Usage:</b> The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows. The Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the NG-RAN node.</p> |
+
+### 9.3.1.38 Non Dynamic 5QI Descriptor
+
+This IE indicates the QoS Characteristics for a standardized or pre-configured 5QI for downlink and uplink.
+
+| IE/Group Name             | Presence | Range | IE type and reference | Semantics description                                                                                                                                                    |
+|---------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5QI                       | M        |       | INTEGER (0..255,...)  | This IE contains the standardized or pre-configured 5QI as specified in TS 23.501 [8]                                                                                    |
+| Priority Level            | O        |       | INTEGER (1..127)      | For details see TS 23.501 [8]. When included overrides standardized or pre-configured value.                                                                             |
+| Averaging Window          | O        |       | 9.3.1.42              | This IE applies to GBR QoS Flows only. For details see TS 23.501 [8]. When included overrides standardized or pre-configured value.                                      |
+| Maximum Data Burst Volume | O        |       | 9.3.1.43              | For details see TS 23.501 [8]. When included overrides standardized or pre-configured value. If the 5QI refers to a non-delay critical QoS flow the IE shall be ignored. |
+
+### 9.3.1.39 Maximum Packet Loss Rate
+
+This IE indicates the Maximum Packet Loss Rate.
+
+| IE/Group Name            | Presence | Range | IE type and reference | Semantics description                                                            |
+|--------------------------|----------|-------|-----------------------|----------------------------------------------------------------------------------|
+| Maximum Packet Loss Rate | M        |       | INTEGER(0..1000)      | Ratio of lost packets per number of packets sent, expressed in tenth of percent. |
+
+### 9.3.1.40 Packet Delay Budget
+
+This IE indicates the Packet Delay Budget for a QoS flow.
+
+| IE/Group Name       | Presence | Range | IE type and reference  | Semantics description                                                                    |
+|---------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------|
+| Packet Delay Budget | M        |       | INTEGER (0..1023, ...) | Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. |
+
+### 9.3.1.41 Packet Error Rate
+
+This IE indicates the Packet Error Rate for a QoS flow.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                                                    |
+|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------|
+| Scalar        | M        |       | INTEGER (0..9, ...)   | The packet error rate is expressed as Scalar x 10 <sup>-k</sup> where k is the Exponent. |
+| Exponent      | M        |       | INTEGER (0..9, ...)   |                                                                                          |
+
+### 9.3.1.42 Averaging Window
+
+This IE indicates the Averaging Window for a QoS flow.
+
+| IE/Group Name    | Presence | Range | IE type and reference  | Semantics description                  |
+|------------------|----------|-------|------------------------|----------------------------------------|
+| Averaging Window | M        |       | INTEGER (0..4095, ...) | Unit: ms. The default value is 2000ms. |
+
+### 9.3.1.43 Maximum Data Burst Volume
+
+This IE indicates the Maximum Data Burst Volume for a QoS flow.
+
+| IE/Group Name             | Presence | Range | IE type and reference  | Semantics description |
+|---------------------------|----------|-------|------------------------|-----------------------|
+| Maximum Data Burst Volume | M        |       | INTEGER (0..4095, ...) | Unit: byte.           |
+
+### 9.3.1.44 Notification Control
+
+The *Notification Control* IE indicates whether the notification control for a given DRB is active or not-active. If the notification control is set to active, the ng-eNB-DU shall, if supported, monitor the QoS of the DRB and notify the ng-eNB-CU.
+
+| IE/Group Name        | Presence | Range | IE Type and Reference               | Semantics Description |
+|----------------------|----------|-------|-------------------------------------|-----------------------|
+| Notification Control | M        |       | ENUMERATED(Active, Not-Active, ...) |                       |
+
+### 9.3.1.45 RAN Area Code
+
+This information element is used to uniquely identify a RAN Area Code.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| RANAC         | M        |       | INTEGER (0..255)      | RAN Area Code         |
+
+### 9.3.1.46 QoS Flow Identifier
+
+This IE identifies a QoS Flow within a PDU Session. The definition and use of the QoS Flow Identifiers specified in TS 23.501 [8].
+
+| IE/Group Name       | Presence | Range | IE type and reference | Semantics description |
+|---------------------|----------|-------|-----------------------|-----------------------|
+| QoS Flow Identifier | M        |       | INTEGER (0 ..63)      |                       |
+
+### 9.3.1.47 Available PLMN List
+
+This IE indicates the list of available PLMN.
+
+| IE/Group Name           | Presence | Range              | IE type and reference | Semantics description |
+|-------------------------|----------|--------------------|-----------------------|-----------------------|
+| Available PLMN Item IEs |          | 1..<maxnoofBPLMNs> |                       |                       |
+| >PLMN Identity          | M        |                    | 9.3.1.14              |                       |
+
+| Range bound   | Explanation                                    |
+|---------------|------------------------------------------------|
+| maxnoofBPLMNs | Maximum no. of Broadcast PLMN Ids. Value is 6. |
+
+### 9.3.1.48 Service Status
+
+This IE is used to indicate the service status of a cell by the ng-eNB-DU.
+
+| IE/Group Name         | Presence | Range | IE type and reference                        | Semantics description                                                                                                                                                                                                   |
+|-----------------------|----------|-------|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service State         | M        |       | ENUMERATED (In-Service, Out-Of-Service, ...) | Indicates the Service State of the cell. In-Service and Out-of-Service Service States are defined in TS 38.401 [4].                                                                                                     |
+| Switching Off Ongoing | O        |       | ENUMERATED (True, ...)                       | This IE indicates that the ng-eNB-DU will delete the cell after some time using a new ng-eNB-DU Configuration Update procedure. When this IE is set to "True" the <i>Service State</i> IE shall be set to "In-Service". |
+
+### 9.3.1.49 RLC Status
+
+This IE indicates about the RLC configuration change included in the container towards the UE.
+
+| IE/Group Name              | Presence | Range | IE type and reference           | Semantics description                                                                   |
+|----------------------------|----------|-------|---------------------------------|-----------------------------------------------------------------------------------------|
+| Reestablishment Indication | O        |       | ENUMERATED (reestablished, ...) | Indicates that following a change in the radio status, the RLC has been re-established. |
+
+### 9.3.1.50 Void
+
+### 9.3.1.51 QoS Flow Mapping Indication
+
+This IE is used to indicate only the uplink or downlink QoS flow is mapped to the DRB.
+
+| IE/Group Name               | Presence | Range | IE type and reference  | Semantics description                                                    |
+|-----------------------------|----------|-------|------------------------|--------------------------------------------------------------------------|
+| QoS Flow Mapping Indication | O        |       | ENUMERATED(ul, dl,...) | Indicates that only the uplink or downlink QoS flow is mapped to the DRB |
+
+### 9.3.1.52 Resource Coordination Transfer Information
+
+This IE contains information for UE-associated E-UTRA – NR resource coordination.
+
+| IE/Group Name                                 | Presence | Range | IE type and reference | Semantics description                                                  |
+|-----------------------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------|
+| MeNB Cell ID                                  | M        |       | BIT STRING (SIZE(28)) | E-UTRAN Cell Global Identifier defined in TS 36.423 [12] clause 9.2.14 |
+| Resource Coordination E-UTRA Cell Information | O        |       | 9.3.1.54              |                                                                        |
+
+### 9.3.1.53 E-UTRA PRACH Configuration
+
+This IE indicates the PRACH resources used in E-UTRA cell.
+
+| IE/Group Name                    | Presence | Range | IE type and reference | Semantics description                                                                                |
+|----------------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------|
+| RootSequenceIndex                | M        |       | INTEGER<br>(0..837)   | See clause 5.7.2. in TS 36.211 [13]                                                                  |
+| ZeroCorrelationZoneConfiguration | M        |       | INTEGER<br>(0..15)    | See clause 5.7.2. in TS 36.211 [13]                                                                  |
+| HighSpeedFlag                    | M        |       | BOOLEAN               | TRUE corresponds to Restricted set and FALSE to Unrestricted set. See clause 5.7.2 in TS 36.211 [13] |
+| PRACH-FrequencyOffset            | M        |       | INTEGER<br>(0..94)    | See clause 5.7.1 of TS 36.211 [13]                                                                   |
+| PRACH-ConfigurationIndex         | O        |       | INTEGER<br>(0..63)    | Mandatory for TDD, shall not be present for FDD.<br>See clause 5.7.1. in TS 36.211 [13]              |
+
+### 9.3.1.54 Resource Coordination E-UTRA Cell Information
+
+This IE contains E-UTRA cell information for UE-associated E-UTRA – NR resource coordination.
+
+| IE/Group Name                 | Presence | Range | IE type and reference                                                              | Semantics description                                                                                                    | Criticality | Assigned Criticality |
+|-------------------------------|----------|-------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| CHOICE <i>EUTRA-Mode-Info</i> | M        |       |                                                                                    |                                                                                                                          | -           |                      |
+| >FDD                          |          |       |                                                                                    |                                                                                                                          | -           |                      |
+| >>FDD Info                    |          | 1     |                                                                                    |                                                                                                                          | -           |                      |
+| >>>UL EARFCN                  | O        |       | INTEGER (0 .. maxExtendedEARFCN, ...)                                              | The relation between EARFCN and carrier frequency (in MHz) is defined in TS 36.104 [14].                                 | -           |                      |
+| >>>DL EARFCN                  | M        |       | INTEGER (0 .. maxExtendedEARFCN, ...)                                              | The relation between EARFCN and carrier frequency (in MHz) is defined in TS 36.104 [14].                                 | -           |                      |
+| >>>UL Transmission Bandwidth  | O        |       | E-UTRA Transmission Bandwidth 9.3.1.59                                             | Present if <i>UL EARFCN</i> IE is present.                                                                               | -           |                      |
+| >>>DL Transmission Bandwidth  | M        |       | E-UTRA Transmission Bandwidth 9.3.1.59                                             |                                                                                                                          | -           |                      |
+| >TDD                          |          |       |                                                                                    |                                                                                                                          | -           |                      |
+| >>TDD Info                    |          | 1     |                                                                                    |                                                                                                                          | -           |                      |
+| >>>EARFCN                     | M        |       | INTEGER (0 .. maxExtendedEARFCN, ...)                                              | The relation between EARFCN and carrier frequency (in MHz) is defined in TS 36.104 [14].                                 | -           |                      |
+| >>>Transmission Bandwidth     | M        |       | E-UTRA Transmission Bandwidth 9.3.1.59                                             |                                                                                                                          | -           |                      |
+| >>>Subframe Assignment        | M        |       | ENUMERATED(sa0, sa1, sa2, sa3, sa4, sa5, sa6,...)                                  | Uplink-downlink subframe configuration information defined in TS 36.211 [13]. In NB-IOT, sa0 and sa6 are not applicable. | -           |                      |
+| >>>Special Subframe Info      |          | 1     |                                                                                    | Special subframe configuration information defined in TS 36.211 [13]                                                     | -           |                      |
+| >>>>Special Subframe Patterns | M        |       | ENUMERATED(ssp0, ssp1, ssp2, ssp3, ssp4, ssp5, ssp6, ssp7, ssp8, ssp9, ssp10, ...) |                                                                                                                          | -           |                      |
+| >>>>Cyclic Prefix DL          | M        |       | ENUMERATED(Normal, Extended,...)                                                   |                                                                                                                          | -           |                      |
+| >>>>Cyclic Prefix UL          | M        |       | ENUMERATED(Normal, Extended,...)                                                   |                                                                                                                          | -           |                      |
+
+|                            |   |  |                       |  |     |        |
+|----------------------------|---|--|-----------------------|--|-----|--------|
+| E-UTRA PRACH Configuration | M |  | 9.3.1.53              |  | -   |        |
+| Ignore PRACH Configuration | O |  | ENUMERATED (true,...) |  | YES | reject |
+
+| Range bound       | Explanation                                        |
+|-------------------|----------------------------------------------------|
+| maxExtendedEARFCN | Maximum value of extended EARFCN. Value is 262143. |
+
+### 9.3.1.55 Extended Available PLMN List
+
+This IE indicates the list of available PLMN.
+
+| IE/Group Name                           | Presence | Range                        | IE type and reference | Semantics description |
+|-----------------------------------------|----------|------------------------------|-----------------------|-----------------------|
+| <b>Extended Available PLMN Item IEs</b> |          | 1..< maxnoofExtendedBPLMNs > |                       |                       |
+| >PLMN Identity                          | M        |                              | 9.3.1.14              |                       |
+
+| Range bound           | Explanation                                             |
+|-----------------------|---------------------------------------------------------|
+| maxnoofExtendedBPLMNs | Maximum no. of Extended Broadcast PLMN Ids. Value is 6. |
+
+### 9.3.1.56 void
+
+### 9.3.1.57 CU to DU RRC Information
+
+This IE contains the RRC Information that are sent from ng-eNB-CU to ng-eNB-DU.
+
+| IE/Group Name                    | Presence | Range | IE type and reference | Semantics description                                                                                             | Criticality | Assigned Criticality |
+|----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| CG-ConfigInfo                    | O        |       | OCTET STRING          | CG-ConfigInfo, as defined in TS 38.331 [16].                                                                      | -           |                      |
+| UE-CapabilityRAT-ContainerList   | O        |       | OCTET STRING          | This IE is used in the NG-RAN and it consists of the UE-CapabilityRAT-ContainerList, as defined in TS 36.331 [2]. | -           |                      |
+| MeasConfig                       | O        |       | OCTET STRING          | MeasConfig, as defined in TS 38.331 [16] (without MeasGapConfig).                                                 | -           |                      |
+| Handover Preparation Information | O        |       | OCTET STRING          | HandoverPreparationInformation, as defined in TS 36.331 [2].                                                      | YES         | ignore               |
+| RadioResourceConfigDedicated     | O        |       | OCTET STRING          | RadioResourceConfigDedicated, as defined in TS 36.331 [2].                                                        | YES         | ignore               |
+| Measurement Timing Configuration | O        |       | OCTET STRING          | Contains the <i>MeasurementTimingConfiguration</i> inter-node message defined in TS 38.331 [16].                  | YES         | ignore               |
+| UEAssistanceInformation          | O        |       | OCTET STRING          | UEAssistanceInformation, as defined in TS 36.331 [2].                                                             | YES         | ignore               |
+| requestedP-MaxFR1                | O        |       | OCTET STRING          | requestedP-MaxFR1, as defined in TS 38.331 [16].                                                                  | YES         | ignore               |
+
+### 9.3.1.58 DU to CU RRC Information
+
+This IE contains the RRC Information that are sent from the ng-eNB-DU to the ng-eNB-CU.
+
+| IE/Group Name                  | Presence | Range | IE type and reference | Semantics description                                                                                                    | Criticality | Assigned Criticality |
+|--------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------|-------------|----------------------|
+| RadioResourceConfigDedicated   | M        |       | OCTET STRING          | RadioResourceConfigDedicated, as defined in TS 36.331 [2].                                                               |             |                      |
+| MeasGapConfig                  | O        |       | OCTET STRING          | MeasGapConfig as defined in TS 36.331 [2].                                                                               |             |                      |
+| Requested P-MaxFR1             | O        |       | OCTET STRING          | requestedP-MaxFR1, as defined in TS 36.331 [2].                                                                          |             |                      |
+| DRX Long Cycle Start Offset    | O        |       | INTEGER (0..10239)    | Identical to the value of the drx-LongCycleStartOffset IE within the DRX-Config as defined in TS 36.331 [2].             |             |                      |
+| Selected BandCombinationIndex  | O        |       | OCTET STRING          | BandCombinationIndex, as defined in TS 38.331 [16].                                                                      | YES         | ignore               |
+| Selected FeatureSetEntryIndex  | O        |       | OCTET STRING          | FeatureSetEntryIndex, as defined in TS 38.331 [16].                                                                      | YES         | ignore               |
+| Ph-InfoSCG                     | O        |       | OCTET STRING          | PH-TypeListSCG, as defined in TS 38.331[16].                                                                             | Yes         | ignore               |
+| Requested BandCombinationIndex | O        |       | OCTET STRING          | BandCombinationIndex, as defined in TS 38.331 [16]. This IE is used for the ng-eNB-DU to request a new Band Combination. | YES         | ignore               |
+| Requested FeatureSetEntryIndex | O        |       | OCTET STRING          | FeatureSetEntryIndex, as defined in TS 38.331 [16]. This IE is used for the ng-eNB-DU to request a new Feature Set.      | YES         | ignore               |
+| DRX Config                     | O        |       | OCTET STRING          | DRX-Config, as defined in TS 36.331 [2].                                                                                 | YES         | ignore               |
+| MeasGapSharingConfig           | O        |       | OCTET STRING          | MeasGapSharingConfig as defined in TS 38.331 [8].                                                                        | YES         | ignore               |
+
+### 9.3.1.59 E-UTRA Transmission Bandwidth
+
+This IE is used to indicate the E-UTRA UL or DL transmission bandwidth expressed in units of resource blocks "  $N_{RB}$  " (TS 36.104 [14]). The values bw1, bw6, bw15, bw25, bw50, bw75, bw100 correspond to the number of resource blocks " $N_{RB}$ " 1, 6, 15, 25, 50, 75, 100.
+
+| IE/Group Name                 | Presence | Range | IE Type and Reference                                     | Semantics Description |
+|-------------------------------|----------|-------|-----------------------------------------------------------|-----------------------|
+| E-UTRA Transmission Bandwidth | M        |       | ENUMERATED (bw1, bw6, bw15, bw25, bw50, bw75, bw100,... ) |                       |
+
+### 9.3.1.60 Number of Broadcasts Requested
+
+This IE indicates the number of times a message is to be broadcast.
+
+| IE/Group Name                  | Presence | Range | IE type and reference | Semantics description |
+|--------------------------------|----------|-------|-----------------------|-----------------------|
+| Number of Broadcasts Requested | M        |       | INTEGER (0..65535)    |                       |
+
+### 9.3.1.61 Criticality Diagnostics
+
+The *Criticality Diagnostics* IE is sent by the ng-eNB-DU or the ng-eNB-CU when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing.
+
+For further details on how to use the *Criticality Diagnostics* IE, (see clause 10). The conditions for inclusion of the *Transaction ID* IE are described in clause 10.
+
+| IE/Group Name                                      | Presence | Range                | IE type and reference                                                    | Semantics description                                                                                                                                                           |
+|----------------------------------------------------|----------|----------------------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Procedure Code                                     | O        |                      | INTEGER (0..255)                                                         | Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. |
+| Triggering Message                                 | O        |                      | ENUMERATED(initiating message, successful outcome, unsuccessful outcome) | The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure.                                                                       |
+| Procedure Criticality                              | O        |                      | ENUMERATED(reject, ignore, notify)                                       | This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure).                                                                         |
+| Transaction ID                                     | O        |                      | 9.3.1.23                                                                 |                                                                                                                                                                                 |
+| <b>Information Element Criticality Diagnostics</b> |          | 0 .. <maxnoofErrors> |                                                                          |                                                                                                                                                                                 |
+| >IE Criticality                                    | M        |                      | ENUMERATED(reject, ignore, notify)                                       | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' is not applicable.                                                            |
+| >IE ID                                             | M        |                      | INTEGER (0..65535)                                                       | The IE ID of the not understood or missing IE.                                                                                                                                  |
+| >Type of Error                                     | M        |                      | ENUMERATED(not understood, missing, ...)                                 |                                                                                                                                                                                 |
+
+| Range bound   | Explanation                                                                                                |
+|---------------|------------------------------------------------------------------------------------------------------------|
+| maxnoofErrors | Maximum no. of IE errors allowed to be reported with a single message. The value for maxnoofErrors is 256. |
+
+### 9.3.1.62 Cell Type
+
+This IE provides the cell coverage area.
+
+| IE/Group Name | Presence | Range | IE type and reference                            | Semantics description |
+|---------------|----------|-------|--------------------------------------------------|-----------------------|
+| Cell Size     | M        |       | ENUMERATED(verysmall, small, medium, large, ...) |                       |
+
+### 9.3.1.63 UE Identity Index value
+
+The *UE Identity Index value* IE is used by the eNB to calculate the Paging Frame TS 36.304 [20].
+
+| IE/Group Name           | Presence | Range | IE type and reference | Semantics description                 |
+|-------------------------|----------|-------|-----------------------|---------------------------------------|
+| UE Identity Index Value | M        |       | BIT STRING (SIZE(10)) | Coded as specified in TS 36.304 [20]. |
+
+### 9.3.1.64 RAN UE Paging identity
+
+This IE indicates the RAN UE Paging identity.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description |
+|---------------|----------|-------|-----------------------|-----------------------|
+| I-RNTI        | M        |       | BIT STRING (SIZE(40)) |                       |
+
+### 9.3.1.65 CN UE Paging Identity
+
+The 5G-S-TMSI is used as UE identifier for CN paging.
+
+| IE/Group Name                       | Presence | Range | IE type and reference | Semantics description             |
+|-------------------------------------|----------|-------|-----------------------|-----------------------------------|
+| CHOICE <i>CN UE paging identity</i> | M        |       |                       |                                   |
+| >5G-S-TMSI                          |          |       |                       |                                   |
+| >>5G-S-TMSI                         | M        |       | BIT STRING (SIZE(48)) | Details defined in TS 38.413 [19] |
+
+### 9.3.1.66 Paging DRX
+
+This IE indicates the Paging DRX as defined in TS 36.304 [20].
+
+| IE/Group Name | Presence | Range | IE type and reference             | Semantics description |
+|---------------|----------|-------|-----------------------------------|-----------------------|
+| Paging DRX    | M        |       | ENUMERATED(32, 64, 128, 256, ...) | Unit in radio frame.  |
+
+### 9.3.1.67 Message Identifier
+
+This IE identifies the warning message.
+
+| IE/Group Name      | Presence | Range | IE type and reference | Semantics description                                                |
+|--------------------|----------|-------|-----------------------|----------------------------------------------------------------------|
+| Message Identifier | M        |       | BIT STRING (SIZE(16)) | This IE is set by the 5GC, transferred to the UE by the NG-RAN node. |
+
+### 9.3.1.68 Serial Number
+
+This IE identifies a particular message from the source and type indicated by the Message Identifier and is altered every time the message with a given Message Identifier is changed.
+
+| IE/Group Name | Presence | Range | IE type and reference | Semantics description                                                |
+|---------------|----------|-------|-----------------------|----------------------------------------------------------------------|
+| Serial Number | M        |       | BIT STRING (SIZE(16)) | This IE is set by the 5GC, transferred to the UE by the NG-RAN node. |
+
+### 9.3.1.69 Additional SIB Message List
+
+This IE indicates the list of additional SIB messages containing all the remaining segments of a public warning message if segmentation is applied to such message.
+
+| IE/Group Name                               | Presence | Range                           | IE type and reference | Semantics description                                                                        |
+|---------------------------------------------|----------|---------------------------------|-----------------------|----------------------------------------------------------------------------------------------|
+| <b>Additional SIB Message List Item IEs</b> |          | 1..<br><maxnoofAdditionalSIBs > |                       |                                                                                              |
+| >Additional SIB                             | M        |                                 | OCTET STRING          | SIB message containing one segment of a public warning message, as defined in TS 36.331 [2]. |
+
+| Range bound           | Explanation                                                                  |
+|-----------------------|------------------------------------------------------------------------------|
+| maxnoofAdditionalSIBs | Maximum no. of additional segments of a public warning message. Value is 63. |
+
+### 9.3.1.70 Paging Origin
+
+This IE indicates whether Paging is originated due to the PDU sessions from the non-3GPP access.
+
+| IE/Group Name | Presence | Range | IE type and reference         | Semantics description |
+|---------------|----------|-------|-------------------------------|-----------------------|
+| Paging Origin | M        |       | ENUMERATED<br>(non-3GPP, ...) |                       |
+
+## 9.3.2 Transport Network Layer Related IEs
+
+### 9.3.2.1 UP Transport Layer Information
+
+The *UP Transport Layer Information* IE identifies a W1 transport bearer associated to a DRB. It contains a Transport Layer Address and a GTP Tunnel Endpoint Identifier. The Transport Layer Address is an IP address to be used for the W1 user plane transport. The GTP Tunnel Endpoint Identifier is to be used for the user plane transport between ng-eNB-CU and ng-eNB-DU.
+
+| IE/Group Name                      | Presence | Range | IE type and reference | Semantics description |
+|------------------------------------|----------|-------|-----------------------|-----------------------|
+| CHOICE Transport Layer Information | M        |       |                       |                       |
+| > <i>GTP Tunnel</i>                |          |       |                       |                       |
+| >>Transport Layer Address          | M        |       | 9.3.2.3               |                       |
+| >>GTP-TEID                         | M        |       | 9.3.2.2               |                       |
+
+### 9.3.2.2 GTP-TEID
+
+The *GTP-TEID* IE is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between the ng-eNB-CU and ng-eNB-DU.
+
+| IE/Group Name | Presence | Range | IE type and reference     | Semantics description                      |
+|---------------|----------|-------|---------------------------|--------------------------------------------|
+| GTP-TEID      | M        |       | OCTET STRING<br>(SIZE(4)) | For details and range, see TS 29.281 [17]. |
+
+### 9.3.2.3 Transport Layer Address
+
+This *Transport Layer Address* IE is an IP address.
+
+| IE/Group Name           | Presence | Range | IE type and reference             | Semantics description                                                                                                                                                          |
+|-------------------------|----------|-------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Transport Layer Address | M        |       | BIT STRING<br>(SIZE(1..160, ...)) | The Radio Network Layer is not supposed to interpret the address information. It should pass it to the Transport Layer for interpretation.<br>For details, see TS 38.414 [18]. |
+
+## 9.4 Message and Information Element Abstract Syntax (with ASN.1)
+
+### 9.4.1 General
+
+WIAP ASN.1 definition conforms to ITU-T Recommendation X.691 [21], ITU-T Recommendation X.680 [22] and ITU-T Recommendation X.681 [23].
+
+The ASN.1 definition specifies the structure and content of WIAP messages. WIAP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct a WIAP message according to the PDU definitions module and with the following additional rules:
+
+- IEs shall be ordered (in an IE container) in the order they appear in object set definitions.
+- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e., an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
+
+NOTE: In the above "IE" means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences will have different IE IDs.
+
+If a WIAP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in clause 10.
+
+### 9.4.2 Usage of private message mechanism for non-standard use
+
+The private message mechanism for non-standard use may be used:
+
+- for special operator- (and/or vendor) specific features considered not to be part of the basic functionality, i.e., the functionality required for a complete and high-quality specification in order to guarantee multivendor interoperability;
+- by vendors for research purposes, e.g., to implement and evaluate new algorithms/features before such features are proposed for standardisation.
+
+The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
+
+### 9.4.3 Elementary Procedure Definitions
+
+```
+-- ASN1START
+-- *****
+--
+-- Elementary Procedure definitions
+--
+-- *****
+```
+
+```
+W1AP-PDU-Descriptions {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  ngran-access (22) modules (3) wlap (3) version1 (1) wlap-PDU-Descriptions (0)}
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- *****
+--
+-- IE parameter types from other modules.
+--
+-- *****
+
+IMPORTS
+  Criticality,
+  ProcedureCode
+
+FROM W1AP-CommonDataTypes
+  Reset,
+  ResetAcknowledge,
+  W1SetupRequest,
+  W1SetupResponse,
+  W1SetupFailure,
+  NGENBDUConfigurationUpdate,
+  NGENBDUConfigurationUpdateAcknowledge,
+  NGENBDUConfigurationUpdateFailure,
+  NGENBCUConfigurationUpdate,
+  NGENBCUConfigurationUpdateAcknowledge,
+  NGENBCUConfigurationUpdateFailure,
+  UEContextSetupRequest,
+  UEContextSetupResponse,
+  UEContextSetupFailure,
+  UEContextReleaseCommand,
+  UEContextReleaseComplete,
+  UEContextModificationRequest,
+  UEContextModificationResponse,
+  UEContextModificationFailure,
+  UEContextModificationRequired,
+  UEContextModificationConfirm,
+  ErrorIndication,
+  UEContextReleaseRequest,
+  DLRRMessageTransfer,
+  ULRRMessageTransfer,
+  NGENBDUResourceCoordinationRequest,
+  NGENBDUResourceCoordinationResponse,
+  PrivateMessage,
+  UEInactivityNotification,
+  InitialULRRMessageTransfer,
+  Paging,
+  Notify,
+  WriteReplaceWarningRequest,
+  WriteReplaceWarningResponse,
+  PWSCancelRequest,
+  PWSCancelResponse,
+  PWSSRestartIndication,
+  PWSFailureIndication,
+  NGENBDUStatusIndication,
+  UEContextModificationRefuse
+
+FROM W1AP-PDU-Contents
+  id-Reset,
+  id-W1Setup,
+  id-ngENBDUConfigurationUpdate,
+  id-ngENBCUConfigurationUpdate,
+  id-UEContextSetup,
+  id-UEContextRelease,
+  id-UEContextModification,
+  id-UEContextModificationRequired,
+  id-ErrorIndication,
+  id-UEContextReleaseRequest,
+  id-DLRRMessageTransfer,
+  id-ULRRMessageTransfer,
+  id-NGENBDUResourceCoordination,
+  id-privateMessage,
+  id-UEInactivityNotification,
+  id-InitialULRRMessageTransfer,
+```
+
+```
+
+id-Paging,
+id-Notify,
+id-WriteReplaceWarning,
+id-PWSCancel,
+id-PWSRestartIndication,
+id-PWSFailureIndication,
+id-NGENBDUStatusIndication
+
+FROM W1AP-Constants
+
+    ProtocolIE-SingleContainer{},
+    W1AP-PROTOCOL-IES
+
+FROM W1AP-Containers;
+
+-- *****
+--
+-- Interface Elementary Procedure Class
+--
+-- *****
+
+W1AP-ELEMENTARY-PROCEDURE ::= CLASS {
+    &InitiatingMessage      ,
+    &SuccessfulOutcome      OPTIONAL,
+    &UnsuccessfulOutcome   OPTIONAL,
+    &procedureCode          ProcedureCode  UNIQUE,
+    &criticality            Criticality    DEFAULT ignore
+}
+WITH SYNTAX {
+    INITIATING MESSAGE      &InitiatingMessage
+    [SUCCESSFUL OUTCOME    &SuccessfulOutcome]
+    [UNSUCCESSFUL OUTCOME  &UnsuccessfulOutcome]
+    PROCEDURE CODE        &procedureCode
+    [CRITICALITY           &criticality]
+}
+
+-- *****
+--
+-- Interface PDU Definition
+--
+-- *****
+
+W1AP-PDU ::= CHOICE {
+    initiatingMessage   InitiatingMessage,
+    successfulOutcome   SuccessfulOutcome,
+    unsuccessfulOutcome UnsuccessfulOutcome
+}
+
+InitiatingMessage ::= SEQUENCE {
+    procedureCode   W1AP-ELEMENTARY-PROCEDURE.&procedureCode      ({W1AP-ELEMENTARY-PROCEDURES}),
+    criticality     W1AP-ELEMENTARY-PROCEDURE.&criticality        ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value           W1AP-ELEMENTARY-PROCEDURE.&InitiatingMessage  ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+SuccessfulOutcome ::= SEQUENCE {
+    procedureCode   W1AP-ELEMENTARY-PROCEDURE.&procedureCode      ({W1AP-ELEMENTARY-PROCEDURES}),
+    criticality     W1AP-ELEMENTARY-PROCEDURE.&criticality        ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value           W1AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome  ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+UnsuccessfulOutcome ::= SEQUENCE {
+    procedureCode   W1AP-ELEMENTARY-PROCEDURE.&procedureCode      ({W1AP-ELEMENTARY-PROCEDURES}),
+    criticality     W1AP-ELEMENTARY-PROCEDURE.&criticality        ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
+    value           W1AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({W1AP-ELEMENTARY-PROCEDURES}{@procedureCode})
+}
+
+-- *****
+--
+-- Interface Elementary Procedure List
+--
+-- *****
+
+```
+
+```
+
+-- *****
+
+WIAP-ELEMENTARY-PROCEDURES WIAP-ELEMENTARY-PROCEDURE ::= {
+    WIAP-ELEMENTARY-PROCEDURES-CLASS-1
+    WIAP-ELEMENTARY-PROCEDURES-CLASS-2,
+    ...
+}
+
+WIAP-ELEMENTARY-PROCEDURES-CLASS-1 WIAP-ELEMENTARY-PROCEDURE ::= {
+    reset
+    w1Setup
+    ngeNBDUConfigurationUpdate
+    ngeNBCUConfigurationUpdate
+    uEContextSetup
+    uEContextRelease
+    uEContextModification
+    uEContextModificationRequired
+    writeReplaceWarning
+    pWSCancel
+    ngeNBDUResourceCoordination
+    ...
+}
+
+WIAP-ELEMENTARY-PROCEDURES-CLASS-2 WIAP-ELEMENTARY-PROCEDURE ::= {
+    errorIndication
+    uEContextReleaseRequest
+    dLRRMessageTransfer
+    uLRRMessageTransfer
+    uEInactivityNotification
+    privateMessage
+    initialULRRMessageTransfer
+    paging
+    notify
+    pWSRestartIndication
+    pWSFailureIndication
+    ngeNBDUStatusIndication
+    ...
+}
+
+-- *****
+--
+-- Interface Elementary Procedures
+--
+-- *****
+
+reset WIAP-ELEMENTARY-PROCEDURE ::= {
+    INITIATING MESSAGE Reset
+    SUCCESSFUL OUTCOME ResetAcknowledge
+    PROCEDURE CODE id-Reset
+    CRITICALITY reject
+}
+
+w1Setup WIAP-ELEMENTARY-PROCEDURE ::= {
+    INITIATING MESSAGE W1SetupRequest
+    SUCCESSFUL OUTCOME W1SetupResponse
+    UNSUCCESSFUL OUTCOME W1SetupFailure
+    PROCEDURE CODE id-W1Setup
+    CRITICALITY reject
+}
+
+ngeNBDUConfigurationUpdate WIAP-ELEMENTARY-PROCEDURE ::= {
+    INITIATING MESSAGE NGENNBDUConfigurationUpdate
+    SUCCESSFUL OUTCOME NGENNBDUConfigurationUpdateAcknowledge
+    UNSUCCESSFUL OUTCOME NGENNBDUConfigurationUpdateFailure
+    PROCEDURE CODE id-ngeNBDUConfigurationUpdate
+    CRITICALITY reject
+}
+
+ngeNBCUConfigurationUpdate WIAP-ELEMENTARY-PROCEDURE ::= {
+    INITIATING MESSAGE NGENNBCUConfigurationUpdate
+    SUCCESSFUL OUTCOME NGENNBCUConfigurationUpdateAcknowledge
+    UNSUCCESSFUL OUTCOME NGENNBCUConfigurationUpdateFailure
+    PROCEDURE CODE id-ngeNBCUConfigurationUpdate
+    CRITICALITY reject
+}
+
+uEContextSetup WIAP-ELEMENTARY-PROCEDURE ::= {
+    INITIATING MESSAGE UEContextSetupRequest
+}
+
+```
+
+```
+        SUCCESSFUL OUTCOME      UEContextSetupResponse
+        UNSUCCESSFUL OUTCOME    UEContextSetupFailure
+        PROCEDURE CODE          id-UEContextSetup
+        CRITICALITY             reject
+    }
+
+    uEContextRelease W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      UEContextReleaseCommand
+        SUCCESSFUL OUTCOME      UEContextReleaseComplete
+        PROCEDURE CODE          id-UEContextRelease
+        CRITICALITY             reject
+    }
+
+    uEContextModification W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      UEContextModificationRequest
+        SUCCESSFUL OUTCOME      UEContextModificationResponse
+        UNSUCCESSFUL OUTCOME    UEContextModificationFailure
+        PROCEDURE CODE          id-UEContextModification
+        CRITICALITY             reject
+    }
+
+    uEContextModificationRequired W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      UEContextModificationRequired
+        SUCCESSFUL OUTCOME      UEContextModificationConfirm
+        UNSUCCESSFUL OUTCOME    UEContextModificationRefuse
+        PROCEDURE CODE          id-UEContextModificationRequired
+        CRITICALITY             reject
+    }
+
+    writeReplaceWarning W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      WriteReplaceWarningRequest
+        SUCCESSFUL OUTCOME      WriteReplaceWarningResponse
+        PROCEDURE CODE          id-WriteReplaceWarning
+        CRITICALITY             reject
+    }
+
+    pWSCancel W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      PWSCancelRequest
+        SUCCESSFUL OUTCOME      PWSCancelResponse
+        PROCEDURE CODE          id-PWSCancel
+        CRITICALITY             reject
+    }
+
+    errorIndication W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      ErrorIndication
+        PROCEDURE CODE          id-ErrorIndication
+        CRITICALITY             ignore
+    }
+
+    uEContextReleaseRequest W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      UEContextReleaseRequest
+        PROCEDURE CODE          id-UEContextReleaseRequest
+        CRITICALITY             ignore
+    }
+
+    initialULRRCMessTransfer W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      InitialULRRCMessTransfer
+        PROCEDURE CODE          id-InitialULRRCMessTransfer
+        CRITICALITY             ignore
+    }
+
+    dLRRCMessTransfer W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      DLRRCMessTransfer
+        PROCEDURE CODE          id-DLRRCMessTransfer
+        CRITICALITY             ignore
+    }
+
+    uLRRCMessTransfer W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      ULRRCMessTransfer
+        PROCEDURE CODE          id-ULRRCMessTransfer
+        CRITICALITY             ignore
+    }
+
+    uEInactivityNotification W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      UEInactivityNotification
+        PROCEDURE CODE          id-UEInactivityNotification
+    }
+```
+
+```
+
+        CRITICALITY      ignore
+    }
+
+    ngeNBDUResourceCoordination W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      NGENBDUResourceCoordinationRequest
+        SUCCESSFUL OUTCOME      NGENBDUResourceCoordinationResponse
+        PROCEDURE CODE          id-NGENBDUResourceCoordination
+        CRITICALITY             reject
+    }
+
+    privateMessage W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      PrivateMessage
+        PROCEDURE CODE          id-privateMessage
+        CRITICALITY             ignore
+    }
+
+    paging W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      Paging
+        PROCEDURE CODE          id-Paging
+        CRITICALITY             ignore
+    }
+
+    notify W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      Notify
+        PROCEDURE CODE          id-Notify
+        CRITICALITY             ignore
+    }
+
+    pWSRestartIndication W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      PWSRestartIndication
+        PROCEDURE CODE          id-PWSRestartIndication
+        CRITICALITY             ignore
+    }
+
+    pWSFailureIndication W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      PWSFailureIndication
+        PROCEDURE CODE          id-PWSFailureIndication
+        CRITICALITY             ignore
+    }
+
+    ngeNBDUStatusIndication W1AP-ELEMENTARY-PROCEDURE ::= {
+        INITIATING MESSAGE      NGENBDUStatusIndication
+        PROCEDURE CODE          id-NGENBDUStatusIndication
+        CRITICALITY             ignore
+    }
+    
+```
+
+```
+
+END
+-- ASN1STOP
+    
+```
+
+### 9.4.4 PDU Definitions
+
+```
+
+-- ASN1START
+-- ******************************************************************************
+--
+-- PDU definitions for W1AP.
+--
+-- ******************************************************************************
+
+W1AP-PDU-Contents {
+    itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+    ngran-access (22) modules (3) wlap (3) version1 (1) wlap-PDU-Contents (1) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- ******************************************************************************
+--
+-- IE parameter types from other modules.
+--
+-- ******************************************************************************
+
+IMPORTS
+    
+```
+
+Candidate-SpCell-Item,  
+Cause,  
+Cells-Failed-to-be-Activated-List-Item,  
+Cells-Status-Item,  
+Cells-to-be-Activated-List-Item,  
+Cells-to-be-Deactivated-List-Item,  
+C-RNTI,  
+CriticalityDiagnostics,  
+CUtoDURRInformation,  
+DRB-Activity-Item,  
+DRBID,  
+DRBs-FailedToBeModified-Item,  
+DRBs-FailedToBeSetup-Item,  
+DRBs-FailedToBeSetupMod-Item,  
+DRB-Notify-Item,  
+DRBs-ModifiedConf-Item,  
+DRBs-Modified-Item,  
+DRBs-Required-ToBeModified-Item,  
+DRBs-Required-ToBeReleased-Item,  
+DRBs-Setup-Item,  
+DRBs-SetupMod-Item,  
+DRBs-ToBeModified-Item,  
+DRBs-ToBeReleased-Item,  
+DRBs-ToBeSetup-Item,  
+DRBs-ToBeSetupMod-Item,  
+DRXCycle,  
+DUtoCURRInformation,  
+EUTRANQoS,  
+NGENB-CU-UE-W1AP-ID,  
+NGENB-DU-UE-W1AP-ID,  
+NGENB-DU-ID,  
+NGENB-DU-Served-Cells-Item,  
+NGENB-DU-System-Information,  
+InactivityMonitoringRequest,  
+InactivityMonitoringResponse,  
+NotificationControl,  
+EUTRANCGI,  
+EUTRANPCI,  
+Potential-SpCell-Item,  
+RAT-FrequencyPriorityInformation,  
+ResourceCoordinationTransferContainer,  
+RRCContainer,  
+RRCReconfigurationCompleteIndicator,  
+SCellIndex,  
+SCell-ToBeRemoved-Item,  
+SCell-ToBeSetup-Item,  
+SCell-ToBeSetupMod-Item,  
+SCell-FailedtoSetup-Item,  
+SCell-FailedtoSetupMod-Item,  
+ServCellIndex,  
+Served-Cell-Information,  
+Served-Cells-To-Add-Item,  
+Served-Cells-To-Delete-Item,  
+Served-Cells-To-Modify-Item,  
+SRBID,  
+SRBs-FailedToBeSetup-Item,  
+SRBs-FailedToBeSetupMod-Item,  
+SRBs-Required-ToBeReleased-Item,  
+SRBs-ToBeReleased-Item,  
+SRBs-ToBeSetup-Item,  
+SRBs-ToBeSetupMod-Item,  
+SRBs-Modified-Item,  
+SRBs-Setup-Item,  
+SRBs-SetupMod-Item,  
+TransactionID,  
+TransmissionActionIndicator,  
+DUtoCURRContainer,  
+PagingCell-Item,  
+UEIdentityIndexValue,  
+UE-associatedLogicalW1-ConnectionItem,  
+PagingDRX,  
+PagingIdentity,  
+PagingOrigin,  
+PWSSystemInformation,  
+Broadcast-To-Be-Cancelled-Item,  
+Cells-Broadcast-Cancelled-Item,  
+E-UTRAN-CGI-List-For-Restart-Item,  
+PWS-Failed-E-UTRAN-CGI-Item,
+
+RepetitionPeriod,  
+NumberofBroadcastRequest,  
+Cells-To-Be-Broadcast-Item,  
+Cells-Broadcast-Completed-Item,  
+Cancel-all-Warning-Messages-Indicator,  
+NotificationInformation,  
+EUTRA-NR-CellResourceCoordinationReq-Container,  
+EUTRA-NR-CellResourceCoordinationReqAck-Container,  
+RequestType,  
+PLMN-Identity,  
+BitRate,  
+NGENBDUOverloadInformation,  
+ResourceCoordinationTransferInformation,  
+IgnoreResourceCoordinationRequestContainer,  
+SCGIndicator
+
+## FROM W1AP-IEs
+
+PrivateIE-Container{},  
+ProtocolExtensionContainer{},  
+ProtocolIE-Container{},  
+ProtocolIE-ContainerPair{},  
+ProtocolIE-SingleContainer{},  
+W1AP-PRIVATE-IES,  
+W1AP-PROTOCOL-EXTENSION,  
+W1AP-PROTOCOL-IES,  
+W1AP-PROTOCOL-IES-PAIR
+
+## FROM W1AP-Containers
+
+id-Candidate-SpCell-List,  
+id-Cause,  
+id-Cancel-all-Warning-Messages-Indicator,  
+id-NotificationInformation,  
+id-Cells-Failed-to-be-Activated-List,  
+id-Cells-Status-List,  
+id-Cells-to-be-Activated-List,  
+id-Cells-to-be-Deactivated-List,  
+id-ConfirmedUEID,  
+id-C-RNTI,  
+id-CUtoDURRCInformation,  
+id-CriticalityDiagnostics,  
+id-DRB-Activity-List,  
+id-DRBs-FailedToBeModified-List,  
+id-DRBs-FailedToBeSetup-List,  
+id-DRBs-FailedToBeSetupMod-List,  
+id-DRBs-ModifiedConf-List,  
+id-DRBs-Modified-List,  
+id-DRB-Notify-List,  
+id-DRBs-Required-ToBeModified-List,  
+id-DRBs-Required-ToBeReleased-List,  
+id-DRBs-Setup-List,  
+id-DRBs-SetupMod-List,  
+id-DRBs-ToBeModified-List,  
+id-DRBs-ToBeReleased-List,  
+id-DRBs-ToBeSetup-List,  
+id-DRBs-ToBeSetupMod-List,  
+id-DRXcycle,  
+id-DUtoCURRCInformation,  
+id-ngenNB-CU-UE-W1AP-ID,  
+id-ngenNB-DU-UE-W1AP-ID,  
+id-ngenNB-DU-ID,  
+id-ngenNB-DU-Served-Cells-List,  
+id-InactivityMonitoringRequest,  
+id-InactivityMonitoringResponse,  
+id-oldngenNB-DU-UE-W1AP-ID,  
+id-Potential-SpCell-List,  
+id-RAT-FrequencyPriorityInformation,  
+id-ResetType,  
+id-ResourceCoordinationTransferContainer,  
+id-RRContainer,  
+id-RRReconfigurationCompleteIndicator,  
+id-SCell-FailedtoSetup-List,  
+id-SCell-FailedtoSetupMod-List,  
+id-SCell-ToBeRemoved-List,  
+id-SCell-ToBeSetup-List,  
+id-SCell-ToBeSetupMod-List,  
+id-Served-Cells-To-Add-List,
+
+```
+
+        id-Served-Cells-To-Delete-List,
+        id-Served-Cells-To-Modify-List,
+        id-ServCellIndex,
+        id-SpCell-ID,
+        id-SRBID,
+        id-SRBs-FailedToBeSetup-List,
+        id-SRBs-FailedToBeSetupMod-List,
+        id-SRBs-Required-ToBeReleased-List,
+        id-SRBs-ToBeReleased-List,
+        id-SRBs-ToBeSetup-List,
+        id-SRBs-ToBeSetupMod-List,
+        id-SRBs-Modified-List,
+        id-SRBs-Setup-List,
+        id-SRBs-SetupMod-List,
+        id-TransactionID,
+        id-TransmissionActionIndicator,
+        id-UE-associatedLogicalW1-ConnectionListResAck,
+        id-DUtoCURRCContainer,
+        id-EUTRANCGI,
+        id-PagingCell-List,
+        id-PagingDRX,
+        id-UEIdentityIndexValue,
+        id-PagingIdentity,
+        id-PagingOrigin,
+        id-PWSSystemInformation,
+        id-RepetitionPeriod,
+        id-NumberOfBroadcastRequest,
+        id-Cells-To-Be-Broadcast-List,
+        id-Cells-Broadcast-Completed-List,
+        id-Broadcast-To-Be-Cancelled-List,
+        id-Cells-Broadcast-Cancelled-List,
+        id-E-UTRAN-CGI-List-For-Restart-List,
+        id-PWS-Failed-E-UTRAN-CGI-List,
+        id-EUTRA-NR-CellResourceCoordinationReq-Container,
+        id-EUTRA-NR-CellResourceCoordinationReqAck-Container,
+        id-RequestType,
+        id-ServingPLMN,
+        id-NGENB-DU-UE-AMBR-UL,
+        id-NGENBDUOverloadInformation,
+        id-ResourceCoordinationTransferInformation,
+        id-IgnoreResourceCoordinationRequestContainer,
+        id-SCGIndicator,
+        maxCellinngenEBDU,
+        maxnoofCandidateSpCells,
+        maxnoofDRBs,
+        maxnoofErrors,
+        maxnoofIndividualW1ConnectionsToReset,
+        maxnoofPotentialSpCells,
+        maxnoofSCells,
+        maxnoofSRBs,
+        maxnoofPagingCells,
+        maxnoofTNLAssociations,
+        maxCellineNB,
+        maxnoofUEIDs
+    
+```
+
+FROM W1AP-Constants;
+
+```
+
+-- ******************************************************************************
+--
+-- RESET ELEMENTARY PROCEDURE
+--
+-- ******************************************************************************
+
+-- ******************************************************************************
+--
+-- Reset
+--
+-- ******************************************************************************
+    
+```
+
+```
+
+Reset ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { {ResetIEs} },
+    ...
+}
+    
+```
+
+```
+
+ResetIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-TransactionID  CRITICALITY reject  TYPE TransactionID  PRESENCE mandatory }|
+    
+```
+
+```
+
+        { ID id-Cause              CRITICALITY ignore  TYPE Cause              PRESENCE mandatory  }|
+        { ID id-ResetType          CRITICALITY reject  TYPE ResetType          PRESENCE mandatory  },
+        ...
+}
+
+ResetType ::= CHOICE {
+    w1-Interface            ResetAll,
+    partOfW1-Interface      UE-associatedLogicalW1-ConnectionListRes,
+    choice-extension        ProtocolIE-SingleContainer { { ResetType-ExtIEs} }
+}
+
+ResetType-ExtIEs W1AP-PROTOCOL-IES ::= {
+    ...
+}
+
+ResetAll ::= ENUMERATED {
+    reset-all,
+    ...
+}
+
+UE-associatedLogicalW1-ConnectionListRes ::= SEQUENCE (SIZE(1..
+maxnoofIndividualW1ConnectionsToReset)) OF UE-associatedLogicalW1-ConnectionItem
+
+-- **************************************************************
+--
+-- Reset Acknowledge
+--
+-- **************************************************************
+
+ResetAcknowledge ::= SEQUENCE {
+    protocolIEs          ProtocolIE-Container          { {ResetAcknowledgeIEs} },
+    ...
+}
+
+ResetAcknowledgeIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-TransactionID                                  CRITICALITY reject  TYPE TransactionID              PRESENCE mandatory  }|
+    { ID id-UE-associatedLogicalW1-ConnectionListResAck    CRITICALITY ignore  TYPE UE-associatedLogicalW1-ConnectionListResAck    PRESENCE optional   }|
+    { ID id-CriticalityDiagnostics                         CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional   },
+    ...
+}
+
+UE-associatedLogicalW1-ConnectionListResAck ::= SEQUENCE (SIZE(1..
+maxnoofIndividualW1ConnectionsToReset)) OF UE-associatedLogicalW1-ConnectionItem
+
+-- **************************************************************
+--
+-- ERROR INDICATION ELEMENTARY PROCEDURE
+--
+-- **************************************************************
+
+-- **************************************************************
+--
+-- Error Indication
+--
+-- **************************************************************
+
+ErrorIndication ::= SEQUENCE {
+    protocolIEs          ProtocolIE-Container          {{ErrorIndicationIEs}},
+    ...
+}
+
+ErrorIndicationIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-TransactionID              CRITICALITY reject  TYPE TransactionID              PRESENCE mandatory}|
+    { ID id-ngENB-CU-UE-W1AP-ID        CRITICALITY ignore  TYPE NGENB-CU-UE-W1AP-ID        PRESENCE optional }|
+    { ID id-ngENB-DU-UE-W1AP-ID        CRITICALITY ignore  TYPE NGENB-DU-UE-W1AP-ID        PRESENCE optional }|
+    { ID id-Cause                      CRITICALITY ignore  TYPE Cause                      PRESENCE mandatory }|
+    { ID id-CriticalityDiagnostics     CRITICALITY ignore  TYPE CriticalityDiagnostics     PRESENCE optional  },
+    ...
+}
+
+-- **************************************************************
+--
+```
+
+```
+
+-- W1 SETUP ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- W1 Setup Request
+--
+-- *****
+
+W1SetupRequest ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { {W1SetupRequestIEs} },
+  ...
+}
+
+W1SetupRequestIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory }|
+  { ID id-ngenB-DU-ID      CRITICALITY reject  TYPE NGENB-DU-ID      PRESENCE mandatory }|
+  { ID id-ngenB-DU-Served-Cells-List      CRITICALITY reject  TYPE NGENB-DU-Served-Cells-List
+    PRESENCE optional },
+  ...
+}
+
+NGENB-DU-Served-Cells-List ::= SEQUENCE (SIZE(1.. maxCellinngenBBDU)) OF NGENB-DU-Served-Cells-Item
+
+-- *****
+--
+-- W1 Setup Response
+--
+-- *****
+
+W1SetupResponse ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { {W1SetupResponseIEs} },
+  ...
+}
+
+W1SetupResponseIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory }|
+  { ID id-Cells-to-be-Activated-List      CRITICALITY reject  TYPE Cells-to-be-Activated-List
+    PRESENCE optional },
+  ...
+}
+
+Cells-to-be-Activated-List ::= SEQUENCE (SIZE(1.. maxCellinngenBBDU)) OF Cells-to-be-Activated-List-Item
+
+-- *****
+--
+-- W1 Setup Failure
+--
+-- *****
+
+W1SetupFailure ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { {W1SetupFailureIEs} },
+  ...
+}
+
+W1SetupFailureIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory }|
+  { ID id-Cause      CRITICALITY ignore  TYPE Cause      PRESENCE mandatory }|
+  { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional },
+  ...
+}
+
+-- *****
+--
+-- NGENB-DU CONFIGURATION UPDATE ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+
+```
+
+```
+
+--
+-- NGENB-DU CONFIGURATION UPDATE
+--
+-- *****
+
+NGENBDUConfigurationUpdate ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { {NGENBDUConfigurationUpdateIEs} },
+    ...
+}
+
+NGENBDUConfigurationUpdateIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory  }|
+    { ID id-Served-Cells-To-Add-List  CRITICALITY reject  TYPE Served-Cells-To-Add-List
+        PRESENCE optional  }|
+    { ID id-Served-Cells-To-Modify-List  CRITICALITY reject  TYPE Served-Cells-To-Modify-List
+        PRESENCE optional  }|
+    { ID id-Served-Cells-To-Delete-List  CRITICALITY reject  TYPE Served-Cells-To-Delete-List
+        PRESENCE optional  }|
+    { ID id-Cells-Status-List  CRITICALITY reject  TYPE Cells-Status-List  PRESENCE optional  }|
+    { ID id-ngenb-DU-ID  CRITICALITY reject  TYPE NGENB-DU-ID  PRESENCE optional  },
+    ...
+}
+
+Served-Cells-To-Add-List ::= SEQUENCE (SIZE(1.. maxCellinngneNBNU)) OF Served-Cells-To-Add-Item
+
+Served-Cells-To-Modify-List ::= SEQUENCE (SIZE(1.. maxCellinngneNBNU)) OF Served-Cells-To-Modify-Item
+
+Served-Cells-To-Delete-List ::= SEQUENCE (SIZE(1.. maxCellinngneNBNU)) OF Served-Cells-To-Delete-Item
+
+Cells-Status-List ::= SEQUENCE (SIZE(0.. maxCellinngneNBNU)) OF Cells-Status-Item
+
+-- *****
+--
+-- NGENB-DU CONFIGURATION UPDATE ACKNOWLEDGE
+--
+-- *****
+
+NGENBDUConfigurationUpdateAcknowledge ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { {NGENBDUConfigurationUpdateAcknowledgeIEs} },
+    ...
+}
+
+NGENBDUConfigurationUpdateAcknowledgeIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID
+        PRESENCE mandatory  }|
+    { ID id-Cells-to-be-Activated-List  CRITICALITY reject  TYPE Cells-to-be-Activated-List
+        PRESENCE optional  }|
+    { ID id-Cells-to-be-Deactivated-List  CRITICALITY reject  TYPE Cells-to-be-Deactivated-List
+        PRESENCE optional  }|
+    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics
+        PRESENCE optional  },
+    ...
+}
+
+-- *****
+--
+-- NGENB-DU CONFIGURATION UPDATE FAILURE
+--
+-- *****
+
+NGENBDUConfigurationUpdateFailure ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { {NGENBDUConfigurationUpdateFailureIEs} },
+    ...
+}
+
+NGENBDUConfigurationUpdateFailureIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE
+        mandatory  }|
+    { ID id-Cause  CRITICALITY ignore  TYPE Cause  PRESENCE
+        mandatory  }|
+    { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics
+        PRESENCE optional  },
+    ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- NGENB-CU CONFIGURATION UPDATE ELEMENTARY PROCEDURE
+--
+-- *****
+--
+-- *****
+--
+-- NGENB-CU CONFIGURATION UPDATE
+--
+-- *****
+
+NGENBCUConfigurationUpdate ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { { NGENBCUConfigurationUpdateIEs} },
+  ...
+}
+
+NGENBCUConfigurationUpdateIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID
+    PRESENCE mandatory  }|
+  { ID id-Cells-to-be-Activated-List      CRITICALITY reject  TYPE Cells-to-be-Activated-List
+    PRESENCE optional  }|
+  { ID id-Cells-to-be-Deactivated-List      CRITICALITY reject  TYPE Cells-to-be-Deactivated-
+List      PRESENCE optional  },
+  ...
+}
+
+Cells-to-be-Deactivated-List ::= SEQUENCE (SIZE(1.. maxCellinngenBBDU)) OF Cells-to-be-
+Deactivated-List-Item
+
+-- *****
+--
+-- NGENB-CU CONFIGURATION UPDATE ACKNOWLEDGE
+--
+-- *****
+
+NGENBCUConfigurationUpdateAcknowledge ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { { NGENBCUConfigurationUpdateAcknowledgeIEs} },
+  ...
+}
+
+NGENBCUConfigurationUpdateAcknowledgeIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID
+    PRESENCE mandatory  }|
+  { ID id-Cells-Failed-to-be-Activated-List      CRITICALITY reject  TYPE Cells-Failed-to-be-
+Activated-List      PRESENCE optional}|
+  { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional  },
+  ...
+}
+
+Cells-Failed-to-be-Activated-List ::= SEQUENCE (SIZE(1.. maxCellinngenBBDU)) OF Cells-Failed-to-
+be-Activated-List-Item
+
+-- *****
+--
+-- NGENB-CU CONFIGURATION UPDATE FAILURE
+--
+-- *****
+
+NGENBCUConfigurationUpdateFailure ::= SEQUENCE {
+  protocolIEs      ProtocolIE-Container      { { NGENBCUConfigurationUpdateFailureIEs} },
+  ...
+}
+
+NGENBCUConfigurationUpdateFailureIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID      CRITICALITY reject  TYPE TransactionID      PRESENCE
+mandatory  }|
+  { ID id-Cause      CRITICALITY ignore  TYPE Cause      PRESENCE
+mandatory  }|
+  { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional  },
+  ...
+}
+
+```
+
+```
+
+-- *****
+--
+-- NGENB-DU RESOURCE COORDINATION REQUEST
+--
+-- *****
+
+NGENBDUResourceCoordinationRequest ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      {NGENBDUResourceCoordinationRequest-IEs},
+    ...
+}
+
+NGENBDUResourceCoordinationRequest-IEs WIAP-PROTOCOL-IES ::= {
+    { ID id-TransactionID  CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory  }|
+    { ID id-RequestType  CRITICALITY reject  TYPE RequestType      PRESENCE mandatory  }|
+    { ID id-EUTRA-NR-CellResourceCoordinationReq-Container  CRITICALITY reject  TYPE EUTRA-NR-
+CellResourceCoordinationReq-Container      PRESENCE mandatory}|
+    { ID id-IgnoreResourceCoordinationRequestContainer  CRITICALITY reject  TYPE
+IgnoreResourceCoordinationRequestContainer      PRESENCE optional },
+    ...
+}
+
+-- *****
+--
+-- NGENBDU RESOURCE COORDINATION RESPONSE
+--
+-- *****
+
+NGENBDUResourceCoordinationResponse ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      {NGENBDUResourceCoordinationResponse-IEs},
+    ...
+}
+
+NGENBDUResourceCoordinationResponse-IEs WIAP-PROTOCOL-IES ::= {
+    { ID id-TransactionID  CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory  }|
+    { ID id-EUTRA-NR-CellResourceCoordinationReqAck-Container  CRITICALITY reject  TYPE EUTRA-NR-
+CellResourceCoordinationReqAck-Container      PRESENCE mandatory},
+    ...
+}
+
+-- *****
+--
+-- UE Context Setup ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- UE CONTEXT SETUP REQUEST
+--
+-- *****
+
+UEContextSetupRequest ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { UEContextSetupRequestIEs} },
+    ...
+}
+
+UEContextSetupRequestIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-ngENB-CU-UE-WIAP-ID      CRITICALITY reject  TYPE NGENB-CU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-ngENB-DU-UE-WIAP-ID      CRITICALITY ignore  TYPE NGENB-DU-UE-WIAP-ID
+      PRESENCE optional  }|
+    { ID id-SpCell-ID      CRITICALITY reject  TYPE EUTRANCGI
+      PRESENCE mandatory  }|
+    { ID id-ServCellIndex      CRITICALITY reject  TYPE ServCellIndex
+      PRESENCE mandatory  }|
+    { ID id-CUtoDURRCInformation      CRITICALITY reject  TYPE CUtoDURRCInformation
+      PRESENCE mandatory}|
+    { ID id-Candidate-SpCell-List      CRITICALITY ignore  TYPE Candidate-SpCell-List
+      PRESENCE optional  }|
+    { ID id-DRXCycle      CRITICALITY ignore  TYPE DRXCycle
+      PRESENCE optional  }|
+    { ID id-SCell-ToBeSetup-List      CRITICALITY ignore  TYPE SCell-ToBeSetup-List
+      PRESENCE optional  }|
+    { ID id-SRBs-ToBeSetup-List      CRITICALITY reject  TYPE SRBs-ToBeSetup-List
+      PRESENCE optional  }|
+}
+
+```
+
+```
+
+    { ID id-DRBs-ToBeSetup-List          CRITICALITY reject  TYPE DRBs-ToBeSetup-List
+      PRESENCE optional  }|
+    { ID id-InactivityMonitoringRequest          CRITICALITY reject  TYPE
+InactivityMonitoringRequest          PRESENCE optional  }|
+    { ID id-RAT-FrequencyPriorityInformation          CRITICALITY reject  TYPE RAT-
+FrequencyPriorityInformation          PRESENCE optional  }|
+    { ID id-RRCContainer          CRITICALITY ignore  TYPE RRCContainer
+      PRESENCE optional  }|
+    { ID id-ServingPLMN          CRITICALITY ignore  TYPE PLMN-Identity
+      PRESENCE optional  }|
+    { ID id-NGENB-DU-UE-AMBR-UL          CRITICALITY ignore  TYPE BitRate
+      PRESENCE conditional }|
+    { ID id-ResourceCoordinationTransferInformation          CRITICALITY ignore  TYPE
+ResourceCoordinationTransferInformation          PRESENCE optional  },
+    ...
+  }
+
+Candidate-SpCell-List ::= SEQUENCE (SIZE(1..maxnoofCandidateSpCells)) OF Candidate-SpCell-Item
+
+SCell-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF SCell-ToBeSetup-Item
+
+SRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-ToBeSetup-Item
+
+DRBs-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-ToBeSetup-Item
+
+-- *****
+--
+-- UE CONTEXT SETUP RESPONSE
+--
+-- *****
+
+UEContextSetupResponse ::= SEQUENCE {
+  protocolIEs          ProtocolIE-Container          { { UEContextSetupResponseIEs } },
+  ...
+}
+
+UEContextSetupResponseIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-NGENB-CU-UE-WIAP-ID          CRITICALITY reject  TYPE NGENB-CU-UE-WIAP-ID
+    PRESENCE mandatory  }|
+  { ID id-NGENB-DU-UE-WIAP-ID          CRITICALITY reject  TYPE NGENB-DU-UE-WIAP-ID
+    PRESENCE mandatory  }|
+  { ID id-DUtoCURRCInformation          CRITICALITY reject  TYPE DUtoCURRCInformation
+    PRESENCE mandatory  }|
+  { ID id-C-RNTI          CRITICALITY ignore  TYPE C-RNTI
+    PRESENCE optional  }|
+  { ID id-ResourceCoordinationTransferContainer          CRITICALITY ignore  TYPE
+ResourceCoordinationTransferContainer          PRESENCE optional  }|
+  { ID id-DRBs-Setup-List          CRITICALITY ignore  TYPE DRBs-Setup-List
+    PRESENCE optional  }|
+  { ID id-SRBs-FailedToBeSetup-List          CRITICALITY ignore  TYPE SRBs-FailedToBeSetup-
+List          PRESENCE optional  }|
+  { ID id-DRBs-FailedToBeSetup-List          CRITICALITY ignore  TYPE DRBs-FailedToBeSetup-
+List          PRESENCE optional  }|
+  { ID id-SCell-FailedtoSetup-List          CRITICALITY ignore  TYPE SCell-FailedtoSetup-
+List          PRESENCE optional  }|
+  { ID id-InactivityMonitoringResponse          CRITICALITY reject  TYPE
+InactivityMonitoringResponse          PRESENCE optional  }|
+  { ID id-SRBs-Setup-List          CRITICALITY ignore  TYPE SRBs-Setup-List
+    PRESENCE optional  }|
+  { ID id-CriticalityDiagnostics          CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional  },
+  ...
+}
+
+DRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-Setup-Item
+
+SRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-FailedToBeSetup-Item
+
+DRBs-FailedToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-FailedToBeSetup-Item
+
+SCell-FailedtoSetup-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF SCell-FailedtoSetup-Item
+
+SRBs-Setup-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-Setup-Item
+
+```
+
+```
+
+-- *****
+--
+-- UE CONTEXT SETUP FAILURE
+--
+-- *****
+
+UEContextSetupFailure ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { { UEContextSetupFailureIEs} },
+    ...
+}
+
+UEContextSetupFailureIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-ngenB-CU-UE-WIAP-ID      CRITICALITY reject  TYPE NGENB-CU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-ngenB-DU-UE-WIAP-ID      CRITICALITY ignore  TYPE NGENB-DU-UE-WIAP-ID
+      PRESENCE optional   }|
+    { ID id-Cause                  CRITICALITY ignore  TYPE Cause                PRESENCE
+      mandatory  }|
+    { ID id-Potential-SpCell-List    CRITICALITY ignore  TYPE Potential-SpCell-List  PRESENCE
+      optional  }|
+    { ID id-CriticalityDiagnostics   CRITICALITY ignore  TYPE CriticalityDiagnostics
+      PRESENCE optional  },
+    ...
+}
+
+Potential-SpCell-List ::= SEQUENCE (SIZE(0..maxnoofPotentialSpCells)) OF Potential-SpCell-Item
+
+-- *****
+--
+-- UE Context Release Request ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- UE Context Release Request
+--
+-- *****
+
+UEContextReleaseRequest ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { { UEContextReleaseRequestIEs} },
+    ...
+}
+
+UEContextReleaseRequestIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-ngenB-CU-UE-WIAP-ID CRITICALITY reject  TYPE NGENB-CU-UE-WIAP-ID    PRESENCE mandatory
+    }|
+    { ID id-ngenB-DU-UE-WIAP-ID CRITICALITY reject  TYPE NGENB-DU-UE-WIAP-ID    PRESENCE mandatory
+    }|
+    { ID id-Cause                CRITICALITY ignore  TYPE Cause                PRESENCE mandatory  },
+    ...
+}
+
+-- *****
+--
+-- UE Context Release (ngenB-CU initiated) ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- UE CONTEXT RELEASE COMMAND
+--
+-- *****
+
+UEContextReleaseCommand ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { { UEContextReleaseCommandIEs} },
+    ...
+}
+
+UEContextReleaseCommandIEs WIAP-PROTOCOL-IES ::= {
+    { ID id-ngenB-CU-UE-WIAP-ID      CRITICALITY reject  TYPE NGENB-CU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-ngenB-DU-UE-WIAP-ID      CRITICALITY reject  TYPE NGENB-DU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-Cause                  CRITICALITY ignore  TYPE Cause
+      PRESENCE mandatory  }|
+}
+
+```
+
+```
+
+    { ID id-RRCContainer          CRITICALITY ignore  TYPE RRCContainer
+    PRESENCE optional  }|
+    { ID id-SRBID               CRITICALITY ignore  TYPE SRBID
+    PRESENCE optional  }|
+    { ID id-oldngNB-DU-UE-W1AP-ID      CRITICALITY ignore  TYPE NGNB-DU-UE-W1AP-ID
+    PRESENCE optional  },
+    ...
+  }
+
+  -- *****
+  --
+  -- UE CONTEXT RELEASE COMPLETE
+  --
+  -- *****
+
+  UEContextReleaseComplete ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { { UEContextReleaseCompleteIEs} },
+    ...
+  }
+
+  UEContextReleaseCompleteIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngNB-CU-UE-W1AP-ID      CRITICALITY reject  TYPE NGNB-CU-UE-W1AP-ID
+    PRESENCE mandatory  }|
+    { ID id-ngNB-DU-UE-W1AP-ID      CRITICALITY reject  TYPE NGNB-DU-UE-W1AP-ID
+    PRESENCE mandatory  }|
+    { ID id-CriticalityDiagnostics      CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional  },
+    ...
+  }
+
+  -- *****
+  --
+  -- UE Context Modification ELEMENTARY PROCEDURE
+  --
+  -- *****
+
+  -- *****
+  --
+  -- UE CONTEXT MODIFICATION REQUEST
+  --
+  -- *****
+
+  UEContextModificationRequest ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      { { UEContextModificationRequestIEs} },
+    ...
+  }
+
+  UEContextModificationRequestIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngNB-CU-UE-W1AP-ID      CRITICALITY reject  TYPE NGNB-CU-UE-W1AP-ID
+    PRESENCE mandatory  }|
+    { ID id-ngNB-DU-UE-W1AP-ID      CRITICALITY reject  TYPE NGNB-DU-UE-W1AP-ID
+    PRESENCE mandatory  }|
+    { ID id-SpCell-ID      CRITICALITY ignore  TYPE EUTRANCGI
+    PRESENCE optional  }|
+    { ID id-ServCellIndex      CRITICALITY reject  TYPE ServCellIndex
+    PRESENCE optional  }|
+    { ID id-DRXCycle      CRITICALITY ignore  TYPE DRXCycle
+    PRESENCE optional  }|
+    { ID id-CUtoDURRCInformation      CRITICALITY reject  TYPE CUtoDURRCInformation
+    PRESENCE optional  }|
+    { ID id-TransmissionActionIndicator      CRITICALITY ignore  TYPE
+    TransmissionActionIndicator      PRESENCE optional  }|
+    { ID id-ResourceCoordinationTransferContainer      CRITICALITY ignore  TYPE
+    ResourceCoordinationTransferContainer      PRESENCE optional  }|
+    { ID id-RRCReconfigurationCompleteIndicator      CRITICALITY ignore  TYPE
+    RRCReconfigurationCompleteIndicator      PRESENCE optional  }|
+    { ID id-RRCContainer      CRITICALITY reject  TYPE RRCContainer
+    PRESENCE optional  }|
+    { ID id-SCell-ToBeSetupMod-List      CRITICALITY ignore  TYPE SCell-ToBeSetupMod-List
+    PRESENCE optional  }|
+    { ID id-SCell-ToBeRemoved-List      CRITICALITY ignore  TYPE SCell-ToBeRemoved-List
+    PRESENCE optional  }|
+    { ID id-SRBs-ToBeSetupMod-List      CRITICALITY reject  TYPE SRBs-ToBeSetupMod-List
+    PRESENCE optional  }|
+    { ID id-DRBs-ToBeSetupMod-List      CRITICALITY reject  TYPE DRBs-ToBeSetupMod-List
+    PRESENCE optional  }|
+  }
+
+```
+
+```
+
+    { ID id-DRBs-ToBeModified-List              CRITICALITY reject  TYPE DRBs-ToBeModified-List
+                        PRESENCE optional   }|
+    { ID id-SRBs-ToBeReleased-List              CRITICALITY reject  TYPE SRBs-ToBeReleased-List
+                        PRESENCE optional   }|
+    { ID id-DRBs-ToBeReleased-List              CRITICALITY reject  TYPE DRBs-ToBeReleased-List
+                        PRESENCE optional   }|
+    { ID id-InactivityMonitoringRequest         CRITICALITY reject  TYPE InactivityMonitoringRequest
+                        PRESENCE optional   }|
+    { ID id-NGENB-DU-UE-AMBR-UL                 CRITICALITY ignore  TYPE BitRate
+                        PRESENCE optional   }|
+    { ID id-RAT-FrequencyPriorityInformation    CRITICALITY reject  TYPE RAT-FrequencyPriorityInformation
+                        PRESENCE optional   }|
+    { ID id-ResourceCoordinationTransferInformation CRITICALITY ignore  TYPE ResourceCoordinationTransferInformation
+                        PRESENCE optional   }|
+    { ID id-SCGIndicator                        CRITICALITY ignore  TYPE SCGIndicator
+                        PRESENCE optional },
+    ...
+}
+
+SCell-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF SCell-ToBeSetupMod-Item
+
+SCell-ToBeRemoved-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF SCell-ToBeRemoved-Item
+
+SRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-ToBeSetupMod-Item
+
+DRBs-ToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-ToBeSetupMod-Item
+
+DRBs-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-ToBeModified-Item
+
+SRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-ToBeReleased-Item
+
+DRBs-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-ToBeReleased-Item
+
+-- **************************************************************
+--
+-- UE CONTEXT MODIFICATION RESPONSE
+--
+-- **************************************************************
+
+UEContextModificationResponse ::= SEQUENCE {
+    protocolIEs         ProtocolIE-Container        { { UEContextModificationResponseIEs} },
+    ...
+}
+
+UEContextModificationResponseIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngeNB-CU-UE-W1AP-ID                 CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+                        PRESENCE mandatory  }|
+    { ID id-ngeNB-DU-UE-W1AP-ID                 CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+                        PRESENCE mandatory  }|
+    { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore  TYPE ResourceCoordinationTransferContainer
+                        PRESENCE optional   }|
+    { ID id-DUtoCURRCInformation                CRITICALITY reject  TYPE DUtoCURRCInformation
+                        PRESENCE optional}|
+    { ID id-DRBs-SetupMod-List                  CRITICALITY ignore  TYPE DRBs-SetupMod-List
+                        PRESENCE optional}|
+    { ID id-DRBs-Modified-List                  CRITICALITY ignore  TYPE DRBs-Modified-List
+                        PRESENCE optional}|
+    { ID id-SRBs-FailedToBeSetupMod-List        CRITICALITY ignore  TYPE SRBs-FailedToBeSetupMod-List
+                        PRESENCE optional   }|
+    { ID id-DRBs-FailedToBeSetupMod-List        CRITICALITY ignore  TYPE DRBs-FailedToBeSetupMod-List
+                        PRESENCE optional   }|
+    { ID id-SCell-FailedtoSetupMod-List         CRITICALITY ignore  TYPE SCell-FailedtoSetupMod-List
+                        PRESENCE optional   }|
+    { ID id-DRBs-FailedToBeModified-List        CRITICALITY ignore  TYPE DRBs-FailedToBeModified-List
+                        PRESENCE optional   }|
+    { ID id-InactivityMonitoringResponse        CRITICALITY reject  TYPE InactivityMonitoringResponse
+                        PRESENCE optional   }|
+    { ID id-C-RNTI                              CRITICALITY ignore  TYPE C-RNTI
+                        PRESENCE optional   }|
+    { ID id-SRBs-SetupMod-List                  CRITICALITY ignore  TYPE SRBs-SetupMod-List
+                        PRESENCE optional   }|
+    { ID id-SRBs-Modified-List                  CRITICALITY ignore  TYPE SRBs-Modified-List
+                        PRESENCE optional   }|
+    { ID id-CriticalityDiagnostics              CRITICALITY ignore  TYPE CriticalityDiagnostics
+                        PRESENCE optional   },
+    ...
+}
+    
+```
+
+```
+
+}
+
+DRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-SetupMod-Item
+DRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-Modified-Item
+SRBs-SetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-SetupMod-Item
+SRBs-Modified-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-Modified-Item
+DRBs-FailedToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-FailedToBeModified-Item
+SRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-FailedToBeSetupMod-Item
+DRBs-FailedToBeSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-FailedToBeSetupMod-Item
+SCell-FailedtoSetupMod-List ::= SEQUENCE (SIZE(1..maxnoofSCells)) OF SCell-FailedtoSetupMod-Item
+
+-- ****************************************************************************
+--
+-- UE CONTEXT MODIFICATION FAILURE
+--
+-- ****************************************************************************
+
+UEContextModificationFailure ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { { UEContextModificationFailureIEs } },
+    ...
+}
+
+UEContextModificationFailureIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngenB-CU-UE-W1AP-ID          CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+      PRESENCE mandatory }|
+    { ID id-ngenB-DU-UE-W1AP-ID          CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+      PRESENCE mandatory }|
+    { ID id-Cause                        CRITICALITY ignore  TYPE Cause
+      PRESENCE mandatory }|
+    { ID id-CriticalityDiagnostics       CRITICALITY ignore  TYPE CriticalityDiagnostics
+      PRESENCE optional },
+    ...
+}
+
+-- ****************************************************************************
+--
+-- UE Context Modification Required (ngenB-DU initiated) ELEMENTARY PROCEDURE
+--
+-- ****************************************************************************
+
+-- ****************************************************************************
+--
+-- UE CONTEXT MODIFICATION REQUIRED
+--
+-- ****************************************************************************
+
+UEContextModificationRequired ::= SEQUENCE {
+    protocolIEs           ProtocolIE-Container      { { UEContextModificationRequiredIEs } },
+    ...
+}
+
+UEContextModificationRequiredIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngenB-CU-UE-W1AP-ID          CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+      PRESENCE mandatory }|
+    { ID id-ngenB-DU-UE-W1AP-ID          CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+      PRESENCE mandatory }|
+    { ID id-ResourceCoordinationTransferContainer      CRITICALITY ignore  TYPE
+      ResourceCoordinationTransferContainer      PRESENCE optional }|
+    { ID id-DUtoCURRCInformation      CRITICALITY reject  TYPE
+      DUtoCURRCInformation      PRESENCE optional }|
+    { ID id-DRBs-Required-ToBeModified-List      CRITICALITY reject  TYPE DRBs-Required-
+      ToBeModified-List      PRESENCE optional }|
+    { ID id-SRBs-Required-ToBeReleased-List      CRITICALITY reject  TYPE SRBs-Required-
+      ToBeReleased-List      PRESENCE optional }|
+    { ID id-DRBs-Required-ToBeReleased-List      CRITICALITY reject  TYPE DRBs-Required-
+      ToBeReleased-List      PRESENCE optional }|
+}
+
+```
+
+```
+
+        { ID id-Cause                      CRITICALITY ignore  TYPE Cause
+          PRESENCE mandatory },
+        ...
+    }
+
+    DRBs-Required-ToBeModified-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-Required-ToBeModified-
+    Item
+
+    DRBs-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-Required-ToBeReleased-
+    Item
+
+    SRBs-Required-ToBeReleased-List ::= SEQUENCE (SIZE(1..maxnoofSRBs)) OF SRBs-Required-ToBeReleased-
+    Item
+
+    -- ****************************************************************************
+    --
+    -- UE CONTEXT MODIFICATION CONFIRM
+    --
+    -- ****************************************************************************
+
+    UEContextModificationConfirm ::= SEQUENCE {
+        protocolIEs      ProtocolIE-Container      { { UEContextModificationConfirmIEs} },
+        ...
+    }
+
+    UEContextModificationConfirmIEs W1AP-PROTOCOL-IES ::= {
+        { ID id-ngenB-CU-UE-W1AP-ID                CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+          PRESENCE mandatory }|
+        { ID id-ngenB-DU-UE-W1AP-ID                CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+          PRESENCE mandatory }|
+        { ID id-ResourceCoordinationTransferContainer  CRITICALITY ignore  TYPE
+    ResourceCoordinationTransferContainer  PRESENCE optional }|
+        { ID id-DRBs-ModifiedConf-List                CRITICALITY ignore  TYPE DRBs-ModifiedConf-
+    List  PRESENCE optional}|
+        { ID id-RRContainer                        CRITICALITY ignore  TYPE RRContainer
+          PRESENCE optional }|
+        { ID id-ResourceCoordinationTransferInformation  CRITICALITY ignore  TYPE
+    ResourceCoordinationTransferInformation  PRESENCE optional }|
+        { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics
+          PRESENCE optional },
+        ...
+    }
+
+    DRBs-ModifiedConf-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRBs-ModifiedConf-Item
+
+    -- ****************************************************************************
+    --
+    -- UE CONTEXT MODIFICATION REFUSE
+    --
+    -- ****************************************************************************
+
+    UEContextModificationRefuse ::= SEQUENCE {
+        protocolIEs      ProtocolIE-Container      { { UEContextModificationRefuseIEs} },
+        ...
+    }
+
+    UEContextModificationRefuseIEs W1AP-PROTOCOL-IES ::= {
+        { ID id-ngenB-CU-UE-W1AP-ID                CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+          PRESENCE mandatory }|
+        { ID id-ngenB-DU-UE-W1AP-ID                CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+          PRESENCE mandatory }|
+        { ID id-Cause                      CRITICALITY ignore  TYPE Cause
+          PRESENCE mandatory }|
+        { ID id-CriticalityDiagnostics  CRITICALITY ignore  TYPE CriticalityDiagnostics
+          PRESENCE optional },
+        ...
+    }
+
+    -- ****************************************************************************
+    --
+    -- WRITE-REPLACE WARNING ELEMENTARY PROCEDURE
+    --
+    -- ****************************************************************************
+
+```
+
+```
+
+-- *****
+--
+-- Write-Replace Warning Request
+--
+-- *****
+
+WriteReplaceWarningRequest ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {WriteReplaceWarningRequestIEs} },
+  ...
+}
+
+WriteReplaceWarningRequestIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID          CRITICALITY reject  TYPE TransactionID
+    PRESENCE mandatory  }|
+  { ID id-PWSSystemInformation   CRITICALITY reject  TYPE PWSSystemInformation
+    PRESENCE mandatory }|
+  { ID id-RepetitionPeriod       CRITICALITY reject  TYPE RepetitionPeriod
+    PRESENCE mandatory }|
+  { ID id-NumberOfBroadcastRequest   CRITICALITY reject  TYPE NumberOfBroadcastRequest
+    PRESENCE mandatory }|
+  { ID id-Cells-To-Be-Broadcast-List   CRITICALITY reject  TYPE Cells-To-Be-Broadcast-List
+    PRESENCE optional  },
+  ...
+}
+
+Cells-To-Be-Broadcast-List ::= SEQUENCE (SIZE(1.. maxCellinngNBNU)) OF Cells-To-Be-Broadcast-Item
+
+-- *****
+--
+-- Write-Replace Warning Response
+--
+-- *****
+
+WriteReplaceWarningResponse ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {WriteReplaceWarningResponseIEs} },
+  ...
+}
+
+WriteReplaceWarningResponseIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID  CRITICALITY reject  TYPE TransactionID      PRESENCE mandatory  }|
+  { ID id-Cells-Broadcast-Completed-List   CRITICALITY reject  TYPE Cells-Broadcast-Completed-List
+    PRESENCE optional  }|
+  { ID id-CriticalityDiagnostics   CRITICALITY ignore  TYPE CriticalityDiagnostics
+    PRESENCE optional  },
+  ...
+}
+
+Cells-Broadcast-Completed-List ::= SEQUENCE (SIZE(1.. maxCellinngNBNU)) OF Cells-Broadcast-Completed-Item
+
+-- *****
+--
+-- PWS CANCEL ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- PWS Cancel Request
+--
+-- *****
+
+PWSCancelRequest ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {PWSCancelRequestIEs} },
+  ...
+}
+
+PWSCancelRequestIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID          CRITICALITY reject  TYPE TransactionID
+    PRESENCE mandatory  }|
+  { ID id-Broadcast-To-Be-Cancelled-List   CRITICALITY reject  TYPE Broadcast-To-Be-Cancelled-List
+    PRESENCE optional  }|
+  { ID id-Cancel-all-Warning-Messages-Indicator   CRITICALITY reject  TYPE Cancel-all-Warning-Messages-Indicator
+    PRESENCE optional  }|
+}
+
+```
+
+```
+
+    { ID id-NotificationInformation
+      PRESENCE mandatory },
+    CRITICALITY reject TYPE NotificationInformation
+  }
+  ...
+}
+
+Broadcast-To-Be-Cancelled-List := SEQUENCE (SIZE(1.. maxCellinngNBNU)) OF Broadcast-To-Be-
+Cancelled-Item
+
+-- *****
+--
+-- PWS Cancel Response
+--
+-- *****
+
+PWSCancelResponse := SEQUENCE {
+  protocolIEs ProtocolIE-Container { {PWSCancelResponseIEs} },
+  ...
+}
+
+PWSCancelResponseIEs WIAP-PROTOCOL-IES := {
+  { ID id-TransactionID
+    PRESENCE mandatory },
+  CRITICALITY reject TYPE TransactionID
+  { ID id-Cells-Broadcast-Cancelled-List
+    PRESENCE optional },
+  CRITICALITY reject TYPE Cells-Broadcast-Cancelled-List
+  { ID id-CriticalityDiagnostics
+    PRESENCE optional },
+  CRITICALITY ignore TYPE CriticalityDiagnostics
+  ...
+}
+
+Cells-Broadcast-Cancelled-List := SEQUENCE (SIZE(1.. maxCellinngNBNU)) OF Cells-Broadcast-
+Cancelled-Item
+
+-- *****
+--
+-- UE Inactivity Notification ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- UE Inactivity Notification
+--
+-- *****
+
+UEInactivityNotification := SEQUENCE {
+  protocolIEs ProtocolIE-Container { { UEInactivityNotificationIEs} },
+  ...
+}
+
+UEInactivityNotificationIEs WIAP-PROTOCOL-IES := {
+  { ID id-ngENB-CU-UE-WIAP-ID
+    PRESENCE mandatory },
+  CRITICALITY reject TYPE NGENB-CU-UE-WIAP-ID
+  { ID id-ngENB-DU-UE-WIAP-ID
+    PRESENCE mandatory },
+  CRITICALITY reject TYPE NGENB-DU-UE-WIAP-ID
+  { ID id-DRB-Activity-List
+    PRESENCE mandatory },
+  CRITICALITY reject TYPE DRB-Activity-List
+  ...
+}
+
+DRB-Activity-List := SEQUENCE (SIZE(1..maxnoofDRBs)) OF DRB-Activity-Item
+
+-- *****
+--
+-- Initial UL RRC Message Transfer ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- INITIAL UL RRC Message Transfer
+--
+-- *****
+
+InitialULRRCMessageTransfer := SEQUENCE {
+  protocolIEs ProtocolIE-Container { { InitialULRRCMessageTransferIEs} },
+  ...
+}
+
+```
+
+```
+
+}
+
+InitialULRRCMessageTransferIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngeNB-DU-UE-W1AP-ID      CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID      PRESENCE
+mandatory    }|
+    { ID id-EUTRANCGI                CRITICALITY reject  TYPE EUTRANCGI                PRESENCE mandatory  }|
+    { ID id-C-RNTI                   CRITICALITY reject  TYPE C-RNTI                   PRESENCE mandatory  }|
+    { ID id-RRCContainer             CRITICALITY reject  TYPE RRCContainer             PRESENCE mandatory  }|
+    { ID id-DUtoCURRCContainer       CRITICALITY reject  TYPE DUtoCURRCContainer       PRESENCE
+optional     }|
+    { ID id-TransactionID            CRITICALITY ignore  TYPE TransactionID            PRESENCE mandatory  },
+    ...
+}
+
+-- **************************************************************
+--
+-- DL RRC Message Transfer ELEMENTARY PROCEDURE
+--
+-- **************************************************************
+
+-- **************************************************************
+--
+-- DL RRC Message Transfer
+--
+-- **************************************************************
+
+DLRRCMessageTransfer ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      {{ DLRRCMessageTransferIEs}},
+    ...
+}
+
+DLRRCMessageTransferIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngeNB-CU-UE-W1AP-ID CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID      PRESENCE mandatory
+}| 
+    { ID id-ngeNB-DU-UE-W1AP-ID CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID      PRESENCE mandatory
+}| 
+    { ID id-oldngeNB-DU-UE-W1AP-ID                  CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+                                 PRESENCE optional  }|
+    { ID id-SRBID                                   CRITICALITY reject  TYPE SRBID
+                                 PRESENCE mandatory }|
+    { ID id-RRCContainer                            CRITICALITY reject  TYPE RRCContainer
+                                 PRESENCE mandatory },
+    ...
+}
+
+-- **************************************************************
+--
+-- UL RRC Message Transfer ELEMENTARY PROCEDURE
+--
+-- **************************************************************
+
+-- **************************************************************
+--
+-- UL RRC Message Transfer
+--
+-- **************************************************************
+
+ULRRCMessageTransfer ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container      {{ ULRRCMessageTransferIEs}},
+    ...
+}
+
+ULRRCMessageTransferIEs W1AP-PROTOCOL-IES ::= {
+    { ID id-ngeNB-CU-UE-W1AP-ID      CRITICALITY reject  TYPE NGENB-CU-UE-W1AP-ID
+      PRESENCE mandatory  }|
+    { ID id-ngeNB-DU-UE-W1AP-ID      CRITICALITY reject  TYPE NGENB-DU-UE-W1AP-ID
+      PRESENCE mandatory  }|
+    { ID id-SRBID                    CRITICALITY reject  TYPE SRBID
+      PRESENCE mandatory  }|
+    { ID id-RRCContainer             CRITICALITY reject  TYPE RRCContainer
+      PRESENCE mandatory  },
+    ...
+}
+
+-- **************************************************************
+--
+-- PRIVATE MESSAGE
+--
+-- **************************************************************
+
+```
+
+```
+
+-- *****
+
+PrivateMessage ::= SEQUENCE {
+    privateIEs      PrivateIE-Container {{PrivateMessage-IEs}},
+    ...
+}
+
+PrivateMessage-IEs WIAP-PRIVATE-IEs ::= {
+    ...
+}
+
+-- *****
+--
+-- Paging PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- Paging
+--
+-- *****
+
+Paging ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container {{ PagingIEs}},
+    ...
+}
+
+PagingIEs WIAP-PROTOCOL-IEs ::= {
+    { ID id-UEIdentityIndexValue      CRITICALITY reject      TYPE UEIdentityIndexValue      PRESENCE
+mandatory  }|
+    { ID id-PagingIdentity      CRITICALITY reject      TYPE PagingIdentity      PRESENCE
+mandatory  }|
+    { ID id-PagingDRX      CRITICALITY ignore      TYPE PagingDRX      PRESENCE
+optional  }|
+    { ID id-PagingCell-List      CRITICALITY ignore      TYPE PagingCell-list      PRESENCE
+mandatory  }|
+    { ID id-PagingOrigin      CRITICALITY ignore      TYPE PagingOrigin      PRESENCE
+optional  },
+    ...
+}
+
+PagingCell-list ::= SEQUENCE (SIZE(1.. maxnoofPagingCells)) OF PagingCell-Item
+
+-- *****
+--
+-- Notify
+--
+-- *****
+
+Notify ::= SEQUENCE {
+    protocolIEs      ProtocolIE-Container {{ NotifyIEs}},
+    ...
+}
+
+NotifyIEs WIAP-PROTOCOL-IEs ::= {
+    { ID id-ngeNB-CU-UE-WIAP-ID      CRITICALITY reject      TYPE NGENB-CU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-ngeNB-DU-UE-WIAP-ID      CRITICALITY reject      TYPE NGENB-DU-UE-WIAP-ID
+      PRESENCE mandatory  }|
+    { ID id-DRB-Notify-List      CRITICALITY reject      TYPE DRB-Notify-List
+      PRESENCE mandatory  },
+    ...
+}
+
+DRB-Notify-List ::= SEQUENCE (SIZE(1.. maxnoofDRBs)) OF DRB-Notify-Item
+
+-- *****
+--
+-- PWS RESTART INDICATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+```
+
+```
+
+-- *****
+--
+-- PWS Restart Indication
+--
+-- *****
+
+PWSRestartIndication ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { { PWSRestartIndicationIEs} },
+  ...
+}
+
+PWSRestartIndicationIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID CRITICALITY reject TYPE TransactionID
+    PRESENCE mandatory }|
+  { ID id-E-UTRAN-CGI-List-For-Restart-List CRITICALITY reject TYPE E-UTRAN-CGI-List-For-
+Restart-List PRESENCE mandatory },
+  ...
+}
+
+E-UTRAN-CGI-List-For-Restart-List ::= SEQUENCE (SIZE(1.. maxCellinngenBDU)) OF E-UTRAN-CGI-
+List-For-Restart-Item
+
+-- *****
+--
+-- PWS FAILURE INDICATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- PWS Failure Indication
+--
+-- *****
+
+PWSFailureIndication ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { { PWSFailureIndicationIEs} },
+  ...
+}
+
+PWSFailureIndicationIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE
+mandatory }|
+  { ID id-PWS-Failed-E-UTRAN-CGI-List CRITICALITY reject TYPE PWS-Failed-E-UTRAN-CGI-List
+    PRESENCE optional },
+  ...
+}
+
+PWS-Failed-E-UTRAN-CGI-List ::= SEQUENCE (SIZE(1.. maxCellinngenBDU)) OF PWS-Failed-E-UTRAN-
+CGI-Item
+
+-- *****
+--
+-- ngeNB-DU STATUS INDICATION ELEMENTARY PROCEDURE
+--
+-- *****
+
+-- *****
+--
+-- ngeNB-DU Status Indication
+--
+-- *****
+
+NGENBDUStatusIndication ::= SEQUENCE {
+  protocolIEs ProtocolIE-Container { {NGENBDUStatusIndicationIEs} },
+  ...
+}
+
+NGENBDUStatusIndicationIEs WIAP-PROTOCOL-IES ::= {
+  { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE
+mandatory }|
+  { ID id-NGENBDUOverloadInformation CRITICALITY reject TYPE NGENBDUOverloadInformation
+    PRESENCE mandatory },
+  ...
+}
+
+```
+
+```
+END
+-- ASN1STOP
+```
+
+## 9.4.5 Information Element Definitions
+
+```
+-- ASN1START
+-- *****
+--
+-- Information Element Definitions
+--
+-- *****
+```
+
+```
+W1AP-IEs {
+  itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+  ngran-access (22) modules (3) wlap (3) version1 (1) wlap-IEs (2) }
+```
+
+```
+DEFINITIONS AUTOMATIC TAGS ::=
+```
+
+```
+BEGIN
+```
+
+```
+IMPORTS
+```
+
+```
+  id-NotificationInformation,
+  id-AdditionalSIBMessageList,
+  id-PDCPTerminatingNodeDLTNLAddrInfo,
+  maxEARFCN,
+  maxnoofAdditionalSIBs,
+  maxnoofErrors,
+  maxnoofBPLMNs,
+  maxnoofDLUPNLInformation,
+  maxnoofE-UTRANCellBands,
+  maxnoofULUPNLInformation,
+  maxnoofQoSFlows,
+  maxnoofSliceItems,
+  maxnoofSIBTypes,
+  maxCellineNB,
+  maxnoofExtendedBPLMNs,
+  maxBandsEutra
+```
+
+```
+FROM W1AP-Constants
+```
+
+```
+  Criticality,
+  ProcedureCode,
+  ProtocolIE-ID,
+  TriggeringMessage
+```
+
+```
+FROM W1AP-CommonDataTypes
+```
+
+```
+  ProtocolExtensionContainer{},
+  W1AP-PROTOCOL-EXTENSION,
+  ProtocolIE-SingleContainer{},
+  W1AP-PROTOCOL-IEs
+```
+
+```
+FROM W1AP-Containers;
+```
+
+```
+-- A
+```
+
+```
+AdditionalSIBMessageList ::= SEQUENCE (SIZE(1..maxnoofAdditionalSIBs)) OF AdditionalSIBMessageList-Item
+```
+
+```
+AdditionalSIBMessageList-Item ::= SEQUENCE {
+  additionalSIB      OCTET STRING,
+  iE-Extensions      ProtocolExtensionContainer { { AdditionalSIBMessageList-Item-ExtIEs } }
+  OPTIONAL
+}
+```
+
+```
+AdditionalSIBMessageList-Item-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+```
+
+```
+AllocationAndRetentionPriority ::= SEQUENCE {
+  priorityLevel      PriorityLevel,
+  pre-emptionCapability  Pre-emptionCapability,
+  pre-emptionVulnerability  Pre-emptionVulnerability,
+  iE-Extensions      ProtocolExtensionContainer { {AllocationAndRetentionPriority-ExtIEs} } OPTIONAL,
+  ...
+}
+```
+
+```
+
+}
+
+AllocationAndRetentionPriority-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+AvailablePLMNList ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF AvailablePLMNList-Item
+
+AvailablePLMNList-Item ::= SEQUENCE {
+  pLMNIdentity          PLMN-Identity,
+  iE-Extensions         ProtocolExtensionContainer { { AvailablePLMNList-Item-ExtIEs} } OPTIONAL,
+  ...
+}
+
+AvailablePLMNList-Item-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+AveragingWindow ::= INTEGER (0..4095, ...)
+
+-- B
+
+BitRate ::= INTEGER (0..40000000000000, ...)
+
+BearerTypeChange ::= ENUMERATED {true, ...}
+
+BPLMN-ID-Info-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF BPLMN-ID-Info-Item
+
+BPLMN-ID-Info-Item ::= SEQUENCE {
+  pLMN-Identity-List      AvailablePLMNList,
+  fiveGS-TAC              FiveGS-TAC                OPTIONAL,
+  eUTRA-Cell-ID           EUTRA-Cell-ID,
+  ranac                     RANAC                     OPTIONAL,
+  iE-Extensions             ProtocolExtensionContainer { { BPLMN-ID-Info-ItemExtIEs} } OPTIONAL,
+  ...
+}
+
+BPLMN-ID-Info-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+Broadcast-To-Be-Cancelled-Item ::= SEQUENCE {
+  eUTRANCGI                 EUTRANCGI,
+  iE-Extensions             ProtocolExtensionContainer { { Broadcast-To-Be-Cancelled-ItemExtIEs } } OPTIONAL,
+  ...
+}
+
+Broadcast-To-Be-Cancelled-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+-- C
+
+Cancel-all-Warning-Messages-Indicator ::= ENUMERATED {true, ...}
+
+Candidate-SpCell-Item ::= SEQUENCE {
+  candidate-SpCell-ID       EUTRANCGI ,
+  iE-Extensions             ProtocolExtensionContainer { { Candidate-SpCell-ItemExtIEs } } OPTIONAL,
+  ...
+}
+
+Candidate-SpCell-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+Cause ::= CHOICE {
+  radioNetwork              CauseRadioNetwork,
+  transport                 CauseTransport,
+  protocol                  CauseProtocol,
+  misc                      CauseMisc,
+  choice-extension          ProtocolIE-SingleContainer { { Cause-ExtIEs} }
+}
+
+Cause-ExtIEs WIAP-PROTOCOL-IES ::= {
+  ...
+}
+
+```
+
+```
+CauseMisc ::= ENUMERATED {  
+    control-processing-overload,  
+    not-enough-user-plane-processing-resources,  
+    hardware-failure,  
+    om-intervention,  
+    unspecified,  
+    ...  
+}  
+  
+CauseProtocol ::= ENUMERATED {  
+    transfer-syntax-error,  
+    abstract-syntax-error-reject,  
+    abstract-syntax-error-ignore-and-notify,  
+    message-not-compatible-with-receiver-state,  
+    semantic-error,  
+    abstract-syntax-error-falsely-constructed-message,  
+    unspecified,  
+    ...  
+}  
+  
+CauseRadioNetwork ::= ENUMERATED {  
+    unspecified,  
+    rl-failure-rlc,  
+    unknown-or-already-allocated-enb-cu-ue-wlap-id,  
+    unknown-or-already-allocated-enb-du-ue-wlap-id,  
+    unknown-or-inconsistent-pair-of-ue-wlap-id,  
+    interaction-with-other-procedure,  
+    not-supported-qci-Value,  
+    action-desirable-for-radio-reasons,  
+    no-radio-resources-available,  
+    procedure-cancelled,  
+    normal-release,  
+    cell-not-available,  
+    rl-failure-others,  
+    ue-rejection,  
+    resources-not-available-for-the-slice,  
+    amf-initiated-abnormal-release,  
+    release-due-to-pre-emption,  
+    multiple-drb-id-instances,  
+    unknown-drb-id,  
+    ...  
+}  
+  
+CauseTransport ::= ENUMERATED {  
+    unspecified,  
+    transport-resource-unavailable,  
+    ...  
+}  
+  
+Cells-Failed-to-be-Activated-List-Item ::= SEQUENCE {  
+    eUTRANCGI           EUTRANCGI,  
+    cause               Cause,  
+    iE-Extensions       ProtocolExtensionContainer { { Cells-Failed-to-be-Activated-List-  
+    ItemExtIEs } } OPTIONAL,  
+    ...  
+}  
+  
+Cells-Failed-to-be-Activated-List-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Cells-Status-Item ::= SEQUENCE {  
+    eUTRANCGI           EUTRANCGI,  
+    service-status      Service-Status,  
+    iE-Extensions       ProtocolExtensionContainer { { Cells-Status-ItemExtIEs } } OPTIONAL,  
+    ...  
+}  
+  
+Cells-Status-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+Cells-To-Be-Broadcast-Item ::= SEQUENCE {  
+    eUTRANCGI           EUTRANCGI,
+```
+
+```
+
+    iE-Extensions      ProtocolExtensionContainer { { Cells-To-Be-Broadcast-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Cells-To-Be-Broadcast-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Cells-Broadcast-Completed-Item ::= SEQUENCE {
+    eUTRANCGI      EUTRANCGI,
+    iE-Extensions  ProtocolExtensionContainer { { Cells-Broadcast-Completed-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Cells-Broadcast-Completed-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Cells-Broadcast-Cancelled-Item ::= SEQUENCE {
+    eUTRANCGI      EUTRANCGI,
+    numberOfBroadcasts  NumberOfBroadcasts,
+    iE-Extensions  ProtocolExtensionContainer { { Cells-Broadcast-Cancelled-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Cells-Broadcast-Cancelled-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Cells-to-be-Activated-List-Item ::= SEQUENCE {
+    eUTRANCGI      EUTRANCGI,
+    eUTRANPCI      EUTRANPCI,
+    ngeNB-CUSystemInformation  NGENB-CUSystemInformation,
+    availablePLMNList  AvailablePLMNList,
+    extendedAvailablePLMN-List  ExtendedAvailablePLMN-List,
+    iE-Extensions  ProtocolExtensionContainer { { Cells-to-be-Activated-List-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Cells-to-be-Activated-List-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Cells-to-be-Deactivated-List-Item ::= SEQUENCE {
+    eUTRANCGI      EUTRANCGI,
+    iE-Extensions  ProtocolExtensionContainer { { Cells-to-be-Deactivated-List-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Cells-to-be-Deactivated-List-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Cell-Type ::= ENUMERATED {
+    verysmall,
+    small,
+    medium,
+    large,
+    ...
+}
+
+CNUEPagingIdentity ::= CHOICE {
+    fiveG-S-TMSI  BIT STRING (SIZE(48)),
+    choice-extension  ProtocolIE-SingleContainer { { CNUEPagingIdentity-ExtIEs } }
+}
+
+CNUEPagingIdentity-ExtIEs WIAP-PROTOCOL-IES ::= {
+    ...
+}
+
+CriticalityDiagnostics ::= SEQUENCE {
+    procedureCode  ProcedureCode,
+    triggeringMessage  TriggeringMessage,
+}
+
+```
+
+```
+
+    procedureCriticality      Criticality                      OPTIONAL,
+    transactionID             TransactionID                    OPTIONAL,
+    iEsCriticalityDiagnostics   CriticalityDiagnostics-IE-List OPTIONAL,
+    iE-Extensions             ProtocolExtensionContainer {{CriticalityDiagnostics-ExtIEs}}
+    OPTIONAL,
+    ...
+}
+
+CriticalityDiagnostics-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1.. maxnoofErrors)) OF CriticalityDiagnostics-IE-Item
+
+CriticalityDiagnostics-IE-Item ::= SEQUENCE {
+    iECriticality             Criticality,
+    iE-ID                     ProtocolIE-ID,
+    typeOfError               TypeOfError,
+    iE-Extensions             ProtocolExtensionContainer {{CriticalityDiagnostics-IE-Item-ExtIEs}}
+    OPTIONAL,
+    ...
+}
+
+CriticalityDiagnostics-IE-Item-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+C-RNTI ::= INTEGER (0..65535, ...)
+
+CUtoDURRCInformation ::= SEQUENCE {
+    cG-ConfigInfo             CG-ConfigInfo                      OPTIONAL,
+    uE-CapabilityRAT-ContainerList   UE-CapabilityRAT-ContainerList OPTIONAL,
+    measConfig                MeasConfig                       OPTIONAL,
+    handoverPreparationInformation   HandoverPreparationInformation OPTIONAL,
+    radioResourceConfigDedicated   RadioResourceConfigDedicated OPTIONAL,
+    measurementTimingConfiguration   MeasurementTimingConfiguration OPTIONAL,
+    uEAssistanceInformation   UEAssistanceInformation          OPTIONAL,
+    requestedP-MaxFR1         OCTET STRING                     OPTIONAL,
+    iE-Extensions             ProtocolExtensionContainer { { CUtoDURRCInformation-ExtIEs } } OPTIONAL,
+    ...
+}
+
+CUtoDURRCInformation-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+-- D
+
+DLUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE (1..maxnoofDLUPTNLInformation)) OF DLUPTNLInformation-ToBeSetup-Item
+
+DLUPTNLInformation-ToBeSetup-Item ::= SEQUENCE {
+    dLUPTNLInformation   UPTransportLayerInformation ,
+    iE-Extensions        ProtocolExtensionContainer { { DLUPTNLInformation-ToBeSetup-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+DLUPTNLInformation-ToBeSetup-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRB-Activity-Item ::= SEQUENCE {
+    dRBID                dRBID,
+    dRB-Activity           dRB-Activity                      OPTIONAL,
+    iE-Extensions          ProtocolExtensionContainer { { DRB-Activity-ItemExtIEs } } OPTIONAL,
+    ...
+}
+
+DRB-Activity-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRB-Activity ::= ENUMERATED {active, not-active}
+
+```
+
+```
+DRBID ::= INTEGER (1..32, ...)
+
+DRBs-FailedToBeModified-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    cause      Cause      OPTIONAL,
+    iE-Extensions  ProtocolExtensionContainer { { DRBs-FailedToBeModified-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+DRBs-FailedToBeModified-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRBs-FailedToBeSetup-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    cause      Cause      OPTIONAL,
+    iE-Extensions  ProtocolExtensionContainer { { DRBs-FailedToBeSetup-ItemExtIEs } }  OPTIONAL,
+    ...
+}
+
+DRBs-FailedToBeSetup-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRBs-FailedToBeSetupMod-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    cause      Cause      OPTIONAL,
+    iE-Extensions  ProtocolExtensionContainer { { DRBs-FailedToBeSetupMod-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+DRBs-FailedToBeSetupMod-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRB-Information ::= SEQUENCE {
+    dRB-QoS      QoSFlowLevelQoSParameters,
+    sNSSAI      SNSSAI,
+    notificationControl  NotificationControl  OPTIONAL,
+    flows-Mapped-To-DRB-List  Flows-Mapped-To-DRB-List,
+    iE-Extensions  ProtocolExtensionContainer { { DRB-Information-ItemExtIEs } }  OPTIONAL
+}
+
+DRB-Information-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRBs-Modified-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    dLUPTNLInformation-ToBeSetup-List  dLUPTNLInformation-ToBeSetup-List,
+    rLC-Status  RLC-Status  OPTIONAL,
+    iE-Extensions  ProtocolExtensionContainer { { DRBs-Modified-ItemExtIEs } }  OPTIONAL,
+    ...
+}
+
+DRBs-Modified-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRBs-ModifiedConf-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    uLUPTNLInformation-ToBeSetup-List  uLUPTNLInformation-ToBeSetup-List,
+    iE-Extensions  ProtocolExtensionContainer { { DRBs-ModifiedConf-ItemExtIEs } }  OPTIONAL,
+    ...
+}
+
+DRBs-ModifiedConf-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRB-Notify-Item ::= SEQUENCE {
+    dRBID      dRBID,
+    notification-Cause  Notification-Cause,
+    iE-Extensions  ProtocolExtensionContainer { { DRB-Notify-ItemExtIEs } }  OPTIONAL,
+    ...
+}
+```
+
+```
+}  
+  
+DRB-Notify-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-Required-ToBeModified-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  dLUPTNLInformation-ToBeSetup-List   dLUPTNLInformation-ToBeSetup-List,  
+  rLC-Status          rLC-Status          OPTIONAL,  
+  iE-Extensions   ProtocolExtensionContainer { { DRBs-Required-ToBeModified-ItemExtIEs } }  
+  OPTIONAL,  
+  ...  
+}  
+  
+DRBs-Required-ToBeModified-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-Required-ToBeReleased-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  iE-Extensions   ProtocolExtensionContainer { { DRBs-Required-ToBeReleased-ItemExtIEs } }  
+  OPTIONAL,  
+  ...  
+}  
+  
+DRBs-Required-ToBeReleased-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-Setup-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  dLUPTNLInformation-ToBeSetup-List   dLUPTNLInformation-ToBeSetup-List,  
+  iE-Extensions   ProtocolExtensionContainer { { DRBs-Setup-ItemExtIEs } }  OPTIONAL,  
+  ...  
+}  
+  
+DRBs-Setup-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-SetupMod-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  dLUPTNLInformation-ToBeSetup-List   dLUPTNLInformation-ToBeSetup-List,  
+  iE-Extensions   ProtocolExtensionContainer { { DRBs-SetupMod-ItemExtIEs } } OPTIONAL,  
+  ...  
+}  
+  
+DRBs-SetupMod-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-ToBeModified-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  qoSInformation          QoSInformation          OPTIONAL,  
+  uLUPTNLInformation-ToBeSetup-List   uLUPTNLInformation-ToBeSetup-List,  
+  dLPDCPSNLength          PDCPSNLength          OPTIONAL,  
+  uLPDCPSNLength          PDCPSNLength          OPTIONAL,  
+  bearerTypeChange          BearerTypeChange      OPTIONAL,  
+  rLCMode                 RLCMode               OPTIONAL,  
+  iE-Extensions           ProtocolExtensionContainer { { DRBs-ToBeModified-  
+  ItemExtIEs } } OPTIONAL,  
+  ...  
+}  
+  
+DRBs-ToBeModified-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+DRBs-ToBeReleased-Item ::= SEQUENCE {  
+  dRBID           DRBID,  
+  iE-Extensions   ProtocolExtensionContainer { { DRBs-ToBeReleased-ItemExtIEs } } OPTIONAL,  
+  ...  
+}  
+  
+DRBs-ToBeReleased-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}
+```
+
+```
+
+}
+
+DRBs-ToBeSetup-Item ::= SEQUENCE {
+    dRBID                 dRBID,
+    qosInformation        QoSInformation,
+    uLUPTNLInformation-ToBeSetup-List   ULUPTNLInformation-ToBeSetup-List,
+    rLCMode               RLCMode,
+    dLPDCPSNLength        PDCPSNLength,
+    uLPDCPSNLength        PDCPSNLength            OPTIONAL,
+    iE-Extensions         ProtocolExtensionContainer { { DRBs-ToBeSetup-ItemExtIEs } } OPTIONAL,
+    ...
+}
+
+DRBs-ToBeSetup-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRBs-ToBeSetupMod-Item ::= SEQUENCE {
+    dRBID                 dRBID,
+    qosInformation        QoSInformation,
+    uLUPTNLInformation-ToBeSetup-List   ULUPTNLInformation-ToBeSetup-List,
+    rLCMode               RLCMode,
+    dLPDCPSNLength        PDCPSNLength            OPTIONAL,
+    uLPDCPSNLength        PDCPSNLength            OPTIONAL,
+    iE-Extensions         ProtocolExtensionContainer { { DRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL,
+    ...
+}
+
+DRBs-ToBeSetupMod-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRXCycle ::= SEQUENCE {
+    longDRXCycleLength    LongDRXCycleLength,
+    shortDRXCycleLength   ShortDRXCycleLength     OPTIONAL,
+    shortDRXCycleTimer    ShortDRXCycleTimer      OPTIONAL,
+    iE-Extensions         ProtocolExtensionContainer { { DRXCycle-ExtIEs } } OPTIONAL,
+    ...
+}
+
+DRXCycle-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+DRX-Config ::= OCTET STRING
+
+DRX-LongCycleStartOffset ::= INTEGER (0..10239)
+
+DUtoCURRCCContainer ::= OCTET STRING
+
+DUtoCURRCInformation ::= SEQUENCE {
+    radioResourceConfigDedicated    RadioResourceConfigDedicated,
+    measGapConfig                 MeasGapConfig            OPTIONAL,
+    requestedP-MaxFR1             OCTET STRING           OPTIONAL,
+    dRX-LongCycleStartOffset      DRX-LongCycleStartOffset OPTIONAL,
+    selectedBandCombinationIndex  SelectedBandCombinationIndex OPTIONAL,
+    selectedFeatureSetEntryIndex  SelectedFeatureSetEntryIndex OPTIONAL,
+    ph-InfoSCG                    Ph-InfoSCG             OPTIONAL,
+    requestedBandCombinationIndex RequestedBandCombinationIndex OPTIONAL,
+    requestedFeatureSetEntryIndex RequestedFeatureSetEntryIndex OPTIONAL,
+    dRX-Config                    DRX-Config             OPTIONAL,
+    iE-Extensions                 ProtocolExtensionContainer { { DUtoCURRCInformation-ExtIEs } } OPTIONAL,
+    ...
+}
+
+DUtoCURRCInformation-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    {ID id-MeasGapSharingConfig    CRITICALITY ignore    EXTENSION MeasGapSharingConfig    PRESENCE optional},
+    ...
+}
+
+Dynamic5QIDescriptor ::= SEQUENCE {
+    qosPriorityLevel            INTEGER (1..127),
+    packetDelayBudget           PacketDelayBudget,
+    packetErrorRate             PacketErrorRate,
+}
+
+```
+
+```
+
+        fiveQI                INTEGER (0..255, ...)           OPTIONAL,
+        delayCritical           ENUMERATED {delay-critical, non-delay-critical} OPTIONAL,
+        averagingWindow         AveragingWindow                 OPTIONAL,
+        maxDataBurstVolume      MaxDataBurstVolume              OPTIONAL,
+        iE-Extensions           ProtocolExtensionContainer { { Dynamic5QIDescriptor-ExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+Dynamic5QIDescriptor-ExtIEs WLAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+-- E
+
+Endpoint-IP-address-and-port ::= SEQUENCE {
+    endpointIPAddress           TransportLayerAddress,
+    iE-Extensions               ProtocolExtensionContainer { { Endpoint-IP-address-and-port-ExtIEs } } OPTIONAL,
+    ...
+}
+
+Endpoint-IP-address-and-port-ExtIEs WLAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+EUTRA-Cell-ID ::= BIT STRING (SIZE(28))
+
+EUTRA-Coex-FDD-Info ::= SEQUENCE {
+    uL-EUTRAARFCN               ExtendedEARFCN                OPTIONAL,
+    dL-EUTRAARFCN               ExtendedEARFCN,
+    uL-Transmission-Bandwidth   EUTRA-Transmission-Bandwidth OPTIONAL,
+    dL-Transmission-Bandwidth   EUTRA-Transmission-Bandwidth,
+    iE-Extensions               ProtocolExtensionContainer { {EUTRA-Coex-FDD-Info-ExtIEs} }
+    OPTIONAL,
+    ...
+}
+
+EUTRA-Coex-FDD-Info-ExtIEs WLAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+EUTRA-Coex-Mode-Info ::= CHOICE {
+    fDD           EUTRA-Coex-FDD-Info,
+    tDD           EUTRA-Coex-TDD-Info,
+    ...
+}
+
+EUTRA-Coex-TDD-Info ::= SEQUENCE {
+    eARFCN                    ExtendedEARFCN,
+    transmission-Bandwidth    EUTRA-Transmission-Bandwidth,
+    subframeAssignment        EUTRA-SubframeAssignment,
+    specialSubframe-Info      EUTRA-SpecialSubframe-Info,
+    iE-Extensions             ProtocolExtensionContainer { {EUTRA-Coex-TDD-Info-ExtIEs} }
+    OPTIONAL,
+    ...
+}
+
+EUTRA-Coex-TDD-Info-ExtIEs WLAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+EUTRA-CyclicPrefixDL ::= ENUMERATED {
+    normal,
+    extended,
+    ...
+}
+
+EUTRA-CyclicPrefixUL ::= ENUMERATED {
+    normal,
+    extended,
+    ...
+}
+
+EUTRA-PRACH-Configuration ::= SEQUENCE {
+    rootSequenceIndex           INTEGER (0..837),
+    zeroCorrelationIndex        INTEGER (0..15),
+    highSpeedFlag               BOOLEAN,
+}
+
+```
+
+```
+
+        prach-FreqOffset          INTEGER (0..94),
+        prach-ConfigIndex         INTEGER (0..63)      OPTIONAL, -- present for TDD --
+        iE-Extensions             ProtocolExtensionContainer { {EUTRA-PRACH-Configuration-
+ExtIEs} }      OPTIONAL,
+        ...
+    }
+
+    EUTRA-PRACH-Configuration-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    EUTRA-SpecialSubframe-Info ::= SEQUENCE {
+        specialSubframePatterns     EUTRA-SpecialSubframePatterns,
+        cyclicPrefixDL              EUTRA-CyclicPrefixDL,
+        cyclicPrefixUL              EUTRA-CyclicPrefixUL,
+        iE-Extensions               ProtocolExtensionContainer { { EUTRA-SpecialSubframe-Info-ExtIEs} }
+    OPTIONAL,
+        ...
+    }
+
+    EUTRA-SpecialSubframe-Info-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    EUTRA-SpecialSubframePatterns ::= ENUMERATED {
+        ssp0,
+        ssp1,
+        ssp2,
+        ssp3,
+        ssp4,
+        ssp5,
+        ssp6,
+        ssp7,
+        ssp8,
+        ssp9,
+        ssp10,
+        ...
+    }
+
+    EUTRA-SubframeAssignment ::= ENUMERATED {
+        sa0,
+        sa1,
+        sa2,
+        sa3,
+        sa4,
+        sa5,
+        sa6,
+        ...
+    }
+
+    EUTRA-Transmission-Bandwidth ::= ENUMERATED {
+        bw1,
+        bw6,
+        bw15,
+        bw25,
+        bw50,
+        bw75,
+        bw100,
+        ...
+    }
+
+    EUTRANQoS ::= SEQUENCE {
+        qCI                         QCI,
+        allocationAndRetentionPriority AllocationAndRetentionPriority,
+        gbrQoSInformation             GBR-QoSInformation      OPTIONAL,
+        iE-Extensions                 ProtocolExtensionContainer { { EUTRANQoS-ExtIEs} } OPTIONAL,
+        ...
+    }
+
+    EUTRANQoS-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    ExtendedEARFCN ::= INTEGER (0..maxEARFCN)
+
+    EUTRA-NR-CellResourceCoordinationReq-Container ::= OCTET STRING
+
+```
+
+```
+EUTRA-NR-CellResourceCoordinationReqAck-Container := OCTET STRING
+
+EUTRAFreqInfo := SEQUENCE {
+    eARFCN          INTEGER (0..maxEARFCN),
+    freqBandListEutra  SEQUENCE (SIZE(1.. maxnoofE-UTRANCellBands)) OF FreqBandEutraItem,
+    iE-Extensions  ProtocolExtensionContainer { { EUTRAFreqInfoExtIEs} } OPTIONAL,
+    ...
+}
+
+EUTRAFreqInfoExtIEs  W1AP-PROTOCOL-EXTENSION := {
+    ...
+}
+
+EUTRANCGI := SEQUENCE {
+    pLMN-Identity      PLMN-Identity,
+    eUTRANCellIdentity  E-UTRANCellIdentity,
+    iE-Extensions      ProtocolExtensionContainer { {EUTRANCGI-ExtIEs} } OPTIONAL,
+    ...
+}
+
+EUTRANCGI-ExtIEs  W1AP-PROTOCOL-EXTENSION := {
+    ...
+}
+
+E-UTRAN-Mode-Info := CHOICE {
+    fDD  FDD-Info,
+    tDD  TDD-Info,
+    choice-extension  ProtocolIE-SingleContainer { { E-UTRAN-Mode-Info-ExtIEs} }
+}
+
+E-UTRAN-Mode-Info-ExtIEs  W1AP-PROTOCOL-IES := {
+    ...
+}
+
+E-UTRANCellIdentity := BIT STRING (SIZE(28))
+
+EUTRANPCI := INTEGER (0..503)
+
+E-UTRAN-CGI-List-For-Restart-Item := SEQUENCE {
+    eUTRANCGI          EUTRANCGI,
+    iE-Extensions      ProtocolExtensionContainer { { E-UTRAN-CGI-List-For-Restart-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+E-UTRAN-CGI-List-For-Restart-ItemExtIEs  W1AP-PROTOCOL-EXTENSION := {
+    ...
+}
+
+ExtendedAvailablePLMN-List := SEQUENCE (SIZE(1..maxnoofExtendedBPLMNs)) OF ExtendedAvailablePLMN-
+Item
+
+ExtendedAvailablePLMN-Item := SEQUENCE {
+    pLMNIdentity      PLMN-Identity,
+    iE-Extensions      ProtocolExtensionContainer { { ExtendedAvailablePLMN-Item-ExtIEs} } OPTIONAL
+}
+
+ExtendedAvailablePLMN-Item-ExtIEs  W1AP-PROTOCOL-EXTENSION := {
+    ...
+}
+
+-- F
+
+FDD-Info := SEQUENCE {
+    uL-EUTRAFreqInfo      EUTRAFreqInfo,
+    dL-EUTRAFreqInfo      EUTRAFreqInfo,
+    uL-Transmission-Bandwidth  Transmission-Bandwidth,
+    dL-Transmission-Bandwidth  Transmission-Bandwidth,
+    iE-Extensions      ProtocolExtensionContainer { {FDD-Info-ExtIEs} } OPTIONAL,
+    ...
+}
+
+FDD-Info-ExtIEs  W1AP-PROTOCOL-EXTENSION := {
+    ...
+}
+```
+
+```
+
+Flows-Mapped-To-DRB-List      ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF Flows-Mapped-To-DRB-Item
+
+Flows-Mapped-To-DRB-Item      ::= SEQUENCE {
+    qosFlowIdentifier           QoSFlowIdentifier,
+    qosFlowLevelQoSParameters   QoSFlowLevelQoSParameters,
+    qosFlowMappingIndication    QoSFlowMappingIndication OPTIONAL,
+    iE-Extensions               ProtocolExtensionContainer { { Flows-Mapped-To-DRB-ItemExtIEs} } OPTIONAL,
+    ...
+}
+
+Flows-Mapped-To-DRB-ItemExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+FreqBandEutraItem ::= SEQUENCE {
+    freqBandIndicatorEutra    INTEGER (1.. maxBandsEutra),
+    iE-Extensions             ProtocolExtensionContainer { { FreqBandEutraItem-ExtIEs} } OPTIONAL,
+    ...
+}
+
+FreqBandEutraItem-ExtIEs    W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+-- G
+
+GBR-QosInformation ::= SEQUENCE {
+    e-RAB-MaximumBitrateDL    BitRate,
+    e-RAB-MaximumBitrateUL    BitRate,
+    e-RAB-GuaranteedBitrateDL BitRate,
+    e-RAB-GuaranteedBitrateUL BitRate,
+    iE-Extensions             ProtocolExtensionContainer { { GBR-QosInformation-ExtIEs} } OPTIONAL,
+    ...
+}
+
+GBR-QosInformation-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+GBR-QoSFlowInformation ::= SEQUENCE {
+    maxFlowBitRateDownlink    BitRate,
+    maxFlowBitRateUplink      BitRate,
+    guaranteedFlowBitRateDownlink BitRate,
+    guaranteedFlowBitRateUplink BitRate,
+    maxPacketLossRateDownlink   MaxPacketLossRate OPTIONAL,
+    maxPacketLossRateUplink     MaxPacketLossRate OPTIONAL,
+    iE-Extensions             ProtocolExtensionContainer { { GBR-QoSFlowInformation-ExtIEs} } OPTIONAL,
+    ...
+}
+
+GBR-QoSFlowInformation-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+NGENB-CUSystemInformation ::= SEQUENCE {
+    sibtypetobeupdatedlist  SEQUENCE (SIZE(1.. maxnoofSIBTypes)) OF SibtypetobeupdatedListItem,
+    iE-Extensions           ProtocolExtensionContainer { { NGENB-CUSystemInformation-ExtIEs} } OPTIONAL,
+    ...
+}
+
+NGENB-CUSystemInformation-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+NGENB-CU-UE-W1AP-ID ::= INTEGER (0..4294967295)
+
+NGENB-DU-UE-W1AP-ID ::= INTEGER (0..4294967295)
+
+NGENB-DU-ID ::= INTEGER (0..68719476735)
+
+```
+
+```
+NGENB-DU-Served-Cells-Item ::= SEQUENCE {  
+    served-Cell-Information    Served-Cell-Information,  
+    ngeNB-DU-System-Information    NGENB-DU-System-Information    OPTIONAL,  
+    iE-Extensions                ProtocolExtensionContainer { { NGENB-DU-Served-Cells-ItemExtIEs} }  
+    OPTIONAL,  
+    ...  
+}  
+  
+NGENB-DU-Served-Cells-ItemExtIEs    WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+NGENB-DU-System-Information ::= SEQUENCE {  
+    mIB-message                MIB-message,  
+    sIB1-message                SIB1-message,  
+    sIB2-message                SIB2-message,  
+    sIB3-message                SIB3-message,  
+    sIB8-message                SIB8-message,  
+    sIB16-message                SIB16-message,  
+    iE-Extensions                ProtocolExtensionContainer { { NGENB-DU-System-Information-  
+    ExtIEs } } OPTIONAL,  
+    ...  
+}  
+  
+NGENB-DU-System-Information-ExtIEs    WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+NGENBDUOverloadInformation ::= ENUMERATED {overloaded, not-overloaded}  
+  
+GTP-TEID                ::= OCTET STRING (SIZE (4))  
+  
+GTPTunnel                ::= SEQUENCE {  
+    transportLayerAddress        TransportLayerAddress,  
+    gTP-TEID                GTP-TEID,  
+    iE-Extensions                ProtocolExtensionContainer { { GTPTunnel-ExtIEs } } OPTIONAL,  
+    ...  
+}  
+  
+GTPTunnel-ExtIEs    WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+-- H  
+  
+HandoverPreparationInformation ::= OCTET STRING  
+  
+-- I  
+IgnoreResourceCoordinationRequestContainer ::= ENUMERATED { true,...}  
+  
+InactivityMonitoringRequest ::= ENUMERATED { true,...}  
+  
+InactivityMonitoringResponse ::= ENUMERATED { not-supported,...}  
+  
+-- J  
+  
+-- K  
+  
+-- L  
+  
+LongDRXCycleLength ::= ENUMERATED  
+{ms10, ms20, ms32, ms40, ms60, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280,  
+ms2048, ms2560,...}  
+  
+-- M  
+  
+MaxDataBurstVolume ::= INTEGER (0..4095,...)  
+  
+MaxPacketLossRate ::= INTEGER (0..1000)  
+  
+MIB-message ::= OCTET STRING  
+  
+MeasConfig ::= OCTET STRING  
+  
+MeasGapConfig ::= OCTET STRING  
+  
+MeasGapSharingConfig ::= OCTET STRING
+```
+
+```
+
+MeasurementTimingConfiguration ::= OCTET STRING
+
+MessageIdentifier ::= BIT STRING (SIZE (16))
+
+-- N
+
+NGRANAllocationAndRetentionPriority ::= SEQUENCE {
+    priorityLevel           PriorityLevel,
+    pre-emptionCapability Pre-emptionCapability,
+    pre-emptionVulnerability Pre-emptionVulnerability,
+    iE-Extensions           ProtocolExtensionContainer { {NGRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL,
+    ...
+}
+
+NGRANAllocationAndRetentionPriority-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+NonDynamic5QIDescriptor ::= SEQUENCE {
+    fiveQI                INTEGER (0..255,...),
+    qosPriorityLevel        INTEGER (1..127)           OPTIONAL,
+    averagingWindow         AveragingWindow            OPTIONAL,
+    maxDataBurstVolume    MaxDataBurstVolume         OPTIONAL,
+    iE-Extensions           ProtocolExtensionContainer { { NonDynamic5QIDescriptor-ExtIEs } } OPTIONAL,
+    ...
+}
+
+NonDynamic5QIDescriptor-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+Notification-Cause ::= ENUMERATED {fulfilled, not-fulfilled,...}
+
+NotificationControl ::= ENUMERATED {active, not-active,...}
+
+NotificationInformation ::= SEQUENCE {
+    message-Identifier    MessageIdentifier,
+    serialNumber          SerialNumber,
+    iE-Extensions         ProtocolExtensionContainer { { NotificationInformationExtIEs} } OPTIONAL,
+    ...
+}
+
+NotificationInformationExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+NumberOfBroadcasts ::= INTEGER (0..65535)
+
+NumberOfBroadcastRequest ::= INTEGER (0..65535)
+
+-- O
+
+-- P
+
+PacketDelayBudget ::= INTEGER (0..1023,...)
+
+PacketErrorRate ::= SEQUENCE {
+    pER-Scalar          PER-Scalar,
+    pER-Exponent        PER-Exponent,
+    iE-Extensions       ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL,
+    ...
+}
+
+PacketErrorRate-ExtIEs W1AP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+PER-Scalar ::= INTEGER (0..9,...)
+PER-Exponent ::= INTEGER (0..9,...)
+
+PagingCell-Item ::= SEQUENCE {
+    eUTRANCGI         EUTRANCGI,
+}
+
+```
+
+```
+    iE-Extensions   ProtocolExtensionContainer { { PagingCell-ItemExtIEs } }   OPTIONAL,  
+    ...  
+}  
+  
+PagingCell-ItemExtIEs   WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+PagingDRX ::= ENUMERATED {  
+    v32,  
+    v64,  
+    v128,  
+    v256,  
+    ...  
+}  
+  
+PagingIdentity ::= CHOICE {  
+    rANUEPagingIdentity RANUEPagingIdentity,  
+    cNUEPagingIdentity CNUEPagingIdentity,  
+    choice-extension      ProtocolIE-SingleContainer { { PagingIdentity-ExtIEs } }  
+}  
+  
+PagingIdentity-ExtIEs WIAP-PROTOCOL-IES ::= {  
+    ...  
+}  
+  
+PagingOrigin ::= ENUMERATED { non-3gpp, ... }  
+  
+PDCP-SN ::= INTEGER (0..4095)  
+  
+PDCPSNLength   ::= ENUMERATED { twelve-bits, eighteen-bits, ... }  
+  
+PDUSessionID ::= INTEGER (0..255)  
+  
+Ph-InfoSCG   ::= OCTET STRING  
+  
+PLMN-Identity ::= OCTET STRING (SIZE(3))  
+  
+Pre-emptionCapability ::= ENUMERATED {  
+    shall-not-trigger-pre-emption,  
+    may-trigger-pre-emption  
+}  
+  
+Pre-emptionVulnerability ::= ENUMERATED {  
+    not-pre-emptable,  
+    pre-emptable  
+}  
+  
+PriorityLevel   ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15)  
+  
+Potential-SpCell-Item ::= SEQUENCE {  
+    potential-SpCell-ID      EUTRANCGI   ,  
+    iE-Extensions   ProtocolExtensionContainer { { Potential-SpCell-ItemExtIEs } }   OPTIONAL,  
+    ...  
+}  
+  
+Potential-SpCell-ItemExtIEs   WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+PWS-Failed-E-UTRAN-CGI-Item ::= SEQUENCE {  
+    eUTRANCGI      EUTRANCGI,  
+    iE-Extensions   ProtocolExtensionContainer { { PWS-Failed-E-UTRAN-CGI-ItemExtIEs } }  
+    OPTIONAL,  
+    ...  
+}  
+  
+PWS-Failed-E-UTRAN-CGI-ItemExtIEs   WIAP-PROTOCOL-EXTENSION ::= {  
+    ...  
+}  
+  
+PWSSystemInformation ::= SEQUENCE {  
+    sIBType      SIBType-PWS,  
+    sIBmessage   OCTET STRING,  
+    iE-Extensions   ProtocolExtensionContainer { { PWSSystemInformationExtIEs } }   OPTIONAL,  
+    ...  
+}
+```
+
+```
+
+PWSSystemInformationExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  {ID id-NotificationInformation CRITICALITY ignore EXTENSION NotificationInformation
+    PRESENCE mandatory}|
+  {ID id-AdditionalSIBMessageList CRITICALITY reject EXTENSION AdditionalSIBMessageList
+    PRESENCE optional}|
+  ...
+}
+
+-- Q
+
+QCI ::= INTEGER (0..255)
+
+QoS-Characteristics ::= CHOICE {
+  non-Dynamic-5QI      NonDynamic5QIDescriptor,
+  dynamic-5QI          Dynamic5QIDescriptor,
+  choice-extension     ProtocolIE-SingleContainer { { QoS-Characteristics-ExtIEs } }
+}
+
+QoS-Characteristics-ExtIEs WIAP-PROTOCOL-IES ::= {
+  ...
+}
+
+QoSFlowIdentifier ::= INTEGER (0..63)
+
+QoSFlowLevelQoSParameters ::= SEQUENCE {
+  qoS-Characteristics      QoS-Characteristics,
+  nGRANAllocationRetentionPriority NGRANAllocationAndRetentionPriority,
+  gBR-QoS-Flow-Information GBR-QoSFlowInformation OPTIONAL,
+  reflective-QoS-Attribute ENUMERATED {subject-to, ...} OPTIONAL,
+  pDUSessionID             PDUSessionID OPTIONAL,
+  uLPDUSessionAggregateMaximumBitRate BitRate OPTIONAL,
+  iE-Extensions            ProtocolExtensionContainer { { QoSFlowLevelQoSParameters-ExtIEs } }
+  OPTIONAL,
+  ...
+}
+
+QoSFlowLevelQoSParameters-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  { ID id-PDCPTerminatingNodeDLTNLAddrInfo CRITICALITY ignore EXTENSION
+  TransportLayerAddress PRESENCE optional },
+  ...
+}
+
+QoSFlowMappingIndication ::= ENUMERATED {ul,dl,...}
+
+QoSInformation ::= CHOICE {
+  eUTRANQoS      EUTRANQoS,
+  dRB-Information DRB-Information,
+  choice-extension ProtocolIE-SingleContainer { { QoSInformation-ExtIEs } }
+}
+
+QoSInformation-ExtIEs WIAP-PROTOCOL-IES ::= {
+  ...
+}
+
+-- R
+
+RadioResourceConfigDedicated ::= OCTET STRING
+
+RANAC ::= INTEGER (0..255)
+
+RANUEPagingIdentity ::= SEQUENCE {
+  iRNTI            BIT STRING (SIZE(40)),
+  iE-Extensions    ProtocolExtensionContainer { { RANUEPagingIdentity-ExtIEs } } OPTIONAL,
+  ...
+}
+
+RANUEPagingIdentity-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+  ...
+}
+
+RAT-FrequencyPriorityInformation ::= CHOICE {
+  eNDC      SubscriberProfileIDforRFP,
+  nGRAN     RAT-FrequencySelectionPriority,
+  choice-extension ProtocolIE-SingleContainer { { RAT-FrequencyPriorityInformation-ExtIEs } }
+}
+
+```
+
+```
+RAT-FrequencyPriorityInformation-ExtIEs WIAP-PROTOCOL-IES ::= {  
+  ...  
+}  
+  
+RAT-FrequencySelectionPriority ::= INTEGER (1.. 256, ...)  
+  
+Reestablishment-Indication ::= ENUMERATED {  
+  reestablished,  
+  ...  
+}  
+  
+RequestedBandCombinationIndex ::= OCTET STRING  
+  
+RequestedFeatureSetEntryIndex ::= OCTET STRING  
+  
+RequestType ::= ENUMERATED {offer, execution, ...}  
+  
+ResourceCoordinationEUTRACellInfo ::= SEQUENCE {  
+  eUTRA-Mode-Info           EUTRA-Coex-Mode-Info,  
+  eUTRA-PRACH-Configuration EUTRA-PRACH-Configuration,  
+  iE-Extensions  ProtocolExtensionContainer { { ResourceCoordinationEUTRACellInfo-ExtIEs } }  
+  OPTIONAL,  
+  ...  
+}  
+  
+ResourceCoordinationEUTRACellInfo-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+ResourceCoordinationTransferInformation ::= SEQUENCE {  
+  meNB-Cell-ID            EUTRA-Cell-ID,  
+  resourceCoordinationEUTRACellInfo  ResourceCoordinationEUTRACellInfo  OPTIONAL,  
+  iE-Extensions  ProtocolExtensionContainer { { ResourceCoordinationTransferInformation-ExtIEs } } OPTIONAL,  
+  ...  
+}  
+  
+ResourceCoordinationTransferInformation-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+ResourceCoordinationTransferContainer ::= OCTET STRING  
+  
+RepetitionPeriod ::= INTEGER (0..131071, ...)  
+  
+RLCMode ::= ENUMERATED {  
+  rlc-am,  
+  rlc-um-bidirectional,  
+  rlc-um-unidirectional-ul,  
+  rlc-um-unidirectional-dl,  
+  ...  
+}  
+  
+RLC-Status ::= SEQUENCE {  
+  reestablishment-Indication  
+  iE-Extensions  ProtocolExtensionContainer { { RLC-Status-ExtIEs } } OPTIONAL,  
+  ...  
+}  
+  
+RLC-Status-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {  
+  ...  
+}  
+  
+RRCContainer ::= OCTET STRING  
+  
+RRCReconfigurationCompleteIndicator ::= ENUMERATED {  
+  true,  
+  failure,  
+  ...  
+}  
+  
+-- S  
+  
+SCell-FailedtoSetup-Item ::= SEQUENCE {  
+  sCell-ID  EUTRANCGI,
+```
+
+```
+
+        cause          Cause          OPTIONAL ,
+        iE-Extensions  ProtocolExtensionContainer { { SCell-FailedtoSetup-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SCell-FailedtoSetup-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SCell-FailedtoSetupMod-Item ::= SEQUENCE {
+        sCell-ID          EUTRANCGI,
+        cause             Cause          OPTIONAL,
+        iE-Extensions     ProtocolExtensionContainer { { SCell-FailedtoSetupMod-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SCell-FailedtoSetupMod-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SCell-ToBeRemoved-Item ::= SEQUENCE {
+        sCell-ID          EUTRANCGI,
+        iE-Extensions     ProtocolExtensionContainer { { SCell-ToBeRemoved-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SCell-ToBeRemoved-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SCell-ToBeSetup-Item ::= SEQUENCE {
+        sCell-ID          EUTRANCGI,
+        sCellIndex        SCellIndex,
+        iE-Extensions     ProtocolExtensionContainer { { SCell-ToBeSetup-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SCell-ToBeSetup-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SCell-ToBeSetupMod-Item ::= SEQUENCE {
+        sCell-ID          EUTRANCGI,
+        sCellIndex        SCellIndex,
+        iE-Extensions     ProtocolExtensionContainer { { SCell-ToBeSetupMod-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SCell-ToBeSetupMod-ItemExtIEs  WIAP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SCellIndex ::= INTEGER (1..31, ...)
+
+    SCGIndicator ::= ENUMERATED {released, ...}
+
+    SIBType-PWS ::= INTEGER (6..8,...)
+
+    SelectedBandCombinationIndex ::= OCTET STRING
+
+    SelectedFeatureSetEntryIndex ::= OCTET STRING
+
+    SerialNumber ::= BIT STRING (SIZE (16))
+
+    CG-ConfigInfo ::= OCTET STRING
+
+    ServCellIndex ::= INTEGER (0..31,...)
+
+    Served-Cell-Information ::= SEQUENCE {
+        eUTRANCGI           EUTRANCGI,
+        eUTRANPCI           EUTRANPCI,
+        fiveGS-TAC          FiveGS-TAC          OPTIONAL,
+        servedPLMNs         ServedPLMNs-List,
+        eUTRAN-Mode-Info    E-UTRAN-Mode-Info,
+        measurementTimingConfiguration  OCTET STRING,
+        rANAC               RANAC             OPTIONAL,
+        cell-Type           Cell-Type         OPTIONAL,
+    }
+
+```
+
+```
+
+    bPLMN-ID-Info-List          BPLMN-ID-Info-List          OPTIONAL,
+    iE-Extensions               ProtocolExtensionContainer { {Served-Cell-Information-ExtIEs} } OPTIONAL,
+    ...
+  }
+
+  Served-Cell-Information-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+  Served-Cells-To-Add-Item ::= SEQUENCE {
+    served-Cell-Information      Served-Cell-Information,
+    ngeNB-DU-System-Information NGENB-DU-System-Information OPTIONAL,
+    iE-Extensions                ProtocolExtensionContainer { { Served-Cells-To-Add-ItemExtIEs} }
+    OPTIONAL,
+    ...
+  }
+
+  Served-Cells-To-Add-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+  Served-Cells-To-Delete-Item ::= SEQUENCE {
+    oldEUTRANCGI                EUTRANCGI,
+    iE-Extensions                ProtocolExtensionContainer { { Served-Cells-To-Delete-ItemExtIEs } }
+    OPTIONAL,
+    ...
+  }
+
+  Served-Cells-To-Delete-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+  Served-Cells-To-Modify-Item ::= SEQUENCE {
+    oldEUTRANCGI                EUTRANCGI,
+    served-Cell-Information      Served-Cell-Information,
+    ngeNB-DU-System-Information NGENB-DU-System-Information OPTIONAL,
+    iE-Extensions                ProtocolExtensionContainer { { Served-Cells-To-Modify-
+    ItemExtIEs } } OPTIONAL,
+    ...
+  }
+
+  Served-Cells-To-Modify-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+  Service-State ::= ENUMERATED {
+    in-service,
+    out-of-service,
+    ...
+  }
+
+  Service-Status ::= SEQUENCE {
+    service-state                Service-State,
+    switchingOffOngoing          ENUMERATED {true, ...} OPTIONAL,
+    iE-Extensions                ProtocolExtensionContainer { { Service-Status-ExtIEs } }
+    OPTIONAL,
+    ...
+  }
+
+  Service-Status-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+  ServedPLMNs-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF ServedPLMNs-Item
+
+  ServedPLMNs-Item ::= SEQUENCE {
+    pLMN-Identity                PLMN-Identity,
+    tAISliceSupportList          SliceSupportList OPTIONAL,
+    iE-Extensions                ProtocolExtensionContainer { { ServedPLMNs-ItemExtIEs} } OPTIONAL,
+    ...
+  }
+
+  ServedPLMNs-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+  }
+
+```
+
+```
+ShortDRXCycleLength ::= ENUMERATED {ms2, ms5, ms8, ms10, ms16, ms20, ms32, ms40, ms64, ms80, ms128,
+ms160, ms256, ms320, ms512, ms640, ...}
+
+ShortDRXCycleTimer ::= INTEGER (1..16)
+
+SIB1-message ::= OCTET STRING
+
+SIB2-message ::= OCTET STRING
+
+SIB3-message ::= OCTET STRING
+
+SIB8-message ::= OCTET STRING
+
+SIB16-message ::= OCTET STRING
+
+SibtypetobeupdatedListItem ::= SEQUENCE {
+    sibType           INTEGER (2..32,...),
+    sibMessage        OCTET STRING,
+    valueTag          INTEGER (0..31,...),
+    iE-Extensions     ProtocolExtensionContainer { { SibtypetobeupdatedListItem-ExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+SibtypetobeupdatedListItem-ExtIEs  WLP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+SliceSupportList ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SliceSupportItem
+
+SliceSupportItem ::= SEQUENCE {
+    sNSSAI  SNSSAI,
+    iE-Extensions     ProtocolExtensionContainer { { SliceSupportItem-ExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+SliceSupportItem-ExtIEs  WLP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+SNSSAI ::= SEQUENCE {
+    sST           OCTET STRING (SIZE(1)),
+    sD            OCTET STRING (SIZE(3))  OPTIONAL,
+    iE-Extensions     ProtocolExtensionContainer { { SNSSAI-ExtIEs } }  OPTIONAL,
+    ...
+}
+
+SNSSAI-ExtIEs  WLP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+SRBID ::= INTEGER (0..3, ...)
+
+SRBs-FailedToBeSetup-Item ::= SEQUENCE {
+    sRBID     SRBID,
+    cause     Cause  OPTIONAL,
+    iE-Extensions     ProtocolExtensionContainer { { SRBs-FailedToBeSetup-ItemExtIEs } }  OPTIONAL,
+    ...
+}
+
+SRBs-FailedToBeSetup-ItemExtIEs  WLP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+SRBs-FailedToBeSetupMod-Item ::= SEQUENCE {
+    sRBID     SRBID,
+    cause     Cause  OPTIONAL,
+    iE-Extensions     ProtocolExtensionContainer { { SRBs-FailedToBeSetupMod-ItemExtIEs } }
+    OPTIONAL,
+    ...
+}
+
+SRBs-FailedToBeSetupMod-ItemExtIEs  WLP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+SRBs-Modified-Item ::= SEQUENCE {
+```
+
+```
+        sRBID                     SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-Modified-ItemExtIEs } } OPTIONAL,
+        ...
+    }
+
+    SRBs-Modified-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-Required-ToBeReleased-Item ::= SEQUENCE {
+        sRBID  SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-Required-ToBeReleased-ItemExtIEs } }
+        OPTIONAL,
+        ...
+    }
+
+    SRBs-Required-ToBeReleased-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-Setup-Item ::= SEQUENCE {
+        sRBID                     SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-Setup-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SRBs-Setup-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-SetupMod-Item ::= SEQUENCE {
+        sRBID                     SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-SetupMod-ItemExtIEs } } OPTIONAL,
+        ...
+    }
+
+    SRBs-SetupMod-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-ToBeReleased-Item ::= SEQUENCE {
+        sRBID  SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-ToBeReleased-ItemExtIEs } } OPTIONAL,
+        ...
+    }
+
+    SRBs-ToBeReleased-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-ToBeSetup-Item ::= SEQUENCE {
+        sRBID  SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-ToBeSetup-ItemExtIEs } }  OPTIONAL,
+        ...
+    }
+
+    SRBs-ToBeSetup-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SRBs-ToBeSetupMod-Item ::= SEQUENCE {
+        sRBID  SRBID,
+        iE-Extensions  ProtocolExtensionContainer { { SRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL,
+        ...
+    }
+
+    SRBs-ToBeSetupMod-ItemExtIEs  W1AP-PROTOCOL-EXTENSION ::= {
+        ...
+    }
+
+    SubscriberProfileIDforRFP ::= INTEGER (1..256, ...)
+
+    -- T
+
+    FiveGS-TAC ::= OCTET STRING (SIZE(3))
+```
+
+```
+
+TDD-Info ::= SEQUENCE {
+    eUTRAFreqInfo             EUTRAFreqInfo,
+    transmission-Bandwidth    Transmission-Bandwidth,
+    iE-Extensions             ProtocolExtensionContainer { {TDD-Info-ExtIEs} } OPTIONAL,
+    ...
+}
+
+TDD-Info-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+TransportLayerAddress ::= BIT STRING (SIZE(1..160,...))
+
+TransactionID ::= INTEGER (0..255,...)
+
+Transmission-Bandwidth ::= SEQUENCE {
+    eUTRANRB    EUTRA-Transmission-Bandwidth,
+    iE-Extensions             ProtocolExtensionContainer { { Transmission-Bandwidth-ExtIEs } }
+OPTIONAL,
+    ...
+}
+
+Transmission-Bandwidth-ExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+TransmissionActionIndicator ::= ENUMERATED {stop, ..., restart}
+
+TypeOfError ::= ENUMERATED {
+    not-understood,
+    missing,
+    ...
+}
+
+-- U
+
+UE-associatedLogicalW1-ConnectionItem ::= SEQUENCE {
+    ngenb-CU-UE-W1AP-ID     NGNB-CU-UE-W1AP-ID OPTIONAL,
+    ngenb-DU-UE-W1AP-ID     NGNB-DU-UE-W1AP-ID OPTIONAL,
+    iE-Extensions             ProtocolExtensionContainer { { UE-associatedLogicalW1-
+ConnectionItemExtIEs } } OPTIONAL,
+    ...
+}
+
+UE-associatedLogicalW1-ConnectionItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+UEAssistanceInformation ::= OCTET STRING
+
+UE-CapabilityRAT-ContainerList ::= OCTET STRING
+
+UEIdentityIndexValue ::= CHOICE {
+    indexLength10             BIT STRING (SIZE (10)),
+    choice-extension            ProtocolIE-SingleContainer { {UEIdentityIndexValueChoice-ExtIEs} }
+}
+
+UEIdentityIndexValueChoice-ExtIEs WIAP-PROTOCOL-IES ::= {
+    ...
+}
+
+ULUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofULUPTNLInformation)) OF
+ULUPTNLInformation-ToBeSetup-Item
+
+ULUPTNLInformation-ToBeSetup-Item ::= SEQUENCE {
+    uLUPTNLInformation        UPTransportLayerInformation,
+    iE-Extensions             ProtocolExtensionContainer { { ULUPTNLInformation-ToBeSetup-
+ItemExtIEs } } OPTIONAL,
+    ...
+}
+
+ULUPTNLInformation-ToBeSetup-ItemExtIEs WIAP-PROTOCOL-EXTENSION ::= {
+    ...
+}
+
+UPTransportLayerInformation ::= CHOICE {
+    gPTunnel                    GPTunnel,
+}
+
+```
+
+```
+
+    choice-extension      ProtocolIE-SingleContainer { { UPTransportLayerInformation-ExtIEs} }
+  }
+
+  UPTransportLayerInformation-ExtIEs W1AP-PROTOCOL-IES ::= {
+    ...
+  }
+  -- V
+  -- W
+  -- X
+  -- Y
+  -- Z
+
+  END
+  -- ASN1STOP
+
+```
+
+### 9.4.6 Common Definitions
+
+```
+
+  -- ASN1START
+  -- *****
+  --
+  -- Common definitions
+  --
+  -- *****
+
+  W1AP-CommonDataTypes {
+    itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+    ngran-access (22) modules (3) wlap (3) version1 (1) wlap-CommonDataTypes (3) }
+
+  DEFINITIONS AUTOMATIC TAGS ::=
+
+  BEGIN
+
+  Criticality      ::= ENUMERATED { reject, ignore, notify }
+
+  Presence         ::= ENUMERATED { optional, conditional, mandatory }
+
+  PrivateIE-ID     ::= CHOICE {
+    local            INTEGER (0..65535),
+    global           OBJECT IDENTIFIER
+  }
+
+  ProcedureCode      ::= INTEGER (0..255)
+
+  ProtocolExtensionID ::= INTEGER (0..65535)
+
+  ProtocolIE-ID      ::= INTEGER (0..65535)
+
+  TriggeringMessage  ::= ENUMERATED { initiating-message, successful-outcome, unsuccessfull-outcome }
+
+  END
+  -- ASN1STOP
+
+```
+
+### 9.4.7 Constant Definitions
+
+```
+
+  -- ASN1START
+  -- *****
+  --
+  -- Constant definitions
+  --
+  -- *****
+
+  W1AP-Constants {
+    itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
+    ngran-access (22) modules (3) wlap (3) version1 (1) wlap-Constants (4) }
+
+  DEFINITIONS AUTOMATIC TAGS ::=
+
+  BEGIN
+
+  -- *****
+  --
+
+```
+
+```
+
+-- IE parameter types from other modules.
+--
+-- *****
+
+IMPORTS
+    ProcedureCode,
+    ProtocolIE-ID
+
+FROM W1AP-CommonDataTypes;
+
+-- *****
+--
+-- Elementary Procedures
+--
+-- *****
+
+id-Reset                      ProcedureCode ::= 0
+id-W1Setup                    ProcedureCode ::= 1
+id-ErrorIndication            ProcedureCode ::= 2
+id-ngeNBDUConfigurationUpdate ProcedureCode ::= 3
+id-ngeNBCUConfigurationUpdate ProcedureCode ::= 4
+id-UEContextSetup             ProcedureCode ::= 5
+id-UEContextRelease           ProcedureCode ::= 6
+id-UEContextModification      ProcedureCode ::= 7
+id-UEContextModificationRequired ProcedureCode ::= 8
+id-UEMobilityCommand          ProcedureCode ::= 9
+id-UEContextReleaseRequest    ProcedureCode ::= 10
+id-InitialULRRCMessageTransfer ProcedureCode ::= 11
+id-DLRRCMessageTransfer       ProcedureCode ::= 12
+id-ULRRCMessageTransfer       ProcedureCode ::= 13
+id-privateMessage             ProcedureCode ::= 14
+id-UEInactivityNotification   ProcedureCode ::= 15
+id-NGENBDUREsourceCoordination ProcedureCode ::= 16
+id-Paging                     ProcedureCode ::= 17
+id-Notify                     ProcedureCode ::= 18
+id-WriteReplaceWarning        ProcedureCode ::= 19
+id-PWSCancel                  ProcedureCode ::= 20
+id-PWSRestartIndication       ProcedureCode ::= 21
+id-PWSFailureIndication       ProcedureCode ::= 22
+id-NGENBDUStatusIndication    ProcedureCode ::= 23
+
+-- *****
+--
+-- Extension constants
+--
+-- *****
+
+maxPrivateIEs                 INTEGER ::= 65535
+maxProtocolExtensions           INTEGER ::= 65535
+maxProtocolIEs                INTEGER ::= 65535
+-- *****
+--
+-- Lists
+--
+-- *****
+
+maxEARFCN                     INTEGER ::= 262143
+maxnoofErrors                 INTEGER ::= 256
+maxnoofIndividualW1ConnectionsToReset INTEGER ::= 65536
+maxCellinngenNBDU             INTEGER ::= 512
+maxnoofSCells                 INTEGER ::= 32
+maxnoofSRBs                   INTEGER ::= 8
+maxnoofDRBs                   INTEGER ::= 64
+maxnoofULUPTNLInformation     INTEGER ::= 2
+maxnoofDLUPTNLInformation     INTEGER ::= 2
+maxnoofBPLMNs                 INTEGER ::= 6
+maxnoofCandidateSpCells       INTEGER ::= 64
+maxnoofPotentialSpCells       INTEGER ::= 64
+maxnoofE-UTRANCellBands       INTEGER ::= 8
+maxnoofSIBTypes               INTEGER ::= 32
+maxnoofPagingCells            INTEGER ::= 512
+maxnoofTNLAssociations        INTEGER ::= 32
+maxnoofQoSFlows               INTEGER ::= 64
+maxnoofSliceItems             INTEGER ::= 1024
+maxCellineNB                  INTEGER ::= 256
+maxnoofExtendedBPLMNs         INTEGER ::= 6
+
+```
+
+```
+
+maxnoofUEIDs                INTEGER ::= 65536
+maxBandsEutra               INTEGER ::= 256
+maxnoofAdditionalSIBs       INTEGER ::= 63
+
+-- *****
+--
+-- IEs
+--
+-- *****
+
+id-Cause                      ProtocolIE-ID ::= 0
+id-Cells-Failed-to-be-Activated-List          ProtocolIE-ID ::= 1
+id-Cells-to-be-Activated-List               ProtocolIE-ID ::= 2
+id-Cells-to-be-Deactivated-List             ProtocolIE-ID ::= 3
+id-CriticalityDiagnostics                 ProtocolIE-ID ::= 4
+id-CUtoDURRCInformation                 ProtocolIE-ID ::= 5
+id-DRBs-FailedToBeModified-List           ProtocolIE-ID ::= 6
+id-DRBs-FailedToBeSetup-List              ProtocolIE-ID ::= 7
+id-DRBs-FailedToBeSetupMod-List           ProtocolIE-ID ::= 8
+id-DRBs-ModifiedConf-List               ProtocolIE-ID ::= 9
+id-DRBs-Modified-List                   ProtocolIE-ID ::= 10
+id-DRBs-Required-ToBeModified-List        ProtocolIE-ID ::= 11
+id-DRBs-Required-ToBeReleased-List        ProtocolIE-ID ::= 12
+id-DRBs-Setup-List                      ProtocolIE-ID ::= 13
+id-DRBs-SetupMod-List                   ProtocolIE-ID ::= 14
+id-DRBs-ToBeModified-List               ProtocolIE-ID ::= 15
+id-DRBs-ToBeReleased-List               ProtocolIE-ID ::= 16
+id-DRBs-ToBeSetup-List                  ProtocolIE-ID ::= 17
+id-DRBs-ToBeSetupMod-List               ProtocolIE-ID ::= 18
+id-DRXCycle                             ProtocolIE-ID ::= 19
+id-DUtoCURRCInformation               ProtocolIE-ID ::= 20
+id-ngeNB-CU-UE-WLAP-ID                ProtocolIE-ID ::= 21
+id-ngeNB-DU-UE-WLAP-ID                ProtocolIE-ID ::= 22
+id-ngeNB-DU-ID                        ProtocolIE-ID ::= 23
+id-ngeNB-DU-Served-Cells-List           ProtocolIE-ID ::= 24
+id-oldngeNB-DU-UE-WLAP-ID             ProtocolIE-ID ::= 25
+id-RAT-FrequencyPriorityInformation     ProtocolIE-ID ::= 26
+id-ResetType                            ProtocolIE-ID ::= 27
+id-ResourceCoordinationTransferContainer ProtocolIE-ID ::= 28
+id-RRContainer                          ProtocolIE-ID ::= 29
+id-SCell-ToBeRemoved-List             ProtocolIE-ID ::= 30
+id-SCell-ToBeSetup-List               ProtocolIE-ID ::= 31
+id-SCell-ToBeSetupMod-List            ProtocolIE-ID ::= 32
+id-Served-Cells-To-Add-List           ProtocolIE-ID ::= 33
+id-Served-Cells-To-Delete-List          ProtocolIE-ID ::= 34
+id-Served-Cells-To-Modify-List          ProtocolIE-ID ::= 35
+id-SpCell-ID                          ProtocolIE-ID ::= 36
+id-SRBID                              ProtocolIE-ID ::= 37
+id-SRBs-FailedToBeSetup-List           ProtocolIE-ID ::= 38
+id-SRBs-FailedToBeSetupMod-List         ProtocolIE-ID ::= 39
+id-SRBs-Required-ToBeReleased-List      ProtocolIE-ID ::= 40
+id-SRBs-ToBeReleased-List             ProtocolIE-ID ::= 41
+id-SRBs-ToBeSetup-List                ProtocolIE-ID ::= 42
+id-SRBs-ToBeSetupMod-List             ProtocolIE-ID ::= 43
+id-TransactionID                      ProtocolIE-ID ::= 44
+id-TransmissionActionIndicator        ProtocolIE-ID ::= 45
+id-UE-associatedLogicalW1-ConnectionListResAck ProtocolIE-ID ::= 46
+id-SCell-FailedtoSetup-List           ProtocolIE-ID ::= 47
+id-SCell-FailedtoSetupMod-List          ProtocolIE-ID ::= 48
+id-RRReconfigurationCompleteIndicator ProtocolIE-ID ::= 49
+id-Cells-Status-List                  ProtocolIE-ID ::= 50
+id-Candidate-SpCell-List              ProtocolIE-ID ::= 51
+id-Potential-SpCell-List              ProtocolIE-ID ::= 52
+id-C-RNTI                             ProtocolIE-ID ::= 53
+id-InactivityMonitoringRequest          ProtocolIE-ID ::= 54
+id-InactivityMonitoringResponse         ProtocolIE-ID ::= 55
+id-DRB-Activity-List                  ProtocolIE-ID ::= 56
+id-EUTRA-NR-CellResourceCoordinationReq-Container ProtocolIE-ID ::= 57
+id-EUTRA-NR-CellResourceCoordinationReqAck-Container ProtocolIE-ID ::= 58
+id-RequestType                        ProtocolIE-ID ::= 59
+id-ServCellIndex                      ProtocolIE-ID ::= 60
+id-EUTRANCGI                          ProtocolIE-ID ::= 61
+id-PagingCell-List                    ProtocolIE-ID ::= 62
+id-PagingDRX                          ProtocolIE-ID ::= 63
+id-UEIdentityIndexValue               ProtocolIE-ID ::= 64
+id-PagingIdentity                     ProtocolIE-ID ::= 65
+id-DUtoCURRCContainer               ProtocolIE-ID ::= 66
+id-DRB-Notify-List                    ProtocolIE-ID ::= 67
+
+```
+
+```
+
+id-NotificationControl                          ProtocolIE-ID ::= 68
+id-PWSSystemInformation                         ProtocolIE-ID ::= 69
+id-RepetitionPeriod                             ProtocolIE-ID ::= 70
+id-NumberOfBroadcastRequest                     ProtocolIE-ID ::= 71
+id-Cells-To-Be-Broadcast-List                   ProtocolIE-ID ::= 72
+id-Cells-Broadcast-Completed-List               ProtocolIE-ID ::= 73
+id-Broadcast-To-Be-Cancelled-List               ProtocolIE-ID ::= 74
+id-Cells-Broadcast-Cancelled-List               ProtocolIE-ID ::= 75
+id-E-UTRAN-CGI-List-For-Restart-List            ProtocolIE-ID ::= 76
+id-PWS-Failed-E-UTRAN-CGI-List                  ProtocolIE-ID ::= 77
+id-ConfirmedUEID                                ProtocolIE-ID ::= 78
+id-Cancel-all-Warning-Messages-Indicator        ProtocolIE-ID ::= 79
+id-NGENB-DU-UE-AMBR-UL                          ProtocolIE-ID ::= 80
+id-ServingPLMN                                  ProtocolIE-ID ::= 81
+id-NGENBDUOverloadInformation                   ProtocolIE-ID ::= 82
+id-ResourceCoordinationTransferInformation       ProtocolIE-ID ::= 83
+id-SRBs-Setup-List                              ProtocolIE-ID ::= 85
+id-SRBs-SetupMod-List                           ProtocolIE-ID ::= 86
+id-SRBs-Modified-List                           ProtocolIE-ID ::= 87
+id-IgnoreResourceCoordinationRequestContainer   ProtocolIE-ID ::= 88
+id-NotificationInformation                      ProtocolIE-ID ::= 89
+id-AdditionalSIBMessageList                     ProtocolIE-ID ::= 90
+id-MeasGapSharingConfig                         ProtocolIE-ID ::= 91
+id-SCGIndicator                                 ProtocolIE-ID ::= 92
+id-PagingOrigin                                 ProtocolIE-ID ::= 93
+id-PDCPTerminatingNodeDLTNLAddrInfo             ProtocolIE-ID ::= 94
+
+```
+
+```
+
+END
+-- ASN1STOP
+
+```
+
+### 9.4.8 Container Definitions
+
+```
+
+-- ASN1START
+-- **************************************************************
+--
+-- Container definitions
+--
+-- **************************************************************
+
+W1AP-Containers {
+itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) 
+ngran-access (22) modules (3) w1ap (3) version1 (1) w1ap-Containers (5) }
+
+DEFINITIONS AUTOMATIC TAGS ::=
+
+BEGIN
+
+-- **************************************************************
+--
+-- IE parameter types from other modules.
+--
+-- **************************************************************
+
+IMPORTS
+    Criticality,
+    Presence,
+    PrivateIE-ID,
+    ProtocolExtensionID,
+    ProtocolIE-ID
+
+FROM W1AP-CommonDataTypes
+    maxPrivateIEs,
+    maxProtocolExtensions,
+    maxProtocolIEs
+
+FROM W1AP-Constants;
+
+-- **************************************************************
+--
+-- Class Definition for Protocol IEs
+--
+-- **************************************************************
+
+W1AP-PROTOCOL-IES ::= CLASS {
+    &id             ProtocolIE-ID           UNIQUE,
+    &criticality    Criticality,
+
+```
+
+```
+
+    &Value,
+    &presence      Presence
+  }
+  WITH SYNTAX {
+    ID            &id
+    CRITICALITY   &criticality
+    TYPE          &Value
+    PRESENCE      &presence
+  }
+
+  -- *****
+  --
+  -- Class Definition for Protocol IEs
+  --
+  -- *****
+
+  W1AP-PROTOCOL-IES-PAIR ::= CLASS {
+    &id           ProtocolIE-ID           UNIQUE,
+    &firstCriticality  Criticality,
+    &FirstValue,
+    &secondCriticality  Criticality,
+    &SecondValue,
+    &presence      Presence
+  }
+  WITH SYNTAX {
+    ID            &id
+    FIRST CRITICALITY  &firstCriticality
+    FIRST TYPE       &FirstValue
+    SECOND CRITICALITY  &secondCriticality
+    SECOND TYPE      &SecondValue
+    PRESENCE         &presence
+  }
+
+  -- *****
+  --
+  -- Class Definition for Protocol Extensions
+  --
+  -- *****
+
+  W1AP-PROTOCOL-EXTENSION ::= CLASS {
+    &id           ProtocolExtensionID           UNIQUE,
+    &criticality  Criticality,
+    &Extension,
+    &presence     Presence
+  }
+  WITH SYNTAX {
+    ID            &id
+    CRITICALITY   &criticality
+    EXTENSION     &Extension
+    PRESENCE      &presence
+  }
+
+  -- *****
+  --
+  -- Class Definition for Private IEs
+  --
+  -- *****
+
+  W1AP-PRIVATE-IES ::= CLASS {
+    &id           PrivateIE-ID,
+    &criticality  Criticality,
+    &Value,
+    &presence     Presence
+  }
+  WITH SYNTAX {
+    ID            &id
+    CRITICALITY   &criticality
+    TYPE          &Value
+    PRESENCE      &presence
+  }
+
+  -- *****
+  --
+  -- Container for Protocol IEs
+  --
+  -- *****
+
+  ProtocolIE-Container {W1AP-PROTOCOL-IES : IEsSetParam} ::=
+
+```
+
+```
+
+    SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+    ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-SingleContainer {W1AP-PROTOCOL-IES : IEsSetParam} ::=
+  ProtocolIE-Field {{IEsSetParam}}
+
+ProtocolIE-Field {W1AP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE {
+  id                W1AP-PROTOCOL-IES.&id                {{IEsSetParam}},
+  criticality       W1AP-PROTOCOL-IES.&criticality        {{IEsSetParam}{@id}},
+  value             W1AP-PROTOCOL-IES.&Value               {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Protocol IE Pairs
+--
+-- *****
+
+ProtocolIE-ContainerPair {W1AP-PROTOCOL-IES-PAIR : IEsSetParam} ::=
+  SEQUENCE (SIZE (0..maxProtocolIEs)) OF
+  ProtocolIE-FieldPair {{IEsSetParam}}
+
+ProtocolIE-FieldPair {W1AP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE {
+  id                W1AP-PROTOCOL-IES-PAIR.&id             {{IEsSetParam}},
+  firstCriticality  W1AP-PROTOCOL-IES-PAIR.&firstCriticality {{IEsSetParam}{@id}},
+  firstValue        W1AP-PROTOCOL-IES-PAIR.&FirstValue      {{IEsSetParam}{@id}},
+  secondCriticality W1AP-PROTOCOL-IES-PAIR.&secondCriticality {{IEsSetParam}{@id}},
+  secondValue       W1AP-PROTOCOL-IES-PAIR.&SecondValue     {{IEsSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Protocol Extensions
+--
+-- *****
+
+ProtocolExtensionContainer {W1AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=
+  SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
+  ProtocolExtensionField {{ExtensionSetParam}}
+
+ProtocolExtensionField {W1AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
+  id                W1AP-PROTOCOL-EXTENSION.&id             {{ExtensionSetParam}},
+  criticality       W1AP-PROTOCOL-EXTENSION.&criticality    {{ExtensionSetParam}{@id}},
+  extensionValue    W1AP-PROTOCOL-EXTENSION.&Extension     {{ExtensionSetParam}{@id}}
+}
+
+-- *****
+--
+-- Container for Private IEs
+--
+-- *****
+
+PrivateIE-Container {W1AP-PRIVATE-IES : IEsSetParam} ::=
+  SEQUENCE (SIZE (1.. maxPrivateIEs)) OF
+  PrivateIE-Field {{IEsSetParam}}
+
+PrivateIE-Field {W1AP-PRIVATE-IES : IEsSetParam} ::= SEQUENCE {
+  id                W1AP-PRIVATE-IES.&id                    {{IEsSetParam}},
+  criticality       W1AP-PRIVATE-IES.&criticality           {{IEsSetParam}{@id}},
+  value             W1AP-PRIVATE-IES.&Value                 {{IEsSetParam}{@id}}
+}
+
+END
+-- ASN1STOP
+
+```
+
+## 9.5 Message Transfer Syntax
+
+W1AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Recommendation X.691 [21].
+
+## 9.6 Timers
+
+Void
+
+---
+
+## 10 Handling of unknown, unforeseen and erroneous protocol data
+
+Clause 10 of TS 38.413 [19] is applicable for the purposes of the present document, with the following additions for non-UE-associated procedures:
+
+- In case of Abstract Syntax Error, when reporting the *Criticality Diagnostics* IE for not comprehended IE/IEgroups or missing IE/IE groups, the *Transaction ID* IE shall also be included.
+- In case of Logical Error, when reporting the *Criticality Diagnostics* IE, the *Transaction ID* IE shall also be included.
+- In case of Logical Error in a response message of a Class 1 procedure, or failure to comprehend *Transaction ID* IE from a received message, the procedure shall be considered as unsuccessfully terminated or not terminated (e.g., transaction ID unknown in response message), and local error handling shall be initiated.
+
+## Annex A (informative): Change History
+
+| Change history |              |           |      |     |     |                                                                                                                                                                                    |             |
+|----------------|--------------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                                                                    | New version |
+| 2018-05        | RAN3#100     | R3-183555 |      |     |     | BL TS submission for approval.                                                                                                                                                     |             |
+| 2019-08        | RAN3#105     | R3-184888 |      |     |     | Capture the agreed main W1 AP procedures: R3-194563, R3-194564, R3-194565                                                                                                          | 0.1.0       |
+| 2019-10        | RAN3#105-Bis | R3-196137 |      |     |     | Add the stage3 paging procedure                                                                                                                                                    | 0.1.0       |
+| 2019-10        | RAN3#105-Bis | R3-196136 |      |     |     | Add Warning message transmission related procedures with corresponding tabular                                                                                                     | 0.1.0       |
+| 2019-10        | RAN3#105-Bis | R3-196192 |      |     |     | Add RRC message Transfer related procedures with corresponding tabular                                                                                                             | 0.1.0       |
+| 2019-11        | RAN3#106     | R3-197262 |      |     |     | - Terminology change to ng-eNB-CU, ng-eNB-DU (R3-197635)<br>- pCR to 37.473 on ASN.1 completion (R3-197544)<br>- pCR to 37.473 on miscellaneous correction to contexts (R3-197636) | 1.1.0       |
+| 2019-12        | RP-86        | RP-192962 |      |     |     | TS submitted to TSG RAN plenary for approval                                                                                                                                       | 1.2.0       |
+| 2019-12        | RP-86        |           |      |     |     | TS approved TSG RAN plenary                                                                                                                                                        | 16.0.0      |
+| 2020-03        | RP-86        |           |      |     |     | Correction to the specification title (E1AP ==> W1AP)                                                                                                                              | 16.0.1      |
+| 2020-03        | RP-87-e      | RP-200429 | 0001 | 2   | F   | Miscellaneous corrections to 37.473                                                                                                                                                | 16.1.0      |
+| 2020-07        | RP-88-e      | RP-201084 | 0002 | 1   | F   | Miscellaneous corrections to 37.473                                                                                                                                                | 16.2.0      |
+| 2020-09        | RP-89-e      | RP-201948 | 0003 | 1   | F   | Corrections to encoding PLMNs in served cell information                                                                                                                           | 16.3.0      |
+| 2020-09        | RP-89-e      | RP-201948 | 0004 | -   | F   | Miscellaneous clean-ups to 37.473                                                                                                                                                  | 16.3.0      |
+| 2020-09        | RP-89-e      | RP-201948 | 0005 | 1   | F   | Correction on PWS related procedure                                                                                                                                                | 16.3.0      |
+| 2021-03        | RP-91-e      | RP-210235 | 0006 | 1   | F   | CR to 37.473 on miscellaneous corrections                                                                                                                                          | 16.4.0      |
+| 2021-06        | RP-92-e      | RP-211314 | 0007 | 2   | F   | CR to 37.473 on MeasGapSharingConfig                                                                                                                                               | 16.5.0      |
+| 2021-06        | RP-92-e      | RP-211314 | 0008 | 2   | F   | Stage-3 CR on SCG release over W1 (Rel-16)                                                                                                                                         | 16.5.0      |
+| 2021-09        | RP-93-e      | RP-211875 | 0010 | -   | F   | Correction on Paging over W1                                                                                                                                                       | 16.6.0      |
+| 2021-09        | RP-93-e      | RP-211875 | 0012 | 1   | F   | Correction to EN-DC definition in W1                                                                                                                                               | 16.6.0      |
+| 2021-12        | RP-94-e      | RP-212861 | 0013 | 1   | F   | Correction on Criticality Diagnostics over W1                                                                                                                                      | 16.7.0      |
+| 2022-03        | RP-95-e      | RP-220274 | 0009 | 5   | F   | Support of dynamic ACL during dual connectivity                                                                                                                                    | 16.8.0      |
+| 2022-06        | RP-96        | RP-221150 | 0014 | -   | F   | W1AP CR for ACL remaining issues                                                                                                                                                   | 16.9.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37544/04238bd6d89845c9012e10d19d0e2b1f_img.jpg b/marked/Rel-16/37_series/37544/04238bd6d89845c9012e10d19d0e2b1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19e7b1c44301c76171df45c907d7ddd1304ee6d3
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/04238bd6d89845c9012e10d19d0e2b1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf90225e62d03e33551b042521b861e0acb35913157f53e9aee9f3964c6be810
+size 21606
diff --git a/marked/Rel-16/37_series/37544/04e646ff9ef67d2f89414607117fd258_img.jpg b/marked/Rel-16/37_series/37544/04e646ff9ef67d2f89414607117fd258_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..29e7790c7a75e2bc995fa991d15f076fdfe43076
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/04e646ff9ef67d2f89414607117fd258_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f23deecb9130213baa3670fa855f60339b8cb8fbbf1ec2b8eeabbee51091a99b
+size 40778
diff --git a/marked/Rel-16/37_series/37544/0e8a9481ac421f11f8cca21fecd5b151_img.jpg b/marked/Rel-16/37_series/37544/0e8a9481ac421f11f8cca21fecd5b151_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a628a4f83b4287441420e1173be4ea5f34fb17d
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/0e8a9481ac421f11f8cca21fecd5b151_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a7c9a3560cb1540e8f72070a4604c6d28cc2899d08333be7be36b53b6449f954
+size 11948
diff --git a/marked/Rel-16/37_series/37544/126e772862105e7d64e4ef3f85a16840_img.jpg b/marked/Rel-16/37_series/37544/126e772862105e7d64e4ef3f85a16840_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb78f129cb313b7c2f0ec86ce2a7dd0e732d52b5
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/126e772862105e7d64e4ef3f85a16840_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5018ea9e8e20bf154b1ac47592df7ea246fff9f8fb93e97a7416930b9262c756
+size 21350
diff --git a/marked/Rel-16/37_series/37544/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg b/marked/Rel-16/37_series/37544/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1432f58832e2d39c1d6f4a318c32995fa5b3b474
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/15fe9d98813f20e61e8f2177ed1b84b4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b0ed71f982c304f3c3e889cce7401db84089730ddc7c840af8951d689b91ab9
+size 23035
diff --git a/marked/Rel-16/37_series/37544/1c578156ee49622ffbdc6b1be40d671c_img.jpg b/marked/Rel-16/37_series/37544/1c578156ee49622ffbdc6b1be40d671c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..400e659e8ad8af205eaa8867215baf0328d98089
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/1c578156ee49622ffbdc6b1be40d671c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3277f4528c928e0a683c0447448ad734732da319bfd2f99bfc9b67795320f415
+size 25604
diff --git a/marked/Rel-16/37_series/37544/20ab59bc10b900f6cf8a34549848bbf4_img.jpg b/marked/Rel-16/37_series/37544/20ab59bc10b900f6cf8a34549848bbf4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7349fd7cbbce7329e4fcdf29dd8add65a5ff03f
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/20ab59bc10b900f6cf8a34549848bbf4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39d62572ddfd4ea758a9ef95512ef361cc2b7a5007de377d2b93f5a5800625bc
+size 10586
diff --git a/marked/Rel-16/37_series/37544/2bec737f6829b7e932b3c2b4cbcc1cb6_img.jpg b/marked/Rel-16/37_series/37544/2bec737f6829b7e932b3c2b4cbcc1cb6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ecf137892b844a46d4d255a984e48a6ef1b10c76
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/2bec737f6829b7e932b3c2b4cbcc1cb6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64b1298cb801c51f6b5f415ff9086633e964b0b9dc2afa4c33ca90b46fcc22f3
+size 14942
diff --git a/marked/Rel-16/37_series/37544/317e0525ef1b2458976c246876f4a948_img.jpg b/marked/Rel-16/37_series/37544/317e0525ef1b2458976c246876f4a948_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c3bee4314177ae12e49569e331a78e923754ec0
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/317e0525ef1b2458976c246876f4a948_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d280fb14e60cf69afabe5edf3cbfd0a8f71905c39af1c109b778d9d25e5e226c
+size 3820
diff --git a/marked/Rel-16/37_series/37544/334cc62d4f043284759925265622d274_img.jpg b/marked/Rel-16/37_series/37544/334cc62d4f043284759925265622d274_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0d12c2524cb0187ec871d6ee9b99988f2cfd75b
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/334cc62d4f043284759925265622d274_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de3bc9e4aaa2a13e283e02785a5e8379894fbe2757136547ac23e94983821631
+size 11247
diff --git a/marked/Rel-16/37_series/37544/38b35511a4152c6ac1260c489ce24c88_img.jpg b/marked/Rel-16/37_series/37544/38b35511a4152c6ac1260c489ce24c88_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94e9ebcf01f1706d9e1f99a513eeda6e5163ee40
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/38b35511a4152c6ac1260c489ce24c88_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:714cbef2cd7cc0ec685ed911b176bab3725fffcf2f75e6d333582bd08b1b343d
+size 25881
diff --git a/marked/Rel-16/37_series/37544/39d598e27d6459d9e6ddfa3d2b0dbf6a_img.jpg b/marked/Rel-16/37_series/37544/39d598e27d6459d9e6ddfa3d2b0dbf6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c71458733a76e28c951a094a6cc32d6646efcbc
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/39d598e27d6459d9e6ddfa3d2b0dbf6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5ca52f28165b10a600b48d3559ffd47b503891e307d3a980f3684e1c7fd1d19a
+size 67104
diff --git a/marked/Rel-16/37_series/37544/3a31a89b46f6eed5da9738f05f81441a_img.jpg b/marked/Rel-16/37_series/37544/3a31a89b46f6eed5da9738f05f81441a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0667d84c10e80af828af1a570f72614f78f09ff9
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/3a31a89b46f6eed5da9738f05f81441a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3a57e5383f5023874d304ebd811dd6e5433102cc39febdd88e458d4db194f070
+size 19000
diff --git a/marked/Rel-16/37_series/37544/3d6d0738981fdd03d003cc653bdfdaae_img.jpg b/marked/Rel-16/37_series/37544/3d6d0738981fdd03d003cc653bdfdaae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d15c0bd2226d9f588908e9e386b015c9faf4a0b4
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/3d6d0738981fdd03d003cc653bdfdaae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c44dfb4b5e686cf82cacf3f1db7fa28e1f88bff0d993866df3140da5db69c478
+size 16039
diff --git a/marked/Rel-16/37_series/37544/453f919ec7eafd7de9131995c5b575df_img.jpg b/marked/Rel-16/37_series/37544/453f919ec7eafd7de9131995c5b575df_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5617daaf2955cb3a94e2d2a3a6577e288402c042
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/453f919ec7eafd7de9131995c5b575df_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d83de7f91f5f4e9af3cd7cd067608c3ed6e5e8547c8939ccc905c11061d42335
+size 10935
diff --git a/marked/Rel-16/37_series/37544/4619b5926b94319fabe72a41d1c70e41_img.jpg b/marked/Rel-16/37_series/37544/4619b5926b94319fabe72a41d1c70e41_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74400e0f0ef79be9b4f83234ef1c3bbb943c6091
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/4619b5926b94319fabe72a41d1c70e41_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdd1ba20988705bd951bcaa01d19e499fa5ca2b1fc9a69c62509e8b4bb110ad2
+size 11616
diff --git a/marked/Rel-16/37_series/37544/47986c416bf25e0ac912000ff02b358c_img.jpg b/marked/Rel-16/37_series/37544/47986c416bf25e0ac912000ff02b358c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c573863b96d85b55a35d73fbcf26b945fc7a3f6
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/47986c416bf25e0ac912000ff02b358c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ef4f1cfc9f7aebc6b46b200430de51322b175474756d60ebb550ca68bee3681
+size 38996
diff --git a/marked/Rel-16/37_series/37544/4842ec5b5670793e4458e671372f1764_img.jpg b/marked/Rel-16/37_series/37544/4842ec5b5670793e4458e671372f1764_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef4dde447195c01d6f4203349ad5a3ba0e3e7340
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/4842ec5b5670793e4458e671372f1764_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:394951aab0321305c13acb0d883780a94f53959972db3e94f891f032d9916ba1
+size 10815
diff --git a/marked/Rel-16/37_series/37544/4e69c7905b279b3264a2f0a4a9fcea4c_img.jpg b/marked/Rel-16/37_series/37544/4e69c7905b279b3264a2f0a4a9fcea4c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..372a3217919261b05b6bc7462ffee20ba76488b8
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/4e69c7905b279b3264a2f0a4a9fcea4c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7167d854915cc9aec35dfef626552bc7a98734a98909806dad0a18c9aad09649
+size 42937
diff --git a/marked/Rel-16/37_series/37544/5756508641ee599941f6d1e85de7e84b_img.jpg b/marked/Rel-16/37_series/37544/5756508641ee599941f6d1e85de7e84b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3e4687daf497689aabb05528b0f35587f24b7be
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/5756508641ee599941f6d1e85de7e84b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:96dd434f595c5db11e0457a502e54ef6d97806c62e7dc9a4ad00bcaf5c9d33db
+size 42705
diff --git a/marked/Rel-16/37_series/37544/5df95034215ad869eca4339a0e7535d0_img.jpg b/marked/Rel-16/37_series/37544/5df95034215ad869eca4339a0e7535d0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be89dacc4e675544d71d2474cb93574943434480
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/5df95034215ad869eca4339a0e7535d0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a3b912ca7eccda03a61d9ef4cd1b88a8bd270aceba91172b7e7167db2c07640c
+size 28547
diff --git a/marked/Rel-16/37_series/37544/69a9b36d36809dceaee1dd5b3471d06f_img.jpg b/marked/Rel-16/37_series/37544/69a9b36d36809dceaee1dd5b3471d06f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b25c0691f51c5343489efc767f4b4e1e9d48f3e
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/69a9b36d36809dceaee1dd5b3471d06f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65453e90fd82af2f6bb08578f0885ec017cbfa96e3f0236dd9d7eb874d5939ff
+size 34992
diff --git a/marked/Rel-16/37_series/37544/6b09ea79b2359d93ef696a0aff7095c4_img.jpg b/marked/Rel-16/37_series/37544/6b09ea79b2359d93ef696a0aff7095c4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9cfb5acb3f6b52c98c7de5af05ba189afd40b4dd
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/6b09ea79b2359d93ef696a0aff7095c4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb45f869b811af95930a7a5f562c5d60ace18b36055dc5527ffc97f687b81fbc
+size 12459
diff --git a/marked/Rel-16/37_series/37544/6c15b3646c84efa0bf1374ca87ef74f8_img.jpg b/marked/Rel-16/37_series/37544/6c15b3646c84efa0bf1374ca87ef74f8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4526323dd20ff60e663f865c28bea3e7bc1221aa
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/6c15b3646c84efa0bf1374ca87ef74f8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45cf89b5338fc9f054e5aac9bb83fe29e20543daec161af816c3b86bd814e4a5
+size 10529
diff --git a/marked/Rel-16/37_series/37544/6d54943c64ae4af089cb9e98a78d0af7_img.jpg b/marked/Rel-16/37_series/37544/6d54943c64ae4af089cb9e98a78d0af7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd83e24078cf3245b5e280530436db93f4b335d5
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/6d54943c64ae4af089cb9e98a78d0af7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02310bae45ba7212b2086b3c9d3490863c125b5306f02eb6c5c0dd9f5a505d7a
+size 37180
diff --git a/marked/Rel-16/37_series/37544/6e10326caf39add89e2f9358de953e4f_img.jpg b/marked/Rel-16/37_series/37544/6e10326caf39add89e2f9358de953e4f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75746645181d37a6b159fc82764e9954ca9503db
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/6e10326caf39add89e2f9358de953e4f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c7294870a61552f4912a0fe5fe4f39e975c9a7c41c14ca79fef17416bdb3c78
+size 47897
diff --git a/marked/Rel-16/37_series/37544/72a946916e42493c2568252c21ba02c6_img.jpg b/marked/Rel-16/37_series/37544/72a946916e42493c2568252c21ba02c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d0768396c59caa986a3089e89bacd1ca86877617
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/72a946916e42493c2568252c21ba02c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5bfed3a1e6af69ae8fb597865dea8b514742a036ed07376a3d557533f1974985
+size 10493
diff --git a/marked/Rel-16/37_series/37544/74a97a8834e7fb1c7f60c03d53136b84_img.jpg b/marked/Rel-16/37_series/37544/74a97a8834e7fb1c7f60c03d53136b84_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed60030bf0e68c3c0c7715860261f72c451e6b8e
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/74a97a8834e7fb1c7f60c03d53136b84_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44c3fbd4837013558c3704c55b19991a4f18d35d303df0e96f8308c738ade916
+size 22250
diff --git a/marked/Rel-16/37_series/37544/7c320c137b880b30ff882c610c458aa1_img.jpg b/marked/Rel-16/37_series/37544/7c320c137b880b30ff882c610c458aa1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fbe7942d266cdbf36cbfed6fd73149b1d3d6fb3
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/7c320c137b880b30ff882c610c458aa1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5996546a363bd6b70a9eff02b0d94f6f11e22fd11ad665d030a752758f37bba7
+size 44086
diff --git a/marked/Rel-16/37_series/37544/8732d25aaca63ddbc0eb0f684de815e2_img.jpg b/marked/Rel-16/37_series/37544/8732d25aaca63ddbc0eb0f684de815e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0f968980068375137f5ed4d3ea6ad69ed68aa09f
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/8732d25aaca63ddbc0eb0f684de815e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec1da447f62999e1d1c0ff12e0fd7680be881d27ba62cc1abb704ddb600e8db9
+size 10546
diff --git a/marked/Rel-16/37_series/37544/8f78b5d84dca49cf2769440c7942a27d_img.jpg b/marked/Rel-16/37_series/37544/8f78b5d84dca49cf2769440c7942a27d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..319bb024adcebeaf41bb3eb23045c3c0bd2fae42
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/8f78b5d84dca49cf2769440c7942a27d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de3c8c3948ae6d3862c2c82bc5c5e0d4a567a1d987e96a6831256dbd25686367
+size 57836
diff --git a/marked/Rel-16/37_series/37544/9507bf8a743ef8e70785692053d75e7c_img.jpg b/marked/Rel-16/37_series/37544/9507bf8a743ef8e70785692053d75e7c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10408689ccdd788c062204932c5e2b933c6233d5
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/9507bf8a743ef8e70785692053d75e7c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d9d927a54194b88f8104cdcd4a815960499a2cfffa8af0fe33b1543a4f2931f
+size 74913
diff --git a/marked/Rel-16/37_series/37544/ab64fc3a5efc3f8eeefbea4dad1697ea_img.jpg b/marked/Rel-16/37_series/37544/ab64fc3a5efc3f8eeefbea4dad1697ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..592726e17ae8efa036dd072f044d86018ef6478b
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/ab64fc3a5efc3f8eeefbea4dad1697ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:63c25a6025046803e2cf52d633649d78eb77d7dd301bb591d66277e57c8dd826
+size 14465
diff --git a/marked/Rel-16/37_series/37544/ab9daa86203d0b410e0a01f588a2f9ca_img.jpg b/marked/Rel-16/37_series/37544/ab9daa86203d0b410e0a01f588a2f9ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e411a131e8250c8a5299e7bbd4106896ddce07fe
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/ab9daa86203d0b410e0a01f588a2f9ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00ea29496681d0acdc9af8de5817beda688c8917a0fe1259757b855725a3ccd3
+size 71523
diff --git a/marked/Rel-16/37_series/37544/acd747438ff021665cd3613c06b661d4_img.jpg b/marked/Rel-16/37_series/37544/acd747438ff021665cd3613c06b661d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5cef1139b247f03b48eed0026dd48887149d5676
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/acd747438ff021665cd3613c06b661d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:07d95f610055483c246f1ff89f6ecf5c8ebfb1c25cd8f6ff2addd6e5a014827d
+size 28728
diff --git a/marked/Rel-16/37_series/37544/af8f53cc5b2ff75aef3871a39964bc9b_img.jpg b/marked/Rel-16/37_series/37544/af8f53cc5b2ff75aef3871a39964bc9b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c0db8bd7f8b68f81022fb7fd0a26b0b950e47106
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/af8f53cc5b2ff75aef3871a39964bc9b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff1c2da966e0485c8ec4e9d5fe3804a84e8f77835b24594861f2e3b7e854525b
+size 17173
diff --git a/marked/Rel-16/37_series/37544/b038de46b62ad59f030ec5a0501673e1_img.jpg b/marked/Rel-16/37_series/37544/b038de46b62ad59f030ec5a0501673e1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f3bb68f41273acc3c1f73479314ebc6f061aff2
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b038de46b62ad59f030ec5a0501673e1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef340dcc092b24bb88942a888504bc513a153ffa168ba65e5bd2d7e83e1c9afd
+size 15438
diff --git a/marked/Rel-16/37_series/37544/b2104007a82f0ebebd231761342dc089_img.jpg b/marked/Rel-16/37_series/37544/b2104007a82f0ebebd231761342dc089_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35184e23b8be230f81aded88b465ae82dd669143
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b2104007a82f0ebebd231761342dc089_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:287e218a460a9a3063da78fdd4f3b2e528ab0d969fc3e1dac8345f6a7acfcfc2
+size 68393
diff --git a/marked/Rel-16/37_series/37544/b2448ec0a23090beb4402121beeff751_img.jpg b/marked/Rel-16/37_series/37544/b2448ec0a23090beb4402121beeff751_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d967425fc90e1ee3f772100e59ef35ec168201ab
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b2448ec0a23090beb4402121beeff751_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9c78a294e035275b3c84849b78389b29a7f08ade431c24c128649c2f10f2946
+size 40866
diff --git a/marked/Rel-16/37_series/37544/b48930dacaf1c87ed6bb9a53c27c20d5_img.jpg b/marked/Rel-16/37_series/37544/b48930dacaf1c87ed6bb9a53c27c20d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77ea103fc220e6d5331f00e91148cdc13ad45e24
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b48930dacaf1c87ed6bb9a53c27c20d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:132436065ecc0e59bfd2107f058791394ecd4caf67a6870e35b4bca462d34775
+size 30297
diff --git a/marked/Rel-16/37_series/37544/b6f51e145a04a7d4ade15a5fb94bf872_img.jpg b/marked/Rel-16/37_series/37544/b6f51e145a04a7d4ade15a5fb94bf872_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d5835595f0b46b12d351319295799d8f4928d43c
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b6f51e145a04a7d4ade15a5fb94bf872_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8e390d067f4f24616db1641c3392d0c5689b4c5bca51278a8904229996ef8a0
+size 14950
diff --git a/marked/Rel-16/37_series/37544/b86a2d07eff8e1b76f6eb4a74c3559e9_img.jpg b/marked/Rel-16/37_series/37544/b86a2d07eff8e1b76f6eb4a74c3559e9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5db63bd4038c1810db210719755ee97413e9732
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b86a2d07eff8e1b76f6eb4a74c3559e9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a9db07b7a68fd13acfbc7a5215518079ae6a12718e0d0f78072b2e3341bcf83
+size 11075
diff --git a/marked/Rel-16/37_series/37544/b8d1d78473c7e0df5d8059f40629021a_img.jpg b/marked/Rel-16/37_series/37544/b8d1d78473c7e0df5d8059f40629021a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..884975948b0f0ca31d2afaed25fb4c039fcae205
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b8d1d78473c7e0df5d8059f40629021a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a448d0c5944dfa0a5bced54546e37c12bc91b5ccc445fec919f4b894be98d9d
+size 26467
diff --git a/marked/Rel-16/37_series/37544/b96be3d7d73fc1d7af1879bb57de1cc4_img.jpg b/marked/Rel-16/37_series/37544/b96be3d7d73fc1d7af1879bb57de1cc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9dd1ecd1c2b54206d860ebc6dbe0dd4a661e9ab4
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/b96be3d7d73fc1d7af1879bb57de1cc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:645c232db85a2c304cf49b031680683c8ff8231876c039a47cf32a6d705735f8
+size 42710
diff --git a/marked/Rel-16/37_series/37544/bb3057eb5987c035bdad3cfe2c8e78c5_img.jpg b/marked/Rel-16/37_series/37544/bb3057eb5987c035bdad3cfe2c8e78c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf25263dab39196f8d8f8641623c6121ea4dbb2f
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/bb3057eb5987c035bdad3cfe2c8e78c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92122241eda53bbdfdd4634cf7fe87dca349f379a3244679de0b8c19e422b356
+size 22373
diff --git a/marked/Rel-16/37_series/37544/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg b/marked/Rel-16/37_series/37544/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bea3dd90acbcefc65f78aa0ae0315ab3340a5330
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/bf4c705bba1ea48c6e9cace4844d01c4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:113eac27aa6f2f62ee3122167b7d629f742d0e3c9680f8d33c5a3cb99215b87b
+size 54578
diff --git a/marked/Rel-16/37_series/37544/c2749f79dd1fc9bd2dce52bcbb2fb3ef_img.jpg b/marked/Rel-16/37_series/37544/c2749f79dd1fc9bd2dce52bcbb2fb3ef_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..068991a5107f7c62ef4358f969037beac0867972
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/c2749f79dd1fc9bd2dce52bcbb2fb3ef_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5216ab85f76f67c4182d72715c98d0699416d90d7349b66e1d4e2d8b71c9a9dc
+size 19983
diff --git a/marked/Rel-16/37_series/37544/c27721d296aa2f83230446e4d4ddc766_img.jpg b/marked/Rel-16/37_series/37544/c27721d296aa2f83230446e4d4ddc766_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..623d35b7a365e7cdbf4db560d24575a786cf60ce
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/c27721d296aa2f83230446e4d4ddc766_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14a179b5dd1bb45fd679d5231997abf0d4ae83649a05e8bad9afab85965fa713
+size 11562
diff --git a/marked/Rel-16/37_series/37544/c613ca237231251d524291a877d91f7a_img.jpg b/marked/Rel-16/37_series/37544/c613ca237231251d524291a877d91f7a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1c1db06c71b328e0e1ceb8cb56907a78f536ef7
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/c613ca237231251d524291a877d91f7a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:130b57992da1453a1cba161126e22b0bae2f2d2981b4253f0c25cdc6fa2df688
+size 23096
diff --git a/marked/Rel-16/37_series/37544/c90c97412b6b575e746e8ac7ed5ce791_img.jpg b/marked/Rel-16/37_series/37544/c90c97412b6b575e746e8ac7ed5ce791_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..333cb60d5414d9e4e1af0616e7bef5f918da9f5c
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/c90c97412b6b575e746e8ac7ed5ce791_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59308a0ea26e1fcbb2239ad9e4998b6f7a51cbb3c9e47bbe8d03323d09d371bf
+size 19122
diff --git a/marked/Rel-16/37_series/37544/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg b/marked/Rel-16/37_series/37544/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3f7c2ab64ee8ce51abfe32438714bc47b08e1e40
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c044ed7330b373477342a17a62a38ab88a45c295c865d37aa7c7cf16b579bc59
+size 26495
diff --git a/marked/Rel-16/37_series/37544/d740ca3c4110579e86de4400c75a06e5_img.jpg b/marked/Rel-16/37_series/37544/d740ca3c4110579e86de4400c75a06e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0d661acb6116aaab82125ff66c7c9c4a20f29e07
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/d740ca3c4110579e86de4400c75a06e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf93630b492deb9a44b8ab1338234cf8b7763068801cfc91de726b2fd0d24719
+size 8661
diff --git a/marked/Rel-16/37_series/37544/de59a02f54f1fb9194f5fc07ba908a03_img.jpg b/marked/Rel-16/37_series/37544/de59a02f54f1fb9194f5fc07ba908a03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e17e0e96192154905decf35fb78bd5337879a065
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/de59a02f54f1fb9194f5fc07ba908a03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3792182f21edcb505f9ced3c9021fa9f943b038bdaf8b15dbe870fc4e875e830
+size 15633
diff --git a/marked/Rel-16/37_series/37544/deaac997fd7ecee678c1d3be47d15ad7_img.jpg b/marked/Rel-16/37_series/37544/deaac997fd7ecee678c1d3be47d15ad7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41720d5ea1c61845f79acf7c97356f1a99725cce
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/deaac997fd7ecee678c1d3be47d15ad7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:faa88d41d840459a2f4e3caa43ace46a3ec8c8322dac6d67f5db8ba7d8a22326
+size 57826
diff --git a/marked/Rel-16/37_series/37544/dee129640d21ff8f138d0bb906c2d7dc_img.jpg b/marked/Rel-16/37_series/37544/dee129640d21ff8f138d0bb906c2d7dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f51fa7365865529098b695806ab1690d4360c421
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/dee129640d21ff8f138d0bb906c2d7dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:211094c1d2f2b63bf71a9aeaaad0b3c3b12f9172db5286689f38d977c9ac9520
+size 11730
diff --git a/marked/Rel-16/37_series/37544/ef8b77a6abdfed4dfe556d2fe12caafd_img.jpg b/marked/Rel-16/37_series/37544/ef8b77a6abdfed4dfe556d2fe12caafd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7e41e9bbf3bd23885ab999c63eefe7a1c3f2dc3
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/ef8b77a6abdfed4dfe556d2fe12caafd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b9582664fc32080e81964a11abc8401fb30bc40bc714b3f1881d6a31f36290f
+size 54372
diff --git a/marked/Rel-16/37_series/37544/raw.md b/marked/Rel-16/37_series/37544/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..91de76475c9ad9091194a9220b25ea0b1f1e0b38
--- /dev/null
+++ b/marked/Rel-16/37_series/37544/raw.md
@@ -0,0 +1,9760 @@
+
+
+
+
+![](317e0525ef1b2458976c246876f4a948_img.jpg)
+
+---
+
+# Contents
+
+|                                                                                                                                 |    |
+|---------------------------------------------------------------------------------------------------------------------------------|----|
+| Foreword.....                                                                                                                   | 14 |
+| 1 Scope.....                                                                                                                    | 15 |
+| 2 References.....                                                                                                               | 15 |
+| 3 Definitions, symbols and abbreviations.....                                                                                   | 17 |
+| 3.1 Definitions.....                                                                                                            | 17 |
+| 3.2 Symbols.....                                                                                                                | 17 |
+| 3.3 Abbreviations.....                                                                                                          | 18 |
+| 4 General.....                                                                                                                  | 19 |
+| 4.1 Terminal classes.....                                                                                                       | 20 |
+| 4.1.1 Mechanical modes.....                                                                                                     | 20 |
+| 4.2 UTRA chip rates.....                                                                                                        | 20 |
+| 4.3 DUT positioning.....                                                                                                        | 20 |
+| 4.3.1 DUT positioning for Speech Mode with beside the Head Phantom.....                                                         | 20 |
+| 4.3.2 DUT positioning for LMEs on Laptop Ground Plane Phantom.....                                                              | 21 |
+| 4.3.3 DUT positioning for Speech Mode with beside the Head and Hand Phantom.....                                                | 21 |
+| 4.3.3.1 General.....                                                                                                            | 21 |
+| 4.3.3.2 Mono-blocks and closed sliders.....                                                                                     | 22 |
+| 4.3.3.3 Folds and open-slides.....                                                                                              | 23 |
+| 4.3.3.4 PDA.....                                                                                                                | 23 |
+| 4.3.4 DUT positioning for Browsing Mode with Hand Phantom.....                                                                  | 24 |
+| 4.3.4.1 General.....                                                                                                            | 24 |
+| 4.3.4.2 Narrow DUT.....                                                                                                         | 24 |
+| 4.3.4.3 PDA.....                                                                                                                | 25 |
+| 4.3.5 DUT positioning for devices with embedded modules.....                                                                    | 25 |
+| 4.3.6 DUT positioning for total radiated multi-antenna sensitivity.....                                                         | 25 |
+| 4.3.6.1 Handheld UE – Free Space.....                                                                                           | 25 |
+| 4.3.6.1.1 MPAC Positioning Guidelines.....                                                                                      | 26 |
+| 4.3.6.1.2 RTS Positioning Guidelines.....                                                                                       | 26 |
+| 4.4 Sampling grid.....                                                                                                          | 26 |
+| 4.5 Number of independent samples (for reverberation chamber procedure).....                                                    | 26 |
+| 5 Measurement frequencies.....                                                                                                  | 26 |
+| 5.1 UTRA FDD frequency bands and measurement channels.....                                                                      | 26 |
+| 5.2 UTRA TDD frequency bands and measurement channels.....                                                                      | 27 |
+| 5.3 E-UTRA FDD frequency bands and measurement frequencies allocations.....                                                     | 28 |
+| 5.4 E-UTRA TDD frequency bands and measurement frequencies allocations.....                                                     | 33 |
+| 5.5 E-UTRA FDD operating bands and measurement frequency allocations for receiver total radiated multi-antenna sensitivity..... | 35 |
+| 5.6 E-UTRA TDD operating bands and measurement frequency allocations for receiver total radiated multi-antenna sensitivity..... | 37 |
+| 6 Transmitter Performance.....                                                                                                  | 38 |
+| 6.1 Performance for handheld UE.....                                                                                            | 38 |
+| 6.1.1 Total Radiated Power (TRP) for UTRA FDD in Speech Mode with beside the Head Phantom.....                                  | 38 |
+| 6.1.1.1 Definition and applicability.....                                                                                       | 38 |
+| 6.1.1.2 Minimum Requirements.....                                                                                               | 39 |
+| 6.1.1.3 Test purpose.....                                                                                                       | 39 |
+| 6.1.1.4 Method of test.....                                                                                                     | 39 |
+| 6.1.1.4.1 Initial conditions.....                                                                                               | 39 |
+| 6.1.1.4.2 Procedure.....                                                                                                        | 40 |
+| 6.1.1.4.3 Procedure, reverberation chamber method.....                                                                          | 40 |
+| 6.1.1.5 Test requirements.....                                                                                                  | 41 |
+| 6.1.2 Total Radiated Power (TRP) for UTRA LCR TDD in Speech Mode with beside the Head Phantom.....                              | 41 |
+| 6.1.2.1 Definition and applicability.....                                                                                       | 42 |
+| 6.1.2.2 Minimum Requirements.....                                                                                               | 42 |
+| 6.1.2.3 Test purpose.....                                                                                                       | 43 |
+| 6.1.2.4 Method of test.....                                                                                                     | 43 |
+
+|           |                                                                                                       |    |
+|-----------|-------------------------------------------------------------------------------------------------------|----|
+| 6.1.2.4.1 | Initial conditions.....                                                                               | 43 |
+| 6.1.2.4.2 | Procedure.....                                                                                        | 44 |
+| 6.1.2.4.3 | Procedure, reverberation chamber method.....                                                          | 44 |
+| 6.1.2.5   | Test requirements.....                                                                                | 44 |
+| 6.1.3     | Total Radiated Power (TRP) for UTRA FDD in Speech Mode with beside the Head and Hand Phantom.....     | 45 |
+| 6.1.3.1   | Definition and applicability.....                                                                     | 45 |
+| 6.1.3.2   | Minimum Requirements.....                                                                             | 46 |
+| 6.1.3.3   | Test purpose.....                                                                                     | 47 |
+| 6.1.3.4   | Method of test.....                                                                                   | 47 |
+| 6.1.3.4.1 | Initial conditions.....                                                                               | 47 |
+| 6.1.3.4.2 | Procedure.....                                                                                        | 47 |
+| 6.1.3.4.3 | Procedure, reverberation chamber method.....                                                          | 48 |
+| 6.1.3.5   | Test requirements.....                                                                                | 48 |
+| 6.1.4     | Total Radiated Power (TRP) for UTRA LCR TDD in Speech Mode with beside the Head and Hand Phantom..... | 49 |
+| 6.1.4.1   | Definition and applicability.....                                                                     | 49 |
+| 6.1.4.2   | Minimum Requirements.....                                                                             | 50 |
+| 6.1.4.3   | Test purpose.....                                                                                     | 51 |
+| 6.1.4.4   | Method of test.....                                                                                   | 51 |
+| 6.1.4.4.1 | Initial conditions.....                                                                               | 51 |
+| 6.1.4.4.2 | Procedure.....                                                                                        | 51 |
+| 6.1.4.4.3 | Procedure, reverberation chamber method.....                                                          | 52 |
+| 6.1.4.5   | Test requirements.....                                                                                | 52 |
+| 6.1.5     | Total Radiated Power (TRP) for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom.....   | 53 |
+| 6.1.5.1   | Definition and applicability.....                                                                     | 53 |
+| 6.1.5.2   | Minimum Requirements.....                                                                             | 55 |
+| 6.1.5.3   | Test purpose.....                                                                                     | 55 |
+| 6.1.5.4   | Method of test.....                                                                                   | 55 |
+| 6.1.5.4.1 | Initial conditions.....                                                                               | 55 |
+| 6.1.5.4.2 | Procedure.....                                                                                        | 56 |
+| 6.1.5.4.3 | Procedure, reverberation chamber method.....                                                          | 56 |
+| 6.1.5.5   | Test requirements.....                                                                                | 56 |
+| 6.1.6     | Total Radiated Power (TRP) for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom.....   | 56 |
+| 6.1.6.1   | Definition and applicability.....                                                                     | 57 |
+| 6.1.6.2   | Minimum Requirements.....                                                                             | 58 |
+| 6.1.6.3   | Test purpose.....                                                                                     | 58 |
+| 6.1.6.4   | Method of test.....                                                                                   | 58 |
+| 6.1.6.4.1 | Initial conditions.....                                                                               | 58 |
+| 6.1.6.4.2 | Procedure.....                                                                                        | 59 |
+| 6.1.6.4.3 | Procedure, reverberation chamber method.....                                                          | 59 |
+| 6.1.6.5   | Test requirements.....                                                                                | 59 |
+| 6.1.7     | Total Radiated Power (TRP) for UTRA FDD in Browsing Mode with Hand Phantom.....                       | 60 |
+| 6.1.7.1   | Definition and applicability.....                                                                     | 60 |
+| 6.1.7.2   | Minimum Requirements.....                                                                             | 61 |
+| 6.1.7.3   | Test purpose.....                                                                                     | 61 |
+| 6.1.7.4   | Method of test.....                                                                                   | 62 |
+| 6.1.7.4.1 | Initial conditions.....                                                                               | 62 |
+| 6.1.7.4.2 | Procedure.....                                                                                        | 62 |
+| 6.1.7.4.3 | Procedure, reverberation chamber method.....                                                          | 63 |
+| 6.1.7.5   | Test requirements.....                                                                                | 63 |
+| 6.1.8     | Total Radiated Power (TRP) for UTRA LCR TDD in Browsing Mode with Hand Phantom.....                   | 63 |
+| 6.1.8.1   | Definition and applicability.....                                                                     | 64 |
+| 6.1.8.2   | Minimum Requirements.....                                                                             | 64 |
+| 6.1.8.3   | Test purpose.....                                                                                     | 65 |
+| 6.1.8.4   | Method of test.....                                                                                   | 65 |
+| 6.1.8.4.1 | Initial conditions.....                                                                               | 65 |
+| 6.1.8.4.2 | Procedure.....                                                                                        | 66 |
+| 6.1.8.4.3 | Procedure, reverberation chamber method.....                                                          | 66 |
+
+|            |                                                                                   |    |
+|------------|-----------------------------------------------------------------------------------|----|
+| 6.1.8.5    | Test requirements.....                                                            | 66 |
+| 6.1.9      | Total Radiated Power (TRP) for E-UTRA FDD in Browsing Mode with Hand Phantom..... | 67 |
+| 6.1.9.1    | Definition and applicability.....                                                 | 67 |
+| 6.1.9.2    | Minimum Requirements.....                                                         | 68 |
+| 6.1.9.3    | Test purpose.....                                                                 | 68 |
+| 6.1.9.4    | Method of test.....                                                               | 68 |
+| 6.1.9.4.1  | Initial conditions.....                                                           | 68 |
+| 6.1.9.4.2  | Procedure.....                                                                    | 69 |
+| 6.1.9.4.3  | Procedure, reverberation chamber method.....                                      | 69 |
+| 6.1.9.5    | Test requirements.....                                                            | 69 |
+| 6.1.10     | Total Radiated Power (TRP) for E-UTRA TDD in Browsing Mode with Hand Phantom..... | 70 |
+| 6.1.10.1   | Definition and applicability.....                                                 | 70 |
+| 6.1.10.2   | Minimum Requirements.....                                                         | 71 |
+| 6.1.10.3   | Test purpose.....                                                                 | 71 |
+| 6.1.10.4   | Method of test.....                                                               | 71 |
+| 6.1.10.4.1 | Initial conditions.....                                                           | 71 |
+| 6.1.10.4.2 | Procedure.....                                                                    | 71 |
+| 6.1.10.4.3 | Procedure, reverberation chamber method.....                                      | 72 |
+| 6.1.10.5   | Test requirements.....                                                            | 72 |
+| 6.2        | Performance for LME.....                                                          | 72 |
+| 6.2.1      | Total Radiated Power (TRP) for UTRA FDD LME.....                                  | 72 |
+| 6.2.1.1    | Definition and applicability.....                                                 | 72 |
+| 6.2.1.2    | Minimum Requirements.....                                                         | 73 |
+| 6.2.1.3    | Test purpose.....                                                                 | 74 |
+| 6.2.1.4    | Method of test.....                                                               | 74 |
+| 6.2.1.4.1  | Initial conditions.....                                                           | 74 |
+| 6.2.1.4.2  | Procedure.....                                                                    | 74 |
+| 6.2.1.4.3  | Procedure, reverberation chamber method.....                                      | 75 |
+| 6.2.1.5    | Test requirements.....                                                            | 75 |
+| 6.2.2      | Total Radiated Power (TRP) for UTRA LCR TDD LME.....                              | 76 |
+| 6.2.2.1    | Definition and applicability.....                                                 | 76 |
+| 6.2.2.2    | Minimum Requirements.....                                                         | 77 |
+| 6.2.2.3    | Test purpose.....                                                                 | 78 |
+| 6.2.2.4    | Method of test.....                                                               | 78 |
+| 6.2.2.4.1  | Initial conditions.....                                                           | 78 |
+| 6.2.2.4.2  | Procedure.....                                                                    | 79 |
+| 6.2.2.4.3  | Procedure, reverberation chamber method.....                                      | 79 |
+| 6.2.2.5    | Test requirements.....                                                            | 80 |
+| 6.2.3      | Total Radiated Power (TRP) for E-UTRA FDD LME.....                                | 80 |
+| 6.2.3.1    | Definition and applicability.....                                                 | 80 |
+| 6.2.3.2    | Minimum Requirements.....                                                         | 81 |
+| 6.2.3.3    | Test purpose.....                                                                 | 82 |
+| 6.2.3.4    | Method of test.....                                                               | 82 |
+| 6.2.3.4.1  | Initial conditions.....                                                           | 82 |
+| 6.2.3.4.2  | Procedure.....                                                                    | 82 |
+| 6.2.3.4.3  | Procedure, reverberation chamber method.....                                      | 82 |
+| 6.2.3.5    | Test requirements.....                                                            | 82 |
+| 6.2.4      | Total Radiated Power (TRP) for E-UTRA TDD LME.....                                | 83 |
+| 6.2.4.1    | Definition and applicability.....                                                 | 83 |
+| 6.2.4.2    | Minimum Requirements.....                                                         | 84 |
+| 6.2.4.3    | Test purpose.....                                                                 | 84 |
+| 6.2.4.4    | Method of test.....                                                               | 84 |
+| 6.2.4.4.1  | Initial conditions.....                                                           | 84 |
+| 6.2.4.4.2  | Procedure.....                                                                    | 85 |
+| 6.2.4.4.3  | Procedure, reverberation chamber method.....                                      | 85 |
+| 6.2.4.5    | Test requirements.....                                                            | 85 |
+| 6.3        | Performance for LEE.....                                                          | 85 |
+| 6.3.1      | Total Radiated Power (TRP) for UTRA FDD LEE.....                                  | 85 |
+| 6.3.1.1    | Definition and applicability.....                                                 | 86 |
+| 6.3.1.2    | Minimum Requirements.....                                                         | 86 |
+| 6.3.1.3    | Test purpose.....                                                                 | 87 |
+
+|           |                                                                                                         |     |
+|-----------|---------------------------------------------------------------------------------------------------------|-----|
+| 6.3.1.4   | Method of test.....                                                                                     | 88  |
+| 6.3.1.4.1 | Initial conditions.....                                                                                 | 88  |
+| 6.3.1.4.2 | Procedure.....                                                                                          | 88  |
+| 6.3.1.4.3 | Procedure, reverberation chamber method.....                                                            | 89  |
+| 6.3.1.5   | Test requirements.....                                                                                  | 89  |
+| 6.3.2     | Total Radiated Power (TRP) for UTRA LCR TDD LEE.....                                                    | 91  |
+| 6.3.2.1   | Definition and applicability.....                                                                       | 91  |
+| 6.3.2.2   | Minimum Requirements.....                                                                               | 92  |
+| 6.3.2.3   | Test purpose.....                                                                                       | 92  |
+| 6.3.2.4   | Method of test.....                                                                                     | 93  |
+| 6.3.2.4.1 | Initial conditions.....                                                                                 | 93  |
+| 6.3.2.4.2 | Procedure.....                                                                                          | 93  |
+| 6.3.2.4.3 | Procedure, reverberation chamber method.....                                                            | 94  |
+| 6.3.2.5   | Test requirements.....                                                                                  | 94  |
+| 6.3.3     | Total Radiated Power (TRP) for E-UTRA FDD LEE.....                                                      | 95  |
+| 6.3.3.1   | Definition and applicability.....                                                                       | 96  |
+| 6.3.3.2   | Minimum Requirements.....                                                                               | 97  |
+| 6.3.3.3   | Test purpose.....                                                                                       | 98  |
+| 6.3.3.4   | Method of test.....                                                                                     | 98  |
+| 6.3.3.4.1 | Initial conditions.....                                                                                 | 98  |
+| 6.3.3.4.2 | Procedure.....                                                                                          | 99  |
+| 6.3.3.4.3 | Procedure, reverberation chamber method.....                                                            | 99  |
+| 6.3.3.5   | Test requirements.....                                                                                  | 99  |
+| 6.3.4     | Total Radiated Power (TRP) for E-UTRA TDD LEE.....                                                      | 100 |
+| 6.3.4.1   | Definition and applicability.....                                                                       | 100 |
+| 6.3.4.2   | Minimum Requirements.....                                                                               | 101 |
+| 6.3.4.3   | Test purpose.....                                                                                       | 102 |
+| 6.3.4.4   | Method of test.....                                                                                     | 102 |
+| 6.3.4.4.1 | Initial conditions.....                                                                                 | 102 |
+| 6.3.4.4.2 | Procedure.....                                                                                          | 103 |
+| 6.3.4.4.3 | Procedure, reverberation chamber method.....                                                            | 103 |
+| 6.3.4.5   | Test requirements.....                                                                                  | 103 |
+| 7         | Receiver Performance.....                                                                               | 104 |
+| 7.1       | Performance for handheld UE.....                                                                        | 104 |
+| 7.1.1     | Total Radiated Sensitivity (TRS) for UTRA FDD in Speech Mode with beside the Head Phantom.....          | 104 |
+| 7.1.1.1   | Definition and applicability.....                                                                       | 104 |
+| 7.1.1.2   | Minimum requirements.....                                                                               | 104 |
+| 7.1.1.3   | Test Purpose.....                                                                                       | 105 |
+| 7.1.1.4   | Method of test.....                                                                                     | 105 |
+| 7.1.1.4.1 | Initial conditions.....                                                                                 | 105 |
+| 7.1.1.4.2 | Test procedure.....                                                                                     | 106 |
+| 7.1.1.4.3 | Test procedure, reverberation chamber method.....                                                       | 106 |
+| 7.1.1.5   | Test requirements.....                                                                                  | 106 |
+| 7.1.2     | Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Speech Mode with beside the Head Phantom.....      | 107 |
+| 7.1.2.1   | Definition and applicability.....                                                                       | 107 |
+| 7.1.2.2   | Minimum Requirements.....                                                                               | 108 |
+| 7.1.2.3   | Test purpose.....                                                                                       | 108 |
+| 7.1.2.4   | Method of test.....                                                                                     | 108 |
+| 7.1.2.4.1 | Initial conditions.....                                                                                 | 108 |
+| 7.1.2.4.2 | Procedure.....                                                                                          | 109 |
+| 7.1.2.4.3 | Procedure, reverberation chamber method.....                                                            | 110 |
+| 7.1.2.5   | Test requirements.....                                                                                  | 110 |
+| 7.1.3     | Total Radiated Sensitivity (TRS) for UTRA FDD in Speech Mode with beside the Head and Hand Phantom..... | 110 |
+| 7.1.3.1   | Definition and applicability.....                                                                       | 110 |
+| 7.1.3.2   | Minimum Requirements.....                                                                               | 111 |
+| 7.1.3.3   | Test purpose.....                                                                                       | 112 |
+| 7.1.3.4   | Method of test.....                                                                                     | 112 |
+| 7.1.3.4.1 | Initial conditions.....                                                                                 | 112 |
+| 7.1.3.4.2 | Procedure.....                                                                                          | 113 |
+
+|           |                                                                                                             |     |
+|-----------|-------------------------------------------------------------------------------------------------------------|-----|
+| 7.1.3.4.3 | Procedure, reverberation chamber method.....                                                                | 113 |
+| 7.1.3.5   | Test requirements.....                                                                                      | 114 |
+| 7.1.4     | Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Speech Mode with beside the Head and Hand Phantom..... | 115 |
+| 7.1.4.1   | Definition and applicability.....                                                                           | 115 |
+| 7.1.4.2   | Minimum Requirements.....                                                                                   | 116 |
+| 7.1.4.3   | Test purpose.....                                                                                           | 117 |
+| 7.1.5.4   | Method of test.....                                                                                         | 117 |
+| 7.1.4.4.1 | Initial conditions.....                                                                                     | 117 |
+| 7.1.4.4.2 | Procedure.....                                                                                              | 118 |
+| 7.1.4.4.3 | Procedure, reverberation chamber method.....                                                                | 118 |
+| 7.1.4.5   | Test requirements.....                                                                                      | 119 |
+| 7.1.5     | Total Radiated Sensitivity (TRS) for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom.....   | 119 |
+| 7.1.5.1   | Definition and applicability.....                                                                           | 119 |
+| 7.1.5.2   | Minimum Requirements.....                                                                                   | 120 |
+| 7.1.5.3   | Test purpose.....                                                                                           | 121 |
+| 7.1.5.4   | Method of test.....                                                                                         | 121 |
+| 7.1.5.4.1 | Initial conditions.....                                                                                     | 121 |
+| 7.1.5.4.2 | Procedure.....                                                                                              | 121 |
+| 7.1.5.4.3 | Procedure, reverberation chamber method.....                                                                | 122 |
+| 7.1.5.5   | Test requirements.....                                                                                      | 122 |
+| 7.1.6     | Total Radiated Sensitivity (TRS) for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom.....   | 122 |
+| 7.1.6.1   | Definition and applicability.....                                                                           | 122 |
+| 7.1.6.2   | Minimum Requirements.....                                                                                   | 123 |
+| 7.1.6.3   | Test purpose.....                                                                                           | 124 |
+| 7.1.6.4   | Method of test.....                                                                                         | 124 |
+| 7.1.6.4.1 | Initial conditions.....                                                                                     | 124 |
+| 7.1.6.4.2 | Procedure.....                                                                                              | 124 |
+| 7.1.6.4.3 | Procedure, reverberation chamber method.....                                                                | 124 |
+| 7.1.6.5   | Test requirements.....                                                                                      | 125 |
+| 7.1.7     | Total Radiated Sensitivity (TRS) for UTRA FDD in Browsing Mode with Hand Phantom.....                       | 125 |
+| 7.1.7.1   | Definition and applicability.....                                                                           | 125 |
+| 7.1.7.2   | Minimum Requirements.....                                                                                   | 126 |
+| 7.1.7.3   | Test purpose.....                                                                                           | 126 |
+| 7.1.7.4   | Method of test.....                                                                                         | 127 |
+| 7.1.7.4.1 | Initial conditions.....                                                                                     | 127 |
+| 7.1.7.4.2 | Procedure.....                                                                                              | 127 |
+| 7.1.7.4.3 | Procedure, reverberation chamber method.....                                                                | 128 |
+| 7.1.7.5   | Test requirements.....                                                                                      | 128 |
+| 7.1.8     | Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Browsing Mode with Hand Phantom.....                   | 129 |
+| 7.1.8.1   | Definition and applicability.....                                                                           | 129 |
+| 7.1.8.2   | Minimum Requirements.....                                                                                   | 129 |
+| 7.1.8.3   | Test purpose.....                                                                                           | 130 |
+| 7.1.8.4   | Method of test.....                                                                                         | 130 |
+| 7.1.8.4.1 | Initial conditions.....                                                                                     | 130 |
+| 7.1.8.4.2 | Procedure.....                                                                                              | 131 |
+| 7.1.8.4.3 | Procedure, reverberation chamber method.....                                                                | 131 |
+| 7.1.8.5   | Test requirements.....                                                                                      | 131 |
+| 7.1.9     | Total Radiated Sensitivity (TRS) for E-UTRA FDD in Browsing Mode with Hand Phantom.....                     | 132 |
+| 7.1.9.1   | Definition and applicability.....                                                                           | 132 |
+| 7.1.9.2   | Minimum Requirements.....                                                                                   | 133 |
+| 7.1.9.3   | Test purpose.....                                                                                           | 133 |
+| 7.1.9.4   | Method of test.....                                                                                         | 133 |
+| 7.1.9.4.1 | Initial conditions.....                                                                                     | 133 |
+| 7.1.9.4.2 | Procedure.....                                                                                              | 133 |
+| 7.1.9.4.3 | Procedure, reverberation chamber method.....                                                                | 134 |
+| 7.1.9.5   | Test requirements.....                                                                                      | 134 |
+| 7.1.10    | Total Radiated Sensitivity (TRS) for E-UTRA TDD in Browsing Mode with Hand Phantom.....                     | 134 |
+| 7.1.10.1  | Definition and applicability.....                                                                           | 134 |
+
+|            |                                                            |     |
+|------------|------------------------------------------------------------|-----|
+| 7.1.10.2   | Minimum Requirements.....                                  | 135 |
+| 7.1.10.3   | Test purpose.....                                          | 135 |
+| 7.1.10.4   | Method of test.....                                        | 135 |
+| 7.1.10.4.1 | Initial conditions.....                                    | 135 |
+| 7.1.10.4.2 | Procedure.....                                             | 136 |
+| 7.1.10.4.3 | Procedure, reverberation chamber method.....               | 136 |
+| 7.1.10.5   | Test requirements.....                                     | 136 |
+| 7.2        | Performance for LME.....                                   | 136 |
+| 7.2.1      | Total Radiated Sensitivity (TRS) for UTRA FDD LME.....     | 136 |
+| 7.2.1.1    | Definition and applicability.....                          | 137 |
+| 7.2.1.2    | Minimum Requirements.....                                  | 137 |
+| 7.2.1.3    | Test purpose.....                                          | 138 |
+| 7.2.1.4    | Method of test.....                                        | 138 |
+| 7.2.1.4.1  | Initial conditions.....                                    | 138 |
+| 7.2.1.4.2  | Procedure.....                                             | 139 |
+| 7.2.1.4.3  | Test procedure, reverberation chamber method.....          | 139 |
+| 7.2.1.5    | Test requirements.....                                     | 139 |
+| 7.2.2      | Total Radiated Sensitivity (TRS) for UTRA LCR TDD LME..... | 140 |
+| 7.2.2.1    | Definition and applicability.....                          | 140 |
+| 7.2.2.2    | Minimum Requirements.....                                  | 141 |
+| 7.2.2.3    | Test purpose.....                                          | 141 |
+| 7.2.2.4    | Method of test.....                                        | 141 |
+| 7.2.2.4.1  | Initial conditions.....                                    | 141 |
+| 7.2.2.4.2  | Procedure.....                                             | 142 |
+| 7.2.2.4.3  | Test procedure, reverberation chamber method.....          | 143 |
+| 7.2.2.5    | Test requirements.....                                     | 143 |
+| 7.2.3      | Total Radiated Sensitivity (TRS) for E-UTRA FDD LME.....   | 143 |
+| 7.2.3.1    | Definition and applicability.....                          | 143 |
+| 7.2.3.2    | Minimum Requirements.....                                  | 144 |
+| 7.2.3.3    | Test purpose.....                                          | 144 |
+| 7.2.3.4    | Method of test.....                                        | 144 |
+| 7.2.3.4.1  | Initial conditions.....                                    | 144 |
+| 7.2.3.4.2  | Procedure.....                                             | 145 |
+| 7.2.3.4.3  | Procedure, reverberation chamber method.....               | 145 |
+| 7.2.3.5    | Test requirements.....                                     | 145 |
+| 7.2.4      | Total Radiated Sensitivity (TRS) for E-UTRA TDD LME.....   | 145 |
+| 7.2.4.1    | Definition and applicability.....                          | 146 |
+| 7.2.4.2    | Minimum Requirements.....                                  | 146 |
+| 7.2.4.3    | Test purpose.....                                          | 146 |
+| 7.2.4.4    | Method of test.....                                        | 147 |
+| 7.2.4.4.1  | Initial conditions.....                                    | 147 |
+| 7.2.4.4.2  | Procedure.....                                             | 147 |
+| 7.2.4.4.3  | Procedure, reverberation chamber method.....               | 147 |
+| 7.2.4.5    | Test requirements.....                                     | 147 |
+| 7.3        | Performance for LEE.....                                   | 148 |
+| 7.3.1      | Total Radiated Sensitivity (TRS) for UTRA FDD LEE.....     | 148 |
+| 7.3.1.1    | Definition and applicability.....                          | 148 |
+| 7.3.1.2    | Minimum Requirements.....                                  | 149 |
+| 7.3.1.3    | Test purpose.....                                          | 150 |
+| 7.3.1.4    | Method of test.....                                        | 150 |
+| 7.3.1.4.1  | Initial conditions.....                                    | 150 |
+| 7.3.1.4.2  | Procedure.....                                             | 151 |
+| 7.3.1.4.3  | Procedure, reverberation chamber method.....               | 151 |
+| 7.3.1.5    | Test requirements.....                                     | 152 |
+| 7.3.2      | Total Radiated Sensitivity (TRS) for UTRA LCR TDD LEE..... | 153 |
+| 7.3.2.1    | Definition and applicability.....                          | 153 |
+| 7.3.2.2    | Minimum Requirements.....                                  | 154 |
+| 7.3.2.3    | Test purpose.....                                          | 155 |
+| 7.3.2.4    | Method of test.....                                        | 155 |
+| 7.3.2.4.1  | Initial conditions.....                                    | 155 |
+| 7.3.2.4.2  | Procedure.....                                             | 156 |
+
+|                                                                                              |                                                                                                   |            |
+|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------|
+| 7.3.2.4.3                                                                                    | Procedure, reverberation chamber method.....                                                      | 156        |
+| 7.3.2.5                                                                                      | Test requirements.....                                                                            | 157        |
+| 7.3.3                                                                                        | Total Radiated Sensitivity (TRS) for E-UTRA FDD LEE.....                                          | 158        |
+| 7.3.3.1                                                                                      | Definition and applicability.....                                                                 | 158        |
+| 7.3.3.2                                                                                      | Minimum Requirements.....                                                                         | 159        |
+| 7.3.3.3                                                                                      | Test purpose.....                                                                                 | 160        |
+| 7.3.3.4                                                                                      | Method of test.....                                                                               | 160        |
+| 7.3.3.4.1                                                                                    | Initial conditions.....                                                                           | 160        |
+| 7.3.3.4.2                                                                                    | Procedure.....                                                                                    | 161        |
+| 7.3.3.4.3                                                                                    | Procedure, reverberation chamber method.....                                                      | 161        |
+| 7.3.3.5                                                                                      | Test requirements.....                                                                            | 161        |
+| 7.3.4                                                                                        | Total Radiated Sensitivity (TRS) for E-UTRA TDD LEE.....                                          | 162        |
+| 7.3.4.1                                                                                      | Definition and applicability.....                                                                 | 162        |
+| 7.3.4.2                                                                                      | Minimum Requirements.....                                                                         | 163        |
+| 7.3.4.3                                                                                      | Test purpose.....                                                                                 | 163        |
+| 7.3.5.4                                                                                      | Method of test.....                                                                               | 164        |
+| 7.3.4.4.1                                                                                    | Initial conditions.....                                                                           | 164        |
+| 7.3.4.4.2                                                                                    | Procedure.....                                                                                    | 164        |
+| 7.3.4.4.3                                                                                    | Procedure, reverberation chamber method.....                                                      | 164        |
+| 7.3.4.5                                                                                      | Test requirements.....                                                                            | 164        |
+| 7.4                                                                                          | Radiated Performance of Multiple-antenna Receivers in the UE.....                                 | 165        |
+| 7.4.1                                                                                        | Total Radiated Multi-antenna Sensitivity (TRMS) for E-UTRA FDD for Handheld UE in Free Space..... | 165        |
+| 7.4.1.1                                                                                      | Definition and applicability.....                                                                 | 165        |
+| 7.4.1.2                                                                                      | Minimum requirements.....                                                                         | 166        |
+| 7.4.1.3                                                                                      | Test Purpose.....                                                                                 | 166        |
+| 7.4.1.4                                                                                      | Method of test for Multi-probe Anechoic Chamber.....                                              | 166        |
+| 7.4.1.4.1                                                                                    | Initial conditions.....                                                                           | 166        |
+| 7.4.1.4.2                                                                                    | Procedure.....                                                                                    | 167        |
+| 7.4.1.4A                                                                                     | Method of test for Radiated Two-Stage.....                                                        | 167        |
+| 7.4.1.4A.1                                                                                   | Initial conditions.....                                                                           | 168        |
+| 7.4.1.4A.2                                                                                   | Procedure.....                                                                                    | 168        |
+| 7.4.1.5                                                                                      | Test requirements.....                                                                            | 169        |
+| 7.4.2                                                                                        | Total Radiated Multi-antenna Sensitivity (TRMS) for E-UTRA TDD for Handheld UE in Free Space..... | 169        |
+| 7.4.2.1                                                                                      | Definition and applicability.....                                                                 | 169        |
+| 7.4.2.2                                                                                      | Minimum requirements.....                                                                         | 170        |
+| 7.4.2.3                                                                                      | Test Purpose.....                                                                                 | 170        |
+| 7.4.2.4                                                                                      | Method of test for Multi-probe Anechoic Chamber.....                                              | 170        |
+| 7.4.2.4.1                                                                                    | Initial conditions.....                                                                           | 170        |
+| 7.4.2.4.2                                                                                    | Procedure.....                                                                                    | 171        |
+| 7.4.2.4A                                                                                     | Method of test for Radiated Two-Stage.....                                                        | 172        |
+| 7.4.2.4A.1                                                                                   | Initial conditions.....                                                                           | 172        |
+| 7.4.2.4A.2                                                                                   | Procedure.....                                                                                    | 172        |
+| 7.4.2.5                                                                                      | Test requirements.....                                                                            | 173        |
+| <b>Annex A (normative): Test system characterization and environmental requirements.....</b> |                                                                                                   | <b>174</b> |
+| A.1                                                                                          | General.....                                                                                      | 174        |
+| A.2                                                                                          | Phantom specifications.....                                                                       | 174        |
+| A.2.1                                                                                        | Head phantom.....                                                                                 | 174        |
+| A.2.2                                                                                        | Hand phantom.....                                                                                 | 174        |
+| A.2.2.1                                                                                      | General.....                                                                                      | 174        |
+| A.2.2.2                                                                                      | Dimensions.....                                                                                   | 174        |
+| A.2.2.3                                                                                      | Dielectric properties.....                                                                        | 176        |
+| A.2.2.4                                                                                      | Hand phantom grips.....                                                                           | 176        |
+| A.2.2.5                                                                                      | Mechanical Requirements of Hand Phantoms.....                                                     | 178        |
+| A.2.3                                                                                        | Laptop Ground Plane Phantom.....                                                                  | 179        |
+| A.2.4                                                                                        | Parameters for embedded devices.....                                                              | 181        |
+| A.2.4.1                                                                                      | General.....                                                                                      | 181        |
+| A.2.4.2                                                                                      | Notebook.....                                                                                     | 181        |
+
+|                                                                                        |                                                                                          |            |
+|----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------|
+| A.2.4.3                                                                                | Tablet.....                                                                              | 182        |
+| A.3                                                                                    | Anechoic chamber constraints.....                                                        | 182        |
+| A.3.1                                                                                  | General.....                                                                             | 182        |
+| A.3.2                                                                                  | Quiet zone dimension.....                                                                | 185        |
+| A.3.3                                                                                  | Minimum distance between the DUT and the measurement antenna.....                        | 185        |
+| A.3.4                                                                                  | Reflectivity of the quiet zone.....                                                      | 185        |
+| A.3.5                                                                                  | Shielding effectiveness of the chamber.....                                              | 185        |
+| A.4                                                                                    | Reverberation chamber constraints.....                                                   | 185        |
+| A.4.1                                                                                  | General.....                                                                             | 185        |
+| A.4.2                                                                                  | Positioning and mode stirring facilities.....                                            | 186        |
+| A.4.3                                                                                  | Polarization imbalance and receiving antennas.....                                       | 186        |
+| A.4.4                                                                                  | Measurement antennas.....                                                                | 187        |
+| A.4.5                                                                                  | Chamber size and characteristics.....                                                    | 187        |
+| A.4.6                                                                                  | Shielding effectiveness of the chamber.....                                              | 187        |
+| A.5                                                                                    | Anechoic chamber constraints for Radiated Performance of Multiple-antenna Receivers..... | 187        |
+| A.5.1                                                                                  | General.....                                                                             | 187        |
+| A.5.1.1                                                                                | Multi-probe Anechoic Chamber.....                                                        | 188        |
+| A.5.1.1.1                                                                              | Concept and configuration.....                                                           | 189        |
+| A.5.1.2                                                                                | Radiated Two-Stage.....                                                                  | 190        |
+| A.5.1.2.1                                                                              | Concept and configuration.....                                                           | 191        |
+| A.5.2                                                                                  | Testing environment conditions.....                                                      | 192        |
+| A.5.2.1                                                                                | MPAC Positioning Guidelines.....                                                         | 198        |
+| A.5.2.2                                                                                | RTS Positioning Guidelines and test zone dimensions.....                                 | 202        |
+| <b>Annex B (normative): Calibration.....</b>                                           |                                                                                          | <b>202</b> |
+| B.1                                                                                    | General.....                                                                             | 202        |
+| B.2.1                                                                                  | Calibration procedure for Anechoic chamber method.....                                   | 203        |
+| B.2.2                                                                                  | Calibration procedure for Reverberation chamber method.....                              | 204        |
+| B.2.2.1                                                                                | Measurement of S-parameters through the chamber for a complete stirring sequence.....    | 204        |
+| B.2.2.2                                                                                | Calculation of the chamber reference transfer function.....                              | 205        |
+| B.2.2.3                                                                                | Cable calibration.....                                                                   | 206        |
+| B.2.3                                                                                  | Calibration procedure for Anechoic chamber method with Multiprobe configuration.....     | 206        |
+| B.2.3.1                                                                                | Example Calibration Procedure.....                                                       | 207        |
+| B.2.4                                                                                  | Calibration procedure for RTS method.....                                                | 208        |
+| <b>Annex C (informative): Measurement test report.....</b>                             |                                                                                          | <b>209</b> |
+| C.1                                                                                    | General.....                                                                             | 209        |
+| <b>Annex D (normative): Maximum uncertainty of test system and test tolerance.....</b> |                                                                                          | <b>210</b> |
+| D.1                                                                                    | Maximum uncertainty of test system.....                                                  | 210        |
+| D.2                                                                                    | Test tolerances.....                                                                     | 212        |
+| <b>Annex E (informative): Estimation of measurement uncertainty.....</b>               |                                                                                          | <b>214</b> |
+| E.1                                                                                    | General.....                                                                             | 214        |
+| E.2                                                                                    | Mismatch uncertainty between measurement receiver and the probe antenna.....             | 220        |
+| E.2.1                                                                                  | Total combined mismatch uncertainty calculations.....                                    | 220        |
+| E.2.1.1                                                                                | Mismatch uncertainty through the connector between two elements.....                     | 220        |
+| E.2.1.2                                                                                | Mismatch uncertainty due to the interaction of several elements.....                     | 221        |
+| E.2.2                                                                                  | Total combined mismatch uncertainty.....                                                 | 222        |
+| E.3                                                                                    | Mismatch uncertainty of the RF relay.....                                                | 222        |
+| E.3.1                                                                                  | First part: RF Relay switched on the co-polarized signal.....                            | 223        |
+| E.3.1.1                                                                                | The mismatch through the connector between two elements.....                             | 223        |
+| E.3.1.2                                                                                | Mismatch due to the interaction between two elements or more.....                        | 223        |
+| E.3.2                                                                                  | Second part: RF relay switched on the cross-polarized signal.....                        | 224        |
+| E.3.2.1                                                                                | The mismatch through the connector between two elements.....                             | 224        |
+| E.3.2.2                                                                                | Mismatch due to the interaction between two elements or more.....                        | 224        |
+
+|                               |                                                                            |            |
+|-------------------------------|----------------------------------------------------------------------------|------------|
+| E.3.3                         | Total combined mismatch uncertainty.....                                   | 225        |
+| E.4                           | Insertion loss of the probe antenna cable.....                             | 225        |
+| E.5                           | Insertion loss of the probe antenna attenuator (if used).....              | 225        |
+| E.6                           | Insertion loss of the RF relays (if used).....                             | 225        |
+| E.7                           | Influence of the antenna cable.....                                        | 226        |
+| E.7.1                         | Probe antenna cable.....                                                   | 226        |
+| E.7.2                         | Calibration antenna cable.....                                             | 226        |
+| E.8                           | Absolute gain of the probe antenna.....                                    | 226        |
+| E.9                           | Measurement receiver: uncertainty of absolute level.....                   | 226        |
+| E.10                          | Measurement distance.....                                                  | 226        |
+| E.10.1                        | Offset of DUT phase centre from axis(es) of rotation.....                  | 226        |
+| E.10.2                        | Mutual coupling.....                                                       | 227        |
+| E.10.3                        | Phase curvature.....                                                       | 227        |
+| E.11                          | Quality of quiet zone.....                                                 | 227        |
+| E.12                          | Tx-power drift of DUT.....                                                 | 227        |
+| E.13                          | Uncertainty related to the use of phantoms.....                            | 228        |
+| E.13.1                        | Uncertainty from using different types of SAM phantom.....                 | 228        |
+| E.13.2                        | Simulated tissue liquid uncertainty.....                                   | 228        |
+| E.13.3                        | Uncertainty of dielectric properties and shape of the hand phantom.....    | 228        |
+| E.13.4                        | Uncertainty from using different types of Laptop Ground Plane phantom..... | 230        |
+| E.14                          | Coarse sampling grid.....                                                  | 230        |
+| E.15                          | Random uncertainty.....                                                    | 231        |
+| E.16                          | Uncertainty of network analyzer.....                                       | 232        |
+| E.17                          | Uncertainty of the gain/efficiency of the calibration antenna.....         | 232        |
+| E.18                          | Base station simulator: uncertainty of the absolute level.....             | 232        |
+| E.19                          | BER measurement: output level step resolution.....                         | 232        |
+| E.20                          | Statistical uncertainty of the BER measurement.....                        | 232        |
+| E.21                          | BER data rate normalization uncertainty.....                               | 233        |
+| E.22                          | DUT sensitivity drift.....                                                 | 233        |
+| E.23                          | Cable loss measurement uncertainty.....                                    | 233        |
+| E.24                          | Signal generator: uncertainty of the absolute output level.....            | 234        |
+| E.25                          | Signal generator: output level stability.....                              | 234        |
+| E.26                          | Insertion loss: calibration antenna feed cable.....                        | 234        |
+| E.27                          | Insertion loss: calibration antenna attenuator (if used).....              | 234        |
+| E.28                          | Chamber Statistical Ripple and Repeatability.....                          | 234        |
+| E.29                          | Additional Power Loss in EUT Chassis.....                                  | 234        |
+| <b>Annex F (informative):</b> | <b>Suggested recipes of liquid to be used inside SAM phantom.....</b>      | <b>246</b> |
+| F.1                           | General.....                                                               | 246        |
+| <b>Annex G (informative):</b> | <b>Anechoic chamber specification and validation method.....</b>           | <b>246</b> |
+| G.1                           | Shielded anechoic chamber specifications.....                              | 246        |
+| G.2                           | Quiet zone reflectivity level validation.....                              | 247        |
+| G.2.1                         | Description of a practical method for Quiet Zone characterization.....     | 247        |
+| G.3                           | Standard deviation of electric field.....                                  | 248        |
+| <b>Annex H (informative):</b> | <b>Reverberation chamber specifications and validation method.....</b>     | <b>248</b> |
+| H.1                           | Shielded reverberation chamber specifications.....                         | 248        |
+| H.2                           | Reverberation chamber statistical ripple and repeatability validation..... | 249        |
+| <b>Annex I (informative):</b> | <b>Recommended performance for Handheld UE.....</b>                        | <b>250</b> |
+| I.1                           | General.....                                                               | 250        |
+| I.2                           | Total Radiated Power.....                                                  | 250        |
+| I.2.1                         | Beside the head phantom position.....                                      | 250        |
+| I.2.1.1                       | UTRA FDD.....                                                              | 250        |
+| I.2.1.2                       | UTRA LCR TDD.....                                                          | 251        |
+
+|                                                                                                     |                                                                                                |            |
+|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------|
+| I.2.2                                                                                               | Beside the head and hand phantoms position.....                                                | 251        |
+| I.2.2.1                                                                                             | UTRA FDD.....                                                                                  | 251        |
+| I.2.2.2                                                                                             | UTRA LCR TDD.....                                                                              | 251        |
+| I.2.2.3                                                                                             | E-UTRA FDD.....                                                                                | 252        |
+| I.2.2.4                                                                                             | E-UTRA TDD.....                                                                                | 252        |
+| I.2.3                                                                                               | Hand phantom browsing mode position.....                                                       | 252        |
+| I.2.3.1                                                                                             | UTRA FDD.....                                                                                  | 252        |
+| I.2.3.2                                                                                             | UTRA LCR TDD.....                                                                              | 252        |
+| I.2.3.3                                                                                             | E-UTRA FDD.....                                                                                | 253        |
+| I.2.3.4                                                                                             | E-UTRA TDD.....                                                                                | 253        |
+| I.3                                                                                                 | Total Radiated Sensitivity.....                                                                | 253        |
+| I.3.1                                                                                               | Beside the head phantom position.....                                                          | 253        |
+| I.3.1.1                                                                                             | UTRA FDD.....                                                                                  | 253        |
+| I.3.1.2                                                                                             | UTRA LCR TDD.....                                                                              | 254        |
+| I.3.2                                                                                               | Beside the head and hand phantoms position.....                                                | 254        |
+| I.3.2.1                                                                                             | UTRA FDD.....                                                                                  | 254        |
+| I.3.2.2                                                                                             | UTRA LCR TDD.....                                                                              | 254        |
+| I.3.2.3                                                                                             | E-UTRA FDD.....                                                                                | 255        |
+| I.3.2.4                                                                                             | E-UTRA TDD.....                                                                                | 255        |
+| I.3.3                                                                                               | Hand phantom browsing mode position.....                                                       | 255        |
+| I.3.3.1                                                                                             | UTRA FDD.....                                                                                  | 255        |
+| I.3.3.2                                                                                             | UTRA LCR TDD.....                                                                              | 256        |
+| I.3.3.3                                                                                             | E-UTRA FDD.....                                                                                | 256        |
+| I.3.3.4                                                                                             | E-UTRA TDD.....                                                                                | 256        |
+| <b>Annex J (informative): Recommended performance for LME.....</b>                                  |                                                                                                | <b>256</b> |
+| J.1                                                                                                 | General.....                                                                                   | 256        |
+| J.2                                                                                                 | Total Radiated Power.....                                                                      | 256        |
+| J.2.1                                                                                               | UTRA FDD.....                                                                                  | 256        |
+| J.2.2                                                                                               | UTRA LCR TDD.....                                                                              | 257        |
+| J.2.3                                                                                               | E-UTRA FDD.....                                                                                | 257        |
+| J.2.4                                                                                               | E-UTRA TDD.....                                                                                | 257        |
+| J.3                                                                                                 | Total Radiated Sensitivity.....                                                                | 257        |
+| J.3.1                                                                                               | UTRA FDD.....                                                                                  | 258        |
+| J.3.2                                                                                               | UTRA LCR TDD.....                                                                              | 258        |
+| J.3.3                                                                                               | E-UTRA FDD.....                                                                                | 258        |
+| J.3.4                                                                                               | E-UTRA TDD.....                                                                                | 258        |
+| <b>Annex K (informative): Recommended performance for LEE.....</b>                                  |                                                                                                | <b>258</b> |
+| K.1                                                                                                 | General.....                                                                                   | 258        |
+| K.2                                                                                                 | Total Radiated Power.....                                                                      | 259        |
+| K.2.1                                                                                               | UTRA FDD.....                                                                                  | 259        |
+| K.2.2                                                                                               | UTRA LCR TDD.....                                                                              | 260        |
+| K.2.3                                                                                               | E-UTRA FDD.....                                                                                | 260        |
+| K.2.4                                                                                               | E-UTRA TDD.....                                                                                | 260        |
+| K.3                                                                                                 | Total Radiated Sensitivity.....                                                                | 260        |
+| K.3.1                                                                                               | UTRA FDD.....                                                                                  | 261        |
+| K.3.2                                                                                               | UTRA LCR TDD.....                                                                              | 261        |
+| K.3.3                                                                                               | E-UTRA FDD.....                                                                                | 262        |
+| K.3.4                                                                                               | E-UTRA TDD.....                                                                                | 262        |
+| <b>Annex L (informative): Multi-Probe Anechoic Chamber Specification and Validation Method.....</b> |                                                                                                | <b>263</b> |
+| L.1                                                                                                 | Multi-probe anechoic chamber specifications.....                                               | 263        |
+| L.2                                                                                                 | Multi-probe anechoic chamber minimum distance between the DUT and the measurement antenna..... | 263        |
+| L.3                                                                                                 | Multi-probe anechoic chamber quiet zone reflectivity level validation.....                     | 263        |
+| L.4                                                                                                 | Multi-probe anechoic chamber channel model verification.....                                   | 263        |
+
+**Annex M (normative): Channel Model emulation of the Base Station antenna pattern configuration for Radiated Performance of Multiple-antenna Receivers..... 264**
+
+M.1 Channel Model(s)..... 264
+
+M.2 Base Station antenna pattern configuration..... 265
+
+**Annex N (informative): Estimation of measurement uncertainty for Multiple-antenna receivers..... 265**
+
+N.1 General..... 265
+
+N.2 Fading channel emulator output uncertainty..... 268
+
+N.3 External Amplifiers Uncertainty Terms..... 269
+
+N.3.1 Stability..... 269
+
+N.3.2 Linearity..... 269
+
+N.3.3 Noise Figure..... 269
+
+N.3.4 Mismatch..... 269
+
+N.3.5 Gain..... 269
+
+**Annex O (normative): Environmental conditions..... 270**
+
+O.1 General..... 270
+
+O.2 Environmental requirements..... 270
+
+O.2.1 Temperature..... 270
+
+O.2.2 Voltage..... 270
+
+**Annex P (normative): Base Station (BS) configuration for Radiated Performance of Multiple-antenna Receivers..... 270**
+
+P.1 eNodeB emulator settings..... 270
+
+**Annex Q (informative): RTS Anechoic Chamber Specification and Validation Method..... 273**
+
+Q.1 RTS anechoic chamber specifications..... 273
+
+Q.2 RTS anechoic chamber minimum distance between the DUT and the measurement antenna..... 273
+
+Q.3 RTS anechoic chamber quiet zone reflectivity level validation..... 274
+
+Q.4 RTS anechoic chamber channel model verification..... 274
+
+**Annex R: UE ATF Requirements..... 274**
+
+R.1 RSAP..... 274
+
+R.2 RSARP..... 274
+
+Annex S: Change history ..... 275
+
+---
+
+## Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document describes the test procedure for the radiated performances measurements of the user equipment (UE).
+
+The handheld UE measurement procedures explained in this document are defined for roaming bands for the speech mode position (beside the head and beside the head and hand) and hand phantom browsing mode position. Laptop mounted equipment (LME) measurement procedures are defined for roaming bands for the data mode transfer position (laptop ground plane phantom). Laptop embedded equipment (LEE) measurement procedures are defined for roaming bands for the data mode transfer position (free space).
+
+The browsing mode position explained in this document applies when the UE is held in hand, but not pressed against ear (such as web browsing and navigation).
+
+The data mode transfer position (free space) explained in this document applies when the UE is used away from the user's head. Free space measurements are applicable to devices used in the data mode transfer position that consist of the laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs.
+
+All bands are potential roaming bands, and the requirements for roaming bands shall therefore be fulfilled for all bands supported by a UE.
+
+Radiated performance of multiple-antenna receivers for handheld UE is defined for roaming bands in free space configuration.
+
+Recommended performance values for operating bands (Annex I) are however included in this specification for information. It should be recognised that the ability to meet the recommended performance values depends on the number of frequency bands supported by the UE.
+
+The radiated radio tests considered here are:
+
+1. The measurement of the Total Radiated Power (TRP)
+2. The measurement of the Total Radiated Sensitivity (TRS)
+3. The measurement of Total Radiated Multi-antenna Sensitivity (TRMS)
+
+The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)".
+- [3] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode".
+- [4] 3GPP TS 34.108: "Common Test Environments for User Equipment (UE) Conformance Testing".
+- [5] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions"
+
+- [6] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing".
+- [7] 3GPP TS 34.121-1: 3rd Generation Partnership Project; Technical Specification Group Terminals; Terminal conformance specification; Radio transmission and reception (FDD)
+- [8] 3GPP TS 34.122: "Terminal conformance specification; Radio transmission and reception (TDD)"
+- [9] 3GPP TS 36 101: "E-UTRA UE radio transmission and reception".
+- [10] 3GPP TS 36.508: "Common test environments for User Equipment (UE)".
+- [11] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: conformance testing".
+- [12] 3GPP TS 37.144: "User Equipment (UE) and Mobile Station (MS) GSM, UTRA, and E-UTRA over the air performance requirements".
+- [13] 3GPP TR 37.844: "User Equipment (UE) GSM, UTRA and E-UTRA over the air performance requirements".
+- [14] 3GPP TR 37.902: "Measurements of User Equipment (UE) radio performances for LTE/UMTS terminals; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology (Release 12)"
+- [15] IEEE standard P1528; "Recommended Practice for Determining the Peak Spatial-Average Specific Absorption Rate (SAR) in the Human Head from Wireless Communications Devices: Experimental Techniques", April, 2003.
+- [16] CENELEC Standard ENS 50361: "Basic Standard for the measurement of Specific Absorption Rate related to human exposure to electromagnetic fields from mobile phones (300 MHz-3 GHz)", Brussels, Belgium, CENELEC, July 2001, 51 p.
+- [17] H. Knoess, M. Christensen, S. Svendsen, T. Hiegler, A. Friederich, "Investigation of Different Phantom Head Models Including Holder", COST 273 TD(04) 068, Gothenburg, June 2004, 6 p.
+- [18] ETSI ETR 273: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [19] M.Y. Kanda, M. Ballen, C.K. Chou. "Formulation and characterization of tissue simulating liquids used for SAR measurement (500-2000 MHz)" Asia-Pacific Radio Science Conference, Tokyo, Japan, August 1-4, 2001, p. 274.
+- [20] V. Vigneras, "Elaboration and characterization of biological tissues equivalent liquids in the frequency range 0.9 - 3 GHz", Final report, PIOM Laboratory, University of Bordeaux, France, November 2001.
+- [21] Dr. Michael D. Foegelle, ETS-Lindgren, Kevin Li, Nokia Corp., Andrew Pavacic and Paul Moller, Motorola, Inc. "Developing a Standard Hand Phantom for Wireless Testing" Part 1, Wireless design and Development
+- [22] Gabriel, C., "Tissue Equivalent Material for Hand Phantoms," Physics in Medicine and Biology, 52 (2007), pp. 4205 - 4210,
+- [23] Dr. Michael D. Foegelle, ETS-Lindgren, Kevin Li, Nokia Corp., Andrew Pavacic and Paul Moller, Motorola, Inc. Wireless Design & Development, The Development of a Standard Hand Phantom for Wireless Performance Testing: Part 2
+- [24] T. Laitinen, J. Ollikainen, P. Vainikainen, C. Icheln, "Rapid Spherical 3-D Field Measurement System for Mobile Terminal Antennas", COST273 TD(03)134
+- [25] ETSI TR 100 028: "ElectroMagnetic Compatibility and Radio Spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics Part 1".
+
+- [26] ETSI TR 102 273-1-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 1: Introduction".
+- [27] ETSI TR 102 273-1-2: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Improvement on Radiated Methods of Measurement (using test site) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measurement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
+- [28] IEEE standard P1528; "Recommended Practice for Determining the Peak Spatial-Average Specific Absorption Rate (SAR) in the Human Head from Wireless Communications Devices: Experimental Techniques", April, 2003
+- [29] 3GPP TR 37.977: "Verification of radiated multi-antenna reception performance of User Equipment (UE)"
+- [30] IEEE.149-1979.R2008: "IEEE Standard Test Procedures for Antennas," IEEE, October 2003.
+- [31] Yanakiev, Boyan Radkov; Nielsen, Jesper Ødum; Christensen, Morten; Pedersen, Gert F, "Antennas In Real Environments", 2011 Proceedings of the Fifth European Conference on Antennas and Propagation (EuCAP). IEEE, 2011. p. 2766-2770.
+- [32] CTIA: "Test Plan for Wireless Device Over-the-Air Performance"
+- [33] TD(09) 742, COST 2100 SWG 2.2, Braunschweig, Germany, February 2009, J. Takada: "Handset MIMO Antenna Testing Using a RF-controlled Spatial Fading Emulator".
+- [34] 3GPP TS 36.509: "Special conformance testing functions for User Equipment (UE)"
+
+## 3 Definitions, symbols and abbreviations
+
+### 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Browsing mode position:** UE is held in hand, but not pressed against ear (such as web browsing and navigation).
+
+**Data mode transfer position:** UE used away from the user's head, applicable for LME and LEE devices.
+
+**FS:** UE used in a free space configuration.
+
+**Intended use position:** UE is attached to the SAM phantom intended for use in the check position.
+
+**LEE:** Laptop embedded equipment (such as embedded module card embedded in notebooks).
+
+**LME:** Laptop mounted equipment (such as plug-in devices like USB dongles).
+
+**Primary mechanical mode:** The mode that is most often used during a call beside the head. Other mechanical modes are secondary. Every terminal has at least one primary mechanical mode.
+
+**Speech mode position:** UE is placed into a hand phantom, which is holding the UE against the SAM head phantom.
+
+### 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                             |                                                                                                                      |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------|
+| $\theta$                    | Zenith angle in the spherical co-ordinate system                                                                     |
+| $\phi$                      | Azimuth angle in the spherical co-ordinate system                                                                    |
+| $\Omega$                    | Solid angle defined at the phase centre of the DUT                                                                   |
+| $G_{\psi}(\theta, \phi, f)$ | Antenna gain pattern in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency |
+| F                           | Carrier frequency                                                                                                    |
+
+|                             |                                                                                                                                                          |
+|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $P_{tr}$                    | Transmitted power                                                                                                                                        |
+| $Q_{\psi}(\theta, \phi, f)$ | Angular power distribution in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency                               |
+| dB                          | decibel                                                                                                                                                  |
+| dBm                         | dB referenced to one milliwatt                                                                                                                           |
+| m                           | meter                                                                                                                                                    |
+| mm                          | millimeter                                                                                                                                               |
+| kbps                        | kilobit per second                                                                                                                                       |
+| ms                          | millisecond                                                                                                                                              |
+| MHz                         | megahertz                                                                                                                                                |
+| $TRMS_{average, 70}$        | Average TRMS quantity calculated from sensitivity measurements at 70% throughput                                                                         |
+| $TRMS_{average, 95}$        | Average TRMS quantity calculated from sensitivity measurements at 95% throughput                                                                         |
+| $TRP_{average}$             | the average measured total radiated power of low, mid and high channel                                                                                   |
+| $TRP_{min}$                 | the lowest measured total radiated power of each channel within an operating band                                                                        |
+| $TRS_{average}$             | the average measured total radiated sensitivity of low, mid and high channel                                                                             |
+| $TRS_{max}$                 | the highest measured total radiated sensitivity of each channel within an operating band                                                                 |
+| $P_d$                       | Direct signal                                                                                                                                            |
+| $P_{meas\ n}$               | Measured power received by field-probe at position $n$                                                                                                   |
+| $P_{MODE, x, i}$            | Measured sensitivity value when <i>MODE</i> is one of { <i>FS_DMP</i> , <i>FS_DML</i> , <i>FS_DMSU</i> }, $x$ is one of {70, 95} at azimuth position $i$ |
+| $P_r$                       | Reflected signal                                                                                                                                         |
+| $P_{RS-EPRE-MAX}$           | Maximum downlink RS-EPRE                                                                                                                                 |
+| $R_{level}$                 | Reflectivity level                                                                                                                                       |
+
+### 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|            |                                                 |
+|------------|-------------------------------------------------|
+| 3G         | 3 <sup>rd</sup> Generation                      |
+| 3GPP       | 3G Partnership Project                          |
+| 3-D        | Three Dimensional                               |
+| AAU        | Aalborg University                              |
+| APD        | Angular Power Distribution                      |
+| ARFCN      | Absolute Radio Frequency Channel Number         |
+| ATF        | Antenna Test Function                           |
+| BER        | Bit Error Ratio                                 |
+| BS         | Base Station                                    |
+| BT         | Bluetooth                                       |
+| BTS        | Base Transceiver Station                        |
+| CAD        | Computer Aided Design                           |
+| CN         | Core Network                                    |
+| CPICH RSCP | Common Pilot Channel Received Signal Code Power |
+| CRC        | Cyclic Redundancy Check                         |
+| DCH        | Dedicated Channel                               |
+| DL         | Downlink                                        |
+| DML        | Data Mode Landscape                             |
+| DMP        | Data Mode Portrait                              |
+| DMSU       | Data Mode Screen Up                             |
+| DPCH       | Dedicated Physical Channel                      |
+| DPDCH      | Dedicated Physical Data Channel                 |
+| DPCCH      | Physical Control Channel                        |
+| DTCH       | Dedicated Traffic Channel                       |
+| DUT        | Device Under Test                               |
+| EIRP       | Effective Isotropic Radiated Power              |
+| EIS        | Effective Isotropic Sensitivity                 |
+| ETSI       | European Telecommunications Standards Institute |
+| EUT        | Equipment Under Test                            |
+| E-UTRA     | Evolved UMTS Terrestrial Radio Access           |
+| E-UTRAN    | Evolved UMTS Terrestrial Radio Access Network   |
+
+|         |                                                                             |
+|---------|-----------------------------------------------------------------------------|
+| FDD     | Frequency Division Duplex                                                   |
+| FS      | Free Space                                                                  |
+| FS DML  | Free Space Data Mode Landscape                                              |
+| FS DMP  | Free Space Data Mode Portrait                                               |
+| FS DMSU | Free Space Data Mode Screen Up                                              |
+| GPS     | Global Positioning System                                                   |
+| HUT     | Helsinki University of Technology                                           |
+| LCD     | Liquid Crystal Display                                                      |
+| LEE     | Laptop Embedded Equipment (e.g. embedded module card embedded in notebooks) |
+| LME     | Laptop Mounted Equipment (e.g., plug-in devices like USB dongles)           |
+| LTE     | Long Term Evolution                                                         |
+| MPAC    | Multi-Probe Anechoic Chamber                                                |
+| NB      | Node B                                                                      |
+| NSA     | Normalised Site Attenuation                                                 |
+| OTA     | Over The Air                                                                |
+| PDA     | Personal Digital Assistant                                                  |
+| QoS     | Quality of Service                                                          |
+| QPSK    | Quadrature Phase Shift Keying (modulation)                                  |
+| RAB     | Radio Access Bearer                                                         |
+| RB      | Radio Bearer                                                                |
+| RAN     | Radio Access Network                                                        |
+| RBW     | Resolution Bandwidth                                                        |
+| RF      | Radio Frequency                                                             |
+| RMS     | Root Mean Square                                                            |
+| RS-EPRE | Reference Signal-Energy Per Resource Element                                |
+| Rx      | Receiver                                                                    |
+| SAM     | Specific Anthropomorphic Mannequin                                          |
+| SAR     | Specific Absorption Rate                                                    |
+| SS      | System Simulator                                                            |
+| TDD     | Time Division Duplex                                                        |
+| TFCI    | Transport Format Combination Indicator                                      |
+| Tx      | Transmitter                                                                 |
+| TRMS    | Total Radiated Multi-antenna Sensitivity                                    |
+| TRP     | Total Radiated Power                                                        |
+| TRS     | Total Radiated Sensitivity                                                  |
+| UDP     | User Datagram Protocol                                                      |
+| UE      | User Equipment                                                              |
+| UL      | Uplink                                                                      |
+| UMTS    | Universal Mobile Telecommunications System                                  |
+| USB     | Universal Serial Bus                                                        |
+| UTRA    | UMTS Terrestrial Radio Access                                               |
+| VBW     | Video Bandwidth                                                             |
+| VNA     | Vector Network Analyzer                                                     |
+| VSWR    | Voltage Standing Wave Ratio                                                 |
+| WLAN    | Wireless Local Area Network                                                 |
+| WWAN    | Wireless Wide Area Network                                                  |
+| XPD     | Cross-Polar Discrimination of the antenna                                   |
+| XPR     | Cross-Polarization ratio of the channel                                     |
+
+---
+
+## 4 General
+
+The device under test (DUT) presented in this clause is based on a device that is tested to determine performance as defined in the present release of specifications.
+
+## 4.1 Terminal classes
+
+### 4.1.1 Mechanical modes
+
+The mechanical modes of a DUT are declared by the manufacturer. A DUT shall have at least one mechanical mode. If only one mode is supported, then this is defined as the primary.
+
+## 4.2 UTRA chip rates
+
+The requirements defined in this specification for UTRA are based on a chip rate of 3.84 Mcps (FDD) and 1.28 Mcps (TDD).
+
+NOTE: Other chip rates may be considered in future releases.
+
+## 4.3 DUT positioning
+
+### 4.3.1 DUT positioning for Speech Mode with beside the Head Phantom
+
+The positioning specified in this clause is used for the tests cases titled as tests for Speech Mode with beside the Head Phantom. The characteristics of the Specific Anthropomorphic Mannequin (SAM) phantom are specified in Annex A.2.1.
+
+The DUT is attached to the SAM phantom in "cheek" position as defined both by IEEE [28] and CELENEC [16] standards. The DUT performance is measured on both left and right side of the head.
+
+Three points as shown in Figure 4.3.1-1 define the reference plane: centre of the right ear piece (RE), centre of the left ear piece (LE) and centre of mouth (M).
+
+At first, set the DUT ready for operation.
+
+Definition of the 'Cheek' position:
+
+1. Align the ear piece of the phone (see Figure 4.3.1-1) at the line RE-LE. Then, position the DUT beside the phantom so that the vertical line (see Figure 4.3.1-3) is parallel to the reference plane in Figure 4.3.1-2 and is aligned with the line M-RE on the reference plane (see Figure 4.3.1-3).
+2. Position the DUT so that the ear piece of the DUT touches the ear piece of the phantom head on the line RE-LE. Tilt the DUT chassis towards the cheek of the phantom having the vertical line aligned with the reference plane until any point on the front side of the DUT is in contact with the cheek or until the contact with the ear is lost.
+
+NOTE: A holder fixture made of e.g. plastic may be used to position the handset against the phantom. An experimental study presented in [17] shows that some plastic holders might introduce an unexpectedly large effect to the measurement results. Therefore, special care must be seen when selecting such fixtures for radiated measurements.
+
+![Figure 4.3.1-1: Reference plane on head phantom, front view. The diagram shows a front view of a human head phantom. A dashed line labeled 'Reference plane' is drawn through the head, passing through three points: RE (centre of the right ear piece), LE (centre of the left ear piece), and M (centre of mouth). The RE and LE points are marked with dots on the ears, and the M point is marked with a dot on the mouth. The reference plane is shown as a dashed line extending from the ears, passing through the mouth, and continuing outwards.](b6f51e145a04a7d4ade15a5fb94bf872_img.jpg)
+
+Figure 4.3.1-1: Reference plane on head phantom, front view. The diagram shows a front view of a human head phantom. A dashed line labeled 'Reference plane' is drawn through the head, passing through three points: RE (centre of the right ear piece), LE (centre of the left ear piece), and M (centre of mouth). The RE and LE points are marked with dots on the ears, and the M point is marked with a dot on the mouth. The reference plane is shown as a dashed line extending from the ears, passing through the mouth, and continuing outwards.
+
+Figure 4.3.1-1: Reference plane on head phantom, front view
+
+![Figure 4.3.1-2: Reference plane on head phantom, side view. A side view of a head phantom with a dashed line representing the reference plane passing through the ear (RE) and mouth (M) area.](20ab59bc10b900f6cf8a34549848bbf4_img.jpg)
+
+Figure 4.3.1-2: Reference plane on head phantom, side view. A side view of a head phantom with a dashed line representing the reference plane passing through the ear (RE) and mouth (M) area.
+
+Figure 4.3.1-2: Reference plane on head phantom, side view
+
+![Figure 4.3.1-3: Reference lines at a DUT. A diagram of a device (DUT) showing a vertical line passing through the center and an antenna, and a horizontal line passing through the ear piece. The width of the chassis is labeled W, and the distance from the center line to each side is labeled W/2.](b038de46b62ad59f030ec5a0501673e1_img.jpg)
+
+Figure 4.3.1-3: Reference lines at a DUT. A diagram of a device (DUT) showing a vertical line passing through the center and an antenna, and a horizontal line passing through the ear piece. The width of the chassis is labeled W, and the distance from the center line to each side is labeled W/2.
+
+Figure 4.3.1-3: Reference lines at a DUT
+
+NOTE: W is the width of the chassis [28].
+
+The characteristics of DUT positioning on head phantom in "cheek" position are specified in Table 4.3.1-1.
+
+Table 4.3.1-1: Characteristics of DUT positioning on head phantom in "cheek" position
+
+| ID | Cheek position on phantom | DUT chassis tilt type | DUT chassis |
+|----|---------------------------|-----------------------|-------------|
+| 0  | Low                       | Shift Down            | Up          |
+| 1  | Medium                    | No Shift              | Aligned     |
+| 2  | High                      | Shift Up              | Down        |
+
+## 4.3.2 DUT positioning for LMEs on Laptop Ground Plane Phantom
+
+The DUT positioning on Laptop Ground Plane Phantom means that a laptop ground plane phantom is used for radiated performance measurements in case of plug-in DUT like USB dongles that is used away from the user's head. This includes all tests cases for LME devices. The characteristics of the laptop ground plane phantom are specified in Annex A.2.3. The objective of the laptop ground plane phantom is to reproduce the effects of the ground plane for the antenna of the DUT while avoiding the variation of the measurements introduced by a real laptop.
+
+The DUT should be plugged into the USB connector and positioned in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation the DUT with either rotary USB port or non-rotary USB port should be horizontally plugged into the horizontal USB connector, as shown in Figure A.2.3-1.
+
+## 4.3.3 DUT positioning for Speech Mode with beside the Head and Hand Phantom
+
+### 4.3.3.1 General
+
+The positioning specified in this clause is used for the tests cases titled as tests for Speech Mode with beside the Head and Hand Phantom. The characteristics of the Head and Hand Phantoms are specified in Annexes A.2.1 and A.2.2.
+
+Speech mode is simulation of a voice call user case. DUT is placed in to a hand phantom, which is holding the DUT against the SAM head phantom. Positioning of the DUT in the hand phantom varies with the grip being used. Positioning of the DUT against the head phantom is identical to Subclause 4.3.2 with the exception that 6° tilt angle from the cheek is being used instead of having direct contact between the cheek and DUT. A mask may be used to help configuration of cheek + 6° tilt angle. The mask is a 32 mm wide conformal strip, created by sweeping the surface of the head phantom through a 6° rotation about the ear. Direct DUT contact against the mask thus establishes the required 6° spacing away from the cheek, regardless of DUT form factor. The material for the head phantom mask spacer shall have dielectric constant of less than 1.3 and a loss tangent of less than 0.003. Material additions can be used to help fixing of the mask spacer onto the head phantom.
+
+#### 4.3.3.2 Mono-blocks and closed sliders
+
+This procedure applies to mounting mono-block DUTs and closed-slide DUTs, when the DUT is less than 56 mm wide. For consistent, repeatable positioning that conforms to the grip studies, an alignment tool with evenly spaced rulings is first used to measure the DUT. Alignment Tool A in Figure 4.3.3.2-1, features a 120° interior corner to ensure that the ring fingertip lands in the desired position at the bottom of the DUT. The DUT is then positioned in accordance with ruled markings on a conformal palm spacer regardless of any curvature in the DUT corners. DUTs with rounded corners will sit lower in the tool than DUTs having square corners, and thus give a different reading.
+
+1. Place the DUT face-up in Alignment Tool A with its side along the side ruler, and slide it down until it makes contact at the 120° corner. Record the bottom location of the DUT by reading off the bottom ruler of Tool A.
+2. Observe the top of the DUT against the side ruler of the tool. If the top of the DUT extends past the 120 mm marking on the side ruler, then the additional length beyond 120 mm shall be added to the reading from Step 1.
+3. Place the DUT on the right-handed or left-handed hand phantom spacer between the fingers. The bottom location of the DUT on the spacer should be aligned with the reading recorded in Steps 1 and 2. Vertical centreline of the DUT should be centred with the spacer. Make sure index finger is in contact with DUT.
+4. While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described in Subclause 4.3.3.
+
+![Figure 4.3.3.2-1: Alignment Tool A and right-handed mono-block hand phantom with a spacer. The image shows two components: on the left, Alignment Tool A, a light green rectangular tool with a 120-degree interior corner. It has a vertical ruler on the left side (0 to 140 mm) and a horizontal ruler at the bottom (0 to 20 mm). A green line indicates the 120 mm mark on the vertical ruler. On the right, a right-handed mono-block hand phantom, also light green, is shown. It has a vertical ruler on its side (0 to 50 mm) and a green arrow pointing down towards the 5 mm mark. The hand phantom is being held by a dark grey hand.](5756508641ee599941f6d1e85de7e84b_img.jpg)
+
+Figure 4.3.3.2-1: Alignment Tool A and right-handed mono-block hand phantom with a spacer. The image shows two components: on the left, Alignment Tool A, a light green rectangular tool with a 120-degree interior corner. It has a vertical ruler on the left side (0 to 140 mm) and a horizontal ruler at the bottom (0 to 20 mm). A green line indicates the 120 mm mark on the vertical ruler. On the right, a right-handed mono-block hand phantom, also light green, is shown. It has a vertical ruler on its side (0 to 50 mm) and a green arrow pointing down towards the 5 mm mark. The hand phantom is being held by a dark grey hand.
+
+**Figure 4.3.3.2-1: Alignment Tool A and right-handed mono-block hand phantom with a spacer**
+
+NOTE: The Alignment tool is used to determine DUT bottom location on spacer. Use left-handed (mirror-imaged) spacers with left-handed phantoms.
+
+### 4.3.3.3 Folds and open-slides
+
+This procedure applies to fold and open-slide DUTs, when the DUT is less than 56 mm wide. To help maintain a consistent, repeatable positioning that conforms to the grip studies, an alignment tool with evenly spaced rulings is first used to measure the DUT. The DUT is then positioned in accordance with ruled markings on a phantom spacer. Alignment Tool B in Figure 4.3.3.3-1 features two rounded humps upon which the DUT is suspended. One hump represents the index fingertip of the hand phantom, while the other represents the palm spacer. This design helps ensure that the index finger remains in contact with the flip for any fold DUT geometry.
+
+1. Open the DUT and place it face-up on the alignment Tool B with its hinge suspended between the two humps. The side of the DUT shall be aligned against the side wall of the tool. The base of the DUT shall rest on the wide hump with ruled markings, and the flip of the DUT shall rest on the narrow hump.
+2. Tool B has an engraved line on the side wall. Align axis of a fold hinge to this marking. An open slider should be slide longitudinally until the base part of the DUT touches the narrow hump of the Tool B. Record the correct longitudinal position of the bottom of the DUT by reading off the ruler of Tool B. Visually align the two halves of the split-level ruler to minimize parallax reading error.
+3. Position the DUT in the right-handed or left-handed Fold Hand Phantom. It should be resting on the index fingertip and palm spacer, with the bottom of the DUT aligned to the ruling on the right-handed or left-handed palm spacer that corresponds to the reading from Step 2. Ensure that all fingertips are in contact with the DUT.
+4. While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described in Subclause 4.3.3.
+
+![Figure 4.3.3.3-1: Alignment Tool B and right-handed fold hand phantom with a spacer. The image shows a grey alignment tool with a vertical back wall. A vertical green line on the wall is labeled 'hinge axis'. The tool has two rounded humps: a 'narrow hump' on the left and a 'wide hump' on the right. The wide hump has a ruler with markings from 0 to 10. A grey right-handed fold hand phantom with a spacer is shown next to the tool, with its index finger resting on the narrow hump and its palm on the wide hump.](c2749f79dd1fc9bd2dce52bcbb2fb3ef_img.jpg)
+
+Figure 4.3.3.3-1: Alignment Tool B and right-handed fold hand phantom with a spacer. The image shows a grey alignment tool with a vertical back wall. A vertical green line on the wall is labeled 'hinge axis'. The tool has two rounded humps: a 'narrow hump' on the left and a 'wide hump' on the right. The wide hump has a ruler with markings from 0 to 10. A grey right-handed fold hand phantom with a spacer is shown next to the tool, with its index finger resting on the narrow hump and its palm on the wide hump.
+
+**Figure 4.3.3.3-1: Alignment Tool B and right-handed fold hand phantom with a spacer**
+
+NOTE: Use left-handed (mirror-imaged) spacers with left-handed phantoms.
+
+### 4.3.3.4 PDA
+
+This procedure applies to DUTs that are from 56 to 72 mm wide. To help achieve a consistent positioning, the DUT is aligned to a PDA palm spacer. No alignment tool is required. The PDA spacer features side and bottom walls to ensure consistent alignment of DUTs of various sizes.
+
+1. Place the DUT on the PDA spacer between the fingers and align the DUT to the side wall of the PDA.
+2. If the DUT is shorter than 135 mm, then align the top of the DUT with the top of the PDA spacer. Otherwise, align the bottom of the DUT with the bottom wall of the PDA spacer.
+3. While keeping the DUT in the hand phantom in the position defined in previous steps, place the DUT and the hand phantom against the head phantom in such way that the DUT is in 6° tilt angle as described in Subclause 4.3.3.
+
+![Figure 4.3.3.4-1: Right-handed PDA hand phantom with a spacer. The image shows a right-handed hand phantom holding a rectangular device (DUT) against a light-colored spacer. The spacer has a vertical 'side wall' on the right and a horizontal 'bottom wall' at the base. Arrows point to these walls for identification.](c613ca237231251d524291a877d91f7a_img.jpg)
+
+Figure 4.3.3.4-1: Right-handed PDA hand phantom with a spacer. The image shows a right-handed hand phantom holding a rectangular device (DUT) against a light-colored spacer. The spacer has a vertical 'side wall' on the right and a horizontal 'bottom wall' at the base. Arrows point to these walls for identification.
+
+**Figure 4.3.3.4-1: Right-handed PDA hand phantom with a spacer**
+
+NOTE: Use left-handed (mirror-imaged) spacers with left-handed phantoms.
+
+## 4.3.4 DUT positioning for Browsing Mode with Hand Phantom
+
+### 4.3.4.1 General
+
+The positioning specified in this clause is used for the test cases titles as tests for Browsing Mode with Hand Phantom. The characteristics of the Hand Phantom are specified in Annex A.2.2. Browsing mode is used to simulate user cases where the DUT is held in hand, but not pressed against ear e.g. web browsing and navigation. The DUT shall be mounted in a suitable hand phantom and oriented such that the DUT's main display is tilted 45 degrees from vertical. Devices with a cover piece are tested cover open.
+
+### 4.3.4.2 Narrow DUT
+
+This procedure is suitable for use with all DUTs narrower than 56 mm. The alignment Tool A in Figure 4.3.4.2-1 is first used to measure the distance between the bottom of the DUT and the centre of its navigation key. The DUT is then positioned in accordance with ruled markings on a palm spacer to data mode hand phantom.
+
+1. Place the DUT on the DUT alignment Tool A. Record the chin length from the scale at the bottom of the alignment tool.
+2. Record the location of the navigation key (or the “2” key, if no navigation key is present) on the side ruler of the DUT alignment tool A. The key's centre is used as the reference.
+3. Add the two readings from Step 2 and 3 together. If the sum is less than 30 mm, then use 30 mm location on spacer instead.
+4. Place the DUT on the right-hand or left-hand narrow data palm spacer and align the side of the DUT with the side wall of the spacer. The bottom edge of the DUT shall be placed on the narrow data palm spacer at the ruling corresponding to the value obtained in Step 4.
+
+Make sure that the index finger is in contact with the back of the DUT. If the device is very narrow and/or thin, it may occur that the middle finger does not curl tightly enough to contact the DUT. In such case, in order to ensure consistent test results, no attempt should be made to force the fingertip to contact the DUT. Touch fastener material may be used to maintain the DUT in the desired position.
+
+![A 3D rendering of a right-handed data hand phantom holding a Device Under Test (DUT) with a spacer. The phantom's fingers are wrapped around the DUT, and a green spacer with a scale from 30 to 100 is visible between the thumb and the DUT.](d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg)
+
+A 3D rendering of a right-handed data hand phantom holding a Device Under Test (DUT) with a spacer. The phantom's fingers are wrapped around the DUT, and a green spacer with a scale from 30 to 100 is visible between the thumb and the DUT.
+
+**Figure 4.3.4.2-1: Right-handed data hand phantom with a spacer**
+
+NOTE: Use left-handed (mirror-imaged) spacers with left-handed phantoms.
+
+#### 4.3.4.3 PDA
+
+This procedure is suitable for use with DUTs of width 56-72 mm. The positioning of the DUT in the PDA hand for data mode is identical to that for speech mode described in Subclause 4.3.3.4.
+
+### 4.3.5 DUT positioning for devices with embedded modules
+
+The DUT positioning in a free space configuration without head and hand phantoms, as specified in Annex A.2.4, is used for radiated performance measurements in case of an embedded module card, which is used away from the user's head. This positioning covers all tests cases for LEE devices. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+### 4.3.6 DUT positioning for total radiated multi-antenna sensitivity
+
+#### 4.3.6.1 Handheld UE – Free Space
+
+The DUT positioning for Handheld UE is done using free space configuration.
+
+##### 4.3.6.1.1 MPAC Positioning Guidelines
+
+The MPAC positioning guidelines of the handheld UE in data mode in the MPAC system shall follow the requirements in Annex A.5.2.1.
+
+##### 4.3.6.1.2 RTS Positioning Guidelines
+
+The RTS positioning guidelines of the handheld UE in data mode in the RTS system shall follow the requirements in Annex A.5.2.2.
+
+## 4.4 Sampling grid
+
+For the anechoic chamber based measurement procedures the measurement of TRP is basically based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. Generally it can be said that since the radiating object has a limited size the gain pattern cannot change arbitrarily versus angle, and therefore only a limited number of samples are required to represent the gain pattern to a given accuracy. The samples of TRP are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions.
+
+The measurement of TRS is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BLER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The samples of TRS are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions.
+
+All the samples are taken with two orthogonal linear polarizations, - and -polarisations. It is also possible to measure some other polarisation components, if it is possible to recover - and -polarisations from the measured data by some technique.
+
+Alternatively, different sampling patterns may be used if they are able to ensure same or greater accuracy and provided appropriate measurement uncertainty terms are applied. The TRP can be calculated by interpolating the values to points on the regular grid. If an alternative sampling pattern is used number of measurement points should be greater than in the regular sampling grid.
+
+For the multi-probe anechoic chambers procedures the measurement of TRMS are taken using sample steps of  $30^\circ$  in phi ( $\phi$ ), i.e. with 12 different UE azimuth rotations. For more details, see Annex A.5.
+
+## 4.5 Number of independent samples (for reverberation chamber procedure)
+
+When measuring TRP and TRS in an isotropic Rayleigh fading environment, 100 independent samples can be considered sufficient for ensuring an expanded accuracy better than 0.5 dB. Observe that it might be necessary to collect more samples than this during a measurement sequence in order to ensure a sufficient number of independent samples, since all collected samples might not be independent. The number of samples to be collected during a measurement sequence for each chamber should be chosen so that the overall measurement uncertainty is within the specified limits.
+
+# 5 Measurement frequencies
+
+## 5.1 UTRA FDD frequency bands and measurement channels
+
+Table 5.1-1 provides the list of UTRA FDD frequency bands.
+
+**Table 5.1-1: UTRA FDD frequency bands**
+
+| Operating Band | UL Frequencies<br>UE transmit, Node B receive | DL frequencies<br>UE receive, Node B transmit |
+|----------------|-----------------------------------------------|-----------------------------------------------|
+| I              | 1920 – 1980 MHz                               | 2110 –2170 MHz                                |
+| II             | 1850 –1910 MHz                                | 1930 –1990 MHz                                |
+| III            | 1710-1785 MHz                                 | 1805-1880 MHz                                 |
+| IV             | 1710-1755 MHz                                 | 2110-2155 MHz                                 |
+| V              | 824 – 849 MHz                                 | 869-894 MHz                                   |
+| VI             | 830-840 MHz                                   | 875-885 MHz                                   |
+| VII            | 2500-2570 MHz                                 | 2620-2690 MHz                                 |
+| VIII           | 880 – 915 MHz                                 | 925 – 960 MHz                                 |
+| IX             | 1749.9-1784.9 MHz                             | 1844.9-1879.9 MHz                             |
+| X              | 1710 – 1770 MHz                               | 2110 – 2170 MHz                               |
+| XIX            | 830 – 845MHz                                  | 875 – 890 MHz                                 |
+
+**Table 5.1-2: specifies the measurement channels for UTRA FDD**
+
+TBD
+
+**Table 5.1-2: UTRA FDD measurement channels**
+
+| Operating Band | UL Channels |      |      | DL Channels |       |       |
+|----------------|-------------|------|------|-------------|-------|-------|
+|                | Low         | Mid  | High | Low         | Mid   | High  |
+| I              | 9612        | 9750 | 9888 | 10562       | 10700 | 10838 |
+| II             | 9262        | 9400 | 9538 | 9662        | 9800  | 9938  |
+| III            | 937         | 1113 | 1288 | 1162        | 1338  | 1513  |
+| IV             | 1312        | 1413 | 1513 | 1537        | 1638  | 1738  |
+| V              | 4132        | 4183 | 4233 | 4357        | 4408  | 4458  |
+| VI             | 4162        | 4175 | 4188 | 4387        | 4400  | 4413  |
+| VII            | 2012        | 2175 | 2338 | 2237        | 2400  | 2563  |
+| VIII           | 2712        | 2788 | 2863 | 2937        | 3013  | 3088  |
+| IX             | 8762        | 8837 | 8912 | 9237        | 9312  | 9387  |
+| X              | 2888        | 3025 | 3162 | 3113        | 3250  | 3387  |
+| XIX            | 387         | 412  | 437  | 787         | 812   | 837   |
+
+## 5.2 UTRA TDD frequency bands and measurement channels
+
+Table 5.2-1 provides the UTRA TDD frequency bands.
+
+**Table 5.2-1: UTRA TDD frequency bands**
+
+| Operating Band | Frequencies                    |
+|----------------|--------------------------------|
+| a              | 1900-1920 MHz<br>2010-2025 MHz |
+| b*             | 1850-1910 MHz<br>1930-1990 MHz |
+| c*             | 1910-1930 MHz                  |
+| d**            | 2570-2620 MHz                  |
+| e              | 2300-2400 MHz                  |
+| f              | 1880-1920 MHz                  |
+
+NOTE: Deployment in other frequency bands is not precluded.
+
+\* Used in ITU Region 2
+
+\*\* Used in ITU Region 1
+
+**Table 5.2-2: specifies the measurement channels for UTRA TDD**
+
+TBD
+
+**Table 5.2-3: UTRA TDD measurement channels**
+
+| Operating Band                             | Channels      |               |               |
+|--------------------------------------------|---------------|---------------|---------------|
+|                                            | Low           | Mid           | High          |
+| <b>a</b><br>1900-1920 MHz<br>2010-2025 MHz | 9504<br>10054 | 9550<br>10087 | 9596<br>10121 |
+| <b>b</b><br>1850-1910 MHz<br>1930-1990 MHz | 9254<br>9654  | 9400<br>9800  | 9546<br>9946  |
+| <b>c</b><br>1910-1930 MHz                  | 9554          | 9600          | 9646          |
+| <b>d</b><br>2570-2620 MHz                  | 12854         | 12975         | 13096         |
+| <b>e</b><br>2300-2400 MHz                  | 11504         | 11750         | 11996         |
+| <b>f</b><br>1880-1920 MHz                  | 9404          | 9500          | 9596          |
+
+## 5.3 E-UTRA FDD frequency bands and measurement frequencies allocations
+
+Editor's notes: This Subclause is incomplete. The following item is missing or incomplete:
+
+- TBDs in Tables 5.3-1 (TRP) and 5.3.3 (TRS)
+- Some E-UTRA bands are not included and are FFS
+
+This section specifies the LTE-FDD TRP and TRS frequency bands and measurement frequencies allocations. Table 5.3-0 lists the operating bands. Table 5.3-1 specifies the measurement frequency allocations for TRP and Table 5.3-2 specifies the measurement frequency allocations for TRS.
+
+**Table 5.3-0 E-UTRA FDD operating bands for TRP and TRS**
+
+| E-UTRA Operating Band | Uplink (UL) operating band<br>BS receive<br>UE transmit |                | Downlink (DL) operating band<br>BS transmit<br>UE receive |                | Duplex Mode |
+|-----------------------|---------------------------------------------------------|----------------|-----------------------------------------------------------|----------------|-------------|
+|                       | $F_{UL\_low}$                                           | $F_{UL\_high}$ | $F_{DL\_low}$                                             | $F_{DL\_high}$ |             |
+| 1                     | 1920 MHz                                                | 1980 MHz       | 2110 MHz                                                  | 2170 MHz       | FDD         |
+| 2                     | 1850 MHz                                                | 1910 MHz       | 1930 MHz                                                  | 1990 MHz       | FDD         |
+| 3                     | 1710 MHz                                                | 1785 MHz       | 1805 MHz                                                  | 1880 MHz       | FDD         |
+| 4                     | 1710 MHz                                                | 1755 MHz       | 2110 MHz                                                  | 2155 MHz       | FDD         |
+| 5                     | 824 MHz                                                 | 849 MHz        | 869 MHz                                                   | 894 MHz        | FDD         |
+| 7                     | 2500 MHz                                                | 2570 MHz       | 2620 MHz                                                  | 2690 MHz       | FDD         |
+| 8                     | 880 MHz                                                 | 915 MHz        | 925 MHz                                                   | 960 MHz        | FDD         |
+| 12                    | 699 MHz                                                 | 716 MHz        | 729 MHz                                                   | 746 MHz        | FDD         |
+| 13                    | 777 MHz                                                 | 787 MHz        | 746 MHz                                                   | 756 MHz        | FDD         |
+| 14                    | 788 MHz                                                 | 798 MHz        | 758 MHz                                                   | 768 MHz        | FDD         |
+| 17                    | 704 MHz                                                 | 716 MHz        | 734 MHz                                                   | 746 MHz        | FDD         |
+| 19                    | 830 MHz                                                 | 845 MHz        | 875 MHz                                                   | 890 MHz        | FDD         |
+| 20                    | 832 MHz                                                 | 862 MHz        | 791 MHz                                                   | 821 MHz        | FDD         |
+| 21                    | 1447.9 MHz                                              | 1462.9 MHz     | 1495.9 MHz                                                | 1510.9 MHz     | FDD         |
+| 22                    | 3410 MHz                                                | 3490 MHz       | 3510 MHz                                                  | 3590 MHz       | FDD         |
+| 23                    | 2000 MHz                                                | 2020 MHz       | 2180 MHz                                                  | 2200 MHz       | FDD         |
+| 24                    | 1626.5 MHz                                              | 1660.5 MHz     | 1525 MHz                                                  | 1559 MHz       | FDD         |
+| 25                    | 1850 MHz                                                | 1915 MHz       | 1930 MHz                                                  | 1995 MHz       | FDD         |
+| 26                    | 814 MHz                                                 | 849 MHz        | 859 MHz                                                   | 894 MHz        | FDD         |
+| 27                    | 807 MHz                                                 | 824 MHz        | 852 MHz                                                   | 869 MHz        | FDD         |
+| 28                    | 703 MHz                                                 | 748 MHz        | 758 MHz                                                   | 803 MHz        | FDD         |
+
+**Table 5.3-1: Measurement frequency allocations for TRP (FDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 1</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 50             | 18050     | 10         | 2115                 | 1925                 | Note 1              | Note 1                 | 12                  | 0                      |
+| 300            | 18300     | 10         | 2140                 | 1950                 | Note 1              | Note 1                 | 12                  | 19                     |
+| 550            | 18550     | 10         | 2165                 | 1975                 | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 2</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 650            | 18650     | 10         | 1935                 | 1855                 | Note 1              | Note 1                 | 12                  | 0                      |
+| 900            | 18900     | 10         | 1960                 | 1880                 | Note 1              | Note 1                 | 12                  | 19                     |
+| 1150           | 19150     | 10         | 1985                 | 1905                 | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 3</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 1250           | 19250     | 10         | 1810                 | 1715                 | Note 1              | Note 1                 | 12                  | 0                      |
+| 1575           | 19575     | 10         | 1842,5               | 1747,5               | Note 1              | Note 1                 | 12                  | 19                     |
+| 1900           | 19900     | 10         | 1875                 | 1780                 | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 4</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2000           | 20000     | 10         | 2115                 | 1715                 | Note 1              | Note 1                 | 12                  | 0                      |
+| 2175           | 20175     | 10         | 2132,5               | 1732,5               | Note 1              | Note 1                 | 12                  | 19                     |
+| 2350           | 20350     | 10         | 2150                 | 1750                 | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 5</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2450           | 20450     | 10         | 874                  | 829                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 2525           | 20525     | 10         | 881,5                | 836,5                | Note 1              | Note 1                 | 12                  | 19                     |
+| 2600           | 20600     | 10         | 889                  | 844                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 7</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2800           | 20800     | 10         | 2625                 | 2505                 | Note 1              | Note 1                 | 12                  | 0                      |
+| 3100           | 21100     | 10         | 2655                 | 2535                 | Note 1              | Note 1                 | 12                  | 19                     |
+| 3400           | 21400     | 10         | 2685                 | 2565                 | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 8</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 3500           | 21500     | 10         | 930                  | 885                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 3625           | 21625     | 10         | 942,5                | 897,5                | Note 1              | Note 1                 | 12                  | 19                     |
+| 3750           | 21750     | 10         | 955                  | 910                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 12</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5060           | 23060     | 10         | 734                  | 704                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 5095           | 23095     | 10         | 737,5                | 707,5                | Note 1              | Note 1                 | 12                  | 19                     |
+| 5130           | 23130     | 10         | 741                  | 711                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 13</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5230           | 23230     | 10         | 751                  | 782                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | Note 1              | Note 1                 | 12                  | 19                     |
+| 5230           | 23230     | 10         | 751                  | 782                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 14</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5330           | 23330     | 10         | 763                  | 793                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | Note 1              | Note 1                 | 12                  | 19                     |
+| 5330           | 23330     | 10         | 763                  | 793                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 17</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5780           | 23780     | 10         | 739                  | 709                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 5790           | 23790     | 10         | 740                  | 710                  | Note 1              | Note 1                 | 12                  | 19                     |
+| 5800           | 23800     | 10         | 741                  | 711                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 19</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6050           | 24050     | 10         | 880                  | 835                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 6075           | 24075     | 10         | 882,5                | 837,5                | Note 1              | Note 1                 | 12                  | 19                     |
+| 6100           | 24100     | 10         | 885                  | 840                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 20</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6200           | 24200     | 10         | 796                  | 837                  | Note 1              | Note 1                 | 12                  | 0                      |
+| 6300           | 24300     | 10         | 806                  | 847                  | Note 1              | Note 1                 | 12                  | 19                     |
+| 6400           | 24400     | 10         | 816                  | 857                  | Note 1              | Note 1                 | 12                  | 38                     |
+| <b>Band 21</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6525           | 24525     | 15         | 1503,4               | 1455,4               | Note 1              | Note 1                 | 16                  | 0                      |
+| 6525           | 24525     | 15         | 1503,4               | 1455,4               | Note 1              | Note 1                 | 16                  | 29                     |
+| 6525           | 24525     | 15         | 1503,4               | 1455,4               | Note 1              | Note 1                 | 16                  | 59                     |
+| <b>Band 22</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 23</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+
+|                                                                                                                                                                   |       |     |        |        |        |        |     |     |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----|--------|--------|--------|--------|-----|-----|
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 24</b>                                                                                                                                                    |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 25</b>                                                                                                                                                    |       |     |        |        |        |        |     |     |
+| 8065                                                                                                                                                              | 26065 | 5   | 1932.5 | 1852.5 | Note 1 | Note 1 | 8   | 0   |
+| 8365                                                                                                                                                              | 26365 | 5   | 1962.5 | 1882.5 | Note 1 | Note 1 | 8   | 8   |
+| 8665                                                                                                                                                              | 26665 | 5   | 1992.5 | 1912.5 | Note 1 | Note 1 | 8   | 17  |
+| <b>Band 26</b>                                                                                                                                                    |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 27</b>                                                                                                                                                    |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 28</b>                                                                                                                                                    |       |     |        |        |        |        |     |     |
+| 9260                                                                                                                                                              | 27260 | 10  | 763    | 708    | Note 1 | Note 1 | 12  | 0   |
+| 9410                                                                                                                                                              | 27410 | 10  | 778    | 723    | Note 1 | Note 1 | 12  | 19  |
+| 9610                                                                                                                                                              | 27610 | 10  | 798    | 743    | Note 1 | Note 1 | 12  | 38  |
+| Note 1: As per 3GPP TS 36.521-1 [11], Section 6.2 (UE Maximum Output Power), and Section A.3.2.A (Downlink Reference measurement channel for TX characteristics). |       |     |        |        |        |        |     |     |
+| Note 2: Network signalling value NS_01 shall be used in TRP test                                                                                                  |       |     |        |        |        |        |     |     |
+
+**Table 5.3-2: Measurement frequency allocations for TRS (FDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 1</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 50             | 18050     | 10         | 2115                 | 1925                 | 50                  | 0                      | 50                  | 0                      |
+| 300            | 18300     | 10         | 2140                 | 1950                 | 50                  | 0                      | 50                  | 0                      |
+| 550            | 18550     | 10         | 2165                 | 1975                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 2</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 650            | 18650     | 10         | 1935                 | 1855                 | 50                  | 0                      | 50                  | 0                      |
+| 900            | 18900     | 10         | 1960                 | 1880                 | 50                  | 0                      | 50                  | 0                      |
+| 1150           | 19150     | 10         | 1985                 | 1905                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 3</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 1250           | 19250     | 10         | 1810                 | 1715                 | 50                  | 0                      | 50                  | 0                      |
+| 1575           | 19575     | 10         | 1842,5               | 1747,5               | 50                  | 0                      | 50                  | 0                      |
+| 1900           | 19900     | 10         | 1875                 | 1780                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 4</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2000           | 20000     | 10         | 2115                 | 1715                 | 50                  | 0                      | 50                  | 0                      |
+| 2175           | 20175     | 10         | 2132,5               | 1732,5               | 50                  | 0                      | 50                  | 0                      |
+| 2350           | 20350     | 10         | 2150                 | 1750                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 5</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2450           | 20450     | 10         | 874                  | 829                  | 50                  | 0                      | 25                  | 25                     |
+| 2525           | 20525     | 10         | 881,5                | 836,5                | 50                  | 0                      | 25                  | 25                     |
+| 2600           | 20600     | 10         | 889                  | 844                  | 50                  | 0                      | 25                  | 25                     |
+| <b>Band 7</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2800           | 20800     | 10         | 2625                 | 2505                 | 50                  | 0                      | 50                  | 0                      |
+| 3100           | 21100     | 10         | 2655                 | 2535                 | 50                  | 0                      | 50                  | 0                      |
+| 3400           | 21400     | 10         | 2685                 | 2565                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 8</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 3500           | 21500     | 10         | 930                  | 885                  | 50                  | 0                      | 25                  | 25                     |
+| 3625           | 21625     | 10         | 942,5                | 897,5                | 50                  | 0                      | 25                  | 25                     |
+| 3750           | 21750     | 10         | 955                  | 910                  | 50                  | 0                      | 25                  | 25                     |
+| <b>Band 12</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5060           | 23060     | 10         | 734                  | 704                  | 50                  | 0                      | 20                  | 30                     |
+| 5095           | 23095     | 10         | 737,5                | 707,5                | 50                  | 0                      | 20                  | 30                     |
+| 5130           | 23130     | 10         | 741                  | 711                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 13</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| <b>Band 14</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| <b>Band 17</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5780           | 23780     | 10         | 739                  | 709                  | 50                  | 0                      | 20                  | 30                     |
+| 5790           | 23790     | 10         | 740                  | 710                  | 50                  | 0                      | 20                  | 30                     |
+| 5800           | 23800     | 10         | 741                  | 711                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 19</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6050           | 24050     | 10         | 880                  | 835                  | 50                  | 0                      | 25                  | 0                      |
+| 6075           | 24075     | 10         | 882,5                | 837,5                | 50                  | 0                      | 25                  | 0                      |
+| 6100           | 24100     | 10         | 885                  | 840                  | 50                  | 0                      | 25                  | 0                      |
+| <b>Band 20</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6200           | 24200     | 10         | 796                  | 837                  | 50                  | 0                      | 20                  | 30                     |
+| 6300           | 24300     | 10         | 806                  | 847                  | 50                  | 0                      | 20                  | 30                     |
+| 6400           | 24400     | 10         | 816                  | 857                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 21</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | 75                  | 0                      | 25                  | 0                      |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | 75                  | 0                      | 25                  | 0                      |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | 75                  | 0                      | 25                  | 0                      |
+| <b>Band 22</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 23</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+
+|                                                                                                                                   |       |     |        |        |     |     |     |     |
+|-----------------------------------------------------------------------------------------------------------------------------------|-------|-----|--------|--------|-----|-----|-----|-----|
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 24</b>                                                                                                                    |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 25</b>                                                                                                                    |       |     |        |        |     |     |     |     |
+| 8065                                                                                                                              | 26065 | 5   | 1932.5 | 1852.5 | 25  | 0   | 25  | 0   |
+| 8365                                                                                                                              | 26365 | 5   | 1962.5 | 1882.5 | 25  | 0   | 25  | 0   |
+| 8665                                                                                                                              | 26665 | 5   | 1992.5 | 1912.5 | 25  | 0   | 25  | 0   |
+| <b>Band 26</b>                                                                                                                    |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 27</b>                                                                                                                    |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                               | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 28</b>                                                                                                                    |       |     |        |        |     |     |     |     |
+| 9260                                                                                                                              | 27260 | 10  | 763    | 708    | 50  | 0   | 25  | 0   |
+| 9410                                                                                                                              | 27410 | 10  | 778    | 723    | 50  | 0   | 25  | 0   |
+| 9610                                                                                                                              | 27610 | 10  | 798    | 743    | 50  | 0   | 25  | 0   |
+| Note 1: Refer to TS 36.521-1-1 [11], Table A.3.2-1 (Fixed Reference Channel for Receiver Requirements (FDD)), 10MHz configuration |       |     |        |        |     |     |     |     |
+| Note 2: Network signalling value NS_01 shall be used in TRS tests unless explicitly specified                                     |       |     |        |        |     |     |     |     |
+| Note 3: Network signalling value NS_03 shall be used for Bands 2, 4, and 23                                                       |       |     |        |        |     |     |     |     |
+| Note 4: Network signalling value NS_06 shall be used for Bands 12, 13, 14, and 17                                                 |       |     |        |        |     |     |     |     |
+| Note 5: Network signalling value NS_08 shall be used for Band 19                                                                  |       |     |        |        |     |     |     |     |
+| Note 6: Network signalling value NS_09 shall be used for Band 21                                                                  |       |     |        |        |     |     |     |     |
+
+## 5.4 E-UTRA TDD frequency bands and measurement frequencies allocations
+
+Editor's notes: This Subclause is incomplete. The following item is missing or incomplete:
+
+- TBDs in Tables 5.4-1 (TRP) and 5.4.3 (TRS)
+
+This section specifies the LTE-TDD TRP and TRS frequency bands and measurement frequencies allocations. Table 5.4-0 lists the operating bands. Table 5.4-1 specifies the measurement frequency allocations for TRP and Table 5.4-2 specifies the measurement frequency allocations for TRS.
+
+**Table 5.4-0 E-UTRA TDD operating bands for TRP and TRS**
+
+| E-UTRA Operating Band | Uplink (UL) operating band<br>BS receive<br>UE transmit |            | Downlink (DL) operating band<br>BS transmit<br>UE receive |            | Duplex Mode |
+|-----------------------|---------------------------------------------------------|------------|-----------------------------------------------------------|------------|-------------|
+|                       | $F_{UL\_low} - F_{UL\_high}$                            |            | $F_{DL\_low} - F_{DL\_high}$                              |            |             |
+| 33                    | 1900 MHz                                                | – 1920 MHz | 1900 MHz                                                  | – 1920 MHz | TDD         |
+| 34                    | 2010 MHz                                                | – 2025 MHz | 2010 MHz                                                  | – 2025 MHz | TDD         |
+| 35                    | 1850 MHz                                                | – 1910 MHz | 1850 MHz                                                  | – 1910 MHz | TDD         |
+| 36                    | 1930 MHz                                                | – 1990 MHz | 1930 MHz                                                  | – 1990 MHz | TDD         |
+| 37                    | 1910 MHz                                                | – 1930 MHz | 1910 MHz                                                  | – 1930 MHz | TDD         |
+| 38                    | 2570 MHz                                                | – 2620 MHz | 2570 MHz                                                  | – 2620 MHz | TDD         |
+| 39                    | 1880 MHz                                                | – 1920 MHz | 1880 MHz                                                  | – 1920 MHz | TDD         |
+| 40                    | 2300 MHz                                                | – 2400 MHz | 2300 MHz                                                  | – 2400 MHz | TDD         |
+| 41                    | 2496 MHz                                                | – 2690 MHz | 2496 MHz                                                  | – 2690 MHz | TDD         |
+| 42                    | 3400 MHz                                                | – 3600 MHz | 3400 MHz                                                  | – 3600 MHz | TDD         |
+| 43                    | 3600 MHz                                                | – 3800 MHz | 3600 MHz                                                  | – 3800 MHz | TDD         |
+| 44                    | 703 MHz                                                 | – 803 MHz  | 703 MHz                                                   | – 803 MHz  | TDD         |
+
+**Table 5.4-1: Measurement frequency allocations for TRP (TDD)**
+
+| DL EARFCN      | UL EARFCN                                                                                                                                                 | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 33</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 36100          | 36100                                                                                                                                                     | 20         | 1910                 | 1910                 | Note 1              | Note 1                 | 18                  | 41                     |
+| <b>Band 34</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD                                                                                                                                                       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 35</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 36450          | 36450                                                                                                                                                     | 20         | 1860                 | 1860                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 36650          | 36650                                                                                                                                                     | 20         | 1880                 | 1880                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 36850          | 36850                                                                                                                                                     | 20         | 1900                 | 1900                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 36</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 37050          | 37050                                                                                                                                                     | 20         | 1940                 | 1940                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 37250          | 37250                                                                                                                                                     | 20         | 1960                 | 1960                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 37450          | 37450                                                                                                                                                     | 20         | 1980                 | 1980                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 37</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 37650          | 37650                                                                                                                                                     | 20         | 1920                 | 1920                 | Note 1              | Note 1                 | 18                  | 41                     |
+| <b>Band 38</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 37850          | 37850                                                                                                                                                     | 20         | 2580                 | 2580                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 38000          | 38000                                                                                                                                                     | 20         | 2595                 | 2595                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 38150          | 38150                                                                                                                                                     | 20         | 2610                 | 2610                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 39</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 38350          | 38350                                                                                                                                                     | 20         | 1890                 | 1890                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 38450          | 38450                                                                                                                                                     | 20         | 1900                 | 1900                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 38550          | 38550                                                                                                                                                     | 20         | 1910                 | 1910                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 40</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 38750          | 38750                                                                                                                                                     | 20         | 2310                 | 2310                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 39150          | 39150                                                                                                                                                     | 20         | 2350                 | 2350                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 39550          | 39550                                                                                                                                                     | 20         | 2390                 | 2390                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 41</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 39750          | 39750                                                                                                                                                     | 20         | 2506                 | 2506                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 40620          | 40620                                                                                                                                                     | 20         | 2593                 | 2593                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 41490          | 41490                                                                                                                                                     | 20         | 2680                 | 2680                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 42</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 41690          | 41690                                                                                                                                                     | 20         | 3410                 | 3410                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 42590          | 42590                                                                                                                                                     | 20         | 3500                 | 3500                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 43490          | 43490                                                                                                                                                     | 20         | 3590                 | 3590                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 43</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| 43690          | 43690                                                                                                                                                     | 20         | 3610                 | 3610                 | Note 1              | Note 1                 | 18                  | 0                      |
+| 44590          | 44590                                                                                                                                                     | 20         | 3700                 | 3700                 | Note 1              | Note 1                 | 18                  | 41                     |
+| 45490          | 45490                                                                                                                                                     | 20         | 3790                 | 3790                 | Note 1              | Note 1                 | 18                  | 82                     |
+| <b>Band 44</b> |                                                                                                                                                           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD                                                                                                                                                       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| Note 1:        | As per 3GPP TS 36.521-1 [11], Section 6.2 (UE Maximum Output Power), and Section A.3.2.A (Downlink Reference measurement channel for TX characteristics). |            |                      |                      |                     |                        |                     |                        |
+| Note 2:        | Network signalling value NS_01 shall be used in TRP tests.                                                                                                |            |                      |                      |                     |                        |                     |                        |
+
+**Table 5.4-2: Measurement frequency allocations for TRS (TDD)**
+
+| DL EARFCN                                                                                                                      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|--------------------------------------------------------------------------------------------------------------------------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 33</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 36100                                                                                                                          | 36100     | 20         | 1910                 | 1910                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 34</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| TBD                                                                                                                            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 35</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 36450                                                                                                                          | 36450     | 20         | 1860                 | 1860                 | 100                 | 0                      | 100                 | 0                      |
+| 36650                                                                                                                          | 36650     | 20         | 1880                 | 1880                 | 100                 | 0                      | 100                 | 0                      |
+| 36850                                                                                                                          | 36850     | 20         | 1900                 | 1900                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 36</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 37050                                                                                                                          | 37050     | 20         | 1940                 | 1940                 | 100                 | 0                      | 100                 | 0                      |
+| 37250                                                                                                                          | 37250     | 20         | 1960                 | 1960                 | 100                 | 0                      | 100                 | 0                      |
+| 37450                                                                                                                          | 37450     | 20         | 1980                 | 1980                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 37</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 37650                                                                                                                          | 37650     | 20         | 1920                 | 1920                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 38</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 37850                                                                                                                          | 37850     | 20         | 2580                 | 2580                 | 100                 | 0                      | 100                 | 0                      |
+| 38000                                                                                                                          | 38000     | 20         | 2595                 | 2595                 | 100                 | 0                      | 100                 | 0                      |
+| 38150                                                                                                                          | 38150     | 20         | 2610                 | 2610                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 39</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 38350                                                                                                                          | 38350     | 20         | 1890                 | 1890                 | 100                 | 0                      | 100                 | 0                      |
+| 38450                                                                                                                          | 38450     | 20         | 1900                 | 1900                 | 100                 | 0                      | 100                 | 0                      |
+| 38550                                                                                                                          | 38550     | 20         | 1910                 | 1910                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 40</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 38750                                                                                                                          | 38750     | 20         | 2310                 | 2310                 | 100                 | 0                      | 100                 | 0                      |
+| 39150                                                                                                                          | 39150     | 20         | 2350                 | 2350                 | 100                 | 0                      | 100                 | 0                      |
+| 39550                                                                                                                          | 39550     | 20         | 2390                 | 2390                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 41</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 39750                                                                                                                          | 39750     | 20         | 2506                 | 2506                 | 100                 | 0                      | 100                 | 0                      |
+| 40620                                                                                                                          | 40620     | 20         | 2593                 | 2593                 | 100                 | 0                      | 100                 | 0                      |
+| 41490                                                                                                                          | 41490     | 20         | 2680                 | 2680                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 42</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 41690                                                                                                                          | 41690     | 20         | 3410                 | 3410                 | 100                 | 0                      | 100                 | 0                      |
+| 42590                                                                                                                          | 42590     | 20         | 3500                 | 3500                 | 100                 | 0                      | 100                 | 0                      |
+| 43490                                                                                                                          | 43490     | 20         | 3590                 | 3590                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 43</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| 43690                                                                                                                          | 43690     | 20         | 3610                 | 3610                 | 100                 | 0                      | 100                 | 0                      |
+| 44590                                                                                                                          | 44590     | 20         | 3700                 | 3700                 | 100                 | 0                      | 100                 | 0                      |
+| 45490                                                                                                                          | 45490     | 20         | 3790                 | 3790                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 44</b>                                                                                                                 |           |            |                      |                      |                     |                        |                     |                        |
+| TBD                                                                                                                            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| Note 1: Refer to TS 36.521-1 [7], Table A.3.2-2 (Fixed Reference Channel for Receiver Requirements (TDD)), 20MHz configuration |           |            |                      |                      |                     |                        |                     |                        |
+| Note 2: Network signalling value NS_01 shall be used in TRS tests                                                              |           |            |                      |                      |                     |                        |                     |                        |
+
+## 5.5 E-UTRA FDD operating bands and measurement frequency allocations for receiver total radiated multi-antenna sensitivity
+
+This section specifies the E-UTRA FDD operating bands and measurement frequency allocations for TRMS. Table 5.5-1 lists the operating bands and Table 5.5-2 specifies the measurement frequency allocations for TRMS.
+
+**Table 5.5-1 E-UTRA FDD operating bands for receiver total radiated multi-antenna sensitivity requirements**
+
+| E-UTRA Operating Band                                                                                                                                                                                                                            | Uplink (UL) operating band<br>BS receive<br>UE transmit | Downlink (DL) operating band<br>BS transmit<br>UE receive | Duplex Mode      |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-----------------------------------------------------------|------------------|
+|                                                                                                                                                                                                                                                  | $F_{UL\_low} - F_{UL\_high}$                            | $F_{DL\_low} - F_{DL\_high}$                              |                  |
+| 1                                                                                                                                                                                                                                                | 1920 MHz – 1980 MHz                                     | 2110 MHz – 2170 MHz                                       | FDD              |
+| 2                                                                                                                                                                                                                                                | 1850 MHz – 1910 MHz                                     | 1930 MHz – 1990 MHz                                       | FDD              |
+| 3                                                                                                                                                                                                                                                | 1710 MHz – 1785 MHz                                     | 1805 MHz – 1880 MHz                                       | FDD              |
+| 4                                                                                                                                                                                                                                                | 1710 MHz – 1755 MHz                                     | 2110 MHz – 2155 MHz                                       | FDD              |
+| 5                                                                                                                                                                                                                                                | 824 MHz – 849 MHz                                       | 869 MHz – 894 MHz                                         | FDD              |
+| 7                                                                                                                                                                                                                                                | 2500 MHz – 2570 MHz                                     | 2620 MHz – 2690 MHz                                       | FDD              |
+| 8                                                                                                                                                                                                                                                | 880 MHz – 915 MHz                                       | 925 MHz – 960 MHz                                         | FDD              |
+| 12                                                                                                                                                                                                                                               | 699 MHz – 716 MHz                                       | 729 MHz – 746 MHz                                         | FDD              |
+| 13                                                                                                                                                                                                                                               | 777 MHz – 787 MHz                                       | 746 MHz – 756 MHz                                         | FDD              |
+| 19                                                                                                                                                                                                                                               | 830 MHz – 845 MHz                                       | 875 MHz – 890 MHz                                         | FDD              |
+| 20                                                                                                                                                                                                                                               | 832 MHz – 862 MHz                                       | 791 MHz – 821 MHz                                         | FDD              |
+| 28                                                                                                                                                                                                                                               | 703 MHz – 748 MHz                                       | 758 MHz – 803 MHz                                         | FDD              |
+| 32                                                                                                                                                                                                                                               | N/A                                                     | 1452 MHz – 1496 MHz                                       | FDD <sup>1</sup> |
+| NOTE 1: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell. |                                                         |                                                           |                  |
+
+Deployment in other frequency bands is not precluded.
+
+**Table 5.5-2: Measurement frequency allocations for TRMS (FDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL $C_{LRB}$ | DL $RB_{Start}$ | UL $C_{LRB}$ | UL $RB_{Start}$ |
+|----------------|-----------|------------|----------------------|----------------------|--------------|-----------------|--------------|-----------------|
+| <b>Band 1</b>  |           |            |                      |                      |              |                 |              |                 |
+| 300            | 18300     | 10         | 2140                 | 1950                 | 50           | 0               | 50           | 0               |
+| <b>Band 2</b>  |           |            |                      |                      |              |                 |              |                 |
+| 900            | 18900     | 10         | 1960                 | 1880                 | 50           | 0               | 50           | 0               |
+| <b>Band 3</b>  |           |            |                      |                      |              |                 |              |                 |
+| 1575           | 19575     | 10         | 1842,5               | 1747,5               | 50           | 0               | 50           | 0               |
+| <b>Band 4</b>  |           |            |                      |                      |              |                 |              |                 |
+| 2175           | 20175     | 10         | 2132,5               | 1732,5               | 50           | 0               | 50           | 0               |
+| <b>Band 5</b>  |           |            |                      |                      |              |                 |              |                 |
+| 2525           | 20525     | 10         | 881,5                | 836,5                | 50           | 0               | 50           | 0               |
+| <b>Band 7</b>  |           |            |                      |                      |              |                 |              |                 |
+| 3100           | 21100     | 10         | 2655                 | 2535                 | 50           | 0               | 50           | 0               |
+| <b>Band 8</b>  |           |            |                      |                      |              |                 |              |                 |
+| 3625           | 21625     | 10         | 942,5                | 897,5                | 50           | 0               | 50           | 0               |
+| <b>Band 12</b> |           |            |                      |                      |              |                 |              |                 |
+| 5095           | 23095     | 10         | 737,5                | 707,5                | 50           | 0               | 50           | 0               |
+| <b>Band 13</b> |           |            |                      |                      |              |                 |              |                 |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50           | 0               | 50           | 0               |
+| <b>Band 19</b> |           |            |                      |                      |              |                 |              |                 |
+| 6075           | 24075     | 10         | 882,5                | 837,5                | 50           | 0               | 50           | 0               |
+| <b>Band 20</b> |           |            |                      |                      |              |                 |              |                 |
+| 6300           | 24300     | 10         | 806                  | 847                  | 50           | 0               | 50           | 0               |
+| <b>Band 28</b> |           |            |                      |                      |              |                 |              |                 |
+| 9410           | 27410     | 10         | 778                  | 723                  | 50           | 0               | 50           | 0               |
+| <b>Band 32</b> |           |            |                      |                      |              |                 |              |                 |
+| 10140          | N/A       | 10         | 1474                 | N/A                  | 50           | 0               | N/A          | N/A             |
+
+## 5.6 E-UTRA TDD operating bands and measurement frequency allocations for receiver total radiated multi-antenna sensitivity
+
+This section specifies the E-UTRA TDD operating bands and measurement frequency allocations for TRMS. Table 5.6-1 lists the operating bands and Table 5.6-2 specifies the measurement frequency allocations for TRMS.
+
+**Table 5.6-1 E-UTRA TDD operating bands for receiver total radiated multi-antenna sensitivity requirements**
+
+| E-UTRA Operating Band                                                                                                                                                                                                                      | Uplink (UL) operating band<br>BS receive<br>UE transmit |            | Downlink (DL) operating band<br>BS transmit<br>UE receive |            | Duplex Mode        |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|------------|-----------------------------------------------------------|------------|--------------------|
+|                                                                                                                                                                                                                                            | $F_{UL\_low} - F_{UL\_high}$                            |            | $F_{DL\_low} - F_{DL\_high}$                              |            |                    |
+| 38                                                                                                                                                                                                                                         | 2570 MHz                                                | – 2620 MHz | 2570 MHz                                                  | – 2620 MHz | TDD                |
+| 39                                                                                                                                                                                                                                         | 1880 MHz                                                | – 1920 MHz | 1880 MHz                                                  | – 1920 MHz | TDD                |
+| 40                                                                                                                                                                                                                                         | 2300 MHz                                                | – 2400 MHz | 2300 MHz                                                  | – 2400 MHz | TDD                |
+| 41                                                                                                                                                                                                                                         | 2496 MHz                                                | – 2690 MHz | 2496 MHz                                                  | – 2690 MHz | TDD                |
+| 42                                                                                                                                                                                                                                         | 3400 MHz                                                | – 3600 MHz | 3400 MHz                                                  | – 3600 MHz | TDD                |
+| 46                                                                                                                                                                                                                                         | 5150 MHz                                                | – 5925 MHz | 5150 MHz                                                  | – 5925 MHz | TDD <sup>1,2</sup> |
+| NOTE 1: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3.<br>NOTE 2: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured. |                                                         |            |                                                           |            |                    |
+
+Deployment in other frequency bands is not precluded.
+
+**Table 5.6-2: Measurement frequency allocations for TRMS (TDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 38</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 38000          | 38000     | 20         | 2595                 | 2595                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 39</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 38450          | 38450     | 20         | 1900                 | 1900                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 40</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 39150          | 39150     | 20         | 2350                 | 2350                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 41</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 40620          | 40620     | 20         | 2593                 | 2593                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 42</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 42590          | 42590     | 20         | 3500                 | 3500                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 46</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 50665          | 50665     | 20         | 5537,5               | 5537,5               | 100                 | 0                      | 100                 | 0                      |
+
+## 6 Transmitter Performance
+
+### 6.1 Performance for handheld UE
+
+#### 6.1.1 Total Radiated Power (TRP) for UTRA FDD in Speech Mode with beside the Head Phantom
+
+##### 6.1.1.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{tx}$  are the orthogonal polarizations, and  $P_{tx}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+### 6.1.1.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.1.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.1.2-1: TRP minimum performance requirement for FDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |      | Power Class 3bis |      | Power Class 4 |      |
+|----------------|---------------|---------------|---------------|------|------------------|------|---------------|------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)      |      | Power (dBm)   |      |
+|                |               |               | Average       | Min  | Average          | Min  | Average       | Min  |
+| I              | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| II             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| III            | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| IV             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| V              | -             | -             | +11           | +9   | +11              | +9   | +9            | +7   |
+| VI             | -             | -             | +11           | +9   | +11              | +9   | +9            | +7   |
+| VII            | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| VIII           | -             | -             | +12           | +10  | +12              | +10  | +10           | +8   |
+| IX             | -             | -             | +15           | +13  | +15              | +13  | +13           | +11  |
+| XIX            | -             | -             | +11.5         | +9.5 | +11.5            | +9.5 | +9.5          | +7.5 |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+The normative reference for this Subclause is TS 37.144 Subclause 6.1.1.2.
+
+### 6.1.1.3 Test purpose
+
+The purpose of this test is to verify that  $P_{max}$  and  $P_{max} - \Delta$  of the UE is not below specified values. A lower  $P_{max}$  and  $P_{max} - \Delta$  decrease the coverage area.
+
+### 6.1.1.4 Method of test
+
+#### 6.1.1.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.121-1 [7] chapter 5.2. The period of measurement shall be at least one timeslot. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Test environment: normal; see TS34.121-1 [7] Annex G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.1.1.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 4) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.1.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                    |
+|------------------|------------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$    |
+| P-CCPCH          | $P\_CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$      |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$     |
+| DPCH             | Test dependent power                     |
+
+#### 6.1.1.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE against the SAM phantom
+- 4) Measure the  $P_{max}$  and  $P_{max} - \Delta$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.1.1
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations, - and -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{std}$  is power measurement done with standard setting,  $P_{nonstd}$  is power measurement done with non standard modulation,  $N_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.1.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE against the SAM phantom
+- 4) Measure a sufficient number of independent samples (see Subclause 4.5) of  $P_{std}$  using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.1.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+#### 6.1.1.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.1.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.1.5-1: TRP test requirement for FDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |     | Power Class 3bis |     | Power Class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+
+|                                          |   |   |          |         |              |         |         |         |
+|------------------------------------------|---|---|----------|---------|--------------|---------|---------|---------|
+| I                                        | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| II                                       | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| III                                      | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| IV                                       | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| V                                        | - | - | +10.3    | +8.0    | +10.3        | +8.0    | +8.3    | +6      |
+| VI                                       | - | - | +10.3    | +8.0    | +10.3        | +8.0    | +8.3    | +6      |
+| VII                                      | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| VIII                                     | - | - | +11.3    | +9.0    | +11.3        | +9.0    | +9.3    | +7      |
+| IX                                       | - | - | +14.3    | +12.0   | +14.3        | +12.0   | +12.3   | +10.0   |
+| XIX                                      | - | - | +11.5+TT | +9.0+TT | +11.5+T<br>T | +9.0+TT | +9.5+TT | +7.5+TT |
+| NOTE: Applicable for dual-mode GSM/UMTS. |   |   |          |         |              |         |         |         |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.1.2 Total Radiated Power (TRP) for UTRA LCR TDD in Speech Mode with beside the Head Phantom
+
+Editor's note: This test case is incomplete. The following aspects are either missing or not yet determined:
+
+- *The TRP Minimum Performance Requirement for operating bands b, c, d of this test is undefined*
+- *The Test Requirements and related Test Tolerances applicable for operating bands b, c, d of this test are undefined*
+
+### 6.1.2.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations.
+
+and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus,
+
+In these formulas  $N$  and  $M$  are the number of sampling intervals for theta and phi, and  $\theta_n$  and  $\phi_m$  are the measurement angles. The sampling intervals are discussed further in Section 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE/MS. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE/MS for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus,
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{avg,n}$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $P_{n,m}$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+### 6.1.2.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.2.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.2.2-1: TRP minimum performance requirement for UTRA LCR TDD using Head Phantom**
+
+| Operating band | Power Class 1                              |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|----------------|--------------------------------------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)                                |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average                                    | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | —                                          | —   | +15           | +13 | —             | —   | —             | —   |
+| b              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| c              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| d              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| e              | —                                          | —   | +15           | +13 | —             | —   | —             | —   |
+| f              | —                                          | —   | +15           | +13 | —             | —   | —             | —   |
+| Note:          | Applicable for dual-mode GSM/UTRA LCR TDD. |     |               |     |               |     |               |     |
+
+The normative reference for this clause is TS37.144 section 6.1.1.3.
+
+### 6.1.2.3 Test purpose
+
+The purpose of this test is to verify that and of the UE are not below specified values. A lower and decrease the coverage area.
+
+### 6.1.2.4 Method of test
+
+#### 6.1.2.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.122 chapter 5.2. The period of measurement shall be at least one timeslot. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement. Normally, the receiving device should be set accordingly so that the receiving signal will be at least 30dB higher than the system noise floor.
+
+Test environment: normal; see 3GPP TS34.122-1 [8] clause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+- 1) Set the SS downlink physical channels parameters. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 4) Enter the UE into loopback test mode and start the loopback test.
+- 5) The measurement receiver shall be set to: zero span, video trigger and RMS detector. The RBW shall be at least  $(1 + \alpha)$  times the chip rate of the radio access mode and the VBW at least 3 times bigger than the RBW. For 1.28Mcps TDD UE, the RBW shall be set to 3MHz, and VBW shall be set to 10MHz.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+#### 6.1.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE against the SAM phantom.
+- 4) Measure the  $EIRP_{\theta}$  and  $EIRP_{\phi}$  with a sample step of  $15^{\circ}$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from chapter 6.1.2.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^{\circ}$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Section 4.4). All the EIRP samples are taken with two orthogonal polarizations,  $\theta$ - and  $\phi$ - polarizations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $EIRPstd_i$  is power measurement done with standard setting.  $EIRPnstd_i$  is power measurement done with non standard modulation.  $n$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.2.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE against the SAM phantom
+- 4) Measure a sufficient number of independent samples (see section 4.5) of using a test system having the characteristics described in Annex A.
+- 5) Calculate TRP using equations from section 6.1.2.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE/MS to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+#### 6.1.2.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.2.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.2.5-1: TRP test performance requirement for UTRA LCR TDD using Head Phantom**
+
+| Operating band                                   | Power Class 1 |     | Power Class 2 |        | Power Class 3 |     | Power Class 4 |     |
+|--------------------------------------------------|---------------|-----|---------------|--------|---------------|-----|---------------|-----|
+|                                                  | Power (dBm)   |     | Power (dBm)   |        | Power (dBm)   |     | Power (dBm)   |     |
+|                                                  | Average       | Min | Average       | Min    | Average       | Min | Average       | Min |
+| a                                                | —             | —   | +14.3         | +12    | —             | —   | —             | —   |
+| b                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| c                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| d                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| e                                                | —             | —   | +14.3         | +12    | —             | —   | —             | —   |
+| f                                                | —             | —   | +14.3         | +12    | —             | —   | —             | —   |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |               |     |               |        |               |     |               |     |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 6.1.3 Total Radiated Power (TRP) for UTRA FDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor's notes: This Subclause is incomplete. The following items are missing or incomplete:
+
+- TBDs in Table 6.1.3.2-1 and 6.1.3.5-1 as they are not specified in TS 37.144 yet
+
+#### 6.1.3.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency,  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+### 6.1.3.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.3.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.1.3.2-1: TRP minimum performance requirement for UTRA FDD roaming bands in the speech mode and the primary mechanical mode**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |     | Power Class 3bis |     | Power Class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+| I              | -             | -             | 13.25         | TBD | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | 13.25         | TBD | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | 9.40          | TBD | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | 9.4           | TBD | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | 9.40          | TBD | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | 9.4           | TBD | TBD              | TBD | TBD           | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914.  
+NOTE 3: Not applicable for devices supporting CDMA or carrier aggregation.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.2.1.
+
+### 6.1.3.3 Test purpose
+
+The purpose of this test is to verify that and of the UE is not below specified values. A lower and decrease the coverage area.
+
+### 6.1.3.4 Method of test
+
+#### 6.1.3.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.121-1 [7] Subclause 5.2. The period of measurement shall be at least one timeslot. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Test environment: normal; see TS 34.121-1 [7] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.1.3.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 4) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.1.3.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                   |
+|------------------|-----------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$   |
+| P-CCPCH          | $P-CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$     |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$    |
+| DPCH             | Test dependent power                    |
+
+#### 6.1.3.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 4) Measure the  $P_{ref}$  and  $P_{non}$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.3.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations,  $+$  and  $-$  polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{ref}$  is power measurement done with standard setting,  $P_{non}$  is power measurement done with non standard modulation,  $P_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.3.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 4) Measure a sufficient number of independent samples (see Subclause 4.5) of  $P_{ref}$  using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.3.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+### 6.1.3.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.3.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.3.5-1: TRP test requirement for UTRA FDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band                                                             | Power Class 1 | Power Class 2 | Power Class 3 |        | Power Class 3bis |        | Power Class 4 |        |
+|----------------------------------------------------------------------------|---------------|---------------|---------------|--------|------------------|--------|---------------|--------|
+|                                                                            | Power (dBm)   | Power (dBm)   | Power (dBm)   |        | Power (dBm)      |        | Power (dBm)   |        |
+|                                                                            |               |               | Average       | Min    | Average          | Min    | Average       | Min    |
+| I                                                                          | -             | -             | 12.55         | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| II                                                                         | -             | -             | 12.55         | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| III                                                                        | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| IV                                                                         | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| V                                                                          | -             | -             | 8.70          | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VI                                                                         | -             | -             | 8.70          | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VII                                                                        | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VIII                                                                       | -             | -             | 8.70          | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| IX                                                                         | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| XIX                                                                        | -             | -             | 8.70          | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| NOTE 1: Applicable for dual-mode GSM/UMTS.                                 |               |               |               |        |                  |        |               |        |
+| NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914. |               |               |               |        |                  |        |               |        |
+| NOTE 3: Not applicable for devices supporting CDMA or carrier aggregation. |               |               |               |        |                  |        |               |        |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.1.4 Total Radiated Power (TRP) for UTRA LCR TDD in Speech Mode with beside the Head and Hand Phantom
+
+**Editor's notes: This Subclause is incomplete. The following items are missing or incomplete:**
+
+- TBDs in Tables 6.1.4.2-1 and 6.1.4.5-2 as they are not specified in TS 37.144 yet
+
+### 6.1.4.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna n,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna n and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna n. These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{avg,n}$  is the average power measured by fixed measurement antenna n and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna n and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+#### 6.1.4.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.4.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.1.4.2-1: TRP minimum performance requirement for UTRA LCR TDD roaming bands in the speech mode and the primary mechanical mode**
+
+| Operating band                                   | Power Class 1 |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|--------------------------------------------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                                                  | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                                                  | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| b                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| c                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| d                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| e                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| f                                                | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |               |     |               |     |               |     |               |     |
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.2.2.
+
+#### 6.1.4.3 Test purpose
+
+The purpose of this test is to verify that  $P_{ref,n}$  and  $\Gamma_n$  of the UE is not below specified values. A lower  $P_{ref,n}$  and decrease the coverage area.
+
+#### 6.1.4.4 Method of test
+
+##### 6.1.4.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.122 [8] Subclause 5.2. The period of measurement shall be at least one timeslot. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement. Normally, the receiving device should be set accordingly so that the receiving signal will be at least 30dB higher than the system noise floor.
+
+Test environment: normal; see 3GPP TS34.122-1 [8] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+- 1) Set the SS downlink physical channels parameters. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 4) Enter the UE into loopback test mode and start the loopback test.
+- 5) The measurement receiver shall be set to: zero span, video trigger and RMS detector. The RBW shall be at least  $(1 + \alpha)$  times the chip rate of the radio access mode and the VBW at least 3 times bigger than the RBW. For 1.28Mcsps TDD UE, the RBW shall be set to 3MHz, and VBW shall be set to 10MHz.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+##### 6.1.4.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 4) Measure the  $EIRP_{\theta}$  and  $EIRP_{\phi}$  with a sample step of  $15^{\circ}$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.4.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^{\circ}$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations,  $\theta$ - and  $\phi$  - polarizations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $EIRPstd_i$  is power measurement done with standard setting.  $EIRPnstd_i$  is power measurement done with non standard modulation.  $n$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.4.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 4) Measure a sufficient number of independent samples (see Subclause 4.5) of using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.4.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+#### 6.1.4.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.4.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.4.5-1: TRP test requirement for UTRA LCR TDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band | Power Class 1                              |     | Power Class 2 |        | Power Class 3 |     | Power Class 4 |     |
+|----------------|--------------------------------------------|-----|---------------|--------|---------------|-----|---------------|-----|
+|                | Power (dBm)                                |     | Power (dBm)   |        | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average                                    | Min | Average       | Min    | Average       | Min | Average       | Min |
+| a              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| b              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| c              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| d              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| e              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| f              | —                                          | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| Note:          | Applicable for dual-mode GSM/UTRA LCR TDD. |     |               |        |               |     |               |     |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+#### 6.1.5 Total Radiated Power (TRP) for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 6.1.5.2-1 and 6.1.5.5-1 as they are not specified in TS 37.144 yet
+
+### 6.1.5.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $\theta$  to denote either  $\theta$  or  $\phi$ , is the  $\theta$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{TX}$  is the transmit power level of the handset so that  $P_{TX} \cdot G_{\theta}(\Omega)$  is the actually transmitted power-level, also known as EIRP, in the  $\theta$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{TRP}$  is normalized to the transmitted power  $P_{TX}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $G_{\theta}(\Omega)$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_{\theta}$  and  $N_{\phi}$ , respectively. The sampling points of the sphere are given by  $\theta_m$  and  $\phi_n$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 6.1.5.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.5.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.5.2-1: TRP minimum performance requirement for E-UTRA FDD roaming mode in beside the head and hand phantom position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.2.3.
+
+### 6.1.5.3 Test purpose
+
+The purpose of this test is to verify that and of the UE is not below specified values. A lower and decrease the coverage area.
+
+### 6.1.5.4 Method of test
+
+#### 6.1.5.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-1 for FDD mode.
+
+#### 6.1.5.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Calculate the TRP using the EIRP pattern data as per Subclause 6.1.5.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.5.2.
+
+#### 6.1.5.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) Measure a sufficient number of independent samples (see Subclause 4.5) of using a test system having characteristics as described in Annex A. Calculate TRP using equations from Subclause 6.1.5.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.5.2.
+
+#### 6.1.5.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.5.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns ‐Min‑.
+
+**Table 6.1.5.5-1: TRP test requirement for E-UTRA FDD roaming bands in the speech position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 6.1.6 Total Radiated Power (TRP) for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 6.1.6.2-1 and 6.1.6.5-1 as they are not specified in TS 37.144 yet
+
+#### 6.1.6.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using to denote either or , is the -polarization component of the gain pattern for the handset antenna measured at the frequency , where is the solid angle describing the direction. is the transmit power level of the handset so that is the actually transmitted power-level, also known as EIRP, in the -polarization and in the direction for frequency .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{\text{TRP}}$  is normalized to the transmitted power . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_\theta$  and  $N_\phi$ , respectively. The sampling points of the sphere are given by  $\theta_m$  and  $\phi_n$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{n,m}$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 6.1.6.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.6.2-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.6.2-1: TRP minimum performance requirement for E-UTRA TDD roaming mode in beside the head and hand phantom position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.2.4.
+
+### 6.1.6.3 Test purpose
+
+The purpose of this test is to verify that  $\text{TRP}_{\text{max}}$  and  $\text{TRP}_{\text{min}}$  of the UE is not below specified values. A lower  $\text{TRP}_{\text{max}}$  and decrease the coverage area.
+
+#### 6.1.6.4 Method of test
+
+##### 6.1.6.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-1 for TDD mode.
+
+##### 6.1.6.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD is set as per Table 8.2.2-1 of 3GPP TS 36.521-1 [11]. Calculate the TRP using the EIRP pattern data as per Subclause 6.1.6.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.6.2.
+
+##### 6.1.6.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) Measure a sufficient number of independent samples (see Subclause 4.5) of using a test system having characteristics as described in Annex A. Calculate TRP using equations from Subclause 6.1.6.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.6.2.
+
+#### 6.1.6.5 Test requirements
+
+The average TRP of low, mid and high channel in beside head position shall be higher than test performance requirements for roaming bands shown in Table 6.1.6.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side of the phantom head.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.6.5-1: TRP test requirement for E-UTRA TDD roaming bands in the speech position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.1.7 Total Radiated Power (TRP) for UTRA FDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Minimum requirements are not specified in TS 37.144 yet
+- Text for Procedure, reverberation chamber method
+
+### 6.1.7.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency,  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus,
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus,
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+### 6.1.7.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.7.2-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.7.2-1: TRP minimum performance requirement for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |     | Power Class 3bis |     | Power Class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+| I              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| II             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| III            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IV             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| V              | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VI             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VII            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| VIII           | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| IX             | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+| XIX            | -             | -             | TBD           | TBD | TBD              | TBD | TBD           | TBD |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.3.1.
+
+### 6.1.7.3 Test purpose
+
+The purpose of this test is to verify that and of the UE is not below specified values. A lower and decrease the coverage area.
+
+### 6.1.7.4 Method of test
+
+#### 6.1.7.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.121-1 [7] Subclause 5.2. The period of measurement shall be at least one timeslot. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Test environment: normal; see TS34.121-1 [7] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.1.7.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 4) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.1.7.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                      | Power |
+|------------------|----------------------|-------|
+| CPICH            | CPICH_Ec / DPCH_Ec   | 7 dB  |
+| P-CCPCH          | P-CCPCH_Ec / DPCH_Ec | 5 dB  |
+| SCH              | SCH_Ec / DPCH_Ec     | 5 dB  |
+| PICH             | PICH_Ec / DPCH_Ec    | 2 dB  |
+| DPCH             | Test dependent power | -     |
+
+#### 6.1.7.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for browsing mode specified in Subclause 4.3.4.
+- 4) Measure the  $P_{rx}$  and  $P_{ref}$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.7.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations, - and -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{rx}$  is power measurement done with standard setting.  $P_{ref}$  is power measurement done with non standard modulation.  $P_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.7.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 6.1.7.5 Test requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than test performance requirements for roaming bands shown in Table 6.1.7.5-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.7.5-1: TRP test requirement for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |        | Power Class 3bis |        | Power Class 4 |        |
+|----------------|---------------|---------------|---------------|--------|------------------|--------|---------------|--------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |        | Power (dBm)      |        | Power (dBm)   |        |
+|                |               |               | Average       | Min    | Average          | Min    | Average       | Min    |
+| I              | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| II             | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| III            | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| IV             | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| V              | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VI             | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VII            | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| VIII           | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| IX             | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+| XIX            | -             | -             | TBD+TT        | TBD+TT | TBD+TT           | TBD+TT | TBD+TT        | TBD+TT |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.1.8 Total Radiated Power (TRP) for UTRA LCR TDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Minimum requirements are not specified in TS 37.144 yet
+- Text for Subclause Procedure, reverberation chamber method
+
+### 6.1.8.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency,  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus,
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus,
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $N$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+### 6.1.8.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.8.2-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.8.2-1: TRP minimum performance requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Power Class 1                              |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|----------------|--------------------------------------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)                                |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average                                    | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| b              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| c              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| d              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| e              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| f              | —                                          | —   | TBD           | TBD | —             | —   | —             | —   |
+| Note:          | Applicable for dual-mode GSM/UTRA LCR TDD. |     |               |     |               |     |               |     |
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.3.2.
+
+### 6.1.8.3 Test purpose
+
+The purpose of this test is to verify that  $\alpha$  and  $\beta$  of the UE is not below specified values. A lower  $\alpha$  and  $\beta$  decrease the coverage area.
+
+### 6.1.8.4 Method of test
+
+#### 6.1.8.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.122 [8] Subclause 5.2. The period of measurement shall be at least one timeslot. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement. Normally, the receiving device should be set accordingly so that the receiving signal will be at least 30dB higher than the system noise floor.
+
+Test environment: normal; see 3GPP TS34.122-1 [8] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+- 1) Set the SS downlink physical channels parameters. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+
+- 4) Enter the UE into loopback test mode and start the loopback test.
+- 5) The measurement receiver shall be set to: zero span, video trigger and RMS detector. The RBW shall be at least  $(1+\alpha)$  times the chip rate of the radio access mode and the VBW at least 3 times bigger than the RBW. For 1.28Mcps TDD UE, the RBW shall be set to 3MHz, and VBW shall be set to 10MHz.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+#### 6.1.8.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE according to the DUT positioning for browsing mode specified in Subclause 4.3.4.
+- 4) Measure the  $EIRP_{\theta}$  and  $EIRP_{\phi}$  with a sample step of  $15^{\circ}$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.1.8.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^{\circ}$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations,  $\theta$ - and  $\phi$  - polarizations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $EIRPstd_i$  is power measurement done with standard setting.  $EIRPnstd_i$  is power measurement done with non standard modulation.  $n$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.1.8.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 6.1.8.5 Test requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than test performance requirements for roaming bands shown in Table 6.1.8.5-1. The averaging shall be done in linear scale for the TRP results of both right and left side hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.8.5-1: TRP test requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band                                   | Power Class 1 |     | Power Class 2 |        | Power Class 3 |     | Power Class 4 |     |
+|--------------------------------------------------|---------------|-----|---------------|--------|---------------|-----|---------------|-----|
+|                                                  | Power (dBm)   |     | Power (dBm)   |        | Power (dBm)   |     | Power (dBm)   |     |
+|                                                  | Average       | Min | Average       | Min    | Average       | Min | Average       | Min |
+| a                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| b                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| c                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| d                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| e                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| f                                                | —             | —   | TBD+TT        | TBD+TT | —             | —   | —             | —   |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |               |     |               |        |               |     |               |     |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.1.9 Total Radiated Power (TRP) for E-UTRA FDD in Browsing Mode with Hand Phantom
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Minimum requirements are not specified in TS 37.144 yet
+- Text for Subclause Procedure, reverberation chamber method
+- Test requirements are to be determined
+
+### 6.1.9.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $G_{\theta}$  to denote either  $G_{\theta}$  or  $G_{\phi}$ , is the  $\theta$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{\text{TX}}$  is the transmit power level of the handset so that  $P_{\text{TX}} G_{\theta}$  is the actually transmitted power-level, also known as EIRP, in the  $\theta$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{\text{TRP}}$  is normalized to the transmitted power  $P_{\text{TX}}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $G_{\theta}$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\phi$  and  $\Delta\theta$  are the sampling intervals for the  $\phi$ - and  $\theta$ -angles, respectively, and the number of samples in the  $\phi$ - and  $\theta$ -angles are given by  $N_\phi$  and  $N_\theta$ , respectively. The sampling points of the sphere are given by  $\phi_i$  and  $\theta_j$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 6.1.9.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.9.2-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.9.2-1: TRP minimum performance requirement for E-UTRA FDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.3.3.
+
+### 6.1.9.3 Test purpose
+
+The purpose of this test is to verify that  $\Delta\phi$  and  $\Delta\theta$  of the UE is not below specified values. A lower  $\Delta\phi$  and  $\Delta\theta$  decrease the coverage area.
+
+### 6.1.9.4 Method of test
+
+#### 6.1.9.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for hand phantom browsing mode specified in Subclause 4.3.4.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-1 for FDD mode.
+
+#### 6.1.9.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Calculate the TRP using the EIRP pattern data as per Subclause 6.1.9.1.
+- 3) Repeat the measurement of the DUT using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.9.2.
+
+#### 6.1.9.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 6.1.9.5 Test requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than test performance requirements for roaming bands shown in Table 6.1.9.5-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in hand phantom browsing mode position shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.1.9.5-1: TRP test requirement for E-UTRA FDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 6.1.10 Total Radiated Power (TRP) for E-UTRA TDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Minimum requirements are not specified in TS 37.144 yet
+- Text for Subclause Procedure, reverberation chamber method
+- Test requirements are to be determined
+
+#### 6.1.10.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $P_{TX}$  to denote either  $P_{TX,H}$  or  $P_{TX,V}$ , is the  $H$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{TX}$  is the transmit power level of the handset so that  $P_{TX}$  is the actually transmitted power-level, also known as EIRP, in the  $H$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{TRP}$  is normalized to the transmitted power  $P_{TX}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $\theta$  and  $\phi$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_\theta$  and  $N_\phi$ , respectively. The sampling points of the sphere are given by  $\theta_i$  and  $\phi_j$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 6.1.10.2 Minimum Requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.10.2-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.10.2-1: TRP minimum performance requirement for E-UTRA TDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.1.3.4.
+
+### 6.1.10.3 Test purpose
+
+The purpose of this test is to verify that  $\text{TRP}_{\text{avg}}$  and  $\text{TRP}_{\text{min}}$  of the UE is not below specified values. A lower  $\text{TRP}_{\text{avg}}$  and decrease the coverage area.
+
+### 6.1.10.4 Method of test
+
+#### 6.1.10.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for hand phantom browsing mode specified in Subclause 4.3.4.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-1 for TDD mode.
+
+#### 6.1.10.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD are set as per Table 8.2.2-1 of 3GPP TS 36.521-1 [11]. Calculate the TRP using the EIRP pattern data as per Subclause 6.1.10.1.
+- 3) Repeat the measurement of the DUT using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.1.10.2.
+
+#### 6.1.10.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 6.1.10.5 Test requirements
+
+The average TRP of low, mid and high channel in hand phantom browsing mode position shall be higher than test performance requirements for roaming bands shown in Table 6.1.10.5-1. The averaging shall be done in linear scale for the TRP results of both right and left hand phantom measurements.
+
+In addition the minimum TRP of each measured channel in beside head position shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.1.10.5-1: TRP test requirement for E-UTRA TDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.2 Performance for LME
+
+### 6.2.1 Total Radiated Power (TRP) for UTRA FDD LME
+
+*Editor's note: This test case is incomplete. The following aspects are either missing or not yet determined:*
+
+- The TRP Minimum Performance Requirement for this test is undefined*
+- The Test Requirements and related Test Tolerances applicable for this test are undefined*
+
+### 6.2.1.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Section 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the LME. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the LME for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna n,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna n and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna n. These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna n and can be calculated using the following expression:
+
+where  $m$  is sample number m of the complex transfer function measured with fixed measurement antenna n and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 11 and later releases that support LME.
+
+NOTE: This test case can be optionally executed for Release 7 and onward UE's supporting LME feature.
+
+### 6.2.1.2 Minimum Requirements
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in Table 6.1.2.2-1. The averaging shall be done in linear scale for the TRP results.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.1.2.2-1: TRP minimum performance requirement for UTRA FDD using LME**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |     | Power Class 3bis |     | Power Class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+
+|                                                                                           |   |   |     |     |     |     |     |     |
+|-------------------------------------------------------------------------------------------|---|---|-----|-----|-----|-----|-----|-----|
+| I                                                                                         | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| II                                                                                        | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| III                                                                                       | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IV                                                                                        | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| V                                                                                         | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VI                                                                                        | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VII                                                                                       | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| VIII                                                                                      | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| IX                                                                                        | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| XIX                                                                                       | - | - | TBD | TBD | TBD | TBD | TBD | TBD |
+| NOTE 1: Applicable for dual-mode GSM/UMTS.<br>NOTE 2: Applicable for USB plug-in devices. |   |   |     |     |     |     |     |     |
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.2.2.
+
+### 6.2.1.3 Test purpose
+
+The purpose of this test is to verify that  $\alpha$  and of the UE is not below specified values. A lower  $\alpha$  and decrease the coverage area.
+
+### 6.2.1.4 Method of test
+
+#### 6.2.1.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see TS 34.121-1 [7] clause 5.2. The period of measurement shall be at least one timeslot. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Test environment: normal; see TS 34.121-1 [7] clause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.2.1.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Connect the plug-in UE to a laptop ground plane phantom. Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 4) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.2.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                      | Power |
+|------------------|----------------------|-------|
+| CPICH            | CPICH_Ec / DPCH_Ec   | 7 dB  |
+| P-CCPCH          | P-CCPCH_Ec / DPCH_Ec | 5 dB  |
+| SCH              | SCH_Ec / DPCH_Ec     | 5 dB  |
+| PICH             | PICH_Ec / DPCH_Ec    | 2 dB  |
+| DPCH             | Test dependent power | -     |
+
+#### 6.2.1.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+
+- 4) Measure the  $P_{iso}$  and  $P_{ref}$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from clause 6.2.1.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Section 4.4). All the EIRP samples are taken with two orthogonal polarizations,  $H$ - and  $V$ -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{ref}$  is power measurement done with standard setting.  $P_{nonstd}$  is power measurement done with non standard modulation.  $P_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.2.1.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+- 4) Measure a sufficient number of independent samples (see section 4.5) of  $P_{iso}$  using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from clause 6.2.1.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE/MS to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+#### 6.2.1.5 Test requirements
+
+The average TRP of low, mid and high channel shall be higher than test performance requirements for roaming bands shown in Table 6.2.1.5-1. The averaging shall be done in linear scale for the TRP.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.2.1.5-1: TRP test requirement for UTRA FDD using LME**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |     | Power Class 3bis |     | Power Class 4 |     |
+|----------------|---------------|---------------|---------------|-----|------------------|-----|---------------|-----|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |     | Power (dBm)      |     | Power (dBm)   |     |
+|                |               |               | Average       | Min | Average          | Min | Average       | Min |
+
+|                                                                                           |   |   |         |            |         |            |         |            |
+|-------------------------------------------------------------------------------------------|---|---|---------|------------|---------|------------|---------|------------|
+| I                                                                                         | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| II                                                                                        | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| III                                                                                       | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| IV                                                                                        | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| V                                                                                         | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| VI                                                                                        | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| VII                                                                                       | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| VIII                                                                                      | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| IX                                                                                        | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| XIX                                                                                       | - | - | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT | TBD +TT | TBD<br>+TT |
+| NOTE 1: Applicable for dual-mode GSM/UMTS.<br>NOTE 2: Applicable for USB plug-in devices. |   |   |         |            |         |            |         |            |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.2.2 Total Radiated Power (TRP) for UTRA LCR TDD LME
+
+Editor’s note: This test case is incomplete. The following aspects are either missing or not yet determined:
+
+- *The TRP Minimum Performance Requirement for this test is undefined*
+- *The Test Requirements and related Test Tolerances applicable for this test are undefined*
+
+### 6.2.2.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency,  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Section 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the LME. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the LME for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna n,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna n, and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna n. These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna n and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $N$  is the total number of samples measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 11 and later releases that support LME.
+
+NOTE: This test case can be optionally executed for Release 8 and onward UE's supporting LME feature.
+
+### 6.2.2.2 Minimum Requirements
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in Table 6.2.2.2-1. The averaging shall be done in linear scale for the TRP results.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.2.2.2-1: TRP minimum performance requirement for UTRA LCR TDD using LME**
+
+| Operating band | Power Class 1 |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| b              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| c              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| d              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| e              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+| f              | —             | —   | TBD           | TBD | —             | —   | —             | —   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.2.3.
+
+### 6.2.2.3 Test purpose
+
+The purpose of this test is to verify that  $\alpha$  and  $\beta$  of the UE is not below specified values. A lower  $\alpha$  and  $\beta$  decrease the coverage area.
+
+### 6.2.2.4 Method of test
+
+#### 6.2.2.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see TS 34.122 [8] clause 5.2. The period of measurement shall be at least one timeslot. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement. Normally, the receiving device should be set accordingly so that the receiving signal will be at least 30 dB higher than the system noise floor.
+
+Test environment: normal; see TS 34.122 [8] clause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see TS 34.122 [8] clause G.2.4.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.2.2.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Connect the plug-in UE to a laptop ground plane phantom. Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 4) Enter the UE into loopback test mode and start the loopback test.
+- 5) The measurement receiver shall be set to: zero span, video trigger and RMS detector. The RBW shall be at least  $(1 + \alpha)$  times the chip rate of the radio access mode and the VBW at least 3 times bigger than the RBW. For 1.28Mcps TDD UE, the RBW shall be set to 3MHz, and VBW shall be set to 10MHz.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.2.2.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                          | Power |
+|------------------|--------------------------|-------|
+| Ior              | -75 dBm                  | -     |
+| DwPCH            | $DwPCH\_Ec / Ior$        | 0 dB  |
+| PCCPCH           | $\sum P-CCPCH\_Ec / Ior$ | -3 dB |
+| SCCPCH           | $\sum S-CCPCH\_Ec / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$    | -6 dB |
+| FPACH            | $FPACH\_Ec / Ior$        | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$    | 0 dB  |
+
+#### 6.2.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+- 4) Measure the  $P_{tot}$  and  $P_{tot,ns}$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from clause 6.2.2.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Section 4.4). All the EIRP samples are taken with two orthogonal polarizations, - and -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{tot}$  is power measurement done with standard setting,  $P_{tot,ns}$  is power measurement done with non standard modulation.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.2.2.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+- 4) Measure a sufficient number of independent samples (see section 4.5) of using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from clause 6.2.2.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE/MS to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+### 6.2.2.5 Test requirements
+
+The average TRP of low, mid and high channel shall be higher than test performance requirements for roaming bands shown in Table 6.2.2.5-1. The averaging shall be done in linear scale for the TRP.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.2.2.5-1: TRP test requirement for UTRA LCR TDD using LME**
+
+| Operating band | Power Class 1 |     | Power Class 2 |          | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|----------|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |          | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min      | Average       | Min | Average       | Min |
+| a              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+| b              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+| c              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+| d              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+| e              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+| f              | —             | —   | TBD + TT      | TBD + TT | —             | —   | —             | —   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 6.2.3 Total Radiated Power (TRP) for E-UTRA FDD LME
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- The requirements are not defined in RAN4 yet
+- Applicability
+- Procedure, reverberation chamber method to be determined
+- Test requirements are to be determined
+
+### 6.2.3.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $\theta$  to denote either  $\theta$  or  $\phi$ , is the  $\theta$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{\text{TX}}$  is the transmit power level of the handset so that  $P_{\text{TX}} G_{\theta}(\Omega)$  is the actually transmitted power-level, also known as EIRP, in the  $\theta$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{\text{TRP}}$  is normalized to the transmitted power  $P_{\text{TX}}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $G_{\theta}(\Omega)$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_{\theta}$  and  $N_{\phi}$ , respectively. The sampling points of the sphere are given by  $\theta_i$  and  $\phi_j$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+[Applicability is TBD]
+
+### 6.2.3.2 Minimum Requirements
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in Table 6.2.3.2-1. The averaging shall be done in linear scale for the TRP results.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.2.3.2-1: TRP minimum performance requirement for E-UTRA FDD using LME**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.2.3.
+
+### 6.2.3.3 Test purpose
+
+The purpose of this test is to verify that  $P_{\text{TRP}}$  and  $P_{\text{EIRP}}$  of the UE is not below specified values. A lower  $P_{\text{TRP}}$  and  $P_{\text{EIRP}}$  decrease the coverage area.
+
+### 6.2.3.4 Method of test
+
+#### 6.2.3.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3. Parameters required for laptop ground plane phantom are specified in Annex A.2.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-1 for FDD mode.
+
+#### 6.2.3.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Calculate the TRP using the EIRP pattern data as per Subclause 6.2.3.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.2.3.2.
+
+...
+
+#### 6.2.3.4.3 Procedure, reverberation chamber method
+
+TBD
+
+### 6.2.3.5 Test requirements
+
+The average TRP of low, mid and high channel shall be higher than test performance requirements for roaming bands shown in Table 6.2.3.5-1. The averaging shall be done in linear scale for the TRP.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.2.3.5-1: TRP test requirement for E-UTRA FDD using LME**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.2.4 Total Radiated Power (TRP) for E-UTRA TDD LME
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- The requirements are not defined in RAN4 yet
+- Applicability
+- Procedure, reverberation chamber method to be determined
+- Test requirements are to be determined
+
+### 6.2.4.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $P_{TX}$  to denote either  $P_{TX,H}$  or  $P_{TX,V}$ , is the  $H$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{TX}$  is the transmit power level of the handset so that  $P_{TX}$  is the actually transmitted power-level, also known as EIRP, in the  $H$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{TRP}$  is normalized to the transmitted power  $P_{TX}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $P_{TX}$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_\theta$  and  $N_\phi$ , respectively. The sampling points of the sphere are given by  $\theta_i$  and  $\phi_j$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+[Applicability is TBD]
+
+### 6.2.4.2 Minimum Requirements
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in Table 6.2.4.2-1. The averaging shall be done in linear scale for the TRP results.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.2.4.2-1: TRP minimum performance requirement for E-UTRA TDD using LME**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.2.4.
+
+### 6.2.4.3 Test purpose
+
+The purpose of this test is to verify that ~~the radiated power samples~~ and of the UE is not below specified values. A lower ~~power level~~ and decrease the coverage area.
+
+### 6.2.4.4 Method of test
+
+#### 6.2.4.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also, care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3. Parameters required for laptop ground plane phantom are specified in Annex A.2.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-1 for TDD mode.
+
+#### 6.2.4.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD are set as per Table 8.2.2-1 of 3GPP TS 36.521-1 [11]. Calculate the TRP using the EIRP pattern data as per Subclause 6.2.4.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.2.4.2.
+
+#### 6.2.4.4.3 Procedure, reverberation chamber method
+
+TBD
+
+### 6.2.4.5 Test requirements
+
+The average TRP of low, mid and high channel shall be higher than test performance requirements for roaming bands shown in Table 6.2.4.5-1. The averaging shall be done in linear scale for the TRP.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns “Min”.
+
+**Table 6.2.4.5-1: TRP test requirement for E-UTRA TDD using LME**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.3 Performance for LEE
+
+### 6.3.1 Total Radiated Power (TRP) for UTRA FDD LEE
+
+Editor's notes: This Subclause is incomplete. The following items are missing or incomplete:
+
+- TBDs in Tables 6.3.1.2-1 and 6.3.1.5-2 as they are not specified in TS 37.144 yet
+
+#### 6.3.1.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency,  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the LEE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the LEE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 11 and later releases that support LEE.
+
+NOTE: This test case can be optionally executed for Release 7 and onward UE's supporting LEE feature.
+
+### 6.3.1.2 Minimum Requirements
+
+The average TRP of low, mid and high channel of the LEE in the data transfers position shall be higher than minimum performance requirements for roaming bands shown in Table 6.3.1.2-1 for notebook devices and in 6.3.1.2-2 for tablet devices. The averaging shall be done in linear scale for the TRP results.
+
+$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$
+
+In addition the minimum TRP of each measured channel in the data transfers position shall be higher than minimum performance requirements shown in the columns "Min".
+
+$$TRP_{min} = \min[P_{low}, P_{mid}, P_{high}]$$
+
+**Table 6.3.1.2-1: TRP minimum performance requirement for UTRA FDD notebook devices in the data transfers position**
+
+| Operating band | Power Class 1<br>Power (dBm) | Power Class 2<br>Power (dBm) | Power Class 3<br>Power (dBm) |      | Power Class 3bis<br>Power (dBm) |     | Power Class 4<br>Power (dBm) |     |
+|----------------|------------------------------|------------------------------|------------------------------|------|---------------------------------|-----|------------------------------|-----|
+|                |                              |                              | Average                      | Min  | Average                         | Min | Average                      | Min |
+| I              | -                            | -                            | 19.0                         | 17.5 | TBD                             | TBD | TBD                          | TBD |
+| II             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| III            | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| IV             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| V              | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| VI             | -                            | -                            | 18.5                         | 16.5 | TBD                             | TBD | TBD                          | TBD |
+| VII            | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| VIII           | -                            | -                            | 18.5                         | 16.5 | TBD                             | TBD | TBD                          | TBD |
+| IX             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| XIX            | -                            | -                            | 18.5                         | 16.5 | TBD                             | TBD | TBD                          | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRP minimum performance requirements in Table 6.3.1.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table 6.3.1.2-2: TRP minimum performance requirement for UTRA FDD tablet devices in the data transfers position**
+
+| Operating band | Power Class 1<br>Power (dBm) | Power Class 2<br>Power (dBm) | Power Class 3<br>Power (dBm) |      | Power Class 3bis<br>Power (dBm) |     | Power Class 4<br>Power (dBm) |     |
+|----------------|------------------------------|------------------------------|------------------------------|------|---------------------------------|-----|------------------------------|-----|
+|                |                              |                              | Average                      | Min  | Average                         | Min | Average                      | Min |
+| I              | -                            | -                            | 19.0                         | 17.5 | TBD                             | TBD | TBD                          | TBD |
+| II             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| III            | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| IV             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| V              | -                            | -                            | 17.0                         | 15.0 | TBD                             | TBD | TBD                          | TBD |
+| VI             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| VII            | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| VIII           | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| IX             | -                            | -                            | TBD                          | TBD  | TBD                             | TBD | TBD                          | TBD |
+| XIX            | -                            | -                            | 17.0                         | 15.0 | TBD                             | TBD | TBD                          | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices with two antennas.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.3.2.
+
+### 6.3.1.3 Test purpose
+
+The purpose of this test is to verify that  $P_{max}$  and  $P_{max} - \Delta P$  of the UE is not below specified values. A lower  $P_{max}$  and decrease the coverage area.
+
+### 6.3.1.4 Method of test
+
+#### 6.3.1.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see 3GPP TS 34.121-1 [7] Subclause 5.2. The period of measurement shall be at least one timeslot. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+The LEE shall be tested according to DUT positioning described in Subclause 4.3.5.
+
+Test environment: normal; see TS34.121-1 [7] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.3.1.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the UE.
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 4) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.3.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                    |
+|------------------|------------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$    |
+| P-CCPCH          | $P\_CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$      |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$     |
+| DPCH             | Test dependent power                     |
+
+#### 6.3.1.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position and configure the LEE according to Subclause 4.3.5.
+- 4) Measure the  $P_{max}$  and  $P_{max} - \Delta P$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.3.1.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations, - and -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{std}$  is power measurement done with standard setting.  $P_{nonstd}$  is power measurement done with non standard modulation.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.3.1.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position and configure the LEE according to Subclause 4.3.5.
+- 4) Measure a sufficient number of independent samples (see Subclause 4.5) of  $P_{std}$  using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.3.1.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+#### 6.3.1.5 Test requirements
+
+The average TRP of low, mid and high channel in the data transfers position shall be higher than test performance requirements for roaming bands shown in Table 6.3.1.5-1 for notebook devices and in Table 6.3.1.5-2 for tablet devices. The averaging shall be done in linear scale for the TRP results.
+
+$$TRP_{average} = 10 \log \left[ \frac{10^{P_{low}/10} + 10^{P_{mid}/10} + 10^{P_{high}/10}}{3} \right]$$
+
+In addition the minimum TRP of each measured channel in the data transfers position shall be higher than minimum performance requirements shown in the columns "Min".
+
+$$TRP_{min} = \min[P_{low}, P_{mid}, P_{high}]$$
+
+**Table 6.3.1.5-1: TRP test requirement for UTRA FDD notebook devices in the data transfers position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |             | Power Class 3bis |            | Power Class 4 |            |
+|----------------|---------------|---------------|---------------|-------------|------------------|------------|---------------|------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |             | Power (dBm)      |            | Power (dBm)   |            |
+|                |               |               | Average       | Min         | Average          | Min        | Average       | Min        |
+| I              | -             | -             | 18.3          | 16.5        | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| II             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| III            | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| IV             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| V              | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VI             | -             | -             | 17.8          | 15.5        | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VII            | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VIII           | -             | -             | 17.8          | 15.5        | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| IX             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| XIX            | -             | -             | 18.5+TT       | 16.5+T<br>T | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for notebook devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 6.3.1.5-2: TRP test requirement for UTRA FDD tablet devices in the data transfers position**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |             | Power Class 3bis |            | Power Class 4 |            |
+|----------------|---------------|---------------|---------------|-------------|------------------|------------|---------------|------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |             | Power (dBm)      |            | Power (dBm)   |            |
+|                |               |               | Average       | Min         | Average          | Min        | Average       | Min        |
+| I              | -             | -             | 18.3          | 16.5        | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| II             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| III            | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| IV             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| V              | -             | -             | 16.3          | 14.0        | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VI             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VII            | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| VIII           | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| IX             | -             | -             | TBD+TT        | TBD+T<br>T  | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+| XIX            | -             | -             | 17.0+TT       | 15.0+T<br>T | TBD+TT           | TBD+T<br>T | TBD+TT        | TBD+T<br>T |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for tablet devices with two antennas.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.3.2 Total Radiated Power (TRP) for UTRA LCR TDD LEE
+
+Editor's notes: This Subclause is incomplete. The following items are missing or incomplete:
+
+- TBDs in Tables 6.3.2.2-1 and 6.3.2.5-2 as they are not specified in TS 37.144 yet
+
+### 6.3.2.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the DUT actually radiates. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Where  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{\theta}$  and  $P_{\phi}$  are the orthogonal polarizations, and  $P_{\theta}$  and  $P_{\phi}$  are the actually transmitted power-levels in corresponding polarizations.
+
+Thus
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the LEE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the LEE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 11 and later releases that support LEE.
+
+Note: This test case can be optionally executed for Release 8 and onward UE's supporting LEE feature.
+
+### 6.3.2.2 Minimum Requirements
+
+The average TRP of low, mid and high channel shall be higher than minimum performance requirements for roaming bands shown in Table 6.3.2.2-1 for notebook devices and in Table 6.3.2.2-2 for tablet devices. The averaging shall be done in linear scale for the TRP results.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.3.2.2-1: TRP minimum performance requirement for UTRA TDD notebook devices in the data transfers position**
+
+| Operating band | Power Class 1 |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+**Table 6.3.2.2-2: TRP minimum performance requirement for UTRA TDD tablet devices in the data transfers position**
+
+| Operating band | Power Class 1 |     | Power Class 2 |     | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|-----|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| b              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| c              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| d              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| e              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+| f              | -             | -   | TBD           | TBD | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.3.3.
+
+### 6.3.2.3 Test purpose
+
+The purpose of this test is to verify that and of the UE is not below specified values. A lower and decrease the coverage area.
+
+### 6.3.2.4 Method of test
+
+#### 6.3.2.4.1 Initial conditions
+
+The output power is a measure of the maximum power the UE can transmit in a bandwidth of at least  $(1 + \alpha)$  times the chip rate of the radio access mode, for more information see TS 34.122 [8] Subclause 5.2. The period of measurement shall be at least one timeslot. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement. Normally, the receiving device should be set accordingly so that the receiving signal will be at least 30 dB higher than the system noise floor.
+
+The LEE shall be tested according to DUT positioning described in Subclause 4.3.5.
+
+Test environment: normal; see TS 34.122 [8] Subclause G.2.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+- 1) Set the SS downlink physical channels according to settings in Table 6.3.2.4.1-1. Set the DPCH power such that there will not be transmission gaps due to too low signal strength throughout the measurement.
+- 2) Power on the LEE UE
+- 3) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+
+- 4) Enter the UE into loopback test mode and start the loopback test.
+- 5) The measurement receiver shall be set to: zero span, video trigger and RMS detector. The RBW shall be at least  $(1 + \alpha)$  times the chip rate of the radio access mode and the VBW at least 3 times bigger than the RBW. For 1.28Mcps TDD UE, the RBW shall be set to 3MHz, and VBW shall be set to 10MHz.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.3.2.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                         | Power |
+|------------------|-------------------------|-------|
+| Ior              | -75 dBm                 | -     |
+| DwPCH            | DwPCH_Ec / Ior          | 0 dB  |
+| PCCPCH           | $\sum$ P-CCPCH_Ec / Ior | -3 dB |
+| SCCPCH           | $\sum$ S-CCPCH_Ec / Ior | -6 dB |
+| PICH             | $\sum$ PICH_Ec / Ior    | -6 dB |
+| FPACH            | FPACH_Ec / Ior          | -6 dB |
+| DL DPCH          | $\sum$ DPCH_Ec / Ior    | 0 dB  |
+
+#### 6.3.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the LEE UE.
+- 2) As the LEE UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position and configure the LEE according to Subclause 4.3.5.
+- 4) Measure the  $P_{ref}$  and  $P_{non}$  with a sample step of  $15^\circ$  in theta ( $\theta$ ) and phi ( $\phi$ ) directions using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.3.2.2.
+
+NOTE 1: The measurement procedure is based on the measurement of the spherical radiation pattern of the DUT. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIRP samples are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. In some cases a different sampling grid may be used to speed up the measurements (See Subclause 4.4). All the EIRP samples are taken with two orthogonal polarizations, - and -polarisations.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+NOTE 3: Non Standard settings: To speed up sensitivity measurements, power measurements may be done with non standard modulation. However to obtain TRP result the measured EIRP figures shall be normalized by
+
+where  $P_{ref}$  is power measurement done with standard setting.  $P_{non}$  is power measurement done with non standard modulation.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRP, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+#### 6.3.2.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the LEE UE.
+- 2) As the LEE UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position and configure the LEE according to Subclause 4.3.5.
+- 4) Measure a sufficient number of independent samples (see Subclause 4.5) of  $P_{ref}$  using a test system having characteristics as described in Annex A.
+- 5) Calculate TRP using equations from Subclause 6.3.2.1.
+
+NOTE 1: The measurement procedure is based on the measurement of the total power radiated from the UE to a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power transmitted by the DUT is undergoing Rayleigh fading and is sampled by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRP value.
+
+NOTE 2: The noise floor of the measurement receiver shall not disturb the power measurement.
+
+### 6.3.2.5 Test requirements
+
+The average TRP of low, mid and high channel shall be higher than test performance requirements for roaming bands shown in Table 6.3.2.5-1 for notebook devices and in Table 6.3.2.5-2 for tablet devices. The averaging shall be done in linear scale for the TRP.
+
+In addition the minimum TRP of each measured channel shall be higher than minimum performance requirements shown in the columns "Min".
+
+**Table 6.3.2.5-1: TRP test requirement for UTRA TDD notebook devices in the data transfers position**
+
+| Operating band | Power Class 1 |     | Power Class 2 |         | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|---------|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |         | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min     | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+| b              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+| c              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+| d              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+| e              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+| f              | -             | -   | TBD +TT       | TBD +TT | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 6.3.2.5-2: TRP test requirement for UTRA TDD tablet devices in the data transfers position**
+
+| Operating band | Power Class 1 |     | Power Class 2 |            | Power Class 3 |     | Power Class 4 |     |
+|----------------|---------------|-----|---------------|------------|---------------|-----|---------------|-----|
+|                | Power (dBm)   |     | Power (dBm)   |            | Power (dBm)   |     | Power (dBm)   |     |
+|                | Average       | Min | Average       | Min        | Average       | Min | Average       | Min |
+| a              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+| b              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+| c              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+| d              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+| e              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+| f              | -             | -   | TBD +TT       | TBD<br>+TT | -             | -   | -             | -   |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+ NOTE 2: Applicable for tablet devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 6.3.3 Total Radiated Power (TRP) for E-UTRA FDD LEE
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 6.3.3.2-1 and 6.3.3.5-1 as they are not specified in TS 37.144 yet
+- Applicability
+
+#### 6.3.3.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using   to denote either   or   ,   is the   -polarization component of the gain pattern for the handset antenna measured at the frequency   , where   is the solid angle describing the direction.   is the transmit power level of the handset so that   is the actually transmitted power-level, also known as EIRP, in the   -polarization and in the direction   for frequency   .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{TRP}$  is normalized to the transmitted power   . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of   are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation   :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the sampling intervals for the  $\theta$ - and  $\phi$ -angles, respectively, and the number of samples in the  $\theta$ - and  $\phi$ -angles are given by  $N_\theta$  and  $N_\phi$ , respectively. The sampling points of the sphere are given by  $\theta_m$  and  $\phi_n$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{avg,n}$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $m$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+### 6.3.3.2 Minimum Requirements
+
+The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in Table 6.3.3.2-1 for notebook devices and in Table 6.3.3.2-2 for tablet devices. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in the column “Min” on the requirement tables.
+
+**Table 6.3.3.2-1: TRP minimum performance requirement for E-UTRA FDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+**Table 6.3.3.2-2: TRP minimum performance requirement for E-UTRA FDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Power Class 1 | Power Class 2 | Power Class 3 |      | Power Class 4 |
+|----------------|---------------|---------------|---------------|------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)   |
+|                |               |               | Average       | Min  |               |
+| 1              |               |               | 18.5          | 17.0 |               |
+| 2              |               |               |               |      |               |
+| 3              |               |               | 18.5          | 17.0 |               |
+| 4              |               |               |               |      |               |
+| 5              |               |               |               |      |               |
+| 7              |               |               | 18.0          | 16.5 |               |
+| 8              |               |               |               |      |               |
+| 12             |               |               |               |      |               |
+| 13             |               |               |               |      |               |
+| 19             |               |               | 17.5          | 15.5 |               |
+| 20             |               |               | 17.5          | 15.5 |               |
+| 21             |               |               | 17.5          | 16.0 |               |
+| 28             |               |               |               |      |               |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.3.4.
+
+### 6.3.3.3 Test purpose
+
+The purpose of this test is to verify that and of the UE is not below specified values. A lower and decrease the coverage area.
+
+### 6.3.3.4 Method of test
+
+#### 6.3.3.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-1 for FDD mode.
+
+#### 6.3.3.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Calculate the TRP using the EIRP pattern data as per Subclause 6.3.3.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.3.3.2.
+
+#### 6.3.3.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) Measure a sufficient number of independent samples (see Subclause 4.5) of using a test system having characteristics as described in Annex A. Calculate TRP using equations from Subclause 6.3.3.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.3.3.2.
+
+#### 6.3.3.5 Test requirements
+
+The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in Table 6.3.3.5-1 for notebook devices and in Table 6.3.3.5-2 for tablet devices. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in the column “Min” on the requirement tables.
+
+**Table 6.3.3.5-1: TRP test requirement for E-UTRA FDD roaming bands for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 6.3.3.5-2: TRP test requirement for E-UTRA FDD roaming bands for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band                                                                                                                                                                         | Power Class 1 | Power Class 2 | Power Class 3 |      | Power Class 4 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------|------|---------------|
+|                                                                                                                                                                                        | Power (dBm)   | Power (dBm)   | Power (dBm)   |      | Power (dBm)   |
+|                                                                                                                                                                                        |               |               | Average       | Min  |               |
+| 1                                                                                                                                                                                      |               |               | 17.8          | 16.0 |               |
+| 2                                                                                                                                                                                      |               |               |               |      |               |
+| 3                                                                                                                                                                                      |               |               | 17.8          | 16.0 |               |
+| 4                                                                                                                                                                                      |               |               |               |      |               |
+| 5                                                                                                                                                                                      |               |               |               |      |               |
+| 7                                                                                                                                                                                      |               |               | 17.3          | 15.5 |               |
+| 8                                                                                                                                                                                      |               |               |               |      |               |
+| 12                                                                                                                                                                                     |               |               |               |      |               |
+| 13                                                                                                                                                                                     |               |               |               |      |               |
+| 19                                                                                                                                                                                     |               |               | 16.8          | 14.5 |               |
+| 20                                                                                                                                                                                     |               |               | 16.8          | 14.5 |               |
+| 21                                                                                                                                                                                     |               |               | 16.8          | 15.0 |               |
+| 28                                                                                                                                                                                     |               |               |               |      |               |
+| NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.<br>NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS. |               |               |               |      |               |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 6.3.4 Total Radiated Power (TRP) for E-UTRA TDD LEE
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 6.3.4.2-1 and 6.3.4.5-1 as they are not specified in TS 37.144 yet
+- Applicability
+
+### 6.3.4.1 Definition and applicability
+
+The Total Radiated Power (TRP) is a measure of how much power the antenna actually radiates, when non-idealities such as mismatch and losses in the antenna are taken into account. The TRP is defined as the integral of the power transmitted in different directions over the entire radiation sphere:
+
+Using  $\theta$  to denote either  $\theta$  or  $\phi$ , is the  $\theta$ -polarization component of the gain pattern for the handset antenna measured at the frequency  $f$ , where  $\Omega$  is the solid angle describing the direction.  $P_{TX}$  is the transmit power level of the handset so that  $P_{TX} \cdot G_{\theta}(\Omega)$  is the actually transmitted power-level, also known as EIRP, in the  $\theta$ -polarization and in the direction  $\Omega$  for frequency  $f$ .
+
+The above equation may be written in "gain" form, that is, the TRP given by  $P_{TRP}$  is normalized to the transmitted power  $P_{TX}$ . This is the total radiation efficiency, which can also be denoted as Total Radiated Power Gain, TRPG,
+
+In practice discrete samples of  $G_{\theta}(\Omega)$  are measured and used to approximate the integral so that the TRP is computed as
+
+Or, by using the relation :
+
+In gain form the TRP can be expressed as:
+
+In these formulas  $\Delta\phi$  and  $\Delta\theta$  are the sampling intervals for the  $\phi$ - and  $\theta$ -angles, respectively, and the number of samples in the  $\phi$ - and  $\theta$ -angles are given by  $N_\phi$  and  $N_\theta$ , respectively. The sampling points of the sphere are given by  $\phi_m$  and  $\theta_n$ . The sampling intervals are discussed further in Section 4.4.
+
+When measuring power radiated by active devices, expressing the data in terms of EIRP is more appropriate. The upper form of the TRP formulas (which includes EIRP terms) will be used in the data processing.
+
+The TRP can also be calculated from Rayleigh faded samples of the total power transmitted from the UE. The measurement of transmitter performance in an isotropic Rayleigh fading environment is based on sampling the radiated power of the UE for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the TRP and by calibrating the average power transfer function, an absolute value of the TRP can be obtained. Thus
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\bar{P}_n$  is the average power measured by fixed measurement antenna  $n$  and can be calculated using the following expression:
+
+where  $P_{m,n}$  is sample number  $m$  of the complex transfer function measured with fixed measurement antenna  $n$  and  $M$  is the total number of samples measured for each fixed measurement antenna.
+
+Note that all averaging must be performed using linear power values (e.g. measurements in Watts).
+
+[Applicability is TBD]
+
+### 6.3.4.2 Minimum Requirements
+
+The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in Table 6.3.4.2-1 for notebook devices and in Table 6.3.4.2-2 for tablet devices. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in the column “Min” on the requirement tables.
+
+**Table 6.3.4.2-1: TRP minimum performance requirement for E-UTRA TDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+**Table 6.3.4.2-2: TRP minimum performance requirement for E-UTRA TDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS37.144 [12] Subclause 6.3.5.
+
+### 6.3.4.3 Test purpose
+
+The purpose of this test is to verify that  $\bar{P}_n$  and  $P_{min,n}$  of the UE is not below specified values. A lower  $\bar{P}_n$  and  $P_{min,n}$  decrease the coverage area.
+
+### 6.3.4.4 Method of test
+
+#### 6.3.4.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+The maximum output power for different UE power classes are defined in 3GPP TS 36.521-1 [11] Subclause 6.2.2 for any transmission bandwidth within the channel bandwidth. Also care should be taken that the noise floor of the measurement receiver is not disturbing the power measurement.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-1.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 6.2.2 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-1 for TDD mode.
+
+#### 6.3.4.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern following the sampling grid specified in Subclause 4.4. Slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD are set as per Table 8.2.2-1 of 3GPP TS 36.521-1 [11]. Calculate the TRP using the EIRP pattern data as per Subclause 6.3.4.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.3.4.2.
+
+#### 6.3.4.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 [11] and ensure that the DUT transmits with its maximum power.
+- 2) Measure a sufficient number of independent samples (see Subclause 4.5) of using a test system having characteristics as described in Annex A. Calculate TRP using equations from Subclause 6.3.4.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRP as per Subclause 6.3.4.2.
+
+### 6.3.4.5 Test requirements
+
+The average measured TRP of low, mid and high channel for laptop embedded equipment shall be higher than the average TRP requirement specified in Table 6.3.4.5-1 for notebook devices and in Table 6.3.5.5-2 for tablet devices. The averaging shall be done in linear scale for the TRP results. Average TRP requirement is shown in the column “Average” on the requirement tables.
+
+In addition the lowest TRP of each measured channel shall be higher than minimum TRP requirement specified in the column “Min” on the requirement tables.
+
+**Table 6.3.4.5-1: TRP test requirement for E-UTRA TDD roaming bands for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 6.3.4.5-2: TRP test requirement for E-UTRA TDD roaming bands for tablet devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+---
+
+## 7 Receiver Performance
+
+### 7.1 Performance for handheld UE
+
+#### 7.1.1 Total Radiated Sensitivity (TRS) for UTRA FDD in Speech Mode with beside the Head Phantom
+
+Editor's notes: This subclause is incomplete. The following item is missing or incomplete:
+
+- Text for Subclause 7.1.1.4.3 Procedure, reverberation chamber method
+
+##### 7.1.1.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $\Delta\theta$  and  $\Delta\phi$  are the number of sampling intervals for theta and phi.  $\theta$  and  $\phi$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+##### 7.1.1.2 Minimum requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.1.2-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the maximum TRS of each measured channel in beside head position shall be better than minimum performance requirements for roaming bands shown in the columns “Max” on the requirement tables.
+
+**Table 7.1.1.2-1: TRS minimum requirements for UTRA FDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating band | Unit         | <REFI <sub>or</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| I              | dBm/3.84 MHz | -101                  | -98 |
+| II             | dBm/3.84 MHz | -99                   | -96 |
+| III            | dBm/3.84 MHz | -98                   | -95 |
+| IV             | dBm/3.84 MHz | -101                  | -98 |
+| V              | dBm/3.84 MHz | -96                   | -93 |
+| VI             | dBm/3.84 MHz | -96                   | -93 |
+| VII            | dBm/3.84 MHz | -99                   | -96 |
+| VIII           | dBm/3.84 MHz | -96                   | -93 |
+| IX             | dBm/3.84 MHz | -100                  | -97 |
+| XIX            | dBm/3.84 MHz | -96                   | -93 |
+
+NOTE 1: For Power class 3, 3bis and 4 this shall be achieved at the maximum output power.
+
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REFI<sub>or</sub>> [average and min] shall apply for Band IX.
+
+NOTE 3: Applicable for dual-mode GSM/UMTS.
+
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REFI<sub>or</sub>> level of -98 dBm/3.84 MHz and max <REFI<sub>or</sub>> level of -95 dBm/3.84 MHz shall apply for Band II.
+
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REFI<sub>or</sub>> level of -100 dBm/3.84 MHz and max <REFI<sub>or</sub>> level of -97 dBm/3.84 MHz shall apply for Band IV.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.1.2.
+
+### 7.1.1.3 Test Purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.1.4 Method of test
+
+#### 7.1.1.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1.
+
+Test environment: normal; see TS 36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.1.4.1-1.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                    |
+|------------------|------------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$    |
+| P-CCPCH          | $P\_CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$      |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$     |
+| DPCH             | Test dependent power                     |
+
+#### 7.1.1.4.2 Test procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the UE against the SAM phantom
+- 4) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 6) Calculate TRS using equations from chapter 7.1.1.1
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $EIS_{std}$  is sensitivity measurement done with standard setting.  $EIS_{non\_std}$  is sensitivity measurement done with non standard settings.  $N_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.1.2.
+
+#### 7.1.1.4.3 Test procedure, reverberation chamber method
+
+TBD
+
+#### 7.1.1.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.1.5-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.1.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+**Table 7.1.1.5-1: TRS test requirements for UTRA FDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>10</sub> > |        |
+|----------------|--------------|----------------------|--------|
+|                |              | Average              | Max    |
+| I              | dBm/3.84 MHz | -100.1               | -96.8  |
+| II             | dBm/3.84 MHz | -98.1                | -94.8  |
+| III            | dBm/3.84 MHz | -97.1                | -93.8  |
+| IV             | dBm/3.84 MHz | -100.1               | -96.8  |
+| V              | dBm/3.84 MHz | -95.1                | -91.8  |
+| VI             | dBm/3.84 MHz | -95.1                | -91.8  |
+| VII            | dBm/3.84 MHz | -98.1                | -94.8  |
+| VIII           | dBm/3.84 MHz | -95.1                | -91.8  |
+| IX             | dBm/3.84 MHz | -99.1                | -95.8  |
+| XIX            | dBm/3.84 MHz | -96+TT               | -93+TT |
+
+NOTE 1: For Power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF<sub>10</sub>> [average and min] shall apply for Band IX.  
+NOTE 3: Applicable for dual-mode GSM/UMTS.  
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>10</sub>> level of -97.1 dBm/3.84 MHz and max <REF<sub>10</sub>> level of -93.8 dBm/3.84 MHz shall apply for Band II.  
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>10</sub>> level of -99.1 dBm/3.84 MHz and max <REF<sub>10</sub>> level of -95.8 dBm/3.84 MHz shall apply for Band IV.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+## 7.1.2 Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Speech Mode with beside the Head Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.2.2-1 and 7.1.2.5-1 as they are not completed in TS 37.144 yet
+- Text for Subclause 7.1.2.4.3 Procedure, reverberation chamber method
+
+### 7.1.2.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+### 7.1.2.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.2.2-1. The averaging shall be done in linear scale for the TRS results
+
+of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.2.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.1.2.2-1: TRS minimum requirements for UTRA LCR TDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating Band | Unit         | <REF <sub>or</sub> > |      |
+|----------------|--------------|----------------------|------|
+|                |              | Average              | Max  |
+| a              | dBm/1.28 MHz | -101                 | -100 |
+| b              | dBm/1.28 MHz | TBD                  | TBD  |
+| c              | dBm/1.28 MHz | TBD                  | TBD  |
+| d              | dBm/1.28 MHz | TBD                  | TBD  |
+| e              | dBm/1.28 MHz | -101                 | -100 |
+| f              | dBm/1.28 MHz | -101                 | -100 |
+
+NOTE Applicable for dual-mode GSM/UTRA LCR TDD.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.1.3.
+
+### 7.1.2.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.2.4 Method of test
+
+#### 7.1.2.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.2.4.1-1. The DL power level should be set to ensure 0% BER at 12.2kbps data rate at the whole 3D initial scan.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 5) Enter the UE into loopback test mode and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] and Annex C of TS 34.122 [8] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.2.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                                 | Power |
+|------------------|---------------------------------|-------|
+| Ior              | -75 dBm                         | -     |
+| DwPCH            | DwPCH_Ec / Ior                  | 0 dB  |
+| PCCPCH           | $\sum P\text{-CCPCH\_Ec} / Ior$ | -3 dB |
+| SCCPCH           | $\sum S\text{-CCPCH\_Ec} / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$           | -6 dB |
+| FPACH            | FPACH_Ec / Ior                  | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$           | 0 dB  |
+
+#### 7.1.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 40000 or more bits; see Annex E.20. The DL power step size shall be no bigger than 0.5dB when the RF level is near the TDD UE sensitivity level.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.1.2.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting,  $S_{non}$  is sensitivity measurement done with non standard settings.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.2.2.
+
+#### 7.1.2.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 7.1.2.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.2.5-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.2.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.2.5-1: TRS minimum requirement for UTRA LCR TDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating Band                                     | Unit         | <REFÎ <sub>or</sub> > |          |
+|----------------------------------------------------|--------------|-----------------------|----------|
+|                                                    |              | Average               | Max      |
+| a                                                  | dBm/1.28 MHz | -100.1                | -98.8    |
+| b                                                  | dBm/1.28 MHz | TBD + TT              | TBD + TT |
+| c                                                  | dBm/1.28 MHz | TBD + TT              | TBD + TT |
+| d                                                  | dBm/1.28 MHz | TBD + TT              | TBD + TT |
+| e                                                  | dBm/1.28 MHz | -100.1                | -98.8    |
+| f                                                  | dBm/1.28 MHz | -100.1                | -98.8    |
+| NOTE    Applicable for dual-mode GSM/UTRA LCR TDD. |              |                       |          |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+### 7.1.3 Total Radiated Sensitivity (TRS) for UTRA FDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.3.2-1 and 7.1.3.5-1 as they are not specified in TS 37.144 yet
+
+#### 7.1.3.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna n,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna n and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna n. These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{ref,n}$  is calculated by using the following equation:
+
+where  $P_{m,n}$  is the m:th value of the transfer function for fixed measurement antenna n, which gives the BER threshold.  $M_n$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+#### 7.1.3.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.3.2-1. The averaging shall be done in linear scale for the TRS results
+
+of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.3.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.1.3.2-1: TRS minimum requirements for UTRA FDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| I              | dBm/3.84 MHz | -101.10               | TBD |
+| II             | dBm/3.84 MHz | -99.0                 | TBD |
+| III            | dBm/3.84 MHz | TBD                   | TBD |
+| IV             | dBm/3.84 MHz | TBD                   | TBD |
+| V              | dBm/3.84 MHz | -96.75                | TBD |
+| VI             | dBm/3.84 MHz | -96.75                | TBD |
+| VII            | dBm/3.84 MHz | TBD                   | TBD |
+| VIII           | dBm/3.84 MHz | -96.75                | TBD |
+| IX             | dBm/3.84 MHz | TBD                   | TBD |
+| XIX            | dBm/3.84 MHz | -96.75                | TBD |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.
+
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF<sub>ior</sub>> [average and min] shall apply for Band IX.
+
+NOTE 3: Applicable for dual-mode GSM/UMTS.
+
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -98 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -95 dBm/3.84 MHz shall apply for Band II.
+
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -100 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -97 dBm/3.84 MHz shall apply for Band IV.
+
+NOTE 6: Applicable for devices narrower than 72mm as defined in TR 25.914.
+
+NOTE 7: Not applicable for devices supporting CDMA or carrier aggregation.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.2.1.
+
+### 7.1.3.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.3.4 Method of test
+
+#### 7.1.3.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.3.4.1-1.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.3.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                    |
+|------------------|------------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$    |
+| P-CCPCH          | $P\_CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$      |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$     |
+| DPCH             | Test dependent power                     |
+
+#### 7.1.3.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 20000 or more bits; see Annex E.20.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.1.3.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{ref}$  is sensitivity measurement done with standard setting,  $S_{non}$  is sensitivity measurement done with non standard settings.  $N_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.3.2.
+
+#### 7.1.3.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Set the base station simulator to a specific output power and perform a BER measurement.
+
+- 4) Increase or decrease the base station output power as needed, and repeat step 4 until the lowest output power is found that gives a BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20. This corresponds to .
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Repeat step 3 and 4 until a sufficient number of independent samples (see section 4.5) of has been measured.
+- 7) Calculate TRS using equations from chapter 7.1.3.1.
+
+NOTE 1: The measurement procedure is based on samples of the received signal power at the UE/MS from a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power received by the DUT is undergoing Rayleigh fading and is transmitted by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRS value.
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.3.2.
+
+### 7.1.3.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.3.5-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.3.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.3.5-1: TRS minimum requirement for UTRA FDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band                                                                                                                                                                                           | Unit         | <REFI <sub>or</sub> > |        |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------|--------|
+|                                                                                                                                                                                                          |              | Average               | Max    |
+| I                                                                                                                                                                                                        | dBm/3.84 MHz | -100.1                | TBD+TT |
+| II                                                                                                                                                                                                       | dBm/3.84 MHz | -98.1                 | TBD+TT |
+| III                                                                                                                                                                                                      | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| IV                                                                                                                                                                                                       | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| V                                                                                                                                                                                                        | dBm/3.84 MHz | -95.85                | TBD+TT |
+| VI                                                                                                                                                                                                       | dBm/3.84 MHz | -95.85                | TBD+TT |
+| VII                                                                                                                                                                                                      | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| VIII                                                                                                                                                                                                     | dBm/3.84 MHz | -95.85                | TBD+TT |
+| IX                                                                                                                                                                                                       | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| XIX                                                                                                                                                                                                      | dBm/3.84 MHz | -95.85                | TBD+TT |
+| NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.                                                                                                                |              |                       |        |
+| NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REFI <sub>or</sub> > [average and min] shall apply for Band IX.                   |              |                       |        |
+| NOTE 3: Applicable for dual-mode GSM/UMTS.                                                                                                                                                               |              |                       |        |
+| NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REFI <sub>or</sub> > level of -98 dBm/3.84 MHz and max <REFI <sub>or</sub> > level of -95 dBm/3.84 MHz shall apply for Band II.  |              |                       |        |
+| NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REFI <sub>or</sub> > level of -100 dBm/3.84 MHz and max <REFI <sub>or</sub> > level of -97 dBm/3.84 MHz shall apply for Band IV. |              |                       |        |
+| NOTE 6: Applicable for devices narrower than 72mm as defined in TR 25.914.                                                                                                                               |              |                       |        |
+| NOTE 7: Not applicable for devices supporting CDMA or carrier aggregation.                                                                                                                               |              |                       |        |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.4 Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.4.2-1 and 7.1.5.4-1 as they are not specified in TS 37.144 yet
+
+### 7.1.4.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{ref,n}$  is calculated by using the following equation:
+
+where  $P_{m,n}$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $M_n$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+### 7.1.4.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.4.2-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.5.2-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.4.2-1: TRS minimum requirements for UTRA LCR TDD roaming bands in the speech position for the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REFÎor> |     |
+|--------------------------------------------------|--------------|----------|-----|
+|                                                  |              | Average  | Max |
+| a                                                | dBm/1.28 MHz | TBD      | TBD |
+| b                                                | dBm/1.28 MHz | TBD      | TBD |
+| c                                                | dBm/1.28 MHz | TBD      | TBD |
+| d                                                | dBm/1.28 MHz | TBD      | TBD |
+| e                                                | dBm/1.28 MHz | TBD      | TBD |
+| f                                                | dBm/1.28 MHz | TBD      | TBD |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |          |     |
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.2.2.
+
+### 7.1.4.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.5.4 Method of test
+
+#### 7.1.4.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.4.4.1-1. The DL power level should be set to ensure 0% BER at 12.2kbps data rate at the whole 3D initial scan.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 5) Enter the UE into loopback test mode and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] and Annex C of TS 34.122 [8] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.4.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                                 | Power |
+|------------------|---------------------------------|-------|
+| Ior              | -75 dBm                         |       |
+| DwPCH            | DwPCH_Ec / Ior                  | 0 dB  |
+| PCCPCH           | $\sum P\text{-CCPCH\_Ec} / Ior$ | -3 dB |
+| SCCPCH           | $\sum S\text{-CCPCH\_Ec} / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$           | -6 dB |
+| FPACH            | FPACH_Ec / Ior                  | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$           | 0 dB  |
+
+#### 7.1.4.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 40000 or more bits; see Annex E.20. The DL power step size shall be no bigger than 0.5dB when the RF level is near the TDD UE sensitivity level.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.1.4.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting,  $S_{non}$  is sensitivity measurement done with non standard settings.  $S_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations,  $\theta$ - and  $\phi$ -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.5.2.
+
+#### 7.1.4.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Set the base station simulator to a specific output power and perform a BER measurement.
+- 4) Increase or decrease the base station output power as needed, and repeat step 4 until the lowest output power is found that gives a BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20. This corresponds to  $S_{min}$ .
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Repeat step 3 and 4 until a sufficient number of independent samples (see section 4.5) of  $S_{min}$  has been measured.
+- 7) Calculate TRS using equations from chapter 7.1.4.1.
+
+NOTE 1: The measurement procedure is based on samples of the received signal power at the UE/MS from a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power received by the DUT is undergoing Rayleigh fading and is transmitted by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRS value.
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.4.2.
+
+#### 7.1.4.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.4.5-1. The averaging shall be done in linear scale for the TRS results
+
+of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.4.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.4.5-1: TRS minimum requirement for UTRA LCR TDD roaming bands in the speech position and the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REFior> |        |
+|--------------------------------------------------|--------------|----------|--------|
+|                                                  |              | Average  | Max    |
+| a                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| b                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| c                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| d                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| e                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| f                                                | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |          |        |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.5 Total Radiated Sensitivity (TRS) for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.5.2-1 and 7.1.5.5-1 as they are not specified in TS 37.144 yet
+
+### 7.1.5.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $G_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $\Gamma_n$  is calculated by using the following equation:
+
+where  $m$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $N$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 7.1.5.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.5.2-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.5.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.5.2-1: TRS minimum requirements for E-UTRA FDD roaming bands in the speech position for the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.2.3.
+
+### 7.1.5.3 Test purpose
+
+The purpose of this test is to ensure that  $TRS_{\text{avg}}$  and  $TRS_{\max}$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.5.4 Method of test
+
+#### 7.1.5.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-2 for FDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.1.5.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.1.5.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.5.2.
+
+#### 7.1.5.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) Repeat Step 1) until a sufficient number of independent samples (see section 4.5) of has been measured. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each sample shall be recorded for calculating the TRS according to Subclause 7.1.5.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.5.2.
+
+#### 7.1.5.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.5.5-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.5.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.5.5-1: TRS minimum requirement for E-UTRA FDD roaming bands in the speech position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 7.1.6 Total Radiated Sensitivity (TRS) for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.6.2-1 and 7.1.6.5-1 as they are not specified in TS 37.144 yet
+
+### 7.1.6.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\alpha$  and  $\beta$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{ref,n}$  is calculated by using the following equation:
+
+where  $P_{ref,n,m}$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $M$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 7.1.6.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.6.2-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.6.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.6.2-1: TRS minimum requirements for E-UTRA TDD roaming bands in the speech position for the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.2.4.
+
+### 7.1.6.3 Test purpose
+
+The purpose of this test is to ensure that  $\Gamma$  and  $L$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+## 7.1.6.4 Method of test
+
+### 7.1.6.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.1 and A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.3.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-2 for TDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+### 7.1.6.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.1.6.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.6.2.
+
+### 7.1.6.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) Repeat Step 1) until a sufficient number of independent samples (see section 4.5) of has been measured. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each sample shall be recorded for calculating the TRS according to Subclause 7.1.6.1.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.6.2.
+
+## 7.1.6.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.6.5-1. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.6.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.6.5-1: TRS minimum requirement for E-UTRA TDD roaming bands in the speech position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.7 Total Radiated Sensitivity (TRS) for UTRA FDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.1.7.2-1 and 7.1.7.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.1.7.4.3 Procedure, reverberation chamber method
+
+### 7.1.7.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 7 and later releases.
+
+### 7.1.7.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.7.2-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.7.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.7.2-1: Handheld UE TRS minimum requirements for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |     |
+|----------------|--------------|-----------------------|-----|
+|                |              | Average               | Max |
+| I              | dBm/3.84 MHz | TBD                   | TBD |
+| II             | dBm/3.84 MHz | TBD                   | TBD |
+| III            | dBm/3.84 MHz | TBD                   | TBD |
+| IV             | dBm/3.84 MHz | TBD                   | TBD |
+| V              | dBm/3.84 MHz | TBD                   | TBD |
+| VI             | dBm/3.84 MHz | TBD                   | TBD |
+| VII            | dBm/3.84 MHz | TBD                   | TBD |
+| VIII           | dBm/3.84 MHz | TBD                   | TBD |
+| IX             | dBm/3.84 MHz | TBD                   | TBD |
+| XIX            | dBm/3.84 MHz | TBD                   | TBD |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF<sub>ior</sub>> [average and min] shall apply for Band IX.  
+NOTE 3: Applicable for dual-mode GSM/UMTS.  
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -98 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -95 dBm/3.84 MHz shall apply for Band II.  
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -100 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -97 dBm/3.84 MHz shall apply for Band IV.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.3.1.
+
+### 7.1.7.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.7.4 Method of test
+
+#### 7.1.7.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for browsing mode specified in Subclause 4.3.4.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.7.4.1-1.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.7.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                   |
+|------------------|-----------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$   |
+| P-CCPCH          | $P-CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$     |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$    |
+| DPCH             | Test dependent power                    |
+
+#### 7.1.7.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.1.7.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $P_{ref}$  is sensitivity measurement done with standard setting.  $P_{nonstd}$  is sensitivity measurement done with non standard settings.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.7.2.
+
+#### 7.1.7.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 7.1.7.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.7.5-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.7.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.1.7.5-1: TRS minimum requirement for UTRA FDD roaming bands in hand phantom browsing mode position**
+
+| Operating band | Unit         | <REF <sub>ior</sub> > |        |
+|----------------|--------------|-----------------------|--------|
+|                |              | Average               | Max    |
+| I              | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| II             | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| III            | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| IV             | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| V              | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| VI             | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| VII            | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| VIII           | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| IX             | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+| XIX            | dBm/3.84 MHz | TBD+TT                | TBD+TT |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.
+
+NOTE 2: For the UE which supports both Band III and Band IX operating frequencies, the reference level of TDB dBm TRS <REF<sub>ior</sub>> [average and min] shall apply for Band IX.
+
+NOTE 3: Applicable for dual-mode GSM/UMTS.
+
+NOTE 4: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -98 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -95 dBm/3.84 MHz shall apply for Band II.
+
+NOTE 5: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>ior</sub>> level of -100 dBm/3.84 MHz and max <REF<sub>ior</sub>> level of -97 dBm/3.84 MHz shall apply for Band IV.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.8 Total Radiated Sensitivity (TRS) for UTRA LCR TDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items is missing or incomplete:
+
+- Table 7.1.8.2-1 and 7.1.8.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.1.8.4.3 Procedure, reverberation chamber method
+
+### 7.1.8.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 8 and later releases.
+
+### 7.1.8.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.5.2-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.8.2-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.8.2-1: Handheld UE TRS minimum requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band                                   | Unit         | <REFior> |     |
+|--------------------------------------------------|--------------|----------|-----|
+|                                                  |              | Average  | Max |
+| a                                                | dBm/1.28 MHz | TBD      | TBD |
+| b                                                | dBm/1.28 MHz | TBD      | TBD |
+| c                                                | dBm/1.28 MHz | TBD      | TBD |
+| d                                                | dBm/1.28 MHz | TBD      | TBD |
+| e                                                | dBm/1.28 MHz | TBD      | TBD |
+| f                                                | dBm/1.28 MHz | TBD      | TBD |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD. |              |          |     |
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.3.2.
+
+### 7.1.8.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.8.4 Method of test
+
+#### 7.1.8.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.4.
+- 2) Set the SS downlink physical channels according to settings in Table 7.1.8.4.1-1. The DL power level should be set to ensure 0% BER at 12.2kbps data rate at the whole 3D initial scan.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2.
+- 5) Enter the UE into loopback test mode and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] and Annex C of TS 34.122 [8] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.1.8.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                                 | Power |
+|------------------|---------------------------------|-------|
+| Ior              | -75 dBm                         | -     |
+| DwPCH            | DwPCH_Ec / Ior                  | 0 dB  |
+| PCCPCH           | $\sum P\text{-CCPCH\_Ec} / Ior$ | -3 dB |
+| SCCPCH           | $\sum S\text{-CCPCH\_Ec} / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$           | -6 dB |
+| FPACH            | FPACH_Ec / Ior                  | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$           | 0 dB  |
+
+#### 7.1.8.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 40000 or more bits, see Annex E.20. The DL power step size shall be no bigger than 0.5dB when the RF level is near the TDD UE sensitivity level.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.1.8.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting.  $S_{non}$  is sensitivity measurement done with non standard settings.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.1.8.2.
+
+#### 7.1.8.4.3 Procedure, reverberation chamber method
+
+TBD
+
+#### 7.1.8.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.8.5-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.8.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.8.5-1: TRS minimum requirement for UTRA LCR TDD roaming bands in hand phantom browsing mode position**
+
+| Operating band                                  | Unit         | <REFior> |        |
+|-------------------------------------------------|--------------|----------|--------|
+|                                                 |              | Average  | Max    |
+| a                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| b                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| c                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| d                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| e                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| f                                               | dBm/1.28 MHz | TBD+TT   | TBD+TT |
+| Note: Applicable for dual-mode GSM/UTRA LCR TDD |              |          |        |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.9 Total Radiated Sensitivity (TRS) for E-UTRA FDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items is missing or incomplete:
+
+- Table 7.1.9.2-1 and 7.1.9.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.1.9.4.3 Procedure, reverberation chamber method
+
+### 7.1.9.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 7.1.9.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.9.2-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.9.2-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.9.2-1: TRS minimum requirements for E-UTRA FDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.3.3.
+
+### 7.1.9.3 Test purpose
+
+The purpose of this test is to ensure that  $\text{TRS}_{\text{max}}$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.1.9.4 Method of test
+
+#### 7.1.9.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.4.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.4-2 for FDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.1.9.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.1.9.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.9.2.
+
+#### 7.1.9.4.3 Procedure, reverberation chamber method
+
+TBD
+
+### 7.1.9.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.9.5-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.9.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\text{max}} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.9.5-1: TRS minimum requirement for E-UTRA FDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.1.10 Total Radiated Sensitivity (TRS) for E-UTRA TDD in Browsing Mode with Hand Phantom
+
+Editor's notes: This subclause is incomplete. The following items is missing or incomplete:
+
+- Table 7.1.10.2-1 and 7.1.10.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.1.10.4.3 Procedure, reverberation chamber method
+
+### 7.1.10.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $x$  and  $y$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of LTE UEs independent of release.
+
+### 7.1.10.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.10.2-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.10.2-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{left\_low} / 10}, 10^{P_{left\_mid} / 10}, 10^{P_{left\_high} / 10}, 10^{P_{right\_low} / 10}, 10^{P_{right\_mid} / 10}, 10^{P_{right\_high} / 10} \right) \right]$$
+
+**Table 7.1.10.2-1: TRS minimum requirements for E-UTRA TDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.1.3.4.
+
+### 7.1.10.3 Test purpose
+
+The purpose of this test is to ensure that  $TRS_{\max}$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+## 7.1.10.4 Method of test
+
+### 7.1.10.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.2.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.5-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for speech mode specified in Subclause 4.3.4.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.5-2 for TDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+### 7.1.10.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.1.10.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT on the left and right ears of the head phantom using the left and right hand phantom for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.1.10.2.
+
+### 7.1.10.4.3 Procedure, reverberation chamber method
+
+TBD
+
+## 7.1.10.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.1.10.5-1. For the hand phantom browsing mode position the averaging shall be done in linear scale for the TRS results of both right and left hand phantom measurements. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.1.10.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.1.10.5-1: TRS minimum requirement for E-UTRA TDD roaming bands in hand phantom browsing mode position**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.2 Performance for LME
+
+### 7.2.1 Total Radiated Sensitivity (TRS) for UTRA FDD LME
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.2.1.2-1 and 7.2.1.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.2.1.4.3 Procedure, reverberation chamber method
+
+#### 7.2.1.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $P_{pol}$  are the orthogonal polarizations.
+
+In these formulas  $N_{\theta}$  and  $N_{\phi}$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_i$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the FDD UE for Release 11 and later releases that support LME.
+
+NOTE: This test case can be optionally executed for Release 7 and onward UE's supporting LME feature.
+
+#### 7.2.1.2 Minimum Requirements
+
+The average TRS of low, mid and high channel for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 25.101 [2] shall be lower than minimum performance requirements for roaming bands shown in Table 7.2.1.2-1. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for roaming bands shown in the columns "Max" on the requirement tables.
+
+**Table 7.2.1.2-1: TRS minimum requirements for UTRA FDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band                                                                           | Unit         | <REF <sub>Ir</sub> > |     |
+|------------------------------------------------------------------------------------------|--------------|----------------------|-----|
+|                                                                                          |              | Average              | Max |
+| I                                                                                        | dBm/3.84 MHz | TBD                  | TBD |
+| II                                                                                       | dBm/3.84 MHz | TBD                  | TBD |
+| III                                                                                      | dBm/3.84 MHz | TBD                  | TBD |
+| IV                                                                                       | dBm/3.84 MHz | TBD                  | TBD |
+| V                                                                                        | dBm/3.84 MHz | TBD                  | TBD |
+| VI                                                                                       | dBm/3.84 MHz | TBD                  | TBD |
+| VII                                                                                      | dBm/3.84 MHz | TBD                  | TBD |
+| VIII                                                                                     | dBm/3.84 MHz | TBD                  | TBD |
+| IX                                                                                       | dBm/3.84 MHz | TBD                  | TBD |
+| IX                                                                                       | dBm/3.84 MHz | TBD                  | TBD |
+| NOTE 1 For Power Class 3, 3bis and 4 this shall be achieved at the maximum output power. |              |                      |     |
+| NOTE 2 Applicable for dual-mode GSM/UMTS.                                                |              |                      |     |
+| NOTE 3 Applicable for USB plug-in devices.                                               |              |                      |     |
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.2.2.
+
+### 7.2.1.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.2.1.4 Method of test
+
+#### 7.2.1.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3.
+
+Test environment: normal; see TS 36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the plug-in UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Set the SS downlink physical channels according to settings in Table 7.2.1.4.1-1.
+- 3) Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.2.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                      | Power |
+|------------------|----------------------|-------|
+| CPICH            | CPICH_Ec / DPCH_Ec   | 7 dB  |
+| P-CCPCH          | P-CCPCH_Ec/ DPCH_Ec  | 5 dB  |
+| SCH              | SCH_Ec / DPCH_Ec     | 5 dB  |
+| PICH             | PICH_Ec / DPCH_Ec    | 2 dB  |
+| DPCH             | Test dependent power | -     |
+
+#### 7.2.1.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+- 4) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the plug-in UE causing BER value of  $1\% \pm 0.2\%$  using 20000 or more bits; see Annex E.20.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 6) Calculate TRS using equations from clause 7.2.1.1
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting.  $S_{nonstd}$  is sensitivity measurement done with non standard settings.  $N_{ref}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.2.1.2.
+
+#### 7.2.1.4.3 Test procedure, reverberation chamber method
+
+TBD
+
+#### 7.2.1.5 Test requirements
+
+The average TRS of low, mid and high channel for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 25.101 [2] shall be lower than test requirements for roaming bands shown in Table 7.2.1.5-1. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for roaming bands shown in the columns "Max" on the requirement tables.
+
+**Table 7.2.1.5-1: TRS test requirements for UTRA FDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band                                                                           | Unit         | <REFÎ <sub>or</sub> > |          |
+|------------------------------------------------------------------------------------------|--------------|-----------------------|----------|
+|                                                                                          |              | Average               | Max      |
+| I                                                                                        | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| II                                                                                       | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| III                                                                                      | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| IV                                                                                       | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| V                                                                                        | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| VI                                                                                       | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| VII                                                                                      | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| VIII                                                                                     | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| IX                                                                                       | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| XIX                                                                                      | dBm/3.84 MHz | TBD + TT              | TBD + TT |
+| NOTE 1 For Power Class 3, 3bis and 4 this shall be achieved at the maximum output power. |              |                       |          |
+| NOTE 2 Applicable for dual-mode GSM/UMTS.                                                |              |                       |          |
+| NOTE 3 Applicable for USB plug-in devices.                                               |              |                       |          |
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+## 7.2.2 Total Radiated Sensitivity (TRS) for UTRA LCR TDD LME
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.2.2.2-1 and 7.2.2.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.2.2.4.3 Procedure, reverberation chamber method
+
+### 7.2.2.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The requirements and this test apply to all types of UTRA for the TDD UE for Release 11 and later releases that support LME.
+
+NOTE: This test case can be optionally executed for Release 7 and onward UE’s supporting LME feature.
+
+### 7.2.2.2 Minimum Requirements
+
+The average TRS of low, mid and high channel for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 34.122 [8] shall be lower than minimum performance requirements for roaming bands shown in Table 7.2.2.2-1. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for roaming bands shown in the columns “Max” on the requirement tables.
+
+**Table 7.2.2.2-1: TRS minimum requirements for UTRA LCR TDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band | Unit         | <REFior> |     |
+|----------------|--------------|----------|-----|
+|                |              | Average  | Max |
+| -              | -            |          |     |
+| a              | dBm/1.28 MHz | TBD      | TBD |
+| b              | dBm/1.28 MHz | TBD      | TBD |
+| c              | dBm/1.28 MHz | TBD      | TBD |
+| d              | dBm/1.28 MHz | TBD      | TBD |
+| e              | dBm/1.28 MHz | TBD      | TBD |
+| f              | dBm/1.28 MHz | TBD      | TBD |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+The normative reference for this clause is TS 37.144 [12] section 7.2.3.
+
+### 7.2.2.3 Test purpose
+
+The purpose of this test is to ensure that  $\Delta$  and  $\Delta$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.2.2.4 Method of test
+
+#### 7.2.2.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the plug-in UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Set the SS downlink physical channels according to settings in Table 7.2.2.4.1-1.
+- 3) Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] and Annex C of TS 34.122 [8] for details regarding generic call setup procedure and loopback test.
+
+**Table 6.7.2: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                                 | Power |
+|------------------|---------------------------------|-------|
+| Ior              | -75 dBm                         | -     |
+| DwPCH            | DwPCH_Ec / Ior                  | 0 dB  |
+| PCCPCH           | $\sum P\text{-CCPCH\_Ec} / Ior$ | -3 dB |
+| SCCPCH           | $\sum S\text{-CCPCH\_Ec} / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$           | -6 dB |
+| FPACH            | FPACH_Ec / Ior                  | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$           | 0 dB  |
+
+#### 7.2.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the plug-in UE.
+- 2) As the plug-in UE reaches maximum power, start sending PN15 data pattern.
+- 3) Position the plug-in UE into the USB connector in accordance with the manufacturer recommended primary mechanical mode. In the absence of such a recommendation position the plug-in UE so that it is horizontally plugged into the horizontal USB connector.
+- 4) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 40000 or more bits; see Annex E.20. The DL power step size shall be no bigger than 0.5dB when the RF level is near the TDD UE sensitivity level.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 6) Calculate TRS using equations from Subclause 7.2.2.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting.  $S_{nonstd}$  is sensitivity measurement done with non standard settings.  $N$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.2.2.2.
+
+#### 7.2.2.4.3 Test procedure, reverberation chamber method
+
+TBD
+
+#### 7.2.2.5 Test requirements
+
+The average TRS of low, mid and high channel for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 34.122 [8] shall be lower than test requirements for roaming bands shown in Table 7.2.2.5-1. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for roaming bands shown in the columns "Max" on the requirement tables.
+
+**Table 7.2.2.5-1: TRS test requirements for UTRA LCR TDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band | Unit         | <REFior> |          |
+|----------------|--------------|----------|----------|
+|                |              | Average  | Max      |
+| -              | -            |          |          |
+| a              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+| b              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+| c              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+| d              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+| e              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+| f              | dBm/1.28 MHz | TBD + TT | TBD + TT |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+## 7.2.3 Total Radiated Sensitivity (TRS) for E-UTRA FDD LME
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.2.3.2-1 and 7.2.3.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.2.3.4.3 Procedure, reverberation chamber method
+- Applicability
+
+### 7.2.3.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+[Applicability is TBD]
+
+### 7.2.3.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.2.3.2-1. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.2.3.2-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.2.3.2-1: TRS minimum performance requirement for E-UTRA FDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.2.4.
+
+### 7.2.3.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.2.3.4 Method of test
+
+#### 7.2.3.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the plug-in UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-2 for FDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.2.3.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.2.3.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.2.3.2.
+
+#### 7.2.3.4.3 Procedure, reverberation chamber method
+
+TBD
+
+### 7.2.3.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.2.3.5-1. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.2.3.5-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.2.3.5-1: TRS minimum requirement for E-UTRA FDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+## 7.2.4 Total Radiated Sensitivity (TRS) for E-UTRA TDD LME
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.2.4.2-1 and 7.2.4.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.2.4.4.3 Procedure, reverberation chamber method
+- Applicability
+
+### 7.2.4.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+[Applicability is TBD]
+
+### 7.2.4.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.2.4.2-1. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+$$TRS_{average} = 10 \log \left[ 6 \left( \frac{1}{10^{P_{left\_low}/10}} + \frac{1}{10^{P_{left\_mid}/10}} + \frac{1}{10^{P_{left\_high}/10}} + \frac{1}{10^{P_{right\_low}/10}} + \frac{1}{10^{P_{right\_mid}/10}} + \frac{1}{10^{P_{right\_high}/10}} \right) \right]$$
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.2.4.2-1. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.2.4.2-1: TRS minimum performance requirement for E-UTRA TDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.2.5.
+
+### 7.2.4.3 Test purpose
+
+The purpose of this test is to ensure that ~~and~~ of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.2.4.4 Method of test
+
+#### 7.2.4.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the plug-in UE according to the DUT positioning on laptop ground plane phantom specified in Subclause 4.3.2.
+- 2) Power on the plug-in UE. The real functional laptop supplies power to the plug-in UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.5-2 for TDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.2.4.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.2.4.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.2.4.2.
+
+#### 7.2.4.4.3 Procedure, reverberation chamber method
+
+TBD
+
+### 7.2.4.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.2.4.5-1. The averaging shall be done in linear scale for the TRS results. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+$$TRS_{average} = 10 \log \left[ 6 / \left( \frac{1}{10^{P_{left\_low}/10}} + \frac{1}{10^{P_{left\_mid}/10}} + \frac{1}{10^{P_{left\_high}/10}} + \frac{1}{10^{P_{right\_low}/10}} + \frac{1}{10^{P_{right\_mid}/10}} + \frac{1}{10^{P_{right\_high}/10}} \right) \right]$$
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.2.4.5-1. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.2.4.5-1: TRS minimum requirement for E-UTRA TDD roaming mode for LME devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.2.
+
+## 7.3 Performance for LEE
+
+### 7.3.1 Total Radiated Sensitivity (TRS) for UTRA FDD LEE
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.3.1.2-1 and 7.3.1.5-1 as they are not specified in TS 37.144 yet
+- Applicability
+
+#### 7.3.1.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $T_n$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $T_n$  is calculated by using the following equation:
+
+where  $T_{m,n}$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $M_n$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+[Applicability is TBD]
+
+#### 7.3.1.2 Minimum Requirements
+
+The average TRS of low, mid and high channel of the LEE in the data transfers position for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS25.101 [2] shall be lower than minimum performance requirements for
+
+roaming bands shown in Table 7.3.1.2-1 for notebook devices and in Table 7.3.1.2-2 for tablet devices. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel in the data transfers position shall be better than minimum performance requirements for roaming bands shown in the columns “Max”.
+
+**Table 7.3.1.2-1: TRS minimum requirements for UTRA FDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Unit         | <REFI <sub>or</sub> > |        |
+|----------------|--------------|-----------------------|--------|
+|                |              | Average               | Max    |
+| I              | dBm/3.84 MHz | -103.5                | -102.0 |
+| II             | dBm/3.84 MHz | TBD                   | TBD    |
+| III            | dBm/3.84 MHz | TBD                   | TBD    |
+| IV             | dBm/3.84 MHz | TBD                   | TBD    |
+| V              | dBm/3.84 MHz | TBD                   | TBD    |
+| VI             | dBm/3.84 MHz | -101.5                | -99.5  |
+| VII            | dBm/3.84 MHz | TBD                   | TBD    |
+| VIII           | dBm/3.84 MHz | -101.5                | -99.5  |
+| IX             | dBm/3.84 MHz | TBD                   | TBD    |
+| XIX            | dBm/3.84 MHz | -101.5                | -99.5  |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for notebook devices.
+
+NOTE: TRS minimum performance requirements in Table 7.3.1.2-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table 7.3.1.2-2: TRS minimum requirements for UTRA FDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Unit         | <REFI <sub>or</sub> > |         |
+|----------------|--------------|-----------------------|---------|
+|                |              | Average               | Max     |
+| I              | dBm/3.84 MHz | -105.75               | -104.25 |
+| II             | dBm/3.84 MHz | TBD                   | TBD     |
+| III            | dBm/3.84 MHz | TBD                   | TBD     |
+| IV             | dBm/3.84 MHz | TBD                   | TBD     |
+| V              | dBm/3.84 MHz | -103.0                | -101.0  |
+| VI             | dBm/3.84 MHz | TBD                   | TBD     |
+| VII            | dBm/3.84 MHz | TBD                   | TBD     |
+| VIII           | dBm/3.84 MHz | TBD                   | TBD     |
+| IX             | dBm/3.84 MHz | TBD                   | TBD     |
+| XIX            | dBm/3.84 MHz | -103.0                | -101.0  |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for tablet devices with two antennas.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.3.2.
+
+### 7.3.1.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.3.1.4 Method of test
+
+#### 7.3.1.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.1-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Set the SS downlink physical channels according to settings in Table 7.3.1.4.1-1.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.3.1.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel | Power                                   |
+|------------------|-----------------------------------------|
+| CPICH            | $CPICH\_Ec / DPCH\_Ec = 7 \text{ dB}$   |
+| P-CCPCH          | $P-CCPCH\_Ec / DPCH\_Ec = 5 \text{ dB}$ |
+| SCH              | $SCH\_Ec / DPCH\_Ec = 5 \text{ dB}$     |
+| PICH             | $PICH\_Ec / DPCH\_Ec = 2 \text{ dB}$    |
+| DPCH             | Test dependent power                    |
+
+#### 7.3.1.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 20000 or more bits; see Annex E.20.
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.3.1.1.
+
+NOTE: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $S_{std}$  is sensitivity measurement done with standard setting,  $S_{nonstd}$  is sensitivity measurement done with non standard settings.  $N_{std}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.3.1.2.
+
+#### 7.3.1.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Set the base station simulator to a specific output power and perform a BER measurement.
+- 4) Increase or decrease the base station output power as needed, and repeat step 4 until the lowest output power is found that gives a BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20. This corresponds to .
+
+NOTE: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Repeat step 3 and 4 until a sufficient number of independent samples (see section 4.5) of has been measured.
+- 7) Calculate TRS using equations from chapter 7.3.1.1.
+
+NOTE 1: The measurement procedure is based on samples of the received signal power at the UE/MS from a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power received by the DUT is undergoing Rayleigh fading and is transmitted by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRS value.
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.3.1.2.
+
+#### 7.3.1.5 Test requirements
+
+The average TRS of low, mid and high channel in the data transfers position for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 25.101 [2] shall be lower than test requirements for roaming bands shown in Table 7.3.1.5-1 for notebook devices and in Table 7.3.1.5-2 for tablet devices. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel in the data transfers position shall be better than minimum performance requirements for roaming bands shown in the columns "Max".
+
+**Table 7.3.1.5-1: TRS test requirements for UTRA FDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>ip</sub> > |        |
+|----------------|--------------|----------------------|--------|
+|                |              | Average              | Max    |
+| I              | dBm/3.84 MHz | -103.5+TT            | TBD+TT |
+| II             | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| III            | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| IV             | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| V              | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| VI             | dBm/3.84 MHz | -101.5+TT            | TBD+TT |
+| VII            | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| VIII           | dBm/3.84 MHz | -101.5+TT            | TBD+TT |
+| IX             | dBm/3.84 MHz | TBD+TT               | TBD+TT |
+| XIX            | dBm/3.84 MHz | -101.5+TT            | TBD+TT |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for notebook devices.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 7.3.1.5-2: TRS test requirements for UTRA FDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>ip</sub> > |            |
+|----------------|--------------|----------------------|------------|
+|                |              | Average              | Max        |
+| I              | dBm/3.84 MHz | -105.75+TT           | -104.25+TT |
+| II             | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| III            | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| IV             | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| V              | dBm/3.84 MHz | -103.0+TT            | -101.0+TT  |
+| VI             | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| VII            | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| VIII           | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| IX             | dBm/3.84 MHz | TBD+TT               | TBD+TT     |
+| XIX            | dBm/3.84 MHz | -103.0+TT            | -101.0+TT  |
+
+NOTE 1: For power class 3, 3bis and 4 this shall be achieved at the maximum output power.  
+NOTE 2: Applicable for dual-mode GSM/UMTS.  
+NOTE 3: Applicable for tablet devices with two antennas.
+
+NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+## 7.3.2 Total Radiated Sensitivity (TRS) for UTRA LCR TDD LEE
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.3.2.2-1 and 7.3.2.5-1 as they are not specified in TS 37.144 yet
+- Text for Subclause 7.3.2.4.3 Procedure, reverberation chamber method
+- Applicability
+
+### 7.3.2.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $h$  and  $v$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{ref,n}$  is calculated by using the following equation:
+
+where  $P_{ref,n,m}$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $M$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+[Applicability is TBD]
+
+### 7.3.2.2 Minimum Requirements
+
+The average TRS of low, mid and high channel of the LEE in the data transfers position for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS34.122 [8] shall be lower than minimum performance requirements for roaming bands shown in Table 7.3.2.2-1 for notebook devices and in Table 7.3.2.2-2 for tablet devices. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel in the data transfers position shall be better than minimum performance requirements for roaming bands shown in the columns “Max”.
+
+**Table 7.3.2.2-1: TRS minimum requirements for UTRA LCR TDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band                                                                                 | Unit         | <REFior> |     |
+|------------------------------------------------------------------------------------------------|--------------|----------|-----|
+|                                                                                                |              | Average  | Max |
+| -                                                                                              | -            |          |     |
+| a                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| b                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| c                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| d                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| e                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| f                                                                                              | dBm/1.28 MHz | TBD      | TBD |
+| NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.<br>NOTE 2: Applicable for notebook devices. |              |          |     |
+
+**Table 7.3.2.2-1: TRS minimum requirements for UTRA LCR TDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band                                     | Unit         | <REFior> |     |
+|----------------------------------------------------|--------------|----------|-----|
+|                                                    |              | Average  | Max |
+| -                                                  | -            |          |     |
+| a                                                  | dBm/1.28 MHz | TBD      | TBD |
+| b                                                  | dBm/1.28 MHz | TBD      | TBD |
+| c                                                  | dBm/1.28 MHz | TBD      | TBD |
+| d                                                  | dBm/1.28 MHz | TBD      | TBD |
+| e                                                  | dBm/1.28 MHz | TBD      | TBD |
+| f                                                  | dBm/1.28 MHz | TBD      | TBD |
+| NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD. |              |          |     |
+| NOTE 2: Applicable for notebook devices.           |              |          |     |
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.3.3.
+
+### 7.3.2.3 Test purpose
+
+The purpose of this test is to ensure that and of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.3.2.4 Method of test
+
+#### 7.3.2.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.2-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Set the SS downlink physical channels according to settings in Table 7.3.2.4.1-1.
+- 3) Power on the UE.
+- 4) A call is set up according to the Generic call setup procedure. The power control algorithm shall be set to Power Control Algorithm 2. Compressed mode shall be set to OFF.
+- 5) Enter the UE into loopback test mode 2 and start the loopback test.
+
+See TS 34.108 [4] and TS 34.109 [5] and Annex C of TS 34.122 [8] for details regarding generic call setup procedure and loopback test.
+
+**Table 7.3.2.4.1-1: Downlink Physical Channels transmitted during a connection**
+
+| Physical Channel |                                 | Power |
+|------------------|---------------------------------|-------|
+| Ior              | -75 dBm                         | -     |
+| DwPCH            | DwPCH_Ec / Ior                  | 0 dB  |
+| PCCPCH           | $\sum P\text{-CCPCH\_Ec} / Ior$ | -3 dB |
+| SCCPCH           | $\sum S\text{-CCPCH\_Ec} / Ior$ | -6 dB |
+| PICH             | $\sum PICH\_Ec / Ior$           | -6 dB |
+| FPACH            | FPACH_Ec / Ior                  | -6 dB |
+| DL DPCH          | $\sum DPCH\_Ec / Ior$           | 0 dB  |
+
+#### 7.3.2.4.2 Procedure
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Measure EIS from one measurement point. EIS is the power transmitted from one specific direction to the UE causing BER value of  $1\% \pm 0.2\%$  using 40000 or more bits; see Annex E.20. The DL power step size shall be no bigger than 0.5dB when the RF level is near the TDD UE sensitivity level.
+
+NOTE 1: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 4) Measure the EIS for every direction of selected sampling grid using two orthogonal polarizations to obtain TRS.
+- 5) Calculate TRS using equations from Subclause 7.3.2.1.
+
+NOTE 2: To speed up sensitivity measurements non standard setting (i.e. data speed, PCL, BER target) can be used in the measurements. However to obtain TRS result the measured EIS figures shall be normalized by
+
+Where  $\text{EIS}_{\text{standard}}$  is sensitivity measurement done with standard setting,  $\text{EIS}_{\text{non\_standard}}$  is sensitivity measurement done with non standard settings.  $N_{\text{ref}}$  is amount of reference measurement points.
+
+To ensure accuracy of TRS, the amount of reference points measured should be at least 4. It is recommended to spread the reference measurements equally during the measurement time.
+
+The measurement procedure is based on the measurement of the spherical sensitivity pattern of the DUT. The sensitivity values of the DUT at a predefined BER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The EIS samples are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions. All the EIS samples are taken with two orthogonal polarizations, - and -polarisations (See Subclause 4.4).
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.3.2.2.
+
+#### 7.3.2.4.3 Procedure, reverberation chamber method
+
+- 1) Send continuously Up power control commands to the UE.
+- 2) As the UE reaches maximum power, start sending PN15 data pattern.
+- 3) Set the base station simulator to a specific output power and perform a BER measurement.
+- 4) Increase or decrease the base station output power as needed, and repeat step 3 until the lowest output power is found that gives a BER value of  $1\% \pm 0.2\%$  using 20000 or more bits, see Annex E.20. This corresponds to  $\text{EIS}_{\text{min}}$ .
+
+NOTE 1: To meet BER value target DL power level can be changed using user's freely selectable algorithm.
+
+- 5) Repeat step 3 and 4 until a sufficient number of independent samples (see section 4.5) of  $\text{EIS}_{\text{min}}$  has been measured.
+- 6)
+- 7) Calculate TRS using equations from chapter 7.3.2.1.
+
+NOTE 2: The measurement procedure is based on samples of the received signal power at the UE/MS from a full 3 dimensional isotropic environment with uniform elevation and azimuth field distribution. The power received by the DUT is undergoing Rayleigh fading and is transmitted by the fixed measurement antennas. Moreover, it is important that the samples collected are independent, in order to get sufficient accuracy of the estimated TRS value.
+
+The Total Radiated Sensitivity is calculated from the measured data by equation in Subclause 7.3.2.2.
+
+...
+
+### 7.3.2.5 Test requirements
+
+The average TRS of low, mid and high channel for 1% BER with 12.2kbps DL reference channel as defined in Annex C.3 of TS 34.122 [8] shall be lower than test requirements for roaming bands shown in Table 7.3.2.5-1 for notebook devices and Table 7.3.2.5-2 for tablet devices. The averaging shall be done in linear scale for the TRS results.
+
+In addition the maximum TRS of each measured channel shall be better than minimum performance requirements for roaming bands shown in the columns "Max".
+
+**Table 7.3.2.5-1: TRS test requirements for UTRA LCR TDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band | Unit         | <REFior> |         |
+|----------------|--------------|----------|---------|
+|                |              | Average  | Max     |
+| a              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| b              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| c              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| d              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| e              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| f              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+**Table 7.3.2.5-2: TRS test requirements for UTRA LCR TDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating Band | Unit         | <REFior> |         |
+|----------------|--------------|----------|---------|
+|                |              | Average  | Max     |
+| a              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| b              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| c              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| d              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| e              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+| f              | dBm/1.28 MHz | TBD +TT  | TBD +TT |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE 2: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex D.
+
+### 7.3.3 Total Radiated Sensitivity (TRS) for E-UTRA FDD LEE
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.3.3.2-1 and 7.3.3.5-1 as they are not specified in TS 37.144 yet
+- Applicability
+
+#### 7.3.3.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency.  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi.  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{rx,m,n}$  is calculated by using the following equation:
+
+where  $P_{rx,m,n}$  is the  $m$ :th value of the transfer function for fixed measurement antenna  $n$ , which gives the BER threshold.  $M_n$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+[Applicability is TBD]
+
+#### 7.3.3.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.3.3.2-1 for notebook devices and in Table 7.3.3.2-2 for tablet devices. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column "Average" on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.3.3.2-1 for notebook devices and in Table 7.3.3.2-2 for tablet devices. Maximum TRS requirement is shown in the column "Max" on the requirement tables.
+
+$$TRS_{max} = 10 \log \left[ \max \left( 10^{P_{left\_low}/10}, 10^{P_{left\_mid}/10}, 10^{P_{left\_high}/10}, 10^{P_{right\_low}/10}, 10^{P_{right\_mid}/10}, 10^{P_{right\_high}/10} \right) \right]$$
+
+**Table 7.3.3.2-1: TRS minimum performance requirement for E-UTRA FDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+LEE TRS minimum performance requirements for E-UTRA FDD in data transfer position mode for throughput  $\geq 95\%$  of the maximum throughput of the reference measurement channels as specified in section 7.3 of [11] and Annex A of [11] are defined in Table 7.3.3.2-2 for Tablet devices.
+
+**Table 7.3.3.2-2: TRS minimum performance requirement for E-UTRA FDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Channel bandwidth | Sensitivity (dBm) |        |
+|----------------|-------------------|-------------------|--------|
+|                |                   | Average           | Max    |
+| 1              | 10 MHz            | -93.75            | -92.25 |
+| 2              | 10 MHz            |                   |        |
+| 3              | 10 MHz            | -95.0             | -93.5  |
+| 4              | 10 MHz            |                   |        |
+| 5              | 10 MHz            |                   |        |
+| 7              | 10 MHz            | -93.5             | -92.0  |
+| 8              | 10 MHz            |                   |        |
+| 12             | 10 MHz            |                   |        |
+| 13             | 10 MHz            |                   |        |
+| 19             | 10 MHz            | -91.5             | -89.5  |
+| 20             | 10 MHz            | -92.5             | -90.5  |
+| 21             | 15 MHz            | -90.0             | -88.5  |
+| 28             | 10 MHz            |                   |        |
+| 32             | 10 MHz            |                   |        |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.3.4.
+
+### 7.3.3.3 Test purpose
+
+The purpose of this test is to ensure that  $\Delta$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.3.3.4 Method of test
+
+#### 7.3.3.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.3-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Power on the UE.
+
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.3-2 for FDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.3.3.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.3.3.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.3.3.2.
+
+#### 7.3.3.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) Repeat Step 1) until a sufficient number of independent samples (see section 4.5) of has been measured. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each sample shall be recorded for calculating the TRS according to Subclause 7.3.3.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.3.3.2.
+
+#### 7.3.3.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.3.3.5-1 for notebook devices and in Table 7.3.3.5-2 for tablet devices. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.3.3.5-1 for notebook devices and in Table 7.3.3.5-2 for tablet devices. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.3.3.5-1: TRS minimum requirement for E-UTRA FDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+**Table 7.3.3.5-2: TRS minimum requirement for E-UTRA FDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+| Operating band | Channel bandwidth | Sensitivity (dBm) |        |
+|----------------|-------------------|-------------------|--------|
+|                |                   | Average           | Max    |
+| 1              | 10 MHz            | -92.85            | -91.05 |
+| 2              | 10 MHz            |                   |        |
+| 3              | 10 MHz            | -94.1             | -92.3  |
+| 4              | 10 MHz            |                   |        |
+| 5              | 10 MHz            |                   |        |
+| 7              | 10 MHz            | -92.6             | -90.8  |
+| 8              | 10 MHz            |                   |        |
+| 12             | 10 MHz            |                   |        |
+| 13             | 10 MHz            |                   |        |
+| 19             | 10 MHz            | -90.6             | -88.3  |
+| 20             | 10 MHz            | -91.6             | -89.3  |
+| 21             | 15 MHz            | -89.1             | -87.3  |
+| 28             | 10 MHz            |                   |        |
+| 32             | 10 MHz            |                   |        |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+## 7.3.4 Total Radiated Sensitivity (TRS) for E-UTRA TDD LEE
+
+Editor’s notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Table 7.3.4.2-1 and 7.3.4.5-1 as they are not specified in TS 37.144 yet
+- Applicability
+
+### 7.3.4.1 Definition and applicability
+
+The Total Radiated Sensitivity is defined as:
+
+Where the effective isotropic sensitivity (*EIS*) is defined as the power available at the antenna output such as the sensitivity threshold is achieved for each polarization.  $\Omega$  is the solid angle describing the direction,  $f$  is frequency, and  $\theta$  and  $\phi$  are the orthogonal polarizations.
+
+In these formulas  $N_\theta$  and  $N_\phi$  are the number of sampling intervals for theta and phi, and  $\theta_i$  and  $\phi_j$  are the measurement angles. The sampling intervals are discussed further in Subclause 4.4.
+
+The TRS can also be calculated from measurements in a Rayleigh fading 3 dimensional isotropic environment with in average uniform elevation and azimuth distribution. The calculation of the TRS is in this case based on searching for the lowest power received by the UE/MS for a discrete number of field combinations in the chamber that gives a BER that is better than the specified target BER level. By calibrating the average power transfer function, an absolute value of the TRS can be obtained. The following expression can be used to find the TRS.
+
+where  $P_{ref,n}$  is the reference power transfer function for fixed measurement antenna  $n$ ,  $\Gamma_n$  is the reflection coefficient for fixed measurement antenna  $n$  and  $L_n$  is the path loss in the cables connecting the measurement receiver to fixed measurement antenna  $n$ . These parameters are calculated from the calibration measurement and are further discussed in Annex B.2.  $P_{ref,n}$  is calculated by using the following equation:
+
+where  $T_{n,m}$  is the m:th value of the transfer function for fixed measurement antenna n, which gives the BER threshold.  $N$  is the total number of values of the BER threshold power measured for each fixed measurement antenna.
+
+[Applicability is TBD]
+
+### 7.3.4.2 Minimum Requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.3.4.2-1 for notebook devices and in Table 7.3.4.2-2 for tablet devices. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.3.4.2-1 for notebook devices and in Table 7.3.4.2-2 for tablet devices. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.3.4.2-1: TRS minimum performance requirement for E-UTRA TDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+**Table 7.3.4.2-2: TRS minimum performance requirement for E-UTRA TDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+The normative reference for this clause is TS 37.144 [12] Subclause 7.3.5.
+
+### 7.3.4.3 Test purpose
+
+The purpose of this test is to ensure that  $T_{n,m}$  and  $TRS_{\text{avg}}$  of the UE is above specified limit. The lack of the reception sensitivity decreases the coverage area at the far side from Node B.
+
+### 7.3.5.4 Method of test
+
+#### 7.3.4.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB simulator to setup calls to the DUT. The NB simulator is also used to send test signals to the UE and measure the BER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+Chamber environment constraints and coordinate system shall be the same as described in Subclause A.3.
+
+Phantom Specifications shall be the same as described in Subclause A.2.4. Parameters required for Notebooks are specified in Annex A.2.4.2 and those for Tablets are specified in Annex A.2.4.3.
+
+Test environment: normal; see TS36.508 [10] Subclause 4.1.1.
+
+Frequencies to be tested: low range, mid range, high range; see Table 5.4-2.
+
+Positioning Requirements shall be the same as described in Subclause 4.3.
+
+- 1) Position the UE according to the DUT positioning for devices with embedded modules specified in Subclause 4.3.5.
+- 2) Power on the UE.
+- 3) Set the initial conditions as per Subclause 7.3 of 3GPP TS 36.521-1 [11], with the following exception: set the carrier frequency, channel bandwidth, RB length and RB location as per Table 5.5-2 for TDD mode. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+
+#### 7.3.4.4.2 Procedure
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) For the anechoic chamber based methodologies, repeat Step 1) with 3-D sampling grid specified in Subclause 4.4. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to Subclause 7.3.4.1 to calculate TRS.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.3.4.2.
+
+#### 7.3.4.4.3 Procedure, reverberation chamber method
+
+- 1) Follow Steps 1 through 4 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11], with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]).
+- 2) Repeat Step 1) until a sufficient number of independent samples (see section 4.5) of has been measured. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each sample shall be recorded for calculating the TRS according to Subclause 7.3.4.1.
+- 3) Repeat the measurement of the DUT for low, mid and high channels.
+- 4) Calculate the average and minimum TRS as per Subclause 7.3.4.2.
+
+#### 7.3.4.5 Test requirements
+
+The average measured total radiated sensitivity (TRS) of low, mid and high channel for handheld UE shall be lower than the average TRS requirement specified in Table 7.3.4.5-1 for notebook devices and in Table 7.3.4.5-2 for tablet devices. The averaging shall be done in linear scale for the TRS results of both right and left side of the phantom head. Average TRS requirement is shown in the column “Average” on the requirement tables.
+
+In addition the highest TRS of each measured channel shall be lower than maximum TRS requirement specified in Table 7.3.4.5-1 for notebook devices and in Table 7.3.4.5-2 for tablet devices. Maximum TRS requirement is shown in the column “Max” on the requirement tables.
+
+$$TRS_{\max} = 10 \log \left[ \max \left( 10^{P_{\text{left\_low}}/10}, 10^{P_{\text{left\_mid}}/10}, 10^{P_{\text{left\_high}}/10}, 10^{P_{\text{right\_low}}/10}, 10^{P_{\text{right\_mid}}/10}, 10^{P_{\text{right\_high}}/10} \right) \right]$$
+
+**Table 7.3.4.5-1: TRS minimum requirement for E-UTRA TDD roaming mode for notebook devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+**Table 7.3.4.5-2: TRS minimum requirement for E-UTRA TDD roaming mode for tablet devices in the data transfers position and the primary mechanical mode**
+
+TBD
+
+### 7.4 Radiated Performance of Multiple-antenna Receivers in the UE
+
+#### 7.4.1 Total Radiated Multi-antenna Sensitivity (TRMS) for E-UTRA FDD for Handheld UE in Free Space
+
+Editor's notes: This subclause is incomplete. The following items are missing or incomplete:
+
+- Statistical significance
+
+### 7.4.1.1 Definition and applicability
+
+Requirements in this section are stated for the free space configuration and are applicable to handheld devices, and are not applicable to wrist-worn devices.
+
+For the MPAC methodology and the harmonized RTS methodology, the average TRMS of free space data mode portrait (FS DMP), free space data mode landscape (FSDML), and free space data mode screen up (FS DMSU), as defined in Annex E of TR 37.977 [29], when measured at the mid channel shall be lower than the average TRMS requirements specified in subclauses 7.4.1.2. The averaging shall be done in linear scale for the TRMS results at these DUT positions. Two average TRMS quantities are calculated from sensitivity measurements at 70% and 95% throughput, respectively. Average TRMS requirement are shown in the column “Average, 70” and “Average, 95” on the requirement tables.
+
+$$TRMS_{average,70} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,70}/10}} + \frac{1}{10^{S_{FS\_DML,70}/10}} + \frac{1}{10^{S_{FS\_DMSU,70}/10}} \right) \right]$$
+
+$$TRMS_{average,95} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,95}/10}} + \frac{1}{10^{S_{FS\_DML,95}/10}} + \frac{1}{10^{S_{FS\_DMSU,95}/10}} \right) \right]$$
+
+Where
+
+$$S_{MODE,x} = 10\log \left[ 12 / \left( \frac{1}{10^{P_{MODE,x,0}/10}} + \frac{1}{10^{P_{MODE,x,1}/10}} + \dots + \frac{1}{10^{P_{MODE,x,11}/10}} \right) \right]$$
+
+Such that *MODE* is one of {*FS\_DMP*, *FS\_DML*, *FS\_DMSU*}, *x* is one of {70, 95}, and {*P<sub>MODE,x,0</sub>*, ..., *P<sub>MODE,x,11</sub>*} are the measured sensitivity values at each azimuth position.
+
+For the MPAC methodology and the harmonized RTS methodology, if 1 azimuth position does not result in a defined measured sensitivity at 70% or 95% throughput, *S<sub>MODE,70</sub>* or *S<sub>MODE,95</sub>* are calculated using the 11 measured sensitivities and the maximum downlink RS-EPRE *P<sub>RS-EPRE-MAX</sub>* (substitution approach) for the one missing result. If 2 azimuth positions do not result in a defined measured sensitivity at 95% throughput, *S<sub>MODE,95</sub>* is calculated using the 10 measured sensitivities and *P<sub>RS-EPRE-MAX</sub>* for the two missing results. If more azimuth positions result in undefined values for measured sensitivity at the 70% and/or 95% throughput, then the TRMS requirement for the corresponding throughput levels has not been met by such a device. *P<sub>RS-EPRE-MAX</sub>* is defined as -80 dBm/15 kHz and is the maximum downlink RS-EPRE supported by the test system.
+
+The requirements and this test apply to all types of E-UTRA FDD UE for Release 14 and forward.
+
+### 7.4.1.2 Minimum requirements
+
+Handheld UE TRMS minimum performance requirements for E-UTRA FDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [29] are defined in Table 7.4.1.2-1.
+
+**Table 7.4.1.2-1: Handheld UE TRMS minimum requirements for E-UTRA FDD roaming bands in free space and the primary mechanical mode**
+
+|                                                                                       |            | Test 1                |             |
+|---------------------------------------------------------------------------------------|------------|-----------------------|-------------|
+| Channel Model as defined in Annex M.1                                                 |            | SCME urban micro-cell |             |
+| Operating band                                                                        | Unit       | <REFI <sub>op</sub> > |             |
+|                                                                                       |            | Average, 70           | Average, 95 |
+| 1                                                                                     | dBm/15 kHz | -94.75                | -92.75      |
+| 3                                                                                     | dBm/15 kHz | -93.75                | -91.75      |
+| 5                                                                                     | dBm/15 kHz | -91.5                 | -89.5       |
+| 7                                                                                     | dBm/15 kHz | -92.5                 | -90.5       |
+| 13                                                                                    | dBm/15 kHz | TBD                   | TBD         |
+| 19                                                                                    | dBm/15 kHz | -91.5                 | -89.5       |
+| NOTE: Applicability for devices supporting 4-receiver architectures is not confirmed. |            |                       |             |
+
+The normative reference for this clause is TS 37.144 [12] Subclause 8.1.1.1.
+
+### 7.4.1.3 Test Purpose
+
+The purpose of this test is to ensure that the UE meets the TRMS minimum performance requirements for E-UTRA FDD specified in Subclause 7.4.1.2.
+
+### 7.4.1.4 Method of test for Multi-probe Anechoic Chamber
+
+#### 7.4.1.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT according to Annex P.1.
+
+Channel model shall be set according to Annex M.1 and the emulated antenna array configuration shall be set according to Annex M.2.
+
+Chamber environment constraints and coordinate system shall be the same as described in Annex A.5.1.
+
+Test environment according to Annex O.
+
+The positioning of the device under test within the test volume shall be set as defined in Annex A.5.2.
+
+The calibration procedure is specified in Annex B.2.3.
+
+Positioning Requirements shall be according to Annex A.5.2.
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+- 1) Ensure environmental requirements of Annex O are met.
+- 2) Configure the test system according to Annex P.1 for the applicable test case.
+- 3) Verify the implementation of the channel model as specified in Annex M.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+- 4) Position the UE in the chamber according to Annex A.5.2.
+- 5) Power on the UE.
+- 6) Set up the connection.
+
+#### 7.4.1.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11].
+- 2) Set the Downlink signal level to the appropriate REFSENS value defined in Table 7.1.9.5-1 for 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]) for azimuth position 0. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE to ensure the UE transmits  $P_{\text{UMAX}}$  level for at least the duration of the Throughput measurement. Measure the average throughput for a duration sufficient to achieve statistical significance TBD.
+
+NOTE 1: The downlink power step size shall be no more than 0.5 dB when RF power level is near the LTE MIMO sensitivity level.
+
+NOTE 2: The initial RS EPRE can be set to the user's freely selectable level. Recommended initial RS EPRE is found in Tables P.1-1 and P.1-2.
+
+NOTE 3: The throughput value target DL power level can be changed using user's freely selectable algorithm.
+
+- NOTE 4: For devices that do not reach target throughput, the highest RS EPRE at which throughput is measured shall be -80 dBm/15 kHz. The starting RS EPRE level of the LTE MIMO sensitivity level search does not need to be specified (NOTE 2)
+- NOTE 5: For devices that exhibit non-linear throughput behaviour and that achieve target throughput at multiple RF power levels, LTE MIMO sensitivity level is chosen to be lowest measured DL power level which crosses the target throughput level
+- 3) Repeat Steps 2 for all azimuth positions: Rotate the UE around vertical axis of the test system by 30 degrees and repeat from Step 2 until one complete rotation has been measured i.e. 12 different UE azimuth rotations. A list of orientations is given in Annex A.5.2.
+  - 4) Repeat Steps 2 & 3 for all MODEs as specified in Clause 7.4.1.1.
+  - 5) Repeat Steps 2, 3 & 4 for 70% throughput as specified in Clause 7.4.1.1.
+  - 6) Use post processing and averaging method specified in Clause 7.4.1.1 and calculate average TRMS for 70% and 95% throughput levels.
+
+#### 7.4.1.4A Method of test for Radiated Two-Stage
+
+Use of the RTS method for conformance test depends on the specification of the UE antenna test function which is defined in TR 36.978 [34].
+
+##### 7.4.1.4A.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT according to Clause P.1.
+
+Channel model shall be set according to Clause M.1 and the emulated antenna array configuration shall be set according to Clause M.2 and Annex C of TR 37.977 [29].
+
+Chamber environment constraints and coordinate system shall be the same as described in Annex A.5.1.2.
+
+Test environment according to Annex O.
+
+The positioning of the device under test within the test volume shall be set as defined in Annex A.5.2.
+
+The calibration procedure is specified in Annex B.2.4.
+
+Positioning Requirements shall be according to Annex A.5.2.
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+- 1) Ensure environmental requirements of Annex O are met.
+- 2) Configure the test system according to P.1 for the applicable test case.
+- 3) Verify the implementation of the channel model as specified in Annex M.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+- 4) Position the UE in the chamber according to Annex A.5.2.
+- 5) Power on the UE.
+- 6) Set up the connection.
+
+##### 7.4.1.4A.2 Procedure
+
+The following steps shall be followed in order to evaluate MIMO OTA performance of the DUT:
+
+- 1) Measure the DUT complex antenna pattern at a nominal -60 dBm downlink power as described in Annex A.5.1.2.1 first stage
+- 2) Select an appropriate orientation from the measured antenna pattern and establish a radiated MIMO connection to the DUT using the V and H probes as described in Annex A.5.1.2.1 second stage. Measure the transmission matrix in the chamber and apply the inverse matrix to the MIMO signal. The DUT orientation at which this is done is selected to optimize the achievable isolation. The unknown gain of the DUT antennas represented by the absolute accuracy of the RSAP measurement is then de-embedded from the measured antenna pattern. This is done by comparing the RSAP measurement from the first stage at the orientation being used in the second stage, to a second RSAP measurement made in the second stage using a nominal signal of -60 dBm adjusted by the uncorrected antenna gain for that orientation. The difference in the RSAP measurements represents the true antenna gain for that orientation.
+- 3) With the desired channel model applied, measure the isolation in dB between each stream as seen by the DUT receiver and ensure it is at least 15 dB averaged over at least 200 RSAP measurements.
+- 4) Using the calibrated radiated connection validate monotonicity of the DUT RSAP and RSARP measurements over the range and step size defined in Annex R.
+- 5) Once monotonicity has been validated, check the linearity of RSAP at the orientation of the peak antenna gain over the range -60 dBm to -80 dBm is < 1 dB. Check the linearity of RSARP over the range ± 180 degrees is < 5 degrees. If the uncorrected RSAP or RSARP results do not meet the linearity requirements, calculate and apply a transfer function to the measured patterns to ensure the necessary linearity; if the linearity fails, it must be re-validated after a transfer function has been applied.
+- 6) Convolve the antenna patterns from stage 1, linearized if necessary, with the channel model in the channel emulator and perform the throughput test.
+- 7) Record the throughput for each DUT orientation controlled by the channel emulator and each RS EPRE level.
+- 8) Identify and report the RS EPRE level achieving 70% throughput for averaged throughput.
+
+NOTE 1: The initial RS EPRE can be set to the user's freely selectable level.  
+Recommended initial RS EPRE is found in Tables P.1-1 and P.1-2.
+
+NOTE 2: To meet the throughput value target DL RS EPRE level can be changed using user's freely selectable algorithm.
+
+#### 7.4.1.5 Test requirements
+
+For Handheld UE TRMS minimum performance test requirements for E-UTRA FDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [29] are specified in Table 7.4.1.6-1.
+
+**Table 7.4.1.6-1: Handheld UE TRMS minimum test requirements for E-UTRA FDD roaming bands in free space and the primary mechanical mode**
+
+|                                                                                       |            | Test 1                                                 |             |
+|---------------------------------------------------------------------------------------|------------|--------------------------------------------------------|-------------|
+| Channel Model as defined in Annex M.1                                                 |            | SCME urban micro-cell                                  |             |
+| Operating band                                                                        | Unit       | $\langle \text{REF}\hat{\text{I}}_{\text{or}} \rangle$ |             |
+|                                                                                       |            | Average, 70                                            | Average, 95 |
+| 1                                                                                     | dBm/15 kHz | -93.75                                                 | -91.75      |
+| 3                                                                                     | dBm/15 kHz | -92.75                                                 | -90.75      |
+| 5                                                                                     | dBm/15 kHz | -90.50                                                 | -88.50      |
+| 7                                                                                     | dBm/15 kHz | -91.50                                                 | -89.50      |
+| 13                                                                                    | dBm/15 kHz | TBD                                                    | TBD         |
+| 19                                                                                    | dBm/15 kHz | -90.50                                                 | -88.50      |
+| NOTE: Applicability for devices supporting 4-receiver architectures is not confirmed. |            |                                                        |             |
+
+## 7.4.2 Total Radiated Multi-antenna Sensitivity (TRMS) for E-UTRA TDD for Handheld UE in Free Space
+
+Editor's note: This subclause is incomplete. The following items are missing or incomplete:
+
+- Statistical significance
+
+### 7.4.2.1 Definition and applicability
+
+Requirements in this section are stated for the free space configuration and are applicable to handheld devices, and are not applicable to wrist-worn devices.
+
+For the reference MPAC methodology and the harmonized RTS methodology, the average TRMS of free space data mode portrait (FS DMP), free space data mode landscape (FSDML), and free space data mode screen up (FS DMSU), as defined in Annex E of TR 37.977 [29], when measured at the mid channel shall be lower than the average TRMS requirements specified in subclauses 7.4.2.2. The averaging shall be done in linear scale for the TRMS results at these DUT positions. Two average TRMS quantities are calculated from sensitivity measurements at 70% and 95% throughput, respectively. Average TRMS requirement are shown in the column "Average, 70" and "Average, 95" on the requirement tables.
+
+$$TRMS_{average,70} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,70}/10}} + \frac{1}{10^{S_{FS\_DML,70}/10}} + \frac{1}{10^{S_{FS\_DMSU,70}/10}} \right) \right]$$
+
+$$TRMS_{average,95} = 10\log \left[ 3 / \left( \frac{1}{10^{S_{FS\_DMP,95}/10}} + \frac{1}{10^{S_{FS\_DML,95}/10}} + \frac{1}{10^{S_{FS\_DMSU,95}/10}} \right) \right]$$
+
+Where
+
+$$S_{MODE,x} = 10\log \left[ 12 / \left( \frac{1}{10^{P_{MODE,x,0}/10}} + \frac{1}{10^{P_{MODE,x,1}/10}} + \dots + \frac{1}{10^{P_{MODE,x,11}/10}} \right) \right]$$
+
+Such that *MODE* is one of {*FS\_DMP*, *FS\_DML*, *FS\_DMSU*}, *x* is one of {70, 95}, and {*P<sub>MODE,x,0</sub>*, ..., *P<sub>MODE,x,11</sub>*} are the measured sensitivity values at each azimuth position.
+
+For the reference MPAC methodology and the harmonized RTS methodology, if 1 azimuth position does not result in a defined measured sensitivity at 70% or 95% throughput, *S<sub>MODE,70</sub>* or *S<sub>MODE,95</sub>* are calculated using the 11 measured sensitivities and the maximum downlink RS-EPRE *P<sub>RS-EPRE-MAX</sub>* (substitution approach) for the one missing result. If 2 azimuth positions do not result in a defined measured sensitivity at 95% throughput, *S<sub>MODE,95</sub>* is calculated using the 10 measured sensitivities and *P<sub>RS-EPRE-MAX</sub>* for the two missing results. If more azimuth positions result in undefined values for measured sensitivity at the 70% and/or 95% throughput, then the TRMS requirement for the corresponding throughput levels has not been met by such a device. *P<sub>RS-EPRE-MAX</sub>* is defined as -80 dBm/15 kHz and is the maximum downlink RS-EPRE supported by the test system.
+
+The requirements and this test apply to all types of E-UTRA TDD UE for Release 14 and forward. Use of the TDD RTS test method requires the device supports the ATF defined in Annex R, uses only two Rx antennas for the tested band and the antenna pattern shall not change in response to the radio environment.
+
+### 7.4.2.2 Minimum requirements
+
+Handheld UE TRMS minimum performance requirements for E-UTRA TDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [29] are defined in Table 7.4.2.2-1.
+
+**Table 7.4.2.2-1: Handheld UE TRMS minimum requirements for E-UTRA TDD roaming bands in free space and the primary mechanical mode**
+
+|                                       |             | <b>Test 1</b>                    |                    |
+|---------------------------------------|-------------|----------------------------------|--------------------|
+| Channel Model as defined in Annex M.1 |             | <b>SCME urban micro-cell</b>     |                    |
+| <b>Operating band</b>                 | <b>Unit</b> | <b>&lt;REFI<sub>or</sub>&gt;</b> |                    |
+|                                       |             | <b>Average, 70</b>               | <b>Average, 95</b> |
+| 38                                    | dBm/15 kHz  | -95.5                            | -93.5              |
+| 41                                    | dBm/15 kHz  | -95.5                            | -93.5              |
+
+NOTE 1: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured.  
+NOTE 2: Applicability for devices supporting 4-receiver architectures is not confirmed.
+
+The normative reference for this clause is TS 37.144 [12] Subclause 8.1.1.2.
+
+### 7.4.2.3 Test Purpose
+
+The purpose of this test is to ensure that the UE meets the TRMS minimum performance requirements for E-UTRA TDD specified in Subclause 7.4.2.2.
+
+### 7.4.2.4 Method of test for Multi-probe Anechoic Chamber
+
+#### 7.4.2.4.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT according to Annex P.1.
+
+Channel model shall be set according to Annex M.1 and the emulated antenna array configuration shall be set according to Annex M.2.
+
+Chamber environment constraints and coordinate system shall be the same as described in Annex A.5.1.
+
+Test environment according to Annex O.
+
+The positioning of the device under test within the test volume shall be set as defined in Annex A.5.2.
+
+The calibration procedure is specified in Annex B.2.3.
+
+Positioning Requirements shall be according to Annex A.5.2.
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+- 1) Ensure environmental requirements of Annex O are met.
+- 2) Configure the test system according to Annex P.1 for the applicable test case.
+- 3) Verify the implementation of the channel model as specified in Annex M.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+- 4) Position the UE in the chamber according to Annex A.5.2.
+- 5) Power on the UE.
+- 6) Set up the connection.
+
+#### 7.4.2.4.2 Procedure
+
+- 1) Follow Steps 1 and 2 in Subclause 7.3.4.2 of 3GPP TS 36.521-1 [11].
+
+- 2) Set the Downlink signal level to the appropriate REFSENS value defined in Table 7.1.9.5-1 for 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Annex A of 3GPP TS 36.521-1 [11]) for azimuth position 0. Send continuously uplink power control "up" commands in the uplink scheduling information to the UE to ensure the UE transmits  $P_{\text{UMAX}}$  level for at least the duration of the Throughput measurement. Measure the average throughput for a duration sufficient to achieve statistical significance TBD.
+
+NOTE 1: The downlink power step size shall be no more than 0.5 dB when RF power level is near the LTE MIMO sensitivity level.
+
+NOTE 2: The initial RS EPRE can be set to the user's freely selectable level. Recommended initial RS EPRE is found in Tables P.1-1 and P.1-2.
+
+NOTE 3: The throughput value target DL power level can be changed using user's freely selectable algorithm.
+
+NOTE 4: For devices that do not reach target throughput, the highest RS EPRE at which throughput is measured shall be -80 dBm/15 kHz. The starting RS EPRE level of the LTE MIMO sensitivity level search does not need to be specified (NOTE 2)
+
+NOTE 5: For devices that exhibit non-linear throughput behaviour and that achieve target throughput at multiple RF power levels, LTE MIMO sensitivity level is chosen to be lowest measured DL power level which crosses the target throughput level
+
+- 3) Repeat Steps 2 for all azimuth positions: Rotate the UE around vertical axis of the test system by 30 degrees and repeat from Step 2 until one complete rotation has been measured i.e. 12 different UE azimuth rotations. A list of orientations is given in Annex A.5.2.
+- 4) Repeat Steps 2 & 3 for all MODEs as specified in Clause 7.4.2.1.
+- 5) Repeat Steps 2, 3 & 4 for 70% throughput as specified in Clause 7.4.2.1.
+- 6) Use post processing and averaging method specified in Clause 7.4.2.1 and calculate average TRMS for 70% and 95% throughput levels.
+
+#### 7.4.2.4A Method of test for Radiated Two-Stage
+
+Use of the RTS method for conformance test depends on the specification of the UE antenna test function which is defined in TR 36.978 [34].
+
+##### 7.4.2.4A.1 Initial conditions
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT according to Clause P.1.
+
+Channel model shall be set according to Clause M.1 and the emulated antenna array configuration shall be set according to Clause M.2 and Annex C of TR 37.977 [29].
+
+Chamber environment constraints and coordinate system shall be the same as described in Annex A.5.1.2.
+
+Test environment according to Annex O.
+
+The positioning of the device under test within the test volume shall be set as defined in Annex A.5.2.
+
+The calibration procedure is specified in Annex B.2.4.
+
+Positioning Requirements shall be according to Annex A.5.2.
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+- 1) Ensure environmental requirements of Annex O are met.
+- 2) Configure the test system according to P.1 for the applicable test case.
+- 3) Verify the implementation of the channel model as specified in Annex M.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+- 4) Position the UE in the chamber according to Annex A.5.2.
+- 5) Power on the UE.
+- 6) Set up the connection.
+
+#### 7.4.2.4A.2 Procedure
+
+The following steps shall be followed in order to evaluate MIMO OTA performance of the DUT:
+
+- 1) Measure the DUT complex antenna pattern at a nominal -60 dBm downlink power as described in Annex A.5.1.2.1 first stage
+- 2) Select an appropriate orientation from the measured antenna pattern and establish a radiated MIMO connection to the DUT using the V and H probes as described in Annex A.5.1.2.1 second stage. Measure the transmission matrix in the chamber and apply the inverse matrix to the MIMO signal. The DUT orientation at which this is done is selected to optimize the achievable isolation. The unknown gain of the DUT antennas represented by the absolute accuracy of the RSAP measurement is then de-embedded from the measured antenna pattern. This is done by comparing the RSAP measurement from the first stage at the orientation being used in the second stage, to a second RSAP measurement made in the second stage using a nominal signal of -60 dBm adjusted by the uncorrected antenna gain for that orientation. The difference in the RSAP measurements represents the true antenna gain for that orientation.
+- 3) With the desired channel model applied, measure the isolation in dB between each stream as seen by the DUT receiver and ensure it is at least 15 dB averaged over at least 200 RSAP measurements.
+- 4) Using the calibrated radiated connection validate monotonicity of the DUT RSAP and RSARP measurements over the range and step size defined in Annex R.
+- 5) Once monotonicity has been validated, check the linearity of RSAP at the orientation of the peak antenna gain over the range -60 dBm to -80 dBm is  $< 1$  dB. Check the linearity of RSARP over the range  $\pm 180$  degrees is  $< 5$  degrees. If the uncorrected RSAP or RSARP results do not meet the linearity requirements, calculate and apply a transfer function to the measured patterns to ensure the necessary linearity; if the linearity fails, it must be re-validated after a transfer function has been applied.
+- 6) Convolve the antenna patterns from stage 1, linearized if necessary, with the channel model in the channel emulator and perform the throughput test.
+- 7) Record the throughput for each DUT orientation controlled by the channel emulator and each RS EPRE level.
+- 8) Identify and report the RS EPRE level achieving 70% throughput for averaged throughput.
+
+NOTE 1: The initial RS EPRE can be set to the user's freely selectable level.  
+Recommended initial RS EPRE is found in Tables P.1-1 and P.1-2.
+
+NOTE 2: To meet the throughput value target DL RS EPRE level can be changed using user's freely selectable algorithm.
+
+#### 7.4.2.5 Test requirements
+
+For Handheld UE TRMS minimum performance test requirements for E-UTRA TDD in free space and the primary mechanical mode for 70% and 95% DL throughput with the reference measurement channel defined in Clause 7 of TR 37.977 [29] are specified in Table 7.4.2.5-1.
+
+**Table 7.4.2.5-1: Handheld UE TRMS minimum test requirements for E-UTRA TDD roaming bands in free space and the primary mechanical mode**
+
+|                                       |             | <b>Test 1</b>                    |                    |
+|---------------------------------------|-------------|----------------------------------|--------------------|
+| Channel Model as defined in Annex M.1 |             | <b>SCME urban micro-cell</b>     |                    |
+| <b>Operating band</b>                 | <b>Unit</b> | <b>&lt;REFI<sub>or</sub>&gt;</b> |                    |
+|                                       |             | <b>Average, 70</b>               | <b>Average, 95</b> |
+| 38                                    | dBm/15 kHz  | -94.5                            | -92.5              |
+| 41                                    | dBm/15 kHz  | -94.5                            | -92.5              |
+
+NOTE 1: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured.  
+NOTE 2: Applicability for devices supporting 4-receiver architectures is not confirmed.
+
+## Annex A (normative): Test system characterization and environmental requirements
+
+### A.1 General
+
+The main objective of this section is to specify basic parameters of simulated user (phantom) and anechoic and reverberation chamber suited for the Tx and Rx measurement.
+
+### A.2 Phantom specifications
+
+#### A.2.1 Head phantom
+
+The Specific Anthropomorphic Mannequin (SAM) is used for radiated performance measurements. The phantom shape is derived from the size and dimensions of the 90-th percentile large adult male reported in an anthropometric study. It has also been adapted to represent the flattened ear of a wireless device user.
+
+For DUT radiated performance measurements in "intended use" position SAM head phantom without a shoulder section will be used.
+
+The shell of the SAM phantom should be made of low-loss material (loss tangent less than 0.05) with low permittivity (less than 5). The thickness has to be  $2.0 \pm 0.2$ mm in the areas close to the handset in "intended use" position.
+
+The phantom has to be filled with tissue simulating liquid. It is recommended to use one of the typical SAR tissue simulating liquids and Annex B gives four example recipes of such liquids. It is also recommended to verify the RF properties of the liquid with suitable equipment. The values should be maintained within 15% of the values relative permittivity  $40 (\pm 15\%)$  and  $\sigma$  1.4  $(\pm 15\%)$  at 1900 MHz. If the difference is more than  $\pm 15\%$ , it should be taken in to account in the uncertainty budget. Dielectric properties measurement methods can be found e.g. in [16] [17].
+
+Alternatively, a dry SAM phantom made of plastic material with corresponding electrical parameters can be used.
+
+NOTE: Measurements for the radiated performance of a UE can be influenced by the hand presence. However, it is very difficult to develop a standardized hand phantom, which could allow pertinent and reproducible measurements. Therefore, a phantom hand is not included in this test procedure.
+
+#### A.2.2 Hand phantom
+
+##### A.2.2.1 General
+
+Users hand can have a great impact on radiated performance of a UE. The impact goes beyond blocking or absorbing a portion of the radiation, since the impedance of the antenna itself may be changed due to the material in near field. Thus, a standardized hand phantom has been developed for radiated testing to reflect real world user scenarios [18].
+
+##### A.2.2.2 Dimensions
+
+Dimensions of the hand phantom are based on 50<sup>th</sup> percentile of the men's hand and women's hand dimensions averaged together in order to produce a standard hand phantom that lies in the middle of the expected range of users. Figure A.2.2.2-1 illustrates the segments of the human hand and Table A.2.2.2-1 summarizes the various dimensions for an open hand phantom [18].
+
+![Anatomical diagram of a human hand showing segments and dimension points. The hand is divided into five digits (I-V). Digit I has two phalanges (Distal, Proximal). Digits II-V have three phalanges (Distal, Middle, Proximal). Other labeled parts include MCP (Metacarpal Phalangeal joint), PIP (Proximal Interphalangeal joint), DIP (Distal Interphalangeal joint), Metacarpals, Carpals, CMC (Carpometacarpal joint), and Wrist (showing Radius and Ulna). Red lines indicate various measurement points and segments.](ef8b77a6abdfed4dfe556d2fe12caafd_img.jpg)
+
+Anatomical diagram of a human hand showing segments and dimension points. The hand is divided into five digits (I-V). Digit I has two phalanges (Distal, Proximal). Digits II-V have three phalanges (Distal, Middle, Proximal). Other labeled parts include MCP (Metacarpal Phalangeal joint), PIP (Proximal Interphalangeal joint), DIP (Distal Interphalangeal joint), Metacarpals, Carpals, CMC (Carpometacarpal joint), and Wrist (showing Radius and Ulna). Red lines indicate various measurement points and segments.
+
+**Figure A.2.2.2-1: Segments and dimension points of the human hand**
+
+**Table A.2.2.2-1: Hand phantom dimensions**
+
+| Dimension Description                                      | Dim. (mm) | Dimension Description                | Dim. (mm) |
+|------------------------------------------------------------|-----------|--------------------------------------|-----------|
+| <b>Major Hand and Wrist Dimensions</b>                     |           | <b>Digit III Dimensions</b>          |           |
+| Wrist Width                                                | 61.4      | Distal Phalanx Length <sup>2</sup>   | 20.1      |
+| Wrist Circumference                                        | 162.9     | Middle Phalanx Length <sup>2</sup>   | 31.7      |
+| Hand Length, Center of Wrist to Tip of Digit III           | 186.5     | Proximal Phalanx Length <sup>2</sup> | 49.6      |
+| Hand Circumference                                         | 200.2     | Metacarpal Length <sup>3</sup>       | 66.2      |
+| Palm Length, Middle to Distal Palm Creases                 | 105.7     | Carpal Length <sup>3</sup>           | 17.4      |
+| Hand Width                                                 | 85.0      | DIP Width                            | 18.5      |
+| <b>Interdigital Crotch Dimensions</b>                      |           | PIP Width                            | 20.9      |
+| Between Digit II & III Crotch to Tip of Digit II           | 72.5      | DIP Circumference                    | 54.4      |
+| Between Digit II & III Crotch to Tip of Digit III          | 80.5      | PIP Circumference                    | 65.5      |
+| Between Digit III & IV Crotch to Tip of Digit IV           | 75.7      | <b>Digit IV Dimensions</b>           |           |
+| Between Digit IV & V Crotch to Tip of Digit V              | 61.5      | Distal Phalanx Length <sup>2</sup>   | 20.0      |
+| Between Digit I & II Crotch to Tip of Digit I <sup>1</sup> | 56.5      | Middle Phalanx Length <sup>2</sup>   | 30.8      |
+| <b>Digit I Dimensions</b>                                  |           | Proximal Phalanx Length <sup>2</sup> | 45.5      |
+| Distal Phalanx Length <sup>2</sup>                         | 29.4      | Metacarpal Length <sup>3</sup>       | 60.4      |
+| Proximal Phalanx Length <sup>2</sup>                       | 36.5      | Carpal Length <sup>3</sup>           | 19.4      |
+| Metacarpal Length <sup>2</sup>                             | 46.8      | DIP Width                            | 17.2      |
+| Carpal Length <sup>2</sup>                                 | 22.0      | PIP Width                            | 19.9      |
+| DIP Width                                                  | 22.3      | DIP Circumference                    | 50.3      |
+| DIP Circumference                                          | 67.7      | PIP Circumference                    | 61.2      |
+| <b>Digit II Dimensions</b>                                 |           | <b>Digit V Dimensions</b>            |           |
+| Distal Phalanx Length <sup>2</sup>                         | 18.1      | Distal Phalanx Length <sup>2</sup>   | 17.3      |
+| Middle Phalanx Length <sup>2</sup>                         | 26.7      | Middle Phalanx Length <sup>2</sup>   | 21.8      |
+| Proximal Phalanx Length <sup>2</sup>                       | 45.7      | Proximal Phalanx Length <sup>2</sup> | 38.0      |
+| Metacarpal Length <sup>3</sup>                             | 67.4      | Metacarpal Length <sup>3</sup>       | 56.6      |
+| Carpal Length <sup>3</sup>                                 | 20.6      | Carpal Length <sup>3</sup>           | 24.3      |
+| DIP Width                                                  | 18.7      | DIP Width                            | 16.1      |
+| PIP Width                                                  | 21.5      | PIP Width                            | 17.9      |
+| DIP Circumference                                          | 54.1      | DIP Circumference                    | 45.9      |
+| PIP Circumference                                          | 64.8      | PIP Circumference                    | 54.2      |
+
+### A.2.2.3 Dielectric properties
+
+Dielectric properties of dry palm human tissue are set as the target dielectric parameters for hand phantoms [19]. The properties are presented in Table A.2.2.3-1. It's important that the hand phantom has equivalent electrical properties to real human hand to ensure that the same near field effects are seen with the hand phantom as would be seen with real hand. Relative permittivity of hand phantoms shall be within  $\pm 15\%$  of the values listed in Table A.2.2.3-1. Conductivity of hand phantoms shall be within  $\pm 25\%$  of the values listed in Table A.2.2.3-1. Methods for measuring dielectric properties can be found e.g. in [22] [23].
+
+**Table A.2.2.3-1: Target dielectric properties of a hand phantom**
+
+| Frequency (MHz) | Er   | $\sigma$ (S/m) |
+|-----------------|------|----------------|
+| 300,00          | 37,1 | 0,36           |
+| 450,00          | 33,9 | 0,43           |
+| 835,00          | 30,3 | 0,59           |
+| 900,00          | 30   | 0,62           |
+| 1450,00         | 27,9 | 0,85           |
+| 1575,00         | 27,5 | 0,9            |
+| 1800,00         | 27   | 0,99           |
+| 1900,00         | 26,7 | 1,04           |
+| 1950,00         | 26,6 | 1,07           |
+| 2000,00         | 26,5 | 1,09           |
+| 2100,00         | 26,3 | 1,14           |
+| 2450,00         | 25,7 | 1,32           |
+| 3000,00         | 24,8 | 1,61           |
+| 4000,00         | 23,5 | 2,18           |
+| 5000,00         | 22,2 | 2,84           |
+| 5200,00         | 22   | 2,98           |
+| 5400,00         | 21,7 | 3,11           |
+| 5600,00         | 21,4 | 3,25           |
+| 5800,00         | 21,2 | 3,38           |
+| 6000,00         | 20,9 | 3,52           |
+
+### A.2.2.4 Hand phantom grips
+
+Hand phantom grips are based on human factor studies that were done to record how a phone of certain form factor was gripped by a large sample of people. Based on the grip study findings, three grip designs are chosen for 40- to 56-mm wide devices: one for mono-block devices used in a voice call, another for fold devices in a voice call, and a third for “data mode” grip, simulating for example web browsing. Figure A.2.2.4-1 shows mono-block and fold grips [20]. Grip studies showed that devices wider than 56 mm (generally PDA and touch screen devices) could be conveniently accommodated by a single grip to cover primary use cases, voice calls and data browsing [20].
+
+Each grip is used with a spacer that is designed for repeatable positioning of terminals to the grips. The material for the monoblock palm spacer shall be hollow with a wall thickness less than 2 mm and a dielectric constant of less than 5.0 and a loss tangent of less than 0.05 or it shall be solid with a dielectric constant of less than 1.3 and a loss tangent of less than 0.003. Touch fastener material may be used to affix the DUT to the palm spacer.
+
+Figures A.2.2.4-1 and A.2.2.4-2 below illustrate the right-handed and left-handed mono-block and fold grips, respectively.
+
+![Two 3D models of a right hand showing different grips for holding mobile devices.](15fe9d98813f20e61e8f2177ed1b84b4_img.jpg)
+
+Two 3D models of a right hand, rendered in a dark gray color. The hand on the left is shown in a grip where the thumb and index finger are extended, while the other three fingers are curled. The hand on the right is shown in a grip where the thumb and index finger are extended, and the other three fingers are also extended. These grips are defined for holding mono-block and fold UEs during voice calls.
+
+Two 3D models of a right hand showing different grips for holding mobile devices.
+
+**Figure A.2.2.4-1: Right-handed grips defined to hold mono-block and fold UEs during voice calls**
+
+![Two 3D models of a left hand showing different grips for holding mobile devices.](acd747438ff021665cd3613c06b661d4_img.jpg)
+
+Two 3D models of a left hand, rendered in a dark gray color. The hand on the left is shown in a grip where the thumb and index finger are extended, while the other three fingers are curled. The hand on the right is shown in a grip where the thumb and index finger are extended, and the other three fingers are also extended. These grips are defined for holding mono-block and fold UEs during voice calls.
+
+Two 3D models of a left hand showing different grips for holding mobile devices.
+
+**Figure A.2.2.4-2: Left-handed grips defined to hold mono-block and fold UEs during voice calls**
+
+Figures A.2.2.4-3 and A.2.2.4-4 below illustrate the right-handed and left-handed data browsing with narrow UEs and PDA grips, respectively.
+
+![Two 3D models of a right hand showing different grips for data browsing with narrow UEs and holding PDA type of devices.](74a97a8834e7fb1c7f60c03d53136b84_img.jpg)
+
+Two 3D models of a right hand, rendered in a dark gray color. The hand on the left is shown in a grip where the thumb and index finger are extended, while the other three fingers are curled. The hand on the right is shown in a grip where the thumb and index finger are extended, and the other three fingers are also extended. These grips are defined for data browsing with narrow UEs and for holding PDA type of devices.
+
+Two 3D models of a right hand showing different grips for data browsing with narrow UEs and holding PDA type of devices.
+
+**Figure A.2.2.4-3: Right-handed grip defined for data browsing with narrow UEs and grip for holding PDA type of devices**
+
+![Figure A.2.2.4-4: Two 3D rendered hand models. The left model shows a left hand in a 'narrow data browsing' grip, with fingers curled around a small object. The right model shows a right hand in a 'PDA type of device' grip, with fingers extended and thumb curled around a small object.](5df95034215ad869eca4339a0e7535d0_img.jpg)
+
+Figure A.2.2.4-4: Two 3D rendered hand models. The left model shows a left hand in a 'narrow data browsing' grip, with fingers curled around a small object. The right model shows a right hand in a 'PDA type of device' grip, with fingers extended and thumb curled around a small object.
+
+**Figure A.2.2.4-4: Left-handed grip defined for data browsing with narrow UEs and grip for holding PDA type of devices**
+
+CAD models in Table A.2.2.4-1 define exact finger locations and spacers for the specified grips. The files are available in a subfolder of the archive area for this specification.
+
+**Table A.2.2.4-1: CAD models for specified hand phantom grips and spacers**
+
+| Hand phantom grip               | Grip CAD file name      | Grip spacer file name     |
+|---------------------------------|-------------------------|---------------------------|
+| Right Mono-block grip           | 25914-b10_CAD_hand1.zip | 25914-b10_CAD_spacer1.zip |
+| Right Fold grip                 | 25914-b10_CAD_hand2.zip | 25914-b10_CAD_spacer2.zip |
+| Right Narrow data browsing grip | 25914-b10_CAD_hand3.zip | 25914-b10_CAD_spacer3.zip |
+| Right PDA grip                  | 25914-b10_CAD_hand4.zip | 25914-b10_CAD_spacer4.zip |
+| Left Mono-block grip            | 25914-b10_CAD_hand5.zip | 25914-b10_CAD_spacer5.zip |
+| Left Fold grip                  | 25914-b10_CAD_hand6.zip | 25914-b10_CAD_spacer6.zip |
+| Left Narrow data browsing grip  | 25914-b10_CAD_hand7.zip | 25914-b10_CAD_spacer7.zip |
+| Left PDA grip                   | 25914-b10_CAD_hand8.zip | 25914-b10_CAD_spacer8.zip |
+
+## A.2.2.5 Mechanical Requirements of Hand Phantoms
+
+The hand phantoms shall be constructed of a material that is sufficiently flexible to accommodate the range of devices specified in A.2.2.4. The material shall also be made sufficiently stiff that the hand grip remains constant under rotation.
+
+Adequate material stiffness of the hand phantom is necessary to maintain high repeatability of OTA measurements. The stiffness of the hand material shall be verified by measuring the deflection of the index finger of a moulded monoblock hand phantom under a given weight. Test procedure is following;
+
+1. Position the hand phantom such that the index finger is horizontal.
+2. Apply an indicator needle that extends horizontally  $55 \text{ mm} \pm 1 \text{ mm}$  beyond the tip of the index finger.
+3. Record the position of the indicator needle on a vertical scale.
+4. Apply  $20 \text{ g} \pm 0.2 \text{ g}$  of weight centred  $6 \text{ mm} \pm 0.5 \text{ mm}$  from the tip of the index finger towards the hand.
+5. Record the new position of the indicator needle on a vertical scale.
+
+The deflection of the index finger of the hand phantom shall be between 2 and 5 mm. Deflection less than 2 mm per 20 g weight indicates a material that is too rigid. Deflection greater than 5 mm per 20 g weight indicates a material that is too soft.
+
+![Figure A.2.2.5-1: Hand phantom stiffness test. A line drawing showing a hand holding a cylindrical device, with an arrow pointing to the index finger tip touching a vertical surface.](0e8a9481ac421f11f8cca21fecd5b151_img.jpg)
+
+Figure A.2.2.5-1: Hand phantom stiffness test. A line drawing showing a hand holding a cylindrical device, with an arrow pointing to the index finger tip touching a vertical surface.
+
+**Figure A.2.2.5-1: Hand phantom stiffness test**
+
+![Figure A.2.2.5-2: A weight container designed for a hand phantom stiffness test. A 3D rendering of a green, irregularly shaped container with a handle-like protrusion.](d740ca3c4110579e86de4400c75a06e5_img.jpg)
+
+Figure A.2.2.5-2: A weight container designed for a hand phantom stiffness test. A 3D rendering of a green, irregularly shaped container with a handle-like protrusion.
+
+**Figure A.2.2.5-2: A weight container designed for a hand phantom stiffness test**
+
+A weight container presented in Figure A.2.2.5-2 may be used in the stiffness test. It is assumed that other grips will have similar stiffness as the monoblock hand from the same material. Therefore, a stiffness test of the monoblock hand alone is considered sufficient.
+
+The characteristics of position of the hand phantom such that the index finger is horizontal are specified in Table A.2.2.5-1.
+
+**Table A.2.2.5-1: Characteristics of position of the hand phantom**
+
+| ID | Hand Grip Placement | Characteris |
+|----|---------------------|-------------|
+| 0  | Low                 | Shift Up    |
+| 1  | Medium              | No Shift    |
+| 2  | High                | Shift Down  |
+
+The characteristics of deflection of the index finger of the hand phantom are specified in Table A.2.2.5-2.
+
+**Table A.2.2.5-2: Characteristics of deflection of the index finger of the hand phantom**
+
+| ID | Deflection of Index Finger (df) Placement         | Characteristic |
+|----|---------------------------------------------------|----------------|
+| 0  | $df \leq 2 \text{ mm per } 20\text{g}$            | Rigid          |
+| 1  | $2\text{mm} < df \leq 5\text{mm per } 20\text{g}$ | Stable         |
+| 2  | $df > 5\text{mm per } 20\text{g}$                 | Soft           |
+
+### A.2.3 Laptop Ground Plane Phantom
+
+Laptop ground plane phantom is used for radiated performance measurements in case of plug-in DUT like USB dongles. The objective of the laptop ground plane phantom is to reproduce the effects of the ground plane for the antenna of the DUT while avoiding the variation of the measurements introduced by a real laptop.
+
+The laptop ground plane phantom, as showed in Figure A.2.3-1, is composed by the following parts:
+
+- A rectangular plane covered by a conductive film on the upper side with thickness of 4mm to emulate the keyboard and main body of the laptop;
+
+- A rectangular plane covered by the same conductive film on the upper side with thickness of 4mm to emulate the screen of laptop;
+- The conductive film on the two planes is connected. The angle between the two planes is 110 degrees. The material is FR-4 copper-clad sheet and the length and width of these two planes are 345mm and 238mm respectively;
+- A horizontal USB connector placed along the short end of the plane; the location of the port is at the right back corner, the distance between the central axis of the USB connector and the rear edge of plane is 45mm, the ground of the USB connector is welded on the conductive film of the plane. The detailed description of the structure is presented in Figure A.2.3-2;
+- A USB cable crossing the ground plane and connecting the USB connector to a real functional laptop; the USB cable should be equipped with a shielded metal film, and the portion of the cable that is hung in the air shall be covered with absorbing material or treated with quarter wave chokes. The part of the USB cable lying on the plane is covered by a conductive adhesive strip used for fixing the cable on the plane and for guaranteeing at the same time the superficial continuity of the conductive plane. The shielded conductive film of this part of the USB cable is connected to the conductive film of the plane and the covered strip to well ground the antenna. The length of the USB cable should be no more than 3 meters.
+
+![Diagram of the laptop ground plane phantom, DUT, and real functional laptop setup.](6e10326caf39add89e2f9358de953e4f_img.jpg)
+
+The diagram illustrates the experimental setup for testing a Device Under Test (DUT). It features a 'Laptop ground plane phantom' consisting of two rectangular planes joined at a 110-degree angle. Both planes are covered with a 'Conductive film'. A 'Conductive adhesive strip' is applied along the edge of the horizontal plane. A 'Choked USB cable, or covered with absorbing material' is connected to a 'USB connector' located at the rear corner of the horizontal plane. The cable is secured to the conductive film by the adhesive strip. The cable then connects to a 'Real functional laptop'. The DUT is shown as a small rectangular block connected to the USB connector. The thickness of the horizontal plane is indicated as 4mm.
+
+Diagram of the laptop ground plane phantom, DUT, and real functional laptop setup.
+
+**Figure A.2.3-1: The laptop ground plane phantom, the DUT and the real functional laptop**
+
+![Figure A.2.3-2: The structure and dimension of the laptop ground phantom. The figure shows three views: Front view, Side view, and Top view. The front view shows a rectangular shape. The side view shows a tilted display (110 degree) with a height of 238mm and a base thickness of 4mm. The top view shows the rear edge, a conductive adhesive strip (30mm wide), a USB connector, and a USB cable. The overall width is 345mm and the depth is 45mm.](69a9b36d36809dceaee1dd5b3471d06f_img.jpg)
+
+Figure A.2.3-2: The structure and dimension of the laptop ground phantom. The figure shows three views: Front view, Side view, and Top view. The front view shows a rectangular shape. The side view shows a tilted display (110 degree) with a height of 238mm and a base thickness of 4mm. The top view shows the rear edge, a conductive adhesive strip (30mm wide), a USB connector, and a USB cable. The overall width is 345mm and the depth is 45mm.
+
+**Figure A.2.3-2: The structure and dimension of the laptop ground phantom**
+
+The real functional laptop is laid on the floor of the anechoic chamber, supplies power to the DUT and controls the state of the DUT. Both the USB cable and the real functional laptop are properly setup in order to have a negligible impact on the measurements: the real functional laptop is fully wrapped up with anechoic absorbers.
+
+## A.2.4 Parameters for embedded devices
+
+### A.2.4.1 General
+
+The main objectives of this section are to define basic parameters required when performing TRP and TRS measurements on notebooks and tablets.
+
+### A.2.4.2 Notebook
+
+A notebook PC is a portable personal computer combining the computer, keyboard and display in one form factor. Typically the keyboard is built into the base and the display is hinged along the back edge of the base. The largest single dimension for a notebook is limited to 0.42 m.
+
+As notebooks are not body worn equipment nor recommended for use placed directly on the lap, the notebook shall be tested in a free space configuration without head and hand phantoms.
+
+When the notebook is placed in a measurement chamber the display shall be configured according to Table A.2.4.2-1.
+
+**Table A.2.4.2-1: Display Settings**
+
+| Parameter         | Value             | Note                                                                                         |
+|-------------------|-------------------|----------------------------------------------------------------------------------------------|
+| Display lid angle | 110 +/- 5 degrees | The lid angle is defined as the angle between the front of the display to the levelled base. |
+| LCD Backlight     | 50%               |                                                                                              |
+| Ambient sensor    | Disabled          |                                                                                              |
+
+A typical notebook PC is equipped with several radio access technologies. During the measurement the DUT shall be configured according to Table A.2.4.2-2.
+
+**Table A.2.4.2-2: Embedded radio transmitters**
+
+| Parameter          | Value    | Note                        |
+|--------------------|----------|-----------------------------|
+| WWAN               | Enabled  | This is the DUT transceiver |
+| Other transceivers | Disabled | UWB, WLAN, Bluetooth™       |
+
+The notebook power management shall be configured according to Table A.2.4.2-3.
+
+**Table A.2.4.2-3: Power management**
+
+| Parameter                            | Value            | Note |
+|--------------------------------------|------------------|------|
+| Screensaver                          | Disabled         |      |
+| Turn OFF display                     | Never            |      |
+| Turn OFF Hard drive                  | Never            |      |
+| System Hibernate                     | Never            |      |
+| System Standby                       | Never            |      |
+| Dynamic control of clock frequencies | Disabled         |      |
+| Power source                         | Standard battery |      |
+
+If the notebook is equipped with retractable antennas the device shall be tested with the antennas in a configuration recommended by the manufactures.
+
+### A.2.4.3 Tablet
+
+A tablet is a portable personal computer combining the computer and display in a single form factor. User input is accomplished via touch screen or a pen. The largest single dimension (i.e., length, width, height) for a tablet is limited to 0.42 m. Tablet devices may have different primary mechanical modes.
+
+Tablet shall be tested in a free space configuration without head and hand phantoms. If hand phantom grips become available for tablets, the testing configuration for tablets may be revisited. The centre of rotation shall be the three-dimensional geometric centre of the EUT, display facing free space.
+
+When a tablet is placed in a measurement chamber the display shall be configured according to Table A.2.4.3-1.
+
+**Table A.2.4.3-1: Display Settings**
+
+| Parameter            | Value    | Note |
+|----------------------|----------|------|
+| LCD Backlight        | 50%      |      |
+| Ambient light sensor | Disabled |      |
+
+A typical tablet is equipped with several radio access technologies. During the measurement the EUT shall be configured according to Table A.2.4.2-2.
+
+EUT shall be powered by battery and power management settings in Table A.2.4.2-3 shall be used.
+
+If a fixture is required to mount the EUT to the positioning system, the EUT holding fixture shall be made of a material with a dielectric constant of less than 5.0, and loss tangent less than 0.05. The fixture shall not extend beyond the footprint of the EUT by more than 20 mm and shall be no more than 20 mm in thickness. It is recommended, but not required, that a Styrofoam spacer would be used between the holding fixture and the EUT.
+
+## A.3 Anechoic chamber constraints
+
+### A.3.1 General
+
+The main objective of this section is to define basic parameters of the anechoic chamber suited for the Tx and Rx measurement of UMTS and E-UTRA UEs.
+
+The chamber should be equipped with an antenna positioner making possible to perform full 3-D measurements for both Tx and Rx radiated performance. Two main measurement set-ups are presented for this purpose:
+
+- A so-called spherical scanner system implies that the DUT is placed on a positioner that rotates in a horizontal plane. The probe antenna is rotated physically in the vertical plane. Alternatively, multiple probe antennas can be placed along an arch in vertical plane and electronically switched in order to get the full 3-D radiation/sensitivity pattern (see Figure A.3.1-1). Alternatively a multiple probe system, which has a set of probes located on the full spherical surface may be used [21]. In this case the DUT does not have to be rotated.
+- A dual axis system implies that the DUT is placed on a positioner that is able to rotate around two different axes. The signal is transmitted/received by a fixed probe (see Figure A.3.1-2). It is noted that many conventional two-
+
+axis systems (i.e. many commercially available systems built for a more general use) are built for the support of rather heavy test objects (with narrow antenna beam), which by their mechanical size may disturb the measurement of nearly omnidirectional antennas. Note that such systems are equipped with a positioner that may disturb the measurement of nearly omnidirectional antennas.
+
+![Two diagrams of spherical positioner systems. The left diagram shows a DUT (Device Under Test) on a rotating turntable with a single probe antenna on a curved track. The right diagram shows the same setup but with multiple probe antennas spaced along the track. Both diagrams include coordinate axes labeled phi (φ) and theta (θ).](39d598e27d6459d9e6ddfa3d2b0dbf6a_img.jpg)
+
+Two diagrams of spherical positioner systems. The left diagram shows a DUT (Device Under Test) on a rotating turntable with a single probe antenna on a curved track. The right diagram shows the same setup but with multiple probe antennas spaced along the track. Both diagrams include coordinate axes labeled phi (φ) and theta (θ).
+
+Figure A.3.1-1: Example of a spherical positioner system with a moving probe antenna (left), and with multiple probe antennas (right)
+
+![Diagram of a dual axis (roll-over-azimuth) positioner system inside an anechoic room. A BS simulator connected to a horn antenna is on the left. On the right, a DUT is mounted on a dual-axis rotation platform. The walls are lined with blue pyramidal wave absorbers. Coordinate axes labeled phi (φ) and theta (θ) are shown on the DUT.](4e69c7905b279b3264a2f0a4a9fcea4c_img.jpg)
+
+Diagram of a dual axis (roll-over-azimuth) positioner system inside an anechoic room. A BS simulator connected to a horn antenna is on the left. On the right, a DUT is mounted on a dual-axis rotation platform. The walls are lined with blue pyramidal wave absorbers. Coordinate axes labeled phi (φ) and theta (θ) are shown on the DUT.
+
+Figure A.3.2-2: Example of a dual axis (roll-over-azimuth) positioner system
+
+![Figure A.3.3-3: The coordinate system used in the measurements. The diagram shows a 3D Cartesian coordinate system with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down and to the left. A vector is shown originating from the origin, making an angle theta (θ) with the Z-axis and an angle phi (φ) with the X-axis. Two orthogonal polarization vectors, E_θ and E_φ, are shown at the tip of the vector, perpendicular to each other and to the direction of propagation.](3a31a89b46f6eed5da9738f05f81441a_img.jpg)
+
+Figure A.3.3-3: The coordinate system used in the measurements. The diagram shows a 3D Cartesian coordinate system with X, Y, and Z axes. The Z-axis is vertical, the Y-axis is horizontal to the right, and the X-axis points diagonally down and to the left. A vector is shown originating from the origin, making an angle theta (θ) with the Z-axis and an angle phi (φ) with the X-axis. Two orthogonal polarization vectors, E\_θ and E\_φ, are shown at the tip of the vector, perpendicular to each other and to the direction of propagation.
+
+**Figure A.3.3-3: The coordinate system used in the measurements**
+
+In both cases the measurement antenna should be able to measure two orthogonal linear polarizations (typically theta ( $\theta$ ) and phi ( $\phi$ ) polarizations).
+
+Note that for an anechoic chamber, horn antennas are usually used as probe antennas. There are two kinds of horn antennas: single-polarized and dual-polarized. The dual-polarized horn antenna has advantages of a major importance in comparison with the single-polarized. In fact, it is possible to measure two orthogonal polarizations without any movement of the probe, and this will:
+
+- Reduce the cable antenna uncertainty contribution
+- Improve the measurement stability
+- Reduce the time delay between the acquisitions of each polarized signal due to the electrical RF relay.
+
+If using single-polarized probe antenna, it is possible to perform the measurements by turning one linear polarized antenna by  $90^\circ$  for every measurement point. However, this technique has a major drawback: the cable of this antenna is subjected to numerous bendings and rotations, which brings some measurement instabilities. The various positions of the cable have an effect on the repeatability of measurements, and the stress applied to the cable can reduce its performance. The use of a "stress cable", or a rotary joint, connected to the main low-loss cable that is connected to the BTS simulator is recommended if using a single-polarized probe.
+
+## A.3.2 Quiet zone dimension
+
+Quiet zone has to be large enough to contain DUT attached to a phantom head and shoulders. The dimensions have to be slightly larger than the phantom dimension due to the fact that the rotation axes are not passing through the symmetry plane of the phantom, but through the phase centre of the DUT. Thus minimum radius of the quiet zone has to be 150mm, which is the approximate distance from a UE to the edge of the head and shoulders phantom while the phone is placed in an "intended use" position.
+
+## A.3.3 Minimum distance between the DUT and the measurement antenna
+
+For far-field measurements, the distance  $r$  between the DUT and the measurement antenna should be calculated by the following equation.
+
+where  $\lambda$  is the largest wavelength within the frequency band of interest and  $D$  the maximum extension of the radiating structure. Then the phase and amplitude uncertainty limits and the reactive near field limit are not exceeded. The influence of measurement distance is discussed in Annex E.
+
+## A.3.4 Reflectivity of the quiet zone
+
+Reflectivity of the quiet zone must be measured for frequencies used with method described in Annex G. Measured reflectivity level is used in uncertainty calculations.
+
+## A.3.5 Shielding effectiveness of the chamber
+
+In order to be able to measure sensitivity all external radiation has to be eliminated. Depending on the conditions at the test site in question, different values of shielding effectiveness of the measurement chamber might be required. The only general requirement on the shielding effectiveness of the chamber is that the measured level of external signals at the frequency of interest (UMTS, E-UTRA frequency band) has to be 10dB below sensitivity level of the UE. See Annex G for more details on shielding effectiveness validation.
+
+When specified in a test, the manufacturer shall declare the nominal value of a parameter, or whether an option is supported.
+
+---
+
+## A.4 Reverberation chamber constraints
+
+### A.4.1 General
+
+The main objective of this section is to define basic parameters of the reverberation chambers suited for the Tx and Rx measurement of UMTS, and E-UTRA UEs.
+
+The reverberation chambers have for a couple of decades been used for some types of EMC measurements. A reverberation chamber is a metal cavity that is sufficiently large to support many resonant modes, and it is provided with means to stir the modes. The measurements in the reverberation chamber are fast and repeatable, provided the chambers utilize efficient stirring methods. The following sections describe how the reverberation chamber can be used for measurements of TRP and TRS.
+
+### A.4.2 Positioning and mode stirring facilities
+
+The reverberation chamber shall be equipped with mode-stirring facilities in such a way that enough number of independent power samples can be achieved for the accuracy requirement stated in this standard to be fulfilled. Possible mode-stirring methods include platform stirring, polarization stirring and mechanical stirring with fan-type stirrers, irregular shaped rotational stirrers, or plate-type stirrers. Also, frequency stirring is possible if the type of measurement allows for a frequency-averaged value, but this is not necessary if the chamber is sufficiently large and well stirred.
+
+For the DUT positioning on head phantom or for the DUT positioning on laptop ground plane phantom, the DUT should be placed in such a way that a sufficient number of independent samples are obtained to fulfil the uncertainty requirements. For example, for chambers utilizing platform stirring the DUT should be placed on the edge of the turntable in order to maximize rotation of the DUT. In addition, the DUT must not be closer than 0.5 wavelengths to other electromagnetic reflective objects inside the chamber and 0.7 wavelengths to absorbing objects.
+
+For the DUT positioning on laptop ground plane phantom the real functional laptop is laid on the floor of the chamber, supplies power to the DUT and controls the state of the DUT. Both the USB cable and the real functional laptop are properly setup in order to have a negligible impact on the measurements: the real functional laptop is fully wrapped up with anechoic absorbers. The real functional laptop can be placed outside the chamber if the connection to the DUT can be maintained and if the communication interface between DUT and real functional laptop has negligible impact on the measurements.
+
+A schematic picture of the measurement setup is provided in Figure A.4.2-1.
+
+![Figure A.4.2-1: A schematic picture of the reverberation chamber measurement setup. The diagram shows a rectangular reverberation chamber containing a mode stirrer/tuner, a test unit, and a fixed measurement antenna. The fixed measurement antenna is connected to a base station simulator. A curved line represents the signal path, labeled 'Same path for up- and downlink'.](6d54943c64ae4af089cb9e98a78d0af7_img.jpg)
+
+Figure A.4.2-1: A schematic picture of the reverberation chamber measurement setup. The diagram shows a rectangular reverberation chamber containing a mode stirrer/tuner, a test unit, and a fixed measurement antenna. The fixed measurement antenna is connected to a base station simulator. A curved line represents the signal path, labeled 'Same path for up- and downlink'.
+
+**Figure A.4.2-1: A schematic picture of the reverberation chamber measurement setup**
+
+### A.4.3 Polarization imbalance and receiving antennas
+
+It is important that the statistical distribution of waves in the chamber corresponds to the chosen test environment. Present knowledge about reverberation chambers limits this to isotropic environments, i.e. the TRP and TRS parameters can be measured. Since the probability of each polarization is equal in the isotropic environment, a check of the polarization imbalance in the reverberation chamber must be done.
+
+The polarization imbalance can be obtained during the calibration measurement by measuring both when the calibration antenna is oriented for vertical polarization and when it is oriented for horizontal polarization. These two values shall differ by less than the specification in Table A.4.3-1. In order to obtain values for comparison with the results in the table, the reference levels shall be measured for both orientations of the calibration dipole at 8 different positions of the dipole inside the chamber. The average, standard deviation and maximum deviation shall be evaluated by comparing results for both polarizations over the whole set of 8 measurements. Alternatively, the levels for the two polarizations of the calibration antenna at 1 MHz intervals between 1900 MHz and 2200 MHz can be measured, and thereafter the average, standard deviation and maximum of the difference between the two sets of values over these frequency ranges are calculated.
+
+An effective way of avoiding polarization imbalance is to use polarization stirring, i.e. using three orthogonal linearly polarized receiving antennas. These three receiving antennas may be monopoles connected orthogonally to three different and orthogonal walls (including ceiling/floor) of the chamber. The three antennas are below referred to as the three fixed wall mounted antennas.
+
+**Table A.4.3-1: Specifications of differences of measured reference levels in each frequency band between using vertically and horizontally polarized calibration dipoles**
+
+|                    | Maximum tolerable value |
+|--------------------|-------------------------|
+| Average            | 0.2 dB                  |
+| Standard deviation | 0.5 dB                  |
+| Maximum            | 1.0 dB                  |
+
+### A.4.4 Measurement antennas
+
+It is important that the measurement antennas are configured in such a way that the statistical distribution of waves in the chamber in average corresponds to an isotropic environment.
+
+### A.4.5 Chamber size and characteristics
+
+The reverberation chamber shall have a volume large enough to support the number of modes needed for the stated accuracy at the lowest operating frequency. If the UE is moved around in the chamber during the measurement, the volume of the reverberation chamber can be reduced. Also, frequency stirring can be used to improve the accuracy. However, this will reduce the resolution of the results correspondingly.
+
+The reverberation chamber can be loaded with lossy objects in order to control the power delay profile in the chamber to some extent. However the reverberation chamber should not be loaded to such an extent that the mode statistics in the chamber are destroyed. It is important to keep the same amount of lossy objects in the chamber during calibration measurement and test measurement, in order not to change the average power transfer function between these two cases. Examples of lossy object are head and hand phantoms.
+
+Furthermore, the DUT must not be closer than 0.5 wavelengths to other electromagnetic reflective objects inside the chamber and 0.7 wavelengths to absorbing objects.
+
+#### A.4.6 Shielding effectiveness of the chamber
+
+The shielding effectiveness of the chamber shall be as large as needed for the interference from other sources not to influence the measured parameters. This means that the requirements of the shielding is specific to each test site and may vary accordingly.
+
+The recommended level of the shielding effectiveness is -100 dB from 800 MHz to 4 GHz. See Annex H for more details on shielding effectiveness validation.
+
+---
+
+### A.5 Anechoic chamber constraints for Radiated Performance of Multiple-antenna Receivers
+
+#### A.5.1 General
+
+An OTA method based on the use of an Anechoic RF Chamber is described consisting of a number of test antenna probes located in the chamber transmitting signals with temporal and spatial characteristics for testing multiple antenna devices.
+
+This clause describes the methodologies based on Anechoic RF Chamber, where a number of test antennas are located in different positions of the chamber, and the Device Under Test (DUT) is located at centre position. The DUT is tested over the air without RF cables.
+
+##### A.5.1.1 Multi-probe Anechoic Chamber
+
+An OTA method based on the use of an Anechoic RF Chamber is described consisting of a number of test antennas located in the chamber transmitting signals with temporal and spatial characteristics for testing multiple antenna devices. The method consists of a number of test antennas located in different positions of the chamber, and the device under test (DUT) is located at the centre position. The DUT is tested over the air without RF cables.
+
+The Anechoic chamber techniques creates a realistic geometric based spatio-temporal-polarimetric radio channel for testing MIMO performance using Geometric based stochastic channel models as defined in Annex M.1.
+
+The components of the solution include:
+
+- Anechoic Chamber
+- System Simulator (SS)
+- N channel RF emulator, with OTA Channel Generation Features
+- N linearly polarized antenna elements configured V, H or co-located V&H or slant X polarizations
+- K azimuthally separated antenna positions with predefined angles at radius R
+- Channel model definition for each test case
+
+An illustration of an anechoic chamber is shown in Figure A.5.1.1-1 below.
+
+![Figure A.5.1.1-1: N-element Anechoic Chamber approach. A 3D perspective view of an anechoic chamber with a Device Under Test (DUT) in the center. The DUT is a small cylinder. Several vertical lines with 'x' marks represent the positions of N elements (antennas) arranged around the DUT. The chamber walls are lined with absorbing tiles, and cabling is not shown.](c90c97412b6b575e746e8ac7ed5ce791_img.jpg)
+
+Figure A.5.1.1-1: N-element Anechoic Chamber approach. A 3D perspective view of an anechoic chamber with a Device Under Test (DUT) in the center. The DUT is a small cylinder. Several vertical lines with 'x' marks represent the positions of N elements (antennas) arranged around the DUT. The chamber walls are lined with absorbing tiles, and cabling is not shown.
+
+Figure A.5.1.1-1: N-element Anechoic Chamber approach (Absorbing tiles and cabling not shown)
+
+![Figure A.5.1.1-2: OTA system level block diagram. A block diagram showing the signal flow for OTA testing. A Source Station (SS) generates an M-branch MIMO signal. This signal is input to an MxN MIMO Channel Emulator. The emulator outputs N signals to an Anechoic Chamber. Inside the chamber, there are multiple antenna positions, each marked with a '+' sign. A 'Return Path' is shown from the chamber back to the SS.](04238bd6d89845c9012e10d19d0e2b1f_img.jpg)
+
+Figure A.5.1.1-2: OTA system level block diagram. A block diagram showing the signal flow for OTA testing. A Source Station (SS) generates an M-branch MIMO signal. This signal is input to an MxN MIMO Channel Emulator. The emulator outputs N signals to an Anechoic Chamber. Inside the chamber, there are multiple antenna positions, each marked with a '+' sign. A 'Return Path' is shown from the chamber back to the SS.
+
+Figure A.5.1.1-2: OTA system level block diagram
+
+A system level block diagram is shown in Figure A.5.1.1-2, which includes the SS to generate the M branch MIMO signal, and an RF Channel Emulator with an OTA Channel Generation Feature to properly correlate, fade, scale, delay, and distribute the signal to each test probe in the chamber. For the selected environmental conditions modelled by the SCME UMa and UMi channel models, the minimum setup configuration can be described as below:
+
+Table A.5.1.1-1: Example of a minimum setup for Boundary Array implementations using the Anechoic Chamber Methodology
+
+|                                     | Full Ring         | Single Cluster                            |
+|-------------------------------------|-------------------|-------------------------------------------|
+| Minimum number of antenna positions | 8                 | 3                                         |
+| Antenna spacing                     | 45°               | Determined on the setup                   |
+| Applicable channel model            | SCME UMa/SCME UMi | Single Cluster UMa and Single Cluster UMi |
+
+The full SCME or Multi-Cluster channel models are defined in Annex M.1. The Single-Cluster model, which is not part of the set of channel models validated in clause 8, would be based on the channel models defined in Annex M.1 with a set of dithered AoAs around zero degrees.
+
+#### A.5.1.1.1 Concept and configuration
+
+For MIMO OTA modelling the geometric channel models are mapped into the fading emulator, converting the geometric channel models into the emulator tap coefficients. This process is illustrated in Figure A.5.1.1-1.
+
+![Figure A.5.1.1.1-1: Modelling process flowchart.](126e772862105e7d64e4ef3f85a16840_img.jpg)
+
+```
+
+    graph LR
+        subgraph Software [Software (Matlab) Implementation]
+            GCM[Geometric Channel Model  
+SCM/SCME/WINNER+/  
+IMT-Advanced]
+        end
+        Software --> OTA[OTA modelling tool  
+(mapping software)]
+        OTA --> FE[Fading emulator]
+        FE --> OC((OTA  
+Chamber))
+    
+```
+
+Figure A.5.1.1.1-1: Modelling process flowchart.
+
+**Figure A.5.1.1.1-1: Modelling process**
+
+The setup of OTA chamber antennas with eight antenna positions is depicted in Figure A.5.1.1.1-2. The DUT is at the centre, and the antennas are in a circle around the DUT with uniform spacing (e.g.  $45^\circ$  with 16 elements arranged in 8 positions, where each position contains a vertically and horizontally polarized antenna pair). Denoting directions of  $K$  OTA antennas with  $\theta_k$ ,  $k = 1 \dots K$ , and antenna spacing in the angle domain with  $\Delta\theta$ . Each antenna is connected to a single fading emulator output port. In the figure, for example, antenna  $A_{1V}$  denotes the first OTA antenna position and Vertically (V) polarized element,  $A_{8H}$  denotes the eight OTA antenna position and horizontally (H) polarized element, etc.
+
+![Figure A.5.1.1.1-2: OTA chamber antenna setup diagram showing 8 dual-polarized antenna positions arranged in a circle around a central DUT. Each position is marked with a cross or plus sign representing vertical (V) and horizontal (H) elements, labeled A1V/A1H through A8V/A8H. The angular spacing between positions is labeled Δθ.](38b35511a4152c6ac1260c489ce24c88_img.jpg)
+
+Figure A.5.1.1.1-2: OTA chamber antenna setup diagram showing 8 dual-polarized antenna positions arranged in a circle around a central DUT. Each position is marked with a cross or plus sign representing vertical (V) and horizontal (H) elements, labeled A1V/A1H through A8V/A8H. The angular spacing between positions is labeled Δθ.
+
+**Figure A.5.1.1.1-2: OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas**
+
+NOTE: In the drawing the V-polarized elements are actually orthogonal to the paper (azimuth plane)
+
+## A.5.1.2 Radiated Two-Stage
+
+The principle of two-stage MIMO OTA method is based on the assumption that the DUT far-field antenna radiation pattern will contain all the necessary information for evaluation of the DUT's antenna's performance like radiation power, efficiency and correlation and that with channel model approaches, the influence of antenna radiation pattern can be correctly incorporated into the channel model. Thus the method will first measure the DUT's MIMO antenna patterns and then convolve the measured antenna patterns with the chosen MIMO OTA channel models for real-time emulation. The resulting test signal generated by the channel emulator and coupled back into the DUT receivers represents the signal that the DUT receivers would have seen if the DUT had been placed in the desired radiated field.
+
+Thus an ideal implementation of the two-stage method provides the same results as an ideal implementation of the boundary antenna array method.
+
+The two-stage method can be used to measure the following figures of merit:
+
+- 1) Throughput
+- 2) TRP and TRS
+- 3) CQI, BLER
+- 4) Antenna efficiency and MEG
+- 5) Antenna correlation, MIMO channel capacity.
+
+In order to accurately measure the antenna pattern of the intact device, the DUT chipset needs to support received amplitude and relative phase measurements of the antennas. The validity of antenna pattern measurement is predicated on the assumption that for the frequency being tested, the DUT antenna pattern is static. Devices that can alter their antenna pattern in real time as a function of the radiated environment is not supported. The method of coupling the base station emulator and DUT uses a specially calibrated radiated connection (radiated two-stage or RTS method) to do the test on throughput, etc., to test how the MIMO antennas will influence the performance. The conducted method of coupling is straightforward but does not capture the impact of radiated leakage from the DUT transmit antennas to the DUT receive antennas, thus in its current form without additional interference estimation the conducted method of coupling in the second stage is not proposed for use in conformance testing. Its description is included for historical completeness of the development of the two-stage method. The radiated method of coupling in the second stage does fully capture radiated leakage and is the method defined for conformance testing.
+
+#### A.5.1.2.1 Concept and configuration
+
+The assumption of the two-stage MIMO OTA method is that the measured far field antenna pattern of the DUT's multiple antennas can fully capture the mutual coupling of the multiple antenna arrays and their influence on radiated performance.
+
+Thus to do the two-stage MIMO OTA test, the antenna patterns of the antenna array needs to be measured accurately in the first stage. In order to accurately measure the antenna pattern of the intact device, the chipset needs to support amplitude and relative phase measurements of the antennas. To achieve this, two new UE measurements have been defined called Reference Signal Antenna Power (RSAP) and Reference Signal Relative Antenna Phase (RSARP). These measurements are defined in TS 36.509 [34].
+
+**Stage 1:** The measurement of the DUT's multiple antennas takes place in a traditional anechoic chamber set up as described in Annex A.3, where the DUT is put into the chamber and each antenna element's complex far zone pattern is measured using the RSAP and RSARP measurements defined in TR 36.509 [34]. The influence of human body loss can also be measured by attaching the DUT to a SAM head and or hand phantom when doing the antenna pattern measurements. The characteristics of the SAM phantom are specified in Annex A.2. The chamber is equipped with a positioner, that makes it possible to perform full 3-D far zone pattern measurements for both Tx and Rx radiated performance. As specified in A.3, the measurement antenna shall be able to measure two orthogonal polarizations (typically linear theta ( $\theta$ ) and phi ( $\phi$ ) polarizations as shown in Figure A.5.1.2.1-1).
+
+![Figure A.5.1.2.1-1: The coordinate system used in the measurements. The diagram shows a Device Under Test (DUT) mounted on a rotating turntable. A probe antenna is positioned to the right of the DUT. The coordinate system is defined by a vertical dashed line passing through the center of the DUT. The angle <math>\phi</math> is measured from the vertical dashed line to the DUT's antenna. The angle <math>\theta</math> is measured from the horizontal dashed line to the probe antenna.](1c578156ee49622ffbdc6b1be40d671c_img.jpg)
+
+Figure A.5.1.2.1-1: The coordinate system used in the measurements. The diagram shows a Device Under Test (DUT) mounted on a rotating turntable. A probe antenna is positioned to the right of the DUT. The coordinate system is defined by a vertical dashed line passing through the center of the DUT. The angle  $\phi$  is measured from the vertical dashed line to the DUT's antenna. The angle  $\theta$  is measured from the horizontal dashed line to the probe antenna.
+
+**Figure A.5.1.2.1-1: The coordinate system used in the measurements**
+
+**Stage 2:** Convolve the antenna patterns measured in stage 1 with the chosen MIMO channel model, using a channel emulator and then use the resulting signal to perform the OTA throughput test. The signal is coupled into the DUT using a radiated connection.
+
+The radiated two-stage (RTS) method is illustrated in Figure A.5.1.2.1-2. The BS emulator is connected to the MIMO channel emulator and then to the DUT using a calibrated radiated connection in an anechoic environment. This coupling technique exploits the Eigen modes of the transmission channel in the anechoic chamber to provide isolated radiated connections between the probe antennas and each DUT receiver after the DUT antenna.
+
+To convolve the DUT antenna patterns with MIMO channel model.
+
+- a) Apply antenna patterns to correlation-based channel models. With a correlation matrix calculation method for arbitrary antenna patterns under multipath channel conditions, the correlation matrix and the antenna imbalance can be calculated and then emulated by the channel emulator.
+
+![Figure A.5.1.2.1-2: Radiated two-stage (RTS) test methodology for MIMO OTA test. The diagram shows a Base Station emulator connected to a Channel emulator. The Channel emulator has two outputs, Polar V and Polar H, which are connected to two probe antennas inside an Anechoic Chamber. The probe antennas are co-located and radiate signals towards a User Equipment (UE) inside the chamber. Dashed lines represent the radiated connections from the probe antennas to the UE.](b8d1d78473c7e0df5d8059f40629021a_img.jpg)
+
+Figure A.5.1.2.1-2: Radiated two-stage (RTS) test methodology for MIMO OTA test. The diagram shows a Base Station emulator connected to a Channel emulator. The Channel emulator has two outputs, Polar V and Polar H, which are connected to two probe antennas inside an Anechoic Chamber. The probe antennas are co-located and radiate signals towards a User Equipment (UE) inside the chamber. Dashed lines represent the radiated connections from the probe antennas to the UE.
+
+**Figure A.5.1.2.1-2: Radiated two-stage (RTS) test methodology for MIMO OTA test**
+
+Figure A.5.1.2.1-2 shows the radiated coupling method for the second stage. Two probe antennas with polarization V and H are co-located in the anechoic chamber. Note, unlike in the first stage where the V and H probes are used at different times, in the second stage both V and H probes are used simultaneously. An example implementation of this would be the dual polarized configuration described in Annex A.3. Due to the propagation channel in the chamber,
+
+signals transmitted from each probe antenna are received by both DUT antennas. However, by precoding the transmitted signals using spatial multiplexing techniques it is possible by calculating the radiated channel matrix and by applying its inverse to the transmitted signals, to create an identity matrix allowing the transmitted signals to be received independently at each DUT receiver after the DUT antenna.
+
+The establishment of the radiated connection is explained as follows. Assume  $x_1$  and  $x_2$  are the transmitted signals from the base station emulator, after applying the desired channel model and convolution with the complex antenna pattern we get:
+
+$$f(x_1) \text{ and } f(x_2).$$
+
+The radiated channel matrix between the probe antennas and the DUT antennas is
+
+$$= \begin{pmatrix} h_{11} & h_{12} \\ h_{21} & h_{22} \end{pmatrix}.$$
+
+If the channel emulator applies the inverse of the radiated channel matrix  $H^{-1} = \begin{pmatrix} \alpha & \beta \\ \gamma & \delta \end{pmatrix}$  to  $f(x_1)$  and  $f(x_2)$ , the signal received after the DUT antennas is same as if the channel emulator were directly connected to equivalent antenna connectors:
+
+$$\begin{pmatrix} y_1 \\ y_2 \end{pmatrix} = \begin{pmatrix} h_{11} & h_{12} \\ h_{21} & h_{22} \end{pmatrix} \begin{pmatrix} \alpha & \beta \\ \gamma & \delta \end{pmatrix} \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix} = \begin{pmatrix} 1 & 0 \\ 0 & 1 \end{pmatrix} \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix} = \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix}$$
+
+The above example of RTS using two probe antennas is applicable to UE with two Rx antennas. For UE with  $> 2$  Rx antennas, the RTS method is FFS.
+
+## A.5.2 Testing environment conditions
+
+This annex lists the testing environment conditions for all DUT types relevant to testing of radiated performance of multiple-antenna receivers. The use cases (positioning) discussed here are applicable for all methodologies, however the orientation and rotations described may be applicable for some methodologies only, and not for some other methodologies.
+
+Table A.5.2-1 below lists the testing environment conditions along with a diagram and applicable references. The reference coordinate system and orientation of devices in that coordinate system is shown in Figure A.5.2-1 below that includes the mechanical alignment of a phone. For tablets the home button, charging connector and similar components can be used to define top and bottom. For laptops the definitions specified in 3GPP TR 25.914 [3] (and repeated here in Table A.5.2-1) are used. In the case of methodologies utilizing a spatial channel model in Figure A.5.2-1, the X axis points towards the channel model reference. For example in the case of an anechoic chamber utilizing 2D antenna array in the azimuth plane (XY plane from Figure A.5.2-1) this is the direction of the first probe at 0 degrees.
+
+![Figure A.5.2-1: Reference coordinate system and reference device orientation. The diagram shows a smartphone in a 3D coordinate system. The Z-axis is vertical, pointing up, labeled 'Length of the phone' and 'Top of the phone'. The -Z axis points down, labeled 'Bottom of Phone'. The Y-axis is horizontal, pointing right, labeled 'Width of the phone'. The -Y axis points left. The X-axis is diagonal, pointing down-left, labeled 'Front of Phone' and 'Screen looks this way'. The -X axis is diagonal, pointing up-right, labeled 'Thickness of the phone'. The phone is shown as a rectangle with a smaller rectangle inside representing the screen.](b48930dacaf1c87ed6bb9a53c27c20d5_img.jpg)
+
+Figure A.5.2-1: Reference coordinate system and reference device orientation. The diagram shows a smartphone in a 3D coordinate system. The Z-axis is vertical, pointing up, labeled 'Length of the phone' and 'Top of the phone'. The -Z axis points down, labeled 'Bottom of Phone'. The Y-axis is horizontal, pointing right, labeled 'Width of the phone'. The -Y axis points left. The X-axis is diagonal, pointing down-left, labeled 'Front of Phone' and 'Screen looks this way'. The -X axis is diagonal, pointing up-right, labeled 'Thickness of the phone'. The phone is shown as a rectangle with a smaller rectangle inside representing the screen.
+
+**Figure A.5.2-1: Reference coordinate system and reference device orientation**
+
+First the terminology used below is defined here. Where possible consistency with [3], [30], [31] and [32] is sought.
+
+**Use Case (Position):** the use case (position) indicates how the DUT is related to its environment. This includes the following example use cases: free space, beside head, beside head and hand, hand only, etc. Note that formerly this has been referred to as position in [6] as well as in [32]. Since to date only isotropic metrics have been used (TRP/TRS) the definition of positioning the device for a certain use case has been equivalent to orienting it relative to the environment. With the introduction of spatial channel models, the positioning for a specific use case has to be separated from the actual orientation relative to the spatial incoming signals. For some methodologies not utilizing spatial channel models this distinction might not be necessary.
+
+**Orientation:** The orientation of the device in three dimensional space is defined using the three Euler angles –  $\Psi$ -yaw;  $\Theta$ -pitch;  $\Phi$ -roll as defined in [30] and [31] and linked to the reference coordinate systems and reference orientation from Figure A.5.2-1. Note that for most use cases practical considerations of how to position the DUT together with the phantom may determine the DUT orientation.
+
+**Rotation:** Once positioned for a specific use case and oriented within the reference coordinate system, the DUT and phantom are rotated within the test zone to measure the performance under various spatial channel illuminations. The rotation is defined with the same Euler angles but expressed as vectors of equal size. An example is given below:
+
+**EXAMPLE:** Consider a DUT measured in an anechoic chamber [29].  
+To measure the free space use case in the YZ plane (see Table A.5.2-1) for example at every 30 degrees the rotation vectors would be as follows:
+
+- $\Psi = [0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0]$  - a vector of 12 zeros indicating no rotation from the reference position for any phi value below
+- $\Theta = [-90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90]$  – a vector of 12 values equal to -90 indicating a constant pitch of -90 degrees for all phi values below
+- $\Phi = [0\ 30\ 60\ 90\ 120\ 150\ 180\ 210\ 240\ 270\ 300\ 330]$  – a vector of 12 distinct rotations from the reference position representing a rotation along the azimuth plane with a step of 30 degrees.
+
+These vectors unambiguously define that the DUT is to be oriented with the screen up and rotated in azimuth every 30 degrees. The principal antenna pattern cuts (XY plane, XZ plane, and YZ plane) are defined in [30]. The XY plane cut corresponds to the absolute throughput testing condition applied to the CTIA reference antennas for the inter-lab inter-technique activity. The XZ plane and YZ plane cuts are shown for completeness and are not required for the absolute data throughput framework. The YZ plane cut corresponds to a device positioned with its screen up in a USB/WLAN tethering scenario and may be a useful testing point for handset devices expected to achieve performance metrics under such usage conditions.
+
+**Table A.5.2-1: Summary of possible testing environment conditions for devices supporting DL MIMO data reception**
+
+| DUT type and dimensions                  | Testing condition                                               | DUT orientation angles                | Diagram                                                                                                                                                                                                                                                                                                                    |
+|------------------------------------------|-----------------------------------------------------------------|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Handset, tablet, CTIA reference antennas | XY plane or P0                                                  | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$  | <img alt="Diagram of a handset/tablet in the XY plane (P0 orientation). The device is upright, with its screen facing the Z-axis. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 277 1246 539" src="4842ec5b5670793e4458e671372f1764_img.jpg"/>             |
+| Handset, tablet, CTIA reference antennas | XZ plane or L0                                                  | $\Psi=90;$<br>$\Theta=0;$<br>$\Phi=0$ | <img alt="Diagram of a handset/tablet in the XZ plane (L0 orientation). The device is lying flat, with its screen facing the X-axis. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 566 1246 828" src="72a946916e42493c2568252c21ba02c6_img.jpg"/>          |
+| Handset, tablet, CTIA reference antennas | Free space data mode screen up (FS DMSU) or YZ plane or Face Up | $\Psi=0;$<br>$\Theta=90;$<br>$\Phi=0$ | <img alt="Diagram of a handset/tablet in the YZ plane (Face Up orientation). The device is lying flat, with its screen facing the Y-axis. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 855 1246 1117" src="c27721d296aa2f83230446e4d4ddc766_img.jpg"/>    |
+| Handset, tablet                          | Face Down                                                       | $\Psi=0;$<br>$\Theta=90;$<br>$\Phi=0$ | <img alt="Diagram of a handset/tablet in the Face Down orientation. The device is lying flat, with its screen facing the -Y axis. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 1144 1246 1406" src="8732d25aaca63ddbc0eb0f684de815e2_img.jpg"/>           |
+| Handset, tablet                          | Free space data mode portrait (FS DMP)                          | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$ | <img alt="Diagram of a handset/tablet in the Free space data mode portrait (FS DMP) orientation. The device is tilted at a 45-degree angle. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 1433 1246 1695" src="dee129640d21ff8f138d0bb906c2d7dc_img.jpg"/> |
+| Handset, tablet                          | Free space portrait tilt down                                   | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$ | <img alt="Diagram of a handset/tablet in the Free space portrait tilt down orientation. The device is tilted at a 45-degree angle. The coordinate system shows X, Y, and Z axes. Pitch is labeled as Θ, Yaw as Ψ, and Roll as Φ." data-bbox="954 1722 1246 1984" src="4619b5926b94319fabe72a41d1c70e41_img.jpg"/>          |
+
+|                                |                                                               |                                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+|--------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Handset, tablet                | Free space data mode landscape (FS DML)                       | $\Psi=90;$<br>$\Theta=45;$<br>$\Phi=0$ – left tilt                                                           | <img alt="Diagram showing a handset in landscape orientation with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="949 190 1252 459" src="b86a2d07eff8e1b76f6eb4a74c3559e9_img.jpg"/>                                                                                                                                                                                                                                                               |
+| Handset, tablet                | Free space landscape tilt down                                | $\Psi=90;$<br>$\Theta=45;$<br>$\Phi=0$ – left tilt                                                           | <img alt="Diagram showing a handset in landscape orientation tilted down, with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="949 481 1252 750" src="334cc62d4f043284759925265622d274_img.jpg"/>                                                                                                                                                                                                                                                  |
+| Handset, width < 56mm          | Left/right hand narrow phantom data mode portrait (LH/RH DMP) | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$                                                                        | <img alt="Diagram showing a hand holding a handset in portrait orientation, with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="917 761 1284 1131" src="453f919ec7eafd7de9131995c5b575df_img.jpg"/>                                                                                                                                                                                                                                               |
+| Handset, 56 mm < width < 72 mm | Left/right hand PDA phantom data mode portrait (LH/RH DMP)    | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$                                                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Handset width < 56 mm          | Beside head and hand right/left (BHHR/BHHL)                   | $\Psi=60;$<br>$\Theta=6;$<br>$\Phi=-90$ – right side<br>$\Psi=-60;$<br>$\Theta=-6;$<br>$\Phi=90$ – left side | <img alt="Diagram showing a hand holding a handset next to a yellow head phantom, with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="901 1176 1300 1556" src="2bec737f6829b7e932b3c2b4cbcc1cb6_img.jpg"/>                                                                                                                                                                                                                                        |
+| Handset 56 < width < 72 mm     | Beside head and hand right/left (BHHR/BHHL)                   | $\Psi=60;$<br>$\Theta=6;$<br>$\Phi=-90$ – right side<br>$\Psi=-60;$<br>$\Theta=-6;$<br>$\Phi=90$ – left side |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| LME                            | Laptop ground plane phantom                                   | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$                                                                         | <img alt="Diagram of a laptop ground plane phantom setup. It shows a laptop with a conductive film, a conductive adhesive strip, a USB connector, and a DUT. A 110 degree angle is indicated. Labels include: Laptop ground plane phantom, 110 degree, Conductive film, Conductive adhesive strip, Choked USB cable or covered with absorbing material, Real functional laptop, DUT, USB connector." data-bbox="885 1601 1316 1825" src="ab64fc3a5efc3f8eeefbea4dad1697ea_img.jpg"/> |
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |          |                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| LEE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | XY plane | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$ | <img alt="Diagram showing two views of a laptop model for LEE orientation. The 'Side View' on the left shows the laptop base on the X-axis and the screen tilted back at a 110-degree angle from the base. The 'Front View' on the right shows the laptop screen centered on the Y-axis. Coordinate axes X, Y, and Z are indicated, with Z being vertical." data-bbox="869 190 1324 436" src="6b09ea79b2359d93ef696a0aff7095c4_img.jpg"/> |
+| <p><b>NOTE 1:</b> The orientation angles given in the table define a set of use cases and orientations relative to the spatial channel model. The rotation angles to be used for measurements are FFS. Methodologies not utilizing spatial channel models might not need to define any rotations but are expected to measure for the given use cases.</p> <p><b>NOTE 2:</b> The CTIA reference antennas have been defined for inter-lab inter-technique testing for the purposes of comparing MIMO OTA methodologies.</p> <p><b>NOTE 3:</b> For DMP, other pitch positions can be considered FFS.</p> <p><b>NOTE 4:</b> The absolute throughput usage mode is defined only within the framework of the CTIA reference antennas and is used for comparison of results within/across MIMO OTA methodologies.</p> <p><b>NOTE 5:</b> Screen up flat positioning reference corresponds to a possible USB/WLAN tethering case, details of implementing this DUT orientation condition such as additional cabling, etc., are FFS.</p> <p><b>NOTE 6:</b> Left/right/both hand phantoms for the DML usage scenario are not currently defined in 3GPP; until these phantom designs become available, is possible to only define a DML usage scenario in free space.</p> <p><b>NOTE 7:</b> For a symmetric 2D coverage of testing points in azimuth, DML left and right tilts are expected to produce identical results in free space. Once phantom designs become available, we expect the interaction of the phantom with the antennas to be dependent on the tilt.</p> <p><b>NOTE 8:</b> The 110 degree angle of the notebook screen opening is a standard reference for all measurements of antennas embedded in notebooks; as a result, the LEE measurement in free space is the principal XY plane cut with respect to this reference.</p> <p><b>NOTE 9:</b> The orientation angles for the talk mode position are only approximate. The phone positioning is defined as in [3] and in [32] relative to the SAM phantom.</p> |          |                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+The Data Mode Portrait (DMP) conditions are defined in TR 25.914 [3], and are included in this table for completeness. The Data Mode Landscape (DML) testing conditions are not currently defined in any standard testing methodology but benefit from a thorough treatment in academic literature [31]. This testing condition considers free space for all handset sizes until a DML phantom design becomes available, at which time the testing condition will be revisited.
+
+The Laptop Mounted Equipment (LME) and Laptop Embedded Equipment (LEE) testing conditions are well defined in TR 25.914 [3] and constitute an XY plane cut measurement, given the proper orientation of the lid of the laptop ground plane phantom (in the case of LME) or of the laptop itself (in the case of LEE).
+
+Given a 2D ring of symmetrically distributed probes [29]:
+
+- The XZ plane is similar to the DML mode except for the additional 45 degrees pitch in the DML
+- For the phantom case the tilt of the DML case is very relevant since the interaction of the phantoms with the antennas will depend on it – see Figure A.5.2-2.
+
+![Diagram showing three views of a phone in landscape mode. The left view shows 'Landscape mode, Left tilt' with a hand on the left side and an angle Psi = +90. The middle view shows 'Straight up position' with 'Front of Phone' and 'Bottom of Phone' labels. The right view shows 'Landscape mode, Right tilt' with a hand on the right side and an angle Psi = -90. Coordinate axes X, Y, and Z are shown for each view. Other labels include 'Length of the phone' and 'Thickness of the phone'.](deaac997fd7ecee678c1d3be47d15ad7_img.jpg)
+
+Diagram showing three views of a phone in landscape mode. The left view shows 'Landscape mode, Left tilt' with a hand on the left side and an angle Psi = +90. The middle view shows 'Straight up position' with 'Front of Phone' and 'Bottom of Phone' labels. The right view shows 'Landscape mode, Right tilt' with a hand on the right side and an angle Psi = -90. Coordinate axes X, Y, and Z are shown for each view. Other labels include 'Length of the phone' and 'Thickness of the phone'.
+
+Figure A.5.2-2: Left and Right tilts for landscape mode with left hand phantom shown to interact differently with the antennas depending on the tilt
+
+### A.5.2.1 MPAC Positioning Guidelines
+
+In order for the anechoic chamber multi probe system to emulate the intended propagation statistics within the region of space incident on the DUT antennas, two concepts determine the associated antenna spacing and positioning guidelines. The maximum antenna spacing in the DUT must be within the limit determined by the anechoic chamber multi probe system’s ability to emulate the spatial correlation function, and the power stability of the field incident on the DUT antennas must be verified.
+
+![Two circular diagrams, (a) and (b), illustrating DUT antenna spacing. Diagram (a) shows 'EUT placement (centered on axis of rotation)' within a 'Potential region of uniform power delivered by MIMO system(unverified)'. Diagram (b) shows 'EUT placement (not centered on axis of rotation)' where the device is partially outside the uniform power region. Labels include 'MPAC probe ring', 'Maximum allowed antenna separation for emulation of spatial correlation function', and 'Region of uniform power delivered by MIMO system (verified)'.](ab9daa86203d0b410e0a01f588a2f9ca_img.jpg)
+
+Two circular diagrams, (a) and (b), illustrating DUT antenna spacing. Diagram (a) shows 'EUT placement (centered on axis of rotation)' within a 'Potential region of uniform power delivered by MIMO system(unverified)'. Diagram (b) shows 'EUT placement (not centered on axis of rotation)' where the device is partially outside the uniform power region. Labels include 'MPAC probe ring', 'Maximum allowed antenna separation for emulation of spatial correlation function', and 'Region of uniform power delivered by MIMO system (verified)'.
+
+Figure A.5.2.1-1: Illustration of DUT antenna spacing and positioning guidelines; a) guideline in this specification, b) example with DUT meeting the maximum allowed antenna separation but not within the verified power stability region
+
+As the channel model validation procedures for spatial correlation as defined in [29] are to be performed at the downlink centre frequency in 3GPP TS 36.508 [10], the maximum antenna spacing in the DUT shall be defined by the wavelength per operating band centre frequency of the middle channel of the downlink at the band under test. A verification of power stability can be derived from the spatial correlation verification results in [29]. Given that this verification spans a region with a diameter of 1 wavelength centered on the axis of rotation in the chamber and that the performance demonstrated by multiple 8 dual-polarized probe MPAC implementations in [29] has shown good alignment up to 0.85  $\lambda$  for SCME UMi, the region where DUT antennas shall be placed (the MIMO OTA test zone) shall be defined in the same way (see Figure A.5.2.1-1a above) but further confined by the 0.85  $\lambda$  antenna separation limit for SCME UMi. Figure A.5.2.1-1b above provides an example of a DUT meeting the maximum allowed antenna separation but not within the verified power stability region; this placement of a DUT shall not be used. The optimization of the maximum allowed antenna spacing of the DUT and the verification of the test zone, as well as SCME UMa considerations, are expected as part of future work.
+
+The region of uniform power delivered by the MIMO system (unverified) as shown in Figure A.5.2.1-1 is an indication of the region where the wave front may maintain its uniformity. Therefore, it may be used to extend the test volume but is not allowed at this time. It is considered unverified because the validation of spatial correlation provides a verification that spans a region of 1  $\lambda$ . Any further extension of the verified test volume would require an update to the spatial correlation validation in [29].
+
+The DUT maximum antenna spacing and placement within the test zone shall be defined by the following two-tier methodology due to the primary radiation modes below 1 GHz and above 1 GHz and how they relate to the device and/or antenna size.
+
+When operating in frequency bands lower than 1GHz, the physical centre of the DUT shall be placed in the chamber centre, the DUT shall be completely contained within the volume defined by the respective operating band equivalent to a sphere with a radius equal to 0.425 wavelengths as defined in Tables A.5.2.1-1 and Tables A.5.2.1-2 for SCME UMi.
+
+When operating in frequency bands higher than 1 GHz the equidistant physical point between the DUT MIMO antenna system shall be placed in the chamber centre following guidance defined in Figure A.5.2.1-2 and the DUT MIMO antenna system (further physical dimension or both antennas' maximum E-field regions) shall be completely contained within the volume defined by the respective operating band equivalent to a sphere with a radius equal to 0.425 wavelength defined in Tables A.5.2.1-1 and Tables A.5.2.1-2 for SCME UMi. The definition of the equidistant point between the DUT MIMO antennas shall be provided through manufacturer declaration for all operating bands where the maximum antenna separation requirement has been met. The location of the equidistant point(s) for each operating band shall be identified by the manufacturer by either marking the device utilized for MIMO OTA testing or by providing clear instructions to the test operator as to the physical location(s).
+
+The two-tier approach is needed to be technically correct when defining the MPAC test volume. While the geometric centre can be used in frequencies lower than 1GHz, the same methodology will add unnecessary limitations for test applicability in frequencies above 1GHz. In this case, manufacturers will need to provide further information to enable the proper definition of the test volume. Ideally, the same approach adopted in frequencies above 1 GHz could be used for all frequencies. However, the extra positioning work and need to identify the equidistant point between the DUT MIMO antennas isn't necessary for frequencies under 1GHz since the wavelength dimension is large enough for all handsets, phablets, and most tablets and laptops.
+
+![Two diagrams illustrating the definition of distance between MIMO antennas and DUT centre. The left diagram shows 'Maximum physical Distance "d" between antennas' as a dashed green line between Antenna 1 and Antenna 2, with a red cross marking the 'Center of MIMO Antenna system'. The right diagram shows 'Maximum E-field Distance "d" between antennas' as a dashed green line between Antenna 1 and Antenna 2, with a red cross marking the 'Center of MIMO Antenna system'. Both diagrams include labels for 'High E-field Antenna 1' and 'High E-field Antenna 2' with dashed circles around them.](8f78b5d84dca49cf2769440c7942a27d_img.jpg)
+
+The diagram consists of two side-by-side rectangular frames. The left frame shows two rectangular antennas, 'Antenna 1' at the bottom and 'Antenna 2' on the right. A dashed green line connects the top-left corner of Antenna 1 to the top-right corner of Antenna 2, labeled 'Maximum physical Distance "d" between antennas'. A red cross is located on this line, labeled 'Center of MIMO Antenna system'. The right frame shows the same two antennas. A dashed green line connects the top-left corner of Antenna 1 to the top-right corner of Antenna 2, labeled 'Maximum E-field Distance "d" between antennas'. A red cross is located on this line, labeled 'Center of MIMO Antenna system'. In both frames, there are dashed circles around the antennas, labeled 'High E-field Antenna 1' and 'High E-field Antenna 2'.
+
+Two diagrams illustrating the definition of distance between MIMO antennas and DUT centre. The left diagram shows 'Maximum physical Distance "d" between antennas' as a dashed green line between Antenna 1 and Antenna 2, with a red cross marking the 'Center of MIMO Antenna system'. The right diagram shows 'Maximum E-field Distance "d" between antennas' as a dashed green line between Antenna 1 and Antenna 2, with a red cross marking the 'Center of MIMO Antenna system'. Both diagrams include labels for 'High E-field Antenna 1' and 'High E-field Antenna 2' with dashed circles around them.
+
+**Figure A.5.2.1-2: Definition of distance between MIMO antennas and DUT centre, maximum physical separation, or E-field maximum separation defined by manufacturer**
+
+**Table A.5.2.1-1: Test zone dimension definition vs. FDD band of operation**
+
+| <b>Band</b> | <b>DL middle channel frequency (MHz)</b> | <b>0.85*Wavelength (m) middle channel</b> | <b>Test volume sphere radius (m)</b> |
+|-------------|------------------------------------------|-------------------------------------------|--------------------------------------|
+| 1           | 2140                                     | 0.119                                     | 0.060                                |
+| 2           | 1960                                     | 0.130                                     | 0.065                                |
+| 3           | 1842.5                                   | 0.138                                     | 0.069                                |
+| 4           | 2132.5                                   | 0.119                                     | 0.060                                |
+| 5           | 881.5                                    | 0.289                                     | 0.145                                |
+| 6           | 880                                      | 0.290                                     | 0.145                                |
+| 7           | 2655                                     | 0.096                                     | 0.048                                |
+| 8           | 942.5                                    | 0.270                                     | 0.135                                |
+| 9           | 1862.4                                   | 0.137                                     | 0.068                                |
+| 10          | 2140                                     | 0.119                                     | 0.060                                |
+| 11          | 1485.9                                   | 0.171                                     | 0.086                                |
+| 12          | 737.5                                    | 0.346                                     | 0.173                                |
+| 13          | 751                                      | 0.339                                     | 0.170                                |
+| 14          | 763                                      | 0.334                                     | 0.167                                |
+| 17          | 740                                      | 0.344                                     | 0.172                                |
+| 18          | 867.5                                    | 0.294                                     | 0.147                                |
+| 19          | 882.5                                    | 0.289                                     | 0.144                                |
+| 20          | 806                                      | 0.316                                     | 0.158                                |
+| 21          | 1503.4                                   | 0.169                                     | 0.085                                |
+| 22          | 3550                                     | 0.072                                     | 0.036                                |
+| 23          | 2190                                     | 0.116                                     | 0.058                                |
+| 24          | 1542                                     | 0.165                                     | 0.083                                |
+| 25          | 1962.5                                   | 0.130                                     | 0.065                                |
+| 26          | 876.5                                    | 0.291                                     | 0.145                                |
+| 27          | 860.5                                    | 0.296                                     | 0.148                                |
+| 28          | 780.5                                    | 0.326                                     | 0.163                                |
+| 29          | 722.5                                    | 0.353                                     | 0.176                                |
+| 30          | 2355                                     | 0.108                                     | 0.054                                |
+| 31          | 465                                      | 0.548                                     | 0.274                                |
+| 32          | 1474                                     | 0.173                                     | 0.086                                |
+
+**Table A.5.2.1-2: Test zone dimension definition vs. TDD band of operation**
+
+| Band | DL middle channel frequency (MHz) | 0.85*Wavelength (m) middle channel | Test Volume Sphere Radius (m) |
+|------|-----------------------------------|------------------------------------|-------------------------------|
+| 34   | 2017.5                            | 0.126                              | 0.063                         |
+| 35   | 1880                              | 0.136                              | 0.068                         |
+| 36   | 1960                              | 0.130                              | 0.065                         |
+| 37   | 1920                              | 0.133                              | 0.066                         |
+| 38   | 2595                              | 0.098                              | 0.049                         |
+| 39   | 1900                              | 0.134                              | 0.067                         |
+| 40   | 2350                              | 0.108                              | 0.054                         |
+| 41   | 2593                              | 0.098                              | 0.049                         |
+| 42   | 3500                              | 0.073                              | 0.036                         |
+| 43   | 3700                              | 0.069                              | 0.034                         |
+| 44   | 753                               | 0.338                              | 0.169                         |
+
+The positioning of the device under test within the test volume shall be set as defined above and in [29].
+
+The environmental requirements for the device under test shall be set as defined in Annex M.
+
+## A.5.2.2 RTS Positioning Guidelines and test zone dimensions
+
+For the RTS system, it can be seen from earlier analysis in the MU budget in TR 37.977 Annex B.2 [29] that the MU elements related to device size are linked to uncertainties in the field uniformity of the anechoic chamber used for the first stage antenna pattern measurement. The RTS MU budget was calculated with the assumption that the device size was within the limits defined by the chamber quiet zone defined in TS 34.114 Annex A2.3 [6], TS 34.114 E.10 [6] and as measured in TS 34.114 Annex G.2 [6]. The applicable device size for RTS is therefore the same as used for SISO TRS in the same chamber.
+
+The second stage of the RTS method which involves a cable replacement radiated connection, is assumed in the MU budget to take place in the same anechoic chamber as was used for the first stage antenna pattern measurement, and there are no additional test zone considerations required. The use of a different chamber for the second stage is not precluded, but would require a recalculation of the impact of any difference between the anechoic chambers.
+
+For device positioning within the test zone for the first stage the normal positioning accuracy assumed in TR 37.977 Table B.2-1 [29] of 1 degree is considered insignificant compared to the raster used for the antenna measurement.
+
+For the second stage positioning impact, and with the assumption the chamber is the same as used in the first stage, the issue is the repeatability of the position used from the first stage. This is likely to be less than the 1 degree absolute positioning error so is again assumed to be negligible.
+
+---
+
+## Annex B (normative): Calibration
+
+### B.1 General
+
+The relative power values of the measurement points will be transformed to absolute radiated power values (in dBm) by performing a calibration measurement. The calibration measurement is done by using a reference antenna with known efficiency or gain values. In the calibration measurement the reference antenna is measured in the same place as the DUT, and the attenuation of the complete transmission path () from the DUT to the measurement receiver/NB/BS simulator is calibrated out.
+
+The gain and/or radiation efficiency of the reference antenna shall be known at the frequency bands in which the calibrations are performed. Recommended calibration antennas are monopole antennas or sleeve dipoles tuned for the each frequency band of interest. Alternatively, other methods may be used if they ensure an equal or greater level of accuracy. A network analyzer is recommended to be used to perform the calibration measurement. Also other devices can be used to measure attenuation.
+
+The principle is based on the use of calibration/substitution antennas presenting an efficiency known with a sufficient accuracy in the measurement bandwidths. Such a calibration antenna is placed on the DUT positioner at the exact UE location used for TRP and TRS measurement. It is possible to use a mechanical piece to place the calibration antenna on the positioner. This mechanical piece should not present any electromagnetic properties, which could influence the frequency response and the radiation properties of the calibration antenna.
+
+## B.2 Calibration procedure
+
+### B.2.1 Calibration procedure for Anechoic chamber method
+
+For the anechoic chamber method, the calibration is performed individually for the both orthogonal polarizations, all the transmission paths and all frequencies used in the testing. An illustration of the substitution configuration is shown in Figure B.2.1-1.
+
+is the attenuation between P and B, see Figure B.2.1-1.
+
+Where  $L_{AC}$  is cable loss from A to C. The cable AC connecting the substitution antenna should be such that its influence upon radiation pattern measurements is minimal.  $L_{AB}$  is the attenuation between points A and B. In TRP and TRS measurements point B is connected to the calibrated input/output port of measurement receiver.
+
+$G_{cal}$  is the efficiency or gain of the calibration antenna at the frequency of interest.
+
+![Diagram of calibration/substitution procedures using a vector network analyzer. A Network Analyser is connected to Port 1 (A) and Port 2 (B). Port 1 is connected to a Calibration antenna via a cable (C). Port 2 is connected to a Dual-polarized horn antenna via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand. The Calibration antenna is connected to the Network Analyser via a cable (C). The Dual-polarized horn antenna is connected to the Network Analyser via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand. The Calibration antenna is connected to the Network Analyser via a cable (C). The Dual-polarized horn antenna is connected to the Network Analyser via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand.](9507bf8a743ef8e70785692053d75e7c_img.jpg)
+
+Diagram of calibration/substitution procedures using a vector network analyzer. A Network Analyser is connected to Port 1 (A) and Port 2 (B). Port 1 is connected to a Calibration antenna via a cable (C). Port 2 is connected to a Dual-polarized horn antenna via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand. The Calibration antenna is connected to the Network Analyser via a cable (C). The Dual-polarized horn antenna is connected to the Network Analyser via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand. The Calibration antenna is connected to the Network Analyser via a cable (C). The Dual-polarized horn antenna is connected to the Network Analyser via a cable. The Calibration antenna is mounted on a positioner. The Dual-polarized horn antenna is mounted on a stand.
+
+Figure B.2.1-1: Calibration/substitution procedures using a vector network analyzer
+
+If the calibration is based on known efficiency of the calibration antenna, a full spherical scanning is performed to determine. Unless the otherwise specified in the calibration antenna documentation, TRP sampling grid in clause 4.4 and equation for TRP in clause 6 should be used for head and hand phantom and TRP sampling grid in clause 4.4 and equation for TRP in clause 6 should be used for laptop ground plane phantom and embedded devices.
+
+This procedure has to be done at each frequency of interest.
+
+To achieve measurements with an uncertainty as low as possible, it is absolutely necessary to exactly keep the same P to B configuration (cables, dual-polarized antenna).
+
+### B.2.2 Calibration procedure for Reverberation chamber method
+
+For the reverberation chamber method, all polarizations and transmission paths are included in one calibration measurement. The calibration antenna can be placed in an arbitrarily position, as long as it is placed 0.5 wavelengths
+
+from other metallic objects and 0.7 wavelengths from absorbing objects. An illustration of the measurement setup for this procedure is shown in Figure B.2.2-1.
+
+The purpose of the calibration measurement is to determine the average power transfer function in the chamber, mismatch of fixed measurement antennas and path losses in cables connecting the power sampling instrument and the fixed measurement antennas. Preferably a network analyzer is used for these measurements. Recommended calibration antennas are dipoles tuned to the frequency band of interest.
+
+In general, the calibration of a reverberation chamber is performed in three steps:
+
+1. Measurement of S-parameters through the reverberation chamber for a complete stirring sequence
+2. Calculation of the chamber reference transfer function
+3. Measurement of connecting cable insertion loss
+
+If several setups are used (e.g. empty chamber, chamber with head or hand phantom, etc.), steps 1 and 2 must be repeated for each configuration. The calibration measurement setup is shown in Figure B.2.2-1.
+
+![Diagram of the calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' is connected to 'Port 1' of a 'Vector network analyzer' via a cable. A 'Fixed measurement antenna' is connected to 'Port 2' of the same analyzer via another cable. Arrows labeled 'VNA calibration points' point to the connection points of both antennas inside the chamber. The diagram shows the setup for measuring S-parameters through the chamber.](b2448ec0a23090beb4402121beeff751_img.jpg)
+
+Diagram of the calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' is connected to 'Port 1' of a 'Vector network analyzer' via a cable. A 'Fixed measurement antenna' is connected to 'Port 2' of the same analyzer via another cable. Arrows labeled 'VNA calibration points' point to the connection points of both antennas inside the chamber. The diagram shows the setup for measuring S-parameters through the chamber.
+
+**Figure B.2.2-1: Calibration measurement setup in the reverberation chamber, using a vector network analyzer**
+
+### B.2.2.1 Measurement of S-parameters through the chamber for a complete stirring sequence
+
+This step will measure S-parameters through the reverberation chamber through a complete stirring sequence. This information is required to determine the chamber's reference transfer function. The procedure must be performed separately for each measurement setup of which the loading of the chamber has been changed. The calibration procedure must be repeated for each frequency as defined above. Therefore, it is advantageous if the network analyzer can be set to a frequency sweep covering the defined frequencies, so that all frequencies of interest can be measured with a minimal number of measurement runs.
+
+- i. Place all objects into the RC which will be used during TRP or TRS measurements, including a head phantom, hand phantom and fixture for the EUT. This ensures that the loss in the chamber, which determines the average power transfer level, is the same during both calibration and test measurements. Also, if the EUT is large or contains many antennas, it may represent a noticeable loading of the chamber. It should then be present in the chamber and turned on during the calibration.
+- ii. Place the calibration antenna inside the chamber. The calibration antenna is preferably mounted on a low-loss dielectric fixture, to avoid effects from the fixture itself which may affect the EUT's radiation efficiency and mismatch factor. The calibration antenna must be placed in the chamber in such a way that it is far enough from
+
+any walls, mode-stirrers, head phantom, hand phantom, or other object, such that the environment for the calibration antenna (taken over the complete stirring sequence) resembles a free space environment. “Far enough away” depends on the type of calibration antenna used. For low gain nearly omni-directional antennas like dipoles, it is normally sufficient to ensure that this spacing is larger than 0.5 wavelengths. More directive calibration antennas should be situated towards the centre of the chamber. The calibration antenna should be present in the chamber during the TRP/TRS measurements.
+
+- iii. Calibrate the network analyzer with a full 2-port calibration in such a way that the vector S-parameters between the ports of the fixed measurement antenna and the calibration antenna can be accurately measured. Preferably, the network analyzer is set to perform a frequency sweep at each stirrer position. This will enable calibration of several frequency points during the same stirring sequence, thereby reducing calibration time. This will also enable frequency stirring, i.e., averaging the measured power transfer function over a small frequency bandwidth around each measured frequency point (moving frequency window). This will increase accuracy at the expense of frequency resolution.
+- iv. Connect the antennas and measure the S-parameters for each stirrer position and each fixed measurement antenna.
+
+The number of stirrer positions in the chosen stirring sequence, i.e. the number of S-parameter samples at each frequency point, should be chosen in such a way that it is large enough to yield an acceptable statistical contribution to the total measurement uncertainty. As a guideline it should be larger than 100, preferable 200 or 400 to ensure that the number of independent samples is not severely limited by the total number of samples measured. The number of independent samples, which is a subset of all samples, determines the statistical contribution to the expanded accuracy (which is two times the standard deviation). This should be not less than 100 to ensure an expanded accuracy better than 0.5 dB. The number of independent samples depends on the operating frequency, volume of the chamber, efficacy of the chamber’s stirrers, the level of loading by absorbing objects, and whether or not frequency stirring is used.
+
+The sequence of moving the stirrers to different positions may be either step-wise (stopping stirrer for each sample) or continuous (sampling on-the-fly). With continuous stirring it may not be possible to characterize the chamber over a wide frequency band at the same time.
+
+### B.2.2.2 Calculation of the chamber reference transfer function
+
+From the S-parameters obtained in the calibration measurement, the chamber reference transfer function for fixed antenna  $n$  can be calculated. The reflection coefficient for fixed antenna  $n$  can be calculated by the following equation,
+
+Thus, the chamber reference transfer function can be calculated by the following equation,
+
+is
+
+where  $M$  is the total number of samples of the transfer function measured for each fixed measurement antenna and sample number  $m$  of the transfer function for measurement antenna  $n$ . Moreover,  $\Gamma_{cal}$  is the complex average of the calibration antenna reflection coefficient. Finally,  $\epsilon_{cal}$  is the radiation efficiency of the calibration antenna.
+
+NOTE: The radiation efficiency of the fixed antenna is not corrected for because it will be the same both during calibration and measurements. Therefore, the fixed antenna’s radiation efficiency will not affect the final results. The same can be said about the mismatch factor of the fixed measurement antennas, but it is still advantageous to correct for this factor if frequency stirring is applied to improve accuracy.
+
+### B.2.2.3 Cable calibration
+
+This measurement step will calibrate the power loss of the cable needed to connect the instrument used to measure the received power at the fixed measurement antenna during TRP measurements, and to generate the power radiated by the fixed antenna during TRS measurements.
+
+- i. Disconnect the cables between the VNA and the chamber.
+- ii. Connect the cables one-by-one between the two ports of the network analyzer. The VNA must be calibrated at its own two ports.
+
+- iii. Measure the frequency response of the transmission S-parameter ( $S_{21}$  or  $S_{12}$ ) of the cable.
+- iv. Save the power transfer values ( $|S_{21}|^2$ ) of the frequency response curve for the test frequencies and cables positions, etc).
+
+Calibration shall be performed yearly or if any equipment in the measurement system is changed.
+
+## B.2.3 Calibration procedure for Anechoic chamber method with Multiprobe configuration
+
+The system needs to be calibrated in two steps in order to ensure that the absolute power is correct. The first calibration steps ensures the accurate generation of the channel model in the centre of the chamber as required by Annex L.4. The second step validates the total power as would be seen by the DUT and allows for that power to be scaled up or down if necessary.
+
+Considering the complexity of the system various way to calibrate are possible. The end goals are however the same no matter the exact procedure. The two steps must achieve the following:
+
+**Step 1:** This step is used to equalize the power in the centre coming from the different probes. This being a relative measurement is very robust and with minimal uncertainty. It is sufficient to use instruments calibrated according to the manufacturer's specifications and the measurements require no additional calibration. This step is done for both vertical and horizontal polarizations. The relative differences between probe path losses are recorded and used (typically in the fading emulator) to adjust the generated fading signals for each probe. Example measurement set-up is shown in Figure B.2.3.1-1.
+
+NOTE 1: If Step 1 is performed as an absolute measurement accounting for the cable and reference antenna gains Step 2 can be omitted.
+
+**Step 2:** This step is used to measure the total absolute power of at least one polarization in the centre of the ring. Then assuming that validation of the channel models has been done, the total power available to the DUT in the centre of the chamber can be computed. If necessary the power can be scaled up or down to achieve the desired power level. Since this is an absolute power measurement, the measurement cable and reference antenna gains have to be accounted for.
+
+NOTE 2: To minimize measurement uncertainty the passive and active components of the system may be calibrated independently as well as at different intervals.
+
+NOTE 3: Step 2 of the calibration should be performed with the channel model loaded and LTE signalling active. Sufficient amount of time averaging is required because of the fading nature of the models used.
+
+NOTE 4: Various ways of performing the two steps may exist depending on the equipment used. The lab is responsible for providing a comprehensive calibration procedure.
+
+NOTE 5: Steps one and two may be combined with the channel verification procedure.
+
+NOTE 6: The calibration must be performed for all frequencies of interest.
+
+### B.2.3.1 Example Calibration Procedure
+
+The calibration procedure outlined below is only one possibility based on a concrete measurement set-up. Improvements can be made to minimize measurement uncertainty.
+
+#### Step 1 (see Figure B.2.3.1-1)
+
+1. Place a vertical reference dipole in the centre of the chamber, connected to a VNA port, with the other VNA port connected to the input of the channel emulator unit.
+2. Configure the channel emulator for bypass mode (NOTE this might not be available in all instruments)
+3. Measure the response of each path from each vertical polarization probe to the reference antenna in the centre.
+4. Adjust the power on all vertical polarization branches of the channel emulator so that the powers received at the centre are equal.
+
+5. Repeat the steps 1 to 4 with the magnetic loop and horizontally polarized probes instead, and adjust the horizontal polarization branches of the channel emulator.
+
+NOTE: At this stage all vertical polarization paths have equalized gains, and so do all horizontal polarization paths. The two polarizations however do not necessarily produce the same signal strength in the centre of the chamber – this most commonly happens if two physically different channel emulators are used for the two polarizations. The resulting power imbalance can be accounted for either at this step or adjusted at point 7 of step 2.
+
+![Diagram of the setup for VNA measurements. A VNA is connected to a Fading emulator. The Fading emulator is connected to a Chamber. Inside the Chamber, there are two antennas: a Test antenna and a reference antenna. The VNA is connected to the Test antenna via a red line, and the Fading emulator is connected to the reference antenna via a black line.](bb3057eb5987c035bdad3cfe2c8e78c5_img.jpg)
+
+The diagram illustrates the experimental setup for VNA measurements. On the left, a box labeled 'VNA' is connected to a box labeled 'Fading emulator'. The 'Fading emulator' is connected to a large rectangular box labeled 'Chamber'. Inside the 'Chamber', there are two antennas: a 'Test antenna' (represented by a red triangle) and a reference antenna (represented by a black triangle). A red line connects the 'VNA' to the 'Test antenna', and a black line connects the 'Fading emulator' to the reference antenna. The 'Chamber' is shown as a 3D perspective view of a rectangular box.
+
+Diagram of the setup for VNA measurements. A VNA is connected to a Fading emulator. The Fading emulator is connected to a Chamber. Inside the Chamber, there are two antennas: a Test antenna and a reference antenna. The VNA is connected to the Test antenna via a red line, and the Fading emulator is connected to the reference antenna via a black line.
+
+**Figure B.2.3.1-1: Setup for VNA measurements**
+
+#### Step 2 (see Figure B.2.3.1-2)
+
+1. Place a vertical reference dipole in the centre of the chamber connected to a spectrum analyzer via an RF cable.
+
+NOTE: A power meter can also be used.
+
+2. Record the cable and reference dipole gains.
+3. Load the target channel model
+4. Start the LTE signalling in the base station emulator with the required parameter identical to the measurements conditions (some special instrument options might be necessary).
+5. Average the power received by the spectrum analyzer for a sufficient amount of time to account for the fading channel – one full channel simulation might be unnecessary.
+6. Repeat steps 1 to 4 with a magnetic loop for the horizontal polarization (NOTE: this way no prior validation of the channel model is required)
+7. Calculate the total power received at the test area as the sum of the power in the two polarizations.
+8. Adjust the power in the two polarizations if necessary. The power adjustment can be a simple scaling of the power up or down or adjustment of the XPR due to slight differences in the fading unit's branches. Depending on the adjustment needed, it can be done at the base station emulator or the channel emulator or both.
+
+![Figure B.2.3.1-2: Example setup for step 2 of the calibration. The diagram shows a signal chain starting from a Radio Communication Tester, passing through a Channel Emulator (where interference is injected), then an Amplifier Box, and finally entering a MIMO Ring. Inside the MIMO Ring, there are multiple Probe Antennas and a central Reference Antenna. A Spectrum Analyzer is connected to the Reference Antenna to measure the signal.](b96be3d7d73fc1d7af1879bb57de1cc4_img.jpg)
+
+Figure B.2.3.1-2: Example setup for step 2 of the calibration. The diagram shows a signal chain starting from a Radio Communication Tester, passing through a Channel Emulator (where interference is injected), then an Amplifier Box, and finally entering a MIMO Ring. Inside the MIMO Ring, there are multiple Probe Antennas and a central Reference Antenna. A Spectrum Analyzer is connected to the Reference Antenna to measure the signal.
+
+**Figure B.2.3.1-2: Example setup for step 2 of the calibration**
+
+## B.2.4 Calibration procedure for RTS method
+
+For the RTS method, only the DUT reporting RSAP calibration is to perform. The RTS method depends on reported RSAP to do the antenna pattern measurement, and the power calibration for radiated second-stage throughput test. Since these reported readings do not come from a calibrated measurement instrument, their accuracies are often subject to questioning. Below procedure provides method for proper calibration to validate the reported RSAP accuracy.
+
+- DUT reporting RSAP calibration:
+
+With proper spherical coordinate definition of mobile terminal setup, the receive antenna pattern at any coordinate  $(\theta_i, \phi_i)$  can be expressed as:
+
+$$P(\theta_i, \phi_i) = \text{RS}_i \quad (1)$$
+
+The test point  $(\theta_i, \phi_i)$  can be at any point on the  $4\pi$  solid angle of the coordinate. More precisely, the reported RS of the UE can be expressed as:
+
+$$\text{RS}_i(x) = m(x) \cdot x + c \quad (2)$$
+
+where  $m(x_i)$  and  $c$  is a function of signal strength independent of testing point angular coordinates.  $x$  is the actual incident field power density that can be derived from the signal power and test range loss. The above equation (2) assumes that the signal variables in both sides of the equation are expressed in decibels or dB. When  $m(x)=1$  and  $c=g_0$ , where  $g_0$  is the received antenna gain at the test point, we would have declared that the RS report is a true reading of the signal strength. But in reality,  $m(x)$  can be biased by either the signal level relative to the receiver's detector operating condition, or by application software programming errors. Meanwhile, the offset constant  $c$  can also be biased by either the noise floor of the receiver and/or other artificial factors in the UE RS reporting. Therefore, a Taylor's series can be introduced to have a better representation of the RS report value:
+
+$$\text{RS}_i(x) = c + ax + bx^2 + dx^3 + ex^4 + \dots \quad (3)$$
+
+In theory, equation (3) may require many terms to represent the RS report accurately. However, since the reported RS reading in the receive antenna pattern in (1) has a limited signal dynamic range, the following three term expression is enough to correct for the reporting errors:
+
+$$\text{RS}_i(x) = c + ax + bx^2 + o(x^3) \quad (4)$$
+
+The third order term  $o(x^3)$  is ignored since it is not significant for limited signal dynamic range.
+
+The RS pattern in (1) will need to be calibrated for its possible reporting errors. One practical method is to introduce signal correction terms in equation (4) to enhance the accuracy. This process is also referred to as the linearization. The following steps describe what is needed to linearize the RS report and the RS antenna pattern in (1):
+
+1. Find the maximum RS reading in the pattern obtained in (1) from all angular test points, and at all polarizations. Set this point as the reference point and record signal generator power  $P_0$  and let  $x_0 = P_0 - \text{Test Range Path Loss (in dB)}$ , and note the maximum RS reading as  $r_0$ .
+2. At the reference test point, decrease the signal generator's output power  $P_i$ , and let  $x_i = P_i - \text{Test Range Path Loss (in dB)}$ , starting from  $P_0$  with a step size (1.0 dB by default) to a power range so as to obtain the full RS reading range while searching from the reference point  $r_0$  when the test system dynamic range allows, or to 20 dB by default when the system dynamic range is known to be limited, whichever is lower in range. Record the corresponding RS reading of the UE as  $r_i$ . Repeat this process until all angular test points are completed as required.
+3. Use those pairs of data obtained in Step 2) ( $r_i$ ,  $x_i$ ) as the input of the quadratic fitting curve in (4) to formulate the Algorithm LSF (Least Square Fit) to calculate the three coefficients ( $a$ ,  $b$ , and  $c$ ) in:
+
+$$\text{Err}(a,b,c) = \sum (c + ax_i + bx_i - r_i)^2 \quad (5)$$
+
+Please note that the power range of the linearization can be limited to 20 dB as stated in Step 2) since the lower RS readings than the processed range do not contribute to the overall receive antenna pattern as much.
+
+Once the three coefficients ( $a$ ,  $b$ , and  $c$ ) are obtained in LSF of (5), the use of the inverse function of Equation (4) to convert RS pattern in (1) into the normalized incident power pattern. This process completes the error correction for both constant biased and the non-linearity in the RS report from the UE within the limited signal dynamic range as tested in (1) and Step 1. Similar steps can be applied for error corrections if multiple receiver RS are involved in the testing.
+
+Of course, the reference test point can also be further tested for the threshold of the receiver sensitivity and/or throughput knee-point for the required calibrated reference power level.
+
+## Annex C (informative): Measurement test report
+
+### C.1 General
+
+Operational mode, model and serial number of the DUT shall be documented to the test report. Whether the DUT is positioned against the phantom head with a specific device holder or by other means it should be described in the test report. When the DUT is positioned on the hand phantom it should be described in the test report. When the DUT is positioned on the laptop ground plane phantom it should be described in the test report. A photograph of the test setup is recommended.
+
+Test equipment list should be included in the test report.
+
+[dBm] and [dBm] values shall be reported for each tested channel and for each side of the head and a frequency band average shall be calculated by using the following equations when the phantom head is used.
+
+[dBm] and [dBm] values shall be reported for each tested channel and for each hand and a frequency band average shall be calculated by using the following equations when the hand phantom is used.
+
+[dBm] and [dBm] values shall be reported for each tested channel and a frequency band average shall be calculated by using the following equations when the laptop ground plane phantom is used and when the embedded devices are tested.
+
+The expanded measurement uncertainty, assessed according Annex E, shall be documented next to the corresponding TRP and TRS results. The uncertainty calculation shall be made available.
+
+---
+
+## Annex D (normative): Maximum uncertainty of test system and test tolerance
+
+### D.1 Maximum uncertainty of test system
+
+The maximum acceptable uncertainty of the Test System is specified in Table D.1-1 for each test, where appropriate. The Test System shall enable each test to be measured with an uncertainty not exceeding the specified values. All ranges and uncertainties are absolute values and are valid for a confidence level of 95 %.
+
+In Annex E, the estimation of measurement uncertainty is defined.
+
+**Table D.1-1: Maximum Test System uncertainties for OTA tests**
+
+| Clause                                                                        | Maximum Test System Uncertainty                                      | Derivation of Test System Uncertainty |
+|-------------------------------------------------------------------------------|----------------------------------------------------------------------|---------------------------------------|
+| 6.1.1 TRP for UTRA FDD in Speech Mode with beside the Head Phantom            | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>±1.9 dB for single measurement | Refer to Annex E                      |
+| 6.1.2 TRP for UTRA TDD in Speech Mode with beside the Head Phantom            | Bands a,e,f<br>±1.9 dB for single measurement                        | Refer to Annex E                      |
+| 6.1.3 TRP for UTRA FDD in Speech Mode with beside the Head and Hand Phantom   | ±1.9 dB for single measurement                                       | [TBD]                                 |
+| 6.1.4 TRP for UTRA TDD in Speech Mode with beside the Head and Hand Phantom   | ±1.9 dB for single measurement                                       | [TBD]                                 |
+| 6.1.5 TRP for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                | [TBD]                                 |
+| 6.1.6 TRP for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                | [TBD]                                 |
+| 6.1.7 TRP for UTRA FDD in Browsing Mode with Hand Phantom                     | [TBD]                                                                | [TBD]                                 |
+| 6.1.8 TRP for UTRA TDD in Browsing Mode with Hand Phantom                     | [TBD]                                                                | [TBD]                                 |
+| 6.1.9 TRP for E-UTRA FDD in Browsing Mode with Hand Phantom                   | [TBD]                                                                | [TBD]                                 |
+| 6.1.10 TRP for E-UTRA TDD in Browsing Mode with Hand Phantom                  | [TBD]                                                                | [TBD]                                 |
+| 6.2.1 TRP for UTRA FDD LME                                                    | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>±1.9 dB for single measurement | Refer to Annex E                      |
+| 6.2.2 TRP for UTRA TDD LME                                                    | Bands a,e,f<br>±1.9 dB for single measurement                        | Refer to Annex E                      |
+| 6.2.3 TRP for E-UTRA FDD LME                                                  | [TBD]                                                                | [TBD]                                 |
+| 6.2.4 TRP for E-UTRA TDD LME                                                  | [TBD]                                                                | [TBD]                                 |
+| 6.3.1 TRP for UTRA FDD LEE                                                    | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>±1.9 dB for single measurement | Refer to Annex E                      |
+| 6.3.2 TRP for UTRA TDD LEE                                                    | Bands a,e,f<br>±1.9 dB for single measurement                        | Refer to Annex E                      |
+| 6.3.3 TRP for E-UTRA FDD LEE                                                  | ±1.9 dB for single measurement                                       | [TBD]                                 |
+| 6.3.4 TRP for E-UTRA TDD LEE                                                  | ±1.9 dB for single measurement                                       | [TBD]                                 |
+| 7.1.1 TRS for UTRA FDD in Speech Mode with beside the Head Phantom            | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>±2.3 dB for single measurement | Refer to Annex E                      |
+| 7.1.2 TRS for UTRA TDD in Speech Mode with beside the Head Phantom            | Bands a,e,f<br>±2.3 dB for single measurement                        | Refer to Annex E                      |
+| 7.1.3 TRS for UTRA FDD in Speech Mode with Head and Hand Phantom              | ±2.3 dB for single measurement                                       | [TBD]                                 |
+| 7.1.4 TRS for UTRA TDD in Speech Mode with beside the Head and Hand Phantom   | ±2.3 dB for single measurement                                       | [TBD]                                 |
+| 7.1.5 TRS for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                | [TBD]                                 |
+| 7.1.6 TRS for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                | [TBD]                                 |
+| 7.1.7 TRS for UTRA FDD in Browsing Mode with Hand Phantom                     | [TBD]                                                                | [TBD]                                 |
+| 7.1.8 TRS for UTRA TDD in Browsing Mode with Hand Phantom                     | [TBD]                                                                | [TBD]                                 |
+| 7.1.9 TRS for E-UTRA FDD in Browsing Mode with Hand Phantom                   | [TBD]                                                                | [TBD]                                 |
+| 7.1.10 TRS for E-UTRA TDD in Browsing Mode with Hand Phantom                  | [TBD]                                                                | [TBD]                                 |
+| 7.2.1 TRS for UTRA FDD LME                                                    | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>±2.3 dB for single measurement | Refer to Annex E                      |
+
+|                                                              |                                                                           |                  |
+|--------------------------------------------------------------|---------------------------------------------------------------------------|------------------|
+| 7.2.2 TRS for UTRA TDD LME                                   | Bands a,e,f<br>$\pm 2.3$ dB for single measurement                        | Refer to Annex E |
+| 7.2.3 TRS for E-UTRA FDD LME                                 | [TBD]                                                                     | [TBD]            |
+| 7.2.4 TRS for E-UTRA TDD LME                                 | [TBD]                                                                     | [TBD]            |
+| 7.3.1 TRS for UTRA FDD LEE                                   | Bands I,II,III,IV,V,VI,VII,VIII,IX<br>$\pm 2.3$ dB for single measurement | Refer to Annex E |
+| 7.3.2 TRS for UTRA TDD LEE                                   | Bands a,e,f<br>$\pm 2.3$ dB for single measurement                        | Refer to Annex E |
+| 7.3.3 TRS for E-UTRA FDD LEE                                 | $\pm 2.3$ dB for single measurement                                       | [TBD]            |
+| 7.3.4 TRS for E-UTRA TDD LEE                                 | $\pm 2.3$ dB for single measurement                                       | [TBD]            |
+| 7.4.1 Radiated Performance of Multiple-antenna Receivers FDD | $\pm 2.65$ dB for MPAC                                                    | Refer to Annex N |
+| 7.4.2 Radiated Performance of Multiple-antenna Receivers TDD | $\pm 2.65$ dB for MPAC                                                    | Refer to Annex N |
+
+---
+
+## D.2 Test tolerances
+
+Test tolerances in Table D.2-1 are used to relax the Minimum Requirements in the present document and to derive the Test Requirements.
+
+**Table D.2-1: Test Tolerances for OTA tests**
+
+| <b>Clause</b>                                                                    | <b>Test Tolerance</b>                                                                                      |
+|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+| 6.1.1 TRP for UTRA FDD in Speech Mode with beside the Head Phantom               | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement |
+| 6.1.2 TRP for UTRA TDD in Speech Mode with beside the Head Phantom               | Bands a,e,f<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement                            |
+| 6.1.3 TRP for UTRA FDD in Speech Mode with beside the Head and Hand Phantom      | 1.0 dB for minimum requirement<br>0.7 dB for average requirement                                           |
+| 6.1.4 TRP for UTRA TDD in Speech Mode with beside the Head and Hand Phantom      | 1.0 dB for minimum requirement<br>0.7 dB for average requirement                                           |
+| 6.1.5 TRP for E-UTRA FDD UE in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                                                      |
+| 6.1.6 TRP for E-UTRA TDD UE in Speech Mode with beside the Head and Hand Phantom | [TBD]                                                                                                      |
+| 6.1.7 TRP for UTRA FDD UE in Browsing Mode with Hand Phantom                     | [TBD]                                                                                                      |
+| 6.1.8 TRP for UTRA TDD UE in Browsing Mode with Hand Phantom                     | [TBD]                                                                                                      |
+| 6.1.9 TRP for E-UTRA FDD UE in Browsing Mode with Hand Phantom                   | [TBD]                                                                                                      |
+| 6.1.10 TRP for E-UTRA TDD UE in Browsing Mode with Hand Phantom                  | [TBD]                                                                                                      |
+| 6.2.1 TRP for UTRA FDD LME                                                       | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement |
+| 6.2.2 TRP for UTRA TDD LME                                                       | Bands a,e,f<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement                            |
+| 6.2.3 TRP for E-UTRA FDD LME                                                     | [TBD]                                                                                                      |
+| 6.2.4 TRP for E-UTRA TDD LME                                                     | [TBD]                                                                                                      |
+| 6.3.1 TRP for UTRA FDD LEE                                                       | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement |
+| 6.3.2 TRP for UTRA TDD LEE                                                       | Bands a,e,f<br>1.0 dB for minimum requirement<br>0.7 dB for average requirement                            |
+| 6.3.3 TRP for E-UTRA FDD LEE                                                     | 1.0 dB for minimum requirement<br>0.7 dB for average requirement                                           |
+| 6.3.4 TRP for E-UTRA TDD LEE                                                     | 1.0 dB for minimum requirement<br>0.7 dB for average requirement                                           |
+| 7.1.1 TRS for UTRA FDD in Speech Mode with beside the Head Phantom               | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.2 dB for maximum requirement<br>0.9 dB for average requirement |
+| 7.1.2 TRS for UTRA TDD in Speech Mode with beside the Head Phantom               | Bands a,e,f<br>1.2 dB for minimum requirement<br>0.9 dB for average requirement                            |
+| 7.1.3 TRS for UTRA FDD in Speech Mode with beside the Head and Hand Phantom      | 1.2 dB for maximum requirement<br>0.9 dB for average requirement                                           |
+| 7.1.4 TRS for UTRA TDD in Speech Mode with beside the Head and Hand Phantom      | 1.2 dB for maximum requirement<br>0.9 dB for average requirement                                           |
+| 7.1.5 TRS for E-UTRA FDD in Speech Mode with beside the Head and Hand Phantom    | [TBD]                                                                                                      |
+| 7.1.6 TRS for E-UTRA TDD in Speech Mode with beside the Head and Hand Phantom    | [TBD]                                                                                                      |
+| 7.1.7 TRS for UTRA FDD in Browsing Mode with Hand Phantom                        | [TBD]                                                                                                      |
+| 7.1.8 TRS for UTRA TDD in Browsing Mode with Hand Phantom                        | [TBD]                                                                                                      |
+| 7.1.9 TRS for E-UTRA FDD in Browsing Mode with Hand Phantom                      | [TBD]                                                                                                      |
+| 7.1.10 TRS for E-UTRA TDD in Browsing Mode with Hand Phantom                     | [TBD]                                                                                                      |
+| 7.2.1 TRS for UTRA FDD LME                                                       | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.2 dB for maximum requirement                                   |
+
+|                                                              |                                                                                                            |
+|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|
+|                                                              | 0.9 dB for average requirement                                                                             |
+| 7.2.2 TRS for UTRA TDD LME                                   | Bands a,e,f<br>1.2 dB for minimum requirement<br>0.9 dB for average requirement                            |
+| 7.2.3 TRS for E-UTRA FDD LME                                 | [TBD]                                                                                                      |
+| 7.2.4 TRS for E-UTRA TDD LME                                 | [TBD]                                                                                                      |
+| 7.3.1 TRS for UTRA FDD LEE                                   | Bands I,II,III,IV,V,VI,VII,VIII,IX,XIX<br>1.2 dB for maximum requirement<br>0.9 dB for average requirement |
+| 7.3.2 TRS for UTRA TDD LEE                                   | Bands a,e,f<br>1.2 dB for minimum requirement<br>0.9 dB for average requirement                            |
+| 7.3.3 TRS for E-UTRA FDD LEE                                 | 1.2 dB for maximum requirement<br>0.9 dB for average requirement                                           |
+| 7.3.4 TRS for E-UTRA TDD LEE                                 | 1.2 dB for maximum requirement<br>0.9 dB for average requirement                                           |
+| 7.4.1 Radiated Performance of Multiple-antenna Receivers FDD | 1 dB                                                                                                       |
+| 7.4.2 Radiated Performance of Multiple-antenna Receivers TDD | 1 dB                                                                                                       |
+
+## Annex E (informative): Estimation of measurement uncertainty
+
+### E.1 General
+
+Individual uncertainty contributions in the TRP and TRS measurements are discussed and evaluated in this Annex. A technique for calculating the total measurement uncertainty is also presented.
+
+An important part of a standard measurement procedure is the identification of uncertainty sources and the evaluation of the overall measurement uncertainty. There are various individual uncertainty sources in the measurement procedure that introduce a certain uncertainty contribution to the final measurement result. The approach in this standard test procedure is that the test laboratories are not limited to using some specific instruments and antenna positioners, for example. However, a limit is set for the maximum overall measurement uncertainty.
+
+The TRP/TRS measurement procedure can be considered to include two stages. In Stage 1 the actual measurement of the 3-D pattern of the Device Under Test (DUT) is performed. In Stage 2 the calibration of the absolute level of the DUT measurement results is performed by means of using a calibration antenna whose absolute gain/radiation efficiency is known at the frequencies of interest. The uncertainty contributions related to TRP are listed in Tables E.1-1 and E.1-2 and the contributions related to TRS are in Tables E.1-3 and E.1-4. The uncertainty contributions are analyzed in the following paragraphs.
+
+The calculation of the uncertainty contribution is based on the ISO Guide to the expression of uncertainty in measurement. Each individual uncertainty is expressed by its Standard Deviation (termed here as 'standard uncertainty') and represented by symbol  $U$ . The uncertainty contributions can be classified to two categories: Type-A uncertainties, which are statistically determined e.g. by repeated measurements, and Type-B uncertainties, which are derived from existing data e.g. data sheets. Several individual uncertainties are common in Stage 1 and Stage 2 and therefore cancel.
+
+The procedure of forming the uncertainty budget in TRP measurement is:
+
+- 1) Compile lists of individual uncertainty contributions for TRP measurement in both Stage 1 and Stage 2.
+- 2) Determine the standard uncertainty of each contribution by
+  - a) Determining the distribution of the uncertainty (Gaussian, U-shaped, rectangular, etc.)
+  - b) Determining the maximum value of each uncertainty (unless the distribution is Gaussian)
+
+c) Calculating the standard uncertainty by dividing the uncertainty by  $\sqrt{2}$  if the distribution is U-shaped, and by  $\sqrt{3}$  if the distribution is rectangular.
+
+3) Convert the units into decibel, if necessary.
+
+4) Combine all the standard uncertainties by the Root of the Sum of the Squares (RSS) method.
+
+5) Combine the total uncertainties in Stage 1 and Stage 2 also by the RSS method:
+
+$$u_c = \sqrt{u_{c,DUT\ measurement}^2 + u_{c,calibration\ measurement}^2}$$
+
+6) Multiply the result by an expansion factor of 1.96 to derive expanded uncertainty at 95% confidence level:
+
+$$1.96 * u_c$$
+
+Example uncertainty budgets are presented in Tables E.29-1, E.29-2, E.29-3, E.29-4, E.29-5, E.29-6, E.29-7, E.29-8, E.29-9, and E.29-10.
+
+**Table E.1-1: Uncertainty contributions in TRP measurement for anechoic chamber method**
+
+| <b>Description of uncertainty contribution</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | <b>Details in paragraph</b> |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|
+| <b>Stage 1, DUT measurement</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                             |
+| 1) Mismatch of receiver chain (i.e. between probe antenna and measurement receiver)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.2-E.3                     |
+| 2) Insertion loss of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.4-E.6                     |
+| 3) Influence of the probe antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.7                         |
+| 4) Uncertainty of the absolute antenna gain of the probe antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | E.8                         |
+| 5) Measurement Receiver: uncertainty of the absolute level                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | E.9                         |
+| 6) Measurement distance:<br>a) offset of DUT phase centre from axis(es) of rotation<br>b) mutual coupling between the DUT and the probe antenna<br>c) phase curvature across the DUT                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.10                        |
+| 7) Quality of quiet zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.11                        |
+| 8) DUT Tx-power drift                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.12                        |
+| 9) Uncertainty related to the use of phantoms: (applicable when a phantom is used):<br><br>If SAM head phantom is used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br><br>If SAM head and hand phantoms are used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a hand phantom is used:<br>a) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a laptop ground plane phantom is used:<br>a) Uncertainty related to the use of the Laptop Ground Plane phantom | E.13                        |
+| 10) Coarse sampling grid                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.14                        |
+| 11) Random uncertainty (repeatability, including positioning uncertainty of the DUT against the SAM phantom or DUT plugged into the Laptop Ground Plane phantom)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | E.15                        |
+| <b>Stage 2 , Calibration measurement, network analyzer method, figure B.2.1-1</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                             |
+| 13) Uncertainty of network analyzer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.16                        |
+| 14) Mismatch of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | E.2-E.3                     |
+| 15) Insertion loss of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.4-E.6                     |
+| 16) Mismatch in the connection of calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.2                         |
+| 17) Influence of the calibration antenna feed cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.7                         |
+| 18) Influence of the probe antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.7                         |
+| 19) Uncertainty of the absolute gain of the probe antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | E.8                         |
+| 20) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.17                        |
+| 21) Measurement distance:<br>a) Offset of calibration antenna's phase centre from axis(es) of rotation<br>b) Mutual coupling between the calibration antenna and the probe antenna<br>c) Phase curvature across the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.10                        |
+| 22) Quality of quiet zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | E.11                        |
+
+**Table E.1-2: Uncertainty contributions in TRP measurement for reverberation chamber method**
+
+| Description of uncertainty contribution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Details in paragraph |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| <b>Stage 1, DUT measurement</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |                      |
+| 1) Mismatch of receiver chain (i.e. between fixed measurement antenna and measurement receiver)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.2-E.3              |
+| 2) Insertion loss of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.4-E.6              |
+| 3) Influence of the fixed measurement antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.7                  |
+| 4) Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | E.8                  |
+| 5) Measurement Receiver: uncertainty of the absolute level                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | E.9                  |
+| 6) Chamber statistical ripple and repeatability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.28                 |
+| 7) Additional power loss in EUT chassis                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.29                 |
+| 8) DUT Tx-power drift                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.12                 |
+| 9) Uncertainty related to the use of phantoms: (applicable when a phantom is used):<br><br>If SAM head phantom is used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br><br>If SAM head and hand phantoms are used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a hand phantom is used:<br>a) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a laptop ground plane phantom is used:<br>a) Uncertainty related to the use of the Laptop Ground Plane phantom | E.13                 |
+| 10) Independent samples                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.14                 |
+| 11) Random uncertainty (repeatability, including positioning uncertainty of the DUT against the SAM phantom or DUT plugged into the Laptop Ground Plane phantom)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | E.15                 |
+| <b>Stage 2 , Calibration measurement, network analyzer method, figure B.2.2-1</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                      |
+| 12) Uncertainty of network analyzer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.16                 |
+| 13) Mismatch of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | E.2-E.3              |
+| 14) Insertion loss of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.4-E.6              |
+| 15) Mismatch in the connection of calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.2                  |
+| 16) Influence of the calibration antenna feed cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.7                  |
+| 17) Influence of the fixed measurement antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.7                  |
+| 18) Uncertainty of the absolute gain of the fixed measurement antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.8                  |
+| 19) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.17                 |
+| 20) Chamber statistical ripple and repeatability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | E.28                 |
+
+**Table E.1-3: Uncertainty contributions in TRS measurement for anechoic chamber method**
+
+| Description of uncertainty contribution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Details in paragraph |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| <b>Stage 1, DUT measurement</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                      |
+| 1) Mismatch of transmitter chain (i.e. between probe antenna and base station simulator)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.2-E.3              |
+| 2) Insertion loss of transmitter chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.4-E.6              |
+| 3) Influence of the probe antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | E.7                  |
+| 4) Uncertainty of the absolute antenna gain of the probe antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.8                  |
+| 5) Base station simulator: uncertainty of the absolute output level                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.18                 |
+| 6) BER measurement: output level step resolution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.19                 |
+| 7) Statistical uncertainty of BER measurement                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | E.20                 |
+| 8) BER data rate normalization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | E.21                 |
+| 9) Measurement distance:<br>a) offset of DUT phase centre from axis(es) of rotation<br>b) mutual coupling between the DUT and the probe antenna<br>c) phase curvature across the DUT                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.10                 |
+| 10) Quality of quiet zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.11                 |
+| 11) DUT sensitivity drift                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.22                 |
+| 12) Uncertainty related to the use of phantoms: (applicable when a phantom is used):<br><br>If SAM head phantom is used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br><br>If SAM head and hand phantoms are used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a hand phantom is used:<br>a) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a laptop ground plane phantom is used:<br>a) Uncertainty related to the use of the Laptop Ground Plane phantom | E.13                 |
+| 13) Coarse sampling grid                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.14                 |
+| 14) Random uncertainty (repeatability)<br>-positioning uncertainty of the DUT against the SAM or DUT plugged into the Laptop Ground Plane phantom                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | E.15                 |
+| <b>Stage 2 , Calibration measurement, network analyzer method, figure B.2.1-1</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |
+| 16) Uncertainty of network analyzer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.16                 |
+| 17) Mismatch in the connection of transmitter chain (i.e. between probe antenna and NA)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | E.2-E.3              |
+| 18) Insertion loss of transmitter chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | E.4-E.6              |
+| 19) Mismatch in the connection of calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.2                  |
+| 20) Influence of the calibration antenna feed cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.7                  |
+| 21) Influence of the probe antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.7                  |
+| 22) Uncertainty of the absolute gain of the probe antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.8                  |
+| 23) Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.17                 |
+| 24) Measurement distance:<br>a) Offset of calibration antenna's phase centre from axis(es) of rotation<br>b) Mutual coupling between the calibration antenna and the probe antenna<br>c) Phase curvature across the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                          | E.10                 |
+| 25) Quality of quiet zone                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.11                 |
+
+**Table E.1-4: Uncertainty contributions in Uncertainty contributions in TRS measurement for reverberation chamber method**
+
+| Description of uncertainty contribution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Details in paragraph |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|
+| <b>Stage 1, DUT measurement</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |                      |
+| 1) Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.2-E.3              |
+| 2) Insertion loss of transmitter chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | E.4-E.6              |
+| 3) Influence of the fixed measurement antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.7                  |
+| 4) Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | E.8                  |
+| 5) Base station simulator: uncertainty of the absolute output level                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.18                 |
+| 6) BER measurement: output level step resolution                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.19                 |
+| 7) Statistical uncertainty of BER measurement                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | E.20                 |
+| 8) BER data rate normalization                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | E.21                 |
+| 9) Chamber statistical ripple and repeatability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | E.28                 |
+| 10) Additional power loss in EUT chassis                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | E.29                 |
+| 11) DUT sensitivity drift                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | E.22                 |
+| 12) Uncertainty related to the use of phantoms: (applicable when a phantom is used):<br><br>If SAM head phantom is used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br><br>If SAM head and hand phantoms are used:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a hand phantom is used:<br>a) uncertainty of dielectric properties and shape of the hand phantom<br><br>If a laptop ground plane phantom is used:<br>a) Uncertainty related to the use of the Laptop Ground Plane phantom | E.13                 |
+| 14) Independent samples                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | E.14                 |
+| 13) Random uncertainty (repeatability)<br>- positioning uncertainty of the DUT against the SAM or DUT plugged into the Laptop Ground Plane phantom                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | E.15                 |
+| <b>Stage 2 , Calibration measurement, network analyzer method, figure B.2.2-1</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |                      |
+| 15) Uncertainty of network analyzer                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.16                 |
+| 16) Mismatch of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | E.2-E.3              |
+| 17) Insertion loss of receiver chain                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.4-E.6              |
+| 18) Mismatch in the connection of calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.2                  |
+| 19) Influence of the calibration antenna feed cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | E.7                  |
+| 20) Influence of the fixed measurement antenna cable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | E.7                  |
+| 21) Uncertainty of the absolute gain of the fixed measurement antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.8                  |
+| 22) Uncertainty of the absolute gain/ radiation efficiency of the calibration antenna                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | E.17                 |
+| 23) Chamber statistical ripple and repeatability                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | E.28                 |
+
+## E.2 Mismatch uncertainty between measurement receiver and the probe antenna
+
+If the same chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant  $\textcircled{P}$  0.00dB value.
+
+If it is not the case, this uncertainty contribution has to be taken into account and determined by the following method.
+
+In a measurement configuration, when two elements (devices, networks...) are connected, if the matching is not ideal, there is an uncertainty in the RF level signal passing through the connection. The magnitude of the uncertainty depends on the VSWR at the junction of the two connectors. In practical measurement system there are probably several connections in a test set-up, they will all interact and contribute to the combined mismatch uncertainty.
+
+The total combined mismatch uncertainty is composed of 2 parts:
+
+- 1) The mismatch through the connector between two elements
+- 2) The mismatch due to the interaction between two elements
+
+### E.2.1 Total combined mismatch uncertainty calculations
+
+#### E.2.1.1 Mismatch uncertainty through the connector between two elements
+
+Hereunder, a measurement configuration:
+
+![Diagram showing a Measurement receiver (M.R) connected to Cable4 via a connector. The reflection coefficient of the Measurement Receiver is labeled as Γ_MR and the reflection coefficient of the cable is labeled as Γ_cable4. The connector is represented by two triangles pointing towards each other.](6c15b3646c84efa0bf1374ca87ef74f8_img.jpg)
+
+```
+
+graph LR
+    MR[Measurement receiver (M.R)] -- "Γ_MR" --- C(( ))
+    C -- "Γ_cable4" --- Cable4[Cable4]
+    Cable4 -.-> Dots[...]
+  
+```
+
+Diagram showing a Measurement receiver (M.R) connected to Cable4 via a connector. The reflection coefficient of the Measurement Receiver is labeled as Γ\_MR and the reflection coefficient of the cable is labeled as Γ\_cable4. The connector is represented by two triangles pointing towards each other.
+
+**Figure E.2.1.1-1: Mismatch uncertainty through the connector**
+
+$\Gamma_{MR}$  is the complex reflection coefficient of the Measurement Receiver
+
+$\Gamma_{cable4}$  is the complex reflection coefficient of the cable4
+
+$S_{21}$  is the forward gain in the network between the two reflection coefficients of interest
+
+$S_{12}$  is the backward gain in the network between the two reflection coefficients of interest
+
+Note that  $S_{21}$  and  $S_{12}$  are set to 1 if the two parts are directly connected.
+
+The uncertainty limits of the mismatch are calculated by means of the following formula table 1 of [26]:
+
+Mismatch limits(% voltage) =
+
+These mismatch limits are divided by because of the U-shaped (table 1 of) [26] distribution of the mismatch uncertainty and give the following standard uncertainty:
+
+$$U_{\text{mismatch}} (\% \text{ voltage}) =$$
+
+To convert this standard uncertainty in dB, we divide it by the standard uncertainty conversion factor (table 1 of) [26]:
+
+$$U_{\text{mismatch}}(\text{dB}) =$$
+
+#### E.2.1.2 Mismatch uncertainty due to the interaction of several elements
+
+Previously, we presented how to determine the mismatch uncertainty between two elements through the junction (connector). Now, we introduce the other type of mismatch uncertainty, which is a result of the interaction between several elements.
+
+Hereunder, a measurement configuration:
+
+![Figure E.2.1.2-1: Mismatch uncertainty due to the interaction of several elements. The diagram shows a Measurement Receiver (M.R) connected to Cable3, which is connected to Cable4. The reflection coefficients are labeled as Γ_MR, Γ_cable3, and Γ_cable4. The S-parameters for Cable3 are labeled as S21 and S12.](3d6d0738981fdd03d003cc653bdfdaae_img.jpg)
+
+Figure E.2.1.2-1: Mismatch uncertainty due to the interaction of several elements. The diagram shows a Measurement Receiver (M.R) connected to Cable3, which is connected to Cable4. The reflection coefficients are labeled as Γ\_MR, Γ\_cable3, and Γ\_cable4. The S-parameters for Cable3 are labeled as S21 and S12.
+
+**Figure E.2.1.2-1: Mismatch uncertainty due to the interaction of several elements**
+
+Firstly, we determine the mismatch uncertainty between junctions of the elements:
+
+Between the MR and the cable3:
+
+$$U_{\text{mismatch1}}(\text{dB}) =$$
+
+Between the cable3 and the cable4:
+
+$$U_{\text{mismatch2}}(\text{dB}) =$$
+
+$|S_{21}|$  and  $|S_{12}|$  are set to 1 because there is no element between cable3 and cable 4.
+
+$$U_{\text{mismatch1}}(\text{dB}) =$$
+
+$$U_{\text{mismatch2}}(\text{dB}) =$$
+
+Each mismatch uncertainty due to the interaction between the measurement receiver and the cable4 is determined by means of the following formula (table 1 of) [26]:
+
+$$U_{\text{mismatch\_interaction1}}(\text{dB}) =$$
+
+$|S_{21}|$  and  $|S_{12}|$  are equal and correspond to the cable3 attenuation.
+
+$$U_{\text{mismatch\_interaction1}}(\text{dB}) =$$
+
+We consider in the general case, the following measurement configuration:
+
+![Figure E.2.1.2-2: Mismatch uncertainty measurement configuration. The diagram shows a Measurement Receiver (MR) connected to Cable1, which is connected to CableN, which is connected to an Antenna. The reflection coefficients are labeled as Γ_MR, Γ_cable1, Γ_cableN, and Γ_antenna. The S-parameters for Cable1 are labeled as S21cable1 and S12cable1, and for CableN as S21cableN and S12cableN.](de59a02f54f1fb9194f5fc07ba908a03_img.jpg)
+
+Figure E.2.1.2-2: Mismatch uncertainty measurement configuration. The diagram shows a Measurement Receiver (MR) connected to Cable1, which is connected to CableN, which is connected to an Antenna. The reflection coefficients are labeled as Γ\_MR, Γ\_cable1, Γ\_cableN, and Γ\_antenna. The S-parameters for Cable1 are labeled as S21cable1 and S12cable1, and for CableN as S21cableN and S12cableN.
+
+**Figure E.2.1.2-2: Mismatch uncertainty measurement configuration**
+
+In the general case, this uncertainty contribution can be calculated by:
+
+$$U_{\text{mismatch\_interaction\_N}}(\text{dB}) =$$
+
+$|S_{21}| = |S_{12}|$  for passive elements (cables...)
+
+$$U_{\text{mismatch\_interaction\_N}}(\text{dB}) =$$
+
+## E.2.2 Total combined mismatch uncertainty
+
+The two kinds of mismatch uncertainty contributions are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty.
+
+The total combined mismatch uncertainty is equal to:
+
+This formula shows that the uncertainty is frequency dependent by the way of the forward and the backward gains in the network between the two components. The uncertainty upon  $|S_{21}|$  and  $|S_{12}|$  increases with frequency. One can therefore expect for the UMTS band a higher mismatch uncertainty value than in the GSM and DCS bands.
+
+Note that for an anechoic chamber, horn antennas are usually used as probe antennas. There are two kinds of horn antennas: single-polarized and dual-polarized. With the second one, it is possible to measure the co-polarized and cross-
+
+polarized signals without any movement of the probe, which reduces the cable antenna uncertainty contribution and improves the measurement stability.
+
+To conduct the signals to the measurement receiver, the measurement system configuration using a dual-polarized horn antenna has to be completed with an RF Relay. This device will include new mismatch uncertainty contributions, which have to be determined with the previously presented calculation methods, completed by the RF relay parameters contributions, and described in the following.
+
+### E.3 Mismatch uncertainty of the RF relay
+
+If the same receiver chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant  $\textcircled{\ominus}$  0.00dB value.
+
+If it is not the case, this uncertainty contribution has to be taken into account and determined by the following method.
+
+The following figure describes the RF Relay with its 'S' parameters and the complex reflection coefficient of the inputs and output:
+
+![Schematic diagram of an RF Relay showing its S-parameters and reflection coefficients. The central 'RF Relay' block has three ports. Port 1 (left) is connected to 'Input 1 device' with reflection coefficient Γ1. Port 2 (bottom) is connected to 'Input 2 Device' with reflection coefficient Γ2. Port 3 (right) is connected to 'Output Device' with reflection coefficient Γ3. S-parameters are indicated by arrows: S11 (reflection at port 1), S21 (transmission from port 1 to port 2), S31 (transmission from port 1 to port 3), S12 (transmission from port 2 to port 1), S22 (reflection at port 2), S32 (transmission from port 2 to port 3), S13 (transmission from port 3 to port 1), S23 (transmission from port 3 to port 2), and S33 (reflection at port 3).](04e646ff9ef67d2f89414607117fd258_img.jpg)
+
+Schematic diagram of an RF Relay showing its S-parameters and reflection coefficients. The central 'RF Relay' block has three ports. Port 1 (left) is connected to 'Input 1 device' with reflection coefficient Γ1. Port 2 (bottom) is connected to 'Input 2 Device' with reflection coefficient Γ2. Port 3 (right) is connected to 'Output Device' with reflection coefficient Γ3. S-parameters are indicated by arrows: S11 (reflection at port 1), S21 (transmission from port 1 to port 2), S31 (transmission from port 1 to port 3), S12 (transmission from port 2 to port 1), S22 (reflection at port 2), S32 (transmission from port 2 to port 3), S13 (transmission from port 3 to port 1), S23 (transmission from port 3 to port 2), and S33 (reflection at port 3).
+
+Figure E.3-1: Mismatch uncertainty of the RF relay
+
+The RF relay is used to switchover the cross and direct polarization signals from the probe antenna. To determine RF Relay mismatch uncertainty contributions, reflection coefficients for each port and the cross talk attenuation have to be known.
+
+The total combined mismatch uncertainty is composed of two parts:
+
+- 1) The mismatch uncertainty contributions when the RF Relay switches on the direct polarization signal
+- 2) The mismatch uncertainty contributions when the RF Relay switches on the cross polarization signal
+
+Each part is composed of two types of uncertainties introduced in the previous paragraph: the mismatch through the connector between two elements and the mismatch due to the interaction between several elements.
+
+#### E.3.1 First part: RF Relay switched on the co-polarized signal
+
+##### E.3.1.1 The mismatch through the connector between two elements
+
+Between the Input1 and the port1:
+
+$$U_{\text{mismatch1}}(\text{dB}) =$$
+
+Between the port3 and the Output:
+
+$$U_{\text{mismatch2}}(\text{dB}) =$$
+
+Between the Input2 and the port2:
+
+The RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution.
+
+### E.3.1.2 Mismatch due to the interaction between two elements or more
+
+Between the Input1 and the Output:
+
+$$U_{\text{interaction1}}(\text{dB}) =$$
+
+Between the Input1 and the Input2:
+
+$$U_{\text{interaction2}}(\text{dB}) =$$
+
+The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered.
+
+Between the Input2 and the Output:
+
+$$U_{\text{interaction3}}(\text{dB}) =$$
+
+The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high cross-talk attenuation, which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered.
+
+## E.3.2 Second part: RF relay switched on the cross-polarized signal
+
+### E.3.2.1 The mismatch through the connector between two elements
+
+Between the Input1 and the port1:
+
+The RF Relay switchovers on the direct polarization signal. As a result, there is no mismatch uncertainty contribution.
+
+Between the port3 and the Output:
+
+$$U_{\text{mismatch3}}(\text{dB}) =$$
+
+Between the Input2 and the port2:
+
+$$U_{\text{mismatch4}}(\text{dB}) =$$
+
+### E.3.2.2 Mismatch due to the interaction between two elements or more
+
+Between the Input1 and the Output:
+
+$$U_{\text{interaction4}}(\text{dB}) =$$
+
+The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered.
+
+Between the Input1 and the Input2:
+
+$$U_{\text{interaction5}}(\text{dB}) =$$
+
+The RF Relay switchovers on the cross polarization signal. As a result; this uncertainty contribution is usually disregarded because of the high crosstalk attenuation which is characterized by 'S' parameters. If the crosstalk attenuation is low, this uncertainty contribution has to be considered.
+
+Between the Input2 and the Output:
+
+$$U_{\text{interactions6}}(\text{dB}) =$$
+
+## E.3.3 Total combined mismatch uncertainty
+
+Each non-zero mismatch uncertainty contribution from both parts (RF Relay switched on the cross and direct polarization signal) are combined by the root-sum-squares (RSS) method to derive the total combined mismatch uncertainty.
+
+The total combined mismatch uncertainty is equal to:
+
+If a RF Relay is used to drive the cross and direct polarization signals from the dual-polarized antenna, this total combined mismatch uncertainty has to be added with all the uncertainty measurement contributions for the total combined measurement uncertainty.
+
+## E.4 Insertion loss of the probe antenna cable
+
+If the probe antenna cable does not move between the calibration and the DUT measurement stage, the uncertainty due to the insertion loss of the cable is assumed to be systematic. Moreover, this uncertainty is common and constant in both stages and that is why this leads to 0.00dB value.
+
+If a different cable is used in the calibration measurement and in the DUT measurement, and the difference of the insertion loss is used in the calculations, then the overall combined standard uncertainty of the insertion loss measurement should be used in the uncertainty budget. The distribution of this uncertainty is assumed to be rectangular, in which case the standard uncertainty can be calculated as the maximum value/ $\sqrt{3}$ .
+
+## E.5 Insertion loss of the probe antenna attenuator (if used)
+
+See Insertion loss of the probe antenna cable
+
+If the probe antenna attenuator is used in both stages, the uncertainty is considered systematic and constant  $\textcircled{/}$  0.00dB value.
+
+## E.6 Insertion loss of the RF relays (if used)
+
+See Insertion loss of the probe antenna cable.
+
+If the RF relay is used in both stages, the uncertainty is considered systematic and constant  $\textcircled{/}$  0.00dB value.
+
+## E.7 Influence of the antenna cable
+
+### E.7.1 Probe antenna cable
+
+If the probe antenna is directional (i.e. peak gain  $>+5\text{dBi}$  e.g. horn, LPDA, etc.) and the same probe antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant  $\textcircled{/}$  0.00dB value.
+
+In other cases a technical study should be done.
+
+An ETSI technical report [25] (clause D.1.3.6) gives a discussion on the results obtained by testing a vertically polarized biconical antenna over a ground plane with differing RF cable configurations.
+
+### E.7.2 Calibration antenna cable
+
+If an efficiency calibration is performed, influence of the calibration antenna feed cable can be assumed to be negligible, due to data averaging.
+
+In the case of gain calibration, the influence of the calibration antenna feed cable must be assessed by measurements. A gain calibration measurement is repeated with a reasonably differing routing of the feed cable. Largest difference between the results is entered to the uncertainty budget with a rectangular distribution.
+
+## E.8 Absolute gain of the probe antenna
+
+The uncertainty appears in the both stages and it is thus considered systematic and constant 0.00dB value.
+
+## E.9 Measurement receiver: uncertainty of absolute level
+
+The receiving device is used to measure the received signal level in TRP tests either as an absolute level or as a relative level. Receiving device used is typically a Base Station Simulator (BSS), spectrum analyzer (SA), or power meter (PM). Generally there occurs an uncertainty contribution from limited absolute level accuracy and non-linearity.
+
+## E.10 Measurement distance
+
+The uncertainty contribution from a finite measurement distance is estimated in three parts.
+
+### E.10.1 Offset of DUT phase centre from axis(es) of rotation
+
+In all the measurements defined in this test procedure the DUT and phantom combination is rotated about the ear reference point of SAM phantom, which is also assumed to be the location of the phase centre in both angular directions of the measurements.
+
+For some turntables this may be practically impossible in which case a measurement uncertainty contribution can arise because the phase centre will rotate on a non-zero radius about the centre of rotation, thereby giving a variable measurement distance. Data averaging process may lead to a partial self-cancel of this uncertainty.
+
+The following formula is used to estimate this uncertainty contribution in stage 1:
+
+$$U_{\text{phase\_center\_limits}} \text{ (dB)} =$$
+
+If a gain calibration is performed in Stage 2, the uncertainty contribution of calibration antenna's displacement is estimated with the previous formula. Misalignment can be estimated with following formula,
+
+$$U_{\text{misalignment}} \text{ (dB)} = ,$$
+
+where  $\alpha$  is the misalignment angle between the calibration antenna and the probe antenna. The contribution shall be added to displacement error:
+
+$$U_{\text{cal}} \text{ (dB)} =$$
+
+For an efficiency calibration with an omnidirectional calibration antenna, the  $U_{\text{cal}}$  is calculated similarly as for gain calibration but the uncertainty may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration.
+
+### E.10.2 Mutual coupling
+
+In measurement of radio performances of UMTS mobile phones in speech mode, the mutual coupling uncertainty for this frequency band is a 0.00dB value (see annex A-2 in [27]).
+
+The 0.00dB value can be extended for the GSM, DCS and PCS band frequencies.
+
+### E.10.3 Phase curvature
+
+This uncertainty originates from the finite far-field measurement distance, which causes phase curvature across the DUT. If the measurement distance is  $> 10\lambda$ , this error is assumed to be negligible. At 2 GHz  $\lambda$  is 0.15 m, thus  $10\lambda$  is 1.5 m.
+
+## E.11 Quality of quiet zone
+
+The uncertainty contribution of the reflectivity level of the anechoic chamber is determined from the average standard deviation of the electric field in the quiet zone. By repeating a free space VSWR measurement in 15-degree grid in elevation and azimuth, 264 standard deviation values in both polarizations are determined. From these values average standard deviation of electric field in the quiet zone can be calculated from the equation:
+
+Where
+
+is number of angular intervals in elevation,
+
+is number of angular intervals in azimuth and
+
+is elevation of single measurement.
+
+If an efficiency calibration with omnidirectional calibration antenna is performed, the effect of reflectivity level decreases in Stage 2 and may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. Efficiency calibration done with sampling step  $\leq 15^\circ$ , can be considered to have at least four independent samples.
+
+It's likely that asymmetry of the field probe will have a very small impact on this measurement uncertainty contributor; however, an upper bound to probe symmetry should be considered.
+
+## E.12 Tx-power drift of DUT
+
+A single point power reference measurement in the beginning and at the end of the measurement procedure is recommended to monitor the power drift of the DUT. Based on TX-power drift measurements for typical 3G UE, an uncertainty of 0.2 dB shall be entered to uncertainty budget with a rectangular distribution. If the drift measurement indicates larger drift, the actual drift shall be included to uncertainty.
+
+In order to minimize Tx-power drift error it's recommended to interleave sensitivity and power measurement of multiple channels. This spreads the measurements over a longer period, which helps to average the drift of the TX-power.
+
+Typical TX-power drifts of 3G UE, measured in a single angular point, DUT placed against phantom head are shown in Figure E.12-1.
+
+![Figure E.12-1: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple lines represent different measurements, showing initial fluctuations followed by a stable period near 0 dB. One line shows a significant negative drift after 90 minutes, reaching approximately -0.3 dB at 105 minutes.](b2104007a82f0ebebd231761342dc089_img.jpg)
+
+Figure E.12-1: Output power variation of typical 3G UE during battery life. The graph shows Power [dB] on the y-axis (from -0.6 to 0.6) versus Time [min] on the x-axis (from 0 to 165). Multiple lines represent different measurements, showing initial fluctuations followed by a stable period near 0 dB. One line shows a significant negative drift after 90 minutes, reaching approximately -0.3 dB at 105 minutes.
+
+Figure E.12-1: Output power variation of typical 3G UE during battery life
+
+## E.13 Uncertainty related to the use of phantoms
+
+### E.13.1 Uncertainty from using different types of SAM phantom
+
+This uncertainty contribution originates from the fact that different laboratories may use the two different versions of SAM head: the SAM head phantom or the SAM phantom including the head and the shoulders. The standard SAM head is the specified phantom. However, the use of the other type of SAM is also allowed with the requirement that the resulting uncertainty contribution is taken into account in the uncertainty budget.
+
+### E.13.2 Simulated tissue liquid uncertainty
+
+This uncertainty will occur, if the laboratory uses a liquid which has dielectric parameters deviating more than  $\pm 15\%$  of the target parameters.
+
+### E.13.3 Uncertainty of dielectric properties and shape of the hand phantom
+
+The hand phantom makes a contribution to OTA measurement uncertainty due to the manufacturing tolerances of its dielectric properties and shape. The dielectric properties on the surface of the hand may differ from those of its interior, so both are included in the evaluation. The moulded exterior surface of the hand shall be measured directly with an open-ended coaxial probe. The interior hand material is evaluated indirectly, by substituting a cube-shaped sample moulded from the same material and having some exterior surfaces removed. Following procedure will be used to evaluate the dielectric properties of the hand phantom;
+
+1. Each hand shall be manufactured together with a reference cube of the same material. The sides of the reference cube shall be not less than 40 mm in length.
+2. The moulded surface on three orthogonal sides of the cube shall be sliced away to a depth of at least 3 mm, in order to expose interior material for evaluation. The remaining three sides of the cube shall be left untreated.
+3. Relative permittivity and conductivity shall be measured at ten different points on each of the three cut, exposed surfaces of the reference cube, and the combined interior averages ( $\varepsilon_{int\ avg}$ ,  $\sigma_{int\ avg}$ , 30 points) and standard deviations ( $\varepsilon_{int\ std}$ ,  $\sigma_{int\ std}$ , 30 points) shall be calculated. Individual interior averages for each of these three sides ( $\varepsilon_{int\ i}$ ,  $\sigma_{int\ i}$ , 10 points) shall also be calculated.
+4. Relative permittivity and conductivity shall be measured at ten points on the hand phantom exterior. A measurement point shall be located to each fingertip or as close to the tip as applicable. One measurement point shall be located to the back of the hand and one to the inner surface of wrist area. The exterior averages ( $\varepsilon_{ext\ avg}$ ,  $\sigma_{ext\ avg}$ , 10 points) and standard deviations ( $\varepsilon_{ext\ std}$ ,  $\sigma_{ext\ std}$ , 10 points) calculated accordingly.
+5. The total averages ( $\varepsilon_{avg}$ ,  $\sigma_{avg}$ ) shall be calculated as the average of exterior and interior values by either evaluating all data points or using equations :  $\varepsilon_{avg} = \frac{\varepsilon_{ext\ avg} + 3 \cdot \varepsilon_{int\ avg}}{4}$  ,  $\sigma_{avg} = \frac{\sigma_{ext\ avg} + 3 \cdot \sigma_{int\ avg}}{4}$
+6. The total standard deviations ( $\varepsilon_{std}$ ,  $\sigma_{std}$ ) shall be calculated as the statistical combination of exterior and interior values by either evaluating all data points or using equations:
+
+$$\varepsilon_{std} = \sqrt{\frac{1}{4} \left( \varepsilon_{ext\ std}^2 + \varepsilon_{int\ std}^2 + 3 \cdot \left( \varepsilon_{ext\ avg}^2 + \varepsilon_{int\ avg}^2 \right) \right) - \varepsilon_{avg}^2}$$
+
+$$\sigma_{std} = \sqrt{\frac{1}{4} \left( \sigma_{ext\ std}^2 + \sigma_{int\ std}^2 + 3 \cdot \left( \sigma_{ext\ avg}^2 + \sigma_{int\ avg}^2 \right) \right) - \sigma_{avg}^2}$$
+
+7. The hands are acceptable for radiated performance testing, i.e., meet the minimal requirements, if
+  - a.  $\varepsilon_{avg}$  deviate by less than 15% from the target values
+  - b.  $\sigma_{avg}$  deviate by less than 25% from the target values
+
+- c. the difference between the averaged permittivity of each 10-point interior surface  $\varepsilon_{int\ avg}$  deviates by less than 10% and  $\varepsilon_{ext\ avg}$  by less than 20% from the total average  $\varepsilon_{avg}$
+  - d. the difference between the averaged conductivity of each 10-point interior surface  $\delta_{int\ avg}$  deviates by less than 20% and  $\sigma_{ext\ avg}$  by less than 30% from the total average  $\sigma_{avg}$
+  - e. the standard deviation of the combined measurements (30 interior points and 10 exterior points) is less than 20% for permittivity  $\varepsilon_{std}$  and less than 40% for conductivity  $\sigma_{std}$
+8. For the hands meeting the minimal requirements of step 7, the following approximations shall be used to determine the hand uncertainty due to dielectric properties.
+
+$$U_{\varepsilon}[dB] = c_1 * \left[ 10 * \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta\varepsilon_{avg}^2 + \varepsilon_{unc}^2 + (a_1\varepsilon_{std})^2}}{\varepsilon} \right| \right) \right]$$
+
+$$U_{\sigma}[dB] = c_2 * \left[ 10 * \log_{10} \left( 1 + \left| \frac{\sqrt{\Delta\sigma_{avg}^2 + \sigma_{unc}^2 + (a_1\sigma_{std})^2}}{\sigma} \right| \right) \right]$$
+
+$\Delta\varepsilon_{avg}$ ,  $\Delta\sigma_{avg}$ ,  $\varepsilon_{std}$ ,  $\sigma_{std}$  are the values determined as defined above and  $\varepsilon_{unc}$  and  $\sigma_{unc}$  are expanded measurement uncertainties ( $k = 2$ ) of the dielectric parameter measurement method. The cube will be provided together with the hand such that the user can evaluate if the interior (cube) properties of the hand has degenerated over time by performing the test above. Coefficient  $c_1 = 0.78$ ,  $c_2 = 0.39$  and  $a_1 = 0.50$  were determined by numeric simulations.
+
+In case the hand phantoms are manufactured within CAD models, the tolerance is 2% and therefore the effects shape errors are negligible. If the tolerance is larger, a numerical study must be conducted.
+
+## E.13.4 Uncertainty from using different types of Laptop Ground Plane phantom
+
+This uncertainty contribution originates from the fact that different laboratories may use different variations of Laptop Ground Plane phantom. The standard Laptop Ground Plane is the specified phantom.
+
+## E.14 Coarse sampling grid
+
+Degreasing of sampling density to finite amount of samples affects the measurement uncertainty by two different errors. First is due to inadequate number of samples and second is a systematic discrimination approximation error in TRP and TRS equations.
+
+Figure E.14-1 shows simulated sampling grid errors for typical 3G UE. Approximation error is not included. Simulations are based on thin plate surface interpolation of real radiation patters, measured beside a phantom head.
+
+![Sampling Grid Error graph showing Standard Deviation of TRP/TRS [dB] vs Sample Step [°].](bf4c705bba1ea48c6e9cace4844d01c4_img.jpg)
+
+This line graph, titled "Sampling Grid Error", plots the "Standard Deviation of TRP/TRS [dB]" on the y-axis (ranging from 0.00 to 0.25) against the "Sample Step [°]" on the x-axis (ranging from 0 to 45). Multiple data series are shown, each represented by a line with open circle markers. All series start at 0.00 dB at a 0° sample step. As the sample step increases, the standard deviation for all series increases. The curves diverge after approximately 15°, with the highest curve reaching about 0.25 dB at a 45° sample step and the lowest reaching about 0.10 dB at the same step.
+
+Sampling Grid Error graph showing Standard Deviation of TRP/TRS [dB] vs Sample Step [°].
+
+Figure E.14-1: Simulated TPR/TRS error as a function of sampling grid
+
+The offset of systematic approximation error can be expressed by using formula
+
+where
+
+is number of angular intervals in elevation,
+
+is elevation.
+
+![Sampling Grid Error graph showing Offset of TRP/TRS [dB] vs Sample Step [°].](47986c416bf25e0ac912000ff02b358c_img.jpg)
+
+This line graph, also titled "Sampling Grid Error", plots the "Offset of TRP/TRS [dB]" on the y-axis (ranging from -0.25 to 0) against the "Sample Step [°]" on the x-axis (ranging from 0 to 45). A single data series is shown, represented by a line with open circle markers. The series starts at 0 dB at a 0° sample step and remains very close to 0 dB until about 10°. Beyond 10°, the offset becomes increasingly negative, following a smooth downward curve that reaches approximately -0.23 dB at a 45° sample step.
+
+Sampling Grid Error graph showing Offset of TRP/TRS [dB] vs Sample Step [°].
+
+Figure E.14-2: Approximation error of TRP/TRS
+
+The 10° or 15° sampling grid used in TRP measurements has been shown to introduce only very small differences as compared to the results obtained with denser grids, so with that sampling grid the uncertainty contribution can be assumed negligible.
+
+When using sample step size of 15° - 30°, standard uncertainty of 0.15dB can be assumed to cover errors. If step size >30° is used, larger uncertainty should be considered.
+
+NOTE: the simulation results presented here are not usable for irregular sampling grids or in the case of MEG/MERS.
+
+## E.15 Random uncertainty
+
+The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference DUT without changing anything in the measurement set-up.
+
+The random uncertainty differs from one laboratory to another. Moreover, each DUT has its own electromagnetic behaviour and random uncertainty. Some uncertainty also occurs from the positioning of the DUT against the SAM phantom, as the DUT cannot be attached exactly in the same way every time. This uncertainty depends on how much the DUT's positioning against the SAM phantom and hand phantoms varies from the specified testing positions. It is noted that the uncertainty of the phone positioning depends on the phone holder and the measurement operator and is in fact difficult to distinguish from random uncertainty. Some uncertainty also occurs from the positioning of the DUT plugged into the Laptop Ground Plane phantom, as the DUT may not be plugged into the USB connector and positioned exactly in the same way every time. This uncertainty depends on how much the DUT's position plugged into the Laptop Ground Plane phantom varies from the specified plug-in position. Therefore, the positioning uncertainty is included in random uncertainty.
+
+To estimate this uncertainty for the SAM phantom, it is suggested to perform at least five evaluations of TRP/TRS whereby the device shall be dismounted and newly positioned with a fully charged battery before each test. This measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three phones with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized value.
+
+With head and hand phantoms, random uncertainty evaluation may be done separately for each measurement configuration i.e. head only, browsing mode or speech mode. A speech mode random uncertainty evaluation, where both head and hand phantoms are used, can reasonably be considered to be the worst-case scenario and thus random uncertainties in other configurations to be less.
+
+To estimate this uncertainty for the Laptop Ground Plane phantom, it is suggested to perform at least five evaluations of TRP/TRS for the plug-in position whereby the device shall be dismounted and newly positioned before each test. This measurement set has to be carried out in mid channel of lowest and highest frequency bands utilized by the testing lab, for at least three USBs with different type of mechanical design. The values have to be normalized by the mean for each measurement set. As a result the uncertainty contribution entered to uncertainty budget is the difference between the maximum and minimum normalized value.
+
+## E.16 Uncertainty of network analyzer
+
+This uncertainty includes the all uncertainties involved in the S21 measurement with a network analyzer, and will be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed, (see clause 5.1.2 in [26]).
+
+## E.17 Uncertainty of the gain/efficiency of the calibration antenna
+
+The calibration antenna only appears in Stage 2. Therefore, the gain/efficiency uncertainty has to be taken into account.
+
+This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [26]).
+
+If the manufacturer's data do not give the information, the value has to be checked, see annex A-12 in [27].
+
+## E.18 Base station simulator: uncertainty of the absolute level
+
+The transmitter device (typically a BS Simulator) is used to drive a signal to the horn antenna in sensitivity tests either as an absolute level or as a relative level. Receiving device used is typically a UE/MS. Generally there occurs uncertainty contribution from limited absolute level accuracy and non-linearity of the BS Simulator.
+
+For practical reasons, the calibration measurement (Stage 2) should be only performed with the probe antenna as a receiver. Hence, the uncertainty on the absolute level of the transmitter device cannot be assumed as systematic. This uncertainty should be calculated from the manufacturer's data in logs with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [26]). Furthermore, the uncertainty of the non-linearity of the device is included in the absolute level uncertainty.
+
+## E.19 BER measurement: output level step resolution
+
+When output power of the BS simulator is swept to reach the BER target, used power step resolution creates this uncertainty. Output power step used in the BER measurement is divided by factor 2 to obtain the uncertainty with rectangular distribution.
+
+## E.20 Statistical uncertainty of the BER measurement
+
+To study statistical uncertainty of BER measurement, see ETSI document TR 100 028-1, section 6.6 [25]. For a BER target of  $1\% \pm 0.2\%$  using 20000 bits, uncertainty of 0.19 dB for a single measurement can be used. Using a BER target of  $10\% \pm 2\%$  with 20000 tested bits will lead to uncertainty of 0.46dB/single measurement.
+
+For a full TRS measurement with a regular sampling grid, the statistical uncertainty can be approximated by using the following formula:
+
+$$,$$
+
+Where
+
+is the statistical uncertainty of single measurement,
+
+is the number of measurements.
+
+## E.21 BER data rate normalization uncertainty
+
+This uncertainty occurs only when a higher data rate than 12.2kbps is used to speed up TRS measurement. It can be calculated using following formula:
+
+$$,$$
+
+Where
+
+is the statistical uncertainty of the used reference measurement,
+
+is the statistical uncertainty of the higher data rate measurement,
+
+Is the number of measured reference points.
+
+## E.22 DUT sensitivity drift
+
+Due to statistical uncertainty of BER measurement, drift in the TRS cannot be monitored similarly to TRP. An uncertainty value of 0.2dB can be used, or the TRS drift should be measured, with a setup corresponding to the actual TRS measurement.
+
+## E.23 Cable loss measurement uncertainty
+
+Before performing the calibration, cable losses have to be measured. This measurement includes a standard uncertainty, which is composed of the mismatch, and the insertion loss uncertainties. In the calibration measurement, the transmitter part is composed with the calibration antenna, cables, and signal generator. The receiver part is composed with the probe antenna, cables, and measurement device.
+
+The cable loss of transmitter and receiver parts should be measured separately. By this way, the cable losses will be compliant with the cable routing of the calibration stage. On the opposite, if the cable losses were measured together at the same time, the measured values would include errors from miscellaneous mismatch contributions, which do not appear in the cable routing of the calibration stage.
+
+The cable loss measurement uncertainty is the result of the RSS of the uncertainty contributions listed in Table E.23-1.
+
+**Table E.23-1: Uncertainty contributions in the cable loss measurement**
+
+| <b>Description of uncertainty contribution</b>       | <b>Standard Uncertainty (dB)</b> |
+|------------------------------------------------------|----------------------------------|
+| Mismatch uncertainty of cable(s) receiver part       |                                  |
+| Insertion loss of the cable(s) receiver part         |                                  |
+| Measurement device: absolute level uncertainty       |                                  |
+| Measurement device: linearity                        |                                  |
+| Mismatch uncertainty of cable(s) transmitter part    |                                  |
+| Insertion loss of the cable(s) transmitter part      |                                  |
+| Signal generator: absolute output level uncertainty  |                                  |
+| Signal generator: output level stability uncertainty |                                  |
+| Cable loss measurement uncertainty (RSS)             |                                  |
+
+## E.24 Signal generator: uncertainty of the absolute output level
+
+The signal generator is only used at this stage. It substitutes the DUT by feeding the calibration antenna with a known power level. The use of this signal generator introduces an uncertainty on the absolute output level.
+
+This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [26]).
+
+## E.25 Signal generator: output level stability
+
+The uncertainty on the output level stability has to be taken into account only when the uncertainty of the absolute level is not considered.
+
+This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [26]).
+
+## E.26 Insertion loss: calibration antenna feed cable
+
+The feed cable of the calibration antenna only appears in Stage 2. As a result, this uncertainty has to be taken into account.
+
+This uncertainty will be measured or calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [26]).
+
+## E.27 Insertion loss: calibration antenna attenuator (if used)
+
+If a calibration antenna attenuator is used, it only appears in Stage 2. As a result, this uncertainty has to be taken into account.
+
+This uncertainty will be calculated from the manufacturer's data in logs with a rectangular distribution (see clause 5.1.2 in [26]).
+
+## E.28 Chamber Statistical Ripple and Repeatability
+
+The uncertainty due to chamber statistics is determined by repeated calibration measurements as described in Annex G. This uncertainty contribution is a composite value consisting of most of the specific reverberation chamber contributions, such as limited number of modes and mode-stirring techniques.
+
+The uncertainty contribution value shall be determined by measurements as described in Annex G and be assumed to have a normal distribution.
+
+## E.29 Additional Power Loss in EUT Chassis
+
+When the EUT is small and do not add noticeable loss to the chamber, the calibration procedure outlined in clause x.x, is performed without the EUT present in the chamber. The possible difference in average chamber transmission level between the EUT measurement and the reference measurement must in this case be considered in the uncertainty evaluation.
+
+The uncertainty value for this contribution can be tested empirically by choosing a unit within a set of samples which is considered to incur the highest amount of loss (normally the largest unit), and measure the average transmission loss in the chamber with and without the test unit present in the chamber. The difference between the two cases shall be used in the uncertainty calculation and the distribution should be assumed to be rectangular.
+
+Alternatively, a fixed value of 0.2 dB with a rectangular distribution can be used in the uncertainty calculations.
+
+**Table E.29-1: Example of uncertainty budget for head only TRP measurement for anechoic chamber method**
+
+| Uncertainty Source                                                            | Comment                                                                                | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                              |                                                                                        |                        |            |     |    |                           |
+| 1) Mismatch of receiver chain                                                 | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05                   | N          | 1   | 1  | 0.05                      |
+| 2) Insertion loss of receiver chain                                           | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                       | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                 | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 5) Measurement Receiver: uncertainty of the absolute level                    | Power Meter                                                                            | 0.06                   | R          |     | 1  | 0.03                      |
+| 6) Measurement distance                                                       | $\Delta d = 0.05\text{m}$                                                              | 0.14                   | R          |     | 1  | 0.08                      |
+| a) Offset of DUT phase centre                                                 |                                                                                        |                        |            |     |    |                           |
+| 7) Quality of quiet zone                                                      | Standard deviation of E-field in QZ measurement                                        | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 8) DUT Tx-power drift                                                         | Drift                                                                                  | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) Uncertainty related to the use of SAM phantom                              | Standard SAM head with standard tissue simulant                                        | 0                      | R          |     | 1  | 0                         |
+| 10) Coarse sampling grid                                                      | Negligible, used = $15^\circ$ and $= 15^\circ$                                         | 0                      | N          | 1   | 1  | 0                         |
+| 11) Repeatability                                                             | Monoblock, clamshell, slide design                                                     | 0.4                    | R          |     | 1  | 0.23                      |
+| <b>STAGE 2 (Calibration)</b>                                                  |                                                                                        |                        |            |     |    |                           |
+| 13) Uncertainty of network analyzer                                           | Manufacturer's uncertainty calculator, covers whole NA setup                           | 0.5                    | R          |     | 1  | 0.29                      |
+| 14) Mismatch of receiver chain                                                | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 15) Insertion loss of receiver chain                                          | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 16) Mismatch in the connection of calibration antenna                         | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 17) Influence of the feed cable of the calibration antenna                    | Gain calibration with a dipole                                                         | 0.3                    | R          |     | 1  | 0.17                      |
+| 18) Influence of the probe antenna cable                                      | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 19) Uncertainty of the absolute gain of the probe antenna                     | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 20) Uncertainty of the absolute gain of the calibration antenna               | Calibration certificate                                                                | 0.5                    | R          |     | 1  | 0.29                      |
+| 21) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                       | 0.29                   | R          |     | 1  | 0.17                      |
+| 22) Quality of quiet zone                                                     | Standard deviation of e-field in QZ measurement, Gain calibration                      | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                 |                                                                                        |                        |            |     |    | 0.89                      |
+| Expanded uncertainty (Confidence interval of 95 %)                            |                                                                                        |                        |            |     |    | 1.75                      |
+
+**Table E.29-2: Example of uncertainty budget for TRP head+hand (speech mode) measurement for anechoic chamber method**
+
+| Uncertainty Source                                                                                                                                                                                                                                  | Comment                                                                                                               | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                                                                                                                                                                                                    |                                                                                                                       |                        |            |     |    |                           |
+| 1) Mismatch of receiver chain                                                                                                                                                                                                                       | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$                                | 0.05                   | N          | 1   | 1  | 0.05                      |
+| 2) Insertion loss of receiver chain                                                                                                                                                                                                                 | Systematic with Stage 2 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                                                                                                                                                                                             | Systematic with Stage 2 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                                                                                                                                                                                       | Systematic with Stage 2 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 5) Measurement Receiver: uncertainty of the absolute level                                                                                                                                                                                          | Power Meter                                                                                                           | 0.06                   | R          |     | 1  | 0.03                      |
+| 6) Measurement distance<br>a) Offset of DUT phase centre                                                                                                                                                                                            | $\Delta d = 0.05\text{m}$                                                                                             | 0.14                   | R          |     | 1  | 0.08                      |
+| 7) Quality of quiet zone                                                                                                                                                                                                                            | Standard deviation of E-field in QZ measurement                                                                       | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 8) DUT Tx-power drift                                                                                                                                                                                                                               | Drift                                                                                                                 | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) Uncertainty related to the use of the SAM head and hand phantoms:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom | Standard SAM head with standard tissue simulant<br>$U_{\epsilon}[\text{dB}] = 0.20$<br>$U_{\sigma}[\text{dB}] = 0.15$ | 0.32                   | R          |     | 1  | 0.19                      |
+| 10) Coarse sampling grid                                                                                                                                                                                                                            | Negligible, used = $15^\circ$ and $= 15^\circ$ .                                                                      | 0                      | N          | 1   | 1  | 0                         |
+| 11) Repeatability of speech mode                                                                                                                                                                                                                    | Monoblock, clamshell and PDA design used for testing                                                                  | 1.04                   | R          |     | 1  | 0.6                       |
+| <b>STAGE 2 (Calibration)</b>                                                                                                                                                                                                                        |                                                                                                                       |                        |            |     |    |                           |
+| 12) Uncertainty of network analyzer                                                                                                                                                                                                                 | Manufacturer's uncertainty calculator, covers whole NA setup                                                          | 0.5                    | R          |     | 1  | 0.29                      |
+| 13) Mismatch of receiver chain                                                                                                                                                                                                                      | Taken in to account in NA setup uncertainty                                                                           | 0                      | U          |     | 1  | 0                         |
+| 14) Insertion loss of receiver chain                                                                                                                                                                                                                | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 15) Mismatch in the connection of calibration antenna                                                                                                                                                                                               | Taken in to account in NA setup uncertainty                                                                           | 0                      | U          |     | 1  | 0                         |
+| 16) Influence of the feed cable of the calibration antenna                                                                                                                                                                                          | Gain calibration with a dipole                                                                                        | 0.3                    | R          |     | 1  | 0.17                      |
+| 17) Influence of the probe antenna cable                                                                                                                                                                                                            | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 18) Uncertainty of the absolute gain of the probe antenna                                                                                                                                                                                           | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 19) Uncertainty of the absolute gain of the calibration antenna                                                                                                                                                                                     | Calibration certificate                                                                                               | 0.5                    | R          |     | 1  | 0.29                      |
+| 20) Measurement distance:<br>Calibration antenna's displacement and misalignment                                                                                                                                                                    | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                                                      | 0.29                   | R          |     | 1  | 0.17                      |
+| 21) Quality of quiet zone                                                                                                                                                                                                                           | Standard deviation of e-field in QZ measurement, Gain calibration                                                     | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                                                                                                                                                                                       |                                                                                                                       |                        |            |     |    | 1.07                      |
+| Expanded uncertainty<br>(Confidence interval of 95 %)                                                                                                                                                                                               |                                                                                                                       |                        |            |     |    | 2.10                      |
+
+**Table E.29-3: Example of uncertainty budget for TRP hand only (browsing mode) measurement for anechoic chamber method**
+
+| Uncertainty Source                                                                                                     | Comment                                                                                | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                                                                       |                                                                                        |                        |            |     |    |                           |
+| 1) Mismatch of receiver chain                                                                                          | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05                   | N          | 1   | 1  | 0.05                      |
+| 2) Insertion loss of receiver chain                                                                                    | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                                                                | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                                                          | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 5) Measurement Receiver: uncertainty of the absolute level                                                             | Power Meter                                                                            | 0.06                   | R          |     | 1  | 0.03                      |
+| 6) Measurement distance<br>a) Offset of DUT phase centre                                                               | $\Delta d = 0.05\text{m}$                                                              | 0.14                   | R          |     | 1  | 0.08                      |
+| 7) Quality of quiet zone                                                                                               | Standard deviation of E-field in QZ measurement                                        | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 8) DUT Tx-power drift                                                                                                  | Drift                                                                                  | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) Uncertainty related to the use of hand phantom: Uncertainty of dielectric properties and shape of the hand phantom. | $U_{\epsilon}[dB] = 0.20$<br>$U_{\sigma}[dB] = 0.15$                                   | 0.32                   | R          |     | 1  | 0.19                      |
+| 10) Coarse sampling grid                                                                                               | Negligible, used = $15^\circ$ and $= 15^\circ$ .                                       | 0                      | N          | 1   | 1  | 0                         |
+| 11) Repeatability of browsing mode                                                                                     | Monoblock, clamshell and PDA design used for testing                                   | 0.81                   | R          |     | 1  | 0.22                      |
+| <b>STAGE 2 (Calibration)</b>                                                                                           |                                                                                        |                        |            |     |    |                           |
+| 12) Uncertainty of network analyzer                                                                                    | Manufacturer's uncertainty calculator, covers whole NA setup                           | 0.5                    | R          |     | 1  | 0.29                      |
+| 13) Mismatch of receiver chain                                                                                         | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 14) Insertion loss of receiver chain                                                                                   | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 15) Mismatch in the connection of calibration antenna                                                                  | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 16) Influence of the feed cable of the calibration antenna                                                             | Gain calibration with a dipole                                                         | 0.3                    | R          |     | 1  | 0.17                      |
+| 17) Influence of the probe antenna cable                                                                               | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 18) Uncertainty of the absolute gain of the probe antenna                                                              | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 19) Uncertainty of the absolute gain of the calibration antenna                                                        | Calibration certificate                                                                | 0.5                    | R          |     | 1  | 0.29                      |
+| 20) Measurement distance: Calibration antenna's displacement and misalignment                                          | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                       | 0.29                   | R          |     | 1  | 0.17                      |
+| 21) Quality of quiet zone                                                                                              | Standard deviation of e-field in QZ measurement, Gain calibration                      | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                                                          |                                                                                        |                        |            |     |    | 1.0                       |
+| Expanded uncertainty (Confidence interval of 95 %)                                                                     |                                                                                        |                        |            |     |    | 1.96                      |
+
+**Table E.29-4: Example of uncertainty budget for TRP measurement with laptop ground plane phantom**
+
+| Uncertainty Source                                                            | Comment                                                                                | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                              |                                                                                        |                        |            |     |    |                           |
+| 1) Mismatch of receiver chain                                                 | $\Gamma_{\text{power meter}} < 0.05$ $\Gamma_{\text{probe antenna connection}} < 0.16$ | 0.05                   | N          | 1   | 1  | 0.05                      |
+| 2) Insertion loss of receiver chain                                           | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                       | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                 | Systematic with Stage 2 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 5) Measurement Receiver: uncertainty of the absolute level                    | Power Meter                                                                            | 0.06                   | R          |     | 1  | 0.03                      |
+| 6) Measurement distance                                                       | $\Delta d = 0.05\text{m}$                                                              | 0.14                   | R          |     | 1  | 0.08                      |
+| a) Offset of DUT phase centre                                                 |                                                                                        |                        |            |     |    |                           |
+| 7) Quality of quiet zone                                                      | Standard deviation of E-field in QZ measurement                                        | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 8) DUT Tx-power drift                                                         | Drift                                                                                  | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) Uncertainty related to the use of laptop ground plane phantom:             | Standard laptop phantom                                                                | 0                      | R          |     | 1  | 0                         |
+| 10) Coarse sampling grid                                                      | Negligible, used = $15^\circ$ and $= 15^\circ$ .                                       | 0                      | N          | 1   | 1  | 0                         |
+| 11) Repeatability                                                             | horizontal USB design, rotary USB port, and non-rotary USB port used for testing       | 0.4                    | R          |     | 1  | 0.23                      |
+| <b>STAGE 2 (Calibration)</b>                                                  |                                                                                        |                        |            |     |    |                           |
+| 13) Uncertainty of network analyzer                                           | Manufacturer's uncertainty calculator, covers whole NA setup                           | 0.5                    | R          |     | 1  | 0.29                      |
+| 14) Mismatch of receiver chain                                                | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 15) Insertion loss of receiver chain                                          | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 16) Mismatch in the connection of calibration antenna                         | Taken in to account in NA setup uncertainty                                            | 0                      | U          |     | 1  | 0                         |
+| 17) Influence of the feed cable of the calibration antenna                    | Gain calibration with a dipole                                                         | 0.3                    | R          |     | 1  | 0.17                      |
+| 18) Influence of the probe antenna cable                                      | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 19) Uncertainty of the absolute gain of the probe antenna                     | Systematic with Stage 1 (=> cancels)                                                   | 0                      | R          |     | 1  | 0                         |
+| 20) Uncertainty of the absolute gain of the calibration antenna               | Calibration certificate                                                                | 0.5                    | R          |     | 1  | 0.29                      |
+| 21) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                       | 0.29                   | R          |     | 1  | 0.17                      |
+| 22) Quality of quiet zone                                                     | Standard deviation of e-field in QZ measurement, Gain calibration                      | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                 |                                                                                        |                        |            |     |    | 0.89                      |
+| Expanded uncertainty (Confidence interval of 95 %)                            |                                                                                        |                        |            |     |    | 1.75                      |
+
+**Table E.29-5: Example of uncertainty budget for TRS head only measurement for anechoic chamber method**
+
+| Uncertainty Source                                                            | Comment                                                                  | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                              |                                                                          |                        |            |     |    |                           |
+| 1) Mismatch of transmitter chain                                              | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02                   | N          | 1   | 1  | 0.02                      |
+| 2) Insertion loss of transmitter chain                                        | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                       | Systematic with Stage 2 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                 | Systematic with Stage 2 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 5) Base station simulator: uncertainty of the absolute level                  |                                                                          | 1                      | R          |     | 1  | 0.58                      |
+| 6) BER measurement: output level step resolution                              | Step 0.1dB                                                               | 0.05                   | R          |     | 1  | 0.03                      |
+| 7) Statistical uncertainty of the BER measurement                             | BER target 10% $\pm$ 2% , 20000 tested bits , N=60                       | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 8) TRS data rate normalization                                                | 4 reference points measured                                              | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 9) Measurement distance<br>a) Offset of DUT phase centre                      | $\Delta d = 0.05\text{m}$                                                | 0.14                   | R          |     | 1  | 0.08                      |
+| 10) Quality of quiet zone                                                     | Standard deviation of E-field in QZ measurement                          | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 11) DUT sensitivity drift                                                     | Drift measurement                                                        | 0.2                    | R          |     | 1  | 0.12                      |
+| 12) Uncertainty related to the use of SAM phantom:                            | Standard SAM with standard tissue simulant                               | 0                      | R          |     | 1  | 0                         |
+| 13) Coarse sampling grid                                                      | $= 30^\circ$ and $= 30^\circ$                                            | 0.15                   | N          | N   | 1  | 0.15                      |
+| 14) Repeatability                                                             | Monoblock, clamshell, slide design                                       | 0.5                    | R          |     | 1  | 0.29                      |
+| <b>STAGE 2 (Calibration)</b>                                                  |                                                                          |                        |            |     |    |                           |
+| 16) Uncertainty of network analyzer                                           | Manufacturer's uncertainty calculator, covers NA setup                   | 0.5                    | R          |     | 1  | 0.29                      |
+| 17) Mismatch of transmitter chain                                             | Taken in to account in NA setup uncertainty                              | 0                      | U          |     | 1  | 0                         |
+| 18) Insertion loss of transmitter chain                                       | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 19) Mismatch in the connection of calibration antenna                         | Taken in to account in NA setup uncertainty                              | 0                      | R          |     | 1  | 0                         |
+| 20) Influence of the feed cable of the calibration antenna                    | Gain calibration with dipole                                             | 0.3                    | R          |     | 1  | 0.17                      |
+| 21) Influence of the probe antenna cable                                      | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 22) Uncertainty of the absolute gain of the probe antenna                     | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 23) Uncertainty of the absolute gain of the calibration antenna               | Calibration certificate                                                  | 0.5                    | R          |     | 1  | 0.29                      |
+| 24) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$         | 0.29                   | R          |     | 1  | 0.17                      |
+| 25) Quality of quiet zone                                                     | Standard deviation of E-field in QZ measurement                          | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                 |                                                                          |                        |            |     |    | 1.1                       |
+| Expanded uncertainty (Confidence interval of 95 %)                            |                                                                          |                        |            |     |    | 2.16                      |
+
+**Table E.29-6: Example of uncertainty budget for TRS head+hand (speech mode) measurement for anechoic chamber method**
+
+| Uncertainty Source                                                                                                                                                                                                                                    | Comment                                                                                                               | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                                                                                                                                                                                                      |                                                                                                                       |                        |            |     |    |                           |
+| 1) Mismatch of transmitter chain                                                                                                                                                                                                                      | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$                                              | 0.02                   | N          | 1   | 1  | 0.02                      |
+| 2) Insertion loss of transmitter chain                                                                                                                                                                                                                | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                                                                                                                                                                                               | Systematic with Stage 2 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                                                                                                                                                                                         | Systematic with Stage 2 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 5) Base station simulator: uncertainty of the absolute level                                                                                                                                                                                          |                                                                                                                       | 1                      | R          |     | 1  | 0.58                      |
+| 6) BER measurement: output level step resolution                                                                                                                                                                                                      | Step 0.1dB                                                                                                            | 0.05                   | R          |     | 1  | 0.03                      |
+| 7) Statistical uncertainty of the BER measurement                                                                                                                                                                                                     | BER target 10% $\pm$ 2% , 20000 tested bits , N=60                                                                    | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 8) TRS data rate normalization                                                                                                                                                                                                                        | 4 reference points measured                                                                                           | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 9) Measurement distance<br>a) Offset of DUT phase centre                                                                                                                                                                                              | $\Delta d = 0.05\text{m}$                                                                                             | 0.14                   | R          |     | 1  | 0.08                      |
+| 10) Quality of quiet zone                                                                                                                                                                                                                             | Standard deviation of E-field in QZ measurement                                                                       | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 11) DUT sensitivity drift                                                                                                                                                                                                                             | Drift measurement                                                                                                     | 0.2                    | R          |     | 1  | 0.12                      |
+| 12) Uncertainty related to the use of the SAM head and hand phantoms:<br>a) uncertainty from using different types of SAM phantom<br>b) simulated tissue liquid uncertainty<br>c) uncertainty of dielectric properties and shape of the hand phantom: | Standard SAM head with standard tissue simulant<br>$U_{\epsilon}[\text{dB}] = 0.12$<br>$U_{\sigma}[\text{dB}] = 0.15$ | 0.32                   | R          |     | 1  | 0.19                      |
+| 13) Coarse sampling grid                                                                                                                                                                                                                              | $= 30^\circ$ and $= 30^\circ$ .                                                                                       | 0.15                   | N          | N   | 1  | 0.15                      |
+| 14) Repeatability of speech mode                                                                                                                                                                                                                      | Monoblock, clamshell and PDA used for testing                                                                         | 1.4                    | R          |     | 1  | 0.81                      |
+| <b>STAGE 2 (Calibration)</b>                                                                                                                                                                                                                          |                                                                                                                       |                        |            |     |    |                           |
+| 15) Uncertainty of network analyzer                                                                                                                                                                                                                   | Manufacturer's uncertainty calculator, covers NA setup                                                                | 0.5                    | R          |     | 1  | 0.29                      |
+| 16) Mismatch of transmitter chain                                                                                                                                                                                                                     | Taken in to account in NA setup uncertainty                                                                           | 0                      | U          |     | 1  | 0                         |
+| 17) Insertion loss of transmitter chain                                                                                                                                                                                                               | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 18) Mismatch in the connection of calibration antenna                                                                                                                                                                                                 | Taken in to account in NA setup uncertainty                                                                           | 0                      | R          |     | 1  | 0                         |
+| 19) Influence of the feed cable of the calibration antenna                                                                                                                                                                                            | Gain calibration with dipole                                                                                          | 0.3                    | R          |     | 1  | 0.17                      |
+| 20) Influence of the probe antenna cable                                                                                                                                                                                                              | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 21) Uncertainty of the absolute gain of the probe antenna                                                                                                                                                                                             | Systematic with Stage 1 (=> cancels)                                                                                  | 0                      | R          |     | 1  | 0                         |
+| 22) Uncertainty of the absolute gain of the calibration antenna                                                                                                                                                                                       | Calibration certificate                                                                                               | 0.5                    | R          |     | 1  | 0.29                      |
+| 23) Measurement distance: Calibration antenna's displacement and misalignment                                                                                                                                                                         | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                                                      | 0.29                   | R          |     | 1  | 0.17                      |
+| 24) Quality of quiet zone                                                                                                                                                                                                                             | Standard deviation of E-field in QZ measurement                                                                       | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                                                                                                                                                                                         |                                                                                                                       |                        |            |     |    | 1.35                      |
+| Expanded uncertainty (Confidence interval of 95 %)                                                                                                                                                                                                    |                                                                                                                       |                        |            |     |    | 2.64                      |
+
+**Table E.29-7: Example of uncertainty budget for TRS hand only (browsing mode) measurement for anechoic chamber method**
+
+| Uncertainty Source                                                                                                      | Comment                                                                  | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                                                                        |                                                                          |                        |            |     |    |                           |
+| 1) Mismatch of transmitter chain                                                                                        | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$ | 0.02                   | N          | 1   | 1  | 0.02                      |
+| 2) Insertion loss of transmitter chain                                                                                  | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                                                                 | Systematic with Stage 2 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                                                           | Systematic with Stage 2 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 5) Base station simulator: uncertainty of the absolute level                                                            |                                                                          | 1                      | R          |     | 1  | 0.58                      |
+| 6) BER measurement: output level step resolution                                                                        | Step 0.1dB                                                               | 0.05                   | R          |     | 1  | 0.03                      |
+| 7) Statistical uncertainty of the BER measurement                                                                       | BER target 10% $\pm$ 2% , 20000 tested bits , N=60                       | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 8) TRS data rate normalization                                                                                          | 4 reference points measured                                              | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 9) Measurement distance<br>a) Offset of DUT phase centre                                                                | $\Delta d = 0.05\text{m}$                                                | 0.14                   | R          |     | 1  | 0.08                      |
+| 10) Quality of quiet zone                                                                                               | Standard deviation of E-field in QZ measurement                          | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 11) DUT sensitivity drift                                                                                               | Drift measurement                                                        | 0.2                    | R          |     | 1  | 0.12                      |
+| 12) Uncertainty related to the use of hand phantom: Uncertainty of dielectric properties and shape of the hand phantom. | $U_{\epsilon}[dB] = 0.12$<br>$U_{\sigma}[dB] = 0.15$                     | 0.32                   | R          |     | 1  | 0.19                      |
+| 13) Coarse sampling grid                                                                                                | $= 30^\circ$ and $= 30^\circ$                                            | 0.15                   | N          | N   | 1  | 0.15                      |
+| 14) Repeatability of browsing mode                                                                                      | Monoblock, clamshell and PDA used for testing                            | 0.91                   | R          |     | 1  | 0.28                      |
+| <b>STAGE 2 (Calibration)</b>                                                                                            |                                                                          |                        |            |     |    |                           |
+| 15) Uncertainty of network analyzer                                                                                     | Manufacturer's uncertainty calculator, covers NA setup                   | 0.5                    | R          |     | 1  | 0.29                      |
+| 16) Mismatch of transmitter chain                                                                                       | Taken in to account in NA setup uncertainty                              | 0                      | U          |     | 1  | 0                         |
+| 17) Insertion loss of transmitter chain                                                                                 | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 18) Mismatch in the connection of calibration antenna                                                                   | Taken in to account in NA setup uncertainty                              | 0                      | R          |     | 1  | 0                         |
+| 19) Influence of the feed cable of the calibration antenna                                                              | Gain calibration with dipole                                             | 0.3                    | R          |     | 1  | 0.17                      |
+| 20) Influence of the probe antenna cable                                                                                | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 21) Uncertainty of the absolute gain of the probe antenna                                                               | Systematic with Stage 1 (=> cancels)                                     | 0                      | R          |     | 1  | 0                         |
+| 22) Uncertainty of the absolute gain of the calibration antenna                                                         | Calibration certificate                                                  | 0.5                    | R          |     | 1  | 0.29                      |
+| 23) Measurement distance: Calibration antenna's displacement and misalignment                                           | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$         | 0.29                   | R          |     | 1  | 0.17                      |
+| 24) Quality of quiet zone                                                                                               | Standard deviation of E-field in QZ measurement                          | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                                                           |                                                                          |                        |            |     |    | 1.2                       |
+| Expanded uncertainty (Confidence interval of 95 %)                                                                      |                                                                          |                        |            |     |    | 2.35                      |
+
+**Table E.29-8: Example of uncertainty budget for TRS measurement with laptop ground plane phantom**
+
+| Uncertainty Source                                                            | Comment                                                                              | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                              |                                                                                      |                        |            |     |    |                           |
+| 1) Mismatch of transmitter chain                                              | $\Gamma_{\text{BSS}} < 0.13$ $\Gamma_{\text{antenna connection}} < 0.03$             | 0.02                   | N          | 1   | 1  | 0.02                      |
+| 2) Insertion loss of transmitter chain                                        | Systematic with Stage 1 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the probe antenna cable                                       | Systematic with Stage 2 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the probe antenna                                 | Systematic with Stage 2 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 5) Base station simulator: uncertainty of the absolute level                  |                                                                                      | 1                      | R          |     | 1  | 0.58                      |
+| 6) BER measurement: output level step resolution                              | Step 0.1dB                                                                           | 0.05                   | R          |     | 1  | 0.03                      |
+| 7) Statistical uncertainty of the BER measurement                             | BER target 10% $\pm$ 2% , 20000 tested bits , N=60                                   | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 8) TRS data rate normalization                                                | 4 reference points measured                                                          | 0.12                   | N          | 1   | 1  | 0.12                      |
+| 9) Measurement distance<br>a) Offset of DUT phase centre                      | $\Delta d = 0.05\text{m}$                                                            | 0.14                   | R          |     | 1  | 0.08                      |
+| 10) Quality of quiet zone                                                     | Standard deviation of E-field in QZ measurement                                      | 0.5                    | N          | 1   | 1  | 0.5                       |
+| 11) DUT sensitivity drift                                                     | Drift measurement                                                                    | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) Uncertainty related to the use of laptop ground plane phantom              | Standard laptop phantom                                                              | 0                      | R          |     | 1  | 0                         |
+| 13) Coarse sampling grid                                                      | $= 30^\circ$ and $= 30^\circ$ .                                                      | 0.15                   | N          | N   | 1  | 0.15                      |
+| 14) Repeatability                                                             | horizontal USB design, rotary USB porter, and non-rotary USB porter used for testing | 0.5                    | R          |     | 1  | 0.29                      |
+| <b>STAGE 2 (Calibration)</b>                                                  |                                                                                      |                        |            |     |    |                           |
+| 15) Uncertainty of network analyzer                                           | Manufacturer's uncertainty calculator, covers NA setup                               | 0.5                    | R          |     | 1  | 0.29                      |
+| 16) Mismatch of transmitter chain                                             | Taken in to account in NA setup uncertainty                                          | 0                      | U          |     | 1  | 0                         |
+| 17) Insertion loss of transmitter chain                                       | Systematic with Stage 1 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 18) Mismatch in the connection of calibration antenna                         | Taken in to account in NA setup uncertainty                                          | 0                      | R          |     | 1  | 0                         |
+| 19) Influence of the feed cable of the calibration antenna                    | Gain calibration with dipole                                                         | 0.3                    | R          |     | 1  | 0.17                      |
+| 20) Influence of the probe antenna cable                                      | Systematic with Stage 1 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 21) Uncertainty of the absolute gain of the probe antenna                     | Systematic with Stage 1 (=> cancels)                                                 | 0                      | R          |     | 1  | 0                         |
+| 22) Uncertainty of the absolute gain of the calibration antenna               | Calibration certificate                                                              | 0.5                    | R          |     | 1  | 0.29                      |
+| 23) Measurement distance: Calibration antenna's displacement and misalignment | $d = 3\text{m}$ , $\Delta d = 0.05\text{m}$ , $\theta = 2^\circ$                     | 0.29                   | R          |     | 1  | 0.17                      |
+| 24) Quality of quiet zone                                                     | Standard deviation of E-field in QZ measurement                                      | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                                 |                                                                                      |                        |            |     |    | 1.1                       |
+| Expanded uncertainty (Confidence interval of 95 %)                            |                                                                                      |                        |            |     |    | 2.16                      |
+
+**Table E.29-9: Example of uncertainty budget for TRP measurement for reverberation chamber method**
+
+| Uncertainty Source                                                    | Comment                                                                                               | Uncertainty Value [dB] | Prob Distr | Div | ci | Standard Uncertainty [dB] |
+|-----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|------------------------|------------|-----|----|---------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                      |                                                                                                       |                        |            |     |    |                           |
+| 1) Mismatch of receiver chain                                         | $\Gamma_{\text{power meter}} < 0.05$<br>$\Gamma_{\text{fixed measurement antenna connection}} < 0.16$ | 0.05                   | U          |     | 1  | 0.04                      |
+| 2) Insertion loss of receiver chain                                   | Systematic with Stage 2 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 3) Influence of the fixed measurement antenna cable                   | Systematic with Stage 2 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 4) Absolute antenna gain of the fixed measurement antenna             | Systematic with Stage 2 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 5) Measurement Receiver: uncertainty of the absolute level            | Power Meter                                                                                           | 0.06                   | R          |     | 1  | 0.03                      |
+| 6) Chamber statistical ripple and repeatability                       | Statistics of chamber                                                                                 | 0.4                    | N          | 1   | 1  | 0.4                       |
+| 7) Additional power loss in EUT chassis                               | The EUT not present in the chamber during calibration measurement                                     | 0.1                    | R          |     | 1  | 0.06                      |
+| 8) DUT Tx-power drift                                                 | Drift                                                                                                 | 0.2                    | R          |     | 1  | 0.12                      |
+| 9) a) Uncertainty related to the use of SAM phantom:                  | Standard SAM head with standard tissue simulant                                                       | 0                      | R          |     | 1  | 0                         |
+| b) Simulated tissue liquid uncertainty                                | Maximum allowed error                                                                                 | 0.5                    | R          |     | 1  | 0.29                      |
+| c) Effect of DUT holder                                               | Fixed value                                                                                           | 0.2                    | R          |     | 1  | 0.12                      |
+| 10) Repeatability                                                     | Using the same setup and stirring sequence                                                            | 0.4                    | R          |     | 1  | 0.23                      |
+| 11) Uncertainty related to the use of Laptop Ground Plane phantom     | Standard Laptop Ground Plane phantom                                                                  | [0]                    | R          |     | 1  | [0]                       |
+| <b>STAGE 2 (Calibration)</b>                                          |                                                                                                       |                        |            |     |    |                           |
+| 12) Uncertainty of network analyzer                                   | Manufacturer's uncertainty calculator, covers whole NA setup                                          | 0.5                    | R          |     | 1  | 0.29                      |
+| 13) Mismatch of receiver chain                                        | Taken in to account in NA setup uncertainty                                                           | 0                      | U          |     | 1  | 0                         |
+| 14) Insertion loss of receiver chain                                  | Systematic with Stage 1 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 15) Mismatch in the connection of calibration antenna                 | Taken in to account in NA setup uncertainty                                                           | 0                      | U          |     | 1  | 0                         |
+| 16) Influence of the feed cable of the calibration antenna            | Gain calibration with a dipole                                                                        | 0.3                    | R          |     | 1  | 0.17                      |
+| 17) Influence of the fixed measurement antenna cable                  | Systematic with Stage 1 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 18) Uncertainty of the absolute gain of the fixed measurement antenna | Systematic with Stage 1 (=> cancels)                                                                  | 0                      | R          |     | 1  | 0                         |
+| 19) Uncertainty of the absolute gain of the calibration antenna       | Calibration certificate                                                                               | 0.5                    | R          |     | 1  | 0.29                      |
+| 20) Chamber statistical ripple and repeatability                      | Statistics of chamber                                                                                 | 0.5                    | N          | 1   | 1  | 0.5                       |
+| Combined standard uncertainty                                         |                                                                                                       |                        |            |     |    | 0.88                      |
+| Expanded uncertainty                                                  |                                                                                                       |                        |            |     |    | 1.73                      |
+
+|                               |  |  |  |  |  |  |
+|-------------------------------|--|--|--|--|--|--|
+| (Confidence interval of 95 %) |  |  |  |  |  |  |
+|-------------------------------|--|--|--|--|--|--|
+
+**Table E.29-10: Example of uncertainty budget for TRS measurement for reverberation chamber method**
+
+| Uncertainty Source                                                    | Comment                                                                     | Uncertainty Value [dB] | Prob Distr | Div | c <sub>i</sub> | Standard Uncertainty y [dB] |
+|-----------------------------------------------------------------------|-----------------------------------------------------------------------------|------------------------|------------|-----|----------------|-----------------------------|
+| <b>STAGE 1 (DUT measurement)</b>                                      |                                                                             |                        |            |     |                |                             |
+| 1) Mismatch of transmitter chain                                      | $\Gamma_{\text{BSS}} < 0.13$<br>$\Gamma_{\text{antenna connection}} < 0.03$ | 0.02                   | N          | 1   | 1              | 0.02                        |
+| 2) Insertion loss of transmitter chain                                | Systematic with Stage 1 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 3) Influence of the fixed measurement antenna cable                   | Systematic with Stage 2 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 4) Absolute antenna gain of the fixed measurement antenna             | Systematic with Stage 2 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 5) Base station simulator: uncertainty of the absolute level          |                                                                             | 1                      | R          |     | 1              | 0.58                        |
+| 6) BER measurement: output level step resolution                      | Step 0.1dB                                                                  | 0.05                   | R          |     | 1              | 0.03                        |
+| 7) Statistical uncertainty of the BER measurement                     | BER target 10% $\pm$ 2% , 20000 tested bits , N=60                          | 0.12                   | N          | 1   | 1              | 0.12                        |
+| 8) TRS data rate normalization                                        | 4 reference points measured                                                 | 0.12                   | N          | 1   | 1              | 0.12                        |
+| 9) Chamber statistical ripple and repeatability                       | Statistics of chamber                                                       | 0.4                    | N          | 1   | 1              | 0.4                         |
+| 10) Additional power loss in EUT chassis                              | The EUT not present in the chamber during calibration measurement           | 0.1                    | R          |     | 1              | 0.06                        |
+| 11) DUT sensitivity drift                                             | Drift measurement                                                           | 0.2                    | R          |     | 1              | 0.12                        |
+| 12) a) Uncertainty related to the use of SAM phantom:                 | Standard SAM with standard tissue simulant                                  | 0                      | R          |     | 1              | 0                           |
+| b) Simulated tissue liquid uncertainty                                | Maximum allowed error                                                       | 0.5                    | R          |     | 1              | 0.29                        |
+| c) Effect of DUT holder                                               | Fixed value                                                                 | 0.2                    | R          |     | 1              | 0.12                        |
+| 13) Repeatability                                                     | Using the same setup and stirring sequence                                  | 0.4                    | R          |     | 1              | 0.23                        |
+| 14) Uncertainty related to the use of Laptop Ground Plane phantom     | Standard Laptop Ground Plane phantom                                        | [0]                    | R          |     | 1              | [0]                         |
+| <b>STAGE 2 (Calibration)</b>                                          |                                                                             |                        |            |     |                |                             |
+| 15) Uncertainty of network analyzer                                   | Manufacturer's uncertainty calculator, covers NA setup                      | 0.5                    | R          |     | 1              | 0.29                        |
+| 16) Mismatch of transmitter chain                                     | Taken in to account in NA setup uncertainty                                 | 0                      | U          |     | 1              | 0                           |
+| 17) Insertion loss of transmitter chain                               | Systematic with Stage 1 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 18) Mismatch in the connection of calibration antenna                 | Taken in to account in NA setup uncertainty                                 | 0                      | R          |     | 1              | 0                           |
+| 19) Influence of the feed cable of the calibration antenna            | Gain calibration with dipole antenna                                        | 0.3                    | R          |     | 1              | 0.17                        |
+| 20) Influence of the fixed measurement antenna cable                  | Systematic with Stage 1 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 21) Uncertainty of the absolute gain of the fixed measurement antenna | Systematic with Stage 1 (=> cancels)                                        | 0                      | R          |     | 1              | 0                           |
+| 22) Uncertainty of the absolute gain of the calibration antenna       | Calibration certificate                                                     | 0.5                    | R          |     | 1              | 0.29                        |
+
+|                                                    |                       |     |   |   |   |      |
+|----------------------------------------------------|-----------------------|-----|---|---|---|------|
+| 23) Chamber statistical ripple and repeatability   | Statistics of chamber | 0.5 | N | 1 | 1 | 0.5  |
+| Combined standard uncertainty                      |                       |     |   |   |   | 1.07 |
+| Expanded uncertainty (Confidence interval of 95 %) |                       |     |   |   |   | 2.09 |
+
+## Annex F (informative): Suggested recipes of liquid to be used inside SAM phantom
+
+### F.1 General
+
+The Specific Anthropomorphic Mannequin (SAM) is used for radiated performance measurements. The absorption of electromagnetic energy by the human muscle or brain tissue is simulated by measuring the electrical field inside a SAM phantom filled with a liquid having the same electrical properties as human tissue. Tables F.1-1 and F.1-2 are proposals for two different recipes of the liquid to be used inside the SAM phantom.
+
+**Table F.1-1: Liquid recipe proposal 1**
+
+| Component        | Mass % |
+|------------------|--------|
+| De-ionized Water | 57.12  |
+| Tween 20         | 42.30  |
+| NaCl             | 0.58   |
+
+**Table F.1-2: Liquid recipe proposal 2**
+
+| Component                                          | Mass %  |
+|----------------------------------------------------|---------|
+| De-ionized Water                                   | 54.9 %  |
+| Diethylene Glycol Butyl Ether (DGBE) (> 99 % pure) | 44.92 % |
+| NaCl                                               | 0.18 %  |
+
+## Annex G (informative): Anechoic chamber specification and validation method
+
+### G.1 Shielded anechoic chamber specifications
+
+To avoid environmental perturbations the measurements shall be performed in a shielded enclosure, preserved from electromagnetic disturbances coming from electromagnetic environment (Radio and TV broadcast, cellular, ISM equipment, etc...). The shielding effectiveness shall be tested according to the EN 50 147-1 standard in the frequency range of 800 MHz up to 4 GHz.
+
+The recommended level of the shielding effectiveness is -100 dB from 800 MHz to 4 GHz.
+
+Testing of the shielding effectiveness can be performed either before or after the installation of absorbers.
+
+### G.2 Quiet zone reflectivity level validation
+
+The performance of anechoic chamber is typically evaluated from reflectivity level in the quiet zone. The reflectivity level is defined as power ratio of all summed reflected signals to direct signal from antenna:
+
+To evaluate the quiet zone reflectivity level, the contribution of absorbing materials, the antenna positioning system and other constructions in the anechoic chamber should be measured.
+
+To measure accurately quality of the quiet zone in anechoic chamber an omni-directional antenna shall be used. Near omni-directional three axes field-probes are available with fibre optic connection thus minimizing cable effects. Because sensitivity of field probe is limited it shall be carefully checked that the field probe is operated at least 6dB above the noise floor of the probe.
+
+NOTE: The quiet zone evaluation should be performed with the antenna positioning system in its place, in order to include its effect on the reflectivity level.
+
+## G.2.1 Description of a practical method for Quiet Zone characterization
+
+A practical version of the Free Space VSWR method is presented.
+
+In the Free Space VSWR method the quality of quiet zone is measured from amplitude ripple caused by reflections inside the anechoic chamber. Phase variation of the direct signal and the reflected signals is obtained by moving a field-probe in the quiet zone. Amplitude ripple in the quiet zone is caused by this phase variation of reflected signals and the direct signal from antenna. Figure 2 below shows seven measuring positions.
+
+![Figure G.2.1-1: Measurement positions with 150mm separation. The diagram shows a 3D coordinate system with x, y, and z axes. Seven measurement points are marked with small L-shaped symbols. Six points are arranged in a hexagonal pattern around the origin, and one point is at the origin itself. A large arrow labeled 'Antenna' points towards the right side of the diagram, indicating the direction of the incident wave.](af8f53cc5b2ff75aef3871a39964bc9b_img.jpg)
+
+Figure G.2.1-1: Measurement positions with 150mm separation. The diagram shows a 3D coordinate system with x, y, and z axes. Seven measurement points are marked with small L-shaped symbols. Six points are arranged in a hexagonal pattern around the origin, and one point is at the origin itself. A large arrow labeled 'Antenna' points towards the right side of the diagram, indicating the direction of the incident wave.
+
+**Figure G.2.1-1: Measurement positions with 150mm separation**
+
+In each of the seven-measurement position amplitude of power received by field-probe [dBm] is measured where  $i$  is index of measuring position. Variance of measurement distance to the antenna from field-probe in different measurement positions can be compensated by following equation:
+
+where,
+
+$d_i$  is distance to point  $i$  from the antenna,
+
+$d_0$  is distance to centre of quiet zone from the antenna
+
+$P_i$  is uncorrected measurement value from point  $i$ .
+
+The sample standard deviation of the electric field in the quiet zone can be calculated from these distance corrected values or directly from the measured values with the following equation:
+
+where,
+
+$N$  is number of measurements positions
+
+$\bar{P}$  is dB average of all
+
+$P_i$  is or
+
+## G.3 Standard deviation of electric field
+
+To obtain a more accurate picture of quality of quiet zone, the measurement described in G.2.1 can be done from multiple directions and polarizations. Doing free space VSWR measurement from different directions in 15-degree separation for elevation and azimuth, results in 264 standard deviation values in both polarizations (. From these values average sample standard deviation in electric field in quiet zone can be calculated from equation:
+
+where,
+
+is number of angular intervals in elevation,
+
+is number of angular intervals in azimuth and
+
+is elevation of measurement .
+
+This quiet zone quality measurement should be done at all the frequencies used in measurements. It can also be sufficient on all the centre frequencies in the measurement bands but also in this case the Tx and Rx shall be measured separately.
+
+---
+
+## Annex H (informative): Reverberation chamber specifications and validation method
+
+### H.1 Shielded reverberation chamber specifications
+
+Before measuring the test site characteristics in terms of stirring effectiveness, the shielding effectiveness of the metallic enclosure must be measured.
+
+To avoid environmental perturbations, the measurements shall be performed in a shielded enclosure, preserved from electromagnetic disturbances coming from electromagnetic environment such as: TV broadcast, radio, cellular, ISM equipment, to name a few. The shielding effectiveness recommended to be tested according to the EN 50 147-1 standard in the frequency range of 800 MHz up to 4 GHz.
+
+The recommended level of the shielding effectiveness is -100 dB from 800 MHz to 4 GHz.
+
+### H.2 Reverberation chamber statistical ripple and repeatability validation
+
+The reverberation chamber is typically evaluated according to its isotropy level and ability to produce independent samples. The uncertainty due to chamber statistics is determined by repeated calibration measurements as described in Annex B.2.2. This uncertainty contribution is a composite value consisting of most of the specific reverberation chamber contributions, such as limited number of modes, polarization imbalance and mode-stirring techniques.
+
+The uncertainty contribution value shall be determined by repeated calibration measurements for nine different positions and orientations of the calibration antenna in order to determine the statistical variation as a function of frequency, or at least at the frequencies where the chamber shall be used. This uncertainty contribution value can be assumed to have a normal distribution.
+
+The uncertainty will depend on chamber size, frequency, stirrer sequence, stirrer types and shapes, polarization stirring (if any), and the degree of chamber loading. All these factors must remain the same for all of the nine calibration measurements. The uncertainty will also depend on frequency stirring bandwidth (if any), but the effects of different amounts of frequency stirring can be studied with the same sets of calibration data as when no frequency stirring is applied.
+
+The nine net average power transfer functions of all or some of the nine calibration configurations for each loading case shall be averaged to provide a good reference level. Frequency stirring can only be applied to improve the reference level. Therefore, the uncertainty shall be found by computing the average and standard deviation of the net average power transfer function of each of the nine reference (antenna) positions and orientations (without frequency stirring) around the reference level (which can be frequency stirred if it gives better overall accuracy).
+
+The data obtained during these reference measurements can be used for analysis of the chamber's systematic and deterministic contribution to S21. Such analysis can help determine possible uncertainty sources in chambers where the "chamber statistics" portion of the uncertainty analysis is too high to fulfil the total uncertainty criterion. The normalized standard deviation is calculated using the following expression:
+
+where,
+
+is the standard deviation of the power transfer function over  $T$  different calibration antenna positions.  $t$  is the reference power transfer function for position  $t$  of the calibration antenna. The power transfer function for every calibration antenna position is further the average over the power transfer function for each fixed measurement antenna in the chamber defined in Annex B.2.2. Thus,
+
+where,
+
+$N$  is the total number of fixed measurement antennas. Moreover,
+
+is the average power transfer function over the  $T$  calibration antenna positions.
+
+## Annex I (informative): Recommended performance for Handheld UE
+
+Editor's notes: This annex is incomplete. The following items are missing or incomplete:
+
+- Table I.2.1.2-1, I.2.2.1-1, I.2.2.2-1, I.2.3.1-1, I.2.3.2-1, I.3.1.2-1, I.3.2.1-1, I.3.2.2-1, I.3.3.1-1 and I.3.3.2-1 as they are not complete in TS 37.144 yet
+- Table I.2.2.3-1, I.2.2.4-1, I.2.3.3-1, I.2.3.4-1, I.3.2.3-1, I.3.2.4-1, I.3.3.3-1 and I.3.3.4 as they are not specified in TS 37.144 yet
+
+### I.1 General
+
+This annex introduces the concept of recommended OTA performance for operating bands for handheld UE's. This requirement is not mandatory but is recommended.
+
+The concept of recommended performance is to ensure that UE OTA performance is maximised in order to improve user experience and network performance. It is recognised that the ability to meet the recommended performance depends on the number of frequency bands supported by the UE.
+
+### I.2 Total Radiated Power
+
+The OTA TRP performance for UTRA and E-UTRA should be greater or equal than the recommended values in this clause.
+
+#### I.2.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in subclause 4.3.1.
+
+### I.2.1.1 UTRA FDD
+
+**Table I.2.1.1-1: Handheld UE TRP recommended performance for UTRA FDD in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | +18           | +18              | +16           |
+| II             | -             | -             | +18           | +18              | +16           |
+| III            | -             | -             | +18           | +18              | +16           |
+| IV             | -             | -             | +18           | +18              | +16           |
+| V              | -             | -             | +14           | +14              | +12           |
+| VI             | -             | -             | +14.5         | +14.5            | +12.5         |
+| VII            | -             | -             | +18           | +18              | +16           |
+| VIII           | -             | -             | +15           | +15              | +13           |
+| IX             | -             | -             | +18           | +18              | +16           |
+| XIX            | -             | -             | +14.5         | +14.5            | +12.5         |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+### I.2.1.2 UTRA LCR TDD
+
+**Table I.2.1.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | +18           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | +18           | -             | -                | -             |
+| f              | -             | +18           | -             | -                | -             |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+## I.2.2 Beside the head and hand phantoms position
+
+Beside the head and hand phantoms test method is defined in subclauses 4.3.3.
+
+### I.2.2.1 UTRA FDD
+
+**Table I.2.2.1-1: Handheld UE TRP recommended performance for UTRA FDD beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               |               | Average       | Average          | Average       |
+| I              | -             | -             | 16.25         | TBD              | TBD           |
+| II             | -             | -             | 16.25         | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | 12.40         | TBD              | TBD           |
+| VI             | -             | -             | 12.40         | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | 12.40         | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 12.40         | TBD              | TBD           |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.
+
+NOTE 2: Applicable for devices narrower than 72mm as defined in TR 25.914.
+
+NOTE 3: Not applicable for devices supporting CDMA or carrier aggregation.
+
+### I.2.2.2 UTRA LCR TDD
+
+**Table I.2.2.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               | Average       |               |                  |               |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+### I.2.2.3 E-UTRA FDD
+
+**Table I.2.2.3-1: TBD**
+
+### I.2.2.4 E-UTRA TDD
+
+**Table I.2.2.4-1: TBD**
+
+## I.2.3 Hand phantom browsing mode position
+
+Hand phantom browsing mode test method is defined in subclauses 4.3.4.
+
+### I.2.3.1 UTRA FDD
+
+**Table I.2.3.1-1: Handheld UE TRP recommended performance for UTRA FDD in the hand phantom browsing mode position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                |               |               | Average       | Average          | Average       |
+| I              | -             | -             | TBD           | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | TBD           | TBD              | TBD           |
+| VI             | -             | -             | TBD           | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | TBD           | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | TBD           | TBD              | TBD           |
+
+NOTE: Applicable for dual-mode GSM/UMTS.
+
+### I.2.3.2 UTRA LCR TDD
+
+**Table I.2.3.2-1: Handheld UE TRP recommended performance for UTRA LCR TDD in the hand phantom browsing mode position**
+
+| Operating band | Power class 1  | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|----------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)    | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | <b>Average</b> |               |               |                  |               |
+| a              | -              | TBD           | -             | -                | -             |
+| b              | -              | TBD           | -             | -                | -             |
+| c              | -              | TBD           | -             | -                | -             |
+| d              | -              | TBD           | -             | -                | -             |
+| e              | -              | TBD           | -             | -                | -             |
+| f              | -              | TBD           | -             | -                | -             |
+
+Note: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+### I.2.3.3 E-UTRA FDD
+
+**Table I.2.3.3-1: Tablet TRP recommended performance for E-UTRA FDD in the data transfer position**
+
+| Operating band | Power Class 1  | Power Class 2 | Power Class 3 | Power Class 4 |
+|----------------|----------------|---------------|---------------|---------------|
+|                | Power (dBm)    | Power (dBm)   | Power (dBm)   | Power (dBm)   |
+|                | <b>Average</b> |               |               |               |
+| 1              |                |               | 21.0          |               |
+| 2              |                |               |               |               |
+| 3              |                |               | 20.5          |               |
+| 4              |                |               |               |               |
+| 5              |                |               |               |               |
+| 7              |                |               | 20.0          |               |
+| 8              |                |               |               |               |
+| 12             |                |               |               |               |
+| 13             |                |               |               |               |
+| 19             |                |               | 20.0          |               |
+| 20             |                |               | 19.5          |               |
+| 21             |                |               | 20.0          |               |
+| 28             |                |               |               |               |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+### I.2.3.4 E-UTRA TDD
+
+**Table I.2.3.4-1: TBD**
+
+## I.3 Total Radiated Sensitivity
+
+The OTA TRS performance for UTRA and E-UTRA should be lower or equal than the recommended values shown in this clause.
+
+### I.3.1 Beside the head phantom position
+
+Beside the head phantom test method is defined in subclause 4.3.1.
+
+### I.3.1.1 UTRA FDD
+
+**Table I.3.1.1-1: Handheld UE TRS recommended performance for FDD in beside the head phantom position for the primary mechanical mode**
+
+| Operating band | Unit         | <REF <sub>lo</sub> > |
+|----------------|--------------|----------------------|
+| I              | dBm/3.84 MHz | -104                 |
+| II             | dBm/3.84 MHz | -102                 |
+| III            | dBm/3.84 MHz | -101                 |
+| IV             | dBm/3.84 MHz | -104                 |
+| V              | dBm/3.84 MHz | -99.5                |
+| VI             | dBm/3.84 MHz | -101                 |
+| VII            | dBm/3.84 MHz | -102                 |
+| VIII           | dBm/3.84 MHz | -100                 |
+| IX             | dBm/3.84 MHz | -103                 |
+| XIX            | dBm/3.84 MHz | -101                 |
+
+NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>lo</sub>> level of -101 dBm/3.84 shall apply for Band II.
+
+NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>lo</sub>> level of -103 dBm/3.84 MHz shall apply for Band IV.
+
+### I.3.1.2 UTRA LCR TDD
+
+**Table I.3.1.2-1: Handheld UE TRS recommended performance for UTRA LCR TDD in beside the head phantom position and the primary mechanical mode.**
+
+| Operating band | Unit         | <REF <sub>lo</sub> ><br>Average |
+|----------------|--------------|---------------------------------|
+| a              | dBm/1.28 MHz | -105                            |
+| b              | dBm/1.28 MHz | TBD                             |
+| c              | dBm/1.28 MHz | TBD                             |
+| d              | dBm/1.28 MHz | TBD                             |
+| e              | dBm/1.28 MHz | -105                            |
+| f              | dBm/1.28 MHz | -105                            |
+
+NOTE: Applicable for dual-mode GSM/UTRA LCR TDD.
+
+## I.3.2 Beside the head and hand phantoms position
+
+Beside the head and hand phantoms test method is defined in subclauses 4.3.3.
+
+### I.3.2.1 UTRA FDD
+
+**Table I.3.2.1-1: TRS recommended performance for UTRA FDD in the beside the head and hand phantoms position for the primary mechanical mode**
+
+| Operating band                                                                                                                                    | Unit         | <REF <sub>flor</sub> ><br>Average |
+|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------|
+| I                                                                                                                                                 | dBm/3.84 MHz | -104.0                            |
+| II                                                                                                                                                | dBm/3.84 MHz | -102.0                            |
+| III                                                                                                                                               | dBm/3.84 MHz | TBD                               |
+| IV                                                                                                                                                | dBm/3.84 MHz | TBD                               |
+| V                                                                                                                                                 | dBm/3.84 MHz | -99.75                            |
+| VI                                                                                                                                                | dBm/3.84 MHz | -99.75                            |
+| VII                                                                                                                                               | dBm/3.84 MHz | TBD                               |
+| VIII                                                                                                                                              | dBm/3.84 MHz | -99.75                            |
+| IX                                                                                                                                                | dBm/3.84 MHz | TBD                               |
+| XIX                                                                                                                                               | dBm/3.84 MHz | -99.75                            |
+| NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>flor</sub> > level of -101 dBm/3.84 shall apply for Band II.     |              |                                   |
+| NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF <sub>flor</sub> > level of -103 dBm/3.84 MHz shall apply for Band IV. |              |                                   |
+| NOTE 3: Applicable for devices narrower than 72mm as defined in TR 25.914                                                                         |              |                                   |
+| NOTE 4: Not applicable for devices supporting CDMA or carrier aggregation                                                                         |              |                                   |
+
+### I.3.2.2 UTRA LCR TDD
+
+**Table I.3.2.2-1: TRS recommended performance for UTRA LCR TDD in the beside the head and hand phantoms position and the primary mechanical mode**
+
+| Operating band                                   | Unit         | <REF <sub>flor</sub> ><br>Average |
+|--------------------------------------------------|--------------|-----------------------------------|
+| a                                                | dBm/1.28 MHz | TBD                               |
+| b                                                | dBm/1.28 MHz | TBD                               |
+| c                                                | dBm/1.28 MHz | TBD                               |
+| d                                                | dBm/1.28 MHz | TBD                               |
+| e                                                | dBm/1.28 MHz | TBD                               |
+| f                                                | dBm/1.28 MHz | TBD                               |
+| NOTE: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                                   |
+
+### I.3.2.3 E-UTRA FDD
+
+**Table I.3.2.3-1: Tablet TRS recommended performance for E-UTRA FDD in data transfer position**
+
+| Operating band | Channel bandwidth | Sensitivity (dBm) |
+|----------------|-------------------|-------------------|
+|                |                   | Average           |
+| 1              | 10 MHz            | -96.0             |
+| 2              | 10 MHz            |                   |
+| 3              | 10 MHz            | -97.0             |
+| 4              | 10 MHz            |                   |
+| 5              | 10 MHz            |                   |
+| 7              | 10 MHz            | -95.75            |
+| 8              | 10 MHz            |                   |
+| 12             | 10 MHz            |                   |
+| 13             | 10 MHz            |                   |
+| 19             | 10 MHz            | -94.5             |
+| 20             | 10 MHz            | -94.5             |
+| 21             | 15 MHz            | -93.0             |
+| 28             | 10 MHz            |                   |
+| 32             | 10 MHz            |                   |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicability for devices supporting CDMA or aggregated carriers (e.g. multi-carrier HSPA, LTE Carrier Aggregation) is FFS.
+
+### I.3.2.4 E-UTRA TDD
+
+**Table I.3.2.4-1: TBD**
+
+## I.3.3 Hand phantom browsing mode position
+
+Hand phantom browsing mode test method is defined in subclauses 4.3.4.
+
+### I.3.3.1 UTRA FDD
+
+**Table I.3.3.1-1: TRS recommended performance for UTRA FDD in hand phantom browsing mode position**
+
+| Operating band | Unit         | <REF <sub>flor</sub> > |
+|----------------|--------------|------------------------|
+|                |              | Average                |
+| I              | dBm/3.84 MHz | TBD                    |
+| II             | dBm/3.84 MHz | TBD                    |
+| III            | dBm/3.84 MHz | TBD                    |
+| IV             | dBm/3.84 MHz | TBD                    |
+| V              | dBm/3.84 MHz | TBD                    |
+| VI             | dBm/3.84 MHz | TBD                    |
+| VII            | dBm/3.84 MHz | TBD                    |
+| VIII           | dBm/3.84 MHz | TBD                    |
+| IX             | dBm/3.84 MHz | TBD                    |
+| XIX            | dBm/3.84 MHz | TBD                    |
+
+NOTE 1: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>flor</sub>> level of -101 dBm/3.84 shall apply for Band II.  
+NOTE 2: For the UE which supports DB-DC-HSDPA configuration 2, average <REF<sub>flor</sub>> level of -103 dBm/3.84 MHz shall apply for Band IV.
+
+### I.3.3.2 UTRA LCR TDD
+
+**Table I.3.3.2-1: TRS recommended performance for UTRA LCR TDD in hand phantom browsing mode position**
+
+| Operating band                                   | Unit         | <REFior> Average |
+|--------------------------------------------------|--------------|------------------|
+| a                                                | dBm/1.28 MHz | TBD              |
+| b                                                | dBm/1.28 MHz | TBD              |
+| c                                                | dBm/1.28 MHz | TBD              |
+| d                                                | dBm/1.28 MHz | TBD              |
+| e                                                | dBm/1.28 MHz | TBD              |
+| f                                                | dBm/1.28 MHz | TBD              |
+| NOTE: Applicable for dual-mode GSM/UTRA LCR TDD. |              |                  |
+
+### I.3.3.3 E-UTRA FDD
+
+**Table I.3.3.3-1 TBD**
+
+### I.3.3.4 E-UTRA TDD
+
+**Table I.3.3.4-1 TBD**
+
+## Annex J (informative): Recommended performance for LME
+
+Editor's notes: This annex is incomplete. The following items are missing or incomplete:
+
+- Table J.2.1-1, J.2.2-1, J.3.1-1 and J.3.2-1 as they are not complete in TS 37.144 yet
+- Table J.2.3-1, J.2.4-1, J.3.3-1 and J.3.4-1 as they are not specified in TS 37.144 yet
+
+### J.1 General
+
+This annex introduces the concept of recommended OTA performance for operating bands for UE's supporting LME feature. This requirement is not mandatory but is recommended.
+
+The concept of recommended performance is to ensure that UE OTA performance is maximised in order to improve user experience and network performance. It is recognised that the ability to meet the recommended performance depends on the number of frequency bands supported by the UE.
+
+### J.2 Total Radiated Power
+
+The OTA TRP performance for UTRA and E-UTRA should be greater or equal than the recommended values in this clause.
+
+Laptop ground plane phantom test method is defined in subclauses 4.3.2.
+
+#### J.2.1 UTRA FDD
+
+**Table J.2.1-1: LME TRP recommended performance for UTRA FDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+
+|                                             |   |   |     |     |     |
+|---------------------------------------------|---|---|-----|-----|-----|
+| I                                           | - | - | TBD | TBD | TBD |
+| II                                          | - | - | TBD | TBD | TBD |
+| III                                         | - | - | TBD | TBD | TBD |
+| IV                                          | - | - | TBD | TBD | TBD |
+| V                                           | - | - | TBD | TBD | TBD |
+| VI                                          | - | - | TBD | TBD | TBD |
+| VII                                         | - | - | TBD | TBD | TBD |
+| VIII                                        | - | - | TBD | TBD | TBD |
+| IX                                          | - | - | TBD | TBD | TBD |
+| XIX                                         | - | - | TBD | TBD | TBD |
+| NOTE 1: Applicable for dual-mode GSM/UMTS.  |   |   |     |     |     |
+| NOTE 2: Applicable for USB plug-in devices. |   |   |     |     |     |
+
+## J.2.2 UTRA LCR TDD
+
+Table J.2.2-1: LME TRP recommended performance for UTRA LCR TDD in data transfer position
+
+| Operating band                                     | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------------------------------------------|---------------|---------------|---------------|------------------|---------------|
+|                                                    | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                                                    | Average       | Average       | Average       | Average          | Average       |
+| a                                                  | -             | TBD           | -             | -                | -             |
+| b                                                  | -             | TBD           | -             | -                | -             |
+| c                                                  | -             | TBD           | -             | -                | -             |
+| d                                                  | -             | TBD           | -             | -                | -             |
+| e                                                  | -             | TBD           | -             | -                | -             |
+| f                                                  | -             | TBD           | -             | -                | -             |
+| NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD. |               |               |               |                  |               |
+| NOTE 2: Applicable for USB plug-in devices.        |               |               |               |                  |               |
+
+## J.2.3 E-UTRA FDD
+
+Table J.2.3-1: TBD
+
+## J.2.4 E-UTRA TDD
+
+Table J.2.4-1: TBD
+
+## J.3 Total Radiated Sensitivity
+
+The OTA TRS performance for UTRA and E-UTRA should be lower or equal than the recommended values shown in this clause.
+
+Laptop ground plane phantom test method is defined in subclauses 4.3.2.
+
+### J.3.1 UTRA FDD
+
+**Table J.3.1-1: LME TRS recommended performance for UTRA FDD in the data transfer position**
+
+| Operating band | Unit         | <REF <sub>Io</sub> > Average |
+|----------------|--------------|------------------------------|
+| I              | dBm/3.84 MHz | TBD                          |
+| II             | dBm/3.84 MHz | TBD                          |
+| III            | dBm/3.84 MHz | TBD                          |
+| IV             | dBm/3.84 MHz | TBD                          |
+| V              | dBm/3.84 MHz | TBD                          |
+| VI             | dBm/3.84 MHz | TBD                          |
+| VII            | dBm/3.84 MHz | TBD                          |
+| VIII           | dBm/3.84 MHz | TBD                          |
+| IX             | dBm/3.84 MHz | TBD                          |
+| XIX            | dBm/3.84 MHz | TBD                          |
+
+NOTE: Applicable for USB plug-in devices.
+
+### J.3.2 UTRA LCR TDD
+
+**Table J.3.2-1: LME TRS recommended performance for UTRA LCR TDD in the data transfer position**
+
+| Operating band | Unit         | <REF <sub>Io</sub> > Average |
+|----------------|--------------|------------------------------|
+| a              | dBm/1.28 MHz | TBD                          |
+| b              | dBm/1.28 MHz | TBD                          |
+| c              | dBm/1.28 MHz | TBD                          |
+| d              | dBm/1.28 MHz | TBD                          |
+| e              | dBm/1.28 MHz | TBD                          |
+| f              | dBm/1.28 MHz | TBD                          |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for USB plug-in devices.
+
+### J.3.3 E-UTRA FDD
+
+**Table J.3.3-1: TBD**
+
+### J.3.4 E-UTRA TDD
+
+**Table J.3.4-1: TBD**
+
+---
+
+## Annex K (informative): Recommended performance for LEE
+
+Editor's notes: This annex is incomplete. The following items are missing or incomplete:
+
+- Table K.2.1-1, K.2.1-2, K.2.2-1, K.2.2-2, K.3.1-1, K.3.1-2, K.3.2-1 and K.3.2-2 as they are not complete in TS 37.144 yet
+- Table K.2.3-1, K.2.3-2, K.2.4-1, K.2.4-2, K.3.3-1, K.3.3-2, K.3.4-1 and K.3.4-2 as they are not specified in TS 37.144 yet
+
+## K.1 General
+
+This annex introduces the concept of recommended OTA performance for operating bands for UE's supporting LEE feature. This requirement is not mandatory but is recommended.
+
+The concept of recommended performance is to ensure that UE OTA performance is maximised in order to improve user experience and network performance. It is recognised that the ability to meet the recommended performance depends on the number of frequency bands supported by the UE.
+
+## K.2 Total Radiated Power
+
+The OTA TRP performance for UTRA and E-UTRA should be greater or equal than the recommended values in this clause.
+
+Test method for devices with embedded modules is defined in subclauses 4.3.5.
+
+### K.2.1 UTRA FDD
+
+**Table K.2.1-1: Notebook TRP recommended performance for UTRA FDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | 21.5          | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | TBD           | TBD              | TBD           |
+| VI             | -             | -             | 21.0          | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | 21.0          | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 21.0          | TBD              | TBD           |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRP minimum performance requirements in Table K.2.1-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table K.2.1-2: Tablet TRP recommended performance for UTRA FDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| I              | -             | -             | 21.5          | TBD              | TBD           |
+| II             | -             | -             | TBD           | TBD              | TBD           |
+| III            | -             | -             | TBD           | TBD              | TBD           |
+| IV             | -             | -             | TBD           | TBD              | TBD           |
+| V              | -             | -             | 19.5          | TBD              | TBD           |
+| VI             | -             | -             | TBD           | TBD              | TBD           |
+| VII            | -             | -             | TBD           | TBD              | TBD           |
+| VIII           | -             | -             | TBD           | TBD              | TBD           |
+| IX             | -             | -             | TBD           | TBD              | TBD           |
+| XIX            | -             | -             | 19.5          | TBD              | TBD           |
+
+NOTE 1: Applicable for dual-mode GSM/UMTS.  
+NOTE 2: Applicable for tablet devices with two antennas.
+
+## K.2.2 UTRA LCR TDD
+
+**Table K.2.2-1: Notebook TRP recommended performance for UTRA LCR TDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+**Table K.2.2-2: Tablet TRP recommended performance for UTRA LCR TDD in data transfer position**
+
+| Operating band | Power class 1 | Power class 2 | Power class 3 | Power class 3bis | Power class 4 |
+|----------------|---------------|---------------|---------------|------------------|---------------|
+|                | Power (dBm)   | Power (dBm)   | Power (dBm)   | Power (dBm)      | Power (dBm)   |
+|                | Average       | Average       | Average       | Average          | Average       |
+| a              | -             | TBD           | -             | -                | -             |
+| b              | -             | TBD           | -             | -                | -             |
+| c              | -             | TBD           | -             | -                | -             |
+| d              | -             | TBD           | -             | -                | -             |
+| e              | -             | TBD           | -             | -                | -             |
+| f              | -             | TBD           | -             | -                | -             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for tablet devices.
+
+## K.2.3 E-UTRA FDD
+
+[Table K.2.3-1 and K.2.3-2 TBD]
+
+## K.2.4 E-UTRA TDD
+
+[Table K.2.4-1 and K.2.4-2 TBD]
+
+## K.3 Total Radiated Sensitivity
+
+The OTA TRS performance for UTRA and E-UTRA should be lower or equal than the recommended values shown in this clause.
+
+Test method for devices with embedded modules is defined in subclauses 4.3.5.
+
+### K.3.1 UTRA FDD
+
+**Table K.3.1-1: Notebook TRS recommended performance for UTRA FDD in the data transfer position**
+
+| Operating band | Unit         | <REFI <sub>o</sub> ><br>Average |
+|----------------|--------------|---------------------------------|
+| I              | dBm/3.84 MHz | -106.5                          |
+| II             | dBm/3.84 MHz | TBD                             |
+| III            | dBm/3.84 MHz | TBD                             |
+| IV             | dBm/3.84 MHz | TBD                             |
+| V              | dBm/3.84 MHz | TBD                             |
+| VI             | dBm/3.84 MHz | -104.5                          |
+| VII            | dBm/3.84 MHz | TBD                             |
+| VIII           | dBm/3.84 MHz | -104.5                          |
+| IX             | dBm/3.84 MHz | TBD                             |
+| XIX            | dBm/3.84 MHz | -104.5                          |
+
+NOTE 1: Applicable for multi-mode GSM/UMTS/LTE.  
+NOTE 2: Applicable for notebook devices.
+
+NOTE: TRS minimum performance requirements in Table K.3.1-1 apply to HSPA and LTE UEs supporting only single carrier operation. Their applicability to multi-carrier operation is FFS. This is because it has not been verified whether the UEs measured to derive the requirements supported carrier aggregation or not.
+
+**Table K.3.1-2: Tablet TRS recommended performance for UTRA FDD in the data transfer position**
+
+| Operating band | Unit         | <REFI <sub>o</sub> ><br>Average |
+|----------------|--------------|---------------------------------|
+| I              | dBm/3.84 MHz | -108.75                         |
+| II             | dBm/3.84 MHz | TBD                             |
+| III            | dBm/3.84 MHz | TBD                             |
+| IV             | dBm/3.84 MHz | TBD                             |
+| V              | dBm/3.84 MHz | -106.0                          |
+| VI             | dBm/3.84 MHz | TBD                             |
+| VII            | dBm/3.84 MHz | TBD                             |
+| VIII           | dBm/3.84 MHz | TBD                             |
+| IX             | dBm/3.84 MHz | TBD                             |
+| XIX            | dBm/3.84 MHz | -106.0                          |
+
+NOTE: Applicable for tablet devices with two antennas.
+
+### K.3.2 UTRA LCR TDD
+
+**Table K.3.2-1: Notebook TRS recommended performance for UTRA LCR TDD in the data transfer position**
+
+| Operating band | Unit         | <REFI <sub>o</sub> ><br>Average |
+|----------------|--------------|---------------------------------|
+| a              | dBm/1.28 MHz | TBD                             |
+| b              | dBm/1.28 MHz | TBD                             |
+| c              | dBm/1.28 MHz | TBD                             |
+| d              | dBm/1.28 MHz | TBD                             |
+| e              | dBm/1.28 MHz | TBD                             |
+| f              | dBm/1.28 MHz | TBD                             |
+
+NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.  
+NOTE 2: Applicable for notebook devices.
+
+**Table K.3.2-2: Tablet TRS recommended performance for UTRA LCR TDD in the data transfer position**
+
+| Operating band                                                                               | Unit         | <REFior><br>Average |
+|----------------------------------------------------------------------------------------------|--------------|---------------------|
+| a                                                                                            | dBm/1.28 MHz | TBD                 |
+| b                                                                                            | dBm/1.28 MHz | TBD                 |
+| c                                                                                            | dBm/1.28 MHz | TBD                 |
+| d                                                                                            | dBm/1.28 MHz | TBD                 |
+| e                                                                                            | dBm/1.28 MHz | TBD                 |
+| f                                                                                            | dBm/1.28 MHz | TBD                 |
+| NOTE 1: Applicable for dual-mode GSM/UTRA LCR TDD.<br>NOTE 2: Applicable for tablet devices. |              |                     |
+
+### K.3.3 E-UTRA FDD
+
+[Table K.3.3-1 and K.3.3-2 TBD]
+
+### K.3.4 E-UTRA TDD
+
+[Table K.3.4-1 and K.3.4-2 TBD]
+
+---
+
+## Annex L (informative): Multi-Probe Anechoic Chamber Specification and Validation Method
+
+### L.1 Multi-probe anechoic chamber specifications
+
+The Multi-Probe Anechoic Chamber implementation is based on the full SCME implementation described in TR 37.977 [29] clause 6.3.1.1 and would be evaluated for shielding effectiveness in accordance with Annex G.1 and would follow the recommendations in Annex A.3.5.
+
+### L.2 Multi-probe anechoic chamber minimum distance between the DUT and the measurement antenna
+
+The multi-probe anechoic chamber minimum distance between the DUT and the measurement antenna would follow the recommendations in Annex A.3.3.
+
+### L.3 Multi-probe anechoic chamber quiet zone reflectivity level validation
+
+The multi-probe anechoic chamber quiet zone reflectivity level validation is performed in accordance with Annex G.2 and Annex G.3 and would follow the recommendations in Annex A.3.2 and Annex A.3.4.
+
+### L.4 Multi-probe anechoic chamber channel model verification
+
+The multi-probe anechoic chamber channel model verification is performed in accordance with TR 37.977 [29] clause 8.3 for the channel model defined in clause 7.4.1.2 at the downlink centre frequency of the mid-channel defined in TS 36.508 [10] for the operating bands defined in clause 7.4.1.2. The results are expected to meet the recommended limits in TR 37.977 [29] clause 8.3.3.
+
+## Annex M (normative): Channel Model emulation of the Base Station antenna pattern configuration for Radiated Performance of Multiple-antenna Receivers
+
+### M.1 Channel Model(s)
+
+The following channel models are used in evaluation of MIMO OTA methodologies.
+
+The generic models are
+
+- SCME Urban micro-cell, and
+
+In addition, the BS antenna assumptions defined in Annex M.2 also apply when emulating the channel models.
+
+In the following we define the cross polarization power ratio a propagation channel as  $\rho$ , where
+
+and
+
+and
+
+- $S_{VV}$  is the coefficient for scattered/reflected power on V-polarization and incident power on V-polarization;
+- $S_{VH}$  is the coefficient for scattered/reflected power on V-polarization and incident power on H-polarization;
+- $S_{HV}$  is the coefficient for scattered/reflected power on H-polarization and incident power on V-polarization;
+- $S_{HH}$  is the coefficient for scattered/reflected power on H-polarization and incident power on H-polarization.
+
+NOTE: For Vertical only measurements, the powers per delay are used without regard to the specified XPR values.
+
+The following SCME Urban Micro-cell is unchanged from the original SCME paper, with added XPR values, Direction of Travel, and Velocity.
+
+**Table M.1-1: SCME urban micro-cell channel model**
+
+| SCME Urban micro-cell                                    |            |     |     |            |       |       |                    |                    |
+|----------------------------------------------------------|------------|-----|-----|------------|-------|-------|--------------------|--------------------|
+| Cluster #                                                | Delay [ns] |     |     | Power [dB] |       |       | AoD [ $^{\circ}$ ] | AoA [ $^{\circ}$ ] |
+| 1                                                        | 0          | 5   | 10  | -3.0       | -5.2  | -7.0  | 6.6                | 0.7                |
+| 2                                                        | 285        | 290 | 295 | -4.3       | -6.5  | -8.3  | 14.1               | -13.2              |
+| 3                                                        | 205        | 210 | 215 | -5.7       | -7.9  | -9.7  | 50.8               | 146.1              |
+| 4                                                        | 660        | 665 | 670 | -7.3       | -9.5  | -11.3 | 38.4               | -30.5              |
+| 5                                                        | 805        | 810 | 815 | -9.0       | -11.2 | -13.0 | 6.7                | -11.4              |
+| 6                                                        | 925        | 930 | 935 | -11.4      | -13.6 | -15.4 | 40.3               | -1.1               |
+| Delay spread [ns]                                        |            |     |     |            |       |       |                    | 294                |
+| Cluster AS AoD / AS AoA [ $^{\circ}$ ]                   |            |     |     |            |       |       |                    | 5 / 35             |
+| Cluster PAS shape                                        |            |     |     |            |       |       |                    | Laplacian          |
+| Total AS AoD / AS AoA [ $^{\circ}$ ]                     |            |     |     |            |       |       |                    | 18.2 / 67.8        |
+| Mobile speed [km/h] / Direction of travel [ $^{\circ}$ ] |            |     |     |            |       |       |                    | 3, 30 / 120        |
+| XPR                                                      |            |     |     |            |       |       |                    | 9 dB               |
+| (NOTE: V & H components based on assumed BS antennas)    |            |     |     |            |       |       |                    |                    |
+| Mid-paths Share Cluster parameter values for:            |            |     |     |            |       |       |                    | AoD, AoA, AS, XPR  |
+
+The parameters of the channel models are the expected parameters for the MIMO OTA channel models. However, the final channel model achieved for different methods could be a combined effect of the chamber and the channel emulator.
+
+The Rayleigh fading may be implementation specific. However, the fading can be considered to be appropriate as long as the statistics of the generated Rayleigh fading are within standard requirement on Rayleigh fading statistics.
+
+## M.2 Base Station antenna pattern configuration
+
+The emulated BS antennas to be used for all emulation of the channel models defined in Annex M.1 shall be assumed to be dual polarized equal power elements with a fixed  $0\lambda$  separation, 45 degrees slanted.
+
+The slant 45 degree antenna is an "X" configuration and is modelled as an ideal dipole with isotropic gain and subject to a foreshortening of the slanted radiating element, which is observed to vary as a function of the path angle of departure. This foreshortening with AoD is a typical slanted dipole behaviour and is a source of power variation in the channel model. The effective antenna pattern for this antenna is illustrated in Figure M.2-1.
+
+![Figure M.2-1: X antenna gain assumption. (a) Linear gain plot showing Gain Linear vs Azimuth Angle in deg. (b) dB gain plot showing Gain in dB vs Azimuth Angle in deg. Both plots show four curves: V1 (solid red), H1 (solid green), V2 (dashed blue), and H2 (dashed black).](7c320c137b880b30ff882c610c458aa1_img.jpg)
+
+Figure M.2-1 consists of two plots, (a) and (b), showing the gain assumption for an X antenna. Both plots have 'Azimuth Angle in deg' on the x-axis, ranging from -200 to 200. Plot (a) shows 'Gain Linear' on the y-axis, ranging from -1 to 1. Plot (b) shows 'Gain in dB' on the y-axis, ranging from -50 to 0. Both plots display four curves: V1 (solid red line), H1 (solid green line), V2 (dashed blue line), and H2 (dashed black line). In both plots, V1 and V2 are horizontal lines at a gain of 1 (0 dB). H1 and H2 show a periodic variation with a minimum at 0 degrees azimuth. In plot (b), a tooltip indicates that at an azimuth angle of 45 degrees, the gain is -6.021 dB for H1 and H2, and -3.01 dB for V1 and V2.
+
+Figure M.2-1: X antenna gain assumption. (a) Linear gain plot showing Gain Linear vs Azimuth Angle in deg. (b) dB gain plot showing Gain in dB vs Azimuth Angle in deg. Both plots show four curves: V1 (solid red), H1 (solid green), V2 (dashed blue), and H2 (dashed black).
+
+Figure M.2-1: X antenna gain assumption (a) Linear gain (b) dB gain
+
+## Annex N (informative): Estimation of measurement uncertainty for Multiple-antenna receivers
+
+### N.1 General
+
+Editor's notes: Table N.1-1 is based on a similar table in RAN4 TR 37.977. There are a number of inconsistencies (examples are listed below) and errors in the source table that are still remaining in Table N.1-1. They should be fixed once RAN4 fixes the corresponding table in TR 37.977.
+
+- NOTES 1, 3 & 4 are not relevant to MPAC; the NOTES should be removed.
+- Item 19 is not relevant to MPAC and should be removed.
+- Items 9 and 10 seem to be related to SIR that is out of scope of the WI; these may be removed from the table.
+
+Individual uncertainty contributions in the TRMS measurements are discussed and evaluated in this Annex. A technique for calculating the total measurement uncertainty is also presented.
+
+An important part of a standard measurement procedure is the identification of uncertainty sources and the evaluation of the overall measurement uncertainty. There are various individual uncertainty sources in the measurement procedure that introduce a certain uncertainty contribution to the final measurement result. The approach in this standard test procedure is that the test laboratories are not limited to using some specific instruments and antenna positioners, for example. However, a limit is set for the maximum overall measurement uncertainty.
+
+The TRMS measurement procedure can be considered to include two stages. In Stage 1 the actual measurement of the MIMO OTA throughput of the Device Under Test (DUT) is performed. In Stage 2 the calibration of the absolute level of the DUT measurement results is performed.
+
+The uncertainty contributions related to TRMS are listed in Tables N.1-1. The uncertainty contributions are analysed in the following paragraphs.
+
+The calculation of the uncertainty contribution is based on the ISO Guide to the expression of uncertainty in measurement. Each individual uncertainty is expressed by its Standard Deviation (termed here as 'standard uncertainty') and represented by symbol  $U$ . The uncertainty contributions can be classified to two categories: Type-A uncertainties, which are statistically determined e.g. by repeated measurements, and Type-B uncertainties, which are derived from existing data e.g. data sheets. Several individual uncertainties are common in Stage 1 and Stage 2 and therefore cancel.
+
+The procedure of forming the uncertainty budget in measurement is:
+
+- 1) Compile lists of individual uncertainty contributions for measurements in both Stage 1 and Stage 2.
+- 2) Determine the standard uncertainty of each contribution by
+  - a) Determining the distribution of the uncertainty (Gaussian, U-shaped, rectangular, etc.)
+  - b) Determining the maximum value of each uncertainty (unless the distribution is Gaussian)
+  - c) Calculating the standard uncertainty by dividing the uncertainty by  $\sqrt{2}$  if the distribution is U-shaped, and by  $\sqrt{3}$  if the distribution is rectangular.
+- 3) Convert the units into decibel, if necessary.
+- 4) Combine all the standard uncertainties by the Root of the Sum of the Squares (RSS) method.
+- 5) Combine the total uncertainties in Stage 1 and Stage 2 also by the RSS method:
+ 
+$$u_c = \sqrt{u_{c,DUT\ measurement}^2 + u_{c,calibration\ measurement}^2}$$
+- 6) Multiply the result by an expansion factor of 1.96 to derive expanded uncertainty at 95% confidence level:  $1.96 * u_c$ .
+
+**Table N.1-1: Measurement uncertainty budget for Multiprobe Anechoic method**
+
+| #  | Description of uncertainty contribution                                                                                                             | Details in                             | MPAC                                                        |                                                 |                      |
+|----|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|-------------------------------------------------|----------------------|
+|    |                                                                                                                                                     |                                        | Example Value [dB]                                          | Prob Distr                                      | Std Uncertainty [dB] |
+|    | <b>Stage 1-DUT measurement</b>                                                                                                                      |                                        |                                                             |                                                 |                      |
+| 1  | Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                   | TS 34.114, E.1-E.2                     | 0.00                                                        | u-shape                                         | 0.00                 |
+| 2  | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-E.5                     | 0.00                                                        | rect                                            | 0.00                 |
+| 3  | Influence of the fixed measurement antenna cable                                                                                                    | TS 34.114, E.6                         | 0.00                                                        | rect                                            | 0.00                 |
+| 4  | Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                           | TS 34.114, E.7                         | 0.00                                                        | rect                                            | 0.00                 |
+| 5  | Base station simulator: uncertainty of the absolute output level                                                                                    | TS 34.114, E.17<br>[TS 36.521-1 F.1.3] | 1.00                                                        | rect                                            | 0.58                 |
+| 6  | Throughput measurement: output level step resolution                                                                                                | TS 34.114, E.18                        | 0.25                                                        | rect                                            | 0.14                 |
+| 7  | Statistical uncertainty of throughput measurement                                                                                                   | TS34.114, E.19                         | FFS<br>(negligible and partially included in repeatability) |                                                 |                      |
+| 8  | Fading channel emulator output uncertainty (if used)<br>- absolute output power<br>- output signal stability<br>- output stability with temperature | N.2                                    | 1.5dB<br>0.5dB<br>0.4dB                                     | normal<br>(output power)<br>rect<br>(stability) | 0.84                 |
+| 9  | AWGN flatness within LTE band                                                                                                                       | TBD (NOTE 4)                           |                                                             |                                                 | FFS                  |
+| 10 | Signal-to noise ratio uncertainty, averaged over downlink transmission Bandwidth                                                                    | TBD (NOTE 4)                           |                                                             |                                                 | FFS                  |
+| 11 | Channel model implementation (NOTE 2)                                                                                                               | TBD                                    | FFS                                                         |                                                 | FFS                  |
+| 12 | Chamber statistical ripple and repeatability                                                                                                        | TS 34.114, E.26.A                      | N/A                                                         |                                                 | 0.00                 |
+| 13 | Additional power loss in EUT chassis                                                                                                                | TS 34.114, E.26.B                      | N/A                                                         |                                                 | 0.00                 |
+| 14 | Quality of the quiet zone                                                                                                                           | TS 34.114, E.10                        | 0.50                                                        | std                                             | 0.50                 |
+| 15 | Measurement Distance<br>- VSWR<br>- Chamber Standing Wave                                                                                           | TS 34.114, E.9                         | 0.00                                                        |                                                 | 0.00                 |
+| 16 | DUT sensitivity drift                                                                                                                               | TS 34.114, E.21                        | 0.20                                                        | rect                                            | 0.12                 |
+| 17 | Uncertainty related to the use of the phantoms:                                                                                                     |                                        |                                                             |                                                 | 0.00                 |
+
+|    |                                                                                                                 |                    |      |         |             |
+|----|-----------------------------------------------------------------------------------------------------------------|--------------------|------|---------|-------------|
+|    | a) Uncertainty of dielectric properties and shape of the hand phantom                                           | TR 25.914, A.12.3  |      |         | 0.00        |
+|    | b) Uncertainty related to the use of laptop ground plane phantom                                                | TR 25.914, A.12.4  |      |         | 0.00        |
+| 18 | Random uncertainty (repeatability)                                                                              | TS 34.114, E.14    | 0.20 | rect    | 0.12        |
+| 19 | Uncertainty associated with the stirring method and number of subframes (NOTE 3)                                |                    | N/A  |         | 0.00        |
+|    | <b>Stage 2-Calibration measurement</b>                                                                          |                    |      |         | <b>0.00</b> |
+| 20 | Uncertainty of network analyzer<br>- Receiver and Source VNA<br>- Receiver VNA Calibration prior to measurement | TS 34.114, E.15    | 0.50 | rect    | 0.29        |
+| 21 | Mismatch of transmitter chain                                                                                   | TS 34.114, E.1-E.2 | 0.20 | u-shape | 0.14        |
+| 22 | Insertion loss of transmitter chain                                                                             | TS 34.114, E.3-E.5 | 0.00 |         | 0.00        |
+| 23 | Mismatch in the connection of calibration antenna                                                               | TS 34.114, E.1     | 0.00 | rect    | 0.00        |
+| 24 | Influence of the calibration antenna feed cable                                                                 | TS 34.114, E.6     |      |         | 0.00        |
+| 25 | Influence of the transmitter antennas/probes cables                                                             | TS 34.114, E.6     | 0.00 | rect    | 0.00        |
+| 26 | Uncertainty of the absolute gain of the transmitter antennas/probes                                             | TS 34.114, E.7     | 0.00 | rect    | 0.00        |
+| 27 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                | TS 34.114, E.16    | 0.50 | std     | 0.50        |
+| 28 | Chamber statistical ripple and repeatability                                                                    | TS 34.114, E.26.A  |      |         | 0.00        |
+| 29 | Phase Centre Offset (when using horn to calibrate)                                                              | TS 34.114, E.9     | 0.00 | rect    | 0.00        |
+| 30 | Quality of the quiet zone (Range Ref. Antenna)                                                                  | TS 34.114, E.10    | 0.50 | rect    | 0.29        |
+|    | <b>External Amplifiers</b>                                                                                      |                    |      |         | <b>0.00</b> |
+| 31 | Stability                                                                                                       | N.3.1              | 0.30 | rect    | 0.17        |
+| 32 | Linearity                                                                                                       | N.3.2              | 0.10 | rect    | 0.06        |
+| 33 | Noise Figure                                                                                                    | N.3.3              | 0.30 | rect    | 0.17        |
+| 34 | Mismatch                                                                                                        | N.3.4              | 0.00 | rect    | 0.00        |
+| 35 | Gain                                                                                                            | N.3.5              | 0.00 | rect    | 0.00        |
+
+NOTE 1: 0dB if fading for RTS is done in baseband; same as RC&CE and MPAC if fading is not in baseband
+
+NOTE 2: assumption is that MU set to 0dB with channel model validation pass/fail limits (FFS) that have negligible impact on TP FOM; MU for channel model validation is FFS
+
+NOTE 3: Analysis of the element associated with stirring method and number of subframes is based on existing harmonization test campaign data and can be further augmented by additional measurements. The following combinations of stirring modes and number of subframes have been identified as common use cases with the following standard uncertainties (different combinations require separate validation):
+
+A: stepped stirring mode with 20k SF per stirring state: 0dB
+
+B: stepped stirring mode with 400 SF per stirring state: 0.22dB
+
+C: continuous stirring mode with 20k SF per sample: FFS
+
+D: continuous stirring mode with 400 SF per sample: FFS
+
+Until MU elements for continuous stirring modes have been defined, the test plan shall only consider stepped stirring approach
+
+NOTE 4: As the applicability of SIR to MIMO OTA performance evaluation is FFS, the measurement uncertainty treatment for SIR related items will remain FFS. When the applicability of SIR is confirmed, the measurement uncertainty treatment defined in 3GPP TS 36.521-1 [11] Table F.1.4-1 for line item 8.2.1.3.1 should be considered along with the related test system constraints. Any adjustments to the test system limits or uncertainty definitions necessary for MIMO OTA performance testing should be applied.
+
+## N.2 Fading channel emulator output uncertainty
+
+In the case where a fading channel emulator is used, the outputs of the fading channel emulator are used to drive signals through the amplifiers, if necessary, to the probe antennas in the MIMO OTA tests either as an absolute level or as a relative level. The receiving device used is a UE. Generally, an uncertainty contribution comes from the absolute level accuracy, non-linearity, and output signal stability of the fading channel emulator. All of the contributions should be considered. However, the applicability of each contribution is contingent on the specific measurement implementation and calibration procedure.
+
+This uncertainty should be determined from the manufacturer's data sheet expressed in dB with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [33]). Furthermore, the uncertainty of the non-linearity and the output signal stability of the device may be included in the absolute level uncertainty. If not, the non-linearity, output signal stability and output signal stability versus temperature should be determined from the manufacturer's data sheet. Once determined, the non-linearity uncertainty and the output signal stability uncertainties should be combined with the output uncertainty using the RSS method.
+
+## N.3 External Amplifiers Uncertainty Terms
+
+Any components in the setup can potentially introduce measurement uncertainty. It is then needed to determine the uncertainty contributors associated with the use of such components. For the case of external amplifiers, the following uncertainties should be considered but the applicability is contingent to the measurement implementation and calibration procedure.
+
+### N.3.1 Stability
+
+An uncertainty contribution comes from the output level stability of the amplifier. Even if the amplifier is part of the system for both measurement and calibration, the uncertainty due to the stability shall be considered. This uncertainty can be either measured or determined by the manufacturers' data sheet for the operating conditions in which the system will be required to operate.
+
+### N.3.2 Linearity
+
+An uncertainty contribution comes from the linearity of the amplifier since in most cases calibration and measurements are performed at two different input/output power levels. This uncertainty can be either measured or determined by the manufacturers' data sheet.
+
+### N.3.3 Noise Figure
+
+When the signal goes into an amplifier, noise is added so that the SNR at the output is reduced with regard to the SNR of the signal at the input. This added noise introduces error on the signal which affects the Error Rate of the receiver thus the EVM (Error Vector Magnitude). An uncertainty can be calculated through the following formula:
+
+$$\varepsilon_{EVM} = 20 \cdot \log \left( 1 + 10^{\frac{-SNR}{20}} \right)$$
+
+where SNR is the signal to noise ratio in dB at the signal level used during the sensitivity measurement.
+
+### N.3.4 Mismatch
+
+If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, the mismatch uncertainty at its input and output shall be either measured or determined by the method described in [3].
+
+## N.3.5 Gain
+
+If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, this uncertainty shall be considered.
+
+---
+
+## Annex O (normative): Environmental conditions
+
+### O.1 General
+
+This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of the present documents shall be fulfilled.
+
+---
+
+### O.2 Environmental requirements
+
+The requirements in this clause apply to all types of UE(s) and MS(s).
+
+#### O.2.1 Temperature
+
+All the OTA requirements are applicable in room temperature e.g. 25°C.
+
+#### O.2.2 Voltage
+
+The UE or MS shall be equipped with a real battery that is fully charged (in the beginning of the Test).
+
+---
+
+## Annex P (normative): Base Station (BS) configuration for Radiated Performance of Multiple-antenna Receivers
+
+### P.1 eNodeB emulator settings
+
+The eNodeB emulator parameters shall be set according to Table P.1-1 for FDD and Table P.1-2 for TDD. The settings for DL stream 1 and stream 2 are the same.
+
+**Table P.1-1: Settings for FDD eNodeB emulator**
+
+| <b>eNodeB settings (Note 1)</b>                                                                                                                                                                                                                          | <b>Unit</b>  | <b>Value</b>                                                                   |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------|
+| <b>Physical channel</b>                                                                                                                                                                                                                                  |              |                                                                                |
+| Connection mode of UE                                                                                                                                                                                                                                    |              | Connection established                                                         |
+| DL MIMO mode                                                                                                                                                                                                                                             |              | 2 x 2 open loop spatial multiplexing                                           |
+| Duplex mode                                                                                                                                                                                                                                              |              | FDD                                                                            |
+| Operating band<br>(UL channel,<br>DL channel)                                                                                                                                                                                                            |              | Band 7 (21100, 3100)<br>Band 20 (24300, 6300)                                  |
+| Schedule type                                                                                                                                                                                                                                            |              | Reference Measurement Channel (RMC)                                            |
+| Reference Channel                                                                                                                                                                                                                                        |              | R.35 (Note 2)                                                                  |
+| Bandwidth DL                                                                                                                                                                                                                                             | MHz          | 10                                                                             |
+| Number of RBs DL                                                                                                                                                                                                                                         |              | 50                                                                             |
+| Start RB DL                                                                                                                                                                                                                                              |              | 0                                                                              |
+| Modulation DL                                                                                                                                                                                                                                            |              | 64QAM                                                                          |
+| Maximum Theoretical Throughput                                                                                                                                                                                                                           | Mbps         | 35.424                                                                         |
+| TBS Idx DL                                                                                                                                                                                                                                               |              | 18 (RMC defined, Note 2)                                                       |
+| Bandwidth UL                                                                                                                                                                                                                                             | MHz          | 10                                                                             |
+| Number of RBs UL                                                                                                                                                                                                                                         |              | 50                                                                             |
+| Start RB UL                                                                                                                                                                                                                                              |              | 0                                                                              |
+| Modulation UL                                                                                                                                                                                                                                            |              | QPSK                                                                           |
+| TBS Idx UL                                                                                                                                                                                                                                               |              | 6 (RMC defined)                                                                |
+| Transmit power control                                                                                                                                                                                                                                   | dBm          | -10/10 MHz, open loop (Note 3)                                                 |
+| PDSCH power offset relative to RS EPRE                                                                                                                                                                                                                   | dB           | $\rho_A = -3$<br>$\rho_B = -3$                                                 |
+| Number of HARQ transmissions                                                                                                                                                                                                                             |              | 1 (no HARQ re-transmissions)                                                   |
+| AWGN                                                                                                                                                                                                                                                     |              | OFF                                                                            |
+| DL power level<br>(RS EPRE)                                                                                                                                                                                                                              | dBm / 15 kHz | Set at eNodeB simulator<br>with correction from calibration                    |
+| Number of subframes for FOM measurement                                                                                                                                                                                                                  |              | 2000 minimum for static channel<br>20000 minimum for faded channel<br>(Note 4) |
+| NOTE 1: This set of parameters is aligned with R&S CMW500, Anritsu MTC8820C, AT&T S3110B, and Agilent E6621A (to be confirmed).                                                                                                                          |              |                                                                                |
+| NOTE 2: This RMC is defined in 3GPP TS 36.521-1 [12], Table A.3.3.2.1-1. R.35 subframes 1-4 and 6-9 utilize DL TBS 18, while R.35 subframe 0 utilizes TBS 17 (See Table A.3.3.2.1-1 Fixed Reference Channel two antenna ports in 3GPP TS 36.521-1 [12]). |              |                                                                                |
+| NOTE 3: No uplink power control.                                                                                                                                                                                                                         |              |                                                                                |
+| NOTE 4: These values might need to be increased for frequency and mobile speed reasons.                                                                                                                                                                  |              |                                                                                |
+
+**Table P.1-2: Settings for TDD eNodeB emulator**
+
+| <b>eNodeB settings</b>                  | <b>Unit</b>  | <b>Value</b>                                                                   |
+|-----------------------------------------|--------------|--------------------------------------------------------------------------------|
+| <b>Physical channel</b>                 |              |                                                                                |
+| Connection mode of UE                   |              | Connection established                                                         |
+| DL MIMO mode                            |              | 2 x 2 open loop spatial multiplexing                                           |
+| Duplex mode                             |              | TDD                                                                            |
+| Operating band<br>(UL / DL channel)     |              | Band 38 (38000)<br>Band 39 (38450)<br>Band 40 (39150)<br>Band 41 (40620)       |
+| Schedule type                           |              | Reference Measurement Channel (RMC)                                            |
+| Reference Channel                       |              | Table P.1-3                                                                    |
+| Up/Downlink Frame Configuration         |              | 1                                                                              |
+| Special Frame configuration             |              | 7                                                                              |
+| Bandwidth DL                            | MHz          | 20                                                                             |
+| Number of RBs DL                        |              | 100                                                                            |
+| Start RB DL                             |              | 0                                                                              |
+| Modulation DL                           |              | 64QAM                                                                          |
+| TBS Idx DL                              |              | 16 (RMC defined, NOTE 1)                                                       |
+| Bandwidth UL                            | MHz          | 20                                                                             |
+| Number of RBs UL                        |              | 100                                                                            |
+| Start RB UL                             |              | 0                                                                              |
+| Modulation UL                           |              | QPSK                                                                           |
+| TBS Idx UL                              |              | 6                                                                              |
+| Transmit power control                  | dBm          | -10/20 MHz, open loop (NOTE 2)                                                 |
+| PDSCH power offset relative to RS EPRE  | dB           | $\rho_A = -3$<br>$\rho_B = -3$                                                 |
+| Number of HARQ transmissions            |              | 1 (no HARQ re-transmissions)                                                   |
+| AWGN                                    |              | OFF                                                                            |
+| DL power level<br>(RS EPRE)             | dBm / 15 kHz | Set at eNodeB simulator<br>with correction from calibration                    |
+| Number of subframes for FOM measurement |              | 2000 minimum for static channel<br>20000 minimum for faded channel<br>(NOTE 3) |
+
+NOTE 1: This RMC is defined in Table P.1-3. Subframes 0, 1, 4, 6 and 9 utilize DL TBS 16, subframe 5 is unused for DL data transmission and other subframes are for UL.
+
+NOTE 2: No uplink power control.
+
+NOTE 3: These values might need to be increased for frequency and mobile speed reasons.
+
+**Table P.1-3: Fixed Reference Channel two antenna ports for 20MHz TD-LTE**
+
+| <b>Parameter</b>                                                                                                                                | <b>Unit</b> | <b>Value</b> |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------|
+| Channel bandwidth                                                                                                                               | MHz         | 20           |
+| Allocated resource blocks (Note 3)                                                                                                              |             | 100          |
+| Uplink-Downlink Configuration (Note 1)                                                                                                          |             | 1            |
+| Allocated subframes per Radio Frame (D+S)                                                                                                       |             | 4+2          |
+| Modulation                                                                                                                                      |             | 64QAM        |
+| Target Coding Rate                                                                                                                              |             | 0.4          |
+| Information Bit Payload (Note 3)                                                                                                                |             |              |
+| For Sub-Frames 4,9                                                                                                                              | Bits        | 32856        |
+| For Sub-Frames 1,6                                                                                                                              |             | 24496        |
+| For Sub-Frame 5                                                                                                                                 | Bits        | N/A          |
+| For Sub-Frame 0                                                                                                                                 | Bits        | 32856        |
+| Number of Code Blocks (Notes 2 and 3)                                                                                                           |             |              |
+| For Sub-Frames 4,9                                                                                                                              |             | 5            |
+| For Sub-Frames 1,6                                                                                                                              |             | 4            |
+| For Sub-Frame 5                                                                                                                                 |             | N/A          |
+| For Sub-Frame 0                                                                                                                                 |             | 5            |
+| Binary Channel Bits (Note 3)                                                                                                                    |             |              |
+| For Sub-Frames 4,9                                                                                                                              | Bits        | 82800        |
+| For Sub-Frames 1,6                                                                                                                              |             | 67968        |
+| For Sub-Frame 5                                                                                                                                 | Bits        | N/A          |
+| For Sub-Frame 0                                                                                                                                 | Bits        | 80712        |
+| Max. Throughput averaged over 1 frame (Note 3)                                                                                                  | Mbps        | 14.756       |
+| UE Category                                                                                                                                     |             | $\geq 1$     |
+| NOTE 1: As per Table 4.2-2 in TS 36.211 [33].                                                                                                   |             |              |
+| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). |             |              |
+| NOTE 3: Given per component carrier per codeword                                                                                                |             |              |
+
+## Annex Q (informative): RTS Anechoic Chamber Specification and Validation Method
+
+### Q.1 RTS anechoic chamber specifications
+
+The RTS Anechoic Chamber implementation is based on the full SCME implementation described in TR 37.977 [29] clause 6.3.1.3 and would be evaluated for shielding effectiveness in accordance with Annex G.1 and would follow the recommendations in Annex A.3.5.
+
+### Q.2 RTS anechoic chamber minimum distance between the DUT and the measurement antenna
+
+The RTS anechoic chamber minimum distance between the DUT and the measurement antenna would follow the recommendations in Annex A.3.3.
+
+### Q.3 RTS anechoic chamber quiet zone reflectivity level validation
+
+The RTS anechoic chamber quiet zone reflectivity level validation is performed in accordance with Annex G.2 and Annex G.3 and would follow the recommendations in Annex A.3.2 and Annex A.3.4.
+
+## Q.4 RTS anechoic chamber channel model verification
+
+The RTS anechoic chamber channel model verification is performed in accordance with TR 37.977 [29] clause 8.3 for the channel model defined in clause 7.4.1.2 at the downlink centre frequency of the mid-channel defined in TS 36.508 [10] for the operating bands defined in clause 7.4.1.2. The results are expected to meet the recommended limits in TR 37.977 [29] clause 8.3.3.
+
+## Annex R: UE ATF Requirements
+
+This annex defines the accuracy requirements for the RSAP and RSARP measurements, these requirements are normative for devices using the RTS method as defined in section 7.4.
+
+It should be noted that the two-stage test method includes RSAP and RSARP validation and if necessary linearization of the results prior to calibration of the results against known radiated metrology standards, therefore the requirement for RSAP and RSARP is that they are monotonic over a given range and resolution. As a consequence their absolute accuracies are not relevant. However, due to the similarity with RSRP, in order to guide RSAP implementation, an upper bound limit on accuracy is defined for RSAP. Since RSAP is measured in much easier conditions than RSRP, the RSRP absolute requirement will not increase the demands on existing receiver designs.
+
+### R.1 RSAP
+
+The requirements for RSAP accuracy are given in Table R-1.
+
+**Table R-1: Reference Signal Antenna Power requirements**
+
+| Parameter         | Value                                                                                                                                                                              |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Absolute accuracy | ± 6 dB                                                                                                                                                                             |
+| Range             | RSAP absolute accuracy and monotonicity to be maintained over the range -60 dBm to -80 dBm incident power measured at the orientation of the DUT's maximum antenna gain.           |
+| Monotonicity      | Monotonicity over a 1 dB interval. This is necessary to enable linearization of the UE RSAP response as part of the accuracy requirements for the derived complex antenna pattern. |
+
+### R.2 RSARP
+
+The requirements for RSARP accuracy are given in Table R-2.
+
+**Table R-2: Reference Signal Antenna Relative Phase requirements**
+
+| Parameter    | Value                                                                                                                                                                                   |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Range        | RSARP monotonicity to be maintained over the range -60 dBm to -80 dBm incident power measured at the orientation of the DUT's maximum antenna gain.                                     |
+| Monotonicity | Monotonicity over a 5 degree interval. This is necessary to enable linearization of the UE RSARP response as part of the accuracy requirements for the derived complex antenna pattern. |
+
+## Annex S: Change history
+
+| Change history |         |           |      |     |                                                                                                                          |        |        |
+|----------------|---------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #   | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                                          | Old    | New    |
+| 2014-08        | RAN5#64 | R5-14xxxx | -    | -   | TS 37.544 Skeleton proposed for RAN5#64                                                                                  | -      | 0.0.1  |
+| 2014-09        | RAN5#64 | R5-144940 | -    | -   | TS 37.544 v0.1.0                                                                                                         | 0.0.1  | 0.1.0  |
+| 2014-11        | RAN5#65 | R5-145473 | -    | -   | TS 37.544 v0.2.0                                                                                                         | 0.1.0  | 0.2.0  |
+| 2015-02        | RAN5#66 | R5150208  | -    | -   | TS 37.544 v0.3.0                                                                                                         | 0.2.0  | 0.3.0  |
+| 2015-05        | RAN5#67 | R5-151230 | -    | -   | TS 37.544 v0.4.0                                                                                                         | 0.3.0  | 0.4.0  |
+| 2015-08        | RAN5#68 | R5-153129 | -    | -   | TS 37.544 v0.5.0                                                                                                         | 0.4.0  | 0.5.0  |
+| 2015-11        | RAN5#69 | R5-155372 | -    | -   | TS 37.544 v0.6.0                                                                                                         | 0.5.0  | 0.6.0  |
+| 2015-12        | RAN#70  | -         | -    | -   | editorial cleanup by MCC according to 3GPP formatting rules                                                              | 0.6.0  | 0.6.1  |
+| 2016-05        | RAN5#71 | R5-162124 | -    | -   | TS 37.544 v0.7.0                                                                                                         | 0.6.1  | 0.7.0  |
+| 2016-08        | RAN5#72 | R5-162123 | -    | -   | TS 37.544 v1.0.0                                                                                                         | 0.7.0  | 1.0.0  |
+| 2016-09        | RAN#73  | -         | -    | -   | TS 37.544 v2.0.0                                                                                                         | 1.0.0  | 2.0.0  |
+| 2016-09        | RAN#73  | -         | -    | -   | TS 37.544 v2.1.0                                                                                                         | 2.0.0  | 2.1.0  |
+| 2016-09        | RAN#73  | -         | -    | -   | upgraded to v14.0.0 with editorial changes                                                                               | 2.1.0  | 14.0.0 |
+| 2017-03        | RAN#75  | R5-171303 | 0008 | -   | Corrections to Test Requirements                                                                                         | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171908 | 0001 | 1   | Radiated Performance of Multiple-antenna Receivers - Scope                                                               | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171909 | 0002 | 1   | Radiated Performance of Multiple-antenna Receivers - References                                                          | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171910 | 0004 | 1   | Radiated Performance of Multiple-antenna Receivers - DUT Positioning for total radiated multi-antenna sensitivity (TRMS) | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171911 | 0003 | 1   | Radiated Performance of Multiple-antenna Receivers - E-UTRA FDD and TDD frequencies                                      | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171912 | 0005 | 1   | Radiated Performance of Multiple-antenna Receivers - Sampling Grid                                                       | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171913 | 0006 | 1   | Radiated Performance of Multiple-antenna Receivers - Receiver TRMS for E-UTRA FDD & TDD in Free Space                    | 14.0.0 | 14.1.0 |
+| 2017-03        | RAN#75  | R5-171914 | 0007 | 1   | E-UTRA FDD and TDD Frequency Bands                                                                                       | 14.0.0 | 14.1.0 |
+| 2017-06        | RAN#76  | R5-173366 | 0009 | 1   | Introduction of Multi-Probe Anechoic Chamber Specification and Validation Method                                         | 14.1.0 | 14.2.0 |
+| 2017-06        | RAN#76  | R5-173368 | 0010 | 1   | Updated minimum requirements for LTE Tablet and UTRA TRP/TRS                                                             | 14.1.0 | 14.2.0 |
+| 2017-09        | RAN#77  | R5-175048 | 0011 | 1   | Updates to TRMS Minimum Requirements for TC 7.4.1 & 7.4.2                                                                | 14.2.0 | 14.3.0 |
+| 2017-09        | RAN#77  | R5-175049 | 0012 | 1   | Updates on maximum RS-EPRE level                                                                                         | 14.2.0 | 14.3.0 |
+| 2017-09        | RAN#77  | R5-175174 | 0013 | 1   | Calibration procedure for Multi-probe Anechoic chamber (MPAC) method                                                     | 14.2.0 | 14.3.0 |
+| 2017-12        | RAN#78  | R5-177099 | 0017 | 2   | MIMO OTA Maximum uncertainty of test system and test tolerance                                                           | 14.3.0 | 14.4.0 |
+| 2017-12        | RAN#78  | R5-177100 | 0018 | 2   | MIMO OTA TRMS requirements for PS1                                                                                       | 14.3.0 | 14.4.0 |
+| 2017-12        | RAN#78  | R5-177101 | 0023 | 2   | Estimation of measurement uncertainty                                                                                    | 14.3.0 | 14.4.0 |
+| 2017-12        | RAN#78  | R5-177386 | 0015 | 1   | MIMO OTA Definitions, symbols and abbreviations                                                                          | 14.3.0 | 14.4.0 |
+| 2017-12        | RAN#78  | R5-177387 | 0016 | 1   | MIMO OTA Environmental Requirements                                                                                      | 14.3.0 | 14.4.0 |
+| 2018-03        | RAN#79  | R5-180882 | 0025 | -   | Introduction of RTS Anechoic Chamber Specification and Validation Method in TS 37.544                                    | 14.4.0 | 14.5.0 |
+| 2018-03        | RAN#79  | R5-181660 | 0024 | 1   | Addition of Radiated Two-Stage (RTS) in TS 37.544                                                                        | 14.4.0 | 14.5.0 |
+| 2018-03        | RAN#79  | R5-181661 | 0026 | 1   | Addition of UE ATF requirements in TS 37.544                                                                             | 14.4.0 | 14.5.0 |
+| 2018-06        | RAN#80  | R5-183852 | 0028 | 1   | Addition RTS applicability for FDD bands                                                                                 | 14.5.0 | 14.6.0 |
+| 2018-09        | RAN#81  | R5-186894 | 0029 | -   | Update on RTS Linearization                                                                                              | 14.6.0 | 14.7.0 |
+| 2020-06        | SA#88   | -         | -    | -   | Upgraded to Rel-15 with no change                                                                                        | 14.7.0 | 15.0.0 |
+| 2020-06        | SA#88   | -         | -    | -   | Upgraded to Rel-16 with no change                                                                                        | 15.0.0 | 16.0.0 |
+| 2021-03        | RAN#91  | R5-210377 | 0030 | -   | Correction of TRS numeric symbol                                                                                         | 16.0.0 | 16.1.0 |
+| 2021-09        | RAN#93  | R5-215267 | 0031 | -   | Update of D.2                                                                                                            | 16.1.0 | 16.2.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37571-4/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-16/37_series/37571-4/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5182d86840d6ab129349c86533deb44bb47c894f
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:258796c6f181e4762e39bb6b95ae91ebca3b16b9d57ec4a0a8a83fabc341edd4
+size 70403
diff --git a/marked/Rel-16/37_series/37571-4/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/37_series/37571-4/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5b37bd8aa25982beac1ad60cbd530ae956da96f
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77bb16673898574614f73e8d10158ec2d239753043c0d0ce931608cc4d59b455
+size 74807
diff --git a/marked/Rel-16/37_series/37571-4/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/37_series/37571-4/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7788e1958b1bd00618e44e13918d56395886ead
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2106da195f9ab0164b212016f871208ab283a900f0b589d5b77f0a55db52eb87
+size 64004
diff --git a/marked/Rel-16/37_series/37571-4/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37571-4/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8818675c9b47bcc4a12ac084ab4baf3eeee30ffc
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:98a8500da3b643a7a9f56772106324b6a0f9258f8436d7657906ab0c1fec0b67
+size 9531
diff --git a/marked/Rel-16/37_series/37571-4/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37571-4/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdcbd9ef8c9554523fb62963f87aa0e7ff196e56
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c7ff4526ed2625cea8ab755ab5f1c79e9fb59f4c7d6f5894166abf68be67a5f
+size 5790
diff --git a/marked/Rel-16/37_series/37571-4/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-16/37_series/37571-4/65550960f5c5afd9d27706aaeddb0638_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d806b1bb7aeaff1013a4576728585d233ebe4166
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/65550960f5c5afd9d27706aaeddb0638_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94aaf3836a233be703777bd93ece5d48f6f4c6104ea3da5b7bebf31130aa0756
+size 80270
diff --git a/marked/Rel-16/37_series/37571-4/704082cc3e11776bda29595c76411362_img.jpg b/marked/Rel-16/37_series/37571-4/704082cc3e11776bda29595c76411362_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7a68b87822210bb3f9c5208f8a6223e38b6a6e6
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/704082cc3e11776bda29595c76411362_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8a04104fb392de77662136673c15152d7b0d3913c3af6a15861e14e9496eae23
+size 72015
diff --git a/marked/Rel-16/37_series/37571-4/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/37_series/37571-4/7f17c430b9598e4d748a8041457810b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fd4747b50182b57aef79529a127f33591e1c494
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/7f17c430b9598e4d748a8041457810b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e6b08523d5e8739d9b3a4ee323e1acd3ccb5c5663745e490b11d96480566af7
+size 47399
diff --git a/marked/Rel-16/37_series/37571-4/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/37_series/37571-4/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2c0c48b0d3c7ec279bb2fd478cd61ff8b070d6cc
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f894b5abc38473736f863f44c52972306c7f4b5d3c29edd502e61a19e1e8e58f
+size 101619
diff --git a/marked/Rel-16/37_series/37571-4/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/marked/Rel-16/37_series/37571-4/bffdddb47fced140f8d17fdc2a29f592_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..88810fa2efdec5e53ccf8cfe62a330eb767b5125
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/bffdddb47fced140f8d17fdc2a29f592_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6f9a85ca724532103b83a69cf3ddae8c8bdb33afcf276e1b512da9b74bbac7f6
+size 62928
diff --git a/marked/Rel-16/37_series/37571-4/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/37_series/37571-4/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d6022937f39ca368470d7825b6ae6de9e45fef3
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c9e171b65c116d46a1b1327f98b4394191606188852f17d52d8171493be4b34
+size 62991
diff --git a/marked/Rel-16/37_series/37571-4/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/37_series/37571-4/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea79ca3fe862004d7a978604b972b5fc383efb52
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dc6875a43ca8272d1853ac0e8ec11679b4455e7f14e53b686e6c72065e636da
+size 80549
diff --git a/marked/Rel-16/37_series/37571-4/raw.md b/marked/Rel-16/37_series/37571-4/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..46e19752bd530f66338cf89cb299791d79beb0ea
--- /dev/null
+++ b/marked/Rel-16/37_series/37571-4/raw.md
@@ -0,0 +1,1641 @@
+
+
+# 3GPP TS 37.571-4 V16.8.0 (2022-12) ---
+
+*Technical Specification*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) conformance specification for UE positioning; Part 4: Test suites (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. Below the "G" is a red signal wave icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+## --- **Keywords**
+
+PIXIT, positioning, TTCN, UE
+
+## **3GPP**
+
+### --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 5  |
+| Introduction .....                                                         | 5  |
+| 1 Scope.....                                                               | 6  |
+| 2 References.....                                                          | 6  |
+| 3 Definitions, symbols and abbreviations .....                             | 8  |
+| 3.1 Definitions.....                                                       | 8  |
+| 3.2 Symbols.....                                                           | 8  |
+| 3.3 Abbreviations .....                                                    | 8  |
+| 4 A-GPS system architecture and test model.....                            | 8  |
+| 4.1 ATS and module structure.....                                          | 8  |
+| 4.2 Upper tester .....                                                     | 8  |
+| 4.3 SV PCO.....                                                            | 8  |
+| 4.4 A-GPS Primitives.....                                                  | 8  |
+| 4.5 Specific test suite operation for A-GPS testing.....                   | 8  |
+| 5 A-GNSS and LTE positioning system architecture and test models .....     | 9  |
+| 5.1 Test system architecture.....                                          | 9  |
+| 5.1.1 General system architecture.....                                     | 9  |
+| 5.1.2 Component architecture.....                                          | 9  |
+| 5.1.2.1 Interfaces.....                                                    | 10 |
+| 5.2 Test model.....                                                        | 10 |
+| 5.2.1 LTE GNSS test model .....                                            | 11 |
+| 5.2.2 UTRA A-GNSS test model .....                                         | 12 |
+| 5.3 ASP specifications.....                                                | 13 |
+| 5.4 LTE OTDOA test model.....                                              | 13 |
+| 5.5 LTE ECID test model.....                                               | 14 |
+| 6 LTE indoor positioning system architecture and test models .....         | 14 |
+| 6.1 Test system architecture.....                                          | 14 |
+| 6.1.1 General system architecture.....                                     | 14 |
+| 6.1.2 Component architecture.....                                          | 14 |
+| 6.1.2.1 Interfaces.....                                                    | 15 |
+| 6.2 Test model.....                                                        | 15 |
+| 6.2.1 LTE indoor positioning test model.....                               | 15 |
+| 6A LTE test models requiring GNSS support .....                            | 16 |
+| 6B NG-RAN NR positioning system architecture and test models.....          | 16 |
+| 6B.1 Test system architecture.....                                         | 16 |
+| 6B.1.1 General system architecture.....                                    | 16 |
+| 6B.1.2 Component architecture.....                                         | 16 |
+| 6B.2 Test models .....                                                     | 17 |
+| 6B.2.1 NR GNSS positioning test model.....                                 | 17 |
+| 6B.2.2 NR indoor positioning test model.....                               | 18 |
+| 6B.2.3 NR OTDOA (LTE) positioning test model.....                          | 18 |
+| 6B.2.4 NR Multi-RTT, DL-AoD and DL-TDOA positioning test model .....       | 20 |
+| 6B.2.5 NR E-CID test model .....                                           | 20 |
+| 6C NR/5GC test models requiring GNSS support .....                         | 21 |
+| 7 Upper Tester Interface .....                                             | 21 |
+| 7.1 MMI for A-GPS .....                                                    | 21 |
+| 7.2 MMI for A-GNSS, LTE and NR positioning.....                            | 21 |
+| 8 EXIT Proforma.....                                                       | 22 |
+| 8.1 A-GPS test suite parameters declarations .....                         | 22 |
+| 8.2 A-GNSS, LTE and NR positioning test suite parameters declarations..... | 22 |
+
+|                                                                                                 |                                                          |           |
+|-------------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------|
+| 9                                                                                               | Other SS Requirements with TTCN-3 impact .....           | 22        |
+| 9.1                                                                                             | Codec Requirements .....                                 | 22        |
+| <b>Annex A (normative): Test Suites.....</b>                                                    |                                                          | <b>23</b> |
+| A.1                                                                                             | UTRA A-GPS test suite .....                              | 23        |
+| A.1.1                                                                                           | Baseline of specifications.....                          | 23        |
+| A.1.2                                                                                           | AGPS ATS.....                                            | 23        |
+| A.1.3                                                                                           | The TTCN Machine Processable form (TTCN.MP).....         | 24        |
+| A.2                                                                                             | UTRA A-GNSS, LTE and NR/5GC positioning test suite ..... | 24        |
+| A.2.1                                                                                           | Baseline of specifications.....                          | 24        |
+| A.2.2                                                                                           | E-UTRA LTE positioning Test Cases.....                   | 24        |
+| A.2.3                                                                                           | UTRA A-GNSS Test Cases .....                             | 25        |
+| A.2.4                                                                                           | NR/5GC Test Cases .....                                  | 25        |
+| <b>Annex B (informative): ASN.1 modules.....</b>                                                |                                                          | <b>26</b> |
+| B.1                                                                                             | A-GPS ASN.1 module .....                                 | 26        |
+| B.2                                                                                             | A-GNSS ASN.1 modules.....                                | 26        |
+| B.3                                                                                             | LPP ASN.1.....                                           | 26        |
+| <b>Annex C (informative): E-UTRA System Simulator Extension ASP Definitions in TTCN-3 .....</b> |                                                          | <b>27</b> |
+| C.1                                                                                             | EUTRA_POS_ASP_TypeDefs.....                              | 27        |
+| C.1.1                                                                                           | System_Configuration_PosExt .....                        | 27        |
+| C.1.2                                                                                           | Cell_Configuration_PosExt .....                          | 27        |
+| C.1.2.1                                                                                         | Cell_Configuration_Common_PosExt.....                    | 27        |
+| C.1.2.2                                                                                         | Downlink_Physical_Layer_Configuration_PosExt .....       | 28        |
+| C.1.3                                                                                           | System_Interface_PosExt.....                             | 28        |
+| C.2                                                                                             | References to TTCN-3 .....                               | 29        |
+| <b>Annex D (informative) Positioning System Simulator ASP Definitions in TTCN-3.....</b>        |                                                          | <b>30</b> |
+| D.1                                                                                             | PosSystem_ASP_TypeDefs.....                              | 30        |
+| D.1.1                                                                                           | PosSystem_Load_Scenario .....                            | 30        |
+| D.1.2                                                                                           | PosSystem_Retrieve_Data .....                            | 31        |
+| D.1.2.1                                                                                         | SatSystem_Retrieve_UTRAN_Data .....                      | 31        |
+| D.1.2.2                                                                                         | PosSystem_Retrieve_LPP_Data.....                         | 32        |
+| D.1.2.3                                                                                         | PosSystem_Retrieve_Data_Common.....                      | 33        |
+| D.1.3                                                                                           | PosSystem_PowerControl.....                              | 33        |
+| D.1.4                                                                                           | PosSystem_GnssUtcTime .....                              | 34        |
+| D.1.5                                                                                           | System_Interface.....                                    | 34        |
+| D.2                                                                                             | CommonDefs .....                                         | 35        |
+| D.3                                                                                             | References to TTCN-3 .....                               | 36        |
+| <b>Annex E (informative) NR5GC System Simulator Extension ASP Definitions in TTCN-3 .....</b>   |                                                          | <b>36</b> |
+| E.1                                                                                             | NR5GC_POS_ASP_TypeDefs.....                              | 36        |
+| E.1.1                                                                                           | NR_System_Configuration_PosExt.....                      | 36        |
+| E.1.2                                                                                           | NR_Cell_Configuration_PosExt.....                        | 37        |
+| E.1.2.1                                                                                         | NR_Cell_Configuration_Common_PosExt .....                | 37        |
+| E.1.2.2                                                                                         | Downlink_Physical_Layer_Configuration_PosExt .....       | 37        |
+| E.1.3                                                                                           | NR_System_Interface_PosExt.....                          | 39        |
+| E.2                                                                                             | References to TTCN-3 .....                               | 39        |
+| <b>Annex F (informative): Change history .....</b>                                              |                                                          | <b>40</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The present document is part 4 of a multi-part conformance test specification. The specification contains a TTCN design frame work and the detailed test specifications in TTCN for the UE:
+
+- A-GPS at the UTRA Uu interface in TTCN-2;
+- A-GNSS at the UTRA Uu interface in TTCN-3;
+- LTE positioning at the LTE-Uu interface in TTCN-3.
+- NR positioning at the NR-Uu interface in TTCN-3.
+
+The present document is part 4 of a multi-parts TS:
+
+- 3GPP TS 37.571-1: User Equipment (UE) conformance specification for UE positioning; Part 1: Terminal conformance.
+- 3GPP TS 37.571-2: User Equipment (UE) conformance specification for UE positioning; Part 2: Protocol conformance.
+- 3GPP TS 37.571-3: User Equipment (UE) conformance specification for UE positioning; Part 3: Implementation Conformance Statement (ICS).
+- **3GPP TS 37.571-4: User Equipment (UE) conformance specification for UE positioning; Part 4: Test suites.**
+- 3GPP TS 37.571-5: User Equipment (UE) conformance specification for UE positioning; Part 5: Test scenarios and assistance data.
+
+# --- 1 Scope
+
+The present document specifies the protocol and signalling conformance testing in TTCN for the UE:
+
+- A-GPS at the UTRA Uu interface;
+- LTE positioning at the LTE-Uu interface;
+- A-GNSS at the UTRA Uu interface.
+- NR positioning at the NR-Uu interface.
+
+The following TTCN test specification and design considerations can be found in the present document:
+
+- Test system architecture;
+- Test models and ASP definitions;
+- Test methods and usage of communication ports definitions;
+- Test configurations;
+- Design principles and assumptions;
+- TTCN styles and conventions;
+- Partial PIXIT proforma;
+- Test suites in TTCN-2 and TTCN-3;
+- The Test Suites designed and implemented in the present document are based on the test specifications in prose in 3GPP TS 37.571-2 [3];
+- The applicability of the individual test cases is specified in the test ICS proforma specification in 3GPP TS 37.571-3 [4].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document unless the context in which the reference is made suggests a different Release is relevant (information on the applicable release in a particular context can be found in e.g. test case title, description or applicability, message description or content).
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 37.571-1: " User Equipment (UE) conformance specification for UE positioning; Part 1: Conformance test specification".
+- [3] 3GPP TS 37.571-2: " User Equipment (UE) conformance specification for UE positioning; Part 2: Protocol conformance".
+- [4] 3GPP TS 37.571-3: " User Equipment (UE) conformance specification for UE positioning; Part 3: Implementation Conformance Statement (ICS)".
+
+- [5] 3GPP TS 37.571-5: " User Equipment (UE) conformance specification for UE positioning; Part 5: Test scenarios and assistance data".
+- [6] 3GPP TS 36.523-3: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); User Equipment (UE) conformance specification; Part 3: Test suites".
+- [7] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing".
+- [8] 3GPP TS 34.123-3: "User Equipment (UE) conformance specification; Part 3: Abstract test suite (ATS)".
+- [9] 3GPP TS 34.108: "Common test environments for User Equipment (UE); Conformance testing".
+- [10] 3GPP TS 37.355: " LTE Positioning Protocol (LPP)".
+- [11] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
+- [12] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
+- [13] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats and coding".
+- [14] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
+- [15] ITU-T Recommendation X.880: "Information technology - Remote Operations: Concepts, model and notation".
+- [16] ITU-T Recommendation Q.773: "Transaction capabilities formats and encoding".
+- [17] ETSI ES 201 873-1: "Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language".
+- [18] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
+- [19] 3GPP TS 23.038: "Alphabets and language-specific information".
+- [20] ETSI TR 101 666 (V1.0.0): "Information technology; Open Systems Interconnection Conformance testing methodology and framework; The Tree and Tabular Combined Notation (TTCN) (Ed. 2++)".
+- [21] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
+- [22] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
+- [23] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation".
+- [24] 3GPP TS 38.523-3: "5GS; User Equipment (UE) conformance specification; Part 3: Protocol Test Suites".
+- [25] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
+- [26] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
+- [27] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
+- [28] 3GPP TS 38.508-1: "5GS; User Equipment (UE) conformance specification; Part 1: Common test environment".
+- [29] 3GPP TS 38.211: "NR; Physical channels and modulation".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] apply.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] apply.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply:
+
+|     |                            |
+|-----|----------------------------|
+| ASP | Abstract Service Primitive |
+|-----|----------------------------|
+
+# --- 4 A-GPS system architecture and test model
+
+A-GPS signalling conformance tests are specified in TTCN-2. The system architecture and the test model are based on 3GPP TS 34.123-3 [8].
+
+## 4.1 ATS and module structure
+
+Refer to 3GPP TS 34.123-3 [8], clause 5.
+
+## 4.2 Upper tester
+
+Refer to 3GPP TS 34.123-3 [8], clause 7.3.5.1.
+
+## 4.3 SV PCO
+
+Refer to 3GPP TS 34.123-3 [8], clause 7.3.5.2.
+
+## 4.4 A-GPS Primitives
+
+Refer to 3GPP TS 34.123-3[8], clause 7.3.5.3.
+
+## 4.5 Specific test suite operation for A-GPS testing
+
+Refer to 3GPP TS 34.123-3 [8], clause 8.7.7.
+
+# 5 A-GNSS and LTE positioning system architecture and test models
+
+## 5.1 Test system architecture
+
+### 5.1.1 General system architecture
+
+Refer to 3GPP TS 36.523-3 [6], clause 4.1.1.
+
+### 5.1.2 Component architecture
+
+Each access technology (RAT) is hosted by a separate TTCN-3 parallel component (PTC):
+
+- E-UTRA PTC;
+- UTRA PTC.
+
+The PTCs are controlled by the TTCN-3 positioning master test component (POS MTC) which:
+
+- Is an extension of the MTC as defined in 3GPP TS 36.523-3 [6], clause 4.1.2.
+- Controls the SS Positioning Simulator.
+
+Figure 5.1.2-1 shows this component architecture for an E-UTRA and UTRA scenario.
+
+![Figure 5.1.2-1: Component architecture for an E-UTRA and UTRA scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 test environment, a Positioning Simulator, a System Simulator, and a User Equipment (UE).](65550960f5c5afd9d27706aaeddb0638_img.jpg)
+
+The diagram illustrates the component architecture for an E-UTRA and UTRA scenario. At the top, an **Upper Tester** (blue box) sends **AT/MMI commands** (dashed arrow) to a **UE** (green box) on the right. The **Upper Tester** is connected to a **TTCN-3** test environment (white box). Inside the **TTCN-3** box, the **POS MTC** (Synchronisation, Upper tester control, POS port control) is connected to the **Upper Tester** and to the **POS Port** of the **Positioning Simulator** (blue box) at the bottom. The **POS MTC** also sends **Coordination messages** (purple arrows) to the **EUTRA PTC** (LTE positioning TTCN) and the **UTRA PTC** (A-GNSS TTCN). The **EUTRA PTC** and **UTRA PTC** are connected to the **System Simulator** (blue box) at the bottom. The **System Simulator** is connected to the **Positioning Simulator** via a **Radio Interface** (solid line). The **Positioning Simulator** is connected to the **UE** via a **Satellite Signal** (solid line). The **UE** is also connected to the **System Simulator** via a **Radio Interface** (solid line).
+
+Figure 5.1.2-1: Component architecture for an E-UTRA and UTRA scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 test environment, a Positioning Simulator, a System Simulator, and a User Equipment (UE).
+
+Figure 5.1.2-1: Component architecture for an E-UTRA and UTRA scenario
+
+The PTCs are allocated according to the following principles:
+
+- For LTE positioning tests cases, the E-UTRA PTC is created.
+- For LTE positioning CS fallback test cases, E-UTRA and UTRA PTCs are created.
+- For UTRA A-GNSS test cases, the UTRA PTC is created.
+
+#### 5.1.2.1 Interfaces
+
+A number of interfaces are taken into consideration.
+
+##### **POS MTC - PTC:**
+
+Common synchronisation of PTCs.
+
+Positioning simulator command/data coordination messages.
+
+Upper tester primitives.
+
+##### **POS MTC - System Interface:**
+
+Upper tester primitives.
+
+##### **POS MTC- Positioning Simulator:**
+
+Positioning simulator command and data primitives.
+
+##### **PTC - PTC:**
+
+Primitives containing information for IRAT handover.
+
+##### **PTC - System Interface:**
+
+Primitives containing peer-to-peer message.
+
+Configuration primitives.
+
+## 5.2 Test model
+
+In order to perform the LTE positioning and A-GNSS tests, the Positioning Simulator shall have two basic functional unites:
+
+- Satellite simulator generating and broadcasting satellite signals.
+- Assistance data source storing the data associated with the pre-defined GPS and GNSS test scenarios (see 3GPP TS 37.571-5 [5]).
+
+This specification supports the following GNSS: GPS, Galileo, GLONASS and BDS.
+
+### 5.2.1 LTE GNSS test model
+
+![Figure 5.2.1-1: E-UTRA Test model for LTE positioning GNSS testing. The diagram shows a 'TTN CODE' block containing 'POS MTC' and 'E-UTRA MTC'. 'POS MTC' connects via a 'POS Port' to a 'Positioning Simulator'. 'E-UTRA MTC' connects via 'DRB', 'SRB2-SRB0', and 'Config/Control' to an 'RRC/NAS Emulator'. The 'RRC/NAS Emulator' is part of a protocol stack: 'Integrity/Ciphering' (PDGP), 'PDGP', 'RLC [AM/UM/TM]', 'MAC', and 'PHY'. The 'Positioning Simulator' and the 'PHY' layer both connect to a 'UE' block at the bottom.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Figure 5.2.1-1: E-UTRA Test model for LTE positioning GNSS testing. The diagram shows a 'TTN CODE' block containing 'POS MTC' and 'E-UTRA MTC'. 'POS MTC' connects via a 'POS Port' to a 'Positioning Simulator'. 'E-UTRA MTC' connects via 'DRB', 'SRB2-SRB0', and 'Config/Control' to an 'RRC/NAS Emulator'. The 'RRC/NAS Emulator' is part of a protocol stack: 'Integrity/Ciphering' (PDGP), 'PDGP', 'RLC [AM/UM/TM]', 'MAC', and 'PHY'. The 'Positioning Simulator' and the 'PHY' layer both connect to a 'UE' block at the bottom.
+
+**Figure 5.2.1-1: E-UTRA Test model for LTE positioning GNSS testing**
+
+The LTE positioning test model consists of an SS E-UTRAN protocol stack and a positioning simulator. The SS E-UTRA emulation part is the same as the model defined in 3GPP TS 36.523-3 [6].
+
+The UE is configured in normal mode. On UE side Ciphering/Integrity (PDGP and NAS) is enabled. The tests are performed on C-Plane.
+
+The ASPs at POS Port are used to:
+
+- Load a pre-defined test scenario into the positioning simulator.
+- Start or stop generating and broadcasting satellite signals from the positioning simulator.
+- Retrieve the GNSS assistance data from assistance data source.
+
+Under the ASP commands, the upper tester loads or re-loads pre-defined GNSS test scenario to the positioning simulator. The generated satellite signals shall simulate the GNSS environment as specified in 3GPP TS 37.571-2 [3], clause 5.
+
+The SS also sends the GNSS assistance data to the UE through LPP signalling (see 3GPP TS 37.355 [10]) to facilitate the UE acquiring and tracking satellites. Such assistance data shall be consistent to within  $\pm 2$  seconds with the satellite signals generated (see 3GPP TS 37.571-2 [3], clause 5.2.1).
+
+The assistance data source shall provide the assistance data consistent to  $+1/-0$  second with the GNSS test scenario currently running in the satellite simulator (i.e. the data shall be up to 1 second in advance of the scenario); this allows for a further 2 seconds of latency in the SS. In case multiple satellite systems are configured in a test, the assistance data are requested or retrieved in a single ASP command for all satellite systems.
+
+The UE positioning services are encoded in a TCAP [16] ROSE component [15] of the facility information element [14] in the Supplement Service [13] conveyed in the NAS messages. The facility information element is encoded in BER in TTCN referred to 3GPP TS 24.080 [13], clause 3.6.1 and 3GPP TS 29.002 [14], clause 17.1.1.
+
+### 5.2.2 UTRA A-GNSS test model
+
+![Figure 5.2.2-1: UTRA Test model for A-GNSS testing. The diagram shows a 'TTCN CODE' block at the top containing 'POS MTC' (with 'POS Port') and 'UTRAN PTC' (with 'Config/Control', 'RAB', and 'SRB0-SRB4'). Below this is a 'Positioning Simulator' (blue box) connected to a 'UE' (white box) at the bottom. The simulator is connected to a protocol stack consisting of 'RLC [AM/UM/TM]' (yellow), 'MAC' (light blue), and 'PHY' (green). The RLC layer includes 'Ciphering' and 'RRC (Integrity) Emulator & Direct transfer'. The MAC layer also includes 'Ciphering'. Arrows indicate data flow from the TTCN CODE through the simulator and down the protocol stack to the UE, and back up the stack.](7f17c430b9598e4d748a8041457810b3_img.jpg)
+
+Figure 5.2.2-1: UTRA Test model for A-GNSS testing. The diagram shows a 'TTCN CODE' block at the top containing 'POS MTC' (with 'POS Port') and 'UTRAN PTC' (with 'Config/Control', 'RAB', and 'SRB0-SRB4'). Below this is a 'Positioning Simulator' (blue box) connected to a 'UE' (white box) at the bottom. The simulator is connected to a protocol stack consisting of 'RLC [AM/UM/TM]' (yellow), 'MAC' (light blue), and 'PHY' (green). The RLC layer includes 'Ciphering' and 'RRC (Integrity) Emulator & Direct transfer'. The MAC layer also includes 'Ciphering'. Arrows indicate data flow from the TTCN CODE through the simulator and down the protocol stack to the UE, and back up the stack.
+
+Figure 5.2.2-1: UTRA Test model for A-GNSS testing
+
+The A-GNSS test model consists of an SS UTRAN protocol stack and a positioning simulator. The SS UTRA emulation part is the same as the model defined in 3GPP TS 36.523-3 [6], clause 4.4.1.
+
+The UE is configured in normal mode. Ciphering and Integrity (RRC) are enabled. The tests are performed on C-Plane.
+
+The ASPs at POS Port are used to:
+
+- Load a pre-defined test scenario into the positioning simulator.
+- Start or stop generating and broadcasting satellite signals from the positioning simulator.
+- Retrieve the GPS and GNSS assistance data from assistance data source.
+
+Under the ASP commands, the upper tester loads or re-loads pre-defined GPS or GNSS test scenario to the positioning simulator. The generated satellite signals shall simulate the A-GPS and A-GNSS environment as specified in 3GPP TS 37.571-2 [3], clause 4.2.
+
+The SS also sends the GPS or GNSS assistance data to the UE through RRC signalling to facilitate the UE acquiring and tracking satellites. Such assistance data shall be consistent to within  $\pm 2$  seconds with the satellite signals generated (see 3GPP TS 37.571-2 [3], clause 4.2).
+
+The assistance data source shall provide the assistance data consistent to  $+1/-0$  second with the GPS or GNSS test scenario currently running in the satellite simulator (i.e. the data shall be up to 1 second in advance of the scenario); this allows for a further 2 seconds of latency in the SS. In case multiple satellite systems are configured in a test, the assistance data are requested or retrieved in a single ASP command for all satellite systems.
+
+The UE positioning services are encoded in a TCAP [16] ROSE component [15] of the facility information element [14] in the Supplement Service [13] conveyed in the NAS messages. The facility information element is encoded in BER in TTCN referred to 3GPP TS 24.080 [13], clause 3.6.1 and 3GPP TS 29.002 [14], clause 17.1.1.
+
+## 5.3 ASP specifications
+
+The E-UTRAN and UTRAN ASP definitions are specified according to 3GPP TS 36.523-3 [6], clause 6.
+
+The positioning simulator ASP definitions are documented in annex C.
+
+## 5.4 LTE OTDOA test model
+
+![Figure 5.4-1: E-UTRA OTDOA test model diagram showing the protocol stack and TTCN CODE interface.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg)
+
+The diagram illustrates the E-UTRA OTDOA test model. At the top, a dashed box labeled 'TTCN CODE' contains a block labeled 'E-UTRA PTC'. This block has four sub-components: 'DRB', 'SRB2-SRB0', 'Config/Control', and 'Extension Config/Control'. Below the 'E-UTRA PTC' block is a protocol stack consisting of several layers: 'RRC/NAS Emulator' (a small box above the main stack), 'PDCP' (purple box containing 'Integrity' and 'Ciphering' sub-components), 'RLC [AM/UM/TM]' (yellow box), 'MAC' (light blue box), and 'PHY' (green box). At the bottom is a box labeled 'UE'. Vertical double-headed arrows connect the 'UE' box to the 'PHY' layer, and the 'PHY' layer to the 'PDCP' layer. Dashed lines connect the 'Config/Control' and 'Extension Config/Control' components of the 'E-UTRA PTC' block to the 'PDCP', 'RLC', 'MAC', and 'PHY' layers respectively. Solid lines connect the 'DRB' and 'SRB2-SRB0' components of the 'E-UTRA PTC' block to the 'RRC/NAS Emulator' box.
+
+Figure 5.4-1: E-UTRA OTDOA test model diagram showing the protocol stack and TTCN CODE interface.
+
+Figure 5.4-1: E-UTRA OTDOA test model
+
+The LTE OTDOA test model consists of an SS E-UTRAN protocol stack. The SS E-UTRA emulation part is the same as the model defined in 3GPP TS 36.523-3 [6] with an additional port to configure the antenna port 6 and the Positioning Reference Signal (PRS) in the LTE cells. The extension of LTE ASPs is defined in annex C.
+
+The simulated OTDOA environment is specified in 3GPP TS 37.571-2 [3], clause 5.2.2), cells are synchronous and configured with the timing offset set to 0. The PRS is transmitted according to 3GPP TS 36.211 [23], clause 6.10.4.
+
+The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled. The tests are performed on C-Plane.
+
+The PRS signals are transmitted by the SS E-UTRAN, the assistance data are written in TTCN.
+
+## 5.5 LTE ECID test model
+
+The test model is referred to the LTE positioning test model defined in clause 5.2.1; except that no satellite signals are required.
+
+# 6 LTE indoor positioning system architecture and test models
+
+## 6.1 Test system architecture
+
+### 6.1.1 General system architecture
+
+Refer to 3GPP TS 36.523-3 [6], clause 4.1.1.
+
+### 6.1.2 Component architecture
+
+The same architecture as in 5.1.2 applies, excluding the UTRA PTC.
+
+![Diagram of component architecture for an E-UTRA scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 test environment (containing POS MTC and EUTRA PTC), an Indoor Positioning Simulator, a System Simulator, and a User Equipment (UE).](704082cc3e11776bda29595c76411362_img.jpg)
+
+The diagram illustrates the component architecture for an E-UTRA scenario. At the top, an **Upper Tester** (blue box) is connected to a **TTCN-3** environment (white box). The Upper Tester sends **AT/MMI commands** (dashed arrow) to the UE. The TTCN-3 environment contains two main components: **POS MTC** (Synchronisation, Upper tester control, POS port control) and **EUTRA PTC** (LTE positioning TTCN). These two components exchange **Coordination messages** (purple double-headed arrow). The POS MTC is connected to the **Indoor Positioning Simulator** (blue box) via a **POS Port**. The EUTRA PTC is connected to the **System Simulator** (blue box) via **E-UTRA Control Ports** and **E-UTRA Ports**. The Indoor Positioning Simulator and the System Simulator are connected to the **UE** (green box) via a **Radio Interface**. The System Simulator sends a **Positioning Signal** (solid arrow) to the UE.
+
+Diagram of component architecture for an E-UTRA scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 test environment (containing POS MTC and EUTRA PTC), an Indoor Positioning Simulator, a System Simulator, and a User Equipment (UE).
+
+Figure 6.1.2-1: Component architecture for an E-UTRA scenario
+
+#### 6.1.2.1 Interfaces
+
+Refer to 5.1.2.1.
+
+## 6.2 Test model
+
+### 6.2.1 LTE indoor positioning test model
+
+![Figure 6.2.1-1: E-UTRA Test model for LTE indoor positioning testing. The diagram shows a protocol stack for the User Equipment (UE) and an Indoor Positioning Simulator. The UE stack includes PHY, MAC, RLC [AM/UM/TM], PDCP (with Integrity and Ciphering), and RRC/NAS Emulator. The Indoor Positioning Simulator is connected to the RRC/NAS Emulator via a POS Port. Above the UE stack, a dashed box labeled 'TTCN CODE' contains 'POS MTC' and 'E-UTRA MTC' (with DRB, SRB2-SRB0, and ConfigControl) components, which are connected to the RRC/NAS Emulator.](bffdddb47fced140f8d17fdc2a29f592_img.jpg)
+
+Figure 6.2.1-1: E-UTRA Test model for LTE indoor positioning testing. The diagram shows a protocol stack for the User Equipment (UE) and an Indoor Positioning Simulator. The UE stack includes PHY, MAC, RLC [AM/UM/TM], PDCP (with Integrity and Ciphering), and RRC/NAS Emulator. The Indoor Positioning Simulator is connected to the RRC/NAS Emulator via a POS Port. Above the UE stack, a dashed box labeled 'TTCN CODE' contains 'POS MTC' and 'E-UTRA MTC' (with DRB, SRB2-SRB0, and ConfigControl) components, which are connected to the RRC/NAS Emulator.
+
+**Figure 6.2.1-1: E-UTRA Test model for LTE indoor positioning testing**
+
+The LTE Indoor Positioning test model consists of an SS E-UTRAN protocol stack and an Indoor Positioning simulator. Depending on the Indoor Positioning Technology to be tested, the Indoor Positioning simulator will generate:
+
+- MBS beacon signals, for MBS test cases;
+- WLAN signals, for WLAN test cases;
+- Bluetooth signals, for Bluetooth test cases.
+- The Indoor Positioning simulator will be switched off for Sensor test cases.
+
+The SS E-UTRA emulation part is the same as the model defined in 3GPP TS 36.523-3 [6].
+
+The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled. The tests are performed on C-Plane.
+
+The ASPs at POS Port are used to:
+
+- Load a pre-defined test scenario into the Indoor Positioning simulator.
+- Start or stop generating and broadcasting signals from the Indoor Positioning simulator.
+
+- Retrieve the appropriate (MBS, WLAN, Sensor) assistance data from the assistance data source.
+
+Under the ASP commands, the upper tester loads or re-loads pre-defined test scenario to the Indoor Positioning simulator. The generated signals shall simulate the corresponding Indoor Positioning environment as specified in 3GPP TS 37.571-2 [3], clause 5.
+
+The SS also sends the appropriate assistance data to the UE through LPP signalling (see 3GPP TS 37.355 [10]) to facilitate the UE acquisition of MBS Beacons or WLAN APs. For UE-based tests, the SS also sends the appropriate assistance data to enable the UE to calculate its position for MBS or WLAN tests, or calculate altitude based on barometric pressure sensor measurements.
+
+The UE positioning services are encoded in a TCAP [16] ROSE component [15] of the facility information element [14] in the Supplement Service [13] conveyed in the NAS messages. The facility information element is encoded in BER in TTCN referred to 3GPP TS 24.080 [13], clause 3.6.1 and 3GPP TS 29.002 [14], clause 17.1.1.
+
+# --- 6A LTE test models requiring GNSS support
+
+Several LTE test models specified in TS 36.523-3 [6] require the presence of a GNSS emulation. Those are:
+
+- V2X services: refer to TS 36.523-3 [6] clause 4.2.11
+- Aerial UE: refer to TS 36.523-3 [6] clause 4.2.12
+
+The positioning simulator shall be capable of generating and broadcasting the following GNSS: GPS, Galileo, GLONASS and BDS.
+
+The ASPs at POS Port for the both test models are used to:
+
+- Load a pre-defined test scenario into the positioning simulator.
+- Start or stop generating and broadcasting satellite signals from the positioning simulator.
+
+The ASPs at POS Port for V2X services are additionally used to:
+
+- Trigger the positioning simulator to move in the test scenario to the next geographical area or zone.
+- Trigger the positioning simulator to switch on/off the transmitter without stopping the UTC time sequence.
+
+The ASPs at POS Port for aerial UE communication are additionally used to:
+
+- Set an initial altitude above the sea level. Geographical latitude and longitude are defined in the test scenario and remain constant during the test execution.
+- Trigger the positioning simulator to simulate a vertical movement in the test scenario towards a specified altitude level.
+
+# --- 6B NG-RAN NR positioning system architecture and test models
+
+## 6B.1 Test system architecture
+
+### 6B.1.1 General system architecture
+
+Refer to 3GPP TS 36.523-3 [6], clause 4.1.1.
+
+### 6B.1.2 Component architecture
+
+The NR PTC is controlled by the TTCN-3 positioning master test component (POS MTC) which:
+
+- Is an extension of the MTC as defined in 3GPP TS 38.523-3 [24], clause 4.2.
+- Controls the SS Positioning Simulator.
+
+![Figure 6B.1.2-1: Component architecture for a NR scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 framework (containing POS MTC, NR PTC, and EUTRA OTDOA PTC), a Positioning Simulator (Indoor & GNSS), a System Simulator, and a UE. The Upper Tester sends AT/MMI commands to the UE and controls the POS MTC. The POS MTC sends coordination messages to the NR PTC and EUTRA OTDOA PTC. The Positioning Simulator connects to the System Simulator via a POS Port. The System Simulator connects to the UE via a Radio Interface. The UE also receives a Satellite Signal from the Positioning Simulator.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg)
+
+The diagram illustrates the component architecture for a NR scenario. At the top, an **Upper Tester** block is connected to a **TTCN-3** framework. The Upper Tester sends **AT/MMI commands** to the **UE** (User Equipment) via a dashed line. Inside the TTCN-3 framework, there are three main components: **POS MTC** (Synchronisation, Upper tester control, POS port control), **NR PTC**, and **EUTRA OTDOA PTC** (only for OTDOA Test cases). The POS MTC sends **Coordination messages** to the NR PTC and EUTRA OTDOA PTC. Below the TTCN-3 framework, there is a **Positioning Simulator (Indoor & GNSS)** and a **System Simulator**. The POS MTC connects to the Positioning Simulator via a **POS Port**. The NR PTC connects to the System Simulator via **NR Control Ports** and **NR Ports**. The EUTRA OTDOA PTC connects to the System Simulator via **E-UTRA Ports** and **E-UTRA Control Ports** (including config of Antenna port 6 and PRS). The System Simulator connects to the **UE** via a **Radio Interface**. The Positioning Simulator also connects to the **UE** via a **Satellite Signal**.
+
+Figure 6B.1.2-1: Component architecture for a NR scenario. The diagram shows the interaction between an Upper Tester, a TTCN-3 framework (containing POS MTC, NR PTC, and EUTRA OTDOA PTC), a Positioning Simulator (Indoor & GNSS), a System Simulator, and a UE. The Upper Tester sends AT/MMI commands to the UE and controls the POS MTC. The POS MTC sends coordination messages to the NR PTC and EUTRA OTDOA PTC. The Positioning Simulator connects to the System Simulator via a POS Port. The System Simulator connects to the UE via a Radio Interface. The UE also receives a Satellite Signal from the Positioning Simulator.
+
+**Figure 6B.1.2-1: Component architecture for a NR scenario**
+
+As specified in TS 37.571-2 [2], subclause 8.2.8:
+
+- The connection between the Position Simulator and the UE (Satellite signal) shall be conducted.
+- The connection between the System Simulator and the UE (Radio Interface) shall be conducted for NR FR1 and radiated (OTA) for NR FR2.
+
+## 6B.2 Test models
+
+### 6B.2.1 NR GNSS positioning test model
+
+The NR positioning test model consists of an SS NR protocol stack and a positioning simulator. The SS NR/5GC emulation part is the same as the model defined in 3GPP TS 38.523-3 [24]. The positioning simulator is the same as for LTE positioning test model defined in clause 5.2.1.
+
+![Figure 6B.2.1-1: Test model for NR GNSS positioning testing. The diagram shows a 'POS MTC' block with a 'POS Port' connected to a 'Positioning Simulator'. The 'Positioning Simulator' is connected to a 'UE' block. Above the 'UE' is a protocol stack: 'PHY' (green), 'MAC' (light blue), 'RLC [AM/UM/TM]' (yellow), 'PDCP' (purple) with 'Integrity' and 'Ciphering' sub-layers, 'SDAP' (grey), and 'NR PTC' (grey) with 'QoS Flow(s)', 'SRB2-SRB0', and 'Config/Control' sub-layers. A dashed box labeled 'TTCN CODE' encloses the 'POS MTC' and 'NR PTC' blocks. A 'RRC/NAS Emulator' (green) is connected to the 'NR PTC' and has dashed lines to the 'SDAP', 'PDCP', 'RLC', 'MAC', and 'PHY' layers.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+Figure 6B.2.1-1: Test model for NR GNSS positioning testing. The diagram shows a 'POS MTC' block with a 'POS Port' connected to a 'Positioning Simulator'. The 'Positioning Simulator' is connected to a 'UE' block. Above the 'UE' is a protocol stack: 'PHY' (green), 'MAC' (light blue), 'RLC [AM/UM/TM]' (yellow), 'PDCP' (purple) with 'Integrity' and 'Ciphering' sub-layers, 'SDAP' (grey), and 'NR PTC' (grey) with 'QoS Flow(s)', 'SRB2-SRB0', and 'Config/Control' sub-layers. A dashed box labeled 'TTCN CODE' encloses the 'POS MTC' and 'NR PTC' blocks. A 'RRC/NAS Emulator' (green) is connected to the 'NR PTC' and has dashed lines to the 'SDAP', 'PDCP', 'RLC', 'MAC', and 'PHY' layers.
+
+Figure 6B.2.1-1: Test model for NR GNSS positioning testing
+
+### 6B.2.2 NR indoor positioning test model
+
+The NR indoor positioning test model is the same as the NR positioning test model in clause 6B.2.1 but replacing the Positioning simulator with an Indoor Positioning simulator. The same principles as in clause 6.2.1 apply but replacing LTE with NR.
+
+### 6B.2.3 NR OTDOA (LTE) positioning test model
+
+OTDOA measurements are not supported on NR cells in Rel-15. The OTDOA measurements are provided by LTE cells instead. The UE will be attached to an NR cell and the LPP session will be established over NR/5GC NAS. The UE will report OTDOA RSTD measurements from LTE neighbour cells.
+
+The NR OTDOA (LTE) positioning model consists of an SS NR/5GC protocol stack and a SS E-UTRAN protocol stack. The SS NR/5GC emulation part is the same as the model defined in 3GPP TS 38.523-3 [34]. The SS E-UTRAN emulation part is the same as the model defined in clause 5.4 (i.e. including an additional port to configure the antenna port 6 and the Positioning Reference Signal (PRS) in the LTE cells). The E-UTRA PTC will not be connected to NASEMU or IMS/IP PTCs.
+
+![Diagram of the test model for NR OTDOA (LTE) positioning testing. It shows two protocol stacks, NR PTC and E-UTRA PTC, enclosed in a dashed box labeled 'TTCN CODE'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+The diagram illustrates the test model for NR OTDOA (LTE) positioning testing. It features two main protocol stacks, NR PTC and E-UTRA PTC, enclosed within a dashed box labeled 'TTCN CODE'.
+
+- NR PTC Stack:** At the top, it contains 'QoS Flow(s)', 'SRB2-SRB0', and 'Config/Control'. Below this, an 'SDAP' layer is present. An 'RRC/NAS Emulator' block is connected to the SDAP layer. The main stack consists of 'PDCP' (with 'Integrity' and 'Ciphering' sub-layers), 'RLC [AM/UM/TM]', 'MAC', and 'PHY'.
+- E-UTRA PTC Stack:** At the top, it contains 'DRB', 'SRB2-SRB0', 'Config/Control', and 'Extension Config/Control'. The main stack below it consists of 'PDCP' (with 'Integrity' and 'Ciphering' sub-layers), 'RLC [AM/UM/TM]', 'MAC', and 'PHY'.
+- Connections:** A double-headed arrow connects the NR PTC and E-UTRA PTC blocks. At the bottom, a 'UE' block is connected to both the NR and E-UTRA PHY layers via double-headed arrows. Dashed lines indicate various interfaces and control points between the layers and the PTC components.
+
+Diagram of the test model for NR OTDOA (LTE) positioning testing. It shows two protocol stacks, NR PTC and E-UTRA PTC, enclosed in a dashed box labeled 'TTCN CODE'.
+
+Figure 6B.2.3-1: Test model for NR OTDOA (LTE) positioning testing
+
+### 6B.2.4 NR Multi-RTT, DL-AoD and DL-TDOA positioning test model
+
+![Diagram of the NR Multi-RTT, DL-AoD and DL-TDOA positioning test model. The diagram shows a protocol stack for the User Equipment (UE) and a Test Station (SS). The UE stack consists of PHY (green), MAC (light blue), RLC [AM/UM/TM] (yellow), PDCP (purple) with Integrity and Ciphering, and SDAP (grey). Above the UE stack is an RRC/NAS Emulator (teal). The SS stack, labeled 'TTCN CODE', contains NR PTC (grey) with QoS Flow(s), SRB2-SRB0, Config/Control, and Extension Config/Control. Connections are shown between the UE and the RRC/NAS Emulator, and between the RRC/NAS Emulator and the NR PTC. Dashed lines indicate control and data paths between the SS and the UE layers.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+Diagram of the NR Multi-RTT, DL-AoD and DL-TDOA positioning test model. The diagram shows a protocol stack for the User Equipment (UE) and a Test Station (SS). The UE stack consists of PHY (green), MAC (light blue), RLC [AM/UM/TM] (yellow), PDCP (purple) with Integrity and Ciphering, and SDAP (grey). Above the UE stack is an RRC/NAS Emulator (teal). The SS stack, labeled 'TTCN CODE', contains NR PTC (grey) with QoS Flow(s), SRB2-SRB0, Config/Control, and Extension Config/Control. Connections are shown between the UE and the RRC/NAS Emulator, and between the RRC/NAS Emulator and the NR PTC. Dashed lines indicate control and data paths between the SS and the UE layers.
+
+Figure 6B.2.4-1: NR Multi-RTT, DL-AoD and DL-TDOA test model
+
+The NR Multi-RTT, DL-AoD and DL-TDOA test model is the same as the NR/5GC Layer 3 test model (TS 38.523-3 [24], clause 5.2.1.1) with an additional port to configure the DL Positioning Reference Signal (DL-PRS) in the NR cells. The extension of NR ASPs is defined in annex X [TBD].
+
+The simulated NR Multi-RTT, DL-AoD and DL-TDOA environments are specified in TS 37.571-2 [3], clauses 8.2.9, 8.2.10 and 8.2.11, respectively. The DL-PRS is transmitted according to TS 38.211 [29], clause 7.4.1.7.
+
+The UE is configured in normal mode. On UE side Ciphering/Integrity (PDCP and NAS) is enabled. The tests are performed on C-Plane.
+
+The DL-PRS is transmitted by the physical layer of the NR cell(s) in the SS. The assistance data to provide the UE with the configuration of the DL-PRS is sent from the SS to the UE via LPP signalling.
+
+For Multi-RTT, the SS will be also configured through the NR\_SYS port to receive UL-SRS from the UE.
+
+### 6B.2.5 NR E-CID test model
+
+The test model is the same as the NR/5GC Layer 3 test model (TS 38.523-3 [24], clause 5.2.1.1).
+
+# 6C NR/5GC test models requiring GNSS support
+
+The NR sidelink test model specified in TS 38.523-3 [24] clause 5.2.1.6 requires the presence of a GNSS emulation.
+
+The positioning simulator shall be capable of generating and broadcasting the following GNSS: GPS, Galileo, GLONASS and BDS.
+
+The ASPs at POS Port for NR sidelink are used to:
+
+- Load a pre-defined test scenario into the positioning simulator.
+- Start or stop generating and broadcasting satellite signals from the positioning simulator.
+- Trigger the positioning simulator to move in the test scenario to the next geographical area or zone.
+- Trigger the positioning simulator to switch on/off the transmitter without stopping the UTC time sequence.
+- Retrieve the current UTC time of the GNSS scenario.
+
+# 7 Upper Tester Interface
+
+## 7.1 MMI for A-GPS
+
+Refer to 3GPP TS 34.123-3 [8], clause B.1.12.
+
+## 7.2 MMI for A-GNSS, LTE and NR positioning
+
+Refer to 3GPP TS 36.523-3 [6], clause 5.
+
+The following MMI commands are defined for A-GNSS, LTE and NR positioning.
+
+**Table 7.2-1: MMI commands**
+
+| Command            | Parameters |       |
+|--------------------|------------|-------|
+|                    | Name       | Value |
+| "CHECK LCS CLIENT" |            | none  |
+| "LOCATION INFO"    |            | none  |
+
+**Table 7.2-2: MMI commands imported from 3GPP TS 36.523-3 [6], clause 5**
+
+| Command                        |
+|--------------------------------|
+| "SWITCH_ON"                    |
+| "SWITCH_OFF"                   |
+| "POWER_ON"                     |
+| "POWER_OFF"                    |
+| "CHECK_DTCH_THROUGHCONNECTED"  |
+| "CLEAR_STORED_ASSISTANCE_DATA" |
+
+The following AT commands are applied in TTCN.
+
+**Table 7.2-3: AT Commands**
+
+| <b>Command</b> | <b>Reference</b> |
+|----------------|------------------|
+| AT+CMOLR       | TS 27.007 [32]   |
+| AT+CMTLR       | TS 27.007 [32]   |
+| AT+CMTLRA      | TS 27.007 [32]   |
+
+# 8 IEXIT Proforma
+
+## 8.1 A-GPS test suite parameters declarations
+
+Refer to 3GPP TS 34.123-3 [8], clause B.1.13.
+
+## 8.2 A-GNSS, LTE and NR positioning test suite parameters declarations
+
+Same PIXIT parameters are referred to clause 8.1.
+
+Additionally, the following PIXIT parameter shall be used:
+
+**Table 8.2-1: A-GNSS, LTE and NR positioning PIXIT**
+
+| <b>Parameter Name</b> | <b>Description</b>                                                  | <b>Type</b> | <b>Default Value</b> | <b>Supported Value</b> |
+|-----------------------|---------------------------------------------------------------------|-------------|----------------------|------------------------|
+| px_GnssScenario2012   | Usage of GNSS scenarios with date in 2012 from 3GPP TS 37.571-5 [5] | BOOLEAN     | FALSE                |                        |
+
+# 9 Other SS Requirements with TTCN-3 impact
+
+## 9.1 Codec Requirements
+
+Refer to 3GPP TS 36.523-3 [6] clause 8.1 and TS 38.523-3 [24] clause 8.1.
+
+# Annex A (normative): Test Suites
+
+This annex contains the approved TTCN Test Suites.
+
+## A.1 UTRA A-GPS test suite
+
+This annex includes the reference to those approved A-GPS ATS which are contained in 3GPP TS 34.123-3 [8], clause A.11.
+
+The ATSs have been produced using the Tree and Tabular Combined Notation (TTCN2) according to TR 101 666 [20].
+
+### A.1.1 Baseline of specifications
+
+Table A.1.1-1 shows the baseline of the relevant core specifications and the test specifications which the delivered ATSs are referred to.
+
+**Table A.1.1-1: Versions of the test and Core specifications**
+
+|                            |                      |
+|----------------------------|----------------------|
+| <b>Core specifications</b> | 3GPP TS 25.331 [12]  |
+| <b>Test specifications</b> | 3GPP TS 37.571-2 [3] |
+|                            | 3GPP TS 37.571-3 [4] |
+|                            | 3GPP TS 37.571-5 [6] |
+|                            | 3GPP TS 34.123-3 [8] |
+|                            | 3GPP TS 34.108 [9]   |
+|                            | 3GPP TS 34.109 [18]  |
+
+### A.1.2 AGPS ATS
+
+The approved AGPS test cases are listed. An "X" in columns FDD or LCR TDD indicates the test case approved for the relevant ATS.
+
+**Table A.1.2-1: AGPS TTCN test cases**
+
+| Test case reference |                 | Description                                                                                           | FDD | TDD |
+|---------------------|-----------------|-------------------------------------------------------------------------------------------------------|-----|-----|
+| TS 37.571-2 [3]     | TS 34.123-3 [8] |                                                                                                       |     |     |
+| 6.1.1.1             | 17.2.2.1        | LCS Network Induced location request/UE-Based GPS/Emergency Call/with USIM                            | X   |     |
+| 6.1.1.2             | 17.2.2.2        | LCS Network Induced location request/UE-Based GPS/Emergency Call/without USIM                         | X   |     |
+| 6.1.1.3             | 17.2.2.3        | LCS Network induced location request/UE-Assisted GPS/Emergency call/With USIM                         | X   |     |
+| 6.1.1.4             | 17.2.2.4        | LCS Network induced location request/UE-Assisted GPS/Emergency call/Without USIM                      | X   |     |
+| 6.1.2.1             | 17.2.3.2        | LCS Mobile originated location request/UE-Based GPS/Position estimate request/Success                 | X   |     |
+| 6.1.2.7             | 17.2.3.9        | LCS Mobile originated location request/UE-Assisted GPS/Position Estimate/Success                      | X   |     |
+| 6.1.3.1             | 17.2.4.1        | LCS Mobile terminated location request/UE-Based GPS                                                   | X   |     |
+| 6.1.3.2             | 17.2.4.2        | LCS Mobile-terminated location request/UE-Based GPS/Request for additional assistance data/Success    | X   |     |
+| 6.1.3.3             | 17.2.4.3        | LCS Mobile-terminated location request/UE-Based GPS/Failure - Not Enough Satellites                   | X   |     |
+| 6.1.3.4             | 17.2.4.4        | LCS Mobile terminated location request/UE-Assisted GPS/Success                                        | X   |     |
+| 6.1.3.5             | 17.2.4.5        | LCS Mobile terminated location request/UE-Assisted GPS/Request for additional assistance data/Success | X   |     |
+| 6.1.3.7             | 17.2.4.7        | LCS Mobile terminated location request/UE-Based GPS/Privacy                                           | X   |     |
+
+|  |  |                                                  |  |  |
+|--|--|--------------------------------------------------|--|--|
+|  |  | Verification/Location Not Allowed if No Response |  |  |
+|--|--|--------------------------------------------------|--|--|
+
+### A.1.3 The TTCN Machine Processable form (TTCN.MP)
+
+The TTCN.MP representation corresponding to the corresponding FDD ATS is referred to 3GPP TS 34.123-3 [8], clause A.11.
+
+## A.2 UTRA A-GNSS, LTE and NR/5GC positioning test suite
+
+The test suites have been produced using the Testing and Test Control Notation version 3 (TTCN-3) according to ES 201 873-1 [17].
+
+### A.2.1 Baseline of specifications
+
+Table A.2.1-1 shows the baseline of the relevant core specifications and the test specifications which the delivered TTCN test suites are referred to.
+
+**Table A.2.1-1: References of the test and Core specifications**
+
+|                                     |                       |
+|-------------------------------------|-----------------------|
+| <b>Core specifications baseline</b> | 3GPP TS 37.355 [10]   |
+|                                     | 3GPP TS 24.301 [11]   |
+|                                     | 3GPP TS 25.331 [12]   |
+|                                     | 3GPP TS 24.501 [25]   |
+|                                     | 3GPP TS 36.331 [26]   |
+|                                     | 3GPP TS 38.331 [27]   |
+| <b>Test specifications</b>          | 3GPP TS 37.571-2 [3]  |
+|                                     | 3GPP TS 37.571-3 [4]  |
+|                                     | 3GPP TS 37.571-5 [5]  |
+|                                     | 3GPP TS 36.508 [7]    |
+|                                     | 3GPP TS 38.508-1 [28] |
+
+The Test Suite in TTCN3 is contained in multiple ASCII files which accompany the present document.
+
+### A.2.2 E-UTRA LTE positioning Test Cases
+
+Table A.2.2-1 lists all approved test cases.
+
+**Table A.2.2-1: E-UTRA LTE positioning TTCN test cases**
+
+| Test case  | Description                                                                                                 |
+|------------|-------------------------------------------------------------------------------------------------------------|
+| 7.1.1      | UE Network Capability                                                                                       |
+| 7.2.1.1    | Location Notification                                                                                       |
+| 7.2.1.2    | Privacy Verification – Location Allowed if no Response                                                      |
+| 7.2.1.3    | Privacy Verification – Location not Allowed if No Response                                                  |
+| 7.2.2.2.5s | Basic Self Location: UE-assisted sub-test 5                                                                 |
+| 7.3.1.1    | Position Capability Transfer                                                                                |
+| 7.3.2.1    | LPP Duplicated Message                                                                                      |
+| 7.3.2.2    | LPP Acknowledgment                                                                                          |
+| 7.3.2.3    | LPP Retransmission                                                                                          |
+| 7.3.3.1    | LPP Requested Method not Supported – UE-Assisted sub-test 1                                                 |
+| 7.3.4.2.5s | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted sub-test 5 |
+| 7.3.4.2.6s | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted sub-test 6 |
+| 7.3.4.2.7s | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted sub-test 7 |
+| 7.3.4.4.5s | E-SMLC Initiated Position Measurement without assistance data: UE-Assisted sub-test 5                       |
+| 7.3.4.4.7s | E-SMLC Initiated Position Measurement without assistance data: UE-Assisted sub-test 7                       |
+| 7.3.5.1.5s | E-SMLC initiated Abort sub-test 5                                                                           |
+
+### A.2.3 UTRA A-GNSS Test Cases
+
+Table A.2.3-1 lists all approved test cases.
+
+**Table A.2.3-1: UTRA A-GNSS TTCN test cases**
+
+| Test case  | Description                                                                         |
+|------------|-------------------------------------------------------------------------------------|
+| 6.2.1.1.4s | NI-LR Emergency Call: UE-Based A-GNSS sub-test 4                                    |
+| 6.2.2.1.4s | MO-LR Position Estimate: UE-Based A-GNSS sub-test 4                                 |
+| 6.2.2.3.4s | MO-LR Position Estimate: UE-Based A-GNSS – Failure Not Enough Satellites sub-test 4 |
+| 6.2.3.2.4s | MT-LR Position Estimate: UE-Based A-GNSS – Failure Not Enough Satellites sub-test 4 |
+| 6.2.3.3    | Location Notification                                                               |
+| 6.2.3.4    | Privacy Verification - Location Allowed if No Response                              |
+| 6.2.3.5    | Privacy Verification - Location Not Allowed if No Response                          |
+
+### A.2.4 NR/5GC Test Cases
+
+Table A.2.4-1 lists all approved test cases.
+
+Table A.2.4-1: NR/5GC TTCN test cases
+
+| Test case         | Description                                                                                                  |
+|-------------------|--------------------------------------------------------------------------------------------------------------|
+| 9.3.1.1.NR5GC     | Position Capability Transfer                                                                                 |
+| 9.3.1.2.5s.NR5GC  | LPP Abort: Subtest 5                                                                                         |
+| 9.3.1.2.15s.NR5GC | LPP Abort: Subtest 15                                                                                        |
+| 9.3.1.2.19s.NR5GC | LPP Abort: Subtest 19                                                                                        |
+| 9.3.2.1.NR5GC     | LPP Duplicated Message                                                                                       |
+| 9.3.2.2.NR5GC     | LPP Acknowledgement                                                                                          |
+| 9.3.2.3.NR5GC     | LPP Retransmission                                                                                           |
+| 9.3.4.1.15s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Based: Subtest 15    |
+| 9.3.4.2.15s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted: Subtest 15 |
+| 9.3.4.2.19s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted: Subtest 19 |
+| 9.3.4.2.20s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted: Subtest 20 |
+| 9.3.4.2.21s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted: Subtest 21 |
+| 9.3.4.2.22s.NR5GC | E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Assisted: Subtest 22 |
+| 9.3.4.3.15s.NR5GC | E-SMLC Initiated Position Measurement without Assistance Data: UE-Based: Subtest 15                          |
+| 9.3.4.4.15s.NR5GC | E-SMLC Initiated Position Measurement without Assistance Data: UE-Assisted: Subtest 15                       |
+
+# --- Annex B (informative): ASN.1 modules
+
+## B.1 A-GPS ASN.1 module
+
+Refer to 3GPP TS 34.123-3 [8], annex H.1.
+
+## --- B.2 A-GNSS ASN.1 modules
+
+Refer to 3GPP TS 34.123-3 [8], annex H.2.
+
+## --- B.3 LPP ASN.1
+
+The LPP asn.1 modules are extracted from 3GPP TS 37.355 [10] without any change.
+
+# Annex C (informative): E-UTRA System Simulator Extension ASP Definitions in TTCN-3
+
+## C.1 EUTRA\_POS\_ASP\_TypeDefs
+
+Type definitions for configuration of Positioning Reference Signal in the system simulator; Common design principles: refer to 3GPP TS 36.523-3 [6], annex D.
+
+### C.1.1 System\_Configuration\_PosExt
+
+Formal ASP Definitions for EUTRA PRS system configuration.
+
+#### SystemRequest\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                              |                                                                                                                                                                                                                                    |
+|-------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Name              | <b>SystemRequest_PosExt_Type</b>                                             |                                                                                                                                                                                                                                    |
+| Comment           | NOTE: Same structure as SystemRequest_Type in 3GPP TS 36.523-3 [6], annex D. |                                                                                                                                                                                                                                    |
+| Cell              | <a href="#">CellConfigRequest_PosExt_Type</a>                                | configure PRS in an LTE cell;<br>the cell shall be configured as usual beforehand and SS shall raise an error when the cell does not exist yet;<br>there is no explicit release of the PRS but the whole cell needs to be released |
+
+#### SystemConfirm\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                                                        |                                 |
+|-------------------|--------------------------------------------------------------------------------------------------------|---------------------------------|
+| Name              | <b>SystemConfirm_PosExt_Type</b>                                                                       |                                 |
+| Comment           | confirmations for system configuration;<br>in general to be sent after the configuration has been done |                                 |
+| Cell              | Null_Type                                                                                              | (no further parameters from SS) |
+
+### C.1.2 Cell\_Configuration\_PosExt
+
+Specific Info for PRS Cell Configuration Primitive.
+
+#### C.1.2.1 Cell\_Configuration\_Common\_PosExt
+
+##### CellConfigRequest\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                              |                                                                                                                                                                                                                                                                    |
+|-------------------|------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Name              | <b>CellConfigRequest_PosExt_Type</b>                                         |                                                                                                                                                                                                                                                                    |
+| Comment           | NOTE: Same structure as SystemRequest_Type in 3GPP TS 36.523-3 [6], annex D. |                                                                                                                                                                                                                                                                    |
+| AddOrReconfigure  | <a href="#">CellConfigInfo_PosExt_Type</a>                                   | for PRS configuration of given cell:<br>CellId : identifier of the cell to be configured<br>RoutingInfo : None<br>TimingInfo : Now (for initial configuration and for reconfiguration in general)<br>ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general) |
+
+##### CellConfigInfo\_PosExt\_Type
+
+| TTCN-3 Record Type |                                                                                                                                                                                                                         |     |                                     |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------------------------------------|
+| Name               | <b>CellConfigInfo_PosExt_Type</b>                                                                                                                                                                                       |     |                                     |
+| Comment            | NOTE: Same structure as SystemRequest_Type in 3GPP TS 36.523-3 [6], annex D; common information for initial cell configuration or reconfiguration; in case of reconfiguration OMIT means 'keep configuration as it is'. |     |                                     |
+| Basic              | <a href="#">BasicCellConfig_PosExt_Type</a>                                                                                                                                                                             | opt | Extended PRS information for a cell |
+
+##### BasicCellConfig\_PosExt\_Type
+
+| TTCN-3 Record Type    |                                                                                                 |     |                                                        |
+|-----------------------|-------------------------------------------------------------------------------------------------|-----|--------------------------------------------------------|
+| Name                  | <b>BasicCellConfig_PosExt_Type</b>                                                              |     |                                                        |
+| Comment               | NOTE: Same structure as SystemRequest_Type in 3GPP TS 36.523-3 [6], annex D.<br>Physical layer: |     |                                                        |
+| PhysicalLayerConfigDL | <a href="#">PhysicalLayerConfigDL_PosExt_Type</a>                                               | opt | Default settings regarding physical control PRS signal |
+
+#### C.1.2.2 Downlink\_Physical\_Layer\_Configuration\_PosExt
+
+Downlink physical layer configuration:
+
+- DL antenna configuration for port 6.
+- PRS configuration.
+
+##### AntennaPort6\_Config\_Type
+
+| TTCN-3 Record Type |                                                                                                                                                            |     |  |
+|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--|
+| Name               | <b>AntennaPort6_Config_Type</b>                                                                                                                            |     |  |
+| Comment            | to configure antenna port 6 for positioning; all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it is" |     |  |
+| Port               | <a href="#">AntennaPort_Type</a>                                                                                                                           | opt |  |
+| PRS                | <a href="#">PRS_Info</a>                                                                                                                                   | opt |  |
+
+##### PhysicalLayerConfigDL\_PosExt\_Type
+
+| TTCN-3 Record Type |                                                                                                               |     |  |
+|--------------------|---------------------------------------------------------------------------------------------------------------|-----|--|
+| Name               | <b>PhysicalLayerConfigDL_PosExt_Type</b>                                                                      |     |  |
+| Comment            | all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it is" |     |  |
+| AntennaPort6       | <a href="#">AntennaPort6_Config_Type</a>                                                                      | opt |  |
+
+### C.1.3 System\_Interface\_PosExt
+
+#### SYSTEM\_CTRL\_POSEXT\_REQ
+
+| TTCN-3 Record Type |                                           |  |                                                       |
+|--------------------|-------------------------------------------|--|-------------------------------------------------------|
+| Name               | <b>SYSTEM_CTRL_POSEXT_REQ</b>             |  |                                                       |
+| Comment            |                                           |  |                                                       |
+| Common             | <a href="#">ReqAspCommonPart_Type</a>     |  | For configuration of antenna port 6 TimingInfo is now |
+| Request            | <a href="#">SystemRequest_PosExt_Type</a> |  | configure a PRS in a cell                             |
+
+#### SYSTEM\_CTRL\_POSEXT\_CNF
+
+| TTCN-3 Record Type |                                           |  |                                                                     |
+|--------------------|-------------------------------------------|--|---------------------------------------------------------------------|
+| Name               | SYSTEM_CTRL_POSEXT_CNF                    |  |                                                                     |
+| Comment            |                                           |  |                                                                     |
+| Common             | CnfAspCommonPart_Type                     |  | TimingInfo is ignored by TTCN<br>=> SS may set TimingInfo to "None" |
+| Confirm            | <a href="#">SystemConfirm_PosExt_Type</a> |  |                                                                     |
+
+#### EUTRA\_SYSTEM\_POSEXT\_PORT
+
+| TTCN-3 Port Type |                                                                |  |  |
+|------------------|----------------------------------------------------------------|--|--|
+| Name             | EUTRA_SYSTEM_POSEXT_PORT                                       |  |  |
+| Comment          | EUTRA PTC: Ext Port for system configuration of antenna port 6 |  |  |
+| out              | <a href="#">SYSTEM_CTRL_POSEXT_REQ</a>                         |  |  |
+| in               | <a href="#">SYSTEM_CTRL_POSEXT_CNF</a>                         |  |  |
+
+## C.2 References to TTCN-3
+
+| References to TTCN-3   |                                         |          |
+|------------------------|-----------------------------------------|----------|
+| EUTRA_POS_ASP_TypeDefs | Positioning/EUTRA_POS_ASP_TypeDefs.ttcn | Rev 6449 |
+
+# Annex D (informative) Positioning System Simulator ASP Definitions in TTCN-3
+
+## D.1 PosSystem\_ASP\_TypeDefs
+
+### PosSystem\_ASP\_TypeDefs: Constant Definitions
+
+| TTCN-3 Basic Types |         |    |  |
+|--------------------|---------|----|--|
+| tsc_MaxPosSystems  | integer | 12 |  |
+
+#### PositioningSystemType
+
+| TTCN-3 Enumerated Type |                       |
+|------------------------|-----------------------|
+| Name                   | PositioningSystemType |
+| Comment                |                       |
+| gps                    |                       |
+| modernizedGPS          |                       |
+| glonass                |                       |
+| galileo                |                       |
+| qzss                   |                       |
+| otdoa                  |                       |
+| ecid                   |                       |
+| bds                    |                       |
+| mbs                    |                       |
+| wlan                   |                       |
+| bluetooth              |                       |
+| sensor                 |                       |
+
+#### PositioningSystemList\_Type
+
+| TTCN-3 Record of Type                                                         |                            |
+|-------------------------------------------------------------------------------|----------------------------|
+| Name                                                                          | PositioningSystemList_Type |
+| Comment                                                                       |                            |
+| record length (1..tsc_MaxPosSystems) of <a href="#">PositioningSystemType</a> |                            |
+
+#### Altitude\_Type
+
+| TTCN-3 Record Type |               |  |                                    |
+|--------------------|---------------|--|------------------------------------|
+| Name               | Altitude_Type |  |                                    |
+| Comment            |               |  |                                    |
+| Height             | integer       |  | Height above a sea level in meters |
+
+### D.1.1 PosSystem\_Load\_Scenario
+
+Load scenarios follow 3GPP TS 37.571-5 [5]
+
+#### PosSystem\_Load\_Scenario: Basic Type Definitions
+
+| TTCN-3 Basic Types  |         |  |  |
+|---------------------|---------|--|--|
+| ScenarioNumber_Type | integer |  |  |
+
+##### PositioningScenario\_Type
+
+| TTCN-3 Union Type |                                     |                                                 |
+|-------------------|-------------------------------------|-------------------------------------------------|
+| Name              | PositioningScenario_Type            |                                                 |
+| Comment           |                                     |                                                 |
+| LTE_Positioning   | <a href="#">ScenarioNumber_Type</a> | Reference to 3GPP TS 37.571-5 [5]               |
+| AGNSS             | <a href="#">ScenarioNumber_Type</a> | Reference to 3GPP TS 37.571-5 [5]               |
+| V2X               | <a href="#">ScenarioNumber_Type</a> | V2X Reference to 3GPP TS 36.508 [7] clause 4.11 |
+| NR_Positioning    | <a href="#">ScenarioNumber_Type</a> | Reference to 3GPP TS 37.571-5 [5]               |
+| Aerial            | <a href="#">ScenarioNumber_Type</a> | Reference to 3GPP TS 36.508 [7] clause 4.12     |
+| NR_Sidelink       | <a href="#">ScenarioNumber_Type</a> | Reference to 3GPP TS 38.508-1 [30] clause 4.11  |
+
+### D.1.2 PosSystem\_Retrieve\_Data
+
+#### D.1.2.1 SatSystem\_Retrieve\_UTRAN\_Data
+
+##### UTRAN\_GPS\_AssistanceDataRequest\_Type
+
+| TTCN-3 Record Type   |                                      |  |                                                                                                  |
+|----------------------|--------------------------------------|--|--------------------------------------------------------------------------------------------------|
+| Name                 | UTRAN_GPS_AssistanceDataRequest_Type |  |                                                                                                  |
+| Comment              |                                      |  |                                                                                                  |
+| AssistanceDataReqGPS | bitstring                            |  | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GPS-AdditionalAssistanceDataRequest |
+
+##### UTRAN\_GNSS\_AssistanceDataRequest\_Type
+
+| TTCN-3 Record Type           |                                       |     |                                                                                                           |
+|------------------------------|---------------------------------------|-----|-----------------------------------------------------------------------------------------------------------|
+| Name                         | UTRAN_GNSS_AssistanceDataRequest_Type |     |                                                                                                           |
+| Comment                      |                                       |     |                                                                                                           |
+| AssistanceDataReqGNSS        | bitstring                             | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GNSS-AdditionalAssistanceDataRequest         |
+| AssistanceDataReqGNSSv860ext | bitstring                             | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GNSS-AdditionalAssistanceDataRequest-v860ext |
+| AssistanceDataReqGNSSvc50ext | bitstring                             | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GNSS-AdditionalAssistanceDataRequest-vc50ext |
+
+##### UTRAN\_AssistanceDataRequest\_Type
+
+| TTCN-3 Union Type |                                                       |
+|-------------------|-------------------------------------------------------|
+| Name              | UTRAN_AssistanceDataRequest_Type                      |
+| Comment           |                                                       |
+| GPS               | <a href="#">UTRAN_GPS_AssistanceDataRequest_Type</a>  |
+| GNSS              | <a href="#">UTRAN_GNSS_AssistanceDataRequest_Type</a> |
+
+##### UTRAN\_AssistanceDataRequestList\_Type
+
+| TTCN-3 Record of Type                                                                   |                                      |
+|-----------------------------------------------------------------------------------------|--------------------------------------|
+| Name                                                                                    | UTRAN_AssistanceDataRequestList_Type |
+| Comment                                                                                 |                                      |
+| record length(1..tsc_MaxPosSystems) of <a href="#">UTRAN_AssistanceDataRequest_Type</a> |                                      |
+
+##### UTRAN\_GPS\_AssistanceData\_Type
+
+| TTCN-3 Record Type       |                                                                                                                                                                                                                |     |                                                                                     |
+|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------------------------------------------------------------------------------------|
+| Name                     | UTRAN_GPS_AssistanceData_Type                                                                                                                                                                                  |     |                                                                                     |
+| Comment                  | The returned Almanac information is split into two fields:<br>Almanac for satellites 1 to 16 in AssistanceDataGPSr7 together with other information;<br>Almanac for satellites 17 to 31: in 'almanacSat17To31' |     |                                                                                     |
+| AssistanceDataGPSr7      | bitstring                                                                                                                                                                                                      | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GPS-AssistanceData-r7  |
+| AssistanceDataGPSr12     | bitstring                                                                                                                                                                                                      | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GPS-AssistanceData-r12 |
+| AlmanacSatInfoList17To31 | bitstring                                                                                                                                                                                                      | opt | bitstring containing 3GPP TS 25.331 [12] type AlmanacSatInfoList                    |
+
+##### UTRAN\_GNSS\_AssistanceData\_Type
+
+| TTCN-3 Record Type     |                                |     |                                                                                      |
+|------------------------|--------------------------------|-----|--------------------------------------------------------------------------------------|
+| Name                   | UTRAN_GNSS_AssistanceData_Type |     |                                                                                      |
+| Comment                |                                |     |                                                                                      |
+| AssistanceDataGNSS_r8  | bitstring                      | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GNSS-AssistanceData-r8  |
+| AssistanceDataGNSS_r12 | bitstring                      | opt | bitstring containing 3GPP TS 25.331 [12] type UE-Positioning-GNSS-AssistanceData-r12 |
+
+##### UTRAN\_AssistanceData\_Type
+
+| TTCN-3 Union Type |                                                |  |
+|-------------------|------------------------------------------------|--|
+| Name              | UTRAN_AssistanceData_Type                      |  |
+| Comment           |                                                |  |
+| GPS               | <a href="#">UTRAN_GPS_AssistanceData_Type</a>  |  |
+| GNSS              | <a href="#">UTRAN_GNSS_AssistanceData_Type</a> |  |
+
+##### UTRAN\_AssistanceDataList\_Type
+
+| TTCN-3 Record of Type                                                            |                               |
+|----------------------------------------------------------------------------------|-------------------------------|
+| Name                                                                             | UTRAN_AssistanceDataList_Type |
+| Comment                                                                          |                               |
+| record length(1..tsc_MaxPosSystems) of <a href="#">UTRAN_AssistanceData_Type</a> |                               |
+
+#### D.1.2.2 PosSystem\_Retrieve\_LPP\_Data
+
+When data is to be requested for more than one positioning system, they will be included into one single template. This template will include a list with one element for each positioning system.  
+See template "cs\_RequestAssistData\_UEB\_GpsAndGlonass" as an example.
+
+##### LPP\_AssistanceDataRequest\_Type
+
+| TTCN-3 Union Type  |                                |                                                                            |
+|--------------------|--------------------------------|----------------------------------------------------------------------------|
+| Name               | LPP_AssistanceDataRequest_Type |                                                                            |
+| Comment            |                                |                                                                            |
+| LPP_AssistanceData | bitstring                      | bitstring containing 3GPP TS 37.355 [10] type RequestAssistanceData-r9-IEs |
+
+##### LPP\_AssistanceDataProvide\_Type
+
+| TTCN-3 Union Type  |                                |                                                                            |
+|--------------------|--------------------------------|----------------------------------------------------------------------------|
+| Name               | LPP_AssistanceDataProvide_Type |                                                                            |
+| Comment            |                                |                                                                            |
+| LPP_AssistanceData | bitstring                      | bitstring containing 3GPP TS 37.355 [10] type ProvideAssistanceData-r9-IEs |
+
+##### LPP\_AssistanceDataRequestList\_Type
+
+| TTCN-3 Record of Type                                                                 |                                    |
+|---------------------------------------------------------------------------------------|------------------------------------|
+| Name                                                                                  | LPP_AssistanceDataRequestList_Type |
+| Comment                                                                               |                                    |
+| record length(1..tsc_MaxPosSystems) of <a href="#">LPP_AssistanceDataRequest_Type</a> |                                    |
+
+##### LPP\_AssistanceDataList\_Type
+
+| TTCN-3 Record of Type                                                                 |                             |
+|---------------------------------------------------------------------------------------|-----------------------------|
+| Name                                                                                  | LPP_AssistanceDataList_Type |
+| Comment                                                                               |                             |
+| record length(1..tsc_MaxPosSystems) of <a href="#">LPP_AssistanceDataProvide_Type</a> |                             |
+
+#### D.1.2.3 PosSystem\_Retrieve\_Data\_Common
+
+##### AssistanceDataRetrieveRequest\_Type
+
+| TTCN-3 Union Type |                                                      |                                                                                                |
+|-------------------|------------------------------------------------------|------------------------------------------------------------------------------------------------|
+| Name              | AssistanceDataRetrieveRequest_Type                   |                                                                                                |
+| Comment           |                                                      |                                                                                                |
+| LPP               | <a href="#">LPP_AssistanceDataRequestList_Type</a>   | LTE/NR positioning                                                                             |
+| UTRA_GNSS         | <a href="#">UTRAN_AssistanceDataRequestList_Type</a> | Retrieve A-GNSS data list in the order of positioning system provided in PositioningSystemList |
+
+##### AssistanceDataRetrieveResponse\_Type
+
+| TTCN-3 Union Type |                                               |                                                                                                |
+|-------------------|-----------------------------------------------|------------------------------------------------------------------------------------------------|
+| Name              | AssistanceDataRetrieveResponse_Type           |                                                                                                |
+| Comment           |                                               |                                                                                                |
+| LPP               | <a href="#">LPP_AssistanceDataList_Type</a>   | LTE/NR positioning                                                                             |
+| UTRA_AGNSS        | <a href="#">UTRAN_AssistanceDataList_Type</a> | Retrieve A-GNSS data list in the order of positioning system provided in PositioningSystemList |
+
+### D.1.3 PosSystem\_PowerControl
+
+#### PowerControl\_Type
+
+| TTCN-3 Union Type |                                                                                   |                                                  |
+|-------------------|-----------------------------------------------------------------------------------|--------------------------------------------------|
+| Name              | PowerControl_Type                                                                 |                                                  |
+| Comment           | V2X. The GNSS simulator is switched on/off without stopping the UTC time sequence |                                                  |
+| PowerOn           | <a href="#">Null_Type</a>                                                         | By default the power is on in the GNSS simulator |
+| PowerOff          | <a href="#">Null_Type</a>                                                         |                                                  |
+
+### D.1.4 PosSystem\_GnssUtcTime
+
+#### GnssUtcTime\_Type
+
+| TTCN-3 Record Type |                                |  |                                                                       |
+|--------------------|--------------------------------|--|-----------------------------------------------------------------------|
+| Name               | <b>GnssUtcTime_Type</b>        |  |                                                                       |
+| Comment            |                                |  |                                                                       |
+| Struct_tm          | <a href="#">Struct_tm_Type</a> |  | Local GNSS time                                                       |
+| TimezoneInfo       | integer                        |  | Difference (in seconds) between the UTC time (GMT) and the local time |
+
+### D.1.5 System\_Interface
+
+Common ASP definitions
+
+#### PosSystemCtrlRequest\_Type
+
+| TTCN-3 Union Type   |                                                    |                                                                                                                   |
+|---------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| Name                | <b>PosSystemCtrlRequest_Type</b>                   |                                                                                                                   |
+| Comment             |                                                    |                                                                                                                   |
+| Start               | <a href="#">Null_Type</a>                          |                                                                                                                   |
+| Stop                | <a href="#">Null_Type</a>                          |                                                                                                                   |
+| LoadScenario        | <a href="#">PositioningScenario_Type</a>           |                                                                                                                   |
+| RetrieveData        | <a href="#">AssistanceDataRetrieveRequest_Type</a> |                                                                                                                   |
+| TriggerMove         | <a href="#">Null_Type</a>                          | V2X. Start moving to the next area/zone in the scenario                                                           |
+| TriggerPowerOnOff   | <a href="#">PowerControl_Type</a>                  | V2X. Switch on/off the transmitter without stopping UTC time sequence                                             |
+| SetAltitude         | <a href="#">Altitude_Type</a>                      | Aerial Set the height above the sea level to the provided value                                                   |
+| TriggerAerialMove   | <a href="#">Altitude_Type</a>                      | Aerial Start moving towards target height                                                                         |
+| RetrieveGnssUtcTime | <a href="#">Null_Type</a>                          | Get current UTC time of the GNSS scenario. This can only be used once a GNSS scenario has been loaded and started |
+
+#### PosSystemCtrlConfirm\_Type
+
+| TTCN-3 Union Type   |                                                              |        |
+|---------------------|--------------------------------------------------------------|--------|
+| Name                | <b>PosSystemCtrlConfirm_Type</b>                             |        |
+| Comment             | In general, to be sent after the configuration has been done |        |
+| Start               | <a href="#">Null_Type</a>                                    |        |
+| Stop                | <a href="#">Null_Type</a>                                    |        |
+| LoadScenario        | <a href="#">Null_Type</a>                                    |        |
+| RetrieveData        | <a href="#">AssistanceDataRetrieveResponse_Type</a>          |        |
+| TriggerMove         | <a href="#">Null_Type</a>                                    | V2X    |
+| TriggerPowerOnOff   | <a href="#">Null_Type</a>                                    | V2X    |
+| SetAltitude         | <a href="#">Null_Type</a>                                    | Aerial |
+| TriggerAerialMove   | <a href="#">Null_Type</a>                                    | Aerial |
+| RetrieveGnssUtcTime | <a href="#">GnssUtcTime_Type</a>                             |        |
+
+#### POS\_SYSTEM\_CTRL\_REQ
+
+| TTCN-3 Record Type    |                                            |  |                                                                                                                           |
+|-----------------------|--------------------------------------------|--|---------------------------------------------------------------------------------------------------------------------------|
+| Name                  | POS_SYSTEM_CTRL_REQ                        |  |                                                                                                                           |
+| Comment               |                                            |  |                                                                                                                           |
+| PositioningSystemList | <a href="#">PositioningSystemList_Type</a> |  | The list of positioning systems to be configured; there is only one system of one type in the list e.g. gps, galileo etc. |
+| CnfFlag               | boolean                                    |  | true => SS shall send CNF                                                                                                 |
+| Request               | <a href="#">PosSystemCtrlRequest_Type</a>  |  |                                                                                                                           |
+
+#### POS\_SYSTEM\_CTRL\_CNF
+
+| TTCN-3 Record Type    |                                            |  |  |
+|-----------------------|--------------------------------------------|--|--|
+| Name                  | POS_SYSTEM_CTRL_CNF                        |  |  |
+| Comment               |                                            |  |  |
+| PositioningSystemList | <a href="#">PositioningSystemList_Type</a> |  |  |
+| Confirm               | <a href="#">PosSystemCtrlConfirm_Type</a>  |  |  |
+
+#### POS\_MTC\_SYSTEM\_PORT
+
+| TTCN-3 Port Type |                                                         |  |  |
+|------------------|---------------------------------------------------------|--|--|
+| Name             | POS_MTC_SYSTEM_PORT                                     |  |  |
+| Comment          | Positioning: port at the MTC to be mapped to the system |  |  |
+| out              | <a href="#">POS SYSTEM CTRL REQ</a>                     |  |  |
+| in               | <a href="#">POS SYSTEM CTRL CNF</a>                     |  |  |
+
+#### POS\_MTC\_PTC\_PORT
+
+| TTCN-3 Port Type |                                                                                                 |  |  |
+|------------------|-------------------------------------------------------------------------------------------------|--|--|
+| Name             | POS_MTC_PTC_PORT                                                                                |  |  |
+| Comment          | Positioning: port at the MTC to hand over information from the positioning system to the PTC(s) |  |  |
+| out              | <a href="#">POS SYSTEM CTRL CNF</a>                                                             |  |  |
+| in               | <a href="#">POS SYSTEM CTRL REQ</a>                                                             |  |  |
+
+#### POS\_PTC\_MTC\_PORT
+
+| TTCN-3 Port Type |                                                                                        |  |  |
+|------------------|----------------------------------------------------------------------------------------|--|--|
+| Name             | POS_PTC_MTC_PORT                                                                       |  |  |
+| Comment          | Positioning: port at the PTC(s) to send commands to the positioning system via the MTC |  |  |
+| out              | <a href="#">POS SYSTEM CTRL REQ</a>                                                    |  |  |
+| in               | <a href="#">POS SYSTEM CTRL CNF</a>                                                    |  |  |
+
+## D.2 CommonDefs
+
+### CommonDefs: Basic Type Definitions
+
+| TTCN-3 Basic Types |                |                                            |
+|--------------------|----------------|--------------------------------------------|
+| Null_Type          | boolean (true) | dummy type for 'typeless' fields in unions |
+
+#### Struct\_tm\_Type
+
+| TTCN-3 Record Type |                                                                                                         |  |                                                                                                                           |
+|--------------------|---------------------------------------------------------------------------------------------------------|--|---------------------------------------------------------------------------------------------------------------------------|
+| Name               | Struct_tm_Type                                                                                          |  |                                                                                                                           |
+| Comment            | TTCN-3 equivalent for the "struct tm" as defined on C standard library (time.h or ctime.h for C or C++) |  |                                                                                                                           |
+| tm_sec             | integer                                                                                                 |  | seconds after the minute 0..61 (tm_sec is generally 0-59. Extra range to accommodate for leap seconds in certain systems) |
+| tm_min             | integer                                                                                                 |  | minutes after the hour 0..59                                                                                              |
+| tm_hour            | integer                                                                                                 |  | hours since midnight 0..23                                                                                                |
+| tm_mday            | integer                                                                                                 |  | day of the month 1..31                                                                                                    |
+| tm_mon             | integer                                                                                                 |  | months since January 0..11                                                                                                |
+| tm_year            | integer                                                                                                 |  | years since 1900                                                                                                          |
+| tm_wday            | integer                                                                                                 |  | days since Sunday 0..6                                                                                                    |
+| tm_yday            | integer                                                                                                 |  | days since January 1 0..365                                                                                               |
+| tm_isdst           | integer                                                                                                 |  | Daylight Saving Time flag                                                                                                 |
+
+## D.3 References to TTCN-3
+
+| References to TTCN-3   |                                 |           |
+|------------------------|---------------------------------|-----------|
+| PosSystem_ASP_TypeDefs | POS/PosSystem_ASP_TypeDefs.ttcn | Rev 32599 |
+| CommonDefs             | Common/CommonDefs.ttcn          | Rev 32608 |
+
+# Annex E (informative) NR5GC System Simulator Extension ASP Definitions in TTCN-3
+
+## E.1 NR5GC\_POS\_ASP\_TypeDefs
+
+Type definitions for configuration of DL Positioning Reference Signal in the system simulator;  
+Common design principles: refer to 3GPP TS 38.523-3 [24] annex D.
+
+### E.1.1 NR\_System\_Configuration\_PosExt
+
+Formal ASP Definitions for NR5GC DL-PRS system configuration
+
+#### NR\_SystemRequest\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                                |                                                                                                                                                                                                                                      |
+|-------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Name              | NR_SystemRequest_PosExt_Type                                                   |                                                                                                                                                                                                                                      |
+| Comment           | NOTE: Same structure as NR_SystemRequest_Type in 3GPP TS 38.523-3 [24] annex D |                                                                                                                                                                                                                                      |
+| Cell              | <a href="#">NR_CellConfigRequest_PosExt_Type</a>                               | configure DL-PRS in an NR cell;<br>the cell shall be configured as usual beforehand and SS shall raise an error when the cell does not exist yet;<br>there is no explicit release of the PRS but the whole cell needs to be released |
+
+#### NR\_SystemConfirm\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                                                        |                                 |
+|-------------------|--------------------------------------------------------------------------------------------------------|---------------------------------|
+| Name              | NR_SystemConfirm_PosExt_Type                                                                           |                                 |
+| Comment           | confirmations for system configuration;<br>in general to be sent after the configuration has been done |                                 |
+| Cell              | Null_Type                                                                                              | (no further parameters from SS) |
+
+### E.1.2 NR\_Cell\_Configuration\_PosExt
+
+Specific Info for DL-PRS Cell Configuration Primitive
+
+#### E.1.2.1 NR\_Cell\_Configuration\_Common\_PosExt
+
+##### NR\_CellConfigRequest\_PosExt\_Type
+
+| TTCN-3 Union Type |                                                                                |                                                                                                                                                                                                                                                                                                                              |
+|-------------------|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Name              | NR_CellConfigRequest_PosExt_Type                                               |                                                                                                                                                                                                                                                                                                                              |
+| Comment           | NOTE: Same structure as NR_SystemRequest_Type in 3GPP TS 38.523-3 [24] annex D |                                                                                                                                                                                                                                                                                                                              |
+| AddOrReconfigure  | <a href="#">NR_CellConfigInfo_PosExt_Type</a>                                  | for PRS configuration of given cell:<br>CellId : identifier of the cell to be configured<br>RoutingInfo : None<br>RlcBearerRouting : 'None'<br>MacBearerRouting : 'omit'<br>TimingInfo : Now (for initial configuration and for reconfiguration in general)<br>ControlInfo : CnfFlag:=true; FollowOnFlag:=false (in general) |
+
+##### NR\_CellConfigInfo\_PosExt\_Type
+
+| TTCN-3 Record Type |                                                                                                                                                                                                                                |     |                                        |
+|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----------------------------------------|
+| Name               | NR_CellConfigInfo_PosExt_Type                                                                                                                                                                                                  |     |                                        |
+| Comment            | NOTE: Same structure as NR_SystemRequest_Type in 3GPP TS 38.523-3 [24] annex D<br>common information for initial cell configuration or reconfiguration;<br>in case of reconfiguration OMIT means 'keep configuration as it is' |     |                                        |
+| PhysicalLayer      | <a href="#">NR_CellConfigPhysicalLayer_PosExt_Type</a>                                                                                                                                                                         | opt | Extended DL-PRS information for a cell |
+
+##### NR\_CellConfigPhysicalLayer\_PosExt\_Type
+
+| TTCN-3 Record Type |                                                                                                   |     |                                                           |
+|--------------------|---------------------------------------------------------------------------------------------------|-----|-----------------------------------------------------------|
+| Name               | NR_CellConfigPhysicalLayer_PosExt_Type                                                            |     |                                                           |
+| Comment            | NOTE: Same structure as NR_SystemRequest_Type in 3GPP TS 38.523-3 [24] annex D<br>Physical layer: |     |                                                           |
+| Downlink           | <a href="#">NR_CellConfigPhysicalLayerDownlink_PosExt_Type</a>                                    | opt | Default settings regarding physical control DL-PRS signal |
+
+#### E.1.2.2 Downlink\_Physical\_Layer\_Configuration\_PosExt
+
+Downlink physical layer configuration:
+
+- DL-PRS Frequency Layer configuration.
+- DL-PRS TRP configuration.
+
+##### Downlink\_Physical\_Layer\_Configuration\_PosExt: Basic Type Definitions
+
+| TTCN-3 Basic Types          |                                                              |  |
+|-----------------------------|--------------------------------------------------------------|--|
+| <b>DIPrs_CombSizeN_Type</b> | NR_DL_PRS_PositioningFrequencyLayer r16.dl_PRS_CombSizeN_r16 |  |
+
+###### DIPrs\_FreqLayerConfig\_Type
+
+| TTCN-3 Record Type   |                                      |     |  |
+|----------------------|--------------------------------------|-----|--|
+| <b>Name</b>          | <b>DIPrs_FreqLayerConfig_Type</b>    |     |  |
+| <b>Comment</b>       |                                      |     |  |
+| DIPrs_Resourc<br>eBW | integer                              | opt |  |
+| DIPrs_CombSi<br>zeN  | <a href="#">DIPrs_CombSizeN_Type</a> | opt |  |
+
+###### DIPrs\_TRPConfig\_Type
+
+| TTCN-3 Record Type                     |                             |     |  |
+|----------------------------------------|-----------------------------|-----|--|
+| <b>Name</b>                            | <b>DIPrs_TRPConfig_Type</b> |     |  |
+| <b>Comment</b>                         |                             |     |  |
+| NrDIPrsSfn0Off<br>set                  | NR_DL_PRS_SFN0_Offset_r16   | opt |  |
+| NrDIPrsExpect<br>edRstd                | integer                     | opt |  |
+| NrDIPrsExpect<br>edRstdUncertai<br>nty | integer                     | opt |  |
+| NrDIPrsInfo                            | NR_DL_PRS_Info_r16          | opt |  |
+
+###### DL\_PRSConfig\_Type
+
+| TTCN-3 Record Type        |                                                                                                                                                       |     |  |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----|--|
+| <b>Name</b>               | <b>DL_PRSConfig_Type</b>                                                                                                                              |     |  |
+| <b>Comment</b>            | to configure DL-PRS for positioning;<br>all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it is" |     |  |
+| DIPrs_FreqLay<br>erConfig | <a href="#">DIPrs_FreqLayerConfig_Type</a>                                                                                                            | opt |  |
+| DIPrs_TRPCon<br>fig       | <a href="#">DIPrs_TRPConfig_Type</a>                                                                                                                  | opt |  |
+
+##### NR\_CellConfigPhysicalLayerDownlink\_PosExt\_Type
+
+| TTCN-3 Record Type |                                                                                                               |     |  |
+|--------------------|---------------------------------------------------------------------------------------------------------------|-----|--|
+| <b>Name</b>        | <b>NR_CellConfigPhysicalLayerDownlink_PosExt_Type</b>                                                         |     |  |
+| <b>Comment</b>     | all fields are declared as optional to allow single reconfigurations; in this case omit means "keep as it is" |     |  |
+| DL_PRSConfig       | <a href="#">DL_PRSConfig_Type</a>                                                                             | opt |  |
+
+### E.1.3 NR\_System\_Interface\_PosExt
+
+#### NR\_SYSTEM\_CTRL\_POSEXT\_REQ
+
+| TTCN-3 Record Type |                                              |  |                                               |
+|--------------------|----------------------------------------------|--|-----------------------------------------------|
+| Name               | NR_SYSTEM_CTRL_POSEXT_REQ                    |  |                                               |
+| Comment            |                                              |  |                                               |
+| Common             | NR_ReqAspCommonPart_Type                     |  | For configuration of DL-PRS TimingInfo is now |
+| Request            | <a href="#">NR_SystemRequest_PosExt_Type</a> |  | configure a DL-PRS in a cell                  |
+
+#### NR\_SYSTEM\_CTRL\_POSEXT\_CNF
+
+| TTCN-3 Record Type |                                              |  |                                                                     |
+|--------------------|----------------------------------------------|--|---------------------------------------------------------------------|
+| Name               | NR_SYSTEM_CTRL_POSEXT_CNF                    |  |                                                                     |
+| Comment            |                                              |  |                                                                     |
+| Common             | NR_CnfAspCommonPart_Type                     |  | TimingInfo is ignored by TTCN<br>=> SS may set TimingInfo to "None" |
+| Confirm            | <a href="#">NR_SystemConfirm_PosExt_Type</a> |  |                                                                     |
+
+#### NR\_SYSTEM\_POSEXT\_PORT
+
+| TTCN-3 Port Type |                                                     |  |  |
+|------------------|-----------------------------------------------------|--|--|
+| Name             | NR_SYSTEM_POSEXT_PORT                               |  |  |
+| Comment          | NR PTC: Ext Port for system configuration of DL-PRS |  |  |
+| out              | <a href="#">NR SYSTEM CTRL POSEXT REQ</a>           |  |  |
+| in               | <a href="#">NR SYSTEM CTRL POSEXT CNF</a>           |  |  |
+
+## E.2 References to TTCN-3
+
+| References to TTCN-3   |                                   |           |
+|------------------------|-----------------------------------|-----------|
+| NR5GC_POS_ASP_TypeDefs | NR5GC/NR5GC_POS_ASP_TypeDefs.ttcn | Rev 20699 |
+
+# Annex F (informative): Change history
+
+| Change history |         |           |      |         |                                                                                                                 |        |        |
+|----------------|---------|-----------|------|---------|-----------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #   | TSG Doc.  | CR   | Re<br>v | Subject/Comment                                                                                                 | Old    | New    |
+| 2011-06        | RAN5#51 | R5-112203 | -    | -       | Initial proposal for A-GNSS                                                                                     |        | 0.0.1  |
+| 2011-09        | RAN5#52 | R5-113037 | -    | -       | Introduced positioning test model                                                                               | 0.0.1  | 0.1.0  |
+| 2011-11        | RAN5#53 | R5-115106 | -    | -       | Imported A-GPS test model from 3GPP TS 34.123-3                                                                 | 0.1.0  | 1.0.0  |
+| 2011-12        | RAN#54  | RP-111627 | -    | -       | Presentation of V1.0.0                                                                                          | 0.1.0  | 1.0.0  |
+| 2012-05        | RAN5#55 | R5-121083 | -    | -       | Presentation of V1.1.0                                                                                          | 1.0.0  | 1.1.0  |
+| 2012-06        | RAN#56  | RP-120614 | -    | -       | Presentation of V2.0.0                                                                                          | 1.0.0  | 2.0.0  |
+| 2012-06        | RAN#56  | -         | -    | -       | Editorial corrections and formatings.                                                                           | 2.0.0  | 9.0.0  |
+| 2012-06        | RAN#56  | -         | -    | -       | Raised to v10.0.0 with no change.                                                                               | 9.0.0  | 10.0.0 |
+| 2012-09        | RAN#57  | R5-123690 | 0001 | -       | 37571-4: Routine maintenance and updates                                                                        | 10.0.0 | 10.1.0 |
+| 2013-06        | RAN#60  | R5-131136 | 0003 | -       | 37571-4: Routine maintenance and updates                                                                        | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130125 | 0004 | -       | Addition of EUTRA UE Positioning test case 7.1.1                                                                | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130145 | 0005 | -       | Addition of EUTRA UE Positioning test case 7.3.1.1                                                              | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130147 | 0006 | -       | Addition of EUTRA UE Positioning test case 7.3.2.1                                                              | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130149 | 0007 | -       | Addition of EUTRA UE Positioning test case 7.3.2.2                                                              | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130151 | 0008 | -       | Addition of EUTRA UE Positioning test case 7.3.2.3                                                              | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130153 | 0009 | -       | Addition of EUTRA UE Positioning test case 7.3.5.1_6s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130155 | 0010 | -       | Addition of EUTRA UE Positioning test case 7.3.5.1_5s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130157 | 0011 | -       | Addition of EUTRA UE Positioning test case 7.3.4.2_5s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130159 | 0012 | -       | Addition of EUTRA UE Positioning test case 7.3.4.2_6s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130288 | 0013 | -       | Addition of EUTRA UE Positioning test case 7.3.4.4_5s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | R5s130290 | 0014 | -       | Addition of EUTRA UE Positioning test case 7.3.5.1_1s                                                           | 10.1.0 | 10.2.0 |
+| 2013-06        | RAN#60  | RP-130616 | 0015 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.1.0 | 10.2.0 |
+| 2013-09        | RAN#61  | R5s130421 | 0016 | -       | Correction to EUTRA UE Positioning test cases 7.3.4.2.5s and 7.3.4.4.5s                                         | 10.2.0 | 10.3.0 |
+| 2013-09        | RAN#61  | R5s130457 | 0017 | -       | Correction to EUTRA UE Positioning test case 7.3.5.1.1s                                                         | 10.2.0 | 10.3.0 |
+| 2013-09        | RAN#61  | R5s130468 | 0018 | -       | Correction to EUTRA UE Positioning test cases 7.3.1.1                                                           | 10.2.0 | 10.3.0 |
+| 2013-09        | RAN#61  | RP-131167 | 0019 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.2.0 | 10.3.0 |
+| 2013-12        | RAN#62  | R5s130618 | 0020 | -       | Addition of EUTRA UE Positioning test case 7.3.4.1_1s                                                           | 10.3.0 | 10.4.0 |
+| 2013-12        | RAN#62  | R5s130627 | 0021 | -       | Addition of EUTRA UE Positioning test case 7.3.4.3_1s                                                           | 10.3.0 | 10.4.0 |
+| 2013-12        | RAN#62  | RP-131871 | 0022 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.3.0 | 10.4.0 |
+| 2014-03        | RAN#63  | R5-140326 | 0023 | -       | A-GNSS ASN.1 reference                                                                                          | 10.4.0 | 10.5.0 |
+| 2014-03        | RAN#63  | R5s130913 | 0024 | -       | Correction to function fl_TC_7_3_5_1_GNSS_TestBody                                                              | 10.4.0 | 10.5.0 |
+| 2014-03        | RAN#63  | R5s130914 | 0025 | -       | Correction to svID values in AcquisitionAssist and AuxiliaryInformation                                         | 10.4.0 | 10.5.0 |
+| 2014-03        | RAN#63  | R5s131009 | 0026 | -       | Addition of EUTRA UE Positioning test case 7.3.5.1_2s                                                           | 10.4.0 | 10.5.0 |
+| 2014-03        | RAN#63  | R5s131011 | 0027 | -       | Addition of EUTRA UE Positioning test case 7.3.5.1_4s                                                           | 10.4.0 | 10.5.0 |
+
+| Change history |        |           |      |         |                                                                                                                 |        |        |
+|----------------|--------|-----------|------|---------|-----------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Re<br>v | Subject/Comment                                                                                                 | Old    | New    |
+| 2014-03        | RAN#63 | RP-140316 | 0028 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.4.0 | 10.5.0 |
+| 2014-06        | RAN#64 | R5s140086 | 0029 | -       | Addition of EUTRA UE Positioning test case 7.2.1.1                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140088 | 0030 | -       | Addition of EUTRA UE Positioning test case 7.2.1.2                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140090 | 0031 | -       | Addition of EUTRA UE Positioning test case 7.2.1.3                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140242 | 0032 | -       | Correction to LTE UE Positioning test case 7.3.5.1                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140253 | 0033 | -       | Addition of EUTRA UE Positioning test case 7.3.4.4.1s                                                           | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140255 | 0034 | -       | Addition of EUTRA UE Positioning test case 7.3.4.2.1s                                                           | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140257 | 0035 | -       | Correction to LTE UE Positioning test case 7.3.4.3.1s                                                           | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140316 | 0036 | -       | Addition of UTRAN UE Positioning test case 6.2.3.3                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140318 | 0037 | -       | Addition of UTRAN UE Positioning test case 6.2.3.4                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140320 | 0038 | -       | Addition of UTRAN UE Positioning test case 6.2.3.5                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140433 | 0039 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.3.4s                                                | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140435 | 0040 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.4.4s                                                | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | RP-140825 | 0041 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140086 | 0029 | -       | Addition of EUTRA UE Positioning test case 7.2.1.1                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140088 | 0030 | -       | Addition of EUTRA UE Positioning test case 7.2.1.2                                                              | 10.5.0 | 10.6.0 |
+| 2014-06        | RAN#64 | R5s140090 | 0031 | -       | Addition of EUTRA UE Positioning test case 7.2.1.3                                                              | 10.5.0 | 10.6.0 |
+| 2014-09        | RAN#65 | R5-144256 | 0042 | -       | Routine maintenance and updates                                                                                 | 10.6.0 | 10.7.0 |
+| 2014-12        | RAN#66 | R5s140739 | 0043 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.2.4s                                                | 10.7.0 | 10.8.0 |
+| 2014-12        | RAN#66 | R5s140777 | 0044 | -       | Usage of <MULTIPLE_CNF> in UpperTesterFunctions                                                                 | 10.7.0 | 10.8.0 |
+| 2014-12        | RAN#66 | RP-142067 | 0045 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.7.0 | 10.8.0 |
+| 2015-03        | RAN#67 | R5s141359 | 0047 | -       | Correction of errors in implementation of positioning CRs                                                       | 10.8.0 | 10.9.0 |
+| 2015-03        | RAN#67 | R5s150027 | 0048 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.1.4s                                                | 10.8.0 | 10.9.0 |
+| 2015-03        | RAN#67 | RP-150336 | 0049 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 10.8.0 | 10.9.0 |
+| 2015-03        | RAN#67 | -         | -    | -       | upgraded to Rel-11 with no change                                                                               | 10.9.0 | 11.0.0 |
+| 2015-03        | RAN#67 | R5-150735 | 0046 | -       | Addition of BeiDou Test Model                                                                                   | 11.0.0 | 12.0.0 |
+| 2015-06        | RAN#68 | RP-150897 | 0050 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150013 | 0051 | -       | Addition of UTRAN UE Positioning test case 6.2.3.2.4s                                                           | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150222 | 0052 | -       | Correction to POS ATS in TTCN-3 delivery 15wk10                                                                 | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150331 | 0053 | -       | Rel-12 baseline upgrade for POS Test Suite                                                                      | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150343 | 0054 | -       | Corrections to UTRAN UE Positioning functions                                                                   | 12.0.0 | 12.1.0 |
+
+| Change history |        |                         |      |         |                                                                                                                          |        |        |
+|----------------|--------|-------------------------|------|---------|--------------------------------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.                | CR   | Re<br>v | Subject/Comment                                                                                                          | Old    | New    |
+| 2015-06        | RAN#68 | R5s150344               | 0055 | -       | Correction to LTE UE Positioning test cases 7.3.5.1.5s and 7.5.1                                                         | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150345               | 0056 | -       | Correction to GLONASS LPP test cases                                                                                     | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150353               | 0057 | -       | Improvement of function f_POS_CheckGnssSupportList                                                                       | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150404               | 0058 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.3.1                                                            | 12.0.0 | 12.1.0 |
+| 2015-06        | RAN#68 | R5s150439               | 0059 | -       | Correction to selection of Assistance Data for sub-test 4                                                                | 12.0.0 | 12.1.0 |
+| 2015-09        | RAN#69 | RP-151421               | 0060 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A          | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | R5s150011               | 0061 | -       | Addition of UTRAN UE Positioning test case 6.2.1.1.4s                                                                    | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | R5s150589               | 0062 | -       | Correction to EUTRA Positioning functions                                                                                | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | R5s150590               | 0063 | -       | Correction to Upper Tester modules                                                                                       | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | R5s150706               | 0064 | -       | Addition of UTRAN UE Positioning test case 6.2.2.1.4s                                                                    | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | R5s150708               | 0065 | -       | Addition of UTRAN UE Positioning test case 6.2.2.3.4s                                                                    | 12.1.0 | 12.2.0 |
+| 2015-09        | RAN#69 | -                       | -    | -       | update of the "non-specific references" in section 2 according to the approved R5-153582 and an action point on ETSI MCC | 12.1.0 | 12.2.0 |
+| 2015-12        | RAN#70 | R5s150710               | 0068 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.2.7s                                                         | 12.2.0 | 12.3.0 |
+| 2015-12        | RAN#70 | R5s150712               | 0069 | -       | Addition of GCF WI-166 EUTRA UE Positioning test case 7.3.4.4.7s                                                         | 12.2.0 | 12.3.0 |
+| 2015-12        | RAN#70 | R5s150805               | 0070 | -       | Correction to POS capability check procedure                                                                             | 12.2.0 | 12.3.0 |
+| 2015-12        | RAN#70 | R5s150911               | 0071 | -       | Code improvements in Positioning test cases                                                                              | 12.2.0 | 12.3.0 |
+| 2015-12        | RAN#70 | RP-151697               | 0072 | -       | CR to 37.571-4: Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A          | 12.2.0 | 12.3.0 |
+| 2016-03        | RAN#71 | R5s151010               | 0073 | -       | Correction to POS type definition in ATS_15wk38                                                                          | 12.3.0 | 12.4.0 |
+| 2016-06        | RAN#72 | R5s160479               | 0074 | 1       | Correction to LTE Positioning test cases                                                                                 | 12.4.0 | 12.5.0 |
+| 2016-06        | RAN#72 | R5s160480               | 0075 | 1       | Correction to UTRA Positioning test cases                                                                                | 12.4.0 | 12.5.0 |
+| 2016-09        | RAN#73 | R5s160713               | 0076 | -       | Rel-13 baseline upgrade for POS Test Suite                                                                               | 12.5.0 | 13.0.0 |
+| 2016-12        | RAN#74 | -                       | -    | -       | updated to deliver latest TTCN                                                                                           | 13.0.0 | 13.1.0 |
+| 2017-03        | RAN#75 | R5-171531               | 0082 | -       | Indoor Positioning: Introduction of Test Model                                                                           | 13.1.0 | 13.2.0 |
+| 2017-03        | RAN#75 | R5s170127               | 0078 | 1       | Correction to GCF WI-166 EUTRA UE Positioning test case 7.3.4.4.7s                                                       | 13.1.0 | 13.2.0 |
+| 2017-03        | RAN#75 | R5s170128               | 0079 | 1       | Correction to function f_POS_CheckCapabilities() for OTDOA                                                               | 13.1.0 | 13.2.0 |
+| 2017-03        | RAN#75 | R5s170186/<br>RP-170104 | 0084 | -       | Update ASP changes due to inclusion of iPOS in 37.571-4 (prose), Annex D                                                 | 13.1.0 | 13.2.0 |
+| 2017-06        | RAN#76 | R5s170311               | 0085 | -       | Addition of LTE UE Positioning test case 7.3.4.1.10s                                                                     | 13.2.0 | 13.3.0 |
+| 2017-06        | RAN#76 | R5s170313               | 0086 | -       | Addition of LTE UE Positioning test case 7.3.4.3.10s                                                                     | 13.2.0 | 13.3.0 |
+| 2017-06        | RAN#76 | R5s170363               | 0087 | -       | Aligning name of PICS used in TTCN to the TS 37.571-3 definition                                                         | 13.2.0 | 13.3.0 |
+| 2017-06        | RAN#76 | R5s170383               | 0083 | 1       | Corrections to UE Positioning test cases                                                                                 | 13.2.0 | 13.3.0 |
+| 2017-06        | RAN#76 | R5s170416               | 0088 | -       | Update of TC list in 37.571-4 (prose), Annex A, due to merging of GNSS subtest                                           | 13.2.0 | 13.3.0 |
+
+| Change history |        |           |      |         |                                                                                 |        |        |
+|----------------|--------|-----------|------|---------|---------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Re<br>v | Subject/Comment                                                                 | Old    | New    |
+| 2017-09        | RAN#77 | R5s170630 | 0089 | 1       | Correction to function 'f_POS_CheckGnssSupportList'                             | 13.3.0 | 13.4.0 |
+| 2017-09        | RAN#77 | R5s170599 | 0090 |         | Rel-14 baseline upgrade for POS Test Suite                                      | 13.4.0 | 14.0.0 |
+| 2017-09        | RAN#77 | R5-173663 | 0091 | -       | Indoor Positioning Enhancements: Introduction of Test Model                     | 13.4.0 | 14.0.0 |
+| 2017-12        | RAN#78 | R5-176982 | 0093 | 1       | GNSS Test Model updates for V2X                                                 | 14.0.0 | 14.1.0 |
+| 2017-12        | RAN#78 | R5s170860 | 0092 | 1       | Correction to UE Positioning test case 7.3.1.1                                  | 14.0.0 | 14.1.0 |
+| 2018-03        | RAN#79 | R5-180677 | 0099 | -       | Routine maintenance for TS 37.571-4                                             | 14.1.0 | 14.2.0 |
+| 2018-03        | RAN#79 | R5s180081 | 0094 | 1       | Correction to EUTRA release information for UE Positioning TCs                  | 14.1.0 | 14.2.0 |
+| 2018-03        | RAN#79 | R5s180113 | 0095 | 1       | Addition of LTE UE Positioning test case 7.3.4.2.15s (BDS)                      | 14.1.0 | 14.2.0 |
+| 2018-03        | RAN#79 | R5s180114 | 0096 | 1       | Addition of LTE UE Positioning test case 7.3.4.4.15s (BDS)                      | 14.1.0 | 14.2.0 |
+| 2018-03        | RAN#79 | R5s180115 | 0097 | 1       | Addition of LTE UE Positioning test case 7.3.5.1.15s (BDS)                      | 14.1.0 | 14.2.0 |
+| 2018-06        | RAN#80 | R5-182292 | 0102 | -       | V2X: Test Model updates                                                         | 14.2.0 | 14.3.0 |
+| 2018-06        | RAN#80 | R5s180327 | 0101 | 1       | Correction / improvement to UE Positioning TCs 7.2.2.1 + 7.2.2.2                | 14.2.0 | 14.3.0 |
+| 2018-12        | RAN#82 | R5s180569 | 0105 | -       | Correction to number of almanac elements for Galileo                            | 14.3.0 | 14.4.0 |
+| 2018-12        | RAN#82 | R5s180554 | 0103 | -       | Rel-15 Sep'18 baseline upgrade for POS Test Suite                               | 14.4.0 | 15.0.0 |
+| 2019-03        | RAN#83 | R5s190056 | 0106 | -       | Correction to checking LPP ePDU capabilities                                    | 15.0.0 | 15.1.0 |
+| 2019-09        | RAN#85 | R5-197174 | 0111 | 1       | UE Positioning over NR: Initial Test Model                                      | 15.1.0 | 15.2.0 |
+| 2019-09        | RAN#85 | R5s190462 | 0109 | -       | Correction to f_POS_CheckCapabilities_Agnss                                     | 15.1.0 | 15.2.0 |
+| 2019-09        | RAN#85 | R5s190463 | 0110 | -       | Correction to f_POS_CheckGnssSupportList                                        | 15.1.0 | 15.2.0 |
+| 2019-09        | RAN#85 | R5s190759 | 0112 | -       | Rel-15 Jun'19 partial baseline upgrade for POS TTCN-3 Test Suite                | 15.1.0 | 15.2.0 |
+| 2019-12        | RAN#86 | R5-198140 | 0113 | -       | Aerial Vehicles: Test Model addition                                            | 15.2.0 | 15.3.0 |
+| 2019-12        | RAN#86 | R5-198142 | 0114 | -       | UE Positioning over NR: Test Model updates                                      | 15.2.0 | 15.3.0 |
+| 2019-12        | RAN#86 | R5-198156 | 0115 | -       | Routine maintenance for TS 37.571-4                                             | 15.2.0 | 15.3.0 |
+| 2019-12        | RAN#86 | R5s191048 | 0116 | -       | Correction to the initialisation function for LTE Positioning test cases        | 15.2.0 | 15.3.0 |
+| 2020-03        | RAN#87 | R5-200261 | 0118 | -       | Routine maintenance for TS 37.571-4                                             | 15.3.0 | 15.4.0 |
+| 2020-03        | RAN#87 | R5-200262 | 0119 | -       | Editorial changes to TS 37.571-X titles to remove references to individual RATs | 15.3.0 | 15.4.0 |
+| 2020-06        | RAN#88 | R5s200581 | 0120 | -       | Correction to f_POS_CheckGnssSupportList                                        | 15.4.0 | 15.5.0 |
+| 2020-12        | RAN#90 | R5s201391 | 0122 | -       | Addition of 5G UE Positioning test case 9.3.1.1                                 | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201393 | 0123 | -       | Addition of 5G UE Positioning test case 9.3.1.2.15s                             | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201395 | 0124 | -       | Addition of 5G UE Positioning test case 9.3.2.1                                 | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201397 | 0125 | -       | Addition of 5G UE Positioning test case 9.3.2.2                                 | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201399 | 0126 | -       | Addition of 5G UE Positioning test case 9.3.2.3                                 | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201401 | 0127 | -       | Addition of 5G UE Positioning test case 9.3.4.1.15s                             | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201403 | 0128 | -       | Addition of 5G UE Positioning test case 9.3.4.2.15s                             | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201405 | 0129 | -       | Addition of 5G UE Positioning test case 9.3.4.3.15s                             | 15.5.0 | 15.6.0 |
+
+| Change history |        |           |      |         |                                                                                                 |        |        |
+|----------------|--------|-----------|------|---------|-------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Re<br>v | Subject/Comment                                                                                 | Old    | New    |
+| 2020-12        | RAN#90 | R5s201407 | 0130 | -       | Addition of 5G UE Positioning test case 9.3.4.4.15s                                             | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201460 | 0131 | -       | Correction to several NR5GC UE Positioning Test related functions                               | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201529 | 0132 | -       | Correction to function f_POS_NR_SendLppAck()                                                    | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201649 | 0134 | -       | Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 15.5.0 | 15.6.0 |
+| 2020-12        | RAN#90 | R5s201388 | 0121 | -       | Rel-16 Sep'20 baseline upgrade for POS Test Suite                                               | 15.6.0 | 16.0.0 |
+| 2021-03        | RAN#91 | R5s210208 | 0133 | 1       | Correction to function f_POS_NR_CheckAgnssMultiFreq                                             | 16.0.0 | 16.1.0 |
+| 2021-03        | RAN#91 | R5s210262 | 0135 | 1       | Correction to a NR5GC UE Positioning related function                                           | 16.0.0 | 16.1.0 |
+| 2021-06        | RAN#92 | R5-212285 | 0138 | -       | Routine maintenance for TS 37.571-4                                                             | 16.1.0 | 16.2.0 |
+| 2021-06        | RAN#92 | R5s210416 | 0136 | -       | Correction for common POS function f_POS_SelectTemplateReq_IonosphModel()                       | 16.1.0 | 16.2.0 |
+| 2021-09        | RAN#93 | R5-214729 | 0143 | -       | Routine maintenance for TS 37.571-4                                                             | 16.2.0 | 16.3.0 |
+| 2021-09        | RAN#93 | R5s210887 | 0144 | -       | Correction to NR5GC Positioning Functions                                                       | 16.2.0 | 16.3.0 |
+| 2021-09        | RAN#93 | R5s210922 | 0141 | 1       | Correction for multi frequency GNSS support checking                                            | 16.2.0 | 16.3.0 |
+| 2021-09        | RAN#93 | R5s210926 | 0142 | 1       | Addition of NR5GC Positioning test case 9.3.1.2.5s                                              | 16.2.0 | 16.3.0 |
+| 2021-09        | RAN#93 | R5s211177 | 0145 | -       | Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 16.2.0 | 16.3.0 |
+| 2021-12        | RAN#94 | R5-216658 | 0149 | -       | NR Positioning: Test Model addition                                                             | 16.3.0 | 16.4.0 |
+| 2021-12        | RAN#94 | R5-217256 | 0151 | -       | Include new pixit for the 2012 GNSS scenarios                                                   | 16.3.0 | 16.4.0 |
+| 2021-12        | RAN#94 | R5s211307 | 0147 | -       | Correction to POS_Parameters                                                                    | 16.3.0 | 16.4.0 |
+| 2021-12        | RAN#94 | R5s211515 | 0148 | -       | Correction to f_POS_OTDOA_CheckEutraBand                                                        | 16.3.0 | 16.4.0 |
+| 2021-12        | RAN#94 | R5s211696 | 0153 | -       | Add new ASP definitions for NR test model extension in Rel-16                                   | 16.3.0 | 16.4.0 |
+| 2022-03        | RAN#95 | R5-220457 | 0156 | -       | 5G V2X: GNSS Test Model updates for NR sidelink                                                 | 16.4.0 | 16.5.0 |
+| 2022-03        | RAN#95 | R5s220170 | 0152 | 1       | Correction to NR5GC_Positioning_Functions for capability check                                  | 16.4.0 | 16.5.0 |
+| 2022-03        | RAN#95 | R5s220432 | 0154 | 1       | Correction to f_POS_NR_CheckCapabilities_NR_Ecid                                                | 16.4.0 | 16.5.0 |
+| 2022-03        | RAN#95 | R5s220433 | 0155 | 1       | Correction to SVIDs for 2012 GNSS scenario                                                      | 16.4.0 | 16.5.0 |
+| 2022-03        | RAN#95 | R5s220439 | 0158 | -       | Update of TTCN type definitions, Annex D                                                        | 16.4.0 | 16.5.0 |
+| 2022-06        | RAN#96 | R5s220671 | 0159 | -       | Correction to f_UT_AT_CheckNotifyLocationRequest                                                | 16.5.0 | 16.6.0 |
+| 2022-06        | RAN#96 | R5s220672 | 0160 | -       | Correction to f_POS_NR_Set_DIPrsPeriodicityAndOffset_11ms                                       | 16.5.0 | 16.6.0 |
+| 2022-09        | RAN#97 | R5s220765 | 0163 | -       | Correction to function f_TC_7_3_4_2_7s_EUTRA                                                    | 16.6.0 | 16.7.0 |
+| 2022-09        | RAN#97 | R5s220799 | 0164 | -       | Correction to f_TC_7_3_4_4_7s_EUTRA                                                             | 16.6.0 | 16.7.0 |
+| 2022-09        | RAN#97 | R5s220900 | 0162 | 1       | Addition of LTE POS testcase 7.2.2.2.5s                                                         | 16.6.0 | 16.7.0 |
+| 2022-09        | RAN#97 | R5s221026 | 0165 | -       | Rel-16 Mar'22 partial baseline upgrade for POS Test Suite                                       | 16.6.0 | 16.7.0 |
+| 2022-09        | RAN#97 | R5s221073 | 0173 | -       | Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 16.6.0 | 16.7.0 |
+| 2022-12        | RAN#98 | R5s221296 | 0166 | 1       | Correction to f_POS_NR_CheckCapabilities_Prs_ProcessingCapabilityBandList                       | 16.7.0 | 16.8.0 |
+| 2022-12        | RAN#98 | R5s221350 | 0168 | 1       | Addition of POS testcase 9.3.1.2.19s                                                            | 16.7.0 | 16.8.0 |
+
+| Change history |        |           |      |     |                                                                                                 |        |        |
+|----------------|--------|-----------|------|-----|-------------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #  | TSG Doc.  | CR   | Rev | Subject/Comment                                                                                 | Old    | New    |
+| 2022-12        | RAN#98 | R5s221351 | 0169 | 1   | Addition of POS testcase 9.3.4.2.19s                                                            | 16.7.0 | 16.8.0 |
+| 2022-12        | RAN#98 | R5s221352 | 0170 | 1   | Addition of POS testcase 9.3.4.2.20s                                                            | 16.7.0 | 16.8.0 |
+| 2022-12        | RAN#98 | R5s221353 | 0171 | 1   | Addition of POS testcase 9.3.4.2.21s                                                            | 16.7.0 | 16.8.0 |
+| 2022-12        | RAN#98 | R5s221354 | 0172 | 1   | Addition of POS testcase 9.3.4.2.22s                                                            | 16.7.0 | 16.8.0 |
+| 2022-12        | RAN#98 | R5s221363 | 0175 | -   | Add new verified and e-mail agreed TTCN test cases in the TC lists in 37.571-4 (prose), Annex A | 16.7.0 | 16.8.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37716-33/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37716-33/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b2958bf61075bb383f5af6e2c6993aa18522590
--- /dev/null
+++ b/marked/Rel-16/37_series/37716-33/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:527d74c84ec4e45948f8a99ef919d5b1a39ef1b712ca7e8c1ce6c1b7e99f1165
+size 9459
diff --git a/marked/Rel-16/37_series/37716-33/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37716-33/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c15ab7705056d3e9d5e1e1b358e629749fed507
--- /dev/null
+++ b/marked/Rel-16/37_series/37716-33/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27666b047b5afdf03d07b5da4c2c85e22cde38adb309d2ca7f866b6000d379bf
+size 5793
diff --git a/marked/Rel-16/37_series/37716-33/raw.md b/marked/Rel-16/37_series/37716-33/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcebd2905ccfad3421116e632d3ad38ce3a1bc6f
--- /dev/null
+++ b/marked/Rel-16/37_series/37716-33/raw.md
@@ -0,0 +1,613 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "G" has a red signal wave icon at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Content
+
+|                                                                              |    |
+|------------------------------------------------------------------------------|----|
+| Content .....                                                                | 3  |
+| Foreword .....                                                               | 4  |
+| 1 Scope.....                                                                 | 4  |
+| 2 References.....                                                            | 5  |
+| 3 Definitions, symbols and abbreviations.....                                | 5  |
+| 3.1 Definitions.....                                                         | 5  |
+| 3.2 Symbols.....                                                             | 6  |
+| 3.3 Abbreviations .....                                                      | 6  |
+| 4 Background .....                                                           | 6  |
+| 4.1 TR Maintenance.....                                                      | 6  |
+| 5 EN-DC with 3 bands DL and 3 bands UL: General Part.....                    | 6  |
+| 5.1 General treatment of $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....     | 6  |
+| 5.2 Maximum Sensitivity Degradation (MSD) analysis .....                     | 7  |
+| 6 EN-DC with 3 bands DL and 3 bands UL: Specific Band Combination Part ..... | 8  |
+| 6.1 Inter-band EN-DC with LTE 1 band+NR 2 bands(including FR2).....          | 8  |
+| 6.1.1 DC_66_n5-n260.....                                                     | 8  |
+| 6.1.1.1 Operating bands for DC_66_n5-n260 .....                              | 8  |
+| 6.1.1.2 Configurations for DC_66_n5-n260.....                                | 9  |
+| 6.1.1.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 9  |
+| 6.1.2 DC_66_n5-n261 .....                                                    | 10 |
+| 6.1.2.1 Operating bands for DC_66_n5-n261 .....                              | 10 |
+| 6.1.2.2 Configuration for DC_66_n5-n261 .....                                | 10 |
+| 6.1.2.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 10 |
+| 6.1.2.4 REFSENS requirements .....                                           | 11 |
+| 6.1.3 DC_3_n79-n258.....                                                     | 11 |
+| 6.1.3.1 Operating bands for DC_3_n79-n258 .....                              | 11 |
+| 6.1.3.2 Configurations for DC_3_n79-n258.....                                | 11 |
+| 6.1.3.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 11 |
+| 6.1.3.4 REFSENS requirements .....                                           | 12 |
+| 6.1.4 DC_21_n77-n257.....                                                    | 12 |
+| 6.1.4.1 Operating bands for DC_21_n77-n257 .....                             | 12 |
+| 6.1.4.2 Configurations for DC_21_n77-n257.....                               | 12 |
+| 6.1.4.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 12 |
+| 6.1.4.4 REFSENS requirements .....                                           | 13 |
+| 6.1.5 DC_21_n78-n257.....                                                    | 13 |
+| 6.1.5.1 Operating bands for DC_21_n78-n257 .....                             | 13 |
+| 6.1.5.2 Configurations for DC_21_n78-n257.....                               | 13 |
+| 6.1.5.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 13 |
+| 6.1.5.4 REFSENS requirements .....                                           | 14 |
+| 6.1.6 DC_21_n79-n257.....                                                    | 14 |
+| 6.1.6.1 Operating bands for DC_21_n79-n257 .....                             | 14 |
+| 6.1.6.2 Configurations for DC_21_n79-n257.....                               | 14 |
+| 6.1.6.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values.....                      | 14 |
+| 6.1.6.4 REFSENS requirements .....                                           | 14 |
+| 6.2 Inter-band EN-DC with LTE 2 bands+NR 1 band(including FR2).....          | 16 |
+| 6.2.x DC_X-Y-nZ.....                                                         | 16 |
+| Annex A: Change history .....                                                | 17 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document is a technical report for Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL under Rel-16 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL for the Rel-16 band combinations, where:
+
+- For only 1 NR band included, only NR FR2 band is applied
+- For only 2 NR bands included, 1 NR FR1 band and 1 NR FR2 band are included and operated as inter-band CA
+
+**Table 1-1: Release 16 Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL (1 NR band)**
+
+| DC combination | Uplink EN-DC configuration |
+|----------------|----------------------------|
+|                |                            |
+|                |                            |
+|                |                            |
+|                |                            |
+|                |                            |
+
+Table 1-2: Release 16 Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL(2 NR bands)
+
+| DC combination   | Uplink EN-DC configuration                                                       |
+|------------------|----------------------------------------------------------------------------------|
+| DC 3 n79-n258    | DC 3A n79A-n258A                                                                 |
+| DC_66_n5-n260    | DC_66A-n5A-n260A                                                                 |
+| DC_66_n5-n261    | DC_66A_n5A-n261A                                                                 |
+| DC_21_n77-n257   | DC_21A_n77A-n257A<br>DC_21A_n77A-n257G<br>DC_21A_n77A-n257H<br>DC_21A_n77A-n257I |
+| DC_21_n78-n257   | DC_21A_n78A-n257A<br>DC_21A_n78A-n257G<br>DC_21A_n78A-n257H<br>DC_21A_n78A-n257I |
+| DC_21_n79-n257   | DC_21A_n79A-n257A<br>DC_21A_n79A-n257G<br>DC_21A_n79A-n257H<br>DC_21A_n79A-n257I |
+| DC_3A_n40A-n258A | DC_3A_n40A-n258A                                                                 |
+
+This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [3] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
+- [4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                   |                                                                                                                  |
+|-------------------|------------------------------------------------------------------------------------------------------------------|
+| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for CA or DC operation, for serving cell $c$ .           |
+| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for CA or DC operation, for serving cell $c$ . |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Background
+
+The present document is a technical report for Dual Connectivity (EN-DC) with 3 bands DL and 3 bands UL under Rel-16 time frame. It covers both the UE and BS side. The document is divided in two different parts:
+
+- General part: this part covers BS and UE specific which is band combination independent.
+- Specific band combination part: this part covers each band combination and its specific issues independently from each other (i.e. one subclause is defined per band combination)
+
+The specific band combination parts are independent and therefore, the working speed also differs.
+
+## 4.1 TR Maintenance
+
+A single company is responsible for introducing all approved TPs in the current TR, i.e. TR editor. However, it is the responsibility of the contact person of each band combination to ensure that the TPs related to the band combination have been implemented.
+
+# --- 5 EN-DC with 3 bands DL and 3 bands UL: General Part
+
+## 5.1 General treatment of $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For the 3 bands DL and 3 bands UL EN-DC band combination, RAN4 should consider to reuse agreed additional insertion losses for all EN-DC band combinations when new RF components are not introduced to support this basket WI. If the new RF components are introduced, then more detail description will be captured in some specific EN-DC band combinations.
+
+In the 3 bands DL and 3 bands UL EN-DC combination, at least one NR FR2 band is included, which means the other two bands can be LTE 2 bands or LTE 1 band + NR 1 FR1 band. It shall be noted that the inter-band EN-DC combination with all the 3UL FR1 bands is excluded since the corresponding RF requirements have not been finished yet.
+
+Unless otherwise stated, for inter-band 3 bands DL and 3 bands UL EN-DC configurations including FR2, there are no additional requirements of  $\Delta T_{IB}$  and  $\Delta R_{IB}$  values for NR FR2 band, which means  $\Delta T_{IB}$  and  $\Delta R_{IB}$  for constituent FR2 NR bands is set to zero.
+
+For Inter-band EN-DC with LTE 2 band+NR 1 band (i.e. NR 1 FR2 band):
+
+- $\Delta T_{IB,c}$  and  $\Delta R_{IB,c}$  for constituent E-UTRA bands is the same as those for the corresponding E-UTRA inter-band CA configuration specified in TS 36.101.
+
+For Inter-band EN-DC with LTE 1 band+NR 2 bands (i.e. NR 1 FR1 band + NR 1 FR2 band):
+
+- $\Delta T_{IB,c}$  and  $\Delta R_{IB,c}$  for E-UTRA and FR1 NR band is the same as those for the corresponding inter-band EN-DC combinations specified in TS 38.101-3.
+
+## 5.2 Maximum Sensitivity Degradation (MSD) analysis
+
+### 5.2.1 MSD caused by Harmonic product
+
+The harmonic product analysis for the inter-band EN-DC combination within FR1 and including FR2 have been captured in the TRs, such as TR 37.716-11-11 and 37.716-21-11. Considering:
+
+- the frequency between E-UTRA band and NR FR2 band are very large, and the NR FR2 band frequency is larger than 3<sup>rd</sup> harmonic frequencies (even 7<sup>th</sup> harmonic frequencies) of all E-UTRA band, which means the NR FR2 band will not be impacted by the harmonic products of the E-UTRA band.
+- the NR FR2 band frequency is larger than 3<sup>rd</sup> harmonic frequencies of all NR FR1 band, which means the NR FR2 band will not be impacted by the 3<sup>rd</sup> harmonic products of the NR FR1 band.
+
+Therefore, unless otherwise stated, for inter-band 3 bands DL and 3 bands UL EN-DC configurations including FR2, there are no MSD requirements caused by harmonic products for constituent FR2 NR band, and MSD caused by harmonic products for constituent E-UTRA and NR FR1 bands are the same as those for the corresponding E-UTRA inter-band CA in TS36.101 or inter band EN-DC configuration without the FR2 bands in TS38.101-3, respectively.
+
+### 5.2.2 MSD caused by intermodulation products
+
+There are two types intermodulation frequencies for 3 bands UL configuration, the first one is choosing desirable UL band configurations for each use scenarios (i.e. 2UL intermodulation frequencies), and the second one is all the possible intermodulation frequencies occur while all three UL's are active concurrently (i.e. 3UL intermodulation frequencies).
+
+For the first type intermodulation frequencies, the study for 2UL intermodulation frequencies have been captured in TR 37.716-21-11 and TR 37.716-21-21, especially for the 2UL band configuration of E-UTRA band and NR FR1 band. It is no need to recalculate the 2UL frequencies intermodulation products for inter-band 3 bands DL and 3 bands EN-DC combinations.
+
+For the second type intermodulation frequencies, on top of 2UL intermodulation frequencies, some additional intermodulation frequencies shall be studied for all three UL frequencies are active concurrently for inter-band 3UL EN-DC combination, which is shown in Table 5.2.2-1.
+
+**Table 5.2.2-1. intermodulation frequencies all three UL frequencies are active concurrently**
+
+| Intermodulation #           | IMD3                                                                     | IMD4                                                                                                                                                                                                                 | IMD5                                                                                                                                                                                                                                                                                                                                                                                                                             |
+|-----------------------------|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Intermodulation frequencies | $ F_1+F_2+F_3 $<br>$ F_1+F_2-F_3 $<br>$ F_1-F_2+F_3 $<br>$ F_1-F_2-F_3 $ | $ 2F_1+F_2+F_3 ,  2F_1+F_2-F_3 $<br>$ 2F_1-F_2+F_3 ,  2F_1-F_2-F_3 $<br>$ F_1+2F_2+F_3 ,  F_1+2F_2-F_3 $<br>$ F_1-2F_2+F_3 ,  F_1-2F_2-F_3 $<br>$ F_1+F_2+2F_3 ,  F_1+F_2-2F_3 $<br>$ F_1-F_2+2F_3 ,  F_1-F_2-2F_3 $ | $ 3F_1+F_2+F_3 ,  3F_1+F_2-F_3 ,  3F_1-F_2+F_3 ,  3F_1-F_2-F_3 $<br>$ F_1+3F_2+F_3 ,  F_1+3F_2-F_3 ,  F_1-3F_2+F_3 ,  F_1-3F_2-F_3 $<br>$ F_1+F_2+3F_3 ,  F_1+F_2-3F_3 ,  F_1-F_2+3F_3 ,  F_1-F_2-3F_3 $<br>$ 2F_1+2F_2+F_3 ,  2F_1+2F_2-F_3 ,  2F_1-2F_2+F_3 ,  2F_1-2F_2-F_3 $<br>$ F_1+2F_2+2F_3 ,  F_1+2F_2-2F_3 ,  F_1-2F_2+2F_3 ,  F_1-2F_2-2F_3 $<br>$ 2F_1+F_2+2F_3 ,  2F_1+F_2-2F_3 ,  2F_1-F_2+2F_3 ,  2F_1-F_2-2F_3 $ |
+
+Considering the larger frequency difference between FR1 band and FR2 band, it can be foreseen that the IMDs product caused by FR1 band and FR2 band will not fall into its own Rx band. Hence, it is no need to calculate the IMDs product in table 5.2.2-1 for inter-band EN-DC combinations including FR2 band.
+
+Therefore, unless otherwise stated, for inter-band 3 bands DL and 3 bands UL EN-DC configurations including FR2, there are no MSD requirements caused by intermodulation products for constituent FR2 NR band, and MSD caused by
+
+intermodulation products caused by harmonic products for constituent E-UTRA and NR FR1 bands are the same as those for the corresponding E-UTRA inter-band CA in TS36.101 or inter band EN-DC configuration without the FR2 bands in TS38.101-3.
+
+## 5.3 Spurious emission band UE co-existence
+
+Unless otherwise stated, for inter-band 3 bands DL and 3 bands UL EN-DC configurations including FR2, there are no additional requirements of spurious emission band UE co-existence.
+
+For Inter-band EN-DC with LTE 2 band+NR 1 band (i.e. NR 1 FR2 band):
+
+- For spurious emission band UE co-existence, no requirements for FR2 NR bands to protect E-UTRA bands are applied to the constituent FR2 NR bands. Spurious emission band UE co-existence requirements specified in TS 36.101 are applied to the constituent E-UTRA bands..
+
+For Inter-band EN-DC with LTE 1 band+NR 2 bands (i.e. NR 1 FR1 band + NR 1 FR2 band):
+
+- Spurious emission band UE co-existence requirements for constituent E-UTRA and FR1 NR bands for the inter-band EN-DC are the same as those for the corresponding EN-DC configuration without the FR2 bands specified in TS38.101-3.
+
+# 6 EN-DC with 3 bands DL and 3 bands UL:Specific Band Combination Part
+
+## 6.1 Inter-band EN-DC with LTE 1 band+NR 2 bands(including FR2)
+
+### 6.1.1 DC\_66\_n5-n260
+
+#### 6.1.1.1 Operating bands for DC\_66\_n5-n260
+
+**Table 6.1.1.1-1: Band combinations for DC\_66\_n5-n260**
+
+| EN_DC Band    | E-UTRA Band | NR Band  |
+|---------------|-------------|----------|
+| DC_66_n5-n260 | 66          | n5, n260 |
+
+#### 6.1.1.2 Configurations for DC\_66\_n5-n260
+
+Table 6.1.1.2-1: Inter-band EN-DC configurations for DC\_66\_n5-n260
+
+| EN_DC Configuration                                                                                                                                                                                                                                                                                                                        | Uplink EN_DC Configuration |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| DC_66A_n5A-n260G<br>DC_66A_n5A-n260H<br>DC_66A_n5A-n260I<br>DC_66A_n5A-n260J<br>DC_66A_n5A-n260K<br>DC_66A_n5A-n260L<br>DC_66A_n5A-n260M                                                                                                                                                                                                   | DC_66A-n5A-n260A           |
+| DC_66A_n5A-n260(2A)<br>DC_66A_n5A-n260(3A)<br>DC_66A_n5A-n260(4A)<br>DC_66A_n5A-n260(5A)<br>DC_66A_n5A-n260(6A)<br>DC_66A_n5A-n260(2H)<br>DC_66A_n5A-n260(2G)<br>DC_66A_n5A-n260(A-2G)<br>DC_66A_n5A-n260(A-H)<br>DC_66A_n5A-n260(A-G)<br>DC_66A_n5A-n260(G-H)<br>DC_66A_n5A-n260(2A-G)<br>DC_66A_n5A-n260(2A-2G)<br>DC_66A_n5A-n260(3A-G) | DC_66A-n5A-n260A           |
+
+#### 6.1.1.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_66A\_n5A-n260A, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB,c}$  values are given in the tables below.
+
+Table 6.1.1.3-1:  $\Delta T_{IB,c}$
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_66_n5-n260               | 66                 | 0.3                    |
+|                             | n5                 | 0.3                    |
+|                             | n260               | 0                      |
+
+Table 6.1.1.3-2:  $\Delta R_{IB,c}$
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_66_n5-n260               | 66                 | 0                    |
+|                             | n5                 | 0                    |
+|                             | n260               | 0                    |
+
+#### 6.1.1.4 REFSENS requirements
+
+No additional MSD is required for DC\_66\_n5-n260
+
+### 6.1.2 DC\_66\_n5-n261
+
+#### 6.1.2.1 Operating bands for DC\_66\_n5-n261
+
+Table 6.1.2.1-1: Band combinations for DC\_66\_n5-n261
+
+| EN_DC Band    | E-UTRA Band | NR Band  |
+|---------------|-------------|----------|
+| DC_66_n5-n261 | 66          | n5, n261 |
+
+#### 6.1.2.2 Configuration for DC\_66\_n5-n261
+
+Table 6.1.2.2-1: Inter-band DC\_66\_n5-n261 configurations
+
+| EN_DC Configuration                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Uplink EN_DC Configuration |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
+| DC_66A_n5A-n261A<br>DC_66A_n5A-n261G<br>DC_66A_n5A-n261H<br>DC_66A_n5A-n261I<br>DC_66A_n5A-n261J<br>DC_66A_n5A-n261K<br>DC_66A_n5A-n261L<br>DC_66A_n5A-n261M                                                                                                                                                                                                                                                                                                                                      | DC_66A_n5A-n261A           |
+| DC_66A_n5A-n261(2A)<br>DC_66A_n5A-n261(3A)<br>DC_66A_n5A-n261(2G)<br>DC_66A_n5A-n261(2H)<br>DC_66A_n5A-n261(A-G)<br>DC_66A_n5A-n261(A-H)<br>DC_66A_n5A-n261(A-I)<br>DC_66A_n5A-n261(A-J)<br>DC_66A_n5A-n261(A-K)<br>DC_66A_n5A-n261(G-H)<br>DC_66A_n5A-n261(G-I)<br>DC_66A_n5A-n261(G-J)<br>DC_66A_n5A-n261(H-I)<br>DC_66A_n5A-n261(A-2G)<br>DC_66A_n5A-n261(A-G-H)<br>DC_66A_n5A-n261(A-G-I)<br>DC_66A_n5A-n261(2A-G)<br>DC_66A_n5A-n261(2A-H)<br>DC_66A_n5A-n261(2A-I)<br>DC_66A_n5A-n261(3A-G) | DC_66A_n5A-n261A           |
+
+#### 6.1.2.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_66A\_n5A-n261A, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB,c}$  values are given in the tables below.
+
+Table 6.1.2.3-1:  $\Delta T_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_66_n5-n261               | 66                 | 0.3                    |
+|                             | n5                 | 0.3                    |
+|                             | n261               | 0                      |
+
+Table 6.1.2.3-2:  $\Delta R_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_66_n5-n261               | 66                 | 0                    |
+|                             | n5                 | 0                    |
+|                             | n261               | 0                    |
+
+#### 6.1.2.4 REFSENS requirements
+
+No additional MSD is required for DC\_66\_n5-n261
+
+### 6.1.3 DC\_3\_n79-n258
+
+#### 6.1.3.1 Operating bands for DC\_3\_n79-n258
+
+Table 6.1.3.1-1: Band combinations EN-DC (three bands)
+
+| EN-DC Band    | E-UTRA Band | NR Band   |
+|---------------|-------------|-----------|
+| DC_3_n79-n258 | 3           | n79, n258 |
+
+#### 6.1.3.2 Configurations for DC\_3\_n79-n258
+
+Table 6.1.3.2-1: Inter-band EN-DC configurations (three bands)
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_3A_n79A-n258A    | DC_3A_n79A-n258A           |
+| DC_3A_n79A-n258D    |                            |
+| DC_3A_n79A-n258E    |                            |
+| DC_3A_n79A-n258F    |                            |
+| DC_3A_n79A-n258G    |                            |
+| DC_3A_n79A-n258H    |                            |
+| DC_3A_n79A-n258I    |                            |
+| DC_3A_n79A-n258J    |                            |
+| DC_3A_n79A-n258K    |                            |
+| DC_3A_n79A-n258L    |                            |
+
+#### 6.1.3.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_3\_n79-n258, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB}$  values are given in the tables below.
+
+Table 6.x.4-2:  $\Delta T_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_3_n79-n258               | 3                  | 0                      |
+|                             | n79                | 0                      |
+|                             | n258               | 0                      |
+
+Table 6.x.4-2:  $\Delta R_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_3_n79-n258               | 3                  | 0                    |
+|                             | n79                | 0                    |
+|                             | n258               | 0                    |
+
+#### 6.1.3.4 REFSENS requirements
+
+There are no additional MSD issue need to be specified.
+
+### 6.1.4 DC\_21\_n77-n257
+
+#### 6.1.4.1 Operating bands for DC\_21\_n77-n257
+
+Table 6.1.4.1-1: Band combinations EN-DC (three bands)
+
+| EN-DC Band     | E-UTRA Band | NR Band   |
+|----------------|-------------|-----------|
+| DC_21_n77-n257 | 21          | n77, n257 |
+
+#### 6.1.4.2 Configurations for DC\_21\_n77-n257
+
+Table 6.1.4.2-1: Inter-band EN-DC configurations (three bands)
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_21A_n77A-n257A   | DC_21A_n77A-n257A          |
+| DC_21A_n77A-n257G   | DC_21A_n77A-n257G          |
+| DC_21A_n77A-n257H   | DC_21A_n77A-n257H          |
+| DC_21A_n77A-n257I   | DC_21A_n77A-n257I          |
+
+#### 6.1.4.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_21\_n77-n257, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB}$  values are given in the tables below.
+
+Table 6.1.4.3-1:  $\Delta T_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_21_n77-n257              | 21                 | 0.4                    |
+|                             | n77                | 0.8                    |
+|                             | n257               | 0                      |
+
+Table 6.1.4.3-2:  $\Delta R_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_21_n77-n257              | 21                 | 0                    |
+|                             | n77                | 0.5                  |
+|                             | n257               | 0                    |
+
+#### 6.1.4.4 REFSSENS requirements
+
+Based on co-existence studies of the fallback band combinations EN-DC of LTE + NR FR1 and EN-DC of LTE + NR FR2 there is no additional harmonic and intermodulation impact for the proposed band combinations.
+
+### 6.1.5 DC\_21\_n78-n257
+
+#### 6.1.5.1 Operating bands for DC\_21\_n78-n257
+
+Table 6.1.5.1-1: Band combinations EN-DC (three bands)
+
+| EN-DC Band     | E-UTRA Band | NR Band   |
+|----------------|-------------|-----------|
+| DC_21_n78-n257 | 21          | n78, n257 |
+
+#### 6.1.5.2 Configurations for DC\_21\_n78-n257
+
+Table 6.1.5.2-1: Inter-band EN-DC configurations (three bands)
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_21A_n78A-n257A   | DC_21A_n78A-n257A          |
+| DC_21A_n78A-n257G   | DC_21A_n78A-n257G          |
+| DC_21A_n78A-n257H   | DC_21A_n78A-n257H          |
+| DC_21A_n78A-n257I   | DC_21A_n78A-n257I          |
+
+#### 6.1.5.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_21\_n78-n257, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB}$  values are given in the tables below.
+
+Table 6.1.5.3-1:  $\Delta T_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_21_n78-n257              | 21                 | 0.4                    |
+|                             | n78                | 0.8                    |
+|                             | n257               | 0                      |
+
+Table 6.1.5.3-2:  $\Delta R_{IB,c}$ 
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_21_n78-n257              | 21                 | 0                    |
+|                             | n78                | 0.5                  |
+|                             | n257               | 0                    |
+
+#### 6.1.5.4 REFSENS requirements
+
+Based on co-existence studies of the fallback band combinations EN-DC of LTE + NR FR1 and EN-DC of LTE + NR FR2 there is no additional harmonic and intermodulation impact for the proposed band combinations.
+
+### 6.1.6 DC\_21\_n79-n257
+
+#### 6.1.6.1 Operating bands for DC\_21\_n79-n257
+
+**Table 6.1.6.1-1: Band combinations EN-DC (three bands)**
+
+| EN-DC Band     | E-UTRA Band | NR Band   |
+|----------------|-------------|-----------|
+| DC_21_n79-n257 | 21          | n79, n257 |
+
+#### 6.1.6.2 Configurations for DC\_21\_n79-n257
+
+**Table 6.1.6.2-1: Inter-band EN-DC configurations (three bands)**
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_21A_n79A-n257A   | DC_21A_n79A-n257A          |
+| DC_21A_n79A-n257G   | DC_21A_n79A-n257G          |
+| DC_21A_n79A-n257H   | DC_21A_n79A-n257H          |
+| DC_21A_n79A-n257I   | DC_21A_n79A-n257I          |
+
+#### 6.1.6.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_21\_n79-n257, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB}$  values are given in the tables below.
+
+**Table 6.1.6.3-1:  $\Delta T_{IB,c}$**
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_21_n79-n257              | 21                 | 0                      |
+|                             | n79                | 0                      |
+|                             | n257               | 0                      |
+
+**Table 6.1.6.3-2:  $\Delta R_{IB,c}$**
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_21_n79-n257              | 21                 | 0                    |
+|                             | n79                | 0                    |
+|                             | n257               | 0                    |
+
+#### 6.1.6.4 REFSENS requirements
+
+Based on co-existence studies of the fallback band combinations EN-DC of LTE + NR FR1 and EN-DC of LTE + NR FR2 there is no additional harmonic and intermodulation impact for the proposed band combinations.
+
+### 6.1.7 DC\_3\_n40-n258
+
+#### 6.1.7.1 Operating bands for DC\_3\_n40-n258
+
+**Table 6.1.7.1-1: Band combinations EN-DC (three bands)**
+
+| EN-DC Band    | E-UTRA Band | NR Band   |
+|---------------|-------------|-----------|
+| DC_3_n40-n258 | 3           | n40, n258 |
+
+#### 6.1.7.2 Configurations for DC\_3\_n40-n258
+
+**Table 6.1.7.2-1: Inter-band EN-DC configurations (three bands)**
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_3A_n40A-n258A    | DC_3A_n40A-n258A           |
+
+#### 6.1.7.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+For DC\_3\_n10-n258, the  $\Delta T_{IB,c}$  and  $\Delta R_{IB}$  values are given in the tables below.
+
+**Table 6.1.7.4-2:  $\Delta T_{IB,c}$**
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta T_{IB,c}$ [dB] |
+|-----------------------------|--------------------|------------------------|
+| DC_3_n40-n258               | 3                  | 0.5                    |
+|                             | n40                | 0.5                    |
+|                             | n258               | 0                      |
+
+**Table 6.1.7.4-2:  $\Delta R_{IB,c}$**
+
+| Inter-band DC Configuration | E-UTRA and NR Band | $\Delta R_{IB}$ [dB] |
+|-----------------------------|--------------------|----------------------|
+| DC_3_n40-n258               | 3                  | 0                    |
+|                             | n40                | 0                    |
+|                             | n258               | 0                    |
+
+#### 6.1.7.4 REFSSENS requirements
+
+There are no additional MSD issue need to be specified.
+
+## 6.2 Inter-band EN-DC with LTE 2 bands+NR 1 band(including FR2)
+
+### 6.2.x DC\_X-Y-nZ
+
+#### 6.2.x.1 Operating bands for DC\_X-Y\_nZ
+
+Table 6.2.x.1-1: Band combinations EN-DC (three bands)
+
+| EN-DC Band | E-UTRA Band | NR Band |
+|------------|-------------|---------|
+|            |             |         |
+
+#### 6.2.x.2 Configurations for DC\_X-Y\_nZ
+
+Table 6.2.x.2-1: Inter-band EN-DC configurations (three bands)
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+|                     |                            |
+
+#### 6.2.x.3 $\Delta T_{IB}$ and $\Delta R_{IB}$ values
+
+#### 6.2.x.4 REFSENS requirements
+
+# Annex A: Change history
+
+| Change history |              |            |    |     |     |                                                                                                                                                                                                                                                                                                                                     |             |
+|----------------|--------------|------------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc       | CR | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                                     | New version |
+| 2019-08        | RAN4#92      | R4-1908551 |    |     |     | TR skeleton                                                                                                                                                                                                                                                                                                                         | 0.0.1       |
+| 2019-10        | RAN4#93      | R4-1913631 |    |     |     | Implemented TP's from RAN4 #92bis:<br>1. TP for TR 37.716-33: DC_66A_n5A-n260 and DC_66A_n5A-n261, Qualcomm Incorporated<br>2., R4-1911252 TP for TR 37.716-33_DC_3A_n79A-n258A,ZTE Corporation                                                                                                                                     | 0.1.0       |
+| 2020-04        | RAN4-94bis-e | R4-2003803 |    |     |     | Implemented TP's from RAN4 #94-e:<br>1. R4-2000477 TP for TR 37.716-33: DC_3A_n79A-n258,ZTE Corporation<br>2. R4-2001124,TP for DC_21_n77-n257 for TR 37.716-33,NTT DOCOMO, INC<br>3. R4-2001125, TP for DC_21_n78-n257 for TR 37.716-33, NTT DOCOMO, INC<br>4. R4-2001126, ,TP for DC_21_n79-n257 for TR 37.716-33,NTT DOCOMO, INC | 0.2.0       |
+| 2020-05        | RAN4-95-e    | R4-2007015 |    |     |     | Implemented TP's from RAN4 #95-e:<br>1. R4-2007015, TP for TR37.716-33_DC_3A_n40A-n258A, ZTE Corporation                                                                                                                                                                                                                            | 0.3.0       |
+| 2020-06        | RAN-88-e     | RP-200713  |    |     |     |                                                                                                                                                                                                                                                                                                                                     | 1.0.0       |
+
+| Change history |         |      |    |     |     |                                                        |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2020-06        | RAN#88  |      |    |     |     | Approved by plenary – Rel-16 spec under change control | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37815/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37815/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b4b75bf47d949c456e4c4beb04a9da643151080
--- /dev/null
+++ b/marked/Rel-16/37_series/37815/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:574011ae087e59abb672d9cf4e3f7bf8f63478f0528e1f232946036ceb7e1510
+size 8194
diff --git a/marked/Rel-16/37_series/37815/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37815/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26fd53abef53f6006c18b37e7980ad7d9fc921af
--- /dev/null
+++ b/marked/Rel-16/37_series/37815/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6c809a272a0875e9ab4896d0496e46dd775d4ff800da817a9e1c51203f5d3c05
+size 5792
diff --git a/marked/Rel-16/37_series/37815/raw.md b/marked/Rel-16/37_series/37815/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7e6d86f8e504126e9b08d64a4be846b0ea4ed5c4
--- /dev/null
+++ b/marked/Rel-16/37_series/37815/raw.md
@@ -0,0 +1,376 @@
+
+
+# 3GPP TR 37.815 V16.0.0 (2019-12)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Networks Study on high power User Equipment (UE) (power class 2) for E-UTRA (Evolved Universal Terrestrial Radio Access) - NR Dual Connectivity (EN-DC) (1 LTE FDD band + 1 NR TDD band) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon at its base.
+
+3GPP logo
+
+A GLOBAL INITIATIVE
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                      |           |
+|----------------------------------------------------------------------|-----------|
+| Foreword .....                                                       | 4         |
+| 1 Scope.....                                                         | 6         |
+| 2 References.....                                                    | 6         |
+| 3 Definitions, symbols and abbreviations .....                       | 6         |
+| 3.1 Definitions.....                                                 | 6         |
+| 3.2 Symbols.....                                                     | 6         |
+| 3.3 Abbreviations .....                                              | 7         |
+| 4 Background .....                                                   | 7         |
+| 4.1 Justification .....                                              | 7         |
+| 4.2 Objective .....                                                  | 7         |
+| 5 Power class definition for EN-DC .....                             | 8         |
+| 5.1 Power class.....                                                 | 8         |
+| 5.2 Power combination of the power class.....                        | 8         |
+| 6 Solutions for SAR Compliance.....                                  | 8         |
+| 6.1 General .....                                                    | 8         |
+| 6.2 Case1 of power class 2 .....                                     | 8         |
+| 6.2.1 Scheme 1 .....                                                 | 8         |
+| 6.2.2 Scheme 2 .....                                                 | 9         |
+| 6.2.3 Scheme 3 .....                                                 | 9         |
+| 6.3 Case2 of power class 2 .....                                     | 10        |
+| 6.3.1 Scheme 1 .....                                                 | 10        |
+| 6.3.2 Scheme 2 .....                                                 | 10        |
+| 6.3.3 Scheme 3 .....                                                 | 11        |
+| 7 Rx sensitivity degradation (if applicable) .....                   | 11        |
+| 8 specification impacts.....                                         | 11        |
+| 8.1 Impacts on RAN4 specifications.....                              | 11        |
+| 8.2 Impacts on specifications for the other WGs (if applicable)..... | 11        |
+| 9 Summary .....                                                      | 11        |
+| <b>Annex A: Change history .....</b>                                 | <b>13</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document is a technical report for high power UE(power class 2) for EN-DC(1 LTE FDD band + 1 NR TDD FDD). The purpose is to study how to introduce the new power class 2 (1 LTE FDD band + 1 NR TDD band) for EN-DC bands in Rel-16.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] RP-182895: " Study on high power UE (power class 2) for EN-DC (1 LTE FDD band + 1 NR TDD band)", China Unicom.
+- [3] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios".
+- [5] 3GPP TS 36.101: "E-UTRAN; User Equipment (UE) radio transmission and reception".
+- [6] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |               |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|           |               |
+|-----------|---------------|
+| <ACRONYM> | <Explanation> |
+|-----------|---------------|
+
+# 4 Background
+
+## 4.1 Justification
+
+In 3GPP, many operators and vendors have realized the significant benefit for increasing the UE transmits power. Now the HPUE for many bands in LTE, e.g., Band 38, Band 40, Band 41 and Band 42 have been completed. This results in significant improvement in UL coverage for these high bands.
+
+Meanwhile, the study of high power UE (HPUE) operation, i.e. power class 2, for NR Band n41, n77, n78 and n79 have been almost completed, motivated by significant benefits in cell coverage and cell edge user throughput that are needed for and can be achieved for NR related networks. Considering E-UTRA and NR need sharing the transmit power in the EN-DC mode, that means the EN-DC UL coverage will be less than NR Standalone and LTE only. This WID will focus on introduce high power UE for EN-DC (1 LTE FDD band + 1 NR TDD band) to the UL coverage of EN-DC networks.
+
+Many issues related to HPUE are common across different combinations. Following the similar approach adopted for LTE TDD HPUE in RAN4, this study item is to study how to introduce power class 2 for EN-DC for 1 LTE FDD band + 1 NR TDD band in Rel-16.
+
+## 4.2 Objective
+
+The objectives of the SI are as follows:
+
+- Study how to introduce the new power class 2 (1 LTE FDD band + 1 NR TDD band) for EN-DC bands in Rel-16
+- Study and define the power class for EN-DC under different power combination such as 23dBm LTE FDD+23dBm NR, 23dBm LTE FDD+26dBm NR in table 4.2-1.
+
+• **Table 4.2-1: Example of power class definition**
+
+| Case number | EN-DC total power | LTE maximum power | NR maximum power |
+|-------------|-------------------|-------------------|------------------|
+| Case 1      | 26dBm             | 23dBm             | 23dBm            |
+| Case 2      | 26dBm             | 23dBm             | 26dBm            |
+
+NOTE1: for case 1 and case 2, the duty cycles of NR TDD can be different.  
+NOTE2: RAN4 study starts from case 1, but case 2 is not precluded.
+
+- Study and define applicable scheme (UE Tx duty cycle) to prevent exceeding local regulatory limits such as SAR
+- The example band combination for this study is DC\_3A\_n78n.
+
+# 5 Power class definition for EN-DC
+
+## 5.1 Power class
+
+For EN-DC with 1 LTE FDD band and 1 NR TDD band, UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1ms). For the example band combination DC\_3A\_n78A, the maximum output power can be specified as in Table 5.1-1.
+
+• **Table 5.1-1: Maximum output power for EN-DC**
+
+| DC configuration                                                                                                                                                                                                                                                             | Power class 2 (dBm) | Tolerance (dB)     | Power class 3 (dBm) | Tolerance (dB)     |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|--------------------|---------------------|--------------------|
+| DC_3A_n78A                                                                                                                                                                                                                                                                   | 26                  | +2/-3 <sup>1</sup> | 23                  | +2/-3 <sup>1</sup> |
+| NOTE 1: refers to the transmission bandwidths confined within F <sub>UL_low</sub> and F <sub>UL_low</sub> + 4 MHz or F <sub>UL_high</sub> – 4 MHz and F <sub>UL_high</sub> , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB |                     |                    |                     |                    |
+| NOTE 2: P <sub>PowerClass_EN-DC</sub> is the maximum UE power specified without taking into account the tolerance                                                                                                                                                            |                     |                    |                     |                    |
+| NOTE 3: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE).                                                                                                                                 |                     |                    |                     |                    |
+
+## 5.2 Power combination of the power class
+
+As stated in clause 4.2, two power combinations are studied i.e.
+
+Case1: LTE FDD power class 3 (23dBm), NR TDD power class 3 (23dBm) and EN-DC power class 2 (26dBm)
+
+Case2: LTE FDD power class 3 (23dBm), NR TDD power class 2 (26dBm) and EN-DC power class 2 (26dBm)
+
+Unless otherwise stated, requirements written in TS 36.101-1 [5] and TS 38.101-1 [3] apply for LTE and NR transmitters respectively.
+
+# 6 Solutions for SAR Compliance
+
+## 6.1 General
+
+To accommodate the SAR limits of the PC2 FDD-TDD High Power UE, a combined UE-based and network-based solution is considered in the study phase. In the network-based solution, there will be a threshold based on the duty cycle and power settings of LTE and NR, the PC2 UE is assumed to be capable of maintaining the PC2 power if the network setting or scheduling does not exceed the threshold. In addition to the network based solution, a UE based solution based on the autonomous UE maximum power back off mechanism, i.e., P-MPR, can further allow the UE to ensure SAR compliance. For the network-based solution following different schemes were discussed in the SI.
+
+## 6.2 Case1 of power class 2
+
+### 6.2.1 Scheme 1
+
+The following equation is applied between the LTE UL duty cycle, NR UL duty cycle and the overall duty threshold.
+
+$$\text{Duty}_{\text{LTE}} * (P_{\text{LTE}} / P_{26}) + \text{Duty}_{\text{NR}} * (P_{\text{NR}} / P_{26}) \leq \text{Duty threshold} \quad \dots(1)$$
+
+P<sub>LTE</sub>, P<sub>NR</sub>, P<sub>26</sub> represent the maximum linear power (mW) of LTE, NR, and EN-DC power class 2 respectively; Duty<sub>LTE</sub>, Duty<sub>NR</sub> represent the maximum uplink percentage of LTE, NR respectively. Duty threshold represents the maximum UL duty cycle that can maintain the PC2 power class for FDD+TDD EN-DC HPUE.
+
+In the case 1 of power class 2 FDD-TDD EN-DC UE, the maximum uplink power of LTE and NR are both 23dBm. By setting the P<sub>LTE</sub>, P<sub>NR</sub> to be 23dBm, equation (1) can be simplified to the following equation.
+
+$$\text{Duty}_{\text{LTE}} + \text{Duty}_{\text{NR}} \leq \text{Duty threshold} \quad \dots(2)$$
+
+Duty<sub>NR</sub>, the uplink percentage of the NR TDD part is determined by scheduling. Duty<sub>LTE</sub>, the maximum uplink percentage of the LTE FDD, can be set up by TDM pattern or determined by scheduling. The maximum uplink percentage of LTE FDD might be adjusted in order to keep the PC2 power.
+
+The PC2 case 1 UE is allowed to fallback to PC3 if the LTE uplink scheduling or the TDM pattern setting of the LTE UL, together with the scheduled NR uplink duty cycle exceeds the duty threshold based on the equation (2).
+
+### 6.2.2 Scheme 2
+
+Specific LTE reference configurations are defined for FDD-TDD EN-DC HPUE duty cycle capability reporting. The reported capability is maximal NR UL duty which can fulfil SAR limits when assuming LTE FDD side being configured as the defined reference configurations with the maximum UL power.
+
+For case 1, the LTE reference configuration can be  $\text{Duty}_{\text{LTE}}=70\%$ . The default value of NR UL duty capability can be 30% i.e. " $\text{Duty}_{\text{LTE}}=70\%$  and  $\text{P}_{\text{LTE}}=23\text{dBm}$ ", corresponding to default  $\text{Duty}_{\text{NR}}=30\%$ ,  $\text{P}_{\text{NR}}=23\text{dBm}$ .
+
+Higher  $\text{Duty}_{\text{NR}}$  value can be reported as the UE capability e.g.  $\text{maxNRDuty}$ . If the scheduled traffic fulfils  $\text{Duty}_{\text{LTE}}<70\%$  and  $\text{Duty}_{\text{NR}}< \text{maxNRDuty}$ , UE can maintain PC2 power.
+
+For better flexibility, two LTE configurations are supported. Based on the two LTE configurations  $\{\text{Duty}_{\text{LTE}1}, \text{Duty}_{\text{LTE}2}\}$ , UE optimizes its SAR compliance capability and reports two  $\text{Duty}_{\text{NR}}$  separately, e.g.  $\{\text{maxNRDuty}1, \text{maxNRDuty}2\}$ .
+
+### 6.2.3 Scheme 3
+
+To address an issue that the impact of each of the uplink bands on SAR is different, scheme 3 is proposed to consider that aspect in an equation to derive SAR ration effect for each of the RATs as follows:
+
+$$\text{UplinkDutyCycle}_{\text{LTE}} * (\text{P}_{\text{LTE}}/\text{P}_{\text{PowerClass, EN-DC}}) * \text{Ratio}_{\text{effect}} + \text{UplinkDutyCycle}_{\text{NR}} * (\text{P}_{\text{NR}}/\text{P}_{\text{PowerClass, EN-DC}}) \leq \text{maxUplinkDutyCycle-EN-DC};$$
+
+Where;
+
+- $\text{maxUplinkDutyCycle-EN-DC}$  for FDD LTE + TDD NR is to be defined in TS 38.306 and that is the total  $\text{maxUplinkDutyCycle}$  of LTE FDD and NR TDD uplink. Note in LTE TDD + NR TDD, the value is only for NR TDD uplink.
+- $\text{UplinkDutyCycle}_{\text{LTE}}$  is the percentage of LTE FDD uplink symbols transmitted in a certain evaluation period;
+- $\text{UplinkDutyCycle}_{\text{NR}}$  is the percentage of NR TDD uplink symbols transmitted in a certain evaluation period;
+- $\text{P}_{\text{PowerClass, EN-DC}}$  is defined in clause 6.2B.1.3 for inter-band EN-DC.  $\text{P}_{\text{PowerClass, EN-DC}}$  is the linear value of  $\text{P}_{\text{PowerClass, EN-DC}}$ ;
+- $\text{P}_{\text{LTE}}$  is the value given by the field *p-maxEUTRA-r15* of the *RRCConnectionReconfiguration-v1510* IE as defined in TS 38.331.  $\text{P}_{\text{LTE}}$  is the linear value of  $\text{P}_{\text{LTE}}$ ;
+- $\text{P}_{\text{NR}}$  is the value given by the field *p-NR-FR1* of the *PhysicalCellGroupConfig* IE as defined in TS 38.331.  $\text{P}_{\text{NR}}$  is the linear value of  $\text{P}_{\text{NR}}$ ;
+- $\text{Ratio}_{\text{effect}}$  is to be defined in TS 38.306 as coefficient taking into account electromagnetic energy absorption effect ratio of the LTE FDD band and the NR TDD band;
+
+The above equations would be able to consider the important aspects which should be considered while both are mutually exclusive relationships.
+
+The above equations would be able to consider the important aspects which should be considered while both are mutually exclusive relationships.
+
+From the performance aspect, it is better to introduce  $\text{Ratio}_{\text{effect}}$  in the equation to utilize the UE's ability. For example, it is assumed that a UE has imbalance of SAR effect such as  $\text{Ratio}_{\text{effect}}=2$ , that is SAR effect of NR band is 2 times as large as that of LTE band. In this case, if we do not capture  $\text{Ratio}_{\text{effect}}$  factor in the equation, UE is forced to report lower EN-DC total duty cycle than what it really has. That is, assuming one of boundary condition is such that  $\text{Duty}_{\text{LTE}}=100\%$  for LTE alone transmission and  $\text{Duty}_{\text{NR}}=50\%$  for NR alone transmission, and if we does not introduce  $\text{Ratio}_{\text{effect}}$ , UE are forced to report EN-DC total duty cycle as 50% to consider the worst case scenario although the UE has ability to transmit higher than 50% UL EN-DC duty cycle.
+
+On the other hands, the scheme 3 becomes meaningful only when  $\text{Ratio}_{\text{effect}}$  is within reasonable range. If the value in the equation is set to 20, which was mentioned by a certain company, LTE FDD uplink is almost not allowed. Given that  $\text{maxUplinkDutyCycle-EN-DC} = 100\%$  while LTE FDD (23dBm) + NR TDD (23dBm) are assumed. If NR TDD uplink duty cycle is 50% for instance, the LTE FDD uplink duty cycle is 2.5%. Even if NR TDD uplink duty cycle is 30%, still LTE FDD duty cycle is 3.5%. The impact on LTE TDD uplink duty cycle depends on the total maxuplink
+
+duty cycle. Hence, the range of  $\text{Ratio}_{\text{effect}}$  together with the total maxuplinkdutycycle for EN-DC if that is introduced should be discussed.
+
+## 6.3 Case2 of power class 2
+
+### 6.3.1 Scheme 1
+
+The following equation is applied between the LTE UL duty cycle, NR UL duty cycle and the overall duty threshold.
+
+$$\text{Duty}_{\text{LTE}} * (P_{\text{LTE}} / P_{26}) + \text{Duty}_{\text{NR}} * (P_{\text{NR}} / P_{26}) \leq \text{Duty threshold} \dots (1)$$
+
+$P_{\text{LTE}}$ ,  $P_{\text{NR}}$ ,  $P_{26}$  represent the maximum linear power (mW) of LTE, NR, and EN-DC power class 2 respectively;  $\text{Duty}_{\text{LTE}}$ ,  $\text{Duty}_{\text{NR}}$  represent the maximum uplink percentage of LTE, NR respectively. Duty threshold represents the maximum UL duty cycle that can maintain the PC2 power class for FDD+TDD EN-DC HPUE.
+
+In the case 2 of power class 2 FDD-TDD EN-DC UE, the maximum uplink power of LTE and NR are 23dBm and 26dBm respectively. By setting the  $P_{\text{LTE}}$ ,  $P_{\text{NR}}$  to be 23dBm and 26dBm, equation (1) can be simplified to the following equation. But note that in case 2 PC2 UE, the total maximum power of LTE and NR cannot exceed 26dBm when transmitting both LTE UL and NR UL at the same time.
+
+$$\text{Duty}_{\text{LTE}} + \text{Duty}_{\text{NR}} \leq \text{Duty threshold} \dots (2)$$
+
+As same as the scheme in clause 6.2.1,  $\text{Duty}_{\text{NR}}$  is determined by scheduling.  $\text{Duty}_{\text{LTE}}$  can be set up by TDM pattern or determined by scheduling.
+
+The PC2 case 2 UE is allowed to fallback to PC3 if the LTE uplink scheduling or the TDM pattern setting of the LTE UL, together with the scheduled NR uplink duty cycle exceeds the duty threshold based on the equation (2).
+
+### 6.3.2 Scheme 2
+
+Specific LTE reference configurations are defined for FDD-TDD EN-DC HPUE duty cycle capability reporting. The reported capability is maximal NR UL duty which can fulfil SAR limits when assuming LTE FDD side being configured as the defined reference configuration with the maximum UL power.
+
+For case 2, the LTE reference configuration can be  $\text{Duty}_{\text{LTE}}=40\%$ . The default value of NR UL duty capability can be 30% i.e. " $\text{Duty}_{\text{LTE}}=40\%$  and  $P_{\text{LTE}}=23\text{dBm}$ ", corresponding to default  $\text{Duty}_{\text{NR}}=30\%$ ,  $P_{\text{NR}}=26\text{dBm}$ .
+
+Higher  $\text{Duty}_{\text{NR}}$  value can be reported as the UE capability e.g.  $\text{maxNRDuty}$ . If the scheduled traffic fulfils  $\text{Duty}_{\text{LTE}} < 40\%$  and  $\text{Duty}_{\text{NR}} < \text{maxNRDuty}$ , UE can maintain PC2 power.
+
+For better flexibility, two LTE configurations are supported. Based on the two LTE configurations  $\{\text{Duty}_{\text{LTE}}1, \text{Duty}_{\text{LTE}}2\}$ , UE optimizes its SAR compliance capability and reports two  $\text{Duty}_{\text{NR}}$  separately, e.g.  $\{\text{maxNRDuty}1, \text{maxNRDuty}2\}$ .
+
+### 6.3.3 Scheme 3
+
+The equation is same as that described in clause 6.2.3 while  $P_{\text{LTE}}$  and  $P_{\text{NR}}$  is set according to Case2 in Table 4.2-1.
+
+# 7 Rx sensitivity degradation (if applicable)
+
+# 8 specification impacts
+
+## 8.1 Impacts on RAN4 specifications
+
+Required changes in UE RF specification TS 38.101-3 are shown in Table 8.1-1.
+
+**Table 8.1-1: Required changes in TS 38.101-3**
+
+| Clause     | Requirement                                                                                                        | Required changes in TS 38.101-3 compared to the same band combination for power class 3                                                                      |
+|------------|--------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 6.2B.1     | UE maximum output power for EN-DC                                                                                  | Add power class 2 for inter-band EN-DC. The additional details of power class for LTE and NR may be also needed                                              |
+| 6.2B.4.1.3 | Configured output power for inter-band EN-DC within FR1                                                            | It shall be verified whether the existing P <sub>cmax</sub> for inter-band EN-DC can be applied to HP UE. Some changes shall be needed to address SAR issue. |
+| 7.3B.2.3.1 | Reference sensitivity exceptions due to UL harmonic interference for EN-DC in NR FR1                               | No changes for case 1<br>No changes for case 2 considering the harmonic product of TDD band (high band) would not be possible to affect the lower FDD band.  |
+| 7.3B.2.3.2 | MSD due to receiver harmonic mixing for EN-DC in NR FR1                                                            | No changes for case 1<br>MSD value may need to be re-evaluated for case 2                                                                                    |
+| 7.3B.2.3.3 | Reference sensitivity exceptions due to close proximity of bands for EN-DC in NR FR1                               | No changes for case 1<br>MSD value may need to be re-evaluated for case 2                                                                                    |
+| 7.3B.2.3.4 | Reference sensitivity exceptions due to cross band isolation for EN-DC in NR FR1                                   | No changes for case 1<br>MSD value may need to be re-evaluated for case 2                                                                                    |
+| 7.3B.2.3.5 | Reference sensitivity exceptions for intermodulation interference due to dual uplink operation for EN-DC in NR FR1 | MSD value may need to be re-evaluated for case 1 and case 2                                                                                                  |
+
+## 8.2 Impacts on specifications for the other WGs (if applicable)
+
+# 9 Summary
+
+In this study item, different solutions which could facilitate Power Class 2 FDD-TDD EN-DC High Power UE to comply with applicable SAR requirement has been throughout studied, with considering the fact that two kinds of UE implementations could exist, i.e., UE implementation case 1 with power class 3 capability for both LTE and NR, and case 2 with power class 3 capability for LTE and power class 2 capability for NR.
+
+The scheme 1, 2, 3 provided in Clause 6 are UE capability reporting based solutions for SAR limitation compliance designed for PC2 FDD-TDD EN-DC HPUE. Particularly, the scheme 2 introduces the UE capability reporting containing the upper limit(s) for the configurable UL duty cycle for NR TDD carrier under the certain pre-defined LTE configuration(s) with upper limit(s) on the ratio of accumulated time allowed for UE maximum power transmission scheduling over the entire evaluation period. By comparing proposed schemes, RAN4 conclude that with introducing the mechanism in scheme 2, network can be indicated with the proper information to facilitate corresponding network configuration for PC2 FDD-TDD EN-DC HPUE with the applicable SAR limit compliance.
+
+During the study item, RAN4 identified that the scheme 2 shall be introduced for specific FDD+TDD EN-DC band combination(s), and RAN4 observed that detailed signalling design to enable scheme 2 shall have RAN2 specification impact.
+
+Meanwhile, RAN4 identified that network-configuration-based scheme in which the HPUE set its total EN-DC power based on higher-layer signalling could also provide the alternative methodology for PC2 FDD-TDD EN-DC HPUE SAR requirement compliance without explicit 3GPP specification impact and without need for signalling and cell-group coordination, while some concern raised for the resultant LTE coverage reduction, and for the applicable SAR limit compliance..
+
+# Annex A: Change history
+
+| Change history |         |            |    |     |     |                                                        |             |
+|----------------|---------|------------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc       | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2019-2         | RAN4#90 | R4-1900694 |    |     |     | Skeleton TR                                            | v0.0.1      |
+| 2019-12        | RAN#86  | RP-192798  |    |     |     | Version for approval to RAN                            | v1.0.0      |
+| 2019-12        | RAN#86  |            |    |     |     | Approved by plenary – Rel-16 spec under change control | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37816/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/37_series/37816/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48aa87310967a373b5aeafed814bcae44c861bbf
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6528a37db66234390adcf9fdfcd7067138f1f02eed6f36fec252056396c87936
+size 21094
diff --git a/marked/Rel-16/37_series/37816/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-16/37_series/37816/5478f70a6cef3e5672b2b22d28830cfb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a667cd74b49be7f88c683ff0e128a96270f6542e
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/5478f70a6cef3e5672b2b22d28830cfb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a1acaccbfa053c98206302502476cebc7bda76e4118b5d03e0d0156767506e39
+size 25554
diff --git a/marked/Rel-16/37_series/37816/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-16/37_series/37816/6e5a85131eedf6b98db62877ee64506e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c16a75dbd68c758f36c6f3efe4622ff95583dde0
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/6e5a85131eedf6b98db62877ee64506e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89a9c24541a9e0940303797bf7b89f40eabb78c18b85f4b6db0829b477ab1f0d
+size 38109
diff --git a/marked/Rel-16/37_series/37816/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/37_series/37816/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6ce0230d2d77c64c6db7d8c40d70056bb47ca58
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57f811728c2a4fa096b1ab05455c6672b854d728add8744bb9008423e88370f9
+size 21143
diff --git a/marked/Rel-16/37_series/37816/90d8516930bb8334d7898604aee1bb58_img.jpg b/marked/Rel-16/37_series/37816/90d8516930bb8334d7898604aee1bb58_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8811f8f77101b837bddf57a293fcab7563e42869
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/90d8516930bb8334d7898604aee1bb58_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94c6d26baafedb64eac2e1c507678af48fa2da89bcd206639b71bb2a4278d0e4
+size 21043
diff --git a/marked/Rel-16/37_series/37816/raw.md b/marked/Rel-16/37_series/37816/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a398fff77afd0c23588e5baa41d972b104711b93
--- /dev/null
+++ b/marked/Rel-16/37_series/37816/raw.md
@@ -0,0 +1,1183 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                 |    |
+|---------------------------------------------------------------------------------|----|
+| Introduction .....                                                              | 5  |
+| 1 Scope.....                                                                    | 6  |
+| 2 References.....                                                               | 6  |
+| 3 Definitions of terms, symbols and abbreviations .....                         | 6  |
+| 3.1 Terms.....                                                                  | 6  |
+| 3.2 Symbols.....                                                                | 7  |
+| 3.3 Abbreviations .....                                                         | 7  |
+| 4 General.....                                                                  | 7  |
+| 5 Use cases and solutions for RAN-centric data collection and utilization ..... | 7  |
+| 5.1 Capacity and Coverage Optimization .....                                    | 7  |
+| 5.1.1 Use case description .....                                                | 7  |
+| 5.1.2 Solution description.....                                                 | 8  |
+| 5.1.2.1 Detection of Coverage and Capacity Issues .....                         | 8  |
+| 5.1.2.2 Possible actions to resolve detected issues .....                       | 9  |
+| 5.1.3 Conclusion.....                                                           | 10 |
+| 5.2 PCI selection .....                                                         | 10 |
+| 5.2.1 Use case description .....                                                | 10 |
+| 5.2.2 Solution description.....                                                 | 10 |
+| 5.2.3 Conclusion.....                                                           | 11 |
+| 5.3 Mobility optimization.....                                                  | 11 |
+| 5.3.1 Use case description .....                                                | 11 |
+| 5.3.2 Solution description.....                                                 | 12 |
+| 5.3.2.1 Connection failure due to mobility .....                                | 12 |
+| 5.3.2.2 Inter-system Unnecessary HO .....                                       | 14 |
+| 5.3.2.3 Inter-system HO ping-pong .....                                         | 15 |
+| 5.3.2.4 SN change failure in case of EN-DC, NGEN-DC, NE-DC and NR-DC.....       | 15 |
+| 5.3.2.5 Successful HO Report.....                                               | 16 |
+| 5.3.3 Conclusion.....                                                           | 17 |
+| 5.4 Load Sharing and Load Balancing Optimization .....                          | 17 |
+| 5.4.1 Use case description .....                                                | 17 |
+| 5.4.2 Solution description.....                                                 | 17 |
+| 5.4.3 Conclusion.....                                                           | 18 |
+| 5.5 RACH Optimization.....                                                      | 18 |
+| 5.5.1 Use case description .....                                                | 18 |
+| 5.5.2 Solution description.....                                                 | 19 |
+| 5.5.3 Conclusion.....                                                           | 20 |
+| 5.6 Energy Saving .....                                                         | 20 |
+| 5.6.1 Use case description .....                                                | 20 |
+| 5.6.2 Solution description.....                                                 | 21 |
+| 5.6.3 Conclusion.....                                                           | 21 |
+| 5.7 Minimization of Drive Test (MDT) Use Cases.....                             | 21 |
+| 5.7.1 General .....                                                             | 21 |
+| 5.7.2 Use case description .....                                                | 22 |
+| 5.7.2.1 Use case: Coverage Optimization via MDT .....                           | 22 |
+| 5.7.2.2 Use case: QoS verification via MDT .....                                | 22 |
+| 5.7.2.3 Use case: Indoor MDT improvement .....                                  | 22 |
+| 5.7.2.4 Use case: Sensor data collection.....                                   | 23 |
+| 5.7.3 Solution description.....                                                 | 23 |
+| 5.7.3.1 Measurements .....                                                      | 23 |
+| 5.7.3.2 MDT procedures .....                                                    | 23 |
+| 5.7.3.3 MDT activation in split RAN .....                                       | 25 |
+| 5.7.3.3.0 General .....                                                         | 25 |
+| 5.7.3.3.1 Signalling activation.....                                            | 25 |
+| 5.7.3.3.2 Management activation .....                                           | 25 |
+| 5.7.3.4 MDT reporting in split RAN .....                                        | 26 |
+
+|           |                                                                                |    |
+|-----------|--------------------------------------------------------------------------------|----|
+| 5.7.3.5   | MDT for dual connectivity .....                                                | 26 |
+| 5.7.4     | Conclusion.....                                                                | 26 |
+| 5.8       | UE energy saving .....                                                         | 27 |
+| 5.8.1     | Use case description .....                                                     | 27 |
+| 5.8.2     | Solution description.....                                                      | 28 |
+| 5.8.3     | Conclusion.....                                                                | 28 |
+| 5.9       | Active Antenna System (AAS) Optimization .....                                 | 28 |
+| 5.9.1     | Use case description .....                                                     | 28 |
+| 5.9.2     | Solution description.....                                                      | 28 |
+| 5.9.3     | Conclusion.....                                                                | 28 |
+| 6         | Measurement quantities, events and faults for collection and utilization ..... | 28 |
+| 6.1       | General .....                                                                  | 28 |
+| 6.2       | Measurement quantities.....                                                    | 29 |
+| 6.2.1     | UE originated measurements.....                                                | 29 |
+| 6.2.2     | L2 measurement quantities.....                                                 | 29 |
+| 6.2.2.0   | General.....                                                                   | 29 |
+| 6.2.2.1   | L2 measurements in TS 28.552 .....                                             | 29 |
+| 6.2.2.2   | RAN part of packet delay measurement .....                                     | 32 |
+| 6.2.2.2.1 | UL packet delay measurement.....                                               | 33 |
+| 6.2.2.2.2 | DL packet delay measurement.....                                               | 33 |
+| 6.2.3     | L1 measurement quantities (e.g. Timing Advance in RAR).....                    | 33 |
+| 6.2.4     | Sensor data for UE orientation/altitude to log in addition to location.....    | 33 |
+| 6.3       | Events and faults .....                                                        | 34 |
+| 6.3.1     | RLF and access failure information.....                                        | 34 |
+| 6.4       | Conclusion.....                                                                | 34 |
+| 7         | Conclusion .....                                                               | 34 |
+| Annex A:  | Change history .....                                                           | 35 |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+A new SI "Study on RAN-centric data collection and utilization for LTE and NR" was approved for Release 16 at the 3GPP TSG RAN #80 meeting and updated in [2]. The study aims to investigate RAN-centric Data collection and utilization for NR and LTE.
+
+# --- 1 Scope
+
+The present document provides descriptions of use cases and solutions with regard to RAN-centric data collection and utilization and analysis of these solutions.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP RP-182105: "Revised SID: Study on RAN-centric data collection and utilization for LTE and NR".
+- [3] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
+- [4] 3GPP TS 28.552: "5G performance measurements".
+- [5] ETSI ES 203 228: "Environmental Engineering (EE); Assessment of mobile network energy efficiency".
+- [6] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
+- [7] 3GPP TR 38.913: "Study on scenarios and requirements for next generation access technologies".
+- [8] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements".
+- [9] 3GPP TS 38.463: "NG-RAN; E1 Application Protocol (E1AP)".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+Void.
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|     |                                  |
+|-----|----------------------------------|
+| AAS | Active Antenna System            |
+| ANR | Automatic Neighbour Relationship |
+
+|     |                                  |
+|-----|----------------------------------|
+| BFD | Beam Failure Detection           |
+| BFR | Beam Failure Recovery            |
+| MDT | Minimization of Drive Test       |
+| MLB | Mobility Load Balancing          |
+| MRO | Mobility Robustness Optimization |
+| PCI | Physical Cell Identifier         |
+| RLF | Radio Link Failure               |
+| RLM | Radio Link Monitoring            |
+| SON | Self-Optimizing Network          |
+
+# --- 4 General
+
+Void
+
+# --- 5 Use cases and solutions for RAN-centric data collection and utilization
+
+## 5.1 Capacity and Coverage Optimization
+
+### 5.1.1 Use case description
+
+Coverage and Capacity Optimization (CCO) is one of the typical operational tasks to optimize the radio access network (RAN). CCO has been identified as a key use case for SON since LTE, which aims to provide the required capacity in the targeted coverage areas and to minimize the interference and maintain an acceptable quality of service in an autonomous way. There is a trade-off between coverage and capacity optimization, capacity enhancements are usually at the expense of service coverage degradations, and vice versa. There is a need to balance and manage the trade-off between the two.
+
+CCO allows the system to periodically adapt to the changes in traffic (i.e. load and location) and the radio environment by automatically adjusting coverage for the cells that serve a certain area for a particular traffic situation. Due to the introduction of beam based antenna structures the set of configurable antenna and RF parameters are multi-dimensional. It is very complex to find the mapping between network configurations with target coverage and capacity performance. To make it feasible, some kind of machine learning techniques could be utilized which will leverage on the data collected in the RAN network. The collected data could be UE measurements, performance measurements, events and other monitoring information, also taking into account beamforming and massive MIMO - related information. These inputs could help the operator firstly identify the coverage and capacity problems, for instance, coverage hole, weak pilot pollution, overshoot coverage and DL and UL channel coverage mismatch and further perform the coverage and capacity optimization.
+
+Coverage holes with unbalanced DL and UL channel coverage require consideration. The concept of RLF reporting from UE to RAN node and corresponding analysis provide the means to identify coverage holes and separate them from mobility related RLF failures, but a more detailed analysis of the root cause of a coverage hole is needed for an efficient CCO algorithm to detect UL channel coverage holes. Providing knowledge about root cause of a coverage hole by more elaborated analysis in the RAN node can trigger the right countermeasures quicker and more reliably.
+
+Active Antenna Systems (AAS) will be deployed widely in NR as well. Therefore, dynamic coverage configuration change function similar to LTE would be supported in NR CCO.
+
+The use cases addressed by the CCO solution for NR can be classified as follows.
+
+#### Use case 1: Coverage problems
+
+This use case focuses on scenarios where the coverage of reference signals is sub-optimal, leaving the UE exposed to failures or degraded performance, e.g. when a coverage hole is found or where UL/DL disparity is encountered. It is worth noticing that MRO will take care of all types of failures due to wrong mobility settings within a network with good cell planning. That implies that CCO should address cases where the root cause of the problem is due to a bad coverage planning.
+
+#### Use Case 2: Capacity problems
+
+Within this class some cases were found where capacity within a cell or beam is saturated, resulting in one or more UEs being subject to failures or suboptimal performance. There are a number of reasons for such event, such as high demand of services which exceeds resources available in the cell/beam or poor radio conditions affecting a large share of served UEs (for example where a large number of UEs is at cell edge, causing high interference to other UEs and consuming large amounts of resources).
+
+It is worth noticing that MLB will take care of load distribution via mobility and that such mobility load balancing is done mainly in inter frequency scenarios, i.e. where cross cell interference is not an issue. That implies that CCO should address cases where the root cause of the problem is due to serving UEs at cell/beam edge, where the "edge" is between cells/beams utilising the same resources.
+
+### 5.1.2 Solution description
+
+Solutions for CCO are based on the capability to adapt cell/beam coverage to achieve better system performance. Solutions can be generalized as made of two components:
+
+- Detection of coverage and/or capacity issue
+- Action to resolve the issue
+
+Generally, there are two types of network coverage adjustment, i.e. long term cell RF parameters tuning and short term cell coverage switching among pre-configurations. The long term cell RF parameters tuning is usually hosted by OAM and relies on UE radio measurements, e.g. RSRP, RSRQ, call drops statistics, etc which collected by MDT or performance management function.
+
+The short term cell coverage switch is implemented by NG-RAN node. The dynamic cell coverage configuration change function will be support by exchanging the cell coverage change information between two neighbouring NG-RAN nodes, including Cell Coverage State, Cell Deployment Status Indicator, and Cell Replacing Info. The LTE mechanism can be taken as a baseline.
+
+#### 5.1.2.1 Detection of Coverage and Capacity Issues
+
+To detect coverage and capacity issues not only information about failure cases are needed but also information about successful events. For example, a sub-optimal coverage planning between neighbour cells may not always imply that UEs handing over between these cells are subject to RLFs. Nevertheless, the handover may be suboptimal and the UE may fail RACH access in the original target beam, while succeeding it in a different beam because there is a "gap" in coverage in the mobility area.
+
+An initial list of information that would be needed to the CCO function to detect coverage and capacity issues would be the following:
+
+- Per source cell/beam RS measurements from UEs:
+
+This is useful to understand the signal strength of the serving RS and to check whether the serving cell coverage is sufficiently good or not.
+
+- Per target(s) beam/cell RS measurement from UEs:
+
+This is useful to understand the signal strength of neighbour cells/beams, which are potential mobility targets. With this information it is possible to understand if the coverage of serving cell and that of neighbour cells have excessive/sufficient/insufficient overlap, e.g. it helps deducing if DL coverage holes are in place.
+
+- Information on failure events associated to source and target cells, e.g. UE measurements on source and target reference signals, e.g. SSBs, at the time of failure (likely included in RLF Reports).
+
+This information is evidence of either wrong mobility setting or of coverage issues. The CCO function should correlate this information with other UE measurements to understand whether the failure is symptom of bad coverage planning, in which case a CCO action is needed, or if the failure is purely the symptom of bad mobility setting, in which case CCO should not react and leave functions like MRO to react instead.
+
+##### - Information about RACH access:
+
+- Number of RACH attempts made by UEs per Beam/Cell ID of a serving cell and of a target cell.
+
+The RAN configures the UE to start RACH access for a given beam starting from a pre-set transmission power level and ramping up such power at every step, in a pre-set way. By knowing the number of RACH access attempts towards a beam the CCO function also knows the transmission power used by the UE per attempt and deduces potential UL coverage issues in case RACH does not succeed.
+
+- Information about successful/failed RACH access together with the cell/beam ID where the access was attempted.
+
+This information is essential to understand in which beams RACH access failed/succeeded. Together with number of attempts it helps building a map of UL coverage.
+
+- UE measurements of DL RS of the beam/cell where RACH access is attempted.
+
+This is needed to compare DL coverage vs UL coverage for a beam for which RACH access is attempted. Comparing this information with number of RACH attempts per beam and successful/failed RACH access per beam it is possible to understand if UL/DL coverage disparities exist.
+
+##### - Interference measurements on a per UE basis (RSRQ):
+
+- This information enables the CCO function to understand if UEs are subject to excessive interference. When used together with source and target RS measurement information it allows to understand whether UEs at cell border are subject to high interference. The CCO function at the RAN is also able to correlate this information with the resources utilized to serve cell edge UEs. The CCO function is therefore able to deliberate whether there is a need for cell/beam border change in order to ease the situation of capacity utilization and interference arising from UEs being served at cell/beam edge.
+
+##### - Cell load and other performance information from the target cell and the neighbour cells:
+
+- This information enables the CCO function to determine relative capacity situation between the target and the neighbour cells and e.g. identify potential candidate cells for coverage and capacity coordination.
+
+#### 5.1.2.2 Possible actions to resolve detected issues
+
+##### Solution 1:
+
+Once the CCO function has a good understanding of the coverage and capacity status of the cells/beams at its hosting RAN node and possibly at neighbouring nodes, the CCO function can trigger a corrective action to address such issue.
+
+For the disaggregated gNB scenario, the gNB-CU should provide relevant information to the gNB-DU, leaving to the gNB-DU freedom to address such problem.
+
+UL coverage optimization based on SUL may be supported by UE reporting of random-access (RA) attempts on SUL and NUL carriers. This may detect mismatch between rsrp-ThresholdSSB-SUL threshold and the actual SUL/NUL radio coverage, and the UE may report this to the network in order to re-configure the rsrp-ThresholdSSB-SUL threshold for better selection of SUL and NUL carriers by the UE.
+
+An inter RAN node signalling solution to coordinate changes of coverage amongst RAN nodes should be specified. For that, an index based solution such as the one in LTE could be adopted, or in general a solution based on RAN nodes learning the coverage configuration of neighbour nodes and adapting accordingly.
+
+##### Solution 2:
+
+In case that the CCO function is hosted at OAM, the OAM can trigger a corrective action to address the CCO issue.
+
+### 5.1.3 Conclusion
+
+RAN3 has concluded the analysis of the CCO function and agreed that solutions in line with the description in the above clause can be moved to normative phase.
+
+## 5.2 PCI selection
+
+### 5.2.1 Use case description
+
+Physical Cell Identifier (PCI) is assigned to each cell to help UE distinguish wireless signals of different cells. The selection of PCI is one of the first use cases that have been introduced in SON, in order to ensure that PCI collision does not happen or are minimized. In LTE, the eNB base the selection of its PCI either on a centralized or distributed PCI assignment algorithm. The centralized assignment works in a way that the eNB selects the specific PCI value sent to it by the OAM as its PCI, while the distributed PCI assignment is that the eNB selects a PCI value randomly from the restricted list of PCIs.
+
+In NR, ultra-dense network is the key technology to meet the demand of future mobile data traffic, and there will be coexistence of macro cell in lower frequency and small cells in higher frequency (mmwave) in a certain area. For the sake of improving energy efficiency, those small cells may switch to sleep mode at any time. Those various cell changes will lead to serious challenges in PCI allocation and selection.
+
+In NR, the PCI selection function should be applicable for split gNB architecture.
+
+The study on the solutions for PCI selection in NR could focus on:
+
+- 1) Definition of the information/data required to support PCI conflict discovery and selection.
+- 2) Functionalities and procedures to support PCI selection, e.g. report by UE or exchange over the X2/Xn/F1 interface
+- 3) PCI confusion resolution, without using CGI reading functionality (ANR).
+
+Solutions of PCI selection in LTE and the mechanisms that have been specified in NR Rel-15 specification should be the baseline. There is a need to first evaluate whether the existing mechanisms is sufficient for PCI selection on NR.
+
+### 5.2.2 Solution description
+
+The NG-RAN node (non-split) bases the selection of its PCI either on a centralized or distributed PCI assignment algorithm.
+
+In the split gNB architecture, there are several options for the PCI selection. A non-exhaustive list of possible option is reported below. Details about which option will be selected for normative specification will be provided during work item phase.
+
+#### **Case 1: centralized PCI selection, OAM assigns a single PCI to each NR cell**
+
+In this case, the OAM configures a single PCI value for NR cells in the DU. The DU sends the PCI of each serving cell to the CU during the F1 setup procedure.
+
+- Option 1a: CU detects PCI conflict and indicates to OAM via DU. OAM assigns a new PCI.
+
+In option 1, when the CU detects PCI conflict between NR cells within a DU or between neighbouring gNBs, it sends the PCI conflict indication to the DU. The DU reports the PCI conflict to the OAM. After that, the OAM will allocate a new PCI value for the DU.
+
+- Option 1b: CU detects PCI conflict and indicates to OAM directly. OAM assigns a new PCI.
+
+When the CU detects the PCI conflict between NR cells within a DU or between neighbouring gNBs, it sends the PCI conflict to OAM directly. And the OAM will allocate a new PCI value for the cell having PCI conflict and configure it to the DU.
+
+#### **Case 2: Distributed PCI selection, OAM configures a list of PCIs to each NR cell**
+
+In this case, the OAM signals a list of PCIs for each cell to the DU, and DU selects one from the list for each NR cell. The DU sends the selected PCI of each serving cell to the CU during F1 setup.
+
+- Option 2a: CU detects PCI conflict and indicates to DU. DU reassigns a new PCI.
+
+When the CU detects the PCI conflict, it sends the PCI conflict indication to the DU. In addition, the CU sends the PCIs of cells neighbouring to the cell subject to PCI update to the DU, or allowed PCIs, or non-allowed
+
+PCIs to the DU. The DU may restrict the PCI list considering the information suggested by CU. Based that, the DU reselects a new PCI value from the remaining list of the PCIs.
+
+- Option 2b: CU detects PCI conflict and reassigns a new PCI.
+
+When the CU detects the PCI conflict, the CU will select a new PCI value from the remaining list of the PCIs reported from the DU, and send the new PCI value to the DU in the gNB-CU configuration update procedure. This option needs the gNB-DU report the PCI list of each NR cell to the gNB-CU during F1 setup.
+
+### 5.2.3 Conclusion
+
+The following features and solutions are recommended to be specified for NR PCI selection function as part of a Rel.16 RAN-centric DCU WI:
+
+- Centralized PCI assignment and distributed PCI assignment for non-split gNB and split gNB.
+- The solution down-selection for split gNB case will be decided in normative phase.
+
+## 5.3 Mobility optimization
+
+### 5.3.1 Use case description
+
+In LTE, Mobility Robustness Optimization (MRO) aims at detecting and enabling correction of following problems, which will deteriorate user experience and waste network resources:
+
+- Connection failure due to intra-LTE or inter-RAT mobility;
+- Unnecessary HO to another RAT (too early IRAT HO with no radio link failure);
+- Inter-RAT ping-pong.
+
+For connection failure due to intra-LTE or inter-RAT mobility, three kinds of failures were identified: too late HO, too early HO and HO to a wrong cell. The detection of the events is enabled by the RLF Indication and HO Report procedures. By analysing the report from UE and network side information, HO related parameters could be adjusted to resolve the detected problems.
+
+For unnecessary HO to another RAT, the RAN node in the other RAT, may instruct the UE to continue to evaluate the received measurement reports with the coverage/quality condition received during the inter-RAT HO preparation phase and decide if an inter-RAT unnecessary HO report should be sent to the RAN node in the source RAT.
+
+For inter-RAT ping-pong, the statistics regarding ping-pong occurrence may be based on evaluation of the UE History Information IE in the HANDOVER REQUIRED message. If the evaluation indicates a potential ping-pong case and the source eNB of the 1<sup>st</sup> inter-RAT handover is different than the target eNB of the 2<sup>nd</sup> inter-RAT handover, the target eNB may use the HANDOVER REPORT message to indicate the occurrence of potential ping-pong cases to the source eNB.
+
+For NR, mobility optimization solution should also be introduced to detect and resolve the above problems. LTE should be taken as the baseline. Intra-system (5GS) intra/inter-RAT mobility and inter-system (5GS) inter-RAT mobility should be studied in the SI. Since new network architectures, e.g. MR-DC, CU-DU split, CP-UP separation and some new features, e.g. BWP, beam, etc, are introduced in NR, enhancements on the procedures and measurements are needed. For instance:
+
+- 1) New information or measurement is defined and collected, e.g. besides cell level measurements, related beam IDs and beam measurements, as well as SUL information are also included in the RLF report, and/or HO Report.
+- 2) Enhancement to F1/Xn/X2 to support mobility enhancement in CU/DU architecture, MR-DC.
+
+### 5.3.2 Solution description
+
+#### 5.3.2.1 Connection failure due to mobility
+
+##### 1) Connection failure due to intra-system mobility
+
+**Failure event definition:**
+
+- [Intra-system Too Late Handover] An RLF occurs after the UE has stayed for a long period of time in the cell; the UE attempts to re-establish the radio link connection in a different cell.
+- [Intra-system Too Early Handover] An RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell.
+- Intra-system Handover to Wrong Cell] An RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell and the target cell.
+
+###### **Detection mechanism:**
+
+- [Intra-system Too Late Handover]  
+There is no recent handover for the UE prior to the connection failure i.e. the UE reported timer is absent or larger than the configured threshold, e.g. Tstore\_UE\_cntxt.
+- [Intra-system Too Early Handover]  
+There is a recent handover for the UE prior to the connection failure i.e. the UE reported timer is smaller than the configured threshold, e.g. Tstore\_UE\_cntxt, and the first re-establishment attempt cell/the cell UE attempts to re-connect is the cell that served the UE at the last handover initialization.
+- [Intra-system Handover to Wrong Cell]
+
+There is a recent handover for the UE prior to the connection failure i.e. the UE reported timer is smaller than the configured threshold, e.g. Tstore\_UE\_cntxt, and the first re-establishment attempt cell/the cell UE attempts to re-connect is neither the cell that served the UE at the last handover initialization nor the cell that served the UE where the RLF happened or the cell that the handover was initialized toward.
+
+###### **Impact to Xn interface:**
+
+- Failure Indication message which is used to provide UE RLF Report from the NG-RAN node that collects the UE report to the last serving node.
+- HO Report message which is used to indicate the failure events in case of too early HO or handover to wrong cell.
+
+###### **Impact to NG interface:**
+
+In case the UE re-connects to a cell that has no Xn interface with the last serving NG-RAN node, the UE RLF Report could also be transferred in NG interface via NG-RAN Node Configuration update message.
+
+###### **Impact to UE:**
+
+To support MRO for NR, UE RLF report should also be supported in NR. The following information should be included in UE RLF Report:
+
+- The CGI of the last cell that served the UE (in case of RLF) or the target of the handover (in case of handover failure).
+- The CGI of the cell towards which the UE wants to initiate re-establishment attempt.
+- The CGI of the cell that served the UE at the last handover initialization.
+- Time elapsed since the last handover initialization until the RRC connection failure.
+- An indication whether the RRC connection failure was due to RLF or handover failure.
+- C-RNTI allocated for the UE in the last serving cell.
+- RLF trigger of the last RLF that was detected.
+- Time elapsed from the RRC connection failure till RLF Report signalling.
+- Handover type i.e. intra-system or inter-system handover should be included in both E-UTRAN and NR UE RLF Report.
+
+- The radio measurements and measurements configurations. These can be listed as follow (subject to RAN2 checking):
+  - Information related to the Radio-link monitoring (RLM) on serving cell (where the RLF is detected) and on target cell (in case of handover failure)
+  - Beam measurements on RLM related resources i.e. measurement on reference signals (RS) such as:
+    - SSB
+    - CSI-RS
+
+Measurements to be logged may be RSRP, RSRQ, SINR, Qout, Qin, etc.
+
+- Information related to the beam failure detection (BFD) on serving cell (where the RLF is detected) and on target cell (in case of handover failure)
+  - Beam measurements on BFD related resources i.e. measurement on reference signals (RS) such as:
+    - SSB
+    - CSI-RS
+
+Measurements to be logged may be at least RSRP, RSRQ, SINR, Qout, Qin, etc.
+
+Note that BFD and RLM resources may be different from each other.
+
+- Information related to the beam failure recovery (BFR) on the serving cell where the RLF happened and on target cell (in case of handover failure) including:
+  - Measurements performed on the list of the candidate beam-resources configured for BFR reason.
+  - Measurement on signals that were "not" listed in the candidate beam-resources list while the UE detects such signals with a quality above a certain beam suitability threshold.
+  - There measured signals can include:
+    - SSB
+    - CSI-RS
+
+Measurements to be logged may be at least RSRP, RSRQ, SINR.
+
+- Information on RRM measurements per beam on a serving cell (where RLF is detected) and on target cell (in case of handover failure)
+  - Beam level measurement for cell quality derivation
+  - Beam level measurement on at least one neighbour cell for cell quality derivation
+  - Beam level measurement on a cell the UE selects and performs reestablishment after RLF
+  - Measurement can be done on different RS types such as:
+    - SSB
+    - CSI-RS
+    - TRS, DMRS or any combination of these signals
+  - RACH related information:
+    - beam identity where RACH access was attempted during handover
+    - Number of RACH attempts for each RACH access attempt
+- Logging sensor data, including UE orientation/altitude to log in addition to location, speed and heading (e.g. digital compass, gyroscope as well as barometer, etc.).
+
+- UE speed state (low, mid, high) detected by UE as part of speed-based scaling procedure.
+
+To support MRO between gNB and ng-eNB, UE RLF Report could be provided via different RAT, i.e. NR RLF Report could be included in E-UTRAN UE ULInformationResponse message. Similarly, E-UTRAN RLF Report could also be included in NR ULInformationResponse message.
+
+##### 2) Connection failure due to inter-system mobility
+
+###### Failure events definition
+
+- [Inter-system/ Too Late Handover] An RLF occurs after the UE has stayed in a E-UTRAN cell which connects with 5GC for a long period of time; the UE attempts to re-establish to an E-UTRAN cell which connects with EPC.
+- [Inter-system/ Too Early Handover] An RLF occurs shortly after a successful handover from a E-UTRAN cell which connects with EPC to a target cell in a E-UTRAN cell which connects with 5GC; the UE attempts to re-establish to the source cell or to another E-UTRAN cell which connects with EPC.
+
+###### Detection mechanism
+
+- [Too Late Inter-system Handover]  
+The connection failure occurs while being connected to an NG-RAN cell, and there is no recent handover for the UE prior to the connection failure i.e. the UE reported timer is absent or larger than the configured threshold, e.g. Tstore\_UE\_cntxt, and the first cell where the UE attempts to re-connect/re-establish is a E-UTRAN cell which connect with EPC.
+- [Too Early Inter-system Handover]  
+The connection failure occurs while being connected to an NG-RAN cell, and there is a recent inter-system handover for the UE prior to the connection failure i.e. the UE reported timer is smaller than the configured threshold, e.g. Tstore\_UE\_cntxt, and the first cell where the UE attempts to re-connect/re-establish and the cell that served the UE at the last handover initialization are both E-UTRAN cell which connect with EPC.
+
+###### Impact to NG interface:
+
+- To support the above too early inter-system handover detections, the NG-RAN node receiving the RLF INDICATION message may inform the E-UTRAN node over NG.
+- The NG-RAN node receiving the RLF report could forward the report to the NG-RAN node that served the UE before the connection failure via Xn or NG interface.
+
+#### 5.3.2.2 Inter-system Unnecessary HO
+
+##### Failure events definition
+
+UE is handed over from NG-RAN to other system (e.g. UTRAN) even though quality of the NG-RAN coverage was sufficient for the service used by the UE. The handover may therefore be considered as unnecessary HO to another system (too early Inter-system HO without connection failure)
+
+##### Detection mechanism
+
+To be able to detect the Unnecessary HO to another system, an NG-RAN may choose to put additional coverage and quality condition information into the HANDOVER REQUIRED message in the Handover Preparation procedure when an inter-system HO from NG-RAN to another system occurs. The RAN node in the other system, upon receiving this additional coverage and quality information, may instruct the UE to continue measuring the source system (NG-RAN) during a period of time, while being connected to another system (e.g. E-UTRAN), and send periodic or single measurement reports to the other system (e.g. E-UTRAN). When the period of time indicated by the source system (NG-RAN) expires, the RAN node in the other system (e.g. E-UTRAN), may evaluate the received measurement reports with the coverage/quality condition received during the inter-system HO procedure and decide if an inter-system unnecessary HO report should be sent to the RAN node in the source RAT (NG-RAN).
+
+##### Impact to NG/S1 interface:
+
+An inter-system unnecessary HO report should be sent from LTE system to the NR system.
+
+#### 5.3.2.3 Inter-system HO ping-pong
+
+##### Failure events definition
+
+A UE is handed over from a cell in a source system (e.g. NG-RAN) to a cell in a target system different from the source system (e.g. E-UTRAN), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient for the service used by the UE. The event may occur more than once.
+
+##### Detection mechanism
+
+The statistics regarding ping-pong occurrence may be based on evaluation of the *UE History Information* IE in the HANDOVER REQUIRED message. If the evaluation indicates a potential ping-pong case and the source NG-RAN node of the 1<sup>st</sup> inter-system handover is different than the target NG-RAN node of the 2<sup>nd</sup> inter-system handover, the target NG-RAN node may use the HANDOVER REPORT message to indicate the occurrence of potential ping-pong cases to the source NG-RAN node.
+
+##### Impact to Xn interface:
+
+HO Report message which is used to indicate the inter-system ping-pong event.
+
+#### 5.3.2.4 SN change failure in case of EN-DC, NGEN-DC, NE-DC and NR-DC
+
+In case of MR-DC, e.g. EN-DC, NGEN-DC, NE-DC and NR-DC, the SN can be configured with SRB3, and can trigger the SN change autonomously. According to the specification TS 37.340 [3], the SCG failure includes multiple causes of SCG RLF, SN change failure, SCG configuration failure, SCG RRC integrity check failure, etc. i.e. the SN change failure can be detected by the UE as one kind of SCG failure. During the period of SN change, the UE may suffer SN change failure due to inappropriate parameter setting of the triggering condition, e.g. too late SN change, too early SN change and wrong SN change (to another SN).
+
+SN change-related failures can be categorized as follows:
+
+- Failures due to too late SN change triggering: an SCG failure occurs after the UE has stayed for a long period of time in the cell of the SN; the MN makes decisions for UE, making UE to establish the radio link connection in a different SN.
+- Failures due to too early SN change triggering: an SCG failure occurs shortly after a successful SN change from a source SN to a target SN or a SN change failure occurs during the SN change procedure; the MN makes decisions for UE, making UE to re-establish the radio link connection in the source SN.
+- Failures due to change to wrong SN triggering: an SCG failure occurs shortly after a successful SN change from a source SN to a target SN or a SN change failure occurs during the SN change procedure; the MN makes decisions for UE, making UE to establish the radio link connection in a SN other than the source SN or target SN.
+
+The detection solution enabled by the RLF Indication and HO Report procedures can be reused, the corresponding messages may be signalled between the MN and SN, and/or among the involved SNs.
+
+- In case of MN trigger SN change, MN can obtain the SCG failure information from UE directly when SCG RLF occurs.
+- In case of SN trigger SN change, MN should inform the SN about the SN change failure to help SN adjust SN change related measurement event thresholds.
+
+#### 5.3.2.5 Successful HO Report
+
+The MRO function in NR could be enhanced to provide a more robust mobility via reporting failure events observed during successful handovers. A solution to this problem is to configure the UE to compile a report associated to a successful handover comprising a set of measurements collected during the handover phase, i.e. measurement at the handover trigger, measurement at the end of handover execution or measurement after handover execution. The UE could be configured with triggering conditions to compile the Successful Handover Report, hence the report would be triggered only if the conditions are met. This limits UE reporting to relevant cases, such as underlying issues detected by RLM, or BFD detected upon a successful handover event.
+
+The availability of a Successful Handover Report may be indicated by the Handover Complete message (*RRCReconfigurationComplete*) transmitted from UE to target NG-RAN node over RRC. The target NG-RAN node may fetch information of a successful handover report via UE Information Request/Response mechanism. In addition, the target NG-RAN node could then forward the Successful Handover Report to the source NR-RAN node to indicate failures experienced during a successful handover event.
+
+The information contained in the successful handover report may comprise:
+
+- RLM related information
+  - RLM related timers (e.g. T310, T312)
+  - Measurements of reference signals used for RLM in terms of RSRP, RSRQ, SINR
+  - RLC retransmission counter
+- Beam failure detection (BFD) related information
+  - Detection indicators and counters (e.g. Qin and Qout indications)
+  - Measurements of reference signals used in BFD in terms of RSRP, RSRQ, SINR
+- Handover related information
+  - Measurements of the configured reference signals at the time of successful handover
+    - SSB beam measurements
+    - CSI-RS measurements
+  - Handover related timers (e.g. T304)
+  - Measurement period indication, i.e. measurements are collected at handover trigger, at the end of handover execution or just after handover execution
+
+Upon reception of a Successful HO Report, the receiving node is able to analyse whether its mobility configuration needs adjustment. Such adjustments may result in changes of mobility configurations, such as changes of RLM configurations or changes of mobility thresholds between the source and the target. In addition, target NG RAN node, in the performed handover, may further optimize the dedicated RACH-beam resources based on the beam measurements reported upon successful handovers.
+
+### 5.3.3 Conclusion
+
+RAN3 has studied the mobility optimization function and has converged to the solution principles and description outlined above. RAN3 has concluded its study on mobility optimization and determined that the mobility optimization feature can be moved to normative phase. The details of the solution parts involving UE behaviour remain pending to RAN2 analysis.
+
+The SN change failure optimization in case of EN-DC and MR-DC is concluded to be specified in the normative phase of this function.
+
+## 5.4 Load Sharing and Load Balancing Optimization
+
+### 5.4.1 Use case description
+
+The objective of load sharing and load balancing is to distribute cell load evenly among cells or to transfer part of the traffic from congested cell, or to offload users from one cell or carrier or RAT to achieve network energy saving. This can be done by means of optimization of cell reselection/handover parameters and handover actions. The automation of such optimization can provide high quality user experience, while simultaneously improving the system capacity and also to minimize human intervention in the network management and optimization tasks.
+
+Compared to LTE, NR new features, e.g. CU/DU split and CP-UP separation architecture, network slicing, and EN-DC/MR-DC should be considered in the load sharing and load balancing optimization in NR. Study on load sharing and balancing across DUs within one gNB is needed (load management over F1), as well as load sharing and
+
+balancing across CU-UPs within one gNB (E1 load management). It should be studied whether slicing level metrics e.g. slice level radio resource utilization and slice availability also need to be taken into account for the reselection/handover parameters and handover action optimization.
+
+Both intra-RAT and inter-RAT load balancing scenarios should be supported. LTE is the baseline, studies for NR will focus on:
+
+- 1) Definition of the data required the load sharing and load balancing;
+- 2) Functionalities and actions required to support the load sharing and load balancing, e.g. load reporting architecture, adapting handover and/or reselection configuration.
+
+### 5.4.2 Solution description
+
+There are possible solutions that enable load management over X2, Xn, F1 and E1 interfaces. On X2 and Xn, the reported information should contain at least cell level load (e.g. resource utilization). Likewise, similar information is required from the gNB-DU to gNB-CU over F1 in case of disaggregated architecture. For E1, load information should also be provided from the gNB-CU-UP to the gNB-CU-CP.
+
+Furthermore, which procedure (i.e. new, reuse of existing one) and the periodicity (i.e. periodic reporting, event-triggered) needs to be considered.
+
+And indicative summary of the load related information discussed during the study phase is summarized in Table 5.4.2-1. More discussions may be needed during normative phase to specify the details of the metrics reported below.
+
+**Table 5.4.2-1: Load Related Information**
+
+| Load Category   | Load Related Information                        | X2 | Xn | F1 | E1 |
+|-----------------|-------------------------------------------------|----|----|----|----|
+| Cell Level      | Composite Available Capacity (CAC)              | X  | X  | X  |    |
+| Cell Level      | Cell Level Load (DL/UL/SUL)                     | X  | X  | X  |    |
+| Cell Level      | Cell Level Load per Slice                       |    | X  | X  |    |
+| Cell Level      | Cell Level Load per Band                        | X  | X  | X  | X  |
+| Cell Level      | PRB Usage for SUL                               | X  | X  | X  |    |
+| Cell Level      | Number of RRC Connections                       | X  | X  |    |    |
+| Beam Level      | PRB Usage for SSBs                              | X  | X  | X  |    |
+| Beam Level      | Composite Available Capacity (CAC) per SSB Beam | X  | X  | X  |    |
+| Hardware Level  | HW Load Indicator                               | X  | X  | X  | X  |
+| Hardware Level  | CU-CP Hardware Load                             | X  | X  |    |    |
+| Hardware Level  | CU-UP Hardware Load                             | X  | X  |    | X  |
+| Hardware Level  | CU Hardware Load (CU-CP+CU-UP)                  | X  | X  |    |    |
+| Hardware Level  | CU-UP (Hardware) Load per Slice                 |    |    |    | X  |
+| Hardware Level  | CU-UP Max Number of DRB Supported               |    |    |    | X  |
+| Hardware Level  | DU Hardware Load                                |    |    | X  |    |
+| Hardware Level  | DU DRB Capacity                                 |    |    | X  |    |
+| Transport Level | TNL Load Indicator                              | X  | X  | X  | X  |
+
+### 5.4.3 Conclusion
+
+Load sharing and load balancing functions over X2, Xn, F1 and E1 interfaces should be specified in Release 16 normative phase. At least the following load related information should be specified. Whether the reporting mechanism supports both periodic and event-triggered procedures is for further decision during normative phase.
+
+- Composite Available Capacity per cell (DL/UL), reported via X2, Xn and F1 interfaces
+- Cell Level Load (DL/UL/SUL) reported via X2, Xn, and F1 interfaces
+- TNL Load reported via X2, Xn, F1, and E1 interfaces
+
+Further refinement on the above metrics, as well as an evaluation on whether these metrics are sufficient for the correct functioning of the load management function and whether they should be complemented with additional enhancements should take place during Release 16 normative phase.
+
+Likewise, introduction of additional load information over X2, Xn, F1 and E1 interfaces is seen as potential enhancement on several areas and may be considered for specification in Release 16. Details to be further discussed during normative phase:
+
+- Beam level load indication
+- Hardware load related information
+- Per slice/band level reporting
+- For EN-DC case, the EN-DC X2 interface are enhanced to support load information report from SgNB to MeNB
+
+## 5.5 RACH Optimization
+
+### 5.5.1 Use case description
+
+The RACH configuration has critical impacts on user experience and overall network performance. The RACH collision probability, and therefore access setup delays, data resuming delays from the UL unsynchronized state, handover delays, transition delays from RRC\_INACTIVE, and beam failure recovery delays are all affected by the RACH settings. In addition, performing RACH on the most suitable downlink beam is also important and will avoid unnecessary power ramping and failed RACH attempts. This is beneficial both for the network as well as for the attempting device; it allows to avoid unnecessary interference in the network and, also, reduce the experienced delay and UE energy consumption. In NR, a new feature allows UE to change RACH resource during a RACH procedure, which lead to more complex behaviour.
+
+The setting of RACH parameters depends on a multitude of factors, e.g.:
+
+- the uplink inter-cell interference from the Physical Uplink Shared Channel (PUSCH),
+- RACH load (call arrival rate, HO rate, tracking area update, RRC\_Inactive transition rate, the request for Other SI, the beam failure recovery, traffic pattern and population under the cell coverage as it affects the UL synchronization states and hence the need to use random access),
+- uplink (SUL) and supplementary uplink (SUL) imbalances,
+- PUSCH load,
+- the cubic metric of the preambles allocated to a cell,
+- whether the cell is in high-speed mode or not,
+- uplink (UL) and downlink (DL) imbalances.
+
+The targets of RACH optimization are indicated as follows:
+
+- Minimize access delays for the UEs under the coverage of popular SSBs
+- Minimize the delays for the UEs to request the other SIs
+- Minimize the imbalance of UEs access delays on uplink (UL) and supplementary uplink (SUL) channel
+- Minimize the beam failure recovery delays for the UEs in RRC\_Connected.
+- Minimize the failed/unnecessary RACH attempts on RACH resource before success.
+
+Consequently, the RACH optimization function will attempt to automatically set several parameters related to the performance of RACH.
+
+Automatic RACH parameter settings can be enabled by collecting the RACH report from UE and by PRACH parameters exchange between gNBs. The mechanism and content of information report/exchange for RACH optimization in LTE could be the baseline whereas taking NR new features. e.g. beam, SUL, etc into account.
+
+### 5.5.2 Solution description
+
+The setting of RACH parameters that can be optimized are:
+
+- RACH configuration (resource unit allocation);
+- RACH preamble split (among dedicated, group A, group B);
+- RACH backoff parameter value;
+- RACH transmission power control parameters.
+
+As a minimum, RACH optimization is realized by UE providing RACH related information report to the NG RAN node, and by exchange of PRACH configuration of normal UL carrier and SUL carrier between NG RAN node.
+
+For CU-DU architecture, gNB-DU should be allowed to report its RACH configuration per cell to the gNB-CU, and the gNB-CU should be allowed to signal the RACH configuration per served cell to neighbouring NG RAN nodes. This allows NG-RAN nodes to identify whether RACH configurations of neighbouring cells are optimized or whether changes are needed in order to achieve a better RACH coordination between neighbouring cells.
+
+Upon receiving the polling message requesting RACH report, e.g. UE Information Request message, from the NG RAN node (potentially gNB-CU of the current serving cell), UE reports RACH information within a UE Information Response message. The gNB-CU and gNB-DU take into account the RACH report and other node information, to achieve an optimized RACH configuration.
+
+The contents of the RACH information report comprises of the following (further check by RAN2 is needed):
+
+- Indexes of the SSBs and number of RACH preambles sent on each tried SSB listed in chronological order of attempts
+- The frequency (NR ARFCN) of tried SSBs
+- The beam quality of each tried SSB (i.e. beam level measurement during RACH attempts such as BRSRP, BRSRQ, BSINR)
+- Indication whether the selected SSB is above or below the rsrp-ThresholdSSB threshold
+- Elapsed time from the last measurement prior to the beam selection time
+- Number of RACH preambles sent on SUL
+- Number of RACH preambles sent on NUL
+- Total number of fallbacks between Contention Based RACH Access (CBRA) and Contention Free RACH Access (CFRA) Contention detection indication
+
+The above RACH information report should also apply to the SN node for MR-DC case.
+
+### 5.5.3 Conclusion
+
+The following features and solutions are recommended to be specified for NR RACH optimization as part of a potential Rel.16 RAN-centric DCU WI:
+
+- RACH optimization is supported by UE reported information and by PRACH parameters exchange over Xn between gNBs and F1 between gNB-CU and gNB-DU.
+- UE RACH report (contents needs further check by RAN2 in normative phase).
+- The PRACH parameters of normal UL carrier and SUL carrier are exchanged over Xn separately.
+
+## 5.6 Energy Saving
+
+### 5.6.1 Use case description
+
+Mobile operators are increasingly aiming at decreasing power consumption in mobile networks to lower their operational expense (OPEX) with energy saving solutions. With the foreseen deployment of more number of network elements in NR, e.g. small base stations with massive MIMO in high-band, energy saving becomes even more urgent and challenging. Energy saving can be achieved through radiated power optimization on air interface (transmission power optimization and lean carrier design), enhanced hardware supporting different sleep mode and coordinated power
+
+optimization among different cells. One of the typical energy saving scenario is that capacity boosters are deployed under the umbrella of cells providing basic coverage, the capacity booster can be switched off when its capacity is no longer needed and to be re-activated on a need basis.
+
+In Rel-15 NR WI, some functionality of energy saving has been supported, including cell activation/deactivation over Xn/X2/F1 interface, and peer eNB/gNB are informed by en-gNB/gNB owning the concerned cell about the activation/deactivation actions. In addition to that, NR new features, e.g. sparser RS and SS signals, URLLC, CU/DU architecture and MR-DC should be studied and their need assessed in the energy saving solutions in NR. Furthermore, to support more efficient 4G and 5G synergy, inter-system inter-RAT energy saving solutions should also be studied based on the use cases described as below.
+
+The following use cases for R16 energy saving should be studied:
+
+#### 1) Inter-system inter-RAT energy saving
+
+Scenario a) The gNB connects with 5GC to provide boost capacity, the LTE eNB connects with EPC to provide basic coverage. The NR capacity booster cells may be switched off. The LTE eNB is allowed to activate the dormant capacity booster NR cell.
+
+#### 2) Energy Efficiency of base stations
+
+To calculate the energy efficiency of base stations, ETSI ES 203 228 ("Environmental Engineering (EE); Assessment of mobile network energy efficiency") defines the following high-level EE KPI:
+
+$$EE_{MN,DV} = \frac{DV_{MN}}{EC_{MN}}$$
+
+In which Mobile Network data Energy Efficiency (EEMN,DV) is the ratio between the performance indicator (i.e. Data Volume DV<sub>MN</sub>) and the energy consumption (EC<sub>MN</sub>).
+
+3GPP SA5 with ETSI TC EE have identified the list of existing 3GPP performance measurements to be used, per pre-5G radio access technology (GERAN, UTRAN, E-UTRAN), for the calculation of the EE KPI. It should be studied how to achieve the same measures for NG-RAN. .
+
+### 5.6.2 Solution description
+
+There is no further solution needed for intra-system energy saving.
+
+#### 1) Inter-RAT Inter-system energy saving solution:
+
+The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to dormant state and possibility for the eNB node owning non-capacity boosting cells to request an inter-system cell re-activation over the S1/NG interface.
+
+The NR capacity booster cell can autonomously switch-off by the NG-RAN node based on its own cell load information or by O&M. The NG-RAN node indicates the switch-off action to the eNB over NG interface and S1 interface.
+
+The eNB providing basic coverage may request a NR cell re-activation based on its own cell load information or neighbour cell load information, the switch-on decision may also be taken by O&M. The eNB requests a NR cell re-activation towards the NG-RAN node over the S1 interface and NG interface.
+
+#### 2) Energy Efficiency of base stations:
+
+Data volume per site could be calculated by using the PDCP PDU data volume Measurement defined in TS 28.552, clause 5.1.3.6.1. These measurements calculate the UL and DL PDCP data volume for a gNB-CU-UP.
+
+If it can be assumed that a site is served by one CU-UP, then these measurements could already provide the desired statistics to calculate the energy per bit per site.
+
+When looking at future cases it could be plausible to assume that one CU-UP may serve gNB-DUs at different sites. In this case the measurements in TS 28.552 could be taken as reference to define new measurements, taken at gNB-DU, and measuring the PDCP data throughput incoming to and outgoing from a gNB-DU
+
+### 5.6.3 Conclusion
+
+Intra-system energy saving was completed in R15.
+
+The following features and solutions are recommended to be specified for Energy Saving as part of a Rel.16 RAN-centric DCU WI:
+
+- Inter-RAT Inter-system energy saving solution
+- Solution for calculation of data volumes for the calculation of energy efficiency for a base station
+
+## 5.7 Minimization of Drive Test (MDT) Use Cases
+
+### 5.7.1 General
+
+The general principles and requirements guiding the definition of functions for Minimization of drive tests are the following:
+
+#### **MDT mode**
+
+There are two modes for the MDT measurements: Logged MDT and Immediate MDT. There are also cases of measurement collection not specified as either immediate or logged MDT, such as Accessibility measurements. Logged MDT is supported by RRC\_INACTIVE and RRC\_IDLE UE state. LTE MDT measurements/failures consists the baseline for NR MDT. Apply the Logged MDT configuration, logged measurements and reporting procedures to RRC\_INACTIVE state.
+
+#### **TRACE**
+
+Management based and signaling based trace procedure in LTE can be reused in NG-RAN MDT. From RAN2 perspective both Management-based MDT & Signaling-based MDT can be either Logged MDT or Immediate MDT. For Signaling-based MDT in NR, the user consent is required as in LTE.
+
+#### **Measurement quantities**
+
+For Immediate MDT, the measurement quantities should consider both cell-level RSRP/RSRQ/SINR and BRSRP/BRSRQ/BSINR. For logged MDT, best beam index (SSB index) of the camped cell is supported as part of the logged MDT report.
+
+#### **UE Measurements**
+
+In order to limit the impact on UE power consumption and processing, the UE measurement logging will rely on the measurements that are available in R15 NR and existing in LTE MDT as baseline.
+
+### 5.7.2 Use case description
+
+#### 5.7.2.1 Use case: Coverage Optimization via MDT
+
+The MDT data reported from UEs and the RAN may be used to monitor and detect coverage problems in the network. Coverage optimization use cases in LTE are the baseline for NR.
+
+Some examples of use cases of coverage problem monitoring and detection are described in the following:
+
+- Coverage hole
+- Weak coverage
+- Pilot Pollution
+- Overshoot coverage
+- Coverage mapping
+- UL coverage
+
+- Cell boundary mapping
+
+#### 5.7.2.2 Use case: QoS verification via MDT
+
+The MDT data reported from UEs and the RAN may be used to verify Quality of Service, assess user experience from RAN perspective, and to assist network capacity extension. QoS verification use cases in LTE are the baseline for NR.
+
+Use cases are described in the following:
+
+- Traffic Location: MDT functionality to obtain information of where data traffic is transferred within a cell.
+- User QoS Experience: MDT functionality to assess the QoS experience for a specific UE together with location information.
+
+#### 5.7.2.3 Use case: Indoor MDT improvement
+
+The WLAN/Bluetooth measurement can be collected to improve positioning accuracy for indoor MDT. WLAN/Bluetooth measurement use cases of LTE are the baseline of NR.
+
+#### 5.7.2.4 Use case: Sensor data collection
+
+In addition to location and time information, UE orientation in a global coordinate system can be collected in MDT if the information is available. No additional measurement is required. Further details are in clause 5.7.3.2.
+
+### 5.7.3 Solution description
+
+#### 5.7.3.1 Measurements
+
+The following measurements should be supported for MDT performance
+
+- DL signal quantities measurement results for the serving cell and for intra-frequency/Inter-frequency/inter-RAT neighbour cells (logged MDT and immediate MDT)
+- PHR (immediate MDT)
+- Received Interference Power measurement (immediate MDT)
+- Data Volume measurement separately for DL and UL (immediate MDT)
+- Scheduled IP Throughput for MDT measurement separately for DL and UL (immediate MDT)
+- Packet Delay measurement separately for DL and UL (immediate MDT)
+- Packet loss rate measurement separately for DL and UL (immediate MDT)
+- RSSI measurement by UE (logged MDT and immediate MDT, for WLAN/Bluetooth measurement)
+- RTT measurement by UE (logged MDT and immediate MDT, for WLAN measurement)
+
+#### 5.7.3.2 MDT procedures
+
+The procedures of LTE MDT are the baseline of NR MDT.
+
+- For immediate MDT: The network can collect data with/without the UE involvement in RRC\_CONNECTED. For example, the UE can report measurements to the RAN via periodical or event-triggered ways.
+- For logged MDT: the network sends logged measurement configuration to the UE in connected mode, and then the UE collects measurements in RRC\_IDLE/INACTIVE. Upon UE restarting the RRC connection, the UE firstly sends available indicator(s) to the network, and then the network can command the UE to send the measurements:
+  - The release operation for logged measurement configuration in the INACTIVE UE is realized only by configuration replacement when the configuration is overwritten or by configuration clearance (due to logging duration expiry).
+
+- For Logged MDT measurement collection for RRC INACTIVE UEs, the actual process of logging within the UE, takes place in RRC INACTIVE and continued in RRC IDLE.
+- The logged measurement stored in UE during RRC INACTIVE and IDLE are kept for a given common period before they are deleted as in LTE MDT.
+- MDT measurement reporting from RRC INACTIVE and IDLE is preceded by logs availability indicator to indicate logs availability.
+- The best beam index (SSB index) of the camped cell is supported as part of the logged MDT report.
+- Beam RSRP/RSRQ of the best beam of camped cell could be included in logged MDT report.
+- Include the 'number of good beams' associated to the cells within the range (which is configured by network for cell reselection) of the R value of the highest ranked cell as part of the beam level measurements in the logged MDT report.
+- The out-of-coverage detection and logging in NR can be configured to be independent of the periodical DL pilot strength logged measurements.
+- For MDT in NR, UE can be configured to only perform the logging for out-of-coverage detection, i.e. UE is not required to log the DL pilot strength measurements if the configuration is only out-of-coverage detection.
+- A new indicator is introduced per logged measurement information entry in order to informing of detection of any cell selection state as in Rel-15 LTE MDT.
+- For RLF report and accessibility measurements, UE logs these measurements without the need for prior configuration by the network. Upon UE entering connected state, the UE firstly sends available indicator(s) to the network, and then the network can command the UE to send the measurements. The mechanisms of LTE RLF (Radio Link Failure) and CEF (Connection Establishment Failure) reporting are taken as baseline for 5G NR. The information included in LTE RLF and CEF reporting is taken as baseline for 5G NR.
+- The use cases of NR accessibility measurements includes:
+  - The UE fails to send RRCSetupRequest, i.e. when timer T300 expires.
+  - The UE fails to send RRCResumeRequest/RRCResumeRequest1, i.e. when timer T319 expires.
+- To address Coverage Optimization use case, RLF report and accessibility measurements are enhanced with:
+  - NR RLF Report can indicate the information that enable to differentiate DL and UL availability after RLF occurrence. NR RLF report is extended with a flag, where at least "no suitable cell is found" is indicated. There is no additional UE measurement requirement for this. When to set the flag can be discussed in WI phase.
+  - NR CEF Report is enhanced with further information elements expressing the number of failed connection setup attempts after RLF at least including the number and available location information. NR CEF Report is extended with "Number of connection failures per cell" field. The UE counts the number of CEFs that it has experienced within the last 48 hours.
+  - RACH failure information, if available, should be included in both RLF report and CEF report. Attempted SSB index can be indicated as part of RACH failure information.
+  - Include SSB related information consisting of SSB index and number of preambles sent for each tried SSB in the RACH information report.
+  - SS Block index, CSI-RS index for both of serving and neighbouring cells could be included in the NR RLF report.
+  - The mechanism of RRC resume failure reporting takes CEF reporting as baseline.
+  - The information included in the NR RRC resume failure reporting takes the information included in the 5G NR CEF reporting as baseline.
+  - CSI-RS index and the corresponding number of preambles sent for each tried beam carrying CSI-RS index can be included in the NR RLF report, if it is RACH procedure failure leading to the RLF.
+
+- SSB index of the downlink beams of both serving cell and neighbour cells, and SUL/NUL carrier information can be included in the NR CEF reporting.
+- for WLAN/Bluetooth measurement collection: procedure for LTE WLAN/Bluetooth measurement collection is taken as baseline. The procedure baseline in TS 36.331 [6] includes:
+  - Supporting WLAN/Bluetooth measurement collection for logged MDT, immediate MDT, RLF report and accessibility measurements.
+  - Supporting WLAN and Bluetooth name list configuration in order to only collect the measurements of operator deployed WLAN and Bluetooth.
+  - Supporting reporting WLAN ID, RSSI, RTT for WLAN measurements and reporting Bluetooth address, RSSI for Bluetooth measurement.
+- For MDT continuity:
+  - Logged MDT continuity could span PLMNs within MDT PLMN list in NR.
+  - Logged MDT configurations and logging should be suspended if the validity time is not expired upon the change of RATs and systems, e.g. when cell reselection to/from NR. Different system mentioned here means different core networks.
+  - Signalling based immediate MDT could be propagated across PLMNs within MDT PLMN list in NR.
+  - Signalling based immediate MDT continuity could not be propagated across RATs, e.g. when handover to/from NR.
+- In addition to location and time information, following sensor information can be collected if available:
+  - The uncompensated barometric pressure measurement if available can be included in the MDT report.
+  - NR MDT measurements can be tagged with information fields informing the network about UE speed.
+  - NR MDT measurements can be tagged with information fields informing the network about UE orientation in a global coordinate system.
+- In Rel-16, UE includes the GNSS location information for Logged MDT, DL signal quantities measurement of Immediate MDT, RLF report, accessibility measurement and out-of-coverage logging, if the GNSS location information is available when the measurement was taken for the UEs with the GNSS receiver.
+
+#### 5.7.3.3 MDT activation in split RAN
+
+##### 5.7.3.3.0 General
+
+NOTE: The solutions in this clause are pending progress in RAN2 and further discussions are needed in RAN3 in normative phase.
+
+##### 5.7.3.3.1 Signalling activation
+
+If the MDT measurement is initiated by the AMF, the AMF sends MDT measurement request to the CU-CP. The CU-CP may further decide which DU or which CU-UP to perform the MDT measurement. For some measurement, the CU-CP may need to split the measurement into different measurements performed in different nodes.
+
+![Sequence diagram showing MDT Activation signaling in split RAN. The diagram involves four lifelines: DU, CU-UP, CU-CP, and AMF. The sequence of messages is: AMF sends 'MDT Activation' to CU-CP; CU-CP sends 'MDT Activation' to CU-UP; CU-UP sends 'MDT Activation' to DU.](26d664119ad25250780f554633444e54_img.jpg)
+
+```
+
+sequenceDiagram
+    participant AMF
+    participant CU-CP
+    participant CU-UP
+    participant DU
+    AMF->>CU-CP: MDT Activation
+    CU-CP->>CU-UP: MDT Activation
+    CU-UP->>DU: MDT Activation
+  
+```
+
+Sequence diagram showing MDT Activation signaling in split RAN. The diagram involves four lifelines: DU, CU-UP, CU-CP, and AMF. The sequence of messages is: AMF sends 'MDT Activation' to CU-CP; CU-CP sends 'MDT Activation' to CU-UP; CU-UP sends 'MDT Activation' to DU.
+
+**Figure 5.7.3.3.1-1: Signalling MDT Activation in split RAN**
+
+##### 5.7.3.3.2 Management activation
+
+If the MDT measurement is initiated by the EM, the EM sends MDT measurement activation to the CU-CP. The CU-CP may further decide which DU or which CU-UP to perform the MDT measurement. For some measurement, the CU-CP may need to split the measurement into different measurements performed in different nodes.
+
+![Sequence diagram showing Management MDT Activation in split RAN. The diagram involves four lifelines: DU, CU-UP, CU-CP, and EM. The sequence of messages is: EM sends 'MDT Activation' to CU-CP; CU-CP sends 'MDT Activation' to CU-UP; CU-UP sends 'MDT Activation' to DU.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant EM
+    participant CU-CP
+    participant CU-UP
+    participant DU
+    EM->>CU-CP: MDT Activation
+    CU-CP->>CU-UP: MDT Activation
+    CU-UP->>DU: MDT Activation
+  
+```
+
+Sequence diagram showing Management MDT Activation in split RAN. The diagram involves four lifelines: DU, CU-UP, CU-CP, and EM. The sequence of messages is: EM sends 'MDT Activation' to CU-CP; CU-CP sends 'MDT Activation' to CU-UP; CU-UP sends 'MDT Activation' to DU.
+
+**Figure 5.7.3.3.2-1: Management MDT Activation in split RAN**
+
+#### 5.7.3.4 MDT reporting in split RAN
+
+Void
+
+#### 5.7.3.5 MDT for dual connectivity
+
+- Immediate MDT configurations are supported for DC scenario.
+- Logged MDT configurations can come from SN node in DC scenario.
+- The existing MDT framework is the baseline for the SCG cells related MDT configuration.
+- The triggers for MDT measurements associated to MCG and SCG are separate.
+- MN-SN coordination is required for MDT measurements' configuration and reporting in DC framework.
+- If SRB3 is not configured, SN related measurements are transmitted to MN via SRB1/2 and then forwarded to SN.
+- If SRB3 is configured, MN related measurements are transmitted to MN via SRB1/2, SN related measurements are transmitted to SN via SRB3
+
+### 5.7.4 Conclusion
+
+This chapter of technical report presents the results of a study on MDT for NR. Multiple use cases for MDT have been identified, including coverage optimization, QoS verification via MDT, indoor MDT improvement and sensor data collection.
+
+To address these use cases, logged MDT, immediate MDT and accessibility measurements for NR are recommended for normative work.
+
+Several measurements are recommended to be supported for NR MDT, including DL signal quantities measurement results, PHR, Received interference power measurement, data volume measurement, scheduled IP throughput, packet delay measurement, packet loss rate measurement, RSSI and RTT for WLAN and Bluetooth.
+
+The procedures for immediate MDT, logged MDT and accessibility measurements described in the present document are recommended to be specified. The procedures of LTE MDT are the baseline for NR. Several new procedures for NR should also be specified, including procedures for RRC INACTIVE, beam related measurements, RLF reporting, CEF reporting, WLAN/Bluetooth measurement collection, MDT continuity, sensor/GNSS location information collection and MDT configuration for DC scenario.
+
+## 5.8 UE energy saving
+
+### 5.8.1 Use case description
+
+High-end mobile devices with 5G modem are expected to feature advanced components e.g. display, processors, graphic engine, etc. Added up, these render power management to be very challenging. In other words, power efficiency is critical for every single component, in particular for the modem itself, regardless of the power source used (e.g. battery capacity and technology).
+
+Battery lifetime is an important criterion directly affecting user experience – no matter how good the other performance aspects of a device may be, if its battery lifetime is poor, user experience will be greatly impacted. To ensure a smooth migration from 4G to 5G, the battery lifetime should thus be, under similar criteria, on par or better using 5G than 4G.
+
+Therefore, network and UE vendors have a common interest in ensuring that the 5G NR ecosystem is able to maximize battery lifetime for all its users in all conditions. This means network and UE ought to cooperate to ensure lower baseline power and maintain better efficiency with all data rates, as shown below.
+
+![Figure 5.8.1-1: UE power variation with data rate. The graph shows UE power on the y-axis versus Data rate Gbps on the x-axis (0 to 4). Three lines are plotted: a dashed blue line labeled 'LTE' starting at (0,0) and rising steeply; a solid orange line labeled 'NR' starting at (0,0) and rising more gradually; and a horizontal dashed orange line labeled 'Baseline control channel monitoring' at a constant low power level.](90d8516930bb8334d7898604aee1bb58_img.jpg)
+
+The figure is a line graph titled 'NR desired behaviour'. The y-axis is labeled 'UE power' and the x-axis is labeled 'Data rate Gbps' with values 0, 1, 2, 3, and 4. There are three lines: 
+ 
+
+- A dashed blue line labeled 'LTE' starts at the origin (0,0) and has a steep positive slope.
+- A solid orange line labeled 'NR' starts at the origin (0,0) and has a less steep positive slope than the LTE line.
+- A horizontal dashed orange line at the bottom is labeled 'Baseline control channel monitoring', representing a constant power level regardless of data rate.
+
+Figure 5.8.1-1: UE power variation with data rate. The graph shows UE power on the y-axis versus Data rate Gbps on the x-axis (0 to 4). Three lines are plotted: a dashed blue line labeled 'LTE' starting at (0,0) and rising steeply; a solid orange line labeled 'NR' starting at (0,0) and rising more gradually; and a horizontal dashed orange line labeled 'Baseline control channel monitoring' at a constant low power level.
+
+**Figure 5.8.1-1: UE power variation with data rate**
+
+3GPP has started an effort, i.e. power saving SI, to achieve this target. From the study, as shown on Figure 5.8.1-2, for different traffic types, roughly less than 36 % of the total power consumption occurs in sleep state (~RRC\_Idle mode). Said otherwise, reducing the power consumption in RRC\_Connected mode is the primary target. As the UE behavior in RRC\_Connected mode is controlled by the network, the joint role of the UE and the network to reduce power consumption in this state is clear.
+
+![Figure 5.8.1-2: Power consumption distribution for different traffic models. The figure contains three pie charts showing power consumption distribution for FTP/Video (High data activity), Instant Message (Low data activity), and VoIP (Voice data activity) models. The legend indicates Sleep (purple), PDCCH (pink), PDSCH (green), SSB/CSI-RS (orange), and UL (blue).](6e5a85131eedf6b98db62877ee64506e_img.jpg)
+
+**FTP/Video: 52.33 units**  
+• High data activity
+
+| Category   | Percentage |
+|------------|------------|
+| PDCCH      | 64%        |
+| PDSCH      | 24%        |
+| Sleep      | 9%         |
+| SSB/CSI-RS | 2%         |
+| UL         | 1%         |
+
+**Instant Message: 10.89 units**  
+• Low data activity
+
+| Category   | Percentage |
+|------------|------------|
+| PDCCH      | 58%        |
+| Sleep      | 32%        |
+| PDSCH      | 6%         |
+| SSB/CSI-RS | 2%         |
+| UL         | 2%         |
+
+**VoIP: 50.63 units**  
+• Voice data activity model
+
+| Category   | Percentage |
+|------------|------------|
+| PDCCH      | 45%        |
+| Sleep      | 36%        |
+| PDSCH      | 8%         |
+| SSB/CSI-RS | 10%        |
+| UL         | 1%         |
+
+Figure 5.8.1-2: Power consumption distribution for different traffic models. The figure contains three pie charts showing power consumption distribution for FTP/Video (High data activity), Instant Message (Low data activity), and VoIP (Voice data activity) models. The legend indicates Sleep (purple), PDCCH (pink), PDSCH (green), SSB/CSI-RS (orange), and UL (blue).
+
+**Figure 5.8.1-2: Power consumption distribution for different traffic models**
+
+For 5G/NR design UE energy efficiency is listed as one of the key performance indicators in 3GPP TR 38.913.
+
+UE energy efficiency, which means the capability of a UE to sustain much better mobile broadband data rate while minimizing the UE modem energy consumption both qualitative and quantitative KPIs are required. Although only a qualitative KPI is captured now, it is also specified that based on the study, more detailed quantitative assessment can be performed.
+
+Although it is possible to measure power consumption of a UE directly, such direct measurement is vendor dependent, i.e. only represent the power consumption of a specific UE model, and it can only represent UE part of the power saving efforts. There is a need for a UE energy efficiency (UE EE) measurement to represent the network part of the power saving efforts, which can be used for network optimization. R1 power consumption model agreed in TR 38.840 can be used as a baseline for such vendor-independent UE energy efficiency measurement. For network optimization, a reliable quantitative KPI UE energy efficiency (UE EE) should be consistent across UE vendors.
+
+The objective of this use case is to measure the network performance on UE energy efficiency through RAN data collection, therefore, the effect of power saving features can be objectively reflected, which in the end leads to network and UE to work together to maximize UE battery lifetime and enhance user experience.
+
+### 5.8.2 Solution description
+
+Void
+
+### 5.8.3 Conclusion
+
+Void
+
+## 5.9 Active Antenna System (AAS) Optimization
+
+### 5.9.1 Use case description
+
+Active Antenna System (AAS) is a key component of 5G radio access networks, and, through the exploitation of a beam-centric design, it enables extensive usage of beamforming techniques. Monitoring the radiated power of Downlink Control Channels in total and per beam allows operators to in-depth monitoring of radiation power emission requirement fulfilments.
+
+RAN2 agreed to define the following NR measurements for the use case of Active Antenna System optimization:
+
+- 1) Total NG-RAN Transmit Power for Control Channels (i.e. SSB/PDCCH/...)
+- 2) NG-RAN Transmit Power per Beam for Control Channels (i.e. SSB/PDCCH/...)
+
+NOTE: The power measurements are conditioned to the approval from RAN1 and RAN4.
+
+### 5.9.2 Solution description
+
+Void
+
+### 5.9.3 Conclusion
+
+Void
+
+# --- 6 Measurement quantities, events and faults for collection and utilization
+
+## 6.1 General
+
+Void
+
+## 6.2 Measurement quantities
+
+### 6.2.1 UE originated measurements
+
+Void
+
+### 6.2.2 L2 measurement quantities
+
+#### 6.2.2.0 General
+
+The following measurements are to be introduced to NR:
+
+- Received Random Access Preambles
+- Number of users for RRC\_CONNECTED
+- Number of users for RRC\_INACTIVE
+
+For the following measurements, SA5 defined measurements are to be used instead of measurements defined in TS 36.314 [8]:
+
+- 4.1.1 PRB usage
+- 4.1.4 Packet Delay
+- 4.1.5 Data loss
+- 4.1.6 Scheduled IP Throughput
+- 4.1.7 Scheduled IP Throughput for MDT
+- 4.1.8 Data Volume
+- 4.1.11 Distribution of scheduled IP throughput
+
+It is not precluded that RAN2 introduce new or alternative measurements.
+
+#### 6.2.2.1 L2 measurements in TS 28.552
+
+RAN2 and RAN3 have analysed SA5 requirements for "Performance measurements for gNB" defined in TS 28.552 [4], and came to the following conclusion:
+
+##### **Table 6.2.2.1-1: Analysis on performance measurements for gNB in TS 28.552**
+
+| Clause  | Title                                                           | Use case description                                                                                                                                                                                                                                                                  | Views from RAN2 and RAN3                                                                                                                                                                                                              |
+|---------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.1.1   | Performance measurements valid for all gNB deployment scenarios |                                                                                                                                                                                                                                                                                       | Measurements in this clause of TS 28.552 refer to the NRCellCU or NRCellDU Measurement Object Classes, while RAN3 has not defined gNB-CU and gNB-DU for non-split gNB deployment scenario.                                            |
+| 5.1.1.1 | Packet Delay                                                    | The average time it takes to get a response back on a HARQ transmission in the DL                                                                                                                                                                                                     | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view                                                                                                                                                                  |
+| 5.1.1.2 | Radio resource utilization                                      | The total usage (in percentage), or distribution of usage.<br>- DL total PRB usage<br>- UL total PRB usage<br>- distribution of DL usage<br>- distribution of UL usage                                                                                                                | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view                                                                                                                                                                  |
+| 5.1.1.3 | UE throughput                                                   | UE throughput/volume:<br>- Average DL UE throughput in gNB<br>- Distribution of DL UE throughput in gNB<br>- Average UL UE throughput in gNB<br>- Distribution of UL UE throughput in gNB<br>- Volume of unrestricted DL UE data in gNB<br>- Volume of unrestricted UL UE data in gNB | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view                                                                                                                                                                  |
+| 5.1.1.4 | RRC connection number                                           | The mean number of users in RRC connected mode<br>- mean number of RRC conn<br>- max number of RRC conn                                                                                                                                                                               | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view                                                                                                                                                                  |
+| 5.1.1.5 | PDU Session Management                                          | There are the following use cases:<br>- Number of PDU Sessions requested to setup<br>- Number of PDU Sessions successfully setup<br>- Number of PDU Sessions failed to setup                                                                                                          | Suggest RAN3 to check the feasibility<br>Feasible from RAN3 point of view.<br>However, RAN3 thinks that these measurements need to also consider the PDU session to setup and failed to setup in the Initial Context Setup procedure. |
+| 5.1.1.6 | Mobility Management                                             | Measurements related to inter-gNB handovers                                                                                                                                                                                                                                           | Suggest RAN3 to check the feasibility<br>Feasible from RAN3 point of view                                                                                                                                                             |
+| 5.1.1.7 | TB related Measurements                                         | TB related measurements                                                                                                                                                                                                                                                               | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view                                                                                                                                                                  |
+| 5.1.1.8 | PDU session modifications                                       | Measurements related to PDU session modifications                                                                                                                                                                                                                                     | Suggest RAN3 to check the feasibility<br>Out of RAN3 scope.                                                                                                                                                                           |
+| 5.1.1.9 | PDU session releases                                            | Measurements related to PDU session releases                                                                                                                                                                                                                                          | Suggest RAN3 to check the feasibility<br>Out of RAN3 scope.                                                                                                                                                                           |
+
+| Clause   | Title                                                             | Use case description                                                                                                                                                                                                                      | Views from RAN2 and RAN3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+|----------|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.1.1.10 | DRB Setup Management                                              | There are the following use cases:<br>- Number of DRBs attempted to setup<br>- Number of DRBs successfully setup                                                                                                                          | <p>Suggest RAN3 to check the feasibility</p> <p>The trigger for the measurement on Number of DRB Successfully setup measurement in TS 28.522 seems badly defined. The following condition is not the main condition for successful DRB setup, although it is an essential part of the overall DRB setup process: <i>On transmission of INITIAL CONTEXT SETUP RESPONSE, PDU SESSION RESOURCE SETUP RESPONSE message containing the "PDU Session Resource Setup Response List" IE (see 3GPP TS 38.413 [18]) or by the PDU SESSION RESOURCE MODIFY REQUEST message from the gNB to the AMF.</i></p> <p>The main condition for successful DRB setup is listed later in the text, namely: <i>On receipt of RRCReconfigurationComplete message by the gNB to the UE, as the response to the transmitted RRCReconfiguration message that contains the DRBs to add.</i></p> <p>RAN3 asks SA5 to revise the triggering condition by taking the above comments into account.</p> |
+| 5.1.2    | Measurements related to end-to-end 5G network and network slicing | No measurements in this clause                                                                                                                                                                                                            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| 5.1.3    | Performance measurements valid for split gNB deployment scenario  |                                                                                                                                                                                                                                           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| 5.1.3.1  | Packet Loss Rate                                                  | <p>The fraction of PDCP SDU packets which are not successfully received at gNB-CU-UP.</p> <ul style="list-style-type: none"> <li>- UL packet loss rate</li> <li>- UL F1-U packet loss rate</li> <li>- DL F1-U packet loss rate</li> </ul> | <p>UL Packet loss rate with measurements maintained per gNB-CU-UP or per gNB-DU (termination point left to gNB implementation) is Feasible from RAN2 point of view.</p> <p>Suggest RAN3 to check the feasibility</p> <p>Feasible from RAN3 point of view.</p> <p>Note 5</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| 5.1.3.2  | Packet drop rate                                                  | <p>The fraction of PDCP SDU packets which are dropped on DL.</p> <ul style="list-style-type: none"> <li>- DL PDCP SDU Drop rate in gNB-CU-UP</li> <li>- DL Packet Drop Rate in gNB-DU</li> </ul>                                          | <p>Feasible from RAN2 point of view with understanding that measurements maintained per gNB-CU-UP or per gNB-DU</p> <p>Feasible from RAN3 point of view.</p> <p>Note 5</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+
+| Clause  | Title                         | Use case description                                                                                                                               | Views from RAN2 and RAN3                                                                                                                                                                                                                                                                                         |
+|---------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.1.3.3 | Packet delay                  | There are the following use cases:<br>- average delay DL in CU-UP<br>- average delay on F1-U<br>- average delay DL in gNB-DU                       | Feasible from RAN2 point of view, with understanding that measurements maintained per gNB-CU-UP or per gNB-DU<br>Suggest RAN3 to check the feasibility<br>Feasible from RAN3 point of view, with the understanding that "NG-U ingress IP termination" should be read as "F1-U ingress IP termination".<br>Note 5 |
+| 5.1.3.4 | IP latency measurements       | IP latency DL in gNB-DU                                                                                                                            | Suggest RAN3 to check the feasibility<br>Feasible from RAN3 point of view<br>Note 5                                                                                                                                                                                                                              |
+| 5.1.3.5 | UE context release            | There are the following use cases:<br>- UE context release request (gNB-DU initiated)<br>- Number of UE context release request (gNB-CU initiated) | Suggest RAN3 to check the feasibility<br>Feasible from RAN3 point of view                                                                                                                                                                                                                                        |
+| 5.1.3.6 | PDCP data volume measurements | There are the following use cases:<br>- PDCP PDU data volume Measurement<br>- PDCP SDU data volume Measurement                                     | Feasible from RAN2 point of view<br>Feasible from RAN3 point of view<br>Note 5                                                                                                                                                                                                                                   |
+
+NOTE 1: It is noted that the current table is based on TS 28.552 v16.0.0, and there may be more measurements due to SA5 progresses.
+
+NOTE 2: The table starts with the reference to clause 5.1.1 "Performance measurements valid for all gNB deployments". Given the generic approach that RAN2 has no insight into F1 (and its termination points), measurements feasibility by RAN2 has not been made for all possible deployments (e.g. but with the assumption that measurements are maintained per gNB, or gNB-CU or per gNB-DU).
+
+NOTE 3: Currently, for some measurements defined in TS 28.552, they are defined per mapped 5QI level (a single 5QI mapped to a DRB). From RAN2 point of view, mapping between 5QI and DRB in NR might be many to one, so there may be alternative ways to do the measurement, e.g. perform measurements by DRB level. RAN2 understanding is that all QoS flows mapped to one DRB get the same QoS treatment.
+
+NOTE 4: RAN3 clarifies that the definition of "Mapped 5QI" in TS 28.552 is in line with RAN3 specifications. Namely, there is a one to one relation between the 5QI assigned to a DRB to be setup (i.e. Mapped 5QI) and the DRB itself. However, there could be many QoS flows, each with individual QoS Flow Level QoS Parameters (including one 5QI), mapped to one DRB.
+
+NOTE 5: The "UL PDCP SDU Loss Rate", the "UL F1-U Packet Loss Rate", the "DL PDCP SDU Drop rate in gNB-CU-UP", the "Average delay DL in CU-UP", the "Average delay on F1-U", the "DL PDCP PDU Data Volume", the "UL PDCP PDU Data Volume", the "DL PDCP SDU Data Volume" and the "UL PDCP SDU Data Volume" require collection on a per mapped 5QI by the gNB-CU-UP. The latter is not possible according to the current version of TS 38.463, due to the mapped 5QI not being signalled from gNB-CU-CP to gNB-CU-UP. However, RAN3 has agreed to include such information in opportune signalling from gNB-CU-CP to gNB-CU-UP in next meeting, hence RAN3 concludes that these measurements can be considered feasible for Release 15 gNB-CU-UPs.
+
+NOTE 6: For RRC connection number, RAN2 common understanding is that it is not part of L1/L2 measurement.
+
+#### 6.2.2.2 RAN part of packet delay measurement
+
+Packet delay includes RAN part of delay and CN part of delay. This study only covers RAN part of the packet delay.
+
+The RAN part of DL and UL packet delay is measured by gNB and UE at DRB level, respectively. In reporting to TCE, the delay may be provided to QoS flow level by gNB with the assumption that all QoS flows mapped to one DRB get the same QoS treatment.
+
+##### 6.2.2.2.1 UL packet delay measurement
+
+![Diagram illustrating the RAN part of UL delay measurement. It shows a packet entering the UE's SDAP layer and being transmitted to the gNB. The delay is measured from the PDCP upper SAP in the UE (T1) to the PDCP upper SAP in the gNB (T2). The delay is split into D1 (PDCP queuing delay in the UE) and D2 (the rest of the delay, including HARQ, RLC, and MAC delays).](5478f70a6cef3e5672b2b22d28830cfb_img.jpg)
+
+The diagram shows the protocol stacks for a User Equipment (UE) and a gNB. On the UE side, a packet enters the SDAP layer. The delay from the PDCP upper SAP (T1) to the MAC lower SAP is labeled D1. The delay from the MAC lower SAP to the PDCP upper SAP in the gNB (T2) is labeled D2. The gNB side shows the SDAP, PDCP, RLC, MAC, and PHY layers. The PDCP layer in the gNB is associated with GTP-U.
+
+Diagram illustrating the RAN part of UL delay measurement. It shows a packet entering the UE's SDAP layer and being transmitted to the gNB. The delay is measured from the PDCP upper SAP in the UE (T1) to the PDCP upper SAP in the gNB (T2). The delay is split into D1 (PDCP queuing delay in the UE) and D2 (the rest of the delay, including HARQ, RLC, and MAC delays).
+
+**Figure 6.2.2.2.1-1: RAN part of UL delay**
+
+As shown in figure 6.2.2.2.1-1, RAN part (T2-T1) of the UL delay is defined as the delay from packet entering the UE's PDCP upper SAP to leaving gNB's PDCP upper SAP. It can be separated into D1 and D2:
+
+- D1 is the PDCP queuing delay in the UE, including the delay from packet arrival at PDCP upper SAP until the UL grant to transmit the packet is available, which has included the delay the UE gets resources granted (from sending SR/RACH to getting first grant). D1 is invisible to the network and should be measured by the UE.
+- D2 is the rest of the delay, including HARQ (re)transmission delay, RLC delay, F1 delay\* and PDCP re-ordering delay in gNB. Separate measurement associated to over-the-air delay in UL will be introduced, and it is defined as the average time between the time of sending the successful HARQ feedback to the time of scheduling grant in UL for the UE.
+
+NOTE: The measurements "average delay DL in CU-UP" and "average delay on F1-U" in the Table 6.2.2.1-1 could be used.
+
+The RAN part of UL delay is measured by the following mechanism:
+
+- UE measures D1 and reports the average of D1 to gNB in RRC;
+- gNB measures the D2 and derives UL delay as D1+D2.
+
+##### 6.2.2.2.2 DL packet delay measurement
+
+RAN part of the DL delay is measured by gNB by DRB level. For arrival of packets the reference point is PDCP upper SAP. For successful reception the reference point is MAC lower SAP. It includes average delay in DL (e.g. average delay in CU-UP, average delay on F1-U and average delay DL in gNB-DU)\*. The delay may be converted to QoS flow level by gNB with the assumption that all QoS flows mapped to one DRB get the same QoS treatment.
+
+NOTE: The measurements "average delay DL in CU-UP" and "average delay on F1-U" in the Table 6.2.2.1-1 could be used.
+
+### 6.2.3 L1 measurement quantities (e.g. Timing Advance in RAR)
+
+Void
+
+### 6.2.4 Sensor data for UE orientation/altitude to log in addition to location
+
+Void
+
+## 6.3 Events and faults
+
+### 6.3.1 RLF and access failure information
+
+Void
+
+## 6.4 Conclusion
+
+The feasibility of L2 measurements in TS 28.552 have been checked in TR 37.816. The following feasible L2 measurements are recommended to be supported in NR in context of RAN-centric data collection:
+
+- PRB usage
+- Packet Delay
+- Data loss
+- Scheduled IP Throughput
+- Scheduled IP Throughput for MDT
+- Data Volume
+- Distribution of scheduled IP throughput
+
+for which the definitions in TS 28.552 apply.
+
+In addition, new definitions for RAN part of packet delay measurement, alternative end user throughput measurement, received random access preambles, number of UEs should be introduced in NR. It is not precluded that RAN2 introduce new or alternative measurements.
+
+# --- 7 Conclusion
+
+RAN3 conclusions
+
+The following SON features are recommended by RAN3 to be specified in normative phase:
+
+- Capacity and Coverage Optimization
+- PCI Selection
+- Mobility Optimization
+- Load Sharing and Load Balancing Optimization
+- RACH Optimization
+- Energy Saving
+
+Recommendations for each feature are described in the dedicated conclusion section for each use case.
+
+RAN2 conclusions
+
+MDT and L2 measurements are recommended by RAN2 to be specified in normative phase, detailed recommendations are described in the dedicated section for MDT and measurements.
+
+# Annex A: Change history
+
+| Change history |                                     |           |    |     |     |                                                                                                                                                                                                                                                                                                                   |             |
+|----------------|-------------------------------------|-----------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting                             | Tdoc      | CR | Rev | Cat | Subject/Comment                                                                                                                                                                                                                                                                                                   | New version |
+| 2018-10-8      | RAN3 #101bis                        | R3-186031 |    |     |     | First Skeleton provided                                                                                                                                                                                                                                                                                           | 0.0.0       |
+| 2018-10-11     | RAN3 #101bis                        | R3-186226 |    |     |     | Skeleton revised                                                                                                                                                                                                                                                                                                  | 0.0.1       |
+| 2018-10-13     | RAN3 #101bis                        | R3-186264 |    |     |     | Agreed TR skeleton                                                                                                                                                                                                                                                                                                | 0.0.2       |
+| 2018-10-26     | RAN3 #101bis                        | R3-186268 |    |     |     | Included agreed TP in R3-186227                                                                                                                                                                                                                                                                                   | 0.1.0       |
+| 2019-03-28     | RAN3 #103                           |           |    |     |     | Included agreed TP in R3-191064                                                                                                                                                                                                                                                                                   | 0.2.0       |
+| 2019-04-25     | RAN3 #103bis<br>and RAN2<br>#105bis | R3-192188 |    |     |     | Included agreed TPs in R3-192130, R3-192136, R3-192180, R3-192181, R2-1904830, R2-1904321, R2-1905197, R2-1905229                                                                                                                                                                                                 | 0.3.0       |
+| 2019-5-22      | RAN3#104<br>and RAN2<br>#106        | R3-193283 |    |     |     | Included agreed TPs in R2-1905924, R2-1908147, R2-1907694, R2-1908143, R2-1908145, R2-1908162, R2-1908148, <u>R3-192544</u> , R3-193185, <u>R3-193184</u> , <u>R3-193186</u> , <u>R3-193187</u> , <u>R3-193188</u> , <u>R3-193189</u> , <u>R3-193190</u> , <u>R3-193247</u> , <u>R3-193246</u> , <u>R3-193249</u> | 0.4.0       |
+| 2019-06        | RAN #84                             |           |    |     |     | Version for one-step approval                                                                                                                                                                                                                                                                                     | 1.0.0       |
+| 2019-07        | RAN #84                             |           |    |     |     | TR is approved by RAN plenary                                                                                                                                                                                                                                                                                     | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37823/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-16/37_series/37823/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9593d2b2d84aae2f09de69365823848a4f1dffdb
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c687fa3edca74aea2c12ce1acfba326624f895dd07211b7f74e4dae0b3c041b
+size 68247
diff --git a/marked/Rel-16/37_series/37823/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/37_series/37823/19a5f0db57a21a0e82a7f326083e96fd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d40a2e7d3ffb3d317ee77901dad09c4210640fa4
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/19a5f0db57a21a0e82a7f326083e96fd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d89ae22015a6b5e11426614e19bff366b70ada05d63d61434e04a6a3cc493304
+size 15998
diff --git a/marked/Rel-16/37_series/37823/3b7c13851b2efcae74f526646918fb49_img.jpg b/marked/Rel-16/37_series/37823/3b7c13851b2efcae74f526646918fb49_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a419cd986eef1cb5ce4366699a6b83f994b3b6a0
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/3b7c13851b2efcae74f526646918fb49_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0be659895775047e757c13d2129c7d6df77dec0307d14599ae174891efefe94
+size 19981
diff --git a/marked/Rel-16/37_series/37823/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37823/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..186fcb1b9980036e006f671fe7c5da89a5d70308
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66a8d22f98e41630a16620c70a21630e74a292e179c141c3a2b8710b013a6174
+size 9765
diff --git a/marked/Rel-16/37_series/37823/624d9669faa18991d525fea5f0e03269_img.jpg b/marked/Rel-16/37_series/37823/624d9669faa18991d525fea5f0e03269_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1325965a626a12aee9b5eba771c88187b914b04
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/624d9669faa18991d525fea5f0e03269_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13c98b3c58366c3540c3a12e2fea22d3555ef90c17b5034cd48827b7604a7d09
+size 35185
diff --git a/marked/Rel-16/37_series/37823/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37823/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b3541246dc5455de440cee144b60f315b85a6f68
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:592a2bb81f7e1a2b1b5975112ef690539dea152405514e1c13720545bc576e82
+size 5849
diff --git a/marked/Rel-16/37_series/37823/b712e7522f1bb7135730c7d1abb46d43_img.jpg b/marked/Rel-16/37_series/37823/b712e7522f1bb7135730c7d1abb46d43_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec1ee8efd44f59975e7e134d741472fcff4c148e
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/b712e7522f1bb7135730c7d1abb46d43_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0241512baf862f62b386665ce5ae111079a9852c8a379807e44f7cd19d22d34
+size 35272
diff --git a/marked/Rel-16/37_series/37823/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/37_series/37823/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2820e708d526c656ce34246ef8836cd2360f0f0
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:895aa3d90770abc863f6e52473a51050abd2e6c569ccd48686ca5ff365b7b9e1
+size 50414
diff --git a/marked/Rel-16/37_series/37823/d369dc114803a761d452c13ee58ed579_img.jpg b/marked/Rel-16/37_series/37823/d369dc114803a761d452c13ee58ed579_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34f2bc58ed36d474ef47a20439fb31fb8e9a61d0
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/d369dc114803a761d452c13ee58ed579_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b690ced921d8b086ef2c5b160f79352b101523386b881f03af0a615a912fe0a
+size 19137
diff --git a/marked/Rel-16/37_series/37823/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/37_series/37823/e636d7ccca0ad14c6b95201404324823_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..04db67ffb762c97a9a8ee2be857815ec5606cfa4
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/e636d7ccca0ad14c6b95201404324823_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:049a8bc9b5bb69db72fb4c562cd00631ce04bf47f6dc2b78cd17406f5da5e37d
+size 21812
diff --git a/marked/Rel-16/37_series/37823/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/37_series/37823/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9eb0a053b42e171a524b82bd29597bc384a87c7b
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56e871c04de07dcb59865bfc7f0e0969f524279ca5cea2e959c083a9b613ffa3
+size 104504
diff --git a/marked/Rel-16/37_series/37823/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/37_series/37823/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4e3218fab75e3ef0010be64f16137c08926fe3a
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ee34da909e2b424837b6a29e5f6bf9bd364745953773775889a89d9e054de280
+size 57456
diff --git a/marked/Rel-16/37_series/37823/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg b/marked/Rel-16/37_series/37823/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a5e66b2964ff7f9d84a83d8f3a0c725ac6f408e2
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05a7f3445fd2058d4e7940a74e0afc8077203029a8499ed7994c48eb47ec7f23
+size 226557
diff --git a/marked/Rel-16/37_series/37823/raw.md b/marked/Rel-16/37_series/37823/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..16805bbab3c1201e9b7b0dc0ef73c03486e48347
--- /dev/null
+++ b/marked/Rel-16/37_series/37823/raw.md
@@ -0,0 +1,770 @@
+
+
+# 3GPP TR 37.823 V16.0.0(2020-06) ---
+
+*Technical Report*
+
+**3rd Generation Partnership Project;  
+Technical Specification Group Radio Access Network;  
+Coexistence between LTE-MTC and NR  
+(Release 16 )**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green, curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" and "P" are connected at the top. Below the "P" is a small red and white signal icon. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+## --- **Keywords**
+
+<keyword[, keyword]>
+
+## **3GPP**
+
+## --- **Postal address**
+
+### --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## --- Contents
+
+|                                                                                                     |           |
+|-----------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                      | 4         |
+| 1 Scope.....                                                                                        | 5         |
+| 2 References.....                                                                                   | 5         |
+| 3 Definitions, symbols and abbreviations .....                                                      | 5         |
+| 3.1 Definitions.....                                                                                | 5         |
+| 3.2 Symbols.....                                                                                    | 5         |
+| 3.3 Abbreviations .....                                                                             | 6         |
+| 4 Background .....                                                                                  | 6         |
+| 5 Frequency band support for coexistence.....                                                       | 6         |
+| 6 LTE-MTC in-band deployment configurations .....                                                   | 8         |
+| 7 Channel raster, PRB and subcarrier grid alignment.....                                            | 10        |
+| 7.1 Minimal guard band, subcarrier grid alignment for LTE based and SCS based channel rasters ..... | 11        |
+| 7.2 PRB alignment .....                                                                             | 12        |
+| 7.2.3 Quantitative analysis .....                                                                   | 14        |
+| 7.2.4 Summary .....                                                                                 | 17        |
+| 8 Simultaneous operation with LTE-MTC and NR.....                                                   | 17        |
+| 8.3.1 Signalling range .....                                                                        | 20        |
+| 8.3.2 Minimum NR BS requirements for RE Power control dynamic range.....                            | 21        |
+| 9 Synchronization issue between LTE-MTC and NR .....                                                | 22        |
+| 10 Testability applicability.....                                                                   | 24        |
+| 11 LTE-MTC coexisting with NR specific feature in R16.....                                          | 24        |
+| 11.1 Subcarrier puncturing .....                                                                    | 24        |
+| 11.2 Resource reservation .....                                                                     | 24        |
+| 12 Summary .....                                                                                    | 24        |
+| <b>Annex A: Change history .....</b>                                                                | <b>26</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is a technical report for the work item of R16 LTE-M [2]. The scope of the TR is as follows:
+
+- For LTE-MTC in-band operation co-existence with NR, RAN4 will investigate the following:
+  - 15 kHz, 30 kHz, and 60 kHz numerologies for NR FR1 bands, with higher priority given first to 15 kHz and then to 30 kHz
+  - Study feasible LTE-MTC placement allocation without RF backward compatibility impact and compatible with Rel-13 LTE-MTC and Rel-15 NR, to operate simultaneously within various NR channel bandwidths
+  - Channel raster, PRB and subcarrier grid alignment between LTE-MTC and NR
+  - Synchronization issue between LTE-MTC and NR, including timing advance
+  - Frequency band support in LTE-MTC and NR
+  - Testability applicability
+  - Compatibility for Rel-15 NR and Rel-13/14/15 LTE-MTC
+
+The case of NR configured with 15 kHz SS block SCS and the case of 30 kHz SS block SCS as specified in 38.101-1 are included in the study. The Rel-16 LTE-MTC and NR coexisting feature
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] RP-190770, "Revised WID for Additional MTC enhancements for LTE"
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Background
+
+In R15, LTE coexisting within a NR carrier is a feature enabling the flexible NR deployment targeting to achieve minimal impact the legacy LTE service. As LTE-MTC service is delivered within a LTE carrier, in general LTE-MTC co-existence with NR will follow the generic framework of the co-existence with NR and LTE. The focus of co-existing LTE-MTC and NR is to deploy MTC service within a NR carrier. The main benefit of the deploy MTC service within NR carrier is that the MTC legacy device and service will be migrate to the 5G network smoothly without backward compatibility issue.
+
+# --- 5 Frequency band support for coexistence
+
+Up to Rel-15, LTE-MTC can operate in the following LTE bands.
+
+UE category M1 and M2 is designed to operate in the E-UTRA operating bands 1, 2, 3, 4, 5, 7, 8, 11, 12, 13, 14, 18, 19, 20, 21, 25, 26, 27, 28, 31, 66, 71, 72, 73, 74 and 85 in both half duplex FDD mode and full-duplex FDD mode, and in bands 39, 40 and 41 in TDD mode.
+
+In Rel-15, the NR operating bands in FR1 are specified as below (see note below the table).
+
+**Table 5-1: NR operating bands in FR1(3GPP TS 38.104)**
+
+| <b>NR operating band</b> | <b>Uplink (UL) operating band<br/>BS receive / UE transmit<br/><math>F_{UL,low} - F_{UL,high}</math></b> | <b>Downlink (DL) operating band<br/>BS transmit / UE receive<br/><math>F_{DL,low} - F_{DL,high}</math></b> | <b>Duplex Mode</b> |
+|--------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------------|
+| n1                       | 1920 MHz – 1980 MHz                                                                                      | 2110 MHz – 2170 MHz                                                                                        | FDD                |
+| n2                       | 1850 MHz – 1910 MHz                                                                                      | 1930 MHz – 1990 MHz                                                                                        | FDD                |
+| n3                       | 1710 MHz – 1785 MHz                                                                                      | 1805 MHz – 1880 MHz                                                                                        | FDD                |
+| n5                       | 824 MHz – 849 MHz                                                                                        | 869 MHz – 894 MHz                                                                                          | FDD                |
+| n7                       | 2500 MHz – 2570 MHz                                                                                      | 2620 MHz – 2690 MHz                                                                                        | FDD                |
+| n8                       | 880 MHz – 915 MHz                                                                                        | 925 MHz – 960 MHz                                                                                          | FDD                |
+| n12                      | 699 MHz – 716 MHz                                                                                        | 729 MHz – 746 MHz                                                                                          | FDD                |
+| n20                      | 832 MHz – 862 MHz                                                                                        | 791 MHz – 821 MHz                                                                                          | FDD                |
+| n25                      | 1850 MHz – 1915 MHz                                                                                      | 1930 MHz – 1995 MHz                                                                                        | FDD                |
+| n28                      | 703 MHz – 748 MHz                                                                                        | 758 MHz – 803 MHz                                                                                          | FDD                |
+| n34                      | 2010 MHz – 2025 MHz                                                                                      | 2010 MHz – 2025 MHz                                                                                        | TDD                |
+| n38                      | 2570 MHz – 2620 MHz                                                                                      | 2570 MHz – 2620 MHz                                                                                        | TDD                |
+| n39                      | 1880 MHz – 1920 MHz                                                                                      | 1880 MHz – 1920 MHz                                                                                        | TDD                |
+| n40                      | 2300 MHz – 2400 MHz                                                                                      | 2300 MHz – 2400 MHz                                                                                        | TDD                |
+| n41                      | 2496 MHz – 2690 MHz                                                                                      | 2496 MHz – 2690 MHz                                                                                        | TDD                |
+| n50                      | 1432 MHz – 1517 MHz                                                                                      | 1432 MHz – 1517 MHz                                                                                        | TDD                |
+| n51                      | 1427 MHz – 1432 MHz                                                                                      | 1427 MHz – 1432 MHz                                                                                        | TDD                |
+| n65                      | 1920 MHz – 2010 MHz                                                                                      | 2110 MHz – 2200 MHz                                                                                        | FDD                |
+| n66                      | 1710 MHz – 1780 MHz                                                                                      | 2110 MHz – 2200 MHz                                                                                        | FDD                |
+| n70                      | 1695 MHz – 1710 MHz                                                                                      | 1995 MHz – 2020 MHz                                                                                        | FDD                |
+| n71                      | 663 MHz – 698 MHz                                                                                        | 617 MHz – 652 MHz                                                                                          | FDD                |
+| n74                      | 1427 MHz – 1470 MHz                                                                                      | 1475 MHz – 1518 MHz                                                                                        | FDD                |
+| n75                      | N/A                                                                                                      | 1432 MHz – 1517 MHz                                                                                        | SDL                |
+| n76                      | N/A                                                                                                      | 1427 MHz – 1432 MHz                                                                                        | SDL                |
+| n77                      | 3300 MHz – 4200 MHz                                                                                      | 3300 MHz – 4200 MHz                                                                                        | TDD                |
+| n78                      | 3300 MHz – 3800 MHz                                                                                      | 3300 MHz – 3800 MHz                                                                                        | TDD                |
+| n79                      | 4400 MHz – 5000 MHz                                                                                      | 4400 MHz – 5000 MHz                                                                                        | TDD                |
+| n80                      | 1710 MHz – 1785 MHz                                                                                      | N/A                                                                                                        | SUL                |
+| n81                      | 880 MHz – 915 MHz                                                                                        | N/A                                                                                                        | SUL                |
+| n82                      | 832 MHz – 862 MHz                                                                                        | N/A                                                                                                        | SUL                |
+| n83                      | 703 MHz – 748 MHz                                                                                        | N/A                                                                                                        | SUL                |
+| n84                      | 1920 MHz – 1980 MHz                                                                                      | N/A                                                                                                        | SUL                |
+| n86                      | 1710 MHz – 1780 MHz                                                                                      | N/A                                                                                                        | SUL                |
+| n90                      | 2496 MHz – 2690 MHz                                                                                      | 2496 MHz – 2690 MHz                                                                                        | TDD                |
+
+Note: The TDD operating band n90 is introduced in Rel-16 specifications as release independent band from Rel-15. Therefore, it is also added in Table 5-1 as it supports coexistence with LTE-MTC.
+
+Hence potentially LTE-MTC can be operated in the following NR bands in Rel-15.
+
+**Table 5-2: NR operating bands supporting LTE-MTC coexistence in Rel-15.**
+
+| NR operating band | Duplex Mode | Channel raster(kHz) | Max NR CBW (MHz) | Support of eMTC | Support of 7.5 kHz shift |
+|-------------------|-------------|---------------------|------------------|-----------------|--------------------------|
+| n1                | FDD         | 100                 | 20               | yes             | yes                      |
+| n2                | FDD         | 100                 | 20               | yes             | yes                      |
+| n3                | FDD         | 100                 | 30               | yes             | yes                      |
+| n5                | FDD         | 100                 | 20               | yes             | yes                      |
+| n7                | FDD         | 100                 | 20               | yes             | yes                      |
+| n8                | FDD         | 100                 | 20               | yes             | yes                      |
+| n12               | FDD         | 100                 | 20               | yes             | yes                      |
+| n20               | FDD         | 100                 | 20               | yes             | yes                      |
+| n25               | FDD         | 100                 | 20               | yes             | yes                      |
+| n28               | FDD         | 100                 | 20               | yes             | yes                      |
+| n39               | TDD         | 100                 | 40               | yes             |                          |
+| n40               | TDD         | 100                 | 100              | yes             |                          |
+| n41               | TDD         | 15/30               | 100              | yes             |                          |
+| n66               | FDD         | 100                 | 40               | yes             | yes                      |
+| n71               | FDD         | 100                 | 20               | yes             | yes                      |
+| n74               | FDD         | 100                 | 20               | yes             | yes                      |
+| n90               | TDD         | 15/30/100           | 100              | yes             | yes                      |
+
+# 6 LTE-MTC in-band deployment configurations
+
+Coexistence with NR is considered for LTE-MTC in-band operation within frequency bands listed in section 5. Different in-band deployment configurations based on FDM and TDM exist, which are considered below for different NR channel bandwidths.
+
+For coexistence between NR and LTE-MTC in-band operation using FDM, the overlapping between static SSB signals occupying 20 RBs and the centre 6 PRBs of the LTE-MTC Narrowband (NB) carrying LTE PSS and NSS as well as PBCH channel needs to be avoided, since these signals are always active and thus generate interference to the coexisting system.
+
+## 6.1 NR channel bandwidth: 5 MHz
+
+For NR channel bandwidth of 5 MHz and SCS=15 kHz, 25 NR RBs can be allocated. The SSB signal occupies 20 RBs (3,6 MHz) leaving only 5 PRBs (0.9 MHz), which is too small for allocating 6 centre PRBs for LTE using FDM. Thus, for NR channel bandwidth of 5 MHz, only mixed TDM / FDM based co-existence is possible, requiring multiplexing of LTE-MTC and NR static signals in the time domain to avoid collision overlap, whilst other LTE-MTC and NR signals can be scheduled at the same time but on different RBs. This can be done in NR using symbol-level bitmap in the time-domain with repetition pattern in order to reserve resource for LTE-MTC. In LTE-MTC, resource can be reserved (that will be used by NR) using invalid subframe bitmap or MBSFN subframe configuration. Enhancements in Rel-16 are being investigated within the feature enhanced resource reservation. Further detail on mixed TDM / FDM is given in the section 8 on simultaneously operation with LTE-MTC and NR.
+
+Note: For the mixed TDM / FDM based coexistence in this NR channel bandwidth, SCS of 30 kHz is not considered for NR as the guard band on the channel edge is twice as large as for SCS of 15 kHz.
+
+## 6.2 NR channel bandwidth: 10 MHz
+
+For NR channel bandwidth of 10 MHz and SCS=15 kHz, 52 NR RBs can be allocated. The SSB signal occupies 20 RBs (3.6 MHz) leaving an allocation of at least 16 RBs on one side of the SSB to place the centre 6 LTE PRBs. Taking into account that LTE requires a 5% guard band (single sided), the guard band for LTE-MTC 1.4 MHz equals 160 kHz and hence is less than the NR 10 MHz guard band (312.5 kHz). Thus, no extra guard band towards the channel edge is needed for this LTE-MTC NB allocation. Therefore, the LTE-MTC NB allocation may be placed at the outer NR RBs or closer to the SSB. Hence aside a mixed TDM/FDM based approach, a FDM based approach is possible for this NR channel bandwidth, which allows to place, in addition to the LTE-MTC NB allocation containing synchronization and broadcast channels and DC carrier, an LTE-MTC NB with 6 PRBs without DC carrier (e.g. adjacent to each other) on one side of the NR SSB, thus serving two LTE-MTC NB allocations, leaving room for NR CORESET and NR traffic channel. Further LTE-MTC NB allocations in case of higher LTE-MTC traffic may be possible, depending on the location of the SSB. Figure 6-1 below shows both deployment cases.
+
+Note: the exact number of available PRBs for LTE-M depends on the NR sync raster and the NR carrier frequency. The consideration for SCS = 30 kHz is FFS. For multiple numerologies a guard band between NR and LTE-MTC NB allocations may be needed, see section 8.2.
+
+## 6.3 NR channel bandwidth: 15 MHz
+
+For NR channel bandwidth of 15 MHz and SCS=15 kHz, 79 RBs, respectively, can be allocated. The SSB signal occupies 20 RBs (3.6 MHz) leaving an allocation of at least 29 RBs, respectively, on one side of the SSB to place the centre 6 LTE PRBs and up to 3 LTE NBs without DC carrier (i.e. adjacent to each other), in total 4 LTE-MTC NB allocations, taking into account that the outer NR RBs again can be used by LTE-MTC NB allocations, similar as for 10 MHz channel bandwidth. Therefore, the LTE-MTC NB allocations may be placed at the outer NR RBs or closer to the SSB. Hence aside a mixed TDM/FDM based approach a FDM based approach is possible for this NR channel bandwidth placing LTE-MTC NB allocations on one side of the NR SSB, leaving room for the NR CORESET and NR traffic channel. Further LTE-MTC NB allocations in case of higher LTE-MTC traffic may be possible, depending on the location of the SSB.
+
+Note: the exact number of available PRBs for LTE-M depends on the NR sync raster and the NR carrier frequency. The consideration for SCS = 30 kHz is FFS. For multiple numerologies a guard band between NR and LTE-MTC NB allocations may be needed, see section 8.2.
+
+This NR channel bandwidth also allows to deploy an LTE-MTC 5 MHz inband allocation on one side of the SSB. Again, the guard band towards NR channel edge for the LTE allocation is lower than for NR (250 kHz vs. 382,5 kHz), hence outer NR RBs can be used as well. Within the LTE-MTC 5 MHz allocation, LTE NB allocations can be assigned to MTC UEs. This inband configuration can be used to also serve Cat M2 and non-BL CE UEs in coexistence scenarios.
+
+Figure 6-1 below shows both deployment cases.
+
+NR channel bandwidths, larger than 15 MHz and ranging up to 100 MHz, are also relevant for coexistence with LTE-MTC, and require similar approaches as depicted above.
+
+Figure 6-1 illustrates the above depicted exemplary LTE-MTC in-band deployment configurations using FDM. For 5 MHz NR channel bandwidth, no FDM between NR and LTE-MTC is possible, thus mixed TDM / FDM must be used.
+
+![Figure 6-1: Exemplary in-band LTE-MTC deployment configurations including legacy 5 MHz LTE allocation for different NR channel bandwidths using FDM. The diagram shows four configurations for NR 10 MHz and NR 15 MHz bandwidths, illustrating the placement of NR, SSB, and LTE-MTC components within the available Resource Blocks (RBs).](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates four exemplary in-band LTE-MTC deployment configurations using Frequency Division Multiplexing (FDM) for different NR channel bandwidths.
+
+- NR 10 MHz (52 RBs):**
+  - The top configuration shows the NR channel (green) containing an SSB (green) and an LTE NB with DC (orange). The total bandwidth is 52 RBs. A note indicates "6 PRBs + DC" for the LTE NB with DC.
+  - The bottom configuration shows the NR channel (green) containing an SSB (green) and two LTE NBs (orange): one with DC and one without DC. The total bandwidth is 52 RBs. A note indicates "20 RBs" for the NR part and "12 PRBs + DC" for the LTE part. A legend indicates "unused sub-carriers due to LTE-MTC DC sub-carrier" for the gap between the two LTE NBs.
+- NR 15 MHz (79 RBs):**
+  - The top configuration shows the NR channel (green) containing an SSB (green) and four LTE NBs (orange): three without DC and one with DC. The total bandwidth is 79 RBs. A note indicates "20 RBs" for the NR part and "24 PRBs + DC" for the LTE part. A note indicates  $\geq 29$  RBs for the total LTE part.
+  - The bottom configuration shows the NR channel (green) containing an SSB (green) and three LTE NBs (orange): two without DC and one 5 MHz LTE allocation. The total bandwidth is 79 RBs. A note indicates "20 RBs" for the NR part and "25 PRBs + DC" for the LTE part. A note indicates  $\geq 29$  RBs for the total LTE part.
+
+Figure 6-1: Exemplary in-band LTE-MTC deployment configurations including legacy 5 MHz LTE allocation for different NR channel bandwidths using FDM. The diagram shows four configurations for NR 10 MHz and NR 15 MHz bandwidths, illustrating the placement of NR, SSB, and LTE-MTC components within the available Resource Blocks (RBs).
+
+Figure 6-1: Exemplary in-band LTE-MTC deployment configurations including legacy 5 MHz LTE allocation for different NR channel bandwidths using FDM.
+
+# 7 Channel raster, PRB and subcarrier grid alignment
+
+## 7.1 Minimal guard band, subcarrier grid alignment for LTE based and SCS based channel rasters
+
+![Figure 7.1-1: LTE EARFCN configuration within NR carrier with NR channel raster = 100kHz. The diagram shows three horizontal frequency axes. The top axis represents the LTE subcarrier grid with green blocks representing Resource Blocks (RBs) and a central 'DC subcarrier'. The middle axis shows the NR channel raster with yellow blocks representing RBs (RB0, RB25, RB26, RB51) and a 'RE0 in RB26' marker. The bottom axis is the 'NR and LTE channel raster' with 100kHz spacing. Vertical dashed lines indicate alignment points: 'NR ARFCN' at RE0 in RB26, 'LTE EARFCN' at the DC subcarrier, and a distance 'M*300kHz' between them, noted as the 'Least common multiple of 15kHz and 100kHz'.](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+Figure 7.1-1: LTE EARFCN configuration within NR carrier with NR channel raster = 100kHz. The diagram shows three horizontal frequency axes. The top axis represents the LTE subcarrier grid with green blocks representing Resource Blocks (RBs) and a central 'DC subcarrier'. The middle axis shows the NR channel raster with yellow blocks representing RBs (RB0, RB25, RB26, RB51) and a 'RE0 in RB26' marker. The bottom axis is the 'NR and LTE channel raster' with 100kHz spacing. Vertical dashed lines indicate alignment points: 'NR ARFCN' at RE0 in RB26, 'LTE EARFCN' at the DC subcarrier, and a distance 'M\*300kHz' between them, noted as the 'Least common multiple of 15kHz and 100kHz'.
+
+Figure 7.1-1: LTE EARFCN configuration within NR carrier with NR channel raster = 100kHz
+
+![Figure 7.1-2: LTE EARFCN configuration within NR carrier with NR channel raster = 15kHz or 30kHz. The top part shows the NR channel raster (15kHz/30kHz) with a frequency axis 'f' and a distance 'K*300kHz' between two points. The bottom part shows the LTE channel raster (100kHz) with a frequency axis 'f' and a distance 'M*300kHz' between two points, noted as the 'Least common multiple of 15/30kHz and 100kHz'. Both diagrams show alignment of the NR ARFCN (499200) and EARFCN (39650) at 2496MHz.](b712e7522f1bb7135730c7d1abb46d43_img.jpg)
+
+Figure 7.1-2: LTE EARFCN configuration within NR carrier with NR channel raster = 15kHz or 30kHz. The top part shows the NR channel raster (15kHz/30kHz) with a frequency axis 'f' and a distance 'K\*300kHz' between two points. The bottom part shows the LTE channel raster (100kHz) with a frequency axis 'f' and a distance 'M\*300kHz' between two points, noted as the 'Least common multiple of 15/30kHz and 100kHz'. Both diagrams show alignment of the NR ARFCN (499200) and EARFCN (39650) at 2496MHz.
+
+Figure 7.1-2: LTE EARFCN configuration within NR carrier with NR channel raster = 15kHz or 30kHz
+
+In LTE channel raster setting in downlink, there is a DC subcarrier where the LTE EARFCN coincides with the center of this subcarrier. Because the NR channel raster definition considers the co-existence with 100kHz channel raster and subcarrier alignment with LTE, for the NR bands that support the LTE-MTC co-existence with 100kHz channel raster for FDD band, the LTE EARFCN can coincide with NR ARFCN at the same frequency location on the center of NR carrier. This means for downlink the LTE and NR can be aligned in the subcarrier level, but not in PRB level due to the DC subcarrier in LTE.
+
+When NR channel raster is 100kHz, as Figure 7.1-1 shows, if LTE carrier is configured with other EARFCN than the center of NR carrier (NR-ARFCN), due to the subcarrier alignment and 100kHz raster, the EARFCN coinciding with NR channel raster will be multiple of 300kHz offset which is the least common multiple of 15kHz and 100kHz. In Figure 7-2, an example is given for a 10MHz NR carrier and a 5 MHz LTE carrier.
+
+When NR channel raster is 15kHz or 30kHz (e.g n41), to have the subcarrier aligned with LTE and NR, the LTE EARFCN need to have multiple 300kHz offset with NR ARFCN as shown in Figure 7.2-2. For example, when  $K=M$ , LTE EARFCN will coincide with NR ARFCN, the subcarrier alignment will be achieved. In another case, if  $K$  is not equal to  $M$ , there will be multiple 300kHz between EARFCN and NR-ARFCN, and the subcarrier alignment will still be achieved.
+
+## 7.2 PRB alignment
+
+### 7.2.1 Impact of LTE-MTC Narrowband Operation
+
+LTE-MTC UEs reuse legacy LTE PSS/SSS/PBCH for initial cell selection, which occupies the centre 72 subcarriers in the system BW excluding the DC subcarrier. After MSG1 in the random access procedure, the UE may use only 6 PRBs in a narrowband for transmissions and receptions if no frequency-hopping is configured. Otherwise hopping between multiple narrowbands may be performed. The mapping between the narrowband and the PRB is defined in 3GPP TS 36.211 [3] Section 6.2.7. Figure 7.2-1 illustrates the mapping for system BW up to 5 MHz.
+
+![Figure 7.2.1-1: Mapping between LTE PRB and Narrowband. A table showing the mapping of PRBs to narrowbands for system bandwidths of 1.4, 3, and 5 MHz. PRBs are numbered 0 to 24. Narrowbands are numbered 0, 1, 2, and 3. Unused PRBs are shown in grey, and narrowbands are shown in yellow.](624d9669faa18991d525fea5f0e03269_img.jpg)
+
+| PRB | System BW (MHz) |        |   |                          |   |
+|-----|-----------------|--------|---|--------------------------|---|
+|     | 1.4             | 3      | 5 |                          |   |
+| 0   | 0               | unused | 0 | unused PRB<br>narrowband |   |
+| 1   |                 | 0      |   |                          |   |
+| 2   |                 | 0      |   |                          | 1 |
+| 3   |                 | 0      |   |                          |   |
+| 4   |                 | 0      |   |                          |   |
+| 5   |                 | 0      |   |                          |   |
+| 6   | unused          | 2      |   |                          |   |
+| 7   | unused          |        |   |                          |   |
+| 8   | 1               |        |   |                          |   |
+| 9   | 1               |        |   |                          |   |
+| 10  | 1               |        |   |                          |   |
+| 11  | 1               |        |   |                          |   |
+| 12  | 1               | 3      |   |                          |   |
+| 13  | 1               |        |   |                          |   |
+| 14  | 1               |        |   |                          |   |
+| 15  | 1               |        |   |                          |   |
+| 16  | 1               |        |   |                          |   |
+| 17  | 1               |        |   |                          |   |
+| 18  | 1               |        |   |                          |   |
+| 19  | 1               |        |   |                          |   |
+| 20  | 1               |        |   |                          |   |
+| 21  | 1               |        |   |                          |   |
+| 22  | 1               |        |   |                          |   |
+| 23  | 1               |        |   |                          |   |
+| 24  | 1               |        |   |                          |   |
+
+Figure 7.2.1-1: Mapping between LTE PRB and Narrowband. A table showing the mapping of PRBs to narrowbands for system bandwidths of 1.4, 3, and 5 MHz. PRBs are numbered 0 to 24. Narrowbands are numbered 0, 1, 2, and 3. Unused PRBs are shown in grey, and narrowbands are shown in yellow.
+
+Figure 7.2.1-1 Mapping between LTE PRB and Narrowband
+
+For up to at least Rel-15 LTE-MTC operation in NR in-band, the number of NR PRBs reserved for LTE-MTC should be large enough to accommodate all the PRBs within the LTE transmission BW configuration. Particularly, the PUCCH channel in the UL always uses the edge PRBs within the system BW.
+
+### 7.2.2 Intuitive Analysis
+
+Consider the case of SCS=15 kHz for NR. A total of  $N_{\text{RB}}^{\text{DL}} + 1$  consecutive NR PRBs in the DL need to be reserved for LTE-MTC owing to the unused DC subcarrier. The set of allowed values for  $N_{\text{RB}}^{\text{DL}}$  is given by 3GPP TS 36.104.
+
+Depending on the parity of  $N_{\text{RB}}^{\text{DL}}$ , the DC subcarrier is either in the middle of a LTE PRB or in between two LTE PRBs. It's easily seen that LTE PRBs can be aligned with NR PRBs if the following conditions are satisfied, and at most half of the PRBs in the LTE system BW can be aligned:
+
+- 1) The LTE DC subcarrier coincides with
+  - a) the lowest (highest) subcarrier, i.e. subcarrier index 0 (11) of a NR PRB if  $N_{\text{RB}}^{\text{DL}}$  is even;
+  - b) the middle subcarrier, i.e. subcarrier index 6 (5) of a NR PRB if  $N_{\text{RB}}^{\text{DL}}$  is odd;
+- 2) The LTE PRB is on the lower (upper) side of the LTE DC subcarrier.
+
+In the UL, the LTE DC subcarrier is a valid subcarrier that belongs to a PRB and a 7.5 kHz frequency shift is employed to mitigate the effect of carrier leakage. Hence, the LTE PRBs may be aligned with the NR PRBs only if the operating NR band also supports 7.5 kHz frequency shift. Furthermore, owing to the restrictions of TX-RX frequency separation as defined in 3GPP TS 36.101, the aforementioned conditions on the DL DC subcarrier should be met so that the LTE DL PRBs on the lower side of the DC subcarrier are aligned with the NR DL PRBs. As a result, all of the LTE UL PRBs can be aligned with the NR UL PRBs.
+
+Figure 7.2-2 illustrates an example of 1.4 MHz LTE carrier inside a NR carrier. In the DL, the LTE DC subcarrier coincides with the subcarrier 0 of an NR PRB. As a result, LTE PRB 0, 1 and 2 are aligned with NR PRBs. In the UL, all LTE PRBs are aligned with NR PRBs after 7.5 kHz shift. Additionally, Figure 7.2-3 illustrates an example of 3 MHz LTE carrier inside a NR carrier. In the DL, the LTE DC subcarrier coincides with the subcarrier 6 of an NR PRB. As a result, LTE PRB 0-6 are aligned with NR PRBs. In the UL, all LTE PRBs are aligned with NR PRBs after 7.5 kHz shift.
+
+![Figure 7.2.2-1: Example PRB alignment for a 1.4 MHz LTE carrier (having one LTE-MTC NB) inside a NR carrier. The diagram shows two frequency spectra: DL (Downlink) and UL (Uplink). In the DL, the LTE DC subcarrier (red dashed line) coincides with the subcarrier 0 of an NR PRB (blue solid line). The LTE PRBs (red dashed boxes) are numbered 0, 1, 2, 3, 4, 5. The NR PRBs are numbered 0, 1, 2, 3, 4, 5. In the UL, the LTE DC subcarrier (red dashed line) is shifted by 7.5 kHz. The legend indicates NR RB (blue solid line) and LTE RB (red dashed line).](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+The diagram illustrates the PRB alignment for a 1.4 MHz LTE carrier within an NR carrier. It is divided into two horizontal sections: DL (Downlink) and UL (Uplink). A legend at the top left shows a blue solid rectangle for 'NR RB' and a red dashed rectangle for 'LTE RB'. In the DL section, a red vertical line labeled 'LTE DC' points to the boundary between NR PRB 2 and 3. The LTE PRBs are labeled 0, 1, 2, 3, 4, 5. In the UL section, a red vertical line labeled 'LTE DC' points to the boundary between NR PRB 3 and 4. The LTE PRBs are also labeled 0, 1, 2, 3, 4, 5. The NR PRBs are shown as blue solid rectangles, and the LTE PRBs are shown as red dashed rectangles.
+
+Figure 7.2.2-1: Example PRB alignment for a 1.4 MHz LTE carrier (having one LTE-MTC NB) inside a NR carrier. The diagram shows two frequency spectra: DL (Downlink) and UL (Uplink). In the DL, the LTE DC subcarrier (red dashed line) coincides with the subcarrier 0 of an NR PRB (blue solid line). The LTE PRBs (red dashed boxes) are numbered 0, 1, 2, 3, 4, 5. The NR PRBs are numbered 0, 1, 2, 3, 4, 5. In the UL, the LTE DC subcarrier (red dashed line) is shifted by 7.5 kHz. The legend indicates NR RB (blue solid line) and LTE RB (red dashed line).
+
+**Figure 7.2.2-1: Example PRB alignment for a 1.4 MHz LTE carrier (having one LTE-MTC NB) inside a NR carrier**
+
+![Diagram showing PRB alignment for a 3 MHz LTE carrier inside an NR carrier. The top part shows the Downlink (DL) with 15 LTE RBs (0-14) aligned with NR RBs. The bottom part shows the Uplink (UL) with the same alignment. A vertical red line indicates the LTE DC subcarrier position.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg)
+
+The figure illustrates the Physical Resource Block (PRB) alignment for a 3 MHz LTE carrier (containing two LTE-MTC Narrowbands) within an NR carrier. It is divided into two horizontal sections: DL (Downlink) at the top and UL (Uplink) at the bottom. Each section shows a sequence of 15 LTE RBs, numbered 0 to 14, represented by red dashed rectangles. These LTE RBs are overlaid on a series of NR RBs, represented by blue solid rectangles. A vertical red line, labeled 'LTE DC', indicates the position of the LTE Direct Current subcarrier, which coincides with subcarrier index 7 of the 15 LTE RBs. The alignment shows that the LTE carrier's subcarriers are partially aligned with the NR carrier's subcarriers.
+
+Diagram showing PRB alignment for a 3 MHz LTE carrier inside an NR carrier. The top part shows the Downlink (DL) with 15 LTE RBs (0-14) aligned with NR RBs. The bottom part shows the Uplink (UL) with the same alignment. A vertical red line indicates the LTE DC subcarrier position.
+
+**Figure 7.2.2-2: Example PRB alignment for a 3 MHz LTE carrier (having two LTE-MTC NBs) inside a NR carrier**
+
+If neither condition #1 nor condition #2 is satisfied, the number of so-called “outlying” subcarriers in the DL LTE carrier would be more than one. The outlying subcarriers are those in the lower/upper edge of the LTE carrier and only partially overlap with a NR RB. Assuming that the LTE DC subcarrier coincides with subcarrier index  $r$
+
+, ( $0 \leq r \leq 11$ ) within a NR RB, the number of outlying subcarriers can be derived as:
+
+**Table 7.2.2-1: Number of outlying subcarriers in LTE-MTC DL**
+
+|                           | Lower edge             | Upper edge            |
+|---------------------------|------------------------|-----------------------|
+| LTE $N_{RB}^{DL}$ is even | $\text{mod}(12-r, 12)$ | $\text{mod}(r+1, 12)$ |
+| LTE $N_{RB}^{DL}$ is odd  | $\text{mod}(6-r, 12)$  | $\text{mod}(r+7, 12)$ |
+
+### 7.2.3 Quantitative analysis
+
+Let  $N_{RB}^{NR}$  and  $N_{RB}^{LTE}$  denote the maximum number of RBs in the NR and LTE carrier, respectively. Let  $F_{REF}^{NR}$  and  $F_c^{LTE}$  denotes the RF reference frequency for NR and carrier frequency for LTE, respectively. It’s known that:
+
+- NR RF reference frequency  $F_{REF}^{NR}$  corresponds to subcarrier 0 of RB  $\frac{N_{RB}^{NR}}{2}$  if  $N_{RB}^{NR}$  is even, and it corresponds to subcarrier 6 of RB  $\left\lfloor \frac{N_{RB}^{NR}}{2} \right\rfloor$  if  $N_{RB}^{NR}$  is odd;
+- LTE carrier frequency  $F_c^{LTE}$  corresponds to the DC subcarrier with extra 7.5 kHz offset in the UL. In the DL, it locates between two adjacent RBs if  $N_{RB}^{LTE}$  is even, and it locates in the middle of a RB if  $N_{RB}^{LTE}$  is odd.
+
+In order to optimize resource utilization, it is desired to align LTE PRBs with NR PRBs (in fact at most half of the PRBs in the DL and all in the UL as described in Section 7.2.2). In the following, we further formulate the conditions described in Section 7.2.2 based on different NR channel raster sizes.
+
+#### 7.2.3.1 NR 100 kHz Channel Raster
+
+For subcarrier alignment (SCS=15 kHz), the NR RF reference frequency and LTE carrier frequency should satisfy the following condition:
+
+$$100m - 100n = 15k \quad (7.2.3.1-1)$$
+
+with:
+
+- $m$  being an integer identifying the LTE carrier on the 100 kHz raster, i.e.  $F_c^{\text{LTE}} = 100m$  kHz;
+- $n$  being an integer identifying the NR carrier on the 100 kHz raster, i.e.  $F_{\text{REF}}^{\text{NR}} = 100n$  kHz;
+- $k$  being an integer representing the subcarrier offset from the NR RF reference frequency.
+
+Re-write Eq. (7.2.3.1-1) as:
+
+$$100(m - n) = 15k \quad (7.2.3.1-2)$$
+
+For the sake of the variable  $k$  being an integer, the value of  $m - n$  has to be a multiple of 3, i.e.,  $m - n = 3p$ , with  $p$  being an integer. Therefore, Eq. (7.2.3.1-2) can be re-written as:
+
+$$k = 20p, \text{ with } p \text{ being an integer } (7.2.3.1-3).$$
+
+This means that the offset of the LTE carrier from the NR RF reference frequency should be a multiple of 20 subcarriers (i.e., a multiple of 300 kHz). We also have  $k > 0$  if the LTE carrier is on the upper side of the NR carrier and  $k < 0$  if the LTE carrier is on the lower side. Next we further derive the LTE carrier position in terms of RB offset as well as subcarrier index within a RB.
+
+If  $N_{\text{RB}}^{\text{NR}}$  is even, the NR RF reference frequency  $F_{\text{REF}}^{\text{NR}}$  corresponds to subcarrier 0 of RB  $\frac{N_{\text{RB}}^{\text{NR}}}{2}$ . Hence, we have:
+
+- $q \triangleq \left\lfloor \frac{k}{12} \right\rfloor$ , the RB offset from the NR RB containing the subcarrier corresponding to  $F_{\text{REF}}^{\text{NR}}$
+- $r \triangleq \text{mod}(k, 12)$ ,  $0 \leq r \leq 11$ , the index of the subcarrier corresponding to  $F_c^{\text{LTE}}$
+
+With these definitions, we re-write  $k = 20p$  as:
+
+$$20p = 12q + r, \quad (7.2.3.1-4)$$
+
+$$\text{or } r = 4(5p - 3q) \quad (7.2.3.1-5).$$
+
+It can be seen that valid values for subcarrier index  $r$  are: 0, 4 and 8. Note that the value of RB offset  $q$  is limited by the NR channel bandwidth, i.e.  $-\left\lfloor \frac{N_{\text{RB}}^{\text{NR}}}{2} \right\rfloor \leq q \leq \left\lfloor \frac{N_{\text{RB}}^{\text{NR}}}{2} \right\rfloor$ . For ensuring subcarrier alignment between the LTE-MTC carrier and the NR carrier, the task is to find a suitable solution of  $(p, q, r)$  that satisfies Eq. (7.2.3.1-4). Further considering PRB alignment, the condition #1a as described in Section 7.2.2 may be met if additional constraint of  $r = 0$  is added. However, the condition #1b as described in Section 7.2.2 can never be met since  $r = 6$  or  $5$  is not valid. This is also indicated by the number of LTE outlying subcarriers corresponding to NR subcarrier index  $r = 0, 4$  or  $8$  as shown in Table 7.2.3.1-1, which matches the observation in RAN1 [4].
+
+**Table 7.2.3.1-1: Number of outlying subcarriers in LTE-MTC DL when the DC subcarrier coincides with NR subcarrier index  $r = 0, 4$  or  $8$  ( $N_{\text{RB}}^{\text{NR}}$  is even)**
+
+|                                         | Lower edge      | Upper edge      |
+|-----------------------------------------|-----------------|-----------------|
+| LTE $N_{\text{RB}}^{\text{DL}}$ is even | <b>0</b> , 8, 4 | <b>1</b> , 5, 9 |
+| LTE $N_{\text{RB}}^{\text{DL}}$ is odd  | 6, 2, 10        | 7, 11, 3        |
+
+Note: The value shown in bold corresponds to the condition #1a in Section 7.2.2.
+
+On the other hand, if  $N_{\text{RB}}^{\text{NR}}$  is odd, the NR RF reference frequency  $F_{\text{REF}}^{\text{NR}}$  corresponds to subcarrier 6 of RB  $\frac{N_{\text{RB}}^{\text{NR}}}{2}$ .
+
+Taking this offset into account, we have  $q \triangleq \left\lfloor \frac{k+6}{12} \right\rfloor$  for RB offset and  $r \triangleq \text{mod}(k + 6, 12)$  for subcarrier index. And Eq. (7.2.3.1-3) can be re-written as:
+
+$$20p + 6 = 12q + r, \quad (7.2.3.1-6)$$
+
+$$\text{or } r = 2 * (10p - 3 * (2q - 1)) \quad (7.2.3.1-7).$$
+
+It can be seen that valid values for subcarrier index  $r$  are: 2, 6 and 10. For ensuring subcarrier alignment between the LTE-MTC carrier and the NR carrier, the task is to find a suitable solution of  $(p, q, r)$  that satisfies Eq. (7.2.3.1-6). Further considering PRB alignment, the condition #1b as described in Section 7.2.2 may be met if additional constraint of  $r = 6$  is added. However, the condition #1a as described in Section 7.2.2 can never be met since  $r = 0$  or 11 is not valid. This is also indicated by the number of LTE outlying subcarriers corresponding to NR subcarrier index  $r = 2, 6$  or 10 as shown in Table 7.2.3.1-2, which matches the observation in RAN1 [4].
+
+**Table 7.2.3.1-2: Number of outlying subcarriers in LTE-MTC DL when the DC subcarrier coincides with NR subcarrier index  $r = 2, 6$  or 10 ( $N_{\text{RB}}^{\text{NR}}$  is odd)**
+
+|                                         | Lower edge      | Upper edge      |
+|-----------------------------------------|-----------------|-----------------|
+| LTE $N_{\text{RB}}^{\text{DL}}$ is even | 10, 6, 2        | 3, 7, 11        |
+| LTE $N_{\text{RB}}^{\text{DL}}$ is odd  | 4, <b>0</b> , 8 | 9, <b>1</b> , 5 |
+
+Note: The value shown in bold corresponds to the condition #1b in Section 7.2.2.
+
+#### 7.2.3.2 NR 15 kHz Channel Raster
+
+Corresponding to the E-UTRA bands that support LTE-MTC, most of the NR counterparts use 100 kHz channel raster. So far, only band n41 uses SCS-based channel raster. For the sake of PRB alignment, only SCS=15 kHz is considered. Considering subcarrier alignment, the NR reference frequency and LTE carrier frequency should satisfy the following condition:
+
+$$100m - 15n = 15k, \quad (7.2.3.2-1)$$
+
+with:
+
+$m$  being an integer identifying the LTE carrier on the 100 kHz raster, i.e.  $F_c^{\text{LTE}} = 100m$  kHz;
+
+$n$  being an integer identifying the NR carrier on the 15 kHz raster, i.e.  $F_{\text{REF}}^{\text{NR}} = 15n$  kHz;
+
+$k$  being an integer representing the subcarrier offset from the NR RF reference frequency.
+
+Rewrite Eq. (7.2.3.1-1) as:
+
+$$100m = 15(n + k). \quad (7.2.3.2-2)$$
+
+This means that the LTE carrier should be on a raster of 300 kHz, i.e.  $m = 3p$ , with  $p$  being an integer. Together with Eq. (7.2.3.2-2), we have:
+
+$$k = 20p - n. \quad (7.2.3.2-3)$$
+
+Reusing the definition of RB offset  $q$  and subcarrier index  $r$  in Section 7.2.3.1, we have:
+
+$$20p - n = 12q + r, \text{ if } N_{\text{RB}}^{\text{NR}} \text{ is even,} \quad (7.2.3.2-4)$$
+
+$$20p - n + 6 = 12q + r, \text{ if } N_{\text{RB}}^{\text{NR}} \text{ is odd.} \quad (7.2.3.2-5)$$
+
+Note that the values of  $p$  and  $q$  are limited by the NR channel bandwidth, e.g.  $-\left\lfloor \frac{N_{\text{RB}}^{\text{NR}}}{2} \right\rfloor \leq q \leq \left\lfloor \frac{N_{\text{RB}}^{\text{NR}}}{2} \right\rfloor$ . For ensuring subcarrier alignment between the LTE-MTC carrier and the NR carrier, the task is to find a suitable solution of  $(p, q, r)$  that satisfies Eq. (7.2.3.2-4) or Eq. (7.2.3.2-5), for a given NR reference frequency, i.e. fixed  $n$ . Further considering PRB alignment, the conditions on subcarrier index  $r$  as described in Section 7.2.2 should be met as additional constraints. Note that such a solution may not always exist.
+
+### 7.2.4 Summary
+
+The conditions for PRB alignment between LTE-MTC carrier and NR carrier are discussed. Section 7.2.2 provides an intuitive analysis, which is confirmed by the quantitative analysis in Section 7.2.3. Additionally, more insights are acquired through the numerical analysis, which are summarized in the following tables.
+
+**Table 7.2.4-1: Conditions for subcarrier alignment between NR and LTE-MTC**
+
+| NR Channel Raster Size | Condition      | Note                                                                                               |
+|------------------------|----------------|----------------------------------------------------------------------------------------------------|
+| 100 kHz                | Eq (7.2.3.1-3) | The frequency offset between the LTE-MTC carrier and the NR carrier should be multiple of 300 kHz. |
+| 15 kHz                 | Eq (7.2.3.2-3) | The LTE-MTC carrier frequency should be a multiple of 300 kHz.                                     |
+
+**Table 7.2.4-2: Constraints on the location of LTE-MTC inside NR in terms of RB offset and subcarrier index**
+
+| NR Channel Raster Size | $N_{RB}^{NR}$ is even | $N_{RB}^{NR}$ is odd |
+|------------------------|-----------------------|----------------------|
+| 100 kHz                | Eq (7.2.3.1-4)        | Eq (7.2.3.1-6)       |
+| 15 kHz                 | Eq (7.2.3.2-4)        | Eq (7.2.3.2-5)       |
+
+Based on the above listed conditions, it is also found that the choice of the NR subcarrier index (within a RB) for placing the LTE-MTC carrier is limited. And different choices result in different number of outlying subcarriers in the LTE-MTC carrier, for which the minimization is usually desired in order to optimize spectrum utilization. Table 7.2.4-3 summarizes the observations for 100 kHz NR channel raster size.
+
+**Table 7.2.4-3: Observations on the NR subcarrier index suitable for LTE MTC and the corresponding number of outlying subcarriers (NR channel raster = 100 kHz)**
+
+|                                | $N_{RB}^{NR}$ is even | $N_{RB}^{NR}$ is odd |
+|--------------------------------|-----------------------|----------------------|
+| Subcarrier index within a RB   | 0, 4, 8               | 2, 6, 10             |
+| Number of outlying subcarriers | Table 7.2.3.1-1       | Table 7.2.3.1-2      |
+
+# 8 Simultaneous operation with LTE-MTC and NR
+
+## 8.1 Collision avoidance for static and other NR signals
+
+When an LTE-M service coexists with NR within a NR carrier, the legacy LTE-M device will operate on the carrier configured as a normal LTE carrier without awareness of NR signals. The NR device, however, could be aware of other technology with NR R15 feature of rate-matching the PDSCH around resource elements used by LTE. For the signal sent from LTE which cannot be rate-matched by the NR device, scheduler or configuration coordination is needed to avoid collision between NR and LTE transmissions (or signals). The LTE signals can be classified as static signals and dynamic signals, where the static signals are “always on” signals and shall be always transmitted. The dynamic signals are traffic specific and scheduled in the real time.
+
+An LTE carrier resource grid for FDD band is shown in Figure 8-1.
+
+![Figure 8-1: Resource grid for downlink signal of the LTE carrier BW=1.4MHz and 4 CRS antenna ports. The grid shows 72 subcarriers (0 to 71) across 10 subframes (0 to 9) of a radio frame. Each subframe contains 7 slots (0 to 6). The grid is color-coded to show various signals: PDSCH (white), PDCCH (light blue), CRS (red), PSS (yellow), SSS (pink), PBCH (green), PHICH (blue), PCFICH (orange), and CSI-RS (purple). The legend on the right identifies these signals.](ef25c3cf1fdb334fc8679e85ab5265ca_img.jpg)
+
+Figure 8-1: Resource grid for downlink signal of the LTE carrier BW=1.4MHz and 4 CRS antenna ports. The grid shows 72 subcarriers (0 to 71) across 10 subframes (0 to 9) of a radio frame. Each subframe contains 7 slots (0 to 6). The grid is color-coded to show various signals: PDSCH (white), PDCCH (light blue), CRS (red), PSS (yellow), SSS (pink), PBCH (green), PHICH (blue), PCFICH (orange), and CSI-RS (purple). The legend on the right identifies these signals.
+
+**Figure 8-1: Resource grid for downlink signal of the LTE carrier BW=1.4MHz and 4 CRS antenna ports.**
+
+As shown in Figure 8-1 for the downlink LTE signal (FDD band) without the scheduled PDSCH,
+
+- 1) PDCCH in the first 1, 2 or 3 symbols depending on the CFI configuration, minimum is 1 symbol for CFI=1 for every subframe (except in the special case with 1.4 MHz system bandwidth when the number of symbols is 2, 3 or 4),
+- 2) PSS/SSS is configured every 5 ms at symbol 5, 6 in the middle 6 PRBs.
+- 3) PBCH is transmitted at slot 1 every 10ms.
+- 4) CRS (4 ports) signal on symbols 0, 1, 4, 7, 8, 11,
+- 5) The DMRS (4 port), on symbols 5, 6, 12, 13,
+- 6) CSI-RS (4 ports) every 10 ms, on symbols 5, 6, 12, 13.
+
+For uplink LTE signals, they are PUCCH and PUSCH, PRACH and SRS which is configurable.
+
+As the DMRS and CSI-RS occupy PDSCH positions, they can be treated as dynamic signals same as PDSCH which is UE specific. NR signals should avoid the overlapping of LTE static signals so the legacy LTE UE performance will not be affected.
+
+For LTE-M, the cell-specific subframe bitmap broadcasted on the System Information (SI) indicates which subframes are capable of LTE-M transmissions. On top of this, there are additional signals MPDCCH and RSS signal:
+
+MPDCCH: MPDCCH carries the LTE-M downlink control information (DCI) and maps to the LTE PDSCH region.
+
+RSS (Resynchronization Signal): Maps to the LTE PDSCH region at periodicity of 8, 16, 32 or 40 subframes and 2 consecutive PRBs.
+
+LTE-M subframes can be configured as valid or invalid for LTE-M transmission, and invalid subframes are not used for LTE-M transmissions. LTE-M signals occupy the NR PDSCH region which makes it possible for an NR UE to perform
+
+rate matching around it. For the PDCCH, PSS/SSS/PBCH in the middle 6 PRBs, and CRS are static signals that are always transmitted.
+
+NR has the following channels and signals:
+
+- 1) SSB, default 20ms periodicity,
+- 2) TRS, needed for PDSCH demodulation
+- 3) CORESET #0 for transmitting PDCCH for SIB1 scheduling SIB1
+- 4) PDCCH at symbol 2,
+- 5) PDSCH + DMRS
+- 6) CSI-RS, symbol 12 and 13
+
+In the NR signals, the SSB signal is a mandatory transmission for the UE initial cell search and thus is a static signal. CORESET #0 is also a static signal which is mandatory to transmit. The other reference signals to help demodulate the PDSCH should not collide with LTE signal so the NR UE performance would be preserved. A solution for avoiding the LTE static signals when NR static signals are transmitted will be needed and one of the options is to use the MBSFN subframes in LTE and the other one is using LTE-MTC invalid subframe bitmaps.
+
+### MBSFN in LTE:
+
+MBSFN is an LTE Release 9 feature, so for the LTE-M from R13, there is no problem for the LTE-M device with the awareness of the MBSFN subframe configuration. The LTE-M will ignore these MBSFN subframes so these MBMS subframes could be used for NR to transmit the static signals or other important signals which otherwise would collide with LTE signals.
+
+The number and locations of MBSFN subframes within a specific radio frame are defined in SIB2 with MBSFN-SubframeConfig IE. It is determined by two parameters radioframeAllocationPeriod and radioframeAllocationOffset, as long as below equation is fulfilled for the MBSFN configuration,
+
+$$[SFN] \bmod [\text{radioframeAllocationPeriod}] = \text{radioframeAllocationOffset}$$
+
+With the MBSFN subframe, LTE-M device could ignore the NR “always on” signal contained in MBSFN frames seen by LTE-M device. Furthermore, in R15, NR can reserve resources using a bitmap for the NR PDSCH region, so NR signals can be rate matched by NR UEs around the resource elements used by LTE signals. By utilizing these methods and scheduler help for uplink, the LTE and NR will avoid the colliding signal each other and can coexist within a NR carrier. Table 8-1 and Table 8-2 lists summary of protection schemes for static signals in two system.
+
+**Table 8-1: NR (SCS=15kHz) solution to avoid the collision with LTE signals**
+
+|                        | Signal   | symbol position | frequency position               | NR solution                            |
+|------------------------|----------|-----------------|----------------------------------|----------------------------------------|
+| <b>LTE-M DL signal</b> | PSS/SSS, | symbol 5, 6     | middle 6 PRB                     | resource reserve with NR rate matching |
+|                        | PBCH     | slot 0          | middle 6 PRB                     | resource reserve with NR rate matching |
+|                        | CRS      | 0,1,4,7,8,11    | interleaved within whole LTE PRB | reserve resource with NR rate matching |
+|                        | DMRS     | 5,6, 12,13      |                                  | resource reserve with NR rate matching |
+|                        | CSI-RS   | 5,6,12,13       |                                  | resource reserve with NR rate matching |
+|                        | PDCCH    | 0,1             |                                  | NR PDCCH only on symbol 2              |
+|                        | PDSCH    |                 |                                  | resource reserve with NR rate matching |
+|                        | MPDCCH   |                 |                                  | resource reserve with NR rate matching |
+| <b>LTE-M UL signal</b> | PRACH    |                 |                                  | Scheduling                             |
+|                        | PUCCH    |                 | edge PRB at LTE BW               | Scheduling                             |
+|                        | SRS      |                 |                                  | Scheduling                             |
+
+**Table 8-2: LTE-M solution to avoid the collision with NR signals (SCS=15kHz)**
+
+|                     | Signal       | symbol position | frequency position  | LTE-M solution                                                                                |
+|---------------------|--------------|-----------------|---------------------|-----------------------------------------------------------------------------------------------|
+| <b>NR DL signal</b> | SSB          | 2,3,4,5         | 20 PRB, sync raster | MBSFN frame and/or configure invalid subframe for LTE-M                                       |
+|                     | CORESET SIB1 |                 |                     | MBSFN frame and/or configure invalid subframe for LTE-M                                       |
+|                     | PDCCH        | 2               |                     | CFI max=2, avoid overlap of LTE PDCCH to NR PDCCH and/or configure invalid subframe for LTE-M |
+|                     | PDSCH        |                 |                     | Scheduling and/or configure invalid subframe for LTE-M                                        |
+|                     | DMRS         |                 |                     | MBSFN and/or configure invalid subframe for LTE-M                                             |
+|                     | TRS          |                 |                     | MBSFN and/or configure invalid subframe for LTE-M                                             |
+|                     | CSI-RS       |                 |                     | MBSFN and/or configure invalid subframe for LTE-M                                             |
+| <b>NR UL signal</b> | PRACH        |                 |                     | Scheduling;                                                                                   |
+|                     | PUCCH        |                 |                     | Scheduling                                                                                    |
+|                     | SRS          |                 |                     | Scheduling                                                                                    |
+
+## 8.2 Numerologies
+
+As NR could support several numerology, e.g. 15KHz, 30KHz and 60KHz in FR1 which might be different from LTE-MTC numerologies (only support 15KHz SCS in downlink and uplink), there might exist mixed numerology configuration which could result in interference between NR subcarrier and LTE-MTC subcarrier In general, guardband between different numerology should be reserved for performance protection, however this should be up to the BS implementation. Similar as the mixed numerology in the NR scenarios, no requirement is defined for mixed numerology between NR and LTE-MTC. In case of LTE-MTC is located close to the channel edge of NR channel bandwidth, the minimum guardband at channel edge is illustrated in Figure 7.1-1.
+
+![Figure 7.1-1: Diagram illustrating the guard band for NR coexist with MTC. The diagram shows a frequency axis (f/Hz) with a 'BS channel bandwidth' indicated by a double-headed arrow. Within this bandwidth, there is a blue block labeled 'MTC' and a green block labeled 'NR'. A red double-headed arrow labeled 'LTE guardband' points to the gap between the MTC block and the left edge of the BS channel bandwidth. A blue double-headed arrow labeled 'NR guardband' points to the gap between the NR block and the right edge of the BS channel bandwidth. A horizontal line labeled 'NR transmission bandwidth configuration' spans the width of the NR block.](e636d7ccca0ad14c6b95201404324823_img.jpg)
+
+Figure 7.1-1: Diagram illustrating the guard band for NR coexist with MTC. The diagram shows a frequency axis (f/Hz) with a 'BS channel bandwidth' indicated by a double-headed arrow. Within this bandwidth, there is a blue block labeled 'MTC' and a green block labeled 'NR'. A red double-headed arrow labeled 'LTE guardband' points to the gap between the MTC block and the left edge of the BS channel bandwidth. A blue double-headed arrow labeled 'NR guardband' points to the gap between the NR block and the right edge of the BS channel bandwidth. A horizontal line labeled 'NR transmission bandwidth configuration' spans the width of the NR block.
+
+Figure 7.1-1. the guard band for NR coexist with MTC
+
+## 8.3 Power boosting for LTE-MTC
+
+This section investigates the impact from power boosting applied to LTE-MTC for coexistence with NR.
+
+### 8.3.1 Signalling range
+
+Power boosting for LTE-MTC was introduced in Rel-15 for the purpose of enhanced coverage and improved power saving. In particular this is applied to
+
+RSS (Re-Synchronization Signal) introduced in Rel-15 to allow the BL/CE UE to perform faster network synchronization in DRX periods after wake-up from light sleep. RSS is transmitted as part of MPDCCH.
+
+RSS uses two consecutive RBs which can be allocated anywhere, according to 3GPP TS 36.331, in the configured LTE channel bandwidth (i.e. frequency location is one RB pair out of 100 RBs covering the 20 MHz bandwidth case).
+
+According to 3GPP TS 36.213, the power offset for RSS EPRE versus CRS EPRE depends on the number of cell specific antenna ports. For one cell specific antenna port, the power offset versus CRS EPRE can be {0, 3, 4.8 and 6 dB}, as specified in 3GPP TS 36.331. Power stealing across other RBs can be applied.
+
+However, RSS is transmitted with given periodicity and at most in 25% of the subframes (3GPP TS 36.331).
+
+MWUS (MTC Wake-Up Signal) introduced in Rel-15 to allow the BL/CE UE to save energy for the purpose of paging monitoring. Rather than to decode the paging channel data for determining if a paging request is received, a wake-up signal was specified to indicate a valid page in the next PO to the UE. MWUS is transmitted as part of MPDCCH.
+
+MWUS uses two consecutive RBs which are allocated in the configured paging narrowband (6 RBs), thus allowing for three disjunct allocations. According to 3GPP TS 36.331, only one RB pair is allocated per cell for MWUS.
+
+According to 3GPP TS 36.213, the power offset for MWUS EPRE versus CRS EPRE depends on the number of cell specific antenna ports. For one cell specific antenna port, the power offset versus CRS EPRE can be {0, 1.8, 3 and 4.8 dB}, as specified in 3GPP TS 36.331. However, MWUS sequence has a limited duration and is not transmitted in all subframes. Power stealing across other RBs can be applied.
+
+GMWUS (group MWUS) added in Rel-16 to allow the BL/CE UEs to be grouped and to dedicate a wake-up signal not to all UEs (common WUS) but to a particular UE group to make paging monitoring even more efficient. GMWUS is transmitted as part of MPDCCH.
+
+GMWUS uses two consecutive RBs which are allocated in the configured paging narrowband (6 RBs), allowing for two disjunct allocations. Up to 2 GMWUS can be allocated per cell. In case 2 GMWUS and 1 MWUS are FDM'ed in the paging narrowband, all 6 RBs in the NB are transmitted.
+
+For GMWUS, the same power offset versus CRS EPRE applies as for MWUS. Thus, for a cell transmitting MWUS and 2 GMWUS, the power offset versus CRS may go up to 4.8 dB in the narrowband, which requires power stealing from outside the narrowband. Again, GMWUS sequence has a limited duration and is not transmitted in all subframes.
+
+Thus, LTE-MTC RBs carrying RSS, MWUS or GMWUS in MPDCCH, can have a higher PSD versus other LTE-MTC RBs of up to 6 dB due to the signalling range.
+
+### 8.3.2 Minimum NR BS requirements for RE Power control dynamic range
+
+On the other side, minimum requirements for power boosting for NR BS exist in 3GPP TS 38.104. In particular, subclause 6.3.2.2 specifies minimum requirements for RE power control dynamic range, where power offset above and below average RE power for a BS at maximum output power is specified. This defines a range between -6 dB and +4 dB for QPSK (PDCCH) and between -6 dB and +3 dB for QPSK (PDSCH), which needs to be supported by the NR BS. These power dynamic ranges are the same as specified for LTE in 3GPP TS 36.104, subclause 6.3.1.1. As MPDCCH maps to LTE PDSCH region and also uses QPSK modulation, from RF perspective similar power boosting performance is expected to be achieved as for NR / LTE RE power boosting for PDSCH (using QPSK).
+
+In conclusion, the NR BS is not mandated to support power boosting for LTE-MTC RBs, which are allocated within the NR transmission bandwidth. The NR BS may support power boosting for LTE-MTC RBs according to the above depicted signalling range, provided that the network still fulfils existing RF performance requirements.
+
+## 8.4 Specific aspects for TDD
+
+LTE-MTC supports all E-UTRA TDD configurations as specified in 3GPP TS 36.211 [3]. In the meantime, NR TDD configurations are very flexible. Not only slots but also individual symbols within a slot can be configured as either DL, UL or flexible (i.e. GP). For the sake of co-existence, the NR TDD configuration should be set up to match that of LTE-MTC.
+
+More explicitly, two different patterns may be configured via the IE TDD-UL-DL-ConfigCommon in SIB1. Furthermore, the common settings may be overridden by UE specific configuration: TDD-UL-DL-ConfigDedicated. Table 8.4-1 shows the details of the RRC signalling.
+
+**Table 8.4-1: RRC Signaling for NR TDD Configuration**
+
+| Field Name                        | Note                                                                                                                                     |
+|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>TDD-UL-DL-ConfigCommon:</b>    | <b>Signalled by SIB1</b>                                                                                                                 |
+| referenceSubcarrierSpacing        | Subcarrier spacing in kHz: 15, 30, 60, etc                                                                                               |
+| dl-UL-TransmissionPeriodicity     | Pattern periodicity in ms                                                                                                                |
+| nrofDownlinkSlots                 | Can be used to configure DL transmissions that matches the duration of DL subframes or forms part of the DwPTS in LTE-MTC                |
+| nrofDownlinkSymbols               | Specifies a partial DL slot, together with other DL slots (if needed), can match the duration of DwPTS in LTE-MTC                        |
+| nrofUplinkSymbols                 | Specifies a partial UL slot, together with other UL slots (if needed), can match the duration of UpPTS in LTE-MTC                        |
+| nrofUplinkSlots                   | Can be used to configure UL transmissions that matches the duration of UL subframes or forms part of the UpPTS in LTE-MTC                |
+| <b>TDD-UL-DL-ConfigDedicated:</b> | UE specific RRC signalling                                                                                                               |
+| slotIndex                         | Depending on the SCS, the duration of a NR slot may be less (i.e. $\frac{1}{2}$ , $\frac{1}{4}$ , etc) or equal to a subframe in LTE-MTC |
+| allDownlink                       | The whole slot is for DL, more than one DL slot may be needed to match the duration of a DL subframe in LTE-MTC                          |
+| allUplink                         | The whole slot is for UL, more than one UL slot may be needed to match the duration of a UL subframe in LTE-MTC                          |
+| nrofDownlinkSymbols               | Specifies a partial DL slot, together with other DL slots (if needed), can match the duration of DwPTS in LTE-MTC                        |
+| nrofUplinkSymbols                 | Specifies a partial UL slot, together with other UL slots (if needed), can match the duration of UpPTS in LTE-MTC                        |
+
+The main limitation of the NR TDD configuration is that the pattern has to be defined in the order of DL, GP and UL. A combination use of TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated shall enable the NR TDD configuration to match that of any LTE UL-DL configuration. For example, Table 8.4-2 shows the NR TDD configuration that matches the LTE-MTC uplink/downlink configuration 1 with the special subframe configuration 7 (i.e. uplink/downlink subframe ratio is 1:1, DwPTS = 10 symbols, GP = 2 symbols, UpPTS = 2 symbols).
+
+**Table 8.4-2: Example of NR TDD configuration which matches with LTE TDD UL/DL configuration 1 and special subframe configuration 7**
+
+| NR TDD                             |             | LTE TDD                          |
+|------------------------------------|-------------|----------------------------------|
+| <b>Tdd-UL-DL-Configuration</b>     |             |                                  |
+| referenceSubcarrierSpacing         | 15          |                                  |
+| dl-UL-TransmissionPeriodicity (ms) | 5           |                                  |
+| nrofDownlinkSlots                  | 1           | Subframe 0 is DL                 |
+| nrofDownlinkSymbols                | 0           |                                  |
+| nrofUplinkSlots                    | 0           |                                  |
+| nrofUplinkSymbols                  | 0           |                                  |
+| <b>Tdd-UL-DL-ConfigDedicated</b>   |             |                                  |
+| slotIndex                          | 1           | Subframe 1 is a special subframe |
+| nrofDownlinkSymbols                | 10          | DwPTS=10                         |
+| nrofUplinkSymbols                  | 2           | UpPTS=2                          |
+| slotIndex                          | 2,3         | Subframe 2,3 is UL               |
+| symbols                            | allUplink   |                                  |
+| slotIndex                          | 4           | Subframe 4 is DL                 |
+| symbols                            | allDownlink |                                  |
+
+# 9 Synchronization issue between LTE-MTC and NR
+
+In order to analyze the LTE-M coexisting with NR, longest CP and shortest CP for NR are considered as two extreme cases in which whether timing misalignment between LTE-M and NR would exceed CP or not could be identified.
+
+If 15kHz SCS is used in the NR carrier where NR has the longest CP, then the TAGs misalignment analysis between LTE-M and NR will be the same as that between LTE-M and E-UTRA. Therefore, there should be no interference issue due to TAGs misalignment between LTE-M and NR if 15kHz SCS is used in the NR system, otherwise such issue would have occurred already between LTE-M and E-UTRA before the migration to NR. Meanwhile some detailed analysis is done in Case 1 where it could be found that timing misalignment between LTE-M and NR is still within the CP, this also indicates there should be no interference issues due to TAGs misalignment.
+
+On the other hand, if 30kHz or 60kHz SCS is used in the NR carrier, the LTE-M UE maximum transmit timing error of  $60T_s (= 48T_s + 4T_s + 8T_s)$  alone as explained in the following will be larger than the CP length of the NR symbol. Therefore, when the NR UE maximum transmit timing error (which is varied according to the SCS used in the NR carrier) is also considered, there would potentially be interference issue due to the inter-symbol-interference between the LTE-M and NR symbols as illustrated in Case 2. However, it has been agreed that this type of mixed numerology cases between LTE-M and NR should be up to the BS implementation and no requirement is defined in the RAN4 specifications. Feasible BS implementation options include separate digital filtering and internal gap between the LTE-M and NR carriers.
+
+## Case 1: the timing misalignment scenario with NR SCS 15KHz
+
+For NR UE transmit timing, if uplink subcarrier spacing is configured with 15KHz and SSB SCS is configured with 15KHz which is specified with worst transmit timing error for uplink SCS 15KHz, the maximum transmit timing error should be  $12 \cdot 64 \cdot T_c + 256 \cdot T_c + 8 \cdot 64 \cdot T_c$  equal to  $(12+4+8) \cdot 64 \cdot T_c$  equal to  $24 \cdot T_s$  which is the same as the maximum LTE UE transmitting error. Based on the above considerations, maximum arrival timing difference between NR carrier and LTE-MTC carrier should be 2.7344us as shown in Figure 8.1 which is less than the NR CP length 4.96us if SCS 15KHz is configured for NR.
+
+![Figure 9.1: Timing diagram for Case 1 (NR SCS 15KHz). It shows a horizontal timeline with a vertical 'Reference timing' line. To the left of the reference line is 'NR UE timing' (red arrow) at a distance of 0.7813us. To the right of the reference line is 'MTC UE timing' (blue arrow) at a distance of 1.9531us. The total distance between NR UE timing and MTC UE timing is labeled as 2.7344us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 15KHz.](d369dc114803a761d452c13ee58ed579_img.jpg)
+
+Figure 9.1: Timing diagram for Case 1 (NR SCS 15KHz). It shows a horizontal timeline with a vertical 'Reference timing' line. To the left of the reference line is 'NR UE timing' (red arrow) at a distance of 0.7813us. To the right of the reference line is 'MTC UE timing' (blue arrow) at a distance of 1.9531us. The total distance between NR UE timing and MTC UE timing is labeled as 2.7344us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 15KHz.
+
+Figure 9.1. the maximum arrival timing difference between NR and LTE-M in Uplink
+
+## Case 2: the timing misalignment scenario with NR SCS 60KHz
+
+For NR UE transmit timing, if uplink subcarrier spacing is configured with 60KHz and SSB SCS configured with 30KHz which is specified with the worst transmit timing error for uplink SCS 60KHz, the maximum transmit timing error should be  $10 \cdot 64 \cdot T_c + 128 \cdot T_c + 8 \cdot 64 \cdot T_c / 4$  equal to  $14 T_s$  (0.4557us). Based on the above consideration, the maximum arrival timing difference between NR carrier and LTE-M carrier should be 2.4088us as shown in Figure 8.2 which is larger than the NR CP length 1.17us if SCS 60KHz is configured for NR.
+
+![Figure 9.2: Timing diagram for Case 2 (NR SCS 60KHz). It shows a horizontal timeline with a vertical 'Reference timing' line. To the left of the reference line is 'NR UE timing' (red arrow) at a distance of 0.4557us. To the right of the reference line is 'MTC UE timing' (blue arrow) at a distance of 1.9531us. The total distance between NR UE timing and MTC UE timing is labeled as 2.4088us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 60KHz.](3b7c13851b2efcae74f526646918fb49_img.jpg)
+
+Figure 9.2: Timing diagram for Case 2 (NR SCS 60KHz). It shows a horizontal timeline with a vertical 'Reference timing' line. To the left of the reference line is 'NR UE timing' (red arrow) at a distance of 0.4557us. To the right of the reference line is 'MTC UE timing' (blue arrow) at a distance of 1.9531us. The total distance between NR UE timing and MTC UE timing is labeled as 2.4088us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 60KHz.
+
+Figure 9.2. the maximum arrival timing difference between NR and LTE-M in Uplink.
+
+# 10 Testability applicability
+
+When LTE-M service is configured within one NR carrier at BS, the LTE-M UE operate it as LTE carrier so no new test on LTE-M UE will be needed.
+
+For a BS supporting both LTE and NR, there is no NR RF impact foreseen because NR can avoid the LTE signal using either dynamic scheduling or MBSFN subframe seen by LTE-M UE. Transmitting LTE signal within a NR carrier does not change the NR signal characteristic and performance (unwanted emission, TX signal quality etc), similarly, receiving a LTE signal on NR BS would not require additional performance requirement. Therefore, no additional test will be needed when LTE-M coexisting within NR carrier. In such case, NR BS RF spec would still apply.
+
+# 11 LTE-MTC coexisting with NR specific feature in R16
+
+## 11.1 Subcarrier puncturing
+
+![Diagram illustrating RB misalignment between NR and LTE-MTC in DL. The top bar represents 6 NR RBs, and the bottom bar represents LTE-M. A dashed vertical line indicates the boundary of the 6 NR RBs. An arrow points to a blue circle on the LTE-M bar, labeled 'Outlying LTE-M subcarrier', which is outside the 6 NR RBs.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg)
+
+The diagram shows two horizontal bars. The top bar is light blue and labeled '6 NR RBs'. The bottom bar is light orange and labeled 'LTE-M'. A dashed vertical line runs through both bars, positioned towards the left side of the top bar. On the bottom bar, to the right of the dashed line, there is a blue circle. An arrow points from the text 'Outlying LTE-M subcarrier' to this circle. The circle is located within the orange bar but outside the area defined by the dashed line relative to the top bar's extent.
+
+Diagram illustrating RB misalignment between NR and LTE-MTC in DL. The top bar represents 6 NR RBs, and the bottom bar represents LTE-M. A dashed vertical line indicates the boundary of the 6 NR RBs. An arrow points to a blue circle on the LTE-M bar, labeled 'Outlying LTE-M subcarrier', which is outside the 6 NR RBs.
+
+Figure 11.1-1: Illustrative example of RB misalignment between NR and LTE-MTC in DL.
+
+In R16, subcarrier puncturing is introduced as a feature to further improve spectrum utilization for the NR coexisting with LTE-MTC deployment scenario. This feature is useful for handling RB misalignment between NR and LTE-MTC in DL, as shown in Figure 11.1-1. By puncturing we refer to the case where the base station avoids transmitting the subcarriers belonging to LTE-MTC with or without informing the UEs. This will cause somewhat degraded performance for the UE whose transmission is punctured (up to 2 subcarrier punctured), but the eNB/gNB scheduler is aware of this, and may compensate by proper adjustment of code rates etc. It should be noted that in DL, since NR UEs can rate match around LTE CRS, there is no need to puncture CRS when it is on outlying subcarriers.
+
+## 11.2 Resource reservation
+
+In R16, finer LTE-MTC resource reservation than subframe level is introduced. LTE-MTC resource reservation for DL can be configured at slot level or symbol level. UL resource reservation for LTE-MTC with slot-level and symbol(s)-level granularity in addition to subframe-level granularity is supported. For DL, frequency-domain resource reservation is also supported, and non-contiguous PRB allocation can be indicated using an RBG bitmap. The unused frequency/time resources for LTE-MTC then can be used by an NR UE. As a result, the NR spectrum utilization will be improved when the traffic on LTE-MTC cell is low.
+
+# 12 Summary
+
+MSR BS supporting NR and E-UTRA can operate NR with LTE-MTC in-band allocation and there is no need to introduce new conformance testing. To ensure efficient operation for coexistence of NR with LTE-MTC, certain technical considerations as described in Chapter 7 & 8 are needed for channel raster, PRB and subcarrier alignment, LTE-MTC power boosting and simultaneous operation of LTE-MTC and NR.
+
+
+
+# Annex A: Change history
+
+| Change history |                |            |    |     |     |                                                             |             |
+|----------------|----------------|------------|----|-----|-----|-------------------------------------------------------------|-------------|
+| Date           | Meeting        | TDoc       | CR | Rev | Cat | Subject/Comment                                             | New version |
+| 2019-04-08     | RAN4#90<br>BIS | R4-1904260 |    |     |     | TR skeleton proposal                                        | V0.0.1      |
+|                |                | R4-1905108 |    |     |     | TP proposal for TR LTE-M and NR coexistence                 |             |
+| 2019-5-13      | RAN4#91        | R4-1906627 |    |     |     | TP on general aspect                                        | V0.1.0      |
+|                |                | R4-1907620 |    |     |     | TP for background and channel raster for TR 36.abc          |             |
+|                |                | R4-1907621 |    |     |     | TP to the new TR related to MTC: mixed numerologies         |             |
+| 2019-10-3      | RAN4#92        | R4-1910482 |    |     |     | TP to the new TR related to MTC: mixed numerologies         | V.0.2.0     |
+|                |                | R4-1910481 |    |     |     | TP for TR 37.832: Testability applicability                 |             |
+|                |                | R4-1910483 |    |     |     | TP for Simultaneously operation with LTE MTC and NR         |             |
+|                |                | R4-1910612 |    |     |     | TP for TR 37.823: LTE-MTC in-band deployment configurations |             |
+| 2019-10-18     | RAN4#92<br>bis | R4-1913001 |    |     |     | TP for TR 37.823: PRB Alignment                             | V.0.3.0     |
+|                |                | R4-1913002 |    |     |     | TP to the new TR related to MTC: TAG misalignment           |             |
+|                |                | R4-1912995 |    |     |     | TP for TR 37.823: Addition of n90 frequency band            |             |
+| 2020-2-11      | RAN4#93        | R4-1915166 |    |     |     | TP for TR 37.823: Correction to n90 frequency band          | V.0.4.0     |
+| 2020-4-10      | RAN4#94<br>e   | R4-2002739 |    |     |     | TP for TR 37.823: Specific aspects for TDD                  | V 0.5.0     |
+|                |                | R4-2002740 |    |     |     | TP for TR 37.823 : R16 RAN1 impact on co-existing           |             |
+| 2020-6-15      | RAN4#95<br>e   | R4-2008423 |    |     |     | TP for TR 37.823: Power boosting for LTE-MTC                | V.1.0.0     |
+|                |                | R4-2008424 |    |     |     | TP to 37.823: Conclusion                                    |             |
+
+| Change history |         |      |    |     |     |                                                        |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2020-06        | RAN#88  |      |    |     |     | Approved by plenary – Rel-16 spec under change control | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37824/03498c9b76f980b32f2dfbb7c2e539d2_img.jpg b/marked/Rel-16/37_series/37824/03498c9b76f980b32f2dfbb7c2e539d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96ac7d52785c2abf299c70018953b12373f4a26e
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/03498c9b76f980b32f2dfbb7c2e539d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f3edb82285cab9dc5ffea12c8a22bf864a6702a09254bd8fdf3fb2f24c44abaa
+size 123179
diff --git a/marked/Rel-16/37_series/37824/051638d871c75230edb3d005fa668810_img.jpg b/marked/Rel-16/37_series/37824/051638d871c75230edb3d005fa668810_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff1e755ef2a967a941cf7eb9926e3c80d734ef7e
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/051638d871c75230edb3d005fa668810_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48499fa0ea9fb700fba358321799850c84d5499b68da59d33c56887d2c9d93ea
+size 56212
diff --git a/marked/Rel-16/37_series/37824/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-16/37_series/37824/0892c0cb3b8502a44c4fe4e786be912a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..424890d1f1c308b1da841148d18ea63e086fd7f0
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/0892c0cb3b8502a44c4fe4e786be912a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9891369fbfd21111d3c82854a0231a58b1f1e38da0b10eb8f62360b2d375ee9
+size 56153
diff --git a/marked/Rel-16/37_series/37824/1316cc5a3c69067473f110271212db3b_img.jpg b/marked/Rel-16/37_series/37824/1316cc5a3c69067473f110271212db3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1b450ce1fe56dd2f00eaebd920aa73bf8ff1eaf8
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/1316cc5a3c69067473f110271212db3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f1f6013fb4128d1e6a95115e6803f48509b81596e1e5a0b6bcf22845af933dad
+size 58152
diff --git a/marked/Rel-16/37_series/37824/14515d82ffeec9475b9add3036ff26ab_img.jpg b/marked/Rel-16/37_series/37824/14515d82ffeec9475b9add3036ff26ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..001d647a2cf43b707c483e1297df75ad92489edb
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/14515d82ffeec9475b9add3036ff26ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60179e1d3b0c9cd2957a33f6d7ad6af0a22d84047c1dfc5282dddf29ed89900a
+size 44427
diff --git a/marked/Rel-16/37_series/37824/16c69c0dacd3c57ae91acd114e5f5bd2_img.jpg b/marked/Rel-16/37_series/37824/16c69c0dacd3c57ae91acd114e5f5bd2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b84664904127fd8853e5af2dcbadbf259d6dcd31
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/16c69c0dacd3c57ae91acd114e5f5bd2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9dfc711c157950a5c850fcdd732d53bac8015e067ced756b50dc0a899aae4ba2
+size 57617
diff --git a/marked/Rel-16/37_series/37824/17cd95aa220e50963bf6eb9818e33163_img.jpg b/marked/Rel-16/37_series/37824/17cd95aa220e50963bf6eb9818e33163_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..173995ebef5bc21fd7a4498ff0aa901003c9d738
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/17cd95aa220e50963bf6eb9818e33163_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8cec878a8817a79a37cf35010b21b79d23bab5ee0563655c8442c5780d0fc56c
+size 19244
diff --git a/marked/Rel-16/37_series/37824/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg b/marked/Rel-16/37_series/37824/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f3e6748e763a621c07d7573d167fd7aeafaa32d8
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44ca1b5e01be04b7c72557ad1fe41f34be1f75fd8a06cfbce1fe1351c8fd425a
+size 57660
diff --git a/marked/Rel-16/37_series/37824/1c2028183a35357e7238438a4af9cab7_img.jpg b/marked/Rel-16/37_series/37824/1c2028183a35357e7238438a4af9cab7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f8b5dd12184a87272ab6fd238b33670ed61afd6
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/1c2028183a35357e7238438a4af9cab7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6104081bee86d95f9efa68b35f6602cfedbf0b785968955dfa67f35ce1f12a02
+size 58014
diff --git a/marked/Rel-16/37_series/37824/20727e57890be6da5692a02d13c0a8ec_img.jpg b/marked/Rel-16/37_series/37824/20727e57890be6da5692a02d13c0a8ec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b94b2708ee3313e87a5b214524c84206905b1015
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/20727e57890be6da5692a02d13c0a8ec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41acd8677267d115c77e517ddee399c3a36db7301023cb6c3cf503d0b30c3c98
+size 60846
diff --git a/marked/Rel-16/37_series/37824/20e597e389dfd8d131e05ad6e1617dcd_img.jpg b/marked/Rel-16/37_series/37824/20e597e389dfd8d131e05ad6e1617dcd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26c75fbd24c933e797df9eace13e8a04b61034d6
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/20e597e389dfd8d131e05ad6e1617dcd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:57181ae48856b2e6dc1de41428337beb562a91818bb196fae2e727d4918b99df
+size 56296
diff --git a/marked/Rel-16/37_series/37824/516d9f1866cc2e359a35fb1d8c046454_img.jpg b/marked/Rel-16/37_series/37824/516d9f1866cc2e359a35fb1d8c046454_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9fca3227c85755a3b0686dbb77dc61bae4f14fc9
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/516d9f1866cc2e359a35fb1d8c046454_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85a4b11f47eb66103c28fc73b9b4c553c0411811a63b7a09ce1052e37363a649
+size 56208
diff --git a/marked/Rel-16/37_series/37824/552265bdbcf6d43d341fd018a9076269_img.jpg b/marked/Rel-16/37_series/37824/552265bdbcf6d43d341fd018a9076269_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6ca6982a2264cf94f175215dd3595a665fcd1e3d
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/552265bdbcf6d43d341fd018a9076269_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9169bbeed82966bcf7899c3fcdab8d39135fcc0de9cab9e84ab0d4fd08aa4cdf
+size 26956
diff --git a/marked/Rel-16/37_series/37824/576ba643ba30a6c1d19bd0883db96e38_img.jpg b/marked/Rel-16/37_series/37824/576ba643ba30a6c1d19bd0883db96e38_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa73b695d08c0cc74b427da713bb54dd48f4db45
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/576ba643ba30a6c1d19bd0883db96e38_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4544b83063e5c14d8b50fd82d809abcc1da7b518c49f4dd47c069123fe92aa4
+size 31863
diff --git a/marked/Rel-16/37_series/37824/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg b/marked/Rel-16/37_series/37824/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c5cee2c8f9da5cfe63c750577f45d7a6d022812
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7057933e839e3a25b02a4cfa15393057f5c339c6730d128f03f7c3d49fdcd30c
+size 54040
diff --git a/marked/Rel-16/37_series/37824/68ec8ddd77b91c6e59d90ca84ad64f11_img.jpg b/marked/Rel-16/37_series/37824/68ec8ddd77b91c6e59d90ca84ad64f11_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..76034222318d485264993eac2bb3eb68541ecce8
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/68ec8ddd77b91c6e59d90ca84ad64f11_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d06e830741443470dfc82db474b1d5d15358bb3eb5617a44804d6510f591a932
+size 111863
diff --git a/marked/Rel-16/37_series/37824/6c865810bad6a51ecc6afa635f9c3ca6_img.jpg b/marked/Rel-16/37_series/37824/6c865810bad6a51ecc6afa635f9c3ca6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10cc2369fc6b0c11b61ad31915f86856b90b6871
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/6c865810bad6a51ecc6afa635f9c3ca6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9e63227c1b439c0271b01c05111254e2a65ea82c8c5a144592215c42fc120e58
+size 28164
diff --git a/marked/Rel-16/37_series/37824/6f10f5cbc920e8c4340d869aae0f1f58_img.jpg b/marked/Rel-16/37_series/37824/6f10f5cbc920e8c4340d869aae0f1f58_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8ff88997151ce347dbd05b93030ff8cd659b3fe
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/6f10f5cbc920e8c4340d869aae0f1f58_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65bb5bff22a4427c91f4748b98741f918ae9c6f20abd039fe79606deaaaaf402
+size 61667
diff --git a/marked/Rel-16/37_series/37824/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg b/marked/Rel-16/37_series/37824/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c439a2e2b03837fba7ff5ab54b1b53ab4f1ad2f3
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/7119b28e39fa3784606bf8b8f44e4f9d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb3421c6d36128ec6cf7602e0553a28420e873f06a002a25513038e390a574ed
+size 61566
diff --git a/marked/Rel-16/37_series/37824/740442c999390734911677f01af0316d_img.jpg b/marked/Rel-16/37_series/37824/740442c999390734911677f01af0316d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7971660ca156d4fbd03607dfe0035eb3c8adeb0c
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/740442c999390734911677f01af0316d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e89fb4ac192e9063c37fd259e84e05aa26d0e086de5e0039b828311755a23c38
+size 63335
diff --git a/marked/Rel-16/37_series/37824/771c18f874d31c59c3b8c4e247be16ca_img.jpg b/marked/Rel-16/37_series/37824/771c18f874d31c59c3b8c4e247be16ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f597fabfbf5cb389238f2c0c7b55fd276aa096e9
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/771c18f874d31c59c3b8c4e247be16ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9de52383f933cec5eef00a0b754b4ba29fd46f29b87be658d1e2ce8f8d0d6ee2
+size 56144
diff --git a/marked/Rel-16/37_series/37824/812b773680b611c18d49243e102b895a_img.jpg b/marked/Rel-16/37_series/37824/812b773680b611c18d49243e102b895a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..814fc013ac506cfb56cf5879fe86c64caab01600
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/812b773680b611c18d49243e102b895a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2bf0041dcf71f4cd26b8d2242c4b92b4597ca262f2a1b9e638d85219292bfe15
+size 66760
diff --git a/marked/Rel-16/37_series/37824/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg b/marked/Rel-16/37_series/37824/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1744590f7cd9f9d1cbbb9776c072849deaa91fb5
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5fdae2d992376f23090500b93f2f118ebef7dfd5688bd8eba1188e41ca474f8b
+size 23000
diff --git a/marked/Rel-16/37_series/37824/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/37_series/37824/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..39e5a6081c41ef556a3e74c7627357358e1ec846
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:836d6acd44074096131f4e5ab550e66592b6fc2a4400d27185856fb37c3bb2e8
+size 55728
diff --git a/marked/Rel-16/37_series/37824/89dcb02be40d2949bb93de93bbf213d5_img.jpg b/marked/Rel-16/37_series/37824/89dcb02be40d2949bb93de93bbf213d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4e03683ce1415bdc0a7f125c42c7b26ac963ba3
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/89dcb02be40d2949bb93de93bbf213d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc7a980723386af389689d6707b6d4497f84942943e20eaaa475fc64da6a6ec0
+size 27047
diff --git a/marked/Rel-16/37_series/37824/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/37_series/37824/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d128f0e25b119c9eeaef78b1fbc36d8c4a828329
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b74e83940cb8d4456597900e02c0ab3123c32e8bdfd13cd34dc4d941d9b01149
+size 54957
diff --git a/marked/Rel-16/37_series/37824/94796d524bd7e0f31f89a379bae95996_img.jpg b/marked/Rel-16/37_series/37824/94796d524bd7e0f31f89a379bae95996_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1cab9a74803c5ea7d13e0448ffe890124db9774
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/94796d524bd7e0f31f89a379bae95996_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:390663d9946f2eec859f77aaea3ac06444b40e50c434ac43387ced457007e72b
+size 112287
diff --git a/marked/Rel-16/37_series/37824/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/37_series/37824/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..462520e852766bb9852ef8fb7ba7e86aad8df909
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/a0739aaf13fa5a632d4faa830f6b2708_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0549f4fa4e8b603b9f02f14300bff55fec79fa22ea417d3cd4cc6c1cc1d7dcc8
+size 77044
diff --git a/marked/Rel-16/37_series/37824/a289b64f80c6df506c0c55d553fc4496_img.jpg b/marked/Rel-16/37_series/37824/a289b64f80c6df506c0c55d553fc4496_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5148a37b57b90a572352c6dc519e5989c471c9a1
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/a289b64f80c6df506c0c55d553fc4496_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9f802953d67acb18c0c4a6d56191deeac90eacecc2eee4751f9fed508862d8b
+size 18621
diff --git a/marked/Rel-16/37_series/37824/a844248c1fa0a79f187fc9aa111182f7_img.jpg b/marked/Rel-16/37_series/37824/a844248c1fa0a79f187fc9aa111182f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..172a2617a78b7264d1fd35a7f2c5e4eae93dbcf4
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/a844248c1fa0a79f187fc9aa111182f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cdddca1720cb33850e203dc48c827f5ccf2199ecfd254c04b378c4144670e56e
+size 60840
diff --git a/marked/Rel-16/37_series/37824/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/marked/Rel-16/37_series/37824/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2e243418874dcdcb7f2c1567156ddfa6a91b6335
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/cfda9df1319e04207eb28bcefd1dab7b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:64eefc7d0d94b2a0b214cf4eda22e3318dabd491e6157c2d7a0f7dd060c39cf3
+size 33973
diff --git a/marked/Rel-16/37_series/37824/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-16/37_series/37824/d3b5eac55166fc428a223bba5c46961b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea10a343ddfbd29cc0f567b506eee3e5f90704db
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/d3b5eac55166fc428a223bba5c46961b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2732ba01ab396890f58a5ace05bb218b7c4d0d74d0b304d4868a2ece813f438
+size 44471
diff --git a/marked/Rel-16/37_series/37824/e714d8aca168c4854edebc4a4f2e9bd1_img.jpg b/marked/Rel-16/37_series/37824/e714d8aca168c4854edebc4a4f2e9bd1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2b10b9eb18d6e024de9cb699956fa1575e094c6
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/e714d8aca168c4854edebc4a4f2e9bd1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce3a7892ca2d8264119d739026404b06a6f01f6c6270afca3206e69535f2e05b
+size 57808
diff --git a/marked/Rel-16/37_series/37824/e9314c83043183351ed74908e9bf2f90_img.jpg b/marked/Rel-16/37_series/37824/e9314c83043183351ed74908e9bf2f90_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..94f22068d123350ae0aa1c4c8547b5ee35a4eb45
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/e9314c83043183351ed74908e9bf2f90_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2a7bfdc1099c8305f47e4b1bbb43ddc26bca28584041aba883b4cbb1c71a186
+size 50195
diff --git a/marked/Rel-16/37_series/37824/fe655d77258397f7242c2df72b965b56_img.jpg b/marked/Rel-16/37_series/37824/fe655d77258397f7242c2df72b965b56_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a8b9e8fa53f6cf3eb816a9131294e5edf6193897
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/fe655d77258397f7242c2df72b965b56_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a093a7af280f49178444fbba9b9979e157972dce60a3a03b6633ae0f5c599515
+size 121827
diff --git a/marked/Rel-16/37_series/37824/raw.md b/marked/Rel-16/37_series/37824/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..48b3fc1dba5cc870f78a997270a04ac785c64f81
--- /dev/null
+++ b/marked/Rel-16/37_series/37824/raw.md
@@ -0,0 +1,1387 @@
+
+
+# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR and E-UTRA; Coexistence between NB-IoT and NR (Release 16)** --- ---
+
+## --- **Keywords**
+
+<keyword[, keyword]>
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+## Contents
+
+|                                                               |           |
+|---------------------------------------------------------------|-----------|
+| Foreword .....                                                | 4         |
+| 1 Scope.....                                                  | 5         |
+| 2 References.....                                             | 5         |
+| 3 Definitions, symbols and abbreviations .....                | 5         |
+| 3.1 Definitions.....                                          | 5         |
+| 3.2 Symbols.....                                              | 5         |
+| 3.3 Abbreviations .....                                       | 6         |
+| 4 Background .....                                            | 7         |
+| 4.1 Task description .....                                    | 7         |
+| 5 NR and NB-IoT coexistence.....                              | 8         |
+| 5.1 General .....                                             | 8         |
+| 5.2 NB-IoT operating in NR in-band .....                      | 9         |
+| 5.2.1.1 Convention.....                                       | 9         |
+| 5.2.1.2 NB-IoT channel raster .....                           | 9         |
+| 5.2.1.3 NR channel raster.....                                | 10        |
+| 5.2.1.4 NR SS Blocks .....                                    | 11        |
+| 5.2.1.5 NB-IoT and NR coexistence.....                        | 12        |
+| 5.2.1.6 NR 100 kHz channel raster.....                        | 13        |
+| 5.2.1.6.1 DL considerations .....                             | 13        |
+| 5.2.1.6.2 NR FDD bands– UL considerations.....                | 15        |
+| 5.2.1.6.3 NR TDD bands – UL considerations .....              | 16        |
+| 5.2.1.6.4 Example.....                                        | 16        |
+| 5.2.1.7 NR SCS based channel raster .....                     | 17        |
+| 5.2.1.7.1 DL considerations .....                             | 17        |
+| 5.2.1.7.1.1 Carrier frequency.....                            | 17        |
+| 5.2.1.7.1.2 RB alignment.....                                 | 17        |
+| 5.2.1.7.1.3 Channel bandwidth.....                            | 18        |
+| 5.2.1.7.1.4 Conclusion.....                                   | 18        |
+| 5.2.1.7.2 UL considerations .....                             | 19        |
+| 5.2.1.7.3 Example.....                                        | 20        |
+| 5.3 NB-IoT operating in NR guard-band .....                   | 21        |
+| 5.3.1 Spectrum utilization consideration .....                | 21        |
+| 5.3.2 Refarming consideration .....                           | 21        |
+| 5.3.3 Conclusion.....                                         | 21        |
+| 5.4 NB-IoT standalone operating.....                          | 22        |
+| 5.5 Synchronization between NR and NB-IoT .....               | 22        |
+| 5.5.1 Background.....                                         | 23        |
+| 5.5.2 TDD synchronization .....                               | 24        |
+| 5.5.2.1 General.....                                          | 24        |
+| 5.5.2.2 NR TDD patterns for synchronization with NB-IoT ..... | 24        |
+| 5.5.2.3 Overriding UE specific dedicated configuration .....  | 24        |
+| 5.6 Specification and conformance impact .....                | 26        |
+| 6 Summary .....                                               | 27        |
+| <b>Annex A: Coexistence simulation.....</b>                   | <b>28</b> |
+| <b>Annex B (informative): Change history.....</b>             | <b>46</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is a technical report for the work item on additional enhancements for NB-IoT, covering the study on the coexistence of NB-IoT with NR, which is one of the objectives of the WI [2].
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] RP-193224: "Additional enhancements for NB-IoT"
+- [3] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception".
+- [4] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [5] 3GPP TS 38.213: "NR; Physical layer procedures for control".
+- [6] 3GPP TS 38.104: "NR: Base Station (BS) radio transmission and reception".
+- [7] 3GPP TS 36.141: " Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing".
+- [8] 3GPP TS 37.141: "NR, E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) conformance testing".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |               |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+# --- 4 Background
+
+## 4.1 Task description
+
+The objective on NR and NB-IoT coexistence is,
+
+Specify NB-IoT resource reservation for UL/DL FDD/TDD NB-IoT non-anchor carriers, to avoid resource overlap between NR and NB-IoT when NB-IoT is deployed within an NR carrier [RAN1, RAN2, RAN4].
+
+For NB-IoT in-band, guard band and standalone operation co-existence with NR, including the case of NR configured in 15kHz SS Block SCS and the case of 30kHz SS Block SCS as specified in 38.101-1, investigate the following: [RAN4]
+
+15KHz, 30KHz, and 60KHz numerologies for NR FR1 concerned bands, with higher priority given first to 15kHz and then to 30kHz
+
+Channel raster, PRB and subcarrier grid alignment between NB-IoT and NR
+
+Study feasible NB-IoT carrier(s) placement allocation without RF backward compatibility impact and compatible with Rel'13 NB-IoT and Rel'15 NR, to operate simultaneously within various NR channel bandwidths
+
+Study if the +6dB downlink RE power boosting can still be allowed for both in-band and guard band operation modes when co-existing with NR
+
+Synchronization issue between NR and NB-IoT, including timing advance
+
+Frequency band support in NB-IoT and NR
+
+Testability applicable to RF
+
+Coexistence between R15 NR and R13/R14/R15 NB-IoT.
+
+Note: After RAN1 concludes the objective on R16 NB-IoT coexistence aspects, evaluate coexistence between R15 NR and R16 NB-IoT.
+
+# 5 NR and NB-IoT coexistence
+
+## 5.1 General
+
+### 5.1.1 System scenarios
+
+For NB-IoT operating in LTE, system scenarios have been divided into 3 following operations,
+
+**Category NB1/NB2 stand-alone operation:** category NB1/NB2 is operating standalone when it utilizes its own spectrum, for example the spectrum used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+**Category NB1/NB2 guard band operation:** category NB1/NB2 is operating in guard band when it utilizes the unused resource block(s) within an E-UTRA carrier's guard-band.
+
+**Category NB1/NB2 in-band operation:** category NB1/NB2 is operating in-band when it utilizes the resource block(s) within a normal E-UTRA carrier.
+
+When it comes to NB-IoT co-existence with NR, depend on the utilized spectrum for NB-IoT operations, 3 system scenarios should be considered,
+
+**NB-IoT operation in NR in-band:** NB-IoT is operating in-band when it is located within a NR transmission bandwidth configuration plus 15 kHz at each edge but not within the NR minimum guard band  $GB_{Channel}$ .
+
+**NB-IoT operation in NR guard band:** NB-IoT is operating in guard band when it is located within a NR BS channel bandwidth but is not NB-IoT operation in NR in-band.
+
+**NB-IoT standalone operation:** NB-IoT is operating standalone when it utilizes its own spectrum, for example the spectrum currently being used by GERAN systems as a replacement of one or more GSM carriers, as well as scattered spectrum for potential IoT deployment.
+
+![Diagram illustrating the definition of channel bandwidth and transmission bandwidth configuration for one NR channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a dashed vertical line on the left marks the start of the 'Transmission Bandwidth Configuration N_RB [RB]', indicated by a double-headed arrow. Within this configuration, a group of blue vertical bars represents 'Active Resource Blocks', with a double-headed arrow above them labeled 'Transmission Bandwidth [RB]'. To the right of the active blocks, a single vertical bar is labeled 'Resource Block'. Below the axis, a double-headed arrow between the 'Active Resource Blocks' and the 'Channel Edge' on the right is labeled 'Guardband, can be asymmetric'.](740442c999390734911677f01af0316d_img.jpg)
+
+Diagram illustrating the definition of channel bandwidth and transmission bandwidth configuration for one NR channel. The diagram shows a horizontal axis representing frequency. A dashed vertical line on the left is labeled 'Channel Edge' and another on the right is also labeled 'Channel Edge'. A double-headed arrow between these edges is labeled 'Channel Bandwidth [MHz]'. Inside, a dashed vertical line on the left marks the start of the 'Transmission Bandwidth Configuration N\_RB [RB]', indicated by a double-headed arrow. Within this configuration, a group of blue vertical bars represents 'Active Resource Blocks', with a double-headed arrow above them labeled 'Transmission Bandwidth [RB]'. To the right of the active blocks, a single vertical bar is labeled 'Resource Block'. Below the axis, a double-headed arrow between the 'Active Resource Blocks' and the 'Channel Edge' on the right is labeled 'Guardband, can be asymmetric'.
+
+Figure 5.1.1-1: Definition of channel bandwidth and transmission bandwidth configuration for one NR channel
+
+## 5.2 NB-IoT operating in NR in-band
+
+### 5.2.1 Channel raster, PRB and subcarrier grid alignment
+
+#### 5.2.1.1 Convention
+
+In the following sub-sections, focus is on NR 15 kHz SCS. Coexistence with NR 30kHz and 60kHz SCS is nevertheless addressed, mentioning additional guard band would be needed in between NR and NB-IoT. Also, PRBs alignment won't really make sense anymore as orthogonality could not be preserved when considering 30kHz and 60 kHz SCS.
+
+In the following sub-sections, here after tone and RB index rules are assumed:
+
+Tone (or subcarrier) #0 of one RB is the first tone (or subcarrier) of that RB, as shown on Figure 5.2.1.2-1 with NB-IoT RB.
+
+If  $N_{RB}$  is the number of RBs for a certain NR channel bandwidth:
+
+RB #0 is the RB hosting the NR RF reference frequency.
+
+Subcarrier #0 is the first subcarrier of RB #0.
+
+As shown on Figure 5.2.1.3-1, if  $N_{RB}$  is even:
+
+RB  $\#(-N_{RB}/2)$  is the RB on the lower edge of NR RF channel BW
+
+Subcarrier  $\#(-N_{RB}/2*12)$  is the first subcarrier at lower edge of NR RF channel BW.
+
+RB  $\#(N_{RB}/2-1)$  is the RB on the upper edge of NR RF channel BW.
+
+Subcarrier  $\#((N_{RB}/2)*12-1)$  is the last subcarrier at upper edge of NR RF channel BW.
+
+As shown on Figure 5.2.1.3-2, if  $N_{RB}$  is odd:
+
+RB  $\#(-(N_{RB}-1)/2)$  is the RB on the lower edge of NR RF channel BW
+
+Subcarrier  $\#(-(N_{RB}-1)/2*12)$  is the first subcarrier at lower edge of NR RF channel BW.
+
+RB  $\#((N_{RB}-1)/2)$  is the RB on the upper edge of NR RF channel BW.
+
+Subcarrier  $\#((N_{RB}+1)/2*12-1)$  is the last subcarrier at upper edge of NR RF channel BW.
+
+For example, for a NR 10MHz channel bandwidth signal:
+
+RB#0 is the RB in the middle hosting the RF reference frequency (channel raster).
+
+RB#(-26) is the RB on the lower edge of NR RF channel BW.
+
+RB#25 is the RB on the upper edge of NR RF channel BW.
+
+#### 5.2.1.2 NB-IoT channel raster
+
+The NB-IoT carrier frequency position is defined on a 100 kHz channel raster based as follow:
+
+$$F_{DL} = F_{DL\_low} + 0.1(N_{DL} - N_{offs-DL}) + 0.0025*(2M_{DL}+1)$$
+
+$$F_{UL} = F_{UL\_low} + 0.1(N_{UL} - N_{offs-UL}) + 0.0025*(2M_{UL})$$
+
+The specified carrier frequency is located in the middle of NB-IoT RB, i.e. the frequency in between tones 5 and 6 of the RB (for 15 kHz SCS), as shown on Figure 5.2.1.2-1.
+
+![Diagram of NB-IoT carrier location within an NB-IoT PRB. The diagram shows 12 tones (Tone #0 to Tone #11) as vertical rectangles. A red arrow labeled 'NB-IoT carrier (F_DL or F_UL)' points to the boundary between Tone #5 and Tone #6. A double-headed arrow at the bottom labeled 'NB-IoT PRB' spans the entire width of the 12 tones.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg)
+
+Diagram of NB-IoT carrier location within an NB-IoT PRB. The diagram shows 12 tones (Tone #0 to Tone #11) as vertical rectangles. A red arrow labeled 'NB-IoT carrier (F\_DL or F\_UL)' points to the boundary between Tone #5 and Tone #6. A double-headed arrow at the bottom labeled 'NB-IoT PRB' spans the entire width of the 12 tones.
+
+**Figure 5.2.1.2-1: NB-IoT carrier location**
+
+$M_{DL}$  and  $M_{UL}$  values ranges are specified in TS 36.104 [3] or TS 36.101 [4].
+
+The anchor NB-IoT RB (broadcasting NPSS/NSSS) position is defined with a limited  $M_{DL}$  range to  $\{-2, -1, 0, 1\}$ .
+
+#### 5.2.1.3 NR channel raster
+
+NR has considered 2 types of channel raster:
+
+- 100 kHz based channel raster, mainly used for NR bands re-farmed from LTE ones.
+
+- SCS based channel raster, 15 or 30 kHz for FR1.
+
+Note that all FDD bands in FR1 have a channel raster based on 100 kHz.
+
+The RF reference frequency defined by this channel raster identifies the RF channel position depending on the number of specified RBs ( $N_{RB}$ ) by the spectrum utilization for a given SCS and channel bandwidth:
+
+- If this number is even, then it points to the subcarrier #0 (first one) of RB index #0, as shown in Figure 2.
+
+- If this number is odd, the it points to the subcarrier #6 of RB index #0, as shown in Figure 5.2.1.3-1.
+
+![Diagrams showing NR RF reference frequency position for even and odd N_RB cases.](e9314c83043183351ed74908e9bf2f90_img.jpg)
+
+The figure contains two diagrams illustrating the NR RF reference frequency position relative to Physical Resource Blocks (PRBs).
+
+- N<sub>RB</sub> is even :** A horizontal line represents the frequency axis. PRBs are shown as blocks. From left to right, they are labeled PRB #(N<sub>RB</sub>/2), PRB #-1, PRB #0, PRB #1, and PRB #(N<sub>RB</sub>/2)-1. A red arrow labeled "NR RF reference frequency" points to the boundary between PRB #-1 and PRB #0. A double-headed arrow below the line spans from the start of PRB #(N<sub>RB</sub>/2) to the end of PRB #(N<sub>RB</sub>/2)-1, labeled "N<sub>RB</sub> (as defined in NR spectrum utilization)".
+- N<sub>RB</sub> is odd :** Similar horizontal line. PRBs are labeled PRB #(N<sub>RB</sub>-1)/2, PRB #-1, PRB #0, PRB #1, and PRB #(N<sub>RB</sub>-1)/2. A red arrow labeled "NR RF reference frequency" points to the center of PRB #0. A double-headed arrow below the line spans from the start of PRB #(N<sub>RB</sub>-1)/2 to the end of PRB #(N<sub>RB</sub>-1)/2, labeled "N<sub>RB</sub> (as defined in NR spectrum utilization)".
+
+Diagrams showing NR RF reference frequency position for even and odd N\_RB cases.
+
+Figure 5.2.1.3-1: NR RF reference frequency position
+
+#### 5.2.1.4 NR SS Blocks
+
+The presence of the NR Synchronization Signal (SS) blocks would restrict possible options when placing a NB. Those blocks contain synchronization signals (PSS and SSS) which are used for UE to synchronize and connect to the BS. It's so key that NB-IoT is not overlapping those blocks to not impact NR UE synchronization performance.
+
+The SS block pattern for 15 kHz SCS is according to Case A (specified in TS 38.213 [5]) and its structure is given in Figure 5.2.1.4-1. SSB occupies 20 RBs in frequency domain and 4 OFDM symbols in time domain.
+
+![Diagram showing the structure of an SS Block across 4 OFDM symbols and 240 subcarriers.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+The diagram shows the structure of an SS Block in the time-frequency plane.
+
+- The vertical axis is labeled "Time (symbols)" and the horizontal axis is labeled "Frequency (subcarriers)".
+- The block consists of 4 OFDM symbols (rows) and 240 subcarriers (20 RBs) (columns).
+- Symbol 1 (top):** Contains PBCH across all 240 subcarriers.
+- Symbol 2:** Contains PBCH in the first 4 RBs and last 4 RBs, with SSS in the middle 127 subcarriers.
+- Symbol 3:** Contains PBCH across all 240 subcarriers.
+- Symbol 4 (bottom):** Contains PSS in the middle 127 subcarriers, with gaps in the first 4 RBs and last 4 RBs.
+- Horizontal dimension labels: "240 subcarriers (20 RBs)" for the total width, "127 subcarriers" for the central signal blocks, and "144 subcarriers" for the total width excluding the 4 RB gaps at each end. Vertical dimension labels: "4 OFDM symbols" for the total height and "4 RBs" for the gap width at each end.
+
+Diagram showing the structure of an SS Block across 4 OFDM symbols and 240 subcarriers.
+
+Figure 5.2.1.4-1: Structure of SS Block
+
+Considering NB-IoT is currently specified only for frequency bands below 3 GHz, following equation gives the frequency position of the synchronization raster:
+
+$$SS_{REF} = 1200N + 50M, \text{ [kHz]} \quad (4.1)$$
+
+where  $N \in \{1, 2, \dots, 2499\}$  is an integer, and  $M \in \{1, 3, 5\}$ .
+
+$SS_{REF}$  refers to the first subcarrier of the RB #10 of the SSB block (which corresponds to 11<sup>th</sup> RB of the SSB block).
+
+Therefore, the minimum and maximum frequencies of the SSB (i.e., SSB edges), based on Figure 5.2.1.4-2, are:
+
+$$F_{SSB,min} = SS_{REF} - (10 \times 180) - 7.5, \text{ [kHz]} \quad (4.2)$$
+
+$$F_{SSB,max} = F_{SSB,min} + (20 \times 180), \text{ [kHz]} \quad (4.3)$$
+
+![Diagram of SSB structure showing 10 RBs on either side of the SS_REF point, with a 7.5 kHz offset.](83dedc2074a453d13ce74cc2e1ae4ff5_img.jpg)
+
+The diagram illustrates the frequency domain representation of an SSB block. A central blue circle represents the SS<sub>REF</sub> point, labeled 'SS<sub>REF</sub>: first subcarrier of 11<sup>th</sup> RB'. To the left of this point is a yellow block labeled '10 RBs', and to the right is another yellow block labeled '10 RBs'. A double-headed arrow between the center and the start of the left block is labeled '7.5 kHz'. The left edge of the left yellow block is marked with a green arrow and labeled  $F_{SSB,min}$ . The right edge of the right yellow block is marked with a green arrow and labeled  $F_{SSB,max}$ .
+
+Diagram of SSB structure showing 10 RBs on either side of the SS\_REF point, with a 7.5 kHz offset.
+
+Figure 5.2.1.4-2: Position of  $SS_{REF}$  in SSB.
+
+Which also means NB-IoT RB, shall also not be overlapping the following frequency range, as illustrated on Figure 5.2.1.4-3:
+
+$$[ 1200N + 50M - (10 \times 180) - 7.5 , 1200N + 50M + (10 \times 180) - 7.5 ] \text{ [kHz]}$$
+
+![Diagram showing feasible locations for an NB-IoT RB to avoid overlap with an NR SSB block.](6c865810bad6a51ecc6afa635f9c3ca6_img.jpg)
+
+The diagram shows an NR SSB block (yellow) in the center, labeled 'NR SSB', with a width of '20 RBs'. To its left is a blue region, and to its right is another blue region. On the left blue region, a green box labeled 'NB-IoT' is shown, with its center frequency  $F_{nb}$ . The left edge of this box is labeled  $(F_{nb}-90)$  and the right edge is labeled  $(F_{nb}+90)$ . Below this box is the text 'one RB (Case 2)'. On the right blue region, another green box labeled 'NB-IoT' is shown, with the text 'one RB (Case 1)' below it. Red arrows point from the left edge of the NR SSB block to the label  $F_{SSB,min}$  and from the right edge to the label  $F_{SSB,max}$ .
+
+Diagram showing feasible locations for an NB-IoT RB to avoid overlap with an NR SSB block.
+
+Figure 5.2.1.4-3: Feasible locations of an NB-IoT RB to avoid overlap with NR SSB in coexistence scenario.
+
+#### 5.2.1.5 NB-IoT and NR coexistence
+
+As mentioned before, NB-IoT carrier frequency and NR RF reference frequency refers to different locations in the frequency domain:
+
+NB-IoT carrier frequency is referring to a frequency located in between 2 NB-IoT tones.
+
+NR RF reference frequency is referring to a frequency located in the middle of a tone.
+
+To align sub-carriers, considering NR 15 kHz SCS, a 7.5 kHz offset shall therefore be considered in between reference frequencies.
+
+#### 5.2.1.6 NR 100 kHz channel raster
+
+##### 5.2.1.6.1 DL considerations
+
+###### 5.2.1.6.1.1 Carrier frequency
+
+Based on previous considerations (NB-IoT carrier frequency, preserving perfect orthogonality in between NB-IoT and NR tones), the following equation should be resolved:
+
+$$100n + 2.5 * (2MDL + 1) = 100m + 15k - 7.5 \quad (6.1)$$
+
+With:
+
+- $MDL$  being the Offset of NB-IoT Channel Number to EARFCN.
+- $n$  being an integer identifying NB-IoT carrier on the 100kHz grid
+- $m$  being an integer identifying NR RF reference frequency on the 100 kHz grid
+- $k$  being an integer representing a subcarrier index from NR RF reference frequency.
+
+This would then result in following potential subcarrier index:
+
+$$k = \frac{20 * (n-m) + MDL+2}{3} \quad (6.2)$$
+
+All possible positions are determined by finding  $(n-m)$  values so that  $k$  is an integer that would solve this equation (6.2).
+
+###### 5.2.1.6.1.2 RB alignment
+
+NB-IoT RB and NR RB should be aligned to optimize resource utilization, avoiding that a NB-IoT RB overlaps 2 NR RBs.
+
+As mentioned in 5.2.1.5, NR reference frequency refers to different subcarriers of the middle RB depending on spectrum utilization, and more specifically on the parity of the number of RBs allocated for a considered channel bandwidth.
+
+Based on this, to ensure RBs alignment, considering  $p$  being an integer representing the RB index from NR reference frequency ( $p = 0$  for the NR RB hosting the NR Reference frequency), if:
+
+The maximum number of RBs for a given channel bandwidth is even: NB-IoT carrier frequency should be further offset with 90 kHz, and equation (6.1) would become:
+
+$$100n + 2.5 * (2MDL + 1) = 100m + 180p - 7.5 + 90 \quad (6.3)$$
+
+![Diagram showing a frequency spectrum with a central DC component and multiple subcarriers. The DC component is marked with a red arrow. The subcarriers are marked with blue arrows. The frequency of the subcarriers is labeled as 100KHz*m+90KHz-7.5KHz+p*180KHz. The diagram is labeled NR at the bottom.](576ba643ba30a6c1d19bd0883db96e38_img.jpg)
+
+The diagram illustrates a frequency spectrum. A central vertical red line represents the DC component. To the right of the DC component, several vertical blue lines represent subcarriers. Above the subcarriers, the frequency formula  $100KHz * m + 90KHz - 7.5KHz + p * 180KHz$  is shown. Below the spectrum, there is a label 'NR' and a double-headed arrow indicating a bandwidth. The spectrum is flanked by two teal-colored blocks representing guard bands or unused spectrum.
+
+Diagram showing a frequency spectrum with a central DC component and multiple subcarriers. The DC component is marked with a red arrow. The subcarriers are marked with blue arrows. The frequency of the subcarriers is labeled as 100KHz\*m+90KHz-7.5KHz+p\*180KHz. The diagram is labeled NR at the bottom.
+
+**Figure 5.2.1.6.1.2-1: Possible “RB aligned” frequency positions for NB-IoT (number of NR RBs is even).**
+
+Equation (6.2) would become:
+
+$$p = \frac{20 * (n-m) + MDL-16}{36} \quad (6.4)$$
+
+The maximum number of RBs for a given channel bandwidth is odd: no further offset shall be considered, equation (6.1) would become:
+
+$$100n + 2.5 * (2MDL + 1) = 100m + 180p - 7.5 \quad (6.5)$$
+
+![Diagram showing possible 'RB aligned' frequency positions for NB-IoT when the number of NR RBs is even. It depicts a spectrum with a central DC component and multiple NR RBs. Arrows indicate frequency offsets from the DC component, labeled as 100KHz*m - 7.5KHz + p*180KHz.](89dcb02be40d2949bb93de93bbf213d5_img.jpg)
+
+The diagram illustrates a frequency spectrum. A central vertical line is labeled 'DC'. To the left and right of the DC line, there are multiple vertical bars representing NR RBs. A red arrow points from the DC line to one of the bars on the right, labeled '100KHz\*m - 7.5KHz + p\*180KHz'. Below the bars, there is a label 'NR' with a double-headed arrow indicating the span of the NR RBs.
+
+Diagram showing possible 'RB aligned' frequency positions for NB-IoT when the number of NR RBs is even. It depicts a spectrum with a central DC component and multiple NR RBs. Arrows indicate frequency offsets from the DC component, labeled as 100KHz\*m - 7.5KHz + p\*180KHz.
+
+**Figure 5.2.1.6.1.2-2: Possible “RB aligned” frequency positions for NB-IoT (number of NR RBs is odd).**
+
+Equation (6.2) would become:
+
+$$p = \frac{20 * (n-m) + MDL+2}{36} \quad (6.6)$$
+
+###### **5.2.1.6.1.3 Channel bandwidth**
+
+In previous equations (6.4) and (6.6), (n-m) represents the frequency separation in between NB-IoT carrier and NR RF reference frequency on a 100 kHz grid.
+
+So, for a given NR RF reference frequency, (n-m) would indicate the relative frequency position of NB-IoT carrier from that NR reference frequency. And vice-versa, for a given NB-IoT carrier frequency, (n-m) would indicate the relative frequency position of NR reference frequency from that NB-IoT carrier.
+
+Also,  $p$  being the RB index from NR reference frequency,  $p$  has limited value determined from NR Channel bandwidth and from the corresponding spectrum utilization.
+
+So, if  $N_{RB}$  is the maximum number of RBs for a certain channel bandwidth (as specified by the transmission bandwidth configuration in TS 38.104 [6], considering  $p = 0$  for the centre RB in that channel bandwidth,  $p$  will be bounded. Equations (6.4) and (6.6) would have following additional conditions:
+
+- If  $N_{RB}$  is even:
+
+$$p = \frac{20 * (n-m) + MDL-16}{36} \quad \text{with } -N_{RB}/2 \leq p \leq (N_{RB}/2) - 1 \quad (6.7)$$
+
+- If  $N_{RB}$  is odd:
+
+$$p = \frac{20 * (n-m) + MDL+2}{36} \quad \text{with } -(N_{RB} - 1)/2 \leq p \leq (N_{RB} - 1)/2 \quad (6.8)$$
+
+Those equations could be used to determine the position of NB-IoT anchor RB ( $M_{DL}$  as then limited set of values  $\{-2, -1, 0, 1\}$ ), or of any non-anchor RB ( $M_{DL}$  possible values would be then in the range of  $\{-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9\}$ ).
+
+###### 5.2.1.6.1.4 Conclusion
+
+NB-IoT and NR operating with 15 kHz SCS could coexist in NR bands supporting 100 kHz channel raster while optimizing resource utilization by aligning respective RBs. The RB index to deploy NB-IoT, for a given channel bandwidth with a transmission bandwidth configuration of  $N_{RB}$ , is given by:
+
+- If  $N_{RB}$  is even:
+
+$$p = \frac{20 * (n-m) + M_{DL} - 16}{36} \quad \text{with } -N_{RB}/2 \leq p \leq (N_{RB}/2) - 1 \quad (\text{Eq6.1})$$
+
+- If  $N_{RB}$  is odd:
+
+$$p = \frac{20 * (n-m) + M_{DL} + 2}{36} \quad \text{with } -(N_{RB} - 1)/2 \leq p \leq (N_{RB} - 1)/2 \quad (\text{Eq6.2})$$
+
+With the additional condition those candidates RBs shall not overlap in the following range:
+
+$$[ 1200N + 50M - (10 \times 180) - 7.5, 1200N + 50M + (10 \times 180) - 7.5 ] \text{ [kHz]} \quad (\text{Cond6.1})$$
+
+where  $N \in \{1, 2, \dots, 2499\}$  is an integer, and  $M \in \{1, 3, 5\}$ .
+
+From those equations, it's then possible to determine where to deploy NB-IoT in-band of a given NR frequency deployment. Or vice-versa, it's possible to determine how to deploy NR for a given NB-IoT frequency deployment, with NB-IoT operating in-band NR.
+
+Those equations could be used to determine the position of NB-IoT anchor RB ( $M_{DL}$  as then limited set of values  $\{-2, -1, 0, 1\}$ ), or of any non-anchor RB ( $M_{DL}$  possible values would be then in the range of  $\{-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9\}$ ).
+
+###### 5.2.1.6.1.5 Example
+
+Based on previous equations, the maximum channel bandwidth for 15 kHz SCS being 50 MHz ( $N_{RB}=270$ ),  $p$  (anchor PRB position) could take one of the following values: [-131, -126, -121, -116, -111, ..., -11, -6, -1, 4, 9, 14, 19, ..., 124, 129, 134]
+
+##### 5.2.1.6.2 NR FDD bands– UL considerations
+
+Due the DC component in DL but not in UL, there is a 7.5 kHz shift in between DL and UL for E-UTRA. As NB-IoT might be operated in E-UTRA in-band, this shift exists also in between NB-IoT DL and UL.
+
+NR has no DC component in its design, so such 7.5 kHz shift doesn't exist in between DL and UL. Nevertheless, to facilitate NR and E-UTRA coexistence and SUL feature, the possibility to have this 7.5 kHz offset has also been introduced for all FDD bands (see TS 38.104 [6] section 5.2.4.1):
+
+For SUL bands and for the uplink of all FDD bands defined in table 5.2-1,
+
+$$F_{REF,shift} = F_{REF} + \Delta_{shift}, \quad \Delta_{shift} = 0 \text{ kHz or } 7.5 \text{ kHz}$$
+
+where  $\Delta_{shift}$  is signalled by the network in higher layer parameter *frequencyShift7p5khz* [11].
+
+Using this 7.5 kHz shift it is possible to align NB-IoT RB when operating in NR in-band with NR RBs and so maintain orthogonality.
+
+##### 5.2.1.6.3 NR TDD bands – UL considerations
+
+Similar to FDD, for E-UTRA TDD, there is a 7.5 kHz offset in between DL and UL.
+
+Unfortunately, the optional 7.5 kHz shift in between UL and DL was not agreed for NR TDD bands. This can't be used then to compensate the offset in between UL and DL for NB-IoT.
+
+However, in the scope of Rel-15 and the introduction of TDD support for NB-IoT, anticipating NR, the range of possible position frequency positions of NB-IoT TDD UL carrier has been extended in TS 36.104 [3].
+
+The NB-IoT UL frequency position was initially specified with:
+
+$$F_{UL} = F_{UL\_low} + 0.1(N_{UL} - N_{offs-UL}) + 0.0025*(2M_{UL})$$
+
+with  $M_{UL}$  in the range of  $\{-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9\}$ .
+
+While from Rel-15, and the introduction of NB-IoT TDD support, the specification is:
+
+$$F_{UL} = F_{UL\_low} + 0.1(N_{UL} - N_{offs-UL}) + 0.0025*(2M_{UL})$$
+
+with  $M_{UL}$  in the range of  $\{-11, -10, -9.5, -9, -8.5, -8, -7.5, -7, -6.5, -6, -5.5, -5, -4.5, -4, -3.5, -3, -2.5, -2, -1.5, -1, -0.5, 0, 0.5, 1, 1.5, 2, 2.5, 3, 3.5, 4, 4.5, 5, 5.5, 6, 6.5, 7, 7.5, 8, 8.5, 9, 9.5, 10, 11\}$  for TDD.
+
+It's then possible for NB-IoT TDD to align UL with DL carrier.
+
+NR UL and DL carriers being aligned, with a 0 kHz offset, this means NB-IoT TDD DL and UL could coexist operating in-band with NR DL and UL, keeping orthogonality in between tones.
+
+The only drawback is that NB-IoT UL carrier can't remain at exact same frequency position when migrating from E-UTRA TDD to NR TDD but shall be shifted with an offset of 7.5 kHz.
+
+##### 5.2.1.6.4 Example
+
+Let's consider a NR 10MHz channel bandwidth ( $N_{RB}=52$ ) deployed in band n1. This band uses 100 kHz channel raster.
+
+Let's assume the RF reference frequency for this deployment is  $N_{REF}=427000$ , so  $F_{REF} = 2,135$  MHz.
+
+$N_{RB}$  being even, such deployment would be in between  $2,135,000 - 7.5 - 4,680 = 2,130,312.5$  kHz (which corresponds to lower edge of RB #(-26)) and  $2,135,000 - 7.5 + 4,680 = 2,139,672.5$  kHz (which corresponds to upper edge of RB #25)..
+
+As seen in 5.2.1.4, the SS block would occupy a frequency block from  $1200*N + 50*M - 10*180 - 7.5$  kHz to  $1200*N + 50*M + 10*180 - 7.5$  kHz.
+
+Assuming  $N=1778$  and  $M=5$  (GSCN=5333), being subcarrier aligned, the SS block would occupy frequency range  $[2,132,042.5 ; 2,135,642.5]$  kHz. In other words, SS block would overlap NR RBs #(-17) to #3.
+
+Considering NB-IoT and NR RB alignment, NB-IoT anchor RB could then be deployed in one of the following NR DL RBs: [-26, -21, 4, 9, 14, 19, 24].
+
+Considering sub-carrier alignment only (with overlapping of NB-IoT RB over 2 NR RBs then) would offer more options for possible NB-IoT RB location, with subcarriers [-306, -300, -299, ... -13, -6, 0, 1, 7, ...294, 300, 301].
+
+#### 5.2.1.7 NR SCS based channel raster
+
+##### 5.2.1.7.1 DL considerations
+
+###### 5.2.1.7.1.1 Carrier frequency
+
+Based on previous considerations (NB-IoT carrier frequency, preserving perfect orthogonality in between NB-IoT and NR tones, which also means NR SCS=15 kHz), the following equation should be resolved:
+
+$$100 * n + 2.5 * (2 * MDL + 1) = k * 15 + 5 * I * m - 7.5 \quad (7.1)$$
+
+With:
+
+- $MDL$ : Offset of NB-IoT Channel Number to EARFCN.
+- $n$ : integer identifying NB-IoT carrier on the 100kHz grid
+- $k$ : subcarrier index.
+- $m$ : integer identifying NR RF reference frequency
+- $I$ : step size as specified in Table 5.4.2.3-1 of TS 38.104,  $Step = \{1, 2, 3, 6\}$  depending on carrier frequency and sub-carrier spacing.
+
+This would then result in following potential subcarrier index:
+
+$$k = \frac{20 * n + MDL - I * m + 2}{3} \quad (7.2)$$
+
+All possible positions are determined by finding  $(n,m)$  values so that  $k$  is an integer that would solve this equation (7.2).
+
+###### 5.2.1.7.1.2 RB alignment
+
+When considering 15 kHz SCS, NB-IoT RB and NR RB should be aligned to optimize resource utilization, avoiding that a NB-IoT RB overlaps 2 NR RBs.
+
+When considering other SCS, RBs alignment is not obvious anymore. Orthogonality will be lost, and some guard would be needed in between NR RBs and NB-IoT RB. Depending on the required guard, it might be more optimal to center NB-IoT RB with one or 2 punctured NR RBs.
+
+In the following, considering no requirement has to be specified for mixed numerology, we will only investigate NR 15 kHz SCS.
+
+As mentioned in 5.2.1.5, NR reference frequency refers to different subcarriers of the middle RB depending on spectrum utilization, and more specifically on the parity of the number of RBs allocated for a considered channel bandwidth.
+
+Based on this, to ensure RBs alignment, considering  $p$  being an integer representing the RB index from NR reference frequency ( $p = 0$  for the NR RB hosting the NR Reference frequency), if:
+
+- The maximum number of RBs for a given channel bandwidth is even: NB-IoT carrier frequency should be further offset with 90 kHz, and equation (1) would become:
+
+$$100 * n + 2.5 * (2 * MDL + 1) = p * 180 + 5 * I_{15} * m - 7.5 + 90 \quad (7.3)$$
+
+With  $I_{15} = 3$  for channel raster below 3 GHz and  $I_{15} = 1$  for channel raster above 3 GHz
+
+Equation (7.2) would become:
+
+$$p = \frac{20 * n + \text{MDL} - I_{15} * m - 16}{36} \quad (7.4)$$
+
+$$p = \frac{20 * n + \text{MDL} - 3 * m - 16}{36}$$
+
+Or for channel raster below 3 GHz.
+
+- The maximum number of RBs for a given channel bandwidth is odd: no further offset shall be considered, equation (7.1) would become:
+
+$$100 * n + 2.5 * (2 * \text{MDL} + 1) = p * 180 + 5 * I_{15} * m - 7.5 \quad (7.5)$$
+
+With  $I_{15} = 3$  for channel raster below 3 GHz and  $I_{15} = 1$  for channel raster above 3 GHz
+
+Equation (7.2) would become:
+
+$$p = \frac{20 * n + \text{MDL} - I_{15} * m + 2}{36} \quad (7.6)$$
+
+$$p = \frac{20 * n + \text{MDL} - 3 * m + 2}{36}$$
+
+Or for channel raster below 3 GHz.
+
+###### 5.2.1.7.1.3 Channel bandwidth
+
+Also,  $p$  being the RB index from NR reference frequency,  $p$  has limited value determined from NR Channel bandwidth and from the corresponding spectrum utilization.
+
+So, if  $N_{\text{RB}}$  is the maximum number of RBs for a certain channel bandwidth (as specified by the transmission bandwidth configuration in TS 38.104 ([6])), considering  $p = 0$  for the centre RB in that channel bandwidth,  $p$  will be bounded. Equations (7.4) and (7.6) would have following additional conditions:
+
+- If  $N_{\text{RB}}$  is even:
+
+$$p = \frac{20 * n + \text{MDL} - 3 * m - 16}{36} \quad \text{with } -N_{\text{RB}}/2 \leq p \leq (N_{\text{RB}}/2) - 1 \quad (7.7)$$
+
+- If  $N_{\text{RB}}$  is odd:
+
+$$p = \frac{20 * n + \text{MDL} - 3 * m + 2}{36} \quad \text{with } -(N_{\text{RB}} - 1)/2 \leq p \leq (N_{\text{RB}} - 1)/2 \quad (7.8)$$
+
+Comparing to 100 kHz channel raster for both NR and NB-IoT, with NR SCS based channel raster, the possible positions of NB-IoT RB depend here of NR carrier frequency position. For a given NR channel bandwidth signal, it's then not possible to give the candidate list of NB-IoT RB as it also depends on NR-ARFCN value.
+
+###### 5.2.1.7.1.4 Conclusion
+
+NB-IoT and NR operating could coexist in NR bands supporting SCS based channel raster, but also optimizing resource utilization by aligning respective RBs for 15 kHz SCS. The RB index to deploy NB-IoT, for a given channel bandwidth with a transmission bandwidth configuration of  $N_{\text{RB}}$ , is given by:
+
+- If  $N_{RB}$  is even:
+
+$$p = \frac{20 * n + MDL - 3 * m - 16}{36} \quad \text{with } -N_{RB}/2 \leq p \leq (N_{RB}/2) - 1 \quad (\text{Eq7.1})$$
+
+- If  $N_{RB}$  is odd:
+
+$$p = \frac{20 * n + MDL - 3 * m + 2}{36} \quad \text{with } -(N_{RB} - 1)/2 \leq p \leq (N_{RB} - 1)/2 \quad (\text{Eq7.2})$$
+
+With the additional condition those candidates RBs shall not overlap in the following range:
+
+$$[ 1200N + 50M - (10 \times 180) - 7.5, 1200N + 50M + (10 \times 180) - 7.5 ] \text{ [kHz]} \quad (\text{Cond7.1})$$
+
+where  $N \in \{1, 2, \dots, 2499\}$  is an integer, and  $M \in \{1, 3, 5\}$ .
+
+From those equations, it's then possible to determine where to deploy NB-IoT in-band of a given NR frequency deployment. Or vice-versa, it's possible to determine how to deploy NR for a given NB-IoT frequency deployment, with NB-IoT operating in-band NR.
+
+Those equations could be used to determine the position of NB-IoT anchor RB ( $M_{DL}$  as then limited set of values  $\{-2, -1, 0, 1\}$ ), or of any non-anchor RB ( $M_{DL}$  possible values would be then in the range of  $\{-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9\}$ ).
+
+##### 5.2.1.7.2 UL considerations
+
+All SCS based channel raster are TDD bands, so the following UL consideration is focusing on TDD bands only.
+
+With E-UTRA, there is a 7.5 kHz offset in between DL and UL.
+
+In the scope of Rel-15 and the introduction of TDD support for NB-IoT, anticipating NR, the range of possible position frequency positions of NB-IoT TDD UL carrier has been extended in TS 36.104 [3].
+
+The NB-IoT UL frequency position was initially specified with:
+
+$$F_{UL} = F_{UL\_low} + 0.1(N_{UL} - N_{offs-UL}) + 0.0025 * (2M_{UL})$$
+
+with  $M_{UL}$  in the range of  $\{-10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9\}$ .
+
+While from Rel-15, and the introduction of NB-IoT TDD support, the specification is:
+
+$$F_{UL} = F_{UL\_low} + 0.1(N_{UL} - N_{offs-UL}) + 0.0025 * (2M_{UL})$$
+
+with  $M_{UL}$  in the range of  $\{-11, -10, -9.5, -9, -8.5, -8, -7.5, -7, -6.5, -6, -5.5, -5, -4.5, -4, -3.5, -3, -2.5, -2, -1.5, -1, -0.5, 0, 0.5, 1, 1.5, 2, 2.5, 3, 3.5, 4, 4.5, 5, 5.5, 6, 6.5, 7, 7.5, 8, 8.5, 9, 9.5, 10, 11\}$  for TDD.
+
+It's then possible for NB-IoT TDD to align UL with DL carrier.
+
+NR UL and DL carriers being aligned, with a 0 kHz offset, this means NB-IoT TDD DL and UL could coexist operating in-band with NR DL and UL, keeping orthogonality in between tones.
+
+The only drawback is that NB-IoT UL carrier can't remain at exact same frequency position when migrating from E-UTRA TDD to NR TDD but shall be shifted with an offset of 7.5 kHz.
+
+##### 5.2.1.7.3 Example
+
+Let's consider a NR 10MHz channel bandwidth ( $N_{RB}=52$ ) deployed in band n41. This band uses 15 kHz or 30 kHz SCS based channel raster, we'll consider 15 kHz SCS in the following.
+
+Let's assume the RF reference frequency for this deployment is  $N_{REF}=512400$ , so  $F_{REF} = 2,562$  MHz.
+
+$N_{RB}$  being even, such deployment would be in between  $2,562,000-7.5-4,680=2,557,312.5$  kHz (which corresponds to lower edge of RB #(-26)) and  $2,520,000-7.5+4,680=2,556,672.5$  kHz (which corresponds to upper edge of RB #25).
+
+As seen in 2.5.4, the SS block would occupy a frequency block from  $1200*N+50*M-10*180-7.5$  kHz to  $1200*N+50*M+10*180-7.5$  kHz.
+
+Assuming  $N=2134$  and  $M=3$  (GSCN=6402), being subcarrier aligned, the SS block would occupy frequency range  $[2,559,142.5 ; 2,562,742.5]$  kHz. In other words, SS block would overlap NR RBs #(-17) to #4.
+
+Considering NB-IoT and NR RB alignment, NB-IoT RB could then be deployed in one of the following NR DL RBs: [-26, -21, 9, 14, 19, 24].
+
+### 5.2.2 Power boosting
+
+For Rel-13 power boosting for E-UTRA guard band operation and in-band operation is introduced in both TS 36.104 and TS 37.104. The minimum requirement is +6 dB power boosting for one NB-IoT RB located within E-UTRA transmission bandwidth configuration for in-band operation or adjacent to the E-UTRA transmission bandwidth configuration edge as close as possible for guard band operation (except for guard band operation with E-UTRA 5 MHz channel bandwidth). Legacy deployment should be taken into account and similar hardware capability should be maintained. Hence +6 dB power boosting should be kept for the migration scenario. Meanwhile +6 dB power boosting will be challenging when NB-IoT is located at NR edge positions since NR spectrum utilization with 15 kHz SCS is much higher than EUTRA for > 5 MHz channel bandwidth. Considering these aspects, power boosting for NB-IoT operation in NR in-band is defined as below,
+
+- For 5 MHz and 10 MHz channel bandwidth, specify the minimum +6 dB power boosting requirement for in-band 180 kHz NB-IoT RB.
+- For 15 MHz channel bandwidth, specify the minimum +6 dB power boosting requirement for in-band center  $77 \times 180$  kHz plus 15 kHz at each edge.
+- For 20 MHz channel bandwidth, specify the minimum +6 dB power boosting requirement for in-band center  $102 \times 180$  kHz plus 15 kHz at each edge.
+- For >20 MHz channel bandwidth, specify the minimum +6 dB power boosting requirement for in-band 180 kHz NB-IoT RB within center 90% of NR channel bandwidth.
+- For >10 MHz channel bandwidth, specify +3 dB power boosting requirement for other in-band 180 kHz NB-IoT RBs.
+- BS manufacturer can declare support of higher power boosting.
+
+### 5.2.3 Numerologies
+
+As NR could support several numerologies, e.g. 15KHz, 30KHz and 60KHz in FR1 which might be different from NB-IoT numerologies (15KHz SCS in downlink and 15KHz/3.75KHz SCS in the uplink), there might exist mixed numerology configuration which would result in interference between NR subcarrier and NB-IoT subcarrier when NB-IoT carrier is deployed within NR carrier. In general, guard band between different numerology should be reserved for performance protection, however this should be up to the BS implementation. Similar as the mixed numerology in NR scenarios, no requirement is defined for mixed numerology between NR and NB-IoT.
+
+## 5.3 NB-IoT operating in NR guard-band
+
+### 5.3.1 Spectrum utilization consideration
+
+Compared to LTE which has fixed spectrum utilization for channel bandwidth larger than and equal to 3 MHz, the spectrum utilization has been improved for NR especially for 15 kHz SCS and channel bandwidth larger than 5MHz. Spectrum utilization values in Rel-15 are the results of companies' compromise. In those cases, NB-IoT operating in NR guard band need further increase the spectrum utilization hence it is agreed that no RF requirement will be specified in Rel.15/Rel.16 as stated in Clause 5.3.3.. For SCS other than 15 kHz, in some scenarios, the spectrum utilization may be less than that in LTE. For those scenarios some extra guard need to be considered for the co-existence of mixed numerology. As agreed in Clause 5.2.3, no requirement would be specified for mixed numerology. Again the spectrum utilization was optimized for 30 kHz and 60 kHz SCS, the operation in guard band will depend on the implementation margin and need to be investigated case by case.
+
+### 5.3.2 Refarming consideration
+
+When refarming the LTE carrier to NR carrier with the existence of downlink anchor guard-band NB-IoT operations, keeping same NB-IoT carrier frequency, NB-IoT might partially operate in NR in-band and partially in NR guard band as shown in figure 5.3.1.
+
+![Figure 5.3.1: Downlink anchor guard-band NB-IoT operation for 10MHz LTE channel bandwidth refarming to 15kHz SCS with 100kHz channel raster NR. The diagram shows two frequency spectra. The top spectrum represents the LTE carrier with a 10MHz bandwidth centered at 'LTE center frequency'. It shows PRB 0 at the left edge, PRB 24 and 25 around the DC center, and PRB 49 at the right edge. Frequency markers are 100*n - 4597.5 kHz, 100*n kHz, and 100*n + 4597.5 kHz. The bottom spectrum represents the NR carrier after refarming, centered at 'NR center frequency'. It shows PRB 0 at the left edge, PRB 25 and 26 around the DC center, and PRB 51 at the right edge. Frequency markers are 100*n - 4597.5 kHz, 100*n kHz, and 100*n + 4582.5 kHz. A callout box indicates that the guard-band NB-IoT carrier partially falls into the NR guard-band. A legend at the bottom shows a blue hatched rectangle for 'NB-IoT carrier' and a white rectangle for 'LTE/NR PRB'. A 312.5kHz offset is shown between the right edge of the NR carrier and the right edge of the LTE carrier.](812b773680b611c18d49243e102b895a_img.jpg)
+
+Figure 5.3.1: Downlink anchor guard-band NB-IoT operation for 10MHz LTE channel bandwidth refarming to 15kHz SCS with 100kHz channel raster NR. The diagram shows two frequency spectra. The top spectrum represents the LTE carrier with a 10MHz bandwidth centered at 'LTE center frequency'. It shows PRB 0 at the left edge, PRB 24 and 25 around the DC center, and PRB 49 at the right edge. Frequency markers are 100\*n - 4597.5 kHz, 100\*n kHz, and 100\*n + 4597.5 kHz. The bottom spectrum represents the NR carrier after refarming, centered at 'NR center frequency'. It shows PRB 0 at the left edge, PRB 25 and 26 around the DC center, and PRB 51 at the right edge. Frequency markers are 100\*n - 4597.5 kHz, 100\*n kHz, and 100\*n + 4582.5 kHz. A callout box indicates that the guard-band NB-IoT carrier partially falls into the NR guard-band. A legend at the bottom shows a blue hatched rectangle for 'NB-IoT carrier' and a white rectangle for 'LTE/NR PRB'. A 312.5kHz offset is shown between the right edge of the NR carrier and the right edge of the LTE carrier.
+
+Figure 5.3.1: Downlink anchor guard-band NB-IoT operation for 10MHz LTE channel bandwidth refarming to 15kHz SCS with 100kHz channel raster NR
+
+As shown in figure 5.3.1, due to the carrier shift by 15kHz, the guard-band NB-IoT PRB operating in the upper half of the LTE 10MHz channel bandwidth will not be aligned with NR PRB 51, which results in one NB-IoT subcarrier falling into NR guard band. However, the frequency distance from NB-IoT PRB edge to NR channel bandwidth edge is not smaller than the minimum NR guard band. Thus there will be no issue for the radio to support this case.
+
+So it is concluded that considering legacy deployments, even if one NB-IoT 15 kHz sub-carrier would operate in NR guard band, still consider this case as NB-IoT operation in NR in-band.
+
+### 5.3.3 Conclusion
+
+NB-IoT operating in NR guard band would be handled as implementation issue and RF requirements will not be specified in Rel-15 (nor in Rel-16 unless new Rel-16 features make this essential).
+
+## 5.4 NB-IoT standalone operating
+
+In Rel-13 when introduction of NB-IoT in the specifications, for stand-alone operation mode, the coexistence between NB-IoT and legacy LTE/UMTS/GSM systems was verified both for the downlink and uplink in TR 36.802. The summary of system level simulation results for coexistence study between Rel-15 NR and Rel-13/14/15 NB-IoT standalone operation is provided in annex A. Based on coexistence study, the RF requirements such as ACLR and ACS for NB-IoT was defined to guarantee coexistence with the legacy systems. And for FR1 the LTE ACLR and ACS requirements are reused for NR. Hence there should be no issue for NB-IoT standalone coexistence with NR.
+
+In addition, in Rel-15 MSR specification, standalone NB-IoT+LTE+NR Multi-Standard operation is supported with capability set (CS17). The corresponding core requirements and conformance testing are already handled in MSR specifications.
+
+## 5.5 Synchronization between NR and NB-IoT
+
+In order to analyze the NB-IoT coexisting with NR, longest CP and shortest CP for NR are considered as two extreme cases in which whether timing misalignment between NB-IoT and NR would exceed CP or not could be identified.
+
+If 15kHz SCS is used in the NR carrier where NR has the longest CP, then the TAGs misalignment analysis between NB-IoT and NR will be the same as that between NB-IoT and E-UTRA. Therefore, there should be no interference issue due to TAGs misalignment between NB-IoT and NR if 15kHz SCS is used in the NR system, otherwise such issue would have occurred already between NB-IoT and E-UTRA before the migration to NR. Meanwhile some detailed analysis is done in Case 1 where it could be found that timing misalignment between NB-IoT and NR is still within the CP, this also indicates there should be no interference issues due to TAGs misalignment.
+
+On the other hand, if 30kHz or 60kHz SCS is used in the NR carrier, the NB-IoT UE maximum transmit timing error of  $101.33T_s (=80T_s+13.33T_s+8T_s)$  alone as explained in the following will be larger than the CP length of the NR symbol. Therefore, when the NR UE maximum transmit timing error (which is varied according to the SCS used in the NR carrier) is also considered, there would potentially be interference issue due to the inter-symbol-interference between the NB-IoT and NR symbols as illustrated in Case 2. However, it has been agreed that this type of mixed numerology cases between NB-IoT and NR should be up to the BS implementation and no requirement is defined in the RAN4 specifications. Feasible BS implementation options include separate digital filtering and internal gap between the NB-IoT and NR carriers.
+
+### Case 1: the timing misalignment scenario with NR SCS 15KHz
+
+For NR UE transmit timing, if uplink subcarrier spacing is configured with 15KHz and SSB SCS is configured with 15KHz which is specified with worst transmit timing error for uplink SCS 15KHz, the maximum transmit timing error should be  $12 \cdot 64 \cdot T_c + 256 \cdot T_c + 8 \cdot 64 \cdot T_c$  equal to  $(12+4+8) \cdot 64 \cdot T_c$  equal to  $24 \cdot T_s$  which is the same as the maximum LTE UE transmitting error. Based on the above considerations, maximum arrival timing difference between NR carrier and NB-IoT carrier should be 4.0798us as shown in Figure 5.5-1 which is less than the NR CP length 4.96us if SCS 15KHz is configured for NR.
+
+![Figure 5.5-1: Timing diagram showing the maximum arrival timing difference between NR and NB-IoT in Uplink. The diagram illustrates three vertical lines representing timing points: 'Reference timing' (blue), 'NR UE timing' (red), and 'NB UE timing' (blue). The horizontal axis is labeled 't/us'. The distance between 'Reference timing' and 'NR UE timing' is 0.7813us. The distance between 'Reference timing' and 'NB UE timing' is 3.2985us. The distance between 'NR UE timing' and 'NB UE timing' is 4.0798us. Text in the top right corner specifies 'SSB SCS = 15KHz; Uplink SCS = 15KHz;'.](17cd95aa220e50963bf6eb9818e33163_img.jpg)
+
+Detailed description of Figure 5.5-1: The figure is a timing diagram on a horizontal axis labeled 't/us'. There are three vertical arrows pointing upwards from the axis. The first arrow is red and labeled 'NR UE timing'. To its right is a blue arrow labeled 'Reference timing'. Further to the right is another blue arrow labeled 'NB UE timing'. A red double-headed horizontal arrow between 'NR UE timing' and 'Reference timing' is labeled '0.7813us'. A blue double-headed horizontal arrow between 'Reference timing' and 'NB UE timing' is labeled '3.2985us'. A larger red double-headed horizontal arrow spanning from 'NR UE timing' to 'NB UE timing' is labeled '4.0798us'. In the upper right area, text states 'SSB SCS = 15KHz;' and 'Uplink SCS = 15KHz;'.
+
+Figure 5.5-1: Timing diagram showing the maximum arrival timing difference between NR and NB-IoT in Uplink. The diagram illustrates three vertical lines representing timing points: 'Reference timing' (blue), 'NR UE timing' (red), and 'NB UE timing' (blue). The horizontal axis is labeled 't/us'. The distance between 'Reference timing' and 'NR UE timing' is 0.7813us. The distance between 'Reference timing' and 'NB UE timing' is 3.2985us. The distance between 'NR UE timing' and 'NB UE timing' is 4.0798us. Text in the top right corner specifies 'SSB SCS = 15KHz; Uplink SCS = 15KHz;'.
+
+Figure 5.5-1. the maximum arrival timing difference between NR and NB-IoT in Uplink
+
+### Case 2: the timing misalignment scenario with NR SCS 60KHz
+
+For NR UE transmit timing, if uplink subcarrier spacing is configured with 60KHz and SSB SCS configured with 30KHz which is specified with the worst transmit timing error for uplink SCS 60KHz, the maximum transmit timing error should be  $10 \cdot 64 \cdot T_c + 128 \cdot T_c + 8 \cdot 64 \cdot T_c / 4$  equal to 14  $T_s$  (0.4557us). Based on the above consideration, the
+
+maximum arrival timing difference between NR carrier and NB-IoT carrier should be 3.7542us as shown in Figure 5.5-2 which is larger than the NR CP length 1.17us if SCS 60KHz is configured for NR.
+
+![Figure 5.5-2: Timing diagram showing the maximum arrival timing difference between NR and NB-IoT in Uplink. The diagram shows three vertical lines representing timing references: 'Reference timing' (blue), 'NR UE timing' (red), and 'NB UE timing' (blue). The time difference between 'Reference timing' and 'NR UE timing' is 0.4557us. The time difference between 'Reference timing' and 'NB UE timing' is 3.2985us. The total time difference between 'NR UE timing' and 'NB UE timing' is 3.7542us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 60KHz. The x-axis is labeled t/us.](a289b64f80c6df506c0c55d553fc4496_img.jpg)
+
+Figure 5.5-2: Timing diagram showing the maximum arrival timing difference between NR and NB-IoT in Uplink. The diagram shows three vertical lines representing timing references: 'Reference timing' (blue), 'NR UE timing' (red), and 'NB UE timing' (blue). The time difference between 'Reference timing' and 'NR UE timing' is 0.4557us. The time difference between 'Reference timing' and 'NB UE timing' is 3.2985us. The total time difference between 'NR UE timing' and 'NB UE timing' is 3.7542us. Text on the right indicates SSB SCS = 15KHz and Uplink SCS = 60KHz. The x-axis is labeled t/us.
+
+Figure 5.5-2. the maximum arrival timing difference between NR and NB-IoT in Uplink
+
+### 5.5.1 Background
+
+The specified E-UTRA TDD configurations are listed in Table 5.5.1.
+
+NB-IoT TDD was specified in Release 15. Due to the lack of available resources, RAN1 agreed to not specify NB-IoT TDD for configuration #0 and #6 (red in Table 5.5.1). Moreover, to avoid any slot truncations, only TDD configuration #1 and #4 (green in Table 5.5.1) are supporting NB-IoT 3.75 kHz SCS. Due to the above reasons, TDD Test Models used for BS RF conformance testing (TS 36.141 [7]) are based on configuration #1 and special subframe configuration 8 when testing E-UTRA with NB-IoT in-band/guard band TDD.
+
+Table 5.5.1. Specified LTE TDD configurations
+
+| Uplink-downlink configuration | Downlink-to-Uplink Switch-point periodicity | Subframe number |   |   |   |   |   |   |   |   | Number of subframes / frame |    |    |   |
+|-------------------------------|---------------------------------------------|-----------------|---|---|---|---|---|---|---|---|-----------------------------|----|----|---|
+|                               |                                             | 0               | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9                           | DL | UL | S |
+| 0                             | 5 ms                                        | D               | S | U | U | U | D | S | U | U | U                           | 2  | 6  | 2 |
+| 1                             | 5 ms                                        | D               | S | U | U | D | D | S | U | U | D                           | 4  | 4  | 2 |
+| 2                             | 5 ms                                        | D               | S | U | D | D | D | S | U | D | D                           | 6  | 2  | 2 |
+| 3                             | 10 ms                                       | D               | S | U | U | U | D | D | D | D | D                           | 6  | 3  | 1 |
+| 4                             | 10 ms                                       | D               | S | U | U | D | D | D | D | D | D                           | 7  | 2  | 1 |
+| 5                             | 10 ms                                       | D               | S | U | D | D | D | D | D | D | D                           | 8  | 1  | 1 |
+| 6                             | 5 ms                                        | D               | S | U | U | U | D | S | U | U | D                           | 3  | 5  | 2 |
+
+NR TDD configurations are very flexible. Comparing to E-UTRA TDD, no predefined pattern has been specified which makes possible to configure TDD according to any specific need. Two different *patterns* might be configured (RRC), and for each pattern following parameters are defined:
+
+- The *periodicity*.
+
+- The *number of slots* (one for downlink, one for uplink)
+- The *number of symbols* (one for downlink, one for uplink), this number of symbols could be used to define an equivalent to LTE special sub-frame.
+
+### 5.5.2 TDD synchronization
+
+#### 5.5.2.1 General
+
+NR and NB-IoT TDD synchronization could be managed:
+
+- Either by defining one or two NR patterns (section 5.5.2.2).
+- Overriding UE specific dedicated configuration (section 5.5.2.3).
+
+#### 5.5.2.2 NR TDD patterns for synchronization with NB-IoT
+
+Following figures show how to configure NR TDD to operate NB-IoT both 15 kHz and 3.75 kHz SCS:
+
+- Figure 5.5.1-1 using one NR pattern to align with LTE configuration #1.
+- Figure 5.5.1-2 using two NR patterns to align with LTE configuration #4.
+
+![Figure 5.5.1-1: NR TDD pattern to sync with LTE TDD configuration #1. The diagram shows two horizontal timelines. The top timeline is labeled 'LTE radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red). The bottom timeline is labeled 'NR radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red). A double-headed arrow labeled 'Configured NR TDD pattern' spans the first four subframes of the NR timeline, indicating alignment with the first four subframes of the LTE timeline.](d3b5eac55166fc428a223bba5c46961b_img.jpg)
+
+Figure 5.5.1-1: NR TDD pattern to sync with LTE TDD configuration #1. The diagram shows two horizontal timelines. The top timeline is labeled 'LTE radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red). The bottom timeline is labeled 'NR radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), followed by a gap, then UL (red). A double-headed arrow labeled 'Configured NR TDD pattern' spans the first four subframes of the NR timeline, indicating alignment with the first four subframes of the LTE timeline.
+
+Figure 5.5.1-1: NR TDD pattern to sync with LTE TDD configuration #1
+
+![Figure 5.5.1-2: NR TDD pattern to sync with LTE TDD configuration #4. The diagram shows two horizontal timelines. The top timeline is labeled 'LTE radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red). The bottom timeline is labeled 'NR radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red). Two double-headed arrows labeled 'Configured NR TDD pattern 1' and 'Configured NR TDD pattern 2' span the first four subframes and the next four subframes of the NR timeline, indicating alignment with the first four subframes and the next four subframes of the LTE timeline.](14515d82ffeec9475b9add3036ff26ab_img.jpg)
+
+Figure 5.5.1-2: NR TDD pattern to sync with LTE TDD configuration #4. The diagram shows two horizontal timelines. The top timeline is labeled 'LTE radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red). The bottom timeline is labeled 'NR radio frame' and shows a sequence of subframes: DL (blue), UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red), UL (red), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), DL (blue), followed by a gap, then UL (red). Two double-headed arrows labeled 'Configured NR TDD pattern 1' and 'Configured NR TDD pattern 2' span the first four subframes and the next four subframes of the NR timeline, indicating alignment with the first four subframes and the next four subframes of the LTE timeline.
+
+Figure 5.5.1-2: NR TDD pattern to sync with LTE TDD configuration #4
+
+#### 5.5.2.3 Overriding UE specific dedicated configuration
+
+As mentioned before, for E-UTRA TDD configuration with NB-IoT operating in-band and/or guard band, the agreed test model in Annex E.0A of TS 37.141 [8] is based on configuration 1, with 5ms switch period and the special subframe configuration 7, i.e. uplink/downlink subframe ratio is 1:2, DwPTS = 10 symbols, GP = 2 symbols, UpPTS = 2 symbols. The specific E-UTRA TDD configuration is illustrated in the Figure 5.5.3-1.
+
+![Diagram of TDD configuration #1 showing two frames. The first frame has 10 subframes: D, S, U, U, D, D, S, U, U, D. A callout 'Special subframe#7' points to the 'S' subframe, showing it consists of 10 'D' symbols, 2 'G' symbols, and 2 'U' symbols. A 'Frame' label with an arrow spans the 10 subframes of the second frame.](552265bdbcf6d43d341fd018a9076269_img.jpg)
+
+**TDD configuration#1**
+
+**Special subframe#7**
+
+Diagram of TDD configuration #1 showing two frames. The first frame has 10 subframes: D, S, U, U, D, D, S, U, U, D. A callout 'Special subframe#7' points to the 'S' subframe, showing it consists of 10 'D' symbols, 2 'G' symbols, and 2 'U' symbols. A 'Frame' label with an arrow spans the 10 subframes of the second frame.
+
+Figure 5.5.3-1. uplink/downlink configuration for E-UTRA TDD test model (2 frames for conformance testing)
+
+According to NR slot configuration, UE specific dedicated configuration could be used to override the flexible slots configured by the *SIB1 tdd-UL-DL-Configuration*. For different SCS, the same ratio of DL and UL are assumed to be configured, therefore based on the following Figure 5.5.3-2, the DL,UL and special subframe could be configured by the UE specific configuration.
+
+![Diagram showing slot and symbol configurations. The top part shows a slot with 14 symbols: 10 Downlink (D), 2 Guard (G), and 2 Uplink (U). Labels indicate d_sym (10 symbols), u_sym (2 symbols), and 'flexible symbols' spanning the G and U symbols. The bottom part shows two frames, Frame#0 and Frame#1, each with 5 slots. Slot 0 is Downlink (D), slots 1-4 are Flexible (F). Periodicity P=5ms and P2=5ms are indicated. A 'd_slots' label indicates the first slot.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg)
+
+**SIB1: tdd-UL-DL-ConfigurationCommon**  
+ $u_{ref}=15$  from *referenceSubcarrierSpacing*  
+ $P=5$  from *dl-UL-transmissionPeriodicity*;  
+ $d_{slots}=1$  from *nrofDownlinkSlots*;  
+ $d_{sym}=0$  from *nrofDownlinkSymbols*;  
+ $u_{slots}=0$  from *nrofUplinkSlots*;  
+ $u_{sym}=0$  from *nrofUplinkSymbols*;
+
+**RRC Config: tdd-UL-DL-Dedicated**  
+**slotIndex=1**  
+nrofDownlinkSymbols=10  
+nrofUplinkSymbols=2  
+**slotIndex=2**  
+symbols=allUplink  
+**slotIndex=3**  
+symbols=allUplink  
+**slotIndex=4**  
+symbols=allDownlink
+
+Diagram showing slot and symbol configurations. The top part shows a slot with 14 symbols: 10 Downlink (D), 2 Guard (G), and 2 Uplink (U). Labels indicate d\_sym (10 symbols), u\_sym (2 symbols), and 'flexible symbols' spanning the G and U symbols. The bottom part shows two frames, Frame#0 and Frame#1, each with 5 slots. Slot 0 is Downlink (D), slots 1-4 are Flexible (F). Periodicity P=5ms and P2=5ms are indicated. A 'd\_slots' label indicates the first slot.
+
+Figure 5.5.3-2. uplink/downlink configuration for E-UTRA TDD test model (2 frames for conformance testing)
+
+The specific TDD configuration for 15 kHz SCS shown in the Figure 5.5.3-2 could be summarized in the following table 5.5.3-1.
+
+Table 5.5.3-1: Configurations
+
+| Field name                                                | 15 kHz SCS     |
+|-----------------------------------------------------------|----------------|
+| <i>Tdd-UL-DL-Configuration</i>                            |                |
+| <i>referenceSubcarrierSpacing</i>                         | 15             |
+| <i>Periodicity (ms) for dl-UL-TransmissionPeriodicity</i> | 5              |
+| <i>nrofDownlinkSlots</i>                                  | 1              |
+| <i>nrofDownlinkSymbols</i>                                | 0              |
+| <i>nrofUplinkSlots</i>                                    | 0              |
+| <i>nrofUplinkSymbols</i>                                  | 0              |
+| <i>Tdd-UL-DL-ConfigDedicated</i>                          |                |
+| <i>nrofDownlinkSymbols</i>                                | For Slot#1: 11 |
+| <i>nrofUplinkSymbols</i>                                  | For Slot#1: 2  |
+| <i>slotIndex</i>                                          | 1              |
+| <i>nrofDownlinkSymbols</i>                                | 11             |
+| <i>nrofUplinkSymbols</i>                                  | 2              |
+| <i>slotIndex</i>                                          | 2, 3           |
+| <i>symbols</i>                                            | allUplink      |
+| <i>slotIndex</i>                                          | 4              |
+| <i>symbols</i>                                            | allDownlink    |
+
+## 5.6 Specification and conformance impact
+
+MSR BS supporting NR and LTE+NB-IoT (LTE in-band/guard band) could also meet current RF requirements when operating NR+(LTE)+NB-IoT (NR in-band) with following limitations:
+
+- Same NR channel bandwidth as LTE
+- NR uses 15 kHz SCS
+- NB-IoT carrier frequency kept when operating with LTE and NR, or shifted closer to NR carrier.
+
+Therefore, MSR BS could operate NB-IoT in NR in-band with above limitations and no need to redo conformance testing in this case.
+
+To remove any limitation, specification update is needed to add support for NB-IoT operating in NR in-band in TS 38.104, TS 38.141-1, TS 37.104 and TS 37.141 in Rel-16 the latest.
+
+# 6 Summary
+
+For NB-IoT co-existence with NR, 3 system scenarios have been studied: NB-IoT operation in NR in-band, NB-IoT operation in NR guard band and NB-IoT standalone operation.
+
+For NB-IoT operation in NR in-band, RB alignment, power boosting and numerologies have been addressed. NB-IoT and NR operating with 15 kHz SCS could coexist in NR band while optimizing resource utilization by aligning respective RBs. And similar as NR, no requirement on mixed numerology is defined for coexistence between NB-IoT and NR.
+
+For NB-IoT operation in NR guard band, the refarming scenarios have been considered and it is concluded that even if one NB-IoT 15 kHz sub-carrier would operate in NR guard band, still consider this case as NB-IoT operation in NR in-band. NB-IoT operating in NR guard band would mean revisiting agreed spectrum utilization in Rel-15, which would be too early. RF requirements will not be specified in Rel-15 (nor in Rel-16 unless new Rel-16 features make this essential).
+
+For NB-IoT standalone operation, based on coexistence study, it is concluded that there is no issue for NB-IoT standalone coexistence with NR.
+
+MSR BS supporting NR and E-UTRA+NB-IoT (E-UTRA in-band and guard) could operate NB-IoT in NR in-band with the limitations listed in clause 5.6 and no need to redo the conformance testing. To remove listed limitations, specification update is needed in Rel-16 for TS 38.104, TS 38.141-1, TS 37.104 and TS 37.141.
+
+# --- Annex A: Coexistence simulation
+
+## A.1 Downlink coexistence simulation results using legacy LTE/UMTS/GSM channel model
+
+The system level simulation methodology and assumptions in TR 36.802 for coexistence study between NB-IoT standalone operation and legacy LTE/UMTS/GSM systems are used here. 10MHz channel bandwidth are used for both LTE and NR here, and 15kHz SCS is used for NR as it has a higher spectrum utilization than 30kHz SCS for 10MHz channel bandwidth. Note that the NB-IoT BS ACLR2 of 50dBc is used here because the NB-IoT BS ACLR1 will fall into the 500kHz internal guard-band of the 10MHz LTE channel, as well as the 312.5kHz minimum guard-band of the 10MHz 15kHz SCS NR channel. Consequently, the overall ACIR is dominated by the LTE or NR UE ACS1 of 33dBc.
+
+The CDFs of the coupling loss between victim LTE UE and BS and the DL SINR of victim LTE UE for 900MHz and 2GHz carrier frequency are shown in Figure A.1-1 below.
+
+![CDF plot of Coupling loss between victim UE and BS (dB) for Serving BS and Interfering BS.](20727e57890be6da5692a02d13c0a8ec_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the coupling loss between a victim User Equipment (UE) and a Base Station (BS). The x-axis represents the 'Coupling loss between victim UE and BS (dB)' ranging from 60 to 200. The y-axis represents the 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Serving BS' and a red line for 'Interfering BS'. The 'Serving BS' curve starts at approximately 65 dB and reaches 100% CDF at about 130 dB. The 'Interfering BS' curve starts at approximately 80 dB and reaches 100% CDF at about 170 dB. The 'Serving BS' curve is consistently above the 'Interfering BS' curve, indicating that the coupling loss to the serving BS is generally lower than to the interfering BS.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 60                 | 0                  | 0                      |
+| 80                 | 10                 | 0                      |
+| 100                | 50                 | 2                      |
+| 120                | 95                 | 15                     |
+| 140                | 100                | 60                     |
+| 160                | 100                | 95                     |
+| 180                | 100                | 100                    |
+| 200                | 100                | 100                    |
+
+CDF plot of Coupling loss between victim UE and BS (dB) for Serving BS and Interfering BS.
+
+![CDF plot of DL SINR of victim UE (dB) for Without and With Interfering BS.](1b1bb497e39fcc025a3fc8bd4fc78d9a_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the Downlink Signal-to-Interference-plus-Noise Ratio (DL SINR) of a victim UE. The x-axis represents the 'DL SINR of victim UE (dB)' ranging from -15 to 20. The y-axis represents the 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Without Interfering BS' and a red line for 'With Interfering BS'. Both curves are nearly identical, starting at approximately -10 dB and reaching 100% CDF at about 15 dB. The 'With Interfering BS' curve is slightly lower than the 'Without Interfering BS' curve in the middle range, indicating a slight degradation in SINR due to interference.
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -15          | 0                              | 0                           |
+| -10          | 0                              | 0                           |
+| -5           | 5                              | 4                           |
+| 0            | 35                             | 33                          |
+| 5            | 65                             | 63                          |
+| 10           | 90                             | 88                          |
+| 15           | 100                            | 100                         |
+| 20           | 100                            | 100                         |
+
+CDF plot of DL SINR of victim UE (dB) for Without and With Interfering BS.
+
+(a) With 900MHz carrier frequency
+
+![CDF plot of coupling loss between victim UE and BS for Serving BS and Interfering BS.](7119b28e39fa3784606bf8b8f44e4f9d_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the coupling loss between a victim UE and a base station (BS). The x-axis is labeled 'Coupling loss between victim UE and BS (dB)' and ranges from 60 to 200 in increments of 20. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100 in increments of 10. There are two curves: a blue curve for 'Serving BS' and a red curve for 'Interfering BS'. The blue curve starts at approximately 65 dB and reaches 100% CDF at about 130 dB. The red curve starts at approximately 80 dB and reaches 100% CDF at about 170 dB.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 60                 | 0                  | 0                      |
+| 80                 | 5                  | 0                      |
+| 100                | 40                 | 2                      |
+| 120                | 95                 | 15                     |
+| 140                | 100                | 60                     |
+| 160                | 100                | 95                     |
+| 180                | 100                | 100                    |
+| 200                | 100                | 100                    |
+
+CDF plot of coupling loss between victim UE and BS for Serving BS and Interfering BS.
+
+![CDF plot of DL SINR of victim UE with and without interfering BS.](20e597e389dfd8d131e05ad6e1617dcd_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the DL SINR of a victim UE. The x-axis is labeled 'DL SINR of victim UE (dB)' and ranges from -15 to 20 in increments of 5. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100 in increments of 10. There are two curves: a blue curve for 'Without Interfering BS' and a red curve for 'With Interfering BS'. Both curves start at approximately -10 dB and reach 100% CDF at about 15 dB. The curves are nearly perfectly overlaid, showing that the presence of an interfering BS has a negligible impact on the DL SINR distribution in this scenario.
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -15          | 0                              | 0                           |
+| -10          | 0                              | 0                           |
+| -5           | 5                              | 5                           |
+| 0            | 35                             | 35                          |
+| 5            | 65                             | 65                          |
+| 10           | 90                             | 90                          |
+| 15           | 100                            | 100                         |
+| 20           | 100                            | 100                         |
+
+CDF plot of DL SINR of victim UE with and without interfering BS.
+
+(b) With 2GHz carrier frequency
+
+Figure A.1-1: For LTE victim UE
+
+The CDFs of the coupling loss between victim NR UE and BS and the DL SINR of victim NR UE for 900MHz and 2GHz carrier frequency are shown in Figure A.1-2 below.
+
+![CDF plot of coupling loss between victim UE and BS (dB) for Serving BS and Interfering BS.](6f10f5cbc920e8c4340d869aae0f1f58_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the coupling loss between a victim User Equipment (UE) and a Base Station (BS) in dB. The x-axis represents the coupling loss in dB, ranging from 60 to 200 with major ticks every 20 units. The y-axis represents the CDF in percentage, ranging from 0 to 100 with major ticks every 10 units. Two curves are plotted: a blue line for 'Serving BS' and a red line for 'Interfering BS'. The 'Serving BS' curve starts at approximately 2% at 70 dB and reaches 100% at about 130 dB. The 'Interfering BS' curve starts at approximately 1% at 80 dB and reaches 100% at about 170 dB.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 60                 | 0                  | 0                      |
+| 80                 | 5                  | 1                      |
+| 100                | 40                 | 2                      |
+| 120                | 95                 | 15                     |
+| 140                | 100                | 60                     |
+| 160                | 100                | 95                     |
+| 180                | 100                | 100                    |
+| 200                | 100                | 100                    |
+
+CDF plot of coupling loss between victim UE and BS (dB) for Serving BS and Interfering BS.
+
+![CDF plot of DL SINR of victim UE (dB) for 'Without Interfering BS' and 'With Interfering BS'.](853ef5420f0432e626e83987e3f38a0b_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the Downlink Signal-to-Interference-plus-Noise Ratio (DL SINR) of a victim UE in dB. The x-axis represents the DL SINR in dB, ranging from -15 to 20 with major ticks every 5 units. The y-axis represents the CDF in percentage, ranging from 0 to 100 with major ticks every 10 units. Two curves are plotted: a blue line for 'Without Interfering BS' and a red line for 'With Interfering BS'. Both curves are nearly perfectly overlaid, starting at 0% at -10 dB and reaching 100% at approximately 17 dB.
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -15          | 0                              | 0                           |
+| -10          | 0                              | 0                           |
+| -5           | 5                              | 5                           |
+| 0            | 35                             | 35                          |
+| 5            | 65                             | 65                          |
+| 10           | 90                             | 90                          |
+| 15           | 98                             | 98                          |
+| 20           | 100                            | 100                         |
+
+CDF plot of DL SINR of victim UE (dB) for 'Without Interfering BS' and 'With Interfering BS'.
+
+(a) With 900MHz carrier frequency
+
+![CDF plot of coupling loss between victim UE and BS for Serving BS and Interfering BS.](a844248c1fa0a79f187fc9aa111182f7_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the coupling loss between a victim UE and a BS. The x-axis is labeled 'Coupling loss between victim UE and BS (dB)' and ranges from 60 to 200. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. Two curves are plotted: a blue line for 'Serving BS' and a red line for 'Interfering BS'. The 'Serving BS' curve starts at approximately 0% at 70 dB and reaches 100% at about 130 dB. The 'Interfering BS' curve starts at approximately 0% at 80 dB and reaches 100% at about 170 dB.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 60                 | 0                  | 0                      |
+| 80                 | 5                  | 0                      |
+| 100                | 40                 | 2                      |
+| 120                | 95                 | 15                     |
+| 140                | 100                | 60                     |
+| 160                | 100                | 95                     |
+| 180                | 100                | 100                    |
+| 200                | 100                | 100                    |
+
+CDF plot of coupling loss between victim UE and BS for Serving BS and Interfering BS.
+
+![CDF plot of DL SINR of victim UE with and without interfering BS.](051638d871c75230edb3d005fa668810_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the DL SINR of a victim UE. The x-axis is labeled 'DL SINR of victim UE (dB)' and ranges from -15 to 20. The y-axis is labeled 'CDF (%)' and ranges from 0 to 100. Two curves are plotted: a blue line for 'Without Interfering BS' and a red line for 'With Interfering BS'. Both curves are nearly identical, starting at 0% at -15 dB and reaching 100% at about 15 dB.
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -15          | 0                              | 0                           |
+| -10          | 0                              | 0                           |
+| -5           | 5                              | 5                           |
+| 0            | 35                             | 35                          |
+| 5            | 65                             | 65                          |
+| 10           | 90                             | 90                          |
+| 15           | 100                            | 100                         |
+| 20           | 100                            | 100                         |
+
+CDF plot of DL SINR of victim UE with and without interfering BS.
+
+(b) With 2GHz carrier frequency
+
+Figure A.1-2: For NR victim UE
+
+The average and 5%-tile DL throughput loss of the victim UE for the simulated cases are summarized in Table A.1-1 below. It can be seen that the average and 5%-tile DL throughput loss of the victim LTE and NR UE are equal (with four decimal point precision) in all simulated cases. This can be explained by the fact that the only difference between the victim LTE and NR UE is the DL bandwidth configuration which accounts to only  $[10\log_{10}(9.36\text{e}6/9\text{e}6)]=0.17\text{dB}$  difference in the UE receiver noise floor, which is minimal compared to the cumulative interference caused by the interfering NB-IoT BS to the DL SINR of victim LTE and NR UE. Therefore, the average and 5%-tile DL throughput loss of the victim NR UE are equal to those of the victim LTE UE (with four decimal point precision).
+
+**Table A.1-1: Average and 5%-tile DL throughput loss of the victim UE**
+
+| Victim UE                                          | LTE   | NR    |
+|----------------------------------------------------|-------|-------|
+| Average throughput loss (900MHz carrier frequency) | 0.30% | 0.30% |
+| 5%-tile throughput loss (900MHz carrier frequency) | 1.03% | 1.03% |
+| Average throughput loss (2GHz carrier frequency)   | 0.31% | 0.31% |
+| 5%-tile throughput loss (2GHz carrier frequency)   | 1.00% | 1.00% |
+
+## A.2 Downlink coexistence simulation results using NR channel model
+
+Further simulation results are obtained using the system level simulation methodology and assumptions in TR 36.802 but with the NR channel model in TR 38.901 instead of the legacy LTE/UMTS/GSM channel model. Only 2GHz carrier frequency is simulated here as the use of BS antenna array in 900MHz has limitation considering the required antenna array size with the longer wavelength. A (4x8) antenna array is assumed here for the NR BS, while legacy antenna is assumed for the UE as well as the LTE and NB-IoT BS.
+
+The CDFs of the coupling loss between victim LTE UE and BS and the DL SINR of victim LTE UE are shown in Figure A.2-1 below.
+
+![Two line graphs showing CDFs for LTE victim UE. The top graph shows CDF (%) vs Coupling loss between victim UE and BS (dB) for Serving BS (blue) and Interfering BS (red). The bottom graph shows CDF (%) vs DL SINR of victim UE (dB) for Without Interfering BS (blue) and With Interfering BS (red).](03498c9b76f980b32f2dfbb7c2e539d2_img.jpg)
+
+The figure consists of two line graphs. The top graph plots the Cumulative Distribution Function (CDF) in percentage on the y-axis (0 to 100) against the Coupling loss between victim UE and BS in dB on the x-axis (40 to 180). It features two curves: a blue curve for 'Serving BS' and a red curve for 'Interfering BS'. The blue curve rises steeply between 60 dB and 120 dB, reaching 100% CDF around 120 dB. The red curve rises more gradually, starting around 80 dB and reaching 100% CDF around 160 dB. The bottom graph plots the CDF in percentage on the y-axis (0 to 100) against the DL SINR of victim UE in dB on the x-axis (-15 to 30). It features two curves: a blue curve for 'Without Interfering BS' and a red curve for 'With Interfering BS'. Both curves are nearly identical, starting near 0% CDF at -10 dB and rising to 100% CDF around 25 dB.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 40                 | 0                  | 0                      |
+| 60                 | 5                  | 0                      |
+| 80                 | 30                 | 1                      |
+| 100                | 85                 | 5                      |
+| 120                | 100                | 20                     |
+| 140                | 100                | 60                     |
+| 160                | 100                | 95                     |
+| 180                | 100                | 100                    |
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -15          | 0                              | 0                           |
+| -10          | 0                              | 0                           |
+| -5           | 2                              | 3                           |
+| 0            | 20                             | 22                          |
+| 5            | 45                             | 48                          |
+| 10           | 70                             | 72                          |
+| 15           | 85                             | 86                          |
+| 20           | 95                             | 96                          |
+| 25           | 100                            | 100                         |
+| 30           | 100                            | 100                         |
+
+Two line graphs showing CDFs for LTE victim UE. The top graph shows CDF (%) vs Coupling loss between victim UE and BS (dB) for Serving BS (blue) and Interfering BS (red). The bottom graph shows CDF (%) vs DL SINR of victim UE (dB) for Without Interfering BS (blue) and With Interfering BS (red).
+
+**Figure A.2-1: For LTE victim UE**
+
+The CDFs of the coupling loss between victim NR UE and BS and the DL SINR of victim NR UE are shown in Figure A.2-2 below.
+
+![Two cumulative distribution function (CDF) plots for NR victim UE. The top plot shows CDF (%) vs. Coupling loss between victim UE and BS (dB) for Serving BS (blue) and Interfering BS (red). The bottom plot shows CDF (%) vs. DL SINR of victim UE (dB) for 'Without Interfering BS' (blue) and 'With Interfering BS' (red).](fe655d77258397f7242c2df72b965b56_img.jpg)
+
+The figure consists of two vertically stacked plots. The top plot shows the Cumulative Distribution Function (CDF) in percentage on the y-axis (0 to 100) against the Coupling loss between victim UE and BS in dB on the x-axis (20 to 180). It features two curves: a blue curve for 'Serving BS' and a red curve for 'Interfering BS'. The blue curve rises steeply between 40 dB and 100 dB, reaching 100% CDF at approximately 100 dB. The red curve rises more gradually, starting around 80 dB and reaching 100% CDF at approximately 160 dB. The bottom plot shows the CDF in percentage on the y-axis (0 to 100) against the DL SINR of victim UE in dB on the x-axis (-10 to 60). It features two curves: a blue curve for 'Without Interfering BS' and a red curve for 'With Interfering BS'. Both curves are nearly identical, starting near 0% CDF at -10 dB and reaching 100% CDF at approximately 50 dB.
+
+| Coupling loss (dB) | Serving BS CDF (%) | Interfering BS CDF (%) |
+|--------------------|--------------------|------------------------|
+| 40                 | 0                  | 0                      |
+| 60                 | 10                 | 0                      |
+| 80                 | 40                 | 1                      |
+| 100                | 100                | 5                      |
+| 120                | 100                | 20                     |
+| 140                | 100                | 50                     |
+| 160                | 100                | 100                    |
+
+| DL SINR (dB) | Without Interfering BS CDF (%) | With Interfering BS CDF (%) |
+|--------------|--------------------------------|-----------------------------|
+| -10          | 0                              | 0                           |
+| 0            | 2                              | 2                           |
+| 10           | 15                             | 18                          |
+| 20           | 50                             | 52                          |
+| 30           | 80                             | 82                          |
+| 40           | 95                             | 96                          |
+| 50           | 100                            | 100                         |
+
+Two cumulative distribution function (CDF) plots for NR victim UE. The top plot shows CDF (%) vs. Coupling loss between victim UE and BS (dB) for Serving BS (blue) and Interfering BS (red). The bottom plot shows CDF (%) vs. DL SINR of victim UE (dB) for 'Without Interfering BS' (blue) and 'With Interfering BS' (red).
+
+**Figure A.2-2: For NR victim UE**
+
+The average and 5%-tile DL throughput loss of the victim UE for the simulated cases are summarized in Table A.2-1 below. It can be seen that the average and 5%-tile DL throughput loss of the victim LTE and NR UE are higher than those using the legacy channel mode in Table A.1-1. This can be explained by the fact that no MCL is applied for the
+
+NR channel model, and thus the coupling loss between the victim UE and the interfering NB-IoT BS can be much smaller using the NR channel model (below 50dB as shown in Figures A.2-1 and A.2-2) compared to those using the legacy channel model in Figures A.1-1 and A.1-2 (where MCL is 70dB). This means that the impact from the interfering NB-IoT BS to the DL SINR of victim LTE and NR UE can be much larger, especially for the 5%-tile DL throughput where the near-far effect is more severe. The 5%-tile DL throughput loss of the victim UE will be greatly reduced if 70dB MCL is also applied to the NR channel model, as shown in Table A.2-1 below. On the other hand, it can be seen that the average DL throughput loss of the victim NR UE is similar to those of the victim LTE UE, while the 5%-tile DL throughput loss of the victim NR UE is lower than those of the victim LTE UE. This shows that the UE specific beamforming used in the NR BS can effectively reduce the impact from the interfering NB-IoT BS to the DL SINR of victim NR UE at the cell edge.
+
+**Table A.2-1: Average and 5%-tile DL throughput loss of the victim UE**
+
+| Victim UE                               | LTE    | NR    |
+|-----------------------------------------|--------|-------|
+| Average throughput loss (without MCL)   | 2.21%  | 2.13% |
+| 5%-tile throughput loss (without MCL)   | 10.50% | 7.80% |
+| Average throughput loss (with 70dB MCL) | 1.35%  | 1.48% |
+| 5%-tile throughput loss (with 70dB MCL) | 4.51%  | 1.90% |
+
+## A.3 Uplink coexistence simulation results using legacy LTE/UMTS/GSM channel model
+
+The system level simulation methodology and assumptions in TR 36.802 for coexistence study between NB-IoT standalone operation and legacy LTE/UMTS/GSM systems are used here. 10MHz channel bandwidth are used for both LTE and NR here, and 15kHz SCS is used for NR as it has a higher spectrum utilization than 30kHz SCS for 10MHz channel bandwidth. The number of active users in both victim and interfering systems is 3. Note that the NB-IoT UE UL power control parameter PLx-ile is bandwidth scaled targeting 15 dB uplink SNR at the serving BS, and the NB-IoT UE ACLR of 37dBc is bandwidth scaled by the factor  $10 \cdot \log_{10}(9\text{e}6 \text{ or } 9.36\text{e}6/3/180\text{e}3)$  to account for the asymmetrical transmission bandwidth. The LTE or NR BS ACS is 45dBc. Consequently, the overall ACIR is dominated by the NB-IoT UE ACLR.
+
+The CDFs of the LTE and NB-IoT UE transmit power and the UL SINR of victim LTE UE for 900MHz and 2GHz carrier frequency are shown in Figure A.3-1 below.
+
+![CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.](e714d8aca168c4854edebc4a4f2e9bd1_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UE transmit power in dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Victim UE' and a red line for 'Interfering UE'. The red curve starts at approximately (-35, 12) and reaches 100% at 0 dBm. The blue curve starts at approximately (-20, 12) and reaches 100% at 20 dBm.
+
+| UE transmit power (dBm) | Victim UE CDF (%) | Interfering UE CDF (%) |
+|-------------------------|-------------------|------------------------|
+| -40                     | -                 | 0                      |
+| -30                     | -                 | 25                     |
+| -20                     | 12                | 55                     |
+| -10                     | 30                | 85                     |
+| 0                       | 65                | 98                     |
+| 10                      | 90                | 100                    |
+| 20                      | 98                | 100                    |
+| 30                      | 100               | 100                    |
+
+CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.
+
+![CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.](771c18f874d31c59c3b8c4e247be16ca_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UL SINR of victim UE in dB. The x-axis represents 'UL SINR of victim UE (dB)' ranging from -15 to 15. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Without Interfering UE' and a red line for 'With Interfering UE'. Both curves are nearly identical, starting at 0% at -15 dB and reaching 100% at 10 dB.
+
+| UL SINR of victim UE (dB) | Without Interfering UE CDF (%) | With Interfering UE CDF (%) |
+|---------------------------|--------------------------------|-----------------------------|
+| -15                       | 0                              | 0                           |
+| -10                       | 0                              | 0                           |
+| -5                        | 1                              | 1                           |
+| 0                         | 40                             | 40                          |
+| 5                         | 90                             | 90                          |
+| 10                        | 100                            | 100                         |
+| 15                        | 100                            | 100                         |
+
+CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.
+
+(a) With 900MHz carrier frequency
+
+![CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.](16c69c0dacd3c57ae91acd114e5f5bd2_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UE transmit power in dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Victim UE' and a red line for 'Interfering UE'. The red curve starts at approximately 10% at -35 dBm and reaches 100% at 0 dBm. The blue curve starts at approximately 10% at -20 dBm and reaches 100% at 20 dBm. The red curve is shifted to the left of the blue curve, indicating that the interfering UE generally has lower transmit power than the victim UE.
+
+| UE transmit power (dBm) | Victim UE CDF (%) | Interfering UE CDF (%) |
+|-------------------------|-------------------|------------------------|
+| -40                     | 0                 | 0                      |
+| -30                     | 0                 | 25                     |
+| -20                     | 10                | 55                     |
+| -10                     | 30                | 85                     |
+| 0                       | 65                | 98                     |
+| 10                      | 90                | 100                    |
+| 20                      | 98                | 100                    |
+| 30                      | 100               | 100                    |
+
+CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.
+
+![CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.](673e9e5873f9a4b71bbe7bac2cf6b758_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UL SINR of the victim UE in dB. The x-axis represents 'UL SINR of victim UE (dB)' ranging from -15 to 15. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Without Interfering UE' and a red line for 'With Interfering UE'. Both curves start at 0% at -15 dB and reach 100% at 10 dB. The red curve is slightly to the left of the blue curve, indicating that the presence of an interfering UE slightly reduces the UL SINR of the victim UE.
+
+| UL SINR of victim UE (dB) | Without Interfering UE CDF (%) | With Interfering UE CDF (%) |
+|---------------------------|--------------------------------|-----------------------------|
+| -15                       | 0                              | 0                           |
+| -10                       | 0                              | 0                           |
+| -5                        | 1                              | 0                           |
+| 0                         | 40                             | 38                          |
+| 5                         | 90                             | 88                          |
+| 10                        | 100                            | 100                         |
+| 15                        | 100                            | 100                         |
+
+CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.
+
+(b) With 2GHz carrier frequency
+
+Figure A.3-1: For LTE victim UE
+
+The CDFs of the NR and NB-IoT UE transmit power and the UL SINR of victim NR UE for 900MHz and 2GHz carrier frequency are shown in Figure A.3-2 below.
+
+![CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.](1316cc5a3c69067473f110271212db3b_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UE transmit power in dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 30. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Victim UE' and a red line for 'Interfering UE'. The red curve starts at approximately (-35, 12) and reaches 100% at 0 dBm. The blue curve starts at approximately (-20, 12) and reaches 100% at 20 dBm. The Interfering UE generally has lower transmit power than the Victim UE.
+
+| UE transmit power (dBm) | Victim UE CDF (%) | Interfering UE CDF (%) |
+|-------------------------|-------------------|------------------------|
+| -40                     | 0                 | 0                      |
+| -30                     | 0                 | 25                     |
+| -20                     | 12                | 55                     |
+| -10                     | 30                | 85                     |
+| 0                       | 65                | 98                     |
+| 10                      | 90                | 100                    |
+| 20                      | 98                | 100                    |
+| 30                      | 100               | 100                    |
+
+CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.
+
+![CDF plot of UL SINR of victim UE (dB) for scenarios without and with interfering UE.](516d9f1866cc2e359a35fb1d8c046454_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UL SINR of victim UE in dB. The x-axis represents 'UL SINR of victim UE (dB)' ranging from -15 to 15. The y-axis represents 'CDF (%)' ranging from 0 to 100. Two curves are plotted: a blue line for 'Without Interfering UE' and a red line for 'With Interfering UE'. Both curves are nearly identical, starting at 0% at -15 dB and reaching 100% at 10 dB. The median SINR (50% CDF) is approximately 2 dB for both scenarios.
+
+| UL SINR of victim UE (dB) | Without Interfering UE CDF (%) | With Interfering UE CDF (%) |
+|---------------------------|--------------------------------|-----------------------------|
+| -15                       | 0                              | 0                           |
+| -10                       | 0                              | 0                           |
+| -5                        | 1                              | 1                           |
+| 0                         | 40                             | 40                          |
+| 5                         | 90                             | 90                          |
+| 10                        | 100                            | 100                         |
+| 15                        | 100                            | 100                         |
+
+CDF plot of UL SINR of victim UE (dB) for scenarios without and with interfering UE.
+
+(a) With 900MHz carrier frequency
+
+![CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.](1c2028183a35357e7238438a4af9cab7_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UE transmit power in dBm. The x-axis represents 'UE transmit power (dBm)' ranging from -40 to 30 in increments of 10. The y-axis represents 'CDF (%)' ranging from 0 to 100 in increments of 10. Two curves are plotted: a blue line for 'Victim UE' and a red line for 'Interfering UE'. The red curve starts at approximately 10% at -35 dBm and reaches 100% at 0 dBm. The blue curve starts at approximately 10% at -20 dBm and reaches 100% at 20 dBm. The red curve is shifted to the left of the blue curve, indicating that the interfering UE generally has lower transmit power than the victim UE.
+
+| UE transmit power (dBm) | Victim UE CDF (%) | Interfering UE CDF (%) |
+|-------------------------|-------------------|------------------------|
+| -40                     | 0                 | 0                      |
+| -30                     | 0                 | 25                     |
+| -20                     | 10                | 55                     |
+| -10                     | 30                | 85                     |
+| 0                       | 65                | 98                     |
+| 10                      | 90                | 100                    |
+| 20                      | 98                | 100                    |
+| 30                      | 100               | 100                    |
+
+CDF plot of UE transmit power (dBm) for Victim UE and Interfering UE.
+
+![CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg)
+
+This figure is a Cumulative Distribution Function (CDF) plot showing the distribution of UL SINR of the victim UE in dB. The x-axis represents 'UL SINR of victim UE (dB)' ranging from -15 to 15 in increments of 5. The y-axis represents 'CDF (%)' ranging from 0 to 100 in increments of 10. Two curves are plotted: a blue line for 'Without Interfering UE' and a red line for 'With Interfering UE'. Both curves are nearly identical, starting at 0% at -15 dB and reaching 100% at 10 dB. The curves are centered around 0 dB SINR.
+
+| UL SINR of victim UE (dB) | Without Interfering UE CDF (%) | With Interfering UE CDF (%) |
+|---------------------------|--------------------------------|-----------------------------|
+| -15                       | 0                              | 0                           |
+| -10                       | 0                              | 0                           |
+| -5                        | 1                              | 1                           |
+| 0                         | 40                             | 40                          |
+| 5                         | 90                             | 90                          |
+| 10                        | 100                            | 100                         |
+| 15                        | 100                            | 100                         |
+
+CDF plot of UL SINR of victim UE (dB) for 'Without Interfering UE' and 'With Interfering UE'.
+
+(b) With 2GHz carrier frequency
+
+Figure A.3-2: For NR victim UE
+
+The average and 5%-tile UL throughput loss of the victim UE for the simulated cases are summarized in Table A.3-1 below. It can be seen that the average and 5%-tile UL throughput loss of the victim LTE and NR UE are similar in all simulated cases. This can be explained by the fact that the only difference between the victim LTE and NR UE is the UL bandwidth configuration which accounts to only  $[10\log_{10}(9.36\text{e}6/9\text{e}6)]=0.17\text{dB}$  difference in the BS receiver noise floor, which is minimal compared to the cumulative interference caused by the interfering NB-IoT UE to the UL SINR of victim LTE and NR UE. Therefore, the average and 5%-tile DL throughput loss of the victim NR UE are similar to those of the victim LTE UE.
+
+**Table A.3-1: Average and 5%-tile UL throughput loss of the victim UE**
+
+| Victim UE                                          | LTE   | NR    |
+|----------------------------------------------------|-------|-------|
+| Average throughput loss (900MHz carrier frequency) | 0.73% | 0.76% |
+| 5%-tile throughput loss (900MHz carrier frequency) | 0.30% | 0.31% |
+| Average throughput loss (2GHz carrier frequency)   | 0.72% | 0.75% |
+| 5%-tile throughput loss (2GHz carrier frequency)   | 0.34% | 0.36% |
+
+## A.4 Uplink coexistence simulation results using NR channel model
+
+Further simulation results are obtained using the system level simulation methodology and assumptions in TR 36.802 but with the NR channel model in TR 38.901 instead of the legacy LTE/UMTS/GSM channel model. Note that 70dB MCL is also applied to the NR channel model as explained in annex A.2. Only 2GHz carrier frequency is simulated here as the use of BS antenna array in 900MHz has limitation considering the required antenna array size with the longer wavelength. A (4x8) antenna array is assumed here for the NR BS, while legacy antenna is assumed for the UE as well as the LTE and NB-IoT BS.
+
+The CDFs of the LTE and NB-IoT UE transmit power and the UL SINR of victim LTE UE are shown in Figure A.4-1 below.
+
+![Two cumulative distribution function (CDF) plots for LTE victim UE. The top plot shows CDF (%) vs UE transmit power (dBm) for Victim UE (blue) and Interfering UE (red). The bottom plot shows CDF (%) vs UL SINR of victim UE (dB) for 'Without Interfering UE' (blue) and 'With Interfering UE' (red).](94796d524bd7e0f31f89a379bae95996_img.jpg)
+
+The figure consists of two vertically stacked plots. The top plot shows the Cumulative Distribution Function (CDF) in percentage on the y-axis (ranging from 10 to 100) against UE transmit power in dBm on the x-axis (ranging from -40 to 30). It contains two curves: a blue curve for 'Victim UE' and a red curve for 'Interfering UE'. The red curve is shifted to the left of the blue curve, indicating that the interfering UE generally has lower transmit power. The bottom plot shows the CDF in percentage on the y-axis (ranging from 0 to 100) against UL SINR of victim UE in dB on the x-axis (ranging from -10 to 20). It contains two curves: a blue curve for 'Without Interfering UE' and a red curve for 'With Interfering UE'. The red curve is shifted to the left of the blue curve, indicating that the presence of an interfering UE results in a lower UL SINR for the victim UE.
+
+| UE transmit power (dBm) | CDF (%) - Victim UE | CDF (%) - Interfering UE |
+|-------------------------|---------------------|--------------------------|
+| -40                     | -                   | 12                       |
+| -30                     | -                   | 25                       |
+| -20                     | 25                  | 40                       |
+| -10                     | 40                  | 65                       |
+| 0                       | 65                  | 90                       |
+| 10                      | 90                  | 100                      |
+| 20                      | 100                 | 100                      |
+
+| UL SINR (dB) | CDF (%) - Without Interfering UE | CDF (%) - With Interfering UE |
+|--------------|----------------------------------|-------------------------------|
+| -10          | 0                                | 0                             |
+| -5           | 0                                | 0                             |
+| 0            | 5                                | 5                             |
+| 5            | 15                               | 20                            |
+| 10           | 50                               | 60                            |
+| 15           | 100                              | 100                           |
+
+Two cumulative distribution function (CDF) plots for LTE victim UE. The top plot shows CDF (%) vs UE transmit power (dBm) for Victim UE (blue) and Interfering UE (red). The bottom plot shows CDF (%) vs UL SINR of victim UE (dB) for 'Without Interfering UE' (blue) and 'With Interfering UE' (red).
+
+**Figure A.4-1: For LTE victim UE**
+
+The CDFs of the NR and NB-IoT UE transmit power and the UL SINR of victim NR UE are shown in Figure A.4-2 below.
+
+![Two cumulative distribution function (CDF) plots for NR victim UE. The top plot shows CDF (%) vs UE transmit power (dBm) for Victim UE (blue) and Interfering UE (red). The bottom plot shows CDF (%) vs UL SINR of victim UE (dB) for 'Without Interfering UE' (blue) and 'With Interfering UE' (red).](68ec8ddd77b91c6e59d90ca84ad64f11_img.jpg)
+
+The figure consists of two vertically stacked plots. The top plot shows the Cumulative Distribution Function (CDF) in percentage on the y-axis (ranging from 10 to 100) against UE transmit power in dBm on the x-axis (ranging from -40 to 30). It contains two curves: a blue curve for 'Victim UE' and a red curve for 'Interfering UE'. The red curve is shifted to the left of the blue curve, indicating that the interfering UE typically transmits at lower power levels than the victim UE. The bottom plot shows the CDF in percentage on the y-axis (ranging from 0 to 100) against the UL SINR of the victim UE in dB on the x-axis (ranging from -10 to 15). It contains two curves: a blue curve for 'Without Interfering UE' and a red curve for 'With Interfering UE'. The red curve is shifted to the right of the blue curve, indicating that the presence of an interfering UE results in a higher UL SINR for the victim UE, which is counter-intuitive but may be due to specific simulation parameters or interference characteristics.
+
+| UE transmit power (dBm) | CDF (%) Victim UE | CDF (%) Interfering UE |
+|-------------------------|-------------------|------------------------|
+| -40                     | -                 | 12                     |
+| -30                     | -                 | 25                     |
+| -20                     | 25                | 40                     |
+| -10                     | 40                | 65                     |
+| 0                       | 65                | 95                     |
+| 10                      | 95                | 100                    |
+| 20                      | 100               | 100                    |
+
+| UL SINR (dB) | CDF (%) Without Interfering UE | CDF (%) With Interfering UE |
+|--------------|--------------------------------|-----------------------------|
+| -10          | 0                              | 0                           |
+| -5           | 0                              | 0                           |
+| 0            | 5                              | 5                           |
+| 5            | 15                             | 20                          |
+| 10           | 50                             | 60                          |
+| 15           | 100                            | 100                         |
+
+Two cumulative distribution function (CDF) plots for NR victim UE. The top plot shows CDF (%) vs UE transmit power (dBm) for Victim UE (blue) and Interfering UE (red). The bottom plot shows CDF (%) vs UL SINR of victim UE (dB) for 'Without Interfering UE' (blue) and 'With Interfering UE' (red).
+
+**Figure A.4-2: For NR victim UE**
+
+The average and 5%-tile UL throughput loss of the victim UE for the simulated cases are summarized in Table A.4-1 below. It can be seen that the average and 5%-tile UL throughput loss of the victim NR UE are higher than those of the victim LTE UE. This can be explained by the fact that the NB-IoT UE ACLR of 37dBc is bandwidth scaled by a larger
+
+factor the factor  $10 \cdot \log_{10} (9.36e6/3/180e3)$  instead of  $10 \cdot \log_{10} (9e6/3/180e3)$  to account for the higher spectrum utilization of the NR BS compared to that of the LTE BS. However, the average and 5%-tile UL throughput loss of the victim NR UE are still lower than the 5% threshold for acceptable throughput degradation.
+
+**Table A.4-1: Average and 5%-tile DL throughput loss of the victim UE**
+
+| Victim UE                               | LTE   | NR    |
+|-----------------------------------------|-------|-------|
+| Average throughput loss (with 70dB MCL) | 4.59% | 4.68% |
+| 5%-tile throughput loss (with 70dB MCL) | 2.58% | 2.69% |
+
+# Annex B (informative): Change history
+
+| Change history |                   |            |    |     |     |                                                                                                                                                                       |             |
+|----------------|-------------------|------------|----|-----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting           | TDoc       | CR | Rev | Cat | Subject/Comment                                                                                                                                                       | New version |
+| 2019-04        | RAN4#90<br>BIS    | R4-1905109 | -  | -   | -   | First version of the draft TR                                                                                                                                         | 0.0.1       |
+| 2019-08        | RAN4#92           | R4-1908370 |    |     |     | Second version of the draft TR<br>Implemented following TPs endorsed during RAN4#91 meeting:<br>R4-1906926, R4-1907810, R4-1907811, R4-1907812                        | 0.1.0       |
+| 2019-10        | RAN4#92<br>-BIS   | R4-1912304 |    |     |     | Third version of the draft TR<br>Implemented following TPs endorsed during RAN4#92 meeting:<br>R4-1908314, R4-1908315, R4-1910486, R4-1910487, R4-1910488, R4-1910489 | 0.2.0       |
+| 2019-11        | RAN4#93           | R4-1915310 |    |     |     | Fourth version of the draft TR<br>Implemented following TPs endorsed during RAN4#92-bis meeting:<br>R4-1912996, R4-1912997                                            | 0.3.0       |
+| 2020-02        | RAN4#94<br>-e     | R4-2000699 |    |     |     | Fifth version of the draft TR<br>Implemented following TPs endorsed during RAN4#93 meeting:<br>R4-1916096, R4-1916097                                                 | 0.4.0       |
+| 2020-04        | RAN4#94<br>-e-Bis | R4-2003592 |    |     |     | Sixth and final version of the draft TR<br>Implemented following TPs endorsed during RAN4#94-e meeting:<br>R4-2000670, R4-2000875, R4-2002915                         | 0.5.0       |
+| 2020-06        | RAN#88e           | RP-200754  |    |     |     | Final submission to RAN                                                                                                                                               | 1.0.0       |
+
+| Change history |         |      |    |     |     |                                                        |             |
+|----------------|---------|------|----|-----|-----|--------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                        | New version |
+| 2020-06        | RAN#88  |      |    |     |     | Approved by plenary – Rel-16 spec under change control | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37825/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37825/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ddffe8a160a347f5b56aeeb3fc078fab866a97ac
--- /dev/null
+++ b/marked/Rel-16/37_series/37825/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d5c2eea7f0a8a0b5e5d2794636efaf8891c0e5eb6c036463ebb7d527a0bce368
+size 9839
diff --git a/marked/Rel-16/37_series/37825/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37825/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5057b4374facb16cc19b8776f6f3742bf8a785ce
--- /dev/null
+++ b/marked/Rel-16/37_series/37825/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02b10e9afad745adce2fc9111a3c32f59e352dfe1b6b114c76e2bead3db6105b
+size 5825
diff --git a/marked/Rel-16/37_series/37825/raw.md b/marked/Rel-16/37_series/37825/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..99492d67e46423c2be733ac2ed1e7d6cb691ef58
--- /dev/null
+++ b/marked/Rel-16/37_series/37825/raw.md
@@ -0,0 +1,807 @@
+
+
+# 3GPP TR 37.825 V16.0.0 (2019-12)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Networks; High power User Equipment (UE) (power class 2) for E-UTRA (Evolved Universal Terrestrial Radio Access) - NR Dual Connectivity (EN-DC) (1 LTE TDD band + 1 NR TDD band) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                                  |    |
+|------------------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                                   | 5  |
+| Scope 7                                                                                                          |    |
+| References .....                                                                                                 | 7  |
+| Definitions, symbols and abbreviations .....                                                                     | 7  |
+| Definitions .....                                                                                                | 7  |
+| Symbols 7                                                                                                        |    |
+| Abbreviations .....                                                                                              | 8  |
+| 4 Background .....                                                                                               | 8  |
+| 4.1 Justification .....                                                                                          | 8  |
+| 4.2 Objective .....                                                                                              | 9  |
+| 5 High power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band): General Part.....                    | 10 |
+| 5.1 Output power and TX power tolerance.....                                                                     | 10 |
+| 5.2 Maximum output power reduction for PC2 EN-DC .....                                                           | 10 |
+| 5.2.1 Intra-band EN-DC .....                                                                                     | 10 |
+| 5.2.1.1 Intra-band contiguous EN-DC .....                                                                        | 10 |
+| 5.2.1.1.1 General .....                                                                                          | 10 |
+| 5.2.1.2 Intra-band non-contiguous EN-DC.....                                                                     | 11 |
+| 5.2.1.2.1 General .....                                                                                          | 11 |
+| 5.2.1.2.2 MPR for EN-DC.....                                                                                     | 12 |
+| 5.2.2 Inter-band EN-DC .....                                                                                     | 13 |
+| 5.3 Additional maximum output power reduction for PC2 EN-DC .....                                                | 13 |
+| 5.3.1 Intra-band EN-DC .....                                                                                     | 13 |
+| 5.3.2 Inter-band EN-DC .....                                                                                     | 13 |
+| 5.4 Configured output power for PC2 EN-DC.....                                                                   | 13 |
+| 5.5 Adjacent channel leakage ratio .....                                                                         | 13 |
+| 5.5.1 Intra-band EN-DC .....                                                                                     | 13 |
+| 5.5.2 Inter-band EN-DC .....                                                                                     | 14 |
+| 5.6 SAR .....                                                                                                    | 14 |
+| 5.6.1 Intra-band EN-DC .....                                                                                     | 14 |
+| 5.6.2 Inter-band EN-DC .....                                                                                     | 14 |
+| 5.7 n41-B40 co-existence requirement.....                                                                        | 15 |
+| 6 High power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band): Specific Band Combination Part ..... | 15 |
+| 6.1 Inter-band PC2 EN-DC .....                                                                                   | 15 |
+| 6.1.1 PC2 EN-DC_41A-79A.....                                                                                     | 15 |
+| 6.1.1.1 Operating bands for PC2 EN_DC.....                                                                       | 15 |
+| 6.1.1.2 Channel bandwidths per operating band for PC2 EN_DC .....                                                | 15 |
+| 6.1.1.3 Co-existence studies for PC2 EN_DC .....                                                                 | 15 |
+| 6.1.1.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN_DC .....                                                 | 15 |
+| 6.1.1.5 MSD for PC2 EN-DC .....                                                                                  | 15 |
+| 6.1.2 PC2 EN-DC_39A-79A.....                                                                                     | 16 |
+| 6.1.2.1 Operating bands for PC2 EN_DC.....                                                                       | 16 |
+| 6.1.2.2 Channel bandwidths per operating band for PC2 EN_DC .....                                                | 16 |
+| 6.1.2.3 Co-existence studies for PC2 EN_DC .....                                                                 | 16 |
+| 6.1.2.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN_DC .....                                                 | 16 |
+| 6.1.2.5 MSD for PC2 EN-DC .....                                                                                  | 16 |
+| 6.1.3 PC2 EN-DC_39A-41A.....                                                                                     | 16 |
+| 6.1.3.1 Operating bands for PC2 EN_DC.....                                                                       | 16 |
+| 6.1.3.2 Channel bandwidths per operating band for PC2 EN_DC .....                                                | 17 |
+| 6.1.3.3 Co-existence studies for PC2 EN_DC .....                                                                 | 17 |
+| 6.1.3.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN_DC .....                                                 | 17 |
+| 6.1.3.5 MSD for PC2 EN-DC .....                                                                                  | 17 |
+| 6.2 Intra-band PC2 EN-DC .....                                                                                   | 17 |
+
+|          |                                                                  |    |
+|----------|------------------------------------------------------------------|----|
+| 6.2.1    | PC2 EN-DC_(n)41AA.....                                           | 17 |
+| 6.2.1.1  | Operating bands for PC2 EN_DC.....                               | 17 |
+| 6.2.1.2  | Channel bandwidths per operating band for PC2 EN_DC .....        | 17 |
+| 6.2.1.3  | Co-existence studies for PC2 EN_DC .....                         | 17 |
+| 6.2.1.4  | $\Delta$ TIB and $\Delta$ RIB values for PC2 EN_DC .....         | 18 |
+| 6.2.1.5  | MSD for PC2 EN-DC .....                                          | 18 |
+| 6.2.1.6  | SEM/A-SEM for PC2 EN-DC .....                                    | 18 |
+| 6.2.1.7  | MPR/A-MPR for PC2 EN-DC .....                                    | 18 |
+| 6.2.2    | PC2 EN-DC_ 41A-n41A .....                                        | 18 |
+| 6.2.2.1  | Operating bands for PC2 EN_DC.....                               | 18 |
+| 6.2.2.2  | Channel bandwidths per operating band for PC2 EN_DC .....        | 18 |
+| 6.2.2.3  | Co-existence studies for PC2 EN_DC .....                         | 18 |
+| 6.2.2.4  | $\Delta$ TIB and $\Delta$ RIB values for PC2 EN_DC .....         | 18 |
+| 6.2.2.5  | MSD for PC2 EN-DC .....                                          | 18 |
+| 6.2.2.6  | SEM/A-SEM for PC2 EN-DC .....                                    | 19 |
+| 6.2.2.7  | MPR/A-MPR for PC2 EN-DC .....                                    | 19 |
+| 7        | Specification impacts .....                                      | 19 |
+| 7.1      | Impacts on RAN4 specifications.....                              | 19 |
+| 7.1.1    | Intraband EN-DC.....                                             | 19 |
+| 7.1.2    | Interband EN-DC.....                                             | 19 |
+| 7.2      | Impacts on specifications for the other WGs (if applicable)..... | 20 |
+| Annex A: | Change history .....                                             | 20 |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+## --- Scope
+
+The present document is a technical report for high power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band). The purpose is to introduce high power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band).
+
+This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
+
+# --- References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [3] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception; Part 3: Range 1 and Range 2 Interworking operation with other radios".
+- [4] 3GPP TS 36.101: "E-UTRAN; User Equipment (UE) radio transmission and reception".
+- [5] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
+
+# --- Definitions, symbols and abbreviations
+
+## Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+### Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                   |                                                                                                             |
+|-------------------|-------------------------------------------------------------------------------------------------------------|
+| $\Delta R_{IB,c}$ | Allowed reference sensitivity relaxation due to support for inter-band CA operation, for serving cell $c$ . |
+| $\Delta T_{IB,c}$ | Allowed maximum configured output power relaxation due to support for inter-band CA                         |
+| $F_{DL\_low}$     | The lowest frequency of the downlink operating band                                                         |
+| $F_{DL\_high}$    | The highest frequency of the downlink operating band                                                        |
+| $F_{UL\_low}$     | The lowest frequency of the uplink operating band                                                           |
+| $F_{UL\_high}$    | The highest frequency of the uplink operating band                                                          |
+
+## Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|         |                                                                                                       |
+|---------|-------------------------------------------------------------------------------------------------------|
+| A-MPR   | Additional Maximum Power Reduction                                                                    |
+| DC      | Dual Connectivity                                                                                     |
+| EN-DC   | E-UTRA/NR DC                                                                                          |
+| FR      | Frequency Range                                                                                       |
+| MPR     | Allowed maximum power reduction                                                                       |
+| MSD     | Maximum Sensitivity Degradation                                                                       |
+| NR      | New Radio                                                                                             |
+| NS      | Network Signalling                                                                                    |
+| NSA     | Non-Standalone, a mode of operation where operation of an other radio is assisted with an other radio |
+| REFSENS | Reference Sensitivity                                                                                 |
+| RF      | Radio Frequency                                                                                       |
+| Rx      | Receiver                                                                                              |
+| TDM     | Time Division Multiplex                                                                               |
+| Tx      | Transmitter                                                                                           |
+| UE      | User Equipment                                                                                        |
+
+# --- 4 Background
+
+## 4.1 Justification
+
+In order to reduce the big imbalance between 5G NR uplink and downlink coverage, RAN4 has completed PC2 HPUE feature to improve the uplink coverage for 5G SA deployments on NR bands n41, n77, n78 and n79 in Rel-15 NR WI, including PC2 UL MIMO (2Tx 23+23dBm) and PC2 1Tx (26dBm) UE. The following NR bands were approved to support PC2 HPUE for 5G NR SA in Rel-15 :
+
+- Band n41 (2496 – 2690 MHz):
+
+UL-MIMO (2Tx 23+23dBm) and 1Tx (26dBm) are supported for NR Band n41
+
+- Band n77 (3.3 - 4.2 GHz):
+
+UL-MIMO (2Tx 23+23dBm) and 1Tx (26dBm) are supported for NR Band n77
+
+- Band n78 (3.3 - 3.8 GHz):
+
+UL-MIMO (2Tx 23+23dBm) and 1Tx (26dBm) are supported for NR Band n78
+
+- Band n79 (4.4 - 5 GHz):
+
+UL-MIMO (2Tx 23+23dBm) and 1Tx (26dBm) are supported for NR Band n79
+
+For 5G NR NSA deployment, the imbalance between UL and DL coverage still exists, and the uplink coverage for EN-DC is also need to be improved. Considering the technical status of the industry chain, the Power Class 2 (+26dBm) EN-DC UE should be the most practical and suitable choice to improve the UL coverage for 5G NR NSA deployment.
+
+It is proposed to specify Power Class 2 UE for EN-DC (1 LTE band + 1 NR band) supporting +26 dBm. PC2 EN-DC for TDD-TDD band combinations are proposed in this Work Item. This Work Item is to develop a new feature to enable Power Class 2 EN-DC UE with 26 dBm maximum output power.
+
+## 4.2 Objective
+
+The objective of the work item is to specify the RF requirements for Power Class 2 EN-DC (1 LTE band (PC3) + 1 NR band (PC3) with 1Tx).
+
+- Specify the band combination specific RF requirements for all listed PC2 EN-DC configurations consisting of 2 different bands DL with 2 different bands UL (1 LTE band and 1 NR band) including at least
+  - Applicable frequencies if necessary
+  - Applicable bandwidths and bandwidth sets if necessary
+  - UE requirements, including UE maximum output power, Tx power tolerance, MPR, A-MPR, IBE and ACLR for Power Class 2 EN-DC, taking into account the potential coexistence with Band 40 in China
+- Analyse combinations that have self-desensitization due to following reasons:
+  - TX Harmonic and/or intermodulation overlap of receive band
+  - TX signal overlap of receiver harmonic frequency
+  - TX frequency being in close proximity of one of the receive bands
+  - Any other identified reasons
+- For the combination where self-desensitization exists:
+  - $\Delta T_{IB,c}$  and  $\Delta R_{IB,c}$
+  - Reference sensitivity exceptions including MSD test cases
+- UE Tx duty cycle requirements sufficient to prevent exceeding local regulatory limits such as SAR
+- Regulatory issues related to the use of PC2 EN-DC capable devices when roaming and/or p-max absence shall be addressed.
+- Simultaneous RxTx UE capability for PC2 EN-DC band combinations shall be decided
+- Release independent issue is to be considered for PC2 EN-DC
+- RAN4 needs to discuss whether existing RAN2 signalling can be reused to solve the issues in this WI. If there is RAN2 signalling impact then RAN4 will send LS to RAN2 to inform the solution. No RAN2 TUs are requested for this WI.
+
+This WI is aimed to specify the category of PC2 EN-DC band combinations consisting of 2 different bands DL with 2 different bands UL (1 LTE band and 1 NR band). An overview table of these PC2 EN-DC configurations is provided here:
+
+| EN-DC configuration | Uplink EN-DC configuration |
+|---------------------|----------------------------|
+| DC_39A-n41A         | DC_39A-n41A                |
+| DC_(n)41AA          | DC_(n)41AA                 |
+| DC_41A-n41A         | DC_41A-n41A                |
+| DC_39A-n79A         | DC_39A-n79A                |
+| DC_41A-n79A         | DC_41A-n79A                |
+
+# 5 High power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band): General Part
+
+## 5.1 Output power and TX power tolerance
+
+For EN-DC with 1 LTE TDD band and 1 NR TDD band, UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1ms). The maximum output power is specified in Table 5.1-1.
+
+**Table 5.1-1 Maximum output power for EN-DC**
+
+| DC configuration | Power class 2 (dBm) | Tolerance (dB)     | Power class 3 (dBm) | Tolerance (dB)     |
+|------------------|---------------------|--------------------|---------------------|--------------------|
+| DC_39A-n41A      | 26                  | +2/-3 <sup>1</sup> | 23                  | +2/-3 <sup>1</sup> |
+| DC_(n)41AA       | 26                  | +2/-2 <sup>1</sup> | 23                  | +2/-2 <sup>1</sup> |
+| DC_41A-n41A      | 26                  | +2/-2 <sup>1</sup> | 23                  | +2/-2 <sup>1</sup> |
+| DC_39A-n79A      | 26                  | +2/-3              | 23                  | +2/-3              |
+| DC_41A-n79A      | 26                  | +2/-3 <sup>1</sup> | 23                  | +2/-3 <sup>1</sup> |
+
+NOTE 1: refers to the transmission bandwidths confined within  $F_{UL\_low}$  and  $F_{UL\_low} + 4$  MHz or  $F_{UL\_high} - 4$  MHz and  $F_{UL\_high}$ , the maximum output power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB
+
+NOTE 2:  $P_{PowerClass\_EN-DC}$  is the maximum UE power specified without taking into account the tolerance
+
+NOTE 3: For inter-band EN-DC the maximum power requirement should apply to the total transmitted power over all component carriers (per UE).
+
+## 5.2 Maximum output power reduction for PC2 EN-DC
+
+### 5.2.1 Intra-band EN-DC
+
+The UE maximum output power reduction (MPR) specified in this clause is applicable for UEs configured with EN-DC when NS\_01 is indicated in the MCG and the SCG. The MPR applies subject to indication in the field *modifiedMPRbehavior* for the SCG [2].
+
+#### 5.2.1.1 Intra-band contiguous EN-DC
+
+##### 5.2.1.1.1 General
+
+When the UE is configured for intra-band contiguous EN-DC, the UE determines the allowed maximum output power reduction as specified in this clause.
+
+For UE supporting dynamic power sharing the following:
+
+- for the MCG,  $MPR'_c$  in accordance with [4]
+- for the SCG,
+
+$$MPR'_c = MPR_{NR} = \text{MAX}(MPR_{single,NR}, MPR_{ENDC})$$
+
+- for the total configured transmission power,
+
+$$MPR_{tot} = P_{PowerClass,EN-DC} - \min(P_{PowerClass,EN-DC}, 10 * \log_{10}(10^{(P_{PowerClass,E-UTRA} - MPR_{E-UTRA})/10}) + 10^{(P_{PowerClass,NR} - MPR_{NR})/10}))$$
+
+where
+
+$$MPR_{E-UTRA} = \text{MAX}(MPR_{single,E-UTRA}, MPR_{ENDC})$$
+
+with
+
+- $MPR_{\text{single, E-UTRA}}$  is the MPR defined for the E-UTRA transmission in [4]
+- $MPR_{\text{single, NR}}$  is the MPR defined for the NR transmission in [2]
+
+For UEs not supporting dynamic power sharing the following
+
+- for the MCG,
+
+$$MPR_c = \text{MAX}(MPR_{\text{single, E-UTRA}}, MPR_{\text{ENDC}})$$
+
+- for the SCG,
+
+$$MPR'_c = \text{MAX}(MPR_{\text{single, NR}}, MPR_{\text{ENDC}})$$
+
+where
+
+- $MPR_{\text{single, NR}}$  is the MPR defined for the NR transmission in [2]
+- $MPR_{\text{single, E-UTRA}}$  is the MPR defined for the E-UTRA transmission in [4]
+
+$MPR_{\text{ENDC}}$  is defined in Subclause 5.2.1.1.2
+
+##### 5.2.1.1.2 MPR for EN-DC
+
+MPR in this sub-clause is applicable for power class 3 and power class 2. The allowed maximum output power reduction applied to transmission on the MCG and the SCG is defined as follows:
+
+$$MPR_{\text{ENDC}} = M_A$$
+
+Where  $M_A$  is defined as follows
+
+$$\begin{aligned} M_A = & [15] \quad ; \quad 0 \leq B < 0.5 \\ & [10] \quad ; \quad 0.5 \leq B < 1.0 \\ & [8] \quad ; \quad 1.0 \leq B < 2.0 \\ & [5] \quad ; \quad 2.0 < B \end{aligned}$$
+
+Where:
+
+For UEs supporting dynamic power sharing,
+
+$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * SCS_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * SCS_{\text{NR}}) / 1,000,000$$
+
+For UEs not supporting dynamic power sharing,
+
+For E-UTRA
+
+$$B = (L_{\text{CRB\_alloc, E-UTRA}} * 12 * SCS_{\text{E-UTRA}} + 12 * SCS_{\text{NR}}) / 1,000,000$$
+
+For NR
+
+$$B = (12 * SCS_{\text{E-UTRA}} + L_{\text{CRB\_alloc, NR}} * 12 * SCS_{\text{NR}}) / 1,000,000$$
+
+and  $M_A$  is reduced by 1 dB for  $B < 2$ .
+
+#### 5.2.1.2 Intra-band non-contiguous EN-DC
+
+##### 5.2.1.2.1 General
+
+When the UE is configured for intra-band non-contiguous EN-DC, the UE determines the allowed maximum output power reduction as specified in this clause.
+
+For UE supporting dynamic power sharing the following:
+
+- for the MCG,  $MPR_c$  in accordance with [4]
+
+- for the SCG,
+
+$$\text{MPR}'_c = \text{MPR}_{\text{NR}} = \text{MAX}(\text{MPR}_{\text{single,NR}}, \text{MPR}_{\text{ENDC}})$$
+
+- for the total configured transmission power,
+
+$$\text{MPR}_{\text{tot}} = P_{\text{PowerClass,EN-DC}} - \min(P_{\text{PowerClass,EN-DC}}, 10 * \log_{10}(10^{((P_{\text{PowerClass,E-UTRA}} - \text{MPR}_{\text{E-UTRA}})/10)} + 10^{((P_{\text{PowerClass,NR}} - \text{MPR}_{\text{NR}})/10)}))$$
+
+where
+
+$$\text{MPR}_{\text{E-UTRA}} = \text{MAX}(\text{MPR}_{\text{single,E-UTRA}}, \text{MPR}_{\text{ENDC}})$$
+
+with
+
+- $\text{MPR}_{\text{single,E-UTRA}}$  is the MPR defined for the E-UTRA transmission in [4]
+- $\text{MPR}_{\text{single,NR}}$  is the MPR defined for the NR transmission in [2]
+
+For UEs not supporting dynamic power sharing the following
+
+- for the MCG,
+
+$$\text{MPR}_c = \text{MAX}(\text{MPR}_{\text{single,E-UTRA}}, \text{MPR}_{\text{ENDC}})$$
+
+- for the SCG,
+
+$$\text{MPR}'_c = \text{MAX}(\text{MPR}_{\text{single,NR}}, \text{MPR}_{\text{ENDC}})$$
+
+where
+
+- $\text{MPR}_{\text{single,NR}}$  is the MPR defined for the NR transmission in [2]
+- $\text{MPR}_{\text{single,E-UTRA}}$  is the MPR defined for the E-UTRA transmission in [4]
+
+$\text{MPR}_{\text{ENDC}}$  is defined in Subclause 5.2.1.2.2
+
+##### 5.2.1.2.2 MPR for EN-DC
+
+MPR in this sub-clause is applicable for power class 3 and power class 2. The allowed maximum output power reduction for IM3 related emissions applied to transmission on the MCG and the SCG is defined as follows:
+
+$$\text{MPR}_{\text{ENDC}} = M_A$$
+
+Where  $M_A$  is defined as follows
+
+$$\begin{aligned} M_A = \quad & [18] \quad ; \quad 0 \leq B < 1.0 \\ & [17] \quad ; \quad 1.0 \leq B < 2.0 \\ & [16] \quad ; \quad 2.0 \leq B < 5.0 \\ & [15] \quad ; \quad 5.0 < B \end{aligned}$$
+
+Where:
+
+For UEs supporting dynamic power sharing,
+
+$$B = (L_{\text{CRB\_alloc,E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + L_{\text{CRB\_alloc,NR}} * 12 * \text{SCS}_{\text{NR}}) / 1,000.000$$
+
+For UEs not supporting dynamic power sharing,
+
+For E-UTRA
+
+$$B = (L_{\text{CRB\_alloc,E-UTRA}} * 12 * \text{SCS}_{\text{E-UTRA}} + 12 * \text{SCS}_{\text{NR}}) / 1,000.000$$
+
+For NR
+
+$$B = (12 * SCS_{E-UTRA} + L_{CRB\_alloc,NR} * 12 * SCS_{NR})/1,000,000$$
+
+and  $M_A$  is reduced by 1 dB for  $B < 2$ .
+
+### 5.2.2 Inter-band EN-DC
+
+For inter-band EN-DC supporting PC2, UE maximum output power reduction for PC3 as specified in TS 36.101[4] and TS 38.101-1[2] apply for E-UTRA and NR respectively.
+
+## 5.3 Additional maximum output power reduction for PC2 EN-DC
+
+### 5.3.1 Intra-band EN-DC
+
+The details of A-MPR for PC2 DC\_(n)41AA and DC\_41A-n41A configuration with NS\_04 signal have been specified in 38.101-3[3] 6.2B.3.1 and 6.2B.3.2 respectively.
+
+### 5.3.2 Inter-band EN-DC
+
+For inter-band EN-DC supporting PC2, UE A-MPR for PC3 as specified in TS 36.101[4] and TS 38.101-1[2] apply for E-UTRA and NR respectively.
+
+## 5.4 Configured output power for PC2 EN-DC
+
+The configured output power for intra-band and inter-band EN-DC as specified in TS 38.101-3[3] apply for PC2 UE.
+
+## 5.5 Adjacent channel leakage ratio
+
+### 5.5.1 Intra-band EN-DC
+
+For EN-DC operation with an E-UTRA sub-block immediately adjacent to an NR sub-block, the ACLR is defined as the ratio of the filtered mean power centred on the aggregated sub-block bandwidth ENBW to the filtered mean power centred on an adjacent bandwidth of the same size ENBW at nominal channel spacing. The UE shall meet the ACLR minimum requirement EN-DC<sub>ACLR</sub> specified in Table 5.5.1-1 with ENBW the sum of the sub-block bandwidths.
+
+The assigned channel power and adjacent channel power are measured with rectangular filters with measurement bandwidths specified in 6.5B.2.1.3-1 in [3].
+
+**Table 5.5.1-1 ACLR for intra-band EN-DC (contiguous sub-blocks) power class 2**
+
+| Parameter                                                                                         | Unit | Value              |
+|---------------------------------------------------------------------------------------------------|------|--------------------|
+| EN-DC <sub>ACLR</sub>                                                                             | dBc  | 31                 |
+| Measurement bandwidth of EN-DC channel                                                            |      | 1.00*ENBW          |
+| Measurement bandwidth of adjacent channel                                                         |      | 0.95*ENBW          |
+| Frequency offset of adjacent channel                                                              |      | ENBW<br>/<br>-ENBW |
+| NOTE 1: ENBW is the aggregated bandwidth in MHz as defined in 38.101-3 sub-clause 5.3B.           |      |                    |
+| NOTE 2: The frequency offset is that in between the centre frequencies of the measurement filters |      |                    |
+
+For intra-band non-contiguous EN-DC, the EN-DC Adjacent Channel Leakage power Ratio (EN-DC<sub>ACLR</sub>) is the ratio of the sum of the filtered mean powers centered on the assigned E-UTRA and NR sub-block frequencies to the filtered mean power centered on an adjacent channel frequency at nominal channel spacing. In case the sub-block gap bandwidth  $W_{gap}$  is smaller than a E-UTRA or NR sub-block bandwidth, no EN-DC<sub>ACLR</sub> requirement is set for the
+
+corresponding sub-block for the gap. The assigned EN-DC sub-block power and adjacent channel power are measured with rectangular filters with measurement bandwidths specified in [4] for the E-UTRA sub-block, and [2], [3] for the NR sub-block. If the measured adjacent channel power is greater than  $-50\text{dBm}$  then the EN-DC ACLR shall be higher than the value specified in for E-UTRA ACLR and NR ACLR
+
+### 5.5.2 Inter-band EN-DC
+
+The ACLR requirements specified in sub-clause 6.6.2.3 of TS 36.101[4] and sub-clause 6.5.2.4 of TS 38.101-1[2] apply for each component carrier of inter-band EN-DC.
+
+## 5.6 SAR
+
+### 5.6.1 Intra-band EN-DC
+
+If UE supports a different power class than the default UE power class for intra-band EN-DC band combination and the supported power class enables the higher maximum output power than that of the default power class:
+
+- if the LTE UL/DL configuration is 0 or 6; or
+- if the LTE UL/DL configuration is 1 and special subframe configuration is 0 or 5; or
+- if the IE *p-maxUE-FR1* as defined in TS 38.331 [5] is provided and set to the maximum output power of the default power class or lower;
+  - apply all requirements for the default power class and set the configured transmitted power as specified in sub-clause 5.4;
+- else
+- apply all requirements for the supported power class and set the configured transmitted power class as specified in sub-clause 5.4;
+
+### 5.6.2 Inter-band EN-DC
+
+If UE supports a different power class than the default UE power class for EN-DC band combination, and the supported power class enables higher maximum output power than that of the default power class:
+
+- if the field of UE capability *maxUplinkDutyCycle-EN-DC* is absent and the percentage of NR uplink symbols transmitted in a certain evaluation period is larger than 30% (The exact evaluation period is no less than one radio frame); or
+- if the field of UE capability *maxUplinkDutyCycle-EN-DC* is not absent and the percentage of NR uplink symbols transmitted in a certain evaluation period is larger than *maxUplinkDutyCycle-EN-DC* as defined in TS 38.331 (The exact evaluation period is no less than one radio frame); or
+- if the IE *p-maxUE-FR1* as defined in TS 38.331 is provided and set to the maximum output power of the default power class or lower:
+- shall apply all requirements for the default power class to the supported power class and set the configured transmitted power as specified in sub-clause 6.2B.4;
+- else if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class and the percentage of uplink symbols transmitted in a certain evaluation period is less than or equal to *maxUplinkDutyCycle-EN-DC* as defined in TS 38.331; or
+- if the IE *p-maxUE-FR1* as defined in TS 38.331 is not provided or set to the higher value than the maximum output power of the default power class and the percentage of NR uplink symbols transmitted in a certain evaluation period is less than or equal to 30% when *maxUplinkDutyCycle-EN-DC* is absent. (The exact evaluation period is no less than one radio frame);
+- shall apply all requirements for the supported power class and set the configured transmitted power class as specified in sub-clause 6.2B.4.
+
+## 5.7 n41-B40 co-existence requirement
+
+For synchronous operation, EUTRA B40 is removed from non-contiguous DC\_41\_n41 and contiguous DC (n)41 coexistence protected bands.
+
+# 6 High power UE (power class 2) for EN-DC (1 LTE TDD band + 1 NR TDD band): Specific Band Combination Part
+
+## 6.1 Inter-band PC2 EN-DC
+
+### 6.1.1 PC2 EN-DC\_41A-79A
+
+#### 6.1.1.1 Operating bands for PC2 EN\_DC
+
+Table 6.1.1.1-1: DC band combination of LTE 1DL/1UL + one NR band
+
+| EN-DC band               | E-UTRA Band | NR Band | Single UL allowed |
+|--------------------------|-------------|---------|-------------------|
+| DC_41A-n79A <sup>1</sup> | 41          | n79     | No                |
+
+NOTE 1: Applicable for UE supporting inter-band carrier aggregation with mandatory simultaneous Rx/Tx capability.
+
+#### 6.1.1.2 Channel bandwidths per operating band for PC2 EN\_DC
+
+Table 6.1.1.2-1: Supported bandwidths per DC band combination of LTE 1DL/1UL + one NR band
+
+| E-UTRA and NR DC Configuration | E-UTRA and NR Band | Subcarrier spacing [kHz] | DC operating / channel bandwidth |        |        |        |         |        |          |        |         | Maximum aggregated bandwidth [MHz] |
+|--------------------------------|--------------------|--------------------------|----------------------------------|--------|--------|--------|---------|--------|----------|--------|---------|------------------------------------|
+|                                |                    |                          | 5 MHz                            | 10 MHz | 15 MHz | 20 MHz | 40 MHz] | 50 MHz | [60 MHz] | 80 MHz | 100 MHz |                                    |
+| DC_41A-n79A                    | 41                 | 15                       | Yes                              | Yes    | Yes    | Yes    |         |        |          |        |         | 120                                |
+|                                | n79                | 15                       |                                  |        |        |        | Yes     | Yes    |          |        |         |                                    |
+|                                |                    | 30                       |                                  |        |        |        | Yes     | Yes    | Yes      | Yes    | Yes     |                                    |
+|                                |                    | 60                       |                                  |        |        |        | Yes     | Yes    | Yes      | Yes    | Yes     |                                    |
+
+#### 6.1.1.3 Co-existence studies for PC2 EN\_DC
+
+The co-existence studies for PC2 EN\_DC\_41A-n79A are reused from PC3 EN\_DC\_41A-n79A.
+
+#### 6.1.1.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN\_DC
+
+For PC2 EN\_DC\_41A-n79A, the  $\square$ TIB,c and  $\square$ RIB values are reused from PC3 EN\_DC\_41A-n79A.
+
+#### 6.1.1.5 MSD for PC2 EN-DC
+
+No specific REFESENS requirements need to be specified
+
+### 6.1.2 PC2 EN-DC\_39A-79A
+
+#### 6.1.2.1 Operating bands for PC2 EN\_DC
+
+**Table 6.1.2.1-1: DC band combination of LTE 1DL/1UL + one NR band**
+
+| EN-DC band                                                                                                        | E-UTRA Band | NR Band | Single UL allowed |
+|-------------------------------------------------------------------------------------------------------------------|-------------|---------|-------------------|
+| DC_39A_n79A <sup>1</sup>                                                                                          | 39          | n79     | No                |
+| NOTE 1: Applicable for UE supporting inter-band carrier aggregation with mandatory simultaneous Rx/Tx capability. |             |         |                   |
+
+#### 6.1.2.2 Channel bandwidths per operating band for PC2 EN\_DC
+
+**Table 6.1.2.2-1: Supported bandwidths per DC band combination of LTE 1DL/1UL + one NR band**
+
+| E-UTRA and NR DC Configuration | E-UTRA and NR Band | Subcarrier spacing [kHz] | DC operating / channel bandwidth |        |        |        |        |        |          |        |         | Maximum aggregated bandwidth [MHz] |
+|--------------------------------|--------------------|--------------------------|----------------------------------|--------|--------|--------|--------|--------|----------|--------|---------|------------------------------------|
+|                                |                    |                          | 5 MHz                            | 10 MHz | 15 MHz | 20 MHz | 40 MHz | 50 MHz | [60 MHz] | 80 MHz | 100 MHz |                                    |
+| DC_39A-n79A                    | 39                 | 15                       | Yes                              | Yes    | Yes    | Yes    |        |        |          |        |         | 120                                |
+|                                | n79                | 15                       |                                  |        |        |        | Yes    | Yes    |          |        |         |                                    |
+|                                |                    | 30                       |                                  |        |        |        | Yes    | Yes    | Yes      | Yes    | Yes     |                                    |
+|                                |                    | 60                       |                                  |        |        |        | Yes    | Yes    | Yes      | Yes    | Yes     |                                    |
+
+#### 6.1.2.3 Co-existence studies for PC2 EN\_DC
+
+The co-existence studies for PC2 EN\_DC\_39A-n79A are reused from PC3 EN\_DC\_39A-n79A.
+
+#### 6.1.2.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN\_DC
+
+For PC2 EN\_DC\_39A-n79A, the  $\Delta$ TIB,c and  $\Delta$ RIB values are reused from PC3 EN\_DC\_39A-n79A.
+
+#### 6.1.2.5 MSD for PC2 EN-DC
+
+No specific REFSENS requirements need to be specified
+
+### 6.1.3 PC2 EN-DC\_39A-41A
+
+#### 6.1.3.1 Operating bands for PC2 EN\_DC
+
+**Table 6.1.3.1-1: DC band combination of LTE 1DL/1UL + one NR band**
+
+| EN-DC band                                                                        | E-UTRA Band | NR Band | Single UL allowed |
+|-----------------------------------------------------------------------------------|-------------|---------|-------------------|
+| DC_39_n41 <sup>1</sup>                                                            | 39          | n41     | No                |
+| NOTE 1: Applicable for UE supporting inter-band EN-DC without simultaneous Rx/Tx. |             |         |                   |
+
+#### 6.1.3.2 Channel bandwidths per operating band for PC2 EN\_DC
+
+**Table 6.1.3.2-1: Supported bandwidths per DC band combination of LTE 1DL/1UL + one NR band**
+
+| EN-DC configuration | Uplink EN-DC configuration | E-UTRA configuration | NR configuration |
+|---------------------|----------------------------|----------------------|------------------|
+| DC_39A_n41A         | DC_39A_n41A                | 39A                  | n41A             |
+
+#### 6.1.3.3 Co-existence studies for PC2 EN\_DC
+
+The co-existence studies for PC2 EN\_DC\_39A-n41A are reused from PC3 EN\_DC\_39A-n41A.
+
+#### 6.1.3.4 ΔTIB and ΔRIB values for PC2 EN\_DC
+
+For PC2 EN\_DC\_39A-n41A, the □TIB,c and □RIB values are reused from PC3 EN\_DC\_39A-n41A.
+
+#### 6.1.3.5 MSD for PC2 EN-DC
+
+No specific REFSENS requirements need to be specified
+
+## 6.2 Intra-band PC2 EN-DC
+
+### 6.2.1 PC2 EN-DC\_(n)41AA
+
+#### 6.2.1.1 Operating bands for PC2 EN\_DC
+
+**Table 6.2.1.1-1: DC band combination of LTE 1DL/1UL + one NR band**
+
+| EN-DC band              | E-UTRA Band | NR Band | Single UL allowed |
+|-------------------------|-------------|---------|-------------------|
+| DC_(n)41AA <sup>1</sup> | 41          | n41     | Yes               |
+
+NOTE 1: Applicable for UE supporting intra-band EN-DC without simultaneous Rx/Tx.
+
+#### 6.2.1.2 Channel bandwidths per operating band for PC2 EN\_DC
+
+**Table 6.2.1.2-1: Supported bandwidths per DC band combination of LTE 1DL/1UL + one NR band**
+
+| E-UTRA and NR DC Configuration | E-UTRA and NR Band | Subcarrier spacing [kHz] | DC operating / channel bandwidth |        |        |        |        |        |        |        |        |         | Maximum aggregated bandwidth [MHz] |
+|--------------------------------|--------------------|--------------------------|----------------------------------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------------------------------------|
+|                                |                    |                          | 5 MHz                            | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 100 MHz |                                    |
+| DC_(n)41AA                     | 41                 | 15                       |                                  |        |        | Yes    |        |        |        |        |        |         | 120                                |
+|                                | n41                | 15                       |                                  |        |        |        |        | Yes    | Yes    |        |        |         |                                    |
+|                                |                    | 30                       |                                  |        |        |        |        | Yes    | Yes    | Yes    | Yes    | Yes     |                                    |
+|                                |                    | 60                       |                                  |        |        |        |        | Yes    | Yes    | Yes    | Yes    | Yes     |                                    |
+
+#### 6.2.1.3 Co-existence studies for PC2 EN\_DC
+
+The co-existence studies for PC2 EN\_DC\_(n)41AA can reuse the band combination specific RF requirements of PC2 EN\_DC\_(n)41AA in TS 38.101-3.
+
+#### 6.2.1.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN\_DC
+
+For PC2 EN\_DC\_(n)41AA, the  $\square$ TIB,c and  $\square$ RIB values can reuse the band combination specific RF requirements of PC2 EN\_DC\_(n)41AA in TS 38.101-3..
+
+#### 6.2.1.5 MSD for PC2 EN-DC
+
+No specific REFSENS requirements need to be specified
+
+#### 6.2.1.6 SEM/A-SEM for PC2 EN-DC
+
+SEM/A-SEM can reuse the band combination specific RF requirements of PC2 EN-DC\_(n)41AA in TS 38.101-3.
+
+#### 6.2.1.7 MPR/A-MPR for PC2 EN-DC
+
+MPR/A-MPR can reuse the band combination specific RF requirements of PC2 EN-DC\_(n)41AA in TS 38.101-3.
+
+### 6.2.2 PC2 EN-DC\_41A-n41A
+
+#### 6.2.2.1 Operating bands for PC2 EN\_DC
+
+**Table 6.2.2.1-1: DC band combination of LTE 1DL/1UL + one NR band**
+
+| EN-DC band                                                                        | E-UTRA Band | NR Band | Single UL allowed |
+|-----------------------------------------------------------------------------------|-------------|---------|-------------------|
+| DC_41A-n41A <sup>1</sup>                                                          | 41          | n41     | Yes               |
+| NOTE 1: Applicable for UE supporting intra-band EN-DC without simultaneous Rx/Tx. |             |         |                   |
+
+#### 6.2.2.2 Channel bandwidths per operating band for PC2 EN\_DC
+
+**Table 6.2.2.2-1: Supported bandwidths per DC band combination of LTE 1DL/1UL + one NR band**
+
+| E-UTRA and NR DC Configuration | E-UTRA and NR Band | Subcarrier spacing [kHz] | DC operating / channel bandwidth |        |        |        |        |        |        |        |        |         | Maximum aggregated bandwidth [MHz] |
+|--------------------------------|--------------------|--------------------------|----------------------------------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------------------------------------|
+|                                |                    |                          | 5 MHz                            | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 100 MHz |                                    |
+| DC_41A-n41A                    | 41                 | 15                       |                                  |        |        | Yes    |        |        |        |        |        |         | 120                                |
+|                                | n41                | 15                       |                                  |        |        |        |        | Yes    | Yes    |        |        |         |                                    |
+|                                |                    | 30                       |                                  |        |        |        |        | Yes    | Yes    | Yes    | Yes    | Yes     |                                    |
+|                                |                    | 60                       |                                  |        |        |        |        | Yes    | Yes    | Yes    | Yes    | Yes     |                                    |
+
+#### 6.2.2.3 Co-existence studies for PC2 EN\_DC
+
+The co-existence studies for PC2 EN\_DC\_41A-n41A can reuse the band combination specific RF requirements of PC2 EN-DC\_41A-n41A in TS 38.101-3.
+
+#### 6.2.2.4 $\Delta$ TIB and $\Delta$ RIB values for PC2 EN\_DC
+
+For PC2 EN\_DC\_41A-n41A, the  $\square$ TIB,c and  $\square$ RIB values can reuse the band combination specific RF requirements of PC2 EN-DC\_41A-n41A in TS 38.101-3.
+
+#### 6.2.2.5 MSD for PC2 EN-DC
+
+No specific REFSENS requirements need to be specified
+
+#### 6.2.2.6 SEM/A-SEM for PC2 EN-DC
+
+SEM/A-SEM can reuse the band combination specific RF requirements of PC2 EN-DC\_41A-n41A in TS 38.101-3.
+
+#### 6.2.2.7 MPR/A-MPR for PC2 EN-DC
+
+MPR/A-MPR can reuse the band combination specific RF requirements of PC2 EN-DC\_41A-n41A in TS 38.101-3.
+
+# 7 Specification impacts
+
+## 7.1 Impacts on RAN4 specifications
+
+### 7.1.1 Intraband EN-DC
+
+Requirements for a Rel-15 UE for additional EN-DC intraband configurations within FR1 compared to TS 38.101-3 of Rel-15 are introduced via this clause.
+
+**Table 7.1.1-1: EN-DC intraband UE power class**
+
+| Feature                                      | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) |
+|----------------------------------------------|-------------|--------------------------|----------------------------------------------------------------------------------------------|
+| Intraband contiguous EN-DC power class 2     | TDD         | Rel-15                   |                                                                                              |
+| Intraband non-contiguous EN-DC power class 2 | TDD         | Rel-15                   |                                                                                              |
+
+**Table 7.1.1-2: PC2 EN-DC intraband configuration**
+
+| EN-DC configuration | REL-indep. From | contact name, company | contact email           | other supporting companies (min. 3) |
+|---------------------|-----------------|-----------------------|-------------------------|-------------------------------------|
+| DC_(n)41AA          | Rel-15          | Shao Zhe, CMCC        | shaozhe@chinamobile.com | CATT, ZTE, Huawei                   |
+| DC_41A-n41A         | Rel-15          | Shao Zhe, CMCC        | shaozhe@chinamobile.com | CATT, ZTE, Huawei                   |
+
+### 7.1.2 Interband EN-DC
+
+Requirements for a Rel-15 UE for additional EN-DC interband configurations within FR1 compared to TS 38.101-3 of Rel-15 are introduced via this clause.
+
+**Table 7.1.2-1: EN-DC interband UE power class**
+
+| Feature                       | Duplex-mode | Release independent from | Requirements to be fulfilled (see TS 38.307 of the release in which the band was introduced) |
+|-------------------------------|-------------|--------------------------|----------------------------------------------------------------------------------------------|
+| Interband EN-DC Power Class 2 | TDD         | Rel-15                   |                                                                                              |
+
+Table 7.1.1-2: PC2 EN-DC interband configuration
+
+| EN-DC configuration | REL-indep. From | contact name, company | contact email           | other supporting companies (min. 3) |
+|---------------------|-----------------|-----------------------|-------------------------|-------------------------------------|
+| DC_39A-n41A         | Rel-15          | Shao Zhe, CMCC        | shaozhe@chinamobile.com | CATT, ZTE, Huawei                   |
+| DC_39A-n79A         | Rel-15          | Shao Zhe, CMCC        | shaozhe@chinamobile.com | CATT, ZTE, Huawei                   |
+| DC_41A-n79A         | Rel-15          | Shao Zhe, CMCC        | shaozhe@chinamobile.com | CATT, ZTE, Huawei                   |
+
+## 7.2 Impacts on specifications for the other WGs (if applicable)
+
+No changes identified
+
+# Annex A: Change history
+
+| Change history |             |            |    |     |                                                                                                                                                                                                                                                                                                                                                           |       |        |  |
+|----------------|-------------|------------|----|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--------|--|
+| Date           | TSG #       | TSG Doc.   | CR | Rev | Subject/Comment                                                                                                                                                                                                                                                                                                                                           | Old   | New    |  |
+| 04/2019        | RAN4#90bis  | R4-1903017 |    |     | TR skeleton                                                                                                                                                                                                                                                                                                                                               | N/A   | 0.0.1  |  |
+| 05/2019        | RAN4#91     | R4-1905403 |    |     | R4-1903018 General part TP for TR37.825 PC2 EN-DC (1 LTE TDD band + 1 NR TDD band).<br>R4-1903019 TP for TR37.825 for PC2 EN-DC_41A-79A<br>R4-1903020 TP for TR37.825 for PC2 EN-DC_39A-79A<br>R4-1903021 TP for TR37.825 for PC2 EN-DC_39A-41A.<br>R4-1903022 TP for TR37.825 for PC2 EN-DC_(n)41AA<br>R4-1903023 TP for TR37.825 for PC2 EN-DC_41A-n41A | 0.0.1 | 0.1.0  |  |
+| 08/2019        | RAN4#92     | R4-1908765 |    |     | R4-1907452 TP for TR37.825 for SAR requirement                                                                                                                                                                                                                                                                                                            | 0.1.0 | 0.2.0  |  |
+| 10/2019        | RAN4#92-bis | R4-1910768 |    |     | Update Definitions, symbols and abbreviations                                                                                                                                                                                                                                                                                                             | 0.2.0 | 0.3.0  |  |
+| 11/2019        | RAN4#93     | R4-1913208 |    |     | <a href="#">R4-1910770</a> TP for TR37.825 for release independent issue                                                                                                                                                                                                                                                                                  | 0.3.0 | 0.4.0  |  |
+| 12/2019        | RAN#86      | RP-192583  |    |     | <a href="#">R4-1913208</a> TR 37.825 v0.4.0 Finalization                                                                                                                                                                                                                                                                                                  | 0.4.0 | 1.0.0  |  |
+| 12/2019        | RAN#86      | RP-192583  |    |     | v16.0.0 created based on approved RP-192583                                                                                                                                                                                                                                                                                                               | 1.0.0 | 16.0.0 |  |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37873/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-16/37_series/37873/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4ccc6536d93d1f9d1c69d8071acff0f461817a17
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/0236eff05bcb8f3a343ea7933aaa306b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:20ea3f3e671bc75fbc7b35bdac60c2887572306254cb71c9821a42b96f6a986b
+size 22890
diff --git a/marked/Rel-16/37_series/37873/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/37_series/37873/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6c8f164a8710605826684ee21784b3f62c828d80
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/1b5a812c8aa20fd5cba28e97001d32de_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:516067162c587bc6e3b54f03cf6c54a8e90ed3e5427abcffd721bf45adc75a5d
+size 53098
diff --git a/marked/Rel-16/37_series/37873/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/37_series/37873/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..522702a5c6e8f7bd7446de3823a6c0b35e382054
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2a729ad9e543b2abddae358e0b2098667aacf4237408750c127978c25d0f01cb
+size 90388
diff --git a/marked/Rel-16/37_series/37873/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/marked/Rel-16/37_series/37873/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8966415fa8794ae26d06a77e2c8aef347eae3737
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:17f25937e963967eaf1347facbf7623e69ea4313952bf291bf35b1e72ec22f20
+size 34427
diff --git a/marked/Rel-16/37_series/37873/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-16/37_series/37873/54fabc351eda5228d2fa28cd9ba07971_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..662f09c9272f9260d39db1b6e83e835522c3c4d9
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/54fabc351eda5228d2fa28cd9ba07971_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8aff018be3f76f8ca5279264b3507bf4929c9e538bfd825c9501d4211ef095f
+size 38469
diff --git a/marked/Rel-16/37_series/37873/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/37_series/37873/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3dbe11e88a70b0f9aa385bcda059babc73f0f02
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e678d8e97263334ee3bdcf9f52e8662f88b83b6e9761ce252f4f3b146cca014b
+size 61817
diff --git a/marked/Rel-16/37_series/37873/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37873/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f04245721b373e8adc662b2dca2a692b4b12c425
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e503ac7ee9e8e35c0de172fefd4192b72352f15b83463e29b78353a92dd7b7a4
+size 8726
diff --git a/marked/Rel-16/37_series/37873/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37873/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0b77bf2c7fe8dbfb2937c6201dba42495ff3e46
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23b4c583c032e010ee30977c34a97a658b49f0704af30cedd9bd024743885032
+size 5422
diff --git a/marked/Rel-16/37_series/37873/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-16/37_series/37873/731f533b0599c8e42a063f06e4332045_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc43560d335b0d50d831eead3e7ffcb8d5f2f078
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/731f533b0599c8e42a063f06e4332045_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6fd86f7027725b9ec1fb25ed43cb14b4dd858cee191647c7ee756bc1276c038c
+size 42753
diff --git a/marked/Rel-16/37_series/37873/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/37_series/37873/7efae06af3af43ffe5d4b956a679cf54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b3052d31383141aabdd9b7b47847f4de840360e
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/7efae06af3af43ffe5d4b956a679cf54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53f9da231c414359c500a12f4916045552af4a1781162723569598ef74c925f6
+size 14779
diff --git a/marked/Rel-16/37_series/37873/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/37_series/37873/8e14350b4b669119a3bdfca7869110ca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f778915bdfaf184e7216dffe36ed7b6d1ae68d78
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/8e14350b4b669119a3bdfca7869110ca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:453fcc8121961ac5f98e68dbe1ef9284eebca6f40ddbb0d39c3a752060e9df05
+size 48612
diff --git a/marked/Rel-16/37_series/37873/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/37_series/37873/a234352dfaccdc24745c88eef7724cc6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d3abe6c4b621818f37db9e0f2eaeb463c75bb433
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/a234352dfaccdc24745c88eef7724cc6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:66e8aaed73c2b301ab50b9cb0d12e38a39b86bea5e3f112c171ae416c35a4381
+size 34863
diff --git a/marked/Rel-16/37_series/37873/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/37_series/37873/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a9569b51151a33ab00735eefd80dcded85ddf98c
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45fb6b775c11f7ea64622617fa35f686dafbb209cce2391f1313335f25cd7ad7
+size 79387
diff --git a/marked/Rel-16/37_series/37873/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/marked/Rel-16/37_series/37873/d17f75945bbb3feb84a153ecfedb9b81_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..878a2ab9c06eae389e7ebcfc9f59bd922c4f9995
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/d17f75945bbb3feb84a153ecfedb9b81_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bdcd50bfca20f38c23d8ccc29f7441f2942d5145722f9c6ef80936198cee35d
+size 16249
diff --git a/marked/Rel-16/37_series/37873/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/37_series/37873/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ff8117d563b222460c05d45d8b2eadb3270a57e2
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:595d8f074f83afa9b96ea456bc22a5393b503b619f7f7dfc4763c91195da116c
+size 61278
diff --git a/marked/Rel-16/37_series/37873/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/37_series/37873/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f437baf368a40ab4d1556ba22d8db62ab6cefb5
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/e9d825d87c5f85c8dba0664eace96ef4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4989ae49f531bee5171fa1fb43a2cabbb3e7c9186fa6bb76f72316709530e5d
+size 51247
diff --git a/marked/Rel-16/37_series/37873/raw.md b/marked/Rel-16/37_series/37873/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..7537059d6840780130817ba0b1a9e02837f15c47
--- /dev/null
+++ b/marked/Rel-16/37_series/37873/raw.md
@@ -0,0 +1,595 @@
+
+
+# 3GPP TR 37.873 V16.0.0 (2019-03) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR and Evolved Universal Terrestrial Radio Access (E-UTRA); Study on optimizations of UE radio capability signalling; (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+---
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                 |                                                                                  |           |
+|-----------------|----------------------------------------------------------------------------------|-----------|
+| 1               | Scope.....                                                                       | 4         |
+| 2               | References.....                                                                  | 4         |
+| 3               | Definitions, symbols and abbreviations .....                                     | 5         |
+| 3.1             | Definitions.....                                                                 | 5         |
+| 4               | Void.....                                                                        | 5         |
+| 5               | UE Radio Capability Signaling Size Analysis .....                                | 5         |
+| 5.1             | UE Radio Capability size estimation .....                                        | 5         |
+| 5.2             | Limitations on different interfaces .....                                        | 5         |
+| 5.3             | Analysis.....                                                                    | 6         |
+| 6               | UE Radio Capability Signaling Optimizations .....                                | 6         |
+| 6.1             | Solutions using UE capability Identity.....                                      | 6         |
+| 6.1.1           | UE capability Identity.....                                                      | 6         |
+| 6.1.1.1         | Description.....                                                                 | 6         |
+| 6.1.1.2         | Signalling for transfer of UE capability identity .....                          | 7         |
+| 6.1.1.2.1       | Approach 1: Transfer via RRC signalling.....                                     | 7         |
+| 6.1.1.2.2       | Approach 2: Transfer via NAS signalling.....                                     | 7         |
+| 6.1.1.3         | Interaction between NG-RAN and CN for management of UE capability identity ..... | 8         |
+| 6.1.1.3.1       | Summary of approaches .....                                                      | 8         |
+| 6.1.1.3.2       | Approach 1: Mapping stored at NG-RAN only .....                                  | 8         |
+| 6.1.1.3.3       | Approach 2: Mapping stored at CN only .....                                      | 9         |
+| 6.1.1.3.4       | Approach 3: Mapping stored at CN and NG-RAN, using NAS signalling.....           | 10        |
+| 6.1.1.3.5       | Approach 4: Mapping stored at CN and NG-RAN, using RRC signalling.....           | 11        |
+| 6.1.2           | UE capability Identity combined with other means .....                           | 12        |
+| 6.1.2.1         | Solution using Hash-based Identification of UE radio capabilities.....           | 12        |
+| 6.1.2.1.1       | Description .....                                                                | 12        |
+| 6.1.2.2         | UE Capability ID with delta set of UE Radio Capabilities.....                    | 12        |
+| 6.1.2.2.1       | Description .....                                                                | 12        |
+| 6.2             | Solutions using other means.....                                                 | 13        |
+| 6.2.1           | Segmentation of capabilities.....                                                | 13        |
+| 6.2.1.1         | Description.....                                                                 | 13        |
+| 6.2.1.2         | Signalling for transfer of UE capabilities in segments .....                     | 13        |
+| 6.2.1.3         | Segmentation structure .....                                                     | 13        |
+| 6.2.1.3.1       | Segmentation at RRC level .....                                                  | 13        |
+| 6.2.1.3.2       | Segmentation at PDCP level .....                                                 | 13        |
+| 6.2.2           | Uplink Capability Signalling Compression (UCSC).....                             | 14        |
+| 7               | Conclusion .....                                                                 | 15        |
+| 7.1             | Solutions using UE capability Identity.....                                      | 15        |
+| 7.2             | Solutions using other means.....                                                 | 15        |
+| <b>Annex A:</b> | <b>Change history .....</b>                                                      | <b>16</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is intended to capture findings produced in the context of the study on optimizations of UE radio capability signalling.
+
+The study is expected to proceed as follows:
+
+- Study the size of UE Radio Capability signaling
+- Study mechanisms to optimise the UE Radio Capability signalling over the air while addressing the limitations of radio protocol interface,
+  - Solutions using UE capability identity,
+  - Solutions using other means (i.e. segmentation, compression).
+
+The study shall consider the possibility to change UE radio capabilities.
+
+As part of the study and in coordination with other WGs especially RAN WGs it should be concluded whether to proceed with normative work.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+
+[2] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
+
+- [3] 3GPP TR 23.743: "Study on optimisations of UE radio capability signalling".
+- [4] 3GPP TS 23.501: "System Architecture for the 5G System".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+# --- 4 Void
+
+# --- 5 UE Radio Capability Signaling Size Analysis
+
+## 5.1 UE Radio Capability size estimation
+
+For LTE, the primary overhead introduced by Rel-15 parameters is *FeatureSetsEUTRA-r15*. The theoretical overhead of *FeatureSetsEUTRA-r15* can exceed 10 kbytes.
+
+In practical deployment, the size of *featureSetsEUTRA-r15* is variable depending on the number of DL/UL feature sets per band and the number of DL/UL feature sets per CC, in some cases the size of *featureSetsEUTRA-r15* can be several kbytes, and the total size of *UE-EUTRA-Capability* can be ~4 kbytes with realistic assumptions.
+
+For NR and EN-DC, based on the newly introduced structure for UE capability in Rel-15, the size of the UE capability is dominated by *rf-Parameters*, *featureSetCombinations* and *featureSets*. The estimated theoretical maximum size of UE radio capabilities for NR or EN-DC (based on the maximum sizes in ASN.1) can approximate to 10000 kbytes,
+
+In practical deployment, the supported bands/band combinations for a device is limited, and the eNB/gNB can for example request the UE to provide UE radio capabilities for a restricted set of band combinations. According to LTE experience and analysis of the NR capability, the estimated practical size of *rf-Parameters* is about 11~12 kbytes based on ~1024 band combinations and up to 4 bands per band combination.
+
+The size of *featureSetCombinations* is highly variable depending on the number of feature set combinations and the number of feature sets per band, the size of *featureSets* is variable depending on the number of DL/UL feature sets per band and the number of DL/UL feature sets per CC. However, in some cases either the size of *featureSetCombinations* or *featureSets* can significantly exceed the size limitation of PDCP PDU. For example, with 256 feature set combinations, 8 feature sets per band, and 4 bands per band combination, the feature set combination list occupies ~22 kbytes.
+
+## 5.2 Limitations on different interfaces
+
+The estimated theoretical maximum size of UE radio capabilities is extremely large. The estimated practical size of UE radio capabilities can be reduced, and the estimated size of "several tens of kilo-octets" appears to be valid.
+
+For RAN interfaces, the size limitation of PDCP PDU is 9000 bytes for NR and 8188 bytes LTE, and there are no limitations for SCTP based interface. For core network interfaces, the size for the RAN transparent container is limited to 50 kbytes for GTP based S10 interface and N26 interface, but no upper limit is defined for HTTP based N14 interface.
+
+## 5.3 Analysis
+
+It is hard for the size of UE radio capabilities to respect the limitation of Uu interface both for NR and LTE, and it can even exceed the limitation of GTP based interfaces.
+
+The issue of exceeding the size limitation exists mainly for:
+
+- 1) UE radio capabilities reporting via Uu interface in NR scenario and LTE scenario;
+- 2) UE radio capabilities transfer between two MMEs (S1 based handover) as well as between MME and AMF (handover between LTE and NR).
+
+# --- 6 UE Radio Capability Signaling Optimizations
+
+## 6.1 Solutions using UE capability Identity
+
+### 6.1.1 UE capability Identity
+
+#### 6.1.1.1 Description
+
+This section describes the use of a UE capability identity, i.e. a short value that can be used as a representation of all or part of the UE capability.
+
+RAN2 preference is for a single capability identity covering all capability containers (i.e. *UE-NR-Capability*, *UE-EUTRA-Capability*, and *UE-MRDC-Capability*), as opposed to separate identity values for the different containers.
+
+The identity based mechanism is intended to coexist with, rather than replace, the legacy capability transfer signalling. It is also intended to coexist with NAS initiated changes of capability. In case of NAS change of capability, RAN2 understand that if the new capability set has an ID assigned, the capability ID signalling can be used to update the capability; if the new capability set does not have an ID assigned, the legacy capability signalling can be used to transfer the new capability. In a context where network-assigned capability IDs are supported, after the UE indicates a changed capability with legacy signalling, RAN2 assume the network may assign a capability ID to the new set.
+
+RAN2 assume the capability ID is known to the NG-RAN during the connection setup procedure.
+
+RAN2 assume that if the UE has an ID for its current capability set, it will signal the capability ID at least in case the network indicates support for the feature.
+
+In 5G, all capability requests will be filtered. The filter is included as a part of the signalled UE capabilities so that the gNB can determine if it should request more capability information from UE's moving into the cell.
+
+In a context where network-assigned capability IDs, RAN2 have discussed filtering and the impacts on capability signalling, and concluded that:
+
+- It is possible for the network to use different filters in different parts of the PLMN.
+- UE provides capability to the network based on the filter and if an ID is assigned then the ID is associated to whatever capabilities it has transferred earlier.
+- The Capability ID is unique within a PLMN - i.e. the UE can provide capability ID anywhere within this PLMN (this does not imply that Capability ID to capability set mapping needs to be known throughout the PLMN).
+
+Further enhancement on current filtering function is to be considered in normative phase.
+
+#### 6.1.1.2 Signalling for transfer of UE capability identity
+
+##### 6.1.1.2.1 Approach 1: Transfer via RRC signalling
+
+The transfer of UE capability in RRC signalling is shown in Figure 6.1.1.2.1-1. The UE sends a UE capability ID in an RRC message, which could be either the *RRCSsetupComplete* message or the *UECapabilityInformation* message. The subsequent handling of the UE capability ID is discussed in subclause 6.1.1.3. In this alternative, the UE capability ID is visible to the NG-RAN at the time of connection setup.
+
+![Sequence diagram showing RRC transfer of UE capability ID using RRCSsetupComplete. The diagram shows three messages between UE and NG-RAN: 1. RRCSsetupRequest from NG-RAN to UE, 2. RRCSsetup from NG-RAN to UE, and 3. RRCSsetupComplete (including UE capability ID) from UE to NG-RAN.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    Note right of NG-RAN: 1. RRCSsetupRequest
+    NG-RAN->>UE: 1. RRCSsetupRequest
+    Note right of NG-RAN: 2. RRCSsetup
+    NG-RAN->>UE: 2. RRCSsetup
+    Note left of UE: 3. RRCSsetupComplete (including UE capability ID)
+    UE->>NG-RAN: 3. RRCSsetupComplete (including UE capability ID)
+```
+
+Sequence diagram showing RRC transfer of UE capability ID using RRCSsetupComplete. The diagram shows three messages between UE and NG-RAN: 1. RRCSsetupRequest from NG-RAN to UE, 2. RRCSsetup from NG-RAN to UE, and 3. RRCSsetupComplete (including UE capability ID) from UE to NG-RAN.
+
+**Figure 6.1.1.2.1-1: RRC transfer of UE capability ID using *RRCSsetupComplete***
+
+Subsequent to the signalling of Figure 6.1.1.2.1-1, it is possible to transfer the UE capability ID also to the CN, e.g. in the Initial UE Message. This allows visibility of the ID in both NG-RAN and CN if necessary.
+
+RRC signalling allows the RAN to know the UE capability ID directly (i.e. without the involvement of the AMF), and if sent early in the connection procedure, it can enable RAN caching for early configuration of the UE capability. RRC signalling does not preclude that the UE capability ID is provided to AMF.
+
+RAN visibility of the capability ID is considered beneficial for RAN caching of the UE capability set, signalling reduction on network interfaces, and early RRM decisions.
+
+After considering SA3 requirement (R2-1900087) on the security protection of UE capability ID, this approach is not considered valid.
+
+##### 6.1.1.2.2 Approach 2: Transfer via NAS signalling
+
+The transfer of UE capability in NAS signalling is shown in Figure 6.1.1.2.2-1. The UE sends a UE capability ID to the CN using a NAS message before the CN sends the Initial Context Setup Request to the NG-RAN. The subsequent handling of the UE capability ID is discussed in subclause 6.1.1.3. In this alternative, the UE capability ID is visible to the CN at the time of the NAS message (i.e. before initial context setup).
+
+![Sequence diagram showing NAS transfer of UE capability ID. The diagram shows two main steps: 1. RRC Connection Establishment procedure between UE and NG-RAN, and 2. UE sends UE capability ID during registration, authentication, or identity response between UE and CN.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note left of NG-RAN: 1. RRC Connection Establishment procedure
+    UE->>NG-RAN: 1. RRC Connection Establishment procedure
+    Note left of CN: 2. UE sends UE capability ID during registration, authentication, or identity response
+    UE->>CN: 2. UE sends UE capability ID during registration, authentication, or identity response
+```
+
+Sequence diagram showing NAS transfer of UE capability ID. The diagram shows two main steps: 1. RRC Connection Establishment procedure between UE and NG-RAN, and 2. UE sends UE capability ID during registration, authentication, or identity response between UE and CN.
+
+**Figure 6.1.1.2.2-1: NAS transfer of UE capability ID**
+
+Subsequent to the signalling of Figure 6.1.1.2.2-1, it is possible to transfer the UE capability ID also to the NG-RAN, e.g. in the Initial Context Setup Request. This allows visibility of the ID in both NG-RAN and CN if necessary.
+
+NAS signalling of the ID enables a solution transparent to RRC.
+
+#### 6.1.1.3 Interaction between NG-RAN and CN for management of UE capability identity
+
+##### 6.1.1.3.1 Summary of approaches
+
+After the UE capability ID is transferred from the UE to either the NG-RAN or the CN, an entity in the network is responsible for mapping the ID to the UE capability set.
+
+If the ID is first provided to the NG-RAN (e.g. by RRC signalling as described in subclause 6.1.1.2.1), there are three alternatives: The mapping of the ID to UE capability set can be stored at the NG-RAN, the CN, or both. In case the mapping is stored in both NG-RAN and CN, there are different solutions depending on whether the capability ID is transferred to the network via RRC or NAS signalling. The different approaches are described in the following sections.
+
+##### 6.1.1.3.2 Approach 1: Mapping stored at NG-RAN only
+
+If the mapping is stored at the NG-RAN only, no capability-related interaction with the CN is required and the capability exchange can proceed as shown in Figure 6.1.1.3.2-1.
+
+![Sequence diagram showing the interaction between UE, NG-RAN, and CN for UE capability identification. The steps are: 1. UE capability ID transfer to NG-RAN; 2. Identify the UE capability in association table (internal NG-RAN step); 3. Initial UE Message (without UE capability request) from NG-RAN to CN; 4. Authentication (between NG-RAN and CN); 5. Initial Context Setup Request from CN to NG-RAN.](731f533b0599c8e42a063f06e4332045_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note right of NG-RAN: 2. Identify the UE capability in association table
+    UE->>NG-RAN: 1. UE capability ID transfer to NG-RAN
+    NG-RAN->>CN: 3. Initial UE Message (without UE capability request)
+    Note over NG-RAN, CN: 4. Authentication
+    CN->>NG-RAN: 5. Initial Context Setup Request
+```
+
+Sequence diagram showing the interaction between UE, NG-RAN, and CN for UE capability identification. The steps are: 1. UE capability ID transfer to NG-RAN; 2. Identify the UE capability in association table (internal NG-RAN step); 3. Initial UE Message (without UE capability request) from NG-RAN to CN; 4. Authentication (between NG-RAN and CN); 5. Initial Context Setup Request from CN to NG-RAN.
+
+**Figure 6.1.1.3.2-1: NG-RAN identification of UE capability without CN interaction**
+
+In the procedure of Figure 6.1.1.3.2-1, step 1 may involve either RRC signalling (as in subclause 6.1.1.2.1) or NAS signalling (as in subclause 6.1.1.2.2, with subsequent transfer of the ID from the CN to the NG-RAN). Step 5 (the Initial Context Setup Request from CN to NG-RAN) may or may not include a request for UE capability, depending on whether the CN has already stored capability information for this UE.
+
+If the NG-RAN is not able to identify the UE capability in the association table, it needs to request it from the CN in step 3 (the Initial UE Message). If neither the NG-RAN nor the CN is able to identify the UE capability, the NG-RAN initiates a UE capability enquiry procedure (and updates the association table accordingly). The latter case is shown in Figure 6.1.1.3.2-2.
+
+![Sequence diagram for Figure 6.1.1.3.2-2: NG-RAN and CN unable to identify UE capability. The diagram shows interactions between UE, NG-RAN, and CN. 1. UE capability ID transfer to NG-RAN. 2. NG-RAN unable to identify UE capability in association table. 3. NG-RAN sends Initial UE Message (with UE capability request) to CN. 4. Authentication. 5. CN has not stored the corresponding UE capability. 6. CN sends Initial Context Setup Request (with UE capability request) to NG-RAN. 7. NG-RAN sends UECapabilityEnquiry to UE. 8. UE sends UECapabilityInformation to NG-RAN. 9. NG-RAN stores the UE capability and updates association table. 10. NG-RAN sends UE Capability Info Indication to CN. 11. CN stores the UE capability.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, NG-RAN: 1. UE capability ID transfer to NG-RAN
+    Note over NG-RAN: 2. Unable to identify the UE capability in association table
+    NG-RAN->>CN: 3. Initial UE Message (with UE capability request)
+    Note over UE, CN: 4. Authentication
+    Note over CN: 5. CN has not stored the corresponding UE capability
+    CN->>NG-RAN: 6. Initial Context Setup Request (with UE capability request)
+    NG-RAN->>UE: 7. UECapabilityEnquiry
+    UE->>NG-RAN: 8. UECapabilityInformation
+    Note over NG-RAN: 9. Store the UE capability and update association table
+    NG-RAN->>CN: 10. UE Capability Info Indication
+    Note over CN: 11. Store the UE capability
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.2-2: NG-RAN and CN unable to identify UE capability. The diagram shows interactions between UE, NG-RAN, and CN. 1. UE capability ID transfer to NG-RAN. 2. NG-RAN unable to identify UE capability in association table. 3. NG-RAN sends Initial UE Message (with UE capability request) to CN. 4. Authentication. 5. CN has not stored the corresponding UE capability. 6. CN sends Initial Context Setup Request (with UE capability request) to NG-RAN. 7. NG-RAN sends UECapabilityEnquiry to UE. 8. UE sends UECapabilityInformation to NG-RAN. 9. NG-RAN stores the UE capability and updates association table. 10. NG-RAN sends UE Capability Info Indication to CN. 11. CN stores the UE capability.
+
+**Figure 6.1.1.3.2-2: NG-RAN and CN unable to identify UE capability**
+
+The benefits of having the mapping visible at the RAN include enabling RAN caching and reducing overhead on network interfaces.
+
+##### 6.1.1.3.3 Approach 2: Mapping stored at CN only
+
+If the mapping is stored at the CN only, the capability exchange can proceed as shown in Figure 6.1.1.3.3-1.
+
+![Sequence diagram for Figure 6.1.1.3.3-1: CN identification of UE capability and delivery to NG-RAN. The diagram shows interactions between UE, NG-RAN, and CN. 1. UE capability ID transfer to CN. 2. CN identifies the UE capability in association table. 3. CN sends Initial Context Setup Request (with UE capability) to NG-RAN.](a234352dfaccdc24745c88eef7724cc6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, CN: 1. UE capability ID transfer to CN
+    Note over CN: 2. Identify the UE capability in association table
+    CN->>NG-RAN: 3. Initial Context Setup Request (with UE capability)
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.3-1: CN identification of UE capability and delivery to NG-RAN. The diagram shows interactions between UE, NG-RAN, and CN. 1. UE capability ID transfer to CN. 2. CN identifies the UE capability in association table. 3. CN sends Initial Context Setup Request (with UE capability) to NG-RAN.
+
+**Figure 6.1.1.3.3-1: CN identification of UE capability and delivery to NG-RAN**
+
+In the procedure of Figure 6.1.1.3.3-1, step 1 may involve either RRC signalling (as in subclause 6.1.1.2.1, with subsequent transfer of the ID from the NG-RAN to the CN) or NAS signalling (as in subclause 6.1.1.2.2). If the CN is not able to identify the UE capability in the association table in step 2, it requests the NG-RAN to retrieve the UE capability in step 3, resulting in a UE capability enquiry procedure as shown in Figure 6.1.1.3.3-2.
+
+![Sequence diagram for Figure 6.1.1.3.3-2: CN unable to identify UE capability. The diagram shows three lifelines: UE, NG-RAN, and CN. Step 1: UE capability ID transfer to CN (UE to CN). Step 2: CN is unable to identify the UE capability in its association table. Step 3: CN sends an Initial Context Setup Request (with UE capability request) to NG-RAN. Step 4: NG-RAN sends a UECapabilityEnquiry to UE. Step 5: UE sends UECapabilityInformation to NG-RAN. Step 6: NG-RAN stores the UE capability. Step 7: NG-RAN sends a UE Capability Info Indication to CN. Step 8: CN stores the UE capability and updates its association table.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, CN: 1. UE capability ID transfer to CN
+    Note right of CN: 2. Unable to identify the UE capability in association table
+    Note right of CN: 3. Initial Context Setup Request (with UE capability request)
+    Note left of NG-RAN: 4. UECapabilityEnquiry
+    Note left of NG-RAN: 5. UECapabilityInformation
+    Note right of NG-RAN: 6. Store the UE capability
+    Note right of NG-RAN: 7. UE Capability Info Indication
+    Note right of CN: 8. Store the UE capability and update association table
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.3-2: CN unable to identify UE capability. The diagram shows three lifelines: UE, NG-RAN, and CN. Step 1: UE capability ID transfer to CN (UE to CN). Step 2: CN is unable to identify the UE capability in its association table. Step 3: CN sends an Initial Context Setup Request (with UE capability request) to NG-RAN. Step 4: NG-RAN sends a UECapabilityEnquiry to UE. Step 5: UE sends UECapabilityInformation to NG-RAN. Step 6: NG-RAN stores the UE capability. Step 7: NG-RAN sends a UE Capability Info Indication to CN. Step 8: CN stores the UE capability and updates its association table.
+
+**Figure 6.1.1.3.3-2: CN unable to identify UE capability**
+
+The benefits of having the mapping visible at the core network include the ability to use the CN as a "master" repository of the mapping (rather than e.g. distributed storage across all gNBs), the ability for the RAN to refer to the CN when it is not aware of the mapping, and access to the capability mapping also for UEs in RRC\_IDLE.
+
+##### 6.1.1.3.4 Approach 3: Mapping stored at CN and NG-RAN, using NAS signalling
+
+If the mapping is stored at the CN and the NG-RAN and the transfer of the UE capability ID uses NAS signalling, the capability exchange can proceed as shown in Figure 6.1.1.3.4-1.
+
+![Sequence diagram for Figure 6.1.1.3.4-1: NG-RAN and CN identification of UE capability (with NAS signalling). The diagram shows three lifelines: UE, NG-RAN, and CN. Step 1: UE capability ID transfer to CN by NAS signalling (UE to CN). Step 2: CN identifies the UE capability in its association table. Step 3: CN sends an Initial Context Setup Request (with UE capability ID) to NG-RAN. Step 4: NG-RAN identifies the UE capability in its association table.](54fabc351eda5228d2fa28cd9ba07971_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, CN: 1. UE capability ID transfer to CN by NAS signalling
+    Note right of CN: 2. Identify the UE capability in association table
+    Note right of CN: 3. Initial Context Setup Request (with UE capability ID)
+    Note right of NG-RAN: 4. Identify the UE capability in association table
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.4-1: NG-RAN and CN identification of UE capability (with NAS signalling). The diagram shows three lifelines: UE, NG-RAN, and CN. Step 1: UE capability ID transfer to CN by NAS signalling (UE to CN). Step 2: CN identifies the UE capability in its association table. Step 3: CN sends an Initial Context Setup Request (with UE capability ID) to NG-RAN. Step 4: NG-RAN identifies the UE capability in its association table.
+
+**Figure 6.1.1.3.4-1: NG-RAN and CN identification of UE capability (with NAS signalling)**
+
+In the procedure of Figure 6.1.1.3.4-1, if the CN is not able to identify the UE capability in step 2, it requests in step 3 for the NG-RAN to deliver the UE capability. If the NG-RAN is not able to identify the UE capability in step 4, it performs a UE capability enquiry procedure, as shown in Figure 6.1.1.3.4-2.
+
+![Sequence diagram for Figure 6.1.1.3.4-2: NG-RAN unable to identify UE capability. The diagram shows three lifelines: UE, NG-RAN, and CN. 1. UE capability ID transfer to CN by NAS signalling. 2. CN identifies the UE capability in its association table. 3. CN sends an Initial Context Setup Request (with UE capability ID) to NG-RAN. 4. NG-RAN fails to identify the UE capability in its association table. 5. NG-RAN sends a UECapabilityEnquiry to UE. 6. UE sends UECapabilityInformation to NG-RAN. 7. NG-RAN stores the UE capability and updates its association table.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, CN: 1. UE capability ID transfer to CN by NAS signalling
+    Note right of CN: 2. Identify the UE capability in association table
+    CN->>NG-RAN: 3. Initial Context Setup Request (with UE capability ID)
+    Note right of NG-RAN: 4. Fail to identify the UE capability in association table
+    NG-RAN->>UE: 5. UECapabilityEnquiry
+    UE->>NG-RAN: 6. UECapabilityInformation
+    Note right of NG-RAN: 7. Store the UE capability and update association table
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.4-2: NG-RAN unable to identify UE capability. The diagram shows three lifelines: UE, NG-RAN, and CN. 1. UE capability ID transfer to CN by NAS signalling. 2. CN identifies the UE capability in its association table. 3. CN sends an Initial Context Setup Request (with UE capability ID) to NG-RAN. 4. NG-RAN fails to identify the UE capability in its association table. 5. NG-RAN sends a UECapabilityEnquiry to UE. 6. UE sends UECapabilityInformation to NG-RAN. 7. NG-RAN stores the UE capability and updates its association table.
+
+Figure 6.1.1.3.4-2: NG-RAN unable to identify UE capability
+
+##### 6.1.1.3.5 Approach 4: Mapping stored at CN and NG-RAN, using RRC signalling
+
+If the mapping is stored at the CN and the NG-RAN and the transfer of the UE capability ID uses RRC signalling, the capability exchange can proceed as shown in Figure 6.1.1.3.5-1.
+
+![Sequence diagram for Figure 6.1.1.3.5-1: NG-RAN and CN identification of UE capability (with RRC signalling). The diagram shows three lifelines: UE, NG-RAN, and CN. 1. UE capability ID transfer to NG-RAN by RRC signalling. 2. NG-RAN identifies the UE capability in its association table. 3. NG-RAN sends an Initial UE Message (with UE capability ID) to CN. 4. Authentication. 5. CN identifies the UE capability in its association table. 6. CN sends an Initial Context Setup Request to NG-RAN.](8e14350b4b669119a3bdfca7869110ca_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note over UE, NG-RAN: 1. UE capability ID transfer to NG-RAN by RRC signalling
+    Note right of NG-RAN: 2. Identify the UE capability in association table
+    NG-RAN->>CN: 3. Initial UE Message (with UE capability ID)
+    Note over UE, CN: 4. Authentication
+    Note right of CN: 5. Identify the UE capability in association table
+    CN->>NG-RAN: 6. Initial Context Setup Request
+  
+```
+
+Sequence diagram for Figure 6.1.1.3.5-1: NG-RAN and CN identification of UE capability (with RRC signalling). The diagram shows three lifelines: UE, NG-RAN, and CN. 1. UE capability ID transfer to NG-RAN by RRC signalling. 2. NG-RAN identifies the UE capability in its association table. 3. NG-RAN sends an Initial UE Message (with UE capability ID) to CN. 4. Authentication. 5. CN identifies the UE capability in its association table. 6. CN sends an Initial Context Setup Request to NG-RAN.
+
+Figure 6.1.1.3.5-1: NG-RAN and CN identification of UE capability (with RRC signalling)
+
+In the procedure of Figure 6.1.1.3.5-1, if the NG-RAN is not able to identify the UE capability in step 2, it requests in step 3 for the CN to deliver the UE capability and the CN delivers it with the subsequent Initial Context Setup Request. If the CN is not able to identify the UE capability in step 4, it requests it from the NG-RAN along with the Initial Context Setup Request. If neither the NG-RAN nor the CN can identify the UE capability, the NG-RAN performs a UE capability enquiry. The latter case is shown in Figure 6.1.1.3.5-2.
+
+![Sequence diagram showing the interaction between UE, NG-RAN, and CN when NG-RAN and CN are unable to identify UE capability. The process involves RRC signalling, authentication, and subsequent capability requests and updates.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant NG-RAN
+    participant CN
+    Note left of NG-RAN: 1. UE capability ID transfer to NG-RAN by RRC signalling
+    Note right of NG-RAN: 2. Fail to identify the UE capability in association table
+    Note right of NG-RAN: 3. Initial UE Message (with UE capability request)
+    Note over UE, NG-RAN, CN: 4. Authentication
+    Note right of CN: 5. Fail to identify the UE capability in association table
+    Note right of CN: 6. Initial Context Setup Request (with UE capability request)
+    Note left of NG-RAN: 7. UECapabilityEnquiry
+    Note right of UE: 8. UECapabilityInformation
+    Note right of NG-RAN: 9. Store the UE capability and update association table
+    Note right of NG-RAN: 10. UE Capability Info Indication
+    Note right of CN: 11. Store the UE capability and update association table
+  
+```
+
+Sequence diagram showing the interaction between UE, NG-RAN, and CN when NG-RAN and CN are unable to identify UE capability. The process involves RRC signalling, authentication, and subsequent capability requests and updates.
+
+Figure 6.1.1.3.5-2: NG-RAN and CN unable to identify UE capability
+
+### 6.1.2 UE capability Identity combined with other means
+
+#### 6.1.2.1 Solution using Hash-based Identification of UE radio capabilities
+
+##### 6.1.2.1.1 Description
+
+*On HASH-based ID's as described in solution #3 in 23.743[3], RAN2 has identified that, to create a hash-Capability ID the UE needs to do this assuming some specific capability information. It is not obvious what capability information the UE would have the hash operate on to create the ID. Further, there are aspects related to the length of the ID, for which the length would need to be longer than other ID solutions.*
+
+*RAN2 concludes that HASH-based ID's offer very little possibilities to explore additional advantages over those already possible with the solutions described in the SA2 interim conclusions.*
+
+#### 6.1.2.2 UE Capability ID with delta set of UE Radio Capabilities
+
+##### 6.1.2.2.1 Description
+
+*On 'delta signalling' as described in solution #9 in 23.743[3], RAN2 understands that all the impacts of 'delta signalling' (i.e. some additional capability information alongside the capability ID) would be within the RAN2 specifications and therefore it should be RAN2 decision to conclude on support of this feature. RAN2 has not yet concluded whether to support or not of this feature.*
+
+## 6.2 Solutions using other means
+
+### 6.2.1 Segmentation of capabilities
+
+#### 6.2.1.1 Description
+
+This section describes the segmentation approach to transfer UE capabilities. If the capability size is over 9000 bytes for NR and 8188 bytes for LTE, then capabilities are segmented into smaller pieces.
+
+#### 6.2.1.2 Signalling for transfer of UE capabilities in segments
+
+A signalling diagram to transfer capabilities in segments is shown in Figure 6.2.1.2-1. In the first step, the eNB/gNB requests capabilities. The UE constructs capabilities and segments the capabilities to the pieces not exceeding the maximum PDCP SDU size. Segments are transmitted to the network by the lower layers. Once the eNB/gNB has received the segments, it recombines the segmented UE radio capability information.
+
+![Signaling diagram of UE capability segmentation. The diagram shows a sequence of messages between a UE and an eNB/gNB. 1. The eNB/gNB sends a decision box 'eNB/gNB decides to enquire the UE radio capability'. 2. An arrow labeled 'UECapabilityEnquiry message' points from the eNB/gNB to the UE. 3. A bracket on the UE side labeled 'complete UE capability' spans multiple outgoing arrows. 4. These arrows are labeled 'UECapabilityInformation message (Segmentation 1)', 'UECapabilityInformation message (Segmentation 2)', '.....', and 'UECapabilityInformation message (Segmentation n)'. 5. All these arrows point to the eNB/gNB. 6. At the eNB/gNB, an arrow points to a box labeled 'eNB/gNB recombines the segmented UE radio capability information'.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg)
+
+Signaling diagram of UE capability segmentation. The diagram shows a sequence of messages between a UE and an eNB/gNB. 1. The eNB/gNB sends a decision box 'eNB/gNB decides to enquire the UE radio capability'. 2. An arrow labeled 'UECapabilityEnquiry message' points from the eNB/gNB to the UE. 3. A bracket on the UE side labeled 'complete UE capability' spans multiple outgoing arrows. 4. These arrows are labeled 'UECapabilityInformation message (Segmentation 1)', 'UECapabilityInformation message (Segmentation 2)', '.....', and 'UECapabilityInformation message (Segmentation n)'. 5. All these arrows point to the eNB/gNB. 6. At the eNB/gNB, an arrow points to a box labeled 'eNB/gNB recombines the segmented UE radio capability information'.
+
+Figure 6.2.1.2-1: Signaling diagram of UE capability segmentation
+
+#### 6.2.1.3 Segmentation structure
+
+##### 6.2.1.3.1 Segmentation at RRC level
+
+In the segmentation of UE capabilities in the RRC level, for each segment, a type (e.g. notLastSegment, lastSegment) as well as a segment number is added. The RRC segmentation can be done in different ways as described below.
+
+Option 1: "hard" split RRC Segmentation:
+
+This approach is similar to ETWS/CMAS in LTE and NR. The total UE radio capability information is encoded as one structure (message or information element) similar to non-segmented case. This is then split into multiple segments in bits. The network can only decode the complete capabilities after assembling all parts, rather than decoding each part.
+
+Option 2: "soft" split RRC Segmentation:
+
+UE radio capability information is encoded separately in parts and carried by multiple messages or information elements (smaller than 9000 bytes for NR or 8188 bytes for LTE). The network can decode and process every segment and combine the content after all the segments are received.
+
+##### 6.2.1.3.2 Segmentation at PDCP level
+
+On the Transmitting side,
+
+1. PDCP segments the huge RRC message (i.e. RRC PDU) into multiple PDCP SDUs;
+2. The size of each PDCP SDU does not exceed 9000bytes for NR or 8188 bytes for LTE;
+3. The last PDCP SDU is tagged with end-marker in the corresponding PDCP PDU header.
+
+![Figure 6.2.1.3.2-1: Illustration of UE capability segmentation at PDCP level. The diagram shows the segmentation of an ASN.1 encoded RRC message into three segments (Segment#1, Segment#2, Segment#3). Each segment is encapsulated into a PDCP PDU (PDCP PDU#1, PDCP PDU#2, PDCP PDU#3). The PDCP PDU headers include an end-marker (E) and a PDCP SN. The last PDCP PDU (PDCP PDU#3) has E=1. The PDCP PDU header structure is shown on the right, with fields for E, R, R, R, and PDCP SN. The MAC layer below shows MAC-i and MAC-i (cont.) for multiple PDUs.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg)
+
+Figure 6.2.1.3.2-1: Illustration of UE capability segmentation at PDCP level. The diagram shows the segmentation of an ASN.1 encoded RRC message into three segments (Segment#1, Segment#2, Segment#3). Each segment is encapsulated into a PDCP PDU (PDCP PDU#1, PDCP PDU#2, PDCP PDU#3). The PDCP PDU headers include an end-marker (E) and a PDCP SN. The last PDCP PDU (PDCP PDU#3) has E=1. The PDCP PDU header structure is shown on the right, with fields for E, R, R, R, and PDCP SN. The MAC layer below shows MAC-i and MAC-i (cont.) for multiple PDUs.
+
+Figure 6.2.1.3.2-1: Illustration of UE capability segmentation at PDCP level
+
+On the Receiving side:
+
+1. PDCP receives and stores the PDCP SDUs;
+2. In PDCP reception buffer, following the in-order delivery principle, UE will reassemble the RRC PDU from the first PDCP SDU to the last PDCP SDU tagged with end-marker.
+  - In the example shown in Figure 6.2.1.3.2-2, SN#2 is the last received PDCP SDU amongst SN#1 to SN#3.
+  - Before receiving PDCP SDU with SN#2, UE does not deliver PDCP SDU with SN#1 to upper layer since it is not tagged with end-marker;
+  - After receiving PDCP SDU with SN#2, UE reassembles the RRC msg#1 from PDCP SDUs with SN#1#2#3;
+3. UE delivers the reassembled RRC message to RRC layer, and delete the associated PDUs.
+
+![Figure 6.2.1.3.2-2: Illustration of concatenation on huge RRC message. The diagram shows the PDCP reception buffer with three PDCP SDUs: SN#1, SN#2 (marked with a red X), and SN#3. Below each SN is an end-marker (E) value: E=0 for SN#1, E=0 for SN#2, and E=1 for SN#3. Arrows from all three SDUs point to a single RRC msg#1, indicating reassembly.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg)
+
+Figure 6.2.1.3.2-2: Illustration of concatenation on huge RRC message. The diagram shows the PDCP reception buffer with three PDCP SDUs: SN#1, SN#2 (marked with a red X), and SN#3. Below each SN is an end-marker (E) value: E=0 for SN#1, E=0 for SN#2, and E=1 for SN#3. Arrows from all three SDUs point to a single RRC msg#1, indicating reassembly.
+
+Figure 6.2.1.3.2-2: Illustration of concatenation on huge RRC message
+
+### 6.2.2 Uplink Capability Signalling Compression (UCSC)
+
+UCSC is a technique to minimize the redundancy in the UE capability information sent by the UE to the network. The NG-RAN informs the UE whether it supports compression in the capability enquiry. Depending on the UE capability to support compression, the UE responds with compressed or uncompressed capability information. A possible candidate for the compression algorithm is DEFLATE. The compression configuration may include the dictionary identifier, when pre-defined dictionaries are used. Capability ID can be used as a dictionary ID.
+
+![Block diagram of UE capability compression operation](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+The diagram illustrates the UE capability compression operation. It consists of a central yellow rectangular block labeled "UCSC (compression)". To the left of this block, a grey arrow points towards it, labeled "Input capability information". To the right of the block, a grey arrow points away from it, labeled "Output compressed capability information".
+
+Block diagram of UE capability compression operation
+
+Figure 6.2.2-1: Block diagram of UE capability compression operation
+
+# 7 Conclusion
+
+## 7.1 Solutions using UE capability Identity
+
+Based on the study, RAN2 recommends that UE capability Identity transfer via NAS signalling, in section 6.1.1.2.2, is introduced in the normative phase. In addition, UE capability ID in *UECapabilityInformation* message should also be supported (only after AS security is activated).
+
+RAN2 also concludes that it is possible for the network to use different filters in different parts of the PLMN. If an ID is assigned by network, then the ID is associated to whatever capabilities the UE has transferred earlier. In context of PLMN assigned ID, the capability ID is unique within a PLMN.
+
+On hash-based ID, RAN2 recommends not to pursue the solution.
+
+On delta signaling with capability ID, RAN2 has not yet concluded whether to support or not of this feature.
+
+## 7.2 Solutions using other means
+
+RAN2 recommends that RRC level segmentation with hard split to be specified in any follow on WI.
+
+# Annex A: Change history
+
+| Change history |              |            |    |     |     |                                                                                 |             |
+|----------------|--------------|------------|----|-----|-----|---------------------------------------------------------------------------------|-------------|
+| Date           | Meeting      | TDoc       | CR | Rev | Cat | Subject/Comment                                                                 | New version |
+| 2018-10        | RAN2 #103bis | R2-1813777 | -  | -   | -   | Skeleton TR                                                                     | 0.0.1       |
+| 2019-03        | RAN2 #105    | R2-1902690 |    |     |     | TR 37.873 v0.1.0 as agreed by RAN2 in email discussion [105#27] after RAN2 #105 | 0.1.0       |
+| 2019-03        | RAN#83       | RP-190296  |    |     |     | Version submitted to RAN#83 for approval                                        | 1.0.0       |
+| 2019-03        | RAN#83       |            |    |     |     | Approved and upgraded to version 16.0.0                                         | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37900/303fadfb9def251d1575d6221199b158_img.jpg b/marked/Rel-16/37_series/37900/303fadfb9def251d1575d6221199b158_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e3d82aa1d3b1c4f51da1c7214f8e6aa43e1e046
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/303fadfb9def251d1575d6221199b158_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f29e259f0324f02e39bec85364a90af721e817f0c546ce97b5ec240ae38c7c15
+size 23410
diff --git a/marked/Rel-16/37_series/37900/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/37_series/37900/523ab7b925beb555f88b2e1e1336974f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..205acb4569d16bba2b69edcaa5fb52a9e1ce48ba
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/523ab7b925beb555f88b2e1e1336974f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb3cd1510350002bc6da101ff3f4d987dbba02cf42fb3e75356ff22a139d896a
+size 30799
diff --git a/marked/Rel-16/37_series/37900/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37900/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01d955e85ce4b36b12507d7a1aa2af028fb68b3a
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3bb8c49c893cfd5d1b755529afd464d0fca4c4d92fe06ebb419bc9ecc7d432e
+size 9482
diff --git a/marked/Rel-16/37_series/37900/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37900/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e77fdb8bc4899d3d15823c584b988bb199351c4d
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c6b5dcd4091123fc6970ed6a090c5987cd0a8a6414a872ebc8d5c00dcf82b85
+size 5726
diff --git a/marked/Rel-16/37_series/37900/6e5a85131eedf6b98db62877ee64506e_img.jpg b/marked/Rel-16/37_series/37900/6e5a85131eedf6b98db62877ee64506e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7dee6e7f0bd8e5298de50451fc46aaddbc140cf2
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/6e5a85131eedf6b98db62877ee64506e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c45844cf9b4ac1bf4fe59fa1331abad56194710160c0aab40afa91fcc1c149a8
+size 37737
diff --git a/marked/Rel-16/37_series/37900/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/37_series/37900/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..17b29ac2a240414ba1c33fa08f64685b87c23fda
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:598eb8887b657c70106c9013cf59bcb7bdaf2d5bb790b79c5f513cd35efd7f37
+size 82784
diff --git a/marked/Rel-16/37_series/37900/c7c1a2a04d07232ca372d3ea08fb19fc_img.jpg b/marked/Rel-16/37_series/37900/c7c1a2a04d07232ca372d3ea08fb19fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eaf407f8f5fc8cdb460bf0ba5541c04809a30b5f
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/c7c1a2a04d07232ca372d3ea08fb19fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5c774a9f6239282ac7971583db5b65fe5c85ba4703a7f6a8d180f38eefd16f14
+size 63219
diff --git a/marked/Rel-16/37_series/37900/df1d0e45191302de72176e4390224c16_img.jpg b/marked/Rel-16/37_series/37900/df1d0e45191302de72176e4390224c16_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab645c5aa22444656b9604432d4a477892d86cb7
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/df1d0e45191302de72176e4390224c16_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68105c03ae84f9954287eb271f5111ac962e05fea4a122121a19162e1b1ff653
+size 49473
diff --git a/marked/Rel-16/37_series/37900/f1091147d93cee4dfa88498610e395a7_img.jpg b/marked/Rel-16/37_series/37900/f1091147d93cee4dfa88498610e395a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f0c8df869c38683a6a65917098810ee23ed1be80
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/f1091147d93cee4dfa88498610e395a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a6186ebaa54921c6b81dccf20647ac31e44fab42e16250b9855e6b4a766b34d0
+size 31555
diff --git a/marked/Rel-16/37_series/37900/raw.md b/marked/Rel-16/37_series/37900/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a599c626c11ff2ecd3cc8299daa3a8dd9c304320
--- /dev/null
+++ b/marked/Rel-16/37_series/37900/raw.md
@@ -0,0 +1,2486 @@
+
+
+# 3GPP TR 37.900 V16.0.0 (2020-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Frequency (RF) requirements for Multicarrier and Multiple Radio Access Technology (Multi-RAT) Base Station (BS) (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. To the right of the "5G" text is a green graphic consisting of three curved lines of increasing length, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. The "3" and "G" are stylized and connected at the bottom by a red horizontal line. Below the "3GPP" text is the phrase "A GLOBAL INITIATIVE" in a smaller, black, sans-serif font. A small ™ trademark symbol is located to the right of the "P" in "3GPP".
+
+3GPP logo
+
+# **3GPP**
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+ Valbonne - FRANCE  
+ Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+# --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+ The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+ All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+ 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+ LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+ GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                                                                                                                     |   |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|
+| Foreword .......................................................................................................................................................................... | 6 |
+| 1 Scope....................................................................................................................................................................... 7    |   |
+| 2 References............................................................................................................................................................... 7       |   |
+| 3 Definitions, symbols and abbreviations ................................................................................................................... 8                      |   |
+| 3.1 Definitions ........................................................................................................................................................ 8          |   |
+| 3.2 Symbols............................................................................................................................................................ 9           |   |
+| 3.3 Abbreviations ................................................................................................................................................. 10              |   |
+| 4 General................................................................................................................................................................... 11     |   |
+| 4.1 Work item objective........................................................................................................................................ 11                  |   |
+| 4.2 Relation to other RAN and GERAN specifications ........................................................................................ 12                                      |   |
+| 4.3 Relationship between minimum requirements and test requirements.............................................................. 12                                                |   |
+| 4.3.1 Relationship for requirements developed for MSR.................................................................................. 12                                          |   |
+| 4.4 Base Station classes........................................................................................................................................ 12                 |   |
+| 4.5 Regional requirements.................................................................................................................................... 13                    |   |
+| 4.6 Manufacturer's declaration ............................................................................................................................. 13                     |   |
+| 5 Multi-Standard Radio scenarios............................................................................................................................. 14                    |   |
+| 5.1 Definitions ...................................................................................................................................................... 14           |   |
+| 5.1.1 Frequency bands and arrangements.......................................................................................................... 14                                 |   |
+| 5.1.1.1 General.................................................................................................................................................. 14                |   |
+| 5.1.1.2 Frequency bands ................................................................................................................................... 14                      |   |
+| 5.1.1.3 Channel spacing.................................................................................................................................... 15                      |   |
+| 5.1.1.4 Channel raster ....................................................................................................................................... 15                   |   |
+| 5.1.1.5 Carrier frequency and channel numbers ............................................................................................... 15                                    |   |
+| 5.1.2 RF bandwidth in MSR specification ........................................................................................................ 16                                 |   |
+| 5.2 FDD multi-RAT and multicarrier scenarios.................................................................................................... 17                                 |   |
+| 5.2.1 Band category 1 scenarios (BC1)............................................................................................................. 18                               |   |
+| 5.2.2 Band category 2 scenarios (BC2)............................................................................................................. 18                               |   |
+| 5.3 TDD multi-RAT and multicarrier scenarios ................................................................................................... 18                                 |   |
+| 5.3.1 Band category 3 scenarios (1.28 Mcps UTRA TDD and E-UTRA TDD)............................................... 18                                                               |   |
+| 5.3.2 F <sub>offset, RAT</sub> of band category 3 ................................................................................................................. 19              |   |
+| 6 Transmitter characteristics ..................................................................................................................................... 19              |   |
+| 6.1 General ........................................................................................................................................................... 19          |   |
+| 6.2 Base Station output power.............................................................................................................................. 20                      |   |
+| 6.3 Output power dynamics ................................................................................................................................. 21                      |   |
+| 6.4 Transmit ON/OFF power ............................................................................................................................... 21                        |   |
+| 6.4.1 Transmitter OFF power ........................................................................................................................... 21                          |   |
+| 6.4.2 Transmitter transient period ..................................................................................................................... 22                         |   |
+| 6.5 Transmitted signal quality............................................................................................................................... 22                    |   |
+| 6.5.1 Modulation quality ................................................................................................................................... 22                     |   |
+| 6.5.2 Frequency error ........................................................................................................................................ 22                   |   |
+| 6.5.2.1 Minimum requirement .......................................................................................................................... 23                           |   |
+| 6.6 Unwanted emissions....................................................................................................................................... 23                    |   |
+| 6.6.1 Operating band unwanted emissions ........................................................................................................ 23                                 |   |
+| 6.6.1.1 Existing regulatory requirements.......................................................................................................... 23                               |   |
+| 6.6.1.1.1 FCC requirements ............................................................................................................................. 23                         |   |
+| 6.6.1.1.2 WAPECS requirements for Europe................................................................................................... 23                                      |   |
+| 6.6.1.1.3 Co-existence with services in adjacent frequency bands .................................................................. 24                                              |   |
+| 6.6.1.2 Application of necessary bandwidth..................................................................................................... 24                                  |   |
+| 6.6.1.3 RF bandwidth scenarios........................................................................................................................ 25                           |   |
+| 6.6.1.4 Derivation of requirement..................................................................................................................... 25                           |   |
+| 6.6.1.4.1 Requirement for band category 1 ...................................................................................................... 25                                 |   |
+| 6.6.1.4.2 Requirement for band category 2 ...................................................................................................... 26                                 |   |
+| 6.6.1.5 Minimum requirement (band category 1).............................................................................................. 27                                      |   |
+
+|           |                                                            |    |
+|-----------|------------------------------------------------------------|----|
+| 6.6.1.6   | Minimum requirement (band category 2) .....                | 28 |
+| 6.6.1.7   | Additional requirements (BC1 and BC2) .....                | 29 |
+| 6.6.1.8   | Minimum requirement (band category 3) .....                | 29 |
+| 6.6.1.9   | Additional requirement (BC3) .....                         | 30 |
+| 6.6.2     | Transmitter spurious emissions .....                       | 30 |
+| 6.6.2.1   | Band category 1 .....                                      | 31 |
+| 6.6.2.1.1 | Mandatory requirements .....                               | 31 |
+| 6.6.2.1.2 | Co-existence in the same geographical area .....           | 31 |
+| 6.6.2.1.3 | Co-location .....                                          | 32 |
+| 6.6.2.1.4 | Protection of the BS receiver of own or different BS ..... | 33 |
+| 6.6.2.2   | Band category 2 .....                                      | 34 |
+| 6.6.2.2.1 | Mandatory requirements .....                               | 34 |
+| 6.6.2.2.2 | Co-existence in the same geographical area .....           | 34 |
+| 6.6.2.2.3 | Co-location .....                                          | 35 |
+| 6.6.2.2.4 | Protection of the BS receiver of own or different BS ..... | 35 |
+| 6.6.2.3   | Band category 3 .....                                      | 35 |
+| 6.6.2.3.1 | Mandatory requirements .....                               | 35 |
+| 6.6.2.3.2 | Co-existence in the same geographical area .....           | 35 |
+| 6.6.2.3.3 | Co-location .....                                          | 36 |
+| 6.6.3     | Occupied bandwidth .....                                   | 36 |
+| 6.6.3.1   | Definition .....                                           | 36 |
+| 6.6.3.2   | Minimum requirement .....                                  | 36 |
+| 6.6.4     | Adjacent Channel Leakage Ratio (ACLR) .....                | 36 |
+| 6.7       | Transmitter intermodulation .....                          | 37 |
+| 6.7.1     | Minimum requirement .....                                  | 37 |
+| 7         | Receiver characteristics .....                             | 39 |
+| 7.1       | General .....                                              | 39 |
+| 7.2       | Reference sensitivity level .....                          | 39 |
+| 7.2.1     | Minimum requirement .....                                  | 40 |
+| 7.3       | Dynamic range .....                                        | 40 |
+| 7.3.1     | Minimum requirement .....                                  | 40 |
+| 7.4       | In-band selectivity and blocking .....                     | 40 |
+| 7.4.1     | Band category 1 .....                                      | 40 |
+| 7.4.1.1   | Blocking .....                                             | 40 |
+| 7.4.1.1.1 | Minimum requirement .....                                  | 41 |
+| 7.4.1.2   | Narrowband blocking .....                                  | 41 |
+| 7.4.1.2.1 | Minimum requirement .....                                  | 41 |
+| 7.4.2     | Band category 2 .....                                      | 42 |
+| 7.4.2.1   | Blocking requirement .....                                 | 42 |
+| 7.4.2.1.1 | Minimum requirement .....                                  | 42 |
+| 7.4.2.2   | Narrowband blocking .....                                  | 42 |
+| 7.4.2.2.1 | Minimum requirement .....                                  | 43 |
+| 7.4.3     | band category 3 .....                                      | 43 |
+| 7.4.3.1   | Blocking .....                                             | 43 |
+| 7.4.3.1.1 | Minimum requirement .....                                  | 43 |
+| 7.4.3.2   | Narrowband blocking .....                                  | 44 |
+| 7.4.3.2.1 | Minimum requirement .....                                  | 44 |
+| 7.5       | Out-of-band blocking .....                                 | 45 |
+| 7.5.1     | Band category 1 .....                                      | 45 |
+| 7.5.1.1   | General “out-of-band” blocking .....                       | 45 |
+| 7.5.1.2   | Co-location .....                                          | 45 |
+| 7.5.2     | Band category 2 .....                                      | 46 |
+| 7.5.2.1   | General “out-of-band” blocking .....                       | 46 |
+| 7.5.2.2   | Co-location .....                                          | 46 |
+| 7.5.3     | Band category 3 .....                                      | 47 |
+| 7.5.3.1   | General “out-of-band” blocking .....                       | 47 |
+| 7.5.3.2   | Co-location .....                                          | 47 |
+| 7.6       | Receiver spurious emissions .....                          | 47 |
+| 7.6.1     | Band category 1 .....                                      | 48 |
+| 7.6.1.1   | Minimum requirement (BC1) .....                            | 48 |
+| 7.6.2     | Band category 2 .....                                      | 48 |
+
+|                 |                                                          |           |
+|-----------------|----------------------------------------------------------|-----------|
+| 7.6.2.1         | Minimum requirement (BC2) .....                          | 49        |
+| 7.6.3           | Band category 3 .....                                    | 49        |
+| 7.6.3.1         | Minimum requirement (BC3) .....                          | 49        |
+| 7.7             | Receiver intermodulation .....                           | 50        |
+| 7.7.1           | Band category 1 .....                                    | 50        |
+| 7.7.1.1         | Intermodulation requirement .....                        | 50        |
+| 7.7.1.1.1       | Minimum requirement.....                                 | 50        |
+| 7.7.1.2         | Narrowband intermodulation .....                         | 51        |
+| 7.7.1.2.1       | Minimum requirement.....                                 | 51        |
+| 7.7.2           | Band category 2 .....                                    | 52        |
+| 7.7.2.1         | Intermodulation requirement .....                        | 52        |
+| 7.7.2.1.1       | Minimum requirement.....                                 | 52        |
+| 7.7.2.2         | Narrowband intermodulation .....                         | 53        |
+| 7.7.2.2.1       | Minimum requirement.....                                 | 53        |
+| 7.7.3           | Band category 3 .....                                    | 54        |
+| 7.7.3.1         | Intermodulation requirement .....                        | 54        |
+| 7.7.3.1.1       | Minimum requirement.....                                 | 55        |
+| 7.7.3.2         | Narrowband intermodulation .....                         | 55        |
+| 7.7.3.2.1       | Minimum requirement.....                                 | 56        |
+| 7.8             | In-channel selectivity .....                             | 57        |
+| 7.8.1           | Minimum requirement.....                                 | 57        |
+| 8               | Other requirements.....                                  | 57        |
+| 8.1             | EMC .....                                                | 57        |
+| 8.2             | Performance requirements.....                            | 57        |
+| 9               | Test specification .....                                 | 58        |
+| 9.1             | BS test configurations .....                             | 58        |
+| 9.1.1           | Definition of Capability Sets (CS) .....                 | 58        |
+| 9.1.2           | Definition of Test Configurations (TC).....              | 59        |
+| 9.1.3           | Mapping from test requirement to test configuration..... | 59        |
+| <b>Annex A:</b> | <b>Characteristics of interfering signals.....</b>       | <b>71</b> |
+| A.1             | UTRA interfering signal .....                            | 71        |
+| A.2             | E-UTRA interfering signal.....                           | 71        |
+| <b>Annex B:</b> | <b>Change history .....</b>                              | <b>72</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is the technical report for the work item on Multi-Standard Radio (MSR), which was approved at TSG RAN#41. The objective of the WI is to first identify relevant scenarios and then write an RF requirements specification that is applicable to Multi-Standard Radio (MSR) Base Station with multiple carriers and/or multiple 3GPP Radio Access Technologies (RAT).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
+- [3] 3GPP TS 25.105: "Base Station (BS) radio transmission and reception (TDD)".
+- [4] 3GPP TS 36.104: "Base Station (BS) radio transmission and reception".
+- [5] 3GPP TS 45.005: "Radio transmission and reception".
+- [6] ITU-R SM.329-10 Recommendation, "Unwanted emissions in the spurious domain".
+- [7] 3GPP TR 25.942: "Radio Frequency (RF) system scenarios".
+- [8] R4-99997, "BS Spurious Emission Requirements for Co-Existence UTRA-FDD/ UTRA-TDD and for Protection of BS receiver in TS 25.104" (Ericsson).
+- [9] RP-020781, "FDD – GSM co-existence in the Same Geographic Area", CR149 to TS 25.104 (RAN WG4).
+- [10] RP-030214, "General corrections on co-existence and co-location requirements for UTRA-FDD BS", CR191 to TS25.104 (RAN WG4).
+- [11] "Title 47 of the Code of Federal Regulations (CFR)", Federal Communications Commission.
+- [12] 3GPP TR 36.804: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception".
+- [13] "Commission Decision of 13 June 2008 on the harmonization of the 2 500-2 690 MHz frequency band for terrestrial systems capable of providing electronic communications services in the Community", Decision 2008/477/EC.
+- [14] ETSI TR 102 748: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Impact of the trend towards flexibility in spectrum usage on the principles for drafting Harmonized Standards and the ETSI work programme for Harmonized Standards".
+- [15] CEPT/ERC/Recommendation 74-01E, "Unwanted Emissions In The Spurious Domain" (Hradec Kralove 05) Edition of October, 2005.
+- [16] 3GPP TR 45.050: "Background for Radio Frequency (RF) requirements".
+
+- [17] 3GPP TS 25.141: “Base Station (BS) conformance testing (FDD)”.
+- [18] 3GPP TS 25.142: “Base Station (BS) conformance testing (TDD)”.
+- [19] 3GPP TS 36.141: “Evolved Universal Terrestrial Radio Access (E-UTRA) ; Base Station (BS) conformance testing”.
+- [20] 3GPP TS 51.021: “Base Station System (BSS) equipment specification; Radio aspects”.
+- [21] ITU-R Recommendation M.1545: “Measurement uncertainty as it applies to test limits for the terrestrial component of International Mobile Telecommunications-2000”.
+- [22] ITU-R Recommendation SM.328-11: “Spectra and bandwidth of emissions”.
+- [23] 3GPP TR 36.942”Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Frequency (RF) system scenarios”.
+- [24] 3GPP TS 25.113: “Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)”.
+- [25] 3GPP TS 36.113: “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) and repeater ElectroMagnetic Compatibility (EMC)”.
+- [26] ETSI EN 301 489-8: “ElectroMagnetic Compatibility (EMC) standard for radio equipment and services – Part 8: Specific conditions for GSM Base Stations”.
+- [27] ETSI EN 301 489-23: “ElectroMagnetic Compatibility (EMC) standard for radio equipment and services – Part 23: Specific conditions for IMT-2000 CDMA Direct Spread (UTRA) Base Station (BS) radio, repeater and ancillary equipment”
+- [28] R4-100806, “ LS from ETSI TFES: LS on Spurious emission limits for MCBTS and MSR”.
+- [29] Recommendation ITU-R SM.1539-1: “Variation of the boundary between the out-of-band and spurious domains required for the application of Recommendations ITU-R SM.1541 and ITU-R SM.329” (2001).
+- [30] “Adjacent Band Compatibility between UMTS and Other Services in the 2 GHz Band”, ERC Report 65, Menton, May 1999, revised in Helsinki, November 1999.
+
+Note: The 3GPP meeting contributions referenced above are included with the current document.
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**Band category:** A group of operating bands for which the same MSR scenarios apply
+
+**Base Station RF bandwidth:** The bandwidth in which a Base Station transmits and receives multiple carriers and/or RATs simultaneously
+
+**Base Station RF bandwidth edge:** The frequency of one of the edges of the Base Station RF bandwidth
+
+**Carrier:** The modulated waveform conveying the E-UTRA, UTRA or GSM physical channels
+
+**Channel bandwidth:** The bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
+
+**Carrier power:** The power at the antenna connector in the channel bandwidth of the carrier averaged over at least one subframe for E-UTRA, at least one slot for UTRA and the useful part of the burst for GSM.
+
+**Downlink operating band:** The part of the operating band designated for downlink.
+
+**Lower RF bandwidth edge:** The frequency of the lower edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements
+
+**Maximum Base Station RF bandwidth:** The maximum RF bandwidth supported by a BS within an operating band.
+
+**Maximum carrier power:** Carrier power available at the antenna connector for a specified reference condition.
+
+**Maximum RAT power:** RAT power available at the antenna connector for a specified reference condition.
+
+**Maximum throughput:** The maximum achievable throughput for a reference measurement channel.
+
+**Maximum total output power:** Total output power available at the antenna connector for a specified reference condition.
+
+**Measurement bandwidth:** The bandwidth in which an emission level is specified.
+
+**MSR Base Station:** Base Station characterized by the ability of its receiver and transmitter to process two or more carriers in common active RF components simultaneously in a declared RF bandwidth, where at least one carrier is of a different RAT than the other carrier(s).
+
+**Multi-carrier transmission configuration:** A set of one or more contiguous carriers that a BS is able to transmit simultaneously according to the manufacturer's specification.
+
+**Necessary bandwidth:** The width of the frequency band which is just sufficient to ensure the transmission of information at the rate and with the quality required under specified conditions (as defined in [6]).
+
+**Occupied bandwidth:** The width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage  $\beta/2$  of the total mean power of a given emission.
+
+**Operating band:** A frequency range in which E-UTRA, UTRA or GSM operates (paired or unpaired), that is defined with a specific set of technical requirements.
+
+NOTE: The operating band(s) for a BS is declared by the manufacturer.
+
+**RAT power:** The sum of all carrier powers for all carriers of the same type.
+
+**RRC filtered mean power:** The mean power of a UTRA carrier as measured through a root raised cosine filter with roll-off factor  $\alpha$  and a bandwidth equal to the chip rate of the radio access mode.
+
+NOTE: The RRC filtered mean power of a perfectly modulated UTRA signal is 0.246 dB lower than the mean power of the same signal.
+
+**Throughput:** The number of payload bits successfully received per second for a reference measurement channel in a specified reference condition.
+
+**Total output power:** The sum of all carrier powers for all carriers transmitted by the BS.
+
+**Transmission bandwidth:** Bandwidth of an instantaneous E-UTRA transmission from a UE or BS, measured in Resource Block units.
+
+**Transmission bandwidth configuration:** The highest E-UTRA transmission bandwidth allowed for uplink or downlink in a given channel bandwidth, measured in Resource Block units.
+
+**Uplink operating band:** The part of the operating band designated for uplink.
+
+**Upper RF bandwidth edge:** The frequency of the upper edge of the Base Station RF bandwidth, used as a frequency reference point for transmitter and receiver requirements
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |                 |
+|----------|-----------------|
+| $\alpha$ | Roll-off factor |
+|----------|-----------------|
+
+|                          |                                                                                                                                                                                                                                                        |
+|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $\beta$                  | Percentage of the mean transmitted power emitted outside the occupied bandwidth on the assigned channel                                                                                                                                                |
+| $BW_{\text{Channel}}$    | Channel bandwidth (for E-UTRA)                                                                                                                                                                                                                         |
+| $BW_{\text{Config}}$     | Transmission bandwidth configuration (for E-UTRA), expressed in MHz, where $BW_{\text{Config}} = N_{\text{RB}} \times 180 \text{ kHz}$ in the uplink and $BW_{\text{Config}} = 15 \text{ kHz} + N_{\text{RB}} \times 180 \text{ kHz}$ in the downlink. |
+| $BW_{\text{RF}}$         | Base Station RF bandwidth, where $BW_{\text{RF}} = F_{\text{BW RF,high}} - F_{\text{BW RF,low}}$                                                                                                                                                       |
+| $BW_{\text{RF,max}}$     | Maximum Base Station RF bandwidth                                                                                                                                                                                                                      |
+| $f$                      | Frequency                                                                                                                                                                                                                                              |
+| $\Delta f$               | Separation between the Base Station RF bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency                                                                                                    |
+| $\Delta f_{\text{max}}$  | The largest value of $\Delta f$ used for defining the requirement                                                                                                                                                                                      |
+| $F_{\text{C}}$           | Carrier centre frequency                                                                                                                                                                                                                               |
+| $f_{\text{offset}}$      | Separation between the Base Station RF bandwidth edge frequency and the centre of the measuring filter                                                                                                                                                 |
+| $f_{\text{offset,max}}$  | The maximum value of $f_{\text{offset}}$ used for defining the requirement                                                                                                                                                                             |
+| $F_{\text{BW RF,high}}$  | Upper RF bandwidth edge, where $F_{\text{BW RF,high}} = F_{\text{C,high}} + F_{\text{offset, RAT}}$                                                                                                                                                    |
+| $F_{\text{BW RF,low}}$   | Lower RF bandwidth edge, where $F_{\text{BW RF,low}} = F_{\text{C,low}} - F_{\text{offset, RAT}}$                                                                                                                                                      |
+| $F_{\text{C,high}}$      | Center frequency of the highest transmitted/received carrier.                                                                                                                                                                                          |
+| $F_{\text{C,low}}$       | Center frequency of the lowest transmitted/received carrier.                                                                                                                                                                                           |
+| $F_{\text{offset, RAT}}$ | Frequency offset from $F_{\text{C,high}}$ to the <i>upper RF bandwidth edge</i> or $F_{\text{C,low}}$ to the <i>lower RF bandwidth edge</i> for a specific RAT.                                                                                        |
+| $F_{\text{DL_low}}$      | The lowest frequency of the downlink operating band                                                                                                                                                                                                    |
+| $F_{\text{DL_high}}$     | The highest frequency of the downlink operating band                                                                                                                                                                                                   |
+| $F_{\text{UL_low}}$      | The lowest frequency of the uplink operating band                                                                                                                                                                                                      |
+| $F_{\text{UL_high}}$     | The highest frequency of the uplink operating band                                                                                                                                                                                                     |
+| $N_{\text{RB}}$          | Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA)                                                                                                                                                               |
+| $P_{\text{REFSENS}}$     | Reference Sensitivity power level                                                                                                                                                                                                                      |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|             |                                                |
+|-------------|------------------------------------------------|
+| ACIR        | Adjacent Channel Interference Ratio            |
+| ACLR        | Adjacent Channel Leakage Ratio                 |
+| ACK         | Acknowledgement (in HARQ protocols)            |
+| ACS         | Adjacent Channel Selectivity                   |
+| ARFCN       | Absolute Radio Frequency Channel Number        |
+| AWGN        | Additive White Gaussian Noise                  |
+| BC          | Band Category                                  |
+| BER         | Bit Error Ratio                                |
+| BS          | Base Station                                   |
+| BTS         | Base Transceiver Station                       |
+| CP          | Cyclic prefix                                  |
+| CRC         | Cyclic Redundancy Check                        |
+| CS          | Capability Set                                 |
+| CW          | Continuous Wave                                |
+| DC          | Direct Current                                 |
+| DB-DC-HSDPA | Dual Band Dual Cell HSDPA                      |
+| DC-HSDPA    | Dual Cell HSDPA                                |
+| DTX         | Discontinuous Transmission                     |
+| DTT         | Digital Terrestrial Television                 |
+| EARFCN      | E-UTRA Absolute Radio Frequency Channel Number |
+| EVM         | Error Vector Magnitude                         |
+| FDD         | Frequency Division Duplex                      |
+| FRC         | Fixed Reference Channel                        |
+| GP          | Guard Period (for E-UTRA TDD operation)        |
+| GSM         | Global System for Mobile Communications        |
+| HSDPA       | High Speed Downlink Packet Access              |
+| ICS         | In-Channel Selectivity                         |
+| ITU-R       | Radiocommunication Sector of the ITU           |
+
+|          |                                                         |
+|----------|---------------------------------------------------------|
+| LNA      | Low Noise Amplifier                                     |
+| MC       | Multi-Carrier (in single RAT)                           |
+| MCL      | Minimum Coupling Loss                                   |
+| MCS      | Modulation and Coding Scheme                            |
+| MIMO     | Multiple Input Multiple Output                          |
+| MR       | Multi-RAT                                               |
+| MS       | Mobile Station                                          |
+| MSR      | Multi-standard Radio                                    |
+| OFDM     | Orthogonal Frequency Division Multiplex                 |
+| OOB      | Out-of-band                                             |
+| PA       | Power Amplifier                                         |
+| PHS      | Personal Handyphone System                              |
+| QAM      | Quadrature Amplitude Modulation                         |
+| QPSK     | Quadrature Phase-Shift Keying                           |
+| RAT      | Radio Access Technology                                 |
+| RB       | Resource Block                                          |
+| RF       | Radio Frequency                                         |
+| RMS      | Root Mean Square (value)                                |
+| RS       | Reference Symbol                                        |
+| RX       | Receiver                                                |
+| RRC      | Root Raised Cosine                                      |
+| SC       | Single Carrier                                          |
+| SNR      | Signal-to-Noise Ratio                                   |
+| SR       | single-RAT                                              |
+| TC       | Test Configuration                                      |
+| TDD      | Time Division Duplex                                    |
+| TD-SCDMA | Time Division Synchronous Code Division Multiple Access |
+| TX       | Transmitter                                             |
+| UARFCN   | UTRA Absolute Radio Frequency Channel Number            |
+| UE       | User Equipment                                          |
+
+# --- 4 General
+
+## 4.1 Work item objective
+
+The objective the TSG RAN Work Item is to first identify relevant scenarios and then write an RF requirements specification that is applicable to Multi-Standard Radio (MSR) Base Station with multiple carriers and/or multiple 3GPP Radio Access Technologies (RAT), according to the following:
+
+- The new specification will cover RF requirements for GSM, UTRA, and E-UTRA (both FDD and TDD modes), for relevant single and multicarrier scenarios and will take into account the regulatory framework in different regions.
+- The new specification will include BS transmission and reception requirements, but no baseband performance requirements.
+- Existing RF specifications will remain and be applicable within their current scope.
+- For a multi-RAT/multi-carrier Base Station, the new RF requirements specification will be applicable for that equipment, together with the baseband requirements of the relevant existing specifications.
+
+The objective of the TSG GERAN Work Task is to support the RAN4 Work Item Building Block, which has the objective to first identify relevant technology migration scenarios and then write an RF requirements specification that is applicable to Multi-Standard Radio (MSR) Base Station.
+
+The Work Task will review the GERAN relevant parts and prepare input for adapting the existing GERAN requirements to an MSR specification with a goal to minimize changes to these requirements.
+
+## 4.2 Relation to other RAN and GERAN specifications
+
+The requirements for MSR are in most parts specified in the present document, while many requirements are also specified through normative references to the respective single-RAT specifications in [2], [3], [4] and [5]. The resulting set of requirements for an MSR BS can be divided into three types, depending on their relation to the single-RAT specifications:
+
+1. **Generic MSR requirement:** A common generic requirement is specified in the present document that applies for all RATs and for BS configured for both multi-RAT and single-RAT operation. In some cases, there are additional requirement(s) that apply only in some Band Category. There are no references to the single-RAT specifications.
+2. **Generic MSR requirement, with additional single-RAT requirements:** A common generic requirement is specified in the present document which applies as in point 1. In addition some single RAT requirement(s) apply, included by normative reference(s) to the single-RAT specification(s).
+3. **Single-RAT only requirements:** In this case, no common generic requirement is defined. The existing single-RAT requirement applies for each RAT, included by normative reference(s) to the single-RAT specification(s).
+
+## 4.3 Relationship between minimum requirements and test requirements
+
+For UTRA and E-UTRA, the Minimum Requirements given in the core specifications [2][3][4] make no allowance for measurement uncertainty. The test specifications [17][18][19] define Test Tolerances. These Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the Minimum Requirements in the core specifications to create Test Requirements.
+
+For some regulatory requirements taken directly from international or regional recommendations or other regulatory references, the test tolerance is set to zero. This concerns the requirements for Spurious emissions and Operating band unwanted emissions.
+
+The measurement results returned by the Test System are compared – without any modification – against the Test Requirements as defined by the shared risk principle. The Shared Risk principle is defined in ITU-R M.1545 [21].
+
+For GSM, the shared risk principle is also applied, with the test requirement in TS 51.021 [20] normally being the same as the requirement defined in the core specification [5].
+
+### 4.3.1 Relationship for requirements developed for MSR
+
+For the minimum requirements developed in the present Technical Report with the purpose to set MSR multi-RAT requirements in the MSR specification, no allowance is given for measurement uncertainty. For the test specification, test Tolerances will be individually calculated for each test and be used to relax the Minimum Requirements in the core specification to create Test Requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero.
+
+For MSR single-RAT requirements, the principle used to define the test requirement remains from the existing specifications.
+
+For both MSR single-RAT and multi-RAT requirements, the measurement results returned by the Test System are compared – without any modification – against the Test Requirements as defined by the shared risk principle.
+
+## 4.4 Base Station classes
+
+The requirements presented in this TR apply to MSR Base Stations intended for general purpose applications. MSR BS requirements for general purpose applications will be based on Wide Area scenarios.
+
+For GSM operation of an MSR BS, a BS intended for general purpose applications corresponds to a normal BTS, including Multicarrier BTS classes. MSR requirements for multi-RAT operation only apply for the highest GSM static power step.
+
+Other Base Station classes are for further study. The requirements for these may be different than those for general purpose applications, or not applicable at all.
+
+## 4.5 Regional requirements
+
+Some requirements in the present document may only apply in certain regions either as optional requirements, or set by local and regional regulation as mandatory requirements. It is normally not stated in the 3GPP specifications under what exact circumstances that the requirements apply, since this is defined by local or regional regulation.
+
+Table 4.5-1 lists all requirements for the MSR specification that may be applied differently in different regions. There are additional regional requirements that may apply for single-RAT operation of an MSR BS. These are listed in the specification for the RATs concerned [2][3][4][5].
+
+**Table 4.5-1: List of regional requirements**
+
+| Clause number                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Requirement                                                     | Comments                                                                                                                                                                                                                                                                                          |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 5.1.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Frequency bands and arrangements                                | Some bands may be applied regionally.                                                                                                                                                                                                                                                             |
+| 6.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Base Station output power                                       | The limit on the rated output power declared by the manufacturer applies in Japan for an E-UTRA BS operating in band 34.                                                                                                                                                                          |
+| 6.6.1.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Existing regulatory requirements (UEM)                          | Regulatory requirements may apply regionally.                                                                                                                                                                                                                                                     |
+| 6.6.1.7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Additional requirements (UEM)                                   | The BS may have to comply with the applicable emission limits established by FCC Title 47 [11], when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer..                                                                                  |
+| 6.6.1.9                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Additional requirement (BC3)                                    | The requirements for unsynchronized TDD co-existence may apply regionally                                                                                                                                                                                                                         |
+| 6.6.2.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Mandatory requirements (spurious emissions)                     | Category A limits are mandatory for regions where Category A limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. Category B limits are mandatory for regions where Category B limits for spurious emissions, as defined in ITU-R Recommendation SM.329 [2] apply. |
+| 6.6.2.1.2,<br>6.6.2.2.2,<br>6.6.2.3.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Co-existence in the same geographical area (spurious emissions) | These requirements may be applied for the protection of system operating in frequency ranges other than the MSR BS operating band. (Note 1)                                                                                                                                                       |
+| 6.6.2.1.3,<br>6.6.2.2.3,<br>6.6.2.3.3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Co-location (spurious emissions)                                | These requirements may be applied for the protection of other BS receivers when a BS operating in another frequency band is co-located with an MSR BS.                                                                                                                                            |
+| 6.6.3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Occupied bandwidth                                              | The requirement may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition.                                                                                                                                                 |
+| 7.5.1.2,<br>7.5.2.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Co-location (blocking)                                          | These requirements may be applied for the protection of the BS receiver when a BS operating in another frequency band is co-located with an MSR BS.                                                                                                                                               |
+| NOTE 1: These requirements may be applied for the protection of system operating in frequency ranges other than the BS downlink operating band. The limits may apply as an optional protection of such systems that are deployed in the same geographical area as the BS, or they may be set by local or regional regulation as a mandatory requirement for an operating band. It is in some cases not stated in the present document whether a requirement is mandatory or under what exact circumstances that a limit applies, since this is set by local or regional regulation. |                                                                 |                                                                                                                                                                                                                                                                                                   |
+
+## 4.6 Manufacturer's declaration
+
+The manufacturer shall declare the following parameters depending on the supported RATs:
+
+General parameters:
+
+- Supported band(s)
+- The maximum RF bandwidth supported by a MSR BS within an operating band
+- The rated total output power as a sum over all RATs
+- Maximum supported power difference between carriers
+
+- Total number of supported carriers
+
+GSM specific parameters:
+
+- Whether the MSR BS supports GSM carriers
+- The maximum number of supported GSM carriers
+- The maximum RF bandwidth supported by the MSR BS when configured with GSM carriers only
+- The rated output power for GSM as a sum of all GSM carriers
+- The rated output power per GSM carrier
+
+UTRA specific parameters:
+
+- Whether the MSR BS supports UTRA carriers
+- The maximum number of supported UTRA carriers
+- The maximum RF bandwidth supported by the MSR BS when configured with UTRA carriers only
+- The rated output power for UTRA as a sum of all UTRA carriers
+- The rated output power per UTRA carrier
+
+E-UTRA specific parameters:
+
+- Whether the MSR BS supports E-UTRA carriers
+- Which of the E-UTRA channel bandwidths specified in TS36.104 subclause 5.6 are supported
+- The maximum number of supported E-UTRA carriers
+- The maximum RF bandwidth supported by the MSR BS when configured with E-UTRA carriers only
+- The rated output power for E-UTRA as a sum of all E-UTRA carriers
+- The rated output power per E-UTRA carrier
+
+# --- 5 Multi-Standard Radio scenarios
+
+## 5.1 Definitions
+
+### 5.1.1 Frequency bands and arrangements
+
+#### 5.1.1.1 General
+
+The channel arrangements presented in this clause are based on the operating bands and channel bandwidths defined in the present release of specifications [2-5]. E-UTRA related requirements in the present document are specified for the channel bandwidths listed in subclause 5.6 of [4].
+
+NOTE: Other operating bands and channel bandwidths may be considered in future releases.
+
+#### 5.1.1.2 Frequency bands
+
+In the present version of the UTRA specifications, there are 15 operating bands defined for UTRA FDD [2] designated with Roman numerals and 6 operating bands defined for UTRA TDD [3] designated alphabetically.
+
+In the present version of the E-UTRA specifications [4], there are 19 paired and 8 unpaired operating bands defined, all designated with Arabic numerals.
+
+In the present version of the GSM specifications [5], there are 14 operating bands defined, all designated with individual names.
+
+In the context of MSR, the operating bands are grouped into Band Categories (BC). The relation between the operating bands for each RAT and how these are categorized is shown in Table 5.2-1 for the paired bands and in Table 5.3-1 for the unpaired bands. The RAT-specific operating band designations for each operating band remain unchanged for MSR.
+
+#### 5.1.1.3 Channel spacing
+
+The GSM/EDGE carrier spacing is 200 kHz [5].
+
+The nominal UTRA channel spacing is 5 MHz for FDD. The nominal channel spacing is 1.6MHz for 1.28 Mcps UTRA TDD Option (TD-SCDMA). These can be adjusted to optimise performance in a particular deployment scenario [2,3].
+
+In E-UTRA the spacing between carriers will depend on the deployment scenario, the size of the frequency block available and the channel bandwidths. The nominal channel spacing between two adjacent E-UTRA carriers is defined as following:
+
+$$\text{Nominal Channel spacing} = (\text{BW}_{\text{Channel}(1)} + \text{BW}_{\text{Channel}(2)})/2$$
+
+where  $\text{BW}_{\text{Channel}(1)}$  and  $\text{BW}_{\text{Channel}(2)}$  are the channel bandwidths of the two respective E-UTRA carriers. The channel spacing can be adjusted to optimize performance in a particular deployment scenario [4].
+
+#### 5.1.1.4 Channel raster
+
+The GSM/EDGE channel raster is 200 kHz for all bands [5].
+
+The UTRA FDD and TDD channel raster is 200 kHz for all bands, which means that the centre frequency must be an integer multiple of 200 kHz. In addition a number of additional centre frequencies are specified according to [2,3], which means that the centre frequencies for these channels are shifted 100 kHz relative to the general raster.
+
+The E-UTRA channel raster is 100 kHz for all bands, which means that the carrier centre frequency must be an integer multiple of 100 kHz [4].
+
+The channel raster for E-UTRA, UTRA and GSM overlap in such a way that all RATs support a common 200 kHz raster in Band Category 1, 2 and 3. For UTRA and E-UTRA in Band Category 1 and 3, there are also some common carrier frequencies on a 100 kHz raster.
+
+#### 5.1.1.5 Carrier frequency and channel numbers
+
+The GSM/EDGE carrier frequency is designated by the absolute radio frequency channel number (ARFCN) [5]. Channel numbers are defined in a way that is uniquely defined for most operating bands, while there is also a possibility for dynamically mapped ARFCNs in some bands as described in clause 2 of [5].
+
+The UTRA carrier frequency is designated by the UTRA Absolute Radio Frequency Channel Number (UARFCN) [2,3]. Channel numbers are uniquely defined for each operating band (except for Band V and VI) as described in subclause 5.4 of [2]. The UARFCN scheme with unique numbers supports inter-band mobility and inter-RAT inter-working.
+
+The UTRA TDD channel numbers have a one-to-one mapping to the carrier frequency as described in subclause 5.4 of [2]. This implies that in case of operating bands that overlap in frequency, the UARFCN are not uniquely defined for each band. It should be noted that numbering schemes for UTRA FDD and TDD are not coordinated, while both are called UARFCN.
+
+The E-UTRA carrier frequency in the uplink and downlink is designated by the E-UTRA Absolute Radio Frequency Channel Number (EARFCN) [4]. Channel numbers are uniquely defined for each operating band (paired and unpaired) as described in subclause 5.7 of [4]. The EARFCN scheme with unique numbers supports inter-band mobility and inter-RAT inter-working.
+
+In the context of MSR, the frequency numbering scheme for each RAT will remain.
+
+### 5.1.2 RF bandwidth in MSR specification
+
+The following terminology and symbols have been agreed as a basis for MSR RF bandwidth related aspects. This terminology is illustrated in Fig 5.1.2-1.
+
+$F_{C,high}$  Center frequency of the highest transmitted/received carrier.
+
+$F_{C,low}$  Center frequency of the lowest transmitted/received carrier.
+
+$F_{offset, RAT}$  Frequency offset from  $F_{C,high}$  to the *upper RF bandwidth edge* or  $F_{C,low}$  to the *lower RF bandwidth edge* for a specific *RAT*.
+
+**Upper RF bandwidth edge:** The frequency at the upper edge of the RF bandwidth located at  $F_{BW RF,high} = F_{C,high} + F_{offset, RAT}$ . It is used as a frequency reference point for both transmitter and receiver requirements.
+
+**Lower RF bandwidth edge:** The frequency at the lower edge of the RF bandwidth located at  $F_{BW RF,low} = F_{C,low} - F_{offset, RAT}$ . It is used as a frequency reference point for both transmitter and receiver requirements.
+
+**RF bandwidth,  $BW_{RF}$ :** The RF bandwidth in which a Base Station transmits and receives multiple carriers and/or RATs simultaneously,  $BW_{RF} = F_{BW RF,high} - F_{BW RF,low}$ .
+
+**Maximum RF bandwidth,  $BW_{RF,max}$ :** The maximum value for  $BW_{RF}$  supported by the BS within an operating band.
+
+![Diagram illustrating RF bandwidth related symbols within the MSR specification. The diagram shows a horizontal axis labeled 'Frequency'. A central grey bar represents the 'RF bandwidth, BW RF'. Above this bar, three colored segments represent different RATs: 'RAT_low' (red), 'Multiple carriers / RATs' (cyan), and 'RAT_high' (green). Vertical dashed lines indicate the center frequencies 'F_C,low' and 'F_C,high'. The left edge of the RF bandwidth is labeled 'F_BW RF, low' and the right edge is labeled 'F_BW RF, high'. Arrows indicate the frequency offsets 'F offset, RAT_low' and 'F offset, RAT_high' from the center frequencies to the bandwidth edges.](df1d0e45191302de72176e4390224c16_img.jpg)
+
+The diagram shows a horizontal axis labeled 'Frequency'. A central grey bar represents the 'RF bandwidth, BW RF'. Above this bar, three colored segments represent different RATs: 'RAT\_low' (red), 'Multiple carriers / RATs' (cyan), and 'RAT\_high' (green). Vertical dashed lines indicate the center frequencies 'F\_C,low' and 'F\_C,high'. The left edge of the RF bandwidth is labeled 'F\_BW RF, low' and the right edge is labeled 'F\_BW RF, high'. Arrows indicate the frequency offsets 'F offset, RAT\_low' and 'F offset, RAT\_high' from the center frequencies to the bandwidth edges.
+
+Diagram illustrating RF bandwidth related symbols within the MSR specification. The diagram shows a horizontal axis labeled 'Frequency'. A central grey bar represents the 'RF bandwidth, BW RF'. Above this bar, three colored segments represent different RATs: 'RAT\_low' (red), 'Multiple carriers / RATs' (cyan), and 'RAT\_high' (green). Vertical dashed lines indicate the center frequencies 'F\_C,low' and 'F\_C,high'. The left edge of the RF bandwidth is labeled 'F\_BW RF, low' and the right edge is labeled 'F\_BW RF, high'. Arrows indicate the frequency offsets 'F offset, RAT\_low' and 'F offset, RAT\_high' from the center frequencies to the bandwidth edges.
+
+**Fig 5.1.2-1 RF bandwidth related symbols within the MSR specification.**
+
+The above terminology shall be understood as follows:
+
+- The RF bandwidth,  $BW_{RF}$ , corresponds to the active RF bandwidth in a certain deployment scenario. No specific HW capability, such as RF filter BW or RX/TX characteristics (PA operating BW, IF filters, etc.), corresponds directly to this value; it is merely a construct for applying RF requirements to a specific configuration with multiple carriers and/or RATs.  $BW_{RF}$  is not declared by the manufacturer.
+- The Maximum RF bandwidth,  $BW_{RF,max}$ , on the other hand is a BS HW capability and is declared by the manufacturer. Obviously  $BW_{RF} \leq BW_{RF,max}$ .
+- MSR RF bandwidth edges ( $F_{BW RF,high}$  and  $F_{BW RF,low}$ ) serve as frequency reference points for both transmitter and receiver requirements. As an example, the Operating band unwanted emission requirements would start above the upper and below the lower RF bandwidth edges located at  $F_{BW RF,high}$  and  $F_{BW RF,low}$ . The RF bandwidth edge can also be seen as a demarcation frequency between uncoordinated operators and in many scenarios it therefore
+
+coincides with the license block edge, while in other scenarios the license block edge may be located outside or even slightly inside the RF bandwidth.
+
+The rationale for this is as follows. The channel edge within the E-UTRA (UTRA) specifications is assumed to coincide with the license block edge of uncoordinated 3GPP systems. This is a worst-case from an interference point of view and gives the operator the assurance that no additional guard bands need to be reserved to facilitate mutual co-existence of same-band uncoordinated 3GPP systems.
+
+Furthermore, the additional FCC Title 47 requirements [11] applicable at the license block edge, are also included within the E-UTRA (UTRA) specifications, they are however defined in reference to the channel edge.
+
+It seems natural to assume for the MSR RF bandwidth edges ( $F_{BW, RF, high}$  and  $F_{BW, RF, low}$ ) the same role, i.e. to serve as the default demarcation frequency between uncoordinated operators and as a frequency reference point for additional license block edge related regulatory requirements (e.g. FCC Title 47 emission limits [11]). Note however that while serving as a frequency reference point for RF requirements, the RF bandwidth edge may in some scenarios not coincide with the license block edge.
+
+While TS 45.005 [5] uses different concepts for specifying OOB limits and in particular, has no definition corresponding to the E-UTRA (UTRA) channel edge, the above principle is seen also as meaningful for RF scenarios involving uncoordinated GSM systems.
+
+- Values for  $F_{offset, RAT}$  needed in order to meet TX and RX requirements will be part of the MSR specifications.  $F_{offset, RAT}$  will be specific for each RAT in each Band Category.
+
+## 5.2 FDD multi-RAT and multicarrier scenarios
+
+To structure the possible FDD scenarios and resulting requirements, the bands divided into two categories:
+
+- Band category 1: Bands for UTRA FDD and E-UTRA FDD operation
+- Band category 2: Bands for UTRA FDD, E-UTRA FDD and GSM operation
+
+A full set of paired bands and how they are categorized is shown in Table 5.2-1.
+
+**Table 5.2-1: Paired bands in E-UTRA, UTRA and GSM.**
+
+| E-UTRA Band | UTRA Band | GSM Band | Uplink (UL) BS receive<br>UE transmit |              | Downlink (DL) BS transmit<br>UE receive |              | Band category |
+|-------------|-----------|----------|---------------------------------------|--------------|-----------------------------------------|--------------|---------------|
+| 1           | I         | -        | 1920 MHz                              | – 1980 MHz   | 2110 MHz                                | – 2170 MHz   | 1             |
+| 2           | II        | PCS 1900 | 1850 MHz                              | – 1910 MHz   | 1930 MHz                                | – 1990 MHz   | 2             |
+| 3           | III       | DCS 1800 | 1710 MHz                              | – 1785 MHz   | 1805 MHz                                | – 1880 MHz   | 2             |
+| 4           | IV        | -        | 1710 MHz                              | – 1755 MHz   | 2110 MHz                                | – 2155 MHz   | 1             |
+| 5           | V         | GSM 850  | 824 MHz                               | – 849 MHz    | 869 MHz                                 | – 894 MHz    | 2             |
+| 6           | VI        | -        | 830 MHz                               | – 840 MHz    | 875 MHz                                 | – 885 MHz    | 1             |
+| 7           | VII       | -        | 2500 MHz                              | – 2570 MHz   | 2620 MHz                                | – 2690 MHz   | 1             |
+| 8           | VIII      | E-GSM    | 880 MHz                               | – 915 MHz    | 925 MHz                                 | – 960 MHz    | 2             |
+| 9           | IX        | -        | 1749.9 MHz                            | – 1784.9 MHz | 1844.9 MHz                              | – 1879.9 MHz | 1             |
+| 10          | X         | -        | 1710 MHz                              | – 1770 MHz   | 2110 MHz                                | – 2170 MHz   | 1             |
+| 11          | XI        | -        | 1427.9 MHz                            | – 1447.9 MHz | 1475.9 MHz                              | – 1495.9 MHz | 1             |
+| 12          | XII       | -        | 698 MHz                               | – 716 MHz    | 728 MHz                                 | – 746 MHz    | 1             |
+| 13          | XIII      | -        | 777 MHz                               | – 787 MHz    | 746 MHz                                 | – 756 MHz    | 1             |
+| 14          | XIV       | -        | 788 MHz                               | – 798 MHz    | 758 MHz                                 | – 768 MHz    | 1             |
+| ...         |           |          |                                       |              |                                         |              |               |
+| 17          | -         | -        | 704 MHz                               | – 716 MHz    | 734 MHz                                 | – 746 MHz    | 1 *           |
+| 18          | -         | -        | 815 MHz                               | – 830 MHz    | 860 MHz                                 | – 875 MHz    | 1 *           |
+| 19          | XIX       | -        | 830 MHz                               | – 845 MHz    | 875 MHz                                 | – 890 MHz    | 1             |
+| 20          | XX        | -        | 832 MHz                               | – 862 MHz    | 791 MHz                                 | – 821 MHz    | 1             |
+| 21          | XXI       | -        | 1447.9 MHz                            | – 1462.9 MHz | 1495.9 MHz                              | – 1510.9 MHz | 1             |
+
+\* NOTE: The band is for E-UTRA only.
+
+### 5.2.1 Band category 1 scenarios (BC1)
+
+BC1 requirements for receiver and transmitter shall apply with a frequency offset from the lowest and highest carriers to the RF bandwidth edge ( $F_{\text{offset, RAT}}$ ) as defined in Table 5.2.1-1.
+
+**Table 5.2.1-1:  $F_{\text{offset, RAT}}$  for band category 1**
+
+| RAT                      | $F_{\text{offset, RAT}}$                  |
+|--------------------------|-------------------------------------------|
+| 1.4, 3 MHz E-UTRA        | $BW_{\text{Channel}}/2 + 200 \text{ kHz}$ |
+| 5, 10, 15, 20 MHz E-UTRA | $BW_{\text{Channel}}/2$                   |
+| UTRA                     | 2.5 MHz                                   |
+
+### 5.2.2 Band category 2 scenarios (BC2)
+
+BC2 requirements for receiver and transmitter shall apply with a frequency offset from the lowest and highest carriers to the RF bandwidth edge ( $F_{\text{offset, RAT}}$ ) as defined in Table 5.2.2-1.
+
+**Table 5.2.2-1:  $F_{\text{offset, RAT}}$  for band category 2**
+
+| RAT    | $F_{\text{offset, RAT}}$ |
+|--------|--------------------------|
+| E-UTRA | $BW_{\text{Channel}}/2$  |
+| UTRA   | 2.5 MHz                  |
+| GSM    | 200 kHz                  |
+
+## 5.3 TDD multi-RAT and multicarrier scenarios
+
+To structure the possible TDD scenarios and resulting requirements, the unpaired bands are put in a third category:
+
+- Band category 3: Bands for UTRA TDD/TD-SCDMA and E-UTRA TDD operation
+
+A full set of unpaired bands and how they are categorized is shown in Table 5.3-1.
+
+**Table 5.3-1: Unpaired bands in E-UTRA and UTRA.**
+
+| E-UTRA Band | UTRA Band | Uplink (UL) BS receive<br>UE transmit | Downlink (DL) BS transmit<br>UE receive | Band category |
+|-------------|-----------|---------------------------------------|-----------------------------------------|---------------|
+| 33          | a)        | 1900 MHz – 1920 MHz                   | 1900 MHz – 1920 MHz                     | 3             |
+| 34          | a)        | 2010 MHz – 2025 MHz                   | 2010 MHz – 2025 MHz                     | 3             |
+| 35          | b)        | 1850 MHz – 1910 MHz                   | 1850 MHz – 1910 MHz                     | 3             |
+| 36          | b)        | 1930 MHz – 1990 MHz                   | 1930 MHz – 1990 MHz                     | 3             |
+| 37          | c)        | 1910 MHz – 1930 MHz                   | 1910 MHz – 1930 MHz                     | 3             |
+| 38          | d)        | 2570 MHz – 2620 MHz                   | 2570 MHz – 2620 MHz                     | 3             |
+| 39          | f)        | 1880 MHz – 1920 MHz                   | 1880 MHz – 1920 MHz                     | 3             |
+| 40          | e)        | 2300 MHz – 2400 MHz                   | 2300 MHz – 2400 MHz                     | 3             |
+
+### 5.3.1 Band category 3 scenarios (1.28 Mcps UTRA TDD and E-UTRA TDD)
+
+1.28 Mcps UTRA TDD option (TD-SCDMA) and E-UTRA TDD can have multiple uplink and downlink configurations, with TD-SCDMA having UL:DL=5:2, 4:3, 3:4, 2:5 and 1:6 configurations and E-UTRA TDD having UL:DL=3:1, 2:2, 1:3 configurations with 5 ms periodicity. However, due to the mix of bandwidths and technologies sharing common radio resources in MSR, it is difficult for TD-SCDMA and E-UTRA TDD sharing the common RF in arbitrary UL:DL configurations manner. According to the UL:DL configurations with TD-SCDMA and E-UTRA TDD defined in [3] and [2], the interference will be unacceptable if the TD-SCDMA and E-UTRA TDD in 10 ms periodicity co-exist in the same geographical region with co-located and co-sited Base Stations. Furthermore, one UL:DL configuration of E-UTRA TDD with 5 ms periodicity can co-exist with one unique associated UL:DL configuration of TD-SCDMA if they are co-sited or co-located.
+
+![Figure 5.3.1-1: Alignment of TD-SCDMA and E-UTRA TDD. The diagram illustrates the timing alignment between TD-SCDMA and various E-UTRA TDD configurations (UL/DL=3:1, 2:2, 1:3) with different Special Subframe (SF) configurations. It shows how time slots (TS) and special fields like DwPTS, GP, and UpPTS align across the different technologies and configurations over a 10ms period.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+Detailed description: The diagram shows the frame structure for TD-SCDMA at the top, followed by three pairs of E-UTRA TDD configurations. TD-SCDMA has time slots TS6, TS0, DwPTS, GP, UpPTS, TS1, TS2, TS3, TS4, TS5, and TS6. The E-UTRA TDD configurations are grouped by UL/DL ratios: 3:1, 2:2, and 1:3. For each ratio, two SF configurations are shown (e.g., SF 3:9:2 and SF 6:6:2). Vertical dashed lines indicate the alignment points between the TD-SCDMA special fields and the E-UTRA TDD subframes. Color coding is used: light green for DL slots, dark green for UL slots, pink for DwPTS, yellow for GP, and light blue for UpPTS.
+
+Figure 5.3.1-1: Alignment of TD-SCDMA and E-UTRA TDD. The diagram illustrates the timing alignment between TD-SCDMA and various E-UTRA TDD configurations (UL/DL=3:1, 2:2, 1:3) with different Special Subframe (SF) configurations. It shows how time slots (TS) and special fields like DwPTS, GP, and UpPTS align across the different technologies and configurations over a 10ms period.
+
+**Figure 5.3.1-1: Alignment of TD-SCDMA and E-UTRA TDD**
+
+Figure 5.3.1-1 shows that the UL:DL=5:2, 3:4 and 2:5 configurations of TD-SCDMA can coexist with UL:DL= 3:1, 2:2 and 1:3 configurations of E-UTRA TDD respectively. Consider minimizing the interference between the TD-SCDMA and E-UTRA TDD, UL and DL alignment of TD-SCDMA and E-UTRA TDD with 5ms periodicity will be assumed in the initial work stage of MSR; For E-UTRA TDD with 10 ms periodicity and TD-SCDMA deployment scenarios, it might be very difficult to define the RF requirements for the TD-SCDMA and E-UTRA TDD co-existence in MSR mode and this case is left aside at this stage.
+
+For minimizing the interference between the TD-SCDMA and E-UTRA TDD the UL and DL alignment of TD-SCDMA and E-UTRA TDD with 5 ms periodicity shall be assumed. The operating band outlined in Table 5.3-1 shall be considered for the MSR combination of TD-SCDMA and E-UTRA TDD.
+
+### 5.3.2 $F_{\text{offset, RAT}}$ of band category 3
+
+BC3 requirements for receiver and transmitter shall apply with a frequency offset from the lowest and highest carriers to the RF bandwidth edge ( $F_{\text{offset, RAT}}$ ) as defined in Table 5.3.2-1.
+
+**Table 5.3.2-1:  $F_{\text{offset, RAT}}$  for band category 3**
+
+| RAT                      | $F_{\text{offset, RAT}}$                    |
+|--------------------------|---------------------------------------------|
+| 1.4, 3 MHz E-UTRA        | $BW_{\text{Channel}} / 2 + 200 \text{ kHz}$ |
+| 5, 10, 15, 20 MHz E-UTRA | $BW_{\text{Channel}} / 2$                   |
+| 1.28Mcps UTRA TDD option | 1 MHz                                       |
+
+# 6 Transmitter characteristics
+
+## 6.1 General
+
+Unless otherwise stated, the requirements in clause 6 are expressed for a single transmitter antenna connector. In case of transmit diversity, DB-DC-HSDPA or MIMO transmission, the requirements apply for each transmitter antenna connector.
+
+Unless otherwise stated, the transmitter characteristics are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a TX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B).
+
+Unless otherwise stated the requirements in clause 6 applies at all times, i.e. during the Transmitter ON period, the Transmitter OFF period and the Transmitter transient period.
+
+![Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Test port A and Test port B indicated.](523ab7b925beb555f88b2e1e1336974f_img.jpg)
+
+The diagram illustrates the transmitter test ports. It shows a sequence of components connected in series: a 'BS cabinet', an 'External PA (if any)', and an 'External device e.g. TX filter (if any)'. The connections are represented by wavy lines. 'Test port A' is indicated by an arrow pointing to the input of the External PA. 'Test port B' is indicated by an arrow pointing to the output of the External device. To the right of Test port B, a dashed line with an arrow points towards the text 'Towards antenna connector'.
+
+Diagram of transmitter test ports showing a BS cabinet connected to an External PA (if any) and an External device (e.g. TX filter, if any), with Test port A and Test port B indicated.
+
+Figure 6.1-1: Transmitter test ports
+
+Values for  $F_{\text{offset, RAT}}$  to meet transmitter requirements are specific for each RAT in each Band Category as specified in subclause 5.2.1 for Band Category 1, subclause 5.2.2 for Band Category 2 and subclause 5.3.2 for Band Category 3.
+
+## 6.2 Base Station output power
+
+With multiple carriers of the same or of different types the power definition of the BS is slightly more complicated than for a single carrier BS. The declared output power for the BS is defined by:
+
+- **Rated carrier power:** The maximum output power that can be configured for a single carrier.
+- **Rated RAT power:** The maximum sum of the output powers of all carriers belonging to the same RAT that can be configured.
+- **Rated total output power:** The maximum sum of the output power of all transmitted carriers that can be configured.
+
+The measured carrier power is defined in the frequency domain by using a square filter. For E-UTRA the channel bandwidth is specified in [4], for UTRA FDD the bandwidth shall be 5 MHz, for 1.28Mcps UTRA TDD (TD-SCDMA) the bandwidth shall be 1.6 MHz, and for GSM the bandwidth shall be 300kHz. For the time domain the different technologies have employed different averaging times. E-UTRA and UTRA can in principle be averaged over any time interval during the transmitter ON period as long as it is longer than a minimum length. For GSM however the averaging period is synchronised to the burst. For this reason the time period used for averaging should depend on the RAT and use the RAT specific averaging time.
+
+The parameters for manufacturer output power declaration are given in Table 6.2-1.
+
+The valorization of those parameters identifies a multi-dimensional space of possible carrier power combinations according to the rated power, number of supported carriers and rated carrier power for each RAT. It is up to the manufacturer to fill in values, making the valorization of the parameters.
+
+To limit the number of possible carrier power combinations inside the above multi-dimensional space, a parameter defining the maximum supported carrier power difference is declared by the manufacturer.
+
+**Table: 6.2-1: Parameters for manufacturer output power declaration**
+
+| Parameter                                  |                                     | Unit |
+|--------------------------------------------|-------------------------------------|------|
+| Rated total output power                   |                                     | dBm  |
+| Maximum supported carrier power difference |                                     | dB   |
+| E-UTRA                                     | Rated E-UTRA output power           | dBm  |
+|                                            | Number of supported E-UTRA carriers | N    |
+|                                            | Rated carrier power (for E-UTRA)    | dBm  |
+| UTRA                                       | Rated UTRA power                    | dBm  |
+|                                            | Number of supported UTRA carriers   | N    |
+|                                            | Rated carrier power (for UTRA)      | dBm  |
+| GSM                                        | Rated GSM power                     | dBm  |
+|                                            | Number of supported GSM carriers    | N    |
+|                                            | Rated carrier power (for GSM)       | dBm  |
+
+There are BS output power-related single-RAT requirements for E-UTRA and UTRA that will continue to apply as single-RAT requirements:
+
+- For E-UTRA, the minimum requirement for DL RS power in TS 36.104 [4], subclause 6.5.4.
+- For UTRA FDD, the minimum requirements for primary CPICH power in TS 25.104 [2], subclause 6.4.4,
+- For UTRA TDD, the minimum requirements for Primary CCPCH power and Differential accuracy of primary CCPCH power in TS 25.105 [3], subclause 6.4.5 and 6.4.6 respectively.
+- For E-UTRA in Band 34, there is a regional limit on the rated output power declared by the manufacturer. There is no test corresponding to this requirement.
+
+## 6.3 Output power dynamics
+
+Transmit dynamic range performance for UTRA [2] is covered by power control step accuracy requirements, code domain dynamic range requirement dynamic range and total power dynamic range. In GSM [5], there are requirements for static power setting, power control dynamic range requirements and output level dynamic operation. E-UTRA [2] has Resource Element (RE) power control dynamic range requirement and also total power dynamic range where the frequency domain scheduling capability of E-UTRA is captured.
+
+There is no synergy between the different output power dynamic requirements for corresponding RAT. This makes transmit power dynamic range requirement suitable as an MSR single RAT requirement. The existing requirements for each RAT, without any changes, are thus applicable as MSR single RAT requirement.
+
+## 6.4 Transmit ON/OFF power
+
+### 6.4.1 Transmitter OFF power
+
+The transmitter OFF power of UTRA TDD is RRC filtered mean power. It is 0.246dB lower than the mean power. After converting to mean power spectral density, the transmit OFF power of 1.28Mcps UTRA TDD is  $-82\text{dBm} + 0.246\text{dB} - 10\log(1.28) = -82.826\text{dBm/MHz}$ . The transmitter OFF power of LTE TDD is less than  $-85\text{dBm/MHz}$ . Combining the requirements of UTRA and LTE, the stricter requirement is adopted for MSR transmit OFF power.
+
+The transmitter OFF power spectral density shall be less than  $-85\text{dBm/MHz}$ .
+
+### 6.4.2 Transmitter transient period
+
+The OFF power for LTE is averaged over 70 us. The ON power is averaged over 1 ms. However the transmitted signal quality requirements apply during the ON period which prevents too much variation in the on power. The transient time is 17 us for the OFF to ON transition and 17us for the ON to OFF transition.
+
+For UTRA TDD 1.28 Mcps option the OFF power is averaged over one timeslot excluding guard periods which is approximately 675 us. The OFF to ON transition is 8 chips which becomes 6.25 us. The ON to OFF transition period is 85 + 3 chips where the last 3 chips allow for a transition from -42 dBm to the OFF power level. The total duration of this period is approximately 68 us.
+
+Short transition times results in larger possible cell radius and to avoid replanning of networks the most stringent requirements from LTE and UTRA TDD 1.28 Mcps option is adopted.
+
+The OFF power is averaged over 70 us. The duration of the OFF to ON transition is 6.25 us and the ON to OFF duration is 17 us. A schematic overview of the transition periods is given in figure 6.4.1-1
+
+![Figure 6.4.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots' (left), 'Transmitter ON period (DL Timeslots and DwPTS)' (middle), and 'GP and UpPTS' (right). The 'UL Timeslots' and 'GP and UpPTS' segments are shaded with diagonal lines. The 'Transmitter ON period' shows a sharp rise from the OFF power level to the ON power level, followed by a slight dip and then a sharp fall back to the OFF power level. Two double-headed arrows labeled 'Transmitter transient period' indicate the time taken for the power to transition between the ON and OFF levels. Two more double-headed arrows labeled 'Transmitter OFF period' indicate the time intervals where the power is at the OFF level, before the first transient and after the second transient.](c7c1a2a04d07232ca372d3ea08fb19fc_img.jpg)
+
+Figure 6.4.1-1: Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period. The graph shows Transmitter Output Power on the y-axis and Time on the x-axis. The y-axis has two horizontal dashed lines: 'ON power level (Informative)' and 'OFF power level'. The x-axis is divided into three main segments: 'UL Timeslots' (left), 'Transmitter ON period (DL Timeslots and DwPTS)' (middle), and 'GP and UpPTS' (right). The 'UL Timeslots' and 'GP and UpPTS' segments are shaded with diagonal lines. The 'Transmitter ON period' shows a sharp rise from the OFF power level to the ON power level, followed by a slight dip and then a sharp fall back to the OFF power level. Two double-headed arrows labeled 'Transmitter transient period' indicate the time taken for the power to transition between the ON and OFF levels. Two more double-headed arrows labeled 'Transmitter OFF period' indicate the time intervals where the power is at the OFF level, before the first transient and after the second transient.
+
+**Figure 6.4.1-1 Illustration of the relations of transmitter ON period, transmitter OFF period and transmitter transient period.**
+
+## 6.5 Transmitted signal quality
+
+### 6.5.1 Modulation quality
+
+The transmit modulation quality in UTRA is formulated as EVM, PCDE and RCDE (only 64QAM). GSM and E-UTRA have EVM as the measure for signal quality for all supported modulation schemes, except for GMSK in GSM where a phase error requirement is used. Definition and modulation quality limits for each concerned RAT are based on extensive investigations and discussions with considerations for system performance.
+
+The existing RAT specific modulation quality requirements can thus be adopted for MSR, both in terms of definition and requirements limits, while maintaining the present performance. In cases where additional modulation quality requirements are presently defined for a modulation scheme, the need for these is for further study.
+
+### 6.5.2 Frequency error
+
+Frequency error is a measure of the difference between the actual BS transmit frequency and the assigned frequency for any concerned RAT. The same source shall be used for RF frequency and data clock generation.
+
+Due to the very large similarity between E-UTRA, UTRA and GSM frequency error requirements, a common generic requirement can be adopted for MSR BS.
+
+#### 6.5.2.1 Minimum requirement
+
+The modulated carrier frequency of any RAT supported by the BS shall be accurate to within  $\pm 0.05$  ppm observed over a period of one sub-frame for E-UTRA, one time slot for UTRA and across the burst for GSM.
+
+The requirement shall apply for both single RAT and multi-RAT operation.
+
+## 6.6 Unwanted emissions
+
+Unwanted emissions consist of out-of-band emissions and spurious emissions [6]. Out of band emissions are unwanted emissions immediately outside the channel bandwidth resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emission, intermodulation products and frequency conversion products, but exclude out of band emissions.
+
+Spurious emissions limits for MSR BS are treated in subclause 6.6.2. Out-of-band emissions requirement for an MSR BS transmitter is specified in terms of an Operating band unwanted emissions requirement (6.6.1), occupied bandwidth (6.6.3) and ACLR (6.6.4).
+
+### 6.6.1 Operating band unwanted emissions
+
+#### 6.6.1.1 Existing regulatory requirements
+
+Generic “masks” as regulatory requirements exist both in the US (FCC) and in Europe (WAPECS) as block edge mask requirements. The concept with limits related to the RF bandwidth edge that is introduced for the MSR scenarios in subclause 5.1.2 will be compatible with such Block edge masks (BEM), since it applies a frequency block (the RF bandwidth) as a reference for limits, rather than single carriers.
+
+##### 6.6.1.1.1 FCC requirements
+
+The US (FCC) requirements for the relevant BC1 and BC2 bands are in Part 22, 24 and 27 of FCC Title 47 [11]. The requirements in [11] are for UTRA and E-UTRA interpreted as a -13 dBm limit, measured in a 100 kHz measurement bandwidth for the bands below 1GHz (band 5) and in 1 MHz for the bands above 1 GHz (bands 2, 4 and 10). For the 1 MHz frequency range immediately outside the license block, the measurement bandwidth can alternatively be taken as 1% of the emission bandwidth of the fundamental emission of the transmitter (the “-26 dB modulation bandwidth”).
+
+A generic limit based on FCC Title 47 [7], applying to UTRA as well as all channel bandwidths of E-UTRA, would have to be based on the highest channel bandwidth of the deployment case at hand. Basing it in a worst case manner on the 20MHz channel bandwidth would be unnecessarily restrictive for all bandwidths below 20 MHz. The FCC Title 47 requirements will be referenced in the MSR specification as regional “additional requirements”, as explained in subclause 6.6.1.7.
+
+##### 6.6.1.1.2 WAPECS requirements for Europe
+
+There are BEM limits defined in the EC “WAPECS” decision [13] for Band 7. These limits are expressed as EIRP, but are based on the shape of the UTRA spectrum mask taken from TS 25.104 [2]. It is expected that similar limits may be defined for other European bands. In studies performed by ETSI, it was concluded that such BEM limits are licensing conditions that are difficult to include in technical specifications or in 23hanneliza standards [14].
+
+The WAPECS requirements are therefore not explicitly included in the MSR specifications, but the UEM limits can be chosen with the WAPECS requirements in mind.
+
+For Band 20, there are also special out-of-band emissions requirements for UTRA FDD and E-UTRA that apply in Europe for the protection of Digital Terrestrial television (DTT). These should be included as additional operating band unwanted emission limits in the same way as in the single-RAT specifications TS 25.104 [2] and TS 36.104 [4].
+
+##### 6.6.1.1.3 Co-existence with services in adjacent frequency bands
+
+For UTRA FDD, there is a requirement in Clause 6.6.3.6 of TS 25.104 [3] that applies regionally for “Co-existence with services in adjacent frequency bands” in UTRA Bands I, II, III and VII. The requirement provides stricter limits than the UTRA spectrum mask in the frequency range from 5 to 10 MHz from the operating band edges. The requirement is based on an ECC study [30] for co-existence with satellite services in Band 1 and should be restricted to that band.
+
+The same requirement should apply regionally for MSR Base Stations in Band 1. The requirement is for UTRA listed as “spurious emissions”, but is specified for the frequency range of 5-10 MHz from the operating band edges. With the definitions for MSR BS, it consequently falls within the definition of operating band unwanted emissions and can be introduced in the MSR specification as a regional “Additional requirement”, with limits according to Table 6.6.1.1.3-1.
+
+**Table 6.6.1.1.3-1: Additional requirement for protection of adjacent band services**
+
+| UTRA Operating Band | Frequency range | Maximum Level                                        | Measurement Bandwidth |
+|---------------------|-----------------|------------------------------------------------------|-----------------------|
+| 1                   | 2100-2105 MHz   | $-30 + 3.4 \cdot (f - 2100 \text{ MHz}) \text{ dBm}$ | 1 MHz                 |
+|                     | 2175-2180 MHz   | $-30 + 3.4 \cdot (2180 \text{ MHz} - f) \text{ dBm}$ | 1 MHz                 |
+
+#### 6.6.1.2 Application of necessary bandwidth
+
+The boundary between unwanted emissions in the spurious domain and the out-of-band domain is normally defined based on the *necessary bandwidth* of the emission, where the spurious domain generally consists of frequencies separated from the centre frequency of the emission by 250% or more of the necessary bandwidth of the emission.
+
+The necessary bandwidth of a transmission is defined by the ITU-R [6] as “the width of the frequency band which is just sufficient to ensure the transmission of information at the rate and with the quality required under specified conditions. “For UTRA, the necessary bandwidth is set to be 5 MHz and for E-UTRA it is the same as the Channel Bandwidth. In both cases this is also identical to the *occupied bandwidth*.”
+
+In the present version of the international recommendations on spurious emissions, ITU-R SM.329-10 [6] and ERC Rec 74-01 [15], there is no definition of necessary bandwidth related to multi-carrier or multi-RAT transmission for Base Stations. There is a general statement regarding multi-carrier transmission in [6], but it does not apply to Base Stations in the mobile service, making it difficult to set the boundary between the out-of-band and spurious domains for multi-carrier and MSR Base Stations.
+
+This lack of definition has been identified as a shortcoming within the ECC, and the Project Team ECC SE21 has worked on defining the necessary bandwidth and the boundary in case of Multicarrier and multi-RAT transmission as part of an ECC WG SE Work Item to revise ERC Rec 74-01 [15]. The revision is scheduled to be completed in September 2010 and may also later be introduced in ITU-R SM.329 [6].
+
+In an LS from ECC SE21, forwarded to 3GPP through ETSI TFES in [28], the present draft text concerning Multicarrier BS for the “Working document towards the revision of ERC REC 74 01” is provided in an Annex. The revised text provides the following elements of relevance to MSR Base Stations:
+
+- A new *Note 3* is added to *recommends 1* of the draft revision, identifying with reference to satellite transmitters that the radio regulation gives some guidance on multicarrier transmitters and that similar guidance for Multicarrier Base Stations in the Mobile Service is given in Annex 2 of the recommendation
+- A new third clause is added to Annex 2 of the draft revision, giving guidance on the necessary bandwidth for Multicarrier Base Stations. The *transmitter bandwidth* is used as the necessary bandwidth for determining the boundary between the out-of-band and spurious domains, where the transmitter bandwidth is defined as the width of the frequency band covering the envelope of the transmitted carriers. This definition corresponds to the *RF bandwidth* of an MSR Base Station.
+- For determining the boundary between the out-of-band and spurious domains, reference is given to ITU-R SM.1539 [29], with the addition that when applying the recommendation for Multicarrier Base Stations operating up to 6 GHz, the value of the upper threshold value  $B_U$  in Annex 1 of [29] should be  $B_U = 10 \text{ MHz}$ .
+
+The implication of point 2 above is that the necessary bandwidth for an MSR Base Station will be equal to the RF bandwidth. The necessary bandwidth will thus not depend on the bandwidth of the individual carriers transmitted or on the RAT of the carriers, only on the total RF bandwidth.
+
+The implication of point 3 above is that the boundary between the out-of-band and spurious domain will be at least 10 MHz away from the RF bandwidth edges, assuming an RF bandwidth of at least 5 MHz.
+
+Based on the draft revision of ERC Rec 74-01 presented above, the conclusion is that operating band unwanted emission limits defined in such a way that they comply with the spurious emission limits in international recommendations ([6] and [15]) for frequencies separated more than 10 MHz from the RF bandwidth edges, will be in line with those recommendations.
+
+#### 6.6.1.3 RF bandwidth scenarios
+
+From a regulatory point of view, a licensed frequency block can be used for various technologies with different number of carriers and bandwidths. As presented in subclause 6.6.1.1, current regulatory requirements in some regions are based on such a frequency block edge approach. Examples are the FCC Title 47 requirements in the US [11] and requirements in the “WAPECS” decision in Europe [13].
+
+Traditionally, 3GPP RF requirements inside the operating band are defined in relation to a carrier, even though in some cases a simplistic approach is used for some multi-carrier requirements. Introducing MSR will require considerations of a group of carriers transmitted within the RF bandwidth as discussed in subclause 5.1.2 and RF requirements are set relative to the RF bandwidth edges that are defined relative to the outermost carriers by  $F_{\text{offset, RAT}}$ .
+
+The level of requirements should be chosen carefully to maintain the performance of the technologies sharing the same frequency spectrum and radio resources. The possible RF scenarios and the resulting  $F_{\text{offset, RAT}}$  values are presented in subclause 5.2.
+
+Based on those definitions, a generic *Operating band unwanted emissions* requirement can be set in relation to the Base Station RF bandwidth as shown in Figure 6.6.1.3-1. The limit starts from the RF bandwidth edges and is valid irrespective of how many carriers are deployed in the RF bandwidth and of what RAT they are (E-UTRA, UTRA or GSM). The principle of defining the requirement is inherited from E-UTRA, in that it is defined from 10 MHz below the lowest frequency of the downlink operating band up to 10 MHz above the highest frequency of the downlink operating band. The level however is derived from the existing UTRA, E-UTRA and GSM requirements as shown below in subclause 6.6.1.4.
+
+![Figure 6.6.1.3-1: Generic UEM mask principle for MSR. The diagram shows a horizontal axis representing frequency. A central portion is labeled 'RF bandwidth' with a bracket. Above this, a bracket labeled 'One or more carriers E-UTRA, UTRA and/or GSM' spans a grey block, an ellipsis, and a teal block. A dashed line extends from the left edge of the RF bandwidth, and another dashed line extends from the right edge. An arrow labeled 'Operating band unwanted emission limit' points to the right dashed line.](303fadfb9def251d1575d6221199b158_img.jpg)
+
+Figure 6.6.1.3-1: Generic UEM mask principle for MSR. The diagram shows a horizontal axis representing frequency. A central portion is labeled 'RF bandwidth' with a bracket. Above this, a bracket labeled 'One or more carriers E-UTRA, UTRA and/or GSM' spans a grey block, an ellipsis, and a teal block. A dashed line extends from the left edge of the RF bandwidth, and another dashed line extends from the right edge. An arrow labeled 'Operating band unwanted emission limit' points to the right dashed line.
+
+Figure 6.6.1.3-1 Generic UEM mask principle for MSR.
+
+#### 6.6.1.4 Derivation of requirement
+
+##### 6.6.1.4.1 Requirement for band category 1
+
+The generic Operating band unwanted emission limits will be based on the limits for E-UTRA in TS 36.104 [4] and UTRA in TS 25.104 [2]. When comparing those limits for a General Purpose/Wide Area BS (output power  $\geq 43$  dBm), it turns out that the UTRA mask is more stringent in all cases except one. This exception is for the E-UTRA mask for Category B spurious emissions, bands above 1 GHz and offsets  $> 10$  MHz. Here, the E-UTRA mask is based on the spurious domain limit of  $-15$  dBm/MHz, which is stricter than the  $-13$  dBm/MHz of the UTRA mask. This stricter limit is taken for both Category A and B as well as for bands above and below 1 GHz in order to make the requirement generic.
+
+Note that  $f\_offset$  and  $\Delta f$  are defined for UTRA [2] in relation to the carrier centre, while the generic requirement developed for MSR defines  $f\_offset$  and  $\Delta f$  in relation to the Base Station RF bandwidth edge, which for UTRA is identical to the channel edge of the carrier. For this reason, all offsets for MSR are reduced with 2.5 MHz (half the UTRA channel bandwidth) compared to the offsets in [2].
+
+The current UTRA emission mask in TS 25.104 [2] is defined as a single carrier requirement, while the generic MSR mask is a multi-carrier/multi-RAT requirement. This makes the generic mask for the scenarios above more stringent than the current requirements for both UTRA and E-UTRA. Since the mask is in general more stringent than the existing ones, it should not pose any increase in interference but rather a reduction. This also excludes the need for additional co-existence studies.
+
+The UMTS mask results in higher ACLR values than the limits specified for both UTRA and E-UTRA. ACLR requirements will thus be implicitly met by the UEM. If needed, ACLR limits can be defined as additional regional requirements or added as an informative Annex.
+
+##### 6.6.1.4.2 Requirement for band category 2
+
+For Band Category 2, there is a range of existing operator scenarios that are supported by today's GSM specification. These include scenarios where a GSM carrier needs to be placed as close as 200 kHz from the RF bandwidth edge. In order to support these scenarios, the following principles are used for deriving a requirement:
+
+1.  $F_{offset, RAT}=200$  kHz for GSM (see subclause 5.2.2). The number supports scenarios with two operators deploying GSM with a carrier spacing (centre-to-centre) of 400 kHz. Based on the existing operator scenarios and the GSM modulation spectrum, this is the smallest known carrier spacing possible to deploy.
+2. The baseline level for the UEM in BC2 is the BC1 mask (Table 6.6.1.5-1), which in turn was based on the UTRA spectrum emission mask (derived for a 43 dBm carrier). Hence the UEM chosen is fundamentally generic for BC1 and BC2 and will be applicable for all multi-RAT combinations that include a UTRA or E-UTRA signal (with the exception expressed in point 4), or both. The mask is not applicable for single-RAT GSM transmission.
+3. When a GSM carrier is operated with  $F_{offset, GSM}=200$  kHz from the RF bandwidth edge, a modification will be needed from the UTRA mask level as shown in Figure 6.6.1.4.2-1. The reason is that the GSM modulation spectrum will exceed the UTRA mask levels for the first  $\sim 150$  kHz outside the RF bandwidth edge. The modified part of the mask will have the shape of the 8PSK mask (TS45.005 [5] Clause 4.2.1 case a2) for 8PSK and Figure A.2b) in this frequency range, derived for 43 dBm GSM carrier. Since the UEM is based on a fixed 43 dBm carrier power, giving a mask that is independent of the carrier power, the UEM for BC2 in the 0 to 150 kHz frequency range will be more strict than the existing GSM spectrum mask for GSM carriers with an output power exceeding 43 dBm.
+4. When an E-UTRA carrier of 1.4 or 3 MHz channel bandwidth is operated adjacent to the RF bandwidth edge a modified level is also needed for E-UTRA requirements derived with  $F_{offset, E-UTRA}=BW_{Channel}/2$ . The same modification as derived for GSM will be applied for this scenario.
+5. The requirements for Spectrum due to the modulation and wide band noise and intra BTS intermodulation of existing GSM multi-carrier BTS will be applied to MSR Base Station of BC2 for GSM single RAT operation.
+
+![Figure 6.6.1.4.2-1: UEM for BC2 in a GSM scenario. The diagram shows two power spectral density masks relative to an RF bandwidth edge (indicated by a vertical dashed blue line). The 8PSK mask (blue line) starts at P_out = 43 dBm at the edge and has a flat region at +5 dBm/30 kHz. The UTRA mask (red line) also starts at P_out = 43 dBm at the edge and has a flat region at -14 dBm/30 kHz. A 200 kHz offset is shown between the RF bandwidth edge and the start of the masks. A 150 kHz offset is shown between the RF bandwidth edge and the start of the flat regions of the masks.](6e5a85131eedf6b98db62877ee64506e_img.jpg)
+
+Figure 6.6.1.4.2-1: UEM for BC2 in a GSM scenario. The diagram shows two power spectral density masks relative to an RF bandwidth edge (indicated by a vertical dashed blue line). The 8PSK mask (blue line) starts at P\_out = 43 dBm at the edge and has a flat region at +5 dBm/30 kHz. The UTRA mask (red line) also starts at P\_out = 43 dBm at the edge and has a flat region at -14 dBm/30 kHz. A 200 kHz offset is shown between the RF bandwidth edge and the start of the masks. A 150 kHz offset is shown between the RF bandwidth edge and the start of the flat regions of the masks.
+
+**Figure 6.6.1.4.2-1: UEM for BC2 in a GSM scenario with  $F_{\text{offset, RAT}}=200$  kHz, based on the UTRA mask (red) and a modified level based on an 8PSK GSM mask (blue addition)**
+
+#### 6.6.1.5 Minimum requirement (band category 1)
+
+Operating band unwanted emission requirements are defined above the upper and below the lower RF bandwidth edge located at  $F_{\text{BW RF,high}}$ , respectively  $F_{\text{BW RF,low}}$  and shall apply within the downlink operating band and in addition the frequency ranges 10 MHz above and 10 MHz below this band. Unwanted emissions outside this frequency range shall be limited by spurious emissions requirements.
+
+The requirements shall apply whatever the type of transmitter considered (single RAT or multi-RAT, single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification.
+
+The requirements shall apply with values for  $F_{\text{offset, RAT}}$  as specified in Table 5.2.1-1.
+
+Emissions shall not exceed the maximum levels specified in the tables below, where:
+
+- $\Delta f$  is the separation between the *RF bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f_{\text{offset}}$  is the separation between the *RF bandwidth edge* frequency and the centre of the measuring filter.
+- $f_{\text{offset,max}}$  is the offset to the frequency 10 MHz outside the downlink operating band.
+- $\Delta f_{\text{max}}$  is equal to  $f_{\text{offset,max}}$  minus half of the bandwidth of the measuring filter.
+
+Since the limits are to a large part based on regulatory requirements, the test tolerance shall be zero when deriving the test requirement for Operating band unwanted emissions.
+
+**Table 6.6.1.5-1: Operating band unwanted emission mask (UEM) for BC1**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$            | Frequency offset of measurement filter centre frequency, $f\_offset$        | Minimum requirement                                                                         | Measurement bandwidth (Note 2) |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------|
+| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$                          | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$                      | -14 dBm                                                                                     | 30 kHz                         |
+| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$                          | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$                      | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz                         |
+| (Note 1)                                                                 | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$                        | -26 dBm                                                                                     | 30 kHz                         |
+| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -13 dBm                                                                                     | 1 MHz                          |
+| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$                      | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                        | -15 dBm (Note 3)                                                                            | 1 MHz                          |
+
+NOTE 1: This frequency range ensures that the range of values of  $f\_offset$  is continuous.
+
+NOTE 2: As a general rule for the requirements in subclause 6.6.1.3, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth.
+
+NOTE 3: The requirement is not applicable when  $\Delta f_{\max} < 10 \text{ MHz}$ .
+
+#### 6.6.1.6 Minimum requirement (band category 2)
+
+Operating band unwanted emission requirements are defined above the upper and below the lower RF bandwidth edge located at  $F_{\text{BW RF,high}}$ , respectively  $F_{\text{BW RF,low}}$  and shall apply within the downlink operating band and in addition the frequency ranges 10 MHz above and 10 MHz below this band. Unwanted emissions outside this frequency range shall be limited by spurious emissions requirements.
+
+The requirements shall apply whatever the type of transmitter considered (single RAT or multi-RAT, single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification, except for GSM single RAT operation. The requirements in TS 45.005 [5] for *Spectrum due to the modulation and wide band noise*, *Intra BTS Intermodulation* and *Out-of-band Spurious Emissions* (for Frequency offset outside relevant transmit band  $< 10 \text{ MHz}$ ) of existing GSM multi-carrier BTS apply to an MSR Base Station for GSM single RAT operation in Band Category 2.
+
+The requirements shall apply with values for  $F_{\text{offset, RAT}}$  as specified in Table 5.2.2-1.
+
+Emissions shall outside of each RF bandwidth edge not exceed the maximum levels specified in the tables below, where:
+
+- $\Delta f$  is the separation between the *RF bandwidth edge* frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f\_offset$  is the separation between the *RF bandwidth edge* frequency and the centre of the measuring filter.
+- $f\_offset_{\max}$  is the offset to the frequency 10 MHz outside the downlink operating band.
+- $\Delta f_{\max}$  is equal to  $f\_offset_{\max}$  minus half of the bandwidth of the measuring filter.
+
+Since the limits are to a large part based on regulatory requirements, the test tolerance shall be zero when deriving the test requirement for Operating band unwanted emissions.
+
+Table 6.6.1.6-1: Operating band unwanted emission mask (UEM for BC2)
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$            | Frequency offset of measurement filter centre frequency, $f\_offset$        | Minimum requirement                                                                         | Measurement bandwidth (Note 5) |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|--------------------------------|
+| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$ (Note 1)                 | $0.015 \text{ MHz} \leq f\_offset < 0.215 \text{ MHz}$                      | -14 dBm                                                                                     | 30 kHz                         |
+| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$                          | $0.215 \text{ MHz} \leq f\_offset < 1.015 \text{ MHz}$                      | $-14 \text{ dBm} - 15 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz                         |
+| (Note 4)                                                                 | $1.015 \text{ MHz} \leq f\_offset < 1.5 \text{ MHz}$                        | -26 dBm                                                                                     | 30 kHz                         |
+| $1 \text{ MHz} \leq \Delta f \leq \min(10 \text{ MHz}, \Delta f_{\max})$ | $1.5 \text{ MHz} \leq f\_offset < \min(10.5 \text{ MHz}, f\_offset_{\max})$ | -13 dBm                                                                                     | 1 MHz                          |
+| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\max}$                      | $10.5 \text{ MHz} \leq f\_offset < f\_offset_{\max}$                        | -15 dBm (Note 6)                                                                            | 1 MHz                          |
+
+NOTE 1: For operation with a GSM or an E-UTRA 1.4 or 3 MHz carrier adjacent to the RF bandwidth edge, the limits in Table 6.6.1.6-2 apply for  $0 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$ .
+
+Table 6.6.1.6-2: Operating band unwanted emission limits for operation in BC2 with GSM or E-UTRA 1.4 or 3 MHz carriers adjacent to the RF bandwidth edge
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$ | Frequency offset of measurement filter centre frequency, $f\_offset$ | Minimum requirement                                                                        | Measurement bandwidth (Note 5) |
+|---------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------------------------------------------------------|--------------------------------|
+| $0 \text{ MHz} \leq \Delta f < 0.05 \text{ MHz}$              | $0.015 \text{ MHz} \leq f\_offset < 0.065 \text{ MHz}$               | $5 \text{ dBm} - 60 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.015 \right) \text{ dB}$  | 30 kHz                         |
+| $0.05 \text{ MHz} \leq \Delta f < 0.15 \text{ MHz}$           | $0.065 \text{ MHz} \leq f\_offset < 0.165 \text{ MHz}$               | $2 \text{ dBm} - 160 \cdot \left( \frac{f\_offset}{\text{MHz}} - 0.065 \right) \text{ dB}$ | 30 kHz                         |
+
+NOTE 2: The limits in this table only apply for operation with a GSM or an E-UTRA 1.4 or 3 MHz carrier adjacent to the RF bandwidth edge.
+
+NOTE 3: All limits in Table 6.6.1.6-1 are identical to the corresponding limits for Band Category 1.
+
+NOTE 4: This frequency range ensures that the range of values of  $f\_offset$  is continuous.
+
+NOTE 5: As a general rule for the requirements in subclause 6.6.1.6, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth.
+
+NOTE 6: The requirement is not applicable when  $\Delta f_{\max} < 10 \text{ MHz}$ .
+
+#### 6.6.1.7 Additional requirements (BC1 and BC2)
+
+In addition to the UEM limits defined in Table 6.6.1.5-1, emission limits defined in FCC title 47 [11] may apply to BS operating in UTRA bands II, IV, V, X, XII, XIII, XIV bands and E-UTRA bands 2, 4, 5, 10, 12, 13, 14 and 17.
+
+The limits from FCC title 47 [11] will not be explicitly included in the MSR specification, but will instead be included by reference as is done today in the GSM specifications [5]. The BS would have to comply with the limits when deployed in regions where FCC Title 47 is applied and under the conditions declared by the manufacturer. This means that they could be met from the RF bandwidth edge for the same  $F_{\text{offset, RAT}}$  that applies for the transmitter and receiver requirements if that is declared by the manufacturer, but other conditions under which they are met could also be declared.
+
+#### 6.6.1.8 Minimum requirement (band category 3)
+
+Operating band unwanted emission requirements are defined above the upper and below the lower RF bandwidth edge located at  $F_{\text{BW RF,high}}$ , respectively  $F_{\text{BW RF,low}}$  and shall apply within the operating band and in addition the frequency
+
+ranges 10 MHz above and 10 MHz below this band. Unwanted emissions outside this frequency range shall be limited by spurious emissions requirements.
+
+The requirements shall apply whatever the type of transmitter considered (single RAT or multi-RAT, single carrier or multi-carrier) and for all transmission modes foreseen by the manufacturer's specification.
+
+The requirements shall apply with values for  $F_{\text{offset, RAT}}$  as specified in Table 5.3.2-1.
+
+Emissions shall not exceed the maximum levels specified in the tables below, where:
+
+- $\Delta f$  is the separation between the RF bandwidth edge frequency and the nominal -3dB point of the measuring filter closest to the carrier frequency.
+- $f_{\text{offset}}$  is the separation between the RF bandwidth edge frequency and the centre of the measuring filter.
+- $f_{\text{offsetmax}}$  is the offset to the frequency 10 MHz outside the downlink operating band.
+- $\Delta f_{\text{max}}$  is equal to  $f_{\text{offsetmax}}$  minus half of the bandwidth of the measuring filter.
+
+Since the limits are to a large part based on regulatory requirements taken, the test tolerance shall be zero when deriving the test requirement for out-of-band Operating band unwanted emissions.
+
+**Table 6.6.1.8-1: Operating band unwanted emission mask (UEM) for BC3**
+
+| Frequency offset of measurement filter -3dB point, $\Delta f$                       | Frequency offset of measurement filter centre frequency, $f_{\text{offset}}$                 | Minimum requirement                                                                                 | Measurement bandwidth (Note 2) |
+|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------------------------------|
+| $0 \text{ MHz} \leq \Delta f < 0.2 \text{ MHz}$                                     | $0.015 \text{ MHz} \leq f_{\text{offset}} < 0.215 \text{ MHz}$                               | -14 dBm                                                                                             | 30 kHz                         |
+| $0.2 \text{ MHz} \leq \Delta f < 1 \text{ MHz}$                                     | $0.215 \text{ MHz} \leq f_{\text{offset}} < 1.015 \text{ MHz}$                               | $-14 \text{ dBm} - 15 \cdot \left( \frac{f_{\text{offset}}}{\text{MHz}} - 0.215 \right) \text{ dB}$ | 30 kHz                         |
+| (Note 1)                                                                            | $1.015 \text{ MHz} \leq f_{\text{offset}} < 1.5 \text{ MHz}$                                 | -26 dBm                                                                                             | 30 kHz                         |
+| $1 \text{ MHz} \leq \Delta f$<br>$\min(\leq 10 \text{ MHz}, \Delta f_{\text{max}})$ | $1.5 \text{ MHz} \leq f_{\text{offset}} <$<br>$\min(10.5 \text{ MHz}, f_{\text{offsetmax}})$ | -13 dBm                                                                                             | 1 MHz                          |
+| $10 \text{ MHz} \leq \Delta f \leq \Delta f_{\text{max}}$                           | $10.5 \text{ MHz} \leq f_{\text{offset}} < f_{\text{offsetmax}}$                             | -15 dBm (Note 4)                                                                                    | 1 MHz                          |
+
+NOTE 1: This frequency range ensures that the range of values of  $f_{\text{offset}}$  is continuous.
+
+NOTE 2: As a general rule for the requirements in subclause 6.6.1.3, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth.
+
+NOTE 3: These requirements apply for E-UTRA TDD and 1.28Mcps UTRA TDD(TD-SCDMA).
+
+NOTE 4: The requirement is not applicable when  $\Delta f_{\text{max}} < 10 \text{ MHz}$ .
+
+#### 6.6.1.9 Additional requirement (BC3)
+
+For E-UTRA, there is a regional requirement in TS 36.104 [4] that may apply to an E-UTRA TDD BS operating in the same geographic area and in the same operating band as another E-UTRA TDD system without synchronisation. For this case the emissions shall not exceed -52 dBm/MHz in the downlink operating band, except in the frequency range from 10 MHz below the lower channel edge to the frequency 10 MHz above the upper channel edge.
+
+The requirement can be specified as a regional requirement for BC3, applying to both E-UTRA and UTRA TDD.
+
+### 6.6.2 Transmitter spurious emissions
+
+The spurious domain covers frequencies, which are separated from the carrier centre frequency by more than 250% of the necessary bandwidth, as recommended in ITU-R SM.329 [6]. This means that the Operating band unwanted emission limits discussed in 6.6.1 also cover parts of the spurious domain. The limits presented in the present subclause
+
+thus excludes the frequency range from 10 MHz below the lowest frequency of the downlink operating band up to 10 MHz above the highest frequency of the downlink operating band.
+
+#### 6.6.2.1 Band category 1
+
+##### 6.6.2.1.1 Mandatory requirements
+
+UTRA and E-UTRA have identical requirements based on recommendations in ITU-R SM.329 [6], both for Category A and Category B limits. The Category B limits for UTRA in TS 25.104 [2] are expressed in a slightly more complex way, but are identical to the E-UTRA limits in TS 36.104 [4].
+
+The requirements of either Table 6.6.2.1.1-1 (Category A limits) or Table 6.6.2.1.1-2 (Category B limits) shall apply.
+
+**Table 6.6.2.1.1-1: BS spurious emission limits, category A**
+
+| Frequency range                                                                                       | Maximum level | Measurement Bandwidth | Note   |  |
+|-------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------|--|
+| 9kHz – 150kHz                                                                                         | -13 dBm       | 1 kHz                 | Note 1 |  |
+| 150kHz – 30MHz                                                                                        |               | 10 kHz                | Note 1 |  |
+| 30MHz – 1GHz                                                                                          |               | 100 kHz               | Note 1 |  |
+| 1GHz – 12.75 GHz                                                                                      |               | 1 MHz                 | Note 2 |  |
+| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1                                                        |               |                       |        |  |
+| NOTE 2: Bandwidth as in ITU-R SM.329 [6], s4.1. Upper frequency as in ITU-R SM.329 [6] , s2.5 table 1 |               |                       |        |  |
+
+**Table 6.6.2.1.1-2: BS spurious emissions limits, category B**
+
+| Frequency range                                                                                       | Maximum Level | Measurement Bandwidth | Note   |
+|-------------------------------------------------------------------------------------------------------|---------------|-----------------------|--------|
+| 9 kHz – 150 kHz                                                                                       | -36 dBm       | 1 kHz                 | Note 1 |
+| 150 kHz – 30 MHz                                                                                      | -36 dBm       | 10 kHz                | Note 1 |
+| 30 MHz – 1 GHz                                                                                        | -36 dBm       | 100 kHz               | Note 1 |
+| 1 GHz – 12.75 GHz                                                                                     | -30 dBm       | 1 MHz                 | Note 2 |
+| NOTE 1: Bandwidth as in ITU-R SM.329 [6], s4.1                                                        |               |                       |        |
+| NOTE 2: Bandwidth as in ITU-R SM.329 [6], s4.1. Upper frequency as in ITU-R SM.329 [6] , s2.5 table 1 |               |                       |        |
+
+##### 6.6.2.1.2 Co-existence in the same geographical area
+
+The co-existence requirements are today almost identical in UTRA and E-UTRA and therefore already well harmonized. The MSR specification can adopt these current requirements for Band Category 1. The most up-to-date requirements are in Table 6.6.4.3.1-1 in [4], where co-existence requirements with all types of systems including E-UTRA/UTRA TDD are combined into a single table.
+
+The parameters are summarised below in Table 6.6.2.1.2-1. The limit to protect the E-UTRA/UTRA downlink is based on a 53 dB MCL (BS-UE) and 3 dB allowed desensitization of the UE receiver [8]. The limit to protect the E-UTRA/UTRA uplink is based on a 67 dB MCL (BS-BS) and 0.8 dB allowed desensitization of the BS receiver [10].
+
+The source of the co-existence requirements with GSM/DCS/PCS downlink is the GSM specifications [5]. The co-existence limit for protecting GSM uplink (-61 dBm/100 kHz) is derived from the GSM co-location requirement in subclause 4.3.2.1 of [5] by shifting the assumed MCL from 30 dB to the 67 dB (BS-BS) assumed for co-existence [9].
+
+**Table 6.6.2.1.2-1: BS spurious emissions limits for co-existence with systems operating in other frequency bands**
+
+| System type to co-exist with    | Frequency range for co-existence requirement  | Maximum Level | Measurement Bandwidth | Note                                                                                                                                                                       |
+|---------------------------------|-----------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| GSM900, GSM 850                 | Downlink operating band of co-existing system | -57 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-existing system.                                                                    |
+|                                 | Uplink operating band of co-existing system   | -61 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-existing system, since it is covered by the protection of own or other BS receiver  |
+| DCS1800, PCS1900                | 1805 – 1880 MHz                               | -47 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-existing system.                                                                    |
+|                                 | 1710 – 1785 MHz                               | -61 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-existing system, since it is covered by the protection of own or other BS receiver  |
+| UTRA FDD and E-UTRA (FDD) bands | Downlink operating band of co-existing system | -52 dBm       | 1 MHz                 | This requirement does not apply to a BS operating in the same operating band as the co-existing system.                                                                    |
+|                                 | Uplink operating band of co-existing system   | -49 dBm       | 1 MHz                 | This requirement does not apply to a BS operating in the same operating band as the co-existing system, since it is covered by the protection of own or other BS receiver. |
+| UTRA TDD and E-UTRA (TDD) bands | Operating band of co-existing system          | -52 dBm       | 1 MHz                 | This requirement does not apply to a BS operating in the same operating band as the co-existing system.                                                                    |
+
+There are also clarifications of the applicability of the limits in two notes to table 6.6.4.3.1-1 in [4], which will be needed also for MSR Base Stations. The first note excludes the frequencies up to 10 MHz immediately outside the downlink operating band from the requirement, since that frequency range is not within the scope of spurious emission. Emission limits for this excluded frequency range may be covered by local or regional requirements.
+
+The second note clarifies that the table above assumes that two operating bands, where the frequency ranges in the table would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications.
+
+There are two additional regional co-existence requirements needed for Band Category 1:
+
+- **Co-existence with PHS:** This requirement applies for protection of PHS for operation in bands applicable in Japan. The requirement is applicable to Band Category 1 and can be taken directly from Table 6.6.4.3.1-2 of the E-UTRA specification [4].
+- **Protection of public safety operations:** This requirement applies for protection of 700 MHz public safety operations for operation in bands 13 and 14. The requirement is applicable to Band Category 1 and can be taken directly from Table 6.6.4.3.1-3 of the E-UTRA specification [4].
+
+##### 6.6.2.1.3 Co-location
+
+The current co-location requirements in the existing specifications for E-UTRA and UTRA are more or less identical for the concerned bands and therefore already well harmonized. The MSR specification can adopt these current requirements for Band Category 1. The most up-to-date requirements are in Table 6.6.4.4.1-1 in [4], where co-location requirements with all types of BS including E-UTRA/UTRA TDD are combined into a single table.
+
+The parameters are summarised below in Table 6.6.2.1.3-1. The source of the co-location requirements with GSM/DCS/PCS (-98 dBm/100 kHz) is the GSM specifications, subclause 4.3.2.1 of [5]. The -96 dBm/100 kHz limit for co-location with E-UTRA/UTRA BS is based on a 30 dB MCL (BS-BS) and 0.8 dB allowed desensitization of the BS receiver.
+
+**Table 6.6.2.1.3-1: BS Spurious emissions limits for BS co-location with another BS**
+
+| Type of co-located BS                     | Frequency range for co-location requirement | Maximum Level | Measurement Bandwidth | Note                                                                                               |
+|-------------------------------------------|---------------------------------------------|---------------|-----------------------|----------------------------------------------------------------------------------------------------|
+| Macro GSM900, DCS1800, PCS1900 and GSM850 | Uplink operating band of co-located BS      | -98 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-located BS. |
+| UTRA FDD and E-UTRA (FDD) bands           | Uplink operating band of co-located BS      | -96 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-located BS. |
+| UTRA TDD and E-UTRA (TDD) bands           | Uplink operating band of co-located BS      | -96 dBm       | 100 kHz               | This requirement does not apply to a BS operating in the same operating band as the co-located BS. |
+
+There are clarifications of the applicability of the limits in three notes to table 6.6.4.4.1-1 in [4], which will be needed also for MSR Base Stations. The first note excludes the frequencies up to 10 MHz immediately outside the downlink operating band from the requirement, since that frequency range is not within the scope of spurious emission. Emission limits for this excluded frequency range may be covered by local or regional requirements. There is also a reference to possible site engineering solutions for such scenarios.
+
+The second note clarifies that the table above assumes that two operating bands, where the frequency ranges in the table would be overlapping, are not deployed in the same geographical area. For such a case of operation with overlapping frequency arrangements in the same geographical area, special co-existence requirements may apply that are not covered by the 3GPP specifications.
+
+The third note remarks that co-located TDD Base Stations that are synchronized and using the same operating band can transmit without special co-locations requirements, while for unsynchronized Base Stations, special co-location requirements may apply that are not covered by the 3GPP specifications
+
+##### 6.6.2.1.4 Protection of the BS receiver of own or different BS
+
+UTRA and E-UTRA have identical limits for this requirement, which is for protection of the uplink operating band of the BS, and it can be adopted also for MSR Band Category 1. The most ‘compact’ way of stating the limits is in Table 6.6.4.2-1 of TS 36.104 [4], where it is covered in a generic fashion by referencing the frequency range of the uplink band in a single table entry through the variables  $F_{UL\_low}$  and  $F_{UL\_high}$ .
+
+The limits are shown below in Table 6.6.2.1.4-1. The limit to protect the E-UTRA/UTRA uplink is based on a 30 dB MCL (BS Tx to BS Rx) and 0.8 dB allowed desensitization of the BS receiver as for the co-location requirement.
+
+The limits to protect other (‘different’) BS are the same as protecting the ‘own’ BS for simplicity, since they cover the same frequency range. This also means that while the scenario for co-existence with other BS would be based on a 67 dB MCL as shown in subclause 6.6.2.1.2 above, the actual requirement gives protection down to 30 dB MCL, thereby enabling not only co-existence, but also co-location with other BS in the same operating band.
+
+**Table 6.6.2.1.4-1: BS spurious emissions limits for protection of the BS receiver (BC1)**
+
+| Frequency range              | Maximum Level | Measurement Bandwidth | Note |
+|------------------------------|---------------|-----------------------|------|
+| $F_{UL\_low} - F_{UL\_high}$ | -96 dBm       | 100 kHz               |      |
+
+#### 6.6.2.2 Band category 2
+
+##### 6.6.2.2.1 Mandatory requirements
+
+The spurious emission requirements for GSM BTS in TS 45.005 [5] for frequencies that are more than 10 MHz outside the operating band are based on the same emission levels of -36 dBm below 1 GHz and -30 dBm above 1 GHz as in ITU-R SM.329 [1] (Category B) and are also the same levels as used for UTRA and E-UTRA. The measurement bandwidth specified in [5] is however not fully aligned with ITU-R SM.329, since it depends on the offset from the edge of the downlink operating band, as shown in Tables 6.6.2.2.1-1 and 6.6.2.2.1-2. This results in that the limits in TS 45.005 [5] are stricter than ITU-R SM.329 [1] (larger measurement BW) for  $f\_offset \geq 10$  MHz in case of frequencies below 1 GHz and for  $f\_offset \geq 30$  MHz in case of frequencies above 1 GHz. In addition, the limits in TS 45.005 [5] for  $10 \leq f\_offset \leq 20$  MHz are more relaxed than ITU-R SM.329 [1] (smaller measurement BW) in case of frequencies above 1 GHz.
+
+**Table 6.6.2.2.1-1: GSM BTS spurious emissions (frequencies  $f < 1$  GHz)**
+
+| Frequency offset from transmitter operating band edge | TS 45.005 [5] limit (Table 4-6 and subclause 4.3.1 b) | Limit in Recommendation ITU-R SM.329 [1] |
+|-------------------------------------------------------|-------------------------------------------------------|------------------------------------------|
+| 10 – 20 MHz                                           | -36 dBm / 300 kHz                                     | -36 dBm / 100 kHz                        |
+| 20 – 30 MHz                                           | -36 dBm / 1 MHz                                       | -36 dBm / 100 kHz                        |
+| $\geq 30$ MHz                                         | -36 dBm / 3 MHz                                       | -36 dBm / 100 kHz                        |
+
+**Table 6.6.2.2.1-2: GSM BTS spurious emissions (frequencies  $f > 1$  GHz)**
+
+| Frequency offset from transmitter operating band edge | TS 45.005 [5] limit (Table 4-6 and subclause 4.3.1 b) | Limit in Recommendation ITU-R SM.329 [1] |
+|-------------------------------------------------------|-------------------------------------------------------|------------------------------------------|
+| 10 – 20 MHz                                           | -30 dBm / 300 kHz                                     | -30 dBm / 1 MHz                          |
+| 20 – 30 MHz                                           | -30 dBm / 1 MHz                                       | -30 dBm / 1 MHz                          |
+| $\geq 30$ MHz                                         | -30 dBm / 3 MHz                                       | -30 dBm / 1 MHz                          |
+
+In order to keep the level of the spurious emission requirements for GSM BTS from TS 45.005 [5] and at the same time align with the recommended limits in ITU-R SM.329 [1] (Category B), the stricter of the two shall apply for BC2.
+
+The mandatory spurious emissions requirements are therefore taken from Table 6.6.2.1.1-2 as applicable also to Band Category 2, with the requirement in Table 6.6.2.2.1-3 applying as additional mandatory Category B limits for BC2 when GSM/EDGE is configured. This gives a set of harmonised limits for the E-UTRA, UTRA and GSM spurious emission requirements, with additional mandatory limits applying in BC2 for Category B.
+
+**Table 6.6.2.2.1-3: Additional mandatory spurious emission limits in BC2, Category B**
+
+| Frequency range  | Frequency offset from transmitter operating band edge | Maximum level | Measurement Bandwidth |
+|------------------|-------------------------------------------------------|---------------|-----------------------|
+| 30 MHz – 1 GHz   | 10 – 20 MHz                                           | -36 dBm       | 300 kHz               |
+|                  | 20 – 30 MHz                                           |               | 1 MHz                 |
+|                  | $\geq 30$ MHz                                         |               | 3 MHz                 |
+| 1GHz – 12.75 GHz | $\geq 30$ MHz                                         | -30 dBm       | 3 MHz                 |
+
+##### 6.6.2.2.2 Co-existence in the same geographical area
+
+The GSM RF specification [5] has co-existence requirements with other GSM bands, protecting the downlink (MS receiver). The limit is -57 dBm/100 kHz for the bands below 1 GHz and -47 dBm/100 kHz for the bands above 1 GHz. These numbers are identical to the ones used by E-UTRA and UTRA for protection of GSM as described in subclause 6.6.2.1.2 and applied to MSR Band Category 1. There are no GSM co-existence requirements for protecting other BS receivers (other than for co-location as discuss in subclause 6.6.2.2.3)
+
+There is a general requirement in subclause 4.3.2.3 of [5] for co-existence with 3G, protecting both uplink and downlink (BS and UE receivers) of Bands 1, 7, 33, 34 and 38. The level is -62 dBm/100 kHz, which corresponds to
+
+the -52 dBm/1 MHz level used also in E-UTRA and UTRA specifications to protect the E-UTRA/UTRA downlink of other bands. As discussed in subclause 6.6.2.1.2, the limit is based on a 53 dB MCL (BS-UE) and 3 dB allowed desensitization of the UE receiver. When applied for protection of the E-UTRA/UTRA uplink as in the GSM RF specifications [5], the limit is 3 dB stricter than needed to match the corresponding E-UTRA/UTRA requirements in [2] and [4]. The reason is probably that no other limit was available at the time when the requirement was set. The -49 dBm/1 MHz level used in the E-UTRA and UTRA specs is judged by TSG RAN to be sufficient for uplink protection and GSM does not need to provide more protection.
+
+For an MSR Base Station, the co-existence scenario is independent of whether it operates in Category 1 bands with E-UTRA/UTRA or in Category 2 bands with E-UTRA/UTRA/GSM. The same limits are therefore applicable for both band categories. The limits used in the existing specifications are also aligned, except for the protection of E-UTRA/UTRA uplink, where the GSM specification [5] is today slightly over-specified as discussed above.
+
+The parameters for the spurious emissions requirement for co-existence are therefore taken from Table 6.6.2.1.2-1 as applicable also to Band Category 2, thereby extending the mutual protection to all E-UTRA, UTRA and GSM bands.
+
+##### 6.6.2.2.3 Co-location
+
+The GSM RF specification [5] has a spurious emissions requirement of -98 dBm/100 kHz for co-location with other GSM Base Stations (subclause 4.3.2.1 of [5]), based on a 30 dB MCL (BS-BS). There is also an additional requirement of -96 dBm/100 kHz for co-location with 3G in subclause 4.3.2.3 of [5], covering Bands 1, 7, 22, 34 and 38. This limit is taken from the UTRA RF specification [2].
+
+For an MSR Base Station, the co-location scenario is independent of whether it operates in Category 1 bands with E-UTRA/UTRA or in Category 2 bands with E-UTRA/UTRA/GSM. The same limits are therefore applicable for both band categories. The limits used in the existing specifications are also completely aligned today as shown above.
+
+The parameters for the spurious emissions requirement for co-location are therefore taken from Table 6.6.2.1.3-1 as applicable also to Band Category 2, thereby extending the mutual protection to all E-UTRA, UTRA and GSM bands.
+
+##### 6.6.2.2.4 Protection of the BS receiver of own or different BS
+
+The GSM RF specification [5] has a spurious emission limit for the BTS receive band in “General requirements” in subclause 4.3.2.1 of TS 45.005 [4]. For a Normal BTS, that limit is -98 dBm in 100 kHz based on a 30 dB MCL, which is the same scenario and limit that apply for co-location with BTS in other bands. While the fundamental scenario for protection of a BS receiver should be the same as in BC1, the 2 dB difference from the BC1 requirement is not significant. The BC2 requirement for protection of the BS receiver can thus be chosen as -98 dBm/100 kHz to align with the co-location requirement for GSM BTS in BC2
+
+The limits are shown below in Table 6.6.2.2.4-1, expressed in the same way as for BC1. As for UTRA and E-UTRA, the limit covers not only protection of own receiver and co-existence with other BTS/BS, but also co-location with other BTS/BS in the same operating band.
+
+**Table 6.6.2.2.4-1: BS Spurious emissions limits for protection of BS receiver (BC2)**
+
+| Frequency range                            | Maximum Level | Measurement Bandwidth | Note |
+|--------------------------------------------|---------------|-----------------------|------|
+| F <sub>UL_low</sub> – F <sub>UL_high</sub> | -98 dBm       | 100 kHz               |      |
+
+#### 6.6.2.3 Band category 3
+
+##### 6.6.2.3.1 Mandatory requirements
+
+The mandatory spurious emissions requirements are taken from subclause 6.6.2.1.1 as applicable also to Band Category 3.
+
+##### 6.6.2.3.2 Co-existence in the same geographical area
+
+The co-existence spurious emissions requirements in the same geographical area are taken from subclause 6.6.2.1.2 as applicable also to Band Category 3.
+
+NOTE 1: For Base Stations operating in BC3 bands in China, the additional BS spurious emission limits for protection of DCS1800 in the same geographical area apply in the frequency range 1805-1850MHz for protection of DCS1800 downlink and in 1710-1755 MHz for protection of DCS1800 uplink.
+
+NOTE 2: For Base Stations operating in BC3 bands in China, the additional regional co-existence requirements for protection of PHS and Public safety operation are not applicable.
+
+##### 6.6.2.3.3 Co-location
+
+The co-location spurious emissions requirements are taken from subclause 6.6.2.1.3 as applicable also to Band Category 3.
+
+### 6.6.3 Occupied bandwidth
+
+Both E-UTRA [4] and UTRA [2,3] have requirements for Occupied bandwidth that is defined strictly in line with ITU-R recommendation ITU-R SM.328 [22]. This requirement is in reality applied only regionally, while it is listed in the specifications as a general requirement.
+
+For GSM [5], there is no requirement for Occupied bandwidth.
+
+Since the requirement only applies per carrier, it can be kept as is, with a common definition and with RAT-specific limits.
+
+#### 6.6.3.1 Definition
+
+The occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage  $\beta/2$  of the total mean transmitted power. See also ITU-R Recommendation SM.328 [22].
+
+The value of  $\beta/2$  shall be taken as 0.5%.
+
+The requirement applies during the transmitter ON period for a single transmitted carrier.
+
+The minimum requirement below may be applied regionally. There may also be regional requirements to declare the Occupied bandwidth according to the definition in the present clause.
+
+#### 6.6.3.2 Minimum requirement
+
+The occupied bandwidth shall be less than values listed in Table 6.6.3.1-1.
+
+**Table 6.6.3.1-1: Occupied bandwidth**
+
+| RAT                            | Occupied bandwidth limit |
+|--------------------------------|--------------------------|
+| E-UTRA                         | $BW_{\text{Channel}}$    |
+| UTRA FDD                       | 5 MHz                    |
+| 1.28 Mcps UTRA TDD<br>TD-SCDMA | 1.6 MHz                  |
+
+### 6.6.4 Adjacent Channel Leakage Ratio (ACLR)
+
+Adjacent Channel Leakage power Ratio (ACLR) is defined as the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency.
+
+As a requirement in the Out-of-band domain, the UTRA FDD and E-UTRA specifications define ACLR requirements applicable for both single and Multicarrier operation:
+
+- For E-UTRA in TS 36.104 [4], the ACLR is defined for the 1<sup>st</sup> and 2<sup>nd</sup> adjacent carrier for each supported channel bandwidth. There are requirements both for adjacent E-UTRA carriers of the same BW measured with a square filter, and for adjacent UTRA carriers measured with a 3.84 Mcps RRC filter.
+
+- For UTRA FDD in TS 25.104 [2], the ACLR is defined for the 1<sup>st</sup> and 2<sup>nd</sup> adjacent UTRA carrier, measured with a 3.84 Mcps RRC filter.
+
+ACLR requirements for UTRA and E-UTRA are derived through extensive simulation work of adjacent channel co-existence scenarios as documented in TR 25.942 [7] and TR 36.942 [23]. ACLR is often used as a reference parameter in co-existence studies and could for this reason also be of interest to document for MSR Base Stations. ACLR does however play a very small role in co-existence studies with non-3GPP technologies.
+
+While the out-of-band emissions for MSR BS will be covered by the Operating band unwanted emission limits, there may for the reasons of understanding co-existence properties with adjacent legacy systems still be an interest to have ACLR limits in the MSR specifications.
+
+The existing single-RAT ACLR requirements for adjacent 5 MHz UTRA systems can thus be adopted for MSR BS and be applied to E-UTRA, UTRA FDD and UTRA TDD. There will be no generic MSR multi-RAT requirement for ACLR.
+
+## 6.7 Transmitter intermodulation
+
+For transmit intermodulation requirements, UTRA and E-UTRA apply interferers with the same bandwidth, level and frequency offset. The difference is the interferer modulation where UTRA is based on a WCDMA modulated signal while the E-UTRA interferer is OFDM modulated. The GSM requirement is also similar in terms of interferer level but it is based on a CW interferer at offsets larger than 800 kHz.
+
+The MSR transmit intermodulation requirement should use both modulated wide-band interferers and CW interferer at lower offsets and maintain the already harmonized interferer level of 30 dB below the wanted signal. Through this approach, added value for all concerned technologies is obtained, since both CW and wide-band modulated interferers are covered.
+
+The GSM Intra BTS intermodulation requirement (Clause 4.7.2 in [5]) is kept as MSR single RAT requirement for GSM in order to ensure the integrity of the system.
+
+### 6.7.1 Minimum requirement
+
+The transmit intermodulation requirement is a measure of the capability of the transmitter to inhibit the generation of signals in its non linear elements caused by presence of the own transmit signal and an interfering signal reaching the transmitter via the antenna.
+
+The transmitter intermodulation level is the power of the intermodulation products when an interfering signal with a level of 30 dB below wanted signal is injected into the antenna connector. The type and offset of the interfering signal from the edge of RF bandwidth shall be as in Table 6.7.1-1 for BC1 and BC2, and in addition as in Table 6.7.1-2 for BC2 and in Table 6.7.1-3 for BC3.
+
+For Band Category 1, the requirement is applicable for a wanted signal being UTRA or E-UTRA of maximum channel bandwidth, with interfering signals according to Table 6.7.1-1.
+
+For Band Category 2, the requirement is applicable for a wanted signal being GSM, UTRA or E-UTRA of maximum channel bandwidth, with interfering signals according to Table 6.7.1-1 and Table 6.7.1-2.
+
+For Band Category 3, the requirement is applicable for a wanted signal being UTRA or E-UTRA of maximum channel bandwidth, with interfering signals according to Table 6.7.1-3.
+
+**Table 6.7.1-1: Interfering signals for the transmitter intermodulation requirement (BC1 and BC2)**
+
+| <b>Parameter</b>                                                         | <b>Value</b>                                                                                                                                                |
+|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Interfering signal type                                                  | E-UTRA signal of channel bandwidth 5 MHz                                                                                                                    |
+| Interfering signal level                                                 | Mean power level 30 dB below the mean power of the wanted signal                                                                                            |
+| Interfering signal centre frequency offset from edge of the RF bandwidth | 2.5 MHz for modulated interferer<br>7.5 MHz for modulated interferer<br>12.5 MHz for modulated interferer                                                   |
+| NOTE:                                                                    | Interfering signal positions that are partially or completely outside of the downlink operating band of the Base Station are excluded from the requirement. |
+
+**Table 6.7.1-2: Interfering signal for the transmitter intermodulation requirement (BC2)**
+
+| <b>Parameter</b>                                                         | <b>Value</b>                                                                                                                                                |
+|--------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Interfering signal type                                                  | CW                                                                                                                                                          |
+| Interfering signal level                                                 | Mean power level 30 dB below the mean power of the wanted signal                                                                                            |
+| Interfering signal centre frequency offset from edge of the RF bandwidth | > 800 kHz for CW interferer                                                                                                                                 |
+| NOTE:                                                                    | Interfering signal positions that are partially or completely outside of the downlink operating band of the Base Station are excluded from the requirement. |
+
+**Table 6.7.1-3: Interfering signals for the transmitter intermodulation requirement (BC3)**
+
+| <b>Parameter</b>                                                         | <b>Value</b>                                                                                                                                                                                                                                                                      |
+|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Interfering signal type                                                  | E-UTRA signal of channel bandwidth 5 MHz<br>1.28Mcps TDD signal of channel bandwidth 1.6 MHz                                                                                                                                                                                      |
+| Interfering signal level                                                 | Mean power level 30 dB below the mean power of the wanted signal                                                                                                                                                                                                                  |
+| Interfering signal centre frequency offset from edge of the RF bandwidth | 2.5 MHz for modulated E-UTRA interferer<br>7.5 MHz for modulated E-UTRA interferer<br>12.5 MHz for modulated E-UTRA interferer<br>0.8 MHz for modulated 1.28Mcps TDD interferer<br>1.6 MHz for modulated 1.28Mcps TDD interferer<br>2.4 MHz for modulated 1.28Mcps TDD interferer |
+| NOTE:                                                                    | Interfering signal positions that are partially or completely outside of the downlink operating band of the Base Station are excluded from the requirement.                                                                                                                       |
+
+The transmitter intermodulation level shall not exceed the unwanted emission limits in subclause 6.6 in the presence of a wanted signal and an interfering signal according to Table 6.7.1-1 for BC1 and BC2, and in addition Table 6.7.1-2 for BC2 and Table 6.7.1-3 for BC3.
+
+# 7 Receiver characteristics
+
+## 7.1 General
+
+The requirements in clause 7 are expressed for a single receiver antenna connector. For receivers with antenna diversity, the requirements apply for each receiver antenna connector.
+
+Unless otherwise stated, the receiver characteristics are specified at the BS antenna connector (test port A) with a full complement of transceivers for the configuration in normal operating conditions. If any external apparatus such as a RX amplifier, a filter or the combination of such devices is used, requirements apply at the far end antenna connector (test port B).
+
+Unless otherwise stated the requirements in clause 7 apply during the Base Station receive period.
+
+![Figure 7.1: Receiver test ports. The diagram shows a sequence of components connected in series from left to right: a 'BS cabinet', an 'External LNA (if any)', and an 'External device e.g. RX filter (if any)'. A wavy line represents a cable connecting the BS cabinet to the External LNA. Another wavy line connects the External LNA to the External device. A dashed wavy line with an arrow pointing left represents the signal 'From antenna connector' entering the External device. Two test ports are indicated: 'Test port A' is at the antenna connector on the BS cabinet, and 'Test port B' is at the antenna connector on the far side of the External device.](f1091147d93cee4dfa88498610e395a7_img.jpg)
+
+Figure 7.1: Receiver test ports. The diagram shows a sequence of components connected in series from left to right: a 'BS cabinet', an 'External LNA (if any)', and an 'External device e.g. RX filter (if any)'. A wavy line represents a cable connecting the BS cabinet to the External LNA. Another wavy line connects the External LNA to the External device. A dashed wavy line with an arrow pointing left represents the signal 'From antenna connector' entering the External device. Two test ports are indicated: 'Test port A' is at the antenna connector on the BS cabinet, and 'Test port B' is at the antenna connector on the far side of the External device.
+
+Figure 7.1: Receiver test ports
+
+E-UTRA throughput requirements defined for the receiver characteristics in this clause do not assume HARQ retransmissions.
+
+Values for  $F_{\text{offset, RAT}}$  to meet receiver requirements are specific for each RAT in each Band Category as specified in subclause 5.2.1 for Band Category 1, subclause 5.2.2 for Band Category 2 and subclause 5.3.2 for Band Category 3.
+
+## 7.2 Reference sensitivity level
+
+The reference sensitivity power level  $P_{\text{REFSENS}}$  is the minimum mean power received at the antenna connector at which a reference performance requirement shall be met for a specified reference measurement channel.
+
+- In E-UTRA, the reference performance is a throughput limit in static conditions and the reference measurement channel is a Fixed Reference Channel (FRC) with QPSK modulation that varies depending on the channel bandwidth (clause 7.2 of [4]). Other channels, modulation schemes and propagation conditions are covered by the performance requirements, which are not within the scope of MSR. A noise figure of 5 dB is assumed.
+- In UTRA, the reference performance is a BER limit in static conditions and the reference measurement channel is a 12.2 kbps channel with QPSK modulation (clause 7.2 of [2]). Other channels, modulation schemes and propagation conditions are covered by the performance requirements, which are not within the scope of MSR. A noise figure of 5 dB is assumed.
+- In GSM, the reference performance is a set of FER, BER and BLER limits in static and fading conditions, and the reference measurement channel is a set of control and traffic channels, including both speech and data. These are in general defined at a fixed  $P_{\text{REFSENS}}$  level, while there are also for some modulation schemes additional sets of  $P_{\text{REFSENS}}$  levels at which fixed FER, BER and BLER limits for those modulation schemes are to be met (Clause 6.2 of [5]). A noise figure of 8 dB is assumed.
+
+Since the definition of reference sensitivity requirements are RAT specific, the existing requirements are applied only as MSR single RAT requirements for each RAT, in BC1, BC2 and BC3. No corresponding multi-RAT requirement is defined.
+
+The reference sensitivity level  $P_{\text{REFSENS}}$  is however also used as a reference level for a number of other receiver requirements, both for single-RAT requirements in existing specifications and for MSR multi-RAT requirements. They will therefore need to be included by reference also in the MSR specification, in order to clearly define what limits are referred to in other receiver requirements.
+
+### 7.2.1 Minimum requirement
+
+For E-UTRA, the minimum requirement for reference sensitivity is specified in TS 36.104 [4], section 7.2.
+
+For UTRA FDD, the minimum requirement for reference sensitivity is specified in TS 25.104 [2], section 7.2.
+
+For UTRA TDD, the minimum requirement for reference sensitivity is specified in TS 25.105 [3], section 7.2.
+
+For GSM/EDGE, the minimum requirement for reference sensitivity is specified in TS 45.005 [5], applicable parts of subclause 6.2.
+
+The conditions specified in TS 45.005 [5], Annex P.1 apply for GSM/EDGE reference sensitivity.
+
+## 7.3 Dynamic range
+
+For both UTRA and E-UTRA, the dynamic range is specified as a measure of the capability of the receiver to receive a wanted signal in the presence of an interfering signal inside the received channel bandwidth. In this condition a Bit Error Rate (BER) or throughput requirement shall be met for a specified reference measurement channel. The intention of this requirement is to ensure that the Base Station can receive high throughput also in the presence of increased interference and higher wanted signal levels.
+
+The receiver dynamic range for the GSM Base Station is mainly defined by the Nominal Error Rate (NER) requirement, which defines BER limits at considerably higher received signal levels than the reference sensitivity level.
+
+The rationale for and definition of those dynamic range requirements are very RAT specific are therefore not modified for BC1, BC2 and BC3 in the context of the MSR.
+
+### 7.3.1 Minimum requirement
+
+For GSM, the minimum requirement is specified in TS 45.005, section 6.1.
+
+For UTRA FDD, the minimum requirement is specified in TS 25.104, section 7.3.1.
+
+For UTRA TDD, the minimum requirement is specified in TS 25.105, section 7.3.1.
+
+For E-UTRA, the minimum requirement is specified in TS 36.104, section 7.3.1.
+
+## 7.4 In-band selectivity and blocking
+
+### 7.4.1 Band category 1
+
+#### 7.4.1.1 Blocking
+
+The UTRA blocking requirement is based on a UTRA interfering signal with mean power of -40dBm and 7.5MHz minimum offset from the channel edge of the wanted signal.
+
+The E-UTRA blocking requirement is based on a E-UTRA interfering signal with mean power of -43dBm. The minimum offset from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is equal to 1.5 E-UTRA channel bandwidth.
+
+Combining the requirements for UTRA and E-UTRA scenarios, a generic MSR blocking requirement based on a UTRA interfering signal with mean power of -40 dBm and 7.5MHz minimum offset from the RF bandwidth edge is adopted.
+
+##### 7.4.1.1.1 Minimum requirement
+
+The blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer. The interfering signal shall be an UTRA signal as specified in Annex A.
+
+For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.1.1.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.1.1.1-1: Blocking requirement for band category 1**
+
+| Operating Band                                                                         | Centre Frequency of Interfering Signal [MHz]      | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum frequency offset from the RF bandwidth edge [MHz] |
+|----------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------|
+| 1, 4, 6-7, 9-11, 13-14                                                                 | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40,                                | $P_{REFSENS} + 6 \text{ dB}^*$ | 7.5                                                                                           |
+| 12                                                                                     | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) |                                     |                                |                                                                                               |
+| 17                                                                                     | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 18$ ) |                                     |                                |                                                                                               |
+| 20                                                                                     | ( $F_{UL\_low} - 11$ ) to ( $F_{UL\_high} + 20$ ) |                                     |                                |                                                                                               |
+| NOTE*: $P_{REFSENS}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                                   |                                     |                                |                                                                                               |
+
+#### 7.4.1.2 Narrowband blocking
+
+The UTRA narrowband blocking requirement is based on a GSM interfering signal with mean power of -47dBm and 200 kHz or 300 kHz minimum offset from the channel edge of the wanted signal.
+
+The E-UTRA narrowband blocking requirement is based on a E-UTRA 1RB interfering signal with mean power of -49dBm. The offset from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is repeated in multiple RB positions over the assumed interfering E-UTRA signal.
+
+A generic MSR narrowband blocking requirement based on a E-UTRA 1RB interfering signal with mean power of -49dBm is appropriate. The interfering signal offsets may be dependent on the victim E-UTRA channel bandwidth. The 240 kHz offset correspond to the first RB (closest to the RF bandwidth edge) of an E-UTRA interfering signal, where the E-UTRA signals channel bandwidth is selected so that the interfering signal is as close as possible to the victim, i.e. a E-UTRA signal with 3 MHz channel BW. The principle of repeating the single RB signal in multiple RB positions over the assumed interfering E-UTRA signal is copied from E-UTRA specification.
+
+##### 7.4.1.2.1 Minimum requirement
+
+The narrowband blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer. The interfering signal shall be an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.1.2.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.1.2.1-1: Narrowband blocking requirement for band category 1**
+
+| Any RAT and carrier                                                                           | Wanted signal mean power [dBm]        | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] |
+|-----------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------|-------------------------------------------------------------------------|
+| UTRA and E-UTRA                                                                               | $P_{\text{REFSENS}} + 6 \text{ dB}^*$ | -49                                 | 240 +m*180,<br>m=0, 1, 2, 3, 4, 9, 14, 19, 24                           |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                       |                                     |                                                                         |
+
+### 7.4.2 Band category 2
+
+#### 7.4.2.1 Blocking requirement
+
+The MSR blocking requirements for band category 1 should also apply for band category 2 with a GSM wanted signal power of  $P_{\text{REFSENS}} + [3] \text{ dB}$  as for other GSM requirements. This gives added value to GSM systems since a blocking requirement with wideband modulated interferer based on the scenario investigated for UTRA is currently not covered in the existing GSM specifications.
+
+A generic MSR blocking requirement based on the UTRA interfering signal with mean power of -40 dBm and 7.5MHz minimum offset from the RF bandwidth edge is adopted based on the BC1 requirement.
+
+##### 7.4.2.1.1 Minimum requirement
+
+The blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer. The interfering signal shall be a UTRA signal as specified in Annex A.
+
+For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.2.1.1-1, the following requirements shall be met:
+
+- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1.
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.2.1.1-1: Blocking requirement for band category 2**
+
+| Operating Band                                                                                                  | Centre Frequency of Interfering Signal [MHz]                    | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm]        | Interfering signal centre frequency minimum frequency offset from the RF bandwidth edge [MHz] |  |  |  |
+|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|-------------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------|--|--|--|
+| 2-3, 5                                                                                                          | ( $F_{\text{UL\_low}} - 20$ ) to ( $F_{\text{UL\_high}} + 20$ ) | -40                                 | $P_{\text{REFSENS}} + x \text{ dB}^*$ | 7.5                                                                                           |  |  |  |
+| 8                                                                                                               | ( $F_{\text{UL\_low}} - 20$ ) to ( $F_{\text{UL\_high}} + 10$ ) |                                     |                                       |                                                                                               |  |  |  |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and on the channel bandwidth, see section 7.2.                   |                                                                 |                                     |                                       |                                                                                               |  |  |  |
+| NOTE**: x is equal to [3] in case of GSM wanted signal and equal to 6 in case of UTRA or E-UTRA wanted signals. |                                                                 |                                     |                                       |                                                                                               |  |  |  |
+
+#### 7.4.2.2 Narrowband blocking
+
+The MSR narrowband blocking requirements for band category 1 should also apply for band category 2 with a GSM wanted signal power of  $P_{\text{REFSENS}} + [3] \text{ dB}$  as for other GSM requirements. A narrowband blocking requirement with narrowband modulated interferer based on the scenario investigated for E-UTRA is currently not covered in the existing GSM specifications. However it should be noted that in TS45.005, the capability of the receiver to receive a wanted modulated signal without exceeding a given degradation due to the presence of an unwanted modulated signal at an adjacent carrier frequency is defined in section 6.3 (reference interference level).
+
+The more strict MC-BTS GSM narrowband blocking requirements levels based on CW interferer are covered as MSR single RAT requirement for GSM and also apply for GSM carriers in multi-RAT operation.
+
+A generic MSR narrowband blocking requirement based on an E-UTRA 1RB interfering signal with mean power of -49dBm and an interfering signal offset of 240 kHz is adopted, based on the BC1 requirement.
+
+##### 7.4.2.2.1 Minimum requirement
+
+The narrowband blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer. The interfering signal shall be an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.2.2.1-1, the following requirements shall be met:
+
+- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.1.
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.2.2.1-1: Narrowband blocking requirement for band category 2**
+
+| Any RAT and carrier                                                                                             | Wanted signal mean power [dBm] | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] |
+|-----------------------------------------------------------------------------------------------------------------|--------------------------------|-------------------------------------|-------------------------------------------------------------------------|
+| GSM, UTRA and E-UTRA                                                                                            | PREFSENS + x dB*               | -49                                 | 240 + m*180,<br>m=0, 1, 2, 3, 4, 9, 14, 19, 24                          |
+| NOTE*: PREFSENS depends on the RAT and on the channel bandwidth, see section 7.2.                               |                                |                                     |                                                                         |
+| NOTE**: x is equal to [3] in case of GSM wanted signal and equal to 6 in case of UTRA or E-UTRA wanted signals. |                                |                                     |                                                                         |
+
+In addition, the GSM MC-BTS blocking requirement as stated in TS 45.005 [5] applies both for GSM single RAT operation as well as for any GSM carrier in multi-RAT operation.
+
+### 7.4.3 band category 3
+
+#### 7.4.3.1 Blocking
+
+The UTRA TDD blocking requirement is based on a UTRA TDD interfering signal with mean power of -40dBm and 2.4 MHz minimum offset from the channel edge of the wanted signal.
+
+The E-UTRA blocking requirement is based on an E-UTRA interfering signal with mean power of -43dBm. The minimum offset from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is equal to  $1.5 \cdot \text{E-UTRA channel bandwidth}$ .
+
+The UTRA TDD and E-UTRA scenarios can be covered by a combination of two 43channelizat. First, the same generic MSR blocking requirement as in BC1 and BC2, based on an UTRA interfering signal with mean power of -40 dBm and 7.5MHz minimum offset from the RF bandwidth edge is adopted. As an additional requirement in BC3, an MSR blocking requirement based on a 1.28 Mcps UTRA TDD interfering signal with mean power of -40 dBm and 2.4MHz minimum offset from the RF bandwidth edge is adopted.
+
+##### 7.4.3.1.1 Minimum requirement
+
+The blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer.
+
+The interfering signal shall be a UTRA signal as specified in Annex A.
+
+For a wanted signal and an interfering UTRA signal as specified in Annex A coupled to the Base Station antenna input, using the parameters in Table 7.4.3.1.1-1, the following requirements shall be met:
+
+- For any UTRA TDD carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.3.1.1-1: Blocking requirement for band category 3**
+
+| Operating Band                                                                         | Centre Frequency of Interfering Signal [MHz]      | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum frequency offset from the RF bandwidth edge [MHz] |
+|----------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------|
+| 33-40                                                                                  | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40,                                | $P_{REFSENS} + 6$ dB*          | 7.5 MHz                                                                                       |
+| NOTE*: $P_{REFSENS}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                                   |                                     |                                |                                                                                               |
+
+For a wanted signal and an interfering 1.28 Mcps UTRA TDD signal as specified in Annex A coupled to the Base Station antenna input, using the parameters in Table 7.4.3.1.1-2, the following requirements shall be met:
+
+- For any UTRA TDD carrier, the BER shall not exceed 0.001.
+- For any E-UTRA TDD carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.1.1.1-2: Additional blocking requirement for band category 3**
+
+| Operating Band                                                                         | Centre Frequency of Interfering Signal [MHz]      | Interfering Signal mean power [dBm] | Wanted Signal mean power [dBm] | Interfering signal centre frequency minimum frequency offset from the RF bandwidth edge [MHz] |
+|----------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------|--------------------------------|-----------------------------------------------------------------------------------------------|
+| 33-40                                                                                  | ( $F_{UL\_low} - 20$ ) to ( $F_{UL\_high} + 20$ ) | -40,                                | $P_{REFSENS} + 6$ dB*          | 2.4                                                                                           |
+| NOTE*: $P_{REFSENS}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                                   |                                     |                                |                                                                                               |
+
+#### 7.4.3.2 Narrowband blocking
+
+The E-UTRA narrowband blocking requirement is based on an E-UTRA 1RB interfering signal with mean power of -49 dBm. The offset from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is repeated in multiple RB positions over the assumed interfering E-UTRA signal. There is no narrowband blocking requirement for UTRA.
+
+A generic MSR narrowband blocking requirement based on an E-UTRA 1RB interfering signal with mean power of -49 dBm is adopted. The interfering signal offsets may be dependent on the victim E-UTRA channel bandwidth. The 240 kHz offset correspond to the first RB (closest to the RF bandwidth edge) of an E-UTRA interfering signal, where the E-UTRA signals channel bandwidth is selected so that the interfering signal is as close as possible to the victim, i.e. a E-UTRA signal with 3 MHz channel BW. The principle of repeating the single RB signal in multiple RB positions over an assumed interfering 5 MHz E-UTRA signal is copied from E-UTRA specification.
+
+##### 7.4.3.2.1 Minimum requirement
+
+The narrowband blocking characteristics are a measure of the receiver ability to receive a wanted signal at its assigned channel in the presence of an unwanted interferer. The interfering signal shall be an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted and interfering signal coupled to the Base Station antenna input, using the parameters in Table 7.4.3.2.1-1, the following requirements shall be met:
+
+- For any UTRA TDD carrier, the BER shall not exceed 0.001.
+
+- For any E-UTRA TDD carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.4.3.2.1-1: Narrowband blocking requirement for band category 3**
+
+| Any RAT and carrier                                                                           | Wanted signal mean power [dBm]        | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] |
+|-----------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------|-------------------------------------------------------------------------|
+| UTRA and E-UTRA                                                                               | $P_{\text{REFSENS}} + 6 \text{ dB}^*$ | -49                                 | 240 + m*180,<br>m=0, 1, 2, 3, 4, 9, 14, 19, 24                          |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                       |                                     |                                                                         |
+
+## 7.5 Out-of-band blocking
+
+### 7.5.1 Band category 1
+
+#### 7.5.1.1 General “out-of-band” blocking
+
+UTRA and E-UTRA requirements are based on a CW interferer at -15 dBm and excludes the frequency range from 20 MHz below the lowest frequency of the uplink operating band up to 20 MHz above the highest frequency of the uplink operating band.
+
+The following “out-of-band” blocking requirement applies to Band Category 1.
+
+For the parameters specified in Table 7.5.1.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001
+- For any E-UTRA carriers, the throughput shall be  $\geq 95\%$  of the maximum throughput of the E-UTRA reference measurement channel.
+
+**Table 7.5.1.1-1: Blocking performance requirement**
+
+| Parameter                                                                                    | Value                                                                                      |
+|----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|
+| Centre Frequency of Interfering Signal                                                       | 1 MHz to $(F_{\text{UL\_low}} - 20)$ MHz<br>$(F_{\text{UL\_high}} + 20)$ MHz to 12 750 MHz |
+| Interfering Signal mean power                                                                | -15 dBm                                                                                    |
+| Wanted Signal mean power                                                                     | $P_{\text{REFSENS}} + 6 \text{ dB}^*$                                                      |
+| Type of Interfering Signal                                                                   | CW                                                                                         |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and the channel bandwidth, see subclause 7.2. |                                                                                            |
+
+#### 7.5.1.2 Co-location
+
+The current blocking requirements for co-location in E-UTRA [4] and UTRA [2] are based on a +16 dBm interference level and are thus already harmonized. This level is derived from a 30 dB minimum coupling loss between co-located Base Stations. The MSR specification can adopt these current requirements for Band Category 1. The most up-to-date requirements are in Table 7.6.2.1-1 in [4], where co-location requirements with all types of BS including E-UTRA/UTRA TDD are combined into a single table. The parameters are shown in Table 7.5.1.2-1.
+
+**Table 7.5.1.2-1: Blocking performance requirement for BS when co-located with BS in other frequency bands**
+
+| Parameter                              | Value                                                                                                                                   |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
+| Co-located BS type                     | BS operating in<br>- Any E-UTRA band (paired and unpaired)<br>- Any UTRA band (paired and unpaired)<br>- Any GSM band (including R-GSM) |
+| Centre Frequency of Interfering Signal | Downlink operating band of co-located BS type                                                                                           |
+| Interfering Signal mean power          | +16 dBm                                                                                                                                 |
+| Wanted Signal mean power               | P <sub>REFSENS</sub> +6dB*                                                                                                              |
+| Type of Interfering Signal             | CW                                                                                                                                      |
+| NOTE*:                                 | P <sub>REFSENS</sub> depends on the RAT and the channel bandwidth, see subclause 7.2.                                                   |
+
+There are also exceptions handled through two notes to table 7.6.2.1-1 in [4], which will be needed also for MSR Base Stations. The first note excludes the frequencies up to 10 MHz immediately outside the Uplink operating band from the requirement. The exception is Band 13 where 9 MHz are excluded below the band, since co-location with Band 14 Base Stations are anticipated.
+
+The second note further clarifies the situation for cases where a paired uplink is directly adjacent to an unpaired band and proposes site-engineering solutions for those cases. The note for E-UTRA FDD in [4] states that “Some combinations of bands may not be possible to co-site based on the requirements above. The current state-of-the-art technology does not allow a single generic solution for co-location of UTRA TDD or E-UTRA TDD with E-UTRA FDD on adjacent frequencies for 30dB BS-BS minimum coupling loss. However, there are certain site-engineering solutions that can be used. These techniques are addressed in TR 25.942”. The corresponding text for UTRA is included in subclause 7.5.3 of [2].
+
+### 7.5.2 Band category 2
+
+#### 7.5.2.1 General “out-of-band” blocking
+
+The out-of-band blocking requirement for GSM is derived for TS 45.005 [5] based on a scenario with co-located BTS at 30 dB coupling loss [16]. Since co-location is covered by the specific requirement in subclause 7.5.2.2, which is also stricter than the general GSM requirement, it is not an applicable scenario for the general out-of-band blocking requirement.
+
+The UTRA and E-UTRA general out-of-band blocking requirements are based on a CW interferer at -15 dBm for the frequency ranges where co-location does not apply and is applied for MSR BC1 as shown in subclause 7.5.1.1. With the stricter co-location requirements defined separately for GSM, the same general -15 dBm limit can also be applied for MSR BC2.
+
+The parameters for the general blocking requirement are therefore taken from Table 7.5.1.1-1 as applicable also to Band Category 2, thereby harmonising the E-UTRA, UTRA and GSM blocking requirements.
+
+#### 7.5.2.2 Co-location
+
+The GSM RF specification [5] does not have a specific blocking requirement for co-location with other Base Stations. Co-location has however been used as one scenario for the general out-of-band blocking requirement.
+
+For an MSR Base Station, the blocking scenario for co-location is independent of whether it operates in Category 1 bands with E-UTRA/UTRA or in Category 2 bands with E-UTRA/UTRA/GSM. The same blocking requirement level of +16 dBm is therefore applicable for both band categories. It should be noted that this level is stricter than the general out-of-band blocking requirements in [5].
+
+The parameters for the blocking requirement for co-location are therefore taken from Table 7.5.1.2-1 as applicable also to Band Category 2, thereby adding a mutual blocking protection covering all E-UTRA, UTRA and GSM bands.
+
+### 7.5.3 Band category 3
+
+#### 7.5.3.1 General “out-of-band” blocking
+
+The general out-band blocking requirements for both E-UTRA TDD and UTRA TDD 1.28Mcps are based on a CW interferer at -15 dBm and exclude the frequency range from 20 MHz below the lowest frequency of the uplink operating band up to 20 MHz above the highest frequency of the uplink operating band.
+
+The following “out-of-band” blocking requirement applies to Band Category 3.
+
+For the parameters specified in Table 7.5.3.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001
+- For any E-UTRA carriers, the throughput shall be  $\geq 95\%$  of the maximum throughput of the E-UTRA reference measurement channel.
+
+**Table 7.5.3.1-1: Blocking performance requirement**
+
+| Parameter                              | Value                                                                                  |
+|----------------------------------------|----------------------------------------------------------------------------------------|
+| Centre Frequency of Interfering Signal | 1 MHz to (F <sub>UL_low</sub> -20) MHz<br>(F <sub>UL_high</sub> +20) MHz to 12 750 MHz |
+| Interfering Signal mean power          | -15 dBm                                                                                |
+| Wanted Signal mean power               | P <sub>REFSENS</sub> +6dB*                                                             |
+| Type of Interfering Signal             | CW                                                                                     |
+| NOTE*:                                 | P <sub>REFSENS</sub> depends on the RAT and the channel bandwidth, see subclause 7.2.  |
+
+#### 7.5.3.2 Co-location
+
+When E-UTRA TDD and UTRA TDD 1.28Mcps Base Stations are collocated with GSM/DCS, UTRA or E-UTRA BS operating in a different frequency band, the current blocking requirements for E-UTRA and UTRA LCR TDD BS are harmonized with +16 dBm interference signal level. Thus the blocking requirement in Table 7.5.3.2-1 is applied when the MSR band category 3 BS is collocated with GSM/DCS, UTRA or E-UTRA BS. The interference level is derived from a 30 dB minimum coupling loss between co-located Base Stations.
+
+**Table 7.5.3.2-1: Blocking performance requirement for band category 3 BS when co-located with GSM/DCS, UTRA or E-UTRA BS in other frequency bands**
+
+| Parameter                              | Value                                                                                                                                    |
+|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|
+| Co-located BS type                     | BS operating in<br>- Any E-UTRA band (paired and unpaired)<br>- Any UTRA band (paired and unpaired)<br>- GSM850/900,DCS1800**            |
+| Centre Frequency of Interfering Signal | Downlink operating band of co-located BS type                                                                                            |
+| Interfering Signal mean power          | +16 dBm                                                                                                                                  |
+| Wanted Signal mean power               | P <sub>REFSENS</sub> +6dB*                                                                                                               |
+| Type of Interfering Signal             | CW                                                                                                                                       |
+| NOTE*:                                 | P <sub>REFSENS</sub> depends on the RAT and the channel bandwidth, see subclause 7.2.                                                    |
+| NOTE**:                                | In China, the co-location blocking requirement is only applicable to the BC3 BS co-located with BTS operating in DCS1800 (1805-1850MHz). |
+
+There are the exceptions handled through two notes to table 7.6.2.1-1 in [4], which is needed also for MSR Base Stations and the solution to the exceptions in 7.5.1.2 for BC1 is applicable to BC3.
+
+## 7.6 Receiver spurious emissions
+
+The requirement specified for E-UTRA, UTRA and GSM receiver spurious emissions is based on the spurious emission requirements for “Receivers and idle/standby transmitters” defined in [15].
+
+### 7.6.1 Band category 1
+
+The requirements for E-UTRA and UTRA consist of three parts:
+
+- A general spurious emissions requirements, based on [15].
+- Additional requirements for protection of BS receivers for FDD uplink and TDD bands. These limits were listed separately for UTRA in [2], but are instead included by reference for E-UTRA in [4].
+- Co-existence requirements that may apply for co-located Base Stations are incorporated by reference.
+
+The general spurious emission requirements apply for UTRA in the same way as for E-UTRA. The frequency range in the out-of-band domain is excluded, i.e. out to the outermost carrier centers plus 250% of the necessary bandwidth (= Channel bandwidth).
+
+In order to align with the way transmitter unwanted emissions are defined in Clause 6.6.1 and 6.6.2, the same generic assumption is applied for the Rx spurious limits. This means that independent of the transmitted RAT(s) and how many carriers that are transmitted within the BS RF bandwidth, only frequencies that are more than 10 MHz below the lower RF bandwidth edge and more than 10 MHz above the upper RF bandwidth edge are covered by the requirement. The frequency range between those points may be excluded.
+
+The additional requirements for co-existence and co-location are based on the corresponding Tx spurious limits and can for this reason be expressed as a direct reference to the additional Tx spurious emission requirements in subclause 6.6.2. This avoids duplication of limits and reduces the risk for errors when updating specifications.
+
+#### 7.6.1.1 Minimum requirement (BC1)
+
+The receiver spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the BS receiver antenna connector. The requirements apply to all BS with separate RX and TX antenna ports. In this case for FDD BS the test shall be performed when both TX and RX are on, with the TX port terminated.
+
+For TDD BS with common RX and TX antenna port the requirement applies during the Transmitter OFF period. For FDD BS with common RX and TX antenna port the transmitter spurious emission limits as specified in subclause 6.6.2 are valid.
+
+The power of any spurious emission shall not exceed the levels in Table 7.6.1.1-1:
+
+**Table 7.6.1.1-1: General spurious emission minimum requirement**
+
+| Frequency range   | Maximum level                                                                                                                  | Measurement Bandwidth | Note |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------|------|
+| 30MHz – 1 GHz     | -57 dBm                                                                                                                        | 100 kHz               |      |
+| 1 GHz – 12.75 GHz | -47 dBm                                                                                                                        | 1 MHz                 |      |
+| NOTE:             | The frequency range from $F_{BW\ RF,DL,low} - 10\ MHz$ to $F_{BW\ RF,DL,high} + 10\ MHz$ may be excluded from the requirement. |                       |      |
+
+In addition to the requirements in Table 7.6.1.1-1, the power of any spurious emission shall not exceed the levels specified for Protection of the E-UTRA FDD BS receiver of own or different BS in subclause 6.6.2.2.4 and for Co-existence with other systems in the same geographical area in subclause 6.6.2.2.2. In addition, the co-existence requirements for co-located Base Stations specified in subclause 6.6.2.2.3 may also be applied.
+
+### 7.6.2 Band category 2
+
+For GSM, a requirement for “Spurious emissions from the receiver antenna connector” is defined in TS 45.005 [5], with the same requirement levels as in UTRA and E-UTRA, which are taken from [15].
+
+The measurement bandwidth applied is however not the same as the recommended values in SM.329 [6] and ERC/REC 74-01 [15], since it varies with the offset from the downlink operating band edge rather than with the frequency, in the same way as for transmitter spurious emissions (see also subclause 6.6.2.2). As for transmitter spurious emissions, this results in that some GSM BTS limits in TS 45.005 [5] are stricter than in [15], while some are more relaxed.
+
+In order to keep the level of the spurious emission requirements for GSM BTS from TS 45.005 [5] and at the same time align with the recommended limits in [15], the stricter of the two shall apply for BC2.
+
+#### 7.6.2.1 Minimum requirement (BC2)
+
+The receiver spurious emission limits for operation in Band Category two are the same as defined in subclause 7.6.1 and table 7.6.1.1-1, with the requirement in Table 7.6.2.1-1 applying as additional mandatory limits for BC2.
+
+**Table 7.6.2.1-1: Additional mandatory receiver spurious emission limits in BC2**
+
+| Frequency range  | Frequency offset from transmitter operating band edge | Maximum level | Measurement Bandwidth |
+|------------------|-------------------------------------------------------|---------------|-----------------------|
+| 30 MHz – 1 GHz   | 10 – 20 MHz                                           | -57 dBm       | 300 kHz               |
+|                  | 20 – 30 MHz                                           |               | 1 MHz                 |
+|                  | ≥ 30 MHz                                              |               | 3 MHz                 |
+| 1GHz – 12.75 GHz | ≥ 30 MHz                                              | -47 dBm       | 3 MHz                 |
+
+### 7.6.3 Band category 3
+
+The requirement specified for UTRA TDD receiver spurious emissions consists of general and additional requirements in [3]. General receiver spurious emission requirements are -57dBm/100kHz for 30MHz ~ 1GHz and -47dBm/1MHz for 1GHz ~ 12.5GHz. It is aligned with E-UTRA.
+
+For 1.28Mcps UTRA TDD(TD-SCDMA), the spurious emission requirements apply with the exception of frequencies between 4 MHz below the first carrier frequency and 4 MHz above the last carrier frequency used by the BS. For MSR, in order to align with the way transmitter unwanted emissions are defined in Clause 6.6.1 and 6.6.2, only frequencies that are more than 10 MHz below the lower RF bandwidth edge and more than 10 MHz above the upper RF bandwidth edge are covered by the requirement. The frequency range between those points may be excluded.
+
+In UTRA TDD specification, the additional receiver spurious emission requirements are for protection of TDD bands or FDD bands. These are -83dBm/1.28MHz for different frequency band. Though the measurement bandwidth is different, it can be aligned to -94dBm/100kHz, i.e.  $-83\text{dBm}/1.28\text{MHz} = -94.07\text{dBm}/100\text{kHz}$ .
+
+In E-UTRA, the requirement for co-located Base Stations is -96dBm/100kHz. Since MSR should satisfy requirements for both E-UTRA and UTRA, a choice of this more strict limitation as MSR receiver spurious emission requirements can also meet the additional requirements for co-location and protection of BS operating in the same operating band for UTRA TDD. It is the same to MSR Tx spurious limits as for co-location, and can be expressed as a direct reference to the additional Tx spurious emission requirements in subclause 6.6.2.3.3.
+
+Though in UTRA TDD specification, only one type of additional spurious emission requirements was defined instead of separated co-existence and co-location requirements, the Tx spurious emission requirements for co-existence with other systems in the same geographical area can also be applied for Rx spurious emissions. MSR Rx spurious limits for co-existence with other systems in the same geographical area can be expressed as a direct reference to the additional Tx spurious emission requirements in subclause 6.6.2.3.2.
+
+#### 7.6.3.1 Minimum requirement (BC3)
+
+The receiver spurious emissions power is the power of emissions generated or amplified in a receiver that appears at the BS receiver antenna connector. For all TDD BS with common RX and TX antenna port the requirement applies during the Transmitter OFF period.
+
+The power of any spurious emission shall not exceed the levels in Table 7.6.3.1-1:
+
+**Table 7.6.3.1-1: General spurious emission minimum requirement**
+
+| Frequency range                                                                                                                      | Maximum level | Measurement Bandwidth | Note |
+|--------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------|------|
+| 30MHz – 1 GHz                                                                                                                        | -57 dBm       | 100 kHz               |      |
+| 1 GHz – 12.75 GHz                                                                                                                    | -47 dBm       | 1 MHz                 |      |
+| NOTE: The frequency range from $F_{BW\ RF,DL,low} - 10\ MHz$ to $F_{BW\ RF,DL,high} + 10\ MHz$ may be excluded from the requirement. |               |                       |      |
+
+In addition to the requirements in Table 7.6.3.1-1, the power of any spurious emission shall not exceed the levels specified for Co-existence with other systems operating in other bands in the same geographical area in subclause 6.6.2.3.2 and for Co-located Base Stations specified in subclause 6.6.2.3.3. These additional spurious emission requirements shall be applied to a BS operating in the same operating band and the frequency range from  $F_{BW\ RF,DL,low} - 10\ MHz$  to  $F_{BW\ RF,DL,high} + 10\ MHz$  shall be excluded.
+
+## 7.7 Receiver intermodulation
+
+### 7.7.1 Band category 1
+
+#### 7.7.1.1 Intermodulation requirement
+
+The UTRA intermodulation requirement is based on CW and UTRA interfering signals with mean power of -48 dBm and with 7.5MHz and 17.5MHz offsets from the channel edge of the wanted signal, respectively.
+
+The E-UTRA intermodulation requirement is based on CW and E-UTRA interfering signals with mean power of -52 dBm. The channel bandwidth of the interfering E-UTRA signal is equal to the channel bandwidth of the wanted signal for channel bandwidths less than 5 MHz, for wider channel bandwidths of the wanted signal the interfering signal is a 5 MHz E-UTRA signal. The offset for the CW signal from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is equal to  $1.5 \cdot E\text{-UTRA channel bandwidth of the interfering signal}$ . The interfering E-UTRA signal is placed so that the intermodulation product falls on the effective channel bandwidth of the wanted signal.
+
+Combining the requirements for UTRA and E-UTRA scenarios, a generic MSR intermodulation requirement based on the CW and E-UTRA interfering signals with mean power of -48 dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+For channel bandwidths equal to or higher than 5MHz, there is a 17.5MHz fixed offset for 5MHz E-UTRA interfering signal. The CW offsets varies from 7.125MHz to 7.5MHz in order to have an intermodulation product at the correct frequency positions.
+
+##### 7.7.1.1.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.1.1.1-1 and 7.7.1.1.1-2, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.1.1.1-1: Intermodulation requirement for band category 1**
+
+| Interfering Signal mean power [dBm]                                               | Wanted Signal mean power [dBm] | Type of interfering signal |
+|-----------------------------------------------------------------------------------|--------------------------------|----------------------------|
+| -48                                                                               | PREFSENS +6 dB*                | See Table 7.7.1.1.1-2      |
+| NOTE*: PREFSENS depends on the RAT and on the channel bandwidth, see section 7.2. |                                |                            |
+
+**Table 7.7.1.1.1-2: Interfering signal for intermodulation requirement in band category 1**
+
+| RAT of the carrier    | Interfering signal centre frequency offset from the RF bandwidth edge [MHz] | Type of interfering signal |
+|-----------------------|-----------------------------------------------------------------------------|----------------------------|
+| E-UTRA 1.4 MHz        | 2.0                                                                         | CW                         |
+|                       | 4.9                                                                         | 1.4MHz E-UTRA signal       |
+| E-UTRA 3 MHz          | 4.4                                                                         | CW                         |
+|                       | 10.5                                                                        | 3MHz E-UTRA signal         |
+| UTRA and E-UTRA 5 MHz | 7.5                                                                         | CW                         |
+|                       | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 10 MHz         | 7.375                                                                       | CW                         |
+|                       | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 15 MHz         | 7.25                                                                        | CW                         |
+|                       | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 20 MHz         | 7.125                                                                       | CW                         |
+|                       | 17.5                                                                        | 5MHz E-UTRA signal         |
+
+#### 7.7.1.2 Narrowband intermodulation
+
+The UTRA narrowband intermodulation requirement is based on CW and GSM interfering signals with mean power of -47dBm and 1MHz and 3.4MHz offsets from the channel edge of the wanted signal, respectively. It should be noted the GSM signal does not exist in Band Category 1.
+
+The E-UTRA narrowband intermodulation requirement is based on CW and E-UTRA 1RB interfering signals with mean power of -52dBm. The offsets from the channel edge of the wanted signal are dependent on the E-UTRA channel bandwidth.
+
+A generic MSR narrowband intermodulation requirement based on CW and E-UTRA 1RB interfering signals with mean power of -52dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+The 970kHz offset corresponds to the distance between the RF bandwidth edge and the fifth closest RB centre frequency of the E-UTRA 1.4MHz interfering signal. The 960kHz offset corresponds to the distance between the RF bandwidth edge and the fifth closest RB centre frequency of the E-UTRA 3MHz interfering signal. The 1060kHz, 1240kHz, 1600kHz and 1780kHz offsets correspond to the distances between the RF bandwidth edge and the fifth, sixth, eighth and ninth closest RB centre frequency of the E-UTRA 5MHz interfering signal, respectively. The CW signal is inside the interfering RB closest to the RF bandwidth edge and adjusted to centre the intermodulation product on the outermost RB of the wanted E-UTRA signal. For a UTRA wanted signal the intermodulation product falls at the edge of the flat part of the wanted signal spectrum.
+
+##### 7.7.1.2.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.1.2.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.1.2.1-1: Narrowband intermodulation requirement for band category 1**
+
+| RAT of the carrier | Wanted signal mean power [dBm]                 | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] | Type of interfering signal    |
+|--------------------|------------------------------------------------|-------------------------------------|-------------------------------------------------------------------------|-------------------------------|
+| E-UTRA 1.4MHz      | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 260                                                                     | CW                            |
+|                    |                                                | -52                                 | 970                                                                     | 1.4 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 3MHz        | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 260                                                                     | CW                            |
+|                    |                                                | -52                                 | 960                                                                     | 3.0 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 5MHz        | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 360                                                                     | CW                            |
+|                    |                                                | -52                                 | 1060                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 10MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 325                                                                     | CW                            |
+|                    |                                                | -52                                 | 1240                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 15MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 380                                                                     | CW                            |
+|                    |                                                | -52                                 | 1600                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| E-UTRA 20MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 345                                                                     | CW                            |
+|                    |                                                | -52                                 | 1780                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| UTRA               | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 345                                                                     | CW                            |
+|                    |                                                | -52                                 | 1780                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+
+NOTE\*:  $P_{\text{REFSENS}}$  depends on the RAT and on the channel bandwidth, see section 7.2.
+
+NOTE\*\*: Interfering signal consisting of one resource block positioned at the stated offset.
+
+NOTE\*\*\*: For E-UTRA, this requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals.
+
+### 7.7.2 Band category 2
+
+#### 7.7.2.1 Intermodulation requirement
+
+Similar MSR RX intermodulation requirements as for Band Category 1 should also apply for Band Category 2 with a GSM wanted signal level of  $P_{\text{REFSENS}} + 3 \text{ dB}$ . This gives added value to GSM systems since intermodulation requirement for wideband modulated interferers based on scenarios investigated for E-UTRA are currently not covered in the existing GSM specifications.
+
+A generic MSR intermodulation requirement based on CW and E-UTRA interfering signals with mean power of -48 dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+##### 7.7.2.1.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.2.1.1-1 and 7.7.2.1.1-2, the following requirements shall be met:
+
+- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.2.
+- For any UTRA carrier, the BER shall not exceed 0.001.
+
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.2.1.1-1: Intermodulation requirement for band category 2**
+
+| Interfering Signal mean power [dBm]                                                                           | Wanted Signal mean power [dBm]             | Type of interfering signal |
+|---------------------------------------------------------------------------------------------------------------|--------------------------------------------|----------------------------|
+| -48                                                                                                           | $P_{\text{REFSENS}} + x^{**} \text{ dB}^*$ | See Table 7.7.2.1.1-2      |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and on the channel bandwidth, see section 7.2.                 |                                            |                            |
+| NOTE**: x is equal to 3 in case of GSM wanted signal and equal to 6 in case of UTRA or E-UTRA wanted signals. |                                            |                            |
+
+**Table 7.7.2.1.1-2: Interfering signal for intermodulation requirement in band category 2**
+
+| RAT of the carrier   | Interfering signal centre frequency offset from the RF bandwidth edge [MHz] | Type of interfering signal |
+|----------------------|-----------------------------------------------------------------------------|----------------------------|
+| E-UTRA 1.4MHz        | 2.1                                                                         | CW                         |
+|                      | 4.9                                                                         | 1.4MHz E-UTRA signal       |
+| E-UTRA 3MHz          | 4.5                                                                         | CW                         |
+|                      | 10.5                                                                        | 3MHz E-UTRA signal         |
+| UTRA and E-UTRA 5MHz | 7.5                                                                         | CW                         |
+|                      | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 10MHz         | 7.375                                                                       | CW                         |
+|                      | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 15MHz         | 7.25                                                                        | CW                         |
+|                      | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 20MHz         | 7.125                                                                       | CW                         |
+|                      | 17.5                                                                        | 5MHz E-UTRA signal         |
+| GSM                  | 7.575                                                                       | CW                         |
+|                      | 17.5                                                                        | 5MHz E-UTRA signal         |
+
+#### 7.7.2.2 Narrowband intermodulation
+
+Similar MSR narrowband intermodulation requirements as for band category 1 should also apply for band category 2 with a GSM wanted signal power of  $P_{\text{REFSENS}} + 3 \text{ dB}$  as for other GSM requirements. This gives added value to GSM systems since narrowband intermodulation requirement with narrowband modulated interferers based on the scenario investigated for the E-UTRA is currently not covered in the existing GSM specifications. The more strict GSM MC-BTS narrowband intermodulation requirements levels based on CW interferer are covered as MSR single RAT requirement for GSM and also apply for GSM carriers in multi-RAT operation.
+
+A generic MSR narrowband intermodulation requirement based on CW and E-UTRA 1RB interfering signals with mean power of -52dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+##### 7.7.2.2.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.2.2.1-1, the following requirements shall be met:
+
+- For any GSM/EDGE carrier, the conditions are specified in TS 45.005 [5], Annex P.2.2.
+- For any UTRA carrier, the BER shall not exceed 0.001.
+
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.2.2.1-1: Narrowband intermodulation requirement for band category 2**
+
+| RAT of the carrier | Wanted signal mean power [dBm]                 | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] | Type of interfering signal    |
+|--------------------|------------------------------------------------|-------------------------------------|-------------------------------------------------------------------------|-------------------------------|
+| E-UTRA 1.4MHz      | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 270                                                                     | CW                            |
+|                    |                                                | -52                                 | 790                                                                     | 1.4 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 3MHz        | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 270                                                                     | CW                            |
+|                    |                                                | -52                                 | 780                                                                     | 3.0 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 5MHz        | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 360                                                                     | CW                            |
+|                    |                                                | -52                                 | 1060                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 10MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 325                                                                     | CW                            |
+|                    |                                                | -52                                 | 1240                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 15MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 380                                                                     | CW                            |
+|                    |                                                | -52                                 | 1600                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| E-UTRA 20MHz       | $P_{\text{REFSENS}} + 6 \text{ dB}^*$<br>(***) | -52                                 | 345                                                                     | CW                            |
+|                    |                                                | -52                                 | 1780                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| UTRA               | $P_{\text{REFSENS}} + 6 \text{ dB}^*$          | -52                                 | 345                                                                     | CW                            |
+|                    |                                                | -52                                 | 1780                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| GSM                | $P_{\text{REFSENS}} + 3 \text{ dB}^*$          | -52                                 | 340                                                                     | CW                            |
+|                    |                                                | -52                                 | 880                                                                     | 5MHz E-UTRA signal, 1 RB**    |
+
+NOTE\*:  $P_{\text{REFSENS}}$  depends on the RAT and on the channel bandwidth, see section 7.2.
+
+NOTE\*\*: Interfering signal consisting of one resource block positioned at the stated offset.
+
+NOTE\*\*\*: For E-UTRA, this requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals.
+
+In addition, GSM MC-BTS receiver inter-modulation requirements as stated in TS 45.005 [5] apply both for GSM single RAT cases as well as for any GSM carrier in multi-RAT operation.
+
+### 7.7.3 Band category 3
+
+#### 7.7.3.1 Intermodulation requirement
+
+The UTRA TDD intermodulation requirement is based on CW and UTRA interfering signals with mean power of -48 dBm and with 2.4MHz and 5.6MHz offsets for 1.28Meps TDD option from the channel edge of the wanted signal, respectively.
+
+The E-UTRA intermodulation requirement is based on CW and E-UTRA interfering signals with mean power of -52 dBm. The channel bandwidth of the interfering E-UTRA signal is equal to the channel bandwidth of the wanted signal for channel bandwidths less than 5 MHz, for wider channel bandwidths of the wanted signal the interfering signal is a 5 MHz E-UTRA signal. The offset for the CW signal from the channel edge of the wanted signal is dependent on the E-UTRA channel bandwidth and is equal to  $1.5 \cdot \text{E-UTRA channel bandwidth}$  of the interfering signal. The interfering E-UTRA signal is placed so that the intermodulation product falls on the effective channel bandwidth of the wanted signal.
+
+Combining the requirements for UTRA and E-UTRA scenarios, a generic MSR intermodulation requirement based on the CW and E-UTRA (or 1.28Meps UTRA TDD) interfering signals with mean power of -48dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+For channel bandwidths equal to or higher than 5MHz, there is a 17.5MHz fixed offset for 5MHz E-UTRA interfering signal. The CW offsets varies from 7.125MHz to 7.5MHz. For 1.28Mcps UTRA TDD, there is a 5.6MHz offset for 1.6MHz UTRA TDD interfering signal and CW offset of 2.3MHz, in order to have an intermodulation product at the correct frequency positions.
+
+##### 7.7.3.1.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA (or 1.28Mcps UTRA TDD) signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.3.1.1-1 and 7.7.3.1.1-2, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.3.1.1-1: Intermodulation requirement for band category 3**
+
+| Interfering Signal mean power [dBm]                                                           | Wanted Signal mean power [dBm]      | Type of interfering signal |
+|-----------------------------------------------------------------------------------------------|-------------------------------------|----------------------------|
+| -48                                                                                           | $P_{\text{REFSENS}} + 6\text{dB}^*$ | See Table 7.7.3.1.1-2      |
+| NOTE*: $P_{\text{REFSENS}}$ depends on the RAT and on the channel bandwidth, see section 7.2. |                                     |                            |
+
+**Table 7.7.3.1.1-2: Interfering signal for intermodulation requirement in band category 3**
+
+| RAT of the outermost carrier | Interfering signal centre frequency offset from the RF bandwidth edge [MHz] | Type of interfering signal |
+|------------------------------|-----------------------------------------------------------------------------|----------------------------|
+| E-UTRA 1.4 MHz               | 2.0                                                                         | CW                         |
+|                              | 4.9                                                                         | 1.4MHz E-UTRA signal       |
+| E-UTRA 3 MHz                 | 4.4                                                                         | CW                         |
+|                              | 10.5                                                                        | 3MHz E-UTRA signal         |
+| E-UTRA 5 MHz                 | 7.5                                                                         | CW                         |
+|                              | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 10 MHz                | 7.375                                                                       | CW                         |
+|                              | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 15 MHz                | 7.25                                                                        | CW                         |
+|                              | 17.5                                                                        | 5MHz E-UTRA signal         |
+| E-UTRA 20 MHz                | 7.125                                                                       | CW                         |
+|                              | 17.5                                                                        | 5MHz E-UTRA signal         |
+| 1.28Mcps UTRA TDD            | 2.3                                                                         | CW                         |
+|                              | 5.6                                                                         | 1.28Mcps UTRA TDD signal   |
+
+#### 7.7.3.2 Narrowband intermodulation
+
+The UTRA TDD have not narrowband intermodulation requirement in the UTRA TDD specification since there is no narrowband interfering inside TDD band. But for MSR, it is possible that a narrow band E-UTRA signal exist in the adjacent channel. So, in BC3 MSR NodeB, the UTRA TDD narrowband intermodulation requirement should be based on the E-UTRA narrowband intermodulation requirement.
+
+The E-UTRA narrowband intermodulation requirement is based on CW and E-UTRA 1RB interfering signals with mean power of -52dBm. The offsets from the channel edge of the wanted signal are dependent on the E-UTRA channel bandwidth.
+
+A generic MSR narrowband intermodulation requirement based on CW and E-UTRA 1RB interfering signals with mean power of -52dBm is adopted. The interfering signal offsets from the RF bandwidth edge are dependent on the
+
+RAT/E-UTRA channel bandwidth and are defined in such a way that the whole intermodulation product falls inside the effective channel bandwidth of the outermost carrier.
+
+The 970kHz offset corresponds to the distance between the RF bandwidth edge and the fifth closest RB centre frequency of the E-UTRA 1.4MHz interfering signal. The 960kHz offset corresponds to the distance between the RF bandwidth edge and the fifth closest RB centre frequency of the E-UTRA 3MHz interfering signal. The 1060kHz, 1240kHz, 1600kHz and 1780kHz offsets correspond to the distances between the RF bandwidth edge and the fifth, sixth, eighth and ninth closest RB centre frequency of the E-UTRA 5MHz interfering signal, respectively. The CW signal is inside the interfering RB closest to the RF bandwidth edge and adjusted to centre the intermodulation product on the outermost RB of the wanted E-UTRA signal. For a UTRA wanted signal the intermodulation product falls at the edge of the flat part of the wanted signal spectrum.
+
+##### 7.7.3.2.1 Minimum requirement
+
+Third and higher order mixing of the two interfering RF signals can produce an interfering signal in the band of the desired channel. Intermodulation response rejection is a measure of the capability of the receiver to receive a wanted signal on its assigned channel frequency in the presence of two interfering signals which have a specific frequency relationship to the wanted signal. Interfering signals shall be a CW signal and an E-UTRA 1RB signal as specified in Annex A.
+
+For the wanted signal at the assigned channel frequency and two interfering signals coupled to the Base Station antenna input, using the parameters in Table 7.7.3.2.1-1, the following requirements shall be met:
+
+- For any UTRA carrier, the BER shall not exceed 0.001.
+- For any E-UTRA carrier, the throughput shall be  $\geq 95\%$  of the maximum throughput of the reference measurement channel.
+
+**Table 7.7.3.2.1-1: Narrowband intermodulation requirement for band category 3**
+
+| RAT of the outermost carrier | Wanted signal mean power [dBm]               | Interfering signal mean power [dBm] | Interfering RB centre frequency offset from the RF bandwidth edge [kHz] | Type of interfering signal    |
+|------------------------------|----------------------------------------------|-------------------------------------|-------------------------------------------------------------------------|-------------------------------|
+| E-UTRA 1.4MHz                | $P_{\text{REFSENS}} + 6\text{dB}^*$          | -52                                 | 260                                                                     | CW                            |
+|                              |                                              | -52                                 | 970                                                                     | 1.4 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 3MHz                  | $P_{\text{REFSENS}} + 6\text{dB}^*$          | -52                                 | 260                                                                     | CW                            |
+|                              |                                              | -52                                 | 960                                                                     | 3.0 MHz E-UTRA signal, 1 RB** |
+| E-UTRA 5MHz                  | $P_{\text{REFSENS}} + 6\text{dB}^*$          | -52                                 | 360                                                                     | CW                            |
+|                              |                                              | -52                                 | 1060                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 10MHz                 | $P_{\text{REFSENS}} + 6\text{dB}^*$<br>(***) | -52                                 | 325                                                                     | CW                            |
+|                              |                                              | -52                                 | 1240                                                                    | 5 MHz E-UTRA signal, 1 RB**   |
+| E-UTRA 15MHz                 | $P_{\text{REFSENS}} + 6\text{dB}^*$<br>(***) | -52                                 | 380                                                                     | CW                            |
+|                              |                                              | -52                                 | 1600                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| E-UTRA 20MHz                 | $P_{\text{REFSENS}} + 6\text{dB}^*$<br>(***) | -52                                 | 345                                                                     | CW                            |
+|                              |                                              | -52                                 | 1780                                                                    | 5MHz E-UTRA signal, 1 RB**    |
+| 1.28Mcps UTRA TDD            | $P_{\text{REFSENS}} + 6\text{dB}^*$          | -52                                 | 190                                                                     | CW                            |
+|                              |                                              | -52                                 | 970                                                                     | 1.4MHz E-UTRA signal, 1 RB**  |
+
+NOTE\*:  $P_{\text{REFSENS}}$  depends on the RAT and on the channel bandwidth, see section 7.2.  
+NOTE\*\*: Interfering signal consisting of one resource block positioned at the stated offset.  
+NOTE\*\*\*: For E-UTRA, this requirement shall apply only for a FRC A1-3 mapped to the frequency range at the channel edge adjacent to the interfering signals.
+
+## 7.8 In-channel selectivity
+
+The in-channel selectivity is a measure of the receiver ability to receive a wanted signal at its assigned resource block locations in the presence of an interfering signal received at a larger power spectral density. In this condition a throughput requirement shall be met for a specified reference measurement channel. The interfering signal shall be an E-UTRA signal as specified in TS 36.104 [4], Annex C.
+
+The in-channel selectivity requirement is applicable only in case of E-UTRA within the context of Multi Standard Radio (MSR).
+
+### 7.8.1 Minimum requirement
+
+For E-UTRA, the minimum requirement is specified in TS 36.104 [4], section 7.4.1.
+
+# --- 8 Other requirements
+
+## 8.1 EMC
+
+EMC requirements are today covered in the following specifications:
+
+- UTRA EMC requirements are covered by TS 25.113 [24].
+- E-UTRA EMC requirements are covered by TS 36.113 [25].
+- There is no 3GPP specification for GSM/EDGE EMC requirements. These are covered by the ETSI standard EN 301 489-8 [26].
+
+The EMC requirements are to a large part universal and based on international recommendations. It is therefore possible to draft a common EMC specification for an MSR Base Station that in principle covers both multi-RAT and single-RAT operation. It can be noted that the European series of EMC-standards is presently updated with a new version of EN 301 489-23 [27], which will include both UTRA and E-UTRA, thereby already covering multiple RATs.
+
+The following parts of an EMC specification are by definition generic to multiple RATs:
+
+- General test conditions
+- Exclusion bands
+- General performance assessment
+- Applicability of emissions and immunity
+- Emission requirements
+- Immunity requirements
+
+The following parts of an EMC specification will have to remain RAT specific:
+
+- Test conditions (test models)
+- Performance assessment in uplink and downlink
+- Performance criteria for BS
+
+The resulting specification TS 37.113 will therefore for most parts be generic to all RATs (E-UTRA, UTRA and GSM/EDGE).
+
+## 8.2 Performance requirements
+
+Performance requirements specify the ability of the BS to correctly demodulate signals in various conditions and configurations. For UTRA and E-UTRA the requirements specify a minimum throughput, BLER or BER that shall be
+
+achieved at a specific SNR. For GSM/EDGE the requirements specify a maximum FER, BLER or BER that shall be achieved at specific sensitivity levels I and specific carrier-to-interference ratios (C/I).
+
+For E-UTRA carriers the minimum requirement is defined in TS 36.104 [4], section 8.
+
+For UTRA FDD carriers the minimum requirement is defined in TS 25.104 [2], section 8.
+
+For UTRA TDD carriers the minimum requirement is defined in TS 25.105 [3], section 8.
+
+For GSM/EDGE, the minimum requirements for reference sensitivity level and reference interference level are defined in TS 45.005 [5], applicable parts of subclauses 6.2, 6.3, 6.4, 6.5 and 6.6. The conditions specified in TS 45.005 [5], Annex P.1 are valid for GSM sensitivity and interference performance.
+
+In the WI objective in subclause 4.1 it is clearly stated that performance requirements should not be a part of the MSR specifications. Thus these requirements apply together with the RF requirements in the MSR specification, but should not be a part of the MSR specifications.
+
+# --- 9 Test specification
+
+## 9.1 BS test configurations
+
+The test configurations are described in three steps. First there is a definition of Capability Sets (CS), which defines the RAT combinations that can be declared. Then the concept of Test Configurations (TC) is explained and finally, the full Mapping of RF requirements and Capability Sets to applicable Test Configurations is presented in two tables.
+
+### 9.1.1 Definition of Capability Sets (CS)
+
+Subclause 4.7 of the test specification TS 37.141 (Manufacturer's declarations of supported RF configurations) will contain defined Capability Sets (CS), the support of which is subject to manufacturers declaration.
+
+Table 9.1.1-1 shows the six capability sets CS1 to CS6, based on the possible RAT combinations that can be declared. The following abbreviations are used below:
+
+|    |                               |
+|----|-------------------------------|
+| CS | Capability Set                |
+| MC | multi-carrier (in single RAT) |
+| SC | single carrier                |
+| MR | multi-RAT                     |
+| SR | single-RAT                    |
+| TC | Test Configuration,           |
+
+Table 9.1.1-1. Example capability sets
+
+| Capability Set supported by the BS | CS1              | CS2                | CS3                                                        | CS4                                                 | CS5                                                     | CS6                                                                                                                                        |
+|------------------------------------|------------------|--------------------|------------------------------------------------------------|-----------------------------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| Supported RATs                     | UTRA (MC)        | E-UTRA (MC)        | UTRA, E-UTRA                                               | GSM, UTRA                                           | GSM, E-UTRA                                             | GSM, UTRA, E-UTRA                                                                                                                          |
+| Supported configurations           | SR UTRA (SC, MC) | SR E-UTRA (SC, MC) | MR UTRA + E-UTRA<br>SR UTRA (SC, MC)<br>SR E-UTRA (SC, MC) | MR GSM + UTRA<br>SR GSM (MCBTS)<br>SR UTRA (SC, MC) | MR GSM + E-UTRA<br>SR GSM (MCBTS)<br>SR E-UTRA (SC, MC) | MR GSM + UTRA + E-UTRA<br>MR GSM + UTRA<br>MR GSM + E-UTRA<br>MR UTRA + E-UTRA<br>SR GSM (MCBTS)<br>SR UTRA (SC, MC)<br>SR E-UTRA (SC, MC) |
+| Applicable BC                      | BC1, BC2 or BC3  | BC1, BC2 or BC3    | BC1, BC2 or BC3                                            | BC2                                                 | BC2                                                     | BC2                                                                                                                                        |
+
+Example: A BS is declared to support CS6. This implies that the BS is capable to support the following configurations (applicable only to BC2):
+
+- MR GSM + UTRA + E-UTRA
+- MR GSM + UTRA
+- MR GSM + E-UTRA
+- MR UTRA + E-UTRA
+- SR GSM (MCBTS)
+- SR UTRA (SC, MC)
+- SR E-UTRA (SC, MC)
+
+It is assumed that a manufacturer declares support of one and only one Capability Set. The applicable Test Configurations will then be defined for each RF requirement and Capability Set. Not every supported configuration within a CS will need to be tested with a specific TC, but a judicious choice is made among the supported configurations to ensure good test coverage.
+
+### 9.1.2 Definition of Test Configurations (TC)
+
+Subclause 4.8 in TS 37.141 (MSR test configurations) will contain the definition of the (generic) Test Configurations (TC) which will be used to test RF requirements. Each TC will thus correspond to a specific configuration appearing within the Capability Sets. As an example, TC2 will be an incarnation of the SR E-UTRA MC configuration.
+
+The idea with the Test Configuration concept is to re-use a few TCs across a wider range of RF requirements, rather than “custom designing” TCs for each and every RF requirement. This reduces the number of configurations to describe and enables a more compact and generic description of the conformance testing.
+
+### 9.1.3 Mapping from test requirement to test configuration
+
+The present clause defines which requirements that apply and what test configurations to use for conformance testing. This is specified in the tables below for single-RAT Multi-carrier in Table 9.1.3-1 and for multi-RAT Base Stations in Table 9.1.3-2. Requirements apply according to the declared RAT Capability Set (CS) of the MSR Base Station and the Band Category of the declared operating band (BC1, BC2 or BC3), as listed in the heading of each table. Some
+
+requirements listed in the tables may not be mandatory or they may apply only regionally. This is further specified for each requirement in clause 6 and 7, and in Table 4.5-1.
+
+For a declared RAT Capability Set (CS), only the requirements listed in the column for that CS apply. Requirements listed under other CS than the declared CS need not be tested.
+
+The clause references to BS test cases below are based on the clause numbering in TS 37.104 and may have to be updated for inclusion in TS 37.141.
+
+Table 9.1.3-1: Test configurations for capability sets for Multi-RAT capable BS
+
+| Capability Set                                             | UTRA + E-UTRA (CS 3) |             |                                               | GSM+ UTRA (CS 4) | GSM + E-UTRA (CS 5) | GSM + UTRA + E-UTRA (CS 6) |
+|------------------------------------------------------------|----------------------|-------------|-----------------------------------------------|------------------|---------------------|----------------------------|
+| BS test case                                               | BC1                  | BC2         | BC3                                           | BC2              | BC2                 | BC2                        |
+| <b>6.2 Base Station output power</b>                       | -                    | -           | -                                             | -                | -                   | -                          |
+| 6.2.1 Minimum requirement                                  | TC3a                 | TC3a        | TC3b                                          | TC4a             | TC4b                | TC4c                       |
+| 6.2.2 Additional requirement (only for band 34)            | N/A                  | N/A         | Compliance stated by manufacturer declaration | N/A              | N/A                 | N/A                        |
+| 6.2.3 E-UTRA minimum requirement for DL RS power           | (TS 36.141)          | (TS 36.141) | (TS 36.141)                                   | N/A              | (TS 36.141)         | (TS 36.141)                |
+| 6.2.4 UTRA FDD minimum requirement for primary CPICH power | (TS 25.141)          | (TS 25.141) | N/A                                           | (TS 25.141)      | N/A                 | (TS 25.141)                |
+| 6.2.5 UTRA TDD minimum requirement for primary CCPCH power | N/A                  | N/A         | (TS 25.142)                                   | N/A              | N/A                 | N/A                        |
+| <b>6.3 Output power dynamics</b>                           | -                    | -           | -                                             | -                | -                   | -                          |
+| 6.3.1 E-UTRA minimum requirement                           | (TS 36.141)          | (TS 36.141) | (TS 36.141)                                   | N/A              | (TS 36.141)         | (TS 36.141)                |
+| 6.3.2 UTRA FDD minimum requirement                         | (TS 25.141)          | (TS 25.141) | N/A                                           | (TS 25.141)      | N/A                 | (TS 25.141)                |
+| 6.3.3 UTRA TDD minimum requirement                         | N/A                  | N/A         | (TS 25.142)                                   | N/A              | N/A                 | N/A                        |
+| 6.3.4 GSM/EDGE minimum requirement                         | N/A                  | N/A         | N/A                                           | (TS 51.021)      | (TS 51.021)         | (TS 51.021)                |
+| <b>6.4 Transmit ON/OFF power</b>                           | -                    | -           | -                                             | -                | -                   | -                          |
+| 6.4.1 Transmitter OFF power                                | N/A                  | N/A         | TC3b                                          | N/A              | N/A                 | N/A                        |
+| 6.4.2 Transmitter transient period                         | N/A                  | N/A         | TC3b                                          | N/A              | N/A                 | N/A                        |
+| <b>6.5 Transmitted signal quality</b>                      | -                    | -           | -                                             | -                | -                   | -                          |
+| <b>6.5.1 Modulation quality</b>                            | -                    | -           | -                                             | -                | -                   | -                          |
+| 6.5.1.1 E-UTRA minimum requirement                         | [TC3a]               | [TC3a]      | [TC3b]                                        | N/A              | [TC4b]              | [TC4c]                     |
+| 6.5.1.2 UTRA FDD minimum requirement                       | [TC3a]               | [TC3a]      | N/A                                           | [TC4a]           | N/A                 | [TC4c]                     |
+| 6.5.1.3 UTRA TDD minimum requirement                       | N/A                  | N/A         | [TC3b]                                        | N/A              | N/A                 | N/A                        |
+| 6.5.1.4 GSM/EDGE minimum requirement                       | N/A                  | N/A         | N/A                                           | [TC4a]           | [TC4b]              | [TC4c]                     |
+
+| Capability Set                                                  | UTRA + E-UTRA<br>(CS 3)                    |               |                                            | GSM+<br>UTRA<br>(CS 4) | GSM +<br>E-UTRA<br>(CS 5) | GSM + UTRA<br>+ E-UTRA<br>(CS 6) |
+|-----------------------------------------------------------------|--------------------------------------------|---------------|--------------------------------------------|------------------------|---------------------------|----------------------------------|
+| BS test case                                                    | BC1                                        | BC2           | BC3                                        | BC2                    | BC2                       | BC2                              |
+| <b>6.5.2 Frequency error</b>                                    | -                                          | -             | -                                          | -                      | -                         | -                                |
+| 6.5.2.1 E-UTRA minimum requirement                              | [(TS 36.141)]                              | [(TS 36.141)] | [(TS 36.141)]                              | N/A                    | [(TS 36.141)]             | [(TS 36.141)]                    |
+| 6.5.2.2 UTRA FDD minimum requirement                            | [(TS 25.141)]                              | [(TS 25.141)] | N/A                                        | [(TS 25.141)]          | N/A                       | [(TS 25.141)]                    |
+| 6.5.2.3 UTRA TDD minimum requirement                            | N/A                                        | N/A           | [(TS 25.142)]                              | N/A                    | N/A                       | N/A                              |
+| 6.5.2.4 GSM/EDGE minimum requirement                            | N/A                                        | N/A           | N/A                                        | [(TS 51.021)]          | [(TS 51.021)]             | [(TS 51.021)]                    |
+| <b>6.5.3 Time alignment between transmitter branches</b>        | -                                          | -             | -                                          | -                      | -                         | -                                |
+| 6.5.3.1 E-UTRA minimum requirement                              | (TS 36.141)                                | (TS 36.141)   | (TS 36.141)                                | N/A                    | (TS 36.141)               | (TS 36.141)                      |
+| 6.5.3.2 UTRA FDD minimum requirement                            | (TS 25.141)                                | (TS 25.141)   | N/A                                        | (TS 25.141)            | N/A                       | (TS 25.141)                      |
+| 6.5.3.3 UTRA TDD minimum requirement                            | N/A                                        | N/A           | (TS 25.142)                                | N/A                    | N/A                       | N/A                              |
+| <b>6.6 Unwanted emissions</b>                                   | -                                          | -             | -                                          | -                      | -                         | -                                |
+| <b>6.6.1 Transmitter spurious emissions</b>                     | -                                          | -             | -                                          | -                      | -                         | -                                |
+| 6.6.1.1.1 Minimum requirement (Category A)                      | TC3a                                       | TC3a          | TC3b                                       | TC4a                   | TC4b                      | TC4c                             |
+| 6.6.1.1.2 Minimum requirement (Category B)                      | TC3a                                       | TC3a          | TC3b                                       | TC4a                   | TC4b                      | TC4c                             |
+| 6.6.1.1.3 Additional minimum requirement for BC2 (Category B)   | N/A                                        | N/A           | N/A                                        | TC4a                   | TC4b                      | TC4c                             |
+| 6.6.1.2 Protection of the BS receiver of own or different BS    | TC3a                                       | TC3a          | TC3b                                       | TC4a                   | TC4b                      | TC4c                             |
+| 6.6.1.3 Additional spurious emissions requirements              | TC3a                                       | TC3a          | TC3b                                       | TC4a                   | TC4b                      | TC4c                             |
+| 6.6.1.4 Co-location with other Base Stations                    | TC3a                                       | TC3a          | TC3b                                       | TC4a                   | TC4b                      | TC4c                             |
+| <b>6.6.2 Operating band unwanted emissions</b>                  | -                                          | -             | -                                          | -                      | -                         | -                                |
+| 6.6.2.1 General minimum requirement for Band Categories 1 and 3 | TC3a,<br>(TS 25.141)<br>and<br>(TS 36.141) | N/A           | TC3b,<br>(TS 25.142)<br>and<br>(TS 36.141) | N/A                    | N/A                       | N/A                              |
+
+| Capability Set                                           | UTRA + E-UTRA<br>(CS 3)                       |                                               |                                               | GSM+<br>UTRA<br>(CS 4)                        | GSM +<br>E-UTRA<br>(CS 5)                     | GSM + UTRA<br>+ E-UTRA<br>(CS 6)              |
+|----------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|
+| BS test case                                             | BC1                                           | BC2                                           | BC3                                           | BC2                                           | BC2                                           | BC2                                           |
+| 6.6.2.2 General minimum requirement for Band Category 2  | N/A                                           | 1) (TS 25.141) and (TS 36.141)<br>2) TC3a     | N/A                                           | 1) (TS 25.141)<br>2) TC4a                     | 1) (TS 36.141)<br>2) TC4b                     | 1) (TS 25.141) and (TS 36.141)<br>2) TC4c     |
+| 6.6.2.3 GSM/EDGE single-RAT requirement                  | N/A                                           | N/A                                           | N/A                                           | (TS 51.021)                                   | (TS 51.021)                                   | (TS 51.021)                                   |
+| 6.6.2.4 Additional requirements (only for band 34)       | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration |
+| <b>6.6.3 Occupied bandwidth</b>                          | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.6.3.1 Minimum requirement                              | (TS 25.141) and (TS 36.141)                   | (TS 25.141) and (TS 36.141)                   | (TS 25.142) and (TS 36.141)                   | (TS 25.141)                                   | (TS 36.141)                                   | (TS 25.141) and (TS 36.141)                   |
+| <b>6.6.4 Adjacent Channel Leakage power Ratio (ACLR)</b> | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.6.4.1 E- UTRA minimum requirement                      | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   | N/A                                           | (TS 36.141)                                   | (TS 36.141)                                   |
+| 6.6.4.2 UTRA FDD minimum requirement                     | (TS 25.141)                                   | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   |
+| 6.6.4.3 UTRA TDD minimum requirement                     | N/A                                           | N/A                                           | (TS 25.142)                                   | N/A                                           | N/A                                           | N/A                                           |
+| <b>6.7 Transmitter intermodulation</b>                   | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.7.1 General minimum requirement                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        |
+| 6.7.2 Additional minimum requirement (BC2)               | N/A                                           | Same TC as used in 6.6                        | N/A                                           | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        |
+| 6.7.3 Additional minimum requirement (BC3)               | N/A                                           | N/A                                           | Same TC as used in 6.6                        | N/A                                           | N/A                                           | N/A                                           |
+| <b>7.2 Reference sensitivity level</b>                   | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 7.2.1 E-UTRA minimum requirement                         | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   | N/A                                           | (TS 36.141)                                   | (TS 36.141)                                   |
+| 7.2.2 UTRA FDD minimum requirement                       | (TS 25.141)                                   | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   |
+| 7.2.3 UTRA TDD minimum requirement                       | N/A                                           | N/A                                           | (TS 25.142)                                   | N/A                                           | N/A                                           | N/A                                           |
+| 7.2.4 GSM/EDGE minimum requirement                       | N/A                                           | N/A                                           | N/A                                           | (TS 51.021)                                   | (TS 51.021)                                   | (TS 51.021)                                   |
+| <b>7.3 Dynamic range</b>                                 | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 7.3.1 E-UTRA minimum requirement                         | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   | N/A                                           | (TS 36.141)                                   | (TS 36.141)                                   |
+| 7.3.2 UTRA FDD minimum                                   | (TS 25.141)                                   | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   | N/A                                           | (TS 25.141)                                   |
+
+| Capability Set                                                        | UTRA + E-UTRA<br>(CS 3) |               |               | GSM+<br>UTRA<br>(CS 4) | GSM +<br>E-UTRA<br>(CS 5) | GSM + UTRA<br>+ E-UTRA<br>(CS 6) |
+|-----------------------------------------------------------------------|-------------------------|---------------|---------------|------------------------|---------------------------|----------------------------------|
+| BS test case                                                          | BC1                     | BC2           | BC3           | BC2                    | BC2                       | BC2                              |
+| requirement                                                           |                         |               |               |                        |                           |                                  |
+| 7.3.3 UTRA TDD minimum requirement                                    | N/A                     | N/A           | (TS 25.142)   | N/A                    | N/A                       | N/A                              |
+| 7.3.4 GSM/EDGE minimum requirement                                    | N/A                     | N/A           | N/A           | (TS 51.021)            | (TS 51.021)               | (TS 51.021)                      |
+| <b>7.4 In-band selectivity and blocking</b>                           | -                       | -             | -             |                        |                           | -                                |
+| 7.4.1 General blocking minimum requirement                            | TC3a                    | TC3a          | TC3b          | TC5a                   | TC5b                      | TC5b                             |
+| 7.4.2 General narrowband blocking minimum requirement                 | TC3a and TC6b           | TC3a and TC6b | TC3b and TC6b | TC5a and TC6a          | TC5b and TC6b             | TC5b and TC6a                    |
+| 7.4.3 Additional Narrowband blocking minimum requirement for GSM/EDGE | N/A                     | N/A           | N/A           | (TS 51.021)            | (TS 51.021)               | (TS 51.021)                      |
+| 7.4.4 GSM/EDGE requirements for AM suppression                        | N/A                     | N/A           | N/A           | (TS 51.021)            | (TS 51.021)               | (TS 51.021)                      |
+| 7.4.5 Additional BC3 blocking minimum requirement                     | N/A                     | N/A           | TC3b          | N/A                    | N/A                       | N/A                              |
+| <b>7.5 Out-of-band blocking</b>                                       | -                       | -             | -             | -                      | -                         | -                                |
+| 7.5.1 General minimum requirement                                     | TC3a                    | TC3a          | TC3b          | TC5a                   | TC5b                      | TC5b                             |
+| 7.5.2 Co-location minimum requirement                                 | TC3a                    | TC3a          | TC3b          | TC5a                   | TC5b                      | TC5b                             |
+| <b>7.6 Receiver spurious emissions</b>                                | -                       | -             | -             | -                      | -                         | -                                |
+| 7.6.1 General minimum requirement                                     | TC3a                    | TC3a          | TC3b          | TC4a                   | TC4b                      | TC4c                             |
+| 7.6.2 Additional minimum requirement for BC2 (Category B)             | TC3a                    | TC3a          | TC3b          | TC4a                   | TC4b                      | TC4c                             |
+| <b>7.7 Receiver intermodulation</b>                                   | -                       | -             | -             | -                      | -                         | -                                |
+| 7.7.1 General intermodulation minimum requirement                     | TC3a                    | TC3a          | TC3b          | TC5a                   | TC5b                      | TC5b                             |
+| 7.7.2 General narrowband intermodulation minimum requirement          | TC3a and TC6b           | TC3a and TC6b | TC3b and TC6b | TC5a and TC6a          | TC5b and TC6b             | TC5b and TC6a                    |
+| 7.7.3 Additional narrowband intermodulation                           | N/A                     | N/A           | N/A           | (TS 51.021)            | (TS 51.021)               | (TS 51.021)                      |
+
+| Capability Set                    | UTRA + E-UTRA<br>(CS 3) |             |             | GSM+<br>UTRA<br>(CS 4) | GSM +<br>E-UTRA<br>(CS 5) | GSM + UTRA<br>+ E-UTRA<br>(CS 6) |
+|-----------------------------------|-------------------------|-------------|-------------|------------------------|---------------------------|----------------------------------|
+| BS test case                      | BC1                     | BC2         | BC3         | BC2                    | BC2                       | BC2                              |
+| minimum requirement for GSM/EDGE  |                         |             |             |                        |                           |                                  |
+| <b>7.8 In-channel selectivity</b> | -                       | -           | -           | -                      | -                         | -                                |
+| 7.8.1 E-UTRA minimum requirement  | (TS 36.141)             | (TS 36.141) | (TS 36.141) | N/A                    | (TS 36.141)               | (TS 36.141)                      |
+
+Table 9.1.3-2: Test configurations for capability sets for Single-RAT capable BS
+
+| Capability Set                                             | UTRA (MC) capable BS (CS1) |             |             | E-UTRA (MC) capable BS (CS2) |             |                                               |
+|------------------------------------------------------------|----------------------------|-------------|-------------|------------------------------|-------------|-----------------------------------------------|
+| BS test case                                               | BC1                        | BC2         | BC3         | BC1                          | BC2         | BC3                                           |
+| <b>6.2 Base Station output power</b>                       | -                          | -           | -           | -                            | -           | -                                             |
+| 6.2.1 Minimum requirement                                  | TC1a                       | TC1a        | TC1b        | TC2                          | TC2         | TC2                                           |
+| 6.2.2 Additional requirement (only for band 34)            | N/A                        | N/A         | N/A         | N/A                          | N/A         | Compliance stated by manufacturer declaration |
+| 6.2.3 E-UTRA minimum requirement for DL RS power           | N/A                        | N/A         | N/A         | (TS 36.141)                  | (TS 36.141) | (TS 36.141)                                   |
+| 6.2.4 UTRA FDD minimum requirement for primary CPICH power | (TS 25.141)                | (TS 25.141) | N/A         | N/A                          | N/A         | N/A                                           |
+| 6.2.5 UTRA TDD minimum requirement for primary CCPCH power | N/A                        | N/A         | (TS 25.142) | N/A                          | N/A         | N/A                                           |
+| <b>6.3 Output power dynamics</b>                           | -                          | -           | -           | -                            | -           | -                                             |
+| 6.3.1 E-UTRA minimum requirement                           | N/A                        | N/A         | N/A         | (TS 36.141)                  | (TS 36.141) | (TS 36.141)                                   |
+| 6.3.2 UTRA FDD minimum requirement                         | (TS 25.141)                | (TS 25.141) | N/A         | N/A                          | N/A         | N/A                                           |
+| 6.3.3 UTRA TDD minimum requirement                         | N/A                        | N/A         | (TS 25.142) | N/A                          | N/A         | N/A                                           |
+| 6.3.4 GSM/EDGE minimum requirement                         | N/A                        | N/A         | N/A         | N/A                          | N/A         | N/A                                           |
+| <b>6.4 Transmit ON/OFF power</b>                           | -                          | -           | -           | -                            | -           | -                                             |
+| 6.4.1 Transmitter OFF power                                | N/A                        | N/A         | TC1b        | N/A                          | N/A         | TC2                                           |
+| 6.4.2 Transmitter transient period                         | N/A                        | N/A         | TC1b        | N/A                          | N/A         | TC2                                           |
+| <b>6.5 Transmitted signal quality</b>                      | -                          | -           | -           | -                            | -           | -                                             |
+| <b>6.5.1 Modulation quality</b>                            | -                          | -           | -           | -                            | -           | -                                             |
+| 6.5.1.1 E-UTRA minimum requirement                         | N/A                        | N/A         | N/A         | [TC2]                        | [TC2]       | [TC2]                                         |
+| 6.5.1.2 UTRA FDD minimum requirement                       | [TC1a]                     | [TC1a]      | N/A         | N/A                          | N/A         | N/A                                           |
+| 6.5.1.3 UTRA TDD minimum requirement                       | N/A                        | N/A         | [TC1b]      | N/A                          | N/A         | N/A                                           |
+| 6.5.1.4                                                    | N/A                        | N/A         | N/A         | N/A                          | N/A         | N/A                                           |
+
+| Capability Set                                                | UTRA (MC) capable BS (CS1) |               |               | E-UTRA (MC) capable BS (CS2) |               |               |
+|---------------------------------------------------------------|----------------------------|---------------|---------------|------------------------------|---------------|---------------|
+| BS test case                                                  | BC1                        | BC2           | BC3           | BC1                          | BC2           | BC3           |
+| GSM/EDGE minimum requirement                                  |                            |               |               |                              |               |               |
+| <b>6.5.2 Frequency error</b>                                  | -                          | -             | -             | -                            | -             | -             |
+| 6.5.2.1 E-UTRA minimum requirement                            | N/A                        | N/A           | N/A           | [(TS 36.141)]                | [(TS 36.141)] | [(TS 36.141)] |
+| 6.5.2.2 UTRA FDD minimum requirement                          | [(TS 25.141)]              | [(TS 25.141)] | N/A           | N/A                          | N/A           | N/A           |
+| 6.5.2.3 UTRA TDD minimum requirement                          | N/A                        | N/A           | [(TS 25.142)] | N/A                          | N/A           | N/A           |
+| 6.5.2.4 GSM/EDGE minimum requirement                          | N/A                        | N/A           | N/A           | N/A                          | N/A           | N/A           |
+| <b>6.5.3 Time alignment between transmitter branches</b>      | -                          | -             | -             | -                            | -             | -             |
+| 6.5.3.1 E-UTRA minimum requirement                            | N/A                        | N/A           | N/A           | (TS 36.141)                  | (TS 36.141)   | (TS 36.141)   |
+| 6.5.3.2 UTRA FDD minimum requirement                          | (TS 25.141)                | (TS 25.141)   | N/A           | N/A                          | N/A           | N/A           |
+| 6.5.3.3 UTRA TDD minimum requirement                          | N/A                        | N/A           | (TS 25.142)   | N/A                          | N/A           | N/A           |
+| <b>6.6 Unwanted emissions</b>                                 | -                          | -             | -             | -                            | -             | -             |
+| <b>6.6.1 Transmitter spurious emissions</b>                   | -                          | -             | -             | -                            | -             | -             |
+| 6.6.1.1.1 Minimum requirement (Category A)                    | TC1a                       | TC1a          | TC1b          | TC2                          | TC2           | TC2           |
+| 6.6.1.1.2 Minimum requirement (Category B)                    | TC1a                       | TC1a          | TC1b          | TC2                          | TC2           | TC2           |
+| 6.6.1.1.3 Additional minimum requirement for BC2 (Category B) | N/A                        | N/A           | N/A           | N/A                          | N/A           | N/A           |
+| 6.6.1.2 Protection of the BS receiver of own or different BS  | TC1a                       | TC1a          | TC1b          | TC2                          | TC2           | TC2           |
+| 6.6.1.3 Additional spurious emissions requirements            | TC1a                       | TC1a          | TC1b          | TC2                          | TC2           | TC2           |
+| 6.6.1.4 Co-location with                                      | TC1a                       | TC1a          | TC1b          | TC2                          | TC2           | TC2           |
+
+| Capability Set                                                  | UTRA (MC) capable BS (CS1)                    |                                               |                                               | E-UTRA (MC) capable BS (CS2)                  |                                               |                                               |
+|-----------------------------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|
+| BS test case                                                    | BC1                                           | BC2                                           | BC3                                           | BC1                                           | BC2                                           | BC3                                           |
+| other Base Stations                                             |                                               |                                               |                                               |                                               |                                               |                                               |
+| <b>6.6.2 Operating band unwanted emissions</b>                  | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.6.2.1 General minimum requirement for Band Categories 1 and 3 | TC1a and (TS 25.141)                          | N/A                                           | TC1b and (TS 25.142)                          | TC2 and (TS 36.141)                           | N/A                                           | TC2 and (TS 36.141)                           |
+| 6.6.2.2 General minimum requirement for Band Category 2         | N/A                                           | TC1a and (TS 25.141)                          | N/A                                           | N/A                                           | TC2 and (TS 36.141)                           | N/A                                           |
+| 6.6.2.3 GSM/EDGE single-RAT requirements                        | N/A                                           | N/A                                           | N/A                                           | N/A                                           | N/A                                           | N/A                                           |
+| 6.6.2.4 Additional requirements                                 | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration | Compliance stated by manufacturer declaration |
+| <b>6.6.3 Occupied bandwidth</b>                                 | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.6.3.1 Minimum requirement                                     | (TS 25.141)                                   | (TS 25.141)                                   | (TS 25.142)                                   | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   |
+| <b>6.6.4 Adjacent Channel Leakage power Ratio (ACLR)</b>        | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.6.4.1 E-UTRA minimum requirement                              | N/A                                           | N/A                                           | N/A                                           | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   |
+| 6.6.4.2 UTRA FDD minimum requirement                            | (TS 25.141)                                   | (TS 25.141)                                   | N/A                                           | N/A                                           | N/A                                           | N/A                                           |
+| 6.6.4.3 UTRA TDD minimum requirement                            | N/A                                           | N/A                                           | (TS 25.142)                                   | N/A                                           | N/A                                           | N/A                                           |
+| <b>6.7 Transmitter intermodulation</b>                          | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 6.7.1 General minimum requirement                               | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        | Same TC as used in 6.6                        |
+| 6.7.2 Additional minimum requirement (BC2)                      | N/A                                           | Same TC as used in 6.6                        | N/A                                           | N/A                                           | Same TC as used in 6.6                        | N/A                                           |
+| 6.7.3 Additional minimum requirement (BC3)                      | N/A                                           | N/A                                           | Same TC as used in 6.6                        | N/A                                           | N/A                                           | Same TC as used in 6.6                        |
+| <b>7.2 Reference sensitivity level</b>                          | -                                             | -                                             | -                                             | -                                             | -                                             | -                                             |
+| 7.2.1 E-UTRA minimum requirement                                | N/A                                           | N/A                                           | N/A                                           | (TS 36.141)                                   | (TS 36.141)                                   | (TS 36.141)                                   |
+| 7.2.2 UTRA FDD minimum requirement                              | (TS 25.141)                                   | (TS 25.141)                                   | N/A                                           | N/A                                           | N/A                                           | N/A                                           |
+| 7.2.3 UTRA TDD minimum                                          | N/A                                           | N/A                                           | (TS 25.142)                                   | N/A                                           | N/A                                           | N/A                                           |
+
+| Capability Set                                                        | UTRA (MC) capable BS (CS1) |                                   |               | E-UTRA (MC) capable BS (CS2) |                                   |              |
+|-----------------------------------------------------------------------|----------------------------|-----------------------------------|---------------|------------------------------|-----------------------------------|--------------|
+| BS test case                                                          | BC1                        | BC2                               | BC3           | BC1                          | BC2                               | BC3          |
+| requirement                                                           |                            |                                   |               |                              |                                   |              |
+| 7.2.4 GSM/EDGE minimum requirement                                    | N/A                        | N/A                               | N/A           | N/A                          | N/A                               | N/A          |
+| <b>7.3 Dynamic range</b>                                              | -                          | -                                 | -             | -                            | -                                 | -            |
+| 7.3.1 E-UTRA minimum requirement                                      | N/A                        | N/A                               | N/A           | (TS 36.141)                  | (TS 36.141)                       | (TS 36.141)  |
+| 7.3.2 UTRA FDD minimum requirement                                    | (TS 25.141)                | (TS 25.141)                       | N/A           | N/A                          | N/A                               | N/A          |
+| 7.3.3 UTRA TDD minimum requirement                                    | N/A                        | N/A                               | (TS 25.142)   | N/A                          | N/A                               | N/A          |
+| 7.3.4 GSM/EDGE minimum requirement                                    | N/A                        | N/A                               | N/A           | N/A                          | N/A                               | N/A          |
+| <b>7.4 In-band selectivity and blocking</b>                           | -                          | -                                 | -             | -                            | -                                 | -            |
+| 7.4.1 General blocking minimum requirement                            | TC1a                       | TC1a                              | TC1b          | TC2                          | TC2                               | TC2          |
+| 7.4.2 General narrowband blocking minimum requirement                 | TC1a and TC6a              | TC1a and TC6a                     | TC1b and TC6c | TC2 and TC6b                 | TC2 and TC6b                      | TC2 and TC6b |
+| 7.4.3 Additional Narrowband blocking minimum requirement for GSM/EDGE | N/A                        | N/A                               | N/A           | N/A                          | N/A                               | N/A          |
+| 7.4.4 GSM/EDGE requirements for AM suppression                        | N/A                        | N/A                               | N/A           | N/A                          | N/A                               | N/A          |
+| 7.4.5 Additional BC3 blocking minimum requirement                     | N/A                        | N/A                               | TC1b          | N/A                          | N/A                               | TC2          |
+| <b>7.5 Out-of-band blocking</b>                                       | -                          | -                                 | -             | -                            | -                                 | -            |
+| 7.5.1 General minimum requirement                                     | TC1a                       | TC1a                              | TC1b          | TC2                          | TC2                               | TC2          |
+| 7.5.2 Co-location minimum requirement                                 | TC1a                       | TC1a                              | TC1b          | TC2                          | TC2                               | TC2          |
+| <b>7.6 Receiver spurious emissions</b>                                |                            |                                   |               |                              |                                   |              |
+| 7.6.1 General minimum requirement                                     | TC1a                       | TC1a                              | TC1b          | TC2                          | TC2                               | TC2          |
+| 7.6.2 Additional minimum requirement for                              | N/A                        | Compliance stated by manufacturer | N/A           | N/A                          | Compliance stated by manufacturer | N/A          |
+
+| Capability Set                                                               | UTRA (MC) capable BS (CS1) |               |               | E-UTRA (MC) capable BS (CS2) |              |              |
+|------------------------------------------------------------------------------|----------------------------|---------------|---------------|------------------------------|--------------|--------------|
+| BS test case                                                                 | BC1                        | BC2           | BC3           | BC1                          | BC2          | BC3          |
+| BC2 (Category B)                                                             |                            | declaration   |               |                              | declaration  |              |
+| <b>7.7 Receiver intermodulation</b>                                          | -                          | -             | -             | -                            | -            | -            |
+| 7.7.1 General intermodulation minimum requirement                            | TC1a                       | TC1a          | TC1b          | TC2                          | TC2          | TC2          |
+| 7.7.2 General narrowband intermodulation minimum requirement                 | TC1a and TC6a              | TC1a and TC6a | TC1b and TC6c | TC2 and TC6b                 | TC2 and TC6b | TC2 and TC6b |
+| 7.7.3 Additional narrowband intermodulation minimum requirement for GSM/EDGE | N/A                        | N/A           | N/A           | N/A                          | N/A          | N/A          |
+| <b>7.8 In-channel selectivity</b>                                            | -                          | -             | -             | -                            | -            | -            |
+| 7.8.1 E-UTRA minimum requirement                                             | N/A                        | N/A           | N/A           | (TS 36.141)                  | (TS 36.141)  | (TS 36.141)  |
+
+Once referring to the existing single-RAT specifications in the table above, existing clauses in the relevant specifications will be used (procedures, test requirements, etc). However, regarding the interpretation of the RF channels to be tested, the following definitions will be used:
+
+B: maximum RF bandwidth at the bottom of (supported frequency range in) the operating band, wanted channel at the bottom of the maximum RF bandwidth
+
+M: maximum RF bandwidth in the middle of (supported frequency range in) the operating band, wanted channel in the middle of the maximum RF bandwidth
+
+T: maximum RF bandwidth at the top of (supported frequency range in) the operating band, wanted channel at the top of the maximum RF bandwidth
+
+# Annex A: Characteristics of interfering signals
+
+## A.1 UTRA interfering signal
+
+The UTRA interfering signal shall be a DPCH containing the DPCCH and one DPDCH. The data content for each channelization code shall be uncorrelated with each other and to the wanted signal and spread and modulated according to clause 4 of TS 25.213. Further characteristics of DPDCH and DPCCH are specified in Table A.1-1.
+
+**Table A.1-1: Characteristics of UTRA interfering signal**
+
+| Channel                                                                                                  | Bit Rate | Spreading Factor | Channelization Code | Relative Power |
+|----------------------------------------------------------------------------------------------------------|----------|------------------|---------------------|----------------|
+| DPDCH                                                                                                    | 240 kbps | 16               | 4                   | 0 dB           |
+| DPCCH                                                                                                    | 15 kbps  | 256              | 0                   | -5.46 dB       |
+| NOTE: The DPDCH and DPCCH settings are chosen to simulate a signal with realistic Peak to Average Ratio. |          |                  |                     |                |
+
+The UTRA interfering signal for band category 3 shall be UTRA TDD signal with one code. The data content shall be uncorrelated to the wanted signal. They are specified in Table A.1-2.
+
+**Table A.1-2: Characteristics of UTRA TDD interfering signal**
+
+| UTRA TDD option                                                                                    | Type of Interfering Signal               |
+|----------------------------------------------------------------------------------------------------|------------------------------------------|
+| 1.28Mcps UTRA TDD (TD-SCDMA)                                                                       | 1,28 Mcps UTRA TDD signal with one code* |
+| * NOTE: The channelization code ID and Midamble shift shall be different with the wanted signal's. |                                          |
+
+## A.2 E-UTRA interfering signal
+
+The E-UTRA interfering signal shall be a PUSCH containing data and reference symbols. Normal CP is used. The data content shall be uncorrelated to the wanted signal and modulated according to clause 5 of TS 36.211. Mapping of PUSCH modulation to receiver requirement are specified in Table A.2-2.
+
+**Table A.2-2: Modulation of the E-UTRA interfering signal**
+
+| Receiver requirement     | Modulation |
+|--------------------------|------------|
+| Narrowband blocking      | QPSK       |
+| Receiver intermodulation | QPSK       |
+
+# Annex B: Change history
+
+| Change history |          |           |    |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |       |       |  |
+|----------------|----------|-----------|----|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|--|
+| Date           | TSG #    | TSG Doc.  | CR | Rev | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Old   | New   |  |
+| 2008-11        | R4#49    | R4-082944 |    |     | Report skeleton                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |       | 0.0.1 |  |
+| 2009-02        | R4#50    | R4-090606 |    |     | Agreed Text Proposals in RAN4#49bis:<br><b>R4-090259</b> , "TP on Spurious emissions (Cat 1) (TR ch 6.6.2)"<br><b>R4-090261</b> , "TP on Out-of-band blocking (Cat 1) (TR ch 7.5)"<br><b>R4-090405</b> , "TP on MSR Work item objective (TR ch 4.1)"<br><b>R4-090410</b> , "TP on MSR scenarios/Band categories (TR ch 5.2 and 5.3)"<br><b>R4-090411</b> , "TP on MSR definitions (TR ch 3)"                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 0.0.1 | 0.0.2 |  |
+| 2009-02        | R4#50    | R4-090993 |    |     | TR updated to be in line with TR template v1.7.0.<br>Agreed Text Proposals in RAN4#50:<br><b>R4-090612</b> , "TPs on Spurious emission requirements for co-existence (Cat 1 and 2) (TR ch 6.6.2)"<br><b>R4-090950</b> , "TP on EVM (Cat 1 and 2) (TR ch 6.5)"<br><b>R4-090951</b> , "TPs on Blocking requirements for co-existence existence (Cat 1) (TR ch 7.5.1.2)"<br><b>R4-090974</b> , "TP on RF bandwidth in MSR specification"<br><b>R4-090975</b> , "TP on BS classes"                                                                                                                                                                                                                                                                                                                                                                         | 0.0.2 | 0.1.0 |  |
+| 2009-03        | R4#50bis | R4-091447 |    |     | Agreed Text Proposals in RAN4#50bis:<br><b>R4-091069</b> , "TP for test ports and antenna assumptions"<br><b>R4-091160</b> , "TP on editorial changes in Chapter 6"<br><b>R4-091256</b> , "TP on Frequency error (BC 1 &2) (TR ch 6.5)"<br><b>R4-091259</b> , "TP on Tx spurious emissions (BC 2) (TR ch 6.6.2.2)"<br><b>R4-091260</b> , "TP on Out-of-band blocking (BC 2) (TR ch 7.5.2)"<br><b>R4-091352</b> , "MSR scenarios on TD-SCDMA and E-UTRA TDD combination"<br><b>R4-091479</b> , "Text proposal on in-channel selectivity"<br><b>R4-091482</b> , "TP on BS Classes (BC 2) (TR ch 4.4)", including <b>R4-091368</b> , "Clarification on BS class for Band category 2"<br><b>R4-091484</b> , "TP on Operating band unwanted emission (UEM) for BC1 (TR ch 6.6.1)"                                                                           | 0.1.0 | 0.2.0 |  |
+| 2009-05        | R4#51    | R4-092003 |    |     | Agreed Text Proposals in RAN4#51:<br><b>R4-091521</b> , "Text proposal on characteristics of the interfering signals"<br><b>R4-091544</b> , "TP for spurious emission of band category 3"<br><b>R4-091836</b> , "TP on Background discussion for UEM for BC1 (TR ch 6.6.1)"<br><b>R4-091840</b> , "TP on Output power dynamics (BC1 & 2) (TR ch 6.3)"<br><b>R4-091848</b> , "TP on Rx spurious emissions (BC 1 & 2) (TR ch 7.6)"<br><b>R4-091852</b> , "TP on Relationship minimum requirements and test requirements (BC1 & 2) (TR ch 4.3)"<br><b>R4-092044</b> , "TP on protection of uplink operating band (BC1 & 2) (TR ch 6.6.2)"<br><b>R4-092045</b> , "Transmitter Intermodulation (BC1 & 2)"<br><b>R4-092046</b> , "TP on Receiver sensitivity (BC 1 & 2) (TR ch 7.2)"<br><b>R4-092048</b> , "TP on Rx Intermodulation (BC 1 & 2) (TR ch 7.7)" | 0.2.0 | 0.3.0 |  |
+
+|         |          |           |  |  |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |       |       |
+|---------|----------|-----------|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+|         |          |           |  |  | <b>R4-092053</b> , "MSR BS Frequency bands and arrangements"<br><b>R4-092054</b> , "Manufacturers declaration for MSR BS"<br><b>R4-092058</b> , "TP for operating band unwanted emissions of band category 3"<br><b>R4-092059</b> , "TP for adding Foffset,RAT for band category 3"<br><b>R4-092064</b> , "Text proposal on blocking"<br><b>R4-092065</b> , "Text proposal on dynamic range"<br><b>R4-092066</b> , "Text proposal on narrowband blocking"<br><b>R4-092069</b> , "MSR output power definitions" (Ericsson).<br><b>R4-092070</b> , "TP on Narrowband Intermodulation (BC 1 & 2) (TR ch 7.7)" (Ericsson, Nokia Siemens Networks, Huawei).<br><b>R4-092083</b> , "TP on Way forward for UEM for BC2 (TR ch 6.6.1)" (Ericsson, Nokia Siemens Networks, Alcatel-Lucent).                                                                                                                                                                                                                             |       |       |
+| 2009-05 | R4#51    | R4-092109 |  |  | Editorial updates made during RAN4#51.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 0.3.0 | 0.3.1 |
+| 2009-06 | R4#51bis | R4-092356 |  |  | Editorial updates made after RAN4#51.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 0.3.1 | 0.3.2 |
+| 2009-07 | R4#51bis | R4-092531 |  |  | Agreed Text Proposals in RAN4#51bis:<br><b>R4-092193</b> , "Modification for section 5.3.1 of MSR specification"<br><b>R4-092194</b> , "Modification for section 6.2 of MSR specification"<br><b>R4-092197</b> , "Dynamic range of BC3"<br><b>R4-092201</b> , "UTRA TDD interference signal of UTRA TDD"<br><b>R4-092350</b> , "TP on FCC requirements for unwanted emissions (BC1 & 2) (TR ch 6.6.1)"<br><b>R4-092351</b> , "TP on Spurious emission for protection of BS receiver (BC2) (TR ch 6.6.2.2.4)"<br><b>R4-092360</b> , "TP on Regional requirements for MSR (TR ch 4.5)"<br><b>R4-092554</b> , "Performance requirements for MSR"<br><b>R4-092555</b> , "Text proposal on intermodulation and narrowband intermodulation"<br><b>R4-092557</b> , "Reference sensitivity level of BC3"<br><b>R4-092558</b> , "Receiver spurious emissions of BC3"<br><b>R4-092572</b> , "Text proposal on blocking and narrowband blocking"<br><b>R4-092586</b> , "TP on MSR topics from GERAN feedback" (Ericsson). | 0.3.2 | 0.4.0 |
+| 2009-07 | R4#51bis | R4-093001 |  |  | E-mail approved Text Proposal after RAN4#51bis:<br><b>R4-092550</b> , "TP on UEM for BC2 (TR ch 6.6.1)"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 0.4.0 | 0.5.0 |
+| 2009-08 | R4#52    | R4-093256 |  |  | Agreed Text Proposals in RAN4#52:<br><b>R4-092846</b> , "Receiver intermodulation of BC3"<br><b>R4-093002</b> , "TR 37.900: TP on Alignment of BC3 requirements for MSR"<br><b>R4-093003</b> , "TR 37.900: TP on Clarification of RF bandwidth edge for MSR"<br><b>R4-093364</b> , "Transmit OFF Power of MSR Base Station"<br><b>R4-093386</b> , "Spurious Emission requirement of MSR category 3(TD-SCDMA and LTE TDD)"<br><b>R4-093387</b> , "Transmitter inter-modulation requirement of MSR category 3(TD-SCDMA and LTE TDD)"<br><b>R4-093388</b> , "Out-of-band blocking requirement of MSR category 3(TD-SCDMA and LTE TDD)"                                                                                                                                                                                                                                                                                                                                                                            | 0.5.0 | 0.6.0 |
+| 2009-09 | RAN#45   | RP-090765 |  |  | Presentation to TSG RAN for information                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 0.6.0 | 1.0.0 |
+| 2009-10 | R4#52bis | R4-093978 |  |  | Agreed Text Proposals in RAN4#52bis:<br><b>R4-093784</b> , "TR 37.900: ACLR requirement (TR ch 6.6.4)"<br><b>R4-093785</b> , "TR 37.900: TP on Occupied bandwidth (TR ch 6.6.3)"<br><b>R4-093786</b> , "TR 37.900: TP on Spurious emissions requirements in BC2 (TR ch 6.6.2 and 7.6)"<br><b>R4-093787</b> , "TR 37.900: TP on In-band selectivity and blocking for BC3 (TR ch 7.4)"<br><b>R4-094000</b> , "Corrections to maximum power definitions"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 1.0.0 | 1.1.0 |
+
+|         |       |           |     |   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |        |        |
+|---------|-------|-----------|-----|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+|         |       |           |     |   | <b>R4-094014</b> , "Clarification on Spurious emissions limits for BS co-existed with another BS (37.900)"<br><b>R4-094028</b> , "TP for 37.900 Manufacturer declaration cleanup"<br><b>R4-094057</b> , "TP for 37.900 BC3 Transmitter ON-OFF characteristics"                                                                                                                                                                                                                |        |        |
+| 2009-11 | R4#53 | R4-094776 |     |   | Agreed Text Proposals in RAN4#53:<br><b>R4-094404</b> , "Corrections on frequency range of unwanted emissions requirements (37.900)"<br><b>R4-094477</b> , "TR 37.900: EMC specification for MSR"                                                                                                                                                                                                                                                                             | 1.1.0  | 1.2.0  |
+| 2010-02 | R4#54 | R4-100974 |     |   | Agreed Text Proposals in RAN4#53:<br><b>R4-100434</b> , "Clarification on operating band unwanted emission mask (UEM) for BC2"<br><b>R4-100577</b> , "TR 37.900: Application of necessary bandwidth (TR ch 6.6.1.2)"<br><b>R4-100957</b> , "TR 37.900: TP for aligning with recent TS 37.104 updates"<br><b>R4-101022</b> , "TP 37.900 TP on Test configurations to requirements mapping (ch 9)"<br><b>R4-101023</b> , "TP 37.900 TP on Test configuration principles (ch 9)" | 1.2.0  | 1.3.0  |
+| 2010-04 | R4#55 | R4-101578 |     |   | Agreed Text Proposals in RAN4 AH#2:<br><b>R4-101510</b> , "TP for requirements and test configuration applicability, subclause 5.1" (TP applied to TS 37.141 and TR 37.900)<br><b>R4-101511</b> , "TP for requirements and test configuration applicability, subclause 5.2" (TP applied to TS 37.141 and TR 37.900)                                                                                                                                                           | 1.3.0  | 1.4.0  |
+| 2010-05 | R4#55 | R4-102215 |     |   | Agreed Text Proposals in RAN4 #55:<br><b>R4-101889</b> , "TR 37.900: TP for Co-existence with services in adjacent frequency bands"                                                                                                                                                                                                                                                                                                                                           | 1.4.0  | 1.5.0  |
+| 2010-06 | RP#48 | RP-100582 |     |   | Presentation to TSG RAN for approval.                                                                                                                                                                                                                                                                                                                                                                                                                                         | 1.5.0  | 2.0.0  |
+| 2010-06 | RP#48 | RP-100582 |     |   | Approved by TSG RAN.                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 2.0.0  | 9.0.0  |
+| 2010-07 |       |           |     |   | Editorial Correction: removal of "Normative/informative" from Annexes (All the annexes are informative in the TR).                                                                                                                                                                                                                                                                                                                                                            | 9.0.0  | 9.0.1  |
+|         | SP-51 |           |     |   | Upgraded unchanged from Rel-9                                                                                                                                                                                                                                                                                                                                                                                                                                                 | 9.0.1  | 10.0.0 |
+| 2012-09 | RP-57 | RP-121323 | 001 |   | Additional co-existence scenarios for BC3 MSR                                                                                                                                                                                                                                                                                                                                                                                                                                 | 10.0.0 | 11.0.0 |
+| 2012-12 |       |           |     |   | Correction of sections numbering                                                                                                                                                                                                                                                                                                                                                                                                                                              | 11.0.0 | 11.0.1 |
+| 2014-09 | SP-65 | -         | -   | - | Update to Rel-12 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                | 11.0.1 | 12.0.0 |
+| 2016-01 | SP-70 | -         | -   | - | Update to Rel-13 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                | 12.0.0 | 13.0.0 |
+| 2017-03 | RP-75 | -         | -   | - | Update to Rel-14 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                                                | 13.0.0 | 14.0.0 |
+
+| <b>Change history</b> |         |      |    |     |     |                                |             |
+|-----------------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date                  | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-06               | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06               | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37902/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37902/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a179c3e7a8d57b2dbf9b4fb9fc9547c77de235f4
--- /dev/null
+++ b/marked/Rel-16/37_series/37902/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2c25295b76107af445c839e49020e3c95bfd82d7e8a6b34d64f936076b3e750
+size 9410
diff --git a/marked/Rel-16/37_series/37902/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37902/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4c1994bb16b9916d9faf2caed45c56be6b5bb35
--- /dev/null
+++ b/marked/Rel-16/37_series/37902/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1545c292ae9794d5da18ec430216c56faa3b9d4b0b03abe2753f8853c7bd8d4
+size 5738
diff --git a/marked/Rel-16/37_series/37902/raw.md b/marked/Rel-16/37_series/37902/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd2446cadc7eb60f2f6e06ea7ec99949a6d4f0d6
--- /dev/null
+++ b/marked/Rel-16/37_series/37902/raw.md
@@ -0,0 +1,776 @@
+
+
+# 3GPP TR 37.902 V16.0.0 (2020-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Measurements of User Equipment (UE) radio performances for LTE/UMTS terminals; Total Radiated Power (TRP) and Total Radiated Sensitivity (TRS) test methodology (Release 16)** ---
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top, and the "P" has a red signal wave icon below it. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+## --- **Postal address**
+
+## --- **3GPP support office address**
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## --- **Internet**
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification**
+
+---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                                                  |           |
+|----------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                   | 4         |
+| Introduction .....                                                               | 4         |
+| 1 Scope.....                                                                     | 5         |
+| 2 References.....                                                                | 5         |
+| 3 Definitions, symbols and abbreviations .....                                   | 5         |
+| 3.1 Definitions.....                                                             | 5         |
+| 3.2 Symbols.....                                                                 | 5         |
+| 3.3 Abbreviations .....                                                          | 6         |
+| 4 General .....                                                                  | 6         |
+| 4.1 Scope .....                                                                  | 7         |
+| 4.2 Device Under Test definition .....                                           | 8         |
+| 5 Measurement environment condition.....                                         | 8         |
+| 5.1 Chamber environment constraints.....                                         | 8         |
+| 5.2 Positioning Requirements and Coordinate system.....                          | 8         |
+| 5.3 DUT Test Positions and Phantom Specifications .....                          | 8         |
+| 5.3.1 Phantom Specifications .....                                               | 8         |
+| 5.3.2 DUT Test Positions .....                                                   | 8         |
+| 6 Measurement parameters .....                                                   | 8         |
+| 6.1 Definition of the Total Radiated Power .....                                 | 8         |
+| 6.2 Definition of Total Radiated Sensitivity .....                               | 9         |
+| 6.2.1 Total Radiated Sensitivity .....                                           | 9         |
+| 6.2.2 Alternate measurement parameter.....                                       | 9         |
+| 6.3 Sampling grid and independent samples.....                                   | 9         |
+| 6.4 Measurement frequencies.....                                                 | 9         |
+| 7 Measurement procedure – transmitter performance .....                          | 15        |
+| 7.1 General measurement arrangements .....                                       | 16        |
+| 7.2 Procedure for radiated power measurement.....                                | 16        |
+| 7.3 Calibration measurement.....                                                 | 17        |
+| 8 Measurement procedure – receiver performance.....                              | 17        |
+| 8.1 General measurement arrangements .....                                       | 17        |
+| 8.2 Procedure for radiated sensitivity measurement .....                         | 17        |
+| 8.3 Calibration measurement.....                                                 | 18        |
+| <b>Annex A: System Parameters.....</b>                                           | <b>19</b> |
+| A.1 Definition and applicability .....                                           | 19        |
+| A.2 Establishing the connection .....                                            | 19        |
+| A.3 Uplink RB allocation for reference sensitivity .....                         | 19        |
+| <b>Annex B: Measurement Uncertainty.....</b>                                     | <b>21</b> |
+| <b>Annex C: Anechoic chamber specifications and validation method .....</b>      | <b>22</b> |
+| <b>Annex D: Reverberation chamber specifications and validation method .....</b> | <b>23</b> |
+| <b>Annex E: Change history.....</b>                                              | <b>24</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+In this technical report, the needed modifications to measurement parameters for LTE devices will be studied and applicability of the existing measurement procedures, e.g. TRP and TRS will be evaluated for LTE devices with multiple receive antennas TDD-LTE and FDD-LTE terminals (as it is expected that the same issues are applicable independent of RAT). As UMTS devices with multiple receive antennas are still needing test methodology, it is easy to extend to this study item contribution to UMTS terminals with, due to similar situation and technical issue. UMTS TRP and TRS test methods should also be updated in the same way.
+
+# --- 1 Scope
+
+The present document is a Technical Report of the Study Item for OTA TRP and TRS requirement of LTE terminals, which was approved at TSG RAN #55 [2]. The report provides the measurement procedure of Over The Air TRP and TRS requirements for LTE terminals. It will make a simple extension to the UE OTA TRP and TRS test methods TS34.114[3] for LTE UE with multiple receive antennas, without considering all of the aspects associated with spatial channels. The work should utilise the existing environments in TR25.914[4]. The results of the UE OTA test method with Head and Hand Phantoms study item can be considered later on once finalized. The report also provides some future extensions and work items after LTE TRP and TRS methods mature.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] RP-120412, "New study item proposal: Measurements of radio performances for LTE terminals - conformance testing methodology".
+- [3] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance".
+- [4] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode".
+- [5] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE) radio transmission and reception".
+- [6] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: conformance testing".
+- [7] RP-120368, "Verification of radiated multi-antenna reception performance of UEs in LTE/UMTS WID".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+Void
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+- $\theta$  Zenith angle in the spherical co-ordinate system
+- $\phi$  Azimuth angle in the spherical co-ordinate system
+- $\Omega$  Solid angle defined at the phase centre of the DUT
+
+|                        |                                                                                                                            |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------|
+| $G\psi(\theta,\phi,f)$ | Antenna gain pattern in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency       |
+| F                      | Carrier frequency                                                                                                          |
+| Ptr                    | Transmitted power                                                                                                          |
+| $Q\psi(\theta,\phi,f)$ | Angular power distribution in the $\psi$ -polarization as function of the spherical co-ordinates and the carrier frequency |
+| dB                     | decibel                                                                                                                    |
+| dBm                    | dB referenced to one milliwatt                                                                                             |
+| m                      | meter                                                                                                                      |
+| mm                     | millimetre                                                                                                                 |
+| kbps                   | kilobit per second                                                                                                         |
+| ms                     | millisecond                                                                                                                |
+| MHz                    | megahertz                                                                                                                  |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|         |                                                                |
+|---------|----------------------------------------------------------------|
+| 3G      | 3rd Generation                                                 |
+| 3GPP    | 3G Partnership Project                                         |
+| 3-D     | Three Dimensional                                              |
+| 16QAM   | 16 Quadrature Amplitude Modulation                             |
+| A-MPR   | Additional Maximum Power Reduction                             |
+| BS      | Base Station                                                   |
+| CN      | Core Network                                                   |
+| DL      | Downlink                                                       |
+| DUT     | Device Under Test                                              |
+| ETSI    | European Telecommunications Standards Institute                |
+| E-UTRA  | Evolved Universal Terrestrial Radio Access                     |
+| LME     | Laptop Mounted Equipment                                       |
+| LEE     | Laptop Embedded Equipment                                      |
+| LTE     | Long Term Evolution                                            |
+| MPR     | Maximum Power Reduction                                        |
+| MS      | Mobile Station                                                 |
+| NB      | Node B                                                         |
+| QoS     | Quality of Service                                             |
+| QPSK    | Quadrature Phase Shift Keying (modulation)                     |
+| RAB     | Radio Access Bearer                                            |
+| RAN     | Radio Access Network                                           |
+| RB      | Resource Block                                                 |
+| RF      | Radio Frequency                                                |
+| Rx      | Receiver                                                       |
+| RBstart | RB number where a RB allocation begins within the channel      |
+| SAM     | Specific Anthropomorphic Mannequin                             |
+| Tx      | Transmitter                                                    |
+| TRP     | Total Radiated Power                                           |
+| TRS     | Total Radiated Sensitivity (also: Total Isotropic Sensitivity) |
+| UL      | Uplink                                                         |
+| UE      | User Equipment                                                 |
+| UTRA    | Universal Terrestrial Radio Access                             |
+
+# --- 4 General
+
+The present document is a Technical Report of the Study Item for OTA TRP and TRS requirement of LTE terminals, which was approved at TSG RAN #55 [2]. The report provides the measurement procedure of Over The Air TRP and TRS requirements for LTE terminals. It will make a simple extension to the UE OTA TRP and TRS test methods TR 25.914[4] for LTE UE with multiple receive antennas, without considering all of the aspects associated with spatial channels. The work should utilise the existing environments in TR 25.914[4]. The results of the UE OTA test method
+
+with Head and Hand Phantoms study item can be considered later on once finalized. The report also provides some future extensions and work items after LTE TRP and TRS methods mature.
+
+## 4.1 Scope
+
+The measurement procedure explained in this document applies to all LTE devices, which are already satisfied the standard 3GPP LTE RF minimum performance requirements and conformance testing defined in 3GPP TS 36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception[5] and 3GPP TS 36.521-1: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: conformance testing[6], respectively.
+
+The testing methodology applies to any 4G LTE handset, USB-dongle and LEE etc, with internal or external antenna. 3GPP TR 25.914[4] has done many meaningful studies for evaluating antenna performance of UMTS and GSM terminals. In this document, the majority work will be focus on the LTE TRP and TRS test. A simple test methodology for LTE devices without channel emulator will be studied.
+
+The radio tests considered here are:
+
+1. The measurement of the radiated output power (TRP)
+2. The measurement of the radiated sensitivity (TRS)
+
+The test procedure described in this document measures the performance of the transmitter and the receiver, including the antenna and also the effects of the user.
+
+The purpose of this document is to serve as a standard test procedure for radio performance testing of 4G LTE mobile terminals. It is the intention that this procedure is going to be used by test houses, network operators, mobile terminal and antenna manufacturers, research institutes etc. The motivation for the development of this document is the lack of standards in this area in 3GPP.
+
+During RAN4 #62bis following proposal were agreed.
+
+**Proposal 1:** LTE TRP test method is the same for all LTE UEs independent of release, including e.g. LTE CA, UL TX Div or UL MIMO capable UEs
+
+**Proposal 2:** LTE TRS test method is the same for all LTE UEs independent of release, including e.g. LTE CA, UL TX Div or UL MIMO capable UEs
+
+**Proposal 3:** In the first phase re-use test environments including phantoms available already in TS34.114 for LTE TRP and TRS purposes as well. Once new methods like hand phantom based test environments are defined for UTRA TRP and TRS, then also LTE TRP and TRS testing should be extended to these additional environments.
+
+During RAN4 #63 following proposal were agreed.
+
+**WF 1:** Select one channel bandwidth per band for TRP and TRS tests for LTE FDD and TDD. Default channel bandwidth is 10 MHz but another bandwidth can be considered on case by case basis.
+
+**WF2:** For TRS select the reference measurement channel configuration for LTE FDD and TDD as defined for the conducted REFSENS minimum requirements and adopt UL allocation per band as defined in 36.101 Table 7.3.1-2 [5]. TRS is measured on low, mid and high channel.
+
+**WF3:** For TRP select the UL reference measurement channel configuration as in conductive maximum output power test and the UL allocation for LTE FDD and TDD per band as shown in a table 1 below. Bands that are not covered in Table 1 will be addressed as well.
+
+**WF4:** Select combined LTE TRS measurement in order to make the test method available for all LTE devices starting from Release 8. (Note: further enhancements for radiated UE receiver verifications are developed under the MIMO OTA WI in RP-120368 [7] and therefore combined LTE TRS test method may eventually be revisited.)
+
+**WF5:** Given that existing TRP and TRS measurement procedures for UMTS terminals in speech mode specify two alternate testing methodologies (i.e. anechoic and reverb) [4], the standardization of two TRP/TRS testing
+
+methodologies for LTE UEs may be one eventual outcome, and RAN4 shall take the view to avoid differences in the absolute test results.
+
+## 4.2 Device Under Test definition
+
+Handset: the UE/MS used under the "Speech mode" or "Browsing mode" conditions that correspond to predefined positions (see Chapter 5.1.6 in [4] for "Speech mode" and Chapter 5.1.7 in [4] for "Browsing mode") for voice or data application when the handset is held close to the user.
+
+Laptop Embedded Equipment : the equipment with a wireless device embedded inside, e.g. notebook and tablet .The corresponding predefined positions for "data mode" application are defined in Chapter 5.3.1 in [4] for notebooks and Chapter 5.3.2 in [4] for tablets.
+
+Laptop Mounted Equipment : the plug-in type device that host on the laptop, e.g. USB-dongle, that correspond to predefined positions (see Chapter 5.1.4 in [4]) for "data mode" application.
+
+# --- 5 Measurement environment condition
+
+## 5.1 Chamber environment constraints
+
+Chamber environment constraints shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+## 5.2 Positioning Requirements and Coordinate system
+
+Positioning Requirements and Coordinate system shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+## 5.3 DUT Test Positions and Phantom Specifications
+
+### 5.3.1 Phantom Specifications
+
+Phantom Specifications shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+### 5.3.2 DUT Test Positions
+
+DUT Test Positions shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# --- 6 Measurement parameters
+
+Measurement parameters shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+## 6.1 Definition of the Total Radiated Power
+
+This definition will be used to calculate the TRP value of LTE DUT. See section 6.1 and E.2.1 in TR25.914[4].
+
+## 6.2 Definition of Total Radiated Sensitivity
+
+### 6.2.1 Total Radiated Sensitivity
+
+This definition will be used to calculate the TRS value of LTE DUT. See section 6.5 and E.2.2 in TR25.914[4].
+
+### 6.2.2 Alternate measurement parameter
+
+## 6.3 Sampling grid and independent samples
+
+For the anechoic chamber based measurement procedures the measurement of TRP is basically based on the measurement of the spherical radiation pattern of the Device Under Test. The power radiated by the DUT is sampled in far field in a group of points located on a spherical surface enclosing the DUT. The samples of TRP are taken using a constant sample step of  $15^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions.
+
+The measurement of TRS is basically based on the measurement of the spherical sensitivity pattern of the Device Under Test. The sensitivity values of the DUT at a predefined BLER level are sampled in far field in a group of points located on a spherical surface enclosing the DUT. The samples of TRS are taken using a constant sample step of  $30^\circ$  both in theta ( $\theta$ ) and phi ( $\phi$ ) directions.
+
+All the samples are taken with two orthogonal linear polarizations,  $\theta$ - and  $\phi$ -polarisations. It is also possible to measure some other polarisation components, if it is possible to recover  $\theta$ - and  $\phi$ -polarisations from the measured data by some technique.
+
+For the reverberation chamber based measurement procedures the measurement of TRP is basically based on sampling the radiated power of the Device-Under-Test for a discrete number of field combinations in the chamber. The average value of these statistically distributed samples is proportional to the Total Radiated Power, and by calibrating the average power transfer function in the chamber, an absolute value of the TRP can be obtained. The samples of TRP are taken so that a minimum of 100 independent Rayleigh faded samples are measured, as per section 5.1.3 in TS34.114[3].
+
+The measurement of TRS is basically based on searching for the lowest power received by the Device Under Test for a discrete number of field combinations in the chamber. The power received by the DUT at each discrete field combination that provides a BLER which is better than the specified target BLER level shall be averaged with other such measurements using different field combinations. By calibrating the average power transfer function, an absolute value of the TRS can be obtained when the linear values of all downlink power levels described above have been averaged. The samples of TRS are taken so that a minimum of 100 independent Rayleigh faded samples are measured, as per section 6.1.3 in TS34.114[3].
+
+## 6.4 Measurement frequencies
+
+This section defines the LTE-FDD and LTE-TDD TRP and TRS measurement frequencies allocations.
+
+**Table 6.4-1: TRP allocations (FDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 1</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 50             | 18050     | 10         | 2115                 | 1925                 | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 300            | 18300     | 10         | 2140                 | 1950                 | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 550            | 18550     | 10         | 2165                 | 1975                 | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 2</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 650            | 18650     | 10         | 1935                 | 1855                 | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 900            | 18900     | 10         | 1960                 | 1880                 | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 1150           | 19150     | 10         | 1985                 | 1905                 | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 3</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 1250           | 19250     | 10         | 1810                 | 1715                 | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 1575           | 19575     | 10         | 1842,5               | 1747,5               | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 1900           | 19900     | 10         | 1875                 | 1780                 | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 4</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2000           | 20000     | 10         | 2115                 | 1715                 | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 2175           | 20175     | 10         | 2132,5               | 1732,5               | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 2350           | 20350     | 10         | 2150                 | 1750                 | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 5</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2450           | 20450     | 10         | 874                  | 829                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 2525           | 20525     | 10         | 881,5                | 836,5                | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 2600           | 20600     | 10         | 889                  | 844                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 7</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2800           | 20800     | 10         | 2625                 | 2505                 | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 3100           | 21100     | 10         | 2655                 | 2535                 | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 3400           | 21400     | 10         | 2685                 | 2565                 | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 8</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 3500           | 21500     | 10         | 930                  | 885                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 3625           | 21625     | 10         | 942,5                | 897,5                | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 3750           | 21750     | 10         | 955                  | 910                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 12</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5060           | 23060     | 10         | 734                  | 704                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 5095           | 23095     | 10         | 737,5                | 707,5                | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 5130           | 23130     | 10         | 741                  | 711                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 13</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5230           | 23230     | 10         | 751                  | 782                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 5230           | 23230     | 10         | 751                  | 782                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 14</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5330           | 23330     | 10         | 763                  | 793                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 5330           | 23330     | 10         | 763                  | 793                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 17</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5780           | 23780     | 10         | 739                  | 709                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 5790           | 23790     | 10         | 740                  | 710                  | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 5800           | 23800     | 10         | 741                  | 711                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 19</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6050           | 24050     | 10         | 880                  | 835                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 6075           | 24075     | 10         | 882,5                | 837,5                | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 6100           | 24100     | 10         | 885                  | 840                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 20</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6200           | 24200     | 10         | 796                  | 837                  | NOTE 1              | NOTE 1                 | 12                  | 0                      |
+| 6300           | 24300     | 10         | 806                  | 847                  | NOTE 1              | NOTE 1                 | 12                  | 19                     |
+| 6400           | 24400     | 10         | 816                  | 857                  | NOTE 1              | NOTE 1                 | 12                  | 38                     |
+| <b>Band 21</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | NOTE 1              | NOTE 1                 | 16                  | 0                      |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | NOTE 1              | NOTE 1                 | 16                  | 29                     |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | NOTE 1              | NOTE 1                 | 16                  | 59                     |
+| <b>Band 22</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+
+|                                                                                                                                                                 |       |     |        |        |        |        |     |     |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-----|--------|--------|--------|--------|-----|-----|
+| <b>Band 23</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 24</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 25</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| 8065                                                                                                                                                            | 26065 | 5   | 1932.5 | 1852.5 | NOTE 1 | NOTE 1 | 8   | 0   |
+| 8365                                                                                                                                                            | 26365 | 5   | 1962.5 | 1882.5 | NOTE 1 | NOTE 1 | 8   | 8   |
+| 8665                                                                                                                                                            | 26665 | 5   | 1992.5 | 1912.5 | NOTE 1 | NOTE 1 | 8   | 17  |
+| <b>Band 26</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 27</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| TBD                                                                                                                                                             | TBD   | TBD | TBD    | TBD    | TBD    | TBD    | TBD | TBD |
+| <b>Band 28</b>                                                                                                                                                  |       |     |        |        |        |        |     |     |
+| 9260                                                                                                                                                            | 27260 | 10  | 763    | 708    | NOTE 1 | NOTE 1 | 12  | 0   |
+| 9410                                                                                                                                                            | 27410 | 10  | 778    | 723    | NOTE 1 | NOTE 1 | 12  | 19  |
+| 9610                                                                                                                                                            | 27610 | 10  | 798    | 743    | NOTE 1 | NOTE 1 | 12  | 38  |
+| NOTE 1: As per 3GPP TS 36.521-1 [6], Section 6.2 (UE Maximum Output Power), and Section A.3.2.A (Downlink Reference measurement channel for TX characteristics) |       |     |        |        |        |        |     |     |
+| NOTE 2: Network signalling value NS_01 shall be used in TRP tests                                                                                               |       |     |        |        |        |        |     |     |
+
+Table 6.4-2: TRP allocations (TDD)
+
+| DL EARFCN                                                                                                                                                       | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 33</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 36100                                                                                                                                                           | 36100     | 20         | 1910                 | 1910                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| <b>Band 34</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| TBD                                                                                                                                                             | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 35</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 36450                                                                                                                                                           | 36450     | 20         | 1860                 | 1860                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 36650                                                                                                                                                           | 36650     | 20         | 1880                 | 1880                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 36850                                                                                                                                                           | 36850     | 20         | 1900                 | 1900                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 36</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 37050                                                                                                                                                           | 37050     | 20         | 1940                 | 1940                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 37250                                                                                                                                                           | 37250     | 20         | 1960                 | 1960                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 37450                                                                                                                                                           | 37450     | 20         | 1980                 | 1980                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 37</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 37650                                                                                                                                                           | 37650     | 20         | 1920                 | 1920                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| <b>Band 38</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 37850                                                                                                                                                           | 37850     | 20         | 2580                 | 2580                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 38000                                                                                                                                                           | 38000     | 20         | 2595                 | 2595                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 38150                                                                                                                                                           | 38150     | 20         | 2610                 | 2610                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 39</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 38350                                                                                                                                                           | 38350     | 20         | 1890                 | 1890                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 38450                                                                                                                                                           | 38450     | 20         | 1900                 | 1900                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 38550                                                                                                                                                           | 38550     | 20         | 1910                 | 1910                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 40</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 38750                                                                                                                                                           | 38750     | 20         | 2310                 | 2310                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 39150                                                                                                                                                           | 39150     | 20         | 2350                 | 2350                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 39550                                                                                                                                                           | 39550     | 20         | 2390                 | 2390                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 41</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 39750                                                                                                                                                           | 39750     | 20         | 2506                 | 2506                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 40620                                                                                                                                                           | 40620     | 20         | 2593                 | 2593                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 41490                                                                                                                                                           | 41490     | 20         | 2680                 | 2680                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 42</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 41690                                                                                                                                                           | 41690     | 20         | 3410                 | 3410                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 42590                                                                                                                                                           | 42590     | 20         | 3500                 | 3500                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 43490                                                                                                                                                           | 43490     | 20         | 3590                 | 3590                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 43</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| 43690                                                                                                                                                           | 43690     | 20         | 3610                 | 3610                 | NOTE 1              | NOTE 1                 | 18                  | 0                      |
+| 44590                                                                                                                                                           | 44590     | 20         | 3700                 | 3700                 | NOTE 1              | NOTE 1                 | 18                  | 41                     |
+| 45490                                                                                                                                                           | 45490     | 20         | 3790                 | 3790                 | NOTE 1              | NOTE 1                 | 18                  | 82                     |
+| <b>Band 44</b>                                                                                                                                                  |           |            |                      |                      |                     |                        |                     |                        |
+| TBD                                                                                                                                                             | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| NOTE 1: As per 3GPP TS 36.521-1 [6], Section 6.2 (UE Maximum Output Power), and Section A.3.2.A (Downlink Reference measurement channel for TX characteristics) |           |            |                      |                      |                     |                        |                     |                        |
+| NOTE 2: Network signalling value NS_01 shall be used in TRP tests                                                                                               |           |            |                      |                      |                     |                        |                     |                        |
+
+**Table 6.4-3: TRS allocations (FDD)**
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 1</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 50             | 18050     | 10         | 2115                 | 1925                 | 50                  | 0                      | 50                  | 0                      |
+| 300            | 18300     | 10         | 2140                 | 1950                 | 50                  | 0                      | 50                  | 0                      |
+| 550            | 18550     | 10         | 2165                 | 1975                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 2</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 650            | 18650     | 10         | 1935                 | 1855                 | 50                  | 0                      | 50                  | 0                      |
+| 900            | 18900     | 10         | 1960                 | 1880                 | 50                  | 0                      | 50                  | 0                      |
+| 1150           | 19150     | 10         | 1985                 | 1905                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 3</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 1250           | 19250     | 10         | 1810                 | 1715                 | 50                  | 0                      | 50                  | 0                      |
+| 1575           | 19575     | 10         | 1842,5               | 1747,5               | 50                  | 0                      | 50                  | 0                      |
+| 1900           | 19900     | 10         | 1875                 | 1780                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 4</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2000           | 20000     | 10         | 2115                 | 1715                 | 50                  | 0                      | 50                  | 0                      |
+| 2175           | 20175     | 10         | 2132,5               | 1732,5               | 50                  | 0                      | 50                  | 0                      |
+| 2350           | 20350     | 10         | 2150                 | 1750                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 5</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2450           | 20450     | 10         | 874                  | 829                  | 50                  | 0                      | 25                  | 25                     |
+| 2525           | 20525     | 10         | 881,5                | 836,5                | 50                  | 0                      | 25                  | 25                     |
+| 2600           | 20600     | 10         | 889                  | 844                  | 50                  | 0                      | 25                  | 25                     |
+| <b>Band 7</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 2800           | 20800     | 10         | 2625                 | 2505                 | 50                  | 0                      | 50                  | 0                      |
+| 3100           | 21100     | 10         | 2655                 | 2535                 | 50                  | 0                      | 50                  | 0                      |
+| 3400           | 21400     | 10         | 2685                 | 2565                 | 50                  | 0                      | 50                  | 0                      |
+| <b>Band 8</b>  |           |            |                      |                      |                     |                        |                     |                        |
+| 3500           | 21500     | 10         | 930                  | 885                  | 50                  | 0                      | 25                  | 25                     |
+| 3625           | 21625     | 10         | 942,5                | 897,5                | 50                  | 0                      | 25                  | 25                     |
+| 3750           | 21750     | 10         | 955                  | 910                  | 50                  | 0                      | 25                  | 25                     |
+| <b>Band 12</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5060           | 23060     | 10         | 734                  | 704                  | 50                  | 0                      | 20                  | 30                     |
+| 5095           | 23095     | 10         | 737,5                | 707,5                | 50                  | 0                      | 20                  | 30                     |
+| 5130           | 23130     | 10         | 741                  | 711                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 13</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| 5230           | 23230     | 10         | 751                  | 782                  | 50                  | 0                      | 15                  | 0                      |
+| <b>Band 14</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| 5330           | 23330     | 10         | 763                  | 793                  | 50                  | 0                      | 20                  | 0                      |
+| <b>Band 17</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 5780           | 23780     | 10         | 739                  | 709                  | 50                  | 0                      | 20                  | 30                     |
+| 5790           | 23790     | 10         | 740                  | 710                  | 50                  | 0                      | 20                  | 30                     |
+| 5800           | 23800     | 10         | 741                  | 711                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 19</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6050           | 24050     | 10         | 880                  | 835                  | 50                  | 0                      | 25                  | 0                      |
+| 6075           | 24075     | 10         | 882,5                | 837,5                | 50                  | 0                      | 25                  | 0                      |
+| 6100           | 24100     | 10         | 885                  | 840                  | 50                  | 0                      | 25                  | 0                      |
+| <b>Band 20</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6200           | 24200     | 10         | 796                  | 837                  | 50                  | 0                      | 20                  | 30                     |
+| 6300           | 24300     | 10         | 806                  | 847                  | 50                  | 0                      | 20                  | 30                     |
+| 6400           | 24400     | 10         | 816                  | 857                  | 50                  | 0                      | 20                  | 30                     |
+| <b>Band 21</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | 75                  | 0                      | 25                  | 0                      |
+| 6525           | 24525     | 15         | 1503.4               | 1455.4               | 75                  | 0                      | 25                  | 0                      |
+| 6525           | 24525     | 15         | 1503.4               | TBD1455.4            | 75                  | 0                      | 25                  | 0                      |
+| <b>Band 22</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+
+|                                                                                                                              |       |     |        |        |     |     |     |     |
+|------------------------------------------------------------------------------------------------------------------------------|-------|-----|--------|--------|-----|-----|-----|-----|
+| <b>Band 23</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 24</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 25</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| 8065                                                                                                                         | 26065 | 5   | 1932.5 | 1852.5 | 25  | 0   | 25  | 0   |
+| 8365                                                                                                                         | 26365 | 5   | 1962.5 | 1882.5 | 25  | 0   | 25  | 0   |
+| 8665                                                                                                                         | 26665 | 5   | 1992.5 | 1912.5 | 25  | 0   | 25  | 0   |
+| <b>Band 26</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 27</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| TBD                                                                                                                          | TBD   | TBD | TBD    | TBD    | TBD | TBD | TBD | TBD |
+| <b>Band 28</b>                                                                                                               |       |     |        |        |     |     |     |     |
+| 9260                                                                                                                         | 27260 | 10  | 763    | 708    | 50  | 0   | 25  | 0   |
+| 9410                                                                                                                         | 27410 | 10  | 778    | 723    | 50  | 0   | 25  | 0   |
+| 9610                                                                                                                         | 27610 | 10  | 798    | 743    | 50  | 0   | 25  | 0   |
+| NOTE 1: Refer to TS 36.521 [6], Table A.3.2-1 (Fixed Reference Channel for Receiver Requirements (FDD)), 10MHz configuration |       |     |        |        |     |     |     |     |
+| NOTE 2: Network signalling value NS_01 shall be used in TRS tests unless explicitly specified                                |       |     |        |        |     |     |     |     |
+| NOTE 3: Network signalling value NS_03 shall be used for Bands 2, 4, and 23                                                  |       |     |        |        |     |     |     |     |
+| NOTE 4: Network signalling value NS_06 shall be used for Bands 12, 13, 14, and 17                                            |       |     |        |        |     |     |     |     |
+| NOTE 5: Network signalling value NS_08 shall be used for Band 19                                                             |       |     |        |        |     |     |     |     |
+| NOTE 6: Network signalling value NS_09 shall be used for Band 21                                                             |       |     |        |        |     |     |     |     |
+
+Table 6.4-4: TRS allocations (TDD)
+
+| DL EARFCN      | UL EARFCN | Channel BW | DL Carrier Frequency | UL Carrier frequency | DL C <sub>LRB</sub> | DL RB <sub>Start</sub> | UL C <sub>LRB</sub> | UL RB <sub>Start</sub> |
+|----------------|-----------|------------|----------------------|----------------------|---------------------|------------------------|---------------------|------------------------|
+| <b>Band 33</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 36100          | 36100     | 20         | 1910                 | 1910                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 34</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+| <b>Band 35</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 36450          | 36450     | 20         | 1860                 | 1860                 | 100                 | 0                      | 100                 | 0                      |
+| 36650          | 36650     | 20         | 1880                 | 1880                 | 100                 | 0                      | 100                 | 0                      |
+| 36850          | 36850     | 20         | 1900                 | 1900                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 36</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 37050          | 37050     | 20         | 1940                 | 1940                 | 100                 | 0                      | 100                 | 0                      |
+| 37250          | 37250     | 20         | 1960                 | 1960                 | 100                 | 0                      | 100                 | 0                      |
+| 37450          | 37450     | 20         | 1980                 | 1980                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 37</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 37650          | 37650     | 20         | 1920                 | 1920                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 38</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 37850          | 37850     | 20         | 2580                 | 2580                 | 100                 | 0                      | 100                 | 0                      |
+| 38000          | 38000     | 20         | 2595                 | 2595                 | 100                 | 0                      | 100                 | 0                      |
+| 38150          | 38150     | 20         | 2610                 | 2610                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 39</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 38350          | 38350     | 20         | 1890                 | 1890                 | 100                 | 0                      | 100                 | 0                      |
+| 38450          | 38450     | 20         | 1900                 | 1900                 | 100                 | 0                      | 100                 | 0                      |
+| 38550          | 38550     | 20         | 1910                 | 1910                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 40</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 38750          | 38750     | 20         | 2310                 | 2310                 | 100                 | 0                      | 100                 | 0                      |
+| 39150          | 39150     | 20         | 2350                 | 2350                 | 100                 | 0                      | 100                 | 0                      |
+| 39550          | 39550     | 20         | 2390                 | 2390                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 41</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 39750          | 39750     | 20         | 2506                 | 2506                 | 100                 | 0                      | 100                 | 0                      |
+| 40620          | 40620     | 20         | 2593                 | 2593                 | 100                 | 0                      | 100                 | 0                      |
+| 41490          | 41490     | 20         | 2680                 | 2680                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 42</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 41690          | 41690     | 20         | 3410                 | 3410                 | 100                 | 0                      | 100                 | 0                      |
+| 42590          | 42590     | 20         | 3500                 | 3500                 | 100                 | 0                      | 100                 | 0                      |
+| 43490          | 43490     | 20         | 3590                 | 3590                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 43</b> |           |            |                      |                      |                     |                        |                     |                        |
+| 43690          | 43690     | 20         | 3610                 | 3610                 | 100                 | 0                      | 100                 | 0                      |
+| 44590          | 44590     | 20         | 3700                 | 3700                 | 100                 | 0                      | 100                 | 0                      |
+| 45490          | 45490     | 20         | 3790                 | 3790                 | 100                 | 0                      | 100                 | 0                      |
+| <b>Band 44</b> |           |            |                      |                      |                     |                        |                     |                        |
+| TBD            | TBD       | TBD        | TBD                  | TBD                  | TBD                 | TBD                    | TBD                 | TBD                    |
+
+NOTE 1: Refer to TS 36.521 [6], Table A.3.2-2 (Fixed Reference Channel for Receiver Requirements (TDD)), 20MHz configuration
+
+NOTE 2: Network signalling value NS\_01 shall be used in TRS tests
+
+# 7 Measurement procedure – transmitter performance
+
+This section describes the specifics of the radiated power measurement procedure.
+
+Measurement procedure – transmitter performance shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+## 7.1 General measurement arrangements
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator may also measure the radiated power samples. Alternatively, a measurement receiver or spectrum analyzer may be used for that purpose.
+
+As section 4.2 definition, the measurements are performed for Handset, Laptop Embedded Equipment and Laptop Mounted Equipment.
+
+- 1) The DUT of Handset should be placed against a head phantom. The measurement of the DUT is performed both on the left and right ears of the head phantom. And the scenario of placed against a head phantom and hold by the hand phantom is suggested to test. The measurement of the DUT is performed both on the left and right ears of the head phantom. Meanwhile, Hand phantom only is also suggested to test. The measurement of the DUT is performed both on the left and right hand phantom. The characteristics of the phantoms are specified in section 5.3.
+- 2) The DUT of laptop embedded equipment should be placed in the following environment: free space for notebook devices (detailed positioning and specification refer to section 5.3.1 in [4]) and free space for tablet devices (detailed positioning and specification refer to section 5.3.2 in [4]).
+- 3) The DUT of laptop mounted equipment should be using laptop ground plane phantom for testing scenario. Detailed phantom positioning and specification refer to section 5.3.
+
+The measurements will be performed for the different antenna configurations of the DUT. For example in the case of a retractable antenna, for both antenna extended and antenna retracted configurations. In future, more specific test configurations for each major type of terminals may be added in this part.
+
+More detail description of the BS simulator or spectrum analyser sees section 7.2 below and Annex A System Parameters.
+
+## 7.2 Procedure for radiated power measurement
+
+1. Set the initial conditions as per section 6.2.2 of 3GPP TS 36.521-1, with the following exception: configure the system simulator and the DUT as per section 5, and set the carrier frequency, channel bandwidth, RB length and RB location as per Table 6.4-1 and Table 6.4-2 respectively for FDD and TDD modes.
+2. Follow steps 1 and 2 in section 6.2.2.4.2 of 3GPP TS 36.521-1 and ensure that the DUT transmits with its maximum power.
+3. For the anechoic chamber based methodologies, measure the spherical effective isotropic radiated power (EIRP) pattern. And following the sampling grid specified in section 6.3 is suggested. For TDD slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD is set as per Table 8.2.2-1 of 3GPP TS 36.521-1. Calculate the TRP using the EIRP pattern data as per section 6.1.
+
+For the reverberation chamber based measurement methodologies, sample the radiated power of the Device Under Test (DUT) for a discrete number of field combinations in the chamber. Follow the guidelines about independent samples in section 6.3. For TDD slots with transient periods are not under test. The uplink downlink configuration and the special subframe configuration in TDD is set as per Table 8.2.2-1 of 3GPP TS 36.521-1. Calculate the TRP using the power samples as per section 6.1.
+
+4. In the case of handset DUT, repeat steps 1 through 3 using the head phantom only, head and hand phantom, and hand phantom only. The head phantom only, head and hand phantom, hand phantom only testing are as per section 5.3. For laptop mounted equipment DUT, the laptop ground plane phantom is used. For laptop embedded equipment notebook DUT, free space test is used. For laptop embedded equipment tablet DUT, free space test is used; the test configuration may be enhanced once definitions of new testing conditions related to the tablet device categories become available (see Chapter 5.3.2 in [4]).
+
+## 7.3 Calibration measurement
+
+Calibration measurement shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# --- 8 Measurement procedure – receiver performance
+
+This section describes the specifics of the radiated sensitivity measurement procedure.
+
+Measurement procedure – transmitter performance shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+## 8.1 General measurement arrangements
+
+A radio communications tester or a corresponding device is used as a NB/BS simulator to setup calls to the DUT. The NB/BS simulator is also used to send test signals to the UE and measure the BLER levels of the radio link and the information on the dedicated channel needed to extract the DUT receiver performances.
+
+As section 4.2 definition, the measurements are performed for Handset, Laptop Embedded Equipment and Laptop Mounted Equipment.
+
+- 1) The DUT of Handset should be placed against a head phantom. The measurement of the DUT is performed both on the left and right ears of the head phantom. And the scenario of placed against a head phantom and hold by the hand phantom is suggested to test. The measurement of the DUT is performed both on the left and right ears of the head phantom. Meanwhile, Hand phantom only is also suggested to test. The measurement of the DUT is performed both on the left and right hand phantom. The characteristics of the phantoms are specified in section 5.3.
+- 2) The DUT of laptop embedded equipment should be placed in the following environment: free space for notebook devices (detailed positioning and specification refer to section 5.3.1 in [4]) and free space for tablet devices (detailed positioning and specification refer to section 5.3.2 in [4]).
+- 3) The DUT of laptop mounted equipment should be using laptop ground plane phantom for testing scenario. Detailed phantom positioning and specification refer to section 5.3.
+
+The measurements will be performed for the different antenna configurations of the DUT. For example in the case of a retractable antenna, for both antenna extended and retracted configurations. In future, more specific test configurations for each major type of terminals may be added in this part.
+
+More detail description of the BS simulator see section 8.2 below and Annex A System Parameters.
+
+## 8.2 Procedure for radiated sensitivity measurement
+
+1. Set the initial conditions as per section 7.3 of 3GPP TS 36.521-1, with the following exception: configure the system simulator and the DUT as per section 5, and set the carrier frequency, channel bandwidth, RB length and RB location as per Table 6.4-3 and Table 6.4-4 respectively for FDD and TDD modes. For DUTs with more than one receiver port, all the tests should be performed using both (all) antenna ports simultaneously.
+2. Follow steps 1 through 4 in sections of 7.3.4.2 of 3GPP TS 36.521-1, with the following exception: measure the receiver sensitivity by adjusting the downlink signal level to 95 % throughput of the maximum throughput of the reference channel (maximum throughput is per Appendix A of 3GPP TS 36.521-1).
+3. For the anechoic chamber based methodologies, repeat step 2 with 3-D sampling grid specified in section 6.3. The minimum RF power level resulting a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for integration pursuant to section 6.2 to calculate TRS.
+
+For the reverberation chamber based methodologies, repeat step 2 for a number of independent samples as specified in section 6.3. The minimum RF power level resulting in a data throughput greater than or equal to 95 % throughput of the maximum throughput for each test shall be recorded for averaging pursuant to section 6.2 to calculate TRS.
+
+4. In the case of handset DUT, repeat steps 1 through 3 using the head phantom only, head and hand phantom, and hand phantom only. The head phantom only, head and hand phantom, hand phantom only testing are as per section 5.3. For laptop mounted equipment, the laptop ground plane phantom is used. For laptop embedded equipment notebook DUT, free space test is used. For laptop embedded equipment tablet DUT, free space test is used; the test configuration may be enhanced once definitions of new testing conditions related to the tablet device categories become available (see Chapter 5.3.2 in [4]).
+
+## 8.3 Calibration measurement
+
+Calibration measurement shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# --- Annex A: System Parameters ---
+
+## A.1 Definition and applicability
+
+This test is aimed at measuring the output power radiated and receiver sensitivity by a LTE DUT in max transmit power.
+
+Radio measurements are performed in the so-called open area mode in such a way to be as close as possible to the free space conditions.
+
+## --- A.2 Establishing the connection
+
+In order to be as close as possible to the real conditions of use, it is necessary to establish the connection between the UE/MS under test and the eNodeB simulator. It makes thus possible to set up the communication parameters to simulate a data link.
+
+## --- A.3 Uplink RB allocation for reference sensitivity
+
+This section is just providing the uplink RB allocation table for information, and Table A.3-1 is same as Table 7.3.1-2 in TS36.101.[5]
+
+Table A.3-1 (for information): Uplink configuration for reference sensitivity
+
+| E-UTRA Band / Channel bandwidth / NRB / Duplex mode |         |       |       |                 |                 |                 |             |
+|-----------------------------------------------------|---------|-------|-------|-----------------|-----------------|-----------------|-------------|
+| E-UTRA Band                                         | 1.4 MHz | 3 MHz | 5 MHz | 10 MHz          | 15 MHz          | 20 MHz          | Duplex Mode |
+| 1                                                   |         |       | 25    | 50              | 75              | 100             | FDD         |
+| 2                                                   | 6       | 15    | 25    | 50              | 501             | 501             | FDD         |
+| 3                                                   | 6       | 15    | 25    | 50              | 501             | 501             | FDD         |
+| 4                                                   | 6       | 15    | 25    | 50              | 75              | 100             | FDD         |
+| 5                                                   | 6       | 15    | 25    | 251             |                 |                 | FDD         |
+| 6                                                   |         |       | 25    | 251             |                 |                 | FDD         |
+| 7                                                   |         |       | 25    | 50              | 751             | 751             | FDD         |
+| 8                                                   | 6       | 15    | 25    | 251             |                 |                 | FDD         |
+| 9                                                   |         |       | 25    | 50              | 501             | 501             | FDD         |
+| 10                                                  |         |       | 25    | 50              | 75              | 100             | FDD         |
+| 11                                                  |         |       | 25    | 251             |                 |                 | FDD         |
+| 12                                                  | 6       | 15    | 201   | 201             |                 |                 | FDD         |
+| 13                                                  |         |       | 201   | 201             |                 |                 | FDD         |
+| 14                                                  |         |       | 151   | 151             |                 |                 | FDD         |
+| ...                                                 |         |       |       |                 |                 |                 |             |
+| 17                                                  |         |       | 201   | 201             |                 |                 | FDD         |
+| 18                                                  |         |       | 25    | 25 <sup>1</sup> | 25 <sup>1</sup> |                 | FDD         |
+| 19                                                  |         |       | 25    | 25 <sup>1</sup> | 25 <sup>1</sup> |                 | FDD         |
+| 20                                                  |         |       | 25    | 20 <sup>1</sup> | 20 <sup>3</sup> | 20 <sup>3</sup> | FDD         |
+| 21                                                  |         |       | 25    | 25 <sup>1</sup> | 25 <sup>1</sup> |                 | FDD         |
+| 22                                                  |         |       | 25    | 50              | 501             | 501             | FDD         |
+| 23                                                  | 6       | 15    | 25    | 50              |                 |                 | FDD         |
+| 24                                                  |         |       | 25    | 50              |                 |                 | FDD         |
+| 25                                                  | 6       | 15    | 25    | 50              | 501             | 501             | FDD         |
+| 26                                                  | 6       | 15    | 25    | 251             | 251             |                 | FDD         |
+| 27                                                  | 6       | 15    | 25    | 25 <sup>1</sup> |                 |                 | FDD         |
+| 28                                                  |         | 15    | 25    | 25 <sup>1</sup> | 25 <sup>1</sup> | 25 <sup>1</sup> | FDD         |
+| ...                                                 |         |       |       |                 |                 |                 |             |
+| 33                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 34                                                  |         |       | 25    | 50              | 75              |                 | TDD         |
+| 35                                                  | 6       | 15    | 25    | 50              | 75              | 100             | TDD         |
+| 36                                                  | 6       | 15    | 25    | 50              | 75              | 100             | TDD         |
+| 37                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 38                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 39                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 40                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 41                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 42                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 43                                                  |         |       | 25    | 50              | 75              | 100             | TDD         |
+| 44                                                  |         | 15    | 25    | 50              | 75              | 100             | TDD         |
+
+NOTE 1: <sup>1</sup> refers to the UL resource blocks shall be located as close as possible to the downlink operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.6-1).
+
+NOTE 2: For the UE which supports both Band 11 and Band 21 the uplink configuration for reference sensitivity is FFS.
+
+NOTE 3: <sup>3</sup> refers to Band 20; in the case of 15MHz channel bandwidth, the UL resource blocks shall be located at RB<sub>start</sub> 11 and in the case of 20MHz channel bandwidth, the UL resource blocks shall be located at RB<sub>start</sub> 16
+
+# --- Annex B: Measurement Uncertainty
+
+Measurement Uncertainty shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# --- Annex C:
+
+## Anechoic chamber specifications and validation method
+
+Anechoic chamber specifications and validation method shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# --- Annex D: Reverberation chamber specifications and validation method
+
+Reverberation chamber specifications and validation method shall be the same as described in TR25.914[4] unless otherwise defined in this TR. This TR only defines differences compared to TR25.914[4].
+
+# Annex E: Change history
+
+| Change history |            |           |      |     |                                                                                               |        |        |
+|----------------|------------|-----------|------|-----|-----------------------------------------------------------------------------------------------|--------|--------|
+| Date           | TSG #      | TSG Doc.  | CR   | Rev | Subject/Comment                                                                               | Old    | New    |
+| 2012-03        | RAN4#62bis | R4-122129 |      |     | Skeleton for LTE TRP TRS study item                                                           | N/A    | 0.0.1  |
+| 2012-05        | RAN4#63    | R4-122506 |      |     | TP of small correction for TRab.cde (LTE TRP TRS)                                             | 0.0.1  | 1.0.0  |
+| 2012-05        | RAN4#63    | R4-122774 |      |     | LTE TRP and TRS test method development                                                       | 0.0.1  | 1.0.0  |
+| 2012-05        | RAN4#63    | R4-123581 |      |     | TP for TRab.cde (LTE TRP TRS) General updating from existing standards                        | 0.0.1  | 1.0.0  |
+| 2012-05        | RAN4#63    | R4-123629 |      |     | Way forward proposal for LTE TRP and TRS test method development                              | 0.0.1  | 1.0.0  |
+| 2012-08        | RAN4#64    | R4-124952 |      |     | TP to TR 37.902: LTE TRP and TRS measurement frequency allocation                             | 1.0.0  | 1.1.0  |
+| 2012-08        | RAN4#64    | R4-124953 |      |     | TP to TR 37.902: Measurement method and measurement procedure                                 | 1.0.0  | 1.1.0  |
+| 2012-08        | RAN#64     | R4-125002 |      |     | LTE TRP/TRS TR 37.902 v 1.1.0                                                                 | 1.1.0  | 2.0.0  |
+| 2012-09        | RAN#57     | RP-121163 |      |     | TR 37.902 Presented to RAN for Approval                                                       | 2.0.0  | -      |
+| 2012-09        | RAN-57     |           |      |     | TR Approved by RAN-57                                                                         | 2.0.0  | 11.0.0 |
+| 2012-12        |            |           |      |     | Correction of typo on cover page                                                              | 11.0.0 | 11.0.1 |
+| 2013-12        | RAN-62     | RP-131968 | 0001 | -   | CR on correction of TRP and TRS measurement procedure for TR37.902                            | 11.0.1 | 11.1.0 |
+| 2013-12        | RAN-62     | RP-131931 | 0002 | -   | Network signaling values in LTE TRP and TRS tests                                             | 11.0.1 | 11.1.0 |
+| 09-2014        | RP-65      | RP-141544 | 0005 |     | CR to TR37.902 on improving tablets definition                                                | 11.1.0 | 12.0.0 |
+| 09-2014        | RP-65      | RP-141544 | 0006 |     | CR to TR37.902 on explicitly listing TRS allocations                                          | 11.1.0 | 12.0.0 |
+| 12-2014        | RP-66      | RP-142171 | 007  | 1   | CR to TR 37.902 on TRP and TRS allocations for bands 19, 21, and 28 and editorial corrections | 12.0.0 | 12.1.0 |
+| 2016-01        | SP-70      | -         | -    | -   | Update to Rel-13 version (MCC)                                                                | 12.1.0 | 13.0.0 |
+| 2017-03        | RP-75      | -         | -    | -   | Update to Rel-14 version (MCC)                                                                | 13.0.0 | 14.0.0 |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-06        | SA#80   | -    | -  | -   | -   | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06        | SA#88   | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37910/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg b/marked/Rel-16/37_series/37910/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6f7fff965d2686770cd75e55abb982832903f6b9
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f066f733570acc98c1ab9cd425434c281fb1035d34a37ff6274ac913451340c
+size 50361
diff --git a/marked/Rel-16/37_series/37910/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/37_series/37910/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e2851371f5416c1302e751253518243b06880d9
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d9acd8d7fcf18c0b4b1dd52363444bcf42105d9726ca918be5e2d14e68cc2f39
+size 30098
diff --git a/marked/Rel-16/37_series/37910/1c140ee5d1a87186977da94a96bfa700_img.jpg b/marked/Rel-16/37_series/37910/1c140ee5d1a87186977da94a96bfa700_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..71f344420848987e87c9f9a653df8cf25c8b0875
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/1c140ee5d1a87186977da94a96bfa700_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b47504332a19defc930746f0bc97aa936d0841822b419f6381d38594b9bb5e6
+size 13297
diff --git a/marked/Rel-16/37_series/37910/236f674770a03c918c0375a74fe950db_img.jpg b/marked/Rel-16/37_series/37910/236f674770a03c918c0375a74fe950db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0140a7c5f2d3f247508111877d851d3ddd6a9fa3
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/236f674770a03c918c0375a74fe950db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:595e6ae68823dccb2d3be1ffed8384a93484d56c8e6ed95bd5085f16927f4d67
+size 25231
diff --git a/marked/Rel-16/37_series/37910/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/37_series/37910/26d664119ad25250780f554633444e54_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b4cd10edb0f2446718980ddf4375050b99961a9b
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/26d664119ad25250780f554633444e54_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbf9b1a1e042b3d98f544b5be898d251c8c77df50b144d61273cf934bd6960b6
+size 25426
diff --git a/marked/Rel-16/37_series/37910/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/37_series/37910/4356776ca004ecba5d599667a155d7d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b60faf7089d921b127017409a6c7fd9bf74f183
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/4356776ca004ecba5d599667a155d7d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8185bd12b3740620a5fb529dde039c7eed4ca6ffc63bb1713ef12318fe40acc
+size 75044
diff --git a/marked/Rel-16/37_series/37910/54d490f646eb3cc3b92ec4abf3030a85_img.jpg b/marked/Rel-16/37_series/37910/54d490f646eb3cc3b92ec4abf3030a85_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..637529a6eae648dbf73f3b174dd422b01f2900a4
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/54d490f646eb3cc3b92ec4abf3030a85_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6570d6552d68d2d3a543481011b67e63495d77fb49cb156294e0a512ba43e42c
+size 52961
diff --git a/marked/Rel-16/37_series/37910/730b6615db6d402580db1024a7f4e163_img.jpg b/marked/Rel-16/37_series/37910/730b6615db6d402580db1024a7f4e163_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8b1a75a95f48dfb8593854ce3c586b958a482e52
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/730b6615db6d402580db1024a7f4e163_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b4c8110f4ae1192f509c4fed9b79e49a45e6a35991380adac0264fb709e60af0
+size 50818
diff --git a/marked/Rel-16/37_series/37910/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/37_series/37910/78ffccd66df9bafd96e3e081110d09dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2183e47600fb23269effce8e6a0561d05a685dab
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/78ffccd66df9bafd96e3e081110d09dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25333c82dc7b8d9680dc96d6391b654d7516196c8978af0b87f62882670c0dd4
+size 72871
diff --git a/marked/Rel-16/37_series/37910/79607caa47ed192b11a2c7b17f0b88dd_img.jpg b/marked/Rel-16/37_series/37910/79607caa47ed192b11a2c7b17f0b88dd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ed2bf3262fea23404772a511cb9a38b3a2c4144
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/79607caa47ed192b11a2c7b17f0b88dd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84e662cbc62c37948f1166d822eac2d3df1abfe82107a92cf4a27563894a467b
+size 118433
diff --git a/marked/Rel-16/37_series/37910/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg b/marked/Rel-16/37_series/37910/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b1f87a45c312262937417dcb1b0378d865330c2e
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f4b2814431d24397374657006b162b094da2f0c11cb60039eada751b19ae73b
+size 97698
diff --git a/marked/Rel-16/37_series/37910/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/37_series/37910/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b070873a05e99a58aa1752671a019922a975ce02
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:daaae5c3cde4b42ad57f480c1609ca8228da0b752a65578dd7711464bbf39e0a
+size 14940
diff --git a/marked/Rel-16/37_series/37910/a26b4f52392209236513dd503db41339_img.jpg b/marked/Rel-16/37_series/37910/a26b4f52392209236513dd503db41339_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..098c7147076f59582228e8731789eddeebc0a191
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/a26b4f52392209236513dd503db41339_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1cccb321f19dd6b2c5e45055101a931f2f7467a40e573bc6265543a062526c77
+size 53512
diff --git a/marked/Rel-16/37_series/37910/cc3cf220e0c191212afa284c6787da0a_img.jpg b/marked/Rel-16/37_series/37910/cc3cf220e0c191212afa284c6787da0a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5fd2371029ca877e5692f8d9eca744345e0bfa8e
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/cc3cf220e0c191212afa284c6787da0a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:24a7446808b82a400a7eb2b14a4e1b8b62c64018e189bdcf4a4d50c476428b34
+size 57204
diff --git a/marked/Rel-16/37_series/37910/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/marked/Rel-16/37_series/37910/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e9e4d4c15f7bb43f1c18d7f382a9ca330088809c
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e099b02f85c456fc3cb16d60efc72ff61b188dd791d3d055e4c261e31213f884
+size 32730
diff --git a/marked/Rel-16/37_series/37910/d0c2bd517f31d89b01136a1847bcdf33_img.jpg b/marked/Rel-16/37_series/37910/d0c2bd517f31d89b01136a1847bcdf33_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2a2fee874bb8c6f2c79367c738ded5ea0e3ddad7
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/d0c2bd517f31d89b01136a1847bcdf33_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a5eec3ab6b2bb334c795e3a993bb3f098dade100dd60173054d5675e0f933fd
+size 59520
diff --git a/marked/Rel-16/37_series/37910/d78e519e9186d30807342196675fd440_img.jpg b/marked/Rel-16/37_series/37910/d78e519e9186d30807342196675fd440_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c81627435ded38897a9521a418f5d26a772a59ab
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/d78e519e9186d30807342196675fd440_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0ea4d1243481101516577d47a87a875b6488c7027912c5ae3556bfb43fd739c8
+size 14023
diff --git a/marked/Rel-16/37_series/37910/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/marked/Rel-16/37_series/37910/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2afd9c2e2270b8afd08247cea1b4150925a5ac45
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:06f96b91efbf6b2a5668b10566766b5306f091aac3c74c857fefd48546967baf
+size 29639
diff --git a/marked/Rel-16/37_series/37910/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/37_series/37910/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..424680edc1f4a60d5079c8ef0e47975d85aac7c8
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b7045eb693e480f32d61233da974d8cde46f6d7e3aa69a78d962c9ca5faa982
+size 43843
diff --git a/marked/Rel-16/37_series/37910/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg b/marked/Rel-16/37_series/37910/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..032c1904aca176d69067edbc60e09d02c5055260
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:99715dc8cd29e891ecf1e24eee9a5f9f29b942e800c29d85f4a8d396486d6e00
+size 52630
diff --git a/marked/Rel-16/37_series/37910/raw.md b/marked/Rel-16/37_series/37910/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..84c069ac96978ca524f08fc72fe1d49cdec887a9
--- /dev/null
+++ b/marked/Rel-16/37_series/37910/raw.md
@@ -0,0 +1,4923 @@
+# **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on self evaluation towards IMT-2020 submission (Release 16)** ---
+
+## Keywords ---
+
+Radio, NR, LTE
+
+## **3GPP**
+
+## Postal address ---
+
+## 3GPP support office address ---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+## Internet ---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTSTM is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# --- Contents
+
+|                                                              |    |
+|--------------------------------------------------------------|----|
+| Foreword .....                                               | 7  |
+| 1 Scope.....                                                 | 8  |
+| 2 References.....                                            | 8  |
+| 3 Definitions, symbols and abbreviations.....                | 9  |
+| 3.1 Definitions.....                                         | 9  |
+| 3.2 Symbols.....                                             | 9  |
+| 3.3 Abbreviations .....                                      | 9  |
+| 4 Introduction.....                                          | 10 |
+| 5 Self evaluation of eMBB technical performance.....         | 10 |
+| 5.1 Peak spectral efficiency.....                            | 11 |
+| 5.1.1 NR.....                                                | 11 |
+| 5.1.1.1 DL peak spectral efficiency .....                    | 12 |
+| 5.1.1.2 UL peak spectral efficiency .....                    | 13 |
+| 5.1.2 LTE.....                                               | 15 |
+| 5.1.2.1 DL peak spectral efficiency .....                    | 15 |
+| 5.1.2.2 UL peak spectral efficiency .....                    | 15 |
+| 5.2 Peak data rate .....                                     | 16 |
+| 5.2.1 NR.....                                                | 16 |
+| 5.2.1.1 DL peak data rate.....                               | 16 |
+| 5.2.1.2 UL peak data rate.....                               | 17 |
+| 5.2.2 LTE.....                                               | 18 |
+| 5.2.2.1 DL peak data rate.....                               | 18 |
+| 5.2.2.2 UL peak data rate.....                               | 18 |
+| 5.3 5 <sup>th</sup> percentile user spectral efficiency..... | 18 |
+| 5.4 Average spectral efficiency .....                        | 18 |
+| 5.4.1 NR.....                                                | 18 |
+| 5.4.1.1 Indoor Hotspot – eMBB .....                          | 19 |
+| 5.4.1.1.1 Evaluation configuration A (CF = 4 GHz).....       | 19 |
+| 5.4.1.1.2 Evaluation configuration B (CF = 30 GHz).....      | 25 |
+| 5.4.1.2 Dense Urban – eMBB.....                              | 29 |
+| 5.4.1.2.1 Evaluation configuration A (CF = 4 GHz).....       | 29 |
+| 5.4.1.2.2 Evaluation configuration B (CF=30 GHz).....        | 35 |
+| 5.4.1.3 Rural – eMBB.....                                    | 36 |
+| 5.4.1.3.1 Evaluation configuration A (CF = 700 MHz) .....    | 36 |
+| 5.4.1.3.2 Evaluation configuration B (CF = 4 GHz).....       | 40 |
+| 5.4.1.3.3 Evaluation configuration C (LMLC).....             | 44 |
+| 5.4.2 LTE.....                                               | 48 |
+| 5.4.2.1 Indoor Hotspot – eMBB .....                          | 48 |
+| 5.4.2.1.1 Evaluation configuration A (CF = 4 GHz).....       | 48 |
+| 5.4.2.2 Dense Urban – eMBB.....                              | 49 |
+| 5.4.2.2.1 Evaluation configuration A (CF = 4 GHz).....       | 49 |
+| 5.4.2.3 Rural – eMBB.....                                    | 51 |
+| 5.4.2.3.1 Evaluation configuration A (CF = 700 MHz) .....    | 51 |
+| 5.4.2.3.2 Evaluation configuration B (CF = 4 GHz).....       | 52 |
+| 5.4.2.3.3 Evaluation configuration C (LMLC).....             | 53 |
+| 5.5 User experienced data rate .....                         | 54 |
+| 5.5.1 NR.....                                                | 54 |
+| 5.5.1.1 Dense Urban – eMBB.....                              | 55 |
+| 5.5.1.1.1 Evaluation configuration A (CF = 4 GHz).....       | 55 |
+| 5.5.1.1.2 Evaluation configuration B (CF = 30 GHz).....      | 60 |
+| 5.5.1.1.3 Evaluation configuration C .....                   | 60 |
+| 5.5.2 LTE.....                                               | 61 |
+| 5.5.2.1 Dense Urban – eMBB.....                              | 61 |
+| 5.5.2.1.1 Evaluation configuration A (CF = 4 GHz).....       | 62 |
+| 5.6 Area traffic capacity .....                              | 63 |
+
+|           |                                                |     |
+|-----------|------------------------------------------------|-----|
+| 5.6.1     | NR.....                                        | 63  |
+| 5.6.1.1   | Indoor Hotspot – eMBB .....                    | 63  |
+| 5.6.1.1.1 | Evaluation configuration A (CF = 4 GHz).....   | 64  |
+| 5.6.1.1.2 | Evaluation configuration B (CF = 30 GHz).....  | 66  |
+| 5.6.2     | LTE.....                                       | 68  |
+| 5.6.2.1   | Indoor Hotspot – eMBB .....                    | 68  |
+| 5.6.2.1.1 | Evaluation configuration A (CF = 4 GHz).....   | 68  |
+| 5.7       | Latency .....                                  | 69  |
+| 5.7.1     | User plane latency .....                       | 69  |
+| 5.7.1.1   | NR.....                                        | 69  |
+| 5.7.1.1.1 | Downlink.....                                  | 70  |
+| 5.7.1.1.2 | Uplink.....                                    | 73  |
+| 5.7.1.2   | LTE .....                                      | 77  |
+| 5.7.1.2.1 | Downlink.....                                  | 77  |
+| 5.7.1.2.2 | Uplink.....                                    | 78  |
+| 5.7.2     | Control plane latency.....                     | 80  |
+| 5.7.2.1   | NR.....                                        | 80  |
+| 5.7.2.2   | LTE .....                                      | 85  |
+| 5.8       | Energy efficiency .....                        | 89  |
+| 5.8.1     | Network side.....                              | 90  |
+| 5.8.1.1   | NR.....                                        | 90  |
+| 5.8.1.1.1 | Evaluation of sleep ratio.....                 | 91  |
+| 5.8.1.1.2 | Evaluation of sleep duration.....              | 92  |
+| 5.8.1.2   | LTE .....                                      | 92  |
+| 5.8.1.2.1 | Evaluation of sleep ratio.....                 | 93  |
+| 5.8.1.2.2 | Evaluation of sleep duration.....              | 93  |
+| 5.8.2     | Device side .....                              | 94  |
+| 5.8.2.1   | NR.....                                        | 94  |
+| 5.8.2.1.1 | Evaluation of sleep ratio.....                 | 94  |
+| 5.8.2.1.2 | Evaluation of sleep duration.....              | 95  |
+| 5.8.2.2   | LTE .....                                      | 95  |
+| 5.8.2.2.1 | Evaluation of sleep ratio.....                 | 95  |
+| 5.8.2.2.2 | Evaluation of sleep duration.....              | 97  |
+| 5.9       | Mobility.....                                  | 97  |
+| 5.9.1     | NR.....                                        | 97  |
+| 5.9.1.1   | Indoor Hotspot – eMBB .....                    | 97  |
+| 5.9.1.1.1 | Evaluation configuration A (CF = 4 GHz).....   | 97  |
+| 5.9.1.1.2 | Evaluation configuration B (CF = 30 GHz).....  | 98  |
+| 5.9.1.2   | Dense Urban – eMBB.....                        | 99  |
+| 5.9.1.2.1 | Evaluation configuration A (CF = 4 GHz).....   | 99  |
+| 5.9.1.2.2 | Evaluation configuration B (CF = 30 GHz).....  | 100 |
+| 5.9.1.3   | Rural – eMBB.....                              | 101 |
+| 5.9.1.3.1 | Evaluation configuration A (CF = 700 MHz)..... | 101 |
+| 5.9.1.3.2 | Evaluation configuration B (CF = 4 GHz).....   | 102 |
+| 5.9.2     | LTE.....                                       | 103 |
+| 5.9.2.1   | Indoor Hotspot – eMBB .....                    | 103 |
+| 5.9.2.1.1 | Evaluation configuration A (CF = 4 GHz).....   | 103 |
+| 5.9.2.2   | Dense Urban – eMBB.....                        | 104 |
+| 5.9.2.2.1 | Evaluation configuration A (CF = 4 GHz).....   | 104 |
+| 5.9.2.3   | Rural – eMBB.....                              | 104 |
+| 5.9.2.3.1 | Evaluation configuration A (CF = 700 MHz)..... | 104 |
+| 5.10      | Mobility interruption time .....               | 106 |
+| 5.10.1    | NR.....                                        | 106 |
+| 5.10.1.1  | Scenarios.....                                 | 106 |
+| 5.10.1.2  | Beam mobility.....                             | 106 |
+| 5.10.1.3  | CA Mobility .....                              | 106 |
+| 5.10.2    | LTE.....                                       | 106 |
+| 5.10.2.1  | Scenarios.....                                 | 106 |
+| 5.10.2.2  | PCell mobility .....                           | 107 |
+| 5.10.2.3  | DC Mobility .....                              | 107 |
+
+|                 |                                                                                                                                                  |            |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------|
+| 6               | Self evaluation of URLLC technical performance .....                                                                                             | 109        |
+| 6.1             | Reliability .....                                                                                                                                | 109        |
+| 6.1.1           | NR.....                                                                                                                                          | 109        |
+| 6.1.1.1         | DL reliability.....                                                                                                                              | 109        |
+| 6.1.1.2         | UL reliability.....                                                                                                                              | 111        |
+| 6.2             | Latency.....                                                                                                                                     | 115        |
+| 6.2.1           | User plane latency .....                                                                                                                         | 115        |
+| 6.2.1.1         | NR.....                                                                                                                                          | 115        |
+| 6.2.1.2         | LTE .....                                                                                                                                        | 115        |
+| 6.2.2           | Control plane latency.....                                                                                                                       | 115        |
+| 6.3             | Mobility interruption time .....                                                                                                                 | 115        |
+| 7               | Self evaluation of mMTC technical performance.....                                                                                               | 116        |
+| 7.1             | Connection density.....                                                                                                                          | 116        |
+| 7.1.1           | NR.....                                                                                                                                          | 116        |
+| 7.1.2           | LTE.....                                                                                                                                         | 117        |
+| 8               | Self evaluation of generic requirements.....                                                                                                     | 119        |
+| 8.1             | Bandwidth and scalability .....                                                                                                                  | 119        |
+| 8.1.1           | NR.....                                                                                                                                          | 119        |
+| 8.1.2           | LTE.....                                                                                                                                         | 120        |
+| 8.2             | Spectrum.....                                                                                                                                    | 120        |
+| 8.2.1           | NR.....                                                                                                                                          | 121        |
+| 8.2.2           | LTE.....                                                                                                                                         | 121        |
+| 8.3             | Service.....                                                                                                                                     | 124        |
+| 9               | Conclusion .....                                                                                                                                 | 125        |
+| <b>Annex A:</b> | <b>Calibration for self evaluation.....</b>                                                                                                      | <b>126</b> |
+| <b>Annex B:</b> | <b>Simulation models and assumptions.....</b>                                                                                                    | <b>129</b> |
+| B.1             | Calculation of pre-processing SINR .....                                                                                                         | 129        |
+| B.2             | Link level assumption for mobility evaluation .....                                                                                              | 131        |
+| B.2.1           | Scaling factor for link level channel model .....                                                                                                | 131        |
+| B.2.2           | TXRU pattern and inter-port spacing in link level simulation.....                                                                                | 134        |
+| B.3             | Evaluation assumption for peak spectral efficiency and peak data rate .....                                                                      | 135        |
+| B.3.1           | Evaluation assumption for NR .....                                                                                                               | 135        |
+| B.3.1.1         | NR downlink .....                                                                                                                                | 135        |
+| B.3.1.2         | NR uplink .....                                                                                                                                  | 136        |
+| B.3.2           | Evaluation assumption for LTE .....                                                                                                              | 137        |
+| B.3.2.1         | LTE downlink.....                                                                                                                                | 137        |
+| B.3.2.2         | LTE uplink.....                                                                                                                                  | 138        |
+| B.4             | Detailed assumptions and evaluation results for simulation related technical performance requirements.....                                       | 139        |
+| B.4.1           | Detailed assumptions and results for average and 5 <sup>th</sup> percentile user spectral efficiency.....                                        | 139        |
+| B.4.2           | Detailed assumptions and results for mobility .....                                                                                              | 139        |
+| B.4.3           | Detailed assumptions and results for user experienced data rate .....                                                                            | 139        |
+| B.4.4           | Detailed assumptions and results for reliability .....                                                                                           | 139        |
+| B.4.5           | Detailed assumptions and results for connection density.....                                                                                     | 139        |
+| B.5             | Simulation results of spectral efficiency for Configuration B in Dense Urban – eMBB with modified ITU-R assumptions (for information only) ..... | 140        |
+| B.6             | Simulation results of Configuration C for Indoor Hotspot – eMBB test environment (for information only) .....                                    | 142        |
+| B.6.1           | Evaluation configuration C (CF = 70 GHz) for spectral efficiency .....                                                                           | 142        |
+| B.6.2           | Evaluation configuration C (CF = 70 GHz) for area traffic capacity.....                                                                          | 143        |
+
+|                                                                                      |            |
+|--------------------------------------------------------------------------------------|------------|
+| <b>Annex C: ITU-R Submission Templates for IMT-2020 .....</b>                        | <b>145</b> |
+| C.1 Description template – characteristics .....                                     | 145        |
+| C.2 Description template – link budget .....                                         | 145        |
+| C.3 Compliance templates for services, for spectrum, for technical performance ..... | 145        |
+| <b>Annex D: Change history .....</b>                                                 | <b>146</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+This report presents the self evaluation results of 3GPP 5G SRIT and 5G NR RIT.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 38.101-1: "User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+- [3] 3GPP TS 38.101-2: "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone".
+- [4] Report ITU-R M.2410: "Minimum requirements related to technical performance for IMT-2020 radio interface(s)".
+- [5] Report ITU-R M.2411: "Requirements, evaluation criteria and submission templates for the development of IMT-2020".
+- [6] Report ITU-R M.2412: "Guidelines for evaluation of radio interface technologies for IMT-2020".
+- [7] 3GPP TS 38.211: "Physical channels and modulation".
+- [8] 3GPP TR 38.817-01: "General aspects for User Equipment (UE) Radio Frequency (RF) for NR".
+- [9] 3GPP TS 38.214: "Physical layer procedures for data".
+- [10] 3GPP TS 38.306: "User Equipment (UE) radio access capabilities".
+- [11] 3GPP TS 36.211: "Physical channels and modulation".
+- [12] 3GPP TS 38.133: "Requirements for support of radio resource management".
+- [13] 3GPP TS 36.133: "Requirements for support of radio resource management".
+- [14] 3GPP TS 36.300: "Overall description; Stage 2".
+- [15] 3GPP TS 38.104: "Base Station (BS) radio transmission and reception".
+- [16] 3GPP TS 38.331: "Radio Resource Control (RRC) protocol specification".
+- [17] 3GPP TS 36.101: "User Equipment (UE) radio transmission and reception".
+- [18] 3GPP TS 36.331: "Radio Resource Control (RRC); Protocol specification".
+- [19] 3GPP TR 36.873: "Study on 3D channel model for LTE".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                                |                                                                                              |
+|--------------------------------|----------------------------------------------------------------------------------------------|
+| $SE_{pj}$                      | Peak spectral efficiency for $j$ -th component carrier (CC); see clause 5.1.1                |
+| $v_{Layers}^{(j)}$             | Maximum number of layers for $j$ -th CC; see clause 5.1.1                                    |
+| $Q_m^{(j)}$                    | Maximum modulation order for $j$ -th CC; see clause 5.1.1                                    |
+| $f^{(j)}$                      | Scaling factor for $j$ -th CC; see clause 5.1.1                                              |
+| $\mu$                          | Numerology as defined in TS 38.211                                                           |
+| $T_s^\mu$                      | Average OFDM symbol duration in a subframe for numerology; see clause 5.1.1                  |
+| $N_{PRB}^{BW(j),\mu}$          | Maximum RB allocation in bandwidth $BW^{(j)}$ with numerology $\mu$ ; see clause 5.1.1       |
+| $OH^{(j)}$                     | Overhead calculated as the average ratio of the number of REs not used for data transmission |
+| $\alpha^{(j)}$                 | Normalized scalar of downlink/uplink ratio                                                   |
+| $R$                            | Peak data rate; see clause 5.2                                                               |
+| $W_j$                          | Effective bandwidth; see clause 5.2                                                          |
+| $P_{SSB}$                      | SSB set periodicity; see clause 5.8.1                                                        |
+| $P_{RMSI}$                     | RMSI periodicity; see clause 5.8.1                                                           |
+| $Sleep\_ratio_{Slot\_based}$   | Sleep ratio per slot basis; see clause 5.8.1                                                 |
+| $Sleep\_ratio_{Symbol\_based}$ | Sleep ratio per symbol basis; see clause 5.8.1                                               |
+| $N_{PC\_RF}$                   | The paging frame and subframe with the period of $N_{PC\_RF}$ radio frame; see clause 5.8.2  |
+| $SINR_{pre-proc}$              | Pre-processing SINR; see clause B.1                                                          |
+| $RSRP_p$                       | Reference signal receiving power; see clause B.1                                             |
+| PL                             | The value of pathloss                                                                        |
+| SF                             | The value of shadow fading                                                                   |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
+
+|        |                                                        |
+|--------|--------------------------------------------------------|
+| CF     | Carrier frequency                                      |
+| CSI-RS | CSI reference signal                                   |
+| DC     | Dual connectivity                                      |
+| DM-RS  | Demodulation reference signal                          |
+| DL     | Downlink                                               |
+| eMBB   | Enhanced mobile broadband                              |
+| eMTC   | Enhanced machine type communication                    |
+| FDD    | Frequency division duplexing                           |
+| FeMBMS | Further evolved multimedia broadcast multicast service |
+| FR1    | Frequency range 1                                      |
+| FR2    | Frequency range 2                                      |
+| ISD    | Inter-site distance                                    |
+| LMLC   | Low mobility large cell                                |
+| LOS    | Line of sight                                          |
+| MeNB   | Master E-UTRAN NodeB                                   |
+| MIMO   | Multiple input multiple output                         |
+| mMTC   | Massive machine type communication                     |
+| MU     | Multiple user                                          |
+
+|        |                                              |
+|--------|----------------------------------------------|
+| NB-IoT | Narrow band internet of things               |
+| NLOS   | Non line of sight                            |
+| OH     | Overhead                                     |
+| OS     | OFDM symbol                                  |
+| PSCell | Primary secondary cell                       |
+| PSS    | Primary synchronization signal               |
+| PT-RS  | Phase-tracking reference signal              |
+| RIT    | Radio interface technology                   |
+| RMa    | Rural macro                                  |
+| RMSI   | Remaining minimum system information         |
+| RTT    | Round-trip time                              |
+| SCS    | Subcarrier spacing                           |
+| SeNB   | Secondary E-UTRAN NodeB                      |
+| SIMO   | Single input multiple output                 |
+| SISO   | Single input single output                   |
+| SRI    | SRS resource indicator                       |
+| SRIT   | Set of RITs                                  |
+| SRS    | Sounding reference signal                    |
+| SS     | Synchronization signal                       |
+| SSB    | SS/PBCH Block                                |
+| SSS    | Secondary synchronization signal             |
+| SU     | Single user                                  |
+| TDD    | Time division duplexing                      |
+| TRxP   | Transmission reception point                 |
+| UL     | Uplink                                       |
+| UMa    | Urban macro                                  |
+| URLLC  | Ultra reliable and low latency communication |
+
+# --- 4 Introduction
+
+This report presents the self evaluation results of 5G<sup>1</sup> developed by 3GPP, which includes two submissions:
+
+- Submission 1: SRIT. It consists of two component RITs
+  - Component RIT 1: NR
+  - Component RIT 2: E-UTRA/LTE (including LTE-NR DC)
+- Submission 2: NR RIT.
+  - It is the same as in NR component RIT in submission 1.
+
+From evaluation perspective, NR RIT and LTE RIT are evaluated against the technical performance requirements as defined in Report ITU-R M.2410 for eMBB, mMTC and URLLC usage scenarios, as well as spectrum requirements and service requirements as defined in Report ITU-R M.2411, using the evaluation criteria as defined by Report ITU-R M.2412. Detailed self evaluation results are provided through Section 5 to 8.
+
+The conclusion is given in Section 9 for SRIT and NR RIT.
+
+# --- 5 Self evaluation of eMBB technical performance
+
+In the following, frequency ranges indicated by FR1 and FR2 are evaluated. The definition are given in Table 5-1 (see also [2] and [3]).
+
+---
+
+<sup>1</sup> Developed by 3GPP as 5G, Release 15 and beyond.
+
+**Table 5-1 Definition of frequency ranges**
+
+| Frequency range designation | Corresponding frequency range |
+|-----------------------------|-------------------------------|
+| FR1                         | 410 MHz – 7125 MHz            |
+| FR2                         | 24250 MHz – 52600 MHz         |
+
+## 5.1 Peak spectral efficiency
+
+As defined in Report ITU-R M.2410 [4], Peak spectral efficiency is the maximum data rate under ideal conditions normalized by channel bandwidth (in bit/s/Hz), where the maximum data rate is the received data bits assuming error-free conditions assignable to a single mobile station, when all assignable radio resources for the corresponding link direction are utilized (i.e. excluding radio resources that are used for physical layer synchronization, reference signals or pilots, guard bands and guard times).
+
+### 5.1.1 NR
+
+The generic formula for peak spectral efficiency for FDD and TDD for a specific component carrier (say  $j$ -th CC) is given by
+
+$$SE_{p_j} = \frac{v_{Layers}^{(j)} \cdot Q_m^{(j)} \cdot f^{(j)} \cdot R_{max} \cdot \frac{N_{PRB}^{BW(j),\mu} \cdot 12}{T_s^\mu} \cdot (1 - OH^{(j)})}{BW^{(j)}} \quad (5.1.1-1)$$
+
+wherein
+
+- $R_{max} = 948/1024$
+- For the  $j$ -th CC,
+  - $v_{Layers}^{(j)}$  is the maximum number of layers
+  - $Q_m^{(j)}$  is the maximum modulation order
+  - $f^{(j)}$  is the scaling factor
+    - The scaling factor can at least take the values 1 and 0.75.
+    - $f^{(j)}$  is signalled per band and per band per band combination as per UE capability signalling
+  - $\mu$  is the numerology (as defined in TS 38.211 [7])
+  - $T_s^\mu$  is the average OFDM symbol duration in a subframe for numerology  $\mu$ , i.e.  $T_s^\mu = \frac{10^{-3}}{14 \cdot 2^\mu}$ . Note that normal cyclic prefix is assumed.
+  - $N_{PRB}^{BW(j),\mu}$  is the maximum RB allocation in bandwidth  $BW^{(j)}$  with numerology  $\mu$ , as given in TR 38.817-01 [8] section 4.5.1, where  $BW^{(j)}$  is the UE supported maximum bandwidth in the given band or band combination.
+  - $OH^{(j)}$  is the overhead calculated as the average ratio of the number of REs occupied by L1/L2 control, Synchronization Signal, PBCH, reference signals and guard period (for TDD), etc. with respect to the total number of REs in effective bandwidth time product as given by  $(\alpha^{(j)} \cdot BW^{(j)} \cdot (14 \times T_s^\mu))$ .
+    - $\alpha^{(j)}$  is the normalized scalar considering the downlink/uplink ratio; for FDD  $\alpha^{(j)}=1$  for DL and UL; and for TDD and other duplexing  $\alpha^{(j)}$  for DL and UL is calculated based on the DL/UL configuration.
+    - For guard period (GP), 50% of GP symbols are considered as downlink overhead, and 50% of GP symbols are considered as uplink overhead.
+
+#### 5.1.1.1 DL peak spectral efficiency
+
+A range of configurations are considered in the evaluation of downlink peak spectral efficiency. The evaluation considers the maximum potential capability as indicated in TS 38.214 [9]. Note that the DL and UL max data rate supported by the UE is indicated in TS38.306 [10].
+
+For NR FDD, DL peak spectral efficiency of frequency range 1 (FR1) for 450 MHz – 7125 MHz is evaluated. The evaluated configurations for FDD generally assume 8-layer downlink transmission, with 256QAM modulation, and a maximum coding rate of 0.9258. The difference among the evaluated configurations lays in the overhead of control and reference signals, etc. The evaluation results are provided in Table 5.1.1.1-1. The detailed assumptions are provided in Annex B.3.1.1.
+
+**Table 5.1.1.1-1 NR FDD DL peak spectral efficiency (bit/s/Hz)**
+
+| SCS [kHz] |    | 5 MHz         | 10 MHz        | 15 MHz        | 20 MHz        | 25 MHz        | 30 MHz        | 40 MHz        | 50 MHz        | 60 MHz        | 80 MHz        | 90 MHz        | 100 MHz       | Req. |
+|-----------|----|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|------|
+| FR1       | 15 | 40.8~<br>42.8 | 44.5~<br>45.5 | 45.1~<br>46.5 | 45.4~<br>47.0 | 45.5~<br>47.2 | 45.7~<br>47.4 | 46.2~<br>48.2 | 46.2~<br>48.3 | -             | -             | -             | -             | 30   |
+|           | 30 | 32.1~<br>37.7 | 39.4~<br>41.1 | 43.0~<br>44.2 | 43.7~<br>44.8 | 44.5~<br>45.9 | 44.5~<br>46.1 | 45.4~<br>47.1 | 45.5~<br>47.4 | 46.2~<br>48.2 | 46.4~<br>48.5 | 48.5~<br>48.7 | 46.7~<br>48.9 | 30   |
+|           | 60 | -             | 32.4~<br>37.7 | 38.4~<br>41.1 | 39.6~<br>41.3 | 41.8~<br>43.1 | 43.2~<br>44.3 | 43.7~<br>44.9 | 44.5~<br>46.0 | 45.1~<br>46.8 | 45.8~<br>47.7 | 47.6~<br>47.8 | 46.2~<br>48.2 | 30   |
+
+For NR TDD, DL peak spectral efficiency for both FR1 and FR2 for 24.25 GHz – 52.6 GHz are evaluated.
+
+For NR TDD in FR1, the evaluated configurations generally assume 8-layer downlink transmission, with 256QAM modulation, and a maximum coding rate of 0.9258. The DL/UL configurations of DDDSU (with ‘S’ slot = 11DL:1GP:2UL) and DSUUD (with ‘S’ slot = 6DL:2GP:6UL and 11DL:1GP:2UL respectively) are evaluated.
+
+The evaluation results of DDDSU for FR1 are provided in Table 5.1.1.1-2. In the evaluation, different control overhead assumptions are considered due to the different transmission schemes. The detailed assumptions are provided in Annex B.3.1.1.
+
+**Table 5.1.1.1-2 NR TDD DL peak spectral efficiency for FR1 (bit/s/Hz)  
+(Frame structure: DDDSU;  $\alpha_{DL}=0.7643$ ; with OH1 and OH2)**
+
+| SCS [kHz] |    | 5 MHz         | 10 MHz        | 15 MHz        | 20 MHz        | 25 MHz        | 30 MHz        | 40 MHz        | 50 MHz        | 60 MHz        | 80 MHz        | 90 MHz        | 100 MHz       | Req. |
+|-----------|----|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|------|
+| FR1       | 15 | 39.6~<br>41.5 | 43.6~<br>44.5 | 44.9~<br>45.6 | 45.6~<br>46.1 | 46.1~<br>46.4 | 46.3~<br>46.6 | 47.1~<br>47.3 | 47.2~<br>47.4 | -             | -             | -             | -             | 30   |
+|           | 30 | 31.7~<br>35.2 | 38.4~<br>40.3 | 42.1~<br>43.3 | 43.1~<br>44.0 | 44.4~<br>45.1 | 44.6~<br>45.3 | 45.9~<br>46.3 | 46.3~<br>46.6 | 47.1~<br>47.4 | 47.5~<br>47.7 | 47.7~<br>47.9 | 47.9~<br>48.1 | 30   |
+|           | 60 | -             | 31.8~<br>35.3 | 37.5~<br>40.1 | 38.7~<br>40.5 | 40.9~<br>42.3 | 42.3~<br>43.5 | 43.3~<br>44.2 | 44.5~<br>45.3 | 45.4~<br>46.0 | 46.4~<br>46.9 | 46.8~<br>47.2 | 47.1~<br>47.4 | 30   |
+
+The evaluation results of DSUUD for the two S-slot configurations for FR1 are provided in Table 5.1.1.1-3. The detailed assumptions are provided in Annex B.3.1.1.
+
+**Table 5.1.1.1-3 NR TDD DL peak spectral efficiency for FR1 (bit/s/Hz)  
+(Frame structure: DSUUD)**
+
+**(a) S slot = 11DL:1GP:2UL,  $\alpha_{DL}=0.5643$ , with OH3**
+
+| SCS [kHz] |    | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | Req. |
+|-----------|----|-------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------|
+| FR1       | 15 | 39.1  | 43.1   | 44.5   | 45.2   | 45.6   | 45.9   | 46.7   | 46.8   | -      | -      | -      | -       | 30   |
+|           | 30 | 30.4  | 38.0   | 41.7   | 42.7   | 44.0   | 44.3   | 45.5   | 45.9   | 46.8   | 47.1   | 47.4   | 47.6    | 30   |
+|           | 60 | -     | 31.0   | 37.1   | 38.4   | 40.6   | 42.0   | 42.9   | 44.2   | 45.1   | 46.1   | 46.5   | 46.8    | 30   |
+
+**(b) S slot = 6DL:2GP:6UL,  $\alpha_{DL}=0.5$ , with OH4**
+
+| SCS [kHz] |    | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | Req. |
+|-----------|----|-------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------|
+| FR1       | 15 | 39.1  | 42.4   | 43.5   | 44.0   | 44.4   | 44.6   | 45.3   | 45.4   | -      | -      | -      | -       | 30   |
+|           | 30 | 33.1  | 37.4   | 40.7   | 41.6   | 42.7   | 42.9   | 44.0   | 44.4   | 45.2   | 45.5   | 45.7   | 45.9    | 30   |
+|           | 60 | -     | 33.1   | 36.4   | 37.4   | 39.4   | 40.7   | 41.6   | 42.7   | 43.5   | 44.5   | 44.8   | 45.1    | 30   |
+
+For NR TDD in FR2, the DL/UL configurations of DDDSU (with 'S' slot = 11DL:1GP:2UL) and DSUUD (with 'S' slot = 6DL:2GP:6UL and 11DL:1GP:2UL respectively) are evaluated. For FR2 evaluation, the number of layers is assumed to be 6. This is because larger than 6-port DMRS is difficult due to the phase noise impact on FR2. Besides, the highest modulation order of 256QAM and the maximum coding rate of 0.9258 are assumed.
+
+The evaluation results of DDDSU and DSUUD for FR2 are provided in Table 5.1.1.1-4 and Table 5.1.1.1-5, respectively. The detailed assumptions are provided in Annex B.3.1.1.
+
+**Table 5.1.1.1-4 NR TDD DL peak spectral efficiency for FR2 (bit/s/Hz)**  
+**(Frame structure: DDDSU,  $\alpha_{DL}=0.7643$ , Number of layer = 6)**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 33.7   | 34.5    | 34.9    | -       | 30   |
+|           | 120 | 31.7   | 34.0    | 34.7    | 35.0    | 30   |
+
+**Table 5.1.1.1-5 NR TDD DL peak spectral efficiency for FR2 (bit/s/Hz)**  
+**(Frame structure: DSUUD, S slot = 11DL:1GP:2UL,  $\alpha_{DL}=0.5643$ , Number of layer = 6)**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 32.9   | 33.8    | 34.2    | -       | 30   |
+|           | 120 | 31.1   | 33.5    | 34.2    | 34.6    | 30   |
+
+If phase noise does not exist for FR2, the 8- layer transmission can be supported for FR2. The evaluation of this capability together with DSUUD is provided in Table 5.1.1.1-6.
+
+**Table 5.1.1.1-6 NR TDD DL peak spectral efficiency for FR2 (bit/s/Hz)**  
+**(Frame structure: DSUUD, S slot = 6DL:2GP:6UL,  $\alpha_{DL}=0.5$ , Number of layer = 8)**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 41.9   | 43.2    | 43.8    | -       | 30   |
+|           | 120 | 38.0   | 41.9    | 43.2    | 43.8    | 30   |
+
+Based on the above analysis, NR fulfils DL peak spectral efficiency requirement with a range of configurations.
+
+#### 5.1.1.2 UL peak spectral efficiency
+
+A range of configurations are considered in the evaluation of uplink peak spectral efficiency.
+
+For NR FDD, UL peak spectral efficiency of FR1 is evaluated. The evaluated configurations for FDD generally assume 4-layer downlink transmission, with 256QAM modulation, and a maximum coding rate of 0.9258. The difference among the evaluated configurations lays in the overhead of control and reference signals, etc. The evaluation results are provided in Table 5.1.1.2-1. The detailed assumptions are provided in Annex B.3.1.2.
+
+**Table 5.1.1.2-1 NR FDD UL peak spectral efficiency (bit/s/Hz)**
+
+| SCS [kHz] |    | 5 MHz         | 10 MHz        | 15 MHz        | 20 MHz        | 25 MHz        | 30 MHz        | 40 MHz        | 50 MHz        | 60 MHz        | 80 MHz        | 90 MHz        | 100 MHz       | Req. |
+|-----------|----|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|------|
+| FR1       | 15 | 22.9~<br>23.5 | 23.8~<br>24.5 | 24.1~<br>24.8 | 24.3~<br>25.0 | 24.4~<br>25.1 | 24.4~<br>25.2 | 24.7~<br>25.5 | 24.7~<br>25.5 | 0.0           | 0.0           | 0.0           | 0.0           | 15   |
+|           | 30 | 20.1~<br>20.7 | 22.0~<br>22.6 | 23.2~<br>23.9 | 23.4~<br>24.1 | 23.8~<br>24.6 | 23.8~<br>24.6 | 24.3~<br>25.1 | 24.4~<br>25.2 | 24.7~<br>25.5 | 24.8~<br>25.7 | 24.9~<br>25.3 | 25.0~<br>25.8 | 15   |
+|           | 60 | 0.0           | 20.1~<br>20.7 | 22.0~<br>22.6 | 22.0~<br>22.7 | 22.7~<br>23.4 | 23.2~<br>23.9 | 23.4~<br>24.1 | 23.8~<br>24.6 | 24.1~<br>24.9 | 24.5~<br>25.3 | 24.9~<br>25.0 | 24.7~<br>25.6 | 15   |
+
+For NR TDD, UL peak spectral efficiency for both FR1 and FR2 are evaluated.
+
+For NR TDD in FR1, the evaluated configurations generally assume 4-layer uplink transmission, with 256QAM modulation, and a maximum coding rate of 0.9258. The DL/UL configurations of DDDSU (with 'S' slot = 11DL:1GP:2UL) and DSUUD (with 'S' slot = 6DL:2GP:6UL and 11DL:1GP:2UL respectively) are evaluated.
+
+The evaluation results of DDDSU for FR1 are provided in Table 5.1.1.2-2. In the evaluation, different control overhead assumptions are considered due to the different transmission schemes. The detailed assumptions are provided in Annex B.3.1.2.
+
+**Table 5.1.1.2-2 NR TDD UL peak spectral efficiency for FR1 (bit/s/Hz)**  
+**(Frame structure: DDDSU,  $\alpha_{UL}=0.2357$ , with OH1 and OH2)**
+
+| SCS [kHz] |    | 5 MHz         | 10 MHz        | 15 MHz        | 20 MHz        | 25 MHz        | 30 MHz        | 40 MHz        | 50 MHz        | 60 MHz        | 80 MHz        | 90 MHz        | 100 MHz       | Req. |
+|-----------|----|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|---------------|------|
+| FR1       | 15 | 20.6~<br>21.6 | 21.5~<br>22.6 | 21.8~<br>22.9 | 22.0~<br>23.0 | 22.0~<br>23.1 | 22.1~<br>23.2 | 22.4~<br>23.5 | 22.4~<br>23.5 | -             | -             | -             | -             | 15   |
+|           | 30 | 18.2~<br>19.1 | 20.0~<br>20.9 | 21.1~<br>22.1 | 21.3~<br>22.3 | 21.7~<br>22.8 | 21.7~<br>22.8 | 22.2~<br>23.2 | 22.2~<br>23.2 | 22.6~<br>23.7 | 22.7~<br>23.8 | 22.8~<br>23.9 | 22.8~<br>23.9 | 15   |
+|           | 60 | -             | 18.3~<br>19.1 | 20.0~<br>21.0 | 20.1~<br>21.0 | 20.8~<br>21.8 | 21.2~<br>22.2 | 21.4~<br>22.4 | 21.8~<br>22.9 | 22.1~<br>23.2 | 22.5~<br>23.5 | 22.6~<br>23.7 | 22.7~<br>23.8 | 15   |
+
+The evaluation results of DSUUD for the two S-slot configurations for FR1 are provided in Table 5.1.1.2-3. The detailed assumptions for the two configurations are provided in Annex B.3.1.2.
+
+**Table 5.1.1.2-3 NR TDD UL peak spectral efficiency for FR1 (bit/s/Hz)**  
+**(Frame structure: DSUUD)**
+
+**(a) S slot = 11DL:1GP:2UL,  $\alpha_{UL}=0.4357$ , with OH3**
+
+| SCS [kHz] |    | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | Req. |
+|-----------|----|-------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------|
+| FR1       | 15 | 22.1  | 23.1   | 23.4   | 23.6   | 23.7   | 23.8   | 24.0   | 24.0   | -      | -      | -      | -       | 15   |
+|           | 30 | 19.4  | 21.3   | 22.5   | 22.7   | 23.1   | 23.1   | 23.6   | 23.7   | 24.1   | 24.2   | 24.3   | 24.3    | 15   |
+|           | 60 | -     | 19.4   | 21.3   | 21.3   | 22.0   | 22.5   | 22.7   | 23.2   | 23.4   | 23.8   | 24.0   | 24.0    | 15   |
+
+**(b) S slot = 6DL:2GP:6UL,  $\alpha_{UL}=0.5$ , with OH4**
+
+| SCS [kHz] |    | 5 MHz | 10 MHz | 15 MHz | 20 MHz | 25 MHz | 30 MHz | 40 MHz | 50 MHz | 60 MHz | 80 MHz | 90 MHz | 100 MHz | Req. |
+|-----------|----|-------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------|------|
+| FR1       | 15 | 21.7  | 23.0   | 23.4   | 23.6   | 23.7   | 23.8   | 24.1   | 24.1   | -      | -      | -      | -       | 15   |
+|           | 30 | 18.3  | 20.8   | 22.2   | 22.5   | 23.0   | 23.1   | 23.6   | 23.7   | 24.2   | 24.3   | 24.4   | 24.2    | 15   |
+|           | 60 | -     | 18.3   | 20.6   | 20.8   | 21.7   | 22.2   | 22.5   | 23.0   | 23.8   | 23.9   | 24.1   | 23.8    | 15   |
+
+For NR TDD in FR2, the evaluated configurations generally assume 4-layer uplink transmission, with 256QAM modulation, and a maximum coding rate of 0.9258. The DL/UL configurations of DDDSU (with ‘S’ slot = 11DL:1GP:2UL) and DSUUD (with ‘S’ slot = 6DL:2GP:6UL and 11DL:1GP:2UL respectively) are evaluated.
+
+The evaluation results of DDDSU and DSUUD for FR2 are provided in Table 5.1.1.2-4 and Table 5.1.1.2-5, respectively. The detailed assumptions are provided in Annex B.3.1.2.
+
+**Table 5.1.1.2-4 NR TDD UL peak spectral efficiency for FR2 (bit/s/Hz)**  
+**(Frame structure: DDDSU,  $\alpha_{UL}=0.2357$ )**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 20.9   | 21.0    | 21.0    | -       | 15   |
+|           | 120 | 20.4   | 21.1    | 21.2    | 21.2    | 15   |
+
+**Table 5.1.1.2-5 NR TDD UL peak spectral efficiency for FR2 (bit/s/Hz)**  
+**(Frame structure: DSUUD)**
+
+**(a) S slot = 11DL:1GP:2UL,  $\alpha_{UL}=0.4357$**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 21.8   | 21.9    | 21.9    | -       | 15   |
+|           | 120 | 21.3   | 22.0    | 22.1    | 22.1    | 15   |
+
+**(b) S slot = 6DL:2GP:6UL,  $\alpha_{UL}=0.5$**
+
+| SCS [kHz] |     | 50 MHz | 100 MHz | 200 MHz | 400 MHz | Req. |
+|-----------|-----|--------|---------|---------|---------|------|
+| FR2       | 60  | 23.0   | 23.1    | 23.2    | -       | 15   |
+|           | 120 | 22.0   | 23.0    | 23.1    | 23.2    | 15   |
+
+Based on the above analysis, NR fulfils UL peak spectral efficiency requirement with a range of configurations.
+
+### 5.1.2 LTE
+
+For LTE, the similar calculation way to NR is used to analyze the spectrum efficiency.
+
+#### 5.1.2.1 DL peak spectral efficiency
+
+For LTE FDD, the evaluation assumes 8-layer downlink transmission, with 256QAM and 1024QAM modulation, and a maximum coding rate of 0.93. The evaluation results for FDD are provided in Table 5.1.2.1-1. Note that the peak spectrum efficiency of LTE is evaluated by selecting the largest TBS as defined in TS 36.211 [11] matching the supportable coding rate as high as possible and the overhead with the assumed composition of MBSFN and non-MBSFN subframes. The detailed assumptions are provided in Annex B.3.2.1.
+
+**Table 5.1.2.1-1 LTE FDD DL peak spectral efficiency (bit/s/Hz)**
+
+| Modulation order |         | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|---------|-------|--------|--------|--------|------|
+| FR1              | 256QAM  | 37.56 | 37.55  | 36.72  | 37.55  | 30   |
+|                  | 1024QAM | 46.38 | 45.96  | 47.15  | 47.11  | 30   |
+
+For LTE TDD, the DL/UL configurations of DSUDD (with Special subframe = 11DL:1GP:2UL) and DSUUD (with Special subframe 11DL:1GP:2UL) are evaluated. The evaluation assumes 8-layer downlink transmission, with 256QAM and 1024QAM modulation, and a maximum coding rate of 0.93. The evaluation results are provided in Table 5.1.2.1-2 and Table 5.1.2.1-3, respectively.
+
+**Table 5.1.2.1-2 LTE TDD DL peak spectral efficiency (bit/s/Hz)**  
+**(Frame structure: DSUDD, Special subframe = 11DL:1GP:2UL,  $\alpha_{DL}=0.7643$ )**
+
+| Modulation order |         | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|---------|-------|--------|--------|--------|------|
+| FR1              | 256QAM  | 36.28 | 36.52  | 36.51  | 36.69  | 30   |
+|                  | 1024QAM | 45.82 | 46.27  | 46.79  | 46.91  | 30   |
+
+**Table 5.1.2.1-3 LTE TDD DL peak spectral efficiency (bit/s/Hz)**  
+**(Frame structure: DSUUD, Special subframe = 11DL:1GP:2UL,  $\alpha_{DL}=0.5643$ )**
+
+| Modulation order |         | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|---------|-------|--------|--------|--------|------|
+| FR1              | 256QAM  | 35.85 | 36.16  | 36.44  | 36.38  | 30   |
+|                  | 1024QAM | 45.07 | 45.93  | 46.21  | 46.57  |      |
+
+Based on the above analysis, LTE fulfils DL peak spectral efficiency requirement.
+
+#### 5.1.2.2 UL peak spectral efficiency
+
+For LTE FDD, the evaluation assumes 4-layer uplink transmission, with 256QAM modulation, and a maximum coding rate of 0.93. The evaluation results for FDD are provided in Table 5.1.2.2-1. The detailed assumptions are provided in Annex B.3.2.2.
+
+**Table 5.1.2.2-1 LTE FDD UL peak spectral efficiency (bit/s/Hz)**
+
+| Modulation order |        | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|--------|-------|--------|--------|--------|------|
+| FR1              | 256QAM | 19.31 | 20.21  | 20.25  | 20.15  | 15   |
+
+For LTE TDD, the DL/UL configurations of DSUDD (with Special subframe = 11DL:1GP:2UL) and DSUUD (with Special subframe 11DL:1GP:2UL) are evaluated. The evaluation assumes 4-layer downlink transmission, with 256QAM modulation, and a maximum coding rate of 0.93. The evaluation results are provided in Table 5.1.2.2-2 and Table 5.1.2.2-3, respectively.
+
+**Table 5.1.2.2-2 LTE TDD UL peak spectral efficiency (bit/s/Hz)**  
+**(Frame structure: DSUDD, Special subframe = 11DL:1GP:2UL,  $\alpha_{UL}=0.2357$ )**
+
+| Modulation order |        | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|--------|-------|--------|--------|--------|------|
+| FR1              | 256QAM | 16.61 | 17.28  | 17.31  | 17.28  | 15   |
+
+**Table 5.1.2.2-3 LTE TDD UL peak spectral efficiency (bit/s/Hz)**  
+**(Frame structure: DSUUD, Special subframe = 11DL:1GP:2UL,  $\alpha_{UL}=0.4357$ )**
+
+| Modulation order |        | 5 MHz | 10 MHz | 15 MHz | 20 MHz | Req. |
+|------------------|--------|-------|--------|--------|--------|------|
+| FR1              | 256QAM | 17.97 | 18.7   | 18.72  | 18.7   | 15   |
+
+Based on the above analysis, LTE fulfils UL peak spectral efficiency requirement.
+
+## 5.2 Peak data rate
+
+As defined in Report ITU-R M.2410 [4], peak data rate is the maximum achievable data rate under ideal conditions (in bit/s), which is the received data bits assuming error-free conditions assignable to a single mobile station, when all assignable radio resources for the corresponding link direction are utilized (i.e. excluding radio resources that are used for physical layer synchronization, reference signals or pilots, guard bands and guard times).
+
+For both NR and LTE, the DL/UL peak data rate for FDD and TDD over  $Q$  component carriers can be calculated as below
+
+$$R = \sum_{j=1}^Q W_j \times SE_{p_j} = \sum_{j=1}^Q \left( \alpha^{(j)} \cdot BW^{(j)} \right) \times SE_{p_j} \quad (5.2-1)$$
+
+where  $W_j$  and  $SE_{p_j}$  ( $j = 1, \dots, Q$ ) are the effective bandwidth and spectral efficiencies on component carrier  $j$ , respectively,  $\alpha^{(j)}$  is the normalized scalar on component carrier  $j$  considering the downlink/uplink ratio on that component carrier; for FDD  $\alpha^{(j)}=1$  for DL and UL; and for TDD and other duplexing  $\alpha^{(j)}$  for DL and UL is calculated based on the frame structure, and  $BW^{(j)}$  is the carrier bandwidth of component  $j$ .
+
+### 5.2.1 NR
+
+#### 5.2.1.1 DL peak data rate
+
+A range of configurations are considered in the evaluation of downlink peak data rate.
+
+DL peak data rate for NR is evaluated based on the evaluation results of NR peak spectral efficiency provided in Section 5.1.1.1. Table 5.2.1.1-1 provides the evaluation results for the specific component carrier (CC) bandwidth. It is observed that NR fulfils the DL peak data rate requirement.
+
+**Table 5.2.1.1-1 NR DL peak data rate**
+
+| Duplexing                        | SCS [kHz]                | Per CC BW (MHz) | Peak data rate per CC (Gbit/s) | Aggregated peak data rate over 16 CCs (Gbit/s) | Required DL bandwidth to meet the requirement (MHz) <sup>1</sup> | Req. (Gbit/s) |
+|----------------------------------|--------------------------|-----------------|--------------------------------|------------------------------------------------|------------------------------------------------------------------|---------------|
+| FDD                              | FR1                      | 15              | 50                             | 2.31~2.41                                      | 37.0~38.6                                                        | 20            |
+|                                  |                          | 30              | 100                            | 4.67~4.89                                      | 74.7~78.2                                                        |               |
+|                                  |                          | 60              | 100                            | 4.62~4.82                                      | 73.9~77.1                                                        |               |
+| TDD (DDDSU)                      | FR1                      | 15              | 50                             | 1.81                                           | 29.0                                                             |               |
+|                                  |                          | 30              | 100                            | 3.68                                           | 58.9                                                             |               |
+|                                  |                          | 60              | 100                            | 3.62                                           | 57.9                                                             |               |
+|                                  | FR2<br>( $N_{layer}=6$ ) | 60              | 200                            | 5.33                                           | 85.3                                                             |               |
+|                                  |                          | 120             | 400                            | 10.7                                           | 171.2                                                            |               |
+| TDD (DSUUD, S slot=11DL:2GP:2UL) | FR1                      | 15              | 50                             | 1.32                                           | 21.1                                                             |               |
+|                                  |                          | 30              | 100                            | 2.69                                           | 43.0                                                             |               |
+|                                  |                          | 60              | 100                            | 2.64                                           | 42.3                                                             |               |
+|                                  | FR2<br>( $N_{layer}=6$ ) | 60              | 200                            | 3.86                                           | 61.8                                                             |               |
+|                                  |                          | 120             | 400                            | 7.81                                           | 125.0                                                            |               |
+| TDD (DSUUD, S slot=6DL:2GP:6UL)  | FR1                      | 15              | 50                             | 1.13                                           | 18.1                                                             |               |
+|                                  |                          | 30              | 100                            | 2.30                                           | 36.8                                                             |               |
+|                                  |                          | 60              | 100                            | 2.26                                           | 36.2                                                             |               |
+|                                  | FR2<br>( $N_{layer}=8$ ) | 60              | 200                            | 4.38                                           | 70.1                                                             |               |
+|                                  |                          | 120             | 400                            | 8.76                                           | 140.2                                                            |               |
+
+NOTE 1: The value only indicates the required bandwidth to meet the DL peak data rate. It is not necessarily supported as NR Transmission bandwidth.
+
+#### 5.2.1.2 UL peak data rate
+
+A range of configurations are considered in the evaluation of uplink peak data rate.
+
+UL peak data rate for NR is evaluated based on the evaluation results of NR peak spectral efficiency provided in Section 5.1.1.2. Table 5.2.1.2-1 provides the evaluation results for the specific component carrier (CC) bandwidth. It is observed that NR fulfils the UL peak data rate requirement.
+
+**Table 5.2.1.2-1 NR UL peak data rate**
+
+| Duplexing                        | SCS [kHz] | Per CC BW (MHz) | Peak data rate per CC (Gbit/s) | Aggregated peak data rate over 16 CCs (Gbit/s) | Required UL bandwidth to meet the requirement (MHz) <sup>1</sup> | Req. (Gbit/s) |
+|----------------------------------|-----------|-----------------|--------------------------------|------------------------------------------------|------------------------------------------------------------------|---------------|
+| FDD                              | FR1       | 15              | 50                             | 1.12~1.18                                      | 17.9~18.9                                                        | 10            |
+|                                  |           | 30              | 100                            | 2.28~2.39                                      | 36.5~38.2                                                        |               |
+|                                  |           | 60              | 100                            | 2.27~2.38                                      | 36.3~38.1                                                        |               |
+| TDD (DDDSU) + SUL                | FR1       | 15              | 50                             | 1.12~1.18                                      | 17.9~18.9                                                        |               |
+|                                  |           | 30              | 100                            | 2.28~2.39                                      | 36.5~38.2                                                        |               |
+|                                  |           | 60              | 100                            | 2.27~2.38                                      | 36.3~38.1                                                        |               |
+| TDD (DSUUD, S slot=11DL:2GP:2UL) | FR1       | 30              | 100                            | 1.06                                           | 17.0                                                             |               |
+|                                  |           | 60              | 100                            | 1.05                                           | 16.8                                                             |               |
+|                                  | FR2       | 60              | 200                            | 1.91                                           | 30.6                                                             |               |
+|                                  |           | 120             | 400                            | 3.85                                           | 61.6                                                             |               |
+| TDD (DSUUD, S slot=6DL:2GP:6UL)  | FR1       | 30              | 100                            | 1.05                                           | 16.8                                                             |               |
+|                                  |           | 60              | 100                            | 1.04                                           | 16.6                                                             |               |
+|                                  | FR2       | 60              | 200                            | 2.02                                           | 32.3                                                             |               |
+|                                  |           | 120             | 400                            | 4.04                                           | 64.6                                                             |               |
+
+NOTE 1: The value only indicates the required bandwidth to meet the DL peak data rate. It is not necessarily supported as NR Transmission bandwidth.
+
+### 5.2.2 LTE
+
+#### 5.2.2.1 DL peak data rate
+
+DL peak data rate for LTE is evaluated based on the evaluation results of LTE peak spectral efficiency provided in Section 5.1.2.1. Table 5.2.2.1-1 provides the evaluation results for 20 MHz CC bandwidth. It is observed that LTE fulfils the DL peak data rate requirement.
+
+**Table 5.2.2.1-1 LTE DL peak data rate**
+
+| Duplexing | Modulation order | Per CC BW (MHz) | Peak data rate per CC (Gbit/s) | Aggregated peak data rate over 32 CCs (Gbit/s) | Req. (Gbit/s) |
+|-----------|------------------|-----------------|--------------------------------|------------------------------------------------|---------------|
+| FDD       | 256QAM           | 20              | 0.751                          | 24.0                                           | 20            |
+| FDD       | 1024QAM          | 20              | 0.942                          | 30.1                                           |               |
+
+#### 5.2.2.2 UL peak data rate
+
+UL peak data rate for LTE is evaluated based on the evaluation results of LTE peak spectral efficiency provided in Section 5.1.2.2. Table 5.2.2.2-1 provides the evaluation results for 20 MHz CC bandwidth. It is observed that LTE fulfils the UL peak data rate requirement.
+
+**Table 5.2.2.2-1 LTE UL peak data rate**
+
+| Duplexing | Per CC BW (MHz) | Peak data rate per CC (Gbit/s) | Aggregated peak data rate over 32 CCs (Gbit/s) | Req. (Gbit/s) |
+|-----------|-----------------|--------------------------------|------------------------------------------------|---------------|
+| FDD       | 20              | 0.403                          | 12.9                                           | 10            |
+
+## 5.3 5<sup>th</sup> percentile user spectral efficiency
+
+As defined in Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency is the 5% point of the CDF of the normalized user throughput. The normalized user throughput is defined as the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time, divided by the channel bandwidth and is measured in bit/s/Hz.
+
+As required by Report ITU-R M.2412 [6], 5<sup>th</sup> percentile user spectral efficiency shall be assessed jointly with average spectral efficiency using the same simulation. Therefore, the evaluation results of the 5<sup>th</sup> percentile user spectral efficiency are provided together with average spectral efficiency in Section 5.4.
+
+## 5.4 Average spectral efficiency
+
+As defined in Report ITU-R M.2410 [4], average spectral efficiency is the aggregate throughput of all users (the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time) divided by the channel bandwidth of a specific band divided by the number of TRxPs and is measured in bit/s/Hz/TRxP.
+
+As required by Report ITU-R M.2412 [6], average spectral efficiency and 5<sup>th</sup> percentile user spectral efficiency are assessed jointly using the same simulation.
+
+### 5.4.1 NR
+
+Average spectral efficiency and 5<sup>th</sup> percentile user spectral efficiency are evaluated for NR. Both NR FDD and TDD are evaluated. A wide range of antenna configurations and transmission schemes are considered. Detailed evaluation assumptions and results can be found in Annex B.4.1.
+
+The antenna configuration is indicated as  $(M, N, P, M_g, N_g; M_p, N_p)$ , where  $M$  and  $N$  are the number of vertical, horizontal antenna elements within a panel,  $P$  is number of polarizations,  $M_g$  is the number of panels in a column,  $N_g$  is the number of panels in row; and  $M_p$  and  $N_p$  are the number of vertical, horizontal TXRUs within a panel and polarization.
+
+#### 5.4.1.1 Indoor Hotspot – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) and evaluation configuration B (carrier frequency = 30 GHz) with either 12TRxP or 36TRxP cases are applied for the evaluations of Indoor Hotspot– eMBB test environment for NR.
+
+##### 5.4.1.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration A with 12TRxP are provided in Table 5.4.1.1.1-1.
+
+It is noted that for NR, the component carrier bandwidth can be larger than the simulation bandwidth as defined in Report ITU-R M.2412 [6]. For those larger bandwidth cases, the guard band ratio can be further decreased; and the OFDM symbol occupation by PDCCH is expected to be reduced, even to less than one OFDM symbol due to the capability of PDCCH resource sharing with PDSCH.
+
+Such capabilities are evaluated in Indoor Hotspot - eMBB test environment as well as in Dense Urban – eMBB test environment and Rural – eMBB test environment, for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+**Table 5.4.1.1.1-1 DL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                             | Sub-carrier spacing (kHz) | ITU Requirement                  |     | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|--------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                              |                           |                                  |     | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 32x4 MU-MIMO Type II Codebook; gNB Config. = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 10                | 10.95     | 12.38     | 13.24     | 7                 | 10.98     | 12.43     | 13.29     |
+|                                                              |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.36      | 0.41      | 0.43      |                   | 0.37      | 0.42      | 0.45      |
+| 32x4 MU-MIMO Type I Codebook; gNB Config. = (4,4,2,1,1;4,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 11.50     | 13.05     | 13.97     | /                 | /         | /         | /         |
+|                                                              |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.31      | 0.35      | 0.38      |                   | /         | /         | /         |
+| 32x8 MU-MIMO Type II Codebook; gNB Config. = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 2                 | 10.43     | 11.76     | 12.57     | 1                 | 10.66     | 12.11     | 12.97     |
+|                                                              |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.39      | 0.44      | 0.47      |                   | 0.47      | 0.54      | 0.58      |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement         |     | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|-----------------------------------------------------------------------|---------------------------|-----------------|-------------------------|-----|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                       |                           |                 |                         |     | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config (4,4,2,1,1;4,4)   | 30                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 2                 | 11.98     | 14.03     | 15.41      | 4                 | 11.67     | 13.64     | 14.98      |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.45      | 0.52      | 0.58       |                   | 0.41      | 0.48      | 0.52       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,4,2,1,1;4,4) | 15                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 12.77     | 14.65     | /          | 2                 | 11.78     | 13.44     | /          |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.39      | 0.45      | /          |                   | 0.38      | 0.44      | /          |
+| 32x4 MU-MIMO, Type II Codebook based; gNB Config = (4,4,2,1,1;4,4)    | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 8.77      | 10.43     | /          | /                 | /         | /         | /          |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.33      | 0.39      | /          |                   | /         | /         | /          |
+| 32x4 MU-MIMO, Type II Codebook; 4T SRS; gNB Config = (4,4,2,1,1;4,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 13.27     | 15.18     | /          | 1                 | 13.55     | 15.5      | /          |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.49      | 0.56      | /          |                   | 0.5       | 0.58      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,4,2,1,1;4,4) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 2                 | 11.61     | 13.68     | 15.08      | 2                 | 11.96     | 14.09     | 15.53      |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.41      | 0.48      | 0.53       |                   | 0.45      | 0.53      | 0.59       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,4,2,1,1;4,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 3                 | 11.73     | 13.46     | /          | 4                 | 11.81     | 13.49     | /          |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.39      | 0.45      | /          |                   | 0.41      | 0.47      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config= (4,4,2,1,1;4,4)  | 30                        | DDDDD DDSUU     | Average [bit/s/Hz/TRxP] | 9   | 2                 | 12.54     | 14.74     | 16.23      | 1                 | 11.71     | 13.96     | 15.47      |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.41      | 0.48      | 0.53       |                   | 0.41      | 0.49      | 0.54       |
+| 32x8 MU-MIMO, Reciprocity based; 2T SRS; gNB Config= (4,4,2,1,1;4,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 9.37      | 10.79     | /          | /                 | /         | /         | /          |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.39      | 0.45      | /          |                   | /         | /         | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config= (4,4,2,1,1;4,4)  | 30                        | DDDSUD DSUU     | Average [bit/s/Hz/TRxP] | 9   | 1                 | 11.37     | 13.64     | 15.17      | 1                 | 11.59     | 13.91     | 15.47      |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.41      | 0.49      | 0.55       |                   | 0.40      | 0.48      | 0.54       |
+| 32x8 MU-MIMO, Type II codebook; gNB Config= (4,4,2,1,1;4,4)           | 30                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 9.90      | 11.55     | 12.68      | 1                 | 10.26     | 11.97     | 13.14      |
+|                                                                       |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.42      | 0.49      | 0.54       |                   | 0.46      | 0.53      | 0.58       |
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration A with 36TRxP are provided in Table 5.4.1.1.1-2.
+
+It is observed that both NR FDD and NR TDD fulfill the DL spectral efficiency requirement for all the above configurations in evaluation configuration A.
+
+**Table 5.4.1.1.1-2 DL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 36TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                              | Sub-carrier spacing (kHz) | ITU Requirement                  |     | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|---------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                               |                           |                                  |     | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 32x4 MU-MIMO Type II Codebook; gNB@ Config = (8,16,2,1,1;2,8) | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 7                 | 12.24     | 13.85     | 14.81     | 4                 | 13.12     | 14.83     | 15.86     |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.36      | 0.40      | 0.43      |                   | 0.35      | 0.39      | 0.42      |
+| 32x4 MU-MIMO Type I codebook; gNB Config = (4,4,2,1,1;4,4)    | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 1                 | /         | 10.67     | /         | /                 | /         | /         | /         |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | /         | 0.31      | /         |                   | /         | /         | /         |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                                                        | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement         |     | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|---------------------------------------------------------------------------------------------------------|---------------------------|-----------------|-------------------------|-----|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                                                         |                           |                 |                         |     | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;2,8)                                  | 30                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 2                 | 12.72     | 14.88     | 16.35      | 1                 | 12.87     | 15.06     | 16.55      |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.41      | 0.48      | 0.53       |                   | 0.39      | 0.46      | 0.50       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;2,8)                                  | 15                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 14.56     | 16.71     | /          | 1                 | 14.67     | 16.84     | /          |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.39      | 0.44      | /          |                   | 0.39      | 0.45      | /          |
+| 32x4 MU-MIMO, Type II Codebook based; gNB Config = (8,16,2,1,1;2,8)                                     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | /                 | 10.38     | 12.35     | /          | /                 | /         | /         | /          |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.33      | 0.40      | /          |                   | /         | /         | /          |
+| 32x4 MU-MIMO, Type II codebook; Reciprocity based; 4T SRS; gNB@ (M,N,P,Mg,Ng; Mp,Np) = (8,16,2,1,1;2,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 2                 | 12.16     | 13.88     | /          | 2                 | 12.37     | 14.12     | /          |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.35      | 0.40      | /          |                   | 0.33      | 0.38      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;2,8)                                  | 30                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 13.00     | 15.18     | 16.66      | 1                 | 13.17     | 15.38     | 16.88      |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.32      | 0.37      | 0.40       |                   | 0.34      | 0.39      | 0.43       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)                                   | 30                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 9.48      | 11.05     | 12.12      | 1                 | 9.46      | 11.03     | 12.11      |
+|                                                                                                         |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.32      | 0.38      | 0.41       |                   | 0.33      | 0.39      | 0.43       |
+
+The evaluation results of UL spectral efficiency for NR FDD and TDD for evaluation configuration A with 12TRxP are provided in Table 5.4.1.1.1-3.
+
+**Table 5.4.1.1.1-3 UL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                  | Sub-carrier spacing (kHz) | ITU Requirement         |      | Channel model A   |          | Channel model B   |          |
+|---------------------------------------------------|---------------------------|-------------------------|------|-------------------|----------|-------------------|----------|
+|                                                   |                           |                         |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 2x32 SU-MIMO, OFDMA; gNB Config = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP] | 6.75 | 3                 | 8.75     | 1                 | 8.87     |
+|                                                   |                           | 5th-tile [bit/s/Hz]     | 0.21 |                   | 0.52     |                   | 0.55     |
+| 4x32 MU-MIMO, OFDMA; gNB Config = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP] | 6.75 | 3                 | 10.16    | 1                 | 10.09    |
+|                                                   |                           | 5th-tile [bit/s/Hz]     | 0.21 |                   | 0.44     |                   | 0.41     |
+| 4x32 SU-MIMO, OFDMA; gNB Config = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP] | 6.75 | 3                 | 8.88     | 4                 | 8.42     |
+|                                                   |                           | 5th-tile [bit/s/Hz]     | 0.21 |                   | 0.55     |                   | 0.52     |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                               | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|----------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 6.95     | 2                 | 7.70     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.39     |                   | 0.44     |
+| 2x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.17     | 1                 | 7.26     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.40     |                   | 0.41     |
+| 4x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.58     | 1                 | 7.62     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.43     |                   | 0.43     |
+| 4x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.87     | 1                 | 7.95     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.44     |                   | 0.45     |
+| 4x32 MU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 12.22    | /                 | /        |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.59     |                   | /        |
+| 4x32 SU-MIMO, Non-Codebook based; gNB Config = (4,4,2,1,1;4,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 9.57     | 2                 | 9.34     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.60     |                   | 0.50     |
+| 4x32 SU-MIMO, Non-Codebook based; gNB Config = (4,4,2,1,1;4,4) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 9.25     | 1                 | 8.99     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.58     |                   | 0.52     |
+| 4x32 SU-MIMO, Codebook based; gNB Configs = (4,4,2,1,1;4,4)    | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.99     | 1                 | 8.65     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.63     |                   | 0.54     |
+| 4x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.58     | 1                 | 8.12     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.57     |                   | 0.48     |
+| 2x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.26     | 1                 | 9.35     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.53     |                   | 0.53     |
+| 2x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DDDSUDDSU U     | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.85     | 1                 | 7.85     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.58     |                   | 0.58     |
+| 2x32 SU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DDDSUDDSU U     | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.02     | 1                 | 7.01     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.52     |                   | 0.52     |
+| 4x32 MU-MIMO, Codebook based; gNB Config = (4,4,2,1,1;4,4)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.89     | 1                 | 8.85     |
+|                                                                |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.36     |                   | 0.36     |
+
+The evaluation results of UL spectral efficiency for NR FDD and TDD for evaluation configuration A with 36TRxP are provided in Table 5.4.1.1.1-4.
+
+It is observed that both NR FDD and NR TDD fulfill the UL spectral efficiency requirement for all the above configurations in evaluation configuration A.
+
+**Table 5.4.1.1.1-4 UL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 36TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                   | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|----------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                    |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 4x32 MU-MIMO, OFDMA; gNB Config = (8,16,2,1,1;2,8) | 15                        | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 14.52    | /                 | /        |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.55     |                   | /        |
+| 2x32 MU-MIMO, OFDMA; gNB Config = (4,4,2,1,1;4,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 6.75 | 2                 | 7.17     | /                 | /        |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.27     |                   | /        |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration            | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|---------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                             |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 4x32 MU-MIMO; gNB Config = (8,16,2,1,1;2,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 13.46    | /                 | /        |
+|                                             |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.51     |                   | /        |
+
+##### **5.4.1.1.2 Evaluation configuration B (CF = 30 GHz)**
+
+The evaluation results of DL spectral efficiency for NR for evaluation configuration B with 12TRxP are provided in Table 5.4.1.1.2-1.
+
+It is noted that for NR, the component carrier bandwidth can be larger than the simulation bandwidth as defined in Report ITU-R M.2412 [6]. For those larger bandwidth cases, the guard band ratio can be further decreased; and the OFDM symbol occupation by PDCCH is expected to be reduced, even to less than one OFDM symbol due to the capability of PDCCH resource sharing with PDSCH.
+
+Such capabilities are evaluated for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+**Table 5.4.1.1.2-1 DL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                                                                          | Sub-carrier spacing (kHz) | ITU Requirement                  |     | Number of samples | BW=40 MHz |
+|-----------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|-----------|
+|                                                                                                           |                           |                                  |     |                   |           |
+| 8x4 MU-MIMO Type II codebook (2 panel@UE)<br>gNB Config = (4,8,2,1,1;2,2)<br>UE Config = (2,4,2,1,2; 1,1) | 120                       | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 8.50      |
+|                                                                                                           |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.31      |
+| 32x8 MU-MIMO Type II codebook (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2;1,1) | 120                       | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 12.27     |
+|                                                                                                           |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.44      |
+| 32x8 MU-MIMO Type II codebook (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2;1,1) | 60                        | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 12.69     |
+|                                                                                                           |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.41      |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                                                                          | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement         |                     | Number of samples | BW= 80MHz / 100 MHz | BW= 200MHz | BW= 400MHz |
+|---------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|-------------------------|---------------------|-------------------|---------------------|------------|------------|
+|                                                                                                                           |                           |                 | Average [bit/s/Hz/TRxP] | 5th-tile [bit/s/Hz] |                   |                     |            |            |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)     | 60                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9                   | 3                 | 12.77               | 14.51      | /          |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.37                | 0.42       | /          |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)     | 120                       | DDDSU           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 13.86               | 15.49      | 16.25      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.48                | 0.53       | 0.56       |
+| 32x4 MU-MIMO, Type II Codebook based (2 panel@UE)<br>gNB Config = (8,8,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,1)        | 120                       | DSUUD           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | /                   | 9.80       | 10.46      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | /                   | 0.40       | 0.42       |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,8,2,1,1;2,8);<br>UE Config = (2,4,2,1,2; 1,2)     | 60                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9                   | 2                 | 13.71               | 15.87      | /          |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.57                | 0.66       | /          |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,8,2,1,1;2,8);<br>UE Config = (2,4,2,1,2; 1,2)     | 120                       | DSUUD           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 14.93               | 16.95      | 17.65      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.61                | 0.69       | 0.72       |
+| 64x8 MU-MIMO, Reciprocity based ; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;2,16);<br>UE Config = (2,4,2,1,2; 1,2)  | 60                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 16.75               | 19.22      | /          |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 1.00                | 1.14       | /          |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;2,16);<br>UE Config = (2,4,2,1,2; 1,2)   | 120                       | DSUUD           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 16.84               | 19.12      | 19.91      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 1.00                | 1.13       | 1.18       |
+| 64x16 MU-MIMO, Reciprocity based ; 4T SRS (2 panel@UE)<br>gNB Config = (4,32,2,1,1;1,32);<br>UE Config = (1,4,2,1,2; 1,4) | 60                        | DDDSU           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 13.90               | 16.87      | /          |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.35                | 0.42       | /          |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS (1 panel@UE)<br>gNB Config = (16,8,2,1,1;2,2);<br>UE Config = (4,4,2,1,1; 1,2)     | 120                       | DDDU            | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 12.03               | 14.40      | 14.97      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.49                | 0.58       | 0.60       |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)    | 120                       | DDDSU           | Average [bit/s/Hz/TRxP] | 9                   | 1                 | 11.03               | 12.53      | 13.01      |
+|                                                                                                                           |                           |                 | 5th-tile [bit/s/Hz]     | 0.3                 |                   | 0.40                | 0.46       | 0.47       |
+
+The evaluation results of DL spectral efficiency for NR for evaluation configuration B with 36TRxP are provided in Table 5.4.1.1.2-2.
+
+It is observed that NR fulfills the DL spectral efficiency requirement for all the above configurations in evaluation configuration B.
+
+**Table 5.4.1.1.2-2 DL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 36TRxP)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                         | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement         |     | Number of samples | BW= 80MHz / 100MHz | BW= 200MHz | BW= 400MHz |
+|--------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|-------------------------|-----|-------------------|--------------------|------------|------------|
+|                                                                                                                          |                           |                 |                         |     |                   |                    |            |            |
+| 32x4 MU-MIMO Type II Codebook based (2 panel@UE)<br>gNB Config = (8,8,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1)         | 120                       | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | /                  | 10.04      | 10.72      |
+|                                                                                                                          |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | /                  | 0.34       | 0.36       |
+| 32x8 MU-MIMO, Reciprocity based; 4Tx SRS (2 panel@UE)<br>gNB Config = (4,16,2,1,1;1,16)<br>UE Config = (2,4,2,1,2; 1,2)  | 60                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 12.72              | 14.60      | /          |
+|                                                                                                                          |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.38               | 0.43       | /          |
+| 32x8 MU-MIMO, Reciprocity based; 4Tx SRS (2 panels@UE)<br>gNB Config = (4,16,2,1,1;1,16)<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 12.11              | 13.75      | 14.32      |
+|                                                                                                                          |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.31               | 0.35       | 0.36       |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;2,16)<br>UE Config = (2,4,2,1,2; 1,2)   | 60                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 14.85              | 17.05      | /          |
+|                                                                                                                          |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.48               | 0.56       | /          |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;2,16);<br>UE Config = (2,4,2,1,2; 1,2)  | 60                        | DSUUD           | Average [bit/s/Hz/TRxP] | 9   | 1                 | 14.22              | 16.14      | 16.81      |
+|                                                                                                                          |                           |                 | 5th-tile [bit/s/Hz]     | 0.3 |                   | 0.49               | 0.56       | 0.58       |
+
+The evaluation results of UL spectral efficiency for NR for evaluation configuration B with 12TRxP are provided in Table 5.4.1.1.2-3.
+
+**Table 5.4.1.1.2-3 UL spectral efficiency for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                                                                  | Sub-carrier spacing (kHz) | ITU Requirement         |      | Number of samples | BW=40MHz |
+|---------------------------------------------------------------------------------------------------|---------------------------|-------------------------|------|-------------------|----------|
+|                                                                                                   |                           |                         |      |                   |          |
+| 4x8 MU-MIMO, OFDMA (2 panel@UE);<br>gNB Config= (4,8,2,1,1; 2,2)<br>UE Config = (2,4,2,1,2; 1,1)  | 120                       | Average [bit/s/Hz/TRxP] | 6.75 | 1                 | 7.66     |
+|                                                                                                   |                           | 5th-tile [bit/s/Hz]     | 0.21 |                   | 0.39     |
+| 8x32 SU-MIMO, OFDMA (2 panel@UE);<br>gNB Config= (4,4,2,1,1; 4,4)<br>UE Config = (2,4,2,1,2; 1,1) | 60                        | Average [bit/s/Hz/TRxP] | 6.75 | 1                 | 10.39    |
+|                                                                                                   |                           | 5th-tile [bit/s/Hz]     | 0.21 |                   | 0.41     |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration                                                                                 | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW= 80MHz |
+|------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|-----------|
+|                                                                                                                  |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |           |
+| 8x32 SU-MIMO, Codebook based, OFDMA (2 panel@UE); gNB Config = (4,4,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,2)     | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 7.04      |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.40      |
+| 4x32 MU-MIMO, Codebook based, OFDMA (2 panel@UE); gNB Config = (8,8,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,1)     | 120                       | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 10.91     |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.41      |
+| 8x32 SU-MIMO, Non-codebook based, OFDMA (2 panel@UE); gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2) | 60                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 7.44      |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.37      |
+| 8x64 MU-MIMO Codebook based (1 panel@UE); gNB Config = (4,32,2,1,1;1,32) UE Config = (1,4,2,1,1; 1,4)            | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 10.19     |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.31      |
+| 4x2, SU-MIMO, Codebook based, OFDMA (1 panel @UE) gNB Config = (16,8,2,1,1;1,1) UE Config = (4,4,2,1,1; 1,2)     | 120                       | DDDU            | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 6.90      |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.30      |
+| 8x16, MU-MIMO, Codebook based, OFDMA (2 panel@UE) gNB Config = (4,16,2,1,1;4,4) UE Config = (2,4,2,1,1; 1,2)     | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 7.83      |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.37      |
+| 8x32, SU-MIMO, Codebook based, OFDMA (2 panel@UE) gNB Config = (8,8,2,1,1;4,4) UE Config = (2,4,2,1,1; 1,2)      | 60                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 7.44      |
+|                                                                                                                  |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.32      |
+
+The evaluation results of UL spectral efficiency for NR for evaluation configuration B with 36TRxP are provided in Table 5.4.1.1.2-4.
+
+It is observed that NR fulfills the UL spectral efficiency requirement for all the above configurations in evaluation configuration B.
+
+**Table 5.4.1.1.2-4 UL spectral efficiency for NR in Indoor Hotspot – eMBB (Evaluation configuration B, CF=30 GHz, for 36TRxP)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration                                              | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW=80MHz |
+|-------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|----------|
+|                                                                               |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |          |
+| 4x32 MU-MIMO OFDMA, gNB Config = (8,8,2,1,1;4,4) UE Config = (2,4,2,1,2; 1,1) | 120                       | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 9.82     |
+|                                                                               |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.33     |
+
+#### **5.4.1.2 Dense Urban – eMBB**
+
+Evaluation configuration A (carrier frequency = 4 GHz) is applied for the evaluations of Dense Urban – eMBB test environment for NR.
+
+##### **5.4.1.2.1 Evaluation configuration A (CF = 4 GHz)**
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.4.1.2.1-1.
+
+Similar to Indoor Hotspot – eMBB test environment, the capability of NR in larger bandwidth are evaluated for DL spectral efficiency. The values of the larger bandwidths are shown together with the evaluation results.
+
+It is observed that both NR FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.1.2.1-1 DL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                                 | Sub-carrier spacing (kHz) | ITU Requirement                  |       | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|------------------------------------------------------------------|---------------------------|----------------------------------|-------|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                                  |                           |                                  |       | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 32x4 MU-MIMO Type I<br>Codebook; gNB Config = (8,8,2,1,1;2,8)    | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 11                | 11.04     | 12.52     | 13.39     | 9                 | 10.95     | 12.42     | 13.28     |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.37      | 0.42      | 0.45      |                   | 0.36      | 0.41      | 0.43      |
+| 32x4 MU-MIMO Type I<br>Codebook; gNB Config = (8,8,2,1,1;2,8)    | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 2                 | 10.95     | 12.33     | 13.16     | /                 | /         | /         | /         |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.33      | 0.38      | 0.40      |                   | /         | /         | /         |
+| 32x4 MU-MIMO Type II<br>Codebook; gNB Config = (8,16,2,1,1;1,16) | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 14.81     | 16.84     | 18.04     | /                 | /         | /         | /         |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.54      | 0.61      | 0.65      |                   | /         | /         | /         |
+| 32x4 MU-MIMO Type II<br>Codebook; gNB Config = (16,8,2,1,1;2,8)  | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 12.65     | 14.3      | 15.28     | 1                 | 12.31     | 13.91     | 14.87     |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.44      | 0.50      | 0.54      |                   | 0.44      | 0.49      | 0.53      |
+| 32x8 MU-MIMO Type II<br>Codebook; gNB Config = (16,8,2,1,1;2,8)  | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 11.83     | 13.26     | 14.13     | /                 | /         | /         | /         |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.33      | 0.37      | 0.40      |                   | /         | /         | /         |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                        |                           |                 |                                  |       | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 4                 | 13.03     | 15.26     | 16.77      | 4                 | 13.07     | 15.20     | 16.60      |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.47      | 0.55      | 0.61       |                   | 0.45      | 0.53      | 0.57       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 2                 | 13.95     | 15.88     | /          | 4                 | 11.77     | 13.36     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.34      | 0.38      | /          |                   | 0.39      | 0.44      | /          |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 16.10     | 18.84     | 20.70      | 2                 | 16.23     | 19.14     | 21.11      |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.49      | 0.58      | 0.64       |                   | 0.52      | 0.62      | 0.68       |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 15.71     | 18.02     | /          | 1                 | 15.46     | 17.73     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.48      | 0.56      | /          |                   | 0.49      | 0.56      | /          |
+| 32x4 MU-MIMO, Type II Codebook based; gNB Config = (8,16,2,1,1;1,16)   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 12.25     | 14.56     | /          | /                 | /         | /         | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.44      | 0.53      | /          |                   | /         | /         | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 13.11     | 15.00     | /          | 1                 | 12.81     | 14.66     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.42      | 0.48      | /          |                   | 0.41      | 0.46      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 2                 | 12.54     | 14.39     | /          | 2                 | 13.64     | 15.46     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.36      | 0.41      | /          |                   | 0.41      | 0.46      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 12.88     | 15.04     | 16.50      | 1                 | 12.50     | 14.59     | 16.02      |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.43      | 0.50      | 0.55       |                   | 0.40      | 0.47      | 0.52       |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 15.72     | 18.01     | /          | 1                 | 15.73     | 18.03     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.59      | 0.68      | /          |                   | 0.57      | 0.65      | /          |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 16.23     | 18.60     | /          | 1                 | 16.28     | 18.66     | /          |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.60      | 0.68      | /          |                   | 0.61      | 0.7       | /          |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 2                 | 16.00     | 18.86     | 20.8       | 2                 | 15.89     | 18.73     | 20.66      |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.58      | 0.69      | 0.76       |                   | 0.57      | 0.67      | 0.74       |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 15.9      | 18.59     | 20.42      | 1                 | 15.87     | 18.55     | 20.38      |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.61      | 0.71      | 0.78       |                   | 0.62      | 0.73      | 0.80       |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS;                               | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 12.20     | 14.82     | /          | /                 | /         | /         | /          |
+
+|                                                                           |    |                |                                  |       |   |       |       |       |   |       |       |       |
+|---------------------------------------------------------------------------|----|----------------|----------------------------------|-------|---|-------|-------|-------|---|-------|-------|-------|
+| gNB Config = (4,32,2,1,1;1,32)                                            |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.30  | 0.36  | /     |   | /     | /     | /     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)    | 30 | DDDDD<br>DDSUU | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 16.07 | 18.95 | 20.89 | / | /     | /     | /     |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.42  | 0.50  | 0.55  |   | /     | /     | /     |
+| 32x8 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (16,8,2,1,1;2,8)    | 15 | DSUUD          | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 11.90 | 13.70 | /     | / | /     | /     | /     |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.32  | 0.36  | /     |   | /     | /     | /     |
+| 32x4 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (16,8,2,1,1;2,8)    | 15 | DSUUD          | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 7.87  | 9.06  | /     | / | /     | /     | /     |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.23  | 0.26  | /     |   | /     | /     | /     |
+| 128x4, MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;4,16) | 30 | DDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | / | /     | /     | /     | 1 | 10.78 | 12.56 | 13.78 |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | /     | /     | /     |   | 0.36  | 0.42  | 0.46  |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;4,8)     | 30 | DDDSU          | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 14.99 | 17.51 | 19.23 | 1 | 15.08 | 17.62 | 19.34 |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.62  | 0.72  | 0.79  |   | 0.54  | 0.63  | 0.69  |
+| 16x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;1,8)     | 30 | DSUUD          | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 9.59  | 11.19 | 12.29 | 1 | 9.51  | 11.11 | 12.19 |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.38  | 0.44  | 0.49  |   | 0.39  | 0.45  | 0.50  |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)     | 30 | DDDDD<br>DDSUU | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 13.05 | 15.55 | 17.23 | 1 | 13.35 | 15.91 | 17.63 |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.54  | 0.64  | 0.71  |   | 0.46  | 0.55  | 0.61  |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)    | 30 | DDDSU<br>DDSUU | Average [bit/s/Hz/TRxP]          | 7.8   | 1 | 16.73 | 20.08 | 22.33 | 1 | 16.59 | 19.91 | 22.14 |
+|                                                                           |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |   | 0.61  | 0.73  | 0.81  |   | 0.57  | 0.68  | 0.76  |
+
+The evaluation results of UL spectral efficiency for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.4.1.2.1-2.
+
+It is observed that both NR FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.1.2.1-2 UL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                       | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|--------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                        |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 2x16 SU-MIMO, OFDMA;<br>gNB Config = (8,8,2,1,1;1,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 4                 | 7.69     | 1                 | 6.67     |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.25     |                   | 0.22     |
+| 2x32 SU-MIMO, OFDMA;<br>gNB Config = (8,8,2,1,1;2,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 2                 | 7.31     | 3                 | 7.53     |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.37     |                   | 0.34     |
+| 4x32 SU-MIMO, OFDMA;<br>gNB Config = (8,8,2,1,1;2,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 2                 | 9.88     | 2                 | 9.23     |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.42     |                   | 0.43     |
+| 4x32 MU-MIMO, OFDMA;<br>gNB Config = (8,16,2,1,1;1,16) | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 19.00    | /                 | /        |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 1.00     |                   | /        |
+| 4x32 MU-MIMO, OFDMA;<br>gNB Config = (16,8,2,1,1;2,8)  | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.08     | /                 | /        |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.24     |                   | /        |
+| 4x16 SU-MIMO, OFDMA;<br>gNB Config = (8,8,2,1,1;1,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.09     | 1                 | 6.40     |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.33     |                   | 0.35     |
+| 4x4 SU-MIMO, OFDMA;<br>gNB Config = (8,8,2,1,1;2,1)    | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 9.57     | /                 | /        |
+|                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.19     |                   | /        |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                       |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.14     | 1                 | 6.11     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.28     |                   | 0.25     |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.57     | 1                 | 6.48     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.28     |                   | 0.25     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.03     | 2                 | 7.21     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.36     |                   | 0.41     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.49     | 1                 | 7.47     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.36     |                   | 0.29     |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.73     | 2                 | 7.64     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.33     |                   | 0.35     |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 2                 | 8.02     | 2                 | 7.71     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.33     |                   | 0.34     |
+| 4x32 MU-MIMO, Codebook based, OFDMA; gNB Config = (8,16,2,1,1;1,16)   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 17.57    | /                 | /        |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.93     |                   | /        |
+| 4x16 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.56     | 1                 | 6.90     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.27     |                   | 0.32     |
+| 4x16 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.28     | 1                 | 6.34     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.26     |                   | 0.35     |
+| 4x16 SU-MIMO, codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.05     | 1                 | 6.43     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.25     |                   | 0.28     |
+| 4x16 SU-MIMO, codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8)     | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 5.69     | 1                 | 6.02     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.23     |                   | 0.29     |
+| 8x64 MU-MIMO, Codebook based, OFDMA; gNB Config = (4,32,2,1,1;1,32)   | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.28     | /                 | /        |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.16     |                   | /        |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,4)    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | /                 | /        | 1                 | 8.16     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | /        |                   | 0.55     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 8.28     | 1                 | 8.24     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.60     |                   | 0.58     |
+| 4x128, MU-MIMO, Codebook based, OFDMA; gNB Config = (8,16,2,1,1;4,16) | 30                        | DDSU            | Average [bit/s/Hz/TRxP]          | 5.4  | /                 | /        | 1                 | 5.51     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | /        |                   | 0.17     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30                        | DDDSUD<br>DSUU  | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.86     | 1                 | 7.87     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.52     |                   | 0.52     |
+
+|                                                                       |    |             |                                  |      |   |      |   |       |
+|-----------------------------------------------------------------------|----|-------------|----------------------------------|------|---|------|---|-------|
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30 | DDDDDD DSUU | Average [bit/s/Hz/TRxP]          | 5.4  | 1 | 7.03 | 1 | 7.04  |
+|                                                                       |    |             | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |   | 0.47 |   | 0.47  |
+| 4x32 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8) | 15 | DSUUD       | Average [bit/s/Hz/TRxP]          | 5.4  | / | /    | 1 | 10.47 |
+|                                                                       |    |             | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |   | /    |   | 0.38  |
+| 4x32 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8) | 15 | DDDSU       | Average [bit/s/Hz/TRxP]          | 5.4  | / | /    | 1 | 8.86  |
+|                                                                       |    |             | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |   | /    |   | 0.28  |
+
+##### 5.4.1.2.2 Evaluation configuration B (CF=30 GHz)
+
+The evaluation results for DL spectral efficiency for configuration B are shown in Table 5.4.1.2.2-1. The bandwidth of 80/100 MHz, 200 MHz and 400 MHz are evaluated for TDD.
+
+**Table 5.4.1.2.2-1 DL spectral efficiency for NR in Dense Urban – eMBB (Evaluation configuration B, CF=30 GHz)**
+
+###### (a) NR TDD
+
+| Scheme and antenna configuration                                                                                   | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Number of samples | BW= 80MHz / 100 MHz | BW= 200MHz | BW= 400MHz |
+|--------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|---------------------|------------|------------|
+|                                                                                                                    |                           |                 | Average [bit/s/Hz/TRxP]          |       |                   |                     |            |            |
+| 32x32 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE) gNB Config = (8,16,2,1,1;1,16); UE Config = (2,8,2,1,1; 1,8) | 60                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 9.83                | 11.28      | /          |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.02                | 0.02       | /          |
+| 64x32 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE) gNB Config = (8,16,2,1,1;2,16); UE Config = (2,8,2,1,1; 1,8) | 60                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 11.14               | 12.79      | /          |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.05                | 0.06       | /          |
+| 128x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE) gNB Config = (8,16,2,1,1;4,16); UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 19.30               | 21.50      | 22.60      |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.05                | 0.06       | 0.06       |
+| 128x8 MU-MIMO, Type I codebook; Wideband (2 panel@UE) gNB Config = (8,16,2,1,1;4,16); UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 15.30               | 17.10      | 18.00      |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.05                | 0.06       | 0.06       |
+
+The evaluation results of UL spectral efficiency for configuration B are provided in Table 5.4.1.2.2-2.
+
+**Table 5.4.1.2.2-2 UL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW=80MHz / 100MHz |
+|-----------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|-------------------|
+|                                                                                                                       |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                   |
+| 8x32 SU-MIMO, Codebook based, OFDMA, (2 panel@UE);<br>gNB Config = (4,8,2,2,2;1,1)<br>UE Config = (2,4,2,1,2; 1,2)    | 120                       | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4                              | 1                 | 6.93              |
+|                                                                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15                             |                   | 0.04              |
+| 8x128 MU-MIMO, Codebook based, OFDMA, (2 panel@UE);<br>gNB Config = (8,16,2,1,1;4,16)<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4                              | 1                 | 10.10             |
+|                                                                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15                             |                   | 0.06              |
+
+Further evaluation results of configuration B, with modified ITU-R parameters, are shown in Appendix B.5 for information purpose.
+
+#### 5.4.1.3 Rural – eMBB
+
+Evaluation configuration A (carrier frequency = 700 MHz), evaluation configuration B (carrier frequency = 4 GHz), and evaluation configuration C (LMLC) are applied for the evaluations of Rural – eMBB test environment for NR.
+
+##### 5.4.1.3.1 Evaluation configuration A (CF = 700 MHz)
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.4.1.3.1-1.
+
+Similar to Indoor Hotspot – eMBB test environment, the capability of NR in larger bandwidth are evaluated for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+It is observed that both NR FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.1.3.1-1 DL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration A, CF=700 MHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                            | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|-------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                             |                           |                                  |      | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 8x2 MU-MIMO Type II Codebook; gNB Config = (8,4,2,1,1;1,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 9                 | 5.92      | 6.66      | 7.1       | 7                 | 5.83      | 6.53      | 6.94      |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.16      | 0.18      | 0.20      |                   | 0.17      | 0.19      | 0.20      |
+| 16x2 MU-MIMO Type II Codebook; gNB Config = (8,4,2,1,1;2,4) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 7.48      | 8.39      | 8.94      | 2                 | 8.83      | 9.96      | 12.64     |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.15      | 0.17      | 0.18      |                   | 0.20      | 0.22      | 0.24      |
+| 8x4 MU-MIMO Type II Codebook; gNB Config = (8,4,2,1,1;1,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 9.42      | 10.66     | 11.40     | 1                 | 9.08      | 10.27     | 10.99     |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.16      | 0.18      | 0.19      |                   | 0.17      | 0.19      | 0.21      |
+| 16x4 MU-MIMO Type II Codebook; gNB Config = (4,8,2,1,1;1,8) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 15.28     | 17.37     | 18.61     | /                 | /         | /         | /         |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.47      | 0.54      | 0.57      |                   | /         | /         | /         |
+| 16x2 MU-MIMO Type II Codebook; gNB Config = (4,8,2,1,1;1,8) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 9.58      | 10.81     | 11.55     | 1                 | 10.02     | 11.23     | 11.96     |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.25      | 0.28      | 0.30      |                   | 0.27      | 0.30      | 0.32      |
+| 8x2 MU-MIMO Type I codebook; gNB Config = (8,4,2,1,1;1,4)   | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 6.08      | 6.82      | 7.27      | /                 | /         | /         | /         |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.15      | 0.17      | 0.19      |                   | /         | /         | /         |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|-----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                       |                           |                 |                                  |      | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 4                 | 6.77      | 7.80      | 8.50       | 4                 | 6.47      | 7.43      | 8.12       |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.16      | 0.19      | 0.21       |                   | 0.18      | 0.21      | 0.23       |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 8.08      | 9.11      | /          | 4                 | 5.71      | 6.44      | /          |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.18      | 0.20      | /          |                   | 0.14      | 0.16      | /          |
+| 16x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;2,4) | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 9.21      | 10.64     | 11.61      | 1                 | 9.22      | 10.65     | 11.62      |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.21      | 0.25      | 0.27       |                   | 0.22      | 0.25      | 0.28       |
+| 16x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;2,4) | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 8.9       | 10.08     | /          | 1                 | 8.95      | 10.14     | /          |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.18      | 0.2       | /          |                   | 0.18      | 0.21      | /          |
+| 16x4 MU-MIMO, Type II codebook based; gNB Config = (4,8,2,1,1;1,8)    | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 12.61     | 14.99     | /          | /                 | /         | /         | /          |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.39      | 0.46      | /          |                   | /         | /         | /          |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 3                 | 8.13      | 9.34      | /          | 3                 | 8.08      | 9.25      | /          |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.24      | 0.28      | /          |                   | 0.23      | 0.26      | /          |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 6.71      | 7.84      | 8.60       | 2                 | 6.91      | 8.07      | 8.86       |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.19      | 0.22      | 0.24       |                   | 0.19      | 0.22      | 0.25       |
+| 16x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,8,2,1,1;1,8) | 30                        | DDSU            | Average [bit/s/Hz/TRxP]          | 3.3  | /                 | /         | /         | /          | 1                 | 6.61      | 7.7       | 8.45       |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | /         | /         | /          |                   | 0.13      | 0.15      | 0.17       |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 30                        | DDDDD DDSUU     | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 5.07      | 5.99      | 6.60       | 1                 | 5.12      | 6.04      | 6.67       |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.14      | 0.16      | 0.18       |                   | 0.15      | 0.17      | 0.19       |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 30                        | DDDSU DDSUU     | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 5.04      | 5.98      | 6.62       | 1                 | 5.04      | 5.98      | 6.62       |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.14      | 0.16      | 0.18       |                   | 0.14      | 0.16      | 0.18       |
+
+The evaluation results of UL spectral efficiency for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.4.1.3.1-2.
+
+It is observed that both NR FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.1.3.1-2 UL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration A, CF=700 MHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                  | Sub-carrier spacing (kHz) | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|---------------------------------------------------|---------------------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                   |                           |                                  |       | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 1x8 SU-MIMO, OFDMA; gNB Config = (8,4,2,1,1;1,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 1.6   | 4                 | 4.35     | 3                 | 4.04     |
+|                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.14     |                   | 0.14     |
+| 4x16 MU-MIMO, OFDMA; gNB Config = (4,8,2,1,1;1,8) | 15                        | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 12.69    | /                 | /        |
+|                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.62     |                   | /        |
+| 2x8 SU-MIMO, OFDMA; gNB Config = (8,4,2,1,1;1,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 1.6   | 3                 | 7.22     | 5                 | 5.66     |
+|                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.17     |                   | 0.19     |
+|                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.20     |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                     | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                      |                           |                 |                                  |       | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 2                 | 3.75     | 2                 | 4.82     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.14     |                   | 0.10     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 2                 | 6.50     | 2                 | 4.85     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.09     |                   | 0.09     |
+| 4x16 MU-MIMO, Codebook based, OFDMA; gNB Config = (4,8,2,1,1;1,8)    | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 11.75    | /                 | /        |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.58     |                   | /        |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 4.44     | 1                 | 4.45     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.18     |                   | 0.16     |
+| 2x8 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4) | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 2                 | 5.08     | 1                 | 4.22     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.16     |                   | 0.17     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 4.71     | 1                 | 4.74     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.20     |                   | 0.16     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 4.51     | 1                 | 4.56     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.18     |                   | 0.15     |
+| 2x16 MU-MIMO, Codebook based, OFDMA; gNB Config = (4,8,2,1,1;1,8)    | 30                        | DDSU            | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 4.19     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.22     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 30                        | DDDSU<br>DDSUU  | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 5.34     | 1                 | 5.38     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.11     |                   | 0.13     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4)     | 30                        | DDDDD<br>DDSUU  | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 4.78     | 1                 | 4.81     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.13     |                   | 0.12     |
+| 2x8 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 5.33     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.14     |
+| 2x8 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 4.53     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.13     |
+
+##### 5.4.1.3.2 Evaluation configuration B (CF = 4 GHz)
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration B are provided in Table 5.4.1.3.2-1.
+
+Similar to Indoor Hotspot – eMBB test environment, the capability of NR in larger bandwidth are evaluated for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+It is observed that both NR FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration B.
+
+**Table 5.4.1.3.2-1 DL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration B, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                              | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|---------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                               |                           |                                  |      | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 32x4 MU-MIMO Type II Codebook; gNB Config = (8,8,2,1,1;2,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 7                 | 12.50     | 14.13     | 15.10     | 8                 | 13.01     | 14.70     | 15.68     |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.44      | 0.49      | 0.53      |                   | 0.41      | 0.46      | 0.49      |
+| 32x4 MU-MIMO Type II Codebook; gNB Config = (8,16,2,1,1;1,16) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 17.32     | 19.64     | 21.01     | 1                 | 16.63     | 18.79     | 20.09     |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.49      | 0.56      | 0.59      |                   | 0.52      | 0.58      | 0.62      |
+| 16x4 MU-MIMO Type II Codebook; gNB Config = (8,8,2,1,1;1,8)   | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 12.58     | 14.23     | 15.22     | 1                 | 11.96     | 13.53     | 14.47     |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.12      | 0.14      | 0.15      |                   | 0.13      | 0.14      | 0.15      |
+| 32x4 MU-MIMO Type I codebook; gNB Config = (8,8,2,1,1;1,8)    | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 10.76     | 12.07     | 12.86     | 1                 | 5.30      | 5.96      | 6.35      |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.22      | 0.25      | 0.26      |                   | 1.76      | 1.98      | 2.11      |
+| 16x4 MU-MIMO Type I codebook; gNB Config = (8,8,2,1,1;1,8)    | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 10.21     | 11.43     | 12.16     | /                 | /         | /         | /         |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.16      | 0.18      | 0.19      |                   | /         | /         | /         |
+| 32x8 MU-MIMO Type II Codebook; gNB Config = (8,16,2,1,1;1,16) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 15.32     | 17.18     | 18.3      | /                 | /         | /         | /         |
+|                                                               |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.27      | 0.30      | 0.32      |                   | /         | /         | /         |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                         | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|--------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                          |                           |                 |                                  |      | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)    | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 4                 | 14.36     | 16.75     | 18.37      | 4                 | 14.30     | 16.58     | 18.08      |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.45      | 0.52      | 0.58       |                   | 0.44      | 0.51      | 0.56       |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)    | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 15.63     | 17.79     | /          | 3                 | 12.84     | 14.60     | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.30      | 0.35      | /          |                   | 0.37      | 0.43      | /          |
+| 32x4 MU-MIMO, Type II Codebook based; gNB Config = (8,16,2,1,1;1,16)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 14.86     | 17.67     | /          | /                 | /         | /         | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.39      | 0.46      | /          |                   | /         | /         | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)    | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 15.04     | 17.46     | /          | 1                 | 15.17     | 17.84     | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.58      | 0.68      | /          |                   | 0.49      | 0.58      | /          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 14.29     | 16.68     | 18.31      | /                 | /         | /         | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.47      | 0.55      | 0.60       |                   | /         | /         | /          |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30                        | DDDDD DDDSU     | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 16.89     | 19.59     | 21.44      | /                 | /         | /         | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.43      | 0.50      | 0.55       |                   | /         | /         | /          |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 2                 | 15.40     | 18.14     | 20.00      | 2                 | 15.23     | 17.94     | 19.78      |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.58      | 0.69      | 0.76       |                   | 0.54      | 0.64      | 0.71       |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3  | /                 | /         | /         | /          | 1                 | 14.52     | 16.90     | 18.53      |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | /         | /         | /          |                   | 0.49      | 0.57      | 0.63       |
+| 128x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,32,2,1,1;2,32) | 30                        | DDSU            | Average [bit/s/Hz/TRxP]          | 3.3  | /                 | /         | /         | /          | 1                 | 10.36     | 12.08     | 13.25      |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | /         | /         | /          |                   | 0.13      | 0.15      | 0.16       |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,32,2,1,1;1,32)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 17.38     | 21.11     | /          | /                 | /         | /         | /          |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.43      | 0.52      | /          |                   | /         | /         | /          |
+| 32x8 MU-MIMO, Reciprocity                                                | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 12.46     | 14.35     | /          | /                 | /         | /         | /          |
+
+|                                                                                   |    |                |                                  |      |   |       |       |       |   |       |       |       |
+|-----------------------------------------------------------------------------------|----|----------------|----------------------------------|------|---|-------|-------|-------|---|-------|-------|-------|
+| based; 2T SRS<br>gNB Config =<br>(8,16,2,1,1;1,16)                                |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |   | 0.18  | 0.20  | /     |   | /     | /     | /     |
+| 32x4 MU-MIMO,<br>Reciprocity<br>based; 4T SRS<br>gNB Config =<br>(8,8,2,1,1;2,8)  | 30 | DDDDD<br>DDSUU | Average<br>[bit/s/Hz/TRxP]       | 3.3  | 1 | 13.21 | 15.74 | 17.44 | 1 | 13.19 | 15.71 | 17.41 |
+|                                                                                   |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |   | 0.43  | 0.51  | 0.57  |   | 0.48  | 0.57  | 0.63  |
+| 64x4 MU-MIMO,<br>Reciprocity<br>based; 4T SRS<br>gNB Config =<br>(12,8,2,1,1;4,8) | 30 | DDDSU<br>DDSUU | Average<br>[bit/s/Hz/TRxP]       | 3.3  | 1 | 14.54 | 17.45 | 19.40 | 1 | 14.76 | 17.72 | 19.70 |
+|                                                                                   |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |   | 0.46  | 0.55  | 0.61  |   | 0.48  | 0.58  | 0.64  |
+| 16x4 MU-MIMO,<br>Reciprocity<br>based; 4T SRS<br>gNB Config =<br>(8,8,2,1,1;1,8)  | 15 | DSUUD          | Average<br>[bit/s/Hz/TRxP]       | 3.3  | / | /     | /     | /     | 1 | 11.24 | 12.63 | /     |
+|                                                                                   |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |   | /     | /     | /     |   | 0.24  | 0.27  | /     |
+| 16x4 MU-MIMO,<br>Reciprocity<br>based; 4T SRS<br>gNB Config =<br>(8,8,2,1,1;1,8)  | 15 | DDDSU          | Average<br>[bit/s/Hz/TRxP]       | 3.3  | / | /     | /     | /     | 1 | 11.08 | 12.43 | /     |
+|                                                                                   |    |                | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |   | /     | /     | /     |   | 0.26  | 0.29  | /     |
+
+The evaluation results of UL spectral efficiency for NR FDD and NR TDD for evaluation configuration B are provided in Table 5.4.1.3.2-2.
+
+It is observed that both NR FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration B.
+
+**Table 5.4.1.3.2-2 UL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration B, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                          | Sub-carrier spacing (kHz) | ITU Requirement                     |       | Channel model A   |          | Channel model B   |          |
+|-----------------------------------------------------------|---------------------------|-------------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                           |                           |                                     |       | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 1x32 SU-MIMO, OFDMA;<br>gNB Config =<br>(8,8,2,1,1;2,8)   | 15                        | Average<br>[bit/s/Hz/TRxP]          | 1.6   | 4                 | 4.28     | 2                 | 4.52     |
+|                                                           |                           | 5 <sup>th</sup> -tile<br>[bit/s/Hz] | 0.045 |                   | 0.14     |                   | 0.16     |
+| 4x32 SU-MIMO, OFDMA;<br>gNB Config =<br>(8,8,2,1,1;2,8)   | 15                        | Average<br>[bit/s/Hz/TRxP]          | 1.6   | 2                 | 7.38     | 3                 | 7.70     |
+|                                                           |                           | 5 <sup>th</sup> -tile<br>[bit/s/Hz] | 0.045 |                   | 0.29     |                   | 0.22     |
+| 4x32 MU-MIMO, OFDMA;<br>gNB Config =<br>(8,16,2,1,1;1,16) | 15                        | Average<br>[bit/s/Hz/TRxP]          | 1.6   | 2                 | 12.46    | /                 | /        |
+|                                                           |                           | 5 <sup>th</sup> -tile<br>[bit/s/Hz] | 0.045 |                   | 0.23     |                   | /        |
+| 2x32 SU-MIMO, OFDMA;<br>gNB Config =<br>(8,8,2,1,1;2,8)   | 15                        | Average<br>[bit/s/Hz/TRxP]          | 1.6   | 1                 | 6.27     | 1                 | 6.16     |
+|                                                           |                           | 5 <sup>th</sup> -tile<br>[bit/s/Hz] | 0.045 |                   | 0.23     |                   | 0.19     |
+| 4x16 SU-MIMO, OFDMA;<br>gNB Config =<br>(8,8,2,1,1;1,8)   | 15                        | Average<br>[bit/s/Hz/TRxP]          | 1.6   | 1                 | 9.90     | /                 | /        |
+|                                                           |                           | 5 <sup>th</sup> -tile<br>[bit/s/Hz] | 0.045 |                   | 0.02     |                   | /        |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                    | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|---------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                     |                           |                 |                                  |       | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 1x32 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;2,8)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 3.18     | 1                 | 3.12     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.11     |                   | 0.09     |
+| 1x32 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;2,8)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 3.54     | 1                 | 3.46     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.12     |                   | 0.10     |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;2,8)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 5.73     | 2                 | 5.86     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.18     |                   | 0.13     |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;2,8)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 6.30     | 2                 | 5.85     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.19     |                   | 0.14     |
+| 4x32 MU-MIMO, Codebook based, OFDMA; gNB Config (8,16,2,1,1;1,16)   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 13.96    | /                 | /        |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.35     |                   | /        |
+| 8x64 SU-MIMO, Codebook based, OFDMA; gNB Config (4,32,2,1,1;1,32)   | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 10.73    | /                 | /        |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.07     |                   | /        |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config (12,8,2,1,1;4,8)    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 7.83     | 1                 | 7.66     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.31     |                   | 0.32     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config (12,8,2,1,1;4,8)    | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 6.82     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.29     |
+| 2x128, MU-MIMO, Codebook-based, OFDMA; gNB Config (8,16,2,1,1;4,16) | 30                        | DDSU            | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 9.2      |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.11     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config (12,8,2,1,1;4,8)    | 30                        | DDDSU<br>DDSUU  | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 7.44     | 1                 | 7.33     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.34     |                   | 0.29     |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config (12,8,2,1,1;4,8)    | 30                        | DDDDD<br>DDSUU  | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 6.66     | 1                 | 6.56     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.30     |                   | 0.26     |
+| 4x16 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;1,8)     | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 2.7      | /                 | /        |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.17     |                   | /        |
+| 4x16 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;1,8)     | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 6.27     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.08     |
+| 4x16 SU-MIMO, Codebook based, OFDMA; gNB Config (8,8,2,1,1;1,8)     | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6   | /                 | /        | 1                 | 5.25     |
+|                                                                     |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | /        |                   | 0.08     |
+
+##### 5.4.1.3.3 Evaluation configuration C (LMLC)
+
+LMLC (Low mobility large cell) is characterized by the large inter-site distance (ISD=6000m) and the low mobility users in Rural – eMBB test environment.
+
+The evaluation results of DL spectral efficiency for NR FDD and NR TDD for evaluation configuration C are provided in Table 5.4.1.3.3-1.
+
+Similar to Indoor Hotspot – eMBB test environment, the capability of NR in larger bandwidth are evaluated for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+It is observed that both NR FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration C.
+
+**Table 5.4.1.3.3-1 DL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration C, LMLC)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                                                    | Sub-carrier spacing (kHz) | ITU Requirement <sup>1</sup>     |     | Channel model A   |           |           |           | Channel model B   |           |           |           |
+|-------------------------------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|-----------|-----------|-----------|-------------------|-----------|-----------|-----------|
+|                                                                                     |                           |                                  |     | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz | Number of samples | BW= 10MHz | BW= 20MHz | BW= 40MHz |
+| 8x4 MU-MIMO Type II Codebook; gNB Config = (8,4,2,1,1;1,4)                          | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | 8                 | 7.81      | 8.79      | 9.39      | 8                 | 7.31      | 8.22      | 8.76      |
+|                                                                                     |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.21      | 0.23      | 0.25      |                   | 0.22      | 0.25      | 0.26      |
+| 16x4 MU-MIMO Type II Codebook; gNB Config = (8,4,2,1,1;2,4)                         | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 8.13      | 9.13      | 9.73      | 1                 | 8.14      | 9.13      | 9.73      |
+|                                                                                     |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.20      | 0.23      | 0.24      |                   | 0.20      | 0.23      | 0.24      |
+| 16x4 MU-MIMO Type II Codebook; gNB Config = (4,8,2,1,1;1,8)                         | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | 2                 | 10.40     | 11.76     | 12.57     | /                 | /         | /         | /         |
+|                                                                                     |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.34      | 0.39      | 0.41      |                   | /         | /         | /         |
+| 8x4 MU-MIMO Type I codebook; gNB Config = (8,4,2,1,1;1,4)                           | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | 2                 | 8.36      | 9.38      | 10.00     | /                 | /         | /         | /         |
+|                                                                                     |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.20      | 0.22      | 0.24      |                   | /         | /         | /         |
+| 8x4 MU-MIMO Type I codebook; gNB Config = (8,4,2,1,1;1,4) (Optimized for cell edge) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | /                 | /         | /         | /         | 1                 | 3.90      | 4.37      | 4.65      |
+|                                                                                     |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /         | /         | /         |                   | 0.84      | 0.94      | 1.00      |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement <sup>1</sup>     |     | Channel model A   |           |           |            | Channel model B   |           |           |            |
+|-------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-----|-------------------|-----------|-----------|------------|-------------------|-----------|-----------|------------|
+|                                                                         |                           |                 |                                  |     | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz | Number of samples | BW= 20MHz | BW= 40MHz | BW= 100MHz |
+| 8x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;1,4);   | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | 4                 | 7.35      | 8.50      | 9.28       | 4                 | 7.66      | 8.83      | 9.74       |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.22      | 0.26      | 0.28       |                   | 0.26      | 0.30      | 0.33       |
+| 8x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;1,4);   | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | 2                 | 9.34      | 10.56     | /          | 3                 | 7.83      | 8.79      | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.22      | 0.25      | /          |                   | 0.21      | 0.24      | /          |
+| 16x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;2,4);  | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 8.61      | 9.98      | 10.91      | 1                 | 8.59      | 9.95      | 10.89      |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.2       | 0.23      | 0.25       |                   | 0.19      | 0.22      | 0.25       |
+| 16x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;2,4);  | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 8.83      | 9.98      | /          | 1                 | 8.82      | 9.96      | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.22      | 0.25      | /          |                   | 0.21      | 0.24      | /          |
+| 16x4 MU-MIMO, Type II Codebook; gNB Config = (4,8,2,1,1;1,8);           | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 10.44     | 12.41     | /          | /                 | /         | /         | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.35      | 0.41      | /          |                   | /         | /         | /          |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,32,2,1,1;1,32) | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 6.01      | 7.3       | /          | /                 | /         | /         | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /         | /         | /          |                   | /         | /         | /          |
+| 8x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;1,4);   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3 | 2                 | 7.98      | 9.33      | /          | 2                 | 8.97      | 19.29     | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.25      | 0.29      | /          |                   | 0.23      | 0.27      | /          |
+| 8x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,4,2,1,1;1,4)    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 8.34      | 9.91      | 10.97      | 1                 | 8.38      | 9.96      | 11.02      |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.28      | 0.33      | 0.37       |                   | 0.31      | 0.37      | 0.41       |
+| 16x4 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (4,8,2,1,1;1,8)   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 7.59      | 8.74      | /          | /                 | /         | /         | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.23      | 0.26      | /          |                   | /         | /         | /          |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)    | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 3.3 | /                 | /         | /         | /          | 1                 | 5.70      | 6.50      | /          |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /         | /         | /          |                   | 0.16      | 0.18      | /          |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+The evaluation results of UL spectral efficiency for NR FDD and NR TDD for evaluation configuration C are provided in Table 5.4.1.3.3-2.
+
+It is observed that both NR FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration C.
+
+**Table 5.4.1.3.3-2 UL spectral efficiency for NR in Rural – eMBB  
+(Evaluation configuration C, LMLC)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                   | Sub-carrier spacing (kHz) | ITU Requirement <sup>1</sup>     |     | Channel model A   |          | Channel model B   |          |
+|----------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                    |                           |                                  |     | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 2x8 SU-MIMO, OFDMA; gNB Config = (8,4,2,1,1;1,4);  | 15                        | Average [bit/s/Hz/TRxP]          | 1.6 | 2                 | 4.22     | 2                 | 4.16     |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.14     |                   | 0.13     |
+| 1x8 SU-MIMO, OFDMA; gNB Config = (8,4,2,1,1;1,4);  | 15                        | Average [bit/s/Hz/TRxP]          | 1.6 | 2                 | 4.54     | /                 | /        |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.09     |                   | /        |
+| 4x8 SU-MIMO, OFDMA; gNB Config = (8,4,2,1,1;1,4);  | 15                        | Average [bit/s/Hz/TRxP]          | 1.6 | 2                 | 5.38     | 2                 | 4.78     |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.13     |                   | 0.09     |
+| 4x16 MU-MIMO, OFDMA; gNB Config = (4,8,2,1,1;1,8); | 15                        | Average [bit/s/Hz/TRxP]          | 1.6 | 2                 | 8.33     | /                 | /        |
+|                                                    |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.11     |                   | /        |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration                                     | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement <sup>1</sup>     |     | Channel model A   |          | Channel model B   |          |
+|----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                                      |                           |                 |                                  |     | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4);    | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 3.33     | 1                 | 3.31     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.06     |                   | 0.05     |
+| 2x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4);    | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 3.56     | 1                 | 3.57     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.05     |                   | /        |
+| 4x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4);    | 30                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 3.84     | 3                 | 3.71     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.07     |                   | 0.06     |
+| 4x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4);    | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | 2                 | 4.21     | 2                 | 3.99     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.06     |                   | 0.06     |
+| 4x16 SU-MIMO, Codebook based, OFDMA; gNB Config = (4,8,2,1,1;1,8);   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 10.59    | /                 | /        |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.08     |                   | /        |
+| 8x64 MU-MIMO, Codebook based, OFDMA; gNB Config = (4,32,2,1,1;1,32)  | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 4.82     | /                 | /        |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /        |                   | /        |
+| 4x8 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4);    | 30                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 4.41     | 1                 | 3.56     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /        |                   | /        |
+| 4x8 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6 | /                 | /        | 1                 | 4.56     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /        |                   | 0.09     |
+| 4x8 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,4,2,1,1;1,4) | 15                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 1.6 | /                 | /        | 1                 | 3.79     |
+|                                                                      |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | /        |                   | 0.08     |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+### 5.4.2 LTE
+
+Average spectral efficiency and 5<sup>th</sup> percentile user spectral efficiency are evaluated for LTE. Both LTE FDD and TDD are evaluated. Detailed evaluation assumptions and results can be found in Annex B.4.1.
+
+#### 5.4.2.1 Indoor Hotspot – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) is applied for the evaluations of Indoor Hotspot – eMBB test environment for LTE.
+
+##### 5.4.2.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of DL spectral efficiency for LTE FDD and LTE TDD for evaluation configuration A with 12TRxP are provided in Table 5.4.2.1.1-1.
+
+It is observed that both LTE FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.1.1-1 DL spectral efficiency for LTE in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### (a) LTE FDD
+
+| Scheme and antenna configuration                                 | Sub-carrier spacing (kHz) | ITU Requirement                  |     | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                                  |                           |                                  |     | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 32x4 MU-MIMO Advanced CSI Codebook; gNB Config = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 9.81     | 1                 | 9.86     |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.35     |                   | 0.40     |
+
+###### (b) LTE TDD
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |     | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                                        |                           |                 |                                  |     | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 64x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,16,2,1,1;4,8) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 9.25     | 1                 | 9.61     |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.33     |                   | 0.34     |
+| 32x4 MU-MIMO, Advanced CSI Codebook; gNB Config = (4,4,2,1,1;1,4)      | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 11.81    | 1                 | 11.88    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.42     |                   | 0.35     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,4,2,1,1;4,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 11.76    | 1                 | 11.78    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.40     |                   | 0.39     |
+| 32x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (4,4,2,1,1;4,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 9.37     | 1                 | 9.46     |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.39     |                   | 0.38     |
+
+The evaluation results of UL spectral efficiency for LTE FDD and TDD for evaluation configuration A are provided in Table 5.4.2.1.1-2.
+
+It is observed that both LTE FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.1.1-2 UL spectral efficiency for LTE in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                        |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 4x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (4,4,2,1,1;4,4) | 15                        | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.47     | 1                 | 7.96     |
+|                                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.51     |                   | 0.49     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                         |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x64 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (8,16,2,1,1;4,8) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 7.37     | 1                 | 7.43     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.38     |                   | 0.40     |
+| 4x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (4,4,2,1,1;4,4)  | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.05     | 1                 | 7.74     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.54     |                   | 0.49     |
+| 2x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (16,8,2,1,1;4,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 6.75 | 1                 | 8.84     | 1                 | 8.81     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21 |                   | 0.34     |                   | 0.32     |
+
+#### **5.4.2.2 Dense Urban – eMBB**
+
+Evaluation configuration A (carrier frequency = 4 GHz) is applied for the evaluations of Dense Urban – eMBB test environment for LTE.
+
+##### **5.4.2.2.1 Evaluation configuration A (CF = 4 GHz)**
+
+The evaluation results of DL spectral efficiency for LTE FDD and LTE TDD for evaluation configuration A are provided in Table 5.4.2.2.1-1.
+
+It is observed that both LTE FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.2.1-1 DL spectral efficiency for LTE in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                  | Sub-carrier spacing (kHz) | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------------|---------------------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                   |                           |                                  |       | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 32x4 MU-MIMO Advanced CSI Codebook; gNB Config = (8,8,2,1,1;2,8)  | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 8.96     | 1                 | 9.03     |
+|                                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.28     |                   | 0.28     |
+| 32x4 MU-MIMO Advanced CSI Codebook; gNB Config = (16,8,2,1,1;2,8) | 15                        | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 9.31     | 1                 | 9.18     |
+|                                                                   |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.29     |                   | 0.29     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                        |                           |                 |                                  |       | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 64x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 8.78     | 1                 | 9.05     |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.25     |                   | 0.26     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 12.25    | 1                 | 12.15    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.39     |                   | 0.38     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 14.53    | 1                 | 14.59    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.52     |                   | 0.50     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 14.91    | 1                 | 14.89    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.52     |                   | 0.52     |
+| 32x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (12,8,2,1,1;4,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 7.8   | 1                 | 10.06    | 1                 | 10.03    |
+|                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225 |                   | 0.33     |                   | 0.34     |
+
+The evaluation results of UL spectral efficiency for LTE FDD and TDD for evaluation configuration A are provided in Table 5.4.2.2.1-2.
+
+It is observed that both LTE FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.2.1-2 UL spectral efficiency for LTE in Dense Urban – eMBB (Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                         |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 4x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (16,8,2,1,1;2,8) | 15                        | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.95     | 1                 | 7.21     |
+|                                                                         |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.39     |                   | 0.41     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                         |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x64 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (12,8,2,1,1;4,8) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.65     | 1                 | 6.59     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.33     |                   | 0.30     |
+| 4x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (16,8,2,1,1;2,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 6.60     | 1                 | 6.77     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.30     |                   | 0.32     |
+| 2x32 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (16,8,2,1,1;4,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 5.4  | 1                 | 7.68     | 1                 | 7.66     |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15 |                   | 0.38     |                   | 0.37     |
+
+#### **5.4.2.3 Rural – eMBB**
+
+Evaluation configuration A (carrier frequency = 700 MHz), evaluation configuration B (carrier frequency = 4 GHz), and evaluation configuration C (LMLC) are applied for the evaluations of Rural – eMBB test environment for LTE.
+
+##### **5.4.2.3.1 Evaluation configuration A (CF = 700 MHz)**
+
+The evaluation results of DL spectral efficiency for LTE FDD and TDD for evaluation configuration A are provided in Table 5.4.2.3.1-1.
+
+It is observed that both LTE FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.3.1-1 DL spectral efficiency for LTE in Rural – eMBB (Evaluation configuration A, CF=700 MHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                 | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                  |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 8x2 MU-MIMO Advanced CSI Codebook; gNB Config = (8,4,2,1,1;1,4)  | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 4.66     | 2                 | 4.51     |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.12     |                   | 0.12     |
+| 16x2 MU-MIMO Advanced CSI Codebook; gNB Config = (4,8,2,1,1;1,8) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 6.45     | 1                 | 6.46     |
+|                                                                  |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.16     |                   | 0.15     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                       |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 16x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (4,8,2,1,1;1,8) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 11.05    | 1                 | 11.22    |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.29     |                   | 0.29     |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (8,4,2,1,1;1,4)  | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 5.00     | 1                 | 5.52     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.18     |                   | 0.19     |
+
+The evaluation results of UL spectral efficiency for LTE FDD and TDD for evaluation configuration A are provided in Table 5.4.2.3.1-2.
+
+It is observed that both LTE FDD and TDD fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration A.
+
+**Table 5.4.2.3.1-1 UL spectral efficiency for LTE in Rural – eMBB  
+(Evaluation configuration A, CF=700 MHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|-----------------------------------------------------------------------|---------------------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                       |                           |                                  |       | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 1x8 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (8,4,2,1,1;1,4) | 15                        | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 3.59     | 1                 | 3.59     |
+|                                                                       |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.10     |                   | 0.10     |
+| 2x8 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (8,4,2,1,1;1,4) | 15                        | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 4.30     | 2                 | 4.75     |
+|                                                                       |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.22     |                   | 0.18     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|-----------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                       |                           |                 |                                  |       | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 2x8 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (8,4,2,1,1;1,4) | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 3.78     | 1                 | 3.80     |
+|                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.15     |                   | 0.13     |
+
+##### **5.4.2.3.2 Evaluation configuration B (CF = 4 GHz)**
+
+The evaluation results of DL spectral efficiency for LTE FDD and TDD for evaluation configuration B are provided in Table 5.4.2.3.2-1.
+
+It is observed that both LTE FDD and TDD fulfill the DL spectral efficiency requirement for these configurations in evaluation configuration B.
+
+**Table 5.4.2.3.2-1 DL spectral efficiency for LTE in Rural – eMBB  
+(Evaluation configuration B, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                            | Sub-carrier spacing (kHz) | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------|---------------------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                             |                           |                                  |      | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 32x4 MU-MIMO Type II Codebook; gNB Config = (8,8,2,1,1;2,8) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 9.65     | 1                 | 9.63     |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.28     |                   | 0.28     |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |      | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|------|-------------------|----------|-------------------|----------|
+|                                                                         |                           |                 |                                  |      | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)   | 15                        | DSUUD           | Average [bit/s/Hz/TRxP]          | 3.3  | /                 | /        | 1                 | 12.25    |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | /        |                   | 0.43     |
+| 64x8 MU-MIMO, Reciprocity based; 8T SRS; gNB Config = (4,32,2,1,1;1,32) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 14.75    | /                 | /        |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.36     |                   | /        |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)   | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 3.3  | 1                 | 11.59    | 1                 | 12.23    |
+|                                                                         |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.12 |                   | 0.45     |                   | 0.38     |
+
+The evaluation results of UL spectral efficiency for LTE for evaluation configuration B are provided in Table 5.4.2.3.2-2.
+
+It is observed that both LTE fulfill the UL spectral efficiency requirement for these configurations in evaluation configuration B.
+
+**Table 5.4.2.3.2-2 UL spectral efficiency for LTE in Rural – eMBB (Evaluation configuration B, CF=4 GHz)**
+
+###### **(a) LTE TDD**
+
+| Scheme and antenna configuration                                         | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |       | Channel model A   |          | Channel model B   |          |
+|--------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-------|-------------------|----------|-------------------|----------|
+|                                                                          |                           |                 |                                  |       | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 8x64 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (4,32,2,1,1;1,32) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 1.6   | 1                 | 10.15    | /                 | /        |
+|                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.045 |                   | 0.07     |                   | /        |
+
+##### **5.4.2.3.3 Evaluation configuration C (LMLC)**
+
+LMLC (Low mobility large cell) is characterized by the large inter-site distance (ISD=6000m) and the low mobility users in Rural – eMBB test environment.
+
+The evaluation results of DL spectral efficiency for LTE for evaluation configuration C are provided in Table 5.4.2.3.3-1.
+
+It is observed that both LTE fulfills the DL spectral efficiency requirement for these configurations in evaluation configuration C.
+
+**Table 5.4.2.3.3-1 DL spectral efficiency for LTE in Rural – eMBB  
+(Evaluation configuration C, LMLC)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                            | Sub-carrier spacing (kHz) | ITU Requirement <sup>1</sup>     |     | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                             |                           |                                  |     | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 8x4 MU-MIMO, Type II Codebook; gNB Config = (8,4,2,1,1;1,4) | 15                        | Average [bit/s/Hz/TRxP]          | 3.3 | 1                 | 5.96     | 1                 | 5.97     |
+|                                                             |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.15     |                   | 0.15     |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                            | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement <sup>1</sup>     |     | Channel model A   |          | Channel model B   |          |
+|-------------------------------------------------------------|---------------------------|-----------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                             |                           |                 |                                  |     | Number of samples | BW=20MHz | Number of samples | BW=20MHz |
+| 8x4 MU-MIMO, Type II Codebook; gNB Config = (8,4,2,1,1;1,4) | 15                        | DSUDD           | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 6.86     | 1                 | 6.68     |
+|                                                             |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.30     |                   | 0.27     |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+The evaluation results of UL spectral efficiency for LTE for evaluation configuration C are provided in Table 5.4.2.3.3-2.
+
+It is observed that both LTE fulfills the UL spectral efficiency requirement for these configurations in evaluation configuration C.
+
+**Table 5.4.2.3.3-2 UL spectral efficiency for LTE in Rural – eMBB  
+(Evaluation configuration C, LMLC)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing (kHz) | ITU Requirement <sup>1</sup>     |     | Channel model A   |          | Channel model B   |          |
+|------------------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|----------|-------------------|----------|
+|                                                                        |                           |                                  |     | Number of samples | BW=10MHz | Number of samples | BW=10MHz |
+| 2x8 SU-MIMO, Codebook based, DFT-S-OFDM; gNB Config = (8,4,2,1,1;1,4); | 15                        | Average [bit/s/Hz/TRxP]          | 1.6 | 1                 | 3.36     | 1                 | 3.31     |
+|                                                                        |                           | 5 <sup>th</sup> -tile [bit/s/Hz] |     |                   | 0.07     |                   | 0.06     |
+
+Note 1: According to Report ITU-R M.2410 [4], the 5<sup>th</sup> percentile user spectral efficiency requirement is not applicable to LMLC. The value shown here is for information only.
+
+## 5.5 User experienced data rate
+
+As defined in Report ITU-R M.2410 [4], user experienced data rate is the 5% point of the cumulative distribution function (CDF) of the user throughput. User throughput (during active time) is defined as the number of correctly received bits, i.e. the number of bits contained in the service data units (SDUs) delivered to Layer 3, over a certain period of time.
+
+### 5.5.1 NR
+
+User experienced data rate for NR are evaluated under Dense Urban – eMBB test environment.
+
+#### 5.5.1.1 Dense Urban – eMBB
+
+For Dense Urban – eMBB test environment, single-band single-layer case using evaluation configuration A (carrier frequency = 4 GHz), and multi-band case using evaluation configuration C as defined in Report ITU-R M.2412 [6] are considered in evaluation. Detailed evaluation assumptions for configuration A are based on spectral efficiency evaluation, and can be found in Annex B.4.1; detailed evaluation assumptions and results for configuration C can be found in Annex B.4.3.
+
+##### 5.5.1.1.1 Evaluation configuration A (CF = 4 GHz)
+
+For evaluation configuration A (single-band case), user experienced data rate for NR is evaluated based on 5<sup>th</sup> percentile user spectral efficiency, using the analytical way as provided in Report ITU-R M.2412 [6].
+
+The evaluation results of DL user experienced data rate for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.5.1.1.1-1.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 40 MHz is used; and for TDD with 30 kHz SCS, a component carrier with 100 MHz is used. Multiple component carriers are aggregated to achieve the DL target user experienced data rate. The assumed DL/UL aggregated system bandwidth (for FDD) or overall aggregated system bandwidth (for TDD) is given in Table 5.5.1.1.1-1.
+
+It is observed that both NR FDD and TDD fulfill the DL user experienced data rate requirement in evaluation configuration A.
+
+**Table 5.5.1.1.1-1 DL user experienced data rate for NR in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### (a) NR FDD
+
+| Scheme and antenna configuration                                 | Sub-carrier spacing | ITU Requirement [Mbps] | Channel model A   |                                   |                            | Channel model B   |                                   |                            |
+|------------------------------------------------------------------|---------------------|------------------------|-------------------|-----------------------------------|----------------------------|-------------------|-----------------------------------|----------------------------|
+|                                                                  |                     |                        | Number of samples | Assumed DL system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed DL system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 32x4 MU-MIMO Type II<br>Codebook; gNB Config = (8,8,2,1,1;2,8)   | 15                  | 100                    | 11                | 240                               | 108.33                     | 8                 | 240                               | 105.30                     |
+| 32x4 MU-MIMO Type I<br>Codebook; gNB Config = (8,8,2,1,1;2,8)    | 15                  | 100                    | 2                 | 280                               | 112.86                     | /                 | /                                 | /                          |
+| 32x4 MU-MIMO Type II<br>Codebook; gNB Config = (8,16,2,1,1;1,16) | 15                  | 100                    | 1                 | 160                               | 104.66                     | /                 | /                                 | /                          |
+| 32x4 MU-MIMO Type II<br>Codebook; gNB Config = (16,8,2,1,1;2,8)  | 15                  | 100                    | 1                 | 200                               | 107.02                     | 1                 | 200                               | 105.81                     |
+| 4x4 MU-MIMO Type II<br>Codebook; gNB Config = (8,8,2,1,1;2,1)    | 15                  | 100                    | 1                 | 240                               | 112.64                     | /                 | /                                 | /                          |
+| 32x8 MU-MIMO Type II<br>Codebook; gNB Config = (16,8,2,1,1;2,8)  | 15                  | 100                    | 1                 | 280                               | 111.68                     | /                 | /                                 | /                          |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing | Frame structure             | ITU Requirement [Mbps] | Channel model A   |                                |                            | Channel model B   |                                |                            |
+|------------------------------------------------------------------------|---------------------|-----------------------------|------------------------|-------------------|--------------------------------|----------------------------|-------------------|--------------------------------|----------------------------|
+|                                                                        |                     |                             |                        | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 30                  | DDDSU, S slot =10DL:2GP:2UL | 100                    | 3                 | 300                            | 138.60                     | 3                 | 300                            | 129.45                     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 30                  | DDDSU, S slot =11DL:1GP:2UL | 100                    | 1                 | 300                            | 137.16                     | /                 | /                              | /                          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 15                  | DDDSU, S slot =10DL:2GP:2UL | 100                    | 2                 | 360                            | 104.36                     | 2                 | 320                            | 102.09                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 30                  | DDDSU, S slot =10DL:2GP:2UL | 100                    | 1                 | 300                            | 144.34                     | 2                 | 200                            | 102.80                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                  | DDDSU, S slot =10DL:2GP:2UL | 100                    | 1                 | 240                            | 100.87                     | 1                 | 240                            | 102.57                     |
+| 32x4 MU-MIMO, Type II Codebook; gNB Config = (8,16,2,1,1;1,16)         | 15                  | DSUUD S slot =6DL:2GP:6UL   | 100                    | 1                 | 400                            | 105.37                     | /                 | /                              | /                          |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 15                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 1                 | 400                            | 107.44                     | 1                 | 400                            | 104.60                     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 15                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 2                 | 440                            | 101.81                     | 2                 | 400                            | 104.16                     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 30                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 1                 | 400                            | 123.50                     | 1                 | 400                            | 116.27                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 1                 | 280                            | 107.37                     | 1                 | 280                            | 103.20                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8) | 15                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 1                 | 280                            | 107.91                     | 1                 | 280                            | 110.81                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 30                  | DSUUD S slot =11DL:1GP:2UL  | 100                    | 1                 | 300                            | 126.31                     | 1                 | 300                            | 126.74                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 30                  | DSUUD S slot =6DL:2GP:6UL   | 100                    | 1                 | 300                            | 114.97                     | 1                 | 300                            | 109.22                     |
+
+|                                                                          |    |                                  |     |   |     |        |   |     |        |
+|--------------------------------------------------------------------------|----|----------------------------------|-----|---|-----|--------|---|-----|--------|
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8)   | 30 | DSUUD S slot =11DL:1GP:2UL       | 100 | 1 | 300 | 132.83 | 1 | 300 | 135.22 |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,32,2,1,1;1,32)  | 15 | DDDSU S slot =10DL:2GP:2UL       | 100 | 1 | 400 | 108.73 | / | /   | /      |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30 | DDDDD DDSUU S slot =6DL:4GP:4UL  | 100 | 1 | 300 | 124.58 | / | /   | /      |
+| 32x8 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (16,8,2,1,1;2,8)   | 15 | DSUUD S slot =6DL:2GP:6UL        | 100 | 1 | 560 | 102.08 | / | /   | /      |
+| 128x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;4,16) | 30 | DDSU S slot =10DL:2GP:2UL        | 100 | / | /   | /      | 1 | 360 | 111.91 |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,8,2,1,1;4,8)    | 30 | DDDSU S slot =10DL:2GP:2UL       | 100 | 1 | 200 | 119.46 | 1 | 200 | 104.18 |
+| 16x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)    | 30 | DDDSU S slot =10DL:2GP:2UL       | 100 | 1 | 300 | 110.93 | 1 | 300 | 113.01 |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30 | DDDDDDD SUU S slot =6DL:4GP:6UL  | 100 | 1 | 200 | 107.91 | 1 | 300 | 138.32 |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8)   | 30 | DDDSUDDS UU S slot =10DL:2GP:2UL | 100 | 1 | 200 | 106.39 | 1 | 300 | 149.29 |
+
+The evaluation results of UL user experienced data rate for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.5.1.1.1-2.
+
+It is assumed that for FDD with 15 kHz SCS, a component carrier with 40 MHz is used; for TDD with 15 kHz SCS, a component carrier with 50 MHz is used; and for TDD with 30 kHz SCS, a component carrier with 100 MHz is used. Multiple component carriers are aggregated to achieve the UL target user experienced data rate. The assumed aggregated system bandwidth is given in Table 5.5.1.1.1-2.
+
+It is observed that both NR FDD and TDD fulfill the UL user experienced data rate requirement in evaluation configuration A.
+
+**Table 5.5.1.1.1-2 UL user experienced data rate for NR in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                    | Sub-carrier spacing | ITU Requirement [Mbps] | Channel model A   |                                   |                            | Channel model B   |                                   |                            |
+|-----------------------------------------------------|---------------------|------------------------|-------------------|-----------------------------------|----------------------------|-------------------|-----------------------------------|----------------------------|
+|                                                     |                     |                        | Number of samples | Assumed UL system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed UL system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 2x16 SU-MIMO, OFDMA; gNB Config = (8,8,2,1,1;1,8)   | 15                  | 50                     | 4                 | 240                               | 59.79                      | 1                 | 240                               | 52.48                      |
+| 2x32 SU-MIMO, OFDMA; gNB Config = (8,8,2,1,1;2,8)   | 15                  | 50                     | 2                 | 160                               | 58.50                      | 3                 | 160                               | 53.79                      |
+| 4x32 SU-MIMO, OFDMA; gNB Config = (8,8,2,1,1;2,8)   | 15                  | 50                     | 2                 | 160                               | 66.66                      | 1                 | 160                               | 59.95                      |
+| 4x32 MU-MIMO, OFDMA; gNB Config = (8,16,2,1,1;1,16) | 15                  | 50                     | 1                 | 120                               | 63.33                      | /                 | /                                 | /                          |
+| 4x32 MU-MIMO, OFDMA; gNB Config = (16,8,2,1,1;2,8)  | 15                  | 50                     | 1                 | 200                               | 55.46                      | /                 | /                                 | /                          |
+| 4x16 SU-MIMO, OFDMA; gNB Config = (8,8,2,1,1;1,8)   | 15                  | 50                     | 1                 | 160                               | 52.80                      | 1                 | 160                               | 55.84                      |
+| 4x4 SU-MIMO, OFDMA; gNB Config = (8,8,2,1,1;2,1)    | 15                  | 50                     | 1                 | 280                               | 54.50                      | /                 | /                                 | /                          |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing | Frame structure               | ITU Requirement [Mbps] | Channel model A   |                                |                            | Channel model B   |                                |                            |
+|-----------------------------------------------------------------------|---------------------|-------------------------------|------------------------|-------------------|--------------------------------|----------------------------|-------------------|--------------------------------|----------------------------|
+|                                                                       |                     |                               |                        | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 30                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 1                 | 800                            | 53.68                      | 1                 | 900                            | 54.55                      |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 1                 | 800                            | 53.94                      | 1                 | 900                            | 53.83                      |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 1                 | 600                            | 51.80                      | 2                 | 600                            | 59.48                      |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 15                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 1                 | 600                            | 52.24                      | 1                 | 700                            | 50.11                      |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 30                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 1                 | 700                            | 56.21                      | 1                 | 700                            | 52.61                      |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15                  | DDDSU<br>S slot =10DL:2GP:2UL | 50                     | 2                 | 700                            | 55.80                      | 1                 | 800                            | 55.98                      |
+| 4x32 MU-MIMO, Codebook based, OFDMA; gNB Config = (8,16,2,1,1;1,16)   | 15                  | DSUUD<br>S slot =6DL:2GP:6UL  | 50                     | 1                 | 300                            | 73.15                      | /                 | /                              | /                          |
+| 4x16 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8) | 15                  | DSUUD<br>S slot =11DL:1GP:2UL | 50                     | 1                 | 500                            | 58.82                      | 1                 | 400                            | 55.07                      |
+| 4x16 SU-MIMO, Non-codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8) | 30                  | DSUUD<br>S slot =11DL:1GP:2UL | 50                     | 1                 | 500                            | 57.08                      | 1                 | 400                            | 61.35                      |
+| 4x16 SU-MIMO, codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8)     | 15                  | DSUUD<br>S slot =11DL:1GP:2UL | 50                     | 1                 | 500                            | 54.90                      | 1                 | 500                            | 60.35                      |
+| 4x16 SU-MIMO, codebook based, OFDMA; gNB Config = (8,8,2,1,1;1,8)     | 30                  | DSUUD<br>S slot =11DL:1GP:2UL | 50                     | 1                 | 500                            | 50.11                      | 1                 | 400                            | 50.89                      |
+| 2x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,4)    | 30                  | DSUUD<br>S slot =6DL:2GP:6UL  | 50                     | /                 | /                              | /                          | 1                 | 200                            | 55.44                      |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30                  | DSUUD<br>S slot =6DL:2GP:6UL  | 50                     | 1                 | 200                            | 59.63                      | 1                 | 200                            | 57.54                      |
+
+|                                                                       |    |                                                |    |   |     |       |   |      |       |
+|-----------------------------------------------------------------------|----|------------------------------------------------|----|---|-----|-------|---|------|-------|
+| 4x128, MU-MIMO, Codebook based, OFDMA; gNB Config = (8,16,2,1,1;4,16) | 30 | DDDSU<br>S slot<br>=10DL:2GP:<br>2UL           | 50 | / | /   | /     | 1 | 1000 | 52.92 |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30 | DDDSUDDDS<br>UU<br>S slot<br>=10DL:2GP:<br>2UL | 50 | 1 | 300 | 53.56 | 1 | 300  | 53.77 |
+| 2x64 SU-MIMO, Codebook based, OFDMA; gNB Config = (12,8,2,1,1;4,8)    | 30 | DDDDDDD<br>SUJ<br>S slot<br>=6DL:4GP:4<br>UL   | 50 | 1 | 500 | 56.53 | 1 | 500  | 56.77 |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15 | DSUUD<br>S slot<br>=11DL:1GP:<br>2UL           | 50 | / | /   | /     | 1 | 300  | 50.06 |
+| 4x32 SU-MIMO, Codebook based, OFDMA; gNB Config = (8,8,2,1,1;2,8)     | 15 | DDDSU<br>S slot<br>=10DL:2GP:<br>2UL           | 50 | / | /   | /     | 1 | 800  | 54.59 |
+
+##### 5.5.1.1.2 Evaluation configuration B (CF = 30 GHz)
+
+Void.
+
+##### 5.5.1.1.3 Evaluation configuration C
+
+For evaluation configuration C (multi-band), the UL user experienced data rate is evaluated using a TDD band (on 30 GHz) and a supplementary uplink (SUL) band (on 4 GHz). System level simulation is used. The “cell edge” users on TDD band are offloaded to SUL band. The evaluation results of NR TDD+SUL are provided in Table 5.5.1.1.3-1.
+
+In the evaluation, it is assumed that for FDD with 15 kHz SCS, a component carrier with 20 MHz is used; for TDD with 60 kHz SCS, a component carrier with 200 MHz is used. Multiple component carriers on either TDD band or SUL band are aggregated to achieve the UL target user experienced data rate. The assumed aggregated system bandwidth is given in Table 5.5.1.1.3-1.
+
+It is observed that NR can fulfill UL user experienced data rate requirement for the above configurations in evaluation configuration C.
+
+**Table 5.5.1.1.3-1 UL user experienced data rate for NR in Dense Urban – eMBB  
+(Evaluation configuration C)**
+
+###### **(a) NR TDD+SUL, Macro layer only**
+
+| Scheme and antenna configuration                                                                                                                                                                                                                        | Sub-carrier spacing         | Frame structure                                                | ITU Requirement [Mbps] | Channel model A   |                                         |                            | Channel model B   |                                         |                            |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------------------------------|------------------------|-------------------|-----------------------------------------|----------------------------|-------------------|-----------------------------------------|----------------------------|
+|                                                                                                                                                                                                                                                         |                             |                                                                |                        | Number of samples | Assumed system bandwidth [MHz]          | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz]          | User exp. data rate [Mbps] |
+| 4 GHz (SUL band): 2x32 SU-MIMO, Codebook based OFDMA gNB Config = (8,8,2,1,1; 2,8)<br><br>30 GHz (TDD band): 8x32 SU-MIMO, Codebook based, OFDMA (2 panel@UE) gNB Config = (4,8,2,2,2; 1,4) UE Config = (2,4,2,1,2; 1,2)<br><br>50% offload to SUL band | 4 GHz: 15<br><br>30 GHz: 60 | 4 GHz: full uplink;<br><br>30 GHz: DDDSU S slot =10DL:2GP:2 UL | 50                     | 1                 | 4 GHz: 100 (for UL)<br><br>30 GHz: 1200 | 53.13                      | 1                 | 4 GHz: 100 (for UL)<br><br>30 GHz: 1200 | 51.39                      |
+
+The DL user experienced data rate is evaluated using a TDD band (on 4GHz) with Macro layer and Micro layer. The evaluation results of NR are provided in Table 5.5.1.1.3-2.
+
+In the evaluation, it is assumed that for TDD with 30 kHz SCS, a component carrier with 20 MHz is used. Multiple component carriers on TDD band are aggregated to achieve the DL target user experienced data rate. The assumed aggregated system bandwidth is given in Table 5.5.1.1.3-2.
+
+It is observed that NR can fulfill DL user experienced data rate requirement for the above configurations in evaluation configuration C.
+
+**Table 5.5.1.1.3-2 DL user experienced data rate for NR in Dense Urban – eMBB  
+(Evaluation configuration C)**
+
+###### **(a) NR TDD band (4GHz), Macro layer + Micro layer**
+
+| Scheme and antenna configuration                                            | Sub-carrier spacing       | Frame structure                                    | ITU Requirement [Mbps] | Channel model A   |                                |                            | Channel model B   |                                |                            |
+|-----------------------------------------------------------------------------|---------------------------|----------------------------------------------------|------------------------|-------------------|--------------------------------|----------------------------|-------------------|--------------------------------|----------------------------|
+|                                                                             |                           |                                                    |                        | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] |
+| Macro and Micro layer : 32x4 MU-MIMO, 4T SRS; gNB Config = (8,8,2,1,1; 2,8) | Macro and Micro layer: 30 | Macro and Micro layer: DDDSU S slot =10DL:2GP:2 UL | 100                    | /                 | /                              | /                          | 1                 | 260                            | 127.66                     |
+
+### 5.5.2 LTE
+
+User experienced data rate for LTE are evaluated under Dense Urban – eMBB test environment.
+
+#### 5.5.2.1 Dense Urban – eMBB
+
+For Dense Urban – eMBB test environment, single-band single-layer case using evaluation configuration A (carrier frequency = 4 GHz) as defined in Report ITU-R M.2412 [6] is considered in evaluation. Detailed evaluation assumptions for configuration A are based on spectral efficiency evaluation, and can be found in Annex B.4.1.
+
+##### 5.5.2.1.1 Evaluation configuration A (CF = 4 GHz)
+
+For evaluation configuration A (single-band case), user experienced data rate for LTE is evaluated based on 5<sup>th</sup> percentile user spectral efficiency, using the analytical way as provided in Report ITU-R M.2412 [6].
+
+The evaluation results of DL user experienced data rate for LTE FDD and NR TDD for evaluation configuration A are provided in Table 5.5.2.1.1-1.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 20 MHz for FDD and TDD is used. Multiple component carriers are aggregated to achieve the DL target user experienced data rate. The assumed DL/UL aggregated system bandwidth (for FDD) or overall aggregated system bandwidth (for TDD) is given in Table 5.5.2.1.1-1.
+
+It is observed that both NR FDD and TDD fulfill the DL user experienced data rate requirement in evaluation configuration A.
+
+**Table 5.5.2.1.1-1 DL user experienced data rate for LTE in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### (a) LTE FDD
+
+| Scheme and antenna configuration                                  | Sub-carrier spacing | ITU Requirement [Mbps] | Channel model A   |                                   |                            | Channel model B   |                                   |                            |
+|-------------------------------------------------------------------|---------------------|------------------------|-------------------|-----------------------------------|----------------------------|-------------------|-----------------------------------|----------------------------|
+|                                                                   |                     |                        | Number of samples | Assumed DL system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed DL system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 32x4 MU-MIMO Advanced CSI Codebook; gNB Config = (8,8,2,1,1;2,8)  | 15                  | 100                    | 1                 | 360                               | 101.52                     | 1                 | 360                               | 101.52                     |
+| 32x4 MU-MIMO Advanced CSI Codebook; gNB Config = (16,8,2,1,1;2,8) | 15                  | 100                    | 1                 | 360                               | 105.48                     | 1                 | 360                               | 103.68                     |
+
+###### (b) LTE TDD
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing | Frame structure             | ITU Requirement [Mbps] | Channel model A   |                                |                            | Channel model B   |                                |                            |
+|------------------------------------------------------------------------|---------------------|-----------------------------|------------------------|-------------------|--------------------------------|----------------------------|-------------------|--------------------------------|----------------------------|
+|                                                                        |                     |                             |                        | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 64x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                  | DSUDD, S slot =10DL:2GP:2UL | 100                    | 1                 | 540                            | 102.21                     | 1                 | 520                            | 100.79                     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;2,8) | 15                  | DSUUD, S slot =11DL:1GP:2UL | 100                    | 1                 | 460                            | 100.19                     | 1                 | 480                            | 102.93                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (12,8,2,1,1;4,8) | 15                  | DSUUD, S slot =11DL:1GP:2UL | 100                    | 1                 | 360                            | 105.43                     | 1                 | 360                            | 102.38                     |
+| 64x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (16,8,2,1,1;4,8) | 15                  | DSUUD, S slot =11DL:1GP:2UL | 100                    | 1                 | 340                            | 100.53                     | 1                 | 340                            | 100.34                     |
+| 32x2 MU-MIMO, Reciprocity based; 2T SRS; gNB Config = (16,8,2,1,1;4,4) | 15                  | DSUUD, S slot =6DL:2GP:6UL  | 100                    | 1                 | 620                            | 102.39                     | 1                 | 600                            | 102.00                     |
+
+The evaluation results of UL user experienced data rate for LTE FDD and NR TDD for evaluation configuration A are provided in Table 5.5.2.1.1-2.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 20 MHz for FDD and TDD is used. Multiple component carriers are aggregated to achieve the UL target user experienced data rate. The assumed DL/UL aggregated system bandwidth (for FDD) or overall aggregated system bandwidth (for TDD) is given in Table 5.5.2.1.1-2.
+
+It is observed that both NR FDD and TDD fulfill the UL user experienced data rate requirement in evaluation configuration A.
+
+**Table 5.5.2.1.1-2 UL user experienced data rate for LTE in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration                        | Sub-carrier spacing | ITU Requirement [Mbps] | Channel model A   |                                   |                            | Channel model B   |                                   |                            |
+|---------------------------------------------------------|---------------------|------------------------|-------------------|-----------------------------------|----------------------------|-------------------|-----------------------------------|----------------------------|
+|                                                         |                     |                        | Number of samples | Assumed UL system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed UL system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 4x32 SU-MIMO, DFT-S-OFDM; gNB Config = (16,8,2,1,1;2,8) | 15                  | 50                     | 1                 | 140                               | 54.46                      | 1                 | 140                               | 56.98                      |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration                                        | Sub-carrier spacing | Frame structure                      | ITU Requirement [Mbps] | Channel model A   |                                |                            | Channel model B   |                                |                            |
+|-------------------------------------------------------------------------|---------------------|--------------------------------------|------------------------|-------------------|--------------------------------|----------------------------|-------------------|--------------------------------|----------------------------|
+|                                                                         |                     |                                      |                        | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] | Number of samples | Assumed system bandwidth [MHz] | User exp. data rate [Mbps] |
+| 4x32 SU-MIMO, Codebook based, DTF-S-OFDM; gNB Config = (16,8,2,1,1;2,8) | 15                  | DSUUD<br>S slot<br>=11DL:1GP:<br>2UL | 50                     | 1                 | 380                            | 50.00                      | 1                 | 360                            | 50.19                      |
+| 2x32 SU-MIMO, Codebook based, DTF-S-OFDM; gNB Config = (16,8,2,1,1;4,4) | 15                  | DSUUD<br>S slot<br>=6DL:2GP:6<br>UL  | 50                     | 1                 | 280                            | 53.04                      | 1                 | 320                            | 51.33                      |
+
+## 5.6 Area traffic capacity
+
+As defined in Report ITU-R M.2410 [4], area traffic capacity is the total traffic throughput served per geographic area (in Mbit/s/m<sup>2</sup>). The throughput is the number of correctly received bits, i.e. the number of bits contained in the SDUs delivered to Layer 3, over a certain period of time.
+
+### 5.6.1 NR
+
+NR evaluation for area traffic capacity is conducted for Indoor Hotspot – eMBB test environment. A wide range of antenna configurations and transmission schemes are considered. Detailed evaluation assumptions are according to spectral efficiency evaluation, which can be found in Annex B.4.1.
+
+#### 5.6.1.1 Indoor Hotspot – eMBB
+
+The area traffic capacity of NR is evaluated using analytical way based on the downlink average spectral efficiency evaluation for NR in Indoor Hotspot – eMBB test environment. The analytical way is defined in Report ITU-R M.2412 [6].
+
+##### 5.6.1.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of area traffic capacity for NR FDD and NR TDD for evaluation configuration A with 12TRxP are provided in Table 5.6.1.1.1-1.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 40 MHz is used; and for TDD with 30 kHz SCS, a component carrier with 100 MHz is used. Multiple component carriers are aggregated to achieve the target area traffic capacity. The assumed aggregated DL system bandwidth (for FDD) and overall system bandwidth (for TDD) are given in Table 5.6.1.1.1-1.
+
+**Table 5.6.1.1.1-1 Area traffic capacity for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 12TRxP)**
+
+###### (a) NR FDD
+
+| Scheme and antenna configuration                              | Sub-carrier spacing | ITU Requirement [Mbps/m <sup>2</sup> ] | Channel model A   |                                   |                                              | Channel model B   |                                   |                                              |
+|---------------------------------------------------------------|---------------------|----------------------------------------|-------------------|-----------------------------------|----------------------------------------------|-------------------|-----------------------------------|----------------------------------------------|
+|                                                               |                     |                                        | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+| 32x4 MU-MIMO Type II<br>Codebook gNB Config = (4,4,2,1,1;4,4) | 15                  | 10                                     | 10                | 400                               | 10.59                                        | 6                 | 400                               | 10.92                                        |
+| 32x4 MU-MIMO Type I<br>Codebook gNB Config = (4,4,2,1,1;4,4)  | 15                  | 10                                     | 1                 | 360                               | 10.06                                        | /                 | /                                 | /                                            |
+| 32x8 MU-MIMO Type II<br>Codebook gNB Config = (4,4,2,1,1;4,4) | 15                  | 10                                     | 2                 | 400                               | 10.05                                        | 1                 | 400                               | 10.38                                        |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing | Frame structure                | ITU Requirement [Mbps/m <sup>2</sup> ] | Channel model A   |                                |                                              | Channel model B   |                                |                                              |
+|-----------------------------------------------------------------------|---------------------|--------------------------------|----------------------------------------|-------------------|--------------------------------|----------------------------------------------|-------------------|--------------------------------|----------------------------------------------|
+|                                                                       |                     |                                |                                        | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (4,4,2,1,1;4,4) | 30                  | DDDSU; S slot = (10DL:2GP:2UL) | 10                                     | 1                 | 400                            | 11.67                                        | 3                 | 500                            | 11.64                                        |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS gNB Config = (4,4,2,1,1;4,4)  | 15                  | DDDSU; S slot = (10DL:2GP:2UL) | 10                                     | 1                 | 480                            | 10.65                                        | 1                 | 480                            | 10.64                                        |
+| 32x4 MU-MIMO, Type II Codebook based, gNB Config = (4,4,2,1,1;4,4)    | 15                  | DSUUD; S slot = (11DL:1GP:2UL) | 10                                     | 1                 | 600                            | 10.28                                        | 1                 | 600                            | 10.50                                        |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 30                  | DSUUD; S slot = (11DL:1GP:2UL) | 10                                     | 1                 | 600                            | 10.71                                        | 1                 | 600                            | 10.91                                        |
+
+|                                                                       |    |                                      |    |   |     |       |   |     |       |
+|-----------------------------------------------------------------------|----|--------------------------------------|----|---|-----|-------|---|-----|-------|
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 30 | DSUUD; S slot = (6DL:2GP :6UL)       | 10 | 1 | 700 | 10.04 | 1 | 700 | 10.46 |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 15 | DSUUD; S slot = (11DL:1GP :2UL)      | 10 | 3 | 680 | 10.33 | 3 | 680 | 10.44 |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 15 | DSUUD; S slot = (6DL:2GP :6UL)       | 10 | / | /   | /     | 1 | 760 | 10.00 |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 30 | DDDDD DDSUU; S slot = (6DL:4GP:4 UL) | 10 | 2 | 500 | 12.29 | 1 | 500 | 11.71 |
+| 32x8 MU-MIMO, Reciprocity based; 8T SRS, gNB Config = (4,4,2,1,1;4,4) | 15 | DSUUD; S slot = (6DL:2GP :6UL)       | 10 | 1 | 800 | 10.20 | / | /   | /     |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS, gNB Config = (4,4,2,1,1;4,4) | 30 | DDDSU DDSUU; S slot = (6DL:4GP:4 UL) | 10 | 1 | 600 | 11.96 | 1 | 500 | 10.17 |
+| 32x8 MU-MIMO, Type II Codebook based; gNB Config = (4,4,2,1,1;4,4)    | 30 | DDDSU; S slot = (10DL:2GP :2UL)      | 10 | 1 | 600 | 11.52 | 1 | 600 | 11.94 |
+
+The evaluation results of area traffic capacity for NR FDD and NR TDD for evaluation configuration A with 36TRxP are provided in Table 5.6.1.1.1-2.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 40 MHz is used; and for TDD with 30 kHz SCS, a component carrier with 100 MHz is used. Multiple component carriers are aggregated to achieve the DL target user experienced data rate. The assumed aggregated system bandwidth is given in Table 5.5.1.1.1-2.
+
+It is observed that both NR FDD and TDD fulfill the area traffic capacity requirement for all the above configurations in evaluation configuration A.
+
+**Table 5.6.1.1.1-2 Area traffic capacity for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 36TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration                            | Sub-carrier spacing | ITU Requirement [Mbps/m <sup>2</sup> ] | Channel model A   |                                   |                                              | Channel model B   |                                   |                                              |
+|-------------------------------------------------------------|---------------------|----------------------------------------|-------------------|-----------------------------------|----------------------------------------------|-------------------|-----------------------------------|----------------------------------------------|
+|                                                             |                     |                                        | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+| 32x4 MU-MIMO Type II Codebook gNB Config = (8,16,2,1,1;2,8) | 15                  | 10                                     | 7                 | 120                               | 10.66                                        | 4                 | 120                               | 11.42                                        |
+| 32x4 MU-MIMO Type I codebook gNB Config = (4,4,2,1,1;4,4)   | 15                  | 10                                     | 1                 | 160                               | 10.91                                        | /                 | /                                 | /                                            |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration                                       | Sub-carrier spacing | Frame structure                 | ITU Requirement [Mbps/m <sup>2</sup> ] | Channel model A   |                                |                                              | Channel model B   |                                |                                              |
+|------------------------------------------------------------------------|---------------------|---------------------------------|----------------------------------------|-------------------|--------------------------------|----------------------------------------------|-------------------|--------------------------------|----------------------------------------------|
+|                                                                        |                     |                                 |                                        | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS gNB Config = (8,16,2,1,1;2,8)  | 30                  | DDDSU; S Slot = (10DL:2GP, 2UL) | 10                                     | 2                 | 200                            | 14.85                                        | 2                 | 200                            | 15.04                                        |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS gNB Config = (8,16,2,1,1;2,8)  | 15                  | DDDSU; S Slot = (10DL:2GP, 2UL) | 10                                     | 1                 | 160                            | 12.15                                        | 1                 | 160                            | 12.24                                        |
+| 32x4 MU-MIMO, Type II Codebook based; gNB Config = (8,16,2,1,1;2,8)    | 15                  | DSUUD; S Slot = (6DL:2GP:6UL)   | 10                                     | 1                 | 280                            | 10.37                                        | /                 | /                              | /                                            |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,16,2,1,1;2,8) | 15                  | DSUUD; S Slot = (11DL:1GP: 2UL) | 10                                     | 2                 | 240                            | 11.28                                        | 2                 | 240                            | 11.47                                        |
+| 32x4 MU-MIMO, Reciprocity based; gNB Config = (8,16,2,1,1;2,8)         | 30                  | DSUUD; S Slot = (11DL:1GP: 2UL) | 10                                     | 1                 | 200                            | 11.28                                        | 1                 | 200                            | 11.43                                        |
+| 32x4 MU-MIMO, Reciprocity based; 4T SRS; gNB Config = (8,8,2,1,1;2,8)  | 30                  | DDDSU; S Slot = (10DL:2GP: 2UL) | 10                                     | 1                 | 200                            | 11.02                                        | 1                 | 200                            | 11.00                                        |
+
+##### **5.6.1.1.2 Evaluation configuration B (CF = 30 GHz)**
+
+The evaluation results of area traffic capacity for NR for evaluation configuration B with 12TRxP are provided in Table 5.6.1.1.2-1.
+
+It is assumed that for TDD with 60 kHz SCS, a component carrier with 200 MHz is used; and for TDD with 120 kHz SCS, a component carrier with 400 MHz is used. Multiple component carriers are aggregated to achieve the target area traffic capacity. The assumed aggregated system bandwidth is given in Table 5.6.1.1.2-1.
+
+**Table 5.6.1.1.2-1 Area traffic capacity for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 12TRxP)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                    | Sub-carrier spacing | Frame structure                | ITU Requirement [Mbps/m <sup>2</sup> ] | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+|---------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------|----------------------------------------|-------------------|--------------------------------|----------------------------------------------|
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (4,4,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,2)                       | 120                 | DDDSU; S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 800                            | 19.69                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (4,4,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,2)                       | 60                  | DDDSU; S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 600                            | 13.05                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (4,4,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,2)                       | 60                  | DDDSU; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 600                            | 13.59                                        |
+| 32x4 MU-MIMO, Type II Codebook based (2 panel@UE), gNB Config = (8,8,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,1)       | 120                 | DSUUD; S Slot = (6DL:2GP:2UL)  | 10                                     | 1                 | 1200                           | 12.55                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2)                       | 60                  | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 600                            | 11.57                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2)                       | 60                  | DSUUD; S Slot = (6DL:2GP:6UL)  | 10                                     | 1                 | 800                            | 11.72                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2)                       | 120                 | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 800                            | 15.93                                        |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;2,16); UE Config = (2,4,2,1,2; 1,2)  | 60                  | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 600                            | 13.02                                        |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;2,16); UE Config = (2,4,2,1,2; 1,2)  | 120                 | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 800                            | 17.98                                        |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS (1 panel at UE), gNB Config = (16,8,2,1,1;2,2); UE Config = (4,4,2,1,1; 1,2) | 120                 | DDDU                           | 10                                     | 1                 | 800                            | 17.96                                        |
+| 64x16 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (4,32,2,1,1;1,32); UE Config = (1,4,2,1,2; 1,4) | 60                  | DDDSU S Slot = (10DL:2GP:2UL)  | 10                                     | 1                 | 400                            | 10.22                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,2)                      | 120                 | DDDSU S Slot = (10DL:2GP:2UL)  | 10                                     | 1                 | 800                            | 15.76                                        |
+
+The evaluation results of area traffic capacity for NR for evaluation configuration B with 36TRxP are provided in Table 5.6.1.1.2-2.
+
+It is assumed that for TDD with 60 kHz SCS, a component carrier with 200 MHz is used; and for TDD with 120 kHz SCS, a component carrier with 400 MHz is used. Multiple component carriers are aggregated to achieve the target area traffic capacity. The assumed aggregated system bandwidth is given in Table 5.6.1.1.2-2.
+
+It is observed that both NR fulfills the area traffic capacity requirement for all the above configurations in evaluation configuration B.
+
+**Table 5.6.1.1.2-2 Area traffic capacity for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 36TRxP)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                   | Sub-carrier spacing | Frame structure                | ITU Requirement [Mbps/m <sup>2</sup> ] | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+|--------------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------|----------------------------------------|-------------------|--------------------------------|----------------------------------------------|
+| 32x4 MU-MIMO, Type II Codebook (2 panel@UE), gNB Config = (8,8,2,1,1;4,4); UE Config = (2,4,2,1,2; 1,1)            | 120                 | DSUUD; S Slot = (6DL:2GP:6UL)  | 10                                     | 1                 | 400                            | 12.86                                        |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2)   | 60                  | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 400                            | 19.77                                        |
+| 32x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,8,2,1,1;2,8); UE Config = (2,4,2,1,2; 1,2)   | 120                 | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 400                            | 19.39                                        |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;2,16); UEConfig = (2,4,2,1,2; 1,2)  | 60                  | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 200                            | 11.54                                        |
+| 64x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;2,16); UE Config = (2,4,2,1,2; 1,2) | 120                 | DSUUD; S Slot = (11DL:1GP:2UL) | 10                                     | 1                 | 400                            | 22.76                                        |
+
+### 5.6.2 LTE
+
+LTE evaluation for area traffic capacity is conducted for Indoor Hotspot – eMBB test environment. A wide range of antenna configurations and transmission schemes are considered. Detailed evaluation assumptions are according to spectral efficiency evaluation, which can be found in Annex B.4.1.
+
+#### 5.6.2.1 Indoor Hotspot – eMBB
+
+The area traffic capacity of LTE is evaluated using analytical way based on the downlink average spectral efficiency evaluation for LTE in Indoor Hotspot – eMBB test environment. The analytical way is defined in Report ITU-R M.2412 [6].
+
+##### 5.6.2.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of area traffic capacity for LTE FDD and LTE TDD for evaluation configuration A with 12TRxP are provided in Table 5.6.2.1.1-1.
+
+It is assumed that for FDD and TDD with 15 kHz SCS, a component carrier with 20 MHz for FDD and TDD is used. The assumed aggregated DL system bandwidth (for FDD) and overall system bandwidth (for TDD) are given in Table 5.6.2.1.1-1.
+
+**Table 5.6.2.1.1-1 Area traffic capacity for LTE in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 12TRxP)**
+
+**(a) LTE FDD**
+
+| Scheme and antenna configuration                                            | Sub-carrier spacing | ITU Requirement [Mbps/m <sup>2</sup> ] | Channel model A   |                                   |                                              | Channel model B   |                                   |                                              |
+|-----------------------------------------------------------------------------|---------------------|----------------------------------------|-------------------|-----------------------------------|----------------------------------------------|-------------------|-----------------------------------|----------------------------------------------|
+|                                                                             |                     |                                        | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] | Number of samples | Assumed DL system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+| 32x4 MU-MIMO<br>Advanced CSI<br>Codebook<br>gNB Config =<br>(4,4,2,1,1;4,4) | 15                  | 10                                     | 1                 | 520                               | 10.20                                        | 1                 | 520                               | 10.25                                        |
+
+## 5.7 Latency
+
+### 5.7.1 User plane latency
+
+As defined in Report ITU-R M.2410 [4], user plane latency is the contribution of the radio network to the time from when the source sends a packet to when the destination receives it (in ms).
+
+#### 5.7.1.1 NR
+
+The evaluation of NR user plane latency is based on the procedure illustrated in Figure 5.7.1.1-1.
+
+![Figure 5.7.1.1-1 User plane procedure for evaluation. The diagram shows a Base Station (BS) and a User Equipment (UE) with arrows indicating the flow of data and timing components. For the downlink (BS to UE), the total latency is the sum of transmission delay at the BS (t_BS,tx), air interface delay (t_FA,DL), data duration (t_data_duration), and reception delay at the UE (t_UE,rx). For the uplink (UE to BS), the total latency is the sum of transmission delay at the UE (t_UE,tx), air interface delay (t_FA,UL), data duration (t_data_duration), and reception delay at the BS (t_BS,rx). A HARQ RTT (Round Trip Time) is shown as a double-headed arrow between the BS and UE.](236f674770a03c918c0375a74fe950db_img.jpg)
+
+Figure 5.7.1.1-1 User plane procedure for evaluation. The diagram shows a Base Station (BS) and a User Equipment (UE) with arrows indicating the flow of data and timing components. For the downlink (BS to UE), the total latency is the sum of transmission delay at the BS (t\_BS,tx), air interface delay (t\_FA,DL), data duration (t\_data\_duration), and reception delay at the UE (t\_UE,rx). For the uplink (UE to BS), the total latency is the sum of transmission delay at the UE (t\_UE,tx), air interface delay (t\_FA,UL), data duration (t\_data\_duration), and reception delay at the BS (t\_BS,rx). A HARQ RTT (Round Trip Time) is shown as a double-headed arrow between the BS and UE.
+
+**Figure 5.7.1.1-1 User plane procedure for evaluation**
+
+The detailed assumptions of each step are provided in Table 5.7.1.1.1-1 and Table 5.7.1.1.2-1 for downlink and uplink, respectively.
+
+The additional assumptions to derive the evaluation results of NR user plane latency are list as below.
+
+- It is assumed that the packet arrives at any time of any OFDM symbol. In this case, the 0.5symbol length is added as the “average symbol alignment time” at the beginning of the procedure.
+
+- The transmission of PDCCH, PDSCH, PUCCH, PUSCH cannot be across the slot. Otherwise the transmission will wait for the next slot.
+- The PDSCH/PUSCH allocation (transmission duration) of 2/4/7/14-OFDM symbols non-slot or slot are evaluated.
+  - If the evaluation is for 14 OFDM Symbol length slot, then slot based scheduling is used.
+  - Otherwise non-slot based scheduling is used.
+- The resource mapping type A and B are considered, which impact the start timing of a transmission. Details on resource mapping mechanism can be found in TS 38.214 [9].
+- It is assumed that PDCCH monitoring occasion occurs at every OFDM symbol in the evaluation.
+
+##### 5.7.1.1.1 Downlink
+
+The downlink procedure is abstracted in Table 5.7.1.1.1-1, where the assumptions of each step for evaluation are given.
+
+Table 5.7.1.1.1-1 DL user plane procedure for NR
+
+| ID  | Component                                   | Notations                                                                                                       | Value                                                                                                                                                                                                                                        |
+|-----|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | DL data transfer                            | $T_1 = (t_{BS,tx} + t_{FA,DL}) + t_{DL\_duration} + t_{UE,rx}$                                                  |                                                                                                                                                                                                                                              |
+| 1.1 | BS processing delay                         | $t_{BS,tx}$<br>The time interval between the data is arrived, and packet is generated.                          | $T_{proc,2}/2$ , with $d_{2,1}= d_{2,2}= d_{2,3}=0$ . ( $T_{proc,2}$ is defined in Section 6.4 of TS38.214) (NOTE1, NOTE2)                                                                                                                   |
+| 1.2 | DL Frame alignment (transmission alignment) | $t_{FA,DL}$<br>It includes frame alignment time, and the waiting time for next available DL slot                | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current DL slot;<br>$T_{wait}$ is the waiting time for next available DL slot if the current slot is not DL slot.                                                   |
+| 1.3 | TTI for DL data packet transmission         | $t_{DL\_duration}$                                                                                              | Length of one slot (14 OFDM symbol length) or non-slot (2/4/7 OFDM symbol length), depending on slot or non-slot selected in evaluation.                                                                                                     |
+| 1.4 | UE processing delay                         | $t_{UE,rx}$<br>The time interval between the PDSCH is received and the data is decoded;                         | $T_{proc,1}/2$ ( $T_{proc,1}$ is defined in Section 5.3 of TS38.214), $d_{1,1}=0$ ; $d_{1,2}$ should be selected according to resource mapping type and UE capability. $N_1$ =the value with “No additional PDSCH DM-RS configured”. (NOTE3) |
+| 2   | HARQ retransmission                         | $T_{HARQ} = T_1 + T_2$<br>$T_2 = (t_{UE,tx} + t_{FA,UL}) + t_{UL\_duration} + t_{BS,rx}$ (For Steps 2.1 to 2.4) |                                                                                                                                                                                                                                              |
+| 2.1 | UE processing delay                         | $t_{UE,tx}$<br>The time interval between the data is decoded, and ACK/NACK packet is generated.                 | $T_{proc,1}/2$ ( $T_{proc,1}$ is defined in Section 5.3 of TS38.214), $d_{1,1}=0$ ; $d_{1,2}$ should be selected according to resource mapping type and UE capability. $N_1$ =the value with “No additional PDSCH DM-RS configured”. (NOTE4) |
+| 2.2 | UL frame alignment (transmission alignment) | $t_{FA,UL}$<br>It includes frame alignment time, and the waiting time for the next available UL slot            | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current UL slot;<br>$T_{wait}$ is the waiting time for next available UL slot if the current slot is not UL slot                                                    |
+| 2.3 | TTI for ACK/NACK transmission               | $t_{UL\_duration}$                                                                                              | 1 OFDM symbol                                                                                                                                                                                                                                |
+| 2.4 | BS processing delay                         | $t_{BS,rx}$<br>The time interval between the ACK is received and the ACK is decoded.                            | $T_{proc,2}/2$ with $d_{2,1}= d_{2,2}= d_{2,3}=0$ . (NOTE1, NOTE5)                                                                                                                                                                           |
+| 2.5 | Repeat DL data transfer from 1.1 to 1.4     | $T_1$                                                                                                           |                                                                                                                                                                                                                                              |
+| -   | Total one way user plane latency for DL     | $T_{UP} = T_1 + n \times T_{HARQ}$<br>where $n$ is the number of re-transmissions ( $n \geq 0$ )                |                                                                                                                                                                                                                                              |
+
+Note:  
+1. The value is used for evaluation only; gNB processing delay may vary depending on implementation.  
+2. For the case of a TDD band (30 kHz SCS) with an SUL band (15 kHz SCS), the value of this step is  $T_{proc,2}(\mu=30kHz) / 2$  for Initial transmission, and  $T_{proc,2}(\mu=15kHz) / 2$  for re-transmission.  
+3. For the above case, the UE is processing PDSCH reception on TDD band with 30kHz SCS, and it is assumed that the value of this step is  $T_{proc,1}(\mu=30kHz)/2$ .  
+4. For the above case, the value of this step is  $T_{proc,1}(\mu=15kHz) - T_{proc,1}(\mu=30kHz)/2$ .  
+5. For the above case, the value of this step is  $T_{proc,2}(\mu=15kHz)/2$ .
+
+Based on the DL user plane procedure and assumptions given in Table 5.7.1.1.1-1, a variety of configurations and UE capabilities are evaluated for NR.
+
+For NR FDD, the evaluation results assuming an initial transmission error probability of  $p=0$  and  $p=0.1$  are provided in Table 5.7.1.1.1-2.
+
+Table 5.7.1.1.1-2 DL user plane latency for NR FDD (ms)
+
+| DL user plane latency – NR FDD |           |     | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|--------------------------------|-----------|-----|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                |           |     | SCS             |        |        |         | SCS             |        |        |
+|                                |           |     | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| Resource                       | M=4 (4OS) | p=0 | 1.37            | 0.76   | 0.54   | 0.34    | 1.00            | 0.55   | 0.36   |
+
+|                                |                    |       |      |      |      |      |      |      |      |
+|--------------------------------|--------------------|-------|------|------|------|------|------|------|------|
+| <b>mapping Type A</b>          | non-slot)          | p=0.1 | 1.58 | 0.87 | 0.64 | 0.40 | 1.12 | 0.65 | 0.41 |
+|                                | M=7 (7OS non-slot) | p=0   | 1.49 | 0.82 | 0.57 | 0.36 | 1.12 | 0.61 | 0.39 |
+|                                |                    | p=0.1 | 1.70 | 0.93 | 0.67 | 0.42 | 1.25 | 0.71 | 0.44 |
+|                                | M=14 (14OS slot)   | p=0   | 2.13 | 1.14 | 0.72 | 0.44 | 1.80 | 0.94 | 0.56 |
+|                                |                    | p=0.1 | 2.43 | 1.29 | 0.82 | 0.51 | 2.00 | 1.04 | 0.63 |
+| <b>Resource mapping Type B</b> | M=2 (2OS non-slot) | p=0   | 0.98 | 0.56 | 0.44 | 0.29 | 0.49 | 0.29 | 0.23 |
+|                                |                    | p=0.1 | 1.16 | 0.67 | 0.52 | 0.35 | 0.60 | 0.35 | 0.28 |
+|                                | M=4 (4OS non-slot) | p=0   | 1.11 | 0.63 | 0.47 | 0.31 | 0.66 | 0.37 | 0.27 |
+|                                |                    | p=0.1 | 1.30 | 0.74 | 0.56 | 0.36 | 0.78 | 0.45 | 0.32 |
+|                                | M=7 (7OS non-slot) | p=0   | 1.30 | 0.72 | 0.52 | 0.33 | 0.93 | 0.51 | 0.34 |
+|                                |                    | p=0.1 | 1.49 | 0.83 | 0.61 | 0.39 | 1.08 | 0.59 | 0.40 |
+
+For NR TDD, the various DL/UL configurations are evaluated. The evaluation results of DDDSU (with S slot = 11DL:1GP:2UL), DSUUD (with S slot = 11DL:1GP:2UL), and DUDU (without GP) are provided in Table 5.7.1.1.1-3, Table 5.7.1.1.1-4, and Table 5.7.1.1.1-5, respectively.
+
+**Table 5.7.1.1.1-3 DL user plane latency for NR TDD (ms)**  
+(Frame structure: DDDSU)
+
+| DL user plane latency – NR TDD (DDDSU) |                    |       | UE capability 1 |        |        | UE capability 2 |        |        |
+|----------------------------------------|--------------------|-------|-----------------|--------|--------|-----------------|--------|--------|
+|                                        |                    |       | SCS             |        |        | SCS             |        |        |
+|                                        |                    |       | 15 kHz          | 30 kHz | 60 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>         | M=4 (4OS non-slot) | p=0   | 1.57            | 0.86   | 0.58   | 1.18            | 0.65   | 0.40   |
+|                                        |                    | p=0.1 | 1.95            | 1.05   | 0.70   | 1.56            | 0.84   | 0.50   |
+|                                        | M=7 (7OS non-slot) | p=0   | 1.69            | 0.92   | 0.61   | 1.30            | 0.71   | 0.43   |
+|                                        |                    | p=0.1 | 2.07            | 1.11   | 0.73   | 1.67            | 0.90   | 0.53   |
+|                                        | M=14 (14OS slot)   | p=0   | 2.38            | 1.26   | 0.78   | 1.99            | 1.06   | 0.60   |
+|                                        |                    | p=0.1 | 2.78            | 1.46   | 0.93   | 2.37            | 1.25   | 0.70   |
+| <b>Resource mapping Type B</b>         | M=2 (2OS non-slot) | p=0   | 1.16            | 0.65   | 0.48   | 0.66            | 0.39   | 0.27   |
+|                                        |                    | p=0.1 | 1.52            | 0.83   | 0.59   | 1.02            | 0.57   | 0.36   |
+|                                        | M=4 (4OS non-slot) | p=0   | 1.28            | 0.71   | 0.51   | 0.82            | 0.47   | 0.31   |
+|                                        |                    | p=0.1 | 1.64            | 0.90   | 0.63   | 1.17            | 0.65   | 0.40   |
+|                                        | M=7 (7OS non-slot) | p=0   | 1.49            | 0.82   | 0.56   | 1.10            | 0.61   | 0.38   |
+|                                        |                    | p=0.1 | 1.86            | 1.01   | 0.69   | 1.47            | 0.80   | 0.47   |
+
+**Table 5.7.1.1.1-4 DL user plane latency for NR TDD (ms)**  
+(Frame structure: DSUUD)
+
+| DL user plane latency – NR TDD (DSUUD) |                    |       | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|----------------------------------------|--------------------|-------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                        |                    |       | SCS             |        |        |         | SCS             |        |        |
+|                                        |                    |       | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>         | M=4 (4OS non-slot) | p=0   | 1.93            | 1.04   | 0.68   | 0.41    | 1.56            | 0.82   | 0.48   |
+|                                        |                    | p=0.1 | 2.37            | 1.26   | 0.78   | 0.48    | 1.99            | 1.04   | 0.59   |
+|                                        | M=7 (7OS non-slot) | p=0   | 2.05            | 1.1    | 0.71   | 0.43    | 1.69            | 0.88   | 0.53   |
+|                                        |                    | p=0.1 | 2.49            | 1.32   | 0.83   | 0.5     | 2.13            | 1.1    | 0.64   |
+|                                        | M=14 (14OS slot)   | p=0   | 2.74            | 1.44   | 0.88   | 0.51    | 2.39            | 1.23   | 0.7    |
+|                                        |                    | p=0.1 | 3.19            | 1.66   | 1      | 0.58    | 2.83            | 1.45   | 0.81   |
+| <b>Resource mapping Type B</b>         | M=2 (2OS non-slot) | p=0   | 1.47            | 0.81   | 0.56   | 0.35    | 1.01            | 0.54   | 0.36   |
+|                                        |                    | p=0.1 | 1.9             | 1.02   | 0.67   | 0.41    | 1.43            | 0.75   | 0.47   |
+|                                        | M=4 (4OS non-slot) | p=0   | 1.59            | 0.87   | 0.59   | 0.37    | 1.16            | 0.62   | 0.4    |
+|                                        |                    | p=0.1 | 2.01            | 1.08   | 0.7    | 0.43    | 1.58            | 0.83   | 0.5    |
+|                                        | M=7 (7OS non-slot) | p=0   | 1.83            | 0.99   | 0.65   | 0.4     | 1.47            | 0.77   | 0.48   |
+|                                        |                    | p=0.1 | 2.26            | 1.2    | 0.76   | 0.46    | 1.9             | 0.99   | 0.58   |
+
+**Table 5.7.1.1.1-5 DL user plane latency for NR TDD (ms)**  
+**(Frame structure: DUDU)**
+
+| DL user plane latency – NR TDD (DU) |                    |       | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|-------------------------------------|--------------------|-------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                     |                    |       | SCS             |        |        |         | SCS             |        |        |
+|                                     |                    |       | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>      | M=4 (4OS non-slot) | p=0   | 1.83            | 1.00   | 0.64   | 0.40    | 1.47            | 0.77   | 0.48   |
+|                                     |                    | p=0.1 | 2.04            | 1.11   | 0.73   | 0.48    | 1.66            | 0.87   | 0.52   |
+|                                     | M=7 (7OS non-slot) | p=0   | 1.94            | 1.04   | 0.65   | 0.41    | 1.59            | 0.83   | 0.50   |
+|                                     |                    | p=0.1 | 2.16            | 1.16   | 0.75   | 0.49    | 1.79            | 0.93   | 0.55   |
+|                                     | M=14 (14OS slot)   | p=0   | 2.61            | 1.38   | 0.83   | 0.50    | 2.29            | 1.18   | 0.68   |
+|                                     |                    | p=0.1 | 2.96            | 1.55   | 0.96   | 0.58    | 2.49            | 1.29   | 0.78   |
+| <b>Resource mapping Type B</b>      | M=2 (2OS non-slot) | p=0   | 1.27            | 0.71   | 0.51   | 0.33    | 0.76            | 0.42   | 0.30   |
+|                                     |                    | p=0.1 | 1.46            | 0.81   | 0.61   | 0.39    | 0.99            | 0.53   | 0.36   |
+|                                     | M=4 (4OS non-slot) | p=0   | 1.46            | 0.80   | 0.56   | 0.35    | 0.98            | 0.54   | 0.36   |
+|                                     |                    | p=0.1 | 1.65            | 0.91   | 0.66   | 0.41    | 1.22            | 0.65   | 0.41   |
+|                                     | M=7 (7OS non-slot) | p=0   | 1.71            | 0.93   | 0.63   | 0.38    | 1.32            | 0.71   | 0.44   |
+|                                     |                    | p=0.1 | 1.91            | 1.03   | 0.73   | 0.46    | 1.55            | 0.81   | 0.50   |
+
+In addition, NR supports X slot that can be flexibly configured based on the traffic pattern. The evaluation of DDXU is provided for this capability, where ‘X’ slot = ‘D’ slot for DL data transmission, and ‘X’=‘U’ for ACK/NACK feedback for DL user plane latency evaluation. The evaluation results are provided in Table 5.7.1.1.1-6.
+
+**Table 5.7.1.1.1-6 DL user plane latency for NR TDD (ms)**  
+**(Frame structure: DDXU, with ‘X’=‘D’ for DL traffic)**
+
+| DL user plane latency – NR TDD (DDXU) |                    |       | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|---------------------------------------|--------------------|-------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                       |                    |       | SCS             |        |        |         | SCS             |        |        |
+|                                       |                    |       | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>        | M=14 (14OS slot)   | p=0   | 2.34            | 1.24   | 0.79   | 0.46    | 2.02            | 1.04   | 0.61   |
+|                                       |                    | p=0.1 | 2.74            | 1.44   | 0.92   | 0.54    | 2.40            | 1.23   | 0.71   |
+| <b>Resource mapping Type B</b>        | M=2 (2OS non-slot) | p=0   | 1.09            | 0.62   | 0.48   | 0.31    | 0.66            | 0.36   | 0.27   |
+|                                       |                    | p=0.1 | 1.37            | 0.80   | 0.59   | 0.37    | 0.88            | 0.47   | 0.34   |
+|                                       | M=4 (4OS non-slot) | p=0   | 1.25            | 0.69   | 0.52   | 0.33    | 0.85            | 0.45   | 0.32   |
+|                                       |                    | p=0.1 | 1.61            | 0.88   | 0.63   | 0.39    | 1.09            | 0.58   | 0.41   |
+|                                       | M=7 (7OS non-slot) | p=0   | 1.46            | 0.80   | 0.57   | 0.35    | 1.17            | 0.61   | 0.40   |
+|                                       |                    | p=0.1 | 1.83            | 0.99   | 0.68   | 0.42    | 1.42            | 0.74   | 0.49   |
+
+NR also supports the use of supplementary uplink (SUL) band together with a TDD band, where continuous uplink transmission opportunity becomes possible. The evaluation is applied to a TDD band with DDSU (with S slot = 11DL:1GP:2UL) together with an SUL band. The evaluation results are provided in Table 5.7.1.1.1-7.
+
+**Table 5.7.1.1.1-7 DL user plane latency for NR TDD + SUL (ms)**  
+**(Frame structure for TDD carrier: DDSU)**
+
+| DL user plane latency – NR TDD (DDSU) + SUL |                    |       | UE capability 1             |                             |                             |                             | UE capability 2             |                             |  |
+|---------------------------------------------|--------------------|-------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|--|
+|                                             |                    |       | SCS                         |                             |                             |                             | SCS                         |                             |  |
+|                                             |                    |       | 15 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) | 15 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) |  |
+| <b>Resource mapping Type A</b>              | M=4 (4OS non-slot) | p=0   | 1.57                        | 0.86                        | 0.86                        | 1.18                        | 0.65                        | 0.65                        |  |
+|                                             |                    | p=0.1 | 1.79                        | 1.03                        | 0.97                        | 1.30                        | 0.76                        | 0.76                        |  |
+|                                             | M=7 (7OS non-slot) | p=0   | 1.69                        | 0.92                        | 0.92                        | 1.30                        | 0.71                        | 0.71                        |  |
+|                                             |                    | p=0.1 | 1.91                        | 1.13                        | 1.04                        | 1.44                        | 0.82                        | 0.82                        |  |
+|                                             | M=14 (14OS slot)   | p=0   | 2.38                        | 1.26                        | 1.26                        | 1.99                        | 1.06                        | 1.06                        |  |
+|                                             |                    | p=0.1 | 2.70                        | 1.48                        | 1.42                        | 2.21                        | 1.22                        | 1.17                        |  |
+| <b>Resource mapping Type B</b>              | M=2 (2OS non-slot) | p=0   | 1.16                        | 0.65                        | 0.65                        | 0.66                        | 0.39                        | 0.39                        |  |
+|                                             |                    | p=0.1 | 1.35                        | 0.83                        | 0.76                        | 0.76                        | 0.48                        | 0.45                        |  |
+|                                             | M=4 (4OS non-slot) | p=0   | 1.28                        | 0.71                        | 0.71                        | 0.82                        | 0.47                        | 0.47                        |  |
+|                                             |                    | p=0.1 | 1.49                        | 0.89                        | 0.83                        | 0.93                        | 0.57                        | 0.54                        |  |
+|                                             | M=7 (7OS non-slot) | p=0   | 1.49                        | 0.82                        | 0.82                        | 1.10                        | 0.61                        | 0.61                        |  |
+|                                             |                    | p=0.1 | 1.71                        | 0.99                        | 0.94                        | 1.23                        | 0.72                        | 0.69                        |  |
+
+It is observed that NR fulfils DL user plane latency requirement in a wide range of configurations.
+
+##### 5.7.1.1.2 Uplink
+
+The uplink procedure using a grant free transmission is abstracted in Table 5.7.1.1.2-1, where the assumptions of each step for evaluation are given.
+
+Table 5.7.1.1.2-1 UL user plane procedure for NR
+
+| Step                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Component                                   | Notations                                                                                                       | Value                                                                                                                                                                                                                                                                                                                                 |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | UL data transfer                            | $T_1 = (t_{UE,tx} + t_{FA,UL}) + t_{UL\_duration} + t_{BS,rx}$                                                  |                                                                                                                                                                                                                                                                                                                                       |
+| 1.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | UE processing delay                         | $t_{UE,tx}$<br>The time interval between the data is arrived, and packet is generated;                          | $T_{proc,2}/2$ ( $T_{proc,2}$ is defined in Section 6.4 of TS38.214), with $d_{2,1} = d_{2,2} = d_{2,3} = 0$                                                                                                                                                                                                                          |
+| 1.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | UL Frame alignment (transmission alignment) | $t_{FA,UL}$<br>It includes frame alignment time, and the waiting time for next available UL slot                | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current UL slot,<br>$T_{wait}$ is the waiting time for next available UL slot if the current slot is not UL slot.                                                                                                                                            |
+| 1.3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TTI for UL data packet transmission         | $t_{UL\_duration}$                                                                                              | Length of one slot (14 OFDM symbol length) or non-slot (2/4/7 OFDM symbol length), depending on slot or non-slot selected in evaluation.                                                                                                                                                                                              |
+| 1.4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | BS processing delay                         | $t_{BS,rx}$<br>The time interval between the PUSCH is received and the data is decoded;                         | $T_{proc,1}/2$ ( $T_{proc,1}$ is defined in Section 5.3 of TS38.214), $d_{1,1} = 0$ ; $d_{1,2}$ should be selected according to resource mapping type and UE capability.<br>$N_1$ =the value with “No additional PDSCH DM-RS configured”; It is assumed that BS processing delay is equal to UE processing delay as for PDSCH (Note1) |
+| 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | HARQ retransmission                         | $T_{HARQ} = T_2 + T_1$<br>$T_2 = (t_{BS,tx} + t_{FA,DL}) + t_{DL\_duration} + t_{UE,rx}$ (For Steps 2.1 to 2.4) |                                                                                                                                                                                                                                                                                                                                       |
+| 2.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | BS processing delay                         | $t_{BS,tx}$<br>The time interval between the data is decoded, and PDCCH preparation                             | $T_{proc,1}/2$ ( $T_{proc,1}$ is defined in Section 5.3 of TS38.214), $d_{1,1} = 0$ ; $d_{1,2}$ should be selected according to resource mapping type and UE capability.<br>$N_1$ =the value with “No additional PDSCH DM-RS configured”.                                                                                             |
+| 2.2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | DL Frame alignment (transmission alignment) | $t_{FA,DL}$<br>It includes frame alignment time, and the waiting time for next available DL slot                | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current DL slot;<br>$T_{wait}$ is the waiting time for next available DL slot if the current slot is not DL slot;                                                                                                                                            |
+| 2.3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | TTI for PDCCH transmission                  | $t_{DL\_duration}$                                                                                              | 1 OFDM symbols for PDCCH scheduling the retransmission.                                                                                                                                                                                                                                                                               |
+| 2.4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | UE processing delay                         | $t_{UE,rx}$<br>The time interval between the PDCCH is received and decoded.                                     | $T_{proc,2}/2$ ( $T_{proc,2}$ is defined in Section 6.4 of TS38.214), with $d_{2,1} = d_{2,2} = d_{2,3} = 0$                                                                                                                                                                                                                          |
+| 2.5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Repeat UL data transfer from 1.1 to 1.4     | $T_1$                                                                                                           |                                                                                                                                                                                                                                                                                                                                       |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Total one way user plane latency for UL     | $T_{UP} = T_1 + n \times T_{HARQ}$<br>where $n$ is the number of re-transmissions ( $n \geq 0$ )                |                                                                                                                                                                                                                                                                                                                                       |
+| Note:<br>1. The value is used for evaluation only; gNB processing delay may vary depending on implementation.<br>Note:<br>2. The grant free transmission is assumed to use the following start symbols:<br>For 2-symbol PUSCH, the start symbol can be symbols {0,2,4,6,8,10,12} for PUSCH resource mapping type B<br>For 4-symbol PUSCH, the start symbol can be:<br>For PUSCH resource mapping type B: symbols {0,7}<br>For PUSCH resource mapping type A: symbol 0;<br>For 7-symbol PUSCH, the start symbol can be:<br>For PUSCH resource mapping type B: symbols {0, 7}<br>For PUSCH resource mapping type A: symbol 0;<br>For 14-symbol PUSCH, the start symbol can be at symbol #0 for PUSCH resource mapping type A and B. |                                             |                                                                                                                 |                                                                                                                                                                                                                                                                                                                                       |
+
+Based on the UL user plane procedure and assumptions given in Table 5.7.1.1.2-1, a variety of configurations and UE capabilities are evaluated for NR.
+
+For NR FDD, the evaluation results assuming an initial transmission error probability of  $p=0$  and  $p=0.1$  are provided in Table 5.7.1.1.2-2.
+
+**Table 5.7.1.1.2-2 UL user plane latency for NR FDD with grant free transmission (ms)**
+
+| UL user plane latency (Grant free) – NR FDD |                    |         | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|---------------------------------------------|--------------------|---------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                             |                    |         | SCS             |        |        |         | SCS             |        |        |
+|                                             |                    |         | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>              | M=4 (4OS non-slot) | $p=0$   | 1.57            | 0.86   | 0.59   | 0.37    | 1.20            | 0.65   | 0.41   |
+|                                             |                    | $p=0.1$ | 1.78            | 1.01   | 0.69   | 0.43    | 1.39            | 0.75   | 0.47   |
+|                                             | M=7 (7OS non-slot) | $p=0$   | 1.68            | 0.91   | 0.61   | 0.38    | 1.30            | 0.70   | 0.43   |
+|                                             |                    | $p=0.1$ | 1.89            | 1.06   | 0.71   | 0.44    | 1.50            | 0.80   | 0.49   |
+|                                             | M=14 (14OS slot)   | $p=0$   | 2.15            | 1.15   | 0.73   | 0.44    | 1.80            | 0.94   | 0.56   |
+|                                             |                    | $p=0.1$ | 2.45            | 1.30   | 0.84   | 0.51    | 2.00            | 1.06   | 0.63   |
+| <b>Resource mapping Type B</b>              | M=2 (2OS non-slot) | $p=0$   | 0.96            | 0.55   | 0.44   | 0.28    | 0.52            | 0.30   | 0.24   |
+|                                             |                    | $p=0.1$ | 1.14            | 0.65   | 0.52   | 0.34    | 0.62            | 0.36   | 0.28   |
+|                                             | M=4 (4OS non-slot) | $p=0$   | 1.31            | 0.72   | 0.52   | 0.33    | 0.79            | 0.43   | 0.30   |
+|                                             |                    | $p=0.1$ | 1.50            | 0.84   | 0.61   | 0.39    | 0.96            | 0.55   | 0.37   |
+|                                             | M=7 (7OS non-slot) | $p=0$   | 1.40            | 0.77   | 0.55   | 0.34    | 1.02            | 0.55   | 0.36   |
+|                                             |                    | $p=0.1$ | 1.60            | 0.89   | 0.63   | 0.40    | 1.19            | 0.64   | 0.42   |
+|                                             | M=14 (14OS slot)   | $p=0$   | 2.14            | 1.14   | 0.74   | 0.44    | 1.81            | 0.93   | 0.56   |
+|                                             |                    | $p=0.1$ | 2.44            | 1.30   | 0.84   | 0.51    | 2.01            | 1.03   | 0.63   |
+
+For NR TDD, the various DL/UL configurations are evaluated. The evaluation results of DDDSU (with S slot = 11DL:1GP:2UL), DSUUD (with S slot = 11DL:1GP:2UL), and DUDU (without GP) are provided in Table 5.7.1.1.1-3, Table 5.7.1.1.1-4, and Table 5.7.1.1.1-5, respectively.
+
+**Table 5.7.1.1.2-3 UL user plane latency for NR TDD with grant free transmission (ms)  
+(Frame structure: DDDSU)**
+
+| UL user plane latency – NR TDD (DDDSU) |                    |         | UE capability 1 |        |        | UE capability 2 |        |        |
+|----------------------------------------|--------------------|---------|-----------------|--------|--------|-----------------|--------|--------|
+|                                        |                    |         | SCS             |        |        | SCS             |        |        |
+|                                        |                    |         | 15 kHz          | 30 kHz | 60 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>         | M=4 (4OS non-slot) | $p=0$   | 3.57            | 1.86   | 1.08   | 3.18            | 1.65   | 0.90   |
+|                                        |                    | $p=0.1$ | -               | 2.11   | 1.21   | 3.68            | 1.90   | 1.03   |
+|                                        | M=7 (7OS non-slot) | $p=0$   | 3.68            | 1.91   | 1.11   | 3.29            | 1.71   | 0.93   |
+|                                        |                    | $p=0.1$ | -               | 2.16   | 1.23   | 3.79            | 1.96   | 1.05   |
+|                                        | M=14 (14OS slot)   | $p=0$   | -               | 2.16   | 1.23   | 3.79            | 1.96   | 1.05   |
+|                                        |                    | $p=0.1$ | -               | 2.41   | 1.36   | -               | 2.21   | 1.18   |
+| <b>Resource mapping Type B</b>         | M=2 (2OS non-slot) | $p=0$   | 2.58            | 1.36   | 0.83   | 2.08            | 1.10   | 0.63   |
+|                                        |                    | $p=0.1$ | 3.07            | 1.60   | 0.95   | 2.57            | 1.35   | 0.75   |
+|                                        | M=4 (4OS non-slot) | $p=0$   | 3.12            | 1.63   | 0.97   | 2.66            | 1.39   | 0.77   |
+|                                        |                    | $p=0.1$ | 3.62            | 1.88   | 1.09   | 3.15            | 1.64   | 0.90   |
+|                                        | M=7 (7OS non-slot) | $p=0$   | 3.23            | 1.69   | 0.99   | 2.84            | 1.48   | 0.82   |
+|                                        |                    | $p=0.1$ | 3.72            | 1.93   | 1.12   | 3.33            | 1.73   | 0.94   |
+
+**Table 5.7.1.1.2-4 UL user plane latency for NR TDD with grant free transmission (ms)  
+(Frame structure: DSUUD)**
+
+| UL user plane latency – NR TDD (DSUUD) |                    |         | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|----------------------------------------|--------------------|---------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                        |                    |         | SCS             |        |        |         | SCS             |        |        |
+|                                        |                    |         | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>         | M=4 (4OS non-slot) | $p=0$   | 2.74            | 1.39   | 0.85   | 0.5     | 2.38            | 1.22   | 0.70   |
+|                                        |                    | $p=0.1$ | 3.22            | 1.64   | 0.97   | 0.56    | 2.77            | 1.46   | 0.82   |
+|                                        | M=7 (7OS non-slot) | $p=0$   | 2.84            | 1.49   | 0.91   | 0.53    | 2.49            | 1.28   | 0.73   |
+|                                        |                    | $p=0.1$ | 3.34            | 1.74   | 1.03   | 0.59    | 2.97            | 1.52   | 0.85   |
+|                                        | M=14 (14OS slot)   | $p=0$   | 3.34            | 1.74   | 1.03   | 0.59    | 2.99            | 1.53   | 0.85   |
+|                                        |                    | $p=0.1$ | 3.84            | 1.99   | 1.15   | 0.67    | 3.47            | 1.77   | 0.98   |
+| <b>Resource mapping Type B</b>         | M=2 (2OS non-slot) | $p=0$   | 1.86            | 1      | 0.66   | 0.4     | 1.39            | 0.73   | 0.46   |
+|                                        |                    | $p=0.1$ | 2.31            | 1.23   | 0.78   | 0.46    | 1.85            | 0.96   | 0.57   |
+|                                        | M=4 (4OS non-slot) | $p=0$   | 2.34            | 1.24   | 0.78   | 0.46    | 1.91            | 0.99   | 0.58   |
+|                                        |                    | $p=0.1$ | 2.81            | 1.47   | 0.9    | 0.52    | 2.38            | 1.22   | 0.7    |
+|                                        | M=7 (7OS non-slot) | $p=0$   | 2.44            | 1.29   | 0.81   | 0.47    | 2.09            | 1.08   | 0.63   |
+|                                        |                    | $p=0.1$ | 2.91            | 1.53   | 0.92   | 0.54    | 2.56            | 1.31   | 0.75   |
+|                                        | M=14 (14OS slot)   | $p=0$   | 3.34            | 1.74   | 1.03   | 0.59    | 2.99            | 1.53   | 0.85   |
+|                                        |                    | $p=0.1$ | 3.82            | 1.98   | 1.15   | 0.67    | 3.47            | 1.77   | 0.97   |
+
+**Table 5.7.1.1.2-5 UL user plane latency for NR TDD with grant free transmission (ms)  
+(Frame structure: DUDU)**
+
+| UL user plane latency – NR TDD (DU) |                    |       | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|-------------------------------------|--------------------|-------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                     |                    |       | SCS             |        |        |         | SCS             |        |        |
+|                                     |                    |       | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>      | M=4 (4OS non-slot) | p=0   | 2.04            | 1.09   | 0.71   | 0.42    | 1.68            | 0.87   | 0.53   |
+|                                     |                    | p=0.1 | 2.24            | 1.28   | 0.80   | 0.49    | 1.87            | 0.97   | 0.57   |
+|                                     | M=7 (7OS non-slot) | p=0   | 2.14            | 1.14   | 0.73   | 0.42    | 1.79            | 0.93   | 0.55   |
+|                                     |                    | p=0.1 | 2.36            | 1.34   | 0.83   | 0.50    | 1.99            | 1.03   | 0.60   |
+|                                     | M=14 (14OS slot)   | p=0   | 2.64            | 1.39   | 0.86   | 0.50    | 2.29            | 1.18   | 0.68   |
+|                                     |                    | p=0.1 | 3.04            | 1.60   | 1.01   | 0.58    | 2.49            | 1.28   | 0.78   |
+|                                     | M=2 (2OS non-slot) | p=0   | 1.29            | 0.71   | 0.52   | 0.33    | 0.80            | 0.44   | 0.31   |
+|                                     |                    | p=0.1 | 1.47            | 0.82   | 0.62   | 0.39    | 1.00            | 0.54   | 0.36   |
+| <b>Resource mapping Type B</b>      | M=4 (4OS non-slot) | p=0   | 1.66            | 0.90   | 0.61   | 0.38    | 1.12            | 0.59   | 0.39   |
+|                                     |                    | p=0.1 | 1.86            | 1.04   | 0.72   | 0.44    | 1.42            | 0.75   | 0.47   |
+|                                     | M=7 (7OS non-slot) | p=0   | 1.77            | 0.96   | 0.64   | 0.39    | 1.39            | 0.73   | 0.46   |
+|                                     |                    | p=0.1 | 1.97            | 1.09   | 0.75   | 0.45    | 1.60            | 0.83   | 0.51   |
+|                                     | M=14 (14OS slot)   | p=0   | 2.64            | 1.39   | 0.86   | 0.50    | 2.29            | 1.18   | 0.68   |
+|                                     |                    | p=0.1 | 3.04            | 1.59   | 1.01   | 0.58    | 2.49            | 1.28   | 0.78   |
+
+In addition, NR supports X slot that can be flexibly configured based on the traffic pattern. The evaluation of DDXU is provided for this capability, where ‘X’ slot = ‘U’ slot for UL data transmission and ‘X’=‘D’ for PDCCH transmission for UL user plane latency evaluation. The evaluation results are provided in Table 5.7.1.1.2-6.
+
+**Table 5.7.1.1.2-6 UL user plane latency for NR TDD with grant free transmission (ms)  
+(Frame structure: DDXU, with ‘X’=‘U’ for UL traffic)**
+
+| UL user plane latency – NR TDD (DDXU) |                    |       | UE capability 1 |        |        |         | UE capability 2 |        |        |
+|---------------------------------------|--------------------|-------|-----------------|--------|--------|---------|-----------------|--------|--------|
+|                                       |                    |       | SCS             |        |        |         | SCS             |        |        |
+|                                       |                    |       | 15 kHz          | 30 kHz | 60 kHz | 120 kHz | 15 kHz          | 30 kHz | 60 kHz |
+| <b>Resource mapping Type A</b>        | M=14 (14OS slot)   | p=0   | 3.34            | 1.74   | 1.04   | 0.59    | 3.02            | 1.54   | 0.86   |
+|                                       |                    | p=0.1 | 3.82            | 1.98   | 1.16   | 0.67    | 3.50            | 1.78   | 0.98   |
+| <b>Resource mapping Type B</b>        | M=2 (2OS non-slot) | p=0   | 1.80            | 0.97   | 0.66   | 0.40    | 1.48            | 0.77   | 0.48   |
+|                                       |                    | p=0.1 | 2.04            | 1.10   | 0.77   | 0.45    | 1.64            | 0.86   | 0.54   |
+|                                       | M=7 (7OS non-slot) | p=0   | 2.44            | 1.29   | 0.82   | 0.48    | 2.12            | 1.09   | 0.64   |
+|                                       |                    | p=0.1 | 2.91            | 1.53   | 0.93   | 0.54    | 2.35            | 1.20   | 0.76   |
+
+NR also supports the use of supplementary uplink (SUL) band together with a TDD band, where continuous uplink transmission opportunity becomes possible. The evaluation is applied to a TDD band with DDSU (with S slot = 11DL:1GP:2UL) together with an SUL band. The evaluation results are provided in Table 5.7.1.1.2-7.
+
+**Table 5.7.1.1.2-7 UL user plane latency for NR TDD + SUL with grant free transmission (ms)  
+(Frame structure for TDD carrier: DDSU)**
+
+| UL user plane latency – NR TDD (DDSU) +SUL |                    |       | UE capability 1             |                             |                             | UE capability 2             |                             |                             |
+|--------------------------------------------|--------------------|-------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|-----------------------------|
+|                                            |                    |       | SCS                         |                             |                             | SCS                         |                             |                             |
+|                                            |                    |       | 15 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) | 15 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) |
+| <b>Resource mapping Type A</b>             | M=4 (4OS non-slot) | p=0   | 1.57                        | 1.57                        | 0.86                        | 1.18                        | 1.18                        | 0.65                        |
+|                                            |                    | p=0.1 | 1.79                        | 1.79                        | 1.01                        | 1.40                        | 1.38                        | 0.76                        |
+|                                            | M=7 (7OS non-slot) | p=0   | 1.68                        | 1.68                        | 0.91                        | 1.29                        | 1.29                        | 0.71                        |
+|                                            |                    | p=0.1 | 1.90                        | 1.90                        | 1.06                        | 1.51                        | 1.49                        | 0.82                        |
+|                                            | M=14 (14OS slot)   | p=0   | 2.18                        | 2.18                        | 1.16                        | 1.80                        | 1.79                        | 0.96                        |
+|                                            |                    | p=0.1 | 2.50                        | 2.48                        | 1.32                        | 2.01                        | 2.01                        | 1.12                        |
+|                                            | M=2 (2OS non-slot) | p=0   | 1.04                        | 1.04                        | 0.59                        | 0.54                        | 0.54                        | 0.33                        |
+|                                            |                    | p=0.1 | 1.23                        | 1.22                        | 0.70                        | 0.64                        | 0.63                        | 0.39                        |
+| <b>Resource mapping Type B</b>             | M=4 (4OS non-slot) | p=0   | 1.32                        | 1.32                        | 0.73                        | 0.86                        | 0.86                        | 0.49                        |
+|                                            |                    | p=0.1 | 1.53                        | 1.52                        | 0.85                        | 0.97                        | 0.97                        | 0.56                        |
+|                                            | M=7 (7OS non-slot) | p=0   | 1.43                        | 1.43                        | 0.79                        | 1.04                        | 1.04                        | 0.58                        |
+|                                            |                    | p=0.1 | 1.64                        | 1.63                        | 0.91                        | 1.17                        | 1.17                        | 0.66                        |
+
+It is observed that NR fulfils UL user plane latency requirement in a wide range of configurations.
+
+#### 5.7.1.2 LTE
+
+For the user plane latency of LTE, the similar procedure to NR is used. The detailed assumptions are given in Table 5.7.1.2.1-1 and Table 5.7.1.2.2-1 for DL and UL, respectively.
+
+##### 5.7.1.2.1 Downlink
+
+The downlink procedure is abstracted in Table 5.7.1.2.1-1, where the assumptions of each step for evaluation are given.
+
+**Table 5.7.1.2.1-1 DL user plane procedure for LTE**
+
+| ID  | Component                                   | Notations                                                                                                                                                                                           | Value                                                                                                                                                                                      |
+|-----|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | DL data transfer                            | $T_1 = (t_{BS,tx} + t_{FA,DL}) + t_{DL\_duration} + t_{UE,rx}$                                                                                                                                      |                                                                                                                                                                                            |
+| 1.1 | BS processing delay                         | $t_{BS,tx}$<br>The time interval between the data is arrived, and packet is generated.                                                                                                              | 1.5 TTI                                                                                                                                                                                    |
+| 1.2 | DL Frame alignment (transmission alignment) | $t_{FA,DL}$<br>It includes frame alignment time, and the waiting time for next available DL slot                                                                                                    | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current DL slot;<br>$T_{wait}$ is the waiting time for next available DL slot if the current slot is not DL slot. |
+| 1.3 | TTI for DL data packet transmission         | $t_{DL\_duration}$                                                                                                                                                                                  | 1 TTI                                                                                                                                                                                      |
+| 1.4 | UE processing delay                         | $t_{UE,rx}$<br>The time interval between the PDSCH is received and the data is decoded;                                                                                                             | 1.5 TTI                                                                                                                                                                                    |
+| 2   | HARQ retransmission                         | $T_{HARQ} = T_1 + T_2$<br>$T_2 = (t_{UE,tx} + t_{FA,UL}) + t_{UL\_duration} + t_{BS,rx}$ (For Steps 2.1 to 2.4)                                                                                     |                                                                                                                                                                                            |
+| 2.1 | UE processing delay                         | $t_{UE,tx}$<br>The time interval between the data is decoded, and ACK/NACK packet is generated.                                                                                                     | 1.5 TTI                                                                                                                                                                                    |
+| 2.2 | UL frame alignment (transmission alignment) | $t_{FA,UL}$<br>It includes frame alignment time, and the waiting time for the next available UL slot                                                                                                | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current UL slot;<br>$T_{wait}$ is the waiting time for next available UL slot if the current slot is not UL slot  |
+| 2.3 | TTI for ACK/NACK transmission               | $t_{UL\_duration}$                                                                                                                                                                                  | 1 OFDM symbol                                                                                                                                                                              |
+| 2.4 | BS processing delay                         | $t_{BS,rx}$<br>The time interval between the ACK is received and the ACK is decoded.                                                                                                                | 1.5 TTI                                                                                                                                                                                    |
+| 2.5 | Repeat DL data transfer from 1.1 to 1.4     | $T_1$                                                                                                                                                                                               |                                                                                                                                                                                            |
+| -   | Total one way user plane latency for DL     | $T_{UP} = T_1 + n \times T_{HARQ}$<br>where $n$ is the number of re-transmissions ( $n \geq 0$ )<br>$Average\ T_{UP} = T_1 + p \times T_{HARQ}$<br>where $p$ is the probability of re-transmissions |                                                                                                                                                                                            |
+
+NOTE: For short TTI, it is assumed that PDCCH and sPDCCH can both schedule sPDSCH such that there is no additional waiting time for PDCCH if the data arrives within the PDCCH region. In addition, sPDCCH and sPDSCH can be frequency multiplexed.
+
+Based on the procedure and assumptions, the DL user plane latency of LTE is derived for both FDD and TDD as provided in Table 5.7.1.2.1-2, and Table 5.7.1.2.1-3, respectively. It is observed that LTE can meet the DL user plane latency requirement.
+
+**Table 5.7.1.2.1-2 DL user plane latency for LTE FDD**
+
+| TTI duration            | Error probability | DL UP latency (ms) |
+|-------------------------|-------------------|--------------------|
+| 20S                     | $p=0$             | 0.63               |
+|                         | $p=0.1$           | 0.73               |
+| 30S                     | $p=0$             | 0.94               |
+|                         | $p=0.1$           | 1.10               |
+| <i>Mixed</i><br>20S/30S | $p=0$             | 0.75               |
+|                         | $p=0.1$           | 0.88               |
+| 70S                     | $p=0$             | 2.20               |
+|                         | $p=0.1$           | 2.58               |
+
+**Table 5.7.1.2.1-3 DL user plane latency for LTE TDD**
+
+| TTI duration | Criterion        | Error probability | DL UP latency (ms) |               |
+|--------------|------------------|-------------------|--------------------|---------------|
+|              |                  |                   | DSUDD (Cfg.1)      | DSUUD (Cfg.2) |
+| 70S          | Average case     | $p=0$             | 2.55               | 2.69          |
+|              |                  | $p=0.1$           | 3.10               | 3.14          |
+|              | <i>Best case</i> | $p=0$             | 2.00               | 2.00          |
+|              |                  | $p=0.1$           | 2.40               | 2.40          |
+
+##### 5.7.1.2.2 Uplink
+
+The uplink procedure using a semi-persistent scheduling uplink transmission is abstracted in Table 5.7.1.2.2-1, where the assumptions of each step for evaluation are given.
+
+Table 5.7.1.2.2-1 UL user plane procedure for LTE
+
+| Step | Component                                   | Notations                                                                                                                                                                                          | Value                                                                                                                                                                                      |
+|------|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1    | UL data transfer                            | $T_1 = (t_{UE,tx} + t_{FA,UL}) + t_{UL\_duration} + t_{BS,rx}$                                                                                                                                     |                                                                                                                                                                                            |
+| 1.1  | UE processing delay                         | $t_{UE,tx}$<br>The time interval between the data is arrived, and packet is generated;                                                                                                             | 1.5 TTI                                                                                                                                                                                    |
+| 1.2  | UL Frame alignment (transmission alignment) | $t_{FA,UL}$<br>It includes frame alignment time, and the waiting time for next available UL slot                                                                                                   | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current UL slot.<br>$T_{wait}$ is the waiting time for next available UL slot if the current slot is not UL slot. |
+| 1.3  | TTI for UL data packet transmission         | $t_{UL\_duration}$                                                                                                                                                                                 | 1 TTI                                                                                                                                                                                      |
+| 1.4  | BS processing delay                         | $t_{BS,rx}$<br>The time interval between the PUSCH is received and the data is decoded;                                                                                                            | 1.5 TTI                                                                                                                                                                                    |
+| 2    | HARQ retransmission                         | $T_{HARQ} = T_2 + T_1$<br>$T_2 = (t_{BS,tx} + t_{FA,DL}) + t_{DL\_duration} + t_{UE,rx}$ (For Steps 2.1 to 2.4)                                                                                    |                                                                                                                                                                                            |
+| 2.1  | BS processing delay                         | $t_{BS,tx}$<br>The time interval between the data is decoded, and PDCCH preparation                                                                                                                | 1.5 TTI                                                                                                                                                                                    |
+| 2.2  | DL Frame alignment (transmission alignment) | $t_{FA,DL}$<br>It includes frame alignment time, and the waiting time for next available DL slot                                                                                                   | $T_{FA} + T_{wait}$ ,<br>$T_{FA}$ is the frame alignment time within the current DL slot;<br>$T_{wait}$ is the waiting time for next available DL slot if the current slot is not DL slot  |
+| 2.3  | TTI for PDCCH transmission                  | $t_{DL\_duration}$                                                                                                                                                                                 | 1 OFDM symbols for PDCCH scheduling the retransmission.                                                                                                                                    |
+| 2.4  | UE processing delay                         | $t_{UE,rx}$<br>The time interval between the PDCCH is received and the decoded.                                                                                                                    | 1.5 TTI                                                                                                                                                                                    |
+| 2.5  | Repeat UL data transfer from 1.1 to 1.4     | $T_1$                                                                                                                                                                                              |                                                                                                                                                                                            |
+|      | Total one way user plane latency for UL     | $T_{UP} = T_1 + n \times T_{HARQ}$<br>where $n$ is the number of re-transmissions ( $n \geq 0$ )<br>Average $T_{UP} = T_1 + p \times T_{HARQ}$<br>where $p$ is the probability of re-transmissions |                                                                                                                                                                                            |
+
+Based on the procedure and assumptions, the UL user plane latency of LTE is derived for both FDD and TDD as provided in Table 5.7.1.2.2-2, and Table 5.7.1.2.2-3, respectively.
+
+Table 5.7.1.2.2-2 UL user plane latency for LTE FDD
+
+| TTI duration  | Error probability | UL UP latency (ms) |
+|---------------|-------------------|--------------------|
+| 20S           | $p=0$             | 0.63               |
+|               | $p=0.1$           | 0.73               |
+| 30S           | $p=0$             | 0.94               |
+|               | $p=0.1$           | 1.10               |
+| Mixed 20S/30S | $p=0$             | 0.75               |
+|               | $p=0.1$           | 0.88               |
+| 70S           | $p=0$             | 2.20               |
+|               | $p=0.1$           | 2.58               |
+
+Table 5.7.1.2.2-3 UL user plane latency for LTE TDD with semi-persistent scheduling (SPS)
+
+| TTI duration | Criterion    | Error probability | UL UP latency (ms) |               |
+|--------------|--------------|-------------------|--------------------|---------------|
+|              |              |                   | DSUDD (Cfg.1)      | DSUUD (Cfg.2) |
+| 70S          | Average case | $p=0$             | -                  | 3.26          |
+|              |              | $p=0.1$           | -                  | 3.73          |
+|              | Best case    | $p=0$             | 2.00               | 2.00          |
+|              |              | $p=0.1$           | 2.45               | 2.40          |
+
+It is observed that LTE can meet the UL user plane latency requirement.
+
+### 5.7.2 Control plane latency
+
+As defined in Report ITU-R M.2410 [4], control plane latency refers to the transition time from a most “battery efficient” state (e.g. Idle state) to the start of continuous data transfer (e.g. Active state).
+
+#### 5.7.2.1 NR
+
+For NR Rel-15, control plane latency is evaluated from RRC\_INACTIVE state to RRC\_CONNECTED state. Figure 5.7.2.1-1 provides an example control plane flow for NR Rel-15.
+
+![Sequence diagram of the C-plane procedure for NR Rel-15 between UE and gNB.](78ffccd66df9bafd96e3e081110d09dd_img.jpg)
+
+The diagram illustrates the control plane procedure between a User Equipment (UE) and a gNodeB (gNB). The sequence of events is as follows:
+
+- Delay for RACH Scheduling Period:** A delay period at the UE before the procedure begins.
+- 2. RACH Preamble:** The UE sends a RACH Preamble to the gNB.
+- 3. Processing delay in gNB:** The gNB processes the RACH Preamble.
+- 4. RA response:** The gNB sends an RA response to the UE.
+- 5. Processing delay in UE:** The UE processes the RA response.
+- 6. RRC Resume Request:** The UE sends an RRC Resume Request to the gNB.
+- 7. Processing delay in gNB:** The gNB processes the RRC Resume Request.
+- 8. RRC Resume:** The gNB sends an RRC Resume message to the UE.
+- 9. Processing delay in UE:** The UE processes the RRC Resume message.
+- 10. RRC Resume Complete:** The UE sends an RRC Resume Complete message to the gNB.
+
+The control plane procedure is indicated by a vertical double-headed arrow on the right side of the diagram, spanning from the start of the RACH Preamble to the end of the RRC Resume Complete message.
+
+Sequence diagram of the C-plane procedure for NR Rel-15 between UE and gNB.
+
+**Figure 5.7.2.1-1 C-plane procedure (example for NR Rel-15)**
+
+The detailed assumption of each step as shown in Figure 5.7.2.1-1 is provided in Table 5.7.2.1-1. The evaluation is for UL data transfer. It is understood that the evaluation results for DL data transfer can be further reduced because UE processing delay in Step 9 for DL data transfer does not need to handle UL grant receiving, and therefore can be reduced compared to the case of UL data transfer.
+
+NOTE: The delay values shown below do not include the waiting time for DL/UL subframe. It is only gNB or UE processing delay. The waiting time will be calculated and it depends on the detailed DL/UL configuration.
+
+**Table 5.7.2.1-1 Assumption of C-plane procedure for NR**
+
+| Step | Description                                                                                                                    | CP Latency for UL data transfer [ms]                                                                                                                                              |
+|------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1    | Delay due to RACH scheduling period (1TTI)                                                                                     | 0                                                                                                                                                                                 |
+| 2    | Transmission of RACH Preamble                                                                                                  | Length of the preamble according to the PRACH format as specified in [6 38.211]                                                                                                   |
+| 3    | Preamble detection and processing in gNB                                                                                       | $T_{proc,2}$ (assuming $d_{2,1}=0$ )                                                                                                                                              |
+| 4    | Transmission of RA response                                                                                                    | $T_s$ (the length of 1 slot / non-slot)<br>NOTE: the length of 1 slot or 1 non-slot include PDCCH and PDSCH (the first OFDM symbol of PDSCH is frequency multiplexed with PDCCH). |
+| 5    | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Resume Request) | $N_{t,1}+N_{t,2}+0.5$ ms                                                                                                                                                          |
+| 6    | Transmission of RRC Resume Request                                                                                             | $T_s$ (the length of 1 slot / non-slot)<br>NOTE: the length of 1 slot or 1 non-slot is equal to PUSCH allocation length.                                                          |
+| 7    | Processing delay in gNB (L2 and RRC)                                                                                           | 3                                                                                                                                                                                 |
+| 8    | Transmission of RRC Resume                                                                                                     | $T_s$ (the length of 1 slot / non-slot)                                                                                                                                           |
+| 9    | Processing delay in UE of RRC Resume including grant reception                                                                 | 7                                                                                                                                                                                 |
+| 10   | Transmission of RRC Resume Complete and UP data                                                                                | 0                                                                                                                                                                                 |
+
+Notes:
+
+- For step 1, the procedure for *transition from a most "battery efficient" state* has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+- For step 3, the value of  $T_{proc,2}$  is used only for evaluation. gNB processing delay may vary depending on implementation.
+- For step 5, the latency of  $N_{t,1}+N_{t,2}+0.5$ ms is used according to Section 8.3 of TS 38.213.  $N_{t,1}$  is a time duration of  $N_1$  symbols corresponding to a PDSCH reception time for PDSCH processing capability 1 when additional PDSCH DM-RS is configured; and  $N_{t,2}$  is a time duration of  $N_2$  symbols corresponding to a PUSCH preparation time for PUSCH processing capability 1. The value of  $N_1$  and  $N_2$  are shown in Table 5.3-1 and Table 6.4-1 of TS38.214, respectively..
+- For step 7, the processing delay in gNB (L2 and RRC) has been reduced to 3 ms. The delays due to inside-gNB or inter-gNB communication are not included in Step 7. Such delays may exist depending on deployment, but are not within the scope of this evaluation.
+- For step 9 for UL data transfer, the processing delay in the UE (L2 and RRC) is considered, i.e., from reception of RRC Connection Resume to the reception of UL grant. The transmission of UL grant by gNB and processing delay in the UE (processing of UL grant and preparing for UL tx) are also considered. The RRCConnectionResume message only includes MAC and PHY configuration. No DRX, SPS, CA, or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRC Connection Resume Complete and the data is transmitted over common search space with DCI format 0.
+- For step 10, the beginning of this subframe is considered to be "*the start of continuous data transfer*", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+- For the case of a TDD band (30 kHz SCS) with an SUL band (15 kHz SCS), the sub-carrier spacing of 15 kHz that results in larger delay is used in evaluating the latency for Step 3 and 5.
+
+In addition, the following assumptions apply to the evaluation:
+
+- The transmission duration of Step 2, 4, 6, and 8 cannot be crossing the boundary of a slot;
+- The CP procedure can start from the OFDM symbols within the slot that PRACH preamble can be transmitted (assuming that the slot is UL slot; otherwise it will wait for the available UL slot).
+
+Based on the control plane procedure and assumptions given in Table 5.7.2.1-1, a variety of configurations and UE capabilities are evaluated for NR for UL data transfer. For a specific configuration, the results are the average over the possible start timing of the control plane procedure.
+
+For NR FDD, the evaluation results of different PRACH lengths are provided in Table 5.7.2.1-2. The evaluation is applied to various non-slot length and sub-carrier spacings. Resource mapping type A and B are considered. UE capability 1 and UE capability 2 are evaluated.
+
+**Table 5.7.2.1-2 Control plane latency for NR FDD (ms)**
+
+##### **(a) PRACH length = 2 OFDM symbols**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 15.4            | 13.1      | 12.3      | 11.7       | 15.0            | 12.8      | 12.1      |
+|                       | $M=7$<br>(70S non-slot) | 15.6            | 13.4      | 12.4      | 11.7       | 15.2            | 13.2      | 12.2      |
+| Type B                | $M=2$<br>(20S non-slot) | 13.3            | 12.0      | 11.8      | 11.3       | 13.0            | 11.9      | 11.6      |
+|                       | $M=4$<br>(40S non-slot) | 13.8            | 12.3      | 12.0      | 11.5       | 13.4            | 12.1      | 11.7      |
+|                       | $M=7$<br>(70S non-slot) | 14.7            | 12.8      | 12.2      | 11.6       | 14.3            | 12.6      | 12.0      |
+
+##### **(b) PRACH length = 6 OFDM symbols**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 15.6            | 13.5      | 12.4      | 11.7       | 15.1            | 13.0      | 12.1      |
+|                       | $M=7$<br>(70S non-slot) | 15.8            | 13.6      | 12.5      | 11.7       | 15.3            | 13.1      | 12.2      |
+| Type B                | $M=2$<br>(20S non-slot) | 13.7            | 12.3      | 11.9      | 11.4       | 13.4            | 12.0      | 11.7      |
+|                       | $M=4$<br>(40S non-slot) | 14.2            | 12.5      | 12.0      | 11.5       | 13.9            | 12.3      | 11.8      |
+|                       | $M=7$<br>(70S non-slot) | 15.3            | 13.0      | 12.3      | 11.6       | 14.8            | 12.8      | 12.1      |
+
+##### **(c) PRACH length=1ms**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           | UE capability 2 |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 15kHz SCS       | 30kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 16.3            | 13.6      | 16.3            | 13.6      |
+|                       | $M=7$<br>(70S non-slot) | 16.5            | 14.3      | 16.5            | 14.3      |
+|                       | $M=14$<br>(140S slot)   | 17.0            | 14.5      | 17.0            | 14.5      |
+| Type B                | $M=2$<br>(20S non-slot) | 14.1            | 12.9      | 13.8            | 12.7      |
+|                       | $M=4$<br>(40S non-slot) | 14.7            | 13.3      | 14.3            | 12.9      |
+|                       | $M=7$<br>(70S non-slot) | 15.8            | 13.8      | 15.0            | 13.3      |
+
+For NR TDD, various DL/UL configurations are evaluated. The evaluation results of DDDSU (with S slot = 11DL: 1GP:2UL), DSUUD (with S slot = 11DL: 1GP:2UL), and DUDU (without GP) are provided. The evaluation is applied to various non-slot length and sub-carrier spacings. Resource mapping type A and B are considered. UE capability 1 and UE capability 2 are evaluated.
+
+Table 5.7.2.1-3 provides the evaluation results for the frame structure of DDDSU for different PRACH length.
+
+**Table 5.7.2.1-3 Control plane latency for NR TDD (ms)**  
+ (Frame structure: DDDSU, S slot = 11DL:1GP:2UL)
+
+##### **(a) PRACH length = 2 OFDM symbols**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           | UE capability 2 |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 15kHz SCS       | 30kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 17.9            | 14.0      | 17.9            | 14.0      |
+|                       | $M=7$<br>(70S non-slot) | 18.1            | 14.4      | 18.1            | 14.2      |
+| Type B                | $M=2$<br>(20S non-slot) | 16.8            | 13.4      | 16.8            | 13.4      |
+|                       | $M=4$<br>(40S non-slot) | 17.2            | 13.6      | 17.2            | 13.6      |
+|                       | $M=7$<br>(70S non-slot) | 17.6            | 13.8      | 17.6            | 13.8      |
+
+##### **(b) PRACH length=1ms**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 | UE capability 2 |
+|-----------------------|-------------------------|-----------------|-----------------|
+|                       |                         | 15kHz SCS       | 15kHz SCS       |
+| Type A                | $M=4$<br>(40S non-slot) | 18.3            | 18.3            |
+|                       | $M=7$<br>(70S non-slot) | 18.5            | 18.5            |
+| Type B                | $M=2$<br>(20S non-slot) | 17.1            | 17.1            |
+|                       | $M=4$<br>(40S non-slot) | 17.6            | 17.6            |
+|                       | $M=7$<br>(70S non-slot) | 18.0            | 18.0            |
+
+In Table 5.7.2.1-4, the evaluation results of DSUUD with different PRACH length are provided.
+
+**Table 5.7.2.1-4 Control plane latency for NR TDD (ms)**  
+ (Frame structure: DSUUD, S slot = 11DL:1GP:2UL)
+
+##### **(a) PRACH length = 2 OFDM symbols**
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 16.2            | 13.9      | 12.6      | 12.2       | 15.6            | 13.4      | 12.6      |
+|                       | $M=7$<br>(70S non-slot) | 16.4            | 14.0      | 12.7      | 12.2       | 15.8            | 13.5      | 12.7      |
+| Type B                | $M=2$<br>(20S non-slot) | 14.3            | 12.6      | 12.3      | 11.5       | 14.3            | 12.6      | 12.3      |
+|                       | $M=4$<br>(40S non-slot) | 15.1            | 12.7      | 12.4      | 11.8       | 15.1            | 12.7      | 12.4      |
+|                       | $M=7$<br>(70S non-slot) | 16.3            | 13.0      | 12.5      | 12.2       | 15.5            | 12.9      | 12.5      |
+
+##### (b) PRACH length = 6 OFDM symbols
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 16.3            | 14.3      | 12.6      | 12.2       | 15.6            | 13.3      | 12.6      |
+|                       | $M=7$<br>(70S non-slot) | 16.5            | 14.4      | 12.7      | 12.2       | 15.8            | 13.4      | 12.7      |
+| Type B                | $M=2$<br>(20S non-slot) | 14.4            | 12.7      | 12.4      | 11.5       | 14.4            | 12.7      | 12.4      |
+|                       | $M=4$<br>(40S non-slot) | 14.9            | 12.8      | 12.5      | 11.8       | 14.9            | 12.8      | 12.5      |
+|                       | $M=7$<br>(70S non-slot) | 17.4            | 13.1      | 12.6      | 12.2       | 16.5            | 13.0      | 12.6      |
+
+##### (c) PRACH length=1ms
+
+| Resource mapping type | Non-slot duration       | UE capability 1 | UE capability 2 |
+|-----------------------|-------------------------|-----------------|-----------------|
+|                       |                         | 15kHz SCS       | 15kHz SCS       |
+| Type A                | $M=4$<br>(40S non-slot) | 17.3            | 17.3            |
+|                       | $M=7$<br>(70S non-slot) | 17.5            | 17.5            |
+| Type B                | $M=2$<br>(20S non-slot) | 14.7            | 14.6            |
+|                       | $M=4$<br>(40S non-slot) | 15.1            | 15.1            |
+|                       | $M=7$<br>(70S non-slot) | 17.3            | 15.5            |
+
+Table 5.7.2.1-5 provides the evaluation results for the frame structure of DUDU for different PRACH length.
+
+**Table 5.7.2.1-5 Control plane latency for NR TDD (ms)**  
+(Frame structure: DUDU, without GP)
+
+##### (a) PRACH length = 2 OFDM symbols
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 17.0            | 14.1      | 12.7      | 11.7       | 16.1            | 13.6      | 12.5      |
+|                       | $M=7$<br>(70S non-slot) | 17.2            | 14.3      | 12.8      | 11.7       | 16.4            | 13.7      | 12.6      |
+| Type B                | $M=2$<br>(20S non-slot) | 13.9            | 12.3      | 12.2      | 11.6       | 13.9            | 12.4      | 11.8      |
+|                       | $M=4$<br>(40S non-slot) | 14.2            | 12.6      | 12.2      | 11.6       | 14.1            | 12.4      | 11.9      |
+|                       | $M=7$<br>(70S non-slot) | 15.2            | 13.3      | 12.8      | 11.7       | 14.6            | 12.8      | 12.4      |
+
+##### (b) PRACH length = 6 OFDM symbols
+
+| Resource mapping type | Non-slot duration       | UE capability 1 |           |           |            | UE capability 2 |           |           |
+|-----------------------|-------------------------|-----------------|-----------|-----------|------------|-----------------|-----------|-----------|
+|                       |                         | 15kHz SCS       | 30kHz SCS | 60kHz SCS | 120kHz SCS | 15kHz SCS       | 30kHz SCS | 60kHz SCS |
+| Type A                | $M=4$<br>(40S non-slot) | 17.1            | 14.5      | 12.8      | 11.8       | 16.1            | 13.6      | 12.5      |
+|                       | $M=7$<br>(70S non-slot) | 17.3            | 14.6      | 12.8      | 11.8       | 16.3            | 13.6      | 12.6      |
+| Type B                | $M=2$<br>(20S non-slot) | 14.1            | 12.5      | 12.2      | 11.6       | 14.1            | 12.5      | 11.7      |
+|                       | $M=4$<br>(40S non-slot) | 14.4            | 13.0      | 12.3      | 11.6       | 14.4            | 12.5      | 12.0      |
+|                       | $M=7$<br>(70S non-slot) | 15.8            | 13.6      | 12.8      | 11.7       | 14.8            | 13.1      | 12.6      |
+
+(c) PRACH length=1ms
+
+| Resource mapping type | Non-slot duration       | UE capability 1 | UE capability 2 |
+|-----------------------|-------------------------|-----------------|-----------------|
+|                       |                         | 15kHz SCS       | 15kHz SCS       |
+| Type A                | $M=4$<br>(4OS non-slot) | 18.3            | 18.3            |
+|                       | $M=7$<br>(7OS non-slot) | 18.5            | 18.5            |
+| Type B                | $M=2$<br>(2OS non-slot) | 14.3            | 14.3            |
+|                       | $M=4$<br>(4OS non-slot) | 14.7            | 14.6            |
+|                       | $M=7$<br>(7OS non-slot) | 17.0            | 15.0            |
+
+NR also supports the use of supplementary uplink (SUL) band together with a TDD band, where continuous uplink transmission opportunity becomes possible. The evaluation is applied to a TDD band with DDDSU (with S slot = 11DL:1GP:2UL) together with an SUL band. The evaluation results are provided in Table 5.7.2.1-6.
+
+**Table 5.7.2.1-6 Control plane latency for NR TDD+SUL (ms)**  
+**(Frame structure for TDD carrier: DDDSU, S slot = 11DL:1GP:2UL)**
+
+(a) PRACH length=2 OFDM symbols
+
+| Resource mapping type | Non-slot duration       | UE capability1             |                             |                             | UE capability2             |                             |                             |
+|-----------------------|-------------------------|----------------------------|-----------------------------|-----------------------------|----------------------------|-----------------------------|-----------------------------|
+|                       |                         | 15 kHz (TDD)+ 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) | 15 kHz (TDD)+ 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) |
+| Type A                | $M=4$<br>(4OS non-slot) | 15.9                       | 13.9                        | 13.1                        | 15.0                       | 13.6                        | 12.8                        |
+|                       | $M=7$<br>(7OS non-slot) | 16.1                       | 14.2                        | 13.4                        | 15.2                       | 13.7                        | 13.2                        |
+| Type B                | $M=2$<br>(2OS non-slot) | 13.3                       | 12.9                        | 12.1                        | 13.0                       | 12.6                        | 11.9                        |
+|                       | $M=4$<br>(4OS non-slot) | 13.8                       | 13.5                        | 12.3                        | 13.4                       | 12.9                        | 12.1                        |
+|                       | $M=7$<br>(7OS non-slot) | 14.7                       | 14.1                        | 12.8                        | 14.4                       | 13.6                        | 12.6                        |
+
+(b) PRACH length=1ms
+
+| Resource mapping type | Non-slot duration       | UE capability1             |                             |                             | UE capability2             |                             |                             |
+|-----------------------|-------------------------|----------------------------|-----------------------------|-----------------------------|----------------------------|-----------------------------|-----------------------------|
+|                       |                         | 15 kHz (TDD)+ 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) | 15 kHz (TDD)+ 15 kHz (SUL) | 30 kHz (TDD) + 15 kHz (SUL) | 30 kHz (TDD) + 30 kHz (SUL) |
+| Type A                | $M=4$<br>(4OS non-slot) | 17.3                       | 15.6                        | 13.6                        | 17.3                       | 14.6                        | 13.6                        |
+|                       | $M=7$<br>(7OS non-slot) | 17.5                       | 15.7                        | 14.8                        | 17.5                       | 14.7                        | 14.8                        |
+|                       | $M=14$<br>(14OS slot)   | 18.8                       | 17.2                        | 15.6                        | 18.8                       | 17.0                        | 15.6                        |
+| Type B                | $M=2$<br>(2OS non-slot) | 14.1                       | 13.8                        | 12.9                        | 13.8                       | 13.4                        | 12.8                        |
+|                       | $M=4$<br>(4OS non-slot) | 14.7                       | 14.6                        | 13.3                        | 14.3                       | 13.7                        | 12.9                        |
+|                       | $M=7$<br>(7OS non-slot) | 15.8                       | 15.2                        | 13.8                        | 15.0                       | 14.7                        | 13.3                        |
+
+It is observed that NR fulfils the control plane latency requirement of 20ms in a wide range of configurations. If, in control plane procedure, the latency of step 7 and step 9 can be further reduced, the 10ms target as encouraged by ITU-R can be achieved in some cases.
+
+#### 5.7.2.2 LTE
+
+For LTE Rel-15, control plane latency is evaluated from IDLE state to CONNECTED state. It is noted that, for LTE, when RRC connection is suspended, RRC connection resume is permitted by E-UTRAN. Figure 5.7.2.2-1 provides an example control plane flow for the above-mentioned IDLE to CONNECTED state transition for LTE Rel-15.
+
+![Sequence diagram of C-plane activation procedure between UE and eNB. The diagram shows 10 steps: 1. Delay for RACH Scheduling Period (UE internal), 2. RACH Preamble (UE to eNB), 3. Processing delay in eNB (eNB internal), 4. RA response (eNB to UE), 5. Processing delay in UE (UE internal), 6. RRC Connection Resume Request (UE to eNB), 7. Processing delay in eNB (eNB internal), 8. RRC Connection Resume (eNB to UE), 9. Processing delay in UE (UE internal), 10. RRC Connection Resume Complete (UE to eNB). A vertical double-headed arrow on the right labeled 'Control plane procedure' spans from step 2 to step 10.](4356776ca004ecba5d599667a155d7d4_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant eNB
+    Note left of UE: 1. Delay for RACH Scheduling Period
+    UE->>eNB: 2. RACH Preamble
+    Note right of eNB: 3. Processing delay in eNB
+    eNB->>UE: 4. RA response
+    Note left of UE: 5. Processing delay in UE
+    UE->>eNB: 6. RRC Connection Resume Request
+    Note right of eNB: 7. Processing delay in eNB
+    eNB->>UE: 8. RRC Connection Resume
+    Note left of UE: 9. Processing delay in UE
+    UE->>eNB: 10. RRC Connection Resume Complete
+```
+
+Sequence diagram of C-plane activation procedure between UE and eNB. The diagram shows 10 steps: 1. Delay for RACH Scheduling Period (UE internal), 2. RACH Preamble (UE to eNB), 3. Processing delay in eNB (eNB internal), 4. RA response (eNB to UE), 5. Processing delay in UE (UE internal), 6. RRC Connection Resume Request (UE to eNB), 7. Processing delay in eNB (eNB internal), 8. RRC Connection Resume (eNB to UE), 9. Processing delay in UE (UE internal), 10. RRC Connection Resume Complete (UE to eNB). A vertical double-headed arrow on the right labeled 'Control plane procedure' spans from step 2 to step 10.
+
+**Figure 5.7.2.2-1 C-plane activation procedure (example for Rel-15)**
+
+It is noted that for Step 9, the processing delay in UE might be different for the start of DL and UL continuous data transfer. Therefore the evaluation of control plane latency is conducted for DL and UL, respectively.
+
+The evaluation results of LTE FDD on control plane latency are provided in Table 5.7.2.2-1.
+
+**Table 5.7.2.2-1 Control plane latency of LTE FDD**
+
+| Step                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Description                                                                                                                               | CP Latency for UL data transfer [ms] |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Delay due to RACH scheduling period (1TTI)                                                                                                | 0                                    |
+| 2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Transmission of RACH Preamble                                                                                                             | 1                                    |
+| 3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Preamble detection and processing in eNB                                                                                                  | 2                                    |
+| 4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Transmission of RA response                                                                                                               | 1                                    |
+| 5                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Resume Request) | 4                                    |
+| 6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Transmission of RRC Connection Resume Request                                                                                             | 1                                    |
+| 7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Processing delay in eNB (L2 and RRC)                                                                                                      | 3                                    |
+| 8                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Transmission of RRC Connection Resume                                                                                                     | 1                                    |
+| 9                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Processing delay in UE of RRC Connection Resume including grant reception                                                                 | 7                                    |
+| 10                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Transmission of RRC Connection Resume Complete and UP data                                                                                | 0                                    |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <b>Total delay [ms]</b>                                                                                                                   | <b>20</b>                            |
+| Notes:<br>1. For step 1, the procedure for <i>transition from a most "battery efficient" state</i> has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.<br>2. For step 5, the latency of 4 ms has been agreed by RAN1, see LS in R2-1806411.<br>3. For step 7, the processing delay in eNB (L2 and RRC) has been reduced to 3 ms.<br>4. For step 9 for UL data transfer, the processing delay in the UE (L2 and RRC) is considered, i.e., from reception of RRC Connection Resume to the reception of UL grant. The transmission of UL grant by eNB and processing delay in the UE (processing of UL grant and preparing for UL tx) are also considered. The RRCConnectionResume message only includes MAC and PHY configuration. No DRX, SPS, CA, or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRC Connection Resume Complete and the data is transmitted over common search space with DCI format 0.<br>5. For step 9 for DL data transfer, only the processing delay in the UE (L2 and RRC) is considered, i.e., from reception of RRC Connection Resume to the reception of DL grant. The RRCConnectionResume message only includes MAC and PHY configuration. No DRX, SPS, CA, or MIMO re-configuration will be triggered by this message. Further, the UL grant for transmission of RRC Connection Resume Complete and the data is transmitted over common search space with DCI format 0.<br>6. For step 10, the beginning of this subframe is considered to be " <i>the start of continuous data transfer</i> ", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above. |                                                                                                                                           |                                      |
+
+For LTE TDD, the achieved latency will depend on when the procedure is initiated due to the TDD-pattern (i.e. in some cases the eNB and UE must wait for a subframe where DL and UL can be transmitted).
+
+For DL data transfer, the evaluation results of LTE TDD are provided in Table 5.7.2.2-2.
+
+**Table 5.7.2.2-2 Control plane latency of LTE TDD for DL data transfer**
+
+| Step                    | Average CP Latency for DL data transfer [ms] |          |          |          |          |          |          |
+|-------------------------|----------------------------------------------|----------|----------|----------|----------|----------|----------|
+|                         | Config 0                                     | Config 1 | Config 2 | Config 3 | Config 4 | Config 5 | Config 6 |
+| 1                       | 0                                            | 0        | 0        | 0        | 0        | 0        | 0        |
+| 2                       | 1                                            | 1        | 1        | 1        | 1        | 1        | 1        |
+| 3                       | 3                                            | 2        | 2        | 2.7      | 2        | 2        | 2.5      |
+| 4                       | 1                                            | 1        | 1        | 1        | 1        | 1        | 1        |
+| 5                       | 4.8                                          | 5.4      | 5.8      | 4.8      | 5.7      | 5.9      | 4.5      |
+| 6                       | 1                                            | 1        | 1        | 1        | 1        | 1        | 1        |
+| 7                       | 3                                            | 3        | 3        | 3        | 3        | 3        | 3.3      |
+| 8                       | 1                                            | 1        | 1        | 1        | 1        | 1        | 1        |
+| 9                       | 4                                            | 3        | 3        | 3        | 3        | 3        | 3.8      |
+| 10                      | 0                                            | 0        | 0        | 0        | 0        | 0        | 0        |
+| <b>Total delay [ms]</b> | 18.8                                         | 17.4     | 17.8     | 17.5     | 17.7     | 17.9     | 18.1     |
+
+Notes:
+
+1. The description of each component is the same as in Table 5.7.2.2-1. TDD frame structure configuration 0~6 are defined in TS36.211.
+2. For step 1, the procedure for transition from a most "battery efficient" state has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+3. For step 3, the eNB processing delay is 2ms as in FDD. Additional delay due to waiting for DL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.
+4. For step 5, the UE processing delay is 4 ms as in FDD, see LS in R2-1806411. Additional delay due to waiting for UL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.
+5. For step 7, the eNB processing delay (L2 and RRC) has been reduced to 3 ms as in FDD. Additional delay due to waiting for DL subframe is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.
+6. For step 9 for DL data transfer, only the processing delay in the UE (L2 and RRC) is considered as in FDD. Additional delay due to waiting for DL subframe for receiving DL grant is included. The delay value is the average delay taken over the starting subframes when the procedure is initiated under the corresponding TDD configuration.
+7. For step 10, the beginning of this subframe is considered to be "*the start of continuous data transfer*", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+
+For UL data transfer, the evaluation results of LTE TDD are provided in Table 5.7.2.2-3 for specific starting subframes for TDD frame structure configurations.
+
+**Table 5.7.2.2-3 Control plane latency of LTE TDD for UL data transfer**
+
+| Step | Description                                                                                                                               | CP Latency for UL data transfer [ms]                                                                                                                                                                            |
+|------|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|      |                                                                                                                                           | for the following cases<br>Config 0, Starting Subframe = 2,7<br>Config 1, Starting Subframe = 2,7<br>Config 3, Starting Subframe = 1, 2<br>Config 4, Starting Subframe = 2<br>Config 6, Starting Subframe = 2,7 |
+| 1    | Delay due to RACH scheduling period (1TTI)                                                                                                | 0                                                                                                                                                                                                               |
+| 2    | Transmission of RACH Preamble                                                                                                             | 1                                                                                                                                                                                                               |
+| 3    | Preamble detection and processing in eNB                                                                                                  | 2                                                                                                                                                                                                               |
+| 4    | Transmission of RA response                                                                                                               | 1                                                                                                                                                                                                               |
+| 5    | UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Resume Request) | 4                                                                                                                                                                                                               |
+| 6    | Transmission of RRC Connection Resume Request                                                                                             | 1                                                                                                                                                                                                               |
+| 7    | Processing delay in eNB (L2 and RRC)                                                                                                      | 3                                                                                                                                                                                                               |
+| 8    | Transmission of RRC Connection Resume                                                                                                     | 1                                                                                                                                                                                                               |
+| 9    | Processing delay in UE of RRC Connection Resume including grant reception                                                                 | 7                                                                                                                                                                                                               |
+| 10   | Transmission of RRC Connection Resume Complete and UP data                                                                                | 0                                                                                                                                                                                                               |
+|      | <b>Total delay [ms]</b>                                                                                                                   | <b>20</b>                                                                                                                                                                                                       |
+
+Notes:
+
+- TDD frame structure configuration 0~6 are defined in TS36.211. The delay value is for the given starting subframes under the corresponding TDD configuration.
+- For step 1, the procedure for transition from a most "battery efficient" state has yet not begun, hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+- For step 3, the eNB processing delay is 2ms as in FDD. Additional delay due to waiting for DL subframe is 0 for the given starting subframes under the corresponding TDD configuration.
+- For step 5, the UE processing delay is 4 ms as in FDD, see LS in R2-1806411. Additional delay due to waiting for UL subframe is 0 for the given starting subframes under the corresponding TDD configuration.
+- For step 7, the eNB processing delay (L2 and RRC) has been reduced to 3 ms as in FDD. Additional delay due to waiting for DL subframe is 0 for the given starting subframes under the corresponding TDD configuration.
+- For step 9 for UL data transfer, the processing delay is considered as in FDD. Additional delay due to waiting for DL subframe for receiving UL grant is 0 for the given starting subframes under the corresponding TDD configuration.
+- For step 10, the beginning of this subframe is considered to be "*the start of continuous data transfer*", hence this step is not relevant for the latency of the procedure which is illustrated by a '0' in the above.
+
+Based on the above analysis, 20ms control plane latency is fulfilled by LTE Rel-15 FDD, and for TDD for the above cases.
+
+## 5.8 Energy efficiency
+
+As defined in Report ITU-R M.2410 [4], network energy efficiency is the capability of a RIT/SRIT to minimize the radio access network energy consumption in relation to the traffic capacity provided. Device energy efficiency is the capability of the RIT/SRIT to minimize the power consumed by the device modem in relation to the traffic characteristics.
+
+The RIT/SRIT shall have the capability to support a high sleep ratio and long sleep duration.
+
+The sleep ratio is the fraction of unoccupied time resources (for the network) or sleeping time (for the device) in a period of time corresponding to the cycle of the control signaling (for the network) or the cycle of discontinuous reception (for the device) when no user data transfer takes place. The sleep duration is the continuous period of time with no transmission (for network and device) and reception (for the device).
+
+### 5.8.1 Network side
+
+#### 5.8.1.1 NR
+
+The sleep ratio and sleep duration for NR network under unloaded case are evaluated.
+
+When no data transfer takes place, NR network will keep periodical transmission of SS/PBCH blocks and RMSI (remaining minimum system information), as well as paging signal in order for UEs to detect and access the radio network. The following mechanisms for SS/PBCH block, RMSI and paging are assumed for the evaluation.
+
+For SS/PBCH block transmission, the following configurations are considered in evaluation.
+
+- One SS/PBCH block occupies 4 OFDM symbols with 20 RBs in one slot.
+- One or multiple SS/PBCH block(s) compose an "SS burst set" (SSB set).
+  - Denote  $L$  as the number of SS/PBCH blocks in an SSB set, where  $L$  can be 1~ 64. For below 3 GHz, the maximum value of  $L$  is 4; for below 7.125 GHz, the maximum value of  $L$  is 8.
+- One SSB set transmission is confined to a half radio frame (5 ms) window
+- The SSB set periodicity ( $P_{\text{SSB}}$ ) can be configured to be {5, 10, 20, 40, 80, 160} ms
+- The following mapping is used in a half radio frame for 15, 30, 120 and 240kHz SCS
+  - 2 SS/PBCH blocks is transmitted in one slot. And the  $L$  SS/PBCH blocks in an SSB set is transmitted in successive slots from the first slot in one SSB set period.
+
+For RMSI transmission, the following configurations are considered in evaluation.
+
+- One RMSI transmission occupies 2 OFDM symbols in one slot.
+- RMSI is multiplexed with SS/PBCH block using the following ways:
+  - For FR1, RMSI is time division multiplexed (TDMed) with SS/PBCH block.
+  - For FR2, RMSI can be frequency division multiplexed (FDMed) with SS/PBCH block.
+  - SS/PBCH block and RMSI could be transmitted in the same slot for both TDM and FDM.
+- RMSI periodicity ( $P_{\text{RMSI}}$ ) is assumed as follows:
+  - 20ms for SSB set periodicity less than or equal to 20ms;
+  - Otherwise RMSI periodicity equals to SSB set periodicity.
+- The following mapping is used
+  - One RMSI transmission corresponds to one SS/PBCH block
+    - If  $L$  SS/PBCH block is transmitted, then  $L$  RMSI transmissions are required.
+  - One slot accommodates 2 RMSI transmissions.
+  - The offset of RMSI transmission can be set as {0, 2, 5, 7}ms with respect to every 20ms time point. In the evaluation, the offset value that allows the closest RMSI transmission to SS/PBCH block transmission is selected.
+
+For paging occasion,
+
+- The periodicity of paging occasion is the same as that of SSB set, and it is FDMed with an SS block.
+
+Figure 5.8.1.1-1 illustrates NR SS/PBCH block and RMSI transmission which employs the above mentioned mechanism.
+
+![Figure 5.8.1.1-1: Illustration of NR SS/PBCH block and RMSI transmission. The diagram shows a timeline of frames. The top part shows a frame with 'Half frame ( )' labels and an 'SSB periodicity' indicator. The bottom part shows a zoomed-in view of a frame containing SS/PBCH blocks (SSB) and RMSI transmission blocks (RMSI).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+Figure 5.8.1.1-1: Illustration of NR SS/PBCH block and RMSI transmission. The diagram shows a timeline of frames. The top part shows a frame with 'Half frame ( )' labels and an 'SSB periodicity' indicator. The bottom part shows a zoomed-in view of a frame containing SS/PBCH blocks (SSB) and RMSI transmission blocks (RMSI).
+
+Figure 5.8.1.1-1 Illustration of NR SS/PBCH block and RMSI transmission
+
+##### 5.8.1.1.1 Evaluation of sleep ratio
+
+Based on the above mechanisms, the sleep ratio per slot basis and per symbol basis are given as follows,
+
+$$Sleep\_ratio_{Slot\_based} = 1 - \frac{\lceil L/2 \rceil}{2^\mu \times P_{SSB}}$$
+
+$$Sleep\_ratio_{Symbol\_based} = 1 - \frac{L \times 2/7}{2^\mu \times P_{SSB}} - \alpha \frac{L/7}{2^\mu \times P_{RMSI}}$$
+
+where  $\lceil x \rceil$  indicates the ceiling of  $x$ ,  $\mu$  is the numerology (as defined in TS 38.211 [7], e.g.,  $\mu=0$  for 15 kHz SCS,  $\mu=1$  for 30 kHz SCS,  $\mu=3$  for 120 kHz SCS, and  $\mu=4$  for 240 kHz SCS),  $L$  is the number of SS/PBCH blocks in one SSB set,  $P_{SSB}$  is the SSB set periodicity,  $P_{RMSI}$  is the RMSI periodicity, and  $\alpha$  is the flag variable ( $\alpha=1$  for FR1, and  $\alpha=0$  for FR2).
+
+Evaluation results are shown in Table 5.8.1.1.1-1 and Table 5.8.1.1.1-2, respectively, for slot level and symbol level sleep ratio. It is observed that with SSB set period of 5ms, more than 80% of sleep ratio can be obtained by NR network; with SSB set period of larger than 10ms, more than 90% of sleep ratio can be obtained by NR network. Higher sleep ratio is expected with finer sleep granularity, e.g., in symbol level. Note that a subset of configurations in terms of number of SSB per set is used to derive the results.
+
+Therefore NR network can achieve high sleep ratio in unloaded case.
+
+Table 5.8.1.1.1-1 NR network sleep ratio in slot level
+
+| SSB configuration |                                          | SSB set periodicity $P_{SSB}$ |        |        |        |        |        |
+|-------------------|------------------------------------------|-------------------------------|--------|--------|--------|--------|--------|
+| SCS [kHz]         | Number of SS/PBCH block per SSB set, $L$ | 5ms                           | 10ms   | 20ms   | 40ms   | 80ms   | 160ms  |
+| 15kHz             | 1                                        | 80.00%                        | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% |
+|                   | 2                                        | 80.00%                        | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% |
+| 30kHz             | 1                                        | 95.00%                        | 97.50% | 98.75% | 99.38% | 99.69% | 99.84% |
+|                   | 4                                        | 80.00%                        | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% |
+| 120kHz            | 8                                        | 90.00%                        | 95.00% | 97.50% | 98.75% | 99.38% | 99.69% |
+|                   | 16                                       | 80.00%                        | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% |
+| 240kHz            | 16                                       | 90.00%                        | 95.00% | 97.50% | 98.75% | 99.38% | 99.69% |
+|                   | 32                                       | 80.00%                        | 90.00% | 95.00% | 97.50% | 98.75% | 99.38% |
+
+**Table 5.8.1.1.1-2 NR network sleep ratio in symbol level**
+
+| SSB configuration |                                          | SSB set periodicity $P_{\text{SSB}}$ |        |         |        |        |        |
+|-------------------|------------------------------------------|--------------------------------------|--------|---------|--------|--------|--------|
+| SCS [kHz]         | Number of SS/PBCH block per SSB set, $L$ | 5ms                                  | 10ms   | 20ms    | 40ms   | 80ms   | 160ms  |
+| 15kHz             | 1                                        | 93.57%                               | 96.43% | 97.86 % | 98.93% | 99.46% | 99.73% |
+|                   | 2                                        | 87.14%                               | 92.86% | 95.71 % | 97.86% | 98.93% | 99.46% |
+| 30kHz             | 1                                        | 96.79%                               | 98.21% | 98.93 % | 99.46% | 99.73% | 99.87% |
+|                   | 4                                        | 87.14%                               | 92.86% | 95.71 % | 97.86% | 98.93% | 99.46% |
+| 120kHz            | 8                                        | 94.29%                               | 97.14% | 98.57 % | 99.29% | 99.64% | 99.82% |
+|                   | 16                                       | 88.57%                               | 94.29% | 97.14 % | 98.57% | 99.29% | 99.64% |
+| 240kHz            | 16                                       | 94.29%                               | 97.14% | 98.57 % | 99.29% | 99.64% | 99.82% |
+|                   | 32                                       | 88.57%                               | 94.29% | 97.14 % | 98.57% | 99.29% | 99.64% |
+
+##### 5.8.1.1.2 Evaluation of sleep duration
+
+Based on the above mechanisms, evaluation results of sleep duration is provided in Table 5.8.1.1.2-1. It is observed that with SSB set period of 160 ms, more than 150ms sleep duration can be obtained by NR network. Therefore NR network can achieve long sleep duration in unloaded case.
+
+Therefore, NR meets network side energy efficiency requirement.
+
+**Table 5.8.1.1.2-1 NR network sleep duration (ms) in slot level**
+
+| SSB configuration |                                          | SSB set periodicity $P_{\text{SSB}}$ |      |       |       |       |        |
+|-------------------|------------------------------------------|--------------------------------------|------|-------|-------|-------|--------|
+| SCS [kHz]         | Number of SS/PBCH block per SSB set, $L$ | 5ms                                  | 10ms | 20ms  | 40ms  | 80ms  | 160ms  |
+| 15kHz             | 1                                        | 4.00                                 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 |
+|                   | 2                                        | 4.00                                 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 |
+| 30kHz             | 1                                        | 4.50                                 | 9.50 | 19.50 | 39.50 | 79.50 | 159.50 |
+|                   | 4                                        | 4.00                                 | 9.00 | 19.00 | 39.00 | 79.00 | 159.00 |
+| 120kHz            | 8                                        | 4.50                                 | 9.72 | 18.92 | 39.03 | 78.97 | 158.99 |
+|                   | 16                                       | 4.00                                 | 9.88 | 18.77 | 39.05 | 78.96 | 158.99 |
+| 240kHz            | 16                                       | 4.50                                 | 9.86 | 18.90 | 39.04 | 78.97 | 158.99 |
+|                   | 32                                       | 4.00                                 | 9.94 | 18.76 | 39.06 | 78.96 | 158.99 |
+
+#### 5.8.1.2 LTE
+
+The sleep ratio and sleep duration for LTE network under unloaded case are evaluated.
+
+For LTE, the FeMBMS/Unicast-mixed cell and MBMS-dedicated cell are employed in LTE network evaluation.
+
+For FeMBMS/Unicast-mixed cell,
+
+- Sub-frame 0 and 5 are always used as non-MBSFN sub-frame for synchronization and SI acquisition.
+- Sub-frame 4 and 9 are assumed to be configured as MBSFN sub-frames.
+- MBSFN sub-frames are assumed not to contain unicast control region.
+
+The above mechanism is illustrated in Figure 5.8.1.2-1.
+
+![Figure 5.8.1.2-1: Illustration of LTE FeMBMS/Unicast-mixed cell transmission. The diagram shows a sequence of 10 subframes (Subframe 0 to Subframe 9) for a Rel-14 FeMBMS/Unicast-mixed carrier. Subframe 0 is a Unicast subframe with Δf=15kHz. Subframes 1-4 are MBSFN subframes with Δf=15kHz. Subframe 5 is an MBSFN subframe with Δf=1.25kHz or Δf=7.5kHz. Subframes 6-9 are Unicast subframes with Δf=15kHz. A legend indicates: Unicast subframe with Δf=15kHz (blue outline), MBSFN subframe with Δf=15kHz (grey outline), MBSFN subframe with Δf=1.25kHz or Δf=7.5kHz (thick grey outline), Unicast control region (green), SSS (yellow), PSS (purple), PBCH (blue), and Paging occasion (red cross-hatch).](26d664119ad25250780f554633444e54_img.jpg)
+
+Figure 5.8.1.2-1: Illustration of LTE FeMBMS/Unicast-mixed cell transmission. The diagram shows a sequence of 10 subframes (Subframe 0 to Subframe 9) for a Rel-14 FeMBMS/Unicast-mixed carrier. Subframe 0 is a Unicast subframe with Δf=15kHz. Subframes 1-4 are MBSFN subframes with Δf=15kHz. Subframe 5 is an MBSFN subframe with Δf=1.25kHz or Δf=7.5kHz. Subframes 6-9 are Unicast subframes with Δf=15kHz. A legend indicates: Unicast subframe with Δf=15kHz (blue outline), MBSFN subframe with Δf=15kHz (grey outline), MBSFN subframe with Δf=1.25kHz or Δf=7.5kHz (thick grey outline), Unicast control region (green), SSS (yellow), PSS (purple), PBCH (blue), and Paging occasion (red cross-hatch).
+
+**Figure 5.8.1.2-1 Illustration of LTE FeMBMS/Unicast-mixed cell transmission**
+
+For MBMS-dedicated cell,
+
+- It is assumed that one non-MBSFN sub-frame is transmitted every 40ms.
+- Other subframes do not contain synchronization signal, PBCH and control region for unicast in unloaded case.
+
+The above mechanism is illustrated in Figure 5.8.1.2-2.
+
+![Figure 5.8.1.2-2: Illustration of LTE MBMS-dedicated cell transmission. Similar to Figure 5.8.1.2-1, it shows 10 subframes for a Rel-14 FeMBMS-dedicated carrier. An orange arrow points to Subframe 0 with the text 'At least one non-MBSFN subframe is transmitted every 40ms'. Subframe 0 contains the Unicast control region, SSS, PSS, and PBCH. Subframes 1-9 are shown as empty MBSFN subframes.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg)
+
+Figure 5.8.1.2-2: Illustration of LTE MBMS-dedicated cell transmission. Similar to Figure 5.8.1.2-1, it shows 10 subframes for a Rel-14 FeMBMS-dedicated carrier. An orange arrow points to Subframe 0 with the text 'At least one non-MBSFN subframe is transmitted every 40ms'. Subframe 0 contains the Unicast control region, SSS, PSS, and PBCH. Subframes 1-9 are shown as empty MBSFN subframes.
+
+**Figure 5.8.1.2-2 Illustration of LTE MBMS-dedicated cell transmission**
+
+##### 5.8.1.2.1 Evaluation of sleep ratio
+
+For FeMBMS/Unicast-mixed cell, 8 sub-frames are configured to be MBSFN sub-frames, and in the remaining 2 sub-frames, only PDCCH/SSS/PSSS and PBCH are transmitted. Therefore the sleep ratio of FeMBMS/Unicast-mixed cell is  $1 - 2/10 = 80\%$  for sub-frame level. Higher sleep ratio is expected with finer sleep granularity, e.g., in symbol level. To be specific, the sleep ratio of FeMBMS/Unicast-mixed cell is  $1 - (1 + 6 + 1 + 2) / 14 / 10 = 92.86\%$  if only one symbol is configured for PDCCH in each unicast sub-frame.
+
+For MBMS-dedicated cell, one non-MBSFN sub-frame is transmitted every 40ms, thus the sleep ratio in subframe level is  $1 - 1/40 = 97.5\%$ . Similarly, in symbol level the sleep ratio can be further improved to  $1 - (1 + 6) / 14 / 40 = 98.75\%$ .
+
+Table 5.8.1.2.1-1 demonstrates the evaluation results of sleep ratio for the above two cell types.
+
+Therefore LTE network can achieve high sleep ratio for FeMBMS/Unicast-mixed cell and MBMS-dedicated cell in unloaded case.
+
+**Table 5.8.1.2.1-1 LTE network sleep ratio in subframe level**
+
+| Cell type                 | Sleep ratio |
+|---------------------------|-------------|
+| FeMBMS/Unicast-mixed cell | 80%         |
+| MBMS-dedicated cell       | 93.75%      |
+
+##### 5.8.1.2.2 Evaluation of sleep duration
+
+For FeMBMS/Unicast-mixed cell, the longest sleep duration lasts from sub-frame #5 (after the PSS) to the start of next sub-frame #0 (before the PDCCH). In this case, the longest sleep duration is 4ms for sub-frame level sleep and  $0.5 + 4 = 4.5\text{ms}$  for symbol level sleep, respectively.
+
+For MBMS-dedicated cell, the longest sleep duration lasts from the end of PBCH in sub-frame#0 to the start of sub-frame#0 in the next 40ms cycle. In this case, the longest sleep duration of MBMS-dedicated cell is 39ms for sub-frame level sleep and  $3/14 + 39 = 39.2\text{ms}$  for symbol level sleep, respectively.
+
+Table 5.8.1.2.2-1 demonstrates the evaluation results of sleep duration for the above two cell types.
+
+It is observed that MBMS-dedicated cell can achieve as long sleep duration as 39 ms in unloaded case.
+
+Therefore LTE meets network side energy efficiency requirement for FeMBMS/Unicast-mixed cell and MBMS-dedicated cell.
+
+**Table 5.8.1.2.2-1 LTE network sleep duration (ms) in subframe level**
+
+| Cell type                 | Sleep duration (ms) |
+|---------------------------|---------------------|
+| FeMBMS/Unicast-mixed cell | 4.00                |
+| MBMS-dedicated cell       | 39.00               |
+
+### 5.8.2 Device side
+
+#### 5.8.2.1 NR
+
+The sleep ratio and sleep duration for NR UEs under unloaded case are evaluated.
+
+For NR, DRX is supported for UEs in idle, inactive and connected states.
+
+##### 5.8.2.1.1 Evaluation of sleep ratio
+
+For idle state and inactive state, the UE should monitor one paging occasion per discontinuous reception (DRX) cycle (which equals to the paging cycle), and the UE can use DRX to reduce power consumption. Before paging receiving, the SSB monitoring is needed. Also RRM measurement(s), including intra- and inter-cell shall be performed.
+
+The DRX cycle for idle state / inactive state UE consists of an "On Duration" during which the UE should perform SSB monitoring, paging monitoring and RRM measurement, and an "Off Duration" during which the UE can skip reception of downlink channels to save energy. It is illustrated in Figure 5.8.2.1.1-1.
+
+Therefore the sleep ratio is determined by the length of "On Duration" and the length of one paging cycle.
+
+![Figure 5.8.2.1.1-1: Illustration of DRX cycle in connected state. The diagram shows a red rectangular pulse representing the 'On duration' and a blue line representing the 'Off duration'. The 'On duration' is the time the UE is active, and the 'Off duration' is the time it is in sleep mode. The 'DRX Cycle' is the total duration of one 'On duration' plus one 'Off duration'.](1c140ee5d1a87186977da94a96bfa700_img.jpg)
+
+The diagram illustrates a Discontinuous Reception (DRX) cycle. It features a red rectangular pulse representing the 'On duration' where the UE is active, and a blue line representing the 'Off duration' where the UE is in sleep mode. The 'DRX Cycle' is indicated by a horizontal double-headed arrow spanning the duration of one 'On duration' followed by one 'Off duration'.
+
+Figure 5.8.2.1.1-1: Illustration of DRX cycle in connected state. The diagram shows a red rectangular pulse representing the 'On duration' and a blue line representing the 'Off duration'. The 'On duration' is the time the UE is active, and the 'Off duration' is the time it is in sleep mode. The 'DRX Cycle' is the total duration of one 'On duration' plus one 'Off duration'.
+
+**Figure 5.8.2.1.1-1 Illustration of DRX cycle in connected state**
+
+When DRX is used, the UE wakes up and receives SSB for synchronization, listens to PDCCH only on specific paging occasion defined in-terms of paging frame and subframe within period of  $N_{PC\_RF}$  radio frames defined by the DRX cycle (paging cycle) of the cell and performs RRM measurement. The UE can remain in sleep mode for remaining duration within DRX cycle.
+
+For synchronization, one SSB-burst set is assumed for short paging cycle (e.g., 320ms). Further, it is assumed that synchronization signal can be located in the same slot as paging-on slot and UE can finish network synchronization before paging monitoring. For longer paging cycle, one SSB-burst can still be assumed. In addition, to improve synchronization accuracy, the case of two SSB-burst sets is also evaluated. In this case, UE needs additional time up to one SSB cycle for SSB reception.
+
+For paging monitoring, a paging occasion *can consist of multiple time slots (e.g. slot or OFDM symbol) where paging DCI can be sent*. In the evaluation, it is assumed that one paging occasion consists of one slot. On the other hand, one paging cycle consists of one or multiple Paging Frames. One Paging Frame may contain one or multiple paging occasion(s) or starting point of a PO. In the evaluation, it is assumed that one Paging Frame contains one paging occasion and time for paging monitoring is not longer than that of one SSB burst.
+
+RRM measurement is based on SS/PBCH. In the evaluation, it is assumed that RRM measurement takes place in "On Duration" time, and the RRM measurement time is assumed to be 3.5ms for FR2 and 3ms for FR1 (see TS 38.133 [12]).
+
+In addition to the above procedure, transition time is needed for UE to switch on / off its components. 10ms transition time is assumed for evaluation; but further reduced value is possible.
+
+Based on the above analysis, the idle mode sleep ratio is evaluated with the configurations shown in Table 5.8.2.1.1-1. It is observed that more than 90% sleep ratio is achieved in idle mode by NR device.
+
+**Table 5.8.2.1.1-1 NR device sleep ratio in slot level (for idle / inactive mode)**
+
+|                       | Paging cycle $N_{PC\_RF} * 10$ (ms) | SCS(kHz) | SSB L | SSB reception time(ms) | SSB cycle (ms) | Number of SSB burst set | RRM measurement time per DRX (ms) | Transition time(ms) | Sleep ratio |
+|-----------------------|-------------------------------------|----------|-------|------------------------|----------------|-------------------------|-----------------------------------|---------------------|-------------|
+| RRC-Idle/<br>Inactive | 320                                 | 240      | 32    | 1                      | --             | 1                       | 3.5                               | 10                  | 95.5%       |
+|                       | 2560                                | 15       | 2     | 1                      | --             | 1                       | 3                                 | 10                  | 99.5%       |
+|                       | 2560                                | 15       | 2     | 1                      | 160            | 2                       | 3                                 | 10                  | 93.2%       |
+
+NOTE: For SSB period, "--" is assumed that SSB reception is during DRX-On time.
+
+For connected state, if there is no data transmission in either downlink or uplink direction, the DRX mode is switched on.
+
+The DRX cycle for connected state UE consists of an “On Duration” during which the UE should perform SSB monitoring, PDCCH monitoring (reflected as *DRX-onDurationTimer*), and RRM measurement, and an “Off Duration” during which the UE can skip reception of downlink channels to save energy. Also, transition time is assumed in “On Duration”. The connected mode sleep ratio for different DRX cycles is shown in Table 5.8.2.1.1-2. Therefore NR device can achieve high sleep ratio for both idle/inactive state and connected state in unloaded case.
+
+**Table 5.8.2.1.1-2 NR device sleep ratio in slot level (for connected mode)**
+
+|               | DRX cycle $T_{sc\_ms} * M_{sc}$ (ms) | Number of SSB burst set | DRX-onDurationTimer(ms) | RRM measurement time per DRX (ms) | Transition time(ms) | Sleep ratio |
+|---------------|--------------------------------------|-------------------------|-------------------------|-----------------------------------|---------------------|-------------|
+| RRC-Connected | 320                                  | 1                       | 2                       | 3.5                               | 10                  | 95.2%       |
+|               | 320                                  | 1                       | 10                      | 3                                 | 10                  | 92.8%       |
+|               | 2560                                 | 1                       | 100                     | 3                                 | 10                  | 95.6%       |
+|               | 10240                                | 1                       | 1600                    | 3                                 | 10                  | 84.2%       |
+
+NOTE: For SSB period, "--" is assumed that SSB reception is during DRX-On time.
+
+##### 5.8.2.1.2 Evaluation of sleep duration
+
+The sleep duration for NR UE in idle mode is 2546ms for paging cycle of 2560ms with the assumed parameters.
+
+The sleep duration of NR UE in connected state is 8627ms for paging cycle of 10240ms with the assumed parameters.
+
+Consequently NR device can achieve very long sleep duration in both idle mode and connected mode.
+
+It is therefore concluded that NR meets device side energy efficiency requirement.
+
+#### 5.8.2.2 LTE
+
+The sleep ratio and sleep duration for NR UEs under unloaded case are evaluated.
+
+For LTE, DRX is supported for UE in both idle and connected modes.
+
+##### 5.8.2.2.1 Evaluation of sleep ratio
+
+For idle mode, the UE should monitor one paging occasion per discontinuous reception (DRX) cycle (which equals to the paging cycle), and the UE can use DRX to reduce power consumption. Before paging receiving, the PSS/SSS monitoring is needed. Also RRM measurement(s), including intra- and inter-cell shall be performed.
+
+The DRX cycle for idle state / inactive state UE consists of an "On Duration" during which the UE should perform PSS/SSS monitoring, paging monitoring and RRM measurement, and an "Off Duration" during which the UE can skip reception of downlink channels to save energy. It is illustrated in Figure 5.8.2.1.1-1.
+
+Therefore the sleep ratio is determined by the length of "On Duration" and the length of one paging cycle.
+
+![Figure 5.8.2.2.1-1 Illustration of DRX cycle. The diagram shows a periodic signal with a square wave pattern. The 'On duration' is the time the signal is high, and the 'Off duration' is the time the signal is low. The 'DRX Cycle' is the total duration of one period (On + Off).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+Figure 5.8.2.2.1-1 Illustration of DRX cycle. The diagram shows a periodic signal with a square wave pattern. The 'On duration' is the time the signal is high, and the 'Off duration' is the time the signal is low. The 'DRX Cycle' is the total duration of one period (On + Off).
+
+**Figure 5.8.2.2.1-1 Illustration of DRX cycle**
+
+When DRX is used, the UE wakes up and receives PSS/SSS for synchronization, listens to PDCCH only on specific paging occasion defined in-terms of paging frame and subframe within period of  $N_{PC\_RF}$  radio frames defined by the DRX cycle (paging cycle) of the cell and performs RRM measurement. The UE can remain in sleep mode for remaining duration within DRX cycle.
+
+For synchronization, one PSS/SSS reception is assumed for short paging cycle (e.g., 320ms). Further, it is assumed that synchronization signal can be located in the same subframe as paging-on slot and UE can finish network synchronization before paging monitoring. Although 10ms is needed for one synchronization cycle, 6ms is assumed for calculation of sleep ratio and sleep duration when both SSS and PSS are received. For longer paging cycle, one PSS/SSS reception can still be assumed. In addition, to improve synchronization accuracy, the case with two-PSS/SSS receptions is also evaluated. In this case, UE needs additional time up to one synchronization cycle for PSS/SSS reception.
+
+For paging monitoring, in LTE, the similar configurations to NR can be assumed. Therefore the idle mode sleep ratio in subframe level is given by  $1 - 1/(10 \times N_{PC\_RF})$ , where  $N_{PC\_RF}$  is the paging cycle (number of radio frames). The default paging cycle (either cell-specific or UE-specific) includes {32, 64, 128, 256} radio frames.
+
+It is assumed that RRM measurement takes place in "On Duration" time, and the RRM measurement time is assumed to be 6ms (see TS 36.133 [13]).
+
+In addition to the above procedure, transition time is needed for UE to switch on / off its components. 10ms transition time is assumed for evaluation; but further reduced value is possible.
+
+Based on the above analysis, the idle mode sleep ratio is evaluated with the configurations shown in Table 5.8.2.2.1-1. It is observed that more than xx% sleep ratio is achieved in idle mode by LTE device.
+
+**Table 5.8.2.2.1-1 LTE device sleep ratio in subframe level (for idle mode)**
+
+|          | Paging cycle $N_{PC\_RF} \times 10$ (ms) | Synchronization reception time per cycle(ms) | Synchronization cycle(ms) | Number of synchronization | RRM measurement time per DRX (ms) | Transition time (ms) | DL/UL subframe ratio | Sleep ratio |
+|----------|------------------------------------------|----------------------------------------------|---------------------------|---------------------------|-----------------------------------|----------------------|----------------------|-------------|
+| RRC-Idle | 320                                      | 2                                            | 10*                       | 1                         | 6                                 | 10                   | 1                    | 93.1 %      |
+|          | 320                                      | 2                                            | 10*                       | 2                         | 6                                 | 10                   | 1                    | 90.0 %      |
+|          | 2560                                     | 2                                            | 10*                       | 1                         | 6                                 | 10                   | 1                    | 99.1 %      |
+|          | 2560                                     | 2                                            | 10*                       | 2                         | 6                                 | 10                   | 1                    | 98.8 %      |
+
+\*6ms is assumed in the calculation when SSS and PSS have both been received.
+
+For LTE UE in RRC connected mode, if there is no data transmission in either downlink or uplink direction, the DRX mode is switched on. The DRX cycle consists of an “On Duration” during which the UE should monitor PSS/SSS, the PDCCH and perform RRM measurement, and an “Off Duration” during which the UE can skip reception of downlink channels to save energy. Also, transition time is assumed in “On Duration”. The DRX cycle is configured by the LTE network in RRC Connection Setup request and RRC Connection Reconfiguration request.
+
+The connected mode sleep ratio for different DRX cycles is shown in Table 5.8.2.2.1-2. Therefore NR device can achieve high sleep ratio for both idle/inactive state and connected state in unloaded case.
+
+**Table 5.8.2.2.1-2 LTE device sleep ratio in subframe level (for connected mode)**
+
+|               | DRX cycle<br>$T_{\text{CYCLE\_SF}}$<br>(ms) | Synchronization<br>reception<br>time(ms) | Synchronization<br>cycle(ms) | Number of<br>synchronization | PDCCH<br>reception<br>time(ms) | RRM<br>measurement<br>time<br>per DRX<br>(ms) | DL/UL<br>subframe<br>ratio | Sleep<br>ratio |
+|---------------|---------------------------------------------|------------------------------------------|------------------------------|------------------------------|--------------------------------|-----------------------------------------------|----------------------------|----------------|
+| RRC-Connected | 320                                         | 2                                        | --                           | 1                            | 10                             | 6                                             | 1                          | 91.9%          |
+|               | 320                                         | 2                                        | 10                           | 2                            | 10                             | 6                                             | 0.5                        | 85.6%          |
+|               | 2560                                        | 2                                        | --                           | 1                            | 100                            | 6                                             | 1                          | 95.5%          |
+|               | 2560                                        | 2                                        | 10                           | 2                            | 100                            | 6                                             | 0.5                        | 91.2%          |
+|               | 10240                                       | 2                                        | --                           | 1                            | 1600                           | 6                                             | 1                          | 84.2%          |
+
+##### 5.8.2.2.2 Evaluation of sleep duration
+
+Based on LTE DRX mechanism for idle mode and connected mode, the sleep duration for idle mode is 2538ms for paging cycle of 2560ms with the assumed parameters, and for connected mode, it is 8624ms for paging cycle of 10240ms with the assumed parameters.
+
+Consequently LTE device can achieve very long sleep duration in both idle mode and connected mode.
+
+It is therefore concluded that LTE meets device side energy efficiency requirement.
+
+## 5.9 Mobility
+
+As defined in Report ITU-R M.2410 [4], Mobility is the maximum mobile station speed at which a defined QoS can be achieved (in km/h). The QoS is defined as normalized traffic channel link data rate.
+
+### 5.9.1 NR
+
+A wide range of antenna configurations and transmission schemes are considered for NR. Detailed evaluation assumptions and results can be found in Annex B.4.2.
+
+#### 5.9.1.1 Indoor Hotspot – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) and evaluation configuration B (carrier frequency = 30 GHz) with either 12TRxP or 36TRxP cases are applied for the evaluations of Indoor Hotspot– eMBB test environment for NR. Both NR FDD and TDD are evaluated.
+
+##### 5.9.1.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration A with 12TRxP are provided in Table 5.9.1.1.1-1.
+
+**Table 5.9.1.1.1-1 NR mobility in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 15                        | 1.5                        | LOS               | 3                 | 1.97                                                 | LOS               | 3                 | 2.13                                                 |
+|                                  |                           |                            | NLOS              | 4                 | 1.78                                                 | NLOS              | 4                 | 1.84                                                 |
+| 1x2 SIMO                         | 30                        |                            | LOS               | 1                 | 2.8                                                  | LOS               | 1                 | 2.8                                                  |
+|                                  |                           |                            | NLOS              | 1                 | 2.5                                                  | NLOS              | 1                 | 2.5                                                  |
+| 2x8 SU-MIMO                      | 30                        |                            | LOS               | /                 | /                                                    | LOS               | /                 | /                                                    |
+|                                  |                           |                            | NLOS              | 1                 | 3.85                                                 | NLOS              | /                 | /                                                    |
+| 1x1 SU-SISO                      | 30                        |                            | LOS               | /                 | /                                                    | LOS               | /                 | /                                                    |
+|                                  |                           |                            | NLOS              | 1                 | 2.18                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 3.21                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 1                 | 2.99                                                 | NLOS              | /                 | /                                                    |
+| 1x16 SIMO                        | 15                        |                            | LOS               | 1                 | 2.27                                                 | LOS               | 1                 | 2.43                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.65                                                 | NLOS              | 1                 | 1.72                                                 |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 30                        | DDDSU           | 1.5                        | LOS               | 1                 | 1.94                                                 | LOS               | 1                 | 1.95                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.59                                                 | NLOS              | 1                 | 1.60                                                 |
+| 1x8 SIMO                         | 15                        | DSUUD           |                            | LOS               | 1                 | 2.07                                                 | LOS               | 1                 | 2.08                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.78                                                 | NLOS              | 1                 | 1.79                                                 |
+| 1x2 SIMO                         | 30                        | UUUUU           |                            | LOS               | 1                 | 2.3                                                  | LOS               | 1                 | 2.3                                                  |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.0                                                  | NLOS              | 1                 | 2.0                                                  |
+| 2x8 SU-MIMO                      | 30                        | DDDDDDDSU       | 1.5                        | NLOS              | 1                 | 3.85                                                 | NLOS              | /                 | /                                                    |
+| 11 SU-SISO                       | 30                        | UUUUU           |                            | NLOS              | 1                 | 1.78                                                 | NLOS              | /                 | /                                                    |
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration A with 36TRxP are provided in Table 5.9.1.1.1-2.
+
+It is observed that NR fulfill the mobility requirement in evaluation configuration A.
+
+**Table 5.9.1.1.1-2 NR mobility in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz, for 36TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 2x8 SU-MIMO                      | 15                        | 1.5                        | NLOS              | 1                 | 1.78                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 1                 | 1.77                                                 | NLOS              | /                 | /                                                    |
+
+##### **5.9.1.1.2 Evaluation configuration B (CF = 30 GHz)**
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration B with 12TRxP are provided in Table 5.9.1.1.2-1.
+
+**Table 5.9.1.1.2-1 NR mobility in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 12TRxP)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|
+| 1x4 SIMO                         | 60                        |                            | NLOS              | 1                 | 2.84                                                 |
+| 4x8 SU-MIMO                      | 120                       | 1.5                        | LOS               | 1                 | 4.76                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 3.01                                                 |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|
+| 2x8 SU-MIMO                      | 60                        | UUUUU           | 1.5                        | NLOS              | 1                 | 4.48                                                 |
+| 2x8 SU-MIMO                      | 120                       | UUUUU           |                            | NLOS              | 1                 | 4.27                                                 |
+| 1x8 SIMO                         | 120                       | DDDSU           | 1.5                        | LOS               | 1                 | 2.15                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.14                                                 |
+
+The evaluation results of mobility for NR for evaluation configuration B with 36TRxP are provided in Table 5.9.1.1.2-2.
+
+It is observed that NR fulfills the mobility requirement in evaluation configuration B.
+
+**Table 5.9.1.1.2-2 NR mobility in Indoor Hotspot – eMBB  
+(Evaluation configuration B, CF=30 GHz, for 36TRxP)**
+
+###### **(a) NR TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|
+| 2x8 SU-MIMO                      | 60                        | UUUUU           | 1.5                        | NLOS              | 1                 | 4.13                                                 |
+| 2x8 SU-MIMO                      | 120                       | UUUUU           |                            | NLOS              | 1                 | 3.91                                                 |
+
+#### 5.9.1.2 Dense Urban – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) and evaluation configuration B (carrier frequency = 30 GHz) are applied for the evaluations of Dense Urban – eMBB test environment for NR.
+
+##### 5.9.1.2.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration A are provided in Table 5.9.1.2.1-1.
+
+It is observed that NR fulfills the mobility requirement in evaluation configuration A.
+
+**Table 5.9.1.2.1-1 NR mobility in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 15                        | 1.12                       | LOS               | 4                 | 2.07                                                 | LOS               | 4                 | 2.19                                                 |
+|                                  |                           |                            | NLOS              | 5                 | 1.87                                                 | NLOS              | 5                 | 1.97                                                 |
+| 1x2 SIMO                         | 30                        |                            | LOS               | 1                 | 2.6                                                  | LOS               | 1                 | 2.6                                                  |
+|                                  |                           |                            | NLOS              | 1                 | 1.8                                                  | NLOS              | 1                 | 1.8                                                  |
+| 1x4 SIMO                         | 30                        |                            | NLOS              | 1                 | 1.14                                                 | NLOS              | 2                 | 1.41                                                 |
+|                                  |                           |                            | LOS               | 1                 | 1.37                                                 | LOS               | 1                 | 1.47                                                 |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 3                 | 3.79                                                 | NLOS              | 1                 | 3.55                                                 |
+| 2x8 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 1.92                                                 | NLOS              | /                 | /                                                    |
+| 1x1 SISO                         | 30                        |                            | NLOS              | 1                 | 1.56                                                 | NLOS              | /                 | /                                                    |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 30                        | DDDSU           | 1.12                       | LOS               | 1                 | 2.17                                                 | LOS               | 1                 | 2.06                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.82                                                 | NLOS              | 1                 | 1.79                                                 |
+| 1x8 SIMO                         | 15                        | DSUUD           |                            | LOS               | 1                 | 2.33                                                 | LOS               | 1                 | 2.29                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.03                                                 | NLOS              | 1                 | 2.00                                                 |
+| 1x2 SIMO                         | 30                        | UUUUU           |                            | LOS               | 1                 | 2.2                                                  | LOS               | 1                 | 2.2                                                  |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.5                                                  | NLOS              | 1                 | 1.5                                                  |
+| 2x8 SU-MIMO                      | 30                        | DDDDDDD<br>SUU  |                            | NLOS              | 1                 | 4.58                                                 | NLOS              | /                 | /                                                    |
+| 1x1 SISO                         | 30                        | UUUUU           |                            | NLOS              | 1                 | 1.28                                                 | NLOS              | /                 | /                                                    |
+| 1x4 SIMO                         | 30                        | UUUUU           |                            | NLOS              | /                 | /                                                    | NLOS              | 1                 | 1.57                                                 |
+
+##### **5.9.1.2.2 Evaluation configuration B (CF = 30 GHz)**
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration B are provided in Table 5.9.1.2.2-1.
+
+It is observed that NR fulfills the mobility requirement in evaluation configuration B.
+
+**Table 5.9.1.2.2-1 NR mobility in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |  |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|--|
+| 1x4 SIMO                         | 60                        | 1.12                       | NLOS              | 1                 | 1.24                                                 |  |
+| 2x8 MIMO                         | 60                        |                            | NLOS              | 1                 | 3.22                                                 |  |
+| 2x8 MIMO                         | 120                       |                            | NLOS              | 1                 | 2.67                                                 |  |
+| 1x8 SIMO                         | 60                        |                            | LOS               | 1                 | 1.62                                                 |  |
+|                                  |                           |                            | NLOS              | 1                 | 1.3                                                  |  |
+| 4x8 MIMO                         | 120                       |                            | LOS               | 1                 | 2.09                                                 |  |
+|                                  |                           |                            | NLOS              | 1                 | 1.23                                                 |  |
+
+#### 5.9.1.3 Rural – eMBB
+
+Evaluation configuration A (carrier frequency = 700 MHz) and evaluation configuration B (carrier frequency = 4 GHz) are applied for the evaluations of Rural – eMBB test environment for NR. Both NR FDD and TDD are evaluated. The mobility class of 120km/h and 500km/h are considered.
+
+##### 5.9.1.3.1 Evaluation configuration A (CF = 700 MHz)
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration A for mobility class of 120km/h are provided in Table 5.9.1.3.1-1.
+
+**Table 5.9.1.3.1-1 NR mobility in Rural – eMBB  
+(Evaluation configuration A, CF=700 MHz, Mobility class of 120km/h)**
+
+###### (a) NR FDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |  |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|--|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |  |
+| 1x4 SIMO (Scheduler 1)           | 15                        | 0.8                        | LOS               | 3                 | 2.49                                                 | LOS               | 3                 | 3.0                                                  |  |
+|                                  |                           |                            | NLOS              | 5                 | 1.71                                                 | NLOS              | 5                 | 2.14                                                 |  |
+| 1x2 SIMO                         | 15                        |                            | LOS               | 1                 | 1.80                                                 | LOS               | 1                 | 1.80                                                 |  |
+|                                  |                           |                            | NLOS              | 1                 | 1.00                                                 | NLOS              | 1                 | 1.00                                                 |  |
+| 1x4 SIMO (Scheduler 2)           | 15                        |                            | NLOS              | /                 | /                                                    | NLOS              | 1                 | 1.75                                                 |  |
+| 2x2 SU-MIMO                      | 15                        |                            | NLOS              | 2                 | 1.79                                                 | NLOS              | 1                 | 1.54                                                 |  |
+| 1x8 SIMO                         | 15                        |                            | LOS               | 1                 | 2.89                                                 | LOS               | 1                 | 2.91                                                 |  |
+|                                  |                           |                            | NLOS              | 1                 | 2.86                                                 | NLOS              | 1                 | 2.90                                                 |  |
+| 2x8 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 2.46                                                 | NLOS              | /                 | /                                                    |  |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 1                 | 2.46                                                 | NLOS              | /                 | /                                                    |  |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |  |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|--|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |  |
+| 1x4 SIMO                         | 15                        | DDDSU           | 0.8                        | LOS               | 1                 | 2.63                                                 | LOS               | 1                 | 2.63                                                 |  |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.10                                                 | NLOS              | 1                 | 2.09                                                 |  |
+| 1x2 SIMO                         | 15                        | UUUUU           |                            | LOS               | 1                 | 1.60                                                 | LOS               | 1                 | 1.60                                                 |  |
+|                                  |                           |                 |                            | NLOS              | 1                 | 0.85                                                 | NLOS              | 1                 | 0.85                                                 |  |
+| 2x2 SU-MIMO                      | 15                        | DDDSU           |                            | NLOS              | 1                 | 2.01                                                 | NLOS              | /                 | /                                                    |  |
+| 1x8 SIMO                         | 15                        | DSUUD           |                            | LOS               | 1                 | 2.81                                                 | LOS               | 1                 | 2.82                                                 |  |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.77                                                 | NLOS              | 1                 | 2.81                                                 |  |
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration A for mobility class of 500km/h are provided in Table 5.9.1.3.1-2.
+
+It is observed that NR fulfills the mobility requirement under both 120km/h and 500km/h.
+
+**Table 5.9.1.3.1-2 NR mobility in Rural – eMBB  
+(Evaluation configuration A, CF=700 MHz, Mobility class of 500km/h)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 30                        | 0.45                       | LOS               | 2                 | 2.53                                                 | LOS               | 2                 | 2.53                                                 |
+|                                  |                           |                            | NLOS              | 4                 | 1.53                                                 | NLOS              | 4                 | 1.54                                                 |
+| 1x2 SIMO                         | 15                        |                            | LOS               | 1                 | 1.40                                                 | LOS               | 1                 | 1.40                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 0.70                                                 | NLOS              | 1                 | 0.70                                                 |
+| 1x4 SIMO                         | 15                        |                            | NLOS              | /                 | /                                                    | NLOS              | 1                 | 0.86                                                 |
+| 2x2 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 1.92                                                 | NLOS              | /                 | /                                                    |
+| 2x2 SU-MIMO                      | 30                        |                            | NLOS              | 1                 | 1.28                                                 | NLOS              | 1                 | 1.21                                                 |
+| 1x8 SIMO                         | 30                        |                            | LOS               | 1                 | 2.40                                                 | LOS               | 1                 | 2.43                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 2.39                                                 | NLOS              | 1                 | 2.40                                                 |
+| 2x8 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 2.73                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 1                 | 2.46                                                 | NLOS              | /                 | /                                                    |
+
+###### **(b) NR TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 30                        | DDDSU           | 0.45                       | LOS               | 1                 | 2.39                                                 | LOS               | 1                 | 2.39                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.88                                                 | NLOS              | 1                 | 1.87                                                 |
+| 1x2 SIMO                         | 15                        | UUUUU           |                            | LOS               | 1                 | 1.10                                                 | LOS               | 1                 | 1.10                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 0.60                                                 | NLOS              | 1                 | 0.60                                                 |
+| 2x2 SU-MIMO                      | 15                        | DDDSU           |                            | LOS               | /                 | /                                                    | LOS               | /                 | /                                                    |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.92                                                 | NLOS              | /                 | /                                                    |
+| 1x8 SIMO                         | 30                        | DSUUD           |                            | LOS               | 1                 | 2.30                                                 | LOS               | 1                 | 2.33                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.28                                                 | NLOS              | 1                 | 2.29                                                 |
+
+##### **5.9.1.3.2 Evaluation configuration B (CF = 4 GHz)**
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration B for mobility class of 120km/h are provided in Table 5.9.1.3.2-1.
+
+**Table 5.9.1.3.2-1 NR mobility in Rural – eMBB  
+(Evaluation configuration B, CF=4 GHz, Mobility class of 120km/h)**
+
+###### **(a) NR FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO (Scheduler 1)           | 30                        | 0.8                        | LOS               | 2                 | 2.08                                                 | LOS               | 3                 | 2.13                                                 |
+|                                  |                           |                            | NLOS              | 5                 | 1.56                                                 | NLOS              | 5                 | 1.6                                                  |
+| 1x4 SIMO (Scheduler 2)           | 30                        |                            | NLOS              | /                 | /                                                    | NLOS              | 1                 | 1.08                                                 |
+| 1x8 SIMO                         | 30                        |                            | LOS               | 1                 | 1.87                                                 | LOS               | 1                 | 1.86                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.74                                                 | NLOS              | 1                 | 1.73                                                 |
+| 2x8 SU-MIMO                      | 15                        |                            | NLOS              | 1                 | 2.75                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 30                        |                            | NLOS              | 2                 | 2.57                                                 | NLOS              | 1                 | 2.41                                                 |
+| 1x1 SISO                         | 30                        |                            | LOS               | 1                 | 1.32                                                 | LOS               | /                 | /                                                    |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 30                        | DDDSU           | 0.8                        | LOS               | 1                 | 1.57                                                 | LOS               | 1                 | 1.52                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.18                                                 | NLOS              | 1                 | 1.16                                                 |
+| 1x8 SIMO                         | 30                        | DSUUD           | 0.8                        | LOS               | 1                 | 1.79                                                 | LOS               | 1                 | 1.78                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.66                                                 | NLOS              | 1                 | 1.65                                                 |
+| 1x1 SISO                         | 30                        | UUUUU           | 0.8                        | LOS               | 1                 | 1.02                                                 | LOS               | /                 | /                                                    |
+
+The evaluation results of mobility for NR FDD and NR TDD for evaluation configuration B for mobility class of 500km/h are provided in Table 5.9.1.3.2-2.
+
+It is observed that NR fulfills the mobility requirement under both 120km/h and 500km/h.
+
+**Table 5.9.1.3.2-2 NR mobility in Rural – eMBB**  
+(Evaluation configuration B, CF=4 GHz, Mobility class of 500km/h)
+
+###### (a) NR FDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 60                        | 0.45                       | LOS               | 2                 | 1.35                                                 | LOS               | 2                 | 1.37                                                 |
+|                                  |                           |                            | NLOS              | 4                 | 0.91                                                 | NLOS              | 4                 | 0.91                                                 |
+| 1x8 SIMO                         | 30                        | 0.45                       | LOS               | 1                 | 1.43                                                 | LOS               | 1                 | 1.38                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.11                                                 | NLOS              | 1                 | 1.08                                                 |
+| 2x8 SU-MIMO                      | 15                        | 0.45                       | NLOS              | 1                 | 2.09                                                 | NLOS              | /                 | /                                                    |
+| 2x8 SU-MIMO                      | 30                        | 0.45                       | NLOS              | 2                 | 2.01                                                 | NLOS              | /                 | /                                                    |
+| 1x1 SISO                         | 30                        | 0.45                       | LOS               | 1                 | 0.82                                                 | LOS               | /                 | /                                                    |
+
+###### (b) NR TDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 60                        | DDDSU           | 0.45                       | LOS               | 1                 | 1.22                                                 | LOS               | 1                 | 1.22                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 0.84                                                 | NLOS              | 1                 | 0.83                                                 |
+| 1x8 SIMO                         | 30                        | DSUUD           | 0.45                       | LOS               | 1                 | 1.37                                                 | LOS               | 1                 | 1.31                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.06                                                 | NLOS              | 1                 | 1.03                                                 |
+| 1x1 SISO                         | 30                        | UUUUU           | 0.45                       | LOS               | 1                 | 0.64                                                 | LOS               | /                 | /                                                    |
+
+### 5.9.2 LTE
+
+Several configurations are evaluated for LTE. Detailed evaluation assumptions and results can be found in Annex B.4.2.
+
+#### 5.9.2.1 Indoor Hotspot – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) is applied for the evaluations of Indoor Hotspot – eMBB test environment for LTE. LTE FDD is evaluated. The mobility class of 10 km/h is considered.
+
+##### 5.9.2.1.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of mobility for LTE FDD for evaluation configuration A are provided in Table 5.9.2.1.1-1.
+
+It is observed that LTE fulfills the mobility requirement in evaluation configuration A.
+
+**Table 5.9.2.1.1-1 LTE mobility in Indoor Hotspot – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x2 SIMO                         | 15                        | 1.5                        | LOS               | 1                 | 2.6                                                  | LOS               | 1                 | 2.6                                                  |
+|                                  |                           |                            | NLOS              | 1                 | 1.9                                                  | NLOS              | 1                 | 1.9                                                  |
+
+#### 5.9.2.2 Dense Urban – eMBB
+
+Evaluation configuration A (carrier frequency = 4 GHz) is applied for the evaluations of Dense Urban – eMBB test environment for LTE. Both LTE FDD and TDD are evaluated. The mobility class of 30 km/h is considered.
+
+##### 5.9.2.2.1 Evaluation configuration A (CF = 4 GHz)
+
+The evaluation results of mobility for LTE FDD and TDD for evaluation configuration A are provided in Table 5.9.2.2.1-1.
+
+It is observed that LTE fulfills the mobility requirement in evaluation configuration A.
+
+**Table 5.9.2.2.1-1 LTE mobility in Dense Urban – eMBB  
+(Evaluation configuration A, CF=4 GHz)**
+
+###### **(a) LTE FDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 15                        | 1.12                       | LOS               | 1                 | 1.99                                                 | LOS               | 1                 | 1.88                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.81                                                 | NLOS              | 1                 | 1.77                                                 |
+
+###### **(b) LTE TDD**
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x8 SIMO                         | 15                        | DSUUD           | 1.12                       | LOS               | 1                 | 1.91                                                 | LOS               | 1                 | 1.81                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.74                                                 | NLOS              | 1                 | 1.70                                                 |
+
+#### 5.9.2.3 Rural – eMBB
+
+Evaluation configuration A (carrier frequency = 700 MHz) is applied for the evaluations of Rural – eMBB test environment for LTE. Both LTE FDD and TDD are evaluated. The mobility class of 120 km/h and 500 km/h are considered.
+
+##### 5.9.2.3.1 Evaluation configuration A (CF = 700 MHz)
+
+The evaluation results of mobility for LTE FDD and TDD for evaluation configuration A for mobility class of 120km/h are provided in Table 5.9.2.3.1-1.
+
+**Table 5.9.2.3.1-1 LTE mobility in Rural – eMBB**  
+**(Evaluation configuration A, CF=700 MHz, Mobility class of 120km/h)**
+
+###### (a) LTE FDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 15                        | 0.8                        | LOS               | 1                 | 2.79                                                 | LOS               | 1                 | 2.79                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 2.20                                                 | NLOS              | 1                 | 2.19                                                 |
+| 1x2 SIMO                         | 15                        | 0.8                        | LOS               | 1                 | 1.70                                                 | LOS               | 1                 | 1.70                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.00                                                 | NLOS              | 1                 | 1.00                                                 |
+| 1x8 SIMO                         | 15                        | 0.8                        | LOS               | 1                 | 2.91                                                 | LOS               | 1                 | 2.90                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 2.75                                                 | NLOS              | 1                 | 2.73                                                 |
+
+###### (b) LTE TDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 15                        | DSUDD           | 0.8                        | LOS               | 1                 | 2.49                                                 | LOS               | 1                 | 2.49                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.96                                                 | NLOS              | 1                 | 1.94                                                 |
+| 1x8 SIMO                         | 15                        | DSUUD           | 0.8                        | LOS               | 1                 | 2.79                                                 | LOS               | 1                 | 2.79                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 2.64                                                 | NLOS              | 1                 | 2.63                                                 |
+
+The evaluation results of mobility for LTE FDD and TDD for evaluation configuration A for mobility class of 500km/h are provided in Table 5.9.2.3.1-2.
+
+It is observed that LTE fulfills the mobility requirement under both 120km/h and 500km/h.
+
+**Table 5.9.2.3.1-2 LTE mobility in Rural – eMBB**  
+**(Evaluation configuration A, CF=700 MHz, Mobility class of 500km/h)**
+
+###### (a) LTE FDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 15                        | 0.45                       | LOS               | 1                 | 2.59                                                 | LOS               | 1                 | 2.59                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.94                                                 | NLOS              | 1                 | 1.93                                                 |
+| 1x2 SIMO                         | 15                        | 0.45                       | LOS               | 1                 | 1.05                                                 | LOS               | 1                 | 1.05                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 0.60                                                 | NLOS              | 1                 | 0.60                                                 |
+| 1x8 SIMO                         | 15                        | 0.45                       | LOS               | 1                 | 2.39                                                 | LOS               | 1                 | 2.38                                                 |
+|                                  |                           |                            | NLOS              | 1                 | 1.82                                                 | NLOS              | 1                 | 1.82                                                 |
+
+###### (b) LTE TDD
+
+| Scheme and antenna configuration | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement (bit/s/Hz) | Channel model A   |                   |                                                      | Channel model B   |                   |                                                      |
+|----------------------------------|---------------------------|-----------------|----------------------------|-------------------|-------------------|------------------------------------------------------|-------------------|-------------------|------------------------------------------------------|
+|                                  |                           |                 |                            | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) | Channel condition | Number of samples | Normalized traffic channel link data rate (bit/s/Hz) |
+| 1x4 SIMO                         | 15                        | DSUDD           | 0.45                       | LOS               | 1                 | 2.31                                                 | LOS               | 1                 | 2.31                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.73                                                 | NLOS              | 1                 | 1.72                                                 |
+| 1x8 SIMO                         | 15                        | DSUUD           | 0.45                       | LOS               | 1                 | 2.29                                                 | LOS               | 1                 | 2.29                                                 |
+|                                  |                           |                 |                            | NLOS              | 1                 | 1.75                                                 | NLOS              | 1                 | 1.75                                                 |
+
+## 5.10 Mobility interruption time
+
+As defined in Report ITU-R M.2410 [4], mobility interruption time is the shortest time duration supported by the system during which a user terminal cannot exchange user plane packets with any base station during mobility transitions.
+
+The mobility interruption time includes the time required to execute any radio access network procedure, radio resource control signalling protocol, or other message exchanges between the mobile station and the radio access network, as applicable to the candidate RIT/SRIT.
+
+### 5.10.1 NR
+
+#### 5.10.1.1 Scenarios
+
+For NR Rel-15, the mobility interruption time is evaluated for the following scenarios:
+
+- Beam mobility;
+- CA mobility.
+
+#### 5.10.1.2 Beam mobility
+
+When moving within the same cell, the transmit-receive beam pair of the UE may need to be changed.
+
+For DL data transmission during UE mobility, gNB can configure different beams for this UE at different slots. It ensures appropriate transmit beam allocation to the UE for continuous DL transmission. Therefore DL data packet transmission is kept during beam pair switching at different slots.
+
+For UL data transmission, PUSCH is sent using the beam configured by SRI (SRS resource indicator) by gNB. Accordingly, an appropriate gNB-side beam is selected for UL data reception. gNB may select different beams at different slots depending on the UE mobility. Therefore UL data packet transmission is kept during beam pair switching at different slots.
+
+Based on the above analysis, the UE can always exchange user plane packets with gNB during the mobility transitions. Therefore, 0ms mobility interruption time is achieved by NR for this scenario.
+
+#### 5.10.1.3 CA Mobility
+
+When moving within the same PCell with CA enabled, the set of configured SCells of the UE may change. The SCell addition procedure and SCell release procedures can occur.
+
+During these procedures, the UE can always exchange user plane packets with the gNB during transitions, because the data transmission between the UE and the PCell is kept. Therefore, 0ms mobility interruption time is achieved by NR for this case.
+
+### 5.10.2 LTE
+
+#### 5.10.2.1 Scenarios
+
+For LTE Rel-15, the mobility interruption time is evaluated under the following scenarios.
+
+- PCell mobility;
+- DC mobility.
+
+#### 5.10.2.2 PCell mobility
+
+In Make-Before-Break handover, the connection to the source eNB is not released until DL synchronization is completed at the target eNB. For intra-frequency handover case, a dual RX UE can receive data from the source eNB and tracking RS from the target at the same time, while synchronizing with target eNB. Nevertheless, the UE releases the serving cell before performing the RACH procedure.
+
+On the other hand, if the source eNB, target eNB and UE are synchronized, the UE may be able to obtain the target eNB timing advance (TA) without explicit TA command, so that a RACH-less handover can be applied: in some scenarios such as no or negligible UE TA difference between the source and target eNB, the UE can use its original TA for the source eNB to transmit the data to the target eNB. In this case, the delay of the RACH procedure can be avoided.
+
+Therefore, by combining Make-Before-Break and RACH-less handover for a dual RX UE in the scenario where there is no or negligible UE TA difference between the source and the target cell, the 0ms mobility interruption time is achieved by LTE for the PCell mobility scenario.
+
+#### 5.10.2.3 DC Mobility
+
+When moving within the same MeNB with DC enabled, the SeNB of the UE may change. The SeNB addition procedure and SeNB release procedure are shown below (see also Section 10.1.2.8 in 3GPP TS 36.300 [14]).
+
+It is observed that during these procedures, the UE can always exchange user plane packets with MeNB during transitions. Therefore 0ms mobility interruption time is achieved by LTE for the DC mobility scenario.
+
+## SeNB Addition
+
+The SeNB Addition procedure is initiated by the MeNB and is used to establish a UE context at the SeNB in order to provide radio resources from the SeNB to the UE. This procedure is used to add at least the first cell (PSCell) of the SCG. Figure 5.10.2.2-1 shows the SeNB Addition procedure. The detailed description of each step is found in Section 10.1.2.8.1 in 3GPP TS 36.300 [14]
+
+![Sequence diagram of the SeNB Addition procedure. The diagram shows interactions between UE, MeNB, SeNB, S-GW, and MME. The procedure starts with the MeNB sending an SeNB addition Request to the SeNB. The SeNB responds with an SeNB addition Request acknowledgement. The MeNB then sends an RRC Connection Reconfiguration to the UE. The UE responds with an RRC Connection Reconfiguration Complete. The MeNB sends a Random Access Procedure to the UE. The SeNB sends a SeNB Reconfiguration Complete to the MeNB. The MeNB sends an SN Status transfer to the SeNB. The SeNB sends a Data Forwarding message to the S-GW. The MeNB initiates a Path Update procedure with the S-GW and MME. The S-GW sends an E-RAB Modification Indication to the MME. The MME sends a Bearer Modification to the S-GW. The S-GW sends an End Marker Packet to the SeNB. The S-GW sends an E-RAB Modification Confirmation to the MeNB.](00942e7d6db56fd4fbd5f45bdbad7fdb_img.jpg)
+
+```
+
+sequenceDiagram
+    participant UE
+    participant MeNB
+    participant SeNB
+    participant S-GW
+    participant MME
+
+    Note right of MeNB: 1. SeNB addition Request (carry SCG-ConfigInfo)
+    MeNB->>SeNB: 1. SeNB addition Request (carry SCG-ConfigInfo)
+    Note right of SeNB: 2. SeNB addition Request acknowledgement (carry SCG-Config)
+    SeNB-->>MeNB: 2. SeNB addition Request acknowledgement (carry SCG-Config)
+    Note right of MeNB: 3. RRC Connection Reconfiguration
+    MeNB->>UE: 3. RRC Connection Reconfiguration
+    Note right of UE: 4. RRC Connection Reconfiguration Complete
+    UE-->>MeNB: 4. RRC Connection Reconfiguration Complete
+    Note right of MeNB: 5. SeNB Reconfiguration Complete
+    MeNB->>SeNB: 5. SeNB Reconfiguration Complete
+    Note right of UE: 6. Random Access Procedure
+    MeNB->>UE: 6. Random Access Procedure
+    Note right of MeNB: 7. SN Status transfer
+    MeNB->>SeNB: 7. SN Status transfer
+    Note right of SeNB: 8. Data Forwarding
+    SeNB-->>S-GW: 8. Data Forwarding
+    Note right of MeNB: Path Update procedure
+    MeNB->>S-GW: 9. E-RAB Modification Indication
+    S-GW->>MME: 10. Bearer Modification
+    Note right of S-GW: 11. End Marker Packet
+    S-GW-->>SeNB: 11. End Marker Packet
+    Note right of S-GW: 12. E-RAB Modification Confirmation
+    S-GW-->>MeNB: 12. E-RAB Modification Confirmation
+  
+```
+
+Sequence diagram of the SeNB Addition procedure. The diagram shows interactions between UE, MeNB, SeNB, S-GW, and MME. The procedure starts with the MeNB sending an SeNB addition Request to the SeNB. The SeNB responds with an SeNB addition Request acknowledgement. The MeNB then sends an RRC Connection Reconfiguration to the UE. The UE responds with an RRC Connection Reconfiguration Complete. The MeNB sends a Random Access Procedure to the UE. The SeNB sends a SeNB Reconfiguration Complete to the MeNB. The MeNB sends an SN Status transfer to the SeNB. The SeNB sends a Data Forwarding message to the S-GW. The MeNB initiates a Path Update procedure with the S-GW and MME. The S-GW sends an E-RAB Modification Indication to the MME. The MME sends a Bearer Modification to the S-GW. The S-GW sends an End Marker Packet to the SeNB. The S-GW sends an E-RAB Modification Confirmation to the MeNB.
+
+Figure 5.10.2.2-1: SeNB Addition procedure
+
+### SeNB Release
+
+The SeNB Release procedure may be initiated either by the MeNB or by the SeNB and is used to initiate the release of the UE context at the SeNB.
+
+It does not necessarily need to involve signalling towards the UE, e.g., RRC connection re-establishment due to Radio Link Failure in MeNB.
+
+### **MeNB initiated SeNB Release**
+
+![Sequence diagram for MeNB initiated SeNB Release procedure. Lifelines: UE, MeNB, SeNB, S-GW, MME. Steps: 1. SeNB Release Request (MeNB to SeNB), 2. RRC Connection Reconfiguration (MeNB to UE), 3. RRC Connection Reconfiguration Complete (UE to MeNB), 4. SN Status transfer (MeNB to SeNB), 5. Data Forwarding (MeNB to S-GW), 6. Path Update procedure (MeNB to MME), 7. UE Context Release (MeNB to SeNB).](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant MeNB
+    participant SeNB
+    participant S-GW
+    participant MME
+    Note left of MeNB: MeNB initiated SeNB Release
+    MeNB->>SeNB: 1. SeNB Release Request
+    MeNB->>UE: 2. RRC Connection Reconfiguration
+    UE-->>MeNB: 3. RRC Connection Reconfiguration Complete
+    MeNB->>SeNB: 4. SN Status transfer
+    MeNB-->>S-GW: 5. Data Forwarding
+    MeNB->>MME: 6. Path Update procedure
+    MeNB->>SeNB: 7. UE Context Release
+```
+
+Sequence diagram for MeNB initiated SeNB Release procedure. Lifelines: UE, MeNB, SeNB, S-GW, MME. Steps: 1. SeNB Release Request (MeNB to SeNB), 2. RRC Connection Reconfiguration (MeNB to UE), 3. RRC Connection Reconfiguration Complete (UE to MeNB), 4. SN Status transfer (MeNB to SeNB), 5. Data Forwarding (MeNB to S-GW), 6. Path Update procedure (MeNB to MME), 7. UE Context Release (MeNB to SeNB).
+
+**Figure 5.10.2.2-2: SeNB Release procedure – MeNB initiated**
+
+Figure 5.10.2.2-2 shows an example signalling flow for the MeNB initiated SeNB Release procedure. The detailed description of each step is found in Section 10.1.2.8.3 in 3GPP TS 36.300 [14].
+
+### **SeNB initiated SeNB Release**
+
+![Sequence diagram for SeNB initiated SeNB Release procedure. Lifelines: UE, MeNB, SeNB, S-GW, MME. Steps: 1. SeNB Release Required (SeNB to MeNB), 2. SeNB Release Confirm (MeNB to SeNB), 3. RRC Connection Reconfiguration (MeNB to UE), 4. RRC Connection Reconfiguration Complete (UE to MeNB), 5. SN Status transfer (MeNB to SeNB), 6. Data Forwarding (MeNB to S-GW), 7. Path Update procedure (MeNB to MME), 8. UE Context Release (MeNB to SeNB).](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg)
+
+```
+sequenceDiagram
+    participant UE
+    participant MeNB
+    participant SeNB
+    participant S-GW
+    participant MME
+    Note left of SeNB: SeNB initiated SeNB Release
+    SeNB->>MeNB: 1. SeNB Release Required
+    MeNB->>SeNB: 2. SeNB Release Confirm
+    MeNB->>UE: 3. RRC Connection Reconfiguration
+    UE-->>MeNB: 4. RRC Connection Reconfiguration Complete
+    MeNB->>SeNB: 5. SN Status transfer
+    MeNB-->>S-GW: 6. Data Forwarding
+    MeNB->>MME: 7. Path Update procedure
+    MeNB->>SeNB: 8. UE Context Release
+```
+
+Sequence diagram for SeNB initiated SeNB Release procedure. Lifelines: UE, MeNB, SeNB, S-GW, MME. Steps: 1. SeNB Release Required (SeNB to MeNB), 2. SeNB Release Confirm (MeNB to SeNB), 3. RRC Connection Reconfiguration (MeNB to UE), 4. RRC Connection Reconfiguration Complete (UE to MeNB), 5. SN Status transfer (MeNB to SeNB), 6. Data Forwarding (MeNB to S-GW), 7. Path Update procedure (MeNB to MME), 8. UE Context Release (MeNB to SeNB).
+
+**Figure 5.10.2.2-3: SeNB Release procedure – SeNB initiated**
+
+Figure 5.10.2.2-3 shows an example signalling flow for the SeNB initiated SeNB Release procedure. The detailed description of each step is found in Section 10.1.2.8.3 in 3GPP TS 36.300 [14].
+
+# 6 Self evaluation of URLLC technical performance
+
+## 6.1 Reliability
+
+As defined in Report ITU-R M.2412 [6], reliability is the success probability of transmitting a layer 2/3 packet within a required maximum time, which is the time it takes to deliver a small data packet from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface at a certain channel quality.
+
+### 6.1.1 NR
+
+NR Reliability is evaluated under Urban Macro – URLLC test environment. Both downlink and uplink are evaluated. A variety of configurations are considered. Detailed assumptions and results are provided in Annex B.z.4.
+
+#### 6.1.1.1 DL reliability
+
+For downlink reliability, both evaluation configuration A (carrier frequency = 4 GHz) and evaluation configuration B (carrier frequency = 700 MHz) are evaluated.
+
+The evaluation results of NR FDD for downlink reliability are provided in Table 6.1.1.1-1. All the evaluation results are derived with less than 100 MHz and 40 MHz bandwidth for evaluation configuration A (CF = 4 GHz) and B (CF = 700 MHz), respectively. It is observed that NR FDD fulfils the reliability requirement for downlink in a wide range of configurations.
+
+Table 6.1.1.1-1 Evaluation results of downlink reliability for NR FDD
+
+##### (a) Evaluation configuration A (CF = 4 GHz)
+
+| Scheme and antenna configuration                                                   | Sub-carrier spacing [kHz] | ITU Requirement | Channel condition | Channel model A   |             | Channel model B   |             |
+|------------------------------------------------------------------------------------|---------------------------|-----------------|-------------------|-------------------|-------------|-------------------|-------------|
+|                                                                                    |                           |                 |                   | Number of samples | Reliability | Number of samples | Reliability |
+| 2x2 SU-MIMO<br>14os <sup>1</sup> slot,<br>Slot aggregation,<br>(1 PDCCH + 2 PDSCH) | 60                        | 99.999%         | NLOS              | 1                 | 99.999899%  | 1                 | 99.99991%   |
+| 2x2 SU-MIMO,<br>4os non-slot,<br>HARQ re-tx<br>(2 PDCCH + 2 PDSCH)                 | 30                        | 99.999%         | NLOS              | 1                 | 99.999898%  | 1                 | 99.99995%   |
+| 2x2 SU-MIMO,<br>4os non-slot,<br>One shot<br>(1 PDCCH + 1 PDSCH)                   | 30                        | 99.999%         | NLOS              | 1                 | 99.99965%   | 1                 | 99.99969%   |
+| 2x4 SU-MIMO<br>7os non-slot,<br>One shot,<br>(1 PDCCH + 1 PDSCH)                   | 30                        | 99.999%         | NLOS              | 1                 | > 99.9999%  | 1                 | > 99.9999%  |
+| 32x8 SU-MIMO<br>14os slot,<br>One shot<br>(1 PDCCH + 1 PDSCH)                      | 30                        | 99.999%         | NLOS              | 1                 | 99.9999%    | /                 | /           |
+| 4x2 SU-MIMO<br>7os slot,<br>Slot aggregation,<br>(1 PDCCH+2 PDSCH)                 | 30                        | 99.999%         | NLOS              | /                 | /           | 1                 | 99.99999%   |
+| 8x4 SU-MIMO<br>14os one-shot<br>(1 PDCCH+1 PDSCH)                                  | 30                        | 99.999%         | NLOS              | 1                 | >99.9999%   | 1                 | >99.9999%   |
+
+NOTE1: os = OFDM symbol
+
+(b) Evaluation configuration B (CF = 700 MHz)
+
+| Scheme and antenna configuration                                         | Sub-carrier spacing [kHz] | ITU Requirement | Channel condition | Channel model A   |             | Channel model B   |             |
+|--------------------------------------------------------------------------|---------------------------|-----------------|-------------------|-------------------|-------------|-------------------|-------------|
+|                                                                          |                           |                 |                   | Number of samples | Reliability | Number of samples | Reliability |
+| 2x2 SU-MIMO<br>140s slot,<br>One shot<br>(1 PDCCH+1 PDSCH)               | 30                        | 99.999%         | NLOS              | 1                 | 99.9998%    | 2                 | 99.9994%    |
+| 2x2 SU-MIMO<br>70s non-slot,<br>one-shot (1 PDCCH+1 PDSCH)               | 30                        | 99.999%         | NLOS              | 4                 | 99.9995%    | 4                 | 99.9995%    |
+| 2x2 SU-MIMO,<br>40s non-slot,<br>Slot aggregation<br>(1 PDCCH + 2 PDSCH) | 30                        | 99.999%         | NLOS              | 2                 | 99.9997%    | 2                 | 99.9998%    |
+| 16x4 SU-MIMO,<br>140s slot,<br>One short<br>(1PDCCH + 1 PDSCH)           | 30                        | 99.999%         | NLOS              | 1                 | 99.9999%    | /                 | /           |
+| 2x2 SU-MIMO<br>70s non-slot,<br>One shot (1 PDCCH+2 PDSCH)               | 30                        | 99.999%         | NLOS              | /                 | /           | 1                 | 99.9999991% |
+| 2x2 SU-MIMO<br>140s slot,<br>One-shot (1 PDCCH+1 PDSCH)                  | 30                        | 99.999%         | NLOS              | 1                 | >99.9999%   | 1                 | >99.9999%   |
+
+#### 6.1.1.2 UL reliability
+
+For uplink reliability, both evaluation configuration A (carrier frequency = 4 GHz) and evaluation configuration B (carrier frequency = 700 MHz) are evaluated.
+
+The evaluation results of NR FDD for uplink reliability are provided in Table 6.1.1.2-1. All the evaluation results are derived with less than 100 MHz and 40 MHz bandwidth for evaluation configuration A (CF = 4 GHz) and B (CF = 700 MHz), respectively.
+
+Table 6.1.1.2-1 Evaluation results of uplink reliability for NR FDD
+
+##### (a) Evaluation configuration A (CF = 4 GHz)
+
+| Scheme and antenna configuration                                  | Sub-carrier spacing [kHz] | ITU Requirement | Channel model A   |                   |                | Channel model B   |                   |                |
+|-------------------------------------------------------------------|---------------------------|-----------------|-------------------|-------------------|----------------|-------------------|-------------------|----------------|
+|                                                                   |                           |                 | Channel condition | Number of samples | Reliability    | Channel condition | Number of samples | Reliability    |
+| 1x16 SIMO, OFDMA , 140s slot, Grant free, One shot (1 PUSCH)      | 60                        | 99.999%         | NLOS              | 1                 | 99.9999%       | NLOS              | 1                 | 99.99999%      |
+| 8x32 SU-MIMO, OFDMA, 140s slot, Grant based, (1 PDCCH + 1 PUSCH)  | 30                        | 99.999%         | LOS               | 1                 | 99.9999%       | LOS               | /                 | /              |
+| 1x8 SIMO, OFDMA, 70s non-slot Grant free One short (1 PUSCH)      | 30                        | 99.999%         | NLOS              | 1                 | > 99.9999%     | NLOS              | 2                 | 99.9999%       |
+| 1x2 SIMO, OFDMA, 40s non-slot Grant free, 2 repetitions (2 PUSCH) | 30                        | 99.999%         | NLOS              | 1                 | 99.9999999992% | NLOS              | 1                 | 99.9999999887% |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free One shot (1 PUSCH)         | 30                        | 99.999%         | NLOS              | /                 | /              | NLOS              | 1                 | 99.9992%       |
+| 2x2 SU-MIMO, OFDMA, 40s non-slot Grant free, One shot (1 PUSCH)   | 30                        | 99.999%         | NLOS              | 1                 | 99.99928%      | NLOS              | 1                 | 99.99974%      |
+| 1x4 SIMO, OFDMA , 70s,Grant free, One-shot (1 PUSCH)              | 30                        | 99.999%         | NLOS              | /                 | /              | NLOS              | 1                 | 99.9999999%    |
+| 1x8 SIMO, OFDMA, 140s, Grant free, 2 repetitions (2 PUSCH)        | 30                        | 99.999%         | NLOS              | 1                 | 99.999984%     | NLOS              | 1                 | 99.99999964%   |
+| 1x8 SIMO, OFDMA, 140s, Grant free, One shot (1 PUSCH)             | 30                        | 99.999%         | NLOS              | 1                 | >99.9999%      | NLOS              | 1                 | >99.9999%      |
+
+##### (b) Evaluation configuration B (CF = 700 MHz)
+
+| Scheme and antenna configuration                                      | Sub-carrier spacing [kHz] | ITU Requirement | Channel model A   |                   |              | Channel model B   |                   |              |
+|-----------------------------------------------------------------------|---------------------------|-----------------|-------------------|-------------------|--------------|-------------------|-------------------|--------------|
+|                                                                       |                           |                 | Channel condition | Number of samples | Reliability  | Channel condition | Number of samples | Reliability  |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free<br>One shot (1 PUSCH)          | 30                        | 99.999%         | NLOS              | 1                 | 99.99999%    | NLOS              | 1                 | 99.9999997%  |
+| 1x2 SIMO, OFDMA, 70s non-slot, Grant free, 2 repetitions (2 PUSCH)    | 30                        | 99.999%         | NLOS              | /                 | /            | NLOS              | 1                 | 99.999998%   |
+| 2x2 SU-MIMO, OFDMA, 40s non-slot, Grant free, 2 repetitions (2 PUSCH) | 30                        | 99.999%         | NLOS              | 1                 | 99.99982%    | NLOS              | 1                 | 99.99979%    |
+| 4x16 SU-MIMO, OFDMA, 140s slot, Grant based (1 PDCCH + 1 PUSCH)       | 30                        | 99.999%         | NLOS              | 1                 | 99.9999%     | NLOS              | /                 | /            |
+| 1x8 SIMO, OFDMA, 70s non-slot, Grant free, One shot (1 PUSCH)         | 30                        | 99.999%         | NLOS              | 1                 | > 99.9999%   | NLOS              | 1                 | > 99.9999%   |
+| 1x2 SIMO, OFDMA, 40s non-slot, Grant free, 2 repetitions (2 PUSCH)    | 30                        | 99.999%         | NLOS              | 1                 | 99.99999999% | NLOS              | 1                 | 99.99999999% |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free, One shot (1 PUSCH, 8RB)       | 30                        | 99.999%         | NLOS              | 1                 | 99.9993%     | NLOS              | 1                 | 99.9993%     |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free, One shot (1 PUSCH, 12RB)      | 30                        | 99.999%         | NLOS              | 1                 | 99.9992%     | NLOS              | 1                 | 99.9992%     |
+| 1x8 SIMO, OFDMA, 70s non-slot, One shot (1 PUSCH, 12RB)               | 30                        | 99.999%         | NLOS              | 1                 | 99.9993%     | NLOS              | 1                 | 99.9993%     |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free, One shot (1 PUSCH)            | 30                        | 99.999%         | NLOS              | /                 | /            | NLOS              | 1                 | 99.99967%    |
+| 1x8 SIMO, OFDMA, 140s slot, Grant free, 2 repetitions (2 PUSCH)       | 30                        | 99.999%         | NLOS              | 1                 | 99.9999999%  | NLOS              | /                 | /            |
+
+|                                                               |    |         |      |   |           |      |   |           |
+|---------------------------------------------------------------|----|---------|------|---|-----------|------|---|-----------|
+| 1x2 SIMO, OFDMA, 140s one slot, Grant free, One shot(1 PUSCH) | 30 | 99.999% | NLOS | / | >99.9999% | NLOS | 1 | >99.9999% |
+|---------------------------------------------------------------|----|---------|------|---|-----------|------|---|-----------|
+
+The evaluation results of NR TDD for uplink reliability are provided in Table 6.1.1.2-2. All the evaluation results are derived with less than 100 MHz and 40 MHz bandwidth for evaluation configuration A (CF = 4 GHz) and B (CF = 700 MHz), respectively.
+
+It is observed that NR fulfils the reliability requirement for uplink in a wide range of configurations.
+
+**Table 6.1.1.2-2 Evaluation results of uplink reliability for NR TDD**
+
+##### **(a) Evaluation configuration A (CF = 4 GHz)**
+
+| Scheme and antenna configuration                                   | Sub-carrier spacing [kHz] | Frame structure             | ITU Requirement | Channel model A   |                   |             | Channel model B   |                   |             |
+|--------------------------------------------------------------------|---------------------------|-----------------------------|-----------------|-------------------|-------------------|-------------|-------------------|-------------------|-------------|
+|                                                                    |                           |                             |                 | Channel condition | Number of samples | Reliability | Channel condition | Number of samples | Reliability |
+| 2x8 MIMO, OFDMA, 40s non-slot, Grant free, 2 repetitions (2 PUSCH) | 60                        | 0.5ms periodicity DL:UL=1:1 | 99.999%         | NLOS              | 1                 | 99.99999 %  | NLOS              | /                 | /           |
+
+##### **(b) Evaluation configuration B (CF = 700 MHz)**
+
+| Scheme and antenna configuration                                   | Sub-carrier spacing [kHz] | Frame structure             | ITU Requirement | Channel model A   |                   |              | Channel model B   |                   |             |
+|--------------------------------------------------------------------|---------------------------|-----------------------------|-----------------|-------------------|-------------------|--------------|-------------------|-------------------|-------------|
+|                                                                    |                           |                             |                 | Channel condition | Number of samples | Reliability  | Channel condition | Number of samples | Reliability |
+| 2x8 MIMO, OFDMA, 40s non-slot, Grant free, 2 repetitions (2 PUSCH) | 60                        | 0.5ms periodicity DL:UL=1:1 | 99.999%         | NLOS              | 1                 | 99.9999958 % | NLOS              | /                 | /           |
+
+## 6.2 Latency
+
+### 6.2.1 User plane latency
+
+#### 6.2.1.1 NR
+
+NR user plane latency for URLLC is evaluated based on the procedures and parameters as described in Section 5.7.1.1.
+
+The evaluation results are shown in Section 5.7.1.1. It is observed that under a wide range of configurations NR fulfills both downlink and uplink user plane latency requirement of 1 ms for URLLC.
+
+#### 6.2.1.2 LTE
+
+LTE user plane latency for URLLC is evaluated based on the procedures and parameters as described in Section 5.7.1.2.
+
+The evaluation results are shown in Section 5.7.1.2. It is observed that LTE fulfills downlink and uplink user plane latency requirement of 1 ms for URLLC with FDD using 2 OFDM symbol and 3 OFDM symbol TTI duration.
+
+### 6.2.2 Control plane latency
+
+Based on the evaluation results shown in Section 5.7.2, the control plane latency requirement is fulfilled by NR and LTE.
+
+## 6.3 Mobility interruption time
+
+Based on the evaluation results shown in Section 5.10, the mobility interruption time requirement is fulfilled by NR and LTE.
+
+# 7 Self evaluation of mMTC technical performance
+
+## 7.1 Connection density
+
+As specified in Report ITU-R M.2410 [4], connection density is the system capacity metric defined as the total number of devices fulfilling a specific quality of service (QoS) per unit area (per km<sup>2</sup>) with 99% grade of service (GoS).
+
+In Report ITU-R M.2412 [6], the required QoS is that a 32-byte packet is successfully received within 10 s.
+
+The connection density can be evaluated using one or both of two alternative methods: The Full-buffer system-level simulation followed by link level simulation, and the Non-full-buffer system level simulation. These are defined in section 7.1.3 of Report ITU-R M.2412 [6]. The detailed assumptions for these approaches, including system level configurations and traffic model, are defined in Table 5 – d) in Report ITU-R M.2412 [6].
+
+### 7.1.1 NR
+
+The connection density of NR is evaluated by using the full buffer system level simulation followed by link level simulation (referred to as “full buffer system level simulation” below).
+
+In a first step this evaluation method employs a full buffer system level simulation to derive the uplink SINR distribution for a candidate technology. In a second step link level simulation are performed to determine the uplink spectral efficiency and data rate as functions of SINR. When combined these three functions supports the calculation of the expected long-term time-frequency resources required for each SINR to support the specified traffic model.
+
+Connection density is in a final step conceptually derived by the system bandwidth, declared for the candidate technology, divided by the average required frequency resource. The requirement is fulfilled if the recorded connection density exceeds the 1.000.000 devices/km<sup>2</sup>, while the time resource, i.e. the packet delay, at the 99<sup>th</sup> percentile SINR is less than 10 s.
+
+This evaluation method is targeted to evaluate the connection density in terms of the capability of uplink data transmission. The capacity calculation is based on an assumption of ideal resource allocation among the multiple packets and users (e.g., there is no collision on resource allocation). The packet delay calculation does not consider the delays introduced by the connection access procedure.
+
+Under this evaluation method, NR FDD is evaluated. The Urban Macro – mMTC test environment is used for evaluation. Both evaluation configuration A (ISD=500 m) and evaluation configuration B (ISD=1732 m) are considered.
+
+The evaluation results of NR FDD are shown in Table 7.1.1-1 expressed as the average performance presented by the contributing companies. It is observed that NR fulfills connection density requirement under full buffer system level simulation followed by link level simulation. Detailed simulation assumptions and results can be found in Annex B.4.5.
+
+**Table 7.1.1-1 Evaluation results of connection density for NR FDD  
+(Full buffer system level simulation followed by link level simulation  
+packet arrival rate: 1 packet / 2 hour / device)**
+
+#### **(a) Evaluation configuration A (ISD=500 m)**
+
+| Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| 1x2 SIMO OFDMA                   | 15 kHz              | 1,000,000                                 | 4                 | 36,323,844                                   | 180                      | 4                 | 36,007,832                                   | 180                      |
+
+#### **(b) Evaluation configuration B (ISD=1 732 m)**
+
+| Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| 1x2 SIMO OFDMA                   | 15 kHz              | 1,000,000                                 | 4                 | 1,267,406                                    | 180                      | 4                 | 1,503,394                                    | 180                      |
+
+### 7.1.2 LTE
+
+The connection density of NB-IoT and eMTC are evaluated using both the full buffer, and the non-full buffer system level simulation as defined in Report ITU-R M.2412 [6].
+
+As indicated in Section 7.1.1, the full buffer system level simulation method targets to evaluate the connection density in terms of the capability of uplink data transmission. It does also not model synchronization and system information acquisition, control channel and downlink data channel performance. It assumes ideal resource allocation among the multiple uplink packets and users (e.g., there is no collision on resource allocation), and the delays introduced by access procedure are not considered.
+
+In the non-full buffer system level simulation, the idle mode synchronization and system information acquisition performance and delays are taken into account. The chosen system access procedure, the uplink data transmission and the connection release procedures are modelled. The link level performance of all relevant physical channels and signals are modelled, and the system level resource allocation and the delays associated with the modeled protocols are considered. The connection density is recorded at the user arrival rate at which 99% of all uplink packet is successfully received within 10s.
+
+Since the non-full buffer system level simulation provides a more detailed level of modelling the evaluation results are, as expected, different from the full buffer system level simulation.
+
+For both evaluation methods, the Urban Macro – mMTC test environment is used. Both evaluation configuration A (ISD=500 m) and evaluation configuration B (ISD=1732 m) are considered.
+
+The evaluation results of NB-IoT and eMTC are shown in Table 7.1.2-1 for full buffer system level simulation, and in Table 7.1.2-2 for non-full buffer system level simulation, respectively. For non-full buffer system level simulation, both the Early Data Transmission (EDT) and the RRC Resume procedures are evaluated. Since EDT procedure is shortened compared to RRC Resume procedure, the evaluation results are different.
+
+In addition to the required bandwidths presented in Table 7.1.2-1 and Table 7.1.2-2, eMTC requires 2 PRBs to be configured at the edges of the configured LTE system bandwidth for supporting PUCCH transmissions. Overhead from (N)PSS, (N)SSS, (N)PBCH or (N)PDSCH system information broadcast is also not accounted for in the reported bandwidths. For NB-IoT a reasonable assumption is that the overhead from NPSS, NSSS, NPBCH and SIB1-NB transmissions constitutes ~30% of one downlink PRB. For LTE-M the corresponding overhead is approximately ~40% of one downlink narrowband.
+
+It is observed that both NB-IoT and eMTC fulfill connection density requirement under either evaluation method, using either system access procedures.
+
+Detailed simulation assumptions and results can be found in Annex B.4.5.
+
+**Table 7.1.2-1 Evaluation results of connection density for NB-IoT and eMTC**  
+**(Full buffer system level simulation followed by link level simulation**  
+**packet arrival rate: 1 packet / 2 hour / device)**
+
+#### **(a) Evaluation configuration A (ISD=500 m)**
+
+| Technical feature | Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|-------------------|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                   |                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| NB-IoT            | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 2                 | 43,691,789                                   | 180                      | 2                 | 43,626,653                                   | 180                      |
+| eMTC              | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 3                 | 35,235,516                                   | 180                      | 3                 | 34,884,438                                   | 180                      |
+
+#### **(b) Evaluation configuration B (ISD=1 732 m)**
+
+| Technical feature | Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|-------------------|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                   |                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| NB-IoT            | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 3                 | 2,335,319                                    | 180                      | 3                 | 2,332,680                                    | 180                      |
+| eMTC              | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 3                 | 1,212,909                                    | 180                      | 3                 | 1,511,989                                    | 180                      |
+
+**Table 7.1.2-2 Evaluation results of connection density for NB-IoT and eMTC**  
+**(Non-full buffer system level simulation**  
+**packet arrival rate: 1 packet / 2 hour / device)**
+
+#### **(a) Evaluation configuration A (ISD=500 m)**
+
+| Technical feature   | Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|---------------------|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                     |                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| NB-IoT (EDT)        | 1x2 SIMO, Single-tone            | 15 kHz              | 1,000,000                                 | 1                 | 8,047,087                                    | 180                      | 1                 | 8,077,017                                    | 180                      |
+| NB-IoT (EDT)        | 1x2 SIMO, Multi-tone             | 15 kHz              | 1,000,000                                 | -                 | -                                            | -                        | 1                 | 16,000,000                                   | 180                      |
+| NB-IoT (RRC Resume) | 1x2 SIMO Multi-tone              | 15 kHz              | 1,000,000                                 | 1                 | 1,233,000                                    | 180                      | 1                 | 1,225,000                                    | 180                      |
+| eMTC (RRC Resume)   | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 1                 | 5,680,000                                    | 1080                     | 1                 | 5,680,000                                    | 1080                     |
+
+#### **(b) Evaluation configuration B (ISD=1 732m)**
+
+| Technical feature   | Scheme and antenna configuration | Sub-carrier spacing | ITU Requirement (device/km <sup>2</sup> ) | Channel model A   |                                              |                          | Channel model B   |                                              |                          |
+|---------------------|----------------------------------|---------------------|-------------------------------------------|-------------------|----------------------------------------------|--------------------------|-------------------|----------------------------------------------|--------------------------|
+|                     |                                  |                     |                                           | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) | Number of samples | Connection density (device/km <sup>2</sup> ) | Required bandwidth (kHz) |
+| NB-IoT (EDT)        | 1x2 SIMO, Single-tone            | 15 kHz              | 1,000,000                                 | 1                 | 1,198,000                                    | 360                      | 1                 | 1,203,880                                    | 360                      |
+| NB-IoT (EDT)        | 1x2 SIMO Multi-tone              | 15 kHz              | 1,000,000                                 | -                 | -                                            | -                        | 1                 | 1,250,000                                    | 360                      |
+| NB-IoT (RRC Resume) | 1x2 SIMO Multi-tone              | 15 kHz              | 1,000,000                                 | 1                 | 1,018,000                                    | 2700                     | 1                 | 1,034,000                                    | 1980                     |
+| eMTC (EDT)          | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 1                 | 1,107,000                                    | 540                      | 1                 | 1,140,000                                    | 540                      |
+| eMTC (RRC Resume)   | 1x2 SIMO                         | 15 kHz              | 1,000,000                                 | 1                 | 1,026,000                                    | 3240                     | 1                 | 1,335,000                                    | 3240                     |
+
+# 8 Self evaluation of generic requirements
+
+## 8.1 Bandwidth and scalability
+
+As defined in Report ITU-R M.2410 [4], bandwidth is the maximum aggregated system bandwidth. The bandwidth may be supported by single or multiple radio frequency (RF) carriers.
+
+Scalable bandwidth is the ability of the candidate RIT/SRIT to operate with different bandwidths.
+
+### 8.1.1 NR
+
+The capability of bandwidth and bandwidth scalability for NR are evaluated.
+
+According to Section 5.3.2 of TS 38.104 [15], the maximum bandwidth related to specific sub-carrier spacing (SCS) and frequency range (FR) for a component carrier is provided in Table 8.1.1-1. Besides, according to Section 6.4 of TS38.331 [16], carrier aggregation of up to sixteen component carriers is supported by NR Rel-15. Accordingly, the NR capability of maximum aggregated system bandwidth is presented in Table 8.1.1-1. It is observed that the maximum aggregated bandwidth for FR 1 is 800 MHz to 1 600 MHz, while for FR 2, the maximum aggregated bandwidth is 3 200 MHz to 6 400 MHz. Therefore the bandwidth requirement of at least 100 MHz is met by NR Rel-15 under all frequency ranges for all sub-carrier spacing values.
+
+**Table 8.1.1-1 NR capability on bandwidth**
+
+|     | SCS [kHz] | Maximum bandwidth for one component carrier (MHz) | Maximum number of component carriers for carrier aggregation | Maximum aggregated bandwidth (MHz) |
+|-----|-----------|---------------------------------------------------|--------------------------------------------------------------|------------------------------------|
+| FR1 | 15        | 50                                                | 16                                                           | 800                                |
+|     | 30        | 100                                               | 16                                                           | 1600                               |
+|     | 60        | 100                                               | 16                                                           | 1600                               |
+| FR2 | 60        | 200                                               | 16                                                           | 3200                               |
+|     | 120       | 400                                               | 16                                                           | 6400                               |
+
+According to Section 5.3.2 of TS 38.104 [15], different bandwidths are supported for a component carrier at given SCS as listed in Table 8.1.1-2. Accordingly, the bandwidth scalability capability of NR Rel-15 is summarized in Table 8.1.1-3. It is observed that up to 12 different bandwidths are supported for FR 1, and up to 4 different bandwidths are supported for FR 2. Therefore bandwidth scalability capability is fulfilled by NR Rel-15.
+
+**Table 8.1.1-2 Transmission bandwidth configuration  $N_{RB}$  in NR**
+
+#### (a) For FR1
+
+| SCS (kHz) | 5MHz     | 10MHz    | 15MHz    | 20 MHz   | 25 MHz   | 30 MHz   | 40 MHz   | 50MHz    | 60 MHz   | 70 MHz   | 80 MHz   | 90 MHz   | 100 MHz  |
+|-----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|
+|           | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ |
+| 15        | 25       | 52       | 79       | 106      | 133      | 160      | 216      | 270      | N/A      | N.A      | N/A      | N/A      | N/A      |
+| 30        | 11       | 24       | 38       | 51       | 65       | 78       | 106      | 133      | 162      | 189      | 217      | 245      | 273      |
+| 60        | N/A      | 11       | 18       | 24       | 31       | 38       | 51       | 65       | 79       | 93       | 107      | 121      | 135      |
+
+#### (b) For FR2
+
+| SCS [kHz] | 50 MHz   | 100 MHz  | 200 MHz  | 400 MHz  |
+|-----------|----------|----------|----------|----------|
+|           | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ | $N_{RB}$ |
+| 60        | 66       | 132      | 264      | N.A      |
+| 120       | 32       | 66       | 132      | 264      |
+
+**Table 8.1.1-3 Bandwidth scalability capability for NR**
+
+|     | SCS [kHz] | Minimum component carrier bandwidth (MHz) | Maximum component carrier bandwidth (MHz) | Maximum Number of supported bandwidth for a component carrier |
+|-----|-----------|-------------------------------------------|-------------------------------------------|---------------------------------------------------------------|
+| FR1 | 15        | 5                                         | 50                                        | 8                                                             |
+|     | 30        | 5                                         | 100                                       | 13                                                            |
+|     | 60        | 10                                        | 100                                       | 12                                                            |
+| FR2 | 60        | 50                                        | 200                                       | 3                                                             |
+|     | 120       | 50                                        | 400                                       | 4                                                             |
+
+### 8.1.2 LTE
+
+The capability of bandwidth and bandwidth scalability for LTE are evaluated.
+
+According to Section 5.6 of TS 36.101 [17], the maximum bandwidth of a component carrier is 20 MHz for LTE. Besides, according to Section 6.4 of TS 36.331 [18], carrier aggregation of up to thirty-two component carriers is supported by LTE Rel-15. Accordingly, LTE Rel-15 reaches the capability of maximum aggregated system bandwidth of 640 MHz. Therefore the bandwidth requirement of at least 100 MHz is met by LTE Rel-15.
+
+**Table 8.1.2-1 LTE capability on bandwidth**
+
+| Maximum bandwidth for one component carrier (MHz) | Maximum number of component carriers for carrier aggregation | Maximum aggregated bandwidth (MHz) |
+|---------------------------------------------------|--------------------------------------------------------------|------------------------------------|
+| 20                                                | 32                                                           | 640                                |
+
+According to Section 5.6 of TS 36.101 [17], six different bandwidths are supported for a component carrier, as shown in Table 8.1.2-2. Therefore bandwidth scalability capability is fulfilled by LTE Rel-15.
+
+**Table 8.1.2-2: Transmission bandwidth configuration  $N_{RB}$  in LTE**
+
+| Channel bandwidth $BW_{Channel}$ [MHz]        | 1.4 | 3  | 5  | 10 | 15 | 20  |
+|-----------------------------------------------|-----|----|----|----|----|-----|
+| Transmission bandwidth configuration $N_{RB}$ | 6   | 15 | 25 | 50 | 75 | 100 |
+
+## 8.2 Spectrum
+
+As defined in Report ITU-R M.2411 [5], spectrum requirement include
+
+- The capability of being able to utilize at least one frequency band identified for IMT in the ITU Radio Regulations, and
+- The capability of being able to utilize the higher frequency range/band(s) above 24.25 GHz (NOTE: In the case of the candidate SRIT, at least one of the component RITs need to fulfil this requirement.).
+
+### 8.2.1 NR
+
+The bands in which NR can be deployed are given in Table 8.2.1-1 and Table 8.2.1-2 according to TS 38.104 [15]. It is observed that NR Rel-15 can support at least one frequency band for IMT, as well as to utilize the higher frequency range/bands above 24.25 GHz. Therefore NR Rel-15 fulfils spectrum requirement.
+
+**Table 8.2.1-1: NR operating bands in FR1**
+
+| <b>NR operating band</b> | <b>Uplink (UL) operating band<br/>BS receive / UE transmit<br/><math>F_{UL\_low} - F_{UL\_high}</math></b> | <b>Downlink (DL) operating band<br/>BS transmit / UE receive<br/><math>F_{DL\_low} - F_{DL\_high}</math></b> | <b>Duplex Mode</b> |
+|--------------------------|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------|
+| n1                       | 1920 MHz – 1980 MHz                                                                                        | 2110 MHz – 2170 MHz                                                                                          | FDD                |
+| n2                       | 1850 MHz – 1910 MHz                                                                                        | 1930 MHz – 1990 MHz                                                                                          | FDD                |
+| n3                       | 1710 MHz – 1785 MHz                                                                                        | 1805 MHz – 1880 MHz                                                                                          | FDD                |
+| n5                       | 824 MHz – 849 MHz                                                                                          | 869 MHz – 894 MHz                                                                                            | FDD                |
+| n7                       | 2500 MHz – 2570 MHz                                                                                        | 2620 MHz – 2690 MHz                                                                                          | FDD                |
+| n8                       | 880 MHz – 915 MHz                                                                                          | 925 MHz – 960 MHz                                                                                            | FDD                |
+| n12                      | 699 MHz – 716 MHz                                                                                          | 729 MHz – 746 MHz                                                                                            | FDD                |
+| n20                      | 832 MHz – 862 MHz                                                                                          | 791 MHz – 821 MHz                                                                                            | FDD                |
+| n25                      | 1850 MHz – 1915 MHz                                                                                        | 1930 MHz – 1995 MHz                                                                                          | FDD                |
+| n28                      | 703 MHz – 748 MHz                                                                                          | 758 MHz – 803 MHz                                                                                            | FDD                |
+| n34                      | 2010 MHz – 2025 MHz                                                                                        | 2010 MHz – 2025 MHz                                                                                          | TDD                |
+| n38                      | 2570 MHz – 2620 MHz                                                                                        | 2570 MHz – 2620 MHz                                                                                          | TDD                |
+| n39                      | 1880 MHz – 1920 MHz                                                                                        | 1880 MHz – 1920 MHz                                                                                          | TDD                |
+| n40                      | 2300 MHz – 2400 MHz                                                                                        | 2300 MHz – 2400 MHz                                                                                          | TDD                |
+| n41                      | 2496 MHz – 2690 MHz                                                                                        | 2496 MHz – 2690 MHz                                                                                          | TDD                |
+| n51                      | 1427 MHz – 1432 MHz                                                                                        | 1427 MHz – 1432 MHz                                                                                          | TDD                |
+| n66                      | 1710 MHz – 1780 MHz                                                                                        | 2110 MHz – 2200 MHz                                                                                          | FDD                |
+| n70                      | 1695 MHz – 1710 MHz                                                                                        | 1995 MHz – 2020 MHz                                                                                          | FDD                |
+| n71                      | 663 MHz – 698 MHz                                                                                          | 617 MHz – 652 MHz                                                                                            | FDD                |
+| n75                      | N/A                                                                                                        | 1432 MHz – 1517 MHz                                                                                          | SDL                |
+| n76                      | N/A                                                                                                        | 1427 MHz – 1432 MHz                                                                                          | SDL                |
+| n77                      | 3300 MHz – 4200 MHz                                                                                        | 3300 MHz – 4200 MHz                                                                                          | TDD                |
+| n78                      | 3300 MHz – 3800 MHz                                                                                        | 3300 MHz – 3800 MHz                                                                                          | TDD                |
+| n79                      | 4400 MHz – 5000 MHz                                                                                        | 4400 MHz – 5000 MHz                                                                                          | TDD                |
+| n80                      | 1710 MHz – 1785 MHz                                                                                        | N/A                                                                                                          | SUL                |
+| n81                      | 880 MHz – 915 MHz                                                                                          | N/A                                                                                                          | SUL                |
+| n82                      | 832 MHz – 862 MHz                                                                                          | N/A                                                                                                          | SUL                |
+| n83                      | 703 MHz – 748 MHz                                                                                          | N/A                                                                                                          | SUL                |
+| n84                      | 1920 MHz – 1980 MHz                                                                                        | N/A                                                                                                          | SUL                |
+| n86                      | 1710 MHz – 1780 MHz                                                                                        | N/A                                                                                                          | SUL                |
+
+**Table 8.2.1-2: NR operating bands in FR2**
+
+| <b>NR operating band</b> | <b>Uplink (UL) and Downlink (DL) operating band<br/>BS transmit/receive<br/>UE transmit/receive<br/><math>F_{UL\_low} - F_{UL\_high}</math><br/><math>F_{DL\_low} - F_{DL\_high}</math></b> | <b>Duplex Mode</b> |
+|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|
+| n257                     | 26500 MHz – 29500 MHz                                                                                                                                                                       | TDD                |
+| n258                     | 24250 MHz – 27500 MHz                                                                                                                                                                       | TDD                |
+| n260                     | 37000 MHz – 40000 MHz                                                                                                                                                                       | TDD                |
+| n261                     | 27500 MHz – 28350 MHz                                                                                                                                                                       | TDD                |
+
+### 8.2.2 LTE
+
+The bands in which LTE can be deployed are given in Table 8.2.2-1 according to TS 36.101 [17]. It is observed that LTE Rel-15 can support at least one frequency band for IMT. Therefore LTE Rel-15 fulfils the spectrum requirement of being able to utilize at least one frequency band identified for IMT in the ITU Radio Regulations.
+
+Table 8.2.2-1 LTE (E-UTRA) operating bands
+
+| E-UTRA Operating Band | Uplink (UL) operating band<br>BS receive<br>UE transmit |                | Downlink (DL) operating band<br>BS transmit<br>UE receive |                | Duplex Mode       |
+|-----------------------|---------------------------------------------------------|----------------|-----------------------------------------------------------|----------------|-------------------|
+|                       | $F_{UL\_low}$                                           | $F_{UL\_high}$ | $F_{DL\_low}$                                             | $F_{DL\_high}$ |                   |
+| 1                     | 1920 MHz                                                | 1980 MHz       | 2110 MHz                                                  | 2170 MHz       | FDD               |
+| 2                     | 1850 MHz                                                | 1910 MHz       | 1930 MHz                                                  | 1990 MHz       | FDD               |
+| 3                     | 1710 MHz                                                | 1785 MHz       | 1805 MHz                                                  | 1880 MHz       | FDD               |
+| 4                     | 1710 MHz                                                | 1755 MHz       | 2110 MHz                                                  | 2155 MHz       | FDD               |
+| 5                     | 824 MHz                                                 | 849 MHz        | 869 MHz                                                   | 894 MHz        | FDD               |
+| 6 <sup>1</sup>        | 830 MHz                                                 | 840 MHz        | 875 MHz                                                   | 885 MHz        | FDD               |
+| 7                     | 2500 MHz                                                | 2570 MHz       | 2620 MHz                                                  | 2690 MHz       | FDD               |
+| 8                     | 880 MHz                                                 | 915 MHz        | 925 MHz                                                   | 960 MHz        | FDD               |
+| 9                     | 1749.9 MHz                                              | 1784.9 MHz     | 1844.9 MHz                                                | 1879.9 MHz     | FDD               |
+| 10                    | 1710 MHz                                                | 1770 MHz       | 2110 MHz                                                  | 2170 MHz       | FDD               |
+| 11                    | 1427.9 MHz                                              | 1447.9 MHz     | 1475.9 MHz                                                | 1495.9 MHz     | FDD               |
+| 12                    | 699 MHz                                                 | 716 MHz        | 729 MHz                                                   | 746 MHz        | FDD               |
+| 13                    | 777 MHz                                                 | 787 MHz        | 746 MHz                                                   | 756 MHz        | FDD               |
+| 14                    | 788 MHz                                                 | 798 MHz        | 758 MHz                                                   | 768 MHz        | FDD               |
+| 15                    | Reserved                                                |                | Reserved                                                  |                | FDD               |
+| 16                    | Reserved                                                |                | Reserved                                                  |                | FDD               |
+| 17                    | 704 MHz                                                 | 716 MHz        | 734 MHz                                                   | 746 MHz        | FDD               |
+| 18                    | 815 MHz                                                 | 830 MHz        | 860 MHz                                                   | 875 MHz        | FDD               |
+| 19                    | 830 MHz                                                 | 845 MHz        | 875 MHz                                                   | 890 MHz        | FDD               |
+| 20                    | 832 MHz                                                 | 862 MHz        | 791 MHz                                                   | 821 MHz        | FDD               |
+| 21                    | 1447.9 MHz                                              | 1462.9 MHz     | 1495.9 MHz                                                | 1510.9 MHz     | FDD               |
+| 22                    | 3410 MHz                                                | 3490 MHz       | 3510 MHz                                                  | 3590 MHz       | FDD               |
+| 23 <sup>1</sup>       | 2000 MHz                                                | 2020 MHz       | 2180 MHz                                                  | 2200 MHz       | FDD               |
+| 24                    | 1626.5 MHz                                              | 1660.5 MHz     | 1525 MHz                                                  | 1559 MHz       | FDD               |
+| 25                    | 1850 MHz                                                | 1915 MHz       | 1930 MHz                                                  | 1995 MHz       | FDD               |
+| 26                    | 814 MHz                                                 | 849 MHz        | 859 MHz                                                   | 894 MHz        | FDD               |
+| 27                    | 807 MHz                                                 | 824 MHz        | 852 MHz                                                   | 869 MHz        | FDD               |
+| 28                    | 703 MHz                                                 | 748 MHz        | 758 MHz                                                   | 803 MHz        | FDD               |
+| 29                    | N/A                                                     |                | 717 MHz                                                   | 728 MHz        | FDD <sup>2</sup>  |
+| 30 <sup>15</sup>      | 2305 MHz                                                | 2315 MHz       | 2350 MHz                                                  | 2360 MHz       | FDD               |
+| 31                    | 452.5 MHz                                               | 457.5 MHz      | 462.5 MHz                                                 | 467.5 MHz      | FDD               |
+| 32                    | N/A                                                     |                | 1452 MHz                                                  | 1496 MHz       | FDD <sup>2</sup>  |
+| 33                    | 1900 MHz                                                | 1920 MHz       | 1900 MHz                                                  | 1920 MHz       | TDD               |
+| 34                    | 2010 MHz                                                | 2025 MHz       | 2010 MHz                                                  | 2025 MHz       | TDD               |
+| 35                    | 1850 MHz                                                | 1910 MHz       | 1850 MHz                                                  | 1910 MHz       | TDD               |
+| 36                    | 1930 MHz                                                | 1990 MHz       | 1930 MHz                                                  | 1990 MHz       | TDD               |
+| 37                    | 1910 MHz                                                | 1930 MHz       | 1910 MHz                                                  | 1930 MHz       | TDD               |
+| 38                    | 2570 MHz                                                | 2620 MHz       | 2570 MHz                                                  | 2620 MHz       | TDD               |
+| 39                    | 1880 MHz                                                | 1920 MHz       | 1880 MHz                                                  | 1920 MHz       | TDD               |
+| 40                    | 2300 MHz                                                | 2400 MHz       | 2300 MHz                                                  | 2400 MHz       | TDD               |
+| 41                    | 2496 MHz                                                | 2690 MHz       | 2496 MHz                                                  | 2690 MHz       | TDD               |
+| 42                    | 3400 MHz                                                | 3600 MHz       | 3400 MHz                                                  | 3600 MHz       | TDD               |
+| 43                    | 3600 MHz                                                | 3800 MHz       | 3600 MHz                                                  | 3800 MHz       | TDD               |
+| 44                    | 703 MHz                                                 | 803 MHz        | 703 MHz                                                   | 803 MHz        | TDD               |
+| 45                    | 1447 MHz                                                | 1467 MHz       | 1447 MHz                                                  | 1467 MHz       | TDD               |
+| 46                    | 5150 MHz                                                | 5925 MHz       | 5150 MHz                                                  | 5925 MHz       | TDD <sup>8</sup>  |
+| 47                    | 5855 MHz                                                | 5925 MHz       | 5855 MHz                                                  | 5925 MHz       | TDD <sup>11</sup> |
+| 48                    | 3550 MHz                                                | 3700 MHz       | 3550 MHz                                                  | 3700 MHz       | TDD               |
+| 49                    | 3550 MHz                                                | 3700 MHz       | 3550 MHz                                                  | 3700 MHz       | TDD <sup>16</sup> |
+| 50                    | 1432 MHz                                                | 1517 MHz       | 1432 MHz                                                  | 1517 MHz       | TDD <sup>13</sup> |
+| 51                    | 1427 MHz                                                | 1432 MHz       | 1427 MHz                                                  | 1432 MHz       | TDD <sup>13</sup> |
+| 52                    | 3300 MHz                                                | 3400 MHz       | 3300 MHz                                                  | 3400 MHz       | TDD               |
+| ...                   |                                                         |                |                                                           |                |                   |
+
+|    |          |         |          |          |                              |
+|----|----------|---------|----------|----------|------------------------------|
+| 64 | Reserved |         |          |          |                              |
+| 65 | 1920 MHz | –       | 2010 MHz | 2110 MHz | – 2200 MHz FDD               |
+| 66 | 1710 MHz | –       | 1780 MHz | 2110 MHz | – 2200 MHz FDD <sup>4</sup>  |
+| 67 |          | N/<br>A |          | 738 MHz  | – 758 MHz FDD <sup>2</sup>   |
+| 68 | 698 MHz  | –       | 728 MHz  | 753 MHz  | – 783 MHz FDD                |
+| 69 |          | N/A     |          | 2570 MHz | – 2620 MHz FDD <sup>2</sup>  |
+| 70 | 1695 MHz | –       | 1710 MHz | 1995 MHz | – 2020 MHz FDD <sup>10</sup> |
+| 71 | 663 MHz  | –       | 698 MHz  | 617 MHz  | – 652 MHz FDD                |
+| 72 | 451 MHz  | –       | 456 MHz  | 461 MHz  | – 466 MHz FDD                |
+| 73 | 450 MHz  | –       | 455 MHz  | 460 MHz  | – 465 MHz FDD                |
+| 74 | 1427 MHz | –       | 1470 MHz | 1475 MHz | – 1518 MHz FDD               |
+| 75 |          | N/<br>A |          | 1432 MHz | – 1517 MHz FDD <sup>2</sup>  |
+| 76 |          | N/<br>A |          | 1427 MHz | – 1432 MHz FDD <sup>2</sup>  |
+| 85 | 698 MHz  | –       | 716 MHz  | 728 MHz  | – 746 MHz FDD                |
+
+NOTE 1: Band 6, 23 is not applicable
+
+NOTE 2: Restricted to E-UTRA operation when carrier aggregation is configured. The downlink operating band is paired with the uplink operating band (external) of the carrier aggregation configuration that is supporting the configured Pcell.
+
+NOTE 3: A UE that complies with the E-UTRA Band 65 minimum requirements in this specification shall also comply with the E-UTRA Band 1 minimum requirements.
+
+NOTE 4: The range 2180-2200 MHz of the DL operating band is restricted to E-UTRA operation when carrier aggregation is configured.
+
+NOTE 5: A UE that supports E-UTRA Band 66 shall receive in the entire DL operating band
+
+NOTE 6: A UE that supports E-UTRA Band 66 and CA operation in any CA band shall also comply with the minimum requirements specified for the DL CA configurations CA\_66B, CA\_66C and CA\_66A-66A.
+
+NOTE 7: A UE that complies with the E-UTRA Band 66 minimum requirements in this specification shall also comply with the E-UTRA Band 4 minimum requirements.
+
+NOTE 8: This band is an unlicensed band restricted to licensed-assisted operation using Frame Structure Type 3
+
+NOTE 9: In this version of the specification, restricted to E-UTRA DL operation when carrier aggregation is configured.
+
+NOTE 10: The range 2010-2020 MHz of the DL operating band is restricted to E-UTRA operation when carrier aggregation is configured and TX-RX separation is 300 MHz The range 2005-2020 MHz of the DL operating band is restricted to E-UTRA operation when carrier aggregation is configured and TX-RX separation is 295 MHz.
+
+NOTE 11: This band is unlicensed band used for V2X communication. There is no expected network deployment in this band so both Frame Structure Type 1 and Frame Structure Type 2 can be used.
+
+NOTE 12: A UE that complies with the E-UTRA Band 74 minimum requirements in this specification shall also comply with the E-UTRA Band 11 and Band 21 minimum requirements.
+
+NOTE 13: UE that complies with the E-UTRA Band 50 minimum requirements in this specification shall also comply with the E-UTRA Band 51 minimum requirements.
+
+NOTE 14: A UE that complies with the E-UTRA Band 75 minimum requirements in this specification shall also comply with the E-UTRA Band 76 minimum requirements.
+
+NOTE 15: Uplink transmission is not allowed at this band for UE with external vehicle-mounted antennas.
+
+NOTE 16: This band is restricted to licensed-assisted operation using Frame Structure Type 3
+
+## 8.3 Service
+
+According to Report ITU-R M.2411 [5], the support for wide range of services should be inspected by the following questions:
+
+- Is the proposal able to support a range of services across different usage scenarios (eMBB, URLLC, and mMTC)?
+- Specify which usage scenarios (eMBB, URLLC, and mMTC) the candidate RIT or candidate SRIT can support.
+
+The evaluation method is defined in Report ITU-R M.2412 [6], and the support of a wide range of services is verified by inspection of the candidate RITs/SRITs ability to meet the minimum technical performance requirements for various usage scenarios and their associated test environments.
+
+Based on the self evaluation results in Section 5 to 7, it is observed that NR RIT can meet the minimum technical performance requirements for the five test environments in eMBB, URLLC and mMTC, and LTE RIT can at least meet the minimum technical performance requirements for the four test environments in eMBB and mMTC. Therefore, both NR and LTE RIT can fulfil the service requirements.
+
+# --- 9 Conclusion
+
+Based on the self evaluation results presented through Section 5 to 8, NR RIT fulfils all technical performance requirements in the five test environments: Indoor Hotspot – eMBB, Dense Urban – eMBB, Rural – eMBB, Urban Macro – URLLC and Urban Macro – mMTC. LTE RIT fulfils the technical performance requirements in at least four test environments: Indoor Hotspot – eMBB, Dense Urban – eMBB, Rural – emBB, Urban Macro – mMTC.
+
+Both NR RIT and LTE RIT fulfils the spectrum requirement. NR RIT can support the frequency bands identified for IMT in the ITU Radio Regulations, as well as the higher frequency range/band(s) above 24.25 GHz. LTE RIT can support the frequency bands identified for IMT in the ITU Radio Regulations.
+
+Both NR RIT and LTE RIT fulfils service requirements.
+
+It is therefore concluded that
+
+- 3GPP's 5G SRIT can meet IMT-2020 requirements.
+- 3GPP's 5G NR RIT can meet IMT-2020 requirements
+
+# Annex A: Calibration for self evaluation
+
+To facilitate the self evaluation towards IMT-2020 submission, the system level simulators have been calibrated to ensure the results from different 3GPP entities are comparable.
+
+The following metrics are selected for calibration of self evaluation:
+
+- DL Geometry (wideband SINR)
+- Coupling gain
+
+The cell association mechanisms as defined in calibration assumptions are used to derive the above metrics, including multi-path based UE attachment model, and analog beamforming (BF) model, etc. Detailed calibration parameters and assumptions are found in Section 4 of RP-180524. It should be noted that these parameters are used for calibration purpose only.
+
+The calibration was conducted to the corresponding evaluation configurations of Indoor Hotspot – eMBB, Dense Urban – eMBB, Rural – eMBB, Urban Macro – mMTC, and Urban Macro - URLLC test environment as defined in Report ITU-R M.2412 [6]. The two channel model variants (channel model A and channel model B) are applied in the calibration.
+
+Twenty-one 3GPP entities provided the calibration results, including CATR, CATT, CEWiT, China Telecom, CMCC, Ericsson, Huawei, Intel, ITRI, LG Electronics, MediaTek, Motorola Mobility/Lenovo, NEC, Nokia, NTT DOCOMO, OPPO, Qualcomm, Samsung, Sharp, vivo and ZTE.
+
+The calibration results for the five test environments are shown through Figure A.1 to Figure A.5, respectively. The results are based on the average of the independent results from the simulators of the contributing entities. The results of DL geometry (wideband SINR) from the independent samples are typically within 1~2 dB of the average SINR.
+
+![Figure A.1: Cumulative Distribution Function (C.D.F.) plots for Coupling gain and DL geometry in the Indoor Hotspot - eMBB test environment. The left plot shows C.D.F. [%] vs. Coupling gain [dB] from -100.0 to -20.0. The right plot shows C.D.F. [%] vs. DL geometry [dB] from -10.0 to 60.0. Both plots compare five configurations: Config. A (4 GHz, Channel model A, 12TRxP) as a dashed blue line, Config. A (4 GHz, Channel model A, 36TRxP) as a solid blue line, Config. A (4 GHz, Channel model B, 12TRxP) as a dashed light blue line, Config. A (4 GHz, Channel model B, 36TRxP) as a solid light blue line, and Config. B (30 GHz, 12TRxP, w/ analog BF) as a dashed red line. In the Coupling gain plot, Config. B (red dashed) reaches 100% C.D.F. around -60 dB, while Config. A (4 GHz) variants reach 100% around -40 dB. In the DL geometry plot, Config. A (4 GHz) variants reach 100% C.D.F. around 10-20 dB, while Config. B (30 GHz) variants reach 100% around 40-50 dB.](79607caa47ed192b11a2c7b17f0b88dd_img.jpg)
+
+Figure A.1: Cumulative Distribution Function (C.D.F.) plots for Coupling gain and DL geometry in the Indoor Hotspot - eMBB test environment. The left plot shows C.D.F. [%] vs. Coupling gain [dB] from -100.0 to -20.0. The right plot shows C.D.F. [%] vs. DL geometry [dB] from -10.0 to 60.0. Both plots compare five configurations: Config. A (4 GHz, Channel model A, 12TRxP) as a dashed blue line, Config. A (4 GHz, Channel model A, 36TRxP) as a solid blue line, Config. A (4 GHz, Channel model B, 12TRxP) as a dashed light blue line, Config. A (4 GHz, Channel model B, 36TRxP) as a solid light blue line, and Config. B (30 GHz, 12TRxP, w/ analog BF) as a dashed red line. In the Coupling gain plot, Config. B (red dashed) reaches 100% C.D.F. around -60 dB, while Config. A (4 GHz) variants reach 100% around -40 dB. In the DL geometry plot, Config. A (4 GHz) variants reach 100% C.D.F. around 10-20 dB, while Config. B (30 GHz) variants reach 100% around 40-50 dB.
+
+Figure A.1 Coupling gain and DL geometry of Indoor Hotspot - eMBB test environment
+
+![Figure A.2 (Left): C.D.F. [%] vs Coupling gain [dB] for Dense Urban - eMBB test environment. The plot shows three curves: Config. A (4 GHz, Channel model A, w/ analog BF) in blue, Config. A (4 GHz, Channel model B, w/ analog BF) in light blue, and Config. B (30 GHz, w/ analog BF) in red. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.](730b6615db6d402580db1024a7f4e163_img.jpg)
+
+Figure A.2 (Left): C.D.F. [%] vs Coupling gain [dB] for Dense Urban - eMBB test environment. The plot shows three curves: Config. A (4 GHz, Channel model A, w/ analog BF) in blue, Config. A (4 GHz, Channel model B, w/ analog BF) in light blue, and Config. B (30 GHz, w/ analog BF) in red. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.
+
+![Figure A.2 (Right): C.D.F. [%] vs DL geometry [dB] for Dense Urban - eMBB test environment. The plot shows three curves: Config. A (4 GHz, Channel model A, w/ analog BF) in blue, Config. A (4 GHz, Channel model B, w/ analog BF) in light blue, and Config. B (30 GHz, w/ analog BF) in red. The x-axis ranges from -40.0 to 50.0 dB, and the y-axis ranges from 0 to 100%.](f217ea7a6e9347a9ca4d6173ed57c33e_img.jpg)
+
+Figure A.2 (Right): C.D.F. [%] vs DL geometry [dB] for Dense Urban - eMBB test environment. The plot shows three curves: Config. A (4 GHz, Channel model A, w/ analog BF) in blue, Config. A (4 GHz, Channel model B, w/ analog BF) in light blue, and Config. B (30 GHz, w/ analog BF) in red. The x-axis ranges from -40.0 to 50.0 dB, and the y-axis ranges from 0 to 100%.
+
+Figure A.2 Coupling gain and DL geometry of Dense Urban - eMBB test environment
+
+![Figure A.3 (Left): C.D.F. [%] vs Coupling gain [dB] for Rural - eMBB test environment. The plot shows six curves: Config. A (1732 m, 700 MHz, Channel model A) in blue, Config. A (1732 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 4 GHz, Channel model A) in red, Config. B (1732 m, 4 GHz, Channel model B) in orange, Config. C (LMLC, 6000 m, 700 MHz, Channel model A) in green, and Config. C (LMLC, 6000 m, 700 MHz, Channel model B) in light green. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.](d0c2bd517f31d89b01136a1847bcdf33_img.jpg)
+
+Figure A.3 (Left): C.D.F. [%] vs Coupling gain [dB] for Rural - eMBB test environment. The plot shows six curves: Config. A (1732 m, 700 MHz, Channel model A) in blue, Config. A (1732 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 4 GHz, Channel model A) in red, Config. B (1732 m, 4 GHz, Channel model B) in orange, Config. C (LMLC, 6000 m, 700 MHz, Channel model A) in green, and Config. C (LMLC, 6000 m, 700 MHz, Channel model B) in light green. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.
+
+![Figure A.3 (Right): C.D.F. [%] vs DL geometry [dB] for Rural - eMBB test environment. The plot shows six curves: Config. A (1732 m, 700 MHz, Channel model A) in blue, Config. A (1732 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 4 GHz, Channel model A) in red, Config. B (1732 m, 4 GHz, Channel model B) in orange, Config. C (LMLC, 6000 m, 700 MHz, Channel model A) in green, and Config. C (LMLC, 6000 m, 700 MHz, Channel model B) in light green. The x-axis ranges from -20.0 to 30.0 dB, and the y-axis ranges from 0 to 100%.](a26b4f52392209236513dd503db41339_img.jpg)
+
+Figure A.3 (Right): C.D.F. [%] vs DL geometry [dB] for Rural - eMBB test environment. The plot shows six curves: Config. A (1732 m, 700 MHz, Channel model A) in blue, Config. A (1732 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 4 GHz, Channel model A) in red, Config. B (1732 m, 4 GHz, Channel model B) in orange, Config. C (LMLC, 6000 m, 700 MHz, Channel model A) in green, and Config. C (LMLC, 6000 m, 700 MHz, Channel model B) in light green. The x-axis ranges from -20.0 to 30.0 dB, and the y-axis ranges from 0 to 100%.
+
+Figure A.3 Coupling gain and DL geometry of Rural - eMBB test environment
+
+![Figure A.4 (Left): C.D.F. [%] vs Coupling gain [dB] for Urban Macro - mMTC test environment. The plot shows four curves: Config. A (500 m, 700 MHz, Channel model A) in blue, Config. A (500 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 700 MHz, Channel model A) in red, and Config. B (1732 m, 700 MHz, Channel model B) in orange. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.](cc3cf220e0c191212afa284c6787da0a_img.jpg)
+
+Figure A.4 (Left): C.D.F. [%] vs Coupling gain [dB] for Urban Macro - mMTC test environment. The plot shows four curves: Config. A (500 m, 700 MHz, Channel model A) in blue, Config. A (500 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 700 MHz, Channel model A) in red, and Config. B (1732 m, 700 MHz, Channel model B) in orange. The x-axis ranges from -160.0 to -40.0 dB, and the y-axis ranges from 0 to 100%.
+
+![Figure A.4 (Right): C.D.F. [%] vs DL geometry [dB] for Urban Macro - mMTC test environment. The plot shows four curves: Config. A (500 m, 700 MHz, Channel model A) in blue, Config. A (500 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 700 MHz, Channel model A) in red, and Config. B (1732 m, 700 MHz, Channel model B) in orange. The x-axis ranges from -15.0 to 35.0 dB, and the y-axis ranges from 0 to 100%.](54d490f646eb3cc3b92ec4abf3030a85_img.jpg)
+
+Figure A.4 (Right): C.D.F. [%] vs DL geometry [dB] for Urban Macro - mMTC test environment. The plot shows four curves: Config. A (500 m, 700 MHz, Channel model A) in blue, Config. A (500 m, 700 MHz, Channel model B) in light blue, Config. B (1732 m, 700 MHz, Channel model A) in red, and Config. B (1732 m, 700 MHz, Channel model B) in orange. The x-axis ranges from -15.0 to 35.0 dB, and the y-axis ranges from 0 to 100%.
+
+Figure A.4 Coupling gain and DL geometry of Urban Macro - mMTC test environment
+
+![Figure A.5: Two cumulative distribution function (CDF) plots for the Urban Macro - URLLC test environment. The left plot shows 'C.D.F. [%]' vs 'Coupling gain [dB]' from -160.0 to -40.0. The right plot shows 'C.D.F. [%]' vs 'DL geometry [dB]' from -15.0 to 35.0. Both plots compare four configurations: Config. A (4 GHz) with Channel model A (dark blue), Config. A (4 GHz) with Channel model B (light blue), Config. B (700 MHz) with Channel model A (red), and Config. B (700 MHz) with Channel model B (orange). In both cases, the curves for each configuration are very close to each other, indicating good agreement between the two channel models.](98ea5e21d919b389f3ce8b17ef4e65f6_img.jpg)
+
+Figure A.5: Two cumulative distribution function (CDF) plots for the Urban Macro - URLLC test environment. The left plot shows 'C.D.F. [%]' vs 'Coupling gain [dB]' from -160.0 to -40.0. The right plot shows 'C.D.F. [%]' vs 'DL geometry [dB]' from -15.0 to 35.0. Both plots compare four configurations: Config. A (4 GHz) with Channel model A (dark blue), Config. A (4 GHz) with Channel model B (light blue), Config. B (700 MHz) with Channel model A (red), and Config. B (700 MHz) with Channel model B (orange). In both cases, the curves for each configuration are very close to each other, indicating good agreement between the two channel models.
+
+**Figure A.5** Coupling gain and DL geometry of Urban Macro - URLLC test environment
+
+A summary of the collected samples for calibration of each test environment and evaluation configuration is shown in Table A.1.
+
+**Table A.1** Sample statistics for ITU-R test environments
+
+| Test environment      | Evaluation configuration          | Channel model / Topology | Number of samples | DL wideband SINR difference compared to average SINR (at 50%-tile CDF point) |
+|-----------------------|-----------------------------------|--------------------------|-------------------|------------------------------------------------------------------------------|
+| Indoor Hotspot - eMBB | Config. A (4 GHz)                 | Channel model A          | 12TRxP            | 16                                                                           |
+|                       |                                   |                          | 36TRxP            | 15                                                                           |
+|                       |                                   | Channel model B          | 12TRxP            | 18                                                                           |
+|                       |                                   |                          | 36TRxP            | 16                                                                           |
+|                       | Config. B (30 GHz)                | Channel model A/B        | 12TRxP            | 17                                                                           |
+|                       |                                   |                          | 36TRxP            | 14                                                                           |
+|                       | Config. C (70 GHz)                | Channel model A/B        | 12TRxP            | 16                                                                           |
+|                       |                                   |                          | 36TRxP            | 12                                                                           |
+| Dense Urban - eMBB    | Config. A (4 GHz)                 | Channel model A          | 16                | <0.8 dB                                                                      |
+|                       |                                   | Channel model B          | 15                | <0.5 dB                                                                      |
+|                       | Config. B (30 GHz)                | Channel model A/B        | 18                | <0.9 dB                                                                      |
+|                       |                                   |                          | 16                | <0.4 dB                                                                      |
+| Rural - eMBB          | Config. A (1732 m, 700 MHz)       | Channel model A          | 18                | <1.3 dB                                                                      |
+|                       |                                   | Channel model B          | 20                | <1.3 dB                                                                      |
+|                       | Config. B (1732 m, 4 GHz)         | Channel model A          | 18                | <0.8 dB                                                                      |
+|                       |                                   | Channel model B          | 20                | <0.9 dB                                                                      |
+|                       | Config. C (LMLC, 6000 m, 700 MHz) | Channel model A          | 15                | <0.9 dB                                                                      |
+|                       |                                   | Channel model B          | 16                | <1.0 dB                                                                      |
+| Urban Macro - mMTC    | Config. A (500 m, 700 MHz)        | Channel model A          | 15                | <0.9 dB                                                                      |
+|                       |                                   | Channel model B          | 16                | <0.6 dB                                                                      |
+|                       | Config. B (1732 m, 700 MHz)       | Channel model A          | 15                | <1.2 dB                                                                      |
+|                       |                                   | Channel model B          | 16                | <0.6 dB                                                                      |
+| Urban Macro - URLLC   | Config. A (4 GHz)                 | Channel model A          | 15                | <0.9 dB                                                                      |
+|                       |                                   | Channel model B          | 17                | <1.0 dB                                                                      |
+|                       | Config. B (700 MHz)               | Channel model A          | 15                | <0.9 dB                                                                      |
+|                       |                                   | Channel model B          | 16                | <1.3 dB                                                                      |
+
+# Annex B: Simulation models and assumptions
+
+## B.1 Calculation of pre-processing SINR
+
+Pre-processing SINR is used for mobility evaluation for SU-MIMO.
+
+The pre-processing SINR is defined on an Rx antenna port with respect to a Tx antenna port.
+
+The following pre-processing SINR formula can be used for a system comprising of  $S$  Tx antenna ports (TXRUs) and  $U$  Rx antenna ports (TXRUs),
+
+$$SINR_{pre- proc} = \frac{\bar{P}_r}{\bar{P}_{I+N}} \quad (B.1-1)$$
+
+where  $\bar{P}_r$  is the average received signal power as given by (B.1-2), and  $\bar{P}_{I+N}$  is the average interference plus noise power as given by (B.1-3).
+
+The average received signal power  $\bar{P}_r$  is over the  $S$  Tx antenna ports and  $U$  Rx antenna ports (similar to (8.1-1) in TR 36.873 [19]) that are expressed as
+
+$$\bar{P}_r \approx \frac{1}{S} \sum_{p=1}^S RSRP_p = \frac{1}{S} \sum_{p=1}^S \left( PL \cdot SF \cdot \sum_{u=1}^U \left( |\alpha_{0,u,p}|^2 + \sum_{n=1}^N \sum_{m=1}^M |\alpha_{n,m,u,p}|^2 \right) \right) \cdot \frac{TX_{power}}{U} \quad (B.1-2)$$
+
+where  $N$  is the number of paths and  $M$  is the number of sub-paths within one path; for NLOS path for  $n=1, \dots, N$ ,
+
+with the notations  $P_n$ ,  $\theta_{n,m,ZOA}$ ,  $\phi_{n,m,AOA}$ ,  $\theta_{n,m,ZOD}$ ,  $\phi_{n,m,AOD}$ ,  $\Phi_{n,m}^{\theta\theta}$ ,  $\Phi_{n,m}^{\theta\phi}$ ,  $\Phi_{n,m}^{\phi\theta}$ ,  $\Phi_{n,m}^{\phi\phi}$  and  $K_{n,m}$  being according to equation (7.3-22) in TR 36.873 [19], and  $K_R$  is the Ricean K-factor;
+
+and for LOS path
+
+with the notations  $\theta_{LOS,ZOA}$ ,  $\phi_{LOS,AOA}$ ,  $\theta_{LOS,ZOD}$ ,  $\phi_{LOS,AOD}$ , and  $\Phi^{LOS}$  being according to equation (7.3-27) in TR 36.873 [19];
+
+and  $F_{tx,p,\theta}$  and  $F_{tx,p,\phi}$  are the field patterns of Tx antenna port  $p$  in the direction of the spherical basis vectors, and respectively,  $F_{rx,u,\theta}$  and  $F_{rx,u,\phi}$  are the field patterns of Rx antenna port  $u$  in the direction of the spherical basis vectors, and respectively; they are given by
+
+$$F_{tx,p,\theta}(\theta_{n,m,ZOD}, \varphi_{n,m,AOD}) = \sum_{k=1}^{N_T} w_k \exp(j2\pi\lambda_0^{-1}(\hat{r}_{tx,n,m}^T \cdot \bar{d}_{tx,k})) F_{tx,k,\theta}(\theta_{n,m,ZOD}, \varphi_{n,m,AOD})$$
+
+$$F_{tx,p,\phi}(\theta_{n,m,ZOD}, \varphi_{n,m,AOD}) = \sum_{k=1}^{N_T} w_k \exp(j2\pi\lambda_0^{-1}(\hat{r}_{tx,n,m}^T \cdot \bar{d}_{tx,k})) F_{tx,k,\phi}(\theta_{n,m,ZOD}, \varphi_{n,m,AOD})$$
+
+$$F_{rx,u,\theta}(\theta_{n,m,ZOA}, \varphi_{n,m,AOA}) = \sum_{l=1}^{N_R} g_l \exp(j2\pi\lambda_0^{-1}(\hat{r}_{rx,n,m}^T \cdot \bar{d}_{rx,l})) F_{rx,l,\theta}(\theta_{n,m,ZOA}, \varphi_{n,m,AOA})$$
+
+$$F_{rx,u,\phi}(\theta_{n,m,ZOA}, \varphi_{n,m,AOA}) = \sum_{l=1}^{N_R} g_l \exp(j2\pi\lambda_0^{-1}(\hat{r}_{rx,n,m}^T \cdot \bar{d}_{rx,l})) F_{rx,l,\phi}(\theta_{n,m,ZOA}, \varphi_{n,m,AOA})$$
+
+where  $N_T$  is the number of antenna elements that virtualizes the Tx antenna port  $p$ ,  $N_R$  is the number of antenna elements that virtualizes the Rx antenna port  $u$ ;  $w_k$  ( $k=1, \dots, N_T$ ) represents a complex weight vector used for virtualization of Tx antenna port  $p$ ,  $g_l$  ( $l=1, \dots, N_R$ ) represents a complex weight vector used for virtualization of Rx antenna port  $u$ ,  $F_{tx,k,\theta}$  and  $F_{tx,k,\phi}$  are the  $k$ th transmit antenna element's field patterns in the direction of the spherical basis vectors, and respectively,  $F_{rx,l,\theta}$  and  $F_{rx,l,\phi}$  are the  $l$ th receive antenna element's field patterns in the direction of the spherical basis vectors, and respectively;
+
+and  $TX_{\text{power}}$  is the total transmit power (over the  $S$  Tx antenna ports) per RE.
+
+The average interference plus noise power  $\bar{P}_{I+N}$  is over  $U$  Rx antenna ports that are expressed as
+
+$$\bar{P}_{I+N} = \frac{1}{U} \text{tr}(\mathbf{R}_{I+N}) \quad (\text{B.1-3})$$
+
+where  $\mathbf{R}_{I+N} = \mathbf{Q} + \mathbf{N}$  is the  $U \times U$  covariance matrix of interference and noise on the same RE as  $TX_{\text{power}}$  is computed,  $\mathbf{Q}$  and  $\mathbf{N}$  are the covariance matrix of the interference and the noise, respectively, and are modeled according to section A.2.1.8 in TR36.814, and  $\text{tr}(\mathbf{R}_{I+N})$  represents the trace of  $\mathbf{R}_{I+N}$ .
+
+## --- B.2 Link level assumption for mobility evaluation
+
+### B.2.1 Scaling factor for link level channel model
+
+According to Report ITU-R M.2412 [6], for the link level simulation part for mobility, reliability, and connection density evaluation, the delay spreads and angular spreads (for AoA, AoD, ZoA, and ZoD) in link-level channel model are scaled to the median values for the environment and channel type (LOS/NLOS) evaluated, and system-level channel model variant (model A or model B) selected.
+
+According to system-level channel model defined in Report ITU-R M.2412 [6], the scaling parameters of delay spreads and angular spreads are given in Table B.2.1-1.
+
+Table B.2.1-1 Scaling parameters for delay spreads and angular spreads for related test environments
+
+| Parameters                                                                   | Indoor Hotspot-eMBB |                    |                      |                    |                      |                    | Dense Urban-eMBB    |                      |                      |                      | Rural-eMBB                    |                      |
+|------------------------------------------------------------------------------|---------------------|--------------------|----------------------|--------------------|----------------------|--------------------|---------------------|----------------------|----------------------|----------------------|-------------------------------|----------------------|
+|                                                                              | Config A<br>(4 GHz) |                    | Config B<br>(30 GHz) |                    | Config C<br>(70 GHz) |                    | Config A<br>(4 GHz) |                      | Config B<br>(30 GHz) |                      | Config A/B<br>(700 MHz/4 GHz) |                      |
+| Link-level<br>Channel<br>model                                               | LOS:<br>CDL/TDL-iv  | NLOS:<br>CDL/TDL-i | LOS:<br>CDL/TDL-iv   | NLOS:<br>CDL/TDL-i | LOS:<br>CDL/TDL-iv   | NLOS:<br>CDL/TDL-i | LOS:<br>CDL/TDL-v   | NLOS:<br>CDL/TDL-iii | LOS:<br>CDL/TDL-v    | NLOS:<br>CDL/TDL-iii | LOS:<br>CDL/TDL-v             | NLOS:<br>CDL/TDL-iii |
+| Delay spread<br>scaling<br>parameter<br>$DS_{desired}$ (ns)                  | 20                  | 39                 | 19.5                 | 26                 | 19.5                 | 20                 | 93                  | 363                  | 79                   | 263                  | 32                            | 37                   |
+| AoA angular<br>spreads<br>scaling<br>parameter<br>$AS_{desired}$<br>(degree) | 42                  | 59                 | 32                   | 50                 | 27                   | 46                 | 65                  | 74                   | 65                   | 48                   | 33                            | 33                   |
+| AoD angular<br>spreads<br>scaling<br>parameter<br>$AS_{desired}$<br>(degree) | 40                  | 42                 | 40                   | 42                 | 40                   | 42                 | 14                  | 26                   | 17                   | 22                   | 8                             | 9                    |
+| ZoA angular<br>spreads<br>scaling<br>parameter<br>$AS_{desired}$<br>(degree) | 17                  | 18                 | 11                   | 14                 | 9                    | 13                 | 9                   | 18                   | 9                    | 11                   | 3                             | 4                    |
+| ZoD angular<br>spreads<br>scaling<br>parameter<br>$AS_{desired}$<br>(degree) | 10                  | 12                 | 1                    | 12                 | 0.4                  | 12                 | (NOTE 1)            | (NOTE 1)             | (NOTE 1)             | (NOTE 1)             | (NOTE 1)                      | (NOTE 1)             |
+| K-factor (dB)                                                                | 13.3                | -                  | 13.3                 | -                  | 13.3                 | -                  | 22                  | -                    | 22                   | -                    | 22                            | -                    |
+
+NOTE 1: This value is derived by the 50%-tile point of CDF of the mean value of ZoD spread (as defined in system level channel model) of all UEs based on UE dropping in system level simulation. The mean value of ZoD spread of a UE is calculated according to the formula given in Table B.2.1-2 and Table B.2.1-3 for Dense Urban – eMBB and Rural – eMBB test environment, respectively, where  $d_{2D}$  and  $h_{UT}$  of a UE is determined by the UE dropping.
+
+**Table B.2.1-2 Mean value calculation for UMa ZoD spread**
+
+|       | Frequency                                       | Parameters          | UMa_x                                                       |                                                            |
+|-------|-------------------------------------------------|---------------------|-------------------------------------------------------------|------------------------------------------------------------|
+|       |                                                 |                     | LOS                                                         | NLOS                                                       |
+|       |                                                 |                     | LOS O-to-I                                                  | NLOS O-to-I                                                |
+| UMa_A | $0.5 \text{ GHz} \leq f_c \leq 6 \text{ GHz}$   | $\mu_{\text{gZSD}}$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.75]$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.9]$ |
+|       | $6 \text{ GHz} < f_c \leq 100 \text{ GHz}$      | $\mu_{\text{gZSD}}$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.75]$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.9]$ |
+| UMa_B | $0.5 \text{ GHz} \leq f_c \leq 100 \text{ GHz}$ | $\mu_{\text{gZSD}}$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.75]$ | $\max[-0.5, -2.1(d_{2D}/1000) - 0.01(h_{UT} - 1.5) + 0.9]$ |
+
+**Table B.2.1-3 Mean value calculation for RMa ZoD spread**
+
+|                | Frequency                                                                                                      | Parameters          | RMa_x                                                        |                                                              |
+|----------------|----------------------------------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------------|--------------------------------------------------------------|
+|                |                                                                                                                |                     | LOS                                                          | NLOS / O-to-I                                                |
+| RMa_A<br>RMa_B | RMa_A: $0.5 \text{ GHz} \leq f_c \leq 6 \text{ GHz}$ ,<br>RMa_B: $0.5 \text{ GHz} \leq f_c \leq 7 \text{ GHz}$ | $\mu_{\text{gZSD}}$ | $\max(-1, -0.17*(d_{2D}/1000) - 0.01*(h_{UT} - 1.5) + 0.22)$ | $\max(-1, -0.19*(d_{2D}/1000) - 0.01*(h_{UT} - 1.5) + 0.28)$ |
+
+### B.2.2 TXRU pattern and inter-port spacing in link level simulation
+
+The companies report the antenna port pattern used in link level simulation (LLS). If the CDL channel model is used in LLS, the following three options can be used for reference.
+
+- Option 1: 0dBi omni-directional gain is assumed for Tx and Rx antenna ports
+- Option 2: 0dBi gain (linear gain = 1) for the paths within the 3dB beamwidth; linear gain = 0 ( $-\infty$  dB gain) for the paths outside the 3dB beamwidth.
+- Option 3: Use the pattern defined in Section 8.5 in Report ITU-R M.2412 [6] for BS and UE side with maximum directional gain of 0dBi for related test environments.
+
+The inter-port spacing calculation is reported by the companies. The calculation method given by equation (B.2.2-1) and (B.2.2-2) as shown below can be used for reference.
+
+The Tx horizontal and vertical inter-port spacing (for the same polarization) can be calculated by
+
+$$d_{tx\_port,H} = d_{tx\_element,H} \times N_T^H \tag{B.2.2-1}$$
+
+$$d_{tx\_port,V} = d_{tx\_element,V} \times N_T^V \tag{B.2.2-2}$$
+
+where  $d_{tx\_element,H}$  and  $d_{tx\_element,V}$  are the Tx inter-element spacing on horizontal and vertical domain, respectively, and  $N_T^H$  and  $N_T^V$  are the number of antenna elements on the same polarization that virtualizes the Tx antenna port on horizontal and vertical domain, respectively. An illustration is given in Figure B.2.2-1.
+
+![Figure B.2.2-1: Illustration of inter-port spacing. The diagram shows a grid of 4x8 antenna elements (dots). Brackets indicate that a group of 2 horizontal elements forms a port with spacing d_tx_port,H, where N_T^H = 2. A group of 4 vertical elements forms a port with spacing d_tx_port,V, where N_T^V = 4. Individual element spacings are marked as d_tx_element,H and d_tx_element,V.](d78e519e9186d30807342196675fd440_img.jpg)
+
+The diagram shows a grid of antenna elements represented by black dots.   
+ Horizontal inter-element spacing is  $d_{tx\_element,H}$ .   
+ Vertical inter-element spacing is  $d_{tx\_element,V}$ .   
+ Horizontal inter-port spacing  $d_{tx\_port,H}$  spans  $N_T^H = 2$  elements.   
+ Vertical inter-port spacing  $d_{tx\_port,V}$  spans  $N_T^V = 4$  elements.
+
+Figure B.2.2-1: Illustration of inter-port spacing. The diagram shows a grid of 4x8 antenna elements (dots). Brackets indicate that a group of 2 horizontal elements forms a port with spacing d\_tx\_port,H, where N\_T^H = 2. A group of 4 vertical elements forms a port with spacing d\_tx\_port,V, where N\_T^V = 4. Individual element spacings are marked as d\_tx\_element,H and d\_tx\_element,V.
+
+Figure B.2.2-1 Illustration of inter-port spacing
+
+## B.3 Evaluation assumption for peak spectral efficiency and peak data rate
+
+### B.3.1 Evaluation assumption for NR
+
+#### B.3.1.1 NR downlink
+
+Evaluation parameters for NR DL peak spectral efficiency and peak data rate is shown in Table B.3.1.1-1. The notations can be found in equation (5.1.1-1) in Section 5.1.1.
+
+**Table B.3.1.1-1 NR Parameters for DL peak spectral efficiency and peak data rate evaluation**
+
+| Parameters                                    | Values                                                                              | Remarks                                                                                 |
+|-----------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| Max. number of layers<br>$\nu_{Layers}^{(j)}$ | For FR1: 8<br>For FR2: 6, 8                                                         |                                                                                         |
+| Highest modulation order<br>$Q_m^{(j)}$       | 8                                                                                   | 256QAM                                                                                  |
+| Scaling factor of modulation<br>$f^{(j)}$     | 1                                                                                   |                                                                                         |
+| Max. coding rate<br>$R_{max}$                 | 948/1024 = 0.9258                                                                   |                                                                                         |
+| $\mu$                                         | 0, 1, 2, 3                                                                          | SCS = $2^\mu \times 15$ kHz                                                             |
+| $N_{PRB}^{BW(j),\mu}$                         | See Table 8.1.1-2 for FR1 and FR2 for specific component carrier bandwidth and SCS. | The maximum number of RBs for the specific component carrier bandwidth and SCS is used. |
+
+The overhead assumption used in the NR DL evaluation is shown in Table B.3.1.1-2.
+
+**Table B.3.1.1-2 Overhead assumption for NR DL evaluation**
+
+|     | Applied duplexing | FR1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | FR2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+|-----|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OH1 | FDD, TDD (DDDSU)  | <ul style="list-style-type: none"> <li>• PDCCH: CORESET of 24 PRBs (4 CCE) in every slot               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/slot</li> </ul> </li> <li>• TRS burst of 2 slots with periodicity of 20ms and occupies 52 PRBs               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/20 ms</li> </ul> </li> <li>• DMRS: Type 2, 16 RE/PRB/slot for 8 layers</li> <li>• CSI-RS: 8 CSI-RS ports with periodicity of 20ms               <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/20 ms</li> </ul> </li> <li>• 1 SS/PBCH blocks (SSB) per 20ms; one SSB occupies 960REs = 4 OFDM symbols <math>\times</math> 20 PRB <math>\times</math> 12 REs/PRB</li> </ul> <p>NOTE1: if the channel bandwidth is less than the bandwidth of SSB, then SSB is not transmitted and the overhead of SS/PBCH block is zero.</p> <p>NOTE2: If the channel bandwidth is less than TRS bandwidth, the TRS bandwidth is assumed to be equal to the channel bandwidth.</p> | <ul style="list-style-type: none"> <li>• PDCCH: CORESET of 24 PRBs (4 CCE) in every slot               <ul style="list-style-type: none"> <li>- 12 RE/PRB/slot</li> </ul> </li> <li>• TRS burst of 2 slots with periodicity of 10ms and occupies 52 PRBs               <ul style="list-style-type: none"> <li>- 12 RE/PRB/slot</li> </ul> </li> <li>• DMRS: Type 2, 12 RE/PRB/slot for 6 layers</li> <li>• CSI-RS: 8 CSI-RS ports with periodicity of 10ms               <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/10 ms</li> </ul> </li> <li>• 8 SSB per 20ms; one SSB occupies 960REs = 4 OFDM symbols <math>\times</math> 20 PRB <math>\times</math> 12 REs/PRB</li> <li>• PTRS: 1 port, frequency density is 4 PRB, and time domain density is 1 symbol</li> <li>• CSI-RS for BM: 1 CSI-RS port with periodicity of 10ms               <ul style="list-style-type: none"> <li>- 2 RE/PRB/10ms</li> </ul> </li> </ul> <p>NOTE: If the channel bandwidth is less than TRS bandwidth, the TRS bandwidth is assumed to be equal to the channel bandwidth.</p> |
+| OH2 | FDD, TDD (DDDSU)  | <ul style="list-style-type: none"> <li>• PDCCH: 2 CCE               <ul style="list-style-type: none"> <li>◆ 144 RE/slot</li> </ul> </li> <li>• TRS burst of 2 slots with periodicity of 80ms and occupies 52 PRBs               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/80 ms</li> </ul> </li> <li>• DMRS: Type 2, 16 RE/PRB/slot</li> <li>• CSI-RS: 8 CSI-RS ports with periodicity of</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | -                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
+|     |                                         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+|-----|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|     |                                         | 20ms <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/20 ms</li> <li>CSI-IM: 4 CSI-RS ports with periodicity of 20ms</li> <li>◆ 4 RE/PRB/20 ms</li> <li>1 SSB</li> </ul> 960 RE/20 ms                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| OH3 | FDD, TDD (DSUUD, S slot = 11DL:1GP:2UL) | <ul style="list-style-type: none"> <li>• PDCCH: 4 CCE in every slot</li> <li>• TRS: <math>\min(52, N_{RB}^{BWP})</math> PRB wide, occurs every 80 ms</li> <li>• DMRS: Type 2, 16 RE/PRB/slot</li> <li>• CSI-RS: 8 CSI-RS ports with 1 RE/RB/port, with periodicity of 20ms</li> <li>• CSI-IM: 4 RE/PRB, with periodicity of 20ms</li> <li>• 1 SSB per 20ms</li> </ul> NOTE1: If the number of REs is less than 240 at the evaluated channel bandwidth and SCS, the SSB is assumed transmitted by lower SCS and the overhead of SS/PBCH block is 1 SSB per 20ms.                                                                                                                                                                                                                                                                                      | <ul style="list-style-type: none"> <li>• PDCCH: 4 CCE in every slot</li> <li>• TRS: <math>\min(52, N_{RB}^{BWP})</math> PRB wide, occurs every 10 ms</li> <li>• DMRS: Type 2, 12 RE/PRB/slot</li> <li>• CSI-RS: 8 CSI-RS ports with 1 RE/RB/port, with periodicity of 2.5ms</li> <li>• CSI-IM: 4 RE/PRB, with periodicity of 2.5ms</li> <li>• 8 SSB per 20ms</li> <li>• PTRS: 1 port, frequency density is 4 PRB, and time domain density is 1 symbol</li> </ul> |
+| OH4 | FDD, TDD (DSUUD, S slot = 6DL:2GP:6UL)  | Overhead is adapted to 0.14 to match the capability of TS38.306<br>For FDD: <ul style="list-style-type: none"> <li>• PDCCH: 4 CCE + 1 symbol per slot</li> <li>  ◆ 12*24 RE/slot</li> <li>• TRS</li> <li>  ◆ 2x4 RE/PRB/20 slots</li> <li>• DMRS: 2 symbol Type 2 FL DMRS with RS on 2 combs</li> <li>  ◆ 16 RE/PRB/slot</li> <li>• CSI-RS: 8-port CSI-RS resources</li> <li>  ◆ 8 RE/PRB/10 slots</li> <li>• 1 SSB</li> <li>  ◆ 960 RE/20 slots</li> </ul> For TDD: <ul style="list-style-type: none"> <li>• PDCCH: 2 CCE + 1 symbol per slot</li> <li>  ◆ 12*12 RE/slot</li> <li>• TRS</li> <li>  ◆ 2x4 RE/PRB/40 slots</li> <li>• DMRS: 2 symbol Type 2 FL DMRS with RS on 2 combs</li> <li>  ◆ 16 RE/PRB/slot</li> <li>• CSI-RS: 8-port CSI-RS resources</li> <li>  ◆ 8 RE/PRB/20 slots</li> <li>• 1 SSB</li> <li>  ◆ 960 RE/20 slots</li> </ul> | Overhead is adapted to 0.18 to match the capability of TS38.306 <ul style="list-style-type: none"> <li>• PDCCH: 4 CCE + 1 symbol per slot</li> <li>  ◆ 12*24 RE/slot</li> <li>• TRS</li> <li>  ◆ 8 RE/PRB/16 slots</li> <li>• DMRS: 2 symbol Type 2 FL DMRS with RS on 2 combs</li> <li>  ◆ 16 RE/PRB/slot</li> <li>• CSI-RS: 8-port CSI-RS resources</li> <li>  ◆ 8 RE/PRB/16 slots</li> <li>• 8 SSB</li> <li>  ◆ 8x960 RE/PRB/80 slots</li> </ul>              |
+
+#### B.3.1.2 NR uplink
+
+Evaluation parameters for NR UL peak spectral efficiency and peak data rate is shown in Table B.3.1.2-1. The notations can be found in equation (5.1.1-1) in Section 5.1.1.
+
+**Table B.3.1.2-1 NR Parameters for UL peak spectral efficiency and peak data rate evaluation**
+
+| Parameters                                  | Values                                                                              | Remarks                                                                                 |
+|---------------------------------------------|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
+| Max. number of layers<br>$v_{Layers}^{(j)}$ | 4                                                                                   |                                                                                         |
+| Highest modulation order<br>$Q_m^{(j)}$     | 8                                                                                   | 256QAM                                                                                  |
+| Scaling factor of modulation<br>$f^{(j)}$   | 1                                                                                   |                                                                                         |
+| Max. coding rate<br>$R_{max}$               | $948/1024 = 0.9258$                                                                 |                                                                                         |
+| $\mu$                                       | 0, 1, 2, 3                                                                          | $SCS = 2^\mu \times 15$ kHz                                                             |
+| $N_{PRB}^{BW(j),\mu}$                       | See Table 8.1.1-2 for FR1 and FR2 for specific component carrier bandwidth and SCS. | The maximum number of RBs for the specific component carrier bandwidth and SCS is used. |
+
+The overhead assumption used in the NR UL evaluation is shown in Table B.3.1.1-2.
+
+**Table B.3.1.2-2 Overhead assumption for NR UL evaluation**
+
+|     | Applied duplexing                       | FR1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | FR2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|-----|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OH1 | FDD, TDD (DDDSU)                        | <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 1 PRB and 1 symbol in every UL slot; 12 RE/slot</li> <li>• DMRS: Type I, one complete symbol; 12 RE/PRB/slot</li> <li>• SRS: 1 symbol with periodicity of 10ms for FDD; 1 symbol with periodicity of 20ms for TDD</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 1 PRB and 1 symbol in every UL slot; 12 RE/slot</li> <li>• DMRS: Type I, one complete symbol; 12 RE/PRB/slot</li> <li>• SRS: 1 symbol with periodicity of 5ms</li> <li>• PTRS: 2 ports PTRS, frequency density is 4 PRB, and time domain density is 1 symbol</li> </ul>                                                                                                                                                                           |
+| OH2 | FDD, TDD (DDDSU)                        | <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 1 PRB and 1 symbol in every UL slot; 12 RE/slot</li> <li>• DMRS: Type II, 8 RE/PRB/slot</li> <li>• SRS: 1 symbol with periodicity of 20ms</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | -                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| OH3 | FDD, TDD (DSUUD, S slot = 11DL:1GP:2UL) | <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 1 PRB over 1 symbol in every slot;</li> <li>• DMRS: Type II, 8 RE/PRB/slot for slot carrying SRS; otherwise 12 RE/PRB/slot.</li> <li>• SRS: Resources ensuring the whole bandwidth measured within 20ms</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 1 PRB over 1 symbol in every slot;</li> <li>• DMRS: Type I, 12 RE/PRB/slot</li> <li>• SRS: Resources ensuring the whole bandwidth measured within 2.5ms</li> <li>• PTRS: 2 ports, frequency density is 4 RB, and time domain density is 1 symbol</li> </ul>                                                                                                                                                                                       |
+| OH4 | FDD, TDD (DSUUD, S slot = 6DL:2GP:6UL)  | Overhead is adapted to 0.08 to match the capability of TS38.306.<br>For FDD: <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 2 symbols and 8 PRBs;               <ul style="list-style-type: none"> <li>◆ 192 RE per slot</li> </ul> </li> <li>• DMRS: 1 symbol Type 2 FL DMRS in each slot with RS on 2 combs;               <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/slot</li> </ul> </li> <li>• SRS               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/5 slots</li> </ul> </li> </ul> For TDD: <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 2 symbols and 8 PRBs;               <ul style="list-style-type: none"> <li>◆ 192 RE/2 slots</li> </ul> </li> <li>• DMRS: 1 symbol Type 2 FL DMRS in each slot with RS on 2 combs;               <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/slot</li> </ul> </li> <li>• SRS               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/10 slots</li> </ul> </li> </ul> | Overhead is adapted to 0.1 to match the capability of TS38.306. <ul style="list-style-type: none"> <li>• PUCCH: short PUCCH with 2 symbols and 8 PRBs;               <ul style="list-style-type: none"> <li>◆ 192 RE/2 slots</li> </ul> </li> <li>• DMRS: 1 symbol Type 2 FL DMRS in each slot with RS on 2 combs;               <ul style="list-style-type: none"> <li>◆ 8 RE/PRB/slot</li> </ul> </li> <li>• SRS               <ul style="list-style-type: none"> <li>◆ 12 RE/PRB/5 slots</li> </ul> </li> </ul> |
+
+### B.3.2 Evaluation assumption for LTE
+
+#### B.3.2.1 LTE downlink
+
+Evaluation parameters for LTE DL peak spectral efficiency and peak data rate is shown in Table B.3.2.1-1. The notations can be found in equation (5.1.1-1) in Section 5.1.1.
+
+**Table B.3.2.1-1 LTE Parameters for DL peak spectral efficiency and peak data rate evaluation**
+
+| Parameters                                  | Values                                                            | Remarks                                                                |
+|---------------------------------------------|-------------------------------------------------------------------|------------------------------------------------------------------------|
+| Max. number of layers<br>$v_{Layers}^{(j)}$ | 8                                                                 |                                                                        |
+| Highest modulation order<br>$Q_m^{(j)}$     | 8<br>10                                                           | 256QAM<br>1024QAM                                                      |
+| Scaling factor of modulation<br>$f^{(j)}$   | 1                                                                 |                                                                        |
+| Max. coding rate<br>$R_{max}$               | According to Transport block size (TBS) table defined in TS36.213 |                                                                        |
+| $N_{PRB}^{BW(j)}$                           | See Table 8.1.2-2 for specific component carrier bandwidth.       | The maximum number of RBs for the specific component carrier bandwidth |
+
+|  |  |          |
+|--|--|----------|
+|  |  | is used. |
+|--|--|----------|
+
+The overhead assumption used in the LTE DL evaluation is shown in Table B.3.2.1-1.
+
+**Table B.3.2.1-2 Overhead assumption for LTE DL evaluation**
+
+|     | Applied duplexing | FR1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|-----|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OH1 | FDD,<br>TDD       | <ul style="list-style-type: none"> <li>- PBCH: 240 RE per 10ms (not including CRS)</li> <li>- PSS/SSS: 288 RE per 10ms</li> <li>- PDCCH: 1 complete symbols</li> <li>- CRS: 1 port for non-MBSFN; 6 RE/PRB; 0 port for MBSFN.</li> <li>- DMRS: 8 ports, 24RE per PRB</li> <li>- CSI-RS: 8 CSI-RS ports with periodicity of 40ms; 8 -RE/PRB/40ms.</li> <li>- MBSFN: 6 subframes per radio frame for MBSFN for FDD; 4 subframes per radio frame for MBSFN for TDD with DSUDD; 2 subframes per radio frame for MBSFN for TDD with DSUUD.</li> </ul> |
+
+#### B.3.2.2 LTE uplink
+
+Evaluation parameters for LTE DL peak spectral efficiency and peak data rate is shown in Table B.3.2.2-1. The notations can be found in equation (5.1.1-1) in Section 5.1.1.
+
+**Table B.3.2.2-1 LTE Parameters for UL peak spectral efficiency and peak data rate evaluation**
+
+| Parameters                                  | Values                                                            | Remarks                                                                         |
+|---------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| Max. number of layers<br>$v_{Layers}^{(j)}$ | 4                                                                 |                                                                                 |
+| Highest modulation order<br>$Q_m^{(j)}$     | 8                                                                 | 256QAM                                                                          |
+| Scaling factor of modulation<br>$f^{(j)}$   | 1                                                                 |                                                                                 |
+| Max. coding rate<br>$R_{max}$               | According to Transport block size (TBS) table defined in TS36.213 |                                                                                 |
+| $N_{PRB}^{BW(j)}$                           | See Table 8.1.2-2 for specific component carrier bandwidth.       | The maximum number of RBs for the specific component carrier bandwidth is used. |
+
+The overhead assumption used in the LTE UL evaluation is shown in Table B.3.2.1-2.
+
+**Table B.3.2.1-2 Overhead assumption for LTE UL evaluation**
+
+|     | Applied duplexing | FR1                                                                                                                                                                             |
+|-----|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OH1 | FDD, TDD          | <ul style="list-style-type: none"> <li>- PUCCH: 2 PRBs in every uplink subframe</li> <li>- DMRS: 2 complete symbols, 24 RE per PRB</li> <li>- SRS: 1 symbol per 10ms</li> </ul> |
+
+## --- **B.4 Detailed assumptions and evaluation results for simulation related technical performance requirements**
+
+### **B.4.1 Detailed assumptions and results for average and 5<sup>th</sup> percentile user spectral efficiency**
+
+The detailed assumptions and results for average and 5<sup>th</sup> percentile user spectral efficiency can be found in the attached document "**B.4.1\_eMBB\_SE.zip**".
+
+### **B.4.2 Detailed assumptions and results for mobility**
+
+The detailed assumptions and results for mobility can be found in the attached document "**B.4.2\_Mobility.zip**".
+
+### **B.4.3 Detailed assumptions and results for user experienced data rate**
+
+The detailed assumptions and results for user experienced data rate for multi-band/layer can be found in the attached document "**B.4.3\_UserExpDataRate.zip**".
+
+### **B.4.4 Detailed assumptions and results for reliability**
+
+The detailed assumptions and results for reliability can be found in the attached document "**B.4.4\_Reliability.zip**".
+
+### **B.4.5 Detailed assumptions and results for connection density**
+
+The detailed assumptions and results for connection density can be found in the attached document "**B.4.5\_ConnectionDensity.zip**".
+
+## B.5 Simulation results of spectral efficiency for Configuration B in Dense Urban – eMBB with modified ITU-R assumptions (for information only)
+
+The evaluation results of average spectral efficiency and the 5<sup>th</sup> percentile spectral efficiency of evaluation configuration B in Dense Urban – eMBB test environment with modified ITU-R parameters/assumptions are shown in this section for information. The detailed assumptions for the evaluations shown in this section can be found in Appendix B.4.1.
+
+The evaluation results of DL spectral efficiency for NR TDD with 100% low-loss penetration assumption are provided in Table B.5-1. It should be noted that Report ITU-R M.2412 [6] defines 80% low loss and 20% high loss for configuration B.
+
+Note that the capability of NR in larger bandwidth are evaluated for DL spectral efficiency. The values of the larger bandwidths are shown together with the evaluation results.
+
+**Table B.5-1 DL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz, 100% low-loss penetration)**
+
+### **a) NR TDD**
+
+| Scheme and antenna configuration                                                                                         | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW= 80MHz / 100 MHz | BW= 200MHz | BW= 400MHz |
+|--------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|---------------------|------------|------------|
+|                                                                                                                          |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                     |            |            |
+| 128x8 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;4,16);<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8                              | 1                 | 21.6                | 24.2       | 25.4       |
+|                                                                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225                            |                   | 0.58                | 0.65       | 0.68       |
+| 128x8 MU-MIMO, Type I codebook; Wideband (2 panel@UE)<br>gNB Config = (8,16,2,1,1;4,16);<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8                              | 1                 | 16.90               | 18.90      | 19.80      |
+|                                                                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225                            |                   | 0.44                | 0.49       | 0.51       |
+
+The evaluation results of UL spectral efficiency for NR TDD with 100% low loss penetration assumption are provided in Table B.5-2. It should be noted that Report ITU-R M.2412 [6] defines 80% low loss and 20% high loss penetration for configuration B.
+
+**Table B.5-2 UL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz, 100% low-loss penetration)**
+
+#### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                      | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW=80MHz / 100MHz |
+|-----------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|-------------------|
+|                                                                                                                       |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                   |
+| 8x128 MU-MIMO, Codebook based, OFDMA, (2 panel@UE);<br>gNB Config = (8,16,2,1,1;4,16)<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4                              | 1                 | 11.3              |
+|                                                                                                                       |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15                             |                   | 0.41              |
+
+The evaluation results with admission control are provided in Tables B.5-3 and B.5-4. For admission control, it means the users with the pathloss value larger than a given threshold is not admitted to access the network, and they are excluded in the derivation of the 5<sup>th</sup> percentile user spectral efficiency, instead of estimating the 5<sup>th</sup> percentile user spectral efficiency from all possible user locations, as defined in Report ITU-R M.2412 [6].
+
+The evaluation results of DL spectral efficiency for NR TDD with admission control are provided in Table B.5-3.
+
+**Table B.5-3 DL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz, with admission control)**
+
+#### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                         | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW= 80MHz / 100 MHz | BW= 200MHz | BW= 400MHz |
+|--------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|---------------------|------------|------------|
+|                                                                                                                          |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                     |            |            |
+| 8x4 MU-MIMO, Reciprocity based; 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;1,4,16);<br>UE Config = (2,4,2,1,2; 1,1) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8                              | 1                 | 8.37                | 9.62       | 10.15      |
+|                                                                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225                            |                   | 0.26                | 0.30       | 0.32       |
+| 8x2 MU-MIMO, Reciprocity based; 2T SRS (2 panel@UE)<br>gNB Config = (16,8,2,1,1;2,2);<br>UE Config = (2,4,2,1,2; 1,1)    | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 7.8                              | 1                 | 9.38                | 10.77      | 11.36      |
+|                                                                                                                          |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.225                            |                   | 0.28                | 0.32       | 0.34       |
+
+The evaluation results of UL spectral efficiency for NR TDD with admission control are provided in Table B.5-4.
+
+**Table B.5-4 UL spectral efficiency for NR in Dense Urban – eMBB  
+(Evaluation configuration B, CF=30 GHz, with admission control)**
+
+### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                                   | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW=80MHz / 100MHz |
+|--------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|-------------------|
+|                                                                                                                    |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                   |
+| 4x8 MU-MIMO, Codebook based, OFDMA, (2 panel@UE);<br>gNB Config = (4,8,2,2,2;1,1)<br>UE Config = (2,4,2,1,2; 1,1)  | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 5.4                              | 1                 | 5.75              |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15                             |                   | 0.22              |
+| 2x2 MU-MIMO, Codebook based, OFDMA, (2 panel@UE);<br>gNB Config = (16,8,2,1,1;1,1)<br>UE Config = (4,4,2,1,2; 1,1) | 120                       | DDDU            | Average [bit/s/Hz/TRxP]          | 5.4                              | 1                 | 5.52              |
+|                                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.15                             |                   | 0.16              |
+
+## B.6 Simulation results of Configuration C for Indoor Hotspot – eMBB test environment (for information only)
+
+The evaluation results of spectral efficiency and area traffic capacity of evaluation configuration C (carrier frequency = 70 GHz) in Indoor Hotspot – eMBB test environment are shown in this section for information only.
+
+Frequency ranges corresponding to Configuration C are not supported in 3GPP NR Rel-15 and 16 specifications.
+
+Some preliminary evaluations were provided by a few companies for configuration C by using existing numerologies specified for FR2 in 3GPP NR Rel-15 and 16 specifications. 3GPP will be developing the specifications for the frequency range from 52.6 GHz to 114 GHz carrier frequencies after Rel-16. The evaluation for Configuration C took an ideal assumption that the physical layer abstraction for FR2 can be also used for 70 GHz CF. Therefore, there is no agreement in 3GPP that the same waveform, numerologies, or simulation assumptions as in existing FR2 can be also used for 70 GHz CF.
+
+The detailed assumptions for the evaluations shown in this section can be found in Appendix B.4.1.
+
+### B.6.1 Evaluation configuration C (CF = 70 GHz) for spectral efficiency
+
+The evaluation results of DL average and the 5<sup>th</sup> percentile user spectral efficiency spectral efficiency for NR for evaluation configuration C with 12TRxP are provided in Table B.6.1-1. The sub-carrier spacing of 60 kHz and 120 kHz are employed.
+
+Similar to the evaluation of NR in Section 5.4, it is noted that the component carrier bandwidth of NR can be larger than the simulation bandwidth as defined in Report ITU-R M.2412 [6]. For those larger bandwidth cases, the guard band ratio can be further decreased; and the OFDM symbol occupation by PDCCH is expected to be reduced, even to less than one OFDM symbol due to the capability of PDCCH resource sharing with PDSCH.
+
+Such capabilities are evaluated for DL spectral efficiency. The values of the assumed bandwidths are shown together with the evaluation results.
+
+**Table B.6.1-1 DL spectral efficiency for NR in Indoor Hotspot – eMBB (Evaluation configuration C, CF=70 GHz, for 12TRxP)**
+
+**(a) NR FDD**
+
+| Scheme and antenna configuration                                                                           | Sub-carrier spacing (kHz) | ITU Requirement                  |     | Number of samples | BW=40 MHz |
+|------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------|-----|-------------------|-----------|
+|                                                                                                            |                           | Average [bit/s/Hz/TRxP]          | 9   |                   |           |
+| 32x8 MU-MIMO Type II codebook (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1) | 60                        | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 12.87     |
+|                                                                                                            |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.47      |
+| 32x8 MU-MIMO Type II codebook (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1) | 120                       | Average [bit/s/Hz/TRxP]          | 9   | 1                 | 11.43     |
+|                                                                                                            |                           | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3 |                   | 0.41      |
+
+#### (b) NR TDD
+
+| Scheme and antenna configuration                                                                   | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW= 80MHz / 100MHz | BW= 200MHz | BW= 400MHz |
+|----------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|--------------------|------------|------------|
+|                                                                                                    |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |                    |            |            |
+| 32x4 MU-MIMO, 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1) | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 9                                | 1                 | 9.61               | 11.03      | /          |
+|                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3                              |                   | 0.51               | 0.58       | /          |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE)<br>gNB Config = (16,8,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1) | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 9                                | 1                 | 10.41              | 12.17      | /          |
+|                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3                              |                   | 0.31               | 0.36       | /          |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1)  | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 9                                | 1                 | 12.77              | 14.27      | 14.97      |
+|                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3                              |                   | 0.45               | 0.5        | 0.53       |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE)<br>gNB Config = (4,4,2,1,1;4,4)<br>UE Config = (2,4,2,1,2; 1,1)  | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 9                                | 1                 | 12.63              | 14.11      | /          |
+|                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3                              |                   | 0.44               | 0.50       | /          |
+| 8x4 MU-MIMO, 4T SRS (2 panel@UE)<br>gNB Config = (8,16,2,1,1;2,2)<br>UE Config = (2,4,2,1,2; 1,1)  | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 9                                | 1                 | 9.98               | 11.12      | 11.56      |
+|                                                                                                    |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.3                              |                   | 0.35               | 0.39       | 0.40       |
+
+The evaluation results of UL spectral efficiency for NR for evaluation configuration C with 12TRxP are provided in Table B.6.1-2. The sub-carrier spacing of 60 kHz and 120 kHz are employed.
+
+**Table B.6.1-2 UL spectral efficiency for NR in Indoor Hotspot – eMBB (Evaluation configuration C, CF=70 GHz, for 12TRxP)**
+
+#### (a) NR TDD
+
+| Scheme and antenna configuration                                                                                       | Sub-carrier spacing (kHz) | Frame structure | ITU Requirement                  |                                  | Number of samples | BW= 80MHz |
+|------------------------------------------------------------------------------------------------------------------------|---------------------------|-----------------|----------------------------------|----------------------------------|-------------------|-----------|
+|                                                                                                                        |                           |                 | Average [bit/s/Hz/TRxP]          | 5 <sup>th</sup> -tile [bit/s/Hz] |                   |           |
+| 8x32 SU-MIMO, Codebook based, OFDMA (2 panel@UE);<br>gNB Config = (8,16,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)    | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 7.37      |
+|                                                                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.37      |
+| 4x32 MU-MIMO, Codebook based, OFDMA (2 panel@UE);<br>gNB Config = (16,8,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,1)    | 60                        | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 6.94      |
+|                                                                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.23      |
+| 4x8 MU-MIMO, Non-Codebook based, OFDMA (2 panel@UE);<br>gNB Config = (8,16,2,1,1;2,2);<br>UE Config = (2,4,2,1,2; 1,2) | 120                       | DDDSU           | Average [bit/s/Hz/TRxP]          | 6.75                             | 1                 | 6.85      |
+|                                                                                                                        |                           |                 | 5 <sup>th</sup> -tile [bit/s/Hz] | 0.21                             |                   | 0.31      |
+
+### B.6.2 Evaluation configuration C (CF = 70 GHz) for area traffic capacity
+
+The evaluation results of area traffic capacity for NR for evaluation configuration C with 12TRxP are provided in Table B.6.2-1. The sub-carrier spacing of 60 kHz and 120 kHz are employed.
+
+It is assumed that for TDD with 60 kHz SCS, a component carrier with 200 MHz is used; and for TDD with 120 kHz SCS, a component carrier with 400 MHz is used. Multiple component carriers are aggregated to achieve the target area traffic capacity. The assumed aggregated system bandwidth is given in Table B.6.2-1.
+
+**Table B.6.2-1 Area traffic capacity for NR in Indoor Hotspot – eMBB  
+(Evaluation configuration C, CF=70 GHz, for 12TRxP)**
+
+#### **(a) NR TDD**
+
+| Scheme and antenna configuration                                                                  | Sub-carrier spacing | Frame structure                   | ITU Requirement [Mbps/m <sup>2</sup> ] | Number of samples | Assumed system bandwidth [MHz] | Area traffic capacity [Mbps/m <sup>2</sup> ] |
+|---------------------------------------------------------------------------------------------------|---------------------|-----------------------------------|----------------------------------------|-------------------|--------------------------------|----------------------------------------------|
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2) | 60                  | DDDSU;<br>S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 600                            | 10.02                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (16,8,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2) | 60                  | DDDSU;<br>S Slot = (6DL:2GP:6UL)  | 10                                     | 1                 | 600                            | 10.23                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (4,4,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)  | 120                 | DDDSU;<br>S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 800                            | 18.14                                        |
+| 32x8 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (4,4,2,1,1;4,4);<br>UE Config = (2,4,2,1,2; 1,2)  | 60                  | DDDSU;<br>S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 600                            | 12.82                                        |
+| 8x4 MU-MIMO, 4T SRS (2 panel@UE), gNB Config = (8,16,2,1,1;2,2);<br>UE Config = (2,4,2,1,2; 1,1)  | 120                 | DDDSU;<br>S Slot = (10DL:2GP:2UL) | 10                                     | 1                 | 800                            | 14.00                                        |
+
+# --- Annex C: ITU-R Submission Templates for IMT-2020
+
+## --- C.1 Description template – characteristics
+
+The characteristics template can be found in the attached document "C.1\_CharacteristicsTemplate.zip".
+
+## --- C.2 Description template – link budget
+
+The link budget template can be found in the attached document "C.2\_LinkBudgetTemplate.zip".
+
+## --- C.3 Compliance templates for services, for spectrum, for technical performance
+
+The compliance template can be found in the attached document "C.3\_ComplianceTemplate.zip".
+
+# Annex D: Change history
+
+| Change history |         |           |    |     |     |                                                                                                                                                                         |  |             |
+|----------------|---------|-----------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------|
+| Date           | Meeting | TDoc      | CR | Rev | Cat | Subject/Comment                                                                                                                                                         |  | New version |
+| 2017-12        | RAN#78  | RP-172539 |    |     |     | Skeleton                                                                                                                                                                |  | 0.0.1       |
+| 2018-03        | RAN#79  | RP-180523 |    |     |     | Calibration results are included in Annex A.                                                                                                                            |  | 0.1.0       |
+| 2018-06        | RAN#80  | RP-181320 |    |     |     | Capture LTE CP latency evaluation results in Section 5.7.2; and capture evaluation models and assumptions for mobility in Annex B.                                      |  | 0.2.0       |
+| 2018-09        | RAN#81  | RP-182057 |    |     |     | Capture all agreed pCRs: RP-181803, RP-181807, RP-181808, RP-181813, RP-182024, RP-182026, RP-182027, RP-182028, RP-182029, RP-182054, RP-182055, RP-182056, RP-182096. |  | 0.3.0       |
+| 2018-09        | RAN#81  | RP-182102 |    |     |     | Accept revision marks of v0.3.0 and add editor's note in Clauses 8.3 and 9.                                                                                             |  | 1.0.0       |
+| 2018-12        | RAN#82  | RP-182786 |    |     |     | Capture agreed pCR RP-182540.                                                                                                                                           |  | 1.1.0       |
+| 2019-06        | RAN#84  | RP-191521 |    |     |     | Capture agreed pCR RP-191532.                                                                                                                                           |  | 2.0.0       |
+| 2019-06        | RAN #84 | -         |    |     |     | Approved by RAN #84 and put under CR control                                                                                                                            |  | 16.0.0      |
+| 2019-09        | RP-85   | RP-191749 |    |     |     | Editorial corrections to TR 37.910 Study on Self Evaluation towards IMT-2020 Submission                                                                                 |  | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37941/03d99823cac9b0c49db95d65dc155d8c_img.jpg b/marked/Rel-16/37_series/37941/03d99823cac9b0c49db95d65dc155d8c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f25b9896f3a4be19b79361cf3f589bfec91eb4a
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/03d99823cac9b0c49db95d65dc155d8c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40dd543b759d5987356aaa517576eb661eb0a69387cc978cbfddb721c56eab32
+size 16740
diff --git a/marked/Rel-16/37_series/37941/072320147c6e0a97ea1854ac62ddfe17_img.jpg b/marked/Rel-16/37_series/37941/072320147c6e0a97ea1854ac62ddfe17_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56ee7639f66d218feee7cb707b10005b190114ed
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/072320147c6e0a97ea1854ac62ddfe17_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ceb3a31e3a0d0f07ee45de4e556c5564acc1f0f9d43dd2dc58f92082889539c
+size 23362
diff --git a/marked/Rel-16/37_series/37941/090f012618e458eb073599905057ad26_img.jpg b/marked/Rel-16/37_series/37941/090f012618e458eb073599905057ad26_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d90f6c380f40d67f8805c8b4e5c68526ea6aac0
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/090f012618e458eb073599905057ad26_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4bf64462bf2a0cbc52fee5ee3bcdb32aec2d04bec180ba861802ecf224ddda98
+size 38699
diff --git a/marked/Rel-16/37_series/37941/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/37_series/37941/0931f3e098bd4539041de11c50cec2d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc9a876e23830cb0cc987d5fe11bc14e5426496a
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/0931f3e098bd4539041de11c50cec2d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ee41f4a66c9b2c2cc8362b78382f8148fc3eb70264763b36d14057b676b7ce2
+size 47506
diff --git a/marked/Rel-16/37_series/37941/11b4377bcba1c43b30732e5bb511ad5d_img.jpg b/marked/Rel-16/37_series/37941/11b4377bcba1c43b30732e5bb511ad5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5a4c3f32c9ba4463c86fec751fb184d8a9648d0b
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/11b4377bcba1c43b30732e5bb511ad5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dbfad0bb60bfc5e97b68fd5b2a5e3c20fb46eb882e7216ba409df22f389ca20
+size 51211
diff --git a/marked/Rel-16/37_series/37941/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/Rel-16/37_series/37941/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18877049e5c0bcca878786d6c1890265605df1fa
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7df698451967b5dade3fbac021f80c8d47542a26b867a551a29e6d754fa1b462
+size 54911
diff --git a/marked/Rel-16/37_series/37941/1cbfab01055f9367de73383e84fa29ad_img.jpg b/marked/Rel-16/37_series/37941/1cbfab01055f9367de73383e84fa29ad_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e09ad7d68d32d63fbfbc5bf9cfc570095a9b000
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/1cbfab01055f9367de73383e84fa29ad_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ba8ed9e6e38ca0b98fb55f7000d0958114419d04fadbf62d07aa640fda09b85
+size 44908
diff --git a/marked/Rel-16/37_series/37941/201de44da5d99899a8cf58eac2fa7bc9_img.jpg b/marked/Rel-16/37_series/37941/201de44da5d99899a8cf58eac2fa7bc9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed88b79a5d4e0b11008727077c2c18fc26e0f492
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/201de44da5d99899a8cf58eac2fa7bc9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:149f6774c0e470b2fb4cddc240b4752b77711e60038cc5be1859e7a80fe500ca
+size 58167
diff --git a/marked/Rel-16/37_series/37941/25cd06273405d5bc76c751e20d62e61d_img.jpg b/marked/Rel-16/37_series/37941/25cd06273405d5bc76c751e20d62e61d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c9cfa1cbf6eaba9dfcce0d0f85bb0334e12e982
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/25cd06273405d5bc76c751e20d62e61d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc3fce7da1a4446050db49697df05a02867761bf521d66416cf142719947fcc5
+size 27059
diff --git a/marked/Rel-16/37_series/37941/2a9813fa664df211b1f5a894fa406bd8_img.jpg b/marked/Rel-16/37_series/37941/2a9813fa664df211b1f5a894fa406bd8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..23b9bf75ac8e5370331d5088fd7d677ffd8f674e
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/2a9813fa664df211b1f5a894fa406bd8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d0399b47401dd6d6455beddc4962cb6dd0714827c2a7c56d47f974fdc293cac4
+size 27214
diff --git a/marked/Rel-16/37_series/37941/2aff6ef70a6f528e5eaeb4c94fd664fe_img.jpg b/marked/Rel-16/37_series/37941/2aff6ef70a6f528e5eaeb4c94fd664fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b80a135cc92e54e3329bce09a894f071e743a5ca
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/2aff6ef70a6f528e5eaeb4c94fd664fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:413663b9720ee645fe7f63476669a2da482e4d82264c88bb19e8fb0e855fafbd
+size 68836
diff --git a/marked/Rel-16/37_series/37941/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg b/marked/Rel-16/37_series/37941/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9e4e7445abc147161eb28f0b15014f42b86169e7
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/2d62ff2bded0c21414a0f40fdf8fd537_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c7c8715516b2f2df3a5bcdb5c6d64f0115fecfa1d76414d1d9d8b864dc0cd5a
+size 43720
diff --git a/marked/Rel-16/37_series/37941/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/37_series/37941/2f587210e4f97c32758c5972e2e83d20_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..392588aa808c42e4ab844bb07974966da842f032
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/2f587210e4f97c32758c5972e2e83d20_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5e4d9c9f9074089266694e78f50dd195c617d19882fac62cf7014b865ec9e426
+size 76298
diff --git a/marked/Rel-16/37_series/37941/30387053b5b3fede6873f6a46a9ca4a9_img.jpg b/marked/Rel-16/37_series/37941/30387053b5b3fede6873f6a46a9ca4a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4aae181803acf14d2ff24f5801e7a7a404619983
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/30387053b5b3fede6873f6a46a9ca4a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba750c6793da335ef9792177d7a94a2db526f49edca2fb6e3cebbf24e3cf0f22
+size 64400
diff --git a/marked/Rel-16/37_series/37941/30a26f2d17ca95672702bf50fb4f0242_img.jpg b/marked/Rel-16/37_series/37941/30a26f2d17ca95672702bf50fb4f0242_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7636689cbc7c61cb4992c5966c11516f99354859
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/30a26f2d17ca95672702bf50fb4f0242_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:feb08ff1aa0575dd021348ff58ec48ba6e335c3fa6a5517193b76c4e739f2e3e
+size 5663
diff --git a/marked/Rel-16/37_series/37941/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/37_series/37941/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf7013730b926f484f0d6cbf958cc416594050eb
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e1b9183ad0542a1379074b9c38f1ea21dfdfa12009a0a7f2d239d79ff151c359
+size 103044
diff --git a/marked/Rel-16/37_series/37941/3252037b597c9317aced0feed4cb5af0_img.jpg b/marked/Rel-16/37_series/37941/3252037b597c9317aced0feed4cb5af0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..982b4612424e940a129dcff6a9865dab03a98b11
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3252037b597c9317aced0feed4cb5af0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1ed19ada4f2b45aa9c910aeed536a6baf9ab168106eef65abd7e4251bfa506b3
+size 59502
diff --git a/marked/Rel-16/37_series/37941/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-16/37_series/37941/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15503d77064bc48342b29416aaddb6e85579cc2d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:820cbc36ffe76e3a41f1a758b150ca85123c555e7ca7a611669c3390522cc8f6
+size 70423
diff --git a/marked/Rel-16/37_series/37941/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-16/37_series/37941/3c04b14104f95eb8f7100f6d497d956e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5ce982aee80c2fc84943bd5803230063d76c87a6
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3c04b14104f95eb8f7100f6d497d956e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0dbd917fe28fc4019c6d4677d3a1f27564323d572761a3c66d27d426b87c93f7
+size 81868
diff --git a/marked/Rel-16/37_series/37941/3c65409bf428d5233f0443c2437c5b40_img.jpg b/marked/Rel-16/37_series/37941/3c65409bf428d5233f0443c2437c5b40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5cb988f953beabacf3c37f201bf529f6c92ea780
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3c65409bf428d5233f0443c2437c5b40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd5d6bd3565cf68513a67412fed4c2d251b1cc73605d99b307231486b2aeda1d
+size 79849
diff --git a/marked/Rel-16/37_series/37941/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg b/marked/Rel-16/37_series/37941/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67eb4397e02dffbd6c101fcea608c2f3523d546e
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4390374a2c90cc579883ff7c568212f7ed1e1971b17a18c4d4a539e9aaee4e63
+size 38881
diff --git a/marked/Rel-16/37_series/37941/3ea2a1f3b801526c45a1a02c3f983822_img.jpg b/marked/Rel-16/37_series/37941/3ea2a1f3b801526c45a1a02c3f983822_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fefabdaafc253a19fbb159038935d7002fad64ae
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/3ea2a1f3b801526c45a1a02c3f983822_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fbcad48d490756af9e54caa128b2ff254becb69f98e08d3898411662aabc7d0
+size 59406
diff --git a/marked/Rel-16/37_series/37941/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/Rel-16/37_series/37941/4537891530c9f6f139a2e1ebf544edc4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8bf7c82b7b488738860f50e3de5d2c882afc9ff0
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/4537891530c9f6f139a2e1ebf544edc4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c8a6d8a9182ec450a00e54cf4201a1232085424444b89efe7e17753b92793d3
+size 28278
diff --git a/marked/Rel-16/37_series/37941/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/37_series/37941/4b398c5e8c4fd656d5b7a61806400650_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..459557797be7f51d2a2a6d842c20df590b36d4b8
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/4b398c5e8c4fd656d5b7a61806400650_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c6909dbe2398123b6e2957dcf6da109be34ca9ed8a57a540e3c3c57dccf6d32
+size 54421
diff --git a/marked/Rel-16/37_series/37941/4d7310dc5ead3bcc30852c99ab09c31f_img.jpg b/marked/Rel-16/37_series/37941/4d7310dc5ead3bcc30852c99ab09c31f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a29d9556c9aed6eacbcda11e028c22815b7aec8f
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/4d7310dc5ead3bcc30852c99ab09c31f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:baa878ec2e6153993cef00c9a8506f73f7af816db603047b1147fc073c9988ba
+size 27303
diff --git a/marked/Rel-16/37_series/37941/513b2f88e0edcd2ffb6b7cf54f465d06_img.jpg b/marked/Rel-16/37_series/37941/513b2f88e0edcd2ffb6b7cf54f465d06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34971699af8ed2dde07df738834382953400236f
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/513b2f88e0edcd2ffb6b7cf54f465d06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe6301356ddd37f05113086c1855bea407b83f2eb490be4e6affbc72b74271e1
+size 20224
diff --git a/marked/Rel-16/37_series/37941/51517948c9faff8158db2bd2d6927606_img.jpg b/marked/Rel-16/37_series/37941/51517948c9faff8158db2bd2d6927606_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f72b76ede90e8205003fd6da0e02e1d67fa12e96
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/51517948c9faff8158db2bd2d6927606_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1438baa314f5f9b7d8dbcf9b399894aaaa88b939066377f2be1e07ff4ac3eea1
+size 42918
diff --git a/marked/Rel-16/37_series/37941/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/37_series/37941/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0925b537843978e0a443c6de44ff8b108cfa258
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/56a5265d174ce056c1dbe5e7a60839fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d55aa25b701f352316039dc4c4efaab9e63deed9c800c6748a8eea0eb7b2321
+size 88412
diff --git a/marked/Rel-16/37_series/37941/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/37_series/37941/575d7d345b3ec04393bb2ec720ebabca_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ee8ed72b1e08b82689029edb7d5c0b1cdc0b0b1
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/575d7d345b3ec04393bb2ec720ebabca_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e159e749152d8949667fe573dc736f9a2c70103ca8ad55c393e34199fb789181
+size 71017
diff --git a/marked/Rel-16/37_series/37941/5a2d10b858b621236f708a5f5fa1ed88_img.jpg b/marked/Rel-16/37_series/37941/5a2d10b858b621236f708a5f5fa1ed88_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dea6158760785b51b72e275b235e9c319e39f1d8
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/5a2d10b858b621236f708a5f5fa1ed88_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:123375e4c3980974d2c5f9d76abcfb053e901b896ac422c5277f27d1fc9cc8d0
+size 17568
diff --git a/marked/Rel-16/37_series/37941/5b87d9e3f7fbaeceb1bc31ae4d7c95b0_img.jpg b/marked/Rel-16/37_series/37941/5b87d9e3f7fbaeceb1bc31ae4d7c95b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b214c023450e8b5ac27f04094190b8650dfcd66b
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/5b87d9e3f7fbaeceb1bc31ae4d7c95b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3be1f4c57f33698e7d7e27bdb878f7c49770f5de5884eaa36913330eaeedd23
+size 52626
diff --git a/marked/Rel-16/37_series/37941/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg b/marked/Rel-16/37_series/37941/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f25882cf456f14e7954164c12e03a0cc98ce9c09
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/5e16d3613b74558acc74ff6d7fd75fa9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa58ecc4647691f8e39584bba4e04680905484d259a1fa5887d428ae6b2b0d64
+size 24526
diff --git a/marked/Rel-16/37_series/37941/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/37_series/37941/5e9af8986a5845504f251d3079da8078_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3992c88479dc1aa40ce982636e7e869b9a800bf2
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/5e9af8986a5845504f251d3079da8078_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8bd3635b5b81e0dba7ed80f8c8f8e54401579b53679b673698a7516c5462186
+size 50886
diff --git a/marked/Rel-16/37_series/37941/6031b46d356ee24f96bfe37ee2cb7616_img.jpg b/marked/Rel-16/37_series/37941/6031b46d356ee24f96bfe37ee2cb7616_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d758269eef3e5e95e8545ad5f9dca5d63cf8c5c0
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/6031b46d356ee24f96bfe37ee2cb7616_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:957943c08579df3106cc20cb38f0f5c766d60b2ea0a9e0daffc0a404b5f96835
+size 88004
diff --git a/marked/Rel-16/37_series/37941/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37941/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2bab9c2de59d4dc114f9691f9c407e1e92013f4a
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ff5c544e81e007e37f8163af288b0d7365b4f668839f4944803d41939b281929
+size 9593
diff --git a/marked/Rel-16/37_series/37941/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/marked/Rel-16/37_series/37941/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab704fc84be31c2b7aaa1189cb2de094e0c08338
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:235c89cf9248b1018e56a2468e631a6d04f3589a6597ad0c0052cfa3d2994090
+size 89029
diff --git a/marked/Rel-16/37_series/37941/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/37_series/37941/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3abf6b0ea2a8546136bf380d309fd3f778befb3c
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9d9868c9c695dc2c330e72f00f217acdf8ed127d31d0f5b073f1c6fcd9f1f0f
+size 58988
diff --git a/marked/Rel-16/37_series/37941/6707cae4df136f92a0c9f3a4676f91a6_img.jpg b/marked/Rel-16/37_series/37941/6707cae4df136f92a0c9f3a4676f91a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5198c3868730028ddb29458feb8444717ccb87f7
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/6707cae4df136f92a0c9f3a4676f91a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:adf5150030b5558385983b316e44be940e69c5773c81c1d887ddd343199f0102
+size 65047
diff --git a/marked/Rel-16/37_series/37941/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/37_series/37941/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8b3f53aaf4b2657cfeefc768d86b5f2d611af08
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1de9d26be89d40f06c66866e6d7e61750ec755fee094cfa78f5887fe090c408
+size 91264
diff --git a/marked/Rel-16/37_series/37941/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/37_series/37941/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f1cfe172c2988a15aa76ecde772d876cd9dee25
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/694df81535f89c7bfb9ef0df6f130dc0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3d9d98842ee9c5a96a5b2db5265df36940b3c82b8cf37f48cbd60380d096c65b
+size 80253
diff --git a/marked/Rel-16/37_series/37941/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg b/marked/Rel-16/37_series/37941/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5f52fbb43846092254f0369a515d45913457717
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:77db54e7b278540790ff4971683a61a4292012f5fe41bc98346a994c9520fd3f
+size 50880
diff --git a/marked/Rel-16/37_series/37941/6dd6f798e257cfeca7aef8c304f321f5_img.jpg b/marked/Rel-16/37_series/37941/6dd6f798e257cfeca7aef8c304f321f5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cd7d11f592490f1a502feefbbc26d49d3415fc0c
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/6dd6f798e257cfeca7aef8c304f321f5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2c941b28d98cada91e86e641b7a945eb5617fd5133b96e6ea9908f218d29a26
+size 26407
diff --git a/marked/Rel-16/37_series/37941/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/37_series/37941/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6270cf139bad585f42ceeaf42b57c28282e0a697
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d52ab667f608183a5ac6ecf274daf6358162e948e735961749b22fd385c6e56
+size 164732
diff --git a/marked/Rel-16/37_series/37941/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/37_series/37941/719ef0f734259484038b2434e5dc3f24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6934674ca6d6a49f5155c25d9658db1b5de9777
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/719ef0f734259484038b2434e5dc3f24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10d4fe0eb018a10e74685a330bb189c51b99e3ed176fe2884248de875bf861db
+size 101764
diff --git a/marked/Rel-16/37_series/37941/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-16/37_series/37941/74d23510f27b21403a7be84820821863_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..21bcd4738988385cb81a5e41eba084a3f8e3fded
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/74d23510f27b21403a7be84820821863_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fc9c4313bf1ec5c5de7d669a60586a782247b8338d5464cc17b9e353a269e4fa
+size 53277
diff --git a/marked/Rel-16/37_series/37941/75b9cb95f5815d6f3bbe57020a049504_img.jpg b/marked/Rel-16/37_series/37941/75b9cb95f5815d6f3bbe57020a049504_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..985753d3b060ea373c3770d3a9e9c35cc74e9b82
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/75b9cb95f5815d6f3bbe57020a049504_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8c7c8ba4951d462d2a8bfd2f598ba45b74260c26ecfa2f337fb006ba5d40ffb
+size 57922
diff --git a/marked/Rel-16/37_series/37941/77a781dfb114c3e2b399f876f1808cfd_img.jpg b/marked/Rel-16/37_series/37941/77a781dfb114c3e2b399f876f1808cfd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7f89a74c42e586ce8816a5551a3e8163de1c0601
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/77a781dfb114c3e2b399f876f1808cfd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6dc53a50ba68bb2d15879b487ab7a9ad284f4ccb8ee08b55082d38cf534f21a1
+size 131056
diff --git a/marked/Rel-16/37_series/37941/77dcb3b9312f3e14215a4890634391e5_img.jpg b/marked/Rel-16/37_series/37941/77dcb3b9312f3e14215a4890634391e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1986ba6b5d7a54d7486e8736f35e77156cc91a7f
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/77dcb3b9312f3e14215a4890634391e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0088d07dea8201ad10ab91b691d36b724dec64717fceda0e2712d83809c4d7d5
+size 55218
diff --git a/marked/Rel-16/37_series/37941/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/37_series/37941/848073118eebfdbfdb9a60e3923fe0b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5224bf3e6a63e3982ac97461e6e14c6ef1ee7fda
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/848073118eebfdbfdb9a60e3923fe0b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dcbd17af8473395e4d83e9eea0d6d0f5d3d1ec206571d14ab69a48cc5a19c596
+size 72124
diff --git a/marked/Rel-16/37_series/37941/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/37_series/37941/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..399bf37e411f5d212e1376a0bf917d73dd0c1faf
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e8f91e638451a4aa7758eaa2f1084c72a1c5402867f0f37fef5d51727e27cfc6
+size 38756
diff --git a/marked/Rel-16/37_series/37941/8d5d12ba8fe7313bc891241275c64d20_img.jpg b/marked/Rel-16/37_series/37941/8d5d12ba8fe7313bc891241275c64d20_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2f1667b6ddea93ede4088320ee356ad5bb6508a7
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/8d5d12ba8fe7313bc891241275c64d20_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1614571c35da1b9d5ddaca12a9b010a1c7806264049cf42e25d0c0b36870c30e
+size 29511
diff --git a/marked/Rel-16/37_series/37941/8f931bb1d65d0ee4ccafab751ee61282_img.jpg b/marked/Rel-16/37_series/37941/8f931bb1d65d0ee4ccafab751ee61282_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..eebf17ce79ab068f43482bb49ceeb38853313e75
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/8f931bb1d65d0ee4ccafab751ee61282_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4da979ad7b07d68d6a7495fd13de428106bcd421abebc498e389077bb751a71d
+size 13983
diff --git a/marked/Rel-16/37_series/37941/8faebfce2615b355cc3aefe58b2e17fc_img.jpg b/marked/Rel-16/37_series/37941/8faebfce2615b355cc3aefe58b2e17fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..18fdfadd2798038e3aabea54691b1a8b8ceed787
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/8faebfce2615b355cc3aefe58b2e17fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:470f3d5751d00ef28efd5f631be451f3d0c7b2a68a5a677930571b89b8b33fd6
+size 44595
diff --git a/marked/Rel-16/37_series/37941/91134b9a38d7f73f03375473e7b706f9_img.jpg b/marked/Rel-16/37_series/37941/91134b9a38d7f73f03375473e7b706f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a3b50c8f977d85039f009a5dd6f26de88a16a52d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/91134b9a38d7f73f03375473e7b706f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af98a5c9d9ac8815c54c6a36a235ab41e2ee233186d63db5aa48482d26263063
+size 74128
diff --git a/marked/Rel-16/37_series/37941/94389c644d3c25d99db7bc6d87bf5779_img.jpg b/marked/Rel-16/37_series/37941/94389c644d3c25d99db7bc6d87bf5779_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f61503f934518fe4279251fb66913c94a2bae2f0
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/94389c644d3c25d99db7bc6d87bf5779_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a0b1e9231841c520fe6628b536d3843f2a0fc4898843e3fad13a28658b953cb5
+size 57999
diff --git a/marked/Rel-16/37_series/37941/967e98a12645f89cb4a7620f42bf8c2e_img.jpg b/marked/Rel-16/37_series/37941/967e98a12645f89cb4a7620f42bf8c2e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0055532ffbbc7f963580229d92a23d6ff470bd64
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/967e98a12645f89cb4a7620f42bf8c2e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0f850e2beb2491103590c08124d3ffc486a54164f62c053d349aad6ee5b4ef53
+size 50895
diff --git a/marked/Rel-16/37_series/37941/9975977c05cf557391d09ea21a0c2263_img.jpg b/marked/Rel-16/37_series/37941/9975977c05cf557391d09ea21a0c2263_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3fb3c57de63c920474aa5ee3c01ada2a935c0ae7
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/9975977c05cf557391d09ea21a0c2263_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9918ee0c386e8c3e867d970808d48fdc9edca8eff09fa0c8ece2468a5ea2be2
+size 54531
diff --git a/marked/Rel-16/37_series/37941/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/37_series/37941/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..049a1f3c1a7f3db420f23f89e95332cf2c9c5c55
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/9e8ebf03cae78f4f81b697548c2d7250_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a7a8b3ab71fec12961ec63b508ac9b113635a28c8a68cfee03ab81c916c03b6
+size 28318
diff --git a/marked/Rel-16/37_series/37941/9f92854fe6ecaf47760515c891a4fccc_img.jpg b/marked/Rel-16/37_series/37941/9f92854fe6ecaf47760515c891a4fccc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08ce44c3d35aee60fa5f5be3ba56bc8db2a07120
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/9f92854fe6ecaf47760515c891a4fccc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0e7a6adb8acd3c06ce6affb2a3bf3f20f6a7558aa040d69df14e694ba0298977
+size 40114
diff --git a/marked/Rel-16/37_series/37941/a0cbe8f8ff7d008d81ed3e82b60c8865_img.jpg b/marked/Rel-16/37_series/37941/a0cbe8f8ff7d008d81ed3e82b60c8865_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..318b60d447d35cf13461e01ca83c472e019e28ce
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/a0cbe8f8ff7d008d81ed3e82b60c8865_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e6ed3def9d25bf818fd55e9b449252cd5f4306fe85569887d22ec6e78a733da0
+size 46962
diff --git a/marked/Rel-16/37_series/37941/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/37_series/37941/a47713c2491e6ce619259ed2f196fd24_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6111486970137e9014e5ad4461f1ec5ee39af1e2
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/a47713c2491e6ce619259ed2f196fd24_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e498a30ef8980ebdcfa6e79dd5b193aa00c17f5180e13da0ec1cb4827154e9f
+size 105428
diff --git a/marked/Rel-16/37_series/37941/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-16/37_series/37941/a4bfa2343d75076b79f7e33d93915e00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7519dfc18281cd205c78d2cae2ebc0dd0ae46837
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/a4bfa2343d75076b79f7e33d93915e00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ffa2351678d67a586245b082aebe985b8dd104d08ae9dd5bb229fcee0223666
+size 80266
diff --git a/marked/Rel-16/37_series/37941/a83b94d3c7b86ae870ab0ea3bd48d0ec_img.jpg b/marked/Rel-16/37_series/37941/a83b94d3c7b86ae870ab0ea3bd48d0ec_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5529e392974452ebdc0afe0781fd87f6c7509287
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/a83b94d3c7b86ae870ab0ea3bd48d0ec_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:435f129e0823cfeeac7a41d141b5063f9af85450a03dfb1295b62aea4f6a8e4f
+size 20254
diff --git a/marked/Rel-16/37_series/37941/a9159a006d67a834a7b1a771c18191cc_img.jpg b/marked/Rel-16/37_series/37941/a9159a006d67a834a7b1a771c18191cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c3315e783196cc3e2dcfc4d34e18c79e098f217d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/a9159a006d67a834a7b1a771c18191cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:444b1e4548d6431eb1ec1419b451fbbfb3db26b78c0c009b7d09fd1ae0859a83
+size 70782
diff --git a/marked/Rel-16/37_series/37941/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/37_series/37941/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1673f185e280713f2db76d26e020ab84c8027ba
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e0d6591409c8d130991e27bcaa6bc0f0106f7615a72f70f6b702f17880984e5f
+size 72963
diff --git a/marked/Rel-16/37_series/37941/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-16/37_series/37941/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..146a66d4c4a09151a4ae3867d1a6f0281dfefe24
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:49041a8701d38c4be616f709e1d85c029234fa2fdbdb883cd011249ce15edf1a
+size 51240
diff --git a/marked/Rel-16/37_series/37941/b723a64dd970a1cb5a08ce1e88ac7921_img.jpg b/marked/Rel-16/37_series/37941/b723a64dd970a1cb5a08ce1e88ac7921_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e69bd16227eec9f4ff5e4f62c34b95f7f705a860
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/b723a64dd970a1cb5a08ce1e88ac7921_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bd796dd1c0271e98923b45afeb553338d224889b8fb6e80cb360eef96276213
+size 36986
diff --git a/marked/Rel-16/37_series/37941/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg b/marked/Rel-16/37_series/37941/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e09d5ee23493bde8fec08c87c4b7b372affd9017
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2d51d1a6fa14d272c9e47afc9c64c2b73fcc21276aac623ff22494ad03c5abdf
+size 33027
diff --git a/marked/Rel-16/37_series/37941/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/37_series/37941/c07e21a8d65991db04263322f859c94f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..780c36efd91fa8032a4c0500a6629d73cf552e5d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/c07e21a8d65991db04263322f859c94f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bcc4491e5411aae37966ffc537dc3f3544edd38764e875527ccd00b28aece3c4
+size 84214
diff --git a/marked/Rel-16/37_series/37941/c0f64806753a053854921deb8f4fc798_img.jpg b/marked/Rel-16/37_series/37941/c0f64806753a053854921deb8f4fc798_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41858deb850eb979fc45012616e5665eeb29b76d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/c0f64806753a053854921deb8f4fc798_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:81d18c84776bfb927d2301b7190bb32f75362459214055f852e0c0723910574a
+size 80216
diff --git a/marked/Rel-16/37_series/37941/c301bbb71a13e5fb2800c48e300bafb1_img.jpg b/marked/Rel-16/37_series/37941/c301bbb71a13e5fb2800c48e300bafb1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de2cfc2a941745d6728ff822e92626aa53fcab1d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/c301bbb71a13e5fb2800c48e300bafb1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2b631018afe7c3eb90f9f8c70b4c709b5ebf79607465aaa566facca73b6678d
+size 42783
diff --git a/marked/Rel-16/37_series/37941/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-16/37_series/37941/cc542843836eecb036b99cb270b54a1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..599e5e24461d3ca35098ea2f1fc2e9fa9c921781
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/cc542843836eecb036b99cb270b54a1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a30ef556e17d5f7940f295688d0459794447aae89ab573a925c3d80bf893df9d
+size 71557
diff --git a/marked/Rel-16/37_series/37941/cdce40d544a867b676500c480efd5886_img.jpg b/marked/Rel-16/37_series/37941/cdce40d544a867b676500c480efd5886_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f79b256cf136d3e0f376194b18095adc6f485239
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/cdce40d544a867b676500c480efd5886_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:915dff9c08ababa39e27611e70f409acda5d5cc0aaa15d97f9057ed298e8dca4
+size 1769
diff --git a/marked/Rel-16/37_series/37941/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg b/marked/Rel-16/37_series/37941/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c824ff1640a58920ca04ec2b60220dec21042993
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb1e662d0a92e424d21648f868722be4d8a961330e881e9f700edcdb3bb1e87c
+size 19012
diff --git a/marked/Rel-16/37_series/37941/d6198648f031082e94008fb2734fda40_img.jpg b/marked/Rel-16/37_series/37941/d6198648f031082e94008fb2734fda40_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d85386166130ba27ed6ceecc6b5ae5a079a3496c
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/d6198648f031082e94008fb2734fda40_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0aba253d43364cefd2e352b0c2b88981ec4f136ef7526b8bef0224e7ba83ad51
+size 72556
diff --git a/marked/Rel-16/37_series/37941/d94a0100320109c1b9cd75c1054c7b95_img.jpg b/marked/Rel-16/37_series/37941/d94a0100320109c1b9cd75c1054c7b95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..808b9b69da731a8fbc937994eb9972fd0020447c
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/d94a0100320109c1b9cd75c1054c7b95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db3d75d37672c484919519fdadd52ebbf32ab9b6a12ed90657a89adcbbc8bd38
+size 80632
diff --git a/marked/Rel-16/37_series/37941/db2f2503931949e0258f7f10eba14eb5_img.jpg b/marked/Rel-16/37_series/37941/db2f2503931949e0258f7f10eba14eb5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f88a8d3a5af619fd563135bc6df057f84aa2c2b5
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/db2f2503931949e0258f7f10eba14eb5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:79e53d269f57d0b4bb5a861f2f4c452cf56577d23b85c44e936fcdef3149bf73
+size 18877
diff --git a/marked/Rel-16/37_series/37941/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/37_series/37941/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fc59d67cda7e3c53bcc48315db89f86f686abc1
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfdc46d353df8c8311e3ce555727761d3a751ed2822407b5a82a07a7d052a9f2
+size 53040
diff --git a/marked/Rel-16/37_series/37941/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg b/marked/Rel-16/37_series/37941/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6853a17e088431445dc822b8ac0035d16f7d2770
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a90dbfe3a73ab9c5141a309a3e8c20e0e38ebdd9ddf4dbb6d0ed2d5b90126f3
+size 47057
diff --git a/marked/Rel-16/37_series/37941/e4d74b50fc10b0f0a08cb2db56123cb9_img.jpg b/marked/Rel-16/37_series/37941/e4d74b50fc10b0f0a08cb2db56123cb9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6cbaff62e1a37434b4c4dc01259cc729415b4b2c
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/e4d74b50fc10b0f0a08cb2db56123cb9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41cfb48435e8f603b2e155a55d5fe38cb77ddd39c1f4b707740d6b0440d5168d
+size 64661
diff --git a/marked/Rel-16/37_series/37941/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg b/marked/Rel-16/37_series/37941/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd3868ea8458c3e59a7ed918ecb0c581c630e402
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:865748befa2b43fb73250420d336d4ac8efb6daa1bb41a4abd09e1e719812544
+size 16323
diff --git a/marked/Rel-16/37_series/37941/e77f9abb052e12e90a8480b9e1e4b571_img.jpg b/marked/Rel-16/37_series/37941/e77f9abb052e12e90a8480b9e1e4b571_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ab9be8910d4a6bb0c00d23dfc4c5061f1a1e2af
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/e77f9abb052e12e90a8480b9e1e4b571_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42488220f06d5930bf1fb51c04fd4b2051737850528f72be8eaf397e22ceda51
+size 143600
diff --git a/marked/Rel-16/37_series/37941/ebd9c6a5314c2d747d9326192468e9cf_img.jpg b/marked/Rel-16/37_series/37941/ebd9c6a5314c2d747d9326192468e9cf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08e32b46672c8c28ada7bde6faaf76c2f258593d
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/ebd9c6a5314c2d747d9326192468e9cf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:674e62b43db7871dbdd44e6450a8c4cea77ade09257f9b6170a0dc21ce3f0e0a
+size 28719
diff --git a/marked/Rel-16/37_series/37941/eed9c8ade8af628fdab5135da476beb7_img.jpg b/marked/Rel-16/37_series/37941/eed9c8ade8af628fdab5135da476beb7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d0357e07d53fbd546b37652020ba1ba07f372b9
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/eed9c8ade8af628fdab5135da476beb7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45b09df9d503c77c1e343d7b20d9878704cc5381c1eb501d105ad296d5c062f3
+size 24928
diff --git a/marked/Rel-16/37_series/37941/ef436853d3483f70254ae5fe1335a28b_img.jpg b/marked/Rel-16/37_series/37941/ef436853d3483f70254ae5fe1335a28b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a10b2506b33e68f165d7235a96d729d0535e0b84
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/ef436853d3483f70254ae5fe1335a28b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32775ddf68fb67ad4ae206370188148b0acd938e7bdd4e3a99f85642421d32b9
+size 27189
diff --git a/marked/Rel-16/37_series/37941/f2e97817636949186cf689a4b532b8a9_img.jpg b/marked/Rel-16/37_series/37941/f2e97817636949186cf689a4b532b8a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..505fd97e5422d4d6f4d025d1b9195261ec92b834
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/f2e97817636949186cf689a4b532b8a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:af87aa8cbaf7380003674e0578e9580c8d52cc659b166b96570fa4d01a6257d6
+size 42567
diff --git a/marked/Rel-16/37_series/37941/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-16/37_series/37941/f468e577645d646f5157ce3eefb4ed96_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..69ea12e96c92aacb05c60cff3ee3e879986a9c8e
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/f468e577645d646f5157ce3eefb4ed96_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33d8e6687217c59be387b9fbf25549cbea717e616994950a5cb9bb6080952049
+size 49790
diff --git a/marked/Rel-16/37_series/37941/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-16/37_series/37941/f97535cdaa4fe017f4659512f4f78028_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70d58a804a0c3bc0715aa3131210d2114e98113b
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/f97535cdaa4fe017f4659512f4f78028_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:212b21567b74296514da369180eaf02b51e74b86d77253878f84d5fa77d8ee5f
+size 72880
diff --git a/marked/Rel-16/37_series/37941/fc77cd5fb91dcf10116215d46da18a00_img.jpg b/marked/Rel-16/37_series/37941/fc77cd5fb91dcf10116215d46da18a00_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..10d08d4f7a186b9b923f125425ac6d519cbd7aec
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/fc77cd5fb91dcf10116215d46da18a00_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e117ec61af39b06430ebcbdfeaa9b3db9267c3d05e2bde8aac5fd162aa43d23a
+size 15375
diff --git a/marked/Rel-16/37_series/37941/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/37_series/37941/fcc757566216206ceddbd6c775e8db02_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c31a51604dfd49a279c2ca3bc62be4a7036372fb
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/fcc757566216206ceddbd6c775e8db02_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0bbeb288c90e17fd32a2f93705e0c6ce8a95345beec83e9ad7dc1b69c56f13fa
+size 66912
diff --git a/marked/Rel-16/37_series/37941/fd8369b549b3d1a5c848cbd83659cae9_img.jpg b/marked/Rel-16/37_series/37941/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc04eb1f7de03d13b7345f70055aca6c50a7136f
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/fd8369b549b3d1a5c848cbd83659cae9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bff8c15c045f91002286e47b90d3f7746b65cd05140c238699894899c83591a6
+size 48675
diff --git a/marked/Rel-16/37_series/37941/raw.md b/marked/Rel-16/37_series/37941/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..fea14c8282665238f80dc53f045a039107621fb2
--- /dev/null
+++ b/marked/Rel-16/37_series/37941/raw.md
@@ -0,0 +1,11035 @@
+
+
+# 3GPP TR 37.941 V16.6.0 (2023-09) ---
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Frequency (RF) conformance testing background for radiated Base Station (BS) requirements (Release 16)**
+
+![5G logo](30a26f2d17ca95672702bf50fb4f0242_img.jpg)
+
+---
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is the tagline "A GLOBAL INITIATIVE" in a smaller, all-caps, sans-serif font. There is a small red signal icon below the "3G" part of the logo.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2023, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
+
+# Contents
+
+|                                                                              |    |
+|------------------------------------------------------------------------------|----|
+| Foreword.....                                                                | 29 |
+| 1 Scope.....                                                                 | 31 |
+| 2 References.....                                                            | 32 |
+| 3 Definitions of terms, symbols and abbreviations.....                       | 33 |
+| 3.1 Terms.....                                                               | 33 |
+| 3.2 Symbols.....                                                             | 35 |
+| 3.3 Abbreviations.....                                                       | 36 |
+| 4 Coordinate system.....                                                     | 37 |
+| 5 Conformance testing aspects.....                                           | 41 |
+| 5.1 Conformance testing framework.....                                       | 41 |
+| 5.2 Uncertainty budget calculation principles.....                           | 42 |
+| 6 Measurement types.....                                                     | 44 |
+| 6.1 Spatial definitions.....                                                 | 44 |
+| 6.2 Directional measurements.....                                            | 44 |
+| 6.2.1 General.....                                                           | 44 |
+| 6.2.2 Beam parameter definitions.....                                        | 44 |
+| 6.2.3 OSDD.....                                                              | 46 |
+| 6.3 TRP measurement.....                                                     | 47 |
+| 6.3.1 General.....                                                           | 47 |
+| 6.3.2 TRP measurement procedures.....                                        | 49 |
+| 6.3.2.1 General.....                                                         | 49 |
+| 6.3.2.2 Procedures for BS output power.....                                  | 50 |
+| 6.3.2.2.1 General.....                                                       | 50 |
+| 6.3.2.2.2 Two cuts with pattern multiplication.....                          | 50 |
+| 6.3.2.2.3 Full sphere.....                                                   | 50 |
+| 6.3.2.2.4 Beam-based directions.....                                         | 50 |
+| 6.3.2.3 Procedures for SEM and OBUE.....                                     | 50 |
+| 6.3.2.3.1 General.....                                                       | 50 |
+| 6.3.2.3.2 Two cuts with pattern multiplication.....                          | 51 |
+| 6.3.2.3.3 Two or three cuts.....                                             | 51 |
+| 6.3.2.3.4 Full sphere.....                                                   | 51 |
+| 6.3.2.3.5 Beam-based directions.....                                         | 51 |
+| 6.3.2.4 Procedures for ACLR.....                                             | 51 |
+| 6.3.2.4.1 General.....                                                       | 51 |
+| 6.3.2.4.2 TRP fraction method.....                                           | 51 |
+| 6.3.2.5 Procedures for transmitter spurious emissions and EMC emissions..... | 52 |
+| 6.3.2.5.1 General.....                                                       | 52 |
+| 6.3.2.5.2 Pre-scan.....                                                      | 52 |
+| 6.3.2.5.3 Peak method.....                                                   | 52 |
+| 6.3.2.5.4 Equal sector with peak average method.....                         | 53 |
+| 6.3.2.5.5 Two or three cuts with dense sampling.....                         | 53 |
+| 6.3.2.5.6 Full sphere with sparse sampling.....                              | 53 |
+| 6.3.2.5.7 Full sphere.....                                                   | 54 |
+| 6.3.3 Angular alignment in TRP measurements.....                             | 54 |
+| 6.3.4 TRP measurement grids.....                                             | 56 |
+| 6.3.4.1 Spherical equal angle grid.....                                      | 56 |
+| 6.3.4.2 Reference angular step criteria.....                                 | 57 |
+| 6.3.4.3 Spherical equal area grids.....                                      | 61 |
+| 6.3.4.4 Spherical Fibonacci grids.....                                       | 62 |
+| 6.3.4.5 Orthogonal cuts grids.....                                           | 63 |
+| 6.3.4.6 Wave vector space sampling grid.....                                 | 65 |
+| 6.3.5 Aspects related to measurement of OTA unwanted emission.....           | 68 |
+| 6.3.5.1 Test range.....                                                      | 68 |
+| 6.3.5.2 Measurement distance.....                                            | 69 |
+
+|           |                                                                    |     |
+|-----------|--------------------------------------------------------------------|-----|
+| 6.3.5.3   | Sampling grid selection.....                                       | 69  |
+| 6.3.6     | TRP summation error.....                                           | 69  |
+| 6.4       | Co-location measurements.....                                      | 70  |
+| 6.4.1     | General.....                                                       | 70  |
+| 6.4.2     | Co-location test antenna.....                                      | 71  |
+| 6.4.3     | Standard test antenna.....                                         | 71  |
+| 6.5       | Requirements classification.....                                   | 71  |
+| 7         | OTA measurement systems.....                                       | 73  |
+| 7.1       | General.....                                                       | 73  |
+| 7.2       | Indoor Anechoic Chamber.....                                       | 73  |
+| 7.2.1     | Measurement system description, Normal test conditions.....        | 73  |
+| 7.2.2     | Measurement system description, Extreme test conditions.....       | 77  |
+| 7.2.3     | Test method limitations.....                                       | 77  |
+| 7.3       | Compact Antenna Test Range.....                                    | 77  |
+| 7.3.1     | Measurement system description, Normal test conditions.....        | 77  |
+| 7.3.2     | Measurement system description, Extreme test conditions.....       | 80  |
+| 7.3.3     | Test method limitations.....                                       | 81  |
+| 7.4       | One Dimensional Compact Range.....                                 | 81  |
+| 7.4.1     | Measurement system description.....                                | 81  |
+| 7.4.2     | Test method limitations.....                                       | 82  |
+| 7.5       | Near Field Test Range.....                                         | 83  |
+| 7.5.1     | Measurement system description.....                                | 83  |
+| 7.5.2     | Test method limitations.....                                       | 83  |
+| 7.5.2.1   | OTA EVM measurement.....                                           | 83  |
+| 7.5.2.2   | OTA RX directional requirements.....                               | 83  |
+| 7.5.2.3   | OTA sensitivity measurement.....                                   | 83  |
+| 7.6       | Plane Wave Synthesizer.....                                        | 84  |
+| 7.6.1     | Measurement system description.....                                | 84  |
+| 7.6.2     | Test method limitations.....                                       | 86  |
+| 7.7       | General Chamber.....                                               | 86  |
+| 7.7.0     | General.....                                                       | 86  |
+| 7.7.1     | Measurement system description (co-location requirements).....     | 86  |
+| 7.7.2     | Test method limitations (co-location requirements).....            | 88  |
+| 7.7.3     | Measurement system description (out-of-band TRP requirements)..... | 88  |
+| 7.7.4     | Test method limitations (out-of-band TRP requirements).....        | 88  |
+| 7.8       | Reverberation chamber.....                                         | 88  |
+| 7.8.1     | Measurement system description.....                                | 88  |
+| 7.8.2     | Test method limitations.....                                       | 91  |
+| 8         | Measurement system calibration.....                                | 91  |
+| 8.1       | General.....                                                       | 91  |
+| 8.2       | Indoor Anechoic Chamber calibration.....                           | 91  |
+| 8.3       | Compact Antenna Test Range calibration.....                        | 93  |
+| 8.4       | One Dimensional Test Range calibration.....                        | 96  |
+| 8.5       | Near Field Test Range calibration.....                             | 96  |
+| 8.6       | Plane Wave Synthesizer calibration.....                            | 96  |
+| 8.7       | General Chamber calibration (co-location requirements).....        | 97  |
+| 8.7A      | General Chamber calibration (out-of-band TRP requirements).....    | 99  |
+| 8.8       | Reverberation chamber calibration.....                             | 99  |
+| 9         | TX directional requirements.....                                   | 100 |
+| 9.1       | General.....                                                       | 100 |
+| 9.2       | EIRP accuracy, Normal test conditions.....                         | 101 |
+| 9.2.1     | General.....                                                       | 101 |
+| 9.2.2     | Indoor Anechoic Chamber.....                                       | 101 |
+| 9.2.2.1   | Measurement system description.....                                | 101 |
+| 9.2.2.2   | Test procedure.....                                                | 101 |
+| 9.2.2.2.1 | Stage 1: Calibration.....                                          | 101 |
+| 9.2.2.2.2 | Stage 2: BS measurement.....                                       | 101 |
+| 9.2.2.3   | MU value derivation, FR1.....                                      | 102 |
+| 9.2.3     | Compact Antenna Test Range.....                                    | 105 |
+| 9.2.3.1   | Measurement system description.....                                | 105 |
+
+|           |                                                                |     |
+|-----------|----------------------------------------------------------------|-----|
+| 9.2.3.2   | Test procedure.....                                            | 105 |
+| 9.2.3.2.1 | Stage 1: Calibration.....                                      | 105 |
+| 9.2.3.2.2 | Stage 2: BS measurement.....                                   | 105 |
+| 9.2.3.3   | MU value derivation, FR1.....                                  | 105 |
+| 9.2.3.4   | MU value derivation, FR2.....                                  | 106 |
+| 9.2.4     | One Dimensional Compact Range.....                             | 108 |
+| 9.2.4.1   | Measurement system description.....                            | 108 |
+| 9.2.4.2   | Test procedure.....                                            | 108 |
+| 9.2.4.2.1 | Stage 1: Calibration.....                                      | 108 |
+| 9.2.4.2.2 | Stage 2: BS measurement.....                                   | 109 |
+| 9.2.4.3   | MU value derivation, FR1.....                                  | 109 |
+| 9.2.5     | Near Field Test Range.....                                     | 112 |
+| 9.2.5.1   | Measurement system description.....                            | 112 |
+| 9.2.5.2   | Test procedure.....                                            | 112 |
+| 9.2.5.2.1 | Stage 1: Calibration.....                                      | 112 |
+| 9.2.5.2.2 | Stage 2: BS measurement.....                                   | 112 |
+| 9.2.5.3   | MU value derivation, FR1.....                                  | 112 |
+| 9.2.6     | Plane Wave Synthesizer.....                                    | 114 |
+| 9.2.6.1   | Measurement system description.....                            | 114 |
+| 9.2.6.2   | Test procedure.....                                            | 115 |
+| 9.2.6.2.1 | Stage 1: Calibration.....                                      | 115 |
+| 9.2.6.2.2 | Stage 2: BS measurement.....                                   | 115 |
+| 9.2.6.3   | MU value derivation, FR1.....                                  | 115 |
+| 9.2.7     | Maximum accepted test system uncertainty.....                  | 116 |
+| 9.2.8     | Test Tolerance for EIRP accuracy, Normal test conditions.....  | 117 |
+| 9.3       | EIRP accuracy, Extreme test conditions.....                    | 118 |
+| 9.3.1     | General.....                                                   | 118 |
+| 9.3.2     | Indoor Anechoic Chamber.....                                   | 118 |
+| 9.3.2.1   | Measurement system description.....                            | 118 |
+| 9.3.2.2   | Test procedure.....                                            | 118 |
+| 9.3.2.2.1 | Stage 1: Calibration.....                                      | 118 |
+| 9.3.2.2.2 | Stage 2: BS measurement.....                                   | 118 |
+| 9.3.2.3   | MU value derivation, FR1.....                                  | 119 |
+| 9.3.3     | Compact Antenna Test Range.....                                | 121 |
+| 9.3.3.1   | Measurement system description.....                            | 121 |
+| 9.3.3.2   | Test procedure.....                                            | 121 |
+| 9.3.3.2.1 | Stage 1: Calibration.....                                      | 121 |
+| 9.3.3.2.2 | Stage 2: BS measurement.....                                   | 121 |
+| 9.3.3.3   | MU value derivation, FR1.....                                  | 122 |
+| 9.3.3.4   | MU value derivation, FR2.....                                  | 123 |
+| 9.3.4     | Maximum accepted test system uncertainty.....                  | 123 |
+| 9.3.5     | Test Tolerance for EIRP accuracy, Extreme test conditions..... | 124 |
+| 9.4       | OTA E-UTRA DL RS power.....                                    | 125 |
+| 9.4.1     | General.....                                                   | 125 |
+| 9.4.2     | Indoor Anechoic Chamber.....                                   | 125 |
+| 9.4.2.1   | Measurement system description.....                            | 125 |
+| 9.4.2.2   | Test procedure.....                                            | 125 |
+| 9.4.2.2.1 | Stage 1: Calibration.....                                      | 125 |
+| 9.4.2.2.2 | Stage 2: BS measurement.....                                   | 125 |
+| 9.4.2.3   | MU value derivation, FR1.....                                  | 126 |
+| 9.4.3     | Compact Antenna Test Range.....                                | 129 |
+| 9.4.3.1   | Measurement system description.....                            | 129 |
+| 9.4.3.2   | Test procedure.....                                            | 129 |
+| 9.4.3.2.1 | Stage 1: Calibration.....                                      | 129 |
+| 9.4.3.2.2 | Stage 2: BS measurement.....                                   | 129 |
+| 9.4.3.3   | MU value derivation, FR1.....                                  | 129 |
+| 9.4.4     | Near Field Test Range.....                                     | 130 |
+| 9.4.4.1   | Measurement system description.....                            | 130 |
+| 9.4.4.2   | Test procedure.....                                            | 131 |
+| 9.4.4.2.1 | Stage 1: Calibration.....                                      | 131 |
+| 9.4.4.2.2 | Stage 2: BS measurement.....                                   | 131 |
+
+|           |                                                 |     |
+|-----------|-------------------------------------------------|-----|
+| 9.4.4.3   | MU value derivation, FR1                        | 132 |
+| 9.4.5     | Plane Wave Synthesizer                          | 133 |
+| 9.4.5.1   | Measurement system description                  | 133 |
+| 9.4.5.2   | Test procedure                                  | 133 |
+| 9.4.5.2.1 | Stage 1: Calibration                            | 133 |
+| 9.4.5.2.2 | Stage 2: BS measurement                         | 133 |
+| 9.4.5.3   | MU value derivation, FR1                        | 133 |
+| 9.4.6     | Maximum accepted test system uncertainty        | 136 |
+| 9.4.7     | Test Tolerance for OTA E-UTRA DL RS power       | 136 |
+| 9.5       | OTA output power dynamics                       | 136 |
+| 9.5.1     | General                                         | 136 |
+| 9.5.2     | Indoor Anechoic Chamber                         | 137 |
+| 9.5.2.1   | Measurement system description                  | 137 |
+| 9.5.2.2   | Test procedure                                  | 137 |
+| 9.5.2.2.1 | Stage 1: Calibration                            | 137 |
+| 9.5.2.2.2 | Stage 2: BS measurement                         | 137 |
+| 9.5.2.3   | MU value derivation, FR1                        | 137 |
+| 9.5.3     | Compact Antenna Test Range                      | 138 |
+| 9.5.3.1   | Measurement system description                  | 138 |
+| 9.5.3.2   | Test procedure                                  | 138 |
+| 9.5.3.2.1 | Stage 1: Calibration                            | 138 |
+| 9.5.3.2.2 | Stage 2: BS measurement                         | 138 |
+| 9.5.3.3   | MU value derivation, FR1                        | 139 |
+| 9.5.4     | Near Field Test Range                           | 140 |
+| 9.5.4.1   | Measurement system description                  | 140 |
+| 9.5.4.2   | Test procedure                                  | 140 |
+| 9.5.4.2.1 | Stage 1: Calibration                            | 140 |
+| 9.5.4.2.2 | Stage 2: BS measurement                         | 140 |
+| 9.5.4.3   | MU value derivation, FR1                        | 140 |
+| 9.5.5     | Plane Wave Synthesizer                          | 140 |
+| 9.5.5.1   | Measurement system description                  | 140 |
+| 9.5.5.2   | Test procedure                                  | 140 |
+| 9.5.5.2.1 | Stage 1: Calibration                            | 140 |
+| 9.5.5.2.2 | Stage 2: BS measurement                         | 141 |
+| 9.5.5.3   | MU value derivation, FR1                        | 141 |
+| 9.5.6     | Maximum accepted test system uncertainty        | 141 |
+| 9.5.7     | Test Tolerance for OTA output power dynamics    | 143 |
+| 9.6       | OTA transmitted signal quality: Frequency error | 144 |
+| 9.6.1     | General                                         | 144 |
+| 9.6.2     | Indoor Anechoic Chamber                         | 144 |
+| 9.6.2.1   | Measurement system description                  | 144 |
+| 9.6.2.2   | Test procedure                                  | 144 |
+| 9.6.2.2.1 | Stage 1: Calibration                            | 144 |
+| 9.6.2.2.2 | Stage 2: BS measurement                         | 144 |
+| 9.6.2.3   | MU value derivation                             | 145 |
+| 9.6.3     | Compact Antenna Test Range                      | 145 |
+| 9.6.3.1   | Measurement system description                  | 145 |
+| 9.6.3.2   | Test procedure                                  | 145 |
+| 9.6.3.2.1 | Stage 1: Calibration                            | 145 |
+| 9.6.3.2.2 | Stage 2: BS measurement                         | 145 |
+| 9.6.3.3   | MU value derivation                             | 145 |
+| 9.6.4     | Near Field Test Range                           | 145 |
+| 9.6.4.1   | Measurement system description                  | 145 |
+| 9.6.4.2   | Test procedure                                  | 146 |
+| 9.6.4.2.1 | Stage 1: Calibration                            | 146 |
+| 9.6.4.2.2 | Stage 2: BS measurement                         | 146 |
+| 9.6.4.3   | MU value derivation                             | 146 |
+| 9.6.5     | Plane Wave Synthesizer                          | 146 |
+| 9.6.5.1   | Measurement system description                  | 146 |
+| 9.6.5.2   | Test procedure                                  | 146 |
+| 9.6.5.2.1 | Stage 1: Calibration                            | 146 |
+
+|            |                                               |     |
+|------------|-----------------------------------------------|-----|
+| 9.6.5.2.2  | Stage 2: BS measurement.....                  | 146 |
+| 9.6.5.3    | MU value derivation.....                      | 147 |
+| 9.6.6      | Maximum accepted test system uncertainty..... | 147 |
+| 9.6.7      | Test Tolerance for frequency error.....       | 147 |
+| 9.7        | OTA transmitted signal quality: EVM.....      | 148 |
+| 9.7.1      | General.....                                  | 148 |
+| 9.7.2      | Indoor Anechoic Chamber.....                  | 148 |
+| 9.7.2.1    | Measurement system description.....           | 148 |
+| 9.7.2.2    | Test procedure.....                           | 148 |
+| 9.7.2.2.1  | Stage 1: Calibration.....                     | 148 |
+| 9.7.2.2.2  | Stage 2: BS measurement.....                  | 148 |
+| 9.7.2.3    | MU value derivation, FR1.....                 | 149 |
+| 9.7.3      | Compact Antenna Test Range.....               | 150 |
+| 9.7.3.1    | Measurement system description.....           | 150 |
+| 9.7.3.2    | Test procedure.....                           | 150 |
+| 9.7.3.2.1  | Stage 1: Calibration.....                     | 150 |
+| 9.7.3.2.2  | Stage 2: BS measurement.....                  | 150 |
+| 9.7.3.3    | MU value derivation, FR1.....                 | 150 |
+| 9.7.4      | Near Field Test Range.....                    | 151 |
+| 9.7.4.1    | Measurement system description.....           | 151 |
+| 9.7.4.2    | Test procedure.....                           | 151 |
+| 9.7.4.2.1  | Stage 1: Calibration.....                     | 151 |
+| 9.7.4.2.2  | Stage 2: BS measurement.....                  | 151 |
+| 9.7.4.3    | MU value derivation, FR1.....                 | 152 |
+| 9.7.5      | Plane Wave Synthesizer.....                   | 152 |
+| 9.7.5.1    | Measurement system description.....           | 152 |
+| 9.7.5.2    | Test procedure.....                           | 152 |
+| 9.7.5.2.1  | Stage 1: Calibration.....                     | 152 |
+| 9.7.5.2.2  | Stage 2: BS measurement.....                  | 153 |
+| 9.7.5.3    | MU value derivation, FR1.....                 | 153 |
+| 9.7.6      | Maximum accepted test system uncertainty..... | 154 |
+| 9.7.7      | Test Tolerance for EVM.....                   | 154 |
+| 9.8        | OTA transmitted signal quality: TAE.....      | 155 |
+| 9.8.1      | General.....                                  | 155 |
+| 9.8.2      | Indoor Anechoic Chamber.....                  | 155 |
+| 9.8.2.1    | Measurement system description.....           | 155 |
+| 9.8.2.2    | Test procedure.....                           | 156 |
+| 9.8.2.2.1  | Stage 1: Calibration.....                     | 156 |
+| 9.8.2.2.2  | Stage 2: BS measurement.....                  | 156 |
+| 9.8.2.3    | MU value derivation.....                      | 156 |
+| 9.8.3      | Compact Antenna Test Range.....               | 156 |
+| 9.8.3.1    | Measurement system description.....           | 156 |
+| 9.8.3.2    | Test procedure.....                           | 156 |
+| 9.8.3.2.1  | Stage 1: Calibration.....                     | 156 |
+| 9.8.3.2.2  | Stage 2: BS measurement.....                  | 156 |
+| 9.8.3.3    | MU value derivation.....                      | 157 |
+| 9.8.4      | Near Field Test Range.....                    | 157 |
+| 9.8.4.1    | Measurement system description.....           | 157 |
+| 9.8.4.2    | Test procedure.....                           | 157 |
+| 9.8.4.2.1  | Stage 1: Calibration.....                     | 157 |
+| 9.8.4.2.2  | Stage 2: BS measurement.....                  | 157 |
+| 9.8.4.3    | MU value derivation.....                      | 157 |
+| 9.8.4A     | Plane Wave Synthesizer.....                   | 157 |
+| 9.8.4A.1   | Measurement system description.....           | 157 |
+| 9.8.4A.2   | Test procedure.....                           | 158 |
+| 9.8.4A.2.1 | Stage 1: Calibration.....                     | 158 |
+| 9.8.4A.2.2 | Stage 2: BS measurement.....                  | 158 |
+| 9.8.4A.3   | MU value derivation.....                      | 158 |
+| 9.8.5      | Maximum accepted test system uncertainty..... | 158 |
+| 9.8.6      | Test Tolerance for TAE.....                   | 159 |
+| 9.9        | OTA occupied bandwidth.....                   | 159 |
+
+|            |                                                                           |     |
+|------------|---------------------------------------------------------------------------|-----|
+| 9.9.1      | General.....                                                              | 159 |
+| 9.9.2      | Indoor Anechoic Chamber.....                                              | 160 |
+| 9.9.2.1    | Measurement system description.....                                       | 160 |
+| 9.9.2.2    | Test procedure.....                                                       | 160 |
+| 9.9.2.2.1  | Stage 1: Calibration.....                                                 | 160 |
+| 9.9.2.2.2  | Stage 2: BS measurement.....                                              | 160 |
+| 9.9.2.3    | MU value derivation.....                                                  | 160 |
+| 9.9.3      | Compact Antenna Test Range.....                                           | 160 |
+| 9.9.3.1    | Measurement system description.....                                       | 160 |
+| 9.9.3.2    | Test procedure.....                                                       | 160 |
+| 9.9.3.2.1  | Stage 1: Calibration.....                                                 | 160 |
+| 9.9.3.2.2  | Stage 2: BS measurement.....                                              | 160 |
+| 9.9.3.3    | MU value derivation.....                                                  | 161 |
+| 9.9.4      | Near Field Test Range.....                                                | 161 |
+| 9.9.4.1    | Measurement system description.....                                       | 161 |
+| 9.9.4.2    | Test procedure.....                                                       | 161 |
+| 9.9.4.2.1  | Stage 1: Calibration.....                                                 | 161 |
+| 9.9.4.2.2  | Stage 2: BS measurement.....                                              | 161 |
+| 9.9.4.3    | MU value derivation.....                                                  | 161 |
+| 9.9.5      | Plane Wave Synthesizer.....                                               | 161 |
+| 9.9.5.1    | Measurement system description.....                                       | 161 |
+| 9.9.5.2    | Test procedure.....                                                       | 161 |
+| 9.9.5.2.1  | Stage 1: Calibration.....                                                 | 161 |
+| 9.9.5.2.2  | Stage 2: BS measurement.....                                              | 162 |
+| 9.9.5.3    | MU value derivation.....                                                  | 162 |
+| 9.9.6      | Maximum accepted test system uncertainty.....                             | 162 |
+| 9.9.7      | Test Tolerance for OTA occupied bandwidth.....                            | 162 |
+| 9.10       | OTA TX OFF power and transmitter transient period.....                    | 163 |
+| 9.10.1     | General.....                                                              | 163 |
+| 9.10.2     | Compact Antenna Test Range.....                                           | 163 |
+| 9.10.2.1   | Measurement system description.....                                       | 163 |
+| 9.10.2.2   | Test procedure.....                                                       | 163 |
+| 9.10.2.2.1 | Stage 1: Calibration.....                                                 | 163 |
+| 9.10.2.2.2 | Stage 2: BS measurement.....                                              | 163 |
+| 9.10.2.3   | MU value derivation, FR2.....                                             | 163 |
+| 9.10.3     | Maximum accepted test system uncertainty.....                             | 164 |
+| 9.10.4     | Test Tolerance for OTA TX OFF power and transmitter transient period..... | 165 |
+| 10         | RX directional requirements.....                                          | 165 |
+| 10.1       | General.....                                                              | 165 |
+| 10.2       | OTA sensitivity.....                                                      | 166 |
+| 10.2.1     | General.....                                                              | 166 |
+| 10.2.2     | Indoor Anechoic Chamber.....                                              | 166 |
+| 10.2.2.1   | Measurement system description.....                                       | 166 |
+| 10.2.2.2   | Test procedure.....                                                       | 166 |
+| 10.2.2.2.1 | Stage 1: Calibration.....                                                 | 166 |
+| 10.2.2.2.2 | Stage 2: BS measurement.....                                              | 166 |
+| 10.2.2.3   | MU value derivation, FR1.....                                             | 166 |
+| 10.2.2.4   | MU value derivation, FR2.....                                             | 169 |
+| 10.2.3     | Compact Antenna Test Range.....                                           | 172 |
+| 10.2.3.1   | Measurement system description.....                                       | 172 |
+| 10.2.3.2   | Test procedure.....                                                       | 172 |
+| 10.2.3.2.1 | Stage 1: Calibration.....                                                 | 172 |
+| 10.2.3.2.2 | Stage 2: BS measurement.....                                              | 172 |
+| 10.2.3.3   | MU value derivation, FR1.....                                             | 172 |
+| 10.2.3.4   | MU value derivation, FR2.....                                             | 173 |
+| 10.2.4     | One Dimensional Compact Range.....                                        | 174 |
+| 10.2.4.1   | Measurement system description.....                                       | 174 |
+| 10.2.4.2   | Test procedure.....                                                       | 174 |
+| 10.2.4.2.1 | Stage 1: Calibration.....                                                 | 174 |
+| 10.2.4.2.2 | Stage 2: BS measurement.....                                              | 174 |
+| 10.2.4.3   | MU value derivation, FR1.....                                             | 175 |
+
+|             |                                                                                 |     |
+|-------------|---------------------------------------------------------------------------------|-----|
+| 10.2.5      | Near Field Test range.....                                                      | 177 |
+| 10.2.5.1    | Measurement system description.....                                             | 177 |
+| 10.2.5.2    | Test procedure.....                                                             | 177 |
+| 10.2.5.2.1  | Stage 1: Calibration.....                                                       | 177 |
+| 10.2.5.2.2  | Stage 2: BS measurement.....                                                    | 177 |
+| 10.2.5.3    | MU value derivation, FR1.....                                                   | 178 |
+| 10.2.6      | Plane Wave Synthesizer.....                                                     | 181 |
+| 10.2.6.1    | Measurement system description.....                                             | 181 |
+| 10.2.6.2    | Test procedure.....                                                             | 181 |
+| 10.2.6.2.1  | Stage 1: Calibration.....                                                       | 181 |
+| 10.2.6.2.2  | Stage 2: BS measurement.....                                                    | 181 |
+| 10.2.6.3    | MU value derivation, FR1.....                                                   | 181 |
+| 10.2.7      | Maximum accepted test system uncertainty.....                                   | 183 |
+| 10.2.8      | Test Tolerance for OTA sensitivity.....                                         | 183 |
+| 10.3        | OTA reference sensitivity.....                                                  | 184 |
+| 10.4        | OTA dynamic range.....                                                          | 184 |
+| 10.4.1      | General.....                                                                    | 184 |
+| 10.4.2      | Indoor Anechoic Chamber.....                                                    | 184 |
+| 10.4.2.1    | Measurement system description.....                                             | 184 |
+| 10.4.2.2    | Test procedure.....                                                             | 184 |
+| 10.4.2.2.1  | Stage 1: Calibration.....                                                       | 184 |
+| 10.4.2.2.2  | Stage 2: BS measurement.....                                                    | 184 |
+| 10.4.2.3    | MU value derivation, FR1.....                                                   | 185 |
+| 10.4.3      | Compact Antenna Test Range.....                                                 | 185 |
+| 10.4.3.1    | Measurement system description.....                                             | 185 |
+| 10.4.3.2    | Test procedure.....                                                             | 185 |
+| 10.4.3.2.1  | Stage 1: Calibration.....                                                       | 185 |
+| 10.4.3.2.2  | Stage 2: BS measurement.....                                                    | 185 |
+| 10.4.3.3    | MU value derivation, FR1.....                                                   | 185 |
+| 10.4.3A     | Plane Wave Synthesizer.....                                                     | 185 |
+| 10.4.3A.2   | Test procedure.....                                                             | 185 |
+| 10.4.3A.2.1 | Stage 1: Calibration.....                                                       | 185 |
+| 10.4.3A.2.2 | Stage 2: BS measurement.....                                                    | 186 |
+| 10.4.3A.3   | MU value derivation, FR1.....                                                   | 186 |
+| 10.4.4      | Maximum accepted test system uncertainty.....                                   | 186 |
+| 10.4.5      | Test Tolerance for OTA dynamic range.....                                       | 186 |
+| 10.5        | OTA adjacent channel selectivity, general blocking and narrowband blocking..... | 186 |
+| 10.5.1      | General.....                                                                    | 186 |
+| 10.5.2      | Indoor Anechoic Chamber.....                                                    | 187 |
+| 10.5.2.1    | Measurement system description.....                                             | 187 |
+| 10.5.2.2    | Test procedure.....                                                             | 187 |
+| 10.5.2.2.1  | Stage 1: Calibration.....                                                       | 187 |
+| 10.5.2.2.2  | Stage 2: BS measurement.....                                                    | 187 |
+| 10.5.2.3    | MU value derivation, FR1.....                                                   | 187 |
+| 10.5.3      | Compact Antenna Test Range.....                                                 | 188 |
+| 10.5.3.1    | Measurement system description.....                                             | 188 |
+| 10.5.3.2    | Test procedure.....                                                             | 188 |
+| 10.5.3.2.1  | Stage 1: Calibration.....                                                       | 188 |
+| 10.5.3.2.2  | Stage 2: BS measurement.....                                                    | 189 |
+| 10.5.3.3    | MU value derivation, FR1.....                                                   | 189 |
+| 10.5.3A     | Plane Wave Synthesizer.....                                                     | 190 |
+| 10.5.3A.1   | Measurement system description.....                                             | 190 |
+| 10.5.3A.2   | Test procedure.....                                                             | 190 |
+| 10.5.3A.2.1 | Stage 1: Calibration.....                                                       | 190 |
+| 10.5.3A.2.2 | Stage 2: BS measurement.....                                                    | 190 |
+| 10.5.3A.3   | MU value derivation, FR1.....                                                   | 191 |
+| 10.5.4      | Maximum accepted test system uncertainty.....                                   | 191 |
+| 10.5.5      | Test Tolerance for OTA ACS, general blocking and narrowband blocking.....       | 193 |
+| 10.6        | OTA receiver intermodulation.....                                               | 193 |
+| 10.6.1      | General.....                                                                    | 193 |
+| 10.6.2      | Indoor Anechoic Chamber.....                                                    | 193 |
+
+|             |                                               |     |
+|-------------|-----------------------------------------------|-----|
+| 10.6.2.1    | Measurement system description.....           | 193 |
+| 10.6.2.2    | Test procedure.....                           | 193 |
+| 10.6.2.2.1  | Stage 1: Calibration.....                     | 193 |
+| 10.6.2.2.2  | Stage 2: BS measurement.....                  | 193 |
+| 10.6.2.3    | MU value derivation, FR1.....                 | 194 |
+| 10.6.3      | Compact Antenna Test Range.....               | 195 |
+| 10.6.3.1    | Measurement system description.....           | 195 |
+| 10.6.3.2    | Test procedure.....                           | 195 |
+| 10.6.3.2.1  | Stage 1: Calibration.....                     | 195 |
+| 10.6.3.2.2  | Stage 2: BS measurement.....                  | 195 |
+| 10.6.3.3    | MU value derivation, FR1.....                 | 196 |
+| 10.6.3A     | Plan Wave Synthesizer.....                    | 197 |
+| 10.6.3A.1   | Measurement system description.....           | 197 |
+| 10.6.3A.2   | Test procedure.....                           | 197 |
+| 10.6.3A.2.1 | Stage 1: Calibration.....                     | 197 |
+| 10.6.3A.2.2 | Stage 2: BS measurement.....                  | 197 |
+| 10.6.3A.3   | MU value derivation, FR1.....                 | 198 |
+| 10.6.4      | Maximum accepted test system uncertainty..... | 199 |
+| 10.6.5      | Test Tolerance for OTA RX IMD.....            | 200 |
+| 10.7        | OTA in-channel selectivity.....               | 200 |
+| 10.7.1      | General.....                                  | 200 |
+| 10.7.2      | Indoor Anechoic Chamber.....                  | 201 |
+| 10.7.2.1    | Measurement system description.....           | 201 |
+| 10.7.2.2    | Test procedure.....                           | 201 |
+| 10.7.2.2.1  | Stage 1: Calibration.....                     | 201 |
+| 10.7.2.2.2  | Stage 2: BS measurement.....                  | 201 |
+| 10.7.2.3    | MU value derivation, FR1.....                 | 201 |
+| 10.7.3      | Compact Antenna Test Range.....               | 201 |
+| 10.7.3.1    | Measurement system description.....           | 201 |
+| 10.7.3.2    | Test procedure.....                           | 201 |
+| 10.7.3.2.1  | Stage 1: Calibration.....                     | 201 |
+| 10.7.3.2.2  | Stage 2: BS measurement.....                  | 201 |
+| 10.7.3.3    | MU value derivation, FR1.....                 | 202 |
+| 10.7.3A     | Plane Wave Synthesizer.....                   | 202 |
+| 10.7.3A.1   | Measurement system description.....           | 202 |
+| 10.7.3A.2   | Test procedure.....                           | 202 |
+| 10.7.3A.2.1 | Stage 1: Calibration.....                     | 202 |
+| 10.7.3A.2.2 | Stage 2: BS measurement.....                  | 202 |
+| 10.7.3A.3   | MU value derivation, FR1.....                 | 202 |
+| 10.7.4      | Maximum accepted test system uncertainty..... | 202 |
+| 10.7.5      | Test Tolerance for OTA ICS.....               | 202 |
+| 11          | In-band TRP requirements.....                 | 203 |
+| 11.1        | General.....                                  | 203 |
+| 11.2        | OTA BS output power.....                      | 203 |
+| 11.2.1      | General.....                                  | 203 |
+| 11.2.2      | Indoor Anechoic Chamber.....                  | 203 |
+| 11.2.2.1    | Measurement system description.....           | 203 |
+| 11.2.2.2    | Test procedure.....                           | 203 |
+| 11.2.2.2.1  | Stage 1: Calibration.....                     | 203 |
+| 11.2.2.2.2  | Stage 2: BS measurement.....                  | 203 |
+| 11.2.2.3    | MU value derivation, FR1.....                 | 204 |
+| 11.2.3      | Compact Antenna Test Range.....               | 205 |
+| 11.2.3.1    | Measurement system description.....           | 205 |
+| 11.2.3.2    | Test procedure.....                           | 205 |
+| 11.2.3.2.1  | Stage 1: Calibration.....                     | 205 |
+| 11.2.3.2.2  | Stage 2: BS measurement.....                  | 205 |
+| 11.2.3.3    | MU value derivation, FR1.....                 | 205 |
+| 11.2.3.4    | MU value derivation, FR2.....                 | 207 |
+| 11.2.4      | Near Field Test Range.....                    | 208 |
+| 11.2.4.1    | Measurement system description.....           | 208 |
+| 11.2.4.2    | Test procedure.....                           | 208 |
+
+|            |                                               |     |
+|------------|-----------------------------------------------|-----|
+| 11.2.4.2.1 | Stage 1: Calibration.....                     | 208 |
+| 11.2.4.2.2 | Stage 2: BS measurement.....                  | 208 |
+| 11.2.4.3   | MU value derivation, FR1.....                 | 208 |
+| 11.2.5     | Reverberation Chamber.....                    | 211 |
+| 11.2.5.1   | Measurement system description.....           | 211 |
+| 11.2.5.2   | Test procedure.....                           | 211 |
+| 11.2.5.2.1 | Stage 1: Calibration.....                     | 211 |
+| 11.2.5.2.2 | Stage 2: BS measurement.....                  | 211 |
+| 11.2.5.3   | MU value derivation, FR1.....                 | 212 |
+| 11.2.5.4   | MU value derivation, FR2.....                 | 212 |
+| 11.2.6     | Plane Wave Synthesizer.....                   | 213 |
+| 11.2.6.1   | Measurement system description.....           | 213 |
+| 11.2.6.2   | Test procedure.....                           | 213 |
+| 11.2.6.2.1 | Stage 1: Calibration.....                     | 213 |
+| 11.2.6.2.2 | Stage 2: BS measurement.....                  | 213 |
+| 11.2.6.3   | MU value derivation, FR1.....                 | 214 |
+| 11.2.7     | Maximum accepted test system uncertainty..... | 216 |
+| 11.2.8     | Test Tolerance for OTA BS output power.....   | 216 |
+| 11.3       | OTA ACLR.....                                 | 217 |
+| 11.3.1     | General.....                                  | 217 |
+| 11.3.2     | Indoor Anechoic Chamber.....                  | 217 |
+| 11.3.2.1   | Measurement system description.....           | 217 |
+| 11.3.2.2   | Test procedure.....                           | 217 |
+| 11.3.2.2.1 | Stage 1: Calibration.....                     | 217 |
+| 11.3.2.2.2 | Stage 2: BS measurement.....                  | 217 |
+| 11.3.2.3   | MU value derivation, FR1.....                 | 218 |
+| 11.3.3     | Compact Antenna Test Range.....               | 221 |
+| 11.3.3.1   | Measurement system description.....           | 221 |
+| 11.3.3.2   | Test procedure.....                           | 221 |
+| 11.3.3.2.1 | Stage 1: Calibration.....                     | 221 |
+| 11.3.3.2.2 | Stage 2: BS measurement.....                  | 221 |
+| 11.3.3.3   | MU value derivation, FR1.....                 | 221 |
+| 11.3.3.4   | MU value derivation, FR2.....                 | 223 |
+| 11.3.4     | Near Field Test Range.....                    | 225 |
+| 11.3.4.1   | Measurement system description.....           | 225 |
+| 11.3.4.2   | Test procedure.....                           | 225 |
+| 11.3.4.2.1 | Stage 1: Calibration.....                     | 225 |
+| 11.3.4.2.2 | Stage 2: BS measurement.....                  | 225 |
+| 11.3.4.3   | MU value derivation, FR1.....                 | 226 |
+| 11.3.5     | Reverberation Chamber.....                    | 228 |
+| 11.3.5.1   | Measurement system description.....           | 228 |
+| 11.3.5.2   | Test procedure.....                           | 228 |
+| 11.3.5.2.1 | Stage 1: Calibration.....                     | 228 |
+| 11.3.5.2.2 | Stage 2: BS measurement.....                  | 228 |
+| 11.3.5.3   | MU value derivation, FR1.....                 | 228 |
+| 11.3.5.4   | MU value derivation, FR2.....                 | 229 |
+| 11.3.6     | Plane Wave Synthesizer.....                   | 231 |
+| 11.3.6.1   | Measurement system description.....           | 231 |
+| 11.3.6.2   | Test procedure.....                           | 231 |
+| 11.3.6.2.1 | Stage 1: Calibration.....                     | 231 |
+| 11.3.6.2.2 | Stage 2: BS measurement.....                  | 231 |
+| 11.3.6.3   | MU value derivation, FR1.....                 | 232 |
+| 11.3.7     | Maximum accepted test system uncertainty..... | 235 |
+| 11.3.8     | Test Tolerance for OTA ACLR.....              | 236 |
+| 11.4       | OTA SEM and OTA OBUE.....                     | 237 |
+| 11.4.1     | General.....                                  | 237 |
+| 11.4.2     | Indoor Anechoic Chamber.....                  | 237 |
+| 11.4.2.1   | Measurement system description.....           | 237 |
+| 11.4.2.2   | Test procedure.....                           | 237 |
+| 11.4.2.2.1 | Stage 1: Calibration.....                     | 237 |
+| 11.4.2.2.2 | Stage 2: BS measurement.....                  | 237 |
+
+|            |                                              |     |
+|------------|----------------------------------------------|-----|
+| 11.4.2.3   | MU value derivation, FR1                     | 238 |
+| 11.4.3     | Compact Antenna Test Range                   | 241 |
+| 11.4.3.1   | Measurement system description               | 241 |
+| 11.4.3.2   | Test procedure                               | 241 |
+| 11.4.3.2.1 | Stage 1: Calibration                         | 241 |
+| 11.4.3.2.2 | Stage 2: BS measurement                      | 241 |
+| 11.4.3.3   | MU value derivation, FR1                     | 241 |
+| 11.4.3.4   | MU value derivation, FR2                     | 242 |
+| 11.4.4     | Near Field Test Range                        | 244 |
+| 11.4.4.1   | Measurement system description               | 244 |
+| 11.4.4.2   | Test procedure                               | 244 |
+| 11.4.4.2.1 | Stage 1: Calibration                         | 244 |
+| 11.4.4.2.2 | Stage 2: BS measurement                      | 244 |
+| 11.4.4.3   | MU value derivation, FR1                     | 244 |
+| 11.4.5     | Reverberation Chamber                        | 244 |
+| 11.4.5.1   | Measurement system description               | 244 |
+| 11.4.5.2   | Test procedure                               | 244 |
+| 11.4.5.2.1 | Stage 1: Calibration                         | 244 |
+| 11.4.5.2.2 | Stage 2: BS measurement                      | 244 |
+| 11.4.5.3   | MU value derivation, FR1                     | 244 |
+| 11.4.5.4   | MU value derivation, FR2                     | 245 |
+| 11.4.6     | Plane Wave Synthesizer                       | 246 |
+| 11.4.6.1   | Measurement system description               | 246 |
+| 11.4.6.2   | Test procedure                               | 246 |
+| 11.4.6.2.1 | Stage 1: Calibration                         | 246 |
+| 11.4.6.2.2 | Stage 2: BS measurement                      | 246 |
+| 11.4.6.3   | MU value derivation, FR1                     | 247 |
+| 11.4.7     | Maximum accepted test system uncertainty     | 247 |
+| 11.4.8     | Test Tolerance for OTA OBUE and OTA SEM      | 247 |
+| 12         | Out-of-band TRP requirements                 | 248 |
+| 12.1       | General                                      | 248 |
+| 12.2       | Transmitter mandatory spurious emissions     | 248 |
+| 12.2.1     | General                                      | 248 |
+| 12.2.2     | General Chamber                              | 249 |
+| 12.2.2.1   | Measurement system description               | 249 |
+| 12.2.2.2   | Test procedure                               | 249 |
+| 12.2.2.2.1 | Stage 1: Calibration                         | 249 |
+| 12.2.2.2.2 | Stage 2: BS measurement                      | 250 |
+| 12.2.2.3   | MU value derivation, FR1                     | 250 |
+| 12.2.2.4   | MU value derivation, FR2                     | 253 |
+| 12.2.3     | Compact Antenna Test Range                   | 255 |
+| 12.2.3.1   | Measurement system description               | 255 |
+| 12.2.3.2   | Test procedure                               | 255 |
+| 12.2.3.2.1 | Stage 1: Calibration                         | 255 |
+| 12.2.3.2.2 | Stage 2: BS measurement                      | 255 |
+| 12.2.3.3   | MU value derivation, FR2                     | 255 |
+| 12.2.4     | Reverberation chamber                        | 256 |
+| 12.2.4.1   | Measurement system description               | 256 |
+| 12.2.4.2   | Test procedure                               | 257 |
+| 12.2.4.2.1 | Stage 1: Calibration                         | 257 |
+| 12.2.4.2.2 | Stage 2: BS measurement                      | 257 |
+| 12.2.4.3   | MU value derivation                          | 257 |
+| 12.2.5     | Maximum accepted test system uncertainty     | 259 |
+| 12.2.6     | Test Tolerance for OTA TX spurious emissions | 260 |
+| 12.3       | Receiver spurious emissions                  | 260 |
+| 12.3.1     | General                                      | 260 |
+| 12.3.2     | General Chamber                              | 260 |
+| 12.3.2.1   | Measurement system description               | 260 |
+| 12.3.2.2   | Test procedure                               | 260 |
+| 12.3.2.2.1 | Stage 1: Calibration                         | 260 |
+| 12.3.2.2.2 | Stage 2: BS measurement                      | 261 |
+
+|            |                                                               |     |
+|------------|---------------------------------------------------------------|-----|
+| 12.3.2.3   | MU value derivation, FR1                                      | 261 |
+| 12.3.3     | Maximum accepted test system uncertainty                      | 264 |
+| 12.3.4     | Test Tolerance for OTA RX spurious emissions                  | 265 |
+| 12.4       | Additional (co-existence) spurious emissions                  | 265 |
+| 12.4.1     | General                                                       | 265 |
+| 12.4.2     | Compact Antenna Test Range                                    | 266 |
+| 12.4.2.1   | Measurement system description                                | 266 |
+| 12.4.2.2   | Test procedure                                                | 266 |
+| 12.4.2.2.1 | Stage 1: Calibration                                          | 266 |
+| 12.4.2.2.2 | Stage 2: BS measurement                                       | 266 |
+| 12.4.2.3   | MU value derivation, FR1                                      | 266 |
+| 12.4.3     | Maximum accepted test system uncertainty                      | 267 |
+| 12.4.4     | Test Tolerance for additional spurious emissions requirements | 268 |
+| 13         | Co-location requirements                                      | 268 |
+| 13.1       | General                                                       | 268 |
+| 13.2       | OTA transmitter OFF power                                     | 268 |
+| 13.2.1     | General                                                       | 268 |
+| 13.2.2     | General Chamber                                               | 269 |
+| 13.2.2.1   | Measurement system description                                | 269 |
+| 13.2.2.2   | Test procedure                                                | 269 |
+| 13.2.2.2.1 | Stage 1: Calibration                                          | 269 |
+| 13.2.2.2.2 | Stage 2: measurement                                          | 269 |
+| 13.2.2.3   | MU value derivation, FR1                                      | 270 |
+| 13.2.3     | Maximum accepted test system uncertainty                      | 271 |
+| 13.2.4     | Test Tolerance for OTA TX OFF power                           | 271 |
+| 13.3       | OTA co-location spurious emissions                            | 271 |
+| 13.3.1     | General                                                       | 271 |
+| 13.3.2     | General Chamber                                               | 271 |
+| 13.3.2.1   | Measurement system description                                | 271 |
+| 13.3.2.2   | Test procedure                                                | 272 |
+| 13.3.2.2.1 | Stage 1: Calibration                                          | 272 |
+| 13.3.2.2.2 | Stage 2: BS measurement                                       | 272 |
+| 13.3.2.3   | MU value derivation, FR1                                      | 272 |
+| 13.3.3     | Maximum accepted test system uncertainty                      | 273 |
+| 13.3.4     | Test Tolerance co-location spurious emissions                 | 274 |
+| 13.4       | OTA transmitter intermodulation                               | 274 |
+| 13.4.1     | General                                                       | 274 |
+| 13.4.2     | General Chamber                                               | 274 |
+| 13.4.2.1   | Measurement system description                                | 274 |
+| 13.4.2.2   | Test procedure                                                | 274 |
+| 13.4.2.2.1 | Stage 1: Calibration                                          | 274 |
+| 13.4.2.2.2 | Stage 2: BS measurement                                       | 274 |
+| 13.4.2.3   | MU value derivation, FR1                                      | 275 |
+| 13.4.3     | Maximum accepted test system uncertainty                      | 275 |
+| 13.4.4     | Test Tolerance co-location spurious emissions                 | 276 |
+| 13.5       | OTA co-location blocking                                      | 276 |
+| 13.5.1     | General                                                       | 276 |
+| 13.5.2     | General Chamber                                               | 276 |
+| 13.5.2.1   | Measurement system description                                | 276 |
+| 13.5.2.2   | Test procedure                                                | 276 |
+| 13.5.2.2.1 | Stage 1: Calibration                                          | 276 |
+| 13.5.2.2.2 | Stage 2: BS measurement                                       | 276 |
+| 13.5.2.3   | MU value derivation, FR1                                      | 277 |
+| 13.5.3     | Maximum accepted test system uncertainty                      | 277 |
+| 13.5.4     | Test Tolerance for OTA co-location blocking                   | 278 |
+| 14         | Out-of-band blocking requirements                             | 278 |
+| 14.1       | General                                                       | 278 |
+| 14.2       | General Chamber                                               | 279 |
+| 14.2.1     | Measurement system description                                | 279 |
+| 14.2.2     | Test procedure                                                | 279 |
+
+|          |                                                                |     |
+|----------|----------------------------------------------------------------|-----|
+| 14.2.2.1 | Stage 1: Calibration.....                                      | 279 |
+| 14.2.2.2 | Stage 2: BS measurement.....                                   | 279 |
+| 14.2.3   | MU value derivation, FR1.....                                  | 280 |
+| 14.2.4   | MU value derivation, FR2.....                                  | 281 |
+| 14.3     | Maximum accepted test system uncertainty.....                  | 282 |
+| 14.4     | Test Tolerance for OOB blocking.....                           | 282 |
+| 15       | Demodulation performance requirements.....                     | 282 |
+| 15.1     | General.....                                                   | 282 |
+| 15.2     | BS demodulation requirements feasible OTA.....                 | 282 |
+| 15.3     | OTA test setup for BS demodulation requirements.....           | 284 |
+| 15.4     | Indoor Anechoic Chamber.....                                   | 285 |
+| 15.4.1   | Measurement system description.....                            | 285 |
+| 15.4.2   | Test procedure.....                                            | 286 |
+| 15.4.2.1 | Stage 1: Calibration.....                                      | 286 |
+| 15.4.2.2 | Stage 2: BS measurement.....                                   | 286 |
+| 15.4.3   | MU value derivation, FR1.....                                  | 286 |
+| 15.5     | Compact Antenna Test Range.....                                | 287 |
+| 15.5.1   | Measurement system description.....                            | 287 |
+| 15.5.2   | Test procedure.....                                            | 287 |
+| 15.5.2.1 | Stage 1: Calibration.....                                      | 287 |
+| 15.5.2.2 | Stage 2: BS measurement.....                                   | 287 |
+| 15.5.3   | MU value derivation, FR1.....                                  | 287 |
+| 15.6     | Maximum accepted test system uncertainty.....                  | 287 |
+| 15.7     | Test Tolerance for OTA demodulation requirements.....          | 287 |
+| 16       | EMC requirements.....                                          | 288 |
+| 16.1     | BS ports for the EMC purposes.....                             | 288 |
+| 16.2     | Field strength in EMC chamber.....                             | 288 |
+| 16.2.1   | General.....                                                   | 288 |
+| 16.2.2   | Conversion between dBm to V/m.....                             | 289 |
+| 16.3     | Protection of measurement equipment.....                       | 289 |
+| 16.4     | Emission requirements.....                                     | 290 |
+| 16.5     | Radiated immunity requirements.....                            | 291 |
+| 16.5.1   | General.....                                                   | 291 |
+| 16.5.2   | Measurement set-up for testing radiated immunity.....          | 291 |
+| 16.5.2   | Alternatives to protect <i>BS type I-O</i> during RI test..... | 291 |
+| 16.5.2.1 | Exclusion bands.....                                           | 292 |
+| 16.5.2.2 | Spatial exclusion.....                                         | 292 |
+
+|                                                                                            |                                                                 |            |
+|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------|------------|
+| 17                                                                                         | Measurement Uncertainty values summary.....                     | 294        |
+| 18                                                                                         | Test Tolerance values summary.....                              | 297        |
+| <b>Annex A (informative): Radiated TX measurement error contribution descriptions.....</b> |                                                                 | <b>301</b> |
+| A.1                                                                                        | Indoor Anechoic Chamber.....                                    | 301        |
+| A.2                                                                                        | Compact Antenna Test Range.....                                 | 303        |
+| A.3                                                                                        | Near Field Test Range.....                                      | 306        |
+| A.4                                                                                        | One Dimensional Compact Range.....                              | 309        |
+| A.5                                                                                        | General Chamber.....                                            | 311        |
+| A.6                                                                                        | Reverberation Chamber.....                                      | 313        |
+| A.7                                                                                        | Plane Wave Synthesizer.....                                     | 314        |
+| <b>Annex B (informative): Radiated RX measurement error contribution descriptions.....</b> |                                                                 | <b>316</b> |
+| B.1                                                                                        | Indoor Anechoic Chamber.....                                    | 316        |
+| B.2                                                                                        | Compact Antenna Test Range.....                                 | 318        |
+| B.3                                                                                        | Near Field Test Range.....                                      | 319        |
+| B.4                                                                                        | One Dimensional Compact Range.....                              | 322        |
+| B.5                                                                                        | Plane Wave Synthesizer.....                                     | 324        |
+| <b>Annex C (informative): Test equipment uncertainty values.....</b>                       |                                                                 | <b>326</b> |
+| C.1                                                                                        | Test equipment measurement error contribution descriptions..... | 326        |
+| C.2                                                                                        | Measurement Equipment uncertainty values.....                   | 327        |
+| C.3                                                                                        | MU of TE derived from conducted specification.....              | 328        |
+| <b>Annex D (informative): Beam sweeping.....</b>                                           |                                                                 | <b>330</b> |
+| D.1                                                                                        | Introduction.....                                               | 330        |
+| D.2                                                                                        | Simulation results.....                                         | 330        |
+| D.3                                                                                        | Measurement results.....                                        | 331        |
+| D.4                                                                                        | Design of beam sweeping test signal.....                        | 333        |
+| <b>Annex E (informative): Sparse sampling for spurious emissions.....</b>                  |                                                                 | <b>334</b> |
+| <b>Annex F (informative): Power density measurements close to BS.....</b>                  |                                                                 | <b>339</b> |
+| <b>Annex G (informative): Excel spreadsheets for MU derivation.....</b>                    |                                                                 | <b>341</b> |
+| <b>Annex H (informative): Change history.....</b>                                          |                                                                 | <b>342</b> |
+
+## Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, modal verbs have the following meanings:
+
+- shall** indicates a mandatory requirement to do something
+- shall not** indicates an interdiction (prohibition) to do something
+
+The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+- should** indicates a recommendation to do something
+- should not** indicates a recommendation not to do something
+- may** indicates permission to do something
+- need not** indicates permission not to do something
+
+The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+- can** indicates that something is possible
+- cannot** indicates that something is impossible
+
+The constructions "can" and "cannot" are not substitutes for "may" and "need not".
+
+- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+The constructions "is" and "is not" do not indicate requirements.
+
+# 1 Scope
+
+The present document is the Technical Report for the Work Item on Over The Air (OTA) Base Station (BS) testing.
+
+This Technical Report covers background information of OTA testing methods, measurement uncertainty and test tolerance values derivation for the radiated conformance testing requirements. This Technical Report covers radiated conformance testing requirements for the following BS types:
+
+- *Hybrid AAS BS* as specified in AAS BS radiated testing specification TS 37.145-2 [4] for the following radio technologies:
+  - *Hybrid AAS BS in single RAT UTRA operation, TDD*
+  - *Hybrid AAS BS in single RAT UTRA operation, FDD*
+  - *Hybrid AAS BS in single RAT E-UTRA operation*
+  - *Hybrid AAS BS in MSR operation* implementing any of the above RATs, including NR operation.
+- OTA AAS BS as specified in AAS BS radiated testing specification TS 37.145-2 [4] for the following radio technologies:
+  - OTA AAS BS in *single RAT UTRA operation, FDD*
+  - OTA AAS BS in *single RAT E-UTRA operation*
+  - OTA AAS BS in *MSR operation* implementing any of the above RATs, and/or NR.
+- *BS type 1-H in single RAT NR operation* in FR1, as specified in NR BS radiated testing specification TS 38.141-2 [6],
+- *BS type 1-O in single RAT NR operation* in FR1, as specified in NR BS radiated testing specification TS 38.141-2 [6],
+- *BS type 2-O in single RAT NR operation* in FR2, as specified in NR BS radiated testing specification TS 38.141-2 [6].
+
+Generic term "BS" is used to refer to any of these BS types, unless otherwise stated.
+
+This 3GPP external Technical Report consolidates the OTA measurement related information originating from multiple AAS BS and NR BS internal technical reports. This information is needed to supplement the BS radiated testing specifications as a single, 3GPP external technical report, such that the information can be referred to from external specifications and bodies.
+
+The NR BS specification refers to two frequency ranges, FR1 and FR2. The AAS BS specification is only applicable for operating bands within FR1. Thus, sections in this report referring to FR2 should be considered as applicable to NR only.
+
+## 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TS 25.141: "Base Station (BS) conformance testing (FDD)".
+- [3] 3GPP TS 36.141: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing".
+- [4] 3GPP TS 37.145-2: "Active Antenna System (AAS) Base Station (BS) conformance testing; Part 2: Radiated conformance testing".
+- [5] 3GPP TS 38.141-1: "NR; Base Station (BS) conformance testing; Part 1: Conducted conformance testing".
+- [6] 3GPP TS 38.141-2: "NR; Base Station (BS) conformance testing; Part 2: Radiated conformance testing".
+- [7] IEEE Std 149: "IEEE Standard Test Procedures for Antennas", IEEE.
+- [8] JCGM 100:2008: "Evaluation of measurement data — Guide to the expression of uncertainty in measurement".
+- [9] Hald, J.; Hansen, J. E.; Jensen, F. & Holm Larsen, F. Hansen, J. (Ed): "Spherical Near-Field Antenna Measurements", Peter Peregrinus Ltd., 1998, vol 26.
+- [10] J. Fridén, A. Razavi, and A. Stjernman: "Angular sampling, Test Signal, and Near-Field Aspects for Over-the-Air Total Radiated Power Assessment in Anechoic Chambers", IEEE Access, 2018, <https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8470084>.
+- [11] IEC 61000-4-21: "Electromagnetic compatibility (EMC) - Part 4-21: Testing and measurement techniques - Reverberation chamber test methods", Edition 2.0 2011-01, The International Electrotechnical Commission (IEC), 2011.
+- [12] Hill, D.A.: "Boundary fields in reverberation chambers", IEEE Transactions on Electromagnetic Compatibility, vol. 47, no. 2, pp. 281-290, May 2005.
+- [13] Krauthäuser, H. G.; Winzerling, T.; J., N.; Eulig, N. & Enders, A: "Statistical interpretation of autocorrelation coefficients for fields in mode-stirred chambers", 2005 International Symposium on Electromagnetic Compatibility, 2005. EMC 2005, 2005, 2, 550-555.
+- [14] 3GPP TS 37.105: "Active Antenna System (AAS) Base Station (BS) transmission and reception".
+- [15] ITU-R Recommendation SM.329: "Unwanted emissions in the spurious domain".
+- [16] 3GPP TS 37.113: "E-UTRA, UTRA and GSM/EDGE; Multi-Standard Radio (MSR) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [17] 3GPP TS 37.114: "Active Antenna System (AAS) Base Station (BS) Electromagnetic Compatibility (EMC)".
+- [18] 3GPP TS 38.113: "Base Station (BS) Electromagnetic Compatibility (EMC)".
+
+- [19] IEC 61000-4-3: "Electromagnetic compatibility (EMC) - Part 4-3: Testing and measurement techniques - Radiated, radio-frequency, electromagnetic field immunity test".
+- [20] Victor Rabinovich, Nikolai Alexandrov, Basim Alkhateeb: "Automotive Antenna Design and Applications"; 2010.
+- [21] 3GPP TS 37.145-1: "Base Station (BS) conformance testing Part 1: Conducted conformance testing".
+- [22] Jonas Fridén: "Sparse sampling analysis", Matlab code, 2020, [https://se.mathworks.com/matlabcentral/fileexchange/67143-sparse-sampling-analysis-tool?s\\_tid=srchtitle](https://se.mathworks.com/matlabcentral/fileexchange/67143-sparse-sampling-analysis-tool?s_tid=srchtitle).
+- [23] Void.
+- [24] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode".
+- [25] ERC Recommendation 74-01: "Unwanted emissions in the spurious domain".
+
+---
+
+## 3 Definitions of terms, symbols and abbreviations
+
+### 3.1 Terms
+
+For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+NOTE 1: Multi-word definitions are treated as linguistic expressions and printed in italic font throughout this requirement specification. Linguistic expressions may not be split and are printed in their entirety.
+
+**active antenna system base station:** base station system which combines an *antenna array* with a *transceiver unit* array and a *radio distribution network*
+
+**array element:** subdivision of a passive *antenna array*, consisting of a single *radiating element* or a group of *radiating elements*, with a fixed *radiation pattern*
+
+**antenna array:** group of *radiating elements* characterized by the geometry and the properties of the *array elements*
+
+**antenna gain:** ratio of the radiation intensity, in a given direction, to the radiation intensity that would be obtained if the power accepted by the antenna were radiated isotropically
+
+NOTE 2: If the direction is not specified, the direction of maximum radiation intensity is implied.
+
+**array factor:** *radiation pattern* of an array antenna when each *array element* is considered to radiate isotropically
+
+NOTE 3: When the *radiation pattern* of individual *array elements* are identical, and the *array elements* are congruent under translation, then the product of the *array factor* and the *array element radiation pattern* gives the *radiation pattern* of the entire array.
+
+**angle of arrival:** is the direction of propagation of electromagnetic wave incident on an BS *antenna array*
+
+**beam:** main lobe of a *radiation pattern* from a BS
+
+NOTE 4: For certain BS *antenna array*, there may be more than one beam.
+
+**beam centre direction:** direction equal to the geometric centre of the half-power contour of the beam
+
+**beam direction pair:** data set consisting of the *beam centre direction* and the related *beam peak direction*
+
+**beam peak direction:** direction where the maximum EIRP is supposed to be found
+
+**beamwidth:** beam which has a half-power contour that is essentially elliptical, the half-power beamwidths in the two pattern cuts that respectively contain the major and minor axis of the ellipse
+
+**BS type 1-O:** NR base station operating at FR1 with a requirement set consisting only of OTA requirements defined at the RIB
+
+**BS type 2-O:** NR base station operating at FR2 with a requirement set consisting only of OTA requirements defined at the RIB
+
+**co-location reference antenna:** reference antenna used for co-location requirements
+
+**co-location test antenna:** practical passive antenna that is used for conformance testing of the co-location requirements and is based on the definition of the *co-location reference antenna*
+
+**cylindrical diameter:** diameter of the smallest cylinder that encloses the radiation source along z-axis (in reference angular step criteria)
+
+**directivity:** ratio of the radiation intensity in a given direction from the antenna to the radiation intensity averaged over all directions
+
+NOTE 5: If the direction is not specified, the direction of maximum radiation intensity is implied.
+
+**equivalent isotropic radiated power:** equivalent power radiated from an isotropic directivity device producing the same field intensity at a point of observation as the field intensity radiated in the direction of the same point of observation by the discussed device
+
+NOTE 6: Isotropic directivity is equal in all directions (i.e. 0 dBi).
+
+**equivalent isotropic sensitivity:** sensitivity for an isotropic directivity device equivalent to the sensitivity of the discussed device exposed to an incoming wave from a defined AoA
+
+NOTE 7: The sensitivity is the minimum received power level at which a RAT specific requirement is met.
+
+NOTE 8: Isotropic directivity is equal in all directions (i.e. 0 dBi).
+
+**frequency range 1:** frequency range capturing AAS BS or NR BS operation in range from 410 MHz up to 7125 MHz
+
+**frequency range 2:** frequency range capturing NR BS operation in range from 24250 MHz up to 52600 MHz
+
+**hybrid AAS BS:** AAS BS which has both a conducted RF interface and a radiated RF interface in the far field and conforms to a *hybrid requirements set*
+
+**hybrid requirements set:** Complete set of requirements applied to a *hybrid AAS BS* with both conducted and radiated requirements
+
+**MSR operation:** operation of AAS BS declared to be MSR in particular *operating band(s)*
+
+**OTA coverage range:** a common range of directions within which TX OTA requirements that are neither specified in the *OTA peak directions sets* nor as *TRP requirement* are intended to be met
+
+**OTA peak directions set:** set(s) of *beam peak directions* within which certain TX OTA requirements are intended to be met, where all *OTA peak directions set(s)* are subsets of the *OTA coverage range*
+
+NOTE 9: The *beam peak directions* are related to a corresponding contiguous range or discrete list of *beam centre directions* by the *beam direction pairs* included in the set.
+
+**OTA REFSSENS RoAoA:** is the RoAoA determined by the contour defined by the points at which the achieved EIS is 3dB higher than the achieved EIS in the reference direction.
+
+NOTE 10: This contour will be related to the average element/sub-array *radiation pattern* 3dB beam width
+
+**OTA requirements set:** complete set of OTA requirements applied to an OTA BS
+
+**OTA sensitivity directions declaration:** set of manufacturer declarations comprising at least one set of declared minimum EIS values (with related RAT and *channel bandwidth*), and related directions over which the EIS applies
+
+NOTE 11: All the directions apply to all the EIS values in an OSDD.
+
+**polarization match:** condition that exists when a plane wave, incident upon an antenna from a given direction, has a polarization that is the same as the receiving polarization of the antenna in that direction
+
+**radiated interface boundary:** operating band specific radiated requirements reference where the radiated requirements apply
+
+NOTE 12: For requirements based on EIRP/EIS, the *radiated interface boundary* is associated to the far-field region
+
+**radiating element:** basic building block of an *array element* characterized by its radiation properties
+
+**radiation pattern:** angular distribution of the radiated electromagnetic field or power level in the far field region
+
+**radio distribution network:** linear passive network which distributes the RF power generated by the *transceiver unit* array to the *antenna array*, and/or distributes the radio signals collected by the *antenna array* to the *transceiver unit* array
+
+NOTE 13: In the case when the active *transceiver units* are physically integrated with the *array elements* of the *antenna array*, the *radio distribution network* is a one-to-one mapping.
+
+**receiver target:** AoA in which reception is performed by OTA BS.
+
+NOTE 14: In this TR, OTA BS is considered to be either OTA AAS BS, or NR BS (*BS type 1-O*, or *BS type 2-O*).
+
+**receiver target redirection range:** union of all the *sensitivity RoAoA* achievable through redirecting the *receiver target* related to particular OSDD
+
+**receiver target reference direction:** direction inside the *OTA sensitivity directions declaration* declared by the manufacturer for conformance testing. For an OSDD without *receiver target redirection range*, this is a direction inside the *sensitivity RoAoA*
+
+**sensitivity RoAoA:** RoAoA within the *OTA sensitivity directions declaration*, within which the declared EIS(s) of an OSDD is intended to be achieved at any instance of time for a specific AAS BS direction setting
+
+**single RAT E-UTRA operation:** operation of AAS BS declared to be single RAT E-UTRA in the *operating band*
+
+NOTE 15: *Single RAT E-UTRA operation* does not cover in-band NB-IoT, nor guardband NB-IoT operation.
+
+**single RAT UTRA operation:** operation of AAS BS declared to be single RAT UTRA in the *operating band*
+
+**spherical diameter:** diameter of the smallest sphere enclosing the radiation source (in reference angular step criteria)
+
+**total radiated power:** is the total power radiated by the antenna.
+
+NOTE 16: The *total radiated power* is the power radiating in all direction for two orthogonal polarizations.
+
+NOTE 17: *Total radiated power* is defined in both the near-field region and the far-field region.
+
+**transceiver array boundary:** conducted interface between the *transceiver unit array* and the composite antenna
+
+**transceiver unit:** active unit consisting of transmitter and/or receiver which transmits and/or receives radio signals, and which may include passive RF filters
+
+**transceiver unit array:** array of *transceiver units* which generate radio signals in the transmit direction and accept radio signals in the receive direction
+
+**transmitter ON period:** time period during which the transmitter is transmitting data and/or reference symbols
+
+**TRP requirement:** OTA BS requirements, which requires dual-polarized measurements of the figure of merit over the whole sphere around the BS
+
+**TRP summation error:** the relative difference between theoretical TRP and numerically estimated TRP
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+$\varphi$  Azimuth angle (defined between  $-180^\circ$  and  $180^\circ$ )
+
+|                                            |                                                                                                                                                                      |
+|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $\theta$                                   | Elevation angle of the signal direction (defined between $-90^\circ$ and $90^\circ$ , $0^\circ$ represents the direction perpendicular to the <i>antenna array</i> ) |
+| $BeW_\theta$                               | Beamwidth in the $\theta$ -axis in degrees                                                                                                                           |
+| $BeW_\phi$                                 | Beamwidth in the $\phi$ -axis in degrees                                                                                                                             |
+| $c_i$                                      | Sensitivity coefficient                                                                                                                                              |
+| $D$                                        | Diameter of the source enclosure, i.e., the diameter of the smallest sphere enclosing all sources                                                                    |
+| $D$                                        | Largest dimension of the antenna of BS (measurement system description)                                                                                              |
+| $D_{\text{BSoutputpower}}$                 | Directivity of BS for the OTA BS output power requirement                                                                                                            |
+| $D_{\text{cyl}}$                           | Diameter of the smallest z-directed circular cylinder that encloses all sources.                                                                                     |
+| $D_{\text{BS}}$                            | Directivity of BS                                                                                                                                                    |
+| $D_y$                                      | Length of radiating part of the BS along y-axis,                                                                                                                     |
+| $D_z$                                      | Length of radiated part of the BS along the z-axis                                                                                                                   |
+| $\text{EIRP}_d$                            | EIRP value for the desired signal (unwanted emissions requirement)                                                                                                   |
+| $\text{EIRP}_e$                            | EIRP value for the emissions (unwanted emissions requirement)                                                                                                        |
+| $\text{EIS}_{\text{REFSENS}}$              | OTA reference sensitivity                                                                                                                                            |
+| $\Gamma_{\text{SGH}}$                      | Reflection coefficient (or mismatch) seen at the SGH connector ( $S_{11}$ with a network analyzer)                                                                   |
+| $G_{\text{REF\_ANT}}$                      | Gain of the reference antenna                                                                                                                                        |
+| $\eta$                                     | Radiation efficiency                                                                                                                                                 |
+| $L$                                        | distance along the z-axis (reference angular step criteria)                                                                                                          |
+| $L_{\text{cal, A}\rightarrow\text{B}}$     | Calibration value between point A and B (measurement system setup)                                                                                                   |
+| $LF_{\text{A}\rightarrow\text{B}}$         | Pathloss between point A and B, or cable loss between point A and B (measurement system setup)                                                                       |
+| $L_{\text{TX\_cal, A}\rightarrow\text{D}}$ | EIRP value for the E-UTRA DL RS requirement                                                                                                                          |
+| $M_1^{(r)}$                                | Mis-match efficiency (reverberation chamber calibration)                                                                                                             |
+| $\text{MU}_{\text{perpoint}}$              | MU value for the per-point measurement for the <i>TRP requirements</i>                                                                                               |
+| $P^{(r)}$                                  | Reference transfer function (reverberation chamber calibration)                                                                                                      |
+| $P_{\text{DL\_RS}}$                        | Measured signal power of DL RS EIRP (E-UTRA DL RS requirement)                                                                                                       |
+| $P_{\text{meas}}$                          | Measured mean power                                                                                                                                                  |
+| $P_{\text{R\_EIRP, D}}$                    | Measured mean power for each carrier at the measurement equipment connector at the reference point D of the OTA measurement system                                   |
+| $P_{\text{rated,c,EIRP}}$                  | Rated EIRP when all the transmitter units are operating at their rated output power for a single carrier                                                             |
+| $P_{\text{rated,c,TRP}}$                   | Rated <i>total radiated power</i> when all the transmitter units are operating at their rated output power for a single carrier                                      |
+| $R_{\text{sph}}$                           | Radius of the smallest sphere enclosing the BS                                                                                                                       |
+| $\text{TRP}_d$                             | TRP values of the desired signal (ACLR calculation)                                                                                                                  |
+| $\text{TRP}_e$                             | TRP values of the emissions (ACLR calculation)                                                                                                                       |
+| $\text{TRP}_{\text{Estimate}}$             | Numerically approximated TRP                                                                                                                                         |
+| $\text{TRP}_{\text{Reference}}$            | Theoretical TRP                                                                                                                                                      |
+| $u_c$                                      | Combined uncertainty                                                                                                                                                 |
+| $u_e$                                      | Expanded uncertainty                                                                                                                                                 |
+| $u_i$                                      | Standard uncertainty                                                                                                                                                 |
+| $\Delta\text{TRP}$                         | TRP correction factor                                                                                                                                                |
+| $\lambda$                                  | Wavelength                                                                                                                                                           |
+
+### 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|         |                                |
+|---------|--------------------------------|
+| ID CATR | One Dimensional Compact Range  |
+| AA      | Antenna Array                  |
+| AAS     | Active Antenna System          |
+| ACLR    | Adjacent Channel Leakage Ratio |
+| ACS     | Adjacent Channel Selectivity   |
+| AoA     | Angle of Arrival               |
+| BFN     | Beam Forming Network           |
+| BS      | Base Station                   |
+| BW      | Bandwidth                      |
+| CACLR   | Cumulative ACLR                |
+
+|            |                                                           |
+|------------|-----------------------------------------------------------|
+| CATR       | Compact Antenna Test Range                                |
+| CLTA       | Co-Location Test Antenna                                  |
+| D          | Largest dimension of the antenna of BS                    |
+| EIRP       | Equivalent Isotropic Radiated Power                       |
+| EIS        | Equivalent Isotropic Sensitivity                          |
+| EMC        | Electromagnetic compatibility                             |
+| EVM        | Error Vector Magnitude                                    |
+| FF         | Far Field                                                 |
+| FR         | Frequency Range                                           |
+| HPBW       | Half Power Beamwidth                                      |
+| IAC        | Indoor Anechoic Chamber                                   |
+| LA         | Local Area                                                |
+| LAA        | Licensed Assisted Access                                  |
+| LNA        | Low Noise Amplifier                                       |
+| MR         | Medium Range                                              |
+| MU         | Measurement Uncertainty                                   |
+| NF         | Near Field                                                |
+| NFTR       | Near Field Test Range                                     |
+| NR         | New Radio                                                 |
+| OBUE       | Operating Band Unwanted Emissions                         |
+| OSDD       | OTA Sensitivity Direction Declaration                     |
+| OTA        | Over-the-Air                                              |
+| PD         | Power Density                                             |
+| PTF        | Power Transfer Function                                   |
+| PWS        | Plane Wave Synthesizer                                    |
+| QZ         | Quiet Zone                                                |
+| RC         | Reverberation Chamber                                     |
+| RDN        | Radio Distribution Network                                |
+| REF TX ant | Reference transmitter antenna (for Reverberation Chamber) |
+| RIB        | Radiated Interface Boundary                               |
+| RoAoA      | Range of Angles of Arrival                                |
+| RSS        | Root of the Sum of the Squares                            |
+| SA         | Signal Analyser                                           |
+| SE         | Summation Error                                           |
+| SEM        | Spectrum Emission Mask                                    |
+| SF         | Sparsity Factor                                           |
+| SG         | Signal Generator                                          |
+| SGH        | Standard Gain Horn                                        |
+| TAE        | Time Alignment Error                                      |
+| TRP        | Total Radiated Power                                      |
+| TT         | Test Tolerance                                            |
+| UID        | Uncertainty Identifier                                    |
+| ULA        | Uniform Linear Array                                      |
+| VNA        | Vector Network Analyser                                   |
+| VSWR       | Voltage Standing Wave Ratio                               |
+| WA         | Wide Area                                                 |
+
+## 4 Coordinate system
+
+OTA requirements are stated in terms of electromagnetic and spatial parameters. The electromagnetic parameters are specified either in terms of power (dBm) or field strength (dB $\mu$ V/m). The spatial parameters are specified in a Cartesian coordinate system ( $x, y, z$ ) with an addition of spherical coordinates ( $r, \Theta, \phi$ ) for manufacturer declared parameters.
+
+The orientation of these coordinates is depicted in the following figures 4-1, 4-2 and 4-3. In figure 4-2,  $\phi$  is the angle in the x/y plane and it is between the x-axis and the projection of the vector onto the x/y plane and is defined between  $-180^\circ$  and  $+180^\circ$ , inclusive. In figure 4-3, the angle  $\Theta$  is the angle between the projection of the vector in the x/y plane and the vector and is defined between  $-90^\circ$  and  $+90^\circ$ , inclusive.
+
+A point in the spherical coordinates ( $r, \Theta, \phi$ ) can be transformed to Cartesian coordinate system ( $x, y, z$ ) using the following relationships:
+
+The inverse transformation from Cartesian coordinate system  $(x, y, z)$  to spherical coordinates  $(r, \Theta, \phi)$  is given by:
+
+![Figure 4-1: Coordinate system representation in Cartesian coordinate system. This 3D diagram shows a Cartesian coordinate system with red axes labeled x, y, and z. A black vector originates from the origin. The angle between the positive z-axis and this vector is labeled Θ (polar angle). The angle between the positive x-axis and the projection of the vector onto the xy-plane is labeled φ (azimuthal angle). Dotted lines indicate the projection of the vector onto the xy-plane and the z-axis.](d4c143a69ccd7e28fe8d01dbc9dfbcfa_img.jpg)
+
+Figure 4-1: Coordinate system representation in Cartesian coordinate system. This 3D diagram shows a Cartesian coordinate system with red axes labeled x, y, and z. A black vector originates from the origin. The angle between the positive z-axis and this vector is labeled Θ (polar angle). The angle between the positive x-axis and the projection of the vector onto the xy-plane is labeled φ (azimuthal angle). Dotted lines indicate the projection of the vector onto the xy-plane and the z-axis.
+
+Figure 4-1: Coordinate system representation in Cartesian coordinate system
+
+![Figure 4-2: Representation of the φ angle (positive and negative values). This 2D diagram shows the xy-plane with a red x-axis and a red y-axis. A circle is centered at the origin. The angle φ is measured from the positive x-axis. Positive values of φ are shown in the first and second quadrants, while negative values are shown in the third and fourth quadrants. The angle φ = 180° is indicated on the negative x-axis. Two gray arrows represent vectors at angles +φ and -φ from the positive x-axis.](03d99823cac9b0c49db95d65dc155d8c_img.jpg)
+
+Figure 4-2: Representation of the φ angle (positive and negative values). This 2D diagram shows the xy-plane with a red x-axis and a red y-axis. A circle is centered at the origin. The angle φ is measured from the positive x-axis. Positive values of φ are shown in the first and second quadrants, while negative values are shown in the third and fourth quadrants. The angle φ = 180° is indicated on the negative x-axis. Two gray arrows represent vectors at angles +φ and -φ from the positive x-axis.
+
+Figure 4-2: Representation of the  $\phi$  angle (positive and negative values)
+
+![Figure 4-3: Representation of Θ angle (positive and negative values).](5a2d10b858b621236f708a5f5fa1ed88_img.jpg)
+
+This diagram shows a 3D Cartesian coordinate system with red axes labeled x, y, and z. The z-axis is vertical, the x-axis is horizontal to the right, and the y-axis points diagonally up and to the right. A black vector originates from the origin and points into the lower-right-front octant. The angle between the positive z-axis and this vector is labeled  $\Theta$ . Two arcs indicate the range of  $\Theta$ : one from the positive z-axis to the positive x-axis labeled  $\Theta = 90^\circ$ , and another from the positive z-axis to the negative z-axis labeled  $\Theta = +90^\circ$ .
+
+Figure 4-3: Representation of Θ angle (positive and negative values).
+
+**Figure 4-3: Representation of  $\Theta$  angle (positive and negative values)**
+
+For the conformance requirements purposes in TS 37.145-2 [4] and TS 38.141-2 [6] the manufacturer declares this coordinate system reference point as a location in reference to an identifiable physical feature of the BS enclosure. The manufacturer also declares the orientation of this coordinate system in reference to an identifiable physical feature of the BS enclosure.
+
+Another conventions for spatial angles are also used and can be found in definitions in IEEE Standard Test Procedures for Antennas [7] as shown in figure 4-4, figure 4-5 and figure 4-6. Such a convention is used in the TRP expression, e.g. as in clause 6.3. In figure 4-5, the angle  $\phi$  is defined for positive values only, that is, from  $0^\circ$  to  $360^\circ$ , inclusive. In figure 4-6, the angle  $\theta$  corresponds to  $\Theta$  in figure 4-3, but it is important to note that  $\theta$  is formed by the positive z-axis and the vector and is defined between  $0^\circ$  and  $+180^\circ$ , inclusive.
+
+![Figure 4-4: Another coordinate system representation in Cartesian coordinate system.](513b2f88e0edcd2ffb6b7cf54f465d06_img.jpg)
+
+This diagram shows a 3D Cartesian coordinate system with red axes labeled x, y, and z. The z-axis is vertical, the y-axis is horizontal to the right, and the x-axis points diagonally down and to the left. A black vector originates from the origin and points into the upper-right-front octant. The angle between the positive z-axis and this vector is labeled  $\theta$ . The angle between the positive y-axis and the projection of the vector onto the xy-plane is labeled  $\phi$ .
+
+Figure 4-4: Another coordinate system representation in Cartesian coordinate system.
+
+**Figure 4-4: Another coordinate system representation in Cartesian coordinate system**
+
+![Figure 4-5: A 3D coordinate system with x, y, and z axes. The x-axis is horizontal to the right, the y-axis is vertical upwards, and the z-axis is a red dot at the origin. A vector is shown in the x-y plane. The angle phi is measured counter-clockwise from the positive x-axis to the vector. Labels include phi=180 degrees, phi=270 degrees, and phi.](8f931bb1d65d0ee4ccafab751ee61282_img.jpg)
+
+Figure 4-5: A 3D coordinate system with x, y, and z axes. The x-axis is horizontal to the right, the y-axis is vertical upwards, and the z-axis is a red dot at the origin. A vector is shown in the x-y plane. The angle phi is measured counter-clockwise from the positive x-axis to the vector. Labels include phi=180 degrees, phi=270 degrees, and phi.
+
+Figure 4-5: Another representation of the  $\phi$  angle (positive values only)
+
+![Figure 4-6: A 3D coordinate system with x, y, and z axes. The x-axis is horizontal to the right, the y-axis is diagonal upwards and to the right, and the z-axis is vertical upwards. A vector is shown in the z-y plane. The angle theta is measured counter-clockwise from the positive z-axis to the vector. Labels include theta=180 degrees, theta=90 degrees, and theta.](e5c6de7d8ff5b0d75d5602d200b899f0_img.jpg)
+
+Figure 4-6: A 3D coordinate system with x, y, and z axes. The x-axis is horizontal to the right, the y-axis is diagonal upwards and to the right, and the z-axis is vertical upwards. A vector is shown in the z-y plane. The angle theta is measured counter-clockwise from the positive z-axis to the vector. Labels include theta=180 degrees, theta=90 degrees, and theta.
+
+Figure 4-6: Another representation of  $\theta$  angle (positive values only)
+
+## 5 Conformance testing aspects
+
+### 5.1 Conformance testing framework
+
+Traditionally when calculating the MU for the conducted tests it was sufficient to analyse a single test method, while for OTA tests the chamber is an integral part of the test environment and it is important to derive MU based on multiple chamber types and test methodologies. As such a framework has been developed to estimate MU's for different test methods and compare them equally.
+
+The following 11 points have been agreed as a framework for developing OTA test:
+
+- 1) Multiple test methods may exist for each requirement.
+- 2) Each test method will require its own test procedure.
+- 3) A single conformance requirement applies for each core requirement, regardless of test procedure.
+- 4) Common maximum accepted test system uncertainty applies for all test methods addressing the same test requirement. Test methods producing significantly worse uncertainty than others at comparable cost should not impact the common maximum accepted test system uncertainty assessment.
+- 5) Common test tolerances apply for all test methods addressing the same test requirement.
+- 6) A common way of establishing the uncertainty result from all test methods' individual budgets is established.
+- 7) A common method of making an uncertainty budget (not a common uncertainty budget) is established.
+- 8) Establish budget format examples for each addressed test method in the form of lists of uncertainty contributions. Contributions that may be negligible with some BS and substantial with others should be in this
+
+list. For each combination of measurement method and test parameter, develop a list with measurement uncertainties.
+
+- 9) Describe potential OTA test methods relevant for testing radiated requirements (e.g. directional, TRP, or co-location requirements). The description requires information about the applicable test range architectures and test procedures. Addressing each item in each uncertainty budget with respect to the expected distribution of the errors, the mechanism creating the error and how it interacts with properties of the BS.
+- 10) Providing example uncertainty budgets will be useful in order to demonstrate the way a budget should be defined and how calculating its resulting measurement uncertainty is done, but the figures used in the examples will clearly be only examples and not applicable in general.
+- 11) Each test instance may require an individual uncertainty budget applicable for the combination of the test facility, the BS and the test procedure and property tested. Here, the tester demonstrates that the uncertainty requirement is fulfilled during the conformance testing.
+
+The linking of core requirements via OTA test methods to conformance requirements is depicted in figure 5.1-2.
+
+![Figure 5.1-2: Examples of OTA core requirement to test requirement mapping. The diagram shows two parallel vertical flows for Requirement #1 and Requirement #2. Each flow starts with a 'Requirement' box, followed by a grid of 'Method' boxes (A, B, C, D, ...). Below each method are 'Description' and 'Procedure: calibration, measurement' boxes. A central horizontal box labeled 'Common uncertainty budget calculation principle' spans both flows. Below this, each flow has a grid of 'Uncertainty budget' boxes (format A, B, C, D, ...), followed by 'Uncertainty assessment' boxes. At the bottom of each flow are three stacked boxes: 'Standard measurement uncertainty σ (frequency dependant)', 'Test Tolerance (frequency dependant)', and 'Test requirement #1 (frequency dependant)' for Requirement #1, and 'Test requirement #2 (frequency dependant)' for Requirement #2.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg)
+
+Figure 5.1-2: Examples of OTA core requirement to test requirement mapping. The diagram shows two parallel vertical flows for Requirement #1 and Requirement #2. Each flow starts with a 'Requirement' box, followed by a grid of 'Method' boxes (A, B, C, D, ...). Below each method are 'Description' and 'Procedure: calibration, measurement' boxes. A central horizontal box labeled 'Common uncertainty budget calculation principle' spans both flows. Below this, each flow has a grid of 'Uncertainty budget' boxes (format A, B, C, D, ...), followed by 'Uncertainty assessment' boxes. At the bottom of each flow are three stacked boxes: 'Standard measurement uncertainty σ (frequency dependant)', 'Test Tolerance (frequency dependant)', and 'Test requirement #1 (frequency dependant)' for Requirement #1, and 'Test requirement #2 (frequency dependant)' for Requirement #2.
+
+**Figure 5.1-2: Examples of OTA core requirement to test requirement mapping**
+
+For *TRP requirements* the OTA conformance testing framework also considers additional aspects of the TRP measurements as detailed in clause 6.3. Depending on the TRP measurement procedure those additional aspects are, e.g. TRP sampling grids, additional MU contributors, *TRP summation error*, or  $\Delta$ TRP correction factor, if applicable.
+
+## 5.2 Uncertainty budget calculation principles
+
+Uncertainty contributions listed in clauses 9 – 15 with descriptions in annex A to C need to be calculated to provide an overall total measurement uncertainty for each OTA test method for the accompanying conformance requirement.
+
+The uncertainty tables are presented with two stages:
+
+- Stage 1: the calibration of the absolute level of the BS measurement results is performed by means of using a calibration antenna (for example a standard gain horn) whose absolute gain is known at the frequencies of measurement,
+- Stage 2: the actual measurement with the BS as either the transmitter or receiver (depending on the considered requirement) is performed.
+
+The final uncertainty budget should comprise of a minimum 5 headings:
+
+- 1) The uncertainty source,
+- 2) Uncertainty value,
+- 3) Distribution of the probability,
+- 4) Divisor based on distribution shape,
+- 5) Sensitivity coefficient  $c_i$  and its calculated standard uncertainty  $u_i$  (based on uncertainty value, divisor and sensitivity coefficient  $c_i$ ).
+
+NOTE: All measurement uncertainty contributions are assumed independent. Measurement uncertainty contributor's values in tables are given in log scale.
+
+The calculation of the uncertainty contribution is based on the ISO Guide on Evaluation of measurement data in [8] to the expression of uncertainty in measurement. Each individual uncertainty is expressed by its standard deviation (termed as 'standard uncertainty') and represented by symbol  $u_i$ .
+
+The procedure for forming the uncertainty budget can be as follows:
+
+- 1) Compile lists of individual uncertainty contributions for the requirement specific measurement, both in Stage 1 (i.e. Calibration measurement) and Stage 2 (i.e. BS measurement).
+- 2) Determine the standard uncertainty of each contribution  $u_i$  by:
+  - a) Determining the distribution of the uncertainty (i.e. Gaussian, U-shaped, rectangular, or exponentially normal).
+  - b) Determining the maximum value of each uncertainty (unless the distributions is Gaussian).
+  - c) Calculating the standard uncertainty by dividing the uncertainty by  $\sqrt{2}$  if the distribution is U-shaped, by 2 if the distribution exponentially normal and by  $\sqrt{3}$  if the distribution is rectangular.
+  - d) Multiplying the standard uncertainty by the sensitivity coefficient  $c_i$ .
+- 3) Convert the units into decibel, if necessary.
+- 4) Combine all the standard uncertainties by the Root of the Sum of the Squares (RSS) method.
+- 5) Combine the uncertainties in Stage 1 and Stage 2 into the combined uncertainty  $u_c$  also by the RSS method:
+$$u_c = \sqrt{u_{c,DUT\ measurement}^2 + u_{c,calibrate\ measurement}^2}$$
+- 6) Multiply the result of the combined uncertainty  $u_c$  by an expansion factor of 1.96 to derive expanded uncertainty  $u_e$  at 95 % confidence level:
+
+$$u_e = 1.96 u_c$$
+
+- 7) For *TRP requirements* where multiple directional measurements have been taken add the *TRP summation error (SE)* to the combined uncertainty  $u_c$  using RSS method.
+
+The above procedure calls for forming a list of uncertainty contributors in step 1, followed by an assessment of each in the following steps. This process traditionally results in 2 tables, e.g. as captured in the legacy technical reports in. The 1<sup>st</sup> table consisting of an uncertainty budget with a list of contributors, their associated UID and reference to a full description. The 2<sup>nd</sup> table carrying out the uncertainty assessment of uncertainty contributions listed in the 1<sup>st</sup> table.
+
+In this report there are many tables so to keep the document manageable the full documentation method is used just for a single requirement type (i.e. EIRP accuracy, Normal test conditions in clause 9.2) in order to demonstrate the process for all considered chamber types. For the all the remaining requirements the same process is followed and the data in the 2 tables is merged into a single one (e.g. as in table 9.3.2.3-1) in order to save space in the report. In the merged table the UID column contains the annex where the uncertainty contributor description is given.
+
+
+
+## 6 Measurement types
+
+### 6.1 Spatial definitions
+
+Spatial definitions for classification of the OTA requirements were introduced below. OTA transmitter requirements can be split into either:
+
+1. Directional requirements: The BS manufacturer declares beam(s) and coverage ranges over which the beam can be steered. Directional requirement type does not imply the requirement is defined only in one direction as many directional requirements have a number of compliance directions. It implies that the directional requirement applies to a single direction at a time.
+2. *TRP requirements*: TRP is a requirement, which is defined as the total power radiated by the BS in all radiation space.
+3. Co-location requirements: Co-location requirements are based on assumption that the BS is co-located with another BS of the same base station class. Co-location requirements ensure that both co-located systems can operate with minimal degradation to each other.
+
+NOTE: Co-location requirements are only applicable in FR1, i.e. for OTA AAS BS, or for *BS type 1-O*.
+
+### 6.2 Directional measurements
+
+#### 6.2.1 General
+
+The test requirements of the BS directional requirements may be placed on one or more manufacturer declared beam(s) that are intended for cell-wide coverage.
+
+Some example directional requirements are defined with respect to an isotropic antenna in terms of EIRP and EIS. EIS is related to the power density of a plane wave incident on the BS when the power level in the receiver is at the sensitivity level.
+
+#### 6.2.2 Beam parameter definitions
+
+A beam (of the antenna) is the main lobe of the *radiation pattern* of an *antenna array* of the BS. A beam is created by means of a superposition of the signals radiated from different parts of the *antenna array*.
+
+Each *beam direction pair* is associated with half-power contour of the *beam centre direction* and a *beam peak direction*. The EIRP is declared at the *beam peak direction*. The *beam centre direction* is used for describing beam steering.
+
+![Figure 6.2.2-1: Example of beam direction pair. The figure contains two sub-diagrams. The left sub-diagram shows a symmetrical beam profile with a single peak labeled 'EIRP peak'. A vertical dashed line extends from this peak to a horizontal axis labeled 'direction'. Below the axis, an arrow points to this line with the text 'Beam centre direction And Beam peak direction'. The right sub-diagram shows a beam profile with a ripple, featuring two peaks. The higher peak is labeled 'EIRP peak'. A vertical dashed line from this peak points to the horizontal axis, with an arrow below it labeled 'Beam peak direction'. Another vertical dashed line from the lower peak points to the horizontal axis, with an arrow below it labeled 'Beam centre direction'.](853ef5420f0432e626e83987e3f38a0b_img.jpg)
+
+Figure 6.2.2-1: Example of beam direction pair. The figure contains two sub-diagrams. The left sub-diagram shows a symmetrical beam profile with a single peak labeled 'EIRP peak'. A vertical dashed line extends from this peak to a horizontal axis labeled 'direction'. Below the axis, an arrow points to this line with the text 'Beam centre direction And Beam peak direction'. The right sub-diagram shows a beam profile with a ripple, featuring two peaks. The higher peak is labeled 'EIRP peak'. A vertical dashed line from this peak points to the horizontal axis, with an arrow below it labeled 'Beam peak direction'. Another vertical dashed line from the lower peak points to the horizontal axis, with an arrow below it labeled 'Beam centre direction'.
+
+**Figure 6.2.2-1: Example of beam direction pair**
+
+In figure 6.2.2-1 left sub-figure shows a symmetrical beam where *beam centre direction* and *beam peak direction* are the same. In figure 6.2.2-1 right sub-figure shows an example of a beam with ripple where the *beam centre direction* and the *beam peak direction* are different.
+
+The number of declared BS beams is for the manufacturer to declare. Some examples of declarations of beams are illustrated in a *directions diagram* in figure 6.2.2-2.
+
+![Figure 6.2.2-2: Examples of BS beam declarations depicted in a directions diagram. The figure shows four quadrants of a coordinate system. Top-left: Red '+' symbols are placed at specific points on the axes and in the quadrants, representing discrete declared directions. Top-right: A shaded blue area covers a continuous region in the bottom-right quadrant, with red '+' symbols at specific points. Bottom-left: A dense grid of blue dots covers a continuous region in the bottom-right quadrant, with red '+' symbols at specific points. Bottom-right: Red '+' symbols are placed at specific points, with a horizontal blue line segment connecting two points on the negative x-axis and a vertical blue line segment connecting two points on the negative y-axis.](5e16d3613b74558acc74ff6d7fd75fa9_img.jpg)
+
+Figure 6.2.2-2: Examples of BS beam declarations depicted in a directions diagram. The figure shows four quadrants of a coordinate system. Top-left: Red '+' symbols are placed at specific points on the axes and in the quadrants, representing discrete declared directions. Top-right: A shaded blue area covers a continuous region in the bottom-right quadrant, with red '+' symbols at specific points. Bottom-left: A dense grid of blue dots covers a continuous region in the bottom-right quadrant, with red '+' symbols at specific points. Bottom-right: Red '+' symbols are placed at specific points, with a horizontal blue line segment connecting two points on the negative x-axis and a vertical blue line segment connecting two points on the negative y-axis.
+
+**Figure 6.2.2-2: Examples of BS beam declarations depicted in a directions diagram**
+
+In figure 6.2.2-2 the shaded areas/points represent the declared EIRP directions set, which may be continuous (top right, bottom right) or not continuous (bottom left), or be restricted to just the points of maximum steering (top left). The red coloured points represent the compliance test points at which EIRP is declared. The maximum EIRP and its accuracy are defined for the declared beams when activated individually on all corresponding RE and the requirements are placed per individual beam.
+
+The maximum radiated transmit power of the BS beam is the mean power level measured at the declared *beam peak direction* at the RF channels B (bottom), M (middle) and T (top) when configured for maximum EIRP value for a specific BS beam of the supported frequency channels declared by the manufacturer.
+
+Another form of directional measurement is the *OTA sensitivity directions declaration(s)* (OSDD) used for the receiver directional requirements. OSDD is declared for OTA sensitivity requirement and described in more details in clause 6.2.3.
+
+### 6.2.3 OSDD
+
+If an OSDD does not include a *receiver target redirection range*, conformance testing is performed for the following five directions, as depicted in the example in figure 6.2.3-1:
+
+- The *receiver target reference direction*.
+- The direction determined by the maximum  $\phi$  value achievable inside the *sensitivity RoAoA* maintaining the *receiver target reference direction*  $\Theta$  value.
+- The direction determined by the minimum  $\phi$  value achievable inside the *sensitivity RoAoA* maintaining the *receiver target reference direction*  $\Theta$  value.
+- The direction determined by the maximum  $\Theta$  value achievable inside the *sensitivity RoAoA* maintaining the *receiver target reference direction*  $\phi$  value.
+- The direction determined by the minimum  $\Theta$  value achievable inside the *sensitivity RoAoA* maintaining the *receiver target reference direction*  $\phi$  value.
+
+The manufacturer declares the five directions for conformance testing.
+
+![Figure 6.2.3-1: OSDD without target redirection capability. A 2D coordinate system with a horizontal axis labeled phi (ranging from -20° to 20°) and a vertical axis labeled Theta (ranging from -10° to 10°). A green shaded elliptical region represents the sensitivity RoAoA. Five red crosses mark the testing directions: one at the center (0°, 0°), two on the horizontal axis at the extreme edges of the ellipse, and two on the vertical axis at the extreme edges of the ellipse.](db2f2503931949e0258f7f10eba14eb5_img.jpg)
+
+Figure 6.2.3-1: OSDD without target redirection capability. A 2D coordinate system with a horizontal axis labeled phi (ranging from -20° to 20°) and a vertical axis labeled Theta (ranging from -10° to 10°). A green shaded elliptical region represents the sensitivity RoAoA. Five red crosses mark the testing directions: one at the center (0°, 0°), two on the horizontal axis at the extreme edges of the ellipse, and two on the vertical axis at the extreme edges of the ellipse.
+
+**Figure 6.2.3-1: OSDD without target redirection capability**
+
+In figure 6.2.3-1 a direction diagram shows a RoAoA without *receiver target redirection capability*. The *receiver target reference direction* and the extreme directions subject to conformance testing are marked by red crosses.
+
+If an OSDD includes a *receiver target redirection range*, conformance testing is performed for the following five directions, as depicted in the example in figure 6.2.3-2:
+
+- The *receiver target reference direction*.
+- The direction determined by the maximum  $\phi$  value achievable inside the *receiver target redirection range* maintaining the *receiver target reference direction*  $\Theta$  value.
+- The direction determined by the minimum  $\phi$  value achievable inside the *receiver target redirection range* maintaining the *receiver target reference direction*  $\Theta$  value.
+- The direction determined by the maximum  $\Theta$  value achievable inside the *receiver target redirection range* maintaining the *receiver target reference direction*  $\phi$  value.
+
+- The direction determined by the minimum  $\Theta$  value achievable inside the *receiver target redirection range* maintaining the *receiver target reference direction*  $\phi$  value.
+
+The manufacturer declares the five directions for conformance testing, the setting of the BS to achieve conformance at each of the conformance test directions, and the resulting *sensitivity RoAoA* for each of these settings.
+
+![Figure 6.2.3-2: OSDD with target redirection capability. A polar plot showing the receiver target redirection range and sensitivity RoAoA for an AAS BS. The horizontal axis is labeled Φ (0° to 20°) and the vertical axis is labeled Θ (-10° to 10°). A large green shaded area represents the receiver target redirection range. Within this area, five smaller green shaded regions represent the sensitivity RoAoA for different conformance test settings. Red crosses mark the receiver target reference direction and the extreme directions subject to conformance testing. Labels indicate the orientation of the coordinate system, instances of multiple possible receiver targets, and one of four maximum steering directions.](d94a0100320109c1b9cd75c1054c7b95_img.jpg)
+
+instances of five *sensitivity RoAoA* declared for conformance testing in case of AAS BS with declared *receiver target redirection range*
+
+*receiver target reference direction* for declared OSDD#n e.g. ( $5^\circ$  ,  $-5^\circ$  )
+
+$-10^\circ$
+
+$-20^\circ$
+
+$20^\circ$
+
+$\Phi$
+
+instances of multiple possible *receiver targets*
+
+one of four maximum steering directions
+
+$10^\circ$
+
+*receiver target redirection range* for OSDD#n, declared wrt. the *receiver target reference direction*
+
+$\Theta$
+
+*sensitivity RoAoA #n*
+
+*sensitivity RoAoA #n+1*
+
+orientation of the coordinate system as subject to the AAS BS declaration
+
+Figure 6.2.3-2: OSDD with target redirection capability. A polar plot showing the receiver target redirection range and sensitivity RoAoA for an AAS BS. The horizontal axis is labeled Φ (0° to 20°) and the vertical axis is labeled Θ (-10° to 10°). A large green shaded area represents the receiver target redirection range. Within this area, five smaller green shaded regions represent the sensitivity RoAoA for different conformance test settings. Red crosses mark the receiver target reference direction and the extreme directions subject to conformance testing. Labels indicate the orientation of the coordinate system, instances of multiple possible receiver targets, and one of four maximum steering directions.
+
+**Figure 6.2.3-2: OSDD with target redirection capability**
+
+In figure 6.2.3-2, a direction diagram is showing a *receiver target redirection range* (with discrete settings for the *sensitivity RoAoA*). The *receiver target reference direction* and the extreme directions subject to conformance testing are marked by red crosses. The *sensitivity RoAoA* for each conformance test setting is shown as shaded. Note that each *sensitivity RoAoA* is exceptionally small compared to the *receiver target redirection range*, for demonstration purposes.
+
+## 6.3 TRP measurement
+
+### 6.3.1 General
+
+The TRP or the radiated power is the total power radiated by a BS. Due to energy conservation, TRP is independent of the choice of test distance.
+
+$TRP_{Reference}$  is defined as the integral of the BS's far field *radiation pattern* over a spherical surface
+
+where  $U(\theta, \phi)$  is the radiation intensity at each angle in watts per Steradian.
+
+In the far field, the radiation intensity can be also expressed in terms of power flux density
+
+Where:
+
+the time average of the Poynting vector (average power density) or the power flux of the electromagnetic field, where  $E$  and  $H$  are effective values of the time-harmonic electric- and magnetic-field intensities, respectively. Furthermore,  $\text{Re}$  denotes real part,  $\text{Re}^*$  denotes the complex conjugate of  $\text{Re}$  and  $\times$  is vector cross product.
+
+average power density in watts per square metre, which is a scalar.
+
+unit vector normal to the closed surface .
+
+infinitesimal area of the closed surface.
+
+For practical reasons, a sphere of radius  $r$  is a common choice for the closed surface, but also other surfaces can be considered e.g. cylinder and planar surface. The spherical coordinate system defined in clause 4 is assumed.
+
+In the far field limit (i.e. ), the  $E$  and  $H$  fields consist of the tangential components ( $E_\theta$  and  $H_\phi$ ), respectively) and the radial components ( $E_r$  and  $H_r$ ) are negligible, and, therefore, , where  $Z_0$  is the intrinsic impedance of vacuum. Thus, the TRP equation becomes
+
+where .
+
+The radiation intensity in the far field region in watts per Steradian is
+
+The power density can be expressed in terms of EIRP as
+
+and when  $r$  is large, radiation intensity is proportional to  $1/r^2$  hence in the far field region  $P_d \sim 1/r^2$  and  $P_d$  multiplied with  $r^2$  becomes roughly constant value. Thus the radiation intensity equation can be defined as
+
+Thus, the definite integral for  $\text{TRP}_{\text{Reference}}$  can be also expressed as
+
+EIRP is defined only in the far- field. However, in some occasions the power measurements can be performed at distances less than  $2d^2/\lambda$  (i.e. the traditional approximate far-field distance boundary). In such cases it is may be possible to measure power density in the radiative near- field considering only the magnitude of the tangential part of E field (i.e. ) with an acceptable level of accuracy as demonstrated in [10], where it is presented that the TRP is well approximated by the integral of over the same sphere assuming far field conditions. Thus  $\text{TRP}_{\text{Reference}}$  can be expressed as
+
+As mentioned, for near-field measurements use the approximation where  $Z_0$  (intrinsic impedance of vacuum).
+
+The minimum distance between the measurement antenna and the smallest sphere enclosing the BS must be at least  $2\lambda$  and the test distance must be at least the far-field distance of the measurement antenna when considering the TRP measurements under far field conditions. More details about the necessary conditions for accurate power density-based measurements close to BS are included in annex F.
+
+When measuring radiated power, at each measurement point, two partial results for two orthogonal polarizations needs to be summed. These can be the  $\theta$  and  $\phi$  polarizations or any pair of orthogonal polarizations.
+
+The distribution of sampling points on the spherical surface depends on the type of sampling grids applied, the frequency and the size of the radiating source. In the following clauses, several spherical sampling grids which can be applied to EIRP or power density measurements are described.
+
+## 6.3.2 TRP measurement procedures
+
+### 6.3.2.1 General
+
+Different procedures can be used to evaluate the TRP estimate. These procedures can provide either an *accurate* assessment or a controlled *overestimate* of the TRP. The choice of methods is based also on the available test setup, measurement equipment, and the measurement time. This clause describes the methods which are suitable for each type of requirements. Other relevant methods are not precluded. For each method, the test purpose (accurate or overestimate) is pointed out. A summary of TRP measurement procedures and their applicability to different OTA BS requirements is shown in table 6.3.2.1-1.
+
+In the following clauses the measurement procedures for different parameters are described under the assumption of equal angle sampling. Similar procedures can be also used with other types of spherical grids, given that the proper reference steps and are determined.
+
+NOTE: OTA FR2 transmit ON/OFF power is excluded from the table although the core requirement is specified as TRP because conformance is verified through EIRP measurements.
+
+**Table 6.3.2.1-1: Applicability of TRP measurement methods and chambers to the type of emissions to be measured**
+
+|                                         |                                                                                                                                                                                                                          | BS output power | Unwanted emissions: ACLR (Note 1) | Unwanted emissions: SEM, OBUE | Spurious emissions (Note 7) |
+|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------|-------------------------------|-----------------------------|
+| Methods applicable to anechoic chambers | Full sphere using reference steps (accurate)                                                                                                                                                                             | X               | X                                 | X                             | X (Note 2)                  |
+|                                         | Full sphere using sparse sampling (overestimate)                                                                                                                                                                         |                 |                                   |                               | X (Note 2, 3)               |
+|                                         | Two cuts + Pattern multiplication (accurate) (Note 4)                                                                                                                                                                    | X               | X                                 | X                             |                             |
+|                                         | Two/three cuts (overestimate)                                                                                                                                                                                            |                 | X                                 | X                             | X (Note 2, 3)               |
+|                                         | Beam-based directions                                                                                                                                                                                                    | X               | X (Note 5)                        | X (Note 5)                    |                             |
+|                                         | Peak method                                                                                                                                                                                                              |                 |                                   | X                             | X (Note 2)                  |
+|                                         | Equal sector with peak average                                                                                                                                                                                           |                 |                                   | X                             | X (Note 2)                  |
+|                                         | Pre-scan (Note 2)                                                                                                                                                                                                        |                 | X                                 | X                             | X                           |
+| Reverberation chamber                   |                                                                                                                                                                                                                          | X               | X                                 | X                             | X (Note 2)                  |
+| Note 1:                                 | Two TRP measurements are needed.                                                                                                                                                                                         |                 |                                   |                               |                             |
+| Note 2:                                 | Pre-scan is needed to identify the frequencies of interest. Pre-scan can also be applied to ACLR, OBUE and SEM.                                                                                                          |                 |                                   |                               |                             |
+| Note 3:                                 | At harmonic frequencies the use of this method is not applicable.                                                                                                                                                        |                 |                                   |                               |                             |
+| Note 4:                                 | Pattern multiplication is conditional.                                                                                                                                                                                   |                 |                                   |                               |                             |
+| Note 5:                                 | Applicable if the directivity of corresponding requirement at the reference direction is equivalent to the directivity at the reference direction when BS emits $P_{\text{rated,c,TRP}}$ and $P_{\text{rated,c,EIRP}}$ . |                 |                                   |                               |                             |
+| Note 6:                                 | If box is blank the method is not excluded but the methodology has not been described in clause 6.3.3 on angular alignment in TRP measurements; if a suitable analysis is shown the method may be applied.               |                 |                                   |                               |                             |
+| Note 7:                                 | Applicability of any chamber for the spurious emissions measurements is subject to the supported frequency range of the chamber, and specifically its upper frequency limit.                                             |                 |                                   |                               |                             |
+
+The *TRP summation error* is based on a reasonable number of test directions, for the reference steps please see figure 6.3.4.2-1. These steps depend on antenna size and frequency and correspond to the minimum beam width. It has been agreed that a reasonable trade-off between accuracy and sampling is achieved when the SE is 0.75 dB for FR1 and 1.2 dB for FR2. For FR2, the beams are expected to be narrower than an FR1 and hence the SE is higher. For the SE derivation, refer to clause 6.3.6.
+
+### 6.3.2.2 Procedures for BS output power
+
+#### 6.3.2.2.1 General
+
+**Test purpose:** Accurate TRP assessment.
+
+The radiation source is assumed to be limited to the antennas on the BS and it's not necessary to take the dimensions of the whole BS into account for calculations of the far-field distance and the reference angular resolution. The test choices are as follows.
+
+#### 6.3.2.2.2 Two cuts with pattern multiplication
+
+Use this method when the antenna symmetries are compatible with pattern multiplication, see clause 6.3.4.5 (orthogonal cuts grids). Following steps are performed during the measurement:
+
+1. Calculate the reference angular steps as described in clause 6.3.4.2 (reference angular step criteria).
+2. Align the BS to allow for proper pattern multiplication. Measure EIRP on two orthogonal cuts with steps smaller or equal to the reference steps according to step 1.
+3. Apply pattern multiplication to extrapolate the two cuts data to full-sphere.
+4. Apply numerical integration to obtain the  $\text{TRP}_{\text{Estimate}}$ .
+
+#### 6.3.2.2.3 Full sphere
+
+Following steps are performed during the measurement:
+
+1. Calculate the reference angular steps as described in clause 6.3.4.2 (reference angular step criteria). Other methods for determining the required angular steps are not precluded.
+2. Choose the angular steps smaller than or equal to the reference angular steps.
+3. Measure EIRP values on a spherical grid according to clause 6.3.4.1 (spherical equal angle grids). Having the poles of the measurement grid along the direction of the main beam shall be avoided.
+
+NOTE: Spherical grids of clause 6.3.4.3 (spherical equal area grids), clause 6.3.4.4 (spherical Fibonacci grids) and clause 6.3.4.6 (wave vector space sampling grids) can also be used with proper angular steps.
+
+4. Apply suitable numerical integration to calculate the  $\text{TRP}_{\text{Estimate}}$ .
+
+#### 6.3.2.2.4 Beam-based directions
+
+This method is only applicable if directivity of BS antenna is known for the operating frequency. The peak EIRP of a beam is measured at the *beam peak direction* within the *beam direction pair*. Following the same approach, the peak EIRP of a beam can be obtained, which is used to derive  $\text{TRP}_{\text{Estimate}}$  using directivity of BS antenna as follows:
+
+, where  $D_{\text{BS}}$  is the directivity of BS.
+
+For the case of OTA BS output power, the directivity ( $D_{\text{BSOutputpower}}$ ) shall be defined as:
+
+### 6.3.2.3 Procedures for SEM and OBUE
+
+#### 6.3.2.3.1 General
+
+**Test purpose:** Accurate or controlled overestimate of TRP.
+
+The radiation source is limited to the antennas on the BS and it's not necessary to take the dimension of the whole BS into account for calculations of the far-field distance and the reference angular steps. The test choices are as follows.
+
+#### 6.3.2.3.2 Two cuts with pattern multiplication
+
+Use the same procedure as in clause 6.3.2.2.2 (i.e. two cuts with pattern multiplication for BS output power).
+
+### 6.3.2.3.3 Two or three cuts
+
+Use this method when the cuts described in clause 6.3.4.5 (orthogonal cuts grids) can be identified, but the pattern multiplication is not applicable according to the requirements in clause 6.3.4.5. This method will provide an overestimated value for TRP. Following steps are performed during the measurement.
+
+1. Calculate the reference angular steps as in clause 6.3.4.2 (reference angular step criteria).
+2. Measure EIRP on two orthogonal cuts with angular steps smaller than or equal to the reference steps according to step 3. Align the BS such that the cardinal cuts are measured. See figure 6.3.4.5-1.
+3. Calculate the average EIRP in each cut and then the  $TRP_{Estimate}$  according to clause 6.3.4.5 (orthogonal cuts grids).
+4. If the TRP estimate is above the requirement limit, perform the measurement on a third cut (See figure 6.3.4.5-1) and repeat step 3.
+
+### 6.3.2.3.4 Full sphere
+
+Use the same procedure as in clause 6.3.2.2.3 for full sphere with appropriate reference steps.
+
+### 6.3.2.3.5 Beam-based directions
+
+This method only applicable if directivity of BS antenna is available for the downlink operating band plus  $\Delta f_{OBU}$  on either side of the band edge. Refer to clause 6.3.2.2.4 for more details.
+
+The pre-scan (refer to clause 6.3.2.5.2), peak (refer to clause 6.3.2.5.3) and equal sector with peak average methods (refer to clause 6.3.2.5.4) are possible options.
+
+## 6.3.2.4 Procedures for ACLR
+
+### 6.3.2.4.1 General
+
+**Test purpose:** Accurate or controlled underestimate of ACLR.
+
+The methods described in this clause are used for assessment of the TRP values for ACLR. Depending on the method, the result can be accurate or a controlled underestimate of the ACLR. The latter applies if the TRP of the radiation in the adjacent band is overestimated. The radiation source is limited to the antennas on the BS and it's not necessary to take the dimension of the whole BS into account for calculations of the far-field distance and the reference angular steps.
+
+### 6.3.2.4.2 TRP fraction method
+
+Following steps are performed during the measurement.
+
+1. For the TRP of the desired signal  $TRP_d$  use a suitable method from clause 6.3.2.2.
+2. For the TRP of the emission  $TRP_e$  use a method from clause 6.3.2.3.
+3. Evaluate the .
+
+## 6.3.2.5 Procedures for transmitter spurious emissions and EMC emissions
+
+### 6.3.2.5.1 General
+
+Test purpose of the procedures addressed in this clause is to measure accurate or controlled overestimate of TRP.
+
+The methods described in this clause are used for assessment of the TRP for spurious emissions. The methods are given in a sequence with increasing accuracy, but also increasing measurement time. There is no mandatory order, in which to use these methods nor all of the methods should be used for evaluating TRP. Some of these methods can be skipped if they are deemed not necessary, for instance, the pre-scan and peak methods.
+
+The radiation source is not limited to the antennas on the BS instead the entire physical dimensions of the BS must be taken into account for calculations of the reference angular steps, see clause 6.3.4.2 (reference angular step criteria). Note that full-sphere sampling using reference angular steps is the only method that aims to provide an accurate TRP.
+
+When available, using a beam sweeping test signal with these methods can reduce the test time and improve the uncertainty.
+
+NOTE: As name of this clause captures both transmitter spurious emissions and EMC emissions, it shall be clarified that in case of radiated measurements of OTA AAS BS, *BS type 1-O* or *BS type 2-O*, the RF radiated spurious emissions includes the EMC radiated emissions, as RF radiated spurious emissions and EMC radiated emissions cannot be distinguished in the OTA measurement setup.
+
+#### 6.3.2.5.2 Pre-scan
+
+Pre-scan is a fast measurement method, which is performed over the entire spurious frequency range to identify spurious frequencies with emission power levels above a threshold. Note, it is not necessary to do pre-scan before executing the test methods in this clause, but it is recommended. It is also not meant to provide an estimate of TRP. Hence, other relevant test methods should be used for TRP estimation.
+
+1. The distance can be shorter than the intended measurement distance between BS and the test antenna for evaluating TRP but should remain fixed throughout the scanning process.
+2. Scan the surface around the BS.
+3. Rotate the measurement antenna to cover all polarizations of emissions to detect the maximum emission.
+4. Record the list of spurious emission frequencies and corresponding power levels, spatial positions of BS and test antenna polarization where the maximum power levels occurred.
+5. For spurious frequencies with emission power levels more than 20 dB below the specified limit in then these spurious frequencies are considered compliant and no further measurements are required.
+6. For all the other spurious frequencies that do not meet the criterion in step 5, further measurements are required.
+
+#### 6.3.2.5.3 Peak method
+
+This method is applicable when the pre-scan method indicates the presence of emission peaks. The peak method can be skipped if there exist no emission peaks. Further, the method does not provide a TRP estimate instead the highest absolute EIRP is measured at each spurious frequency identified in the pre-scan. If the absolute EIRP meets the specified TRP limit, then it implies that the TRP estimate would meet the limit too. As a result, it is not needed to perform further measurement using the other methods.
+
+1. Find the direction of the peak emission EIRP or peak power density.
+2. Start with the spurious frequency that has the maximum power level recorded during pre-scan.
+3. The BS and test antenna are oriented to the same position where the maximum power level is recorded during the pre-scan.
+
+NOTE: This set-up might not be applicable if pre-scan is performed in near-field.
+
+4. BS and test antenna are moved around the position to identify and measure the peak EIRP.
+5. If the peak EIRP for a spurious frequency is less than the specified limit then no further measurements are required else use the methods below to evaluate TRP estimates.
+6. Repeat steps 4 to 6 for the next strongest emission.
+
+#### 6.3.2.5.4 Equal sector with peak average method
+
+The equal sector with peak average method can be considered as an extension to the peak method. It is performed on the list of spurious frequencies which have not met the limit using the peak method. The method takes into account several peak EIRPs of beams belonging to different sectors of the sphere.  $TRP_{Estimate}$  is calculated as the average of the peak EIRP in different sectors.
+
+1. The measurement distance is in the far field.
+2. The sphere is divided into  $K$  equal sectors. The total number of sectors depend on the dimensions of BS. If the largest dimension is less than 60 cm, then each sector is a half quadrant of  $45^\circ$ . Other techniques for determining the sector size are not precluded such as using the angular step.
+3. For those spurious frequencies which need further measurements by the peak method, start with the spurious frequency that has the highest recorded power level.
+4. Perform steps 4 and 5 as in the peak method (see clause 6.3.2.5.3).
+5. Move to the next sector with next higher emissions recorded and repeat step 4 until all sectors are covered.
+6. Calculate TRP estimate as  $TRP_{Estimate} = \frac{1}{K} \sum_{k=1}^K EIRP_k$ , where  $EIRP_k = EIRP_{k,p1} + EIRP_{k,p2}$  is in linear units.
+7. Repeat steps 4 and 5 for at least 7 spurious frequencies with the next higher emission in descending order.
+8. If TRP estimate for each of the 8 spurious frequencies is less than the specified limit then no further measurements are required else use the other methods to evaluate TRP estimates.
+
+#### 6.3.2.5.5 Two or three cuts with dense sampling
+
+Following sequence can be used:
+
+1. Follow steps described in clause 6.3.2.3.3 and calculate the  $TRP_{Estimate}$ . Note that no alignment is needed for spurious emissions.
+2. Add the appropriate correction factor  $\Delta TRP$  according to table 6.3.2.5.5-1 to ensure overestimation with 95% confidence.
+3. Compare the  $(TRP_{Estimate} + \Delta TRP)$  to the limit.
+4. If the  $(TRP_{Estimate} + \Delta TRP)$  is above the limit, perform the measurement on an additional third cut (see figure 6.3.4.5-1) and repeat steps 1 to 3.
+
+**Table 6.3.2.5.5-1: The correction factor for two or three cuts dense sampling**
+
+|                                     | Three cuts | Two cuts |
+|-------------------------------------|------------|----------|
+| Correction factor $\Delta TRP$ (dB) | 2.0        | 2.5      |
+
+#### 6.3.2.5.6 Full sphere with sparse sampling
+
+Sparse angular sampling with a correction factor can be used to save measurement time. The only difference is in the used angular steps. Following sequence can be used:
+
+1. Set the angular grid:
+  - a. Non-harmonic frequencies: choose the angular steps  $\Delta\theta$  and  $\Delta\phi$  smaller than or equal to  $15^\circ$ . Calculate the sparsity factor (SF) as:
+
+and the correction factor as:
+
+- b. where  $\Delta\theta$  corresponds to  $15^\circ$  angular step. If the sparsity factor is smaller than 1, the correction factor  $\Delta TRP$  is 0 dB. Harmonic frequencies with fixed beam test signal: choose the angular steps smaller than or equal to the reference angular steps  $\Delta\theta_{ref}$  and  $\Delta\phi_{ref}$ . Correction factor  $\Delta TRP$  is 0 dB.
+- c. Harmonic frequencies with beam sweeping test signal: set the angular steps to  $15^\circ$ . Correction factor is  $\Delta TRP$  0 dB.
+
+2. Measure EIRP (or power density multiplied by grid surface) on a spherical grid according to clause 10.8.2. Having the poles of the measurement grid along the direction of the main beam shall be avoided.
+
+NOTE: Other spherical grids can also be used with proper angular sampling.
+
+3. Apply a suitable numerical integration to calculate the  $TRP_{Estimate}$ .
+4. Add the appropriate correction factor  $\Delta TRP$  according to step 1 to ensure an overestimation with 95% confidence.
+5. Compare the  $(TRP_{Estimate} + \Delta TRP)$  with the limit. If the  $(TRP_{Estimate} + \Delta TRP)$  is above the limit, choose a smaller angular step and repeat steps 2 - 4. If the sparsity factor is less than one, no significant improvement of accuracy is expected.
+
+#### 6.3.2.5.7 Full sphere
+
+Use the same procedure as in clause 6.3.2.2.3 for full sphere with appropriate reference steps.
+
+### 6.3.3 Angular alignment in TRP measurements
+
+For the TRP test methods relying on finding EIRP peak measurements, guidance on how to find the peak with acceptable accuracy is required.
+
+The following test methods relies on finding peak EIRP:
+
+1. Beam-based direction (clause 6.3.2.2.4)
+2. Orthogonal cut grid (clause 6.3.4.5)
+3. Peak method (clause 6.3.2.5.3)
+4. Equal sector with peak average method (clause 6.3.2.5.4)
+
+For the above procedures, measuring maximum EIRP accurately is critical to the accuracy of TRP estimates. If the maximum value is not accurately sampled, this will result in measurement errors. In the worst case, the measurement error is larger than the MU, which is not acceptable. The measurement error is caused by angular misalignment which is the difference (in degrees) between the actual and the measured angular positions of the intended maximum EIRP. Figure 6.3.3-1 shows an example of angular misalignment, where the measured EIRP is at an angle equal to  $-2^\circ$  while the actual angular position of the maximum EIRP is at  $0^\circ$  in the *radiation pattern*. This results in an absolute measurement error  $\approx 1$  dB.
+
+![Figure 6.3.3-1: Angular misalignment. A graph showing Normalised Power (dB) on the y-axis (from -7 to 0) versus Angle (degrees) on the x-axis (from -8 to 8). A blue curve represents the radiation pattern. A red dot at 0 degrees is labeled 'Intended EIRP (maximum)'. Another red dot at -2 degrees is labeled 'Measured EIRP' with an arrow pointing to it. The measured EIRP is lower than the intended EIRP due to angular misalignment.](eed9c8ade8af628fdab5135da476beb7_img.jpg)
+
+Figure 6.3.3-1: Angular misalignment. A graph showing Normalised Power (dB) on the y-axis (from -7 to 0) versus Angle (degrees) on the x-axis (from -8 to 8). A blue curve represents the radiation pattern. A red dot at 0 degrees is labeled 'Intended EIRP (maximum)'. Another red dot at -2 degrees is labeled 'Measured EIRP' with an arrow pointing to it. The measured EIRP is lower than the intended EIRP due to angular misalignment.
+
+**Figure 6.3.3-1: Angular misalignment**
+
+If the actual angular position of maximum EIRP is known (e.g., declared by manufacturers), measurement errors due to angular misalignment can be alleviated. However, if the actual angular position of maximum EIRP is not known, then
+
+the angular interval used in searching for the maximum EIRP employing the peak search method can contribute to the measurement errors due to angular misalignment. The search is performed in the proximity of the expected angular position of maximum EIRP (e.g., a broadside *radiation pattern*). To determine the magnitude of the measurement error caused by angular misalignment, the angular step size can be expressed in terms of half-power beam width (HPBW) of test beams. If the angular step size is set to HPBW, the absolute measurement error can be as large as 3 dB. Table 6.3.3-1 summarizes the maximum absolute measurement error versus different angular step sizes. The absolute measurement errors were derived assuming a linear approximation between the maximum EIRP and the 2 HPBW points as illustrated in figure 6.3.3-2. The linear approximation gives us the worst-case scenario as can be observed in figure 6.3.3-2.
+
+![Figure 6.3.3-2: Linear approximation of measurement errors. The graph plots Normalized Power (dB) on the y-axis from -7 to 0 against Angle (degrees) on the x-axis from -8 to 8. A blue parabolic-like curve represents the actual radiation pattern, peaking at (0, 0). A red dot marks this peak. A horizontal line at -3 dB represents the HPBW level, intersecting the curve at approximately -4 and 4 degrees. A black triangle formed by straight lines connects the peak (0,0) to these two intersection points on the -3 dB line, illustrating the linear approximation. Labels include 'HPBW/2' for the angular distance from the peak to the half-power point and 'HPBW' for the full width at the -3 dB level.](8d5d12ba8fe7313bc891241275c64d20_img.jpg)
+
+Figure 6.3.3-2: Linear approximation of measurement errors. The graph plots Normalized Power (dB) on the y-axis from -7 to 0 against Angle (degrees) on the x-axis from -8 to 8. A blue parabolic-like curve represents the actual radiation pattern, peaking at (0, 0). A red dot marks this peak. A horizontal line at -3 dB represents the HPBW level, intersecting the curve at approximately -4 and 4 degrees. A black triangle formed by straight lines connects the peak (0,0) to these two intersection points on the -3 dB line, illustrating the linear approximation. Labels include 'HPBW/2' for the angular distance from the peak to the half-power point and 'HPBW' for the full width at the -3 dB level.
+
+**Figure 6.3.3-2: Linear approximation of measurement errors**
+
+**Table 6.3.3-1: Sampling beam peak error due to misalignment error**
+
+| Angular misalignment | Beam peak misalignment error (dB) |
+|----------------------|-----------------------------------|
+| HPBW                 | 3                                 |
+|                      | 1.5                               |
+|                      | 1                                 |
+|                      | 0.75                              |
+
+Based on the measurement error in table 6.3.3-1, the measurement error should be within the *TRP summation error* to ensure the angular misalignment is not greater than (for  $f \leq 3$  GHz and  $3 \text{ GHz} < f \leq 6$  GHz), and (for  $24.25 < f \leq 29.5$  GHz and  $37 < f \leq 43.5$  GHz). Note, there is a trade-off between search time and angular misalignment (that is, the difference in actual and measured angular positions of intended peak EIRP). Larger misalignment for FR2 is reasonable since FR2 beams are in general narrower than FR1.
+
+For the orthogonal cut procedure in clauses 6.3.2.2.2 and 6.3.2.3.2 (i.e. two cuts with pattern multiplication), angular step size smaller than the reference angular step may be desired as outlined in step 2. In order to sample half power EIRP in addition to the maximum EIRP, the angular step size may be set to  $\text{HPBW}/2$ , where HPBW is the half-power beam width of the frequency under measurement.
+
+## 6.3.4 TRP measurement grids
+
+### 6.3.4.1 Spherical equal angle grid
+
+With the spherical equal angle grid, the grid spacing is uniform in  $\theta$  and  $\phi$  directions. The range of  $\theta$  angles from 0 to  $\pi$  is divided into equally spaced subintervals and the range of  $\phi$  angles from 0 to  $2\pi$  is divided into equally spaced subintervals. The width of each subinterval in the  $\theta$ - and  $\phi$ -angle is given as:
+
+and
+
+The total number of angular sampling points is equal to .
+
+Let  $n$  and  $m$  be the indices used to denote the  $n^{\text{th}}$  and  $m^{\text{th}}$  angles, respectively. In practice, discrete samples of EIRP are measured at each sample point  $(n, m)$  by measuring its two orthogonally polarized components,  $E_{\theta}$  and  $E_{\phi}$ . The EIRP sample are then used to approximate the definite integral for  $\text{TRP}_{\text{Reference}}$  as the discrete average sum of EIRP measured at different  $n$  and  $m$  angles.
+
+The above equation can be simplified considering  $\Delta\phi = \Delta\theta = 0$ . Thus the total number of angular sampling points is equal to  $(N - 1)M$ .
+
+NOTE:  $\text{TRP}_{\text{Estimate}} = \text{TRP}_{\text{Reference}}$  as  $\Delta\phi$  and  $\Delta\theta$  approach 0.
+
+There is a trade-off between the accuracy of the  $\text{TRP}_{\text{Estimate}}$  and the total number of sampling points. A large number of sampling points leads to long measurement time. Thus, it is important to achieve short measurement time and fulfilling the minimum *TRP summation error*. Clause 6.3.4.2 (i.e. reference angular step criteria) outlines the criteria for determining the minimum number of sampling points to characterize. Other means for set the number of sampling points are not precluded.
+
+One observation is that the equal angle grid points are not uniformly distributed on the sphere surface, and many are clustered towards the poles, as shown in figure 6.3.4.1-1.
+
+![A 3D plot showing a spherical equal angle sampling grid. The grid is composed of lines of constant latitude and longitude, forming a mesh on the surface of a sphere. The points are more densely packed near the poles (top and bottom) and more sparse near the equator. The axes are labeled from -1 to 1, with intermediate ticks at -0.5 and 0.5.](c301bbb71a13e5fb2800c48e300bafb1_img.jpg)
+
+A 3D plot showing a spherical equal angle sampling grid. The grid is composed of lines of constant latitude and longitude, forming a mesh on the surface of a sphere. The points are more densely packed near the poles (top and bottom) and more sparse near the equator. The axes are labeled from -1 to 1, with intermediate ticks at -0.5 and 0.5.
+
+**Figure 6.3.4.1-1: Spherical equal angle sampling grid**
+
+### 6.3.4.2 Reference angular step criteria
+
+For each frequency, the reference angular steps  $\Delta\phi_{\text{ref}}$  and  $\Delta\theta_{\text{ref}}$  in degrees, are calculated as in [9]:
+
+$$\Delta\phi_{\text{ref}} = \min\left(\frac{180^\circ}{\pi} \frac{\lambda}{D_{\text{cyl}}}, 15^\circ\right)$$
+
+$$\Delta\theta_{\text{ref}} = \min\left(\frac{180^\circ}{\pi} \frac{\lambda}{D}, 15^\circ\right)$$
+
+where  $D$  and  $D_{cyl}$  are defined further down in this clause. This implies a maximum angular step of  $15^\circ$ . The upper limit for these reference angular steps of  $15^\circ$  ensures a low *TRP summation error* when is large compared to the BS dimensions.
+
+The reference steps can be derived as follows. Consider two short vertical current elements separated a distance  $L$  along the  $z$ -axis. The EIRP pattern of this source is
+
+Here, the element factor is  $\sin\theta$  and  $\cos(kL\cos\theta/2)$  is the *array factor* contribution. To calculate the TRP value correctly, an angular sampling of  $\Delta\theta$  is required, see figure 6.3.4.2-1. But a single  $\Delta\theta$  is enough since the pattern is  $\phi$ -independent (omni-directional).
+
+Any current flowing on a line between the points  $z = -L/2$  and  $z = L/2$  will correspond to source separations less than or equal to  $L$ . Hence its EIRP pattern will correspond to the same angular resolution, i.e., the average value will be correctly predicted using the same angular step.
+
+![Figure 6.3.4.2-1: A line graph showing Average EIRP (dB) on the y-axis (from -20 to 5) versus angular step Δθ (°) on the x-axis (from 30 to 0). Four curves represent different source separations L/λ: 4 (blue), 8 (orange), 16 (yellow), and 32 (purple). Vertical dashed lines indicate reference angular steps for each L/λ: λ/L = 1/4 (blue dashed line at Δθ ≈ 15°), 1/8 (orange dashed line at Δθ ≈ 7.5°), 1/16 (yellow dashed line at Δθ ≈ 4°), and 1/32 (purple dashed line at Δθ ≈ 2°). The graph shows that as the angular step Δθ decreases, the average EIRP for each curve converges towards a stable value, with the required step size being inversely proportional to the source separation L/λ.](94389c644d3c25d99db7bc6d87bf5779_img.jpg)
+
+Figure 6.3.4.2-1: A line graph showing Average EIRP (dB) on the y-axis (from -20 to 5) versus angular step Δθ (°) on the x-axis (from 30 to 0). Four curves represent different source separations L/λ: 4 (blue), 8 (orange), 16 (yellow), and 32 (purple). Vertical dashed lines indicate reference angular steps for each L/λ: λ/L = 1/4 (blue dashed line at Δθ ≈ 15°), 1/8 (orange dashed line at Δθ ≈ 7.5°), 1/16 (yellow dashed line at Δθ ≈ 4°), and 1/32 (purple dashed line at Δθ ≈ 2°). The graph shows that as the angular step Δθ decreases, the average EIRP for each curve converges towards a stable value, with the required step size being inversely proportional to the source separation L/λ.
+
+**Figure 6.3.4.2-1: The average EIRP when using different angular steps and the EIRP pattern of two short vertical current elements separated a distance  $L=4, 8, 12, 16$ , and  $32$  wavelengths, respectively. The dashed lines depict the reference angular step radians for the used source separations**
+
+To proceed to more general sources two observations are useful:
+
+- 1) A rotation of a source will not change the required resolution, but the resolution must be set equal to the resolution.
+- 2) If the source distribution is stretched along the  $z$ -direction, the  $\phi$ -resolution will not change.
+
+Based on these two observations and the angular resolution of the line source of length  $L$ , the following can be deduced.
+
+- 1) If the line source is tilted  $90^\circ$  down to the  $xy$ -plane, and then arbitrarily rotated around the  $z$ -axis, a flat disc of diameter  $L$  is generated. Based on observation 1, the angular resolution is  $\Delta\theta$ .
+- 2) If the disc is stretched a distance  $h$  along the  $z$ -axis (current elements are translated parallel to the  $z$ -axis), then the  $\phi$ -resolution is unchanged, whereas the vertical angular resolution increases to  $\Delta\theta$  to encompass the largest possible source separation within the cylinder.
+
+The final shape of the source enclosure is hence a cylinder of diameter  $L$  and height  $h$ , and the angular steps required to get an accurate EIRP average (TRP value) are
+
+Here,  $D$  is the diameter of the source enclosure, i.e., the diameter of the smallest sphere enclosing all radiation sources, and  $D_{\text{cyl}}$  is the diameter of the smallest  $z$ -directed circular cylinder that encloses all sources.
+
+Other methods for determining the reference angular steps are not precluded.
+
+NOTE: When sampling with the reference angular step, fine details of the *radiation pattern* are maybe not captured but the estimated TRP value is still accurate.
+
+The spherical and cylindrical diameters are calculated as:
+
+The radiation source can be the *antenna array* or even the whole BS, depending on the emissions to consider. This is further explained in clause 6.3.2.
+
+Some basic definitions and relations are given here for readability.
+
+![Figure 6.3.4.2-2: A 3D coordinate system (x, y, z) showing a rectangular radiation source with dimensions depth (d), width (w), and height (h). A red vector P points from the origin to a point on the surface of the source. The angle theta is shown between the z-axis and the vector P. The angle phi is shown in the xy-plane between the x-axis and the projection of the vector P onto the plane. Dashed lines indicate the dimensions and the spherical coordinate system.](072320147c6e0a97ea1854ac62ddfe17_img.jpg)
+
+Figure 6.3.4.2-2: A 3D coordinate system (x, y, z) showing a rectangular radiation source with dimensions depth (d), width (w), and height (h). A red vector P points from the origin to a point on the surface of the source. The angle theta is shown between the z-axis and the vector P. The angle phi is shown in the xy-plane between the x-axis and the projection of the vector P onto the plane. Dashed lines indicate the dimensions and the spherical coordinate system.
+
+**Figure 6.3.4.2-2: The dimensions of a radiation source are depth (d), width (w) and height (h)**
+
+Optionally, for the specific case of a Uniform Linear Array (ULA) system, the array spatial pattern could be defined as in the following equation.
+
+$$G_0(\theta) = \left| \frac{\sin(m\beta/2)}{m \sin(\beta/2)} \right|$$
+
+Where spatial frequency  $\beta$  is defined as following:
+
+$$\beta = (2\pi d \sin(\theta))/\lambda$$
+
+Similar to Nyquist sampling in the time domain signal, the Rayleigh resolution for spatial domain signal to avoid the aliasing can be derived as:
+
+$$\sin(m\beta/2) = 0 \quad \langle m\beta/2 = m \cdot 2\pi d \sin(\theta)/2\lambda = \pi$$
+
+where  $d$  is the separation distance between antenna elements and  $m$  is the number of antenna elements. If BS is mounted along the y-z plane as shown in figure 6.3.4.2-3, based on the above considerations on the Rayleigh resolution for spatial domain signal, then subinterval in the  $\phi$  and  $\theta$  in degrees angle is calculated as:
+
+Where  $D_y$  is length of radiating part of the BS along y-axis,  $D_z$  is length of radiated part of the BS along the z-axis and  $\lambda$  is wavelength for the measured frequency. Arcsine is in radians.
+
+![Figure 6.3.4.2-3: Spherical coordinate for OTA conformance testing of BS. The diagram shows a sphere centered at the origin of a 3D Cartesian coordinate system with x, y, and z axes. A small rectangular block representing the Base Station (BS) is located at the origin. A vector is drawn from the origin to a point on the sphere's surface. The angle between the positive z-axis and this vector is labeled theta (θ). The angle between the positive y-axis and the projection of the vector onto the y-z plane is labeled phi (φ). The projection of the vector onto the y-axis is labeled Ky, and the projection onto the z-axis is labeled Kz.](ebd9c6a5314c2d747d9326192468e9cf_img.jpg)
+
+Figure 6.3.4.2-3: Spherical coordinate for OTA conformance testing of BS. The diagram shows a sphere centered at the origin of a 3D Cartesian coordinate system with x, y, and z axes. A small rectangular block representing the Base Station (BS) is located at the origin. A vector is drawn from the origin to a point on the sphere's surface. The angle between the positive z-axis and this vector is labeled theta (θ). The angle between the positive y-axis and the projection of the vector onto the y-z plane is labeled phi (φ). The projection of the vector onto the y-axis is labeled Ky, and the projection onto the z-axis is labeled Kz.
+
+**Figure 6.3.4.2-3: Spherical coordinate for OTA conformance testing of BS**
+
+In the NR coexistence study, it was assumed that antenna configuration for wide area BS is 8x16 supporting two orthogonal polarizations. If BS mounted along y/z plane with antenna configuration 16x8 where 16 columns are assumed along the y-axis and 8 rows are assumed along the z-axis. Antenna elements are uniformly distributed with separation distance  $\lambda/2$ , therefore aperture size  $D_y \approx 8\lambda$  and  $D_z \approx 4\lambda$ . The uniform sampling in the spherical coordinate for this approach is demonstrated in the figure 6.3.4.2-4.
+
+![Figure 6.3.4.2-4: A contour plot showing uniform sampling in spherical coordinates. The horizontal axis is phi (degree) from -80 to 80, and the vertical axis is theta (degree) from 0 to 180. The plot displays a grid of red crosses representing sampling points, overlaid on a complex pattern of colored contours representing signal strength or gain. The contours are primarily green and yellow, with some blue areas at the top and bottom.](77a781dfb114c3e2b399f876f1808cfd_img.jpg)
+
+Figure 6.3.4.2-4: A contour plot showing uniform sampling in spherical coordinates. The horizontal axis is phi (degree) from -80 to 80, and the vertical axis is theta (degree) from 0 to 180. The plot displays a grid of red crosses representing sampling points, overlaid on a complex pattern of colored contours representing signal strength or gain. The contours are primarily green and yellow, with some blue areas at the top and bottom.
+
+**Figure 6.3.4.2-4: Uniform sampling in the spherical coordinate, red crosses denotes the sampling points**
+
+For a wanted signal, the reference angular steps are approximately equal to the beamwidth (in degrees) of the main beam.
+
+$$\Delta\phi_{ref} \cong BeW_{\phi} \cong \frac{FNBW_{\phi}}{2}$$
+
+$$\Delta\theta_{ref} \cong BeW_{\theta} \cong \frac{FNBW_{\theta}}{2}$$
+
+where  $BeW_{\phi}$  and  $BeW_{\theta}$  are the *beamwidth* of the wanted signal in the  $\phi$ -axis and  $\theta$ -axis, respectively;  $FNBW_{\phi}$  and  $FNBW_{\theta}$  are the first null beamwidth of the wanted signal in the  $\phi$ -axis and  $\theta$ -axis, respectively.
+
+Using *beamwidth* of the wanted signal, the reference angular steps for each frequency within the *downlink operating band* including  $\Delta f_{OBUE}$  can be expressed as follows:
+
+$$\Delta\phi_{ref} = \frac{\lambda}{\lambda_0} BeW_{\phi} = \frac{\lambda}{\lambda_0} \frac{FNBW_{\phi}}{2}$$
+
+$$\Delta\theta_{ref} = \frac{\lambda}{\lambda_0} BeW_{\theta} = \frac{\lambda}{\lambda_0} \frac{FNBW_{\theta}}{2}$$
+
+where  $\lambda_0$  is the wavelength of the wanted signal, and  $BeW_{\phi}$  and  $BeW_{\theta}$  are the *beamwidth* in the  $\phi$ -axis and  $\theta$ -axis, respectively.
+
+For the OTA BS radiated transmit power requirement, beamwidths at five different directions is declared by manufacturers. The declared beamwidth may be used to set  $BeW_{\phi}$  and  $BeW_{\theta}$  in the above equations provided the same beam is applied to test in-band *TRP requirements*. If the numerical singularity at of a test beam is not declared, then
+
+the beamwidth can be obtained through measurements following the same procedure as the BS radiated transmit power requirement prior to TRP measurements.
+
+In addition, the beamwidth of the wanted signal can be used to determine the physical dimensions of a radiation source as follows:
+
+$$D_{cyl} = \frac{\lambda_0}{BeW_{\phi}}$$
+
+$$D = \frac{\lambda_0}{BeW_{\theta}}$$
+
+and for the ULA case:
+
+$$D_y = \frac{\lambda_0}{\sin(BeW_{\phi})}$$
+
+$$D_z = \frac{\lambda_0}{BeW_{\theta}}$$
+
+### 6.3.4.3 Spherical equal area grids
+
+With the spherical equal area sampling grid, the spherical surface is partitioned into equal area regions. Let  $n$  be the index for the  $n$ th region and there is one point  $(\theta_n, \phi_n)$  located in the centre of each region. The definite integral for  $TRP_{Reference}$  can be approximated as:
+
+The total number angular sampling points is  $N$ . Unlike the spherical equal angle grid, the  $TRP_{Estimate}$  equation is not weighted by  $\sin\theta$ . As shown in figure 6.3.4.3-1, the equal area grid points are distributed uniformly on the sphere but the pattern of  $\theta$  and  $\phi$  angles is irregular.
+
+One possible way to estimate  $TRP_{Estimate}$  is as follows:
+
+where  $\theta_n$  and  $\phi_n$  are defined in clause 6.3.4.2. Other methods are possible and not precluded.
+
+![A 3D plot of a sphere showing a spherical equal area sampling grid. The grid consists of numerous colored dots (yellow, green, blue, purple, red) distributed across the surface of the sphere, forming a regular pattern. The axes are labeled from -1 to 1 in increments of 0.5.](9f92854fe6ecaf47760515c891a4fccc_img.jpg)
+
+A 3D plot of a sphere showing a spherical equal area sampling grid. The grid consists of numerous colored dots (yellow, green, blue, purple, red) distributed across the surface of the sphere, forming a regular pattern. The axes are labeled from -1 to 1 in increments of 0.5.
+
+**Figure 6.3.4.3-1: Spherical equal area sampling grid**
+
+#### 6.3.4.4 Spherical Fibonacci grids
+
+The Fibonacci grid points are arranged along a generative spiral on the spherical surface. Similar to the equal area sampling grid, the Fibonacci grid generates points that are uniformly spaced in an isotropic way. Assume there are  $I$  points in the Fibonacci sampling grid, then the definite integral for  $\text{TRP}_{\text{Reference}}$  can be approximated as:
+
+where  $i = 0 \dots$
+
+and
+
+,
+
+where
+
+The total number of angular sampling points is  $I$ , which can be estimated in a similar manner as in clause 6.3.4.3. Like the spherical equal area grid, the  $\text{TRP}_{\text{Estimate}}$  equation is not weighted by .
+
+![A 3D plot showing a spherical Fibonacci sampling grid. The grid consists of numerous blue dots distributed across the surface of a sphere, with yellow lines connecting them to form a mesh. The axes are labeled from -1 to 1 in the horizontal plane and -0.8 to 0.8 in the vertical axis.](75b9cb95f5815d6f3bbe57020a049504_img.jpg)
+
+A 3D plot showing a spherical Fibonacci sampling grid. The grid consists of numerous blue dots distributed across the surface of a sphere, with yellow lines connecting them to form a mesh. The axes are labeled from -1 to 1 in the horizontal plane and -0.8 to 0.8 in the vertical axis.
+
+**Figure 6.3.4.4-1: Spherical Fibonacci sampling grid**
+
+#### 6.3.4.5 Orthogonal cuts grids
+
+Compared to the TX spurious emissions the OBUE emissions and ACLR are likely to experience the similar beamforming pattern as for the wanted signal. Due to this reason, it is easily predictable where the maximum of the emissions is going to be, hence the possibility to enhance the measurement method to achieve better accuracy. Here we choose to apply the pattern multiplication method [10].
+
+In this method, at least two cuts (default) shall be used, an optional third cut can be added if needed. The alignment of the cuts must be along the symmetry planes of the *antenna array*. Note that theta reference steps apply to the vertical cuts and phi reference steps to the horizontal cuts.
+
+The first mandatory cut is a horizontal cut passing through the peak direction of the main beam.
+
+The second mandatory is a vertical cut passing through the peak direction of the main beam.
+
+Using the data from these two mandatory cuts, a conditional pattern multiplication can be used.
+
+The third optional cut is a vertical cut orthogonal to the first and the second cut.
+
+Once the number and the orientation of the cuts are decided, the total EIRP is measured on the orthogonal cuts and the TRP is then calculated as follows: First the contributions from each cut is calculated as:
+
+where  $P$  is the number of sampling points. The final contribution for all cuts is calculated as:
+
+where  $N$  is the number of cuts. Note that when orthogonal cuts are measured, the intersection points are measured multiple times and the repeated values can be removed from the samples before averaging.
+
+![Figure 6.3.4.5-1: Two diagrams illustrating orthogonal cuts geometry. The left diagram shows two mandatory cuts: a vertical cut in the yz-plane (red dots) and a horizontal cut in the xy-plane (green dots). The right diagram shows the same two mandatory cuts plus an optional third cut in the xz-plane (blue dots). All cuts are centered at the origin of a 3D coordinate system with x, y, and z axes.](2d62ff2bded0c21414a0f40fdf8fd537_img.jpg)
+
+Figure 6.3.4.5-1: Two diagrams illustrating orthogonal cuts geometry. The left diagram shows two mandatory cuts: a vertical cut in the yz-plane (red dots) and a horizontal cut in the xy-plane (green dots). The right diagram shows the same two mandatory cuts plus an optional third cut in the xz-plane (blue dots). All cuts are centered at the origin of a 3D coordinate system with x, y, and z axes.
+
+**Figure 6.3.4.5-1: Example of orthogonal cuts geometry when the main lobe points along the x-axis. Two mandatory cuts grid (left) and the optional added third cut (right). The first two cuts are generated by rotating the BS around its z-axis and y-axis, respectively, and the optional third cut is generated by rotating the BS around its x-axis**
+
+Two cuts cut data gives a conservative TRP estimate (an overestimation of the real TRP). Through pattern multiplication a less conservative estimate is obtained, based on the calculation of the antenna *array factor* as a product of two terms, corresponding to the two cuts.
+
+The following conditions for being able to apply pattern multiplication method are mandatory:
+
+- i. The vertical cut (and the main beam) is in the  $\phi$ -plane
+- ii. The frequency of the emission is within the downlink operating band.
+- iii. The bandwidth of the emission is the same as the bandwidth of the in-band modulated signal
+- iv. The emission appears/disappears when the TX power is turned on/off.
+- v. The *antenna arrays* of the BS
+  1. Have rectangular grids of antenna element positions
+  2. Have symmetry planes that are vertical and horizontal.
+  3. Have parallel antenna planes
+
+The *antenna array* is here assumed to be placed in the yz-plane. The pattern multiplication is performed in uv-coordinates and the data in the two cuts are denoted  $EIRP_{cut1}(u)$  at and a vertical cut with data  $EIRP_{cut2}(v)$  at . The data is split in two parts corresponding to the forward and backward hemisphere. The uv-coordinates are the projections of the angular directions onto the antenna plane, here the yz-plane. Using the spherical coordinates as depicted in figure 6.3.4.2-2 the u and v coordinates are defined as:
+
+Note that only the data on the coordinate axes are measured, and hence only the data  $EIRP_{cut1}(u)$  for (the horizontal cut) and  $EIRP_{cut2}(v)$  for (the vertical cut) are known. Moreover, Only the points in the circular disc , a.k.a. the visible region, contribute to the TRP.
+
+The pattern multiplication is used to calculate power density values outside the two cardinal cuts as:
+
+In Figure 6.3.4.5-2, the case where is illustrated.
+
+![Figure 6.3.4.5-2: Example of pattern multiplication. The figure shows a circular plot of EIRP(u, v) in the uv-plane, with axes u and v ranging from -1 to 1. A color bar on the right indicates power levels in dB, ranging from -40 (dark blue) to 0 (yellow). The plot shows a grid of power levels. Two dashed lines represent cuts: EIRP_cut1(u) is a horizontal cut at v=0, and EIRP_cut2(v) is a vertical cut at u=0. The EIRP(u, v) label is placed near the top right of the circle.](fd8369b549b3d1a5c848cbd83659cae9_img.jpg)
+
+Figure 6.3.4.5-2: Example of pattern multiplication. The figure shows a circular plot of EIRP(u, v) in the uv-plane, with axes u and v ranging from -1 to 1. A color bar on the right indicates power levels in dB, ranging from -40 (dark blue) to 0 (yellow). The plot shows a grid of power levels. Two dashed lines represent cuts: EIRP\_cut1(u) is a horizontal cut at v=0, and EIRP\_cut2(v) is a vertical cut at u=0. The EIRP(u, v) label is placed near the top right of the circle.
+
+**Figure 6.3.4.5-2: Example of pattern multiplication**
+
+The pattern multiplication is applied separately for the forward (fwd) and backward (bwd) hemisphere. The TRP is then calculated as
+
+NOTE: The numerical singularity at  $\theta = 0$  must be treated with care, e.g. by changing the coordinate system to polar as in [10].
+
+#### 6.3.4.6 Wave vector space sampling grid
+
+Similar as Rayleigh sampling approach, BS is placed on the yz plane in the spherical coordinate and normal vector of BS is pointing along the x-axis as shown in figure 6.3.4.2-2. The angle  $\varphi$  and  $\theta$  represent azimuth and elevation respectively,  $u$  and  $v$  represent the projection of normalized wave vector on y-axis and z-axis.
+
+According to the relationship between the normalized wave vector and spherical coordinate, the wave vector can be represented as following:
+
+TRP is defined in the spherical coordinate as following:
+
+$$\text{TRP} = \frac{1}{4\pi} \iint \text{EIRP}(\theta, \varphi) \sin \theta d\theta d\varphi$$
+
+As TRP is defined in the wave vector coordinate, therefore TRP definition should be revised accordingly in the corresponding coordinate. For the TRP definition in normalized wave vector space, according to the 2D Jacobian transformation, the above equation could be adjusted as following, namely:
+
+Based on the above two equations, then we could get
+
+where relationship between  $(\theta, \varphi)$  and  $(u, v)$  is demonstrated in the equation before. Similar as discrete sampling process, the above equation is approximated in the far-field region as the sum of the total EIRP at a number of discrete directions as follows:
+
+The above considerations could be applied for both polarization.
+
+Uniform sampling in the wave vector coordinate as shown in figure 6.3.4.6-1:
+
+- Rayleigh resolution in y-axis:
+- Rayleigh resolution in z-axis:
+
+Where  $D_y$  is length of radiating parts of BS along y-axis,  $D_z$  is length of radiating parts of BS along the z-axis.
+
+Based on the uniform sampling grid on the yz plane, we could get the sampling point  $(u, v)$ . In addition, according to the transformation between  $(u, v)$  and  $(\phi, \theta)$ , then azimuth and elevation  $(\phi_{m,n}, \theta_n)$  in the spherical coordinate could be derived correspondingly as shown in figure 6.3.4.6-2. Based on the  $(\phi_{m,n}, \theta_n)$  in the spherical coordinate, EIRP on the spherical coordinate could be measured.
+
+![Figure 6.3.4.6-1: Sampling grid in the wave vector space. The plot shows a circular sampling grid in the (u, v) plane. The horizontal axis is labeled 'u' and the vertical axis is labeled 'v', both ranging from -1.00 to 1.00. A dashed circle of radius 1.00 is centered at the origin. Red '+' markers represent the sampling points, arranged in a rectangular grid with a spacing of 0.125 units. The points are located at u = -0.75, -0.625, -0.5, -0.375, -0.25, -0.125, 0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75 and v = -0.75, -0.5, -0.25, 0, 0.25, 0.5, 0.75. Only the points within the dashed circle are shown.](e4d74b50fc10b0f0a08cb2db56123cb9_img.jpg)
+
+Figure 6.3.4.6-1: Sampling grid in the wave vector space. The plot shows a circular sampling grid in the (u, v) plane. The horizontal axis is labeled 'u' and the vertical axis is labeled 'v', both ranging from -1.00 to 1.00. A dashed circle of radius 1.00 is centered at the origin. Red '+' markers represent the sampling points, arranged in a rectangular grid with a spacing of 0.125 units. The points are located at u = -0.75, -0.625, -0.5, -0.375, -0.25, -0.125, 0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75 and v = -0.75, -0.5, -0.25, 0, 0.25, 0.5, 0.75. Only the points within the dashed circle are shown.
+
+Figure 6.3.4.6-1: Sampling grid in the wave vector space
+
+![Figure 6.3.4.6-2: Sampling grid in the spherical coordinate. The plot shows a grid of red '+' markers representing sampling points in the spherical coordinate system. The horizontal axis is labeled phi(degree) and ranges from -90 to 90. The vertical axis is labeled theta(degree) and ranges from 0 to 180. The grid points are arranged in a regular pattern, with theta values at 40, 60, 80, 100, 120, 140, and 160 degrees, and phi values at -70, -50, -30, -10, 10, 30, 50, and 70 degrees.](201de44da5d99899a8cf58eac2fa7bc9_img.jpg)
+
+Figure 6.3.4.6-2: Sampling grid in the spherical coordinate. The plot shows a grid of red '+' markers representing sampling points in the spherical coordinate system. The horizontal axis is labeled phi(degree) and ranges from -90 to 90. The vertical axis is labeled theta(degree) and ranges from 0 to 180. The grid points are arranged in a regular pattern, with theta values at 40, 60, 80, 100, 120, 140, and 160 degrees, and phi values at -70, -50, -30, -10, 10, 30, 50, and 70 degrees.
+
+Figure 6.3.4.6-2: Sampling grid in the spherical coordinate
+
+## 6.3.5 Aspects related to measurement of OTA unwanted emission
+
+### 6.3.5.1 Test range
+
+Test of OTA unwanted emission required an OTA test environment, capable of measuring TRP emission under the condition that the test object is radiating the wanted signal at full power. To handle high RF power from the test object required careful planning of the setup (e.g. test personal and test equipment cannot be placed inside the test chamber during the test). To avoid measurement chamber influence and external interferer on the test result, use of a shielded anechoic chamber is preferable. A positioner is used to move the test object according to selected measurement grid for a proper TRP measurement. The emission is measured at the output RF port of the measurement antenna placed at a suitable test distance. In figure 6.3.5.1-1, a principle test environment suitable for OTA unwanted emission is depicted.
+
+![Figure 6.3.5.1-1: Principle test environment. The diagram illustrates a measurement setup inside a shielded anechoic chamber. On the left, a Device Under Test (DUT) is mounted on a positioner. The DUT has two connections labeled (1) and (2). A coordinate system (x, y, z) is centered near the DUT. A signal path is shown from the DUT to a 'Test range antenna' on the right. The path is characterized by L_path_loss. The antenna has a gain G_ant. The signal then passes through a cable with loss L_cable, a notch filter with loss L_notch_filter, and a Low Noise Amplifier (LNA) with noise figure NF_LNA. The output of the LNA goes to a Spectrum analyzer (RX). Below the chamber, a 'Positioner controller' is connected to the DUT positioner and to a 'PC'. The PC is also connected to the Spectrum analyzer.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg)
+
+Figure 6.3.5.1-1: Principle test environment. The diagram illustrates a measurement setup inside a shielded anechoic chamber. On the left, a Device Under Test (DUT) is mounted on a positioner. The DUT has two connections labeled (1) and (2). A coordinate system (x, y, z) is centered near the DUT. A signal path is shown from the DUT to a 'Test range antenna' on the right. The path is characterized by L\_path\_loss. The antenna has a gain G\_ant. The signal then passes through a cable with loss L\_cable, a notch filter with loss L\_notch\_filter, and a Low Noise Amplifier (LNA) with noise figure NF\_LNA. The output of the LNA goes to a Spectrum analyzer (RX). Below the chamber, a 'Positioner controller' is connected to the DUT positioner and to a 'PC'. The PC is also connected to the Spectrum analyzer.
+
+**Figure 6.3.5.1-1: Principle test environment**
+
+The test environment may differ between OTA unwanted emission requirements; OTA ACLR, OTA OBUE and OTA spurious emission. For OTA spurious emission, a test environment similar to the one used for EMC radiated emission or a Shielded Indoor Anechoic Chamber (IAC) can be used. For OTA unwanted emission requirements defined within the in-band region other test environments could be considered e.g. CATR or IAC.
+
+A band stop filter is needed to protect the measurement receiver from the wanted signal, achieving dynamic range for the emission to be measured with acceptable measurement uncertainty.
+
+### 6.3.5.2 Measurement distance
+
+The measurement distance is the distance between the test object and the measurement antenna (or probe antenna). The measurement distance is usually determined by the signal-to-noise ratio (SNR) required for the measurement receiver to detect the emission level with acceptable measurement uncertainty. Unlike, EIRP, *total radiated power* (TRP) is not exclusively a far-field parameter. TRP is defined as the *total radiated power* radiated by an object, regardless to the distance. Since emission power levels tends to be low, it is essential to conserve the path-loss in the test setup, by minimizing the measurement distance. Another aspect is the for the lower limit (i.e. 30 MHz) the far-field criteria would result in unpractical measurement distances for OTA testing. Further guidance on near-field testing can be found in annex F.
+
+### 6.3.5.3 Sampling grid selection
+
+A dense full-sphere grid, i.e. using reference steps, will result in a very large number of measurement points to extract TRP per frequency, while a sparse grid requires a few measurements. The selection of grid and corresponding sampling resolution determines the measurement uncertainty error contribution related to sampling the radiating power over the sphere. Determining proper sampling grids for emission, assumptions of the spatial distribution of emission should be considered. If it can be established that the emission is radiating in all directions, the sample grid resolution can be significantly reduced.
+
+The ability of direct emission in certain direction is set by the physical size of BS, number of radiating sources and correlation properties. For low frequencies, where  $D \ll \lambda$ , it is reasonable to believe that the radiated emission will be omni-directional, while for the case where  $D \gg \lambda$ , there is a potential risk that emission leaking through the encapsulation or the antenna aperture can be directed in a certain direction. Therefore, the process to determine the sampling grid and corresponding resolution needs to include the frequency as one parameter. Consequently, a concept with a fixed sampling grid over the whole spurious frequency domain is not suitable to balance measurement uncertainty with test time.
+
+### 6.3.6 TRP summation error
+
+In practice, discrete samples of EIRP or power density are measured at different directions over the entire sphere, which are used to numerically approximate the surface  $TRP_{Reference}$  integral. The obtained value,  $TRP_{Estimate}$ , is an approximation of  $TRP_{Reference}$  and the difference between them is defined as the *TRP summation error* (SE) which is
+
+$$SE = | \text{TRP}_{\text{Estimate}} - \text{TRP}_{\text{reference}} | \text{ (in dB)}$$
+
+The SE is the error caused by the numerical integration of measured values on the grid to obtain  $\text{TRP}_{\text{Estimate}}$ , given that the number of test points correspond to the reference angular steps, which are in turn dependent on antenna size and frequency, as described in clause 6.3.4. A reasonable trade-off between accuracy and sampling time is achieved when the SE = 0.75 dB.
+
+## 6.4 Co-location measurements
+
+### 6.4.1 General
+
+Co-location measurements are required for the OTA co-location requirements which are based on assuming the BS is co-located with another BS of the same base station class. They ensure that both co-located systems can operate with minimal degradation to each other.
+
+Co-location requirements are specified as power levels into or out of the conducted interface of the *co-location reference antenna*. For conformance testing the requirements are translated to the input or output of a *co-location test antenna* (CLTA).
+
+CLTA is a practical passive antenna that is used for conformance testing of the co-location requirements and is based on the definition of the *co-location reference antenna*. Basic principle of the CLTA are outlines in clause 6.4.2. For more details on the *co-location test antenna* characteristics, refer to TS 37.145-2 [4] clause 4.15.2.2, or TS 38.141-2 [6] clause 4.12.2.2. The CLTA is suitable for testing BS implemented with a planar *antenna array*.
+
+The alignment between the BS under test and the *co-location test antenna* is depicted in figure 6.4.1-1. For more details on the *co-location test antenna* alignment and test arrangement, refer to TS 37.145-2 [4] clause 4.15.2.3, or TS 38.141-2 [6] clause 4.12.2.3. The same physical alignment applies to in-band and out-of-band co-location requirements.
+
+Co-location requirements are not applicable to FR2.
+
+![Figure 6.4.1-1: Alignment of BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, an NR BS type 1-O (represented by a square with an X) and a CLTA (represented by a narrow rectangle with an X) are shown. A dashed horizontal line connects their centers, and a double-headed arrow labeled 'd' indicates the distance between them. In the Vertical View, the NR BS type 1-O is shown as a rectangle, and the CLTA as a small rectangle. A dashed vertical line connects their centers. Arrows point down from each to the label 'Mechanical bore-sight direction'. In the Side View, the NR BS type 1-O is shown as a dashed rectangle with two small squares inside, labeled 'Back side' and 'Front side'.](3252037b597c9317aced0feed4cb5af0_img.jpg)
+
+Figure 6.4.1-1: Alignment of BS and CLTA. The diagram shows three views: Horizontal View, Vertical View, and Side View. In the Horizontal View, an NR BS type 1-O (represented by a square with an X) and a CLTA (represented by a narrow rectangle with an X) are shown. A dashed horizontal line connects their centers, and a double-headed arrow labeled 'd' indicates the distance between them. In the Vertical View, the NR BS type 1-O is shown as a rectangle, and the CLTA as a small rectangle. A dashed vertical line connects their centers. Arrows point down from each to the label 'Mechanical bore-sight direction'. In the Side View, the NR BS type 1-O is shown as a dashed rectangle with two small squares inside, labeled 'Back side' and 'Front side'.
+
+Figure 6.4.1-1: Alignment of BS and CLTA
+
+## 6.4.2 Co-location test antenna
+
+The *co-location test antenna* is a practical passive antenna based on the definition of the *co-location reference antenna*, and it is used for conformance testing of the co-location requirements. Thus the CLTA should be within a certain tolerance of the co-location reference antenna definition, so that commonly available passive BS antennas can be used to test the co-location requirements without having to use a large number of test antennas and without having to design specialized *co-location test antennas*.
+
+For example, where the co-location reference antenna definition specifies that the *co-location reference antenna*, should be a single column passive antenna which has the same vertical radiating dimension (h) as the composite antenna of BS, this would be very restrictive when selecting a test antenna. Hence the CLTA should be within a certain tolerance for the vertical radiating dimension (h) such that a suitable practical BS antenna can be found for each BS.
+
+The CLTA is hence defined as follows:
+
+- The CLTA is a single column passive antenna which has a vertical radiating dimension (h) which is equal to the vertical radiating dimension of the BS composite antenna  $\pm 30\%$ .
+- For in-band requirements, the CLTA supports the same frequency range and polarizations as the BS composite antenna.
+- For out-of-band co-location requirements, the half power vertical beamwidth of the CLTA equals the narrowest declared vertical beamwidth  $\pm 3^\circ$ .
+- The polarization should match the in-band CLTA polarization.
+- The CLTA has a horizontal half-power beamwidth of  $65^\circ \pm 10^\circ$ .
+- The front faces of the BS and the CLTA need to be aligned in a common plane perpendicular to the mechanical bore-sight direction.
+- The centre of the vertical radiating regions of the CLTA and the BS composite antenna need to be aligned.
+
+## 6.4.3 Standard test antenna
+
+Co-location requirements may also be tested with a standardised test antenna such as a dipole. This has a number of advantages:
+
+- Standard test antennas are easily available and easier to specify.
+  - Repeatability between different conformance testing runs will be greater.
+- Using standard test antennas, fewer antennas will be required for conformance testing.
+- A standard test antenna can have higher gain in the direction of the BS than a CLTA, so that signal levels can be higher relative to the noise floor in emission measurements and lower test levels can be used in interference measurements.
+
+In order to test with a standard test antenna, the translation between measured power levels in the standard test antenna and the *co-location reference antenna* must be shown. The method for translating the power levels in the *co-location reference antenna* to the standard test antenna and vice versa is not covered by the present release of this technical report.
+
+## 6.5 Requirements classification
+
+Based on the above spatial definitions, in table 6.5-1 captures classification of the radiated TX requirements and table 6.5-2 captures classification of the radiated RX requirements.
+
+**Table 6.5-1: Classification of radiated TX requirements**
+
+| TX requirement                       | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Classification                                            |
+|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
+| Radiated transmit power              | The minimum requirements for radiated transmit power, are placed on one or more manufacturer declared beams over a declared OTA peak direction set. OTA requirements for BS output power are defined for directional EIRP requirements as radiated transmit power requirements.<br>This requirement originates from the Rel-13 AAS BS requirement for the EIRP accuracy.                                                                                                                                                                                                                                                                                                               | Directional                                               |
+| OTA BS output power                  | TRP metric is used for BS output power limit requirement.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | TRP                                                       |
+| OTA output power dynamics            | OTA output power dynamics consists of the Total power dynamic range, as well as the RE power control dynamic range requirements.<br>For E-UTRA specification, the RE power control dynamic range requirement has no specific test and is tested together with the EVM. Furthermore, verification of the output power dynamics is not impacted by the spatial aspects around the BS. Therefore, the OTA output power dynamics requirements are considered as directional requirements.                                                                                                                                                                                                  | Directional                                               |
+| OTA transmit OFF power               | The OTA transmit OFF power is a co-location requirement in FR1, defined at the <i>co-location reference antenna</i> conductive output side, subject to scaling.<br>For FR2, it is defined as <i>TRP requirement</i> .                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | FR1: Co-location<br>FR2: TRP                              |
+| OTA transient period                 | Same as OTA transmit OFF power, the OTA transient period is a co-location requirement in FR1, defined at the <i>co-location reference antenna</i> conductive output side, subject to scaling.<br>For FR2, it is defined as directional requirement.                                                                                                                                                                                                                                                                                                                                                                                                                                    | FR1: Co-location<br>FR2: directional                      |
+| OTA transmitted signal quality       | EVM: The range of directions where the EVM requirement must be met is declared by the manufacturer as <i>OTA coverage range</i> , while the requirement itself is considered directional.<br>Frequency error: The frequency error is coherent and will have a 'flat' response in the spatial domain, i.e. OTA frequency error will not depend on the selection of the measurement point within beam's compliance directions set. Therefore, single directional requirement can be applied.<br>TAE: In terms of testing effort it is beneficial, to coordinate testing of OTA TAE with testing of other transmitter parameters such as OTA frequency error and radiated transmit power. | Directional                                               |
+| OTA occupied bandwidth               | For occupied bandwidth, the beam characteristics are not important. The requirement should however cover the fact that all transmitter is active and the system is operating at the maximum declared rated <i>total radiated power</i> . Occupied bandwidth is specified as a directional requirement valid over the <i>OTA coverage range</i> .                                                                                                                                                                                                                                                                                                                                       | Directional                                               |
+| OTA ACLR                             | ACLR requirement is the ratio of two TRP measures: the total radiated filtered mean power centred on the assigned channel frequency to the total radiated filtered mean power centred on an adjacent channel frequency.                                                                                                                                                                                                                                                                                                                                                                                                                                                                | TRP                                                       |
+| OTA operating band unwanted emission | The OBUE unwanted emissions requirement in the OTA domain must capture all emissions around the BS by application of the TRP metric.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | TRP                                                       |
+| OTA transmitter spurious emission    | Similar to other Unwanted emissions requirements, the metric used to capture transmitter spurious emissions OTA is TRP.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | TRP except for co-location requirements applicable in FR1 |
+| OTA transmitter intermodulation      | OTA transmitter intermodulation requirement relies on Unwanted emission requirements (i.e. operating band unwanted emission, transmitter spurious emission, and ACLR; all defined as TRP) in the presence of a wanted signal and an interfering signal.<br>No requirement for FR2 is defined.                                                                                                                                                                                                                                                                                                                                                                                          | Co-location                                               |
+
+Directional requirements are to be met over one of two defined directions sets, with each direction set being declared:
+
+- The *OTA coverage range*: range of directions over which *directional requirements* associated with BS-UE communication are intended such as modulation quality, TAE and frequency error. It can be regarded as the range of directions which define the cell coverage. There is only one *OTA coverage range* per BS.
+- The *OTA peak directions set*: intended for *directional requirements* which are intended for the centre of the beam for example EIRP accuracy. The *OTA peak directions set* must always be within the *OTA coverage range*.
+
+There may be more than one *OTA peak directions set* declared, the declarations cover the range of directions which a beam may be steered. As the BS may generate more than one type of beam with different beam widths and different steering capabilities the declaration allows for multiple *OTA peak direction sets* to be declared. The minimum set of declarations covers the beams with the narrowest and the widest beam widths.
+
+**Table 6.5-2: Classification of radiated Rx requirements**
+
+| Rx requirement                       | Description and discussion                                                                                                                                                                                                                                                                              | Classification                                                                    |
+|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| OTA sensitivity                      | Based on the Rel-13 EIS requirement declaration over the OSDD, the OTA sensitivity is directional requirement by definition. Conformance testing for OTA sensitivity is performed for the five directions. This requirement is not applicable for <i>BS type 2-O</i> .                                  | Directional                                                                       |
+| OTA reference sensitivity level      | Conformance testing for OTA reference sensitivity is performed for five directions declared by the manufacturer.                                                                                                                                                                                        | Directional                                                                       |
+| OTA dynamic range                    | It was agreed that the requirement assumes that the wanted signal and interfering signal come from the same direction. Testing is defined in the <i>receiver target reference direction</i> , meaning that this is directional requirement. This requirement is not applicable for <i>BS type 2-O</i> . | Directional                                                                       |
+| OTA in-band selectivity and blocking | The OTA blocking requirement is tested as follows:<br>- In the reference direction of the minSENS OSDD using the minSENS based requirement level<br>- In each of the 4 conformance direction at the extremities of the <i>OTA REFSENS RoAoA</i> using the REFSENS based requirement level.              | Directional                                                                       |
+| OTA out-of-band blocking             | Out-of-band blocking is a long test and hence it is optimum to minimize the number of conformance test directions. The <i>antenna gain</i> can be assumed to be maximum at the reference direction, therefore it is sufficient to show conformance at the reference direction only.                     | Directional, except for co-location requirement applicable for <i>BS type 1-O</i> |
+| OTA receiver spurious emission       | The Rx spurious emissions requirement follows the approach for the Tx spurious emissions, i.e. the emissions in the spurious region needs to be measured as TRP due to unknown <i>radiation pattern</i> .                                                                                               | TRP                                                                               |
+| OTA receiver intermodulation         | Since RX sensitivity and blocking already test at all conformance directions, it is sufficient to test RX IM only in a single direction.                                                                                                                                                                | Directional                                                                       |
+| OTA in-channel selectivity           | In channel selectivity requirement is tested in a single direction.                                                                                                                                                                                                                                     | Directional                                                                       |
+
+## 7 OTA measurement systems
+
+### 7.1 General
+
+All the measurement systems are described for measurement in Normal test conditions, unless otherwise stated.
+
+### 7.2 Indoor Anechoic Chamber
+
+#### 7.2.1 Measurement system description, Normal test conditions
+
+This method measures the EIRP in an anechoic chamber with the separation between the manufacturer declared coordinate system reference point of the BS and the phase centre of the receiving antenna of no less than  $2D^2/\lambda$ , where D is the largest dimension of the antenna of BS and  $\lambda$  is the wavelength. The measurement system setup is as depicted in figure 7.2.1-1 for TX requirements, and in figure 7.2.1-2 for RX requirements.
+
+![Diagram of IAC measurement system setup for TX requirements. It shows an AAS BS under test inside a semi-circular anechoic chamber. A receiving antenna is positioned on the right wall, connected to measurement equipment via its connector (C) and RF in (D). Reference point A is on the BS, and phase center B is on the receiving antenna.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg)
+
+The diagram illustrates the IAC measurement system setup for TX requirements. An AAS BS under test is located on the left side of a semi-circular anechoic chamber. On the right side, a receiving antenna is mounted. A dashed vertical line labeled 'A' passes through the center of the AAS BS. Another dashed vertical line labeled 'B' passes through the phase center of the receiving antenna. The receiving antenna is connected to measurement equipment at point 'C' (Receiving antenna connector) and point 'D' (RF in). The measurement equipment is shown as a box labeled 'Measurement equipment' with 'RF in' at point 'D'.
+
+A: Reference point of AAS BS  
+B: Phase centre of the receiving antenna  
+C: Receiving antenna connector  
+D: Measurement equipment connector
+
+Diagram of IAC measurement system setup for TX requirements. It shows an AAS BS under test inside a semi-circular anechoic chamber. A receiving antenna is positioned on the right wall, connected to measurement equipment via its connector (C) and RF in (D). Reference point A is on the BS, and phase center B is on the receiving antenna.
+
+Figure 7.2.1-1: IAC measurement system setup for TX requirements
+
+![Diagram of IAC measurement system setup for RX requirements. It shows an AAS BS under test inside a semi-circular anechoic chamber. A transmitting antenna is positioned on the right wall, connected to a signal generator via its connector (C) and RF out (D). Reference point A is on the BS, and phase center B is on the transmitting antenna.](848073118eebfdbfdb9a60e3923fe0b3_img.jpg)
+
+The diagram illustrates the IAC measurement system setup for RX requirements. An AAS BS under test is located on the left side of a semi-circular anechoic chamber. On the right side, a transmitting antenna is mounted. A dashed vertical line labeled 'A' passes through the center of the AAS BS. Another dashed vertical line labeled 'B' passes through the phase centre of the transmitting antenna. The transmitting antenna is connected to a signal generator at point 'C' (Transmitting antenna connector) and point 'D' (RF out). The signal generator is shown as a box labeled 'Signal Generator' with 'RF out' at point 'D'.
+
+A: Reference point of AAS BS  
+B: Phase centre of the transmitting antenna  
+C: Transmitting antenna connector  
+D: Measurement equipment connector
+
+Diagram of IAC measurement system setup for RX requirements. It shows an AAS BS under test inside a semi-circular anechoic chamber. A transmitting antenna is positioned on the right wall, connected to a signal generator via its connector (C) and RF out (D). Reference point A is on the BS, and phase center B is on the transmitting antenna.
+
+Figure 7.2.1-2: IAC measurement system setup for RX requirements
+
+![Diagram of IAC measurement system setup for OTA dynamic range. It shows an AAS BS Under test inside a chamber with a transmitting antenna. The antenna is connected to a Power combiner/Coupler, which is further connected to two Signal Generators: one for AWGN signal (RF out E) and one for wanted signal (RF out D). Reference points A, B, and C are marked.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg)
+
+A: Reference point of AAS BS  
+B: Phase centre of the transmitting antenna  
+C: Transmitting antenna connector  
+D, E: Measurement equipment connector
+
+Diagram of IAC measurement system setup for OTA dynamic range. It shows an AAS BS Under test inside a chamber with a transmitting antenna. The antenna is connected to a Power combiner/Coupler, which is further connected to two Signal Generators: one for AWGN signal (RF out E) and one for wanted signal (RF out D). Reference points A, B, and C are marked.
+
+Figure 7.2.1-3: IAC measurement system setup for OTA dynamic range
+
+![Diagram of IAC measurement system setup for adjacent channel selectivity, general blocking, narrowband blocking and in-channel selectivity. It shows an AAS BS Under test inside a chamber with a transmitting antenna. The antenna is connected to a Power combiner/Coupler, which is further connected to two Signal Generators: one for unwanted signal (RF out E) and one for wanted signal (RF out D). Reference points A, B, and C are marked.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg)
+
+A: Reference point of AAS BS  
+B: Phase centre of the transmitting antenna  
+C: Transmitting antenna connector  
+D, E: Measurement equipment connector
+
+Diagram of IAC measurement system setup for adjacent channel selectivity, general blocking, narrowband blocking and in-channel selectivity. It shows an AAS BS Under test inside a chamber with a transmitting antenna. The antenna is connected to a Power combiner/Coupler, which is further connected to two Signal Generators: one for unwanted signal (RF out E) and one for wanted signal (RF out D). Reference points A, B, and C are marked.
+
+Figure 7.2.1-4: IAC measurement system setup for adjacent channel selectivity, general blocking, narrowband blocking and in-channel selectivity
+
+![Diagram of IAC measurement system setup for OTA receiver intermodulation. It shows an AAS BS under test and a transmitting antenna inside a semi-circular anechoic chamber. The transmitting antenna is connected to a power combiner/coupler, which is further connected to three signal generators (RF out) labeled F, E, and D. Labels A, B, and C indicate the reference point, phase centre, and connector respectively.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg)
+
+A: Reference point of AAS BS  
+ B: Phase centre of the transmitting antenna  
+ C: Transmitting antenna connector  
+ D, E, F: Measurement equipment connector
+
+Diagram of IAC measurement system setup for OTA receiver intermodulation. It shows an AAS BS under test and a transmitting antenna inside a semi-circular anechoic chamber. The transmitting antenna is connected to a power combiner/coupler, which is further connected to three signal generators (RF out) labeled F, E, and D. Labels A, B, and C indicate the reference point, phase centre, and connector respectively.
+
+Figure 7.2.1-5: IAC measurement system setup for OTA receiver intermodulation
+
+![Diagram of IAC measurement system setup for co-location requirements. It shows an AAS BS under test and a co-location [test] antenna inside a semi-circular anechoic chamber. The co-location antenna is connected to a power amplifier (PA) and then to an RF out signal generator (F). The AAS BS is connected to an RF in measurement equipment (D). Labels A, B, C, and E indicate the attachment point, phase centre, connector, and co-location antenna connector respectively. Arrows indicate rotation directions for theta and phi.](3c04b14104f95eb8f7100f6d497d956e_img.jpg)
+
+Diagram of IAC measurement system setup for co-location requirements. It shows an AAS BS under test and a co-location [test] antenna inside a semi-circular anechoic chamber. The co-location antenna is connected to a power amplifier (PA) and then to an RF out signal generator (F). The AAS BS is connected to an RF in measurement equipment (D). Labels A, B, C, and E indicate the attachment point, phase centre, connector, and co-location antenna connector respectively. Arrows indicate rotation directions for theta and phi.
+
+(a) General set-up (top view)  
+(Positioner is not described here)
+
+Figure 7.2.1-6: IAC measurement system setup for co-location requirements
+
+## 7.2.2 Measurement system description, Extreme test conditions
+
+This method places the BS under test inside a RF transparent environmentally sealed enclosure so that the BS temperature can be controlled whilst the result of the OTA chamber facility is at nominal temperature.
+
+The separation between the manufacturer declared coordinate system reference point of the BS and the phase centre of the receiving antenna of no less than  $2D^2/\lambda$ , where D is the largest dimension of the antenna of BS and  $\lambda$  is the wavelength. The measurement system setup is as depicted in figure 7.2.2-1.
+
+![Diagram of the IAC measurement system setup for EIRP accuracy, Extreme test conditions. The diagram shows a cross-section of a test system enclosure with a radome-like outer wall. Inside, an AAS BS is mounted on a temperature control system. A 'Test system Calibrated point' is marked on the BS. The 'AAS declared coordinate reference point and orientation' is indicated by a dashed line with angles theta and phi. A 'Test antenna' is positioned to the right, with its 'Phase centre' marked. The 'Receiving antenna connector' is shown on the test antenna, and the 'Measurement equipment connector' is shown on the measurement equipment. The distance between the BS and the test antenna is labeled as 'Test system enclosure'.](a4bfa2343d75076b79f7e33d93915e00_img.jpg)
+
+Diagram of the IAC measurement system setup for EIRP accuracy, Extreme test conditions. The diagram shows a cross-section of a test system enclosure with a radome-like outer wall. Inside, an AAS BS is mounted on a temperature control system. A 'Test system Calibrated point' is marked on the BS. The 'AAS declared coordinate reference point and orientation' is indicated by a dashed line with angles theta and phi. A 'Test antenna' is positioned to the right, with its 'Phase centre' marked. The 'Receiving antenna connector' is shown on the test antenna, and the 'Measurement equipment connector' is shown on the measurement equipment. The distance between the BS and the test antenna is labeled as 'Test system enclosure'.
+
+- A: Reference point of AAS BS
+- B: Phase centre of the receiving antenna
+- C: Receiving antenna connector
+- D: Measurement equipment connector
+
+Figure 7.2.2-1: IAC measurement system setup for EIRP accuracy, Extreme test conditions
+
+## 7.2.3 Test method limitations
+
+The maximum size of the BS is a chamber restriction that would affect the quality of the quiet zone. For larger BS sizes larger size chambers should be considered such that the uncertainty of the quiet zone is taken into account.
+
+# 7.3 Compact Antenna Test Range
+
+## 7.3.1 Measurement system description, Normal test conditions
+
+In case of TX requirements measurement, the Compact Antenna Test Range (CATR) uses the BS which radiates a wavefront to a range antenna reflector which will then collimate the radiated spherical wavefront into a feed antenna. The sufficient separation between the BS and the receiver (feed antenna shown in figure 7.3.1-1) so that the emanating spherical wave reaches nearly plane phase fronts from transmitter to receiver. The BS transmits a wavefront that will illuminate the range antenna reflector, which will then reflect the transmitted energy into the feed antenna. The range feed antenna is connected to a vector network analyzer or other equivalent test equipment.
+
+![CATR measurement system setup for TX requirements diagram](575d7d345b3ec04393bb2ec720ebabca_img.jpg)
+
+This diagram illustrates the CATR measurement system setup for TX requirements. It shows a DUT (Device Under Test) mounted on a positioner (labeled 1, 2, 3, 4) inside an anechoic chamber. A feed antenna is positioned to illuminate the DUT. A range antenna reflector is used to collimate the radiated spherical wavefront. The system is controlled by a PC connected to a Positioner controller and a PM/SG (Phase Meter/Signal Generator). A coordinate system (x, y, z) is shown, with the y-axis pointing into the page.
+
+CATR measurement system setup for TX requirements diagram
+
+**Figure 7.3.1-1: CATR measurement system setup, TX requirements**
+
+In case of RX requirements, the CATR uses the feed antenna which radiates a spherical wavefront to a range reflector antenna which will then collimate the radiated spherical wavefront to the BS. There is sufficient separation between the BS and the transmitter (feed antenna shown in figure 7.3.1-2) so that the emanating spherical wave reaches nearly plane phase fronts from transmitter to receiver. The feed antenna transmits a wavefront that will illuminate the range antenna reflector, which will then reflect the transmitted energy towards the BS.
+
+![CATR measurement system setup for RX requirements diagram](cc542843836eecb036b99cb270b54a1e_img.jpg)
+
+This diagram illustrates the CATR measurement system setup for RX requirements. It shows a DUT (Device Under Test) mounted on a positioner (labeled 1, 2, 3, 4) inside an anechoic chamber. A feed antenna is positioned to illuminate the DUT. A range antenna reflector is used to collimate the radiated spherical wavefront. The system is controlled by a PC connected to a Positioner controller and a PM/SG (Phase Meter/Signal Generator). A coordinate system (x, y, z) is shown, with the y-axis pointing into the page. A dashed vertical line labeled 'A' indicates the reference plane. The PM/SG has two output ports labeled 'B' and 'C'.
+
+CATR measurement system setup for RX requirements diagram
+
+Figure 7.3.1-2: CATR measurement system setup, RX requirements
+
+![Diagram of CATR measurement system setup for RX requirements. It shows a DUT (Device Under Test) inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, two PM/SG units (one for 'wanted' signal, one for AWGN), and a power combiner.](30387053b5b3fede6873f6a46a9ca4a9_img.jpg)
+
+The diagram illustrates the CATR measurement system setup for RX requirements. A DUT is positioned inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, two PM/SG units (one for 'wanted' signal, one for AWGN), and a power combiner. The DUT is connected to the positioner controller and the PC. The transmitting antenna is connected to the PC. The range antenna reflector is connected to the power combiner. The power combiner is connected to the two PM/SG units. The first PM/SG unit is labeled 'wanted' with inputs C and B. The second PM/SG unit is labeled 'AWGN' with inputs D and E. The power combiner outputs to the range antenna reflector. The DUT is also connected to the range antenna reflector. The coordinate system (x, y, z) is shown, with the x-axis pointing right, the y-axis pointing into the page, and the z-axis pointing up. The DUT is located at point A, and the transmitting antenna is at point F.
+
+Diagram of CATR measurement system setup for RX requirements. It shows a DUT (Device Under Test) inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, two PM/SG units (one for 'wanted' signal, one for AWGN), and a power combiner.
+
+Figure 7.3.1-3: CATR measurement system setup, RX OTA dynamic range, ACS, general blocking and narrowband blocking
+
+![Diagram of CATR measurement system setup for RX OTA dynamic range, ACS, general blocking and narrowband blocking. It shows a DUT (Device Under Test) inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, three PM/SG units (one for 'wanted' signal, one for 'interferer1', one for 'interferer2'), and power combiners.](91134b9a38d7f73f03375473e7b706f9_img.jpg)
+
+The diagram illustrates the CATR measurement system setup for RX OTA dynamic range, ACS, general blocking and narrowband blocking. A DUT is positioned inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, three PM/SG units (one for 'wanted' signal, one for 'interferer1', one for 'interferer2'), and power combiners. The DUT is connected to the positioner controller and the PC. The transmitting antenna is connected to the PC. The range antenna reflector is connected to the power combiners. The power combiners are connected to the three PM/SG units. The first PM/SG unit is labeled 'wanted' with inputs C and B. The second PM/SG unit is labeled 'interferer1' with inputs D and E. The third PM/SG unit is labeled 'interferer2' with inputs G and H. The power combiners output to the range antenna reflector. The DUT is also connected to the range antenna reflector. The coordinate system (x, y, z) is shown, with the x-axis pointing right, the y-axis pointing into the page, and the z-axis pointing up. The DUT is located at point A, and the transmitting antenna is at point F.
+
+Diagram of CATR measurement system setup for RX OTA dynamic range, ACS, general blocking and narrowband blocking. It shows a DUT (Device Under Test) inside a chamber with a transmitting antenna and a range antenna reflector. The system includes a positioner controller, a PC, three PM/SG units (one for 'wanted' signal, one for 'interferer1', one for 'interferer2'), and power combiners.
+
+Figure 7.3.1-4: CATR measurement system setup, OTA RX IMD
+
+![CATR measurement system setup for OTA ICS diagram](fcc757566216206ceddbd6c775e8db02_img.jpg)
+
+This diagram illustrates the CATR measurement system setup for OTA ICS. It features a large rectangular RF chamber with jagged edges representing wave absorbers. Inside the chamber, a 'DUT' (Device Under Test) is mounted on a vertical stand. To the right of the DUT is a 'Range antenna reflector', and below it is a 'Transmitting antenna'. A coordinate system with x, y, and z axes is shown. A red dashed line labeled 'A' indicates a cross-section. Outside the chamber, a 'Positioner controller' is connected to the DUT's mount and to a 'PC'. The 'PC' is also connected to a 'PM/SG' (Phase and Power Source Generator) which has ports labeled 'C', 'B', and 'D'. The 'PM/SG' is connected to a 'Power combiner', which in turn is connected to the 'Transmitting antenna' inside the chamber.
+
+CATR measurement system setup for OTA ICS diagram
+
+Figure 7.3.1-5: CATR measurement system setup for OTA ICS
+
+![CATR measurement system setup for TAE diagram](74d23510f27b21403a7be84820821863_img.jpg)
+
+This diagram illustrates the CATR measurement system setup for TAE. It shows a similar RF chamber setup with a 'DUT' and a 'Range antenna reflector'. However, the 'Feed antenna' is positioned differently, pointing towards the DUT. The 'DUT' is connected to a 'Positioner controller' which is linked to a 'PC'. A 'GPS disciplined oscillator' provides a 'Reference Clock Synchronized' signal to both the 'Positioner controller' and a 'Signal Analyzer'. The 'Signal Analyzer' is connected to the 'DUT' and to the 'Feed antenna' inside the chamber.
+
+CATR measurement system setup for TAE diagram
+
+Figure 7.3.1-6: CATR measurement system setup for TAE
+
+### 7.3.2 Measurement system description, Extreme test conditions
+
+This method places the BS under test inside a RF transparent environmentally sealed enclosure so that the BS temperature can be controlled whilst the result of the OTA chamber facility is at nominal temperature.
+
+The Compact Antenna Test Range (CATR) uses the BS which radiates a wave front to a range antenna reflector which will then collimate the radiated spherical wave front into a feed antenna. The sufficient separation between the BS and the receiver (feed antenna shown in figure 7.3.2-1) so that the emanating spherical wave reaches nearly plane phase fronts from transmitter to receiver. The BS transmits a wave front that will illuminate the range antenna reflector, which will then reflect the transmitted energy into the feed antenna. The range feed antenna is connected to a vector network analyzer or other equivalent test equipment.
+
+For the environmental control of the BS required to produce the extreme temperature environment the BS under test is placed inside a RF transparent environmentally sealed enclosure so that the BS temperature can be controlled whilst the result of the OTA chamber facility is at nominal temperature.
+
+![Diagram of CATR measurement system setup for EIRP accuracy in Extreme test conditions. The diagram shows a 'Radome like enclosure' containing a 'Temperature control system' and a 'Test system Calibrated point'. Inside the enclosure is an 'AAS BS' (Active Antenna System Base Station) with a coordinate reference point and orientation (theta, phi). A 'Test antenna' is positioned to receive signals from the BS. The 'Test system enclosure' contains a 'Positioner controller', a 'PM/SG' (Phase and Magnitude Source/Generator), and a 'PC'. The system is connected to a 'Test system Calibrated point' and a 'Test antenna'.](a47713c2491e6ce619259ed2f196fd24_img.jpg)
+
+The diagram illustrates the CATR measurement system setup. A large rectangular 'Test system enclosure' with a jagged border represents the chamber. Inside, on the left, is a 'Radome like enclosure' which houses a 'Temperature control system'. Within the radome is the 'AAS BS' (Active Antenna System Base Station). A 'Test system Calibrated point' is marked on the BS. A coordinate system is defined with the origin at the BS, with axes labeled  $\theta$  and  $\phi$ . To the right of the BS is a 'Test antenna'. Blue arrows represent the signal path from the BS to the test antenna. Below the enclosure, a 'Positioner controller' and a 'PM/SG' (Phase and Magnitude Source/Generator) are connected to a 'PC'. The 'Positioner controller' is also connected to a mechanical assembly (labeled 1, 2, 3, 4) that appears to be part of the antenna positioning system.
+
+Diagram of CATR measurement system setup for EIRP accuracy in Extreme test conditions. The diagram shows a 'Radome like enclosure' containing a 'Temperature control system' and a 'Test system Calibrated point'. Inside the enclosure is an 'AAS BS' (Active Antenna System Base Station) with a coordinate reference point and orientation (theta, phi). A 'Test antenna' is positioned to receive signals from the BS. The 'Test system enclosure' contains a 'Positioner controller', a 'PM/SG' (Phase and Magnitude Source/Generator), and a 'PC'. The system is connected to a 'Test system Calibrated point' and a 'Test antenna'.
+
+Figure 7.3.2-1: CATR measurement system setup for EIRP accuracy in Extreme test conditions
+
+### 7.3.3 Test method limitations
+
+The maximum size of the BS is a chamber restriction that would affect the quality of the quiet zone. For larger BS sizes larger size chambers should be considered such that the uncertainty of the quiet zone is taken into account.
+
+The CATR is not suitable for low frequency measurements.
+
+## 7.4 One Dimensional Compact Range
+
+### 7.4.1 Measurement system description
+
+The principle of the One Dimensional Compact Range measurement setup is shown in figure 7.4.1-1. It closely resembles the standard compact range chamber. But for the generation of the plane wave in the quiet zone the proposed method uses a special one dimensional probe instead of the standard set up comprising a concave mirror and a feed
+
+horn. The main advantage is a reduced chamber size and a simplified probe system replacing the standard mirror feed horn set up.
+
+![Figure 7.4.1-1: One Dimensional Compact Range measurement system setup for EIRP accuracy. The diagram shows an anechoic chamber containing a Device under test (DUT) on a rotating stand connected to a Controller. To the right of the DUT is a 'Special quasi compact probe' which is an 'Antenna element' connected to a 'Feed system'. The feed system is connected to 'Measurement equipment' outside the chamber. A dashed arrow points from the DUT towards the probe.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg)
+
+Figure 7.4.1-1: One Dimensional Compact Range measurement system setup for EIRP accuracy. The diagram shows an anechoic chamber containing a Device under test (DUT) on a rotating stand connected to a Controller. To the right of the DUT is a 'Special quasi compact probe' which is an 'Antenna element' connected to a 'Feed system'. The feed system is connected to 'Measurement equipment' outside the chamber. A dashed arrow points from the DUT towards the probe.
+
+**Figure 7.4.1-1: One Dimensional Compact Range measurement system setup for EIRP accuracy**
+
+![Figure 7.4.1-2: One Dimensional Compact Range measurement system setup for OTA sensitivity. The diagram shows an anechoic chamber containing a 'Radiator' (Antenna element) connected to a 'Feed system', which is connected to a 'Signal Generator' outside the chamber. The radiator produces 'Plane wave or cylindrical wave fronts' (labeled 'Wave fronts'). A 'Device under test (DUT)' is positioned in the 'Measurement zone (Quiet zone)' between the radiator and the chamber wall. The DUT is connected to 'Measurement equipment' inside the chamber.](6031b46d356ee24f96bfe37ee2cb7616_img.jpg)
+
+Figure 7.4.1-2: One Dimensional Compact Range measurement system setup for OTA sensitivity. The diagram shows an anechoic chamber containing a 'Radiator' (Antenna element) connected to a 'Feed system', which is connected to a 'Signal Generator' outside the chamber. The radiator produces 'Plane wave or cylindrical wave fronts' (labeled 'Wave fronts'). A 'Device under test (DUT)' is positioned in the 'Measurement zone (Quiet zone)' between the radiator and the chamber wall. The DUT is connected to 'Measurement equipment' inside the chamber.
+
+**Figure 7.4.1-2: One Dimensional Compact Range measurement system setup for OTA sensitivity**
+
+The probe antenna is set up of a one dimensional array of antenna modules, connected by a special feed system. Optimized amplitude and phase settings in the feed system result in a plane wave in vertical direction. As no near field to far field transformation has to be carried out, it is not required to measure a whole set of azimuth and elevation angles.
+
+## 7.4.2 Test method limitations
+
+One Dimensional Compact Range test method is only suitable for BS whose *antenna array* consists of a single column *antenna array*. For a BS equipped with multi-column *antenna array*, this method would not be suitable due to the high amplitude uncertainty of edge column elements. High amplitude uncertainty makes testing of the declared steering angles not possible to meet EIRP accuracy requirements.
+
+## 7.5 Near Field Test Range
+
+### 7.5.1 Measurement system description
+
+The Near Field Test Range (NFTR) measurement techniques consist in measuring amplitude and phase of the modulated signal at the BS under test, on some specific surfaces such as planar, cylindrical, and spherical. Each of the near field test methods can be implemented by one or more mechanical rotations of the probe and/or BS under test as shown in figure 7.5.1. One or more mechanical movement can be substitute by a probe array. All the scanning methods will need an RF transmit and receive system equipped with an automated scanning, a data collection and control system, and computerized analysis ability.
+
+![Figure 7.5.1: Probe/scanner near field systems: spherical, cylindrical and planar. The figure shows three diagrams illustrating different near-field measurement setups. The first diagram shows a spherical probe (a sphere with a grid) positioned in front of a device under test (DUT). The second diagram shows a cylindrical probe (a cylinder with a grid) positioned in front of the DUT. The third diagram shows a planar probe (a flat grid) positioned in front of the DUT. Each diagram is enclosed in a dashed rectangular box with blue arrows pointing outwards, indicating the measurement area.](ef436853d3483f70254ae5fe1335a28b_img.jpg)
+
+Figure 7.5.1: Probe/scanner near field systems: spherical, cylindrical and planar. The figure shows three diagrams illustrating different near-field measurement setups. The first diagram shows a spherical probe (a sphere with a grid) positioned in front of a device under test (DUT). The second diagram shows a cylindrical probe (a cylinder with a grid) positioned in front of the DUT. The third diagram shows a planar probe (a flat grid) positioned in front of the DUT. Each diagram is enclosed in a dashed rectangular box with blue arrows pointing outwards, indicating the measurement area.
+
+**Figure 7.5.1: Probe/scanner near field systems: spherical, cylindrical and planar**
+
+NOTE: Although there are three methods available for obtaining the near field data, the spherical method is used as a working example.
+
+In case the radiated field is sampled on a sphere surrounding completely the BS under test, the 3D full sphere value of the measured parameter can be measured in near field when the BS is:
+
+- transmitting (for TX requirements) a defined modulated signals in a declared beam, or
+- receiving (for RX requirements) a defined modulated signals.
+
+The near field measurement technique would imply the use of mathematical artefact, NF to FF transform in order to have the measured parameter's value the in far field. The near field to far field transform is based on the well-known Huygens-Fresnel principle. The spherical modal wave expansion is the implicit application of the Huygens principle. A direct solution of the Helmholtz equations is found by applying boundary conditions on the surface  $S$  at infinity. From the tangential fields over the surface, the modal coefficients can be determined using the orthogonality of the modal expansion. Based on this formulation, the near field sampling criteria does play an important role.
+
+### 7.5.2 Test method limitations
+
+#### 7.5.2.1 OTA EVM measurement
+
+For BS implementations that point a beam in the EVM conformance direction during testing, the near field technique may report too high, but will never report too low EVM. In case the BS does not point a beam centre in the test direction, there is a risk of the near field technique report too low EVM.
+
+#### 7.5.2.2 OTA RX directional requirements
+
+There are some limitations on the use of that the BS must not have any BB beam forming. Considering that BS must have at least 8 TRX the probability of it meeting the restrictive conditions is small. In addition there are some issues surrounding the interference requirements when testing in the near field as the wanted and interfering signal may experience different beam forming.
+
+#### 7.5.2.3 OTA sensitivity measurement
+
+The near field test method is suitable for OTA sensitivity measurement of BS implementations where the beam forming is done on in a fixed or pre-set manner for the measured OSDD declaration, i.e. there is only one interface to
+
+digital/baseband processing. The near field test method is not suitable if for the measured OSDD declaration any combining is not fixed or preset. Some examples of architectures for which near field test method is possible and for which it is not possible are depicted on figure 7.5.2.3-2. The BS under test should not have any other non-linear behaviour that would cause the near field to far field transformation to fail or cause increased OTA sensitivity measurement uncertainty (for example, Automatic Gain Control if applicable must be disabled and the receiver dynamic range must be sufficient to prevent any increased measurement uncertainty due to the range of the near field values).
+
+![Figure 7.5.2.3-1: Examples of limit of OSDD functionality testable with near field test method for a single OSDD. The diagram shows two system architectures. The left architecture consists of a 'Digital/baseband processing' block connected to an 'Rx ADC' block, which is connected to an 'RXU' block, which is then connected to an 'RDN + AA' block. A dashed box labeled 'limit of OSDD functionality testable with Near field test method' encloses the 'Rx ADC', 'RXU', and 'RDN + AA' blocks. The right architecture consists of a 'Digital/baseband processing' block connected to a 'Fixed or preset Beamforming' block (highlighted in red), which is connected to four parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and all four 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'limit of OSDD functionality testable with Near field test method' encloses the 'Fixed or preset Beamforming', 'Rx ADC', 'RXU', and 'RDN + AA' blocks.](a9159a006d67a834a7b1a771c18191cc_img.jpg)
+
+Figure 7.5.2.3-1: Examples of limit of OSDD functionality testable with near field test method for a single OSDD. The diagram shows two system architectures. The left architecture consists of a 'Digital/baseband processing' block connected to an 'Rx ADC' block, which is connected to an 'RXU' block, which is then connected to an 'RDN + AA' block. A dashed box labeled 'limit of OSDD functionality testable with Near field test method' encloses the 'Rx ADC', 'RXU', and 'RDN + AA' blocks. The right architecture consists of a 'Digital/baseband processing' block connected to a 'Fixed or preset Beamforming' block (highlighted in red), which is connected to four parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and all four 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'limit of OSDD functionality testable with Near field test method' encloses the 'Fixed or preset Beamforming', 'Rx ADC', 'RXU', and 'RDN + AA' blocks.
+
+Figure 7.5.2.3-1: Examples of limit of OSDD functionality testable with near field test method for a single OSDD
+
+![Figure 7.5.2.3-2: Examples of limit of OSDD functionality not testable with near field test method for a single OSDD. The diagram shows two system architectures. The left architecture consists of a 'Digital/baseband processing' block connected to two parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and both 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'OSDD' encloses the 'Rx ADC', 'RXU', and 'RDN + AA' blocks. The right architecture consists of a 'Digital/baseband processing' block connected to a 'Fixed or preset Beamforming' block (highlighted in red), which is connected to four parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and all four 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'OSDD' encloses the 'Fixed or preset Beamforming', 'Rx ADC', 'RXU', and 'RDN + AA' blocks.](6707cae4df136f92a0c9f3a4676f91a6_img.jpg)
+
+Figure 7.5.2.3-2: Examples of limit of OSDD functionality not testable with near field test method for a single OSDD. The diagram shows two system architectures. The left architecture consists of a 'Digital/baseband processing' block connected to two parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and both 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'OSDD' encloses the 'Rx ADC', 'RXU', and 'RDN + AA' blocks. The right architecture consists of a 'Digital/baseband processing' block connected to a 'Fixed or preset Beamforming' block (highlighted in red), which is connected to four parallel 'Rx ADC' blocks. Each 'Rx ADC' block is connected to an 'RXU' block, and all four 'RXU' blocks are connected to a single 'RDN + AA' block. A dashed box labeled 'OSDD' encloses the 'Fixed or preset Beamforming', 'Rx ADC', 'RXU', and 'RDN + AA' blocks.
+
+Figure 7.5.2.3-2: Examples of limit of OSDD functionality not testable with near field test method for a single OSDD
+
+## 7.6 Plane Wave Synthesizer
+
+### 7.6.1 Measurement system description
+
+This method is an extension of a CATR measurement method as captured in clause 7.3, where the reflector is replaced by an *antenna array*, or Plane Wave Synthesizer (PWS), capable of approximating a plane wave within a specified quiet zone in front of the antenna in a similar manner as the reflector in a CATR system.
+
+The principle of the Plane Wave Synthesizer is shown in figure 7.6.1-1:
+
+![Diagram of PWS measurement setup for Tx requirements. A base station (BS) is shown with its antenna connector (B) connected to a measurement receiver (C). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.](5e9af8986a5845504f251d3079da8078_img.jpg)
+
+A: BS coordinate reference point  
+B: PWS antenna connector  
+C: Measurement receiver connector
+
+Diagram of PWS measurement setup for Tx requirements. A base station (BS) is shown with its antenna connector (B) connected to a measurement receiver (C). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.
+
+Figure 7.6.1-1: PWS measurement setup, Tx requirements
+
+![Diagram of PWS measurement setup for Rx requirements. A base station (BS) is shown with its antenna connector (B) connected to a signal generator (C). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.](f468e577645d646f5157ce3eefb4ed96_img.jpg)
+
+A: BS coordinate reference point  
+B: PWS antenna connector  
+C: Signal generator connector
+
+Diagram of PWS measurement setup for Rx requirements. A base station (BS) is shown with its antenna connector (B) connected to a signal generator (C). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.
+
+Figure 7.6.1-2: PWS measurement setup, Rx requirements
+
+![Diagram of PWS measurement setup for OTA dynamic range, ACS, blocking and ICS. A base station (BS) is shown with its antenna connector (B) connected to a power combiner. The power combiner is connected to two signal generators: one for the wanted signal (C) and one for AWGN/unwanted signal (D). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg)
+
+A: BS coordinate reference point  
+B: PWS antenna connector  
+C/D: Signal generator connector
+
+Diagram of PWS measurement setup for OTA dynamic range, ACS, blocking and ICS. A base station (BS) is shown with its antenna connector (B) connected to a power combiner. The power combiner is connected to two signal generators: one for the wanted signal (C) and one for AWGN/unwanted signal (D). The BS coordinate reference point (A) is indicated. The setup is enclosed in a blue jagged border representing an anechoic chamber.
+
+Figure 7.6.1-3: PWS measurement setup, OTA dynamic range, ACS, blocking and ICS
+
+![Figure 7.6.1-4: PWS measurement setup, Receiver intermodulation. The diagram shows a Base Station (BS) on a rotating turntable inside a chamber lined with blue triangular wave absorbers. A PWS antenna (B) is mounted on the BS. Signal generators (C, D, E) are connected to the PWS antenna connector (B) via a power combiner. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C/D/E: Signal generator connector. The signal generators are labeled 'Signal Generator (Wanted Signal)', 'Signal Generator (Interferer 1)', and 'Signal Generator (Interferer 2)'.](4b398c5e8c4fd656d5b7a61806400650_img.jpg)
+
+Figure 7.6.1-4: PWS measurement setup, Receiver intermodulation. The diagram shows a Base Station (BS) on a rotating turntable inside a chamber lined with blue triangular wave absorbers. A PWS antenna (B) is mounted on the BS. Signal generators (C, D, E) are connected to the PWS antenna connector (B) via a power combiner. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C/D/E: Signal generator connector. The signal generators are labeled 'Signal Generator (Wanted Signal)', 'Signal Generator (Interferer 1)', and 'Signal Generator (Interferer 2)'.
+
+**Figure 7.6.1-4: PWS measurement setup, Receiver intermodulation**
+
+The PWS typically consists of two main components: the *radiating elements* arranged in the structure of an array and the feeding system. The architecture of the latter depends on the adopted technology, e.g. it could be fed by a standard Beam Forming Network (BFN) or by an active system.
+
+Using similar technique of setting the phase and amplitude of the array signals, a quiet zone containing planar waves as a linear superposition of the *array elements'* spherical radiation waves can be created within the near field of the array.
+
+The PWS can achieve far-field testing conditions in a Quiet Zone (QZ) as in the case of CATRs it enables direct measurements of far-field BS performance in a controlled indoor environment as an alternative to CATR.
+
+## 7.6.2 Test method limitations
+
+The maximum rated Power Density (PD) per section of the PWS area (e.g. dBm/cm<sup>2</sup>) might be restricted depending on the implementation. This Power Density at a specific reference plane can be calculated for each BS as a function of the *total radiated power*, the test distance and the *radiation pattern* of the BS.
+
+## 7.7 General Chamber
+
+### 7.7.0 General
+
+The term general chamber has been used in 2 different ways during the analysis of the MU budgets the meaning of the term general chamber differs for the following requirement types:
+
+- Co-location requirements, as described in clause 7.7.1 and 7.7.2,
+- Out-of-band TRP requirements, as described in clause 7.7.3 and 7.7.4.
+
+For co-location requirements, the MU calculation focuses on the uncertainties between the test equipment, the CLTA and the DUT as such the precise chamber type is not relevant as such when calculation the MU it was referred to as a General Chamber meaning any of the available chamber types which are capable of performing the appropriate OTA measurement associated with the co-location requirements.
+
+For out-of-band spurious emissions and out-of-band blocking requirements the frequency range specified is very great (1 MHz to 12.75 GHz) as such many of the constraints on the band-specific chambers cannot be met, it is possible that multiple chambers may be required to cover the whole frequency range for example, so in this case the term General Chamber was used to imply a non-specific chamber that was capable of meeting the MU values specified.
+
+### 7.7.1 Measurement system description (co-location requirements)
+
+This section provides description of the chambers for the purpose of the co-location requirements measurements, i.e.
+
+- OTA transmitter OFF power,
+
+- OTA co-location spurious emissions,
+- OTA transmitter intermodulation, and
+- OTA co-location blocking.
+
+For more details on the co-location measurements, refer to clause 6.4.
+
+The General Chamber represents any suitable OTA chamber which shields the BS and CLTA from external interference and prevents reflections within the chamber from altering the coupling between the BS and the CLTA, i.e. any of the OTA measurement systems described in clauses 7.2 to 7.6 may be considered as example of the General Chamber.
+
+![Figure 7.7.1-1: General chamber test system set up diagram for co-location TX OFF and co-location emissions. The diagram shows a test system enclosure with a BS on a positioner and a Co-Location Test Antenna (CLTA) at a calibrated point. A Test antenna is connected to a Measurement receiver. A red line from the CLTA leads to a Switch, limiter or filter, which is then connected to a Measurement Device.](c0f64806753a053854921deb8f4fc798_img.jpg)
+
+The diagram illustrates the test system setup within a 'Test system enclosure' lined with electromagnetic wave absorbers. Inside, a 'BS' (Base Station) is mounted on a 'Positioner' that allows for rotation. A 'Calibrated point' is marked on the BS. The 'BS declared coordinate reference point and orientation' is indicated by a dashed line. A 'Co-Location Test Antenna' (CLTA) is positioned at the calibrated point. A 'Test antenna' is located outside the enclosure, connected to a 'Measurement receiver'. A red line from the CLTA leads to a 'Switch, limiter or filter', which is then connected to a 'Measurement Device'.
+
+Figure 7.7.1-1: General chamber test system set up diagram for co-location TX OFF and co-location emissions. The diagram shows a test system enclosure with a BS on a positioner and a Co-Location Test Antenna (CLTA) at a calibrated point. A Test antenna is connected to a Measurement receiver. A red line from the CLTA leads to a Switch, limiter or filter, which is then connected to a Measurement Device.
+
+**Figure 7.7.1-1: General chamber test system set up diagram for co-location TX OFF and co-location emissions**
+
+The OTA measurement receiver must be capable of conforming that the BS is radiating the wanted signal at the required power level, however the measurement is made at the output of the CLTA. The diagram shows a switch/limiter or filter which is used to reduce the level of the wanted signal before the requirement is measured in the measurement device.
+
+![Figure 7.7.1-2: General chamber test system set up diagram for co-location TX IMD. The diagram shows a test system enclosure with a BS (Base Station) and a Test antenna. The BS is mounted on a Positioner, which is connected to a Signal Generator for the interfering signal. The Test antenna is connected to a Measurement receiver. The BS is also connected to a Test system Calibrated point. The BS declared coordinate reference point and orientation is indicated. The diagram also shows the BS, Positioner, Co-Location Test Antenna, and Test system enclosure.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg)
+
+The diagram illustrates a general chamber test system setup for co-location TX IMD. It features a large rectangular 'Test system enclosure' with jagged edges representing the walls. Inside, a 'BS' (Base Station) is mounted on a 'Positioner' which can rotate it, as indicated by a curved arrow. A dashed vertical line marks the 'Test system Calibrated point'. Another dashed line indicates the 'BS declared coordinate reference point and orientation'. A 'Co-Location Test Antenna' is positioned near the BS. A red line connects the BS to a 'Signal Generator for the interfering signal' located outside the enclosure. To the right, a 'Test antenna' is mounted on the enclosure wall, connected to a 'Measurement receiver' outside. Angles  $\theta$  and  $\phi$  are shown relative to the calibrated point.
+
+Figure 7.7.1-2: General chamber test system set up diagram for co-location TX IMD. The diagram shows a test system enclosure with a BS (Base Station) and a Test antenna. The BS is mounted on a Positioner, which is connected to a Signal Generator for the interfering signal. The Test antenna is connected to a Measurement receiver. The BS is also connected to a Test system Calibrated point. The BS declared coordinate reference point and orientation is indicated. The diagram also shows the BS, Positioner, Co-Location Test Antenna, and Test system enclosure.
+
+**Figure 7.7.1-2: General chamber test system set up diagram for co-location TX IMD**
+
+The General Chamber represents any chamber capable of performing the OTA transmitter spurious emissions requirements, the OTA operating band unwanted emissions requirements and the OTA ACLR requirements to the specified accuracy.
+
+## 7.7.2 Test method limitations (co-location requirements)
+
+This method may be limited by the availability of suitable CLTA antenna.
+
+## 7.7.3 Measurement system description (out-of-band TRP requirements)
+
+This section provides description of the chambers for the purpose of the following Out-of-band TRP requirements:
+
+- Transmitter mandatory spurious emissions, see clause 12.2.2,
+- Receiver spurious emissions, see clause 12.3.2.
+- Out-of-band blocking, see clause 14.2.
+
+The General Chamber represents any suitable OTA chamber [capable of performing the out-of-band TRP requirements](#). Any OTA measurement systems may be considered as example of the General Chamber as long as the MU is within the specified value (or the test requirement is offset appropriately) and they are suitable for the frequencies being tested.
+
+## 7.7.4 Test method limitations (out-of-band TRP requirements)
+
+Test method limitations of the specific OTA chamber used apply, see clause 7.2.3, 7.3.3, 7.4.2, 7.5.2, 7.6.2, where applicable.
+
+# 7.8 Reverberation chamber
+
+## 7.8.1 Measurement system description
+
+A reverberation chamber (RC) is an electrically large shielded metal enclosure that employs one or several "stirring" methods to randomize the fields, such as moving paddles, turntables, etc. In this way, a large number of uncorrelated
+
+samples is obtained. The volume in the room where the field is well-stirred is the working volume. Here the E-field, averaged over an entire stirring cycle, is independent of the location in the room, i.e. the field is spatially uniform.
+
+For a proper analysis of the measured data a sufficient number of uncorrelated samples is required. The auto-correlation function is used to calculate the offset between statistically uncorrelated samples using the following expression as in IEC 61000-4-21 [11]:
+
+where the modulus operator  $\text{mod}(x,y)$  is the remainder of  $x/y$ , here performing a circular shift of the measurement samples over a distance  $k$ . The symbols  $\langle x \rangle$  and  $\sigma = \text{"std"}(x)$  denote the average value and standard deviation. The threshold value for uncorrelated samples,  $r_{\text{lim}}$ , is defined as in IEC 61000-4-21 [11]:
+
+The distance between uncorrelated samples is calculated as the minimum  $k$ -value satisfying . The number of uncorrelated samples is calculated as:
+
+$$N_{\text{ind}} = \frac{N}{k_{\text{lim}}}$$
+
+When properly designed, this facility can be used for non-directional antenna measurements, such as TRP. In fact, a well-stirred RC is capable of measuring TRP in a reliable way, regardless of the directivity pattern of the emission or frequency range. When measuring TRP of sources with a directive pattern, special care must be taken to characterize the working volume of the chamber.
+
+The purpose of the chamber characterization is to ensure that the effect of a non-uniform field distribution in the chamber has a negligible influence on the measurement result when the BS is placed in the working volume. Lack of chamber uniformity is a major contributor to measurement uncertainty in reverberation chambers and should be handled with care.
+
+The uniformity test can be quite time consuming and the test can be performed separate from the BS measurement. Due to the non-negligible size of BS equipment the BS can have a significant influence on the uniformity. To take this effect into account, either the BS itself must be present in the room during characterization or an absorber with dimensions equal or larger than the BS must be placed at the BS's location in the room.
+
+The characterization procedure consists of placing a reference transmitter antenna (REF TX ant) at different locations and with different orientations in the room and measuring the Power Transfer Function (PTF) between the REF TX and chamber's RX antenna, see figure 7.8.1-1. The actual mode of RC operation shall be used, including stirrer movement, BS movement, diversity antenna usage, etc. The directivity of the REF TX ant will influence the spatial uniformity of the room, a more directive REF TX ant is better at detecting parts of the room that are less-well stirred. Therefore, the REF TX ant chosen for the uniformity test should excite the chamber in a similar way as the BS.
+
+![Diagram of a reverberation chamber (RC) setup for characterization. The RC is a dashed rectangular box. Inside, a 'Stirrer' is on the left with a red circular arrow indicating rotation. A 'Working volume' is a dashed rectangle in the center, containing an 'RF Absorber' labeled 'size of max EUT'. Four corner markers 1, 2, 3, and 4 are at the corners of the working volume. 'REF TX' is at position 3, and 'RX' is at position 2. A blue arrow labeled 'Transfer function' points from REF TX to RX. Below the RC, a box labeled 'NA' (Network Analyzer) is connected to both REF TX and RX.](0931f3e098bd4539041de11c50cec2d2_img.jpg)
+
+Diagram of a reverberation chamber (RC) setup for characterization. The RC is a dashed rectangular box. Inside, a 'Stirrer' is on the left with a red circular arrow indicating rotation. A 'Working volume' is a dashed rectangle in the center, containing an 'RF Absorber' labeled 'size of max EUT'. Four corner markers 1, 2, 3, and 4 are at the corners of the working volume. 'REF TX' is at position 3, and 'RX' is at position 2. A blue arrow labeled 'Transfer function' points from REF TX to RX. Below the RC, a box labeled 'NA' (Network Analyzer) is connected to both REF TX and RX.
+
+**Figure 7.8.1-1: Setup for characterization of a reverberation chamber**
+
+The working volume shall be at least half a wavelength from the chamber walls and other electromagnetic reflective objects according to [12]. According to IEC 61000-4-21 [11] this distance may be restricted to 0.75 m below 100 MHz. The number of positions and orientations to use depends on the chamber size and the directivity of the REF TX ant. Measurements made at positions and orientations at the edges of the working volume are used to characterize the chamber and derive certain components of uncertainty.
+
+The exact number of positions and orientations remain for further study, but at least (3) uncorrelated locations should be used and (6) uncorrelated orientations per position when directive spurs are to be detected.
+
+Different test equipment set ups can be used for the acquisition of the PTF between REF TX and RX. Such as devices capable of directly extracting the PTF, like a Vector Network Analyzer (VNA) or a set up with separate transmitter and receiver test equipment, such as a Signal Generator (SG) and Spectrum/signal Analyzer (SA) configuration. In the latter case the operator should account for the losses in the set up originating from cables, mismatch, etc.
+
+When using a VNA, the REF TX ant and the measurement receive antenna (RX) are connected to the test equipment. For each location/orientation  $n$  of the REF TX ant, RC sample, and desired frequency  $f$ , the power transfer function
+
+is measured. The explicit dependence on RC sample and frequency is not written out here.
+
+In case of using a SG and SA the PTF is calculated as follows:
+
+with  $U_r$  the received voltage,  $50 \Omega$  being the reference impedance of the SA,  $P_t$  the transmit power of the signal source,  $L_s$  the losses in the cables,  $M_t$  the mismatch efficiency at the TX antenna calculated as .
+
+At least 250 uncorrelated samples shall be used per position/orientation. Using a lower number is not compatible with the underlying analysis on measurement uncertainty, see IEC 61000-4-21 [11] and publication in [13].
+
+The following tests are performed and shall be verified for each frequency:
+
+- a) Uniformity of transfer function: For each location/orientation evaluate  $P_n$ . The standard deviation of these average values shall be below the assumed measurement uncertainty level for A6-7 uncertainty contributor, as described in annex A.6.
+- b) Dynamic range: The dynamic range of each  $P_n$  shall be at least 20 dB.
+- c) Uncorrelated samples: At least 250 uncorrelated samples shall be used.
+
+It is important to note that spatial uniformity (and number of uncorrelated samples) in an RC is harder to achieve for more directive antenna patterns. As such, the measurement uncertainty of a sub-optimally configured room will be higher and additional measures to randomize the fields should be considered. Optimization of the BS position in the chamber and positional stirring are good starting points.
+
+## 7.8.2 Test method limitations
+
+The reverberation chamber test method is not suitable for testing spurious emissions at very low frequencies. The MU evaluation is applicable for the frequency above 380 MHz.
+
+---
+
+# 8 Measurement system calibration
+
+## 8.1 General
+
+Calibration of the OTA measurement systems is assumed to be the same for FR1 and FR2 frequencies, unless otherwise stated.
+
+## 8.2 Indoor Anechoic Chamber calibration
+
+Calibration shall be done to ensure that the SNR at the measurement equipment input is appropriate and the reception signal level at the measurement equipment is within the dynamic range of measurement equipment.
+
+- 1) Calibration system configuration
+
+For TX requirements: connect the reference antenna and the receiving antenna to the measurement RF out port and RF in port of the network analyzer, respectively, as shown in figure 8.2-1. The amplifier may be installed between C and D if required.
+
+![Diagram of an indoor anechoic chamber calibration system setup for TX requirements. The diagram shows a rectangular chamber with blue triangular wave absorbers on all four walls. Inside, a 'Reference antenna' is on the left and a 'Receiving antenna' is on the right. A dashed vertical line labeled 'A' passes through the center of the reference antenna, and another dashed vertical line labeled 'B' passes through the center of the receiving antenna. A connector labeled 'F' is on the reference antenna, and a connector labeled 'C' is on the receiving antenna. A cable connects connector 'F' to an external 'Network Analyzer' box. The Network Analyzer has an 'RF out' port labeled 'E' and an 'RF in' port labeled 'D'. A second cable connects connector 'C' to the 'RF in' port 'D' of the Network Analyzer. The labels E, F, A, B, C, D, and E are in red text in the original image.](719ef0f734259484038b2434e5dc3f24_img.jpg)
+
+E: Network analyzer output connector
+
+F: Reference antenna connector
+
+A: Phase centre of the reference antenna  
+(aligned to the reference point of AAS BS at DUT measurement)
+
+B: Phase centre of the receiving antenna
+
+C: Receiving antenna connector
+
+D: Network Analyzer input connection point  
+( the same as the measurement equipment connection point at DUT measurement)
+
+Diagram of an indoor anechoic chamber calibration system setup for TX requirements. The diagram shows a rectangular chamber with blue triangular wave absorbers on all four walls. Inside, a 'Reference antenna' is on the left and a 'Receiving antenna' is on the right. A dashed vertical line labeled 'A' passes through the center of the reference antenna, and another dashed vertical line labeled 'B' passes through the center of the receiving antenna. A connector labeled 'F' is on the reference antenna, and a connector labeled 'C' is on the receiving antenna. A cable connects connector 'F' to an external 'Network Analyzer' box. The Network Analyzer has an 'RF out' port labeled 'E' and an 'RF in' port labeled 'D'. A second cable connects connector 'C' to the 'RF in' port 'D' of the Network Analyzer. The labels E, F, A, B, C, D, and E are in red text in the original image.
+
+**Figure 8.2-1: Indoor Anechoic Chamber calibration system setup for TX requirements**
+
+For RX requirements: Connect the reference antenna and the transmitting antenna to RF in port and RF out port of the network analyzer, respectively, as shown in figure 8.2-2.
+
+![Diagram of an indoor anechoic chamber calibration system setup for RX requirements. The diagram shows a rectangular chamber with blue waveguide-like structures on the walls. Inside, a 'Reference antenna' is on the left and a 'Transmitting antenna' is on the right. Point A is the phase centre of the reference antenna, and point B is the phase centre of the transmitting antenna. Point F is the reference antenna connector, and point C is the transmitting antenna connector. A Network Analyzer is shown at the bottom, with 'RF in' connected to point E (Network analyzer input connector) and 'RF out' connected to point D (Network Analyzer output connection point). A cable connects point F to point E. Dashed lines indicate the alignment of the antennas and their phase centres.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg)
+
+E: Network analyzer input connector  
+F: Reference antenna connector  
+A: Phase centre of the reference antenna  
+(aligned to the reference point of AAS BS at DUT measurement)  
+B: Phase centre of the transmitting antenna  
+C: Transmitting antenna connector  
+D: Network Analyzer output connection point  
+(the same as the measurement equipment connection point at DUT measurement)
+
+Diagram of an indoor anechoic chamber calibration system setup for RX requirements. The diagram shows a rectangular chamber with blue waveguide-like structures on the walls. Inside, a 'Reference antenna' is on the left and a 'Transmitting antenna' is on the right. Point A is the phase centre of the reference antenna, and point B is the phase centre of the transmitting antenna. Point F is the reference antenna connector, and point C is the transmitting antenna connector. A Network Analyzer is shown at the bottom, with 'RF in' connected to point E (Network analyzer input connector) and 'RF out' connected to point D (Network Analyzer output connection point). A cable connects point F to point E. Dashed lines indicate the alignment of the antennas and their phase centres.
+
+**Figure 8.2-2: Indoor Anechoic Chamber calibration system setup for RX requirements**
+
+- 2) Install the reference antenna with its *beam peak direction* and the height of its phase centre aligned with the receiving antenna, or transmitting antenna (in case of transmitter or receiver requirement, respectively).
+- 3) Set the centre frequency of the network analyzer to the carrier centre frequency of the tested signal and measure  $LF_{E \rightarrow D}$ , which is equivalent to  $20\log|S_{21}|$  (dB) obtained by the network analyzer:
+  - $LF_{E \rightarrow D}$ : Pathloss between E and D in figure 8.2-1 (for Tx requirements) and 8.2-2 (for Rx requirements).
+- 4) Measure the cable loss,  $LF_{E \rightarrow F}$  between the reference antenna connector and the network analyzer connector:
+  - $LF_{E \rightarrow F}$ : Cable loss between E and F in figure 15.1-1.
+- 5) Calculate the calibration value between A and D with the following formulas:
+  - $L_{cal, A \rightarrow D} = LF_{E \rightarrow D} + G_{REF\_ANT, F \rightarrow A} - LF_{E \rightarrow F}$ .
+  - $L_{cal, A \rightarrow D}$ : Calibration value between A and D in figure 8.2-1 (for Tx requirements) and 8.2-2 (for Rx requirements).
+  - $G_{REF\_ANT, A \rightarrow F}$ : Antenna gain of the reference antenna.
+
+## 8.3 Compact Antenna Test Range calibration
+
+The calibration measurement is done by using a reference antenna (SGH used in figure 8.3-1 or 8.3-2) with known efficiency or gain values. In the calibration measurement the reference antenna is measured in the same place as the BS, and the attenuation of the complete transmission path ( $C \leftrightarrow A$ , as in figure 8.3-1 or 8.3-2) from the BS to the
+
+measurement receiver is calibrated out. Figures 8.3-1 and 8.3-2 presents a setup of a typical compact antenna test range for TX and RX requirements, respectively.
+
+![Diagram of CATR calibration system setup for TX requirements. It shows a DUT (Device Under Test) and a feed antenna inside a compact antenna test range (CATR) with reflectors. The system is controlled by a PC connected to a positioner controller and a PM/SG (Power Meter/Signal Generator).](f97535cdaa4fe017f4659512f4f78028_img.jpg)
+
+The diagram illustrates the CATR calibration system setup for TX requirements. It features a DUT (Device Under Test) and a feed antenna positioned within a compact antenna test range (CATR) defined by anechoic chamber walls (jagged lines). A coordinate system (x, y, z) is shown: z-axis points up, x-axis points right, and y-axis (indicated by a circle with a cross) points into the page. The DUT is mounted on a multi-axis positioner with numbered components (1, 2, 3, 4). A dashed vertical line labeled 'A' marks the reference plane of the DUT. The DUT transmits towards a parabolic 'Range antenna reflector', which reflects the signal to a 'Feed antenna'. The Feed antenna is connected to a 'PM/SG' (Power Meter/Signal Generator) unit. The PM/SG has a display and ports labeled 'C' and 'B'. The PM/SG is connected to a 'PC'. The PC is also connected to a 'Positioner controller', which in turn controls the DUT positioner. The entire test area is enclosed in an anechoic chamber.
+
+Diagram of CATR calibration system setup for TX requirements. It shows a DUT (Device Under Test) and a feed antenna inside a compact antenna test range (CATR) with reflectors. The system is controlled by a PC connected to a positioner controller and a PM/SG (Power Meter/Signal Generator).
+
+**Figure 8.3-1: CATR calibration system setup, TX requirements**
+
+![Diagram of the CATR calibration system setup. A large rectangular chamber with jagged walls represents the test environment. Inside, a 'Feed antenna' is on the right, and an 'SGH' (Standard Gain Horn) is on the left, mounted on a 'Positioner controller' which is connected to a 'PC'. A 'Network analyzer' is connected to the SGH via a cable. Point 'A' is a vertical dashed line near the SGH. Point 'B' is at the output of the network analyzer. Point 'C' is at the input of the network analyzer. Arrows indicate signal paths: from C to A, from A to B, and from the feed antenna to the SGH. A coordinate system (x, y, z) is shown in the center, with the z-axis pointing up, the x-axis pointing right, and the y-axis pointing into the page.](2f587210e4f97c32758c5972e2e83d20_img.jpg)
+
+Diagram of the CATR calibration system setup. A large rectangular chamber with jagged walls represents the test environment. Inside, a 'Feed antenna' is on the right, and an 'SGH' (Standard Gain Horn) is on the left, mounted on a 'Positioner controller' which is connected to a 'PC'. A 'Network analyzer' is connected to the SGH via a cable. Point 'A' is a vertical dashed line near the SGH. Point 'B' is at the output of the network analyzer. Point 'C' is at the input of the network analyzer. Arrows indicate signal paths: from C to A, from A to B, and from the feed antenna to the SGH. A coordinate system (x, y, z) is shown in the center, with the z-axis pointing up, the x-axis pointing right, and the y-axis pointing into the page.
+
+**Figure 8.3-2: CATR calibration system setup, RX requirements**
+
+1) Path loss calibration  $C \rightarrow A$ :
+
+- Measure SGH (or other calibrated reference antenna) reflection coefficient separately at the antenna's connector with a network analyser (or equivalent measurement equipment) to obtain  $\Gamma_{\text{SGH}}$ .
+- Measure cable loss from point C to input of SGH, call this  $L_{C \rightarrow \text{SGH}}$  which is the equivalent of  $20 \log |S_{21}|$  from the use of a network analyser.
+- Calculate the combined total path loss from  $C \rightarrow A$  by using the following expression:
+
+$$L_{\text{SGHcal}} = L_{C, \text{SGH}} + 10 \log(1 - |\Gamma_{\text{SGH}}|^2) - G_{\text{SGH}},$$
+
+where  $10 \log(1 - |\Gamma_{\text{SGH}}|^2)$  is the compensation for SGH connector return loss,  $G_{\text{SGH}}$  is the known gain of the reference SGH.
+
+- Connect SGH and  $C \leftrightarrow A$  cable.
+- To remove polarization(s) mismatch between range antenna (labelled as feeder antenna in diagram) and SGH use positions to position the SGH in the boresight of range antenna.
+- Measure path loss  $C \rightarrow B$  with network analyzer  $L_{C \rightarrow B} = 20 \log |S_{21}|$ .
+- Calculate the test path loss compensation factor. This is the total path loss between  $A \leftrightarrow B$  using the results from step 1c and 4.  $L = L_{\text{SGHcal}} - L_{C \rightarrow B}$ .
+
+Where  $\Gamma_{\text{SGH}}$  is the reflection coefficient (or mismatch) seen at the SGH connector ( $S_{11}$  with a network analyzer).
+
+The CATR test setup and calibration for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures. However, it is noted that in order to achieve the test instrument uncertainties that were assumed, calibration of the spectrum analyzer may be needed.
+
+## 8.4 One Dimensional Test Range calibration
+
+## 8.5 Near Field Test Range calibration
+
+Calibration accounts for the various factors affecting the measurements. These factors include components such as range length path loss, cable losses, gain of the receiving antenna, etc. Each measured data point for both radiated power and radiated sensitivity is transformed from a relative value in dB to an absolute value in dBm. For doing that the total path loss from the BS to the measurement receiver, named  $L_{path}$  loss is calibrated out. The calibration measurement is usually done by using a reference antenna with known gain. This approach is based on the so called gain-comparison method as in IEEE Standard Test Procedures for Antennas [7]. Figure 8.5-1 shows the typical configuration for measuring path loss.
+
+![Figure 8.5-1: Typical Lpath loss measurement configuration. The diagram shows a Source connected to a reference antenna (Gref, Piso) via a cable (A). The reference antenna is connected to a Measurement Antenna via a cable (B). The Measurement Antenna is connected to a Receiver. The path loss (Lpath) is indicated by a bracket over the distance between the reference antenna and the measurement antenna. The power levels are labeled as Psource at the source, Pref at the reference antenna input, Piso at the reference antenna output, Ptest at the measurement antenna output, Prec at the receiver input, and Psource at the source.](4537891530c9f6f139a2e1ebf544edc4_img.jpg)
+
+Figure 8.5-1: Typical Lpath loss measurement configuration. The diagram shows a Source connected to a reference antenna (Gref, Piso) via a cable (A). The reference antenna is connected to a Measurement Antenna via a cable (B). The Measurement Antenna is connected to a Receiver. The path loss (Lpath) is indicated by a bracket over the distance between the reference antenna and the measurement antenna. The power levels are labeled as Psource at the source, Pref at the reference antenna input, Piso at the reference antenna output, Ptest at the measurement antenna output, Prec at the receiver input, and Psource at the source.
+
+**Figure 8.5-1: Typical  $L_{path}$  loss measurement configuration**
+
+The  $L_{path}$  pathloss can be determined from the power into the reference antenna by adding the gain of the reference antenna:
+
+$$P_{iso} = P_{ref} + G_{ref}$$
+
+so that:
+
+$$L_{path} = P_{ref} + G_{ref} - P_{test}$$
+
+In order to determine  $P_{ref}$ , a cable reference measurement is performed in order to calibrate out the A, and B paths. Assuming that the power at the source is fixed, it can be showed that:
+
+$$P_{ref} - P_{test} = P_{rec}' - P_{rec}$$
+
+Where  $P_{rec}$  and  $P_{rec}'$  are the power measured at the receiver during the calibration measurement with the reference antenna and the power measured at the receiver during the cable reference measurement respectively.  $L_{path}$  loss is then given by:
+
+$$L_{path} = G_{ref} + P_{rec}' - P_{rec}$$
+
+## 8.6 Plane Wave Synthesizer calibration
+
+The calibration measurement is done by using a reference antenna with known efficiency or gain values (e.g. SGH). In the calibration measurement the reference antenna is measured in the same place as the BS, and the attenuation of the complete transmission path (C↔A, see figure 8.6-1) from the BS to the measurement receiver is calibrated out.
+
+![Figure 8.6-1: Path loss calibration in PWS, TX requirements. The diagram shows a test setup inside a chamber with blue triangular wave absorbers. On the left, a vertical horn antenna (SGH) is connected to a Network Analyzer at point E. On the right, a mobile device (UE) with a reference antenna (D) is positioned at point A. A cable connects point B (PWS antenna connector) on the UE to point C (Network Analyzer connector) on the Network Analyzer. The Network Analyzer is also connected to point E (Network analyzer connector) on the SGH. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg)
+
+Figure 8.6-1: Path loss calibration in PWS, TX requirements. The diagram shows a test setup inside a chamber with blue triangular wave absorbers. On the left, a vertical horn antenna (SGH) is connected to a Network Analyzer at point E. On the right, a mobile device (UE) with a reference antenna (D) is positioned at point A. A cable connects point B (PWS antenna connector) on the UE to point C (Network Analyzer connector) on the Network Analyzer. The Network Analyzer is also connected to point E (Network analyzer connector) on the SGH. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector.
+
+**Figure 8.6-1: Path loss calibration in PWS, TX requirements**
+
+![Figure 8.6-2: Path loss calibration in PWS, RX requirements. The diagram shows a test setup inside a chamber with blue triangular wave absorbers. On the left, a vertical horn antenna (SGH) is connected to a Network Analyzer at point E. On the right, a mobile device (UE) with a reference antenna (D) is positioned at point A. A cable connects point B (PWS antenna connector) on the UE to point C (Network Analyzer connector) on the Network Analyzer. The Network Analyzer is also connected to point E (Network analyzer connector) on the SGH. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector.](967e98a12645f89cb4a7620f42bf8c2e_img.jpg)
+
+Figure 8.6-2: Path loss calibration in PWS, RX requirements. The diagram shows a test setup inside a chamber with blue triangular wave absorbers. On the left, a vertical horn antenna (SGH) is connected to a Network Analyzer at point E. On the right, a mobile device (UE) with a reference antenna (D) is positioned at point A. A cable connects point B (PWS antenna connector) on the UE to point C (Network Analyzer connector) on the Network Analyzer. The Network Analyzer is also connected to point E (Network analyzer connector) on the SGH. The legend identifies: A: BS coordinate reference point; B: PWS antenna connector; C: Network Analyzer connector; D: Reference antenna connector; E: Network analyzer connector.
+
+**Figure 8.6-2: Path loss calibration in PWS, RX requirements**
+
+1) Path loss calibration E→A:
+
+- Measure SGH (or other calibrated reference antenna) reflection coefficient separately at the antenna's connector with a network analyzer (or equivalent measurement equipment) to obtain  $\Gamma_{\text{SGH}}$ .
+- Measure cable loss from point E to input of SGH, call this  $L_{\text{E}\rightarrow\text{SGH}}$  which is the equivalent of  $20\log|S_{21}|$  from the use of a network analyzer.
+- Calculate the combined total path loss from E→A by using the following expression:
+
+$$L_{\text{SGHcal}} = L_{\text{E,SGH}} + 10\log(1 - |\Gamma_{\text{SGH}}|^2) - G_{\text{SGH}}, \text{ where } 10\log(1 - |\Gamma_{\text{SGH}}|^2) \text{ is the compensation for SGH connector return loss, } G_{\text{SGH}} \text{ is the known gain of the reference SGH.}$$
+
+- Connect SGH and D↔E cable.
+- Measure path loss C→E with network analyzer  $L_{\text{C}\rightarrow\text{E}} = 20\log|S_{21}|$ .
+- Calculate the test path loss compensation factor. This is the total path loss between C↔A using the results from step 1c and 3.  $L = L_{\text{SGHcal}} - L_{\text{C}\rightarrow\text{E}}$ .
+
+Where  $\Gamma_{\text{SGH}}$  is the reflection coefficient (or mismatch) seen at the SGH connector ( $S_{11}$  with a network analyzer).
+
+## 8.7 General Chamber calibration (co-location requirements)
+
+The General Chamber here refers to the one described in clause 7.7.1.
+
+The OTA path of the General Chamber is calibrated according to its chamber type using the methodology in clause 8.2 to 8.6.
+
+![General chamber test system set up diagram for co-location TX OFF and co-location emissions. The diagram shows a test system enclosure with a BS (Base Station) on a positioner. A calibrated point is marked on the BS. The BS is oriented at an angle phi. A co-location test antenna is mounted on the BS. A measurement receiver is connected to the test antenna. A network analyzer is connected to the BS via a switch, limiter or filter. The network analyzer is connected to point B. The BS is connected to point A.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg)
+
+The diagram illustrates the test system setup for co-location TX OFF and co-location emissions. It features a 'Test system enclosure' lined with electromagnetic wave absorbers. Inside, a 'BS' (Base Station) is mounted on a 'Positioner' that can rotate it by an angle  $\phi$ . A 'Test system Calibrated point' is indicated on the BS. The 'BS declared coordinate reference point and orientation' is also shown. A 'Co-Location Test Antenna' is attached to the BS. A 'Measurement receiver' is connected to a 'Test antenna' located outside the enclosure. A 'Switch, limiter or filter' is connected to the BS and then to a 'Network Analyzer'. The Network Analyzer is connected to point 'B'. A line labeled 'A' connects the Network Analyzer to the BS.
+
+General chamber test system set up diagram for co-location TX OFF and co-location emissions. The diagram shows a test system enclosure with a BS (Base Station) on a positioner. A calibrated point is marked on the BS. The BS is oriented at an angle phi. A co-location test antenna is mounted on the BS. A measurement receiver is connected to the test antenna. A network analyzer is connected to the BS via a switch, limiter or filter. The network analyzer is connected to point B. The BS is connected to point A.
+
+Figure 8.7-1: General chamber test system set up diagram for co-location TX OFF and co-location emissions
+
+![Figure 8.7-2: General chamber test system set up diagram for co-location TX IMD. The diagram shows a test system enclosure with a BS (Base Station) and a Test antenna. The BS is connected to a Positioner and a Co-Location Test Antenna (CLTA). The CLTA is connected to a Network Analyzer via a cable. The Test antenna is connected to a Measurement receiver. The BS is also connected to a Test system Calibrated point. The BS declared coordinate reference point and orientation is indicated. The diagram also shows the BS and the Test antenna within the Test system enclosure. The Network Analyzer is connected to the CLTA at point A and point B. The Measurement receiver is connected to the Test antenna.](c07e21a8d65991db04263322f859c94f_img.jpg)
+
+Figure 8.7-2: General chamber test system set up diagram for co-location TX IMD. The diagram shows a test system enclosure with a BS (Base Station) and a Test antenna. The BS is connected to a Positioner and a Co-Location Test Antenna (CLTA). The CLTA is connected to a Network Analyzer via a cable. The Test antenna is connected to a Measurement receiver. The BS is also connected to a Test system Calibrated point. The BS declared coordinate reference point and orientation is indicated. The diagram also shows the BS and the Test antenna within the Test system enclosure. The Network Analyzer is connected to the CLTA at point A and point B. The Measurement receiver is connected to the Test antenna.
+
+**Figure 8.7-2: General chamber test system set up diagram for co-location TX IMD**
+
+The CLTA path is calibrated as follows:
+
+- 1) Cable and matching loss calibration for CLTA for each polarization supported by the CLTA
+  - a) Measure CLTA reflection coefficient separately at the antenna's connector with a network analyser (or equivalent measurement equipment) to obtain  $\Gamma_{ANT}$ .
+  - b) Measure cable loss from input of CLTA (A) to point B for TX OFF and co-location spurious emissions and from point B to input of CLTA (A) for TX IMD, call this  $L_{ANT \leftrightarrow F}$  which is the equivalent of  $20\log|S_{21}|$  from the use of a network analyser.
+  - c) Calculate the combined total path loss from F to CLTA using the following equation:
+
+$$L_{cal} = L_{ANT \leftrightarrow F} + 10\log(1 - |\Gamma_{ANT}|^2)$$
+
+## 8.7A General Chamber calibration (out-of-band TRP requirements)
+
+The General Chamber here refers to the one described in clause 7.7.3.
+
+The OTA path of the General Chamber is calibrated according to its chamber type using the methodology in clause 8.2 to 8.6.
+
+## 8.8 Reverberation chamber calibration
+
+To correctly determine the TRP by the BS a calibration step to account for losses in cables, antennas, etc. is required. A reference PTF is determined at each frequency of interest by using a relevant reference TX antenna (REF TX ant). The
+
+chamber should be set up identically to the actual set up of the TRP measurement, which means the BS has to be in the room, the same stirring procedure has to be used, etc.
+
+A minimum  $N_{ref} = 1$  reference measurement is required, but it is noted that more measurements can be used to estimate
+
+the reference PTF and that this will lead to a reduction of the uncertainty by a factor  $1/\sqrt{N_{ref}}$ . The radiation efficiency,  $\eta$ , of the reference antenna can be assumed to be the value declared by the manufacturer or can be determined in a separate antenna efficiency measurement.
+
+![Figure 8.8-1: The procedure for TRP measurements uses three consecutive setups: (a) Reference measurement, (b) ambient noise measurement, and (c) TRP measurement. The diagrams show a Reconfigurable Cavity (RC) with a stirrer, a Device Under Test (DUT), a reference transmitter (REF TX), and a receiver (RX). In (a), the DUT is OFF, and the REF TX is connected to a Network Analyser (NA). In (b), the DUT is ON, and the REF TX is connected to a terminator (TERM). In (c), the DUT is ON, and the REF TX is connected to a second reference transmitter (REF TX 2). Blue dots indicate the measurement planes.](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg)
+
+Figure 8.8-1: The procedure for TRP measurements uses three consecutive setups: (a) Reference measurement, (b) ambient noise measurement, and (c) TRP measurement. The diagrams show a Reconfigurable Cavity (RC) with a stirrer, a Device Under Test (DUT), a reference transmitter (REF TX), and a receiver (RX). In (a), the DUT is OFF, and the REF TX is connected to a Network Analyser (NA). In (b), the DUT is ON, and the REF TX is connected to a terminator (TERM). In (c), the DUT is ON, and the REF TX is connected to a second reference transmitter (REF TX 2). Blue dots indicate the measurement planes.
+
+**Figure 8.8-1: The procedure for TRP measurements uses three consecutive setups: (a) Reference measurement, (b) ambient noise measurement, and (c) TRP measurement. The blue dots indicate the measurement planes**
+
+Calibration procedure:
+
+- 1) Place the BS and the REF TX ant in the working volume of the RC. Turn off BS power and BS controls. See figure 8.8-1 (a). If more positions are used to determine the reference PTF the REF TX ant should be placed at uncorrelated positions within the test volume.
+- 2) Set the stirrers and turntables in the mode of operation used in the chamber characterization.
+- 3) Set the sampling rate as in the chamber characterization.
+- 4) Connect the REF TX ant and the RX antenna with a calibrated Network analyser (NA).
+- 5) Measure the scattering parameters or received power over a complete stirring cycle for each frequency of interest and for each position and orientation.
+- 6) Calculate the reference transfer function,  $P^{(r)}$ .
+- 7) Calculate the mis-match efficiency,  $M_1^{(r)}$ .
+
+## 9 TX directional requirements
+
+### 9.1 General
+
+Most TX directional requirements require demodulation of the transmitted signal using the "global in-channel TX test" as described e.g. in annex L of TS 38.141-2 [6] for NR.
+
+For simplicity since  $L_{path}$  requirements do not all use the same RAT-specific test models, the OTA test procedures have been kept general by using "applicable test signal" where the RAT-specific test models can be found in AAS BS or NR BS test specifications TS 37.145-2 [4] and TS 38.141-2 [6], respectively.
+
+Some requirements are differential and hence many of the calibration and OTA measurement uncertainties may cancel. These are investigated on a case by case basis.
+
+NOTE 1: All the calibration and test procedures are valid for FR1 as well as FR2, unless otherwise stated.
+
+NOTE 2: All the MU and TT values derivations are valid for Normal test conditions, unless otherwise stated.
+
+NOTE 3: The FR2 MU assessment was carried out using a CATR chamber only however other chamber types are not precluded if suitable MU assessment is done.
+
+## 9.2 EIRP accuracy, Normal test conditions
+
+### 9.2.1 General
+
+Clause 9.2 captures MU and TT values derivation for the EIRP accuracy directional requirement in Normal test conditions.
+
+For the MU and TT values derivation for the EIRP accuracy in Extreme test conditions, refer to clause 9.3.
+
+Specification of Normal and Extreme test conditions is captured in TS 38.141-2 [6] for NR BS (i.e. *BS type 1-O* and *BS type 2-O*), and in TS 37.145-2 [4] for OTA AAS BS.
+
+### 9.2.2 Indoor Anechoic Chamber
+
+#### 9.2.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 9.2.2.2 Test procedure
+
+##### 9.2.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for TX requirements depicted in figure 8.2-1.
+
+##### 9.2.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with the manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Set the BS to generate the tested beam with the *beam peak direction* intended to be the same as the testing direction.
+- 3) Rotate the BS to make the testing direction aligned with the direction of the receiving antenna.
+- 4) Set the BS to transmit the test signal at the maximum power according to applicable test model.
+- 5) Measure the mean power for each carrier arriving at the measurement equipment connector, denoted by  $P_{R\_EIRP, D}$ , which is defined as measured mean power for each carrier at the measurement equipment connector at the reference point D in figure 7.2.1-1.
+- 6) Calculate the EIRP with the following formula:
+
+$$EIRP = P_{R\_EIRP, D} + L_{EIRP\_cal, A \rightarrow D}$$
+
+- 7) Calculate total EIRP =  $EIRP_{p1} + EIRP_{p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+- 8) Repeat the above steps 2 - 7 per conformance test *beam direction pair*.
+
+### 9.2.2.3 MU value derivation, FR1
+
+Table 9.2.2.3-1 captures uncertainty budget contributors and table 9.2.2.3-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 9.2.2.3-1: Indoor Anechoic Chamber measurement uncertainty contributors for EIRP accuracy measurements, Normal test conditions, FR1**
+
+| UID / Details in annex                  | Uncertainty source                                                                            |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------|
+| <b>Stage 2: BS measurement</b>          |                                                                                               |
+| A1-1                                    | Positioning misalignment between the BS and the reference antenna                             |
+| A1-2                                    | Pointing misalignment between the BS and the receiving antenna                                |
+| A1-3                                    | Quality of quiet zone                                                                         |
+| A1-4a                                   | Polarization mismatch between the BS and the receiving antenna                                |
+| A1-5a                                   | Mutual coupling between the BS and the receiving antenna                                      |
+| A1-6                                    | Phase curvature                                                                               |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)       |
+| A1-7                                    | Impedance mismatch in the receiving chain                                                     |
+| A1-8                                    | Random uncertainty                                                                            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                               |
+| A1-9                                    | Impedance mismatch between the receiving antenna and the network analyzer                     |
+| A1-10                                   | Positioning and pointing misalignment between the reference antenna and the receiving antenna |
+| A1-11                                   | Impedance mismatch between the reference antenna and the network analyzer.                    |
+| A1-3                                    | Quality of quiet zone                                                                         |
+| A1-4b                                   | Polarization mismatch between the reference antenna and the receiving antenna                 |
+| A1-5                                    | Mutual coupling between the reference antenna and the receiving antenna                       |
+| A1-6                                    | Phase curvature                                                                               |
+| C1-3                                    | Uncertainty of the network analyzer                                                           |
+| A1-12                                   | Influence of the reference antenna feed cable                                                 |
+| A1-13                                   | Reference antenna feed cable loss measurement uncertainty                                     |
+| A1-14                                   | Influence of the receiving antenna feed cable                                                 |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                     |
+| A1-15                                   | Uncertainty of the absolute gain of the receiving antenna                                     |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.2.3-2: Indoor Anechoic Chamber measurement uncertainty value derivation for EIRP accuracy measurements, Normal test conditions, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                                          |                                                                                               | f < 3 GHz              | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |                                 |                                     |                | f < 3 GHz                                | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                                                                     | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                                                                     | Pointing misalignment between the BS and the receiving antenna                                | 0.3                    | 0.3             | 0.3             | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-3                                                                                     | Quality of quiet zone                                                                         | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4a                                                                                    | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                                                                    | Mutual coupling between the BS and the receiving antenna                                      | 0                      | 0               | 0               | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                                     | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)       | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A1-7                                                                                     | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                                                                     | Random uncertainty                                                                            | 0.1                    | 0.1             | 0.1             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                                                                     | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                                                                    | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                                                                    | Impedance mismatch between the reference antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                                                                     | Quality of quiet zone                                                                         | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                                                                    | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                                                                    | Mutual coupling between the reference antenna and the receiving antenna                       | 0                      | 0               | 0               | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                                     | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                           | 0.13                   | 0.2             | 0.2             | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                                                                    | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                                                                    | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                                                                    | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                                                                    | Uncertainty of the absolute gain of the receiving antenna                                     | 0                      | 0               | 0               | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.44</b>                              | <b>0.54</b>     | <b>0.54</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.87</b>                              | <b>1.06</b>     | <b>1.06</b>     |
+
+## 9.2.3 Compact Antenna Test Range
+
+### 9.2.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.2.3.2 Test procedure
+
+#### 9.2.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3 with the calibration system setup for TX requirements depicted in figure 8.3-1.
+
+#### 9.2.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with *beam peak direction* of range antenna.
+- 2) Configure TX branch and carrier according to maximum power requirement and test configuration.
+- 3) Set the BS to transmit the test signal according to applicable test model.
+- 4) Measure mean power ( $P_{\text{meas}}$ ) of each carrier arriving at the measurement equipment (such as a spectrum analyzer or power meter) denoted in figure 8.3-1.
+- 5) Calculate EIRP, where  $\text{EIRP} = P_{\text{meas}} + L_{A \rightarrow B}$ .
+- 6) Calculate total EIRP =  $\text{EIRP}_{p1} + \text{EIRP}_{p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+- 7) Repeat steps 2 - 6 for all conformance test *beam direction pairs*.
+
+### 9.2.3.3 MU value derivation, FR1
+
+Table 9.2.3.3-1 captures uncertainty budget contributors and Table 9.2.3.3-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in CATR (Normal test conditions, FR1).
+
+**Table 9.2.3.3-1: CATR measurement uncertainty contributors for EIRP accuracy measurements, Normal test conditions, FR1**
+
+| UID / Details in annex                  | Uncertainty source                                                                      |
+|-----------------------------------------|-----------------------------------------------------------------------------------------|
+| <b>Stage 2: BS measurement</b>          |                                                                                         |
+| A2-1a                                   | Misalignment and pointing error of BS (for EIRP)                                        |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) |
+| A2-2a                                   | Standing wave between BS and test range antenna                                         |
+| A2-3                                    | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   |
+| A2-4a                                   | QZ ripple experienced by BS                                                             |
+| A2-12                                   | Frequency flatness of test system                                                       |
+| <b>Stage 1: Calibration measurement</b> |                                                                                         |
+| C1-3                                    | Uncertainty of the network analyzer                                                     |
+| A2-5a                                   | Mismatch of receiver chain between receiving antenna and measurement receiver           |
+| A2-6                                    | Insertion loss of receiver chain                                                        |
+| A2-3                                    | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   |
+| A2-7                                    | Influence of the calibration antenna feed cable                                         |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                               |
+| A2-8                                    | Misalignment positioning system                                                         |
+| A2-1b                                   | Misalignment and pointing error of calibration antenna                                  |
+| A2-9                                    | Rotary joints                                                                           |
+| A2-2b                                   | Standing wave between calibration antenna and test range antenna                        |
+
+|       |                                              |
+|-------|----------------------------------------------|
+| A2-4b | QZ ripple experienced by calibration antenna |
+| A2-11 | Switching uncertainty                        |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.3.3-2: CATR MU value derivation for EIRP accuracy measurements, Normal test conditions, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                  |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 G Hz             | 3 < f ≤ 4.2 G Hz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                  |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-1a                                                                  | Misalignment and pointing error of BS (for EIRP)                                        | 0.00                   | 0.00             | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26             | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                         | 0.21                   | 0.21             | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00             | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                             | 0.09                   | 0.09             | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A2-12                                                                  | Frequency flatness of test system                                                       | 0.25                   | 0.25             | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                  |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20             | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver           | 0.13                   | 0.33             | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18             | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00             | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                         | 0.02                   | 0.02             | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43             | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A2-8                                                                   | Misalignment positioning system                                                         | 0.00                   | 0.00             | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna                                  | 0.50                   | 0.50             | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| A2-9                                                                   | Rotary joints                                                                           | 0.05                   | 0.05             | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                        | 0.09                   | 0.09             | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                            | 0.01                   | 0.01             | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A2-11                                                                  | Switching uncertainty                                                                   | 0.26                   | 0.26             | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                  |                 |                                 |                                     |                | <b>0.57</b>                              | <b>0.65</b>     | <b>0.65</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                  |                 |                                 |                                     |                | <b>1.11</b>                              | <b>1.27</b>     | <b>1.27</b>     |
+
+### 9.2.3.4 MU value derivation, FR2
+
+The MU assessment was carried out using a CATR chamber only however other chamber types are not precluded if suitable MU assessment is done.
+
+A CATR MU budget was assessed in order to determine acceptable MU for the EIRP accuracy measurement in FR2. The CATR test setup and calibration and measurement procedures for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures.
+
+Table 9.2.3.4-1 captures the uncertainty budget contributors and table 9.2.3.4-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in CATR (Normal test conditions, FR2).
+
+**Table 9.2.3.4-1: CATR measurement uncertainty contributors for EIRP accuracy measurements, Normal test conditions, FR2**
+
+| UID / Details in annex                  | Uncertainty source                                                                                   |
+|-----------------------------------------|------------------------------------------------------------------------------------------------------|
+| <b>Stage 2: BS measurement</b>          |                                                                                                      |
+| A2-1a                                   | Misalignment and pointing error of BS (for EIRP)                                                     |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power |
+| A2-2a                                   | Standing wave between BS and test range antenna                                                      |
+| A2-3                                    | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                |
+| A2-4a                                   | QZ ripple experienced by BS                                                                          |
+| A2-12                                   | Frequency flatness of test system                                                                    |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                      |
+| C1-3                                    | Uncertainty of the network analyzer                                                                  |
+| A2-5a                                   | Mismatch of receiver chain between receiving antenna and measurement receiver                        |
+| A2-6                                    | Insertion loss of receiver chain                                                                     |
+| A2-3                                    | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                |
+| A2-7                                    | Influence of the calibration antenna feed cable                                                      |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                            |
+| A2-8                                    | Misalignment positioning system                                                                      |
+| A2-1b                                   | Misalignment and pointing error of calibration antenna (for EIRP)                                    |
+| A2-9                                    | Rotary joints                                                                                        |
+| A2-2b                                   | Standing wave between calibration antenna and test range antenna                                     |
+| A2-4b                                   | QZ ripple experienced by calibration antenna                                                         |
+| A2-11                                   | Switching uncertainty                                                                                |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.3.4-2: CATR MU value derivation for EIRP accuracy measurements, Normal test conditions, FR2**
+
+| UID                                                                                      | Uncertainty source                                                                                   | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution on shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|----------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                                          |                                                                                                      | 24.25 < f < 29.5 GHz   | 37 < f < 43.5 GHz |                                 |                                        |                | 24.25 < f < 29.5 GHz                     | 37 < f < 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                      |                        |                   |                                 |                                        |                |                                          |                   |
+| A2-1a                                                                                    | Misalignment and pointing error of BS (for EIRP)                                                     | 0.20                   | 0.20              | Exp. normal                     | 2.00                                   | 1              | 0.10                                     | 0.10              |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power | 0.50                   | 0.70              | Normal                          | 1.00                                   | 1              | 0.50                                     | 0.70              |
+| A2-2a                                                                                    | Standing wave between BS and test range antenna                                                      | 0.03                   | 0.03              | U-shaped                        | 1.41                                   | 1              | 0.02                                     | 0.02              |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01              | Normal                          | 1.00                                   | 1              | 0.01                                     | 0.01              |
+| A2-4a                                                                                    | QZ ripple experienced by BS                                                                          | 0.40                   | 0.40              | Normal                          | 1.00                                   | 1              | 0.40                                     | 0.40              |
+| A2-12                                                                                    | Frequency flatness of test system                                                                    | 0.25                   | 0.25              | Normal                          | 1.00                                   | 1              | 0.25                                     | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                      |                        |                   |                                 |                                        |                |                                          |                   |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                                  | 0.30                   | 0.30              | Normal                          | 1.00                                   | 1              | 0.30                                     | 0.30              |
+| A2-5a                                                                                    | Mismatch of receiver chain between receiving antenna and measurement receiver                        | 0.43                   | 0.57              | U-shaped                        | 1.41                                   | 1              | 0.30                                     | 0.40              |
+| A2-6                                                                                     | Insertion loss of receiver chain                                                                     | 0.00                   | 0.00              | Rectangular                     | 1.73                                   | 1              | 0.00                                     | 0.00              |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01              | Normal                          | 1.00                                   | 1              | 0.01                                     | 0.01              |
+| A2-7                                                                                     | Influence of the calibration antenna feed cable                                                      | 0.21                   | 0.29              | U-shaped                        | 1.41                                   | 1              | 0.15                                     | 0.21              |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                                            | 0.52                   | 0.52              | Rectangular                     | 1.73                                   | 1              | 0.30                                     | 0.30              |
+| A2-8                                                                                     | Misalignment positioning system                                                                      | 0.00                   | 0.00              | Exp. normal                     | 2.00                                   | 1              | 0.00                                     | 0.00              |
+| A2-1b                                                                                    | Misalignment and pointing error of calibration antenna (for EIRP)                                    | 0.00                   | 0.00              | Exp. normal                     | 2.00                                   | 1              | 0.00                                     | 0.00              |
+| A2-9                                                                                     | Rotary joints                                                                                        | 0.00                   | 0.00              | U-shaped                        | 1.41                                   | 1              | 0.00                                     | 0.00              |
+| A2-2b                                                                                    | Standing wave between calibration antenna and test range antenna                                     | 0.09                   | 0.09              | U-shaped                        | 1.41                                   | 1              | 0.06                                     | 0.06              |
+| A2-4b                                                                                    | QZ ripple experienced by calibration antenna                                                         | 0.01                   | 0.01              | Normal                          | 1.00                                   | 1              | 0.01                                     | 0.01              |
+| A2-11                                                                                    | Switching uncertainty                                                                                | 0.10                   | 0.10              | Rectangular                     | 1.73                                   | 1              | 0.06                                     | 0.06              |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                                      |                        |                   |                                 |                                        |                | <b>0.89</b>                              | <b>1.06</b>       |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                      |                        |                   |                                 |                                        |                | <b>1.74</b>                              | <b>2.07</b>       |
+
+## 9.2.4 One Dimensional Compact Range
+
+### 9.2.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.4.1.
+
+### 9.2.4.2 Test procedure
+
+#### 9.2.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the One Dimensional Compact Range is captured in clause 8.4.
+
+### 9.2.4.2.2 Stage 2: BS measurement
+
+The One Dimensional Compact Range testing procedure consists of the following steps:
+
+- 1) Connect the receive network of the compact probe to the measurement equipment.
+- 2) Calibrate the test range, using a reference antenna with standard gain installed in the quiet zone of the probe and measure the path loss between reference antenna and the measurement equipment.
+- 3) Install the BS in the quiet zone of the probe with its manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with testing system.
+- 4) Align with the required conformance steering directions.
+- 5) Set the BS to transmit at maximum EIRP appropriate to conformance steering directions according to the manufacturer declaration.
+- 6) Measure the received power at the probe and thus the EIRP of the BS.
+- 7) Calculate total EIRP =  $EIRP_{p1} + EIRP_{p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+- 8) Repeat test steps 2 - 7 for all declared beams and corresponding conformance steering directions.
+
+### 9.2.4.3 MU value derivation, FR1
+
+Table 9.2.4.3-1 captures the uncertainty budget contributors and table 9.2.4.3-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in One Dimensional Compact Range.
+
+**Table 9.2.4.3-1: One Dimensional Compact Range measurement accuracy contributors for EIRP accuracy measurements, FR1**
+
+| UID / Details in annex                  | Uncertainty source                                                                                             |
+|-----------------------------------------|----------------------------------------------------------------------------------------------------------------|
+| <b>Stage 2: BS measurement</b>          |                                                                                                                |
+| A4-1                                    | Misalignment and pointing error of BS                                                                          |
+| A4-2a                                   | Standing wave between BS and test range antenna                                                                |
+| A4-3a                                   | Quiet zone ripple experienced by BS                                                                            |
+| A4-4a                                   | Phase curvature across the BS antenna                                                                          |
+| A4-5a                                   | Polarization mismatch between BS and receiving antenna                                                         |
+| A4-6a                                   | Mutual coupling between BS and receiving antenna                                                               |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                        |
+| A4-7                                    | Impedance mismatch in receiving chain                                                                          |
+| A4-8a                                   | RF leakage (BS connector terminated and test range antenna connector cable terminated)                         |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                                |
+| A4-9                                    | Misalignment positioning system                                                                                |
+| A4-10                                   | Pointing error between reference antenna and test range antenna                                                |
+| A4-11                                   | Impedance mismatch in path to reference antenna                                                                |
+| A4-12                                   | Impedance mismatch in path to compact probe                                                                    |
+| A4-2b                                   | Standing wave between reference antenna and receiving antenna                                                  |
+| A4-3b                                   | Quiet zone ripple experienced by reference antenna                                                             |
+| A4-4b                                   | Phase curvature across the reference antenna                                                                   |
+| A4-5b                                   | Polarization mismatch between reference antenna and receiving antenna                                          |
+| A4-6b                                   | Mutual coupling between reference antenna and receiving antenna                                                |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                        |
+| A4-13                                   | Influence of the reference antenna feed cable (flexing cables, adapters, attenuators, connector repeatability) |
+| A4-14                                   | Mismatch of receiver chain                                                                                     |
+| A4-15                                   | Insertion loss of receiver chain                                                                               |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                                      |
+| A4-8b                                   | RF leakage (SGH connector terminated and test range antenna connector cable terminated)                        |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.4.3-2: One Dimensional Compact Range MU value derivation for EIRP accuracy measurements, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                                             | Uncertainty value (dB) |                 |                  | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------|-----------------|------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                                                                          |                                                                                                                | f < 3 G Hz             | 3 < f < 4.2 GHz | 4.2 < f < 6 G Hz |                                 |                                     |                | f < 3 G Hz                               | 3 < f < 4.2 G Hz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                                |                        |                 |                  |                                 |                                     |                |                                          |                  |                 |
+| A4-1                                                                                     | Misalignment and pointing error of BS                                                                          | 0.00                   | 0.00            | 0.00             | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A4-2a                                                                                    | Standing wave between BS and test range antenna                                                                | 0.18                   | 0.18            | 0.18             | U-shaped                        | 1.41                                | 1              | 0.13                                     | 0.13             | 0.13            |
+| A4-3a                                                                                    | Quiet zone ripple experienced by BS                                                                            | 0.03                   | 0.03            | 0.03             | Gaussian                        | 1.00                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| A4-4a                                                                                    | Phase curvature across the BS antenna                                                                          | 0.01                   | 0.01            | 0.01             | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| A4-5a                                                                                    | Polarization mismatch between BS and receiving antenna                                                         | 0.05                   | 0.05            | 0.05             | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| A4-6a                                                                                    | Mutual coupling between BS and receiving antenna                                                               | 0.00                   | 0.00            | 0.00             | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                        | 0.14                   | 0.26            | 0.26             | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26             | 0.26            |
+| A4-7                                                                                     | Impedance mismatch in receiving chain                                                                          | 0.01                   | 0.01            | 0.01             | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.01             | 0.01            |
+| A4-8a                                                                                    | RF leakage (BS connector terminated and test range antenna connector cable terminated)                         | 0.00                   | 0.00            | 0.00             | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                                |                        |                 |                  |                                 |                                     |                |                                          |                  |                 |
+| A4-9                                                                                     | Misalignment positioning system                                                                                | 0.00                   | 0.00            | 0.00             | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A4-10                                                                                    | Pointing error between reference antenna and test range antenna                                                | 0.00                   | 0.00            | 0.00             | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A4-11                                                                                    | Impedance mismatch in path to reference antenna                                                                | 0.05                   | 0.05            | 0.05             | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04             | 0.04            |
+| A4-12                                                                                    | Impedance mismatch in path to compact probe                                                                    | 0.03                   | 0.03            | 0.03             | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| A4-2b                                                                                    | Standing wave between reference antenna and receiving antenna                                                  | 0.09                   | 0.09            | 0.09             | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| A4-3b                                                                                    | Quiet zone ripple experienced by reference antenna                                                             | 0.18                   | 0.18            | 0.18             | Gaussian                        | 1.00                                | 1              | 0.18                                     | 0.18             | 0.18            |
+| A4-4b                                                                                    | Phase curvature across the reference antenna                                                                   | 0.00                   | 0.00            | 0.00             | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A4-5b                                                                                    | Polarization mismatch between reference antenna and receiving antenna                                          | 0.05                   | 0.05            | 0.05             | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| A4-6b                                                                                    | Mutual coupling between reference antenna and receiving antenna                                                | 0.00                   | 0.00            | 0.00             | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                        | 0.14                   | 0.26            | 0.26             | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26             | 0.26            |
+| A4-13                                                                                    | Influence of the reference antenna feed cable (flexing cables, adapters, attenuators, connector repeatability) | 0.08                   | 0.08            | 0.08             | Rectangular                     | 1.73                                | 1              | 0.05                                     | 0.05             | 0.05            |
+| A4-14                                                                                    | Mismatch of receiver chain                                                                                     | 0.20                   | 0.30            | 0.30             | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.21             | 0.21            |
+| A4-15                                                                                    | Insertion loss of receiver chain                                                                               | 0.18                   | 0.18            | 0.18             | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10             | 0.10            |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                                                      | 0.50                   | 0.43            | 0.43             | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25            |
+| A4-8b                                                                                    | RF leakage (SGH connector terminated and test range antenna connector cable terminated)                        | 0.00                   | 0.00            | 0.00             | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                                                |                        |                 |                  |                                 |                                     |                | <b>0.46</b>                              | <b>0.56</b>      | <b>0.56</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                                |                        |                 |                  |                                 |                                     |                | <b>0.90</b>                              | <b>1.10</b>      | <b>1.10</b>     |
+
+## 9.2.5 Near Field Test Range
+
+### 9.2.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+### 9.2.5.2 Test procedure
+
+#### 9.2.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 9.2.5.2.2 Stage 2: BS measurement
+
+The Near Field Test Range testing procedure consists of the following steps:
+
+- 1) BS near field *radiation pattern* measurement: this is performed with the BS transmitting a defined modulated signal, as defined in appropriate conformance test specification.
+- 2) BS near field to far field transformation: the near field power calibration is applied.
+
+The near field to far field transformation is a mathematical computation which is applied to the near field measured *radiation pattern* in order to compute the far field *radiation pattern*. It is typically performed expanding the measured near field over a set of orthogonal basis functions. The near to far field transform is then performed in two steps:
+
+- 1) Expansion (or projection) of the measured near field (i.e.  $E_{meas}(r)$ ) over a set of orthogonal basis functions (i.e.  $F_{basis}(r)$ ) in order to evaluate the transformed spectrum:
+
+$$E_{meas}(r) = \text{Spectrum} * F_{basis}(r)$$
+
+- 2) FF (i.e.  $E_{FF}$ ) computation using the previously calculated spectrum and with the basis functions evaluated at  $r \rightarrow \infty$  (i.e.  $F_{basis}(r \rightarrow \infty)$ ):
+
+$$E_{FF} = \text{Spectrum} * F_{basis}(r \rightarrow \infty)$$
+
+When performing the near field to far field transformation, the gain calibration is applied so that the near field pattern will be transformed from relative power (i.e. dB) to absolute power (i.e. dBm). In this specific case, the EIRP far field pattern is expressed in terms of the absolute power radiated by the BS in the declared beam:
+
+- 1) BS radiated transmit power: once the full 3D far field EIRP pattern has been computed, the radiated transmit power can be derived.
+
+### 9.2.5.3 MU value derivation, FR1
+
+Table 9.2.5.3-1 captures the uncertainty budget contributors and table 9.2.5.3-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in Near Field Test Range.
+
+Standard uncertainty values for the signal generator, network analyzer and reference antenna are according to the test equipment uncertainty values, as captured in annex C.
+
+**Table 9.2.5.3-1: NFTR measurement accuracy contributors for EIRP accuracy measurements, FR1**
+
+| UID / Details in annex  | Uncertainty source                 |
+|-------------------------|------------------------------------|
+| Stage 2: BS measurement |                                    |
+| A3-1                    | Axes intersection                  |
+| A3-2                    | Axes orthogonality                 |
+| A3-3                    | Horizontal pointing                |
+| A3-4                    | Probe vertical position            |
+| A3-5                    | Probe horizontal/vertical pointing |
+| A3-6                    | Measurement distance               |
+| A3-7                    | Amplitude and phase drift          |
+| A3-8                    | Amplitude and phase noise          |
+| A3-9                    | Leakage and crosstalk              |
+| A3-10                   | Amplitude non-linearity            |
+
+|                                         |                                                                                         |
+|-----------------------------------------|-----------------------------------------------------------------------------------------|
+| A3-11                                   | Amplitude and phase shift in rotary joints                                              |
+| A3-12                                   | Channel balance amplitude and phase                                                     |
+| A3-13                                   | Probe polarization amplitude and phase                                                  |
+| A3-14                                   | Probe pattern knowledge                                                                 |
+| A3-15                                   | Multiple Reflections                                                                    |
+| A3-16                                   | Room scattering                                                                         |
+| A3-17                                   | BS support scattering                                                                   |
+| A3-18                                   | Scan area truncation                                                                    |
+| A3-19                                   | Sampling point offset                                                                   |
+| A3-20                                   | Spherical mode truncation                                                               |
+| A3-21                                   | Positioning                                                                             |
+| A3-22                                   | Probe array uniformity                                                                  |
+| A3-23                                   | Mismatch of receiver chain                                                              |
+| A3-24                                   | Insertion loss of receiver chain                                                        |
+| A3-25                                   | Uncertainty of the absolute gain of the probe antenna                                   |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) |
+| A3-26                                   | Measurement repeatability - positioning repeatability                                   |
+| A3-33                                   | Frequency flatness of test system                                                       |
+| <b>Stage 1: Calibration measurement</b> |                                                                                         |
+| C1-3                                    | Uncertainty of the network analyzer                                                     |
+| A3-27                                   | Mismatch of receiver chain                                                              |
+| A3-28                                   | Insertion loss of receiver chain                                                        |
+| A3-29                                   | Mismatch in the connection of the calibration antenna                                   |
+| A3-30                                   | Influence of the calibration antenna feed cable                                         |
+| A3-31                                   | Influence of the probe antenna cable                                                    |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                               |
+| A3-32                                   | Short term repeatability                                                                |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.5.3-2: NFTR measurement uncertainty value derivation for EIRP accuracy measurements, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                                                                          |                                                                                         | f < 3 G Hz             | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |                                 |                                     |                | f < 3 G Hz                               | 3 < f < 4.2 G Hz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                  |                 |
+| A3-1                                                                                     | Axes intersection                                                                       | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-2                                                                                     | Axes orthogonality                                                                      | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-3                                                                                     | Horizontal pointing                                                                     | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-4                                                                                     | Probe vertical position                                                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-5                                                                                     | Probe horizontal/vertical pointing                                                      | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-6                                                                                     | Measurement distance                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-7                                                                                     | Amplitude and phase drift                                                               | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-8                                                                                     | Amplitude and phase noise                                                               | 0.02                   | 0.02            | 0.02            | Gaussian                        | 1.00                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| A3-9                                                                                     | Leakage and crosstalk                                                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-10                                                                                    | Amplitude non-linearity                                                                 | 0.04                   | 0.04            | 0.04            | Gaussian                        | 1.00                                | 1              | 0.04                                     | 0.04             | 0.04            |
+| A3-11                                                                                    | Amplitude and phase shift in rotary joints                                              | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-12                                                                                    | Channel balance amplitude and phase                                                     | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-13                                                                                    | Probe polarization amplitude and phase                                                  | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-14                                                                                    | Probe pattern knowledge                                                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-15                                                                                    | Multiple reflections                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-16                                                                                    | Room scattering                                                                         | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09            |
+| A3-17                                                                                    | BS support scattering                                                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-18                                                                                    | Scan area truncation                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-19                                                                                    | Sampling point offset                                                                   | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| A3-20                                                                                    | Spherical mode truncation                                                               | 0.02                   | 0.02            | 0.02            | Gaussian                        | 1.00                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| A3-21                                                                                    | Positioning                                                                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| A3-22                                                                                    | Probe array uniformity                                                                  | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| A3-23                                                                                    | Mismatch of receiver chain                                                              | 0.28                   | 0.28            | 0.28            | U-Shaped                        | 1.41                                | 1              | 0.20                                     | 0.20             | 0.20            |
+| A3-24                                                                                    | Insertion loss of receiver chain                                                        | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-25                                                                                    | Uncertainty of the absolute gain of the probe antenna                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26             | 0.26            |
+| A3-26                                                                                    | Measurement repeatability - positioning repeatability                                   | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.15                                     | 0.15             | 0.15            |
+| A3-33                                                                                    | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Normal                          | 1.00                                | 1              | 0.25                                     | 0.25             | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                  |                 |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20             | 0.20            |
+| A3-27                                                                                    | Mismatch of receiver chain                                                              | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-28                                                                                    | Insertion loss of receiver chain                                                        | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-29                                                                                    | Mismatch in the connection of the calibration antenna                                   | 0.02                   | 0.02            | 0.02            | U-Shaped                        | 1.41                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| A3-30                                                                                    | Influence of the calibration antenna feed cable                                         | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A3-31                                                                                    | Influence of the probe antenna cable                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25            |
+| A3-32                                                                                    | Short term repeatability                                                                | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09            |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.52</b>                              | <b>0.56</b>      | <b>0.56</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.01</b>                              | <b>1.10</b>      | <b>1.10</b>     |
+
+## 9.2.6 Plane Wave Synthesizer
+
+### 9.2.6.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+## 9.2.6.2 Test procedure
+
+### 9.2.6.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6 with the calibration system setup for TX requirements depicted in figure 8.6-1.
+
+### 9.2.6.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-1. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Set the BS to generate the tested beam with the applicable test model with the *beam peak direction* intended to be the same as the testing direction.
+- 3) Measure mean power ( $P_{\text{meas}}$ ) at the measurement equipment (such as a spectrum analyzer or power meter) denoted in figure 7.6.1-1.
+- 4) Calculate EIRP, where  $\text{EIRP} = P_{\text{meas}} + L_{c \rightarrow A}$ .
+- 5) Calculate total EIRP =  $\text{EIRP}_{p1} + \text{EIRP}_{p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+- 6) Repeat steps 2 - 5 for all conformance test *beam direction pairs* and test conditions.
+
+### 9.2.6.3 MU value derivation, FR1
+
+Table 9.2.6.3-1 captures the uncertainty budget contributors and table 9.2.6.3-2 captures the derivation of the expanded measurement uncertainty values for EIRP accuracy measurements in PWS.
+
+**Table 9.2.6.3-1: PWS measurement accuracy contributors for EIRP accuracy measurements, FR1**
+
+| UID / Details in annex                  | Uncertainty source                                                                                           |
+|-----------------------------------------|--------------------------------------------------------------------------------------------------------------|
+| <b>Stage 2: BS measurement</b>          |                                                                                                              |
+| A7-1a                                   | Misalignment and pointing error of BS                                                                        |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                      |
+| A7-2a                                   | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna          |
+| A7-3                                    | RF leakage (calibration antenna connector terminated)                                                        |
+| A7-4a                                   | QZ ripple experienced by BS                                                                                  |
+| A7-5                                    | Miscellaneous uncertainty                                                                                    |
+| A7-14                                   | System non-linearity                                                                                         |
+| A7-13                                   | Frequency flatness of test system                                                                            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                              |
+| C1-3                                    | Uncertainty of the network analyzer                                                                          |
+| A7-6                                    | Mismatch (i.e. reference antenna, network analyser and reference cable)                                      |
+| A7-7                                    | Insertion loss of receiver chain                                                                             |
+| A7-3                                    | RF leakage (calibration antenna connector terminated)                                                        |
+| A7-8                                    | Influence of the calibration antenna feed cable                                                              |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                                    |
+| A7-9                                    | Misalignment of positioning system                                                                           |
+| A7-1b                                   | Misalignment and pointing error of calibration antenna                                                       |
+| A7-10                                   | Rotary joints                                                                                                |
+| A7-2b                                   | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna |
+| A7-4b                                   | QZ ripple experienced by calibration antenna                                                                 |
+| A7-11                                   | Switching uncertainty                                                                                        |
+| A7-12                                   | Field repeatability                                                                                          |
+
+NOTE: In the legacy technical reports for BS testability (RAN4) or UE testability (RAN5), the MU/TT derivation tables were using UID as counting numbers across multiple test chambers and requirement's clauses. In this TR a simplified approach was taken with the UID's being the annex number of the measurement uncertainty source description.
+
+**Table 9.2.6.3-2: PWS measurement uncertainty value derivation for EIRP accuracy measurements, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                                           | Uncertainty value (dB) |                 |                  | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                  |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------|-----------------|------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|------------------|
+|                                                                                          |                                                                                                              | f < 3 G Hz             | 3 < f < 4.2 GHz | 4.2 < f < 6 G Hz |                                 |                                     |                | f < 3 G Hz                               | 3 < f < 4.2 G Hz | 4.2 < f < 6 G Hz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                              |                        |                 |                  |                                 |                                     |                |                                          |                  |                  |
+| A7-1a                                                                                    | Misalignment and pointing error of BS                                                                        | 0.10                   | 0.10            | 0.10             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.06             |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                      | 0.14                   | 0.26            | 0.26             | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26             | 0.26             |
+| A7-2a                                                                                    | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna          | 0.05                   | 0.14            | 0.20             | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08             | 0.12             |
+| A7-3                                                                                     | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09             | Normal                          | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09             |
+| A7-4a                                                                                    | QZ ripple experienced by BS                                                                                  | 0.42                   | 0.43            | 0.57             | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25             | 0.33             |
+| A7-5                                                                                     | Miscellaneous uncertainty                                                                                    | 0.00                   | 0.00            | 0.00             | Normal                          | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00             |
+| A7-14                                                                                    | System non-linearity                                                                                         | 0.10                   | 0.10            | 0.15             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.09             |
+| A7-13                                                                                    | Frequency flatness of test system                                                                            | 0.13                   | 0.13            | 0.13             | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08             | 0.08             |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                              |                        |                 |                  |                                 |                                     |                |                                          |                  |                  |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                                          | 0.13                   | 0.20            | 0.20             | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20             | 0.20             |
+| A7-6                                                                                     | Mismatch (i.e. reference antenna, network analyzer and reference cable)                                      | 0.13                   | 0.33            | 0.33             | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23             | 0.23             |
+| A7-7                                                                                     | Insertion loss of receiver chain                                                                             | 0.18                   | 0.18            | 0.18             | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10             | 0.10             |
+| A7-3                                                                                     | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09             | Normal                          | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09             |
+| A7-8                                                                                     | Influence of the calibration antenna feed cable                                                              | 0.10                   | 0.10            | 0.10             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.06             |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                                                    | 0.50                   | 0.43            | 0.43             | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25             |
+| A7-9                                                                                     | Misalignment of positioning system                                                                           | 0.00                   | 0.00            | 0.00             | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00             | 0.00             |
+| A7-1b                                                                                    | Misalignment and pointing error of calibration antenna                                                       | 0.05                   | 0.05            | 0.05             | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03             |
+| A7-10                                                                                    | Rotary joints                                                                                                | 0.00                   | 0.00            | 0.00             | U-shaped                        | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00             |
+| A7-2b                                                                                    | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna | 0.12                   | 0.12            | 0.15             | Rectangular                     | 1.73                                | 1              | 0.07                                     | 0.07             | 0.09             |
+| A7-4b                                                                                    | QZ ripple experienced by calibration antenna                                                                 | 0.20                   | 0.20            | 0.20             | Rectangular                     | 1.73                                | 1              | 0.12                                     | 0.12             | 0.12             |
+| A7-11                                                                                    | Switching uncertainty                                                                                        | 0.02                   | 0.02            | 0.02             | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01             | 0.01             |
+| A7-12                                                                                    | Field repeatability                                                                                          | 0.06                   | 0.12            | 0.15             | Normal                          | 1.00                                | 1              | 0.06                                     | 0.12             | 0.15             |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                                              |                        |                 |                  |                                 |                                     |                | <b>0.50</b>                              | <b>0.61</b>      | <b>0.66</b>      |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                              |                        |                 |                  |                                 |                                     |                | <b>0.98</b>                              | <b>1.19</b>      | <b>1.29</b>      |
+
+## 9.2.7 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for the EIRP accuracy test can be derived from values captured in table 9.2.7-1, separately for each of the defined frequency ranges. The common maximum accepted test system uncertainty values are applicable for all test methods addressing
+
+EIRP accuracy test requirement in Normal test conditions. Based on input values in table 9.2.7-1, the expanded uncertainty  $u_e$  (1.96 $\sigma$  - confidence interval of 95 %) values were derived for frequency ranges as below:
+
+- For the frequency range up to 4.2 GHz (with the breakdown point at 3 GHz), the same MU values as for E-UTRA in TS 37.145-2 [4] were adopted also for NR operation below 4.2 GHz. It is expected that the test chamber setup, calibration and measurement procedures for E-UTRA and NR will be highly similar. All uncertainty factors were judged to be the same. The MU value was thus agreed to be 1.1 dB for up to 3 GHz bands.
+- For the frequency range 4.2 - 6 GHz, all MU factors including instrumentation related MU were judged to be the same as for the 3 - 4.2 GHz range, and thus the total MU for 4.2 – 6 GHz is the same as for 3 - 4.2 GHz. This assessment was made under the assumption of testing BS designed for licensed spectrum; for unlicensed spectrum the MU may differ. The MU value was thus agreed to be 1.3 dB for 3 – 6 GHz bands. The MU in 4.2 - 6 GHz is valid for BS designed to operate in licensed spectrum.
+- Based on CATR inputs in clause 9.2.3.4, for the frequency range  $24.25 < f < 29.5$  GHz the MU was decided to be 1.7 dB.
+- Based on CATR inputs in clause 9.2.3.4, for the frequency range  $37 < f < 43.5$  GHz the MU was decided to be 2.0 dB.
+
+**Table 9.2.7-1: OTA test system specific measurement uncertainty values for the EIRP accuracy, FR1, Normal test conditions**
+
+|                                                        | Expanded uncertainty (dB) |                   |                   |
+|--------------------------------------------------------|---------------------------|-------------------|-------------------|
+|                                                        | $f < 3$ GHz               | $3 < f < 4.2$ GHz | $4.2 < f < 6$ GHz |
+| Indoor Anechoic Chamber                                | 0.87                      | 1.06              | 1.06              |
+| Compact Antenna Test Range                             | 1.11                      | 1.27              | 1.27              |
+| One Dimensional Compact Range Chamber                  | 0.90                      | 1.10              | 1.10              |
+| Near Field Test Range                                  | 1.01                      | 1.10              | 1.10              |
+| Plane Wave Synthesizer                                 | 0.98                      | 1.19              | 1.29              |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.10</b>               | <b>1.30</b>       | <b>1.30</b>       |
+
+**Table 9.2.7-2: OTA test system specific measurement uncertainty values for the EIRP accuracy, FR2, Normal test conditions**
+
+|                                                        | Expanded uncertainty (dB) |                     |                       |
+|--------------------------------------------------------|---------------------------|---------------------|-----------------------|
+|                                                        | $24.25 < f < 29.5$ GHz    | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+| Indoor Anechoic Chamber                                | -                         | -                   | -                     |
+| Compact Antenna Test Range                             | 1.74                      | 2.07                | -                     |
+| One Dimensional Compact Range Chamber                  | -                         | -                   | -                     |
+| Near Field Test Range                                  | -                         | -                   | -                     |
+| Plane Wave Synthesizer                                 | -                         | -                   | -                     |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.70</b>               | <b>2.00</b>         | <b>2.2 (NOTE)</b>     |
+
+NOTE: MU estimation for  $43.5 < f < 48.2$  GHz was derived based on the linear approximation (based on MU values for lower frequency ranges). MU extrapolation approach was used instead of the typical derivation of the Expanded MU based on the MU budget calculations, as in case of lower frequency ranges.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 9.2.8 Test Tolerance for EIRP accuracy, Normal test conditions
+
+Considering the methodology described in clause 5.1, Test Tolerance values for EIRP were derived based on values captured in clause 9.2.7.
+
+The TT was decided to be the same as the MU for EIRP accuracy in FR1.
+
+The TT was decided to be the same as the MU for EIRP accuracy in FR2.
+
+Frequency range specific Test Tolerance values for the EIRP accuracy test are defined in table 9.2.8-1.
+
+**Table 9.2.8-1: Test Tolerance values for the EIRP accuracy in Normal test conditions, FR1**
+
+|                     | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 < f < 6 \text{ GHz}$ |
+|---------------------|------------------------|------------------------------------------|---------------------------|
+| Test Tolerance (dB) | 1.1                    | 1.3                                      | 1.3                       |
+
+**Table 9.2.8-2: Test Tolerance values for the EIRP accuracy in Normal test conditions, FR2**
+
+|                     | $24.25 < f < 29.5 \text{ GHz}$ | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+|---------------------|--------------------------------|-----------------------------|-------------------------------|
+| Test Tolerance (dB) | 1.7                            | 2.0                         | 2.2                           |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.3 EIRP accuracy, Extreme test conditions
+
+### 9.3.1 General
+
+Clause 9.3 captures MU and TT values derivation for the EIRP accuracy directional requirement in Extreme test conditions.
+
+For the MU and TT values derivation for the EIRP accuracy in Normal test conditions, refer to clause 9.2. Specification of Normal and Extreme test conditions is captured in TS 38.141-2 [6] for NR BS (i.e. *BS type 1-O* and *BS type 2-O*), and in TS 37.145-2 [4] for OTA AAS BS.
+
+### 9.3.2 Indoor Anechoic Chamber
+
+#### 9.3.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.2.
+
+#### 9.3.2.2 Test procedure
+
+##### 9.3.2.2.1 Stage 1: Calibration
+
+Calibration shall be done with the same procedure as in clause 8.2 (i.e. EIRP accuracy calibration procedure for Normal test conditions) to ensure that the SNR at the measurement equipment input is appropriate for the measurement of the requirement and the reception signal level at the measurement equipment is within the dynamic range of measurement equipment.
+
+##### 9.3.2.2.2 Stage 2: BS measurement
+
+Reference IAC testing procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions).
+
+### 9.3.2.3 MU value derivation, FR1
+
+**Table 9.3.2.3-1: Indoor Anechoic Chamber measurement uncertainty value derivation for EIRP accuracy measurements in Extreme test conditions, FR1**
+
+| UID                                                                    | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                               | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                                                   | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                                                   | Pointing misalignment between the BS and the receiving antenna                                | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-17                                                                  | Quality of quiet zone (extreme test conditions)                                               | 0.60                   | 0.60            | 0.60            | Gaussian                        | 1.00                                | 1              | 0.60                                     | 0.60            | 0.60            |
+| A1-4a                                                                  | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                                                  | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                   | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)       | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A1-7                                                                   | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                                                   | Random uncertainty                                                                            | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-19                                                                  | Radome loss variation                                                                         | 0.40                   | 0.40            | 0.40            | Rectangular                     | 1.73                                | 1              | 0.23                                     | 0.23            | 0.23            |
+| A1-18                                                                  | Wet radome loss variation                                                                     | 0.95                   | 0.95            | 0.95            | Gaussian                        | 1.00                                | 1              | 0.95                                     | 0.95            | 0.95            |
+| A1-20                                                                  | Change in absorber behavior                                                                   | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-16                                                                  | Frequency flatness of test system                                                             | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                                                   | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                                                  | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                                                  | Impedance mismatch between the reference antenna and the network analyzer.                    | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                                                   | Quality of quiet zone (normal test conditions)                                                | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                                                  | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                                                  | Mutual coupling between the reference antenna and the receiving antenna                       | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                   | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                           | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                                                  | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                                                  | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                                                  | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                                                  | Uncertainty of the absolute gain of the receiving antenna                                     | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>1.26</b>                              | <b>1.29</b>     | <b>1.29</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>2.46</b>                              | <b>2.53</b>     | <b>2.53</b>     |
+
+### 9.3.3 Compact Antenna Test Range
+
+#### 9.3.3.1 Measurement system description
+
+Measurement system description for the CATR measurement in the Extreme test environment is captured in clause 7.3.2.
+
+#### 9.3.3.2 Test procedure
+
+##### 9.3.3.2.1 Stage 1: Calibration
+
+The CATR calibration for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures.
+
+Calibration shall be done with the same procedure shown in clause 9.2.3.2.1 (i.e. EIRP accuracy calibration procedure for Normal test conditions) to ensure that the SNR at the measurement equipment input is appropriate for the measurement of the requirement and the reception signal level at the measurement equipment is within the dynamic range of measurement equipment.
+
+##### 9.3.3.2.2 Stage 2: BS measurement
+
+The CATR test setup and measurement procedures for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures.
+
+Reference procedure in clause 9.2.3.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions).
+
+## 9.3.3.3 MU value derivation, FR1
+
+**Table 9.3.3.3-1: CATR MU value derivation for EIRP accuracy measurements in Extreme test conditions**
+
+| UID                                                                                      | Uncertainty source                                                                      | Uncertainty value (dB)         |                      |                      | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                      |                      |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|--------------------------------|----------------------|----------------------|---------------------------------|-------------------------------------|-------|---------------------------------|----------------------|----------------------|
+|                                                                                          |                                                                                         | $f \leq 3$ GHz                 | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                                 |                                     |       | $f \leq 3$ GHz                  | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+|                                                                                          |                                                                                         | <b>Stage 2: BS measurement</b> |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| A2-1a                                                                                    | Misalignment and pointing error of BS (for EIRP)                                        | 0.00                           | 0.00                 | 0.00                 | Exp. normal                     | 2.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                           | 0.26                 | 0.26                 | Gaussian                        | 1.00                                | 1     | 0.14                            | 0.26                 | 0.26                 |
+| A2-2a                                                                                    | Standing wave between BS and test range antenna                                         | 0.21                           | 0.21                 | 0.21                 | U-shaped                        | 1.41                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                           | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-13                                                                                    | Quality of quiet zone (extreme test conditions)                                         | 0.60                           | 0.60                 | 0.60                 | Gaussian                        | 1.00                                | 1     | 0.60                            | 0.60                 | 0.60                 |
+| A2-12                                                                                    | Frequency flatness of test system                                                       | 0.25                           | 0.25                 | 0.25                 | Gaussian                        | 1.00                                | 1     | 0.25                            | 0.25                 | 0.25                 |
+| A2-14                                                                                    | Wet radome loss variation                                                               | 0.40                           | 0.40                 | 0.40                 | Rectangular                     | 1.73                                | 1     | 0.23                            | 0.23                 | 0.23                 |
+| A2-15                                                                                    | Radome loss variation                                                                   | 0.95                           | 0.95                 | 0.95                 | Gaussian                        | 1.00                                | 1     | 0.95                            | 0.95                 | 0.95                 |
+| A2-16                                                                                    | Change in absorber behavior                                                             | 0.10                           | 0.10                 | 0.10                 | Gaussian                        | 1.00                                | 1     | 0.10                            | 0.10                 | 0.10                 |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                         |                                |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                     | 0.13                           | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.13                            | 0.20                 | 0.20                 |
+| A2-5a                                                                                    | Mismatch of receiver chain between receiving antenna and measurement receiver           | 0.13                           | 0.33                 | 0.33                 | U-shaped                        | 1.41                                | 1     | 0.09                            | 0.23                 | 0.23                 |
+| A2-6                                                                                     | Insertion loss of receiver chain                                                        | 0.18                           | 0.18                 | 0.18                 | Rectangular                     | 1.73                                | 1     | 0.10                            | 0.10                 | 0.10                 |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                           | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-7                                                                                     | Influence of the calibration antenna feed cable                                         | 0.02                           | 0.02                 | 0.02                 | U-shaped                        | 1.41                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                               | 0.50                           | 0.43                 | 0.43                 | Rectangular                     | 1.73                                | 1     | 0.29                            | 0.25                 | 0.25                 |
+| A2-8                                                                                     | Misalignment positioning system                                                         | 0.00                           | 0.00                 | 0.00                 | Exp. normal                     | 2.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-1b                                                                                    | Misalignment and pointing error of calibration antenna (for EIRP)                       | 0.50                           | 0.50                 | 0.50                 | Exp. normal                     | 2.00                                | 1     | 0.25                            | 0.25                 | 0.25                 |
+| A2-9                                                                                     | Rotary joints                                                                           | 0.05                           | 0.05                 | 0.05                 | U-shaped                        | 1.41                                | 1     | 0.03                            | 0.03                 | 0.03                 |
+| A2-2b                                                                                    | Standing wave between calibration antenna and test range antenna                        | 0.09                           | 0.09                 | 0.09                 | U-shaped                        | 1.41                                | 1     | 0.06                            | 0.06                 | 0.06                 |
+| A2-4b                                                                                    | QZ ripple experienced by calibration antenna (normal test conditions)                   | 0.01                           | 0.01                 | 0.01                 | Gaussian                        | 1.00                                | 1     | 0.01                            | 0.01                 | 0.01                 |
+| A2-11                                                                                    | Switching uncertainty                                                                   | 0.26                           | 0.26                 | 0.26                 | Rectangular                     | 1.73                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                         |                                |                      |                      |                                 |                                     |       | <b>1.28</b>                     | <b>1.32</b>          | <b>1.30</b>          |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                         |                                |                      |                      |                                 |                                     |       | <b>2.51</b>                     | <b>2.58</b>          | <b>2.55</b>          |
+
+### 9.3.3.4 MU value derivation, FR2
+
+**Table 9.3.3.4-1: CATR MU value derivation for EIRP accuracy measurements in Extreme test conditions, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                   | Uncertainty value (dB) |            | Distribution of the probability | Divisor based on distribution shape | <i>c<sub>i</sub></i> | Standard uncertainty <i>u<sub>i</sub></i> (dB) |             |
+|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------|------------|---------------------------------|-------------------------------------|----------------------|------------------------------------------------|-------------|
+|                                                                        |                                                                                                      | 24.25 < f              | 37 < f     |                                 |                                     |                      | 24.25 < f                                      | 37 < f      |
+|                                                                        |                                                                                                      | ≤ 29.5 GHz             | ≤ 43.5 GHz |                                 |                                     |                      | ≤ 29.5 GHz                                     | ≤ 43.5 GHz  |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                      |                        |            |                                 |                                     |                      |                                                |             |
+| A2-1a                                                                  | Misalignment and pointing error of BS (for EIRP)                                                     | 0.20                   | 0.20       | Exp. normal                     | 2.00                                | 1                    | 0.10                                           | 0.10        |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power | 0.50                   | 0.70       | Gaussian                        | 1.00                                | 1                    | 0.50                                           | 0.70        |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                                      | 0.03                   | 0.03       | U-shaped                        | 1.41                                | 1                    | 0.02                                           | 0.02        |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01       | Gaussian                        | 1.00                                | 1                    | 0.01                                           | 0.01        |
+| A2-13                                                                  | QZ ripple with BS (extreme test conditions)                                                          | 0.70                   | 0.70       | Gaussian                        | 1.00                                | 1                    | 0.70                                           | 0.70        |
+| A2-12                                                                  | Frequency flatness of test system                                                                    | 0.25                   | 0.25       | Gaussian                        | 1.00                                | 1                    | 0.25                                           | 0.25        |
+| A2-15                                                                  | Radome loss variation                                                                                | 0.50                   | 0.50       | Gaussian                        | 1.00                                | 1                    | 0.50                                           | 0.50        |
+| A2-14                                                                  | Wet radome loss variation                                                                            | 0.90                   | 0.90       | Gaussian                        | 1.00                                | 1                    | 0.90                                           | 0.90        |
+| A2-16                                                                  | Change in absorber behavior                                                                          | 0.50                   | 0.50       | Gaussian                        | 1.00                                | 1                    | 0.50                                           | 0.50        |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                      |                        |            |                                 |                                     |                      |                                                |             |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                  | 0.30                   | 0.30       | Gaussian                        | 1.00                                | 1                    | 0.30                                           | 0.30        |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver                        | 0.43                   | 0.57       | U-shaped                        | 1.41                                | 1                    | 0.30                                           | 0.40        |
+| A2-6                                                                   | Insertion loss of receiver chain                                                                     | 0.00                   | 0.00       | Rectangular                     | 1.73                                | 1                    | 0.00                                           | 0.00        |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01       | Gaussian                        | 1.00                                | 1                    | 0.01                                           | 0.01        |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                                      | 0.21                   | 0.29       | U-shaped                        | 1.41                                | 1                    | 0.15                                           | 0.21        |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                            | 0.52                   | 0.52       | Rectangular                     | 1.73                                | 1                    | 0.30                                           | 0.30        |
+| A2-8                                                                   | Misalignment positioning system                                                                      | 0.00                   | 0.00       | Exp. normal                     | 2.00                                | 1                    | 0.00                                           | 0.00        |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                                    | 0.00                   | 0.00       | Exp. normal                     | 2.00                                | 1                    | 0.00                                           | 0.00        |
+| A2-9                                                                   | Rotary joints                                                                                        | 0.00                   | 0.00       | U-shaped                        | 1.41                                | 1                    | 0.00                                           | 0.00        |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                                     | 0.09                   | 0.09       | U-shaped                        | 1.41                                | 1                    | 0.06                                           | 0.06        |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna (normal test conditions)                                | 0.01                   | 0.01       | Gaussian                        | 1.00                                | 1                    | 0.01                                           | 0.01        |
+| A2-11                                                                  | Switching uncertainty                                                                                | 0.10                   | 0.10       | Rectangular                     | 1.73                                | 1                    | 0.06                                           | 0.06        |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                      |                        |            |                                 |                                     |                      | <b>1.56</b>                                    | <b>1.66</b> |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                      |                        |            |                                 |                                     |                      | <b>3.05</b>                                    | <b>3.25</b> |
+
+### 9.3.4 Maximum accepted test system uncertainty
+
+For the frequency range up to 4.2 GHz, the same MU values as for E-UTRA in TS 37.145-2 [4] were adopted. It is expected that the test chamber setup, calibration and measurement procedures for E-UTRA and NR will be highly similar. All uncertainty factors were judged to be the same.
+
+For the frequency range 4.2 - 6 GHz, all MU factors, including instrumentation related MU were judged to be the same as for the 3 - 4.2 GHz range, and thus the total MU for 4.2 – 6 GHz is the same as for 3 - 4.2 GHz. This assessment was made under the assumption of testing BS designed for licensed spectrum; for unlicensed spectrum the MU may differ.
+
+The MU value was thus agreed to be 2.5 dB for up to 3 GHz bands and 2.6 dB for 3 – 6 GHz bands. The MU in 4.2 - 6 GHz is valid for BS designed to operate in licensed spectrum.
+
+For FR2, for the direct far field method the MU budget is very similar to the existing MU budget for the EIRP accuracy requirement. However there are a number of additional sources of uncertainty due to the environmental enclosure that need to be added to the budget. For FR2 only the CATR MU budget has been assessed however other suitable camber types are not precluded.
+
+Based on the above evaluation, the MU was decided to be 3.1 dB for the frequency range  $24.25 < f < 29.5$  GHz and 3.3 dB for the frequency range  $37 < f < 43.5$  GHz.
+
+Test system specific measurement uncertainty values for the EIRP accuracy in Extreme test conditions are summarised in table 9.3.4-1.
+
+**Table 9.3.4-1: Test system specific measurement uncertainty values for the EIRP accuracy in Extreme test conditions, FR1**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 2.46                            | 2.53                       | 2.53                       |
+| Compact Antenna Test Range                             | 2.51                            | 2.58                       | 2.55                       |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.5</b>                      | <b>2.6</b>                 | <b>2.6</b>                 |
+
+**Table 9.3.4-2: Test system specific measurement uncertainty values for the EIRP accuracy in Extreme test conditions, FR2**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                        |                       |
+|--------------------------------------------------------|---------------------------------|------------------------|-----------------------|
+|                                                        | $24.25 < f < 29.5$ GHz          | $37 < f \leq 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+| Compact Antenna Test Range                             | 3.05                            | 3.25                   | -                     |
+| <b>Common maximum accepted test system uncertainty</b> | <b>3.1</b>                      | <b>3.3</b>             | <b>3.5 (NOTE)</b>     |
+
+NOTE: MU estimation for  $43.5 < f < 48.2$  GHz was derived based on the linear approximation (based on MU values for lower frequency ranges). MU extrapolation approach was used instead of the typical derivation of the Expanded MU based on the MU budget calculations, as in case of lower frequency ranges.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+### 9.3.5 Test Tolerance for EIRP accuracy, Extreme test conditions
+
+Considering the methodology described in clause 5.1, Test Tolerance values for EIRP were derived based on values captured in clause 9.3.4.
+
+The TT was decided to be the same as the MU for EIRP accuracy in FR1.
+
+The TT was decided to be the same as the MU for EIRP accuracy in FR2.
+
+Frequency range specific Test Tolerance values for the EIRP accuracy test are defined in table 9.3.5-1.
+
+**Table 9.3.5-1: Test Tolerance values for the EIRP accuracy in Extreme test conditions, FR1**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 2.5            | 2.6                        | 2.6                        |
+
+**Table 9.3.5-2: Test Tolerance values for the EIRP accuracy in Extreme test conditions, FR2**
+
+|                     | 24.25 < f < 29.5 GHz | 37 GHz < f ≤ 43.5 GHz | 43.5 < f < 48.2 GHz |
+|---------------------|----------------------|-----------------------|---------------------|
+| Test Tolerance (dB) | 3.1                  | 3.3                   | 3,5                 |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.4 OTA E-UTRA DL RS power
+
+### 9.4.1 General
+
+Clause 9.4 captures MU and TT values derivation for the OTA E-UTRA DL RS power directional requirement.
+
+DL RS power is an E-UTRA specific measurement applicable to the OTA AAS BS, and it is defined as:
+
+- The DL RS power is the resource element power of the Downlink Reference Symbol at the RIB transmitting the DL RS for a cell.
+- The absolute DL RS power is indicated on the DL-SCH. The absolute accuracy is defined as the maximum deviation between the DL RS power indicated on the DL-SCH and the DL RS power of each E-UTRA carrier.
+
+As such it is an absolute power (i.e. EIRP) measurement of a single RE.
+
+It is assumed that the value broadcast on DL-SCH is a conducted or TRP value, since the power is measured at the antenna connector. To facilitate efficient testing, OTA DL RS power is tested by measuring EIRP as a directional requirement, and compared with a declared DL RS EIRP derived from the power broadcast on the DL-SCH and the BS directivity in the direction to be tested. This is sufficient to demonstrate the ability of the physical layer to deliver accurate RS power.
+
+As the requirement is based on absolute directional power the absolute level will be subject to the same calibration and measurement errors as the EIRP measurement (in Normal test conditions). However as the measurement is for a single RE it is necessary to demodulate the received signal and this is done at the same time as the OTA EVM test using the "global in-channel TX test" as described in annex L of TS 38.141-2 [6] for NR.
+
+The demodulated power accuracy test is not as accurate as the power measurement using a power meter for the EIRP accuracy test.
+
+The MU is calculated by using the conducted MU in the MU uncertainty budget in place of the RF measurement equipment.
+
+### 9.4.2 Indoor Anechoic Chamber
+
+#### 9.4.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 9.4.2.2 Test procedure
+
+##### 9.4.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for TX requirements depicted in figure 8.2-1.
+
+##### 9.4.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with the manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Set the BS to generate the tested beam with the *beam peak direction* intended to be the same as the testing direction.
+- 3) Rotate the BS to make the testing direction aligned with the direction of the receiving antenna.
+- 4) Set the BS to transmit the test signal at the maximum power according to applicable test model.
+- 5) Measure the  $P_{\text{DL\_RS}}$ , which is the measured signal power of DL RS EIRP (in the *beam peak direction*).
+- 6) Calculate the  $\text{EIRP}_{\text{DL\_RS}}$  with the following formula:
+
+$$\text{EIRP}_{\text{DL\_RS}} = P_{\text{DL\_RS}} + L_{\text{TX\_cal, A}\rightarrow\text{D}}$$
+
+and
+
+$$\text{EIRP}_{\text{DL\_RS}} = \text{EIRP}_{\text{DL\_RS\_p1}} + \text{EIRP}_{\text{DL\_RS\_p2}}$$
+
+where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+- 7) Repeat steps 2 - 6 for all conformance test *beam direction pairs* and test conditions.
+
+### 9.4.2.3 MU value derivation, FR1
+
+As the DL RS power is an absolute measurement most of the uncertainties form the EIRP accuracy remain the same. Also it can be noted that the measured signal is a wanted signal and hence will be beam formed in the same way as the wanted signal, hence any errors which may be dependent on the beam shape will be the same as for the EIRP accuracy measurement.
+
+**Table 9.4.2.3-1: Indoor Anechoic Chamber measurement uncertainty value derivation for OTA E-UTRA DL RS power measurement**
+
+| UID                                            | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                |                                                                                               | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                 |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                           | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                           | Pointing misalignment between the BS and the receiving antenna                                | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-3                                           | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4a                                          | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                          | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                           | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C3-1                                           | DL-RS MU derived from conducted specification                                                 | 0.41                   | 0.56            | 0.56            | Gaussian                        | 1.00                                | 1              | 0.41                                     | 0.56            | 0.56            |
+| A1-7                                           | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                           | Random uncertainty                                                                            | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>        |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                           | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                          | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                          | Impedance mismatch between the reference antenna and the network analyzer.                    | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                           | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                          | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                          | Mutual coupling between the reference antenna and the receiving antenna                       | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                           | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                           | Uncertainty of the network analyzer                                                           | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                          | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                          | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                          | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                           | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                          | Uncertainty of the absolute gain of the receiving antenna                                     | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Combined standard uncertainty (1σ) (dB)</b> |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.59</b>                              | <b>0.73</b>     | <b>0.73</b>     |
+
+|                                                                         |      |      |      |
+|-------------------------------------------------------------------------|------|------|------|
+| Expanded uncertainty (1.96 $\sigma$ - confidence interval of 95 %) (dB) | 1.15 | 1.44 | 1.44 |
+|-------------------------------------------------------------------------|------|------|------|
+
+### 9.4.3 Compact Antenna Test Range
+
+#### 9.4.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+#### 9.4.3.2 Test procedure
+
+##### 9.4.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+##### 9.4.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with *beam peak direction* of range antenna.
+- 2) Configure TX branch and carrier according to maximum power requirement and test configuration.
+- 4) Set the BS to transmit the applicable test signal.
+- 5) Measure the  $P_{DL\_RS}$  which is the measured signal power of DL RS EIRP (in the *beam peak direction*).
+- 6) Calculate  $EIRP_{DL\_RS}$  using the following equation:
+
+$$EIRP_{DL\_RS\_p(x)} = P_{DL\_RS\_meas} + L_{A \rightarrow B}.$$
+
+And
+
+$EIRP_{DL\_RS} = EIRP_{DL\_RS\_p1} + EIRP_{DL\_RS\_p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+- 7) Repeat steps 2-6 for all conformance test *beam direction pairs* and test conditions.
+
+#### 9.4.3.3 MU value derivation, FR1
+
+As the DL RS power is an absolute measurement most of the uncertainties from the EIRP accuracy remain the same. Also it can be noted that the measured signal is a wanted signal and hence will be beam formed in the same way as the wanted signal, hence any errors which may be dependent on the beam shape will be the same as for the EIRP accuracy measurement.
+
+**Table 9.4.3.3-1: CATR MU value derivation for OTA E-UTRA DL RS power measurement**
+
+| UID                                                                                      | Uncertainty source                                                                    | Uncertainty value (dB) |                      |                      | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                      |                      |
+|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|------------------------|----------------------|----------------------|---------------------------------|-------------------------------------|-------|---------------------------------|----------------------|----------------------|
+|                                                                                          |                                                                                       | $f \leq 3$ GHz         | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                                 |                                     |       | $f \leq 3$ GHz                  | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                       |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| A2-1a                                                                                    | Misalignment and pointing error of BS (for EIRP)                                      | 0.00                   | 0.00                 | 0.00                 | Exp. normal                     | 2.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C3-1                                                                                     | DL-RS MU derived from conducted specification                                         | 0.41                   | 0.56                 | 0.56                 | Gaussian                        | 1.00                                | 1     | 0.41                            | 0.56                 | 0.56                 |
+| A2-2a                                                                                    | Standing wave between BS and test range antenna                                       | 0.21                   | 0.21                 | 0.21                 | U-shaped                        | 1.41                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-4a                                                                                    | QZ ripple experienced by BS                                                           | 0.09                   | 0.09                 | 0.09                 | Gaussian                        | 1.00                                | 1     | 0.09                            | 0.09                 | 0.09                 |
+| A2-12                                                                                    | Frequency flatness of test system                                                     | 0.25                   | 0.25                 | 0.25                 | Gaussian                        | 1.00                                | 1     | 0.25                            | 0.25                 | 0.25                 |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                       |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                   | 0.13                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.13                            | 0.20                 | 0.20                 |
+| A2-5a                                                                                    | Mismatch of receiver chain between receiving antenna and measurement receiver         | 0.13                   | 0.33                 | 0.33                 | U-shaped                        | 1.41                                | 1     | 0.09                            | 0.23                 | 0.23                 |
+| A2-6                                                                                     | Insertion loss of receiver chain                                                      | 0.18                   | 0.18                 | 0.18                 | Rectangular                     | 1.73                                | 1     | 0.10                            | 0.10                 | 0.10                 |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-7                                                                                     | Influence of the calibration antenna feed cable                                       | 0.02                   | 0.02                 | 0.02                 | U-shaped                        | 1.41                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                             | 0.50                   | 0.43                 | 0.43                 | Rectangular                     | 1.73                                | 1     | 0.29                            | 0.25                 | 0.25                 |
+| A2-8                                                                                     | Misalignment positioning system                                                       | 0.00                   | 0.00                 | 0.00                 | Exp. normal                     | 2.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A2-1b                                                                                    | Misalignment and pointing error of calibration antenna (for EIRP)                     | 0.50                   | 0.50                 | 0.50                 | Exp. normal                     | 2.00                                | 1     | 0.25                            | 0.25                 | 0.25                 |
+| A2-9                                                                                     | Rotary joints                                                                         | 0.05                   | 0.05                 | 0.05                 | U-shaped                        | 1.41                                | 1     | 0.03                            | 0.03                 | 0.03                 |
+| A2-2b                                                                                    | Standing wave between calibration antenna and test range antenna                      | 0.09                   | 0.09                 | 0.09                 | U-shaped                        | 1.41                                | 1     | 0.06                            | 0.06                 | 0.06                 |
+| A2-4b                                                                                    | QZ ripple experienced by calibration antenna                                          | 0.01                   | 0.01                 | 0.01                 | Gaussian                        | 1.00                                | 1     | 0.01                            | 0.01                 | 0.01                 |
+| A2-11                                                                                    | Switching uncertainty                                                                 | 0.26                   | 0.26                 | 0.26                 | Rectangular                     | 1.73                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                       |                        |                      |                      |                                 |                                     |       | <b>0.69</b>                     | <b>0.81</b>          | <b>0.81</b>          |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                       |                        |                      |                      |                                 |                                     |       | <b>1.35</b>                     | <b>1.60</b>          | <b>1.60</b>          |
+
+## 9.4.4 Near Field Test Range
+
+### 9.4.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+#### 9.4.4.2 Test procedure
+
+##### 9.4.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+##### 9.4.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+- 1) BS near field *radiation pattern* measurement: this is performed with the BS transmitting a defined modulated signal, as defined in applicable conformance test specification.
+  - a) DL RS is measured during near field *radiation pattern* measurement and used as the basis for the NF to FF transformation.
+- 2) BS near field to far field transformation: the near field power calibration is applied.
+
+The near field to far field transformation is a mathematical computation which is applied to the near field measured *radiation pattern* in order to compute the far field *radiation pattern*. It is typically performed expanding the measured near field over a set of orthogonal basis functions. The near to far field transform is then performed in two steps:
+
+- 1) Expansion (or projection) of the measured near field (i.e.  $E_{\text{meas}}(r)$ ) over a set of orthogonal basis functions (i.e.  $F_{\text{basis}}(r)$ ) in order to evaluate the transformed spectrum:
+
+$$E_{\text{meas}}(r) = \text{Spectrum} * F_{\text{basis}}(r)$$
+
+- 2) FF (i.e. EFF) computation using the previously calculated spectrum and with the basis functions evaluated at  $r \rightarrow \infty$  (i.e.  $F_{\text{basis}}(r \rightarrow \infty)$ ):
+
+$$\text{EFF} = \text{Spectrum} * F_{\text{basis}}(r \rightarrow \infty)$$
+
+When performing the near field to far field transformation, the gain calibration is applied so that the near field pattern will be transformed from relative power (i.e. dB) to absolute power (i.e. dBm). In this specific case, the EIRP far field pattern is expressed in terms of the absolute power radiated by the BS in the declared beam:
+
+- 1) DL RS power EIRP: once the full 3D far field EIRP pattern has been computed, the DL RS power EIRP can be derived at the *beam peak direction* according to the declared *beam direction pair*.
+
+## 9.4.4.3 MU value derivation, FR1
+
+**Table 9.4.4.3-1: NFTR measurement uncertainty value derivation for OTA E-UTRA DL RS power measurement**
+
+| UID                                                                                      | Uncertainty source                                        | Uncertainty value (dB) |                      |                      | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                      |                      |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------|------------------------|----------------------|----------------------|---------------------------------|-------------------------------------|-------|---------------------------------|----------------------|----------------------|
+|                                                                                          |                                                           | $f \leq 3$ GHz         | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                                 |                                     |       | $f \leq 3$ GHz                  | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                           |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| A3-1                                                                                     | Axes intersection                                         | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-2                                                                                     | Axes orthogonality                                        | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-3                                                                                     | Horizontal pointing                                       | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-4                                                                                     | Probe vertical position                                   | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-5                                                                                     | Probe horizontal/vertical pointing                        | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-6                                                                                     | Measurement distance                                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-7                                                                                     | Amplitude and phase drift                                 | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-8                                                                                     | Amplitude and phase noise                                 | 0.02                   | 0.02                 | 0.02                 | Gaussian                        | 1.00                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| A3-9                                                                                     | Leakage and crosstalk                                     | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-10                                                                                    | Amplitude non-linearity                                   | 0.04                   | 0.04                 | 0.04                 | Gaussian                        | 1.00                                | 1     | 0.04                            | 0.04                 | 0.04                 |
+| A3-11                                                                                    | Amplitude and phase shift in rotary joints                | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-12                                                                                    | Channel balance amplitude and phase                       | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-13                                                                                    | Probe polarization amplitude and phase                    | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-14                                                                                    | Probe pattern knowledge                                   | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-15                                                                                    | Multiple reflections                                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-16                                                                                    | Room scattering                                           | 0.09                   | 0.09                 | 0.09                 | Gaussian                        | 1.00                                | 1     | 0.09                            | 0.09                 | 0.09                 |
+| A3-17                                                                                    | BS support scattering                                     | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-18                                                                                    | Scan area truncation                                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-19                                                                                    | Sampling point offset                                     | 0.01                   | 0.01                 | 0.01                 | Gaussian                        | 1.00                                | 1     | 0.01                            | 0.01                 | 0.01                 |
+| A3-20                                                                                    | Spherical mode truncation                                 | 0.02                   | 0.02                 | 0.02                 | Gaussian                        | 1.00                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| A3-21                                                                                    | Positioning                                               | 0.03                   | 0.03                 | 0.03                 | Rectangular                     | 1.73                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| A3-22                                                                                    | Probe array uniformity                                    | 0.06                   | 0.06                 | 0.06                 | Gaussian                        | 1.00                                | 1     | 0.06                            | 0.06                 | 0.06                 |
+| A3-23                                                                                    | Mismatch of receiver chain                                | 0.28                   | 0.28                 | 0.28                 | U-Shaped                        | 1.41                                | 1     | 0.20                            | 0.20                 | 0.20                 |
+| A3-24                                                                                    | Insertion loss of receiver chain                          | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-25                                                                                    | Uncertainty of the absolute gain of the probe antenna     | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C3-1                                                                                     | DL-RS MU derived from conducted specification             | 0.41                   | 0.56                 | 0.56                 | Gaussian                        | 1.00                                | 1     | 0.41                            | 0.56                 | 0.56                 |
+| A3-26                                                                                    | Measurement repeatability - positioning repeatability     | 0.15                   | 0.15                 | 0.15                 | Gaussian                        | 1.00                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                           |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| C1-3                                                                                     | Uncertainty of the network analyzer                       | 0.13                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.13                            | 0.20                 | 0.20                 |
+| A3-27                                                                                    | Mismatch of receiver chain                                | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-28                                                                                    | Insertion loss of receiver chain                          | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-29                                                                                    | Mismatch in the connection of the calibration antenna     | 0.02                   | 0.02                 | 0.02                 | U-Shaped                        | 1.41                                | 1     | 0.01                            | 0.01                 | 0.01                 |
+| A3-30                                                                                    | Influence of the calibration antenna feed cable           | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-31                                                                                    | Influence of the probe antenna cable                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna | 0.50                   | 0.43                 | 0.43                 | Rectangular                     | 1.73                                | 1     | 0.29                            | 0.25                 | 0.25                 |
+| A3-32                                                                                    | Short term repeatability                                  | 0.09                   | 0.09                 | 0.09                 | Gaussian                        | 1.00                                | 1     | 0.09                            | 0.09                 | 0.09                 |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                           |                        |                      |                      |                                 |                                     |       | <b>0.59</b>                     | <b>0.71</b>          | <b>0.71</b>          |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                           |                        |                      |                      |                                 |                                     |       | <b>1.17</b>                     | <b>1.39</b>          | <b>1.39</b>          |
+
+## 9.4.5 Plane Wave Synthesizer
+
+### 9.4.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 9.4.5.2 Test procedure
+
+#### 9.4.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+#### 9.4.5.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with *beam peak direction* of range antenna.
+- 2) Configure TX branch and carrier according to maximum power requirement and test configuration.
+- 3) Set the BS to transmit the applicable test signal.
+- 4) Measure the  $P_{DL\_RS}$  which is the measured signal power of DL RS EIRP (in the *beam peak direction*).
+- 5) Calculate  $EIRP_{DL\_RS}$  using the following equation:
+
+$$EIRP_{DL\_RS\_p(x)} = P_{DL\_RS\_meas} + L_{A \rightarrow C}.$$
+
+And
+
+$EIRP_{DL\_RS} = EIRP_{DL\_RS\_p1} + EIRP_{DL\_RS\_p2}$  where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+- 6) Repeat steps 2-5 for all conformance test *beam direction pairs* and test conditions.
+
+### 9.4.5.3 MU value derivation, FR1
+
+As the DL RS power is an absolute measurement most of the uncertainties form the EIRP accuracy remain the same. Also it can be noted that the measured signal is a wanted signal and hence will be beam formed in the same way as the wanted signal, hence any errors which may be dependent on the beam shape will be the same as for the EIRP accuracy measurement.
+
+**Table 9.4.5.3-1: PWS MU value derivation for OTA E-UTRA DL RS power measurement**
+
+| UID                                     | Uncertainty source                                                                                  | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                                                                     | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                                     |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A7-1a                                   | Misalignment and pointing error of BS                                                               | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C3-1                                    | DL-RS MU derived from conducted specification                                                       | 0.41                   | 0.56            | 0.56            | Gaussian                        | 1.00                                | 1              | 0.41                                     | 0.56            | 0.56            |
+| A7-2a                                   | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna | 0.05                   | 0.14            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08            | 0.12            |
+| A7-3                                    | RF leakage (calibration antenna connector terminated)                                               | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A7-4a                                   | QZ ripple experienced by BS                                                                         | 0.42                   | 0.43            | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25            | 0.33            |
+| A7-5                                    | Miscellaneous uncertainty                                                                           | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A7-14                                   | System non-linearity                                                                                | 0.10                   | 0.10            | 0.15            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.09            |
+| A7-13                                   | Frequency flatness of test system                                                                   | 0.13                   | 0.13            | 0.13            | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08            | 0.08            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                     |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                    | Uncertainty of the network analyzer                                                                 | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A7-6                                    | Mismatch (i.e. reference antenna, network analyser and reference cable)                             | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A7-7                                    | Insertion loss of receiver chain                                                                    | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A7-3                                    | RF leakage (calibration antenna connector terminated)                                               | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A7-8                                    | Influence of the calibration antenna feed cable                                                     | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                           | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A7-9                                    | Misalignment of positioning system                                                                  | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A7-1b                                   | Misalignment and pointing error of calibration antenna                                              | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A7-10                                   | Rotary joints                                                                                       | 0.00                   | 0.00            | 0.00            | U-shaped                        | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+
+|                                                                                          |                                                                                                              |      |      |      |             |      |   |             |             |             |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------|------|------|-------------|------|---|-------------|-------------|-------------|
+| A7-2b                                                                                    | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna | 0.12 | 0.12 | 0.15 | Rectangular | 1.73 | 1 | 0.07        | 0.07        | 0.09        |
+| A7-4b                                                                                    | QZ ripple experienced by calibration antenna                                                                 | 0.20 | 0.20 | 0.20 | Rectangular | 1.73 | 1 | 0.12        | 0.12        | 0.12        |
+| A7-11                                                                                    | Switching uncertainty                                                                                        | 0.02 | 0.02 | 0.02 | Rectangular | 1.73 | 1 | 0.01        | 0.01        | 0.01        |
+| A7-12                                                                                    | Field repeatability                                                                                          | 0.06 | 0.12 | 0.15 | Gaussian    | 1.00 | 1 | 0.06        | 0.12        | 0.15        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                                              |      |      |      |             |      |   | <b>0.63</b> | <b>0.78</b> | <b>0.82</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                              |      |      |      |             |      |   | <b>1.24</b> | <b>1.53</b> | <b>1.62</b> |
+
+## 9.4.6 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for the OTA E-UTRA DL RS power test can be derived from values captured in table 9.4.6-1, separately for each of the defined frequency ranges. The common maximum values are applicable for all test methods addressing OTA E-UTRA DL RS power test requirement. Based on the input values, the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values were derived.
+
+**Table 9.4.6-1: Test system specific measurement uncertainty values for the OTA E-UTRA DL RS power test**
+
+|                                                        | <b>Expanded uncertainty <math>u_e</math> (dB)</b> |                                           |                                           |
+|--------------------------------------------------------|---------------------------------------------------|-------------------------------------------|-------------------------------------------|
+|                                                        | <b><math>f \leq 3</math> GHz</b>                  | <b><math>3 &lt; f \leq 4.2</math> GHz</b> | <b><math>4.2 &lt; f \leq 6</math> GHz</b> |
+| Indoor Anechoic Chamber                                | 1.15                                              | 1.44                                      | 1.44                                      |
+| Compact Antenna Test Range                             | 1.35                                              | 1.60                                      | 1.60                                      |
+| One Dimensional Compact Range Chamber                  | 1.17                                              | 1.39                                      | 1.39                                      |
+| Plane Wave Synthesizer                                 | 1.24                                              | 1.53                                      | 1.62                                      |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.3</b>                                        | <b>1.5</b>                                | <b>1.5</b>                                |
+
+## 9.4.7 Test Tolerance for OTA E-UTRA DL RS power
+
+The TT was decided to be the same as the MU in FR1.
+
+**Table 9.4.7-1: Test Tolerance values for the OTA E-UTRA DL RS power**
+
+|                     | <b><math>f \leq 3</math> GHz</b> | <b><math>3\text{ GHz} &lt; f \leq 4.2\text{ GHz}</math></b> | <b><math>4.2\text{ GHz} &lt; f \leq 6\text{ GHz}</math></b> |
+|---------------------|----------------------------------|-------------------------------------------------------------|-------------------------------------------------------------|
+| Test Tolerance (dB) | <b>1.3</b>                       | <b>1.5</b>                                                  | <b>1.5</b>                                                  |
+
+# 9.5 OTA output power dynamics
+
+## 9.5.1 General
+
+Clause 9.5 captures MU and TT values derivation for the OTA output power dynamics directional requirement.
+
+There are a number of UTRA and E-UTRA dynamic power requirements, they are all relative requirements which specify the dynamic range and step size accuracy of UTRA code domain channels and E-UTRA RE's.
+
+As the requirements are differential many of the measurement uncertainty values may cancel out however, in some cases demodulated signal power level (code domain power or RE power) are compared to maximum carrier power. As such the differential measurements may use different test equipment setting and hence not all test equipment uncertainties are cancelled out.
+
+In all cases the measured signal are wanted signals and will be subject to the same beam forming as the main beam.
+
+## 9.5.2 Indoor Anechoic Chamber
+
+### 9.5.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+### 9.5.2.2 Test procedure
+
+#### 9.5.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2.
+
+#### 9.5.2.2.2 Stage 2: BS measurement
+
+Reference IAC testing procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions) where the appropriate measurement is:
+
+The appropriate test parameter in steps 5 - 7 for the output power dynamics vary depending on the specific measurement as described for the conducted measurement in TS 37.145-1 [21] in each case however the EIRP measurement is made on both polarisations and added as follows:
+
+$$\text{EIRP}_{\text{meas\_p(x)}} = P_{\text{meas\_p(x)}} + L_{A \rightarrow B}$$
+
+and
+
+$$\text{EIRP}_{\text{meas}} = \text{EIRP}_{\text{meas\_p1}} + \text{EIRP}_{\text{meas\_p2}}$$
+
+where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+Furthermore, the measurement is performed twice; once with the BS transmitting at  $P_{\text{rated,c,EIRP}}$  on all PRBs and then a second time with the BS transmitting on a single PRB. Both measurements are made in the same conformance direction in the same calibrated test setup. The ratio of these two EIRP levels is used to assess compliance for the OTA total power dynamic range.
+
+### 9.5.2.3 MU value derivation, FR1
+
+As the output power dynamics are relative measurements most of the uncertainties from the EIRP accuracy cancel out as the same error will be applied to both of the measured OTA signals.
+
+This includes all calibration errors, misalignment errors, impedance mismatch and mutual coupling.
+
+As the both the measured OTA signal will have the same beam pattern quiet zone errors, phase curvature errors also can be expected to be the same for both signals.
+
+The uncertainty budget descriptions are the same as those in clause 9.2.2.3 with the addition descriptions in table 9.5.2.3-1.
+
+The MU uncertainty assessment is shown in table 9.5.2.3-1, zero values have been omitted in the table for the sake of space, but still be considered as part of the budget.
+
+**Table 9.5.2.3-1: Indoor Anechoic Chamber measurement uncertainty value derivation for OTA total power dynamic range measurement**
+
+| UID                                                                    | Uncertainty source                              | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                 | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                 |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C3-2                                                                   | Total power dynamic range conducted uncertainty | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A1-8                                                                   | Random uncertainty                              | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                 |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                 |                        |                 |                 |                                 |                                     |                | <b>0.21</b>                              | <b>0.21</b>     | <b>0.21</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                 |                        |                 |                 |                                 |                                     |                | <b>0.41</b>                              | <b>0.41</b>     | <b>0.41</b>     |
+
+The same uncertainty assessments have been carried out for the UTRA dynamic range requirements, i.e.
+
+- Power control steps,
+- Power control dynamic range,
+- Total power dynamic range,
+- IPDL Time mask.
+
+In each case the uncertainty for the conducted measurement is the same as that for the conducted MU in TS 25.141 [2] as follows:
+
+- Power control steps, Uncertainty of conducted measurement = 0.1 dB, Expanded OTA uncertainty = 0.15 dB.
+- Power control dynamic range, Uncertainty of conducted measurement = 1.1 dB, Expanded OTA uncertainty = 1.11 dB.
+- Total power dynamic range, Uncertainty of conducted measurement = 0.3 dB, Expanded OTA uncertainty = 0.32 dB.
+- IPDL Time mask, Uncertainty of conducted measurement = 0.7dB, Expanded OTA uncertainty = 0.71 dB.
+
+## 9.5.3 Compact Antenna Test Range
+
+### 9.5.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.5.3.2 Test procedure
+
+#### 9.5.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 9.5.3.2.2 Stage 2: BS measurement
+
+Reference CATR measurement procedure in clause 9.2.3.2.2 where in step 6 the appropriate measurement is:
+
+The appropriate test parameter in step 6 for the output power dynamics vary depending on the specific measurement as described for the conducted measurement in each case however the EIRP measurement is made on both polarisations and added as follows:
+
+$$\text{EIRP}_{\text{meas\_p(x)}} = P_{\text{meas\_p(x)}} + L_{A \rightarrow B}.$$
+
+and
+
+$$EIRP_{\text{meas}} = EIRP_{\text{meas\_p1}} + EIRP_{\text{meas\_p2}}$$
+
+where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+Furthermore, the measurement is performed twice; once with the BS transmitting at  $P_{\text{rated,c,EIRP}}$  on all PRBs (in case of NR) and then a second time with the BS transmitting on a single PRB. Both measurements are made in the same conformance direction in the same calibrated test setup. The ratio of these two EIRP levels is used to assess compliance for the OTA total power dynamic range.
+
+### 9.5.3.3 MU value derivation, FR1
+
+As the output power dynamics are relative measurements most of the uncertainties from the EIRP accuracy cancel out as the same error will be applied to both of the measured OTA signals.
+
+This includes all calibration errors, misalignment errors, impedance mismatch and mutual coupling.
+
+As both the measured OTA signal will have the same beam pattern, quiet zone errors, phase curvature errors also can be expected to be the same for both signals.
+
+The uncertainty budget descriptions are the same as those in clause 9.2.3.2.2 with the addition descriptions in table 9.5.3.3-1.
+
+The MU uncertainty assessment is shown in table 9.5.3.3-1, zero values have been omitted in the table for the sake of space, but still be considered as part of the budget.
+
+**Table 9.5.3.3-1: CATR MU value derivation for OTA total power dynamic range measurement**
+
+| UID                                                                                      | Uncertainty source                              | Uncertainty value (dB) |                              |                              | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                              |                              |
+|------------------------------------------------------------------------------------------|-------------------------------------------------|------------------------|------------------------------|------------------------------|---------------------------------|-------------------------------------|-------|---------------------------------|------------------------------|------------------------------|
+|                                                                                          |                                                 | $f \leq 3 \text{ GHz}$ | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |                                 |                                     |       | $f \leq 3 \text{ GHz}$          | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+| <b>Stage 2: BS measurement</b>                                                           |                                                 |                        |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| C3-2                                                                                     | Total power dynamic range conducted uncertainty | 0.20                   | 0.20                         | 0.20                         | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                         | 0.20                         |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                 |                        |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                 |                        |                              |                              |                                 |                                     |       | 0.20                            | 0.20                         | 0.20                         |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                 |                        |                              |                              |                                 |                                     |       | 0.39                            | 0.39                         | 0.39                         |
+
+The same uncertainty assessments have been carried out for the UTRA dynamic range requirements, i.e.
+
+- Power control steps,
+- Power control dynamic range,
+- Total power dynamic range,
+- IPDL Time mask.
+
+In each case the uncertainty for the conducted measurement is the same as that for the conducted MU in TS 25.141 [2] as follows:
+
+- Power control steps: Uncertainty of conducted measurement = 0.1 dB, Expanded OTA uncertainty = 0.1 dB.
+- Power control dynamic range: Uncertainty of conducted measurement = 1.1 dB, Expanded OTA uncertainty = 1.1 dB.
+- Total power dynamic range: Uncertainty of conducted measurement = 0.3 dB, Expanded OTA uncertainty = 0.3 dB.
+- IPDL Time mask: Uncertainty of conducted measurement = 0.7 dB, Expanded OTA uncertainty = 0.7 dB.
+
+## 9.5.4 Near Field Test Range
+
+### 9.5.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+### 9.5.4.2 Test procedure
+
+#### 9.5.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 9.5.4.2.2 Stage 2: BS measurement
+
+The NFTR measurement procedure consists of the following steps:
+
+- 1) Measure full DL RS pattern according to the procedure in clause 9.4.4.2.2.
+- 2) From the *beam peak direction*: Measure the appropriate test parameter as specified for the conducted measurement. However the signal power is measured for both polarizations.
+
+### 9.5.4.3 MU value derivation, FR1
+
+As the output power dynamics are relative measurements most of the uncertainties from the EIRP accuracy cancel out as the same error will be applied to both of the measured OTA signals.
+
+The uncertainty budget descriptions are the same as those in table 9.4.4.3-1 (excluding uncertainties from the NF to FF transformation, since the transformation is not needed) with the addition descriptions in table 9.5.4.3-1.
+
+The MU uncertainty assessment is shown in table 9.5.4.3-1, zero values have been omitted in the table for the sake of space, but still be considered as part of the budget.
+
+**Table 9.5.4.3-1: NFTR MU value derivation for OTA E-UTRA total power dynamic range measurement**
+
+| UID                                                                                      | Uncertainty source                              | Uncertainty value (dB)         |                              |                              | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                              |                              |
+|------------------------------------------------------------------------------------------|-------------------------------------------------|--------------------------------|------------------------------|------------------------------|---------------------------------|-------------------------------------|-------|---------------------------------|------------------------------|------------------------------|
+|                                                                                          |                                                 | $f \leq 3 \text{ GHz}$         | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |                                 |                                     |       | $f \leq 3 \text{ GHz}$          | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+|                                                                                          |                                                 | <b>Stage 2: BS measurement</b> |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| C3-2                                                                                     | Total power dynamic range conducted uncertainty | 0.20                           | 0.20                         | 0.20                         | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                         | 0.20                         |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                 |                                |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                 |                                |                              |                              |                                 |                                     |       | 0.20                            | 0.20                         | 0.20                         |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                 |                                |                              |                              |                                 |                                     |       | 0.39                            | 0.39                         | 0.39                         |
+
+## 9.5.5 Plane Wave Synthesizer
+
+### 9.5.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 9.5.5.2 Test procedure
+
+#### 9.5.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+### 9.5.5.2.2 Stage 2: BS measurement
+
+Reference PWS measurement procedure in clause 9.2.6.2.2 where in step 4 the appropriate measurement is:
+
+The appropriate test parameter in step 4 for the output power dynamics vary depending on the specific measurement as described for the conducted measurement in each case however the EIRP measurement is made on both polarisations and added as follows:
+
+$$\text{EIRP}_{\text{meas\_p(x)}} = P_{\text{meas\_p(x)}} + L_{A \rightarrow C}.$$
+
+and
+
+$$\text{EIRP}_{\text{meas}} = \text{EIRP}_{\text{meas\_p1}} + \text{EIRP}_{\text{meas\_p2}}$$
+
+where the declared beam is the measured signal for any two orthogonal polarizations (denoted p1 and p2).
+
+Furthermore, the measurement is performed twice; once with the BS transmitting at  $P_{\text{rated,c,EIRP}}$  on all PRBs (in case of NR) and then a second time with the BS transmitting on a single PRB. Both measurements are made in the same conformance direction in the same calibrated test setup. The ratio of these two EIRP levels is used to assess compliance for the OTA total power dynamic range.
+
+### 9.5.5.3 MU value derivation, FR1
+
+As the output power dynamics are relative measurements most of the uncertainties from the EIRP accuracy cancel out as the same error will be applied to both of the measured OTA signals.
+
+The uncertainty budget descriptions are the same as those in table 9.2.6.3-1 with the addition descriptions in table 9.5.5.3-1.
+
+The MU uncertainty assessment is shown in table 9.5.5.3-1, zero values have been omitted in the table for the sake of space, but still be considered as part of the budget.
+
+**Table 9.5.5.3-1: PWS MU value derivation for OTA total power dynamic range measurement**
+
+| UID                                                                                      | Uncertainty source                              | Uncertainty value (dB) |                              |                              | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                              |                              |
+|------------------------------------------------------------------------------------------|-------------------------------------------------|------------------------|------------------------------|------------------------------|---------------------------------|-------------------------------------|-------|---------------------------------|------------------------------|------------------------------|
+|                                                                                          |                                                 | $f \leq 3 \text{ GHz}$ | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |                                 |                                     |       | $f \leq 3 \text{ GHz}$          | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+| <b>Stage 2: BS measurement</b>                                                           |                                                 |                        |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| C3-2                                                                                     | Total power dynamic range conducted uncertainty | 0.20                   | 0.20                         | 0.20                         | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                         | 0.20                         |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                 |                        |                              |                              |                                 |                                     |       |                                 |                              |                              |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                 |                        |                              |                              |                                 |                                     |       | 0.20                            | 0.20                         | 0.20                         |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                 |                        |                              |                              |                                 |                                     |       | 0.39                            | 0.39                         | 0.39                         |
+
+### 9.5.6 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for the OTA output power dynamics tests can be derived from values captured in tables 9.5.6-1 to 9.5.6-5, separately for each of the defined frequency ranges. The common maximum values are applicable for all test methods addressing certain OTA output power dynamics test requirement. Based on the input values, the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values were derived.
+
+The output power dynamic range MU for FR1 for up to 4.2 GHz was agreed to be the same as for eAAS WI. It is expected that the measurement chamber setup, calibration and measurement procedures and the MU budget will be identical for E-UTRA and NR.
+
+Furthermore, for the frequency range 4.2 – 6 GHz, the chamber and instrument uncertainties are the same as those for the frequency range 3 – 4.2 GHz, assuming testing of a BS designed for operation in licensed spectrum. The MU value was agreed to be  $\pm 0.4$  dB for all bands up to 6 GHz.
+
+For FR2: Similarly to FR1, since the OTA output power dynamic range requirement is a relative measurement, only the test equipment uncertainty is of importance. Based on expected test equipment uncertainty, the output power dynamic range MU for FR2 was decided to be  $\pm 0.4$  dB (same as for FR1).
+
+**Table 9.5.6-1: Test system specific measurement uncertainty values for the OTA E-UTRA and NR total power dynamic range test**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 0.41                            | 0.41                       | 0.41                       |
+| Compact Antenna Test Range                             | 0.39                            | 0.39                       | 0.39                       |
+| Near Field Test Range                                  | 0.39                            | 0.39                       | 0.39                       |
+| Plane Wave Synthesizer                                 | 0.39                            | 0.39                       | 0.39                       |
+| <b>Common maximum accepted test system uncertainty</b> | <b>0.4</b>                      | <b>0.4</b>                 | <b>0.4</b>                 |
+
+**Table 9.5.6-2: Test system specific measurement uncertainty values for the UTRA inner loop power control steps test**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 0.1                             | 0.1                        | 0.1                        |
+| Compact Antenna Test Range                             | 0.1                             | 0.1                        | 0.1                        |
+| Near Field Test Range                                  | 0.1                             | 0.1                        | 0.1                        |
+| Plane Wave Synthesizer                                 | 0.1                             | 0.1                        | 0.1                        |
+| <b>Common maximum accepted test system uncertainty</b> | <b>0.1</b>                      | <b>0.1</b>                 | <b>0.1</b>                 |
+
+**Table 9.5.6-3: Test system specific measurement uncertainty values for the UTRA power control dynamic range test**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 1.1                             | 1.1                        | 1.1                        |
+| Compact Antenna Test Range                             | 1.1                             | 1.1                        | 1.1                        |
+| Near Field Test Range                                  | 1.1                             | 1.1                        | 1.1                        |
+| Plane Wave Synthesizer                                 | 1.1                             | 1.1                        | 1.1                        |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.1</b>                      | <b>1.1</b>                 | <b>1.1</b>                 |
+
+**Table 9.5.6-4: Test system specific measurement uncertainty values for the UTRA total power dynamic range test**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 0.3                             | 0.3                        | 0.3                        |
+| Compact Antenna Test Range                             | 0.3                             | 0.3                        | 0.3                        |
+| Near Field Test Range                                  | 0.3                             | 0.3                        | 0.3                        |
+| Plane Wave Synthesizer                                 | 0.3                             | 0.3                        | 0.3                        |
+| <b>Common maximum accepted test system uncertainty</b> | <b>0.3</b>                      | <b>0.3</b>                 | <b>0.3</b>                 |
+
+**Table 9.5.6-5: Test system specific measurement uncertainty values for the UTRA IPDL time mask test**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 0.7                             | 0.7                        | 0.7                        |
+| Compact Antenna Test Range                             | 0.7                             | 0.7                        | 0.7                        |
+| Near Field Test Range                                  | 0.7                             | 0.7                        | 0.7                        |
+| Plane Wave Synthesizer                                 | 0.7                             | 0.7                        | 0.7                        |
+| <b>Common maximum accepted test system uncertainty</b> | <b>0.7</b>                      | <b>0.7</b>                 | <b>0.7</b>                 |
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 9.5.7 Test Tolerance for OTA output power dynamics
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA output power dynamics were derived based on values captured in clause 9.5.6.
+
+The TT was decided to be the same as the MU in FR1.
+
+**Table 9.5.7-1: Test Tolerance values for the OTA total power dynamic range, FR1**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 0.4            | 0.4                        | 0.4                        |
+
+**Table 9.5.7-2: Test Tolerance values for the OTA total power dynamic range, FR2**
+
+|                     | $24.25 < f < 29.5$ GHz | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+|---------------------|------------------------|---------------------|-----------------------|
+| Test Tolerance (dB) | 0.4                    | 0.4                 | 0.4                   |
+
+**Table 9.5.7-3: Test Tolerance values for the UTRA inner loop power control steps**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 0.1            | 0.1                        | 0.1                        |
+
+**Table 9.5.7-4: Test Tolerance values for the UTRA power control dynamic range**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 1.1            | 1.1                        | 1.1                        |
+
+**Table 9.5.7-5: Test Tolerance values for the UTRA total power dynamic range**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 0.3            | 0.3                        | 0.3                        |
+
+**Table 9.5.7-6: Test Tolerance values for the UTRA IPDL time mask**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (dB) | 0.7            | 0.7                        | 0.7                        |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.6 OTA transmitted signal quality: Frequency error
+
+### 9.6.1 General
+
+Clause 9.6 captures MU and TT values derivation for the OTA frequency error directional requirement.
+
+Frequency error is the measure of the difference between the actual BS transmit frequency and the assigned frequency. The same source shall be used for RF frequency and data clock generation.
+
+Frequency error is not affected by any time or frequency varying amplitude errors. It is possible that some aspects of the OTA environment may impact the signal fidelity; for example, ripple in a quiet zone relates to reflections in the chamber and may create a frequency specific ripple. It is not expected that such effects would have any significant impact on the frequency error As long as the signal is large enough the only measurement uncertainty will be associated with the measurement equipment. It is important that considering the chamber path loss and gain of the measurement antenna and equipment, the test equipment is provided with a sufficient RX power level. As a guide, measurement equipment vendors quote EVM accuracy down to approx. -20 dBm input power for E-UTRA signals.
+
+Few typical BS output power levels and antenna arrangements for different BS classes are captured in table 9.6.1-1:
+
+**Table 9.6.1-1: Typical BS output power levels**
+
+| BS class | Pout (dBm) | G_AAS (dBi) | L_ant (m) | d_FF (m) | FSPL (dB) | G_RX (dBi) | P_RX (dBm) |
+|----------|------------|-------------|-----------|----------|-----------|------------|------------|
+| WA BS    | 43         | 17          | 1         | 13.33    | 60.96     | 9          | 8.04       |
+| MR BS    | 38         | 9           | 0.5       | 6.67     | 54.94     | 9          | 1.06       |
+| LA BS    | 24         | 5           | 0.2       | 2.67     | 46.98     | 9          | -8.98      |
+
+It can be seen that there is considerable margin over -20 dBm for the received power level, so it seems unlikely that this will cause any measurement problems.
+
+As the OTA test system is not expected to substantially affect the measurement accuracy for frequency error the existing conducted MU can be used.
+
+### 9.6.2 Indoor Anechoic Chamber
+
+#### 9.6.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 9.6.2.2 Test procedure
+
+##### 9.6.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2.
+
+##### 9.6.2.2.2 Stage 2: BS measurement
+
+Reference IAC measurement procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions) where in steps 5 – 7 the appropriate measurement parameter is frequency error. In this case, however testing
+
+should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+### 9.6.2.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the frequency error uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the frequency error measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.6.3 Compact Antenna Test Range
+
+### 9.6.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.6.3.2 Test procedure
+
+#### 9.6.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 9.6.3.2.2 Stage 2: BS measurement
+
+As the frequency error is tested together with EVM, the CATR measurement procedure is same with EVM as in clause 9.7.3. The CATR testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of range antenna.
+- 2) Configure TX branch and carrier according to required test configuration.
+- 3) Measure frequency error of each carrier arriving at the measurement equipment (such as a spectrum analyzer or equivalent instrument).
+- 4) Repeat steps 2 - 3 for all conformance test direction as declared by the manufacturer in TS 37.145-2 [4] or TS 38.141-2 [6].
+- 5) Repeat steps 2 - 4 for all applicable conformance test models.
+
+NOTE: All the discussions above are based on the measurement pre-condition of reference clock synchronized between measurement system with RF frequency signal.
+
+### 9.6.3.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the frequency error uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the frequency error measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.6.4 Near Field Test Range
+
+### 9.6.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA Frequency Error type of measurements, NF to FF transform is not needed. Frequency Error is measured in Near Field for the declared direction.
+
+## 9.6.4.2 Test procedure
+
+### 9.6.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5 to ensure that the SNR at the measurement equipment input is appropriate and the reception signal level at the measurement equipment is within the dynamic range of measurement equipment.
+
+### 9.6.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+1. Align the BS with (Theta, Phi) angles corresponding to the declared conformance direction to be measured.
+2. Configure TX branch and carrier according to the manufacturer's declared rated output power.
+3. Set the BS to transmit the test signal according to applicable test models.
+4. Measure OTA frequency error of each carrier arriving at the measurement equipment (such as a spectrum analyzer or equivalent instrument).
+5. Repeat steps 2 - 4 for other applicable test models.
+
+For conformance tests, the OTA frequency error shall be measured at maximum power setting.
+
+### 9.6.4.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the frequency error uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the frequency error measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.6.5 Plane Wave Synthesizer
+
+### 9.6.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 9.6.5.2 Test procedure
+
+#### 9.6.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+#### 9.6.5.2.2 Stage 2: BS measurement
+
+As the frequency error is tested together with EVM, the PWS measurement procedure is same with EVM as in clause 9.7.5. The PWS testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of range antenna.
+- 2) Configure TX branch and carrier according to required test configuration.
+- 3) Measure frequency error of each carrier arriving at the measurement equipment (such as a spectrum analyzer or equivalent instrument).
+
+- 4) Repeat steps 2 - 3 for all conformance test direction as declared by the manufacturer in TS 37.145-2 [4] or TS 38.141-2 [6].
+- 5) Repeat steps 2 - 4 for all applicable conformance test models.
+
+NOTE: All the discussions above are based on the measurement pre-condition of reference clock synchronized between measurement system with RF frequency signal.
+
+### 9.6.5.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the frequency error uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the frequency error measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.6.6 Maximum accepted test system uncertainty
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the frequency error uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the frequency error measurement uncertainty. The frequency error MU is  $\pm 12$  Hz.
+
+The MU for FR1 for frequency error for up to 4.2 GHz was agreed to be the same as for eAAS WI. It is expected that the measurement chamber setup, calibration and measurement procedures and the MU budget will be identical for E-UTRA and NR.
+
+Furthermore, for the frequency range 4.2 – 6 GHz, the chamber and instrument uncertainties are the same as those for the frequency range 3 – 4.2 GHz, assuming testing of a BS designed for operation in licensed spectrum.
+
+For FR2, similarly to FR1, as long as the link budget is sufficient to provide a signal at the test equipment that is within its operating range, then the signal quality requirements MU depends only on the test equipment MU. In the beam center, for a CATR, there is sufficient link budget and thus the MU was decided based on expected test equipment performance.
+
+The MU values are  $\pm 12$  Hz for frequency error.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 9.6.7 Test Tolerance for frequency error
+
+Considering the methodology described in clause 5.1, Test Tolerance values for frequency error were derived based on values captured in clause 9.6.6.
+
+The TT values were agreed to be the same as the MU values.
+
+Frequency range specific Test Tolerance values for the frequency error test are defined in table 9.6.7-1.
+
+**Table 9.6.7-1: Test Tolerance values for frequency error, FR1**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (Hz) | 12             | 12                         | 12                         |
+
+**Table 9.6.7-2: Test Tolerance values for frequency error, FR2**
+
+|                     | $24.25 < f < 29.5$ GHz | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+|---------------------|------------------------|---------------------|-----------------------|
+| Test Tolerance (Hz) | 12                     | 12                  | 12                    |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.7 OTA transmitted signal quality: EVM
+
+### 9.7.1 General
+
+Clause 9.7 captures MU and TT values derivation for the OTA EVM directional requirement.
+
+The Error Vector Magnitude (EVM) is defined as measure of the difference between the ideal symbols and the measured symbols after the equalization. This difference is called the error vector. The equaliser parameters are defined in appropriate annex of TS 37.145-2 [4], or TS 38.141-2 [6]. The EVM result is defined as the square root of the ratio of the mean error vector power to the mean reference power expressed in percent.
+
+Although EVM is represented as a % it can also be thought of as a relative power ratio in dBc, when looked at as a power ratio the effect of potential amplitude errors in the OTA chamber can be seen.
+
+![Figure 6.7.1-1: Example of EVM as a power ratio in dB. The graph shows a vertical bar representing power (P(dBm)) on the y-axis against frequency (Freq) on the x-axis. The bar is divided into two sections: a top white section labeled 'Wanted' and a bottom red section labeled 'Noise'. A double-headed arrow between the two sections is labeled 'e.g. 45dBc'. To the right of the bar, the formula EVM_% = 10^(-45/20) * 100 = 0.56% is shown.](4d7310dc5ead3bcc30852c99ab09c31f_img.jpg)
+
+Figure 6.7.1-1: Example of EVM as a power ratio in dB. The graph shows a vertical bar representing power (P(dBm)) on the y-axis against frequency (Freq) on the x-axis. The bar is divided into two sections: a top white section labeled 'Wanted' and a bottom red section labeled 'Noise'. A double-headed arrow between the two sections is labeled 'e.g. 45dBc'. To the right of the bar, the formula EVM\_% = 10^(-45/20) \* 100 = 0.56% is shown.
+
+**Figure 6.7.1-1: Example of EVM as a power ratio in dB**
+
+In the example the co-channel noise is 45 dBc which equates to an EVM of 0.56 %, if the measurement system were to alter the ratio between the wanted signal and the co-channel signal then this would affect the EVM result in %.
+
+### 9.7.2 Indoor Anechoic Chamber
+
+#### 9.7.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 9.7.2.2 Test procedure
+
+##### 9.7.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2.
+
+##### 9.7.2.2.2 Stage 2: BS measurement
+
+Reference IAC measurement procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions) where in steps 5 - 7 measure the EVM for the applicable test case and the specific test models. In this case, however testing should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+### 9.7.2.3 MU value derivation, FR1
+
+As both the wanted signal and the noise signal are at the same frequency they will be measured at the same time the requirement is effectively differential and most of the OTA chamber errors will cancel out.
+
+The wanted signal will be beam formed and hence the errors used for the EIRP accuracy will be valid, however the co-channel noise may not be beam formed and hence could suffer different errors due to the chamber quiet zone, and phase profile. These items are included in both the calibration error and the measurement error, as the requirement is differential if there is a difference between the wanted and the unwanted it will only be due to the measurement phase. The calibration errors will cancel as calibration is only done one so they will be the same for both wanted and unwanted signals.
+
+Potentially, the EVM may vary in space due to different patterns of wanted signal and distortion. Thus for narrow beams, it may be possible that beam pointing and alignment errors could impact EVM results.
+
+As EVM is also dependent on the phase of the calibrated path it is possible that phase ripple in the quiet zone or elsewhere, which arises due to multipath reflections, may lead to frequency ripple and cause additional EVM errors which do not appear in a power accuracy analysis as done for EIRP accuracy.
+
+The potential impacts of both beam pointing misalignment and scattering within the chamber on the received waveform and measurement accuracy were investigated. The potential deviation in the measured EVM arising from beam pointing errors was examined considering a worst case scenario, in which variation in space of EVM is maximal due to the ideal signal being correlated and the distortion uncorrelated; hence the impact of misalignment error would be the difference between array gain and element gain. Even in this circumstance, alignment errors of several degrees would not lead to a significant error in the measured EVM. Considering all likely chamber sizes, for E-UTRA any scattering would fall within the cyclic prefix of the OFDM symbol and hence not cause ISI. Furthermore, the likely delay spread of any scattering would relate to coherence bandwidths much larger than any UTRA/E-UTRA channel bandwidth. Even if the scattered energy would cause interference, the interference level would anyhow not lead to a significant EVM increase. Thus it was concluded that the impact scattering within the measurement chamber would be negligible.
+
+The uncertainty causing by power variations when measuring OTA EVM is indicated in table 9.7.2.3-1:
+
+**Table 9.7.2.3-1: IAC MU value derivation for power uncertainty aspects of OTA EVM, FR1**
+
+| UID                                                                                      | Uncertainty source    | Uncertainty value (dB) |                   |                   | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                   |                   |
+|------------------------------------------------------------------------------------------|-----------------------|------------------------|-------------------|-------------------|---------------------------------|-------------------------------------|-------|---------------------------------|-------------------|-------------------|
+|                                                                                          |                       | $f < 3$ GHz            | $3 < f < 4.2$ GHz | $4.2 < f < 6$ GHz |                                 |                                     |       | $f < 3$ GHz                     | $3 < f < 4.2$ GHz | $4.2 < f < 6$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                       |                        |                   |                   |                                 |                                     |       |                                 |                   |                   |
+| A1-3                                                                                     | Quality of quiet zone | 0.1                    | 0.1               | 0.1               | Gaussian                        | 1                                   | 1     | 0.10                            | 0.10              | 0.10              |
+| A1-6                                                                                     | Phase curvature       | 0.05                   | 0.05              | 0.05              | Gaussian                        | 1                                   | 1     | 0.05                            | 0.05              | 0.05              |
+| A1-8                                                                                     | Random uncertainty    | 0.1                    | 0.1               | 0.1               | Rectangular                     | 1.73                                | 1     | 0.06                            | 0.06              | 0.06              |
+| <b>Stage 1: Calibration measurement</b>                                                  |                       |                        |                   |                   |                                 |                                     |       |                                 |                   |                   |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                       |                        |                   |                   |                                 |                                     |       | <b>0.13</b>                     | <b>0.13</b>       | <b>0.13</b>       |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                       |                        |                   |                   |                                 |                                     |       | <b>0.25</b>                     | <b>0.25</b>       | <b>0.25</b>       |
+
+The indoor anechoic chamber budget is carried out without consideration of the measurement equipment as this MU is given in %, converting to dB gives, for example:
+
+$$2\% \text{ is equivalent to } 20 \cdot \log_{10}(2/100) = -33.98 \text{ dB}$$
+
+If the unwanted signal is 0.25 dB higher than the wanted due to the test system then this will be degraded to -33.73 dB, and
+
+$$-33.73 \text{ dB is equivalent to: } 10^{(-33.73/20)} \cdot 100 = 2.06 \%$$
+
+Additional error due to potential phase error has not been considered however the potential increase due to the OTA test equipment is well within the contribution allowable with a 1 % linear MU.
+
+NOTE: Analysis of the phase uncertainties indicates that the contributions are not significant to affect the final MU value, however if future work indicates that phase or any other errors not related to amplitude calibration may affect the EVM measurement uncertainty the MU analysis may be re-examined.
+
+## 9.7.3 Compact Antenna Test Range
+
+### 9.7.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.7.3.2 Test procedure
+
+#### 9.7.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 9.7.3.2.2 Stage 2: BS measurement
+
+Reference CATR measurement procedure in clause 9.2.3.2.2 where in step 6 the appropriate measurement parameter is the EVM for the applicable test case and the specific test models. In this case, however testing should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+### 9.7.3.3 MU value derivation, FR1
+
+As both the wanted signal and the noise signal are at the same frequency they will be measured at the same time the requirement is effectively differential and most of the OTA chamber errors will cancel out.
+
+The wanted signal will be beam formed and hence the errors used for the EIRP accuracy will be valid, however the co-channel noise may not be beam formed and hence could suffer different errors due to the chamber quite zone, and phase profile. These items are included in both the calibration error and the measurement error, as the requirement is differential if there is a difference between the wanted and the unwanted it will only be due to the measurement phase. The calibration errors will cancel as calibration is only done one so they will be the same for both wanted and unwanted signals.
+
+Potentially, the EVM may vary in space due to different patterns of wanted signal and distortion. Thus for narrow beams, it may be possible that beam pointing and alignment errors could impact EVM results.
+
+As EVM is also dependent on the phase of the calibrated path it is possible that phase ripple in the quite zone or elsewhere, which arises due to multipath reflections, may lead to frequency ripple and cause additional EVM errors which do not appear in a power accuracy analysis as done for EIRP accuracy.
+
+The potential impacts of both beam pointing misalignment and scattering within the chamber on the received waveform and measurement accuracy were investigated. The potential deviation in the measured EVM arising from beam pointing errors was examined considering a worst case scenario, in which variation in space of EVM is maximal due to the ideal signal being correlated and the distortion uncorrelated; hence the impact of misalignment error would be the difference between array gain and element gain. Even in this circumstance, alignment errors of several degrees would not lead to a significant error in the measured EVM. Considering all likely chamber sizes, for E-UTRA any scattering would fall within the cyclic prefix of the OFDM symbol and hence not cause ISI. Furthermore, the likely delay spread of any scattering would relate to coherence bandwidths much larger than any UTRA/E-UTRA channel bandwidth. Even if the scattered energy would cause interference, the interference level would anyhow not lead to a significant EVM increase. Thus it was concluded that the impact scattering within the measurement chamber would be negligible.
+
+The uncertainty causing by power variations when measuring OTA EVM is indicated in table 9.7.3.3-1:
+
+**Table 9.7.3.3-1: CATR MU value derivation for power uncertainty aspects of OTA EVM, FR1**
+
+| UID                                                                                      | Uncertainty source                              | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------------------------|-------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                                          |                                                 | f < 3 GHz              | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |                                 |                                     |                | f < 3 GHz                                | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                 |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-2a                                                                                    | Standing wave between BS and test range antenna | 0.21                   | 0.21            | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| A2-4a                                                                                    | QZ ripple experienced by BS                     | 0.09                   | 0.09            | 0.09            | Normal                          | 1                                   | 1              | 0.09                                     | 0.09            | 0.09            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                 |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                 |                        |                 |                 |                                 |                                     |                | <b>0.18</b>                              | <b>0.18</b>     | <b>0.18</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                 |                        |                 |                 |                                 |                                     |                | <b>0.34</b>                              | <b>0.34</b>     | <b>0.34</b>     |
+
+The CATR budget is carried out without consideration of the measurement equipment as this MU is given in %, converting to dB gives, for example:
+
+$$2\% \text{ is equivalent to } 20 \cdot \log_{10}(2/100) = -33.98 \text{ dB}$$
+
+If the unwanted signal is 0.35 dB higher than the wanted due to the test system then this will be degraded to -33.63 dB, and
+
+$$-33.63 \text{ dB is equivalent to: } 10^{(-33.63/20)} \cdot 100 = 2.08\%$$
+
+Additional error due to potential phase error has not been considered however the potential increase due to then OTA test equipment is well within the contribution allowable with a 1% linear MU.
+
+NOTE: Analysis of the phase uncertainties indicates that the contributions are not significant to affect the final MU value, however if future work indicates that phase or any other errors not related to amplitude calibration may affect the EVM measurement uncertainty the MU analysis may be re-examined.
+
+## 9.7.4 Near Field Test Range
+
+### 9.7.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA EVM type of measurements, NF to FF transform is not needed. EVM is measured in Near Field for the declared directions.
+
+### 9.7.4.2 Test procedure
+
+#### 9.7.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 9.7.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+1. Align the BS with (Theta, Phi) angles corresponding to the declared conformance direction to be measured.
+2. Configure TX beamforming and carrier according to the manufacturer's declared rated output power.
+3. Set the BS to transmit the test signal according to the applicable test model.
+4. Measure OTA EVM of each carrier arriving at the measurement equipment (such as a spectrum analyzer or equivalent instrument).
+
+5. Repeat steps 3 - 4 for all conformance test *beam direction pairs* as declared by the manufacturer in TS 37.145-2 [4] or TS 38.141-2 [6].
+6. Repeat steps 3 - 5 for other applicable test models.
+
+For conformance tests, EVM shall be measured at maximum and minimum power settings while frequency error, and occupied BW at only maximum power setting.
+
+### 9.7.4.3 MU value derivation, FR1
+
+EVM is a relative measurement given that the wanted signal and noise signal are at the same frequency and measured at the same time therefore most of the OTA anechoic chamber errors will cancel out.
+
+Nearly all of uncertainty terms for the EVM measurement and EVM calibration are the same and hence EVM is a differential or relative measurement.
+
+Potentially, the EVM may vary in space due to different patterns of wanted signal and distortion. Thus for narrow beams, it may be possible that beam pointing and alignment errors could impact EVM results. The importance and impact of such effects is likely to be even smaller than for far field based measurements.
+
+As EVM is also dependent on the phase of the calibrated path it is possible that phase ripple in the quiet zone or elsewhere, which arises due to multipath reflections, may lead to frequency ripple and cause additional EVM errors which do not appear in a power accuracy analysis as done for EIRP accuracy. Analysis of the effect of such effects is that the effects will be even smaller than for far field based measurements.
+
+The Near Field budget is carried out without consideration of the measurement equipment therefore the MU is given in % and can be converted to dB, for example:
+
+$$2\% \text{ is equivalent to } 20 \cdot \log_{10}(2/100) = -33.98 \text{ dB}$$
+
+If the unwanted signal is 0.35 dB higher than the wanted due to the test system then this will be degraded to -33.63 dB, and
+
+$$-33.63 \text{ dB is equivalent to: } 10^{(-33.63/20)} \cdot 100 = 2.08\%$$
+
+Additional error due to potential phase error has not been considered however the potential increase due to the OTA test equipment is well within the contribution allowable with a 1% linear MU.
+
+For Near Field Test Range a new measurement uncertainty term shall be added to the MU. This term will take into account the fact that in Near Field the phase pattern will sum up so that the signal level is increasing while the noise level is the same. This MU term will only cause an error in the direction of increasing the reported EVM value and not decreasing it, and will depend on the implementation of the BS.
+
+NOTE: Analysis of the phase uncertainties indicates that the contributions are not significant enough to affect the final MU value, however if future work indicates that phase or any other errors not related to amplitude calibration may affect the EVM measurement uncertainty, the MU analysis may need to be re-examined.
+
+## 9.7.5 Plane Wave Synthesizer
+
+### 9.7.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 9.7.5.2 Test procedure
+
+#### 9.7.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+### 9.7.5.2.2 Stage 2: BS measurement
+
+Reference PWS measurement procedure in clause 9.4.5.2.2 where in step 4 the appropriate measurement parameter is the EVM for the applicable test case and the specific test models. In this case, however testing should be carried out in the *OTA coverage range* reference direction and *OTA coverage range* maximum directions.
+
+### 9.7.5.3 MU value derivation, FR1
+
+As both the wanted signal and the noise signal are at the same frequency they will be measured at the same time the requirement is effectively differential and most of the OTA chamber errors will cancel out.
+
+The wanted signal will be beam formed and hence the errors used for the EIRP accuracy will be valid, however the co-channel noise may not be beam formed and hence could suffer different errors due to the chamber quite zone, and phase profile. These items are included in both the calibration error and the measurement error, as the requirement is differential if there is a difference between the wanted and the unwanted it will only be due to the measurement phase. The calibration errors will cancel as calibration is only done one so they will be the same for both wanted and unwanted signals.
+
+Potentially, the EVM may vary in space due to different patterns of wanted signal and distortion. Thus for narrow beams, it may be possible that beam pointing and alignment errors could impact EVM results.
+
+As EVM is also dependent on the phase of the calibrated path it is possible that phase ripple in the quite zone or elsewhere, which arises due to multipath reflections, may lead to frequency ripple and cause additional EVM errors which do not appear in a power accuracy analysis as done for EIRP accuracy.
+
+The potential impacts of both beam pointing misalignment and scattering within the chamber on the received waveform and measurement accuracy were investigated. The potential deviation in the measured EVM arising from beam pointing errors was examined considering a worst case scenario, in which variation in space of EVM is maximal due to the ideal signal being correlated and the distortion uncorrelated; hence the impact of misalignment error would be the difference between array gain and element gain. Even in this circumstance, alignment errors of several degrees would not lead to a significant error in the measured EVM. Considering all likely chamber sizes, for E-UTRA any scattering would fall within the cyclic prefix of the OFDM symbol and hence not cause ISI. Furthermore, the likely delay spread of any scattering would relate to coherence bandwidths much larger than any UTRA/E-UTRA channel bandwidth. Even if the scattered energy would cause interference, the interference level would anyhow not lead to a significant EVM increase. Thus it was concluded that the impact scattering within the measurement chamber would be negligible.
+
+The uncertainty causing by power variations when measuring OTA EVM is indicated in table 9.7.5.3-1:
+
+**Table 9.7.5.3-1: PWS MU value derivation for power uncertainty aspects of OTA EVM, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                                  | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                                          |                                                                                                     | f < 3 G Hz             | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |                                 |                                     |                | f < 3 G Hz                               | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                     |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A7-2a                                                                                    | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna | 0.05                   | 0.14            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08            | 0.12            |
+| A7-4a                                                                                    | QZ ripple experienced by BS                                                                         | 0.42                   | 0.43            | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25            | 0.33            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                     |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                                     |                        |                 |                 |                                 |                                     |                | <b>0.24</b>                              | <b>0.26</b>     | <b>0.35</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                     |                        |                 |                 |                                 |                                     |                | <b>0.48</b>                              | <b>0.51</b>     | <b>0.68</b>     |
+
+The PWS budget is carried out without consideration of the measurement equipment as this MU is given in %, converting to dB gives, for example:
+
+$$2\% \text{ is equivalent to } 20 \cdot \log_{10}(2/100) = -33.98 \text{ dB}$$
+
+If the unwanted signal is 0.5 dB higher than the wanted due to the test system then this will be degraded to -33.48 dB, and
+
+-33.48 dB is equivalent to:  $10^{(-33.48/20)} * 100 = 2.12\%$
+
+Additional error due to potential phase error has not been considered however the potential increase due to then OTA test equipment is well within the contribution allowable with a 1% linear MU.
+
+NOTE: Analysis of the phase uncertainties indicates that the contributions are not significant to affect the final MU value, however if future work indicates that phase or any other errors not related to amplitude calibration may affect the EVM measurement uncertainty the MU analysis may be re-examined.
+
+## 9.7.6 Maximum accepted test system uncertainty
+
+Without consideration of any phase uncertainty, the amplitude error analysis shows the conducted MU of 1% can be maintained for the OTA MU (subject to the clarification noted in the limitations clause that the reported EVM may be greater than the real EVM due to the difference between near field and far field EVM values. The extent of such a difference is dependent on the architecture of the BS).
+
+NOTE: Analysis of the phase uncertainties indicates that the contributions are not significant to affect the final MU value, however if future work indicates that phase or any other errors not related to amplitude calibration may affect the EVM measurement uncertainty the MU analysis may be re-examined.
+
+The MU for FR1 for EVM below 4.2 GHz was agreed to be the same as for eAAS WI. It is expected that the measurement chamber setup, calibration and measurement procedures and the MU budget will be identical for E-UTRA and NR.
+
+Furthermore, for the frequency range 4.2 – 6 GHz, the chamber and instrument uncertainties are the same as those for the frequency range 3 – 4.2 GHz, assuming testing of a BS designed for operation in licensed spectrum.
+
+For FR2, similarly to FR1, as long as the link budget is sufficient to provide a signal at the test equipment that is within its operating range, then the signal quality requirements MU depends only on the test equipment MU. In the beam center, for a CATR, there is sufficient link budget and thus the MU was decided based on expected test equipment performance.
+
+The MU values are 1% for EVM.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 9.7.7 Test Tolerance for EVM
+
+Considering the methodology described in clause 5.1, Test Tolerance values for EVM were derived based on values captured in clause 9.7.6.
+
+The TT values were agreed to be the same as the MU values.
+
+Frequency range specific Test Tolerance values for the EVM test are defined in table 9.7.7-1.
+
+**Table 9.7.7-1: Test Tolerance values for EVM, FR1**
+
+|                    | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|--------------------|------------------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (%) | 1                      | 1                                        | 1                                        |
+
+**Table 9.7.7-2: Test Tolerance values for EVM, FR2**
+
+|                    | $24.25 < f < 29.5 \text{ GHz}$ | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+|--------------------|--------------------------------|-----------------------------|-------------------------------|
+| Test Tolerance (%) | 1                              | 1                           | 1                             |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.8 OTA transmitted signal quality: TAE
+
+### 9.8.1 General
+
+Clause 9.8 captures MU and TT values derivation for the OTA TAE directional requirement.
+
+TAE is the timing difference between 2 modulated signals, either TX diversity, MIMO or CA carriers. Conducted TAE is measured as follows:
+
+![Figure 9.8.1-1: Conducted TAE measurement set up. A block diagram showing a 'BS Under TX test' with four outputs labeled TX1, TX2, TX3, and TX4. TX1 and TX2 are connected to a combiner, which then connects to 'Measurement Equipment'. TX3 and TX4 are each connected to a 'Termination' block.](bdbdf9152f5224e9ced4fc6f402fbe45_img.jpg)
+
+Figure 9.8.1-1: Conducted TAE measurement set up. A block diagram showing a 'BS Under TX test' with four outputs labeled TX1, TX2, TX3, and TX4. TX1 and TX2 are connected to a combiner, which then connects to 'Measurement Equipment'. TX3 and TX4 are each connected to a 'Termination' block.
+
+Figure 9.8.1-1: Conducted TAE measurement set up
+
+As the conducted signals are combined before being input to the test equipment the OTA test is simple to implement.
+
+![Figure 9.8.1-2: OTA TAE measurement set up. A block diagram showing an 'AAS BS Under TX test' block. Two signals, 'Signal 1' (circled in blue) and 'Signal 2' (circled in red), are shown being transmitted from the BS towards a receive antenna. The antenna is connected to 'Measurement Equipment'.](6dd6f798e257cfeca7aef8c304f321f5_img.jpg)
+
+Figure 9.8.1-2: OTA TAE measurement set up. A block diagram showing an 'AAS BS Under TX test' block. Two signals, 'Signal 1' (circled in blue) and 'Signal 2' (circled in red), are shown being transmitted from the BS towards a receive antenna. The antenna is connected to 'Measurement Equipment'.
+
+Figure 9.8.1-2: OTA TAE measurement set up
+
+The OTA signals are both transmitted from the BS and added at the test receive antenna. As the test paths for the 2 signals are identical there are no additional timing errors added to the test system compared to the conducted test system.
+
+As the TAE requirement is a measure of timing difference it is not affected by the accuracy of the test system amplitude calibration and measurement uncertainties.
+
+As long as the signals fed into the measurement equipment are of a sufficient amplitude then the only measurement uncertainty will be that of the measurement equipment itself.
+
+The measurement equipment requires a level of > -20 dBm to accurately carry out the TAE.
+
+As the requirement is done for the wanted beam at full power, even for low power BS it is not anticipated the received test signal will be lower than -10 dBm.
+
+There may be a tiny impact to signal fidelity due to scattering in the chamber, however this will be insignificant and is not expected to impact TAE.
+
+As the OTA test system does not affect the measurement accuracy for TAE the existing conducted MU can be used.
+
+### 9.8.2 Indoor Anechoic Chamber
+
+#### 9.8.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+## 9.8.2.2 Test procedure
+
+### 9.8.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2.
+
+### 9.8.2.2.2 Stage 2: BS measurement
+
+Reference IAC measurement procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions) where in steps 5 - 7 the appropriate measurement parameter is TAE. In this case, however testing should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+## 9.8.2.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the TAE measurement uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the TAE measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.8.3 Compact Antenna Test Range
+
+### 9.8.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.8.3.2 Test procedure
+
+#### 9.8.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 9.8.3.2.2 Stage 2: BS measurement
+
+Reference CATR measurement procedure in clause 9.2.3.2.2 where in steps 4 - 6 the appropriate measurement parameter is TAE. In this case, however testing should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+The testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of the range antenna.
+- 2) Configure BS to transmit signals carrying reference signals. All beams must be pointed at the same direction.
+
+NOTE: The transmitted signals should represent the beam configuration with the lowest number of beams. Each beam should be identifiable using a reference signal.
+
+- For a BS declared to be capable of single carrier operation only, set BS to transmit according to rated beam EIRP level.
+  - If the BS supports intra band contiguous or non-contiguous Carrier Aggregation, set BS to transmit using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+  - If the BS supports inter band carrier aggregation, set BS to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+- 3) Measure TAE between the reference signals with signal/spectrum analyser or equivalent equipment.
+
+### 9.8.3.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the TAE measurement uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the TAE measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.8.4 Near Field Test Range
+
+### 9.8.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA TAE type of measurements, NF to FF transform is not needed. TAE is measured in Near Field for the declared direction.
+
+### 9.8.4.2 Test procedure
+
+#### 9.8.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 9.8.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+- 1) Align the BS with (Theta, Phi) angles corresponding to the declared conformance direction to be measured
+- 2) Configure BS to transmit signals carrying reference signals. All beams must be pointed at the same direction.
+
+NOTE: The transmitted signals should represent the beam configuration with the lowest number of beams. Each beam should be identifiable using a reference signal.
+
+- For a BS declared to be capable of single carrier operation only, set BS to transmit according to rated beam EIRP level.
+  - If the BS supports intra band contiguous or non-contiguous Carrier Aggregation, set BS to transmit using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+  - If the BS supports inter band carrier aggregation, set BS to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+- 3) Measure the TAE between the reference signals with signal/spectrum analyser or equivalent equipment.
+
+### 9.8.4.3 MU value derivation
+
+Refer to clause 9.8.3.3 for the OTA TAE measurement in CATR.
+
+## 9.8.4A Plane Wave Synthesizer
+
+### 9.8.4A.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.
+
+## 9.8.4A.2 Test procedure
+
+### 9.8.4A.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+### 9.8.4A.2.2 Stage 2: BS measurement
+
+Reference PWS measurement procedure in clause 9.2.6.2.2 where in steps 3 - 5 the appropriate measurement parameter is TAE. In this case, however testing should be carried out in the OTA conformance reference direction, not the *beam peak direction* of the *OTA peak directions set* reference direction.
+
+The testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of the range antenna.
+- 2) Configure BS to transmit signals carrying reference signals. All beams must be pointed at the same direction.
+
+NOTE: The transmitted signals should represent the beam configuration with the lowest number of beams. Each beam should be identifiable using a reference signal.
+
+- For a BS declared to be capable of single carrier operation only, set BS to transmit according to rated beam EIRP level.
+- If the BS supports intra band contiguous or non-contiguous Carrier Aggregation, set BS to transmit using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+- If the BS supports inter band carrier aggregation, set BS to transmit, for each band, a single carrier or all carriers, using the applicable test configuration and corresponding power setting specified in TS 37.145-2 [4] for AAS BS, or in TS 38.141-2 [6] for NR BS.
+
+- 3) Measure TAE between the reference signals with signal/spectrum analyser or equivalent equipment.
+
+### 9.8.4A.3 MU value derivation
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the TAE measurement uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the TAE measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU.
+
+## 9.8.5 Maximum accepted test system uncertainty
+
+The uncertainty in the power accuracy of the OTA test chamber will not affect the TAE measurement uncertainty.
+
+Possible phase variation in the chamber due to variation in the signal BW is not significant to affect the TAE measurement uncertainty.
+
+The conducted MU value is adopted for the OTA MU, and is  $\pm 25$  ns.
+
+The MU for FR1 for TAE up to 4.2 GHz was agreed to be the same as for eAAS WI. It is expected that the measurement chamber setup, calibration and measurement procedures and the MU budget will be identical for E-UTRA and NR.
+
+Furthermore, for the frequency range 4.2 – 6 GHz, the chamber and instrument uncertainties are the same as those for the frequency range 3 – 4.2 GHz, assuming testing of a BS designed for operation in licensed spectrum.
+
+For FR2, similarly to FR1, as long as the link budget is sufficient to provide a signal at the test equipment that is within its operating range, then the signal quality requirements MU depends only on the test equipment MU. In the beam center, for a CATR, there is sufficient link budget and thus the MU was decided based on expected test equipment performance.
+
+The MU values are 25 ns for time alignment error.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 9.8.6 Test Tolerance for TAE
+
+Considering the methodology described in clause 5.1, Test Tolerance values for TAE were derived based on values captured in clause 9.8.5.
+
+The TT values were agreed to be the same as the MU values.
+
+Frequency range specific Test Tolerance values for the TAE test are defined in table 9.8.6-1 and 9.8.6-2.
+
+**Table 9.8.6-1: Test Tolerance values for TAE, FR1**
+
+|                     | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|------------------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (ns) | 25                     | 25                                       | 25                                       |
+
+**Table 9.8.6-2: Test Tolerance values for TAE, FR2**
+
+|                     | $24.25 < f < 29.5 \text{ GHz}$ | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+|---------------------|--------------------------------|-----------------------------|-------------------------------|
+| Test Tolerance (ns) | 25                             | 25                          | 25                            |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.9 OTA occupied bandwidth
+
+### 9.9.1 General
+
+Clause 9.9 captures MU and TT values derivation for the OTA occupied bandwidth directional requirement.
+
+It is defined as the occupied bandwidth is the width of a frequency band such that, below the lower and above the upper frequency limits, the mean powers emitted are each equal to a specified percentage  $\beta/2$  of the total mean transmitted power.
+
+Occupied BW is specified in Hz.
+
+It is measured by taking a number of narrow band power measurements across the modulated BW and finding the half power level and hence the frequency points which correspond to the half power level. The measurement is effectively a differential measurement as total power and hence half power is found from the measured data.
+
+The only effect the measurement chamber would have on the accuracy of the measurement were if the frequency response of the chamber were not flat, however a 40 MHz BW is unlikely to introduce any significant frequency ripple in a RF chamber (40 MHz is 4% of 1 GHz) so this effect can be ignored.
+
+The largest error it is due to the number of measurement points taken, looking at the gap between points compared to the conducted MU:
+
+**Table 9.9.1-1: Occupied BW conducted MU**
+
+| <b>Channel bandwidth <math>BW_{Channel}</math> (MHz)</b> | <b>0.2</b> | <b>1.4</b> | <b>3</b> | <b>5</b> | <b>10</b> | <b>15</b> | <b>20</b> | <b>&gt;20</b>                                                       |
+|----------------------------------------------------------|------------|------------|----------|----------|-----------|-----------|-----------|---------------------------------------------------------------------|
+| <b>Span (MHz)</b>                                        | 0.4        | 10         | 10       | 10       | 20        | 30        | 40        | $2 \times BW_{Channel\_CA}$                                         |
+| <b>Minimum number of measurement points</b>              | 400        | 142<br>9   | 667      | 400      | 400       | 400       | 400       | $\left\lceil \frac{2 \times BW_{Channel\_CA}}{100kHz} \right\rceil$ |
+| <b>Gap between samples (MHz)</b>                         | 0.001      | 0.01       | 0.01     | 0.025    | 0.05      | 0.075     | 0.1       | 0.1                                                                 |
+| <b>Conducted MU (MHz)</b>                                |            | 0.03       | 0.03     | 0.1      | 0.1       | 0.3       | 0.3       | 0.3                                                                 |
+
+The MU is 3 to 4 time larger than the distance between the measurement points. Which allows the estimation of the 3dB point to be 1.5 to 2 steps out on each side of the modulated band width.
+
+As the OTA system will not introduce any additional frequency error and it will not introduce any additional differential amplitude error, the MU for the OTA measurement should be the same as for the conducted requirement.
+
+It should be noted that the signal power level at the bandwidth edge required for meeting the OBW requirement is in general at least 20dB higher than the level that is required to meet unwanted emissions requirements. Thus there is very substantial room to accommodate measurement uncertainty for the OBW requirement.
+
+## 9.9.2 Indoor Anechoic Chamber
+
+### 9.9.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+### 9.9.2.2 Test procedure
+
+#### 9.9.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2.
+
+#### 9.9.2.2.2 Stage 2: BS measurement
+
+Reference IAC procedure in clause 9.2.2.2.2 (i.e. EIRP accuracy measurement procedure for Normal test conditions) where in step 5 - 7 the appropriate measurements needed for calculating occupied bandwidth.
+
+### 9.9.2.3 MU value derivation
+
+The MU value is the same as the conducted value given in table 9.9.1-1.
+
+## 9.9.3 Compact Antenna Test Range
+
+### 9.9.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 9.9.3.2 Test procedure
+
+#### 9.9.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 9.9.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Configure transmitter according to the manufacturer's declared EIRP at rated TRP.
+- 2) Set the BS to transmit the test signal according to applicable test model for the tested carrier BW.
+- 3) Align BS such that *beam peak direction* of probe antenna is aligned with the reference direction within the *OTA coverage range*.
+- 4) Measure the OTA occupied BW for a single carrier positioned at M channel.
+
+### 9.9.3.3 MU value derivation
+
+The MU value is the same as the conducted value given in table 9.9.1-1.
+
+## 9.9.4 Near Field Test Range
+
+### 9.9.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA occupied BW type of measurements, NF to FF transform is not needed. Occupied BW is measured in Near Field for the declared direction.
+
+### 9.9.4.2 Test procedure
+
+#### 9.9.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 9.9.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+- 1) Align the BS with (Theta, Phi) angles corresponding to the declared *beam peak direction* to be measured.
+- 2) Configure TX branch and carrier according to the manufacturer's declared rated output power.
+- 3) Set the BS to transmit the test signal according to the applicable test model.
+- 4) Measure OTA occupied BW of each carrier arriving at the measurement equipment (such as a spectrum analyzer or equivalent instrument).
+- 5) Repeat steps 3 - 4 for other applicable test models.
+
+For conformance tests, the OTA occupied BW shall be measured at maximum power setting.
+
+### 9.9.4.3 MU value derivation
+
+The MU value is the same as the conducted value given in table 9.9.1-1.
+
+## 9.9.5 Plane Wave Synthesizer
+
+### 9.9.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 9.9.5.2 Test procedure
+
+#### 9.9.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+#### 9.9.5.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Configure transmitter according to the manufacturer's declared EIRP at rated TRP.
+- 2) Set the BS to transmit the test signal according to applicable test model for the tested carrier BW.
+- 3) Align BS such that *beam peak direction* of probe antenna is aligned with the reference direction within the *OTA coverage range*.
+- 4) Measure the OTA occupied BW for a single carrier positioned at M channel.
+
+#### 9.9.5.3 MU value derivation
+
+The MU value is the same as the conducted value given in table 9.9.1-1.
+
+### 9.9.6 Maximum accepted test system uncertainty
+
+For E-UTRA, the OTA occupied BW MU is the same as the conducted MU and is as follows:
+
+- 1.4 MHz, 3 MHz Channel BW: 30 kHz
+- 5 MHz, 10 MHz Channel BW: 100 kHz
+- 15 MHz,  $\geq 20$  MHz: Channel BW: 300 kHz
+
+For NR in FR1, the MU for the OTA occupied bandwidth depends on the roll-off of the transmitted signal and the instrument MU, not on the OTA chamber related MU. In principle, the occupied bandwidth MU was agreed to be the same as for E-UTRA. However NR covers larger BS channel bandwidths than E-UTRA, and thus additional MU relating to larger channel bandwidths were estimated. The MU was decided based on the density of power measurements within the channel bandwidth and the expected test instrument performance.
+
+For NR in FR1, the MU was agreed to be:
+
+- $\pm 100$  kHz for BS channel bandwidths up to 10 MHz,
+- $\pm 300$  kHz for  $10 \text{ MHz} < \text{BS channel bandwidth} \leq 50 \text{ MHz}$ , and
+- $\pm 300$  kHz for  $50 \text{ MHz} < \text{BS channel bandwidths} \leq 100 \text{ MHz}$ .
+
+For NR in FR2, based on expected test equipment performance, the MU for occupied bandwidth was decided to be:
+
+- $\pm 600$  kHz (same as for FR1 for channel bandwidths greater than 50 MHz).
+
+For NR in FR2, similarly to FR1, as long as the link budget is sufficient to provide a signal at the test equipment that is within its operating range, then the occupied bandwidth MU depends only on the test equipment MU. In the beam center, for a CATR, there is sufficient link budget and thus the MU was decided based on expected test equipment performance, considering the agreed density of power measurements in the frequency domain.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+### 9.9.7 Test Tolerance for OTA occupied bandwidth
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA occupied bandwidth were derived based on values captured in clause 9.9.6.
+
+For NR in FR1 as well as in FR2, the TT value was agreed to be 0 Hz.
+
+Frequency range specific Test Tolerance values for the OTA occupied bandwidth test are defined in tables 9.9.7-1 and 9.9.7-2.
+
+**Table 9.9.7-1: Test Tolerance values for the EIRP accuracy in Normal test conditions, FR1**
+
+|                     | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+|---------------------|----------------|----------------------------|----------------------------|
+| Test Tolerance (Hz) | 0              | 0                          | 0                          |
+
+**Table 9.9.7-2: Test Tolerance values for the EIRP accuracy in Normal test conditions, FR2**
+
+|                     | $24.25 < f < 29.5$ GHz | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+|---------------------|------------------------|---------------------|-----------------------|
+| Test Tolerance (Hz) | 0                      | 0                   | 0                     |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 9.10 OTA TX OFF power and transmitter transient period
+
+### 9.10.1 General
+
+Clause 9.10 captures MU and TT values derivation for the OTA TX OFF power and transmitter transient period directional requirements in FR2.
+
+This clause is only applicable to the NR operation in FR2.
+
+OTA TX OFF power and transmitter transient period for FR1 is a co-location requirement is and captured in clause 10.6.2.
+
+### 9.10.2 Compact Antenna Test Range
+
+#### 9.10.2.1 Measurement system description
+
+The MU assessment was carried out using a CATR chamber only. However other chamber types are not precluded if suitable MU assessment is done.
+
+Measurement system description is captured in clause 7.3.1.
+
+#### 9.10.2.2 Test procedure
+
+##### 9.10.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+##### 9.10.2.2.2 Stage 2: BS measurement
+
+NOTE: CATR-specific test procedure was not provided at the time of creation of this TR. Refer appropriate test procedure for BS type 2-O in TS 38.141-2, clause 6.5.2.4.2.1 with FR2 specific procedure steps in TS 38.141-2, clause 6.5.2.4.2.3.
+
+#### 9.10.2.3 MU value derivation, FR2
+
+The MU assessment was carried out using a CATR chamber only. However other chamber types are not precluded if suitable MU assessment is done.
+
+The CATR test setup and calibration and measurement procedures for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures. However, it is noted that in order to achieve the test instrument uncertainties that were assumed, calibration of the spectrum analyzer may be needed.
+
+**Table 9.10.2.3-1: CATR uncertainty assessment for EIRP measurements for transmitter OFF power and transmitter transient period**
+
+| UID                                                                                      | Uncertainty source                                                                                                                                        | Uncertainty value    |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty $u_i$ (dB) |                   |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|---------------------------------|-------------------------------------|----------------|---------------------------------|-------------------|
+|                                                                                          |                                                                                                                                                           | 24.25 < f ≤ 29.5 GHz | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz            | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                                                                           |                      |                   |                                 |                                     |                |                                 |                   |
+| A2-1a                                                                                    | Misalignment and pointing error of BS (for EIRP)                                                                                                          | 0.20                 | 0.20              | Exp. normal                     | 2.00                                | 1              | 0.10                            | 0.10              |
+| C1-9                                                                                     | Uncertainty of the RF power measurement equipment standard uncertainty $\sigma$ (dB) of the absolute level for a time domain wideband measurement for FR2 | 1.25                 | 1.45              | Gaussian                        | 1.00                                | 1              | 1.25                            | 1.45              |
+| A2-2a                                                                                    | Standing wave between BS and test range antenna                                                                                                           | 0.03                 | 0.03              | U-shaped                        | 1.41                                | 1              | 0.02                            | 0.02              |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                                                     | 0.01                 | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                            | 0.01              |
+| A2-4a                                                                                    | QZ ripple experienced by BS                                                                                                                               | 0.40                 | 0.40              | Gaussian                        | 1.00                                | 1              | 0.40                            | 0.40              |
+| A2-12                                                                                    | Frequency flatness of test system                                                                                                                         | 0.25                 | 0.25              | Gaussian                        | 1.00                                | 1              | 0.25                            | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                                                                           |                      |                   |                                 |                                     |                |                                 |                   |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                                                                                       | 0.30                 | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                            | 0.30              |
+| A2-5b                                                                                    | Mismatch of receiver chain for low power receiver                                                                                                         | 0.72                 | 0.72              | U-shaped                        | 1.41                                | 1              | 0.51                            | 0.51              |
+| A2-6                                                                                     | Insertion loss of receiver chain                                                                                                                          | 0.00                 | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                            | 0.00              |
+| A2-3                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                                                     | 0.01                 | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                            | 0.01              |
+| A2-7                                                                                     | Influence of the calibration antenna feed cable                                                                                                           | 0.21                 | 0.29              | U-shaped                        | 1.41                                | 1              | 0.15                            | 0.21              |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                                                                                                 | 0.52                 | 0.52              | Rectangular                     | 1.73                                | 1              | 0.30                            | 0.30              |
+| A2-8                                                                                     | Misalignment positioning system                                                                                                                           | 0.00                 | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                            | 0.00              |
+| A2-1b                                                                                    | Misalignment and pointing error of calibration antenna (for EIRP)                                                                                         | 0.00                 | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                            | 0.00              |
+| A2-9                                                                                     | Rotary joints                                                                                                                                             | 0.00                 | 0.00              | U-shaped                        | 1.41                                | 1              | 0.00                            | 0.00              |
+| A2-2b                                                                                    | Standing wave between calibration antenna and test range antenna                                                                                          | 0.09                 | 0.09              | U-shaped                        | 1.41                                | 1              | 0.06                            | 0.06              |
+| A2-4b                                                                                    | QZ ripple experienced by calibration antenna                                                                                                              | 0.01                 | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                            | 0.01              |
+| A2-11                                                                                    | Switching uncertainty                                                                                                                                     | 0.10                 | 0.10              | Rectangular                     | 1.73                                | 1              | 0.06                            | 0.06              |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                                                                                           |                      |                   |                                 |                                     |                | <b>1.50</b>                     | <b>1.68</b>       |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> – confidence interval of 95 %) (dB)</b> |                                                                                                                                                           |                      |                   |                                 |                                     |                | <b>2.95</b>                     | <b>3.29</b>       |
+
+### 9.10.3 Maximum accepted test system uncertainty
+
+The MU assessment was carried out using a CATR chamber only. However other chamber types are not precluded if suitable MU assessment is done.
+
+**Table 9.10.3-1: Maximum accepted test system uncertainty values for the EIRP accuracy, FR2**
+
+|                                                                                                                                                                                                                                                                                                               | 24.25 < f < 29.5 GHz | 37 < f < 43.5 GHz | 43.5 < f < 48.2 GHz |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------|---------------------|
+| Maximum accepted test system uncertainty (dB)                                                                                                                                                                                                                                                                 | 2.9                  | 3.3               | 3.6 (NOTE)          |
+| NOTE: MU estimation for 43.5 < f < 48.2 GHz was derived based on the linear approximation (based on MU values for lower frequency ranges). MU extrapolation approach was used instead of the typical derivation of the Expanded MU based on the MU budget calculations, as in case of lower frequency ranges. |                      |                   |                     |
+
+## 9.10.4 Test Tolerance for OTA TX OFF power and transmitter transient period
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA TX OFF power and transmitter transient period were derived based on values captured in clause 9.10.3.
+
+The TT value was agreed to be the same as the MU.
+
+Frequency range specific Test Tolerance values for the OTA TX OFF power and transmitter transient period test are defined in table 9.10.4-1.
+
+**Table 9.10.4-1: Test Tolerance values for the EIRP accuracy, FR2**
+
+|                     | 24.25 < f < 29.5 GHz | 37 < f < 43.5 GHz | 43.5 < f < 48.2 GHz |
+|---------------------|----------------------|-------------------|---------------------|
+| Test Tolerance (dB) | 2.9                  | 3.3               | 3.6                 |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+# 10 RX directional requirements
+
+## 10.1 General
+
+RX in-band directional requirements all use a wanted signal at a specified EIS power level and throughput/BER quality metric. Requirements which also include an in-band interferer have the wanted signal and the interferer coming from the same direction within the specified RoAoA.
+
+For simplicity since OTA requirements do not all use the same RAT-specific test models nor the same reference measurement channels, the OTA test procedures have been kept general by using "applicable test signal" and "applicable reference measurement channel" where the RAT-specific test model and reference measurement channels can be found in AAS BS or NR BS test specifications TS 37.145-2 [4] and TS 38.141-2 [6].
+
+NOTE 1: All the calibration and test procedures are valid for FR1 as well as FR2, unless otherwise stated.
+
+NOTE 2: All the MU and TT values derivations are valid for Normal test conditions, unless otherwise stated.
+
+For wanted signal frequency above 4.2 GHz in FR1 (4.2 GHz < f ≤ 6 GHz), it has been agreed that MU are obtained as:
+
+With
+
+1.96 0.58
+
+And
+
+## 10.2 OTA sensitivity
+
+### 10.2.1 General
+
+Clause 10.2 captures MU and TT values derivation for the OTA sensitivity directional requirement.
+
+### 10.2.2 Indoor Anechoic Chamber
+
+#### 10.2.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 10.2.2.2 Test procedure
+
+##### 10.2.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for RX requirements depicted in figure 8.2-2.
+
+##### 10.2.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with its manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with testing system.
+- 2) Set the BS to be satisfied with the *sensitivity RoAoA* covering conformance testing receiving direction.
+- 3) Rotate the BS to make the conformance testing receiving direction aligned with the *beam peak direction* of the reference antenna at the calibration stage.
+- 4) For FDD, start BS transmission using applicable test model at manufacturer's declared rated output power.
+- 5) Set the test signal mean power at the RF signal source generator as the declared minimum EIS level plus  $L_{cal, A \rightarrow D}$  (as defined in clause 8.2) and applicable reference measurement channel .
+- 6) Measure the throughput.
+- 7) Repeat the above steps 2 ~ 6 per conformance testing direction.
+
+#### 10.2.2.3 MU value derivation, FR1
+
+Table 10.2.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 10.2.2.3-1: IAC MU value derivation for OTA sensitivity measurement, FR1**
+
+| UID                                     | Uncertainty source                                                                               | Uncertainty value (dB) |                  |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|-----------------------------------------|--------------------------------------------------------------------------------------------------|------------------------|------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                         |                                                                                                  | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GH z | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GH z | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                                  |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| B1-1                                    | Positioning misalignment between the BS and the reference antenna                                | 0.03                   | 0.03             | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| B1-2                                    | Pointing misalignment between the BS and the transmitting antenna                                | 0.30                   | 0.30             | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17             | 0.17            |
+| B1-3                                    | Quality of quiet zone                                                                            | 0.10                   | 0.10             | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10             | 0.10            |
+| B1-4a                                   | Polarization mismatch between the BS and the transmitting antenna                                | 0.01                   | 0.01             | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| B1-5a                                   | Mutual coupling between the BS and the transmitting antenna                                      | 0.00                   | 0.00             | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| B1-6                                    | Phase curvature                                                                                  | 0.05                   | 0.05             | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05             | 0.05            |
+| C1-2                                    | Uncertainty of the RF signal generator                                                           | 0.46                   | 0.46             | 0.46            | Gaussian                        | 1.00                                | 1              | 0.46                                     | 0.46             | 0.46            |
+| B1-7                                    | Impedance mismatch in the transmitting chain                                                     | 0.14                   | 0.23             | 0.23            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.16             | 0.16            |
+| B1-8                                    | Random uncertainty                                                                               | 0.10                   | 0.10             | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                  |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| B1-9                                    | Impedance mismatch between the transmitting antenna and the network analyzer                     | 0.05                   | 0.05             | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04             | 0.04            |
+| B1-10                                   | Positioning and pointing misalignment between the reference antenna and the transmitting antenna | 0.01                   | 0.01             | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| B1-11                                   | Impedance mismatch between the reference antenna and network analyzer                            | 0.05                   | 0.05             | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04             | 0.04            |
+| B1-3                                    | Quality of quiet zone                                                                            | 0.10                   | 0.10             | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10             | 0.10            |
+| B1-4b                                   | Polarization mismatch between the reference antenna and the transmitting antenna                 | 0.01                   | 0.01             | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| B1-5b                                   | Mutual coupling between the reference antenna and the transmitting antenna                       | 0.00                   | 0.00             | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| B1-6                                    | Phase curvature                                                                                  | 0.05                   | 0.05             | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05             | 0.05            |
+| C1-3                                    | Uncertainty of the network analyzer                                                              | 0.13                   | 0.20             | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20             | 0.20            |
+| B1-12                                   | Influence of the reference antenna feed cable                                                    | 0.05                   | 0.05             | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| B1-13                                   | Reference antenna feed cable loss measurement uncertainty                                        | 0.06                   | 0.06             | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| B1-14                                   | Influence of the transmitting antenna feed cable                                                 | 0.05                   | 0.05             | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                        | 0.50                   | 0.43             | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25            |
+| B1-15                                   | Uncertainty of the absolute gain of the transmitting antenna                                     | 0.00                   | 0.00             | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+
+|                                                                                          |             |             |             |
+|------------------------------------------------------------------------------------------|-------------|-------------|-------------|
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         | <b>0.62</b> | <b>0.64</b> | <b>0.64</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> | <b>1.22</b> | <b>1.25</b> | <b>1.25</b> |
+
+#### 10.2.2.4 MU value derivation, FR2
+
+Table 10.2.2.4-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in Indoor Anechoic Chamber (Normal test conditions, FR2).
+
+**Table 10.2.2.4-1: IAC MU value derivation for OTA sensitivity measurement, FR2**
+
+| UID                                     | Uncertainty source                                                                               | Uncertainty value    |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|-----------------------------------------|--------------------------------------------------------------------------------------------------|----------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                         |                                                                                                  | 24.25 < f < 29.5 GHz | 37 < f < 43.5 GHz |                                 |                                     |                | 24.25 < f < 29.5 GHz                     | 37 < f < 43.5 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                                  |                      |                   |                                 |                                     |                |                                          |                   |
+| B1-1                                    | Positioning misalignment between the BS and the reference antenna                                | 0.18                 | 0.18              | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10              |
+| B1-2                                    | Pointing misalignment between the BS and the transmitting antenna                                | 0.18                 | 0.18              | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10              |
+| B1-3                                    | Quality of quiet zone                                                                            | 0.10                 | 0.10              | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10              |
+| B1-4a                                   | Polarization mismatch between the BS and the transmitting antenna                                | 0.02                 | 0.02              | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01              |
+| B1-5a                                   | Mutual coupling between the BS and the transmitting antenna                                      | 0.00                 | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| B1-6                                    | Phase curvature                                                                                  | 0.07                 | 0.07              | Gaussian                        | 1.00                                | 1              | 0.07                                     | 0.07              |
+| C1-2                                    | Uncertainty of the RF signal generator                                                           | 0.90                 | 0.90              | Gaussian                        | 1.00                                | 1              | 0.90                                     | 0.90              |
+| B1-7                                    | Impedance mismatch in the transmitting chain                                                     | 0.42                 | 0.42              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.30              |
+| B1-8                                    | Random uncertainty                                                                               | 0.18                 | 0.25              | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.14              |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                  |                      |                   |                                 |                                     |                |                                          |                   |
+| B1-9                                    | Impedance mismatch between the transmitting antenna and the network analyzer                     | 0.43                 | 0.57              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.40              |
+| B1-10                                   | Positioning and pointing misalignment between the reference antenna and the transmitting antenna | 0.43                 | 0.43              | Rectangular                     | 1.73                                | 1              | 0.25                                     | 0.25              |
+| B1-11                                   | Impedance mismatch between the reference antenna and network analyzer                            | 0.43                 | 0.57              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.40              |
+| B1-3                                    | Quality of quiet zone                                                                            | 0.10                 | 0.10              | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10              |
+| B1-4b                                   | Polarization mismatch between the reference antenna and the transmitting antenna                 | 0.02                 | 0.02              | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01              |
+| B1-5b                                   | Mutual coupling between the reference antenna and the transmitting antenna                       | 0.00                 | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| B1-6                                    | Phase curvature                                                                                  | 0.07                 | 0.07              | Gaussian                        | 1.00                                | 1              | 0.07                                     | 0.07              |
+| C1-3                                    | Uncertainty of the network analyzer                                                              | 0.30                 | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| B1-12                                   | Influence of the reference antenna feed cable                                                    | 0.18                 | 0.18              | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10              |
+| B1-13                                   | Reference antenna feed cable loss measurement uncertainty                                        | 0.10                 | 0.10              | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10              |
+| B1-14                                   | Influence of the transmitting antenna feed cable                                                 | 0.18                 | 0.18              | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10              |
+
+|                                                                                          |                                                              |      |      |             |      |   |             |             |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------|------|------|-------------|------|---|-------------|-------------|
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna    | 0.52 | 0.52 | Rectangular | 1.73 | 1 | 0.30        | 0.30        |
+| B1-15                                                                                    | Uncertainty of the absolute gain of the transmitting antenna | 0.00 | 0.00 | Rectangular | 1.73 | 1 | 0.00        | 0.00        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                              |      |      |             |      |   | <b>1.19</b> | <b>1.25</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                              |      |      |             |      |   | <b>2.33</b> | <b>2.46</b> |
+
+## 10.2.3 Compact Antenna Test Range
+
+### 10.2.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1.
+
+### 10.2.3.2 Test procedure
+
+#### 10.2.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 10.2.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with *beam peak direction* of range antenna.
+- 2) Configure signal generator, one port (polarization) and one carrier at a time according to maximum power requirement.
+- 3) Start with signal level at sensitivity level using applicable test model.
+- 4) Calculate EIS per port (polarization) at this point with  $EIS = PBER - L_{A \rightarrow B}$ .
+- 5) Repeat steps 2 - 4 for all conformance test *beam direction pairs*.
+
+### 10.2.3.3 MU value derivation, FR1
+
+Table 10.2.3.3-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in CATR (Normal test conditions, FR1).
+
+**Table 10.2.3.3-1: CATR MU value derivation for OTA sensitivity measurements, Normal test conditions, FR1**
+
+| UID                                                                    | Uncertainty source                                                                    | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|---------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                       | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                       |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| B2-1a                                                                  | Misalignment and pointing error of BS                                                 | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B2-2                                                                   | Standing wave between BS and test range antenna                                       | 0.21                   | 0.21            | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| C1-2                                                                   | Uncertainty of the RF signal generator                                                | 0.46                   | 0.46            | 0.46            | Gaussian                        | 1.00                                | 1              | 0.46                                     | 0.46            | 0.46            |
+| B2-3                                                                   | RF leakage & dynamic range, test range antenna cable connector terminated.            | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B2-4a                                                                  | QZ ripple experienced by BS                                                           | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| B2-9                                                                   | Miscellaneous uncertainty                                                             | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                       |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                   | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| B2-5                                                                   | Mismatch of transmit chain (i.e. between transmitting measurement antenna and BS)     | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| B2-6                                                                   | Insertion loss of transmitter chain                                                   | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| B2-7                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B2-8                                                                   | Influence of the calibration antenna feed cable                                       | 0.02                   | 0.02            | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                             | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| B2-9                                                                   | Miscellaneous uncertainty                                                             | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B2-4b                                                                  | QZ ripple experienced by calibration antenna                                          | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| B2-10                                                                  | Rotary joints                                                                         | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| B2-1b                                                                  | Misalignment and pointing error of calibration antenna                                | 0.50                   | 0.50            | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| B2-11                                                                  | Misalignment positioning system                                                       | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B2-12                                                                  | Standing wave between SGH and test range antenna                                      | 0.09                   | 0.09            | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| B2-13                                                                  | Switching uncertainty                                                                 | 0.26                   | 0.26            | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                       |                        |                 |                 |                                 |                                     |                | <b>0.68</b>                              | <b>0.71</b>     | <b>0.71</b>     |
+| <b>Expanded uncertainty (1.96σ – confidence interval of 95 %) (dB)</b> |                                                                                       |                        |                 |                 |                                 |                                     |                | <b>1.33</b>                              | <b>1.40</b>     | <b>1.40</b>     |
+
+### 10.2.3.4 MU value derivation, FR2
+
+Table 10.2.3.4-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in CATR (Normal test conditions, FR2).
+
+**Table 10.2.3.4-1: CATR MU value derivation for OTA sensitivity measurement, FR2**
+
+| UID                                                                                      | Uncertainty source                                                                    | Uncertainty value    |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                                          |                                                                                       | 24.25 < f < 29.5 GHz | 37 < f < 43.5 GHz |                                 |                                     |                | 24.25 < f < 29.5 GHz                     | 37 < f < 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                       |                      |                   |                                 |                                     |                |                                          |                   |
+| B2-1a                                                                                    | Misalignment and pointing error of BS                                                 | 0.2                  | 0.2               | Exp. normal                     | 2.00                                | 1              | 0.10                                     | 0.10              |
+| B2-2                                                                                     | Standing wave between BS and test range antenna                                       | 0.21                 | 0.21              | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15              |
+| C1-2                                                                                     | Uncertainty of the RF signal generator                                                | 0.9                  | 0.9               | Gaussian                        | 1.00                                | 1              | 0.90                                     | 0.90              |
+| B2-3                                                                                     | RF leakage & dynamic range, test range antenna cable connector terminated.            | 0.01                 | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| B2-4a                                                                                    | QZ ripple experienced by BS                                                           | 0.4                  | 0.4               | Gaussian                        | 1.00                                | 1              | 0.40                                     | 0.40              |
+| B2-9                                                                                     | Miscellaneous uncertainty                                                             | 0                    | 0                 | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00              |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                       |                      |                   |                                 |                                     |                |                                          |                   |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                   | 0.3                  | 0.3               | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| B2-5                                                                                     | Mismatch of transmit chain (i.e. between transmitting measurement antenna and BS)     | 0.43                 | 0.57              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.40              |
+| B2-6                                                                                     | Insertion loss of transmitter chain                                                   | 0.12                 | 0.12              | Rectangular                     | 1.73                                | 1              | 0.07                                     | 0.07              |
+| B2-7                                                                                     | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.01                 | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| B2-8                                                                                     | Influence of the calibration antenna feed cable                                       | 0.21                 | 0.29              | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.21              |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                             | 0.52                 | 0.52              | Rectangular                     | 1.73                                | 1              | 0.30                                     | 0.30              |
+| B2-11                                                                                    | Misalignment positioning system                                                       | 0                    | 0                 | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| B2-4b                                                                                    | QZ ripple experienced by calibration antenna                                          | 0.1                  | 0.1               | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10              |
+| B2-10                                                                                    | Rotary joints                                                                         | 0                    | 0                 | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.00              |
+| B2-1b                                                                                    | Misalignment and pointing error of calibration antenna                                | 0                    | 0                 | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| B2-12                                                                                    | Standing wave between SGH and test range antenna                                      | 0.09                 | 0.09              | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06              |
+| B2-13                                                                                    | Switching uncertainty                                                                 | 0.1                  | 0.1               | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06              |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                                                       |                      |                   |                                 |                                     |                | <b>1.15</b>                              | <b>1.19</b>       |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> – confidence interval of 95 %) (dB)</b> |                                                                                       |                      |                   |                                 |                                     |                | <b>2.25</b>                              | <b>2.33</b>       |
+
+## 10.2.4 One Dimensional Compact Range
+
+### 10.2.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.4.1.
+
+### 10.2.4.2 Test procedure
+
+#### 10.2.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the One Dimensional Compact Range is captured in clause 8.4.
+
+#### 10.2.4.2.2 Stage 2: BS measurement
+
+The 1D CATR testing procedure consists of the following steps:
+
+- 1) Connect the feed system of the compact probe to the signal generator.
+
+- 2) Calibrate the test range, using a reference antenna with standard gain installed in the quiet zone of the probe and measure the path loss between signal generator and reference antenna.
+- 3) Position the BS in the quiet zone of the probe with its manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with testing system.
+- 4) Connect the BS to the measurement equipment.
+- 5) Align with the conformance test direction.
+- 6) Set the signal generator to the manufacturer declared sensitivity (EIS) level plus the measured path loss.
+- 7) Measure the throughput and BER of the BS.
+- 8) Repeat test steps 2 - 7 for all declared beams and corresponding conformance steering directions.
+
+#### 10.2.4.3 MU value derivation, FR1
+
+Table 10.2.4.3-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in One Dimensional Compact Range.
+
+**Table 10.2.4.3-1: One Dimensional Compact Range measurement uncertainty value derivation for OTA sensitivity measurements, FR1**
+
+| UID                                     | Uncertainty source                                                                                         | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                                                                            | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                                            |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| B4-1                                    | Misalignment BS and pointing error                                                                         | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B4-2a                                   | Standing wave between BS and test range antenna                                                            | 0.18                   | 0.18            | 0.18            | U-shaped                        | 1.41                                | 1              | 0.13                                     | 0.13            | 0.13            |
+| B4-3a                                   | Quiet zone ripple experienced by BS                                                                        | 0.03                   | 0.03            | 0.03            | Gaussian                        | 1.00                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-2                                    | Uncertainty of the RF signal generator                                                                     | 0.46                   | 0.46            | 0.46            | Gaussian                        | 1.00                                | 1              | 0.46                                     | 0.46            | 0.46            |
+| B4-4                                    | Phase curvature                                                                                            | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| B4-5a                                   | Polarization mismatch between BS and transmitting antenna                                                  | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| B4-6a                                   | Mutual coupling between BS and transmitting antenna                                                        | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                    | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| B4-7                                    | Impedance mismatch in transmitter chain                                                                    | 0.01                   | 0.01            | 0.01            | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.01            | 0.01            |
+| B4-8                                    | RF leakage and dynamic range                                                                               | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                                            |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| B4-9                                    | Misalignment positioning system                                                                            | 0.00                   | 0.00            | 0.00            | Exp. Normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B4-10                                   | Pointing error between reference antenna and test range antenna                                            | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B4-11                                   | Impedance mismatch in path to reference antenna                                                            | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| B4-12                                   | Impedance mismatch in path to compact probe                                                                | 0.03                   | 0.03            | 0.03            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| B4-2b                                   | Standing wave between reference antenna and test range antenna                                             | 0.15                   | 0.15            | 0.15            | U-shaped                        | 1.41                                | 1              | 0.11                                     | 0.11            | 0.11            |
+| B4-3b                                   | Quiet zone ripple experienced by reference antenna                                                         | 0.18                   | 0.18            | 0.18            | Gaussian                        | 1.00                                | 1              | 0.18                                     | 0.18            | 0.18            |
+| B4-4                                    | Phase curvature                                                                                            | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| B4-5b                                   | Polarization mismatch between reference antenna and transmitting antenna                                   | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| B4-6b                                   | Mutual coupling between reference antenna and transmitting antenna                                         | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                    | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| B4-13                                   | Influence of reference antenna feed cable (flexing cables, adapters, attenuators, connector repeatability) | 0.08                   | 0.08            | 0.08            | Rectangular                     | 1.73                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| B4-14                                   | Mismatch of transmitter chain                                                                              | 0.20                   | 0.30            | 0.30            | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.21            | 0.21            |
+| B4-15                                   | Insertion loss of transmitter chain                                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+
+|                                                                                          |                                                                                         |      |      |      |             |      |   |             |             |             |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------|------|------|-------------|------|---|-------------|-------------|-------------|
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                               | 0.50 | 0.43 | 0.43 | Rectangular | 1.73 | 1 | 0.29        | 0.25        | 0.25        |
+| B4-16                                                                                    | RF leakage (SGH connector terminated and test range antenna connector cable terminated) | 0.00 | 0.00 | 0.00 | Gaussian    | 1.00 | 1 | 0.00        | 0.00        | 0.00        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                         |      |      |      |             |      |   | <b>0.66</b> | <b>0.73</b> | <b>0.73</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> – confidence interval of 95 %) (dB)</b> |                                                                                         |      |      |      |             |      |   | <b>1.29</b> | <b>1.43</b> | <b>1.43</b> |
+
+## 10.2.5 Near Field Test range
+
+### 10.2.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.
+
+### 10.2.5.2 Test procedure
+
+#### 10.2.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 10.2.5.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists in the following steps:
+
+- 1) BS near field *radiation pattern* measurement: this is performed when the BS will be receiving a defined modulated signal, as defined in applicable conformance test specification.
+
+NOTE: if the Near Field pattern is derived, for example by transmitting through the *antenna array*, then uncertainty contributors need to be considered in the measurement uncertainty budget (including differences in matching losses between transmit and receive chains).
+
+- 2) BS near field OTA sensitivity measurement: this is performed by measuring the sensitivity in near field when a modulated signal is received by the BS under test,
+- 3) BS near field to far field EIS transformation: sensitivity measurement is applied.
+
+The near field to far field transformation is a mathematical computation which is applied to the near field measured *radiation pattern* in order to compute the far field *radiation pattern*. It is typically performed expanding the measured near field over a set of orthogonal basis functions. The near to far field transform is then performed in two steps:
+
+- 3.1) Expansion (or projection) of the measured near field (i.e.  $E_{meas}$ ) over a set of orthogonal basis functions (i.e.  $F_{bal}(r)$ ) in order to evaluate the transformed spectrum:
+
+$$I_{eas}(r) = Spectrum * F_{basis}(r)$$
+
+- 3.2) FF (i.e.  $E_{FF}$ ) computation using the previously calculated spectrum and with the basis functions evaluated at  $r \rightarrow \infty$  (i.e.  $F_{basis}(r \rightarrow \infty)$ ):
+
+$$E_{FF} = Spectrum * F_{basis}(r \rightarrow \infty)$$
+
+When performing the near field to far field transformation, the sensitivity measurement is applied so that the near field pattern will be transformed from relative power (i.e. dB) to absolute power (i.e. dBm). In this specific case, the EIS far field pattern is expressed in terms of the absolute power received by the BS.
+
+- 4) BS OTA sensitivity: once the full 3D far field EIS pattern has been computed in step 3 from measurements in step 2, the OTA sensitivity can be derived.
+
+### 10.2.5.3 MU value derivation, FR1
+
+Table 10.2.5.3-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in Near Field Test Range.
+
+Standard uncertainty values for the signal generator, network analyzer and reference antenna are according to the test equipment uncertainty values, as captured in annex C.
+
+**Table 10.2.5.3-1: NFTR measurement uncertainty value derivation for OTA sensitivity measurements, FR1**
+
+| UID                                     | Uncertainty source                                    | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|-------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                       | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                       |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| B3-1                                    | Axes intersection                                     | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-2                                    | Axes orthogonality                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-3                                    | Horizontal pointing                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-4                                    | Probe vertical position                               | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-5                                    | Probe horizontal/vertical pointing                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-6                                    | Measurement distance                                  | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-7                                    | Amplitude and phase drift                             | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-8                                    | Amplitude and phase noise                             | 0.02                   | 0.02            | 0.02            | Gaussian                        | 1.00                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| B3-9                                    | Leakage and crosstalk                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-10                                   | Amplitude non-linearity                               | 0.04                   | 0.04            | 0.04            | Gaussian                        | 1.00                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| B3-11                                   | Amplitude and phase shift in rotary joints            | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-12                                   | Channel balance amplitude and phase                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-13                                   | Probe polarization amplitude and phase                | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-14                                   | Probe pattern knowledge                               | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-15                                   | Multiple reflections                                  | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-16                                   | Room scattering                                       | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| B3-17                                   | BS support scattering                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-18                                   | Scan area truncation                                  | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-19                                   | Sampling point offset                                 | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| B3-20                                   | Mode truncation                                       | 0.02                   | 0.02            | 0.02            | Gaussian                        | 1.00                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| B3-21                                   | Positioning                                           | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| B3-22                                   | Probe array uniformity                                | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| B3-23                                   | Mismatch of transmitter chain                         | 0.28                   | 0.28            | 0.28            | U-Shaped                        | 1.41                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| B3-24                                   | Insertion loss of transmitter chain                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B3-25                                   | Uncertainty of the absolute gain of the probe antenna | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| C1-2                                    | Uncertainty of the RF signal generator                | 0.46                   | 0.46            | 0.46            | Gaussian                        | 1.00                                | 1              | 0.46                                     | 0.46            | 0.46            |
+| B3-26                                   | Measurement repeatability - positioning repeatability | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Stage 1: Calibration measurement</b> |                                                       |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+
+|                                                                                          |                                                           |      |      |      |             |      |   |             |             |             |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------|------|------|------|-------------|------|---|-------------|-------------|-------------|
+| C1-3                                                                                     | Uncertainty of the network analyzer                       | 0.13 | 0.20 | 0.20 | Gaussian    | 1.00 | 1 | 0.13        | 0.20        | 0.20        |
+| B3-27                                                                                    | Mismatch of transmitter chain                             | 0.00 | 0.00 | 0.00 | Gaussian    | 1.00 | 1 | 0.00        | 0.00        | 0.00        |
+| B3-28                                                                                    | Insertion loss of transmitter chain                       | 0.00 | 0.00 | 0.00 | Gaussian    | 1.00 | 1 | 0.00        | 0.00        | 0.00        |
+| B3-29                                                                                    | Mismatch in the connection of the calibration antenna     | 0.02 | 0.02 | 0.02 | U-Shaped    | 1.41 | 1 | 0.01        | 0.01        | 0.01        |
+| B3-30                                                                                    | Influence of the calibration antenna feed cable           | 0.00 | 0.00 | 0.00 | Gaussian    | 1.00 | 1 | 0.00        | 0.00        | 0.00        |
+| B3-31                                                                                    | Influence of the probe antenna cable                      | 0.00 | 0.00 | 0.00 | Gaussian    | 1.00 | 1 | 0.00        | 0.00        | 0.00        |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna | 0.50 | 0.43 | 0.43 | Rectangular | 1.73 | 1 | 0.29        | 0.25        | 0.25        |
+| B3-32                                                                                    | Short term repeatability                                  | 0.09 | 0.09 | 0.09 | Gaussian    | 1.00 | 1 | 0.09        | 0.09        | 0.09        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                           |      |      |      |             |      |   | <b>0.63</b> | <b>0.63</b> | <b>0.63</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> – confidence interval of 95 %) (dB)</b> |                                                           |      |      |      |             |      |   | <b>1.24</b> | <b>1.24</b> | <b>1.24</b> |
+
+## 10.2.6 Plane Wave Synthesizer
+
+### 10.2.6.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 10.2.6.2 Test procedure
+
+#### 10.2.6.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+#### 10.2.6.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install BS as BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-2. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Configure signal generator, one port and one carrier at a time according to maximum power requirement.
+- 3) Calculate EIS at this point with  $EIS = PBER - L_{C \rightarrow A}$ .
+- 4) Repeat steps 2 - 3 for all conformance test *beam direction pairs* and test conditions.
+
+### 10.2.6.3 MU value derivation, FR1
+
+Table 10.2.6.3-1 captures derivation of the expanded measurement uncertainty values for OTA sensitivity measurements in PWS.
+
+**Table 10.2.6.3-1: Plane wave synthesizer MU value derivation for OTA sensitivity measurements, FR1**
+
+| UID                                                                    | Uncertainty source                                                                                           | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                                              | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| B5-1a                                                                  | Misalignment and pointing error of BS                                                                        | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-2                                                                   | Uncertainty of the RF signal generator                                                                       | 0.46                   | 0.46            | 0.46            | Gaussian                        | 1.00                                | 1              | 0.46                                     | 0.46            | 0.46            |
+| B5-2a                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna          | 0.05                   | 0.14            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08            | 0.12            |
+| B5-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| B5-4a                                                                  | QZ ripple experienced by BS                                                                                  | 0.42                   | 0.43            | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25            | 0.33            |
+| B5-5                                                                   | Miscellaneous uncertainty                                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B5-14                                                                  | System non-linearity                                                                                         | 0.10                   | 0.10            | 0.15            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.09            |
+| B5-13                                                                  | Frequency flatness of test system                                                                            | 0.13                   | 0.13            | 0.13            | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08            | 0.08            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                          | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| B5-6                                                                   | Mismatch (i.e. reference antenna, network analyser and reference cable)                                      | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| B5-7                                                                   | Insertion loss of transmit chain                                                                             | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| B5-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| B5-8                                                                   | Influence of the calibration antenna feed cable                                                              | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                    | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| B5-9                                                                   | Misalignment of positioning system                                                                           | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B5-1b                                                                  | Misalignment and pointing error of calibration antenna                                                       | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| B5-10                                                                  | Rotary joints                                                                                                | 0.00                   | 0.00            | 0.00            | U-shaped                        | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| B5-2b                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna | 0.12                   | 0.12            | 0.15            | Rectangular                     | 1.73                                | 1              | 0.07                                     | 0.07            | 0.09            |
+| B5-4b                                                                  | QZ ripple experienced by calibration antenna                                                                 | 0.20                   | 0.20            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.12                                     | 0.12            | 0.12            |
+| B5-11                                                                  | Switching uncertainty                                                                                        | 0.02                   | 0.02            | 0.02            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| B5-12                                                                  | Field repeatability                                                                                          | 0.06                   | 0.12            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.12            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>0.67</b>                              | <b>0.71</b>     | <b>0.76</b>     |
+| <b>Expanded uncertainty (1.96σ – confidence interval of 95 %) (dB)</b> |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>1.31</b>                              | <b>1.40</b>     | <b>1.48</b>     |
+
+## 10.2.7 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for OTA sensitivity test can be derived from values captured in tables 10.2.7-1 and 10.2.7-2, derived based on the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA sensitivity test requirement.
+
+**Table 10.2.7-1: OTA test system specific measurement uncertainty values for the OTA sensitivity in Normal test conditions, FR1**
+
+|                                                        | Expanded uncertainty (dB) |                              |                              |
+|--------------------------------------------------------|---------------------------|------------------------------|------------------------------|
+|                                                        | $f \leq 3 \text{ GHz}$    | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+| Indoor Anechoic Chamber                                | 1.22                      | 1.25                         | 1.25                         |
+| Compact Antenna Test Range                             | 1.33                      | 1.40                         | 1.40                         |
+| Near Field Test Range                                  | 1.24                      | 1.24                         | 1.24                         |
+| One Dimensional Compact Range Chamber                  | 1.29                      | 1.43                         | 1.43                         |
+| Plane Wave Synthesizer                                 | 1.31                      | 1.40                         | 1.48                         |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.3</b>                | <b>1.4</b>                   | <b>1.6</b>                   |
+
+**Table 10.2.7-2: OTA test system specific measurement uncertainty values for the OTA sensitivity in Normal test conditions, FR2**
+
+|                                                        | Expanded uncertainty (dB)                     |                                            |                                              |
+|--------------------------------------------------------|-----------------------------------------------|--------------------------------------------|----------------------------------------------|
+|                                                        | $24.25 \text{ GHz} < f \leq 29.5 \text{ GHz}$ | $37 \text{ GHz} < f \leq 43.5 \text{ GHz}$ | $43.5 \text{ GHz} < f \leq 48.2 \text{ GHz}$ |
+| Indoor Anechoic Chamber                                | 2.33                                          | 2.46                                       |                                              |
+| Compact Antenna Test Range                             | 2.25                                          | 2.33                                       |                                              |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.4</b>                                    | <b>2.4</b>                                 | <b>3.5</b>                                   |
+
+From FR2 MU inputs in clauses 10.2.2.4 and 10.2.3.4, it has been agreed that  $MU_{\text{EIS}}$  is 2.4 dB for up to 43.5 GHz.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 10.2.8 Test Tolerance for OTA sensitivity
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA sensitivity were derived based on values captured in clause 10.2.7.
+
+It has been agreed that the TT for the regulatory receiver directional requirements should be zero, while the TT for other receiver directional requirements should be equal to the MU.
+
+Frequency range specific Test Tolerance values for the OTA sensitivity test are defined in table 10.2.8-1 and 10.2.8-2.
+
+**Table 10.2.8-1: Test Tolerance values for the OTA sensitivity, Normal test conditions**
+
+|                     | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|------------------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (dB) | 1.3                    | 1.4                                      | 1.6                                      |
+
+**Table 10.2.8-2: Test Tolerance values for the OTA sensitivity, Normal test conditions**
+
+|                     | $24.25 \text{ GHz} < f \leq 29.5 \text{ GHz}$ | $37 \text{ GHz} < f \leq 43.5 \text{ GHz}$ | $43.5 \text{ GHz} < f \leq 48.2 \text{ GHz}$ |
+|---------------------|-----------------------------------------------|--------------------------------------------|----------------------------------------------|
+| Test Tolerance (dB) | 2.4                                           | 2.4                                        | 3.5                                          |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 10.3 OTA reference sensitivity
+
+The OTA REFSENS requirement is intended to ensure the OTA reference sensitivity level for a declared *OTA REFSENS RoAoA*.
+
+The OTA reference sensitivity power level  $EIS_{REFSENS}$  is the mean power received at the radiated interface at which a reference performance requirement shall be met for a specified reference measurement channel.
+
+The measurement methods, along with the corresponding calibration, procedure and MU assessment, are the same as those for the OTA sensitivity requirement in clause 10.2, except that the required level is  $EIS_{REFSENS}$  in the measurement procedure.
+
+## 10.4 OTA dynamic range
+
+### 10.4.1 General
+
+Clause 10.4 captures MU and TT values derivation for the OTA dynamic range directional requirement.
+
+The OTA dynamic range is a measure of the capability of the receiver unit to receive a wanted signal in the presence of an interfering signal inside the received *channel bandwidth* or the capability of receiving high level of wanted signal.
+
+The requirement applies at the RIB when the AoA of the incident wave of a received signal and the interfering signal are from the same direction and are within the *OTA REFSENS RoAoA*.
+
+The wanted and interfering signals apply to all supported polarizations, under the assumption of *polarization match*.
+
+### 10.4.2 Indoor Anechoic Chamber
+
+#### 10.4.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1.
+
+#### 10.4.2.2 Test procedure
+
+##### 10.4.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber shall be done with the procedure shown in clause 8.2, with the wanted and AWGN interfering signals with power combiner/coupler:
+
+$L_{Wanted\_cal, A \rightarrow D}$ : Calibration value for wanted signal between A and D in figure 7.2.1-3.
+
+$L_{AWGN\_cal, A \rightarrow E}$ : Calibration value for AWGN signal between A and E in figure 7.2.1-3.
+
+##### 10.4.2.2.2 Stage 2: BS measurement
+
+The IAC measurement procedure is the same as those for the OTA sensitivity requirement in clause 10.2.2.2.2, except that step 5 is modified as follow:
+
+- 5) Set the test signal mean power at the RF signal source generator for wanted signal as the required level plus  $L_{Wanted\_cal, A \rightarrow D}$  and the reference measurement channel. Set the test signal mean power at the RF signal source generator for AWGN interfering signal as the required level plus  $L_{AWGN\_cal, A \rightarrow E}$  and at the same frequency as wanted signal.
+
+### 10.4.2.3 MU value derivation, FR1
+
+The MU for OTA dynamic range requirement is not impacted by OTA chamber related uncertainties, so the MU is the same as for the conducted dynamic range requirement. This is further discussed and concluded in clause 10.4.4.
+
+## 10.4.3 Compact Antenna Test Range
+
+### 10.4.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1 and the measurement system setup for OTA dynamic range depicted on figure 7.3.1-3.
+
+### 10.4.3.2 Test procedure
+
+#### 10.4.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the CATR shall be done with the procedure shown in clause 8.3, for the wanted and AWGN interfering signals with power combiner/coupler:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{B}}$ : Calibration value for wanted signal between A and B in figure 7.3.1-3.
+
+$L_{\text{AWGN\_cal, A}\rightarrow\text{E}}$ : Calibration value for AWGN interfering signal between A and E in figure 7.3.1-3.
+
+#### 10.4.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with boresight of transmitting antenna.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{B}}$  and at reference measurement channel.
+- 3) Configure RF signal generator for AWGN interferer to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{E}}$  and at the same frequency as wanted signal.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat steps 2 - 4 for all conformance test bands and directions.
+
+### 10.4.3.3 MU value derivation, FR1
+
+The MU for OTA dynamic range requirement is not impacted by OTA chamber related uncertainties, so the MU is the same as for the conducted dynamic range requirement. This is further discussed and concluded in clause 10.4.4.
+
+## 10.4.3A Plane Wave Synthesizer
+
+Measurement system description is captured in clause 7.6.1 and the measurement system setup for OTA dynamic range depicted on figure 7.6.1-3.
+
+### 10.4.3A.2 Test procedure
+
+#### 10.4.3A.2.1 Stage 1: Calibration
+
+Calibration procedure for the PWS shall be done with the procedure shown in clause 8.6, for the wanted and AWGN interfering signals with power combiner/coupler:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{C}}$ : Calibration value for wanted signal between A and C in figure 7.6.1-3.
+
+$L_{\text{AWGN\_cal, A}\rightarrow\text{D}}$ : Calibration value for AWGN interfering signal between A and D in figure 7.6.1-3.
+
+### 10.4.3A.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-3. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{A \rightarrow C}$  and at reference measurement channel.
+- 3) Configure RF signal generator for AWGN interferer to set the signal at the required level plus  $L_{A \rightarrow D}$  and at the same frequency as wanted signal.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat steps 2 - 4 for all conformance test bands and directions.
+
+### 10.4.3A.3 MU value derivation, FR1
+
+The MU for OTA dynamic range requirement is not impacted by OTA chamber related uncertainties, so the MU is the same as for the conducted dynamic range requirement. This is further discussed and concluded in clause 10.4.4.
+
+## 10.4.4 Maximum accepted test system uncertainty
+
+The OTA dynamic range requirement provides both a wanted signal and an in-channel AWGN interferer to the BS input. Both the wanted signal and interferer power levels are well above the receiver noise floor, to the extent that the SNR in the receiver is dependent only on the transmitter signal to AWGN level and is independent of the receiver noise level.
+
+Small variations of the receiver power level due to uncertainty factors in the OTA environment will impact both the wanted signal and AWGN equally, and hence do not impact the SNR experienced by the receiver or change the measurement result. Thus, the receiver dynamic range requirement is not impacted by OTA chamber related uncertainties.
+
+In TS 36.141 [3], the MU for the conducted RX dynamic range is taken as the uncertainty in achieving the correct SNR at the test equipment transmitter. Considering the above argumentation that OTA chamber aspects will not impact MU for receiver dynamic range, the same MU of 0.3 dB as for the conducted case can be assumed.
+
+## 10.4.5 Test Tolerance for OTA dynamic range
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA dynamic range were derived based on values in clause 10.4.4.
+
+It has been agreed that the TT for the regulatory receiver directional requirements should be zero, while the TT for other receiver directional requirements should be equal to the MU.
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 10.5 OTA adjacent channel selectivity, general blocking and narrowband blocking
+
+### 10.5.1 General
+
+Clause 10.5 captures MU and TT values derivation for the OTA adjacent channel selectivity (ACS), general blocking and narrowband blocking directional requirements.
+
+## 10.5.2 Indoor Anechoic Chamber
+
+### 10.5.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup for ACS, general blocking and narrowband blocking depicted on figure 7.2.1-4.
+
+### 10.5.2.2 Test procedure
+
+#### 10.5.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber shall be done with the procedure shown in clause 8.2, for the frequencies of wanted and unwanted signals with power combiner/coupler. Calculate the calibration value for wanted and unwanted signal from A to D as well as from A to E:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{D}}$ : Calibration value for wanted signal between A and D in figure 7.2.1-4.
+
+$L_{\text{Unwanted\_cal, A}\rightarrow\text{E}}$ : Calibration value for unwanted signal between A and E in figure 7.2.1-4.
+
+#### 10.5.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with its manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with testing system.
+- 2) Set the BS to be satisfied with the *RoAoA* desired by the requirement covering conformance testing receiving direction.
+- 3) Rotate the BS to make the conformance testing receiving direction aligned with the boresight of the reference antenna at the calibration stage.
+- 4) For FDD BS start transmission at the required condition.
+- 5) Set the test signal mean power at the RF signal source generator for wanted signal as the required level plus  $L_{\text{Wanted\_cal, A}\rightarrow\text{D}}$  and the reference measurement channel.
+- 6) Set the test signal mean power at the RF signal source generator for unwanted signal as the required level plus  $L_{\text{Unwanted\_cal, A}\rightarrow\text{E}}$  and the interference signal channel.
+- 7) Measure the throughput.
+- 8) Repeat the above steps 1 - 6 per conformance testing direction.
+
+### 10.5.2.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+Where
+
+The uncertainty budget behind the EIS MU is captured in clause 10.2. The 2 sigma matching uncertainty is 0.196 dB for  $f \leq 3$  GHz and 0.314 dB for  $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ .
+
+The ACLR effect from the interference signal is assumed to be 0.4 dB, as in TS 36.141 [3]. This is under the assumption that no additional PA is needed for the test signal in the OTA test setup.
+
+The MU for ACS is calculated as follows. Note that all uncertainties in the table are  $1.96\sigma$  values.
+
+**Table 10.5.2.3-1: IAC MU value derivation for OTA ACS, general blocking and narrowband blocking measurement, FR1**
+
+|             | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | Calculation details |
+|-------------|----------------|----------------------------|---------------------|
+|             | $\pm 0.7$ dB   | $\pm 1$ dB                 |                     |
+|             | $\pm 0.7$ dB   | $\pm 1$ dB                 |                     |
+|             | $\pm 0.196$ dB | $\pm 0.314$ dB             |                     |
+|             | $\pm 0.672$ dB | $\pm 0.949$ dB             |                     |
+|             | $\pm 0.672$ dB | $\pm 0.949$ dB             |                     |
+|             | 1.22 dB        | 1.25 dB                    |                     |
+|             | 0.9 dB         | 0.9 dB                     |                     |
+|             | $\pm 0.196$ dB | $\pm 0.314$ dB             |                     |
+|             | $\pm 0.8$ dB   | $\pm 0.804$ dB             |                     |
+| ACLR effect | 0.4 dB         |                            |                     |
+|             | 1.7 dB         | 2.00 dB                    |                     |
+
+## 10.5.3 Compact Antenna Test Range
+
+### 10.5.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the CATR measurement system setup for ACS, general blocking and narrowband blocking depicted on figure 7.3.1-3.
+
+### 10.5.3.2 Test procedure
+
+#### 10.5.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range shall be done with the procedure shown in clause 8.3, for the frequencies of wanted and interfering signals with power combiner/coupler. Calculate the calibration value for wanted and interfering signal from A to B as well as from A to E:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{B}}$ : Calibration value for wanted signal between A and B in figure 7.3.1-3.
+
+$L_{\text{interferer\_cal, A}\rightarrow\text{E}}$ : Calibration value for interfering signal between A and E in figure 7.3.1-3.
+
+#### 10.5.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with boresight of transmitting antenna.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{B}}$  and at reference measurement channel.
+
+- 3) Configure RF signal generator for interferer to set the signal at the required level plus  $L_{A \rightarrow E}$  and at reference measurement channel. The interferer's centre frequency offset should be swept as required.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat steps 2 - 4 for all conformance test directions.
+- 6) Repeat steps above per involved band for multi-band RIB(s).
+
+### 10.5.3.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+The 2 sigma matching uncertainty is 0.294 dB up to 4.2 GHz.
+
+Test system uncertainty is obtained by following equations:
+
+Where
+
+And we assume
+
+Test system uncertainty for ACS, narrow band blocking, and general band blocking is shown in table 10.5.3.3-1. Note that all uncertainties in table are  $1.96\sigma$  values.
+
+**Table 10.5.3.3-1: CATR MU value derivation for OTA ACS, general blocking and narrowband blocking measurement, FR1**
+
+|             | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | Calculation details |
+|-------------|------------------------|------------------------------------------|---------------------|
+|             | $\pm 0.7 \text{ dB}$   | $\pm 1 \text{ dB}$                       |                     |
+|             | $\pm 0.7 \text{ dB}$   | $\pm 1 \text{ dB}$                       |                     |
+|             | $\pm 0.294 \text{ dB}$ | $\pm 0.294 \text{ dB}$                   |                     |
+|             | $\pm 0.635 \text{ dB}$ | $\pm 0.956 \text{ dB}$                   |                     |
+|             | $\pm 0.635 \text{ dB}$ | $\pm 0.956 \text{ dB}$                   |                     |
+|             | 1.33 dB                | 1.40 dB                                  |                     |
+|             | 0.9 dB                 | 0.9 dB                                   |                     |
+|             | $\pm 0.294 \text{ dB}$ | $\pm 0.294 \text{ dB}$                   |                     |
+|             | $\pm 0.933 \text{ dB}$ | $\pm 1.03 \text{ dB}$                    |                     |
+| ACLR effect | 0.4 dB                 |                                          |                     |
+|             | 1.7 dB                 | 2.1 dB                                   |                     |
+
+## 10.5.3A Plane Wave Synthesizer
+
+### 10.5.3A.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1, with the PWS measurement system setup for ACS, general blocking and narrowband blocking depicted on figure 7.6.1-3.
+
+## 10.5.3A.2 Test procedure
+
+### 10.5.3.2A.1 Stage 1: Calibration
+
+Calibration procedure for the PWS shall be done with the procedure shown in clause 8.6, for the frequencies of wanted and interfering signals with power combiner/coupler. Calculate the calibration value for wanted and interfering signal from A to C as well as from A to D:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{C}}$ : Calibration value for wanted signal between A and C in figure 7.6.1-3.
+
+$L_{\text{interferer\_cal, A}\rightarrow\text{D}}$ : Calibration value for interfering signal between A and D in figure 7.6.1-3.
+
+### 10.5.3A.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-3. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{C}}$  and at reference measurement channel.
+- 3) Configure RF signal generator for interferer to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{D}}$  and at reference measurement channel. The interferer's centre frequency offset should be swept as required.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat steps 2 - 4 for all conformance test directions.
+- 6) Repeat steps above per involved band for multi-band RIB(s).
+
+## 10.5.3A.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+The 2 sigma matching uncertainty is 0.3 dB up to 4.2 GHz.
+
+Test system uncertainty is obtained by following equations:
+
+Where
+
+And we assume
+
+Test system uncertainty for ACS, narrow band blocking, and general band blocking is shown in table 10.5.3A.3-1. Note that all uncertainties in table are  $1.96\sigma$  values.
+
+**Table 10.5.3A.3-1: PWS MU value derivation for OTA ACS, general blocking and narrowband blocking measurement, FR1**
+
+|             | <b>f ≤ 3 GHz</b> | <b>3 GHz &lt; f ≤ 4.2 GHz</b> | <b>Calculation details</b> |
+|-------------|------------------|-------------------------------|----------------------------|
+|             | ±0.7 dB          | ±1 dB                         |                            |
+|             | ±0.7 dB          | ±1 dB                         |                            |
+|             | ±0.3 dB          | ±0.3 dB                       |                            |
+|             | ±0.632 dB        | ±0.954 dB                     |                            |
+|             | ±0.632 dB        | ±0.954 dB                     |                            |
+|             | 1.31 dB          | 1.40 dB                       |                            |
+|             | 0.9 dB           | 0.9 dB                        |                            |
+|             | ±0.3 dB          | ±0.3 dB                       |                            |
+|             | ±0.902 dB        | ±1.03 dB                      |                            |
+| ACLR effect | 0.4 dB           |                               |                            |
+|             | 1.7 dB           | 2.1 dB                        |                            |
+
+## 10.5.4 Maximum accepted test system uncertainty
+
+MU can be calculated as follows:
+
+$$MU_{ACS,IBB,ICS} = \sqrt{MU_{EIS}^2 + MU_{TestEquipment}^2 + MU_{PA}^2 + ACLR_{effect}^2}$$
+
+With
+
+$$MU_{TestEquipment} (1.96\sigma) = 1.96 \times 0.9$$
+
+$$MU_{PA} (1.96\sigma) = 1.96 \times 0.2$$
+
+And
+
+$$ACLR_{effect} (1.96\sigma) = 0.4$$
+
+The MU for 4.2 GHz < f ≤ 6 GHz for each receiver directional requirement can be calculated as shown in tables 10.5.4-1 to 10.5.4-3 below.
+
+**Table 10.5.4-1: MU for adjacent channel selectivity, narrowband blocking, in-channel selectivity**
+
+| <b>Test System Uncertainty</b>                                        | <b>Standard uncertainty u<sub>i</sub> (dB)</b> |                               |                               |                               |
+|-----------------------------------------------------------------------|------------------------------------------------|-------------------------------|-------------------------------|-------------------------------|
+|                                                                       | <b>IAC</b>                                     |                               | <b>CATR</b>                   |                               |
+|                                                                       | <b>3 GHz &lt; f ≤ 4.2 GHz</b>                  | <b>4.2 GHz &lt; f ≤ 6 GHz</b> | <b>3 GHz &lt; f ≤ 4.2 GHz</b> | <b>4.2 GHz &lt; f ≤ 6 GHz</b> |
+| MU <sub>conductedwanted</sub> (Wanted signal level error)             | 1                                              | 1.30                          | 1                             | 1.30                          |
+| MU <sub>conductedint</sub> (Interferer signal level error)            | 1                                              | 1.30                          | 1                             | 1.30                          |
+| MU <sub>EIS</sub> (Combined standard uncertainty)                     | 0.64                                           | 0.77                          | 0.71                          | 0.83                          |
+| MU <sub>TestEquipment</sub> (Uncertainty of the RF signal generator)  | 0.46                                           | 0.58                          | 0.46                          | 0.58                          |
+| MU <sub>matching</sub> (Impedance mismatch in the transmitting chain) | 0.16                                           | 0.28                          | 0.15                          | 0.28                          |
+| ACLR <sub>effect</sub> (Impact of interferer leakage)                 | 0.4                                            | 0.4                           | 0.4                           | 0.4                           |
+| <b>Combined standard uncertainty (1σ)</b>                             | <b>1.02</b>                                    | <b>1.19</b>                   | <b>1.08</b>                   | <b>1.24</b>                   |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %)</b>     | <b>2.00</b>                                    | <b>2.33</b>                   | <b>2.12</b>                   | <b>2.43</b>                   |
+
+**Table 10.5.4-2: MU for in-band blocking**
+
+| Test System Uncertainty                                                             | Standard uncertainty $u_i$ (dB)          |                                          |                                          |                                          |
+|-------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|
+|                                                                                     | IAC                                      |                                          | CATR                                     |                                          |
+|                                                                                     | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+| $MU_{\text{conductedwanted}}$ (Wanted signal level error)                           | 1                                        | 1.30                                     | 1                                        | 1.30                                     |
+| $MU_{\text{conductedint}}$ (Interferer signal level error)                          | 1.2                                      | 1.46                                     | 1.2                                      | 1.46                                     |
+| $MU_{\text{EIS}}$ (Combined standard uncertainty)                                   | 0.64                                     | 0.77                                     | 0.71                                     | 0.83                                     |
+| $MU_{\text{TestEquipment}}$ (Uncertainty of the RF signal generator)                | 0.46                                     | 0.58                                     | 0.46                                     | 0.58                                     |
+| $MU_{\text{matching}}$ (Impedance mismatch in the transmitting chain)               | 0.16                                     | 0.28                                     | 0.15                                     | 0.28                                     |
+| $ACLR_{\text{effect}}$ (Impact of interferer leakage)                               | 0.4                                      | 0.4                                      | 0.4                                      | 0.4                                      |
+| <b>Combined standard uncertainty (<math>1\sigma</math>)</b>                         | <b>1.09</b>                              | <b>1.25</b>                              | <b>1.14</b>                              | <b>1.29</b>                              |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %)</b> | <b>2.13</b>                              | <b>2.44</b>                              | <b>2.24</b>                              | <b>2.54</b>                              |
+
+Substituting the variables above into the formula, the MU for each receiver directional requirement can be calculated as shown in table 10.5.4-3 below.
+
+**Table 10.5.4-3: MU for adjacent channel selectivity, in-band blocking, in-channel selectivity**
+
+| Test System Uncertainty                                                             | Standard uncertainty $u_i$ (dB) |
+|-------------------------------------------------------------------------------------|---------------------------------|
+| $MU_{\text{EIS}}$ (Expanded uncertainty)                                            | 2.4                             |
+| $MU_{\text{TestEquipment}}$ (Uncertainty of the RF signal generator)                | 0.9                             |
+| $MU_{\text{PA}}$ (Uncertainty due to use of PA)                                     | 0.2                             |
+| $ACLR_{\text{effect}}$ (Impact of interferer leakage)                               | 0.4                             |
+| <b>Combined standard uncertainty (<math>1\sigma</math>)</b>                         | <b>1.74</b>                     |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %)</b> | <b>3.40</b>                     |
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for OTA ACS, general blocking and narrowband blocking test can be derived from values captured in table 10.5.4-1, derived based on the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA ACS, general blocking and narrowband blocking test requirements.
+
+## 10.5.5 Test Tolerance for OTA ACS, general blocking and narrowband blocking
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA ACS, general blocking and narrowband blocking were derived based on values in clause 10.5.4.
+
+It has been agreed that the TT for the regulatory receiver directional requirements should be zero, while the TT for other receiver directional requirements should be equal to the MU.
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 10.6 OTA receiver intermodulation
+
+### 10.6.1 General
+
+Clause 10.2 captures MU and TT values derivation for the OTA receiver intermodulation directional requirement.
+
+## 10.6.2 Indoor Anechoic Chamber
+
+### 10.6.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup for OTA RX IMD depicted on figure 7.2.1-5.
+
+### 10.6.2.2 Test procedure
+
+#### 10.6.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber shall be done with the procedure shown in clause 8.2, for frequencies of wanted and unwanted signals with power combiner/coupler. Calculate the calibration value for wanted and unwanted signal from A to D, from A to E, and from A to F:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{D}}$ : Calibration value for wanted signal between A and D in figure 7.2.1-5.
+
+$L_{\text{Unwanted\_cal, A}\rightarrow\text{E}}$ : Calibration value for unwanted signal between A and E in figure 7.2.1-5.
+
+$L_{\text{Unwanted\_cal, A}\rightarrow\text{F}}$ : Calibration value for unwanted signal between A and F in figure 7.2.1-5.
+
+#### 10.6.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with its manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with testing system.
+- 2) Set the BS to be satisfied with the *RoAoA* desired by the requirement covering conformance testing receiving direction.
+- 3) Rotate the BS to make the conformance testing receiving direction aligned with the boresight of the reference antenna at the calibration stage.
+- 4) For FDD BS start transmission at the required condition.
+- 5) Set the test signal mean power at the RF signal source generator for wanted signal as the required level plus  $L_{\text{Wanted\_cal, A}\rightarrow\text{D}}$  and the reference measurement channel.
+- 6) Set the test signal mean power at the RF signal source generators for unwanted signal as the required level plus  $L_{\text{Unwanted\_cal, A}\rightarrow\text{E}}$  or plus  $L_{\text{Unwanted\_cal, A}\rightarrow\text{F}}$  and the interference signal channel.
+- 7) Measure the throughput.
+- 8) Repeat the above steps 2 - 6 per conformance testing direction.
+
+### 10.6.2.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+Where
+
+The uncertainty budget behind the EIS MU is captured in clause 10.2. The 2 sigma matching uncertainty is 0.196 dB for  $f \leq 3$  GHz and 0.314 dB for  $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ .
+
+The ACLR effect from the interference signal is assumed to be 0.4 dB, as in TS 36.141 [3]. This is under the assumption that no additional PA is needed for the test signal in the OTA test setup.
+
+The MU for RX IM is calculated as follows. Note that all uncertainties in the table are  $1.96\sigma$  values.
+
+**Table 10.6.2.3-1: IAC MU value derivation for OTA RX IMD measurement, FR1**
+
+| Frequency range | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | Calculation details |
+|-----------------|------------------------|------------------------------------------|---------------------|
+|                 | $\pm 0.7 \text{ dB}$   | $\pm 1.0 \text{ dB}$                     |                     |
+|                 | $\pm 0.5 \text{ dB}$   | $\pm 0.7 \text{ dB}$                     |                     |
+|                 | $\pm 0.7 \text{ dB}$   | $\pm 1.0 \text{ dB}$                     |                     |
+|                 | $\pm 0.196 \text{ dB}$ | $\pm 0.314 \text{ dB}$                   |                     |
+|                 | $\pm 0.672 \text{ dB}$ | $\pm 0.949 \text{ dB}$                   |                     |
+|                 | $\pm 0.460 \text{ dB}$ | $\pm 0.626 \text{ dB}$                   |                     |
+|                 | $\pm 0.672 \text{ dB}$ | $\pm 0.949 \text{ dB}$                   |                     |
+|                 | 1.22 dB                | 1.25 dB                                  |                     |
+|                 | 0.9 dB                 | 0.9 dB                                   |                     |
+|                 | $\pm 0.196 \text{ dB}$ | $\pm 0.314 \text{ dB}$                   |                     |
+|                 | $\pm 0.8 \text{ dB}$   | $\pm 0.807 \text{ dB}$                   |                     |
+| ACLR effect     | 0.4 dB                 |                                          |                     |
+|                 | 2.0 dB                 | 2.5 dB                                   |                     |
+
+## 10.6.3 Compact Antenna Test Range
+
+### 10.6.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the CATR measurement system setup for OTA RX IMD depicted on figure 7.3.1-4.
+
+### 10.6.3.2 Test procedure
+
+#### 10.6.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the CATR shall be done with the procedure shown in clause 8.3, for the frequencies of wanted and 2 interfering signals with power combiners/couplers. Calculate the calibration value for wanted and interfering signals from A to B as well as from A to E and A to H:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{B}}$ : Calibration value for wanted signal between A and B in figure 7.3.1-4.
+
+$L_{\text{interferer1\_cal, A}\rightarrow\text{E}}$ : Calibration value for interfering signal between A and E in figure 7.3.1-4.
+
+$L_{\text{interferer2\_cal, A}\rightarrow\text{H}}$ : Calibration value for interfering signal between A and H in figure 7.3.1-4.
+
+#### 10.6.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with boresight of transmitting antenna.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{B}}$  and at reference measurement channel.
+- 3) Configure RF signal generator for interferer1 to set a modulated signal at the required level plus  $L_{\text{A}\rightarrow\text{E}}$  and at reference measurement channel. The interferer's centre frequency offset should also fulfil the requirement.
+
+- 4) Configure RF signal generator for interferer2 to set a CW signal at the required level plus  $L_{A \rightarrow H}$  and at reference measurement channel. The interferer's centre frequency offset should also fulfil the requirement.
+- 5) Measure the BER or throughput of the wanted signal.
+- 6) Repeat steps all above per involved band for multi-band RIB(s).
+
+### 10.6.3.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+Test system uncertainty is obtained by following equations:
+
+Where
+
+And we assume
+
+Test system uncertainty for OTA receiver intermodulation is shown in table 10.6.3.3-1. Note that all uncertainties in table are  $1.96\sigma$  values.
+
+**Table 10.6.3.3-1: CATR MU value derivation for OTA receiver intermodulation measurement, FR1**
+
+| Frequency range | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | Calculation details |
+|-----------------|----------------|----------------------------|---------------------|
+|                 | $\pm 0.7$ dB   | $\pm 1.0$ dB               |                     |
+|                 | $\pm 0.5$ dB   | $\pm 0.7$ dB               |                     |
+|                 | $\pm 0.7$ dB   | $\pm 1.0$ dB               |                     |
+|                 | $\pm 0.294$ dB | $\pm 0.294$ dB             |                     |
+|                 | $\pm 0.635$ dB | $\pm 0.956$ dB             |                     |
+|                 | $\pm 0.404$ dB | $\pm 0.635$ dB             |                     |
+|                 | $\pm 0.635$ dB | $\pm 0.956$ dB             |                     |
+|                 | 1.33 dB        | 1.40 dB                    |                     |
+|                 | 0.9 dB         | 0.9 dB                     |                     |
+|                 | $\pm 0.294$ dB | $\pm 0.294$ dB             |                     |
+|                 | $\pm 0.933$ dB | $\pm 1.03$ dB              |                     |
+| ACLR effect     | 0.4 dB         |                            |                     |
+|                 | 2.0 dB         | 2.6 dB                     |                     |
+
+## 10.6.3A Plan Wave Synthesizer
+
+### 10.6.3A.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1, with the CATR measurement system setup for OTA RX IMD depicted on figure 7.6.1-4.
+
+## 10.6.3A.2 Test procedure
+
+### 10.6.3A.2.1 Stage 1: Calibration
+
+Calibration procedure for the PWS shall be done with the procedure shown in clause 8.6, for the frequencies of wanted and 2 interfering signals with power combiners/couplers. Calculate the calibration value for wanted and interfering signals from A to C as well as from A to D and A to E:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{C}}$ : Calibration value for wanted signal between A and C in figure 7.6.1-4.
+
+$L_{\text{interferer1\_cal, A}\rightarrow\text{D}}$ : Calibration value for interfering signal between A and D in figure 7.6.1-4.
+
+$L_{\text{interferer2\_cal, A}\rightarrow\text{E}}$ : Calibration value for interfering signal between A and E in figure 7.6.1-4.
+
+### 10.6.3A.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-4. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Configure RF signal generator for wanted signal to set the signal at the required level plus  $L_{\text{A}\rightarrow\text{C}}$  and at reference measurement channel.
+- 3) Configure RF signal generator for interferer1 to set a modulated signal at the required level plus  $L_{\text{A}\rightarrow\text{D}}$  and at reference measurement channel. The interferer's centre frequency offset should also fulfil the requirement.
+- 4) Configure RF signal generator for interferer2 to set a CW signal at the required level plus  $L_{\text{A}\rightarrow\text{E}}$  and at reference measurement channel. The interferer's centre frequency offset should also fulfil the requirement.
+- 5) Measure the BER or throughput of the wanted signal.
+- 6) Repeat steps all above per involved band for multi-band RIB(s).
+
+### 10.6.3A.3 MU value derivation, FR1
+
+The MU is estimated based on conducted MU value (e.g. as in TS 36.141 [3]), the MU for EIS in clause 10.2 and an estimated uncertainty for matching of test equipment and BS or test antenna.
+
+Test system uncertainty is obtained by following equations:
+
+Where:
+
+And we assume
+
+Test system uncertainty for OTA receiver intermodulation is shown in table 10.6.3A.3-1. Note that all uncertainties in table are  $1.96\sigma$  values.
+
+**Table 10.6.3A.3-1: PWS MU value derivation for OTA receiver intermodulation measurement, FR1**
+
+| Frequency range | $f \leq 3$ GHz | $3$ GHz $< f \leq 4.2$ GHz | Calculation details |
+|-----------------|----------------|----------------------------|---------------------|
+|                 | $\pm 0.7$ dB   | $\pm 1.0$ dB               |                     |
+|                 | $\pm 0.5$ dB   | $\pm 0.7$ dB               |                     |
+|                 | $\pm 0.7$ dB   | $\pm 1.0$ dB               |                     |
+|                 | $\pm 0.3$ dB   | $\pm 0.3$ dB               |                     |
+|                 | $\pm 0.632$ dB | $\pm 0.954$ dB             |                     |
+|                 | $\pm 0.400$ dB | $\pm 0.632$ dB             |                     |
+|                 | $\pm 0.632$ dB | $\pm 0.954$ dB             |                     |
+|                 | 1.31 dB        | 1.40 dB                    |                     |
+|                 | 0.9 dB         | 0.9 dB                     |                     |
+|                 | $\pm 0.3$ dB   | $\pm 0.3$ dB               |                     |
+|                 | $\pm 0.902$ dB | $\pm 1.03$ dB              |                     |
+| ACLR effect     | 0.4 dB         |                            |                     |
+|                 | 1.9 dB         | 2.5 dB                     |                     |
+
+### 10.6.4 Maximum accepted test system uncertainty
+
+MU can be calculated as follows:
+
+$$MU_{RXIMD} = \sqrt{MU_{EIS}^2 + MU_{TestEquipment}^2 + MU_{CWint}^2 + MU_{PA}^2 + ACLR_{effect}^2}$$
+
+With
+
+$$MU_{TestEquipment} (1.96\sigma) = 1.96 \times 0.9$$
+
+$$MU_{PA} (1.96\sigma) = 1.96 \times 0.2$$
+
+And
+
+$$ACLR_{effect} (1.96\sigma) = 0.4$$
+
+**Table 10.6.4-1: MU for receiver intermodulation**
+
+| Test System Uncertainty                                            | Standard uncertainty $u_i$ (dB) |                            |                            |                            |
+|--------------------------------------------------------------------|---------------------------------|----------------------------|----------------------------|----------------------------|
+|                                                                    | IAC                             |                            | CATR                       |                            |
+|                                                                    | $3$ GHz $< f \leq 4.2$ GHz      | $4.2$ GHz $< f \leq 6$ GHz | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| $MU_{conductedwanted}$ (Wanted signal level error)                 | 1                               | 1.30                       | 1                          | 1.30                       |
+| $MU_{conductedmodint}$ (Modulated interferer signal level error)   | 1                               | 1.30                       | 1                          | 1.30                       |
+| $MU_{conductedCWint}$ (CW interferer signal level error)           | 0.7                             | 1.08                       | 0.7                        | 1.09                       |
+| $MU_{EIS}$ (Combined standard uncertainty)                         | 0.64                            | 0.77                       | 0.71                       | 0.83                       |
+| $MU_{TestEquipment}$ (Uncertainty of the RF signal generator)      | 0.46                            | 0.58                       | 0.46                       | 0.58                       |
+| $MU_{matching}$ (Impedance mismatch in the transmitting chain)     | 0.16                            | 0.28                       | 0.15                       | 0.28                       |
+| $ACLR_{effect}$ (Impact of interferer leakage)                     | 0.4                             | 0.4                        | 0.4                        | 0.4                        |
+| Combined standard uncertainty ( $1\sigma$ )                        | <b>1.24</b>                     | <b>1.57</b>                | <b>1.32</b>                | <b>1.62</b>                |
+| Expanded uncertainty ( $1.96\sigma$ - confidence interval of 95 %) | <b>2.43</b>                     | <b>3.09</b>                | <b>2.60</b>                | <b>3.17</b>                |
+
+Substituting the variables above into the formula, the MU for each receiver directional requirement can be calculated as shown in table below.
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for OTA RX IMD test can be derived from values captured in table 10.6.4-1, derived based on the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA RX IMD test requirements.
+
+**Table 10.6.4-2: MU for receiver intermodulation**
+
+| <b>Test System Uncertainty</b>                                                      | <b>Standard uncertainty <math>u_i</math> (dB)</b> |
+|-------------------------------------------------------------------------------------|---------------------------------------------------|
+| $MU_{EIS}$ (Expanded uncertainty)                                                   | 2.4                                               |
+| $MU_{TestEquipment}$ (Uncertainty of the RF signal generator)                       | 0.9                                               |
+| $MU_{CWint}$ (CW interferer signal level error)                                     | 0.9                                               |
+| $MU_{PA}$ (Uncertainty due to use of PA)                                            | 0.2                                               |
+| $ACLR_{effect}$ (Impact of interferer leakage)                                      | 0.4                                               |
+| <b>Combined standard uncertainty (<math>1\sigma</math>)</b>                         | <b>1.99</b>                                       |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %)</b> | <b>3.90</b>                                       |
+
+## 10.6.5 Test Tolerance for OTA RX IMD
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA RX IMD were derived based on values discussed in clause 10.6.4.
+
+It has been agreed that the TT for the regulatory receiver directional requirements should be zero, while the TT for other receiver directional requirements should be equal to the MU.
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 10.7 OTA in-channel selectivity
+
+### 10.7.1 General
+
+Clause 10.7 captures MU and TT values derivation for the OTA in-channel selectivity (ICS) directional requirements.
+
+### 10.7.2 Indoor Anechoic Chamber
+
+#### 10.7.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup for OTA ICS depicted on figure 7.2.1-5.
+
+#### 10.7.2.2 Test procedure
+
+##### 10.7.2.2.1 Stage 1: Calibration
+
+The procedure for calibration for OTA ICS is the same as for OTA ACS, as described in clause 10.5.2.2.1 and the system setup depicted on figure 7.2.1-4, however calibration must be carried out for wanted signal and interferer signals appropriate to OTA ICS.
+
+##### 10.7.2.2.2 Stage 2: BS measurement
+
+The IAC procedure for OTA ICS is based on the OTA ACS procedure, described in clause 10.5.2.2.1.
+
+#### 10.7.2.3 MU value derivation, FR1
+
+The MU budget and values for OTA ICS are the same as those for OTA ACS, described in clause 10.5.2.3.
+
+## 10.7.3 Compact Antenna Test Range
+
+### 10.7.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the CATR measurement system setup for OTA ICS depicted on figure 7.3.1-5.
+
+### 10.7.3.2 Test procedure
+
+#### 10.7.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the CATR shall be done with the procedure shown in clause 8.3, with power combiner/coupler. Calculate the calibration value for wanted and interfering signal from A to B as well as from A to D:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{B}}$ : Calibration value for wanted signal between A and B in figure 7.3.1-5.
+
+$L_{\text{interferer\_cal, A}\rightarrow\text{D}}$ : Calibration value for interfering signal between A and D in figure 7.3.1-5.
+
+#### 10.7.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align BS with boresight of transmitting antenna.
+- 2) Configure RF signal generator for wanted signal to set it at the required level plus  $L_{\text{A}\rightarrow\text{B}}$  and at one side of the frequency centre of reference measurement channel.
+- 3) Configure RF signal generator for interferer to set it at the required level plus  $L_{\text{A}\rightarrow\text{E}}$  and at the other side of the frequency centre of reference measurement channel. The interferer should be adjacent to the wanted signal.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat the steps 2 - 4 by exchange the locations of wanted signal and interfering signal in frequency domain at the same channel.
+- 6) Repeat steps above per involved band for multi-band RIB(s).
+
+### 10.7.3.3 MU value derivation, FR1
+
+The MU budget and values for OTA ICS are the same as those for OTA ACS, described in clause 10.5.3.3.
+
+## 10.7.3A Plane Wave Synthesizer
+
+### 10.7.3A.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1, with the PWS measurement system setup for OTA ICS depicted on figure 7.6.1-3.
+
+### 10.7.3A.2 Test procedure
+
+#### 10.7.3A.2.1 Stage 1: Calibration
+
+Calibration procedure for the PWS shall be done with the procedure shown in clause 8.6, with power combiner/coupler. Calculate the calibration value for wanted and interfering signal from A to C as well as from A to D:
+
+$L_{\text{Wanted\_cal, A}\rightarrow\text{C}}$ : Calibration value for wanted signal between A and C in figure 7.6.1-3.
+
+$L_{\text{interferer\_cal, A}\rightarrow\text{D}}$ : Calibration value for interfering signal between A and D in figure 7.6.1-3.
+
+### 10.7.3A.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-3. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Configure RF signal generator for wanted signal to set it at the required level plus  $L_{A \rightarrow C}$  and at one side of the frequency centre of reference measurement channel.
+- 3) Configure RF signal generator for interferer to set it at the required level plus  $L_{A \rightarrow D}$  and at the other side of the frequency centre of reference measurement channel. The interferer should be adjacent to the wanted signal.
+- 4) Measure the throughput of the wanted signal.
+- 5) Repeat the steps 2 - 4 by exchange the locations of wanted signal and interfering signal in frequency domain at the same channel.
+- 6) Repeat steps above per involved band for multi-band RIB(s).
+
+### 10.7.3A.3 MU value derivation, FR1
+
+The MU budget and values for OTA ICS are the same as those for OTA ACS, described in clause 10.5.3A.3.
+
+## 10.7.4 Maximum accepted test system uncertainty
+
+The MU value for OTA ICS is the same as that for OTA ACS, described in clause 10.5.4.
+
+## 10.7.5 Test Tolerance for OTA ICS
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA ICS were derived based on values in clause 10.5.4.
+
+It has been agreed that the TT for the regulatory receiver directional requirements should be zero, while the TT for other receiver directional requirements should be equal to the MU.
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+---
+
+# 11 In-band TRP requirements
+
+## 11.1 General
+
+Clause 11 captures MU and TT values derivation for the in-band *TRP requirements*.
+
+## 11.2 OTA BS output power
+
+### 11.2.1 General
+
+Clause 11.2 captures MU and TT values derivation for the OTA BS output power *TRP requirement* in Normal test conditions.
+
+## 11.2.2 Indoor Anechoic Chamber
+
+### 11.2.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup depicted on figure 7.2.1-1.
+
+NOTE: Whilst the TRP estimation does not require far-field conditions explicitly the MU budget below is based on errors under far-field conditions. If far-field conditions are not met an IAC may still be used but a separate MU analysis is necessary.
+
+### 11.2.2.2 Test procedure
+
+#### 11.2.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for TX requirements depicted in figure 8.2-1.
+
+#### 11.2.2.2.2 Stage 2: BS measurement
+
+The IAC testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with the manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Rotate the BS to make the testing direction aligned with the direction of the receiving antenna.
+- 3) Set the BS to transmit the test signal at the maximum power according to the applicable test model.
+- 4) Measure the applicable test parameter.
+- 5) Repeat the above steps 3 - 4 at a number of discrete directions around the sphere according to the chosen measurement grid, see clause 6.3.3.
+- 6) Calculate TRPs from EIRP, as shown in clause 6.3.
+
+The appropriate test parameter in step 4 is the measured mean power  $P_{R\_desired, D}$  within the desired signal channel bandwidth for each carrier arriving at the measurement equipment connector at reference point D (figure 7.2.1-1). Calculation of  $EIRP_d$  is done using the following equation:
+
+$$EIRP_d = P_{R\_desired, D} + L_{TX\_cal, A \rightarrow D}$$
+
+NOTE: If the test facility only supports single polarization, then measure EIRP with the test facility's test antenna/probe *polarization matched* to the BS, then measure and sum the EIRP on both polarizations. If the test facility supports dual polarization then measure total EIRP for two orthogonal polarizations and calculate total radiated transmit power as the sum over both polarizations.
+
+### 11.2.2.3 MU value derivation, FR1
+
+Table 11.2.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 11.2.2.3-1: IAC MU value derivation for EIRP measurement of OTA BS output power, FR1**
+
+| UID                                                                    | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                               | f < 3 GHz              | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |                                 |                                     |                | f < 3 GHz                                | 3 < f < 4.2 GHz | 4.2 < f < 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                                                   | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                                                   | Pointing misalignment between the BS and the receiving antenna                                | 0.3                    | 0.3             | 0.3             | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-3                                                                   | Quality of quiet zone                                                                         | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4a                                                                  | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                                                  | Mutual coupling between the BS and the receiving antenna                                      | 0                      | 0               | 0               | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                   | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment                                             | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A1-7                                                                   | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                                                   | Random uncertainty                                                                            | 0.1                    | 0.1             | 0.1             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                                                   | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                                                  | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                                                  | Impedance mismatch between the reference antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                                                   | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                                                  | Polarization mismatch for reference antenna                                                   | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                                                  | Mutual coupling between the reference antenna and the receiving antenna                       | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                                                   | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                           | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                                                  | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                                                  | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                                                  | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                                                  | Uncertainty of the absolute gain of the receiving antenna                                     | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.44</b>                              | <b>0.54</b>     | <b>0.54</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.87</b>                              | <b>1.06</b>     | <b>1.06</b>     |
+| <b>TRP summation error</b>                                             |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                               |                        |                 |                 |                                 |                                     |                | <b>1.15</b>                              | <b>1.30</b>     | <b>1.30</b>     |
+
+## 11.2.3 Compact Antenna Test Range
+
+### 11.2.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the Compact Antenna Test Range measurement system setup depicted on figure 8.3-1.
+
+### 11.2.3.2 Test procedure
+
+#### 11.2.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+NOTE: This stage may be omitted provided calibration stage has been performed already during output power measurement.
+
+#### 11.2.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Set up BS in place of SGH from calibration stage. Align the coordinates system of the BS with that of the test system.
+- 2) Set the BS to transmit the test signal at the maximum power according to the applicable test model.
+- 3) Rotate the BS to make the testing direction aligned with the direction of the receiving antenna.
+- 4) Measure the applicable test parameter.
+- 5) Repeat the above steps 2 - 4 at a number of discrete directions around the sphere according to the chosen measurement grid, see clause 6.3.3.
+- 6) Calculate TRPs from power density, as shown in clause 6.3.3.
+
+The appropriate test parameter in step 5 is measured mean power  $P_{R\_desired, B}$  within the desired signal channel bandwidth for each carrier arriving at the measurement equipment connector B in figure 8.3-1. Calculation of  $power_d$  is done using the following equation:
+
+$$power_d = P_{R\_desired, B} + L_{TX\_cal, A \rightarrow B}$$
+
+NOTE: If the test facility only supports single polarization, then measure power with the test facility's test antenna/probe *polarization matched* to the BS, then measure and sum the power on both polarizations. If the test facility supports dual polarization then measure total power for two orthogonal polarizations and calculate total radiated transmit power as the sum over both polarizations.
+
+### 11.2.3.3 MU value derivation, FR1
+
+Table 11.2.3.3-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in CATR (Normal test conditions, FR1).
+
+**Table 11.2.3.3-1: CATR MU value derivation for OTA BS output power measurement, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-18                                                                  | Misalignment and pointing error of BS (for TRP)                                         | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.173                                    | 0.173           | 0.173           |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.140                                    | 0.260           | 0.260           |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                         | 0.21                   | 0.21            | 0.21            | U-shaped                        | 1.41                                | 1              | 0.148                                    | 0.148           | 0.148           |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.001                                    | 0.001           | 0.001           |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                             | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.093                                    | 0.093           | 0.093           |
+| A2-12                                                                  | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1.00                                | 1              | 0.250                                    | 0.250           | 0.250           |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A2-5a                                                                  | Mismatch or receiver chain between receiving antenna and measurement receiver           | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                         | 0.02                   | 0.02            | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A2-8                                                                   | Misalignment positioning system                                                         | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-18b                                                                 | Misalignment and pointing error of calibration antenna (for TRP)                        | 0.50                   | 0.50            | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| A2-9                                                                   | Rotary joints                                                                           | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                        | 0.09                   | 0.09            | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                            | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A2-11                                                                  | Switching uncertainty                                                                   | 0.26                   | 0.26            | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.59</b>                              | <b>0.67</b>     | <b>0.67</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.16</b>                              | <b>1.31</b>     | <b>1.31</b>     |
+| <b>TRP summation error</b>                                             |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.39</b>                              | <b>1.51</b>     | <b>1.51</b>     |
+
+### 11.2.3.4 MU value derivation, FR2
+
+A CATR MU budget was assessed in order to determine acceptable MU for the EIRP accuracy measurement in FR2. The CATR test setup and calibration and measurement procedures for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures.
+
+Table 11.2.3.4-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in CATR (Normal test conditions, FR2).
+
+**Table 11.2.3.4-1: CATR MU value derivation for OTA BS output power measurement, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                   | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                      | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                      |                        |                   |                                 |                                     |                |                                          |                   |
+| A2-1a                                                                  | Misalignment and pointing error of BS (for EIRP)                                                     | 0.20                   | 0.20              | Exp. normal                     | 2.00                                | 1              | 0.10                                     | 0.10              |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power | 0.50                   | 0.70              | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.70              |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                                      | 0.03                   | 0.03              | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02              |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                                          | 0.40                   | 0.40              | Gaussian                        | 1.00                                | 1              | 0.40                                     | 0.40              |
+| A2-12                                                                  | Frequency flatness of test system                                                                    | 0.25                   | 0.25              | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                      |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                  | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver                        | 0.43                   | 0.57              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.40              |
+| A2-6                                                                   | Insertion loss of receiver chain                                                                     | 0.00                   | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                                      | 0.21                   | 0.29              | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.21              |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                            | 0.52                   | 0.52              | Rectangular                     | 1.73                                | 1              | 0.30                                     | 0.30              |
+| A2-8                                                                   | Misalignment positioning system                                                                      | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                                    | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-9                                                                   | Rotary joints                                                                                        | 0.00                   | 0.00              | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.00              |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                                     | 0.09                   | 0.09              | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06              |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                                         | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                      |                        |                   |                                 |                                     |                | <b>0.88</b>                              | <b>1.05</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                      |                        |                   |                                 |                                     |                | <b>1.73</b>                              | <b>2.07</b>       |
+| <b>TRP summation error</b>                                             |                                                                                                      |                        |                   |                                 |                                     |                | <b>1.20</b>                              | <b>1.20</b>       |
+| <b>Total MU</b>                                                        |                                                                                                      |                        |                   |                                 |                                     |                | <b>2.11</b>                              | <b>2.39</b>       |
+
+## 11.2.4 Near Field Test Range
+
+### 11.2.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA BS output power measurements, NF to FF transform is not needed since TRP is computed based on power density measured in Near Field by sampling properly the declared beam.
+
+### 11.2.4.2 Test procedure
+
+#### 11.2.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 11.2.4.2.2 Stage 2: BS measurement
+
+The NFTR testing procedure consists of the following steps:
+
+- 1) Configure the beam of the BS according to the required conditions for the TRP test.
+- 2) Set the BS to transmit the test signal at the maximum power according to the applicable test model.
+- 3) Measure the power density at a number of points (Theta; Phi) in the beam according to the chosen measurement grid. Refer to clause 6.3 for details about measurement grids for TRP measurements.
+- 4) Calculate TRP from the measured power density as in clause 6.3.
+
+### 11.2.4.3 MU value derivation, FR1
+
+Table 11.2.4.3-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in NFTR (Normal test conditions, FR1).
+
+**Table 11.2.4.3-1: NFTR MU value derivation for power density pattern measurement, FR1**
+
+| UID                                     | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A3-1                                    | Axes intersection                                                                       | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-2                                    | Axes orthogonality                                                                      | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-3                                    | Horizontal pointing                                                                     | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-4                                    | Probe vertical position                                                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-5                                    | Probe horizontal/vertical pointing                                                      | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-6                                    | Measurement distance                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-7                                    | Amplitude and phase drift                                                               | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-8                                    | Amplitude and phase noise                                                               | 0.02                   | 0.02            | 0.02            | Gaussian                        | 1                                   | 1              | 0.02                                     | 0.02            | 0.02            |
+| A3-9                                    | Leakage and crosstalk                                                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-10                                   | Amplitude non-linearity                                                                 | 0.04                   | 0.04            | 0.04            | Gaussian                        | 1                                   | 1              | 0.04                                     | 0.04            | 0.04            |
+| A3-11                                   | Amplitude and phase shift in rotary joints                                              | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-12                                   | Channel balance amplitude and phase                                                     | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-13                                   | Probe polarization amplitude and phase                                                  | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-14                                   | Probe pattern knowledge                                                                 | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-15                                   | Multiple reflections                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-16                                   | Room scattering                                                                         | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1                                   | 1              | 0.09                                     | 0.09            | 0.09            |
+| A3-17                                   | BS support scattering                                                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-21                                   | Positioning                                                                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A3-22                                   | Probe array uniformity                                                                  | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1                                   | 1              | 0.06                                     | 0.06            | 0.06            |
+| A3-23                                   | Mismatch of receiver chain                                                              | 0.28                   | 0.28            | 0.28            | U-Shaped                        | 1.41                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A3-24                                   | Insertion loss of receiver chain                                                        | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-25                                   | Uncertainty of the absolute gain of the probe antenna                                   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1                                   | 1              | 0.14                                     | 0.26            | 0.26            |
+| A3-26                                   | Measurement repeatability - positioning repeatability                                   | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1                                   | 1              | 0.15                                     | 0.15            | 0.15            |
+| A3-33                                   | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1                                   | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                    | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1                                   | 1              | 0.13                                     | 0.20            | 0.20            |
+| A3-27                                   | Mismatch of receiver chain                                                              | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-28                                   | Insertion loss of receiver chain                                                        | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+| A3-29                                   | Mismatch in the connection of the calibration antenna                                   | 0.02                   | 0.02            | 0.02            | U-Shaped                        | 1.41                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A3-30                                   | Influence of the calibration antenna feed cable                                         | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1                                   | 1              | 0.00                                     | 0.00            | 0.00            |
+
+|                                                                                          |                                                           |      |      |      |             |        |   |             |             |             |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------|------|------|------|-------------|--------|---|-------------|-------------|-------------|
+| A3-31                                                                                    | Influence of the probe antenna cable                      | 0.00 | 0.00 | 0.00 | Gaussian    | 1      | 1 | 0.00        | 0.00        | 0.00        |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna | 0.50 | 0.43 | 0.43 | Rectangular | 1.7321 | 1 | 0.29        | 0.25        | 0.25        |
+| A3-32                                                                                    | Short term repeatability                                  | 0.09 | 0.09 | 0.09 | Gaussian    | 1      | 1 | 0.09        | 0.09        | 0.09        |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                           |      |      |      |             |        |   | <b>0.52</b> | <b>0.56</b> | <b>0.56</b> |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                           |      |      |      |             |        |   | <b>1.01</b> | <b>1.10</b> | <b>1.10</b> |
+| <b>TRP summation error</b>                                                               |                                                           |      |      |      |             |        |   | <b>0.75</b> | <b>0.75</b> | <b>0.75</b> |
+| <b>Total MU</b>                                                                          |                                                           |      |      |      |             |        |   | <b>1.26</b> | <b>1.33</b> | <b>1.33</b> |
+
+## 11.2.5 Reverberation Chamber
+
+### 11.2.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.7.1.
+
+### 11.2.5.2 Test procedure
+
+#### 11.2.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Reverberation chamber is captured in clause 8.7.
+
+#### 11.2.5.2.2 Stage 2: BS measurement
+
+TRP calculation in an RC does not rely on a coordinate system and as such no reference coordinate system is defined for the RC method, and no alignment between BS and test system is required. The BS should be placed/mounted in the working volume of the RC. It is advised (but not mandatory) to orient the BS is such a way that its antenna boresight is pointing towards a well-stirred part of the chamber (such as towards the stirrer).
+
+The RC testing procedure consists of the following steps:
+
+##### 1. Calculate Ambient Power Level:
+
+- 1) Connect the RX antenna to a calibrated receiver test equipment using the same cables as in the calibration step. Turn on the BS control. Keep the BS RF power off. Terminate the REF TX ant in a 50  $\Omega$  load. See figure 8.7-1 (b).
+
+- 2) Measure the voltage data  $U_{amb}$  and calculate the ambient power level as 
+$$P_{amb} = \frac{\langle |U_{amb}|^2 \rangle}{50}$$
+
+- 3) Calculate the ambient TRP level as 
+$$TRP_{amb} = \frac{\eta M_1^{(r)}}{P^{(r)}} P_{amb}$$
+
+##### 2. Calculate BS TRP:
+
+- 1) Turn on the BS RF power and measure the received voltage  $U_{BS}$ , see figure 8.7-1 (c).
+- 2) Calculate the BS power as:
+- 3) Calculate the TRP from the BS as:
+- 4) The following tests shall be performed on the measurement data:
+  - The dynamic range  $TRP_{BS}/TRP_{amb}$  must be at least 20 dB.
+  - The number of uncorrelated samples, calculated via the auto-correlation function, see [35], shall be at least 250.
+
+There is no need for additional directional measurements to the stirring cycle. In a well-stirred chamber, all directional components will be contained in the samples collected during the measurement cycle and accounted for correctly in the final TRP calculation.
+
+NOTE: A reverberation chamber does not represent a real-life deployment for the BS and can be considered as a hostile environment due to the potentially high field strengths. Therefore, it is important to make sure that the BS is operating properly throughout the entire measurement.
+
+### 11.2.5.3 MU value derivation, FR1
+
+Table 11.2.5.3-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in Reverberation Chamber (Normal test conditions, FR1).
+
+**Table 11.2.5.3-1: Reverberation chamber MU value derivation for OTA BS output power, FR1**
+
+| UID                                                                                      | Uncertainty source                                                                      | Uncertainty value (dB) |                      |                      | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                      |                      |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|----------------------|----------------------|---------------------------------|-------------------------------------|-------|---------------------------------|----------------------|----------------------|
+|                                                                                          |                                                                                         | $f \leq 3$ GHz         | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                                 |                                     |       | $f \leq 3$ GHz                  | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+|                                                                                          |                                                                                         |                        | <b>Hz</b>            |                      |                                 |                                     |       | <b>z</b>                        | <b>Hz</b>            |                      |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                         |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26                 | 0.26                 | Gaussian                        | 1.00                                | 1     | 0.14                            | 0.26                 | 0.26                 |
+| A6-1                                                                                     | Impedance mismatch in the receiving chain                                               | 0.20                   | 0.20                 | 0.20                 | U-shaped                        | 1.41                                | 1     | 0.14                            | 0.14                 | 0.14                 |
+| A6-2                                                                                     | Random uncertainty                                                                      | 0.10                   | 0.10                 | 0.10                 | Rectangular                     | 1.73                                | 1     | 0.06                            | 0.06                 | 0.06                 |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                         |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| A6-3                                                                                     | Reference antenna radiation efficiency                                                  | 0.20                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                 | 0.20                 |
+| A6-4                                                                                     | Mean value estimation of reference antenna mismatch efficiency                          | 0.15                   | 0.15                 | 0.15                 | Gaussian                        | 1.00                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.13                            | 0.20                 | 0.20                 |
+| A6-5                                                                                     | Influence of the reference antenna feed cable                                           | 0.20                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                 | 0.20                 |
+| A6-6                                                                                     | Mean value estimation of transfer function                                              | 0.27                   | 0.27                 | 0.27                 | Gaussian                        | 1.00                                | 1     | 0.27                            | 0.27                 | 0.27                 |
+| A6-7                                                                                     | Uniformity of transfer function                                                         | 0.50                   | 0.50                 | 0.50                 | Gaussian                        | 1.00                                | 1     | 0.50                            | 0.50                 | 0.50                 |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>0.70</b>                     | <b>0.75</b>          | <b>0.75</b>          |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>1.37</b>                     | <b>1.46</b>          | <b>1.46</b>          |
+
+### 11.2.5.4 MU value derivation, FR2
+
+Table 11.2.5.4-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in Reverberation Chamber (Normal test conditions, FR2).
+
+**Table 11.2.5.4-1: Reverberation chamber MU value derivation for OTA BS output power, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                               | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                                  | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                  |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power (EIRP, TRP) | 0.50                   | 0.70              | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.70              |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                                                        | 0.20                   | 0.20              | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.14              |
+| A6-2                                                                   | Random uncertainty                                                                                               | 0.10                   | 0.10              | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                  |                        |                   |                                 |                                     |                |                                          |                   |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                                           | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                                                   | 0.27                   | 0.27              | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27              |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                              | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                                                    | 0.20                   | 0.20              | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20              |
+| A6-6                                                                   | Mean value estimation of transfer function                                                                       | 0.27                   | 0.27              | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27              |
+| A6-7                                                                   | Uniformity of transfer function                                                                                  | 0.50                   | 0.50              | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.50              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                  |                        |                   |                                 |                                     |                | <b>0.94</b>                              | <b>1.06</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                  |                        |                   |                                 |                                     |                | <b>1.85</b>                              | <b>2.08</b>       |
+
+## 11.2.6 Plane Wave Synthesizer
+
+### 11.2.6.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 11.2.6.2 Test procedure
+
+#### 11.2.6.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+#### 11.2.6.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Install the BS as BS with the manufacturer declared coordinate system reference point in the same place as the phase center of the reference antenna A as shown in figure 7.6.1-1. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+- 2) Set the BS to generate the tested beam with the applicable test model with the *beam peak direction* intended to be the same as the testing direction.
+- 3) Measure the appropriate test parameter at the measurement equipment (such as a spectrum analyzer or power meter) denoted in figure 7.6.1-1.
+- 4) Repeat the above steps 2 - 3 at a number of discrete directions around the sphere according to the chosen measurement grid, see clause 6.3.3.
+- 5) Calculate TRPs from power density, as shown in clause 6.3.3.
+
+The appropriate test parameter in step 4 is mean power  $P_{R\_desired, c}$ , within the desired signal channel bandwidth for each carrier arriving at the measurement equipment connector  $\bar{C}$  in figure 7.6.1-1. Calculation of  $power_c$  is done using the following equation:
+
+$$power_c = P_{R\_desired, c} + L$$
+
+NOTE: If the test facility only supports single polarization, then measure power with the test facility's test antenna/probe *polarization matched* to the BS, then measure and sum the power on both polarizations. If the test facility supports dual polarization then measure total power for two orthogonal polarizations and calculate total radiated transmit power as the sum over both polarizations.
+
+### 11.2.6.3 MU value derivation, FR1
+
+Table 11.2.6.3-1 captures derivation of the expanded measurement uncertainty values for OTA BS output power measurements in PWS.
+
+**Table 11.2.6.3-1: PWS MU value derivation for OTA BS output power**
+
+| UID                                                                    | Uncertainty source                                                                                           | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                                              | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A7-1a                                                                  | Misalignment and pointing error of BS                                                                        | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                      | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A7-2a                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna          | 0.05                   | 0.14            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08            | 0.12            |
+| A7-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A7-4a                                                                  | QZ ripple experienced by BS                                                                                  | 0.42                   | 0.43            | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25            | 0.33            |
+| A7-5                                                                   | Miscellaneous uncertainty                                                                                    | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A7-14                                                                  | System non-linearity                                                                                         | 0.10                   | 0.10            | 0.15            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.09            |
+| A7-13                                                                  | Frequency flatness of test system                                                                            | 0.13                   | 0.13            | 0.13            | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08            | 0.08            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                          | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A7-6                                                                   | Mismatch (i.e. reference antenna, network analyser and reference cable)                                      | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A7-7                                                                   | Insertion loss of receiver chain                                                                             | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A7-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A7-8                                                                   | Influence of the calibration antenna feed cable                                                              | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                    | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A7-9                                                                   | Misalignment of positioning system                                                                           | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A7-1b                                                                  | Misalignment and pointing error of calibration antenna                                                       | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A7-10                                                                  | Rotary joints                                                                                                | 0.00                   | 0.00            | 0.00            | U-shaped                        | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A7-2b                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna | 0.12                   | 0.12            | 0.15            | Rectangular                     | 1.73                                | 1              | 0.07                                     | 0.07            | 0.09            |
+| A7-4b                                                                  | QZ ripple experienced by calibration antenna                                                                 | 0.20                   | 0.20            | 0.20            | Rectangular                     | 1.73                                | 1              | 0.12                                     | 0.12            | 0.12            |
+| A7-11                                                                  | Switching uncertainty                                                                                        | 0.02                   | 0.02            | 0.02            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A7-12                                                                  | Field repeatability                                                                                          | 0.06                   | 0.12            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.12            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>0.50</b>                              | <b>0.60</b>     | <b>0.66</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>0.98</b>                              | <b>1.18</b>     | <b>1.29</b>     |
+| <b>TRP summation error</b>                                             |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                                              |                        |                 |                 |                                 |                                     |                | <b>1.24</b>                              | <b>1.40</b>     | <b>1.49</b>     |
+
+## 11.2.7 Maximum accepted test system uncertainty
+
+For the frequency range up to 4.2 GHz, the same MU values as for E-UTRA in TS 37.145-2 [4] were adopted. It is expected that the test chamber setup, calibration and measurement procedures for E-UTRA and NR will be highly similar. All uncertainty factors were judged to be the same.
+
+For the frequency range 4.2 - 6 GHz, all MU factors, including instrumentation related MU were judged to be the same as for the 3 - 4.2 GHz range, and thus the total MU for 4.2 – 6 GHz is the same as for 3 - 4.2 GHz. This assessment was made under the assumption of testing BS designed for licensed spectrum; for unlicensed spectrum the MU may differ.
+
+For CATR the expanded MU is established as a root sum square combining of the dB values for the MU and the SE (see clause 12.10), the MU was decided to be 2.1 dB for the frequency range  $24.25 < f < 29.5$  GHz and 2.4 dB for the frequency range  $37 < f < 43.5$  GHz.
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for OTA BS output power test can be derived from values captured in table 11.2.7-1 for FR1 and in table 11.2.7-2 for FR2, derived based on the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA BS output power test requirement.
+
+**Table 11.2.7-1: Test system specific MU values for the OTA BS output power test, Normal test conditions, FR1**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                                          |                                          |
+|--------------------------------------------------------|---------------------------------|------------------------------------------|------------------------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+| Indoor Anechoic Chamber                                | 1.15                            | 1.30                                     | 1.30                                     |
+| Compact Antenna Test Range                             | 1.39                            | 1.51                                     | 1.51                                     |
+| Near Field Test Range                                  | 1.26                            | 1.33                                     | 1.33                                     |
+| Plane Wave Synthesizer                                 | 1.24                            | 1.40                                     | 1.49                                     |
+| Reverberation Chamber                                  | 1.37                            | 1.46                                     | 1.46                                     |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.4</b>                      | <b>1.5</b>                               | <b>1.5</b>                               |
+
+**Table 11.2.7-2: Test system specific MU values for the OTA BS output power test, Normal test conditions, FR2**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                             |                               |
+|--------------------------------------------------------|---------------------------------|-----------------------------|-------------------------------|
+|                                                        | $24.25 < f < 29.5 \text{ GHz}$  | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+| Indoor Anechoic Chamber                                |                                 |                             | -                             |
+| Compact Antenna Test Range                             | 2.11                            | 2.39                        | -                             |
+| Near Field Test Range                                  |                                 |                             | -                             |
+| Reverberation chamber                                  | 1.85                            | 2.08                        | -                             |
+| Plane Wave Synthesizer                                 |                                 |                             | -                             |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.1</b>                      | <b>2.4</b>                  | <b>2.6</b>                    |
+
+NOTE: MU estimation for  $43.5 < f < 48.2$  GHz was derived based on the linear approximation (based on MU values for lower frequency ranges). MU extrapolation approach was used instead of the typical derivation of the Expanded MU based on the MU budget calculations, as in case of lower frequency ranges.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 11.2.8 Test Tolerance for OTA BS output power
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA BS output power were derived based on values captured in clause 11.2.7.
+
+The TT value was agreed to be the same as the MU value, both for FR1 and FR2.
+
+Frequency range specific Test Tolerance values for the OTA BS output power test are defined in table 11.2.8-1 for FR1 and in table 11.2.8-2 for FR2.
+
+**Table 11.2.8-1: Test Tolerance values for the OTA BS output power, Normal test conditions, FR1**
+
+|                     | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|------------------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (dB) | 1.4                    | 1.5                                      | 1.5                                      |
+
+**Table 11.2.8-2: Test Tolerance values for the OTA BS output power, Normal test conditions, FR2**
+
+|                     | $24.25 < f < 29.5 \text{ GHz}$ | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+|---------------------|--------------------------------|-----------------------------|-------------------------------|
+| Test Tolerance (dB) | 2.1                            | 2.4                         | 2.6                           |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 11.3 OTA ACLR
+
+### 11.3.1 General
+
+Clause 11.3 captures MU and TT values derivation for the OTA ACLR *TRP requirement* in Normal test conditions.
+
+### 11.3.2 Indoor Anechoic Chamber
+
+#### 11.3.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup depicted on figure 7.2.1-1.
+
+NOTE: Whilst the TRP estimation does not require far-field conditions explicitly the MU budget below is based on errors under far-field conditions. If far-field conditions are not met an in-door anechoic chamber may be used but a separate MU analysis is necessary.
+
+#### 11.3.2.2 Test procedure
+
+##### 11.3.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for TX requirements depicted in figure 8.2-1.
+
+Calibration shall be performed individually for both the wanted signal and adjacent channel frequencies.
+
+##### 11.3.2.2.2 Stage 2: BS measurement
+
+Reference IAC procedure in clause 11.2.2.2.2 (i.e. the same procedure as for OTA BS output power measurement in IAC). The appropriate parameters in step 4 are:
+
+$P_{R\_desired, D}$ : Measured mean power within the desired signal channel bandwidth for each carrier at the measurement equipment connector at D in figure 7.2.1-1.
+
+$P_{R\_emission, D}$ : Measured mean emission power in the neighbouring channel bandwidth for each carrier at the measurement equipment connector at D in figure 7.2.1-1.
+
+Calculation of  $power_d$  and  $power_e$  is done using following formulas:
+
+$$power_d = P_{R\_desired, D} + L_{TX\_cal, A \rightarrow D}$$
+
+$$power_e = P_{R\_emission, D} + L_{TX\_cal, A \rightarrow D}$$
+
+After calculation of TRP from power as shown in clause 6.3 calculate the OTA ACLR.
+
+### 11.3.2.3 MU value derivation, FR1
+
+Table 11.3.2.3-1 captures derivation of the expanded measurement uncertainty values for absolute OTA ACLR measurements in in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 11.3.2.3-1: IAC MU value derivation for the absolute OTA ACLR measurement**
+
+| UID                                     | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                                                               | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                    | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                    | Pointing misalignment between the BS and the receiving antenna                                | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4a                                   | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                   | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                    | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)       | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A1-7                                    | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                    | Random uncertainty                                                                            | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                    | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                   | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                   | Impedance mismatch between the reference antenna and the network analyzer.                    | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                   | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                   | Mutual coupling between the reference antenna and the receiving antenna                       | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                    | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                    | Uncertainty of the network analyzer                                                           | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                   | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                   | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                   | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                   | Uncertainty of the absolute gain of the receiving antenna                                     | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+
+|                                                                                          |             |             |             |
+|------------------------------------------------------------------------------------------|-------------|-------------|-------------|
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         | <b>0.44</b> | <b>0.54</b> | <b>0.54</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> | <b>0.87</b> | <b>1.06</b> | <b>1.06</b> |
+| <b>TRP summation error</b>                                                               | <b>0.75</b> | <b>0.75</b> | <b>0.75</b> |
+| <b>Total MU</b>                                                                          | <b>1.15</b> | <b>1.30</b> | <b>1.30</b> |
+
+### 11.3.3 Compact Antenna Test Range
+
+#### 11.3.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the Compact Antenna Test Range measurement system setup depicted on figure 8.3-1.
+
+#### 11.3.3.2 Test procedure
+
+##### 11.3.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+NOTE: This stage may be omitted provided calibration stage has been performed already during output power measurement.
+
+##### 11.3.3.2.2 Stage 2: BS measurement
+
+The CATR testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of the range antenna.
+- 2) Configure carrier at a power level according to the manufacturer's declared rated output power and test configuration.
+- 3) Measure wanted and adjacent channel power for the frequency offsets both side of carrier frequency considering both polarizations of the range antenna. In multiple carrier case only offset frequencies below the lowest and above the offsets highest carrier frequency used shall be measured for ACLR; offsets in between carriers may be subject to CACLR.
+- 4) Repeat step 3 for additional points for all necessary points needed for full TRP for the wanted signal and adjacent channel emissions.
+- 5) Calculate ACLR or CACLR from the wanted signal TRP and the adjacent channel emissions TRP.
+
+The appropriate parameters in step 3 are:
+
+$P_{R\_desired, D}$ : Measured mean power within the desired signal channel bandwidth for each carrier at the measurement equipment connector at D in figure 7.3.1-1.
+
+$P_{R\_emission, D}$ : Measured mean emission power in the neighbouring channel bandwidth for each carrier at the measurement equipment connector at D in figure 7.3.1-1.
+
+Calculation of  $Power_d$  and  $Power_e$  is done using following formulas:
+
+$$Power_d = P_{R\_desired, D} + L_{TX\_cal, A \rightarrow D}$$
+
+$$Power_e = P_{R\_emission, D} + L_{TX\_cal, A \rightarrow D}$$
+
+After calculation of TRP from power as shown in clause 6.3, calculate the OTA ACLR.
+
+#### 11.3.3.3 MU value derivation, FR1
+
+Table 11.3.3.3-1 captures derivation of the expanded measurement uncertainty values for absolute OTA ACLR measurements in in Compact Antenna Test Range (Normal test conditions, FR1).
+
+Table 11.3.3.3-2 captures derivation of the expanded measurement uncertainty values for relative OTA ACLR measurements in in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 11.3.3.3-1: CATR MU value derivation for the EIRP measurement of the absolute OTA ACLR, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-18a                                                                 | Misalignment and pointing error of BS (for TRP)                                         | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                         | 0.21                   | 0.21            | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                             | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A2-12                                                                  | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver           | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                         | 0.02                   | 0.02            | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A2-8                                                                   | Misalignment positioning system                                                         | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-18b                                                                 | Misalignment and pointing error of calibration antenna (for TRP)                        | 0.50                   | 0.50            | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| A2-9                                                                   | Rotary joints                                                                           | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                        | 0.09                   | 0.09            | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                            | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A2-11                                                                  | Switching uncertainty                                                                   | 0.26                   | 0.26            | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.59</b>                              | <b>0.67</b>     | <b>0.67</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.16</b>                              | <b>1.31</b>     | <b>1.31</b>     |
+| <b>TRP summation error</b>                                             |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.39</b>                              | <b>1.51</b>     | <b>1.51</b>     |
+
+**Table 11.3.3.3-2: CATR MU value derivation for the EIRP measurement of the relative OTA ACLR, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-18a                                                                 | Misalignment and pointing error of BS (a) (for TRP)                                     | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                             | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A2-12                                                                  | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver           | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A2-11                                                                  | Switching uncertainty                                                                   | 0.26                   | 0.26            | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.42</b>                              | <b>0.54</b>     | <b>0.54</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.83</b>                              | <b>1.06</b>     | <b>1.06</b>     |
+| <b>TRP summation error</b>                                             |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.12</b>                              | <b>1.30</b>     | <b>1.30</b>     |
+
+### 11.3.3.4 MU value derivation, FR2
+
+A CATR MU budget was assessed in order to determine acceptable MU for the EIRP accuracy measurement in FR2. The CATR test setup and calibration and measurement procedures for FR2 are expected to be similar to those of FR1, although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures. However, it is noted that in order to achieve the test instrument uncertainties that were assumed, calibration of the spectrum analyzer may be needed.
+
+Table 11.3.3.4-1 captures derivation of the expanded measurement uncertainty values for absolute OTA ACLR measurements in in Compact Antenna Test Range (Normal test conditions, FR2).
+
+Table 11.3.3.4-2 captures derivation of the expanded measurement uncertainty values for relative OTA ACLR measurements in in Compact Antenna Test Range (Normal test conditions, FR2).
+
+**Table 11.3.3.4-1: CATR MU value derivation for the EIRP measurement of the absolute OTA ACLR, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                                       | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                                          | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                          |                        |                   |                                 |                                     |                |                                          |                   |
+| A2-1a                                                                  | Misalignment and pointing error of BS (for EIRP)                                                                         | 0.20                   | 0.20              | Exp. normal                     | 2.00                                | 1              | 0.10                                     | 0.10              |
+| C1-7                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.90                   | 0.90              | Gaussian                        | 1.00                                | 1              | 0.90                                     | 0.90              |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                                                          | 0.03                   | 0.03              | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02              |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                                                              | 0.40                   | 0.40              | Gaussian                        | 1.00                                | 1              | 0.40                                     | 0.40              |
+| A2-12                                                                  | Frequency flatness of test system                                                                                        | 0.25                   | 0.25              | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                          |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                                      | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A2-5b                                                                  | Mismatch of receiver chain for low power                                                                                 | 0.72                   | 0.72              | U-shaped                        | 1.41                                | 1              | 0.51                                     | 0.51              |
+| A2-6                                                                   | Insertion loss in receiver chain                                                                                         | 0.00                   | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| C2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                                                          | 0.21                   | 0.29              | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.21              |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                                | 0.52                   | 0.52              | Rectangular                     | 1.73                                | 1              | 0.30                                     | 0.30              |
+| A2-8                                                                   | Misalignment positioning system                                                                                          | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                                                        | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-9                                                                   | Rotary joints                                                                                                            | 0.00                   | 0.00              | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.00              |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                                                         | 0.09                   | 0.09              | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06              |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                                                             | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-11                                                                  | Switching uncertainty                                                                                                    | 0.10                   | 0.10              | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                          |                        |                   |                                 |                                     |                | <b>1.23</b>                              | <b>1.24</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                        |                   |                                 |                                     |                | <b>2.41</b>                              | <b>2.43</b>       |
+| <b>TRP summation error</b>                                             |                                                                                                                          |                        |                   |                                 |                                     |                | <b>1.20</b>                              | <b>1.20</b>       |
+| <b>Total MU</b>                                                        |                                                                                                                          |                        |                   |                                 |                                     |                | <b>2.69</b>                              | <b>2.71</b>       |
+
+**Table 11.3.3.4-2: CATR MU value derivation for the EIRP measurement of the relative OTA ACLR, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                        | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                           | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                           |                        |                   |                                 |                                     |                |                                          |                   |
+| A2-1a                                                                  | Misalignment and pointing error of BS (for EIRP)                                                          | 0.20                   | 0.20              | Exp. normal                     | 2.00                                | 1              | 0.10                                     | 0.10              |
+| C1-8                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - relative (ACLR) | 0.75                   | 0.90              | Gaussian                        | 1.00                                | 1              | 0.75                                     | 0.90              |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                                               | 0.40                   | 0.40              | Gaussian                        | 1.00                                | 1              | 0.40                                     | 0.40              |
+| A2-12                                                                  | Frequency flatness of test system                                                                         | 0.25                   | 0.25              | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                           |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                       | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver                             | 0.43                   | 0.57              | U-shaped                        | 1.41                                | 1              | 0.30                                     | 0.40              |
+| A2-6                                                                   | Insertion loss in receiver chain                                                                          | 0.00                   | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| A2-11                                                                  | Switching uncertainty                                                                                     | 0.10                   | 0.10              | Rectangular                     | 1.73                                | 0              | 0.06                                     | 0.06              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                           |                        |                   |                                 |                                     |                | <b>0.99</b>                              | <b>1.14</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                           |                        |                   |                                 |                                     |                | <b>1.94</b>                              | <b>2.23</b>       |
+| <b>TRP summation error</b>                                             |                                                                                                           |                        |                   |                                 |                                     |                | <b>1.20</b>                              | <b>1.20</b>       |
+| <b>Total MU</b>                                                        |                                                                                                           |                        |                   |                                 |                                     |                | <b>2.28</b>                              | <b>2.54</b>       |
+
+## 11.3.4 Near Field Test Range
+
+### 11.3.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA ACLR measurement, the NF to FF transform is not needed since ACLR is based on TRP.
+
+### 11.3.4.2 Test procedure
+
+#### 11.3.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 11.3.4.2.2 Stage 2: BS measurement
+
+The NFTR procedure for absolute ACLR OTA measurement consists of the following steps:
+
+1. Configure TX branch and carrier according to the required test configuration
+2. Measure in Near Field ACLR and CALCR for the frequency offsets both side of carrier frequency for both polarizations. In multiple carrier case only offset frequencies below the lowest and above the offsets highest carrier frequency used shall be measured.
+  - a. Power is measured Near Field – no NF to FF transform is applied.
+  - b. Full sphere power is measured with using a defined sampling grid (refer to clause 6.3 for proper measurement grids).
+3. Calculate TRP.
+
+### 11.3.4.3 MU value derivation, FR1
+
+Table 11.3.4.3-1 captures derivation of the expanded measurement uncertainty values for OTA ACLR measurements in NFTR (Normal test conditions, FR1).
+
+**Table 11.3.4.3-1: NFTR MU value derivation for absolute ACLR measurement**
+
+| UID                                                                                      | Uncertainty source                                                                      | Uncertainty value (dB) |                      |                      | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                      |                      |
+|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|----------------------|----------------------|---------------------------------|-------------------------------------|-------|---------------------------------|----------------------|----------------------|
+|                                                                                          |                                                                                         | $f \leq 3$ GHz         | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                                 |                                     |       | $f \leq 3$ GHz                  | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                         |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| A3-1                                                                                     | Axes intersection                                                                       | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-2                                                                                     | Axes orthogonality                                                                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-3                                                                                     | Horizontal pointing                                                                     | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-4                                                                                     | Probe vertical position                                                                 | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-5                                                                                     | Probe horizontal/vertical pointing                                                      | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-6                                                                                     | Measurement distance                                                                    | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-7                                                                                     | Amplitude and phase drift                                                               | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-8                                                                                     | Amplitude and phase noise                                                               | 0.02                   | 0.02                 | 0.02                 | Gaussian                        | 1.00                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| A3-9                                                                                     | Leakage and crosstalk                                                                   | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-10                                                                                    | Amplitude non-linearity                                                                 | 0.04                   | 0.04                 | 0.04                 | Gaussian                        | 1.00                                | 1     | 0.04                            | 0.04                 | 0.04                 |
+| A3-11                                                                                    | Amplitude and phase shift in rotary joints                                              | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-12                                                                                    | Channel balance amplitude and phase                                                     | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-13                                                                                    | Probe polarization amplitude and phase                                                  | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-14                                                                                    | Probe pattern knowledge                                                                 | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-15                                                                                    | Multiple reflections                                                                    | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-16                                                                                    | Room scattering                                                                         | 0.09                   | 0.09                 | 0.09                 | Gaussian                        | 1.00                                | 1     | 0.09                            | 0.09                 | 0.09                 |
+| A3-17                                                                                    | BS support scattering                                                                   | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-21                                                                                    | Positioning                                                                             | 0.03                   | 0.03                 | 0.03                 | Rectangular                     | 1.73                                | 1     | 0.02                            | 0.02                 | 0.02                 |
+| A3-22                                                                                    | Probe array uniformity                                                                  | 0.06                   | 0.06                 | 0.06                 | Gaussian                        | 1.00                                | 1     | 0.06                            | 0.06                 | 0.06                 |
+| A3-23                                                                                    | Mismatch of receiver chain                                                              | 0.28                   | 0.28                 | 0.28                 | U-Shaped                        | 1.41                                | 1     | 0.20                            | 0.20                 | 0.20                 |
+| A3-24                                                                                    | Insertion loss of receiver chain                                                        | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-25                                                                                    | Uncertainty of the absolute gain of the probe antenna                                   | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C1-1                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26                 | 0.26                 | Gaussian                        | 1.00                                | 1     | 0.14                            | 0.26                 | 0.26                 |
+| A3-26                                                                                    | Measurement repeatability - positioning repeatability                                   | 0.15                   | 0.15                 | 0.15                 | Gaussian                        | 1.00                                | 1     | 0.15                            | 0.15                 | 0.15                 |
+| A3-33                                                                                    | Frequency flatness of test system                                                       | 0.25                   | 0.25                 | 0.25                 | Gaussian                        | 1.00                                | 1     | 0.25                            | 0.25                 | 0.25                 |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                         |                        |                      |                      |                                 |                                     |       |                                 |                      |                      |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20                 | 0.20                 | Gaussian                        | 1.00                                | 1     | 0.13                            | 0.20                 | 0.20                 |
+| A3-27                                                                                    | Mismatch of receiver chain                                                              | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-28                                                                                    | Insertion loss of receiver chain                                                        | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-29                                                                                    | Mismatch in the connection of the calibration antenna                                   | 0.02                   | 0.02                 | 0.02                 | U-Shaped                        | 1.41                                | 1     | 0.01                            | 0.01                 | 0.01                 |
+| A3-30                                                                                    | Influence of the calibration antenna feed cable                                         | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| A3-31                                                                                    | Influence of the probe antenna cable                                                    | 0.00                   | 0.00                 | 0.00                 | Gaussian                        | 1.00                                | 1     | 0.00                            | 0.00                 | 0.00                 |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43                 | 0.43                 | Rectangular                     | 1.73                                | 1     | 0.29                            | 0.25                 | 0.25                 |
+| A3-32                                                                                    | Short term repeatability                                                                | 0.09                   | 0.09                 | 0.09                 | Gaussian                        | 1.00                                | 1     | 0.09                            | 0.09                 | 0.09                 |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>0.52</b>                     | <b>0.56</b>          | <b>0.56</b>          |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>1.01</b>                     | <b>1.10</b>          | <b>1.10</b>          |
+| <b>TRP summation error</b>                                                               |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>0.75</b>                     | <b>0.75</b>          | <b>0.75</b>          |
+| <b>Total MU</b>                                                                          |                                                                                         |                        |                      |                      |                                 |                                     |       | <b>1.26</b>                     | <b>1.33</b>          | <b>1.33</b>          |
+
+### 11.3.5 Reverberation Chamber
+
+#### 11.3.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.7.1.
+
+#### 11.3.5.2 Test procedure
+
+##### 11.3.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Reverberation chamber is captured in clause 8.7.
+
+##### 11.3.5.2.2 Stage 2: BS measurement
+
+The RC test procedure is described in clause 11.2.5.2.2 (i.e. the same procedure as for the OTA BS output power).
+
+#### 11.3.5.3 MU value derivation, FR1
+
+Table 11.3.5.3-1 captures derivation of the expanded measurement uncertainty values for relative ACLR measurements in Reverberation Chamber (Normal test conditions, FR1).
+
+Table 11.3.5.3-2 captures derivation of the expanded measurement uncertainty values for absolute ACLR measurements in Reverberation Chamber (Normal test conditions, FR1).
+
+**Table 11.3.5.3-1: Reverberation Chamber MU value derivation for relative ACLR measurement**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                               | 0.20                   | 0.20            | 0.20            | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.14            | 0.14            |
+| A6-2                                                                   | Random uncertainty                                                                      | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                  | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1                                   | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                          | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1                                   | 1              | 0.15                                     | 0.15            | 0.15            |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1                                   | 1              | 0.13                                     | 0.20            | 0.20            |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                           | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1                                   | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-6                                                                   | Mean value estimation of transfer function                                              | 0.27                   | 0.27            | 0.27            | Gaussian                        | 1                                   | 1              | 0.27                                     | 0.27            | 0.27            |
+| A6-7                                                                   | Uniformity of transfer function                                                         | 0.50                   | 0.50            | 0.50            | Gaussian                        | 1                                   | 1              | 0.50                                     | 0.50            | 0.50            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.70</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.37</b>                              | <b>1.46</b>     | <b>1.46</b>     |
+
+**Table 11.3.5.3-2: Reverberation chamber MU value derivation for absolute ACLR measurement**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                               | 0.20                   | 0.20            | 0.20            | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.14            | 0.14            |
+| A6-2                                                                   | Random uncertainty                                                                      | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                  | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                          | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                           | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-6                                                                   | Mean value estimation of transfer function                                              | 0.27                   | 0.27            | 0.27            | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27            | 0.27            |
+| A6-7                                                                   | Uniformity of transfer function                                                         | 0.50                   | 0.50            | 0.50            | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.50            | 0.50            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.70</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.37</b>                              | <b>1.46</b>     | <b>1.46</b>     |
+
+### 11.3.5.4 MU value derivation, FR2
+
+Table 11.3.5.4-1 captures derivation of the expanded measurement uncertainty values for relative ACLR measurements in Reverberation Chamber (Normal test conditions, FR2).
+
+Table 11.3.5.4-2 captures derivation of the expanded measurement uncertainty values for absolute ACLR measurements in Reverberation Chamber (Normal test conditions, FR2).
+
+**Table 11.3.5.4-1: Reverberation chamber MU value derivation for absolute ACLR measurement, FR2**
+
+| UID                                                                                      | Uncertainty source                                                                                                       | Uncertainty value (dB)    |                        | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                        |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------|---------------------------------|-------------------------------------|-------|---------------------------------|------------------------|
+|                                                                                          |                                                                                                                          | $24.25 < f \leq 29.5$ GHz | $37 < f \leq 43.5$ GHz |                                 |                                     |       | $24.25 < f \leq 29.5$ GHz       | $37 < f \leq 43.5$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                                          |                           |                        |                                 |                                     |       |                                 |                        |
+| C1-7                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.90                      | 0.90                   | Gaussian                        | 1.00                                | 1     | 0.90                            | 0.90                   |
+| A6-1                                                                                     | Impedance mismatch in the receiving chain                                                                                | 0.20                      | 0.20                   | U-shaped                        | 1.41                                | 1     | 0.14                            | 0.14                   |
+| A6-2                                                                                     | Random uncertainty                                                                                                       | 0.10                      | 0.10                   | Rectangular                     | 1.73                                | 1     | 0.06                            | 0.06                   |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                                          |                           |                        |                                 |                                     |       |                                 |                        |
+| A6-3                                                                                     | Reference antenna radiation efficiency                                                                                   | 0.30                      | 0.30                   | Gaussian                        | 1.00                                | 1     | 0.30                            | 0.30                   |
+| A6-4                                                                                     | Mean value estimation of reference antenna mismatch efficiency                                                           | 0.27                      | 0.27                   | Gaussian                        | 1.00                                | 1     | 0.27                            | 0.27                   |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                                                      | 0.30                      | 0.30                   | Gaussian                        | 1.00                                | 1     | 0.30                            | 0.30                   |
+| A6-5                                                                                     | Influence of the reference antenna feed cable                                                                            | 0.20                      | 0.20                   | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                   |
+| A6-6                                                                                     | Mean value estimation of transfer function                                                                               | 0.27                      | 0.27                   | Gaussian                        | 1.00                                | 1     | 0.27                            | 0.27                   |
+| A6-7                                                                                     | Uniformity of transfer function                                                                                          | 0.50                      | 0.50                   | Gaussian                        | 1.00                                | 1     | 0.50                            | 0.50                   |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                                                          |                           |                        |                                 |                                     |       | <b>1.20</b>                     | <b>1.20</b>            |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                           |                        |                                 |                                     |       | <b>2.36</b>                     | <b>2.36</b>            |
+
+**Table 11.3.5.4-2: Reverberation chamber MU value derivation for relative ACLR measurement, FR2**
+
+| UI<br>D                                                                | Uncertainty source                                                                                        | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                           | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                           |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-8                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - relative (ACLR) | 0.75                   | 0.90              | Gaussian                        | 1.00                                | 1              | 0.75                                     | 0.90              |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                                                 | 0.20                   | 0.20              | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.14              |
+| A6-2                                                                   | Random uncertainty                                                                                        | 0.10                   | 0.10              | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                           |                        |                   |                                 |                                     |                |                                          |                   |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                                    | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                                            | 0.27                   | 0.27              | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27              |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                       | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                                             | 0.20                   | 0.20              | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20              |
+| A6-6                                                                   | Mean value estimation of transfer function                                                                | 0.27                   | 0.27              | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27              |
+| A6-7                                                                   | Uniformity of transfer function                                                                           | 0.50                   | 0.50              | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.50              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                           |                        |                   |                                 |                                     |                | <b>1.10</b>                              | <b>1.20</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                           |                        |                   |                                 |                                     |                | <b>2.15</b>                              | <b>2.36</b>       |
+
+## 11.3.6 Plane Wave Synthesizer
+
+### 11.3.6.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 11.3.6.2 Test procedure
+
+#### 11.3.6.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+NOTE: This stage may be omitted provided calibration stage has been performed already during output power measurement.
+
+#### 11.3.6.2.2 Stage 2: BS measurement
+
+The PWS testing procedure consists of the following steps:
+
+- 1) Align BS with boresight of the range antenna.
+- 2) Configure carrier at a power level according to the manufacturer's declared rated output power and test configuration.
+
+- 3) Measure wanted and adjacent channel power for the frequency offsets both side of carrier frequency considering both polarizations of the range antenna. In multiple carrier case only offset frequencies below the lowest and above the offsets highest carrier frequency used shall be measured for ACLR; offsets in between carriers may be subject to CACLR.
+- 4) Repeat step 3 for additional points for all necessary points needed for full TRP for the wanted signal and adjacent channel emissions.
+- 5) Calculate ACLR or CACLR from the wanted signal TRP and the adjacent channel emissions TRP.
+
+The appropriate parameters in step 3 are:
+
+$P_{R\_desired, c}$ : Measured mean power within the desired signal channel bandwidth for each carrier at the measurement equipment connector at C in figure 7.6.1-1.
+
+$P_{R\_emission, c}$ : Measured mean emission power in the neighbouring channel bandwidth for each carrier at the measurement equipment connector at C in figure 7.6.1-1.
+
+Calculation of  $Power_d$  and  $Power_e$  is done using following formulas:
+
+$$Power_d = P_{R\_desired, c} + L$$
+
+$$Power_e = P_{R\_emission, c} + L$$
+
+After calculation of TRP from power as shown in clause 6.3, calculate the OTA ACLR.
+
+### 11.3.6.3 MU value derivation, FR1
+
+The MU value derivation for absolute ACLR measurements is the same as in clause 11.2.6.3 (i.e. OTA BS output power).
+
+Table 11.3.6.3-1 captures derivation of the expanded measurement uncertainty values for relative ACLR measurements in PWS.
+
+Table 11.3.6.3-2 captures derivation of the expanded measurement uncertainty values for absolute ACLR measurements in PWS.
+
+**Table 11.3.6.3-1: PWS MU value derivation for relative ACLR measurement**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A7-1a                                                                  | Misalignment and pointing error of BS                                                   | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A7-4a                                                                  | QZ ripple experienced by BS                                                             | 0.42                   | 0.43            | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25            | 0.33            |
+| A7-13                                                                  | Frequency flatness of test system                                                       | 0.13                   | 0.13            | 0.13            | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08            | 0.08            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A7-6                                                                   | Mismatch (i.e. reference antenna, network analyser and reference cable)                 | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A7-7                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A7-11                                                                  | Switching uncertainty                                                                   | 0.02                   | 0.02            | 0.02            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.35</b>                              | <b>0.49</b>     | <b>0.54</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.69</b>                              | <b>0.96</b>     | <b>1.05</b>     |
+| <b>TRP summation error</b>                                             |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.02</b>                              | <b>1.22</b>     | <b>1.29</b>     |
+
+**Table 11.3.6.3-2: PWS MU value derivation for absolute ACLR measurement**
+
+| UID                                                                    | Uncertainty source                                                                                           | Uncertainty value (dB) |                  |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------|------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                                                        |                                                                                                              | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GH z | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GH z | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                              |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| A7-1a                                                                  | Misalignment and pointing error of BS                                                                        | 0.10                   | 0.10             | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)                      | 0.14                   | 0.26             | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26             | 0.26            |
+| A7-2a                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna          | 0.05                   | 0.14             | 0.20            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.08             | 0.12            |
+| A7-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09             | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09            |
+| A7-4a                                                                  | QZ ripple experienced by BS                                                                                  | 0.42                   | 0.43             | 0.57            | Rectangular                     | 1.73                                | 1              | 0.24                                     | 0.25             | 0.33            |
+| A7-5                                                                   | Miscellaneous uncertainty                                                                                    | 0.00                   | 0.00             | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A7-14                                                                  | System non-linearity                                                                                         | 0.10                   | 0.10             | 0.15            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.09            |
+| A7-13                                                                  | Frequency flatness of test system                                                                            | 0.13                   | 0.13             | 0.13            | Rectangular                     | 1.73                                | 1              | 0.08                                     | 0.08             | 0.08            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                              |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                          | 0.13                   | 0.20             | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20             | 0.20            |
+| A7-6                                                                   | Mismatch (i.e. reference antenna, network analyser and reference cable)                                      | 0.13                   | 0.33             | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23             | 0.23            |
+| A7-7                                                                   | Insertion loss of receiver chain                                                                             | 0.18                   | 0.18             | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10             | 0.10            |
+| A7-3                                                                   | RF leakage (calibration antenna connector terminated)                                                        | 0.09                   | 0.09             | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09            |
+| A7-8                                                                   | Influence of the calibration antenna feed cable                                                              | 0.10                   | 0.10             | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                    | 0.50                   | 0.43             | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25            |
+| A7-9                                                                   | Misalignment of positioning system                                                                           | 0.00                   | 0.00             | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A7-1b                                                                  | Misalignment and pointing error of calibration antenna                                                       | 0.05                   | 0.05             | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| A7-10                                                                  | Rotary joints                                                                                                | 0.00                   | 0.00             | 0.00            | U-shaped                        | 1.73                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A7-2b                                                                  | Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for calibration antenna | 0.12                   | 0.12             | 0.15            | Rectangular                     | 1.73                                | 1              | 0.07                                     | 0.07             | 0.09            |
+| A7-4b                                                                  | QZ ripple experienced by calibration antenna                                                                 | 0.20                   | 0.20             | 0.20            | Rectangular                     | 1.73                                | 1              | 0.12                                     | 0.12             | 0.12            |
+| A7-11                                                                  | Switching uncertainty                                                                                        | 0.02                   | 0.02             | 0.02            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| A7-12                                                                  | Field repeatability                                                                                          | 0.06                   | 0.12             | 0.15            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.12             | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                              |                        |                  |                 |                                 |                                     |                | <b>0.50</b>                              | <b>0.61</b>      | <b>0.66</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                              |                        |                  |                 |                                 |                                     |                | <b>0.98</b>                              | <b>1.19</b>      | <b>1.29</b>     |
+| <b>TRP summation error</b>                                             |                                                                                                              |                        |                  |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>      | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                                              |                        |                  |                 |                                 |                                     |                | <b>1.24</b>                              | <b>1.40</b>      | <b>1.49</b>     |
+
+### 11.3.7 Maximum accepted test system uncertainty
+
+For the frequency range up to 4.2 GHz, the same MU values as for E-UTRA were adopted. It is expected that the test chamber setup, calibration and measurement procedures for E-UTRA and NR will be highly similar. All uncertainty factors were judged to be the same.
+
+For the frequency range 4.2 - 6 GHz, all MU factors, including instrumentation related MU were judged to be the same as for the 3 - 4.2 GHz range, and thus the total MU for 4.2 – 6 GHz is the same as for 3 - 4.2 GHz. This assessment was made under the assumption of testing BS designed for licensed spectrum; for unlicensed spectrum the MU may differ.
+
+For CATR the expanded MU is established as a root sum square combining of the dB values for the MU and the SE (see clause 6.3.6), the MU for absolute ACLR was decided to be 2.7 dB for the frequency range  $24.25 < f < 29.5$  GHz and 2.7 dB for the frequency range  $37 < f < 43.5$  GHz. The MU for relative ACLR was decided to be 2.3 dB for the frequency range  $24.25 < f < 29.5$  GHz and 2.6 dB for the frequency range  $37 < f < 43.5$  GHz.
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for absolute and relative OTA ACLR tests can be derived from values captured in tables 11.3.7-1 to 11.3.7-4, derived based on the expanded uncertainty  $u_e$  ( $1.96\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA ACLR test requirement.
+
+**Table 11.3.7-1: Test system specific MU values for the absolute OTA ACLR, Normal test conditions, FR1**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 1.15                            | 1.30                       | 1.30                       |
+| Compact Antenna Test Range                             | 1.39                            | 1.51                       | 1.51                       |
+| Near Field Test Range                                  | 1.26                            | 1.33                       | 1.33                       |
+| Plane Wave Synthesizer                                 | 1.24                            | 1.40                       | 1.49                       |
+| Reverberation Chamber                                  | 1.37                            | 1.46                       | 1.46                       |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.2</b>                      | <b>2.7</b>                 | <b>2.7</b>                 |
+
+**Table 11.3.7-2: Test system specific MU values for the relative OTA ACLR, Normal test conditions, FR1**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | -                               | -                          | -                          |
+| Compact Antenna Test Range                             | 1.12                            | 1.30                       | 1.30                       |
+| Near Field Test Range                                  | -                               | -                          | -                          |
+| Plane Wave Synthesizer                                 | 1.02                            | 1.22                       | 1.29                       |
+| Reverberation Chamber                                  | 1.37                            | 1.46                       | 1.46                       |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.0</b>                      | <b>1.2</b>                 | <b>1.2</b>                 |
+
+**Table 11.3.7-3: Test system specific MU values for the absolute OTA ACLR, Normal test conditions, FR2**
+
+|  | Expanded uncertainty $u_e$ (dB) |                     |                       |
+|--|---------------------------------|---------------------|-----------------------|
+|  | $24.25 < f < 29.5$ GHz          | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+|  |                                 |                     |                       |
+
+|                                                        |            |            |            |
+|--------------------------------------------------------|------------|------------|------------|
+| Indoor Anechoic Chamber                                |            |            | -          |
+| Compact Antenna Test Range                             | 2.69       | 2.71       | -          |
+| Near Field Test Range                                  |            |            | -          |
+| Reverberation Chamber                                  | 2.36       | 2.36       | -          |
+| Plane Wave Synthesizer                                 |            |            | -          |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.7</b> | <b>2.7</b> | <b>2.9</b> |
+
+**Table 11.3.7-4: Test system specific MU values for the relative OTA ACLR, Normal test conditions, FR2**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                     |                       |
+|--------------------------------------------------------|---------------------------------|---------------------|-----------------------|
+|                                                        | $24.25 < f < 29.5$ GHz          | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+| Indoor Anechoic Chamber                                | -                               | -                   | -                     |
+| Compact Antenna Test Range                             | 2.28                            | 2.54                | -                     |
+| Near Field Test Range                                  | -                               | -                   | -                     |
+| Reverberation Chamber                                  | 2.15                            | 2.36                | -                     |
+| Plane Wave Synthesizer                                 | -                               | -                   | -                     |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.3</b>                      | <b>2.6</b>          | <b>2.8 (NOTE)</b>     |
+
+NOTE: MU estimation for  $43.5 < f < 48.2$  GHz was derived based on the linear approximation (based on MU values for lower frequency ranges). MU extrapolation approach was used instead of the typical derivation of the Expanded MU based on the MU budget calculations, as in case of lower frequency ranges.
+
+For relative ACLR, the MU value was agreed to be 1.0 dB for 0 – 3 GHz bands and 1.2 dB for 3 – 6 GHz bands. The MU in 4.2 - 6 GHz is valid for BS designed to operate in licensed spectrum.
+
+For absolute ACLR, the MU value was agreed to be 2.2 dB for 0 – 3 GHz bands and 2.7 dB for 3 – 6 GHz bands. The MU in 4.2 - 6 GHz is valid for BS designed to operate in licensed spectrum.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+### 11.3.8 Test Tolerance for OTA ACLR
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA ACLR were derived based on values captured in clause 11.3.7.
+
+For FR1:
+
+- For relative ACLR, the TT was agreed to be the same as the MU.
+- For absolute ACLR, the TT was agreed to be 0 dB.
+
+For FR2: The TT was agreed to be the same as the MU.
+
+Frequency range specific Test Tolerance values for the OTA ACLR test are defined in tables 11.3.8-1 to 11.3.8-4.
+
+**Table 11.3.8-1: Test Tolerance values for the absolute OTA ACLR, Normal test conditions, FR1**
+
+|                     | $f \leq 3$ GHz | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|----------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (dB) | 0              | 0                                        | 0                                        |
+
+**Table 11.3.8-2: Test Tolerance values for the relative OTA ACLR, Normal test conditions, FR1**
+
+|                     | $f \leq 3$ GHz | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|----------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (dB) | 1.0            | 1.2                                      | 1.2                                      |
+
+**Table 11.3.8-3: Test Tolerance values for the absolute OTA ACLR, Normal test conditions, FR2**
+
+|                        | 24.25 < f <<br>29.5 GHz | 37 < f < 43.5<br>GHz | 43.5 < f < 48.2<br>GHz |
+|------------------------|-------------------------|----------------------|------------------------|
+| Test Tolerance<br>(dB) | 2.7                     | 2.7                  | 2.9                    |
+
+**Table 11.3.8-4: Test Tolerance values for the relative OTA ACLR, Normal test conditions, FR2**
+
+|                        | 24.25 < f <<br>29.5 GHz | 37 < f < 43.5<br>GHz | 43.5 < f < 48.2<br>GHz |
+|------------------------|-------------------------|----------------------|------------------------|
+| Test Tolerance<br>(dB) | 2.3                     | 2.6                  | 2.8                    |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 11.4 OTA SEM and OTA OBUE
+
+### 11.4.1 General
+
+Clause 11.4 captures MU and TT values derivation for the OTA operating band unwanted emission (OBUE) *TRP requirement*, as well as the OTA spectrum emission mask (SEM) in Normal test conditions.
+
+### 11.4.2 Indoor Anechoic Chamber
+
+#### 11.4.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.2.1, with the Indoor Anechoic Chamber measurement system setup depicted on figure 7.2.1-1.
+
+NOTE: Whilst the TRP estimation does not require far-field conditions explicitly the MU budget below is based on errors under far-field conditions. If far-field conditions are not met an in-door anechoic chamber may be used but a separate MU analysis is necessary.
+
+#### 11.4.2.2 Test procedure
+
+##### 11.4.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Indoor Anechoic Chamber is captured in clause 8.2 with the calibration system setup for TX requirements depicted in figure 8.2-1.
+
+Calibration shall be performed individually for each frequency at which unwanted emissions are measured. This may involve calibration measurement or interpolation between calibration points.
+
+##### 11.4.2.2.2 Stage 2: BS measurement
+
+Reference IAC procedure in clause 11.2.2.2.2 (i.e. the same procedure as for OTA BS output power measurement in IAC).
+
+The appropriate parameters in step 4 is the mean power for OBUE or SEM test for each carrier arriving at the measurement equipment connector D (figure 7.2.1-1), denoted by  $P_{R\_OBUE\_D}$  or  $P_{R\_SEM\_D}$ , and calculation of EIRP<sub>e</sub> using following formulas:
+
+$$EIRP_e = P_{R\_OBUE\_D} + L_{TX\_cal, A \rightarrow D}$$
+
+$$EIRP_e = P_{R\_SEM\_D} + L_{TX\_cal, A \rightarrow D}$$
+
+### 11.4.2.3 MU value derivation, FR1
+
+Table 11.4.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA OBUE or OTA SEM measurements in Indoor Anechoic Chamber (Normal test conditions, FR1).
+
+**Table 11.4.2.3-1: IAC MU value derivation for OTA OBUE or OTA SEM measurement, FR1**
+
+| UID                                     | Uncertainty source                                                                            | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                         |                                                                                               | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-1                                    | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03            | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| A1-2                                    | Pointing misalignment between the BS and the receiving antenna                                | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| A1-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4a                                   | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5a                                   | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                    | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-1                                    | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)       | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A1-7                                    | Impedance mismatch in the receiving chain                                                     | 0.14                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.10                                     | 0.23            | 0.23            |
+| A1-8                                    | Random uncertainty                                                                            | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                               |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A1-9                                    | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-10                                   | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-11                                   | Impedance mismatch between the reference antenna and the network analyzer.                    | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04            | 0.04            |
+| A1-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10            | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A1-4b                                   | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01            | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A1-5b                                   | Mutual coupling between the reference antenna and the receiving antenna                       | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A1-6                                    | Phase curvature                                                                               | 0.05                   | 0.05            | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05            | 0.05            |
+| C1-3                                    | Uncertainty of the network analyzer                                                           | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A1-12                                   | Influence of the reference antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A1-13                                   | Reference antenna feed cable loss measurement uncertainty                                     | 0.06                   | 0.06            | 0.06            | Gaussian                        | 1.00                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A1-14                                   | Influence of the receiving antenna feed cable                                                 | 0.05                   | 0.05            | 0.05            | Rectangular                     | 1.73                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| C1-4                                    | Uncertainty of the absolute gain of the reference antenna                                     | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A1-15                                   | Uncertainty of the absolute gain of the receiving antenna                                     | 0.00                   | 0.00            | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00            | 0.00            |
+
+|                                                                                          |             |             |             |
+|------------------------------------------------------------------------------------------|-------------|-------------|-------------|
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         | <b>0.44</b> | <b>0.54</b> | <b>0.54</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> | <b>0.87</b> | <b>1.06</b> | <b>1.06</b> |
+| <b>TRP summation error</b>                                                               | <b>0.75</b> | <b>0.75</b> | <b>0.75</b> |
+| <b>Total MU</b>                                                                          | <b>1.15</b> | <b>1.30</b> | <b>1.30</b> |
+
+## 11.4.3 Compact Antenna Test Range
+
+### 11.4.3.1 Measurement system description
+
+Measurement system description is captured in clause 7.3.1, with the Compact Antenna Test Range measurement system setup depicted on figure 8.3-1.
+
+### 11.4.3.2 Test procedure
+
+#### 11.4.3.2.1 Stage 1: Calibration
+
+Calibration should be carried out using the same procedure as in 8.3.
+
+Calibration shall be performed individually for each frequency at which unwanted emissions are measured. This may involve calibration measurement or interpolation between calibration points.
+
+NOTE: This stage may be omitted provided calibration stage has been performed already during BS output power measurement.
+
+#### 11.4.3.2.2 Stage 2: BS measurement
+
+Reference CATR procedure in clause 11.2.3.2.2 (i.e. the same procedure as for OTA BS output power).
+
+The appropriate parameters in step 4 is the mean power for OBUE or SEM test for each carrier arriving at the measurement equipment connector B (figure 7.3.1-1), denoted by  $P_{R\_OBUE\_B}$  or  $P_{R\_SEM\_B}$ , and calculation of  $power_e$  is done using following formulas:
+
+$$power_e = P_{R\_OBUE\_B} + L_{TX\_cal, A \rightarrow B}$$
+
+$$power_e = P_{R\_SEM\_B} + L_{TX\_cal, A \rightarrow B}$$
+
+### 11.4.3.3 MU value derivation, FR1
+
+Table 11.4.3.3-1 captures derivation of the expanded measurement uncertainty values for OTA OBUE or OTA SEM measurements in CATR (Normal test conditions, FR1).
+
+**Table 11.4.3.3-1: CATR MU value derivation for OTA OBUE or OTA SEM measurement, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A2-18a                                                                 | Misalignment and pointing error of BS (for TRP)                                         | 0.30                   | 0.30            | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17            | 0.17            |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                         | 0.21                   | 0.21            | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                             | 0.09                   | 0.09            | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09            | 0.09            |
+| A2-12                                                                  | Frequency flatness of test system                                                       | 0.25                   | 0.25            | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20            | 0.20            |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver           | 0.13                   | 0.33            | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23            | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                        | 0.18                   | 0.18            | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)   | 0.00                   | 0.00            | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                         | 0.02                   | 0.02            | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02            | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                               | 0.50                   | 0.43            | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25            | 0.25            |
+| A2-8                                                                   | Misalignment positioning system                                                         | 0.00                   | 0.00            | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00            | 0.00            |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                       | 0.50                   | 0.50            | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25            | 0.25            |
+| A2-9                                                                   | Rotary joints                                                                           | 0.05                   | 0.05            | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03            | 0.03            |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                        | 0.09                   | 0.09            | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                            | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| A2-11                                                                  | Switching uncertainty                                                                   | 0.26                   | 0.26            | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.59</b>                              | <b>0.67</b>     | <b>0.67</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.16</b>                              | <b>1.31</b>     | <b>1.31</b>     |
+| <b>TRP summation error</b>                                             |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.39</b>                              | <b>1.51</b>     | <b>1.51</b>     |
+
+### 11.4.3.4 MU value derivation, FR2
+
+A CATR MU budget was assessed in order to determine acceptable MU for the EIRP accuracy measurement in FR2. The CATR test setup and calibration and measurement procedures for FR2 are expected to be similar to those of FR1,
+
+although the test chamber dimensions and associated MU values will scale due to the shorter wavelengths and larger relative array apertures. However, it is noted that in order to achieve the test instrument uncertainties that were assumed, calibration of the spectrum analyzer may be needed.
+
+Table 11.4.3.4-1 captures derivation of the expanded measurement uncertainty values for OTA OBUE measurements in CATR (Normal test conditions, FR2).
+
+**Table 11.4.3.4-1: CATR MU value derivation for OTA OBUE measurement, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                                       | Uncertainty value (dB) |                   | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                   |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-------------------|
+|                                                                        |                                                                                                                          | 24.25 < f ≤ 29.5 GHz   | 37 < f ≤ 43.5 GHz |                                 |                                     |                | 24.25 < f ≤ 29.5 GHz                     | 37 < f ≤ 43.5 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                          |                        |                   |                                 |                                     |                |                                          |                   |
+| A2-18a                                                                 | Misalignment and pointing error of BS (for TRP)                                                                          | 0.30                   | 0.30              | Exp. normal                     | 2.00                                | 1              | 0.15                                     | 0.15              |
+| C1-7                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.90                   | 0.90              | Gaussian                        | 1.00                                | 1              | 0.90                                     | 0.90              |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                                                          | 0.03                   | 0.03              | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02              |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                                                              | 0.40                   | 0.40              | Gaussian                        | 1.00                                | 1              | 0.40                                     | 0.40              |
+| A2-12                                                                  | Frequency flatness of test system                                                                                        | 0.25                   | 0.25              | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25              |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                          |                        |                   |                                 |                                     |                |                                          |                   |
+| C1-3                                                                   | Uncertainty of the Network Analyzer                                                                                      | 0.30                   | 0.30              | Gaussian                        | 1.00                                | 1              | 0.30                                     | 0.30              |
+| A2-5b                                                                  | Mismatch of receiver chain for low power receiver                                                                        | 0.72                   | 0.72              | U-shaped                        | 1.41                                | 1              | 0.51                                     | 0.51              |
+| A2-6                                                                   | Insertion loss in receiver chain                                                                                         | 0.00                   | 0.00              | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00              |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                                                          | 0.21                   | 0.29              | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.21              |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                                | 0.52                   | 0.52              | Rectangular                     | 1.73                                | 1              | 0.30                                     | 0.30              |
+| A2-8                                                                   | Misalignment positioning system                                                                                          | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                                                        | 0.00                   | 0.00              | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00              |
+| A2-9                                                                   | Rotary joints                                                                                                            | 0.00                   | 0.00              | U-shaped                        | 1.41                                | 1              | 0.00                                     | 0.00              |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                                                         | 0.09                   | 0.09              | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06              |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                                                             | 0.01                   | 0.01              | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01              |
+| A2-11                                                                  | Switching uncertainty                                                                                                    | 0.10                   | 0.10              | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06              |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                          |                        |                   |                                 |                                     |                | <b>1.23</b>                              | <b>1.24</b>       |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                        |                   |                                 |                                     |                | <b>2.42</b>                              | <b>2.44</b>       |
+| <b>TRP summation error</b>                                             |                                                                                                                          |                        |                   |                                 |                                     |                | <b>1.20</b>                              | <b>1.20</b>       |
+| <b>Total MU</b>                                                        |                                                                                                                          |                        |                   |                                 |                                     |                | <b>2.70</b>                              | <b>2.72</b>       |
+
+## 11.4.4 Near Field Test Range
+
+### 11.4.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.5.1.
+
+In case of OTA OBUE measurement, NF to FF transform is not needed since TRP is computed based on power density measured in Near Field by sampling properly the power density for OBUE or SEM.
+
+### 11.4.4.2 Test procedure
+
+#### 11.4.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Near Field Test Range is captured in clause 8.5.
+
+#### 11.4.4.2.2 Stage 2: BS measurement
+
+Refer to clause 11.2.4.2.2 (i.e. same procedure as for OTA BS output power in the NFTR). The measured power in step 3 is the power density for OBUE or SEM test for each carrier arriving at the measurement equipment connector.
+
+### 11.4.4.3 MU value derivation, FR1
+
+Refer to clause 11.2.4.3 (i.e. the MU value derivation for the OTA BS output power measurement in NFTR) for MU value per point measurement.
+
+## 11.4.5 Reverberation Chamber
+
+### 11.4.5.1 Measurement system description
+
+Measurement system description is captured in clause 7.7.1.
+
+### 11.4.5.2 Test procedure
+
+#### 11.4.5.2.1 Stage 1: Calibration
+
+Calibration procedure for the Reverberation chamber is captured in clause 8.7.
+
+#### 11.4.5.2.2 Stage 2: BS measurement
+
+The RC test procedure is described in clause 11.2.5.2.2 (i.e. the same procedure as for the OTA BS output power).
+
+### 11.4.5.3 MU value derivation, FR1
+
+Table 11.4.5.3-1 captures derivation of the expanded measurement uncertainty values for OTA OBUE or OTA SEM measurement in Reverberation chamber (Normal test conditions, FR1).
+
+**Table 11.4.5.3-1: Reverberation chamber MU value derivation for OTA OBUE or OTA SEM measurement, FR1**
+
+| UID                                                                    | Uncertainty source                                                                      | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                                         | f ≤ 3 G Hz             | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-1                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26            | 0.26            | Gaussian                        | 1.00                                | 1              | 0.14                                     | 0.26            | 0.26            |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                               | 0.20                   | 0.20            | 0.20            | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.14            | 0.14            |
+| A6-2                                                                   | Random uncertainty                                                                      | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                  | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                          | 0.15                   | 0.15            | 0.15            | Gaussian                        | 1.00                                | 1              | 0.15                                     | 0.15            | 0.15            |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                     | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                           | 0.20                   | 0.20            | 0.20            | Gaussian                        | 1.00                                | 1              | 0.20                                     | 0.20            | 0.20            |
+| A6-6                                                                   | Mean value estimation of transfer function                                              | 0.27                   | 0.27            | 0.27            | Gaussian                        | 1.00                                | 1              | 0.27                                     | 0.27            | 0.27            |
+| A6-7                                                                   | Uniformity of transfer function                                                         | 0.50                   | 0.50            | 0.50            | Gaussian                        | 1.00                                | 1              | 0.50                                     | 0.50            | 0.50            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>0.71</b>                              | <b>0.75</b>     | <b>0.75</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |                 |                 |                                 |                                     |                | <b>1.40</b>                              | <b>1.46</b>     | <b>1.46</b>     |
+
+#### 11.4.5.4 MU value derivation, FR2
+
+Table 11.4.5.4-1 captures derivation of the expanded measurement uncertainty values for OTA OBUE measurements in Reverberation chamber (Normal test conditions, FR2).
+
+**Table 11.4.5.4-1: Reverberation chamber MU value derivation for OTA OBUE measurement, FR2**
+
+| UID                                                                                      | Uncertainty source                                                                                                       | Uncertainty value (dB)    |                        | Distribution of the probability | Divisor based on distribution shape | $c_i$ | Standard uncertainty $u_i$ (dB) |                        |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------|---------------------------------|-------------------------------------|-------|---------------------------------|------------------------|
+|                                                                                          |                                                                                                                          | $24.25 < f \leq 29.5$ GHz | $37 < f \leq 43.5$ GHz |                                 |                                     |       | $24.25 < f \leq 29.5$ GHz       | $37 < f \leq 43.5$ GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                                                                                          |                           |                        |                                 |                                     |       |                                 |                        |
+| C1-7                                                                                     | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.90                      | 0.90                   | Gaussian                        | 1.00                                | 1     | 0.90                            | 0.90                   |
+| A6-1                                                                                     | Impedance mismatch in the receiving chain                                                                                | 0.20                      | 0.20                   | U-shaped                        | 1.41                                | 1     | 0.14                            | 0.14                   |
+| A6-2                                                                                     | Random uncertainty                                                                                                       | 0.10                      | 0.10                   | Rectangular                     | 1.73                                | 1     | 0.06                            | 0.06                   |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                                                                                          |                           |                        |                                 |                                     |       |                                 |                        |
+| A6-3                                                                                     | Reference antenna radiation efficiency                                                                                   | 0.30                      | 0.30                   | Gaussian                        | 1.00                                | 1     | 0.30                            | 0.30                   |
+| A6-4                                                                                     | Mean value estimation of reference antenna mismatch efficiency                                                           | 0.27                      | 0.27                   | Gaussian                        | 1.00                                | 1     | 0.27                            | 0.27                   |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                                                                      | 0.30                      | 0.30                   | Gaussian                        | 1.00                                | 0.3   | 0.30                            | 0.30                   |
+| A6-5                                                                                     | Influence of the reference antenna feed cable                                                                            | 0.20                      | 0.20                   | Gaussian                        | 1.00                                | 1     | 0.20                            | 0.20                   |
+| A6-6                                                                                     | Mean value estimation of transfer function                                                                               | 0.27                      | 0.27                   | Gaussian                        | 1.00                                | 1     | 0.27                            | 0.27                   |
+| A6-7                                                                                     | Uniformity of transfer function                                                                                          | 0.50                      | 0.50                   | Gaussian                        | 1.00                                | 1     | 0.50                            | 0.50                   |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                                                                          |                           |                        |                                 |                                     |       | <b>1.20</b>                     | <b>1.20</b>            |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                           |                        |                                 |                                     |       | <b>2.36</b>                     | <b>2.36</b>            |
+
+## 11.4.6 Plane Wave Synthesizer
+
+### 11.4.6.1 Measurement system description
+
+Measurement system description is captured in clause 7.6.1.
+
+### 11.4.6.2 Test procedure
+
+#### 11.4.6.2.1 Stage 1: Calibration
+
+Calibration procedure for the Plane Wave Synthesizer is captured in clause 8.6.
+
+NOTE: This stage may be omitted provided calibration stage has been performed already during OTA BS output power measurement.
+
+Calibration shall be performed individually for each frequency at which unwanted emissions are measured. This may involve calibration measurement or interpolation between calibration points.
+
+#### 11.4.6.2.2 Stage 2: BS measurement
+
+Reference PWS procedure in clause 11.2.6.2.2 (i.e. the same procedure as for OTA BS output power in PWS).
+
+The appropriate parameters in step 3 is the mean power for OBUE or SEM test for each carrier arriving at the measurement equipment connector C (figure 7.6.1-1), denoted by  $P_{R\_OBUE\_C}$  or  $P_{R\_SEM\_C}$ , and calculation of EIRP<sub>e</sub> is done using following formulas:
+
+$$EIRP_e = P_{R\_OBUE\_C} + L$$
+
+$$EIRP_e = P_{R\_SEM\_C} + L$$
+
+### 11.4.6.3 MU value derivation, FR1
+
+The MU value for OTA OBUE or OTA SEM in PWS is the same as in clause 11.2.6.3 (i.e. OTA BS output power MU in PWS).
+
+## 11.4.7 Maximum accepted test system uncertainty
+
+For the frequency range up to 4.2 GHz, the same MU values as for E-UTRA were adopted. It is expected that the test chamber setup, calibration and measurement procedures for E-UTRA and NR will be highly similar. All uncertainty factors were judged to be the same.
+
+For the frequency range 4.2 - 6 GHz, all MU factors, including instrumentation related MU were judged to be the same as for the 3 - 4.2 GHz range, and thus the total MU for 4.2 – 6 GHz is the same as for 3 - 4.2 GHz. This assessment was made under the assumption of testing BS designed for licensed spectrum; for unlicensed spectrum the MU may differ.
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values.
+
+According to the methodology referred above, the common maximum accepted test system uncertainty values for OTA OBUE or OTA SEM test can be derived from values captured in tables 11.4.7-1 and 11.4.7-2, derived based on the expanded uncertainty  $u_e$  (1.96 $\sigma$  - confidence interval of 95 %) values. The common maximum accepted test system uncertainty values are applicable for all test methods addressing OTA OBUE or OTA SEM test requirement.
+
+**Table 11.4.7-1: Test system specific MU values for the OTA OBUE or OTA SEM measurement, FR1**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                            |                            |
+|--------------------------------------------------------|---------------------------------|----------------------------|----------------------------|
+|                                                        | $f \leq 3$ GHz                  | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz |
+| Indoor Anechoic Chamber                                | 1.15                            | 1.30                       | 1.30                       |
+| Compact Antenna Test Range                             | 1.39                            | 1.51                       | 1.51                       |
+| Near Field Test Range                                  | 1.26                            | 1.33                       | 1.33                       |
+| Plane Wave Synthesizer                                 | 1.24                            | 1.40                       | 1.49                       |
+| Reverberation Chamber                                  | 1.40                            | 1.46                       | 1.46                       |
+| <b>Common maximum accepted test system uncertainty</b> | <b>1.8</b>                      | <b>2.0</b>                 | <b>2.0</b>                 |
+
+**Table 11.4.7-2: Test system specific MU values for the OTA OBUE measurement, FR2**
+
+|                                                        | Expanded uncertainty $u_e$ (dB) |                     |                       |
+|--------------------------------------------------------|---------------------------------|---------------------|-----------------------|
+|                                                        | $24.25 < f < 29.5$ GHz          | $37 < f < 43.5$ GHz | $43.5 < f < 48.2$ GHz |
+| Indoor Anechoic Chamber                                | -                               | -                   | -                     |
+| Compact Antenna Test Range                             | 2.70                            | 2.72                | -                     |
+| Near Field Test Range                                  | -                               | -                   | -                     |
+| Reverberation Chamber                                  | 2.36                            | 2.36                | -                     |
+| Plane Wave Synthesizer                                 | -                               | -                   | -                     |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.7</b>                      | <b>2.7</b>          | <b>2.9</b>            |
+
+The MU value was agreed to be 1.4 dB for up to 3 GHz bands and 1.5 dB for 3 – 6 GHz bands. The MU in 4.2-6 GHz is valid for BS designed to operate in licensed spectrum.
+
+For CATR the expanded MU is established as a root sum square combining of the dB values for the MU and the SE (see clause 6.3.6), the MU was decided to be 2.7 dB for the frequency range  $24.25 < f < 29.5$  GHz and 2.7 dB for the frequency range  $37 < f < 43.5$  GHz.
+
+An overview of the MU values for all the requirements is captured in clause 17.
+
+## 11.4.8 Test Tolerance for OTA OBUE and OTA SEM
+
+Considering the methodology described in clause 5.1, Test Tolerance values for OTA OBUE and OTA SEM were derived based on values captured in clause 11.4.7.
+
+NOTE: For OTA SEM, TT values up to 4.2 GHz apply.
+
+FR1: The TT value was agreed to be the same as the MU value for 0 - 10 MHz from the carrier and 0 dB for >10 MHz from the carrier.
+
+FR2: The TT value was agreed to be the same as the MU (i.e. 2.7 dB) for 0 - 10% of the BS channel bandwidth away from the carrier, and 0 dB for >10% of BS channel bandwidth from the carrier.
+
+Frequency range specific Test Tolerance values for the OTA OBUE and OTA SEM test in FR1 are defined in table 11.4.8-1.
+
+Frequency range specific Test Tolerance values for the OTA OBUE test in FR2 are defined in table 11.4.8-2.
+
+**Table 11.4.8-1: Test Tolerance values for the OTA OBUE and OTA SEM, Normal test conditions, FR1**
+
+|                     | $f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 \text{ GHz} < f \leq 6 \text{ GHz}$ |
+|---------------------|------------------------|------------------------------------------|------------------------------------------|
+| Test Tolerance (dB) | 1.8                    | 2.0                                      | 2.0                                      |
+
+**Table 11.4.8-2: Test Tolerance values for the OTA OBUE, Normal test conditions, FR2**
+
+|                     | $24.25 < f < 29.5 \text{ GHz}$ | $37 < f < 43.5 \text{ GHz}$ | $43.5 < f < 48.2 \text{ GHz}$ |
+|---------------------|--------------------------------|-----------------------------|-------------------------------|
+| Test Tolerance (dB) | 2.7                            | 2.7                         | 2.9                           |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 12 Out-of-band TRP requirements
+
+### 12.1 General
+
+The TRP MU consists of a MU per-point and a *TRP summation error* (SE) which allows for errors in the calculation of the TRP from multiple directional power measurements and allows for a sparse grid to be used to reduce measurement time. The total MU is calculated as follows:
+
+Refer to clause 6.3.6 for the SE value derivation.
+
+### 12.2 Transmitter mandatory spurious emissions
+
+#### 12.2.1 General
+
+Clause 12.2 captures MU and TT values derivation for the TX mandatory spurious emissions *TRP requirement* in Normal test conditions.
+
+The conducted spurious emission requirement MU is split up into a number of frequency ranges as in table 12.2.1-1.
+
+**Table 12.2.1-1: MU values for conducted spurious emission requirement**
+
+| <b>Transmitter spurious emissions, mandatory requirements</b> | <b>MU (dB)</b> |
+|---------------------------------------------------------------|----------------|
+| $30 \text{ MHz} \leq f \leq 4 \text{ GHz}$                    | 2.0            |
+| $4 \text{ GHz} < f \leq 19 \text{ GHz}$                       | 4.0            |
+
+The conducted analysis based on UTRA/E-UTRA frequencies which were all below 4.2 GHz (at the time), the break point in the MU is hence somewhat related to the in-band and out-of-band MU analysis. As in-band MU analysis is now being done up to 6 GHz (for the LAA and NR bands) it is sensible to change the frequency break point to 6 GHz.
+
+The spurious emission requirements cover a large frequency range from 30 MHz to 26 GHz, many of the chambers chosen for analysis cannot cover this entire range. The MU analysis is therefore based on a General Chamber analysis (see 7.7.3) rather than any specific OTA chamber. Other chambers may of course be used as long as the MU is within the specified value (or the test requirement is offset appropriately) and they are suitable for the frequencies being tested.
+
+The spurious emissions requirements of the *BS type 2-O* are between 30 MHz to the 2<sup>nd</sup> harmonic of the DL operating band. Currently the upper frequency limit calculated MU is 60 GHz.
+
+This range can be split into a number of regions:
+
+### **30 MHz < f ≤ 6 GHz**
+
+This region also exists in FR1, the same MU is assumed for FR2 and for FR1.
+
+### **6 GHz < f ≤ 18 GHz**
+
+This is also an FR1 region however the MU values assumed in FR1 is larger than the in-band MU for FR2 which is at a higher frequency. An FR2 BS will likely be smaller than an FR1 BS and hence the chamber can be smaller and the requirements on the quiet zone can be relaxed. In addition, the test equipment is suitable for much higher frequencies (FR2 in band is above the frequency range) implying a low uncertainty. The MU in the region therefore is assumed to be the same as the FR2 in-band MU.
+
+### **18 GHz < f ≤ 43.5 GHz**
+
+This frequency range covers the FR2 in-band region. The in-band MU budget is found in clause 11.2.5.4.
+
+### **43.5 GHz < f ≤ 60 GHz**
+
+This frequency range is above the in-band region, the measured frequencies are above the measurement frequency of the test equipment and hence a mixer is used to down convert the measured frequency to within the range of the test equipment.
+
+It is not necessary to measure TRP in the far field as a large enough range may be impractical for the frequency range being considered.
+
+## **12.2.2 General Chamber**
+
+### **12.2.2.1 Measurement system description**
+
+As the BS antenna radiating dimensions are fixed then the far field distance increases ( $FF \approx 2d^2/\lambda$ ). At 12.75 GHz the far field distance for a 1.5 m BS *antenna array* is almost 200 m, this is clearly impractical in an indoor chamber (and the path loss would also make measurement difficult), so spurious emission testing will not always be in the far field. This is acceptable as the requirement is TRP and hence it is not necessary to measure in the far field however it needs to be considered when looking at MU.
+
+Considerations of the large frequency range must also be considered, including the chamber performance (quiet zone), the calibration effectiveness and the available reference and test antennas over the frequency range.
+
+Measurement system description is captured in clause 7.7.3.
+
+### **12.2.2.2 Test procedure**
+
+#### **12.2.2.2.1 Stage 1: Calibration**
+
+Calibration procedure for the General Chamber is captured in clause 8.7A.
+
+NOTE: The calibration for the out-of-band measurements should be repeated for each frequency being tested and each test antenna.
+
+#### **12.2.2.2.2 Stage 2: BS measurement**
+
+The General Chamber testing procedure consists of the following steps:
+
+- 1) Place the BS at the positioner.
+- 2) Align the manufacturer declared coordinate system orientation of the BS with the test system.
+- 3) Measurements shall use appropriate measurement bandwidth.
+- 4) The measurement device characteristics shall be: Detection mode: True RMS.
+- 5) Set the BS to transmit according to the applicable test configuration
+- 6) Align the BS and the test antenna such that measurements to determine TRP can be performed (see clause 6.3.3 for the TRP measurement procedures).
+- 7) Measure the emission at the specified frequencies with specified measurement bandwidth.
+- 8) Repeat step 6 - 7 for all directions in the appropriated TRP measurement grid needed for full TRP estimation (see clause 6.3.3 for the TRP measurement procedures) and for frequency points to be tested.
+
+NOTE 1: The TRP measurement grid may not be the same for all measurement frequencies.
+
+NOTE 2: The frequency sweep or the TRP measurement grid sweep may be done in any order.
+
+- 9) Calculate TRP at each specified frequency using the directional measurements.
+
+### 12.2.2.3 MU value derivation, FR1
+
+For FR1 a General Chamber and Reverberation Chamber were analysed for the MU derivation. Table 12.2.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA TX spurious emissions measurements in General Chamber (Normal test conditions, FR1).
+
+**Table 12.2.2.3-1: General Chamber MU value derivation for the TX spurious emissions, FR1**
+
+| UID                                     | Uncertainty source                                                                            | Uncertainty value (dB) |                    |                     | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                    |                     |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|--------------------|---------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|--------------------|---------------------|
+|                                         |                                                                                               | 30 MHz < f ≤ 6 GHz     | 6 GHz < f ≤ 19 GHz | 19 GHz < f ≤ 26 GHz |                                 |                                     |                | 30 MHz < f ≤ 6 GHz                       | 6 GHz < f ≤ 19 GHz | 19 GHz < f ≤ 26 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                               |                        |                    |                     |                                 |                                     |                |                                          |                    |                     |
+| A5-1                                    | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03               | 0.03                | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02               | 0.02                |
+| A5-2                                    | Pointing misalignment between the BS and the receiving antenna                                | 0.00                   | 0.00               | 0.00                | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00               | 0.00                |
+| A5-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10               | 0.10                | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10               | 0.10                |
+| A5-4a                                   | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01               | 0.01                | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01               | 0.01                |
+| A5-5a                                   | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00               | 0.00                | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00               | 0.00                |
+| A5-6a                                   | Phase curvature across the BS antenna                                                         | 0.05                   | 0.05               | 0.05                | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05               | 0.05                |
+| C3-3                                    | Transmitter mandatory spurious emissions - Conducted Uncertainty (minus miss match)           | 1.00                   | 2.00               | 2.00                | Gaussian                        | 1.00                                | 1              | 1.00                                     | 2.00               | 2.00                |
+| A5-7                                    | Impedance mismatch in the receiving chain                                                     | 0.20                   | 0.45               | 0.45                | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.32               | 0.32                |
+| A5-8                                    | Random uncertainty                                                                            | 0.10                   | 0.10               | 0.10                | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06               | 0.06                |
+| A5-17                                   | Measurement antenna frequency variation                                                       | 0.10                   | 0.10               | 0.10                | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06               | 0.06                |
+| A5-18                                   | FSPL estimation error                                                                         | 0.00                   | 0.00               | 0.00                | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00               | 0.00                |
+| A5-16                                   | Frequency flatness of test system                                                             | 0.25                   | 0.25               | 0.25                | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25               | 0.25                |
+| <b>Stage 1: Calibration measurement</b> |                                                                                               |                        |                    |                     |                                 |                                     |                |                                          |                    |                     |
+| A5-9                                    | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05               | 0.05                | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04               | 0.04                |
+| A5-10                                   | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01               | 0.01                | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01               | 0.01                |
+
+|                                                                                          |                                                                               |      |      |      |             |      |   |             |             |             |
+|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------|------|------|-------------|------|---|-------------|-------------|-------------|
+| A5-11                                                                                    | Impedance mismatch between the reference antenna and the network analyzer.    | 0.05 | 0.05 | 0.05 | U-shaped    | 1.41 | 1 | 0.04        | 0.04        | 0.04        |
+| A5-3                                                                                     | Quality of quiet zone                                                         | 0.10 | 0.10 | 0.10 | Gaussian    | 1.00 | 1 | 0.10        | 0.10        | 0.10        |
+| A5-4b                                                                                    | Polarization mismatch between the reference antenna and the receiving antenna | 0.01 | 0.01 | 0.01 | Rectangular | 1.73 | 1 | 0.01        | 0.01        | 0.01        |
+| A5-5b                                                                                    | Mutual coupling between the reference antenna and the receiving antenna       | 0.00 | 0.00 | 0.00 | Rectangular | 1.73 | 1 | 0.00        | 0.00        | 0.00        |
+| A5-6b                                                                                    | Phase curvature across the reference antenna                                  | 0.05 | 0.05 | 0.05 | Gaussian    | 1.00 | 1 | 0.05        | 0.05        | 0.05        |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                           | 0.13 | 0.20 | 0.20 | Gaussian    | 1.00 | 1 | 0.13        | 0.20        | 0.20        |
+| A5-12                                                                                    | Influence of the reference antenna feed cable                                 | 0.05 | 0.05 | 0.05 | Rectangular | 1.73 | 1 | 0.03        | 0.03        | 0.03        |
+| A5-13                                                                                    | Reference antenna feed cable loss measurement uncertainty                     | 0.06 | 0.06 | 0.06 | Gaussian    | 1.00 | 1 | 0.06        | 0.06        | 0.06        |
+| A5-14                                                                                    | Influence of the receiving antenna feed cable                                 | 0.05 | 0.05 | 0.05 | Rectangular | 1.73 | 1 | 0.03        | 0.03        | 0.03        |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna                     | 0.50 | 0.43 | 0.43 | Rectangular | 1.73 | 1 | 0.29        | 0.25        | 0.25        |
+| A5-15                                                                                    | Uncertainty of the absolute gain of the receiving antenna                     | 0.00 | 0.00 | 0.00 | Rectangular | 1.73 | 1 | 0.00        | 0.00        | 0.00        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                               |      |      |      |             |      |   | <b>1.11</b> | <b>2.08</b> | <b>2.08</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                               |      |      |      |             |      |   | <b>2.17</b> | <b>4.07</b> | <b>4.07</b> |
+| <b>TRP summation error</b>                                                               |                                                                               |      |      |      |             |      |   | <b>0.75</b> | <b>0.75</b> | <b>0.75</b> |
+| <b>Total MU</b>                                                                          |                                                                               |      |      |      |             |      |   | <b>2.29</b> | <b>4.14</b> | <b>4.14</b> |
+
+### 12.2.2.4 MU value derivation, FR2
+
+As opposed to FR1, for FR2 the IAC, CATR and Reverberation Chamber were analysed separately for the MU value derivation. Table 12.2.2.4-1 captures derivation of the expanded measurement uncertainty values for OTA TX spurious emissions measurements in IAC (Normal test conditions, FR2).
+
+Up to 43.5 GHz the OBUE MU values are assumed.
+
+**Table 12.2.2.4-1: IAC MU value derivation for TX spurious emissions, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                                       | Uncertainty value (dB) | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|
+|                                                                        |                                                                                                                          | 43.5 GHz < f ≤ 60 GHz  |                                 |                                     |                | 43.5 GHz < f ≤ 60 GHz                    |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| A1-1                                                                   | Positioning misalignment between the BS and the reference antenna                                                        | 0.02                   | Rectangular                     | 1.73                                | 1              | 0.01                                     |
+| A1-2                                                                   | Pointing misalignment between the BS and the receiving antenna                                                           | 0.00                   | Rectangular                     | 1.73                                | 1              | 0.00                                     |
+| A1-3                                                                   | Quality of quiet zone                                                                                                    | 0.10                   | Gaussian                        | 1.00                                | 1              | 0.10                                     |
+| A1-4a                                                                  | Polarization mismatch between the BS and the receiving antenna                                                           | 0.02                   | Rectangular                     | 1.73                                | 1              | 0.01                                     |
+| A1-5a                                                                  | Mutual coupling between the BS and the receiving antenna                                                                 | 0.00                   | Rectangular                     | 1.73                                | 1              | 0.00                                     |
+| A1-6                                                                   | Phase curvature                                                                                                          | 0.05                   | Gaussian                        | 1.00                                | 1              | 0.05                                     |
+| C1-7                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.60                   | Gaussian                        | 1.00                                | 1              | 0.60                                     |
+| A1-16                                                                  | Frequency flatness of test system                                                                                        | 0.25                   | Gaussian                        | 1.00                                | 1              | 0.25                                     |
+| A1-21                                                                  | Uncertainty of the LNA (FR2 only)                                                                                        | 0.00                   | Gaussian                        | 1.00                                | 1              | 0.00                                     |
+| A1-22                                                                  | Uncertainty of the mixer (FR2 only)                                                                                      | 2.25                   | Gaussian                        | 1.00                                | 1              | 2.25                                     |
+| A1-7                                                                   | Impedance mismatch in the receiving chain                                                                                | 0.42                   | U-shaped                        | 1.41                                | 1              | 0.30                                     |
+| A1-8                                                                   | Random uncertainty                                                                                                       | 0.10                   | Rectangular                     | 1.73                                | 1              | 0.06                                     |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| A1-9                                                                   | Impedance mismatch between the receiving antenna and the network analyzer                                                | 0.57                   | U-shaped                        | 1.41                                | 1              | 0.40                                     |
+| A1-10                                                                  | Positioning and pointing misalignment between the reference antenna and the receiving antenna                            | 0.43                   | Rectangular                     | 1.73                                | 1              | 0.25                                     |
+| A1-11                                                                  | Impedance mismatch between the reference antenna and the network analyzer.                                               | 0.57                   | U-shaped                        | 1.41                                | 1              | 0.40                                     |
+| A1-3                                                                   | Quality of quiet zone                                                                                                    | 0.10                   | Gaussian                        | 1.00                                | 1              | 0.10                                     |
+| A1-4b                                                                  | Polarization mismatch between the reference antenna and the receiving antenna                                            | 0.02                   | Rectangular                     | 1.73                                | 1              | 0.01                                     |
+| A1-5b                                                                  | Mutual coupling between the reference antenna and the receiving antenna                                                  | 0.00                   | Rectangular                     | 1.73                                | 1              | 0.00                                     |
+| A1-6                                                                   | Phase curvature                                                                                                          | 0.07                   | Gaussian                        | 1.00                                | 1              | 0.07                                     |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                                      | 0.30                   | Gaussian                        | 1.00                                | 1              | 0.30                                     |
+| A1-12                                                                  | Influence of the reference antenna feed cable                                                                            | 0.18                   | Rectangular                     | 1.73                                | 1              | 0.10                                     |
+| A1-13                                                                  | Reference antenna feed cable loss measurement uncertainty                                                                | 0.10                   | Gaussian                        | 1.00                                | 1              | 0.10                                     |
+| A1-14                                                                  | Influence of the receiving antenna feed cable                                                                            | 0.18                   | Rectangular                     | 1.73                                | 1              | 0.10                                     |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                                | 0.52                   | Rectangular                     | 1.73                                | 1              | 0.30                                     |
+| A1-15                                                                  | Uncertainty of the absolute gain of the receiving antenna                                                                | 0.00                   | Rectangular                     | 1.73                                | 1              | 0.00                                     |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                          |                        |                                 |                                     |                | <b>2.49</b>                              |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                        |                                 |                                     |                | <b>4.88</b>                              |
+| <b>TRP summation error</b>                                             |                                                                                                                          |                        |                                 |                                     |                | <b>0.75</b>                              |
+| <b>Total MU</b>                                                        |                                                                                                                          |                        |                                 |                                     |                | <b>4.94</b>                              |
+
+## 12.2.3 Compact Antenna Test Range
+
+### 12.2.3.1 Measurement system description
+
+### 12.2.3.2 Test procedure
+
+#### 12.2.3.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+#### 12.2.3.2.2 Stage 2: BS measurement
+
+Reference CATR procedure in clause 11.2.3.2.2 (i.e. OTA BS output power in CATR).
+
+The appropriate parameters in step 4 is the mean power of spurious emissions test over the measurement BW described in the test requirement.
+
+### 12.2.3.3 MU value derivation, FR2
+
+Table 12.2.3.3-1 captures derivation of the expanded measurement uncertainty values for OTA TX spurious emissions measurements in CATR (Normal test conditions, FR2).
+
+**Table 12.2.3.3-1: CATR value derivation for TX spurious emissions, FR2**
+
+| UID                                                                    | Uncertainty source                                                                                                       | Uncertainty value (dB) | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|
+|                                                                        |                                                                                                                          | 43.5 GHz < f ≤ 60 GHz  |                                 |                                     |                | 43.5 GHz < f ≤ 60 GHz                    |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| A2-18a                                                                 | Misalignment and pointing error of BS (for TRP)                                                                          | 0.30                   | Exp. normal                     | 2.00                                | 1              | 0.15                                     |
+| C1-7                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.60                   | Gaussian                        | 1.00                                | 1              | 0.60                                     |
+| A2-19                                                                  | Uncertainty of the LNA (FR2 only)                                                                                        | 0.00                   | Gaussian                        | 1.00                                | 1              | 0.00                                     |
+| A2-20                                                                  | Uncertainty of the mixer (FR2 only)                                                                                      | 2.25                   | Gaussian                        | 1.00                                | 1              | 2.25                                     |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                                                          | 0.21                   | Gaussian                        | 1.00                                | 1              | 0.21                                     |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.00                   | Gaussian                        | 1.00                                | 1              | 0.00                                     |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                                                              | 0.09                   | Gaussian                        | 1.00                                | 1              | 0.09                                     |
+| A2-12                                                                  | Frequency flatness of test system                                                                                        | 0.25                   | Gaussian                        | 1.00                                | 1              | 0.25                                     |
+| A2-10                                                                  | Miscellaneous uncertainty                                                                                                | 0.00                   | Rectangular                     | 1.73                                | 1              | 0.00                                     |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                                      | 0.30                   | Gaussian                        | 1.00                                | 1              | 0.30                                     |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver                                            | 0.57                   | U-shaped                        | 1.41                                | 1              | 0.40                                     |
+| A2-5b                                                                  | Mismatch of receiver chain for low power receiver                                                                        | 0.00                   | U-shaped                        | 1.41                                | 1              | 0.00                                     |
+| A2-6                                                                   | Insertion loss of receiver chain                                                                                         | 0.18                   | Rectangular                     | 1.73                                | 1              | 0.10                                     |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated)                                    | 0.00                   | Gaussian                        | 1.00                                | 1              | 0.00                                     |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                                                          | 0.29                   | U-shaped                        | 1.41                                | 1              | 0.21                                     |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                                                                | 0.52                   | Rectangular                     | 1.73                                | 1              | 0.30                                     |
+| A2-8                                                                   | Misalignment positioning system                                                                                          | 0.00                   | Exp. normal                     | 2.00                                | 1              | 0.00                                     |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                                                        | 0.00                   | Exp. normal                     | 2.00                                | 1              | 0.00                                     |
+| A2-9                                                                   | Rotary joints                                                                                                            | 0.00                   | U-shaped                        | 1.41                                | 1              | 0.00                                     |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                                                         | 0.09                   | U-shaped                        | 1.41                                | 1              | 0.06                                     |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                                                             | 0.01                   | Gaussian                        | 1.00                                | 1              | 0.01                                     |
+| A2-11                                                                  | Switching uncertainty                                                                                                    | 0.43                   | Rectangular                     | 1.73                                | 1              | 0.25                                     |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                          |                        |                                 |                                     |                | <b>2.45</b>                              |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                        |                                 |                                     |                | <b>4.81</b>                              |
+| <b>TRP summation error</b>                                             |                                                                                                                          |                        |                                 |                                     |                | <b>1.20</b>                              |
+| <b>Total MU</b>                                                        |                                                                                                                          |                        |                                 |                                     |                | <b>4.96</b>                              |
+
+## 12.2.4 Reverberation chamber
+
+### 12.2.4.1 Measurement system description
+
+Measurement system description is captured in clause 7.7.1.
+
+## 12.2.4.2 Test procedure
+
+### 12.2.4.2.1 Stage 1: Calibration
+
+Calibration procedure for the Reverberation chamber is captured in clause 8.7.
+
+NOTE: The calibration for the out-of-band measurements should be repeated for each frequency being tested and each test antenna.
+
+### 12.2.4.2.2 Stage 2: BS measurement
+
+TRP measurement procedure for the Reverberation chamber is captured in clause 11.2.5.2.2 (i.e. OTA BS output power).
+
+## 12.2.4.3 MU value derivation
+
+Table 12.2.3.4-1 captures derivation of the expanded measurement uncertainty values for OTA TX spurious emissions measurements in Reverberation Chamber (Normal test conditions).
+
+**Table 12.2.4.3-1: Reverberation Chamber value derivation for TX spurious emissions, 380 MHz – 26 GHz**
+
+| UI D                                                                   | Uncertainty source                                                                      | Uncertainty value (dB) |               |                  |                   |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |               |                  |                   |                 |
+|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|------------------------|---------------|------------------|-------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|---------------|------------------|-------------------|-----------------|
+|                                                                        |                                                                                         | 380 MHz < z ≤ 3 GHz    | 3 < f ≤ 6 GHz | 6 < f ≤ 12.7 GHz | 12.7 < f ≤ 19 GHz | 19 < f ≤ 26 GHz |                                 |                                     |                | 380 MHz < z ≤ 3 GHz                      | 3 < f ≤ 6 GHz | 6 < f ≤ 12.7 GHz | 12.7 < f ≤ 19 GHz | 19 < f ≤ 26 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                         |                        |               |                  |                   |                 |                                 |                                     |                |                                          |               |                  |                   |                 |
+| C1 -1                                                                  | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) | 0.14                   | 0.26          | 0.26             | 0.37              | 0.37            | Gaussian                        | 1.00                                | 1.00           | 0.14                                     | 0.26          | 0.26             | 0.37              | 0.37            |
+| A6 -1                                                                  | Impedance mismatch in the receiving chain                                               | 0.20                   | 0.20          | 0.45             | 0.45              | 0.45            | U-shaped                        | 1.41                                | 1.00           | 0.14                                     | 0.14          | 0.32             | 0.32              | 0.32            |
+| A6 -2                                                                  | Random uncertainty                                                                      | 0.10                   | 0.10          | 0.10             | 0.1               | 0.10            | Rectangular                     | 1.73                                | 1.00           | 0.06                                     | 0.06          | 0.06             | 0.06              | 0.06            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                         |                        |               |                  |                   |                 |                                 |                                     |                |                                          |               |                  |                   |                 |
+| A6 -3                                                                  | Reference antenna radiation efficiency                                                  | 0.50                   | 0.50          | 0.50             | 0.5               | 0.50            | Gaussian                        | 1.00                                | 1.00           | 0.50                                     | 0.50          | 0.50             | 0.50              | 0.50            |
+| A6 -4                                                                  | Mean value estimation of reference antenna mismatch efficiency                          | 0.27                   | 0.27          | 0.27             | 0.27              | 0.27            | Gaussian                        | 1.00                                | 1.00           | 0.27                                     | 0.27          | 0.27             | 0.27              | 0.27            |
+| C1 -3                                                                  | Uncertainty of the network analyzer                                                     | 0.13                   | 0.20          | 0.20             | 0.2               | 0.20            | Gaussian                        | 1.00                                | 1.00           | 0.13                                     | 0.20          | 0.20             | 0.20              | 0.20            |
+| A6 -5                                                                  | Influence of the reference antenna feed cable                                           | 0.20                   | 0.20          | 0.20             | 0.2               | 0.20            | Gaussian                        | 1.00                                | 1.00           | 0.20                                     | 0.20          | 0.20             | 0.20              | 0.20            |
+| A6 -6                                                                  | Mean value estimation of transfer function                                              | 0.27                   | 0.27          | 0.27             | 0.27              | 0.27            | Gaussian                        | 1.00                                | 1.00           | 0.27                                     | 0.27          | 0.27             | 0.27              | 0.27            |
+| A6 -7                                                                  | Uniformity of transfer function                                                         | 1.50                   | 1.50          | 1.50             | 1.5               | 1.50            | Gaussian                        | 1.00                                | 1.00           | 1.50                                     | 1.50          | 1.50             | 1.50              | 1.50            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                         |                        |               |                  |                   |                 |                                 |                                     |                | 1.66                                     | 1.68          | 1.70             | 1.72              | 1.72            |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                         |                        |               |                  |                   |                 |                                 |                                     |                | 3.25                                     | 3.29          | 3.34             | 3.38              | 3.38            |
+
+**Table 12.2.4.3-2: Reverberation Chamber value derivation for TX spurious emissions, 18 GHz – 60 GHz**
+
+| UID                                                                    | Uncertainty source                                                                                                       | Uncertainty value (dB) | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |
+|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|
+|                                                                        |                                                                                                                          | 43.5 GHz < f ≤ 60 GHz  |                                 |                                     |                | 43.5 GHz < f ≤ 60 GHz                    |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| C1-7                                                                   | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM, absolute ACLR) | 0.60                   | Gaussian                        | 1.00                                | 1              | 0.60                                     |
+| A6-1                                                                   | Impedance mismatch in the receiving chain                                                                                | 0.45                   | U-shaped                        | 1.41                                | 1              | 0.32                                     |
+| A6-2                                                                   | Random uncertainty                                                                                                       | 0.10                   | Rectangular                     | 1.73                                | 1              | 0.06                                     |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                                                          |                        |                                 |                                     |                |                                          |
+| A6-3                                                                   | Reference antenna radiation efficiency                                                                                   | 0.50                   | Normal                          | 1.00                                | 1              | 0.50                                     |
+| A6-4                                                                   | Mean value estimation of reference antenna mismatch efficiency                                                           | 0.27                   | Normal                          | 1.00                                | 1              | 0.27                                     |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                                                      | 0.30                   | Gaussian                        | 1.00                                | 1              | 0.30                                     |
+| A6-5                                                                   | Influence of the reference antenna feed cable                                                                            | 0.20                   | Normal                          | 1.00                                | 1              | 0.20                                     |
+| A6-6                                                                   | Mean value estimation of transfer function                                                                               | 0.27                   | Normal                          | 1.00                                | 1              | 0.27                                     |
+| A6-7                                                                   | Uniformity of transfer function                                                                                          | 1.50                   | Normal                          | 1.00                                | 1              | 1.50                                     |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                                                          |                        |                                 |                                     |                | <b>1.80</b>                              |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                                                          |                        |                                 |                                     |                | <b>3.53</b>                              |
+
+## 12.2.5 Maximum accepted test system uncertainty
+
+Considering the methodology described in clause 5.1, maximum accepted test system uncertainty values for OTA transmitter spurious emissions were derived based on values captured in clauses 12.2.1 to 12.2.4.
+
+Frequency range specific Test Tolerance values for the OTA TX spurious emissions test are defined in tables 12.2.5-1 and 12.2.5-2.
+
+Hence, we have the following MU values for the whole spurious emissions range (for FR1 and FR2 cases):
+
+**Table 12.2.5-1: Spurious emissions MU values – FR1**
+
+|                                                        | Expanded uncertainty (dB) |                    |                     |
+|--------------------------------------------------------|---------------------------|--------------------|---------------------|
+|                                                        | 30 MHz < f ≤ 6 GHz        | 6 GHz < f ≤ 19 GHz | 19 GHz < f ≤ 26 GHz |
+| General Chamber                                        | 2.29                      | 4.14               | 4.14                |
+| Reverberation Chamber                                  | 3.29                      | 3.38               | 3.38                |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.30</b>               | <b>4.20</b>        | <b>4.20</b>         |
+
+For FR2 only the frequency range 43.5 GHz < f ≤ 60 GHz has been considered in this clause, the other frequency ranges are common with existing FR1 and FR2 in-band TRP emissions measurements:
+
+- 30 MHz < f ≤ 6 GHz: the MU values are the same as for FR1,
+- 6 GHz < f ≤ 43.5 GHz: the MU values are the same as the in-band TRP emission measurements in clause 11.2.
+
+**Table 12.2.5-2: Spurious emissions MU values – FR2**
+
+|                                                        | Expanded uncertainty (dB) |                      |                       |
+|--------------------------------------------------------|---------------------------|----------------------|-----------------------|
+|                                                        | 30 MHz < f ≤ 6 GHz        | 6 GHz < f ≤ 43.5 GHz | 43.5 GHz < f ≤ 60 GHz |
+| General Chamber                                        | x                         | x                    | 4.94                  |
+| Compact Antenna Test Range                             | x                         | x                    | 4.96                  |
+| Reverberation Chamber                                  | x                         | x                    | 3.53                  |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.5</b>                | <b>2.7</b>           | <b>5</b>              |
+
+## 12.2.6 Test Tolerance for OTA TX spurious emissions
+
+The conducted test tolerance for the mandatory spurious emissions requirements is zero. As the requirements are set by regulatory limits the same test tolerance is used for OTA.
+
+TT = 0.
+
+## 12.3 Receiver spurious emissions
+
+### 12.3.1 General
+
+Clause 12.3 captures MU and TT values derivation for the RX spurious emissions *TRP requirement* in Normal test conditions.
+
+The conducted receiver spurious emission requirement MU is the same as for the TX spurious emissions, the measurement technique is the same and the power level is > -60 dBm (where there is a break point for conducted power measurement accuracy), so this is reasonable.
+
+For the OTA receiver emissions requirements however the lower power level of the requirement reduces the dynamic range of the TRP measurement and reduces measurement accuracy.
+
+Considering that the loss in the chamber is based on the wanted signal being in the far field the per point noise floor is assumed to be approx. -100 dBm and the receiver emissions level translated to the test equipment is approx. -90 dBm. Hence the TRP calculation has only a 10 dB dynamic range.
+
+An uncertainty of 1 dB is added to the TRP uncertainty budget to account for this additional uncertainty.
+
+### 12.3.2 General Chamber
+
+#### 12.3.2.1 Measurement system description
+
+As the BS antenna radiating dimensions are fixed then the far field distance increases ( $FF \approx 2d^2/\lambda$ ). At 12.75 GHz the far field distance for a 1.5 m BS *antenna array* is almost 200 m, this is clearly impractical in an indoor chamber (and the path loss would also make measurement difficult), so spurious emission testing will not always be in the far field. This is acceptable as the requirement is TRP and hence it is not necessary to measure in the far field however it needs to be considered when looking at MU.
+
+Considerations of the large frequency range must also be considered, including the chamber performance (quiet zone), the calibration effectiveness and the available reference and test antennas over the frequency range.
+
+Measurement system description is captured in clause 7.7.3.
+
+#### 12.3.2.2 Test procedure
+
+##### 12.3.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the General Chamber is captured in clause 8.7A.
+
+NOTE: The calibration for the out-of-band measurements should be repeated for each frequency being tested and each test antenna.
+
+#### 12.3.2.2.2 Stage 2: BS measurement
+
+The General Chamber measurement procedure is the same as described in clause 12.2.2.2.2 (i.e. OTA TX spurious emissions in General Chamber).
+
+#### 12.3.2.3 MU value derivation, FR1
+
+Table 12.3.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA RX spurious emissions measurements in General Chamber (Normal test conditions, FR1).
+
+**Table 12.3.2.3-1: General Chamber MU value derivation for RX spurious emissions, FR1**
+
+| UID                                     | Uncertainty source                                                                            | Uncertainty value (dB) |                |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                |                 |
+|-----------------------------------------|-----------------------------------------------------------------------------------------------|------------------------|----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|----------------|-----------------|
+|                                         |                                                                                               | 30 MHz < f ≤ 6 GHz     | 6 < f ≤ 19 GHz | 19 < f ≤ 26 GHz |                                 |                                     |                | 30 MHz < f ≤ 6 GHz                       | 6 < f ≤ 19 GHz | 19 < f ≤ 26 GHz |
+| <b>Stage 2: BS measurement</b>          |                                                                                               |                        |                |                 |                                 |                                     |                |                                          |                |                 |
+| A5-1                                    | Positioning misalignment between the BS and the reference antenna                             | 0.03                   | 0.03           | 0.03            | Rectangular                     | 1.73                                | 1              | 0.02                                     | 0.02           | 0.02            |
+| A5-2                                    | Pointing misalignment between the BS and the receiving antenna                                | 0.00                   | 0.00           | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00           | 0.00            |
+| A5-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10           | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10           | 0.10            |
+| A5-4a                                   | Polarization mismatch between the BS and the receiving antenna                                | 0.01                   | 0.01           | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01           | 0.01            |
+| A5-5a                                   | Mutual coupling between the BS and the receiving antenna                                      | 0.00                   | 0.00           | 0.00            | Rectangular                     | 1.73                                | 1              | 0.00                                     | 0.00           | 0.00            |
+| A5-6a                                   | Phase curvature across the BS antenna                                                         | 0.05                   | 0.05           | 0.05            | Gaussian                        | 1.00                                | 1              | 0.05                                     | 0.05           | 0.05            |
+| C3-4                                    | Receiver spurious emissions - Conducted Uncertainty (minus mismatch)                          | 1.00                   | 2.00           | 2.00            | Gaussian                        | 1.00                                | 1              | 1.00                                     | 2.00           | 2.00            |
+| A5-7                                    | Impedance mismatch in the receiving chain                                                     | 0.20                   | 0.45           | 0.45            | U-shaped                        | 1.41                                | 1              | 0.14                                     | 0.32           | 0.32            |
+| A5-8                                    | Random uncertainty                                                                            | 0.10                   | 0.10           | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06           | 0.06            |
+| A5-17                                   | Measurement antenna frequency variation                                                       | 0.10                   | 0.10           | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06           | 0.06            |
+| A5-18                                   | FSPL estimation error                                                                         | 0.00                   | 0.00           | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00           | 0.00            |
+| A5-16                                   | Frequency flatness of test system                                                             | 0.25                   | 0.25           | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25           | 0.25            |
+| A5-19                                   | Measurement system dynamic range uncertainty                                                  | 0.51                   | 0.51           | 0.51            | Gaussian                        | 1.00                                | 1              | 0.51                                     | 0.51           | 0.51            |
+| <b>Stage 1: Calibration measurement</b> |                                                                                               |                        |                |                 |                                 |                                     |                |                                          |                |                 |
+| A5-9                                    | Impedance mismatch between the receiving antenna and the network analyzer                     | 0.05                   | 0.05           | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04           | 0.04            |
+| A5-10                                   | Positioning and pointing misalignment between the reference antenna and the receiving antenna | 0.01                   | 0.01           | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01           | 0.01            |
+| A5-11                                   | Impedance mismatch between the reference antenna and the network analyzer.                    | 0.05                   | 0.05           | 0.05            | U-shaped                        | 1.41                                | 1              | 0.04                                     | 0.04           | 0.04            |
+| A5-3                                    | Quality of quiet zone                                                                         | 0.10                   | 0.10           | 0.10            | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10           | 0.10            |
+| A5-4b                                   | Polarization mismatch between the reference antenna and the receiving antenna                 | 0.01                   | 0.01           | 0.01            | Rectangular                     | 1.73                                | 1              | 0.01                                     | 0.01           | 0.01            |
+
+|                                                                                          |                                                                         |      |      |      |             |      |   |             |             |             |
+|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|------|------|------|-------------|------|---|-------------|-------------|-------------|
+| A5-5b                                                                                    | Mutual coupling between the reference antenna and the receiving antenna | 0.00 | 0.00 | 0.00 | Rectangular | 1.73 | 1 | 0.00        | 0.00        | 0.00        |
+| A5-6b                                                                                    | Phase curvature across the reference antenna                            | 0.05 | 0.05 | 0.05 | Gaussian    | 1.00 | 1 | 0.05        | 0.05        | 0.05        |
+| C1-3                                                                                     | Uncertainty of the network analyzer                                     | 0.13 | 0.20 | 0.20 | Gaussian    | 1.00 | 1 | 0.13        | 0.20        | 0.20        |
+| A5-12                                                                                    | Influence of the reference antenna feed cable                           | 0.05 | 0.05 | 0.05 | Rectangular | 1.73 | 1 | 0.03        | 0.03        | 0.03        |
+| A5-13                                                                                    | Reference antenna feed cable loss measurement uncertainty               | 0.06 | 0.06 | 0.06 | Gaussian    | 1.00 | 1 | 0.06        | 0.06        | 0.06        |
+| A5-14                                                                                    | Influence of the receiving antenna feed cable                           | 0.05 | 0.05 | 0.05 | Rectangular | 1.73 | 1 | 0.03        | 0.03        | 0.03        |
+| C1-4                                                                                     | Uncertainty of the absolute gain of the reference antenna               | 0.50 | 0.43 | 0.43 | Rectangular | 1.73 | 1 | 0.29        | 0.25        | 0.25        |
+| A5-15                                                                                    | Uncertainty of the absolute gain of the receiving antenna               | 0.00 | 0.00 | 0.00 | Rectangular | 1.73 | 1 | 0.00        | 0.00        | 0.00        |
+| <b>Combined standard uncertainty (<math>1\sigma</math>) (dB)</b>                         |                                                                         |      |      |      |             |      |   | <b>1.22</b> | <b>2.14</b> | <b>2.14</b> |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                                         |      |      |      |             |      |   | <b>2.39</b> | <b>4.19</b> | <b>4.19</b> |
+| <b>TRP summation error</b>                                                               |                                                                         |      |      |      |             |      |   | <b>0.75</b> | <b>0.75</b> | <b>0.75</b> |
+| <b>Total MU</b>                                                                          |                                                                         |      |      |      |             |      |   | <b>2.50</b> | <b>4.25</b> | <b>4.25</b> |
+
+### 12.3.3 Maximum accepted test system uncertainty
+
+The TRP MU is very similar to that for the transmitter mandatory spurious emissions. However, the receiver requirements are at a much lower power level so TRP calculation may be affected by the noise floor of the measurement system.
+
+For FR2 the following MU are calculated.
+
+**Table 12.3.3-1: Receiver spurious emissions MU values – FR1**
+
+|                                                        | <b>Expanded uncertainty (dB)</b>                           |                                                            |                                                             |
+|--------------------------------------------------------|------------------------------------------------------------|------------------------------------------------------------|-------------------------------------------------------------|
+|                                                        | <b><math>30\text{ MHz} &lt; f \leq 6\text{ GHz}</math></b> | <b><math>6\text{ GHz} &lt; f \leq 19\text{ GHz}</math></b> | <b><math>19\text{ GHz} &lt; f \leq 26\text{ GHz}</math></b> |
+| General Chamber                                        | 2.50                                                       | 4.25                                                       | 4.25                                                        |
+| Reverberation Chamber                                  | -                                                          | -                                                          | -                                                           |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.50</b>                                                | <b>4.20</b>                                                | <b>4.20</b>                                                 |
+
+For FR2 the out of band frequency range is much larger, the range can be split into a number of regions:
+
+#### **$30\text{ MHz} < f \leq 6\text{ GHz}$**
+
+The same value is assumed for receiver spurious emissions as for transmitter spurious emissions. This is the same as the in band FR2 MU value.
+
+#### **$6\text{ GHz} < f \leq 18\text{ GHz}$**
+
+The same value is assumed for receiver spurious emissions as for transmitter spurious emissions. This is the same as the in band FR2 MU value.
+
+#### **$18\text{ GHz} < f \leq 43.5\text{ GHz}$**
+
+The same value is assumed for receiver spurious emissions as for transmitter spurious emissions. This is calculated in clause 12.2.5.
+
+#### 43.5 GHz < f ≤ 60 GHz
+
+The same value is assumed for receiver spurious emissions as for transmitter spurious emissions. This is calculated in clause 12.2.5.
+
+**Table 12.3.3-2: Receiver spurious emissions MU values**
+
+| Frequency range       | MU (dB) |
+|-----------------------|---------|
+| 30 MHz < f ≤ 6 GHz    | 2.5     |
+| 6 GHz < f ≤ 18 GHz    | 2.7     |
+| 18 GHz < f ≤ 43.5 GHz | 2.7     |
+| 43.5 GHz < f ≤ 60 GHz | 5       |
+
+### 12.3.4 Test Tolerance for OTA RX spurious emissions
+
+The conducted test tolerance for the receiver spurious emissions requirements is zero. However for OTA BS the receiver spurious emissions requirements only apply to TTD in OFF mode. As such the limit is set by RAN4 to be considerably lower than the equivalent regulatory requirement.
+
+In addition due to the difficulty in measuring low levels of TRP close to the measurement system noise floor the risk of false failures is high. As the risk is due to the noise floor of the measurement system it cannot be mitigated by BS design.
+
+Hence it has been agreed that for receiver spurious emissions the TT = MU.
+
+From December 2019, the regulation around receiver spurious emissions has been clarified in ERC recommendation 74-01 [25] and the requirement has been updated. Since then OTA RX spurious emissions is a regulatory requirement with TT = 0.
+
+## 12.4 Additional (co-existence) spurious emissions
+
+### 12.4.1 General
+
+Clause 12.4 captures MU and TT values derivation for the additional (co-existence) spurious emission *TRP requirement* in Normal test conditions.
+
+The additional spurious emissions requirements consist of the co-existence emissions requirements, and some additional regional requirements such as the protection of PHS and 700 and 800 public safety.
+
+The conducted MU are consistent with the mandatory spurious emissions MU.
+
+The test set up for the OTA additional emissions requirements is the same as that for the mandatory spurious emissions in clause 12.2.1. However, the additional spurious emissions are at a much lower level than the mandatory requirements so the additional effect of the test system dynamic range must be considered in the same way as the receiver emissions requirements.
+
+Unlike the other spurious emissions requirements the additional (co-existence) requirements are specified for other 3GPP bands and as such can be measured in the same chambers as the in-band measurements.
+
+As the CATR MU budget results is the largest MU and is used for setting the in-band MU values only the CATR MU is analysed below. However any suitable IAC or NFTR chamber can be used.
+
+## 12.4.2 Compact Antenna Test Range
+
+### 12.4.2.1 Measurement system description
+
+The CATR method only is described as it provides the worst MU budget for the additional requirements MU analysis.
+
+Measurement system description is captured in clause 7.3.1, with the Compact Antenna Test Range measurement system setup depicted on figure 8.3-1.
+
+### 12.4.2.2 Test procedure
+
+#### 12.4.2.2.1 Stage 1: Calibration
+
+Calibration procedure for the Compact Antenna Test Range is captured in clause 8.3.
+
+NOTE: The calibration for the out-of-band measurements should be repeated for each frequency being tested and each test antenna.
+
+#### 12.4.2.2.2 Stage 2: BS measurement
+
+Reference CATR procedure in clause 11.2.3.2.2 (i.e. OTA BS output power in CATR).
+
+The appropriate parameters in step 4 is the mean power of additional spurious emissions test over the measurement BW described in the test requirement.
+
+### 12.4.2.3 MU value derivation, FR1
+
+Table 12.4.2.3-1 captures derivation of the expanded measurement uncertainty values for additional (co-existence) OTA TX spurious emissions measurements in CATR (Normal test conditions, FR1).
+
+**Table 12.4.2.3-1: CATR MU value derivation for additional (co-existence) OTA TX spurious emissions**
+
+| UID                                                                    | Uncertainty source                                                                    | Uncertainty value (dB) |                  |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|------------------------------------------------------------------------|---------------------------------------------------------------------------------------|------------------------|------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                                                        |                                                                                       | f ≤ 3 G Hz             | 3 < f ≤ 4.2 G Hz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 G Hz                               | 3 < f ≤ 4.2 G Hz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                                       |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| A2-18a                                                                 | Misalignment and pointing error of BS (for TRP)                                       | 0.30                   | 0.30             | 0.30            | Rectangular                     | 1.73                                | 1              | 0.17                                     | 0.17             | 0.17            |
+| C3-5                                                                   | Additional (COEX) emissions - Conducted Uncertainty (minus mismatch)                  | 1.02                   | 1.28             | 1.53            | Gaussian                        | 1.00                                | 1              | 1.02                                     | 1.28             | 1.53            |
+| A2-2a                                                                  | Standing wave between BS and test range antenna                                       | 0.21                   | 0.21             | 0.21            | U-shaped                        | 1.41                                | 1              | 0.15                                     | 0.15             | 0.15            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.00                   | 0.00             | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A2-4a                                                                  | QZ ripple experienced by BS                                                           | 0.09                   | 0.09             | 0.09            | Gaussian                        | 1.00                                | 1              | 0.09                                     | 0.09             | 0.09            |
+| A2-17                                                                  | Measurement system dynamic range uncertainty                                          | 0.51                   | 0.51             | 0.51            | Gaussian                        | 1.00                                | 1              | 0.51                                     | 0.51             | 0.51            |
+| A2-12                                                                  | Frequency flatness of test system                                                     | 0.25                   | 0.25             | 0.25            | Gaussian                        | 1.00                                | 1              | 0.25                                     | 0.25             | 0.25            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                                       |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| C1-3                                                                   | Uncertainty of the network analyzer                                                   | 0.13                   | 0.20             | 0.20            | Gaussian                        | 1.00                                | 1              | 0.13                                     | 0.20             | 0.20            |
+| A2-5a                                                                  | Mismatch of receiver chain between receiving antenna and measurement receiver         | 0.13                   | 0.33             | 0.33            | U-shaped                        | 1.41                                | 1              | 0.09                                     | 0.23             | 0.23            |
+| A2-6                                                                   | Insertion loss of receiver chain                                                      | 0.18                   | 0.18             | 0.18            | Rectangular                     | 1.73                                | 1              | 0.10                                     | 0.10             | 0.10            |
+| A2-3                                                                   | RF leakage (SGH connector terminated & test range antenna connector cable terminated) | 0.00                   | 0.00             | 0.00            | Gaussian                        | 1.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A2-7                                                                   | Influence of the calibration antenna feed cable                                       | 0.02                   | 0.02             | 0.02            | U-shaped                        | 1.41                                | 1              | 0.02                                     | 0.02             | 0.02            |
+| C1-4                                                                   | Uncertainty of the absolute gain of the reference antenna                             | 0.50                   | 0.43             | 0.43            | Rectangular                     | 1.73                                | 1              | 0.29                                     | 0.25             | 0.25            |
+| A2-8                                                                   | Misalignment positioning system                                                       | 0.00                   | 0.00             | 0.00            | Exp. normal                     | 2.00                                | 1              | 0.00                                     | 0.00             | 0.00            |
+| A2-1b                                                                  | Misalignment and pointing error of calibration antenna (for EIRP)                     | 0.50                   | 0.50             | 0.50            | Exp. normal                     | 2.00                                | 1              | 0.25                                     | 0.25             | 0.25            |
+| A2-9                                                                   | Rotary joints                                                                         | 0.05                   | 0.05             | 0.05            | U-shaped                        | 1.41                                | 1              | 0.03                                     | 0.03             | 0.03            |
+| A2-2b                                                                  | Standing wave between calibration antenna and test range antenna                      | 0.09                   | 0.09             | 0.09            | U-shaped                        | 1.41                                | 1              | 0.06                                     | 0.06             | 0.06            |
+| A2-4b                                                                  | QZ ripple experienced by calibration antenna                                          | 0.01                   | 0.01             | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01             | 0.01            |
+| A2-11                                                                  | Switching uncertainty                                                                 | 0.26                   | 0.26             | 0.26            | Rectangular                     | 1.73                                | 1              | 0.15                                     | 0.15             | 0.15            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                                       |                        |                  |                 |                                 |                                     |                | <b>1.28</b>                              | <b>1.51</b>      | <b>1.73</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                                       |                        |                  |                 |                                 |                                     |                | <b>2.51</b>                              | <b>2.96</b>      | <b>3.38</b>     |
+| <b>TRP summation error</b>                                             |                                                                                       |                        |                  |                 |                                 |                                     |                | <b>0.75</b>                              | <b>0.75</b>      | <b>0.75</b>     |
+| <b>Total MU</b>                                                        |                                                                                       |                        |                  |                 |                                 |                                     |                | <b>2.62</b>                              | <b>3.05</b>      | <b>3.47</b>     |
+
+## 12.4.3 Maximum accepted test system uncertainty
+
+The additional spurious emission requirements including the co-existence with other BS in the same geographical area are based on existing co-existence with other 3GPP bands so the frequency ranges for the uncertainty assessment are
+
+different from the mandatory spurious emissions. In this case the uncertainty budgets for the in-band chambers are considered in the MU analysis. As the TRP level is at a low power level the measurement system dynamic range uncertainty is also considered as with the receiver spurious emissions.
+
+**Table 12.4.3-1: Test system specific MU values for the additional (co-existence) spurious emissions measurement**
+
+|                                                        | Expanded uncertainty (dB) |                     |                 |
+|--------------------------------------------------------|---------------------------|---------------------|-----------------|
+|                                                        | 30 MHz < f ≤ 3 GHz        | 3 GHz < f ≤ 4.2 GHz | 4.2 < f < 6 GHz |
+| Compact Antenna Test Range                             | 2.62                      | 3.05                | 3.47            |
+| <b>Common maximum accepted test system uncertainty</b> | <b>2.60</b>               | <b>3.00</b>         | <b>3.50</b>     |
+
+NOTE: There are currently no additional spurious emissions requirements or co-existence requirements for FR2.
+
+## 12.4.4 Test Tolerance for additional spurious emissions requirements
+
+The conducted test tolerance for the additional spurious emissions requirements is zero.
+
+However for OTA BS, the difficulty in measuring TRP of the additional spurious emissions requirements at low levels close to the measurement system noise floor means the high risk of false failures. As the risk is due to the noise floor of the measurement system it cannot be mitigated by BS design.
+
+As the 3GPP to 3GPP co-existence requirements are not regulatory but set by RAN4 to assist with co-existence of 3GPP systems in the same geographical area it is acceptable for RAN4 to set the TT value to be non-zero.
+
+Hence it has been agreed that for 3GPP to 3GPP co-existence spurious emissions the TT = MU.
+
+**Table 12.4.4-1: TT values for the additional (coexistence) spurious emissions measurement**
+
+|                     | 30 MHz < f ≤ 3 GHz | 3 GHz < f ≤ 4.2 GHz | 4.2 < f < 6 GHz |
+|---------------------|--------------------|---------------------|-----------------|
+| Test Tolerance (dB) | 1.8                | 2.0                 |                 |
+
+For PHS, and public safety additional requirements the TT = 0 dB.
+
+Some additional requirements such as the protection of PHS and the 700 and 800 MHz public safety bands, are regulatory so it is not possible to have a non-zero TT, hence for these requirements the TT is zero.
+
+# 13 Co-location requirements
+
+## 13.1 General
+
+This clause collects information on the co-location requirement procedures in General Chamber, as described in clause 7.7.1.
+
+## 13.2 OTA transmitter OFF power
+
+### 13.2.1 General
+
+This clause captures MU and TT values derivation for the OTA transmitter OFF power co-location requirement in Normal test conditions.
+
+OTA transmitter ON/OFF power requirements apply only to TDD operation.
+
+The OTA transmit ON/OFF power requirements are co-location requirements and specified as the power sum of the supported polarization(s) at the CLTA conducted output(s).
+
+The FR1 transmitter OFF power and transmitter transient period is a co-location requirement while the FR2 transmitter OFF power requirement is a directional requirement.
+
+It is not possible to separate OTA emissions from separate *transceiver units* therefore OTA emissions requirements are specified as the sum of the emissions from all *transceiver units* in the BS. For spurious emissions this has been the case for both conducted and OTA emissions. The sum of the total emissions from the BS is intended to be no greater than that of a non-AAS system with equivalent number of MIMO branches and hence emission are capped at a level consistent with the maximum MIMO capability of the appropriate RAT (i.e. 8 for E-UTRA and NR, 4 for UTRA), however conducted TX OFF level is specified per *TAB connector* and as such is not subject to the same cap. However as the conducted requirement is primarily concerned with protection of your own receiver and OTA is concerned with co-location the parameters have somewhat changed.
+
+As a co-located TDD receiver should be offered the same protection as any other co-located receiver it is reasonable to apply the same cap on the TX OFF level as is applied to other unwanted emissions.
+
+The FR1 transmitter OFF power is measured as the conducted output of the CLTA, no accurate measurements are required in the chamber itself. The MU analysis of the TX OFF measurement is therefore agnostic to the chamber used. The chambers main purpose is to shield the BS and the CLTA form external interference which may influence the result and to avoid RF reflections which may alter the coupling between the BS and the CLTA.
+
+Hence the MU analysis for FR1 TX OFF is done using a "General chamber" under the assumption that any of the chambers discussed (with the exception of the Reverb chamber) will be suitable.
+
+## 13.2.2 General Chamber
+
+### 13.2.2.1 Measurement system description
+
+The General Chamber description for co-location requirements is intended to cover any suitable chamber type which screens the measurement system for outside interference and does not affect the coupling between the BS and the CLTA.
+
+Measurement system description is captured in clause 7.7.1.
+
+### 13.2.2.2 Test procedure
+
+#### 13.2.2.2.1 Stage 1: Calibration
+
+Calibration for wanted signal power level is the same as in clause 9.2.
+
+Calibration for the CLTA path is described in clause 8.8.
+
+#### 13.2.2.2.2 Stage 2: measurement
+
+The testing procedure consists of the following steps:
+
+- 1) Place BS and CLTA as specified for the co-location requirement in TS 37.145-2 [4] clause 4.15 for AAS BS, and in TS 38.141-2 [6] clause 4.12 for NR BS.
+- 2) Place range antenna in boresight direction (reference direction) at far-field distance, aligned in both polarizations with the BS.
+- 3) The Range antenna shall be dual (or single) polarized with the same frequency range as the BS for transmitter OFF power test case.
+- 4) Connect range antenna and CLTA to the measurement equipment.
+- 5) OTA transmitter OFF power is measured at the CLTA conducted output(s).
+- 6) The measurement device (signal analyser) characteristics shall be: Detection mode: True RMS.
+
+## 7) Set the BS to transmit:
+
+- For BS declared to be capable of single carrier operation only, set the BS to transmit full beam power (rated beam EIRP), both polarizations, in boresight direction (reference direction), at manufacturer's declared rated output power,  $P_{\text{rated,t,TRP}}$ .
+- For BS declared to be capable of multi-carrier and/or CA operation, set the BS to transmit full beam power (rated beam EIRP), both polarizations, in boresight direction (reference direction) on all carriers configured using the applicable test configuration and corresponding power setting.
+- Check that specified beam power (EIRP) is obtained at range antenna RF output(s) (conducted side) for each polarization. Re-align if the specified beam power is not achieved.
+
+8) Measure the mean power spectral density from all CLTA conducted output(s) over 70  $\mu\text{s}$  filtered with a square filter of bandwidth equal to the RF bandwidth of the RIB centred on the central frequency of the RF bandwidth. 70  $\mu\text{s}$  average window centre is set from 35  $\mu\text{s}$  after end of one *transmitter ON period* + 17  $\mu\text{s}$  to 35  $\mu\text{s}$  before start of next *transmitter ON period* - 6.25  $\mu\text{s}$ .
+
+Additional factor to be considered in the measurement is that the test requirement is very close to thermal noise floor, and the measurement setup needs to be able to tolerate both very high and low signal levels. This will impact measurement uncertainty.
+
+## 13.2.2.3 MU value derivation, FR1
+
+Table 13.2.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA TX OFF power measurements in General Chamber (Normal test conditions, FR1).
+
+**Table 13.2.2.3-1: General Chamber MU value derivation for OTA TDD OFF power level measurement**
+
+| UID                                                                                      | Uncertainty source                                           | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------------------------|--------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                                          |                                                              | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                                           |                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C2-9                                                                                     | Uncertainty related to the selection of the CLTA             | 1.5                    | 1.5             | 1.5             | Rectangular                     | 1.73                                | 1              | 0.87                                     | 0.87            | 0.87            |
+| C2-10                                                                                    | Uncertainty related to the placement of the CLTA             | 1.7                    | 1.7             | 1.7             | Rectangular                     | 1.73                                | 1              | 0.98                                     | 0.98            | 0.98            |
+| C2-12                                                                                    | Uncertainty related to measuring close to noise floor Tx OFF | 1                      | 1               | 1               | Gaussian                        | 1.00                                | 1              | 1.00                                     | 1.00            | 1.00            |
+| C2-13                                                                                    | Impedance mismatch between feeder cable and CLTA             | 0.14                   | 0.23            | 0.25            | U-Shaped                        | 1.41                                | 1              | 0.10                                     | 0.16            | 0.18            |
+| C2-14                                                                                    | Gain variations in LNA                                       | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A5-8                                                                                     | Random uncertainty                                           | 0.1                    | 0.1             | 0.1             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-5                                                                                     | Measurement receiver (co-location)                           | 0.41                   | 0.74            | 0.8             | Gaussian                        | 1.00                                | 1              | 0.41                                     | 0.74            | 0.80            |
+| A5-20                                                                                    | Reflections in anechoic chamber                              | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| C2-15                                                                                    | Gain variations in measurement amplifier                     | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| <b>Stage 1: Calibration measurement</b>                                                  |                                                              |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-6                                                                                     | Noise figure measurement accuracy                            | 0.2                    | 0.2             | 0.2             | Gaussian                        | 1.00                                | 1              | 0.2                                      | 0.2             | 0.2             |
+| <b>Combined standard uncertainty (1<math>\sigma</math>) (dB)</b>                         |                                                              |                        |                 |                 |                                 |                                     |                | <b>1.72</b>                              | <b>1.83</b>     | <b>1.86</b>     |
+| <b>Expanded uncertainty (1.96<math>\sigma</math> - confidence interval of 95 %) (dB)</b> |                                                              |                        |                 |                 |                                 |                                     |                | <b>3.37</b>                              | <b>3.59</b>     | <b>3.64</b>     |
+
+UID are referenced to annex A, B or C as appropriate.
+
+### 13.2.3 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values in clause 13.2.2.
+
+**Table 13.2.3-1: Common maximum accepted test system uncertainty value derivation for TDD OFF power level measurement**
+
+|                                                        | Expanded uncertainty (dB) |                      |                      |
+|--------------------------------------------------------|---------------------------|----------------------|----------------------|
+|                                                        | $f \leq 3$ GHz            | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+| General Chamber                                        | 3.37                      | 3.59                 | 3.64                 |
+| <b>Common maximum accepted test system uncertainty</b> | <b>3.40</b>               | <b>3.60</b>          | <b>3.60</b>          |
+
+Fulfilling the criteria for CLTA selection and placement in is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the CLTA and its alignment as shall be used for evaluating the test system uncertainty.
+
+### 13.2.4 Test Tolerance for OTA TX OFF power
+
+Considering the methodology described in clause 5.1, Test Tolerance values for TX OFF were derived based on values captured in clause 13.2.3.
+
+The TT was decided to be the same as the MU for TX OFF in FR1.
+
+**Table 13.2.4-1: Test Tolerance values for the TX OFF in Normal test conditions**
+
+|                     | $f \leq 3$ GHz | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+|---------------------|----------------|----------------------|----------------------|
+| Test Tolerance (dB) | 3.4            | 3.6                  | 3.6                  |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 13.3 OTA co-location spurious emissions
+
+### 13.3.1 General
+
+This clause captures MU and TT values derivation for the OTA co-location spurious emissions requirement in Normal test conditions.
+
+The FR1 OTA co-location emissions are measured as the conducted output of the CLTA, no accurate measurements are required in the chamber itself. The MU analysis of the co-location emissions measurement is therefore agnostic to the chamber used. The chambers main purpose is to shield the BS and the CLTA form external interference which may influence the result and to avoid RF reflections which may alter the coupling between the BS and the CLTA.
+
+Hence the MU analysis for FR1 co-location emissions is done using a General Chamber under the assumption that any of the chambers discussed (with the exception of the Reverberation Chamber) will be suitable.
+
+### 13.3.2 General Chamber
+
+#### 13.3.2.1 Measurement system description
+
+The General Chamber description for co-location requirements is intended to cover any suitable chamber type which screens the measurement system for outside interference and does not affect the coupling between the BS and the CLTA.
+
+Measurement system description is captured in clause 7.7.1.
+
+### 13.3.2.2 Test procedure
+
+#### 13.3.2.2.1 Stage 1: Calibration
+
+Calibration for wanted signal power level is the same as in clause 9.2.
+
+Calibration for the CLTA path is described in clause 8.8.
+
+#### 13.3.2.2.2 Stage 2: BS measurement
+
+The testing procedure consists of the following steps:
+
+- 1) Place BS and CLTA as specified in clause 4.15, TS 37.145-2 [4].
+- 2) Place range antenna in boresight direction (reference direction) at far-field distance, aligned in both polarizations with the BS.
+- 3) Connect range antenna and CLTA to the measurement equipment.
+- 4) OTA co-location spurious emissions are measured at the CLTA conducted output(s).
+- 5) The measurement device (signal analyser) characteristics shall be: Detection mode: True RMS.
+- 6) Set the BS to transmit:
+  - For BS declared to be capable of single carrier operation only, set the BS to transmit full beam power (rated beam EIRP), both polarizations, either simultaneously or sequentially, in boresight direction (reference direction), at manufacturer's declared rated output power,  $P_{\text{rated,t,TRP}}$ .
+  - For BS declared to be capable of multi-carrier and/or CA operation, set the BS to transmit full beam power (rated beam EIRP), both polarizations, in boresight direction (reference direction) on all carriers configured using the applicable test configuration and corresponding power setting.
+  - Check that specified beam power (EIRP) is obtained at Range antenna RF output(s) (conducted side) for each polarization. Re-align if the specified beam power is not achieved.
+- 7) Measure the mean power spectral density from all CLTA conducted output(s) with each wanted signal polarization under test.
+
+Additional factor to be considered in the measurement is that the test requirement is very close to thermal noise floor, and the measurement setup needs to be able to tolerate both very high and low signal levels. This will impact measurement uncertainty.
+
+### 13.3.2.3 MU value derivation, FR1
+
+Table 13.3.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA co-location spurious emissions measurements in General Chamber (Normal test conditions, FR1).
+
+**Table 13.3.2.3-1: General Chamber MU value derivation for co-location spurious emissions level measurement**
+
+| UI D                                                                   | Uncertainty source                                                | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|-------------------------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                                   | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                                   |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C2-9                                                                   | Uncertainty related to the selection of the CLTA                  | 1.5                    | 1.5             | 1.5             | Rectangular                     | 1.73                                | 1              | 0.87                                     | 0.87            | 0.87            |
+| C2-10                                                                  | Uncertainty related to the placement of the CLTA                  | 1.7                    | 1.7             | 1.7             | Rectangular                     | 1.73                                | 1              | 0.98                                     | 0.98            | 0.98            |
+| C2-11                                                                  | Uncertainty related to measuring close to noise floor - Emissions | 0.68                   | 0.68            | 0.68            | Gaussian                        | 1.00                                | 1              | 0.68                                     | 0.68            | 0.68            |
+| C2-13                                                                  | Impedance mismatch between feeder cable and CLTA                  | 0.14                   | 0.23            | 0.25            | U-Shaped                        | 1.41                                | 1              | 0.10                                     | 0.16            | 0.18            |
+| C2-14                                                                  | Gain variations in LNA                                            | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| A5-8                                                                   | Random uncertainty                                                | 0.1                    | 0.1             | 0.1             | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| C1-5                                                                   | Measurement receiver (co-location)                                | 0.41                   | 0.74            | 0.8             | Gaussian                        | 1.00                                | 1              | 0.41                                     | 0.74            | 0.80            |
+| A5-20                                                                  | Reflections in anechoic chamber                                   | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| C2-15                                                                  | Gain variations in measurement amplifier                          | 0.1                    | 0.1             | 0.1             | Gaussian                        | 1.00                                | 1              | 0.10                                     | 0.10            | 0.10            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                                   |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C1-6                                                                   | Noise figure measurement accuracy                                 | 0.2                    | 0.2             | 0.2             | Gaussian                        | 1                                   | 1              | 0.2                                      | 0.2             | 0.2             |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                                   |                        |                 |                 |                                 |                                     |                | <b>1.55</b>                              | <b>1.68</b>     | <b>1.71</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                                   |                        |                 |                 |                                 |                                     |                | <b>3.05</b>                              | <b>3.29</b>     | <b>3.34</b>     |
+
+UID are referenced to annex A, B or C as appropriate.
+
+### 13.3.3 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values in clause 13.3.2.
+
+**Table 13.3.3-1: Common maximum accepted test system uncertainty value derivation for co-location emissions level measurement**
+
+|                                                        | Expanded uncertainty (dB) |                 |                 |
+|--------------------------------------------------------|---------------------------|-----------------|-----------------|
+|                                                        | f ≤ 3 GHz                 | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| General Chamber                                        | 3.05                      | 3.29            | 3.34            |
+| <b>Common maximum accepted test system uncertainty</b> | <b>3.1</b>                | <b>3.3</b>      | <b>3.4</b>      |
+
+Fulfilling the criteria for CLTA selection and placement in is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the CLTA and its alignment as shall be used for evaluating the test system uncertainty.
+
+### 13.3.4 Test Tolerance co-location spurious emissions
+
+Considering the methodology described in clause 5.1, Test Tolerance values for co-location emissions were derived based on values captured in clause 13.3.3.
+
+The TT was decided to be the same as the MU for TX OFF in FR1.
+
+**Table 13.3.4-1: Test Tolerance values for the co-location emissions in Normal test conditions**
+
+|                     | $f \leq 3$ GHz | $3 < f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |
+|---------------------|----------------|----------------------|----------------------|
+| Test Tolerance (dB) | 3.1            | 3.3                  | 3.4                  |
+
+An overview of the TT values for all the requirements is captured in clause 18.
+
+## 13.4 OTA transmitter intermodulation
+
+### 13.4.1 General
+
+This clause captures MU and TT values derivation for the OTA transmitter intermodulation co-location requirement in Normal test conditions.
+
+The transmitter intermodulation requirement is that the spurious emissions requirements (OTA transmitter spurious emissions, OTA operating band unwanted emissions/SEM and OTA ACLR) are met whilst an interferer is injected into the antenna from a co-located bases station.
+
+The measurement method and uncertainty for those measurements is the same as described in clauses 12.2, 11.3 and 11.4.
+
+There is an additional uncertainty however associated with the accuracy of the interfering signal injected from the CLTA. It is that uncertainty which is investigated in this clause.
+
+The interferer is injected into the CLTA and the accuracy of this is not dependent on the chamber type used. The measurement uncertainty calculation is therefore done using a General Chamber type.
+
+### 13.4.2 General Chamber
+
+#### 13.4.2.1 Measurement system description
+
+This method measures the OTA TX IMD in a General Chamber.
+
+Measurement system description is captured in clause 7.7.1.
+
+#### 13.4.2.2 Test procedure
+
+##### 13.4.2.2.1 Stage 1: Calibration
+
+Calibration for the emissions measurement is the same as in clause 11.3, 11.5 and 12.2.
+
+Calibration for the CLTA path is described in clause 8.8.
+
+##### 13.4.2.2.2 Stage 2: BS measurement
+
+The General Chamber testing procedure consists of the following steps:
+
+- 1) Uninstall the reference antenna and install the BS with the manufacturer declared coordinate system reference point in the same place as the phase centre of the reference antenna. The manufacturer declared coordinate system orientation of the BS is set to be aligned with the testing system.
+
+- 2) Set the CLTA as specified in in TS 37.145-2 [4] clause 4.15 for AAS BS, and in TS 38.141-2 [6] clause 4.12 for NR BS, at the declared worst case side.
+- 3) Set the signal generator to generate the interfering signal to achieve the required level at the input port of CLTA.
+- 4) Perform required ACLR, OBUE (for E-UTRA/NR), SEM (for UTRA), occupied bandwidth, spurious emission tests according to the corresponding testing procedures.
+
+### 13.4.2.3 MU value derivation, FR1
+
+Table 13.4.2.3-1 captures derivation of the expanded measurement uncertainty values for OTA transmitter intermodulation measurements in General Chamber (Normal test conditions, FR1).
+
+**Table 13.4.2.3-1: MU for OTA transmitter intermodulation interferer signal**
+
+| UID                                                                    | Uncertainty source                               | Uncertainty value (dB) |                 |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                 |                 |
+|------------------------------------------------------------------------|--------------------------------------------------|------------------------|-----------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|-----------------|-----------------|
+|                                                                        |                                                  | f ≤ 3 GHz              | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                  |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C2-9                                                                   | Uncertainty related to the selection of the CLTA | 1.50                   | 1.50            | 1.50            | Rectangular                     | 1.73                                | 1              | 0.87                                     | 0.87            | 0.87            |
+| C2-10                                                                  | Uncertainty related to the placement of the CLTA | 1.70                   | 1.70            | 1.70            | Rectangular                     | 1.73                                | 1              | 0.98                                     | 0.98            | 0.98            |
+| C2-13                                                                  | Impedance mismatch between feeder cable and CLTA | 0.14                   | 0.23            | 0.25            | U-Shaped                        | 1.41                                | 1              | 0.10                                     | 0.16            | 0.18            |
+| A5-8                                                                   | Random uncertainty                               | 0.10                   | 0.10            | 0.10            | Rectangular                     | 1.73                                | 1              | 0.06                                     | 0.06            | 0.06            |
+| A5-20                                                                  | Reflections in anechoic chamber                  | 0.01                   | 0.01            | 0.01            | Gaussian                        | 1.00                                | 1              | 0.01                                     | 0.01            | 0.01            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                  |                        |                 |                 |                                 |                                     |                |                                          |                 |                 |
+| C3-6                                                                   | TX IMD - conducted measurement uncertainty       | 1.00                   | 1.10            | 1.20            | Gaussian                        | 1.00                                | 1              | 1.00                                     | 1.10            | 1.20            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                  |                        |                 |                 |                                 |                                     |                | <b>1.65</b>                              | <b>1.72</b>     | <b>1.79</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                  |                        |                 |                 |                                 |                                     |                | <b>3.24</b>                              | <b>3.37</b>     | <b>3.50</b>     |
+
+UID are referenced to annex A, B or C as appropriate.
+
+### 13.4.3 Maximum accepted test system uncertainty
+
+Maximum test system uncertainties derivation methodology was described in clause 5.1. The maximum accepted test system uncertainty values was derived based on test system specific values in clause 13.4.4.
+
+**Table 13.4.3-1: Common maximum accepted test system uncertainty value derivation for co-location TX IMD interferer signal level**
+
+|                                                        | Expanded uncertainty (dB) |                 |                 |
+|--------------------------------------------------------|---------------------------|-----------------|-----------------|
+|                                                        | f ≤ 3 GHz                 | 3 < f ≤ 4.2 GHz | 4.2 < f ≤ 6 GHz |
+| General Chamber                                        | 3.24                      | 3.37            | 3.50            |
+| <b>Common maximum accepted test system uncertainty</b> | <b>3.20</b>               | <b>3.40</b>     | <b>3.50</b>     |
+
+Fulfilling the criteria for CLTA selection and placement in is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the CLTA and its alignment as shall be used for evaluating the test system uncertainty.
+
+#### 13.4.4 Test Tolerance co-location spurious emissions
+
+The test tolerance for the emissions measurements (OTA transmitter spurious emissions, OTA operating band unwanted emissions/SEM and OTA ACLR) is as specified for each specific requirement.
+
+The test tolerance for the interferer level is zero.
+
+### 13.5 OTA co-location blocking
+
+#### 13.5.1 General
+
+This clause 13.5 captures MU and TT values derivation for the OTA co-location blocking requirement in Normal test conditions.
+
+The OTA co-location blocking measurement uncertainty is calculated as a combination of the wanted signal MU and the interferer signal MU in the same way as the normal out of band blocking requirement, where:
+
+The  $\text{Noise}_{\text{effect}}$  from the signal generator is 0.1 dB and the  $\text{MU}_{\text{wanted signal}}$  value is  $\text{MU}_{\text{EIS}}$  from clause 10.2.
+
+The measurement uncertainty associated with the interferer is based on the accuracy of the interfering signal injected from the CLTA. It is that uncertainty which is investigated in this clause.
+
+The interferer is injected into the CLTA and the accuracy of this is not dependent on the chamber type used. The measurement uncertainty calculation is therefore done using a General Chamber type.
+
+Any chamber capable of performing the EIS measurement to the required accuracy is suitable for the test however.
+
+#### 13.5.2 General Chamber
+
+##### 13.5.2.1 Measurement system description
+
+This method measures the OTA co-location blocking characteristics in a General Chamber.
+
+Measurement system description is captured in clause 7.1.
+
+##### 13.5.2.2 Test procedure
+
+###### 13.5.2.2.1 Stage 1: Calibration
+
+Calibration for wanted signal power level is the same as in clause 10.2.
+
+Calibration for the CLTA path is described in clause 8.8.
+
+###### 13.5.2.2.2 Stage 2: BS measurement
+
+The General Chamber testing procedure consists of the following steps:
+
+- 1) Place NR BS and CLTA as specified in TS 37.145-2 [4] clause 4.15 for AAS BS, and in TS 38.141-2 [6] clause 4.12 for NR BS, at the declared worst case side. Several CLTA are required to cover the whole co-location blocking frequency ranges. The CLTA shall be selected according to clause 6.4.
+- 2) Align the NR BS and test antenna(s) according to the directions to be tested.
+- 3) Connect test antenna and CLTA to the measurement equipment as depicted in clause 7.7.
+
+- 5) The NR BS receives the wanted signal in all supported polarizations, in the *receiver target reference direction* from the test antenna.
+- 6) The OTA co-location blocking interferer is injected via the CLTA. The CLTA is fed with the specified co-location blocking interferer power per supported polarization.
+- 7) Generate the wanted signal in *receiver target reference direction*, all supported polarizations, from the test antenna, according to the applicable test configuration using applicable reference measurement channel to the RIB.
+- 8) Configure the *beam peak direction* for the transmitter units associated with the RIB under test according to the declared reference *beam direction pair* for the appropriate beam identifier with the carrier set-up and power allocation according to the applicable test configuration(s). The transmitter may be turned OFF for the out-of-band blocker tests when the frequency of the blocker is such that no IM2 or IM3 products fall inside the bandwidth of the wanted signal.
+- 9) Adjust the signal generators to the type of interfering signals, levels and the frequency offsets as specified for general test requirements and, when applicable, for co-location test requirements.
+- 10) The CW interfering signal shall be swept with a step size of 1 MHz within the frequency range corresponding to downlink operating bands related to co-located systems.
+- 11) Measure the performance of the wanted signal at the receiver unit associated with the RIB.
+
+### 13.5.2.3 MU value derivation, FR1
+
+The MU for the interferer signal is as follows:
+
+**Table 13.5.2.3-1: MU for co-location blocking interferer signal**
+
+| UID                                                                    | Uncertainty source                                      | Uncertainty value (dB) |                  |                 | Distribution of the probability | Divisor based on distribution shape | c <sub>i</sub> | Standard uncertainty u <sub>i</sub> (dB) |                  |                 |
+|------------------------------------------------------------------------|---------------------------------------------------------|------------------------|------------------|-----------------|---------------------------------|-------------------------------------|----------------|------------------------------------------|------------------|-----------------|
+|                                                                        |                                                         | f ≤ 3 G Hz             | 3 < f ≤ 4.2 G Hz | 4.2 < f ≤ 6 GHz |                                 |                                     |                | f ≤ 3 GHz                                | 3 < f ≤ 4.2 G Hz | 4.2 < f ≤ 6 GHz |
+| <b>Stage 2: BS measurement</b>                                         |                                                         |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| C2-9                                                                   | Uncertainty related to the selection of the CLTA        | 1,50                   | 1,50             | 1,50            | Rectangular                     | 1,73                                | 1              | 0,87                                     | 0,87             | 0,87            |
+| C2-10                                                                  | Uncertainty related to the placement of the CLTA        | 1,70                   | 1,70             | 1,70            | Rectangular                     | 1,73                                | 1              | 0,98                                     | 0,98             | 0,98            |
+| C2-13                                                                  | Impedance mismatch between feeder cable and CLTA        | 0,14                   | 0,23             | 0,25            | U-Shaped                        | 1,41                                | 1              | 0,10                                     | 0,16             | 0,18            |
+| A5-8                                                                   | Random uncertainty                                      | 0,10                   | 0,10             | 0,10            | Rectangular                     | 1,73                                | 1              | 0,06                                     | 0,06             | 0,06            |
+| A5-3                                                                   | Quality of quiet zone                                   | 0,10                   | 0,10             | 0,10            | Gaussian                        | 1,00                                | 1              | 0,10                                     | 0,10             | 0,10            |
+| <b>Stage 1: Calibration measurement</b>                                |                                                         |                        |                  |                 |                                 |                                     |                |                                          |                  |                 |
+| C3-7                                                                   | Colocation blocking - conducted measurement uncertainty | 1,00                   | 1,10             | 1,20            | Gaussian                        | 1,00                                | 1              | 1,00                                     | 1,10             | 1,20            |
+| <b>Combined standard uncertainty (1σ) (dB)</b>                         |                                                         |                        |                  |                 |                                 |                                     |                | <b>1,65</b>                              | <b>1,72</b>      | <b>1,79</b>     |
+| <b>Expanded uncertainty (1.96σ - confidence interval of 95 %) (dB)</b> |                                                         |                        |                  |                 |                                 |                                     |                | <b>3,24</b>                              | <b>3,37</b>      | <b>3,51</b>     |
+
+UID are referenced to annex A, B or C as appropriate.
+
+### 13.5.3 Maximum accepted test system uncertainty
+
+The final MU is calculated as follows:
+
+The  $\text{Noise}_{\text{effect}}$  from the signal generator is 0.1 dB and the  $\text{MU}_{\text{wanted signal}}$  value is  $\text{MU}_{\text{EIS}}$  from clause 10.2.7, where  $\text{MU}_{\text{interferer}}$  is derived in clause 14.2.3.
+
+**Table 13.5.3-1: Common maximum accepted test system uncertainty value derivation for co-location blocking interferer signal level**
+
+|                                                        | Expanded uncertainty (dB) |                              |                              |
+|--------------------------------------------------------|---------------------------|------------------------------|------------------------------|
+|                                                        | $f \leq 3 \text{ GHz}$    | $3 < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+| General Chamber                                        | 3,24                      | 3,37                         | 3,51                         |
+| <b>Common maximum accepted test system uncertainty</b> | <b>3,20</b>               | <b>3,40</b>                  | <b>3,50</b>                  |
+
+Fulfilling the criteria for CLTA selection and placement in is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the CLTA and its alignment as shall be used for evaluating the test system uncertainty.
+
+The final values are given in table 13.5.3-2.
+
+**Table 13.5.3-2: MU values for co-location blocking**
+
+| Co-location blocking MU (dB) |                                          | Wanted signal operating band            |                                          |                              |
+|------------------------------|------------------------------------------|-----------------------------------------|------------------------------------------|------------------------------|
+|                              |                                          | $30 \text{ MHz} < f \leq 3 \text{ GHz}$ | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | $4.2 < f \leq 6 \text{ GHz}$ |
+| Interferer frequency         | $30 \text{ MHz} < f \leq 3 \text{ GHz}$  | 3,4                                     | 3,5                                      | 3,6                          |
+|                              | $3 \text{ GHz} < f \leq 4.2 \text{ GHz}$ | 3,5                                     | 3,6                                      | 3,8                          |
+|                              | $4.2 < f \leq 6 \text{ GHz}$             | 3,7                                     | 3,7                                      | 3,8                          |
+
+## 13.5.4 Test Tolerance for OTA co-location blocking
+
+The test tolerance for co-location out of band blocking is zero.
+
+# 14 Out-of-band blocking requirements
+
+## 14.1 General
+
+Clause 14 captures MU and TT values derivation for the OTA out-of-band blocking requirement in Normal test conditions.
+
+The OTA out-of-band blocking requirement requires both a wanted in-band signal and an interferer out-of-band signal to be transmitted with the chamber. The wanted signal is defined in the far field, the interferer is defined as a field strength, due to the large range for frequencies it will not always be in the far field.
+
+Hence any acceptable measurement chamber for the OTA sensitivity requirement measurements (as described in clauses 7.2 to 7.6) is also suitable for the OTA out-of-band blocking requirement, it may be necessary that the interfering signal is transmitted from a separate antenna due to the large frequency range of the interferer.
+
+![Diagram of the general blocking test set-up using a different antenna. The setup is inside a 'Test system enclosure' lined with waveguides. On the left, two 'Signal Generator' boxes (one for the wanted signal, one for the interfering signal) are connected to two 'Test antenna' units. The top antenna is labeled '(in band)' and the bottom '(out of band)'. An arrow points to these antennas with the text 'Test antenna polarisation can be adjusted'. On the right, a box labeled 'AAS BS' (Antenna Under Test) is shown. It has a 'Calibrated point' marked with a dot. A coordinate system is defined with a vertical dashed line as the reference. The angle from the vertical to the line connecting the calibrated point to the antenna is labeled theta (θ), and the angle from the vertical to the line connecting the calibrated point to the antenna's main axis is labeled phi (φ). The 'AAS declared coordinate reference point and orientation' is indicated by an arrow pointing to the calibrated point.](3c65409bf428d5233f0443c2437c5b40_img.jpg)
+
+Diagram of the general blocking test set-up using a different antenna. The setup is inside a 'Test system enclosure' lined with waveguides. On the left, two 'Signal Generator' boxes (one for the wanted signal, one for the interfering signal) are connected to two 'Test antenna' units. The top antenna is labeled '(in band)' and the bottom '(out of band)'. An arrow points to these antennas with the text 'Test antenna polarisation can be adjusted'. On the right, a box labeled 'AAS BS' (Antenna Under Test) is shown. It has a 'Calibrated point' marked with a dot. A coordinate system is defined with a vertical dashed line as the reference. The angle from the vertical to the line connecting the calibrated point to the antenna is labeled theta (θ), and the angle from the vertical to the line connecting the calibrated point to the antenna's main axis is labeled phi (φ). The 'AAS declared coordinate reference point and orientation' is indicated by an arrow pointing to the calibrated point.
+
+**Figure 14.1-1: General blocking test set-up using a different antenna**
+
+In the worst case the wanted and interfering signal are transmitted from separate test antennas, hence they each may have a different uncertainty associated with the OTA chamber. This differs from the in-band interference measurements where the wanted signal and the interferer are added together outside the chamber and applied to the same test antenna and hence have a common OTA chamber uncertainty.
+
+The uncertainty of the interferer is analysed in this clause using a General Chamber assumption (see 7.7.3). The requirement may be tested in any suitable chamber (e.g. IAC, CATR) that is capable of measuring EIS accurately and also applying the out-of-band interferer. For interferer frequencies where it can be applied from a common antenna (like the in-band requirements) this is acceptable but it is expected the MU will be lower so will not influence the final MU value. The chosen chamber must of course be specified to handle the frequency of both the interferer and the wanted signal. The complete out-of-band blocking test may be completed using multiple chambers for different frequency ranges if necessary.
+
+The distance between the test object and test antenna injecting the interferer signal is adjusted when necessary to ensure specified interferer signal level to be received.
+
+## 14.2 General Chamber
+
+### 14.2.1 Measurement system description
+
+Measurement system description is captured in clause 7.7.1.
+
+A General Chamber is analysed for the interferer MU value, this is considered worst case for setting the MU value.
+
+### 14.2.2 Test procedure
+
+#### 14.2.2.1 Stage 1: Calibration
+
+For the wanted signal the calibration procedure and MU for the OTA sensitivity in clause 10.2 can be assumed for each chamber type and FR.
+
+The interferer path is calibrated using the same method with appropriate antennas.
+
+#### 14.2.2.2 Stage 2: BS measurement
+
+The General Chamber testing procedure consists of the following steps:
+
+- 1) Place test antenna(s) in at appropriate test directions, at appropriate distance, aligned in all supported polarizations (single or dual) with the BS.
+- 2) Connect test antenna(s) to the measurement equipment.
+- 3) The test antenna(s) shall be dual (or single) polarized covering the same frequency ranges as the BS and the blocking frequencies. If the test antenna does not cover both the wanted and interfering signal frequencies, separate test antennas for the wanted and interfering signal are required.
+- 4) The OTA blocking interferer is injected into the test antenna, with the blocking interferer producing specified interferer field strength level for each supported polarization. The interferer shall be *polarization matched* to the BS in band and the position maintained for OOB measurements.
+- 5) The BS receives the wanted signal and the interferer signal for all supported polarizations (single or dual), in the reference direction from the test antenna(s).
+
+### 14.2.3 MU value derivation, FR1
+
+The MU value for OTA out-of-band blocking consists of the MU value for the wanted signal and the MU value for the interfering signal.
+
+The unwanted signal is defined as a field strength so can be applied in the near field with the assumption that the test antenna fully illuminated the BS under test. For the purposes of calculating a MU value of the interfering signal the same general out-of-band OTA chamber used for the TX spurious emissions requirement in clause 12.2 is assumed.
+
+The out-of-band blocking is analysed using the same methodology as the other receiver interference requirements where:
+
+The  $MU_{\text{wanted signal}}$  of the wanted signal is the same as that for the OTA sensitivity requirement.
+
+The  $Noise_{\text{effect}}$  MU from the signal generator for the broad band noise effect is the same as the conducted requirement (i.e. 0.1 dB).
+
+The MU assessment for the General Chamber is as follows:
+
+**Table 14.2.3-1: MU assessment for out-of-band blocking interferer**
+
+The OTA chamber is one part of the total interferer MU value. The rest of the MU is from the conducted signal accuracy, for this the conducted accuracy is used as a guide. In addition care is taken to ensure the mismatch is not added twice (from the chamber and the conducted value) and also it is considered if a PA is needed to achieve sufficient test signal power level.
+
+The interferer is specified as a field strength of 0.36 V/m, the required conducted power level depends on chamber size (the FSPL) the test *antenna gain* and the conducted signal path, and example is given in table 14.2.3-2.
+
+**Table 14.2.3-2: Example of required conducted interferer level**
+
+| OOB blocking interferer level |              |     |
+|-------------------------------|--------------|-----|
+| Field strength                | 0.36         | V/m |
+| d                             | 4            | m   |
+| EIRP                          | 18.40        | dBm |
+| Antenna                       | 5            | dBi |
+| Cables, filers, etc.          | 10           | dB  |
+| Signal generator              | <b>23.40</b> | dBm |
+
+Some signal generators can provide 23.4 dBm but it is at the top end so it is sensible to consider a PA in the test set up.
+
+The  $MU_{\text{interferer}}$  value is hence given by:
+
+For each of the frequency ranges this gives the value in table 14.2.3-3.
+
+**Table 14.2.3-3: MU<sub>interferer</sub> values**
+
+| Frequency range       | cond. int. (mod) | PA  | cond. matching | out-of-band chamber | OTA interferer |
+|-----------------------|------------------|-----|----------------|---------------------|----------------|
+| 30 MHz < f ≤ 3 GHz    | 1                | 0.2 | 0.294          | 0.93                | 1.35           |
+| 3 GHz < f ≤ 6 GHz     | 1.2              | 0.2 | 0.294          | 0.93                | 1.50           |
+| 6 GHz < f ≤ 12.75 GHz | 3                | 0.2 | 0.55           | 1.12                | 3.16           |
+
+The final MU for the OTA out-of-band blocking requirement is calculated as follows:
+
+The Noise<sub>effect</sub> from the signal generator is 0.1 dB and the MU<sub>wantedsignal</sub> value is MU<sub>EIS</sub> from clause 10.2.
+
+The final values are given in table 14.2.3-4:
+
+**Table 14.2.3-4: MU values for out-of-band blocking**
+
+| OOB blocking MU (dB) |                       | Wanted signal operating band |                     |                     |
+|----------------------|-----------------------|------------------------------|---------------------|---------------------|
+|                      |                       | 30 MHz < f ≤ 3 GHz           | 3 GHz < f ≤ 4.2 GHz | 4.2 GHz < f ≤ 6 GHz |
+| Interferer frequency | 30 MHz < f ≤ 3 GHz    | 2.0                          | 2.2                 | 2.2                 |
+|                      | 3 GHz < f ≤ 6 GHz     | 2.1                          | 2.1                 | 2.3                 |
+|                      | 6 GHz < f ≤ 12.75 GHz | 3.5                          | 3.6                 | 3.6                 |
+
+## 14.2.4 MU value derivation, FR2
+
+It has been agreed that the MU for the out-of-band blocking requirement can be calculated as follows:
+
+$$+ \text{Broadband noise effect}$$
+
+With
+
+$$MU_{EIS} (1.96\sigma) = 2.4$$
+
+$$MU_{OOBint} (1.96\sigma) = 1.96 \times 1.1$$
+
+$$MU_{PA} (1.96\sigma) = 1.96 \times 0.2$$
+
+And
+
+$$\text{Broadband noise effect} (1.96\sigma) = 0.4$$
+
+Substituting the variables above into the formula, the MU in FR2 for the out-of-band blocking requirement can be calculated as 3.6 dB, as shown in table 14.2.4-1 below.
+
+**Table 14.2.4-1: MU for out-of-band blocking, FR2**
+
+| Test System Uncertainty                                                             | Standard uncertainty $u_i$ (dB)<br>IAC, CATR |
+|-------------------------------------------------------------------------------------|----------------------------------------------|
+| MU <sub>EIS</sub> (Expanded uncertainty)                                            | 2.4                                          |
+| MU <sub>OOBint</sub> (Additional uncertainty for the OOB interferer signal)         | 1.1                                          |
+| MU <sub>PA</sub> (Uncertainty due to use of PA)                                     | 0.2                                          |
+| Broadband noise effect (Impact of interferer broadband noise)                       | 0.4                                          |
+| <b>Combined standard uncertainty (<math>1\sigma</math>)</b>                         | <b>1.86</b>                                  |
+| <b>Expanded uncertainty (<math>1.96\sigma</math> - confidence interval of 95 %)</b> | <b>3.6</b>                                   |
+
+## 14.3 Maximum accepted test system uncertainty
+
+The final values are given in table 14.3-1.
+
+**Table 14.3-1: MU values for out of band blocking**
+
+| OOB blocking MU (dB) |                       | Wanted signal operating band |
+|----------------------|-----------------------|------------------------------|
+|                      |                       | 4.2 GHz < f ≤ 6 GHz          |
+| Interferer frequency | 30 MHz < f ≤ 3 GHz    | 2.2                          |
+|                      | 3 GHz < f ≤ 6 GHz     | 2.3                          |
+|                      | 6 GHz < f ≤ 12.75 GHz | 3.6                          |
+
+## 14.4 Test Tolerance for OOB blocking
+
+It has been agreed that the TT for the out-of-band blocking requirement should be zero.
+
+# 15 Demodulation performance requirements
+
+## 15.1 General
+
+This clause describes the OTA aspects of the test procedure for assessing demodulation requirements, based on the analysis of the UTRA FDD and E-UTRA demodulation requirements which were found feasible OTA, as captured in clause 15.2. The same principles are to be used for the analysis of the OTA demodulation performance requirements for NR.
+
+The OTA part of the test procedure is the same for each requirement.
+
+## 15.2 BS demodulation requirements feasible OTA
+
+The feasibility analysis of the OTA test cases modelling concluded that the conducted test case with one TX (UE side) and one or two RX chains (BS side) were identified as candidates for feasible OTA demodulation cases.
+
+For 2RX case the cross-polarisation is assumed to be used in order to achieve separation of streams at the RX side of OTA test setup. Most of the conducted test cases in 1TX-1RX, or 1TX-2RX configuration, can be implemented in OTA test setups as illustrated in figures 15.3-1 and 15.3-2 for the multipath fading propagation conditions, and in figures 15.3-3 and 15.3-4 for the static propagation conditions.
+
+Based on the analysis of the conducted BS demodulation requirements for UTRA FDD and E-UTRA, the single RAT requirements considered as feasible in OTA test setup were listed in tables 15.2-1 and 15.2-2 for UTRA and E-UTRA. The same principles (i.e. based on cross-polarisation) are to be used for the analysis of the OTA demodulation performance requirements for NR.
+
+**Table 15.2-1: UTRA FDD BS demodulation requirements feasible OTA**
+
+| <b>UTRA FDD BS demodulation requirements</b>                                  |          | <b>Tx<br/>(UE<br/>emulator<br/>)</b> | <b>Rx<br/>(OTA<br/>BS)</b> |  |
+|-------------------------------------------------------------------------------|----------|--------------------------------------|----------------------------|--|
+| Demodulation in static propagation conditions                                 | DCH      | 1Tx                                  | 1Rx, 2Rx                   |  |
+| Demodulation of DCH in multipath fading conditions                            |          |                                      | 1Rx, 2Rx                   |  |
+| Demodulation of DCH in moving propagation conditions                          |          |                                      | 1Rx, 2Rx                   |  |
+| Demodulation of DCH in birth/death propagation conditions                     |          |                                      | 1Rx, 2Rx                   |  |
+| Demodulation of DCH in high speed train conditions                            |          |                                      | 1Rx, 2Rx                   |  |
+| Performance requirement for RACH preamble detection                           | RACH     |                                      | 1Rx, 2Rx                   |  |
+| Demodulation of RACH message                                                  |          |                                      | 1Rx, 2Rx                   |  |
+| ACK false alarm                                                               | HS-DPCCH |                                      | 2Rx                        |  |
+| ACK mis-detection                                                             |          |                                      | 2Rx                        |  |
+| ACK/NACK detection for 4C-HSDPA HS-DPCCH (ACK false alarm, ACK mis-detection) |          |                                      | 2Rx                        |  |
+| ACK/NACK detection for 8C-HSDPA HS-DPCCH                                      |          |                                      | 2Rx                        |  |
+| E-DPDCH in multipath fading condition                                         | E-DPDCH  |                                      | 1Rx, 2Rx                   |  |
+| E-DPDCH and S-E-DPDCH in multipath fading condition for UL MIMO               |          |                                      | 2Rx                        |  |
+| Signalling detection for E-DPCCH in multipath fading condition                |          |                                      | 1Rx, 2Rx                   |  |
+
+**Table 15.2-2: E-UTRA BS demodulation requirements feasible OTA**
+
+| <b>E-UTRA BS demodulation requirements</b>                                                                    |       | <b>Tx<br/>(UE emulator)</b> | <b>Rx<br/>(OTA BS)</b> |  |
+|---------------------------------------------------------------------------------------------------------------|-------|-----------------------------|------------------------|--|
+| PUSCH in multipath fading propagation conditions transmission                                                 | PUSCH | 1Tx                         | 2Rx                    |  |
+| UL timing adjustment                                                                                          |       |                             | 2Rx                    |  |
+| HARQ-ACK multiplexed on PUSCH                                                                                 |       |                             | 2Rx                    |  |
+| High Speed Train conditions                                                                                   |       |                             | 1Rx, 2Rx               |  |
+| PUSCH with TTI bundling and enhanced HARQ pattern                                                             |       |                             | 2Rx                    |  |
+| Enhanced performance requirement type A in multipath fading propagation conditions, synchronous interference  |       |                             | 2Rx                    |  |
+| Enhanced performance requirement type A in multipath fading propagation conditions, asynchronous interference |       |                             | 2Rx                    |  |
+| Enhanced performance requirement type B in multipath fading propagation conditions                            |       |                             | 2Rx                    |  |
+| Requirements for PUSCH supporting coverage enhancement                                                        |       |                             | 2Rx                    |  |
+| Requirements for PUSCH supporting Cat-M1 UEs                                                                  |       |                             | 2Rx                    |  |
+| ACK missed detection for single user PUCCH format 1a transmission                                             | PUCCH |                             | 2Rx                    |  |
+| CQI performance requirements for PUCCH format 2 transmission                                                  |       |                             | 2Rx                    |  |
+| ACK missed detection for multi user PUCCH format 1a                                                           |       |                             | 2Rx                    |  |
+| ACK missed detection for PUCCH format 1b with Channel Selection                                               |       |                             | 2Rx                    |  |
+| ACK missed detection for PUCCH format 3                                                                       |       |                             | 2Rx                    |  |
+| NACK to ACK detection for PUCCH format 3                                                                      |       |                             | 2Rx                    |  |
+| CQI performance requirements for PUCCH format 2 with DTX detection                                            |       |                             | 2Rx                    |  |
+| PUCCH performance requirements for supporting Cat-M1 UEs                                                      |       |                             | 2Rx                    |  |
+| ACK missed detection requirements for PUCCH format 4                                                          |       |                             | 2Rx                    |  |
+| ACK missed detection requirements for PUCCH format 5                                                          |       |                             | 2Rx                    |  |
+| PRACH missed detection, normal mode                                                                           | PRACH |                             | 2Rx                    |  |
+| PRACH missed detection, high speed mode restricted set type A                                                 |       |                             | 2Rx                    |  |
+| PRACH missed detection, Cat-M1 mode                                                                           |       |                             | 2Rx                    |  |
+| PRACH missed detection, high speed mode restricted set type B                                                 |       |                             | 2Rx                    |  |
+
+It is noted, that the possibility of OTA testing is considered also for those BS demodulation requirements, which were declared as optional.
+
+The OTA related parts of the conformance testing test procedures for the demodulation requirements are based upon the OTA RX dynamic range requirement procedure, as described in clause 10.4. The setup and operation of the signal generator and measurement instruments are the same as for the corresponding conducted requirements.
+
+The demodulation requirements are in essence very similar to the RX dynamic range requirement; in both cases a wanted signal and AWGN is transmitted from the test equipment and should be reassured to be received at the absolute level well above the noise floor. The test equipment setup for demodulation requirements may include multiple wanted and interference signals and a fading channel emulators, as described in clause 15.3.
+
+## 15.3 OTA test setup for BS demodulation requirements
+
+As the BS demodulation requirements rely on the link level performance between the UE and BS, in case of the requirements definition for the BS, it is required to establish radio link in uplink based on the test equipment (i.e. BS Tester test and reference antenna(s)) located within the RoAoA corresponding to the frequency band used for the BS demodulation testing.
+
+For PUSCH testing purposes in OTA setup, the HARQ feedback can be delivered to the BS Tester via conducted interface.
+
+Figure 15.3-1 shows BS measurement test setup for multipath fading propagation conditions, which is equivalent to the conducted 1TX – 1RX test setup.
+
+The OTA BS is comprised in an anechoic chamber and is configured to receive with single RX configuration. Test signal source is connected to the single TX test antenna. The radio propagation channel is emulated by connecting a fading channel emulator between the test signal generator and the TX antenna.
+
+NOTE: OTA demodulation requirements can be tested in IAC, as well as in CATR, as outlined in clause 15.4 and 15.5. All the examples of the OTA test setups for the BS demodulation requirements are based on the IAC test setup.
+
+AWGN noise floor levels required in the conformance test setup are to be derived from conducted BS demodulation test setup procedures. Wanted signal generators are configured so that the SNR levels defined by the demodulation requirements are achievable at the BS. For SNR derivation, the noise injection at the BS tester side is considered as the baseline approach.
+
+![Figure 15.3-1: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 1RX). The diagram shows a BS tester connected to a Channel simulator, which is connected to a TX antenna (Tx A, polarization 1) inside an anechoic chamber. An AWGN generator is also connected to the Channel simulator. The BS under test (Rx A) is inside the chamber, receiving the signal from the TX antenna. A HARQ feedback line (only for PUSCH) is shown between the BS under test and the BS tester.](f2e97817636949186cf689a4b532b8a9_img.jpg)
+
+The diagram illustrates the OTA test setup for multipath fading propagation conditions. On the left, outside the anechoic chamber, a 'BS tester' is connected to a 'Channel simulator'. An 'AWGN generator' is also connected to the 'Channel simulator'. The 'Channel simulator' is connected to a TX antenna labeled 'Tx A, polarization 1' inside the anechoic chamber. The 'BS under test' (Rx A) is also inside the chamber, receiving the signal from the TX antenna. A dashed line labeled 'HARQ feedback (only for PUSCH)' connects the 'BS under test' back to the 'BS tester'. The chamber is represented by a rectangle with a jagged border, and a large arrow labeled 'Far field region' points from the TX antenna to the RX antenna.
+
+Figure 15.3-1: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 1RX). The diagram shows a BS tester connected to a Channel simulator, which is connected to a TX antenna (Tx A, polarization 1) inside an anechoic chamber. An AWGN generator is also connected to the Channel simulator. The BS under test (Rx A) is inside the chamber, receiving the signal from the TX antenna. A HARQ feedback line (only for PUSCH) is shown between the BS under test and the BS tester.
+
+**Figure 15.3-1: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 1RX)**
+
+Figure 15.3-2 shows BS measurement test setup for multipath fading propagation conditions, which is equivalent to the conducted 1TX – 2RX test setup. The BS is comprised in an anechoic chamber and is configured to receive with 2RX diversity in a cross-polarised configuration. Test signal source is connected to the 2TX tests antenna in cross-polarised configuration. The two orthogonal radio propagation channels are emulated by passing the same test signal through one fading channel emulator for each of TX antennas.
+
+![Figure 15.3-2: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 2RX setup).](6c5c4041e081d25a3f7e13f5fd2a3390_img.jpg)
+
+This diagram illustrates the OTA test setup for multipath fading propagation conditions, equivalent to a conducted 1TX – 2RX setup. On the left, a 'BS tester' is connected to two 'Channel simulator' blocks and two 'AWGN generator' blocks. The outputs of the channel simulators are combined and fed into a transmit antenna labeled 'Tx A, polarization 1' and 'Tx A, polarization 2'. These antennas are located within a large rectangular area representing the 'Far field region'. Inside this region, on the right, is the 'BS under test' which has two receive antennas labeled 'Rx A' and 'Rx B'. A dashed line labeled 'HARQ feedback (only for PUSCH)' connects the 'BS under test' back to the 'BS tester'.
+
+Figure 15.3-2: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 2RX setup).
+
+**Figure 15.3-2: OTA test setup for multipath fading propagation conditions (equivalent to conducted 1TX – 2RX setup)**
+
+![Figure 15.3-3: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 1RX setup).](11b4377bcba1c43b30732e5bb511ad5d_img.jpg)
+
+This diagram illustrates the OTA test setup for static propagation conditions, equivalent to a conducted 1TX – 1RX setup. On the left, a 'BS tester' is connected to a single 'AWGN generator' block. The output of the AWGN generator is combined and fed into a transmit antenna labeled 'Tx A, polarization 1'. This antenna is located within a large rectangular area representing the 'Far field region'. Inside this region, on the right, is the 'BS under test' which has one receive antenna labeled 'Rx A'. A dashed line labeled 'HARQ feedback (only for PUSCH)' connects the 'BS under test' back to the 'BS tester'.
+
+Figure 15.3-3: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 1RX setup).
+
+**Figure 15.3-3: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 1RX setup)**
+
+![Figure 15.3-4: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 2RX setup).](77dcb3b9312f3e14215a4890634391e5_img.jpg)
+
+This diagram illustrates the OTA test setup for static propagation conditions, equivalent to a conducted 1TX – 2RX setup. On the left, a 'BS tester' is connected to two 'AWGN generator' blocks. The outputs of the AWGN generators are combined and fed into two transmit antennas labeled 'Tx A, polarization 1' and 'Tx A, polarization 2'. These antennas are located within a large rectangular area representing the 'Far field region'. Inside this region, on the right, is the 'BS under test' which has two receive antennas labeled 'Rx A' and 'Rx B'. A dashed line labeled 'HARQ feedback (only for PUSCH)' connects the 'BS under test' back to the 'BS tester'.
+
+Figure 15.3-4: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 2RX setup).
+
+**Figure 15.3-4: OTA test setup for static propagation conditions (equivalent to conducted 1TX – 2RX setup)**
+
+## 15.4 Indoor Anechoic Chamber
+
+### 15.4.1 Measurement system description
+
+The general IAC test setup for demodulation requirements is the same as that for OTA dynamic range, i.e. the same as described in clause 7.2.1. For more detailed test setup with the consideration of the channel simulators, AWGN noise generators as well as the polarization separation for 2RX setup, refer to the figures in clause 15.3.
+
+## 15.4.2 Test procedure
+
+### 15.4.2.1 Stage 1: Calibration
+
+The calibration procedure for demodulation requirements is the same as that for OTA dynamic range, i.e. the same as described in clause 7.2.1 and depicted in figure 7.2.1-3. Calibration of the wanted signal and AWGN levels shall be performed.
+
+### 15.4.2.2 Stage 2: BS measurement
+
+The IAC measurement procedure is the same as those for the OTA sensitivity requirement in clause 10.2.2.2.2, except that step 5 is modified to measure applicable performance metric for the BS demodulation requirements (i.e. BER, or throughput, depending on the RAT and requirement).
+
+The transmit signal power level may be set in the same manner as for OTA dynamic range; i.e. by considering the AWGN absolute levels referenced from appropriate conducted RAT-specific testing specifications, together with an adjustment  $\Delta_{\text{OTAREFSENS}}$  to take into account BS *antenna gain* (path loss is taken account of by the calibration procedure). Examples of the AWGN power levels for the E-UTRA PUSCH requirements are listed in table 15.4.2.2-1 (AWGN levels for other requirements can be found in the conducted single RAT specifications).
+
+**Table 15.4.2.2-1: examples of the AWGN power level at the BS input for E-UTRA demodulation requirements**
+
+| Channel bandwidth (MHz) | AWGN power level                                    |
+|-------------------------|-----------------------------------------------------|
+| 1.4                     | $-92.7 - \Delta_{\text{OTAREFSENS}}$ dBm / 1.08 MHz |
+| 3                       | $-88.7 - \Delta_{\text{OTAREFSENS}}$ dBm / 2.7 MHz  |
+| 5                       | $-86.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 4.5 MHz  |
+| 10                      | $-83.5 - \Delta_{\text{OTAREFSENS}}$ dBm / 9 MHz    |
+| 15                      | $-81.7 - \Delta_{\text{OTAREFSENS}}$ dBm / 13.5 MHz |
+| 20                      | $-80.4 - \Delta_{\text{OTAREFSENS}}$ dBm / 18 MHz   |
+
+## 15.4.3 MU value derivation, FR1
+
+The BS demodulation requirements consist of a wanted signal and AWGN (potentially with fading modelling and additional interfering signals). In the conducted test setup, the received AWGN level is well above the noise floor, and so the SNR experienced at the BS receiver is dependent on the transmitter SNR/SINR (in case of E-UTRA) or  $E_b/N_0$  (in case of UTRA).
+
+Small variations in the received power level due to additional uncertainties in the OTA measurement chamber will not impact the receiver SNR, and hence uncertainties due to OTA will not impact the demodulation requirement MU. The MU can be considered to depend on the TX SNR/SINR (in case of E-UTRA) or on the TX  $E_b/N_0$  (in case of UTRA) and, where applicable the fading channel generation uncertainty, in the same manner as for the conducted requirements.
+
+Thus, the MU for OTA demodulation requirements is the same as the MU for conducted demodulation requirements, as derived in RAT-specific conducted testing specifications:
+
+- TS 25.141 [2] for UTRA FDD
+- TS 36.141 [3] for E-UTRA
+- TS 38.141-1 [5] for NR
+
+The resulting test requirements for OTA BS can be reused from the above conducted test specifications, as long as the SNR/SINR (in case of E-UTRA and NR) or the TX  $E_b/N_0$  (in case of UTRA) at the BS receiver is not impacted by the noise floor due to the OTA test chamber path loss.
+
+## 15.5 Compact Antenna Test Range
+
+### 15.5.1 Measurement system description
+
+The general CATR test setup for demodulation requirements is the same as that for OTA dynamic range, i.e. the same as described in clause 7.3.1 and the measurement system setup for OTA dynamic range depicted on figure 7.3.1-3. For more detailed test setup with the consideration of the channel simulators, AWGN noise generators as well as the polarization separation for 2RX setup, refer to the figures in clause 15.3.
+
+### 15.5.2 Test procedure
+
+#### 15.5.2.1 Stage 1: Calibration
+
+The calibration procedure for demodulation requirements is the same as that for OTA dynamic range, as described in clause 8.3 and depicted on figure 7.3.1-3. Calibration of the wanted signal and AWGN levels shall be performed.
+
+#### 15.5.2.2 Stage 2: BS measurement
+
+The CATR measurement procedure is the same as those for the OTA dynamic range requirement in clause 10.4.3.2.2, except that step 4 is modified to measure applicable performance metric for the BS demodulation requirements (i.e. BER, or throughput, depending on the RAT and requirement).
+
+The transmit signal power level may be set in the same manner as described in clause 15.4.2.2 (i.e. BS demodulation requirements in IAC).
+
+### 15.5.3 MU value derivation, FR1
+
+The MU for OTA demodulation requirements is the same as for conducted demodulation requirements for the same reasons as applicable for the indoor anechoic chamber, described in clause 15.4.3.
+
+## 15.6 Maximum accepted test system uncertainty
+
+Measurement Uncertainties for the OTA BS demodulation requirements are the same as for the conducted requirements.
+
+For maximum accepted OTA test system uncertainty values for the OTA demodulation requirements, refer to the following RAT-specific specifications:
+
+- For UTRA demodulation requirements refer to TS 25.141 [2], clause 4.1.4.
+- For E-UTRA demodulation requirements, refer to TS 36.141 [3], clause 4.1.2.3.
+- For NR demodulation requirements, refer to TS 38.141-2 [6], clause 4.1.2.4.
+
+## 15.7 Test Tolerance for OTA demodulation requirements
+
+Test Tolerance values for the OTA BS demodulation requirements are the same as for the conducted requirements.
+
+For Test Tolerance values used for the OTA demodulation requirements derivation, refer to the following RAT-specific specifications:
+
+- For UTRA demodulation requirements refer to TS 25.141 [2], clause 4.2.3.
+- For E-UTRA demodulation requirements, refer to TS 36.141 [3], Annex G, clause G.3.
+- For NR demodulation requirements, refer to TS 38.141-2 [6], Annex C, clause C.3.
+
+## 16 EMC requirements
+
+### 16.1 BS ports for the EMC purposes
+
+The OTA AAS BS architecture does not have a conducted interface and so the antennas cannot be disconnected. This means that the conducted methods where the *EMC antenna ports* are terminated are no longer possible and hence new methods for EMC testing are needed.
+
+Figure 8.1-1 shows the prime difference in architecture from an EMC view point when comparing the ports on a conventional non-AAS BS to the ports on an AAS BS.
+
+![Figure 8.1-1: Comparison between BS architectures for EMC testing. The diagram shows two side-by-side representations of a Base Station (BS) apparatus. The left side represents a conventional non-AAS BS, showing an 'Apparatus' box with an 'Enclosure Port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Antenna port', 'Signal/control port', and 'Telecommunication port' on the right. The right side represents an AAS BS, showing an 'Apparatus' box with an 'Enclosure Port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Signal/control port' and 'Telecommunication port' on the right. The 'Antenna port' on the right is crossed out with a red 'X'. Inside the 'Apparatus' box on the right, there is a dashed red rectangle labeled 'Integrated Antenna Array'.](b723a64dd970a1cb5a08ce1e88ac7921_img.jpg)
+
+Figure 8.1-1: Comparison between BS architectures for EMC testing. The diagram shows two side-by-side representations of a Base Station (BS) apparatus. The left side represents a conventional non-AAS BS, showing an 'Apparatus' box with an 'Enclosure Port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Antenna port', 'Signal/control port', and 'Telecommunication port' on the right. The right side represents an AAS BS, showing an 'Apparatus' box with an 'Enclosure Port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Signal/control port' and 'Telecommunication port' on the right. The 'Antenna port' on the right is crossed out with a red 'X'. Inside the 'Apparatus' box on the right, there is a dashed red rectangle labeled 'Integrated Antenna Array'.
+
+**Figure 8.1-1: Comparison between BS architectures for EMC testing**
+
+Since the *antenna array* for the OTA AAS BS is integrated within the BS, the transmissions from the BS within the test chamber have *antenna gain* included in them.
+
+Figure 8.1-2 illustrates the status of *EMC antenna ports* during EMC testing where it is noted that the ports are connected to a terminating load and the *hybrid AAS BS* is then set to transmit at full power.
+
+![Figure 8.1-2: EMC Antenna port status during EMC testing. The diagram shows a Base Station (BS) apparatus inside a dashed blue rectangle representing an EMC test chamber. The 'Apparatus' box has an 'Enclosure port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Antenna port', 'Signal/control port', and 'Telecommunication port' on the right. The 'Antenna port' is connected to a grey box labeled 'Terminating load'. The entire setup is enclosed within a dashed blue rectangle labeled 'Enclosure port' at the top.](a83b94d3c7b86ae870ab0ea3bd48d0ec_img.jpg)
+
+Figure 8.1-2: EMC Antenna port status during EMC testing. The diagram shows a Base Station (BS) apparatus inside a dashed blue rectangle representing an EMC test chamber. The 'Apparatus' box has an 'Enclosure port' at the top, 'AC power port', 'DC power port', and 'Earth port' on the left, and 'Antenna port', 'Signal/control port', and 'Telecommunication port' on the right. The 'Antenna port' is connected to a grey box labeled 'Terminating load'. The entire setup is enclosed within a dashed blue rectangle labeled 'Enclosure port' at the top.
+
+**Figure 8.1-2: EMC Antenna port status during EMC testing**
+
+## 16.2 Field strength in EMC chamber
+
+### 16.2.1 General
+
+This clause provides an example estimation of field strength within the EMC chamber. Assuming free space propagation loss in an anechoic chamber, the path loss can be calculated as:
+
+$$L = G_t G_r \left( \frac{\lambda}{4\pi R} \right)^2$$
+
+where  $G_t$  and  $G_r$  are the *antenna gains* (with respect to an isotropic radiator) of the transmitting and receiving antennas respectively,  $\lambda$  is the wavelength, and  $R$  is the distance between the TX and RX.
+
+Assuming a 0dBi *antenna gain* for the TX and RX, the isotropic free space path loss is plotted in figure 8.3.1-1 for 30, 1000, 2000, 4000, 6000 and 12000 MHz.
+
+![Figure 16.2.1-1: Free-space path loss, assuming G_t=G_r=0 dBi. The graph shows Loss [dB] on the y-axis (0 to 80) versus Distance [m] on the x-axis (0 to 20). Six curves are plotted for frequencies of 30, 1000, 2000, 4000, 6000, and 12000 MHz. The 12000 MHz curve is the highest, reaching approximately 78 dB at 20 meters. The 30 MHz curve is the lowest, reaching approximately 28 dB at 20 meters. All curves show a rapid increase in loss as distance increases, with the rate of increase being higher for higher frequencies.](090f012618e458eb073599905057ad26_img.jpg)
+
+Figure 16.2.1-1: Free-space path loss, assuming G\_t=G\_r=0 dBi. The graph shows Loss [dB] on the y-axis (0 to 80) versus Distance [m] on the x-axis (0 to 20). Six curves are plotted for frequencies of 30, 1000, 2000, 4000, 6000, and 12000 MHz. The 12000 MHz curve is the highest, reaching approximately 78 dB at 20 meters. The 30 MHz curve is the lowest, reaching approximately 28 dB at 20 meters. All curves show a rapid increase in loss as distance increases, with the rate of increase being higher for higher frequencies.
+
+**Figure 16.2.1-1: Free-space path loss, assuming  $G_t=G_r=0$  dBi**
+
+It can be noted that for a typical distance between the BS and the probe antenna within the chamber, (e.g. 5 meters), the path loss at 2 GHz is more than 50 dB. However, if the BS has an integrated antenna which has gain, and the measurement probe antenna also has gain the total loss between the BS and the measurement equipment may drop. For example, a BS with TX *antenna gain* = 10 dBi and assuming 10 dBi *antenna gain* for the probe antenna, the coupling loss at 5 meters is roughly 30 dB, i.e. 20 dB lower than the coupling loss assuming 0 dBi *antenna gains*. With this observation, and the fact the AAS BS is transmitting and connected to its integrated antenna, it can be contemplated that an AAS BS leads to significantly increased field strength within the chamber compared to the usual EMC measurement scenario where the transmitters are connected to terminating loads. This increased field strength and associated received power from the measurement probe could potentially damage the test equipment.
+
+## 16.2.2 Conversion between dBm to V/m
+
+Since the field strength within the EMC chamber is expressed in terms of electric field strength (i.e. V/m), it is important to establish the intensity of electric field strength generated when transmitting at a certain power (dBm). This conversion exists in prior art and is explained in [20]. In summary, for a free space wave impedance of 377 ohm, the electric field (V/m) can be expressed as:
+
+Where  $R$  is the distance of BS from the interferer (during the immunity testing).
+
+This formula provides us a way to calculate the field strength within the chamber.
+
+## 16.3 Protection of measurement equipment
+
+In order to protect the measurement device from the increased field strength levels within the EMC chamber during the spurious emission testing. Traditionally in EMC testing as the BS transmitters are working into a load the received signal from the EMC test antenna is at a low power level which can be fed directly into the measurement equipment. With the AAS BS testing as the transmitter units are radiating through the AAS BS antenna the transmit signal received at the measurement device is of a high power. In order to protect the measurement device from this signal, the device needs to ensure additional attenuation by filtering out the wanted signal with a notch or band stop filter. Additionally,
+
+TX exclusion bands similar to those used in existing conducted spurious emissions requirements may need to be defined in certain areas to ensure that the increased field strength does not block/damage the measurement device.
+
+The existing RAT-specific frequency boundary limits defined for out-of-band emissions by the SEM or OBUE requirements in TS 37.105 [14] is a sufficient boundary to limit exposure of the measurement's equipment receiver from the high field strengths of the wanted signal.
+
+## 16.4 Emission requirements
+
+In terms of transmitter spurious emission, two types of core requirements specified for AAS BS are relevant:
+
+1. The RF spurious emission requirements specified in TS 37.105 [14] with different measurement bandwidths and spurious emission levels as detailed in SM.329 [15].
+2. The EMC radiated emission requirements specified in TS 37.114 [17] with the same measurement bandwidths as the RF spurious emission requirements.
+
+In terms of the applicability of the RF Radiated Spurious Emission (RF RSE) and EMC Radiated Emission (EMC RE) requirements in the OTA setup, according to the existing conducted requirements, these requirements apply from 30 MHz to 12.75 GHz with consideration of exceptions:
+
+- Unwanted emissions: the RF RSE requirement apply at frequencies within the above specified frequency range with the exception of the UTRA spectrum emission mask (SEM) and E-UTRA operating band unwanted emissions (OBUE) ranges specified in single RAT and MSR specifications.
+- Upper frequency: in order for the RF RSE requirement to comply with the SM.329 recommendation [15], for certain operating bands the upper limit of the spurious range is extended beyond 12.75 GHz to the limit of 5<sup>th</sup> harmonic (but not higher than 26 GHz). For more details on the upper limit setting in those cases, refer to SM.329 [15].
+
+The applicability of EMC RE and RF RSE requirements is illustrated in figure 16.4-1 below
+
+![A small blue rectangular box, likely a placeholder for a diagram or figure.](cdce40d544a867b676500c480efd5886_img.jpg)
+
+A small blue rectangular box, likely a placeholder for a diagram or figure.
+
+**Figure 16.4-1: Applicability of spurious emission requirements**
+
+It is to be noted that these EMC RE requirements are applicable at the enclosure port and the *EMC antenna port* is connected to a terminating load while the AAS BS is transmitting at full power. The EMC RE are then tested in this setup to make sure that the requirements are fulfilled.
+
+For the OTA AAS BS architecture that does have the possibility of disconnecting the composite antenna, the *EMC antenna ports* can no longer be connected to a terminating load. This means that the RF RSE and EMC RE requirements cannot be differentiated any needs to be considered as single OTA requirement specified at the enclosure of the BS. The single requirement contains a RF RSE component and an EMC RE component as shown in figure 16.4-1 and the total emission requirement is as specified in the SM.329 [15] recommendation.
+
+Mechanism to specify the regional and additional co-existence requirements is not covered by the present release of this technical report.
+
+## 16.5 Radiated immunity requirements
+
+### 16.5.1 General
+
+When performing EMC RI tests of an OTA AAS BS or *BS type 1-O*, due to lack of the antenna connectors a higher power level may, for certain test scenarios, enter the RX of the BS, while for a *hybrid AAS BS* the antenna connectors
+
+would be terminated during test preventing this to happen. This may lead to the receiver of the OTA AAS BS or *BS type 1-O* being inoperable (in case the RF blocking requirements are not met). To avoid the OTA AAS BS or *BS type 1-O* receiver being inoperable during the EMC RI test, protection mechanisms need to be employed for BS RX during the RI testing.
+
+NOTE: Within Rel-15 timeframe, there were no EMC Radiated Immunity requirement defined for FR2 and *BS type 2-O*.
+
+## 16.5.2 Measurement set-up for testing radiated immunity
+
+In an EMC RI testing test setup for non-AAS BS products, the antenna connectors of the BS are terminated during test to prevent high power levels entering the RX of the BS. For the AAS BS architectures such as *BS type 1-O*, due to lack of the antenna connectors (called TAB connectors in case of AAS BS products), it is not possible to terminate TAB connectors and prevent disturbances affecting the RX chain. This may lead to the receiver of the *BS type 1-O* being inoperable (in case the RF blocking requirements are not met). To avoid the *BS type 1-O* receiver being inoperable during the EMC RI test, protection mechanisms need to be employed for BS RX during the RI testing.
+
+A high level example of EMC RI test setup for an OTA AAS BS is illustrated in figure 16.5.2-1. The BS is placed in an anechoic chamber on top of a turn table. A range antenna or probe antenna generates the interfering RF electromagnetic field.
+
+![Diagram of the radiated immunity test setup for a BS type 1-O. The setup is inside a shielded anechoic chamber. A 'Test object' (AAS Array) is mounted on a 'Positioner' (turn table). 'Measurement equipment antenna' is shown near the test object. A 'Range Antenna' is positioned to the right, connected by a 'Range antenna feeder cable'. Below the chamber, 'Test equipment for monitoring performance' and 'TX Generating interferer' are shown, with lines connecting them to the test object and the range antenna respectively.](25cd06273405d5bc76c751e20d62e61d_img.jpg)
+
+Diagram of the radiated immunity test setup for a BS type 1-O. The setup is inside a shielded anechoic chamber. A 'Test object' (AAS Array) is mounted on a 'Positioner' (turn table). 'Measurement equipment antenna' is shown near the test object. A 'Range Antenna' is positioned to the right, connected by a 'Range antenna feeder cable'. Below the chamber, 'Test equipment for monitoring performance' and 'TX Generating interferer' are shown, with lines connecting them to the test object and the range antenna respectively.
+
+**Figure 16.5.2-1: Example radiated immunity test setup for a *BS type 1-O***
+
+An important difference of the EMC radiated immunity test setup for a *BS type 1-O* as compared with testing of the BS equipped with the antenna connectors is the need for OTA performance parameter monitoring. During EMC RI test the BS is rotated horizontally in order to expose it to the interfering RF electromagnetic field from all directions in horizontal plane.
+
+According to IEC 61000-4-3 [25], all testing of equipment shall be performed in a configuration as close as possible to actual installation conditions. In order to allow electromagnetic susceptibility testing of the maximum surface for *BS type 1-O*, the BS shall be mounted using rack (or pole) mount, if possible.
+
+## 16.5.2 Alternatives to protect *BS type 1-O* during RI test
+
+3GPP has agreed on the use of two mechanisms to protect the BS during RI testing:
+
+- Exclusion bands, or
+- Spatial exclusion.
+
+The combined use of these two alternatives is reflected in both AAS BS EMC specification TS 37.114 [17] and the NR BS EMC specification TS 38.113 [18].
+
+### 16.5.2.1 Exclusion bands
+
+Exclusion bands were considered as a mechanism to protect the receiver from potential damage/undue stress during the RI test of the non-AAS BS products so far, where the exclusion bands represent a range of frequencies over which no tests are made.
+
+During the discussion of Release 15, the need for widening the size of the exclusion bands in TS 37.113 [16], TS 37.114 [17] and TS 38.113 [18] has been recognized. The parameter proposed to get this extension was the boundary of the in-band and out-of-band region, represented by the maximum offset of the out-of-band boundary from the uplink operating band edge (i.e.  $\Delta f_{\text{OOB}}$ ). The value of  $\Delta f_{\text{OOB}}$  was derived considering the width of the NR operating band and was agreed to be:
+
+- 20 MHz, for operating bands narrower than 100 MHz, or
+- 60 MHz, for operating bands wider than 100 MHz.
+
+The above  $\Delta f_{\text{OOB}}$  values considered the use of spatial exclusion during the EMC RI testing.
+
+Before the significant risk to over-dimension the Rx band filter for *BS type 1-O*, the need for using a value higher than  $\Delta f_{\text{OOB}}$  to calculate the exclusion bands size was agreed for the test case with no spatial exclusion being considered. In this case the exclusion band takes into account the width of the operating band as follows:
+
+- 60 MHz, for operating bands narrower than 100 MHz, or
+- 200 MHz, for operating bands wider than 100 MHz.
+
+### 16.5.2.2 Spatial exclusion
+
+According to IEC 61000-4-3 [19], the EMC Radiated Immunity test is performed with the generating antenna facing each side of the BS. When technically justified, some BS can be tested by exposing fewer faces to the generating antenna. For *BS type 1-O* the RI test need to be reduced to fewer angular incidences. This is to protect the BS receiver from being blocked due to received input power levels exceeding the OOB blocking limits during the RI testing. Referring to the IEC 61000-4-3 [19] guidance above, the angular incidence where the front of the *BS type 1-O* is facing the interferer range antenna needs to be omitted, as depicted in figure 16.7.2.2-1.
+
+![Diagram illustrating RI testing directions for BS type 1-O in the horizontal plane. The diagram shows a central 'EUT' (Equipment Under Test) represented by a rectangle. A dashed vertical line to the right of the EUT defines a 'Spatial exclusion zone'. Arrows indicate 'RI testing direction' from the top and bottom, pointing towards the EUT. A horizontal arrow pointing to the right from the EUT is labeled 'EUT radiating direction'. A semi-circular arc on the left side of the EUT represents the front face that is excluded from testing.](2a9813fa664df211b1f5a894fa406bd8_img.jpg)
+
+Diagram illustrating RI testing directions for BS type 1-O in the horizontal plane. The diagram shows a central 'EUT' (Equipment Under Test) represented by a rectangle. A dashed vertical line to the right of the EUT defines a 'Spatial exclusion zone'. Arrows indicate 'RI testing direction' from the top and bottom, pointing towards the EUT. A horizontal arrow pointing to the right from the EUT is labeled 'EUT radiating direction'. A semi-circular arc on the left side of the EUT represents the front face that is excluded from testing.
+
+Figure 16.5.2.2-1: RI testing directions for *BS type 1-O* (horizontal plane depicted)
+
+## 17 Measurement Uncertainty values summary
+
+**Table 17-1: TX Measurement Uncertainty values derivation – FR1**
+
+| Requirement                                                                    | Maximum OTA Test System uncertainty                                                                                                                                                                                                                                                                                                                                                       | Clause |
+|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| Radiated transmit power                                                        | Normal condition:<br>$\pm 1.1$ dB, $f \leq 3$ GHz<br>$\pm 1.3$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                               | 9.2.7  |
+|                                                                                | Extreme condition:<br>$\pm 2.5$ dB, $f \leq 3$ GHz<br>$\pm 2.6$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                              | 9.3.4  |
+| OTA base station output power                                                  | $\pm 1.4$ dB, $f \leq 3$ GHz<br>$\pm 1.5$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                    | 11.2.7 |
+| OTA E-UTRA DL RS power                                                         | $\pm 1.3$ dB, $f \leq 3$ GHz<br>$\pm 1.5$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                    | 9.4.6  |
+| OTA UTRA inner loop power control in the downlink                              | $\pm 0.1$ dB                                                                                                                                                                                                                                                                                                                                                                              | 9.5.6  |
+| OTA UTRA power control dynamic range                                           | $\pm 1.1$ dB                                                                                                                                                                                                                                                                                                                                                                              | 9.5.6  |
+| OTA total power dynamic range                                                  | $\pm 0.3$ dB UTRA<br>$\pm 0.4$ dB E-UTRA & NR                                                                                                                                                                                                                                                                                                                                             | 9.5.6  |
+| OTA UTRA IPDL time mask                                                        | $\pm 0.7$ dB                                                                                                                                                                                                                                                                                                                                                                              | 9..5.6 |
+| OTA RE power control dynamic range (NR)                                        | N/A                                                                                                                                                                                                                                                                                                                                                                                       |        |
+| OTA transmitter OFF power                                                      | $\pm 3.4$ dB, $f \leq 3$ GHz<br>$\pm 3.6$ dB, $3$ GHz $< f \leq 6$ GHz<br>(NOTE 1)                                                                                                                                                                                                                                                                                                        | 13.2.3 |
+| OTA transmitter transient period                                               | N/A                                                                                                                                                                                                                                                                                                                                                                                       |        |
+| OTA frequency error                                                            | $\pm 12$ Hz                                                                                                                                                                                                                                                                                                                                                                               | 9.6.6  |
+| OTA modulation quality                                                         | $\pm 1$ %                                                                                                                                                                                                                                                                                                                                                                                 | 9.7.6  |
+| OTA time alignment error                                                       | $\pm 25$ ns                                                                                                                                                                                                                                                                                                                                                                               | 9.8.5  |
+| OTA occupied bandwidth                                                         | $\pm 100$ kHz, $BW_{\text{Channel}}$ 5 MHz, 10 MHz<br>$\pm 300$ kHz, $BW_{\text{Channel}}$ 15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz<br>$\pm 600$ kHz, $BW_{\text{Channel}}$ 60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz                                                                                                                                                                 | 9.9.6  |
+| OTA ACLR/CACLR                                                                 | $f \leq 3$ GHz<br>$\pm 1$ dB<br><br>$3$ GHz $< f \leq 6$ GHz<br>$\pm 1.2$ dB, $BW \leq 20$ MHz<br>$\pm 1.2$ dB, $BW > 20$ MHz<br><br>Absolute power $\pm 2.2$ dB, $f \leq 3$ GHz<br>Absolute power $\pm 2.7$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                 | 11.3.7 |
+| OTA operating band unwanted emissions (E-UTRA, NR)                             | Absolute power $\pm 1.8$ dB, $f \leq 3$ GHz<br>Absolute power $\pm 2$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                        | 11.4.7 |
+| OTA SEM (UTRA only)                                                            | Absolute power $\pm 1.8$ dB, $f \leq 3$ GHz<br>Absolute power $\pm 2$ dB, $3$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                        | 11.4.7 |
+| OTA transmitter spurious emissions, mandatory requirements                     | $\pm 2.3$ dB, $30$ MHz $< f \leq 6$ GHz<br>$\pm 4.2$ dB, $6$ GHz $< f \leq 26$ GHz                                                                                                                                                                                                                                                                                                        | 12.2.5 |
+| OTA transmitter spurious emissions, protection of BS receiver                  | $\pm 3.1$ dB, $f \leq 3$ GHz<br>$\pm 3.3$ dB, $3$ GHz $< f \leq 4.2$ GHz<br>$\pm 3.4$ dB, $4.2$ GHz $< f \leq 6$ GHz<br>(NOTE 1)                                                                                                                                                                                                                                                          | 13.3.3 |
+| OTA transmitter spurious emissions, additional spurious emissions requirements | $\pm 2.6$ dB, $f \leq 3$ GHz<br>$\pm 3.0$ dB, $3$ GHz $< f \leq 4.2$ GHz<br>$\pm 3.5$ dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                      | 12.4.3 |
+| OTA transmitter spurious emissions, co-location                                | $\pm 3.1$ dB, $f \leq 3$ GHz<br>$\pm 3.3$ dB, $3$ GHz $< f \leq 4.2$ GHz<br>$\pm 3.4$ dB, $4.2$ GHz $< f \leq 6$ GHz<br>(NOTE)                                                                                                                                                                                                                                                            | 13.3.3 |
+| OTA transmitter intermodulation                                                | The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests (11.3 for ACLR, 11.4 for OBUE and 12.2 for TX spurious emissions) which have to be carried out in the presence of the interferer.<br>$\pm 3.2$ dB, $f \leq 3$ GHz<br>$\pm 3.4$ dB, $3$ GHz $< f \leq 4.2$ GHz<br>$\pm 3.5$ dB, $4.2$ GHz $< f \leq 6$ GHz<br>(NOTE 1) | 13.4.3 |
+
+NOTE 1: Fulfilling the criteria for CLTA selection and placement in clause 6.4 is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the co-location test antenna and its alignment as specified in the appropriate measurement uncertainty budgets in this TR shall be used for evaluating the test system uncertainty.
+
+NOTE 2: Test system uncertainty values are applicable for normal condition unless otherwise stated.
+
+**Table 17-2: Tx Measurement Uncertainty values derivation – FR2**
+
+| <b>Requirement</b>                                                                                | <b>Maximum OTA Test System uncertainty</b>                                                               | <b>Clause</b> |
+|---------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|---------------|
+| Radiated transmit power                                                                           | Normal condition:<br>±1.7 dB (24.25 – 29.5 GHz)<br>±2.0 dB (37 – 43.5 GHz)<br>±2.2 dB (43.5 – 48.2 GHz)  | 9.2.7         |
+|                                                                                                   | Extreme condition:<br>±3.1 dB (24.25 – 29.5 GHz)<br>±3.3 dB (37 – 43.5 GHz)<br>±3.5 dB (43.5 – 48.2 GHz) | 9.3.4         |
+| OTA base station output power                                                                     | ±2.1 dB (24.25 – 29.5 GHz)<br>±2.4 dB (37 – 43.5 GHz)<br>±2.6 dB (43.5 – 48.2 GHz)                       | 11.2.7        |
+| OTA RE power control dynamic range                                                                | N/A                                                                                                      |               |
+| OTA total power dynamic range                                                                     | ±0.4 dB                                                                                                  | 9.5.6         |
+| OTA transmitter OFF power                                                                         | ±2.9 dB (24.25 – 29.5 GHz)<br>±3.3 dB (37 – 43.5 GHz)<br>±3.6 dB (43.5 – 48.2 GHz)                       | 9.10.3        |
+| OTA transmitter transient period                                                                  | N/A                                                                                                      |               |
+| OTA frequency error                                                                               | ±12 Hz                                                                                                   | 9.6.6         |
+| OTA modulation quality                                                                            | 1%                                                                                                       | 9.7.6         |
+| OTA time alignment error                                                                          | ±25 ns                                                                                                   | 9.8.5         |
+| OTA occupied bandwidth                                                                            | 600 kHz                                                                                                  | 9.9.6         |
+| OTA ACLR                                                                                          | Relative ACLR:<br>±2.3 dB (24.25 – 29.5 GHz)<br>±2.6 dB (37 – 43.5 GHz)<br>±2.8 dB (43.5 – 48.2 GHz)     | 11.3.7        |
+|                                                                                                   | Absolute ACLR:<br>±2.7 dB (24.25 – 29.5 GHz)<br>±2.7 dB (37 – 43.5 GHz)<br>±2.9 dB (43.5 – 48.2 GHz)     |               |
+| OTA operating band unwanted emissions                                                             | ±2.7 dB (24.25 – 29.5 GHz)<br>±2.7 dB (37 – 43.5 GHz)<br>±2.9 dB (43.5 – 48.2 GHz)                       | 11.4.7        |
+| OTA transmitter spurious emissions, mandatory requirements                                        | ±2.3 dB, 30 MHz ≤ f ≤ 6 GHz<br>±2.7 dB, 6 GHz < f ≤ 43.5 GHz<br>±5.0 dB, 43.5 GHz < f ≤ 60 GHz           | 12.2.5        |
+| OTA transmitter spurious emissions, additional requirements                                       | ±2.3 dB, 30 MHz ≤ f ≤ 6 GHz<br>±2.7 dB, 6 GHz < f ≤ 43.5 GHz<br>±5.0 dB, 43.5 GHz < f ≤ 60 GHz           | 12.2.5        |
+| NOTE: Test system uncertainty values are applicable for normal condition unless otherwise stated. |                                                                                                          |               |
+
+**Table 17-3: RX Measurement Uncertainty values derivation – FR1**
+
+| Requirement                                                                                                                                                                                                                                                                                                                                                                                        | Maximum OTA Test System uncertainty                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Clause |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| OTA sensitivity                                                                                                                                                                                                                                                                                                                                                                                    | ±1.3 dB, $f \leq 3$ GHz<br>±1.4 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±1.6 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.2.7 |
+| OTA reference sensitivity level                                                                                                                                                                                                                                                                                                                                                                    | ±1.3 dB, $f \leq 3$ GHz<br>±1.4 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±1.6 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.3   |
+| OTA dynamic range                                                                                                                                                                                                                                                                                                                                                                                  | ±0.3 dB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 10.4.4 |
+| OTA adjacent channel selectivity                                                                                                                                                                                                                                                                                                                                                                   | ±1.7 dB, $f \leq 3$ GHz<br>±2.1 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±2.4 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.5.4 |
+| In-band blocking (General)                                                                                                                                                                                                                                                                                                                                                                         | ±1.9 dB, $f \leq 3$ GHz<br>±2.2 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±2.5 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.5.4 |
+| In-band blocking (Narrowband)                                                                                                                                                                                                                                                                                                                                                                      | ±1.7 dB, $f \leq 3$ GHz<br>±2.1 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±2.4 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.5.4 |
+| OTA out-of-band blocking (General)                                                                                                                                                                                                                                                                                                                                                                 | $f_{wanted} \leq 3$ GHz:<br>±2.0 dB, $f_{interferer} \leq 3$ GHz<br>±2.1 dB, $3$ GHz $< f_{interferer} \leq 6$ GHz<br>±3.5 dB, $6$ GHz $< f_{interferer} \leq 12.75$ GHz<br><br>$3$ GHz $< f_{wanted} \leq 4.2$ GHz:<br>±2.0 dB, $f_{interferer} \leq 3$ GHz<br>±2.1 dB, $3$ GHz $< f_{interferer} \leq 6$ GHz<br>±3.6 dB, $6$ GHz $< f_{interferer} \leq 12.75$ GHz<br><br>$4.2$ GHz $< f_{wanted} \leq 6$ GHz:<br>±2.2 dB, $f_{interferer} \leq 3$ GHz<br>±2.3 dB, $3$ GHz $< f_{interferer} \leq 6$ GHz<br>±3.6 dB, $6$ GHz $< f_{interferer} \leq 12.75$ GHz | 14.3   |
+| OTA out-of-band blocking (Co-location) (NOTE 1)                                                                                                                                                                                                                                                                                                                                                    | $f_{wanted} \leq 3$ GHz:<br>±3.4 dB, $f_{interferer} \leq 3$ GHz<br>±3.5 dB, $3$ GHz $< f_{interferer} \leq 4.2$ GHz<br>±3.7 dB, $4.2$ GHz $< f_{interferer} \leq 6$ GHz<br><br>$3$ GHz $< f_{wanted} \leq 4.2$ GHz:<br>±3.5 dB, $f_{interferer} \leq 3$ GHz<br>±3.6 dB, $3$ GHz $< f_{interferer} \leq 4.2$ GHz<br>±3.7 dB, $4.2$ GHz $< f_{interferer} \leq 6$ GHz<br><br>$4.2$ GHz $< f_{wanted} \leq 6$ GHz:<br>±3.6 dB, $f_{interferer} \leq 3$ GHz<br>±3.7 dB, $3$ GHz $< f_{interferer} \leq 4.2$ GHz<br>±3.8 dB, $4.2$ GHz $< f_{interferer} \leq 6$ GHz | 13.5.4 |
+| OTA receiver spurious emissions                                                                                                                                                                                                                                                                                                                                                                    | ±2.5 dB, $30$ MHz $\leq f \leq 6$ GHz<br>±4.2 dB, $6$ GHz $< f \leq 26$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 12.3.3 |
+| OTA receiver intermodulation                                                                                                                                                                                                                                                                                                                                                                       | ±2.0 dB, $f \leq 3$ GHz<br>±2.6 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±3.2 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.6.4 |
+| OTA in-channel selectivity                                                                                                                                                                                                                                                                                                                                                                         | ±1.7 dB, $f \leq 3$ GHz<br>±2.1 dB, $3$ GHz $< f \leq 4.2$ GHz<br>±2.4 dB, $4.2$ GHz $< f \leq 6$ GHz                                                                                                                                                                                                                                                                                                                                                                                                                                                            | 10.7.4 |
+| NOTE 1: Fulfilling the criteria for CLTA selection and placement in clause 6.4 is deemed sufficient for the test purposes. When these criteria are met, the measurement uncertainty related to the selection of the co-location test antenna and its alignment as specified in the appropriate measurement uncertainty budget in this TR shall be used for evaluating the test system uncertainty. |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |        |
+| NOTE 2: Test system uncertainty values are applicable for normal condition unless otherwise stated.                                                                                                                                                                                                                                                                                                |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |        |
+
+**Table 17-4: RX Measurement Uncertainty values derivation – FR2**
+
+| Requirement                                                                                       | Maximum OTA Test System uncertainty                                                                     | Clause |
+|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|--------|
+| OTA reference sensitivity level                                                                   | ±2.4 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±2.4 dB, 37 GHz < f ≤ 43.5 GHz<br>±3.5 dB, 43.5 GHz < f ≤ 48.2 GHz | 10.2.7 |
+| OTA adjacent channel selectivity                                                                  | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±3.4 dB, 37 GHz < f ≤ 43.5 GHz<br>±5.1 dB, 43.5 GHz < f ≤ 48.2 GHz | 10.5.4 |
+| OTA in-band blocking (General)                                                                    | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±3.4 dB, 37 GHz < f ≤ 43.5 GHz<br>±5.1 dB, 43.5 GHz < f ≤ 48.2 GHz | 10.5.4 |
+| OTA out-of-band blocking                                                                          | ±3.6 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±3.6 dB, 37 GHz < f ≤ 43.5 GHz<br>±4.5 dB, 43.5 GHz < f ≤ 48.2 GHz | 14.3   |
+| OTA receiver spurious emissions                                                                   | ±2.5 dB, 30 MHz ≤ f ≤ 6 GHz<br>±2.7 dB, 6 GHz < f ≤ 43.5 GHz<br>±5.0 dB, 43.5 GHz < f ≤ 60 GHz          | 12.3.3 |
+| OTA receiver intermodulation                                                                      | ±3.9 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±3.9 dB, 37 GHz < f ≤ 43.5 GHz<br>±5.4 dB, 43.5 GHz < f ≤ 48.2 GHz | 10.6.4 |
+| OTA in-channel selectivity                                                                        | ±3.4 dB, 24.25 GHz < f ≤ 29.5 GHz<br>±3.4 dB, 37 GHz < f ≤ 43.5 GHz<br>±5.1 dB, 43.5 GHz < f ≤ 48.2 GHz | 10.7.4 |
+| NOTE: Test System uncertainty values are applicable for normal condition unless otherwise stated. |                                                                                                         |        |
+
+## 18 Test Tolerance values summary
+
+Considering the methodology described in clause 5.1, Test Tolerance values for all the considered requirements are captured in this clause, based on the maximum accepted test system uncertainty values derived for each specific requirement. Frequency range specific Test Tolerance values are captured in table 18-1.
+
+**Table 18-1: Test Tolerance values derivation, TX FR1**
+
+| Requirement                                                                                 | Test Tolerance (TT <sub>OTA</sub> )                                                                                                               | Clause |
+|---------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| Radiated transmit power                                                                     | Normal condition:<br>±1.1 dB, f ≤ 3 GHz<br>±1.3 dB, 3 GHz < f ≤ 6 GHz                                                                             | 9.2.8  |
+|                                                                                             | Extreme condition:<br>2.5 dB, f ≤ 3 GHz<br>2.6 dB, 3 GHz < f ≤ 6 GHz                                                                              | 9.3.5  |
+| OTA base station output power                                                               | 1.4 dB, f ≤ 3 GHz<br>1.5 dB, 3 GHz < f ≤ 6 GHz                                                                                                    | 11.2.8 |
+| OTA E-UTRA DL RS power                                                                      | 1.3 dB, f ≤ 3 GHz<br>1.5 dB, 3 GHz < f ≤ 6 GHz                                                                                                    | 9.4.7  |
+| OTA UTRA inner loop power control in the downlink                                           | 0.1 dB                                                                                                                                            | 9.5.7  |
+| OTA UTRA power control dynamic range                                                        | 1.1 dB                                                                                                                                            | 9.5.7  |
+| OTA total power dynamic range                                                               | 0.3 dB UTRA<br>0.4 dB E-UTRA & NR                                                                                                                 | 9.5.7  |
+| OTA UTRA IPDL time mask                                                                     | 0.7 dB                                                                                                                                            | 9.5.7  |
+| OTA RE power control dynamic range (NR)                                                     | N/A                                                                                                                                               |        |
+| OTA transmitter OFF power                                                                   | 3.4 dB, f ≤ 3 GHz<br>3.6 dB, 3 GHz < f ≤ 6 GHz<br>(NOTE)                                                                                          | 13.2.4 |
+| OTA transmitter transient period                                                            | N/A                                                                                                                                               |        |
+| OTA frequency error                                                                         | 12 Hz                                                                                                                                             | 9.6.7  |
+| OTA modulation quality                                                                      | 1 %                                                                                                                                               | 9.7.7  |
+| OTA time alignment error                                                                    | 25 ns                                                                                                                                             | 9.8.6  |
+| OTA occupied bandwidth                                                                      | 0 Hz                                                                                                                                              | 9.9.7  |
+| OTA ACLR/CACL                                                                               | Relative:<br>1.0 dB, f ≤ 3 GHz<br>1.2 dB, 3 GHz < f ≤ 6 GHz<br><br>Absolute:<br>0 dB                                                              | 11.3.8 |
+| OTA operating band unwanted emissions (E-UTRA, NR)                                          | Offsets < 10 MHz<br>1.8 dB, f ≤ 3 GHz<br>2 dB, 3 GHz < f ≤ 6 GHz<br><br>Offsets ≥ 10 MHz<br>0 dB                                                  | 11.4.8 |
+| SEM (UTRA only)                                                                             | 1.8 dB, f ≤ 3 GHz<br>2.0 dB, 3 GHz < f ≤ 4.2 GHz                                                                                                  | 11.4.8 |
+| OTA transmitter spurious emissions, mandatory requirements                                  | 0 dB                                                                                                                                              | 12.2.6 |
+| OTA transmitter spurious emissions, protection of BS receiver                               | 3.1 dB, f ≤ 3 GHz<br>3.3 dB, 3 GHz < f ≤ 4.2 GHz<br>3.4 dB, 4.2 GHz < f ≤ 6 GHz                                                                   | 13.3.4 |
+| OTA transmitter spurious emissions, additional spurious emissions requirements              | 2.6 dB, f ≤ 3 GHz<br>3.0 dB, 3 GHz < f ≤ 4.2 GHz<br>3.5 dB, 4.2 GHz < f ≤ 6 GHz<br><br>For co-existence with PHS and public safety bands.<br>0 dB | 12.4.4 |
+| OTA transmitter spurious emissions, co-location                                             | 3.1 dB, f ≤ 3 GHz<br>3.3 dB, 3 GHz < f ≤ 4.2 GHz<br>3.4 dB, 4.2 GHz < f ≤ 6 GHz                                                                   | 13.3.4 |
+| OTA transmitter intermodulation                                                             | 0 dB                                                                                                                                              | 13.4.4 |
+| NOTE: TT <sub>OTA</sub> values are applicable for normal condition unless otherwise stated. |                                                                                                                                                   |        |
+
+**Table 18-2: Test Tolerance values derivation, TX FR2**
+
+| Requirement                                                                                                                                                                                                                                                                                                                                          | Test Tolerance (TT <sub>OTA</sub> )                                                                                                                                                                        | Claus<br>e |
+|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|
+| Radiated transmit power                                                                                                                                                                                                                                                                                                                              | Normal condition:<br>1.7 dB (24.25 – 29.5 GHz)<br>2.0 dB (37 – 43.5 GHz)<br>2.2 dB (43.5 – 48.2 GHz)                                                                                                       | 9.2.8      |
+|                                                                                                                                                                                                                                                                                                                                                      | Extreme condition:<br>3.1 dB (24.25 – 29.5 GHz)<br>3.3 dB (37 – 43.5 GHz)<br>3.5 dB (43.5 – 48.2 GHz)                                                                                                      | 9.3.5      |
+| OTA base station output power                                                                                                                                                                                                                                                                                                                        | 2.1 dB (24.25 – 29.5 GHz)<br>2.4 dB (37 – 43.5 GHz)<br>2.6 dB (43.5 – 48.2 GHz)                                                                                                                            | 11.2.8     |
+| OTA total power dynamic range                                                                                                                                                                                                                                                                                                                        | 0.4 dB                                                                                                                                                                                                     | 9.5.6      |
+| OTA transmitter OFF power                                                                                                                                                                                                                                                                                                                            | 2.9 dB (24.25 – 29.5 GHz)<br>3.3 dB (37 – 43.5 GHz)<br>3.6 dB (43.5 – 48.2 GHz)                                                                                                                            | 9.10.4     |
+| OTA transmitter transient period                                                                                                                                                                                                                                                                                                                     | N/A                                                                                                                                                                                                        |            |
+| OTA frequency error                                                                                                                                                                                                                                                                                                                                  | 12 Hz                                                                                                                                                                                                      | 9.6.6      |
+| OTA modulation quality                                                                                                                                                                                                                                                                                                                               | 1%                                                                                                                                                                                                         | 9.7.6      |
+| OTA time alignment error                                                                                                                                                                                                                                                                                                                             | 25 ns                                                                                                                                                                                                      | 9.8.6      |
+| OTA occupied bandwidth                                                                                                                                                                                                                                                                                                                               | 0 Hz                                                                                                                                                                                                       | 9.9.6      |
+| OTA ACLR                                                                                                                                                                                                                                                                                                                                             | Relative ACLR:<br>2.3 dB (24.25 – 29.5 GHz)<br>2.6 dB (37 – 43.5 GHz)<br>2.8 dB (43.5 – 48.2 GHz)<br><br>Absolute ACLR:<br>2.7 dB (24.25 – 29.5 GHz)<br>2.7 dB (37 – 43.5 GHz)<br>2.9 dB (43.5 – 48.2 GHz) | 11.3.8     |
+| OTA operating band unwanted emissions                                                                                                                                                                                                                                                                                                                | 2.7 dB (24.25 – 29.5 GHz)<br>2.7 dB (37 – 43.5 GHz)<br>2.9 dB (43.5 – 48.2 GHz)<br>(NOTE 2)                                                                                                                | 11.4.8     |
+| OTA transmitter spurious emissions, mandatory requirements                                                                                                                                                                                                                                                                                           | 0 dB                                                                                                                                                                                                       | 12.2.5     |
+| OTA transmitter spurious emissions, additional requirements                                                                                                                                                                                                                                                                                          | NOTE 2                                                                                                                                                                                                     |            |
+| NOTE 1: TT <sub>OTA</sub> values are applicable for normal condition unless otherwise stated.<br>NOTE 2: There may be additional regional regulatory requirements being applicable, tightening the TT <sub>OTA</sub> values to 0 dB, e.g. for co-existence with Earth Exploration Satellite Service. For more details refer to e.g. TS 38.141-2 [6]. |                                                                                                                                                                                                            |            |
+
+**Table 18-3: Test Tolerance values derivation, RX FR1**
+
+| Requirement                            | Test Tolerance (TT <sub>OTA</sub> )                                                                | Claus e |
+|----------------------------------------|----------------------------------------------------------------------------------------------------|---------|
+| OTA sensitivity                        | 1.3 dB, $f \leq 3$ GHz<br>1.4 dB, $3$ GHz $< f \leq 4.2$ GHz<br>1.6 dB, $4.2$ GHz $< f \leq 6$ GHz | 10.2.8  |
+| OTA reference sensitivity level        | 1.3 dB, $f \leq 3$ GHz<br>1.4 dB, $3$ GHz $< f \leq 4.2$ GHz<br>1.6 dB, $4.2$ GHz $< f \leq 6$ GHz | 10.3    |
+| OTA dynamic range                      | 0.3 dB                                                                                             | 10.4.5  |
+| OTA adjacent channel selectivity       | 0 dB                                                                                               | 10.5.5  |
+| OTA in-band blocking (General)         | 0 dB                                                                                               | 10.5.5  |
+| OTA in-band blocking (Narrowband)      | 0 dB                                                                                               | 10.5.5  |
+| OTA out-of-band blocking (General)     | 0 dB                                                                                               | 14.4    |
+| OTA out-of-band blocking (Co-location) | 0 dB                                                                                               | 13.5.4  |
+| OTA receiver spurious emissions        | 0 dB<br>(NOTE 2)                                                                                   | 12.3.4  |
+| OTA receiver intermodulation           | 0 dB                                                                                               | 10.6.5  |
+| OTA in-channel selectivity             | 1.7 dB, $f \leq 3$ GHz<br>2.1 dB, $3$ GHz $< f \leq 4.2$ GHz<br>2.4 dB, $4.2$ GHz $< f \leq 6$ GHz | 10.7.4  |
+
+NOTE 1: TT<sub>OTA</sub> values are applicable for normal condition unless otherwise stated.  
+NOTE 2: From December 2019, the regulation around receiver spurious emissions has been clarified in ERC recommendation 74-01 [25] and the requirement has been updated. Since then OTA RX spurious emissions is a regulatory requirement with TT = 0 (as opposed to the previous agreement with TT = MU).
+
+**Table 18-4: Test Tolerance values derivation, RX FR2**
+
+| Requirement                      | Test Tolerance (TT <sub>OTA</sub> )                                                                                       | Claus e |
+|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|---------|
+| OTA reference sensitivity level  | 2.4 dB, $24.25$ GHz $< f \leq 29.5$ GHz<br>2.4 dB, $37$ GHz $< f \leq 43.5$ GHz<br>3.5 dB, $43.5$ GHz $< f \leq 48.2$ GHz | 10.2.8  |
+| OTA adjacent channel selectivity | 0 dB                                                                                                                      | 10.5.5  |
+| OTA in-band blocking (General)   | 0 dB                                                                                                                      | 10.5.5  |
+| OTA out-of-band blocking         | 0 dB                                                                                                                      | 14.4    |
+| OTA receiver spurious emissions  | 0 dB                                                                                                                      | 12.3.4  |
+| OTA receiver intermodulation     | 0 dB                                                                                                                      | 10.6.5  |
+| OTA in-channel selectivity       | 3.4 dB, $24.25$ GHz $< f \leq 29.5$ GHz<br>3.4 dB, $37$ GHz $< f \leq 43.5$ GHz<br>5.1 dB, $43.5$ GHz $< f \leq 48.2$ GHz | 10.7.5  |
+
+NOTE: TT<sub>OTA</sub> values are applicable for normal condition unless otherwise stated.
+
+## Annex A (informative): Radiated TX measurement error contribution descriptions
+
+### A.1 Indoor Anechoic Chamber
+
+This clause describes measurement uncertainty contributors for TX measurements in Indoor Anechoic Chamber.
+
+NOTE 1: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### A1-1 Positioning misalignment between the BS and the reference antenna
+
+This contribution originates from the misalignment of the manufacturer declared coordinate system reference point of the BS and the phase centre of the reference antenna. The uncertainty makes the space propagation loss between the BS and the receiving antenna at the BS measurement stage (i.e. Stage 2) different from the space propagation loss between the reference antenna and the receiving antenna at the calibration stage (i.e. Stage 1).
+
+#### A1-2 Pointing misalignment between the BS and the receiving antenna
+
+This contribution originates from the misalignment of the testing direction and the *beam peak direction* of the receiving antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beamwidth of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam.
+
+#### A1-3 Quality of quiet zone (normal test conditions)
+
+This contribution originates from a reflectivity level of an anechoic chamber. The reflectivity level is determined from the average standard deviation of the electric field in the quiet zone. By repeating a free space VSWR measurement in  $15^\circ$  grid in elevation and azimuth, 264 standard deviation values in both polarizations are determined. From these values an average standard deviation of electric field in the quiet zone can be calculated from the equation:
+
+Where:
+
+is the number of angular intervals in elevation,
+
+is the number of angular intervals in azimuth, and
+
+is elevation of single measurement .
+
+If an efficiency calibration with omni-directional calibration antenna is performed, the effect of reflectivity level decreases in Stage 1 (i.e. calibration measurement) and may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. Efficiency calibration done with sampling step  $\leq 30^\circ$ , can be considered to have at least four independent samples. may be divided by factor 2 also in Stage 2 (i.e. BS measurement) for the same reason.
+
+It's likely that asymmetry of the field probe will have a very small impact on this measurement uncertainty contributor, however, an upper bound to probe symmetry should be considered.
+
+NOTE 2: This MU contributor is defined for normal test conditions. MU contributor for the quality of QZ in extreme test conditions is defined in A1-17.
+
+#### A1-4 Polarization mismatch between the BS (a) / reference antenna (b) and the receiving antenna
+
+This contribution originates from the misaligned polarization between the BS/reference antenna and the receiving antenna.
+
+#### A1-5 Mutual coupling between the BS(a) / reference antenna (b) and the receiving antenna
+
+This contribution originates from mutual coupling between the BS/reference antenna and the receiving antenna. Mutual coupling degrades not just the antenna efficiency, i.e. the EIRP value, but it can alter the antenna's *radiation pattern* as well. For indoor anechoic chamber, usually the spacing between the BS/reference antenna and the receiving antennas is large enough so that the level of mutual coupling might be negligible.
+
+#### **A1-6 Phase curvature**
+
+This contribution originates from the finite far field measurement distance, which causes phase curvature across the antenna of BS/reference antenna.
+
+#### **A1-7 Impedance mismatch in the receiving chain**
+
+This contribution originates from multiple reflections between the receiving antenna and the power measurement equipment. The multiple reflections can produce an overall reflection that depends not only upon the individual reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **A1-8 Random uncertainty**
+
+The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference BS without changing anything in the measurement set-up.
+
+#### **A1-9 Impedance mismatch between the receiving antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the receiving antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the receiving antenna feed cable and the receiving antenna.
+
+#### **A1-10 Positioning and pointing misalignment between the reference antenna and the receiving antenna**
+
+This contribution originates from reference antenna alignment and pointing error. In this measurement if the maximum gain directions of the reference antenna and the receiving antenna are aligned to each other, this contribution can be considered negligible and therefore set to zero.
+
+#### **A1-11 Impedance mismatch between the reference antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the reference antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the reference antenna feed cable and the reference antenna.
+
+#### **A1-12 Influence of the reference antenna feed cable**
+
+In the calibration Stage 1, the influence of the calibration antenna feed cable is assessed by measurements. A measurement for calibration may be repeated with a reasonably differing routing of the feed cable. Largest difference among the results is entered to the uncertainty budget with a rectangular distribution.
+
+#### **A1-13 Reference antenna feed cable loss measurement uncertainty**
+
+Before performing the calibration, the reference antenna feed cable loss have to be measured. The measurement can be done with a network analyzer to measure its  $S_{21}$  and uncertainty is introduced.
+
+#### **A1-14 Influence of the receiving antenna feed cable**
+
+If the probe antenna is directional (i.e. peak gain  $>+5$  dBi, e.g. horn, LPDA, etc.) and the same probe antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+In other cases a technical study should be done.
+
+#### **A1-15 Uncertainty of the absolute gain of the receiving antenna**
+
+The uncertainty appears in both stages and it is thus considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+#### **A1-16 Frequency flatness of test system**
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+#### **A1-17 Quality of quiet zone (extreme test conditions)**
+
+This contribution is related to the ambient quality of the quiet zone for normal test conditions (i.e. A1-3) which originates from a reflectivity level of an anechoic chamber. The reflectivity level is determined from the average standard deviation of the electric field in the quiet zone. As the environmental enclosure is larger than the BS and the material of the environmental chamber may cause some reflection and refraction the quiet zone flatness will be effected. The quality of the quiet zone for the extreme test is therefore larger that for the ambient due to the environmental enclosures effect.
+
+NOTE 3: This MU contributor is defined for extreme test conditions. MU contributor for the quality of QZ in normal test conditions is defined in A1-3.
+
+#### **A1-18 Wet radome loss variation**
+
+The environmental chamber radome will be an ineffective thermal isolator and will have extreme temperatures on the inside and the OTA chamber ambient temperature on the outside. In such conditions condensation is inevitable. This uncertainty is due to the variation in the radome loss due to condensation on the environmental chamber radome.
+
+#### **A1-19 Radome loss variation**
+
+The environmental chamber radome will affect the path between the BS and the test antenna due to both its insertion loss and also reflection and refraction from the materials surface. The loss is dependent on the material as well as its proximity to the BS. The uncertainty is the residual uncertainty of the total loss after calibration.
+
+#### **A1-20 Change in absorber behaviour**
+
+The environmental chamber will contain RF absorptive material to prevent reflections within the chamber. This RF absorptive material will be subjected to the extreme temperatures inside the environmental chamber and hence its properties will change. This uncertainty accounts for the effect of that change in behavior.
+
+#### **A1-21 Uncertainty of the LNA (FR2 only)**
+
+To maintain a low noise figure for the measurement system (possibly considering the addition of a down conversion mixer for high frequencies) and LNA may be required. The variation in the gain of the LNA after the calibration procedure is accounted for in this uncertainty contribution.
+
+#### **A1-22 Uncertainty of the Mixer (FR2 only)**
+
+Higher frequency emissions beyond the upper frequency range of the measurement equipment require down converting prior to measurement. The uncertainty introduced by the down conversion is accounted for in this uncertainty contribution.
+
+---
+
+## **A.2 Compact Antenna Test Range**
+
+This clause describes measurement uncertainty contributors for TX measurements in Compact Antenna Test Range.
+
+NOTE 1: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### **A2-1 Misalignment and pointing error of BS (a) /calibration antenna (b) (for EIRP)**
+
+This contribution denotes uncertainty in BS/calibration antenna alignment and BS/calibration antenna pointing error. In this measurement the BS/calibration antenna is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The calibration antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the point error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+NOTE 2: This MU contributor used different values for the EIRP measurement and for TRP measurement. Therefore, those two were explicitly differentiated in the MU derivation tables, i.e. A2-1 for EIRP, A2-18 for TRP.
+
+#### **A2-2 Standing wave between BS (a) / calibration antenna (b) and test range antenna**
+
+This value is extracting the uncertainty value and standard deviation of gain ripple coming from standing waves between BS and test range antenna. This value can be captured by moving the BS towards the test range antenna as the standing waves go in and out of phase causing a ripple in measured gain.
+
+#### **A2-3 RF leakage (SGH connector terminated & test range antenna connector cable terminated)**
+
+This contribution denotes noise leaking in to connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between SGH/reference antenna and transmitting equipment.
+
+#### **A2-4 QZ ripple experienced by BS (a) / calibration antenna (b) (normal test conditions)**
+
+This is the quiet zone (QZ) ripple experienced by the BS/calibration antenna during the measurement or calibration phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to the EIRP measurement. The sum of all these reflections from the walls, range reflector (if applicable), roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS/calibration antenna. To capture the full effect of the QZ ripple a distance of  $1\lambda$  should be measured from each of the BS/calibration antenna physical aperture edges, i.e. total QZ distance = physical aperture length +  $2\lambda$ , to ensure the full volume of the QZ is captured in the uncertainty measurement.
+
+NOTE 3: This MU contributor is defined for normal test conditions. MU contributor for the quality of QZ in extreme test conditions is defined in A2-13.
+
+#### **A2-5 Mismatch of receiver chain (i.e. between receiving antenna and measurement receiver (a) / low power receiver (b))**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the receiving antenna and the test receiver equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the receive antenna and also towards the test receiver. The mismatch between the antenna reflection and the receiver reflection can also be calculated. If the same cable is used for calibration Stage 1, this can be considered systematic and negligible.
+
+#### **A2-6 Insertion loss of receiver chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration Stage 1 and the measurement Stage 2, the uncertainty is assumed to be systematic and negligible during the measurement stage. Alternatively, the insertion loss can also be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the BS or calibration antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+#### **A2-7 Influence of the calibration antenna feed cable (i.e. flexing cables, adapters, attenuators, extra pathloss cable & connector repeatability)**
+
+During the calibration phase this cable is used to feed the calibration antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+#### **A2-8 Misalignment positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the calibration antenna is aligned to maximum this contribution can be considered negligible and therefore set to zero.
+
+#### **A2-9 Rotary joints**
+
+If applicable the contribution of this uncertainty the accuracy in changing from azimuth to vertical measurements.
+
+## **A2-10 Miscellaneous uncertainty**
+
+The term 'miscellaneous uncertainty' is used to define all the unknown, unquantifiable, etc. uncertainties associated with EIRP measurements. This term should include truly random effects as well as systematic uncertainties, such as that arising from dissimilarity between the patterns of the reference antenna (SGH) and the BS.
+
+## **A2-11 Switching uncertainty**
+
+The purpose of the switching unit is to switch electromechanically different RF path to different measurement instruments of different measurement modes. The electromechanical switching clearly reduces the errors arising from manual switching work. Switching is also used to measure the path loss values of each polarization component. Even though the electromechanical switching is preferable during path loss and antenna performance measurements, some minor uncertainties can occur when the switch states are programmed to change their polarity.
+
+## **A2-12 Frequency flatness of test system**
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+## **A2-13 Quality of quiet zone (extreme test conditions)**
+
+This contribution is related to the ambient quality of the quiet zone for normal test conditions (A2-4) which originates from a reflectivity level of an anechoic chamber. The reflectivity level is determined from the average standard deviation of the electric field in the quiet zone. As the environmental enclosure is larger than the BS and the material of the environmental chamber may cause some reflection and refraction the quiet zone flatness will be effected. The quality of the quiet zone for the extreme test is therefore larger than for the ambient due to the environmental enclosures effect.
+
+## **A2-14 Wet radome loss variation**
+
+The environmental chamber radome will be an ineffective thermal isolator and will have extreme temperatures on the inside and the OTA chamber ambient temperature on the outside. In such conditions condensation is inevitable. This uncertainty is due to the variation in the radome loss due to condensation on the environmental chamber radome.
+
+## **A2-15 Radome loss variation**
+
+The environmental chamber radome will affect the path between the BS and the test antenna due to both its insertion loss and also reflection and refraction from the materials surface. The loss is dependent on the material as well as its proximity to the BS. The uncertainty is the residual uncertainty of the total loss after calibration.
+
+## **A2-16 Change in absorber behaviour**
+
+The environmental chamber will contain RF absorptive material to prevent reflections within the chamber. This RF absorptive material will be subjected to the extreme temperatures inside the environmental chamber and hence its properties will change. This uncertainty accounts for the effect of that change in behavior.
+
+## **A2-17 Measurement system dynamic range uncertainty**
+
+Uncertainty associated with the addition of each of the directional power measurements to calculate the TRP due to the limited dynamic range of the OTA test system causing an overestimation.
+
+## **A2-18 Misalignment and pointing error of BS (a) /calibration antenna (b) (for TRP)**
+
+This contribution denotes uncertainty in BS/calibration antenna alignment and BS/calibration antenna pointing error and its effect on the TRP calculation. The pointing error for TRP emissions measurement is larger than for EIRP (A2-1).
+
+NOTE 4: This MU contributor used different values for the EIRP measurement and for TRP measurement. Therefore, those two were explicitly differentiated in the MU derivation tables, i.e. A2-1 for EIRP, A2-18 for TRP.
+
+## **A2-19 Uncertainty of the LNA (FR2 only)**
+
+To maintain a low noise figure for the measurement system (possibly considering the addition of a down conversion mixer for high frequencies) and LNA may be required. The variation in the gain of the LNA after the calibration procedure is accounted for in this uncertainty contribution
+
+#### **A2-20 Uncertainty of the mixer (FR2 only)**
+
+Higher frequency emissions beyond the upper frequency range of the measurement equipment require down converting prior to measurement. The uncertainty introduced by the down conversion is accounted for in this uncertainty contribution.
+
+---
+
+### **A.3 Near Field Test Range**
+
+This clause describes measurement uncertainty contributors for TX measurements in Near Field Test Range.
+
+#### **A3-1 Axes intersection**
+
+This is a mechanical uncertainty term and aim to find the uncertainty related with the lateral displacement between the horizontal and vertical axes of the BS positioner. This can result in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-2 Axes orthogonality**
+
+The difference from  $90^\circ$  of the angle between the horizontal and vertical axes also results in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-3 Horizontal pointing**
+
+The horizontal mispointing of the horizontal axis to the probe reference point for  $\Theta=0^\circ$  also results in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-4 Probe vertical position**
+
+The vertical displacement of the probe reference point from the horizontal axis results in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-5 Probe horizontal/vertical pointing**
+
+The horizontal or vertical mispointing of the probe z-axis from the intersection point of the horizontal/vertical axis. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-6 Measurement distance**
+
+This is the knowledge of the distance between the intersection point of the horizontal and vertical axis and probe reference point. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-7 Amplitude and phase drift**
+
+The system drift due to temperature variations the signal at BS location to drift in amplitude and phase. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-8 Amplitude and phase noise**
+
+This uncertainty is due to the noise level of the test range so that the S/N ratio should be determined or measured at the BS location. The noise level is usually measured with a Spectrum Analyzer. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-9 Leakage and crosstalk**
+
+This uncertainty can be addressed by measurements on the actual system setup. The leakage and crosstalk cannot be separated from the random amplitude and phase errors so that the relative importance should be determined. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-10 Amplitude non-linearity**
+
+This uncertainty is the linearity of the receiver used for the measurement. It can be taken from the data sheet of the receiver.
+
+#### **A3-11 Amplitude and phase shift in rotary joint**
+
+This uncertainty is due to the variation of the rotary joint. It can be measured and is assumed to have a Gaussian distribution.
+
+#### **A3-12 Channel balance amplitude and phase**
+
+This uncertainty is relevant for systems which are using dual polarized probes and polarization switches. The amplitude and phase difference between two signal channels of the receiver includes the difference between the probe ports, difference between the channels of the polarization switch, connecting cables and reflection coefficients. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-13 Probe polarization amplitude and phase**
+
+The amplitude and phase of the probe polarization coefficients should be measured. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-14 Probe pattern knowledge**
+
+The probe(s) pattern(s) is assumed to be known so that the BS measurement in near field can be corrected when performing the near field to far field transform. There is no direct dependence between the BS pattern and the probe pattern in near field measurements. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-15 Multiple reflections**
+
+The multiple reflections occur when a portion of the transmitted signal is reflected from the receiving antenna back to the transmitting antenna and re-reflected by the transmitting antenna back to the receiving antenna. This uncertainty can be determined by multiple measurements of the BS when at different distance from the probes. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-16 Room scattering**
+
+As for the multiple reflections, a portion of the transmitted signal is reflected by either the absorbers or other structures in the measurement anechoic chamber before being received by the receiving antenna. This effect can be isolated from the multiple reflections by testing the BS in different positions, separated by  $\lambda/4$  with respect to the anechoic chamber and comparing these measurements with the reference. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-17 BS support scattering**
+
+This is the uncertainty due to the BS supporting structure on the signal level. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-18 Scan area truncation**
+
+This uncertainty does affect this near field measurement. It can be addressed by comparing the measurement result when scanning the full area. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-19 Sampling point offset**
+
+This uncertainty has an influence in near field and far field. It is assumed to have a Gaussian distribution.
+
+#### **A3-20 Spherical mode truncation**
+
+The measured near field is expanded using a finite set of spherical modes. The number of modes is linked to number of samples. The filtering effect generated by the finite number of modes can improve measurement results by removing signals from outside the physical area of the BS. Care should be taken in order to make sure the removed signals are not from the BS itself. This uncertainty is usually negligible.
+
+#### **A3-21 Positioning**
+
+The relative position of the probe array is not ideal. This uncertainty is assumed to have a rectangular distribution.
+
+#### **A3-22 Probe array uniformity**
+
+This is the uncertainty due to the fact that different probes are used for each physical position. Different probes have different *radiation patterns*. Generally, the probe array is calibrated so that the uniformity of the probes is achieved.
+
+#### **A3-23 Mismatch of receiver chain**
+
+If the same chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant  $\rightarrow$  0.00 dB value.
+
+If it is not the case, this uncertainty contribution has to be taken into account and should be measured or determined by the method described in TR 25.914 [24]. This uncertainty is assumed to have a U-shaped distribution.
+
+#### **A3-24 Insertion loss of receiver chain**
+
+It is composed of the following:
+
+- Insertion loss of the probe antenna cable.
+- Insertion loss of the probe antenna attenuator (if used).
+- Insertion loss of RF relays (if used).
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant  $\rightarrow$  0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-25 Uncertainty of the absolute gain of the probe antenna**
+
+This uncertainty appears in the both stages and it is thus considered systematic and constant  $\rightarrow$  0.00 dB value.
+
+#### **A3-26 Measurement repeatability - positioning repeatability**
+
+This uncertainty is due to the repositioning of the BS in the test setup. It can be addressed by repeating the corresponding measurement 5 times. Calculate the standard deviation of the metric obtained and use that as the measurement uncertainty. For tests that require multiple setups, the worst-case standard deviation is used. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-27 Mismatch of receiver chain**
+
+If the same chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant  $\rightarrow$  0.00 dB value.
+
+If it is not the case, each uncertainty contribution has to be taken into account and should be measured or determined and then taking the total of all non-zero mismatch uncertainty contribution from all parts by root-sum-squares (RSS) method. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-28 Insertion loss of receiver chain**
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant  $\rightarrow$  0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-29 Mismatch in the connection of the calibration antenna**
+
+This is the uncertainty from the mismatch in the connection between the system coax cable and the calibration antenna. This uncertainty is from the mismatch between the cable and the reference antenna that is used for calibration. It is determined by the  $S_{11}$  of the reference antenna and the  $S_{11}$  of the cable to which the antenna is connected i.e. if using an SGH antenna for calibration and 10 dB pad is inserted on the cable connecting to the antenna this uncertainty contribution can be considered negligible. This uncertainty is assumed to have a U-shaped distribution.
+
+#### **A3-30 Influence of the calibration antenna feed cable**
+
+This uncertainty is due to the impact of the feeding cable on the radiation properties of the calibration antenna. In case of using either a standard horn or standard gain horn, the impact of the cable is to be considered negligible thus the uncertainty  $\rightarrow$  0.00 dB value. In case of using a dipole-like antenna, the uncertainty should be addressed by measuring this impact. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-31 Influence of the probe antenna cable**
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant  $\rightarrow$  0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+#### **A3-32 Short term repeatability**
+
+It can be addressed by performing a repeatability test of the calibration antenna. This uncertainty is assumed to have a Gaussian distribution.
+
+### A3-33 Frequency flatness of test system
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+---
+
+## A.4 One Dimensional Compact Range
+
+This clause describes measurement uncertainty contributors for TX measurements in One Dimensional Compact Range.
+
+NOTE: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+### A4-1 Misalignment and pointing error of BS
+
+This contribution denotes uncertainty in BS alignment and BS pointing error. In this measurement the BS is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The reference antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the pointing error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+### A4-2 Standing wave between BS (a) / reference antenna (b) and test range antenna
+
+This value is extracting the uncertainty value and standard deviation of gain ripple coming from standing waves between BS and test range antenna. This value can be captured by moving the BS towards the test range antenna as the standing waves go in and out of phase causing a ripple in measured gain.
+
+### A4-3 Quiet zone ripple experienced by BS (a) / reference antenna (b)
+
+This is the quiet zone (QZ) ripple experienced by the BS/reference antenna during the measurement phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to the EIRP measurement. The sum of all these reflections from the walls, range reflector (if applicable), roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS/reference antenna. To capture the full effect of the QZ ripple a distance of  $1\lambda$  must be measured from each of the BS/reference antenna physical aperture edges, i.e. total QZ distance = physical aperture length +  $2\lambda$ , to ensure the full volume of the QZ is captured in the uncertainty measurement.
+
+### A4-4 Phase curvature across the BS antenna (a) / reference antenna (b)
+
+This contribution originates from the finite far field measurement distance, which causes phase curvature across the antenna of BS (a) / reference antenna (b).
+
+### A4-5 Polarization mismatch between BS (a) / reference antenna (b) and receiving antenna
+
+This contribution originates from the misaligned polarization between the BS/reference antenna and the receiving antenna.
+
+### A4-6 Mutual coupling between BS (a) / reference antenna (b) and receiving antenna
+
+This contribution originates from mutual coupling between the BS/reference antenna and the receiving antenna. Mutual coupling degrades not just the antenna efficiency, i.e. the EIRP value, but it can alter the antenna's *radiation pattern* as well. For compact range chamber, usually the spacing between the BS/reference antenna and the receiving antennas is large enough so that the level of mutual coupling might be negligible.
+
+### A4-7 Impedance mismatch in receiving chain
+
+This contribution originates from multiple reflections between the receiving antenna and the measurement equipment. The multiple reflections can produce an overall reflection that depends not only upon the individual reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **A4-8 RF leakage (BS (a) / SGH (b) connector terminated and test range antenna connector cable terminated)**
+
+This contribution denotes noise leaking into connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between SGH/reference antenna and transmitting equipment.
+
+#### **A4-9 Misalignment positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the calibration antenna is aligned to maximum this contribution can be considered negligible and therefore set to zero.
+
+#### **A4-10 Pointing error between reference antenna and test range antenna**
+
+This contribution originates from the misalignment of the testing direction and the *beam peak direction* of the receiving antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beamwidth of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam.
+
+#### **A4-11 Impedance mismatch in path to reference antenna**
+
+This contribution originates from multiple reflections between the reference antenna and the measurement equipment. After appropriate calibration, the measurement equipment may not introduce impedance mismatch error, but the error still happens between the reference antenna feed cable and the reference antenna.
+
+#### **A4-12 Impedance mismatch in path to compact probe**
+
+This contribution originates from multiple reflections between the receiving antenna and the measurement equipment. After appropriate calibration, the measurement equipment may not introduce impedance mismatch error, but the error still happens between the receiving antenna feed cable and the receiving antenna.
+
+#### **A4-13 Influence of reference antenna feed cable (i.e. flexing cables, adapters, attenuators, connector repeatability)**
+
+During the calibration phase this cable is used to feed the reference antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+#### **A4-14 Mismatch of receiver chain (i.e. between receiving antenna and measurement equipment)**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the receiving antenna and the test receiver equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the receive antenna and also towards the test receiver. The mismatch between the antenna reflection and the receiver reflection can also be calculated. If the same cable is used for calibration stage, this can be considered systematic and negligible.
+
+#### **A4-15 Insertion loss of receiver chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration and the measurement stage, the uncertainty is assumed to be systematic and negligible during the measurement stage. Alternatively, the insertion loss can also be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the BS or reference antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+---
+
+## **A.5 General Chamber**
+
+This clause describes the measurement uncertainty contributors for TX measurements in General Chamber.
+
+NOTE: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### A5-1 Positioning misalignment between the BS and the reference antenna
+
+This contribution originates from the misalignment of the manufacturer declared coordinate system reference point of the BS and the phase centre of the reference antenna. The uncertainty makes the space propagation loss between the BS and the receiving antenna at the BS measurement stage (i.e. Stage 2) different from the space propagation loss between the reference antenna and the receiving antenna at the calibration stage (i.e. Stage 1).
+
+#### A5-2 Pointing misalignment between the BS and the receiving antenna
+
+This contribution originates from the misalignment of the testing direction and the *beam peak direction* of the receiving antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beamwidth of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam.
+
+#### A5-3 Quality of quiet zone
+
+This contribution originates from a reflectivity level of an anechoic chamber. The reflectivity level is determined from the average standard deviation of the electric field in the quiet zone. By repeating a free space VSWR measurement in  $15^\circ$  grid in elevation and azimuth, 264 standard deviation values in both polarizations are determined. From these values an average standard deviation of electric field in the quiet zone can be calculated from the equation:
+
+Where:
+
+is the number of angular intervals in elevation,
+
+is the number of angular intervals in azimuth, and
+
+is elevation of single measurement .
+
+If an efficiency calibration with omni-directional calibration antenna is performed, the effect of reflectivity level decreases in Stage 1 (i.e. calibration measurement) and may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. Efficiency calibration done with sampling step  $\leq 30^\circ$ , can be considered to have at least four independent samples. may be divided by factor 2 also in Stage 2 (i.e. BS measurement) for the same reason.
+
+It's likely that asymmetry of the field probe will have a very small impact on this measurement uncertainty contributor, however, an upper bound to probe symmetry should be considered.
+
+#### A5-4 Polarization mismatch between the BS (a) /reference antenna (b) and the receiving antenna
+
+This contribution originates from the misaligned polarization between the BS/reference antenna and the receiving antenna.
+
+#### A5-5 Mutual coupling between the BS (a) /reference antenna (b) and the receiving antenna
+
+This contribution originates from mutual coupling between the BS/reference antenna and the receiving antenna. Mutual coupling degrades not just the antenna efficiency, i.e. the EIRP value, but it can alter the antenna's *radiation pattern* as well. For indoor anechoic chamber, usually the spacing between the BS/reference antenna and the receiving antennas is large enough so that the level of mutual coupling might be negligible.
+
+#### A5-6 Phase curvature across the BS antenna (a) /reference antenna (b)
+
+This contribution originates from the finite far field measurement distance, which causes phase curvature across the antenna of BS (a) /reference antenna (b).
+
+#### A5-7 Impedance mismatch in the receiving chain
+
+This contribution originates from multiple reflections between the receiving antenna and the power measurement equipment. The multiple reflections can produce an overall reflection that depends not only upon the individual
+
+reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **A5-8 Random uncertainty**
+
+The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference BS without changing anything in the measurement set-up.
+
+#### **A5-9 Impedance mismatch between the receiving antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the receiving antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the receiving antenna feed cable and the receiving antenna.
+
+#### **A5-10 Positioning and pointing misalignment between the reference antenna and the receiving antenna**
+
+This contribution originates from reference antenna alignment and pointing error. In this measurement if the maximum gain directions of the reference antenna and the receiving antenna are aligned to each other, this contribution can be considered negligible and therefore set to zero.
+
+#### **A5-11 Impedance mismatch between the reference antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the reference antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the reference antenna feed cable and the reference antenna.
+
+#### **A5-12 Influence of the reference antenna feed cable**
+
+In the calibration Stage 1, the influence of the calibration antenna feed cable is assessed by measurements. A measurement for calibration may be repeated with a reasonably differing routing of the feed cable. Largest difference among the results is entered to the uncertainty budget with a rectangular distribution.
+
+#### **A5-13 Reference antenna feed cable loss measurement uncertainty**
+
+Before performing the calibration, the reference antenna feed cable loss have to be measured. The measurement can be done with a network analyzer to measure its  $S_{21}$  and uncertainty is introduced.
+
+#### **A5-14 Influence of the receiving antenna feed cable**
+
+If the probe antenna is directional (i.e. peak gain  $>+5$  dBi, e.g. horn, LPDA, etc.) and the same probe antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+In other cases a technical study should be done.
+
+#### **A5-15 Uncertainty of the absolute gain of the receiving antenna**
+
+The uncertainty appears in both stages and it is thus considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+#### **A5-16 Frequency flatness of test system**
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+#### **A5-17 Measurement antenna frequency variation**
+
+For wide band measurement the measurement *antenna gain* will vary considerably over frequency. The gain can be calibrated however variation may still remain between calibration frequency steps. This uncertainty accounts for the variation between the calibrated steps.
+
+#### **A5-18 FSPL estimation error**
+
+For wide band measurement the measurement free space path loss in the chamber will vary with frequency. The loss can be calibrated however this uncertainty accounts for the variation between the calibrated steps.
+
+#### **A5-19 Measurement system dynamic range uncertainty**
+
+Uncertainty associated with the addition of each of the directional power measurements to calculate the TRP due to the limited dynamic range of the OTA test system causing an overestimation.
+
+#### **A5-20 Reflections in anechoic chamber**
+
+Uncertainty associated with the reflections in the chamber changing the coupling between the BS and the CLTA.
+
+---
+
+## **A.6 Reverberation Chamber**
+
+This clause describes measurement uncertainty contributors for TX measurements in Reverberation Chamber.
+
+#### **A6-1 Impedance mismatch in the receiving chain**
+
+This contribution originates from multiple reflections between the receiving antenna and the power measurement equipment. The multiple reflections can produce an overall reflection that depends not only upon the individual reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **A6-2 Random uncertainty**
+
+The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference BS without changing anything in the measurement set-up.
+
+#### **A6-3 Reference antenna radiation efficiency**
+
+This contribution is a residue of uncertainty of reference antenna radiation efficiency after calibration.
+
+#### **A6-4 Mean value estimation of reference antenna mismatch efficiency**
+
+This contribution originates from the error of the estimated mean related to the use of a finite number of samples in the measurement of the reference antenna mismatch efficiency. The mean value estimation is calculated as  $\bar{x}$  where  $s$  is the standard deviation of the series of measured values.
+
+#### **A6-5 Influence of the reference antenna feed cable**
+
+Before performing the calibration, the reference antenna feed cable loss has to be measured. The measurement can be done with a network analyzer to measure its  $S_{21}$  and uncertainty is introduced.
+
+#### **A6-6 Mean value estimation of transfer function**
+
+This contribution originates from the error of the estimated mean related to the use of a finite number of samples in the measurement of the transfer function. The mean value estimation is calculated as  $\bar{x}$  where  $s$  is the standard deviation of the series of measured values.
+
+#### **A6-7 Uniformity of transfer function**
+
+Standard deviation over BS positions and rotations of the transfer function. This uncertainty expresses the variations of measured TRP values with respect to translations and rotations of the BS. Ideally, the TRP does neither depend on translations nor rotations of the BS.
+
+---
+
+## **A.7 Plane Wave Synthesizer**
+
+This clause describes measurement uncertainty contributors for TX measurements in Plane Wave Synthesizer.
+
+**NOTE:** Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### **A7-1 Misalignment and pointing error of BS (a) /calibration antenna (b)**
+
+This contribution denotes uncertainty in BS/calibration antenna alignment and BS/calibration antenna pointing error. In this measurement the BS/calibration antenna is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The calibration antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the point error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+#### **A7-2 Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna (a) / calibration antenna (b)**
+
+This value covers the effect of standing wave between BS or calibration antenna and the test range antenna, but also counts for the PWS imperfect field synthesis over distance. This value can be captured by moving the BS or calibration antenna towards the test range antenna.
+
+#### **A7-3 RF leakage (calibration antenna connector terminated)**
+
+This contribution denotes noise leaking in to connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between reference antenna and transmitting equipment.
+
+#### **A7-4 QZ ripple experienced by BS (a) / calibration antenna (b)**
+
+This is the quiet zone (QZ) ripple experienced by the BS/reference antenna during the measurement phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to measurements. The sum of all these reflections from the walls, roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS/reference antenna.
+
+#### **A7-5 Miscellaneous uncertainty**
+
+The term 'miscellaneous uncertainty' is used to define all the unknown, unquantifiable, etc. uncertainties associated with EIRP measurements. This term should include truly random effects as well as systematic uncertainties, such as that arising from dissimilarity between the patterns of the reference antenna and the BS.
+
+#### **A7-6 Mismatch (i.e. reference antenna, network analyser and reference cable)**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the receiving antenna and the test receiver equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the receive antenna and also towards the test receiver. The mismatch between the antenna reflection and the receiver reflection can also be calculated. If the same cable is used for calibration Stage 1, this can be considered systematic and negligible.
+
+#### **A7-7 Insertion loss of receiver chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration Stage 1 and the measurement Stage 2, the uncertainty is assumed to be systematic and negligible during the measurement stage. Alternatively, the insertion loss can also be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the BS or calibration antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+#### **A7-8 Influence of the calibration antenna feed cable (i.e. flexing cables, adapters, attenuators, extra pathloss cable & connector repeatability)**
+
+During the calibration phase this cable is used to feed the calibration antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+#### **A7-9 Misalignment of positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the calibration antenna is aligned to maximum this contribution can be considered negligible and therefore set to zero.
+
+#### **A7-10 Rotary joints**
+
+If applicable, this uncertainty term corresponds to the accuracy in changing from azimuth to vertical measurements.
+
+#### **A7-11 Switching uncertainty**
+
+The purpose of the switching unit is to switch electromechanically different RF path to different measurement instruments of different measurement modes. The electromechanical switching clearly reduces the errors arising from manual switching work. Switching is also used to measure the path loss values of each polarization component. Even though the electromechanical switching is preferable during path loss and antenna performance measurements, some minor uncertainties can occur when the switch states are programmed to change their polarity.
+
+#### **A7-12 Field repeatability**
+
+Each execution of field calibration of the measurement *antenna array* to find the PWS settings provides a slightly different set of settings for the RF components for each antenna path. This results in variation of the synthesized plane wave in the QZ and variation of PWS antenna to reference antenna coupling. This variation is described by field repeatability term.
+
+#### **A7-13 Frequency flatness of test system**
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+#### **A7-14 System non-linearity**
+
+This uncertainty term is calculated as RSS of the following items, assuming a rectangular distribution:
+
+- System non-linearity in time. This is assessed by repeated measurements over a period of time (e.g. 60 minutes) for the same reference power transmitted by the reference antenna. The largest difference between the results is recorded as the uncertainty.
+- System non-linearity in power. This is assessed by repeated measurements over a range of transmitted powers. The largest delta between the increments on the receiving side versus the transmitting side is recorded as the uncertainty.
+
+## Annex B (informative): Radiated RX measurement error contribution descriptions
+
+### B.1 Indoor Anechoic Chamber
+
+This clause describes measurement uncertainty contributors for RX measurements in Indoor Anechoic Chamber.
+
+NOTE: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### B1-1 Positioning misalignment between the BS and the reference antenna
+
+This contribution originates from the misalignment of the manufacturer declared coordinate system reference point of the BS and the phase centre of the reference antenna. The uncertainty makes the space propagation loss between the BS and the transmitting antenna at the BS measurement stage (i.e. Stage 2) different from the space propagation loss between the reference antenna and the transmitting antenna at the calibration stage (i.e. Stage 1).
+
+#### B1-2 Pointing misalignment between the BS and the transmitting antenna
+
+This contribution originates from the misalignment of the testing direction and the *beam peak direction* of the transmitting antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beamwidth of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam.
+
+#### B1-3 Quality of quiet zone
+
+This contribution originates from a reflectivity level of an anechoic chamber. The reflectivity level is determined from the average standard deviation of the electric field in the quiet zone. By repeating a free space VSWR measurement in 15 ° grid in elevation and azimuth, 264 standard deviation values in both polarizations are determined. From these values an average standard deviation of electric field in the quiet zone can be calculated from the equation:
+
+where:
+
+is the number of angular intervals in elevation,
+
+is the number of angular intervals in azimuth, and
+
+is elevation of single measurement .
+
+If an efficiency calibration with omni-directional calibration antenna is performed, the effect of reflectivity level decreases in Stage 1 (i.e. calibration measurement) and may be divided by factor 2. This is due to correcting impact of data averaging in this type of calibration. Efficiency calibration done with sampling step  $\leq 30^\circ$ , can be considered to have at least four independent samples. may be divided by factor 2 also in stage 2 (i.e. BS measurement) for the same reason.
+
+It's likely that asymmetry of the field probe will have a very small impact on this measurement uncertainty contributor, however, an upper bound to probe symmetry should be considered.
+
+#### B1-4 Polarization mismatch between the BS (a) / reference antenna (b) and the transmitting antenna
+
+This contribution originates from the misaligned polarization between the BS (a) /reference antenna (b) and the transmitting antenna.
+
+#### B1-5 Mutual coupling between the BS (a) /reference antenna (b) and the transmitting antenna
+
+This contribution originates from mutual coupling between the BS (a) /reference antenna (b) and the transmitting antenna. Mutual coupling degrades not just the antenna efficiency, but it can alter the antenna's *radiation pattern* as
+
+well. For indoor anechoic chamber, usually the spacing between the transmitting antenna and the BS/reference antenna is large enough so that the level of mutual coupling might be negligible.
+
+#### **B1-6 Phase curvature**
+
+This contribution originates from the finite far-field measurement distance, which causes phase curvature across the antenna of the BS/reference antenna.
+
+#### **B1-7 Impedance mismatch in the transmitting chain**
+
+This contribution originates from multiple reflections between the transmitting antenna and the signal generator. The multiple reflections can produce an overall reflection that depends not only upon the individual reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **B1-8 Random uncertainty**
+
+The random uncertainty characterizes the undefined and miscellaneous effects which cannot be forecasted. One can estimate this type of uncertainty with a repeatability test by making a series of repeated measurement with a reference BS without changing anything in the measurement set-up.
+
+#### **B1-9 Impedance mismatch between the transmitting antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the transmitting antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the transmitting antenna feed cable and the transmitting antenna.
+
+#### **B1-10 Positioning and pointing misalignment between the reference antenna and the transmitting antenna**
+
+This contribution originates from reference antenna alignment and pointing error. In this measurement if the maximum gain direction of the reference antenna and the transmitting antenna are aligned to each other, this contribution can be considered negligible and therefore set to zero.
+
+#### **B1-11 Impedance mismatch between the reference antenna and the network analyzer**
+
+This contribution originates from multiple reflections between the reference antenna and the network analyzer. After appropriate calibration, the network analyzer may not introduce impedance mismatch error, but the error still happens between the transmitting antenna feed cable and the transmitting antenna.
+
+#### **B1-12 Influence of the reference antenna feed cable**
+
+In the calibration Stage 1, the influence of the calibration antenna feed cable is assessed by measurements. A measurement for calibration may be repeated with a reasonably differing routing of the feed cable. Largest difference among the results is entered to the uncertainty budget with a rectangular distribution.
+
+#### **B1-13 Reference antenna feed cable loss measurement uncertainty**
+
+Before performing the calibration, the reference antenna feed cable loss have to be measured. The measurement can be done with a network analyzer to measure its  $S_{21}$  and uncertainty is introduced.
+
+#### **B1-14 Influence of the transmitting antenna feed cable**
+
+If the probe antenna is directional (i.e. peak gain  $>+5$  dBi e.g. horn, LPDA, etc.) and the same probe antenna cable configuration is used for both stages, the uncertainty is considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+#### **B1-15 Uncertainty of the absolute gain of the transmitting antenna**
+
+The uncertainty appears in both stages and it is thus considered systematic and constant  $\rightarrow 0.00$  dB value.
+
+---
+
+## **B.2 Compact Antenna Test Range**
+
+This clause describes measurement uncertainty contributors for RX measurements in Compact Antenna Test Range.
+
+NOTE: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+#### **B2-1 Misalignment and pointing error of BS (a) /calibration antenna (b)**
+
+This contribution denotes uncertainty in BS (a) /calibration antenna (b) alignment and BS (a) /calibration antenna (b) pointing error. In this measurement the BS (a) /calibration antenna (b) is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The calibration antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the point error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+#### **B2-2 Standing wave between BS and test range antenna**
+
+This value is extracting the uncertainty value and standard deviation of gain ripple coming from standing waves between BS and test range antenna. This value can be captured by moving the BS towards the test range antenna as the standing waves go in and out of phase causing a ripple in measured gain.
+
+#### **B2-3 RF leakage & dynamic range, test range antenna cable connector terminated**
+
+This contribute denotes noise leaking in to connectors and cables between test range antenna and receiving equipment.
+
+#### **B2-4 QZ ripple experienced by BS (a) /calibration antenna (b)**
+
+This is the quiet zone ripple experienced by the BS (a) /calibration antenna (b) during the measurement phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to the EIS measurement. The sum of all these reflections from the walls, roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS (a) /calibration antenna (b). To capture the full effect of the QZ ripple a distance of  $1\lambda$  should be measured from each of the BS (a) /calibration antenna (b) physical aperture edges, i.e. total QZ distance = physical aperture length +  $2\lambda$ , to ensure the full volume of the QZ is captured in the uncertainty measurement.
+
+#### **B2-5 Mismatch of transmit chain (i.e. between transmitting measurement antenna and BS)**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the transmitting antenna and the signal generation equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the transmit antenna and also towards the test signal generator equipment. The mismatch between the antenna reflection and the transmit reflection can also be calculated.
+
+#### **B2-6 Insertion loss of transmit chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration Stage 1 and the BS measurement Stage 2, the uncertainty is assumed to be systematic. Alternatively, the insertion loss can also be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the measurement antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+#### **B2-7 RF leakage (SGH connector terminated & test range antenna connector terminated)**
+
+This contribution denotes noise leaking in to connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between SGH/reference antenna and transmitting equipment.
+
+#### **B2-8 Influence of the calibration antenna feed cable (i.e. flexing cables, adapters, attenuators & connector repeatability)**
+
+During the calibration phase this cable is used to feed the calibration antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+### **B2-9 Miscellaneous uncertainty**
+
+The term 'miscellaneous uncertainty' is used to define all the unknown, unquantifiable, etc. uncertainties associated with EIRP measurements. This term should include truly random effects as well as systematic uncertainties, such as that arising from dissimilarity between the patterns of the reference antenna (SGH) and the BS.
+
+### **B2-10 Rotary joints**
+
+If applicable the contribution of this uncertainty is the accuracy in changing from azimuth to vertical measurements.
+
+### **B2-11 Misalignment positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the calibration antenna is aligned to the maximum then this contribution can be considered negligible and therefore set to zero.
+
+### **B2-12 Standing wave between SGH and test range antenna**
+
+This value is extracting the uncertainty value and standard deviation of gain ripple coming from standing waves between BS and test range antenna. This value can be captured by moving the BS towards the test range antenna as the standing waves go in and out of phase causing a ripple in measured gain.
+
+### **B2-13 Switching uncertainty**
+
+The purpose of the switching unit is to switch electromechanically different RF path to different measurement instruments of different measurement modes. The electromechanical switching clearly reduces the errors arising from manual switching work. Switching is also used to measure the path loss values of each polarization component. Even though the electromechanical switching is preferable during path loss and antenna performance measurements, some minor uncertainties can occur when the switch states are programmed to change their polarity.
+
+---
+
+## **B.3 Near Field Test Range**
+
+This clause describes measurement uncertainty contributors for RX measurements in Near Field Test Range.
+
+### **B3-1 Axes intersection**
+
+This is a mechanical uncertainty term and aim to find the uncertainty related with the lateral displacement between the horizontal and vertical axes of the BS positioner. This can result in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-2 Axes orthogonality**
+
+The difference from 90 ° of the angle between the horizontal and vertical axes also results in sampling the field on a non ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-3 Horizontal pointing**
+
+The horizontal mispointing of the horizontal axis to the probe reference point for  $\Theta = 0^\circ$  also results in sampling the field on a non-ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-4 Probe vertical position**
+
+The vertical displacement of the probe reference point from the horizontal axis results in sampling the field on a non ideal sphere. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-5 Probe horizontal/vertical pointing**
+
+The horizontal or vertical mispointing of the probe z-axis from the intersection point of the horizontal/vertical axis. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-6 Measurement distance**
+
+This is the knowledge of the distance between the intersection point of the horizontal and vertical axis and probe reference point. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-7 Amplitude and phase drift**
+
+The system drift due to temperature variations causes the signal at BS location to drift in amplitude and phase. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-8 Amplitude and phase noise**
+
+This uncertainty is due to the noise level of the test range so that the S/N ratio should be determined or measured at the BS location. The noise level is usually measured with a spectrum analyzer. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-9 Leakage and crosstalk**
+
+This uncertainty can be addressed by measurements on the actual system setup. The leakage and crosstalk cannot be separated from the random amplitude and phase errors so that the relative importance should be determined. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-10 Amplitude non-linearity**
+
+This uncertainty is the linearity of the receiver used for the measurement. It can be taken from the data sheet of the receiver.
+
+### **B3-11 Amplitude and phase shift in rotary joint**
+
+This uncertainty is due to the variation of the rotary joint. It can be measured and is assumed to have a Gaussian distribution.
+
+### **B3-12 Channel balance amplitude and phase**
+
+This uncertainty is relevant for systems which are using dual polarized probes and polarization switches. The amplitude and phase difference between two signal channels of the receiver includes the difference between the probe ports, difference between the channels of the polarization switch, connecting cables and reflection coefficients. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-13 Probe polarization amplitude and phase**
+
+The amplitude and phase of the probe polarization coefficients should be measured. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-14 Probe pattern knowledge**
+
+The probe(s) pattern(s) is assumed to be known so that the BS measurement in near field can be corrected when performing the near field to far field transform. There is no direct dependence between the BS pattern and the probe pattern in near field measurements. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-15 Multiple reflections**
+
+The multiple reflections occur when a portion of the transmitted signal is reflected from the receiving antenna back to the transmitting antenna and re-reflected by the transmitting antenna back to the receiving antenna. This uncertainty can be determined by multiple measurements of the BS when at different distance from the probes. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-16 Room scattering**
+
+As for the multiple reflections, a portion of the transmitted signal is reflected by either the absorbers or other structures in the measurement anechoic chamber before being received by the receiving antenna. This effect can be isolated from the multiple reflections by testing the BS in different positions, separated by  $\lambda/4$  with respect to the anechoic chamber and comparing these measurements with the reference. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-17 BS support scattering**
+
+This is the uncertainty due to the BS supporting structure on the signal level. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-18 Scan area truncation**
+
+This uncertainty does affect the near field measurement. It can be addressed by comparing the measurement result when scanning the full area. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-19 Sampling point offset**
+
+This uncertainty has an influence in near field and far field. It is assumed to have a Gaussian distribution.
+
+### **B3-20 Mode truncation**
+
+The measured near field is expanded using a finite set of spherical modes. The number of modes is linked to number of samples. The filtering effect generated by the finite number of modes can improve measurement results by removing signals from outside the physical area of the BS. Care should be taken in order to make sure the removed signals are not from the BS itself. This uncertainty is usually negligible.
+
+### **B3-21 Positioning**
+
+The relative position of the probe array is not ideal. This uncertainty is assumed to have a rectangular distribution.
+
+### **B3-22 Probe array uniformity**
+
+This is the uncertainty due to the fact that different probes are used for each physical position. Different probes have different *radiation patterns*. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-23 Mismatch of transmitter chain**
+
+If the same chain configuration (including the vector signal generator; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant → 0.00 dB value.
+
+If it is not the case, this uncertainty contribution has to be taken into account and should be measured or determined by the method described in TR 25.914 [24]. This uncertainty is assumed to have a U-shaped distribution.
+
+### **B3-24 Insertion loss of transmitter chain**
+
+It is composed of the following:
+
+- Insertion loss of the probe antenna cable.
+- Insertion loss of the probe antenna attenuator (if used).
+- Insertion loss of RF relays (if used).
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant → 0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-25 Uncertainty of the absolute gain of the probe antenna**
+
+This uncertainty appears in the both stages and it is thus considered systematic and constant → 0.00 dB value.
+
+### **B3-26 Measurement repeatability - positioning repeatability**
+
+This uncertainty is due to the repositioning of the BS in the test setup. It can be addressed by repeating the corresponding measurement 10 times. Calculate the standard deviation of the metric obtained and use that as the measurement uncertainty. For tests that require multiple setups, the worst-case standard deviation is used. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-27 Mismatch of transmitter chain**
+
+If the same chain configuration (including the measurement receiver; the probe antenna and other elements) is used in both stages, the uncertainty is considered systematic and constant → 0.00 dB value.
+
+If it is not the case, this uncertainty contribution has to be taken into account and should be measured or determined by the method described in TR 25.914 [24]. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-28 Insertion loss of transmitter chain**
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant → 0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-29 Mismatch in the connection of the calibration antenna**
+
+This is the uncertainty from the mismatch in the connection between the system coax cable and the calibration antenna. It should be measured or determined by the method described in TR 25.914 [24]. This uncertainty is assumed to have a U-shaped distribution.
+
+### **B3-30 Influence of the calibration antenna feed cable**
+
+This uncertainty is due to the impact of the feeding cable on the radiation properties of the calibration antenna. In case of using either a standard horn or standard gain horn, the impact of the cable is to be considered negligible thus the uncertainty  $\rightarrow$  0.00 dB value. In case of using a dipole-like antenna, the uncertainty should be addressed by measuring this impact. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-31 Influence of the probe antenna cable**
+
+If the same chain configuration is used for measurement and calibration, the uncertainty due to the above components is considered systematic and constant  $\rightarrow$  0.00 dB value. This uncertainty is assumed to have a Gaussian distribution.
+
+### **B3-32 Short term repeatability**
+
+It can be addressed by performing a repeatability test of the calibration antenna. This uncertainty is assumed to have a Gaussian distribution.
+
+---
+
+## **B.4 One Dimensional Compact Range**
+
+This clause describes measurement uncertainty contributors for RX measurements in One Dimensional Compact Range.
+
+NOTE: Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+### **B4-1 Misalignment BS and pointing error**
+
+This contribution denotes uncertainty in BS alignment and BS pointing error. In this measurement the BS is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The reference antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the pointing error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+### **B4-2 Standing wave between BS (a) /reference antenna (b) and test range antenna**
+
+This value is extracting the uncertainty value and standard deviation of gain ripple coming from standing waves between BS/reference antenna and test range antenna. This value can be captured by moving the BS (a) /reference antenna (b) towards the test range antenna as the standing waves go in and out of phase causing a ripple in measured gain.
+
+### **B4-3 Quiet zone ripple experienced by BS (a) /reference antenna (b)**
+
+This is the quiet zone (QZ) ripple experienced by the BS (a) / reference antenna (b) during the measurement phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to the EIS measurement. The sum of all these reflections from the walls, roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS (a) / reference antenna (b). To capture the full effect of the QZ ripple a distance of  $1\lambda$  must be measured from each of the BS (a) / reference antenna (b) physical aperture edges, i.e. total QZ distance = physical aperture length +  $2\lambda$ , to ensure the full volume of the QZ is captured in the uncertainty measurement.
+
+### **B4-4 Phase curvature**
+
+This contribution originates from the finite far-field measurement distance, which causes phase curvature across the antenna of the BS/reference antenna.
+
+#### **B4-5 Polarization mismatch between BS (a) /reference antenna (b) and transmitting antenna**
+
+This contribution originates from the misaligned polarization between the BS (a) /reference antenna (b) and the transmitting antenna.
+
+#### **B4-6 Mutual coupling between BS (a) /reference antenna (b) and transmitting antenna**
+
+This contribution originates from mutual coupling between the BS (a) /reference antenna (b) and the transmitting antenna. Mutual coupling degrades not just the antenna efficiency, but it can alter the antenna's *radiation pattern* as well. For compact range chamber, usually the spacing between the transmitting antenna and the BS (a) /reference antenna (b) is large enough so that the level of mutual coupling might be negligible.
+
+#### **B4-7 Impedance mismatch in transmitting chain**
+
+This contribution originates from multiple reflections between the transmitting antenna and the signal generator. The multiple reflections can produce an overall reflection that depends not only upon the individual reflections of each part but their reflective interactions as well. The combination loss by the overall reflection can be higher or lower than individual loss by multiple reflections. The combination loss is called the mismatch error and leads to the measurement uncertainty.
+
+#### **B4-8 RF leakage and dynamic range**
+
+This contribute denotes noise leaking into connectors and cables between test range antenna and receiving equipment.
+
+#### **B4-9 Misalignment positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the reference antenna is aligned to the maximum then this contribution can be considered negligible and therefore set to zero.
+
+#### **B4-10 Pointing error between reference antenna and test range antenna**
+
+This contribution originates from the misalignment of the testing direction and the *beam peak direction* of the transmitting antenna due to imperfect rotation operation. The pointing misalignment may happen in both azimuth and vertical directions and the effect of the misalignment depends highly on the beamwidth of the beam under test. The same level of misalignment results in a larger measurement error for a narrower beam.
+
+#### **B4-11 Impedance mismatch in path to reference antenna**
+
+This contribution originates from multiple reflections between the reference antenna and the measurement equipment. After appropriate calibration, the measurement equipment may not introduce impedance mismatch error, but the error still happens between the reference antenna feed cable and the reference antenna.
+
+#### **B4-12 Impedance mismatch in path to compact probe**
+
+This contribution originates from multiple reflections between the transmitting antenna and the measurement equipment. After appropriate calibration, the measurement equipment may not introduce impedance mismatch error, but the error still happens between the transmitting antenna feed cable and the transmitting antenna.
+
+#### **B4-13 Influence of reference antenna feed cable (flexing cables, adapters, attenuators and connector repeatability)**
+
+During the calibration phase this cable is used to feed the reference antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+#### **B4-14 Mismatch of transmitter chain (i.e. between transmitting measurement antenna and BS)**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the transmitting antenna and the signal generation equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the transmit antenna and also towards the test signal generator equipment. The mismatch between the antenna reflection and the transmit reflection can also be calculated.
+
+#### **B4-15 Insertion loss of transmitter chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration and the BS measurement stage, the uncertainty is assumed to
+
+be systematic. Alternatively, the insertion loss can be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the measurement antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+#### **B4-16 RF leakage (SGH connector terminated and test range antenna connector terminated)**
+
+This contribution denotes noise leaking into connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between SGH/reference antenna and transmitting equipment.
+
+---
+
+## **B.5 Plane Wave Synthesizer**
+
+This clause describes measurement uncertainty contributors for RX measurements in Plane Wave Synthesizer.
+
+**NOTE:** Several MU contributor descriptions are defined in a way combining both BS for the measurement stage and calibration/reference antenna for calibration stage, e.g. for A1-4 this contribution is denoted as A1-4a for polarization mismatch between the BS and the receiving antenna, and as A1-4b for polarization mismatch between the reference antenna and the receiving antenna.
+
+### **B5-1 Misalignment and pointing error of BS (a) /calibration antenna (b)**
+
+This contribution denotes uncertainty in BS/calibration antenna alignment and BS/calibration antenna pointing error. In this measurement the BS/calibration antenna is aligned to maximum, also allowing for a zero contribution for polarization mismatch uncertainty. By adjusting for maximums to align, this contribution can be a small contribution. The calibration antenna's phase centre and polarization purity changes slightly according to the frequency. Therefore, there should be some uncertainty reserved for this. To ensure that the point error is at a minimal, this contribution should be captured using the antenna pattern cut which is broadest (in the case of the BS this would most likely be in the azimuth domain).
+
+### **B5-2 Longitudinal position uncertainty (i.e. standing wave and imperfect field synthesis) for BS antenna (a) / calibration antenna (b)**
+
+This value covers the effect of standing wave between BS or calibration antenna and the test range antenna, but also counts for the PWS imperfect field synthesis over distance. This value can be captured by moving the BS or calibration antenna towards the test range antenna.
+
+### **B5-3 RF leakage (calibration antenna connector terminated)**
+
+This contribution denotes noise leaking in to connector and cable(s) between test range antenna and receiving equipment. The contribution also includes the noise leakage between the connector and cable(s) between reference antenna and transmitting equipment.
+
+### **B5-4 QZ ripple experienced by BS (a) /calibration antenna (b)**
+
+This is the quiet zone (QZ) ripple experienced by the BS/reference antenna during the measurement phase. The purpose of this component is to capture the contributions that the reflections from the walls, roof and floor that will add to measurements. The sum of all these reflections from the walls, roof and floor will give the overall value for the QZ ripple. In other words, the uncertainty component from the wall will not be separated from the roof or the floor. The purpose of this uncertainty component is to capture the overall reflections from the chamber walls experienced by the BS/reference antenna.
+
+### **B5-5 Miscellaneous uncertainty**
+
+The term 'miscellaneous uncertainty' is used to define all the unknown, unquantifiable, etc. uncertainties associated with EIRP measurements. This term should include truly random effects as well as systematic uncertainties, such as that arising from dissimilarity between the patterns of the reference antenna and the BS.
+
+### **B5-6 Mismatch (i.e. reference antenna, network analyser and reference cable)**
+
+This uncertainty is the residual uncertainty contribution coming from multiple reflections between the receiving antenna and the test receiver equipment. This value can be captured through measurement by measuring the  $S_{11}$  towards the receive antenna and also towards the test receiver. The mismatch between the antenna reflection and the receiver
+
+reflection can also be calculated. If the same cable is used for calibration Stage 1, this can be considered systematic and negligible.
+
+#### **B5-7 Insertion loss of transmit chain**
+
+This uncertainty is the residual uncertainty contribution coming from introducing an antenna at the end of the cable. If this cable does not change/move between the calibration Stage 1 and the measurement Stage 2, the uncertainty is assumed to be systematic and negligible during the measurement stage. Alternatively, the insertion loss can also be calculated by taking the measurement of the cable where port 2 is the end of the cable connected to the BS or calibration antenna.
+
+$$IL = -20\log_{10}|S_{21}| \text{ dB}$$
+
+#### **B5-8 Influence of the calibration antenna feed cable (i.e. flexing cables, adapters, attenuators, extra pathloss cable & connector repeatability)**
+
+During the calibration phase this cable is used to feed the calibration antenna and any influence it may have upon the measurements is captured. This is assessed by repeated measurements while flexing the cables and rotary joints. The largest difference between the results is recorded as the uncertainty.
+
+#### **B5-9 Misalignment of positioning system**
+
+This contribution originates from uncertainty in sliding position and turn table angle accuracy. If the calibration antenna is aligned to maximum this contribution can be considered negligible and therefore set to zero.
+
+#### **B5-10 Rotary joints**
+
+If applicable, this uncertainty term corresponds to the accuracy in changing from azimuth to vertical measurements.
+
+#### **B5-11 Switching uncertainty**
+
+The purpose of the switching unit is to switch electromechanically different RF path to different measurement instruments of different measurement modes. The electromechanical switching clearly reduces the errors arising from manual switching work. Switching is also used to measure the path loss values of each polarization component. Even though the electromechanical switching is preferable during path loss and antenna performance measurements, some minor uncertainties can occur when the switch states are programmed to change their polarity.
+
+#### **B5-12 Field repeatability**
+
+Each execution of field calibration of the measurement *antenna array* to find the PWS settings provides a slightly different set of settings for the RF components for each antenna path. This results in variation of the synthesized plane wave in the QZ and variation of PWS antenna to reference antenna coupling. This variation is described by field repeatability term.
+
+#### **B5-13 Frequency flatness of test system**
+
+This uncertainty contribution to account for the frequency interpolation error caused by a finite frequency resolution during the calibration stage.
+
+#### **B5-14 System non-linearity**
+
+This uncertainty term is calculated as RSS of the following items, assuming a rectangular distribution:
+
+- System non-linearity in time. This is assessed by repeated measurements over a period of time (e.g. 60 minutes) for the same reference power transmitted by the reference antenna. The largest difference between the results is recorded as the uncertainty.
+- System non-linearity in power. This is assessed by repeated measurements over a range of transmitted powers. The largest delta between the increments on the receiving side versus the transmitting side is recorded as the uncertainty.
+
+---
+
+## Annex C (informative): Test equipment uncertainty values
+
+### C.1 Test equipment measurement error contribution descriptions
+
+#### **C1-1 Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter)**
+
+The receiving device used to measure the received signal level in the EIRP tests either as an absolute level or as a relative level. These receiving devices to name a few are spectrum analyzers, network analyzers or power meter. These devices will have an uncertainty contribution of their own; this value declared by the test gear vendor should be recorded as this uncertainty contribution. If a power meter is used then both measurement uncertainty and out of band noise is considered as part of the contribution. This uncertainty value can be found in table C2-1 and was a result of compromised value in order to align all test methods having this uncertainty contribution.
+
+#### **C1-2 Uncertainty of the RF signal generator**
+
+The use of this signal generator introduces an uncertainty on the absolute output level. The uncertainty value will be indicated in the manufacturer's data sheet in logs. This uncertainty value can be found in Annex C2-1 and was a result of compromised value in order to align all test methods having this uncertainty contribution.
+
+#### **C1-3 Uncertainty of the network analyser**
+
+##### **Drift (temp, oscillators, filters, etc.) start-to-end time of measurements**
+
+This uncertainty includes all the uncertainties involved in the  $S_{21}$  measurement (including drift and frequency flatness) with a network analyzer, and will be calculated from the manufacturer's data in logs. This uncertainty also includes analyzer uncertainty for multi-polarization (2 or more ports) measured simultaneously. This uncertainty value can be found in table C2-1 and was a result of compromised value in order to align all test methods having this uncertainty contribution.
+
+#### **C1-4 Uncertainty of the absolute gain of the reference antenna**
+
+This uncertainty consists of the uncertainty of the gain value associated with the gain value denoted from the antenna calibration. This uncertainty value can be found in table C2-1 and was a result of compromised value in order to align all test methods having this uncertainty contribution.
+
+#### **C1-5 Measurement receiver (co-location)**
+
+Error for the receiver used to measure the noise floor level in the co-location test.
+
+#### **C1-6 Noise figure measurement accuracy**
+
+Noise figure calibration accuracy used for the low power levels used during the co-location measurements.
+
+#### **C1-7 RF power measurement equipment (e.g. spectrum analyser, power meter) - low power (UEM, absolute ACLR)**
+
+Measurement equipment error associated with measuring low power absolute high frequency (FR2) unwanted emissions.
+
+#### **C1-8 RF power measurement equipment (e.g. spectrum analyzer, power meter) - relative (ACLR)**
+
+Measurement equipment error associated with measuring low power relative high frequency (FR2) unwanted emissions.
+
+#### **C1-9 RF power measurement equipment standard uncertainty $\sigma$ (dB) of the absolute level for a time domain wideband measurement for FR2**
+
+Measurement equipment error associated with measuring low power, wide band time domain high dynamic range signals required for the Tx OFF transient test.
+
+## C.2 Measurement Equipment uncertainty values
+
+The following uncertainty distribution and standard uncertainty ( $\sigma$ ) values proposed by test vendors are adopted for the RF power measurement equipment, RF signal generator, and network analyzer to calculate the uncertainty budget.
+
+**Table C.2-1: Test equipment uncertainty values for FR1**
+
+| UID  | Instrument                                                           | Use case          | Measurement Uncertainty type                                 | Standard uncertainty $\sigma$ (dB) |                            |                      | Probability distribution |
+|------|----------------------------------------------------------------------|-------------------|--------------------------------------------------------------|------------------------------------|----------------------------|----------------------|--------------------------|
+|      |                                                                      |                   |                                                              | $f \leq 3$ GHz                     | $3$ GHz $< f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                          |
+| C1-1 | RF power measurement equipment (e.g. spectrum analyzer, power meter) | Measurement stage | Total amplitude accuracy (with input levels down to -70 dBm) | 0.14                               | 0.26                       | 0.26                 | Gaussian                 |
+| C1-2 | RF signal generator                                                  | Measurement stage | Level error                                                  | 0.46                               | 0.46                       | 0.46                 | Gaussian                 |
+| C1-3 | Network analyzer                                                     | Calibration stage | Accuracy of transmission measurements                        | 0.13                               | 0.20                       | 0.2                  | Gaussian                 |
+| C1-5 | Measurement receiver (co-location)                                   | Measurement stage | Amplitude accuracy                                           | 0.41                               | 0.74                       | 0.8                  | Gaussian                 |
+| C1-6 | Noise figure measurement accuracy                                    | Calibration stage | Amplitude accuracy                                           | 0.2                                | 0.2                        | 0.2                  | Gaussian                 |
+
+NOTE: Standard uncertainty values were derived from datasheets of mid-tier to high-end RF signal generators, spectrum analyzers, and VNAs. Standard uncertainty values of power measurement equipment were derived from datasheet of spectrum analyzers.
+
+**Table C.2-2: Test equipment uncertainty values for FR2**
+
+| UID  | Instrument                                                                                           | Standard uncertainty $\sigma$ (dB) |                        | Probability distribution |
+|------|------------------------------------------------------------------------------------------------------|------------------------------------|------------------------|--------------------------|
+|      |                                                                                                      | $24.25 < f \leq 29.5$ GHz          | $37 < f \leq 43.5$ GHz |                          |
+| C1-1 | Uncertainty of the RF power measurement equipment (e.g. spectrum analyzer, power meter) - high power | 0.50                               | 0.70                   | Gaussian                 |
+| C1-2 | RF signal generator                                                                                  | 0.90                               | 0.90                   | Gaussian                 |
+| C1-3 | Network Analyzer                                                                                     | 0.30                               | 0.30                   | Gaussian                 |
+| C1-7 | RF power measurement equipment (e.g. spectrum analyzer, power meter) - low power (UEM)               | 0.90                               | 0.90                   | Gaussian                 |
+| C1-8 | RF power measurement equipment (e.g. spectrum analyzer, power meter) - relative (ACLR)               | 0.75                               | 0.90                   | Gaussian                 |
+| C1-9 | RF power measurement equipment (e.g. spectrum analyzer, power meter) - relative (ACLR)               | 1.25                               | 1.45                   | Gaussian                 |
+
+The following uncertainty distribution and standard uncertainty ( $\sigma$ ) value for the reference antenna derived as the maximum of companies' proposals are adopted in all test methods to calculate the uncertainty budget.
+
+**Table C.2-3: Reference antenna uncertainty value for FR1**
+
+| UID  | Instrument        | Use case          | Standard uncertainty $\sigma$ (dB) |                            |                      | Probability distribution |
+|------|-------------------|-------------------|------------------------------------|----------------------------|----------------------|--------------------------|
+|      |                   |                   | $f \leq 3$ GHz                     | $3$ GHz $< f \leq 4.2$ GHz | $4.2 < f \leq 6$ GHz |                          |
+| C1-4 | Reference antenna | Calibration stage | 0.29                               | 0.25                       | 0.25                 | Rectangular              |
+
+**Table C.2-4: Reference antenna uncertainty value for FR2**
+
+| UID  | Instrument        | Use case          | Standard uncertainty $\sigma$ (dB) |                        | Probability distribution |
+|------|-------------------|-------------------|------------------------------------|------------------------|--------------------------|
+|      |                   |                   | $24.25 < f \leq 29.5$ GHz          | $37 < f \leq 43.5$ GHz |                          |
+| C1-4 | Reference antenna | Calibration stage | 0.3                                | 0.3                    | Rectangular              |
+
+## C.3 MU of TE derived from conducted specification
+
+For a number of test cases the conducted measurement uncertainty used in TS 36.141 [3] is used to estimate the uncertainty contributing of the conducted part (filters, limiters, switches etc.) of the OTA test set up.
+
+Where appropriate the mismatch uncertainty is removed from the conducted uncertainty so that it is not included twice in the calculation.
+
+### C3-1 DL-RS MU derived from conducted specification
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $\pm 0.8$  dB,  $f \leq 3$  GHz,  $\pm 1.1$  dB,  $3$  GHz  $< f \leq 4.2$  GHz
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $\pm 0.41$  dB,  $f \leq 3$  GHz,  $\pm 0.56$  dB,  $3$  GHz  $< f \leq 4.2$  GHz
+
+### C3-2 Total power dynamic range conducted uncertainty
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $\pm 0.4$  dB
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $\pm 0.2$  dB
+
+### C3-3 Transmitter mandatory spurious emissions
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $9$  kHz  $< f \leq 4$  GHz:  $\pm 2.0$  dB,  $4$  GHz  $< f \leq 19$  GHz:  $\pm 4.0$  dB
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $9$  kHz  $< f \leq 4$  GHz:  $\pm 1.0$  dB,  $4$  GHz  $< f \leq 19$  GHz:  $\pm 2.0$  dB
+
+### C3-4 Receiver spurious emissions
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $30$  MHz  $< f \leq 4$  GHz:  $\pm 2.0$  dB,  $4$  GHz  $< f \leq 19$  GHz:  $\pm 4.0$  dB
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $9$  kHz  $< f \leq 4$  GHz:  $\pm 1.0$  dB,  $4$  GHz  $< f \leq 19$  GHz:  $\pm 2.0$  dB
+
+### C3-5 Additional (co-existence) spurious emissions
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $\pm 2.0$  dB for  $> -60$ dBm,  $f \leq 3$  GHz,  $\pm 2.5$  dB,  $3$  GHz  $< f \leq 4.2$  GHz,  $\pm 3.0$  dB,  $4.2$  GHz  $< f \leq 6$  GHz
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $\pm 1.0$  dB for  $> -60$ dBm,  $f \leq 3$  GHz,  $\pm 1.28$  dB,  $3$  GHz  $< f \leq 4.2$  GHz,  $\pm 1.53$  dB,  $4.2$  GHz  $< f \leq 6$  GHz
+
+### C3-6 TX IMD - conducted measurement uncertainty
+
+Conducted MU ( $1.96\sigma$ ) from TS 36.141 [3]:  $\pm 1.0$  dB
+
+Conducted contribution for OTA MU budget ( $1\sigma$ ):  $\pm 1.0$  dB,  $f \leq 3$  GHz,  $\pm 1.1$  dB,  $3$  GHz  $< f \leq 4.2$  GHz,  $\pm 1.2$  dB,  $4.2$  GHz  $< f \leq 6$  GHz
+
+### C3-7 Colocation blocking - conducted measurement uncertainty
+
+Conducted accuracy of the co-location blocking interferer is the same as the TX IMD interferer.
+
+**Table C.3-1: MU derived from the conducted specification**
+
+| UID  | Requirement                                             | Use case          | Standard uncertainty $\sigma$ (dB) |                            |                            |                           | Probability distribution |
+|------|---------------------------------------------------------|-------------------|------------------------------------|----------------------------|----------------------------|---------------------------|--------------------------|
+|      |                                                         |                   | $f \leq 3$ GHz                     | $3$ GHz $< f \leq 4.2$ GHz | $4.2$ GHz $< f \leq 6$ GHz | $6$ GHz $< f \leq 26$ GHz |                          |
+| C3-1 | DL-RS MU derived from conducted specification           | Measurement stage | 0.41                               | 0.56                       | 0.56                       | N/A                       | Gaussian                 |
+| C3-2 | Total power dynamic range conducted uncertainty         |                   | 0.2                                | 0.2                        | 0.2                        | N/A                       |                          |
+| C3-3 | Transmitter mandatory spurious emissions                |                   | 1.0                                |                            |                            | 2.0                       |                          |
+| C3-4 | Receiver spurious emissions                             |                   | 1.0                                |                            |                            | 2.0                       |                          |
+| C3-5 | Additional (co-existence) spurious emissions            |                   | 1.02                               | 1.28                       | 1.53                       | N/A                       |                          |
+| C3-6 | TX IMD - conducted measurement uncertainty              |                   | 1                                  | 1.1                        | 1.2                        | N/A                       |                          |
+| C3-7 | Colocation blocking - conducted measurement uncertainty |                   | 1                                  | 1.1                        | 1.2                        | N/A                       |                          |
+
+## Annex D (informative): Beam sweeping
+
+### D.1 Introduction
+
+For emissions with a high beam-forming gain, correct assessment of TRP requires grid measurements at small angular steps. In a measurement where the BS is mounted on a turntable this turns into a large number of mechanical rotations of the BS and hence lengthy measurements. One way to mitigate this problem is to use *beam sweeping* as a complement to mechanical rotations. Instead of performing the TRP measurements using a fixed beam, the BS will be programmed to move the beam across several pre-defined positions, while the power samples are recorded for each point on the grid.
+
+Such method could be advantageous not only for in-band signals, but also for spurious emissions characterized by high beamforming gain, such as harmonics.
+
+The results below show that the calculated TRP from the beam average pattern is very close to the TRP of all individual beams that are included in the sweeping. The advantage of this method would be the possibility to use sparser spherical grid compared to reference angular steps, and without the need to find the peaks of the emissions.
+
+### D.2 Simulation results
+
+The effect of beam sweeping is illustrated by using a 10x10 Uniform Rectangular Array with element separation at the carrier frequency. A number of beams is realized by a constant phase-gradient steering. The beam sweeping range is selected to completely avoid the forming of grating lobes and the angular step between two lobes is selected as the Half Power Beamwidth (HPBW) of a broadside beam.
+
+In the example of figure D.2-1 the reference angular step is  $11.6^\circ$  ( $=1/5$  radians). For the harmonic in figure D.2-2 the reference step is  $5.8^\circ$ . The full sphere average of the EIRP is the TRP. For simplicity, only sweeping in the horizontal plane is employed. In the case where a fixed beam is used the average EIRP is not correct when the sampling angular step is larger than the reference angular step. However, when the EIRP pattern is first averaged over all beams (blue curves) the average EIRP is virtually constant for any angular step up to  $36^\circ$ , see figure D.2-3.
+
+![Figure D.2-1: Two plots comparing beam patterns. The left plot, titled 'URA with steered beams', shows EIRP (dB) vs. phi (°) from -180 to 180. It features a dashed black line for the 'Element pattern' and two solid green lines for 'Beam 1' and 'Beam 2'. The right plot, titled 'Max hold and average beam', shows EIRP (dB) vs. phi (°) from -180 to 180. It features a red line for 'Max hold' and a blue line for 'Average'. The 'Max hold' line shows the peak EIRP across all beams, while the 'Average' line shows the mean EIRP.](9975977c05cf557391d09ea21a0c2263_img.jpg)
+
+Figure D.2-1: Two plots comparing beam patterns. The left plot, titled 'URA with steered beams', shows EIRP (dB) vs. phi (°) from -180 to 180. It features a dashed black line for the 'Element pattern' and two solid green lines for 'Beam 1' and 'Beam 2'. The right plot, titled 'Max hold and average beam', shows EIRP (dB) vs. phi (°) from -180 to 180. It features a red line for 'Max hold' and a blue line for 'Average'. The 'Max hold' line shows the peak EIRP across all beams, while the 'Average' line shows the mean EIRP.
+
+**Figure D.2-1: In the left figure several beam patterns of the array are depicted, together with the corresponding element pattern. In the right picture two different settings of a spectrum analyser are simulated. Under the "Max hold" setting of the analyser the maximum EIRP over all beams is presented at every angular point. Under the "Average" setting the average EIRP over all beams is presented. The latter case is the intended setting to use for TRP assessment**
+
+![Figure D.2-2: Two plots showing EIRP (dB) vs. ϕ (°). Left plot: 'URA with steered beams' showing individual beam patterns (Element pattern, Beam 1, Beam 2, etc.) with multiple green lobes and a dashed black element pattern. Right plot: 'Max hold and average beam' showing a red 'Max hold' curve and a blue 'Average' curve across the same angular range.](2aff6ef70a6f528e5eaeb4c94fd664fe_img.jpg)
+
+Figure D.2-2: Two plots showing EIRP (dB) vs. ϕ (°). Left plot: 'URA with steered beams' showing individual beam patterns (Element pattern, Beam 1, Beam 2, etc.) with multiple green lobes and a dashed black element pattern. Right plot: 'Max hold and average beam' showing a red 'Max hold' curve and a blue 'Average' curve across the same angular range.
+
+**Figure D.2-2: The beam sweeping at the 2<sup>nd</sup> harmonic frequency is simulated using an embedded element pattern. Left plot depicts the EIRP patterns of individual beams. Right plot depicts the *max hold* and beam *average* EIRP patterns**
+
+![Figure D.2-3: Two plots showing TRP (dB) vs. ϕ step (°). Left plot: 'Fundamental frequency' showing TRP values for Max hold (red), Average (blue), Broad side (yellow), and various beams (green dashed). Right plot: '2nd harmonic' showing similar curves but with much higher variation and lower TRP values for the steered beams (green dashed) compared to the fundamental.](d6198648f031082e94008fb2734fda40_img.jpg)
+
+Figure D.2-3: Two plots showing TRP (dB) vs. ϕ step (°). Left plot: 'Fundamental frequency' showing TRP values for Max hold (red), Average (blue), Broad side (yellow), and various beams (green dashed). Right plot: '2nd harmonic' showing similar curves but with much higher variation and lower TRP values for the steered beams (green dashed) compared to the fundamental.
+
+**Figure D.2-3: Calculation of average EIRP in the azimuth cut by using different angular step sizes. The yellow curve corresponds to a fixed broadside beam (perpendicular to the *antenna array surface*), and all the green curves correspond to steered, but fixed beams. The variation in TRP for different beams at the harmonic is due to grating lobe effects**
+
+## D.3 Measurement results
+
+The effect of beam sweeping measured on an BS employing a 4x16 array, is depicted in figures D.3-2 and D.3-3. Measurements were performed in a CATR, in far-field conditions, with an BS that transmits one single beam that can be moved across a number of pre-defined directions. For the results using beam sweeping, see right figure in figure D.3-2, the following beam settings were used:
+
+- 48 pre-defined beam directions (see fig. D.3-1) were swept, changing the beam direction every 15 us
+- the range of beam directions is  $\pm 60$  and  $\pm 15^\circ$  in azimuth and elevation, respectively.
+- The BS is making a full rotation (i.e.  $360^\circ$ ) mechanically into the horizontal plane, with a step of  $1^\circ$ . Each position was held for about 1 s, while the spectrum analyser recorded a time averaged value of the received power (at least 1000 samples for each angular position were considered enough for good statistical average).
+
+![Figure D.3-1: Heatmap of pre-defined possible directions of the main beam. The x-axis is azimuth angle phi [deg] from -60 to 60. The y-axis is elevation angle theta [deg] from 60 to 120. A grid of 48 red spots (beam directions) is shown between theta 80-110 and phi -40 to 40. Each spot is labeled with a beam index BI: [row, col].](3e6effbdaf24cc5ca251ab0f290f8fa5_img.jpg)
+
+Detailed description of Figure D.3-1: The heatmap shows a rectangular region of high gain (yellow/red) against a blue background. Within this region, a grid of 4x12 beam indices is labeled. The rows (theta) are indexed from 4 down to 0, and columns (phi) from 0 to 11. For example, the top-left labeled beam is BI: [4,0] and the bottom-right is BI: [0,11]. A color bar on the right indicates 'Dir [dB]' from 15 to 25.
+
+Figure D.3-1: Heatmap of pre-defined possible directions of the main beam. The x-axis is azimuth angle phi [deg] from -60 to 60. The y-axis is elevation angle theta [deg] from 60 to 120. A grid of 48 red spots (beam directions) is shown between theta 80-110 and phi -40 to 40. Each spot is labeled with a beam index BI: [row, col].
+
+**Figure D.3-1: Pre-defined possible directions of the main beam (red spots). Compared to the broadside beam (the middle one) the maximum supported steering is  $\pm 60^\circ$  in azimuth and  $\pm 15^\circ$  in elevation. The extreme directions are excluded in this experiment, so only 48 directions are swept**
+
+![Figure D.3-2: Two 3D surface plots of Peak normalized EIRP (dB) vs frequency (f-f_c in MHz) and Angles (deg).](e4a32ec6d1b56eec38fd6f6313f83b06_img.jpg)
+
+Detailed description of Figure D.3-2: 
+ - Left plot: 'Fixed broad side beam'. Shows a narrow peak in the angular domain (around 180 degrees) that is consistent across the frequency range (-100 to 300 MHz). Peak EIRP is around 0 dB.
+ - Right plot: 'Beam sweeping'. Shows a much wider plateau in the angular domain, indicating that the beam is being swept across a range of angles. The peak EIRP remains around 0 dB but covers a larger angular area.
+
+Figure D.3-2: Two 3D surface plots of Peak normalized EIRP (dB) vs frequency (f-f\_c in MHz) and Angles (deg).
+
+**Figure D.3-2: EIRP values for measured data in a horizontal cut versus frequency (in relative scale)**
+
+![Figure D.3-3: Two line graphs comparing Fixed beam and Beam sweeping performance.](3ea2a1f3b801526c45a1a02c3f983822_img.jpg)
+
+Detailed description of Figure D.3-3:
+ - Left graph: Peak normalized EIRP (dB) vs Angles (deg). The 'Fixed beam' (blue line) shows a sharp, narrow peak at approximately 180 degrees with high-frequency oscillations. The 'Beam sweeping' (orange line) shows a much broader, smoother envelope centered around 180 degrees, with a lower peak value (approx -15 dB).
+ - Right graph: Average EIRP (dB) vs Angular step used in integration (deg). The 'Fixed beam' (blue line) starts at -17 dB and increases with significant fluctuations to about -10 dB as the step size increases to 30 degrees. The 'Beam sweeping' (orange line) is very stable, staying flat around -17.5 dB across all angular step sizes.
+
+Figure D.3-3: Two line graphs comparing Fixed beam and Beam sweeping performance.
+
+**Figure D.3-3: To the left measured data for a horizontal cut are shown at a single frequency. A significantly broader pattern is detected for the beam sweeping signal (spectrum analyser in "Average" mode). To the right the angular average of the EIRP values are depicted for different angular step sizes**
+
+---
+
+## D.4 Design of beam sweeping test signal
+
+The following design criteria have been identified:
+
+1. Full transmit power is used for all beams.
+2. Horizontal beam separation shall be the HPBW in the azimuth direction and the vertical beam separation shall be the HPBW in the vertical direction, evaluated for a broadside beam.
+3. Lobes with high loss compared to the broadside beam are avoided. By loss we mean the reduction in beamforming gain between different positions of the beam).
+
+The motivation for the third criterion is to have a fairly constant TRP for the used beams. The loss can be due to both loss in element pattern gain, but also due to adverse mutual coupling effects. Removing lobes with high loss gives a beam average TRP that is close to the TRP for any individual beam.
+
+## Annex E (informative): Sparse sampling for spurious emissions
+
+In the case of spurious emissions for large BSs, such as the BS, the emissions do not necessarily radiate through the antenna elements. For this reason, to be on the conservative side, the entire BS dimensions should be considered when calculating the reference angular steps on the spherical grid.
+
+The emission lobes will be narrow and hard to locate for some emissions, especially in the higher part of the spurious emissions domain. Instead of searching for the direction of the emission lobes, it is proposed to perform the measurement on a grid without alignment considerations and add a correction factor to the TRP obtained from the grid, to ensure overestimation. This correction factor is obtained through the study of random rotations of the BS.
+
+In practice, the emissions are likely to have a low degree of correlation, except for harmonic emissions. For harmonic emissions a beam sweeping test signal is proposed in annex D and the description of such signal is not covered by the present release of this technical report.
+
+For non-harmonic emissions, a correlation factor distributed uniformly in a given interval from 0 to  $\rho_{\max}$  is assumed when calculating the correction factor  $\Delta\text{TRP}$  for the  $\text{TRP}_{\text{Estimate}}$ . The angular variation of the emissions coming from low correlated sources is dominated by the *array factor*, i.e., the spatial distribution of the sources. Hence, emissions can be modelled by the *array factor* of a set of point sources, i.e., for simplicity the element pattern is isotropic. To quantify the degree of sparse sampling relative to the reference angular steps a Sparsity Factor (SF) is introduced. For a spherical equal angles grid
+
+$$\text{SF} = \max \left( \frac{\Delta\theta}{\Delta\theta_{\text{ref}}}, \frac{\Delta\phi}{\Delta\phi_{\text{ref}}} \right)$$
+
+Where
+
+$$\begin{cases} \Delta\theta_{\text{ref}} = \lambda/D \\ \Delta\phi_{\text{ref}} = \lambda/D_{\text{cyl}} \end{cases}$$
+
+The  $\text{TRP}_{\text{Estimate}}$  values are then calculated by using a given angular grid defined by  $\Delta\theta$  and  $\Delta\phi$  which are larger than the reference angular steps  $\Delta\theta_{\text{ref}}$  and  $\Delta\phi_{\text{ref}}$ . The CDF of these TRP values are then created and the CDF is shifted so that the 5th percentile corresponds to 0 dB TRP error. This shift is introduced as  $\Delta\text{TRP}$ , see figure E-1.
+
+In the followings we propose a method to estimate  $\Delta\text{TRP}$  for large antennas ( $D > 4\lambda$ ), based on generating a set of statistical samples of TRP values calculated on a set of randomly generated emission sources of a given size  $D$ .
+
+In this investigation each statistical sample is generated as follows:
+
+1. Set up a quadratic uniform linear  $N \times N$  array in the yz-plane, with horizontal and vertical element separation  $D$ .  $N$  is randomly chosen such that the element separation is larger or equal to a half wave length.
+
+2. Rotate the source points by an Euler zyz-rotation with angles  $a$ ,  $b$ , and  $c$  which are uniformly chosen in the intervals  $[0,360]$ ,  $[0,90]$  and  $[0,360]$  degrees, respectively. The rotated position of source  $n$  is denoted  $\vec{d}_n$
+
+3. Pick a random correlation value  $\rho$  from the uniform distribution between 0 and  $\rho_{\max}$ , and generate source weights as
+
+$$w_n(\rho) = \sqrt{\rho} + \frac{(x_n + jy_n)}{\sqrt{2}} \sqrt{1 - \rho}$$
+
+Where  $x_n, y_n \in N(0, 1)$  are picked from a normal distribution with zero mean and unit standard deviation.
+
+4. Normalize the weights to  $\text{TRP} = 1$  by using a full sphere grid with sparsity factor 0.25.
+
+5. Generate EIRP values on the desired grid by using an *array factor*
+
+$$\text{EIRP}(\theta, \phi) = \left| \sum_{n=1}^N e^{jk\hat{r}(\theta, \phi) \cdot \vec{d}_n} w_n \right|^2$$
+
+6. Calculate the TRP value as an appropriate mean value of the EIRP values for two/three cut grids and using full sphere numerical integration for the full sphere case.
+
+There is publicly available Matlab code for sparse sampling analysis in [22] and more results can be found in publication in [10].
+
+The resulting 5<sup>th</sup> percentile values of the empirical CDFs are used as a practical lower bound on the TRP calculated directly from the points in the actual grid. If the 5<sup>th</sup> percentile value is positive, there is no need for a systematic correction, that means  $\Delta\text{TRP} = 0$ . On the other hand, if the 5<sup>th</sup> percentile value is negative, a systematic correction is needed to guarantee TRP overestimation with 95% confidence. For this purpose, the absolute value of the 5<sup>th</sup> percentile is used as systematic correction factor, denoted  $\Delta\text{TRP}$  (see figure E-1). Some simulation results are found in figures E-2 (a) – (c) for two different choices of max correlation and the three grid types: full-sphere, three-cut, and two-cuts.
+
+![Figure E-1: Determination of ΔTRP based on the 5th percentile values. The graph shows Empirical CDF (%) on the y-axis (0 to 100) versus TRP error (dB) on the x-axis (-1.5 to 1.5). A dashed blue curve represents the empirical CDF, and a solid blue curve represents the corrected CDF. The 5th percentile value is marked on the x-axis at approximately -0.8 dB, and the correction factor ΔTRP is indicated by a horizontal arrow from this point to the origin (0 dB).](1cbfab01055f9367de73383e84fa29ad_img.jpg)
+
+The figure is a line graph showing the Empirical CDF (%) on the y-axis (ranging from 0 to 100) against the TRP error (dB) on the x-axis (ranging from -1.5 to 1.5). Two curves are plotted: a dashed blue line representing the empirical CDF and a solid blue line representing the corrected CDF. The dashed curve starts at 0% CDF at approximately -1.2 dB and rises to 100% at approximately 1.0 dB. The solid curve starts at 0% CDF at 0 dB and rises to 100% at approximately 1.5 dB. A horizontal arrow labeled  $\Delta\text{TRP}$  points from the 5th percentile value on the x-axis (approximately -0.8 dB) to the origin (0 dB), indicating the systematic correction factor.
+
+Figure E-1: Determination of ΔTRP based on the 5th percentile values. The graph shows Empirical CDF (%) on the y-axis (0 to 100) versus TRP error (dB) on the x-axis (-1.5 to 1.5). A dashed blue curve represents the empirical CDF, and a solid blue curve represents the corrected CDF. The 5th percentile value is marked on the x-axis at approximately -0.8 dB, and the correction factor ΔTRP is indicated by a horizontal arrow from this point to the origin (0 dB).
+
+**Figure E-1: Determination of  $\Delta\text{TRP}$  based on the 5<sup>th</sup> percentile values. The dashed curve depicts the empirical CDF found from the statistical analysis, and the solid curve depicts the corrected CDF corresponding to over-estimation with 95% confidence**
+
+![Line graph (a) showing ΔTRP (dB) vs Sparsity factor for D = 10λ. The graph compares two correlation intervals, ρ_max = 0.25 (green lines) and ρ_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 3.5, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=1.5 and x=2.5. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest. Line graph (b) showing ΔTRP (dB) vs Sparsity factor for D = 15λ. The graph compares two correlation intervals, ρ_max = 0.25 (green lines) and ρ_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 5, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=2.5 and x=4. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest. Line graph (c) showing ΔTRP (dB) vs Sparsity factor for D = 20λ. The graph compares two correlation intervals, ρ_max = 0.25 (green lines) and ρ_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 7, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=4.5 and x=5. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest.](e77f9abb052e12e90a8480b9e1e4b571_img.jpg)
+
+$D = 10\lambda$ , Markers: + two cuts,  $\Delta$  three cuts, O sphere
+
+(a)
+
+$D = 15\lambda$ , Markers: + two cuts,  $\Delta$  three cuts, O sphere
+
+(b)
+
+$D = 20\lambda$ , Markers: + two cuts,  $\Delta$  three cuts, O sphere
+
+(c)
+
+Line graph (a) showing ΔTRP (dB) vs Sparsity factor for D = 10λ. The graph compares two correlation intervals, ρ\_max = 0.25 (green lines) and ρ\_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 3.5, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=1.5 and x=2.5. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest. Line graph (b) showing ΔTRP (dB) vs Sparsity factor for D = 15λ. The graph compares two correlation intervals, ρ\_max = 0.25 (green lines) and ρ\_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 5, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=2.5 and x=4. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest. Line graph (c) showing ΔTRP (dB) vs Sparsity factor for D = 20λ. The graph compares two correlation intervals, ρ\_max = 0.25 (green lines) and ρ\_max = 0.5 (yellow lines), across three marker types: two cuts (+), three cuts (Δ), and sphere (O). The x-axis (Sparsity factor) ranges from 1 to 7, and the y-axis (ΔTRP (dB)) ranges from 0 to 3. A shaded region is present between x=4.5 and x=5. The yellow lines are consistently higher than the green lines, and the 'two cuts' (+) markers show the highest ΔTRP values, while the 'sphere' (O) markers show the lowest.
+
+Figure E-2: Correction factor  $\Delta\text{TRP}$  for 95% confidence overestimation of the TRP for three different electrical sizes  $D/\lambda$  and correlation intervals
+
+![Line graph titled 'Full sphere' showing Δ TRP (dB) vs Sparsity factor for different ρ_max values (0, 0.25, 0.5, 0.75). A vertical dashed line at Δθ = 15° is present.](5b87d9e3f7fbaeceb1bc31ae4d7c95b0_img.jpg)
+
+This line graph, titled "Full sphere", plots the correction factor  $\Delta \text{ TRP}$  (dB) on the y-axis (ranging from 0 to 2) against the Sparsity factor on the x-axis (ranging from 1 to 3.5). Four data series are shown for different maximum correlation values  $\rho_{\max}$ : 0 (blue), 0.25 (orange), 0.5 (yellow), and 0.75 (purple). All series start at 0 dB for a sparsity factor of 1. The correction factor increases with the sparsity factor. The  $\rho_{\max} = 0.75$  series shows the steepest increase, reaching approximately 1.4 dB at a sparsity factor of 3.5. A vertical dashed line is drawn at a sparsity factor of approximately 2.6, labeled  $\Delta\theta = 15^\circ$ .
+
+| Sparsity factor | $\rho_{\max} = 0$ (dB) | $\rho_{\max} = 0.25$ (dB) | $\rho_{\max} = 0.5$ (dB) | $\rho_{\max} = 0.75$ (dB) |
+|-----------------|------------------------|---------------------------|--------------------------|---------------------------|
+| 1.0             | 0.0                    | 0.0                       | 0.0                      | 0.0                       |
+| 1.5             | 0.1                    | 0.1                       | 0.15                     | 0.25                      |
+| 2.0             | 0.2                    | 0.25                      | 0.35                     | 0.55                      |
+| 2.5             | 0.28                   | 0.3                       | 0.45                     | 0.75                      |
+| 3.0             | 0.38                   | 0.4                       | 0.6                      | 1.0                       |
+| 3.5             | 0.42                   | 0.55                      | 0.9                      | 1.4                       |
+
+Line graph titled 'Full sphere' showing Δ TRP (dB) vs Sparsity factor for different ρ\_max values (0, 0.25, 0.5, 0.75). A vertical dashed line at Δθ = 15° is present.
+
+Figure E-3: Full sphere correction factors  $\Delta \text{TRP}$  for max correlation up to 0.75 and  $D/\lambda=10$
+
+![Line graph titled 'Three cuts' showing Δ TRP (dB) vs Sparsity factor for different ρ_max values (0, 0.25, 0.5, 0.75). A vertical dashed line at Δθ = 15° is present.](8faebfce2615b355cc3aefe58b2e17fc_img.jpg)
+
+This line graph, titled "Three cuts", plots the correction factor  $\Delta \text{ TRP}$  (dB) on the y-axis (ranging from 0 to 4) against the Sparsity factor on the x-axis (ranging from 1 to 3.5). Four data series are shown for different maximum correlation values  $\rho_{\max}$ : 0 (blue), 0.25 (orange), 0.5 (yellow), and 0.75 (purple). All series start at a positive value for a sparsity factor of 1. The correction factor increases with the sparsity factor. The  $\rho_{\max} = 0.75$  series starts at approximately 2.1 dB and reaches 3.0 dB at a sparsity factor of 3.5. A vertical dashed line is drawn at a sparsity factor of approximately 2.6, labeled  $\Delta\theta = 15^\circ$ .
+
+| Sparsity factor | $\rho_{\max} = 0$ (dB) | $\rho_{\max} = 0.25$ (dB) | $\rho_{\max} = 0.5$ (dB) | $\rho_{\max} = 0.75$ (dB) |
+|-----------------|------------------------|---------------------------|--------------------------|---------------------------|
+| 1.0             | 0.8                    | 0.95                      | 1.35                     | 2.1                       |
+| 1.5             | 0.95                   | 1.1                       | 1.45                     | 2.15                      |
+| 2.0             | 1.05                   | 1.2                       | 1.55                     | 2.35                      |
+| 2.5             | 1.15                   | 1.3                       | 1.75                     | 2.55                      |
+| 3.0             | 1.3                    | 1.45                      | 1.9                      | 2.75                      |
+| 3.5             | 1.4                    | 1.55                      | 2.1                      | 3.0                       |
+
+Line graph titled 'Three cuts' showing Δ TRP (dB) vs Sparsity factor for different ρ\_max values (0, 0.25, 0.5, 0.75). A vertical dashed line at Δθ = 15° is present.
+
+Figure E-4: Three cuts correction factors  $\Delta \text{TRP}$  for max correlation up to 0.75 and  $D/\lambda=10$
+
+![Line graph titled 'Two cuts' showing correction factors ΔTRP (dB) vs Sparsity factor for different correlation levels ρ_max.](a0cbe8f8ff7d008d81ed3e82b60c8865_img.jpg)
+
+The graph shows the correction factor  $\Delta TRP$  (dB) on the y-axis (ranging from 0 to 4) against the Sparsity factor on the x-axis (ranging from 1 to 3.5). A vertical dashed line at  $SF = 2.67$  is labeled  $\Delta\theta = 15^\circ$ . Four curves are plotted for different maximum correlation coefficients  $\rho_{max}$ :
+
+| Sparsity factor | $\rho_{max} = 0$ (dB) | $\rho_{max} = 0.25$ (dB) | $\rho_{max} = 0.5$ (dB) | $\rho_{max} = 0.75$ (dB) |
+|-----------------|-----------------------|--------------------------|-------------------------|--------------------------|
+| 1.0             | 1.1                   | 1.4                      | 2.1                     | 3.1                      |
+| 1.5             | 1.3                   | 1.5                      | 2.2                     | 3.2                      |
+| 2.0             | 1.4                   | 1.6                      | 2.3                     | 3.3                      |
+| 2.5             | 1.5                   | 1.8                      | 2.5                     | 3.5                      |
+| 3.0             | 1.7                   | 1.9                      | 2.6                     | 3.7                      |
+| 3.5             | 1.8                   | 2.1                      | 2.7                     | 3.8                      |
+
+Line graph titled 'Two cuts' showing correction factors ΔTRP (dB) vs Sparsity factor for different correlation levels ρ\_max.
+
+**Figure E-5: Two cuts correction factors  $\Delta TRP$  for max correlation up to 0.75 and  $D/\lambda=10$**
+
+The following systematic correction factors are proposed be used in the test procedure, given the results obtained for , which is considered to be acceptable at this point.
+
+**Table E-1: For a ful sphere sparse grid the proposed correction factor is zero for angular sampling below or equal to the reference steps ( $SF < 1$ ). The maximum SF is the SF at  $15^\circ$  angular sampling**
+
+|                        | Full-sphere sparse grid | Three cuts using reference angular steps | Two cuts using reference angular steps |
+|------------------------|-------------------------|------------------------------------------|----------------------------------------|
+| Correction factor (dB) | $(SF-1)/(SF_{max}-1)$   | 2.0                                      | 2.5                                    |
+
+## Annex F (informative): Power density measurements close to BS
+
+This annex contains guidelines for measurement of power density flux on a sphere surrounding the BS. The rationale for using a small test distance (compared to the far-field of BS) is that any amount of power that radiates from the BS also will radiate through any sphere enclosing the BS, i.e., energy conservation.
+
+Power flux density based on measurement of tangential electric field components can be used for correct TRP assessment [31]. For accurate power density assessment, the following conditions need to be met:
+
+1. The test distance shall be at least the far-field distance of the measurement antenna, i.e.  $r_0 \geq 2D_{MA}^2 / \lambda$ .
+2. The measurement antenna shall sample an approximately constant field.
+3. The test distance must be at least two wavelengths from the smallest sphere enclosing the BS.
+
+The second criterion is quantified as:
+
+$$r_0 \geq \frac{\frac{w}{\lambda} (R_{sph} + \lambda)}{2} \quad (F-1)$$
+
+where  $R_{sph}$  is the radius of the smallest sphere enclosing the BS. Furthermore, equation (F-1) sets a minimum test distance for a given measurement antenna size  $w$  [31].
+
+![Diagram illustrating the measurement setup. A Base Station (BS) labeled 'EUT' is shown on the left, enclosed in a dashed circle of radius R_sph. A Measurement Antenna (MA) is shown on the right, with a diameter D_MA and a height w. The distance between the center of the BS sphere and the center of the MA is labeled r_0. Dashed lines connect the center of the BS sphere to the edges of the MA.](fc77cd5fb91dcf10116215d46da18a00_img.jpg)
+
+Diagram illustrating the measurement setup. A Base Station (BS) labeled 'EUT' is shown on the left, enclosed in a dashed circle of radius R\_sph. A Measurement Antenna (MA) is shown on the right, with a diameter D\_MA and a height w. The distance between the center of the BS sphere and the center of the MA is labeled r\_0. Dashed lines connect the center of the BS sphere to the edges of the MA.
+
+**Figure F-1: The measurement distance and the dimensions of BS and MA**
+
+**EXAMPLE:** For assessing TRP using power density data close to BS, consider the patterns in Figure G-2, which are sampled at (a) 0.75 m, (b) 2.5 m and (c) 30 m from the same BS. The far-field distance of the BS is 30 m. The angular patterns vary with distance, but the full-sphere integration for TRP deviates less than 0.065 dB. The lower power density levels in the lower figure are balanced by the larger total area of the measurement sphere.
+
+![Three heatmaps (a, b, c) showing angular power density patterns at 0.75 m, 2.5 m, and 30 m from the BS. The x-axis is phi (deg) from -180 to 180, and the y-axis is theta (deg) from 0 to 180. A color bar on the right of each plot indicates power density in dBW/m^2 from -70 to 10.](51517948c9faff8158db2bd2d6927606_img.jpg)
+
+Figure F-2 displays three angular power density patterns (a, b, and c) measured at different distances from the Base Station (BS). The patterns are shown as heatmaps of power density in dBW/m<sup>2</sup> as a function of azimuth angle  $\phi$  (deg) and elevation angle  $\theta$  (deg).
+
+- (a) 0.75 m: Shows a broad, relatively uniform power distribution across the angular space, with values ranging from approximately -70 dBW/m<sup>2</sup> to 10 dBW/m<sup>2</sup>. The peak is centered around  $\phi = 0$  and  $\theta = 90$ .
+- (b) 2.5 m: Shows a more concentrated power distribution, with a peak power density around 0 dBW/m<sup>2</sup> near the center ( $\phi = 0$ ,  $\theta = 90$ ).
+- (c) 30 m: Shows a highly concentrated power distribution, with a sharp peak power density around 10 dBW/m<sup>2</sup> near the center ( $\phi = 0$ ,  $\theta = 90$ ), and values dropping to -70 dBW/m<sup>2</sup> at the periphery.
+
+Three heatmaps (a, b, c) showing angular power density patterns at 0.75 m, 2.5 m, and 30 m from the BS. The x-axis is phi (deg) from -180 to 180, and the y-axis is theta (deg) from 0 to 180. A color bar on the right of each plot indicates power density in dBW/m^2 from -70 to 10.
+
+**Figure F-2: Angular power density patterns measured at (a) 0.75 m, (b) 2.5 m and (c) 30 m from the BS [31]**
+
+---
+
+## Annex G (informative): Excel spreadsheets for MU derivation
+
+This annex collects information on the Excel spreadsheets attached to this TR, which contain the MU derivation calculations.
+
+Whenever the MU contributors, or MU values are corrected, or new OTA test method is added in this TR, the related Excel spreadsheet is expected to be also corrected in order to keep consistency among the TR and the Excel spreadsheet calculations.
+
+The following Excel spreadsheets are attached to this TR:
+
+1. Spreadsheet 1: FR1 transmitter requirements MU calculation tables
+2. Spreadsheet 2: FR1 receiver requirements MU calculation tables
+3. Spreadsheet 3: FR2 transmitter requirements MU calculation tables
+4. Spreadsheet 4: FR2 receiver requirements MU calculation tables
+5. Spreadsheet 5: FR1 co-location requirements MU calculation tables
+
+## Annex H (informative): Change history
+
+| Change history |               |            |        |             |             |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |             |
+|----------------|---------------|------------|--------|-------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting       | TDoc       | C<br>R | R<br>e<br>v | C<br>a<br>t | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | New version |
+| 2020-02        | RAN4#94-e     | R4-2001807 |        |             |             | Skeleton                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | 0.0.1       |
+| 2020-04        | RAN4#94-e     | R4-2003997 |        |             |             | First draft implementing TPs from RAN4#94-e meeting, based on content of R4-2002430.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | 0.1.0       |
+| 2020-05        | RAN4#94-e-Bis | R4-2005609 |        |             |             | Implementation of the agreed TPs on top of version 0.1.0:<br>- R4-2003998 TP to TR 37.941: general sections<br>- R4-2004394 TP to TR 37.941 to introduce additional Tx test cases for PWS<br>- R4-2004526 TP to TR 37.941 : Test uncertainty annexes - update<br>- R4-2004531 TP to TR 37.941 -RX MU value derivation sub-clause 10 update (FR1)<br>- R4-2004535 TP to TR 37.941 Tx TRP emissions MU value derivation sub-clause 11 updates (FR1)<br>- R4-2004536 TP to TR 37.941: Tx TRP emissions MU value derivation sub-clause 11 updates (FR2)<br>- R4-2004537 Spurious emissions MU value derivation sub-clause 12 update (FR1)<br>- R4-2004538 TP to TR 37.941 - Spurious emissions MU value derivation sub-clause 12 update (FR2)<br>- R4-2004641 TP to TR 37.941: cleanup<br>- R4-2004643 TP to TR 37.941: reverberation chamber description correction<br>- R4-2005502 Ambiguity on two orthogonal polarizations measurements<br>- R4-2005503 TP to TR 37.941: Coordinate system<br>- R4-2005504 TP to TR 37.941: conformance testing framework<br>- R4-2005510 TP to TR 37.941: co-location measurements description<br>- R4-2005511 TP to TR 37.941: Correction to reverberation description<br>- R4-2005512 TP to TR 37.941: Improvement of text in subclause 6.3.2<br>- R4-2005601 TP to TR 37.941 -Tx MU value derivation sub-clause 9 update (FR1) | 0.2.0       |
+| 2020-06        | RAN4#95-e     | R4-2009064 |        |             |             | Implementation of the approved TPs on top of version 0.2.0:<br>- R4-2008858 TP to 37.941: MU tables for additional Tx test cases for PWS<br>- R4-2007911 TP to TR 37.941 FR2 TX directional<br>- R4-2007913 TP to TR 37.941 FR2 RX directional<br>- R4-2008856 TP to TR 37.941 MU budget procedure update<br>- R4-2008857 TP to TR 37.941 EIRP MU budget procedure update<br>- R4-2008005 TP to TR 37.941 on editorial corrections for PWS references                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | 0.3.0       |
+| 2020-06        | RAN#88-e      | RP-200810  |        |             |             | Final version of the Rel-15 TR for Approval.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | 2.0.0       |
+
+| Change history |         |           |      |     |     |                                                                                                                                           |             |
+|----------------|---------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc      | CR   | Rev | Cat | Subject/Comment                                                                                                                           | New version |
+| 2020-06        | RAN#88  |           |      |     |     | Approved by plenary – Rel-15 spec under change control                                                                                    | 15.0.0      |
+| 2020-06        | RAN#88  |           |      |     |     | Update to Rel-16 version                                                                                                                  | 16.0.0      |
+| 2020-06        |         |           |      |     |     | Update of history table                                                                                                                   | 16.0.1      |
+| 2020-09        | RAN#89  | RP-201501 | 0003 |     | A   | CR to TR 37.941: Clause 6 Measurement Types                                                                                               | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201501 | 0004 |     | A   | CR to TR 37.941: Clause 6.3.3 Angular alignment in TRP measurements                                                                       | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201501 | 0006 | 1   | A   | Mirror CR to TR 37.941: Completion of MU terms for PWS.                                                                                   | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201501 | 0008 |     | A   | CR to TR 37.941: editorial cleanup, Rel-16                                                                                                | 16.1.0      |
+| 2020-09        | RAN#89  | RP-201501 | 0010 |     | A   | CR to TR 37.941: new Annex for Excel spreadsheets with MU derivation, Rel-16                                                              | 16.1.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0014 |     | A   | CR to TR 37.941: overall TR cleanup, Rel-16                                                                                               | 16.2.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0016 |     | A   | CR to TR 37.941: MU and TT values alignments and corrections, Rel-16                                                                      | 16.2.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0018 |     | A   | CR to TR 37.941: alignments and corrections to the MU contributors and MU derivations, Rel-16                                             | 16.2.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0020 |     | A   | CR to TR 37.941: Corrections to TRP measurement procedures                                                                                | 16.2.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0022 |     | A   | Mirror CR to TR 37.941: Additional test cases for PWS                                                                                     | 16.2.0      |
+| 2020-12        | RAN#90  | RP-202503 | 0024 |     | A   | Mirror CR to TR 37.941: Completion of MU terms for PWS.                                                                                   | 16.2.0      |
+| 2021-09        | RAN#93  | RP-211889 | 0028 |     | F   | Big CR for TR 37.941 Maintenance (Rel-16 CAT F)                                                                                           | 16.3.0      |
+| 2021-12        | RAN#94  | RP-212852 | 0029 |     | F   | Big CR for TR 37.941 maintenance (Rel-16, CAT F)                                                                                          | 16.4.0      |
+| 2023-06        | RAN#100 | RP-231352 | 0039 |     | F   | CR to TR 37.941: correction of n259-related frequency range for MU of the EIRP test requirement, Rel-16                                   | 16.5.0      |
+| 2023-09        | RAN#101 | RP-232498 | 0046 |     | A   | [OTA_BS_testing-Perf] CR to TR 37.941: correction of the applicability of General Chamber (co-location, out-of-band requirements), Rel-16 | 16.6.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37976/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-16/37_series/37976/04dc3838022e96d8d5548bb1b777b38c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6a197c0582671e3b96dc08f4e152ef4ea2f9a01c
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/04dc3838022e96d8d5548bb1b777b38c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ce7b1b1bc1a51c50a10541516b3a40c97d99d47884c0d7ef52155a920ee8bf0
+size 17551
diff --git a/marked/Rel-16/37_series/37976/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/37_series/37976/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e412432ef8849933111679ac3e51b538cc512cab
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60ea37c42f189d5ab54b66c47e9c7a3ba432ed956b6b2558949b9759b51186cc
+size 140882
diff --git a/marked/Rel-16/37_series/37976/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/37_series/37976/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c484b8122b3b137d3f84edac13608d6440a662d
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/1439cb942d9e363bbb3161b5540dd8c6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:407318f4a131b7bbad636258c78944ec0077c67ae637acfb5a57e88a7162d7ae
+size 10143
diff --git a/marked/Rel-16/37_series/37976/14bbaf9e8820aa362b68a5bc8d11a4c2_img.jpg b/marked/Rel-16/37_series/37976/14bbaf9e8820aa362b68a5bc8d11a4c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..134ae5dadfa8de902d8a2113614b11429956aaef
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/14bbaf9e8820aa362b68a5bc8d11a4c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9d954957820f892e1bd8f27690fd6166c165f0b22bc301627ce3cb9167f64c6
+size 33711
diff --git a/marked/Rel-16/37_series/37976/17439b945bd5156395c7ba15bf04f8fb_img.jpg b/marked/Rel-16/37_series/37976/17439b945bd5156395c7ba15bf04f8fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af20a9999c1d8e3211b015e00e24eb000c3b6043
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/17439b945bd5156395c7ba15bf04f8fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b4a4bed05bf6a59ec02dc9d0435abebc3829db2cda9b3975cdfa23a0f34083a
+size 31549
diff --git a/marked/Rel-16/37_series/37976/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/37_series/37976/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6707af4f0a6967b38db3f84b3f76cf9e1ec3f92e
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/1b893df61c2b73b7a85e65fc1f58e203_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c4339f3e2ac8b8c99e30712637255f71ca071d351b9a80006110429293608abe
+size 66291
diff --git a/marked/Rel-16/37_series/37976/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/marked/Rel-16/37_series/37976/3493d7ba4c86f944e159de1bf45ff03d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3b7cc8df5e9cd530f1f1157c1a905a269c3bb498
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/3493d7ba4c86f944e159de1bf45ff03d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab0cd44d8d4e7a5ca70fb82e2628b8f23ef8d37e7e453dbfa8c51b984d05715e
+size 32576
diff --git a/marked/Rel-16/37_series/37976/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/37_series/37976/3da1a07cb87051bf616c9876db958cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87d72d43ac07e8abe8a3339c34bde27f7926ca69
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/3da1a07cb87051bf616c9876db958cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d49e300376a32453c72253bc9275e4be8e3121bab74ce46184b25e902b480b7b
+size 21610
diff --git a/marked/Rel-16/37_series/37976/4aa9c7965776f4f4b8eba638b2c53369_img.jpg b/marked/Rel-16/37_series/37976/4aa9c7965776f4f4b8eba638b2c53369_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f8d7e7f432c6d295aa10e7327e851a94e1dbdc21
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/4aa9c7965776f4f4b8eba638b2c53369_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c6841fe8325513628c89ee2acdfc33f0ea388a3bf50afd4e2e6e582a1932e49
+size 24309
diff --git a/marked/Rel-16/37_series/37976/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-16/37_series/37976/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b581ec04038b93f3c02a8e517fc6926a7e774a77
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad3018302234fed1e83a15badc8df527a234b8ab8dc77c5445eca6a647b16286
+size 137552
diff --git a/marked/Rel-16/37_series/37976/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37976/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01d955e85ce4b36b12507d7a1aa2af028fb68b3a
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3bb8c49c893cfd5d1b755529afd464d0fca4c4d92fe06ebb419bc9ecc7d432e
+size 9482
diff --git a/marked/Rel-16/37_series/37976/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37976/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..081f752208a75295a375e13cd314e1be0048fa83
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62c4798ffff61fdae1fd026dfb07c79fa9b93fd4df66291e30b7f73a4d62b005
+size 5738
diff --git a/marked/Rel-16/37_series/37976/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/37_series/37976/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e678353d41463934779624135c5a2e37ee525de4
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/65e8c0628536d6d4245e9ab46ba070c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d2ccd3af70e817689e4fe3064e219cce026b5c5ef65d6cc3411af94a5d4836f
+size 28809
diff --git a/marked/Rel-16/37_series/37976/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/marked/Rel-16/37_series/37976/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed0a697d7cbb09b02ba0aa6f396e707c7516f0e2
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3dfc3a2a5b02c5af237609c03468ea0cbf29e398703c15794c7c1bc9c04e2fa8
+size 99838
diff --git a/marked/Rel-16/37_series/37976/78ebfe3116918cd317b54c861da8d8d2_img.jpg b/marked/Rel-16/37_series/37976/78ebfe3116918cd317b54c861da8d8d2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..70aeb7da40572a5a7907568617bba168645d1072
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/78ebfe3116918cd317b54c861da8d8d2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7f07b0bd4c927036ca4bd0ac83369c6983c8eb36198f6a538f46d4adbf5a8f2b
+size 34673
diff --git a/marked/Rel-16/37_series/37976/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-16/37_series/37976/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c022c8494dcbd5f096800662192539257e41461d
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/7a0db9703b68b3d06cdaeefc084c0006_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be2951dc164afc5c7f6590ea8673e868c912ac001811f15b4a14fdd0b4fb1672
+size 199793
diff --git a/marked/Rel-16/37_series/37976/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-16/37_series/37976/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fe313c6d6b0fa9bb55c39dee41f4debe29a6f28e
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1c5180fa98f0c7e21384cd75d18055526e38fbd2ae9e9fe5f0e45f8d48204f5
+size 37677
diff --git a/marked/Rel-16/37_series/37976/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/37_series/37976/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..200328ce5e69ab7cef4967f8d212d40dcdc6c27b
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8e25709f53359383ec9ecb5ee10b5f357457bcb2eaf3fa8f4f0b384fad162eee
+size 30283
diff --git a/marked/Rel-16/37_series/37976/822e033872d5ab16e861571f47b81ba7_img.jpg b/marked/Rel-16/37_series/37976/822e033872d5ab16e861571f47b81ba7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c78c94995c1313e73fa822a8faa5d3ed8e58675c
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/822e033872d5ab16e861571f47b81ba7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2db872df81890edfed25f785dfdab77f81cf5c9b6e24f5ce790342431003e2fe
+size 41070
diff --git a/marked/Rel-16/37_series/37976/853ef5420f0432e626e83987e3f38a0b_img.jpg b/marked/Rel-16/37_series/37976/853ef5420f0432e626e83987e3f38a0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ba4ed1a487b14f4a173d01162c17fcbaa40aba2e
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/853ef5420f0432e626e83987e3f38a0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:31a2d5db9cfba52e1bcd9879f9b98212bfac6cbc4082cf8b8dfd7f67db626b5b
+size 71192
diff --git a/marked/Rel-16/37_series/37976/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/37_series/37976/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b51cb9385f04a94943ee6b993387f60b6cf332ea
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/898fb89a50d9ec1dfb4e425c816976a7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:714a15820bf1b23cadc848ebc94f733c037de70d8c0c792c9617e1fcd624fc18
+size 29482
diff --git a/marked/Rel-16/37_series/37976/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-16/37_series/37976/90ddf538ef276510e2b631f7b96654e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51d5b03c823dda23697e7a988d29f5055af8220a
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/90ddf538ef276510e2b631f7b96654e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f142f223802e148a2a0463db82e0dff10d80aa7f88a2e7ca59f326e5d4a62410
+size 34060
diff --git a/marked/Rel-16/37_series/37976/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/37_series/37976/9b686adccf125267a013fa25721231a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0527c4273fa83aceea7c65daba89648090d7f0b8
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/9b686adccf125267a013fa25721231a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ea0316d6d9f69ba9223b86c7d14a3369196f2c267786d11c23b876d8f749f60
+size 30707
diff --git a/marked/Rel-16/37_series/37976/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/marked/Rel-16/37_series/37976/a1890b9a9b85f13e67ed59bbad623659_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a43e4c141acb53ae5b657e143a6469870786f656
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/a1890b9a9b85f13e67ed59bbad623659_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b10de6e374fba027b46ca30f0aead6e0643a7a10b3b420e86897d4b567cebb97
+size 36671
diff --git a/marked/Rel-16/37_series/37976/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/37_series/37976/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..414a272c21cc2cf3e0e74693e2294900433a9976
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a94a701e2b7f9fc88b25b078a638738095e7e8b01a8c6f0f962d804c5a4a7cd
+size 63054
diff --git a/marked/Rel-16/37_series/37976/a97f7c055c1fd8d79037d02b3fc38496_img.jpg b/marked/Rel-16/37_series/37976/a97f7c055c1fd8d79037d02b3fc38496_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a53eab1cc5e107330caf222169aa30501a72d709
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/a97f7c055c1fd8d79037d02b3fc38496_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c8c42d15c6cbca226d50301e3eb8296682953f05f8e6a6e82402f2e91a8f5751
+size 39228
diff --git a/marked/Rel-16/37_series/37976/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/37_series/37976/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..116d0a15d2ad7dd389f422f0c7b7554eb98c5465
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d50f48c05b7b29c74252281d6be120073ff6e6d13a2dcf2558a46a16119c49a9
+size 56610
diff --git a/marked/Rel-16/37_series/37976/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-16/37_series/37976/c1278da91cbcabe32628e589ebc47418_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2b7a2aff588d2d21d30acd7fb7754f9291809355
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/c1278da91cbcabe32628e589ebc47418_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf13db430ba8057b763bedb5c882f29d2d88d2e0dc1a07948afed5a3fb014286
+size 39103
diff --git a/marked/Rel-16/37_series/37976/c85b57b2414f341860dfc338e1cf2509_img.jpg b/marked/Rel-16/37_series/37976/c85b57b2414f341860dfc338e1cf2509_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..064cb38abe54a1fa0381fe01af74c2ded908d70c
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/c85b57b2414f341860dfc338e1cf2509_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b61e1cf0ddb8f954b876861f8653a07553eb063bfd818dbe3fcf2c9836b2a782
+size 40863
diff --git a/marked/Rel-16/37_series/37976/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/37_series/37976/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3681199a46b7977bc87768ea06fa30e172684bcb
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/dbbc0baac7341cda76cc4f8355dce23f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:217e2eb7111a27faee35ef93db6fc11b3a717bac9556574996d1d5c322eeb425
+size 29434
diff --git a/marked/Rel-16/37_series/37976/df1966d80c74bc127f159a48f38b13ee_img.jpg b/marked/Rel-16/37_series/37976/df1966d80c74bc127f159a48f38b13ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4180f0b06e6dafce99157dba8e551f4ffe792886
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/df1966d80c74bc127f159a48f38b13ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1cdaa1b91a3df54417d13249411d2fb9e5603dc2517c431e245de99e46eb4d1
+size 55057
diff --git a/marked/Rel-16/37_series/37976/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/37_series/37976/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..00e2b57bf59cc008963d4ecced96b259a56d8a2c
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92ca64a746db10219c8b130de96a5ec90b31b1fe249b4c2681d420c240c3aee6
+size 305099
diff --git a/marked/Rel-16/37_series/37976/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/37_series/37976/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..986eef48640a3a2f1ed2bd3c40a37eeaa9c4e0ab
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7d4ab8e11a78871298fd5f46b89905d39485d3abcbd42acc6f26d5df953ceb5
+size 25651
diff --git a/marked/Rel-16/37_series/37976/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/37_series/37976/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7028815ec133ac0aaec921d3b1521b5918c3c4d
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2ff1a3f2de4368cc158b2a65d6336f8ade8f6d79443b9d09ee0f59b74032c46
+size 77647
diff --git a/marked/Rel-16/37_series/37976/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/37_series/37976/f2ea0f64a770b22b902820457d262265_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f99b62d4995d0487096b26896e1fc022584318b9
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/f2ea0f64a770b22b902820457d262265_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d052fb50e717e29cb07e06d4331ee1dc92562c2f149ca2ab390ee4cb49a45c3
+size 21912
diff --git a/marked/Rel-16/37_series/37976/fb4274c4b7882a4059103f1dbca9b111_img.jpg b/marked/Rel-16/37_series/37976/fb4274c4b7882a4059103f1dbca9b111_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b3a30869872e9a35654114c79befdabdd98ee62
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/fb4274c4b7882a4059103f1dbca9b111_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2226fce39168c50e02c8e680d4437c51bc7a5806f0a06abc4daedb543442766
+size 29177
diff --git a/marked/Rel-16/37_series/37976/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg b/marked/Rel-16/37_series/37976/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8cc5bbeacd67f0d98ef16a3841745616dad87fb1
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/fbdb9a4a74e70721e19f3d576ba7b651_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6780e7b312b0311b6409785f258a7b378adb1117e4dd515425a830e541bd87da
+size 63017
diff --git a/marked/Rel-16/37_series/37976/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/37_series/37976/fd3cbb53e991f8209ba17b398f426e13_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3bdb7e4c494ec0d16dac7963b15525b517acb236
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/fd3cbb53e991f8209ba17b398f426e13_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a110fafbb379024532d5a22b1a6d0061ea09d314623787424fb8d03ed2c936b
+size 76999
diff --git a/marked/Rel-16/37_series/37976/raw.md b/marked/Rel-16/37_series/37976/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..792105227efc04dd29e273b9cb64ee285b52969a
--- /dev/null
+++ b/marked/Rel-16/37_series/37976/raw.md
@@ -0,0 +1,2381 @@
+
+
+# 3GPP TR 37.976 V16.0.0 (2020-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Measurement of radiated performance for Multiple Input Multiple Output (MIMO) and multi-antenna reception for High Speed Packet Access (HSPA) and LTE terminals (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+---
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top. Below the "P" is a red signal wave icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                         |    |
+|---------------------------------------------------------|----|
+| Foreword .....                                          | 5  |
+| 1 Scope.....                                            | 6  |
+| 2 References.....                                       | 6  |
+| 3 Definitions, symbols and abbreviations .....          | 7  |
+| 3.1 Definitions.....                                    | 7  |
+| 3.2 Symbols.....                                        | 7  |
+| 3.3 Abbreviations .....                                 | 7  |
+| 4 Introduction.....                                     | 8  |
+| 4.1 Background .....                                    | 8  |
+| 4.2 Study item objective.....                           | 8  |
+| 4.3 High Level Requirements.....                        | 8  |
+| 4.4 Proposed work plan.....                             | 8  |
+| 5 Performance Metrics .....                             | 11 |
+| 5.1 Figure of Merits.....                               | 11 |
+| 5.1.1 Definition of MIMO Throughput .....               | 11 |
+| 5.1.2 Definition of SNR.....                            | 11 |
+| 5.1.2.1 Multiple probe antenna based method.....        | 12 |
+| 5.1.2.2 Reverberation chamber based method.....         | 13 |
+| 5.1.2.3 Two-stage method.....                           | 13 |
+| 5.2 Receiver Performance Metrics.....                   | 13 |
+| 6 Measurement Methodologies.....                        | 13 |
+| 6.1 Fixed Reference Measurement Channels (FRCs) .....   | 13 |
+| 6.2 MIMO Channel Models .....                           | 13 |
+| 6.3 Downlink Measurement Methodologies.....             | 17 |
+| 6.3.1 Methodologies based on Anechoic RF Chamber .....  | 18 |
+| 6.3.1.1 Candidate Solution 1.....                       | 18 |
+| 6.3.1.1.1 Concept and Configuration .....               | 19 |
+| 6.3.1.1.2 Test Conditions .....                         | 20 |
+| 6.3.1.2 Candidate Solution 2.....                       | 21 |
+| 6.3.1.2.1 Concept and Configuration .....               | 22 |
+| 6.3.1.2.1A Scalability of the methodology .....         | 23 |
+| 6.3.1.2.2 Test Conditions .....                         | 24 |
+| 6.3.1.3 Candidate Solution 3.....                       | 25 |
+| 6.3.1.3.1 Concept and Configuration .....               | 25 |
+| 6.3.1.3.2 Test Conditions .....                         | 26 |
+| 6.3.1.4 Candidate Solution 4.....                       | 27 |
+| 6.3.1.4.1 Concept and Configuration .....               | 27 |
+| 6.3.1.5 Candidate Solution 5.....                       | 28 |
+| 6.3.1.5.1 Concept and Configuration .....               | 28 |
+| 6.3.1.5.2 Test Conditions .....                         | 31 |
+| 6.3.1.Y Downlink Transmission Modes .....               | 32 |
+| 6.3.2 Methodologies based on Reverberation Chamber..... | 32 |
+| 6.3.2.1 Candidate Solution 1.....                       | 32 |
+| 6.3.2.1.1 Concept and Configuration .....               | 33 |
+| 6.3.2.1.2 Test Conditions .....                         | 34 |
+| 6.3.2.2 Candidate Solution 2.....                       | 35 |
+| 6.3.2.2.1 Concept and Configuration .....               | 36 |
+| 6.3.2.2.2 Test Conditions .....                         | 36 |
+| 6.3.2.Y Downlink Transmission Modes .....               | 37 |
+| 7 Measurement Results from COST2100 .....               | 37 |
+| 7.1 Reference Measurement Channels .....                | 37 |
+
+|                               |                                                                                                         |           |
+|-------------------------------|---------------------------------------------------------------------------------------------------------|-----------|
+| 8                             | Measurement Results from CTIA .....                                                                     | 37        |
+| 8.1                           | Reference Measurement Channels .....                                                                    | 37        |
+| 9                             | Conclusions .....                                                                                       | 38        |
+| 9.1                           | Comparison of Candidate Methodologies .....                                                             | 38        |
+| 9.1.1                         | Definitions of rows in the table .....                                                                  | 41        |
+| 9.2                           | Lessons learnt and conclusions .....                                                                    | 42        |
+| 10                            | Recommendations .....                                                                                   | 43        |
+| <b>Annex A (Informative):</b> | <b>Test Plan for Anechoic Chamber based candidate methodologies with 3 or more probe antennas .....</b> | <b>45</b> |
+| A.1                           | Introduction .....                                                                                      | 45        |
+| A.2                           | Test setup .....                                                                                        | 45        |
+| A.2.1                         | Calibration .....                                                                                       | 46        |
+| A.2.1.1                       | Calibration Check .....                                                                                 | 46        |
+| A.2.2                         | Radio Channel Conditions .....                                                                          | 47        |
+| A.2.2.1                       | Average channel power .....                                                                             | 47        |
+| A.3                           | Test Procedure .....                                                                                    | 48        |
+| A.3.1                         | HSDPA connection settings .....                                                                         | 48        |
+| A.3.1.1                       | FRC .....                                                                                               | 48        |
+| A.3.2                         | Method of test .....                                                                                    | 49        |
+| <b>Annex B (Informative):</b> | <b>LTE MIMO OTA Test Plan .....</b>                                                                     | <b>51</b> |
+| B.1                           | Test Objectives .....                                                                                   | 51        |
+| B.2                           | Test Setup .....                                                                                        | 51        |
+| B.2.1                         | Figure of Merits (FOMs) .....                                                                           | 54        |
+| B.2.2                         | Channel Models .....                                                                                    | 55        |
+| B.2.3                         | Antenna Probes .....                                                                                    | 55        |
+| B.2.4                         | eNodeB Emulator Parameter Settings .....                                                                | 56        |
+| B.2.5                         | Reference DUTs Configurations .....                                                                     | 57        |
+| B.3                           | Calibration of Test System .....                                                                        | 58        |
+| B.3.1                         | Calibration Procedure for Anechoic-chamber based methodologies .....                                    | 58        |
+| B.3.1.1                       | Probe power calibration .....                                                                           | 58        |
+| B.3.1.2                       | Channel power calibration .....                                                                         | 59        |
+| B.3.1.3                       | Calibration check .....                                                                                 | 59        |
+| B.3.2                         | Calibration Procedure for Reverberation-chamber based methodologies .....                               | 60        |
+| B.3.2.1                       | Tuning Reverberation Chamber to Specific Channel Model .....                                            | 61        |
+| B.3.2.2.1                     | Reverberation Chamber Combined with Channel Emulator .....                                              | 61        |
+| B.3.2.2                       | Average Path Loss Measurement .....                                                                     | 61        |
+| B.3.3                         | Calibration Procedure for 2-Stage methodologies .....                                                   | 62        |
+| B.3.3.1                       | Antenna pattern measurement calibration in stage I .....                                                | 62        |
+| B.3.3.3                       | Power calibration for results comparison from different OTA test methods .....                          | 64        |
+| B.3.4                         | Calibration Procedure for antenna pattern based methodologies .....                                     | 64        |
+| B.3.5                         | Calibration Procedure for two-channel method .....                                                      | 65        |
+| B.4                           | Test Procedure .....                                                                                    | 65        |
+| B.4.1                         | Test Procedure 1 .....                                                                                  | 65        |
+| B.4.1A                        | Test Procedure 1A (Reverberation Chamber Based Methodologies) .....                                     | 67        |
+| B.4.2                         | Test Procedure 2 .....                                                                                  | 67        |
+| B.4.3                         | Test Procedure 3 (Antenna spatial correlation measurement) .....                                        | 68        |
+| B.4.4                         | Test Procedure 4 (Two-stage throughput) .....                                                           | 69        |
+| B.4.5                         | Test Procedure 5 for two-channel method .....                                                           | 71        |
+| <b>Annex C (informative):</b> | <b>Change history .....</b>                                                                             | <b>72</b> |
+
+# --- Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is the technical report for the study item on MIMO OTA, which was approved at TSG RAN#43 [2]. The scope of the SI is to define a 3GPP methodology for measuring the radiated performance of multiple antenna reception and MIMO receivers in the UE. The test methodology should be relevant for HSPA and LTE technologies, with particular focus on handheld devices and devices embedded in laptop computers.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] RP-090352, "Proposed new study item: Measurement of radiated performance for MIMO and multi-antenna reception for HSPA and LTE terminals."
+- [3] TD(09) 766, COST2100 SWG 2.2, Braunschweig, Germany, Pekka Kyösti et. al. "Proposal for standardized test procedure for OTA testing of multi-antenna terminals", Elektrob.it.
+- [4] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) Antenna Performance Conformance Testing".
+- [5] 3GPP TS 25.214, "Physical Layer Procedures (FDD)"
+- [6] TD(09) 742, COST 2100 SWG 2.2, Braunschweig, Germany, February 2009, J. Takada, "Handset MIMO Antenna Testing Using a RF-controlled Spatial Fading Emulator".
+- [7] 3GPP TS 36.212, "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding".
+- [8] 3GPP TS 36.213, "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures".
+- [9] CTIA, "Test Plan for Mobile Station Over the Air Performance - Method of Measurement for Radiated RF Power and Receiver Performance", Revision 3.0, 4/30/2009.
+- [10] 3GPP TS 36.101, "User Equipment (UE) radio transmission and reception".
+- [11] 3GPP TR 25.914, "Measurements of radio performances for UMTS terminals in speech mode".
+- [12] 3GPP TS 36.521-1, "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification Radio transmission and reception; Part 1: Conformance Testing"
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |                                                   |
+|----------|---------------------------------------------------|
+| H        | Channel matrix                                    |
+| $\phi$   | Adjacent probe separation angle                   |
+| $\theta$ | Zenith angle in the spherical co-ordinate system  |
+| $\phi$   | Azimuth angle in the spherical co-ordinate system |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|      |                                                     |
+|------|-----------------------------------------------------|
+| AoA  | Angle of Arrival                                    |
+| AoD  | Angle of Departure                                  |
+| BS   | Base Station                                        |
+| BSE  | Base Station Emulator                               |
+| BTS  | Base Transceiver Station                            |
+| COST | Cooperation of Scientific and Technical             |
+| CTIA | Cellular and Telecommunication Industry Association |
+| DL   | Downlink                                            |
+| DUT  | Device Under Test                                   |
+| FRC  | Fixed Reference Measurement Channel                 |
+| FTP  | File Transfer Protocol                              |
+| HSPA | High Speed Packet Access                            |
+| HTTP | HyperText Transfer Protocol                         |
+| LTE  | Long Term Evolution                                 |
+| MCS  | Modulation and Coding Scheme                        |
+| MIMO | Multiple Input Multiple Output                      |
+| OTA  | Over-the-Air                                        |
+| SCM  | Spatial Channel Model                               |
+| SCME | Spatial Channel Model Extension                     |
+| SI   | Study Item                                          |
+| SISO | Single Input Single Output                          |
+| SNR  | Signal-to-Noise Ratio                               |
+| SS   | System Simulator                                    |
+| TBS  | Transport Block Size                                |
+| TTI  | Transmission Time Interval                          |
+| UE   | User Equipment                                      |
+| UDP  | User Datagram Protocol                              |
+| UL   | Uplink                                              |
+| VRC  | Variable Reference Measurement Channel              |
+
+# 4 Introduction
+
+## 4.1 Background
+
+The use of MIMO and receiver diversity in the UE is expected to give large gains in downlink throughput performance for HSPA and LTE devices. 3GPP already defined conducted tests for MIMO and multiple antenna receivers (type 1 and type 3 in TS25.101 for HSPA demodulation), but it is clear that the ability to duplicate these gains in the field is highly dependent on the performance of the receive-antenna system.
+
+At TSG RAN#41, it was indicated that there is a need for a test methodology to be created with the aim of measuring and verifying the radiated performance of multi-antenna and MIMO receiver in UEs for both HSPA and LTE devices. As an outcome of the discussion, an LS was sent to COST 2100 SWG2.2 and CTIA ERP to ask them for feedback on their plans/ongoing work in this area, and also the timescales for which such work could be completed to define such a methodology, with particular focus on handheld devices and devices embedded in laptop computers.
+
+Since then, feedback from COST 2100 and CTIA has suggested they are happy to work on this topic. However given that 3GPP is the customer for this work as well as being a potential contributor, it is important to aim for commonly-accepted measurement and test methodology to be used across the industry.
+
+## 4.2 Study item objective
+
+The high level objective of this study item is to define a 3GPP methodology for measuring the radiated performance of multiple antenna reception and MIMO receivers in the UE. The test methodology should be relevant for HSPA and LTE technologies, with particular focus on handheld devices and devices embedded in laptop computers.
+
+The steps intended to achieve this involve the following:
+
+- 1) Identify the performance metrics and clarify the requirements of operators for defining such a methodology.
+- 2) Review of potential solutions also considering input from CTIA ERP and COST 2100.
+- 3) Agree the final solution, and detail the agreed 3GPP solution in a technical report to be reported to RAN plenary.
+- 4) Maintain ongoing communication with COST 2100 and CTIA ERP to ensure industry coordination on this topic.
+
+TSG RAN should contact TSG GERAN to get feedback on the applicability of such a test methodology for GERAN.
+
+## 4.3 High Level Requirements
+
+The following high level requirements are agreed by RAN4:
+
+1. Measurement of radiated performance for MIMO and multi-antenna reception for HSPA and LTE terminals must be performed over-the-air, i.e. without RF cable connections to the DUT.
+
+NOTE 1: DUTs to the test house will have accessibility to temporary antenna port for conducted purposes.
+
+NOTE 2: Temporary antenna port is used to assess to DUT receiver.
+
+NOTE 3: UE special function to measure antenna pattern is not desirable for MIMO OTA purposes.
+
+2. The MIMO OTA method(s) must be able to differentiate between a good terminal and a bad terminal in terms of MIMO OTA performance.
+3. The desired primary Figure of Merit (FOM) is throughput.
+
+## 4.4 Proposed work plan
+
+Figure 4.4-1 illustrates the work plan for MIMO OTA.
+
+Figure 4.4-2 illustrates the extended work plan for MIMO OTA due to the SI extension.
+
+Figure 4.4-3 illustrates the extended work plan for MIMO OTA as a result of further extension of the SI.
+
+![Flowchart of the MIMO OTA work plan, showing two parallel tracks of meetings and discussions leading to the finalization of candidate solutions.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg)
+
+```
+graph TD; subgraph LeftTrack [Left Track]; L1[RAN4#50bis : 23 – 27 March 2009, Seoul, South Korea<br/>- Agree skeleton report for the MIMO OTA study item.<br/>- Agree on work plan and schedule for MIMO OTA<br/>- Open discussion on figure of merits/parameters<br/>- Discussions on candidate solutions]; L2[RAN4#51 : 4 – 8 May 2009, San Francisco, USA<br/>- Agree on figure of merits/parameters to use<br/>- Discussions on candidate solutions<br/>- Present/discuss measurement data to verify each candidate solution]; L3[RAN4#51bis : 29 June – 2 July 2009, Los Angeles, USA<br/>- Discuss measurement procedure<br/>- Discuss candidate solutions<br/>- More measurement data for MIMO OTA test methods<br/>- Revise work plan]; L4[RAN4#52 : 24 – 28 August 2009, China<br/>- Verification of each candidate solution – Phase 1]; L5[RAN4#52bis : 12 – 15 October, Japan<br/>- Verification of each candidate solution – Phase 2]; L6[RAN4#53 : 9 – 13 November, Jeju Island, South Korea<br/>- Resolve remaining technical issues<br/>- Complete study item and technical report<br/>- Report to RAN#46 on recommendations of MIMO OTA methods.]; L1 --> L2; L2 --> L3; L3 --> L4; L4 --> L5; L5 --> L6; subgraph RightTrack [Right Track]; R1[7th MCM: 16th – 18th February, 2009, Braunschweig, Germany<br/>- Discuss Figure of Merits<br/>- Candidate proposals discussion<br/>- Some measurement data analysis for MIMO OTA]; R2[8th MCM: 18th – 19th May, 2009, Valencia, Spain<br/>- Measurement data analysis for each MIMO OTA method<br/>- Further discussion on candidate solutions<br/>- Finalise figure of merits for MIMO OTA]; R3[9th MCM: TBA, Vienna, Austria<br/>- Detail verification of each candidate solution<br/>- More measurement data campaigns<br/>- Use realistic devices]; R4[10th MCM: TBA, Vienna, Austria<br/>- finalise each candidate solution<br/>- resolve any technical issues]; R1 --> R2; R2 --> R3; R3 --> R4;
+```
+
+**Left Track (RAN meetings):**
+
+- RAN4#50bis : 23 – 27 March 2009, Seoul, South Korea**
+  - Agree skeleton report for the MIMO OTA study item.
+  - Agree on work plan and schedule for MIMO OTA
+  - Open discussion on figure of merits/parameters
+  - Discussions on candidate solutions
+- RAN4#51 : 4 – 8 May 2009, San Francisco, USA**
+  - Agree on figure of merits/parameters to use
+  - Discussions on candidate solutions
+  - Present/discuss measurement data to verify each candidate solution
+- RAN4#51bis : 29 June – 2 July 2009, Los Angeles, USA**
+  - Discuss measurement procedure
+  - Discuss candidate solutions
+  - More measurement data for MIMO OTA test methods
+  - Revise work plan
+- RAN4#52 : 24 – 28 August 2009, China**
+  - Verification of each candidate solution – Phase 1
+- RAN4#52bis : 12 – 15 October, Japan**
+  - Verification of each candidate solution – Phase 2
+- RAN4#53 : 9 – 13 November, Jeju Island, South Korea**
+  - Resolve remaining technical issues
+  - Complete study item and technical report
+  - Report to RAN#46 on recommendations of MIMO OTA methods.
+
+**Right Track (MCM meetings):**
+
+- 7<sup>th</sup> MCM: 16<sup>th</sup> – 18<sup>th</sup> February, 2009, Braunschweig, Germany**
+  - Discuss Figure of Merits
+  - Candidate proposals discussion
+  - Some measurement data analysis for MIMO OTA
+- 8<sup>th</sup> MCM: 18<sup>th</sup> – 19<sup>th</sup> May, 2009, Valencia, Spain**
+  - Measurement data analysis for each MIMO OTA method
+  - Further discussion on candidate solutions
+  - Finalise figure of merits for MIMO OTA
+- 9<sup>th</sup> MCM: TBA, Vienna, Austria**
+  - Detail verification of each candidate solution
+  - More measurement data campaigns
+  - Use realistic devices
+- 10<sup>th</sup> MCM: TBA, Vienna, Austria**
+  - finalise each candidate solution
+  - resolve any technical issues
+
+Flowchart of the MIMO OTA work plan, showing two parallel tracks of meetings and discussions leading to the finalization of candidate solutions.
+
+Figure 4.4-1: MIMO OTA work plan
+
+![Flowchart and Gantt chart showing the extension of the MIMO OTA work plan. The flowchart details meetings from RAN4 AH#2 to RAN4#61, with inputs from COST2100 and CTIA. The Gantt chart tracks tasks like LTE Round-robin test, HSPA Round robin test, and Technical Points across various meetings and dates from 2011 to 2011.11.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the further extension of the MIMO OTA work plan, showing a sequence of meetings and a detailed Gantt chart of tasks.
+
+**Meetings and Inputs:**
+
+- RAN4 AH#2: Dublin, Ireland**
+  - Agreed on MIMO OTA FOMs and definitions.
+  - Agreed on high level requirements (operator requirements)\*.
+  - Agreed on comparison table and methodologies comparison.
+  - Agreed on MIMO OTA channel models.
+  - Discuss Reference measurement channels for HSPA and LTE.
+- Inputs to RAN4 AH#2:**
+  - COST2100 Email Discussion: MIMO OTA Definitions, Reference Measurement Channels.
+  - Inputs from CTIA: OTA test plan version 3.0.0, Measurement results.
+- RAN4#55: Montreal, Canada**
+  - Agreed on any pending issues from last RAN4 meeting.
+  - MIMO OTA calibrations.
+  - MIMO OTA measurement uncertainty.
+  - MIMO OTA general measurement procedures.
+  - Preliminary measurement results discussions.
+  - Discussion on TR recommendations, conclusions.
+- Inputs to RAN4#55:**
+  - COST2100 Email Discussion: Measurement results, Measurement uncertainty, procedures, etc.
+  - Inputs from CTIA: Measurement results.
+- RAN4 AH#3 Bratislava, Slovakia**
+  - Agreed on pending issues from last RAN4 meeting.
+  - Measurement campaign results discussions.
+  - Potential merging of MIMO OTA methodologies.
+  - Agreed on text proposals on TR (recommendations, conclusions).
+- Inputs to RAN4 AH#3:**
+  - 11<sup>th</sup> MCM: Aalborg, Denmark: Measurement campaign results discussions.
+  - Inputs from CTIA: Measurement results.
+- RAN4#56: August, Madrid, Spain**
+  - SI on hold.
+- RAN4#AH4: October, Xian, China**
+  - Analysis of HSPA measurement campaign results.
+- Inputs to RAN4#AH4:** Inputs from CTIA: MIMO OTA summary of findings.
+- RAN4#57: November, Jacksonville, USA**
+  - Analysis of HSPA measurement campaign results.
+- Inputs to RAN4#57:**
+  - 12<sup>th</sup> MCM: (Nov) Bologna, Italy: COST2100 action completed, MIMO OTA summary of findings.
+
+**MIMO OTA work plan**
+
+**Gantt Chart Details:**
+
+- Main Tasks:**
+  - LTE Round-robin test:** Test Plan Finalized (RAN4#57AH), EU/US 1<sup>st</sup> round (RAN4#58AH), Results analysis (MIMO OTA AH), EU/US 2<sup>nd</sup> round (RAN4#60AH), Discussion Completed (RAN4#61).
+  - HSPA Round robin test:** LS from COST2100 (RAN4#57AH), Results analysis in 3GPP (RAN4#58AH), Capture in TR (MIMO OTA AH), Discussion Completed (RAN4#60AH).
+  - Technical Points:** List Up Open issues (RAN4#58AH), 2D/3D (MIMO OTA AH), FRC/VRC (MIMO OTA AH), Noise/Interference (MIMO OTA AH), Discussion Completed (RAN4#60AH).
+  - Final solution(s):** Discussion based on all the results (RAN4#60AH), Finalized (RAN4#61).
+  - LTE TRP/TRS:** Discuss and Define in CTIA (RAN4#57AH), Input to 3GPP (RAN4#60AH).
+- Timeline:** 2011.01, 2011.03, 2011.09, 2011.11.
+- Meetings on Timeline:** RAN4#57AH Austin, RAN4#58AH Shanghai, MIMO OTA AH Aalborg, RAN4#60AH Chuhi, RAN4#61 San Francisco, RAN#54.
+- Completion:** Completion of study item (RAN#54).
+
+Flowchart and Gantt chart showing the extension of the MIMO OTA work plan. The flowchart details meetings from RAN4 AH#2 to RAN4#61, with inputs from COST2100 and CTIA. The Gantt chart tracks tasks like LTE Round-robin test, HSPA Round robin test, and Technical Points across various meetings and dates from 2011 to 2011.11.
+
+Figure 4.4-3: Further extension of MIMO OTA work plan
+
+# 5 Performance Metrics
+
+*<Editor: list down the essential parameters to be measured, metrics of measuring OTA performance>*
+
+## 5.1 Figure of Merits
+
+The performance metrics applies to both HSPA and LTE system.
+
+**Table 5-1: Categories of Figure of Merits**
+
+| Category    | I                                  | II                      | III                                                       | IV                                 | V                           |
+|-------------|------------------------------------|-------------------------|-----------------------------------------------------------|------------------------------------|-----------------------------|
+| FOMs        | MIMO<br>Throughput<br>CQI<br>(FRC) | TRP<br>TRS              | Gain Imbalance<br>Spatial<br>correlation<br>MIMO Capacity | Antenna<br>Efficiency<br>MEG       | MIMO<br>Throughput<br>(VRC) |
+| Type        | OTA                                | OTA                     | MIMO antennas                                             | MIMO antennas                      | OTA                         |
+| Methodology | Active<br>(with fading)            | Active<br>(with fading) | Passive/Active<br>(with fading)                           | Passive/Active<br>(without fading) | Active<br>(with fading)     |
+
+NOTE 1: Category V MIMO throughput measurement is performed over active communication link with DUT by using the variable reference channel. This is FFS.  
+NOTE 2: FOMs can be measured either by establishing active communication link with the DUT (similar to current SISO OTA) incorporating realistic fading propagation channel models (Active methodology), or by simply transmitting RF signal in uplink or downlink, with or without the fading effect included in the measurement setup (Passive methodology).
+
+### 5.1.1 Definition of MIMO Throughput
+
+MIMO Throughput is defined here as the time-averaged number of correctly received transport blocks in a communication system running an application, where a Transport Block is defined in the reference measurement channel. From OTA perspective, this is also called MIMO OTA throughput.
+
+The MIMO OTA throughput is measured at the top of physical layer of HSPA and LTE system. Therefore, this is also measured at the same point as in the conductive measurement setup: under the use of FRC, the SS transmit fixed-size payload bits to the DUT. The DUT signals back either ACK or NACK to the SS. The SS then records the following:
+
+- Number of ACKs,
+- Number of NACKs, and
+- Number of DTX TTIs
+
+Hence the MIMO (OTA) throughput can be calculated as
+
+$$MIMO (OTA) Throughput = \frac{Transmitted\ TBS \times Num\ of\ ACKs}{MeasurementTime}$$
+
+where Transmitted TBS is the Transport Block Size transmitted by the SS, which is fixed for a FRC during the measurement period. MeasurementTime is the total composed of successful TTIs (ACK), unsuccessful TTIs (NACK) and DTX-TTIs.
+
+The time-averaging is to be taken over a time period sufficiently long to average out the variations due to the fading channel. Therefore, this is also called the average MIMO OTA throughput. The throughput should be measured at a time when eventual start-up transients in the system have evanesced.
+
+### 5.1.2 Definition of SNR
+
+The typical configuration of a MIMO handset under real channel with co-channel interference is shown in Figure 5.1.2-1. As a first step the interference can be simplified to use non-directional AWGN with no fading. More realistic noise including narrowband statistical scheduling and directional aspects is for further study.
+
+To evaluate the MIMO antenna's influence, a multipath channel needs to be applied to the downlink signal. This configuration can still be illustrated by Figure 5.1.2-1.
+
+![Diagram illustrating a MIMO handset under co-channel interference. A central blue rectangle represents the handset. Surrounding it are several antenna elements represented by triangles. A green triangle labeled 'S' is on the right, representing the signal source. Other triangles labeled I1, I2, I3, I, and Im represent co-channel interferers at various positions around the handset.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg)
+
+Diagram illustrating a MIMO handset under co-channel interference. A central blue rectangle represents the handset. Surrounding it are several antenna elements represented by triangles. A green triangle labeled 'S' is on the right, representing the signal source. Other triangles labeled I1, I2, I3, I, and Im represent co-channel interferers at various positions around the handset.
+
+**Figure 5.1.2-1: MIMO Handset under co-channel interference**
+
+Suppose a reference dipole antenna is placed in the center of configuration, then the received signal power by one element of the handset antenna is
+
+$P = P_S H_S G_{dipole}$ , where  $H$  is the channel gain for the transmitted signal under given configuration,  $G_{dipole}$  is the antenna gain of the dipole antenna.
+
+The received interference signal is
+
+$$P_I = \sum_i P_{Ii} H_i G_{dipole}$$
+
+The SNR is defined to be  $SNR = P / P_I$  when there is a co-channel interferer. If the co-channel interferer is removed by setting the power of the interferer zero, then the test configuration corresponds to the test case where the device under test self noise will be the major noise influencing the performance. It is not possible to know the actual SNR for this case without knowing details of the handset design. From the MIMO OTA test perspective, it is not necessary to know the actual SNR for this case. What is needed for the test is to control the downlink signal power to search for the lowest power level at which the DUT achieves a pre-defined throughput. This power corresponds to potential improvement in coverage.
+
+The SNR definition is applied to the three main MIMO radiated test methods as follows:
+
+#### 5.1.2.1 Multiple probe antenna based method
+
+For the multiple probe antenna based methods, the AWGN is applied to a full circle of antennas surrounding the DUT with equal angle interval. On each probe antenna, equal power AWGN is applied. Equal power AWGN is applied to both vertical polarization and horizontal polarization.
+
+The AWGN can be super-imposed on the probe antennas for signal generation or can be on independent probe antennas. The number of probe antennas for AWGN noise generation is at least 3 to have a good approximation of spatial AWGN.
+
+When testing MIMO antenna design with the throughput figure of merits, the AWGN interferer's power level is set to a constant level. The downlink power level is changed to vary the SNR. The measured throughput under different SNR will be used to evaluate the different MIMO antenna design. When testing the coverage improvement, the AWGN interferers are turned off. The downlink signal power is changed to find the power level where a given throughput is achieved. The measured signal power with a dipole for this case will be a measure of potential coverage improvement for the MIMO downlink.
+
+#### 5.1.2.2 Reverberation chamber based method
+
+For the reverberation chamber based method, the way of applying AWGN is to apply it to the test signal before it is radiated through the test antenna. When testing MIMO antenna design with the throughput figure of merits, the AWGN interferer's power level is set to a constant level. The downlink power level is changed to vary the SNR. The measured throughput under different SNR will be used to evaluate the different MIMO antenna design. When testing the coverage improvement, the AWGN interferers are turned off. The downlink signal power is changed to find the power level where a given throughput is achieved. The measured signal power with a dipole for this case will be a measure of coverage improvement.
+
+#### 5.1.2.3 Two-stage method
+
+The spatial AWGN is integrated over the antenna pattern and the resulting noise power is used to generate the noise power for the second stage throughput test. The first stage antenna pattern measurement does not require AWGN. The output power of the channel emulator is set to ensure the power received by the DUT with RF connection is comparable to the power received through the DUT's antenna. The SNR is emulated by setting the power of the AWGN correctly when measuring the throughput for the given MIMO antenna design. When measuring for coverage improvement, the AWGN interference is turned off.
+
+## 5.2 Receiver Performance Metrics
+
+*<Editor: add texts>*
+
+# --- 6 Measurement Methodologies
+
+## 6.1 Fixed Reference Measurement Channels (FRCs)
+
+*<Editor: add texts>*
+
+## 6.2 MIMO Channel Models
+
+The following channel models are used in evaluation of MIMO OTA methodologies. The same models are also potential candidates for final MIMO OTA UE tests (WI).
+
+There are three different clustered delay line (CDL) models, and one simplified (single cluster) model.
+
+The generic models are
+
+- SCME Urban micro-cell,
+- Modified SCME Urban micro-cell,
+- SCME Urban macro-cell, and
+- WINNER II Outdoor-to-indoor.
+
+The single cluster models are based on
+
+- SCME Urban micro-cell and
+- Extended Pedestrian A (EPA)
+
+The uniform models are based on
+
+- Extended Pedestrian A (EPA) and
+- Exponential decay.
+
+The emulated base station antennas may be assumed to be one of the following:
+
+- 1) Vertically polarized elements
+  - a.) with a fixed  $4\lambda$  separation, specified at the center frequency, or
+  - b) are uncorrelated, i.e. to allow the UE to be measured independently from BS effects
+- 2) Dual polarized equal power elements that are uncorrelated with a fixed  $0\lambda$  separation, 45 degrees slanted.
+
+In the following we define the cross polarization power ratio a propagation channel as  $XPR = XPR_V = XPR_H$ , where
+
+$$XPR_V = \frac{S_{VV}}{S_{HV}} \text{ and } XPR_H = \frac{S_{HH}}{S_{VH}}$$
+
+and
+
+- $S_{VV}$  is the coefficient for scattered/reflected power on V-polarization and incident power on V-polarization
+- $S_{VH}$  is the coefficient for scattered/reflected power on V-polarization and incident power on H-polarization
+- $S_{HV}$  is the coefficient for scattered/reflected power on H-polarization and incident power on V-polarization
+- $S_{HH}$  is the coefficient for scattered/reflected power on H-polarization and incident power on H-polarization
+
+Note: for Vertical only measurements, the powers per delay are used without regard to the specified XPR values.
+
+**Table 6.2-1: SCME urban micro-cell channel model**
+
+| SCME Urban micro-cell                               |            |     |     |            |       |       |         |                   |
+|-----------------------------------------------------|------------|-----|-----|------------|-------|-------|---------|-------------------|
+| Cluster #                                           | Delay [ns] |     |     | Power [dB] |       |       | AoD [°] | AoA [°]           |
+| 1                                                   | 0          | 5   | 10  | -3.0       | -5.2  | -7.0  | 6.6     | 0.7               |
+| 2                                                   | 285        | 290 | 295 | -4.3       | -6.5  | -8.3  | 14.1    | -13.2             |
+| 3                                                   | 205        | 210 | 215 | -5.7       | -7.9  | -9.7  | 50.8    | 146.1             |
+| 4                                                   | 660        | 665 | 670 | -7.3       | -9.5  | -11.3 | 38.4    | -30.5             |
+| 5                                                   | 805        | 810 | 815 | -9.0       | -11.2 | -13.0 | 6.7     | -11.4             |
+| 6                                                   | 925        | 930 | 935 | -11.4      | -13.6 | -15.4 | 40.3    | -1.1              |
+| Delay spread [ns]                                   |            |     |     |            |       |       |         | 294               |
+| Cluster AS AoD / AS AoA [°]                         |            |     |     |            |       |       |         | 5 / 35            |
+| Cluster PAS shape                                   |            |     |     |            |       |       |         | Laplacian         |
+| Total AS AoD / AS AoA [°]                           |            |     |     |            |       |       |         | 18.2 / 67.8       |
+| Mobile speed [km/h] / Direction of travel [°]       |            |     |     |            |       |       |         | 3, 30 / 120       |
+| XPR                                                 |            |     |     |            |       |       |         | 9 dB              |
+| NOTE: V & H components based on assumed BS antennas |            |     |     |            |       |       |         |                   |
+| Mid-paths Share Cluster parameter values for:       |            |     |     |            |       |       |         | AoD, AoA, AS, XPR |
+
+The following Modified SCME Urban Micro-cell channel model has the same PDP as the original one, but angle spread is smaller.
+
+**Table 6.2-2: Modified SCME urban micro-cell channel model**
+
+| <b>Modified SCME Urban micro-cell</b>               |                   |          |           |                   |             |             |                |                   |
+|-----------------------------------------------------|-------------------|----------|-----------|-------------------|-------------|-------------|----------------|-------------------|
+| <b>Cluster #</b>                                    | <b>Delay [ns]</b> |          |           | <b>Power [dB]</b> |             |             | <b>AoD [°]</b> | <b>AoA [°]</b>    |
+|                                                     | <b>0</b>          | <b>5</b> | <b>10</b> | <b>-3.0</b>       | <b>-5.2</b> | <b>-7.0</b> |                |                   |
+| 1                                                   |                   |          |           |                   |             |             | 6.6            | -2.3              |
+| 2                                                   | 285               | 290      | 295       | -4.3              | -6.5        | -8.3        | 14.1           | 42.6              |
+| 3                                                   | 205               | 210      | 215       | -5.7              | -7.9        | -9.7        | 50.8           | -49.5             |
+| 4                                                   | 660               | 665      | 670       | -7.3              | -9.5        | -11.3       | 38.4           | 24.7              |
+| 5                                                   | 805               | 810      | 815       | -9.0              | -11.2       | -13.0       | 6.7            | 61.7              |
+| 6                                                   | 925               | 930      | 935       | -11.4             | -13.6       | -15.4       | 40.3           | 10.6              |
+| Delay spread [ns]                                   |                   |          |           |                   |             |             |                | 294               |
+| Cluster AS AoD / AS AoA [°]                         |                   |          |           |                   |             |             |                | 5 / 35            |
+| Cluster PAS shape                                   |                   |          |           |                   |             |             |                | Laplacian         |
+| Total AS AoD / AS AoA [°]                           |                   |          |           |                   |             |             |                | 18.2 / 49.0       |
+| Mobile speed [km/h] / Direction of travel [°]       |                   |          |           |                   |             |             |                | 3, 30 / 120       |
+| XPR                                                 |                   |          |           |                   |             |             |                | 9dB               |
+| NOTE: V & H components based on assumed BS antennas |                   |          |           |                   |             |             |                |                   |
+| Mid-paths Share Cluster parameter values for:       |                   |          |           |                   |             |             |                | AoD, AoA, AS, XPR |
+
+The following SCME Urban Macro-cell is unchanged from the original SCME paper, with added XPR values, Direction of Travel, and Velocity.
+
+**Table 6.2-3: SCME urban macro-cell channel model**
+
+| <b>SCME Urban macro-cell</b>                        |                   |          |           |                   |             |           |                |                   |
+|-----------------------------------------------------|-------------------|----------|-----------|-------------------|-------------|-----------|----------------|-------------------|
+| <b>Cluster #</b>                                    | <b>Delay [ns]</b> |          |           | <b>Power [dB]</b> |             |           | <b>AoD [°]</b> | <b>AoA [°]</b>    |
+|                                                     | <b>0</b>          | <b>5</b> | <b>10</b> | <b>-3</b>         | <b>-5.2</b> | <b>-7</b> |                |                   |
+| 1                                                   |                   |          |           |                   |             |           | 82             | 66                |
+| 2                                                   | 360               | 365      | 370       | -5.2              | -7.4        | -9.2      | 81             | 46                |
+| 3                                                   | 255               | 260      | 265       | -4.7              | -6.9        | -8.7      | 80             | 143               |
+| 4                                                   | 1040              | 1045     | 1050      | -8.2              | -10.4       | -12.2     | 99             | 33                |
+| 5                                                   | 2730              | 2735     | 2740      | -12.1             | -14.3       | -16.1     | 102            | -91               |
+| 6                                                   | 4600              | 4605     | 4610      | -15.5             | -17.7       | -19.5     | 107            | -19               |
+| Delay spread [ns]                                   |                   |          |           |                   |             |           |                | 839.5             |
+| Cluster AS AoD / AS AoA [°]                         |                   |          |           |                   |             |           |                | 2 / 35            |
+| Cluster PAS shape                                   |                   |          |           |                   |             |           |                | Laplacian         |
+| Total AS AoD / AS AoA [°]                           |                   |          |           |                   |             |           |                | 7.8 / 62.6        |
+| Mobile speed [km/h] / Direction of travel [°]       |                   |          |           |                   |             |           |                | 3, 30 / 120       |
+| XPR                                                 |                   |          |           |                   |             |           |                | 9 dB              |
+| NOTE: V & H components based on assumed BS antennas |                   |          |           |                   |             |           |                |                   |
+| Mid-paths Share Cluster parameter values for:       |                   |          |           |                   |             |           |                | AoD, AoA, AS, XPR |
+
+The following Winner II Outdoor-to-Indoor is modified from the original Winner II report, with the following Angle Spread, XPR values, Direction of Travel, and Velocity.
+
+**Table 6.2-4: Modified WINNER II outdoor-to-indoor channel model**
+
+| <b>Modified Winner II Outdoor-to-Indoor</b>         |                   |     |    |                   |       |      |                |                                                     |
+|-----------------------------------------------------|-------------------|-----|----|-------------------|-------|------|----------------|-----------------------------------------------------|
+| <b>Cluster #</b>                                    | <b>Delay [ns]</b> |     |    | <b>Power [dB]</b> |       |      | <b>AoD [°]</b> | <b>AoA [°]</b>                                      |
+|                                                     | 0                 | 5   | 10 | -3                | -5.2  | -7   |                |                                                     |
+| 1                                                   | 0                 | 5   | 10 | -3                | -5.2  | -7   | 0              | 0                                                   |
+| 2                                                   |                   | 0   |    |                   | -8.7  |      | 32             | 101.5                                               |
+| 3                                                   |                   | 5   |    |                   | -3.7  |      | -21            | 66.2                                                |
+| 4                                                   |                   | 10  |    |                   | -11.9 |      | 37             | -118.7                                              |
+| 5                                                   |                   | 35  |    |                   | -16.2 |      | -43            | 138.5                                               |
+| 6                                                   |                   | 35  |    |                   | -6.9  |      | 28             | -90.4                                               |
+| 7                                                   | 65                | 70  | 75 | -3.9              | -6.1  | -7.9 | -49            | 32.7                                                |
+| 8                                                   |                   | 120 |    |                   | -10.3 |      | -34            | 10.5                                                |
+| 9                                                   |                   | 125 |    |                   | -20.7 |      | -49            | 156.6                                               |
+| 10                                                  |                   | 195 |    |                   | -16.0 |      | 43             | 137.7                                               |
+| 11                                                  |                   | 250 |    |                   | -21.0 |      | 49             | -157.7                                              |
+| 12                                                  |                   | 305 |    |                   | -22.9 |      | 51             | -164.7                                              |
+| Delay spread [ns]                                   |                   |     |    |                   |       |      |                | 40.5                                                |
+| Cluster AS AoD / AS AoA [°]                         |                   |     |    |                   |       |      |                | 5 / 25                                              |
+| Cluster PAS shape                                   |                   |     |    |                   |       |      |                | Laplacian                                           |
+| Total AS AoD / AS AoA [°]                           |                   |     |    |                   |       |      |                | 28.6 / 56                                           |
+| Mobile speed [km/h] / Direction of travel [°]       |                   |     |    |                   |       |      |                | 3 / 120                                             |
+| XPR                                                 |                   |     |    |                   |       |      |                | 9dB                                                 |
+| NOTE: V & H components based on assumed BS antennas |                   |     |    |                   |       |      |                |                                                     |
+| Mid-paths Share Cluster parameter values for:       |                   |     |    |                   |       |      |                | AoD, AoA, AS, XPR <sub>V</sub> and XPR <sub>H</sub> |
+
+The following Single Cluster model is based on the SCME Urban Micro-cell model with all AoAs assumed to be zero degrees. XPR values, Direction of Travel, and Velocity were specified. An option allows a cluster angle spread to be specified with  $\sigma_{AS} = 35^\circ$  or with  $\sigma_{AS} = 25^\circ$  to enable a range of spatial correlation for different types of devices.
+
+**Table 6.2-5: Single spatial cluster model with multi-path based on SCME urban micro-cell channel model**
+
+| <b>Single Spatial Cluster Model with Multi-path based on SCME Urban micro-cell</b> |                   |     |     |                   |       |       |                |                   |
+|------------------------------------------------------------------------------------|-------------------|-----|-----|-------------------|-------|-------|----------------|-------------------|
+| <b>Cluster #</b>                                                                   | <b>Delay [ns]</b> |     |     | <b>Power [dB]</b> |       |       | <b>AoD [°]</b> | <b>AoA [°]</b>    |
+|                                                                                    | 0                 | 5   | 10  | -3.0              | -5.2  | -7.0  |                |                   |
+| 1                                                                                  | 0                 | 5   | 10  | -3.0              | -5.2  | -7.0  | 6.6            | 0                 |
+| 2                                                                                  | 285               | 290 | 295 | -4.3              | -6.5  | -8.3  | 14.1           | 0                 |
+| 3                                                                                  | 205               | 210 | 215 | -5.7              | -7.9  | -9.7  | 50.8           | 0                 |
+| 4                                                                                  | 660               | 665 | 670 | -7.3              | -9.5  | -11.3 | 38.4           | 0                 |
+| 5                                                                                  | 805               | 810 | 815 | -9.0              | -11.2 | -13.0 | 6.7            | 0                 |
+| 6                                                                                  | 925               | 930 | 935 | -11.4             | -13.6 | -15.4 | 40.3           | 0                 |
+| Delay spread [ns]                                                                  |                   |     |     |                   |       |       |                | 294               |
+| Cluster AS AoD / AS AoA [°]                                                        |                   |     |     |                   |       |       |                | 5 / 25 or 35      |
+| Cluster PAS shape                                                                  |                   |     |     |                   |       |       |                | Laplacian         |
+| Total AS AoD / AS AoA [°]                                                          |                   |     |     |                   |       |       |                | 18.2 / 25 or 35   |
+| Mobile speed [km/h] / Direction of travel [°]                                      |                   |     |     |                   |       |       |                | 3, 30 / 120       |
+| XPR                                                                                |                   |     |     |                   |       |       |                | 9 dB              |
+| NOTE: V & H components based on assumed BS antennas                                |                   |     |     |                   |       |       |                |                   |
+| Mid-paths Share Cluster parameter values for:                                      |                   |     |     |                   |       |       |                | AoD, AoA, AS, XPR |
+
+For some techniques, which cannot control the channel model a 3D uniform channel model is assumed. For comparison purpose, a 2D uniform channel model is specified as follows for other methods which can control the channel model.
+
+**Table 6.2-6: 3D uniform channel model**
+
+| <b>3D uniform channel model</b> |                   |
+|---------------------------------|-------------------|
+| PDP                             | Exponential decay |
+| PAS                             | 3D uniform        |
+| XPR                             | 0 dB              |
+
+Table 6.2-7: 2D uniform multipath channel model
+
+| 2D Uniform Multipath Model                                                                                                                                  |            |            |         |               |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|---------|---------------|
+| Cluster #                                                                                                                                                   | Delay [ns] | Power [dB] | AoD [°] | AoA [°]       |
+| 1                                                                                                                                                           | 0          | 0.0        | N/A     | 0             |
+| 2                                                                                                                                                           | 30         | -1.0       | N/A     | 0             |
+| 3                                                                                                                                                           | 70         | -2.0       | N/A     | 0             |
+| 4                                                                                                                                                           | 90         | -3.0       | N/A     | 0             |
+| 5                                                                                                                                                           | 110        | -8.0       | N/A     | 0             |
+| 6                                                                                                                                                           | 190        | -17.2      | N/A     | 0             |
+| 7                                                                                                                                                           | 410        | -20.8      | N/A     | 0             |
+| Delay spread [ns]                                                                                                                                           |            |            |         | 45            |
+| Cluster AS AoD / AS AoA [°]                                                                                                                                 |            |            |         | N/A/104       |
+| Cluster PAS shape                                                                                                                                           |            |            |         | Uniform       |
+| Total AS AoD / AS AoA [°]                                                                                                                                   |            |            |         | N/A/104       |
+| XPR<br>NOTE: No depolarization based on XPR<br>Equal power transmitted in V & H, $P_V = 0.5$ , $P_H = 0.5$<br>V & H components based on assumed BS antennas |            |            |         | 0 dB          |
+| Mobile speed [km/h] / Direction of travel [°]                                                                                                               |            |            |         | 3 or 30 / N/A |
+
+For comparison purpose, a single cluster multi-path channel model is specified to compare the test results with the reverberation chamber based method as follows
+
+Table 6.2-8: single cluster multipath channel model
+
+| Single Cluster Multipath Model                                                                                                                              |            |            |         |               |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|---------|---------------|
+| Cluster #                                                                                                                                                   | Delay [ns] | Power [dB] | AoD [°] | AoA [°]       |
+| 1                                                                                                                                                           | 0          | 0.0        | N/A     | 0             |
+| 2                                                                                                                                                           | 30         | -1.0       | N/A     | 0             |
+| 3                                                                                                                                                           | 70         | -2.0       | N/A     | 0             |
+| 4                                                                                                                                                           | 90         | -3.0       | N/A     | 0             |
+| 5                                                                                                                                                           | 110        | -8.0       | N/A     | 0             |
+| 6                                                                                                                                                           | 190        | -17.2      | N/A     | 0             |
+| 7                                                                                                                                                           | 410        | -20.8      | N/A     | 0             |
+| Delay spread [ns]                                                                                                                                           |            |            |         | 45            |
+| Cluster AS AoD / AS AoA [°]                                                                                                                                 |            |            |         | N/A/70        |
+| Cluster PAS shape                                                                                                                                           |            |            |         | Laplacian     |
+| Total AS AoD / AS AoA [°]                                                                                                                                   |            |            |         | N/A/70        |
+| XPR<br>NOTE: No depolarization based on XPR<br>Equal power transmitted in V & H, $P_V = 0.5$ , $P_H = 0.5$<br>V & H components based on assumed BS antennas |            |            |         | 0 dB          |
+| Mobile speed [km/h] / Direction of travel [°]                                                                                                               |            |            |         | 3 or 30 / 120 |
+
+The parameters of the channel models are the expected parameters for the MIMO OTA channel models. However, the final channel model achieved for different methods could be a combined effect of the chamber and the channel emulator.
+
+How the Rayleigh fading is implemented in the channel emulator or in the MIMO OTA test for different test methods is implementation specific and should be appropriate as long as the statistics of the generated Rayleigh fading are within standard requirement on Rayleigh fading statistics.
+
+## 6.3 Downlink Measurement Methodologies
+
+The methodologies defined in this subclause are candidate methodologies being studied for the purpose of defining procedures for conformance testing of over the air performance.
+
+### 6.3.1 Methodologies based on Anechoic RF Chamber
+
+An OTA method based on the use of an Anechoic RF Chamber is described consisting of a number of test antenna probes located in the chamber transmitting signals with temporal and spatial characteristics for testing multiple antenna devices.
+
+This section describes the methodologies based on Anechoic RF Chamber, where a number of test antennas are located in different positions of the chamber, and the device under test (DUT) is located at center position. The DUT is tested over the air without RF cables.
+
+#### 6.3.1.1 Candidate Solution 1
+
+An Anechoic Chamber technique is defined, consisting of a number of source elements at one end or surrounding the DUT to create a realistic geometric based spatio-temporal radio channel for testing MIMO performance. The latter implementation is illustrated in Figure 6.3.1.1-1.
+
+By utilizing specific geometries of the test probes in the chamber, a range of possible channels are emulated. The exact number and positioning of the source antenna probes will be fixed in a final design; however they may be optimized for the best performance when the OTA channel models are defined. In other words, depending on the types of channel models required and the range of parameters needed for testing, the number of probes may be optimized to produce the best performance with the fewest number of probes. For example, based on the range of channels defined by the SCM, SCME, Winner I & II channel models, the optimized number of probes may vary from 6 to 8 for a given polarization. In general, the most flexible configurations require the higher number of probes.
+
+Azimuth spread is created by energizing sets of probes separated in azimuth with signals that will combine over the air at a specific delay to emulate a path or cluster. Elevation spread may be created by installing probes at different elevations, however doing this tends to constrain their flexibility.
+
+The components of the solution include:
+
+- Anechoic Chamber
+- System Simulator (SS)
+- N channel RF emulator, with OTA Channel Generation Features
+- N antenna elements configured with V, H or co-located V&H or slant X polarizations
+- K azimuthally separated antenna positions with predefined angles at radius R
+- Channel Model definition for each test case
+
+![Figure 6.3.1.1-1: N-Element Anechoic Chamber Approach. A 3D perspective view of an anechoic chamber. In the center, a Device Under Test (DUT) is represented by a blue cylinder. Six vertical lines, each marked with an 'X' at the top, represent antenna probes arranged around the DUT. The chamber walls are lined with curved, wave-like structures representing electromagnetic wave absorbers.](78ebfe3116918cd317b54c861da8d8d2_img.jpg)
+
+Figure 6.3.1.1-1: N-Element Anechoic Chamber Approach. A 3D perspective view of an anechoic chamber. In the center, a Device Under Test (DUT) is represented by a blue cylinder. Six vertical lines, each marked with an 'X' at the top, represent antenna probes arranged around the DUT. The chamber walls are lined with curved, wave-like structures representing electromagnetic wave absorbers.
+
+Figure 6.3.1.1-1: N-Element Anechoic Chamber Approach (Absorbing tiles and cabling not shown)
+
+![Figure 6.3.1.1-2: OTA System Level Block Diagram. A block diagram showing the signal flow for OTA testing. On the left, a block labeled 'SS' (Signal Source) has an output labeled 'M' pointing to a block labeled 'MxN MIMO Channel Emulator'. The emulator has an output labeled 'N' pointing to a block labeled 'Anechoic Chamber'. Inside the Anechoic Chamber, there are three '+' symbols representing antenna probes. A 'Return Path' is indicated by a line with an arrow pointing from the Anechoic Chamber back to the SS block. Between the MIMO Channel Emulator and the Anechoic Chamber, there is a vertical stack of three '2's with a vertical ellipsis between them, indicating multiple signal branches.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg)
+
+Figure 6.3.1.1-2: OTA System Level Block Diagram. A block diagram showing the signal flow for OTA testing. On the left, a block labeled 'SS' (Signal Source) has an output labeled 'M' pointing to a block labeled 'MxN MIMO Channel Emulator'. The emulator has an output labeled 'N' pointing to a block labeled 'Anechoic Chamber'. Inside the Anechoic Chamber, there are three '+' symbols representing antenna probes. A 'Return Path' is indicated by a line with an arrow pointing from the Anechoic Chamber back to the SS block. Between the MIMO Channel Emulator and the Anechoic Chamber, there is a vertical stack of three '2's with a vertical ellipsis between them, indicating multiple signal branches.
+
+Figure 6.3.1.1-2: OTA System Level Block Diagram
+
+A system level block diagram is shown in Figure 6.3.1.1-2, which includes the SS to generate the M branch MIMO signal, and an RF Channel Emulator with an OTA Channel Generation Feature to properly correlate, fade, scale, delay, and distribute the signal to each test probe in the chamber.
+
+For research purposes, a range of possible channel models and parameterizations will be used to specify the most generic and versatile antenna test probe configuration. For performance and conformance testing, the channel model is expected to be limited in scope or simplified, which may allow an optimized design to reduce the number of test probes required. Thus the number of test probes will be selected to best meet the requirements of the test so that the most efficient and economical design can be achieved.
+
+##### 6.3.1.1.1 Concept and Configuration
+
+###### 6.3.1.1.1.1 Emulating Spatial Channels
+
+Spatial channel models, including SCM, SCME, Winner I & II, and ITU-A, were developed from measured data, and attempt to preserve the measured behaviour of the channel at the path (cluster) level, including spatial, temporal, polarization, and delay characteristics. Reference [3] described a technique for reproducing the spatial characteristics of a narrow angle spread signal with a reduced number of antenna probes. This technique uses pre-faded signals at each
+
+probe wherein the power-adjusted signals from the multiple probes, i.e. typically 2-4 or more, are combined over the air to produce an accurate narrow angle spread representation of the signal for each delay. This technique is able to maintain its close match to an ideal narrow angle spread signal even for severe antenna variations.
+
+The spacing of the antenna probes in the chamber are constrained by the range of angle spreads being emulated, and therefore the channel model is a key determining factor in optimizing an OTA chamber design. For the angle spreads defined by SCM, SCME, Winner I & II, and the ITU-A channel models, the optimum number of probes may vary from 6 to 8 for a given polarization, depending on the device type, and for large devices the number of probes may increase. In general, the most flexible configurations will tend to require the higher number of probes. Once the design of parameters of the system are decided, it is expected that the number of probes will be fixed to a value that works for all channel models and devices being simulated. Figure 6.3.1.1.1.1-1 illustrates some practical antenna probe configurations to support devices such as handsets and laptops. The single cluster approach can be performed using probes distributed over a portion of a circle or in a full ring-like distribution.
+
+![Figure 6.3.1.1.1.1-1: Some Practical Antenna Probe Configurations, (shown with dual polarization). The diagram shows three configurations of antenna probes around a central Device Under Test (DuT). 1. '4 Probe Single Cluster': Four probes are arranged in a semi-circle on the left side of the DuT. 2. '8 Probe Single Cluster': Eight probes are arranged in a semi-circle on the left side of the DuT. 3. '8 Probe Circular or 8 Probe Single Cluster': Eight probes are arranged in a full circle around the DuT. Each probe is represented by a cross symbol, indicating dual polarization.](3da1a07cb87051bf616c9876db958cf0_img.jpg)
+
+Figure 6.3.1.1.1.1-1: Some Practical Antenna Probe Configurations, (shown with dual polarization). The diagram shows three configurations of antenna probes around a central Device Under Test (DuT). 1. '4 Probe Single Cluster': Four probes are arranged in a semi-circle on the left side of the DuT. 2. '8 Probe Single Cluster': Eight probes are arranged in a semi-circle on the left side of the DuT. 3. '8 Probe Circular or 8 Probe Single Cluster': Eight probes are arranged in a full circle around the DuT. Each probe is represented by a cross symbol, indicating dual polarization.
+
+**Figure 6.3.1.1.1.1-1: Some Practical Antenna Probe Configurations, (shown with dual polarization)**
+
+The probe separation angle,  $\phi$  used in the Chamber design, shown in Figure 6.3.1.1.1.1-1, will be defined in conjunction with the channel models as described below. In general, the angles will not be exact even integer fractions of pi, to avoid symmetries. i.e. exact symmetry will produce convergence problems due to correlated Doppler, e.g.  $\cos(\alpha) = -\cos(\alpha + \pi)$ .
+
+###### 6.3.1.1.1.2 Joint Selection of a Channel Model and a Chamber Design
+
+Since link modelling is usually associated with a single “drop” or single “channel realization” from the channel model, a few specific channel realizations will likely be specified and standardized for evaluation purposes. From a testing standpoint, only a few channel realizations will be measured in an OTA performance/conformance system, and it would be useful to align the channel model clusters with the probe locations in an optimized chamber design. However, there is enough flexibility inherent in these probe configurations to emulate clusters from arbitrary angles if desired.
+
+Specifically, since the chamber layout has probes at specific angles, and since most spatial channel models draw channel AoAs randomly from specified distributions, it is reasonable that specific AoAs are chosen to align with the chamber layout for these few test channels.
+
+For research purposes, a more generic OTA chamber design is possible, but generally at the cost of having the maximum number of probes. Also, there is a trade-off in modelling signals with arbitrary AoA while controlling the signals Angle Spread at the same time. By selecting specific AoAs within a valid channel realization, a more precise AS can be obtained. Thus performance of the OTA design is closely tied to the channel modelling assumptions used, and can be specified more completely when the channel model and its associated parameters are specified.
+
+##### 6.3.1.1.2 Test Conditions
+
+For performance and conformance testing purposes, only a small number of channel realizations is practical due to the nature of the OTA measurements. Based on this, it is reasonable to define a range of conditions for testing that can be represented in 2-3 channel realizations. It is anticipated that these channel realizations would represent a Low, Medium, and High correlation cases, which generally align to the ability of the channel to support MIMO operation.
+
+These channels may also be used to optimize the design and layout of the chamber to reduce the number of probes and achieve the most efficient and cost effective design.
+
+#### 6.3.1.2 Candidate Solution 2
+
+The MIMO OTA test setup is composed of a number of OTA chamber antennas, a multidimensional fading emulator, an anechoic chamber, communication tester / BS emulator and a device under test (DUT). The following figure depicts an example of the OTA concept. The purpose of the figure is not to restrict the implementation, but rather to clarify the general idea of the MIMO OTA concept. For simplicity, uplink cabling is not drawn here.
+
+![Diagram of a MIMO/Multiantenna OTA test setup. A 'Communication Tester / BS Emulator' is connected to a 'Fading emulator'. The 'Fading emulator' is connected to multiple 'OTA chamber antennas' inside an 'Anechoic chamber'. The 'DUT' is located in the center of the chamber, receiving signals from the antennas. The uplink signal path is omitted.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg)
+
+The diagram illustrates the MIMO/Multiantenna OTA test setup. On the left, a 'Communication Tester / BS Emulator' is connected to a 'Fading emulator'. The 'Fading emulator' is connected to a series of 'OTA chamber antennas' located inside an 'Anechoic chamber'. The 'DUT' (Device Under Test) is positioned in the center of the chamber, receiving signals from the antennas. The uplink signal path is omitted for simplicity.
+
+Diagram of a MIMO/Multiantenna OTA test setup. A 'Communication Tester / BS Emulator' is connected to a 'Fading emulator'. The 'Fading emulator' is connected to multiple 'OTA chamber antennas' inside an 'Anechoic chamber'. The 'DUT' is located in the center of the chamber, receiving signals from the antennas. The uplink signal path is omitted.
+
+**Figure 6.3.1.2-1: Example of MIMO/Multiantenna OTA test setup (Uplink signal path omitted in the figure)**
+
+The DUT is located at center of the anechoic chamber. The idea of locating DUT into center provides a possibility to create a radio channel environment where the signal can arrive from various possible directions simultaneously to the DUT. This is the key aspect of the wideband MIMO radio channel models implemented today.
+
+The proposed test setup is composed of a transmitter, a multidimensional radio channel emulator, an anechoic chamber equipped with OTA antennas and a DUT with multiple antennas. The crucial challenge is to generate realistic angular and polarization behavior within the anechoic chamber. The family of geometry-based stochastic channel models (GSCM) is well suitable for MIMO OTA testing. The GSCM include 3GPP SCM, SCME, WINNER and IMT-Advanced channel models. This angular and polarization behavior creates appropriate correlation at the DUT antennas. The correlation is defined implicitly via the per-path angle of arrival and real antennas. Correlation matrix based model is not suitable for this, because it includes the antenna information in the model itself.
+
+Geometry based channel modeling methodology models BS and UE antenna arrays and the propagation between them (including angular power spectra). The parameters that are included are Doppler, Angle of Arrival, Angle of Departure, delay and polarization. The parameters are based mainly on measurements. The measurements define certain statistics and radio channel realizations are then created by these statistical properties.
+
+The geometrical models are divided in to three parts:
+
+- 1) BS antenna arrangement and the angular power spectrum as well as the AoD from the BS are modeled in the channel emulator.
+- 2) AoA is created by dividing the appropriate clusters based on their original AoA to corresponding OTA antennas. The user terminal is not physically in a motion, thus the fading and Doppler spectrum are built in the channel model.
+
+- 3) The angular power spectrum at DUT is created by radiating the signal from multiple OTA antennas.
+
+UE (DUT) antenna characteristics are assumed unknown. In other words we do not use this information in the OTA modeling.
+
+##### 6.3.1.2.1 Concept and Configuration
+
+The idea of the MIMO OTA modelling is that the geometric channel models are mapped into the fading emulator. The mapping process covers all the required mathematics when converting the traditional geometric channel model to fading emulator tap coefficients as well as the calibration. The modeling process is shown in Figure 6.3.1.2.1-1.
+
+![Figure 6.3.1.2.1-1: Modelling process flowchart. A box labeled 'Public Matlab implementation' contains 'Geometric channel model' and 'SCM/SCME/WINNER/IMT-Advanced'. An arrow points from this box to 'OTA modelling tool (mapping SW)'. Another arrow points from 'OTA modelling tool (mapping SW)' to 'Fading emulator'. A downward arrow points from 'Fading emulator' to a circle labeled 'OTA chamber' which contains a small antenna symbol.](90ddf538ef276510e2b631f7b96654e6_img.jpg)
+
+```
+
+graph LR
+    subgraph A [ ]
+        direction TB
+        A1[Public Matlab implementation]
+        A2[Geometric channel model  
+SCM/SCME/WINNER/  
+IMT-Advanced]
+    end
+    A --> B[OTA modelling tool  
+(mapping SW)]
+    B --> C[Fading emulator]
+    C --> D((OTA chamber  
+H))
+    style A fill:#e1e1e1,stroke:none
+    style D fill:none,stroke:none
+    style A2 fill:none,stroke:none
+    style A1 fill:none,stroke:none
+    style D stroke:none
+    style C fill:none,stroke:none
+    style B fill:none,stroke:none
+    style A1 fill:none,stroke:none
+    style A2 fill:none,stroke:none
+    style D fill:none,stroke:none
+    style C fill:none,stroke:none
+    style B fill:none,stroke:none
+  
+```
+
+Figure 6.3.1.2.1-1: Modelling process flowchart. A box labeled 'Public Matlab implementation' contains 'Geometric channel model' and 'SCM/SCME/WINNER/IMT-Advanced'. An arrow points from this box to 'OTA modelling tool (mapping SW)'. Another arrow points from 'OTA modelling tool (mapping SW)' to 'Fading emulator'. A downward arrow points from 'Fading emulator' to a circle labeled 'OTA chamber' which contains a small antenna symbol.
+
+Figure 6.3.1.2.1-1: Modelling process
+
+The setup of OTA chamber antennas with eight antenna elements is depicted in Figure 6.3.1.2.1-2. DUT is at center and the antennas are on a circle around DUT with uniform spacing (e.g.  $45^\circ$  with 8 elements). Let us denote directions of  $K$  OTA antennas with  $\theta_k, k = 1, \dots, K$ , and antenna spacing in the angle domain with  $\Delta\theta$ . Each antenna is connected to a single fading emulator output port. If single antenna BS is considered the fading emulator configuration is 1x8 SIMO, with two BS antennas 2x8 MIMO etc. If dual polarized OTA antennas are used like in Figure 6.3.1.2.1-3 the fading emulator configuration will be with 1 BS antenna 1x16 SIMO, with two BS antennas 2x16 MIMO etc. In the figure for example antenna  $A_{1V}$  denotes the first OTA antenna position and vertically (V) polarized element,  $A_{8H}$  denotes the eight OTA antenna position and horizontally (H) polarized element, etc.
+
+![Figure 6.3.1.2.1-2: OTA chamber antenna setup with eight uniformly spaced chamber antennas. A circle represents the OTA chamber with eight antenna elements at positions theta_1=0, theta_2=45, theta_3=90, theta_4=135, theta_5=180, theta_6=225, theta_7=270, and theta_8=315 degrees. The angle between adjacent antennas is labeled Delta theta.](04dc3838022e96d8d5548bb1b777b38c_img.jpg)
+
+Figure 6.3.1.2.1-2: OTA chamber antenna setup with eight uniformly spaced chamber antennas. A circle represents the OTA chamber with eight antenna elements at positions theta\_1=0, theta\_2=45, theta\_3=90, theta\_4=135, theta\_5=180, theta\_6=225, theta\_7=270, and theta\_8=315 degrees. The angle between adjacent antennas is labeled Delta theta.
+
+Figure 6.3.1.2.1-2: OTA chamber antenna setup with eight uniformly spaced chamber antennas
+
+![Diagram of an OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas. The antennas are arranged in a circle around a central point. Each antenna is labeled with a subscript (1-8) and a polarization (H for horizontal, V for vertical). The angle between adjacent antennas is labeled Δθ. The V-polarized elements are shown as blue crosses, and the H-polarized elements are shown as red crosses.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+The diagram illustrates an OTA chamber antenna setup. A central point is surrounded by a circle of eight antennas, labeled A<sub>1</sub> through A<sub>8</sub>. Each antenna is dual-polarized, with a horizontal (H) element shown as a red cross and a vertical (V) element shown as a blue cross. The antennas are uniformly spaced at an angle Δθ from each other. The V-polarized elements are actually orthogonal to the paper (azimuth plane).
+
+Diagram of an OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas. The antennas are arranged in a circle around a central point. Each antenna is labeled with a subscript (1-8) and a polarization (H for horizontal, V for vertical). The angle between adjacent antennas is labeled Δθ. The V-polarized elements are shown as blue crosses, and the H-polarized elements are shown as red crosses.
+
+**Figure 6.3.1.2.1-3: OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas. In the drawing the V-polarized elements are actually orthogonal to the paper (azimuth plane)**
+
+###### 6.3.1.2.1A Scalability of the methodology
+
+The number of antennas is scalable. In theory, there is no upper limit and the lower limit is one. The required number of channels depends on three main aspects: channel model, DUT size, and polarization. The key question is how accurately the channel model is emulated. Based on the quiet zone discussion, it was proposed to use 8 antennas in the case of single polarization and 16 antennas in the case of dual polarization. However, for single cluster case, less antennas may be enough. On the other hand, if elevation is needed, the antenna number will be higher. Additionally, the antenna positions can be adjusted to optimize the accuracy with limited number of antennas.
+
+Other aspect is the channel model. Most of the geometry-based stochastic channel models (GSCMs) are two-dimensional, i.e. azimuth plane only, but the proposed MIMO OTA concept is not limited into azimuth plane. It can also be extended to elevation plane, when we talk about 3D MIMO OTA. However, the 3D MIMO OTA is rather complex and it does not provide very much additional information about the DUT. Therefore, 3D MIMO OTA can be considered as one future development, but it is not the recommended solution in the beginning of MIMO OTA testing.
+
+Downscaling of the proposed method is more attractive due to the possibility to save the cost of the test system. Full SCME requires at least 8 probe antennas, but single cluster SCME can be implemented with lower number of antennas. The difference between full SCME and Single Cluster model is depicted in Figure 6.3.1.2.1A-1. Basically the only difference is that the mean Angle-of-Arrival (AoA) of each cluster is turned to the same direction. Obviously, one AoA requires lower number of antennas than multiple AoAs especially when angular spread is narrow, e.g., 35 degrees. The number of fading channels is the same as the number of antennas. Therefore, single cluster SCME would require less fading channels as well.
+
+![Figure 6.3.1.2.1A-1: Full SCME vs. Single Cluster model. The diagram is divided into two parts, (a) and (b). Part (a) shows a 'Full SCME' model where a central 'DUT' (Device Under Test) is surrounded by multiple clusters of signal paths. Each cluster is represented by a group of lines radiating from the DUT to a specific area, with a corresponding 'PAS' (Power Angular Spectrum) graph showing multiple peaks. Part (b) shows a 'Single Cluster' model where the 'DUT' is surrounded by a single cluster of signal paths, with a corresponding 'PAS' graph showing a single peak.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+Figure 6.3.1.2.1A-1: Full SCME vs. Single Cluster model. The diagram is divided into two parts, (a) and (b). Part (a) shows a 'Full SCME' model where a central 'DUT' (Device Under Test) is surrounded by multiple clusters of signal paths. Each cluster is represented by a group of lines radiating from the DUT to a specific area, with a corresponding 'PAS' (Power Angular Spectrum) graph showing multiple peaks. Part (b) shows a 'Single Cluster' model where the 'DUT' is surrounded by a single cluster of signal paths, with a corresponding 'PAS' graph showing a single peak.
+
+Figure 6.3.1.2.1A-1: Full SCME vs. Single Cluster model.
+
+##### 6.3.1.2.2 Test Conditions
+
+This candidate solution supports testing of different figure of merits. It is also applicable for any 3GPP Release, and even for other standards. It supports different channel models from SCM to IMT-Advanced. Due to its generality, it does not restrict the test conditions. However, for simplicity, it is good to start from downlink throughput testing.
+
+The downlink throughput testing can be done e.g. in following manner.
+
+BS transmits signal through a radio channel emulator. This signal is routed to several antennas in anechoic chamber. The DUT is placed at center of the chamber and the performance is measured from the DUT.
+
+- OTA antennas are located along a circle around the DUT.
+- The circular geometry is needed because we need signal from many directions at the same time (requirement from the channel models)
+
+The test steps can be, e.g., according to [3] or as follows:
+
+- 1) Calibrate the full system with a test signal.
+- 2) Set the first test case (e.g. channel model) to the fading emulator.
+- 3) Generate test signal by the communication tester / BS emulator.
+- 4) Measure the DUT performance (downlink throughput).
+- 5) If the performance exceeds the specified limit, the DUT passes the test case.
+- 6) If all test cases done, go to step 7. Otherwise, set the next test case (e.g. channel model) to the fading emulator and go back to step 3.
+- 7) If DUT passed all the test cases, the DUT passes the full MIMO OTA test.
+- 8) If DUT failed in at least one test case, the DUT failed the full MIMO OTA test.
+
+#### 6.3.1.3 Candidate Solution 3
+
+The principle of two-stage MIMO OTA method is based on the assumption that the far-field antenna radiation pattern will contain all the necessary information for evaluation the antenna's performance like radiation power, efficiency and correlation and that with channel model approaches, the influence of antenna radiation pattern can be correctly incorporated into the channel model. Thus the method will first measure the MIMO antenna patterns and then incorporate the measurement antenna patterns with chosen MIMO OTA channel models for real-time emulation. In order to accurately measure the antenna pattern of the intact device, the chipset needs to support amplitude and relative phase measurements of the antennas. If the EUT has dynamic antenna tuning elements, detailed information on the implementation is required to understand the consequences for the pattern measurement. The BTS and DUT can then be connected to the real-time channel emulator through the standard temporary antenna connectors to do the test on throughput, etc., to test how the MIMO antennas will influence the performance.
+
+It should be noted that should this methodology be chosen for conformance testing, the method for antenna gain and phase measurement would require to be standardized. The details for proposed antenna gain and phase measurements are FFS. Further details will be provided before the RAN4 evaluation of this methodology can progress.
+
+##### 6.3.1.3.1 Concept and Configuration
+
+The assumption of the two-stage MIMO OTA method is that the measured far field antenna pattern of the multiple antennas can fully capture the mutual coupling of the multiple antenna arrays and their influence. Thus to do the two-stage MIMO OTA test, the antenna patterns of the antenna array needs to be measured accurately in the first stage. In order to accurately measure the antenna pattern of the intact device, the chipset needs to support amplitude and relative phase measurements of the antennas.
+
+Stage 1: Test multiple antennas system in a traditional anechoic chamber. The chamber for antenna pattern measurement is set up as described in Annex A.2 in [4], where the DUT is put into a chamber and each antenna element's far zone pattern is measured. Section B.4.3 gives description on how to measure each antenna element's pattern using non-intrusive method. The influence of human body loss can be measured by attaching the DUT to a SAM head and or hand when doing the antenna pattern measurements. The DUT is placed against a SAM phantom, and the characteristics of the SAM phantom are specified in Annex A.1 of [4]. The chamber is equipped with a positioner, which makes it possible to perform full 3-D far zone pattern measurements for both Tx and Rx radiated performance. The measurement antenna should be able to measure two orthogonal polarizations (typically linear theta ( $\theta$ ) and phi ( $\phi$ ) polarizations as shown in Figure 6.3.1.3.1-1).
+
+![Diagram of the coordinate system used in the measurements. A DUT (Device Under Test) is shown on the left, mounted on a stand. A probe antenna is shown on the right, mounted on a stand. The coordinate system is defined by the theta (θ) and phi (φ) angles. The theta angle is measured from the vertical axis (z-axis) down towards the horizontal plane. The phi angle is measured in the horizontal plane, starting from the vertical axis and rotating counter-clockwise. The DUT is positioned such that its antenna is at the center of the coordinate system, and the probe antenna is positioned to measure the radiation pattern.](14bbaf9e8820aa362b68a5bc8d11a4c2_img.jpg)
+
+Diagram of the coordinate system used in the measurements. A DUT (Device Under Test) is shown on the left, mounted on a stand. A probe antenna is shown on the right, mounted on a stand. The coordinate system is defined by the theta (θ) and phi (φ) angles. The theta angle is measured from the vertical axis (z-axis) down towards the horizontal plane. The phi angle is measured in the horizontal plane, starting from the vertical axis and rotating counter-clockwise. The DUT is positioned such that its antenna is at the center of the coordinate system, and the probe antenna is positioned to measure the radiation pattern.
+
+Figure 6.3.1.3.1-1: The coordinate system used in the measurements
+
+Stage 2: Combine the antenna patterns measured in stage 1 into MIMO channel model, emulate the MIMO channel model with the measured antenna patterns incorporated in the commercial channel emulator and perform the OTA test in conducted approach.
+
+The MIMO OTA method based on the above mentioned two-stage method is illustrated in Figure 6.3.1.3.1-2. The integrated channel model with both MIMO antenna effect and the multipath channel effect can be emulated with a commercial MIMO channel emulator. The BS emulator is connected to the MIMO channel emulator and then to the MIMO device's temporary antenna ports via approved RF cables. These ports are the standard ones provided for conducted conformance tests. By controlling the power settings of the channel emulator and also the integrated channel model, the end-to-end throughput with the MIMO antenna radiation influence can be measured.
+
+There are two different approaches to combine the antenna patterns with MIMO channel model.
+
+- a) Apply antenna patterns to Ray-based channel models. Ray-based models are capable to support arbitrary antenna patterns under predefined channel modes in a natural way as described above. If Ray-based model like SCM model is specified to be used for MIMO OTA test, then the channel emulator needs to be able to support SCM channel model emulation and support loading measured antenna patterns.
+- b) Apply antenna patterns to correlation-based channel models. MIMO channel model. With a correlation matrix calculation method for arbitrary antenna patterns under multipath channel conditions, the correlation matrix and the antenna imbalance can be calculated and then emulated by the channel emulator.
+- c) This method can be used to measure the following figure of merit:
+  - 1) Throughput
+  - 2) TRP and TRS
+  - 3) CQI, BLER
+  - 4) Antenna efficiency and MEG
+  - 5) Antenna correlation, MIMO channel capacity.
+
+The coupling between the UE antenna and internal spurious emission of the UE might be characterized during the antenna pattern measurement stage inside the chamber by lowering down the signal power and is for further research.
+
+![Figure 6.3.1.3.1-2: Proposed two-stage test methodology for MIMO OTA test. The diagram illustrates two stages of testing. Stage 1 (OTA) shows a BS Emulator connected to a Test Chamber containing a Reference Antenna and a MIMO DUT. The Reference Antenna is connected to the BS Emulator, and the MIMO DUT is connected to the BS Emulator via RF cables. The MIMO DUT is also connected to a box labeled 'Antenna Patterns'. Stage 2 (Conducted) shows a Channel Emulator connected to a BS Emulator, which is connected to a MIMO DUT. The MIMO DUT is connected to a box labeled 'BER, FER, H, R'. A red dashed line connects the 'Antenna Patterns' box from Stage 1 to the Channel Emulator in Stage 2.](9b686adccf125267a013fa25721231a3_img.jpg)
+
+Figure 6.3.1.3.1-2: Proposed two-stage test methodology for MIMO OTA test. The diagram illustrates two stages of testing. Stage 1 (OTA) shows a BS Emulator connected to a Test Chamber containing a Reference Antenna and a MIMO DUT. The Reference Antenna is connected to the BS Emulator, and the MIMO DUT is connected to the BS Emulator via RF cables. The MIMO DUT is also connected to a box labeled 'Antenna Patterns'. Stage 2 (Conducted) shows a Channel Emulator connected to a BS Emulator, which is connected to a MIMO DUT. The MIMO DUT is connected to a box labeled 'BER, FER, H, R'. A red dashed line connects the 'Antenna Patterns' box from Stage 1 to the Channel Emulator in Stage 2.
+
+**Figure 6.3.1.3.1-2: Proposed two-stage test methodology for MIMO OTA test**
+
+##### 6.3.1.3.2 Test Conditions
+
+This candidate solution supports testing of different figure of merits. It is also applicable for any 3GPP Release, and even for other standards.
+
+This method can reuse existing SISO OTA anechoic chambers to make the antenna pattern measurements; the channel emulator number is required to match the number of device receiver inputs regardless of the complexity of the chosen channel model, the method is consequently easily scalable to higher order MIMO due to the reduced number of instruments required; the channel models are highly accurate due to being implemented electronically and are also fully
+
+flexible and can be altered to suit any desired operating conditions such as indoor-outdoor, high or low Doppler spread, high or low delay spread, beam width, in 2D or full 3D etc.
+
+This method requires the chipset in DUT to support amplitude and relative phase measurements of the antennas, and it cannot directly measure self-desensitization since the antenna pattern measurement does not take account of possible signal leakage from the device transmit antennas into the receive antennas.
+
+The detailed test procedure can be found in Annex B.
+
+#### 6.3.1.4 Candidate Solution 4
+
+In this method an assessment of the antenna's performance in MIMO or Diversity operation is performed. Several simplifications are used in order to optimise the testing.
+
+A test of the UE in an anechoic environment with the help of a base station emulator is proposed, with a limited number of faded channels and transmitting antennas, and in a simple geometrical set-up.
+
+The underlying principle is to decompose the task for evaluating MIMO performance. Since in the conformance test many properties of the DUT are already tested in a conducted environment, the OTA test only has to add information not achievable by a cabled set-up.
+
+For that reason it then is sufficient to define some abstract channel environment during the test which does not need to be very close to reality. Abstraction on the environment makes it easier to interpret the obtained results.
+
+The channel information available in the UE can be used to deliver a quick answer to the test system about the current receive quality. Such a measurement is much faster than the evaluation of a throughput figure, but it is nevertheless closely related to it. If necessary, an explicit scaling from one quantity onto the other one can be made.
+
+##### 6.3.1.4.1 Concept and Configuration
+
+The test set-up uses an anechoic chamber. In case of an RX diversity measurement the signal from the base station emulator is routed via a two-channel fading to two antennas in the chamber. For an RX MIMO measurement, the two signals from the base station emulator can undergo a 2x2 channel fading simulation before reaching the antennas in the chamber, or can be routed directly to the probe antennas with some chosen polarization.
+
+Figure 6.3.1.4.1-1 is a sketch of the chamber set-up. For obtaining various angles of arrival (AoA) at the EUT, two antennas A1 and A2 can be rotated in a vertical plane and can be put to angles  $\theta_1$  and  $\theta_2$ . The UE is placed on a turntable rotating around the vertical axis by some angle  $\phi$ . In addition, the UE may be tilted by some additional rotation around the horizontal axis, not shown in the figure. By this arrangement the two antennas A1 and A2 can send the signals from the base station emulator to any position on the unit sphere around the UE, thus creating arbitrary AoA.
+
+As an alternative to moving the antennas by mechanically rotating them it is possible to arrange the antennas in a horizontal plane and to move one antenna with respect to the other in order to vary the angle difference between the two. In that case the positioner rotating the UE will be designed in a more complex way.
+
+Typically, the antennas are dual-polarised ones. In the usual configuration each antenna is sending its signal in one polarization only. Tests are made for the various combinations of antenna polarizations in order to generate either co-polarized or cross-polarized signals. As a special case it is also possible to test with one antenna where each polarization is transmitting one MIMO data stream. This will lead to identical AoAs for the two data streams.
+
+If one wants to extend this method to 3D AoA, a third antenna outside the plane can be used.
+
+The figure does not show an additional antenna used for the uplink communication. This antenna may be placed in the vicinity of the UE, for example in the  $\phi$  positioner. It is common practise to use circularly polarized antennas for this purpose, and to use a limiting amplifier in the path towards the BSE in order to get a good and constant UL level.
+
+![Diagram of the 2 Channel Method antenna arrangement in an anechoic chamber. A central Device Under Test (DUT) is shown with two antennas, A1 and A2, positioned above it. Red curved arrows indicate the rotation angles: theta 1 for antenna A1, theta 2 for antenna A2, and phi for the DUT itself. The chamber walls are lined with blue triangular wave absorbers.](4aa9c7965776f4f4b8eba638b2c53369_img.jpg)
+
+Diagram of the 2 Channel Method antenna arrangement in an anechoic chamber. A central Device Under Test (DUT) is shown with two antennas, A1 and A2, positioned above it. Red curved arrows indicate the rotation angles: theta 1 for antenna A1, theta 2 for antenna A2, and phi for the DUT itself. The chamber walls are lined with blue triangular wave absorbers.
+
+**Figure 6.3.1.4.1-1: 2 Channel Method, antenna arrangement in anechoic chamber**
+
+A test point is described by:
+
+- 1) Signal from BSE, e.g. frequency, MCS, data rate, MIMO mode, ...
+- 2) Fading characteristics (if applicable) and antenna polarisations
+- 3) Antenna positions
+- 4) UE position elevation, azimuth
+
+The detailed settings for the various parameters describing a test point are for further study.
+
+The measurement then uses the quantities CQI, RI and PMI for a quick evaluation of the channel characteristics for each given test point. More precisely, the DL power will be changed until a change in the returned channel information is observed.
+
+In case the required figure of merit is some other quantity such as throughput, some mapping from the channel information onto the figure of merit can be made. This mapping of course depends on the signal settings on the BSE and possibly on other parameters. The mapping can be derived in a series of measurements where changes to the channel parameters lead to different channel information values and to different corresponding values of the figure of merit. It is also possible but more time-consuming to measure the figure of merit for each test point.
+
+The OTA performance can better be described by taking statistical evaluations into account. If, for example, for each test point a relative throughput value is obtained as function of subcarrier power, one can plot the results for different points in a histogram and to obtain some CCDF indicating the conditions for getting at least a given TP value.
+
+#### 6.3.1.5 Candidate Solution 5
+
+The RF-controlled spatial fading emulator can directly reproduce a multipath radio propagation environment by radio waves emitted from antenna-probe units arranged around a handset tested. Moreover, the emulator has an advantage of measuring radiation characteristics of a handset antenna for the present OTA testing in 3GPP as well as the multipath testing because of its RF operation [6].
+
+##### 6.3.1.5.1 Concept and Configuration
+
+The RF-controlled spatial fading emulator can directly reproduce multipath radio propagation environments both in line-of-sight (LOS) and non line-of-sight (NLOS) situations by radio waves emitted from antenna probes arranged around a DUT. Thus, the emulator can be easily used for measurement of the MIMO characteristics of a HSPA/LTE multiple antenna device in a multipath fading environment.
+
+Figure 6.3.1.5.1-1 (a) and (b) show the configuration and arrangement of the antenna probes of the RF spatial fading emulator in an anechoic chamber. In this method, the DUT is designated as any device that possesses multiple antennas, including a HSPA or LTE device.
+
+The height of DUT from the floor of the anechoic chamber is  $H$ . The DUT can also be placed at a rotatable turn-table in order to set and vary the horizontal angle of the DUT. The DUT is surrounded by  $N$  numbers of antenna probes. The distance between DUT and each antenna probe is  $r$ . The antenna probe consists of two antennas. The one is a half-wavelength dipole set vertically for emitting the vertically-polarized wave and the other is a horizontally-located half-wavelength dipole for the horizontally-polarized wave. This configuration of the antenna-probe unit can represent a cross polarization power ratio, XPR, of incoming wave. The separation between vertical and horizontal antennas is  $d$ . The height of the antenna probe from the anechoic chamber floor is  $h$ . The distance between the ring of antenna probes and the walls of anechoic chamber is  $D$ . (Note if the anechoic chamber is not square, then  $D_1$  and  $D_2$  are used).
+
+A reference antenna probe is designated so that it can be used to determine the direction of motion of DUT. This parameter is designated as  $\phi_{shift}$ . The circular angle between antenna probes from the centre of the ring (i.e. DUT) is  $\phi_i$  with respect to the reference antenna probe.
+
+![Figure 6.3.1.5.1-1 (a) Experimental Setup. A 3D diagram of an anechoic chamber containing a DUT at height H and a ring of antenna probes at height h and distance r. An inset photo shows a close-up of a dual-polarized antenna probe. Below the chamber is a block diagram showing a Computer connected to a D/A Converter, which controls an Attenuator and Phase Shifter/Power Divider system connected to a Transmitter and the scattering units. A Receiver is also shown connected to the units.](f0a97d0d3818a253c1d2a009966081b1_img.jpg)
+
+Figure 6.3.1.5.1-1 (a) Experimental Setup. A 3D diagram of an anechoic chamber containing a DUT at height H and a ring of antenna probes at height h and distance r. An inset photo shows a close-up of a dual-polarized antenna probe. Below the chamber is a block diagram showing a Computer connected to a D/A Converter, which controls an Attenuator and Phase Shifter/Power Divider system connected to a Transmitter and the scattering units. A Receiver is also shown connected to the units.
+
+**(a) Experimental Setup**
+
+![Figure 6.3.1.5.1-1 (b) Arrangement of the antenna probes. A top-down circular diagram showing the DUT at the center and N scattering units (antenna probes) arranged in a circle of radius r. Unit #1 is the reference. Unit #i is at an angle phi_i. A red arrow indicates the direction of motion at an angle phi_shift from the reference unit.](f2ea0f64a770b22b902820457d262265_img.jpg)
+
+Figure 6.3.1.5.1-1 (b) Arrangement of the antenna probes. A top-down circular diagram showing the DUT at the center and N scattering units (antenna probes) arranged in a circle of radius r. Unit #1 is the reference. Unit #i is at an angle phi\_i. A red arrow indicates the direction of motion at an angle phi\_shift from the reference unit.
+
+**(b) Arrangement of the antenna probes**
+
+**Figure 6.3.1.5.1-1: Experimental setup of the spatial fading emulator**
+
+The key features of this method are that it does not use the sophisticated commercial channel emulator. By using the combination of phase shifters, power dividers and attenuators, operating in the RF band, it has been shown that a realistic fading channel environment can be emulated. To reduce the influence from the measurement equipment, the receiver, phase shifter, power divider, transmitter and computer are set outside of the anechoic chamber. Firstly, we describe channel response between the  $m^{\text{th}}$  base station, BS, antenna and the  $n^{\text{th}}$  handset antenna for  $M$ -by- $N$  MIMO radio communication system. The channel response is calculated by following equation:
+
+$$h_{nm} = \sum_{i=1}^N E_n(\phi_i) \sqrt{\Omega(\phi_i)} \frac{\lambda}{4\pi \cdot r} \exp[-j\{kr + 2\pi \cdot t \cdot f_D \cos(\phi_0 - \phi_i) + \alpha_{mi}\}] \quad (1)$$
+
+where  $E_n$  and  $f_D$  are radiation component of the  $n$ -th handset antenna and the Doppler frequency respectively.  $\phi_0$  is the direction of motion and  $\phi_i$  is the direction of the  $i$ -th antenna probe.  $\alpha_{mi}$  is initial phase of the signal radiated from the  $i$ -th antenna probe. The waves radiated from each base station (BS) antenna are uncorrelated each other. For the investigation of MIMO antennas, the waves from different BS antenna are represented by different sets of initial phases,  $\alpha_{mi}$ , of the waves. According to the propagation models, such as SCM and SCME, the angular power spectrum  $\Omega$  of the spatial cluster of incoming waves in the horizontal plane can be modelled by a Laplacian distribution in the following, for instance:
+
+$$\Omega(\phi) = \frac{P}{2\sigma} \exp\left\{-\frac{|\phi - \mu_\phi|}{\sigma}\right\} \quad (2)$$
+
+where  $P$  and  $\mu_\phi$  are power and average direction of angle of the cluster.  $\sigma$  is a standard deviation of the APS. In this case, the spatial distribution in the vertical plane is modelled by a delta function.
+
+In addition, the strongest point of the spatial fading emulator is to be capable of evaluating radiation characteristics of a handset antenna for the present OTA testing in 3GPP as well as the multipath-fading evaluation since the emulator is operated in a radio frequency (RF) band.
+
+A calibration of the RF-controlled spatial fading emulator is carried out using the following procedure:
+
+- 1) Firstly a half-wavelength dipole for the receiving antenna is vertically placed at the center of a circle arranging the antenna probes.
+- 2) A radio wave with vertical polarization is radiated only from a vertical dipole of the antenna probe #i ( $i=1, 2, \dots, L$ ), and then, the dipole at the center of the emulator can receive the wave. From this, we can obtain amplitude and phase of the RF signal from the transmitter to the receiver via the vertical dipole of the antenna probe #i.
+- 3) The attenuator and phase shifter are adjusted so that the RF signals received by the dipole at the center have the same values in amplitude and phase.
+- 4) Secondly the slotted cylindrical antenna is placed at the center of the antenna probes located on the circle.
+- 5) A radio wave with horizontal polarization is radiated only from a horizontally-located dipole of the antenna probe #i ( $i=1, 2, \dots, L$ ). From the received signal from the antenna probe #i, we also obtain amplitude and phase of the RF signal from the transmitter to the receiver via the horizontal dipole of the antenna probe #i.
+- 6) The attenuator and phase shifter are adjusted so that the RF signals received by the slotted cylindrical antenna at the center have the same values in amplitude and phase.
+
+The calibration procedure above mentioned can be performed by using an electrical-controlled RF switch. Thus, the calibration of the emulator can be done automatically using a computer in our system. Once the calibration is finished, we can vary the attenuators in order to produce a special distribution of the incoming wave and to make a cross polarization power ratio (XPR). Moreover, we can set an initial phase to each antenna probe to create a multipath fading channel.
+
+With regard to the signal-to-noise power ratio, SNR, of incoming wave, the signal power can be determined by an average value of faded signal powers received by a half-wavelength dipole antenna for the vertical polarization and a slotted cylindrical antenna for the horizontal polarization. Both antennas have an omni-directional radiation pattern. Thus, SNR can be obtained as the following equation:
+
+$$SNR = \frac{S_V + S_H}{N_0} \quad (3)$$
+
+where  $S_V$  and  $S_H$  are the average signal powers received by the dipole and slotted cylindrical antennas, respectively.  $N_0$  is the noise power that was calculated as a thermal noise within the frequency bandwidth of the radio communication.
+
+##### 6.3.1.5.2 Test Conditions
+
+In this method, all signals are operated and controlled at RF level. A computer (either a laptop or relatively powerful computer) is used to provide the followings:
+
+- 1) Graphical user interface (GUI) to set the input parameters, determine the measured parameters to be collected, setting of calibration parameters and setting of DUT parameters.
+- 2) Generating control signals to manipulate the phase angle of each Phase Shifter.
+- 3) Collecting measured raw data obtained via the DUT.
+- 4) Post-processing the measured raw data to derive the desired figure of merits (i.e. minimum requirements for DUT).
+- 5) To initiate the BS emulator and start the testing session (by establishing a communication session with DUT)
+
+The RF signals transmitted from the BS emulator's antenna connector are fed to a bank of Power Dividers. Each power divider provides identical RF signal from each of the output ports. The number of Power Dividers required is determined by  $N$ .
+
+Each Power Divider output is then fed to a Phase Shifter. The Phase Shifter is used to change the phase of the RF signal according to the parameter setting input to the computer earlier. Note that the control signal from the computer is digital-to-analogue, D/A, converted, before used to control the Phase Shifter. By controlling the phase of each RF signal, a Rayleigh distributed or other relevant multipath distribution can be obtained. The number of Phase Shifters required is determined by  $N$ .
+
+The output of the Phase Shifters is connected to the antenna probes. The signal from each Phase Shifter is fed to the vertical and horizontal antennas and radiates toward the DUT. The DUT then measures the signals from each antenna probe and the measurement data is reported back to the computer. The amount of measurement data to be collected can be controlled by the computer by setting the sampling rate,  $R$ .
+
+An example below illustrated the principle of creating Rayleigh faded signal by control the phase of each component wave in Figure 6.3.1.5.2-1.
+
+Number of antenna probes  $N$  : 15
+
+Direction of motion  $\phi_0$  : 10 deg.
+
+Doppler frequency  $f_D$  : 20 Hz
+
+Sampling frequency  $f_S$  : 400 Hz
+
+Radius of circle arranging antenna probes  $r$  : 1.0 m
+
+Operating frequency : 2.14 GHz
+
+Receiving antenna (Rx) : half-wavelength Dipole
+
+Radiation pattern of Rx  $E_n(\phi)$  : omni
+
+APS,  $\Omega(\phi)$  : Uniform
+
+![Figure 6.3.1.5.2-1: A line graph showing Normalized received power [dB] on the y-axis (ranging from -50 to 10) versus fd*t [λ] on the x-axis (ranging from 0 to 25). Two data series are plotted: 'Meas.' (solid blue line) and 'Cal.' (dashed red line). Both lines show rapid, random fluctuations between approximately -45 dB and 10 dB, characteristic of a Rayleigh faded signal. The two lines are closely overlaid, showing good agreement between measurement and calculation.](853ef5420f0432e626e83987e3f38a0b_img.jpg)
+
+Figure 6.3.1.5.2-1: A line graph showing Normalized received power [dB] on the y-axis (ranging from -50 to 10) versus fd\*t [λ] on the x-axis (ranging from 0 to 25). Two data series are plotted: 'Meas.' (solid blue line) and 'Cal.' (dashed red line). Both lines show rapid, random fluctuations between approximately -45 dB and 10 dB, characteristic of a Rayleigh faded signal. The two lines are closely overlaid, showing good agreement between measurement and calculation.
+
+Figure 6.3.1.5.2-1: Rayleigh faded signal by control the phase of each component wave
+
+### 6.3.1.Y Downlink Transmission Modes
+
+<Editor: add texts>
+
+### 6.3.2 Methodologies based on Reverberation Chamber
+
+#### 6.3.2.1 Candidate Solution 1
+
+The reverberation chambers is a metallic cavity or cavities that can emulate an isotropic multi-path environment which represents a reference environment for systems designed to work during fading, similar to how the free space “anechoic” reference environment is used for tests of Line-Of-Sight systems. The Rayleigh environment in a reverberation chamber is well known as a good reference for urban and indoor environments, but does not well represent rural and suburban environments.
+
+For a future Multi-antenna OTA measurement standard it is important to have a fast and repeatable test method to evaluate and compare multi-antenna devices in the environments and under the conditions where most people will use them. The overwhelming majority of calls/data connections with mobile phones are made indoors and in urban areas which can be very well represented by the reverberation chamber. These environments are well characterised by multi-path and 3D distribution of the communication signals and it makes sense to use the reverberation chamber for optimizing/evaluating devices with both single and multiple antenna configurations to be used indoors and in urban areas.
+
+The test setup for testing UE receiver diversity performance is composed of a base station emulator, a reverberation chamber equipped with fixed BS wall-mounted antennas, a switch to direct the base station signal to/from one of the BS wall mounted antennas, mechanical metallic stirrers and a rotating platform to hold the DUT (Figure 6.3.2.1-1). Alternatively, the chamber may contain one or more cavities coupled through waveguides or slotted plates (Figure 7.1-2).
+
+Reverberation chambers have no quiet zone. As long as the DUT is placed at least 0.5 wavelengths from the wall or metallic stirrers the result will be the same within the standard deviation of the chamber.
+
+Mechanical stirrers and switching among different fixed BS wall-mounted antennas (monopoles used for polarization stirring) allow simulating the Rayleigh fading at each antenna of the terminal inside the chamber. Accuracy can even be increased by rotating the platform holding the device.
+
+Each position of the mechanical stirrers for each position of the platform and each fixed BS antenna, represents a point of the Rayleigh distribution in terms of receive power on the device antennas. In that way a Rayleigh fading is artificially created.
+
+In that way, several UE metrics can be measured: throughput with RX-DIV, TRP, TIS (Total isotropic sensitivity), etc.
+
+For each point of the Rayleigh distribution created by the different configurations of the chamber, the metric is noted. This method can be used to measure UE sensitivity and UE radiated power.
+
+![Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity. The diagram shows a single reverberation chamber with a device under test (DUT) on a turntable inside. A mechanical stirrer is also inside. The DUT is connected to a 'Base station simulator' via a 'Switch'.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg)
+
+Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity. The diagram shows a single reverberation chamber with a device under test (DUT) on a turntable inside. A mechanical stirrer is also inside. The DUT is connected to a 'Base station simulator' via a 'Switch'.
+
+**Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity [source: Bluetest AB]**
+
+![Figure 6.3.2.1-2: Reverberation Chambers with Multiple Cavities. The diagram shows two adjacent reverberation chambers. The left chamber contains a 'Base station simulator' connected to a 'Switch 2xT', which is connected to multiple antennas inside the chamber. The right chamber contains a 'DUT' on a turntable. A 'waveguide' connects the two chambers. Both chambers have 'stirrers' and a 'slotted plate'.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg)
+
+Figure 6.3.2.1-2: Reverberation Chambers with Multiple Cavities. The diagram shows two adjacent reverberation chambers. The left chamber contains a 'Base station simulator' connected to a 'Switch 2xT', which is connected to multiple antennas inside the chamber. The right chamber contains a 'DUT' on a turntable. A 'waveguide' connects the two chambers. Both chambers have 'stirrers' and a 'slotted plate'.
+
+**Figure 6.3.2.1-2 Reverberation Chambers with Multiple Cavities [source: EMITE Ing]**
+
+##### 6.3.2.1.1 Concept and Configuration
+
+In order to calibrate the reverberation chamber a broadband antenna can be used to measure the losses in the chamber with a network analyzer. This takes < 10 minutes. CTIA RCSG is working on a standard methodology for reverberation chamber calibration.
+
+There are no active electronics in the measurement path that needs to be calibrated.
+
+Reflections in turntables, cables, doors, etc, do not degrade accuracy. Reflections increase the richness of the channel in the reverberation chamber.
+
+Existing studies show that low standard deviation (good accuracy) can be achieved by measuring the DUT in sufficient number of different positions and calculate the average of the values. Some analysis (see relevant references in [2]) show a typical standard deviation less than 0.5 dB at about 800 MHz, in a reverberation chamber with a size of 1.2m x 1.75m x 1.8m and continuous mode stirring. At higher frequencies or with a chamber of larger dimensions the standard deviation decreases and accuracy increases.
+
+The following figure presents an example for an HSDPA receive diversity test configuration in a reverberation chamber.
+
+For these tests we emulate an HSDPA call with a Node B emulator. The latter is connected to one of the 3 BS wall-mounted antennas through a switch. A fourth antenna allows measuring the DL received signal in the chamber with a spectrum analyzer.
+
+![Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber. The diagram shows a Node B emulator connected to a switch. The switch is connected to three wall-mounted antennas inside a reverberation chamber. A fourth antenna is also inside the chamber, connected to a spectrum analyzer. The chamber contains a rotating platform with a DUT (Device Under Test) and two metallic stirrers.](a1890b9a9b85f13e67ed59bbad623659_img.jpg)
+
+The diagram illustrates the test bench configuration for testing in a reverberation chamber. On the left, a Node B emulator is shown. A cable connects it to a 'Switch' box. From the switch, three cables lead into a 3D representation of a reverberation chamber, connecting to three wall-mounted antennas. Inside the chamber, there is a rotating platform holding a DUT (represented by a laptop icon) and two metallic stirrers. A fourth antenna is mounted on the bottom wall of the chamber, with a cable leading out to a spectrum analyzer.
+
+Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber. The diagram shows a Node B emulator connected to a switch. The switch is connected to three wall-mounted antennas inside a reverberation chamber. A fourth antenna is also inside the chamber, connected to a spectrum analyzer. The chamber contains a rotating platform with a DUT (Device Under Test) and two metallic stirrers.
+
+**Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber**
+
+In order to create a Rayleigh fading environment, we've got 3 types of parameters that can be set using a tool on a computer plugged to the chamber:
+
+- Antenna among the 3, installed at the top of the cavity with different polarizations, is chosen
+- Turning the platform that holds the DUT
+- The 2 metallic stirrers near the walls can be moved on their axes
+
+##### 6.3.2.1.2 Test Conditions
+
+Once the chamber is calibrated, the downlink throughput testing can be performed as follows to get one throughput averaged measurement:
+
+- The DUT is placed in the chamber at least 0.5 wavelengths from the wall or from the metallic stirrers
+- An HSDPA call is emulated using the NodeB emulator with a pre-defined BS TX power.
+- To get one measurement sample we set up one of the following possible combinations: position of the rotating platform  $\{0, \pi/2, \pi, 3\pi/2, \text{etc.}\}$  + position of the metallic stirrers  $\{0, 25, 50, 75, 100, \text{etc.}\}$  + antenna from  $\{1, 2, 3\}$ .
+
+- For each one of these combinations we can record CQI, DL Throughput and DL Power in the chamber. The latter is measured using a fourth antenna and a spectrum analyzer. This constitutes one measurement sample. For each measurement sample, the link adaptation is performed manually or automatically on the NodeB emulator as follows: the HS-DSCH is configured (modulation, transport block size, number of HS-DSCH) depending on the CQI (Channel Quality Indicator) reported by the UE (User Equipment) according to the mapping table in [5].
+- Once enough different DL throughput measurement samples (ideally  $\geq 100$ ), corresponding to different Antenna, rotating platform's position and stirrers' position combinations, are recorded for the same NodeB emulator DL TX power, they can be averaged to have the averaged DL throughput measurement.
+
+The test duration can be significantly reduced if all these steps are automated. With a variable reference channel (VRC) and continuous mode stirring total measurement time of less than 10 minutes could be possible.
+
+#### 6.3.2.2 Candidate Solution 2
+
+The reverberation chamber by itself has a limited range of channel modeling capabilities. Specifically,
+
+- The power/delay profile is limited to a single decaying exponential
+- The Doppler spectrum and maximum Doppler is limited by the relatively slow motion of the stirrers
+- It is difficult to impart a specific, repeatable MIMO fading correlation on the downlink waveform
+
+These limitations can be overcome when a MIMO channel emulator and reverberation chamber are cascaded.
+
+The power/delay profile (PDP) can be enhanced beyond the single decaying exponential by programming the channel emulator with fading taps set at the desired excess delays. The resulting PDP will be the convolution of the taps provided by the channel.
+
+The fading taps provided by the channel emulator allow much higher Doppler spreads than from the reverberation chamber alone. If a classical fading spectrum with a maximum Doppler of 100 Hz is desired, the channel emulator is configured to provide this. The resulting overall Doppler spectrum that results is the convolution of the channel emulator's Doppler spectrum with that of the reverberation chamber.
+
+The fading produced by the cascaded channel emulator and reverberation chamber has a double-Rayleigh amplitude distribution. Because performance simulations generally use Rayleigh fading, simulation results for the double-Rayleigh case are not available.
+
+The benefit is testing with a much higher maximum Doppler, on the order of 100 Hz or higher, than is possible with the reverberation chamber alone. Under these conditions, the reverberation chamber-induced fading will effectively be constant while the channel emulator-induced fading will dominate. Therefore, while a receiver's performance under such circumstances will definitely be different than under normal Rayleigh fading conditions, it should not undermine the receiver's ability to demodulate. Tests have shown that this is indeed the case. However, due to the lack of double-Rayleigh simulation results, measured results should only be compared with other devices using these same test conditions.
+
+The correlation of fading between the downlink MIMO transmission paths can be adjusted using the channel emulator. This is also known as "BS correlation," reflecting the fact that it is controlled on the BS side of the link. The way to set this correlation using the channel emulator is as follows: using the Kronecker model of fading correlation, set the desired correlation of the transmit or BS correlation matrix. The receiver or MS correlation matrix should be set to identity. An example is given for a 2x2 MIMO system:
+
+$$R_{BS} = \begin{bmatrix} 1 & \rho \\ \rho & 1 \end{bmatrix}, \quad R_{MS} = \begin{bmatrix} 1 & 0 \\ 0 & 1 \end{bmatrix}, \quad R_{chan} = R_{BS} \otimes R_{MS}$$
+
+The value for  $\rho$  is the desired correlation between the two downlink paths. Note that it is not possible to control the phase of the correlation, only the amplitude.
+
+The downlink antennas in the chamber are typically referred to as "wall" antennas. There should be a number of them equal to the number of spatial streams supported by the DUT. The spacing of the wall antennas is not very important. Tests have shown that as the spacing between them is changed over a range between 6 and 80 mm, the measured correlation changes very little, on the order of 5% to 10%.
+
+##### 6.3.2.2.1 Concept and Configuration
+
+The general configuration to be used for testing is shown in Figure 6.3.2.2.1-1. The specific example shown there is for two BS antennas. If higher order MIMO devices are to be tested, additional antennas are required. The channel emulator is placed between the (e)NodeB emulator and the reverberation chamber. Two calibrations are performed:
+
+- 1) Calibration of reverberation chamber loading to set the proper chamber impulse response. Most of the time, the chamber will be loaded to produce a specific, desired chamber RMS delay spread. This is achieved using such devices as a phantom head, tank filled with liquid, and RF absorbing foam. For use with the channel emulator, it is desirable to set the chamber RMS delay spread as low as is allowable (approximately 55 ns)<sup>1</sup>, although higher RMS delay spreads are also legitimate, depending on the desired overall PDP.
+
+NOTE 1: If the delay spread is reduced to below this point, the chamber's ability to produce the desired Rayleigh amplitude distribution at the DUT is degraded.
+
+- 2) Calibration of the losses from (e)NodeB emulator to DUT location. This is already described in the test methodology for the reverberation chamber alone (subclause 6.3.2.1).
+
+The calibrations are performed in this order, using a test antenna as the DUT antenna, and with the DUT in the chamber as it will be during the test. The contents of the chamber should not be disturbed after the calibration is complete. More information about the calibration procedures are found in a later section.
+
+![Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration. The diagram shows an (e)NodeB Emulator connected to a Channel Emulator. The Channel Emulator is connected to two Wall Antennas inside a reverberation chamber. The Wall Antennas are connected to a Device Under Test (DUT) on a Turntable inside the chamber. A Return Path is shown from the DUT back to the (e)NodeB Emulator. The chamber also contains a Stirrer.](c85b57b2414f341860dfc338e1cf2509_img.jpg)
+
+The diagram illustrates the test bench configuration. On the left, an (e)NodeB Emulator is connected to a Channel Emulator. The Channel Emulator has two output lines leading to two Wall Antennas located inside a large rectangular reverberation chamber. Inside the chamber, there is a Device Under Test (DUT) placed on a Turntable. A Return Path is indicated by a line from the DUT back to the (e)NodeB Emulator. The chamber also contains a Stirrer and is labeled with 'Wall Antennas', 'Stirrer', 'Device Under Test', and 'Turntable'.
+
+Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration. The diagram shows an (e)NodeB Emulator connected to a Channel Emulator. The Channel Emulator is connected to two Wall Antennas inside a reverberation chamber. The Wall Antennas are connected to a Device Under Test (DUT) on a Turntable inside the chamber. A Return Path is shown from the DUT back to the (e)NodeB Emulator. The chamber also contains a Stirrer.
+
+**Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration**
+
+##### 6.3.2.2.2 Test Conditions
+
+After the chamber is calibrated, the emulator is configured for the desired channel model, including the end-to-end PDP, the desired fading spectrum and Doppler spread, and the MIMO fading correlation. At this point, the system is ready to test the DUT, and a procedure appropriate to the FOM being measured is carried out.
+
+There are two basic operating methods, dependent on the motion of the stirrers and the state of the fading in the channel emulator, the “dynamic” and the “move-and-stop” methods.
+
+In the dynamic method, the stirrers, turntable and channel emulator to operate continuously while the specific FOM is measured. A good example of this use would be throughput measurements under the conditions of a high Doppler rate, or, measured while the signal levels are varied over a wide range.
+
+In the move-and-stop method, the stirrers and turntable are positioned in a number of combinations as described in 6.3.2.1.2. The channel emulator is allowed to run for a fixed length of time (usually 1 or 2 seconds is enough) and paused. The FOM is measured while the stirrers and turntable are not in motion, and the channel emulator is paused. In this method, the number of fixed positions and emulator states must be at least enough to guarantee the proper amplitude distribution. Automation of this entire procedure will significantly reduce the test time.
+
+#### 6.3.2.Y Downlink Transmission Modes
+
+*<Editor: Text to be added>*
+
+# --- 7 Measurement Results from COST2100
+
+## 7.1 Reference Measurement Channels
+
+*<Editor: Text to be added>*
+
+# --- 8 Measurement Results from CTIA
+
+## 8.1 Reference Measurement Channels
+
+*<Editor: Text to be added>*
+
+# --- 9 Conclusions
+
+In section 9.1 the different candidate methodologies are compared. In section 9.2 lessons learnt after round robin test campaign together with final conclusions are given.
+
+## 9.1 Comparison of Candidate Methodologies
+
+The candidate methodologies for MIMO OTA can be broadly classified into 3 categories:
+
+- 1) Anechoic Chamber
+- 2) Reverberation Chamber
+- 3) Multi-stage Method
+
+It is recognized that the content of the table is preliminary and based on currently available information. Many of the attributes of the candidate methodologies require further study/proof and are subject to change.
+
+| Attribute                                           | Reverberation Chamber       |                                         | Anechoic Chamber Based                             |                                                    |                                          | Multi-stage methods                               |                                          |
+|-----------------------------------------------------|-----------------------------|-----------------------------------------|----------------------------------------------------|----------------------------------------------------|------------------------------------------|---------------------------------------------------|------------------------------------------|
+|                                                     | RC                          | RC + CE                                 | Single Cluster                                     | Ring                                               | 2 channel method                         | 2 stage method <sup>7</sup>                       | Antenna method <sup>6</sup>              |
+| <b>Setup</b>                                        |                             |                                         |                                                    |                                                    |                                          |                                                   |                                          |
+| Major components                                    | Reverberation chamber       | Channel Emulator, Reverberation Chamber | Channel emulator, probe antennas, anechoic chamber | Channel emulator, probe antennas, anechoic chamber | Channel emulator, probe antenna          | Channel emulator, probe antenna, anechoic chamber | Probe Antenna, Anechoic Chamber          |
+| Number of probe antennas                            | 2-9                         | 2 – 9                                   | 3-16 (varies)                                      | 8-32 (varies)                                      | 2-3                                      | 1                                                 | 1                                        |
+| <b>Operating bands</b>                              |                             |                                         |                                                    |                                                    |                                          |                                                   |                                          |
+| Supported 3GPP bands                                | All                         | All                                     | All                                                | All                                                | All                                      | All                                               | All                                      |
+| Bandwidths supported: HSPA/LTE                      | Yes/Yes                     | Yes/Yes                                 | Yes/Yes                                            | Yes/Yes                                            | Yes/Yes                                  | Yes/Yes                                           | Yes/Yes                                  |
+| <b>Channel Modelling aspects</b>                    |                             |                                         |                                                    |                                                    |                                          |                                                   |                                          |
+| 2D/3D                                               | 3D                          | 3D                                      | 2D/3D (varies)                                     | 2D/3D <sup>1</sup> (varies)                        | 2D/3D                                    | 2D/3D                                             | 2D/3D <sup>1</sup>                       |
+| Number of spatial clusters                          | 1                           | 1                                       | 1                                                  | 1-24 (varies)                                      | 1-2                                      | 1-24                                              | 1-No upper bound                         |
+| Power angular spectrum per cluster                  | Uniform                     | Uniform                                 | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| Angular spread                                      | Random <sup>8</sup>         | Random <sup>8</sup>                     | Controllable                                       | Controllable                                       | Partly Controllable                      | Controllable                                      | Controllable                             |
+| Power delay profile                                 | Exponential decay           | Controllable + Exponential              | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| Delay spread                                        | Slightly controllable decay | Controllable                            | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| Doppler shift                                       | Limited                     | Controllable                            | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| Supported channel models                            | Uniform <sup>5</sup>        | Uniform spatial, controllable multipath | Single cluster, multipath (varies)                 | SCME, Single Cluster, Uniform, Arbitrary           | SCME, Single cluster, uniform, arbitrary | SCME, Single cluster, uniform, arbitrary          | SCME, Single cluster, uniform, arbitrary |
+| Controllable spatial characteristics of BS antennas | FFS                         | Controllable                            | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| XPR                                                 | Constant                    | Constant                                | Controllable                                       | Controllable                                       | Controllable                             | Controllable                                      | Controllable                             |
+| <b>Other MIMO OTA attributes</b>                    |                             |                                         |                                                    |                                                    |                                          |                                                   |                                          |
+| Supported 3GPP                                      | 1 – 7                       | 1 – 7                                   | 1 – 7                                              | 1 – 7                                              | 1 – 7                                    | 1 – 7                                             | 1-7                                      |
+
+|                                                                  |                                   |                                   |                                                                           |                                                                           |                                                                           |                                                                           |                                                           |
+|------------------------------------------------------------------|-----------------------------------|-----------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|---------------------------------------------------------------------------|-----------------------------------------------------------|
+| transmission modes [7]                                           |                                   |                                   |                                                                           |                                                                           |                                                                           |                                                                           |                                                           |
+| Ability to control interference direction                        | No                                | No                                | Limited – Yes                                                             | Yes                                                                       | Yes                                                                       | Yes                                                                       | FFS                                                       |
+| SNR control <sup>3</sup>                                         | FFS                               | Yes                               | Yes                                                                       | Yes                                                                       | Yes                                                                       | Yes                                                                       | N/A (Part of channel capacity calculation)                |
+| DUT size constraints                                             | None                              | None                              | 0.5 – 4 lambda, (varies)                                                  | 0.5 – 4 lambda (varies)                                                   | FFS                                                                       | None                                                                      | None                                                      |
+| <b>Measurements &amp; Results</b>                                |                                   |                                   |                                                                           |                                                                           |                                                                           |                                                                           |                                                           |
+| Supported FOM <sup>2</sup><br>(Categories in Sec 5.1)            | I, II, part of IV (except MEG), V | I, II, part of IV (except MEG), V | I-V +Throughput( $\theta$ ) + other antenna characteristics <sup>10</sup> | I-V +Throughput( $\theta$ ) + other antenna characteristics <sup>10</sup> | I-V +Throughput( $\theta$ ) + other antenna characteristics <sup>10</sup> | I-V +Throughput( $\theta$ ) + other antenna characteristics <sup>10</sup> | II, III, IV + other antenna characteristics <sup>11</sup> |
+| Demonstration results available                                  | Yes                               | Yes                               | Yes                                                                       | Yes                                                                       | Yes                                                                       | Yes                                                                       | Partial                                                   |
+| <b>System/Hardware Details</b>                                   |                                   |                                   |                                                                           |                                                                           |                                                                           |                                                                           |                                                           |
+| Calibration equipment/method                                     | 2-Port VNA <sup>4</sup>           | 2-Port VNA <sup>4</sup>           | Joint OTA link calibration using 2-port VNA <sup>4</sup>                  | Joint OTA link calibration using 2-port VNA <sup>4</sup>                  | Range calibration by 2-port VNA <sup>4</sup> , for example                | Chamber calibration by 2-port VNA <sup>4</sup> , second stage calibration | Chamber calibration by 2-port VNA <sup>4</sup>            |
+| Use this method in SISO OTA                                      | Yes                               | Yes                               | Yes                                                                       | Yes                                                                       | Yes                                                                       | Yes                                                                       | Yes                                                       |
+| Re-use potential existing SISO OTA systems                       | High                              | High                              | High                                                                      | High                                                                      | High                                                                      | High                                                                      | High                                                      |
+| <b>Other Considerations</b>                                      |                                   |                                   |                                                                           |                                                                           |                                                                           |                                                                           |                                                           |
+| Requires non-intrusive test mode for antenna pattern measurement | N/A <sup>9</sup>                  | N/A <sup>9</sup>                  | No                                                                        | No                                                                        | No                                                                        | Yes                                                                       | Yes                                                       |
+| Throughput measurement method                                    | OTA                               | OTA                               | OTA                                                                       | OTA                                                                       | OTA                                                                       | Conducted via temporary antenna connector                                 | N/A (Capacity metric calculated from antenna parameters)  |
+
+### NOTES:
+
+Note 1: 3D is feasible if 3D channel model is used.
+
+Note 2: Metrics supported: the measurement metrics supported by the test method like throughput, TRP/TRS, antenna pattern, gain imbalance, etc
+
+Note 3: SNR control: explicit SNR, implicit SNR, etc
+
+Note 4: VNA is an abbreviation of Vector Network Analyzer.
+
+- Note 5: random AoA, uniform average
+- Note 6: antenna-based method uses stage 1 from the 2 stage method and derive from this, a MIMO channel capacity FOM
+- Note 7: 2 stage method does not require channel capacity metric, but measures throughput using second stage in a conducted test
+- Note 8: The angular spread observed in a reverberation chamber depends on the duration of observation. For short durations, it is random. For long durations, the angle spread converges to a fixed value based on a uniform angular distribution.
+- Note 9: the antenna pattern cannot be measured, if needed
+- Note 10: The throughput, branch imbalance, spatial correlation, antenna gain can be measured as a function of DUT rotation
+- Note 11: The branch imbalance, spatial correlation, antenna gain can be measured as a function of DUT rotation
+
+### 9.1.1 Definitions of rows in the table
+
+#### Setup
+
+Major components: List of main hardware components required
+
+Number of probe antennas: self-explanatory
+
+#### Operating bands
+
+Supported bands: Which frequency bands does the method support (TS 36.101, TS 25.101)
+
+Bandwidths supported: HSPA/LTE: Does the method support at least 20 MHz
+
+#### Channel Modelling
+
+2D/3D: ability of method to support 2D/3D modelling of environment
+
+Number of clusters: number of taps/multipath components supported by method. This determines how 'spread out' the arriving signal is spatially.
+
+Power angular spectrum per cluster: Types of power angular (azimuth) spectrum distributions supported by method. The distributions should be settable for each cluster.
+
+Angular spread: Ability to set the amount of angle spread. This determines how 'spread out' the arriving signal corresponding to each cluster is spatially.
+
+Power Delay Profile: Types of power delay profiles supported. Ability to control the powers and delays of each of the clusters.
+
+Delay spread: ability to support different delay spreads.
+
+Doppler shift: types of Doppler spectra that can be supported. This determines the frequency domain (and by duality, the time domain) characteristics of the wireless channel emulated.
+
+Supported channel models: channel models supported by method.
+
+Controllable spatial characteristics of BS antennas: ability to set the spatial correlation of the BS antennas.
+
+XPR: Cross-polarization ratio values supported.
+
+#### Other MIMO OTA attributes
+
+Supported 3GPP transmission modes: self-explanatory. Refer to [7].
+
+Ability to control interference direction: ability to model the direction from which interference arrives
+
+SNR control: Explicit SNR, Implicit SNR
+
+DUT size constraints: range of DUT size supported. (quiet zone dependency on channel model and number of antennas)
+
+#### Measurements and Results
+
+Supported FOM (subclause 5.1): The figures of merit listed in subclause 5.1 that are supported. Does the method provide any other enhancements to the FOM measured?
+
+Demonstration results available: Are demonstration results available?
+
+#### System/Hardware Details
+
+Calibration equipment/method: list of main equipment required for calibration of system with some insight into the calibration approach.
+
+Use this method in SISO OTA: Can this same method be used in SISO OTA too?
+
+Re-use potential existing SISO OTA systems: Can this method be re-used in existing SISO OTA systems?
+
+#### Other considerations
+
+Requires non-intrusive test mode for antenna pattern measurement: Does the method require a special mode (hardware/software capability) in the UE to make antenna pattern measurements
+
+Throughput measurement method: Are the throughput measurements made over the air or in a conducted setup?
+
+## 9.2 Lessons learnt and conclusions
+
+After round robin testing campaign the following conclusions have been reached and agreed, and taken as lessons learnt:
+
+### Test Result Agreement within a Methodology
+
+- Anechoic chamber based OTA typically shows good level of agreement when using UMi and UMa channel propagation models.
+- Reverberation chamber based OTA typically shows good level of agreement when using NIST, UMi and UMa channel propagation models.
+- Uncertainties in the measurements and different lab setups prevent full comparison in some cases.
+- It can be seen from the comparison that Nokia's two stage results and Agilent two-stage results from Pool 4 USB-dongle are comparable with a 3dB difference. One possible reason for the difference related to measurement setup is that the Nokia setup selected cross polarized BS antennas and the Agilent setup selected uncorrelated BS antennas. Apart from this difference the setups should be comparable and any difference in results likely to be due to the achievable accuracy of calibration between two separate labs. In some cases, results within a methodology were corrupted by inadvertent errors in test equipment settings or changes to the DUT's operating environment.
+
+### Test Result Agreement between Methodologies
+
+- Results show that several test methods were proven to be able to show a clear ranking between DUTs.
+- In several cases, very good agreement between anechoic (multiprobe, single cluster and two-channel methods), reverberation chamber and two-stage results were observed for a single device, however uncertainties in the measurements and in the labs setups prevent to take any conclusion regarding any inter-methodology comparison.
+- For some other test cases, big differences among the test method results are still to be further understood.
+- It's not obvious as to how different methodologies can be directly compared due to the fact that there are many different variables between the methods.
+
+The following issues were identified which made a true comparison difficult:
+
+- Test configuration issues: lack of clearly defined test environment (Base Station antenna correlation settings, channel model details, not all labs had access to all DUTs, and DUT configuration varied between labs.
+
+- Reference UE issues: Instability of DUTs over test duration, laptop noise affected throughput results, and receiver (antenna and baseband) characteristics of each test UE were unknown so difficult to verify specifically what caused differences in results.
+- Propagation Environment Aspects: SCME channel models are two-dimensional only; maybe there are (or there will be) more appropriate channel models for us to consider, 1 drop/instance of a channel model unlikely to be enough to verify real-world performance.
+- Test equipment aspects: eNode B emulators were not mature and even today labs have found UE performance differences between them.
+
+It is understood to be feasible to specify a test methodology to measure multiple antenna receiver performance, but the different types of methods need further technical analysis before agreement can be made on what methodology(ies) are finally selected.
+
+In chapter 10, recommendations are given on how to scope the work so that the standardization of a method (s) can progress in the most effective and efficient way.
+
+# --- 10 Recommendations
+
+Recommendation is to close current SI and open a WI which basically will take all the lessons learnt in the SI phase in order to conclude in a method (s) able to accurately provide MIMO OTA performance that is meaningful compared to MIMO end user experience.
+
+After Round Robin testing campaign it has been proven that the different candidate methodologies are able to provide a measure of MIMO OTA performance, nevertheless it is recognized that there are a number of pending issues that need to be technically treated in order to be able to conclude a final test methodology(ies). The following list of items are suggested to be considered within the scope of the WI:
+
+1. The initial focus shall be on over-the-air testing of LTE MIMO terminals (with expansion to LTE SIMO and HSPA SIMO/MIMO afterwards).
+2. Deploy reference antennas and reference device(s)
+  - a. Realize and validate reference antennas
+  - b. Agree on a reduced set of devices to be tested across all labs.
+  - c. Reference devices will be selected such that they represent as well several chipset manufacturers.
+3. Create reference environment (standardization of RF environment):
+  - a. RF environment shall consider all key radio link aspects, including, for example, downlink power levels, SNR, (e)Node B transmission modes, reference channel types and channel rank. In order to minimize variables and uncertainty during the initial phase, tests shall use of LTE Transmission Mode 3, Fixed Reference Channel, and forced Rank 2.
+  - b. Standardize eNB, channel emulator
+    - i. Agree on eNodeB emulator settings (begin with same s/w version, MCS settings, etc.). emulator parameters shall be evaluated and standardized for MIMO OTA performance evaluation, ensuring alignment with the configurations used in real-life deployments.
+    - ii. Define BS antenna parameters
+    - iii. Standardize channel emulator, validation of channel emulator.
+  - c. Use channel model from TR
+
+- i. Clearly select the channel models from the TR and specify all the parameters used to ensure consistent test results within and across methodologies. The selection shall be done to reflect likely field conditions.
+    - ii. Therefore, validation procedures shall be developed to ensure that any given channel model has been correctly implemented within each methodology.
+  - d. Utilize reference antennas in combination with a known UE baseband receiver (verified via conducted RF tests with and without channel impairments). This is intended to verify whether the characteristics of the receive antenna design (*i.e.* correlation, gain imbalance, etc) affecting receiver performance can be accurately distinguished by proposed test methods
+    - i. Measure conducted reference sensitivity unimpaired.
+    - ii. Measure conducted performance (power and noise levels need to be defined) using an agreed channel model with direct connections (no antenna impact).
+    - iii. Measure conducted performance (power and noise levels need to be defined) using simulated or measured reference antenna and agreed channel model.
+  - e. Validate channel model implementation in chamber
+4. Simulation of expected UE performance in chosen channel model
+  5. Identify the repeatability, reliability and level of measurement uncertainty of each proposed methodology.
+  6. Evaluate the use of statistical performance analysis in order to minimize test time and help ensure accurate performance assessment.
+  7. Consider whether any additional MIMO performance metrics are necessary.
+  8. For a final selection of the method(s) cost, time and other implications should be considered.
+
+Also it is noted that the standardisation of multiple test methodologies may be one eventual outcome but, during the WI, RAN4 shall avoid fragmentation of the absolute measurement result that is output as part of the 3GPP test framework for any given tested device. 3GPP shall also ensure that all devices can be comparably tested. Currently throughput is the figure of merit to be used as to compare the different results across the different methods. Absolute throughput is agreed as the only figure of merit that will be used for comparable testing across different methods.
+
+# Annex A (Informative): Test Plan for Anechoic Chamber based candidate methodologies with 3 or more probe antennas
+
+## A.1 Introduction
+
+This annex describes the test plan for OTA throughput comparison measurements. This test plan is focused on anechoic chamber based methodologies with 3 or more probe antennas. The plan has previously been presented in COST2100 and CTIA.
+
+The aim of the comparison measurement campaign is to study how well an OTA throughput measurement in a predefined propagation channel can be reproduced in different labs. Testing time and challenges in system calibration are also matters of interest. There is a risk that labs participating in the measurement campaign use different setups, different channel model realizations, and different Node-B Emulator settings. This may lead into some inconsistent results. Therefore, the goal of this test plan is to define the radio channel conditions and the throughput measurement in such detail that the results are as comparable as practically possible.
+
+To be able to compare throughput results between labs one of the challenges of this test plan has been to define an absolute power level in the center of the test volume of the used chamber.
+
+One of the important aspects for further study is to implement horizontal polarization to the test system. Because the aim of this contribution was to study calibration and repeatability, it was left out. However to create a realistic radio channel to the chamber, both vertical and horizontal polarizations have to be taken in to account.
+
+## A.2 Test setup
+
+Testing is done in an anechoic chamber. A number of vertically polarized antennas are located in a horizontal plane in respect to the UE. The typical number of antennas is at least eight in a full circle and at least three for a single cluster test. The probe distance from the UE will vary from lab to lab. The fading channel is generated by using a channel emulator/simulator which is fed by a Node-B Emulator. The UE will be rotated around its vertical centre line by using a turntable or manually. Figure A.2-1 depicts the test setup. The requirement on the probe antenna is FFS.
+
+![Diagram of the test setup showing a UE (EUT) in the center of an anechoic chamber, surrounded by multiple probe antennas. The EUT is connected to a Channel Emulator, which is connected to a Communication Tester.](822e033872d5ab16e861571f47b81ba7_img.jpg)
+
+The diagram illustrates the test setup within an anechoic chamber, represented by a square with jagged edges. In the center is a circular EUT (Equipment Under Test) with a curved arrow indicating rotation. Surrounding the EUT are eight black dots representing probe antennas arranged in a circle. Curved lines connect each antenna to a 'Channel Emulator' box on the right. Below the Channel Emulator is a 'Communication Tester' box, which is also connected to the Channel Emulator.
+
+Diagram of the test setup showing a UE (EUT) in the center of an anechoic chamber, surrounded by multiple probe antennas. The EUT is connected to a Channel Emulator, which is connected to a Communication Tester.
+
+Figure A.2-1: Test Setup (Communication Tester here means Node-B Emulator)
+
+### A.2.1 Calibration
+
+The test system shall be calibrated using the setup in Figure A.2.1-1. The UE is replaced by a reference antenna with known gain characteristics. A CW non-faded calibration signal is fed to one probe at a time and received by the reference antenna. Based on the known properties of the reference antenna, the path loss from the input of the channel emulator to the UE location will be calculated.
+
+The settings (except fading model) of the channel emulator during the calibration and measurement phases should be identical. The channel model used in the calibration is static propagation conditions (1 tap, no fading, max. output power). Signal is routed to one probe antenna at a time. Each path (antenna probe) is calibrated separately.
+
+![Figure A.2.1-1: Calibration Setup. The diagram shows a square chamber with jagged edges representing a reverberation chamber. Inside, there are several probe antennas labeled 1, 2, 3, 4, 5, 6, 7, and n. A reference antenna labeled B is positioned in the center. To the right, a 'Channel Emulator' and a 'VNA' (Vector Network Analyzer) are shown. Point A is the input to the channel emulator, and point B is the UE location represented by the reference antenna. Curved lines represent the signal paths from the channel emulator through the probes to the reference antenna.](c1278da91cbcabe32628e589ebc47418_img.jpg)
+
+Figure A.2.1-1: Calibration Setup. The diagram shows a square chamber with jagged edges representing a reverberation chamber. Inside, there are several probe antennas labeled 1, 2, 3, 4, 5, 6, 7, and n. A reference antenna labeled B is positioned in the center. To the right, a 'Channel Emulator' and a 'VNA' (Vector Network Analyzer) are shown. Point A is the input to the channel emulator, and point B is the UE location represented by the reference antenna. Curved lines represent the signal paths from the channel emulator through the probes to the reference antenna.
+
+**Figure A.2.1-1: Calibration Setup (VNA stands for Vector Network Analyzer)**
+
+Calibration steps:
+
+- Measure the attenuation between points A and B through each probe. Point A is the input to the channel emulator and point B is the UE location represented by the reference antenna.
+- Compensate for path loss differences. This can be done for example by adjusting the channel emulator outputs by the factor:
+
+$$Path_{compensation_i} = Attn_i - \max(Attn)$$
+
+where
+
+$Path_{compensation_i}$  is the compensation factor for probe i to be adjusted by channel emulator.
+
+$Attn_i$  is the measured attenuation via probe i, and,
+
+$\max(Attn)$  is the highest attenuation over all probes.
+
+- Calculate the path loss of each route as follows:
+
+$$PathLoss = \max(Attn) - G_{ref antenna}$$
+
+#### A.2.1.1 Calibration Check
+
+A UE sensitivity measurement is performed for each probe antenna using the static propagation conditions model. The result of this check can be used to verify that the probe antennas have been properly calibrated.
+
+Configure the test system according to section B.3 with the following exceptions:
+
+- 1) The channel model is single tap, non faded
+
+- 2) Only one probe antenna is used at a time
+
+Rotate the UE using an angle step of 45° and measure the UE reference sensitivity which is the highest transmit power resulting in a throughput of between 1499 kbps and 1999 kbps for each probe antenna. Note: These throughput values are for H-Set 3, 16QAM. For H-Set 6, the values are FFS.
+
+For each probe and angle of rotation, record the UE reference sensitivity in Table A.2.1.1-1.
+
+**Table A.2.1.1-1: Calibration check table**
+
+| Reference sensitivity/ Angle | Path 1 [dBm] | Path 2 [dBm] | Path 3 [dBm] | Path 4 [dBm] | Path 5 [dBm] | Path 6 [dBm] | Path 7 [dBm] | Path 8 [dBm] |
+|------------------------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|
+| 0°                           |              |              |              |              |              |              |              |              |
+| 45°                          |              |              |              |              |              |              |              |              |
+| 90°                          |              |              |              |              |              |              |              |              |
+| 135°                         |              |              |              |              |              |              |              |              |
+| 180°                         |              |              |              |              |              |              |              |              |
+| 225°                         |              |              |              |              |              |              |              |              |
+| 270°                         |              |              |              |              |              |              |              |              |
+| 315°                         |              |              |              |              |              |              |              |              |
+| Path Average                 |              |              |              |              |              |              |              |              |
+
+$$PathAverage_n = 10 * \log_{10} \left( \frac{8}{\sum 1/10^{(Path_h/10)}} \right)$$
+
+The path loss compensation is considered successful if the path average results are within  $\pm 1$  dB.
+
+### A.2.2 Radio Channel Conditions
+
+The desired radio channel models are the same as described in the main part of this TR (subclause 6.2). The recommended sub-set of channel models for anechoic chamber based measurements are listed below.
+
+For full circle testing:
+
+- SCME Urban micro-cell,
+- SCME Urban macro-cell, and
+
+For single cluster testing:
+
+- Single Spatial Cluster Model with Multi-path based on SCME Urban micro-cell, or
+- Single Cluster Multi-Path Model based on Extended Pedestrian A (EPA)
+
+The channel model used in the test is independent of implementation. When/if the sum of sinusoids based implementation of SCME channel models is used, the number of sub-paths per cluster is 20.
+
+NOTE: The Doppler spectrum is based on the geometry (AoA and DoT).
+
+#### A.2.2.1 Average channel power
+
+During the calibration phase the static propagation condition was used with one probe antenna at a time.
+
+For the measurement phase using faded channel conditions, the signal is transmitted via several probe antennas at a time. Therefore, the per-path calibration information gained from the path loss measurements needs to be used to adjust the signal level when using multiple antennas and a fading channel.
+
+Composite loss is the loss between point A and point B. The average channel power is defined as the signal level in the centre of the probe array (location B). The power at location B is the sum of signal powers via a number of calibrated probe antennas. The total power should be determined for each channel model separately. The average channel power at
+
+location B is the Node-B Emulator output power (location A) minus the composite loss. The average channel power level is defined to be the measured power in the centre of the probe array, averaged over 30 seconds, for the selected channel model when a HSDPA link is applied. [An example step by step procedure is necessary to explain how to take the calibrated individual static paths from the calibration phase and turn this into a calibrated composite faded signal at point B. The example step by step procedure will be completed by proponents].
+
+![Diagram illustrating signal level in fading radio channel conditions. A Node-B emulator is connected to a fading emulator at point A. The fading emulator has multiple output paths, labeled i=1, i=2, ..., i=n, each with an antenna. These antennas point towards a single antenna at point B. A bracket labeled 'composite loss' spans from the Node-B emulator output at A to the antenna at B, indicating the total loss in the system.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg)
+
+Diagram illustrating signal level in fading radio channel conditions. A Node-B emulator is connected to a fading emulator at point A. The fading emulator has multiple output paths, labeled i=1, i=2, ..., i=n, each with an antenna. These antennas point towards a single antenna at point B. A bracket labeled 'composite loss' spans from the Node-B emulator output at A to the antenna at B, indicating the total loss in the system.
+
+Figure A.2.2.1-1. Signal level in fading radio channel conditions
+
+## A.3 Test Procedure
+
+The following UE device detail refers only to the COST2100 measurement campaign.
+
+The USB modem will be tested with the provided laptop. Due to practical reasons the lid is kept closed during measurements. The laptop has two USB ports, use the one close to the lid for testing i.e. the higher one. The laptop will be powered by battery and following power management settings should be used:
+
+- Turn off monitor - never
+- Turn off hard disks - never
+- System standby - never
+- WLAN and Bluetooth radios – off
+
+### A.3.1 HSDPA connection settings
+
+Working assumptions:
+
+- 1) HSDPA category 8
+- 2) FRC (Fixed Reference Channel) H-Set 3 (16QAM)
+- 3) Single Link Performance
+- 4) DL channel 10562 is used for testing. Other DL channels can also be used, but this needs to be described in the measurement report.
+
+#### A.3.1.1 FRC
+
+H-Set3 from 34.121-1 is chosen as the FRC. During the FRC tests the behaviour of the Node-B Emulator in response to the ACK/NACK signalling field of the HS-DPCCH is specified in Table A.3.1.1-1.
+
+**Table A.3.1.1-1: Behaviour of Node-B Emulator in response to ACK/NACK/DTX**
+
+| HS-DPCCH ACK/NACK Field State | Node-B Emulator Behaviour                                                             |
+|-------------------------------|---------------------------------------------------------------------------------------|
+| ACK                           | ACK: new transmission using 1 <sup>st</sup> redundancy and constellation version (RV) |
+| NACK                          | NACK: retransmission using the next RV (up to the maximum permitted number of RV's)   |
+| DTX                           | DTX: retransmission using the RV previously transmitted to the same H-ARQ process     |
+
+### A.3.2 Method of test
+
+The average throughput is measured by varying the average channel power by 8 dB either side of the 50% point of the FRC maximum throughput. The example steps for doing that are shown below.
+
+**Table A.3.2-1: Physical channel levels for HSDPA connections set up**
+
+| Parameter During Measurement | Unit | Value |
+|------------------------------|------|-------|
+| P-CPICH Ec/lor               | dB   | -9.9  |
+| P-CCPCH and SCH Ec/lor       | dB   | -11.9 |
+| PICH Ec/lor                  | dB   | -14.9 |
+| HS-PDSCH                     | dB   | -5.9  |
+| HS-SCCH_1                    | dB   | -7.4  |
+| DPCH Ec/lor                  | dB   | -5    |
+| OCNS Ec/lor                  | dB   | -13.3 |
+
+**Table A.3.2-2: Test parameters for testing 16QAM H-set 3**
+
+| Parameter                                            | Unit                                                                                                                                                                            | Test 1    | Test 2 | Test 3 | Test 4 |
+|------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|--------|--------|--------|
+| Phase reference                                      | dBm/3.84 MHz                                                                                                                                                                    | P-CPICH   |        |        |        |
+| Redundancy and constellation version coding sequence |                                                                                                                                                                                 | {6,2,1,5} |        |        |        |
+| Maximum number of HARQ transmission                  |                                                                                                                                                                                 | 4         |        |        |        |
+| NOTE:                                                | The HS-SCCH-1 and HS-PDSCH shall be transmitted continuously with constant power. HS-SCCH-1 shall only use the identity of the UE under test for those TTI intended for the UE. |           |        |        |        |
+
+- 1) Set up fading conditions defined in section A.2.1.1.
+- 2) Establish an HSDPA connection according to subclause A.3.1 with the UE in angular position 0 degrees.
+- 3) Set the SS behaviour according to Table A.3.1.1-1.
+- 4) Set test parameters on the SS according to Table A.3.2-2.
+- 5) Set up number of frames to 5000, and repetition to “Single Shot”.
+- 6) Select inner loop power control algorithm 2, power continuously up.
+- 7) Adjust the average channel power to achieve roughly 50% of the FRC maximum throughput (DUT rotation 0°). Note this power.
+
+Throughput is calculated with the following formula:
+
+$$\text{Throughput} = \text{Transmitted blocks size} \times \text{Number of blocks acknowledged} / \text{Measuring time}$$
+
+- 8) Set the average channel power 8 dB below the level recorded in step 7).
+
+- 9) Measure the throughput of the UE and record in the result in Table A.3.2-3.
+- 10) Increase the average channel power by 2 dB.
+- 11) Repeat steps 9) and 10) until the throughput has been measured at 8 dB above the level in step 7).
+- 12) Rotate the UE by 45 degrees and repeat steps 8 to 11 until all 8 angles have been measured.
+- 13) Calculate the average throughput for each power step.
+
+**Table A.3.2-3: Throughput result table**
+
+| <b>Device:</b>        |                              |              |             |
+|-----------------------|------------------------------|--------------|-------------|
+| <b>Channel Model:</b> |                              |              |             |
+|                       | <b>Average channel power</b> |              |             |
+|                       | <b>[dBm]</b>                 | <b>[dBm]</b> | <b>etc.</b> |
+| Rotation Angle        | Throughput [kbps]            |              |             |
+| 0°                    |                              |              |             |
+| 45°                   |                              |              |             |
+| 90°                   |                              |              |             |
+| 135°                  |                              |              |             |
+| 180°                  |                              |              |             |
+| 225°                  |                              |              |             |
+| 270°                  |                              |              |             |
+| 315°                  |                              |              |             |
+| Average               |                              |              |             |
+
+# Annex B (Informative): LTE MIMO OTA Test Plan
+
+## B.1 Test Objectives
+
+- 1) To measure a set of figure of merits by using the same reference DUTs for the candidate methodologies,
+- 2) To compare the OTA figure of merits results between the candidate methodologies, and
+- 3) To determine and prove whether the candidate test methodology can be used to differentiate a good and bad DUT
+
+## B.2 Test Setup
+
+The test system setup is shown in Figure B.2 for the proposed methodologies in 6.3. For anechoic chamber based methodologies in Figure B.2-1, a number of vertically and horizontally polarized antennas are located on a plane with respect to the DUT. The typical number of antennas is at least eight in a full circle and at least three for a single cluster test. The antenna probes' distance from the DUT,  $r$ , will vary from lab to lab. In the candidate solution 4 typically two antennas will be used. The DUT will be rotated around its centre line by using the electronically-controlled turntable system or using a manual turning approach. The angle of turning is designated as  $\theta$ . An anechoic chamber of sufficient size ( $W \times L$ ) m is used and this will vary from lab to lab. Some uplink signal amplifier may be used to ensure good isolation between Tx and Rx port of eNodeB emulator.
+
+![Figure B.2-1: Anechoic-chamber based methodologies. The diagram shows a test setup inside a 'Fully Anechoic chamber' with dimensions 'L' (length) and 'W' (width). Inside the chamber, there are 'absorber' panels on the walls and a 'Quiet zone' in the center. A 'DUT' (Device Under Test) is mounted on a 'Multi-axis positioner' which can rotate by an angle 'θ'. The DUT is connected to a 'MIMO Fading emulator'. The emulator is connected to a 'Relay switch unit (RSU)', which is connected to a 'Dynamic Range Extender (DRE)'. The DRE is connected to a 'NodeB emulator'. The NodeB emulator is connected to a 'Spectrum Analyzer'. The Spectrum Analyzer is connected to a 'PC running test automation software'. The PC is connected to a 'Signal interface/Bus', which is connected to a 'Positioning controller'. The Positioning controller is connected to the Multi-axis positioner. The diagram also shows several 'Communication antenna' probes arranged in a circle around the DUT at a distance 'r'.](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg)
+
+Figure B.2-1: Anechoic-chamber based methodologies. The diagram shows a test setup inside a 'Fully Anechoic chamber' with dimensions 'L' (length) and 'W' (width). Inside the chamber, there are 'absorber' panels on the walls and a 'Quiet zone' in the center. A 'DUT' (Device Under Test) is mounted on a 'Multi-axis positioner' which can rotate by an angle 'θ'. The DUT is connected to a 'MIMO Fading emulator'. The emulator is connected to a 'Relay switch unit (RSU)', which is connected to a 'Dynamic Range Extender (DRE)'. The DRE is connected to a 'NodeB emulator'. The NodeB emulator is connected to a 'Spectrum Analyzer'. The Spectrum Analyzer is connected to a 'PC running test automation software'. The PC is connected to a 'Signal interface/Bus', which is connected to a 'Positioning controller'. The Positioning controller is connected to the Multi-axis positioner. The diagram also shows several 'Communication antenna' probes arranged in a circle around the DUT at a distance 'r'.
+
+**Figure B.2-1: Anechoic-chamber based methodologies**
+
+Figure B.2-2 shows the setup for the reverberation-chamber based methodologies. Several measurement antennas can be used to transmit the RF signals to the DUT. The DUT is inserted in a position inside the chamber. The mode stirrers are used to create scattering waves that mimic certain propagation conditions. The uplink antennas are used to establish active communication link between the eNodeB emulator and the DUT. A reverberation chamber is equipped with
+
+mode stirrers and can create a statistically isotropic distribution of incoming waves to the UE (User Equipment). When in the isotropic mimic, there are no restrictions for aligning the UE in a certain direction, but the UE must be placed at a minimum distance of 0.7 wavelengths from any other conducting object or RF absorbing material in the chamber. The reverberation chamber may be loaded with absorbing objects in order to tune the power-delay-profile to fit the channel models described below.
+
+![Figure B.2-2: MIMO measurement setup for baseline configuration with reverberation chamber only. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer' (a crossed rectangular object) and a 'DUT' (Device Under Test, a small rectangular object). A 'MIMO link' is indicated by a double-headed arrow between the DUT and the chamber wall. On the right wall, two 'Fixed measurement antennas' are shown, connected by lines to a 'Base station' box outside the chamber.](fb4274c4b7882a4059103f1dbca9b111_img.jpg)
+
+Figure B.2-2: MIMO measurement setup for baseline configuration with reverberation chamber only. The diagram shows a rectangular 'Reverberation chamber' containing a 'Mode stirrer' (a crossed rectangular object) and a 'DUT' (Device Under Test, a small rectangular object). A 'MIMO link' is indicated by a double-headed arrow between the DUT and the chamber wall. On the right wall, two 'Fixed measurement antennas' are shown, connected by lines to a 'Base station' box outside the chamber.
+
+**Figure B.2-2: MIMO measurement setup for baseline configuration with reverberation chamber only. Several measurement antennas can be used to transmit the RF signals to the DUT**
+
+![Figure B.2-2A: MIMO measurement setup for extended configuration with reverberation chamber paired with channel emulator. This diagram is similar to Figure B.2-2 but includes an additional 'Channel emulator' box below the 'Base station'. Both the 'Base station' and the 'Channel emulator' are connected to the 'Fixed measurement antennas' inside the 'Reverberation chamber'.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg)
+
+Figure B.2-2A: MIMO measurement setup for extended configuration with reverberation chamber paired with channel emulator. This diagram is similar to Figure B.2-2 but includes an additional 'Channel emulator' box below the 'Base station'. Both the 'Base station' and the 'Channel emulator' are connected to the 'Fixed measurement antennas' inside the 'Reverberation chamber'.
+
+**Figure B.2-2A: MIMO measurement setup for extended configuration with reverberation chamber paired with channel emulator.**
+
+The measurement setup with reverberation chamber can be combined with a channel emulator to produce more specific power delay profiles. Figure B.2-2A shows the measurement setup with added channel emulator. Configuration of the channel emulator and the reverberation chamber is slightly different from the reverberation chamber alone. Note that the intent is to mimic the channel model created by the emulator as much as possible. Since the chamber introduces its own decaying exponential PDP, the chamber must be tuned to as low a delay spread as possible without compromising the desired statistics. Provisionally, 90 ns has been selected as the target value. For everything else related to the setup in the reverberation chamber, the same considerations as in the previous section about reverberation chamber only should be followed.
+
+For the two-stage methodologies shown in Figure B.2-3, this method divides the MIMO OTA test into two stages:
+
+- 1) Measure the device antenna pattern inside an anechoic chamber. In order to accurately measure the antenna pattern of the intact device, the chipset needs to support amplitude and relative phase measurements of the antennas. Section B.4.3 gives a description on how to measure each antenna element's pattern using a non-intrusive method.
+
+- 2) Use a commercial MIMO channel emulator to convolve the measured antenna pattern with the desired channel model to provide the stimulus for a conducted throughput test on the DUT.
+
+The chamber for antenna pattern measurement is set up as described in Annex A.2 of [4], where the DUT is put into a chamber and each antenna element's far zone pattern is measured. The influence of human body loss can be measured by attaching the DUT to a SAM head and or hand when doing the antenna pattern measurements. The antenna pattern can be measured using non-intrusive methods as described in B.4.3. The integrated channel model with both MIMO antenna effect and the multipath channel effect can then be emulated with a commercial MIMO channel emulator. The Node B emulator is connected to the MIMO channel emulator and then to the MIMO device's temporary antenna ports via approved RF cables. These ports are the standard ones provided for conducted conformance tests. By controlling the power settings of the channel emulator and also the integrated channel model, the end-to-end throughput with the MIMO antenna radiation influence can be measured.
+
+![Figure B.2-3: Two-stage based methodology Test Setup. The diagram illustrates a two-stage test process. In the first stage (top), a BS Emulator is connected to a Test Chamber containing a Reference Antenna and a MIMO DUT surrounded by Anechoic Material. The output from the MIMO DUT in the chamber is labeled 'Antenna Patterns'. In the second stage (bottom), labeled 'Conducted', the 'Antenna Patterns' are fed into a Channel Emulator. This Channel Emulator is connected to a BS Emulator, which in turn is connected to the MIMO DUT. The final output block shows 'BER, FER, H, R'. A red dashed line connects the BS Emulator from the first stage to the Channel Emulator in the second stage.](df1966d80c74bc127f159a48f38b13ee_img.jpg)
+
+Figure B.2-3: Two-stage based methodology Test Setup. The diagram illustrates a two-stage test process. In the first stage (top), a BS Emulator is connected to a Test Chamber containing a Reference Antenna and a MIMO DUT surrounded by Anechoic Material. The output from the MIMO DUT in the chamber is labeled 'Antenna Patterns'. In the second stage (bottom), labeled 'Conducted', the 'Antenna Patterns' are fed into a Channel Emulator. This Channel Emulator is connected to a BS Emulator, which in turn is connected to the MIMO DUT. The final output block shows 'BER, FER, H, R'. A red dashed line connects the BS Emulator from the first stage to the Channel Emulator in the second stage.
+
+**Figure B.2-3: Two-stage based methodology Test Setup**
+
+NOTE: Detailed test setup should be presented together with the measurement results.
+
+![Figure B.2.4: Test setup for antenna pattern measurement in anechoic chamber. The diagram shows an anechoic chamber with blue pyramidal wave absorbers on the walls. Inside, a 'Measurement Antenna' is mounted on a vertical stand, with labels for 'θ-pol' and 'φ-pol'. To the right, an 'EUT' (Equipment Under Test) is mounted on a rotating platform. Two rotation axes are indicated: 'φ - Axis Pos. Direction of Rotation' (vertical axis) and 'θ - Axis Pos. Direction of Rotation' (horizontal axis). A coordinate system (X, Y, Z) is shown near the EUT. Below the chamber, a 'Node B Emulator' is connected via a red line to a 'PC running test automation software'. The PC is also connected to a 'Position Controller' via a 'GPIB' interface. The Position Controller is connected to the rotating platform.](0a73b03fba21af142d619a9a662e6490_img.jpg)
+
+Figure B.2.4: Test setup for antenna pattern measurement in anechoic chamber. The diagram shows an anechoic chamber with blue pyramidal wave absorbers on the walls. Inside, a 'Measurement Antenna' is mounted on a vertical stand, with labels for 'θ-pol' and 'φ-pol'. To the right, an 'EUT' (Equipment Under Test) is mounted on a rotating platform. Two rotation axes are indicated: 'φ - Axis Pos. Direction of Rotation' (vertical axis) and 'θ - Axis Pos. Direction of Rotation' (horizontal axis). A coordinate system (X, Y, Z) is shown near the EUT. Below the chamber, a 'Node B Emulator' is connected via a red line to a 'PC running test automation software'. The PC is also connected to a 'Position Controller' via a 'GPIB' interface. The Position Controller is connected to the rotating platform.
+
+**Figure B.2.4: Test setup for antenna pattern measurement in anechoic chamber**
+
+Set up
+
+- LTE Node B emulator.
+- Anechoic chamber with position controller capable of moving the DUT and antenna probe relative to each other in theta ( $\theta$ ) and phi ( $\phi$ ). Anechoic chamber designed and calibrated to support desired test frequencies.
+- The DUT is capable of measuring complex antenna pattern data (i.e. both magnitude and phase) for both antennas used in the reception of LTE signals. A diagnostic tool may be used to capture the data. Devices that connect to the USB port of the laptop shall be connected directly to a USB port on the left or right side of the laptop.
+- PC running test automation software.
+
+### B.2.1 Figure of Merits (FOMs)
+
+The figure of merits or test parameters in Table B.2.1-1 must be measured.
+
+**Table B.2.1-1: Figure of Merits**
+
+| Category    | I                         |
+|-------------|---------------------------|
+| FOMs        | MIMO Throughput CQI (FRC) |
+| Type        | OTA                       |
+| Methodology | Active (with fading)      |
+
+CQI – Channel Quality Indicator (This FOM is optional but where possible it should be measured)
+
+From the FOMs, the second-order statistics can also be derived to assess the OTA performance of the DUT. For OTA throughput, the PDF and CDF of throughput should be generated.
+
+### B.2.2 Channel Models
+
+The desired radio channel models that can be used for the measurement campaign are described in 6.2. The recommended sub-set of channel models for the measurement campaign is listed below:
+
+For full circle testing:
+
+- SCME Urban micro-cell,
+- SCME Urban macro-cell, and
+
+For single cluster testing:
+
+- Single Spatial Cluster Model with Multi-path based on SCME Urban micro-cell (Angle spread : 35 deg)
+- Single Cluster Multi-Path Model based on Extended Pedestrian A (EPA) (Angle spread : 35 deg)
+
+For uniform model testing:
+
+- Extended Pedestrian A (EPA)
+
+The channel model used in the test is independent of implementation. When/if the sum of sinusoids based implementation of SCME channel models is used, the number of sub-paths per cluster is 20. The Doppler spectrum is based on the geometry (AoA and DoT). The mobile speed of the channel models is 3 km/h.
+
+The candidate solution 4 (two-channel method) does not require a channel model to be applied.
+
+### B.2.3 Antenna Probes
+
+This setup is only applicable to anechoic-chamber based methodologies.
+
+The measurement antennas or antenna probes should be based on orthogonally polarised antennas that are capable of transmitting the vertical and horizontal component of the RF transmitted signals.
+
+Different types of antenna probes can be used, depending on the test methodology. However, antenna probes should be able to support the 3GPP LTE frequency bands, at various centre frequencies. The number of antenna probes needed in an anechoic chamber will depend on the methodology employed.
+
+For measurement campaign purpose, the antenna probes should be calibrated where possible and the following additional information about the antenna probes should be recorded:
+
+- The antenna pattern of the antenna probes.
+- The cross-polarisation of the antenna probes. The cross-polarisation of an antenna probe is defined using Cross Polarisation Purity (AntennaCrossPolarisation). AntennaCrossPolarisation is used to ensure quality/controllability of polarisation effect. The vertical and horizontal gain component of antenna probe can be measured separately or simultaneously to define the XPR. The cross polarisation of the measurement antennas should be  $\geq 20$  dB for the operating carrier frequency.
+- The mutual coupling between vertical and horizontal antenna probe element. The mutual coupling between horizontal and vertical antenna probe element should be minimised (1 dB).
+
+For the round robin measurement campaign, measurements have to be done for horizontal and vertical polarization of the probe antennas. If applicable, mixing polarizations for different antennas is recommended as an additional test. This test will be especially important to verify performance for polarization diversity transmissions.
+
+### B.2.4 eNodeB Emulator Parameter Settings
+
+The eNodeB emulator parameters are set according to the Table B.2.4.1-2. Testing with 64QAM is considered to be done optionally. The settings for DL stream 1 and stream 2 are the same.
+
+**Table B.2.4.1-2: Parameter settings for eNodeB emulator**
+
+| Parameters<br>(Note 1)                     | Unit         | Value                                                                       |                         |
+|--------------------------------------------|--------------|-----------------------------------------------------------------------------|-------------------------|
+|                                            |              | Signal level (Note 2)                                                       |                         |
+| Parameters                                 | Unit         | middle                                                                      | high                    |
+| <b>Physical channel</b>                    |              |                                                                             |                         |
+| Connection mode of UE                      |              | Connection established                                                      |                         |
+| DL MIMO mode                               |              | 2 x 2 open loop spatial multiplexing                                        |                         |
+| Duplex mode                                |              | FDD                                                                         |                         |
+| Operating band<br>(UL channel, DL channel) |              | band 7 (21100, 3100)<br>band 20 (24300, 6300)                               |                         |
+| Schedule tyoe                              |              | Reference Measurement Channel (RMC)                                         |                         |
+| Reference Channel                          |              | R.11 (Note 3)                                                               | not applicable (Note 4) |
+| Bandwidth DL                               | MHz          | 10                                                                          |                         |
+| Number of RBs DL                           |              | 50                                                                          |                         |
+| Start RB DL                                |              | 0                                                                           |                         |
+| Modulation DL                              |              | 16QAM                                                                       | 64QAM                   |
+| TBS Idx DL                                 |              | 13 (RMC defined)                                                            | 24 (RMC defined)        |
+| Bandwidth UL                               | MHz          | 10                                                                          |                         |
+| Number of RBs UL                           |              | 50                                                                          |                         |
+| Start RB UL                                |              | 0                                                                           |                         |
+| Modulation UL                              |              | QPSK                                                                        | 16QAM                   |
+| TBS Idx UL                                 |              | 6 (RMC defined)                                                             | 19 (RMC defined)        |
+| Transmit power control                     | dBm          | -10, open loop (Note 5)                                                     |                         |
+| PDSCH power offset relative to RS EPRE     | dB           | $\rho_A = -3$<br>$\rho_B = -3$                                              |                         |
+| Number of HARQ transmissions               |              | 1 (no HARQ re-transmissions)                                                |                         |
+| AWGN                                       |              | OFF                                                                         |                         |
+| DL power level (RS EPRE)                   | dBm / 15 kHz | Set at eNodeB simulator with correction from calibration                    |                         |
+| Number of subframes for FOM measurement    |              | 2000 minimum for static channel<br>20000 minimum for faded channel (Note 6) |                         |
+
+Note 1: This set of parameters is aligned with R&S CMW500, Anritsu MTC8820C, AT4 S3110B, and Agilent E6621A (to be confirmed).
+
+Note 2: The indications for the signal level to be middle or high are describing the channel conditions under which either a 16QAM or a 64QAM modulation, as selected for the test, usually would be applied.
+
+Note 3: This RMC is defined in 3GPP TS 36.521-1, subclause 8.2.1.3.1
+
+- Note 4: This RMC is not yet given a name in RAN5.
+- Note 5: No uplink power control
+- Note 6: These values might need to be increased for frequency and mobile speed reasons.
+
+### B.2.5 Reference DUTs Configurations
+
+A set of reference DUTs consists of:
+
+- 1) Laptops with LTE embedded modules (not yet available)
+- 2) LTE USB dongles
+- 3) [Other LTE devices with different form factors]
+
+These DUTs are used for the purpose of round-robin measurement campaign.
+
+The reference DUTs shall be treated as commercial off-the-shell MIMO devices.
+
+The test SIM requirement to establish the communication links between DUT and the BS emulator should be provided by each proponent of methodology. The SIMs are only used to set up communication link and therefore it should not impact the measurement results.
+
+Note that the DUTs are usually equipped with RF connectors which allow conducted testing.
+
+#### USB Dongles
+
+For USB dongle or modem type DUTs, a laptop (non-MIMO capable) will be used to connect to them. A spare laptop will also be provided to charge up the battery. The laptop shall be battery powered during the test.
+
+The USB dongle will be tested with the provided laptop. The lid is kept open in a 110 degree position during measurements. Use the USB port labelled for USB connection. The following power management settings should be used:
+
+On the Dell E6400 notebook, the USB port to be used is the upper one on the left side. On the Dell D430 it is the one most to the right side.
+
+| <u>Configurations</u> | <u>Settings</u> |
+|-----------------------|-----------------|
+| Turn off monitor      | never           |
+| Turn off hard disks   | never           |
+| System standby        | never           |
+| WLAN                  | off             |
+| Bluetooth radio       | off             |
+
+For LTE USB dongles that are attached to the laptops for the purpose of measurement, the laptops shall be positioned with respect to the turn-table and anechoic chamber coordinate system as outlined in Appendix L.9 in [9].
+
+For LTE DUT, if the DUT is capable of 90 degrees mechanical mode, then such mechanical mode shall be used if the host laptop allows doing so. Otherwise, the horizontal (0 degree) mechanical mode shall be used.
+
+The support of engineering software for DUTs is not needed during the measurement process of the DUTs.
+
+## B.3 Calibration of Test System
+
+### B.3.1 Calibration Procedure for Anechoic-chamber based methodologies
+
+The calibration procedure is composed of following three steps.
+
+1. Probe power calibration
+2. Channel power calibration
+3. Calibration check
+
+#### B.3.1.1 Probe power calibration
+
+The test system shall be calibrated using the setup in Figure B.3.1-1. The UE is replaced by a reference antenna (shown in green) with known gain characteristics. A CW non-faded calibration signal is fed to one probe at a time and received by the reference antenna. Based on the known properties of the reference antennas, the pathloss from the input of the fading emulator to the UE location will be calculated.
+
+The settings (except fading model) of the channel emulator during the calibration and measurement phases should be identical. The channel model used in the calibration is static propagation conditions (1 tap, no fading, maximum channel output power). Signal is routed to one antenna probe at a time. Each path (antenna probe) is calibrated separately.
+
+![Figure B.3.1-1: Probe Power Calibration Setup. Diagram showing Signal Generator connected to Channel Emulator (Point A), which feeds multiple Probe Antennas inside an Anechoic Chamber. A Reference Antenna (Point B) inside the chamber is connected to a Spectrum Analyzer.](17439b945bd5156395c7ba15bf04f8fb_img.jpg)
+
+```
+
+    graph LR
+        SG[Signal Generator] --> A((A))
+        A --> CE[Channel emulator]
+        CE --> P1[+] 
+        CE --> P2[+]
+        CE --> P3[+]
+        subgraph AC [Anechoic Chamber]
+            P1
+            P2
+            P3
+            RA[Reference Antenna] 
+        end
+        RA --> B((B))
+        B --> SA[Spectrum Analyzer]
+    
+```
+
+Figure B.3.1-1: Probe Power Calibration Setup. Diagram showing Signal Generator connected to Channel Emulator (Point A), which feeds multiple Probe Antennas inside an Anechoic Chamber. A Reference Antenna (Point B) inside the chamber is connected to a Spectrum Analyzer.
+
+**Figure B.3.1-1: Probe Power Calibration Setup**
+
+The calibration steps are given as follows:
+
+- 1) Measure the attenuation between points A and B (shown in Figure B.3.1-1) through the antenna probe. Point A is the input to the channel emulator and point B is the UE location represented by the reference antenna for the first polarization. The reference antenna has to be aligned with the antenna probe in order to have the antenna probe within the main lobe of the reference antenna, and with the correct polarization.
+- 2) Calculate pathloss compensation factor as below:
+
+$$Path_{\text{compensation}_i} = Attn_i - \max(Attn)$$
+
+where
+
+$Path_{\text{compensation}_i}$  is the compensation factor for antenna probe  $i$  to be adjusted by channel emulator.
+
+$Attn_i$  is the measured attenuation via antenna probe  $i$ , and,
+
+$\max(Attn)$  is the highest attenuation over all antenna probes.
+
+- 3) Adjust the channel emulator outputs by the compensation factor.
+- 4) Calculate the pathloss of each route as follows:
+
+$$Pathloss = \max(Attn) - G_{ref\ antenna}$$
+
+where  $G_{ref\ antenna}$  is the reference antenna gain.
+
+- 5) Repeat the above procedure for the other polarization.
+
+#### B.3.1.2 Channel power calibration
+
+During the calibration phase the static propagation channel condition is used with one probe antenna at a time. For the measurement phase using faded channel conditions, the signal is transmitted via several probe antennas at a time. Therefore, the per-path calibration information gained from the pathloss measurements needs to be used to adjust the signal level when using multiple antennas and a fading channel.
+
+The composite loss is the loss between point A and point B, as shown in Figure B.3.1-2. The average channel power is defined as the measured signal power level in the center of the probe array (Point B) using an omnidirectional reference antenna for the vertical or the horizontal polarization respectively. The power at location B is the sum of signal powers via a number of calibrated probe antennas and averaged over 30 seconds. The total power should be determined for each channel model, and polarization separately. The average channel power at Point B is also the eNodeB Emulator output power (Point A) minus the composite loss. The average channel power at the reference antenna for both vertical and horizontal polarization should be set as the target received power respectively, for example -60 dBm for the initial power for each polarization.
+
+![Figure B.3.1-2: Channel Power Calibration Setup. The diagram shows an eNodeB emulator connected to a Channel emulator. The Channel emulator is connected to multiple Probe Antennas inside an Anechoic Chamber. A Reference Antenna is also inside the chamber. The output of the Reference Antenna is connected to a Spectrum Analyzer. A green double-headed arrow labeled 'Composite loss' connects Point A (at the eNodeB emulator) and Point B (at the Reference Antenna).](7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg)
+
+Figure B.3.1-2: Channel Power Calibration Setup. The diagram shows an eNodeB emulator connected to a Channel emulator. The Channel emulator is connected to multiple Probe Antennas inside an Anechoic Chamber. A Reference Antenna is also inside the chamber. The output of the Reference Antenna is connected to a Spectrum Analyzer. A green double-headed arrow labeled 'Composite loss' connects Point A (at the eNodeB emulator) and Point B (at the Reference Antenna).
+
+Figure B.3.1-2: Channel Power Calibration Setup
+
+#### B.3.1.3 Calibration check
+
+In order to verify that each antenna probe has been properly calibrated, a UE sensitivity measurement is performed for each antenna probe using the static propagation channel model. The result of this check can be used to verify that the probe antennas have been properly calibrated.
+
+The test system is configured as in Figure B.1-1 according to the test procedure described in the “**Test Procedure**” section below, but with the following exceptions:
+
+- 1) The channel model is a single tap and non-faded (AWGN) channel.
+- 2) Only one probe antenna is used at a time.
+
+Rotate the UE using an angle step,  $\theta$  of  $45^\circ$  and measure the UE reference sensitivity. For each antenna probe and angle of step,  $\theta$ , and polarization, record the UE reference sensitivity in Table B.3.1-1.
+
+**Table B.3.1-1: Calibration check table**
+
+| Reference sensitivity/Angle | Path 1 [dBm] | Path 2 [dBm] | Path 3 [dBm] | Path 4 [dBm] | Path 5 [dBm] | Path 6 [dBm] | ---- | Path n [dBm] |
+|-----------------------------|--------------|--------------|--------------|--------------|--------------|--------------|------|--------------|
+| $0^\circ$                   |              |              |              |              |              |              |      |              |
+| $45^\circ$                  |              |              |              |              |              |              |      |              |
+| $90^\circ$                  |              |              |              |              |              |              |      |              |
+| $135^\circ$                 |              |              |              |              |              |              |      |              |
+| $180^\circ$                 |              |              |              |              |              |              |      |              |
+| $225^\circ$                 |              |              |              |              |              |              |      |              |
+| $270^\circ$                 |              |              |              |              |              |              |      |              |
+| $315^\circ$                 |              |              |              |              |              |              |      |              |
+| Path Average                |              |              |              |              |              |              |      |              |
+
+$$PathAverage_\theta = 10 * \log 10 \left( \frac{N_\theta}{\sum_\theta 1/10^{(Path_\theta/10)}} \right)$$
+
+where  $\theta$  is the rotation angle,
+
+$N_\theta = 8$  for angle step of  $45^\circ$ , and,
+
+$Path_\theta$  is the recorded reference sensitivity for each angle step  $\theta$ .
+
+The pathloss compensation is considered successful if the path average results are within  $\pm 1$  dB.
+
+### B.3.2 Calibration Procedure for Reverberation-chamber based methodologies
+
+The calibration of reverberation-chamber based methodologies should be based on Appendix E.3 in [11], which has been devised to support SISO-type device OTA measurement.
+
+For MIMO OTA, additional considerations on calibration procedure of reverberation-chamber based methodologies should be made. The S-parameters should be obtained using the standard vector network analyser that can support multiple port connections. These S-parameters are
+
+$$S_{11}(i, n), S_{22}(i, n), S_{21}(i, n) \quad \text{for } n = 1, 2, 3, \dots, N$$
+
+for  $i^{\text{th}}$  measurement antenna installed inside the chamber.  $N$  is the total number of stirrer positions.
+
+During the calibration, several essential parameters should be recorded: Chamber Q-factor or average power received from a lossless antenna, propagation channel-related parameters such as RMC delay, coherence bandwidth and Doppler spread. A proposed calibration setup for reverberation chamber type methodologies is shown in Figure B.3.2-1.
+
+![Figure B.3.2-1: Generic setup for calibration measurement in reverberation chamber. The diagram shows a rectangular reverberation chamber containing a mode stirrer/tuner, a reference antenna, and a fixed measurement antenna. The reference antenna is connected to Port 1 of a vector network analyzer, and the fixed measurement antenna is connected to Port 2 of the same vector network analyzer.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg)
+
+Figure B.3.2-1: Generic setup for calibration measurement in reverberation chamber. The diagram shows a rectangular reverberation chamber containing a mode stirrer/tuner, a reference antenna, and a fixed measurement antenna. The reference antenna is connected to Port 1 of a vector network analyzer, and the fixed measurement antenna is connected to Port 2 of the same vector network analyzer.
+
+**Figure B.3.2-1: Generic setup for calibration measurement in reverberation chamber**
+
+#### B.3.2.1. Tuning Reverberation Chamber to Specific Channel Model
+
+Since the power-delay-profile (PDP) in a reverberation chamber can take the shape of exponential decay, the RMS delay spread is the only parameter needed to characterize the chamber PDP. From calibration data the RMS delay spread of the current setup can be calculated. This should be used to tune the RMS delay spread to what is specified.
+
+For tuning of the reverberation chamber to a specific radio channel condition, the RMS delay spread can be calculated in either of two ways. The first alternative is the direct method where the frequency response of the chamber is Fourier transformed to the time domain and a standard calculation of RMS delay spread is performed on the time domain data. The second alternative is the simplified method where the relationship between RMS delay spread, coherence bandwidth, and average power transfer function of the chamber is used. The relationship between RMS delay spread and average power transfer function of the chamber is given by
+
+$$\sigma_{\tau} = \frac{8\pi f^2 V G_{ch}}{c_o^3}$$
+
+##### B.3.2.2.1 Reverberation Chamber Combined with Channel Emulator
+
+For the case when a channel emulator is used in combination with a reverberation chamber, the total power available for the UE is dependent on the output power available from the channel emulator.
+
+The calibration of the reverberation chamber part of the system should be carried out as stated in the section above about calibration of the reverberation chamber only. The total path loss should then be adjusted so as to appropriately account for the channel emulator path loss.
+
+#### B.3.2.2 Average Path Loss Measurement
+
+Based on Figure B.3.1-3 and Appendix E.3 in TR 25.914 [11], the following calibration procedure can be used:
+
+- 1) Place all objects, which will be used during the measurements, into the RC. These objects could include a head phantom, hand phantom and fixture for the EUT, if applicable. The purpose of this step is to ensure that the loss in the chamber is the same during both calibration and measurements later.
+- 2) Place the calibration or reference antenna inside the RC. The calibration antenna is preferably mounted on a low-loss dielectric fixture, to avoid effects from the fixture itself which may affect the EUT's radiation efficiency and mismatch factor. The calibration antenna must be placed in the chamber in such a way that it is far enough from any walls, mode-stirrers, head phantom, or other object, such that the environment for the calibration antenna (taken over the complete stirring sequence) resembles a free space environment. "Far enough away" depends on the type of calibration antenna used. For low-gain, nearly omni-directional antennas like dipoles it is normally sufficient to ensure that this spacing is larger than 0.5 wavelengths. More directive calibration antennas should be directed towards the center of the chamber.
+
+- 3) Connect the first fixed measurement antenna and measure the S-parameters between port of fixed measurement antenna and the calibration antenna. The network analyser should be calibrated (by manufacturer) so that the S-parameter can be measured accurately.
+- 4) Repeat Step 3 for each stirrer position and carrier frequency.
+- 5) Connect the next fixed measurement antenna and repeat Step 3 – 4.
+- 6) Repeat Step 5 until all the fixed measurement antennas have been installed and calibrated in the chamber.
+
+Note that the frequency dependency of the S-parameters is suppressed in this formulation. The number of stirrer positions  $N$  in the chosen stirring sequence, i.e. the number of S-parameter samples at each frequency point, should be chosen in such a way that it is large enough to yield an acceptable statistical contribution to the total measurement uncertainty. As a guideline it should be in the range of 200 – 400 to ensure that the number of independent samples is not severely limited by the total number of samples measured. The number of independent samples, which is a subset of all samples, determines the statistical contribution to the expanded measurement uncertainty. This should be larger than 100 to ensure an expanded uncertainty less than 1 dB.
+
+Note also that the number of independent samples depends on the frequency, size of chamber, quality of stirrers, the level of loading by absorbing objects, and whether or not frequency stirring is used. A good chamber can provide 100 independent samples down to a lower frequency of operation than a bad chamber. The sequence of moving the stirrers to different positions may be either step-wise (stopping stirrer for each sample) or continuous (sampling on-the-fly). With continuous stirring it may not be possible to characterize the chamber over a wide frequency band at the same time.
+
+An uplink signal amplifier may be required to ensure good isolation between Tx and Rx port of eNodeB emulator.
+
+### B.3.3 Calibration Procedure for 2-Stage methodologies
+
+#### B.3.3.1 Antenna pattern measurement calibration in stage I
+
+The DUT antenna patterns are measured in a calibrated certified anechoic chamber. The anechoic chamber constraints can be found in Annex A.2 in [4]. The preferred measurement is based on the assumption that the chipset in device has the capability to support amplitude and relative phase measurements of the antennas. Less integrated devices such as those providing cabled access to the antenna and receiver After the antenna pattern measurement using non-intrusive methods as described in B.4.3, the antenna pattern absolute gain calibration is carried out by using a reference dipole with known gain to measure the path loss, which means that the path loss is calibrated out from the measured pattern. The detailed path loss  $L_{wavi}$  calibration process is as below, which is from Annex B in [4].
+
+##### Path loss calibration process
+
+$L_{total}$  is the attenuation between P and B, see figure B.3-1.
+
+$$L_{total} = (L_{AB} - L_{AC} + E_{cal})$$
+
+Where  $L_{AC}$  is cable loss from A to B. The cable AC connecting the substitution antenna should be such that its influence upon radiation pattern measurements is minimal.  $L_{AB}$  is the attenuation between points A and B.  $E_{cal}$  is the efficiency or gain of the calibration antenna at the frequency of interest.
+
+![Diagram of calibration/substitution procedures using a vector network analyzer. A Network Analyser with Port 1 (A) and Port 2 (B) is connected to a Calibration antenna (with points P and C) and a Dual-polarized horn antenna inside a blue-walled anechoic chamber. Red lines represent signal paths between the components.](fd3cbb53e991f8209ba17b398f426e13_img.jpg)
+
+Detailed description: The diagram shows a vector network analyzer outside an anechoic chamber. Port 1 (labeled A) is connected via a cable to a dual-polarized high gain antenna inside the chamber. Port 2 (labeled B) is connected via a cable to a calibration antenna mounted on a rotating pedestal. The calibration antenna has reference points P and C. The anechoic chamber is lined with blue pyramidal absorbers. Red curved lines represent the electromagnetic wave propagation between the calibration antenna and the dual-polarized antenna.
+
+Diagram of calibration/substitution procedures using a vector network analyzer. A Network Analyser with Port 1 (A) and Port 2 (B) is connected to a Calibration antenna (with points P and C) and a Dual-polarized horn antenna inside a blue-walled anechoic chamber. Red lines represent signal paths between the components.
+
+**Figure B.3.3.1-1 Calibration/substitution procedures using a vector network analyzer from Annex B in TS 34.114 V.9.0.0**
+
+If the calibration is based on known efficiency of the calibration antenna, a full spherical scanning is performed to determine  $L_{AB}$ .
+
+This procedure has to be done at each frequency of interest.
+
+To achieve measurements with an uncertainty as low as possible, it is absolutely necessary to exactly keep the same P to B configuration (cables, dual-polarized antenna and cables positions, etc).
+
+Calibration shall be performed yearly or if any equipment in the measurement system is changed.
+
+#### B.3.3.2 Antenna pattern change compensation
+
+![Flowchart for antenna pattern change compensation. It shows a 'Channel Emulator' and a 'BS Emulator' connected to a device. Arrows indicate the flow of data: 'Load antenna pattern measured in chamber' into the Channel Emulator, 'Measured antenna pattern after cable connection' from the device, and 'Compare the pattern change' between the two.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg)
+
+Detailed description: The diagram illustrates the process of antenna pattern change compensation. A box on the left labeled 'Load antenna pattern measured in chamber' points to a 'Channel Emulator'. The 'Channel Emulator' is connected to a 'BS Emulator'. A box on the right labeled 'Compare the pattern change' receives input from the 'Load antenna pattern' path and from a box below it labeled 'Measured antenna pattern after cable connection'. An arrow from 'Compare the pattern change' leads down to a box labeled 'Compensate the pattern change'.
+
+Flowchart for antenna pattern change compensation. It shows a 'Channel Emulator' and a 'BS Emulator' connected to a device. Arrows indicate the flow of data: 'Load antenna pattern measured in chamber' into the Channel Emulator, 'Measured antenna pattern after cable connection' from the device, and 'Compare the pattern change' between the two.
+
+**Figure B.3.3.2-1 Calibration antenna pattern change introduced by test platform**
+
+For throughput measurement in stage II, we should calibrate out the antenna pattern change introduced by the test platform. The calibration process is below:
+
+- 1) Set up the conducted throughput test platform as shown in Figure B.3-2.
+- 2) Load antenna pattern measured in chamber into channel emulator, and configure the channel to one Line of Sight (LOS) path without fading.
+- 3) Using device's non-intrusive pattern measurement capability to measure the emulated pattern under this connection and compare this result with the loaded one to get the pattern change introduced by test platform
+
+- 4) Compensate the pattern change from the original pattern file to get the calibrated pattern file, and make sure the measured pattern from this test platform is same as that measured in the chamber. Assume the original pattern measured in chamber is A, and the measured emulated-pattern under cable connection in step 3 is B, then the compensated pattern should be  $A + (A - B)$
+
+#### B.3.3.3 Power calibration for results comparison from different OTA test methods
+
+To meaningfully compare the throughput results for different MIMO OTA test methods, it is essential to ensure the incident power level is independent of the test method. Using the multi-probe test method as an example: the reference power is defined as the total received power on the minimum sphere surface surrounding the DUT antenna. The transmitted power is measured from the  $i^{\text{th}}$  probe antenna over all N antennas as  $P_i$ , and the measured path loss between each probe antenna and the DUT as  $P_{\text{loss}}$  (this method can be found in Vodafone, "Detailed Test Plan of MIMO/multiple receiver antennas OTA measurement campaign for COST2100 and CTIA"). The total received power on the minimum sphere surface surrounding the DUT antenna is  $\sum_{i=1}^N P_i - P_{\text{loss}}$ . To compare the two-stage method results with the multi-probe method, the power at the temporary antenna connectors is set to be the same as would have been received when using the multi-probe method.
+
+### B.3.4 Calibration Procedure for antenna pattern based methodologies
+
+![Figure B.3.4-1: Generic setup for calibration measurement in anechoic chamber. The diagram shows an anechoic chamber with blue wave absorbers on the walls. Inside, a 'Measurement Antenna' is mounted on a black vertical stand on the left, and a 'Substitute Antenna' is mounted on a green vertical stand on the right. A blue double-headed arrow labeled 'A' and 'B' indicates the distance between the two antennas. Below the chamber, a 'Signal Generator' is connected to the Measurement Antenna. A 'PC running test automation software' is connected via a 'GPIB' interface to a 'Position Controller'. The Position Controller is connected to the Substitute Antenna and a 'Power Meter'. The Power Meter is also connected to the Signal Generator.](4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg)
+
+Figure B.3.4-1: Generic setup for calibration measurement in anechoic chamber. The diagram shows an anechoic chamber with blue wave absorbers on the walls. Inside, a 'Measurement Antenna' is mounted on a black vertical stand on the left, and a 'Substitute Antenna' is mounted on a green vertical stand on the right. A blue double-headed arrow labeled 'A' and 'B' indicates the distance between the two antennas. Below the chamber, a 'Signal Generator' is connected to the Measurement Antenna. A 'PC running test automation software' is connected via a 'GPIB' interface to a 'Position Controller'. The Position Controller is connected to the Substitute Antenna and a 'Power Meter'. The Power Meter is also connected to the Signal Generator.
+
+Figure B.3.4-1: Generic setup for calibration measurement in anechoic chamber
+
+- 1) Set up: An anechoic chamber with signal generator, reference antenna supporting the test frequencies of interest, probe antenna as shown in Figure B.3.4-1. Free space path loss from point A to point B can be measured using measurement methods described in CTIA OTA Test Plan version 3.0, section 4 [2].
+
+- 2) The UE is replaced by a reference antenna with known gain characteristics. A CW non-faded calibration signal is fed to the probe antenna and received by the reference antenna. Based on the known properties of the reference antenna, the pathloss from the input of the the UE location will be calculated.
+- 3) Repeat this measurement for both horizontal and vertical polarization path losses and record these values. Use these values to account for the path loss from the Node B emulator to the DUT.
+
+### B.3.5 Calibration Procedure for two-channel method
+
+The calibration in the case of candidate solution 4 (two-channel method) is similar to the calibration of power levels in the SISO case. Attenuation of cables as well as free space attenuation are measured to determine the path loss between an RF output of the eNodeB emulator and the output of an ideally isotropic radiator placed at the centre of the quiet zone. The radiator is co-polarized with the utilized test antenna. The measurement can be achieved using a signal generator, a power meter and a calibrated reference antenna, for example.
+
+The attenuation values obtained by means of this method are then used in the following way:
+
+For the power level at the quiet zone due to antenna 1, the power level of the eNodeB emulator is taken and the total attenuation for that path is subtracted in order to obtain the power level at the UE's position. Since there are usually different paths involved, one for each polarization, the correction for the appropriate polarization has to be taken.
+
+The power level at the quiet zone due to antenna 2 then is set to the same level by adjusting the power level in the eNodeB emulator. The power level going into the first antenna is taken and shifted by the difference in attenuations of the two paths involved.
+
+The resulting uncertainty is determined by the uncertainty of the attenuation measurement and the uncertainty of the eNodeB emulator output.
+
+## B.4 Test Procedure
+
+### B.4.1 Test Procedure 1
+
+The following test procedure is used to measure MIMO throughput and CQI given in Table B.2.1-1. The FOM is measured by varying the average channel power. The steps for doing that are shown below:
+
+- 1) Set up fading test conditions defined in section B.2 and appropriate probe antenna polarizations.
+- 2) Establish an LTE connection according to [12] with the UE in angular position 0 degrees.
+- 3) Ensure and check that the eNodeB emulator behaviour is according to Table B.2.4.1-1.
+- 4) Set eNodeB emulator parameters according to Table B.2.4.1-2 depending on the DUT type.
+- 5) Set up number of subframes to 2000, and repetition to “Single Shot”.
+- 6) Adjust the average channel power to a level approximately 1 dB higher than the point where throughput degradation starts to occur. Record this power level.
+
+Throughput is calculated with the following formula:
+
+$$\text{Throughput} = \frac{\text{Transmitted TBS} \times \text{No. of ACKs}}{\text{MeasurementTime}}$$
+
+- 7) Measure the FOM and record the FOM result in a new row below row #21, as shown in Table B.4.1-1
+- 8) Reduce the power level in steps of 0.5 dB and record the throughput / power levels accordingly, until the throughput value is less than 10 % of the maximum throughput of step 6.
+- 9) Rotate the DUT by  $\theta$  degrees and repeat steps 6 to 8 until all rotation angles have been measured
+- 10) Calculate the average value of the FOM for each power step over all rotation angles.
+
+Table B.4.1-1: Throughput and CQI FOM result table
+
+| Row | Col A          | Col B       | Col C               | Col D    | Col E    | Description                                                                                                                                          |
+|-----|----------------|-------------|---------------------|----------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 1   | Setup ID       |             |                     |          |          | An identifier that indicates the conditions of the test setup; this ID is unique for each measurement result submitted by a company                  |
+| 2   | Lab            | R&S         |                     |          |          | lab where the test has been made (text)                                                                                                              |
+| 3   | ID             | 10001       |                     |          |          | unique identifier of form nnmmmm; nn is the lab, mmmm is consecutive number freely assigned by the lab                                               |
+|     |                |             |                     |          |          | nn (see schedule): 01=R&S, 02=SATIMO, 03=Nokia, 04=EMITE, 05=Bluetest, 06=ETS-Lindgren, 07=Azimuth                                                   |
+|     |                |             |                     |          |          | 08=Spirent, 09=Qualcomm, 10=NTT DCM, 11=Agilent, 12=Huawei, 13=CATR, 14=Samsung                                                                      |
+| 4   | Method         | 2-chan      |                     |          |          | any of anechoic, reverb, 2-chan, 2-stage                                                                                                             |
+| 5   | Ch model       | 0           | TR 37.976 6.2-2     |          |          | Column B may be any of Umi, Uma; 0 means no additional channel model. Column C defines the channel model drop (e.g. specific reference to TR 37.976) |
+| 6   | Test ant.      | 2           |                     |          |          | number of test antennas * polarizations; e.g. 8 dual-pol antennas with 16 signals --> 16                                                             |
+| 7   | Constellations | 10° to 150° | averaged            |          |          | circle, cluster, any other information describing the test antenna constellations                                                                    |
+|     |                |             |                     |          |          | if col C contains "averaged", data are taken for different constellations and are then averaged                                                      |
+| 8   | Polarization   | 4 comb.     | averaged            |          |          | hor, ver, hor+ver (2 signals per antenna), n/a, 4 comb.                                                                                              |
+|     |                |             |                     |          |          | 4 comb: one measurement for each of h+h, h+v, v+h, v+v, and then averaged                                                                            |
+| 9   | Positions      | 7           | averaged or         |          |          | number of UE positions / antenna relocations (typically 8)                                                                                           |
+|     |                |             | elevation & azimuth |          |          | Column C specifies if FoM was averaged over all positions or if the data specifies elevation and azimuth information                                 |
+| 10  | eNodeB         | CMW500      | SW ver              | HW ver   | FW ver   | CMW500, MT8820C, ... Columns C, D, E: SW, HW, FW versions respectively                                                                               |
+| 11  | Modulation     | 16QAM       |                     |          |          | 16QAM or 64QAM, all other parameters as per table B.2.4.1-2 of TR 37.976                                                                             |
+| 12  | Subframes      | 2000        |                     |          |          | number of subframes for averaging the throughput values                                                                                              |
+| 13  | Host           | E6400       | p1                  |          |          | E6400 or D430, col c = p1 (pool 1) or p2 (pool 2) etc.                                                                                               |
+| 14  | UE             | E398        | p1ue2               |          |          | E398 (Huawei) / B3710, B3740 (Samsung GT-...), AL621 (ZTE), ...                                                                                      |
+|     |                |             |                     |          |          | col c: p1ue1=E398, p1ue2=B3740, p1ue4=B3710; p2ue1=E398, p2ue4=B3710, p2ue2=AL621; p3ue1=E398, p3ue2=AL621                                           |
+| 15  | Orientation    | vertical    |                     |          |          | UE arrangement: horizontal, vertical, Styrofoam, see fig.                                                                                            |
+| 16  | UE Ant         | internal    |                     |          |          | internal, external (in this case use col c for additional info like "crosspol", "copolar" etc.)                                                      |
+| 17  | Comments       |             |                     |          |          | short comment or reference to footnote or to other location for additional information                                                               |
+| 18  | Legend         | Huawei E398 |                     |          |          | will be the data set name in the legend                                                                                                              |
+| 19  |                |             |                     |          |          | this row intentionally left blank                                                                                                                    |
+| 20  | Level          | Throughput  | TP rel              | Az. Ang. | Ev. Ang. | Headers for the signal level, throughput, relative throughput, azimuth angle, and elevation angle columns of data                                    |
+| 21  | dBm            | kBit/s      | %                   | degree   | degree   | Units for each column of data                                                                                                                        |
+
+For comparison purposes the same test should be made using an external antenna. The connection to the modem is done by means of short cables. See figure B.4.1-1 how the mounting of the antenna shall be made.
+
+![Figure B.4.1-1: Mounting of external antenna on USB modem. The image shows a white rectangular device, likely a USB modem, connected to a laptop via a black cable. A yellow external antenna is mounted on top of the device using a metal bracket and two screws. The laptop's keyboard is visible in the background.](fbdb9a4a74e70721e19f3d576ba7b651_img.jpg)
+
+Figure B.4.1-1: Mounting of external antenna on USB modem. The image shows a white rectangular device, likely a USB modem, connected to a laptop via a black cable. A yellow external antenna is mounted on top of the device using a metal bracket and two screws. The laptop's keyboard is visible in the background.
+
+**Figure B.4.1-1: Mounting of external antenna on USB modem**
+
+In addition a test in conducted mode has to be made with similar settings, but of course using the much smaller attenuation of the conducted setup.
+
+### B.4.1A Test Procedure 1A (Reverberation Chamber Based Methodologies)
+
+1. Set up the fading conditions defined in Section B.2.
+2. Set the eNodeB behavior according to Table B.2.4.1-2.
+3. Establish a connection according to the settings called for in [12] with the UE placed in the chamber.
+4. Adjust the output power so that the average power available for the UE is equal to [-50 dBm].
+5. Measure the average throughput during a full mode-stirrer sequence, with either step-wise or continuous stirrer movement:
+  - Step-wise stirring: Sample the throughput in each fixed stirrer position by using 50 frames for each sample, then calculate the average over the complete set of samples. The number of samples should be 150 or more.
+  - Continuous stirring: Set the number of subframes to [5000] and make the stirrers to move continuously for as long as it takes to measure the throughput for this number of frames.
+
+Throughput is calculated with the following formula:
+
+$$\text{Throughput} = \text{Transmitted blocks size} \times (\text{Number of blocks acknowledged} / \text{Measuring time})$$
+
+6. Repeat steps 6 and 7, each time with a 2 dB lower output power of the eNodeB until the average throughput is equal to zero or measurement cannot be continued due to disconnection of the UE.
+7. Record the average power setting and the average throughput measurement at each repetition of steps 6 and 7.
+
+### B.4.2 Test Procedure 2
+
+The following test procedure is used to measure TRS/TIS given in Table B.2.1-1. Detailed steps are FFS.
+
+### B.4.3 Test Procedure 3 (Antenna spatial correlation measurement)
+
+The following test procedure is used to measure Spatial correlation, given in Table B.2.1-1.
+
+For the purposes of the antenna amplitude and relative phase measurement the conditions under which the measurements are required to operate are in the received power range of REFSENS + 10 dBm or higher in a static channel with one dominant angle of arrival. The amplitude and phase measurements should be computed from the same period of time which should be sufficient for the result to represent the power and phase of the static signal, with an upper limit of [10] ms is provisionally proposed FFS. An absolute power accuracy of +/- [6] dB is considered sufficient for this study phase investigation and the figure for relative phase accuracy is [2] degrees.
+
+The test setup is according to Figure B.2.4.
+
+#### eNodeB Emulator Parameter Settings
+
+The eNodeB emulator parameters are set according to the type of DUT to be tested.
+
+**Table B.4.3-1: Test Parameters for Channel Bandwidths**
+
+| Test Parameters for Channel Bandwidths |                        |               |     |                      |               |     |
+|----------------------------------------|------------------------|---------------|-----|----------------------|---------------|-----|
+| Ch BW                                  | Downlink Configuration |               |     | Uplink Configuration |               |     |
+|                                        | Mod'n                  | RB allocation |     | Mod'n                | RB allocation |     |
+|                                        |                        | FDD           | TDD |                      | FDD           | TDD |
+| 1.4MHz                                 | QPSK                   | 6             | 6   | QPSK                 | 6             | 6   |
+| 3MHz                                   | QPSK                   | 15            | 15  | QPSK                 | 15            | 15  |
+| 5MHz                                   | QPSK                   | 25            | 25  | QPSK                 | 25            | 25  |
+| 5MHz                                   | QPSK                   | 25            | N/A | QPSK                 | 20            | N/A |
+| 10MHz                                  | QPSK                   | 50            | 50  | QPSK                 | 50            | 50  |
+| 10MHz                                  | QPSK                   | 50            | N/A | QPSK                 | 25            | N/A |
+| 10MHz                                  | QPSK                   | 50            | N/A | QPSK                 | 20            | N/A |
+| 15MHz                                  | QPSK                   | 75            | 75  | QPSK                 | 75            | 75  |
+| 15MHz                                  | QPSK                   | 75            | N/A | QPSK                 | 50            | N/A |
+| 15MHz                                  | QPSK                   | 75            | N/A | QPSK                 | 25            | N/A |
+| 20MHz                                  | QPSK                   | 100           | 100 | QPSK                 | 100           | 100 |
+| 20MHz                                  | QPSK                   | 100           | N/A | QPSK                 | 75            | N/A |
+| 20MHz                                  | QPSK                   | 100           | N/A | QPSK                 | 50            | N/A |
+| 20MHz                                  | QPSK                   | 100           | N/A | QPSK                 | 25            | N/A |
+
+Note 1: Test Channel Bandwidths are checked separately for each E-UTRA band, which applicable channel bandwidths are specified in Table 5.4.2.1-1 of TS36.521-1.  
+Note 2: Depending on E-UTRA band, only the appropriate Uplink RB allocation value according to table 7.3.3-2 is tested per Test Channel Bandwidth. TS36.521-1  
+Note 3: For the DL signal one sided dynamic OCNG Pattern OP.1 FDD/TDD is used.
+
+- 1) Set initial position of DUT with respect to probe antenna.
+- 2) Set up eNode B conditions defined in Table B.4.3-1, as per section 7.3.4.1 of [12].
+- 3) Set the downlink signal level to REFSENS + 45 dB, above reference sensitivity level of DUT.
+- 4) Inner loop power control shall be enabled for the uplink.
+- 5) Establish an LTE connection according to 3GPP 36.521-1 section 7.3.4.2 of [12].
+- 6) Enable the DUT to measure complex antenna pattern data, Received for each DUT receive antenna and the relative phase between the antennas.
+
+The details of the received signal strength and phase measurements are to be elaborated but at this time it is assumed that these are based on the downlink RS as a non-limiting example.
+
+[editor's note: Details for complex antenna pattern data, Received Signal Strength (RSS) and phase and how their obtained are FFS. Further details shall be provided before test plan for this candidate method can progress]
+
+- 7) Rotate the DUT/antenna probe to measure complex antenna pattern data over a spherical space around the DUT. Data points are taken every 3 degrees in theta ( $\theta$ ) and phi ( $\phi$ ).
+- 8) Linearize the RSS pattern measurements using the procedure in section 6.16.2 of [9]. The downlink signal strength in shall be adjusted as needed.
+- 9) Extract the measured complex antenna pattern data per each measured theta ( $\theta$ ) and phi ( $\phi$ ) position.
+- 10) Calculate the antenna correlation coefficient  $\rho_e$ . For each theta ( $\theta$ ) and phi ( $\phi$ ), indexed as i and j for discrete elevation and azimuth positions, the antenna correlation coefficient,  $\rho_e$  can be calculated using the following expressions:
+
+For antenna pair (1, 2),
+
+$$\rho = \frac{R_{12}}{\sqrt{\sigma_1 \cdot \sigma_2}}, \text{ where}$$
+
+$$R_{12} = \sum_{j=1}^{N\phi} \sum_{i=1}^{N\theta} (XPR \cdot E_{\theta 1^{i,j}} \cdot E_{\theta 2^{i,j}}^* \cdot P_{\theta^{i,j}} + E_{\phi 1^{i,j}} \cdot E_{\phi 2^{i,j}}^* \cdot P_{\phi^{i,j}}) \cdot \sin \theta \cdot \Delta \theta \cdot \Delta \phi$$
+
+$$\sigma_1 = \sum_{j=1}^{N\phi} \sum_{i=1}^{N\theta} (XPR \cdot E_{\theta 1^{i,j}} \cdot E_{\theta 1^{i,j}}^* \cdot P_{\theta^{i,j}} + E_{\phi 1^{i,j}} \cdot E_{\phi 1^{i,j}}^* \cdot P_{\phi^{i,j}}) \cdot \sin \theta \cdot \Delta \theta \cdot \Delta \phi$$
+
+$$\sigma_2 = \sum_{j=1}^{N\phi} \sum_{i=1}^{N\theta} (XPR \cdot E_{\theta 2^{i,j}} \cdot E_{\theta 2^{i,j}}^* \cdot P_{\theta^{i,j}} + E_{\phi 2^{i,j}} \cdot E_{\phi 2^{i,j}}^* \cdot P_{\phi^{i,j}}) \cdot \sin \theta \cdot \Delta \theta \cdot \Delta \phi$$
+
+Where:
+
+- XPR = cross-polarization ratio ( $P_V/P_H$ )
+- $P_\theta$  and  $P_\phi$  are the incident field power densities from the assumed channel model
+- $\Delta\theta$  and  $\Delta\phi$  are the measurement angular increments
+- $N\theta$  and  $N\phi$  are the number of angular measurement points in  $\theta$  and  $\phi$  assuming the measurement is made over a sphere of angles.
+- $\theta$  varies from 0 to  $\pi$ , and  $\phi$  varies from 0 to  $2\pi$ .
+
+And the the antenna correlation coefficient is  $\rho_e = \frac{|R_{12}|^2}{\sigma_1 \cdot \sigma_2}$
+
+### B.4.4 Test Procedure 4 (Two-stage throughput)
+
+The following test procedure is used to measure OTA throughput and CQI given in Table B.2.1-1 using the two-stage method.
+
+The FOM is measured by varying the average channel power. Here the power is not the output power from channel emulator, but is the total received power on the minimum sphere surface surrounding the DUT antenna, it does not include antenna gain's influence, which is same as that in multi-probe method and does not require averaging over angle rotation. The steps are shown below:
+
+- 1) Measure the amplitude and phase patterns of each element of the DUT antenna array as defined in B.4.3 and store the results. The path loss calibration as described in section B.3.4 also should be done in this step.
+- 2) Connect the equipment as shown in Figure B.2-3.
+- 3) Load the measured antenna patterns into the channel emulator, and configure the desired MIMO channel model defined in section B.2.
+- 4) Configure the eNodeB emulator and establish an LTE connection according to Vodafone, "Detailed Test Plan of MIMO/multiple receiver antennas OTA measurement campaign for COST2100 and CTIA with the UE.
+- 5) Perform the antenna pattern calibration described in section B.3.2 to compensate the pattern change introduced by the test platform, and make sure after this calibration the emulated pattern from this test platform is same as that measured in step 1)
+- 6) Ensure and check that the eNodeB emulator behaviour is according to Table B.2.3.1-1.
+- 7) Set eNodeB emulator parameters according to Table B.2.3.1-2 depending on the DUT type.
+- 8) Set up number of frames to 5000, and repetition to "Single Shot".
+- 9) Switch on the inner loop power control and ensure power continuously up.
+- 10) Adjust the output power of the channel emulator to achieve roughly 50% of the maximum throughput and record this power level. The reference power, which is defined as the total received power on the minimum sphere surface surrounding the DUT antenna, can be deduced by using this power minus antenna gain and power loss between channel emulator output port and DUT temporary antenna connectors.
+
+Throughput is calculated with the following formula:
+
+$$\text{Throughput} = \frac{\text{Transmitted TBS} \times \text{No. of ACKs}}{\text{MeasurementTime}}$$
+
+Transmit Block Size (TBS): defines the transmitted bit number in each block. If there is a reference power available from a different test method, then perform the reference power calibration as described in B.3.2. In this case the throughput measured for the two-stage method can be meaningfully compared with the throughput for other methods.
+
+- 11) Set the power to 8 dB below the power level used in step 10.
+- 12) Measure throughput and the Channel Quality Indicator (CQI) for each DUT rotation angle in steps of 45 degrees. The DUT rotation is emulated from within the channel emulator by rotating measured antenna pattern.
+- 13) Increase the average channel power by 2 dB and repeat step 12 until measurements have been completed at 8 dB above the power level in step 9.
+- 14) Calculate the average value of the FOM for each power step over all rotation angles.
+
+Table B.4.1-1: Throughput and CQI FOM result table
+
+| Device Model                |            |    |    |     |                |
+|-----------------------------|------------|----|----|-----|----------------|
+| Average channel power [dBm] | P1         | P2 | P3 | --- | P <sub>n</sub> |
+| Rotation Angle              | FOM Result |    |    |     |                |
+| 0°                          |            |    |    |     |                |
+| 45°                         |            |    |    |     |                |
+| 90°                         |            |    |    |     |                |
+| 135°                        |            |    |    |     |                |
+| 180°                        |            |    |    |     |                |
+| 225°                        |            |    |    |     |                |
+| 270°                        |            |    |    |     |                |
+| 315°                        |            |    |    |     |                |
+| Average                     |            |    |    |     |                |
+
+### B.4.5 Test Procedure 5 for two-channel method
+
+The following test procedure is used to measure MIMO throughput and CQI given in Table B.2.1-1. The FOM is measured by varying the PDSCH resource element power controlled via setting the RS EPRE power. The steps are similar to the ones in section B.4.1 but with some changes.
+
+- 1) Set up the paths to the antennas / polarizations to be used for this test, and select an antenna distance ( $\theta_2 - \theta_1$ ).
+- 2) Establish an LTE connection according to [12] with the turntable at  $\phi = 0$  degrees and with antenna 1 at  $\theta_1 = 0$  degrees.
+- 3) Set eNodeB emulator parameters according to Table B.2.4.1-2.
+- 4) Set up number of subframes to 2000, and repetition to “Single Shot”.
+- 5) Adjust the power of PDSCH resource elements to a level approximately 1 dB higher than the point where throughput degradation starts to occur. Record this power level.
+
+Throughput is calculated with the following formula:
+
+$$\text{Throughput} = \frac{\text{Transmitted TBS} \times \text{No. of ACKs}}{\text{MeasurementTime}}$$
+
+- 6) Measure the FOM and record the FOM result.
+- 7) Reduce the power level in steps of 0.5 dB and record the throughput / power levels accordingly, until the throughput value is less than 10 % of the maximum throughput of step 5.
+- 8) Rotate the antennas by  $\theta$  degrees and repeat steps 5 to 7 until all rotation angles have been measured
+- 9) Calculate the average value of the FOM for each power step over all rotation angles.
+
+# Annex C (informative): Change history
+
+| Change history |          |                         |    |     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |       |       |
+|----------------|----------|-------------------------|----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|
+| Date           | TSG #    | TSG Doc.                | CR | Rev | Subject/Comment                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Old   | New   |
+| 2009-03        | R4#50bis | R4-091391               |    |     | Skeleton report                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |       | 0.0.1 |
+| 2009-11        | R4#53    | R4-094953               |    |     | Agreed Text Proposals in RAN4#51bis:<br>R4-092515, "Test Methodology for MIMO OTA", Spirent Communications<br>R4-092438, "Text Proposal for MIMO OTA report", Elektrobrit<br>Editorials: References to RAN4 tdocs are removed                                                                                                                                                                                                                                                                                                                                                                                                                     | 0.0.1 | 0.0.2 |
+| 2009-11        | R4#53    | R4-095027,<br>R4-100926 |    |     | Agreed Text Proposals in RAN4#52bis:<br>R4-093944, "TP for MIMO OTA TR on reverberation chambers methodology", Orange<br>R4-093889, "Text proposal to MIMO OTA TR for two-stage method", Agilent Technologies                                                                                                                                                                                                                                                                                                                                                                                                                                     | 0.0.2 | 0.1.0 |
+| 2010-02        | R4#54    | R4-100997               |    |     | R4-094266, "MIMO OTA Text Proposal - 2 channel method", Rohde&Schwarz                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.1.0 | 0.2.0 |
+| 2010-05        | R4#55    | R4-102194               |    |     | Agreed Text Proposals in RAN4 AH#2 and RAN4#55:<br>R4-101833, "Revised skeleton of MIMO OTA TR 37.976", Vodafone.<br>R4-101834, "Revised TPs for MIMO OTA TR 37.976: Figure of Merits", Vodafone.<br>R4-101835, "Revised TPs for MIMO OTA TR 37.976: Operators Requirements", Vodafone.<br>R4-101978, "MIMO-OTA TR text update", Spirent Communications.<br>R4-101437, "Revised MIMO OTA work plan", Vodafone.<br>R4-091405, "MIMO OTA work plan", Vodafone.                                                                                                                                                                                      | 0.2.0 | 0.3.0 |
+| 2010-05        | R4#55    | R4-102246               |    |     | Agreed text proposals:<br>R4-100381, "Text proposal to MIMO OTA TR for RF-controlled spatial fading emulator", Panasonic, Tokyo Institute of Technology<br>R4-101979, "MIMO OTA Channel Models", Spirent Communications, Elektrobrit, Agilent Technologies, NTT-DoCoMo<br>R4-102207, "MIMO-OTA TP to TR 25-series MIMO OTA technical report (SNR definition)", Agilent Technologies<br>R4-102237, "Text proposal for 37.976: CE+RC Methodology", Azimuth Systems<br>R4-102242, "Text Proposal: MIMO OTA Methodology Comparison", Spirent Communications, Agilent Technologies, Qualcomm Incorporated, Elektrobrit, Rohde&Schwarz, Azimuth Systems | 0.3.0 | 1.0.0 |
+| 2010-05        | R4#55    | R4-102357               |    |     | Agreed text proposal (via email approval):<br>R4-102241, "TP: Test Plan for Anechoic Chamber based MIMO OTA methods", Elektrobrit, Nokia, ETS-Lindgren, SATIMO, Spirent Communications, Agilent Technologies, Rohde&Schwarz, NTT DOCOMO, LG Electronics                                                                                                                                                                                                                                                                                                                                                                                           | 1.0.0 | 1.1.0 |
+| 2010-12        | R4#57    | R4-104803               |    |     | Updates for MIMO OTA Study Item TR37.976 v1.1.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 1.1.0 | 1.2.0 |
+| 2010-12        | R4#57    | R4-104883               |    |     | Updates for MIMO OTA Study Item TR37.976 v1.1.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 1.1.0 | 1.2.0 |
+| 2010-12        | R4#57    | R4-104950               |    |     | Revised LTE MIMO-OTA test plan                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | 1.1.0 | 1.2.0 |
+| 2011-01        | R4#57bis | R4-110525               |    |     | TR 37.976 v1.2.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | 1.2.0 | 1.2.1 |
+| 2011-01        | R4#58    | R4-111529               |    |     | TP Addition of test procedures for antenna-based metrics                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | 1.2.1 | 1.3.0 |
+| 2011-03        | R4#58-AH | R4-11930                |    |     | Incorporates the TPs approved in R4#58<br>R4-110645, "TP to TR 37.976, detailing the two-channel method", Rohde & Schwarz<br>R4-111616, "TP to TR 37.976, changes to Annex B, eNodeB settings", Elektrobrit, Rohde & Schwarz, NTT DoCoMo, Vodafone<br>R4-111645, "TP Addition to Antenna Pattern based Test                                                                                                                                                                                                                                                                                                                                       | 1.3.0 | 1.4.0 |
+
+|         |       |           |   |   |                                                                                                                                                                                                                                                                                                                                                                                                                                                       |        |        |
+|---------|-------|-----------|---|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|
+|         |       |           |   |   | Procedure", Qualcomm Incorporated, Agilent<br>R4-111650, "TP to TR 37.976, additions and corrections to<br>Section 3.3 and Annex B", Rohde & Schwarz<br>R4-111690, "TP for 37.976: LTE MIMO OTA Test Plan for<br>Reverberation Chamber Based Methodologies", Azimuth<br>Systems, Bluetest, CTTC<br>R4-111681, "TP for TR37.976, corrections to Annex B",<br>NTT DOCOMO<br>R4-111682, "TP: Text update for MIMO OTA candidate<br>solution", Elektrobit |        |        |
+| 2011-05 | R4#59 | R4-112505 |   |   | Agreed Text Proposals:<br>R4-112218, "MIMO OTA work plan update ", Vodafone,<br>NTT DoCoMo, Orange                                                                                                                                                                                                                                                                                                                                                    | 1.4.0  | 1.5.0  |
+| 2011-11 | R4#61 | R4-115903 |   |   | Agreed Text Proposal:<br>R4-114724, "TP for defining the format of LTE MIMO OTA<br>round robin data" Intel Corporation                                                                                                                                                                                                                                                                                                                                | 1.5.0  | 1.6.0  |
+| 2012-02 | R4#62 |           |   |   | Version 1.7.0 withdrawn                                                                                                                                                                                                                                                                                                                                                                                                                               |        |        |
+| 2012-02 | R4#62 | R4-121108 |   |   | Agreed text proposals from RAN4 #62:<br>R4-120998 "TP for 3GPP TR 37.976 V1.6.0"<br>The applicable Release is changed from 10 to 11.                                                                                                                                                                                                                                                                                                                  | 1.6.0  | 1.8.0  |
+| 2012-03 | RP-55 | RP-120271 |   |   | Presentation to RAN for approval                                                                                                                                                                                                                                                                                                                                                                                                                      |        | 1.8.0  |
+| 2012-03 | RP-55 | RP-120271 |   |   | Approved by RAN55                                                                                                                                                                                                                                                                                                                                                                                                                                     | 1.8.0  | 11.0.0 |
+| 2014-09 | SP-65 | -         | - | - | Update to Rel-12 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                        | 11.0.0 | 12.0.0 |
+| 2016-01 | SP-70 | -         | - | - | Update to Rel-13 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                        | 12.0.0 | 13.0.0 |
+| 2017-03 | RP-75 | -         | - | - | Update to Rel-14 version (MCC)                                                                                                                                                                                                                                                                                                                                                                                                                        | 13.0.0 | 14.0.0 |
+
+| Change history |         |      |    |     |     |                                |             |
+|----------------|---------|------|----|-----|-----|--------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version |
+| 2018-09        | RAN#81  |      |    |     |     | Update to Rel-15 version (MCC) | 15.0.0      |
+| 2020-06        | RAN#88  | -    | -  | -   | -   | Update to Rel-16 version (MCC) | 16.0.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37977/00c19bd8502c529040b374841106f2c3_img.jpg b/marked/Rel-16/37_series/37977/00c19bd8502c529040b374841106f2c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bf7559784e4f7757f0fcfd975b1b74d9d6f03880
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/00c19bd8502c529040b374841106f2c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13d7612f00e8e2f6265a71d5d894e024c0b56093e6b8c6787deb454f445af48d
+size 97135
diff --git a/marked/Rel-16/37_series/37977/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg b/marked/Rel-16/37_series/37977/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3523a849bdc146c340ee7c297873706fb6643af2
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/00f2e7c3d8a12df65c41a981bad8d89d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ea6a48c07488eba450e40a0e17bfe52c8ffc71146ffa28501fd1624a17f011aa
+size 68169
diff --git a/marked/Rel-16/37_series/37977/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg b/marked/Rel-16/37_series/37977/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f612dc1638e67e07cca0925138dbc0c3810da905
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/010f64870d9b7d9e04dc4059b1cf5f45_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5ad90f21fb78b847702e08387c9363f9a3b074dc8e107d53bb69de699248240
+size 60324
diff --git a/marked/Rel-16/37_series/37977/0892c0cb3b8502a44c4fe4e786be912a_img.jpg b/marked/Rel-16/37_series/37977/0892c0cb3b8502a44c4fe4e786be912a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..11b5c4bf77f2c52d7e880738eb2c9a681a230f62
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0892c0cb3b8502a44c4fe4e786be912a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3810d10d5f11442e574bf6f00593782f15e0d5e4a3364ce59824a01d426d51ba
+size 74971
diff --git a/marked/Rel-16/37_series/37977/09b5a76dd3d981abcc585df1314ef30a_img.jpg b/marked/Rel-16/37_series/37977/09b5a76dd3d981abcc585df1314ef30a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5d39e849d296dde8bfc63b4e2efbe43b4f23bd8a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/09b5a76dd3d981abcc585df1314ef30a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:76d2c0bced51abfb46737d8cd189e385bf408f9a21d5b26b9af5c2a1ebc91e84
+size 87932
diff --git a/marked/Rel-16/37_series/37977/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/37_series/37977/0a73b03fba21af142d619a9a662e6490_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6ce7f01b30a307ec28c3f8bb832e1696d31f4b4
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0a73b03fba21af142d619a9a662e6490_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a7c88d7f5eac125c406d47f4b3e699d99e426a9f88d2452bbdfaa18c5089984
+size 26912
diff --git a/marked/Rel-16/37_series/37977/0ba76cf9e44e2bdf70c30182f7990ce7_img.jpg b/marked/Rel-16/37_series/37977/0ba76cf9e44e2bdf70c30182f7990ce7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..766273a7c60f43320608c9c45c8cb2b6a3211a55
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0ba76cf9e44e2bdf70c30182f7990ce7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cff4c10ee15afca01ff07e1df87489d4ffa52176606614d516dc365d5c4c0e9b
+size 50702
diff --git a/marked/Rel-16/37_series/37977/0c1dec10830679ed9dab2f0cd5c3d313_img.jpg b/marked/Rel-16/37_series/37977/0c1dec10830679ed9dab2f0cd5c3d313_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..252156613d544226c61baf00ead1571d8dcda2ba
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0c1dec10830679ed9dab2f0cd5c3d313_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:94258a13e15f3702fcc0f59a1f0308711522535a4c2a1a6da0c0c6bb7ed26e22
+size 51854
diff --git a/marked/Rel-16/37_series/37977/0da08ff31b255c351a205a58b94b3635_img.jpg b/marked/Rel-16/37_series/37977/0da08ff31b255c351a205a58b94b3635_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fa802f5990afbfeaffcc7cad287d427035f6ba2a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0da08ff31b255c351a205a58b94b3635_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3bcdedc6144465696f61d341a72f335cc275cf9acfffacfac7eca5f1d1f70bb5
+size 45158
diff --git a/marked/Rel-16/37_series/37977/0e0257d43c47df039e9755c59674c2e5_img.jpg b/marked/Rel-16/37_series/37977/0e0257d43c47df039e9755c59674c2e5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..575bef35fd163c632e27d2fc7b90c3fce1fc197e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/0e0257d43c47df039e9755c59674c2e5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aec6917711806a59b99c46c94c965610081e5bc6606d6d207257002596b1eda3
+size 96813
diff --git a/marked/Rel-16/37_series/37977/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg b/marked/Rel-16/37_series/37977/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..33886b6ce17dc13a55ea07a65368ff5aa2ce2de9
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:047f344f9822992fe401abb1368463230c3fcd5beee2c2776784bb2d927f4a8c
+size 45612
diff --git a/marked/Rel-16/37_series/37977/10f1d65dbabe0b2d04537846a6c0e1ed_img.jpg b/marked/Rel-16/37_series/37977/10f1d65dbabe0b2d04537846a6c0e1ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..63f756a07e799f3ee3e2cd5d5625d6d3a4492eba
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/10f1d65dbabe0b2d04537846a6c0e1ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:376f0553a41bf70b9adccd945f9e5ef54ffac4e09cb159f3951ed8cc95c21373
+size 49143
diff --git a/marked/Rel-16/37_series/37977/117f43cb271793ec681551c4fdd92cf0_img.jpg b/marked/Rel-16/37_series/37977/117f43cb271793ec681551c4fdd92cf0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9de5b7a483e1987fd070a25f05a46ff7a5f25d5a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/117f43cb271793ec681551c4fdd92cf0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1821c804f2723a0b2c51c702059e55e3ea2161efb9ad5aca8e08ef938e8aed0
+size 62137
diff --git a/marked/Rel-16/37_series/37977/12b521317c2c8ea33a1382d83e2b76be_img.jpg b/marked/Rel-16/37_series/37977/12b521317c2c8ea33a1382d83e2b76be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d96a9aad4f6332ba070e2448280611c1dc1d47d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/12b521317c2c8ea33a1382d83e2b76be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bbeae7e50b282949b9e56aeb07f562d8561dd0d36013a2c837bbd4c83d03e6a5
+size 65795
diff --git a/marked/Rel-16/37_series/37977/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg b/marked/Rel-16/37_series/37977/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ecda76041f2093fd8cc6e163740f2fda3b0aa23a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/15d97ee42b0c3d8c1c45245583d67ff1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf709c47a83220540f24aa641bb26781ed4426cce6ae2b47626a531dead82f5e
+size 55417
diff --git a/marked/Rel-16/37_series/37977/18fcacec609d0fd4816b30201438a00a_img.jpg b/marked/Rel-16/37_series/37977/18fcacec609d0fd4816b30201438a00a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2ef560e2cab98bc2c2b258d7ce48228d3831e9a2
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/18fcacec609d0fd4816b30201438a00a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fb8e604be7ac83091f2044c86f181ae228576ae2ccd0f8d44acb6e321c7c32a8
+size 81549
diff --git a/marked/Rel-16/37_series/37977/2333c01db80c100fb3f8467a0717d99d_img.jpg b/marked/Rel-16/37_series/37977/2333c01db80c100fb3f8467a0717d99d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d110deae89f1288376a224116bb4423252c1c33e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/2333c01db80c100fb3f8467a0717d99d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d6369c86eb990cf663c9b0f77283fa040bf510137b215f0e67341448bd23699
+size 82433
diff --git a/marked/Rel-16/37_series/37977/26489d838b18f7c0321fc12ed839dab2_img.jpg b/marked/Rel-16/37_series/37977/26489d838b18f7c0321fc12ed839dab2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cba797fa4cd6b8c7cbf44f2be65912b184b2646e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/26489d838b18f7c0321fc12ed839dab2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cfc24cba1867e66049052ceeaf7458be0d4783406ce7c7fe94d11d489643b2e5
+size 69098
diff --git a/marked/Rel-16/37_series/37977/26e4d6ae09790488a51e9171a1df0357_img.jpg b/marked/Rel-16/37_series/37977/26e4d6ae09790488a51e9171a1df0357_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0de4142b7da75cee1f82921973ccdfe712b1ab5b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/26e4d6ae09790488a51e9171a1df0357_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5f27669a38b7bebd9ad2c15ac62e2340edb215b0c1264d1905c45a4f5a810f73
+size 42183
diff --git a/marked/Rel-16/37_series/37977/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg b/marked/Rel-16/37_series/37977/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea7e5c7fcf522c76a578d8c382b0661a96d043bc
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fea20b248b44bd2a89d966964e25f29f695dffc1072fe4f2d33b512797a75a99
+size 83917
diff --git a/marked/Rel-16/37_series/37977/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/37_series/37977/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1a988770e8a9f95ae0f5d2a2d88fdd0268ece988
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acf3dabd25c22f00e9be05e8d5ecd2bdaa8ff077aacc7483a14e077f371a3a44
+size 56905
diff --git a/marked/Rel-16/37_series/37977/2b56a53620616729fb852d9ac827e8bd_img.jpg b/marked/Rel-16/37_series/37977/2b56a53620616729fb852d9ac827e8bd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7e13e9336182cb5cf07d17b1cd06112637a40665
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/2b56a53620616729fb852d9ac827e8bd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3e86296dd4f4ca580c5aefdbd65bd353cbe16adcf8c06f27e4621f7b7f023e07
+size 29156
diff --git a/marked/Rel-16/37_series/37977/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg b/marked/Rel-16/37_series/37977/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bab26b337fc33d2d82996a42135db7e883901f20
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/2c5884241ad393e03dd8e4ea25ff74a2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6bef82d9ca65aefa4bb435af55ad789e732983f415e5dee584ebd627c23ffd5f
+size 39657
diff --git a/marked/Rel-16/37_series/37977/2df1e34671c73d7c0d047d4e9009251e_img.jpg b/marked/Rel-16/37_series/37977/2df1e34671c73d7c0d047d4e9009251e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f55c1922cbc5ea9bd65c7f528686c66a4d74eac1
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/2df1e34671c73d7c0d047d4e9009251e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7bd2f4b3a3fd01bf673d873617b52203126149a162d667c23156f831d35d45f4
+size 41659
diff --git a/marked/Rel-16/37_series/37977/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/marked/Rel-16/37_series/37977/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..73065b1f2f50b2bce4121bf5c58ea79651114d9f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4870d09b69eeb60a85db9b2ab5c390e078e87e382a36c9a83e7872b454b73806
+size 42751
diff --git a/marked/Rel-16/37_series/37977/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-16/37_series/37977/356eb99ab9489bbd647223390a913903_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08b90c9b672c2a77bd1d3d55444a1c3127fddc21
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/356eb99ab9489bbd647223390a913903_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0c6b9785f03ff583f800440d37262ef5bf13efc0dee2fbb3ba4e90d4cc834995
+size 19760
diff --git a/marked/Rel-16/37_series/37977/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg b/marked/Rel-16/37_series/37977/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..be3f5abbb75cb22003efafbd9c3ff612089f1841
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08174da40423b9dfcbd885dc65c34ab6c52c9ff0f62dd2e39e1a60e01186f123
+size 96215
diff --git a/marked/Rel-16/37_series/37977/37871b402d58e7fc0bbae75a4ba6650f_img.jpg b/marked/Rel-16/37_series/37977/37871b402d58e7fc0bbae75a4ba6650f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f5f9ca90ec11853c08e1c1aa5fa9546410b8a791
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/37871b402d58e7fc0bbae75a4ba6650f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bc40d3882c2cef45416a49ddd3cd867ab60e92533d1c7ea528f86d5b94751cb9
+size 37773
diff --git a/marked/Rel-16/37_series/37977/38630b597138d11a54ca4d4032eb428d_img.jpg b/marked/Rel-16/37_series/37977/38630b597138d11a54ca4d4032eb428d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9628eaf44c97c50324fb3824ad5e2164232dc122
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/38630b597138d11a54ca4d4032eb428d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51012d83872ee39b7ea65a8dd10ea62c7aa5e88cef0110c8fca3318287779611
+size 48339
diff --git a/marked/Rel-16/37_series/37977/3881b390d52f27a35faedfc170916c86_img.jpg b/marked/Rel-16/37_series/37977/3881b390d52f27a35faedfc170916c86_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aba66833847b243793c75a67e652bedfbb195031
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/3881b390d52f27a35faedfc170916c86_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90508099c2400a75f502c303460f0a484d3a5084f78aae31989d9a18de8194c0
+size 78789
diff --git a/marked/Rel-16/37_series/37977/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/37_series/37977/38d82ffe820e339811b396206f40a201_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3493680a14813859b8400012361970319e6f0dcb
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/38d82ffe820e339811b396206f40a201_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:74ea6152dcfc5743eafe8583d4fddead24f9a076690d95a3732c72f238e23d51
+size 130642
diff --git a/marked/Rel-16/37_series/37977/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg b/marked/Rel-16/37_series/37977/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2dc057b227fe6a8493656946ffc7f4249da73281
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eefa6bdf5f5cc2b3aaf34facd78adc9b2b073dba451a2db21bfed63849dec7a2
+size 95408
diff --git a/marked/Rel-16/37_series/37977/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/37_series/37977/3b00a61116faef21d3a6009fd350b46a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0ff5653d897648a97a6df599951e2a36cc41b3b8
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/3b00a61116faef21d3a6009fd350b46a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1224b719a8f5e2f8e87cdb6b090ba0c044e45d57e4dbf9619c0a12e1c0506b60
+size 60954
diff --git a/marked/Rel-16/37_series/37977/3bc294250861a15a143cdcf2b8297fd1_img.jpg b/marked/Rel-16/37_series/37977/3bc294250861a15a143cdcf2b8297fd1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..56ace7885b0536a0c03a1003e38104b83d85592f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/3bc294250861a15a143cdcf2b8297fd1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:197029c479ddb35379c2560663e78cecbff9205c60c4fdfd9a2dafbb999949d3
+size 36138
diff --git a/marked/Rel-16/37_series/37977/3d6d0738981fdd03d003cc653bdfdaae_img.jpg b/marked/Rel-16/37_series/37977/3d6d0738981fdd03d003cc653bdfdaae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3d8a782ad850de9279e2c13eef96faa71ff2c284
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/3d6d0738981fdd03d003cc653bdfdaae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6331df8e9596f434db9f34f2852f37c4a5c3cc2e08a228cbb79065f7aa82dc15
+size 41786
diff --git a/marked/Rel-16/37_series/37977/3e79b23ceef44b802985f19098824e62_img.jpg b/marked/Rel-16/37_series/37977/3e79b23ceef44b802985f19098824e62_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b5f526c0bf1e5f4c5ccb7f2029eefd4e24b7327f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/3e79b23ceef44b802985f19098824e62_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c633db3ac920c759a2fd36ed18fd93d6d5bc95346c23548e0c354e6d1370993a
+size 58198
diff --git a/marked/Rel-16/37_series/37977/4225405c542ca18957be6328721b7386_img.jpg b/marked/Rel-16/37_series/37977/4225405c542ca18957be6328721b7386_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f9db4cf78e65d0a3a250dd75fa3ef38474f8edd2
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/4225405c542ca18957be6328721b7386_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:112d62866c58ccf7cacb287c14f16e02c2bd55438a88eec36172876325c25813
+size 93131
diff --git a/marked/Rel-16/37_series/37977/440236efe61277b409f0f16c982945c4_img.jpg b/marked/Rel-16/37_series/37977/440236efe61277b409f0f16c982945c4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2fcb236c2d561f45cfe74a1aa1b16fdb49c2f280
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/440236efe61277b409f0f16c982945c4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b25d327e9a7d68a87f1d9125d7004e0d52366e81ac376cfbeb94fb0ab4bc343b
+size 41585
diff --git a/marked/Rel-16/37_series/37977/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg b/marked/Rel-16/37_series/37977/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e15007442e90da3d26c69ff7be47b2534ea90378
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/449dd9d482c5b47f1c013ce3e18b09e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6eb7b2ad8e5194733967492361e8248b3ed94e3bddf1fb9f8e837f5797fd5612
+size 163862
diff --git a/marked/Rel-16/37_series/37977/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-16/37_series/37977/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..35e044a26dbebc10346c13202a946ef7dfa6b343
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/458fdbcb4015a4ee90bd84809afc4aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dbe1e848994c93e18db44c10b91db22c132b451ab00a5feb35b84b2cebade377
+size 22359
diff --git a/marked/Rel-16/37_series/37977/45ab13a475fe6b64200c003830b2a51c_img.jpg b/marked/Rel-16/37_series/37977/45ab13a475fe6b64200c003830b2a51c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..80d28ecdc683fc182b832e7756db368930f774ae
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/45ab13a475fe6b64200c003830b2a51c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7cb23f9ce468fad44460ec7c2811beeb3e42e0022bef06dbeeeb50c9b231158d
+size 94115
diff --git a/marked/Rel-16/37_series/37977/475c496c4cd20198211aeaa241af7279_img.jpg b/marked/Rel-16/37_series/37977/475c496c4cd20198211aeaa241af7279_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cb3ed8277820947db1034d163b9e6e00c2e2904
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/475c496c4cd20198211aeaa241af7279_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7fb30837c5764c345b74f1180153d54dcee5676b448502d24ac9e9bc862d88e4
+size 107219
diff --git a/marked/Rel-16/37_series/37977/4c617a4f2bf25b6cee75c21d6b15136e_img.jpg b/marked/Rel-16/37_series/37977/4c617a4f2bf25b6cee75c21d6b15136e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0adbdfb6612b21bc03cc1159df273339005ffe5
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/4c617a4f2bf25b6cee75c21d6b15136e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8312df809df2a0de0f72f198370b02026f12030a49a1f745b4c577071e0e9190
+size 96372
diff --git a/marked/Rel-16/37_series/37977/4f7470055bfc22c4aa6b007a4056940e_img.jpg b/marked/Rel-16/37_series/37977/4f7470055bfc22c4aa6b007a4056940e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4c70d58e31bd0068409b7a6da766e86c1f5dd501
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/4f7470055bfc22c4aa6b007a4056940e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ef035152c81befff489f39e5fe002669c096dc3bcc05679872c118cf37f6e6a6
+size 44290
diff --git a/marked/Rel-16/37_series/37977/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-16/37_series/37977/4ff00a489baaa34a0c01070de1d613db_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6e7fe070f095faea89ea47cb72b27bbfd41325b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/4ff00a489baaa34a0c01070de1d613db_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67bf74542a1b936feb06a5f260905e98dd0ba95778c7611eed62124af73232c1
+size 22513
diff --git a/marked/Rel-16/37_series/37977/53d8bef47c63e0897de4cd058bad2cbd_img.jpg b/marked/Rel-16/37_series/37977/53d8bef47c63e0897de4cd058bad2cbd_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c712159c0f5454d2719d43805ceadf5631ffc351
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/53d8bef47c63e0897de4cd058bad2cbd_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:942f83a52d6b90d41ca10d747d2bf98cdb93024ab4305c1bd0bd0fbe15d93851
+size 86514
diff --git a/marked/Rel-16/37_series/37977/55fb58e14ec092ccc4fe111de0dc6278_img.jpg b/marked/Rel-16/37_series/37977/55fb58e14ec092ccc4fe111de0dc6278_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9f4bd635dca901325c71f21719d31e86ea75539b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/55fb58e14ec092ccc4fe111de0dc6278_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f6cc88a87be579418604a9a181ea7067963f3cd27c20e014f7e7d06bb9189a28
+size 19073
diff --git a/marked/Rel-16/37_series/37977/56bd052546d4b5a5eb90bc8235ab4c81_img.jpg b/marked/Rel-16/37_series/37977/56bd052546d4b5a5eb90bc8235ab4c81_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..450c73b0d033505ef7eda1af08a3e058ef4e92a3
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/56bd052546d4b5a5eb90bc8235ab4c81_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:711daacfce426a610f09b5dd37271872a271dac6965d4b19048d91d5f7e13fce
+size 28178
diff --git a/marked/Rel-16/37_series/37977/572db3880dc9cf651443b610d82ea66b_img.jpg b/marked/Rel-16/37_series/37977/572db3880dc9cf651443b610d82ea66b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d6e22eead804d08a371b6dcf746de778d84b7212
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/572db3880dc9cf651443b610d82ea66b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:065826e22c35c1b3b3c82999e07edc2cb69e0b76d0542881b03b13b6b77437dc
+size 67346
diff --git a/marked/Rel-16/37_series/37977/578d2763eaf3edf3f1bd6657455ad54a_img.jpg b/marked/Rel-16/37_series/37977/578d2763eaf3edf3f1bd6657455ad54a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1efd27a408a91b4de78360d320c880c6105ff10
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/578d2763eaf3edf3f1bd6657455ad54a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:01a6f213873354836876da64241b3c29e125e26a9df6d2d861f6cd92b0013e6a
+size 61417
diff --git a/marked/Rel-16/37_series/37977/5ae38ef48a8b04f4e6ad410da4555172_img.jpg b/marked/Rel-16/37_series/37977/5ae38ef48a8b04f4e6ad410da4555172_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aaad542cfe9f65b56e98df630898517848b9f5d0
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/5ae38ef48a8b04f4e6ad410da4555172_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:12f470acc4df5e673c5f93277f1386bd8e30159a4e0a2f866ef855f279b202ff
+size 82939
diff --git a/marked/Rel-16/37_series/37977/5b9706ecd40852e908c7d9280f9e212a_img.jpg b/marked/Rel-16/37_series/37977/5b9706ecd40852e908c7d9280f9e212a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b7a4f0cbd616f8c02194851a55f8e1866fb6a9b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/5b9706ecd40852e908c7d9280f9e212a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33c6ab209f983b187323393760a698c5732f4d2e319aa0105ffc79f978c58f31
+size 11111
diff --git a/marked/Rel-16/37_series/37977/5bd2e409e2ed67e06109635cc3a56e25_img.jpg b/marked/Rel-16/37_series/37977/5bd2e409e2ed67e06109635cc3a56e25_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c555b6511e6d7b9b50a2305fb702e33dfe892c7
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/5bd2e409e2ed67e06109635cc3a56e25_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69772db84fd1f2b01121df62413e4d9b68e90a27ae0e5fe2c0e9bcaf88c32f57
+size 25282
diff --git a/marked/Rel-16/37_series/37977/5c257a05603439a153cb0cf9d4ea626a_img.jpg b/marked/Rel-16/37_series/37977/5c257a05603439a153cb0cf9d4ea626a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..748fe5088f4368674bc5cd6d1275f340adc7fa3e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/5c257a05603439a153cb0cf9d4ea626a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5cb734015cb811784fbdd7dc9333b5199dbb1a67154a9f0760dd8872cf4b7b16
+size 31866
diff --git a/marked/Rel-16/37_series/37977/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37977/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..01d955e85ce4b36b12507d7a1aa2af028fb68b3a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3bb8c49c893cfd5d1b755529afd464d0fca4c4d92fe06ebb419bc9ecc7d432e
+size 9482
diff --git a/marked/Rel-16/37_series/37977/61de503b1d455cc618610b290f55914d_img.jpg b/marked/Rel-16/37_series/37977/61de503b1d455cc618610b290f55914d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..75527086ae4c6bd48736ec40263a37091197b02f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/61de503b1d455cc618610b290f55914d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cb8f511a8dc5d08d2006b98ff7533fb8d1ffdcfa0c62911d1a28d813bd28912e
+size 58927
diff --git a/marked/Rel-16/37_series/37977/6243dbbad1ae96ba4862675d1b3d3443_img.jpg b/marked/Rel-16/37_series/37977/6243dbbad1ae96ba4862675d1b3d3443_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac91e3ede1123da2176461f84d1c3504fd4e4058
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6243dbbad1ae96ba4862675d1b3d3443_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46289dadbda78693346e35db78312b8702824f054e6ae46dd4ea8c3992ddb514
+size 38769
diff --git a/marked/Rel-16/37_series/37977/624646367ef6cd220973a363f00310a0_img.jpg b/marked/Rel-16/37_series/37977/624646367ef6cd220973a363f00310a0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1895cd6a9f78b48b6d2405277cd993ad6c90aff1
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/624646367ef6cd220973a363f00310a0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:626cf2cb6278da0fb350dab2177f6072f1ea38933a29c23ee50c0c6bd1fdffdd
+size 94910
diff --git a/marked/Rel-16/37_series/37977/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37977/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcdcf53ad3304cc60b8fcc447c5d56afa3959b9d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:629196a453cd4a52810f9cedfe2666ad9f70927a5d0b9f4afc234acf69700104
+size 5633
diff --git a/marked/Rel-16/37_series/37977/64e9a7b00fe083b55736c3eb5a7139e9_img.jpg b/marked/Rel-16/37_series/37977/64e9a7b00fe083b55736c3eb5a7139e9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d98f62d169e0c34f6386c1d77004873bade974c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/64e9a7b00fe083b55736c3eb5a7139e9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39134019861123896b393d170aafb34d4eae5a375f765d697d85b7cb9b1be413
+size 54761
diff --git a/marked/Rel-16/37_series/37977/67032144ed8eb3c41af3ef1aa82a9c74_img.jpg b/marked/Rel-16/37_series/37977/67032144ed8eb3c41af3ef1aa82a9c74_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5000f6d654e94099f381c792d44e44ea131e37ac
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/67032144ed8eb3c41af3ef1aa82a9c74_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5dd1a6f9d4b191137c13b01e815ab069b238260b9d1916b6f45b0e140cb0525
+size 87649
diff --git a/marked/Rel-16/37_series/37977/67408c41c75d983c13a9bd3d66953f3c_img.jpg b/marked/Rel-16/37_series/37977/67408c41c75d983c13a9bd3d66953f3c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..25a5bbc9c88c27a07aca98e8d95ed79757f4dcbe
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/67408c41c75d983c13a9bd3d66953f3c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:23b1088b1c5cf5584db327fdf65fafc04ff57f624f850394123ecf7a083a0c5d
+size 96582
diff --git a/marked/Rel-16/37_series/37977/6766862d9c432178c879b0f71ad2dac1_img.jpg b/marked/Rel-16/37_series/37977/6766862d9c432178c879b0f71ad2dac1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6002e69b03bde2fc4fb77bc8a5c4686a2cc29c67
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6766862d9c432178c879b0f71ad2dac1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6cfb5a4a6a1f50e8d6e61cdff074e92ea15d18628286ecc1a6823cda04f8f5ca
+size 74048
diff --git a/marked/Rel-16/37_series/37977/6784f8ce8ef7f7f05e0b53eb5c24f59f_img.jpg b/marked/Rel-16/37_series/37977/6784f8ce8ef7f7f05e0b53eb5c24f59f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..644fd8b63c512214c38c39f986f530f13ad1f7af
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6784f8ce8ef7f7f05e0b53eb5c24f59f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1250d74c726d163e15d71029fb084c3ef6fd32b627fadbb7ecb3f3858a1118f
+size 61826
diff --git a/marked/Rel-16/37_series/37977/67c232883c119b120d2fb337bf588e05_img.jpg b/marked/Rel-16/37_series/37977/67c232883c119b120d2fb337bf588e05_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5c77d2c2ce017cadd6e59b815b299dbbb0fcd39f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/67c232883c119b120d2fb337bf588e05_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8d0ff8e671ddeb39542885f5f72b500a58d33d47f75fabcabac32a2679444b9
+size 50003
diff --git a/marked/Rel-16/37_series/37977/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/marked/Rel-16/37_series/37977/6be06b7dc72bb42afcb3465394667c3b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1bcde25dd306aac3d56ad33781edf0b53a4502e0
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6be06b7dc72bb42afcb3465394667c3b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c6e0baaf1150d30148fe372517c5c92e53dba6c969f36eacea78c7dfde0af072
+size 89510
diff --git a/marked/Rel-16/37_series/37977/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/37_series/37977/6e15fc9ea763541c5913d26f85072ae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e2f78a0ba7292b7a96e64bd96aabee693471b769
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6e15fc9ea763541c5913d26f85072ae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:33d13b6c6cc5027945cb4ad4c69dfb4f673b0b34cb2d4baf213e984179b4398b
+size 54329
diff --git a/marked/Rel-16/37_series/37977/6e5302244dc783e0cc95a2f76710974d_img.jpg b/marked/Rel-16/37_series/37977/6e5302244dc783e0cc95a2f76710974d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d71fed3d0c80c860c37c65a37c002de3f27345c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/6e5302244dc783e0cc95a2f76710974d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:535297d6b1e551c1f2df5e4998e9999ba98804e653451b01ab95e9a9f30d18b0
+size 14739
diff --git a/marked/Rel-16/37_series/37977/70fa50a74183d4d85213f463bf9d84ea_img.jpg b/marked/Rel-16/37_series/37977/70fa50a74183d4d85213f463bf9d84ea_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..780c5fdfbb16fd2fa380f5f24358279598ef16f6
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/70fa50a74183d4d85213f463bf9d84ea_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f04b51fc15d8ab54b4197abc7cd91c9a43fa22754a708b1f3bbe45070760d5e7
+size 34490
diff --git a/marked/Rel-16/37_series/37977/730b6615db6d402580db1024a7f4e163_img.jpg b/marked/Rel-16/37_series/37977/730b6615db6d402580db1024a7f4e163_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fca8e5c9760af42b363c15e291f7d0c112594583
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/730b6615db6d402580db1024a7f4e163_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67befc4525e9b15e52cf77de32260872ad3246ea7552605877c6a9a730990901
+size 17755
diff --git a/marked/Rel-16/37_series/37977/7317ad6b925dc0474d45f40ac5d3ae3d_img.jpg b/marked/Rel-16/37_series/37977/7317ad6b925dc0474d45f40ac5d3ae3d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bcec6a2a2a4740a878df8ce9c0d79c52cf576971
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/7317ad6b925dc0474d45f40ac5d3ae3d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acadaaf99b6900e9c08a3f8878ccf89e6f0156c09ade92420584144045b90378
+size 52284
diff --git a/marked/Rel-16/37_series/37977/7416c959934a45ae287874c83007a146_img.jpg b/marked/Rel-16/37_series/37977/7416c959934a45ae287874c83007a146_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9c6479ba470ac4ad48c56892dfa2607d0d1f0e50
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/7416c959934a45ae287874c83007a146_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:357d57ab4477b8ce14279571adc2ad8b5f3b5feb7a844576be948e8e79b5b339
+size 55029
diff --git a/marked/Rel-16/37_series/37977/7498bf530d9e13633524982a399d4439_img.jpg b/marked/Rel-16/37_series/37977/7498bf530d9e13633524982a399d4439_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..594d066a251146bb1e2bf0bc2e5e6d572826924e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/7498bf530d9e13633524982a399d4439_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0559702a6f54c0947e8d2bfe6f8cfd2ec0b5197c266ea3a00c171d4bd09b5ee1
+size 120912
diff --git a/marked/Rel-16/37_series/37977/783c6fe6b529f9ffac79e20e1a440167_img.jpg b/marked/Rel-16/37_series/37977/783c6fe6b529f9ffac79e20e1a440167_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8dded44c745e58615471a3a02fa94c94a145a4c3
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/783c6fe6b529f9ffac79e20e1a440167_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7c3f9b77d31c8ed2076e36aeea6178c4259c70520f73083624f344bdf21e33be
+size 35508
diff --git a/marked/Rel-16/37_series/37977/785ffdb80d7fb12f2eee04b161106715_img.jpg b/marked/Rel-16/37_series/37977/785ffdb80d7fb12f2eee04b161106715_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..91c37d92c4b86a1663d62d5a72182f36a8019e68
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/785ffdb80d7fb12f2eee04b161106715_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:92fe779dc80c74f20df2138fd076590eeae1c836d42d8f2f33f167e7feb88b4a
+size 16282
diff --git a/marked/Rel-16/37_series/37977/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/37_series/37977/79e1709a7317ead45379cbb8ff3ba802_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..894e484e26db814296fcf49be8edafcfaa17e45c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/79e1709a7317ead45379cbb8ff3ba802_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:62f375b7001507072d0c8e0eddf0aa39fe118f8ccb3fd710b93b6048b95853ab
+size 53664
diff --git a/marked/Rel-16/37_series/37977/815e371be8c93f43b2ed745e5a78ee5a_img.jpg b/marked/Rel-16/37_series/37977/815e371be8c93f43b2ed745e5a78ee5a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fed20c835ab735c96387afbf21ad8ad5a192b045
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/815e371be8c93f43b2ed745e5a78ee5a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6a955aa7a48f227649b3e5b1052eede6559fec76f364843382b754de79f42b79
+size 171991
diff --git a/marked/Rel-16/37_series/37977/834359004b142e33f72aea7a3de2440f_img.jpg b/marked/Rel-16/37_series/37977/834359004b142e33f72aea7a3de2440f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c24aadb192590d295126d1957008a251a343ccc1
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/834359004b142e33f72aea7a3de2440f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:975fdb64a91edbde2db86c37dab0ce5d0841f1d2d8f921e7dc134f3d3274bb8f
+size 50957
diff --git a/marked/Rel-16/37_series/37977/839f9152f020c693e6c10ccb4fe611f9_img.jpg b/marked/Rel-16/37_series/37977/839f9152f020c693e6c10ccb4fe611f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0f5d50e282a04517b16fe473c92fb9600c126fe
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/839f9152f020c693e6c10ccb4fe611f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5a5eb7e94e5d519017592842e3d56ab5103b5b30fb096f381956ad688090785
+size 82096
diff --git a/marked/Rel-16/37_series/37977/87afd2b5c75bd1f35d29290e1188e7d3_img.jpg b/marked/Rel-16/37_series/37977/87afd2b5c75bd1f35d29290e1188e7d3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e0b7367f5415ed60fd96aa00ce4042bad4a2ff59
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/87afd2b5c75bd1f35d29290e1188e7d3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:10d823aaa7278b7c0e162225753c0907a178513db955330d773102ac1e4fe485
+size 36800
diff --git a/marked/Rel-16/37_series/37977/8952187b46b5ceed6c4b01df625c0c94_img.jpg b/marked/Rel-16/37_series/37977/8952187b46b5ceed6c4b01df625c0c94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..84e380d96efc92b4f7422311861e639be446fb51
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/8952187b46b5ceed6c4b01df625c0c94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8ba989a01679ca331e6a831ac4bed7debcc08d8dd9a446636cb9c1a1e464ed4
+size 11119
diff --git a/marked/Rel-16/37_series/37977/898c1327035aaf14d832e4400901e092_img.jpg b/marked/Rel-16/37_series/37977/898c1327035aaf14d832e4400901e092_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ecc557d520d2531233b1816d16e33dde01a29ef0
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/898c1327035aaf14d832e4400901e092_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b9fd813c3de4b65d12ae562a3a3df8e6140f36244f8e566c6052c305f1633170
+size 86605
diff --git a/marked/Rel-16/37_series/37977/89d23fa870a5ab93f96d1d119af3d0cb_img.jpg b/marked/Rel-16/37_series/37977/89d23fa870a5ab93f96d1d119af3d0cb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..af0ca5c476ce58cf3d429af977b0b3a6d43bbd77
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/89d23fa870a5ab93f96d1d119af3d0cb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:65a892d956c6f04b607bcc390c05c09f728038e7f3d21802609f97b10318b84c
+size 72754
diff --git a/marked/Rel-16/37_series/37977/8cf12562763d72a28bb42fd6ff4905ac_img.jpg b/marked/Rel-16/37_series/37977/8cf12562763d72a28bb42fd6ff4905ac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0dd89b2bc3e82a661c40f286b6e393dd08e328d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/8cf12562763d72a28bb42fd6ff4905ac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aecadf88048acfb0588a0c167bc92f7483612ce4c3cc1b36da7842daa7eb3705
+size 89997
diff --git a/marked/Rel-16/37_series/37977/8d634ce92bb10765e51c1cc4af9c09f3_img.jpg b/marked/Rel-16/37_series/37977/8d634ce92bb10765e51c1cc4af9c09f3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fd32d96dcc00fb4b0e47b04e974e9ca4ee99d78a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/8d634ce92bb10765e51c1cc4af9c09f3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d2c704e5e236fd33a633a8fe0ce1a0cb4c195f8cd1f0d56467383a83ef20b06d
+size 25434
diff --git a/marked/Rel-16/37_series/37977/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/37_series/37977/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..649950008248ea5a2965d546cb6e0dee273dd0c1
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a0d8047da366feeee8807800d5cfa8ff918c98ee0d298fa23138c7663e6be3d
+size 42336
diff --git a/marked/Rel-16/37_series/37977/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg b/marked/Rel-16/37_series/37977/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..603068c18937f1e5906556606a22bd64defa418b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:56c44190aad4764069297b8237407d06ec40a2661a5b610ff04aa0ed9f0cb04b
+size 109720
diff --git a/marked/Rel-16/37_series/37977/94a83e3305f0eb414087648ad5909689_img.jpg b/marked/Rel-16/37_series/37977/94a83e3305f0eb414087648ad5909689_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cfcb708c5adc20dac85a40277803ee5238210cf5
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/94a83e3305f0eb414087648ad5909689_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c448b3bf74c80382700de5db8b3dad88a3026cf23cf4af16750a9ebd655061f
+size 32285
diff --git a/marked/Rel-16/37_series/37977/99781d878388c3e0f359b1d6ce14119c_img.jpg b/marked/Rel-16/37_series/37977/99781d878388c3e0f359b1d6ce14119c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..12f44554f411c88f296e95f8675f9ee4fb380f32
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/99781d878388c3e0f359b1d6ce14119c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b93c1fe1fe26fb604465b215f735a30e5d5d0ac24a529050086bda83157222d
+size 49669
diff --git a/marked/Rel-16/37_series/37977/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/37_series/37977/9a14684f8ae1345c6efea6f5994c730c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f81246f12ac7ba79b85f2067ee155cc349b41999
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/9a14684f8ae1345c6efea6f5994c730c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d8beca92aaefd74cb49f98c092e29d3637bf90cbb6f86de5632ec82d0b5c3f28
+size 28907
diff --git a/marked/Rel-16/37_series/37977/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/37_series/37977/9b686adccf125267a013fa25721231a3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..48e90a9db06967ddae2ccd2633cb01236de5e015
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/9b686adccf125267a013fa25721231a3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:88ca0510f9192cbcc25fb9cc14e74afbbcaedd8c94a6f603fd77f84630ddb521
+size 21292
diff --git a/marked/Rel-16/37_series/37977/9bdb8898200f6a82bca1c1e6ff4621b9_img.jpg b/marked/Rel-16/37_series/37977/9bdb8898200f6a82bca1c1e6ff4621b9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a68be0ca8ecfb91ccb3d586e7d35a8fbd44f6942
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/9bdb8898200f6a82bca1c1e6ff4621b9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8dd4b4049f9d346b4054b53c6217858924fd9d3bf4a7660726f85fd582f9868a
+size 44273
diff --git a/marked/Rel-16/37_series/37977/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/37_series/37977/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4385ac5924a87640ae3bd32902613158eb88c70c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c66d29c6a5dccd0d6e5f05976b42173c8c73f9efe01b8976a277b1e4794da14e
+size 25872
diff --git a/marked/Rel-16/37_series/37977/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/37_series/37977/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..047ff7e66bf536221dc08422d751f34965cb93da
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/9f6dec4d4e9fde40bce018861ef1278e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd01e06300c93fdc3d0240e424227c80d355bef2ef20a478799b89e409e436de
+size 80517
diff --git a/marked/Rel-16/37_series/37977/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-16/37_series/37977/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cb3b8f3cf3181d6c1122239cd6dd289eb7d4cbae
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1824c275cec738f87ef37c5ea182dde5e1e45b3bb569ab641706d18d4c4dad33
+size 26714
diff --git a/marked/Rel-16/37_series/37977/a0b992c3c544896bb2567bf22e532bd1_img.jpg b/marked/Rel-16/37_series/37977/a0b992c3c544896bb2567bf22e532bd1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2153e994334a68dfb8cc4907fd8f01e2db9060e4
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a0b992c3c544896bb2567bf22e532bd1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ca095bf67bc1047cd49930f3fd7a14e5512cc834b02ca8bf9d28b17b352f156
+size 111745
diff --git a/marked/Rel-16/37_series/37977/a10590b8cd913a41920c6ceadb521e77_img.jpg b/marked/Rel-16/37_series/37977/a10590b8cd913a41920c6ceadb521e77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f1578739ea3f970c560eb449347a4e3f50c67b4e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a10590b8cd913a41920c6ceadb521e77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c7d97967a6852006bcaf79f49fd1418071fe1df28e88fac78261bfc1dbe29e69
+size 101619
diff --git a/marked/Rel-16/37_series/37977/a147b08b7a2311fd6e2391968931c14b_img.jpg b/marked/Rel-16/37_series/37977/a147b08b7a2311fd6e2391968931c14b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..309d1bee3c061070b4243f04b646a09f89074cd2
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a147b08b7a2311fd6e2391968931c14b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fa3cd275741e9b2a1ceb501ef40d200711fa709948757337cd57bb13a0d5224a
+size 11073
diff --git a/marked/Rel-16/37_series/37977/a346e19f92f1699e3f96432c0464c957_img.jpg b/marked/Rel-16/37_series/37977/a346e19f92f1699e3f96432c0464c957_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8d21b8d65448b22ecc1be727d6ebe74756b0fe3f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a346e19f92f1699e3f96432c0464c957_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:decd22b839e1d1cbe9ce5941437db6d8e5f70cb2e1bf43e469840c0244a8ac0e
+size 49056
diff --git a/marked/Rel-16/37_series/37977/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg b/marked/Rel-16/37_series/37977/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4d2c8f780642dae1429ebc82828ae7079801bbac
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a4a24ac70004b2e8087923d3f0f6d01d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:918e4a51fe27deec920e125fc5d1baa0b71248449f48999c539d9cf6c6371046
+size 75400
diff --git a/marked/Rel-16/37_series/37977/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/37_series/37977/a5184899f915014fa38608754efcc9c7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a2d333aa0468c0106607f02033a27055f2d9e78
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a5184899f915014fa38608754efcc9c7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1467ae428e2fc8eafac30affdc6f3328567b9b00c08f028cbd30946b95fe2893
+size 35939
diff --git a/marked/Rel-16/37_series/37977/a5d373f8234b0a8b8f4541da64f9ac64_img.jpg b/marked/Rel-16/37_series/37977/a5d373f8234b0a8b8f4541da64f9ac64_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc5fe497d3a6e6e7f8cf183c586eba7a52020381
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a5d373f8234b0a8b8f4541da64f9ac64_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d09b136353518b26828b60394f755191dd7359825e4b4d1edcce2eed20eb984b
+size 97246
diff --git a/marked/Rel-16/37_series/37977/a802694aeb53f806085863c8eaa0451d_img.jpg b/marked/Rel-16/37_series/37977/a802694aeb53f806085863c8eaa0451d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1ec318e34c909f7cedff00d0f34c25e2b0c5bdb3
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a802694aeb53f806085863c8eaa0451d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1b43b7baf99b48d2aa601a4d922edc9927d738d6ee1d08370a80b8dac217b75a
+size 31959
diff --git a/marked/Rel-16/37_series/37977/a93a411a51b0e65719fab15f375fdd82_img.jpg b/marked/Rel-16/37_series/37977/a93a411a51b0e65719fab15f375fdd82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d619ca82b230c1b7663c22e0ee9e40ac9fe0ffca
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/a93a411a51b0e65719fab15f375fdd82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f7c90a8b541ac4e32b4db2859a100eb371c7f42d1618bfc6c5f9933eae6e0b0
+size 88042
diff --git a/marked/Rel-16/37_series/37977/aa44d56b283764316570c8885f370b1f_img.jpg b/marked/Rel-16/37_series/37977/aa44d56b283764316570c8885f370b1f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4b74d7c578fdf349f3b11f8896ae30c6a1eb830d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/aa44d56b283764316570c8885f370b1f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0947ab4b81659935f802cf4f56464de381959c6cffd736c16ab05a55e13a477d
+size 29825
diff --git a/marked/Rel-16/37_series/37977/aa75bb3aaab7d58772b885504627945a_img.jpg b/marked/Rel-16/37_series/37977/aa75bb3aaab7d58772b885504627945a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f7b59600ba2e2cfe77b6739a87959060d6b9c8b8
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/aa75bb3aaab7d58772b885504627945a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2fe93dc658fe846365a5a4750173fac7fad8f7f96a147b90a8936b625481e9c6
+size 28277
diff --git a/marked/Rel-16/37_series/37977/b02ba0b73e95416eb547976f6145b169_img.jpg b/marked/Rel-16/37_series/37977/b02ba0b73e95416eb547976f6145b169_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ac0900611262b35f202fe46f28b0cdaff99391d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/b02ba0b73e95416eb547976f6145b169_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5a33443fe584487234e059b1ac99d84dcffccafaedd2b4c7be80f3f2b1963d8a
+size 64823
diff --git a/marked/Rel-16/37_series/37977/b11c2eb778491a9a07084b02124d1faa_img.jpg b/marked/Rel-16/37_series/37977/b11c2eb778491a9a07084b02124d1faa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a962bf617d16a254f64202d9f2b88a04083a27b5
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/b11c2eb778491a9a07084b02124d1faa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14793929c409047daa7615437a3d9212d1c1a31390595c1b96b1c1f2932de60e
+size 30138
diff --git a/marked/Rel-16/37_series/37977/b1c27d955a3589957e99cc4f284ddcb1_img.jpg b/marked/Rel-16/37_series/37977/b1c27d955a3589957e99cc4f284ddcb1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab53fa3e4a32aee15946313f7951662977528cd7
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/b1c27d955a3589957e99cc4f284ddcb1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:537fdf9256c2228eab856b80dd9aa1d2e8caa3ff2602165ab877139d2efe2a90
+size 54896
diff --git a/marked/Rel-16/37_series/37977/b75617f33603d5f399500e7791997841_img.jpg b/marked/Rel-16/37_series/37977/b75617f33603d5f399500e7791997841_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b7c9f3b3cc89cf59b40f0f631ef2baa8be3a7805
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/b75617f33603d5f399500e7791997841_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:00b789912355e47396c928afadc5068d922b146a47af6fa5c69b4860afe4a3b7
+size 21822
diff --git a/marked/Rel-16/37_series/37977/ba3af4f84c0ed2d69d4eb276529510e2_img.jpg b/marked/Rel-16/37_series/37977/ba3af4f84c0ed2d69d4eb276529510e2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..87343b49cfd00ae4d89b8acc95098b4674872373
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/ba3af4f84c0ed2d69d4eb276529510e2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f95e8a5365a0ce8993a226bac049014be7358452b0600d7d369016b22736fb88
+size 66069
diff --git a/marked/Rel-16/37_series/37977/ba99363c7d61d24290635b47b71e41c2_img.jpg b/marked/Rel-16/37_series/37977/ba99363c7d61d24290635b47b71e41c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..708edd815ea4c148479ba1f4c8bcd9edefe7bdbe
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/ba99363c7d61d24290635b47b71e41c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9aab8d3392a261108d0343eb47d7f6c75723f173a5c895ba31c923a1b5bcd94e
+size 52789
diff --git a/marked/Rel-16/37_series/37977/bb908297bfe73e2759a9dd88ae0506f9_img.jpg b/marked/Rel-16/37_series/37977/bb908297bfe73e2759a9dd88ae0506f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed493bd890fcc7964f52e558074cd2195e1f0a25
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/bb908297bfe73e2759a9dd88ae0506f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:172e1390c6a371b0d28c24bb560d6cbf4f78a1a9736395819916af41d39bc740
+size 98266
diff --git a/marked/Rel-16/37_series/37977/bbad6dce7d0dca9ee0b885b4f28453b2_img.jpg b/marked/Rel-16/37_series/37977/bbad6dce7d0dca9ee0b885b4f28453b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cedb17dde0c9ddb12bd8354563258630dfa2f48b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/bbad6dce7d0dca9ee0b885b4f28453b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6416307586dce0223275ed7b16d89eadd8e60f7d83bffe9a8b6037623320c17d
+size 54953
diff --git a/marked/Rel-16/37_series/37977/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg b/marked/Rel-16/37_series/37977/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d8953cc038ff6956cbf7b60b99857d7b2cfd0eb3
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a293842060b5330670e0a724d1590e040472d11fe7e12f3e31a4cad44436c25a
+size 91212
diff --git a/marked/Rel-16/37_series/37977/bd361bbf5003c5df0416591de03a4522_img.jpg b/marked/Rel-16/37_series/37977/bd361bbf5003c5df0416591de03a4522_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3436f70341ec6cf51918186750f3eda8bf88ae1f
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/bd361bbf5003c5df0416591de03a4522_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4eb6bd89ed7d7811f9aaac04210375d75fba91669c02de467b6d8c6ae2fe4614
+size 74453
diff --git a/marked/Rel-16/37_series/37977/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/37_series/37977/c07e21a8d65991db04263322f859c94f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..59bd6b87c5aac593cbaa4f21add7a2d2794dc9fd
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c07e21a8d65991db04263322f859c94f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2dc37c85b01e6882886523c82d387ed3cd0acc5595052bca6a16fb085a742821
+size 77509
diff --git a/marked/Rel-16/37_series/37977/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg b/marked/Rel-16/37_series/37977/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..81895d7bbe8c749faad03f4517e10a2170ebf932
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e475fc6ba3a696ce62e19835f63adff8461f0997fd1066b444d8cdce88a84058
+size 43182
diff --git a/marked/Rel-16/37_series/37977/c21fe89d8034ec5b80bd47c1cd710202_img.jpg b/marked/Rel-16/37_series/37977/c21fe89d8034ec5b80bd47c1cd710202_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc70daf4145b05ed553645fecd3c563ea66ebb36
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c21fe89d8034ec5b80bd47c1cd710202_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:71d08bf57a3c4daf00072f6071a4ff979be54f38c468a0726d5bacccd1bf072d
+size 89361
diff --git a/marked/Rel-16/37_series/37977/c3d8104dc13f901e55235041c000a837_img.jpg b/marked/Rel-16/37_series/37977/c3d8104dc13f901e55235041c000a837_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..efddb933a9e6cd9e4c4abe42609bef49dc87696a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c3d8104dc13f901e55235041c000a837_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:070e9447385289f725329868010e25940c5c5a5fca3065356b76e0f47d9db918
+size 83613
diff --git a/marked/Rel-16/37_series/37977/c3f02cb9dab65cb16d8a4f9aa20bf12d_img.jpg b/marked/Rel-16/37_series/37977/c3f02cb9dab65cb16d8a4f9aa20bf12d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..736a13cc42e4ccf3649b78db99a918f5c985f5d4
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c3f02cb9dab65cb16d8a4f9aa20bf12d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0175d3d50bbc410c321af32e5bdc4c2c1cfef791eb88a3656fc913effb14ba7
+size 76844
diff --git a/marked/Rel-16/37_series/37977/c53adc66eab40abd5f8b9107d950ad04_img.jpg b/marked/Rel-16/37_series/37977/c53adc66eab40abd5f8b9107d950ad04_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f976d201badd3f29733143af56dfa142e8e6d109
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c53adc66eab40abd5f8b9107d950ad04_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:67c75a0e5f84e9df8891ac729926bcdfa986f01d3efc8345ccf0addd6db87319
+size 34599
diff --git a/marked/Rel-16/37_series/37977/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg b/marked/Rel-16/37_series/37977/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0a73a274e83787a97c0ed9f258231b7c169bb470
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c8d2bc5b813f5d46408a32185a56a7b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba158c0261e4cb5b8469e067796689b3774798c79fb64bd1dd253a50fc89c7e9
+size 115771
diff --git a/marked/Rel-16/37_series/37977/c9829c80e5f6e9384df5f75e24da4c25_img.jpg b/marked/Rel-16/37_series/37977/c9829c80e5f6e9384df5f75e24da4c25_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3ee29df30a7bbd10140afc5d04cdfa2c5afde10b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/c9829c80e5f6e9384df5f75e24da4c25_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b86feff78db2799883493cea07ce99f6cd4ae38cef7e2c1f3045d379b42ace86
+size 67375
diff --git a/marked/Rel-16/37_series/37977/ca1e31c6a55f9221c960f1fbce96e589_img.jpg b/marked/Rel-16/37_series/37977/ca1e31c6a55f9221c960f1fbce96e589_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d989ce98eb1f4652246201ad81403aab0766d52a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/ca1e31c6a55f9221c960f1fbce96e589_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd37224578ce2620dec729243bd535ed4877cc4be80268075b45b34cdf78b39b
+size 60709
diff --git a/marked/Rel-16/37_series/37977/cf67b3ae51d596591ce42defeb62f9d4_img.jpg b/marked/Rel-16/37_series/37977/cf67b3ae51d596591ce42defeb62f9d4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8f1f74a1d60411ba4bd42a05a24d795be5c9fbd8
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/cf67b3ae51d596591ce42defeb62f9d4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4acfc23a6cf7809e04a35ffae72b2773dd2f855b961ea97cf6806d72b87f5135
+size 15066
diff --git a/marked/Rel-16/37_series/37977/d3b73b32af148cbe75a9d016ac7bdd4d_img.jpg b/marked/Rel-16/37_series/37977/d3b73b32af148cbe75a9d016ac7bdd4d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0fed9e07898f01062a0ca41a614e65106ff6ec90
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/d3b73b32af148cbe75a9d016ac7bdd4d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:95623a9d06710de46bd812dc3503071a42b5dcb04fbec3887c940fa9f54220ec
+size 52857
diff --git a/marked/Rel-16/37_series/37977/d579d14979ebeaa676740df2e3dbe024_img.jpg b/marked/Rel-16/37_series/37977/d579d14979ebeaa676740df2e3dbe024_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a7398f656fdb7d253609ea57a1c0652464305583
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/d579d14979ebeaa676740df2e3dbe024_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8005e84258333ed150ac7a6c0a16424a36a28d7ed5f9634f8cd535420528df55
+size 41149
diff --git a/marked/Rel-16/37_series/37977/d989d8766a23d5e409031f1ceae6572b_img.jpg b/marked/Rel-16/37_series/37977/d989d8766a23d5e409031f1ceae6572b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a1aa6c6e653d29699218cf1356e21694ed650c0b
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/d989d8766a23d5e409031f1ceae6572b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2a4951f5ccff7a663109e9b138ee7bdae0ff4bf0396048a4786d4566eda4ed3
+size 97613
diff --git a/marked/Rel-16/37_series/37977/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg b/marked/Rel-16/37_series/37977/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..578a4ed5b9b98a64769eb07e7e34dc4a1d383dfc
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/df72bd7468eb8bd59e911d0b5cb7a810_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b814cb3fdb5348a8d1173514633f37b3a66a151d162fdd664b9ac78d5a9d821d
+size 71436
diff --git a/marked/Rel-16/37_series/37977/e01c6273c4177746475715ee9c17a882_img.jpg b/marked/Rel-16/37_series/37977/e01c6273c4177746475715ee9c17a882_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c721ce04518604c5ddd2a09f9b06789ab1ef215e
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e01c6273c4177746475715ee9c17a882_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:417cfb5d7ca915d01ff69c656bdbefa70af4c4ec9b71d4159cc5916107080785
+size 42256
diff --git a/marked/Rel-16/37_series/37977/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/37_series/37977/e05b36c0d46549e681ce6581422c66b2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aba19bcb101f66649c836e19dd4cc743e7335603
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e05b36c0d46549e681ce6581422c66b2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:224f389b0ae4e829073758ce2fd1be4b1b3e3b056e6f505d8cedddc9f165396b
+size 31860
diff --git a/marked/Rel-16/37_series/37977/e178518844c9a050d9f0e76a8819d9ac_img.jpg b/marked/Rel-16/37_series/37977/e178518844c9a050d9f0e76a8819d9ac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..46d40c4ce4564882d6325ed95c70f1d920de14ad
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e178518844c9a050d9f0e76a8819d9ac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf8596f46aec4116b1b3590d8e35c96f62740e968c23d255b7269cd26f98f3db
+size 57765
diff --git a/marked/Rel-16/37_series/37977/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/37_series/37977/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..575a25aabea64f6a44de79ae8ff72c42d5af3892
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edbc5f0f997f7722cf391b18aa71b30c2b79f28df3189adad4c5f112d14e9285
+size 70301
diff --git a/marked/Rel-16/37_series/37977/e2028979caae230f36254a6bec04bcd9_img.jpg b/marked/Rel-16/37_series/37977/e2028979caae230f36254a6bec04bcd9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c005cb6cfb1413b136cecba296dd9f7c3a17062d
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e2028979caae230f36254a6bec04bcd9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bb83b875a952fb8b87f4a1ef53e2e1b84355181cbe22ffed252252459ded42a1
+size 38455
diff --git a/marked/Rel-16/37_series/37977/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg b/marked/Rel-16/37_series/37977/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..379d71de584ecbdc8f8b5ae9440a65871da46dca
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2aee45a49d5e8540e0f3848437f26b8aa7380f273b61f28611165d69b3f042f
+size 77985
diff --git a/marked/Rel-16/37_series/37977/e84de38c2eac283d770e2c8acdf64308_img.jpg b/marked/Rel-16/37_series/37977/e84de38c2eac283d770e2c8acdf64308_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77da87c8b7a22cb3caa1d363f8a77615d87be82a
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/e84de38c2eac283d770e2c8acdf64308_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:edd40915f8f537d0e5da12dde135b625d59657c46045d516f57cd6e3bdfb22da
+size 70432
diff --git a/marked/Rel-16/37_series/37977/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/37_series/37977/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..794af701d05ec87a38c2f272e6c274f0fc6253fa
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:72f21e3de24ee01200069bbd05f63b2bd46bfd061f5df0c61b78263b2d13c39b
+size 31513
diff --git a/marked/Rel-16/37_series/37977/eb672b49a91c9683b2dade9969e6c8b0_img.jpg b/marked/Rel-16/37_series/37977/eb672b49a91c9683b2dade9969e6c8b0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..92fc959060c1a1d6771812332513a0c5cdf5be62
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/eb672b49a91c9683b2dade9969e6c8b0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:de1050fb568fa9fa8bcf6cb650cf1093692f74eb3504ef9c57108dce248d6368
+size 69697
diff --git a/marked/Rel-16/37_series/37977/ebce469575e197e659de896b83c7a9cc_img.jpg b/marked/Rel-16/37_series/37977/ebce469575e197e659de896b83c7a9cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..de5708acbdd4d040c0c3297bf4bdbf9717371a73
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/ebce469575e197e659de896b83c7a9cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a614a5eb039a864949dcaf2966e21878bb04cad89469ed063df1c3a939b473e4
+size 85940
diff --git a/marked/Rel-16/37_series/37977/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg b/marked/Rel-16/37_series/37977/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..90553580378c169da42e8f378b180c2c35316822
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f22e617a7aef13de5ffd8e390bfda1c3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e4908487fbfd19ce6cc725522bbd971800a6235ef518a1e17128a632a78c2e47
+size 43111
diff --git a/marked/Rel-16/37_series/37977/f455955c4bc84005728b4138f19098dc_img.jpg b/marked/Rel-16/37_series/37977/f455955c4bc84005728b4138f19098dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d644651d22d83fe3a61186f241c8e2c08c1101c1
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f455955c4bc84005728b4138f19098dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f5cbc87ab0b7567ffe17c9dd8eedb09a97bc1b904905da9bffda14c471e5eacc
+size 93656
diff --git a/marked/Rel-16/37_series/37977/f5a43bbc3d3642eb257baf1b10602488_img.jpg b/marked/Rel-16/37_series/37977/f5a43bbc3d3642eb257baf1b10602488_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9360394172fdfb41a2609d6b3274372977d5d6cf
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f5a43bbc3d3642eb257baf1b10602488_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e25d76f99d859e43fe3028e3c165973109e729ca83a37bb92e4ffb195245291b
+size 50939
diff --git a/marked/Rel-16/37_series/37977/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/marked/Rel-16/37_series/37977/f5d2a88925807080157c7cfb1d41cf0b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89842ec50a80fc6f29708347c1c29f2703dfc05c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f5d2a88925807080157c7cfb1d41cf0b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d3decc94c46d8f9b26a14a97c09999f01847276a3692001b4ba963e915cb772a
+size 24918
diff --git a/marked/Rel-16/37_series/37977/f78e0a777a9c5dc76cda197cbee0f206_img.jpg b/marked/Rel-16/37_series/37977/f78e0a777a9c5dc76cda197cbee0f206_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8cb434c9cd688a54da103a19980b7105eb562d33
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f78e0a777a9c5dc76cda197cbee0f206_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c3181390ae5b65cf2b91c2d0cd3fe81074a8ac6b660d7b7b5149f5280cda1f3e
+size 71862
diff --git a/marked/Rel-16/37_series/37977/f81154fc60dd0722df3c247514f141e6_img.jpg b/marked/Rel-16/37_series/37977/f81154fc60dd0722df3c247514f141e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4a1b95b330e811c8a97d05dfb092284373e0e0ba
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/f81154fc60dd0722df3c247514f141e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3b5d8c7e0e38753956c299b532b43d3929ad1829b45f6edd0b24af5c8223fb16
+size 33200
diff --git a/marked/Rel-16/37_series/37977/faff5ea2bac20b616b62b35da5a5d67c_img.jpg b/marked/Rel-16/37_series/37977/faff5ea2bac20b616b62b35da5a5d67c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..19e0111f2775e9e7b8207cd886ecd85abd382e9c
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/faff5ea2bac20b616b62b35da5a5d67c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:060ed2f60414442234088ab2efd8952650fafc1f5ab126b105d9ab14ce7fc204
+size 81207
diff --git a/marked/Rel-16/37_series/37977/fc3763c02020b3a260045bbadc1d36ba_img.jpg b/marked/Rel-16/37_series/37977/fc3763c02020b3a260045bbadc1d36ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f04381ae2f19638ac457e39fa9aba8dd92b79769
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/fc3763c02020b3a260045bbadc1d36ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2384e91a817342bb71618e1115423fb5aab16b8e96dc494a54afe524b9fb545a
+size 89898
diff --git a/marked/Rel-16/37_series/37977/fd6ee6f896324983fe3a8e9ee6c534b3_img.jpg b/marked/Rel-16/37_series/37977/fd6ee6f896324983fe3a8e9ee6c534b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e842d9460c8e20c8da95ca3223e3c94c0762d3a2
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/fd6ee6f896324983fe3a8e9ee6c534b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7571f3e100e06f3a0656ef28086f49afbd6e85d8661497a4b92525b2951d674d
+size 188151
diff --git a/marked/Rel-16/37_series/37977/raw.md b/marked/Rel-16/37_series/37977/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a94056846e103f872fdff483fe137eaa539eb6ae
--- /dev/null
+++ b/marked/Rel-16/37_series/37977/raw.md
@@ -0,0 +1,6562 @@
+
+
+# 3GPP TR 37.977 V16.0.0 (2020-06) ---
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Verification of radiated multi-antenna reception performance of User Equipment (UE) (Release 16)** ---
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. To the right of the "5G" text is a green graphic element consisting of three curved lines of increasing length, resembling a signal strength indicator or a stylized wave.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a small red graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font.
+
+3GPP logo
+
+## **3GPP**
+
+Postal address
+
+3GPP support office address  
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+Internet  
+<http://www.3gpp.org>
+
+## **Copyright Notification**
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                                     |    |
+|-------------------------------------------------------------------------------------|----|
+| Foreword.....                                                                       | 8  |
+| 1 Scope.....                                                                        | 9  |
+| 2 References.....                                                                   | 9  |
+| 3 Definitions, symbols and abbreviations.....                                       | 10 |
+| 3.1 Definitions.....                                                                | 10 |
+| 3.2 Symbols.....                                                                    | 10 |
+| 3.3 Abbreviations.....                                                              | 10 |
+| 4 Introduction.....                                                                 | 11 |
+| 4.1 Background.....                                                                 | 11 |
+| 4.2 Work item objective.....                                                        | 11 |
+| 4.3 High level requirements.....                                                    | 12 |
+| 5 Performance metrics.....                                                          | 13 |
+| 5.1 Figure of Merits.....                                                           | 13 |
+| 5.1.1 Definition of MIMO throughput.....                                            | 13 |
+| 5.1.2 Definition of Signal-to-Interference Ratio (SIR).....                         | 13 |
+| 5.1.2.1 SIR Control for Multi-Probe Anechoic Chamber Methodology.....               | 14 |
+| 5.1.2.2 SIR Control for the reverberation chamber method.....                       | 15 |
+| 5.1.2.3 SIR Control for the reverberation chamber plus channel emulator method..... | 16 |
+| 5.1.2.4 SIR Control for the two-stage methodology.....                              | 17 |
+| 5.2 Averaging of throughput curves.....                                             | 19 |
+| 5.2.1 Average of power levels.....                                                  | 19 |
+| 6 Candidate measurement methodologies.....                                          | 20 |
+| 6.1 Void.....                                                                       | 20 |
+| 6.2 Void.....                                                                       | 20 |
+| 6.3 Downlink measurement methodologies.....                                         | 20 |
+| 6.3.1 Methodologies based on Anechoic RF Chamber.....                               | 20 |
+| 6.3.1.1 Candidate Solution 1.....                                                   | 20 |
+
+|           |                                                                    |    |
+|-----------|--------------------------------------------------------------------|----|
+| 6.3.1.1.1 | Concept and configuration.....                                     | 21 |
+| 6.3.1.1.2 | Scalability of the methodology.....                                | 22 |
+| 6.3.1.1.3 | Test conditions.....                                               | 23 |
+| 6.3.1.2   | Void.....                                                          | 24 |
+| 6.3.1.3   | Candidate solution 3.....                                          | 24 |
+| 6.3.1.3.1 | Concept and configuration.....                                     | 24 |
+| 6.3.1.3.2 | Test conditions.....                                               | 27 |
+| 6.3.1.3.3 | Overview of calibration procedures specific to the RTS method..... | 27 |
+| 6.3.1.4   | Candidate solution 4.....                                          | 28 |
+| 6.3.1.4.1 | Concept and configuration.....                                     | 28 |
+| 6.3.1.4.2 | Decomposition approach.....                                        | 29 |
+| 6.3.1.4.3 | Conducted test.....                                                | 30 |
+| 6.3.1.4.4 | Radiated test.....                                                 | 30 |
+| 6.3.1.4.5 | Possible extensions of the decomposition method.....               | 31 |
+| 6.3.1.5   | Candidate solution 5.....                                          | 31 |
+| 6.3.1.5.1 | Concept and configuration.....                                     | 32 |
+| 6.3.1.5.2 | Test conditions.....                                               | 34 |
+| 6.3.2     | Methodologies based on Reverberation Chamber.....                  | 35 |
+| 6.3.2.1   | Candidate solution 1.....                                          | 35 |
+| 6.3.2.1.1 | Concept and configuration.....                                     | 36 |
+| 6.3.2.1.2 | Test conditions.....                                               | 37 |
+| 6.3.2.2   | Candidate solution 2.....                                          | 38 |
+| 6.3.2.2.1 | Concept and configuration.....                                     | 38 |
+| 6.3.2.2.2 | Test conditions.....                                               | 39 |
+| 7         | Base Station (BS) configuration.....                               | 40 |
+| 7.1       | eNodeB emulator settings.....                                      | 40 |
+| 8         | Channel Models.....                                                | 42 |
+| 8.1       | Introduction.....                                                  | 42 |
+| 8.2       | Channel Model(s) to be validated.....                              | 42 |
+| 8.3       | Verification of Channel Model implementations.....                 | 44 |
+
+|           |                                                                                |    |
+|-----------|--------------------------------------------------------------------------------|----|
+| 8.3.1     | Measurement instruments and setup.....                                         | 44 |
+| 8.3.1.1   | Vector Network Analyzer (VNA) setup.....                                       | 44 |
+| 8.3.1.2   | Spectrum Analyzer (SA) setup.....                                              | 45 |
+| 8.3.2     | Validation measurements.....                                                   | 45 |
+| 8.3.2.1   | Power Delay Profile (PDP).....                                                 | 45 |
+| 8.3.2.2   | Doppler/Temporal correlation.....                                              | 47 |
+| 8.3.2.3   | Spatial correlation.....                                                       | 49 |
+| 8.3.2.4   | Cross-polarization.....                                                        | 52 |
+| 8.3.3     | Reporting.....                                                                 | 53 |
+| 8.4       | Channel Model validation results.....                                          | 56 |
+| 8.4.1     | Scope.....                                                                     | 56 |
+| 8.4.2     | Power Delay Profile (PDP).....                                                 | 56 |
+| 8.4.3     | Doppler / Temporal Correlation.....                                            | 62 |
+| 8.4.4     | Spatial correlation.....                                                       | 66 |
+| 8.4.5     | Cross polarization.....                                                        | 68 |
+| 8.4.6     | Summary.....                                                                   | 69 |
+| 8.5       | Channel Model emulation of the Base Station antenna pattern configuration..... | 70 |
+| 9         | Reference antennas and devices testing.....                                    | 70 |
+| 9.1       | Reference antennas design.....                                                 | 70 |
+| 9.2       | Reference devices.....                                                         | 70 |
+| 9.3       | Description of tests with reference antennas and devices.....                  | 70 |
+| 9.3.1     | The Absolute Data Throughput Comparison Framework.....                         | 70 |
+| 9.3.1.1   | Introduction.....                                                              | 70 |
+| 9.3.1.2   | Antenna pattern data format.....                                               | 71 |
+| 9.3.1.3   | Emulation of antenna pattern rotation.....                                     | 72 |
+| 9.3.1.4   | Absolute Data Throughput measurement enabler.....                              | 74 |
+| 9.3.1.5   | Output data format.....                                                        | 75 |
+| 9.3.1.6   | Application of the framework and scenarios for comparison.....                 | 78 |
+| 9.3.1.7   | Proof of concept.....                                                          | 80 |
+| 9.3.1.7.1 | The first scenario, anechoic based.....                                        | 80 |
+
+|           |                                                                                                                                             |     |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------|-----|
+| 9.3.1.7.2 | The second scenario, reverberation chamber based.....                                                                                       | 82  |
+| 9.3.1.7.3 | The third scenario, reverberation chamber and channel emulator based.....                                                                   | 83  |
+| 9.4       | Device positioning.....                                                                                                                     | 85  |
+| 9.4.1     | Handheld UE – Browsing mode.....                                                                                                            | 85  |
+| 9.4.1.1   | MPAC Positioning Guidelines.....                                                                                                            | 85  |
+| 9.4.2     | Handheld UE – Speech mode.....                                                                                                              | 85  |
+| 9.4.2.1   | MPAC Positioning Guidelines.....                                                                                                            | 85  |
+| 9.4.3     | Laptop Mounted Equipment (LME).....                                                                                                         | 85  |
+| 9.4.3.1   | MPAC Positioning Guidelines.....                                                                                                            | 86  |
+| 9.4.4     | Laptop Embedded Equipment (LEE).....                                                                                                        | 86  |
+| 9.4.4.1   | MPAC Positioning Guidelines.....                                                                                                            | 86  |
+| 10        | Measurement results from testing campaigns.....                                                                                             | 86  |
+| 10.1      | Introduction.....                                                                                                                           | 86  |
+| 10.2      | CTIA test campaign.....                                                                                                                     | 86  |
+| 10.2.1    | Description of the test plan.....                                                                                                           | 86  |
+| 10.2.2    | Anechoic chamber method with multiprobe configuration.....                                                                                  | 87  |
+| 10.2.3    | Reverberation chamber method using NIST channel model and using channel emulator with short delay spread low correlation channel model..... | 92  |
+| 10.2.4    | RTS method results.....                                                                                                                     | 100 |
+| 10.3      | 3GPP harmonization test campaign.....                                                                                                       | 104 |
+| 10.3.1    | Description of the test plan.....                                                                                                           | 104 |
+| 10.3.2    | Devices under test.....                                                                                                                     | 105 |
+| 10.3.3    | Measurement uncertainty bound for harmonization.....                                                                                        | 106 |
+| 10.3.4    | Summary of results.....                                                                                                                     | 107 |
+| 10.3.5    | Harmonization outcome.....                                                                                                                  | 111 |
+| 10.3.5a   | Harmonization outcome with device set 3.....                                                                                                | 112 |
+| 10.3.5b   | Harmonization outcome with device set 4.....                                                                                                | 113 |
+| 10.4      | Lab alignment procedures for performance labs.....                                                                                          | 114 |
+| 10.4.1    | General.....                                                                                                                                | 114 |
+| 10.4.2    | Channel model validation data.....                                                                                                          | 114 |
+
+|          |                                                                           |     |
+|----------|---------------------------------------------------------------------------|-----|
+| 10.4.3   | Calibration with a specific set of reference dipoles.....                 | 115 |
+| 10.4.4   | Performance alignment measurements.....                                   | 115 |
+| 10.4.5   | Acceptance criteria.....                                                  | 115 |
+| 11       | Void.....                                                                 | 116 |
+| 12       | MIMO OTA test procedures.....                                             | 116 |
+| 12.1     | Anechoic chamber method with multiprobe configuration test procedure..... | 116 |
+| 12.1.1   | Base Station configuration.....                                           | 116 |
+| 12.1.2   | Channel Models.....                                                       | 116 |
+| 12.1.3   | Device positioning and environmental conditions.....                      | 116 |
+| 12.1.4   | System Description.....                                                   | 116 |
+| 12.1.4.1 | Solution Overview.....                                                    | 116 |
+| 12.1.4.2 | Configuration.....                                                        | 116 |
+| 12.1.4.3 | Calibration.....                                                          | 116 |
+| 12.1.5   | Figure of Merit.....                                                      | 117 |
+| 12.1.6   | Test procedure.....                                                       | 117 |
+| 12.1.6.1 | Initial conditions.....                                                   | 117 |
+| 12.1.6.2 | Test procedure.....                                                       | 117 |
+| 12.1.7   | Measurement Uncertainty budget.....                                       | 118 |
+| 12.2     | Reverberation chamber test procedure.....                                 | 118 |
+| 12.2.1   | Base Station configuration.....                                           | 118 |
+| 12.2.2   | Channel Models.....                                                       | 118 |
+| 12.2.3   | Device positioning and environmental conditions.....                      | 118 |
+| 12.2.4   | System Description.....                                                   | 118 |
+| 12.2.4.1 | Solution Overview.....                                                    | 118 |
+| 12.2.4.2 | Configuration.....                                                        | 118 |
+| 12.2.4.3 | Calibration.....                                                          | 118 |
+| 12.2.5   | Figure of Merit.....                                                      | 118 |
+| 12.2.6   | Test procedure.....                                                       | 118 |
+| 12.2.6.1 | Initial conditions.....                                                   | 118 |
+| 12.2.6.2 | Test procedure.....                                                       | 119 |
+
+|          |                                                      |     |
+|----------|------------------------------------------------------|-----|
+| 12.2.7   | Measurement Uncertainty budget.....                  | 119 |
+| 12.3     | RTS method test procedure.....                       | 119 |
+| 12.3.1   | Base Station configuration.....                      | 119 |
+| 12.3.2   | Channel Models.....                                  | 119 |
+| 12.3.3   | Device positioning and environmental conditions..... | 120 |
+| 12.3.4   | System Description.....                              | 120 |
+| 12.3.4.1 | Solution Overview.....                               | 120 |
+| 12.3.4.2 | Configuration.....                                   | 120 |
+| 12.3.4.3 | Calibration.....                                     | 120 |
+| 12.3.5   | Figure of Merit.....                                 | 120 |
+| 12.3.6   | Test procedure.....                                  | 120 |
+| 12.3.6.1 | Initial conditions.....                              | 120 |
+| 12.3.6.2 | Test procedure.....                                  | 120 |
+| 12.3.7   | Measurement Uncertainty budget.....                  | 121 |
+| 12.4     | Comparison of methodologies.....                     | 121 |
+
+|                                                                                                |            |
+|------------------------------------------------------------------------------------------------|------------|
+| <b>Annex A: eNodeB Emulator Downlink power verification.....</b>                               | <b>124</b> |
+| A.1 Introduction.....                                                                          | 124        |
+| A.2 Test prerequisites.....                                                                    | 124        |
+| A.3 Test Methodology.....                                                                      | 125        |
+| <b>Annex B: Measurement uncertainty budget.....</b>                                            | <b>128</b> |
+| B.1 Measurement uncertainty budget for multiprobe method.....                                  | 128        |
+| B.2 Measurement uncertainty budget contributors for the RTS method.....                        | 131        |
+| B.3 Measurement uncertainty budget for reverberation chamber method.....                       | 133        |
+| B.4 Measurement uncertainty budget for decomposition method.....                               | 135        |
+| B.5 Measurement uncertainty budget for reverberation chamber plus channel emulator method..... | 136        |
+| B.6 Fading channel emulator output uncertainty.....                                            | 138        |
+| B.7 External Amplifiers Uncertainty Terms.....                                                 | 138        |
+| B.7.1 Stability.....                                                                           | 138        |
+| B.7.2 Linearity.....                                                                           | 138        |
+| B.7.3 Noise Figure.....                                                                        | 138        |
+| B.7.4 Mismatch.....                                                                            | 138        |
+| B.7.5 Gain.....                                                                                | 139        |
+| <b>Annex C: Other Environmental Test conditions for consideration.....</b>                     | <b>140</b> |
+| C.1 Scope.....                                                                                 | 140        |
+| C.2 3D isotropic Channel Models.....                                                           | 140        |
+| C.3 Verification of Channel Model implementations.....                                         | 142        |
+| C.3.1 Measurement instruments and setup.....                                                   | 142        |
+| C.3.1.1 Vector Network Analyzer (VNA) setup.....                                               | 142        |
+| C.3.1.2 Spectrum Analyzer (SA) setup.....                                                      | 143        |
+| C.3.2 Validation measurements.....                                                             | 144        |
+| C.3.2.1 Power Delay Profile (PDP).....                                                         | 144        |
+
+|                                                 |                                                               |            |
+|-------------------------------------------------|---------------------------------------------------------------|------------|
+| C.3.2.2                                         | Doppler for 3D isotropic models.....                          | 146        |
+| C.3.2.3                                         | Base Station antenna correlation for 3D isotropic models..... | 148        |
+| C.3.2.4                                         | Rayleigh fading.....                                          | 149        |
+| C.3.2.5                                         | Isotropy for 3D isotropic models.....                         | 153        |
+| C.3.3                                           | Reporting.....                                                | 155        |
+| C.4                                             | Channel model validation results.....                         | 156        |
+| C.4.1                                           | Scope.....                                                    | 156        |
+| C.4.2                                           | Power Delay Profile (PDP) for 3D isotropic models.....        | 156        |
+| C.4.2.1                                         | Setup used by harmonization test lab.....                     | 158        |
+| C.4.3                                           | Doppler for 3D isotropic models.....                          | 160        |
+| C.4.3.1                                         | Setup used by harmonization test lab.....                     | 161        |
+| C.4.4                                           | Base Station antenna correlation for 3D isotropic models..... | 163        |
+| C.4.4.1                                         | Setup used by harmonization test lab.....                     | 164        |
+| C.4.5                                           | Rayleigh fading for 3D isotropic models.....                  | 165        |
+| C.4.5.1                                         | Setup used by harmonization test lab.....                     | 166        |
+| C.4.6                                           | Isotropy for 3D isotropic models.....                         | 167        |
+| C.4.6.1                                         | Setup used by harmonization test lab.....                     | 169        |
+| C.4.7                                           | Summary for 3D Isotropic Models.....                          | 170        |
+| <b>Annex D: Environmental requirements.....</b> |                                                               | <b>171</b> |
+| D.1                                             | Scope.....                                                    | 171        |
+| D.2                                             | Ambient temperature.....                                      | 171        |
+| D.3                                             | Operating voltage.....                                        | 171        |
+| <b>Annex E: DUT orientation conditions.....</b> |                                                               | <b>172</b> |
+| E.1                                             | Scope.....                                                    | 172        |
+| E.2                                             | Testing environment conditions.....                           | 172        |
+| E.2.1                                           | MPAC Positioning Guidelines.....                              | 177        |
+| E.2.2                                           | RTS Positioning Guidelines and test zone dimensions.....      | 181        |
+
+|                                                                                                  |            |
+|--------------------------------------------------------------------------------------------------|------------|
+| <b>Annex F: Calibration.....</b>                                                                 | <b>182</b> |
+| F.1 Scope.....                                                                                   | 182        |
+| F.2 Calibration Procedure – Anechoic chamber method with multiprobe configuration.....           | 182        |
+| F.2.1 Example Calibration Procedure.....                                                         | 182        |
+| F.3 Calibration Procedure – Reverberation chamber method.....                                    | 184        |
+| F.3.1 Measurement of S-parameters through the chamber for a complete stirring sequence.....      | 184        |
+| F.3.2 Calculation of the chamber reference transfer function.....                                | 185        |
+| F.3.3 Cable calibration.....                                                                     | 185        |
+| F.4 Calibration Procedure: RTS method.....                                                       | 186        |
+| F.5 Noise Floor Measurement Procedure – Anechoic chamber method with multiprobe configuration... | 187        |
+| <b>Annex G: Test Volume Validation.....</b>                                                      | <b>189</b> |
+| G.1 Test Volume Validation for the RC+CE Methodology.....                                        | 189        |
+| G.1.1 Test Volume Validation Setup.....                                                          | 189        |
+| G.1.1.1 Type 1 Reverberation Chamber – With Turntable.....                                       | 189        |
+| G.1.1.2 Type 2 Reverberation Chamber – Without Turntable.....                                    | 191        |
+| G.1.2 Test Volume Validation Procedure.....                                                      | 192        |
+| G.1.2.1 Isotropy.....                                                                            | 193        |
+| G.1.2.2 Chamber Statistical Ripple and Repeatability.....                                        | 193        |
+| <b>Annex H: Change history.....</b>                                                              | <b>194</b> |
+
+# Foreword
+
+This Technical Report has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document is the technical report for the work item on MIMO OTA, which was approved at TSG RAN#55 [13]. The scope of the WI is to define a 3GPP methodology or set of comparable methodologies for measuring the radiated performance of multiple antenna reception and MIMO receivers in the UE. The test methodology should be relevant for HSPA and LTE technologies, with particular focus on handheld devices and devices embedded in laptop computers.
+
+RAN WG4 has been working on the study item "Measurement of radiated performance for MIMO and multi-antenna reception for HSPA and LTE terminals" with the objective to define a test methodology for measuring the radiated performance of MIMO and multi-antenna UE reception in UMTS and LTE.
+
+RAN4 has done sufficient work to be confident that the definition of a meaningful test methodology is feasible; however RAN4 does not have sufficient evidence yet to conclude on a single test methodology that would fulfil all requirements for standardisation, and the standardisation of multiple test methodologies may be one eventual outcome, with a view to avoid differences in the decision of what is a "good" or "bad" device from the radiated receiver performance perspective.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] RP-090352: "Proposed new study item: Measurement of radiated performance for MIMO and multi-antenna reception for HSPA and LTE terminals."
+- [3] TD(09) 766, COST2100 SWG 2.2, Braunschweig, Germany, Pekka Kyösti et. al. "Proposal for standardized test procedure for OTA testing of multi-antenna terminals", Elektrobrit.
+- [4] 3GPP TS 34.114: "User Equipment (UE) / Mobile Station (MS) Over The Air (OTA) antenna performance; Conformance testing".
+- [5] 3GPP TS 25.214: "Physical layer procedures (FDD)"
+- [6] TD(09) 742, COST 2100 SWG 2.2, Braunschweig, Germany, February 2009, J. Takada: "Handset MIMO Antenna Testing Using a RF-controlled Spatial Fading Emulator".
+- [7] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding".
+- [8] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures".
+- [9] CTIA: "Test Plan for Wireless Device Over-the-Air Performance ".
+
+- [10] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [11] 3GPP TR 25.914: "Measurements of radio performances for UMTS terminals in speech mode".
+- [12] 3GPP TS 36.521-1: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification Radio transmission and reception; Part 1: Conformance testing"
+- [13] RP-120368: Revised WID on "Verification of radiated multi-antenna reception performance of UEs in LTE/UMTS – performance aspects".
+- [14] B. Yanakiev, J. O. Nielsen, M. Christensen, G. F. Pedersen: "The AAU 3D antenna pattern format-proposal for IC1004".
+- [15] 3GPP TR 25.996: "Spatial channel model for Multiple Input Multiple Output (MIMO) simulations".
+- [16] IEC 61000-4-21: "Electromagnetic compatibility (EMC) – Part 4-21: Testing and measurement techniques – Reverberation chamber test methods", Edition 2.0 2011-01.
+- [17] IEEE.149-1979.R2008: "IEEE Standard Test Procedures for Antennas," IEEE, October 2003.
+- [18] B. Yanakiev, J. Nielsen, M. Christensen, G. Pedersen: "Antennas In Real Environments," EuCAP 2011.
+- [19] 3GPP TS 36.508: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Common test environments for User Equipment (UE) conformance testing".
+- [20] 3GPP TS 36.978: "User Equipment (UE) antenna test function definition for two-stage Multiple Input Multiple Output (MIMO) Over The Air (OTA) test method".
+- [21] P.M. Shankar, "*Introduction to Wireless Systems*," John Wiley & Sons, 2002, Section 2.5.
+- [22] D. A. Hill, "Boundary Fields in Reverberation Chambers", IEEE Transactions on Electromagnetic Compatibility, Vol. 47, No. 2, May 2005.
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |                                                   |
+|----------|---------------------------------------------------|
+| H        | Channel matrix                                    |
+| $\phi$   | Adjacent probe separation angle                   |
+| $\theta$ | Zenith angle in the spherical co-ordinate system  |
+| $\phi$   | Azimuth angle in the spherical co-ordinate system |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply.
+
+An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+|         |                                                     |
+|---------|-----------------------------------------------------|
+| ADTF    | Absolute Data Throughput Framework                  |
+| AoA     | Angle of Arrival                                    |
+| AoD     | Angle of Departure                                  |
+| BS      | Base Station                                        |
+| BSE     | Base Station Emulator                               |
+| BTS     | Base Transceiver Station                            |
+| COST    | Cooperation of Scientific and Technical             |
+| CTIA    | Cellular and Telecommunication Industry Association |
+| DL      | Downlink                                            |
+| DUT     | Device Under Test                                   |
+| FRC     | Fixed Reference Measurement Channel                 |
+| FTP     | File Transfer Protocol                              |
+| HSPA    | High Speed Packet Access                            |
+| HTTP    | HyperText Transfer Protocol                         |
+| LTE     | Long Term Evolution                                 |
+| MCS     | Modulation and Coding Scheme                        |
+| MIMO    | Multiple Input Multiple Output                      |
+| MPAC    | Multi-probe Anechoic                                |
+| OTA     | Over-the-Air                                        |
+| RC      | Reverberation Chamber                               |
+| RC + CE | Reverberation chamber plus channel emulator         |
+| RTS     | Radiated Two-Stage                                  |
+| SCM     | Spatial Channel Model                               |
+| SCME    | Spatial Channel Model Extension                     |
+| SI      | Study Item                                          |
+| SISO    | Single Input Single Output                          |
+| SIR     | Signal-to-Interference Ratio                        |
+| SNR     | Signal-to-Noise Ratio                               |
+| SS      | System Simulator                                    |
+| TBS     | Transport Block Size                                |
+| TTI     | Transmission Time Interval                          |
+| UE      | User Equipment                                      |
+| UDP     | User Datagram Protocol                              |
+| UL      | Uplink                                              |
+| VRC     | Variable Reference Measurement Channel              |
+
+# --- 4 Introduction
+
+## 4.1 Background
+
+The use of MIMO and receiver diversity in the UE is expected to give large gains in downlink throughput performance for HSPA and LTE devices. 3GPP already defined conducted tests for MIMO and multiple antenna receivers (type 1 and type 3 in TS 25.101 for HSPA demodulation), but it is clear that the ability to duplicate these gains in the field is highly dependent on the performance of the receive-antenna system.
+
+At TSG RAN#41, Sep 2008, it was indicated that there is a need for a test methodology to be created with the aim of measuring and verifying the radiated performance of multi-antenna and MIMO receiver in UEs for both HSPA and LTE
+
+devices. As an outcome of the discussion, an LS was sent to COST 2100 SWG2.2 and CTIA ERP to ask them for feedback on their plans/ongoing work in this area, and also the timescales for which such work could be completed to define such a methodology, with particular focus on handheld devices and devices embedded in laptop computers.
+
+Since then, feedback from COST 2100 and CTIA has suggested they are happy to work on this topic. However, given that 3GPP is the customer for this work as well as being a potential contributor, it is important to aim for commonly-accepted measurement and test methodology to be used across the industry.
+
+## 4.2 Work item objective
+
+The high level objective of this work item is to define a test methodology (ies) for verifying the radiated performance of multiple antenna reception in the UE and such methodology shall be able to:
+
+- Verify the radiated "Over-The-Air" (OTA) performance of multiple antenna reception in the UE.
+- Accurately able to reflect MIMO and SIMO performance under realistic MIMO and SIMO channel conditions. Be able to distinguish between UEs of "Good" and "Bad" multi-Rx antenna OTA performance, and offer a good reflection of the likely experience in the field.
+- Offer good reliability, repeatability and an acceptable level of measurement uncertainty.
+
+Such test methodology(ies) shall enable performance verification for:
+
+- Handheld devices, devices embedded in laptop computers, and other devices (such as M2M equipment).
+- All transmission modes of LTE and HSDPA, including spatial multiplexing (MIMO) and single spatial layer operation. However the transmission modes used in the test shall be defined as part of the work.
+  - Initially tests shall use of LTE Transmission Mode 3, Fixed Reference Channel, and forced Rank 2. As the work progresses, other transmission modes of LTE and HSPA shall be introduced.
+  - The utilization of Variable Reference Channels and other-cell interference shall also be studied at a later stage.
+
+The following is required for the analysis phase of this work item:
+
+- In order to compare results across the different methods, absolute throughput shall be used as the Figure of Merit.
+- In order to analyse and accurately validate a method(s) the following work shall be performed:
+  - eNodeB settings shall be agreed.
+  - Realistic MIMO conditions and realistic channel models shall be identified to be used as a reference radio environment.
+  - The MIMO conditions and channel models shall be validated for the proposed test methods.
+  - Calibration of the power levels in the methodology shall be performed.
+  - The absolute throughput measured for each test method shall be compared with the absolute throughput measured in the reference radio environment, in order to identify the capability of each method to provide a measurement result that matches what is observed in realistic environments.
+  - In order to minimize the variables associated with testing of production UEs with unknown antenna characteristics, utilize reference antennas in combination with a known UE baseband receiver (verified via conducted RF tests with and without channel impairments). This is intended to verify whether the characteristics of the receive antenna design (i.e. correlation, gain imbalance, etc) affecting receiver performance can be accurately distinguished by proposed test methods.
+
+In the event that more than one test methodology is agreed to be standardised, differences between methodologies in the decision of what is a "good" or "bad" device from the radiated receiver performance perspective shall be avoided.
+
+When selecting the method(s) for specification for LTE MIMO, applicability to LTE-SIMO UMTS-SIMO/MIMO shall be described.
+
+During the course of this Work Item, maintain ongoing communication with COST and CTIA MOSG to ensure industry coordination on this topic and to distribute tasks according to expertise or resource availability.
+
+TSG RAN should contact TSG GERAN to get feedback on the applicability of such a test methodology for GERAN.
+
+## 4.3 High level requirements
+
+The following high level requirements are agreed by RAN4:
+
+1. Measurement of radiated performance for MIMO and multi-antenna reception for HSPA and LTE terminals must be performed over-the-air, i.e. without RF cable connections to the DUT.
+
+NOTE 1: DUTs to the test house will have accessibility to temporary antenna port for conducted purposes.
+
+NOTE 2: Temporary antenna port is used to assess to DUT receiver.
+
+NOTE 3: UE special function to measure antenna pattern is not desirable for MIMO OTA purposes.
+
+2. The MIMO OTA method(s) must be able to differentiate between a good terminal and a bad terminal in terms of MIMO OTA performance.
+3. The desired primary Figure Of Merit (FOM) is absolute throughput. This will easily allow meaningful comparison of the ability of different methods to evaluate MIMO OTA performance.
+
+# --- 5 Performance metrics
+
+## 5.1 Figure of Merits
+
+Absolute throughput performance is used in order to be able to compare the different proposed methodologies in their ability to distinguish good and bad MIMO devices.
+
+The performance metric applies to both HSPA and LTE system.
+
+Other Figure of Merits and their applicability on the assessment of MIMO performance is for further study.
+
+### 5.1.1 Definition of MIMO throughput
+
+MIMO throughput is defined here as the time-averaged number of correctly received transport blocks in a communication system running an application, where a Transport Block is defined in the reference measurement channel. From OTA perspective, this is also called MIMO OTA throughput.
+
+The MIMO OTA throughput is measured at the top of physical layer of HSPA and LTE system. Therefore, this is also measured at the same point as in the conductive measurement setup: under the use of FRC, the SS transmit fixed-size payload bits to the DUT. The DUT signals back either ACK or NACK to the SS. The SS then records the following:
+
+- ~ Number of ACKs,
+- ~ Number of NACKs, and
+- ~ Number of DTX TTIs
+
+Hence the MIMO (OTA) throughput can be calculated as
+
+where Transmitted TBS is the Transport Block Size transmitted by the SS, which is fixed for a FRC during the measurement period. MeasurementTime is the total composed of successful TTIs (ACK), unsuccessful TTIs (NACK) and DTX-TTIs.
+
+The time-averaging is to be taken over a time period sufficiently long to average out the variations due to the fading channel. Therefore, this is also called the average MIMO OTA throughput. The throughput should be measured at a time when eventual start-up transients in the system have evanescend.
+
+### 5.1.2 Definition of Signal-to-Interference Ratio (SIR)
+
+Applicability of SIR to MIMO OTA performance evaluation is FFS.
+
+This definition is applicable to MIMO OTA test cases where control of the signal to interference ratio (SIR) is required (i.e. DUT throughput characterized as a function of SIR shall require control of SIR within the test volume as described in the sub-sections that follow). For test cases where SIR control is not required (i.e. throughput characterized as a function of signal power incident to the DUT antennas, such as RS EPRE) this definition is not applicable.
+
+In real world scenarios the mobile will experience an interference floor higher than the device noise floor. As a consequence, the methodology for quantifying MIMO OTA performance of a device may have to include the use of an external interferer signal. MIMO OTA testing is useful for a situation where, in general, a high signal level is received that is not close to the sensitivity level of the UE and the interference floor is dominated by inter-cell interference and/or other interferers and not the UE noise floor. In most UE performance testing, interference is modelled as AWGN for conducted testing. This proposal intends to align with this assumption and use AWGN for the interference signal.
+
+From a system level point of view, the omnidirectional (isotropic) and uncorrelated nature of the interfering signal to the wanted signal is a crucial assumption. Injecting a noise signal that is correlated to the wanted faded signal is neither a scenario that is typically found in the network nor a scenario for which the UE modem is designed. As a result, we propose the methodology for injecting an omnidirectional (isotropic) and uncorrelated interferer signal.
+
+#### 5.1.2.1 SIR Control for Multi-Probe Anechoic Chamber Methodology
+
+The interference level necessary to achieve a given SIR inside the test zone shall be generated as an independent process at each antenna probe with equal power, regardless of the signal power transmitted through that probe. The SIR shall be decreased by increasing the AWGN power while keeping the signal level constant.
+
+To validate the control of SIR, the measurement setup shown in Figure 5.1.2.1-1 below may be used.
+
+![Diagram of the anechoic chamber multi-cluster MIMO OTA setup. A Radio Communication Tester is connected to a Channel Emulator (where interference is injected). The output of the Channel Emulator is connected to an Amplifier Box. The Amplifier Box is connected to a MIMO Ring. The MIMO Ring contains multiple Probe Antennas and a Reference Antenna. The Reference Antenna is connected to a Spectrum Analyzer.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg)
+
+The diagram illustrates the setup for verifying SIR level in an anechoic chamber. On the left, a 'Radio Communication Tester' is connected to a 'Channel Emulator (interference injected at or after emulator output)'. The output of the Channel Emulator is connected to an 'Amplifier Box'. The Amplifier Box is connected to a 'MIMO Ring'. The MIMO Ring is a circular structure containing multiple 'Probe Antennas' and a 'Reference Antenna' at the center. The Reference Antenna is connected to a 'Spectrum Analyzer'.
+
+Diagram of the anechoic chamber multi-cluster MIMO OTA setup. A Radio Communication Tester is connected to a Channel Emulator (where interference is injected). The output of the Channel Emulator is connected to an Amplifier Box. The Amplifier Box is connected to a MIMO Ring. The MIMO Ring contains multiple Probe Antennas and a Reference Antenna. The Reference Antenna is connected to a Spectrum Analyzer.
+
+**Figure 5.1.2.1-1: Verifying SIR level in the anechoic chamber multi-cluster MIMO OTA setup**
+
+The actual system components shown in the diagram, such as amplifier box or the source of the omnidirectional interferer signal, may or may not be present as shown.
+
+The procedure below shall be used to verify SIR control inside the test zone for a given target SIR.
+
+Verification procedure for establishing SIR control:
+
+1. Configure the spectrum analyser with the settings given in Table 5.1.2.1-1 below
+2. Load the target channel model into the channel emulator (e.g. SCME UMa, SCME UMi) and start the emulation
+3. Configure the system gains for the LTE signal and injected interfering signal paths to achieve the target SIR
+4. Disable interfering signal injection (depending on the system configuration this may be configured within the channel emulator itself or in an external signal generator)
+5. Connect a vertically polarized reference dipole to the spectrum analyser via a cable and place inside the chamber at the center of the test zone
+6. Measure the received power with the spectrum analyser over a duration sufficient to achieve statistical significance as defined in clause 12.1.6.2 and record the value as
+
+$$P_{\text{SIG\_MEAS\_VER}}$$
+
+7. Compensate for the loss of the cable ( $\alpha_{\text{CABLE}}$ ) and the gain of the dipole ( $G_{\text{DIPOLE}}$ ) such that
+
+$$P_{\text{SIG\_VER}} = P_{\text{SIG\_MEAS\_VER}} - \alpha_{\text{CABLE}} - G_{\text{DIPOLE}}$$
+
+8. Repeat steps 5 to 7 with the magnetic loop and get
+
+$$P_{\text{SIG\_HOR}} = P_{\text{SIG\_MEAS\_HOR}} - \alpha_{\text{CABLE}} - G_{\text{LOOP}}$$
+
+9. Calculate the total signal power received as
+
+$$P_{\text{SIG\_TOTAL}} = P_{\text{SIG\_VER|LINEAR}} + P_{\text{SIG\_HOR|LINEAR}}$$
+
+10. Disable the LTE signal source and enable interference injection (depending on the system configuration this may be configured within the channel emulator itself or in an external signal generator)
+
+11. Connect a reference dipole to the spectrum analyser via a cable and place inside the chamber at the center of the test zone
+
+12. Measure the received interfering signal power with the spectrum analyser over aduration sufficient to achieve statistical significance and record the value as
+
+$$P_{\text{INT\_MEAS\_VER}}$$
+
+13. Compensate for the loss of the cable ( $\alpha_{\text{CABLE}}$ ) and the gain of the dipole ( $G_{\text{DIPOLE}}$ ) such that
+
+$$P_{\text{INT\_VER}} = P_{\text{INT\_MEAS\_VER}} - \alpha_{\text{CABLE}} - G_{\text{DIPOLE}}$$
+
+14. Repeat steps 11 to 13 with the magnetic loop and get
+
+$$P_{\text{INT\_HOR}} = P_{\text{INT\_MEAS\_HOR}} - \alpha_{\text{CABLE}} - G_{\text{LOOP}}$$
+
+15. Calculate the total interfering signal power received as
+
+$$P_{\text{INT\_TOTAL}} = P_{\text{INT\_VER|LINEAR}} + P_{\text{INT\_HOR|LINEAR}}$$
+
+16. Calculate the achieved signal to interference ratio such that
+
+$$\text{SIR}_{\text{ACHIEVED}} = P_{\text{SIG\_TOTAL}} - P_{\text{INT\_TOTAL}}$$
+
+and validate that it matches the target SIR.
+
+**Table 5.1.2.1-1: Spectrum analyzer settings for SIR control verification**
+
+| Item                                                                                                                                       | Unit | Value                                                                  |
+|--------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------------------------------------------------------|
+| Center frequency                                                                                                                           | MHz  | Downlink center frequency<br>in 3GPP TS 36.508<br>as required per band |
+| Span                                                                                                                                       | MHz  | 9 <sup>1</sup>                                                         |
+| Resolution BW                                                                                                                              | kHz  | 30                                                                     |
+| Video BW                                                                                                                                   | MHz  | ≥10                                                                    |
+| Number of points                                                                                                                           |      | > 200                                                                  |
+| Number of averages                                                                                                                         |      | Sufficient to achieve statistical significance as defined above        |
+| NOTE 1: Span is shown using the assumption of a 10 MHz LTE RF channel BW and would be adjusted accordingly for an alternate RF channel BW. |      |                                                                        |
+
+Care shall be taken to ensure that the signal level measurement in step 6 and the interfering signal level measurement in step 12 are sufficiently above the noise floor of the measurement system as to not impact the final SIR level. A horizontally polarized reference dipole may be used as opposed to the magnetic loop as long as the theta gain pattern is properly accounted for.
+
+#### 5.1.2.2 SIR Control for the reverberation chamber method
+
+Additive White Gaussian Noise (AWGN) is used as interference for the SIR-controlled test case. Figure 5.1.2.2-1 shows an example setup for adding AWGN to the test environment with the injection point for the AWGN highlighted. The AWGN noise power used to create the desired SIR within the test volume shall be generated as an independent process. It is represented by faded noise driven in an isotropic fashion. The AWGN is injected into the reverberation chamber using a separate chamber antenna and the fading of the signal and the noise will be uncorrelated. The SIR is computed as a long-term average.
+
+![Diagram of an example setup for SIR-controlled test scenario for the reverberation chamber methodology.](79e1709a7317ead45379cbb8ff3ba802_img.jpg)
+
+The diagram illustrates a test setup for a reverberation chamber (RC) methodology. A large rectangular box labeled 'RC' contains a 'DUT' (Device Under Test) mounted on a rotating turntable. Inside the RC, there are two grey rectangular panels, one on the top wall and one on the right wall, with arrows indicating signal reflections. Three antennas are positioned at the bottom of the RC, connected to a common horizontal bus. This bus is connected to an 'AWGN' (Additive White Gaussian Noise) generator and a 'ComTester' unit. The ComTester has a screen and three output ports labeled '1', '2', and '3', which are connected to the three antennas. The DUT is shown as a small rectangular device on a circular turntable with a curved arrow indicating rotation.
+
+Diagram of an example setup for SIR-controlled test scenario for the reverberation chamber methodology.
+
+**Figure 5.1.2.2-1: Example setup for SIR-controlled test scenario for the reverberation chamber methodology**
+
+#### 5.1.2.3 SIR Control for the reverberation chamber plus channel emulator method
+
+AWGN will be used as interference for the SIR-controlled test case. Figure 5.1.2.3-1 shows an example setup for adding AWGN to the test environment with the injection points for the AWGN highlighted. The AWGN noise power used to create the desired SIR within the test volume shall be generated as an independent process with equal power at each output of the channel emulator. It is represented by an un-faded noise driven in an isotropic fashion. The AWGN is combined with the signal at the output of the channel emulator (after the channel emulator fading) but before the signal is fed to the reverberation chamber antennas. The combined signal and AWGN is then fed into the chamber with the same chamber antennas. The SIR is computed as a long-term average.
+
+![Figure 5.1.2.3-1: Example setup for SIR-controlled test scenario for the reverberation chamber and channel emulator methodology. The diagram shows a 'ComTester' at the top with three ports (1, 2, 3) connected to an 'Input' bus. This bus enters a 'Fading' block. The 'Fading' block has four outputs labeled S1, S2, S3, and S4. Each output is summed with an AWGN signal (N1, N2, N3, N4) at a summing node. The summed signals then enter a 'CE' (Channel Emulator) block. The 'CE' block has four outputs labeled 'Output' which are connected to a 'RC' (Reverberation Chamber). Inside the 'RC', there is a 'DUT' (Device Under Test) on a rotating turntable. The 'RC' also contains two reflectors and a downward-pointing arrow indicating the signal path.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+Figure 5.1.2.3-1: Example setup for SIR-controlled test scenario for the reverberation chamber and channel emulator methodology. The diagram shows a 'ComTester' at the top with three ports (1, 2, 3) connected to an 'Input' bus. This bus enters a 'Fading' block. The 'Fading' block has four outputs labeled S1, S2, S3, and S4. Each output is summed with an AWGN signal (N1, N2, N3, N4) at a summing node. The summed signals then enter a 'CE' (Channel Emulator) block. The 'CE' block has four outputs labeled 'Output' which are connected to a 'RC' (Reverberation Chamber). Inside the 'RC', there is a 'DUT' (Device Under Test) on a rotating turntable. The 'RC' also contains two reflectors and a downward-pointing arrow indicating the signal path.
+
+**Figure 5.1.2.3-1: Example setup for SIR-controlled test scenario for the reverberation chamber and channel emulator methodology**
+
+#### 5.1.2.4 SIR Control for the two-stage methodology
+
+The two-stage method is fundamentally different from the multi-probe boundary array method and this has a significant impact on how omnidirectional AWGN is generated and validated.
+
+In the two-stage method the AWGN is added digitally to the baseband signals. The goal is to emulate omnidirectional AWGN at the UE antennas. Since the signals generated by the second stage of two-stage method represent the signals after applying the effect of the receive antennas this has implications for the addition of AWGN.
+
+If uncorrelated AWGN is added to the second stage signals for each UE receiver this creates a slightly easier test environment where each receiver sees uncorrelated noise. However, when the UE is placed in an actual omnidirectional noise field, the noise reaching each of the receivers is correlated by the same amount as the antennas are correlated. The impact of using uncorrelated AWGN depends on the antennas in question. Highly correlated antennas would see the same AWGN signal at each receiver but very low correlated antennas would expect see uncorrelated AWGN which is easier to process. For typical devices the performance difference has been measured at around 0.5 dB.
+
+To fully represent the impact of omnidirectional AWGN on the wanted signals being generated for each receiver after the antennas, it is therefore necessary to correlate the AWGN according to the antenna correlation for an isotropic field.
+
+To validate the control of SIR, the measurement setup shown in Figure 5.1.2.4-1 below may be used.
+
+![Diagram illustrating the setup for verifying SIR level for the RTS method. A Base Station Emulator is connected to a Channel Emulator. The Channel Emulator outputs two signals, labeled V (Vertical) and H (Horizontal), which are fed into an Anechoic chamber. Inside the Anechoic chamber, there is a Reference dipole antenna.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+The diagram shows a 'Base Station Emulator' block connected to a 'Channel Emulator' block. The 'Channel Emulator' has two output ports labeled 'V' (Vertical) and 'H' (Horizontal). These outputs are connected to two separate antenna symbols inside a large rectangle labeled 'Anechoic chamber'. To the right of these antennas, inside the chamber, is another antenna symbol labeled 'Reference dipole'.
+
+Diagram illustrating the setup for verifying SIR level for the RTS method. A Base Station Emulator is connected to a Channel Emulator. The Channel Emulator outputs two signals, labeled V (Vertical) and H (Horizontal), which are fed into an Anechoic chamber. Inside the Anechoic chamber, there is a Reference dipole antenna.
+
+**Figure 5.1.2.4-1: Verifying SIR level for the RTS method**
+
+Note: The signals from the vertical polarization and horizontal polarization have a different meaning from the multi-probe method. For the multi-probe method, the signal from vertical polarization antenna represents the vertical polarized signal in the real propagation environment. But for RTS method, the signal from the vertical polarization antenna represents the signal intended for one receiver, which has had the dual-polarized channel environment and antenna pattern applied. The same is true for the horizontal antenna. Thus the signals from each probe antenna include AWGN components from both polarizations.
+
+The actual system components shown in the diagram are indicative of functions and may or may not be integrated.
+
+The procedure below shall be used to verify SIR control for a given target SIR.
+
+1. Configure the spectrum analyzer with the settings given in Table 5.1.2.4-1 below
+2. Load the target channel model into the channel emulator (e.g. SCME UMa, SCME UMi) and start the emulation
+3. Configure the system gains for the LTE signals and interfering signal to achieve the target SIR
+4. Disable the interfering signal
+5. Connect a vertically polarized reference dipole to the spectrum analyzer via a cable and place inside the chamber at the center of the test zone
+6. Measure the received power with the spectrum analyzer over a duration sufficient to achieve statistical significance as defined in clause 12.3.6.2 and record the value as
+
+$$P_{\text{SIG\_MEAS\_VER}}$$
+
+7. Compensate for the loss of the cable ( $\alpha_{\text{CABLE}}$ ) and the gain of the dipole ( $G_{\text{DIPOLE}}$ ) such that
+
+$$P_{\text{SIG\_VER}} = P_{\text{SIG\_MEAS\_VER}} - \alpha_{\text{CABLE}} - G_{\text{DIPOLE}}$$
+
+8. Repeat steps 5 to 7 with the magnetic loop and get
+
+$$P_{\text{SIG\_HOR}} = P_{\text{SIG\_MEAS\_HOR}} - \alpha_{\text{CABLE}} - G_{\text{LOOP}}$$
+
+9. Disable the LTE signal source and enable interference injection (depending on the system configuration this may be configured within the channel emulator itself or in an external signal generator)
+
+10. Connect a reference dipole to the spectrum analyzer via a cable and place inside the chamber at the center of the test zone
+11. Measure the received interfering signal power with the spectrum analyzer over a duration sufficient to achieve statistical significance and record the value as
+
+$$P_{\text{INT\_MEAS\_VER}}$$
+
+12. Compensate for the loss of the cable ( $\alpha_{\text{CABLE}}$ ) and the gain of the dipole ( $G_{\text{DIPOLE}}$ ) such that
+
+$$P_{\text{INT\_VER}} = P_{\text{INT\_MEAS\_VER}} - \alpha_{\text{CABLE}} - G_{\text{DIPOLE}}$$
+
+13. Repeat steps 10 to 12 with the magnetic loop and get
+
+$$P_{\text{INT\_HOR}} = P_{\text{INT\_MEAS\_HOR}} - \alpha_{\text{CABLE}} - G_{\text{LOOP}}$$
+
+14. Calculate the achieved signal to interference ratio for vertical polarization branch as
+
+$$\text{SIR}_{\text{ACHIEVED\_VER}} = P_{\text{SIG\_VER}} - P_{\text{INT\_VER}}$$
+
+Calculate the achieved signal to interference ratio for horizontal polarization branch as
+
+$$\text{SIR}_{\text{ACHIEVED\_HOR}} = P_{\text{SIG\_HOR}} - P_{\text{INT\_HOR}}$$
+
+and validate that  $\text{SIR}_{\text{ACHIEVED\_VER}}$  and  $\text{SIR}_{\text{ACHIEVED\_HOR}}$  matches the target SIR.
+
+**Table 5.1.2.4-1: Spectrum analyzer settings for SIR control verification**
+
+| Item               | Unit | Value                                                                  |
+|--------------------|------|------------------------------------------------------------------------|
+| Center frequency   | MHz  | Downlink center frequency<br>in 3GPP TS 36.508<br>as required per band |
+| Span               | MHz  | 9 <sup>1</sup>                                                         |
+| Resolution BW      | kHz  | 30                                                                     |
+| Video BW           | MHz  | $\geq 10$                                                              |
+| Number of points   |      | $> 200$                                                                |
+| Number of averages |      | Sufficient to achieve statistical significance as defined above        |
+
+NOTE 1: Span is shown using the assumption of a 10 MHz LTE RF channel BW and would be adjusted accordingly for an alternate RF channel BW.
+
+Care shall be taken to ensure that the signal level measurement in step 6 and the interfering signal level measurement in step 11 are sufficiently above the noise floor of the measurement system as to not impact the final SIR level. A horizontally polarized reference dipole may be used as opposed to the magnetic loop as long as the theta gain pattern is properly accounted for.
+
+## 5.2 Averaging of throughput curves
+
+There are different possibilities how to average the curves where throughput (TP) was recorded as function of downlink (DL) power (expressed in RS EPRE) or of Signal-to-Interference (SIR) level. Averages shall be calculated by the following formula.
+
+### 5.2.1 Average of power levels
+
+The averaging of DL power (or SIR) is the first possibility. The power levels are summed similar to the formula used for TIS evaluation, i.e. using the inverse of power. The formula to use is:
+
+For every selected TP value  $y$  a corresponding power level  $P_n(y)$  can be found, and summed over all  $N$  conditions. The subscript "inv" is used to indicate that the inverse sum of power values is taken.
+
+The power levels have to be converted to linear values in mW before the summation takes place, and the average then can be reconverted to dBm / 15 kHz for RS EPRE or dB for SIR.
+
+Since the recording of the TP curves is done with fixed steps in power, only few TP values are available. In order to calculate the correct average, the TP curves have to be interpolated, and a fixed set of  $y$  values for TP can be used for generating the curve of  $P_{avg}(y)$ .
+
+In the case that a curve was not recorded down to 0 % TP, it shall be extrapolated from the point taken with lowest TP to TP = 0 using the same power level.
+
+If a curve did not reach nominal TP, it shall be extrapolated it in a way that it would reach nominal TP at the lowest power level where it was reaching its individual maximum TP value.
+
+The average TP curve shall only be calculated up to a TP value which equals to the average of all individual maximum TP values.
+
+# --- 6 Candidate measurement methodologies
+
+## 6.1 Void
+
+## 6.2 Void
+
+## 6.3 Downlink measurement methodologies
+
+The methodologies defined in this subclause are candidate methodologies being studied for the purpose of defining procedures for performance testing of over the air performance.
+
+Final test procedure for the approved test methodology or methodologies is described in clause 12.
+
+### 6.3.1 Methodologies based on Anechoic RF Chamber
+
+An OTA method based on the use of an Anechoic RF Chamber is described consisting of a number of test antenna probes located in the chamber transmitting signals with temporal and spatial characteristics for testing multiple antenna devices.
+
+This clause describes the methodologies based on Anechoic RF Chamber, where a number of test antennas are located in different positions of the chamber, and the Device Under Test (DUT) is located at center position. The DUT is tested over the air without RF cables.
+
+#### 6.3.1.1 Candidate Solution 1
+
+An OTA method based on the use of an Anechoic RF Chamber is described consisting of a number of test antennas located in the chamber transmitting signals with temporal and spatial characteristics for testing multiple antenna devices. The method consists of a number of test antennas located in different positions of the chamber, and the device under test (DUT) is located at the center position. The DUT is tested over the air without RF cables.
+
+The Anechoic chamber techniques creates a realistic geometric based spatio-temporal-polarimetric radio channel for testing MIMO performance using Geometric based stochastic channel models as defined in Clause 8.2.
+
+The components of the solution include:
+
+- Anechoic Chamber
+- System Simulator (SS)
+- N channel RF emulator, with OTA Channel Generation Features
+- N linearly polarized antenna elements configured V, H or co-located V&H or slant X polarizations
+- K azimuthally separated antenna positions with predefined angles at radius R
+- Channel model definition for each test case
+
+An illustration of an anechoic chamber is shown in Figure 6.3.1.1-1 below.
+
+![Figure 6.3.1.1-1: N-element Anechoic Chamber approach. A 3D perspective view of an anechoic chamber with a Device Under Test (DUT) in the center. The DUT is a small cylinder. Six vertical arrows, representing antenna elements, are arranged around the DUT at different azimuthal positions. The chamber walls are lined with wave-absorbing material, shown as a wavy surface.](55fb58e14ec092ccc4fe111de0dc6278_img.jpg)
+
+Figure 6.3.1.1-1: N-element Anechoic Chamber approach. A 3D perspective view of an anechoic chamber with a Device Under Test (DUT) in the center. The DUT is a small cylinder. Six vertical arrows, representing antenna elements, are arranged around the DUT at different azimuthal positions. The chamber walls are lined with wave-absorbing material, shown as a wavy surface.
+
+**Figure 6.3.1.1-1: N-element Anechoic Chamber approach (Absorbing tiles and cabling not shown)**
+
+![Figure 6.3.1.1-2: OTA system level block diagram. A block diagram showing the signal flow. A block labeled 'SS' (System Simulator) outputs an 'M' branch signal to a block labeled 'MxN MIMO Channel Emulator'. The emulator outputs an 'N' channel signal to an 'Anechoic Chamber'. Inside the chamber, the signal is distributed to multiple antenna elements, represented by '+' symbols. A 'Return Path' is shown as a line with an arrow pointing from the chamber back to the 'SS' block.](9b686adccf125267a013fa25721231a3_img.jpg)
+
+Figure 6.3.1.1-2: OTA system level block diagram. A block diagram showing the signal flow. A block labeled 'SS' (System Simulator) outputs an 'M' branch signal to a block labeled 'MxN MIMO Channel Emulator'. The emulator outputs an 'N' channel signal to an 'Anechoic Chamber'. Inside the chamber, the signal is distributed to multiple antenna elements, represented by '+' symbols. A 'Return Path' is shown as a line with an arrow pointing from the chamber back to the 'SS' block.
+
+**Figure 6.3.1.1-2: OTA system level block diagram**
+
+A system level block diagram is shown in Figure 6.3.1.1-2, which includes the SS to generate the M branch MIMO signal, and an RF Channel Emulator with an OTA Channel Generation Feature to properly correlate, fade, scale, delay, and distribute the signal to each test probe in the chamber. For the selected environmental conditions modelled by the SCME UMa and UMi channel models, the minimum setup configuration can be described as below:
+
+**Table 6.3.1.1-1: Example of a minimum setup for Boundary Array implementations using the Anechoic Chamber Methodology**
+
+|                                     | Full Ring         | Single Cluster                            |
+|-------------------------------------|-------------------|-------------------------------------------|
+| Minimum number of antenna positions | 8                 | 3                                         |
+| Antenna spacing                     | 45°               | Determined on the setup                   |
+| Applicable channel model            | SCME UMa/SCME UMi | Single Cluster UMa and Single Cluster UMi |
+
+The full SCME or Multi-Cluster channel models are defined in Clause 8.2. The Single-Cluster model, which is not part of the set of channel models validated in clause 8, would be based on the channel models defined in section 8.2 with a set of dithered AoAs around zero degrees.
+
+##### 6.3.1.1.1 Concept and configuration
+
+For MIMO OTA modelling the geometric channel models are mapped into the fading emulator, converting the geometric channel models into the emulator tap coefficients. This process is illustrated in Figure 6.3.1.1.1-1.
+
+![Figure 6.3.1.1.1-1: Modelling process flowchart. The process starts with 'Software (Matlab) Implementation' which contains a 'Geometric Channel Model' (SCM/SCME/WINNER/IMT-Advanced). This is followed by an 'OTA modelling tool (mapping software)', which then connects to a 'Fading emulator'. The 'Fading emulator' is connected to an 'OTA Chamber'.](356eb99ab9489bbd647223390a913903_img.jpg)
+
+```
+
+graph LR
+    subgraph Software [Software (Matlab) Implementation]
+        GCM[Geometric Channel Model  
+SCM/SCME/WINNER/  
+IMT-Advanced]
+    end
+    Software --> OTA[OTA modelling tool  
+(mapping software)]
+    OTA --> FE[Fading emulator]
+    FE --> OC((OTA Chamber))
+  
+```
+
+Figure 6.3.1.1.1-1: Modelling process flowchart. The process starts with 'Software (Matlab) Implementation' which contains a 'Geometric Channel Model' (SCM/SCME/WINNER/IMT-Advanced). This is followed by an 'OTA modelling tool (mapping software)', which then connects to a 'Fading emulator'. The 'Fading emulator' is connected to an 'OTA Chamber'.
+
+**Figure 6.3.1.1.1-1: Modelling process**
+
+The setup of OTA chamber antennas with eight antenna positions is depicted in Figure 6.3.1.1.1-2. The DUT is at the center, and the antennas are in a circle around the DUT with uniform spacing (e.g. 45° with 16 elements arranged in 8 positions, where each position contains a vertically and horizontally polarized antenna pair). Denoting directions of  $K$  OTA antennas with  $\theta_k$ ,  $k = 1, \dots, K$ , and antenna spacing in the angle domain with  $\Delta\theta$ . Each antenna is connected to a single fading emulator output port. In the figure, for example, antenna  $A_{1V}$  denotes the first OTA antenna position and Vertically (V) polarized element,  $A_{8H}$  denotes the eight OTA antenna position and horizontally (H) polarized element, etc.
+
+![Diagram of an OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas. The antennas are arranged in a circle around a central point. Each antenna is labeled with a subscript (1-8) and a polarization indicator (H for horizontal, V for vertical). The antennas are labeled A1H, A1V, A2H, A2V, A3H, A3V, A4H, A4V, A5H, A5V, A6H, A6V, A7H, A7V, A8H, and A8V. The angle between the horizontal axis and the line to the first antenna is labeled Δθ.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+Diagram of an OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas. The antennas are arranged in a circle around a central point. Each antenna is labeled with a subscript (1-8) and a polarization indicator (H for horizontal, V for vertical). The antennas are labeled A1H, A1V, A2H, A2V, A3H, A3V, A4H, A4V, A5H, A5V, A6H, A6V, A7H, A7V, A8H, and A8V. The angle between the horizontal axis and the line to the first antenna is labeled Δθ.
+
+NOTE: In the drawing the V-polarized elements are actually orthogonal to the paper (azimuth plane)
+
+**Figure 6.3.1.1.1-2: OTA chamber antenna setup with eight uniformly spaced dual polarized chamber antennas**
+
+##### 6.3.1.1.2 Scalability of the methodology
+
+The number of antennas is scalable. In theory, there is no upper limit and the lower limit is one. The required number of channels depends on three main aspects: channel model, DUT size, and polarization. The key question is how accurately the channel model is emulated. Based on the quiet zone discussion, it was proposed to use 8 antennas in the case of single polarization and 16 antennas in the case of dual polarization. However, for single cluster case, fewer antennas may be enough. On the other hand, if elevation is needed, the antenna number will be higher. Additionally, the antenna positions can be adjusted to optimize the accuracy with limited number of antennas.
+
+Another aspect is the channel model. Most of the Geometry-based Stochastic Channel Models (GSCMs) are two-dimensional, i.e. azimuth plane only, but the proposed MIMO OTA concept is not limited to the azimuth plane. It can also be extended to elevation plane, when we talk about 3D MIMO OTA. However, the 3D MIMO OTA is rather complex and it does not provide very much additional information about the DUT. Therefore, 3D MIMO OTA can be considered as one future development, but it is not the recommended solution in the beginning of MIMO OTA testing.
+
+Downscaling of the proposed method is more attractive due to the possibility to save the cost of the test system. Full SCME requires multiple antennas, but single cluster SCME can be implemented with lower number of antennas than full SCME. The same downscaling benefits of the single-cluster model apply based on DUT size. The difference between full SCME and Single Cluster model is depicted in Figure 6.3.1.1.2-1. Basically the only difference is that the mean Angle-of-Arrival (AoA) of each cluster is turned to the same primary direction. If all AoA's were identical, it would be a problematic case as it locks all like-angle sub-paths together with identical Doppler, which results in a breakdown of the model. With slight dithering as in the example that the AoAs = [0 -1 1 -2 2 -3] degrees, the angle spread after dithering increases from 35.00 to 35.02 degrees, which is not significant, however the model now performs as expected. Obviously, one primary cluster requires a lower number of antennas than multiple clusters especially when angular spread is narrow, e.g. 35 degrees. The number of fading channels is the same as the number of antennas. Therefore, single cluster SCME would require less fading channels as well.
+
+![Figure 6.3.1.1.2-1: Full SCME vs. Single Cluster model. The diagram is split into two parts. Part (a) 'Full SCME' shows a central 'DUT' (Device Under Test) surrounded by four clusters of antennas, each labeled 'PAS'. Green arrows point from the DUT to each cluster, and from each cluster to a small bar chart. Part (b) 'Single Cluster' shows a 'DUT' with a single cluster of antennas labeled 'PAS' pointing towards it, and a single bar chart representing the power distribution.](28d75f39a24203712ee907b32cf0bbe5_img.jpg)
+
+Figure 6.3.1.1.2-1: Full SCME vs. Single Cluster model. The diagram is split into two parts. Part (a) 'Full SCME' shows a central 'DUT' (Device Under Test) surrounded by four clusters of antennas, each labeled 'PAS'. Green arrows point from the DUT to each cluster, and from each cluster to a small bar chart. Part (b) 'Single Cluster' shows a 'DUT' with a single cluster of antennas labeled 'PAS' pointing towards it, and a single bar chart representing the power distribution.
+
+Figure 6.3.1.1.2-1: Full SCME vs. Single Cluster model
+
+##### 6.3.1.1.3 Test conditions
+
+This candidate solution supports testing of different figure of merits and is applicable to any 3GPP release. It supports different channel models from SCM to IMT-Advanced. Due to its generality, it does not restrict the test conditions. However, for simplicity, it is good to start from downlink throughput testing.
+
+The downlink throughput testing can be done e.g. in the following manner.
+
+BS transmits signal through a radio channel emulator. This signal is routed to several antennas in anechoic chamber. The DUT is placed at center of the chamber and the performance is measured from the DUT.
+
+- OTA antennas are located along a circle around the DUT;
+- The circular geometry is needed because we need signal from many directions at the same time (requirement from the channel models).
+
+The test steps can be, e.g., according to [3] or as follows:
+
+- 1) Calibrate the full system with a test signal;
+- 2) Set the first test case (e.g. channel model) to the fading emulator;
+- 3) Generate test signal by the communication tester / BS emulator;
+- 4) Measure the DUT performance (downlink throughput);
+- 5) If the performance exceeds the specified limit, the DUT passes the test case;
+- 6) If all test cases done, go to step 7. Otherwise, set the next test case (e.g. channel model) to the fading emulator and go back to step 3.
+- 7) If DUT passed all the test cases, the DUT passes the full MIMO OTA test;
+- 8) If DUT failed in at least one test case, the DUT failed the full MIMO OTA test.
+
+#### 6.3.1.2 Void
+
+#### 6.3.1.3 Candidate solution 3
+
+The principle of two-stage MIMO OTA method is based on the assumption that the DUT far-field antenna radiation pattern will contain all the necessary information for evaluation of the DUT's antenna's performance like radiation power, efficiency and correlation and that with channel model approaches, the influence of antenna radiation pattern can be correctly incorporated into the channel model. Thus the method will first measure the DUT's MIMO antenna patterns and then convolve the measured antenna patterns with the chosen MIMO OTA channel models for real-time emulation. The resulting test signal generated by the channel emulator and coupled back into the DUT receivers represents the signal that the DUT receivers would have seen if the DUT had been placed in the desired radiated field. Thus an ideal implementation of the two-stage method provides the same results as an ideal implementation of the boundary antenna array method.
+
+The two-stage method can be used to measure the following figures of merit:
+
+- 1) Throughput
+- 2) TRP and TRS
+- 3) CQI, BLER
+- 4) Antenna efficiency and MEG
+- 5) Antenna correlation, MIMO channel capacity.
+
+In order to accurately measure the antenna pattern of the intact device, the DUT chipset needs to support received amplitude and relative phase measurements of the antennas. The validity of antenna pattern measurement is predicated on the assumption that for the frequency being tested, the DUT antenna pattern is static. Devices that can alter their antenna pattern in real time as a function of the radiated environment – sometimes referred to as active antennas – is FFS as noted in Table 12.4-1. The method of coupling the base station emulator and DUT can be through the standard temporary antenna connectors (conducted two-stage method) or by using a specially calibrated radiated connection (radiated two-stage or RTS method) to do the test on throughput, etc., to test how the MIMO antennas will influence the performance. The conducted method of coupling is straightforward but does not capture the impact of radiated leakage from the DUT transmit antennas to the DUT receive antennas, thus in its current form without additional interference estimation the conducted method of coupling in the second stage is not proposed for use in conformance testing. Its description is included for historical completeness of the development of the two-stage method. The radiated method of coupling in the second stage does fully capture radiated leakage and is the method defined for conformance testing in Clause 12.
+
+##### 6.3.1.3.1 Concept and configuration
+
+The assumption of the two-stage MIMO OTA method is that the measured far field antenna pattern of the DUT's multiple antennas can fully capture the mutual coupling of the multiple antenna arrays and their influence on radiated performance.
+
+Thus to do the two-stage MIMO OTA test, the antenna patterns of the antenna array needs to be measured accurately in the first stage. In order to accurately measure the antenna pattern of the intact device, the chipset needs to support amplitude and relative phase measurements of the antennas. To achieve this, two new UE measurements have been defined called Reference Signal Antenna Power (RSAP) and Reference Signal Relative Antenna Phase (RSARP). These measurements are defined in TR 36.978 [20].
+
+**Stage 1:** The measurement of the DUT's multiple antennas takes place in a traditional anechoic chamber set up as described in Annex A.2 in [4], where the DUT is put into the chamber and each antenna element's complex far zone pattern is measured using the RSAP and RSARP measurements defined in [20]. The influence of human body loss can also be measured by attaching the DUT to a SAM head and or hand phantom when doing the antenna pattern measurements. The characteristics of the SAM phantom are specified in Annex A.1 of [4]. The chamber is equipped
+
+with a positioner, that makes it possible to perform full 3-D far zone pattern measurements for both Tx and Rx radiated performance. As specified in A.2 of [4] the measurement antenna shall be able to measure two orthogonal polarizations (typically linear theta ( $\theta$ ) and phi ( $\phi$ ) polarizations as shown in Figure 6.3.1.3.1-1).
+
+![Figure 6.3.1.3.1-1: The coordinate system used in the measurements. The diagram shows a Device Under Test (DUT) represented by a human head silhouette mounted on a vertical stand. A probe antenna is positioned to the right of the DUT. A dashed vertical line represents the z-axis. A dashed horizontal line represents the x-axis. A curved arrow indicates the theta (θ) angle, measured from the z-axis towards the probe antenna. Another curved arrow indicates the phi (φ) angle, measured around the z-axis. The probe antenna is shown with a series of triangular elements, suggesting a horn or array antenna.](5bd2e409e2ed67e06109635cc3a56e25_img.jpg)
+
+Figure 6.3.1.3.1-1: The coordinate system used in the measurements. The diagram shows a Device Under Test (DUT) represented by a human head silhouette mounted on a vertical stand. A probe antenna is positioned to the right of the DUT. A dashed vertical line represents the z-axis. A dashed horizontal line represents the x-axis. A curved arrow indicates the theta (θ) angle, measured from the z-axis towards the probe antenna. Another curved arrow indicates the phi (φ) angle, measured around the z-axis. The probe antenna is shown with a series of triangular elements, suggesting a horn or array antenna.
+
+**Figure 6.3.1.3.1-1: The coordinate system used in the measurements**
+
+**Stage 2:** Convolve the antenna patterns measured in stage 1 with the chosen MIMO channel model, using a channel emulator and then use the resulting signal to perform the OTA throughput test. The signal is coupled into the DUT using either a cabled or radiated connection.
+
+The two-stage method is illustrated in Figure 6.3.1.3.1-2. In the conducted two-stage method shown in Figure 6.3.1.3.1-2 the BS emulator is connected to the MIMO channel emulator and then to the DUT's temporary antenna ports via approved RF cables. These ports are the standard ones provided for conducted conformance tests. The alternative to using a conducted connection is to use a calibrated radiated connection in an anechoic environment as shown in Figure 6.3.1.3.1-3 is the radiated two-stage (RTS) method. This coupling technique exploits the Eigen modes of the transmission channel in the anechoic chamber to provide isolated radiated connections between the probe antennas and each DUT receiver after the DUT antenna. Throughput with the DUT's MIMO antenna influence can be measured using either coupling method. However, only the radiated coupling method intrinsically includes the effects of DUT self-interference and is the method defined for conformance testing in Clause 12.
+
+There are two different approaches to convolve the DUT antenna patterns with MIMO channel model.
+
+- a) Apply antenna patterns to geometric (Ray-based) channel models. Ray-based models support arbitrary antenna patterns under predefined channel modes in a natural way as described above. If Ray-based models like SCME are specified to be used for MIMO OTA testing, then the channel emulator needs to support SCME channel model emulation and convolution with the measured antenna patterns.
+- b) Apply antenna patterns to correlation-based channel models. With a correlation matrix calculation method for arbitrary antenna patterns under multipath channel conditions, the correlation matrix and the antenna imbalance can be calculated and then emulated by the channel emulator.
+
+![Figure 6.3.1.3.1-2: Proposed conducted two-stage test methodology for MIMO OTA test. The diagram shows two stages. The first stage is a 'Test Chamber' containing a 'Reference Antenna' and a 'MIMO DUT' surrounded by 'Anechoic Material'. A 'BS Emulator' is connected to the Reference Antenna. The second stage is a 'Conducted' setup where a 'Channel Emulator' and a 'BS Emulator' are connected to the 'MIMO DUT'. The output is measured as 'BER, FER, H, R'. An 'Antenna Patterns' block is shown between the two stages.](e05b36c0d46549e681ce6581422c66b2_img.jpg)
+
+Figure 6.3.1.3.1-2: Proposed conducted two-stage test methodology for MIMO OTA test. The diagram shows two stages. The first stage is a 'Test Chamber' containing a 'Reference Antenna' and a 'MIMO DUT' surrounded by 'Anechoic Material'. A 'BS Emulator' is connected to the Reference Antenna. The second stage is a 'Conducted' setup where a 'Channel Emulator' and a 'BS Emulator' are connected to the 'MIMO DUT'. The output is measured as 'BER, FER, H, R'. An 'Antenna Patterns' block is shown between the two stages.
+
+Figure 6.3.1.3.1-2: Proposed conducted two-stage test methodology for MIMO OTA test
+
+An example implementation of the radiated method of connecting to the EUT in the second stage is shown in Figure 6.3.1.3.1-3.
+
+![Figure 6.3.1.3.1-3: Alternative connection for the radiated two-stage (RTS) test methodology for MIMO OTA test. The diagram shows a 'Base Station emulator' connected to a 'Channel emulator'. The Channel emulator has two outputs labeled 'Polar V' and 'Polar H' entering an 'Anechoic Chamber'. Inside the chamber, these signals are received by a 'UE' (User Equipment). A feedback line connects the UE back to the Base Station emulator.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg)
+
+Figure 6.3.1.3.1-3: Alternative connection for the radiated two-stage (RTS) test methodology for MIMO OTA test. The diagram shows a 'Base Station emulator' connected to a 'Channel emulator'. The Channel emulator has two outputs labeled 'Polar V' and 'Polar H' entering an 'Anechoic Chamber'. Inside the chamber, these signals are received by a 'UE' (User Equipment). A feedback line connects the UE back to the Base Station emulator.
+
+Figure 6.3.1.3.1-3: Alternative connection for the radiated two-stage (RTS) test methodology for MIMO OTA test
+
+Figure 6.3.1.3.1-3 shows the radiated coupling method for the second stage. Two probe antennas with polarization V and H are co-located in the anechoic chamber. Note, unlike in the first stage where the V and H probes are used at different times, in the second stage both V and H probes are used simultaneously. An example implementation of this would be the dual polarized configuration described in Annex A.2.2 of [4]. The only difference between the conducted second stage and the radiated second stage is to replace the RF cables with the radiated channel inside the chamber. Due to the propagation channel in the chamber, signals transmitted from each probe antenna are received by both DUT antennas which is different from the cable conducted case where the signals are isolated by the cables. However, by precoding the transmitted signals using spatial multiplexing techniques it is possible by calculating the radiated channel matrix and by applying its inverse to the transmitted signals, to create an identity matrix allowing the transmitted signals to be received independently at each DUT receiver after the DUT antenna. This precoding recreates the equivalent of the isolated cable conducted conditions at the receiver but but with radiated self-interference now included.
+
+The establishment of the radiated connection is explained as follows. Assume  $x_1$  and  $x_2$  are the transmitted signals from the base station emulator, after applying the desired channel model and convolution with the complex antenna pattern we get:
+
+$$f(x_1) \text{ and } f(x_2) = \begin{pmatrix} h_{11} & h_{12} \\ h_{21} & h_{22} \end{pmatrix}$$
+
+The radiated channel matrix between the probe antennas and the DUT antennas is
+
+If the channel emulator applies the inverse of the radiated channel matrix  $H^{-1} = \begin{pmatrix} \alpha & \beta \\ \gamma & \delta \end{pmatrix}$  to  $f(x_1)$  and  $f(x_2)$ , the signal received after the DUT antennas is same as the cable-conducted method as follows:
+
+$$\begin{pmatrix} y_1 \\ y_2 \end{pmatrix} = \begin{pmatrix} h_{11} & h_{12} \\ h_{21} & h_{22} \end{pmatrix} \begin{pmatrix} \alpha & \beta \\ \gamma & \delta \end{pmatrix} \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix} = \begin{pmatrix} 1 & 0 \\ 0 & 1 \end{pmatrix} \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix} = \begin{pmatrix} f(x_1) \\ f(x_2) \end{pmatrix}$$
+
+The above example of RTS using two probe antennas is applicable to UE with two Rx antennas. For UE with  $> 2$  Rx antennas, the RTS method is FFS.
+
+##### 6.3.1.3.2 Test conditions
+
+This candidate solution supports testing of different figure of merits. It is also applicable for any 3GPP Release, and even for other standards.
+
+This method can reuse existing SISO OTA anechoic chambers to make the antenna pattern measurements; the channel emulator number is required to match the number of device receiver inputs regardless of the complexity of the chosen channel model, the method is consequently easily scalable to higher order MIMO due to the reduced number of instruments required; the channel models are highly accurate due to being implemented electronically and are also fully flexible and can be altered to suit any desired operating conditions such as indoor-outdoor, high or low Doppler spread, high or low delay spread, beam width, in 2D or full 3D etc.
+
+This method requires the chipset in the DUT to support amplitude and relative phase measurements of the antennas as defined in TR 36.978 [20]. The conducted coupling method in the second stage cannot directly measure DUT self-desensitization since the antenna pattern measurement does not take account of possible signal leakage from the device transmit antennas into the receive antennas. The radiated coupling method for the second stage does fully characterize any DUT self-desensitization and is the method specified in Clause 12 for conformance testing.
+
+The detailed RTS test procedure can be found in Subclause 12.3.
+
+##### 6.3.1.3.3 Overview of calibration procedures specific to the RTS method
+
+The efficacy of the RTS method is based on the ability to accurately measure the DUT complex antenna pattern and establish an isolated radiated MIMO connection in the second stage.
+
+The output of the first stage is a relative antenna pattern of unknown gain and linearity. The calibration of the antenna pattern occurs in the second stage.
+
+###### Selection of orientation for the second stage
+
+The second stage starts with the selection of a DUT orientation at which to establish a radiated MIMO connection to the DUT. This orientation is chosen from any point on the measured pattern at which the optimal isolation between the streams can be achieved by application of the inverse channel matrix. A degree of isolation between the received streams for most antenna patterns is achieved through use of different transmit polarizations or by using separate antennas. Improved isolation will be achieved by choosing a DUT orientation that avoids nulls in the antenna pattern. The algorithm for selecting the optimal orientation is left up to implementation. The only criterion is that the selected orientation achieves sufficient isolation.
+
+###### Calculation of the inverse transmission matrix
+
+Once an orientation is selected an unfaded SISO connection is established from the first probe antenna and the RSAP for each DUT antenna and the RSARP between the antennas is measured. These measurements are repeated using the second probe antenna. From these measurements the optimal transmission matrix from the probe antennas to the DUT receiver can be calculated. When the inverse of this matrix is applied to the probes it is possible to transmit a wanted signal from the first probe to the first receiver and from the second probe to the second receiver with minimal crosstalk.
+
+###### Calibration of the measured antenna pattern gain
+
+The impact of the unknown gain of the DUT antennas then de-embedded from the test system by setting the downlink power for each probe to the level that returns the same RSAP measurement that was reported for that probe polarization during the first stage at the orientation being used for the second stage. This nulling process is the reason why the absolute accuracy of the RSAP measurement is unimportant since the antenna gain is represented by the change in downlink power necessary to achieve the same RSAP report for the first and second stage at the same DUT orientation.
+
+For example using a -60 dBm nominal level in the first stage for the V antenna assume the DUT for one orientation returns RSAP for receiver 1 of -67 dBm representing an uncorrected gain of -7 dB. This report includes the true gain of the antenna at the V polarization for this orientation (assume -4 dB) plus an unknown error in the RSAP absolute accuracy (-3 dB). In the second stage antenna calibration step, a wanted signal of -60 dBm is transmitted, adjusted to -53 dBm to de-embed the uncorrected gain of -7 dB and the RSAP measured. If the RSAP accuracy were perfect the DUT would report -60 dBm but since the true antenna gain at that orientation is -4 dB, the reported RSAP is higher at -57 dBm. The difference between the first stage RSAP measurement and the second stage RSAP with the uncorrected gain applied then represents the true antenna gain at that orientation referred to the known accuracy of the downlink signal.
+
+###### Validation of the isolation between the streams
+
+Once the RSAP absolute error has been measured and removed from the measured antenna pattern the isolation of the streams in the second stage can be measured. This could be done with static signals but what matters is the isolation achieved under the more difficult dynamic fading conditions. The isolation can be measured by establishing a connection and, with the channel model and antenna pattern applied, measure the difference in dB between the RSAP reported for each DUT receiver. For a DUT to be usable with the RTS method a minimum isolation has to be achieved of 15 dB averaged over at least 200 RSAP measurements.
+
+###### Monotonicity check of RSAP and RSARP
+
+Once the minimum isolation of the radiated second stage has been validated it is necessary to validate the linearity of RSAP and RSARP measurements over the operating range -60 dB, to -80 dBm and +/- 180 degrees. This starts with a monotonicity check using a [1] dB step size for RSAP and a [5] degree step size for RSARP. The step sizes of the monotonicity check determine the accuracy to which the measurements can be linearized. If the monotonicity check fails the RTS method is not usable for the DUT.
+
+###### Linearization of RSAP and RSARP
+
+Once monotonicity has been validated, the linearity of RSAP can be measured. This is done from the orientation of the peak antenna gain over the range -60 dBm to -80 dBm. The linearity shall be < [1] dB. The linearity of RSARP shall be within [5] degrees over the range  $\pm 180$  degrees measured at -60 dBm and -80 dBm. If the uncorrected RSAP or RSARP results do not meet the linearity requirements, calculate and apply a transfer function to the measured patterns to ensure the necessary linearity.
+
+#### 6.3.1.4 Candidate solution 4
+
+##### 6.3.1.4.1 Concept and configuration
+
+In this method an assessment of the antenna's performance in MIMO or Diversity operation is performed. Several simplifications are used in order to optimise the testing.
+
+A test of the UE in an anechoic environment with the help of a base station emulator is proposed, with a limited number of faded channels and transmitting antennas, and in a simple geometrical set-up.
+
+The underlying principle is to decompose the task for evaluating MIMO performance. It combines the radiated measurements in the anechoic chamber where no fading is applied with conducted measurements with fading. The total performance of the UE is decomposed into these two steps, and therefore we name it decomposition approach. Figure 6.3.1.4.1-1 illustrates this approach.
+
+![Diagram of decomposition approach for 2x2 LTE MIMO showing three scenarios: Real World, Conducted, and Radiated.](6e15fc9ea763541c5913d26f85072ae1_img.jpg)
+
+The diagram illustrates three decomposition approaches for 2x2 LTE MIMO testing:
+
+- Real World:** A Base Station is connected to a Real-World Channel, which is then connected to a User Equipment (UE) containing a 2x2 MIMO Receiver.
+- Conducted:** A Base Station Emulator is connected to a Dynamic Fading (Fading Simulator), which is then connected to a UE containing a 2x2 MIMO Receiver.
+- Radiated:** A Base Station Emulator is connected to a chamber with No Fading Profiles (applied in chamber), which is then connected to a UE containing a 2x2 MIMO Receiver.
+
+Diagram of decomposition approach for 2x2 LTE MIMO showing three scenarios: Real World, Conducted, and Radiated.
+
+Figure 6.3.1.4.1-1: Diagram of decomposition approach for 2x2 LTE MIMO
+
+##### 6.3.1.4.2 Decomposition approach
+
+To determine the throughput results for the overall MIMO device performance, the following key measurements are needed, as shown in Figure 6.3.1.4.2-1:
+
+- Baseline: the conducted measurement with channel model of the identity matrix
+- Conducted: the conducted measurement with the real-world channel model
+- Radiated: the average of the radiated measurements for a set of antenna constellations
+
+![Graph of Rel. Throughput vs DL Power and corresponding measurement diagrams for Baseline, Conducted, and Radiated scenarios.](6243dbbad1ae96ba4862675d1b3d3443_img.jpg)
+
+The figure shows a graph of Relative Throughput versus Downlink (DL) Power, with three curves representing different measurement scenarios:
+
+- Baseline:** Represented by a dashed blue line, showing the highest throughput performance.
+- Conducted:** Represented by a solid red line, showing lower throughput due to real-world channel fading.
+- Radiated:** Represented by a solid blue line, showing throughput performance in a radiated environment.
+
+Accompanying diagrams show the setup for each scenario: Baseline (identity matrix channel model), Conducted (dynamic fading simulator), and Radiated (no fading profiles in chamber).
+
+Graph of Rel. Throughput vs DL Power and corresponding measurement diagrams for Baseline, Conducted, and Radiated scenarios.
+
+Figure 6.3.1.4.2-1: Key measurements for Decomposition Approach
+
+From these measurements, the receiver MIMO efficiency and the antenna MIMO efficiency are determined as illustrated in Figure 6.3.1.4.2-2. The receiver MIMO efficiency is defined as the difference between the baseline conducted test and the conducted test with dynamic fading as a function of throughput, Figure 6.3.1.4.2-2 (a). Similarly, the antenna MIMO efficiency is defined as the difference between the baseline conducted test and the radiated test for all throughput levels, Figure 6.3.1.4.2-2 (b)
+
+![Graph of Rel. Throughput vs DL Power for Receiver MIMO Efficiency calculation, comparing Baseline and Conducted scenarios.](70fa50a74183d4d85213f463bf9d84ea_img.jpg)
+
+This figure, labeled (a), focuses on Receiver MIMO Efficiency. It includes a graph of Relative Throughput versus DL Power and two measurement diagrams:
+
+- Graph:** Shows the difference between the Baseline (dashed blue line) and Conducted (solid red line) throughput levels, indicated by horizontal double-headed arrows at various throughput points.
+- Diagrams:** Compare the Baseline setup (identity matrix channel model) with the Conducted setup (dynamic fading simulator).
+- Receiver MIMO Efficiency:** Labeled above the diagrams, indicating the metric being derived from the difference between these two setups.
+
+Graph of Rel. Throughput vs DL Power for Receiver MIMO Efficiency calculation, comparing Baseline and Conducted scenarios.
+
+![Figure 6.3.1.4.2-2: Definition of (a) receiver MIMO and (b) antenna MIMO efficiencies. (a) shows a graph of Relative Throughput vs. DL Power with three red arrows indicating throughput increments. (b) shows two diagrams: 'Baseline' (Base Station Emulator to 2x2 MIMO Receiver) and 'Radiated' (Base Station Emulator to No Fading Profiles (equal in channel) to 2x2 MIMO Receiver).](c53adc66eab40abd5f8b9107d950ad04_img.jpg)
+
+Figure 6.3.1.4.2-2 consists of two parts. Part (a) is a graph showing 'Rel. Throughput' on the y-axis and 'DL Power' on the x-axis. A red curve starts at the origin and rises, with three horizontal red double-headed arrows indicating throughput levels at different power points. Part (b) is titled 'Antenna MIMO Efficiency' and shows two diagrams. The top diagram, labeled 'Baseline', shows a 'Base Station Emulator' connected to a '2x2 MIMO Receiver' via a dashed box labeled 'UE'. The bottom diagram, labeled 'Radiated', shows a 'Base Station Emulator' connected to a 'No Fading Profiles (equal in channel)' block, which is then connected to a '2x2 MIMO Receiver' via a dashed box labeled 'UE'.
+
+Figure 6.3.1.4.2-2: Definition of (a) receiver MIMO and (b) antenna MIMO efficiencies. (a) shows a graph of Relative Throughput vs. DL Power with three red arrows indicating throughput increments. (b) shows two diagrams: 'Baseline' (Base Station Emulator to 2x2 MIMO Receiver) and 'Radiated' (Base Station Emulator to No Fading Profiles (equal in channel) to 2x2 MIMO Receiver).
+
+**Figure 6.3.1.4.2-2: Definition of (a) receiver MIMO and (b) antenna MIMO efficiencies**
+
+The relative Figure Of Merit (FOM) for the UE MIMO performance is subsequently defined as the UE MIMO efficiency that is the sum of the receiver and antenna MIMO efficiencies. By adding this efficiency to the baseline throughput curve, the absolute FOM for the UE MIMO performance, i.e., decomposed throughput curve as a function of DL power level, can be obtained as shown in 6.3.1.4.2-3.
+
+![Figure 6.3.1.4.2-3: Illustration of the decomposed throughput curve calculation. It shows the equation: UE MIMO Efficiency = Antenna MIMO Efficiency + Receiver MIMO Efficiency. Below the equation is a graph of Relative Throughput vs. DL Power with three horizontal arrows (black, red, blue) representing the decomposition. To the right are four diagrams: 'Real World', 'Radiated', 'Conducted', and 'Baseline'.](010f64870d9b7d9e04dc4059b1cf5f45_img.jpg)
+
+Figure 6.3.1.4.2-3 illustrates the decomposition of throughput curve calculation. At the top, an equation shows 'UE MIMO Efficiency' equal to the sum of 'Antenna MIMO Efficiency' and 'Receiver MIMO Efficiency'. Below this is a graph of 'Rel. Throughput' vs. 'DL Power' with three horizontal arrows (black, red, blue) representing the decomposition. To the right of the graph are four diagrams stacked vertically: 'Real World' (Base Station to Real-World Channel to 2x2 MIMO Receiver), 'Radiated' (Base Station Emulator to No Fading Profiles (equal in channel) to 2x2 MIMO Receiver), 'Conducted' (Base Station Emulator to Dynamic Fading (equal in channel) to 2x2 MIMO Receiver), and 'Baseline' (Base Station Emulator to 2x2 MIMO Receiver).
+
+Figure 6.3.1.4.2-3: Illustration of the decomposed throughput curve calculation. It shows the equation: UE MIMO Efficiency = Antenna MIMO Efficiency + Receiver MIMO Efficiency. Below the equation is a graph of Relative Throughput vs. DL Power with three horizontal arrows (black, red, blue) representing the decomposition. To the right are four diagrams: 'Real World', 'Radiated', 'Conducted', and 'Baseline'.
+
+**Figure 6.3.1.4.2-3: Illustration of the decomposed throughput curve calculation**
+
+##### 6.3.1.4.3 Conducted test
+
+In the conducted tests, measurements with different channel models have to be performed.
+
+The most basic Channel Model (CM) is the identity static channel matrix without fading.
+
+This matrix provides a frequency-flat transfer characteristic that does not change over time. Since non-diagonal elements of the channel matrix are zero, each RF port of the UE receives a single LTE data stream. This ideal CM characterizes the noise figure of the MIMO receiver and acts as a "baseline" for further testing.
+
+Another test has to be performed with the CM selected. Typically the channel models are either based on SCME UMa or UMi. Since the channel models are applied in conducted mode, the spatial information of the base station antenna correlation is calculated numerically and implemented as coefficient alpha in the fading model. The coefficient beta describing the correlation at the UE side is set to zero.
+
+##### 6.3.1.4.4 Radiated test
+
+The two-channel method is covering the radiated part of the test where the performance of the UE's antenna subsystem is evaluated. It is using two probe antennas and one azimuth positioner in order to cover a large number of different angle-of-arrival constellations. In each constellation also the polarizations of the two probe antennas are defined.
+
+For an RX MIMO measurement (TM2 or TM3), the two signals from the base station emulator are routed directly to the probe antennas with the chosen polarization.
+
+In order to assess the radiated performance of the MIMO antenna system in 3D, the UE shall be tested for a set of antenna constellations uniformly covering the sphere and generating a wide variety of AoAs. In the radiated test the constellations are categorized as spatial constellations, i.e, the azimuth orientation of the UE and the elevation positions of the two DL antennas and as polarization constellations, i.e., the set of polarizations of the DL antennas used to transmit the LTE MIMO streams. Figure 6.3.1.4.4-1 highlights the key parameters for each constellation category.
+
+![Figure 6.3.1.4.4-1: Overview of (a) spatial and (b) polarization constellations. (a) shows spatial constellations with elevation angles theta_1 (EL) and theta_2 (EL) for DL1 and DL2, and azimuth angle phi (AZ) for the UE. (b) shows polarization constellations with phi-pol and theta-pol for DL1 and DL2, and azimuth angle phi (AZ) for the UE. Both diagrams include a UE model, probe antennas, and a test system.](6be06b7dc72bb42afcb3465394667c3b_img.jpg)
+
+Figure 6.3.1.4.4-1 consists of two sub-diagrams, (a) and (b), illustrating different antenna constellations for radiated testing. Both diagrams show a User Equipment (UE) model on a turntable, two probe antennas (DL1 and DL2) mounted on a spherical structure, and a test system connected to them.
+
+(a) Spatial constellations: This diagram shows the spatial arrangement of the antennas. The elevation angles for the two downlink (DL) antennas are labeled as  $\theta_1$  (EL) and  $\theta_2$  (EL). The azimuth angle for the UE is labeled as  $\phi$  (AZ). The test system is connected to the probe antennas and the UE.
+
+(b) Polarization constellations: This diagram shows the polarization states of the antennas. A legend indicates that  $\phi$ -pol (horizontal line) and  $\theta$ -pol (vertical line) are used for the DL antennas. The azimuth angle for the UE is labeled as  $\phi$  (AZ). The test system is connected to the probe antennas and the UE.
+
+Figure 6.3.1.4.4-1: Overview of (a) spatial and (b) polarization constellations. (a) shows spatial constellations with elevation angles theta\_1 (EL) and theta\_2 (EL) for DL1 and DL2, and azimuth angle phi (AZ) for the UE. (b) shows polarization constellations with phi-pol and theta-pol for DL1 and DL2, and azimuth angle phi (AZ) for the UE. Both diagrams include a UE model, probe antennas, and a test system.
+
+**Figure 6.3.1.4.4-1: Overview of (a) spatial and (b) polarization constellations**
+
+An optimized constellation approach determines a set of constellations.
+
+The algorithm used has been written specifically for the decomposition approach.
+
+A total of 128 constellations have been identified to be sufficient in order to sample the antenna performance.
+
+For each constellation, a curve of throughput as a function of DL power level or SNR is recorded.
+
+At the end of the test, i.e., 128 constellations, an average of all curves is determined that represents the FOM for the MIMO antenna subsystem performance for a complete set of 3D AoAs.
+
+##### 6.3.1.4.5 Possible extensions of the decomposition method
+
+There are several possible extensions of the method briefly addressed in this Clause.
+
+- The channel information available in the UE can be used to deliver a quick answer to the test system about the current receive quality. If necessary, an explicit scaling from one quantity onto the other one can be made.
+- In case of an RX diversity measurement the signal from the base station emulator has to be routed via a two-channel fading to the two probe antennas in the chamber in order to decorrelate the signals.
+
+- In addition of the movements of the probe antennas and the azimuth positioner, the UE may be tilted by some additional rotation around the horizontal axis.
+- As a special case it is also possible to test with one antenna where each polarization is transmitting one MIMO data stream.
+- As an alternative to moving the antennas by mechanically rotating them it is possible to arrange the antennas in a horizontal plane and to move one antenna with respect to the other in order to vary the angle difference between the two. In that case the positioner rotating the UE will be designed in a more complex way.
+- If one wants to extend this method to 3D AoA, a third antenna outside the plane can be used.
+
+The OTA performance can better be described by taking statistical evaluations into account. If, for example, for each test point a relative throughput value is obtained as function of subcarrier power, one can plot the results for different points in a histogram and to obtain some CCDF indicating the conditions for getting at least a given throughput value.
+
+#### 6.3.1.5 Candidate solution 5
+
+The RF-controlled spatial fading emulator can directly reproduce a multipath radio propagation environment by radio waves emitted from antenna-probe units arranged around a handset tested. Moreover, the emulator has an advantage of measuring radiation characteristics of a handset antenna for the present OTA testing in 3GPP as well as the multipath testing because of its RF operation [6].
+
+##### 6.3.1.5.1 Concept and configuration
+
+The RF-controlled spatial fading emulator can directly reproduce multipath radio propagation environments both in Line-Of-Sight (LOS) and Non Line-Of-Sight (NLOS) situations by radio waves emitted from antenna probes arranged around a DUT. Thus, the emulator can be easily used for measurement of the MIMO characteristics of a HSPA/LTE multiple antenna device in a multipath fading environment.
+
+Figure 6.3.1.5.1-1 (a) and (b) show the configuration and arrangement of the antenna probes of the RF spatial fading emulator in an anechoic chamber. In this method, the DUT is designated as any device that possesses multiple antennas, including a HSPA or LTE device.
+
+The height of DUT from the floor of the anechoic chamber is  $H$ . The DUT can also be placed at a rotatable turn-table in order to set and vary the horizontal angle of the DUT. The DUT is surrounded by  $N$  numbers of antenna probes. The distance between DUT and each antenna probe is  $r$ . The antenna probe consists of two antennas. The one is a half-wavelength dipole set vertically for emitting the vertically-polarized wave and the other is a horizontally-located half-wavelength dipole for the horizontally-polarized wave. This configuration of the antenna-probe unit can represent a cross polarization power ratio, XPR, of incoming wave. The separation between vertical and horizontal antennas is  $d$ . The height of the antenna probe from the anechoic chamber floor is  $h$ . The distance between the ring of antenna probes and the walls of anechoic chamber is  $D$ . (Note if the anechoic chamber is not square, then  $D_1$  and  $D_2$  are used).
+
+A reference antenna probe is designated so that it can be used to determine the direction of motion of DUT. This parameter is designated as  $\phi$ . The circular angle between antenna probes from the centre of the ring (i.e. DUT) is with respect to the reference antenna probe.
+
+![Figure 6.3.1.5.1-1(a): Experimental Setup. This diagram shows a schematic of the experimental setup. A person stands inside an anechoic chamber, surrounded by scattering units labeled 0, 1, 2, 3, 4, 5, and N-1. The distance from the center to a scattering unit is r, and the height of the scattering unit is h. The total height of the chamber is H. The distance between scattering units is p. To the right, a photograph shows a scattering unit and a receiver. Below the chamber, a block diagram shows the signal flow: Transmitter -> Power Divider -> Phase Shifter -> Attenuator -> D/A Converter -> Computer.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg)
+
+Figure 6.3.1.5.1-1(a): Experimental Setup. This diagram shows a schematic of the experimental setup. A person stands inside an anechoic chamber, surrounded by scattering units labeled 0, 1, 2, 3, 4, 5, and N-1. The distance from the center to a scattering unit is r, and the height of the scattering unit is h. The total height of the chamber is H. The distance between scattering units is p. To the right, a photograph shows a scattering unit and a receiver. Below the chamber, a block diagram shows the signal flow: Transmitter -> Power Divider -> Phase Shifter -> Attenuator -> D/A Converter -> Computer.
+
+(a) Experimental Setup
+
+![Figure 6.3.1.5.1-1(b): Arrangement of the antenna probes. This diagram shows a circular arrangement of antenna probes. A central point is labeled (DUT)R. Probes are arranged in a circle of radius r. Probe #1 is at an angle of 0 degrees. Probe #i is at an angle of phi_i. Probe #3 is at an angle of phi_0. Probe #N is at an angle of phi_shift. The Doppler frequency is labeled f_D. The distance between probes is labeled x. The probes are labeled Scattering units.](4ff00a489baaa34a0c01070de1d613db_img.jpg)
+
+Figure 6.3.1.5.1-1(b): Arrangement of the antenna probes. This diagram shows a circular arrangement of antenna probes. A central point is labeled (DUT)R. Probes are arranged in a circle of radius r. Probe #1 is at an angle of 0 degrees. Probe #i is at an angle of phi\_i. Probe #3 is at an angle of phi\_0. Probe #N is at an angle of phi\_shift. The Doppler frequency is labeled f\_D. The distance between probes is labeled x. The probes are labeled Scattering units.
+
+(b) Arrangement of the antenna probes
+
+Figure 6.3.1.5.1-1: Experimental setup of the spatial fading emulator
+
+The key features of this method are that it does not use the sophisticated commercial channel emulator.
+
+By using the combination of phase shifters, power dividers and attenuators, operating in the RF band, it has been shown that a realistic fading channel environment can be emulated. To reduce the influence from the measurement equipment, the receiver, phase shifter, power divider, transmitter and computer are set outside of the anechoic chamber.
+
+Firstly, we describe channel response between the  $m^{\text{th}}$  base station, BS, antenna and the  $n^{\text{th}}$  handset antenna for  $M$ -by- $N$  MIMO radio communication system. The channel response is calculated by following equation:
+
+$$(1)$$
+
+where  $E_n$  and  $f_D$  are radiation component of the  $n^{\text{th}}$  handset antenna and the Doppler frequency respectively.  $\phi_0$  is the direction of motion and  $\phi_i$  is the direction of the  $i^{\text{th}}$  antenna probe.  $\alpha_{mi}$  is initial phase of the signal radiated from the  $i^{\text{th}}$  antenna probe. The waves radiated from each base station (BS) antenna are uncorrelated each other.
+
+For the investigation of MIMO antennas, the waves from different BS antenna are represented by different sets of initial phases,  $\alpha_{mi}$ , of the waves. According to the propagation models, such as SCM and SCME, the angular power spectrum
+
+$\Omega$  of the spatial cluster of incoming waves in the horizontal plane can be modelled by a Laplacian distribution in the following, for instance:
+
+$$(2)$$
+
+where  $P$  and  $\mu_\phi$  are power and average direction of angle of the cluster.  $\sigma$  is a standard deviation of the APS. In this case, the spatial distribution in the vertical plane is modelled by a delta function.
+
+In addition, the strongest point of the spatial fading emulator is to be capable of evaluating radiation characteristics of a handset antenna for the present OTA testing in 3GPP as well as the multipath-fading evaluation since the emulator is operated in a Radio Frequency (RF) band.
+
+A calibration of the RF-controlled spatial fading emulator is carried out using the following procedure:
+
+- 1) Firstly a half-wavelength dipole for the receiving antenna is vertically placed at the center of a circle arranging the antenna probes.
+- 2) A radio wave with vertical polarization is radiated only from a vertical dipole of the antenna probe #i (i=1, 2, ..., L), and then, the dipole at the center of the emulator can receive the wave. From this, we can obtain amplitude and phase of the RF signal from the transmitter to the receiver via the vertical dipole of the antenna probe #i.
+- 3) The attenuator and phase shifter are adjusted so that the RF signals received by the dipole at the center have the same values in amplitude and phase.
+- 4) Secondly the slotted cylindrical antenna is placed at the center of the antenna probes located on the circle.
+- 5) A radio wave with horizontal polarization is radiated only from a horizontally-located dipole of the antenna probe #i (i=1, 2, ..., L). From the received signal from the antenna probe #i, we also obtain amplitude and phase of the RF signal from the transmitter to the receiver via the horizontal dipole of the antenna probe #i.
+- 6) The attenuator and phase shifter are adjusted so that the RF signals received by the slotted cylindrical antenna at the center have the same values in amplitude and phase.
+
+The calibration procedure above mentioned can be performed by using an electrical-controlled RF switch.
+
+Thus, the calibration of the emulator can be done automatically using a computer in our system. Once the calibration is finished, we can vary the attenuators in order to produce a special distribution of the incoming wave and to make a Cross polarization Power Ratio (XPR). Moreover, we can set an initial phase to each antenna probe to create a multipath fading channel.
+
+With regard to the signal-to-noise power ratio, SNR, of incoming wave, the signal power can be determined by an average value of faded signal powers received by a half-wavelength dipole antenna for the vertical polarization and a slotted cylindrical antenna for the horizontal polarization. Both antennas have an omni-directional radiation pattern. Thus, SNR can be obtained as the following equation:
+
+$$(3)$$
+
+where  $S_V$  and  $S_H$  are the average signal powers received by the dipole and slotted cylindrical antennas, respectively.  $N_0$  is the noise power that was calculated as a thermal noise within the frequency bandwidth of the radio communication.
+
+##### 6.3.1.5.2 Test conditions
+
+In this method, all signals are operated and controlled at RF level. A computer (either a laptop or relatively powerful computer) is used to provide the followings:
+
+- 1) Graphical User Interface (GUI) to set the input parameters, determine the measured parameters to be collected, setting of calibration parameters and setting of DUT parameters.
+- 2) Generating control signals to manipulate the phase angle of each Phase Shifter.
+
+- 3) Collecting measured raw data obtained via the DUT.
+- 4) Post-processing the measured raw data to derive the desired figure of merits (i.e. minimum requirements for DUT).
+- 5) To initiate the BS emulator and start the testing session (by establishing a communication session with DUT).
+
+The RF signals transmitted from the BS emulator's antenna connector are fed to a bank of Power Dividers.
+
+Each power divider provides identical RF signal from each of the output ports.
+
+The number of Power Dividers required is determined by  $N$ .
+
+Each Power Divider output is then fed to a Phase Shifter. The Phase Shifter is used to change the phase of the RF signal according to the parameter setting input to the computer earlier. Note that the control signal from the computer is digital-to-analogue, D/A, converted, before used to control the Phase Shifter. By controlling the phase of each RF signal, a Rayleigh distributed or other relevant multipath distribution can be obtained.
+
+The number of Phase Shifters required is determined by  $N$ .
+
+The output of the Phase Shifters is connected to the antenna probes. The signal from each Phase Shifter is fed to the vertical and horizontal antennas and radiates toward the DUT. The DUT then measures the signals from each antenna probe and the measurement data is reported back to the computer. The amount of measurement data to be collected can be controlled by the computer by setting the sampling rate,  $R$ .
+
+An example below illustrated the principle of creating Rayleigh faded signal by control the phase of each component wave in Figure 6.3.1.5.2-1.
+
+Number of antenna probes  $N$  : 15
+
+Direction of motion  $\phi_0$  : 10 deg.
+
+Doppler frequency  $f_D$  : 20 Hz
+
+Sampling frequency  $f_S$  : 400 Hz
+
+Radius of circle arranging antenna probes  $r$  : 1.0 m
+
+Operating frequency : 2.14 GHz
+
+Receiving antenna (Rx) : half-wavelength Dipole
+
+Radiation pattern of Rx  $E_n(\phi)$  : omni
+
+APS,  $\Omega(\phi)$  : Uniform
+
+![Figure 6.3.1.5.2-1: A line graph showing Normalized received power [dB] on the y-axis (ranging from -50 to 10) versus fd*t [λ] on the x-axis (ranging from 0 to 25). Two data series are plotted: 'Meas.' (solid blue line) and 'Cal.' (dashed red line). Both lines show rapid fluctuations, with the 'Cal.' line generally exhibiting deeper fades than the 'Meas.' line. The graph illustrates a Rayleigh faded signal.](0892c0cb3b8502a44c4fe4e786be912a_img.jpg)
+
+Figure 6.3.1.5.2-1: A line graph showing Normalized received power [dB] on the y-axis (ranging from -50 to 10) versus fd\*t [λ] on the x-axis (ranging from 0 to 25). Two data series are plotted: 'Meas.' (solid blue line) and 'Cal.' (dashed red line). Both lines show rapid fluctuations, with the 'Cal.' line generally exhibiting deeper fades than the 'Meas.' line. The graph illustrates a Rayleigh faded signal.
+
+Figure 6.3.1.5.2-1: Rayleigh faded signal by control the phase of each component wave
+
+### 6.3.2 Methodologies based on Reverberation Chamber
+
+#### 6.3.2.1 Candidate solution 1
+
+The Reverberation Chamber is a metallic cavity or cavities that can emulate an isotropic multi-path environment which represents a reference environment for systems designed to work during fading, similar to how the free space "anechoic" reference environment is used for tests of Line-Of-Sight systems. The Rayleigh environment in a reverberation chamber is well known as a good reference for urban and indoor environments, but does not well represent rural and suburban environments.
+
+For a future multi-antenna OTA measurement standard it is important to have a fast and repeatable test method to evaluate and compare multi-antenna devices in the environments and under the conditions where most people will use them. The overwhelming majority of calls/data connections with mobile phones are made indoors and in urban areas which can be very well represented by the reverberation chamber. These environments are well characterised by multi-path and 3D distribution of the communication signals and it makes sense to use the reverberation chamber for optimizing/evaluating devices with both single and multiple antenna configurations to be used indoors and in urban areas.
+
+The test setup for testing UE receiver diversity performance is composed of a Base Station (BS) emulator, a reverberation chamber equipped with fixed BS wall-mounted antennas, a switch to direct the base station signal to/from one of the BS wall mounted antennas, mechanical metallic stirrers and a rotating platform to hold the DUT (Figure 6.3.2.1-1).
+
+Alternatively, the chamber may contain one or more cavities coupled through waveguides or slotted plates (Figure 7.1-2).
+
+Reverberation chambers have no quiet zone. As long as the DUT is placed at least 0.5 wavelengths from the wall or metallic stirrers the result will be the same within the standard deviation of the chamber.
+
+Mechanical stirrers and switching among different fixed BS wall-mounted antennas (monopoles used for polarization stirring) allow simulating the Rayleigh fading at each antenna of the terminal inside the chamber. Accuracy can even be increased by rotating the platform holding the device.
+
+Each position of the mechanical stirrers for each position of the platform and each fixed BS antenna, represents a point of the Rayleigh distribution in terms of receive power on the device antennas. In that way a Rayleigh fading is artificially created.
+
+In that way, several UE metrics can be measured: throughput with RX-DIV, TRP, TIS (Total Isotropic Sensitivity), etc.
+
+For each point of the Rayleigh distribution created by the different configurations of the chamber, the metric is noted. This method can be used to measure UE sensitivity and UE radiated power.
+
+![Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity. The diagram shows a single reverberation chamber with a turntable inside. A 'Base station simulator' is connected to a 'Switch', which is connected to the chamber. A person is shown inside the chamber, representing the Device Under Test (DUT).](9a14684f8ae1345c6efea6f5994c730c_img.jpg)
+
+Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity. The diagram shows a single reverberation chamber with a turntable inside. A 'Base station simulator' is connected to a 'Switch', which is connected to the chamber. A person is shown inside the chamber, representing the Device Under Test (DUT).
+
+**Figure 6.3.2.1-1: Reverberation chamber setup for devices testing with Single Cavity**  
+[source: Bluetest AB]
+
+![Figure 6.3.2.1-2: Reverberation Chambers with Multiple Cavities. The diagram shows two reverberation chambers connected by a waveguide. Each chamber has its own 'Base station simulator' and 'Switch 2xT' system. The chambers contain 'stirrers' and a 'slotted plate'. A 'DUT' is shown in the second chamber.](3b00a61116faef21d3a6009fd350b46a_img.jpg)
+
+Figure 6.3.2.1-2: Reverberation Chambers with Multiple Cavities. The diagram shows two reverberation chambers connected by a waveguide. Each chamber has its own 'Base station simulator' and 'Switch 2xT' system. The chambers contain 'stirrers' and a 'slotted plate'. A 'DUT' is shown in the second chamber.
+
+**Figure 6.3.2.1-2: Reverberation Chambers with Multiple Cavities**  
+[source: EMITE Ing]
+
+##### 6.3.2.1.1 Concept and configuration
+
+In order to calibrate the reverberation chamber a broadband antenna can be used to measure the losses in the chamber with a network analyzer. This takes < 10 minutes. CTIA RCSG is working on a standard methodology for reverberation chamber calibration.
+
+There are no active electronics in the measurement path that needs to be calibrated.
+
+Reflections in turntables, cables, doors, etc, do not degrade accuracy. Reflections increase the richness of the channel in the reverberation chamber.
+
+Existing studies show that low standard deviation (good accuracy) can be achieved by measuring the DUT in sufficient number of different positions and calculate the average of the values. Some analysis (see relevant references in [2])
+
+show a typical standard deviation less than 0.5 dB at about 800 MHz, in a reverberation chamber with a size of 1.2m x 1.75m x 1.8m and continuous mode stirring. At higher frequencies or with a chamber of larger dimensions the standard deviation decreases and accuracy increases.
+
+The following figure presents an example for an HSDPA receive diversity test configuration in a reverberation chamber.
+
+For these tests we emulate an HSDPA call with a Node B emulator. The latter is connected to one of the 3 BS wall-mounted antennas through a switch. A fourth antenna allows measuring the DL received signal in the chamber with a spectrum analyzer.
+
+![Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber. The diagram shows a Node B emulator connected to a switch. The switch is connected to three wall-mounted antennas inside a reverberation chamber. A fourth antenna is also inside the chamber, connected to a spectrum analyzer. The chamber contains a rotating platform with a DUT (Device Under Test) and two metallic stirrers.](a5184899f915014fa38608754efcc9c7_img.jpg)
+
+The diagram illustrates the test bench configuration for testing in a reverberation chamber. On the left, a Node B emulator is shown. A cable connects it to a 'Switch' box. From the switch, three cables lead into a 3D representation of a reverberation chamber, connecting to three different wall-mounted antennas. Inside the chamber, there is a rotating platform holding a laptop (the DUT). Two pink, blade-like metallic stirrers are positioned near the walls. A fourth antenna is mounted on the bottom wall of the chamber, with a cable leading out to a spectrum analyzer.
+
+Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber. The diagram shows a Node B emulator connected to a switch. The switch is connected to three wall-mounted antennas inside a reverberation chamber. A fourth antenna is also inside the chamber, connected to a spectrum analyzer. The chamber contains a rotating platform with a DUT (Device Under Test) and two metallic stirrers.
+
+**Figure 6.3.2.1.1-1: Test bench configuration for testing in reverberation chamber**
+
+In order to create a Rayleigh fading environment, we've got 3 types of parameters that can be set using a tool on a computer plugged to the chamber:
+
+- Antenna among the 3, installed at the top of the cavity with different polarizations, is chosen;
+- Turning the platform that holds the DUT;
+- The 2 metallic stirrers near the walls can be moved on their axes.
+
+##### 6.3.2.1.2 Test conditions
+
+Once the chamber is calibrated, the downlink throughput testing can be performed as follows to get one throughput averaged measurement:
+
+- The DUT is placed in the chamber at least 0.5 wavelengths from the wall or from the metallic stirrers.
+- An HSDPA call is emulated using the NodeB emulator with a pre-defined BS TX power.
+- To get one measurement sample we set up one of the following possible combinations: position of the rotating platform  $\{0, \pi/2, \pi, 3\pi/2, \text{etc.}\}$  + position of the metallic stirrers  $\{0, 25, 50, 75, 100, \text{etc.}\}$  + antenna from  $\{1, 2, 3\}$ .
+- For each one of these combinations we can record CQI, DL Throughput and DL Power in the chamber. The latter is measured using a fourth antenna and a spectrum analyzer. This constitutes one measurement
+
+sample. For each measurement sample, the link adaptation is performed manually or automatically on the NodeB emulator as follows: the HS-DSCH is configured (modulation, transport block size, number of HS-DSCH) depending on the CQI (Channel Quality Indicator) reported by the UE (User Equipment) according to the mapping table in 3GPP TS 25.214 [5].
+
+- Once enough different DL throughput measurement samples (ideally  $\geq 100$ ), corresponding to different Antenna, rotating platform's position and stirrers' position combinations, are recorded for the same NodeB emulator DL TX power, they can be averaged to have the averaged DL throughput measurement.
+
+The test duration can be significantly reduced if all these steps are automated. With a Variable Reference Channel (VRC) and continuous mode stirring total measurement time of less than 10 minutes could be possible.
+
+#### 6.3.2.2 Candidate solution 2
+
+The reverberation chamber by itself has a limited range of channel modelling capabilities. Specifically,
+
+- The power/delay profile is limited to a single decaying exponential.
+- The Doppler spectrum and maximum Doppler is limited by the relatively slow motion of the stirrers.
+- It is difficult to impart a specific, repeatable MIMO fading correlation on the downlink waveform.
+
+These limitations can be overcome when a MIMO channel emulator and reverberation chamber are cascaded.
+
+The Power/Delay Profile (PDP) can be enhanced beyond the single decaying exponential by programming the channel emulator with fading taps set at the desired excess delays. The resulting PDP will be the convolution of the taps provided by the channel.
+
+The fading taps provided by the channel emulator allow much higher Doppler spreads than from the reverberation chamber alone. If a classical fading spectrum with a maximum Doppler of 100 Hz is desired, the channel emulator is configured to provide this. The resulting overall Doppler spectrum that results is the convolution of the channel emulator's Doppler spectrum with that of the reverberation chamber.
+
+The fading produced by the cascaded channel emulator and reverberation chamber has a double-Rayleigh amplitude distribution. Because performance simulations generally use Rayleigh fading, simulation results for the double-Rayleigh case are not available.
+
+The benefit is testing with a much higher maximum Doppler, on the order of 100 Hz or higher, than is possible with the reverberation chamber alone. Under these conditions, the reverberation chamber-induced fading will effectively be constant while the channel emulator-induced fading will dominate. Therefore, while a receiver's performance under such circumstances will definitely be different than under normal Rayleigh fading conditions, it should not undermine the receiver's ability to demodulate. Tests have shown that this is indeed the case. However, due to the lack of double-Rayleigh simulation results, measured results should only be compared with other devices using these same test conditions.
+
+The correlation of fading between the downlink MIMO transmission paths can be adjusted using the channel emulator. This is also known as "BS correlation", reflecting the fact that it is controlled on the BS side of the link.
+
+The way to set this correlation using the channel emulator is as follows: using the Kronecker model of fading correlation, set the desired correlation of the transmit or BS correlation matrix. The receiver or MS correlation matrix should be set to identity. An example is given for a 2x2 MIMO system:
+
+$$R_{BS} = \begin{bmatrix} 1 & \rho \\ \rho & 1 \end{bmatrix}, \quad R_{MS} = \begin{bmatrix} 1 & 0 \\ 0 & 1 \end{bmatrix}, \quad R_{chan} = R_{BS} \otimes R_{MS}$$
+
+The value for  $\rho$  is the desired correlation between the two downlink paths. Note that it is not possible to control the phase of the correlation, only the amplitude.
+
+The downlink antennas in the chamber are typically referred to as "wall" antennas. There should be a number of them equal to the number of spatial streams supported by the DUT. The spacing of the wall antennas is not very important. Tests have shown that as the spacing between them is changed over a range between 6 and 80 mm, the measured correlation changes very little, on the order of 5% to 10%.
+
+##### 6.3.2.2.1 Concept and configuration
+
+The general configuration to be used for testing is shown in Figure 6.3.2.2.1-1. The specific example shown there is for two BS antennas. If higher order MIMO devices are to be tested, additional antennas are required. The channel emulator is placed between the (e)NodeB emulator and the reverberation chamber. Two calibrations are performed:
+
+- 1) Calibration of reverberation chamber loading to set the proper chamber impulse response. Most of the time, the chamber will be loaded to produce a specific, desired chamber RMS delay spread. This is achieved using such devices as a phantom head, tank filled with liquid, and RF absorbing foam. For use with the channel emulator, it is desirable to set the chamber RMS delay spread as low as is allowable (approximately 55 ns - see Note), although higher RMS delay spreads are also legitimate, depending on the desired overall PDP.
+
+NOTE: If the delay spread is reduced to below this point, the chamber's ability to produce the desired Rayleigh amplitude distribution at the DUT is degraded.
+
+- 2) Calibration of the losses from (e)NodeB emulator to DUT location. This is already described in the test methodology for the reverberation chamber alone (subclause 6.3.2.1).
+
+The calibrations are performed in this order, using a test antenna as the DUT antenna, and with the DUT in the chamber as it will be during the test. The contents of the chamber should not be disturbed after the calibration is complete. More information about the calibration procedures are found in Annex F.
+
+![Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration. The diagram shows an (e)NodeB Emulator connected to a Channel Emulator. The Channel Emulator is connected to four Wall Antennas inside a reverberation chamber. The Wall Antennas are connected to a Device Under Test (DUT) on a Turntable. A Return Path is shown from the DUT back to the (e)NodeB Emulator. The chamber also contains a Stirrer.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg)
+
+The diagram illustrates the test bench configuration. On the left, an (e)NodeB Emulator is connected to a Channel Emulator. The Channel Emulator has two output ports connected to two Wall Antennas inside a reverberation chamber. Inside the chamber, there are four Wall Antennas in total, a Stirrer, and a Device Under Test (DUT) on a Turntable. A Return Path is shown from the DUT back to the (e)NodeB Emulator. The chamber is a large rectangular box with a door on the left side.
+
+Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration. The diagram shows an (e)NodeB Emulator connected to a Channel Emulator. The Channel Emulator is connected to four Wall Antennas inside a reverberation chamber. The Wall Antennas are connected to a Device Under Test (DUT) on a Turntable. A Return Path is shown from the DUT back to the (e)NodeB Emulator. The chamber also contains a Stirrer.
+
+**Figure 6.3.2.2.1-1: Test bench configuration for test using channel emulator and reverberation chamber for a 2x2 MIMO configuration**
+
+##### 6.3.2.2.2 Test conditions
+
+After the chamber is calibrated, the emulator is configured for the desired channel model, including the end-to-end PDP, the desired fading spectrum and Doppler spread, and the MIMO fading correlation. At this point, the system is ready to test the DUT, and a procedure appropriate to the Figure Of Merit (FOM) being measured is carried out.
+
+There are three (3) operating methods, dependent on the motion of the stirrers and the state of the fading in the channel emulator.
+
+In method 1, the stirrers, turntable or source antennas and channel emulator to operate continuously while the specific FOM is measured. A good example of this use would be throughput measurements under the conditions of a high Doppler rate, or, measured while the signal levels are varied over a wide range.
+
+In method 2, the stirrers and turntable or source antennas are positioned in a number of combinations as described in 6.3.2.1.2. The channel emulator is allowed to run for a fixed length of time (usually 1 or 2 seconds is enough) and paused. The FOM is measured while the stirrers and turntable are not in motion, and the channel emulator is paused. In this method, the number of fixed positions and emulator states must be at least enough to guarantee the proper amplitude distribution. Automation of this entire procedure will significantly reduce the test time.
+
+In method 3, the stirrers and turntable and/or source antennas are positioned as in method 2, but for each position, the channel emulator is allowed to run the fading channel model. The FOM is measured with the stirrers and turntable or source antenna stirring fixed and the channel emulator fading. This method is most analogous to the anechoic method which fixes the device rotation and runs the fading channel emulator while the FOM is measured. This method may also facilitate simulation.
+
+# --- 7 Base Station (BS) configuration
+
+## 7.1 eNodeB emulator settings
+
+The eNodeB emulator parameters shall be set according to Table 7.1-1 for FDD and Table 7.1-2 for TDD. The settings for DL stream 1 and stream 2 are the same.
+
+**Table 7.1-1: Settings for FDD eNodeB emulator**
+
+| eNodeB settings (Note 1)                                                                                                                                                                                                                                    | Unit         | Value                                                                          |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------|
+| <b>Physical channel</b>                                                                                                                                                                                                                                     |              |                                                                                |
+| Connection mode of UE                                                                                                                                                                                                                                       |              | Connection established                                                         |
+| DL MIMO mode                                                                                                                                                                                                                                                |              | 2 x 2 open loop spatial multiplexing                                           |
+| Duplex mode                                                                                                                                                                                                                                                 |              | FDD                                                                            |
+| Operating band<br>(UL channel,<br>DL channel)                                                                                                                                                                                                               |              | Band 7 (21100, 3100)<br>Band 20 (24300, 6300)                                  |
+| Schedule type                                                                                                                                                                                                                                               |              | Reference Measurement Channel (RMC)                                            |
+| Reference Channel                                                                                                                                                                                                                                           |              | R.35 (Note 2)                                                                  |
+| Bandwidth DL                                                                                                                                                                                                                                                | MHz          | 10                                                                             |
+| Number of RBs DL                                                                                                                                                                                                                                            |              | 50                                                                             |
+| Start RB DL                                                                                                                                                                                                                                                 |              | 0                                                                              |
+| Modulation DL                                                                                                                                                                                                                                               |              | 64QAM                                                                          |
+| Maximum Theoretical Throughput                                                                                                                                                                                                                              | Mbps         | 35.424                                                                         |
+| TBS Idx DL                                                                                                                                                                                                                                                  |              | 18 (RMC defined, Note 2)                                                       |
+| Bandwidth UL                                                                                                                                                                                                                                                | MHz          | 10                                                                             |
+| Number of RBs UL                                                                                                                                                                                                                                            |              | 50                                                                             |
+| Start RB UL                                                                                                                                                                                                                                                 |              | 0                                                                              |
+| Modulation UL                                                                                                                                                                                                                                               |              | QPSK                                                                           |
+| TBS Idx UL                                                                                                                                                                                                                                                  |              | 6 (RMC defined)                                                                |
+| Transmit power control                                                                                                                                                                                                                                      | dBm          | -10/10 MHz, open loop (Note 3)                                                 |
+| PDSCH power offset relative to RS EPRE                                                                                                                                                                                                                      | dB           | $\rho_A = -3$<br>$\rho_B = -3$                                                 |
+| Number of HARQ transmissions                                                                                                                                                                                                                                |              | 1 (no HARQ re-transmissions)                                                   |
+| AWGN                                                                                                                                                                                                                                                        |              | OFF                                                                            |
+| DL power level<br>(RS EPRE)                                                                                                                                                                                                                                 | dBm / 15 kHz | Set at eNodeB simulator<br>with correction from calibration                    |
+| Number of subframes for FOM measurement                                                                                                                                                                                                                     |              | 2000 minimum for static channel<br>20000 minimum for faded channel<br>(Note 4) |
+| NOTE 1: This set of parameters is aligned with R&S CMW500, Anritsu MTC8820C, AT4 S3110B, and Agilent E6621A (to be confirmed).                                                                                                                              |              |                                                                                |
+| NOTE 2: This RMC is defined in 3GPP TS 36.521-1 [12], Table A.3.3.2.1-1. R.35 subframes 1-4 and 6-9 utilize DL TBS 18, while R.35 subframe 0 utilizes TBS 17<br>(See Table A.3.3.2.1-1 Fixed Reference Channel two antenna ports in 3GPP TS 36.521-1 [12]). |              |                                                                                |
+| NOTE 3: No uplink power control.                                                                                                                                                                                                                            |              |                                                                                |
+| NOTE 4: These values might need to be increased for frequency and mobile speed reasons.                                                                                                                                                                     |              |                                                                                |
+
+Table 7.1-2: Settings for TDD eNodeB emulator
+
+| eNodeB settings                                                                                                                                                         | Unit         | Value                                                                          |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------|
+| <b>Physical channel</b>                                                                                                                                                 |              |                                                                                |
+| Connection mode of UE                                                                                                                                                   |              | Connection established                                                         |
+| DL MIMO mode                                                                                                                                                            |              | 2 x 2 open loop spatial multiplexing                                           |
+| Duplex mode                                                                                                                                                             |              | TDD                                                                            |
+| Operating band<br>(UL / DL channel)                                                                                                                                     |              | Band 38 (38000)<br>Band 39 (38450)<br>Band 40 (39150)<br>Band 41 (40620)       |
+| Schedule type                                                                                                                                                           |              | Reference Measurement Channel (RMC)                                            |
+| Reference Channel                                                                                                                                                       |              | Table 7.1-3                                                                    |
+| Up/Downlink Frame Configuration                                                                                                                                         |              | 1                                                                              |
+| Special Frame configuration                                                                                                                                             |              | 7                                                                              |
+| Bandwidth DL                                                                                                                                                            | MHz          | 20                                                                             |
+| Number of RBs DL                                                                                                                                                        |              | 100                                                                            |
+| Start RB DL                                                                                                                                                             |              | 0                                                                              |
+| Modulation DL                                                                                                                                                           |              | 64QAM                                                                          |
+| TBS Idx DL                                                                                                                                                              |              | 16 (RMC defined, NOTE 1)                                                       |
+| Bandwidth UL                                                                                                                                                            | MHz          | 20                                                                             |
+| Number of RBs UL                                                                                                                                                        |              | 100                                                                            |
+| Start RB UL                                                                                                                                                             |              | 0                                                                              |
+| Modulation UL                                                                                                                                                           |              | QPSK                                                                           |
+| TBS Idx UL                                                                                                                                                              |              | 6                                                                              |
+| Transmit power control                                                                                                                                                  | dBm          | -10/20 MHz, open loop (NOTE 2)                                                 |
+| PDSCH power offset relative to RS EPRE                                                                                                                                  | dB           | $\rho_A = -3$<br>$\rho_B = -3$                                                 |
+| Number of HARQ transmissions                                                                                                                                            |              | 1 (no HARQ re-transmissions)                                                   |
+| AWGN                                                                                                                                                                    |              | OFF                                                                            |
+| DL power level<br>(RS EPRE)                                                                                                                                             | dBm / 15 kHz | Set at eNodeB simulator<br>with correction from calibration                    |
+| Number of subframes for FOM measurement                                                                                                                                 |              | 2000 minimum for static channel<br>20000 minimum for faded channel<br>(NOTE 3) |
+| NOTE 1: This RMC is defined in Table 7.1-3. Subframes 0, 1, 4, 6 and 9 utilize DL TBS 16, subframe 5 is unused for DL data transmission and other subframes are for UL. |              |                                                                                |
+| NOTE 2: No uplink power control.                                                                                                                                        |              |                                                                                |
+| NOTE 3: These values might need to be increased for frequency and mobile speed reasons.                                                                                 |              |                                                                                |
+
+**Table 7.1-3: Fixed Reference Channel two antenna ports for 20MHz TD-LTE**
+
+| Parameter                                                                                                                                       | Unit | Value    |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|------|----------|
+| Channel bandwidth                                                                                                                               | MHz  | 20       |
+| Allocated resource blocks (Note 3)                                                                                                              |      | 100      |
+| Uplink-Downlink Configuration (Note 1)                                                                                                          |      | 1        |
+| Allocated subframes per Radio Frame (D+S)                                                                                                       |      | 4+2      |
+| Modulation                                                                                                                                      |      | 64QAM    |
+| Target Coding Rate                                                                                                                              |      | 0.4      |
+| Information Bit Payload (Note 3)                                                                                                                |      |          |
+| For Sub-Frames 4,9                                                                                                                              | Bits | 32856    |
+| For Sub-Frames 1,6                                                                                                                              |      | 24496    |
+| For Sub-Frame 5                                                                                                                                 | Bits | N/A      |
+| For Sub-Frame 0                                                                                                                                 | Bits | 32856    |
+| Number of Code Blocks (Notes 2 and 3)                                                                                                           |      |          |
+| For Sub-Frames 4,9                                                                                                                              |      | 5        |
+| For Sub-Frames 1,6                                                                                                                              |      | 4        |
+| For Sub-Frame 5                                                                                                                                 |      | N/A      |
+| For Sub-Frame 0                                                                                                                                 |      | 5        |
+| Binary Channel Bits (Note 3)                                                                                                                    |      |          |
+| For Sub-Frames 4,9                                                                                                                              | Bits | 82800    |
+| For Sub-Frames 1,6                                                                                                                              |      | 67968    |
+| For Sub-Frame 5                                                                                                                                 | Bits | N/A      |
+| For Sub-Frame 0                                                                                                                                 | Bits | 80712    |
+| Max. Throughput averaged over 1 frame (Note 3)                                                                                                  | Mbps | 14.756   |
+| UE Category                                                                                                                                     |      | $\geq 1$ |
+| NOTE 1: As per Table 4.2-2 in TS 36.211 [4].                                                                                                    |      |          |
+| NOTE 2: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code Block (otherwise L = 0 Bit). |      |          |
+| NOTE 3: Given per component carrier per codeword                                                                                                |      |          |
+
+# 8 Channel Models
+
+## 8.1 Introduction
+
+In order to understand how different methodologies are able to similarly distinguish good and bad MIMO devices, it is important to ensure that the radio propagation conditions that are implying to a particular DUT are the same or similar to a certain extent.
+
+The different channel models are used as a simple way to create complex multipath radio propagation conditions and RAN4 has agreed to compare the realization of those channel models across the different methods.
+
+## 8.2 Channel Model(s) to be validated
+
+Editor's Note: Initially a small set of representative channel models shall be agreed and use to validate channel model realization. Other channel models could be used at a later stage.
+
+This clause shall also contain the identification of the main properties that characterize a given channel model as well as the expected results when realizing a channel model regardless of the methodology.
+
+The following channel models are to be used in evaluation of MIMO OTA methodologies.
+
+The generic models are
+
+- SCME Urban micro-cell, and
+- SCME Urban macro-cell.
+
+In addition, the BS antenna assumptions defined in subclause 8.5 also apply when emulating the channel models.
+
+In the following we define the cross polarization power ratio a propagation channel as  $XPR = E[|S_{VV}|^2] / E[|S_{VH}|^2]$ , where  $S_{VV}$  and  $S_{VH}$  are defined below, and  $XPR = E[|S_{HH}|^2] / E[|S_{HV}|^2]$  where  $S_{HH}$  and  $S_{HV}$  are defined below.
+
+and
+
+and
+
+- $S_{VV}$  is the coefficient for scattered/reflected power on V-polarization and incident power on V-polarization;
+- $S_{VH}$  is the coefficient for scattered/reflected power on V-polarization and incident power on H-polarization;
+- $S_{HV}$  is the coefficient for scattered/reflected power on H-polarization and incident power on V-polarization;
+- $S_{HH}$  is the coefficient for scattered/reflected power on H-polarization and incident power on H-polarization.
+
+NOTE: For Vertical only measurements, the powers per delay are used without regard to the specified XPR values.
+
+The following SCME Urban Micro-cell is unchanged from the original SCME paper, with added XPR values, Direction of Travel, and Velocity.
+
+**Table 8.2-1: SCME urban micro-cell channel model**
+
+| SCME Urban micro-cell                                        |            |     |     |            |       |       |         |                   |
+|--------------------------------------------------------------|------------|-----|-----|------------|-------|-------|---------|-------------------|
+| Cluster #                                                    | Delay [ns] |     |     | Power [dB] |       |       | AoD [°] | AoA [°]           |
+|                                                              | 1          | 0   | 5   | 10         | -3.0  | -5.2  |         |                   |
+| 2                                                            | 285        | 290 | 295 | -4.3       | -6.5  | -8.3  | 14.1    | -13.2             |
+| 3                                                            | 205        | 210 | 215 | -5.7       | -7.9  | -9.7  | 50.8    | 146.1             |
+| 4                                                            | 660        | 665 | 670 | -7.3       | -9.5  | -11.3 | 38.4    | -30.5             |
+| 5                                                            | 805        | 810 | 815 | -9.0       | -11.2 | -13.0 | 6.7     | -11.4             |
+| 6                                                            | 925        | 930 | 935 | -11.4      | -13.6 | -15.4 | 40.3    | -1.1              |
+| Delay spread [ns]                                            |            |     |     |            |       |       |         | 294               |
+| Cluster AS AoD / AS AoA [°]                                  |            |     |     |            |       |       |         | 5 / 35            |
+| Cluster PAS shape                                            |            |     |     |            |       |       |         | Laplacian         |
+| Total AS AoD / AS AoA [°]                                    |            |     |     |            |       |       |         | 18.2 / 67.8       |
+| Mobile speed [km/h] / Direction of travel [°]                |            |     |     |            |       |       |         | 3, 30 / 120       |
+| XPR<br>(NOTE: V & H components based on assumed BS antennas) |            |     |     |            |       |       |         | 9 dB              |
+| Mid-paths Share Cluster parameter values for:                |            |     |     |            |       |       |         | AoD, AoA, AS, XPR |
+
+The following SCME Urban Macro-cell is unchanged from the original SCME paper, with added XPR values, Direction of Travel, and Velocity.
+
+**Table 8.2-2: SCME urban macro-cell channel model**
+
+| SCME Urban macro-cell                                        |            |      |      |            |       |       |         |                   |
+|--------------------------------------------------------------|------------|------|------|------------|-------|-------|---------|-------------------|
+| Cluster #                                                    | Delay [ns] |      |      | Power [dB] |       |       | AoD [°] | AoA [°]           |
+|                                                              | 0          | 5    | 10   | -3         | -5.2  | -7    |         |                   |
+| 1                                                            | 0          | 5    | 10   | -3         | -5.2  | -7    | 82.0    | 65.7              |
+| 2                                                            | 360        | 365  | 370  | -5.2       | -7.4  | -9.2  | 80.5    | 45.6              |
+| 3                                                            | 255        | 260  | 265  | -4.7       | -6.9  | -8.7  | 79.6    | 143.2             |
+| 4                                                            | 1040       | 1045 | 1050 | -8.2       | -10.4 | -12.2 | 98.6    | 32.5              |
+| 5                                                            | 2730       | 2735 | 2740 | -12.1      | -14.3 | -16.1 | 102.1   | -91.1             |
+| 6                                                            | 4600       | 4605 | 4610 | -15.5      | -17.7 | -19.5 | 107.1   | -19.2             |
+| Delay spread [ns]                                            |            |      |      |            |       |       |         | 839.5             |
+| Cluster AS AoD / AS AoA [°]                                  |            |      |      |            |       |       |         | 2 / 35            |
+| Cluster PAS shape                                            |            |      |      |            |       |       |         | Laplacian         |
+| Total AS AoD / AS AoA [°]                                    |            |      |      |            |       |       |         | 7.9 / 62.4        |
+| Mobile speed [km/h] / Direction of travel [°]                |            |      |      |            |       |       |         | 3, 30 / 120       |
+| XPR<br>(NOTE: V & H components based on assumed BS antennas) |            |      |      |            |       |       |         | 9 dB              |
+| Mid-paths Share Cluster parameter values for:                |            |      |      |            |       |       |         | AoD, AoA, AS, XPR |
+
+The parameters of the channel models are the expected parameters for the MIMO OTA channel models. However, the final channel model achieved for different methods could be a combined effect of the chamber and the channel emulator.
+
+The Rayleigh fading may be implementation specific. However, the fading can be considered to be appropriate as long as the statistics of the generated Rayleigh fading are within standard requirement on Rayleigh fading statistics.
+
+Editor's Note: NIST channel model is not ruled out, but before it can be used, more information on the AoA values would need to be provided.
+
+## 8.3 Verification of Channel Model implementations
+
+Channel Models have been specified in Clause 8.2.
+
+This clause describes the MIMO OTA validation measurements, in order to ensure that the channel models are correctly implemented and hence capable of generating the propagation environment, as described by the model, within a test area. Measurements are done mainly with a Vector Network Analyser (VNA) and a spectrum analyzer.
+
+Note that the term "**OTA antenna configuration**" used in this subclause refers only to the physical antennas used to perform the validation. The BS antenna assumptions defined as part of the channel model in subclause 8.5 apply in addition to the physical antenna configuration.
+
+### 8.3.1 Measurement instruments and setup
+
+The measurement setup includes the following equipment:
+
+**Table 8.3.1-1: Measurement equipment list for the verification procedure**
+
+| Item | Quantity | Item              |
+|------|----------|-------------------|
+| 1    | 1        | Channel Emulator  |
+| 2    | 1        | Signal Generator  |
+| 3    | 1        | Spectrum Analyzer |
+| 4    | 1        | VNA               |
+| 5    | 1        | Magnetic Dipole   |
+| 6    | 1        | Sleeve Dipole     |
+
+#### 8.3.1.1 Vector Network Analyzer (VNA) setup
+
+Most of the measurements are performed with a VNA. An example set of equipment required for this set-up is shown in Figure 8.3.1.1-1. VNA transmits frequency sweep signals through the MIMO OTA test system.
+
+A test antenna, within the test area, receives the signal and VNA analyzes the frequency response of the system.
+
+A number of traces (frequency responses) are measured and recorded by VNA and analyzed by a post processing SW, e.g., Matlab. Special care has to be taken into account to keep the fading conditions unchanged, i.e. frozen, during the short period of time of a single trace measurement. The fading may proceed only in between traces. This setup can be used to measure PDP, Spatial Correlation and Polarization of the Channel models defined in clause 8.2.
+
+![Figure 8.3.1.1-1: Setup for VNA measurements. A block diagram showing a VNA box connected via a red line to a Fading emulator box. The Fading emulator has multiple black output lines entering a 3D perspective drawing of a Chamber. Inside the chamber, these lines connect to three small antenna symbols. A separate 'Test antenna' symbol inside the chamber is connected via a red line back to the VNA box. The chamber is labeled 'Chamber'.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg)
+
+The diagram shows the hardware configuration for VNA-based measurements. A Vector Network Analyzer (VNA) provides the signal to a Fading emulator. The output of the emulator is fed into a shielded Chamber containing multiple antennas. A specific Test antenna within the chamber captures the signal and routes it back to the VNA for analysis.
+
+Figure 8.3.1.1-1: Setup for VNA measurements. A block diagram showing a VNA box connected via a red line to a Fading emulator box. The Fading emulator has multiple black output lines entering a 3D perspective drawing of a Chamber. Inside the chamber, these lines connect to three small antenna symbols. A separate 'Test antenna' symbol inside the chamber is connected via a red line back to the VNA box. The chamber is labeled 'Chamber'.
+
+**Figure 8.3.1.1-1: Setup for VNA measurements**
+
+#### 8.3.1.2 Spectrum Analyzer (SA) setup
+
+The Doppler spectrum is measured with a spectrum analyzer as shown in Figure 8.3.1.2-1. In this case a signal generator transmits CW signal through the MIMO OTA test system. The signal is received by a test antenna within the test area. Finally the signal is analyzed by a spectrum analyzer and the measured spectrum is compared to the target spectrum. This setup can be used to measure Doppler Spectrum of the Channel models defined in Clause 8.2.
+
+![Figure 8.3.1.2-1: Setup for VNA measurements. A block diagram showing a Signal Generator box and a Spectrum Analyzer box. The Signal Generator is connected via a red line to a Fading emulator box. The Fading emulator has multiple black output lines entering a 3D perspective drawing of a Chamber. Inside the chamber, these lines connect to three small antenna symbols. A separate 'Test antenna' symbol inside the chamber is connected via a red line back to the Spectrum Analyzer box. The chamber is labeled 'Chamber'.](f5d2a88925807080157c7cfb1d41cf0b_img.jpg)
+
+The diagram illustrates the setup for Spectrum Analyzer measurements. A Signal Generator sends a CW signal to the Fading emulator. The emulated signals are transmitted via antennas inside a Chamber. A Test antenna receives the signal, which is then sent to a Spectrum Analyzer for frequency domain analysis.
+
+Figure 8.3.1.2-1: Setup for VNA measurements. A block diagram showing a Signal Generator box and a Spectrum Analyzer box. The Signal Generator is connected via a red line to a Fading emulator box. The Fading emulator has multiple black output lines entering a 3D perspective drawing of a Chamber. Inside the chamber, these lines connect to three small antenna symbols. A separate 'Test antenna' symbol inside the chamber is connected via a red line back to the Spectrum Analyzer box. The chamber is labeled 'Chamber'.
+
+**Figure 8.3.1.2-1: Setup for VNA measurements**
+
+The RTS channel model validation setup consists of a vector signal generator and a spectrum analyser with signal analysis capabilities or scope as depicted in Figure 8.3.1.2-2 and the provided validation procedures apply for both, correlation-based and geometry-based channel model implementations. For RTS implementations that use a standalone channel emulator, the channel validation procedures in this clause may not apply; instead, the MPAC validation procedures may be carried out.
+
+![Figure 8.3.1.2-2: Setup for RTS channel model validation. The diagram shows a 3D perspective view of a rectangular 'Chamber'. Inside the chamber, there is a 'TX Antenna' on the left and an 'RX Antenna' on the right. A red line connects the TX Antenna to a 'Fading Emulator' box outside the chamber. The 'Fading Emulator' is connected to a 'Signal Generator' and a 'Spectrum Analyzer/Scope'. A red line also connects the 'RX Antenna' inside the chamber to the 'Spectrum Analyzer/Scope'.](0a73b03fba21af142d619a9a662e6490_img.jpg)
+
+Figure 8.3.1.2-2: Setup for RTS channel model validation. The diagram shows a 3D perspective view of a rectangular 'Chamber'. Inside the chamber, there is a 'TX Antenna' on the left and an 'RX Antenna' on the right. A red line connects the TX Antenna to a 'Fading Emulator' box outside the chamber. The 'Fading Emulator' is connected to a 'Signal Generator' and a 'Spectrum Analyzer/Scope'. A red line also connects the 'RX Antenna' inside the chamber to the 'Spectrum Analyzer/Scope'.
+
+Figure 8.3.1.2-2: Setup for RTS channel model validation
+
+### 8.3.2 Validation measurements
+
+#### 8.3.2.1 Power Delay Profile (PDP)
+
+This measurement checks that the resulting Power Delay Profile (PDP) is like defined in the channel model.
+
+##### Method of measurement:
+
+Step the emulation and store traces from VNA. I.e. run the emulation to CIR number 1, pause, measure VNA trace, run the emulation to CIR number 10, pause, measure VNA trace. Continue until 1000 VNA traces are measured.
+
+##### VNA settings:
+
+Table 8.3.2.1-1: VNA settings for PDP
+
+| Item                                                                                                                                                           | Unit              | Value                                                                 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------|
+| Center frequency                                                                                                                                               | MHz               | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Span                                                                                                                                                           | MHz               | 200 [TDB]                                                             |
+| RF output level                                                                                                                                                | dBm               | -15                                                                   |
+| Number of traces                                                                                                                                               |                   | 1000                                                                  |
+| Distance between traces in channel model                                                                                                                       | wavelength (Note) | > 2                                                                   |
+| Number of points                                                                                                                                               |                   | 1101                                                                  |
+| Averaging                                                                                                                                                      |                   | 1                                                                     |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]<br>MS speed [ $\lambda$ /s] = MS speed [m/s] / Speed of light [m/s] * Center frequency [Hz] |                   |                                                                       |
+
+##### Channel model specification:
+
+Table 8.3.2.1-2: Channel model specification for PDP
+
+| Item                  | Unit       | Value                                                                 |
+|-----------------------|------------|-----------------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Channel model samples | wavelength | > 2000                                                                |
+| Channel model         |            | As specified in Clause 8.2                                            |
+
+##### Method of measurement result analysis:
+
+Measured VNA traces (frequency responses  $H(t,f)$ ) are saved into a hard drive. The data is read into, e.g., Matlab. The analysis is performed by taking the Fourier transform of each FR. The resulting impulse responses  $h(t,\tau)$  are averaged in power over time:
+
+Finally the resulting PDP is shifted in delay, such that the first tap is on delay zero. The reference PDP plots from Table 8.2-1 and Table 8.2-2 are shown in Figure 8.3.2.1-1.
+
+**OTA antenna configuration:** For e.g. 1 full ring (or single cluster configuration) of V polarized elements.
+
+**Measurement antenna:** For e.g. Vertically oriented sleeve dipole.
+
+![Figure 8.3.2.1-1: Reference PDP values for SCME Urban Macro / SCME Urban Micro plotted from Table 8.2-1 and Table 8.2-2. The figure contains two plots. The left plot, titled 'PDP, SCME Urban micro, Table 6.2-1', shows magnitude [dB] on the y-axis (from -16 to 0) versus delay [ns] on the x-axis (from 0 to 1000). It features several sharp red spikes representing discrete taps. The right plot, titled 'PDP, SCME Urban macro, Table 6.2-3', shows magnitude [dB] on the y-axis (from -20 to 0) versus delay [ns] on the x-axis (from 0 to 5000). This plot also shows sharp red spikes, but with more taps and varying magnitudes.](e2028979caae230f36254a6bec04bcd9_img.jpg)
+
+Figure 8.3.2.1-1: Reference PDP values for SCME Urban Macro / SCME Urban Micro plotted from Table 8.2-1 and Table 8.2-2. The figure contains two plots. The left plot, titled 'PDP, SCME Urban micro, Table 6.2-1', shows magnitude [dB] on the y-axis (from -16 to 0) versus delay [ns] on the x-axis (from 0 to 1000). It features several sharp red spikes representing discrete taps. The right plot, titled 'PDP, SCME Urban macro, Table 6.2-3', shows magnitude [dB] on the y-axis (from -20 to 0) versus delay [ns] on the x-axis (from 0 to 5000). This plot also shows sharp red spikes, but with more taps and varying magnitudes.
+
+**Figure 8.3.2.1-1: Reference PDP values for SCME Urban Macro / SCME Urban Micro plotted from Table 8.2-1 and Table 8.2-2**
+
+##### Method of measurement for RTS:
+
+The vector signal generator repeatedly generates the Zadoff-Chu sequence as defined in Table 8.3.2.1-3. After a given time interval, the spectrum analyser or scope is triggered by the vector signal generator at the beginning of the next Zadoff-Chu sequence. The time interval needs to exceed the required minimum distance between two PDPs as defined in Table 8.3.2.1-4 and depends on the centre frequency and the mobile speed.
+
+After receiving the trigger signal, the spectrum analyser or scope starts with the acquisition of the IQ data. The number of recorded IQ samples corresponds to the length of the used Zadoff-Chu sequence. This step is repeated until at least 1000 blocks of IQ samples are recorded.
+
+##### Vector signal generator settings:
+
+**Table 8.3.2.1-3: PDP measurement parameters for signal generator**
+
+| Item                  | Unit    | Value                                                                 |
+|-----------------------|---------|-----------------------------------------------------------------------|
+| Centre frequency      | MHz     | Downlink centre frequency in 3GPP TS 36.508 [19] as required per band |
+| Min. signal bandwidth | MHz     | 100                                                                   |
+| RF output level       | dBm     | -15                                                                   |
+| Sequence type         |         | Zadoff-Chu or similar waveform with good autocorrelation properties   |
+| Min. sequence length  | Samples | 1023                                                                  |
+
+##### Signal and spectrum analyser settings:
+
+**Table 8.3.2.1-4: PDP measurement parameters for spectrum analyser**
+
+| Item                                                                                                                                                           | Unit              | Value                                                                 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------|
+| Centre frequency                                                                                                                                               | MHz               | Downlink centre frequency in 3GPP TS 36.508 [19] as required per band |
+| Min. sampling rate                                                                                                                                             | MHz               | 100                                                                   |
+| Min. number of PDPs for averaging                                                                                                                              |                   | 1000                                                                  |
+| Distance between PDPs in channel model                                                                                                                         | Wavelength (Note) | > 2                                                                   |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]<br>MS speed [ $\lambda$ /s] = MS speed [m/s] / Speed of light [m/s] * Centre frequency [Hz] |                   |                                                                       |
+
+The channel model specifications match those from Table 8.3.2.1-2.
+
+##### Method of measurement result analysis:
+
+The measured blocks of IQ samples are saved and later analysed by a post processing SW, e.g., Matlab. The analysis is performed by applying the circular cross-correlation between each recorded block of IQ samples and the IQ samples of the original Zadoff-Chu sequence. The resulting impulse responses  $h(t,\tau)$  are averaged in power over time:
+
+Finally the resulting PDP is shifted in delay and normalized in power, such that the first tap is on delay zero and has a relative power of 0 dB.
+
+**Antenna configurations:** For e.g. a pair of vertically oriented sleeve dipoles or vertically polarized horn antennas.
+
+#### 8.3.2.2 Doppler/Temporal correlation
+
+This measurement checks the Doppler/temporal correlation.
+
+##### Method of measurement:
+
+Sine wave (CW, carrier wave) signal is transmitted from the signal generator. The signal is connected from the signal generator to fading emulator via cables. The fading emulator output signals are connected to power amplifier boxes via cables. The amplified signals are then transferred via cables to the probe antennas. The probe antennas radiate the signals over the air to the test antenna. The Doppler spectrum is measured by the spectrum analyzer and the trace is saved.
+
+##### Signal generator settings:
+
+**Table 8.3.2.2-1: Signal generator settings for Doppler/Temporal correlation**
+
+| Item             | Unit | Value                                                                 |
+|------------------|------|-----------------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Output level     | dBm  | -15                                                                   |
+| Modulation       |      | OFF                                                                   |
+
+##### Spectrum analyzer settings:
+
+**Table 8.3.2.2-2: Spectrum analyzer settings for Doppler/Temporal correlation**
+
+| Item             | Unit | Value                                                                 |
+|------------------|------|-----------------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Minimum Span     | Hz   | max(4 x MaxDoppler, 400 Hz)                                           |
+| RBW              | Hz   | 1                                                                     |
+| VBW              | Hz   | 1 or use FFT                                                          |
+| Number of points |      | 8001                                                                  |
+| Averaging        |      | 100                                                                   |
+
+**Channel model specification:**
+
+**Table 8.3.2.2-3: Channel model specification for Doppler/Temporal correlation**
+
+| Item             | Unit | Value                                                                 |
+|------------------|------|-----------------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Channel model    |      | As specified in Clause 8.2                                            |
+| Mobile speed     | km/h | 100                                                                   |
+
+Method of measurement result analysis: Measurement data file (Doppler power spectrum) is saved into hard drive.
+
+The data is read into, e.g., Matlab.
+
+The analysis is performed by taking the Fourier transformation of the Doppler spectrum.
+
+The resulting temporal correlation function is normalized such that .
+
+Then the function values left from the maximum is cut out.
+
+Further on the function values after, e.g. seven periods is cut out.
+
+The reference temporal correlation plots from Table 8.2-1 and 8.2-2 are shown in Figure 8.3.2.2-1 and Figure 8.3.2.2-2.
+
+**OTA antenna configuration:** For e.g. 1 full ring (or single cluster configuration) of V polarized elements.
+
+**Measurement antenna:** For e.g. vertically oriented dipole.
+
+![Figure 8.3.2.2-1: Reference Temporal Correlation Functions for SCME Urban Macro (left) and SCME Urban Micro (right).](3881b390d52f27a35faedfc170916c86_img.jpg)
+
+Figure 8.3.2.2-1 consists of two line graphs. The left graph is titled 'Temporal Correlation SCMe UMa channel model' and the right graph is titled 'Temporal correlation SCMe UMi channel model'. Both graphs plot the correlation coefficient  $\rho$  on the y-axis (ranging from 0 to 1) against Distance [ $\lambda$ ] on the x-axis (ranging from 0 to 5). Both curves start at a correlation of 1.0 at 0 distance and exhibit a damped oscillatory decay as distance increases. The UMa curve (left) decays more rapidly than the UMi curve (right), reaching near-zero correlation by distance 5.
+
+Figure 8.3.2.2-1: Reference Temporal Correlation Functions for SCME Urban Macro (left) and SCME Urban Micro (right).
+
+**Figure 8.3.2.2-1: Reference Temporal Correlation Functions for SCME Urban Macro (left) and SCME Urban Micro (right) plotted from Table 8.2-1 and Table 8.2-2**
+
+![Figure 8.3.2.2-2: Reference Temporal Correlation Function for correlation implementation of SCME UMa and UMi with Jake's Doppler spectrum.](2c5884241ad393e03dd8e4ea25ff74a2_img.jpg)
+
+Figure 8.3.2.2-2 is a line graph titled 'Theoretical temporal correlation for correlation based SCME UMi and UMa with modified Jakes Doppler spectrum'. It plots 'Correlation [Unitless]' on the y-axis (ranging from 0 to 1) against 'Wavelength [ $\lambda$ ]' on the x-axis (ranging from 0 to 5). The curve starts at 1.0 at 0 wavelength and shows a damped oscillatory decay, similar to the temporal correlation functions in Figure 8.3.2.2-1, but with a different oscillation frequency and decay rate.
+
+Figure 8.3.2.2-2: Reference Temporal Correlation Function for correlation implementation of SCME UMa and UMi with Jake's Doppler spectrum.
+
+**Figure 8.3.2.2-2: Reference Temporal Correlation Function for correlation implementation of SCME UMa and UMi with Jake's Doppler spectrum plotted from Table 8.2-1 and Table 8.2-2**
+
+#### 8.3.2.3 Spatial correlation
+
+This measurement checks whether the measured correlation curve follows the theoretical curve.
+
+##### Method of measurement:
+
+Stop the emulation and store traces from VNA. I.e. run the emulation to CIR number 1, pause, measure VNA traces in 11 different DUT positions, run the emulation to CIR number 10, pause, measure VNA traces in 11 different DUT positions, ... etc. Continue until frequency response of 1000 CIRs in 11 positions ( $=1000 \times 11$  VNA traces) are measured.
+
+11 test antenna positions sample a segment of line of length 1 wavelength with sampling interval of 0.1 wavelengths. Antenna spacing (wave lengths): -0.5 to +0.5 step of 0.1.
+
+![Figure 8.3.2.3-1: Test antenna positions. A scatter plot showing 11 test antenna positions along the Y-axis at X=0. The Y-axis ranges from -0.5 to 0.5 λ, and the X-axis ranges from -1 to 1 λ. An arrow points to the right along the X-axis, labeled 'AoA = 0° direction'.](730b6615db6d402580db1024a7f4e163_img.jpg)
+
+Figure 8.3.2.3-1: Test antenna positions. A scatter plot showing 11 test antenna positions along the Y-axis at X=0. The Y-axis ranges from -0.5 to 0.5 λ, and the X-axis ranges from -1 to 1 λ. An arrow points to the right along the X-axis, labeled 'AoA = 0° direction'.
+
+Figure 8.3.2.3-1: Test antenna positions
+
+VNA settings:
+
+Table 8.3.2.3-1: VNA settings for spatial correlation
+
+| Item                                     | Unit              | Value                                                                 |
+|------------------------------------------|-------------------|-----------------------------------------------------------------------|
+| Center frequency                         | MHz               | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Span                                     | MHz               | 10                                                                    |
+| RF output level                          | dBm               | -15                                                                   |
+| Number of traces                         |                   | 1000                                                                  |
+| Distance between traces in channel model | Wavelength (Note) | > 2                                                                   |
+| Number of points                         |                   | 1 (or the smallest possible)                                          |
+| Averaging                                |                   | 1                                                                     |
+
+NOTE: Time in seconds = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]  
+MS speed [ $\lambda$ /s] = MS speed [m/s] / Speed of light [m/s] \* Center frequency [Hz]
+
+Channel model specification:
+
+Table 8.3.2.3-2: Channel model specification for spatial correlation
+
+| Item                  | Unit       | Value                                                                 |
+|-----------------------|------------|-----------------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Channel model samples | Wavelength | > 2000                                                                |
+| Channel model         |            | As specified in Clause 8.2                                            |
+| Mobile speed          | km/h       | 30                                                                    |
+
+Measurement Procedure
+
+CALIBRATE
+
+OPEN corrVNATrace trace file
+
+FOR EACH gridPoint IN [test zone grid set]
+
+MOVE measurement antenna to gridPoint
+
+FOR EACH chanIRNumber IN [0:SD:1000\*SD]
+
+MEASURE Freq Resp with VNA
+
+SAVE freq resp trace to trace file
+
+END
+
+END
+
+CLOSE corrVNATrace\_<calibMethod>\_<polarization> trace file
+
+##### Method of Measurement Results Analysis
+
+Calculate correlation of 1000 x 11 matrix  $\mathbf{H}(f)$  of frequency response samples. The procedure is to correlate sixth column (the trace measured at the centre of chamber) with the 10 other columns as follows (Matlab example)
+
+```
+for ind = 1:11;
+    Corr(:, :, ind) = abs(corrcoef(H(:, 1), H(:, ind)));
+end
+Correlation = squeeze(Corr(1, 2, :));
+```
+
+The reference spatial correlation plots from Table 8.2-1 and 8.2-2 are shown in Figure 8.3.2.3-2.
+
+**OTA antenna configuration:** For e.g. 1 full ring (or a single cluster configuration) of V polarized elements.
+
+**Measurement antenna:** For e.g. Sleeve dipole.
+
+![Figure 8.3.2.3-2: Reference Spatial Correlation Functions for SCME Urban Macro / SCME Urban Micro. The figure contains two line graphs. The left graph, titled 'Spatial Correlation for SCME Urban Micro', shows the correlation coefficient (rho) on the y-axis (ranging from 0 to 1) against spatial separation in lambda on the x-axis (ranging from 0 to 1). The curve starts at 1.0 at 0 lambda, drops sharply to about 0.1 at 0.5 lambda, and then oscillates slightly around 0.1. The right graph, titled 'Spatial Correlation for SCME Urban Macro', shows the same axes. The curve starts at 1.0 at 0 lambda, drops more gradually to about 0.5 at 0.5 lambda, and then continues to decrease to about 0.35 at 1.0 lambda.](3e79b23ceef44b802985f19098824e62_img.jpg)
+
+Figure 8.3.2.3-2: Reference Spatial Correlation Functions for SCME Urban Macro / SCME Urban Micro. The figure contains two line graphs. The left graph, titled 'Spatial Correlation for SCME Urban Micro', shows the correlation coefficient (rho) on the y-axis (ranging from 0 to 1) against spatial separation in lambda on the x-axis (ranging from 0 to 1). The curve starts at 1.0 at 0 lambda, drops sharply to about 0.1 at 0.5 lambda, and then oscillates slightly around 0.1. The right graph, titled 'Spatial Correlation for SCME Urban Macro', shows the same axes. The curve starts at 1.0 at 0 lambda, drops more gradually to about 0.5 at 0.5 lambda, and then continues to decrease to about 0.35 at 1.0 lambda.
+
+**Figure 8.3.2.3-2: Reference Spatial Correlation Functions for SCME Urban Macro / SCME Urban Micro plotted from Table 8.2-1 and Table 8.2-2**
+
+For RTS, spatial correlation is verified using the setup in Figure 8.3.1.2-2. The channel emulator is configured for a MIMO channel model with two transmit and two receive antenna patterns. The transmit antennas are assumed to be dual-polarized equal power elements with a fixed  $0\lambda$  separation, 45 degrees slanted, Clause 8.5, while the two receiver antennas are configured as vertically polarized dipoles with varying antenna separation. The antenna positions sample a
+
+line of length  $1\lambda$  with a sampling interval of  $0.1\lambda$ . Both antennas and the respective patterns are simulated in the channel emulator.
+
+##### **Vector signal generator settings:**
+
+**Table 8.3.2.3-3: Signal generator settings for spatial correlation for RTS**
+
+| Item                  | Unit    | Value                                                                 |
+|-----------------------|---------|-----------------------------------------------------------------------|
+| Centre frequency      | MHz     | Downlink centre frequency in 3GPP TS 36.508 [19] as required per band |
+| Min. signal bandwidth | kHz     | 10                                                                    |
+| RF output level       | dBm     | -15                                                                   |
+| Sequence type         |         | Zadoff-Chu or similar waveform with good autocorrelation properties   |
+| Min. sequence length  | Samples | 1023                                                                  |
+
+##### **Signal and spectrum analyser settings:**
+
+**Table 8.3.2.3-4: Spectrum analyser settings for spatial correlation for RTS**
+
+| Item                                                                                                                                                              | Unit              | Value                                                                 |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------|
+| Centre frequency                                                                                                                                                  | MHz               | Downlink centre frequency in 3GPP TS 36.508 [19] as required per band |
+| Min. sampling rate                                                                                                                                                | kHz               | 10                                                                    |
+| Min. measurement duration                                                                                                                                         | Wavelength (Note) | 2000                                                                  |
+| NOTE:    Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]<br>MS speed [ $\lambda$ /s] = MS speed [m/s] / Speed of light [m/s] * Centre frequency [Hz] |                   |                                                                       |
+
+The channel model specifications match those from Table 8.3.2.3-2.
+
+##### **Measurement Process:**
+
+For each antenna position, the signal generator continuously sends the Zadoff-Chu sequence to the channel emulator which applies the required channel model as specified in Table 8.3.2.3-2. The output RF signal from the channel emulator is connected to the TX antenna and received by the RX antenna which is connected to the RF input of the spectrum analyser or scope, Figure 8.3.1.2-2.
+
+The RF signals received by the RX antenna for different simulated antenna positions/separations are captured by the spectrum analyser or the scope. The spatial correlation analysis is performed by performing the cross-correlation operation directly on the received signals captured for different antenna positions/separations.
+
+#### 8.3.2.4 Cross-polarization
+
+This measurement checks how well the measured vertically or horizontally polarized power levels follow expected values.
+
+**Method of measurement:**    Stop the emulation and store traces from VNA.
+
+##### **VNA settings:**
+
+**Table 8.3.2.4-1: VNA settings for cross-polarization**
+
+| Item                                                                                                                                                           | Unit              | Value                                                                 |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------|
+| Center frequency                                                                                                                                               | MHz               | Downlink Center Frequency in 3GPP TS 36.508 [19] as required per band |
+| Span                                                                                                                                                           | MHz               | 10                                                                    |
+| RF output level                                                                                                                                                | dBm               | -15                                                                   |
+| Number of traces                                                                                                                                               |                   | 1000                                                                  |
+| Distance between traces in channel model                                                                                                                       | Wavelength (Note) | > 2                                                                   |
+| Number of points                                                                                                                                               |                   | 201                                                                   |
+| Averaging                                                                                                                                                      |                   | 1                                                                     |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]<br>MS speed [ $\lambda$ /s] = MS speed [m/s] / Speed of light [m/s] * Center frequency [Hz] |                   |                                                                       |
+
+##### **Channel model specification:**
+
+**Table 8.3.2.4-2: Channel model specification for cross-polarization.**
+
+| Item                  | Unit       | Value                                                                 |
+|-----------------------|------------|-----------------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink center frequency in 3GPP TS 36.508 [19] as required per band |
+| Channel model samples | wavelength | > 2000                                                                |
+| Channel model         |            | As specified in Clause 8.2                                            |
+| Mobile speed          | km/h       | 30                                                                    |
+
+##### **Measurement Procedure**
+
+1. Play or step through the channel model -> SCME UMi, or UMa X Corr.
+2. Measure the absolute power received at the center of the array, averaged over a statistically significant number of fades.
+  - a. Use a vertically polarized sleeve dipole to measure the V component.
+  - b. Use a horizontally polarized (vertically oriented) magnetic loop dipole, or a horizontally polarized sleeve dipole measured in two orthogonal horizontal positions and summed to measure the H component.
+3. Calculate the V/H ratio.
+4. Compare it with the theory -> 0.74dB for UMi, and 8.13dB for UMa.
+
+##### **Expected measurement results**
+
+V/H ratio (composite, i.e. all 6 paths combined) of the 3GPP SCME Umicro model is 0.74 dB and for Umacro 8.13 dB. The BS antennas are isotropic dipoles with +/- 45 degrees slant and subject to a foreshortening of the slanted radiating element. See channel model details specified in clause 8.2.
+
+For RTS, the cross-polarization is verified using the setup in Figure 8.3.1.2-2. The channel emulator is configured for a MIMO channel model with two transmit and two receive antenna patterns. The transmit antenna patterns are assumed to be dual-polarized equal power elements with a fixed  $0\lambda$  separation, 45 degrees slanted, Clause 8.5. One simulated receive antenna is configured as an ideal dipole with vertical polarization, and the other one is configured as ideal dipole with horizontal polarization. Both antennas have a fixed  $0\lambda$  separation.
+
+This cross polarization measurement verifies the correct power ratio of the different polarizations in the channel model. The measurement can be accomplished by either using a physical transmit and receive antenna with a single polarization while alternately changing the RX antenna polarization configuration in the fading emulator or by using physical dual-polarized antennas with high isolation between the two polarizations of the transmit and receive antennas. Both approaches guarantee that only the cross polarization of the channel model is verified.
+
+##### Channel model specification:
+
+The channel model specifications match those from Table 8.3.2.4-2.
+
+##### Measurement Procedure
+
+1. Play the channel model defined in Table 8.3.2.4-2.
+2. Measure the absolute power received at the RX antenna, averaged over a statistically sufficient number of fades (defined as channel model samples in Table 8.3.2.4-2).
+  - a. Measure the power intended for the vertically polarized receive antenna to measure the V component.
+  - b. Measure the power intended for the horizontally polarized receive antenna to measure the H component.
+3. Calculate the V/H ratio.
+
+Theoretical and expected measurement results are the same as MPAC.
+
+### 8.3.3 Reporting
+
+The tolerance for the channel model measurements is defined in tables 8.3.3-2, 8.3.3-3, 8.3.3-4 and 8.3.3-5.
+
+These tolerances are based on what can practically be measured for each metric in order that pass/fail limits can be defined for validation of acceptable channel model implementation. Studies of the impact on non-ideal channel model implementation have not been carried out and therefore it may be necessary in the future when a better understanding of the impact of the channel model implementation on throughput measurements is found, that these tolerance values may need to be revised.
+
+**Table 8.3.3-1: Void**
+
+**Table 8.3.3-2: Limits for PDP**
+
+| Maximum Power Deviation per Cluster                                                                                                                                                                                       | Maximum Excess Delay Deviation per Cluster |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|
+| $\pm 0.85\text{dB}$                                                                                                                                                                                                       | $\pm 11\text{ns}$                          |
+| NOTE 1: The PDP must be postprocessed with a running average of 9 elements                                                                                                                                                |                                            |
+| NOTE 2: These limits apply to the MPAC test methods using the geometric implementation of the SCME UMi channel model and for the RTS test method using the correlation-based implementation of the SCME UMi channel model |                                            |
+
+**Table 8.3.3-3: Limits for Doppler / Temporal Correlation for the geometric implementation**
+
+| $\lambda$ | Lower Limit | Upper Limit |
+|-----------|-------------|-------------|
+| 0         | 0.95        | 1           |
+| 0.1       | 0.8         | 1           |
+| 0.3       | 0.27        | 0.57        |
+| 0.4       | 0.27        | 0.5         |
+| 0.45      | 0.27        | 0.5         |
+| 0.6       | 0.37        | 0.5         |
+| 0.75      | 0.1         | 0.5         |
+| 0.8       | 0.06        | 0.37        |
+| 0.93      | 0.06        | 0.25        |
+| 1.05      | 0.06        | 0.31        |
+| 1.15      | 0.15        | 0.31        |
+| 1.25      | 0.075       | 0.31        |
+| 1.35      | 0           | 0.21        |
+| 1.45      | 0           | 0.21        |
+| 1.5       | 0           | 0.25        |
+| 1.65      | 0.1         | 0.25        |
+| 1.75      | 0           | 0.25        |
+| 5         | 0           | 0.2         |
+
+NOTE: These limits apply to the MPAC test method using the geometric implementation of the SCME UMi channel model
+
+**Table 8.3.3-3A: Limits for Doppler / Temporal Correlation for the correlation-based implementation**
+
+| $\lambda$ | Lower Limit | Upper Limit |
+|-----------|-------------|-------------|
+| 0         | 0.95        | 1           |
+| 0.08      | 0.8         | 1           |
+| 0.3       | 0           | 0.57        |
+| 0.45      | 0           | 0.5         |
+| 1.75      | 0           | 0.3         |
+| 5         | 0           | 0.18        |
+
+NOTE: These limits apply to the RTS test method using the correlation-based implementation of the SCME UMi channel model
+
+**Table 8.3.3-4: Limits for Spatial Correlation for the MPAC test method**
+
+| $\lambda$                                                                                                         | Lower Limit | Upper Limit |
+|-------------------------------------------------------------------------------------------------------------------|-------------|-------------|
+| 0                                                                                                                 | 0.99        | 1.015       |
+| 0.1                                                                                                               | 0.9         | 0.975       |
+| 0.2                                                                                                               | 0.70        | 0.83        |
+| 0.3                                                                                                               | 0.46        | 0.63        |
+| 0.4                                                                                                               | 0.22        | 0.4         |
+| 0.5                                                                                                               | 0           | 0.21        |
+| 0.6                                                                                                               | 0           | 0.18        |
+| 0.7                                                                                                               | 0           | 0.18        |
+| 0.8                                                                                                               | 0           | 0.2         |
+| 0.9                                                                                                               | 0.08        | 0.32        |
+| 1                                                                                                                 | 0.23        | 0.56        |
+| NOTE: These limits apply to the MPAC test method using the geometric implementation of the SCME UMi channel model |             |             |
+
+**Table 8.3.3-4A: Limits for Spatial Correlation for the RTS test method**
+
+| $\lambda$                                                                                                                | Lower Limit | Upper Limit |
+|--------------------------------------------------------------------------------------------------------------------------|-------------|-------------|
+| 0                                                                                                                        | 0.99        | 1.015       |
+| 0.1                                                                                                                      | 0.9         | 0.975       |
+| 0.2                                                                                                                      | 0.7         | 0.83        |
+| 0.3                                                                                                                      | 0.46        | 0.63        |
+| 0.4                                                                                                                      | 0.22        | 0.4         |
+| 0.5                                                                                                                      | 0           | 0.21        |
+| 0.6                                                                                                                      | 0           | 0.18        |
+| 0.7                                                                                                                      | 0           | 0.18        |
+| 0.8                                                                                                                      | 0           | 0.2         |
+| 1                                                                                                                        | 0           | 0.15        |
+| NOTE: These limits apply to the RTS test method using the correlation-based implementation of the SCME UMi channel model |             |             |
+
+**Table 8.3.3-5: Limits for Cross Polarization**
+
+| V/H Maximum Deviation                                                                                                                                                                                                         |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $\pm 0.9$ dB                                                                                                                                                                                                                  |
+| <b>NOTE:</b> These limits apply to the MPAC test method using the geometric implementation of the SCME UMi channel model and for the RTS test method using the correlation-based implementation of the SCME UMi channel model |
+
+## 8.4 Channel Model validation results
+
+### 8.4.1 Scope
+
+Clauses 8.4.2-6 contain the validation results of channel models defined in Clause 8.2 for companies using methods as described in Clauses 6.3.1.1 , 6.3.1.2 and 6.3.1.3. These results are based on three different types of channel emulators and setup vendors, and all three sets of results are included here for comparison.
+
+### 8.4.2 Power Delay Profile (PDP)
+
+The power delay profiles of the SCME UMi channel model specified in Clause 8.2 has been measured according to the procedures in 8.3.2.1. Figure 8.4.1-1a below illustrates the measured results for Band 13, and Band 7.
+
+**Figure 8.4.2-1: Void**
+
+![Normalized Power Delay Profile (dB) Band 13 - CE 1. A line graph showing multiple peaks in red against a grid. Y-axis ranges from -20 to 0 dB. X-axis is Time (s) scaled by 10^-6. Normalized Power Delay Profile (dB) Band 13 - CE 2. A line graph showing multiple peaks in red against a grid. Y-axis ranges from -20 to 0 dB. X-axis is Time (s) scaled by 10^-6.](0c1dec10830679ed9dab2f0cd5c3d313_img.jpg)
+
+(a)
+
+(b)
+
+Normalized Power Delay Profile (dB) Band 13 - CE 1. A line graph showing multiple peaks in red against a grid. Y-axis ranges from -20 to 0 dB. X-axis is Time (s) scaled by 10^-6. Normalized Power Delay Profile (dB) Band 13 - CE 2. A line graph showing multiple peaks in red against a grid. Y-axis ranges from -20 to 0 dB. X-axis is Time (s) scaled by 10^-6.
+
+![Six subplots (a-f) showing Power Delay Profile (PDP) verification measurements. (a) and (b) show Normalized PDP for Band 7 - CE 1 and CE 2 respectively. (c) and (d) show Normalized PDP for Band 7 - CE 1 and CE 2. (e) and (f) show Power Delay Profile for Vertical polarization (Model: SCME_UMI_MC_8DP) for Band 13 and Band 7 respectively. Each plot compares Measured data (blue line) with Ideal SCME (red dots).](53d8bef47c63e0897de4cd058bad2cbd_img.jpg)
+
+Figure 8.4.2-1a consists of six subplots labeled (a) through (f), arranged in a 3x2 grid. Subplots (a) and (b) are titled 'Normalized Power Delay Profile (dB) Band 7 - CE 1' and 'Normalized Power Delay Profile (dB) Band 7 - CE 2' respectively. Subplots (c) and (d) are titled 'Normalized Power Delay Profile (dB) Band 7 - CE 1' and 'Normalized Power Delay Profile (dB) Band 7 - CE 2' respectively. Subplots (e) and (f) are titled 'Power Delay Profile, Vertical polarization Model: SCME\_UMI\_MC\_8DP'. All subplots show a red line representing measured data and red dots representing ideal SCME data. The x-axis for (a) and (b) is 'Time (s)' ranging from 0 to 1 (x10<sup>-5</sup>). The x-axis for (c) and (d) is 'Time (s)' ranging from 0 to 1 (x10<sup>-5</sup>). The x-axis for (e) and (f) is 'Delay [μs]' ranging from 0 to 1. The y-axis for all subplots is 'Magnitude [dB]' ranging from -25 to 5. Subplots (e) and (f) include a legend indicating 'Measured' (blue line) and 'Ideal SCME' (red dots). A table of delay values in μs is provided in the bottom right of (e) and (f):
+
+| TAP | Delay [μs] |
+|-----|------------|
+| 1   | 0          |
+| 2   | 0.16       |
+| 3   | 0.027      |
+| 4   | 0.071      |
+| 5   | 0.27       |
+| 6   | 0.31       |
+
+Six subplots (a-f) showing Power Delay Profile (PDP) verification measurements. (a) and (b) show Normalized PDP for Band 7 - CE 1 and CE 2 respectively. (c) and (d) show Normalized PDP for Band 7 - CE 1 and CE 2. (e) and (f) show Power Delay Profile for Vertical polarization (Model: SCME\_UMI\_MC\_8DP) for Band 13 and Band 7 respectively. Each plot compares Measured data (blue line) with Ideal SCME (red dots).
+
+Figure 8.4.2-1a: For MPAC system 1, CE 1 (a) and CE 2 (b) PDP verification measurement for Band 13; for MPAC system 1, CE 1 (c) CE 2 (d) PDP verification measurement for Band 7; For MPAC system 2, PDP verification measurements for Band 13 (e) and Band 7 (f).
+
+Table 8.4.2-1a below summarizes the PDP verification results.
+
+Table 8.4.2-1: Void
+
+**Table 8.4.2-1a: Summary of PDP verification results at Band 13, and Band 7 from MPAC system providers**
+
+| MPAC System 1 and CE 1 Band 13 |            |      |       |            |       |       | MPAC System 1 and CE 2 Band 13 |      |       |            |       |       |
+|--------------------------------|------------|------|-------|------------|-------|-------|--------------------------------|------|-------|------------|-------|-------|
+| Cluster                        | Delay (ns) |      |       | Power (dB) |       |       | Delay (ns)                     |      |       | Power (dB) |       |       |
+|                                | Theory     | Meas | Delta | Theory     | Meas  | Delta | Theory                         | Meas | Delta | Theory     | Meas  | Delta |
+| 1                              | 0          | 0    | 0     | 0          | 0     | 0     | 0                              | 0    | 0     | 0          | 0     | 0     |
+| 2                              | 205        | 201  | 4     | -2.70      | -3.00 | 0.30  | 205                            | 204  | 1     | -2.70      | -3.06 | 0.36  |
+| 3                              | 285        | 280  | 5     | -1.30      | -1.10 | 0.20  | 285                            | 284  | 1     | -1.30      | -1.25 | 0.05  |
+| 4                              | 660        | 659  | 1     | -4.30      | -4.26 | 0.04  | 660                            | 660  | 0     | -4.30      | -4.39 | 0.09  |
+| 5                              | 805        | 800  | 5     | -6.00      | -6.00 | 0.00  | 805                            | 804  | 1     | -6.00      | -5.83 | 0.17  |
+| 6                              | 925        | 920  | 5     | -8.40      | -8.58 | 0.18  | 925                            | 925  | 0     | -8.40      | -8.39 | 0.01  |
+
+  
+
+| MPAC System 1 and CE 1 Band 7 |            |      |       |            |       |       | MPAC System 1 and CE 2 Band 7 |      |       |            |       |       |
+|-------------------------------|------------|------|-------|------------|-------|-------|-------------------------------|------|-------|------------|-------|-------|
+| Cluster                       | Delay (ns) |      |       | Power (dB) |       |       | Delay (ns)                    |      |       | Power (dB) |       |       |
+|                               | Theory     | Meas | Delta | Theory     | Meas  | Delta | Theory                        | Meas | Delta | Theory     | Meas  | Delta |
+| 1                             | 0          | 0    | 0     | 0          | 0     | 0     | 0                             | 0    | 0     | 0          | 0     | 0     |
+| 2                             | 205        | 200  | 5     | -2.70      | -2.94 | 0.24  | 205                           | 201  | 4     | -2.70      | -3.17 | 0.47  |
+| 3                             | 285        | 285  | 0     | -1.02      | -1.12 | 0.10  | 285                           | 287  | 2     | -1.30      | -1.18 | 0.12  |
+| 4                             | 660        | 656  | 4     | -4.30      | -4.59 | 0.29  | 660                           | 658  | 2     | -4.30      | -4.42 | 0.12  |
+| 5                             | 805        | 805  | 0     | -6.00      | -6.01 | 0.01  | 805                           | 807  | 2     | -6.00      | -6.01 | 0.01  |
+| 6                             | 925        | 923  | 2     | -8.40      | -8.43 | 0.03  | 925                           | 926  | 1     | -8.40      | -8.68 | 0.28  |
+
+  
+
+| MPAC System 2 and CE 1 Band 7 |            |      |       |            |       |       | MPAC System 2 and CE 1 Band 7 |      |       |            |       |       |
+|-------------------------------|------------|------|-------|------------|-------|-------|-------------------------------|------|-------|------------|-------|-------|
+| Cluster                       | Delay (ns) |      |       | Power (dB) |       |       | Delay (ns)                    |      |       | Power (dB) |       |       |
+|                               | Theory     | Meas | Delta | Theory     | Meas  | Delta | Theory                        | Meas | Delta | Theory     | Meas  | Delta |
+| 1                             | 0          | 0    | 0     | 0          | 0     | 0     | 0                             | 0    | 0     | 0          | 0     | 0     |
+| 2                             | 205        | 208  | 3     | -2.70      | -2.83 | 0.13  | 205                           | 200  | 5     | -2.70      | -2.81 | 0.11  |
+| 3                             | 285        | 290  | 5     | -1.30      | -1.29 | 0.00  | 285                           | 289  | 4     | -1.30      | -1.23 | 0.07  |
+| 4                             | 660        | 668  | 8     | -4.30      | -4.41 | 0.11  | 660                           | 665  | 5     | -4.30      | -4.44 | 0.14  |
+| 5                             | 805        | 812  | 7     | -6.00      | -5.73 | 0.27  | 805                           | 810  | 5     | -6.00      | -5.85 | 0.15  |
+| 6                             | 925        | 928  | 3     | -8.40      | -8.29 | 0.11  | 925                           | 930  | 5     | -8.40      | -8.27 | 0.13  |
+
+The results for the RTS method with geometric implementation are shown in Figure 8.4.2-2 for System 1 with CE1 for Band 13, in Figure 8.4.2-2a for System 2 with CE2 for Band 13, and in Figure 8.4.2-2b for System 2 with CE2 for Band 7.
+
+![Figure 8.4.2-2: Two line graphs showing Relative Power(dB) vs Delay(ns) for the RTS method with geometric implementation. The left graph shows 'Measured' (blue line) and 'Ideal' (red circles) data for System 1 with CE1 for Band 13. The right graph shows 'Measured' (blue line) and 'Ideal' (red circles) data for System 2 with CE2 for Band 13. Both graphs show a series of peaks representing multipath components, with the measured data closely following the ideal data points.](09b5a76dd3d981abcc585df1314ef30a_img.jpg)
+
+Figure 8.4.2-2: Two line graphs showing Relative Power(dB) vs Delay(ns) for the RTS method with geometric implementation. The left graph shows 'Measured' (blue line) and 'Ideal' (red circles) data for System 1 with CE1 for Band 13. The right graph shows 'Measured' (blue line) and 'Ideal' (red circles) data for System 2 with CE2 for Band 13. Both graphs show a series of peaks representing multipath components, with the measured data closely following the ideal data points.
+
+**Figure 8.4.2-2: SCMe UMa and UMi PDP verification measurement for the RTS method with geometric implementation for System 1 with CE1 for Band 13**
+
+![Two line graphs showing Power Delay Profile for Geometry-based SCME UMa and UMi. The left graph for UMa shows relative power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows relative power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured PDP (blue line) and Theoretical Values (red circles).](f455955c4bc84005728b4138f19098dc_img.jpg)
+
+Two line graphs showing Power Delay Profile for Geometry-based SCME UMa and UMi. The left graph for UMa shows relative power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows relative power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured PDP (blue line) and Theoretical Values (red circles).
+
+Figure 8.4.2-2a: SCMe UMa and UMi PDP verification measurement for the RTS method with geometric implementation for System 2 with CE2 for Band 13
+
+![Two line graphs showing Power Delay Profile for Geometry-based SCME UMa and UMi. The left graph for UMa shows relative power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows relative power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured PDP (blue line) and Theoretical Values (red circles).](67408c41c75d983c13a9bd3d66953f3c_img.jpg)
+
+Two line graphs showing Power Delay Profile for Geometry-based SCME UMa and UMi. The left graph for UMa shows relative power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows relative power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured PDP (blue line) and Theoretical Values (red circles).
+
+Figure 8.4.2-2b: SCMe UMa and UMi PDP verification measurement for the RTS method with geometric implementation for System 2 with CE2 for Band 7
+
+The results for the RTS method with correlation implementation (Jake's Doppler spectrum) are shown in Figures 8.4.2-3 to 8.4.2-3b:
+
+![Two line graphs showing Power Delay Profile for SCME UMa and UMi. The left graph for UMa shows power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured (blue line) and Theory (red circles).](ebce469575e197e659de896b83c7a9cc_img.jpg)
+
+Two line graphs showing Power Delay Profile for SCME UMa and UMi. The left graph for UMa shows power in dB vs delay in ns (0 to 5000) with peaks at approximately 0, 200, 400, 1000, 2700, and 4500 ns. The right graph for UMi shows power in dB vs delay in ns (0 to 1000) with peaks at approximately 0, 200, 300, 650, 800, and 950 ns. Both graphs compare Measured (blue line) and Theory (red circles).
+
+Figure 8.4.2-3: SCMe UMa and UMi PDP verification measurement for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 1 with CE1 for Band 13
+
+![Power Delay Profile for Correlation-based SCME UMa. The graph shows Relative Power in dB (y-axis, -50 to 5) versus Delay in ns (x-axis, 0 to 5000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 400, 1000, 2700, and 4500 ns.](a346e19f92f1699e3f96432c0464c957_img.jpg)
+
+Power Delay Profile for Correlation-based SCME UMa. The graph shows Relative Power in dB (y-axis, -50 to 5) versus Delay in ns (x-axis, 0 to 5000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 400, 1000, 2700, and 4500 ns.
+
+![Power Delay Profile for Correlation-based SCME UMi. The graph shows Relative Power in dB (y-axis, -50 to 5) versus Delay in ns (x-axis, 0 to 1000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 300, 650, 800, and 950 ns.](834359004b142e33f72aea7a3de2440f_img.jpg)
+
+Power Delay Profile for Correlation-based SCME UMi. The graph shows Relative Power in dB (y-axis, -50 to 5) versus Delay in ns (x-axis, 0 to 1000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 300, 650, 800, and 950 ns.
+
+**Figure 8.4.2-3a: SCMe UMa and UMi PDP verification measurement for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 13**
+
+![Power Delay Profile for Correlation-based SCME UMa. The graph shows Relative Power in dB (y-axis, -60 to 0) versus Delay in ns (x-axis, 0 to 5000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 400, 1000, 2700, and 4500 ns.](f22e617a7aef13de5ffd8e390bfda1c3_img.jpg)
+
+Power Delay Profile for Correlation-based SCME UMa. The graph shows Relative Power in dB (y-axis, -60 to 0) versus Delay in ns (x-axis, 0 to 5000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 400, 1000, 2700, and 4500 ns.
+
+![Power Delay Profile for Correlation-based SCME UMi. The graph shows Relative Power in dB (y-axis, -60 to 0) versus Delay in ns (x-axis, 0 to 1000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 300, 650, 800, and 950 ns.](1071a283fcadf8d3e2ff23b77eefd4a8_img.jpg)
+
+Power Delay Profile for Correlation-based SCME UMi. The graph shows Relative Power in dB (y-axis, -60 to 0) versus Delay in ns (x-axis, 0 to 1000). It compares Measured PDP (blue line) with Theoretical Values (red circles). Peaks are visible at approximately 0, 200, 300, 650, 800, and 950 ns.
+
+**Figure 8.4.2-3b: SCMe UMa and UMi PDP verification measurement for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 7**
+
+The summarized results can be found in Tables 8.4.2-2 to 8.4.2-3b:
+
+**Table 8.4.2-2: Summary of PDP verification results at Band 13 for the RTS method with geometric implementation for System 1 with CE1 for Band 13**
+
+| <b>SCME Urban Macro</b> |                   |                 |                   |                   |                 |                   |
+|-------------------------|-------------------|-----------------|-------------------|-------------------|-----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 255               | 256             | 1                 | -1.7              | -2              | -0.3              |
+| 3                       | 360               | 360             | 0                 | -2.2              | -2.2            | 0                 |
+| 4                       | 1040              | 1040            | 0                 | -5.2              | -5.2            | 0                 |
+| 5                       | 2730              | 2728            | -2                | -9.1              | -9.4            | -0.3              |
+| 6                       | 4600              | 4600            | 0                 | -12.5             | -12.5           | 0                 |
+| <b>SCME Urban Micro</b> |                   |                 |                   |                   |                 |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 205               | 208             | 3                 | -2.7              | -2.6            | 0.1               |
+| 3                       | 285               | 288             | 3                 | -1.3              | -1.2            | 0.1               |
+| 4                       | 660               | 664             | 4                 | -4.3              | -4.5            | -0.2              |
+| 5                       | 805               | 808             | 3                 | -6                | -6.1            | -0.1              |
+| 6                       | 925               | 928             | 3                 | -8.4              | -8.3            | 0.1               |
+
+**Table 8.4.2-2a: Summary of PDP verification results at Band 13 for the RTS method with geometric implementation for System 2 with CE2 for Band 13**
+
+| <b>SCME Urban Macro</b> |                   |                 |                   |                   |                 |                   |
+|-------------------------|-------------------|-----------------|-------------------|-------------------|-----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 255               | 255             | 0                 | -1.7              | -1.7            | 0                 |
+| 3                       | 360               | 360             | 0                 | -2.2              | -2.2            | 0                 |
+| 4                       | 1040              | 1040            | 0                 | -5.2              | -5.2            | 0                 |
+| 5                       | 2730              | 2730            | 0                 | -9.1              | -9.3            | -0.2              |
+| 6                       | 4600              | 4600            | 0                 | -12.5             | -12.5           | 0                 |
+| <b>SCME Urban Micro</b> |                   |                 |                   |                   |                 |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 205               | 205             | 0                 | -2.7              | -2.8            | -0.1              |
+| 3                       | 285               | 285             | 0                 | -1.3              | -1              | 0.3               |
+| 4                       | 660               | 660             | 0                 | -4.3              | -4.3            | 0                 |
+| 5                       | 805               | 805             | 0                 | -6                | -6              | 0                 |
+| 6                       | 925               | 925             | 0                 | -8.4              | -8.4            | 0                 |
+
+**Table 8.4.2-2b: Summary of PDP verification results at Band 13 for the RTS method with geometric implementation for System 2 with CE2 for Band 7**
+
+| <b>SCME Urban Macro</b> |                   |                 |                   |                   |                 |                   |
+|-------------------------|-------------------|-----------------|-------------------|-------------------|-----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 255               | 255             | 0                 | -1.7              | -1.7            | 0                 |
+| 3                       | 360               | 360             | 0                 | -2.2              | -2.2            | 0                 |
+| 4                       | 1040              | 1040            | 0                 | -5.2              | -5.2            | 0                 |
+| 5                       | 2730              | 2730            | 0                 | -9.1              | -9.1            | 0                 |
+| 6                       | 4600              | 4600            | 0                 | -12.5             | -12.5           | 0                 |
+| <b>SCME Urban Micro</b> |                   |                 |                   |                   |                 |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 205               | 205             | 0                 | -2.7              | -2.7            | 0                 |
+| 3                       | 285               | 285             | 0                 | -1.3              | -1.3            | 0                 |
+| 4                       | 660               | 660             | 0                 | -4.3              | -4.3            | 0                 |
+| 5                       | 805               | 805             | 0                 | -6                | -6              | 0                 |
+| 6                       | 925               | 925             | 0                 | -8.4              | -8.4            | 0                 |
+
+**Table 8.4.2-3: Summary of PDP verification results for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 1 with CE1 for Band 13**
+
+| <b>SCME Urban Macro</b> |                   |                 |                   |                   |                 |                   |
+|-------------------------|-------------------|-----------------|-------------------|-------------------|-----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 255               | 256             | 1                 | -1.7              | -1.6            | 0.1               |
+| 3                       | 360               | 360             | 0                 | -2.2              | -2.1            | 0.1               |
+| 4                       | 1040              | 1040            | 0                 | -5.2              | -5.2            | 0                 |
+| 5                       | 2730              | 2728            | -2                | -9.1              | -9.7            | -0.6              |
+| 6                       | 4600              | 4600            | 0                 | -12.5             | -12.3           | 0.2               |
+| <b>SCME Urban Micro</b> |                   |                 |                   |                   |                 |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theory</b>     | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 205               | 208             | 3                 | -2.7              | -2.9            | 0.2               |
+| 3                       | 285               | 288             | 3                 | -1.3              | -1.4            | -0.1              |
+| 4                       | 660               | 664             | 4                 | -4.3              | -4.9            | -0.6              |
+| 5                       | 805               | 808             | 3                 | -6                | -6              | 0                 |
+| 6                       | 925               | 928             | 3                 | -8.4              | -8.3            | 0.1               |
+
+**Table 8.4.2-3a: Summary of PDP verification results for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 13**
+
+| <b>SCME Urban Macro</b> |                   |                |                   |                   |                |                   |
+|-------------------------|-------------------|----------------|-------------------|-------------------|----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                |                   | <b>Power (dB)</b> |                |                   |
+|                         | <b>Theor</b>      | <b>Measure</b> | <b>Delta (ns)</b> | <b>Theor</b>      | <b>Measure</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0              | 0                 | 0                 | 0              | 0                 |
+| 2                       | 255               | 255            | 0                 | -1.7              | -1.8           | -0.1              |
+| 3                       | 360               | 360            | 0                 | -2.2              | -2.2           | 0                 |
+| 4                       | 1040              | 1040           | 0                 | -5.2              | -4.9           | 0.3               |
+| 5                       | 2730              | 2730           | 0                 | -9.1              | -9.1           | 0                 |
+| 6                       | 4600              | 4600           | 0                 | -12.5             | -12.4          | 0.1               |
+| <b>SCME Urban Micro</b> |                   |                |                   |                   |                |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                |                   | <b>Power (dB)</b> |                |                   |
+|                         | <b>Theor</b>      | <b>Measure</b> | <b>Delta (ns)</b> | <b>Theor</b>      | <b>Measure</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0              | 0                 | 0                 | 0              | 0                 |
+| 2                       | 205               | 205            | 0                 | -2.7              | -2.7           | 0                 |
+| 3                       | 285               | 285            | 0                 | -1.3              | -1.4           | -0.1              |
+| 4                       | 660               | 660            | 0                 | -4.3              | -4.2           | 0.1               |
+| 5                       | 805               | 805            | 0                 | -6                | -6.1           | -0.1              |
+| 6                       | 925               | 925            | 0                 | -8.4              | -8.7           | -0.3              |
+
+**Table 8.4.2-3b: Summary of PDP verification results for the RTS method with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 7**
+
+| <b>SCME Urban Macro</b> |                   |                 |                   |                   |                 |                   |
+|-------------------------|-------------------|-----------------|-------------------|-------------------|-----------------|-------------------|
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theo</b>       | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 255               | 255             | 0                 | -1.7              | -1.8            | -0.1              |
+| 3                       | 360               | 360             | 0                 | -2.2              | -2.1            | 0.1               |
+| 4                       | 1040              | 1040            | 0                 | -5.2              | -5.2            | 0                 |
+| 5                       | 2730              | 2730            | 0                 | -9.1              | -9.2            | -0.1              |
+| 6                       | 4600              | 4600            | 0                 | -12.5             | -12.6           | -0.1              |
+| <b>SCME Urban Micro</b> |                   |                 |                   |                   |                 |                   |
+| <b>Cluster</b>          | <b>Delay (ns)</b> |                 |                   | <b>Power (dB)</b> |                 |                   |
+|                         | <b>Theory</b>     | <b>Measured</b> | <b>Delta (ns)</b> | <b>Theo</b>       | <b>Measured</b> | <b>Delta (dB)</b> |
+| 1                       | 0                 | 0               | 0                 | 0                 | 0               | 0                 |
+| 2                       | 205               | 205             | 0                 | -2.7              | -2.8            | -0.1              |
+| 3                       | 285               | 285             | 0                 | -1.3              | -1.3            | 0                 |
+| 4                       | 660               | 660             | 0                 | -4.3              | -4.3            | 0                 |
+| 5                       | 805               | 805             | 0                 | -6                | -6.1            | -0.1              |
+| 6                       | 925               | 925             | 0                 | -8.4              | -8.3            | 0.1               |
+
+### 8.4.3. Doppler / Temporal Correlation
+
+The Doppler spread and temporal correlation of the SCME UMi channel model defined in clause 8.2 has been characterized according to clause 8.3.2.2. Figure 8.4.3-1a below illustrates the measured results for Band 13, and Band 7.
+
+**Figure 8.4.3-1: Void**
+
+![Six line graphs (a-f) showing temporal correlation vs separation/distance for various bands and systems. Each graph includes 'Measured', 'Lower', and 'Upper' data series.](449dd9d482c5b47f1c013ce3e18b09e6_img.jpg)
+
+The figure consists of six subplots arranged in a 3x2 grid, labeled (a) through (f). Each subplot shows 'Correlation' on the y-axis (ranging from 0 to 1) against 'Separation (Wavelengths)' or 'Distance (λ)' on the x-axis (ranging from 0 to 5). Each plot contains three data series: 'Measured' (red line), 'Lower' (magenta line), and 'Upper' (cyan line). The 'Measured' series shows a sharp drop from 1.0 at zero separation to around 0.2-0.3, followed by small oscillations. The 'Lower' series follows the 'Measured' series closely but with more pronounced dips. The 'Upper' series drops less sharply and remains relatively flat around 0.2-0.3.
+
+- (a) Temporal Correlation Band 13 - CE 1
+- (b) Temporal Correlation Band 13 - CE 2
+- (c) Temporal Correlation Band 7 - CE 1
+- (d) Temporal Correlation Band 7 - CE 2
+- (e) Temporal Correlation SCME UMI - BAND13
+- (f) Temporal Correlation UMI - BAND7
+
+Six line graphs (a-f) showing temporal correlation vs separation/distance for various bands and systems. Each graph includes 'Measured', 'Lower', and 'Upper' data series.
+
+**Figure 8.4.3-1a: For MPAC system 1, CE 1 (a) and CE 2 (b) temporal correlation measurements for Band 13; for MPAC system 1, CE 1 (c) CE 2 (d) temporal correlation measurements for Band 7; For MPAC system 2, temporal correlation measurements for Band 13 (e) and Band 7 (f)**
+
+**Figure 8.4.3-2: Void**
+
+**Figure 8.4.3-3: Void**
+
+The temporal correlation results for the RTS method using the geometric implementation are shown in Figures 8.4.3-4 to 8.4.3-4b:
+
+![Two line graphs showing temporal correlation (Rt) vs lambda for LteUma and LteUmi. Each graph compares 'Measurement' (red line) and 'Theoretical' (black line) results. The x-axis (lambda) ranges from 0 to 5, and the y-axis (Rt) ranges from 0 to 1. Both graphs show a sharp initial drop from Rt=1 followed by oscillatory behavior.](26f6e6fd981d9bcf4ab4100aebb0400b_img.jpg)
+
+Figure 8.4.3-4 displays two plots of Temporal correlation ( $R_t$ ) versus  $\lambda$  for the RTS method with geometric implementation for System 1 with CE1 for Band 13. The left plot is for LteUma and the right plot is for LteUmi. Both plots show 'Measurement' (red line) and 'Theoretical' (black line) results. The x-axis ( $\lambda$ ) ranges from 0 to 5, and the y-axis ( $R_t$ ) ranges from 0 to 1. The correlation starts at 1.0 and decays rapidly, exhibiting oscillatory behavior as  $\lambda$  increases.
+
+Two line graphs showing temporal correlation (Rt) vs lambda for LteUma and LteUmi. Each graph compares 'Measurement' (red line) and 'Theoretical' (black line) results. The x-axis (lambda) ranges from 0 to 5, and the y-axis (Rt) ranges from 0 to 1. Both graphs show a sharp initial drop from Rt=1 followed by oscillatory behavior.
+
+**Figure 8.4.3-4: Temporal correlation measurements of SCMe UMa and UMi for the RTS method with geometric implementation for System 1 with CE1 for Band 13**
+
+![Two line graphs showing Temporal Correlation vs Wavelength in lambda for SCMe UMa and UMi. The left graph for UMa compares 'Measured Correlation' (blue line) and 'Ideal Correlation' (dashed grey line). The right graph for UMi compares 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis ranges from 0 to 5, and the y-axis ranges from 0 to 1.](624646367ef6cd220973a363f00310a0_img.jpg)
+
+Figure 8.4.3-4a displays two plots of Temporal Correlation versus Wavelength in  $\lambda$  for the RTS method with geometric implementation for System 2 with CE2 for Band 13. The left plot is for SCMe UMa and the right plot is for SCMe UMi. Both plots show 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis (Wavelength in  $\lambda$ ) ranges from 0 to 5, and the y-axis (Temporal Correlation) ranges from 0 to 1. The correlation starts at 1.0 and decays rapidly, exhibiting oscillatory behavior as Wavelength in  $\lambda$  increases.
+
+Two line graphs showing Temporal Correlation vs Wavelength in lambda for SCMe UMa and UMi. The left graph for UMa compares 'Measured Correlation' (blue line) and 'Ideal Correlation' (dashed grey line). The right graph for UMi compares 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis ranges from 0 to 5, and the y-axis ranges from 0 to 1.
+
+**Figure 8.4.3-4a: Temporal correlation measurements of SCMe UMa and UMi for the RTS method with geometric implementation for System 2 with CE2 for Band 13**
+
+![Two line graphs showing Temporal Correlation vs Wavelength in lambda for SCMe UMa and UMi. The left graph for UMa compares 'Measured Correlation' (blue line) and 'Ideal Correlation' (dashed grey line). The right graph for UMi compares 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis ranges from 0 to 5, and the y-axis ranges from 0 to 1.](45ab13a475fe6b64200c003830b2a51c_img.jpg)
+
+Figure 8.4.3-4b displays two plots of Temporal Correlation versus Wavelength in  $\lambda$  for the RTS method with geometric implementation for System 2 with CE2 for Band 7. The left plot is for SCMe UMa and the right plot is for SCMe UMi. Both plots show 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis (Wavelength in  $\lambda$ ) ranges from 0 to 5, and the y-axis (Temporal Correlation) ranges from 0 to 1. The correlation starts at 1.0 and decays rapidly, exhibiting oscillatory behavior as Wavelength in  $\lambda$  increases.
+
+Two line graphs showing Temporal Correlation vs Wavelength in lambda for SCMe UMa and UMi. The left graph for UMa compares 'Measured Correlation' (blue line) and 'Ideal Correlation' (dashed grey line). The right graph for UMi compares 'Measured Correlation' (blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (red lines). The x-axis ranges from 0 to 5, and the y-axis ranges from 0 to 1.
+
+**Figure 8.4.3-4b: Temporal correlation measurements of SCMe UMa and UMi for the RTS method with geometric implementation for System 2 with CE2 for Band 7**
+
+The temporal correlation results for the radiated two-stage method using correlation implementation of SCME (Jake's Doppler spectrum) are shown in Figures 8.4.3-5 to 8.4.3-5b:
+
+![Two line graphs showing temporal correlation for SCME Uma and UMi. The left graph is 'Time correlation for SCME Uma' and the right is 'Time correlation for SCME UMi'. Both plot |Temporal Correlation| (0 to 1) against Wavelength in lambda (0 to 5). Each graph contains two series: 'Measured' (solid black line) and 'Theory' (dashed red line). Both series show an initial high correlation at 0 lambda that decays and oscillates as wavelength increases, with the two lines closely overlapping.](c21fe89d8034ec5b80bd47c1cd710202_img.jpg)
+
+Two line graphs showing temporal correlation for SCME Uma and UMi. The left graph is 'Time correlation for SCME Uma' and the right is 'Time correlation for SCME UMi'. Both plot |Temporal Correlation| (0 to 1) against Wavelength in lambda (0 to 5). Each graph contains two series: 'Measured' (solid black line) and 'Theory' (dashed red line). Both series show an initial high correlation at 0 lambda that decays and oscillates as wavelength increases, with the two lines closely overlapping.
+
+Figure 8.4.3-5: Temporal correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi with correlation implementation (Jake's Doppler spectrum) for System 1 with CE1 for Band 13
+
+![Two line graphs for System 2 with CE2 for Band 13. The left graph is 'Temporal Correlation for Correlation-based SCME UMa' and the right is 'Temporal Correlation for Correlation-based SCME UMi'. Both plot 'Temporal Correlation' (0 to 1) against 'Wavelength in lambda' (0 to 5). The left graph shows 'Measured Correlation' (solid blue line) and 'Ideal Correlation' (dashed grey line). The right graph shows 'Measured Correlation' (solid blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (solid red line). In both cases, the correlation decays and oscillates with wavelength.](38e1f09a72ec6ec6cdce4357bc9b4024_img.jpg)
+
+Two line graphs for System 2 with CE2 for Band 13. The left graph is 'Temporal Correlation for Correlation-based SCME UMa' and the right is 'Temporal Correlation for Correlation-based SCME UMi'. Both plot 'Temporal Correlation' (0 to 1) against 'Wavelength in lambda' (0 to 5). The left graph shows 'Measured Correlation' (solid blue line) and 'Ideal Correlation' (dashed grey line). The right graph shows 'Measured Correlation' (solid blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (solid red line). In both cases, the correlation decays and oscillates with wavelength.
+
+Figure 8.4.3-5a: Temporal correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 13
+
+![Two line graphs for System 2 with CE2 for Band 7. The left graph is 'Temporal Correlation for Correlation-based SCME UMa' and the right is 'Temporal Correlation for Correlation-based SCME UMi'. Both plot 'Temporal Correlation' (0 to 1) against 'Wavelength in lambda' (0 to 5). The left graph shows 'Measured Correlation' (solid blue line) and 'Ideal Correlation' (dashed grey line). The right graph shows 'Measured Correlation' (solid blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (solid red line). The correlation decays and oscillates with wavelength, similar to the Band 13 results.](35a76ce9ad49a4aa1c1a5a3031ffbc71_img.jpg)
+
+Two line graphs for System 2 with CE2 for Band 7. The left graph is 'Temporal Correlation for Correlation-based SCME UMa' and the right is 'Temporal Correlation for Correlation-based SCME UMi'. Both plot 'Temporal Correlation' (0 to 1) against 'Wavelength in lambda' (0 to 5). The left graph shows 'Measured Correlation' (solid blue line) and 'Ideal Correlation' (dashed grey line). The right graph shows 'Measured Correlation' (solid blue line), 'Ideal Correlation' (dashed grey line), and '3GPP Boundaries' (solid red line). The correlation decays and oscillates with wavelength, similar to the Band 13 results.
+
+Figure 8.4.3-5b: Temporal correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi with correlation implementation (Jake's Doppler spectrum) for System 2 with CE2 for Band 7
+
+### 8.4.4 Spatial correlation
+
+The spatial correlation properties of the SCME UMi channel model defined in clause 8.2 has been characterized according to clause 8.3.2.3. Figure 8.4.4-1a below illustrates the measured results for Band 13, and Band 7.
+
+Figure 8.4.4-1: Void
+
+![Six subplots (a-f) showing spatial correlation vs separation for different bands and configurations. (a) Band 13 - CE 1, (b) Band 13 - CE 2, (c) Band 7 - CE 1, (d) Band 7 - CE 2, (e) SCME UMi - BAND13, (f) SCME UMi - BAND7. Each plot shows Measured, Lower, and Upper correlation curves.](fd6ee6f896324983fe3a8e9ee6c534b3_img.jpg)
+
+The figure consists of six subplots arranged in a 3x2 grid, labeled (a) through (f). Each subplot shows 'Correlation' on the y-axis (ranging from 0 to 1) and 'Separation (Wavelengths)' on the x-axis (ranging from 0 to 1). Each plot contains three curves: 'Measured' (red line), 'Lower' (magenta line), and 'Upper' (cyan line). All curves start at a correlation of 1.0 at zero separation and generally decrease as separation increases, reaching a minimum around 0.5 to 0.7 wavelengths before slightly increasing towards 1.0 at 1.0 wavelength separation. The 'Upper' curve consistently shows higher correlation than the 'Measured' curve, which in turn shows higher correlation than the 'Lower' curve.
+
+- (a) Spatial Correlation Band 13 - CE 1
+- (b) Spatial Correlation Band 13 - CE 2
+- (c) Spatial Correlation Band 7 - CE 1
+- (d) Spatial Correlation Band 7 - CE 2
+- (e) Spatial Correlation SCME UMi - BAND13
+- (f) Spatial Correlation SCME UMi - BAND7
+
+Six subplots (a-f) showing spatial correlation vs separation for different bands and configurations. (a) Band 13 - CE 1, (b) Band 13 - CE 2, (c) Band 7 - CE 1, (d) Band 7 - CE 2, (e) SCME UMi - BAND13, (f) SCME UMi - BAND7. Each plot shows Measured, Lower, and Upper correlation curves.
+
+Figure 8.4.4-1a: For MPAC system 1, CE 1 (a) and CE 2 (b) spatial correlation measurements for Band 13; for MPAC system 1, CE 1 (c) CE 2 (d) spatial correlation measurements for Band 7; For MPAC system 2, spatial correlation measurements for Band 13 (e) and Band 7 (f)
+
+Figure 8.4.4-2: Void
+
+Figure 8.4.4-3: Void
+
+The spatial correlation results for the RTS method using correlation implementation of SCME (Jake's Doppler spectrum) are shown in Figures 8.4.4-4 to 8.4.4-4b.
+
+![Two line graphs showing spatial correlation for SCEM UMa and UMi. The left graph is for SCEM UMa and the right is for SCEM UMi. Both plot correlation coefficient (0 to 1) against antenna distance in lambda (-0.5 to 0.5). Theory is shown as a blue line with circles, and Measured as a red line with squares. Both curves peak at 1.0 at 0 lambda distance.](92f8a2dda0aa6e2c03e3fe24131ab6fe_img.jpg)
+
+The figure contains two subplots. The left subplot is titled 'Spatial correlation for SCEM UMa' and the right is titled 'Spatial correlation for SCEM UMi'. Both plots show the 'Correlation coefficient' on the y-axis (ranging from 0 to 1) against the 'Distance between two antennas (lambda)' on the x-axis (ranging from -0.5 to 0.5). Each plot compares 'Theory' (blue line with circle markers) and 'Measured' (red line with square markers) data. In both cases, the correlation starts around 0.6 at -0.5 lambda, rises to a peak of 1.0 at 0 lambda, and then decreases back towards 0.6 at 0.5 lambda. The two lines are nearly perfectly overlaid.
+
+Two line graphs showing spatial correlation for SCEM UMa and UMi. The left graph is for SCEM UMa and the right is for SCEM UMi. Both plot correlation coefficient (0 to 1) against antenna distance in lambda (-0.5 to 0.5). Theory is shown as a blue line with circles, and Measured as a red line with squares. Both curves peak at 1.0 at 0 lambda distance.
+
+Figure 8.4.4-4: Spatial correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi (Jake's Doppler spectrum) for System 1 with CE1 for Band 13
+
+![Two line graphs showing spatial correlation for Correlation-based SCME UMa and UMi. The left graph is for UMa and the right is for UMi. Both plot |Corr| (0 to 1) against antenna spacing in lambda (0 to 1). Measured Correlation is a blue line with circles, Ideal Correlation is a dashed grey line, and 3GPP Boundaries are shown as red lines in the UMi plot.](fc3763c02020b3a260045bbadc1d36ba_img.jpg)
+
+The figure contains two subplots. The left subplot is titled 'Spatial Correlation for Correlation-based SCME UMa' and the right is titled 'Spatial Correlation for Correlation-based SCME UMi'. Both plots show the magnitude of correlation, '|Corr|', on the y-axis (ranging from 0 to 1) against 'Antenna Spacing in  $\lambda$ ' on the x-axis (ranging from 0 to 1). The left plot compares 'Measured Correlation' (blue line with circles) and 'Ideal Correlation' (dashed grey line). The right plot compares the same two lines and adds '3GPP Boundaries' (solid red lines). In both plots, the correlation starts at 1.0 at 0 lambda and decreases as spacing increases. The measured correlation in the UMi plot drops more sharply than in the UMa plot, reaching a minimum around 0.6 lambda before slightly rising, while the 3GPP boundary remains higher.
+
+Two line graphs showing spatial correlation for Correlation-based SCME UMa and UMi. The left graph is for UMa and the right is for UMi. Both plot |Corr| (0 to 1) against antenna spacing in lambda (0 to 1). Measured Correlation is a blue line with circles, Ideal Correlation is a dashed grey line, and 3GPP Boundaries are shown as red lines in the UMi plot.
+
+Figure 8.4.4-a: Spatial correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi (Jake's Doppler spectrum) for System 2 with CE2 for Band 13
+
+![Two line graphs showing spatial correlation for Correlation-based SCME UMa and UMi for Band 7. The left graph is for UMa and the right is for UMi. Both plot |Corr| (0 to 1) against antenna spacing in lambda (0 to 1). Measured Correlation is a blue line with circles, and Ideal Correlation is a dashed grey line.](8cf12562763d72a28bb42fd6ff4905ac_img.jpg)
+
+The figure contains two subplots. The left subplot is titled 'Spatial Correlation for Correlation-based SCME UMa' and the right is titled 'Spatial Correlation for Correlation-based SCME UMi'. Both plots show the magnitude of correlation, '|Corr|', on the y-axis (ranging from 0 to 1) against 'Antenna Spacing in  $\lambda$ ' on the x-axis (ranging from 0 to 1). The left plot compares 'Measured Correlation' (blue line with circles) and 'Ideal Correlation' (dashed grey line). The right plot compares the same two lines. In both plots, the correlation starts at 1.0 at 0 lambda and decreases as spacing increases. The measured correlation in the UMi plot drops more sharply than in the UMa plot, reaching a minimum around 0.6 lambda before slightly rising.
+
+Two line graphs showing spatial correlation for Correlation-based SCME UMa and UMi for Band 7. The left graph is for UMa and the right is for UMi. Both plot |Corr| (0 to 1) against antenna spacing in lambda (0 to 1). Measured Correlation is a blue line with circles, and Ideal Correlation is a dashed grey line.
+
+Figure 8.4.4-b: Spatial correlation measurements for the radiated two-stage method using correlation implementation of SCME UMa and UMi (Jake's Doppler spectrum) for System 2 with CE2 for Band 7
+
+The spatial correlation results for the RTS method using geometric implementation of SCME are shown in Figures 8.4.4-5 to 8.4.4-5b.
+
+![Two line graphs showing spatial correlation for SCME UMa and UMi for System 1 with CE1 for Band 13. The left graph is for UMa and the right is for UMi. Both plot correlation coefficient against antenna distance in lambda, comparing theoretical and measured results.](4c617a4f2bf25b6cee75c21d6b15136e_img.jpg)
+
+The figure contains two line graphs. The left graph is titled "Spatial correlation for SCME UMa" and the right graph is titled "Spatial correlation for Single Cluster SCME UMi". Both graphs plot the "Correlation coefficient" on the y-axis (ranging from 0 to 1) against the "Distance between two antennas (lambda)" on the x-axis (ranging from -0.5 to 0.5). Each graph contains two data series: "Theoretical" (represented by a black line with square markers) and "Measurement" (represented by a red line with square markers). In both cases, the correlation starts at approximately 0.5 at -0.5 lambda, rises to a peak of 1.0 at 0 lambda, and then decreases back towards 0.5 at 0.5 lambda. The two lines are nearly perfectly overlaid, showing excellent agreement between theory and measurement.
+
+Two line graphs showing spatial correlation for SCME UMa and UMi for System 1 with CE1 for Band 13. The left graph is for UMa and the right is for UMi. Both plot correlation coefficient against antenna distance in lambda, comparing theoretical and measured results.
+
+Figure 8.4.4-5: Spatial correlation measurements for the RTS method using geometric implementation of SCME UMa and UMi for System 1 with CE1 for Band 13
+
+![Two line graphs showing spatial correlation for Geometry-based SCME UMa and UMi for System 2 with CE2 for Band 13. The left graph is for UMa and the right is for UMi. Both plot |Corr| against antenna spacing in lambda, comparing measured and ideal correlation.](faff5ea2bac20b616b62b35da5a5d67c_img.jpg)
+
+The figure contains two line graphs. The left graph is titled "Spatial Correlation for Geometry-based SCME UMa" and the right graph is titled "Spatial Correlation for Geometry-based SCME UMi". Both graphs plot the magnitude of correlation, "|Corr|", on the y-axis (ranging from 0 to 1) against "Antenna Spacing in  $\lambda$ " on the x-axis (ranging from 0 to 1). Each graph contains two data series: "Measured Correlation" (represented by a blue line with circle markers) and "Ideal Correlation" (represented by a dashed grey line). In both cases, the correlation starts at 1.0 at 0 lambda and decreases as spacing increases. The measured correlation follows the ideal correlation very closely throughout the entire range.
+
+Two line graphs showing spatial correlation for Geometry-based SCME UMa and UMi for System 2 with CE2 for Band 13. The left graph is for UMa and the right is for UMi. Both plot |Corr| against antenna spacing in lambda, comparing measured and ideal correlation.
+
+Figure 8.4.4-5a: Spatial correlation measurements for the RTS method using geometric implementation of SCME UMa and UMi for System 2 with CE2 for Band 13
+
+![Two line graphs showing spatial correlation for Geometry-based SCME UMa and UMi for System 2 with CE2 for Band 7. The left graph is for UMa and the right is for UMi. Both plot |Corr| against antenna spacing in lambda, comparing measured and ideal correlation.](5ae38ef48a8b04f4e6ad410da4555172_img.jpg)
+
+The figure contains two line graphs. The left graph is titled "Spatial Correlation for Geometry-based SCME UMa" and the right graph is titled "Spatial Correlation for Geometry-based SCME UMi". Both graphs plot the magnitude of correlation, "|Corr|", on the y-axis (ranging from 0 to 1) against "Antenna Spacing in  $\lambda$ " on the x-axis (ranging from 0 to 1). Each graph contains two data series: "Measured Correlation" (represented by a blue line with circle markers) and "Ideal Correlation" (represented by a dashed grey line). In both cases, the correlation starts at 1.0 at 0 lambda and decreases as spacing increases. The measured correlation follows the ideal correlation very closely throughout the entire range.
+
+Two line graphs showing spatial correlation for Geometry-based SCME UMa and UMi for System 2 with CE2 for Band 7. The left graph is for UMa and the right is for UMi. Both plot |Corr| against antenna spacing in lambda, comparing measured and ideal correlation.
+
+Figure 8.4.4-5b: Spatial correlation measurements for the RTS method using geometric implementation of SCME UMa and UMi for System 2 with CE2 for Band 7
+
+### 8.4.5 Cross polarization
+
+The cross polarization properties of the SCME UMi channel models defined in clause 8.2 has been characterized according to clause 8.3.2.3. The measured results shown in Table 8.4.5-1a below are for Band 13, and Band 7.
+
+**Table 8.4.5-1: Void**
+
+**Table 8.4.5-1a: Summary of cross polarization verification results for Band 13, and Band 7 for the UMi channel model**
+
+|               | MPAC System 1, CE 1, Band 13 |           |           | MPAC System 1, CE 1, Band 7 |           |           |
+|---------------|------------------------------|-----------|-----------|-----------------------------|-----------|-----------|
+| Channel Model | Theory                       | V/H ratio | Deviation | Theory                      | V/H ratio | Deviation |
+| UMi           | 0.74                         | 1.07      | 0.33      | 0.74                        | 0.14      | 0.60      |
+|               | MPAC System 1, CE 2, Band 13 |           |           | MPAC System 1, CE 2, Band 7 |           |           |
+| Channel Model | Theory                       | V/H ratio | Deviation | Theory                      | V/H ratio | Deviation |
+| UMi           | 0.74                         | 0.77      | 0.03      | 0.74                        | 0.97      | 0.23      |
+|               | MPAC System 2, CE 1, Band 13 |           |           | MPAC System 2, CE 1, Band 7 |           |           |
+| Channel Model | Theory                       | V/H ratio | Deviation | Theory                      | V/H ratio | Deviation |
+| UMi           | 0.74                         | 0.47      | 0.27      | 0.74                        | 0.67      | 0.07      |
+
+The cross-polarization results for the RTS method using geometric implementation of SCME are shown in Table 8.4.5-2:
+
+**Table 8.4.5-2: Summary of cross polarization verification results with geometric implementation**
+
+| Channel model | Band | System/CE         | V/H ratio | Theory | Deviation |
+|---------------|------|-------------------|-----------|--------|-----------|
+| UMa MC        | 13   | System 1 with CE1 | 8.1       | 8.13   | 0.03      |
+| UMi MC        | 13   | System 1 with CE1 | 0.8       | 0.74   | 0.06      |
+| UMa           | 13   | System 2 with CE2 | 7.78      | 8.13   | -0.35     |
+| UMi           | 13   | System 2 with CE2 | 0.89      | 0.74   | 0.15      |
+| UMa           | 7    | System 2 with CE2 | 7.75      | 8.13   | -0.38     |
+| UMi           | 7    | System 2 with CE2 | 0.85      | 0.74   | 0.11      |
+
+The cross-polarization results for the RTS method using correlation implementation of SCME (Jake's Doppler spectrum) are shown in Table 8.4.5-3:
+
+**Table 8.4.5-3: Summary of cross polarization verification results with correlation implementation (Jake's Doppler spectrum)**
+
+| Channel model | Band | System/CE         | V/H ratio | Theory | Deviation |
+|---------------|------|-------------------|-----------|--------|-----------|
+| UMa           | 13   | System 1 with CE1 | 7.9       | 8.13   | -0.23     |
+| UMi           | 13   | System 1 with CE1 | 0.8       | 0.74   | 0.06      |
+| UMa           | 13   | System 2 with CE2 | 8.44      | 8.13   | 0.31      |
+| UMi           | 13   | System 2 with CE2 | 0.68      | 0.74   | -0.06     |
+| UMa           | 7    | System 2 with CE2 | 8.34      | 8.13   | 0.21      |
+| UMi           | 7    | System 2 with CE2 | 0.80      | 0.74   | 0.06      |
+
+### 8.4.6 Summary
+
+The summary of the channel model validation activity is provided in Table 8.4.6-1 below.
+
+Table 8.4.6-1: Summary of channel model validation results
+
+| Item                                                                                                                                                                             | Parameter                      | Result    | Tolerances | Comments |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|-----------|------------|----------|
+| 1                                                                                                                                                                                | Power delay profile            | See 8.4.2 | FFS (Note) |          |
+| 2                                                                                                                                                                                | Doppler / Temporal Correlation | See 8.4.3 | FFS (Note) |          |
+| 3                                                                                                                                                                                | Spatial Correlation            | See 8.4.4 | FFS (Note) |          |
+| 4                                                                                                                                                                                | Cross Polarization             | See 8.4.5 | FFS (Note) |          |
+| NOTE: Further investigation of channel model validation metrics and their corresponding tolerances is ongoing within the framework of measurement uncertainty budget development |                                |           |            |          |
+
+## 8.5 Channel Model emulation of the Base Station antenna pattern configuration
+
+Editor's Note: To include the agreed X-polarized method. Any additional approach would need to be clearly specified.
+
+The emulated BS antennas to be used for all emulation of the channel models defined in subclause 8.2 shall be assumed to be dual polarized equal power elements with a fixed  $0\lambda$  separation, 45 degrees slanted.
+
+The slant 45 degree antenna is an "X" configuration and is modelled as an ideal dipole with isotropic gain and subject to a foreshortening of the slanted radiating element, which is observed to vary as a function of the path angle of departure. This foreshortening with AoD is a typical slanted dipole behaviour and is a source of power variation in the channel model. The effective antenna pattern for this antenna is illustrated in Figure 8.5-1.
+
+![Figure 8.5-1: X antenna gain assumption. (a) Linear gain plot showing Gain Linear vs Azimuth Angle in deg. (b) dB gain plot showing Gain in dB vs Azimuth Angle in deg. Both plots show four curves: V1 (solid red), H1 (solid green), V2 (dashed blue), and H2 (dashed black).](9bdb8898200f6a82bca1c1e6ff4621b9_img.jpg)
+
+Figure 8.5-1 consists of two plots, (a) and (b), showing the gain assumption for an X antenna configuration. Both plots have 'Azimuth Angle in deg' on the x-axis, ranging from -200 to 200. Plot (a) shows 'Gain Linear' on the y-axis, ranging from -1 to 1. Plot (b) shows 'Gain in dB' on the y-axis, ranging from -50 to 0. Both plots display four curves: V1 (solid red line), H1 (solid green line), V2 (dashed blue line), and H2 (dashed black line). In both plots, V1 and V2 are horizontal lines at a gain of 1 (0 dB). H1 and H2 show periodic variations. In (a), H1 (green) has peaks at 0, 180, and -180 degrees, and H2 (black) has peaks at 90 and 270 degrees. In (b), H1 (green) has deep nulls at 90 and 270 degrees, and H2 (black) has deep nulls at 0, 180, and -180 degrees. Callouts in (b) indicate specific points: X: 45, Y: -6.021 for H1 and X: 45, Y: -3.01 for H2.
+
+Figure 8.5-1: X antenna gain assumption. (a) Linear gain plot showing Gain Linear vs Azimuth Angle in deg. (b) dB gain plot showing Gain in dB vs Azimuth Angle in deg. Both plots show four curves: V1 (solid red), H1 (solid green), V2 (dashed blue), and H2 (dashed black).
+
+Figure 8.5-1: X antenna gain assumption (a) Linear gain (b) dB gain
+
+# 9 Reference antennas and devices testing
+
+## 9.1 Reference antennas design
+
+Editor's Note: Text to be added
+
+## 9.2 Reference devices
+
+## 9.3 Description of tests with reference antennas and devices
+
+### 9.3.1 The Absolute Data Throughput Comparison Framework
+
+#### 9.3.1.1 Introduction
+
+In an effort to compare different MIMO OTA methodologies' results to conducted results under the implementations of channel models defined in clause 8.2, the absolute data throughput comparison framework has been defined.
+
+By utilizing the reference antennas (clause 9.1) and reference devices (clause 9.2), this framework shall be used to compare each MIMO OTA testing method's ability to emulate the specified network and channel propagation characteristics based on an absolute data throughput metric.
+
+The framework consists of a set of conducted (Figure 9.3.1.1-1) and radiated (Figure 9.3.1.1-2) measurements of MIMO throughput (clause 5.1.1). The details for the application of this framework are described in clause 9.3.1.6.
+
+![Figure 9.3.1.1-1: Method of measuring the conducted absolute throughput reference performance. The diagram shows a flow from two 'Specify:' boxes to an 'eNB emulator', then to a 'Fading emulator', and finally to an 'LTE UE'. The first 'Specify:' box contains 'DL pwr level', 'RMC', 'MCS', and 'etc.'. The second 'Specify:' box contains 'Channel Model', 'Set of drops', 'Fading level', and 'etc.'. A box below the 'Fading emulator' contains 'Apply spatial filter corresponding to set of Reference Antennas (convolve with channel)'. An arrow points from the 'Fading emulator' to the 'LTE UE' with the text 'Conducted connection to an LTE UE'.](67c232883c119b120d2fb337bf588e05_img.jpg)
+
+```
+
+graph LR
+    S1[Specify:  
+DL pwr level  
+RMC  
+MCS  
+etc.] --> eNB[eNB emulator]
+    S2[Specify:  
+Channel Model  
+Set of drops  
+Fading level  
+etc.] --> FE[Fading emulator]
+    eNB --> FE
+    FE --> UE[LTE UE]
+    SF[Apply spatial filter  
+corresponding to set of  
+Reference Antennas  
+(convolve with channel)] --> FE
+    FE -- "Conducted connection to an LTE UE" --> UE
+  
+```
+
+Figure 9.3.1.1-1: Method of measuring the conducted absolute throughput reference performance. The diagram shows a flow from two 'Specify:' boxes to an 'eNB emulator', then to a 'Fading emulator', and finally to an 'LTE UE'. The first 'Specify:' box contains 'DL pwr level', 'RMC', 'MCS', and 'etc.'. The second 'Specify:' box contains 'Channel Model', 'Set of drops', 'Fading level', and 'etc.'. A box below the 'Fading emulator' contains 'Apply spatial filter corresponding to set of Reference Antennas (convolve with channel)'. An arrow points from the 'Fading emulator' to the 'LTE UE' with the text 'Conducted connection to an LTE UE'.
+
+Figure 9.3.1.1-1: Method of measuring the conducted absolute throughput reference performance
+
+![Figure 9.3.1.1-2: Method of measuring the absolute radiated data throughput metric with the reference antennas. The diagram shows a flow from two 'Specify:' boxes to an 'eNB emulator', then to a 'Fading emulator', and finally to a 'Test Methodology Environment'. The first 'Specify:' box contains 'DL pwr level', 'RMC', 'MCS', and 'etc.'. The second 'Specify:' box contains 'Channel Model', 'Set of drops', 'Fading level', and 'etc.'. The 'Test Methodology Environment' box contains a 'Ref Antenna Fixture' box, which in turn contains an 'LTE UE' box. An arrow points from the 'Fading emulator' to the 'Test Methodology Environment' with the text 'Connection between fading emulator and test environment varies by methodology'.](99781d878388c3e0f359b1d6ce14119c_img.jpg)
+
+```
+
+graph LR
+    S1[Specify:  
+DL pwr level  
+RMC  
+MCS  
+etc.] --> eNB[eNB emulator]
+    S2[Specify:  
+Channel Model  
+Set of drops  
+Fading level  
+etc.] --> FE[Fading emulator]
+    eNB --> FE
+    FE -- "Connection between fading emulator and test environment varies by methodology" --> TME[Test Methodology Environment]
+    subgraph TME [Test Methodology Environment]
+        RAF[Ref Antenna Fixture] --> UE[LTE UE]
+    end
+  
+```
+
+Figure 9.3.1.1-2: Method of measuring the absolute radiated data throughput metric with the reference antennas. The diagram shows a flow from two 'Specify:' boxes to an 'eNB emulator', then to a 'Fading emulator', and finally to a 'Test Methodology Environment'. The first 'Specify:' box contains 'DL pwr level', 'RMC', 'MCS', and 'etc.'. The second 'Specify:' box contains 'Channel Model', 'Set of drops', 'Fading level', and 'etc.'. The 'Test Methodology Environment' box contains a 'Ref Antenna Fixture' box, which in turn contains an 'LTE UE' box. An arrow points from the 'Fading emulator' to the 'Test Methodology Environment' with the text 'Connection between fading emulator and test environment varies by methodology'.
+
+Figure 9.3.1.1-2: Method of measuring the absolute radiated data throughput metric with the reference antennas
+
+The following subclauses define the antenna pattern data format, emulation of antenna pattern rotation, absolute data throughput measurement enabler, and the output data format.
+
+#### 9.3.1.2 Antenna pattern data format
+
+The antenna pattern data format—used in the conducted portion of the measurements — shall be in the 3D AAU format as defined by COST IC1004 [14]. Table 9.3.1.2-1 and 9.3.1.2-2 below illustrates the header structure with a sample data set respectively.
+
+**Table 9.3.1.2-1: Auxiliary informational header**
+
+| Line(s)                                                                                            | Pos.                                                                                        | Description                                               | Values - <i>examples</i> or <b>defaults</b> |
+|----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------------|
+| 1                                                                                                  | 1                                                                                           | Pattern frequency                                         | free (750)                                  |
+|                                                                                                    | 2                                                                                           | Frequency units                                           | {Hz,KHz, <b>MHz</b> ,GHz}                   |
+|                                                                                                    | 3                                                                                           | Port index (to resolve antennas automatically)            | free (1)                                    |
+|                                                                                                    | 4                                                                                           | Pattern type (Directivity, Gain, Realized Gain, E-field)  | {D,G,Gr,E} - possible more                  |
+|                                                                                                    | 5                                                                                           | Units format (as in touchstone plus the E-field format)   | {DB,MA, <b>RI,V/m</b> }                     |
+| NOTE: There is no freedom in the column arrangement but the labels can vary. Done for ease of use. |                                                                                             |                                                           |                                             |
+| 2                                                                                                  | 1                                                                                           | $\theta$ scan stepping - must be constant                 | Theta [deg]                                 |
+|                                                                                                    | 2                                                                                           | $\phi$ scan stepping - must be constant                   | Phi [deg]                                   |
+|                                                                                                    | 3                                                                                           | Absolute of the field X(1-4) in [units(1-5)]              | Abs X [units]                               |
+|                                                                                                    | 4                                                                                           | $\theta$ polarized field X(1-4) in [units(1-5)]           | XTh [units]                                 |
+|                                                                                                    | 5                                                                                           | phase of the $\theta$ polarized field - always in degrees | phase Th [deg]                              |
+|                                                                                                    | 6                                                                                           | $\phi$ polarized field X(1-4) in [units(1-5)]             | XPh [units]                                 |
+|                                                                                                    | 7                                                                                           | phase of the $\phi$ polarized field - always in degrees   | phase Ph [deg]                              |
+| 3,4 ...                                                                                            | NOTE: Any number additional lines can be added, always beginning with Matlab comment sign % |                                                           |                                             |
+|                                                                                                    | N/A                                                                                         | Some custom comment, ID etc.                              | % File version 1.0                          |
+
+Note: A semicolon should be used as a delimiter in the header.
+
+**Table 9.3.1.2-2: 3D AAU file format example**
+
+| 750; MHz; 1; G; DB                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |               |                |                |                |                |                |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|----------------|----------------|----------------|----------------|----------------|
+| Theta [deg]                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Phi [deg]     | Abs G [dB]     | GTh [dB]       | phase Th [deg] | GPh [dB]       | phase Ph [deg] |
+| File version 1.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |               |                |                |                |                |                |
+| 0.0000000e+00                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -7.1488243e+00 | -8.8275753e+00 | 2.9473810e+02  | -1.2089176e+01 | 2.9741836e+02  |
+| 5.0000000e+00                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -5.9290614e+00 | -6.9276561e+00 | 2.8631853e+02  | -1.2802746e+01 | 2.9300649e+02  |
+| 1.0000000e+01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -4.6884986e+00 | -5.2974347e+00 | 2.8098081e+02  | -1.3521536e+01 | 2.8790096e+02  |
+| 1.5000000e+01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -3.5323323e+00 | -3.9212541e+00 | 2.7745182e+02  | -1.4204563e+01 | 2.8204220e+02  |
+| 2.0000000e+01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -2.4979324e+00 | -2.7615381e+00 | 2.7503474e+02  | -1.4797363e+01 | 2.7547303e+02  |
+| 2.5000000e+01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | 0.0000000e+00 | -1.5926370e+00 | -1.7843443e+00 | 2.7333007e+02  | -1.5239593e+01 | 2.6841058e+02  |
+| ...                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | ...           | ...            | ...            | ...            | ...            | ...            |
+| In this table we further define the following parameters:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |               |                |                |                |                |                |
+| <ul style="list-style-type: none"> <li>• Position 1 on Line 1 shall indicate the measurement frequency.</li> <li>• Position 2 on Line 1 shall indicate the frequency units to be MHz.</li> <li>• Position 3 on Line 1 shall indicate the antenna index 1 or 2.</li> <li>• Antenna index is defined as: antenna index 1 defined as left antenna (portrait front view, from RF enclosure side).</li> <li>• Antenna index 2 defined as right antenna (portrait front view, from RF enclosure side).</li> <li>• Position 4 on Line 1 shall be G.</li> <li>• Position 5 on Line 1 shall be dBi.</li> <li>• Positions 3, 4, and 6 on Line 2 shall describe the measured gain in dBi.</li> </ul> |               |                |                |                |                |                |
+
+The file name format shall be defined as "(lab acronym)\_(antenna serial number)\_CTIA\_MIMO 2x2\_Band(B7, B13..Bxx)\_(Good, Nominal, or Bad)\_Ant(1 or 2).3daau".
+
+Based on experiments taken with low (<1GHz) and high (>1.8GHz) frequency band antennas, the magnitude of the complex correlation coefficient generated from measured data remains unchanged from higher resolution antenna pattern measurements up to 15 degrees resolution in theta and phi orientations. To align with current COST IC1004 TWGO MIMO OTA topic group proposed resolution for 3D MIMO OTA complex radiation pattern measurements, the antenna pattern measurement step size in theta and phi shall be no more than 5 degrees. In the specific case of 2D measurements theta is fixed at 90 degrees.
+
+#### 9.3.1.3 Emulation of antenna pattern rotation
+
+For the conducted portion of the absolute data throughput framework, it is necessary to generate the spatially filtered channel impulse response per polarization and then combine to generate the emulated channel impulse response coefficients. The measured antenna pattern shall be interpolated to match the spatial resolution of the angles of arrival of the SCME channel emulator (this value is typically 1 degrees). Figure 9.3.1.3-1 below illustrates an example of this procedure using a simplified antenna pattern and channel PAS.
+
+![Figure 9.3.1.3-1: Rotation of antenna pattern over azimuth positions. The figure shows two polar plots of antenna patterns. The left plot is labeled 'Rx1 PAS, Az Position 1, Vert pol' and the right plot is labeled 'Rx1 PAS, Az Position n, Vert pol'. Both plots show a yellow curve representing the antenna pattern. The left plot has an orange arrow pointing to the curve labeled 'vert/horz antenna pattern azimuth cut'. The right plot has an orange arrow pointing to the curve labeled 'antenna pattern rotated'. A purple arrow points from both plots to a box labeled 'emulated channel PAS'. The plots are separated by an ellipsis '...' in the center.](f78e0a777a9c5dc76cda197cbee0f206_img.jpg)
+
+The figure illustrates the rotation of an antenna pattern across different azimuth positions. It consists of two polar plots. The left plot, titled 'Rx1 PAS, Az Position 1, Vert pol', shows a yellow curve representing the antenna pattern. An orange arrow points to this curve with the label 'vert/horz antenna pattern azimuth cut'. The right plot, titled 'Rx1 PAS, Az Position n, Vert pol', shows the same yellow curve rotated. An orange arrow points to this curve with the label 'antenna pattern rotated'. A purple arrow points from both plots to a box labeled 'emulated channel PAS'. The plots are separated by an ellipsis '...' in the center.
+
+Figure 9.3.1.3-1: Rotation of antenna pattern over azimuth positions. The figure shows two polar plots of antenna patterns. The left plot is labeled 'Rx1 PAS, Az Position 1, Vert pol' and the right plot is labeled 'Rx1 PAS, Az Position n, Vert pol'. Both plots show a yellow curve representing the antenna pattern. The left plot has an orange arrow pointing to the curve labeled 'vert/horz antenna pattern azimuth cut'. The right plot has an orange arrow pointing to the curve labeled 'antenna pattern rotated'. A purple arrow points from both plots to a box labeled 'emulated channel PAS'. The plots are separated by an ellipsis '...' in the center.
+
+**Figure 9.3.1.3-1: Rotation of antenna pattern over azimuth positions**
+
+In general, the emulation of antenna pattern rotation is specific to the channel model. For 2D channel models antenna pattern rotation shall be performed over 360 degrees in 30 degree steps (12 total positions). For other channel models this process is FFS.
+
+A spatial filtering operation alone does not capture the behaviour of the 2D channel model as a function of DUT rotation. Figure 9.3.1.3-2 below illustrates the geometric parameters of the 2D channel model [15] for two DUT rotations.
+
+![Figure 9.3.1.3-2: (a) 2D channel model geometric parameters for MS array direction = 0 degrees; (b) MS array direction = 60 degrees. Both diagrams show a Base Station (BS) array and a Mobile Station (MS) array connected by a path through a cluster n and subpath m. The diagrams illustrate various geometric parameters including angles of arrival (AoA) and departure (AoD), cluster and subpath angles, and the MS direction of travel.](c07e21a8d65991db04263322f859c94f_img.jpg)
+
+Figure 9.3.1.3-2 consists of two diagrams, (a) and (b), illustrating the 2D channel model geometric parameters. Both diagrams show a Base Station (BS) array on the left and a Mobile Station (MS) array on the right, connected by a path through a cluster  $n$  and subpath  $m$ .
+
+Diagram (a) shows the MS array direction = 0 degrees. The BS array is at an angle  $\theta_{BS}$  relative to the horizontal. The cluster  $n$  is at an angle  $\theta_{n,m,AoD}$  from the BS array. The subpath  $m$  is at an angle  $\theta_{n,m,AoA}$  from the cluster  $n$ . The MS array is at an angle  $\theta_{MS} = \theta_{BS} + 0$  relative to the horizontal. The MS direction of travel is indicated by an orange arrow. The angle  $\theta_v = \theta_{BS} + 120 - \theta_{MS}$  is shown.
+
+Diagram (b) shows the MS array direction = 60 degrees. The BS array is at an angle  $\theta_{BS}$  relative to the horizontal. The cluster  $n$  is at an angle  $\theta_{n,m,AoD}$  from the BS array. The subpath  $m$  is at an angle  $\theta_{n,m,AoA}$  from the cluster  $n$ . The MS array is at an angle  $\theta_{MS} = \theta_{BS} + 60$  relative to the horizontal. The MS direction of travel is indicated by an orange arrow. The angle  $\theta_v = \theta_{BS} + 120 - \theta_{MS}$  is shown.
+
+Figure 9.3.1.3-2: (a) 2D channel model geometric parameters for MS array direction = 0 degrees; (b) MS array direction = 60 degrees. Both diagrams show a Base Station (BS) array and a Mobile Station (MS) array connected by a path through a cluster n and subpath m. The diagrams illustrate various geometric parameters including angles of arrival (AoA) and departure (AoD), cluster and subpath angles, and the MS direction of travel.
+
+**Figure 9.3.1.3-2: (a) 2D channel model geometric parameters for MS array direction = 0 degrees;  
+(b) MS array direction = 60 degrees**
+
+For a given rotation of the DUT, the angle of the MS array relative to the cluster angles of arrival changes. Thus, MS array rotation together with the spatial filtering operations described above is necessary to emulate the conducted portion of the framework properly. Doppler spread, which is a function of the MS direction of travel relative to the channel model clusters' angles of arrival, shall remain the same for all rotations of the DUT.
+
+Calculation of the required spatial filtering operations as a function of DUT orientation for channel emulators using a geometric implementation is self-evident from Figures 9.3.1.3-1 and 9.3.1.3-2. For channel emulators implementing the alternative correlation-based approach, the same spatial filtering operations are carried out by computing the correlation matrix and power imbalance for the specific channel model used and then applying the calculated correlation matrix and power in the channel emulation. The detail for how this is done is considered implementation specific and is not elaborated further here. It is noted that the correlation implementation results in a Doppler spectrum and corresponding temporal correlation that is independent of DUT orientation.
+
+This process may be automated with channel emulator control software or performed manually. The output data format is described in clause 9.3.1.5.
+
+#### 9.3.1.4 Absolute Data Throughput measurement enabler
+
+The fundamental enabler for the adoption of the Absolute Data Throughput metric is the ability to apply the complex radiation pattern to the channel for the conducted portion of the test. Such conducted measurements can be performed manually; however, without an application (SW) to rotate the loaded antenna complex radiation pattern, the measurement may become very time consuming and prone to human errors. Automation of this process is highly recommended.
+
+#### 9.3.1.5 Output data format
+
+A unified data format for recording the conducted and radiated test results by each lab is defined in Tables 9.3.1.5-1 and 9.3.1.5-2 below.
+
+**Table 9.3.1.5-1: Conducted measurement data table format**
+
+|                                                             |                                                                     |                             |                    |                      |
+|-------------------------------------------------------------|---------------------------------------------------------------------|-----------------------------|--------------------|----------------------|
+| <b>Absolute data throughput: conducted measurement data</b> |                                                                     |                             |                    |                      |
+| <b>ID</b>                                                   | <measurement ID>                                                    |                             |                    |                      |
+| <b>Lab info</b>                                             | <lab name, location, chamber ID>                                    |                             |                    |                      |
+| <b>Date</b>                                                 | <YYYY-MM-DD>                                                        |                             |                    |                      |
+| <b>eNodeB emulator</b>                                      | <manufacturer name, model number, serial number>                    |                             |                    |                      |
+| <b>eNodeB emulator version</b>                              | <hardware and firmware version numbers>                             |                             |                    |                      |
+| <b>eNodeB test application name and version</b>             | <test application name and version>                                 |                             |                    |                      |
+| <b>eNodeB ant config</b>                                    | Clause 8.5                                                          |                             |                    |                      |
+| <b>eNodeB PHY config</b>                                    | Clause 7.1                                                          |                             |                    |                      |
+| <b>Band</b>                                                 | <band num>                                                          |                             |                    |                      |
+| <b>DL channel</b>                                           | <channel num>                                                       |                             |                    |                      |
+| <b>UL channel</b>                                           | <channel num>                                                       |                             |                    |                      |
+| <b>RMC</b>                                                  | <R.11 or R.35>                                                      |                             |                    |                      |
+| <b>Transmission Mode</b>                                    | <TM2 or TM3>                                                        |                             |                    |                      |
+| <b>Num subframes per SIR pt</b>                             |                                                                     |                             |                    |                      |
+| <b>Channel emulator</b>                                     | <manufacturer name, model number, serial number>                    |                             |                    |                      |
+| <b>Channel emulator version</b>                             | <hardware and firmware version numbers>                             |                             |                    |                      |
+| <b>Channel model config</b>                                 | Clause 8.2                                                          |                             |                    |                      |
+| <b>Channel model</b>                                        | <UMi, UMa, etc>                                                     |                             |                    |                      |
+| <b>Emulated vehicular speed</b>                             | <speed in km/h>                                                     |                             |                    |                      |
+| <b>Reference antenna classification</b>                     | <good, nominal, or bad>                                             |                             |                    |                      |
+| <b>Ant1 pattern</b>                                         | <filename of reference antenna data as described in Clause 9.3.1.2> |                             |                    |                      |
+| <b>Ant2 pattern</b>                                         | <filename of reference antenna data as described in Clause 9.3.1.2> |                             |                    |                      |
+| <b>UE manufacturer</b>                                      | <manufacturer name>                                                 |                             |                    |                      |
+| <b>UE model</b>                                             | <model name>                                                        |                             |                    |                      |
+| <b>UE ID</b>                                                | <IMEI and possible additional unique ID number>                     |                             |                    |                      |
+| <b>Max theoretical throughput</b>                           | <kbps>                                                              |                             |                    |                      |
+| <b>Num theta positions</b>                                  | Clause 9.3.1.3                                                      |                             |                    |                      |
+| <b>Theta positions</b>                                      | Clause 9.3.1.3                                                      |                             |                    |                      |
+| <b>Num phi positions</b>                                    | Clause 9.3.1.3                                                      |                             |                    |                      |
+| <b>Phi positions</b>                                        | Clause 9.3.1.3                                                      |                             |                    |                      |
+| <b>Test plan name and version</b>                           |                                                                     |                             |                    |                      |
+| <b>Comments</b>                                             |                                                                     |                             |                    |                      |
+| <b>Test points per single position below</b>                | Skip if not applicable                                              |                             |                    |                      |
+| <b>Theta (deg)</b>                                          | <b>Phi (deg)</b>                                                    | <b>RS EPRE (dBm/15 kHz)</b> | <b>DL SIR (dB)</b> | <b>DL TPT (kbps)</b> |
+| <b>90</b>                                                   | <b>0</b>                                                            | <b>r_max</b>                | <b>s_max</b>       | <b>TPT_max</b>       |
+| ...                                                         | ...                                                                 | ...                         | ...                | ...                  |
+| <b>90</b>                                                   | <b>0</b>                                                            | <b>r_1</b>                  | <b>s_1</b>         | <b>TPT_1</b>         |
+| <b>90</b>                                                   | <b>0</b>                                                            | <b>r_2</b>                  | <b>s_2</b>         | <b>TPT_2</b>         |
+| ...                                                         | ...                                                                 | ...                         | ...                | ...                  |
+| <b>90</b>                                                   | <b>0</b>                                                            | <b>r_min</b>                | <b>s_min</b>       | <b>TPT_min</b>       |
+| <b>90</b>                                                   | <b>30</b>                                                           | <b>r_max</b>                | <b>s_max</b>       | <b>TPT_max</b>       |
+| ...                                                         | ...                                                                 | ...                         | ...                | ...                  |
+| <b>90</b>                                                   | <b>30</b>                                                           | <b>r_1</b>                  | <b>s_1</b>         | <b>TPT_1</b>         |
+
+|                                      |             |                         |          |         |
+|--------------------------------------|-------------|-------------------------|----------|---------|
+| <b>90</b>                            | 30          | r_2                     | s_2      | TPT_2   |
+| ...                                  | ...         | ...                     | ...      | ...     |
+| <b>90</b>                            | 30          | r_min                   | s_min    | TPT_min |
+| <b>Spatial average results below</b> |             |                         |          |         |
+| <b>RS EPRE (dBm/15 kHz)</b>          | DL SIR (dB) | AVG DL<br>TPT<br>(kbps) | Comments |         |
+| <b>r_max</b>                         | s_max       | TPT_max                 |          |         |
+| ...                                  | ...         | ...                     |          |         |
+| <b>r_1</b>                           | s_1         | TPT_1                   |          |         |
+| <b>r_2</b>                           | s_2         | TPT_2                   |          |         |
+| ...                                  | ...         | ...                     |          |         |
+| <b>r_min</b>                         | s_min       | TPT_min                 |          |         |
+
+**Table 9.3.1.5-2: Radiated measurement data table format**
+
+|                                                            |                                                  |                             |                    |                      |
+|------------------------------------------------------------|--------------------------------------------------|-----------------------------|--------------------|----------------------|
+| <b>Absolute data throughput: radiated measurement data</b> |                                                  |                             |                    |                      |
+| <b>ID</b>                                                  | <measurement ID>                                 |                             |                    |                      |
+| <b>Lab info</b>                                            | <lab name, location, chamber ID>                 |                             |                    |                      |
+| <b>Date</b>                                                | <YYYY-MM-DD>                                     |                             |                    |                      |
+| <b>Test methodology</b>                                    |                                                  |                             |                    |                      |
+| <b>eNodeB emulator</b>                                     | <manufacturer name, model number, serial number> |                             |                    |                      |
+| <b>eNodeB emulator version</b>                             | <hardware and firmware version numbers>          |                             |                    |                      |
+| <b>eNodeB test application name and version</b>            | <test application name and version>              |                             |                    |                      |
+| <b>eNodeB ant config</b>                                   | Clause 8.5                                       |                             |                    |                      |
+| <b>eNodeB PHY config</b>                                   | Clause 7.1                                       |                             |                    |                      |
+| <b>Band</b>                                                | <band num>                                       |                             |                    |                      |
+| <b>DL channel</b>                                          | <channel num>                                    |                             |                    |                      |
+| <b>UL channel</b>                                          | <channel num>                                    |                             |                    |                      |
+| <b>RMC</b>                                                 | <R.11 or R.35>                                   |                             |                    |                      |
+| <b>Transmission Mode</b>                                   | <TM2 or TM3>                                     |                             |                    |                      |
+| <b>Num subframes per SIR pt</b>                            |                                                  |                             |                    |                      |
+| <b>Channel emulator</b>                                    | <manufacturer name, model number, serial number> |                             |                    |                      |
+| <b>Channel emulator version</b>                            | <hardware and firmware version numbers>          |                             |                    |                      |
+| <b>Channel model config</b>                                | Clause 8.2                                       |                             |                    |                      |
+| <b>Channel model</b>                                       | <UMi, UMa, etc>                                  |                             |                    |                      |
+| <b>Emulated vehicular speed</b>                            | <speed in km/h>                                  |                             |                    |                      |
+| <b>Reference antenna classification and serial number</b>  | <(good, nominal, or bad)_SN>                     |                             |                    |                      |
+| <b>Ant 1</b>                                               | <Tx/Rx port of the UE>                           |                             |                    |                      |
+| <b>Ant 2</b>                                               | <Rx port of the UE>                              |                             |                    |                      |
+| <b>UE manufacturer</b>                                     | <manufacturer name>                              |                             |                    |                      |
+| <b>UE model</b>                                            | <model name>                                     |                             |                    |                      |
+| <b>UE ID</b>                                               | <IMEI and possible additional unique ID number>  |                             |                    |                      |
+| <b>Max theoretical throughput</b>                          | <kbps>                                           |                             |                    |                      |
+| <b>Num theta positions</b>                                 | <if applicable>                                  |                             |                    |                      |
+| <b>Theta positions</b>                                     | <if applicable>                                  |                             |                    |                      |
+| <b>Num phi positions</b>                                   | <if applicable>                                  |                             |                    |                      |
+| <b>Phi positions</b>                                       | <if applicable>                                  |                             |                    |                      |
+| <b>Configuration of testing antennas in chamber</b>        | <detailed description>                           |                             |                    |                      |
+| <b>Test plan name and version</b>                          |                                                  |                             |                    |                      |
+| <b>Comments</b>                                            |                                                  |                             |                    |                      |
+| <b>Test points per single position below</b>               | Skip if not applicable                           |                             |                    |                      |
+| <b>Theta (deg)</b>                                         | <b>Phi (deg)</b>                                 | <b>RS EPRE (dBm/15 kHz)</b> | <b>DL SIR (dB)</b> | <b>DL TPT (kbps)</b> |
+| 90                                                         | 0                                                | r_max                       | s_max              | TPT_max              |
+| ...                                                        | ...                                              | ...                         | ...                | ...                  |
+| 90                                                         | 0                                                | r_1                         | s_1                | TPT_1                |
+| 90                                                         | 0                                                | r_2                         | s_2                | TPT_2                |
+| ...                                                        | ...                                              | ...                         | ...                | ...                  |
+| 90                                                         | 0                                                | r_min                       | s_min              | TPT_min              |
+| 90                                                         | 30                                               | r_max                       | s_max              | TPT_max              |
+
+|                                      |             |                   |          |         |
+|--------------------------------------|-------------|-------------------|----------|---------|
+| ...                                  | ...         | ...               | ...      | ...     |
+| <b>90</b>                            | 30          | r_1               | s_1      | TPT_1   |
+| <b>90</b>                            | 30          | r_2               | s_2      | TPT_2   |
+| ...                                  | ...         | ...               | ...      | ...     |
+| <b>90</b>                            | 30          | r_min             | s_min    | TPT_min |
+| <b>Spatial average results below</b> |             |                   |          |         |
+| <b>RS EPRE (dBm/15 kHz)</b>          | DL SIR (dB) | AVG DL TPT (kbps) | Comments |         |
+| <b>r_max</b>                         | s_max       | TPT_max           |          |         |
+| ...                                  | ...         | ...               |          |         |
+| <b>r_1</b>                           | s_1         | TPT_1             |          |         |
+| <b>r_2</b>                           | s_2         | TPT_2             |          |         |
+| ...                                  | ...         | ...               |          |         |
+| <b>r_min</b>                         | s_min       | TPT_min           |          |         |
+
+#### 9.3.1.6 Application of the framework and scenarios for comparison
+
+This framework is methodology agnostic, and shall be used to compare each MIMO OTA testing method's ability to emulate the specified network and channel propagation characteristics based on an absolute data throughput metric (Clause 5.1.1).
+
+The purposes of this framework are:
+
+- For the agreed Channel Models, currently SCME Umi and Uma, to understand and quantify what are the deviations (if any) introduced by the chamber used in radiated mode compared to the conducted mode (when reference antennas are embedded). This shall be applied inter labs for the same method and inter methods.
+- For methods that are able to reproduce channel models that are not agreed in the present document, it can be used to define the channel model details that need to be injected in the conducted test to obtain same results in the radiated part. And therefore it is easier to reproduce those conditions across methods.
+
+The above use cases for the framework are required to be conducted for inter methodology comparison. Other applications for the framework are optional and not excluded.
+
+And more concretely, the following scenarios for comparison are defined:
+
+![Figure 9.3.1.6-1: Application of the framework and scenarios for comparison. The diagram shows three test scenarios: Anechoic, Reverb, and Reverb. Each scenario compares conducted and radiated test results for LTE UE throughput (Tput).](38d82ffe820e339811b396206f40a201_img.jpg)
+
+The diagram illustrates three test scenarios for comparing conducted and radiated test results for LTE UE throughput (Tput). Each scenario consists of two parallel test paths: Conducted and Radiated.
+
+- Anechoic Scenario:**
+  - Conducted:** eNB emulator → Fading emulator (Channel Model defined in TR) → LTE UE. Result: Tput\_CM\_Cond.
+  - Radiated:** eNB emulator → Fading emulator (Channel Model defined in TR) → Test methodology environment → LTE UE. Result: Tput\_AC.
+  - Comparison: Tput\_CM\_Cond = ? Tput\_AC
+- Reverb Scenario:**
+  - Conducted:** eNB emulator → Fading emulator (Channel Model defined in TR) → LTE UE. Result: Tput\_CM\_Cond.
+  - Radiated:** eNB emulator → Fading emulator (Channel Model defined in TR) → Test methodology environment → LTE UE. Result: Tput\_RC.
+  - Comparison: Tput\_CM\_Cond = ? Tput\_RC
+- Reverb Scenario (Modified):**
+  - Conducted:** eNB emulator → Fading emulator (CM in TR+reverb isotropy) → LTE UE. Result: Tput\_ModCM\_Cond.
+  - Radiated:** eNB emulator → Fading emulator (Channel Model defined in TR) → Test methodology environment → LTE UE. Result: Tput\_RC.
+  - Comparison: Tput\_ModCM\_Cond = ? Tput\_RC
+
+Figure 9.3.1.6-1: Application of the framework and scenarios for comparison. The diagram shows three test scenarios: Anechoic, Reverb, and Reverb. Each scenario compares conducted and radiated test results for LTE UE throughput (Tput).
+
+**Figure 9.3.1.6-1: Application of the framework and scenarios for comparison**
+
+These scenarios are intended to address the following aspects:
+
+- The first scenario**, anechoic based: intended to compare the conducted portion of the test (with embedded radiation pattern antennas) with the same results of the radiated test. Throughputs are compared to understand any artifacts introduced by the setup.
+- The second scenario**, reverberation based: intended to compare the conducted portion of the test (with embedded radiation pattern antennas) with the same results of the radiated test. Throughputs are compared to understand any artifacts introduced by the setup.
+- The third scenario**, reverberation based: intended to compare the conducted portion of the test (with embedded radiation pattern antennas) and with 3D isotropic channel model with the same results of the radiated test. Throughputs are compared to understand any artifacts introduced by the setup. Additionally this scenario will help to define the 3D isotropic properties of the channel model as perceived by the UE in the reverb chamber, and compare its realization in the conducted portion.
+
+**NOTE:** If scenario2 holds true, it would mean that for the agreed setup anechoic method and reverberation method provides comparable results for the agreed channel models in the present document, currently 2D SCME.
+
+#### 9.3.1.7 Proof of concept
+
+##### 9.3.1.7.1 The first scenario, anechoic based
+
+The implementation of the Absolute Data Throughput Framework based in the first scenario; i.e. anechoic chamber ring of probes; is defined in Clause 9.3.1.6 and table 9.3.1.7.1-1.
+
+Figure 9.3.1.7.1-2 indicates variation equal or less than 0.5dB when comparing OTA measurements with correspondent conducted measurements, therefore validating the framework concept.
+
+**Table 9.3.1.7.1-1: Absolute Data Throughput proof of concept measurement setup**
+
+| Anechoic based measurement setup | Conducted              | Radiated               |
+|----------------------------------|------------------------|------------------------|
+| Lab                              | Conducted lab "A"      | Radiated "B"           |
+| Methodology                      | Conducted              | Radiated               |
+| eNodeB emul.                     | model "A"              | model "A"              |
+| eNodeB ant config                | Clause 7.2             | Clause 7.2             |
+| eNodeB PHY config                | Clause 7.1             | Clause 7.1             |
+| Band                             | 13                     | 13                     |
+| DL channel                       | 5230                   | 5230                   |
+| UL channel                       | 23230                  | 23230                  |
+| RMC                              | R11                    | R11                    |
+| Num subframes per SNR pt         | 20000                  | 20000                  |
+| Channel emul.                    | model "B1"             | model "B2"             |
+| Channel model config             | Clause 8.2             | Clause 8.2             |
+| Channel model                    | SCME Umi, SCME Uma     | SCME Umi, SCME Uma     |
+| Emul. veh. speed                 | 30 km/h                | 30 km/h                |
+| UE mfg                           | Commercially available | Commercially available |
+| Transmission Mode                | TM3                    | TM3                    |
+
+![Figure 9.3.1.7.1-1: First Scenario (anechoic based) proof of concept, measurement results. A line graph showing Data Throughput (Mbit/s) on the y-axis (0 to 25) versus RS EPRE (dBm/15KHz) on the x-axis (-117 to -87). The graph compares OTA and Conducted measurements for Good and Bad SCME UMi and Good SCME Uma channel models. The 'OTA (lab) Conducted unfaded' and 'Conducted (lab) unfaded' lines are flat at approximately 22.5 Mbit/s. The 'OTA Good SCME UMi' and 'Conducted Good SCME UMi' lines show a sharp increase in throughput starting around -112 dBm, reaching a plateau of about 22.5 Mbit/s by -107 dBm. The 'OTA Bad SCME UMi' and 'Conducted Bad SCME UMi' lines show a sharp increase starting around -107 dBm, reaching a plateau of about 22.5 Mbit/s by -102 dBm. The 'OTA Good SCME Uma' and 'Conducted Good SCME Uma' lines show a sharp increase starting around -102 dBm, reaching a plateau of about 22.5 Mbit/s by -97 dBm.](00c19bd8502c529040b374841106f2c3_img.jpg)
+
+Band 13, SCME Umi & SCME Uma, 16 QAM, abs TP Framework
+
+Figure 9.3.1.7.1-1: First Scenario (anechoic based) proof of concept, measurement results. A line graph showing Data Throughput (Mbit/s) on the y-axis (0 to 25) versus RS EPRE (dBm/15KHz) on the x-axis (-117 to -87). The graph compares OTA and Conducted measurements for Good and Bad SCME UMi and Good SCME Uma channel models. The 'OTA (lab) Conducted unfaded' and 'Conducted (lab) unfaded' lines are flat at approximately 22.5 Mbit/s. The 'OTA Good SCME UMi' and 'Conducted Good SCME UMi' lines show a sharp increase in throughput starting around -112 dBm, reaching a plateau of about 22.5 Mbit/s by -107 dBm. The 'OTA Bad SCME UMi' and 'Conducted Bad SCME UMi' lines show a sharp increase starting around -107 dBm, reaching a plateau of about 22.5 Mbit/s by -102 dBm. The 'OTA Good SCME Uma' and 'Conducted Good SCME Uma' lines show a sharp increase starting around -102 dBm, reaching a plateau of about 22.5 Mbit/s by -97 dBm.
+
+**Figure 9.3.1.7.1-1: First Scenario (anechoic based) proof of concept, measurement results**
+
+The implementation of the Absolute Data Throughput Framework based on the anechoic RTS method is defined in clause 9.3.1.6 and Table 9.3.1.7.1-2.
+
+Figure 9.3.1.7.1-2 indicates variation equal or less than 0.5dB when comparing OTA measurements with correspondent conducted measurements, therefore validating the framework concept.
+
+These results were generated using the correlation-based channel model implementation.
+
+**Table 9.3.1.7.1-2: Absolute Data Throughput proof of concept measurement setup**
+
+| RTS measurement setup    | Conducted          | Radiated           |
+|--------------------------|--------------------|--------------------|
+| Lab                      | Conducted lab "A"  | Radiated lab "B"   |
+| Methodology              | Conducted          | Radiated           |
+| eNodeB emul.             | Agilent PXT        | Agilent PXT        |
+| eNodeB ant config        | Clause 7.2         | Clause 7.2         |
+| eNodeB PHY config        | Clause 7.1         | Clause 7.1         |
+| Band                     | 13                 | 13                 |
+| DL channel               | 5230               | 5230               |
+| UL channel               | 23230              | 23230              |
+| RMC                      | R11                | R11                |
+| Num subframes per SNR pt | 20000              | 20000              |
+| Channel emul.            | Agilent PXB        | Agilent PXB        |
+| Channel model config     | Clause 8.2         | Clause 8.2         |
+| Channel model            | SCME Umi, SCME UMa | SCME Umi, SCME UMa |
+| Emul. veh. speed         | 30 km/h            | 30 km/h            |
+| UE mfg                   | HTC ADR6425LVW     | HTC ADR6425LVW     |
+| Transmission Mode        | TM3                | TM3                |
+
+![Figure 9.3.1.7.1-3: Radiated vs Cable-conducted Absolute Throughput Test for Umi MC Model using correlation-based channel model. The graph plots Throughput (Mbps) on the y-axis (ranging from 15 to 36) against RS_EPRE (dBm/15kHz) on the x-axis (ranging from -115 to -70). Seven data series are shown: Umi MC, good (green triangles), Umi MC, nominal (purple crosses), Umi MC, bad (blue asterisks), OTA, Umi MC, good (red squares), OTA, Umi MC, bad 2nd (light blue pluses), OTA, Umi MC, bad 1st (pink pluses), and OTA, Umi MC, nominal (orange circles). The curves show that throughput increases with RS_EPRE and is highest for the 'good' channel model and lowest for the 'bad' channel model. The OTA results closely match the corresponding Umi MC results.](117f43cb271793ec681551c4fdd92cf0_img.jpg)
+
+Figure 9.3.1.7.1-3: Radiated vs Cable-conducted Absolute Throughput Test for Umi MC Model using correlation-based channel model. The graph plots Throughput (Mbps) on the y-axis (ranging from 15 to 36) against RS\_EPRE (dBm/15kHz) on the x-axis (ranging from -115 to -70). Seven data series are shown: Umi MC, good (green triangles), Umi MC, nominal (purple crosses), Umi MC, bad (blue asterisks), OTA, Umi MC, good (red squares), OTA, Umi MC, bad 2nd (light blue pluses), OTA, Umi MC, bad 1st (pink pluses), and OTA, Umi MC, nominal (orange circles). The curves show that throughput increases with RS\_EPRE and is highest for the 'good' channel model and lowest for the 'bad' channel model. The OTA results closely match the corresponding Umi MC results.
+
+**Figure 9.3.1.7.1-3: Radiated vs Cable-conducted Absolute Throughput Test for Umi MC Model using correlation-based channel model**
+
+![Figure 9.3.1.7.1-4: Radiated vs Cable-conducted Absolute Throughput Test for Uma MC Model using correlation-based channel model. The graph plots Throughput (Mbps) on the y-axis (15 to 36) against RS_EPRE (dBm/15kHz) on the x-axis (-115 to -70). Six curves are shown: Uma MC/B, good (blue crosses); Uma MC/B, nominal (red crosses); Uma MC/B, bad (green circles); OTA, Uma MC/B, good (blue diamonds); OTA, Uma MC/B, nominal (red squares); and OTA, Uma MC/B, bad (green triangles). The curves show that throughput increases with RS_EPRE and is higher for 'good' channel conditions compared to 'bad' conditions. The OTA and MC/B results are closely aligned for each channel condition.](578d2763eaf3edf3f1bd6657455ad54a_img.jpg)
+
+Figure 9.3.1.7.1-4: Radiated vs Cable-conducted Absolute Throughput Test for Uma MC Model using correlation-based channel model. The graph plots Throughput (Mbps) on the y-axis (15 to 36) against RS\_EPRE (dBm/15kHz) on the x-axis (-115 to -70). Six curves are shown: Uma MC/B, good (blue crosses); Uma MC/B, nominal (red crosses); Uma MC/B, bad (green circles); OTA, Uma MC/B, good (blue diamonds); OTA, Uma MC/B, nominal (red squares); and OTA, Uma MC/B, bad (green triangles). The curves show that throughput increases with RS\_EPRE and is higher for 'good' channel conditions compared to 'bad' conditions. The OTA and MC/B results are closely aligned for each channel condition.
+
+**Figure 9.3.1.7.1-4: Radiated vs Cable-conducted Absolute Throughput Test for Uma MC Model using correlation-based channel model**
+
+##### 9.3.1.7.2 The second scenario, reverberation chamber based
+
+Figure 9.3.1.7.2-1 shows results from measurements using the absolute data throughput comparison framework for the reverberation chamber methodology, implementing the isotropic channel model based on NIST. The conducted and radiated results align within  $\pm 0.5$  dB (comparing the 70 % throughput level), therefore validating the framework concept.
+
+Details about the measurement setup are given in Table 9.3.1.7.2-1.
+
+**Table 9.3.1.7.2-1: Measurement setup for the reverberation chamber methodology**
+
+| Reverberation chamber based measurement setup | Conducted              | Radiated               |
+|-----------------------------------------------|------------------------|------------------------|
+| Lab                                           | A                      | A                      |
+| Methodology                                   | Conducted              | Radiated               |
+| eNodeB emul.                                  | model "A.1"            | model "A.1"            |
+| eNodeB ant config                             | Uncorrelated           | Uncorrelated           |
+| eNodeB PHY config                             | Clause 7.1             | Clause 7.1             |
+| Band                                          | 13                     | 13                     |
+| DL channel                                    | 5230                   | 5230                   |
+| UL channel                                    | 23230                  | 23230                  |
+| RMC                                           | R35                    | R,35                   |
+| Num subframes per power level                 | 96000                  | 96000                  |
+| Channel emul.                                 | model "A.2"            | N/A                    |
+| Channel model config                          | Annex C.2              | Annex C.2              |
+| Channel model                                 | Isotropic NIST         | Isotropic NIST         |
+| Emul. veh. speed                              | 1 km/h                 | N/A                    |
+| UE mfg                                        | Commercially available | Commercially available |
+| Transmission Mode                             | TM3                    | TM3                    |
+
+![Figure 9.3.1.7.2-1: A line graph showing Throughput [kbps] on the y-axis (ranging from 24,000 to 36,000) versus Power [dBm/15kHz] on the x-axis (ranging from -109 to -90). The graph compares six scenarios: Good (green squares), Nominal (blue squares), Bad (red squares), Cond - Good (green line), Cond - Nominal (blue line), and Cond - Bad (red line). The 'Good' scenario shows the highest throughput, reaching approximately 35,500 kbps at -100 dBm. The 'Bad' scenario shows the lowest throughput, reaching approximately 35,500 kbps at -92 dBm. The 'Cond' scenarios show intermediate performance between 'Good' and 'Bad'.](d989d8766a23d5e409031f1ceae6572b_img.jpg)
+
+Figure 9.3.1.7.2-1: A line graph showing Throughput [kbps] on the y-axis (ranging from 24,000 to 36,000) versus Power [dBm/15kHz] on the x-axis (ranging from -109 to -90). The graph compares six scenarios: Good (green squares), Nominal (blue squares), Bad (red squares), Cond - Good (green line), Cond - Nominal (blue line), and Cond - Bad (red line). The 'Good' scenario shows the highest throughput, reaching approximately 35,500 kbps at -100 dBm. The 'Bad' scenario shows the lowest throughput, reaching approximately 35,500 kbps at -92 dBm. The 'Cond' scenarios show intermediate performance between 'Good' and 'Bad'.
+
+**Figure 9.3.1.7.2-1: Proof of concept for the reverberation chamber methodology, implementing the isotropic channel model based on NIST**
+
+##### 9.3.1.7.3 The third scenario, reverberation chamber and channel emulator based
+
+Figure 9.3.1.7.3-1 and Figure 9.3.1.7.3-2 show results from measurements using the absolute data throughput comparison framework for the reverberation chamber and channel emulator methodology, implementing the short delay spread low correlation and the long delay spread high correlation channel model. The conducted and radiated results align within  $\pm 1$  dB (comparing the 70 % throughput level), therefore validating the framework concept.
+
+Details about the measurement setups are given in Table 9.3.1.7.3-1 and Table 9.3.1.7.3-2.
+
+**Table 9.3.1.7.3-1: Measurement setup for the reverberation chamber and channel emulator methodology**
+
+| Reverberation chamber based measurement setup | Conducted                                    | Radiated                                     |
+|-----------------------------------------------|----------------------------------------------|----------------------------------------------|
+| Lab                                           | A                                            | A                                            |
+| Methodology                                   | Conducted                                    | Radiated                                     |
+| eNodeB emul.                                  | model A.1                                    | model A.1                                    |
+| eNodeB ant config                             | Clause 8.5                                   | Clause 8.5                                   |
+| eNodeB PHY config                             | Clause 7.1                                   | Clause 7.1                                   |
+| Band                                          | 13                                           | 13                                           |
+| DL channel                                    | 5230                                         | 5230                                         |
+| UL channel                                    | 23230                                        | 23230                                        |
+| RMC                                           | R35                                          | R,35                                         |
+| Num subframes per power level                 | 96000                                        | 96000                                        |
+| Channel emul.                                 | model A.2                                    | model A.2                                    |
+| Channel model config                          | Annex C.2                                    | Annex C.2                                    |
+| Channel model                                 | Isotropic short delay spread low correlation | Isotropic short delay spread low correlation |
+| Emul. veh. speed                              | 30 km/h                                      | 30 km/h                                      |
+| UE mfg                                        | Commercially available                       | Commercially available                       |
+| Transmission Mode                             | TM3                                          | TM3                                          |
+
+![Figure 9.3.1.7.3-1: A line graph showing Throughput [kbps] on the Y-axis (ranging from 24,000 to 36,000) versus Power [dBm/15kHz] on the X-axis (ranging from -114 to -85). The graph displays six curves representing different channel conditions and measurement methods: Conducted - Good (green line with squares), OTA - Good (green line with squares), Conducted - Nominal (blue line with squares), OTA - Nominal (blue line with squares), Conducted - Bad (red line with squares), and OTA - Bad (red line with squares). The 'Good' condition curves show the highest throughput, followed by 'Nominal', and then 'Bad'. Conducted results generally show higher throughput than OTA results for the same channel condition.](bb908297bfe73e2759a9dd88ae0506f9_img.jpg)
+
+Figure 9.3.1.7.3-1: A line graph showing Throughput [kbps] on the Y-axis (ranging from 24,000 to 36,000) versus Power [dBm/15kHz] on the X-axis (ranging from -114 to -85). The graph displays six curves representing different channel conditions and measurement methods: Conducted - Good (green line with squares), OTA - Good (green line with squares), Conducted - Nominal (blue line with squares), OTA - Nominal (blue line with squares), Conducted - Bad (red line with squares), and OTA - Bad (red line with squares). The 'Good' condition curves show the highest throughput, followed by 'Nominal', and then 'Bad'. Conducted results generally show higher throughput than OTA results for the same channel condition.
+
+Figure 9.3.1.7.3-1: Proof of concept for the reverberation chamber and channel emulator methodology emulating the short delay spread low correlation channel model
+
+Table 9.3.1.7.3-2: Measurement setup for the reverberation chamber and channel emulator methodology
+
+| Reverberation chamber based measurement setup | Conducted                                    | Radiated                                     |
+|-----------------------------------------------|----------------------------------------------|----------------------------------------------|
+| Lab                                           | A                                            | A                                            |
+| Methodology                                   | Conducted                                    | Radiated                                     |
+| eNodeB emul.                                  | model A.3                                    | model A.3                                    |
+| eNodeB ant config                             | Clause 8.5                                   | Clause 8.5                                   |
+| eNodeB PHY config                             | Clause 7.1                                   | Clause 7.1                                   |
+| Band                                          | 13                                           | 13                                           |
+| DL channel                                    | 5230                                         | 5230                                         |
+| UL channel                                    | 23230                                        | 23230                                        |
+| RMC                                           | R35                                          | R,35                                         |
+| Num subframes per power level                 | 96000                                        | 96000                                        |
+| Channel emul.                                 | model A.4                                    | model A.4                                    |
+| Channel model config                          | Annex C.2                                    | Annex C.2                                    |
+| Channel model                                 | Isotropic long delay spread high correlation | Isotropic long delay spread high correlation |
+| Emul. veh. speed                              | 30 km/h                                      | 30 km/h                                      |
+| UE mfg                                        | Commercially available                       | Commercially available                       |
+| Transmission Mode                             | TM3                                          | TM3                                          |
+
+![Figure 9.3.1.7.3-2: A line graph showing Throughput [Kbps] on the Y-axis (ranging from 24000 to 36000) versus Power [dBm/15kHz] on the X-axis (ranging from -105 to -82). The graph compares six channel conditions: Good - Cond (solid green line), Good - OTA (green line with circles), Nominal - Cond (solid blue line), Nominal - OTA (blue line with circles), Bad - Cond (solid red line), and Bad - OTA (red line with circles). The 'Good' conditions show the highest throughput, followed by 'Nominal', and then 'Bad'. The 'Cond' (conducted) curves generally show higher throughput than their corresponding 'OTA' (over-the-air) curves for the same power level.](2333c01db80c100fb3f8467a0717d99d_img.jpg)
+
+Figure 9.3.1.7.3-2: A line graph showing Throughput [Kbps] on the Y-axis (ranging from 24000 to 36000) versus Power [dBm/15kHz] on the X-axis (ranging from -105 to -82). The graph compares six channel conditions: Good - Cond (solid green line), Good - OTA (green line with circles), Nominal - Cond (solid blue line), Nominal - OTA (blue line with circles), Bad - Cond (solid red line), and Bad - OTA (red line with circles). The 'Good' conditions show the highest throughput, followed by 'Nominal', and then 'Bad'. The 'Cond' (conducted) curves generally show higher throughput than their corresponding 'OTA' (over-the-air) curves for the same power level.
+
+**Figure 9.3.1.7.3-2: Proof of concept for the reverberation chamber and channel emulator methodology emulating the long delay spread high correlation channel model**
+
+## 9.4 Device positioning
+
+### 9.4.1 Handheld UE – Browsing mode
+
+Handheld UE is a device which is primarily used in a handgrip like normal mobile/smart phones when they are used for browsing.
+
+Browsing mode testing method is used for MIMO OTA performance measurements in case of handheld types of UE form factors as defined in 3GPP TR 25.914 [11] subclause 5.1.7.
+
+#### 9.4.1.1 MPAC Positioning Guidelines
+
+The MPAC positioning guidelines of the handheld UE in browsing mode in the MPAC system shall follow the requirements in Annex E.2.1.
+
+### 9.4.2 Handheld UE – Speech mode
+
+Handheld UE which supports VoLTE is primarily used in speech mode when doing a voice call.
+
+Speech mode is simulation of a voice call user case. DUT is placed in to a hand phantom which is holding the DUT against SAM head phantom. Speech mode testing is used for MIMO OTA performance measurements as defined in 3GPP TR 25.914 [11] subclause 5.1.6.
+
+#### 9.4.2.1 MPAC Positioning Guidelines
+
+The MPAC positioning guidelines of the handheld UE in speech mode in the MPAC system shall follow the requirements in Annex E.2.1.
+
+### 9.4.3 Laptop Mounted Equipment (LME)
+
+Laptop Mounted Equipment (LME) type UE is a plug-in device that hosts on the laptop (like USB dongles).
+
+A laptop ground plane phantom is used for radiated MIMO OTA performance measurements in case of LME plug-in DUT as defined in TR 25.914 [11] subclauses 5.1.3 and 5.1.4.
+
+#### 9.4.3.1 MPAC Positioning Guidelines
+
+The MPAC positioning guidelines of an LME DUT in the MPAC system shall follow the requirements in Annex E.2.1.
+
+### 9.4.4 Laptop Embedded Equipment (LEE)
+
+Laptop Embedded Equipment (LEE) are notebook PC's or tablets.
+
+A notebook PC is a portable personal computer combining the computer, keyboard and display in one form factor. Typically the keyboard is built into the base and the display is hinged along the back edge of the base. The largest single dimension for a notebook is limited to 0.42 m.
+
+As notebooks are not body worn equipment nor recommended for use placed directly on the lap, the notebook shall be tested in a free space configuration without head and hand phantoms.
+
+LEE Notebook PC's shall be tested in free space configuration as defined in TR 25.914 [11] subclause 5.3.1.
+
+Tablet positioning is FFS.
+
+#### 9.4.4.1 MPAC Positioning Guidelines
+
+The MPAC positioning guidelines of an LEE DUT in the MPAC system shall follow the requirements in Annex E.2.1.
+
+# --- 10 Measurement results from testing campaigns
+
+## 10.1 Introduction
+
+Subclause 10.2 contains measurement results that are considered valid for the devices with reference antennas, and test conditions used. These results represent the ability of the methodologies described hereafter to distinguish good from bad devices in terms of their MIMO OTA performance under the conditions described in clause 10.2.1.
+
+## 10.2 CTIA test campaign
+
+### 10.2.1 Description of the test plan
+
+This clause summarizes the test environment used within CTIA during execution of the "Phase 2" Inter Laboratory and Inter-Technique (IL/IT) comparison activity. The settings utilized during execution of this test activity have been summarized here according to the applicable clauses, tables and annexes of the present document.
+
+**Table 10.2.1-1: Summary of settings used in the test plan for IL/IT testing campaign**
+
+|                                                                           | Settings used in test plan                                                                                                                                                   | Observations                                                                   |
+|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
+| eNodeB                                                                    | Table 7.1-1                                                                                                                                                                  | Initial Downlink RS-EPRE of -85 dBm/15 kHz                                     |
+| Channel Models                                                            | Clause 8 and Annex C                                                                                                                                                         | Additional channel models were also included in the CTIA Phase 2 test campaign |
+| Channel Model emulation of the Base Station antenna pattern configuration | Clause 8.5                                                                                                                                                                   | None                                                                           |
+| Frequency bands                                                           | Band 7 and 13                                                                                                                                                                | Band 13 mandatory<br>Band 7 recommended                                        |
+| SIR                                                                       | Not used                                                                                                                                                                     | None                                                                           |
+| Transmission Mode                                                         | TM3 according to Table 7.1-1                                                                                                                                                 | None                                                                           |
+| Devices                                                                   | Clause 9.2                                                                                                                                                                   | None                                                                           |
+| Reference antennas                                                        | Clause 9.1                                                                                                                                                                   | None                                                                           |
+| Measurements performed                                                    | Absolute throughput performance in conducted and radiated modes<br>Channel model verification (Clause 8 and Annex C)<br>Absolute data throughput verification (Clause 9.3.1) | None                                                                           |
+
+### 10.2.2 Anechoic chamber method with multiprobe configuration
+
+Inter-Lab/Inter-Technique (IL/IT) campaigns have been performed in CTIA MOSG LTE MIMO OTA by the Anechoic Chamber test methodology. The results are produced here in Figures 10.2.2-1 to 10.2.2-9.
+
+![Figure 10.2.2-1: Absolute data throughput framework results for the SCME UMi Channel model for SATIMO. The graph plots Throughput [bps] on the y-axis (ranging from 5000 to 37000) against Power [dBm/15KHz] on the x-axis (ranging from -110 to -82). Six data series are shown: UMi Good Ant config - OTA (blue line with circles), UMi Nominal Ant Config - OTA (red line with squares), UMi Good Ant config - Conducted (purple line with crosses), UMi Nominal Ant Config - Conducted (cyan line with diamonds), UMi Bad Ant Config - OTA (green line with triangles), and UMi Bad Ant Config - Conducted (orange line with diamonds). The 'Conducted' results show higher throughput at lower power levels compared to 'OTA' results for the same antenna configuration. The 'Good Ant config' achieves the highest throughput, followed by 'Nominal' and then 'Bad Ant Config'.](a0b992c3c544896bb2567bf22e532bd1_img.jpg)
+
+Figure 10.2.2-1: Absolute data throughput framework results for the SCME UMi Channel model for SATIMO. The graph plots Throughput [bps] on the y-axis (ranging from 5000 to 37000) against Power [dBm/15KHz] on the x-axis (ranging from -110 to -82). Six data series are shown: UMi Good Ant config - OTA (blue line with circles), UMi Nominal Ant Config - OTA (red line with squares), UMi Good Ant config - Conducted (purple line with crosses), UMi Nominal Ant Config - Conducted (cyan line with diamonds), UMi Bad Ant Config - OTA (green line with triangles), and UMi Bad Ant Config - Conducted (orange line with diamonds). The 'Conducted' results show higher throughput at lower power levels compared to 'OTA' results for the same antenna configuration. The 'Good Ant config' achieves the highest throughput, followed by 'Nominal' and then 'Bad Ant Config'.
+
+**Figure 10.2.2-1: Absolute data throughput framework results for the SCME UMi Channel model for SATIMO**
+
+![Figure 10.2.2-2: Absolute data throughput framework results for the SCME UMa-B Channel model for SATIMO. The graph plots Throughput [Kbps] on the y-axis (5000 to 37000) against Power [dBm/15KHz] on the x-axis (-104 to -74). Six curves are shown: UMa B case Good Ant Config - OTA (blue line with circles), UMa B case Nominal Ant Config - OTA (red line with squares), UMa B case Bad Ant Config - OTA (green line with triangles), UMa B case Good Ant Config - Conducted (orange line with circles), UMa B case Bad Ant Config - Conducted (light blue line with circles), and UMa B case Nominal Ant Config - Conducted (purple line with squares). The conducted results generally show higher throughput than the OTA results for the same antenna configuration.](7498bf530d9e13633524982a399d4439_img.jpg)
+
+Figure 10.2.2-2: Absolute data throughput framework results for the SCME UMa-B Channel model for SATIMO. The graph plots Throughput [Kbps] on the y-axis (5000 to 37000) against Power [dBm/15KHz] on the x-axis (-104 to -74). Six curves are shown: UMa B case Good Ant Config - OTA (blue line with circles), UMa B case Nominal Ant Config - OTA (red line with squares), UMa B case Bad Ant Config - OTA (green line with triangles), UMa B case Good Ant Config - Conducted (orange line with circles), UMa B case Bad Ant Config - Conducted (light blue line with circles), and UMa B case Nominal Ant Config - Conducted (purple line with squares). The conducted results generally show higher throughput than the OTA results for the same antenna configuration.
+
+**Figure 10.2.2-2: Absolute data throughput framework results for the SCME UMa-B Channel model for SATIMO**
+
+Further, from Figure 10.2.2-2, it can be noted that the max deviation between the absolute data throughput and OTA measurements is around 1.5dB at 70% throughput. This can be observed for the Good antenna system and SCME UMi case with the absolute data throughput outperforming the OTA measurements. There is also a deviation of around 1dB for the following case - SCME UMi with Nominal antenna and SCME UMa B case with Good antenna. Very little deviation is noted for the Bad antenna and both SCME UMi, and UMa B case.
+
+![Figure 10.2.2-3: Absolute data throughput framework results for the SCME UMi Channel model for Intel. The graph plots Throughput [kbps] on the y-axis (2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (-105 to -80). Six curves are shown: UMi Bad Antenna - Conducted (black line with circles), UMi Good Antenna - Conducted (magenta line with circles), UMi Nominal Antenna - Conducted (yellow line with circles), UMi Good Antenna - OTA (magenta dashed line with circles), UMi Nominal Antenna - OTA (yellow dashed line with circles), and UMi Bad Antenna - OTA (black dashed line with circles). The conducted results show higher throughput than the OTA results for the Good and Nominal antenna configurations.](18fcacec609d0fd4816b30201438a00a_img.jpg)
+
+Figure 10.2.2-3: Absolute data throughput framework results for the SCME UMi Channel model for Intel. The graph plots Throughput [kbps] on the y-axis (2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (-105 to -80). Six curves are shown: UMi Bad Antenna - Conducted (black line with circles), UMi Good Antenna - Conducted (magenta line with circles), UMi Nominal Antenna - Conducted (yellow line with circles), UMi Good Antenna - OTA (magenta dashed line with circles), UMi Nominal Antenna - OTA (yellow dashed line with circles), and UMi Bad Antenna - OTA (black dashed line with circles). The conducted results show higher throughput than the OTA results for the Good and Nominal antenna configurations.
+
+**Figure 10.2.2-3 Absolute data throughput framework results for the SCME UMi Channel model for Intel**
+
+![Figure 10.2.2-4: Absolute data throughput framework results for the SCME UMa B Channel model for Intel. The graph plots Throughput [kbps] on the y-axis (ranging from 2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (ranging from -105 to -80). Six curves are shown: UMa B Bad Antenna - Conducted (solid blue), UMa B Good Antenna - Conducted (solid red), UMa B Nominal Antenna - Conducted (solid green), UMa B Bad Antenna OTA (dashed blue), UMa B Nominal Antenna OTA (dashed green), and UMa B Good Antenna OTA (dashed red). The Good Antenna curves show the highest throughput, reaching approximately 3.5 x 10^4 kbps at lower RS EPRE values compared to the others.](bc9fe6d1f3411f724ddf3b8c11a37f7e_img.jpg)
+
+Figure 10.2.2-4: Absolute data throughput framework results for the SCME UMa B Channel model for Intel. The graph plots Throughput [kbps] on the y-axis (ranging from 2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (ranging from -105 to -80). Six curves are shown: UMa B Bad Antenna - Conducted (solid blue), UMa B Good Antenna - Conducted (solid red), UMa B Nominal Antenna - Conducted (solid green), UMa B Bad Antenna OTA (dashed blue), UMa B Nominal Antenna OTA (dashed green), and UMa B Good Antenna OTA (dashed red). The Good Antenna curves show the highest throughput, reaching approximately 3.5 x 10^4 kbps at lower RS EPRE values compared to the others.
+
+**Figure 10.2.2-4 Absolute data throughput framework results for the SCME UMa B Channel model for Intel**
+
+Figure 10.2.2-3 and Figure 10.2.2-4 show a results agreement within the specified margins.
+
+![Figure 10.2.2-5: Comparison between the conductive measurements between Intel and SATIMO for the SCME UMi channel model. The graph plots Throughput [kbps] on the y-axis (ranging from 2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (ranging from -110 to -80). The legend includes: Intel UMi Bad - Conducted faded (solid blue), Intel UMi Good Antenna - Conducted faded (solid red), Intel UMi Nominal Antenna - Conducted faded (solid green), Intel - Conducted Non faded (solid black with square markers), Satimo - Conducted Non faded (solid black with triangle markers), Satimo SCMe UMi Bad - Conducted faded (solid blue with triangle markers), Satimo SCMe UMi Nominal - Conducted faded (solid green with triangle markers), and Satimo SCMe UMi Good - Conducted faded (solid red with triangle markers).](e7d6aacb9818a209033d6d8d7b99c8d9_img.jpg)
+
+Figure 10.2.2-5: Comparison between the conductive measurements between Intel and SATIMO for the SCME UMi channel model. The graph plots Throughput [kbps] on the y-axis (ranging from 2 to 3.6 x 10^4) against RS EPRE [dBm/15 kHz] on the x-axis (ranging from -110 to -80). The legend includes: Intel UMi Bad - Conducted faded (solid blue), Intel UMi Good Antenna - Conducted faded (solid red), Intel UMi Nominal Antenna - Conducted faded (solid green), Intel - Conducted Non faded (solid black with square markers), Satimo - Conducted Non faded (solid black with triangle markers), Satimo SCMe UMi Bad - Conducted faded (solid blue with triangle markers), Satimo SCMe UMi Nominal - Conducted faded (solid green with triangle markers), and Satimo SCMe UMi Good - Conducted faded (solid red with triangle markers).
+
+**Figure 10.2.2-5: Comparison between the conductive measurements between Intel and SATIMO for the SCME UMi channel model**
+
+![Line graph showing Throughput [Kbps] vs RS EPRE [dBm/15 kHz] for conducted measurements. The y-axis ranges from 2 to 3.6 x 10^4 Kbps. The x-axis ranges from -110 to -80 dBm/15 kHz. The legend includes: Intel UMa B Bad Antenna - Conducted faded (blue line with circles), Intel UMa B Good Antenna - Conducted faded (red line with circles), Intel UMa B Nominal Antenna - Conducted faded (green line with circles), Intel - Conducted Non faded (black line with circles), Satimo - Conducted Non faded (black line with circles), Satimo UMaB Bad - Conducted faded (blue line with circles), Satimo UMaB Nominal - Conducted faded (green line with circles), and Satimo UMaB Good - Conducted faded (red line with circles). The graph shows that throughput increases with RS EPRE and is higher for good antennas and non-faded conditions.](bd361bbf5003c5df0416591de03a4522_img.jpg)
+
+Line graph showing Throughput [Kbps] vs RS EPRE [dBm/15 kHz] for conducted measurements. The y-axis ranges from 2 to 3.6 x 10^4 Kbps. The x-axis ranges from -110 to -80 dBm/15 kHz. The legend includes: Intel UMa B Bad Antenna - Conducted faded (blue line with circles), Intel UMa B Good Antenna - Conducted faded (red line with circles), Intel UMa B Nominal Antenna - Conducted faded (green line with circles), Intel - Conducted Non faded (black line with circles), Satimo - Conducted Non faded (black line with circles), Satimo UMaB Bad - Conducted faded (blue line with circles), Satimo UMaB Nominal - Conducted faded (green line with circles), and Satimo UMaB Good - Conducted faded (red line with circles). The graph shows that throughput increases with RS EPRE and is higher for good antennas and non-faded conditions.
+
+Figure 10.2.2-6: Comparison between the conductive measurements between Intel and SATIMO for the SCME UMaB channel model
+
+![Line graph showing Average radiated throughput [Kbps] vs RS EPRE [dBm/15 kHz] for UMi OTA measurements. The y-axis ranges from 2 to 3.6 x 10^4 Kbps. The x-axis ranges from -105 to -80 dBm/15 kHz. The legend includes: Intel UMi Good Antenna OTA (red line with circles), Intel UMi Nominal Antenna OTA (green line with circles), Intel UMi Bad Antenna OTA (blue line with circles), Satimo SCMe UMi Bad OTA (blue line with circles), Satimo SCMe UMi Nominal OTA (green line with circles), and Satimo SCMe UMi Good OTA (red line with circles). The graph shows that throughput increases with RS EPRE and is higher for good antennas and non-faded conditions.](ba3af4f84c0ed2d69d4eb276529510e2_img.jpg)
+
+Line graph showing Average radiated throughput [Kbps] vs RS EPRE [dBm/15 kHz] for UMi OTA measurements. The y-axis ranges from 2 to 3.6 x 10^4 Kbps. The x-axis ranges from -105 to -80 dBm/15 kHz. The legend includes: Intel UMi Good Antenna OTA (red line with circles), Intel UMi Nominal Antenna OTA (green line with circles), Intel UMi Bad Antenna OTA (blue line with circles), Satimo SCMe UMi Bad OTA (blue line with circles), Satimo SCMe UMi Nominal OTA (green line with circles), and Satimo SCMe UMi Good OTA (red line with circles). The graph shows that throughput increases with RS EPRE and is higher for good antennas and non-faded conditions.
+
+Figure 10.2.2-7: Average radiated throughput comparison under SCMe UMi OTA for Intel and SATIMO
+
+![Line graph showing Average radiated throughput comparison under SCMe UMa-B OTA for Intel and SATIMO. The y-axis is Throughput [Kbps] (multiplied by 10^4) ranging from 2 to 3.6. The x-axis is RS EPRE [dBm/15 kHz] ranging from -105 to -80. Six curves are shown: Intel UMa B Bad Antenna OTA (blue line with circles), Intel UMa B Nominal Antenna OTA (green line with circles), Intel UMa B Good Antenna OTA (red line with circles), Satimo SCMe UMa B Bad OTA (blue line with triangles), Satimo SCMe UMa B Nominal OTA (green line with triangles), and Satimo SCMe UMa B Good OTA (red line with triangles).](00f2e7c3d8a12df65c41a981bad8d89d_img.jpg)
+
+Line graph showing Average radiated throughput comparison under SCMe UMa-B OTA for Intel and SATIMO. The y-axis is Throughput [Kbps] (multiplied by 10^4) ranging from 2 to 3.6. The x-axis is RS EPRE [dBm/15 kHz] ranging from -105 to -80. Six curves are shown: Intel UMa B Bad Antenna OTA (blue line with circles), Intel UMa B Nominal Antenna OTA (green line with circles), Intel UMa B Good Antenna OTA (red line with circles), Satimo SCMe UMa B Bad OTA (blue line with triangles), Satimo SCMe UMa B Nominal OTA (green line with triangles), and Satimo SCMe UMa B Good OTA (red line with triangles).
+
+Figure 10.2.2-8: Average radiated throughput comparison under SCMe UMa-B OTA for Intel and SATIMO
+
+![Line graph showing Conducted non-faded measurements comparison between Intel and SATIMO. The y-axis is TPT [Mbps] ranging from 5 to 35. The x-axis is RS EPRE [dBm/15 KHz] ranging from -111 to -109. The legend lists 12 data series: Intel - S1 - DUTA - Rep 1, Intel - S1 - DUTA - Rep 2, Intel - S1 - DUTA - Rep 3, Intel - S1 - DUTB - Rep 1, Intel - S1 - DUTB - Rep 2, Intel - S2 - DUTA - Rep 1, Intel - S2 - DUTA - Rep 2, Intel - S2 - DUTA - Rep 3, Intel - S2 - DUTB - Rep 1, Intel - S2 - DUTB - Rep 2, Intel - S2 - DUTB - Rep 3, Intel - S2 - DUTB - Rep 4, Intel - S3 - DUTA - Rep 1, Intel - S4 - DUTA - Rep 1, and SATIMO - S5 - DUT MOSG-RD-13-05 - Rep 1.](c8d2bc5b813f5d46408a32185a56a7b1_img.jpg)
+
+Line graph showing Conducted non-faded measurements comparison between Intel and SATIMO. The y-axis is TPT [Mbps] ranging from 5 to 35. The x-axis is RS EPRE [dBm/15 KHz] ranging from -111 to -109. The legend lists 12 data series: Intel - S1 - DUTA - Rep 1, Intel - S1 - DUTA - Rep 2, Intel - S1 - DUTA - Rep 3, Intel - S1 - DUTB - Rep 1, Intel - S1 - DUTB - Rep 2, Intel - S2 - DUTA - Rep 1, Intel - S2 - DUTA - Rep 2, Intel - S2 - DUTA - Rep 3, Intel - S2 - DUTB - Rep 1, Intel - S2 - DUTB - Rep 2, Intel - S2 - DUTB - Rep 3, Intel - S2 - DUTB - Rep 4, Intel - S3 - DUTA - Rep 1, Intel - S4 - DUTA - Rep 1, and SATIMO - S5 - DUT MOSG-RD-13-05 - Rep 1.
+
+Figure 10.2.2-9: Conducted non-faded measurements comparison between Intel and SATIMO
+
+The legend in the Figure 10.2.2-9 should be read as indicated in Table 10.2.2-1.
+
+**Table 10.2.2-1: Explanation of the legend for Figure 10.2.2-9**
+
+| DUT/Setup     | Category | Lab             | Comment                                                 |
+|---------------|----------|-----------------|---------------------------------------------------------|
+| S1 – 4<br>S5  | Setup    | Intel<br>SATIMO | Different base station emulators and cable calibrations |
+| DUT A/B       | Phone    | Intel           | Details below                                           |
+| MOSG-RD-13-05 | Phone    | SATIMO          | Details below                                           |
+
+The references for the different phones are provided in Table 10.2.2-2.
+
+**Table 10.2.2-2: Explanation of the legend for Figure 10.2.2-9**
+
+| Device ID        | DUT A                       | DUT B                       | MOSG-RD-13-05 |
+|------------------|-----------------------------|-----------------------------|---------------|
+| Manufacturer     | HTC                         | HTC                         | HTC           |
+| Model            | Rezound                     | Rezound                     | Rezound       |
+| Operating system | Android 4.0.3               | Android 4.0.3               | Android       |
+| Software number  | 4.03.605.2 710RD            | 4.03.605.2 710RD            | NA            |
+| Baseband version | 2.22.10.0801r,2.22.10.0803r | 2.22.10.0801r,2.22.10.0803r | NA            |
+| Serial Number    | HT1APS201087                | HT1APS201196                | HT18KS200216  |
+| IMEI             | 990000338088158             | 990000338089248             | NA            |
+| HTC version      | Sense 3.6                   | Sense 3.6                   | NA            |
+| PRI Version      | 1.16_002-3.01_002           | 1.16_002-3.01_002           | NA            |
+| PRL Version      | 00000                       | 00666                       | NA            |
+| ERI Version      | 5                           | 5                           | NA            |
+| Kernel           | 3.0.16-g480e1b0             | 3.0.16-g480e1b0             | NA            |
+| Lab              | Intel                       | Intel                       | SATIMO        |
+
+And finally Rep. in the legend stands for repetition number.
+
+### 10.2.3 Reverberation chamber method using NIST channel model and using channel emulator with short delay spread low correlation channel model
+
+The IL/IT test results from CTIA MOSG LTE MIMO OTA Round Robin campaign for the reverberation chamber candidate methodology 1 (RC) using the NIST model are reproduced in figures 10.2.3-1 to 10.2.3-4.
+
+A maximum standard deviation uncertainty value for inter-chamber comparison of NIST of 0.7 dB STD has been found, showing that IL/IT consistency has been achieved using the reverberation chamber methodology 1 (RC).
+
+![Figure 10.2.3-1: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model (all reference antennas). The graph plots Throughput (%) from 70.0 to 100.0 against RS_EPRE (dBm/15kHz) from -108.00 to -90.00. It includes 14 data series for EMITE and BT hTC models under various NIST conditions (Good, Nominal, Bad) and antenna types (LC, SC, abs data tput).](475c496c4cd20198211aeaa241af7279_img.jpg)
+
+This graph shows the throughput performance for various hTC models and NIST channel conditions. The x-axis represents RS\_EPRE in dBm/15kHz, ranging from -108.00 to -90.00. The y-axis represents Throughput in percentage, ranging from 70.0 to 100.0. The legend identifies 14 different data series:
+ 
+
+- EMITE hTC Good NIST (blue line with circles)
+- EMITE hTC Nominal NIST (red line with squares)
+- EMITE hTC Bad NIST (green line with triangles)
+- BT hTC Good NIST LC (purple line with crosses)
+- BT hTC Good NIST SC (cyan line with squares)
+- BT hTC Nominal NIST LC (orange line with triangles)
+- BT hTC Nominal NIST SC (light blue line with crosses)
+- BT hTC Bad NIST LC (pink line with crosses)
+- BT hTC Bad NIST SC (light green line with circles)
+- EMITE hTC Good cond NIST abs data tput (dark green line with triangles)
+- EMITE hTC Nom cond NIST abs data tput (dark red line with squares)
+- EMITE hTC Bad cond NIST abs data tput (dark blue line with circles)
+- BT hTC Good cond NIST abs data tput (dark purple line with crosses)
+- BT hTC Nom cond NIST abs data tput (dark cyan line with squares)
+- BT hTC Bad cond NIST abs data tput (dark orange line with triangles)
+
+ The curves show that throughput increases with RS\_EPRE and plateaus at 100% for higher values. The 'Good cond NIST' and 'Good NIST' models generally achieve higher throughput at lower RS\_EPRE values compared to 'Nominal' and 'Bad' models.
+
+Figure 10.2.3-1: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model (all reference antennas). The graph plots Throughput (%) from 70.0 to 100.0 against RS\_EPRE (dBm/15kHz) from -108.00 to -90.00. It includes 14 data series for EMITE and BT hTC models under various NIST conditions (Good, Nominal, Bad) and antenna types (LC, SC, abs data tput).
+
+Figure 10.2.3-1: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model (all reference antennas)
+
+![Figure 10.2.3-2: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model with the Good reference antennas. The graph plots Throughput (%) from 70.0 to 100.0 against RS_EPRE (dBm/15kHz) from -108.00 to -100.00. It includes 5 data series for EMITE and BT hTC models using Good reference antennas.](89d23fa870a5ab93f96d1d119af3d0cb_img.jpg)
+
+This graph focuses on the throughput performance using Good reference antennas. The x-axis represents RS\_EPRE in dBm/15kHz, ranging from -108.00 to -100.00. The y-axis represents Throughput in percentage, ranging from 70.0 to 100.0. The legend identifies 5 data series:
+ 
+
+- EMITE hTC Good cond NIST abs data tput (dark green line with triangles)
+- EMITE hTC Good NIST (blue line with circles)
+- BT hTC Good cond NIST abs data tput (dark purple line with crosses)
+- BT hTC Good NIST LC (purple line with crosses)
+- BT hTC Good NIST SC (cyan line with squares)
+
+ All five series show a rapid increase in throughput as RS\_EPRE increases from -107.00 dBm/15kHz, reaching near 100% throughput by -102.00 dBm/15kHz. The performance of all models is very consistent when using Good reference antennas.
+
+Figure 10.2.3-2: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model with the Good reference antennas. The graph plots Throughput (%) from 70.0 to 100.0 against RS\_EPRE (dBm/15kHz) from -108.00 to -100.00. It includes 5 data series for EMITE and BT hTC models using Good reference antennas.
+
+Figure 10.2.3-2: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model with the Good reference antennas
+
+![Line graph showing Throughput (%) vs RS_EPRE (dBm/15kHz) for Nominal reference antennas. The graph compares EMITE and BT hTC results for Nominal NIST channel models. The x-axis ranges from -106.00 to -94.00 dBm/15kHz, and the y-axis ranges from 70.0 to 100.0%.](e84de38c2eac283d770e2c8acdf64308_img.jpg)
+
+This graph shows the throughput performance for Nominal reference antennas. The x-axis represents RS\_EPRE in dBm/15kHz, ranging from -106.00 to -94.00. The y-axis represents Throughput in %, ranging from 70.0 to 100.0. Five data series are plotted: EMITE hTC Nom cond NIST abs data tput (red squares), EMITE hTC Nominal NIST (red line), BT hTC Nom cond NIST abs data tput (blue crosses), BT hTC Nominal NIST LC (orange triangles), and BT hTC Nominal NIST SC (light blue crosses). All series show a sharp increase in throughput between -104 dBm/15kHz and -98 dBm/15kHz, reaching a plateau near 100% for values above -98 dBm/15kHz.
+
+| RS_EPRE (dBm/15kHz) | EMITE hTC Nom cond NIST abs data tput (%) | EMITE hTC Nominal NIST (%) | BT hTC Nom cond NIST abs data tput (%) | BT hTC Nominal NIST LC (%) | BT hTC Nominal NIST SC (%) |
+|---------------------|-------------------------------------------|----------------------------|----------------------------------------|----------------------------|----------------------------|
+| -104.00             | 70.0                                      | 70.0                       | 70.0                                   | 70.0                       | 70.0                       |
+| -102.00             | 85.0                                      | 88.0                       | 82.0                                   | 90.0                       | 87.0                       |
+| -100.00             | 96.0                                      | 98.0                       | 94.0                                   | 99.0                       | 97.0                       |
+| -98.00              | 99.5                                      | 100.0                      | 99.0                                   | 100.0                      | 100.0                      |
+| -96.00              | 100.0                                     | 100.0                      | 100.0                                  | 100.0                      | 100.0                      |
+| -94.00              | 100.0                                     | 100.0                      | 100.0                                  | 100.0                      | 100.0                      |
+
+Line graph showing Throughput (%) vs RS\_EPRE (dBm/15kHz) for Nominal reference antennas. The graph compares EMITE and BT hTC results for Nominal NIST channel models. The x-axis ranges from -106.00 to -94.00 dBm/15kHz, and the y-axis ranges from 70.0 to 100.0%.
+
+Figure 10.2.3-3: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model with the Nominal reference antennas
+
+![Line graph showing Throughput (%) vs RS_EPRE (dBm/15kHz) for Bad reference antennas. The graph compares EMITE and BT hTC results for Bad NIST channel models. The x-axis ranges from -100.00 to -88.00 dBm/15kHz, and the y-axis ranges from 70.0 to 100.0%.](eb672b49a91c9683b2dade9969e6c8b0_img.jpg)
+
+This graph shows the throughput performance for Bad reference antennas. The x-axis represents RS\_EPRE in dBm/15kHz, ranging from -100.00 to -88.00. The y-axis represents Throughput in %, ranging from 70.0 to 100.0. Five data series are plotted: EMITE hTC Bad cond NIST abs data tput (blue diamonds), EMITE hTC Bad NIST (green line), BT hTC Bad cond NIST abs data tput (orange circles), BT hTC Bad NIST LC (pink crosses), and BT hTC Bad NIST SC (light green crosses). The throughput increases sharply between -98 dBm/15kHz and -92 dBm/15kHz, plateauing near 100% for values above -92 dBm/15kHz.
+
+| RS_EPRE (dBm/15kHz) | EMITE hTC Bad cond NIST abs data tput (%) | EMITE hTC Bad NIST (%) | BT hTC Bad cond NIST abs data tput (%) | BT hTC Bad NIST LC (%) | BT hTC Bad NIST SC (%) |
+|---------------------|-------------------------------------------|------------------------|----------------------------------------|------------------------|------------------------|
+| -98.00              | 70.0                                      | 70.0                   | 70.0                                   | 70.0                   | 70.0                   |
+| -96.00              | 85.0                                      | 90.0                   | 80.0                                   | 92.0                   | 91.0                   |
+| -94.00              | 96.0                                      | 98.0                   | 92.0                                   | 99.0                   | 98.0                   |
+| -92.00              | 99.5                                      | 100.0                  | 98.0                                   | 100.0                  | 100.0                  |
+| -90.00              | 100.0                                     | 100.0                  | 99.0                                   | 100.0                  | 100.0                  |
+| -88.00              | 100.0                                     | 100.0                  | 100.0                                  | 100.0                  | 100.0                  |
+
+Line graph showing Throughput (%) vs RS\_EPRE (dBm/15kHz) for Bad reference antennas. The graph compares EMITE and BT hTC results for Bad NIST channel models. The x-axis ranges from -100.00 to -88.00 dBm/15kHz, and the y-axis ranges from 70.0 to 100.0%.
+
+Figure 10.2.3-4: IL/IT results consistency for Reverberation Chamber candidate methodology 1 (RC) measurements implementing the NIST channel model with the Bad reference antennas
+
+The IL/IT test results from CTIA MOSG LTE MIMO OTA Round Robin campaign for the reverberation chamber candidate methodology 2 (RC+CE) using the Short Delay Spread Low Correlation model are reproduced in Figures
+
+10.2.3-5 to 10.2.3-8. A maximum standard deviation uncertainty value for inter-chamber comparison of Short Delay Spread Low Correlation of 1.7 dB STD has been found, showing that IL/IT consistency has been achieved using the reverberation chamber methodology 2 (RC+CE).
+
+![Figure 10.2.3-5: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model (all antennas). The graph plots Throughput % (Y-axis, 70 to 100) against Power, dBm/15 KHz (X-axis, -110 to -85).](0e0257d43c47df039e9755c59674c2e5_img.jpg)
+
+The graph shows the relationship between Power (dBm/15 KHz) on the x-axis and Throughput (%) on the y-axis for various antenna configurations. The x-axis ranges from -110 to -85 dBm/15 KHz, and the y-axis ranges from 70 to 100% throughput. The legend identifies twelve data series: AZ-DevB-SD-Good-Cond (blue diamonds), AZ-DevB-SD-Bad-cond (red squares), AZ-DevB-SD-Nom-Cond (green triangles), BT-SD-Good-cond (purple crosses), BT-SD-Nom-cond (light blue crosses), BT-SD-Bad-cond (orange circles), AZ-DevB-SD-Bad-OTA (blue plus signs), AZ-DevB-SD-Nom-OTA (red plus signs), AZ-DevB-SD-Good-OTA (green plus signs), BT-SD-Good-OTA (purple plus signs), BT-SD-Nom-OTA (light blue plus signs), and BT-SD-Bad-OTA (orange plus signs). The curves show that throughput increases with power, and the 'Good-Cond' and 'Good-OTA' configurations achieve higher throughput at lower power levels compared to 'Bad-Cond' and 'Bad-OTA' configurations.
+
+Figure 10.2.3-5: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model (all antennas). The graph plots Throughput % (Y-axis, 70 to 100) against Power, dBm/15 KHz (X-axis, -110 to -85).
+
+Figure 10.2.3-5: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model (all antennas)
+
+![Line graph showing Throughput % vs Power (dBm/15 KHz) for four scenarios: AZ-DevB-SD-Good-Cond, BT-SD-Good-cond, AZ-DevB-SD-Good-OTA, and BT-SD-Good-OTA. The graph shows that throughput increases with power and plateaus at 100% for all scenarios. AZ-DevB-SD-Good-Cond reaches 100% throughput at the lowest power level, while BT-SD-Good-OTA reaches it at the highest power level.](12b521317c2c8ea33a1382d83e2b76be_img.jpg)
+
+The graph illustrates the consistency of IL/IT results for Reverberation Chamber candidate methodology 2 (RC+CE) measurements. The Y-axis represents Throughput % (70 to 100), and the X-axis represents Power, dBm/15 KHz (-110 to -95). Four data series are plotted: AZ-DevB-SD-Good-Cond (blue diamonds), BT-SD-Good-cond (purple crosses), AZ-DevB-SD-Good-OTA (green squares), and BT-SD-Good-OTA (purple diamonds). All series show a sharp increase in throughput as power increases, eventually plateauing at 100%.
+
+| Power, dBm/15 KHz | AZ-DevB-SD-Good-Cond (%) | BT-SD-Good-cond (%) | AZ-DevB-SD-Good-OTA (%) | BT-SD-Good-OTA (%) |
+|-------------------|--------------------------|---------------------|-------------------------|--------------------|
+| -108              | 76                       | -                   | -                       | -                  |
+| -107              | 84                       | -                   | 77                      | -                  |
+| -106              | 97                       | 70                  | 87                      | -                  |
+| -105              | 99                       | 88                  | 90                      | 74                 |
+| -104              | 100                      | 95                  | 97                      | 88                 |
+| -103              | 100                      | 99                  | 99                      | 94                 |
+| -102              | 100                      | 100                 | 100                     | 97                 |
+| -101              | 100                      | 100                 | 100                     | 99                 |
+| -100              | 100                      | 100                 | 100                     | 100                |
+| -99               | 100                      | 100                 | 100                     | 100                |
+| -98               | 100                      | 100                 | 100                     | 100                |
+| -97               | 100                      | 100                 | 100                     | 100                |
+| -96               | 100                      | 100                 | 100                     | 100                |
+| -95               | 100                      | 100                 | 100                     | 100                |
+
+Line graph showing Throughput % vs Power (dBm/15 KHz) for four scenarios: AZ-DevB-SD-Good-Cond, BT-SD-Good-cond, AZ-DevB-SD-Good-OTA, and BT-SD-Good-OTA. The graph shows that throughput increases with power and plateaus at 100% for all scenarios. AZ-DevB-SD-Good-Cond reaches 100% throughput at the lowest power level, while BT-SD-Good-OTA reaches it at the highest power level.
+
+Figure 10.2.3-6: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model with the Good reference antennas
+
+![Line graph showing Throughput % vs Power, dBm/15 KHz for Nominal reference antennas. Four series are plotted: AZ-DevB-SD-Nom-Cond (green triangles), BT-SD-Nom-cond (blue crosses), AZ-DevB-SD-Nom-OTA (pink squares), and BT-SD-Nom-OTA (light blue squares). Throughput increases with power, reaching 100% around -100 dBm/15 KHz.](572db3880dc9cf651443b610d82ea66b_img.jpg)
+
+| Power, dBm/15 KHz | AZ-DevB-SD-Nom-Cond (%) | BT-SD-Nom-cond (%) | AZ-DevB-SD-Nom-OTA (%) | BT-SD-Nom-OTA (%) |
+|-------------------|-------------------------|--------------------|------------------------|-------------------|
+| -105              | 75                      | -                  | -                      | -                 |
+| -104              | 83                      | -                  | -                      | -                 |
+| -103              | 93                      | 85                 | 82                     | -                 |
+| -102              | 97                      | 95                 | 87                     | 71                |
+| -101              | 98                      | 98                 | 92                     | 81                |
+| -100              | 99                      | 99                 | 97                     | 90                |
+| -99               | 99                      | 99                 | 98                     | 95                |
+| -98               | 99                      | 99                 | 99                     | 98                |
+| -97               | 99                      | 99                 | 99                     | 99                |
+| -96               | 99                      | 99                 | 99                     | 99                |
+| -95               | 99                      | 99                 | 99                     | 99                |
+
+Line graph showing Throughput % vs Power, dBm/15 KHz for Nominal reference antennas. Four series are plotted: AZ-DevB-SD-Nom-Cond (green triangles), BT-SD-Nom-cond (blue crosses), AZ-DevB-SD-Nom-OTA (pink squares), and BT-SD-Nom-OTA (light blue squares). Throughput increases with power, reaching 100% around -100 dBm/15 KHz.
+
+Figure 10.2.3-7: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model with the Nominal reference antennas
+
+![Line graph showing Throughput % vs Power, dBm/15 KHz for Bad reference antennas. Four series are plotted: AZ-DevB-SD-Bad-cond (dark red squares), BT-SD-Bad-cond (orange circles), AZ-DevB-SD-Bad-OTA (blue plus signs), and BT-SD-Bad-OTA (orange triangles). Throughput increases with power, reaching 100% around -92 dBm/15 KHz.](26489d838b18f7c0321fc12ed839dab2_img.jpg)
+
+| Power, dBm/15 KHz | AZ-DevB-SD-Bad-cond (%) | BT-SD-Bad-cond (%) | AZ-DevB-SD-Bad-OTA (%) | BT-SD-Bad-OTA (%) |
+|-------------------|-------------------------|--------------------|------------------------|-------------------|
+| -99               | 71                      | -                  | -                      | -                 |
+| -98               | 81                      | 72                 | -                      | -                 |
+| -97               | 88                      | 86                 | -                      | -                 |
+| -96               | 97                      | 94                 | 83                     | -                 |
+| -95               | 98                      | 97                 | 88                     | -                 |
+| -94               | 99                      | 99                 | 92                     | 78                |
+| -93               | 99                      | 99                 | 97                     | 88                |
+| -92               | 99                      | 99                 | 97                     | 93                |
+| -91               | 99                      | 99                 | 98                     | 95                |
+| -90               | 99                      | 99                 | 99                     | 96                |
+| -89               | 99                      | 99                 | 99                     | 97                |
+| -88               | 99                      | 99                 | 99                     | 99                |
+| -87               | 99                      | 99                 | 99                     | 99                |
+
+Line graph showing Throughput % vs Power, dBm/15 KHz for Bad reference antennas. Four series are plotted: AZ-DevB-SD-Bad-cond (dark red squares), BT-SD-Bad-cond (orange circles), AZ-DevB-SD-Bad-OTA (blue plus signs), and BT-SD-Bad-OTA (orange triangles). Throughput increases with power, reaching 100% around -92 dBm/15 KHz.
+
+Figure 10.2.3-8: IL/IT results consistency for Reverberation Chamber candidate methodology 2 (RC+CE) measurements implementing the Short Delay channel model with the Bad reference antennas
+
+The IL/IT test results from CTIA MOSG LTE MIMO OTA Round Robin campaign for the reverberation chamber candidate methodology 2 (RC+CE) using the Long Delay Spread High Correlation model are reproduced in figures 10.2.3-9 to 10.2.3-12. A maximum standard deviation uncertainty value for inter-chamber comparison of Long Delay Spread High Correlation of 1.86 dB STD has been found, showing that IL/IT consistency has been achieved using the reverberation chamber methodology 2 (RC+CE).
+
+![Figure 10.2.3-9: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model (all antennas). The graph plots Throughput (%) on the y-axis (70% to 100%) against Power (dBm/15 KHz) on the x-axis (-105 to -85). It shows 12 curves representing different antenna configurations and channel models (AZ and BT, Long Delay, B-good, B-nominal, B-bad, OTA, Conducted).](a93a411a51b0e65719fab15f375fdd82_img.jpg)
+
+The graph shows the relationship between Power (dBm/15 KHz) on the x-axis and Throughput (%) on the y-axis. The x-axis ranges from -105 to -85 dBm/15 KHz, and the y-axis ranges from 70% to 100% throughput. There are 12 data series plotted, each representing a different antenna configuration and channel model. The series are:
+ 
+
+- AZ-Long Delay/B-bad-OTA (blue line with 'x' markers)
+- AZ-Long Delay/B-nominal-OTA (red line with square markers)
+- AZ-Long Delay/B-good-OTA (green line with triangle markers)
+- AZ-Long Delay/B-good-Conducted (purple line with diamond markers)
+- AZ-Long Delay/B-bad-Conducted (cyan line with square markers)
+- AZ-Long Delay/B-nominal-Conducted (orange line with triangle markers)
+- BT-Long Delay/B - Good-OTA (dark blue line with 'x' markers)
+- BT-Long Delay/B-Nominal-OTA (dark red line with square markers)
+- BT-Long Delay/B-Bad-OTA (dark green line with triangle markers)
+- BT-Long Delay/B- Good-Conducted (dark purple line with diamond markers)
+- BT-Long Delay/B-Nom-Conducted (dark cyan line with square markers)
+- BT-Long Delay/B-Bad-Conducted (dark orange line with triangle markers)
+
+ The curves show that as power increases, throughput increases and plateaus. The 'Good' channel models generally achieve higher throughput at lower power levels compared to 'Bad' or 'Nominal' models. Conducted measurements typically show higher throughput than OTA measurements for the same channel model.
+
+Figure 10.2.3-9: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model (all antennas). The graph plots Throughput (%) on the y-axis (70% to 100%) against Power (dBm/15 KHz) on the x-axis (-105 to -85). It shows 12 curves representing different antenna configurations and channel models (AZ and BT, Long Delay, B-good, B-nominal, B-bad, OTA, Conducted).
+
+**Figure 10.2.3-9: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model (all antennas)**
+
+![Figure 10.2.3-10: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Good reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-good-OTA (green line with circles), AZ-Long Delay/B-good-Conducted (purple line with diamonds), BT-Long Delay/B - Good-OTA (blue line with diamonds), and BT-Long Delay/B- Good-Conducted (dark purple line with crosses). All curves show a sharp increase in throughput between -102 dBm and -95 dBm, reaching near 100% by -92 dBm.](64e9a7b00fe083b55736c3eb5a7139e9_img.jpg)
+
+Figure 10.2.3-10: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Good reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-good-OTA (green line with circles), AZ-Long Delay/B-good-Conducted (purple line with diamonds), BT-Long Delay/B - Good-OTA (blue line with diamonds), and BT-Long Delay/B- Good-Conducted (dark purple line with crosses). All curves show a sharp increase in throughput between -102 dBm and -95 dBm, reaching near 100% by -92 dBm.
+
+**Figure 10.2.3-10: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Good reference antenna only**
+
+![Figure 10.2.3-11: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Nominal reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-nominal-OTA (red line with circles), AZ-Long Delay/B-nominal-Conducted (orange line with triangles), BT-Long Delay/B-Nominal-OTA (dark red line with squares), and BT-Long Delay/B-Nom-Conducted (light blue line with crosses). All curves show a sharp increase in throughput between -100 dBm and -93 dBm, reaching near 100% by -90 dBm.](7416c959934a45ae287874c83007a146_img.jpg)
+
+Figure 10.2.3-11: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Nominal reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-nominal-OTA (red line with circles), AZ-Long Delay/B-nominal-Conducted (orange line with triangles), BT-Long Delay/B-Nominal-OTA (dark red line with squares), and BT-Long Delay/B-Nom-Conducted (light blue line with crosses). All curves show a sharp increase in throughput between -100 dBm and -93 dBm, reaching near 100% by -90 dBm.
+
+**Figure 10.2.3-11: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Nominal reference antenna only**
+
+![Figure 10.2.3-12: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Bad reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-bad-OTA (blue line with 'x' markers), AZ-Long Delay/B-bad-Conducted (blue line with square markers), BT-Long Delay/B-Bad-OTA (green line with triangle markers), and BT-Long Delay/B-Bad-Conducted (orange line with circle markers). All curves show a sharp increase in throughput as power increases, with the conducted measurements generally achieving higher throughput at lower power levels compared to OTA measurements.](7317ad6b925dc0474d45f40ac5d3ae3d_img.jpg)
+
+| Power (dBm/15 KHz) | AZ-Long Delay/B-bad-OTA (%) | AZ-Long Delay/B-bad-Conducted (%) | BT-Long Delay/B-Bad-OTA (%) | BT-Long Delay/B-Bad-Conducted (%) |
+|--------------------|-----------------------------|-----------------------------------|-----------------------------|-----------------------------------|
+| -93                | -                           | -                                 | -                           | 74                                |
+| -92                | 70                          | 72                                | 70                          | 83                                |
+| -91                | 75                          | 83                                | 74                          | 88                                |
+| -90                | 78                          | 87                                | 79                          | 91                                |
+| -89                | 82                          | 92                                | 85                          | 93                                |
+| -88                | 85                          | 95                                | 87                          | 96                                |
+| -87                | 88                          | 96                                | 89                          | 97                                |
+| -86                | 90                          | 97                                | 90                          | 98                                |
+| -85                | 91                          | 98                                | 91                          | 99                                |
+
+Figure 10.2.3-12: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Bad reference antenna only. The graph shows Throughput, % (70% to 100%) vs Power (dBm/15 KHz) (-105 to -85). Four curves are plotted: AZ-Long Delay/B-bad-OTA (blue line with 'x' markers), AZ-Long Delay/B-bad-Conducted (blue line with square markers), BT-Long Delay/B-Bad-OTA (green line with triangle markers), and BT-Long Delay/B-Bad-Conducted (orange line with circle markers). All curves show a sharp increase in throughput as power increases, with the conducted measurements generally achieving higher throughput at lower power levels compared to OTA measurements.
+
+**Figure 10.2.3-12: IL/IT results consistency for reverberation chamber methodology 2 (RC+CE) measurements implementing the Long Delay Spread High Correlation channel model with Bad reference antenna only**
+
+The case for conducted non-faded measurements is shown in Figure 10.2.3-13.
+
+![Figure 10.2.3-13: Conducted non-faded measurements comparison between Bluetest and Azimuth. The graph shows Throughput % (70% to 100%) vs Power (dBm/15 KHz) (-120 to -110). Two curves are plotted: AZ-DevB-Static-Cond (red line with square markers) and BT-Static-Cond (green line with triangle markers). Both curves show a sharp increase in throughput as power increases, with the BT-Static-Cond measurement achieving 100% throughput at a lower power level (-113.5 dBm) compared to the AZ-DevB-Static-Cond measurement (-112.5 dBm).](ba99363c7d61d24290635b47b71e41c2_img.jpg)
+
+| Power (dBm/15 KHz) | AZ-DevB-Static-Cond (%) | BT-Static-Cond (%) |
+|--------------------|-------------------------|--------------------|
+| -114               | -                       | 70                 |
+| -113.5             | -                       | 100                |
+| -113               | -                       | 100                |
+| -112.5             | 70                      | -                  |
+| -112               | 99                      | -                  |
+| -111               | 100                     | -                  |
+| -110               | 100                     | -                  |
+
+Figure 10.2.3-13: Conducted non-faded measurements comparison between Bluetest and Azimuth. The graph shows Throughput % (70% to 100%) vs Power (dBm/15 KHz) (-120 to -110). Two curves are plotted: AZ-DevB-Static-Cond (red line with square markers) and BT-Static-Cond (green line with triangle markers). Both curves show a sharp increase in throughput as power increases, with the BT-Static-Cond measurement achieving 100% throughput at a lower power level (-113.5 dBm) compared to the AZ-DevB-Static-Cond measurement (-112.5 dBm).
+
+**Figure 10.2.3-13: Conducted non-faded measurements comparison between Bluetest and Azimuth**
+
+In all cases for Figures 10.2.3-5 through 10.2.3-13 the following applies:
+
+- AZ: Azimuth
+- BT: Bluetest
+
+The details on the devices used in all cases for Figures 10.2.3-5 through 10.2.3-13 are given in the table below.
+
+**Table 10.1.2-1**
+
+|                      | Azimuth Lab     | Bluetest Lab    |
+|----------------------|-----------------|-----------------|
+| <b>Device ID</b>     | Dev B           | MOSG-RD-13-03   |
+| <b>Manufacturer</b>  | HTC             | HTC             |
+| <b>Model</b>         | Rezound         | Rezound         |
+| <b>Model Number</b>  | ADR6425LVW      | ADR6425LVW      |
+| <b>Serial Number</b> | HT1AXS201238    | HT18KS200207    |
+| <b>IMEI Number</b>   | 990000338748983 | 990000327075521 |
+
+### 10.2.4 RTS method results
+
+Inter-Lab/Inter-Technique (IL/IT) campaigns have been performed in CTIA MOSG LTE MIMO OTA by the RTS test methodology by Agilent's lab and CATR using the GTS lab. Both labs used the correlation implementation of the SCME channel model with the Jake's Doppler spectrum.
+
+The static conducted baseline measurements for Agilent and GTS are provided in Figure 10.2.4-1.
+
+![Figure 10.2.4-1: Two-stage static sensitivity results. A line graph showing Throughput (Mbps) on the Y-axis (0 to 40) versus RS_EPRE (dBm/15kHz) on the X-axis (-115 to -93). Two data series are plotted: GTS static (purple line with 'x' markers) and Agilent static (red line with square markers). Both series show a sharp increase in throughput starting around -113 dBm/15kHz, reaching a plateau of approximately 35 Mbps between -111 dBm/15kHz and -107 dBm/15kHz. The Agilent static series reaches the plateau slightly earlier than the GTS static series.](61de503b1d455cc618610b290f55914d_img.jpg)
+
+| RS_EPRE (dBm/15kHz) | GTS static Throughput (Mbps) | Agilent static Throughput (Mbps) |
+|---------------------|------------------------------|----------------------------------|
+| -113                | 0                            | 0                                |
+| -112                | 10                           | 30                               |
+| -111                | 35                           | 35                               |
+| -110                | 35                           | 35                               |
+| -109                | 35                           | 35                               |
+| -108                | 35                           | 35                               |
+| -107                | 35                           | 35                               |
+
+Figure 10.2.4-1: Two-stage static sensitivity results. A line graph showing Throughput (Mbps) on the Y-axis (0 to 40) versus RS\_EPRE (dBm/15kHz) on the X-axis (-115 to -93). Two data series are plotted: GTS static (purple line with 'x' markers) and Agilent static (red line with square markers). Both series show a sharp increase in throughput starting around -113 dBm/15kHz, reaching a plateau of approximately 35 Mbps between -111 dBm/15kHz and -107 dBm/15kHz. The Agilent static series reaches the plateau slightly earlier than the GTS static series.
+
+**Figure 10.2.4-1: Static conducted reference results for Agilent and GTS**
+
+The absolute data throughput framework proof of concept for the RTS method is in Clause 9.3.1.7.
+
+The absolute data throughput measurements for the new GTS lab to demonstrate equivalence between conducted and radiated measurements was performed for the UMi channel model are shown in Figures 10.2.4-2 and 10.2.4-3.
+
+These results show approximately +/- 0.2 dB consistency for UMi and +/- 0.6 dB consistency for UMa/B.
+
+![Umi Radiated and Cable-conducted Results graph showing Throughput(MBps) vs RS_EPRE (dBm/15kHz) for UMi Model.](c9829c80e5f6e9384df5f75e24da4c25_img.jpg)
+
+This line graph, titled "Umi Radiated and Cable-conducted Results", compares the throughput performance of the UMi model under various conditions. The x-axis represents RS\_EPRE (dBm/15kHz) from -102 to -76, and the y-axis represents Throughput(MBps) from 25 to 35. Six data series are plotted: Umi, good,cable (green line with circles), Umi, normal,cable (purple line with diamonds), Umi, bad,cable (light blue line with squares), Umi, normal,OTA (red line with squares), Umi, bad,OTA (dark green line with triangles), and Umi, good,OTA (blue line with diamonds). The "good,OTA" series shows the highest performance, reaching a throughput of approximately 35 MBps at -96 dBm/15kHz. The "bad,OTA" series shows the lowest performance, reaching the same throughput at approximately -88 dBm/15kHz.
+
+| RS_EPRE (dBm/15kHz) | Umi, good,cable | Umi, normal,cable | Umi, bad,cable | Umi, normal,OTA | Umi, bad,OTA | Umi, good,OTA |
+|---------------------|-----------------|-------------------|----------------|-----------------|--------------|---------------|
+| -102                | 25.5            | -                 | -              | -               | -            | 27.5          |
+| -100                | 31.5            | -                 | -              | -               | -            | 34.5          |
+| -98                 | -               | 31.5              | -              | 28.5            | -            | 35.0          |
+| -96                 | -               | -                 | -              | 33.5            | -            | 35.0          |
+| -94                 | -               | -                 | -              | -               | 25.5         | 35.0          |
+| -92                 | -               | -                 | 31.5           | -               | 31.5         | 35.0          |
+| -90                 | -               | -                 | -              | -               | 34.5         | 35.0          |
+| -88                 | -               | -                 | -              | -               | 35.0         | 35.0          |
+| -86                 | -               | -                 | -              | -               | 35.0         | 35.0          |
+| -84                 | -               | -                 | 35.0           | -               | 35.0         | 35.0          |
+| -82                 | -               | -                 | 35.0           | -               | 35.0         | 35.0          |
+
+Umi Radiated and Cable-conducted Results graph showing Throughput(MBps) vs RS\_EPRE (dBm/15kHz) for UMi Model.
+
+Figure 10.2.4-2: Radiated vs Cable-conducted Absolute Throughput Test for UMi Model for the GTS lab
+
+![UMa/B Cable conducted and Radiated Results graph showing Throughput (MBps) vs RS_EPRE (dBm/15kHz) for UMa/B Model.](a4a24ac70004b2e8087923d3f0f6d01d_img.jpg)
+
+This line graph, titled "UMa/B Cable conducted and Radiated Results", compares the throughput performance of the UMa/B model. The x-axis represents RS\_EPRE (dBm/15kHz) from -105 to -81, and the y-axis represents Throughput (MBps) from 24 to 36. Six data series are plotted: OTA,UmaB good (blue line with circles), OTA,UmaB norm (red line with squares), OTA,UmaB bad (green line with triangles), Cable,Uma good (blue line with diamonds), Cable,Uma norm (red line with squares), and Cable,Uma bad (green line with triangles). The "Cable,Uma good" series shows the highest performance, reaching a throughput of approximately 35 MBps at -93 dBm/15kHz. The "OTA,UmaB bad" series shows the lowest performance, reaching the same throughput at approximately -88 dBm/15kHz.
+
+| RS_EPRE (dBm/15kHz) | OTA,UmaB good | OTA,UmaB norm | OTA,UmaB bad | Cable,Uma good | Cable,Uma norm | Cable,Uma bad |
+|---------------------|---------------|---------------|--------------|----------------|----------------|---------------|
+| -105                | -             | -             | -            | 24.5           | -              | -             |
+| -103                | -             | -             | -            | 26.5           | -              | -             |
+| -101                | -             | -             | -            | 28.5           | -              | -             |
+| -99                 | -             | -             | -            | 30.5           | -              | -             |
+| -97                 | -             | -             | -            | 32.5           | 26.5           | -             |
+| -95                 | -             | -             | -            | 34.5           | 28.5           | -             |
+| -93                 | -             | -             | -            | 35.0           | 32.5           | 24.5          |
+| -91                 | -             | -             | 32.5         | 35.0           | 34.5           | 30.5          |
+| -89                 | -             | -             | 34.5         | 35.0           | 35.0           | 33.5          |
+| -87                 | -             | -             | 35.0         | 35.0           | 35.0           | 34.5          |
+| -85                 | -             | -             | 35.0         | 35.0           | 35.0           | 35.0          |
+| -83                 | -             | -             | 35.0         | 35.0           | 35.0           | 35.0          |
+| -81                 | -             | -             | 35.0         | 35.0           | 35.0           | 35.0          |
+
+UMa/B Cable conducted and Radiated Results graph showing Throughput (MBps) vs RS\_EPRE (dBm/15kHz) for UMa/B Model.
+
+Figure 10.2.4-3: Radiated vs. Cable-conducted Absolute Throughput Test for UMa/B Model for the GTS lab
+
+A comparison between both RTS labs is shown in Figures 10.2.4-4 and 10.2.4-5.
+
+![Two-stage UMi Comparison graph showing throughput vs SNR for Agilent and GTS in Good, Nom, and Bad conditions.](6766862d9c432178c879b0f71ad2dac1_img.jpg)
+
+**Two-stage UMi Comparison**
+
+This line graph compares the throughput (Y-axis, 24 to 36) against the SNR (X-axis, -105 to -85) for the UMi scenario. The legend identifies six data series: Agilent, Good (purple line); Agilent, Nom (cyan line); Agilent, Bad (orange line); GTS, Good (blue line with diamond markers); GTS, Nom (red line with square markers); and GTS, Bad (purple line with 'x' markers). The Agilent, Good series shows the best performance, reaching a throughput of approximately 35.5 at an SNR of -95. The GTS, Good series follows closely. The Agilent, Nom and GTS, Nom series show similar performance, reaching a throughput of about 35 at an SNR of -93. The Agilent, Bad and GTS, Bad series show the worst performance, reaching a throughput of about 35 at an SNR of -91.
+
+| SNR  | Agilent, Good | Agilent, Nom | Agilent, Bad | GTS, Good | GTS, Nom | GTS, Bad |
+|------|---------------|--------------|--------------|-----------|----------|----------|
+| -105 | 24.0          | -            | -            | -         | -        | -        |
+| -103 | 32.0          | -            | -            | -         | -        | -        |
+| -101 | 34.5          | -            | -            | 27.5      | -        | -        |
+| -99  | 35.0          | -            | -            | 32.0      | -        | -        |
+| -97  | 35.2          | 33.0         | -            | 34.0      | 28.5     | -        |
+| -95  | 35.3          | 34.5         | -            | 35.0      | 32.5     | -        |
+| -93  | 35.4          | 35.0         | 30.0         | 35.2      | 34.5     | 25.5     |
+| -91  | 35.5          | 35.2         | 33.5         | 35.3      | 35.0     | 32.0     |
+| -89  | 35.5          | 35.3         | 35.0         | 35.4      | 35.2     | 34.5     |
+| -87  | 35.5          | 35.4         | 35.2         | 35.5      | 35.3     | 35.0     |
+| -85  | 35.5          | 35.5         | 35.3         | 35.5      | 35.4     | 35.2     |
+
+Two-stage UMi Comparison graph showing throughput vs SNR for Agilent and GTS in Good, Nom, and Bad conditions.
+
+Figure 10.2.4-4: Comparison of RTS results for UMi
+
+![Two-stage UMa/B Comparison graph showing throughput vs SNR for Agilent and GTS in Good, Nom, and Bad conditions.](c3f02cb9dab65cb16d8a4f9aa20bf12d_img.jpg)
+
+**Two-stage UMa/B Comparison**
+
+This line graph compares the throughput (Y-axis, 24 to 36) against the SNR (X-axis, -100 to -80) for the UMa/B scenario. The legend identifies six data series: Agilent, Good (blue line with '+' markers); Agilent, Nom (red line); Agilent, Bad (green line); GTS, Good (purple line with diamond markers); GTS, Nom (cyan line with square markers); and GTS, Bad (orange line with triangle markers). The Agilent, Good and Agilent, Nom series show the best performance, reaching a throughput of approximately 35.5 at an SNR of -92. The GTS, Good and GTS, Nom series follow closely, reaching a throughput of about 35 at an SNR of -90. The GTS, Bad series shows intermediate performance, reaching a throughput of about 35 at an SNR of -88. The Agilent, Bad series shows the worst performance, reaching a throughput of about 34 at an SNR of -82.
+
+| SNR  | Agilent, Good | Agilent, Nom | Agilent, Bad | GTS, Good | GTS, Nom | GTS, Bad |
+|------|---------------|--------------|--------------|-----------|----------|----------|
+| -100 | -             | -            | -            | -         | -        | -        |
+| -98  | 24.0          | 24.0         | -            | -         | -        | -        |
+| -96  | 30.0          | 30.0         | -            | 28.0      | -        | -        |
+| -94  | 33.0          | 33.0         | -            | 31.0      | 27.0     | -        |
+| -92  | 34.5          | 34.5         | -            | 33.5      | 31.5     | 27.0     |
+| -90  | 35.0          | 35.0         | -            | 34.5      | 33.5     | 31.0     |
+| -88  | 35.2          | 35.2         | 24.0         | 35.0      | 34.5     | 34.0     |
+| -86  | 35.3          | 35.3         | 28.0         | 35.2      | 35.0     | 35.0     |
+| -84  | 35.4          | 35.4         | 31.0         | 35.3      | 35.2     | 35.2     |
+| -82  | 35.5          | 35.5         | 33.0         | 35.4      | 35.3     | 35.3     |
+| -80  | 35.5          | 35.5         | 34.0         | 35.5      | 35.4     | 35.4     |
+
+Two-stage UMa/B Comparison graph showing throughput vs SNR for Agilent and GTS in Good, Nom, and Bad conditions.
+
+Figure 10.2.4-5: Comparison of RTS results for UMa/B
+
+The RTS UMi results compared against Intel and SATIMO anechoic are shown in Figure 10.2.4-6.
+
+![UMi Comparison graph showing Absolute Throughput vs SNR for UMi Model. The graph compares Agilent, GTS, Intel, and Satimo results across Good, Nom, and Bad channel conditions. The x-axis represents SNR from -105 to -85 dB, and the y-axis represents Throughput from 24 to 36 Mbps.](67032144ed8eb3c41af3ef1aa82a9c74_img.jpg)
+
+**UMi Comparison**
+
+This line graph shows the absolute throughput (Mbps) versus SNR (dB) for the UMi model. The x-axis ranges from -105 to -85 dB in 2 dB increments. The y-axis ranges from 24 to 36 Mbps in 2 Mbps increments. The legend identifies 12 data series: Agilent (Good, Nom, Bad), GTS (Good, Nom, Bad), Intel (Good, Nom, Bad), and Satimo (Good, Nom, Bad). Satimo's 'Good' condition shows the best performance, reaching 36 Mbps at approximately -100 dB SNR. Agilent's 'Good' condition follows closely. GTS and Intel show similar performance, with their 'Good' conditions reaching 36 Mbps around -95 dB SNR. All 'Nom' and 'Bad' conditions show significantly lower performance, with 'Bad' conditions only reaching 36 Mbps at SNRs above -90 dB.
+
+UMi Comparison graph showing Absolute Throughput vs SNR for UMi Model. The graph compares Agilent, GTS, Intel, and Satimo results across Good, Nom, and Bad channel conditions. The x-axis represents SNR from -105 to -85 dB, and the y-axis represents Throughput from 24 to 36 Mbps.
+
+Figure 10.2.4-6: Absolute Throughput Test for UMi Model
+
+The RTS UMa results compared against Intel and SATIMO anechoic are shown in Figure 10.2.4-7.
+
+![UMaB Comparison graph showing Absolute Throughput vs SNR for UMa/B Model. The graph compares Agilent, GTS, Intel, and Satimo results across Good, Nom, and Bad channel conditions. The x-axis represents SNR from -100 to -80 dB, and the y-axis represents Throughput from 24 to 36 Mbps.](a5d373f8234b0a8b8f4541da64f9ac64_img.jpg)
+
+**UMaB Comparison**
+
+This line graph shows the absolute throughput (Mbps) versus SNR (dB) for the UMa/B model. The x-axis ranges from -100 to -80 dB in 2 dB increments. The y-axis ranges from 24 to 36 Mbps in 2 Mbps increments. The legend identifies 12 data series: Agilent (Good, Nom, Bad), GTS (Good, Nom, Bad), Intel (Good, Nom, Bad), and Satimo (good, Nom, Bad). Intel's 'Good' condition shows the best performance, reaching 36 Mbps at approximately -95 dB SNR. Agilent's 'Good' condition follows. GTS and Satimo show similar performance, with their 'Good' conditions reaching 36 Mbps around -92 dB SNR. All 'Nom' and 'Bad' conditions show lower performance, with 'Bad' conditions only reaching 36 Mbps at SNRs above -85 dB.
+
+UMaB Comparison graph showing Absolute Throughput vs SNR for UMa/B Model. The graph compares Agilent, GTS, Intel, and Satimo results across Good, Nom, and Bad channel conditions. The x-axis represents SNR from -100 to -80 dB, and the y-axis represents Throughput from 24 to 36 Mbps.
+
+Figure 10.2.4-7: Absolute Throughput Test for UMa/B Model
+
+A tabular comparison of all the results at 70% throughput is given in Tables 10.2.4-1 and 10.2.4-2.
+
+Table 10.2.4-1: Summary of UMi results at 70% throughput
+
+|                   | Good (dBm) | Nominal (dBm) | Bad (dBm) |
+|-------------------|------------|---------------|-----------|
+| <b>Agilent</b>    | -103.6     | -99.4         | -94.7     |
+| <b>GTS</b>        | -101.5     | -98.2         | -94.2     |
+| <b>Intel</b>      | -100.5     | -99           | -94.2     |
+| <b>SATIMO</b>     | -102.8     | -100          | -94.2     |
+| <b>Spread +/-</b> | +/- 1.55   | +/- 0.9       | +/- 0.25  |
+
+**Table 10.2.4-2. Summary of UMa results at 70% throughput**
+
+|                         | Good (dBm) | Nominal (dBm) | Bad (dBm) |
+|-------------------------|------------|---------------|-----------|
+| <b>Agilent</b>          | -97.9      | -97.6         | -89.2     |
+| <b>GTS</b>              | -96.6      | -95.8         | -92       |
+| <b>Intel</b>            | -98        | -96.8         | -91.5     |
+| <b>SATIMO</b>           | -98        | -94.7         | -89.3     |
+| <b>Spread (all) +/-</b> | +/- 0.7    | +/- 1.45      | +/- 1.4   |
+
+## 10.3 3GPP harmonization test campaign
+
+### 10.3.1 Description of the test plan
+
+The objective of the harmonization measurement campaign is to capture comparable data from the different MIMO OTA methodologies, whose procedures are described in Clause 12, and to draw conclusions based on this data on the ability to harmonize across two or more methodologies.
+
+The free space (FS) testing condition is used in this measurement campaign.
+
+1. Eight device orientations are used for testing with the MPAC and RTS methodologies. With the vertical portrait orientation defined as (0,0,0) of (yaw, pitch, roll), these are:Portrait - (0°, 0°, roll)
+2. Portrait tilt down - (0°, -45°, roll)
+3. Portrait tilt up - (0°, 45°, roll)
+4. Face up - (0°, 90°, roll)
+5. Face down - (0°, -90°, roll)
+6. Landscape - (90°, 0°, roll)
+7. Landscape tilt down - (90°, -45°, roll)
+8. Landscape tilt up - (90°, 45°, roll),
+
+where the roll is represented by the rotation around the turntable axis to produce a single cut.
+
+For MPAC and RTS methodologies a complete Throughput versus Power curve is obtained over 12 azimuth angles per device orientation. The total number of subframes (TNS) per power step is 20,000 to enable post-processing of the result using the agreed FoM working assumptions.
+
+For RC and RC+CE, device orientation is not applicable, but the following other conditions apply. At least 100 samples and 400 subframes per power step and sample (giving a total of 40,000 TNS per power step) are measured to enable post-processing of the results using the FoM working assumptions. Additionally, an MU analysis on the TNS will be completed by measuring all the devices with at least 100 samples and 20,000 subframes per power step and sample (giving a total of TNS=2,000,000 per power step), with the aim of validating the use of the small number of subframes through a comparison of their final averaged outage values. Results for both stepwise and continuous stirring modes are measured.
+
+For any method, the power step is 0.5 dB from 95% down to 60%.
+
+The following channel models are emulated by the different methodologies:
+
+RC: NIST channel model (Table C.2-3)
+
+RC+CE: Short delay spread low correlation (SDLC; Table C.2-1) and long delay spread high correlation (LDHC; Table C.2-2)
+
+MPAC: SCMe UMi (Table 8.2-1) and SCMe UMa (Table 8.2-2)
+
+RTS: SCMe UMi (Table 8.2-1) and SCMe UMa (Table 8.2-2)
+
+The following is the working assumption on the figure of merit to be used for the analysis of harmonization testing campaign results:
+
+Option 1: statistic of outages per throughput curve
+
+Option 2: outage point from the average throughput curve
+
+In addition to these procedures, each methodology also performs absolute data throughput framework tests in order to derive the measurement uncertainty bound for harmonization (as defined in Clause 10.3.3). The AC methodologies utilize a single free space portrait 90° device orientation, with the MIMO reference antenna placed at 90° elevation, and the RF enclosure door facing the 0° azimuth. The RC test methodologies conduct their measurements in stepstirred mode only. The lab performing RC and RC+CE methodologies can determine the optimal number of subframes per stirring state and per power level for the ADTF analysis only. All methodologies use the channel models defined in Clauses 8.2 and Annex C. ADTF results for each methodology, band, and channel model include 5 conducted ADTF results and 5 radiated results. The ADTF repeatability results for the MPAC methodology were impacted by additional measurement uncertainty due to re-cabling and test system re-configuration during the repeatability testing period.
+
+### 10.3.2 Devices under test
+
+The devices used in the harmonization testing campaign are listed in Tables 10.3.2-1, 10.3.2-2 and 10.3.2-3 below.
+
+**Table 10.3.2-1: Devices used in the harmonization testing campaign: device set 1**
+
+|                     |               | MPAC | RC   | RC+CE | RTS                            |
+|---------------------|---------------|------|------|-------|--------------------------------|
+| <b>Band 13</b>      | DUT01         | Done | Done | Done  | Done                           |
+|                     | DUT02         | Done | Done | Done  | DUT does not support           |
+|                     | DUT03 (Black) | Done | Done | Done  | Done                           |
+| <b>Band 13 ADTF</b> | DUT04 (White) | Done | Done | Done  | Done                           |
+| <b>Band 7</b>       | DUT02         | Done | Done | Done  | DUT does not support           |
+|                     | DUT05         | Done | Done | Done  | Done                           |
+|                     | DUT06         | Done | Done | Done  | Done                           |
+| <b>Band 7 ADTF</b>  | DUT05         | Done | Done | Done  | Done                           |
+| <b>Band 41</b>      | DUT07         | Done | Done | Done  | RTS does not support TDD bands |
+|                     | DUT08         | Done | Done | Done  |                                |
+|                     | DUT09         | Done | Done | Done  |                                |
+| <b>Band 41 ADTF</b> | DUT08         | Done | Done | Done  |                                |
+
+**Table 10.3.2-2: Devices used in the harmonization testing campaign: device set 2**
+
+|                |       | MPAC | RC   | RC+CE | RTS                            |
+|----------------|-------|------|------|-------|--------------------------------|
+| <b>Band 13</b> | KS1   | Done | Done | Done  | Done                           |
+|                | KS2   | Done | Done | Done  | Done                           |
+| <b>Band 7</b>  | KS2   | Done | Done | Done  | Done                           |
+|                | SP1   | Done | Done | Done  | DUT does not support           |
+| <b>Band 41</b> | CMCC1 | Done | Done | Done  | DUT does not support TDD bands |
+
+**Table 10.3.2-3: Devices used in the harmonization testing campaign: device set 3**
+
+|                |       | MPAC | RC+CE | RTS                  |
+|----------------|-------|------|-------|----------------------|
+| <b>Band 13</b> | PAD2  | Done | Done  | Done                 |
+|                | KS1   | Done | Done  | Done                 |
+|                | KS2   | Done |       | Done                 |
+|                | KS3   | Done |       | Done                 |
+|                | RS3   | Done | Done  | Done                 |
+|                | RS4   | Done | Done  | Done                 |
+|                | RS5   | Done | Done  | Done                 |
+|                | RS6   | Done | Done  | Done                 |
+| <b>Band 5</b>  | PAD2  | Done | Done  | Done                 |
+|                | KS1   | Done | Done  | Done                 |
+|                | KS2   | Done | Done  | Done                 |
+|                | KS3   | Done | Done  | Done                 |
+|                | RS3   | Done | Done  | Done                 |
+|                | RS4   | Done | Done  | Done                 |
+|                | RS5   | Done | Done  | Done                 |
+| <b>Band 3</b>  | PAD2  | Done | Done  | Done                 |
+|                | KS1   | Done | Done  | Done                 |
+|                | KS2   | Done | Done  | Done                 |
+|                | KS3   | Done | Done  | Done                 |
+|                | RS3   | Done | Done  | Done                 |
+|                | RS4   | Done | Done  | Done                 |
+|                | RS5   | Done | Done  | Done                 |
+|                | RS6   | Done | Done  | Done                 |
+| <b>Band 7</b>  | PAD2  | Done | Done  | Done                 |
+|                | KS1   | Done | Done  | Done                 |
+|                | KS2   | Done | Done  | Done                 |
+|                | KS3   | Done | Done  | Done                 |
+|                | RS3   | Done | Done  | Done                 |
+|                | RS4   | Done | Done  | Done                 |
+|                | RS5   | Done | Done  | Done                 |
+|                | RS6   | Done | Done  | Done                 |
+| <b>Band 38</b> | BT1   | Done | Done  | DUT does not support |
+|                | CTTC1 | Done | Done  |                      |
+|                | CTTC2 | Done | Done  |                      |
+| <b>Band 41</b> | BT1   | Done | Done  |                      |
+|                | CTTC1 | Done | Done  |                      |
+|                | CTTC2 | Done | Done  |                      |
+
+### 10.3.3 Measurement uncertainty bound for harmonization
+
+For the harmonization analysis of device set 3, the target cost of harmonization, assuming 100% statistical significance of the sample size, is set to be 1.5 dB. The measure of the statistical significance based on the total number of devices used in determining the residuals is provided in Table 10.3.3-1 below.
+
+**Table 10.3.3-1: Statistical significance of using m devices**
+
+| Num devices (m) | Target pct |
+|-----------------|------------|
+| 30              | 99.99      |
+| 8               | 79.37      |
+| 7               | 76.78      |
+| 6               | 72.72      |
+| 5               | 67.33      |
+| 4               | 58.26      |
+| 3               | 44.74      |
+| 2               | 29.26      |
+| 1               | 14.3       |
+| 0               | 0          |
+
+For the harmonization analysis of device set 3, the assessed measurement uncertainty of the single test laboratory in which the harmonization campaign was performed is listed in Table 10.3.3-2.
+
+**Table 10.3.3-2: Assessed measurement uncertainty**
+
+| Method | Assessed MU |
+|--------|-------------|
+| RC+CE  | 1.90        |
+| RTS    | 1.54        |
+| MPAC   | 1.91        |
+
+### 10.3.4 Summary of results
+
+Harmonization evaluations across methodologies are carried out by defining harmonization options. Table 10.3.4-1 below lists harmonization options and their associated parameters.
+
+**Table 10.3.4-1: Harmonization options**
+
+| Option                                      | Channel models                                                               | MPAC/RTS positions                   | Averaging type |
+|---------------------------------------------|------------------------------------------------------------------------------|--------------------------------------|----------------|
+| C                                           | UMi, NIST, LCLD                                                              | AVG {P 45,L 45,P 90}                 | inverse        |
+| D                                           | UMi, NIST, LCLD                                                              | AVG {P 45,L 45,P 90}                 | linear         |
+| G<br>(3 orientations)                       | UMa, UMi, NIST, LCSD, HCLD<br>NIST is compared to both UMa/HCLD and UMi/LCSD | AVG {P 45,L 45,P 90}                 | linear         |
+| G<br>(2 orientations<br>P45, L45)           | UMa, UMi, NIST, LCSD, HCLD<br>NIST is compared to both UMa/HCLD and UMi/LCSD | AVG {P 45,L 45}                      | linear         |
+| G<br>(1 orientation, all<br>3 combinations) | UMa, UMi, NIST, LCSD, HCLD<br>NIST is compared to both UMa/HCLD and UMi/LCSD | 1 orientation,<br>all 3 combinations | linear         |
+| H<br>(3 orientations)                       | UMa, UMi, NIST, LCSD, HCLD                                                   | AVG {P 45,L 45,P 90}                 | inverse        |
+| I                                           | UMa, NIST, HCLD                                                              | AVG {P 45,L 45,P 90}                 | linear         |
+| J                                           | UMa, NIST, HCLD                                                              | AVG {P 45,L 45,P 90}                 | inverse        |
+| K                                           | UMi, LCSD                                                                    | AVG {P 45,L 45,P 90}                 | inverse        |
+
+For each option, each band, and each pair of methodologies (i.e. MPAC/RC, MPAC/RC+CE, and MPAC/RTS), harmonization offsets are selected and harmonization residuals are calculated. Table 10.3.4-2 below lists the harmonized MU terms (h), within the parameters of each option. In this table the inter-methodology offsets were optimized across the measurements obtained from device set 1 and device set 2 at 70% throughput. For Option K the RC+CE testing procedure utilized 120 stirring states with 400 subframes per stirring state.
+
+**Table 10.3.4-2: Harmonized MU (h) with offsets optimized across UEs from device set 1 and device set 2**
+
+| Option                                      | Band    | RC&MPAC | RC+CE/MPAC | RTS/MPAC |
+|---------------------------------------------|---------|---------|------------|----------|
+| C                                           | Band 13 | 4.2     | 4.2        | 3.1      |
+|                                             | Band 7  | 3.2     | 3.4        | 3.1      |
+|                                             | Band 41 | 2.9     | 3.6        |          |
+| D                                           | Band 13 | 4.4     | 4.4        | 3.4      |
+|                                             | Band 7  | 3.4     | 3.4        | 3.1      |
+|                                             | Band 41 | 2.9     | 3.6        |          |
+| G<br>(3 orientations)                       | Band 13 | 7.2     | 4.6        | 3.6      |
+|                                             | Band 7  | 5.9     | 3.5        | 3.3      |
+|                                             | Band 41 | 6.1     | 4.3        |          |
+| G<br>(2 orientations<br>P45, L45)           | Band 13 | 7.3     | 4.9        | 3.3      |
+|                                             | Band 7  | 5.9     | 4.3        | 3.8      |
+|                                             | Band 41 | 6.4     | 4.5        |          |
+| G<br>(1 orientation, all<br>3 combinations) | Band 13 | 8.2     | 5.7        | 4.4      |
+|                                             | Band 7  | 6.8     | 5.7        | 4.9      |
+|                                             | Band 41 | 7.7     | 5.5        |          |
+| H<br>(3 orientations)                       | Band 13 | 7.0     | 4.6        | 3.1      |
+|                                             | Band 7  | 8.9     | 3.9        | 3.8      |
+|                                             | Band 41 | 6.1     | 4.2        |          |
+| I                                           | Band 13 | 4.6     | 4.5        | 3.6      |
+|                                             | Band 7  | 3.3     | 2.9        | 3.3      |
+|                                             | Band 41 | 3.5     | 4.1        |          |
+| J                                           | Band 13 | 4.5     | 4.5        | 3.0      |
+|                                             | Band 7  | 3.8     | 3.5        | 3.8      |
+|                                             | Band 41 | 3.4     | 4.2        |          |
+
+Table 10.3.4-3 below lists the robustness bias terms (b). In this table the inter-methodology offsets were optimized only across the measurements obtained from device set 1 at 70% throughput.
+
+**Table 10.3.4-3: Robustness bias terms (b) without optimizing offsets after UEs from device set 2 were added**
+
+| Option                                      | Band    | RC&MPAC | RC+CE/MPAC | RTS/MPAC |
+|---------------------------------------------|---------|---------|------------|----------|
+| C                                           | Band 13 | 1.3     | 2.7        | 0.8      |
+|                                             | Band 7  | 0.0     | 0.5        | 0.1      |
+|                                             | Band 41 | 0.0     | 1.2        |          |
+| D                                           | Band 13 | 1.0     | 2.3        | 1.0      |
+|                                             | Band 7  | 0.2     | 0.4        | 0.2      |
+|                                             | Band 41 | 0.0     | 1.1        |          |
+| G<br>(3 orientations)                       | Band 13 | 0.8     | 2.1        | 0.2      |
+|                                             | Band 7  | 0.0     | 0.4        | 0.1      |
+|                                             | Band 41 | 0.0     | 1.2        |          |
+| G<br>(2 orientations<br>P45, L45)           | Band 13 | 0.0     | 3.6        | 0.6      |
+|                                             | Band 7  | 0.0     | 0.9        | 0.0      |
+|                                             | Band 41 | 0.7     | 1.1        |          |
+| G<br>(1 orientation, all<br>3 combinations) | Band 13 | 0.0     | 0.3        | 1.1      |
+|                                             | Band 7  | 0.0     | 0.2        | 0.0      |
+|                                             | Band 41 | 0.0     | 0.4        |          |
+| H<br>(3 orientations)                       | Band 13 | 1.5     | 2.9        | 0.0      |
+|                                             | Band 7  | 0.0     | 0.1        | 0.0      |
+|                                             | Band 41 | 0.3     | 1.2        |          |
+| I                                           | Band 13 | 0.8     | 2.2        | 1.0      |
+|                                             | Band 7  | 0.0     | 0.4        | 0.0      |
+|                                             | Band 41 | 0.0     | 1.6        |          |
+| J                                           | Band 13 | 1.5     | 3.0        | 0.2      |
+|                                             | Band 7  | 0.0     | 0.3        | 0.0      |
+|                                             | Band 41 | 0.4     | 2.4        |          |
+
+Table 10.3.4-4 below lists the delta of residuals between 70% and 95% throughput. In this table the inter-methodology offsets were optimized across the measurements obtained from device set 1 and device set 2 at 70% throughput.
+
+**Table 10.3.4-4: Delta of residuals (r) between 95% and 70% throughput**
+
+| Option                                      | Band    | RC&MPAC | RC+CE/MPAC | RTS/MPAC |
+|---------------------------------------------|---------|---------|------------|----------|
+| C                                           | Band 13 | 0.4     | -0.4       | 0.0      |
+|                                             | Band 7  | 1.6     | -0.1       | -0.1     |
+|                                             | Band 41 | 2.0     | -0.6       | 0.0      |
+| D                                           | Band 13 | 0.7     | -0.4       | 0.4      |
+|                                             | Band 7  | 1.6     | 0.1        | 0.1      |
+|                                             | Band 41 | 2.1     | -0.4       | 0.0      |
+| G<br>(3 orientations)                       | Band 13 | 1.1     | -0.4       | 0.2      |
+|                                             | Band 7  | 1.7     | 0.1        | -0.1     |
+|                                             | Band 41 | 1.9     | -0.4       | 0.0      |
+| G<br>(2 orientations<br>P45, L45)           | Band 13 | -0.3    | -0.3       | 0.0      |
+|                                             | Band 7  | 1.8     | -0.3       | 0.0      |
+|                                             | Band 41 | 2.9     | -0.2       | 0.0      |
+| G<br>(1 orientation, all<br>3 combinations) | Band 13 |         |            |          |
+|                                             | Band 7  |         |            |          |
+|                                             | Band 41 |         |            |          |
+| H<br>(3 orientations)                       | Band 13 | 0.6     | -0.4       | 0.1      |
+|                                             | Band 7  | 1.8     | 0.2        | -0.1     |
+|                                             | Band 41 | 1.4     | -0.3       | 0.0      |
+| I                                           | Band 13 | 1.1     | -0.1       | 0.2      |
+|                                             | Band 7  | 1.7     | -0.2       | -0.1     |
+|                                             | Band 41 | 1.9     | -0.6       | 0.0      |
+| J                                           | Band 13 | 0.6     | -0.4       | 0.2      |
+|                                             | Band 7  | 1.8     | -0.1       | -0.1     |
+|                                             | Band 41 | 1.4     | -0.3       | 0.0      |
+
+Table 10.3.4-5 below list the informational flags.
+
+**Table 10.3.4-5: Informational Flags**
+
+| <b>Informational Flags (UEs from device set 1)</b> |                                                                                                                                                                                                                                                                                                                                                                                              |
+|----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| UE                                                 | Flag                                                                                                                                                                                                                                                                                                                                                                                         |
+| Z3                                                 | RC&CE: Z3 did not reach 95% TP for 1/120 states for UMa channel model in Band 13                                                                                                                                                                                                                                                                                                             |
+| Z3                                                 | RC&CE: Z3 did not reach 95% TP for 2/120 states for UMa channel model in Band 7                                                                                                                                                                                                                                                                                                              |
+| S5                                                 | RC&CE: S5 did not reach 95% TP for 1/120 states for UMa channel model in Band 41                                                                                                                                                                                                                                                                                                             |
+| <b>Informational Flags (UEs from device set 2)</b> |                                                                                                                                                                                                                                                                                                                                                                                              |
+| UE                                                 | Flag                                                                                                                                                                                                                                                                                                                                                                                         |
+| KS1                                                | MPAC: In Band 13, KS1 did not reach 95% TP in 1/12 AZ positions in Landscape 45 orientation                                                                                                                                                                                                                                                                                                  |
+| KS1                                                | MPAC: In Band 13, KS1 did not reach 95% TP in 4/12 AZ positions in Portrait 90 orientation                                                                                                                                                                                                                                                                                                   |
+| KS1                                                | RTS: In Band 7, KS1 did not reach 95% TP in 6/12 AZ positions in Portrait 45 orientation, in 4/12 AZ positions in Portrait 90 orientation, and in 5/12 AZ positions in Landscape 45 orientation                                                                                                                                                                                              |
+| KS1                                                | RTS: In Band 7, KS1 did not reach 95% TP in 2/12 AZ positions in Portrait 45 orientation                                                                                                                                                                                                                                                                                                     |
+| KS2                                                | RTS: In Band 13, KS2 did not reach 95% TP in 12/12 AZ positions in P45 orientation and 3/12 AZ positions in L45 orientation for UMa channel model                                                                                                                                                                                                                                            |
+| KS2                                                | RC+CE: In Band 13, KS2 did not reach 95% TP in 4/120 stirring modes for UMa channel model                                                                                                                                                                                                                                                                                                    |
+| SP1                                                | MPAC: In Band 7, SP1 did not reach 70% TP in 10/12 AZ positions in P45, in 11/12 AZ positions in P90, an 12/12 AZ positions in L45 orientation for UMa channel model                                                                                                                                                                                                                         |
+| SP1                                                | MPAC: In Band 7, SP1 did not reach 95% TP in 12/12 AZ positions in all three orientations (P45, P90, L45) for UMa channel model                                                                                                                                                                                                                                                              |
+| SP1                                                | RC+CE: In Band 7, SP1 did not reach 70% and 95% TP in 120/120 stirring modes for UMa channel model                                                                                                                                                                                                                                                                                           |
+| SP1                                                | RC+CE: In Band 7, SP1 did not reach 70% and 95% TP in 120/120 stirring modes for UMa channel model                                                                                                                                                                                                                                                                                           |
+| <b>Additional Flags</b>                            |                                                                                                                                                                                                                                                                                                                                                                                              |
+| UE                                                 | Flag                                                                                                                                                                                                                                                                                                                                                                                         |
+| SP1                                                | As this device did not achieve 70% in many cases, further analysis of the raw data using throughput averaging was performed to estimate the performance delta in dB between MPAC and RC+CE. The deltas are as follows after applying the optimized fixed offsets.<br>RC+CE to MPAC difference at 12.5Mbps:<br>P45: -11 dB<br>P90: -14 dB<br>L45: +18.5 dB<br>Average(P45,P90,L45): -11.75 dB |
+| KS2                                                | B13 UMa – RTS does not provide a 95% outage while MPAC does – This is probably due to subtle differences in the channel conditions for a device near its limit                                                                                                                                                                                                                               |
+| KS1                                                | B13 UMa – MPAC does not provide a 95% outage while RTS does – This was due to too low a starting power to try to save test time                                                                                                                                                                                                                                                              |
+| KS1                                                | B7 UMi – RTS does not provide a 95% outage while MPAC does                                                                                                                                                                                                                                                                                                                                   |
+| KS1                                                | B7 UMa – RTS does not provide a 95% outage while MPAC does – This is due to insufficient power from the amplifier for this particularly bad device                                                                                                                                                                                                                                           |
+
+Devices in device set 3 were analysed according to harmonization option K. Table 10.3.4-6 below provides a summary of the harmonization analysis.
+
+**Table 10.3.4-6: Harmonization analysis summary with device set 3**
+
+| <b>Band</b> | <b>DL Fc (MHz)</b> | <b>Method 2</b> | <b>Offsets</b> | <b>num r</b> | <b>Harm target</b> | <b>Ref MU</b> | <b>M2 MU</b> | <b>r_70%</b> | <b>r_95%</b> | <b>h</b> | <b>Harmonization cost</b> |
+|-------------|--------------------|-----------------|----------------|--------------|--------------------|---------------|--------------|--------------|--------------|----------|---------------------------|
+| 13          | 751.0              | RC+CE           | 1.95           | 6            | 1.09               | 1.91          | 1.90         | 2.22         | 2.23         | 4.30     | 2.22                      |
+| 5           | 881.5              | RC+CE           | 4.61           | 7            | 1.15               | 1.91          | 1.90         | 1.20         | 1.20         | 3.27     | 1.19                      |
+| 3           | 1842.5             | RC+CE           | 4.19           | 8            | 1.19               | 1.91          | 1.90         | 2.33         | 2.34         | 4.41     | 2.33                      |
+| 7           | 2655.0             | RC+CE           | 4.66           | 8            | 1.19               | 1.91          | 1.90         | 2.29         | 2.59         | 4.66     | 2.58                      |
+| 41          | 2595.0             | RC+CE           | 5.63           | 3            | 0.67               | 1.91          | 1.90         | 0.38         | 0.38         | 2.45     | 0.37                      |
+| 38          | 2593.0             | RC+CE           | 5.64           | 3            | 0.67               | 1.91          | 1.90         | 0.60         | 0.61         | 2.68     | 0.60                      |
+| 13          | 751.0              | RTS             | 0.00           | 8            | 1.19               | 1.91          | 1.54         | 0.64         | 0.91         | 2.45     | 0.54                      |
+| 5           | 881.5              | RTS             | 0.00           | 7            | 1.15               | 1.91          | 1.54         | 0.87         | 0.73         | 2.41     | 0.50                      |
+| 3           | 1842.5             | RTS             | 0.00           | 8            | 1.19               | 1.91          | 1.54         | 0.79         | 0.97         | 2.51     | 0.60                      |
+| 7           | 2655.0             | RTS             | 0.00           | 8            | 1.19               | 1.91          | 1.54         | 0.98         | 1.29         | 2.83     | 0.92                      |
+
+### 10.3.5 Harmonization outcome
+
+Harmonization cost has been calculated among the options in Table 10.3.4-1 and is defined as  $c = \max(h\_B7, h\_B13, h\_B41) - m\_MPAC$ . Table 10.3.5-1 below lists the cost values per option and methodology combination.
+
+**Table 10.3.5-1: Harmonization cost**
+
+| <b>Option</b>                                                    | <b>RC&amp;MPAC</b> | <b>RC+CE&amp;MPAC</b> | <b>RTS&amp;MPAC</b> | <b>RC+CE&amp;RTS&amp;MPAC</b> | <b>RC&amp;RC+CE&amp;RTS&amp;MPAC</b> |
+|------------------------------------------------------------------|--------------------|-----------------------|---------------------|-------------------------------|--------------------------------------|
+| C                                                                | 1.6                | 1.6                   | 0.5                 | 1.6                           | 1.6                                  |
+| D                                                                | 1.8                | 1.8                   | 0.7                 | 1.8                           | 1.9                                  |
+| G (3 orientations)                                               | 4.5                | 2                     | 1                   | 2                             | 4.5                                  |
+| G (2 orientations P45, L45)                                      | 4.9                | 2.3                   | 1.2                 | 2.3                           | 4.9                                  |
+| G (1 orientation, all 3 combinations)                            | 5.5                | 3.2                   | 2.3                 | 4                             | 6.6                                  |
+| H (3 orientations)                                               | 4.4                | 2                     | 1.2                 | 2                             | 4.4                                  |
+| I                                                                | 2                  | 1.8                   | 1                   | 1.8                           | 2                                    |
+| J                                                                | 1.9                | 1.9                   | 1.2                 | 1.9                           | 1.9                                  |
+| NOTE: RTS cannot test TDD (as of today) and requires UE support. |                    |                       |                     |                               |                                      |
+
+Additionally, as offsets were optimized for 70% throughput, a check is made at 95% to determine the change in the residuals (r). Table 10.3.5-2 below lists the cost check values per option and methodology combination.
+
+**Table 10.3.5-2: Harmonization cost check at 95% outage**
+
+| Option             | RC&MPAC | RC+CE&MPAC | RTS&MPAC | RC+CE&RTS&MPAC | RC&RC+CE&RTS&MPAC |
+|--------------------|---------|------------|----------|----------------|-------------------|
+| C                  | 1.9     | 0          | 0        | 0              | 1.4               |
+| D                  | 2.1     | 0.1        | 0.4      | 0.1            | 1.6               |
+| G (3 orientations) | 1.9     | 0.1        | 0.2      | 0.1            | 1.7               |
+| G (2 orientations) | 2.5     | -0.2       | 0        | -0.3           | 1.8               |
+| H (3 orientations) | 1.7     | 0.1        | 0.1      | 0.1            | 1.7               |
+| I                  | 1.9     | -0.1       | 0.2      | -0.1           | 1.7               |
+| J                  | 1.8     | -0.1       | 0.2      | -0.1           | 1.7               |
+
+The following agreements have been made:
+
+- Final harmonization cannot be successfully claimed. But potential for harmonization can be found. In this situation, a single method shall be selected according to WID, while work on improving harmonization is deemed possible and needed
+- Select MPAC methodology, and start new activity on performance requirement phase for MPAC
+- Select UMi channel model, and inverse averaging. Option C
+- Select the following KPIs: 70% and 95%
+- How to treat failing of devices:
+  - For 95% tput: 2 orientations/azimuth rotations that fail are allowed. If more orientations fail then device fails test
+  - For 70% tput: 1 orientation /azimuth rotations that fail is allowed. If more orientations fail then device fails test
+- Start follow-up harmonization activity in parallel to Performance requirement activity above, for the pair or pairs of methods that have potential harmonization
+  - This follow-up activity will increase the number of devices to be tested with the aim to augment and improve harmonization
+  - This follow-up activity will also increase the bands to be considered for harmonization
+  - Add UMa only option (Option J) for harmonization it in this follow-up harmonization activity which will be tested in parallel to UMi harmonization. UMa is not excluded from future performance work
+- Due to robustness check at 95%, methods involving RC-only shall not be considered
+- RC+CE&MPAC, RTS&MPAC and RC+CE&RTS&MPAC shall be considered in the harmonization activity
+- Everything can be done in the same WI
+- Bands for performance requirement definition activity: 1,2,3,4,5,7, 8,12,13,19,20,28,32,38,40,41,42,46
+- The first set of bands to define requirements for and to perform harmonization activity are 2 FDD low bands, 2 FDD high bands and 2 TDD bands
+- if harmonization fails for a particular set of corresponding channel models, then that method is not applicable for testing in that particular set of corresponding channel model
+- Sample size for performance requirement: 100 measurements as a minimum
+
+14. How to claim new harmonization activity is successful
+
+1. Same bands (or set) as in the performance activity will be addressed in the same order, and harmonization will be checked after the performance requirement for each band (or set) is finalized.
+2. How many measurements samples per band: 30 of devices used for Performance requirement phase will be used for this harmonization activity. And tested in the same lab to minimize MUs with a controlled environment
+
+15. Add Rayleigh validation procedure for RC+CE method
+
+The following open items have been identified:
+
+1. Study how to perform averaging across orientations that did not fail the KPI
+2. Add how to extend the concept of devices failing in MPAC as agreed in slide 5 to RC+CE method
+3. Development of the procedure to validate Rayleigh
+4. Think what happens if we don't find a single lab with a controllable environment
+5. Include statistical analysis to determine when to stop testing more devices for harmonization
+6. Study how to find the offset
+7. Study the distribution of residuals when analysing the cost
+8. Study how to calculate the cost and threshold
+
+#### 10.3.5a Harmonization outcome with device set 3
+
+RAN4 has reviewed harmonization analyses and has drawn the following conclusions regarding the MPAC/RC+CE harmonization outcome:
+
+1. For the TDD bands tested in the MPAC/RC+CE harmonization, the harmonization cost varies between 0.37 and 0.60 dB. This harmonization cost is within the lowest harmonization target for all TDD bands considering the statistical significance. Because only 3 devices were used to determine the offsets, harmonization between MPAC and RC+CE for Bands 38 and 41 should be further investigated. Testing 5 more devices in the chosen TDD bands in Lab3 can help to evaluate the harmonization offsets and the harmonization cost for TDD.
+2. For all FDD bands tested in the MPAC/RC+CE harmonization, the harmonization cost varies between 1.19 and 2.58 dB; some bands exceed their highest harmonization bound and, therefore, harmonization between MPAC and RC+CE cannot be confirmed for all FDD bands based on the results available from the harmonization testing campaign.
+3. The potential to harmonize in FDD has been observed by isolating devices which have contributed to higher residual errors, particularly LNA-active devices, defining the related applicability criteria, and investigating more suitable RC+CE settings and harmonization formulas.
+
+RAN4 has reviewed harmonization analyses and has drawn the following conclusions regarding the MPAC/RTS harmonization outcome:
+
+1. For the FDD bands tested in the MPAC/RTS harmonization, the harmonization cost varies between 0.5 and 0.92 dB. This harmonization cost is within the harmonization target for all bands and, therefore, harmonization between MPAC and RTS for Bands 13, 5, 3, and 7 can be confirmed.
+2. Considering the positive outcome of the MPAC/RTS harmonization analysis, the following applicability criteria for the MPAC/RTS harmonization are proposed based on the current understanding of the RTS methodology capabilities:
+
+- a. The harmonized RTS system is a two probe system capable of measuring devices with two Rx antennas. Devices with more Rx antennas are not supported.
+- b. The RTS method is only applicable to devices which do not change their antenna pattern in response to the radio environment.
+- c. The RTS method requires device support for the antenna test function (ATF) defined in TR 36.978. The ATF access of devices depends on the support of chip vendors.
+- d. There are two methods defined for ATF access, L3 signalling or a vendor-supplied device app. The devices used for harmonization were all modified to install the special ATF application. Harmonization has been confirmed using devices with the special ATF application. Harmonization for unmodified devices using the L3 access has not been confirmed.
+- e. RTS is harmonized for FDD bands. TDD harmonization has not been evaluated.
+- f. Harmonization measurements for RTS were performed with correlation based channel models; harmonization and channel model validation limits would need to be confirmed for geometric based channel models.
+
+#### 10.3.5b Harmonization outcome with device set 4
+
+In view of the applicability statements in subclause 10.3.5a relating to the evaluation of L3 access and TDD, two further devices were evaluated.
+
+**Table 10.3.5b-1: Comparison for device A of RTS using L3 ATF vs. MPAC for UMi in TDD band 41**
+
+| Orientation | Method     | Threshold |        |        |
+|-------------|------------|-----------|--------|--------|
+|             |            | 70 %      | 90 %   | 95 %   |
+| P +45       | RTS        | -99.5     | -98    | -97.23 |
+|             | MPAC       | -98.66    | -97.16 | -96.41 |
+|             | Difference | 0.84      | 0.84   | 0.82   |
+| L +45       | RTS        | -97.13    | -95.65 | -94.92 |
+|             | MPAC       | -97.69    | -96.23 | -95.54 |
+|             | Difference | -0.56     | -0.58  | -0.62  |
+| P +90       | RTS        | -96.47    | -94.92 | -94.1  |
+|             | MPAC       | -96.51    | -94.92 | -94.17 |
+|             | Difference | -0.04     | 0.00   | -0.07  |
+| TRMS        | RTS        | -97.70    | -96.19 | -95.42 |
+|             | MPAC       | -97.62    | -96.10 | -95.37 |
+|             | Difference | 0.08      | 0.09   | 0.04   |
+
+**Table 10.3.5b-2: Comparison for device B of RTS using Application-based ATF reporting vs. MPAC for UMi in TDD band 41**
+
+| Orientation  | Method     | Threshold |         |        |
+|--------------|------------|-----------|---------|--------|
+|              |            | 70 %      | 90 %    | 95 %   |
+| P +45        | RTS        | -101.8    | -100.28 | -99.45 |
+|              | MPAC       | -101.59   | -100.14 | -99.43 |
+|              | Difference | 0.21      | 0.14    | 0.02   |
+| L +45        | RTS        | -101.44   | -99.93  | -99.16 |
+|              | MPAC       | -100.71   | -99.26  | -98.49 |
+|              | Difference | 0.73      | 0.67    | 0.67   |
+| Partial TRMS | RTS        | -101.62   | -100.11 | -99.31 |
+|              | MPAC       | -101.15   | -99.70  | -98.96 |
+|              | Difference | 0.47      | 0.41    | 0.34   |
+
+**Table 10.3.5b-3: Comparison for device D of RTS using L3 ATF vs. MPAC for UMi in FDD band 4**
+
+| Orientation  | Method     | Threshold |        |        |
+|--------------|------------|-----------|--------|--------|
+|              |            | 70 %      | 90 %   | 95 %   |
+| <b>P +45</b> | RTS        | -98.54    | -97    | -96.19 |
+|              | MPAC       | -99.19    | -97.87 | -97.08 |
+|              | Difference | -0.65     | -0.87  | -0.89  |
+| <b>L +45</b> | RTS        | -99.27    | -97.74 | -96.98 |
+|              | MPAC       | -98.70    | -97.40 | -96.72 |
+|              | Difference | 0.57      | 0.34   | 0.26   |
+| <b>P +90</b> | RTS        | -95.56    | -94.14 | -93.43 |
+|              | MPAC       | -96.58    | -95.28 | -94.49 |
+|              | Difference | -1.02     | -1.14  | -1.06  |
+| <b>TRMS</b>  | RTS        | -97.79    | -96.29 | -95.53 |
+|              | MPAC       | -98.16    | -96.85 | -96.10 |
+|              | Difference | -0.37     | -0.56  | -0.56  |
+
+Based on this additional evaluation of L3 ATF reporting and five TDD S<sub>MODE</sub> results the applicability statements d and e from subclause 10.3.5a are modified as follows:
+
+- d. There are two methods defined for ATF access, L3 signalling or a vendor-supplied device app.  
+Harmonization has been confirmed using devices with the special ATF application and using the L3 access for both FDD and TDD.
+- e. RTS is harmonized for FDD and TDD bands.
+
+## 10.4 Lab alignment procedures for performance labs
+
+### 10.4.1 General
+
+Labs intending to contribute to the performance requirement part of the work shall complete the lab alignment measurements and report the results to RAN4 in the approved data format.
+
+### 10.4.2 Channel model validation data
+
+If the lab implements a commercial test solution for which the test solution provider has already submitted channel model validation data to RAN4 and which results have been included in TR 37.977, then a submission of the channel model validation data is not required.
+
+If the lab implements a commercial test solution for which the test solution provider has not yet submitted channel model validation data to RAN4, then the channel model validation data shall be provided by the solution provider. If the lab implements a custom test solution, then the lab (as the test solution provider) shall provide channel model validation data to RAN4, such that
+
+- The measurements are made according to the procedures described in Clause 8.3 of TR 37.977
+- Using the channel models defined in 8.1.1 of TS 37.144
+- The results are submitted to RAN4 as a CR to TR 37.977
+- The testing frequencies are the center frequencies corresponding to LTE bands 13 and 7
+
+### 10.4.3 Calibration with a specific set of reference dipoles
+
+A set of reference dipoles shall be used by the lab to perform the chamber range calibration in both the V and H polarizations as well as to verify the sum of the power in vertical and horizontal polarizations during the alignment activity. This set shall be shipped together with the alignment devices. Table 10.4.3-1 below lists the calibration reference antennas in the set.
+
+**Table 10.4.3-1: Calibration reference antennas**
+
+| Reference antenna ID | Reference antenna type | Operating Band | Availability | Current location |
+|----------------------|------------------------|----------------|--------------|------------------|
+| TBD                  | Sleeve dipole          | 13             | TBD          | TBD              |
+| TBD                  | Sleeve dipole          | 7              | TBD          | TBD              |
+
+For each operating band listed in Table 10.4.3-1, the lab shall report the measured power in the V polarization for the SCMe UMi channel model and, optionally, for the UMa channel model, as defined in 8.2 of TR 37.977.
+
+### 10.4.4 Performance alignment measurements
+
+The lab shall perform alignment measurements according to the following parameters:
+
+- Using the performance alignment devices (PAD) and bands listed in Table 10.4.4-1.
+- Using the testing conditions as defined in 8.1.1 of TS 37.144.
+- Recording and reporting the measured data in the agreed spreadsheet format.
+
+**Table 10.4.4-1: Performance alignment devices (PAD)**
+
+| UE    | Operating Band(s) | Availability | Current location |
+|-------|-------------------|--------------|------------------|
+| PAD_2 | FDD7, FDD13       | Now          | USA              |
+| PAD_3 | TDD41             | TBD          | TBD              |
+| PAD_4 | TDD41             | TBD          | TBD              |
+| PAD_5 | FDD7, FDD13       | TBD          | TBD              |
+
+Total tests with the PAD set: 6 device-band combinations x 3 orientations = 18 tests.
+
+Optionally, the lab may perform additional alignment measurements according to the following parameters:
+
+- Using the additional alignment devices (AAD), bands, and UE orientations listed in Table 10.4.4-2.
+- Using the SCMe UMa channel model as defined in 8.2 of TR 37.977.
+- Recording and reporting the measured data in the agreed spreadsheet format.
+
+**Table 10.4.4-2: Additional alignment devices (AAD) with UMa**
+
+| UE    | Operating Band | UE orientation | Availability | Current location |
+|-------|----------------|----------------|--------------|------------------|
+| AAD_1 | FDD7           | L0 & P0        | Now          | Europe           |
+| AAD_2 | FDD13          | P0 & Face Down | Now          | Europe           |
+| AAD_3 | FDD13          | P0 & L -45     | Now          | USA              |
+
+Total tests with the AAD set: 3 device-band combinations x 2 orientations = 6 tests.
+
+The alignment procedures are applicable to MPAC.
+
+### 10.4.5 Acceptance criteria
+
+The criteria for accepting the outcome of the lab alignment activity for a given lab are listed in Table 10.4.5-1 below.
+
+**Table 10.4.5-1: Performance alignment acceptance criteria**
+
+| Aspect                   | Case                 | Band   | Acceptance criterion                                                                   |
+|--------------------------|----------------------|--------|----------------------------------------------------------------------------------------|
+| Channel model validation | PDP                  | {13,7} | 8.4.6                                                                                  |
+|                          | Temporal correlation | {13,7} | 8.4.6                                                                                  |
+|                          | Spatial correlation  | {13,7} | 8.4.6                                                                                  |
+|                          | Cross-polarization   | {13,7} | 8.4.6                                                                                  |
+| Power verification       | (V) for UMi          | {13,7} | TBD                                                                                    |
+| PAD                      | PAD_5                | 13     | Maximum deviation of $S_{Mode,x} \leq 1.0$ dB,<br>Maximum deviation of $TRMS \leq TBD$ |
+|                          | PAD_5                | 7      |                                                                                        |
+|                          | PAD_2                | 13     |                                                                                        |
+|                          | PAD_2                | 7      |                                                                                        |
+|                          | PAD_3                | 41     |                                                                                        |
+|                          | PAD_4                | 41     |                                                                                        |
+
+# 11 Void
+
+# 12 MIMO OTA test procedures
+
+## 12.1 Anechoic chamber method with multiprobe configuration test procedure
+
+### 12.1.1 Base Station configuration
+
+The SS parameter settings shall be set according to Clause 7.1.
+
+The emulated antenna array configuration shall be set according to Clause 8.5.
+
+### 12.1.2 Channel Models
+
+The applicable channel models are defined in Clause 8.2.
+
+### 12.1.3 Device positioning and environmental conditions
+
+The positioning of the device under test within the test volume shall be set as defined in Clause 9.4.
+
+The environmental requirements for the device under test shall be set as defined in Annex D.
+
+### 12.1.4 System Description
+
+#### 12.1.4.1 Solution Overview
+
+The setup described in Clause 6.3.1.1 shall be used.
+
+#### 12.1.4.2 Configuration
+
+The concept and configuration of the test setup is given in Clause 6.3.1.1.1.
+
+#### 12.1.4.3 Calibration
+
+The calibration procedure is specific to the test concept and configuration, therefore is unique for each implementation. The calibration procedure shall be documented by each lab, with enough details to allow third party verification. Examples for signal level calibration are given in Annex F.
+
+### 12.1.5 Figure of Merit
+
+The performance metric is given in Clause 5.
+
+### 12.1.6 Test procedure
+
+#### 12.1.6.1 Initial conditions
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+1. Ensure environmental requirements of Annex A are met.
+2. Configure the test system according to Clauses 12.1.1 and 12.1.2 for the applicable test case.
+3. Verify the implementation of the channel model as specified in Clause 12.1.2.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+4. Position the UE in the chamber according to Clause 12.1.3.
+5. Power on the UE.
+6. Set up the connection.
+
+#### 12.1.6.2 Test procedure
+
+The following steps shall be followed in order to evaluate MIMO OTA performance of the DUT:
+
+1. Measure MIMO OTA throughput from one measurement point. MIMO OTA throughput is the minimum downlink power (or SIR) resulting in a throughput value of 70% and 95% of the maximum theoretical throughput. The downlink power (or SIR) step size shall be no more than 0.5 dB when RF power level is near the LTE MIMO sensitivity level. Measurement duration shall be sufficient to achieve statistical significance that is TBD.
+
+NOTE 1: The initial RS EPRE can be set to the user's freely selectable level.
+
+Recommended initial RS EPRE is found in Tables 7.1-1 and 7.1-2. For the SIR control tests, ensure that the default signal level is set such that the target SIR values can be achieved when utilizing the SIR validation procedure defined in clause 5.1.2.1.
+
+NOTE 2: The throughput value target DL power level (or SIR) can be changed using user's freely selectable algorithm.
+
+NOTE 3: Assuming that the default signal level meets the criteria in NOTE 1, the interference level will be adjusted to achieve the target SIR.
+
+NOTE 4: For devices that do not reach target TP, the highest RS EPRE at which TP is measured shall be -80 dBm/15 kHz. The starting RS EPRE level of the LTE MIMO sensitivity level search does not need to be specified (NOTE 1)
+
+NOTE 5: For devices that exhibit non-linear TP behaviour and that achieve target throughput at multiple RF power levels, LTE MIMO sensitivity level is chosen to be lowest measured DL power level which crosses the target throughput level
+
+2. Rotate the UE around vertical axis of the test system by 30 degrees and repeat from step 1 until one complete rotation has been measured i.e. 12 different UE azimuth rotations.
+3. Repeat the test from step 1 for each specified device orientation. A list of orientations is given in Annex E.
+4. The postprocessing method to calculate the average MIMO Throughput is defined in 5.2.1.
+
+### 12.1.7 Measurement Uncertainty budget
+
+The measurement uncertainty budget for the test methodology is given in Annex B.
+
+## 12.2 Reverberation chamber test procedure
+
+### 12.2.1 Base Station configuration
+
+The SS parameter settings shall be set according to Clause 7.1.
+
+The emulated antenna array configuration shall be set according to Clause 8.5. For the isotropic channel model based on NIST, the base station antennas shall be uncorrelated.
+
+### 12.2.2 Channel Models
+
+The applicable channel models are defined in Annex C.
+
+### 12.2.3 Device positioning and environmental conditions
+
+The positioning of the device under test within the test volume shall be set as defined in Clause 9.4.
+
+The environmental requirements for the device under test shall be set as defined in Annex D.
+
+### 12.2.4 System Description
+
+#### 12.2.4.1 Solution Overview
+
+The setup described in Clause 6.3.2.1 or Clause 6.3.2.2 shall be used, depending on the applicable test case.
+
+#### 12.2.4.2 Configuration
+
+The concept and configuration of the test setup is given in Clause 6.3.2.1 or Clause 6.3.2.2, depending on the applicable test case.
+
+#### 12.2.4.3 Calibration
+
+The calibration procedure is specific to the test concept and configuration, therefore is unique for each implementation. The calibration procedure shall be documented by each lab, with enough details to allow third party verification. Examples for signal level calibration are given in Annex F.
+
+### 12.2.5 Figure of Merit
+
+The performance metric is given in Clause 5.
+
+### 12.2.6 Test procedure
+
+#### 12.2.6.1 Initial conditions
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+1. Ensure environmental requirements of Annex A are met.
+2. Configure the test system according to Clauses 12.2.1 and 12.2.2 for the applicable test case.
+3. Verify the implementation of the channel model as specified in Clause 12.2.2.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+4. Position the UE in the chamber according to Clause 12.2.3.
+5. Power on the UE.
+6. Set up the connection.
+
+#### 12.2.6.2 Test procedure
+
+The following steps shall be followed in order to evaluate MIMO OTA performance of the DUT:
+
+1. Generate a test signal by the SS. The SS transmits the signal through the test system to the DUT.
+2. Search for the minimum average DL RS EPRE (or SIR) level resulting in a MIMO OTA throughput of at least 70 % of the maximum theoretical throughput. The measurement procedure shall be based on sending a pre-defined number of subframes for each throughput sample for each DL RS EPRE (or SIR) level. When all samples have been collected for a specific DL RS EPRE (or SIR) level, the procedure is repeated for other DL RS EPRE (or SIR) levels. Alternatively, the search can be performed for each stirring combination and then average the RS EPRE (or SIR) levels when all throughput samples have been collected.
+
+NOTE 1: The initial RS EPRE (or SIR) can be set to the user's freely selectable level.
+
+Recommended initial RS EPRE is found in Tables 7.1-1 and 7.1-2. For the SIR control tests, ensure that the default signal level is set such that the target SIR values can be achieved when utilizing the SIR validation procedure defined in clauses 5.1.2.2 and 5.1.2.3.
+
+NOTE 2: To meet the throughput value target DL RS EPRE (or SIR) level can be changed using user's freely selectable algorithm.
+
+NOTE 3: The average throughput calculated from all samples collected for each RS EPRE (or SIR) level is reported as the MIMO OTA throughput.
+
+NOTE 4: The downlink RS EPRE (or SIR) step size shall be no more than 0.5 dB, when RF power level is near the MIMO OTA throughput sensitivity level.
+
+NOTE 5: Assuming that the default signal level meets the criteria in NOTE 1, the interference level will be adjusted to achieve the target SIR.
+
+3. The minimum average DL RS EPRE (or SIR) level that results in a MIMO OTA throughput of at least 70 % of the maximum theoretical throughput shall be reported.
+
+### 12.2.7 Measurement Uncertainty budget
+
+The measurement uncertainty budget for the test methodology is given in Annex B.
+
+## 12.3 RTS method test procedure
+
+### 12.3.1 Base Station configuration
+
+The SS parameter settings shall be set according to Clause 7.1.
+
+The emulated antenna array configuration shall be set according to Clause 8.5.
+
+### 12.3.2 Channel Models
+
+The applicable channel models are defined in Clauses 8.2 and Annex C.
+
+### 12.3.3 Device positioning and environmental conditions
+
+The positioning of the device under test within the test volume shall be set as defined in Clause 9.4.
+
+The environmental requirements for the device under test shall be set as defined in Annex D.
+
+### 12.3.4 System Description
+
+#### 12.3.4.1 Solution Overview
+
+The setup described in Clause 6.3.1.3 shall be used.
+
+Use of the RTS method for conformance test depends on the specification of the UE antenna test function which is defined in TR 36.978 [20].
+
+#### 12.3.4.2 Configuration
+
+The concept and configuration of the test setup is given in Clause 6.3.1.3.
+
+#### 12.3.4.3 Calibration
+
+The calibration procedure is specific to the test concept and configuration, therefore is unique for each implementation. The calibration procedure shall be documented by each lab, with enough details to allow third party verification. Examples for signal level calibration are given in Annex F.
+
+### 12.3.5 Figure of Merit
+
+The performance metric is given in Clause 5.
+
+### 12.3.6 Test procedure
+
+#### 12.3.6.1 Initial conditions
+
+Initial conditions are a set of test configurations the UE shall be tested in and the steps for the SS to take with the UE to reach the correct measurement state for each test case.
+
+1. Ensure environmental requirements of Annex A are met.
+2. Configure the test system according to Clauses 12.3.1 and 12.3.2 for the applicable test case.
+3. Verify the implementation of the channel model as specified in Clause 12.3.2.
+
+NOTE: The verification of the channel model implementation can be part of the laboratory accreditation process i.e. performed once for each channel model, and will remain valid as long as the setup and instruments remain unchanged. Otherwise the channel model validation may need to be performed prior to starting each throughput test.
+
+4. Position the UE in the chamber according to Clause 12.3.3.
+5. Power on the UE.
+6. Set up the connection.
+
+#### 12.3.6.2 Test procedure
+
+The following steps shall be followed in order to evaluate MIMO OTA performance of the DUT:
+
+1. Measure the DUT complex antenna pattern at a nominal -60 dBm downlink power as described in subclause 6.3.1.3 first stage.
+2. Select an appropriate orientation from the measured antenna pattern and establish a radiated MIMO connection to the DUT using the V and H probes as described in subclause 6.3.1.3 second stage. Measure the transmission matrix in the chamber and apply the inverse matrix to the MIMO signal. The DUT orientation at which this is done is selected to optimize the achievable isolation. The unknown gain of the DUT antennas represented by the absolute accuracy of the RSAP measurement is then de-embedded from the measured antenna pattern. This is done by comparing the RSAP measurement from the first stage at the orientation being used in the second stage, to a second RSAP measurement made in the second stage using a nominal signal of -60 dBm adjusted by the uncorrected antenna gain for that orientation. The difference in the RSAP measurements represents the true antenna gain for that orientation.
+3. With the desired channel model applied, measure the isolation in dB between each stream as seen by the DUT receiver and ensure it is at least 15 dB averaged over at least 200 RSAP measurements.
+4. Using the calibrated radiated connection validate monotonicity of the DUT RSAP and RSARP measurements over the range -60 dB, to -80 dBm and +/- 180 degrees. The step size for RSAP shall be [1] dB and the step size for RSARP shall be [5] degrees.
+5. Once monotonicity has been validated, check the linearity of RSAP at the orientation of the peak antenna gain over the range -60 dBm to -80 dBm is < [1] dB. Check the linearity of RSARP is within [5] degrees over the range +/- 180 degrees. If the uncorrected RSAP or RSARP results do not meet the linearity requirements, calculate and apply a transfer function to the measured patterns to ensure the necessary linearity.
+
+6. Convolve the antenna patterns from stage 1, linearized if necessary, with the channel model in the channel emulator and perform the throughput test.
+7. Record the throughput for each DUT orientation controlled by the channel emulator and each RS EPRE level.
+8. Identify and report the RS EPRE (or SIR) level achieving 70% throughput for averaged throughput.
+
+NOTE 1: The initial RS EPRE can be set to the user's freely selectable level.
+
+Recommended initial RS EPRE is found in Tables 7.1-1 and 7.1-2. For the SIR control tests, ensure that the default signal level is set such that the target SIR values can be achieved when utilizing the SIR validation procedure defined in clause 5.1.2.4.
+
+NOTE 2: To meet the throughput value target DL RS EPRE level can be changed using user's freely selectable algorithm.
+
+NOTE 3: Assuming that the default signal level meets the criteria in NOTE 1, the interference level will be adjusted to achieve the target SIR.
+
+### 12.3.7 Measurement Uncertainty budget
+
+The measurement uncertainty budget for the test methodology is given in Annex B.
+
+## 12.4 Comparison of methodologies
+
+The methodologies which tests plans are described Clause 12, can be broadly classified into 3 categories:
+
+- 1) Reverberation Chamber (RC);
+- 2) Anechoic Chamber (AC);
+- 3) Multi-stage Method.
+
+The content of the Table 12.4-1 is based on what has been validated as well as currently available state-of-the-art information, and may be reconsidered when the state of the art technology progresses.
+
+**Table 12.4-1: Simplified methodology comparison**
+
+| Attribute                                                                            | Reverberation Chamber                                    |                                                          | Anechoic Chamber                                                                                                                            | Multi-stage methods                                                |
+|--------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
+|                                                                                      | RC                                                       | RC + CE                                                  | Multi probe                                                                                                                                 | 2 stage method rad.                                                |
+| <b>Channel Modelling aspects</b>                                                     |                                                          |                                                          |                                                                                                                                             |                                                                    |
+| 2D/3D dimension over which the signals simultaneously arrive at the DUT location     | 3D <sup>1</sup>                                          | 3D <sup>1</sup>                                          | 2D                                                                                                                                          | 2D <sup>11</sup>                                                   |
+| Directional distribution of angles of arrival                                        | Random                                                   | Random                                                   | Selected as defined by SCME channel model in Clause 8                                                                                       | Selected as defined by SCME channel model in Clause 8              |
+| Channel model with controllable spatial characteristics                              | no                                                       | no                                                       | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| Angular spread                                                                       | Statistically isotropic                                  | Statistically isotropic                                  | Selected as defined by SCME channel model in Clause 8                                                                                       | Selected as defined by SCME channel model in Clause 8              |
+| Ability to control angular spread                                                    | no                                                       | no                                                       | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| Power delay profile                                                                  | Exponential decay                                        | Selected as defined by channel model in Annex C          | Selected as defined by SCME channel model in Clause 8                                                                                       | Selected as defined by SCME channel model in Clause 8              |
+| Ability to control power delay profile                                               | Partly controllable <sup>2,3</sup>                       | Yes <sup>2</sup>                                         | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| UE speed                                                                             | Approximately 1Km/h                                      | 30Km/h                                                   | 30Km/h                                                                                                                                      | 30Km/h                                                             |
+| Ability to control UE speed                                                          | No                                                       | Yes <sup>2</sup>                                         | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| UE direction of travel                                                               | N/A                                                      | N/A                                                      | 120° as specified in Clause 8                                                                                                               | 120° as specified in Clause 8                                      |
+| Ability to control direction of travel                                               | N/A                                                      | N/A                                                      | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| Supported channel models                                                             | NIST                                                     | Short Delay Spread<br>Long Delay Spread                  | SCME Uma<br>SCME Umi                                                                                                                        | SCME Uma<br>SCME Umi                                               |
+| BS antenna configuration                                                             | Uncorrelated                                             | Selected as defined in Clause 8.5                        | Selected as defined in Clause 8.5                                                                                                           | Selected as defined in Clause 8.5                                  |
+| Ability to control BS antenna configuration                                          | No                                                       | Yes <sup>2</sup>                                         | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| XPR (defined in Clause 8.2)                                                          | N/A                                                      | N/A                                                      | 9dB                                                                                                                                         | 9dB                                                                |
+| V/H ratio                                                                            | 0dB on average                                           | 0dB on average                                           | 0.74 dB for SCME UMi<br>8.13 dB for SCME UMa                                                                                                | 0.74 dB for SCME UMi<br>8.13 dB for SCME UMa                       |
+| Ability to control XPR and V/H                                                       | No                                                       | No                                                       | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| <b>MIMO OTA attributes not yet tested</b>                                            |                                                          |                                                          |                                                                                                                                             |                                                                    |
+| Ability to control noise and interference direction                                  | Limited <sup>4</sup>                                     | Limited <sup>4</sup>                                     | Yes <sup>2</sup>                                                                                                                            | Yes <sup>2</sup>                                                   |
+| DUT size constraints                                                                 | Depends on chamber size <sup>5</sup><br>and stirrer size | Depends on chamber size <sup>5</sup><br>and stirrer size | Depends on chamber size <sup>5</sup> , and number of active antenna probes and channel emulator ports to fit required active antenna probes | Depends on chamber size <sup>5</sup><br>(SISO chamber quiet zone)  |
+| <b>Other Considerations</b>                                                          |                                                          |                                                          |                                                                                                                                             |                                                                    |
+| Non-intrusive test mode for DUT antenna pattern measurement                          | Not required                                             | Not required                                             | Not required                                                                                                                                | Required                                                           |
+| Ability to distinguish performance based on device orientation relative to the field | No                                                       | No                                                       | Yes                                                                                                                                         | Yes                                                                |
+| Major equipment elements for MIMO OTA test setup (all need MIMO BS emulator)         | MIMO capable reverberation chamber                       | MIMO capable reverberation chamber and channel emulator  | MIMO capable anechoic chamber to fit antenna probes and channel emulator                                                                    | SISO anechoic chamber with additional antenna and channel emulator |
+| Number of channel emulator ports <sup>7</sup>                                        | N/A                                                      | 4                                                        | 16 <sup>6</sup>                                                                                                                             | 2                                                                  |
+
+|                                                                      |                                                                               |                                                                               |                                       |                                                                                                                                |
+|----------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| DUT antenna polarization discrimination <sup>8</sup>                 | No                                                                            | No                                                                            | Yes                                   | Yes                                                                                                                            |
+| DUT Antenna radiation pattern adaptation, performance discrimination | Feasibility study not yet performed                                           | Feasibility study not yet performed                                           | Yes <sup>9</sup>                      | Feasibility study not yet performed <sup>10</sup>                                                                              |
+| Number of independent measurements                                   | 1 after sufficient number of stirrers states to ensure isotropy <sup>12</sup> | 1 after sufficient number of stirrers states to ensure isotropy <sup>12</sup> | 12 device rotations for 2D evaluation | Measurement of radiation pattern in 1 <sup>st</sup> stage and measurement in radiated stage for 12 rotations for 2D evaluation |
+| Dependence on number of UE Rx ports                                  | N/A                                                                           | N/A                                                                           | N/A                                   | The two probe RTS system is only applicable to UE with 2 Rx antennas                                                           |
+
+Note 1: Random distribution of angles of arrival. Isotropy is achieved after sufficient amount of test time as per Annex C.
+
+Note 2: Requires validation.
+
+Note 3: PDP modification will require new loading of chamber.
+
+Note 4: Feasibility study under progress.
+
+Note 5: Chamber size depends on the size of the UE and the frequency of the test.
+
+Note 6: Minimum setup configuration as per table 6.3.1.1-1.
+
+Note 7: Configuration reflects what has been tested. Optimization may be possible.
+
+Note 8: Assuming that correlation, gain imbalance, total efficiency are equivalent among DUT, purely isolating antennas polarization.
+
+Note 9: Based on preliminary feasibility study.
+
+Note 10: It will require DUT feedback mechanism.
+
+Note 11: 3D is possible without new test setup if 3D channel models are specified. It requires validation.
+
+Note 12: Isotropy is achieved after sufficient amount of isotropic states as per Annex C.  
+The guideline for TRS, number of independent samples should be larger than 100, preferable 200 or 400 (3GPP TS 34.114 [4]).
+
+# Annex A: eNodeB Emulator Downlink power verification
+
+## A.1 Introduction
+
+The measurements described in this clause serve three primary purposes; to confirm that:
+
+- 1) the PDSCH total power is balanced between the MIMO transmit ports of an eNodeB emulator;
+- 2) the PDCCH-EPRE vs. PDSCH-EPRE is balanced per eNodeB emulator antenna port within a given RB;
+- 3) the RS-EPRE vs. PDSCH-EPRE ratio is correct per eNodeB emulator antenna port within a given RB.
+
+## A.2 Test prerequisites
+
+The parameters specified in Table A.1-1 and Table A.1-2 below are based on the eNodeB emulator settings described in Table 7.1-1 and Table 7.1-2.
+
+**Table A.1-1: FDD eNodeB Emulator Configuration for Downlink Power Verification**
+
+| Parameter                              | Value                                                                                                                                                        |                  |
+|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| Operating Band/Channel (see Note)      | Band 7 (3100 DL/21100 UL)<br>Band 13 (5230 DL/23230 UL)<br>Band 20 (6300 DL/24300 UL)                                                                        |                  |
+| Downlink Bandwidth                     | 10 MHz                                                                                                                                                       |                  |
+| Duplex Mode                            | FDD                                                                                                                                                          |                  |
+| Schedule Type                          | Reference Measurement Channel (RMC)                                                                                                                          |                  |
+| Downlink Reference Channel             | R.11 FDD                                                                                                                                                     | R.35 FDD         |
+| Downlink Modulation                    | 16QAM                                                                                                                                                        | 64QAM            |
+| Downlink TBS Index                     | 13 (RMC Defined)                                                                                                                                             | 24 (RMC Defined) |
+| Downlink MIMO Mode                     | 2x2 Open Loop Spatial Multiplexing                                                                                                                           |                  |
+| Number of Downlink RBs                 | 50                                                                                                                                                           |                  |
+| Downlink RB <sub>Start</sub>           | 0                                                                                                                                                            |                  |
+| Downlink Power Level, eNodeB emulator  | -50 dBm/15 kHz<br>(RS-EPRE at each eNodeB emulator port)                                                                                                     |                  |
+| Uplink Bandwidth                       | 10 MHz                                                                                                                                                       |                  |
+| Uplink Modulation                      | QPSK                                                                                                                                                         | 16QAM            |
+| Uplink TBS Index                       | 6 (RMC Defined)                                                                                                                                              | 19 (RMC Defined) |
+| Number of Uplink RBs                   | 50                                                                                                                                                           |                  |
+| Uplink RB <sub>Start</sub>             | 0                                                                                                                                                            |                  |
+| Transmit Power Control                 | 10 dB below the nominal maximum output power defined by the DUT power class (e.g. +13 dBm/10 MHz for a DUT with UE Power Class 3)                            |                  |
+| PDSCH Power Offset Relative to RS EPRE | $\rho_A = -3$ dB<br>$\rho_B = -3$ dB                                                                                                                         |                  |
+| HARQ Transmissions                     | 1 (No HARQ)                                                                                                                                                  |                  |
+| AWGN                                   | Off                                                                                                                                                          |                  |
+| OCNG                                   | Off                                                                                                                                                          |                  |
+| NOTE:                                  | Labs executing this test may use any one of the three bands listed in Table A.1-1 according to test UE availability and band support in the eNodeB emulator. |                  |
+
+**Table A.1-2: TDD eNodeB Emulator Configuration for Downlink Power Verification**
+
+| Parameter                                 | Value                                                                                                                                                          |                  |
+|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|
+| Operating Band / Channel<br>(see Note)    | Band 38 (38000)<br>Band 39 (38450)<br>Band 40 (39150)<br>Band 41 (40620)                                                                                       |                  |
+| Downlink Bandwidth                        | 20 MHz                                                                                                                                                         |                  |
+| Duplex Mode                               | TDD                                                                                                                                                            |                  |
+| Schedule Type                             | Reference Measurement Channel (RMC)                                                                                                                            |                  |
+| Downlink Reference Channel                | R.30 TDD                                                                                                                                                       | R.31-4 TDD       |
+| Downlink Modulation                       | 16QAM                                                                                                                                                          | 64QAM            |
+| Downlink TBS Index                        | 13 (RMC defined)                                                                                                                                               | 26 (RMC defined) |
+| Up/Downlink Frame<br>Configuration        | 1                                                                                                                                                              |                  |
+| Special Frame configuration               | 7                                                                                                                                                              |                  |
+| Downlink MIMO Mode                        | 2x2 Open Loop Spatial Multiplexing                                                                                                                             |                  |
+| Number of Downlink RBs                    | 100                                                                                                                                                            |                  |
+| Downlink RB <sub>Start</sub>              | 0                                                                                                                                                              |                  |
+| Downlink Power Level,<br>eNodeB emulator  | -50 dBm/15 kHz<br>(RS-EPRE at each eNodeB emulator port)                                                                                                       |                  |
+| Uplink Bandwidth                          | 20 MHz                                                                                                                                                         |                  |
+| Uplink Modulation                         | QPSK                                                                                                                                                           | 16QAM            |
+| Uplink TBS Index                          | 6 (RMC Defined)                                                                                                                                                | 19 (RMC Defined) |
+| Number of Uplink RBs                      | 100                                                                                                                                                            |                  |
+| Uplink RB <sub>Start</sub>                | 0                                                                                                                                                              |                  |
+| Transmit Power Control                    | 10 dB below the nominal maximum output power defined by the DUT power class (e.g.<br>+13 dBm/20 MHz for a DUT with UE Power Class 3)                           |                  |
+| PDSCH Power Offset Relative<br>to RS EPRE | $\rho_A = -3$ dB<br>$\rho_B = -3$ dB                                                                                                                           |                  |
+| HARQ Transmissions                        | 1 (No HARQ)                                                                                                                                                    |                  |
+| AWGN                                      | Off                                                                                                                                                            |                  |
+| OCNG                                      | Off                                                                                                                                                            |                  |
+| NOTE:                                     | Labs executing this test may use any one of the four bands listed in Table A.1-2<br>according to test UE availability and band support in the eNodeB emulator. |                  |
+
+## A.3 Test Methodology
+
+For the purpose of verifying channel power levels called for in this document, the eNodeB emulator shall be connected to a test UE (DUT) according to the configuration shown in Figure A.3-1 below:
+
+![Figure A.3-1: eNodeB Connections for Downlink Power Verification. The diagram shows an eNB connected to a DUT via a circulator and two splitters. The eNB has three ports: Tx1, Rx, and Tx2. Tx1 is connected to Splitter #1, which has two output ports: one to an Analyzer (labeled Note 3) and one to the circulator. The Analyzer output is labeled 'To Splitter #1 or Splitter #2 (see Text)'. The circulator has two output ports: one to the DUT's Tx/Rx1 port (labeled '10 dB Atten') and one to the DUT's Rx2 port (labeled '12 dB Atten'). The DUT's Rx2 port is also connected to Splitter #2, which has two output ports: one to the Analyzer (labeled Note 3) and one to the circulator. The eNB's Rx port is connected to the circulator's Rx port. The eNB's Tx2 port is connected to Splitter #2. Power levels are indicated at various points: at the eNB ports (Tx1: -43 dBm, -70 dBm; Rx: -22 dBm; Tx2: -70 dBm), at the splitters (Splitter #1: -73 dBm, -46 dBm; Splitter #2: -73 dBm), at the circulator (Circulator: -40 dBm, -20 dBm, -73 dBm, -75 dBm), and at the DUT ports (Tx/Rx1: -10 dBm, -85 dBm; Rx2: -85 dBm). A legend indicates that black text represents DL power (RS-EPRE dBm/15 kHz) and red text represents UL power (dBm/10 MHz).](b02ba0b73e95416eb547976f6145b169_img.jpg)
+
+Figure A.3-1: eNodeB Connections for Downlink Power Verification. The diagram shows an eNB connected to a DUT via a circulator and two splitters. The eNB has three ports: Tx1, Rx, and Tx2. Tx1 is connected to Splitter #1, which has two output ports: one to an Analyzer (labeled Note 3) and one to the circulator. The Analyzer output is labeled 'To Splitter #1 or Splitter #2 (see Text)'. The circulator has two output ports: one to the DUT's Tx/Rx1 port (labeled '10 dB Atten') and one to the DUT's Rx2 port (labeled '12 dB Atten'). The DUT's Rx2 port is also connected to Splitter #2, which has two output ports: one to the Analyzer (labeled Note 3) and one to the circulator. The eNB's Rx port is connected to the circulator's Rx port. The eNB's Tx2 port is connected to Splitter #2. Power levels are indicated at various points: at the eNB ports (Tx1: -43 dBm, -70 dBm; Rx: -22 dBm; Tx2: -70 dBm), at the splitters (Splitter #1: -73 dBm, -46 dBm; Splitter #2: -73 dBm), at the circulator (Circulator: -40 dBm, -20 dBm, -73 dBm, -75 dBm), and at the DUT ports (Tx/Rx1: -10 dBm, -85 dBm; Rx2: -85 dBm). A legend indicates that black text represents DL power (RS-EPRE dBm/15 kHz) and red text represents UL power (dBm/10 MHz).
+
+NOTE 1: TX Port #1 is used as transmit-only on eNodeB emulators with a separate uplink RX port.
+
+NOTE 2: If the eNodeB emulator supports full duplex operation on TX port #1, the circulator's RX port shall be terminated in a 50 Ohm load.
+
+NOTE 3: These splitter ports will be used to provide a downlink RF sample to the analyzer and shall be terminated in a 50 Ohm load when not in use.
+
+**Figure A.3-1: eNodeB Connections for Downlink Power Verification**
+
+The analyzer shown in Figure A.3-1 above must be capable of measuring the eNodeB emulator's average PDCCH power independent of the eNodeB emulator's average PDSCH power, expressed as a PSD in dBm/15 kHz.
+
+The analyzer must also be capable of measuring RS EPRE and PDSCH EPRE in dBm/15 kHz.
+
+Any instrument capable of making these measurements is acceptable.
+
+The following eight measurements shall be made while the UE is in an active data session and sending continuous uplink data to the eNodeB emulator using the settings described in Table A.1-1 and Table A.1-2:
+
+- 1) Average power at TX Port 1 (through Splitter 1) of all PDCCH RBs expressed as a PSD in dBm/15 kHz
+- 2) Average power at TX Port 1 (through Splitter 1) of all PDSCH RBs expressed as a PSD in dBm/15 kHz
+- 3) PDSCH-EPRE at TX Port 1 (through Splitter 1) in dBm/15 kHz
+- 4) RS-EPRE at TX Port 1 (through Splitter 1) in dBm/15 kHz for the Reference Signals in DL
+- 5) Average power at TX Port 2 (through Splitter 2) of all PDCCH RBs expressed as a PSD in dBm/15 kHz
+- 6) Average power at TX Port 2 (through Splitter 2) of all PDSCH RBs expressed as a PSD in dBm/15 kHz
+- 7) PDSCH-EPRE at TX Port 2 (through Splitter 2) in dBm/15 kHz
+- 8) RS-EPRE at TX Port 2 (through Splitter 2) in dBm/15 kHz
+
+From the eight measurements described above, calculate the following:
+
+- eNodeB TX Port 1/TX Port 2 PDCCH average power balance (in dB) across all DL RBs
+- eNodeB TX Port 1/TX Port 2 PDSCH average power balance (in dB) across all DL RBs
+
+- eNodeB RS-EPRE to PDSCH-EPRE power ratio (in dB), TX Port 1
+- eNodeB RS-EPRE to PDSCH-EPRE power ratio (in dB), TX Port 2
+
+To be considered compliant with 3GPP TS 36.521-1 [12], the following criteria must be met:
+
+- a. eNodeB PDCCH-EPRE TX Port1/TX Port 2 power balance must be 0 dB, +/- 0.7 dB
+- b. eNodeB PDSCH-EPRE TX Port 1/TX Port 2 power balance must be 0 dB, +/- 0.7 dB
+- c. eNodeB PDCCH-EPRE to PDSCH-EPRE TX Port 1 power ratio must be 0 dB, +/- 0.7 dB
+- d. eNodeB PDCCH-EPRE to PDSCH-EPRE TX Port 2 power ratio must be 0 dB, +/- 0.7 dB
+
+In addition, the following criteria must be met per antenna based on the PDSCH EPRE power offset relative to RS EPRE called for in Table A.1-1 and Table A.1-2:
+
+- e. eNodeB RS-EPRE to PDSCH-EPRE ratio must be +3 dB, +/- 0.7 dB for TX Port 1
+- f. eNodeB RS-EPRE to PDSCH-EPRE ratio must be +3 dB, +/- 0.7 dB for TX Port 2
+
+# --- Annex B:
+
+## Measurement uncertainty budget
+
+## B.1 Measurement uncertainty budget for multiprobe method
+
+**Table B.1-1: Measurement uncertainty budget for multiprobe method**
+
+| #                                      | Description of uncertainty contribution                                                                                                             | Details in                             | MPAC                                                        |                                           |                      |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|-------------------------------------------|----------------------|
+|                                        |                                                                                                                                                     |                                        | Example Value [dB]                                          | Prob Distr                                | Std Uncertainty [dB] |
+| <b>Stage 1-DUT measurement</b>         |                                                                                                                                                     |                                        |                                                             |                                           |                      |
+| 1                                      | Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                   | TS 34.114, E.1-E.2                     | 0.00                                                        | u-shape                                   | 0.00                 |
+| 2                                      | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-E.5                     | 0.00                                                        | rect                                      | 0.00                 |
+| 3                                      | Influence of the fixed measurement antenna cable                                                                                                    | TS 34.114, E.6                         | 0.00                                                        | rect                                      | 0.00                 |
+| 4                                      | Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                           | TS 34.114, E.7                         | 0.00                                                        | rect                                      | 0.00                 |
+| 5                                      | Base station simulator: uncertainty of the absolute output level                                                                                    | TS 34.114, E.17<br>[TS 36.521-1 F.1.3] | 1.00                                                        | rect                                      | 0.58                 |
+| 6                                      | Throughput measurement: output level step resolution                                                                                                | TS 34.114, E.18                        | 0.25                                                        | rect                                      | 0.14                 |
+| 7                                      | Statistical uncertainty of throughput measurement                                                                                                   | TS34.114, E.19                         | FFS<br>(negligible and partially included in repeatability) |                                           |                      |
+| 8                                      | Fading channel emulator output uncertainty (if used)<br>- absolute output power<br>- output signal stability<br>- output stability with temperature | B.6                                    | 1.5dB<br>0.5dB<br>0.4dB                                     | normal (output power)<br>rect (stability) | 0.84                 |
+| 9                                      | AWGN flatness within LTE band                                                                                                                       | TBD (NOTE 4)                           |                                                             |                                           | FFS                  |
+| 10                                     | Signal-to noise ratio uncertainty, averaged over downlink transmission Bandwidth                                                                    | TBD (NOTE 4)                           |                                                             |                                           | FFS                  |
+| 11                                     | Channel model implementation (NOTE 2)                                                                                                               | TBD                                    | FFS                                                         |                                           | FFS                  |
+| 12                                     | Chamber statistical ripple and repeatability                                                                                                        | TS 34.114, E.26.A                      | N/A                                                         |                                           | 0.00                 |
+| 13                                     | Additional power loss in EUT chassis                                                                                                                | TS 34.114, E.26.B                      | N/A                                                         |                                           | 0.00                 |
+| 14                                     | Quality of the quiet zone                                                                                                                           | TS 34.114, E.10                        | 0.50                                                        | std                                       | 0.50                 |
+| 15                                     | Measurement Distance<br>- VSWR<br>- Chamber Standing Wave                                                                                           | TS 34.114, E.9                         | 0.00                                                        |                                           | 0.00                 |
+| 16                                     | Positioner error (2nd stage RTS) (assuming < 0.5 degrees)                                                                                           |                                        | N/A                                                         |                                           | 0.00                 |
+| 17                                     | DUT sensitivity drift                                                                                                                               | TS 34.114, E.21                        | 0.20                                                        | rect                                      | 0.12                 |
+| 18                                     | Uncertainty related to the use of the phantoms:                                                                                                     | TR 25.914                              |                                                             |                                           | 0.00                 |
+|                                        | a) Uncertainty of dielectric properties and shape of the hand phantom                                                                               | A.12.3                                 |                                                             |                                           | 0.00                 |
+|                                        | b) Uncertainty related to the use of laptop ground plane phantom                                                                                    | A.12.4                                 |                                                             |                                           | 0.00                 |
+| 19                                     | Random uncertainty (repeatability)                                                                                                                  | TS 34.114, E.14                        | 0.20                                                        | rect                                      | 0.12                 |
+| 20                                     | Uncertainty associated with the stirring method and number of subframes (NOTE 3)                                                                    |                                        | N/A                                                         |                                           | 0.00                 |
+| <b>Stage 2-Calibration measurement</b> |                                                                                                                                                     |                                        |                                                             |                                           |                      |
+| 21                                     | Uncertainty of network analyzer<br>- Receiver and Source VNA<br>- Receiver VNA Calibration prior to measurement                                     | TS 34.114, E.15                        | 0.50                                                        | rect                                      | 0.29                 |
+| 22                                     | Mismatch of transmitter chain                                                                                                                       | TS 34.114, E.1-E.2                     | 0.20                                                        | u-shape                                   | 0.14                 |
+| 23                                     | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-                        | 0.00                                                        |                                           | 0.00                 |
+
+|    |                                                                                                                      |                     |      |      |             |
+|----|----------------------------------------------------------------------------------------------------------------------|---------------------|------|------|-------------|
+|    |                                                                                                                      | E.5                 |      |      |             |
+| 24 | Mismatch in the connection of calibration antenna                                                                    | TS 34.114, E.1      | 0.00 | rect | 0.00        |
+| 25 | Influence of the calibration antenna feed cable                                                                      | TS 34.114, E.6      |      |      | 0.00        |
+| 26 | Influence of the transmitter antennas/probes cables                                                                  | TS 34.114, E.6      | 0.00 | rect | 0.00        |
+| 27 | Uncertainty of the absolute gain of the transmitter antennas/probes                                                  | TS 34.114, E.7      | 0.00 | rect | 0.00        |
+| 28 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                     | TS 34.114, E.16     | 0.50 | std  | 0.50        |
+| 29 | Chamber statistical ripple and repeatability                                                                         | TS 34.114, E.26.A   |      |      | 0.00        |
+| 30 | Phase Center Offset (when using horn to calibrate)                                                                   | TS 34.114, E.9      | 0.00 | rect | 0.00        |
+| 31 | Quality of the quiet zone (Range Ref. Antenna)                                                                       | TS 34.114, E.10     | 0.50 | rect | 0.29        |
+| 32 | Impact of ATF pattern error on TP<br>- DUT RSAP measurement uncertainty TR<br>- DUT RSARP measurement uncertainty TR | TR 37.978<br>10.1&2 | N/A  |      | 0.00        |
+| 33 | Impact of non-ideal isolation between streams in radiated 2nd stage (assuming 15 dB isolation)                       |                     | N/A  |      | 0.00        |
+|    | <b>External Amplifiers</b>                                                                                           |                     |      |      | <b>0.00</b> |
+| 34 | Stability                                                                                                            | B.7.1               | 0.30 | rect | 0.17        |
+| 35 | Linearity                                                                                                            | B.7.2               | 0.10 | rect | 0.06        |
+| 36 | Noise Figure                                                                                                         | B.7.3               | 0.30 | rect | 0.17        |
+| 37 | Mismatch                                                                                                             | B.7.4               | 0.00 | rect | 0.00        |
+| 38 | Gain                                                                                                                 | B.7.5               | 0.00 | rect | 0.00        |
+
+NOTE 1: 0dB if fading for RTS is done in baseband; same as RC&CE and MPAC if fading is not in baseband
+
+NOTE 2: assumption is that MU set to 0dB with channel model validation pass/fail limits (FFS) that have negligible impact on TP FOM; MU for channel model validation is FFS
+
+NOTE 3: Analysis of the element associated with stirring method and number of subframes is based on existing harmonization test campaign data and can be further augmented by additional measurements. The following combinations of stirring modes and number of subframes have been identified as common use cases with the following standard uncertainties (different combinations require separate validation):
+
+A: stepped stirring mode with 20k SF per stirring state: 0dB
+
+B: stepped stirring mode with 400 SF per stirring state: 0.22dB
+
+C: continuous stirring mode with 20k SF per sample: FFS
+
+D: continuous stirring mode with 400 SF per sample: FFS
+
+Until MU elements for continuous stirring modes have been defined, the test plan shall only consider stepped stirring approach
+
+NOTE 4: As the applicability of SIR to MIMO OTA performance evaluation is FFS, the measurement uncertainty treatment for SIR related items will remain FFS. When the applicability of SIR is confirmed, the measurement uncertainty treatment defined in 3GPP TS 36.521-1 [12] Table F.1.4-1 for line item 8.2.1.3.1 should be considered along with the related test system constraints. Any adjustments to the test system limits or uncertainty definitions necessary for MIMO OTA performance testing should be applied.
+
+## --- B.2 Measurement uncertainty budget contributors for the RTS method
+
+**Table B.2-1: Measurement uncertainty budget contributors for the RTS method**
+
+| #                                      | Description of uncertainty contribution                                                                                                             | Details in                             | RTS                                                         |            |                      |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|------------|----------------------|
+|                                        |                                                                                                                                                     |                                        | Example Value [dB]                                          | Prob Distr | Std Uncertainty [dB] |
+| <b>Stage 1-DUT measurement</b>         |                                                                                                                                                     |                                        |                                                             |            |                      |
+| 1                                      | Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                   | TS 34.114, E.1-E.2                     | 0.00                                                        | u-shape    | 0.00                 |
+| 2                                      | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-E.5                     | 0.00                                                        | rect       | 0.00                 |
+| 3                                      | Influence of the fixed measurement antenna cable                                                                                                    | TS 34.114, E.6                         | 0.00                                                        | rect       | 0.00                 |
+| 4                                      | Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                           | TS 34.114, E.7                         | 0.00                                                        | rect       | 0.00                 |
+| 5                                      | Base station simulator: uncertainty of the absolute output level                                                                                    | TS 34.114, E.17<br>[TS 36.521-1 F.1.3] | 1.00                                                        | rect       | 0.58                 |
+| 6                                      | Throughput measurement: output level step resolution                                                                                                | TS 34.114, E.18                        | 0.25                                                        | rect       | 0.14                 |
+| 7                                      | Statistical uncertainty of throughput measurement                                                                                                   | TS34.114, E.19                         | FFS<br>(negligible and partially included in repeatability) |            |                      |
+| 8                                      | Fading channel emulator output uncertainty (if used)<br>- absolute output power<br>- output signal stability<br>- output stability with temperature | B.6                                    | 0 (NOTE 1)                                                  |            | 0.00                 |
+| 9                                      | AWGN flatness within LTE band                                                                                                                       | TBD (NOTE 4)                           |                                                             |            | FFS                  |
+| 10                                     | Signal-to noise ratio uncertainty, averaged over downlink transmission Bandwidth                                                                    | TBD (NOTE 4)                           |                                                             |            | FFS                  |
+| 11                                     | Channel model implementation (NOTE 2)                                                                                                               | TBD                                    | FFS                                                         |            | FFS                  |
+| 12                                     | Chamber statistical ripple and repeatability                                                                                                        | TS 34.114, E.26.A                      | N/A                                                         |            | 0.00                 |
+| 13                                     | Additional power loss in EUT chassis                                                                                                                | TS 34.114, E.26.B                      | N/A                                                         |            | 0.00                 |
+| 14                                     | Quality of the quiet zone                                                                                                                           | TS 34.114, E.10                        | 0.50                                                        | std        | 0.50                 |
+| 15                                     | Measurement Distance<br>- VSWR<br>- Chamber Standing Wave                                                                                           | TS 34.114, E.9                         | 0.00                                                        |            | 0.00                 |
+| 16                                     | Positioner error (2nd stage RTS) (assuming < 0.5 degrees)                                                                                           |                                        |                                                             |            | 0.00                 |
+| 17                                     | DUT sensitivity drift                                                                                                                               | TS 34.114, E.21                        | 0.20                                                        | rect       | 0.12                 |
+| 18                                     | Uncertainty related to the use of the phantoms:                                                                                                     | TR 25.914                              |                                                             |            | 0.00                 |
+|                                        | a) Uncertainty of dielectric properties and shape of the hand phantom                                                                               | A.12.3                                 |                                                             |            | 0.00                 |
+|                                        | b) Uncertainty related to the use of laptop ground plane phantom                                                                                    | A.12.4                                 |                                                             |            | 0.00                 |
+| 19                                     | Random uncertainty (repeatability)                                                                                                                  | TS 34.114, E.14                        | 0.20                                                        | rect       | 0.12                 |
+| 20                                     | Uncertainty associated with the stirring method and number of subframes (NOTE 3)                                                                    |                                        | N/A                                                         |            | 0.00                 |
+| <b>Stage 2-Calibration measurement</b> |                                                                                                                                                     |                                        |                                                             |            |                      |
+| 21                                     | Uncertainty of network analyzer<br>- Receiver and Source VNA<br>- Receiver VNA Calibration prior to measurement                                     | TS 34.114, E.15                        | 0.50                                                        | rect       | 0.29                 |
+| 22                                     | Mismatch of transmitter chain                                                                                                                       | TS 34.114, E.1-E.2                     | 0.00                                                        | u-shape    | 0.00                 |
+| 23                                     | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-                        | 0.00                                                        |            | 0.00                 |
+
+|    |                                                                                                                      |                     |      |      |             |
+|----|----------------------------------------------------------------------------------------------------------------------|---------------------|------|------|-------------|
+|    |                                                                                                                      | E.5                 |      |      |             |
+| 24 | Mismatch in the connection of calibration antenna                                                                    | TS 34.114, E.1      | 0.00 | rect | 0.00        |
+| 25 | Influence of the calibration antenna feed cable                                                                      | TS 34.114, E.6      |      |      | 0.00        |
+| 26 | Influence of the transmitter antennas/probes cables                                                                  | TS 34.114, E.6      | 0.00 | rect | 0.00        |
+| 27 | Uncertainty of the absolute gain of the transmitter antennas/probes                                                  | TS 34.114, E.7      | 0.00 | rect | 0.00        |
+| 28 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                     | TS 34.114, E.16     | 0.50 | std  | 0.50        |
+| 29 | Chamber statistical ripple and repeatability                                                                         | TS 34.114, E.26.A   |      |      | 0.00        |
+| 30 | Phase Center Offset (when using horn to calibrate)                                                                   | TS 34.114, E.9      | 0.00 | rect | 0.00        |
+| 31 | Quality of the quiet zone (Range Ref. Antenna)                                                                       | TS 34.114, E.10     | 0.50 | rect | 0.29        |
+| 32 | Impact of ATF pattern error on TP<br>- DUT RSAP measurement uncertainty TR<br>- DUT RSARP measurement uncertainty TR | TR 37.978<br>10.1&2 | 0.20 | std  | 0.20        |
+| 33 | Impact of non-ideal isolation between streams in radiated 2nd stage (assuming 15 dB isolation)                       |                     | 0.20 | std  | 0.20        |
+|    | <b>External Amplifiers</b>                                                                                           |                     |      |      | <b>0.00</b> |
+| 34 | Stability                                                                                                            | B.7.1               |      |      | 0.00        |
+| 35 | Linearity                                                                                                            | B.7.2               |      |      | 0.00        |
+| 36 | Noise Figure                                                                                                         | B.7.3               |      |      | 0.00        |
+| 37 | Mismatch                                                                                                             | B.7.4               |      |      | 0.00        |
+| 38 | Gain                                                                                                                 | B.7.5               |      |      | 0.00        |
+
+NOTE 1: 0dB if fading for RTS is done in baseband; same as RC&CE and MPAC if fading is not in baseband
+
+NOTE 2: assumption is that MU set to 0dB with channel model validation pass/fail limits (FFS) that have negligible impact on TP FOM; MU for channel model validation is FFS
+
+NOTE 3: Analysis of the element associated with stirring method and number of subframes is based on existing harmonization test campaign data and can be further augmented by additional measurements. The following combinations of stirring modes and number of subframes have been identified as common use cases with the following standard uncertainties (different combinations require separate validation):
+
+A: stepped stirring mode with 20k SF per stirring state: 0dB
+
+B: stepped stirring mode with 400 SF per stirring state: 0.22dB
+
+C: continuous stirring mode with 20k SF per sample: FFS
+
+D: continuous stirring mode with 400 SF per sample: FFS
+
+Until MU elements for continuous stirring modes have been defined, the test plan shall only consider stepped stirring approach
+
+NOTE 4: As the applicability of SIR to MIMO OTA performance evaluation is FFS, the measurement uncertainty treatment for SIR related items will remain FFS. When the applicability of SIR is confirmed, the measurement uncertainty treatment defined in 3GPP TS 36.521-1 [12] Table F.1.4-1 for line item 8.2.1.3.1 should be considered along with the related test system constraints. Any adjustments to the test system limits or uncertainty definitions necessary for MIMO OTA performance testing should be applied.
+
+## --- B.3 Measurement uncertainty budget for reverberation chamber method
+
+**Table B.3-1: Measurement uncertainty budget for reverberation chamber method**
+
+| #                                      | Description of uncertainty contribution                                                                                                             | Details in                             | RC                                                          |            |                      |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|------------|----------------------|
+|                                        |                                                                                                                                                     |                                        | Example Value [dB]                                          | Prob Distr | Std Uncertainty [dB] |
+| <b>Stage 1-DUT measurement</b>         |                                                                                                                                                     |                                        |                                                             |            |                      |
+| 1                                      | Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                   | TS 34.114, E.1-E.2                     | 0.02                                                        | u-shape    | 0.01                 |
+| 2                                      | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-E.5                     | 0.00                                                        | rect       | 0.00                 |
+| 3                                      | Influence of the fixed measurement antenna cable                                                                                                    | TS 34.114, E.6                         | 0.00                                                        | rect       | 0.00                 |
+| 4                                      | Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                           | TS 34.114, E.7                         | 0.00                                                        | rect       | 0.00                 |
+| 5                                      | Base station simulator: uncertainty of the absolute output level                                                                                    | TS 34.114, E.17<br>[TS 36.521-1 F.1.3] | 1.00                                                        | rect       | 0.58                 |
+| 6                                      | Throughput measurement: output level step resolution                                                                                                | TS 34.114, E.18                        | 0.25                                                        | rect       | 0.14                 |
+| 7                                      | Statistical uncertainty of throughput measurement                                                                                                   | TS34.114, E.19                         | FFS<br>(negligible and partially included in repeatability) |            |                      |
+| 8                                      | Fading channel emulator output uncertainty (if used)<br>- absolute output power<br>- output signal stability<br>- output stability with temperature | B.6                                    | 0.00                                                        |            | 0.00                 |
+| 9                                      | AWGN flatness within LTE band                                                                                                                       | TBD (NOTE 4)                           |                                                             |            | FFS                  |
+| 10                                     | Signal-to noise ratio uncertainty, averaged over downlink transmission Bandwidth                                                                    | TBD (NOTE 4)                           |                                                             |            | FFS                  |
+| 11                                     | Channel model implementation (NOTE 2)                                                                                                               | TBD                                    | FFS                                                         |            | FFS                  |
+| 12                                     | Chamber statistical ripple and repeatability                                                                                                        | TS 34.114, E.26.A                      | 0.30                                                        | std        | 0.30                 |
+| 13                                     | Additional power loss in EUT chassis                                                                                                                | TS 34.114, E.26.B                      | 0.10                                                        | rect       | 0.06                 |
+| 14                                     | Quality of the quiet zone                                                                                                                           | TS 34.114, E.10                        | N/A                                                         |            | 0.00                 |
+| 15                                     | Measurement Distance<br>- VSWR<br>- Chamber Standing Wave                                                                                           | TS 34.114, E.9                         | N/A                                                         |            | 0.00                 |
+| 16                                     | Positioner error (2nd stage RTS) (assuming < 0.5 degrees)                                                                                           |                                        | N/A                                                         |            | 0.00                 |
+| 17                                     | DUT sensitivity drift                                                                                                                               | TS 34.114, E.21                        | 0.20                                                        | rect       | 0.12                 |
+| 18                                     | Uncertainty related to the use of the phantoms:                                                                                                     | TR 25.914                              |                                                             |            | 0.00                 |
+|                                        | a) Uncertainty of dielectric properties and shape of the hand phantom                                                                               | A.12.3                                 |                                                             |            | 0.00                 |
+|                                        | b) Uncertainty related to the use of laptop ground plane phantom                                                                                    | A.12.4                                 |                                                             |            | 0.00                 |
+| 19                                     | Random uncertainty (repeatability)                                                                                                                  | TS 34.114, E.14                        | 0.20                                                        | rect       | 0.12                 |
+| 20                                     | Uncertainty associated with the stirring method and number of subframes (NOTE 3)                                                                    |                                        | see NOTE 3                                                  | std        | see NOTE 3           |
+| <b>Stage 2-Calibration measurement</b> |                                                                                                                                                     |                                        |                                                             |            |                      |
+| 21                                     | Uncertainty of network analyzer<br>- Receiver and Source VNA<br>- Receiver VNA Calibration prior to measurement                                     | TS 34.114, E.15                        | 0.50                                                        | rect       | 0.29                 |
+| 22                                     | Mismatch of transmitter chain                                                                                                                       | TS 34.114, E.1-E.2                     | 0.00                                                        | u-shape    | 0.00                 |
+| 23                                     | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-                        | 0.00                                                        |            | 0.00                 |
+
+|    |                                                                                                                      |                   |      |      |             |
+|----|----------------------------------------------------------------------------------------------------------------------|-------------------|------|------|-------------|
+|    |                                                                                                                      | E.5               |      |      |             |
+| 24 | Mismatch in the connection of calibration antenna                                                                    | TS 34.114, E.1    | 0.00 | rect | 0.00        |
+| 25 | Influence of the calibration antenna feed cable                                                                      | TS 34.114, E.6    |      |      | 0.00        |
+| 26 | Influence of the transmitter antennas/probes cables                                                                  | TS 34.114, E.6    | 0.00 | rect | 0.00        |
+| 27 | Uncertainty of the absolute gain of the transmitter antennas/probes                                                  | TS 34.114, E.7    | 0.00 | rect | 0.00        |
+| 28 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                     | TS 34.114, E.16   | 0.50 | std  | 0.50        |
+| 29 | Chamber statistical ripple and repeatability                                                                         | TS 34.114, E.26.A | 0.30 | std  | 0.30        |
+| 30 | Phase Center Offset (when using horn to calibrate)                                                                   | TS 34.114, E.9    | N/A  |      | 0.00        |
+| 31 | Quality of the quiet zone (Range Ref. Antenna)                                                                       | TS 34.114, E.10   | N/A  |      | 0.00        |
+| 32 | Impact of ATF pattern error on TP<br>- DUT RSAP measurement uncertainty TR<br>- DUT RSARP measurement uncertainty TR | TR 37.978 10.1&2  | N/A  |      | 0.00        |
+| 33 | Impact of non-ideal isolation between streams in radiated 2nd stage (assuming 15 dB isolation)                       |                   | N/A  |      | 0.00        |
+|    | <b>External Amplifiers</b>                                                                                           |                   |      |      | <b>0.00</b> |
+| 34 | Stability                                                                                                            | B.7.1             |      |      | 0.00        |
+| 35 | Linearity                                                                                                            | B.7.2             |      |      | 0.00        |
+| 36 | Noise Figure                                                                                                         | B.7.3             |      |      | 0.00        |
+| 37 | Mismatch                                                                                                             | B.7.4             |      |      | 0.00        |
+| 38 | Gain                                                                                                                 | B.7.5             |      |      | 0.00        |
+
+NOTE 1: 0dB if fading for RTS is done in baseband; same as RC&CE and MPAC if fading is not in baseband
+
+NOTE 2: assumption is that MU set to 0dB with channel model validation pass/fail limits (FFS) that have negligible impact on TP FOM; MU for channel model validation is FFS
+
+NOTE 3: Analysis of the element associated with stirring method and number of subframes is based on existing harmonization test campaign data and can be further augmented by additional measurements. The following combinations of stirring modes and number of subframes have been identified as common use cases with the following standard uncertainties (different combinations require separate validation):
+
+A: stepped stirring mode with 20k SF per stirring state: 0dB
+
+B: stepped stirring mode with 400 SF per stirring state: 0.22dB
+
+C: continuous stirring mode with 20k SF per sample: FFS
+
+D: continuous stirring mode with 400 SF per sample: FFS
+
+Until MU elements for continuous stirring modes have been defined, the test plan shall only consider stepped stirring approach
+
+NOTE 4: As the applicability of SIR to MIMO OTA performance evaluation is FFS, the measurement uncertainty treatment for SIR related items will remain FFS. When the applicability of SIR is confirmed, the measurement uncertainty treatment defined in 3GPP TS 36.521-1 [12] Table F.1.4-1 for line item 8.2.1.3.1 should be considered along with the related test system constraints. Any adjustments to the test system limits or uncertainty definitions necessary for MIMO OTA performance testing should be applied.
+
+## --- B.4 Measurement uncertainty budget for decomposition method
+
+**Table B.4-1: Measurement uncertainty budget for decomposition method**
+
+| Description of uncertainty contribution                                                                                                                                                                                                 | Details in                           |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
+| <b>Step 1, UE radiated measurement</b>                                                                                                                                                                                                  |                                      |
+| 1) Mismatch of transmitter chain (i.e. between probe antenna and base station simulator)                                                                                                                                                | TS 34.114, E.1-E.2                   |
+| 2) Insertion loss of transmitter chain                                                                                                                                                                                                  | TS 34.114, E.3-E.5                   |
+| 3) Influence of the probe antenna cable                                                                                                                                                                                                 | TS 34.114, E.6                       |
+| 4) Uncertainty of the absolute antenna gain of the probe antenna                                                                                                                                                                        | TS 34.114, E.7                       |
+| 5) Base station simulator: uncertainty of the absolute output level                                                                                                                                                                     | TS 34.114, E.17, [TS 36.521-1 F.1.3] |
+| 6) Throughput measurement: output level step resolution                                                                                                                                                                                 | TS 34.114, E.18                      |
+| 7) Statistical uncertainty of throughput measurement                                                                                                                                                                                    | TBD                                  |
+| 8) Channel flatness within LTE band                                                                                                                                                                                                     | TBD                                  |
+| 9) Measurement distance:<br>a) offset of UE phase centre from axis(es) of rotation<br>b) mutual coupling between the UE and the probe antenna<br>c) phase curvature across the UE                                                       | TS 34.114, E.9                       |
+| 10) Quality of quiet zone                                                                                                                                                                                                               | TS 34.114, E.10                      |
+| 11) UE sensitivity drift                                                                                                                                                                                                                | TS 34.114, E.21                      |
+| 12) Uncertainty related to the use of the phantoms:<br>a) Uncertainty of dielectric properties and shape of the hand phantom.<br>b) Uncertainty related to the use of laptop ground plane phantom:                                      | TR 25.914<br>A.12.3<br>A.12.4        |
+| 13) Geometrical and polarization constellations                                                                                                                                                                                         | TBD                                  |
+| 14) Random uncertainty (repeatability)                                                                                                                                                                                                  | TS 34.114, E.14                      |
+| <b>Step 2, Calibration measurement, network analyzer method, TR 34.114 figure B.1</b>                                                                                                                                                   |                                      |
+| 15) Uncertainty of network analyzer                                                                                                                                                                                                     | TS 34.114, E.15                      |
+| 16) Mismatch in the connection of transmitter chain (i.e. between probe antenna and NA)                                                                                                                                                 | TS 34.114, E.1-E.2                   |
+| 17) Insertion loss of transmitter chain                                                                                                                                                                                                 | TS 34.114, E.3-E.5                   |
+| 18) Mismatch in the connection of calibration antenna                                                                                                                                                                                   | TS 34.114, E.1                       |
+| 19) Influence of the calibration antenna feed cable                                                                                                                                                                                     | TS 34.114, E.6                       |
+| 20) Influence of the probe antenna cable                                                                                                                                                                                                | TS 34.114, E.6                       |
+| 21) Uncertainty of the absolute gain of the probe antenna                                                                                                                                                                               | TS 34.114, E.7                       |
+| 22) Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                                                                                                                                    | TS 34.114, E.16                      |
+| 23) Measurement distance:<br>a) Offset of calibration antenna's phase centre from axis(es) of rotation<br>b) Mutual coupling between the calibration antenna and the probe antenna<br>c) Phase curvature across the calibration antenna | TS 34.114<br>E.9                     |
+| 24) Quality of quiet zone                                                                                                                                                                                                               | TS 34.114, E.10                      |
+| <b>Step 3, UE conducted measurements, baseband fader</b>                                                                                                                                                                                |                                      |
+| 25) Mismatch uncertainty between UE antenna system radiated connectivity and UE conducted mode test connectivity                                                                                                                        | TBD                                  |
+| 26) Insertion loss of transmitter chain                                                                                                                                                                                                 | TS 34.114, E.3-E.5                   |
+| 27) Base station simulator: uncertainty of the absolute output level                                                                                                                                                                    | TS 34.114, E.17, [TS 36.521-1 F.1.3] |
+| 28) Channel flatness within LTE band                                                                                                                                                                                                    | TBD                                  |
+| 29) Channel model implementation                                                                                                                                                                                                        | TBD                                  |
+| 30) Throughput measurement: output level step resolution                                                                                                                                                                                | TS 34.114, E.18                      |
+| 31) Statistical uncertainty of throughput measurement                                                                                                                                                                                   | TDB                                  |
+
+## B.5 Measurement uncertainty budget for reverberation chamber plus channel emulator method
+
+Table B.5-1: Measurement uncertainty budget for reverberation chamber plus channel emulator method
+
+| #  | Description of uncertainty contribution                                                                                                             | Details in                             | RC&CE                                                       |                                                 |                      |
+|----|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------|-------------------------------------------------|----------------------|
+|    |                                                                                                                                                     |                                        | Example Value [dB]                                          | Prob Distr                                      | Std Uncertainty [dB] |
+|    | <b>Stage 1-DUT measurement</b>                                                                                                                      |                                        |                                                             |                                                 |                      |
+| 1  | Mismatch of transmitter chain (i.e. between fixed measurement antenna and base station simulator)                                                   | TS 34.114, E.1-E.2                     | 0.04                                                        | u-shape                                         | 0.03                 |
+| 2  | Insertion loss of transmitter chain                                                                                                                 | TS 34.114, E.3-E.5                     | 0.00                                                        | rect                                            | 0.00                 |
+| 3  | Influence of the fixed measurement antenna cable                                                                                                    | TS 34.114, E.6                         | 0.00                                                        | rect                                            | 0.00                 |
+| 4  | Uncertainty of the absolute antenna gain of the fixed measurement antenna                                                                           | TS 34.114, E.7                         | 0.00                                                        | rect                                            | 0.00                 |
+| 5  | Base station simulator: uncertainty of the absolute output level                                                                                    | TS 34.114, E.17<br>[TS 36.521-1 F.1.3] | 1.00                                                        | rect                                            | 0.58                 |
+| 6  | Throughput measurement: output level step resolution                                                                                                | TS 34.114, E.18                        | 0.25                                                        | rect                                            | 0.14                 |
+| 7  | Statistical uncertainty of throughput measurement                                                                                                   | TS34.114, E.19                         | FFS<br>(negligible and partially included in repeatability) |                                                 |                      |
+| 8  | Fading channel emulator output uncertainty (if used)<br>- absolute output power<br>- output signal stability<br>- output stability with temperature | B.6                                    | 1.5dB<br>0.5dB<br>0.4dB                                     | normal<br>(output power)<br>rect<br>(stability) | 0.84                 |
+| 9  | AWGN flatness within LTE band                                                                                                                       | TBD (NOTE 4)                           |                                                             |                                                 | FFS                  |
+| 10 | Signal-to noise ratio uncertainty, averaged over downlink transmission Bandwidth                                                                    | TBD (NOTE 4)                           |                                                             |                                                 | FFS                  |
+| 11 | Channel model implementation (NOTE 2)                                                                                                               | TBD                                    | FFS                                                         |                                                 | FFS                  |
+| 12 | Chamber statistical ripple and repeatability                                                                                                        | G.1.2.2                                | 0.40                                                        | std                                             | 0.40                 |
+| 13 | Additional power loss in EUT chassis                                                                                                                | TS 34.114, E.26.B                      | 0.10                                                        | rect                                            | 0.06                 |
+| 14 | Quality of the quiet zone                                                                                                                           | TS 34.114, E.10                        | N/A                                                         |                                                 | 0.00                 |
+| 15 | Measurement Distance<br>- VSWR<br>- Chamber Standing Wave                                                                                           | TS 34.114, E.9                         | N/A                                                         |                                                 | 0.00                 |
+| 16 | Positioner error (2nd stage RTS) (assuming < 0.5 degrees)                                                                                           |                                        | N/A                                                         |                                                 | 0.00                 |
+| 17 | DUT sensitivity drift                                                                                                                               | TS 34.114, E.21                        | 0.20                                                        | rect                                            | 0.12                 |
+| 18 | Uncertainty related to the use of the phantoms:                                                                                                     | TR 25.914                              |                                                             |                                                 | 0.00                 |
+
+|    |                                                                                                                      |                     |            |         |             |
+|----|----------------------------------------------------------------------------------------------------------------------|---------------------|------------|---------|-------------|
+|    | a) Uncertainty of dielectric properties and shape of the hand phantom                                                | A.12.3              |            |         | 0.00        |
+|    | b) Uncertainty related to the use of laptop ground plane phantom                                                     | A.12.4              |            |         | 0.00        |
+| 19 | Random uncertainty (repeatability)                                                                                   | TS 34.114, E.14     | 0.20       | rect    | 0.12        |
+| 20 | Uncertainty associated with the stirring method and number of subframes (NOTE 3)                                     |                     | see NOTE 3 | std     | see NOTE 3  |
+|    | <b>Stage 2-Calibration measurement</b>                                                                               |                     |            |         | <b>0.00</b> |
+| 21 | Uncertainty of network analyzer<br>- Receiver and Source VNA<br>- Receiver VNA Calibration prior to measurement      | TS 34.114, E.15     | 0.50       | rect    | 0.29        |
+| 22 | Mismatch of transmitter chain                                                                                        | TS 34.114, E.1-E.2  | 0.00       | u-shape | 0.00        |
+| 23 | Insertion loss of transmitter chain                                                                                  | TS 34.114, E.3-E.5  | 0.00       |         | 0.00        |
+| 24 | Mismatch in the connection of calibration antenna                                                                    | TS 34.114, E.1      | 0.00       | rect    | 0.00        |
+| 25 | Influence of the calibration antenna feed cable                                                                      | TS 34.114, E.6      |            |         | 0.00        |
+| 26 | Influence of the transmitter antennas/probes cables                                                                  | TS 34.114, E.6      | 0.00       | rect    | 0.00        |
+| 27 | Uncertainty of the absolute gain of the transmitter antennas/probes                                                  | TS 34.114, E.7      | 0.00       | rect    | 0.00        |
+| 28 | Uncertainty of the absolute gain/radiation efficiency of the calibration antenna                                     | TS 34.114, E.16     | 0.50       | std     | 0.50        |
+| 29 | Chamber statistical ripple and repeatability                                                                         | G.1.2.2             | 0.40       | std     | 0.40        |
+| 30 | Phase Center Offset (when using horn to calibrate)                                                                   | TS 34.114, E.9      | N/A        |         | 0.00        |
+| 31 | Quality of the quiet zone (Range Ref. Antenna)                                                                       | TS 34.114, E.10     | N/A        |         | 0.00        |
+| 32 | Impact of ATF pattern error on TP<br>- DUT RSAP measurement uncertainty TR<br>- DUT RSARP measurement uncertainty TR | TR 37.978<br>10.1&2 | N/A        |         | 0.00        |
+| 33 | Impact of non-ideal isolation between streams in radiated 2nd stage (assuming 15 dB isolation)                       |                     | N/A        |         | 0.00        |
+|    | <b>External Amplifiers</b>                                                                                           |                     |            |         | <b>0.00</b> |
+| 34 | Stability                                                                                                            | B.7.1               |            |         | 0.00        |
+| 35 | Linearity                                                                                                            | B.7.2               |            |         | 0.00        |
+| 36 | Noise Figure                                                                                                         | B.7.3               |            |         | 0.00        |
+| 37 | Mismatch                                                                                                             | B.7.4               |            |         | 0.00        |
+| 38 | Gain                                                                                                                 | B.7.5               |            |         | 0.00        |
+
+NOTE 1: 0dB if fading for RTS is done in baseband; same as RC&CE and MPAC if fading is not in baseband
+
+NOTE 2: assumption is that MU set to 0dB with channel model validation pass/fail limits (FFS) that have negligible impact on TP FOM; MU for channel model validation is FFS
+
+NOTE 3: Analysis of the element associated with stirring method and number of subframes is based on existing harmonization test campaign data and can be further augmented by additional measurements. The following combinations of stirring modes and number of subframes have been identified as common use cases with the following standard uncertainties (different combinations require separate validation):
+
+A: stepped stirring mode with 20k SF per stirring state: 0dB
+
+B: stepped stirring mode with 400 SF per stirring state: 0.22dB
+
+C: continuous stirring mode with 20k SF per sample: FFS
+
+D: continuous stirring mode with 400 SF per sample: FFS
+
+Until MU elements for continuous stirring modes have been defined, the test plan shall only consider stepped stirring approach
+
+NOTE 4: As the applicability of SIR to MIMO OTA performance evaluation is FFS, the measurement uncertainty treatment for SIR related items will remain FFS. When the applicability of SIR is confirmed, the measurement uncertainty treatment defined in 3GPP TS 36.521-1 [12] Table F.1.4-1 for line item 8.2.1.3.1 should be considered along with the related test system constraints. Any adjustments to the test system limits or uncertainty definitions necessary for MIMO OTA performance testing should be applied.
+
+## --- B.6 Fading channel emulator output uncertainty
+
+In the case where a fading channel emulator is used, the outputs of the fading channel emulator are used to drive signals through the amplifiers, if necessary, to the probe antennas in the MIMO OTA tests either as an absolute level or as a relative level. The receiving device used is a UE. Generally, an uncertainty contribution comes from the absolute level accuracy, non-linearity, and output signal stability of the fading channel emulator. All of the contributions should be considered. However, the applicability of each contribution is contingent on the specific measurement implementation and calibration procedure.
+
+This uncertainty should be determined from the manufacturer's data sheet expressed in dB with a rectangular distribution, unless otherwise informed (see clause 5.1.2 in [6]). Furthermore, the uncertainty of the non-linearity and the output signal stability of the device may be included in the absolute level uncertainty. If not, the non-linearity, output signal stability and output signal stability versus temperature should be determined from the manufacturer's data sheet. Once determined, the non-linearity uncertainty and the output signal stability uncertainties should be combined with the output uncertainty using the RSS method.
+
+## --- B.7 External Amplifiers Uncertainty Terms
+
+Any components in the setup can potentially introduce measurement uncertainty. It is then needed to determine the uncertainty contributors associated with the use of such components. For the case of external amplifiers, the following uncertainties should be considered but the applicability is contingent to the measurement implementation and calibration procedure.
+
+### B.7.1 Stability
+
+An uncertainty contribution comes from the output level stability of the amplifier. Even if the amplifier is part of the system for both measurement and calibration, the uncertainty due to the stability shall be considered. This uncertainty can be either measured or determined by the manufacturers' data sheet for the operating conditions in which the system will be required to operate.
+
+### B.7.2 Linearity
+
+An uncertainty contribution comes from the linearity of the amplifier since in most cases calibration and measurements are performed at two different input/output power levels. This uncertainty can be either measured or determined by the manufacturers' data sheet.
+
+### B.7.3 Noise Figure
+
+When the signal goes into an amplifier, noise is added so that the SNR at the output is reduced with regard to the SNR of the signal at the input. This added noise introduces error on the signal which affects the Error Rate of the receiver thus the EVM (Error Vector Magnitude). An uncertainty can be calculated through the following formula:
+
+$$\varepsilon_{EVM} = 20 \cdot \log \left( 1 + 10^{\frac{-SNR}{20}} \right)$$
+
+where SNR is the signal to noise ratio in dB at the signal level used during the sensitivity measurement.
+
+### B.7.4 Mismatch
+
+If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, the mismatch uncertainty at its input and output shall be either measured or determined by the method described in [11].
+
+### B.7.5 Gain
+
+If the external amplifier is used for both stages, measurement and calibration the uncertainty contribution associated with it can be considered systematic and constant -> 0dB. If it is not the case, this uncertainty shall be considered.
+
+# Annex C: Other Environmental Test conditions for consideration
+
+## C.1 Scope
+
+This annex contains non standard channel models which are described for evaluation purposes. Approved channel models are described in Clause 4.2.
+
+## C.2 3D isotropic Channel Models
+
+This clause proposes three 3D isotropic channel models. One of the models is based on the NIST channel model and two of the models are based on the temporal aspects and Base Station (BS) correlation properties of the SCME UMi and SCME UMa channel models.
+
+The proposed 3D isotropic channel models are not directly based on real life operating conditions, rather, are an attempt to model the properties of the reverberation chamber which has been shown to represent a statistically isotropic environment provided sufficient averaging is performed using mode stirring. The instantaneous conditions within the reverberation chamber are not isotropic.
+
+The following 3D isotropic model is based on the PDP and BS correlation of the SCME Urban Micro-cell model with isotropic AoAs and modified XPR values and Velocity.
+
+**Table C.2-1: Short delay spread low correlation channel model**
+
+| Cluster #                                                                                                                                       | Delay [ns] |     |     | Power [dB] |       |       | AoD [°] | AoA <sup>1</sup>                      |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----|-----|------------|-------|-------|---------|---------------------------------------|
+| 1                                                                                                                                               | 0          | 5   | 10  | -3.0       | -5.2  | -7.0  | 6.6     | Average isotropic <sup>1</sup>        |
+| 2                                                                                                                                               | 285        | 290 | 295 | -4.3       | -6.5  | -8.3  | 14.1    | Average isotropic <sup>1</sup>        |
+| 3                                                                                                                                               | 205        | 210 | 215 | -5.7       | -7.9  | -9.7  | 50.8    | Average isotropic <sup>1</sup>        |
+| 4                                                                                                                                               | 660        | 665 | 670 | -7.3       | -9.5  | -11.3 | 38.4    | Average isotropic <sup>1</sup>        |
+| 5                                                                                                                                               | 805        | 810 | 815 | -9.0       | -11.2 | -13.0 | 6.7     | Average isotropic <sup>1</sup>        |
+| 6                                                                                                                                               | 925        | 930 | 935 | -11.4      | -13.6 | -15.4 | 40.3    | Average isotropic <sup>1</sup>        |
+| Delay spread [ns]                                                                                                                               |            |     |     |            |       |       |         | 294                                   |
+| Cluster AS AoD / AS AoA [°]                                                                                                                     |            |     |     |            |       |       |         | 5 / Average isotropic <sup>1</sup>    |
+| Cluster PAS shape                                                                                                                               |            |     |     |            |       |       |         | 3D uniform                            |
+| Total AS AoD / AS AoA [°]                                                                                                                       |            |     |     |            |       |       |         | 18.2 / Average isotropic <sup>1</sup> |
+| Mobile speed [km/h]                                                                                                                             |            |     |     |            |       |       |         | 3, 30                                 |
+| XPR <sup>2</sup>                                                                                                                                |            |     |     |            |       |       |         | 0 dB                                  |
+| NOTE 1: The angles of arrival are said to be Average Isotropic when the incoming field satisfies the Isotropy requirements established in [16]. |            |     |     |            |       |       |         |                                       |
+| NOTE 2: V & H components based on assumed BS antenna array configurations in Clause 7.2.                                                        |            |     |     |            |       |       |         |                                       |
+
+The following 3D isotropic model is based on the PDP and BS correlation of the SCME Urban Macro-cell model with isotropic AoAs and modified XPR values and velocity.
+
+**Table C.2-2: Long delay spread high correlation channel model**
+
+| Cluster #                                                                                                                                       | Delay [ns] |      |      | Power [dB] |       |       | AoD [°] | AoA [°]                              |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|------------|------|------|------------|-------|-------|---------|--------------------------------------|
+|                                                                                                                                                 | 0          | 5    | 10   | -3         | -5.2  | -7    |         |                                      |
+| 1                                                                                                                                               | 0          |      |      | -3         | -5.2  | -7    | 82.0    | Average isotropic <sup>1</sup>       |
+| 2                                                                                                                                               | 360        | 365  | 370  | -5.2       | -7.4  | -9.2  | 80.5    | Average isotropic <sup>1</sup>       |
+| 3                                                                                                                                               | 255        | 260  | 265  | -4.7       | -6.9  | -8.7  | 79.6    | Average isotropic <sup>1</sup>       |
+| 4                                                                                                                                               | 1040       | 1045 | 1050 | -8.2       | -10.4 | -12.2 | 98.6    | Average isotropic <sup>1</sup>       |
+| 5                                                                                                                                               | 2730       | 2735 | 2740 | -12.1      | -14.3 | -16.1 | 102.1   | Average isotropic <sup>1</sup>       |
+| 6                                                                                                                                               | 4600       | 4605 | 4610 | -15.5      | -17.7 | -19.5 | 107.1   | Average isotropic <sup>1</sup>       |
+| Delay spread [ns]                                                                                                                               |            |      |      |            |       |       |         | 839.5                                |
+| Cluster AS AoD / AS AoA [°]                                                                                                                     |            |      |      |            |       |       |         | 2 / Average isotropic <sup>1</sup>   |
+| Cluster PAS shape                                                                                                                               |            |      |      |            |       |       |         | 3D uniform                           |
+| Total AS AoD / AS AoA [°]                                                                                                                       |            |      |      |            |       |       |         | 7.9 / Average isotropic <sup>1</sup> |
+| Mobile speed [km/h]                                                                                                                             |            |      |      |            |       |       |         | 3, 30                                |
+| XPR <sup>2</sup>                                                                                                                                |            |      |      |            |       |       |         | 0 dB                                 |
+| NOTE 1: The angles of arrival are said to be average isotropic when the incoming field satisfies the isotropy requirements established in [16]. |            |      |      |            |       |       |         |                                      |
+| NOTE 2: V & H components based on assumed BS antenna array configurations in Clause 7.2.                                                        |            |      |      |            |       |       |         |                                      |
+
+The following 3D isotropic model is based on the NIST model with isotropic AoAs and added XPR values and Velocity. The cluster model described below is a simplification of the full model, where a continuous exponential decaying power transfer function with an RMS delay spread of 80 ns is obtained.
+
+**Table C.2-3: Isotropic model based on the NIST channel model**
+
+| Cluster #                                                                                                                                       | Delay [ns] | Power [dB] | AoD [°] | AoA [°]                              |
+|-------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|---------|--------------------------------------|
+| 1                                                                                                                                               | 0          | 0.0        | N/A     | Average isotropic <sup>1</sup>       |
+| 2                                                                                                                                               | 40         | -1.7       | N/A     | Average isotropic <sup>1</sup>       |
+| 3                                                                                                                                               | 120        | -5.2       | N/A     | Average isotropic <sup>1</sup>       |
+| 4                                                                                                                                               | 180        | -7.8       | N/A     | Average isotropic <sup>1</sup>       |
+| 5                                                                                                                                               | 210        | -9.1       | N/A     | Average isotropic <sup>1</sup>       |
+| 6                                                                                                                                               | 260        | -11.3      | N/A     | Average isotropic <sup>1</sup>       |
+| 7                                                                                                                                               | 350        | -15.2      | N/A     | Average isotropic <sup>1</sup>       |
+| Delay spread [ns]                                                                                                                               |            |            |         | 80                                   |
+| Cluster AS AoD / AS AoA [°]                                                                                                                     |            |            |         | N/A / Average isotropic <sup>1</sup> |
+| Cluster PAS shape                                                                                                                               |            |            |         | 3D uniform                           |
+| Total AS AoD / AS AoA [°]                                                                                                                       |            |            |         | N/A / Average isotropic <sup>1</sup> |
+| Mobile speed [km/h]                                                                                                                             |            |            |         | 1                                    |
+| XPR <sup>2</sup>                                                                                                                                |            |            |         | 0 dB                                 |
+| NOTE 1: The angles of arrival are said to be average isotropic when the incoming field satisfies the isotropy requirements established in [16]. |            |            |         |                                      |
+| NOTE 2: V & H components based on assumed BS antenna array configurations in Clause 7.2.                                                        |            |            |         |                                      |
+
+The parameters of the channel models are the expected parameters for the MIMO OTA channel models. However, the final channel model achieved for different methods could be a combined effect of the chamber and the channel emulator.
+
+The Rayleigh fading may be implementation specific. However, the fading can be considered to be appropriate as long as the statistics of the generated Rayleigh fading are within standard requirement on Rayleigh fading statistics.
+
+## C.3 Verification of Channel Model implementations
+
+Channel Models have been specified in Clause C.2.
+
+This clause describes the MIMO OTA validation measurements, in order to ensure that the channel models are correctly implemented and hence capable of generating the propagation environment, as described by the model, within a test area. Measurements are done mainly with a Vector Network Analyzer (VNA) and a spectrum analyzer.
+
+### C.3.1 Measurement instruments and setup
+
+The measurement setup includes the following equipment:
+
+**Table C.3.1-1: Measurement equipment list for the verification procedure**
+
+| Item | Quantity | Item                  |
+|------|----------|-----------------------|
+| 1    | 1        | Channel Emulator      |
+| 2    | 1        | Signal Generator      |
+| 3    | 1        | Spectrum Analyzer     |
+| 4    | 1        | VNA                   |
+| 5    | 1        | Electric Dipole       |
+| 6    | 1        | Wideband test antenna |
+
+#### C.3.1.1 Vector Network Analyzer (VNA) setup
+
+Most of the measurements are performed with a VNA. An example set of equipment required for this set-up is shown in Figure C.3.1.1-1. VNA transmits frequency sweep signals through the MIMO OTA test system.
+
+A test antenna, within the test area, receives the signal and VNA analyzes the frequency response of the system.
+
+A number of traces (frequency responses) are measured and recorded by VNA and analyzed by a post processing SW, e.g., Matlab. Special care has to be taken into account to keep the fading conditions unchanged, i.e. frozen, during the short period of time of a single trace measurement. The fading may proceed only in between traces. This setup can be used to measure PDP, BS antenna correlation, Rayleigh fading and Isotropy of the Channel models defined in Clause C.2.
+
+![Figure C.3.1.1-1: Setup for VNA measurements for reverberation chamber and channel emulator methods. The diagram shows a VNA (ports 1, 2, 3) connected to a Channel Emulator (CE). The CE is connected to multiple measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles phi-hat, rho-hat, and z-hat.](e01c6273c4177746475715ee9c17a882_img.jpg)
+
+The diagram illustrates the setup for VNA measurements. A VNA with three ports (1, 2, 3) is connected to a Channel Emulator (CE). The CE is connected to multiple measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles  $\hat{\phi}$ ,  $\hat{\rho}$ , and  $\hat{z}$ .
+
+Figure C.3.1.1-1: Setup for VNA measurements for reverberation chamber and channel emulator methods. The diagram shows a VNA (ports 1, 2, 3) connected to a Channel Emulator (CE). The CE is connected to multiple measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles phi-hat, rho-hat, and z-hat.
+
+Figure C.3.1.1-1: Setup for VNA measurements for reverberation chamber and channel emulator methods
+
+![Figure C.3.1.1-2: Setup for VNA measurements for reverberation chamber-only methods. The diagram shows a VNA (ports 1, 2, 3) connected directly to measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles phi-hat, rho-hat, and z-hat.](d579d14979ebeaa676740df2e3dbe024_img.jpg)
+
+The diagram illustrates the setup for VNA measurements. A VNA with three ports (1, 2, 3) is connected directly to measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles  $\hat{\phi}$ ,  $\hat{\rho}$ , and  $\hat{z}$ .
+
+Figure C.3.1.1-2: Setup for VNA measurements for reverberation chamber-only methods. The diagram shows a VNA (ports 1, 2, 3) connected directly to measurement antennas inside a chamber. A test antenna is mounted on a turntable inside the chamber, with a stirrer. Coordinate axes x, y, z are shown, and the test antenna is oriented with angles phi-hat, rho-hat, and z-hat.
+
+Figure C.3.1.1-2: Setup for VNA measurements for reverberation chamber-only methods
+
+#### C.3.1.2 Spectrum Analyzer (SA) setup
+
+The Doppler spectrum is measured with a Spectrum Analyzer as shown in Figure C.3.1.2-1. In this case a Signal generator transmits CW signal through the MIMO OTA test system. The signal is received by a test antenna within the test area. Finally the signal is analyzed by a Spectrum Analyzer and the measured spectrum is compared to the target spectrum. This setup can be used to measure Doppler Spectrum of the Channel models defined in Clause C.2.
+
+![Figure C.3.1.2-1: Setup for SA measurements for reverberation chamber and channel emulator methods. The diagram shows a Signal Generator connected to a CE (Channel Emulator). The CE is connected to two measurement antennas inside a rectangular Chamber. A Spectrum Analyzer is connected to a Test Antenna inside the chamber. The Test Antenna is mounted on a Turntable. A Stirrer is also present inside the chamber. A 3D coordinate system is shown with axes x, y, and z. At the turntable, unit vectors are labeled as $\hat{z}$, $\hat{\phi}$, and $\hat{\rho}$.](4f7470055bfc22c4aa6b007a4056940e_img.jpg)
+
+Figure C.3.1.2-1: Setup for SA measurements for reverberation chamber and channel emulator methods. The diagram shows a Signal Generator connected to a CE (Channel Emulator). The CE is connected to two measurement antennas inside a rectangular Chamber. A Spectrum Analyzer is connected to a Test Antenna inside the chamber. The Test Antenna is mounted on a Turntable. A Stirrer is also present inside the chamber. A 3D coordinate system is shown with axes x, y, and z. At the turntable, unit vectors are labeled as \$\hat{z}\$, \$\hat{\phi}\$, and \$\hat{\rho}\$.
+
+**Figure C.3.1.2-1: Setup for SA measurements for reverberation chamber and channel emulator methods**
+
+![Figure C.3.1.2-3: Setup for SA measurements for reverberation chamber-only methods. This diagram is similar to the previous one but without the CE. The Signal Generator is connected directly to the measurement antennas inside the Chamber. The Spectrum Analyzer is connected to the Test Antenna on the Turntable. The chamber also contains a Stirrer. The same coordinate system (x, y, z) and unit vectors ($\hat{z}$, $\hat{\phi}$, $\hat{\rho}$) are depicted.](2df1e34671c73d7c0d047d4e9009251e_img.jpg)
+
+Figure C.3.1.2-3: Setup for SA measurements for reverberation chamber-only methods. This diagram is similar to the previous one but without the CE. The Signal Generator is connected directly to the measurement antennas inside the Chamber. The Spectrum Analyzer is connected to the Test Antenna on the Turntable. The chamber also contains a Stirrer. The same coordinate system (x, y, z) and unit vectors (\$\hat{z}\$, \$\hat{\phi}\$, \$\hat{\rho}\$) are depicted.
+
+**Figure C.3.1.2-3: Setup for SA measurements for reverberation chamber-only methods**
+
+### C.3.2 Validation measurements
+
+#### C.3.2.1 Power Delay Profile (PDP)
+
+This measurement checks that the resulting Power Delay Profile (PDP) is as defined in the channel model.
+
+**Method of measurement:**
+
+Step the chamber stirring sequence and store traces from VNA measurements at each step until the Number of Traces specified in Table C.3.2.1-1 is obtained. For the RC+CE, also the channel model emulation will be stepped for each VNA trace.
+
+The VNA sampling should be such that independent samples of the channel model impulse response are obtained. This is ensured if the effective distance travelled by the UE between faded samples of the channel model is as defined in the table below, regardless of the number of stirring positions in the chamber stirring sequence. To accurately emulate the longest PDP duration  $t_f$  of 5  $\mu\text{s}$ , the relationship  $N/\text{Span} = t_f$  must be satisfied.
+
+VNA settings:
+
+**Table C.3.2.1-1: VNA settings for PDP**
+
+| Item                                                                                             | Unit              | Value                                                            |
+|--------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------|
+| Center frequency                                                                                 | MHz               | Downlink Center Frequency in 36.508 [19]<br>as required per band |
+| Span                                                                                             | MHz               | 200                                                              |
+| RF output level                                                                                  | dBm               | 0                                                                |
+| Number of traces                                                                                 |                   | 1000                                                             |
+| Effective distance traveled by UE between faded channel model samples                            | wavelength (Note) | > 2                                                              |
+| Number of points in the trace                                                                    |                   | 1101                                                             |
+| Averaging                                                                                        |                   | 1                                                                |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda/\text{s}$ ]                        |                   |                                                                  |
+| MS speed [ $\lambda/\text{s}$ ] = MS speed [m /s] / Speed of light [m/s] * Center frequency [Hz] |                   |                                                                  |
+
+**Channel model specification:**
+
+**Table C.3.2.1-2: Channel model specification for PDP**
+
+| Item                  | Unit       | Value                                                            |
+|-----------------------|------------|------------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink Center Frequency in 36.508 [19]<br>as required per band |
+| Channel model samples | wavelength | > 2000                                                           |
+| Channel model         |            | As specified in Clause C.2                                       |
+
+**Method of measurement result analysis:**
+
+Measured VNA traces (frequency responses  $H(t,f)$ ) are saved into a hard drive. The data is read into, e.g., Matlab. The analysis is performed by taking the Fourier transform of each frequency response. The resulting impulse responses  $h(t, \tau)$  are averaged in power over time (or samples):
+
+Finally the resulting PDP is shifted in delay, such that the first tap is on delay zero.
+
+The reference PDP plots from Table C.2-1, Table C.2-2 and Table C.2-3 are shown in Figure C.3.2.1-1.
+
+In a reverberation chamber, when a channel emulator is not used and the PDP is therefore an exponential decay, such as the NIST channel model, only the inherent RMS Delay Spread of the reverberation chamber needs to be calculated. The selection of the  $T h_i(t, \tau)$  measurements has to be performed when the absorber loading technique is used to tune the RMS DS in an RC. Alternatively, the sample selection technique allows for selecting a subset of  $M h_i(t, \tau)$  measurements which provide the desired RMS DS, and in this case the averaging has to be performed only over the selected subset of  $M$  channel impulse responses.
+
+The calculation of RMS delay spread is performed on the time domain data as the square root of the second central moment of the PDP, that is:
+
+$$\sigma_{\tau} = \sqrt{\sum_{\tau} \tau^2 \frac{PDP(\tau)}{\sum_{\tau} PDP(\tau)} - \left( \sum_{\tau} \tau \frac{PDP(\tau)}{\sum_{\tau} PDP(\tau)} \right)^2}$$
+
+Only PDP values above a threshold of -60 dB should be included in the calculation of the RMS delay spread.
+
+The expected RMS delay spread for the NIST channel model is 80 ns.
+
+**OTA antenna configuration:** Fixed measurement source antenna.
+
+**Measurement antenna:**
+
+A suitable wideband test antenna.
+
+**Tolerances:**
+
+Performance bounds of (cluster power  $\pm 0.85$  dB and excess delay  $\pm 11$  ns).
+
+![Figure C.3.2.1-1: Reference PDP values for the short delay spread low correlation and long delay spread high correlation and NIST channel models plotted from Table C.2-1, Table C.2-2 and Table C.2-3. The figure contains three subplots: 1. 'PDP, SCME Urban micro, Table 6.2-1' showing magnitude (dB) vs delay (ns) with discrete impulses. 2. 'PDP, SCME Urban macro, Table 6.2-3' showing magnitude (dB) vs delay (ns) with discrete impulses. 3. 'Delay profile' showing Relative Path Power (dB) vs Delay (ns) as a bar chart.](ca1e31c6a55f9221c960f1fbce96e589_img.jpg)
+
+Figure C.3.2.1-1: Reference PDP values for the short delay spread low correlation and long delay spread high correlation and NIST channel models plotted from Table C.2-1, Table C.2-2 and Table C.2-3. The figure contains three subplots: 1. 'PDP, SCME Urban micro, Table 6.2-1' showing magnitude (dB) vs delay (ns) with discrete impulses. 2. 'PDP, SCME Urban macro, Table 6.2-3' showing magnitude (dB) vs delay (ns) with discrete impulses. 3. 'Delay profile' showing Relative Path Power (dB) vs Delay (ns) as a bar chart.
+
+**Figure C.3.2.1-1: Reference PDP values for the short delay spread low correlation and long delay spread high correlation and NIST channel models plotted from Table C.2-1, Table C.2-2 and Table C.2-3**
+
+#### C.3.2.2 Doppler for 3D isotropic models
+
+This measurement checks that the resulting is as defined in the channel model.
+
+**Doppler. Method of measurement:**
+
+For Doppler validation, two methods could be used to measure the Doppler spectrum. The first uses a CW tone from the Signal Generator fed directly, or via the channel emulator if used, to the fixed measurement antennas and is recorded by the spectrum analyzer. For the second method, the input signal from the VNA is fed directly, or via the channel emulator if used, to the fixed measurement antennas of the chamber.
+
+For the first method, a sine wave (CW, carrier wave) signal is transmitted from the signal generator. The signal is connected from the signal generator to the channel emulator via cables, or alternatively directly fed to the chamber measurement antenna for the RC methodology. For the RC+CE methodology, the channel emulator output signals are then transferred via cables to the fixed measurement antennas (possibly via amplifiers). The fixed measurement antennas radiate the signals over the air to the test antenna. The Doppler spectrum is measured by the spectrum analyzer having the stirring sequence and, if applicable, the channel emulation active and the trace is saved. The signal generator and the spectrum analyzer reference oscillators should be synchronized, in order to minimize frequency shift etc.
+
+Alternatively, the Doppler spectrum can be measured with a VNA. Frequency sweeps are measured with the VNA for a complete stirring sequence, thus collecting samples of the chamber transfer function for each fixed stirrer position. To get a correct estimate of the Doppler power spectrum, the spatial distance between the stirrer positions should be small enough to satisfy Nyquist theorem. is Fourier transformed according to
+
+The Doppler spectrum can then be calculated using
+
+The discrete Doppler power spectrum will now have a frequency axis ranging from 0 to N-1, where N is the number of stirrer positions used. To convert this into a Doppler frequency domain, the sampling theorem gives a frequency axis in the interval [,, where
+
+and the frequency step between each Doppler frequency sample is given by
+
+is the time step between the measured samples.
+
+##### **Signal generator settings:**
+
+**Table C.3.2.2-1: Signal generator settings for Doppler**
+
+| Item             | Unit | Value                                                         |
+|------------------|------|---------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 36.508 [19] as required per band |
+| Output level     | dBm  | 0                                                             |
+| Modulation       |      | OFF                                                           |
+
+##### **Spectrum analyzer settings:**
+
+**Table C.3.2.2-2: Spectrum analyzer settings for Doppler**
+
+| Item             | Unit | Value                                                         |
+|------------------|------|---------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 36.508 [19] as required per band |
+| Span             | Hz   | 3x maximum Doppler                                            |
+| RBW              | Hz   | 1                                                             |
+| VBW              | Hz   | 1                                                             |
+| Number of points |      | 101                                                           |
+| Averaging        |      | 100                                                           |
+
+##### **VNA settings**
+
+**Table C.3.2.2-3: VNA settings for Doppler**
+
+| Item             | Unit | Value                                                         |
+|------------------|------|---------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 36.508 [19] as required per band |
+| Span             | MHz  | Downlink portion of frequency band                            |
+| RF output level  | dBm  | 0                                                             |
+| Number of traces |      | 600                                                           |
+| Number of points |      | 1401                                                          |
+| Averaging        |      | 1                                                             |
+
+##### **Channel model specification:**
+
+**Table C.3.2.2-4: Channel model specification for Doppler**
+
+| Item             | Unit | Value                                                         |
+|------------------|------|---------------------------------------------------------------|
+| Center frequency | MHz  | Downlink center frequency in 36.508 [19] as required per band |
+| Channel model    |      | As specified in Clause C.2                                    |
+
+##### **Method of Measurement Result Analysis:**
+
+Calculate the square root of the second central moment of the Doppler spectrum from center frequency to the frequency corresponding to -30 dB (make sure that no noise is included in the calculations). Use the value obtained ( $\Delta f$ ) to calculate the equivalent speed ( $\Delta v$ ) using the following equation:
+
+$$\Delta v = \frac{\Delta f * c}{f_0}$$
+
+where  $c$  is the speed of light and  $f_0$  is the carrier frequency.
+
+The reference classical Doppler spectrum is shown in figure C.3.2.2-1.  $B_d$  is the maximum Doppler shift expected for the mobile speed used for the measurements.
+
+![Figure C.3.2.2-1: Reference Doppler Spectrum for Jake's fading models. The graph shows a U-shaped curve labeled 'DOPPLER SPECTRUM' on a plot of power versus frequency ('FREQ.'). The curve is symmetric about the center frequency (0 Hz) and is bounded by two vertical dashed lines at -B_d and B_d. The curve has a minimum at the center frequency and increases towards the boundaries at -B_d and B_d.](785ffdb80d7fb12f2eee04b161106715_img.jpg)
+
+Figure C.3.2.2-1: Reference Doppler Spectrum for Jake's fading models. The graph shows a U-shaped curve labeled 'DOPPLER SPECTRUM' on a plot of power versus frequency ('FREQ.'). The curve is symmetric about the center frequency (0 Hz) and is bounded by two vertical dashed lines at -B\_d and B\_d. The curve has a minimum at the center frequency and increases towards the boundaries at -B\_d and B\_d.
+
+**Figure C.3.2.2-1: Reference Doppler Spectrum for Jake's fading models**
+
+**OTA antenna configuration:** Fixed measurement source antennas.
+
+**Measurement antenna:** A suitably wideband test antenna.
+
+##### **Tolerances:**
+
+The equivalent speed obtained shall be within 30 km/h +/- 5 km/h.
+
+#### C.3.2.3 Base Station antenna correlation for 3D isotropic models
+
+This measurement checks that the resulting Base Station (BS) antenna correlation follows the computed values from the channel parameters given in tables C.2-1, C.2-2 and C.2-3.
+
+##### **Method of measurement:**
+
+For correlation validation, the input signal from the VNA is fed directly (for table C.2-3), or via the channel emulator (for tables C.2-1 and C.2-2), to the fixed measurement antennas of the reverberation chamber.
+
+Step the chamber stirring sequence and store traces from VNA measurements at each step until the Number of Traces specified in Table C.3.2.3-1 is obtained. For the RC+CE, also the channel model emulation will be stepped for each VNA trace.
+
+Each of the paths for the two transmit streams must be measured separately using the procedure above. The samples for each path must be taken for the exact same channel emulator and stirring positions.
+
+The VNA sampling should be such that independent samples of the channel model impulse response are obtained. This is ensured if the effective distance travelled by the UE between faded samples of the channel model is as defined in the table below.
+
+##### **VNA settings:**
+
+**Table C.3.2.3-1: VNA settings for BS antenna correlation**
+
+| Item                                                                                      | Unit              | Value                                                         |
+|-------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------|
+| Center frequency                                                                          | MHz               | Downlink center frequency in 36.508 [19] as required per band |
+| Span                                                                                      | MHz               | Same as signal bandwidth                                      |
+| RF output level                                                                           | dBm               | 0                                                             |
+| Number of traces                                                                          |                   | 600                                                           |
+| Effective distance traveled by UE between faded channel model samples                     | wavelength (Note) | > 2                                                           |
+| Number of points                                                                          |                   | Configured to obtain 1 MHz step size                          |
+| Averaging                                                                                 |                   | 1                                                             |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]                        |                   |                                                               |
+| MS speed [ $\lambda$ /s] = MS speed [m /s] / Speed of light [m/s] * Center frequency [Hz] |                   |                                                               |
+
+##### **Channel model specification:**
+
+**Table C.3.2.3-2: Channel model specification for BS antenna correlation**
+
+| Item                  | Unit       | Value                                                         |
+|-----------------------|------------|---------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink center frequency in 36.508 [19] as required per band |
+| Channel model samples | wavelength | > 2000                                                        |
+| Channel model         |            | As specified in Clause C.2                                    |
+
+##### **Method of Measurement Results Analysis**
+
+Compute the correlation between two traces (e.g. S21 and S31) which represents the correlation between two transmit streams. This correlation should match that of the channel model used.
+
+**OTA antenna configuration:** Fixed measurement source antennas.
+
+**Measurement antenna:** A suitably wideband test antenna.
+
+##### **Tolerances:**
+
+The amplitude of the complex correlation averaged over the channel bandwidth shall be within the interval 0.05 – 0.2.
+
+#### C.3.2.4 Rayleigh fading
+
+This measurement checks that the resulting fading of the MIMO OTA system is Rayleigh as per the channel model.
+
+##### **Method of measurement:**
+
+For Rayleigh Fading validation, the input signal from the VNA is fed to one of the two input ports of the channel emulator and further to the fixed measurement transmit antennas of the reverberation chamber. The same stirring sequence, number of active CE output ports, channel model and CE channel model emulation as used for the DUT measurement, as well as the chamber loading used for the DUT measurement and PDP validation, should be used for the validation measurement.
+
+In order to achieve statistical significance, the number of samples should be >1000. If the DUT stirring sequence has less than 1000 steps, the number of measurements shall be increased proportionally without altering the fading envelope distribution. This is done reducing the CE IR, and the stirring step by dividing them by an N value such as the resultant number of measurements will be > 1000 while keeping the same amplitude distribution. e.g. if the stirring sequence has 120 steps, and for every measurement the stirrers move equally 9 degrees, then using N = 9 for 1080 samples will result
+
+in changing the stirring sequence to 1 degree per measurement for all the stirrers, and dividing the IR step by 9. If needed, the IR should be rounded to the closest integer.
+
+Step the chamber stirring sequence and store traces from VNA measurements at each step until the Number of Traces specified in Table C.3.2.4-1 is obtained. For the RC+CE, also the channel model emulation will be stepped for each VNA trace.
+
+The VNA sampling should be such that independent samples of the channel model impulse response are obtained. This is ensured if the effective distance travelled by the UE between faded samples of the channel model is as defined in the table below.
+
+The procedure described above shall be performed in two of the extreme test volume validation positions (TVVPs) defined in Annex G. Observe that each TVVP consists of three orientations, which means that in total 6 Rayleigh validation measurements shall be performed and the results from each of these measurements shall pass the limits. The same stirring sequence, number of active CE output ports, channel model and CE channel model emulation shall be used at each of the chosen TVVPs.
+
+##### VNA settings:
+
+**Table C.3.2.4-1: VNA settings for Rayleigh fading**
+
+| Item                                                                                                                                                                | Unit              | Value                                                         |
+|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------------------------------------------------|
+| Center frequency                                                                                                                                                    | MHz               | Downlink center frequency in 36.508 [19] as required per band |
+| Span                                                                                                                                                                | MHz               | Same as signal bandwidth                                      |
+| RF output level                                                                                                                                                     | dBm               | 0                                                             |
+| Number of traces                                                                                                                                                    |                   | >1000                                                         |
+| Effective distance traveled by UE between faded channel model samples                                                                                               | wavelength (Note) | > 2                                                           |
+| Number of points                                                                                                                                                    |                   | Configured to obtain 1 MHz step size                          |
+| Averaging                                                                                                                                                           |                   | 1                                                             |
+| NOTE: Time [s] = distance [ $\lambda$ ] / MS speed [ $\lambda$ /s]<br><br>MS speed [ $\lambda$ /s] = MS speed [m /s] / Speed of light [m/s] * Center frequency [Hz] |                   |                                                               |
+
+##### Channel model specification:
+
+**Table C.3.2.4-2: Channel model specification for Rayleigh fading**
+
+| Item                  | Unit       | Value                                                         |
+|-----------------------|------------|---------------------------------------------------------------|
+| Center frequency      | MHz        | Downlink Center Frequency in 36.508 [19] as required per band |
+| Channel model samples | wavelength | > 2 x Number of traces                                        |
+| Channel model         |            | As specified in Annex C.2                                     |
+
+##### Method of Measurement Results Analysis
+
+The primary performance criterion to evaluate Rayleigh fading is the Cumulative Distribution Function (CDF) of the received signal amplitude ( $x$ ) at the DUT. CDF describes the probability of a signal level being less than the CDF parameter. The CDF of  $x$  in a set of measured samples in a reverberation chamber is defined as,
+
+![Figure C.3.2.4-1: Reference Rayleigh distribution. A line graph showing the Rayleigh distribution curve. The x-axis is labeled 'x' and ranges from 0 to 3 with major ticks every 0.5 units. The y-axis is labeled 'Rayleigh Distribution' and ranges from 0 to 1 with major ticks every 0.1 units. The curve starts at (0,0), rises to a peak of approximately 0.92 at x ≈ 0.7, and then decays towards zero, reaching about 0.1 at x = 1.5 and near zero by x = 2.5.](26e4d6ae09790488a51e9171a1df0357_img.jpg)
+
+Figure C.3.2.4-1: Reference Rayleigh distribution. A line graph showing the Rayleigh distribution curve. The x-axis is labeled 'x' and ranges from 0 to 3 with major ticks every 0.5 units. The y-axis is labeled 'Rayleigh Distribution' and ranges from 0 to 1 with major ticks every 0.1 units. The curve starts at (0,0), rises to a peak of approximately 0.92 at x ≈ 0.7, and then decays towards zero, reaching about 0.1 at x = 1.5 and near zero by x = 2.5.
+
+**Figure C.3.2.4-1: Reference Rayleigh distribution**
+
+The difference between the measured histogram of CDF (also known as empirical CDF, ECDF) and ideal histogram is computed within the framework of the Chi-Square test [3] to determine if the chamber provides a Rayleigh fading. The Chi-Square test is a purely statistical test for determining if the observed data ECDF follows the theoretic CDF. The Chi-Square test is performed as follows [21].
+
+1. Partition the measured sample space (N samples) into K disjoint intervals (bins).
+2. Calculate the number  $m_i$  of samples that fall in each of these intervals. This is a measure of the probability that the outcome will fall in that interval.
+3. Compare the Rayleigh CDF obtained from the measured data to the theoretical probability distribution using the Chi-Square test.
+
+The Chi-Square statistic is defined as the “weighted square error” and is given by
+
+$$\chi^2 = \sum_{i=1}^K \frac{(m_i - Np_i)^2}{Np_i}$$
+
+Here, N is the number of samples,  $p_i$  is the theoretical probability of landing in the bin with index i, and  $m_i$  is the measured number of samples in the bin with index i. K=15 shall be used for the validation. The theoretical value  $p_i$  is given in Table C.3.2.4-3 below.
+
+Due to the statistical variations of the chi-squared value, the final reported value should be obtained by averaging the chi-squared values obtained for each frequency point in the signal bandwidth. This averaged value should be compared to the limit.
+
+**Table C.3.2.4-3: Theoretical probability distribution for the Rayleigh distribution with 15 bins**
+
+| Bin limit (min) | Bin limit (max) | p <sub>i</sub> |
+|-----------------|-----------------|----------------|
+| 0.00000         | 0.06899         | 1/15           |
+| 0.06899         | 0.14310         | 1/15           |
+| 0.14310         | 0.22314         | 1/15           |
+| 0.22314         | 0.31015         | 1/15           |
+| 0.31015         | 0.40547         | 1/15           |
+| 0.40547         | 0.51083         | 1/15           |
+| 0.51083         | 0.62861         | 1/15           |
+| 0.62861         | 0.76214         | 1/15           |
+| 0.76214         | 0.91629         | 1/15           |
+| 0.91629         | 1.09861         | 1/15           |
+| 1.09861         | 1.32176         | 1/15           |
+| 1.32176         | 1.60944         | 1/15           |
+| 1.60944         | 2.01490         | 1/15           |
+| 2.01490         | 2.70805         | 1/15           |
+| 2.70805         | +infinity       | 1/15           |
+
+Note: These limits are given as Watt ratios.
+
+According to [22], a chi-squared value less than or equal to 27.69 will mean that the numbers are Rayleigh distributed (1% significance level).
+
+It also needs to be verified that there is no strong LOS component present. This is done by evaluating the ratio of the direct path component to the scattered component (also known as K-factor). If there is no direct component present, then K = 0, K = -∞ dB.
+
+$$K = \frac{(| < S_{21} > |)^2}{(< |S_{21} - < S_{21} > |^2 >)}$$
+
+The maximum allowed K-factor is -10dB, anything higher than will be considered a failure.
+
+![Scattered Plot of Measured S21 with no LOS component present. The plot shows a dense cloud of blue diamond-shaped data points centered around the origin (0,0) on a coordinate system ranging from -0.5 to 0.5 on both axes. A single red square is located at the origin (0,0).](6784f8ce8ef7f7f05e0b53eb5c24f59f_img.jpg)
+
+Scattered Plot of Measured S21 with no LOS component present. The plot shows a dense cloud of blue diamond-shaped data points centered around the origin (0,0) on a coordinate system ranging from -0.5 to 0.5 on both axes. A single red square is located at the origin (0,0).
+
+**Figure C.3.2.4-2: Scattered Plot of Measured S21 with no LOS component present.**
+
+**OTA antenna configuration:** Fixed measurement source antennas.
+
+**Measurement antenna:** A suitably wideband test antenna.
+
+#### C.3.2.5 Isotropy for 3D isotropic models
+
+This measurement checks that the resulting received signal characteristics are statistically spatially isotropic.
+
+##### Method of measurement:
+
+For isotropic validation, the input signal from the VNA is fed directly, or via the channel emulator, to the fixed measurement antennas of the reverberation chamber. If a channel emulator is used, it has to be placed in Bypass mode where no fading is used. An electric dipole is placed on the turn table.
+
+Three orthogonal components of the electric field are recorded with the dipole in three different orientations. The same stirring sequence as used for the DUT measurement, as well as the chamber loading used for the DUT measurement and PDP validation, should be used for the validation measurement.
+
+Step the chamber stirring sequence and store traces from VNA measurements at each step until the Number of Traces specified in Table C.3.2.5-1 is obtained. Repeat this procedure with the dipole in all three orthogonal orientations.
+
+##### VNA settings:
+
+**Table C.3.2.5-1: VNA settings for isotropy**
+
+| Item                                             | Unit | Value                                                         |
+|--------------------------------------------------|------|---------------------------------------------------------------|
+| Center frequency                                 | MHz  | Downlink center frequency in 36.508 [19] as required per band |
+| Span                                             | MHz  | Same as signal bandwidth                                      |
+| RF output level                                  | dBm  | 0                                                             |
+| Number of traces per receive antenna orientation |      | Same as in DUT measurement                                    |
+| Number of points                                 |      | Configured to obtain 1 MHz step size                          |
+| Averaging                                        |      | 1                                                             |
+
+##### Method of Measurement Results Analysis
+
+Compute and evaluate the anisotropy coefficients from the measured data as described in [2]. Using S parameters, the anisotropy coefficient that employs two orientations may be given as
+
+$$A_{pq}(n) = (|S_{21,p}(n)|^2 - |S_{21,q}(n)|^2) / (|S_{21,p}(n)|^2 + |S_{21,q}(n)|^2),$$
+
+where  $p < q = 1, 2, 3$ . The total anisotropy coefficient that takes into account all three orientations is given by
+
+$$A_{tot}(n) = \sqrt{\{[A_{12}(n)]^2 + [A_{13}(n)]^2 + [A_{23}(n)]^2\} / 3}.$$
+
+The cumulative distribution functions (CDFs) for the ideal anisotropy coefficients are shown in figure C.3.2.5-1, where the left plot applies to  $A_{pq}(n)$  and the right plot applies to  $A_{tot}(n)$ .
+
+![Figure C.3.2.5-1: Reference anisotropy coefficients for two orientations (Apq) and for three orientations (Atot). The figure contains two plots. The left plot, titled 'Two Orientations', shows the CDF of Apq(n) on the y-axis (ranging from 0 to 1) against Apq on the x-axis (ranging from -1 to 1). The curve is a straight line from (0,0) to (1,1). The right plot, titled 'Three Orientations', shows the CDF of Atot(n) on the y-axis (ranging from 0 to 1) against Atot on the x-axis (ranging from 0 to 1). The curve is an S-shaped curve starting at (0,0) and ending at (1,1).](f81154fc60dd0722df3c247514f141e6_img.jpg)
+
+Figure C.3.2.5-1: Reference anisotropy coefficients for two orientations (Apq) and for three orientations (Atot). The figure contains two plots. The left plot, titled 'Two Orientations', shows the CDF of Apq(n) on the y-axis (ranging from 0 to 1) against Apq on the x-axis (ranging from -1 to 1). The curve is a straight line from (0,0) to (1,1). The right plot, titled 'Three Orientations', shows the CDF of Atot(n) on the y-axis (ranging from 0 to 1) against Atot on the x-axis (ranging from 0 to 1). The curve is an S-shaped curve starting at (0,0) and ending at (1,1).
+
+**Figure C.3.2.5-1: Reference anisotropy coefficients for two orientations ( $A_{pq}$ ) and for three orientations ( $A_{tot}$ )**
+
+NOTE: These figures have been provided by the National Institute of Standards and Technology in USA.
+
+The differences between the measured CDF of  $A_{pq}(n)$ ,  $A_{tot}(n)$  and their ideal CDF's are computed within the framework of the chi-square test [3] to determine if the chamber is isotropic. The chi-square test is a statistical test for determining whether the CDF of the observed data for  $A_{pq}(n)$ , and  $A_{tot}(n)$  are significantly different from the ideal. The chi-square test is performed as follows [21].
+
+1. Sort the N measured values of  $A_{pq}(n)$ , and  $A_{tot}$  into the K equal, disjoint intervals (bins) specified in the first two columns of Table C.3.2.5-1A and C.3.2.5-2, with  $K = 10$ , and  $K = 11$  respectively.
+2. Count the number  $M_k$  of measured samples of  $A_{pq}(n)$ , and  $A_{tot}$  that fall in the kth interval. It is necessary that at least 5 measured samples fall into each interval.
+3. For  $A_{pq}(n)$  the numbers of samples per bin are equal, therefore  $p_i = N/10$ . For  $A_{tot}(n)$  calculate the probability  $p_k$  of samples for each bin from the ideal CDF in the kth interval. Table C.3.2.5-2 provides the values of  $p_k$  for  $K = 11$  bins.
+4. Compare the  $M_k$  with the expected number obtained from the ideal CDF  $p_k$  using the chi-square test as follows.
+
+$$\chi^2 = \sum (M_k - N p_k)^2 / (N p_k).$$
+
+The summation over bins goes from  $k=1$  to  $K$ .
+
+Due to the statistical variations of the chi-squared value, the final reported value should be obtained by averaging the chi-squared values obtained for each frequency point in the signal bandwidth. This averaged value should be compared to the limit.
+
+**Table C.3.2.5-1A: Expected Count for 2 Orientations Anisotropy Coefficients with 10 bins**
+
+| Bin limit (min) | Bin limit (max) | $p_i$ |
+|-----------------|-----------------|-------|
+| -1.0            | -0.8            | 1/10  |
+| -0.8            | -0.6            | 1/10  |
+| -0.6            | -0.4            | 1/10  |
+| -0.4            | -0.2            | 1/10  |
+| -0.2            | 0.0             | 1/10  |
+| 0.0             | 0.2             | 1/10  |
+| 0.2             | 0.4             | 1/10  |
+| 0.4             | 0.6             | 1/10  |
+| 0.6             | 0.8             | 1/10  |
+| 0.8             | 1.0             | 1/10  |
+
+**Table C.3.2.5-2: Expected Count for Total Anisotropy Coefficient with 11 Bins**
+
+| Bin limit (min) | Bin limit (max) | $p_k$ |
+|-----------------|-----------------|-------|
+| 0.00000         | 0.09090909      | 0.013 |
+| 0.09090909      | 0.18181818      | 0.040 |
+| 0.18181818      | 0.27272727      | 0.066 |
+| 0.27272727      | 0.36363636      | 0.093 |
+| 0.36363636      | 0.45454545      | 0.118 |
+| 0.45454545      | 0.54545454      | 0.140 |
+| 0.54545454      | 0.63636363      | 0.157 |
+| 0.63636363      | 0.72727272      | 0.163 |
+| 0.72727272      | 0.81818181      | 0.150 |
+| 0.81818181      | 0.90909090      | 0.053 |
+| 0.90909090      | 1.00000000      | 0.006 |
+
+According to [22], a chi-squared value less than or equal to 21.67 will mean that the 2 orientation anisotropy coefficients,  $A_{pq}(n)$ , are uniformly distributed as expected (1% significance level). For the Total anisotropy coefficients,  $A_{tot}(n)$ , a chi-squared value less than or equal to 23,21 will mean that the there is no significant difference from the ideal reference (1% significance level).
+
+**OTA antenna configuration:** Fixed measurement source antennas.
+
+**Measurement antenna:** The electric dipole.
+
+### C.3.3 Reporting
+
+Additionally, the results should be summarized in the following table (some entries like isotropy apply only to certain methods):
+
+**Table C.3.3-1: Template for reporting validation results**
+
+| Item | Parameter              | Result | Tolerances (Note 1) | Comments |
+|------|------------------------|--------|---------------------|----------|
+| 1    | Power delay profile    |        |                     |          |
+| 2    | Doppler                |        |                     |          |
+| 3    | BS antenna correlation |        |                     |          |
+| 4    | Rayleigh fading        |        |                     |          |
+| 5    | Isotropy               |        |                     |          |
+
+NOTE 1: The exact tolerances are for further study.
+
+NOTE 2: In addition to the validation of channel model parameters stated here, in order to properly identify test tolerances it is important to verify test repeatability.  
+Though not required for channel model verification, individual labs are encouraged to run test repeatability experiments, such as the one described in Annex G.A.2 in [4].  
+For future uncertainty analyses, test repeatability of all methodologies has to be reported.
+
+## C.4 Channel model validation results
+
+Channel models have been specified in clause C.2.
+
+This clause describes the MIMO OTA validation measurements, in order to ensure that the channel models are correctly implemented and hence capable of generating the propagation environment, as described by the model, within a test area. Measurements are done mainly with a Vector Network Analyzer (VNA) and a spectrum analyzer.
+
+### C.4.1 Scope
+
+Clauses C.4.2-C.4.6 contain the validation results of channel models in Annex C.2 for companies using methods as described in Clause 6.3.2. These results are based on two different types of equipment vendors and both sets of results are included here for comparison.
+
+### C.4.2 Power Delay Profile (PDP) for 3D isotropic models
+
+The power delay profiles of the channel models in Annex C.2 have been measured according to the procedures in Annex C.3.
+
+Figure C.4.2-1 below illustrates the measured results for Band 13 for the isotropic channel model based on NIST for two different reverberation chambers.
+
+Figure C.4.2-2 illustrates the measured results for Band 13 for the short delay spread low correlation and long delay spread high correlation isotropic channel models for two different reverberation chambers and channel emulators.
+
+![Graph (a) showing Power [dB] vs Delay [ns] for reverberation chamber A. The y-axis ranges from -50 to -8 dB, and the x-axis ranges from 0 to 900 ns. The curve shows a smooth, exponential-like decay of power over time.](0da08ff31b255c351a205a58b94b3635_img.jpg)
+
+Graph (a) showing Power [dB] vs Delay [ns] for reverberation chamber A. The y-axis ranges from -50 to -8 dB, and the x-axis ranges from 0 to 900 ns. The curve shows a smooth, exponential-like decay of power over time.
+
+(a)
+
+![Graph (b) showing Power [dB] vs Delay [ns] for reverberation chamber B. The y-axis ranges from -60 to -10 dB, and the x-axis ranges from 0 to 950 ns. The curve shows a smooth, exponential-like decay of power over time.](8d634ce92bb10765e51c1cc4af9c09f3_img.jpg)
+
+Graph (b) showing Power [dB] vs Delay [ns] for reverberation chamber B. The y-axis ranges from -60 to -10 dB, and the x-axis ranges from 0 to 950 ns. The curve shows a smooth, exponential-like decay of power over time.
+
+(b)
+
+Figure C.4.2-1: For Band 13, isotropic channel model based on NIST PDP verification measurement for reverberation chamber A (a); isotropic channel model based on NIST PDP verification measurement for reverberation chamber B (b)
+
+![Graph (a) showing Measured (blue line) and Theory (red crosses) PDP for short delay spread low correlation. The y-axis ranges from -35 to -1 dB, and the x-axis ranges from 0 to 1500 ns. The theoretical model closely follows the measured data points.](5c257a05603439a153cb0cf9d4ea626a_img.jpg)
+
+Graph (a) showing Measured (blue line) and Theory (red crosses) PDP for short delay spread low correlation. The y-axis ranges from -35 to -1 dB, and the x-axis ranges from 0 to 1500 ns. The theoretical model closely follows the measured data points.
+
+(a)
+
+![Graph (b) showing Measured (blue line) and Theory (red crosses) PDP for long delay spread high correlation. The y-axis ranges from -35 to -1 dB, and the x-axis ranges from 0 to 5000 ns. The theoretical model closely follows the measured data points.](aa44d56b283764316570c8885f370b1f_img.jpg)
+
+Graph (b) showing Measured (blue line) and Theory (red crosses) PDP for long delay spread high correlation. The y-axis ranges from -35 to -1 dB, and the x-axis ranges from 0 to 5000 ns. The theoretical model closely follows the measured data points.
+
+(b)
+
+![Graph (c) showing Envelope Power vs Time (ns) for short delay spread low correlation. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 1000 ns. It compares Measurement (blue line) and Model (red line), showing good agreement between the two.](87afd2b5c75bd1f35d29290e1188e7d3_img.jpg)
+
+Graph (c) showing Envelope Power vs Time (ns) for short delay spread low correlation. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 1000 ns. It compares Measurement (blue line) and Model (red line), showing good agreement between the two.
+
+(c)
+
+![Graph (d) showing Envelope Power vs Time (ns) for long delay spread high correlation. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5000 ns. It compares Measurement (blue line) and Model (red line), showing good agreement between the two.](783c6fe6b529f9ffac79e20e1a440167_img.jpg)
+
+Graph (d) showing Envelope Power vs Time (ns) for long delay spread high correlation. The y-axis ranges from 0 to 1, and the x-axis ranges from 0 to 5000 ns. It compares Measurement (blue line) and Model (red line), showing good agreement between the two.
+
+(d)
+
+Figure C.4.2-2: For Band 13, short delay spread low correlation (a) and long delay spread high correlation (b) isotropic channel models PDP verification measurement for reverberation chamber and channel emulator setup A; short delay spread low correlation (c) and long delay spread high correlation (d) isotropic channel models PDP verification measurement for reverberation chamber and channel emulator setup C
+
+Table C.4.2-1 and Table C.4.2-2 below summarize the PDP verification results.
+
+**Table C.4.2-1: Summary of PDP verification results at Band 13 for the isotropic channel model based on NIST for both equipment vendors**
+
+| Chamber | RMS Delay Spread measured [ns] | RMS Delay Spread theory [ns] | Delta [ns] |
+|---------|--------------------------------|------------------------------|------------|
+| 1       | 79.34                          | 80                           | - 0.66     |
+| 2       | 82.21                          | 80                           | + 2.21     |
+
+**Table C.4.2-2: Summary of PDP verification results at Band 13 for the short delay spread low correlation and long delay spread high correlation isotropic channel models for both equipment vendors**
+
+| Isotropic Long Delay Spread High Correlation | Reverberation Chamber and Channel Emulator A |                     |       | Reverberation Chamber and Channel Emulator C |                     |       |
+|----------------------------------------------|----------------------------------------------|---------------------|-------|----------------------------------------------|---------------------|-------|
+| Cluster                                      | Theoretical Power (dB)                       | Measured Power (dB) | Delta | Theoretical Power (dB)                       | Measured Power (dB) | Delta |
+| 1                                            | 0                                            | 0                   | 0     | 0                                            | 0                   | 0     |
+| 2                                            | -2.2                                         | -1.44               | +0.76 | -2.2                                         | -2.31               | -0.11 |
+| 3                                            | -1.7                                         | -1.48               | +0.22 | -1.7                                         | -1.43               | +0.27 |
+| 4                                            | -5.2                                         | -5.19               | +0.01 | -5.2                                         | -4.98               | +0.22 |
+| 5                                            | -9.1                                         | -8.86               | +0.24 | -9.1                                         | -8.75               | +0.35 |
+| 6                                            | -12.5                                        | -12.20              | +0.30 | -12.5                                        | -12.45              | +0.05 |
+| Isotropic Short Delay Spread Low Correlation | Reverberation Chamber and Channel Emulator A |                     |       | Reverberation Chamber and Channel Emulator C |                     |       |
+| Cluster                                      | Theoretical Power (dB)                       | Measured Power (dB) | Delta | Theoretical Power (dB)                       | Measured Power (dB) | Delta |
+| 1                                            | 0                                            | 0                   | 0     | 0                                            | 0                   | 0     |
+| 2                                            | -1.3                                         | -1.11               | +0.19 | -1.3                                         | -1.26               | +0.04 |
+| 3                                            | -2.7                                         | -2.57               | +0.13 | -2.7                                         | -2.79               | -0.09 |
+| 4                                            | -4.3                                         | -4.47               | -0.17 | -4.3                                         | -4.42               | -0.12 |
+| 5                                            | -6.0                                         | -5.79               | +0.21 | -6.0                                         | -5.86               | +0.14 |
+| 6                                            | -8.4                                         | -8.18               | +0.22 | -8.4                                         | -7.88               | +0.52 |
+
+#### C.4.2.1 Setup used by harmonization test lab
+
+The measurement procedures and data analysis align with Annex C.3.2.1. The inherent RMS delay spread of the chamber (without channel emulator) is 50 ns and 1000 stirring positions are used (one per VNA trace).
+
+Figure C.4.2.1-1 and Figure C.4.2.1-2 show the results from the PDP validation measurements for the SDLC channel model for 751 MHz and 2655 MHz, respectively. Table C.4.2.1-1 shows a summary of the delta between measured and ideal values.
+
+![Line graph showing Power [dB] vs Delay [ns] for 751 MHz. The y-axis ranges from -105 to -65 dB, and the x-axis ranges from 0 to 1400 ns. A blue line represents the data, with several peaks marked by black squares at approximately 200, 300, 650, 800, and 950 ns.](839f9152f020c693e6c10ccb4fe611f9_img.jpg)
+
+This graph displays the Power Delay Profile (PDP) for the SDLC channel model at 751 MHz. The y-axis represents Power in dB, ranging from -105 to -65 in increments of 5 dB. The x-axis represents Delay in ns, ranging from 0 to 1400 in increments of 200 ns. The blue line shows a series of peaks and valleys. The first major peak is at approximately 200 ns (marked with a black square), followed by a slightly higher peak at 300 ns. A significant dip occurs around 600 ns, followed by a sharp rise to a peak at 650 ns (marked with a black square). Subsequent peaks are at 800 ns (marked with a black square) and 950 ns (marked with a black square). The power level generally decreases after 1000 ns, reaching a noise floor around -105 dB by 1400 ns.
+
+Line graph showing Power [dB] vs Delay [ns] for 751 MHz. The y-axis ranges from -105 to -65 dB, and the x-axis ranges from 0 to 1400 ns. A blue line represents the data, with several peaks marked by black squares at approximately 200, 300, 650, 800, and 950 ns.
+
+Figure C.4.2.1-1: Results from PDP validation measurements for the SDLC channel model and 751 MHz.
+
+![Line graph showing Power [dB] vs Delay [ns] for 2655 MHz. The y-axis ranges from -104 to -74 dB, and the x-axis ranges from 0 to 1400 ns. A blue line represents the data, with several peaks marked by black squares at approximately 200, 300, 650, 800, and 950 ns.](a10590b8cd913a41920c6ceadb521e77_img.jpg)
+
+This graph displays the Power Delay Profile (PDP) for the SDLC channel model at 2655 MHz. The y-axis represents Power in dB, ranging from -104 to -74 in increments of 2 dB. The x-axis represents Delay in ns, ranging from 0 to 1400 in increments of 200 ns. The blue line shows a similar pattern to the 751 MHz graph but with lower overall power levels. Peaks are marked with black squares at approximately 200, 300, 650, 800, and 950 ns. The peak at 300 ns is the highest, reaching approximately -75 dB. The power level decreases significantly after 1000 ns, reaching a noise floor around -104 dB by 1400 ns.
+
+Line graph showing Power [dB] vs Delay [ns] for 2655 MHz. The y-axis ranges from -104 to -74 dB, and the x-axis ranges from 0 to 1400 ns. A blue line represents the data, with several peaks marked by black squares at approximately 200, 300, 650, 800, and 950 ns.
+
+Figure C.4.2.1-2: Results from PDP validation measurements for the SDLC channel model and 2655 MHz.
+
+**Table C.4.2.1-1: Summary of deltas between measured and ideal values for the SDLC channel model for 751 MHz and 2655 MHz.**
+
+| Cluster | 751 MHz          |                  | 2655 MHz         |                  |
+|---------|------------------|------------------|------------------|------------------|
+|         | Power delta [dB] | Delay delta [ns] | Power delta [dB] | Delay delta [ns] |
+| 1       | 0                | 0                | 0                | 0                |
+| 2       | -0.1             | -5               | +0.2             | 0                |
+| 3       | +0.6             | 0                | +0.4             | 0                |
+| 4       | -0.3             | 0                | -0.6             | 0                |
+| 5       | -0.3             | 0                | -0.3             | +5               |
+| 6       | -0.1             | -5               | +0.5             | 0                |
+
+### C.4.3 Doppler for 3D isotropic models
+
+The Doppler spectrum of the channel models defined in Annex C.2 has been characterized according to Annex C.3. Figure C.4.3-1 illustrates the measured results for Band 13 for the isotropic channel model based on NIST and Figure C.4.3-2 shows the measured results for Band 13 for the short delay spread low correlation and long delay spread high correlation isotropic channel models.
+
+![Figure C.4.3-1: Doppler spectrum for isotropic channel model based on NIST. (a) shows the spectrum for reverberation chamber A, and (b) shows the spectrum for reverberation chamber B. Both plots show Power [dB] vs Frequency [Hz] centered at 0 Hz.](440236efe61277b409f0f16c982945c4_img.jpg)
+
+Figure C.4.3-1 consists of two subplots, (a) and (b), showing the Doppler spectrum for an isotropic channel model based on NIST. Both plots have 'Power [dB]' on the y-axis (ranging from -130 to -60) and 'Frequency [Hz]' on the x-axis (ranging from -150 to 150). Both spectra are centered at 0 Hz.
+
+Subplot (a) represents the spectrum for reverberation chamber A. It shows a sharp peak at 0 Hz reaching approximately -65 dB. The spectrum is relatively flat around -125 dB for frequencies between -150 Hz and -50 Hz, and between 50 Hz and 150 Hz, with some minor fluctuations.
+
+Subplot (b) represents the spectrum for reverberation chamber B. It also shows a sharp peak at 0 Hz reaching approximately -65 dB. The spectrum is smoother than in (a), with a gradual decrease in power as frequency moves away from 0 Hz, reaching approximately -125 dB at ±150 Hz.
+
+Figure C.4.3-1: Doppler spectrum for isotropic channel model based on NIST. (a) shows the spectrum for reverberation chamber A, and (b) shows the spectrum for reverberation chamber B. Both plots show Power [dB] vs Frequency [Hz] centered at 0 Hz.
+
+**Figure C.4.3-1: For Band 13, Doppler spectrum for isotropic channel model based on NIST emulated by reverberation chamber A (a); Doppler spectrum for isotropic channel model based on NIST emulated by reverberation chamber B (b)**
+
+![Figure C.4.3-2(a): Doppler Spectrum plot showing Normalized Power [dB] vs Frequency [Hz]. The plot shows a broad, noisy spectrum centered around 0 Hz, with power levels ranging from approximately -45 dB to 0 dB. The x-axis ranges from -70 to 70 Hz, and the y-axis ranges from -50 to 10 dB.](aa75bb3aaab7d58772b885504627945a_img.jpg)
+
+Figure C.4.3-2(a): Doppler Spectrum plot showing Normalized Power [dB] vs Frequency [Hz]. The plot shows a broad, noisy spectrum centered around 0 Hz, with power levels ranging from approximately -45 dB to 0 dB. The x-axis ranges from -70 to 70 Hz, and the y-axis ranges from -50 to 10 dB.
+
+(a)
+
+![Figure C.4.3-2(b): Doppler Spectrum plot showing Power [10 dB/div] vs Frequency [10 Hz/div]. The plot shows a narrow, sharp peak at 749.9983 MHz, with power levels ranging from approximately -45 dB to 0 dB. The x-axis is labeled 'Frequency, 10Hz/div' and the y-axis is labeled 'Power, 10 dB/div'.](a802694aeb53f806085863c8eaa0451d_img.jpg)
+
+Figure C.4.3-2(b): Doppler Spectrum plot showing Power [10 dB/div] vs Frequency [10 Hz/div]. The plot shows a narrow, sharp peak at 749.9983 MHz, with power levels ranging from approximately -45 dB to 0 dB. The x-axis is labeled 'Frequency, 10Hz/div' and the y-axis is labeled 'Power, 10 dB/div'.
+
+(b)
+
+**Figure C.4.3-2: For Band 13, Doppler spectrum for short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup A (a); Doppler spectrum for short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup C (b)**
+
+#### C.4.3.1 Setup used by harmonization test lab
+
+The measurement procedures and data analysis align with Annex C.3.2.2. The inherent RMS delay spread of the chamber (without channel emulator) is 50 ns and 100 stirring positions are used (one per spectrum analyzer sweep).
+
+Figure C.4.3.1-1 and Figure C.4.3.1-2 show the results from the Doppler validation measurements for the SDLC channel model for 751 MHz and 2655 MHz, respectively.
+
+![Figure C.4.3.1-1: Doppler validation measurements for the SDLC channel model at 751 MHz.](4225405c542ca18957be6328721b7386_img.jpg)
+
+This line graph shows the results of Doppler validation measurements for the SDLC channel model at 751 MHz. The y-axis represents the power level in dB, ranging from -65 to 5 with major grid lines every 5 dB. The x-axis represents the Doppler shift in Hz, with labels at 750 999 940, 750 999 960, 750 999 980, 751 000 000, 751 000 020, 751 000 040, and 751 000 060. A blue line represents the measured data, showing a peak power level near 0 dB between the two red vertical lines. Two red vertical lines are drawn at approximately ±20.88 Hz from the center (0 Hz), representing the ideal maximum Doppler shift for 30 km/h. The power level drops off significantly outside these lines, reaching around -55 dB at the edges of the plot.
+
+Figure C.4.3.1-1: Doppler validation measurements for the SDLC channel model at 751 MHz.
+
+Figure C.4.3.1-1: Results from Doppler validation measurements for the SDLC channel model, 751 MHz. The red vertical lines represent the ideal maximum Doppler shift for 30 km/h (20.88 Hz).
+
+![Figure C.4.3.1-2: Doppler validation measurements for the SDLC channel model at 2655 MHz.](898c1327035aaf14d832e4400901e092_img.jpg)
+
+This line graph shows the results of Doppler validation measurements for the SDLC channel model at 2655 MHz. The y-axis represents the power level in dB, ranging from -65 to 5 with major grid lines every 5 dB. The x-axis represents the Doppler shift in Hz, with labels at 2 654 999 800, 2 654 999 900, 2 655 000 000, 2 655 000 100, and 2 655 000 200. A blue line represents the measured data, showing a peak power level near 0 dB between the two red vertical lines. Two red vertical lines are drawn at approximately ±73.80 Hz from the center (0 Hz), representing the ideal maximum Doppler shift for 30 km/h. The power level drops off significantly outside these lines, reaching around -55 dB at the edges of the plot.
+
+Figure C.4.3.1-2: Doppler validation measurements for the SDLC channel model at 2655 MHz.
+
+Figure C.4.3.1-2: Results from Doppler validation measurements for the SDLC channel model, 2655 MHz. The red vertical lines represent the ideal maximum Doppler shift for 30 km/h (73.80 Hz).
+
+### C.4.4 Base Station antenna correlation for 3D isotropic models
+
+The Base Station (BS) antenna correlation of the models defined in Annex C.2 has been characterized according to Annex C.3.
+
+Figure C.4.4-1 shows the measured results for the isotropic channel model based on NIST and Figure C.4.4-2 shows the measured results for the short delay spread low correlation and long delay spread high correlation isotropic channel models for Band 13.
+
+![Figure C.4.4-1: Two line graphs showing base station antenna correlation for Band 13. (a) Amplitude of complex correlation vs Frequency [MHz] for NIST model in Chamber A. (b) Complex Correlation Amplitude vs Frequency [MHz] for NIST model in Chamber B.](10f1d65dbabe0b2d04537846a6c0e1ed_img.jpg)
+
+Figure C.4.4-1 consists of two subplots, (a) and (b), showing the base station antenna correlation for Band 13. Both plots have Frequency [MHz] on the x-axis, ranging from 746 to 756.
+
+Subplot (a) shows the Amplitude of complex correlation on the y-axis, ranging from 0 to 1. The plot is titled "BS Correlation" and contains a legend entry for "NIST". The data series is a flat line at approximately 0.05 across the entire frequency range.
+
+Subplot (b) shows the Complex Correlation Amplitude on the y-axis, ranging from 0 to 1. The data series is a flat line at approximately 0.05 across the entire frequency range.
+
+Figure C.4.4-1: Two line graphs showing base station antenna correlation for Band 13. (a) Amplitude of complex correlation vs Frequency [MHz] for NIST model in Chamber A. (b) Complex Correlation Amplitude vs Frequency [MHz] for NIST model in Chamber B.
+
+**Figure C.4.4-1: For Band 13, base station antenna correlation for isotropic channel model based on NIST emulated by reverberation chamber A (a); base station antenna correlation for isotropic channel model based on NIST emulated by reverberation chamber B (b)**
+
+![Figure C.4.4-2: Base station antenna correlation for Band 13. (a) High correlation (long delay spread) showing Amplitude of complex correlation vs Frequency [MHz] for OTA and Cond. (b) Low correlation (short delay spread) showing Amplitude of complex correlation vs Frequency [MHz] for OTA and Cond. (c) Correlation vs Frequency (MHz) for different imposed correlation values (rho=0, 0.3, 0.6, 0.9, 0.99).](c3d8104dc13f901e55235041c000a837_img.jpg)
+
+Figure C.4.4-2 consists of three subplots labeled (a), (b), and (c).  
+(a) High correlation: The y-axis is 'Amplitude of complex correlation' from 0 to 1. The x-axis is 'Frequency [MHz]' from 746 to 756. Two lines, 'OTA' (blue) and 'Cond' (green), are nearly horizontal at a correlation of approximately 0.75.  
+(b) Low correlation: The y-axis is 'Amplitude of complex correlation' from 0 to 1. The x-axis is 'Frequency [MHz]' from 746 to 756. Two lines, 'OTA' (blue) and 'Cond' (green), are nearly horizontal at a correlation of approximately 0.15.  
+(c) Imposed correlation: The y-axis is 'Correlation' from 0 to 1. The x-axis is 'Frequency (MHz)' from 742 to 760. Five horizontal lines represent different imposed correlation values:  $\rho=0$  (black),  $\rho=0.3$  (blue),  $\rho=0.6$  (red),  $\rho=0.9$  (green), and  $\rho=0.99$  (cyan).
+
+Figure C.4.4-2: Base station antenna correlation for Band 13. (a) High correlation (long delay spread) showing Amplitude of complex correlation vs Frequency [MHz] for OTA and Cond. (b) Low correlation (short delay spread) showing Amplitude of complex correlation vs Frequency [MHz] for OTA and Cond. (c) Correlation vs Frequency (MHz) for different imposed correlation values (rho=0, 0.3, 0.6, 0.9, 0.99).
+
+**Figure C.4.4-2: For Band 13, base station antenna correlation for the long delay spread high correlation (a) and short delay spread low correlation (b) isotropic channel models emulated by reverberation chamber and channel emulator setup A; base station antenna correlation observed in the test volume for different values of base station antenna correlation imposed by the channel emulator for the reverberation chamber and channel emulator setup C (c)**
+
+#### C.4.4.1 Setup used by harmonization test lab
+
+The measurement procedures and data analysis align with Annex C.3.2.3. The inherent RMS delay spread of the chamber (without channel emulator) is 50 ns and 600 stirring positions are used (one per VNA trace).
+
+Figure C.4.4.1-1 and Figure C.4.4.1-2 show the results from the base station correlation validation measurements for the SDLC channel model for 751 MHz and 2655 MHz, respectively.
+
+![Line graph showing Correlation vs Frequency [MHz] for 751 MHz. The y-axis ranges from 0 to 1. The x-axis ranges from 746 to 756 MHz. Two lines are plotted: 'Ampl of compl corr (antenna 1 and 2)' (black line) and 'Ideal correlation' (blue line). The ideal correlation is a constant horizontal line at approximately 0.15. The measured correlation fluctuates around this ideal line, with values mostly between 0.1 and 0.2.](d3b73b32af148cbe75a9d016ac7bdd4d_img.jpg)
+
+| Frequency [MHz] | Ampl of compl corr (antenna 1 and 2) | Ideal correlation |
+|-----------------|--------------------------------------|-------------------|
+| 746             | 0.15                                 | 0.15              |
+| 747             | 0.08                                 | 0.15              |
+| 748             | 0.15                                 | 0.15              |
+| 749             | 0.18                                 | 0.15              |
+| 750             | 0.14                                 | 0.15              |
+| 751             | 0.20                                 | 0.15              |
+| 752             | 0.14                                 | 0.15              |
+| 753             | 0.16                                 | 0.15              |
+| 754             | 0.16                                 | 0.15              |
+| 755             | 0.15                                 | 0.15              |
+| 756             | 0.14                                 | 0.15              |
+
+Line graph showing Correlation vs Frequency [MHz] for 751 MHz. The y-axis ranges from 0 to 1. The x-axis ranges from 746 to 756 MHz. Two lines are plotted: 'Ampl of compl corr (antenna 1 and 2)' (black line) and 'Ideal correlation' (blue line). The ideal correlation is a constant horizontal line at approximately 0.15. The measured correlation fluctuates around this ideal line, with values mostly between 0.1 and 0.2.
+
+Figure C.4.4.1-1: Results from base station antenna correlation validation measurements for the SDLC channel model and 751 MHz.
+
+![Line graph showing Correlation vs Frequency [MHz] for 2655 MHz. The y-axis ranges from 0 to 1. The x-axis ranges from 2 650 2 to 2 660 2 MHz. Two lines are plotted: 'Ampl of compl corr (antenna 1 and 2)' (black line) and 'Ideal correlation' (blue line). The ideal correlation is a constant horizontal line at approximately 0.15. The measured correlation fluctuates around this ideal line, with values mostly between 0.1 and 0.2.](b1c27d955a3589957e99cc4f284ddcb1_img.jpg)
+
+| Frequency [MHz] | Ampl of compl corr (antenna 1 and 2) | Ideal correlation |
+|-----------------|--------------------------------------|-------------------|
+| 2 650 2         | 0.13                                 | 0.15              |
+| 2 651 2         | 0.12                                 | 0.15              |
+| 2 652 2         | 0.08                                 | 0.15              |
+| 2 653 2         | 0.11                                 | 0.15              |
+| 2 654 2         | 0.11                                 | 0.15              |
+| 2 655 2         | 0.16                                 | 0.15              |
+| 2 656 2         | 0.11                                 | 0.15              |
+| 2 657 2         | 0.14                                 | 0.15              |
+| 2 658 2         | 0.13                                 | 0.15              |
+| 2 659 2         | 0.13                                 | 0.15              |
+| 2 660 2         | 0.14                                 | 0.15              |
+
+Line graph showing Correlation vs Frequency [MHz] for 2655 MHz. The y-axis ranges from 0 to 1. The x-axis ranges from 2 650 2 to 2 660 2 MHz. Two lines are plotted: 'Ampl of compl corr (antenna 1 and 2)' (black line) and 'Ideal correlation' (blue line). The ideal correlation is a constant horizontal line at approximately 0.15. The measured correlation fluctuates around this ideal line, with values mostly between 0.1 and 0.2.
+
+Figure C.4.4.1-2: Results from base station antenna correlation validation measurements for the SDLC channel model and 2655 MHz.
+
+### C.4.5 Rayleigh fading for 3D isotropic models
+
+The Rayleigh fading of the models defined in Annex C.2 have been characterized according to Annex C.3.
+
+Figure C.4.5-1 shows the measured results for the short delay spread low correlation and long delay spread high correlation isotropic channel models for Band 13.
+
+![Figure C.4.5-1: Three plots (a, b, c) showing cumulative probability and CCDF for Rayleigh fading models. Plot (a) shows Cumulative probability vs Relative rec. power [dB] for Theoretical Rayleigh, Double Rayleigh (Measured), RC, and RC+CE. Plot (b) shows Cumulative Probability vs Rel. Rec. Power (dB) for Theoretical Rayleigh and E40. Plot (c) shows CCDF vs Normalized signal amplitude (dB) for Theoretical Rayleigh and E40. Each plot includes text indicating maximum differences from theoretical models.](815e371be8c93f43b2ed745e5a78ee5a_img.jpg)
+
+(a)
+
+Max diff to theoretical +10 to -20 dB: < 1.5 dB  
+ Max diff to theoretical -20 to -30 dB: < 1.5 dB  
+ $\chi^2$  for RC: 5.37  
+ $\chi^2$  for RC+CE: 15.22
+
+(b)
+
+Max diff to theoretical +10 to -20 dB: < 1.0 dB  
+ Max diff to theoretical -20 to -30 dB: < 1.0 dB
+
+(c)
+
+Max diff to theoretical +10 to -20 dB: < 1.5 dB  
+ Max diff to theoretical -20 to -30 dB: < 1.5 dB
+
+Figure C.4.5-1: Three plots (a, b, c) showing cumulative probability and CCDF for Rayleigh fading models. Plot (a) shows Cumulative probability vs Relative rec. power [dB] for Theoretical Rayleigh, Double Rayleigh (Measured), RC, and RC+CE. Plot (b) shows Cumulative Probability vs Rel. Rec. Power (dB) for Theoretical Rayleigh and E40. Plot (c) shows CCDF vs Normalized signal amplitude (dB) for Theoretical Rayleigh and E40. Each plot includes text indicating maximum differences from theoretical models.
+
+**Figure C.4.5-1: For Band 13, Rayleigh fading for isotropic channel model based on NIST, short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup A (a); Rayleigh fading for isotropic channel model based on NIST emulated by reverberation chamber B (b); Rayleigh fading for short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup C (c)**
+
+#### C.4.5.1 Setup used by harmonization test lab
+
+The measurement procedures and data analysis align with Annex C.3.2.4. The inherent RMS delay spread of the chamber (without channel emulator) is 50 ns and 1080 stirring positions are used (one per VNA trace).
+
+Table C.4.5.1-1 shows the chi-squared values calculated for two different TVVPs (see Annex C.4.6.1) and three orientations for each TVVP for the SDLC channel model at 751 MHz and 2655 MHz. As can be seen from this table, the chi-squared value is within the limit ( $< 27.69$ ) for all cases.
+
+**Table C.4.5.1-1: Chi-squared values for the SDLC channel model for 751 MHz and 2655 MHz.**
+
+| Frequency [MHz] | TVVP 1-1 | TVVP 1-2 | TVVP 1-3 | TVVP 9-1 | TVVP 9-2 | TVVP 9-3 |
+|-----------------|----------|----------|----------|----------|----------|----------|
+| 751             | 18,6     | 16,2     | 19,0     | 25,3     | 21,9     | 24,3     |
+| 2655            | 22,6     | 18,4     | 20,9     | 18,2     | 23,1     | 21,1     |
+
+In addition, the K-factor was calculated for the same positions and orientations as described above. The result is shown in Table C.4.5.1-2 for the SDLC channel model at 751 MHz and 2655 MHz. All values are within the limit ( $< -10$  dB).
+
+**Table C.4.5.1-2: K-factor for the SDLC channel model for 751 MHz and 2655 MHz.**
+
+| Frequency [MHz] | TVVP 1-1 | TVVP 1-2 | TVVP 1-3 | TVVP 9-1 | TVVP 9-2 | TVVP 9-3 |
+|-----------------|----------|----------|----------|----------|----------|----------|
+| 751             | -51,8    | -37,1    | -43,6    | -30,5    | -28,5    | -25,0    |
+| 2655            | -41,4    | -31,8    | -26,3    | -30,0    | -26,7    | -26,6    |
+
+### C.4.6 Isotropy for 3D isotropic models
+
+The isotropy of the models defined in Annex C.2 has been characterized according to Annex C.3. Figure C.4.6-1 shows the measured results for the isotropic channel model based on NIST, short delay spread low correlation and long delay spread high correlation isotropic channel models for band 13.
+
+![CDF plot of A_ab for isotropy X vs Y, X vs Z, and Y vs Z.](37871b402d58e7fc0bbae75a4ba6650f_img.jpg)
+
+This figure shows the Cumulative Distribution Function (CDF) of the parameter  $A_{ab}$ . The x-axis ranges from -1 to 1, and the y-axis represents Probability from 0 to 1. Three curves are plotted: 'Isotropy: X vs Y' (black), 'Isotropy: X vs Z' (blue), and 'Isotropy: Y vs Z' (red). All three curves are nearly identical, starting at (0,0) and increasing linearly to (1,1).
+
+CDF plot of A\_ab for isotropy X vs Y, X vs Z, and Y vs Z.
+
+![CDF plot of Total isotropy.](b11c2eb778491a9a07084b02124d1faa_img.jpg)
+
+This figure shows the CDF of 'Total isotropy'. The x-axis ranges from 0 to 1, and the y-axis represents Probability from 0 to 1. A single black curve is plotted, labeled 'Isotropy: X-Y-Z'. The curve starts at (0,0) and increases to (1,1), following a slightly S-shaped path.
+
+CDF plot of Total isotropy.
+
+$\chi^2: 7.89$
+
+(a)
+
+![CDF plot of Total isotropy with data points.](b75617f33603d5f399500e7791997841_img.jpg)
+
+This figure shows the CDF of 'Total isotropy' with data points marked by 'x'. The x-axis ranges from 0 to 1, and the y-axis represents CDF from 0.0 to 1.0. The curve starts at (0,0) and increases to (1,1), passing through the data points.
+
+CDF plot of Total isotropy with data points.
+
+(b)
+
+![Four CDF plots for 750MHz: radial-tangential, radial-vertical, tangential-vertical, and total.](38630b597138d11a54ca4d4032eb428d_img.jpg)
+
+This figure contains four subplots, each showing the CDF for a different parameter at 750MHz. Each subplot compares 'measured' (red line) and 'ideal' (grey line) distributions.
+ 
+
+- radial-tangential:** Both measured and ideal lines are nearly perfectly overlaid, ranging from -1 to 1.
+- radial-vertical:** Both measured and ideal lines are nearly perfectly overlaid, ranging from -1 to 1.
+- tangential-vertical:** Both measured and ideal lines are nearly perfectly overlaid, ranging from -1 to 1.
+- total:** Both measured and ideal lines are nearly perfectly overlaid, ranging from 0 to 1.
+
+ All plots have a CDF y-axis from 0 to 1.
+
+Four CDF plots for 750MHz: radial-tangential, radial-vertical, tangential-vertical, and total.
+
+(c)
+
+![Figure C.4.6-1 (d) shows two CDF plots. The left plot is labeled 'Two Orientations' and the right plot is labeled 'Three Orientations'. Both plots show the CDF (Cumulative Distribution Function) on the y-axis (ranging from 0 to 1) against an x-axis ranging from -1 to 1. The left plot shows a straight diagonal line from (0,0) to (1,1). The right plot shows a smooth S-shaped curve that is slightly above the diagonal line.](2b56a53620616729fb852d9ac827e8bd_img.jpg)
+
+Figure C.4.6-1 (d) shows two CDF plots. The left plot is labeled 'Two Orientations' and the right plot is labeled 'Three Orientations'. Both plots show the CDF (Cumulative Distribution Function) on the y-axis (ranging from 0 to 1) against an x-axis ranging from -1 to 1. The left plot shows a straight diagonal line from (0,0) to (1,1). The right plot shows a smooth S-shaped curve that is slightly above the diagonal line.
+
+(d)
+
+**Figure C.4.6-1: For Band 13, isotropy for isotropic channel model based on NIST, short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup A (a); Isotropy for isotropic channel model based on NIST emulated by reverberation chamber B (b); Isotropy for short delay spread low correlation and long delay spread high correlation isotropic channel models emulated by reverberation chamber and channel emulator setup C (c); Reference anisotropy coefficients (d)**
+
+#### C.4.6.1 Setup used by harmonization test lab
+
+The measurement procedures and data analysis align with Annex C.3.2.5. The inherent RMS delay spread of the chamber (without channel emulator) is 50 ns and 120 stirring positions are used (one per VNA trace).
+
+The RC+CE setup used is a Type 1 RC, with a schematic setup as shown in Figure C.4.6.1-1. The TVVPs map to the physical dimensions as shown in Table C.4.6.1-1. For each TVVP three orthogonal orientations were used, denoted 1.1, 1.2 and 1.3 (and similarly for the other TVVPs).
+
+![Figure C.4.6.1-1 is a schematic diagram of the RC+CE setup. It shows a cylindrical 'Test Volume' mounted on a 'Turntable'. Inside the cylinder, there are nine points labeled TVVP1 through TVVP9. TVVP1, TVVP2, and TVVP3 are on the bottom face; TVVP4, TVVP5, and TVVP6 are on the middle section; and TVVP7, TVVP8, and TVVP9 are on the top face. The distance from the bottom face to the middle section is labeled 0.5λ, and the distance from the middle section to the top face is also labeled 0.5λ. The distance from the side of the cylinder to the 'Stirrer' is labeled > 0.5λ. There are two 'Stirrer' units shown, one above the cylinder and one to the side.](3bc294250861a15a143cdcf2b8297fd1_img.jpg)
+
+Figure C.4.6.1-1 is a schematic diagram of the RC+CE setup. It shows a cylindrical 'Test Volume' mounted on a 'Turntable'. Inside the cylinder, there are nine points labeled TVVP1 through TVVP9. TVVP1, TVVP2, and TVVP3 are on the bottom face; TVVP4, TVVP5, and TVVP6 are on the middle section; and TVVP7, TVVP8, and TVVP9 are on the top face. The distance from the bottom face to the middle section is labeled 0.5λ, and the distance from the middle section to the top face is also labeled 0.5λ. The distance from the side of the cylinder to the 'Stirrer' is labeled > 0.5λ. There are two 'Stirrer' units shown, one above the cylinder and one to the side.
+
+**Figure C.4.6.1-1. Schematics of the RC+CE setup used for the harmonization testing and the corresponding TVVPs.**
+
+**Table C.4.6.1-1. Physical dimensions of the TVVPs.**
+
+| Test Volume Validation Position                                     | Height above reference point <sup>1</sup> [cm] | Radius [cm] |
+|---------------------------------------------------------------------|------------------------------------------------|-------------|
+| TVVP1                                                               | 0                                              | 0           |
+| TVVP2                                                               | 0                                              | 16          |
+| TVVP3                                                               | 0                                              | 32          |
+| TVVP4                                                               | 30                                             | 0           |
+| TVVP5                                                               | 30                                             | 16          |
+| TVVP6                                                               | 30                                             | 32          |
+| TVVP7                                                               | 60                                             | 0           |
+| TVVP8                                                               | 60                                             | 16          |
+| TVVP9                                                               | 60                                             | 32          |
+| Note 1: Reference point at least 0.5 $\lambda$ above the turntable. |                                                |             |
+
+The chi-squared values for the 2 and 3 orientation anisotropy coefficients are given in Table C.4.6.1-2 and Table C.4.6.1-3 for 751 MHz and 2655 MHz, respectively. As can be seen, all values fall within the limits ( $< 21.67$  and  $< 23.21$  for 2 and 3 orientation anisotropy coefficients, respectively).
+
+**Table C.4.6.1-2. Chi-squared for 2 and 3 orientation anisotropy coefficients for all TVVPs for 751 MHz.**
+
+|                   | Chi-squared |        |        |        |        |        |        |        |        |
+|-------------------|-------------|--------|--------|--------|--------|--------|--------|--------|--------|
+|                   | TVVP 1      | TVVP 2 | TVVP 3 | TVVP 4 | TVVP 5 | TVVP 6 | TVVP 7 | TVVP 8 | TVVP 9 |
+| 3 orientations    | 16,86       | 15,36  | 13,08  | 12,19  | 15,81  | 12,67  | 13,08  | 14,97  | 14,56  |
+| 2 orientations XY | 10,54       | 8,81   | 7,52   | 17,26  | 9,74   | 12,31  | 10,91  | 14,65  | 14,19  |
+| 2 orientations XZ | 9,46        | 7,76   | 6,78   | 10,5   | 8      | 11     | 9,26   | 12,02  | 11,06  |
+| 2 orientations YZ | 7,33        | 8,72   | 8,44   | 15,09  | 9,54   | 11,37  | 16,67  | 13,26  | 11,87  |
+
+**Table C.4.6.1-3. Chi-squared for 2 and 3 orientation anisotropy coefficients for all TVVPs for 2655 MHz.**
+
+|                   | Chi-squared |        |        |        |        |        |        |        |        |
+|-------------------|-------------|--------|--------|--------|--------|--------|--------|--------|--------|
+|                   | TVVP 1      | TVVP 2 | TVVP 3 | TVVP 4 | TVVP 5 | TVVP 6 | TVVP 7 | TVVP 8 | TVVP 9 |
+| 3 orientations    | 16,58       | 14,94  | 15,69  | 11,61  | 16,28  | 15,5   | 15,64  | 12,78  | 14,31  |
+| 2 orientations XY | 9,2         | 9,24   | 12,87  | 9,33   | 9,11   | 8,28   | 10,33  | 6,74   | 11,44  |
+| 2 orientations XZ | 10,54       | 9,78   | 9,5    | 9,37   | 7,76   | 10,31  | 9,78   | 9,46   | 8,59   |
+| 2 orientations YZ | 8,83        | 7,93   | 8,2    | 8,81   | 11,83  | 7,61   | 7,67   | 9,19   | 6,76   |
+
+### C.4.7 Summary for 3D Isotropic Models
+
+The summary of the channel model validation activity is provided in Table C.4.7-1 below.
+
+**Table C.4.7-1: Summary of channel model validation results**
+
+| Item | Parameter              | Result    | Tolerances  | Comments |
+|------|------------------------|-----------|-------------|----------|
+| 1    | Power delay profile    | See C.4.2 | See C.3.2.1 |          |
+| 2    | Doppler                | See C.4.3 | See C.3.2.2 |          |
+| 3    | BS Antenna Correlation | See C.4.4 | See C.3.2.3 |          |
+| 4    | Rayleigh Fading        | See C.4.5 | See C.3.2.4 |          |
+| 5    | Isotropy               | See C.4.6 | See C.3.2.5 |          |
+
+# --- Annex D: Environmental requirements
+
+## D.1 Scope
+
+The requirements in this clause apply to all types of UE(s) and MS(s).
+
+## --- D.2 Ambient temperature
+
+All the MIMO OTA requirements are applicable in room temperature e.g. 25°C.
+
+## --- D.3 Operating voltage
+
+The device under test shall be equipped with a real battery that is fully charged (at the beginning of the test).
+
+# Annex E: DUT orientation conditions
+
+## E.1 Scope
+
+This annex lists the testing environment conditions for all DUT types relevant to MIMO OTA testing.
+
+The use cases (positioning) discussed here are applicable for all methodologies, however the orientation and rotations described may be applicable for some methodologies only, and not for some other methodologies.
+
+## E.2 Testing environment conditions
+
+Table E.2-1 below lists the testing environment conditions along with a diagram and applicable references.
+
+The reference coordinate system and orientation of devices in that coordinate system is shown in Figure E.2-1 below, which includes the mechanical alignment of a phone.
+
+For tablets the home button, charging connector and similar components can be used to define top and bottom.
+
+For laptops the definitions specified in 3GPP TR 25.914 [11] (and repeated here in Table E.2-1) are used.
+
+In the case of methodologies utilizing a spatial channel model in Figure E.2-1, the X axis points towards the channel model reference. For example in the case of an anechoic chamber utilizing 2D antenna array in the azimuth plane (XY plane from Figure E.2-1) this is the direction of the first probe at 0 degrees as shown in Figure 6.3.1.2.1-2.
+
+![Figure E.2-1: Reference coordinate system and reference device orientation. The diagram shows a rectangular phone model centered at the origin of a 3D coordinate system. The Z-axis is vertical, pointing up through the 'Top of the phone' and down through the 'Bottom of Phone'. The Y-axis is horizontal, pointing left through the '-Y' side and right through the 'Y' side. The X-axis is diagonal, pointing towards the bottom-left through the 'X' side and away through the '-X' side. Labels include 'Length of the phone' for the Z-dimension, 'Width of the phone' for the Y-dimension, and 'Thickness of the phone' for the X-dimension. An arrow along the X-axis is labeled 'Screen looks this way', indicating the front of the phone.](94a83e3305f0eb414087648ad5909689_img.jpg)
+
+Figure E.2-1: Reference coordinate system and reference device orientation. The diagram shows a rectangular phone model centered at the origin of a 3D coordinate system. The Z-axis is vertical, pointing up through the 'Top of the phone' and down through the 'Bottom of Phone'. The Y-axis is horizontal, pointing left through the '-Y' side and right through the 'Y' side. The X-axis is diagonal, pointing towards the bottom-left through the 'X' side and away through the '-X' side. Labels include 'Length of the phone' for the Z-dimension, 'Width of the phone' for the Y-dimension, and 'Thickness of the phone' for the X-dimension. An arrow along the X-axis is labeled 'Screen looks this way', indicating the front of the phone.
+
+**Figure E.2-1: Reference coordinate system and reference device orientation**
+
+First the terminology used below is defined here. Where possible consistency with [11], [17], [18] and [9] is sought.
+
+**Use Case (Position):** the use case (position) indicates how the DUT is related to its environment. This includes the following example use cases: free space, beside head, beside head and hand, hand only etc.
+
+Note that formerly this has been referred to as position in [4] as well as in [9]. Since to date only isotropic metrics have been used (TRP/TRS) the definition of positioning the device for a certain use case has been equivalent to orienting it relative to the environment. With the introduction of spatial channel models, the positioning for a specific use case has to be separated from the actual orientation relative to the spatial incoming signals. For some methodologies not utilizing spatial channel models this distinction might not be necessary.
+
+**Orientation:** The orientation of the device in three dimensional space is defined using the three Euler angles –  $\Psi$ -yaw;  $\Theta$ -pitch;  $\Phi$ -roll as defined in [17] and [18] and linked to the reference coordinate systems and reference orientation from Figure E.2-1. Note that for most use cases practical considerations of how to position the DUT together with the phantom may determine the DUT orientation.
+
+**Rotation:** Once positioned for a specific use case and oriented within the reference coordinate system, the DUT and phantom are rotated within the test zone to measure the performance under various spatial channel illuminations. The rotation is defined with the same Euler angles but expressed as vectors of equal size. An example is given below:
+
+EXAMPLE: Consider a DUT measured in an anechoic chamber as described in Clause 6.  
+To measure the free space use case in the YZ plane (see Table E.2-1) for example at every 30 degrees the rotation vectors would be as follows:
+
+$\Psi = [0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0\ 0]$  - a vector of 12 zeros indicating no rotation from the reference position for any phi value below
+
+$\Theta = [-90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90\ -90]$  – a vector of 12 values equal to -90 indicating a constant pitch of -90 degrees for all phi values below
+
+$\Phi = [0\ 30\ 60\ 90\ 120\ 150\ 180\ 210\ 240\ 270\ 300\ 330]$  – a vector of 12 distinct rotations from the reference position representing a rotation along the azimuth plane with a step of 30 degrees.
+
+These vectors unambiguously define that the DUT is to be oriented with the screen up and rotated in azimuth every 30 degrees.
+
+The principal antenna pattern cuts (XY plane, XZ plane, and YZ plane) are defined in [17].
+
+The XY plane cut corresponds to the absolute throughput testing condition applied to the CTIA reference antennas for the IL/IT activity. The XZ plane and YZ plane cuts are shown for completeness and are not required for the absolute data throughput framework. The YZ plane cut corresponds to a device positioned with its screen up in a USB/WLAN tethering scenario and may be a useful testing point for handset devices expected to achieve performance metrics under such usage conditions.
+
+**Table E.2-1: Summary of possible testing environment conditions for devices supporting DL MIMO data reception**
+
+| DUT type and dimensions                  | Testing condition                                               | DUT orientation angles                | Diagram                                                                                                                                                                                                                                                                                                                                                                                           |
+|------------------------------------------|-----------------------------------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Handset, tablet, CTIA reference antennas | XY plane or P0                                                  | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$  | <p>Image: Diagram of a handset/tablet in the XY plane (P0 orientation). The device is upright, with its screen facing the Z-axis. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p>                                    |
+| Handset, tablet, CTIA reference antennas | XZ plane or L0                                                  | $\Psi=90;$<br>$\Theta=0;$<br>$\Phi=0$ | <p>Image: Diagram of a handset/tablet in the XZ plane (L0 orientation). The device is lying flat, with its screen facing the Y-axis. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p>                                 |
+| Handset, tablet, CTIA reference antennas | Free space data mode screen up (FS DMSU) or YZ plane or Face Up | $\Psi=0;$<br>$\Theta=90;$<br>$\Phi=0$ | <p>Image: Diagram of a handset/tablet in the YZ plane (Face Up orientation). The device is lying flat, with its screen facing the Z-axis. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p>                            |
+| Handset, tablet                          | Face Down                                                       | $\Psi=0;$<br>$\Theta=90;$<br>$\Phi=0$ | <p>Image: Diagram of a handset/tablet in the Face Down orientation. The device is lying flat, with its screen facing the -Z axis. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p>                                    |
+| Handset, tablet                          | Free space data mode portrait (FS DMP)                          | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$ | <p>Image: Diagram of a handset/tablet in the Free space data mode portrait (FS DMP) orientation. The device is tilted at a 45-degree angle from the Z-axis. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p>          |
+| Handset, tablet                          | Free space portrait tilt down                                   | $\Psi=0;$<br>$\Theta=45;$<br>$\Phi=0$ | <p>Image: Diagram of a handset/tablet in the Free space portrait tilt down orientation. The device is tilted at a 45-degree angle from the Z-axis, tilted downwards. The X-axis points left, the Y-axis points right, and the Z-axis points up. The Pitch angle Θ is measured from the Z-axis, the Yaw angle Ψ is measured from the Y-axis, and the Roll angle Φ is measured from the X-axis.</p> |
+
+|                                |                                                               |                                                                                                              |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+|--------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Handset, tablet                | Free space data mode landscape (FS DML)                       | $\Psi=90;$<br>$\Theta=-45;$<br>$\Phi=0$ – left tilt                                                          | <img alt="Diagram showing a handset in landscape orientation with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="949 190 1252 459" src="a147b08b7a2311fd6e2391968931c14b_img.jpg"/>                                                                                                                                                                                                                                                         |
+| Handset, tablet                | Free space landscape tilt down                                | $\Psi=90;$<br>$\Theta=45;$<br>$\Phi=0$ – left tilt                                                           | <img alt="Diagram showing a handset in landscape orientation tilted down with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="949 481 1252 750" src="8952187b46b5ceed6c4b01df625c0c94_img.jpg"/>                                                                                                                                                                                                                                             |
+| Handset, width < 56mm          | Left/right hand narrow phantom data mode portrait (LH/RH DMP) | $\Psi=0;$<br>$\Theta=-45;$<br>$\Phi=0$                                                                       | <img alt="Diagram showing a hand holding a handset in portrait orientation with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="917 772 1284 1153" src="5b9706ecd40852e908c7d9280f9e212a_img.jpg"/>                                                                                                                                                                                                                                          |
+| Handset, 56 mm < width < 72 mm | Left/right hand PDA phantom data mode portrait (LH/RH DMP)    | $\Psi=0;$<br>$\Theta=-45;$<br>$\Phi=0$                                                                       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| Handset width < 56 mm          | Beside head and hand right/left (BHHR/BHHL)                   | $\Psi=60;$<br>$\Theta=6;$<br>$\Phi=-90$ – right side<br>$\Psi=-60;$<br>$\Theta=-6;$<br>$\Phi=90$ – left side | <img alt="Diagram showing a hand holding a handset next to a head phantom in portrait orientation with axes X, Y, Z. Pitch is labeled as Theta, Yaw as Psi, and Roll as Phi." data-bbox="901 1220 1300 1601" src="cf67b3ae51d596591ce42defeb62f9d4_img.jpg"/>                                                                                                                                                                                                                  |
+| Handset 56 < width < 72 mm     | Beside head and hand right/left (BHHR/BHHL)                   | $\Psi=60;$<br>$\Theta=6;$<br>$\Phi=-90$ – right side<br>$\Psi=-60;$<br>$\Theta=-6;$<br>$\Phi=90$ – left side |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| LME                            | Laptop ground plane phantom                                   | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$                                                                         | <img alt="Diagram of a laptop ground plane phantom setup. It shows a 'Laptop ground plane phantom' with 'Conductive film' and 'Conductive adhesive strip'. A 'Choked USB cable or covered with absorbing material' is connected to the phantom. A 'Real functional laptop' is shown below. The angle is labeled '110 degree'. A 'DUT' (Device Under Test) is connected via a 'USB connector'." data-bbox="885 1680 1316 1904" src="6e5302244dc783e0cc95a2f76710974d_img.jpg"/> |
+
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |          |                                      |                                                                                                                                                                                                                                                                                                                                     |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| LEE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | XY plane | $\Psi=0;$<br>$\Theta=0;$<br>$\Phi=0$ | <p>Image: Diagram showing two views of a laptop (Side View and Front View) with orientation angles and dimensions. The Side View shows a 110-degree angle for the screen opening and dimensions X1, X2, Y1, Y2. The Front View shows dimensions Y1, Y2 and a 10-degree angle. Coordinate axes X, Y, Z are shown for both views.</p> |
+| <p>NOTE 1: The orientation angles given in the table define a set of use cases and orientations relative to the spatial channel model. The rotation angles to be used for measurements are FFS. Methodologies not utilizing spatial channel models might not need to define any rotations but are expected to measure for the given use cases.</p> <p>NOTE 2: The CTIA reference antennas have been defined for inter-lab inter-technique testing for the purposes of comparing MIMO OTA methodologies.</p> <p>NOTE 3: For DMP, other pitch positions can be considered FFS.</p> <p>NOTE 4: The absolute throughput usage mode is defined only within the framework of the CTIA reference antennas and is used for comparison of results within/across MIMO OTA methodologies.</p> <p>NOTE 5: Screen up flat positioning reference corresponds to a possible USB/WLAN tethering case, details of implementing this DUT orientation condition such as additional cabling, etc., are FFS.</p> <p>NOTE 6: Left/right/both hand phantoms for the DML usage scenario are not currently defined in 3GPP; until these phantom designs become available, is possible to only define a DML usage scenario in free space.</p> <p>NOTE 7: For a symmetric 2D coverage of testing points in azimuth, DML left and right tilts are expected to produce identical results in free space. Once phantom designs become available, we expect the interaction of the phantom with the antennas to be dependent on the tilt.</p> <p>NOTE 8: The 110 degree angle of the notebook screen opening is a standard reference for all measurements of antennas embedded in notebooks; as a result, the LEE measurement in free space is the principal XY plane cut with respect to this reference.</p> <p>NOTE 9: The orientation angles for the talk mode position are only approximate. The phone positioning is defined as in [11] and in [9] relative to the SAM phantom.</p> |          |                                      |                                                                                                                                                                                                                                                                                                                                     |
+
+The Data Mode Portrait (DMP) conditions are defined in TR 25.914 [11], and are included in this table for completeness. The Data Mode Landscape (DML) testing conditions are not currently defined in any standard testing methodology but benefit from a thorough treatment in academic literature [18]. This testing condition considers free space for all handset sizes until a DML phantom design becomes available, at which time the testing condition will be revisited.
+
+The Laptop Mounted Equipment (LME) and Laptop Embedded Equipment (LEE) testing conditions are well defined in TR 25.914 [11] and constitute an XY plane cut measurement, given the proper orientation of the lid of the laptop ground plane phantom (in the case of LME) or of the laptop itself (in the case of LEE).
+
+Given a 2D ring of symmetrically distributed probes (as in Clause 6):
+
+- The XZ plane is similar to the DML mode except for the additional 45 degrees pitch in the DML case
+- For the phantom case the tilt of the DML case is very relevant since the interaction of the phantoms with the antennas will depend on it – see Figure E.2-2
+
+![Figure E.2-2: Left and Right tilts for landscape mode with left hand phantom. The diagram shows three phone orientations: 'Landscape mode, Left tilt' (Psi = +90), 'Straight up position', and 'Landscape mode, Right tilt' (Psi = -90). A left hand phantom is shown interacting with the phone in the tilted positions. Coordinate axes X, Y, and Z are shown for each orientation. Labels include 'Length of the phone', 'Thickness of the phone', 'Front of Phone', and 'Bottom of Phone'.](e178518844c9a050d9f0e76a8819d9ac_img.jpg)
+
+The diagram illustrates three phone orientations for testing with a left hand phantom. The central orientation is the 'Straight up position'. To the left is 'Landscape mode, Left tilt' with a tilt angle of  $\text{Psi} = +90$ . To the right is 'Landscape mode, Right tilt' with a tilt angle of  $\text{Psi} = -90$ . A left hand phantom is shown gripping the phone in the tilted positions. Coordinate axes X, Y, and Z are indicated for each orientation. The 'Length of the phone' is indicated along the Z-axis in the straight position. The 'Thickness of the phone' is indicated along the X-axis in the straight position. The 'Front of Phone' and 'Bottom of Phone' are also labeled.
+
+Figure E.2-2: Left and Right tilts for landscape mode with left hand phantom. The diagram shows three phone orientations: 'Landscape mode, Left tilt' (Psi = +90), 'Straight up position', and 'Landscape mode, Right tilt' (Psi = -90). A left hand phantom is shown interacting with the phone in the tilted positions. Coordinate axes X, Y, and Z are shown for each orientation. Labels include 'Length of the phone', 'Thickness of the phone', 'Front of Phone', and 'Bottom of Phone'.
+
+**Figure E.2-2: Left and Right tilts for landscape mode with left hand phantom shown to interact differently with the antennas depending on the tilt**
+
+### E.2.1 MPAC Positioning Guidelines
+
+In order for the anechoic chamber multi probe system to emulate the intended propagation statistics within the region of space incident on the DUT antennas, two concepts determine the associated antenna spacing and positioning guidelines. The maximum antenna spacing in the DUT must be within the limit determined by the anechoic chamber multi probe system's ability to emulate the spatial correlation function, and the power stability of the field incident on the DUT antennas must be verified.
+
+![Figure E.2.1-1: Illustration of DUT antenna spacing and positioning guidelines. The figure consists of two circular diagrams, (a) and (b), representing a test chamber. Each diagram shows an 'MPAC probe ring' as an outer circle and 'EUT placement' as a central area. In (a), the EUT is centered on the axis of rotation, and a dashed circle indicates the 'Potential region of uniform power delivered by MIMO system (unverified)'. A line points to the gap between the probe ring and the dashed circle, labeled 'Maximum allowed antenna separation for emulation of spatial correlation function'. In (b), the EUT is not centered on the axis of rotation. It shows the same dashed circle for the unverified power region. A solid yellow circle represents the 'Region of uniform power delivered by MIMO system (verified)'. A line points to the gap between the probe ring and the dashed circle, labeled 'Maximum allowed antenna separation for emulation of spatial correlation function'.](df72bd7468eb8bd59e911d0b5cb7a810_img.jpg)
+
+Figure E.2.1-1: Illustration of DUT antenna spacing and positioning guidelines. The figure consists of two circular diagrams, (a) and (b), representing a test chamber. Each diagram shows an 'MPAC probe ring' as an outer circle and 'EUT placement' as a central area. In (a), the EUT is centered on the axis of rotation, and a dashed circle indicates the 'Potential region of uniform power delivered by MIMO system (unverified)'. A line points to the gap between the probe ring and the dashed circle, labeled 'Maximum allowed antenna separation for emulation of spatial correlation function'. In (b), the EUT is not centered on the axis of rotation. It shows the same dashed circle for the unverified power region. A solid yellow circle represents the 'Region of uniform power delivered by MIMO system (verified)'. A line points to the gap between the probe ring and the dashed circle, labeled 'Maximum allowed antenna separation for emulation of spatial correlation function'.
+
+**Figure E.2.1-1: Illustration of DUT antenna spacing and positioning guidelines;**  
+**a) guideline in this specification, b) example with DUT meeting the maximum allowed antenna separation but not within the verified power stability region**
+
+As the channel model validation procedures for spatial correlation as defined in clause 8.3.2.3 are to be performed at the downlink center frequency in 3GPP TS 36.508 [19], the maximum antenna spacing in the DUT shall be defined by the wavelength per operating band center frequency of the middle channel of the downlink at the band under test. A verification of power stability can be derived from the spatial correlation verification results in clause 8.3.2.3. Given that this verification spans a region with a diameter of 1 wavelength centered on the axis of rotation in the chamber and that the performance demonstrated by multiple 8 dual-polarized probe MPAC implementations in clause 8.4.4 has shown good alignment up to 0.85  $\lambda$  for SCME UMi, the region where DUT antennas shall be placed (the MIMO OTA test zone) shall be defined in the same way (see Figure E.2.1-1a above) but further confined by the 0.85  $\lambda$  antenna separation limit for SCME UMi. Figure E.2.1-1b above provides an example of a DUT meeting the maximum allowed antenna separation but not within the verified power stability region; this placement of a DUT shall not be used. The optimization of the maximum allowed antenna spacing of the DUT and the verification of the test zone, as well as SCME UMa considerations, are expected as part of future work.
+
+The region of uniform power delivered by the MIMO system (unverified) as shown in Figure E.2.1-1 is an indication of the region where the wavefront may maintain its uniformity. Therefore, it may be used to extend the test volume but is not allowed at this time. It is considered unverified because the validation of spatial correlation provides a verification that spans a region of 1  $\lambda$ . Any further extension of the verified test volume would require an update to the spatial correlation validation in clause 8.3.2.3.
+
+The DUT maximum antenna spacing and placement within the test zone shall be defined by the following two-tier methodology due to the primary radiation modes below 1 GHz and above 1 GHz and how they relate to the device and/or antenna size.
+
+When operating in frequency bands lower than 1GHz, the physical center of the DUT shall be placed in the chamber center, the DUT shall be completely contained within the volume defined by the respective operating band equivalent to a sphere with a radius equal to 0.425 wavelength as defined in Tables E.2.1-1 and Tables E.2.1-2 for SCME UMi.
+
+When operating in frequency bands higher than 1 GHz the equidistant physical point between the DUT MIMO antenna system shall be placed in the chamber center following guidance defined in Figure E.2-2 and the DUT MIMO antenna system (further physical dimension or both antennas' maximum E-field regions) shall be completely contained within the volume defined by the respective operating band equivalent to a sphere with a radius equal to 0.425 wavelength defined in Tables E.2.1-1 and Tables E.2.1-2 for SCME UMi. The definition of the equidistant point between the DUT MIMO antennas shall be provided through manufacturer declaration for all operating bands where the maximum antenna separation requirement has been met. The location of the equidistant point(s) for each operating band shall be
+
+identified by the manufacturer by either marking the device utilized for MIMO OTA testing or by providing clear instructions to the test operator as to the physical location(s).
+
+The two-tier approach is needed to be technically correct when defining the MPAC test volume. While the geometric center can be used in frequencies lower than 1GHz, the same methodology will add unnecessary limitations for test applicability in frequencies above 1GHz. In this case, manufacturers will need to provide further information to enable the proper definition of the test volume. Ideally, the same approach adopted in frequencies above 1 GHz could be used for all frequencies. However, the extra positioning work and need to identify the equidistant point between the DUT MIMO antennas isn't necessary for frequencies under 1GHz since the wavelength dimension is large enough for all handsets, phablets, and most tablets and laptops.
+
+![Figure E.2-2: Definition of distance between MIMO antennas and DUT center, maximum physical separation, or E-field maximum separation defined by manufacturer. The diagram shows two cases: one for low frequencies where the geometric center is used, and another for high frequencies where the E-field maximum separation is used.](15d97ee42b0c3d8c1c45245583d67ff1_img.jpg)
+
+The diagram illustrates two methods for defining the distance between MIMO antennas and the DUT center. Both cases show a rectangular device with two antennas, Antenna 1 and Antenna 2, and a red cross marking the center of the MIMO antenna system.
+
+**Left Case (Low Frequency):** A dashed green line connects Antenna 1 and Antenna 2. A red cross marks the center of the MIMO antenna system. A green label indicates the "Maximum physical Distance 'd' between antennas".
+
+**Right Case (High Frequency):** A dashed green line connects Antenna 1 and Antenna 2. A red cross marks the center of the MIMO antenna system. A green label indicates the "Maximum E-field Distance 'd' between antennas". Dashed circles are drawn around each antenna, labeled "High E-field Antenna 1" and "High E-field Antenna 2".
+
+Figure E.2-2: Definition of distance between MIMO antennas and DUT center, maximum physical separation, or E-field maximum separation defined by manufacturer. The diagram shows two cases: one for low frequencies where the geometric center is used, and another for high frequencies where the E-field maximum separation is used.
+
+**Figure E.2-2: Definition of distance between MIMO antennas and DUT center, maximum physical separation, or E-field maximum separation defined by manufacturer**
+
+**Table E.2.1-1: Test zone dimension definition vs. FDD band of operation**
+
+| <b>Band</b> | <b>DL middle channel frequency (MHz)</b> | <b>0.85*Wavelength (m) middle channel</b> | <b>Test volume sphere radius (m)</b> |
+|-------------|------------------------------------------|-------------------------------------------|--------------------------------------|
+| 1           | 2140                                     | 0.119                                     | 0.060                                |
+| 2           | 1960                                     | 0.130                                     | 0.065                                |
+| 3           | 1842.5                                   | 0.138                                     | 0.069                                |
+| 4           | 2132.5                                   | 0.119                                     | 0.060                                |
+| 5           | 881.5                                    | 0.289                                     | 0.145                                |
+| 6           | 880                                      | 0.290                                     | 0.145                                |
+| 7           | 2655                                     | 0.096                                     | 0.048                                |
+| 8           | 942.5                                    | 0.270                                     | 0.135                                |
+| 9           | 1862.4                                   | 0.137                                     | 0.068                                |
+| 10          | 2140                                     | 0.119                                     | 0.060                                |
+| 11          | 1485.9                                   | 0.171                                     | 0.086                                |
+| 12          | 737.5                                    | 0.346                                     | 0.173                                |
+| 13          | 751                                      | 0.339                                     | 0.170                                |
+| 14          | 763                                      | 0.334                                     | 0.167                                |
+| 17          | 740                                      | 0.344                                     | 0.172                                |
+| 18          | 867.5                                    | 0.294                                     | 0.147                                |
+| 19          | 882.5                                    | 0.289                                     | 0.144                                |
+| 20          | 806                                      | 0.316                                     | 0.158                                |
+| 21          | 1503.4                                   | 0.169                                     | 0.085                                |
+| 22          | 3550                                     | 0.072                                     | 0.036                                |
+| 23          | 2190                                     | 0.116                                     | 0.058                                |
+| 24          | 1542                                     | 0.165                                     | 0.083                                |
+| 25          | 1962.5                                   | 0.130                                     | 0.065                                |
+| 26          | 876.5                                    | 0.291                                     | 0.145                                |
+| 27          | 860.5                                    | 0.296                                     | 0.148                                |
+| 28          | 780.5                                    | 0.326                                     | 0.163                                |
+| 29          | 722.5                                    | 0.353                                     | 0.176                                |
+| 30          | 2355                                     | 0.108                                     | 0.054                                |
+| 31          | 465                                      | 0.548                                     | 0.274                                |
+| 32          | 1474                                     | 0.173                                     | 0.086                                |
+
+**Table E.2.1-2: Test zone dimension definition vs. TDD band of operation**
+
+| <b>Band</b> | <b>DL middle channel frequency (MHz)</b> | <b>0.85*Wavelength (m) middle channel</b> | <b>Test Volume Sphere Radius (m)</b> |
+|-------------|------------------------------------------|-------------------------------------------|--------------------------------------|
+| 34          | 2017.5                                   | 0.126                                     | 0.063                                |
+| 35          | 1880                                     | 0.136                                     | 0.068                                |
+| 36          | 1960                                     | 0.130                                     | 0.065                                |
+| 37          | 1920                                     | 0.133                                     | 0.066                                |
+| 38          | 2595                                     | 0.098                                     | 0.049                                |
+| 39          | 1900                                     | 0.134                                     | 0.067                                |
+| 40          | 2350                                     | 0.108                                     | 0.054                                |
+| 41          | 2593                                     | 0.098                                     | 0.049                                |
+| 42          | 3500                                     | 0.073                                     | 0.036                                |
+| 43          | 3700                                     | 0.069                                     | 0.034                                |
+| 44          | 753                                      | 0.338                                     | 0.169                                |
+
+The positioning of the device under test within the test volume shall be set as defined above and in Clause 9.4.
+
+The environmental requirements for the device under test shall be set as defined in Annex D.
+
+### E.2.2 RTS Positioning Guidelines and test zone dimensions
+
+For the RTS system, it can be seen from earlier analysis in the MU budget in Annex B.2 that the MU elements related to device size are linked to uncertainties in the field uniformity of the anechoic chamber used for the first stage antenna pattern measurement. The RTS MU budget was calculated with the assumption that the device size was within the limits defined by the chamber quiet zone defined in TS 34.114 Annex A2.3, TS 34.114 E.10 and as measured in TS 34.114 Annex G.2. The applicable device size for RTS is therefore the same as used for SISO TRS in the same chamber.
+
+The second stage of the RTS method which involves a cable replacement radiated connection, is assumed in the MU budget to take place in the same anechoic chamber as was used for the first stage antenna pattern measurement, and there are no additional test zone considerations required. The use of a different chamber for the second stage is not precluded, but would require a recalculation of the impact of any difference between the anechoic chambers.
+
+For device positioning within the test zone for the first stage the normal positioning accuracy assumed in Table B.2-1 of 0.5 degrees is considered insignificant compared to the raster used for the antenna measurement.
+
+For the second stage positioning impact, and with the assumption the chamber is the same as used in the first stage, the issue is the repeatability of the position used from the first stage. This is likely to be less than the 0.5 degree absolute positioning error so is again assumed to be negligible.
+
+# --- Annex F: Calibration
+
+## F.1 Scope
+
+Here the absolute power level calibration in the center of the test zone is described. Note that Clause 8.3 describes in detail the verification process for the various channel models however in addition to that an absolute power calibration needs to be performed as well. Note also that the channel model validation and absolute power calibration may have different renewal cycles.
+
+## --- F.2 Calibration Procedure – Anechoic chamber method with multiprobe configuration
+
+The system needs to be calibrated in two steps in order to ensure that the absolute power is correct. The first calibration steps ensures the accurate generation of the channel model in the center of the chamber as required by Clause 8.3. The second step validates the total power as would be seen by the DUT and allows for that power to be scaled up or down if necessary.
+
+Considering the complexity of the system various way to calibrate are possible. The end goals are however the same no matter the exact procedure. The two steps must achieve the following:
+
+**Step 1:** This step is used to equalize the power in the center coming from the different probes. This being a relative measurement is very robust and with minimal uncertainty. It is sufficient to use instruments calibrated according to the manufacturer's specifications and the measurements require no additional calibration. This step is done for both vertical and horizontal polarizations. The relative differences between probe path losses are recorded and used (typically in the fading emulator) to adjust the generated fading signals for each probe. Example measurement set-up is shown in Figure 8.3.1.1-1.
+
+NOTE 1: If Step 1 is performed as an absolute measurement accounting for the cable and reference antenna gains Step 2 can be omitted.
+
+**Step 2:** This step is used to measure the total absolute power of at least one polarization in the center of the ring. Then assuming that validation of the channel models has been done, the total power available to the DUT in the center of the chamber can be computed. If necessary the power can be scaled up or down to achieve the desired power level. Since this is an absolute power measurement, the measurement cable and reference antenna gains have to be accounted for.
+
+NOTE 2: To minimize measurement uncertainty the passive and active components of the system may be calibrated independently as well as at different intervals.
+
+NOTE 3: Step 2 of the calibration should be performed with the channel model loaded and LTE signaling active. Sufficient amount of time averaging is required because of the fading nature of the models used.
+
+NOTE 4: Various ways of performing the two steps may exist depending on the equipment used. The lab is responsible for providing a comprehensive calibration procedure.
+
+NOTE 5: Steps one and two may be combined with the channel verification procedure.
+
+NOTE 6: The calibration must be performed for all frequencies of interest.
+
+### F.2.1 Example Calibration Procedure
+
+The calibration procedure outlined below is only one possibility based on a concrete measurement set-up. Improvements can be made to minimize measurement uncertainty.
+
+#### Step 1:
+
+1. Place a vertical reference dipole in the center of the chamber, connected to a VNA port, with the other VNA port connected to the input of the channel emulator unit – Figure 8.3.1.1-1.
+2. Configure the channel emulator for bypass mode (NOTE this might not be available in all instruments)
+3. Measure the response of each path from each vertical polarization probe to the reference antenna in the center.
+4. Adjust the power on all vertical polarization branches of the channel emulator so that the powers received at the center are equal.
+5. Repeat the steps 1 to 4 with the magnetic loop and horizontally polarized probes instead, and adjust the horizontal polarization branches of the channel emulator.
+
+NOTE: At this stage all vertical polarization paths have equalized gains, and so do all horizontal polarization paths. The two polarizations however do not necessarily produce the same signal strength in the center of the chamber – this most commonly happens if two physically different channel emulators are used for the two polarizations. The resulting power imbalance can be accounted for either at this step or adjusted at point 7 of step 2.
+
+#### Step 2 (see Figure F.2.1-1):
+
+1. Place a vertical reference dipole in the center of the chamber connected to a spectrum analyzer via an RF cable.
+
+NOTE: A power meter can also be used.
+
+2. Record the cable and reference dipole gains.
+3. Load the target channel model
+4. Start the LTE signaling in the base station emulator with the required parameter identical to the measurements conditions (some special instrument options might be necessary).
+5. Average the power received by the spectrum analyzer for a sufficient amount of time to account for the fading channel – one full channel simulation might be unnecessary.
+6. Repeat steps 1 to 4 with a magnetic loop for the horizontal polarization (NOTE: this way no prior validation of the channel model is required)
+7. Calculate the total power received at the test area as the sum of the power in the two polarizations.
+8. Adjust the power in the two polarizations if necessary. The power adjustment can be a simple scaling of the power up or down or adjustment of the XPR due to slight differences in the fading unit's branches. Depending on the adjustment needed, it can be done at the base station emulator or the channel emulator or both.
+
+![Figure F.2.1-1: Example setup for step 2 of the calibration. The diagram shows a signal flow from a Radio Communication Tester to a Channel Emulator (with interference injection), then to an Amplifier Box, and finally to a MIMO Ring. The MIMO Ring contains multiple Probe Antennas and a Reference Antenna. A Spectrum Analyzer is connected to the Reference Antenna.](3d6d0738981fdd03d003cc653bdfdaae_img.jpg)
+
+The diagram illustrates the calibration setup. On the left, a 'Radio Communication Tester' is connected to a 'Channel Emulator (interference injected at or after emulator output)'. The output of the emulator is connected to an 'Amplifier Box'. The output of the amplifier box is connected to a 'MIMO Ring'. The MIMO Ring is a circular structure containing several 'Probe Antennas' and a 'Reference Antenna'. A 'Spectrum Analyzer' is connected to the 'Reference Antenna'.
+
+Figure F.2.1-1: Example setup for step 2 of the calibration. The diagram shows a signal flow from a Radio Communication Tester to a Channel Emulator (with interference injection), then to an Amplifier Box, and finally to a MIMO Ring. The MIMO Ring contains multiple Probe Antennas and a Reference Antenna. A Spectrum Analyzer is connected to the Reference Antenna.
+
+Figure F.2.1-1: – Example setup for step 2 of the calibration
+
+## F.3 Calibration Procedure – Reverberation chamber method
+
+The purpose of the calibration measurement is to determine the average power transfer function in the chamber, mismatch of fixed measurement antennas and path losses in cables connecting the power sampling instrument and the fixed measurement antennas. Preferably a network analyzer is used for these measurements. Recommended calibration antennas are dipoles tuned to the frequency band of interest.
+
+In general, the calibration of a reverberation chamber is performed in three steps:
+
+1. Measurement of S-parameters through the reverberation chamber for a complete stirring sequence
+2. Calculation of the chamber reference transfer function
+3. Measurement of connecting cable insertion loss
+
+If several setups are used (e.g. empty chamber, chamber with head phantom, etc.), steps 1 and 2 must be repeated for each configuration. The calibration measurement setup can be studied in Figure F.3-1.
+
+![Diagram of calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' is connected to 'Port 1' of a 'Vector network analyzer' (VNA). A 'Fixed measurement antenna' is connected to 'Port 2' of the VNA. Arrows labeled 'VNA calibration points' point to both antennas. A mode stirrer is also shown inside the chamber.](c0ef0292328b1602e278f6a0b2ee07e0_img.jpg)
+
+Diagram of calibration measurement setup in a reverberation chamber. A rectangular box represents the 'Reverberation chamber'. Inside, a 'Reference antenna' is connected to 'Port 1' of a 'Vector network analyzer' (VNA). A 'Fixed measurement antenna' is connected to 'Port 2' of the VNA. Arrows labeled 'VNA calibration points' point to both antennas. A mode stirrer is also shown inside the chamber.
+
+**Figure F.3-1: Calibration measurement setup in the reverberation chamber, using a vector network analyzer**
+
+### F.3.1 Measurement of S-parameters through the chamber for a complete stirring sequence
+
+This step will measure S-parameters through the reverberation chamber through a complete stirring sequence. This information is required to determine the chamber's reference transfer function. The procedure must be performed separately for each measurement setup of which the loading of the chamber has been changed. The calibration procedure must be repeated for each frequency as defined above. Therefore, it is advantageous if the network analyzer can be set to a frequency sweep covering the defined frequencies, so that all frequencies of interest can be measured with a minimal number of measurement runs.
+
+- i. Place all objects into the RC which will be used during the throughput measurements, including a head phantom, hand phantom and fixture for the EUT. This ensures that the loss in the chamber, which determines the average power transfer level, is the same during both calibration and test measurements. Also, if the EUT is large or contains many antennas, it may represent a noticeable loading of the chamber. It should then be present in the chamber and turned on during the calibration.
+- ii. Place the calibration antenna inside the chamber. The calibration antenna is preferably mounted on a low-loss dielectric fixture, to avoid effects from the fixture itself which may affect the EUT's radiation efficiency and mismatch factor. The calibration antenna must be placed in the chamber in such a way that it is far enough from any walls, mode-stirrers, head phantom, or other object, such that the environment for the calibration antenna (taken over the complete stirring sequence) resembles a free space environment. "Far enough away" depends on the type of calibration antenna used. For low gain nearly omni-directional antennas like dipoles, it is normally sufficient to ensure that this spacing is larger than 0.5 wavelengths. More directive calibration antennas should be situated towards the centre of the chamber. The calibration antenna should be present in the chamber during the throughput measurements.
+- iii. Calibrate the network analyzer with a full 2-port calibration in such a way that the vector S-parameters between the ports of the fixed measurement antenna and the calibration antenna can be accurately measured. Preferably, the network analyzer is set to perform a frequency sweep at each stirrer position. This will enable calibration of several frequency points during the same stirring sequence, thereby reducing calibration time. This will also enable frequency stirring, i.e., averaging the measured power transfer function over a small frequency bandwidth around each measured frequency point (moving frequency window). This will increase accuracy at the expense of frequency resolution.
+
+- iv. Connect the antennas and measure the S-parameters for each stirrer position and each fixed measurement antenna.
+
+The number of stirrer positions in the chosen stirring sequence, i.e. the number of S-parameter samples at each frequency point, should be chosen in such a way that it is large enough to yield an acceptable statistical contribution to the total measurement uncertainty.
+
+### F.3.2 Calculation of the chamber reference transfer function
+
+From the S-parameters obtained in the calibration measurement, the chamber reference transfer function for fixed antenna n can be calculated. The reflection coefficient for fixed antenna n can be calculated as
+
+Thus, the chamber reference transfer function can be calculated as
+
+where M is the total number of samples of the transfer function measured for each fixed measurement antenna and  $m$  is sample number m of the transfer function for measurement antenna n. Moreover,  $\Gamma_n$  is the complex average of the calibration antenna reflection coefficient. Finally,  $\epsilon_n$  is the radiation efficiency of the calibration antenna.
+
+Note that the radiation efficiency of the fixed antenna is not corrected for, because it will be the same both during calibration and measurements. Therefore the fixed antenna's radiation efficiency will not affect the final results. The same can be said about the mismatch factor of the fixed measurement antennas, but it is still advantageous to correct for this factor if frequency stirring is applied to improve accuracy.
+
+### F.3.3 Cable calibration
+
+This measurement step will calibrate the power loss of the cables needed to connect the instrument to the reverberation chamber.
+
+- i. Disconnect the cables between the VNA and the chamber.
+- ii. Connect the cables one-by-one between the two ports of the network analyzer. The VNA must be calibrated at its own two ports.
+- iii. Measure the frequency response of the transmission S-parameter ( $S_{21}$  or  $S_{12}$ ) of the cable.
+- iv. Save the power transfer values ( $|S_{21}|^2$ ) of the frequency response curve for the test frequencies. and cables positions, etc).
+
+## --- F.4 Calibration Procedure: RTS method
+
+For the RTS method, only the DUT reporting RSAP calibration is to perform. The RTS method depends on reported RSAP to do the antenna pattern measurement, and the power calibration for radiated second-stage throughput test. Since these reported readings do not come from a calibrated measurement instrument, their accuracies are often subject to questioning. Below procedure provides method for proper calibration to validate the reported RSAP accuracy.
+
+- DUT reporting RSAP calibration calibration:
+
+With proper spherical coordinate definition of mobile terminal setup, the receive antenna pattern at any coordinate ( $\theta_i$ ,  $\phi_i$ ) can be expressed as:
+
+$$P(\theta_i, \phi_i) = \text{RS}_i \quad (1)$$
+
+The test point  $(\theta_i, \phi_i)$  can be at any point on the  $4\pi$  solid angle of the coordinate. More precisely, the reported RS of the UE can be expressed as:
+
+$$\text{RS}_i(x) = m(x) * x + c \quad (2)$$
+
+where  $m(x_i)$  and  $c$  is a function of signal strength independent of testing point angular coordinates.  $x$  is the actual incident field power density that can be derived from the signal power and test range loss. The above equation (2) assumes that the signal variables in both sides of the equation are expressed in decibels or dB's. When  $m(x)=1$  and  $c=g_0$ , where  $g_0$  is the received antenna gain at the test point, we would have declared that the RS report is a true reading of the signal strength. But in reality,  $m(x)$  can be biased by either the signal level relative to the receiver's detector operating condition, or by application software programming errors. Meanwhile, the offset constant  $c$  can also be biased by either the noise floor of the receiver and/or other artificial factors in the UE RS reporting. Therefore, a Taylor's series can be introduced to have a better representation of the RS report value:
+
+$$\text{RS}_i(x) = c + ax + bx^2 + dx^3 + ex^4 + \dots \quad (3)$$
+
+In theory, equation (3) may require many terms to represent the RS report accurately. However, since the reported RS reading in the receive antenna pattern in (1) has a limited signal dynamic range, the following three term expression is enough to correct for the reporting errors:
+
+$$\text{RS}_i(x) = c + ax + bx^2 + o(x^3) \quad (4)$$
+
+The third order term  $o(x^3)$  is ignored since it is not significant for limited signal dynamic range.
+
+The RS pattern in (1) will need to be calibrated for its possible reporting errors. One practical method is to introduce signal correction terms in equation (4) to enhance the accuracy. This process is also referred to as the linearization. The following steps describe what is needed to linearize the RS report and the RS antenna pattern in (1):
+
+- 1). Find the maximum RS reading in the pattern obtained in (1) from all angular test points, and at all polarizations. Set this point as the reference point and record signal generator power  $P_0$  and let  $x_0 = P_0 - \text{Test Range Path Loss (in dB)}$ , and note the maximum RS reading as  $r_0$ .
+- 2). At the reference test point, decrease the signal generator's output power  $P_i$ , and let  $x_i = P_i - \text{Test Range Path Loss (in dB)}$ , starting from  $P_0$  with a step size (1.0 dB by default) to a power range so as to obtain the full RS reading range while searching from the reference point  $r_0$  when the test system dynamic range allows, or to 20 dB by default when the system dynamic range is known to be limited, whichever is lower in range. Record the corresponding RS reading of the UE as  $r_i$ . Repeat this process until all angular test points are completed as required.
+- 3). Use those pairs of data obtained in Step 2)  $(r_i, x_i)$  as the input of the quadratic fitting curve in (4) to formulate the Algorithm LSF (Least Square Fit) to calculate the three coefficients  $(a, b, \text{ and } c)$  in:
+
+$$\text{Err}(a, b, c) = \sum (c + ax_i + bx_i^2 - r_i)^2 \quad (5)$$
+
+Please note that the power range of the linearization can be limited to 20 dB as stated in Step 2) since the lower RS readings than the processed range do not contribute to the overall receive antenna pattern as much.
+
+Once the three coefficients  $(a, b, \text{ and } c)$  are obtained in LSF of (5), the use of the inverse function of Equation (4) to convert RS pattern in (1) into the normalized incident power pattern. This process completes the error correction for both constant biased and the non-linearity in the RS report from the UE within the limited signal dynamic range as tested in (1) and Step 1. Similar steps can be applied for error corrections if multiple receiver RS are involved in the testing.
+
+Of course, the reference test point can also be further tested for the threshold of the receiver sensitivity and/or throughput knee-point for the required calibrated reference power level.
+
+## F.5 Noise Floor Measurement Procedure – Anechoic chamber method with multiprobe configuration
+
+The noise floor of system at the DUT location must be sufficiently lower than the signal levels used to measure the device. The following procedure determines the noise level at the DUT location.
+
+Prior to measuring the system, the noise floor of the spectrum analyser is measured. The noise floor of the spectrum analyser must be at or lower than the noise floor limit of TBD.
+
+### Measure the Noise Floor of the Spectrum Analyzer:
+
+1. Connect a 50 ohm load to the input of the Spectrum Analyzer
+2. Turn on the Spectrum Analyzer and allow it to come to a stable operating temperature
+3. Set the spectrum analyzer as follows:
+  - Averaging set to 20
+  - Set Detector (Averaging) to RMS
+  - Span 13.5 MHz
+  - Resolution BW 30 kHz
+  - Video BW 50 MHz
+  - (Optional) Pre-amplifier on
+  - Internal attenuator set to 0 dB
+4. Set the reference level according to the signal level that you are measuring.
+5. Measure the average power over the channel bandwidth.
+
+### Measuring the MPAC system Noise Floor
+
+The system shall be set up in the standard MPAC configuration. For each frequency to be evaluated perform the following steps.
+
+1. Power on all the equipment and allow it to come to a stable operating temperature
+2. Load the channel model as defined in 3GPP TR 37.977 in the channel emulator.
+3. Using the channel emulator set the power level at the DUT location to -90 dBm/ 15 kHz.
+4. Turn off the signal input to the channel emulator.
+5. Set the spectrum analyzer as follows:
+  - Averaging set to 20
+  - Set Detector (Averaging) to RMS
+  - Span 13.5 MHz
+  - Resolution BW 30 kHz
+  - Video BW 50 MHz
+  - (Optional) Pre-amplifier on
+
+- Internal attenuator set to 0 dB
+- 6. Connect the output of the first RF Amplifier which corresponds to the first channel output of the channel emulator to the spectrum analyser using a cable with a known loss.
+- 7. Set the reference level according to the signal level that you are measuring.
+- 8. Measure the average power over the channel bandwidth.
+- 9. Add the losses from the output of the Amplifier to the DUT location to the measurement performed in step 8.
+- 10. Repeat steps 6 through 9 until all 16 channels have been measured.
+- 11. Sum the noise (at DUT location calculated in step 9) from all 16 paths (in linear and convert to dBm) and account for any necessary additional cable losses (from amplifier output to Spectrum Analyzer input).
+
+The result found in step 11 should be at or below the noise floor limit of TBD.
+
+# --- Annex G: Test Volume Validation
+
+This annex describes the procedures for validating the test volume for the different methodologies.
+
+## --- G.1 Test Volume Validation for the RC+CE Methodology
+
+The crucial parameters for defining the RC+CE test volume are the isotropy and the standard deviation of the power transfer function. The validation procedure will thus consist of the following:
+
+- Isotropy measurements in the extreme positions (boundaries) of the test volume, as well as in positions within the boundaries of the test volume.
+- Standard deviation of the power transfer function measured in the same positions as defined for the isotropy measurements.
+
+This is described in detail below.
+
+### G.1.1 Test Volume Validation Setup
+
+There are two main RC configurations available in the industry. The first configuration utilizes a turntable for the stirring sequence and thus to emulate the desired environment. Additional stirring procedures might also exist to further improve the accuracy of the emulated channel properties. The DUT is kept on the turntable throughout the measurement sequence, thus moved around in the test volume.
+
+The second configuration does not utilize a turntable, thus instead relying on other stirring procedures for emulating the desired environment. For this case the DUT is kept at a fixed position in the test volume throughout the measurement sequence.
+
+In order to define a generic test volume validation procedure, it is needed to differentiate between these two types of RCs.
+
+#### G.1.1.1 Type 1 Reverberation Chamber – With Turntable
+
+For RCs utilizing a stirring configuration with a turntable, the test volume will consist of a cylinder as depicted in Figure G.1.1.1-1. The Test Volume Validation Positions (TVVPs) in this test volume consist of extreme positions, e.g. minimum distances to other metallic and/or absorbing objects and the location on the turntable, as well as additional positions representative to DUT test positions. Based on Figure G.1.1.1-1, the following baseline TVVPs are identified:
+
+- TVVP1-3: These three positions correspond to the lower extremes of having the DUT as close as possible to the metallic turntable plate and still fulfil the  $0.5 \lambda$  guideline from [22].
+  - o TVVP1 will experience a minimum of statistics, given that a DUT in this position will be kept at the same position throughout the measurement. This position could also be shifted away from the centre of the turntable, if needed for the accuracy of the measurements. For such case, the test volume would be a cylinder with the centre excluded.
+  - o TVVP2 corresponds to additional test position representative to DUT test position for gathering sufficient statistics.
+
+- o TVVP3 is the edge of the test volume. This is the position farthest away from the turntable centre that still fulfils the requirement in [22] of being 0.5 lambda separated from other metallic or absorbing objects in the chamber (e
+- TVVP4-6: These three positions correspond to additional test positions in the centre azimuth cut of the cylinder representative to DUT test positions, in order to gather sufficient statistics for the validation. The individual points correspond to the same distances from the centre of the turntable as TVVP1-3.
+- TVVP7-9: These three positions correspond to extreme points at the upper edge of the test volume, which still satisfy the requirements in [22] of being 0.5 lambda away from metallic or absorbing objects (in this case the metallic stirrer plate; it can also be bounded by the roof of the chamber). The individual points correspond to the same distances from the centre of the turntable as TVVP1-3.
+
+One azimuth cut consisting of 3 TVVPs is shown in Figure G.1.1.1-2 for clarity.
+
+In addition to metallic surfaces and objects, different amount of absorbing objects can be used for obtaining the desired chamber characteristics. If such objects exist the boundaries of the test volume must be set as to take these into account. This case is depicted in Figure G.1.1.1-3, where the absorber located on the chamber wall decreases the size of the test volume.
+
+The 9 positions defined above will be the TVVPs for Type 1 RCs and will define the valid test volume. The test system vendor should declare these 9 TVVPs for each implementation.
+
+Having nine individual measurements will provide a sufficient statistical ground for concluding on the RC test volume characteristics. It matches the minimum number of points adopted for characterizing the uncertainty related to the chamber statistical ripple and repeatability in TS34.114 [4]. Observe however that there will be three orientations measured for each position, in order to calculate the anisotropy coefficients. This means that there will be 27 individual estimates of the power transfer function and all of these shall be used for the standard deviation calculation.
+
+In order to pass the test volume validation, the isotropy in all TVVPs must satisfy the requirements and standard deviation of the power transfer function must result in an acceptable overall uncertainty once combined with the other uncertainty sources. If any of the positions fail the isotropy test or the resulting uncertainty exceeds acceptable limits, the test volume boundaries, and thus the TVVPs, must be redefined and the procedure repeated in the new TVVPs.
+
+![Schematics of the test volume and baseline TVVPs for Type 1 RC.](0ba76cf9e44e2bdf70c30182f7990ce7_img.jpg)
+
+This diagram illustrates a cylindrical test volume mounted on a turntable. The test volume is labeled 'Test Volume' and has a radius of  $0.5\lambda$ . It is positioned between two 'Stirrers'. The turntable is labeled 'Turntable'. Nine baseline Test Volume Validation Positions (TVVPs) are marked with black dots: TVVP1, TVVP2, and TVVP3 are on the bottom face; TVVP4, TVVP5, and TVVP6 are on the side surface; and TVVP7, TVVP8, and TVVP9 are on the top face. The distance between the top and bottom faces is also  $0.5\lambda$ . The distance from the side surface to the nearest stirrer is indicated as  $> 0.5\lambda$ .
+
+Schematics of the test volume and baseline TVVPs for Type 1 RC.
+
+Figure G.1.1.1-1: Schematics of the test volume and baseline TVVPs for Type 1 RC.
+
+![Top view schematics of one azimuth cut of the test volume consisting of 3 TVVPs for Type 1 RC.](56bd052546d4b5a5eb90bc8235ab4c81_img.jpg)
+
+This top-view diagram shows a solid blue circle representing the test volume. A dashed blue circle represents the 'Test volume outer boundary'. Three black dots, labeled 'Test volume validation positions', are shown: one at the center of the test volume, one on the boundary of the test volume, and one on the outer boundary.
+
+Top view schematics of one azimuth cut of the test volume consisting of 3 TVVPs for Type 1 RC.
+
+Figure G.1.1.1-2: Top view schematics of one azimuth cut of the test volume consisting of 3 TVVPs for Type 1 RC.
+
+![Schematics of the test volume and TVVPs for Type 1 RC, when the test volume is bounded by an absorber on the chamber wall. The diagram shows a cylindrical test volume with a turntable at the bottom. An absorber is on the left wall. Two stirrers are shown, one above and one to the right. The test volume is bounded by the absorber on the left and the stirrers on the top and right. The distance from the absorber to the test volume is 0.5λ. The distance from the stirrers to the test volume is > 0.5λ. The distance from the turntable to the test volume is 0.5λ. The test volume is labeled 'Test Volume'. The TVVPs are labeled TVVP1 through TVVP9. TVVP1-4 are at the bottom, TVVP5-8 are at the top, and TVVP9 is in the center.](bbad6dce7d0dca9ee0b885b4f28453b2_img.jpg)
+
+Schematics of the test volume and TVVPs for Type 1 RC, when the test volume is bounded by an absorber on the chamber wall. The diagram shows a cylindrical test volume with a turntable at the bottom. An absorber is on the left wall. Two stirrers are shown, one above and one to the right. The test volume is bounded by the absorber on the left and the stirrers on the top and right. The distance from the absorber to the test volume is 0.5λ. The distance from the stirrers to the test volume is > 0.5λ. The distance from the turntable to the test volume is 0.5λ. The test volume is labeled 'Test Volume'. The TVVPs are labeled TVVP1 through TVVP9. TVVP1-4 are at the bottom, TVVP5-8 are at the top, and TVVP9 is in the center.
+
+**Figure G.1.1.1-3: Schematics of the test volume and TVVPs for Type 1 RC, when the test volume is bounded by an absorber on the chamber wall.**
+
+#### G.1.1.2 Type 2 Reverberation Chamber – Without Turntable
+
+For RCs utilizing a stirring configuration without a turntable, the test volume will consist of a rectangular box as depicted in Figure G.1.1.2-1. As for Type 1 chambers, the TVVPs correspond to extreme positions, e.g. minimum distances to other metallic and/or absorbing objects and the location on the turntable, as well as additional positions representative to DUT test positions. Based on Figure G.1.1.2-1, the following baseline TVVPs are identified:
+
+- TVVP1-4: These four corner positions correspond to the lower extremes of having the DUT as close as possible to the metallic floor as well as two additional walls of the chamber (or stirrers and other metallic objects) and still fulfil the 0.5 lambda guideline from [22].
+- TVVP5-8: These four corner positions correspond to the upper extremes of having the DUT as close as possible to the metallic roof as well as two additional walls of the chamber (or stirrers and other metallic objects) and still fulfil the 0.5 lambda guideline from [22]. The individual points correspond to the same distances from the chamber walls as TVVP1-4.
+- TVVP9: This is the centre position of the test volume and represents an additional point representative to DUT test position and provides additional statistics.
+
+In addition to metallic surfaces and objects, different amount of absorbing objects can be used for obtaining the desired chamber characteristics. If such objects exist the boundaries of the test volume must be set as to take these into account, as for Type 1 RCs.
+
+The 9 positions defined above will be the TVVPs for Type 2 RCs and will define the valid test volume. The test system vendor should declare these 9 TVVPs for each implementation.
+
+Having nine individual measurements will provide a sufficient statistical ground for concluding on the RC test volume characteristics. It matches the minimum number of points adopted for characterizing the uncertainty related to the chamber statistical ripple and repeatability in TS34.114 [4]. Observe however that there will be three orientations measured for each position, in order to calculate the anisotropy coefficients. This means that there will be 27 individual estimates of the power transfer function and all of these shall be used for the standard deviation calculation.
+
+In order to pass the test volume validation, the isotropy in all TVVPs must satisfy the requirements and standard deviation of the power transfer function must result in an acceptable overall uncertainty once combined with the other uncertainty sources. If any of the positions fail the isotropy test or the resulting uncertainty exceeds acceptable limits, the test volume boundaries, and thus the TVVPs, must be redefined and the procedure repeated in the new TVVPs.
+
+![Schematics of the test volume and baseline TVVPs for Type 2 RC. The diagram shows a rectangular 'Test Volume' containing nine Test Volume Reference Points (TVVPs). TVVP1, TVVP2, TVVP3, and TVVP4 are at the corners. TVVP5, TVVP6, TVVP7, and TVVP8 are at the midpoints of the edges. TVVP9 is at the center. The distance between adjacent TVVPs along the edges is labeled as 0.5λ. Two 'Stirrer' units, represented by crossed rectangles, are shown outside the test volume, one above and one to the right, indicating their placement for field stirring.](f5a43bbc3d3642eb257baf1b10602488_img.jpg)
+
+Schematics of the test volume and baseline TVVPs for Type 2 RC. The diagram shows a rectangular 'Test Volume' containing nine Test Volume Reference Points (TVVPs). TVVP1, TVVP2, TVVP3, and TVVP4 are at the corners. TVVP5, TVVP6, TVVP7, and TVVP8 are at the midpoints of the edges. TVVP9 is at the center. The distance between adjacent TVVPs along the edges is labeled as 0.5λ. Two 'Stirrer' units, represented by crossed rectangles, are shown outside the test volume, one above and one to the right, indicating their placement for field stirring.
+
+Figure G.1.1.2-1: Schematics of the test volume and baseline TVVPs for Type 2 RC.
+
+### G.1.2 Test Volume Validation Procedure
+
+In each of the positions defined above, the procedure described in Clause C.3.2.5 of TR37.977 shall be used to obtain the test volume validation data. From this data it is possible to calculate the metrics of interest, as described below.
+
+#### G.1.2.1 Isotropy
+
+The procedure described in Annex C.3.2.5 shall be used to evaluate the isotropy in each TVVP.
+
+#### G.1.2.2 Chamber Statistical Ripple and Repeatability
+
+From the data obtained with the procedure above the chamber transfer function is calculated for each TVVP. The normalized standard deviation is then calculated as
+
+where
+
+M is the number of antenna positions used for the estimate, in this case 27 (9 TVVPs and 3 orientations in each TVVP).
+
+The total standard deviation is then given by
+
+where  $\delta$  is 1.05.
+
+The standard measurement uncertainty estimate is obtained by selecting the worst case for each band/channel combination. The value obtained should be inserted into the uncertainty budget in Annex B.5 as the “chamber statistical ripple and repeatability”.
+
+# --- Annex H: Change history
+
+| Change history |           |           |    |     |     |                                                                                                                                                                                             |             |
+|----------------|-----------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
+| Date           | Meeting   | TDoc      | CR | Rev | Cat | Subject/Comment                                                                                                                                                                             | New version |
+| 2012-03        | R4#62bis  | R4-121734 |    |     |     | Blank report: initial content to be incorporated from TR 37.976 v1.8.0                                                                                                                      | 0.0.1       |
+| 2012-03        | R4#62bis  | R4-122118 |    |     |     | Updated TR incorporating agreed text proposals R4-122096, R4-122097, and R4-122099.                                                                                                         | 0.1.0       |
+| 2012-05        | R4#64     | R4-124568 |    |     |     | Updated TR incorporating agreed text proposals: R4-123526 (proposed change to 6.4 is applied to Clause 8.3)<br>R4-123271.                                                                   | 0.2.0       |
+| 2012-11        | R4#65     | R4-126204 |    |     |     | Updated TR incorporating agreed text proposals: R4-125975<br>R4-125939                                                                                                                      | 0.3.0       |
+| 2013-01        | R4#66     | R4-130645 |    |     |     | Updated TR incorporating agreed text proposals: R4-126911<br>R4-126926                                                                                                                      | 0.4.0       |
+| 2013-02        | RAN #59   | RP-130342 |    |     |     | Presentation of TR 37.977 v0.4.0: Verification of radiated multi-antenna reception performance of User Equipment (UE)<br>Moved to Release 12                                                | 0.4.0       |
+| 2013-04        | R4 #66bis | R4-131665 |    |     |     | Updated TR incorporating agreed text proposals: R4-131672<br>R4-131673<br>R4-131674                                                                                                         | 0.5.0       |
+| 2013-05        | R4 #67    | R4-132685 |    |     |     | Updated TR incorporating agreed text proposals: R4-131993<br>R4-131211<br>Agreed text proposals from R4#66<br>R4-130881<br>R4-130710<br>R4-130742<br>R4-130751                              | 0.6.0       |
+| 2013-08        | R4 #68    | R4-133205 |    |     |     | Updated TR incorporating agreed text proposals: R4-133086<br>R4-133000<br>R4-133088<br>R4-133133<br>R4-132843<br>R4-132161<br>R4-132887                                                     | 0.7.0       |
+| 2013-09        | -         | -         |    |     |     | MCCclean-up                                                                                                                                                                                 | 0.7.1       |
+| 2013-09        | RP#61     | RP-131221 |    |     |     | Presented to RP#61 for information                                                                                                                                                          | 1.0.0       |
+| 2013-10        | R4 #68bis | R4-135392 |    |     |     | Updated TR incorporating agreed text proposals: R4-134445<br>R4-134502<br>R4-134435<br>R4-134233<br>R4-134429<br>R4-134501<br>R4-134511<br>R4-134497<br>R4-133208<br>R4-133297<br>R4-133288 | 1.1.0       |
+| 2013-11        | R4 #69    | R4-136755 |    |     |     | Updated TR incorporating agreed text proposals: R4-135719                                                                                                                                   | 1.2.0       |
+
+|  |  |  |  |  |  |                                                                                                                                                                       |  |
+|--|--|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+|  |  |  |  |  |  | R4-135720<br>R4-135738<br>R4-135725<br>R4-135466<br>R4-135736<br>R4-135735<br>R4-135749<br>R4-135733<br>R4-135722<br>R4-135734<br>R4-135368<br>R4-135566<br>R4-135766 |  |
+|--|--|--|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
+
+|         |        |           |      |   |   |                                                                                                                                                                                                                                               |        |
+|---------|--------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
+| 2013-11 | R4 #69 | R4-137114 |      |   |   | R4-136805<br>R4-136186<br>R4-136859<br>R4-137060<br>R4-137111<br>R4-136765<br>R4-137063<br>R4-137136                                                                                                                                          | 1.3.0  |
+| 2013-12 | RP#62  | RP-131819 |      |   |   | Presented to RP#62 for approval                                                                                                                                                                                                               | 2.0.0  |
+| 2013-12 | -      | -         |      |   |   | TR approved by RAN                                                                                                                                                                                                                            | 12.0.0 |
+| 03-2014 | RP-63  | RP-140376 | 001  | 1 |   | Clarifications to Single Cluster Channel Model in TR 37.977 Clause 6                                                                                                                                                                          | 12.1.0 |
+| 03-2014 | RP-63  | RP-140376 | 002  |   |   | Significant Figures for AoAs and AoDs for UMa-based Channel Models in TR 37.977                                                                                                                                                               | 12.1.0 |
+| 03-2014 | RP-63  | RP-140376 | 004  |   |   | Clarifications to Channel Model Validation in TR 37.977 Clause 8                                                                                                                                                                              | 12.1.0 |
+| 07-2015 | RP-68  | RP-150966 | 011  |   |   | Change of TDD eNodeB emulator settings for MIMO OTA test                                                                                                                                                                                      | 13.0.0 |
+| 07-2015 | RP-68  | RP-150966 | 012  | 1 |   | Addition of the ATF to the two-stage method description                                                                                                                                                                                       | 13.0.0 |
+| 07-2015 | RP-68  | RP-150966 | 015  |   |   | Addition of the ATF to the two-stage method description                                                                                                                                                                                       | 13.0.0 |
+| 09-2015 | RP-69  | RP-151493 | 0016 | 1 |   | CR to 37.977 on harmonization outcome                                                                                                                                                                                                         | 13.1.0 |
+| 09-2015 | RP-69  | RP-151493 | 0019 | - |   | Addition of SIR Control for MIMO OTA test methods                                                                                                                                                                                             | 13.1.0 |
+| 12-2015 | RP-70  | RP-152145 | 0023 | 1 |   | CR to 37.977 on harmonization test campaign                                                                                                                                                                                                   | 13.2.0 |
+| 12-2015 | RP-70  | RP-152145 | 0025 |   |   | CR to 37.977 to clarify BS antenna assumptions for channel model validation                                                                                                                                                                   | 13.2.0 |
+| 12-2015 | RP-70  | RP-152145 | 0026 |   |   | CR to TR37.977: Measurement uncertainty budget for AC and RC Methodologies. This CR replaces Table B.1-1, Table B.2-1 and Table B.3-1 with new tables. However the deletion of tables B.1-1, B.2-1 and B.3-1 is not shown with track changes. | 13.2.0 |
+| 03/2016 | RP-71  | RP-160471 | 0028 |   | F | CR to TR37.977: Further updates to channel model validation procedures for the RC and RC+CE methodologies                                                                                                                                     | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0030 |   | F | CR for Definition of Fading Channel Emulator Output Uncertainty Term                                                                                                                                                                          | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0031 |   | F | CR for SIR Related Uncertainty Terms                                                                                                                                                                                                          | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0032 |   | F | Update of channel model validation results for RTS                                                                                                                                                                                            | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0033 |   | F | Update of terminology                                                                                                                                                                                                                         | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0034 | 1 | F | CR for Definition of External Amplifiers Uncertainty Terms                                                                                                                                                                                    | 13.3.0 |
+| 03/2016 | RP-71  | RP-160471 | 0027 | 1 | B | CR to TR 37.977 on harmonization outcome                                                                                                                                                                                                      | 13.3.0 |
+| 06/2016 | RP-72  | RP-161142 | 0035 | 1 | F | CR to TR37.977: RC+CE Test Volume Validation                                                                                                                                                                                                  | 13.4.0 |
+| 06/2016 | RP-72  | RP-161142 | 0037 | - | F | CR to TR37.977: RC+CE Validation Updates                                                                                                                                                                                                      | 13.4.0 |
+| 06/2016 | RP-72  | RP-161142 | 0036 | 2 | F | Definition of device positioning within the Multi Probe Anechoic Chamber test volume                                                                                                                                                          | 14.0.0 |
+| 09/2016 | RP-73  | RP-161635 | 0038 | 1 | F | CR to TR37.977: Clarification to the Rayleigh Validation                                                                                                                                                                                      | 14.1.0 |
+| 12/2016 | RP-74  | RP-162389 | 0040 |   | F | Correction of DUT testing conditions                                                                                                                                                                                                          | 14.2.0 |
+| 12/2016 | RP-74  | RP-162436 | 0043 | 1 | F | CR to TR37.977: RC+CE Channel Model Validation Results                                                                                                                                                                                        | 14.2.0 |
+| 03/2017 | RP-75  | RP-170556 | 0046 | 2 | F | CR to TR 37.977 on lab alignment test plan                                                                                                                                                                                                    | 14.3.0 |
+| 03/2017 | RP-75  | RP-170602 | 0047 | - | F | CR to TR37.977: RC+CE Channel Model Validation Requirements                                                                                                                                                                                   | 14.3.0 |
+| 03/2017 | RP-75  | RP-170602 | 0048 | 2 | B | UMi Channel Model validation limits                                                                                                                                                                                                           | 14.3.0 |
+| 03/2017 | RP-75  | RP-170556 | 0049 | - | F | CR to 37.977 to add test zone size for RTS                                                                                                                                                                                                    | 14.3.0 |
+| 03/2017 | RP-75  | RP-170556 | 0050 | 2 | F | Correction of uplink power control setting                                                                                                                                                                                                    | 14.3.0 |
+| 06/2017 | RP-76  | RP-171258 | 0051 |   | F | CR on updating PADs list                                                                                                                                                                                                                      | 14.4.0 |
+| 06/2017 | RP-76  | RP-171258 | 0053 | 2 | F | CR to 37.977 Definition of RTS 2nd stage isolation                                                                                                                                                                                            | 14.4.0 |
+| 06/2017 | RP-76  | RP-171298 | 0054 | 1 | B | CR to 37.977 to define RTS channel model validation limits                                                                                                                                                                                    | 14.4.0 |
+| 06/2017 | RP-76  | RP-171258 | 0056 | 1 | F | CR on Channel model validation procedures for RTS                                                                                                                                                                                             | 14.4.0 |
+| 06/2017 | RP-76  | RP-171258 | 0057 |   | F | CR on harmonization outcome                                                                                                                                                                                                                   | 14.4.0 |
+
+|         |        |           |      |   |   |                                          |        |
+|---------|--------|-----------|------|---|---|------------------------------------------|--------|
+| 06/2017 | RP-76  | RP-171258 | 0058 | 3 | F | RTS applicability for > 2 Rx             | 14.4.0 |
+| 06/2017 | RP-76  | RP-171258 | 0059 |   | F | CR on Theoretical V/H Limits             | 14.4.0 |
+| 06/2017 | RP-76  | RP-171258 | 0060 | 3 | B | CR on Channel Model Validation           | 14.4.0 |
+| 09/2017 | RP-77  | RP-171931 | 0061 | 1 | B | CR on Channel Model Validation Results   | 14.5.0 |
+| 09/2017 | RP-77  | RP-171931 | 0062 | 2 | B | CR on MIMO OTA Measurement Procedures    | 14.5.0 |
+| 09/2017 | RP-77  | RP-171931 | 0063 |   | B | Noise Floor Measurement Procedure        | 14.5.0 |
+| 2018-06 | RAN#80 | RP-181115 | 0067 | 2 | F | Addition of RTS L3 ATF reporting and TDD | 14.6.0 |
+| 2018-09 | RAN#81 |           |      |   |   | Update to Rel-15 version (MCC)           | 15.0.0 |
+| 2020-06 | RAN#88 | -         | -    | - | - | Update to Rel-16 version (MCC)           | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/37_series/37985/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/37_series/37985/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..029765cafd834c1010eb410a63cbb48d8bd76693
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4d93468e7cba067400810f95266a06938bf93b434eaa5400d39dbb8d46e992b8
+size 16985
diff --git a/marked/Rel-16/37_series/37985/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/37_series/37985/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df50cd1356c49cd1649b8d8d63ed1261948a9458
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/1a827b10290f33d4fec04d0e8ef7a897_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d13cd1d3040a017d3e7d556bfcdffcb28bd101947c0b0aded9af855b4e17b259
+size 65223
diff --git a/marked/Rel-16/37_series/37985/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/37_series/37985/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4fb86aff89c98bd5fd8878cfe5ea6ce819cd8cb9
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:815682073198b23ecae3403b649549054cbc8072f635553ca805350901cea421
+size 23414
diff --git a/marked/Rel-16/37_series/37985/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/37_series/37985/28d75f39a24203712ee907b32cf0bbe5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..93275a9e766d293bdf2a98ac15b0d7e954607c28
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/28d75f39a24203712ee907b32cf0bbe5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:386fea8012d1e31e34726fe27fe12304eeb3e5b943f43e859886c89de82c223f
+size 23317
diff --git a/marked/Rel-16/37_series/37985/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/37_series/37985/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9b222108c690f194b1a3055c6846868a70af952f
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3f8e9bd3d4f3af81d4926a1fc2b7b5d6096fe6734acef4cab73fad0f46d236e
+size 64881
diff --git a/marked/Rel-16/37_series/37985/2e399449b7f62d40167a65ca88888917_img.jpg b/marked/Rel-16/37_series/37985/2e399449b7f62d40167a65ca88888917_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da255dae2b4ce73e7f9a69cb00fdb8e8aa1f34d1
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/2e399449b7f62d40167a65ca88888917_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44bb4f8cc342c3494dc94ece731c8b0e0c180c0f775220538e477483a8958a35
+size 44828
diff --git a/marked/Rel-16/37_series/37985/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/37_series/37985/5fb340ad68b0c71df0b56698b137e35b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec70d29dc03e3afd868e000b210048581b17cc8e
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/5fb340ad68b0c71df0b56698b137e35b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e296527d3660acd0472d2aa446dfa20a2b6a0a051150e3fa8f6151546eeebec2
+size 9995
diff --git a/marked/Rel-16/37_series/37985/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/37_series/37985/64662465bba247703fdec49c8f3309f9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7927f61b1239d261225220b410e3ffed88c5ef0b
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/64662465bba247703fdec49c8f3309f9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf1b852352c70ae4b6507e4a2cd8bd48142366a142f3f00a430c18206dfedd57
+size 5817
diff --git a/marked/Rel-16/37_series/37985/6f659142d4789aa889184459f884787e_img.jpg b/marked/Rel-16/37_series/37985/6f659142d4789aa889184459f884787e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40a9e96b4ceda0e9c395737de27bc74f9e310605
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/6f659142d4789aa889184459f884787e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae59fec81698d3b4715aec1850c846103e2d4344dcf591eb1f26920f1b395143
+size 21177
diff --git a/marked/Rel-16/37_series/37985/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/37_series/37985/75e4b78ee25f885d73120e3066a5253e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0dd987f9acb249cc6bfa453db5f043690df46378
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/75e4b78ee25f885d73120e3066a5253e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:60ab90d1cc16d99effbae3739c96744762e2b1934ba9a5acaa94d8d48fa822a9
+size 23598
diff --git a/marked/Rel-16/37_series/37985/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-16/37_series/37985/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..acfbc4d1ee007ba0f34a7c00574541dc0ef115aa
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa14f697e372ca150aea0cfaa41b74574f4f6f22e3c931c92310e89d44d59f36
+size 26077
diff --git a/marked/Rel-16/37_series/37985/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/marked/Rel-16/37_series/37985/7ede87328f6b696dcffa65ebc4570cc8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4702760c53099935046fda5e52fb52e5d8b7a39b
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/7ede87328f6b696dcffa65ebc4570cc8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b403e7dc93793c6be8c97ab8f7abae343c69d7103d23b11e210b239aaa361aed
+size 24991
diff --git a/marked/Rel-16/37_series/37985/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/Rel-16/37_series/37985/80ec3bf791fd8eb41f73a420c2122529_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e70daf625f15d7574b4bb03abd0b1a8b112f0a91
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/80ec3bf791fd8eb41f73a420c2122529_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab67d8479c4818428b60fc73166a98db4a4ccd3dee912537714481e7bf700aa8
+size 12932
diff --git a/marked/Rel-16/37_series/37985/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/37_series/37985/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e944175f19a09331b63db96bce28f9e22f4fa12
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:08f6250eadb8a9cd02b72e563f4e1634f8da413507664b8b631e0518618bd8e0
+size 28471
diff --git a/marked/Rel-16/37_series/37985/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/marked/Rel-16/37_series/37985/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..15bd8ef9f2733b2661df3bf4049ff0c31512f0b4
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/9b9d2abd741ed4bafe7f78f89961c663_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2e257f204a55dd0cbdbcac9499f13243adf834a0d743ec7681f6b08322897c32
+size 22847
diff --git a/marked/Rel-16/37_series/37985/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/37_series/37985/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bd892a84133aaa46d81b0a71149696f479948eb7
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:abca1daa8b6e7dd7878ab0a94ba8f94440f8d51917128b3a084e715a75047233
+size 21957
diff --git a/marked/Rel-16/37_series/37985/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/37_series/37985/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6df6d800c6b95c063406312e579fe6e22215e0e
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bf26854062f5153bc5277dea9c7022fa541e8e27f98568405dd20485cb931f6a
+size 49393
diff --git a/marked/Rel-16/37_series/37985/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/37_series/37985/b2ea162a0f53d5e0504b7d28346e0754_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d7b3f87d5241a4ad12c0eb77b7e66f9356709495
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/b2ea162a0f53d5e0504b7d28346e0754_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:743055727f9a9bed397c82daf682d6b232c2c1f5750fb4158299072ffacaa18b
+size 51840
diff --git a/marked/Rel-16/37_series/37985/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/37_series/37985/b5335262987c819d7f71ce40f99cb71b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4f4151019d992cf7aabe969c55ba5adb254a3270
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/b5335262987c819d7f71ce40f99cb71b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1d85e6589eb86ef709b5cfd4c30e5335e87a29777e0df0672e7b7aff6d0d40c4
+size 14857
diff --git a/marked/Rel-16/37_series/37985/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/37_series/37985/b904ac2472cab80892d1e783e6230d6e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..247065f7005267887bfe40ff03e9c17a7439f324
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/b904ac2472cab80892d1e783e6230d6e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ab7b3788bfdf0f1738c0cee5b3dee43b55e4634c2d9d8ec0d4722223fdfcbeac
+size 17986
diff --git a/marked/Rel-16/37_series/37985/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg b/marked/Rel-16/37_series/37985/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c861f9a6d402145e4cd4e74d071d984780c5545
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/cb4cfa42ce34febde7bdb882f3fc3094_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce0077d069b8193858982c3cec00830d5b941eaed4b1d9d64535da8aa3b052d5
+size 43983
diff --git a/marked/Rel-16/37_series/37985/d6a5f8423065d7cef55e11a0007014d9_img.jpg b/marked/Rel-16/37_series/37985/d6a5f8423065d7cef55e11a0007014d9_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42f7ef202db7901773806232b75837a257e9cd2f
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/d6a5f8423065d7cef55e11a0007014d9_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1a3a4e27b360adcf76c3f2b5fca4bc3e39bfee2979613df5840a90ebd3ca0b44
+size 30388
diff --git a/marked/Rel-16/37_series/37985/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-16/37_series/37985/dfaa8b98082261913dac00eae86b2889_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab64e88b1d9c7223a1ca07aa3a139cee981adb89
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/dfaa8b98082261913dac00eae86b2889_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3c45ed99ba1b670aee93f300e68ca728253b760dbdcf360ae97e624834e9f4c1
+size 18147
diff --git a/marked/Rel-16/37_series/37985/e1476fd216f6cf773e262013fb4aba7d_img.jpg b/marked/Rel-16/37_series/37985/e1476fd216f6cf773e262013fb4aba7d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..67d48ab13e29900a2eec88ccad305d63e3b77be9
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/e1476fd216f6cf773e262013fb4aba7d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8ce210b960bb5c547c1d7e8eb2599ec1d5bd4a55ef43832d92238a0ba017232
+size 14775
diff --git a/marked/Rel-16/37_series/37985/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-16/37_series/37985/e9b43ac020435f8121e8592f31afdc52_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6babf41b8840faf43c6edee5a9db372d78cdf155
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/e9b43ac020435f8121e8592f31afdc52_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:923cb930ac855ee4a29b00b505796585b1dcd0e652d7576bd5d058ec2cb1cf92
+size 20310
diff --git a/marked/Rel-16/37_series/37985/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/37_series/37985/f0a97d0d3818a253c1d2a009966081b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b6f97a44254f96038b617621d5f27fd4952f741a
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/f0a97d0d3818a253c1d2a009966081b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:22cc4f414b44b19d13b7dc6bf437e3013cd7c9512a18036474ccdeed3d74f1ad
+size 24539
diff --git a/marked/Rel-16/37_series/37985/raw.md b/marked/Rel-16/37_series/37985/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8dbee9eb6318a8aa6dffcfc48289b3464a4a34c6
--- /dev/null
+++ b/marked/Rel-16/37_series/37985/raw.md
@@ -0,0 +1,1102 @@
+
+
+# 3GPP TR 37.985 V16.1.0 (2022-03)
+
+*Technical Report*
+
+## **3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR (Release 16)**
+
+![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg)
+
+The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves.
+
+5G logo
+
+![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg)
+
+The 3GPP logo, featuring the text "3GPP" in a bold, black, stylized font. Below the "P" is a red signal icon consisting of three curved lines. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font.
+
+3GPP logo
+
+The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices.
+
+## **3GPP**
+
+---
+
+Postal address
+
+---
+
+3GPP support office address
+
+---
+
+650 Route des Lucioles - Sophia Antipolis  
+Valbonne - FRANCE  
+Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
+
+---
+
+Internet
+
+---
+
+<http://www.3gpp.org>
+
+## --- **Copyright Notification** ---
+
+No part may be reproduced except as authorized by written permission.  
+The copyright and the foregoing restriction extend to reproduction in all media.
+
+© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).  
+All rights reserved.
+
+UMTS™ is a Trade Mark of ETSI registered for the benefit of its members  
+3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners  
+GSM® and the GSM logo are registered and owned by the GSM Association
+
+# Contents
+
+|                                                                           |    |
+|---------------------------------------------------------------------------|----|
+| Foreword .....                                                            | 5  |
+| Introduction .....                                                        | 6  |
+| 1 Scope.....                                                              | 7  |
+| 2 References.....                                                         | 7  |
+| 3 Definitions of terms, symbols and abbreviations .....                   | 8  |
+| 3.1 Terms.....                                                            | 8  |
+| 3.2 Symbols.....                                                          | 8  |
+| 3.3 Abbreviations .....                                                   | 8  |
+| 4 Services and requirements .....                                         | 9  |
+| 5 LTE V2X.....                                                            | 10 |
+| 5.1 V2X sidelink physical layer.....                                      | 10 |
+| 5.1.1 Physical sidelink channels and signals .....                        | 10 |
+| 5.1.2 Sidelink synchronization .....                                      | 11 |
+| 5.1.3 Concurrent operation and carrier aggregation .....                  | 12 |
+| 5.2 V2X sidelink resource allocation .....                                | 13 |
+| 5.2.1 Resource pools.....                                                 | 13 |
+| 5.2.2 Resource allocation modes .....                                     | 14 |
+| 5.3 Sidelink congestion control.....                                      | 17 |
+| 5.4 V2X sidelink higher-layer protocols .....                             | 17 |
+| 5.4.1 General .....                                                       | 17 |
+| 5.4.2 Resource pool configuration.....                                    | 18 |
+| 5.4.3 Measurement and reporting .....                                     | 18 |
+| 5.4.4 Mobility management.....                                            | 18 |
+| 5.4.5 Assistance information for SL SPS configuration.....                | 18 |
+| 5.4.6 Transmission carrier selection.....                                 | 18 |
+| 5.4.7 SL packet duplication .....                                         | 18 |
+| 5.4.8 Coordination between UL and V2X SL transmission.....                | 19 |
+| 5.4.9 Multi-PLMN operation.....                                           | 19 |
+| 5.5 V2X via the Uu interface .....                                        | 19 |
+| 5.6 Network aspects .....                                                 | 19 |
+| 5.6.1 V2X service authorization.....                                      | 19 |
+| 5.6.2 Sidelink AMBR .....                                                 | 19 |
+| 6 NR V2X .....                                                            | 20 |
+| 6.1 Sidelink unicast, groupcast, and broadcast.....                       | 20 |
+| 6.2 V2X sidelink physical layer.....                                      | 20 |
+| 6.2.1 Physical sidelink channels and signals .....                        | 20 |
+| 6.2.2 Sidelink synchronization .....                                      | 21 |
+| 6.2.3 Sidelink CSI.....                                                   | 23 |
+| 6.2.4 Sidelink HARQ .....                                                 | 23 |
+| 6.2.5 In-device coexistence between LTE-V2X and NR-V2X sidelinks .....    | 23 |
+| 6.2.6 Concurrent operation .....                                          | 24 |
+| 6.3 V2X sidelink resource allocation .....                                | 24 |
+| 6.3.1 Sidelink bandwidth parts and resource pools .....                   | 24 |
+| 6.4 Sidelink congestion control.....                                      | 28 |
+| 6.5 V2X sidelink higher-layer protocols .....                             | 28 |
+| 6.5.1 General .....                                                       | 28 |
+| 6.5.2 Measurement and reporting related to NR sidelink communication..... | 29 |
+| 6.5.3 Mobility management for NR SL transmission/reception.....           | 30 |
+| 6.5.4 Assistance information and SL configured grant configuration.....   | 30 |
+| 6.5.5 Coordination between UL and NR SL transmission .....                | 30 |
+| 6.5.6 QoS mechanism.....                                                  | 30 |
+| 6.5.7 Sidelink RRC .....                                                  | 30 |
+| 6.6 V2X via the Uu interface .....                                        | 31 |
+
+- 6.7 Network aspects ..... 31
+  - 6.7.1 V2X service authorization..... 31
+  - 6.7.2 Alternative QoS Profiles..... 31
+- 7 Multi-RAT V2X..... 31
+  - 7.1 Cross-RAT operation ..... 31
+  - 7.2 MR-DC..... 32
+- 8 Transmission profiles..... 34
+- 9 Pedestrian UE..... 34
+- 10 Roadside unit..... 35
+
+# Foreword
+
+This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+In the present document, certain modal verbs have the following meanings:
+
+**shall** indicates a mandatory requirement to do something
+
+**shall not** indicates an interdiction (prohibition) to do something
+
+NOTE 1: The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports.
+
+NOTE 2: The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document.
+
+**should** indicates a recommendation to do something
+
+**should not** indicates a recommendation not to do something
+
+**may** indicates permission to do something
+
+**need not** indicates permission not to do something
+
+NOTE 3: The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended.
+
+**can** indicates that something is possible
+
+**cannot** indicates that something is impossible
+
+NOTE 4: The constructions "can" and "cannot" shall not to be used as substitutes for "may" and "need not".
+
+**will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+**will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document
+
+**might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document
+
+In addition:
+
+**is** (or any other verb in the indicative mood) indicates a statement of fact
+
+**is not** (or any other negative verb in the indicative mood) indicates a statement of fact
+
+NOTE 5: The constructions "is" and "is not" do not indicate requirements.
+
+# --- Introduction
+
+The 3GPP platform was first expanded to the automotive industry by the introduction of support for V2V and V2X services in Release 14. This support forms Phase 1 of 3GPP's ongoing project relating to V2X, and was intended to support a set of requirements sufficient for basic road safety services. Vehicles containing UEs with these features can use the uplink, downlink and sidelink to exchange information on their own status, such as position, speed, and heading with other nearby vehicles, infrastructure nodes, and pedestrians. Phase 2 of the V2X project was standardised in Release 15, and adds a number of new features to the sidelink intended to enhance efficiency and exploit developments in UE and network designs. These enhancements include sidelink carrier aggregation, higher-order modulation, and reduced latency.
+
+Phase 3 of V2X, in Release 16, adds support to NR (and also 5GC, not addressed in this TR) for advanced V2X use cases, and includes introduction of the NR sidelink. The use-cases are broadly grouped to enable vehicular platooning, exchange of extended sensor information, advanced driving, and remote driving. Phase 3 also allows either RAT's sidelink to be operated under control of the other RAT's Uu interface, as well as permitting connection to EPC or 5GC, to enable usage in the main MR-DC deployment scenarios.
+
+In the following clauses, LTE-V2X is described first, then NR-V2X, and finally certain aspects which have a degree of commonality to both RATs.
+
+Although this TR deals with RAN aspects, note that the core network architectures also have many adaptations to support V2X in both EPC and 5GC. These are referred to only as needed for other explanations in this TR, and details can be found in the relevant specifications.
+
+# --- 1 Scope
+
+The present document provides an overall description of the features introduced by 3GPP to LTE and NR in support of V2X services, starting from Rel-14. The purpose of this TR is to give an overview across the RAN specifications of how the features have been designed, and how they operate together. This document addresses LTE V2X and NR V2X via both sidelink, i.e. the PC5 interfaces, and via the cellular uplink/downlink, i.e. the Uu interfaces. It covers V2V, V2I/N, and V2P, as well as the eNB/gNB, UE, and RSU nodes. The intention is to provide descriptions at approximately the Stage 2 level of detail, and thus references are provided to RAN specifications for the reader to obtain precise details.
+
+The document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [2] 3GPP TR 36.885: "Study on LTE-based V2X Services".
+- [3] ETSI EN 302 637-2: "Specification of Cooperative Awareness Basic Service".
+- [4] SAE J2735: "Dedicated Short Range Communications (DSRC) Message Set Dictionary".
+- [5] ETSI EN 302 637-3 "Specifications of Decentralized Environmental Notification Basic Service".
+- [6] 3GPP TS 22.185: "Service requirements for V2X services".
+- [7] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
+- [8] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation".
+- [9] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding".
+- [10] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC)".
+- [11] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
+- [12] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Measurements".
+- [13] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
+- [14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC)".
+- [15] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP)".
+
+- [16] 3GPP TS 38.211: "NR; Physical channels and modulation".
+- [17] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
+- [18] 3GPP TS 38.213: "NR; Physical layer procedures for control".
+- [19] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2".
+- [20] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
+- [21] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
+- [22] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone".
+
+# --- 3 Definitions of terms, symbols and abbreviations
+
+## 3.1 Terms
+
+For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
+
+**example:** text used to clarify abstract rules by applying them literally.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|          |               |
+|----------|---------------|
+| <symbol> | <Explanation> |
+|----------|---------------|
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
+
+Where the same abbreviation is used for LTE V2X and NR V2X, which is meant can be derived from the clause within which it appears, unless otherwise stated.
+
+|       |                                                  |
+|-------|--------------------------------------------------|
+| 5GC   | Fifth Generation core network                    |
+| AGC   | Automatic gain control                           |
+| AMBR  | Aggregate maximum bit rate                       |
+| BSM   | Basic safety message                             |
+| BWP   | Bandwidth part                                   |
+| CA    | Carrier aggregation                              |
+| CAM   | Cooperative awareness message                    |
+| CBR   | Channel busy ratio                               |
+| CR    | Channel usage ratio                              |
+| DENM  | Decentralized environmental notification message |
+| DMRS  | Demodulation reference signal                    |
+| EPC   | Evolved packet core                              |
+| MBSFN | Multicast-broadcast single-frequency network     |
+| MNO   | Mobile network operator                          |
+| PPPP  | ProSe per-packet priority                        |
+| PPPR  | ProSe per-packet reliability                     |
+| PSBCH | Physical sidelink broadcast channel              |
+| PSCCH | Physical sidelink control channel                |
+| PSSCH | Physical sidelink shared channel                 |
+
+|             |                                                                                                 |
+|-------------|-------------------------------------------------------------------------------------------------|
+| PSSS, S-PSS | Primary sidelink synchronization signal (LTE), sidelink primary synchronization signal (NR)     |
+| PT-RS       | Phase-tracking reference signal                                                                 |
+| P-UE        | Pedestrian UE                                                                                   |
+| RSU         | Roadside unit                                                                                   |
+| SA          | Scheduling assignment                                                                           |
+| SCI         | Sidelink control information                                                                    |
+| SC-PTM      | Single-cell point-to-multipoint                                                                 |
+| SL-BCH      | Sidelink broadcast channel                                                                      |
+| SLSS        | Sidelink synchronization signal                                                                 |
+| S-RSSI      | Sidelink received signal strength indicator                                                     |
+| S-SSB       | Sidelink synchronization signal block                                                           |
+| SSSS, S-SSS | Secondary sidelink synchronization signal (LTE), sidelink secondary synchronization signal (NR) |
+| V2I         | Vehicle-to-infrastructure                                                                       |
+| V2P         | Vehicle-to-pedestrian                                                                           |
+| V2V         | Vehicle-to-vehicle                                                                              |
+| V2X         | Vehicle-to-everything                                                                           |
+
+# 4 Services and requirements
+
+LTE-V2X is designed with BSM, CAM, and DENM particularly in mind. BSMs and CAMs have the characteristic of generating periodic messages at intervals, whereas DENMs are event-triggered. As an illustration of the different message types, in TR 36.885 [2], BSM/CAM were modelled, for evaluation purposes, as periodically occurring sets of one 300-byte message followed by four 190-byte messages. These types of message regularly broadcast information such as the vehicle's heading, speed, latitude/longitude, etc. ETSI EN 302 637-2 [3], SAE J2735 [4]. In TR 36.885 [2], DENMs were modelled, for evaluation purposes, as Poisson distributed initiations of six 800-byte messages spaced by 100 ms. DENMs can contain various different messages depending on the cause for their transmission, such as imminent collision, sudden braking, or detection of a traffic jam, amongst others ETSI EN 302 637-3 [5]. The requirements relating to traffic size and pattern for LTE-V2X set in TS 22.185 [6] can be summarized as follows, although they do not limit the usage of LTE-V2X. Other requirements relating to general system function are also included in TS 22.185 [6].
+
+- Support for periodic broadcast messages with payloads of 50-300 bytes.
+- Support for event-triggered messages with payloads of up to 1200 bytes.
+- Up to 10 messages per second transmitted by a UE.
+- V2V and V2P latency of maximum 100 ms, or for V2V pre-crash sensing, maximum 20 ms.
+- V2I latency, i.e. between a UE and RSU, of maximum 100 ms.
+- V2N latency, i.e. when transferring messages via the cellular network, of maximum 1000 ms.
+- Maximum relative velocity between two vehicles of 500 km/h, and maximum absolute velocity of 250 km/h for V2V and V2P UEs, and of a UE communicating with an RSU.
+- Requirements relating to security, integrity, authorization, and privacy.
+
+NR V2X is designed with a broader set of more advanced V2X use cases in mind. These were specified in TS 22.18 [7], and are broadly arranged into four use case groups: vehicular platooning, extended sensors, advanced driving, and remote driving.
+
+- 1) Vehicles Platooning enables the vehicles to dynamically form a platoon travelling together. All the vehicles in the platoon obtain information from the leading vehicle to manage this platoon. These information allow the vehicles to drive closer than normal in a coordinated manner, going to the same direction and travelling together.
+- 2) Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video images among vehicles, road site units, devices of pedestrian and V2X application servers. The vehicles can increase the perception of their environment beyond of what their own sensors can detect and have a more broad and holistic view of the local situation. High data rate is one of the key characteristics.
+
+- 3) Advanced Driving enables semi-automated or full-automated driving. Each vehicle and/or RSU shares its own perception data obtained from its local sensors with vehicles in proximity and that allows vehicles to synchronize and coordinate their trajectories or manoeuvres. Each vehicle shares its driving intention with vehicles in proximity too.
+- 4) Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive by themselves or remote vehicles located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. High reliability and low latency are the main requirements.
+
+The most demanding requirements set in TS 22.186 [7] are for a maximum sidelink range of 1000 m, a maximum throughput of 1 Gbps, a shortest latency of 3 ms, a maximum reliability of 99.999%, and a maximum transmission rate of 100 messages/second. However, there is not a use case which, on its own, demands all of these bounding requirements. The communication scenarios described in TS 22.186 [7] include a mixture of periodic and aperiodic services. Similar to LTE-V2X, there are also requirements relating to security, integrity, authorization, and privacy.
+
+# --- 5 LTE V2X
+
+## 5.1 V2X sidelink physical layer
+
+The LTE V2X sidelink supports broadcast transmission of messages in the physical layer, since this is a suitable approach for delivery BSM, CAM, DENM and similar traffic. In the MAC layer, a broadcast address can be mapped to a single UE or a group of UEs by implementation. Such implementation techniques have no particular specification support in LTE, and are transparent to the physical layer.
+
+### 5.1.1 Physical sidelink channels and signals
+
+The LTE V2X sidelink uses the following physical channels and signals:
+
+- Physical sidelink broadcast channel (PSBCH), specified in TS 36.211 [8, clause 9.6]
+- Physical sidelink control channel (PSCCH), specified in TS 36.211 [8, clause 9.4]
+- Physical sidelink shared channel (PSSCH), specified in TS 36.211 [8, clause 9.3]
+- Primary and secondary sidelink synchronization signals (PSSS and SSSS) specified in TS 36.211 [8, clause 9.7]. These can be referred to jointly as the sidelink synchronization signal (SLSS).
+- A demodulation reference signal (DMRS) associated with each of the three physical channels, specified in TS 36.211 [8, clause 9.8]
+
+LTE-V2X sidelink physical channels are transmitted using SC-FDMA.
+
+PSBCH transmits the SL-BCH transport channel, which carries the sidelink V2X Master Information Block (MIB-V2X) from the RRC layer. When in use, PSBCH transmits MIB-V2X every 160 ms in the central 72 subcarriers of the SL bandwidth. DMRS associated with PSBCH are transmitted in the 5th, 7th, and 10th symbols of the subframe.
+
+PSSS and SSSS are transmitted to allow other UEs to achieve sidelink synchronization when they do not have another source of synchronization available. They jointly convey the SLSS ID selected by the UE. For further details of SLSS and synchronization, refer to Clause 5.1.2. PSSS/SSSS also allow UEs to detect the sidelink subframe boundary, with subframe number and frame number signalled in MIB-V2X.
+
+PSSCH transmits the SL-SCH transport channel, which carries the TBs of data for transmission over SL. The resources in which PSSCH is transmitted can either be scheduled by an eNB and granted to the UE by a DCI (termed resource allocation mode 3, see Clause 5.2.2.1) or determined through a sensing procedure conducted autonomously by the transmitting UE (termed resource allocation mode 4, see Clause 5.2.2.2). A given TB can be transmitted once or twice, with a second transmission occurring a time gap after the first which is indicated in the scheduling SCI.
+
+PSCCH transmits physical layer sidelink control information (SCI), also known as a scheduling assignment (SA). For V2X, PSCCH is transmitted in two frequency-adjacent PRBs, and always carries SCI format 1, defined in TS 36.212 [9, clause 5.4.3.1.2]. To receive PSCCH, a UE has to monitor each defined pair of PRBs to determine whether PSCCH has
+
+been transmitted in them. PSCCH is transmitted in the same subframe(s) as the associated PSSCH, and can be transmitted in PRBs that are either frequency adjacent or frequency non-adjacent to the PSSCH.
+
+DMRS associated with PSSCH and PSCCH are transmitted in the 3rd, 6th, 9th, and 12th symbols of a subframe.
+
+### 5.1.2 Sidelink synchronization
+
+#### 5.1.2.1 Synchronization references and priorities
+
+There are four basic sources, or references, from which a V2X UE can derive its own synchronization: GNSS, its serving eNB, another UE transmitting SLSS (a SyncRef UE), or its own internal clock. In general, GNSS or eNB are regarded as the highest-quality sources. SyncRef UEs are distinguished between those which are directly synchronized to GNSS or an eNB, those which are 1 further step away, and those which are  $\geq 2$  further steps away from GNSS/eNB. As a last resort, a UE unable to find any other synchronization reference will use its own internal clock to transmit SLSS. The V2X synchronization procedure defines a hierarchy or set of priorities among such synchronization references and requires all UEs to continuously search the hierarchy to get to the highest-quality one they can find. The general preference order is as follows, with details specified in TS 36.331 [10, clause 5.10.8]:
+
+- Level 1. Either GNSS or eNB, according to (pre-)configuration.
+- Level 2. A SyncRef UE directly synchronized to a Level 1 source.
+- Level 3. A SyncRef UE synchronized to a Level 2 source, i.e. indirectly synchronized to a Level 1 source.
+  - When the Level 1 preference is (pre-)configured as GNSS, in Level 2 and 3, SyncRef UEs in hierarchies derived from GNSS and eNB are of equal preference as a synchronization source.
+- Level 4. Any other SyncRef UE.
+- Level 5. UE's internal clock.
+
+Within a Level 2, or 3, or 4 set of SyncRef UEs, the one with the highest S-RSRP is selected. The hierarchy also allows fallback between eNB-derived and GNSS-derived chains should the Level 1 type chosen by (pre-)configuration be unsuitable.
+
+#### 5.1.2.2 SLSS
+
+The transmission and reception of SLSS (and PSBCH) is an optional V2X UE capability, and they can be transmitted on one or multiple synchronization carriers.
+
+A UE which is deriving its own synchronization from eNB or GNSS can be configured by the network to transmit SLSS on a synchronization carrier, or the network can permit it to do so if the RSRP of a reference cell falls below a threshold. If the network is not available, and the UE is synchronized to GNSS, it will transmit SLSS if permitted by its pre-configuration. When such a UE does not have GNSS synchronization, it will transmit SLSS, if permitted by its pre-configuration, while it cannot find a SyncRef UE with sufficiently high S-RSRP. Full details of the conditions for SLSS transmission are specified in TS 36.331 [10, clause 5.10.7.2].
+
+In a V2X system, there can be a variety of UEs which are deriving synchronization from different sources, and since a UE can transmit SLSS on multiple carriers, it can have different synchronization sources among them. SLSS is therefore transmitted in different subframes depending on what synchronization source the UE is using. The system can be configured with either two or three different offsets with respect to the start of the 160 ms PSBCH period can be defined, which can allow different subframes for transmission according to whether the UE is synchronized to GNSS, eNB, or another SyncRef UE.
+
+PSSS and SSSS use the same sequences as PSS and SSS, respectively, with different root indices. When in use, both sequences are transmitted in the central 62 subcarriers of the SL bandwidth, in the same subframe as PSBCH, i.e. every 160 ms. PSSS is in the 2nd and 3rd symbols of the subframe, and SSSS in the 12th and 13th symbols. The two symbols of each signal are the same, which allows detectors to benefit from phase tracking between the two symbols. Figure 5.1.2.1-1 shows the relevant contents of a subframe which contain PSBCH, PSSS, and SSSS.
+
+![Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe. The diagram shows a 1 ms subframe structure. It starts with a 6 RBs (Resource Block) wide PSBCH (Physical Sidelink Broadcast Channel) block, followed by two PSSS (Physical Sidelink Synchronization Signal) blocks. This is followed by a DMRS (Demodulation Reference Signal) block, then another PSBCH block, another DMRS block, another PSBCH block, another DMRS block, another PSBCH block, and finally two SSSS (Physical Sidelink Synchronization Signal) blocks. The subframe ends with a GUARD interval. The total duration is 1 ms, and the total number of subcarriers is 62.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe. The diagram shows a 1 ms subframe structure. It starts with a 6 RBs (Resource Block) wide PSBCH (Physical Sidelink Broadcast Channel) block, followed by two PSSS (Physical Sidelink Synchronization Signal) blocks. This is followed by a DMRS (Demodulation Reference Signal) block, then another PSBCH block, another DMRS block, another PSBCH block, another DMRS block, another PSBCH block, and finally two SSSS (Physical Sidelink Synchronization Signal) blocks. The subframe ends with a GUARD interval. The total duration is 1 ms, and the total number of subcarriers is 62.
+
+Figure 5.1.2.2-1: Contents of an LTE-V2X synchronization subframe.
+
+##### 5.1.2.2.1 SLSSID
+
+The SLSSID itself conveys information about the synchronization source of the transmitting UE. In general, the further a UE is away from a high-quality source of GNSS or eNB, the lower quality will be its own synchronization and thus the quality of an SLSS it transmits. There are a series of association rules among SLSS IDs, designed to allow the identification, and propagation through the system of, high-quality synchronization sources. Thus, for example, a UE which is in-coverage and directly synchronized to an eNB (a Level 2 SyncRef UE) uses an SLSSID which is configured by the network from 1-167, allowing SLSSID planning, and a UE using such a UE as a SyncRef UE (a Level 3 SyncRef UE) uses the same SLSSID, but indicates in V2X MIB that it is not directly eNB-synchronized. Subsequent UEs in this example hierarchy (Level 4 SyncRef UEs) use the SLSSID+168 to indicate their source is not directly synchronized to an eNB. A similar propagation hierarchy is used starting with a UE which is directly synchronized to GNSS, whose SLSSID is always 0, resulting in any UE which is more than one further step from GNSS using SLSSID 168 (or, in some cases, 169) so that a synchronization hierarchy based on GNSS can always be identified. Finally, a UE which cannot find GNSS, eNB, nor a SyncRef UE, selects an SLSSID randomly from 170-335, and UEs which synchronize to it propagate the same SLSSID.
+
+### 5.1.3 Concurrent operation and carrier aggregation
+
+V2X operation is defined in band 47 in TS 36.101 [11, clause 5.5G], which supports single-carrier and multi-carrier operation:
+
+Table 5.1.3-1: V2X operating band
+
+| E-UTRA Operating Band | E-UTRA V2X Operating Band | V2X UE transmit     |   | V2X UE receive       |                     | Duplex Mode | Interface |    |     |
+|-----------------------|---------------------------|---------------------|---|----------------------|---------------------|-------------|-----------|----|-----|
+|                       |                           | F <sub>UL_low</sub> | – | F <sub>UL_high</sub> | F <sub>DL_low</sub> |             |           |    |     |
+| 47                    | 47                        | 5855 MHz            | – | 5925 MHz             | 5855 MHz            | –           | 5925 MHz  | HD | PC5 |
+
+The V2X sidelink in band 47 can be operated concurrently with Uu FDD bands 3, 5, 7, 8, 20, 28, and Uu TDD bands 34, 39, 41, and 71.
+
+Sidelink CA is defined for resource allocation modes 3 and 4. When operating in CA, a given (sidelink) MAC PDU is transmitted, and if necessary re-transmitted, on a single sidelink carrier, and multiple MAC PDUs can be transmitted in parallel on different carriers. This provides a throughput gain in a similar way as for Uu CA.
+
+Sidelink CA in resource allocation mode 3 using a dynamic grant is similar to on the Uu interface, by including a carrier indication field (CIF) in the DCI from the eNB. This indicates which among the up to 8 configured sidelink carriers the allocation in the DCI applies to.
+
+Sidelink CA in resource allocation mode 4 uses the sensing procedure described in Clause 5.2.2.2 to select resources independently on each involved carrier. The same carrier is used for all MAC PDUs of the same sidelink process at least until the process triggers resource re-selection. Procedures to avoid unexpected UE behaviour when the demands of CA become high are also specified, which allow a UE to drop a transmission which uses an unmanageable amount of resources or transmit chains, or to reject and re-select resources for which it cannot meet the RF requirements under CA.
+
+Sidelink synchronization can also operate on multiple carriers, as mentioned in Clause 5.1.2. In addition, in sidelink CA operation, a SyncRef UE uses a single synchronization reference for all aggregated carriers, and may transmit SLSS/PSBCH on one or multiple of them according to capability. A receiving UE likewise uses the same
+
+synchronization reference (not necessarily a SyncRef UE) for all its aggregated carriers, and it uses the highest priority synchronization reference present among the available synchronization carriers.
+
+Another form of CA is PDCP duplication, where the same PDCP packet is transmitted in parallel on multiple sidelink carriers, to increase reliability. See Clause 5.4.7 for more discussion.
+
+## 5.2 V2X sidelink resource allocation
+
+### 5.2.1 Resource pools
+
+PSCCH and PSSCH resources are defined within resource pools for the respective channels. This concept is used because in general PSCCH/PSSCH cannot be transmitted (and thus are not expected to be received) in all PRBs and subframes in the system bandwidth, nor within a given frequency span configured for V2X sidelink. The notion of a resource pool also reflects, in resource allocation mode 4, that a UE will make its resource selections based on sensing within the (PSSCH) pool.
+
+For PSSCH, a resource pool is divided into sub-channels in the frequency domain, which are consecutively non-overlapping sets of  $\geq 4$  PRBs in a subframe, the size depending on (pre-)configuration. Resource allocation, sensing, and resource selection are performed in units of a sub-channel, although it is possible that a small number of PRBs within a sub-channel are not used for transmission.
+
+For PSCCH, the resource pool definition depends on whether adjacent or non-adjacent transmission of PSCCH and PSSCH has been (pre-)configured for the resource pool. Adjacent transmission is achieved by defining the lowest pair of PRBs in each subchannel as candidates to contain PSCCH, and PSSCH is transmitted in the contiguous PRBs above them for the allocated number of subchannels. Non-adjacent transmission is achieved by defining sequential pairs of PRBs starting at the lowest frequency of the resource pool for PSCCH, and associating the  $n^{\text{th}}$  pair to PSSCH transmission occupying from the  $n^{\text{th}}$  PSSCH sub-channel for the allocated number of subchannels. Figure 5.2.1-1 shows examples of adjacent and non-adjacent transmission. To receive PSCCH, a UE has to monitor each defined pair of PRBs to determine whether PSCCH has been transmitted in them.
+
+![Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) subframes. A vertical bracket on the left indicates 'One sub-channel'. Arrows point to specific cells labeled 'PSCCH candidate resources'. Four UEs are shown: UE1 (top), UE4 (middle), UE2 (bottom left), and UE1 (bottom right). Each UE's transmission consists of a green PSCCH block followed by a yellow PSSCH block in the same subframe. UE1's PSCCH is in the second column, followed by yellow blocks in columns 3-5. UE4's PSCCH is in the fourth column, followed by yellow blocks in columns 5-7. UE2's PSCCH is in the second column, followed by yellow blocks in columns 3-5. UE1's PSCCH is in the fourth column, followed by yellow blocks in columns 5-7.](2e399449b7f62d40167a65ca88888917_img.jpg)
+
+Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) subframes. A vertical bracket on the left indicates 'One sub-channel'. Arrows point to specific cells labeled 'PSCCH candidate resources'. Four UEs are shown: UE1 (top), UE4 (middle), UE2 (bottom left), and UE1 (bottom right). Each UE's transmission consists of a green PSCCH block followed by a yellow PSSCH block in the same subframe. UE1's PSCCH is in the second column, followed by yellow blocks in columns 3-5. UE4's PSCCH is in the fourth column, followed by yellow blocks in columns 5-7. UE2's PSCCH is in the second column, followed by yellow blocks in columns 3-5. UE1's PSCCH is in the fourth column, followed by yellow blocks in columns 5-7.
+
+Figure 5.2.1-1a: Illustration of adjacent allocations of PSCCH and associated PSSCH.
+
+![Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. A 'One sub-channel' bracket on the left indicates a single frequency unit. Below it, a 'PSCCH candidate resources' bracket indicates a set of time slots. The grid contains labels UE1, UE4, and UE2. Green blocks represent PSCCH transmissions, and yellow blocks represent PSSCH transmissions. Dashed arrows show the association between PSCCH and PSSCH. UE1 transmits PSCCH in the first time slot and PSSCH in the third. UE4 transmits PSCCH in the second time slot and PSSCH in the fourth. UE2 transmits PSCCH in the third time slot and PSSCH in the fifth. The non-adjacent nature is shown by the gap between the PSCCH and PSSCH blocks for each UE.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH. The diagram shows a grid of frequency (f) vs. time (t) resources. A 'One sub-channel' bracket on the left indicates a single frequency unit. Below it, a 'PSCCH candidate resources' bracket indicates a set of time slots. The grid contains labels UE1, UE4, and UE2. Green blocks represent PSCCH transmissions, and yellow blocks represent PSSCH transmissions. Dashed arrows show the association between PSCCH and PSSCH. UE1 transmits PSCCH in the first time slot and PSSCH in the third. UE4 transmits PSCCH in the second time slot and PSSCH in the fourth. UE2 transmits PSCCH in the third time slot and PSSCH in the fifth. The non-adjacent nature is shown by the gap between the PSCCH and PSSCH blocks for each UE.
+
+**Figure 5.2.1-1b: Illustration of non-adjacent allocations of PSCCH and associated PSSCH.**
+
+Resource pools are (pre-)configured to a UE separately from the transmission perspective (TX pools) and the reception perspective (RX pools). This allows a UE to monitor for PSCCH, and hence receive PSSCH transmissions, in resource pools other than those in which it transmits, so that it can attempt to receive transmissions made by other UEs in those RX pools.
+
+In addition, there are exceptional resource pools configured to a UE, in its serving cell's SIB21 or in dedicated signalling. These can be used e.g. during RLF, handover, transition from RRC IDLE to RRC CONNECTED, or during change of dedicated V2X sidelink resource pools within a cell. In these cases, a UE may not have a stable configuration of TX resource pools but nevertheless should not be removed from the V2X system, so it can randomly select resources in the exceptional pool provided in its serving cell's SIB21 or in dedicated signalling, and use them temporarily. Likewise, UEs need to monitor the exceptional pools for PSCCH transmissions.
+
+### 5.2.2 Resource allocation modes
+
+LTE sidelink defines four resource allocation modes: 1, 2, 3, and 4. Modes 1 and 2 apply to D2D, while modes 3 and 4 apply to LTE V2X.
+
+#### 5.2.2.1 Resource allocation mode 3
+
+Mode 3 is for resource allocation scheduled by eNB. As described in Clause 4, among the primary use cases for LTE-V2X is transmission of periodically-occurring messages, and for this reason there is particular support for sidelink SPS. However, dynamic sidelink grants are equally supported.
+
+The eNB scheduling activity is driven by the UE needing to send data on sidelink performing a sidelink BSR procedure similar to that on Uu to request a sidelink resource allocation from eNB. Depending on the type of traffic the UE has, eNB can provide a dynamic sidelink grant, or an activation of a SPS sidelink grant.
+
+A dynamic sidelink grant DCI provides, amongst other details TS 36.212 [9, clause 5.3.3.1.9A], the resources for up to two transmissions of the same TB. This is to allow higher reliability to be achieved without a feedback-based HARQ procedure, since LTE-V2X physical layer supports only broadcast transmission. Unlike Uu UL grants, the MCS information can optionally be provided by RRC signalling instead of the traditional DCI. For the case where RRC does not provide the MCS, the transmitting UE is left to select an appropriate MCS/TBS itself based on the knowledge it has of the TB to be transmitted and, potentially, the sidelink radio conditions. The transmitting UE populates its SCI with the information from eNB and other fields related to sidelink operation TS 36.212 [9, clause 5.4.3.1.2], and then transmits it and the associated PSSCH.
+
+The UE can be configured by eNB with up to 8 sidelink SPS configurations. Each configuration has an identifying index, and provides a different periodicity of sidelink transmission resource. A sidelink SPS configuration is not used by the UE until the eNB sends the UE a DCI which indicates it is now active. The activating DCI also provides all the
+
+same fields as a dynamic sidelink scheduling DCI described above, allowing the precise resource allocation for SPS to be determined by eNB at the time it is needed. A transmitting UE can use the thus activated sidelink SPS resources, at the configured periodicity, until they are released (i.e. de-activated) by the eNB transmitting a special DCI. Note that each time the UE uses the resources, it either uses the RRC configured MCS/TBS or selects one itself, i.e. the same way as dynamic operation.
+
+#### 5.2.2.2 Resource allocation mode 4
+
+Mode 4 is for UE autonomous resource selection. Its basic structure is of a UE sensing, within a (pre-)configured resource pool, which resources are not in use by other UEs with higher-priority traffic, and choosing an appropriate amount of such resources for its own PSCCH/PSSCH transmission. Having selected such resources, the UE can transmit in them on a periodic (i.e. SPS) basis for a certain number of times, or until a cause of resource reselection is triggered.
+
+As described in Clause 5.2.2.1, the SCIs transmitted by UEs on PSCCH indicate the time-frequency resources in which the UE will transmit a PSSCH. The same SCI contents is used in mode 4, and also indicates the periodicity with which the UE will use the same resources. These SCI transmissions are used by sensing UEs to maintain a moving sensing window in the immediate past of which resources have been reserved by other UEs. This window is 1000 ms long for FDD systems. A sensing UE also measures the PSSCH-RSRP in the subframes of the sensing window, which implies the level of interference which would be caused and experienced if the sensing UE were to transmit in them.
+
+The sensing UE then selects resources for its first transmission from within a resource selection window. This window begins  $\leq 4$  ms after the trigger for transmission, and is bounded by the latency requirement of the traffic, up to 100 ms (see Clause 4). The sensing UE assumes the same resources will be used by other UEs in the future as have been found reserved during the sensing window, according to the indicated periodicities and durations. Reserved resources in the selection window with PSSCH-RSRP above a threshold are excluded from being candidates by the sensing UE, with the threshold set according to the priorities (PPPP) of the traffic of the sensing and transmitting UE. Thus, a higher priority transmission from a sensing UE can occupy resources which are reserved by a transmitting UE with sufficiently low PSSCH-RSRP and sufficiently lower-priority traffic.
+
+From the set of resources in the selection window which have not been excluded, the sensing UE identifies those containing the lowest total received energy as a way to account for transmissions which were not found during decoding of PSCCHs, and identifies resources totalling 20% of the available resources within the traffic's latency bound, including gradual relaxation of the PSSCH-RSRP exclusion thresholds in 3 dB steps if necessary. The UE then selects a resource at random from the identified 20% and uses this resource semi-persistently for its transmissions.
+
+There are a number of triggers for resource re-selection. They are designed to support high mobility, and ensure that a UE cannot assume occupation of a resource for an excessive period, nor when the selected resource is either insufficient or excessive for what is needed by the UE's traffic, amongst other causes.
+
+![Flowchart of sensing and resource (re-)selection procedures.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+```
+
+    graph TD
+    A["Keep decoding other UEs' SA  
+and measuring corresponding  
+PSSCH energy"] --> B["Collect sensing information  
+including PSSCH-RSRP and  
+S-RSSI measurement"]
+    B --> C["Exclude high-energy  
+resources and form candidate  
+resource set"]
+    C --> D["Select Tx resource and  
+transmit semi-persistently"]
+    D --> E{Resource  
+Re-selection?}
+    E -- "YES -  
+Restart  
+process" --> B
+    E -- "NO -  
+Continue  
+transmissions  
+on same  
+resources" --> D
+  
+```
+
+Flowchart of sensing and resource (re-)selection procedures.
+
+**Figure 5.2.2.2-1: Summary of sensing and resource (re-)selection procedures.**
+
+##### 5.2.2.2.1 Zones
+
+Cellular networks are designed to support resource re-use over a given geographical area, to manage interference and improve area spectral efficiency. A similar concept is available in LTE-V2X. LTE-V2X can optionally divide the world into zones, which have a (pre-)configurable width and height. Nearby zones are assigned different resource pools, with spatially-periodic re-use over a distance controlled by the zone width and height. A UE performs transmission within the resource pool(s) associated with its current zone, for mode 4. Figure 5.2.3-1 shows an example of the configuration of zones, where those with the same zone\_id use the same transmission resource pools.
+
+![Illustration of zones showing a repeating grid of zone IDs 0-8 based on x and y coordinates.](cb4cfa42ce34febde7bdb882f3fc3094_img.jpg)
+
+| y \ x | 0      | 1      | 2      | 0      | 1      | 2      |
+|-------|--------|--------|--------|--------|--------|--------|
+| 0     | Zone 0 | Zone 1 | Zone 2 | Zone 0 | Zone 1 | Zone 2 |
+| 1     | Zone 3 | Zone 4 | Zone 5 | Zone 3 | Zone 4 | Zone 5 |
+| 2     | Zone 6 | Zone 7 | Zone 8 | Zone 6 | Zone 7 | Zone 8 |
+| 0     | Zone 0 | Zone 1 | Zone 2 | Zone 0 | Zone 1 | Zone 2 |
+| 1     | Zone 3 | Zone 4 | Zone 5 | Zone 3 | Zone 4 | Zone 5 |
+
+Illustration of zones showing a repeating grid of zone IDs 0-8 based on x and y coordinates.
+
+**Figure 5.2.3-1: Illustration of zones.  $x' = \text{ceil}(x/L) \bmod N_x$ ;  $y' = \text{ceil}(y/W) \bmod N_y$ ; zone\_id =  $y' \times N_x + x'$ ; where  $x$  and  $y$  are the longitude and latitude of the UE's location,  $L$ ,  $W$  are the length and width of each zone, respectively, and  $N_x$ ,  $N_y$  are the number of zones in length and width respectively.**
+
+#### 5.2.2.3 Modes 3 and 4 resource pool sharing
+
+Resource pools for mode 3 and mode 4 are (pre-)configured separately from one another. In Rel-14, a receiving UE whether operating in mode 3 or mode 4 does not know in any particular way that a transmission in mode 3 has SPS characteristics, since the mode 3 SCI always indicates that its PSSCH transmission is single-shot. Thus, a mode 4 UE will not exclude the occupied resources during its resource selection procedure. In Rel-15, resource pool sharing is enabled by the mode 3 SCI also indicating a SPS reservation period, and mode 4 UEs of both releases are therefore able to account for such transmissions in the resource (re-)selection procedure.
+
+It is also possible for a UE operating in mode 3 to perform the mode 4 sensing procedure in order to report to eNB regarding the occupancy of resources in the mode 4 pools. This provides information which the eNB can use in determining its scheduling behaviour for mode 3.
+
+## 5.3 Sidelink congestion control
+
+Each sidelink packet is associated with a PPPP and PPPR passed down ultimately to the physical layer from upper layers, which determine the values based on the QoS requirements of the message. PPPR allows management of reliability, for example see Clause 5.4.7. The PPPP of a packet is indicated dynamically in the SCI which schedules the PSSCH for the packet. A physical measurement of CBR is also defined in each subframe TS 36.214 [12, clause 5.1.30], which measures the portion of the resource in a resource pool which has a high received signal energy (S-RSSI) in the most recent 100 subframes. CBR is a measurement of the congestion present recently in the resource pool. Another measurement, CR defined in TS 36.214 [12, clause 5.1.31], counts the total number of subchannels a UE has and will transmit in during a window of up to 1000 ms including the current subframe. CR is thus a measurement of how much resource a UE has recently, and will soon, claim.
+
+A UE can be (pre-)configured with a set of CBR ranges to each of which is linked a CR-limit. When a UE finds its CR exceeds the CR-limit for the CBR range it currently measures, it must reduce its CR to not exceed the limit. How this is done is up to UE implementation, and can include increasing MCS to reduce resource occupation, dropping (re-)transmissions, etc. PPPP can also be (pre-)configured with a mapping to the UE's maximum permitted transmit power, the limitation on which acts to reduce the CBR measured by sufficiently distant UEs.
+
+PPPP is used as described in Clause 5.2.2 to aid distributed sidelink congestion control based on the relative priorities of traffic from UEs that consider occupying a given resource. PPPP and CBR can each also be (pre-)configured with mappings to ranges of values of transmission parameters, e.g. a range of MCS values, and/or a range of numbers of subchannels, etc. In this case, the UE has to choose its transmission parameters from within the range corresponding to the prevailing PPPP and/or CBR.
+
+## 5.4 V2X sidelink higher-layer protocols
+
+### 5.4.1 General
+
+Figure 5.4.1-1 shows the user plane protocol stack for V2X sidelink communication. The Access Stratum protocol stack for user plane in the PC5 interface consists of PDCP, RLC, MAC and PHY as shown below in Figure 5.4.1-1. The detailed functions performed by PDCP, RLC and MAC sublayers are listed in TS 36.300 [13, clause 6], and some other details specific to V2X sidelink are described in TS 36.300 [13, clauses 23.10.2.1 and 23.14.1.1]. The PHY layer performs the functions described in Clause 5.1.
+
+![Diagram of the user-plane protocol stack for V2X sidelink communication between UE A and UE B. The stack consists of four layers: PDCP, RLC, MAC, and PHY. The layers are stacked vertically within each UE, and horizontal arrows indicate bidirectional communication between corresponding layers in UE A and UE B. The entire stack is labeled PC5-U at the bottom.](6f659142d4789aa889184459f884787e_img.jpg)
+
+```
+
+graph LR
+    subgraph UE_A [UE A]
+        PDCP_A[PDCP]
+        RLC_A[RLC]
+        MAC_A[MAC]
+        PHY_A[PHY]
+    end
+    subgraph UE_B [UE B]
+        PDCP_B[PDCP]
+        RLC_B[RLC]
+        MAC_B[MAC]
+        PHY_B[PHY]
+    end
+    PDCP_A <--> PDCP_B
+    RLC_A <--> RLC_B
+    MAC_A <--> MAC_B
+    PHY_A <--> PHY_B
+    PC5_U[PC5-U]
+  
+```
+
+Diagram of the user-plane protocol stack for V2X sidelink communication between UE A and UE B. The stack consists of four layers: PDCP, RLC, MAC, and PHY. The layers are stacked vertically within each UE, and horizontal arrows indicate bidirectional communication between corresponding layers in UE A and UE B. The entire stack is labeled PC5-U at the bottom.
+
+Figure 5.4.1-1: User-Plane protocol stack for V2X sidelink communication
+
+Figure 5.4.1-2 shows the control plane protocol stack for V2X sidelink communication. The Access Stratum protocol stack for control plane in the PC5 interface consists of RRC, RLC, MAC and PHY as shown below in Figure 5.4.1-2. The control plane protocol for V2X sidelink communication is mainly used for the transmission of sidelink broadcast control channel (SBCCH), and its functions are detailed in TS 36.300 [13, clause 23.10.2.2].
+
+![Diagram of the control-plane protocol stack for V2X sidelink communication between UE A and UE B. The stack consists of four layers: RRC, RLC, MAC, and PHY. Each layer in UE A is connected to the corresponding layer in UE B via a bidirectional arrow. The entire stack is labeled PC5-C at the bottom.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg)
+
+```
+
+graph LR
+    subgraph UE_A [UE A]
+        RRC_A[RRC]
+        RLC_A[RLC]
+        MAC_A[MAC]
+        PHY_A[PHY]
+    end
+    subgraph UE_B [UE B]
+        RRC_B[RRC]
+        RLC_B[RLC]
+        MAC_B[MAC]
+        PHY_B[PHY]
+    end
+    RRC_A <--> RRC_B
+    RLC_A <--> RLC_B
+    MAC_A <--> MAC_B
+    PHY_A <--> PHY_B
+    PC5_C[PC5-C]
+  
+```
+
+Diagram of the control-plane protocol stack for V2X sidelink communication between UE A and UE B. The stack consists of four layers: RRC, RLC, MAC, and PHY. Each layer in UE A is connected to the corresponding layer in UE B via a bidirectional arrow. The entire stack is labeled PC5-C at the bottom.
+
+Figure 5.4.1-2: Control-Plane protocol stack for V2X sidelink communication
+
+### 5.4.2 Resource pool configuration
+
+When the UE is in network coverage, it may use the resource configurations provided by the eNB via dedicated signalling or system information. When the UE is out of coverage, it may use pre-configured resource pools for V2X sidelink communication. Details of how the resource pools are (pre)configured and how the UE uses them for V2X sidelink communication transmission and reception are specified in TS 36.300 [17, clauses 5.10.12 and 5.10.13].
+
+### 5.4.3 Measurement and reporting
+
+Some measurement and reporting mechanisms are supported specifically for V2X sidelink communication, including CBR measurement and reporting, reporting of its sensing results and geo-location reporting. Details of above listed measurement and reporting mechanism specific for V2X sidelink communication are specified in TS 36.331 [10, clause 5.5].
+
+### 5.4.4 Mobility management
+
+UE can perform V2X sidelink transmission and reception during handover and cell reselection. Related details are specified in TS 36.331 [10, clause 5.10.13.1].
+
+### 5.4.5 Assistance information for SL SPS configuration
+
+The UE can report UE assistance information to the eNB to facilitate the configuration of sidelink SPS described in Clause 5.2.2.1. Details of the UE assistance information for sidelink SPS configuration are specified in TS 36.331 [10, clause 5.6.10].
+
+### 5.4.6 Transmission carrier selection
+
+For V2X sidelink communication, the UE is allowed to transmit and receive on multiple sidelink carriers (pre)configured by the network, and the UE selects specific sidelink carriers among them for transmission. The (pre)configured sidelink carriers can be provided by the network as specified in TS 36.331 [10, clause 5.10.13.1]. Details of transmission carrier selection are specified in TS 36.321 [14, clause 5.14.1.5].
+
+### 5.4.7 SL packet duplication
+
+To improve the reliability of V2X sidelink communication, a sidelink PDCP duplication mechanism is supported, where a PDCP PDU is duplicated into two instances and transmitted on two different sidelink carriers. Details of sidelink PDCP duplication are specified in TS 36.323 [15, clause 5.1.3 and 5.1.4] as well as TS 36.321 [14, clause 5.14.1.3.1].
+
+### 5.4.8 Coordination between UL and V2X SL transmission
+
+There is the possibility that the UE needs to perform UL transmission and V2X sidelink transmission overlapped in time domain, but the UE cannot transmit both. In this case, the UE will prioritize between the two transmissions. Details of the prioritization between UL transmission and V2X sidelink transmission are specified in TS 36.321 [14, clauses 5.4.2.2 and 5.14.1.2.2].
+
+### 5.4.9 Multi-PLMN operation
+
+To support multi-PLMN operation for V2X sidelink communication, the UE may receive the V2X sidelink communication of other PLMNs. However, V2X sidelink transmission in other PLMNs is not allowed. The same sidelink resource pool may be configured to the eNBs within a PLMN. Details of multi-PLMN operation for V2X sidelink communication are specified in TS 36.331 [10, clause 23.14.1.1].
+
+## 5.5 V2X via the Uu interface
+
+LTE-V2X, as mentioned above, is focused on transmission of a few types of periodic traffic, which can have different periodicities. Apart from using the sidelink, it is possible to transfer V2X data via the cellular network UL/DL, taking advantage of its centrally-scheduled operation, predictable latency bounds, and inter-cell communications.
+
+An extended form of UL SPS for V2X is supported, to allow firstly that V2X UL SPS and normal UL SPS can be used together, and also that multiple V2X UL SPS configurations can be defined to account for the different periodic V2X traffic types. Whereas in Rel-8 UL SPS a single SPS configuration can be provided by RRC, for LTE-V2X, up to 8 UL SPS configurations can be provided, similar to on the sidelink, which the eNB is assisted in the configuration of by information on traffic characteristics, etc., reported provided by the UE. A specialised version of DCI format 0 is then used to activate/release UL V2X SPS configurations as needed, and separately from the normal UL SPS configuration.
+
+LTE supports multicast/broadcast operation via SC-PTM and MBSFN transmission. These transmission types can also be used for V2X messages, and some adaptations for LTE-V2X are included to allow scheduling more frequent transmissions of data and service (re-)configuration information.
+
+## 5.6 Network aspects
+
+### 5.6.1 V2X service authorization
+
+Considering the different UE types based on subscription information in the HSS, the eNB receives the authorization status of the UE provided by a MME or a neighbour eNB, to know whether the UE is authorized as a Vehicle UE and/or a Pedestrian UE.
+
+Only authorized UEs can perform V2X sidelink communication. Sidelink radio resources are provided to UEs in different ways according to the different services supported.
+
+### 5.6.2 Sidelink AMBR
+
+UE sidelink AMBR is provided to the eNB by a MME or a neighbour eNB, and used for the UE's sidelink communication in mode 3. The sidelink AMBR is based on subscription information from the HSS and the operator's policy, which is used to cap the PC5 transmission from a particular UE.
+
+![Figure 5.6-1 Network Infrastructure for LTE V2X. The diagram shows an EPC (Evolved Packet Core) connected to two eNBs (evolved NodeBs). The left eNB is connected to three User Equipment (UE) vehicles via Uu interfaces. The right eNB is connected to three UE vehicles via PC5 interfaces. A callout box from the EPC indicates: '- Authorization status of UE' and '- UE Sidelink AMBR'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+Figure 5.6-1 Network Infrastructure for LTE V2X. The diagram shows an EPC (Evolved Packet Core) connected to two eNBs (evolved NodeBs). The left eNB is connected to three User Equipment (UE) vehicles via Uu interfaces. The right eNB is connected to three UE vehicles via PC5 interfaces. A callout box from the EPC indicates: '- Authorization status of UE' and '- UE Sidelink AMBR'.
+
+Figure 5.6-1 Network Infrastructure for LTE V2X.
+
+# 6 NR V2X
+
+## 6.1 Sidelink unicast, groupcast, and broadcast
+
+Whereas LTE-V2X supports broadcast transmission in the physical layer and any finer-grained addressing is handled according to MAC layer ID implementation, NR V2X has physical layer support for broadcast, unicast, and groupcast sidelink operation. The addition of unicast and groupcast is linked with the introduction of sidelink HARQ feedback (clause 6.2.4), high order modulation, sidelink CSI, and PC5-RRC (clause 6.5.7), amongst other points.
+
+## 6.2 V2X sidelink physical layer
+
+### 6.2.1 Physical sidelink channels and signals
+
+The NR V2X sidelink uses the following physical channels and signals:
+
+- Physical sidelink broadcast channel (PSBCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.3 and 8.4.1.4]
+- Physical sidelink control channel (PSCCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.2 and 8.4.1.3]
+- Physical sidelink shared channel (PSSCH) and its DMRS, specified in TS 38.211 [16, clauses 8.3.1 and 8.4.1.1]
+- Physical sidelink feedback channel (PSFCH), specified in TS 38.211 [16, clause 8.3.4]
+- Sidelink primary and secondary synchronization signals (S-PSS and S-SSS) specified in TS 38.211 [16, clause 8.4.2], which are organized into the sidelink synchronization signal block (S-SSB) together with PSBCH. S-PSS and S-SSS can be referred to jointly as the sidelink synchronization signal (SLSS).
+- Phase-tracking reference signal (PT-RS) in FR2, specified in TS 38.211 [16, clause 8.4.1.2].
+- Channel state information reference signal (CSI-RS), specified in TS 38.211 [16, clause 8.4.1.5]. See clause 6.2.3 for CSI.
+
+NR-V2X sidelink supports subcarrier spacings of 15, 30, 60 and 120 kHz. Their associations to CPs and frequency ranges are as for NR UL/DL, but using only the CP-OFDM waveform. The modulation schemes available are QPSK, 16-QAM, 64-QAM, and 256-QAM.
+
+PSBCH transmits the SL-BCH transport channel, which carries the sidelink V2X Master Information Block (MIB-V2X) from the RRC layer. When in use, PSBCH transmits MIB-V2X every 160 ms in 11 RBs of the SL bandwidth, with possible repetitions in the period. DMRS associated with PSBCH are transmitted in every symbol of the S-SSB slot. S-PSS and S-SSS are transmitted together with PSBCH in the S-SSB. They jointly convey the SLSS ID used by the UE. For further details of S-SSB, SLSS, and synchronization, refer to Clause 6.2.2.
+
+Sidelink control information (SCI) in NR V2X is transmitted in two stages. The first-stage SCI is carried on PSCCH and contains information to enable sensing operations, as well as information about the resource allocation of the PSSCH.
+
+PSSCH transmits the second-stage SCI and the SL-SCH transport channel. The second-stage SCI carries information needed to identify and decode the associated SL-SCH, as well as control for HARQ procedures, and triggers for CSI feedback, etc. SL-SCH carries the TB of data for transmission over SL.
+
+The resources in which PSSCH is transmitted can be scheduled or configured by a gNB (termed resource allocation mode 1, see Clause 6.3.2.1) or determined through a sensing procedure conducted autonomously by the transmitting UE (termed resource allocation mode 2, see Clause 6.3.2.2). A given TB can be transmitted multiple times, as described in Clauses 6.2.4 and 6.3.2. DMRS associated with rank-1 or rank-2 PSSCH can be transmitted in 2, 3, or 4 sidelink symbols distributed through a sidelink slot.
+
+Multiplexing between PSCCH and PSSCH is in time and frequency within a slot, illustrated in two examples in Figure 6.2.1-1.
+
+![Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH. The diagram shows a single slot divided into 14 symbols. From left to right: Symbol 1 is AGC (blue); Symbols 2 and 3 are PSCCH (yellow) and PSSCH (green) respectively; Symbols 4 and 5 are DMRS (red); Symbols 6 through 11 are PSSCH (green); Symbols 12 and 13 are DMRS (red); Symbol 14 is GUARD (white). A double-headed arrow below the symbols indicates the duration of '1 slot'.](75e4b78ee25f885d73120e3066a5253e_img.jpg)
+
+Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH. The diagram shows a single slot divided into 14 symbols. From left to right: Symbol 1 is AGC (blue); Symbols 2 and 3 are PSCCH (yellow) and PSSCH (green) respectively; Symbols 4 and 5 are DMRS (red); Symbols 6 through 11 are PSSCH (green); Symbols 12 and 13 are DMRS (red); Symbol 14 is GUARD (white). A double-headed arrow below the symbols indicates the duration of '1 slot'.
+
+Figure 6.2.1-1(a): Example slot format of 2-symbol PSCCH, 2-symbol PSSCH-DMRS, and no PSFCH.
+
+![Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH. The diagram shows a single slot divided into 14 symbols. From left to right: Symbol 1 is AGC (blue); Symbols 2, 3, and 4 are PSCCH (yellow), DMRS (red), and PSSCH (green) respectively; Symbols 5 through 7 are DMRS (red), PSSCH (green), and PSSCH (green) respectively; Symbols 8 and 9 are DMRS (red); Symbols 10 and 11 are PSSCH (green); Symbol 12 is GUARD (white); Symbol 13 is PSFCH (purple) with a diagonal hatched pattern; Symbol 14 is GUARD (white). A double-headed arrow below the symbols indicates the duration of '1 slot'.](7ede87328f6b696dcffa65ebc4570cc8_img.jpg)
+
+Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH. The diagram shows a single slot divided into 14 symbols. From left to right: Symbol 1 is AGC (blue); Symbols 2, 3, and 4 are PSCCH (yellow), DMRS (red), and PSSCH (green) respectively; Symbols 5 through 7 are DMRS (red), PSSCH (green), and PSSCH (green) respectively; Symbols 8 and 9 are DMRS (red); Symbols 10 and 11 are PSSCH (green); Symbol 12 is GUARD (white); Symbol 13 is PSFCH (purple) with a diagonal hatched pattern; Symbol 14 is GUARD (white). A double-headed arrow below the symbols indicates the duration of '1 slot'.
+
+Figure 6.2.1-1(b): Example slot format of 3-symbol PSCCH, 3-symbol PSSCH-DMRS, and PSFCH.
+
+PSFCH carries HARQ feedback over the sidelink from a UE which is an intended recipient of a PSSCH transmission (henceforth an Rx UE) to the UE which performed the transmission (henceforth a Tx UE). Sidelink HARQ feedback may be in the form of conventional ACK/NACK, or NACK-only with nothing transmitted in case of successful decoding; for more information refer to clause 6.2.4. PSFCH transmits a Zadoff-Chu sequence in one PRB repeated over two OFDM symbols, the first of which can be used for AGC, near the end of the sidelink resource in a slot. The time resources for PSFCH are (pre-)configured to occur once in every 1, 2, or 4 slots. Frequency/code resources are derived implicitly from those used by the associated PSSCH transmission, together with the L1 identity of the UE transmitting PSSCH and, when groupcast with ACK/NACK feedback is used, the identity within the group of the UE transmitting PSFCH.
+
+### 6.2.2 Sidelink synchronization
+
+#### 6.2.2.1 Synchronization references and priorities
+
+There are four basic sources, or references, from which a V2X UE can derive its own synchronization: GNSS, a gNB/eNB, another UE transmitting SLSS (here termed a SyncRef UE), or its own internal clock. In general, GNSS or eNB/gNB are regarded as the highest-quality sources. SyncRef UEs are distinguished between those which are directly
+
+synchronized to GNSS or a gNB/eNB, those which are 1 further step away, and those which are  $\geq 2$  further steps away from GNSS or gNB/eNB. As a last resort, a UE unable to find any other synchronization reference will use its own internal clock to transmit S-SSB. The V2X synchronization procedure defines a hierarchy or set of priorities among such synchronization references and requires all UEs to continuously search the hierarchy to get to the highest-quality one they can find. The general preference order is as follows, with details specified in TS 38.331 [17, clause 5.8.6]:
+
+- Level 1. Either GNSS or eNB/gNB, according to (pre-)configuration.
+- Level 2. A SyncRef UE directly synchronized to a Level 1 source.
+- Level 3. A SyncRef UE synchronized to a Level 2 source, i.e. indirectly synchronized to a Level 1 source.
+- Level 4. Whichever of GNSS or eNB/gNB was not (pre-)configured as the Level 1 source.
+- Level 5. A SyncRef UE directly synchronized to a Level 4 source.
+- Level 6. A SyncRef UE synchronized to a Level 5 source, i.e. indirectly synchronized to a Level 4 source.
+- Level 7. Any other SyncRef UE.
+- Level 8. UE's internal clock.
+
+The NR V2X scheme is intended to allow the merging of otherwise-separate hierarchies derived from GNSS and gNB/eNB, so that a UE is able to move between nearby such hierarchies without loss of sidelink service. However, since it is possible that a gNB/eNB does not itself have synchronization to GNSS, use of Levels 4-6 can be disabled when GNSS is used as Level 1, so that there is no deviation from the hierarchy being derived from GNSS.
+
+#### 6.2.2.2 S-SSB and SLSS
+
+S-PSS and S-SSS use the same types of sequence as NR PSS and SSS respectively, i.e. an *M*-sequence and a Gold sequence. When in use, both sequences are transmitted in 127 subcarriers of the S-SSB bandwidth, in the same slots as PSBCH. S-PSS is in the 2nd and 3rd symbols of the slot, S-SSS is in the 4th and 5th symbols, and PSBCH and its DMRS in each of the remaining symbols. The two symbols of each synchronization signal are the same, which allows detectors to benefit from phase tracking between the two symbols. Figure 6.2.2.2-1 shows the contents of a slot containing S-SSB, the frequency location of which is (pre-)configured.
+
+![Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. The diagram shows a single slot with 14 symbols. The first symbol is PSBCH (blue). Symbols 2 and 3 are S-PSS (yellow). Symbols 4 and 5 are S-SSS (green). Symbols 6 through 13 are PSBCH (blue). Symbol 14 is GUARD (white). Vertical double-headed arrows on the left and right indicate a bandwidth of 127 subcarriers / 11 RBs. A horizontal double-headed arrow at the bottom indicates the duration of 1 slot.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg)
+
+Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. The diagram shows a single slot with 14 symbols. The first symbol is PSBCH (blue). Symbols 2 and 3 are S-PSS (yellow). Symbols 4 and 5 are S-SSS (green). Symbols 6 through 13 are PSBCH (blue). Symbol 14 is GUARD (white). Vertical double-headed arrows on the left and right indicate a bandwidth of 127 subcarriers / 11 RBs. A horizontal double-headed arrow at the bottom indicates the duration of 1 slot.
+
+**Figure 6.2.2.2-1: Contents of a slot containing S-SSB for normal CP. Each PSBCH symbol contains DMRS.**
+
+The MIB-V2X is transmitted on PSBCH every 160 ms, and thus S-SSB occurs on the same period. Within a period, there can be multiple transmissions of S-SSB, with the number depending on subcarrier spacing and frequency range. For details refer to TS 38.213 [18, clause 16.1].
+
+##### 6.2.2.2.1 SLSSID
+
+The SLSSID itself conveys information about the synchronization source of the transmitting UE. In general, the further a UE is away from a high-quality source of GNSS or gNB/eNB, the lower quality will be its own synchronization and thus the quality of an SLSS it transmits. There are a series of association rules among SLSS IDs, designed to allow the identification, and propagation through the system of, high-quality synchronization sources. The operation of this procedure is essentially the same as LTE-V2X, described in Clause 5.1.2.2.1, with the main difference that there are
+
+672 SLSS IDs in NR-V2X, divided into 0, 1, ..., 335 for in-coverage indication and 336, ..., 671 for out-of-coverage indication. The special SLSS IDs of 0, 336, and 337 in NR-V2X are used equivalently to 0, 168, and 169 respectively in LTE-V2X.
+
+### 6.2.3 Sidelink CSI
+
+To provide the Tx UE with information it can use for sidelink link adaptation and rank adaptation in unicast transmissions, the Tx UE can configure aperiodic sidelink CSI reporting from the Rx UE. CQI and RI are reported via MAC layer signalling, in a PSSCH transmission. Calculation of the reported values is performed on sidelink CSI-RS from the Tx UE, which are a simplified subset of the Uu CSI-RS design, suitable for 1 or 2 antenna ports. The CSI report is transmitted by the Rx UE within a latency bound that is configured via PC5-RRC by the Tx UE, to ensure the report is timely with respect to the latency characteristic of the Tx UE's data traffic. The Tx UE must wait to trigger the next CSI report from a given Rx UE until the preceding report has been received, or its latency bound has expired.
+
+### 6.2.4 Sidelink HARQ
+
+NR-V2X supports HARQ based on transmission of ACK/NACK (or DTX) for sidelink unicast and groupcast services, as well as a NACK-only HARQ scheme particular to groupcast services. In addition, it supports blind re-transmission schemes, which are described in clauses 6.3.2.1 and 6.3.2.2 on resource allocation modes 1 and 2, respectively.
+
+When ACK/NACK (or DTX) operation is used, the sidelink HARQ procedure is similar to the Uu scheme for non-codeblock group feedback, i.e. the HARQ feedback is transmitted based on the success or failure of the whole transport block.
+
+NACK-only operation is defined for groupcast to allow a potentially lower sidelink resource demand to be created when a larger number of Rx UEs need to send feedback to the same Tx UE. A typical use case is an extended sensors scenario where UEs within a given radius all receive the same sensor information from the Tx UE, and re-transmission will occur if any UE fails to decode successfully. Since such information may only be relevant within a given radius around the Tx UE (e.g. a few tens or hundreds of meters around a road junction), the transmission of NACK-only feedback can be restricted to UEs within such a radius, and any UE beyond it does not provide any HARQ feedback. The minimum range requirement of a service is provided together with the associated QoS parameters from service layers.
+
+One bit of sidelink HARQ feedback is carried on PSFCH from an Rx UE to its Tx UE. In addition, when under the control of a gNB in resource allocation mode 1, the Tx UE informs the gNB via PUCCH or PUSCH of the status of the sidelink HARQ feedback it has computed related to a particular dynamic or configured grant to assist the scheduling of re-transmissions and allocation of sidelink resources.
+
+### 6.2.5 In-device coexistence between LTE-V2X and NR-V2X sidelinks
+
+It is envisaged that there will exist devices that support both LTE-V2X and NR-V2X, and which will be operating in both systems concurrently. If the two RATs are widely spaced in frequency, e.g. being in different bands, then there need be no particular issues to consider since it is assumed that a separate RF chain will be provided for each band.
+
+If, however, a sufficiently close frequency spacing is deployed, then it is desirable to enable a single RF chain to be used in the implementation, and also to adhere to the sidelink half-duplex principle established in LTE-V2X, i.e. that the UE is not required to simultaneously transmit and receive on sidelink. The former constraint means that interference between the two RATs' receptions can occur in the device if they are placed sufficiently close together in the frequency domain, and that simultaneous transmission on both RATs is prevented by the UE's single power budget. The latter constraint implies that one RAT cannot be received/transmitted while the other RAT is doing the opposite.
+
+It is possible to (pre-)configure the resource pools for the two sidelinks such that overlapping is avoided entirely. When this is not arranged, the general rule is that (at least) one of the RATs may be dropped at times when both occur simultaneously, but that in some cases where the priority of the V2X service on both RATs is known, the higher priority one is automatically selected:
+
+- Receive/receive overlap handling is always left to UE implementation decision.
+- Transmit/transmit overlap handling and transmit/receive overlap handling will automatically select the RAT with the highest priority service if both priorities are known. If the priorities are equal or not both known, the handling is left to UE implementation to decide.
+
+In the above rules, the priority of transmission and reception of sidelink synchronization signals/channels is set by (pre-)configuration and that of PSFCH is the same as the corresponding PSSCH.
+
+### 6.2.6 Concurrent operation
+
+NR-V2X operation is defined in bands n38 and n47 in TS 38.101-1 [22, clause 5.2E], which support single-carrier operation:
+
+**Table 6.2.6-1: NR-V2X operating bands**
+
+| V2X Operating Band                                                                                                | Sidelink (SL) Transmission operating band |   |                      | Sidelink (SL) Reception operating band |   |                      | Duplex Mode | Interface |
+|-------------------------------------------------------------------------------------------------------------------|-------------------------------------------|---|----------------------|----------------------------------------|---|----------------------|-------------|-----------|
+|                                                                                                                   | F <sub>UL_low</sub>                       | – | F <sub>UL_high</sub> | F <sub>DL_low</sub>                    | – | F <sub>DL_high</sub> |             |           |
+| n38 <sup>1</sup>                                                                                                  | 2570 MHz                                  | - | 2620 MHz             | 2570 MHz                               | - | 2620 MHz             | HD          | PC5       |
+| n47                                                                                                               | 5855 MHz                                  | - | 5925 MHz             | 5855 MHz                               | - | 5925 MHz             | HD          | PC5       |
+| Note 1: When this band is used for V2X SL service, the band is exclusively used for NR V2X in particular regions. |                                           |   |                      |                                        |   |                      |             |           |
+
+The NR-V2X sidelink in band n47 can be operated concurrently with Uu band n71.
+
+## 6.3 V2X sidelink resource allocation
+
+### 6.3.1 Sidelink bandwidth parts and resource pools
+
+#### 6.3.1.1 Sidelink bandwidth parts
+
+BWPs are defined for the sidelink in a similar way as for UL/DL, to provide a convenient way to specify aspects relating to a UEs RF hardware chain implementation. A UE is configured with one active sidelink BWP when in connected mode to a gNB, which is the same as the single sidelink BWP used for idle mode or out-of-coverage operation.
+
+The subcarrier spacing used on sidelink is provided in the sidelink BWP (pre-)configuration, from the same set of values and associations to frequency ranges as for the Uu interface (i.e. 15, 30, or 60 kHz for FR1; and 60 or 120 kHz for FR2). Sidelink transmission and reception for a UE are thus contained within a sidelink BWP, and the same sidelink BWP is used for both transmitting and receiving. This means that resource pools, S-SSB, etc. must also be contained within an appropriate sidelink BWP from the UE's perspective.
+
+#### 6.3.1.2 Resource pools
+
+PSCCH and PSSCH resources are defined within resource pools for the respective channels. This concept is used because in general PSCCH/PSSCH cannot be transmitted (and thus are not expected to be received) in all RBs and slots in the NR system bandwidth, nor within the frequency span configured for V2X sidelink. The notion of a resource pool also reflects, in resource allocation mode 2, that a UE will make its resource selections based on sensing within the pool.
+
+A resource pool is divided into sub-channels in the frequency domain, which are consecutively non-overlapping sets of  $\geq 10$  PRBs in a slot, the size depending on (pre-)configuration. Resource allocation, sensing, and resource selection are performed in units of a sub-channel. The UE's PSCCH occupies a (pre-)configurable number of PRBs within one sub-channel, starting from the lowest PRB of the PSSCH it schedules.
+
+Within the slots that can be used for PSSCH transmission, there can be from 7 to 14 of the symbols reserved for sidelink operation, of which PSSCH can be transmitted in 5 to 12 symbols. The remaining sidelink symbols transmit some or all of PSCCH, PSFCH, AGC symbol(s), guard symbol(s). Refer to Figure 6.2.1-1 for examples of slot formats.
+
+Resource pools are (pre-)configured to a UE separately from the transmission perspective (TX pools) and the reception perspective (RX pools). This allows a UE to monitor for PSCCH, and hence receive PSSCH transmissions, in resource pools other than those in which it transmits, so that it can attempt to receive transmissions made by other UEs in those RX pools.
+
+In addition, there are exceptional resource pools configured to a UE, in its serving cell's broadcast or in dedicated signalling. These can be used e.g. during RLF in some cases, handover, transition from RRC IDLE to RRC CONNECTED, or during change of dedicated V2X sidelink resource pools within a cell. In these cases, a UE may not have a stable configuration of TX resource pools but nevertheless should not be removed from the V2X system, and so it can randomly select resources in the exceptional pool, and use them temporarily. Likewise, UEs need to monitor the exceptional TX pools for PSCCH transmissions.
+
+### 6.3.2 Resource allocation modes
+
+#### 6.3.2.1 Mode 1
+
+Mode 1 is for resource allocation by gNB. As described in Clause 4, the use cases intended for NR V2X can generate a diverse array of periodic and aperiodic message types. Therefore, resource allocation mode 1 provides dynamic grants of sidelink resources from a gNB, as well as grants of periodic sidelink resources configured semi-statically by RRC, termed sidelink configured grants.
+
+A dynamic sidelink grant DCI can provide resources for one or multiple transmissions of a transport block, in order to allow control of reliability. The transmission(s) can be subject to the sidelink HARQ procedure, if that operation is enabled.
+
+A sidelink configured grant can be such that it is configured once and can be used by the UE immediately, until it is released by RRC signalling (known as Type 1). A UE is allowed to continue using this type of sidelink configured grant when beam failure or physical layer problems occur in NR Uu until an RLF detection timer expires, before falling back to an exception resource pool. The other type of sidelink configured grant, known as Type 2, is configured once but cannot be used until the gNB sends the UE a DCI indicating it is now active, and only until another DCI indicates deactivation. The resources in both types are a set of sidelink resources recurring with a periodicity which a gNB will desire to match to the characteristics of the V2X traffic. Multiple configured grants can be configured, to allow provision for different services, traffic types, etc.
+
+MCS information for dynamic and configured grants can optionally be provided or constrained by RRC signalling instead of the traditional DCI. RRC can configure the exact MCS the Tx UE uses, or a range of MCS. It may also be left unconfigured. For the cases where RRC does not provide the exact MCS, the transmitting UE is left to select an appropriate MCS itself based on the knowledge it has of the TB to be transmitted and, potentially, the sidelink radio conditions.
+
+The gNB scheduling activity is driven by the UE reporting its sidelink traffic characteristics to the gNB, or by performing a sidelink BSR procedure similar to that on Uu to request a sidelink resource allocation from gNB.
+
+#### 6.3.2.2 Mode 2
+
+Mode 2 is for UE autonomous resource selection. Its basic structure is of a UE sensing, within a (pre-)configured resource pool, which resources are not in use by other UEs with higher-priority traffic, and choosing an appropriate amount of such resources for its own transmissions. Having selected such resources, the UE can transmit and re-transmit in them a certain number of times, or until a cause of resource reselection is triggered.
+
+The mode 2 sensing procedure can select and then reserve resources for a variety of purposes reflecting that NR V2X introduces sidelink HARQ in support of unicast and groupcast in the physical layer. It may reserve resources to be used for a number of blind (re-)transmissions or HARQ-feedback-based (re-)transmissions of a transport block, in which case the resources are indicated in the SCI(s) scheduling the transport block. Alternatively, it may select resources to be used for the initial transmission of a later transport block, in which case the resources are indicated in an SCI scheduling a current transport block, in a manner similar to the LTE-V2X scheme (clause 5.2.2.2). Finally, an initial transmission of a transport block can be performed after sensing and resource selection, but without a reservation.
+
+The first-stage SCIs transmitted by UEs on PSCCH indicate the time-frequency resources in which the UE will transmit a PSSCH. These SCI transmissions are used by sensing UEs to maintain a record of which resources have been reserved by other UEs in the recent past. When a resource selection is triggered (e.g. by traffic arrival or a re-selection trigger), the UE considers a sensing window which starts a (pre-)configured time in the past and finishes shortly before the trigger time. The window can be either 1100 ms or 100 ms wide, with the intention that the 100 ms option is particularly useful for aperiodic traffic, and 1100 ms particularly for periodic traffic. A sensing UE also measures the SL-RSRP in the slots of the sensing window, which implies the level of interference which would be caused and experienced if the sensing UE were to transmit in them. In NR-V2X, SL-RSRP is a (pre-)configurable measurement of either PSSCH-RSRP or PSCCH-RSRP.
+
+The sensing UE then selects resources for its (re-)transmission(s) from within a resource selection window. The window starts shortly after the trigger for (re-)selection of resources, and cannot be longer than the remaining latency budget of the packet due to be transmitted. Reserved resources in the selection window with SL-RSRP above a threshold are excluded from being candidates by the sensing UE, with the threshold set according to the priorities of the traffic of the sensing and transmitting UEs. Thus, a higher priority transmission from a sensing UE can occupy resources which are reserved by a transmitting UE with sufficiently low SL-RSRP and sufficiently lower-priority traffic.
+
+If the set of resources in the selection window which have not been excluded is less than a certain proportion of the available resources within the window, the SL-RSRP exclusion threshold is relaxed in 3 dB steps. The proportion is set by (pre-)configuration to 20%, 35%, or 50% for each traffic priority. The UE selects an appropriate amount of resources randomly from this non-excluded set. The resources selected are not in general periodic. Up to three resources can be indicated in each SCI transmission, which can each be independently located in time and frequency. When the indicated resources are for semi-persistent transmission of another transport block, the range of supported periodicities is expanded compared to LTE-V2X, in order to cover the broader set of envisioned use cases in NR-V2X.
+
+Shortly before transmitting in a reserved resource, a sensing UE re-evaluates the set of resources from which it can select, to check whether its intended transmission is still suitable, taking account of late-arriving SCIs due, typically, to an aperiodic higher-priority service starting to transmit after the end of the original sensing window. If the reserved resources would not be part of the set for selection at this time ( $T3$ ), then new resources are selected from the updated resource selection window. The cut-off time  $T3$  is long enough before transmission to allow the UE to perform the calculations relating to resource re-selection.
+
+The timeline of the sensing and resource (re-)selection windows with respect to the time of trigger  $n$ , are shown in Figure 6.3.2.2-2(a), and the effect of the possibility of re-evaluation before first use of the reservation in Figure 6.3.2.2-2(b).
+
+There are a number of triggers for resource re-selection, several of which are similar to LTE-V2X in Clause 5.2.2.2. In addition, there is the possibility to configure a resource pool with a pre-emption function designed to help accommodate aperiodic sidelink traffic, so that a UE reselects all the resources it has already reserved in a particular slot if another nearby UE with higher priority indicates it will transmit in any of them, implying a high-priority aperiodic traffic arrival at the other UE, and the SL-RSRP is above the exclusion threshold. The application of pre-emption can apply between all priorities of data traffic, or only when the priority of the pre-empting traffic is higher than a threshold and higher than that of the pre-empted traffic. A UE does not need to consider the possibility of pre-emption later than time  $T3$  before the particular slot containing the reserved resources.
+
+![Flowchart of sensing and resource (re-)selection procedures.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+```
+
+graph TD
+    A[Keep decoding other UEs' PSCCH and measuring corresponding PSSCH energy] --> B[Collect sensing information including reserved resources and SL-RSRP measurements]
+    B --> C[Exclude own, and high-energy resources, and form candidate resource set]
+    C --> D[Select Tx resource semi-persistently, or up to maximum reservations, with start time 'm']
+    D --> E[Re-evaluate resource selection]
+    E --> F{Re-selection triggered?}
+    F -- YES --> G[Begin transmitting]
+    F -- NO --> B
+    G --> H{Resource re-selection?}
+    H -- "YES - Restart process" --> B
+    H -- "NO - Continue using reservation" --> G
+
+```
+
+Flowchart of sensing and resource (re-)selection procedures.
+
+Figure 6.3.2.2-1: Summary of sensing and resource (re-)selection procedures
+
+![Timeline of sensing and resource (re-)selection procedure triggered at time n.](d6a5f8423065d7cef55e11a0007014d9_img.jpg)
+
+Timeline details:
+
+- The horizontal axis represents time.
+- Sensing window:** Ends at time  $n$ , with duration  $T_0$ .
+- Processing time:**  $T_{proc,0}$  occurs immediately after time  $n$ .
+- Selection window:** Starts after  $T_{proc,0}$  and ends at the end of the PDB. It contains the first reserved resource at time  $m$ .
+- Timing constraints:**  $T2, T2_{min} \le T2 \le \text{remaining PDB}$ .
+- Reservations:** Indicated by green blocks starting at time  $m$ , with blue arrows showing periodic reservations.
+
+Timeline of sensing and resource (re-)selection procedure triggered at time n.
+
+Figure 6.3.2.2-2(a): Timeline of sensing and resource (re-)selection procedure triggered at time  $n$ , without re-evaluation before  $(m-T_3)$ . Its first reserved resource is at time  $m$ .
+
+![Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure. A horizontal timeline shows a 'sensing window' ending at time n. A 're-selection window' starts at time m and ends at time m'. A time interval T3 is marked between the end of the sensing window and the start of the re-selection window. At time m, a resource is reserved (indicated by a green bar with an X). At time m', a new resource is reserved (indicated by a green bar). Arrows point from the resource at m to the resource at m', and from the resource at m' to subsequent 'reservation(s)'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure. A horizontal timeline shows a 'sensing window' ending at time n. A 're-selection window' starts at time m and ends at time m'. A time interval T3 is marked between the end of the sensing window and the start of the re-selection window. At time m, a resource is reserved (indicated by a green bar with an X). At time m', a new resource is reserved (indicated by a green bar). Arrows point from the resource at m to the resource at m', and from the resource at m' to subsequent 'reservation(s)'.
+
+Figure 6.3.2.2-2(b): Timeline of sensing and resource (re-)selection procedure originally triggered at time  $n$ , which has a first reserved resource at time  $m$ , when re-evaluation occurring at  $m-T3$  determines the resources are no longer selectable. The new re-evaluation cut-off becomes  $(m'-T3)$ .
+
+## 6.4 Sidelink congestion control
+
+Congestion control for NR-V2X is similar to that described in Clause 5.3 for LTE-V2X, and it likewise is used in resource allocation mode 2 in NR. The main differences are that each packet is associated with a single 'priority' value, passed down to the physical layer from upper layers, which is comparable to PPPP in LTE-V2X. The priority value is transmitted in the first-stage SCI associated with each transport block. Broadly equivalent measurements of CBR and CR, together with CR-limits are defined, which can be used similarly to constrain the ranges of transmission parameters. NR V2X sets a shorter time of 1 ms or 2 ms in which the UE must calculate the CR and CBR than LTE-V2X's 4 ms, with the aim of adapting to faster fluctuations in congestion due to aperiodic traffic.
+
+## 6.5 V2X sidelink higher-layer protocols
+
+### 6.5.1 General
+
+Figure 6.5.1-1 shows the user plane protocol stack for NR sidelink communication. The AS protocol stack of user plane in the PC5 interface consists of SDAP, PDCP, RLC, MAC, and the physical layer as shown below in Figure 6.5.1-1, from TS 38.300 [20, Clause 16.9.2.1].
+
+![Figure 6.5.1-1: User plane protocol stack for STCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a stack of five protocols: SDAP, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the corresponding protocol layers between UE A and UE B, indicating bidirectional communication.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg)
+
+Figure 6.5.1-1: User plane protocol stack for STCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a stack of five protocols: SDAP, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the corresponding protocol layers between UE A and UE B, indicating bidirectional communication.
+
+Figure 6.5.1-1: User plane protocol stack for STCH.
+
+Figure 6.5.1-2 shows the control plane protocol stack for SCCH for RRC for NR sidelink communication. The AS protocol stack of the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC, MAC and the physical layer as shown below in Figure 6.5.1-2, from TS 38.300 [20, Clause 16.9.2.1].
+
+![Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: RRC, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](28d75f39a24203712ee907b32cf0bbe5_img.jpg)
+
+Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: RRC, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.
+
+**Figure 6.5.1-2: Control plane (PC5-C) protocol stack for SCCH for RRC.**
+
+Figure 6.5.1-3 shows the control plane protocol stack for PC-S. PC5-S is located on top of PDCP, RLC and MAC sublayers, and the physical layer for the control plane in the PC5 interface as shown in Figure 6.5.1-3, from TS 38.300 [20, Clause 16.9.2.1].
+
+![Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: PC5-S, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the PC5-S layer of UE A to the PC5-S layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](f0a97d0d3818a253c1d2a009966081b1_img.jpg)
+
+Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of five protocol layers: PC5-S, PDCP, RLC, MAC, and PHY. Horizontal double-headed arrows connect the PC5-S layer of UE A to the PC5-S layer of UE B, the PDCP layer of UE A to the PDCP layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.
+
+**Figure 6.5.1-3: Control plane (PC5-C) protocol stack for SCCH for PC5-S.**
+
+The AS protocol stack for SBCCH in the PC5 interface consists of RRC, RLC, MAC sublayers, and the physical layer as shown below in Figure 6.5.1-4, from TS 38.300 [20, Clause 16.9.2.1].
+
+![Figure 6.5.1-4: Control plane protocol stack for SBCCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of four protocol layers: RRC, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.](e9b43ac020435f8121e8592f31afdc52_img.jpg)
+
+Figure 6.5.1-4: Control plane protocol stack for SBCCH. The diagram shows two User Equipment (UE) blocks, UE A and UE B, each containing a vertical stack of four protocol layers: RRC, RLC, MAC, and PHY. Horizontal double-headed arrows connect the RRC layer of UE A to the RRC layer of UE B, the RLC layer of UE A to the RLC layer of UE B, the MAC layer of UE A to the MAC layer of UE B, and the PHY layer of UE A to the PHY layer of UE B.
+
+**Figure 6.5.1-4: Control plane protocol stack for SBCCH.**
+
+### 6.5.2 Measurement and reporting related to NR sidelink communication
+
+Some measurement and reporting mechanisms are supported specifically for NR sidelink communication, including CBR measurement and reporting to NG-RAN, reporting of location information to NG-RAN, and L3-filtered RSRP measurement and reporting in PC5 interface.
+
+To provide some information to assist network's scheduling and/or transmission parameter adjustment, CBR measurement and reporting is performed for the RRC\_CONNECTED UEs.
+
+To provide the Tx UE with information it can use for open loop power control in unicast transmissions, the Rx UE can perform RSRP measurement based on DMRS and report the L3-filtered RSRP to the Tx UE.
+
+Details of the measurement and reporting mechanism specific for NR sidelink communication are specified in TS 38.331 [17, clause 5.5].
+
+### 6.5.3 Mobility management for NR SL transmission/reception
+
+UE can perform NR sidelink transmission and reception during handover and cell reselection. During handover, sidelink transmission and reception are performed based on configuration of the exceptional transmission resource pool or configured sidelink grant Type 1 and reception resource pool of the target cell as provided in the handover command.
+
+Related details are specified in TS 38.331 [17, clause 5.8.8].
+
+### 6.5.4 Assistance information and SL configured grant configuration
+
+NG-RAN can allocate sidelink resources to UE with two types of configured sidelink grants (Type 1 and Type 2). For the UE performing NR sidelink communication, there can be more than one configured sidelink grant activated at a time on the carrier configured for sidelink transmission.
+
+To provide assistance information for the configuration of configured grant, UE assistance information on traffic pattern can be reported to the network. The periodicity, time offset, message size, QoS info and destination can be included in the reporting message.
+
+### 6.5.5 Coordination between UL and NR SL transmission
+
+NR-UL/NR-SL prioritization is performed when the following scenarios occur:
+
+- when UL TX overlaps in time domain with SL TX in the shared/same carrier frequency;
+- when UL TX and SL TX (in different carrier frequency) share TX chains and power budget;
+
+To support NR-UL/NR-SL prioritization, a separate LCH priority threshold is configured for both NR-UL and NR-SL. For SL data and UL data/SRB, the SL transmission is prioritized if the highest priority value of UL LCH(s) with available data is larger than the UL priority threshold and the highest priority value of SL LCH(s) with available data is lower than the SL priority threshold, otherwise the UL transmission is prioritized. Details of the prioritization between UL transmission and NR sidelink transmission are specified in TS 38.321 [21, clause 5.22.1.3].
+
+The physical layer also provides prioritization and multiplexing rules between NR UL and NR SL when their transmissions would overlap, using rules similar to those from the Uu interface and relying on the priorities of the respective transmissions.
+
+### 6.5.6 QoS mechanism
+
+For NR sidelink communication, per flow based QoS model is used for sidelink unicast, groupcast and broadcast.
+
+For RRC\_CONNECTED UEs, the UE may report the QoS information of the PC5 QoS flow via RRC dedicated signalling for transmission of a new PC5 QoS flow, and the network may provide SLRB configurations and configure the mapping of PC5 QoS flow to SLRB via RRC dedicated signalling, based on the QoS information reported by the UE.
+
+For RRC\_IDLE/INACTIVE UEs, the network may provide SLRB configurations and configure the PC5 QoS profile to SLRB mapping via V2X-specific SIB.
+
+For out of coverage UEs, SLRB configurations and the mapping of PC5 QoS profile to SLRB are pre-configured..
+
+### 6.5.7 Sidelink RRC
+
+For unicast NR sidelink communication, the PC5-RRC connection is a logical connection between a pair of source and destination L2 IDs.
+
+The AS layer configuration including the parameters which need to be aligned between Tx UE and Rx UE can be conveyed via PC5 RRC signalling. In case AS layer configuration fails, both explicit failure message and timer based indication can be considered to be used to indicate the failure to the peer UE.
+
+UE capability can be interacted between pair UEs via PC5 RRC. A UE can send Capability Enquiry message to request peer UE's capability along with its own capability information. When to include its own capabilities is up to UE implementation.
+
+Moreover, SL RLM/RLF is supported for unicast NR sidelink communication. Upon RL RLF declaration, the UE releases the PC5 RRC connection immediately and sends an indication to upper layer. For RRC\_CONNECTED UEs, the UE also informs the network via sidelink UE information upon RLF is detected.
+
+Details of the sidelink RRC procedures for NR sidelink communication are specified in TS 38.331 [17, clause 5.8.9].
+
+## 6.6 V2X via the Uu interface
+
+Some advanced V2X services are provided by an application server residing in the Internet which processes information received from the UE and issues instructions back to control the vehicle. Such applications can allow a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves. Other services, termed advanced driving, can incorporate video sharing among vehicles via an application server. In such applications, the communication is UE to/from the server via a cellular network's NR Uu interface.
+
+Therefore, the Uu interface can activate multiple PUSCH configured grants (which are periodical resource grants configured by RRC, similar to LTE SPS in clause 5.5) simultaneously so that traffic sources with different requirements on latency, reliability, etc. can be handled at the same time. It is also possible for a PUSCH configured grant to send more than one PUSCH repetition in a slot or across a slot boundary, for the purpose of reducing UL latency.
+
+## 6.7 Network aspects
+
+### 6.7.1 V2X service authorization
+
+Similarly as LTE V2X, the NG-RAN node receives the authorization status of the UE provided by a Core Network or a neighbour NG-RAN node, to know whether the UE is authorized as a Vehicle UE and/or a Pedestrian UE. Only the authorized UEs can perform V2X sidelink communication. Sidelink radio resources are provided to UEs in different ways according to the different services supported.
+
+### 6.7.2 Alternative QoS Profiles
+
+A list of alternative QoS parameter sets may be provided additionally for a GBR QoS Flow with Notification control enabled by the SMF to the NG-RAN node, or by the source NG-RAN node to the target NG-RAN node during handover.
+
+The NG-RAN node, or the target NG-RAN node during handover, checks the requested QoS profile and the list of alternative QoS parameter sets. If one of the alternative QoS parameter sets can be fulfilled, it then indicates a reference to the fulfilled alternative QoS parameters set to the SMF and/or the source NG-RAN node.
+
+# --- 7 Multi-RAT V2X
+
+## 7.1 Cross-RAT operation
+
+It is envisaged that NR-V2X and LTE-V2X will be at least initially deployed in similar timeframes, and also during a time when MNOs may have either or both of NR and LTE cellular networks available. An optional UE design response to this is supported where a device has both an LTE-V2X RAT and an NR-V2X RAT which are able to inter-communicate. This would enable the UE to perform sidelink communications with other UEs which implement only one of the sidelinks, and to do so whether they are in a cellular network of LTE or NR. Hence, for example, an LTE cellular network can be involved in controlling the NR sidelink via such dual-mode UEs, and an NR cellular network can similarly be involved in controlling LTE sidelink UEs.
+
+LTE Uu can control NR resource allocation mode 1 by providing configured grant Type 1 configurations via LTE RRC signalling. This allows provision of periodically occurring sets of NR resources for the NR sidelink – see Clause 6.3.2.1. Control of NR resource allocation mode 2 is by LTE Uu RRC providing the semi-static configurations relevant
+
+to resource pools, sensing, etc. within which the NR-V2X RAT autonomously selects resources for sidelink transmission.
+
+NR Uu can control LTE resource allocation mode 3 by transmitting an NR DCI which contains the information needed to dynamically control the LTE sidelink. The UE transfers this information internally to its LTE RAT, for which a certain amount of processing time is allowed, and then follows normal LTE sidelink procedures. Control of LTE resource allocation mode 4 is by NR Uu RRC providing the necessary semi-static configurations within which the LTE-V2X RAT autonomously selects resources for sidelink transmission.
+
+Two separate sets of information for V2X services authorization can be signalled, i.e., the NR V2X Services Authorized IE, and the LTE V2X Services Authorized IE. These can be provided over the NG, S1, Xn, X2, and F1 interfaces, from the Core Network to the RAN node, between RAN nodes, and from gNB-CU to gNB-DU.
+
+## 7.2 MR-DC
+
+The scenarios for LTE V2X sidelink communication and NR sidelink communication are captured in the following figures. The scenarios can be categorized into standalone and MR-DC scenarios, according to TS 37.340 [19], regarding the architecture.
+
+Figure 7.2-1, Figure 7.2-2 and Figure 7.2-3 illustrate the standalone scenarios to support LTE V2X sidelink communication and NR sidelink communication. Particularly:
+
+- 1) In scenario 1, a gNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL;
+- 2) In scenario 2, an ng-eNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL;
+- 3) In scenario 3, an eNB provides control/configuration for a UE's V2X communication in both LTE SL and NR SL.
+
+![Diagram of Scenario 1: A 5GC cloud connected to an NR base station (yellow antenna icon). Two cars are shown below, connected to the NR base station. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'.](80ec3bf791fd8eb41f73a420c2122529_img.jpg)
+
+The diagram shows a 5GC cloud at the top connected to an NR base station, represented by a yellow antenna icon. Below the base station, two white cars are shown. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'. Arrows point from the NR base station to each car.
+
+Diagram of Scenario 1: A 5GC cloud connected to an NR base station (yellow antenna icon). Two cars are shown below, connected to the NR base station. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'.
+
+Figure 7.2-1: Scenario 1
+
+![Diagram of Scenario 2: A 5GC cloud connected to an E-UTRAN base station (blue antenna icon). Two cars are shown below, connected to the E-UTRAN base station. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'.](e1476fd216f6cf773e262013fb4aba7d_img.jpg)
+
+The diagram shows a 5GC cloud at the top connected to an E-UTRAN base station, represented by a blue antenna icon. Below the base station, two white cars are shown. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'. Arrows point from the E-UTRAN base station to each car.
+
+Diagram of Scenario 2: A 5GC cloud connected to an E-UTRAN base station (blue antenna icon). Two cars are shown below, connected to the E-UTRAN base station. Between the cars, there are two horizontal double-headed arrows: a yellow one labeled 'NR V2X SL' and a blue one labeled 'LTE V2X SL'.
+
+Figure 7.2-2: Scenario 2
+
+![Figure 7.2-3: Scenario 3 diagram showing two UEs connected to a single EPC/E-UTRAN. The UEs are shown with bidirectional arrows for NR V2X SL and LTE V2X SL communication between them.](b5335262987c819d7f71ce40f99cb71b_img.jpg)
+
+The diagram illustrates Scenario 3. At the top, a cloud labeled 'EPC' contains a blue antenna icon labeled 'E-UTRAN'. Below it, two white car icons represent User Equipment (UEs). A yellow double-headed arrow between the cars is labeled 'NR V2X SL', and a blue double-headed arrow below it is labeled 'LTE V2X SL'. Arrows point from each car up to the E-UTRAN icon.
+
+Figure 7.2-3: Scenario 3 diagram showing two UEs connected to a single EPC/E-UTRAN. The UEs are shown with bidirectional arrows for NR V2X SL and LTE V2X SL communication between them.
+
+Figure 7.2-3: Scenario 3
+
+Figure 7.2-4, Figure 7.2-5 and Figure 7.2-6 illustrate the MR-DC scenarios to support LTE V2X sidelink communication and NR sidelink communication. For the MR-DC scenario, MN controlling/configuring both NR SL and LTE SL in Scenarios 4, 5 and 6 is covered by Scenarios 1, 2 and 3 respectively. Particularly:
+
+- 1) In scenario 4, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured with NE-DC;
+- 2) In scenario 5, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured in NGEN-DC;
+- 3) In scenario 6, a UE's V2X communication in LTE SL and NR SL is controlled/configured by Uu while the UE is configured in EN-DC.
+
+![Figure 7.2-4: Scenario 4 diagram showing two UEs connected to a 5GC via MgNB and SeNB. The UEs are shown with bidirectional arrows for LTE V2X SL and NR V2X SL communication between them.](b904ac2472cab80892d1e783e6230d6e_img.jpg)
+
+The diagram illustrates Scenario 4. At the top, a cloud labeled '5GC' contains two antenna icons: a blue one labeled 'MgNB' and a yellow one labeled 'SeNB'. Below it, two white car icons represent UEs. A yellow double-headed arrow between the cars is labeled 'LTE V2X SL', and a blue double-headed arrow below it is labeled 'NR V2X SL'. Arrows point from each car to both the MgNB and SeNB icons.
+
+Figure 7.2-4: Scenario 4 diagram showing two UEs connected to a 5GC via MgNB and SeNB. The UEs are shown with bidirectional arrows for LTE V2X SL and NR V2X SL communication between them.
+
+Figure 7.2-4: Scenario 4
+
+![Figure 7.2-5: Scenario 5 diagram showing two UEs connected to a 5GC via MeNB and SgNB. The UEs are shown with bidirectional arrows for NR V2X SL and LTE V2X SL communication between them.](dfaa8b98082261913dac00eae86b2889_img.jpg)
+
+The diagram illustrates Scenario 5. At the top, a cloud labeled '5GC' contains two antenna icons: a blue one labeled 'MeNB' and a yellow one labeled 'SgNB'. Below it, two white car icons represent UEs. A yellow double-headed arrow between the cars is labeled 'NR V2X SL', and a blue double-headed arrow below it is labeled 'LTE V2X SL'. Arrows point from each car to both the MeNB and SgNB icons.
+
+Figure 7.2-5: Scenario 5 diagram showing two UEs connected to a 5GC via MeNB and SgNB. The UEs are shown with bidirectional arrows for NR V2X SL and LTE V2X SL communication between them.
+
+Figure 7.2-5: Scenario 5
+
+![Diagram of Scenario 6 showing a Mobile Network (MN) and a Serving Network (SN) connected to an EPC cloud. Two cars are shown below, with dashed arrows indicating communication links from the MN and SN to each car. Solid double-headed arrows between the cars are labeled 'NR V2X SL' and 'LTE V2X SL'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg)
+
+The diagram illustrates Scenario 6. At the top, a cloud labeled 'EPC' is connected to two network nodes: 'MN' (Mobile Network) on the left and 'SN' (Serving Network) on the right. Below the cloud, two cars are depicted. Dashed arrows point from the 'MN' node to both cars, and from the 'SN' node to both cars. Between the two cars, there are two horizontal double-headed arrows: the top one is labeled 'NR V2X SL' and the bottom one is labeled 'LTE V2X SL'.
+
+Diagram of Scenario 6 showing a Mobile Network (MN) and a Serving Network (SN) connected to an EPC cloud. Two cars are shown below, with dashed arrows indicating communication links from the MN and SN to each car. Solid double-headed arrows between the cars are labeled 'NR V2X SL' and 'LTE V2X SL'.
+
+Figure 7.2-6: Scenario 6
+
+# 8 Transmission profiles
+
+LTE-V2X was developed over the course of two 3GPP Releases, Rel-14 and Rel-15. In Rel-15, non-backward compatible changes to physical transmission formats were introduced, primarily to support the use of 64-QAM on PSSCH compared to the maximum of 16-QAM in Rel-14. Such transmissions cannot be decoded by Rel-14 UEs. However, on sidelink, a transmitting UE cannot know the Release of specifications supported by the UEs which will receive the PSSCH transmission, since the transmission is broadcast in the physical layer. Therefore, the concept of transmission profiles was introduced, which associates to each transmission by a Rel-15 UE a (pre-)configuration of which Release's transmission format to use. A transmitting UE performs transmission format selection based on the profile indicated by higher layer of the 3GPP protocol stack. If a Rel-14 format is indicated, then the transmission can be decoded by both Releases of UE, whereas if Rel-15 format is indicated, it can be decoded only by Rel-15 UEs. When a UE has traffic from different application sources to transmit at the same time, the transmission profile associated with the highest-priority traffic is applied. The association of transmission profiles to traffic sources (specifically, logical channels) is provided by 3GPP protocol layers outside of RAN.
+
+In the present Release of this TR, transmission profiles are not defined in NR-V2X.
+
+# 9 Pedestrian UE
+
+As discussed in Clause 4, LTE-V2X includes communications between Pedestrian LTE UEs and Vehicular LTE UEs, i.e. V2P. Whereas a vehicular LTE UE is assumed to be attached the vehicle's power supply, and thus to have no particular battery life concerns, the situation is different for a P-UE. A P-UE could be, e.g. a conventional smartphone running suitable applications, or a specialised device attached to a pedestrians clothing, etc. In either case, battery life has to be considered so that the device will provide the LTE-V2P services for a reasonable length of time without need of re-charging, and without imposing such battery drain that LTE-V2P applications could become unattractive.
+
+As described in Clause 5.2.2.2, a LTE-V2X UE performs sensing continuously in a 1000 ms historical window, implying an amount of ongoing power consumption due to the sensing procedure. It is allowed for a LTE P-UE to not support sidelink reception, so that it is only broadcasting packets relating to its own location and direction. This type of P-UE is allowed to select transmission resources randomly, with no sensing procedure. For a LTE P-UE which does support sidelink reception, it can be (pre-)configured to perform partial sensing. In partial sensing, only a subset of the subframes in the typically 1000 ms sensing window have to be monitored. The LTE UE implementation can choose how few subframes it wishes to monitor, by trading off the reliability of its transmissions with the power saving, subject to monitoring a (pre-)configured minimum number. (Pre-)configuration can also set how far into the past the sensing window extends, and can require that the UE performs partial sensing in a number of these truncated sensing windows.
+
+In the present Release of this TR, functions particular to Pedestrian UEs are not defined in NR-V2X.
+
+# --- 10 Roadside unit
+
+The development of LTE and NR V2X contemplates three entities in the network: base stations, i.e. eNBs and gNBs; UEs; and RSUs. An RSU is defined in TS 22.185 [6], TS 22.186 [7] as a stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications. Note that RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic using the functionality provided by either a 3GPP network (referred to as an eNB/gNB-type RSU) or a UE (referred to as UE-type RSU).
+
+Since an RSU is essentially only different from an eNB/gNB or UE in terms of its deployment nature, e.g. it may be deployed by a national roads authority instead of an MNO, there is no specification of features particular to RSUs. They operate simply according to sidelink or UL/DL specifications as appropriate.
+
+# Annex <A> (informative): Change history
+
+| Change history |               |            |      |     |     |                                                                   |             |
+|----------------|---------------|------------|------|-----|-----|-------------------------------------------------------------------|-------------|
+| Date           | Meeting       | TDoc       | CR   | Rev | Cat | Subject/Comment                                                   | New version |
+| 2019-05        | RAN1#97       | R1-1906663 |      |     |     | Initial version of TR and skeleton of LTE-V2X clauses             | 0.0.1       |
+| 2019-08        | RAN1#98       | R1-1909651 |      |     |     | LTE-V2X first version, and skeleton of NR-V2X clauses             | 0.1.0       |
+| 2019-10        | RAN1#98bis    | R1-1910616 |      |     |     | Addition of RAN2 and RAN3 LTE-V2X, and NR-V2X first version       | 0.2.0       |
+| 2019-11        | RAN1#99       | R1-1913120 |      |     |     | RAN2 NR V2X skeleton and updates to RAN1 NR V2X clauses           | 0.3.0       |
+| 2019-11        | RAN1#99       | R1-1913587 |      |     |     | V1.0.0 to RAN for information                                     | 1.0.0       |
+| 2020-02        | RAN1#100-e    | R1-2001223 |      |     |     | Updates to NR V2X clauses; addition of introduction and scope     | 1.1.0       |
+| 2020-04        | RAN1#100bis-e | R1-2002762 |      |     |     | Updates and refinements after RAN1#100-e                          | 1.2.0       |
+| 2020-05        | RAN1#101-e    | R1-2004861 |      |     |     | Updates and refinements after RAN1#100bis-e                       | 1.4.0       |
+| 2020-06        | RAN#88-e      | RP-200708  |      |     |     | V2.0.0 (endorsed by RAN1#101-e in R1-2005121) to RAN for approval | 2.0.0       |
+| 2020-06        | RAN#88-e      | -          |      |     |     | TR37.985 is approved and under change control as a Rel-16 spec    | 16.0.0      |
+| 2022-03        | RAN#95-e      | RP-220245  | 0002 |     | F   | Addition of Rel-16 NR V2X bands to TR 37.985                      | 16.1.0      |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46001/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46001/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..41fd1fe779448fbbab7a8f7c30a7ea864fe638c5
--- /dev/null
+++ b/marked/Rel-16/46_series/46001/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8dc54750dc55b712d3b71069e08d607fd94b93397a28506ec02f19cd6c7799f4
+size 146832
diff --git a/marked/Rel-16/46_series/46001/raw.md b/marked/Rel-16/46_series/46001/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..4acbc0e40b56f34ac761d25b6abb6dd6a30579e0
--- /dev/null
+++ b/marked/Rel-16/46_series/46001/raw.md
@@ -0,0 +1,218 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                         |    |
+|-------------------------------------------------------------------------|----|
+| Foreword .....                                                          | 4  |
+| 1 Scope.....                                                            | 5  |
+| 2 References.....                                                       | 5  |
+| 3 Abbreviations .....                                                   | 5  |
+| 4 Introduction.....                                                     | 6  |
+| 5 Full rate speech transcoding (GSM 06.10) .....                        | 6  |
+| 6 Full rate Discontinuous Transmission (DTX) (GSM 06.31) .....          | 6  |
+| 7 Full rate Voice Activity Detection (VAD) (GSM 06.32) .....            | 7  |
+| 8 Full rate comfort noise insertion (GSM 06.12).....                    | 7  |
+| 9 Full rate lost speech frame substitution and muting (GSM 06.11) ..... | 7  |
+| 10 Full Rate codec homing (GSM 06.10, optional feature).....            | 7  |
+| 11 Speech transmission functions of the half rate traffic channel ..... | 8  |
+| Annex A (informative): Change History.....                              | 10 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is an introduction to the 06 series of the GSM technical specifications dealing with the Full rate speech processing functions in the GSM system. A general overview of the speech processing parts is given with reference to the technical specifications where each part is specified in detail.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
+- [3] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding".
+- [4] GSM 06.11: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels".
+- [5] GSM 06.12: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels".
+- [6] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels".
+- [7] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for full rate speech traffic channels".
+- [8] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- [9] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [10] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- [11] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- [12] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [13] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+# --- 3 Abbreviations
+
+Abbreviations used in the present document are listed in GSM 01.04 [1].
+
+# --- 4 Introduction
+
+Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant technical specifications for each function are also indicated.
+
+In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface to the PSTN. The specification of the audio parts are contained in GSM 03.50 [2] (Transmission plan aspects of the speech service in the GSM PLMN system). These aspects are only considered in the GSM 06-series to the extent that the performance of the audio parts affect the performance of the speech transcoder.
+
+# --- 5 Full rate speech transcoding (GSM 06.10)
+
+As shown in figure 1, the speech encoder takes its input as a 13 bit uniform PCM signal either from the audio part of the mobile station or on the network side, from the PSTN via an 8 bit/A-law or  $\mu$ -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function defined in GSM 05.03 to produce an encoded block consisting of 456 bits leading to a gross bit rate of 22,8 kbit/s.
+
+In the receive direction, the inverse operations take place. GSM 06.10 [3] describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format to encoded blocks of 260 bits and from encoded blocks of 260 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to an average bit rate for the encoded bit stream of 13 kbit/s. The coding scheme is the so-called Regular Pulse Excitation - Long Term prediction - Linear Predictive Coder, here-after referred to as RPE-LTP.
+
+The technical specification describes the codec down to the bit level, thus enabling the verification of compliance to the technical specification to a high degree of confidence by use of a set of digital test sequences. These test sequences are also described and are available on floppy disks.
+
+# --- 6 Full rate Discontinuous Transmission (DTX) (GSM 06.31)
+
+During a normal conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes:
+
+- 1) in the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration;
+- 2) the average interference level on the "air" is reduced, leading to better spectrum efficiency.
+
+The overall DTX mechanism is implemented in the DTX handlers (TX and RX) described in GSM 06.31 [6] and requires the following functions which are described in separate technical specifications:
+
+- a Voice Activity Detector on the transmit side;
+- evaluation of the background acoustic noise on the transmit side, in order to transmit characteristic parameters to the receive side;
+- generation on the receive side of a similar noise, called comfort noise, during periods where the radio transmission is cut.
+
+The transmission of comfort noise information to the receive side is achieved by means of a special frame (Silence descriptor = SID). This frame is transmitted at the end of speech bursts and serves as an end of speech marker for the receive side. In order to update the comfort noise characteristics at the receive side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the radio subsystem.
+
+For the overall DTX functionality, the DTX handlers interwork via various flags with the Radio Subsystem, which is in control of the actual transmitter keying on the TX side and which performs various pre-processing functions on the RX side. This is also described in GSM 06.31 [6].
+
+A common terminology used throughout the GSM 06-series of technical specifications is also defined in the present document.
+
+# --- 7 Full rate Voice Activity Detection (VAD) (GSM 06.32)
+
+The input to the VAD is a set of parameters computed by the full-rate speech encoder defined in GSM 06.10 [3]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not. Note that the VAD flag is an input to TX DTX handler and does not control the transmitter keying directly.
+
+The technical specification describes the VAD algorithm down to the bit level. The conventions used in the bit-exact specification are the same as those used in GSM 06.10 [3]. The verification of compliance to the technical specification is achieved by use of digital test sequences applied to the same interface as the test sequences for the speech codec. These test sequences are also described and are available on floppy disks.
+
+# --- 8 Full rate comfort noise insertion (GSM 06.12)
+
+When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise is perceived as very annoying and may reduce the intelligibility of speech if presented to a listener without modification.
+
+This so-called "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent.
+
+GSM 06.12 [5] deals with the detailed aspects of the comfort noise process:
+
+- the evaluation of the acoustic background noise in the transmitter;
+- the noise parameter encoding (SID frames) and decoding;
+- and the generation of comfort noise in the receiver.
+
+The algorithm for updating the noise parameters during speech pauses is also defined.
+
+The comfort noise mechanism is based on the full rate speech codec defined in GSM 06.10 [3].
+
+# --- 9 Full rate lost speech frame substitution and muting (GSM 06.11)
+
+In the receiver, frames may be lost due to transmission errors or frame stealing. GSM 06.11 [4] describes the actions to be taken in these cases, both for lost speech frames and for lost SID-frames in DTX operation.
+
+In order to mask the effect of an isolated lost frame, a scheme is used, where the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several lost frames in a row, some muting technique must be used to indicate to the customer that transmission is interrupted.
+
+# --- 10 Full Rate codec homing (GSM 06.10, optional feature)
+
+A codec homing procedure has been introduced to the GSM Full Rate speech codec as an optional feature.
+
+The GSM Full Rate speech transcoder and VAD algorithm (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exactly in the same state at the beginning of the experiment.
+
+The input test sequences provided in GSM 06.10 [3] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting.
+
+The modules may be set into their home states by provoking the appropriate homing-functions.
+
+NOTE: This is normally done during reset (initialization of the codec).
+
+Special inband signalling frames (encoder-homing-frame and decoder-homing-frame) also described in GSM 06.10 [3] have been defined to provoke these homing-functions also in remotely placed modules.
+
+This mechanism is specified to support three main areas:
+
+- type approval and laboratory test of mobile terminal equipment;
+- type approval and laboratory test of infrastructure equipment;
+- remote control and testing for operation and maintenance.
+
+At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall be rendered into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output.
+
+# --- 11 Speech transmission functions of the half rate traffic channel
+
+The gross bit rate of the half rate speech traffic channel is 11,4 kbit/s. The algorithm for the half rate speech transcoder as well as the associated DTX functions are defined in GSM 06.02 [8], GSM 06.20 [9], GSM 06.21 [10], GSM 06.22 [11], GSM 06.41 [12] and GSM 06.42 [13].
+
+![Figure 1: Overview of audio processing functions. The diagram is split into two main sections: 'Transmit side' and 'Receive side'. The Transmit side shows the flow from BSS side (GSM 06.10) and MS side (GSM 03.50) through a TX DTX handler containing Voice Activity Detector (GSM 06.32), Speech encoder (GSM 06.10), and Comfort noise TX functions (GSM 06.12) to produce VAD, Speech frame, and SID frame outputs, which are then processed by a DTX control and operation block (GSM 06.31) to generate SP flag and Info. bits. The Receive side shows the flow from Info. bits, BFI, SID, and TAF inputs through a DTX control and operation block (GSM 06.31) to produce Speech frame, SID frame, and Comfort noise RX functions (GSM 06.12) outputs, which are then processed by a Speech decoder (GSM 06.10) and Speech frame substitution (GSM 06.11) to produce 13 bit uniform PCM, which is then converted to 8 bit /A- or u-law PCM (GSM 06.10) for the BSS side and D/A and LPF for the MS side (GSM 03.50).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+**Transmit side**
+
+The transmit side shows the flow of audio data from the BSS side (GSM 06.10) and MS side (GSM 03.50) through a TX DTX handler. The BSS side data is processed by an 8 bit /A- or u-law to 13 bit uniform converter (1). The MS side data is processed by an LPF and A/D converter. Both are then processed by a Speech encoder (GSM 06.10) to produce a Speech frame (4). A Voice Activity Detector (GSM 06.32) produces a VAD (3). Comfort noise TX functions (GSM 06.12) produce a SID frame (5). These are then processed by a DTX control and operation block (GSM 06.31) to produce a SP flag (6) and Info. bits (7).
+
+**Receive side**
+
+The receive side shows the flow of audio data from the Info. bits, BFI, SID, and TAF inputs through a DTX control and operation block (GSM 06.31) to produce Speech frame (4), SID frame (5), and Comfort noise RX functions (GSM 06.12) outputs. These are then processed by a Speech decoder (GSM 06.10) and Speech frame substitution (GSM 06.11) to produce 13 bit uniform PCM, which is then converted to 8 bit /A- or u-law PCM (GSM 06.10) for the BSS side and D/A and LPF for the MS side (GSM 03.50).
+
+Figure 1: Overview of audio processing functions. The diagram is split into two main sections: 'Transmit side' and 'Receive side'. The Transmit side shows the flow from BSS side (GSM 06.10) and MS side (GSM 03.50) through a TX DTX handler containing Voice Activity Detector (GSM 06.32), Speech encoder (GSM 06.10), and Comfort noise TX functions (GSM 06.12) to produce VAD, Speech frame, and SID frame outputs, which are then processed by a DTX control and operation block (GSM 06.31) to generate SP flag and Info. bits. The Receive side shows the flow from Info. bits, BFI, SID, and TAF inputs through a DTX control and operation block (GSM 06.31) to produce Speech frame, SID frame, and Comfort noise RX functions (GSM 06.12) outputs, which are then processed by a Speech decoder (GSM 06.10) and Speech frame substitution (GSM 06.11) to produce 13 bit uniform PCM, which is then converted to 8 bit /A- or u-law PCM (GSM 06.10) for the BSS side and D/A and LPF for the MS side (GSM 03.50).
+
+- (1) 8 bit /A- or u-law (PCS 1900) PCM (ITU-T rec G.711)
+- (2) 13 bit uniform PCM, 8000 samples/s
+- (3) Voice activity flag
+- (4) Encoded speech frame, 50 samples/s, 260 bits/frame
+- (5) Silence Descriptor (SID) frame, 260 bits/frame
+- (6) Speech flag, indicates whether information bits are speech or SID information
+- (7) Information bits delivered to the radio subsystem
+- (8) Information bits received from the radio subsystem
+- (9) Bad Frame Indication (BFI) flag
+- (10) Silence Descriptor (SID) flag
+- (11) Time Alignment Flag (TAF), marks the position of the SID frame within the SACCH multiframe
+
+**Figure 1: Overview of audio processing functions**
+
+# Annex A (informative): Change History
+
+| Change history |                  |              |                 |             |                                                                           |
+|----------------|------------------|--------------|-----------------|-------------|---------------------------------------------------------------------------|
+| SMG No.        | TDoc. No.        | CR. No.      | Clause affected | New version | Subject/Comments                                                          |
+| SMG#07         |                  |              |                 | 4.0.5       | ETSI Publication                                                          |
+| SMG#20         |                  |              |                 | 5.0.1       | Release 1996 version                                                      |
+| SMG#23         | 97-737<br>97-741 | A004<br>A005 |                 | 5.1.0       | UAP61 comments<br>Introduction of Homing for Full Rate Speech Transcoding |
+| SMG#23         |                  |              |                 | 5.1.1       | ETSI version change                                                       |
+| SMG#27         |                  |              |                 | 6.0.0       | Release 1997 version                                                      |
+| SMG#28         | P-99-136         | A006         | 5 and Figure 1  | 7.0.0       | Addition of mu-law (PCS 1900)                                             |
+|                |                  |              |                 | 7.0.2       | Update to Version 7.0.2 for Publication                                   |
+| SMG#31         |                  |              |                 | 8.0.0       | Version for Release 1999                                                  |
+|                |                  |              |                 | 8.0.1       | Update to Version 8.0.1 for Publication                                   |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46002/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/46_series/46002/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ea11cad30df19cd7f15e36da25985f34a876be38
--- /dev/null
+++ b/marked/Rel-16/46_series/46002/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c04f810103a3615a81d55e7a7b45b76c9fc4617959ef910fb6619f5533afb665
+size 159828
diff --git a/marked/Rel-16/46_series/46002/raw.md b/marked/Rel-16/46_series/46002/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..41e1eae7e138d066fc52d357d2b4ddf0301a6b05
--- /dev/null
+++ b/marked/Rel-16/46_series/46002/raw.md
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                            |    |
+|------------------------------------------------------------|----|
+| Foreword .....                                             | 4  |
+| 1 Scope.....                                               | 5  |
+| 2 References.....                                          | 5  |
+| 3 Definitions and abbreviations .....                      | 5  |
+| 3.1 Definitions.....                                       | 5  |
+| 3.2 Abbreviations .....                                    | 6  |
+| 4 General.....                                             | 6  |
+| 5 Half rate speech transcoding.....                        | 8  |
+| 6 Half rate Discontinuous Transmission (DTX).....          | 8  |
+| 7 Half rate Voice Activity Detection (VAD).....            | 9  |
+| 8 Half rate comfort noise insertion .....                  | 9  |
+| 9 Half rate lost speech frame substitution and muting..... | 9  |
+| 10 Half rate codec homing.....                             | 10 |
+| Annex A (informative): Change History.....                 | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+The present document gives a general overview of the half rate speech traffic channels speech processing functions for the digital cellular telecommunications system. The present document is part of ENs' series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".**
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+
+# --- 1 Scope
+
+The present document is an introduction to GSM 06.20 [4], GSM 06.21 [5], GSM 06.22 [6], GSM 06.41 [7] and GSM 06.42 [8] TSs dealing with the speech processing functions in the half-rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the TSs where each function is specified in detail.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 03.50: "Digital cellular telecommunication system (Phase 2+); Transmission planning aspects of the speech services in the GSM Public Land Mobile Network (PLMN) system".
+- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [4] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech: Half rate speech transcoding".
+- [5] GSM 06.21: " Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels".
+- [6] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels ".
+- [7] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous transmission (DTX) for half rate speech traffic channels".
+- [8] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels ".
+- [9] ITU-T Recommendation G.711: "Pulse Code Modulation (PCM) of voice frequencies".
+- [10] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- [11] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.20 [4], GSM 06.21 [5], GSM 06.22 [6], GSM 06.41 [7] and GSM 06.42 [8].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply.
+
+|         |                                         |
+|---------|-----------------------------------------|
+| BFI     | Bad Frame Indication                    |
+| BSS     | Base Station System                     |
+| DTX     | Discontinuous Transmission              |
+| GSM     | Global System for Mobile communications |
+| MS      | Mobile Station                          |
+| PCM     | Pulse Code Modulated                    |
+| PLMN    | Public Land Mobile Network              |
+| PSTN    | Public Switched Telephone Network       |
+| RF      | Radio Frequency                         |
+| RX      | Receive                                 |
+| RSS     | Radio SubSystem                         |
+| SACCH   | Slow Associated Control CHannel         |
+| SID     | SIlence Descriptor                      |
+| SP flag | SPeech flag                             |
+| TAF     | Time Alignment Flag                     |
+| TX      | Transmit                                |
+| VSELP   | Vector Sum Excited Linear Predictor     |
+| UFI     | Unreliable Frame Indication             |
+
+For abbreviations not given in this subclause, see GSM 01.04 [1].
+
+# --- 4 General
+
+Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant documents for each function are also indicated.
+
+In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included, to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface of the Public Switched Telephone Network (PSTN). The detailed specification of the audio parts are contained in GSM 03.50 [2]. These aspects are only considered to the extent that the performance of the audio parts affect the performance of the speech transcoder.
+
+![Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between the Transmit Side (TX) and the Receive Side (RX). On the TX side, audio from BSS (GSM 06.02) and MS (GSM 03.50) is converted to 13-bit uniform PCM (point 2). This is processed by a TX DTX handler (GSM 06.41) which includes a Voice Activity Detector (VAD, point 3), a Speech encoder (GSM 06.20, point 4), and Comfort noise TX functions (GSM 06.22, point 5). The DTX handler outputs a VAD flag (point 3), a Speech frame (point 4), a SID frame (point 5), an SP flag (point 6), and info. bits (point 7). On the RX side, the RX DTX handler (GSM 06.41) receives Info bits (point 8), BFI (point 9), SID (point 10), TAF (point 11), and UFI (point 12). It controls a Speech frame substitution (GSM 06.21), a speech decoder (GSM 06.20, point 4), and Comfort noise RX functions (GSM 06.22, point 5). The decoded audio is then converted back to 8-bit A-law (GSM 06.02) for BSS and D/A + LPF (GSM 03.50) for MS (point 2).](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between the Transmit Side (TX) and the Receive Side (RX). On the TX side, audio from BSS (GSM 06.02) and MS (GSM 03.50) is converted to 13-bit uniform PCM (point 2). This is processed by a TX DTX handler (GSM 06.41) which includes a Voice Activity Detector (VAD, point 3), a Speech encoder (GSM 06.20, point 4), and Comfort noise TX functions (GSM 06.22, point 5). The DTX handler outputs a VAD flag (point 3), a Speech frame (point 4), a SID frame (point 5), an SP flag (point 6), and info. bits (point 7). On the RX side, the RX DTX handler (GSM 06.41) receives Info bits (point 8), BFI (point 9), SID (point 10), TAF (point 11), and UFI (point 12). It controls a Speech frame substitution (GSM 06.21), a speech decoder (GSM 06.20, point 4), and Comfort noise RX functions (GSM 06.22, point 5). The decoded audio is then converted back to 8-bit A-law (GSM 06.02) for BSS and D/A + LPF (GSM 03.50) for MS (point 2).
+
+- 1 8 bit /A-law or  $\mu$ -law (PCS 1900) PCM (ITU-T Recommendation G.711) [9], 8 000 samples/s.
+- 2 13 bit uniform PCM, 8 000 samples/s.
+- 3 Voice Activity Detector (VAD) flag.
+- 4 Encoded speech frame, 50 frames/s, 112 bits/frame.
+- 5 Silence Descriptor (SID) frame, 112 bits/frame.
+- 6 SPeech (SP) flag, indicates whether information bits are speech or SID information.
+- 7 Information bits delivered to the radio subsystem.
+- 8 Information bits received from the radio subsystem.
+- 9 Bad Frame Indication (BFI) flag.
+- 10 Silence Descriptor (SID) flag.
+- 11 Time Alignment Flag (TAF), marks the position of the SID frame within the Slow Associated Control CHannel (SACCH) multiframe.
+- 12 Unreliable Frame Indication (UFI).
+
+**Figure 1: Overview of audio processing functions**
+
+# --- 5 Half rate speech transcoding
+
+The half rate speech transcoding function is described in GSM 06.20 [4].
+
+As shown in figure 1, the speech encoder takes its input as a 13 bit uniform Pulse Code Modulated (PCM) signal either from the audio part of the MS or on the network side, from the PSTN via an 8 bit/A-law or  $\mu$ -law (PCS 1900) to 13 bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function as defined in GSM 05.03 [3] to produce an encoded block consisting of 228 bits leading to a gross bit rate of 11,4 kbit/s.
+
+In the RX direction, the inverse operations take place.
+
+GSM 06.20 [4] describes the detailed mapping between input blocks of 160 speech samples in 13 bit uniform PCM format into encoded blocks of 112 bits and from encoded blocks of 112 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to an average bit rate for the encoded bit stream of 5,6 kbit/s. The coding scheme is called Vector Sum Excited Linear Prediction (VSELP) coding.
+
+GSM 06.20 [4] describes the codec and GSM 06.06 [11] defines the C code, thus enabling the verification of compliance to GSM 06.20 [4] to a high degree of confidence by use of a set of digital test sequences given in GSM 06.07 [10].
+
+# --- 6 Half rate Discontinuous Transmission (DTX)
+
+The half rate discontinuous transmission function is described in GSM 06.41 [7].
+
+During a normal conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous Transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes:
+
+- 1) in the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration;
+- 2) the average interference level over the air interface is reduced, leading to better Radio Frequency (RF) spectrum efficiency.
+
+The overall DTX mechanism is implemented in the DTX handlers (Transmit (TX) and Receive (RX)) described in GSM 06.41 [7] and requires the following functions:
+
+- a Voice Activity Detector (VAD) on the TX side, see GSM 06.42 [8];
+- evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side, see GSM 06.22 [6];
+- generation of comfort noise on the RX side during periods where the radio transmission is turned off, see GSM 06.22 [6].
+
+The transmission of comfort noise information to the RX side is achieved by means of a SIlence Descriptor (SID) frame. The SID frame is transmitted at the end of speech bursts and serves as an end of speech marker for the RX side. In order to update the comfort noise characteristics at the RX side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the Radio SubSystem (RSS).
+
+The DTX handlers interwork with the RSS using flags. The RSS is controlled by the transmitter keying on the TX side, which performs pre-processing functions on the RX side. This is described in GSM 06.41 [7].
+
+The speech flag (SP) indicates whether information bits are speech or SID information. The SP flag is calculated from the VAD flag by the TX DTX handler. When SID information is transmitted (SP="0") the operation of the speech encoder is modified to reduce the remaining computation for that frame. This is described in GSM 06.22 [6].
+
+# --- 7 Half rate Voice Activity Detection (VAD)
+
+The half rate VAD function is described in GSM 06.42 [8].
+
+The input to the VAD is a set of parameters computed by the half-rate speech encoder defined in GSM 06.20 [4]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not.
+
+NOTE: The VAD flag is an input to TX DTX handler and does not control the transmitter keying directly.
+
+GSM 06.42 [8] describes the VAD algorithm and GSM 06.06 [11] defines the C code. The verification of compliance to GSM 06.42 [8] is achieved by use of digital test sequences (see GSM 06.07 [10]) applied to the same interface as the test sequences for the speech codec.
+
+# --- 8 Half rate comfort noise insertion
+
+The half rate noise comfort insertion function is described in GSM 06.22 [6].
+
+When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end, if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise may be perceived as annoying and reduce the intelligibility of speech, if presented to a listener without modification.
+
+This "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent.
+
+The comfort noise processes are as follows:
+
+- the evaluation of the acoustic background noise in the transmitter;
+- the noise parameter encoding (SID frames) and decoding;
+- and the generation of comfort noise in the receiver.
+
+The comfort noise processes and the algorithm for updating the noise parameters during speech pauses are defined in detail in GSM 06.22 [6].
+
+The comfort noise mechanism is based on the half rate speech codec defined in GSM 06.20 [4].
+
+# --- 9 Half rate lost speech frame substitution and muting
+
+The half rate speech frame substitution and muting function is described in GSM 06.21 [5].
+
+In the receiver, frames may be lost due to transmission errors or frame stealing.
+
+GSM 06.21 [5] describes the actions to be taken in these cases, both for lost speech frames and for lost SID frames in DTX operation.
+
+In order to mask the effect of an isolated lost frame, the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several subsequent lost frames, a muting technique shall be used to indicate to the listener that transmission has been interrupted.
+
+# --- 10 Half rate codec homing
+
+The GSM half rate speech transcoder, VAD, DTX system and comfort noise parts of the audio processing functions (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exact in the same state at the beginning of the experiment.
+
+The input test sequences provided in GSM 06.07 [10] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting.
+
+The modules may be set into their home states by provoking the appropriate homing-functions.
+
+NOTE: This is normally done during reset.
+
+Special inband signalling frames (encoder-homing-frame and decoder-homing-frame described in GSM 06.20 [4]) have been defined to provoke these homing-functions also in remotely placed modules.
+
+This mechanism is specified to support three main areas:
+
+- type approval of mobile terminal equipment;
+- type approval of infrastructure equipment;
+- remote control and testing for operation and maintenance.
+
+At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall go into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output.
+
+# Annex A (informative): Change History
+
+| Change history |           |         |                        |             |                                         |
+|----------------|-----------|---------|------------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected       | New version | Subject/Comments                        |
+| SMG#13         |           |         |                        | 4.0.2       | ETSI Publication                        |
+| SMG#20         |           |         |                        | 5.0.1       | Release 1996 version                    |
+| SMG#27         |           |         |                        | 6.0.0       | Release 1997 version                    |
+| SMG#28         | P-99-137  | A001    | 5 and caption Figure 1 | 7.0.0       | Addition of mu-law (PCS 1900)           |
+|                |           |         |                        | 7.0.2       | Update to Version 7.0.2 for Publication |
+| SMG#31         |           |         |                        | 8.0.0       | Version for Release 1999                |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46006/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46006/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7d09965d3951412accde8059240cbc2966d8a9cf
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f55ee77c9c2dc5063f6192073d30b904a8d4fcee751027ebde810fd4fdd88138
+size 44348
diff --git a/marked/Rel-16/46_series/46006/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/46_series/46006/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e487fbd53d7f263e5b3ff78e1cb60f2f445b1367
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ebe2c003817d8fdb1478ffb25503ad04ca943833f4d4b947d372b86daff584fd
+size 77144
diff --git a/marked/Rel-16/46_series/46006/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/46_series/46006/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6fb38f104280cf6d18a6bc148d8c57288e3279da
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1838102f460a39b9a6f11bffc1b8599c9ab6d053e251cfa7e59647aa18749acc
+size 59902
diff --git a/marked/Rel-16/46_series/46006/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46006/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e25fe88a696ec07fe3c095d42ca7063935cf309d
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7b8bcf3daf4f2dd8c3cce7cfc337301fe32ceddc013036477bbb6cca624407d9
+size 98129
diff --git a/marked/Rel-16/46_series/46006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/46_series/46006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ccde662d897b5ccd554c314d6f23f54381c5a2f
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55e08754c9e43d540d63e108a588286d87fd39322cd1b399edd09ab376652189
+size 55984
diff --git a/marked/Rel-16/46_series/46006/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/46_series/46006/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0b42a3a4c7daefcd0b93265e8600e80e082a9c8b
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b7ade28dbdd5c2f2aed641a3b0a30e03c3ff5f573f90715321e9f1d82654ea04
+size 156495
diff --git a/marked/Rel-16/46_series/46006/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/46_series/46006/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7036fa430b54728031a9683f43413f3e3ec413aa
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8c0083b1c885a15e7159d8d5295348844b72163696a74ef5043168c67b66f96a
+size 65645
diff --git a/marked/Rel-16/46_series/46006/raw.md b/marked/Rel-16/46_series/46006/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2be19a375fae2e173105327cb7d548089c7f983
--- /dev/null
+++ b/marked/Rel-16/46_series/46006/raw.md
@@ -0,0 +1,282 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                        |    |
+|--------------------------------------------------------|----|
+| Foreword .....                                         | 4  |
+| 1 Scope.....                                           | 5  |
+| 2 References.....                                      | 5  |
+| 3 Definitions and abbreviations .....                  | 5  |
+| 3.1 Definitions.....                                   | 5  |
+| 3.2 Abbreviations .....                                | 6  |
+| 4 C code structure .....                               | 6  |
+| 4.1 Directory structure.....                           | 6  |
+| 4.2 Program execution.....                             | 7  |
+| 4.3 Code hierarchy .....                               | 7  |
+| 5 ANSI-C code for the GSM half rate speech codec ..... | 12 |
+| Annex A (informative): Change History.....             | 13 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+The present document specifies the half rate speech traffic channels for the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".**
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+# --- 1 Scope
+
+The present document contains an electronic copy of the ANSI-C code for the GSM half rate codec. The ANSI-C code is necessary for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]), Discontinuous Transmission (GSM 06.41 [5]) and example solutions for substituting and muting of lost frames (GSM 06.21 [3]).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [3] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels".
+- [4] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- [5] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [6] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- [7] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- [8] American National Standards Institute ANSI 9899 (1990): "Programming Language - C (ISO)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.20 [2], GSM 06.21 [3], GSM 06.22 [4], GSM 06.41 [5] and GSM 06.42 [6].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                         |
+|-------|-----------------------------------------|
+| ANSI  | American National Standards Institute   |
+| DS-HD | Double Sided High Density               |
+| ETS   | European Telecommunication Standard     |
+| GSM   | Global System for Mobile communications |
+| I/O   | Input/Output                            |
+
+ROM                    Read Only Memory
+
+For abbreviations not given in this clause, see GSM 01.04 [1].
+
+# 4 C code structure
+
+This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the electronic attachment accompanying the present document.
+
+The C code has been verified on the following systems:
+
+- Sun Microsystems's <sup>1)</sup> workstations and Sun Microsystems acc;
+- IBM <sup>2)</sup> PC/AT compatible computers and Borlands Turbo-C <sup>3)</sup> compiler;
+- VAX <sup>4)</sup> and Digital Equipment Corporations CC.
+
+ANSI-C 9899 [8] was selected as the programming language because portability was desirable.
+
+The code representation is contained in a MS-DOS <sup>5)</sup> file (called Disk and contained in archive en\_300967v080001p0.ZIP which accompanies the present document.
+
+## 4.1 Directory structure
+
+A listing of the directories is given in table 1.
+
+**Table 1: Directory structure listing**
+
+| Directory name | Contents                                   | Size (bytes) |
+|----------------|--------------------------------------------|--------------|
+| \c             | C files and headers                        | 1 215 563    |
+| \d             | example binary data input and output files | 72 400       |
+| \exec          | executables and makefiles                  | 5 509        |
+| \utils         | utility programs and the "reid" program    | 49 531       |
+| readme.txt     | usage description of files                 | 9 116        |
+
+The C code file (called Disk and contained in archive en\_300967v080001p0.ZIP) which accompanies the present document has one main directory and four subdirectories. The top directory has in it the file readme.txt which explains the installation procedure, along with some miscellaneous descriptive information regarding the code.
+
+Below this directory, are the four subdirectories. The "c" subdirectory contains all the source code and header files. This directory alone is essential, the others aid in the building, or testing of the code. All ROM data is in this source directory. After installation, this directory can be made read only.
+
+The "d" subdirectory contains all the speech coder installation verification data files. All of the data files are written/read as 16 bit words, so these may require byte swapping on the target platform. All data and text files are formatted such that they are correct for an IBM PC/AT compatible.
+
+Final verification is to be performed using the GSM half rate test sequences described in GSM 06.07 [7].
+
+<sup>1)</sup> ) Registered trade mark of Sun Microsystems
+
+<sup>2)</sup> ) Registered trade mark of International Business Machines
+
+<sup>3)</sup> ) Registered trade mark of Borland
+
+<sup>4)</sup> ) Registered trade mark of Digital Equipment Corporation
+
+<sup>5)</sup> ) Registered trade mark of Microsoft
+
+The "utils" subdirectory contains miscellaneous utilities which may be useful in the installation of the software. Two programs are provided to transform text files: topcwild and tosnwild. The program topcwild takes UNIX text files and converts them to pc text files. tosnwild does the opposite. The program swapbin is also in this directory. This performs byte swapping on a binary data file. A fourth program, reid, is also contained in this sub directory. This is the residual error insertion program which also provides the format conversion between the encoder output file format and the decoder input file format.
+
+The "exec" subdirectory contains the makefiles for the various platforms. Once the software is installed, this directory will have a compiled version of gsm\_hr (the bit-exact C executable), programs from the "utils" directory, and all the object files.
+
+The program gsm\_hr is the name of the GSM half rate codec executable file.
+
+## 4.2 Program execution
+
+The GSM half rate speech codec is implemented as two separate programs:
+
+- (gsm\_hr) speech codec;
+- (reid) encoder/decoder interface.
+
+The gsm\_hr program operates in one of two modes:
+
+- (0) encoding only;
+- (1) decoding only.
+
+For encoding, the input is a binary speech file (\*.inp) and the output is a binary encoded parameter file (\*.cod). For decoding, the input is a binary parameter files (\*.dec) and the output is a binary synthesized speech file (\*.out). Note that the format for the parameter input file required for decoding (\*.dec) is not the same as the format of the parameter output file generated by encoding (\*.cod). The reid program will translate an \*.cod file into an \*.dec file (select error-free mode, EP0).
+
+See the file readme.txt for more information on how to run the gsm\_hr and reid programs.
+
+## 4.3 Code hierarchy
+
+Figures 1 to 7 are call graphs that show the functions used in the speech codec.
+
+The encode call graph is broken down into six separate call graphs. Those clauses, which are large, are separated from the primary encode call tree and given their own call tree. Each vertical column represents a call level. For example, main() is at level 0, encode() at level 1, speechEncoder() at level 2, openLoopLagSearch() at level 3, getCCThreshold() at level 4, etc. The basic operations are not counted as extending the depth, therefore the deepest level in this software is level 6.
+
+Some items have been omitted from this call graph. All standard C functions: printf(), fwrite(), etc. have been omitted. Also, no basic operations (add(), L\_add(), mac(), etc.) or double precision extended operations (e.g. L\_mpy\_ls()) appear in the graphs.
+
+![Speech decoder call graph showing the hierarchy of functions starting from 'main' and 'decode' leading to 'speechDecoder' and its sub-functions.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+The call graph illustrates the execution flow of a speech decoder. It begins with 'main' and 'decode' pointing to 'speechDecoder'. 'speechDecoder' branches into 'speechDecoderHostInterface', 'readDecfile', 'decoderHomingFrameTest', and 'resetDec'. 'resetDec' further points to 'decoderReset' and 'dtxResetRx'. The central part of the graph shows 'speechDecoder' calling numerous sub-functions: 'level\_estimator', 'spectralPostFilter', 'signal\_conceal\_sub', 'pitchPreFilt', 'scaleExcite', 'is\_mNs', 'is\_r', 'v\_con', 'b\_con', 'fp\_ex', 'lagDecode', 'r0BasedEnergyShft', 'getSfmLpc', 'a\_sst', 'rxInterpR0Lpc', 'getPnBits', 'gsQuant', 'avgGsHistQtz', 'lookupVq', and 'para\_conceal\_speech\_decoder'. These sub-functions further call other internal functions: 'level\_estimator' calls 'level\_calc'; 'spectralPostFilter', 'signal\_conceal\_sub', 'pitchPreFilt', and 'scaleExcite' all call 'ageGain', 'lpclir', and 'lpcFir'; 'is\_mNs' calls 'g\_corr1s'; 'is\_r' calls 'get\_ipij' and 'g\_corr1'; 'lagDecode' calls 'interpolateCheck'; 'r0BasedEnergyShft' calls 'reToADp'; 'a\_sst' calls 'aFlatRcDp', 'reToConDpL', 'linInterpSid', and 'linInterpSidShort'; 'rxInterpR0Lpc' calls 'reToADp', 'aFlatRcDp', 'reToConDpL', 'linInterpSid', and 'linInterpSidShort'. Finally, 'interpolateCheck' calls 'res\_eng' and 'aToRc', which both then call 'sqrtot'.
+
+Speech decoder call graph showing the hierarchy of functions starting from 'main' and 'decode' leading to 'speechDecoder' and its sub-functions.
+
+Figure 1: Speech decoder call graph
+
+![Speech encoder call graph showing the hierarchy of function calls starting from main to encode, then branching into various sub-functions like writeEncfile, speechEncoder, hostEncoderInterface, resetEnc, encoderHomingFrameTest, fillBitAlloc, sfmAnalysis, periodicity_update, openLoopLagSearch, weightSpeechFrame, getSfmLpcTx, rcToADp, aFlatRcDp, g_corr1, lpcZsLirP, lpcZsFir, lpcRzSliR, aflat, filt4_2nd, iir_d, lpclr, compResidEnergy, interpolateCheck, lpcFir, res_eng, sqroot, and aToRc.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+```
+graph LR; main --> encode; encode --> writeEncfile; encode --> speechEncoder; encode --> hostEncoderInterface; encode --> resetEnc; encode --> encoderHomingFrameTest; speechEncoder --> fillBitAlloc; speechEncoder --> sfmAnalysis; speechEncoder --> periodicity_update; speechEncoder --> openLoopLagSearch; speechEncoder --> weightSpeechFrame; speechEncoder --> getSfmLpcTx; speechEncoder --> rcToADp; speechEncoder --> aFlatRcDp; speechEncoder --> g_corr1; speechEncoder --> lpcZsLirP; speechEncoder --> lpcZsFir; speechEncoder --> lpcRzSliR; speechEncoder --> aflat; speechEncoder --> filt4_2nd; resetEnc --> encoderReset; resetEnc --> vad_reset; resetEnc --> dtxResetTx; getSfmLpcTx --> lpclr; getSfmLpcTx --> compResidEnergy; getSfmLpcTx --> interpolateCheck; getSfmLpcTx --> lpcFir; getSfmLpcTx --> res_eng; res_eng --> sqroot; aFlatRcDp --> aToRc; filt4_2nd --> iir_d;
+```
+
+Speech encoder call graph showing the hierarchy of function calls starting from main to encode, then branching into various sub-functions like writeEncfile, speechEncoder, hostEncoderInterface, resetEnc, encoderHomingFrameTest, fillBitAlloc, sfmAnalysis, periodicity\_update, openLoopLagSearch, weightSpeechFrame, getSfmLpcTx, rcToADp, aFlatRcDp, g\_corr1, lpcZsLirP, lpcZsFir, lpcRzSliR, aflat, filt4\_2nd, iir\_d, lpclr, compResidEnergy, interpolateCheck, lpcFir, res\_eng, sqroot, and aToRc.
+
+Figure 2: Speech encoder call graph
+
+![Speech encoder LPC quantization call graph](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+graph LR; aflat --> aflatNewBarRecursionL; aflat --> getNextVec; aflat --> setupQuant; aflat --> findBestInQuantList; aflat --> aflatRecursion; aflat --> setupPreQ; aflat --> initPBarVBarL; aflat --> initPBarFullVBarFullL; aflat --> swComfortNoise; aflat --> vad_algorithm; aflat --> rcToCorrDpL; aflat --> flat; flat --> r0Quant; flat --> sqroot; flat --> cov32;
+```
+
+This call graph shows the function 'aflat' at the root, which branches out to 11 other functions. The functions are: aflatNewBarRecursionL, getNextVec, setupQuant, findBestInQuantList, aflatRecursion, setupPreQ, initPBarVBarL, initPBarFullVBarFullL, swComfortNoise, vad\_algorithm, and rcToCorrDpL. The function 'rcToCorrDpL' further branches to a function 'flat', which in turn branches to three functions: r0Quant, sqroot, and cov32.
+
+Speech encoder LPC quantization call graph
+
+Figure 3: Speech encoder LPC quantization call graph
+
+![Speech encoder open-loop lag search call graph](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg)
+
+```
+graph LR; openLoopLagSearch --> bestDelta; openLoopLagSearch --> pitchLags; openLoopLagSearch --> getCCThreshold; openLoopLagSearch --> r0BasedEnergyShft; openLoopLagSearch --> g_corr1s; bestDelta --> maxCCOverGWithSign; bestDelta --> get_ipjj; pitchLags --> quantLag; pitchLags --> GCInterp; pitchLags --> CGInterpValid; pitchLags --> findPeak; getCCThreshold --> fnExp2; getCCThreshold --> fnLog2; r0BasedEnergyShft --> fnBest_CG;
+```
+
+This call graph shows the function 'openLoopLagSearch' at the root, which branches out to five functions: bestDelta, pitchLags, getCCThreshold, r0BasedEnergyShft, and g\_corr1s. The function 'bestDelta' branches to two functions: maxCCOverGWithSign and get\_ipjj. The function 'pitchLags' branches to four functions: quantLag, GCInterp, CGInterpValid, and findPeak. The function 'getCCThreshold' branches to two functions: fnExp2 and fnLog2. The function 'r0BasedEnergyShft' branches to one function: fnBest\_CG.
+
+Speech encoder open-loop lag search call graph
+
+Figure 4: Speech encoder open-loop lag search call graph
+
+![Speech encoder subframe processing call graph](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+This call graph illustrates the subframe processing within a speech encoder. The root node, **sfmrAnalysis**, initiates a series of calls to various processing blocks. These include **lpcIir**, **scaleExcite**, **g\_quant\_vl**, **rs\_rrNs**, **hnwFilt**, **v\_con**, **b\_con**, **v\_srch**, **decorr**, **closedLoopLagSearch**, and **lpcZiIir**. Further sub-calls include **gainTweak**, **g\_corr1**, **g\_corr2**, **lpcZsIir**, **sqroot**, **get\_ipjj**, **fp\_ex**, **quantLag**, and **maxCCOverGWithSign**.
+
+Speech encoder subframe processing call graph
+
+Figure 5: Speech encoder subframe processing call graph
+
+![Comfort noise call graph](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+This call graph shows the processing flow for comfort noise. The root node, **swComfortNoise**, calls several functions: **getPnBits**, **lpcCorrQntz**, **r0Quant**, **avgCNHist**, **gsQuant**, **avgGsHistQntz**, and **updateCNHist**. The **lpcCorrQntz** function further calls **aflatNewBarRecursionL**, **getNextVec**, **setupQuant**, **findBestInQuantList**, **aflatRecursion**, **setupPreQ**, **initPBarVBarL**, and **initPBarFullVBarFullL**.
+
+Comfort noise call graph
+
+Figure 6: Comfort noise call graph
+
+![Voice Activity Detector (VAD) call graph](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph LR; vad_algorithm[vad_algorithm] --> vad_hangover[vad_hangover]; vad_algorithm --> vad_decision[vad_decision]; vad_algorithm --> threshold_adaptation[threshold_adaptation]; vad_algorithm --> tone_detection[tone_detection]; vad_algorithm --> spectral_comparison[spectral_comparison]; vad_algorithm --> predictor_values[predictor_values]; vad_algorithm --> average_acf[average_acf]; vad_algorithm --> energy_computation[energy_computation]; tone_detection --> step_up[step_up]; predictor_values --> compute_rav1[compute_rav1]; predictor_values --> schur_recursion[schur_recursion];
+```
+
+The diagram illustrates the call graph for the Voice Activity Detector (VAD) algorithm. The central node is `vad_algorithm`, which branches out to eight sub-functions: `vad_hangover`, `vad_decision`, `threshold_adaptation`, `tone_detection`, `spectral_comparison`, `predictor_values`, `average_acf`, and `energy_computation`. Further, `tone_detection` calls `step_up`, and `predictor_values` calls `compute_rav1` and `schur_recursion`.
+
+Voice Activity Detector (VAD) call graph
+
+**Figure 7: Voice Activity Detector (VAD) call graph**
+
+# --- 5 ANSI-C code for the GSM half rate speech codec
+
+NOTE: This clause is contained in archive en\_300967v080001p0.ZIP which accompanies the present document.
+
+# Annex A (informative): Change History
+
+| Change history |                  |              |                  |             |                                                           |
+|----------------|------------------|--------------|------------------|-------------|-----------------------------------------------------------|
+| SMG No.        | TDoc. No.        | CR. No.      | Section affected | New version | Subject/Comments                                          |
+| SMG#16         |                  |              |                  | 4.0.3       | ETSI Publication                                          |
+| SMG#17         | 332/95<br>119/96 | A001<br>A002 |                  | 4.1.0       | HR C-code<br>GSM half rate Codec Homing Procedure         |
+| SMG#23         | 97-737           | A002         |                  | 4.1.1       | UAP60 and Supplementary notes on 06.06 Call Graph Changes |
+| SMG#20         |                  |              |                  | 5.0.0       | Release 1996 version                                      |
+| SMG#20         |                  |              |                  | 5.0.1       | ETSI version change                                       |
+| SMG#22         | 430/97           | A002         |                  | 5.1.0       | UAP 60                                                    |
+| SMG#23         | 97-737           | A003         |                  | 5.1.1       | UAP60 and Supplementary notes on 06.06 Call Graph Changes |
+| SMG#27         |                  |              |                  | 6.0.0       | Release 1997 version                                      |
+| SMG#28         |                  |              |                  | 6.0.1       | ETSI Publication                                          |
+| SMG#29         |                  |              |                  | 7.0.0       | Release 1998 version                                      |
+|                |                  |              |                  | 7.0.1       | Version update to 7.0.1 for Publication                   |
+| SMG#31         |                  |              |                  | 8.0.0       | Release 1999 version                                      |
+|                |                  |              |                  | 8.0.1       | Update to Version 8.0.1 for Publication                   |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46007/raw.md b/marked/Rel-16/46_series/46007/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..664a26eb175e8bf08809e45e044abd764e2aeb44
--- /dev/null
+++ b/marked/Rel-16/46_series/46007/raw.md
@@ -0,0 +1,512 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                    |    |
+|------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                     | 4  |
+| 1 Scope.....                                                                       | 6  |
+| 2 References.....                                                                  | 6  |
+| 3 Definitions and abbreviations .....                                              | 6  |
+| 3.1 Definitions.....                                                               | 6  |
+| 3.2 Abbreviations .....                                                            | 7  |
+| 4 General.....                                                                     | 7  |
+| 5 Test sequence format .....                                                       | 7  |
+| 5.1 File format.....                                                               | 7  |
+| 5.2 Codec homing .....                                                             | 8  |
+| 6 Speech codec test sequences.....                                                 | 8  |
+| 6.1 Codec configuration.....                                                       | 8  |
+| 6.2 Speech codec test sequences .....                                              | 9  |
+| 6.2.1 Speech encoder test sequences .....                                          | 9  |
+| 6.2.2 Speech decoder test sequences .....                                          | 9  |
+| 6.2.3 Codec homing sequence .....                                                  | 9  |
+| 7 DTX test sequences.....                                                          | 10 |
+| 7.1 Codec configuration .....                                                      | 10 |
+| 7.2 DTX test sequences.....                                                        | 10 |
+| 7.2.1 Predictor values computation .....                                           | 10 |
+| 7.2.2 Spectral comparison .....                                                    | 11 |
+| 7.2.3 Threshold adaptation .....                                                   | 11 |
+| 7.2.4 Periodicity detection.....                                                   | 11 |
+| 7.2.5 Tone detection .....                                                         | 11 |
+| 7.2.6 Safety and initialization .....                                              | 11 |
+| 7.2.7 Comfort noise test sequence.....                                             | 11 |
+| 7.2.8 Real speech and tones.....                                                   | 11 |
+| 8 Sequences for finding the 20 ms framing of the GSM half rate speech encoder..... | 12 |
+| 8.1 Bit synchronization .....                                                      | 12 |
+| 8.2 Frame synchronization .....                                                    | 12 |
+| 8.3 Formats and sizes of the synchronization sequences .....                       | 13 |
+| 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences .....               | 14 |
+| 10 Test sequences for the GSM half rate speech codec .....                         | 15 |
+| Annex A (informative): Change history.....                                         | 16 |
+
+# Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+An electronic attachment accompanies the present document, containing test sequences for a bit exact implementation of the half rate speech transcoder.
+
+Archive en\_300968v080001p0.ZIP which accompanies the present document contains compressed files which are labelled as follows:
+
+- Disks24.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 2 and 4 (GSM 06.07).
+- Disks135.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 1, 3 and 5 (GSM 06.07).
+- Disks6A.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 6 and 10 (GSM 06.07).
+- Disks7B.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 7 and 11 (GSM 06.07).
+- Disks89.zip Clause 10: Test sequences for the GSM half rate speech codec; Disks 8 and 9 (GSM 06.07).
+
+The present document specifies the half rate speech traffic channels for the Digital cellular telecommunications system.
+
+The present document specifies the digital test sequences for the GSM half rate speech codec for the digital cellular telecommunications system. The present document, is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".**
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+
+GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the digital test sequences for the GSM half rate speech codec. These sequences test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific
+
+- For a specific reference, subsequent revisions do not apply.
+
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [3] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels".
+- [4] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- [5] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [6] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- [7] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- [8] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech coding functions".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.20 [2], GSM 06.21 [3], GSM 06.22 [4], GSM 06.41 [5] and GSM 06.42 [6].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                                         |
+|-----|-----------------------------------------|
+| ETS | European Telecommunication Standard     |
+| GSM | Global System for Mobile communications |
+
+For abbreviations not given in this clause, see GSM 01.04 [1].
+
+# --- 4 General
+
+Digital test sequences are necessary to test for a bit exact implementation of the half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]).
+
+The test sequences may also be used to verify installations of the ANSI C code in GSM 06.06 [7].
+
+Clause 5 describes the format of the files which contain the digital test sequences. Clause 6 describes the test sequences for the speech transcoder. Clause 7 describes the test sequences for the VAD, comfort noise and discontinuous transmission.
+
+Clause 8 describes the method by which synchronization is obtained between the test sequences and the speech codec under test.
+
+Clause 9 describes the optional acceptance testing of the speech encoder and decoder in the TRAU by means of 8 bit A- or  $\mu$ -law compressed test sequences on the A-Interface.
+
+Electronic copies of the digital test sequences are provided as clause 10, these digital test sequences are contained in archive en\_300968v080001p0.ZIP which accompanies the present document.
+
+# --- 5 Test sequence format
+
+This clause provides information on the format of the digital test sequences for the GSM half rate speech transcoder (GSM 06.20 [2]), Voice Activity Detector (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and the discontinuous transmission (GSM 06.41 [5]).
+
+## 5.1 File format
+
+The test sequence files are provided in archive en\_300968v080001p0.ZIP which accompanies the present document.
+
+Following decompression, by execution of the 11 "disk\*.exe" files, four types of file are provided:
+
+- Files for input to the GSM half rate speech encoder: \*.INP
+- Files for comparison with the encoder output: \*.COD
+- Files for input to the GSM half rate speech decoder: \*.DEC
+- Files for comparison with the decoder output: \*.OUT
+
+Tables 1, 2, 3 and 4 define the formats of the four types of file. Each parameter in these tables is contained in a 16 bit word except for the samples of the 8 bit PCM test sequences, which are contained in an 8 bit word each. The left or right justification is indicated in the tables. The size and location of speech parameters in the encoder output (\*.COD) and decoder input files (\*.DEC) are described in GSM 06.20 [2].
+
+## 5.2 Codec homing
+
+Each \*.INP file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech encoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.06 [7]), all speech encoder output frames shall be identical to the corresponding frame in the \*.COD file. In the case of a correct hardware implementation undergoing type approval, the first speech encoder output frame is undefined and need not be identical to the first frame in the \*.COD file, but all remaining speech encoder output frames shall be identical to the corresponding frames in the \*.COD file.
+
+Each \*.DEC file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech decoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.06 [7]), all speech decoder output frames shall be identical to the corresponding frame in the \*.OUT file. In the case of a correct hardware implementation undergoing type approval, the first speech decoder output frame is undefined and need not be identical to first frame in the \*.OUT file, but all remaining speech decoder output frames shall be identical to the corresponding frames in the \*.OUT file.
+
+**Table 1: Encoder input sequence (\*.INP) format**
+
+| Name | Description          | No. of bits | Justification |
+|------|----------------------|-------------|---------------|
+| s(n) | Encoder input signal | 13          | Left          |
+
+**Table 2: Encoder output sequence (\*.COD) format**
+
+| Name                   | Description                              | No. of words | Justification |
+|------------------------|------------------------------------------|--------------|---------------|
+| Speech                 | Speech parameters to the channel encoder | 18           | Right         |
+| Additional information |                                          |              |               |
+| VAD                    | Voice activity detection flag            | 1            | Right         |
+| SP                     | SP flag                                  | 1            | Right         |
+
+**Table 3: Decoder input sequence (\*.DEC) format**
+
+| Name              | Description                              | No. of bits/words | Justification |
+|-------------------|------------------------------------------|-------------------|---------------|
+| Speech parameters | Speech parameters to the channel encoder | 18 words          | Right         |
+| BFI flag          | Bad Frame Indicator                      | 1 bit / 1 word    | Right         |
+| UFI flag          | Unreliable Frame Indicator               | 1 bit / 1 word    | Right         |
+| SID flag          | Silence Descriptor                       | 2 bits / 1 word   | Right         |
+| TAF flag          | Time Alignment Flag                      | 1 bit / 1 word    | Right         |
+
+**Table 4: Decoder output sequence (\*.OUT) format**
+
+| Name  | Description           | No. of bits | Justification |
+|-------|-----------------------|-------------|---------------|
+| s'(n) | Decoder output signal | 13          | Left          |
+
+# 6 Speech codec test sequences
+
+This clause describes the test sequences designed to exercise the GSM half rate speech transcoder (GSM 06.20 [2]).
+
+## 6.1 Codec configuration
+
+The speech encoder shall be configured to operate in the non-DTX mode. The VAD and SP flags shall be set to 1 at the speech encoder output.
+
+## 6.2 Speech codec test sequences
+
+Table 5 lists the location and size of the speech codec test sequences.
+
+### 6.2.1 Speech encoder test sequences
+
+Three encoder input sequences are provided:
+
+- SEQ01.INP - Sequence for exercising the LPC vector quantization codebooks;
+- SEQ02.INP - Sequence for exercising the long term predictor codebooks;
+- SEQ03.INP - Sequence for exercising the remaining excitation codebooks.
+
+The SEQ01.INP sequence causes the GSM half rate speech encoder to select every vector in the three reflection coefficient vector quantizers at least once. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ01.COD sequence.
+
+The SEQ02.INP sequence causes the encoder to select at least once every quantization level in the eight bit table of long term filter lags for the first subframe, and every quantization level in the four bit delta lag quantizer for subframes 2, 3, and 4. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ02.COD sequence.
+
+The SEQ03.INP sequence causes the encoder to select each of the quantization levels at least once for the remaining GSM half rate speech coder parameters: R0 (frame energy), the soft interpolation decision for the LPC coefficients, the four voicing modes, the gain vectors (GSP0) for each of the voicing modes, and the voiced and unvoiced VSELP codebooks. The only exception to this is that two GSP0 levels in the unvoiced mode are not selected. However, these levels are exercised in the GSM half rate speech decoder as described below. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the SEQ03.COD sequence.
+
+### 6.2.2 Speech decoder test sequences
+
+Four speech decoder input sequences are provided:
+
+- SEQ01.DEC;
+- SEQ02.DEC;
+- SEQ03.DEC;
+- SEQ04.DEC.
+
+The SEQ01.DEC, SEQ02.DEC, and SEQ03.DEC sequences test the operation of the GSM half rate speech decoder in the absence of channel errors. They are derived from the corresponding SEQXX.INP sequences. In a correct implementation, the resulting speech decoder output shall be identical to the SEQ01.OUT, SEQ02.OUT, and SEQ03.OUT sequences, respectively. Together, these three sequences exercise every quantization level in every codebook in the decoder, with the exception of two GSP0 levels in the unvoiced mode.
+
+The SEQ04.DEC sequence is designed to test the GSM half rate speech decoder under conditions which can result from channel errors. In particular, it is the decoding of LTP lags at the lag table boundaries, given delta lag codes which if incorrectly decoded would point outside the eight bit lag table, that is being tested. Also, the two remaining GSP0 levels in the unvoiced mode are exercised by this sequence. In a correct implementation, the resulting speech decoder output shall be identical to the SEQ04.OUT sequence.
+
+### 6.2.3 Codec homing sequence
+
+In addition to the test sequences described above, two homing sequences are provided to assist in codec type approval testing. SEQ05.INP contains one encoder-homing-frame. SEQ05.DEC contains one decoder-homing-frame. The use of these sequences is described in GSM 06.02 [8].
+
+**Table 5: Location and size of speech codec test sequences**
+
+| Disk No. | File Name | No. of frames | Size (bytes) |
+|----------|-----------|---------------|--------------|
+| 1        | SEQ01.INP |               | 754 880      |
+| 1        | SEQ01.COD | 2 359         | 94 360       |
+| 2        | SEQ01.DEC |               | 103 796      |
+| 2        | SEQ01.OUT |               | 754 880      |
+| 1        | SEQ02.INP |               | 249 920      |
+| 1        | SEQ02.COD | 781           | 31 240       |
+| 2        | SEQ02.DEC |               | 34 364       |
+| 2        | SEQ02.OUT |               | 249 920      |
+| 1        | SEQ03.INP |               | 132 160      |
+| 1        | SEQ03.COD | 413           | 16 520       |
+| 2        | SEQ03.DEC |               | 18 172       |
+| 2        | SEQ03.OUT |               | 132 160      |
+| 2        | SEQ04.DEC | 76            | 3 344        |
+| 2        | SEQ04.OUT |               | 24 320       |
+| 1        | SEQ05.INP | 1             | 320          |
+| 2        | SEQ05.DEC |               | 44           |
+
+# 7 DTX test sequences
+
+This clause describes the test sequences designed to exercise the VAD algorithm (GSM 06.42 [6]), comfort noise (GSM 06.22 [4]) and discontinuous transmission (GSM 06.41 [5]).
+
+## 7.1 Codec configuration
+
+The VAD, comfort noise and discontinuous transmission shall be tested in conjunction with the speech encoder [2]). The speech encoder shall be configured to operate in the DTX mode defined in GSM 06.22 [4].
+
+## 7.2 DTX test sequences
+
+Each DTX test sequence consists of four files:
+
+- Files for input to the GSM half rate speech encoder: \*.INP
+- Files for comparison with the encoder output \*.COD
+- Files for input to the GSM half rate speech decoder: \*.DEC
+- Files for comparison with the decoder output: \*.OUT
+
+The \*.DEC files are generated from the corresponding \*.COD files.
+
+In a correct implementation, the speech encoder parameters generated by the \*.INP file shall be identical to those specified in the \*.COD file; and the speech decoder output generated by the \*.DEC file shall be identical to that specified in the \*.OUT file.
+
+Table 6 lists the DTX test sequences and their size in frames.
+
+### 7.2.1 Predictor values computation
+
+The computation of the predictor values described in GSM 06.42 [6] is not tested explicitly, since the results from the computation are tested many times via the spectral comparison and threshold adaptation tests.
+
+### 7.2.2 Spectral comparison
+
+The spectral comparison algorithm described in GSM 06.42 [6] is tested by the following test sequence:
+
+- DTX01.\*
+
+### 7.2.3 Threshold adaptation
+
+The threshold adaptation algorithm described in GSM 06.42 [6] is tested by the following test sequence:
+
+- DTX02.\*
+
+### 7.2.4 Periodicity detection
+
+The periodicity detection algorithm described in GSM 06.42 [6] is tested by the following test sequence:
+
+- DTX03.\*
+
+### 7.2.5 Tone detection
+
+The tone detection algorithm described in GSM 06.42 [6] is tested by the following test sequence:
+
+- DTX04.\*
+
+### 7.2.6 Safety and initialization
+
+This sequence checks the safety paths used to prevent zero values being passed to the norm function. It checks the functions described in the adaptive filtering and energy computation, and the prediction values computation given in GSM 06.42 [6]. This sequence also checks the initialization of thvad and the rvad array:
+
+- DTX05.\*
+
+### 7.2.7 Comfort noise test sequence
+
+The test sequences described in sub-clauses 7.2.2 to 7.2.6 are designed to exercise the VAD described in GSM 06.42 [6] and the discontinuous transmission described in GSM 06.41 [5]. The following test sequence is defined to exercise the comfort noise algorithm described in GSM 06.22 [4]:
+
+- DTX06.\*
+
+### 7.2.8 Real speech and tones
+
+The test sequences cannot be guaranteed to find every possible error. There is therefore a small possibility that an incorrect implementation produces the correct output for the test sequences, but fails with real signals. Consequently, an extra sequence is included, which consists of very clean speech, barely detectable speech and a swept frequency tone:
+
+- DTX07.\*
+
+NOTE: Some of the DTX test sequences contain homing frames. The DTX test sequences are therefore only suitable for testing a single transcoding.
+
+**Table 6: Location and size of DTX test sequences**
+
+| Disk No. | File Name | No. of Frames | size (bytes) |        |        |         |
+|----------|-----------|---------------|--------------|--------|--------|---------|
+|          |           |               | *.INP        | *.COD  | *.DEC  | *.OUT   |
+| 3        | DTX01     | 460           | 147 200      | 18 400 | 20 240 | 147 200 |
+| 3        | DTX02     | 886           | 283 520      | 35 440 | 38 984 | 283 520 |
+| 3        | DTX03     | 125           | 40 000       | 5 000  | 5 500  | 40 000  |
+| 3        | DTX04     | 317           | 101 440      | 12 680 | 13 948 | 101 440 |
+| 3        | DTX05     | 37            | 11 840       | 1 480  | 1 628  | 11 840  |
+| 4        | DTX06     | 240           | 76 800       | 9 600  | 10 560 | 76 800  |
+| 4        | DTX07     | 1 188         | 380 160      | 47 520 | 52 272 | 380 160 |
+
+# 8 Sequences for finding the 20 ms framing of the GSM half rate speech encoder
+
+When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (testing of MS) or can be reached easily on the A<sub>bis</sub>-interface (testing on network side).
+
+When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder.
+
+In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronization sequences. This procedure can be used for MS as well as for network side.
+
+Synchronization can be achieved in two steps. First, bit synchronization has to be found. In a second step, frame synchronization can be determined. This procedure takes advantage of the codec homing feature of the half rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined and can be triggered to.
+
+## 8.1 Bit synchronization
+
+The input to the speech encoder is a series of 13 bit long words (104 kbits/s, 13 bit linear PCM). When starting to test the speech encoder, no knowledge is available on bit synchronization, i.e. where the encoder expects its least significant bits, and where it expects the most significant bits.
+
+The encoder homing frame consists of 160 samples, all set to zero with the exception of the least significant bit, which is set to one (0 0000 0000 0001 binary, or 0x0008 hex if written into 16 bit words left justified). If two such encoder homing frames are input to the encoder consecutively, the decoder homing frame is expected at the output as a reaction of the second encoder homing frame.
+
+Since there are only 13 possibilities for bit synchronization, after a maximum of 13 trials bit synchronization can be reached. In each trial, three consecutive encoder homing frames are input to the encoder. If the decoder homing frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder homing frame is detected at the output, bit synchronization is found, and the first step can be terminated.
+
+The reason why three consecutive encoder homing frames are needed is that frame synchronization is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder homing frames.
+
+An example of the 13 different frame triplets is given in sequence BITSYNC.INP (see table 7).
+
+## 8.2 Frame synchronization
+
+Once bit synchronization is found, frame synchronization can be found by inputting one special frame that delivers 160 different output frames, depending on the 160 different positions that this frame can possibly have with respect to the encoder framing.
+
+This special synchronization frame was found by taking one input frame and shifting it through the positions 0 to 159. The corresponding 160 encoded speech frames were calculated and it was verified that all 160 output frames were different. When shifting the input synchronization frame, the samples at the beginning were set to 0x0008 hex, which corresponds to the samples of the encoder homing frame.
+
+Before inputting this special synchronization frame to the encoder, again the encoder has to be reset by one encoder homing frame. A second encoder homing frame is needed to provoke a decoder homing frame at the output that can be triggered to. And since the framing of the encoder is not known at that stage, three encoder homing frames have to precede the special synchronization frame to ensure that the encoder reads at least two homing frames, and at least one decoder homing frame is produced at the output, serving as a trigger for recording.
+
+The special synchronization frame preceded by the three encoder homing frames are given in SEQSYNC.INP. The corresponding 160 different output frames are given in SYNC000.COD through SYNC159.COD. The three digit number in the filename indicates the number of samples by which the input was retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing can be reached.
+
+## 8.3 Formats and sizes of the synchronization sequences
+
+### BIT SYNC.INP:
+
+This sequence consists of 13 frame triplets. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero).
+
+The size of it is therefore:
+
+$$\text{SIZE (BITSYNC.INP)} = 13 * 3 * 160 * 2 \text{ bytes} = 12480 \text{ bytes.}$$
+
+### SEQSYNC.INP:
+
+This sequence consists of 3 encoder reset frames and the special synchronization frame. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero).
+
+The size of it is therefore:
+
+$$\text{SIZE (SEQSYNC.INP)} = 4 * 160 * 2 \text{ bytes} = 1280 \text{ bytes.}$$
+
+### SYNCXXX.COD:
+
+These sequences consists of 1 encoder output frame each. They have the format of the speech encoder output test sequences (16 bit words right justified). The values of the VAD and SP flags are set to one in these files.
+
+The size of them is therefore:
+
+$$\text{SIZE (SYNCXXX.COD)} = (18 + 2) * 2 \text{ bytes} = 40 \text{ bytes}$$
+
+Table 7 summarizes this information.
+
+**Table 7: Location, size and justification of synchronization sequences**
+
+| Disk No. | Purpose of Sequence            | Name of Sequence | No. of Frames | Size in Bytes | Justification |
+|----------|--------------------------------|------------------|---------------|---------------|---------------|
+| 5        | Bit Synchronization            | BITSYNC.INP      | 39            | 1 2480        | Left          |
+| 5        | Frame Synchronization (input)  | SEQSYNC.INP      | 4             | 1 280         | Left          |
+| 5        | Frame Synchronization (output) | SYNC000.COD      | 1             | 40            | Right         |
+|          |                                | SYNC001.COD      | 1             | 40            | Right         |
+|          |                                | SYNC002.COD      | 1             | 40            | Right         |
+|          |                                | "                | "             | "             | "             |
+|          |                                | "                | "             | "             | "             |
+|          |                                | "                | "             | "             | "             |
+|          |                                | SYNC159.COD      | 1             | 40            | Right         |
+
+# 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences
+
+In the previous clauses tests for the transcoder in the TRAU are described using 13 bit linear test sequences. However, these 13 bit test sequences require a special interface in the Trau and do not allow testing in the field. In most cases the TRAU has to be set in special mode before testing.
+
+As an option, the speech codec tests can be performed with A/ $\mu$  law compressed 8 bit PCM test sequences on the A interface. These modified input test sequences (\*-X.INP) are generated from the original sequences by A or  $\mu$  law compression. As an input to the encoder they result in modified encoder output sequences (\*-X.COD). The same \*.dec decoder input sequences as in clause 6.2.2. are then used to produce the output sequences \*-X.OUT, which are A- or  $\mu$ -law compressed.
+
+The A- and  $\mu$ -law compression and decompression does not change the homing frames at the encoder input. The format of all A- and  $\mu$ -law PCM files \*-X.INP and \*-X.OUT is one sample (8 bit) per byte. The format of all other files is as described in clause 5.
+
+All files are provided in archive en\_300968v080001p0.ZIP which accompanies the present document. The 'X' in the tables below with the filenames stands for A (A-law) and U ( $\mu$ -law), respectively. The decoder input files \*.dec are the same as in Table 5 and are not described in this clause.
+
+**Table 8: Location and size of compressed 8 bit PCM speech codec test sequences**
+
+| Disk No. | File Name   | No. of frames | Size (bytes) |
+|----------|-------------|---------------|--------------|
+| 6/7      | SEQ01-X.INP | 2 359         | 377 440      |
+| 6/7      | SEQ01-X.COD |               | 94 360       |
+| 6/7      | SEQ01-X.OUT |               | 377 440      |
+| 6/7      | SEQ02-X.INP | 781           | 124 960      |
+| 6/7      | SEQ02-X.COD |               | 31 240       |
+| 6/7      | SEQ02-X.OUT |               | 124 960      |
+| 6/7      | SEQ03-X.INP | 413           | 66 080       |
+| 6/7      | SEQ03-X.COD |               | 16 520       |
+| 6/7      | SEQ03-X.OUT |               | 66 080       |
+| 6/7      | SEQ04-X.OUT | 76            | 12 160       |
+| 6/7      | SEQ05-X.INP | 1             | 160          |
+
+**Table 9: Location and size of compressed 8 bit PCM DTX test sequences**
+
+| Disk No. | File Name | No. of Frames | size (bytes) |        |         |
+|----------|-----------|---------------|--------------|--------|---------|
+|          |           |               | *.INP        | *.COD  | *.OUT   |
+| 8/9      | DTX01-X   | 460           | 73 600       | 18 400 | 73 600  |
+| 8/9      | DTX02-X   | 886           | 141 760      | 35 440 | 141 760 |
+| 8/9      | DTX03-X   | 125           | 20 000       | 5 000  | 20 000  |
+| 8/9      | DTX04-X   | 317           | 50 720       | 12 680 | 50 720  |
+| 8/9      | DTX05-X   | 37            | 5 920        | 1 480  | 5 920   |
+| 8/9      | DTX06-X   | 240           | 38 400       | 9 600  | 38 400  |
+| 8/9      | DTX07-X   | 1 188         | 190 080      | 47 520 | 190 080 |
+
+In addition to the test sequences above, special input (seqsyncX.inp) and output (syncxxxX.cod) sequences for frame synchronization are provided. The X again stands for A and  $\mu$  law compressed PCM. The synchronization procedure is described in clause 8.
+
+**Table 10: Location, size and justification of compressed 8 bit PCM test sequences**
+
+| Disk No. | Purpose of Sequence            | Name of Sequence | No. of Frames | Size in Bytes | Justification |
+|----------|--------------------------------|------------------|---------------|---------------|---------------|
+| 10/11    | Frame Synchronization (input)  | SEQSYN CX.INP    | 4             | 640           | -             |
+| 10/11    | Frame Synchronization (output) | SYNC000X.COD     | 1             | 40            | Right         |
+|          |                                | SYNC001X.COD     | 1             | 40            | Right         |
+|          |                                | SYNC002X.COD     | 1             | 40            | Right         |
+|          |                                | "                | "             | "             | "             |
+|          |                                | "                | "             | "             | "             |
+|          |                                | "                | "             | "             | "             |
+|          |                                | "                | "             | "             | "             |
+|          |                                | SYNC159X.COD     | 1             | 40            | Right         |
+
+# 10 Test sequences for the GSM half rate speech codec
+
+NOTE: This clause is contained in archive en\_300968v080001p0.ZIP which accompanies the present document.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                  |             |                                                           |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                                          |
+| SMG#16         |           |         |                  | 4.0.3       | ETSI Publication                                          |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                                      |
+| SMG#23         | 97-737    | A003    |                  | 5.1.1       | UAP60 and Supplementary notes on 06.06 Call Graph Changes |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                                      |
+| SMG#28         |           |         |                  | 6.0.1       | ETSI Publication                                          |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                                      |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication                   |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                                      |
+|                |           |         |                  | 8.0.1       | Update to Version 8.0.1 for Publication                   |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                                                              |             |
+|----------------|---------|------|----|-----|-----|------------------------------------------------------------------------------|-------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                                                              | New version |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14                                                       | 14.0.0      |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15                                                       | 15.0.0      |
+| 2020-10        | SA#88-e | -    | -  | -   | -   | Update to Rel-16 version (MCC)                                               | 16.0.0      |
+| 2020-10        | 88-e    |      |    |     |     | Post SA#88-e, Updated after insertion of correct document in the zipped file | 16.0.1      |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46008/88362167d90777ecb0aeb145832e78c2_img.jpg b/marked/Rel-16/46_series/46008/88362167d90777ecb0aeb145832e78c2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..df2ff45005e1911a415f942f15cf8d7e4c3f7f90
--- /dev/null
+++ b/marked/Rel-16/46_series/46008/88362167d90777ecb0aeb145832e78c2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ad7b3192d0da162d9fee737130bd3d0bd48c32d053685cbef356e0ad7835fe0d
+size 32672
diff --git a/marked/Rel-16/46_series/46008/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-16/46_series/46008/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d237158a9ee818ef06cd8cb6ab6ceafbf6c07ee6
--- /dev/null
+++ b/marked/Rel-16/46_series/46008/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:346f8103c5f38a0d46cc47839c24a74643e3c42ebe32811e0e31f589ae687c07
+size 56194
diff --git a/marked/Rel-16/46_series/46008/raw.md b/marked/Rel-16/46_series/46008/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..c3ca0464cf0b95b4f9cae231485fa1581ab48c7b
--- /dev/null
+++ b/marked/Rel-16/46_series/46008/raw.md
@@ -0,0 +1,676 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                   |           |
+|-----------------------------------------------------------------------------------|-----------|
+| ContentsForeword .....                                                            | 3         |
+| Foreword .....                                                                    | 4         |
+| Introduction .....                                                                | 4         |
+| 1 Scope.....                                                                      | 6         |
+| 2 References.....                                                                 | 6         |
+| 3 Abbreviations.....                                                              | 6         |
+| 4 Quality under error conditions (A-law, IRS), Experiment 1.....                  | 7         |
+| 5 Quality under error conditions (UPCM, No IRS), Experiment 2 .....               | 7         |
+| 6 Quality under tandeming conditions.....                                         | 8         |
+| 6.1 Quality under tandeming conditions, Experiment 3.....                         | 8         |
+| 6.2 Effect of tandeming with other standards, Experiment 7 .....                  | 8         |
+| 7 Quality under background noise conditions.....                                  | 9         |
+| 7.1 Experiments 4 and 5.....                                                      | 9         |
+| 7.2 Special background noise.....                                                 | 10        |
+| 7.2.1 Introduction .....                                                          | 10        |
+| 7.2.2 Observations .....                                                          | 10        |
+| 8 Assessment of equivalent qdu, Experiment 6.....                                 | 11        |
+| 9 Talker dependency, Experiment 8 .....                                           | 11        |
+| 10 DTX System.....                                                                | 11        |
+| 10.1 Assessment of DTX algorithm, Experiment 9 .....                              | 11        |
+| 10.2 Channel activity in DTX mode .....                                           | 12        |
+| 10.2.1 Test procedure .....                                                       | 12        |
+| 10.2.2 Speech channel activity .....                                              | 12        |
+| 10.2.3 Level compensation.....                                                    | 12        |
+| 10.2.4 SID update rate .....                                                      | 12        |
+| 10.2.5 Interleaving compensation.....                                             | 12        |
+| 10.2.6 Estimated mean TDMA channel activity .....                                 | 12        |
+| 11 Performance with DTMF tones.....                                               | 13        |
+| 11.1 Introduction .....                                                           | 13        |
+| 11.2 Test set-up .....                                                            | 13        |
+| 11.3 Results.....                                                                 | 13        |
+| 11.4 Conclusions.....                                                             | 14        |
+| 11.5 Result tables of experiments with standard and modified DTMF detectors ..... | 14        |
+| 12 Performance with signalling tones.....                                         | 14        |
+| 13 Delay.....                                                                     | 15        |
+| 14 Frequency response.....                                                        | 15        |
+| 15 Half Rate codec complexity.....                                                | 17        |
+| 16 Summary of results from characterization Phase 1 and 2.....                    | 17        |
+| 16.1 Summary of Results From Characterization Phase 1.....                        | 17        |
+| 16.2 Summary of Results From Characterization Phase 2.....                        | 19        |
+| 16.3 Conclusion.....                                                              | 19        |
+| <b>Annex A: Bibliography</b>                                                      | <b>20</b> |
+| Annex B: Change history                                                           | 21        |
+
+# Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+During five years of activity, the Traffic CHannel Half rate Speech (TCH-HS) Experts Group has produced a number of test plans and experiments to assess the performance of the candidate algorithms submitted for the GSM half rate standardization. An aid in this task was a large knowledge base made available from previous CCITT (now ITU-T) and ETSI activities on codec assessment (see annex A references 1) 2) 3) 4) 5)), plus the use of recommendations in the field (see annex A references 6) 7) 8)).
+
+Here are reported 3 different phases of the standardization of the GSM half rate codec: Characterization Phase 1, Characterization Phase 2 and Verification phase. The selection of the codec candidate for the GSM half rate traffic channel was based on the results of the characterization phase 1. Test results reported hereafter are based on version 3.3 of the GSM half rate codec.
+
+**Characterization Phase 1** (Experiments 1 to 5): For characterization Phase 1, C-simulations of the candidate codecs were used as hardware implementations were not available at that time. The simulations were produced by MOTOROLA (USA) and Ericsson (Sweden) with support by MATRA (France). The following experiments were carried out:
+
+- Experiment 1: Quality under error conditions (A-law, IRS);
+- Experiment 2: Quality under error conditions (UPCM, No IRS);
+- Experiment 3: Quality under tandeming conditions;
+- Experiment 4: Quality under background noise conditions (ACR);
+- Experiment 5: Quality under background noise conditions (DCR).
+
+**Characterization Phase 2** (Experiments 6 to 9): During Characterization Phase 2, a hardware implementation of the candidate algorithm was employed, provided by ANT (Germany). The following experiments were carried out:
+
+- Experiment 6: Assessment of equivalent qdu;
+- Experiment 7: Effect of tandeming with other standards;
+- Experiment 8: Talker Dependency;
+- Experiment 9: Assessment of DTX algorithm.
+
+**Verification phase:** Further tests accompanied characterization Phase 1 and 2 to obtain a better knowledge of the characteristics of the GSM half rate codec and its performance under different operational conditions:
+
+- Special background noise;
+- Channel activity in DTX mode;
+- Performance with DTMF tones;
+- Performance with signalling tones;
+- Delay;
+- Frequency response;
+- Complexity.
+
+For the characterization tests, a practical "indirect" method of performance comparison between different codecs was adopted, that utilizes the Modulated Noise Reference Unit (MNRU) (see annex A reference 7)) as a reference degradation in a subjective experiment including the codecs under test.
+
+NOTE: The MNRU is a device designed for producing speech correlated noise that sounds subjectively like the quantizing noise produced by log-companded PCM codecs. The device is subjectively calibrated for Mean Opinion Scores (MOS) against Q dB (where Q is the ratio of the speech to speech-correlated noise power). The "Equivalent Q" of the codecs under test can then be found from the corresponding MOS on the calibration curve of the MNRU.
+
+It is well known that this procedure works as long as the reference degradation sounds similar to the degradation under test.
+
+The MNRU provides the additional function of normalization across laboratories carrying out the same experiment, i.e. all MOS are converted to Equivalent Q (dB) and the results can be analysed statistically for differences between laboratories. An appropriate analysis of variance (ANOVA) was identified to evaluate the statistical significance of the experimental factors.
+
+The aim was to show that the subjective performance of the GSM half rate algorithm is at least as good as that of the full rate codec over a selected set of conditions. To allow for experimental error, the half rate candidate had to perform better than 1 dB below the performance of the full rate (for the overall figure of merit) and better than 3 dB below the performance of the full rate for individual test conditions.
+
+To model its use in a network, the half rate candidate codec had to be placed between either a ITU-T Recommendation G.711 [1] PCM coder and decoder, or a Uniform PCM, which provided the necessary A/D and D/A conversions. Source files of speech, produced either by using an "average" telephone set (called IRS - Intermediate Reference System) or a microphone showing a "flat" sending frequency characteristic (No IRS or "flat"), could then be processed through the different experimental conditions, for presentation to subjects in listening experiments. Among the different experimental conditions were error conditions at different input levels under both IRS A-Law PCM and No-IRS Linear PCM audio parts, tandeming conditions for different error patterns and background noise conditions. During all phases of testing, the host laboratory functions for the processing were provided by Aachen University of Technology (RWTH at Aachen, Germany).
+
+The whole set of "individual" and "global" data, collected in Experiment 1 to Experiment 9 were extensively analysed and discussed within TCH-HS expert group; for each condition, the MOS (or DMOS for Experiment 5) were computed, separately for male and female speech, as well as averaged together, and the effects of different factors and their interactions were subject to analysis of variance (ANOVA). Within characterization Phase 1, conversion to Q values and weighted averages were calculated for the whole set of results, in order to assess that the global figure of merit of the GSM half rate algorithm meets the quality requirement.
+
+# --- 1 Scope
+
+The present document gives background information on the performance of the GSM half rate speech codec. Experimental results from the characterization and verification tests carried out during the selection process by the Traffic CHannel Half rate Speech (TCH-HS) expert group are reported to give a more detailed picture of the behaviour of the GSM half rate speech codec under different conditions of operation.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] ITU-T Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".
+- [2] ITU-T Recommendation G.726: "40, 32, 24, 16 kbit/s adaptive differential pulse code modulation".
+- [3] ITU-T Recommendation G.728: "Coding of speech at 16 kbit/s using low-delay code excited linear prediction".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                                                   |
+|---------|-----------------------------------------------------------------------------------|
+| A/D     | Analogue to Digital                                                               |
+| ACR     | Absolute Category Rating                                                          |
+| ANOVA   | ANalysis Of VAriance                                                              |
+| C/I     | Carrier-to-Interferer ratio                                                       |
+| CEPT    | Conférence Européenne des Postes et Télécommunications                            |
+| CNI     | Comfort Noise Insertion                                                           |
+| D/A     | Digital to Analogue                                                               |
+| DAT     | Digital Audio Tape                                                                |
+| DCR     | Degradation Category Rating                                                       |
+| DSP     | Digital Signal Processor                                                          |
+| DTMF    | Dual Tone Multi Frequency                                                         |
+| DTX     | Discontinuous Transmission for power consumption and interference reduction       |
+| EID     | Error Insertion Device                                                            |
+| ETSI    | European Telecommunications Standards Institute                                   |
+| GBER    | Average gross bit error rate                                                      |
+| GSM     | Global System for Mobile communications                                           |
+| IRS     | Intermediate Reference System, No IRS= rather flat                                |
+| HLCS    | Host Laboratory Control System                                                    |
+| ITU-T   | International Telecommunication Union - Telecommunications Standardization Sector |
+| MNRU    | Modulated Noise Reference Unit                                                    |
+| MOS     | Mean Opinion Score                                                                |
+| MS      | Mobile Station                                                                    |
+| OVL     | Overload point                                                                    |
+| PCM     | Pulse Code Modulation                                                             |
+| Q       | Speech-to-speech correlated noise power ratio in dB                               |
+| qdu     | quantization distortion unit                                                      |
+| RPE-LTP | Regular Pulse Excited codec with Long Term Prediction                             |
+
+|        |                                        |
+|--------|----------------------------------------|
+| SCD    | Signal Conditioning Device             |
+| SFC    | Sending Frequency Characteristic       |
+| SID    | Silence Descriptor                     |
+| SMG    | Special Mobile Group                   |
+| SNR    | Signal to Noise Ratio                  |
+| TCH-HS | Traffic CHannel Half rate Speech       |
+| TDMA   | Time Division Multiple Access          |
+| UPCM   | Uniform or Linear PCM                  |
+| VAD    | Voice Activity Detector                |
+| wMOPs  | Weighted Million OPerations per second |
+
+Four different Error Patterns (EP0, EP1, EP2 and EP3) were used, where:
+
+- EP0 without channel errors;
+- EP1 C/I=10 dB; 5 % GBER (well inside a cell);
+- EP2 C/I= 7 dB; 8 % GBER (at a cell boundary);
+- EP3 C/I= 4 dB; 13 % GBER (outside a cell).
+
+# 4 Quality under error conditions (A-law, IRS), Experiment 1
+
+A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method.
+
+Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and Deutsche Telekom (Germany). Table 1 reports the results obtained in Experiment 1: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate.
+
+**Table 1: Results from experiment 1 (A-law, IRS)**
+
+| Error Pattern | Input Level<br>(dB relative to OVL) |       |       |
+|---------------|-------------------------------------|-------|-------|
+|               | -12                                 | -22   | -32   |
+| EP0           | -0,27                               | -0,02 | 0,34  |
+| EP1           | -0,26                               | -0,86 | -0,59 |
+| EP2           | -0,49                               | -1,61 | 1,14  |
+| EP3           | -0,39                               | 1,79  | 3,80  |
+
+NOTE: The figures in table 1 indicate DQ values in dB, where  $DQ = Q_{HR} - Q_{FR}$ .
+
+In general, the candidate codec performed equally well or slightly worse than the full rate (in any case never exceeded the -3 dB limit).
+
+# 5 Quality under error conditions (UPCM, No IRS), Experiment 2
+
+A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method.
+
+Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and DEUTSCHE TELEKOM (Germany). Table 2 reports the results obtained in Experiment 2: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate codec, negative values meaning worse performance than the full rate codec.
+
+**Table 2: Results from experiment 2 (UPCM, No IRS)**
+
+| Error Pattern | Input Level<br>(dB relative to OVL) |       |       |
+|---------------|-------------------------------------|-------|-------|
+|               | -12                                 | -22   | -32   |
+| EP0           | -1,13                               | -2,90 | -1,70 |
+| EP1           | <b>-3,72</b>                        | -1,72 | -1,21 |
+| EP2           | -1,93                               | -1,79 | 0,69  |
+| EP3           | 0,79                                | 1,49  | 3,59  |
+
+NOTE: The figures indicate DQ values in dB, where  $DQ = Q_{HR} - Q_{FR}$ .
+
+In general, the candidate codec performed equally well or slightly worse than the full rate (in one case, at -12 dB relative to Overload point (OVL) in EP1 condition,  $Q_{HR} - Q_{FR}$  exceeded the -3 dB limit).
+
+# 6 Quality under tandeming conditions
+
+## 6.1 Quality under tandeming conditions, Experiment 3
+
+A listening-only test was chosen, adopting the Absolute Category Rating (ACR) method. Subjective tests were carried out by BT (United Kingdom), CSELT (Italy), and DEUTSCHE TELEKOM (Germany). Table 3 reports the results obtained in Experiment 3: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate.
+
+**Table 3: Results from experiment 3 (Tandem Conditions)**
+
+| Error Pattern | A-Law PCM (with IRS)<br>$DQ (dB) = (HR+HR)-(FR+FR)$ |       |       | Linear PCM (No IRS)<br>$DQ (dB) = (HR+HR)-(FR+FR)$ |              |              |
+|---------------|-----------------------------------------------------|-------|-------|----------------------------------------------------|--------------|--------------|
+|               | Input Level<br>(dB relative to OVL)                 |       |       | Input Level<br>(dB relative to OVL)                |              |              |
+|               | -12                                                 | -22   | -32   | -12                                                | -22          | -32          |
+| EP0           | -0,14                                               | -0,56 | -0,03 | <b>-5,20</b>                                       | <b>-5,43</b> | <b>-3,89</b> |
+| EP1           | -0,46                                               | -0,75 | 0,49  | <b>-4,98</b>                                       | <b>-4,14</b> | -2,79        |
+
+NOTE: The figures indicate DQ values in dB, where  $DQ = Q_{HR} - Q_{FR}$ .
+
+In general, two candidate codecs in tandem performed equally well or slightly worse than two full rate codecs in tandem for the A-Law IRS audio part, while in most cases exceeded the -3 dB limit for the Uniform PCM No IRS audio part.
+
+In operating networks, A-law coding and decoding is performed between both speech processing steps in both mobile to mobile calls. Therefore, the results of real network configurations are expected to be somewhere in between the figures obtained using the A-law input speech material and those obtained using the linear PCM speech material for each condition.
+
+## 6.2 Effect of tandeming with other standards, Experiment 7
+
+The experiment was conducted in two different laboratories: BT (UK) and CNET (France).
+
+The following standards were tandemed with the half rate codec in this experiment: half rate, full rate, ITU-T Recommendation G.726 [2] (at 32 kbit/s) and G.728 [3]. Both possible orders of tandeming were tested for each of these cases, in both error free and EP1 conditions. The error pattern EP1 was only applied to the full and half rate codecs.
+
+The main conclusion that can be drawn is that the performance is always better when the half rate codec follows the other codec in the tandeming chain. This effect is most pronounced at the higher speech input level (12 dB below overload point).
+
+# 7 Quality under background noise conditions
+
+## 7.1 Experiments 4 and 5
+
+International subjective test programs have been conducted in the past, by both the ITU and ETSI, to investigate the effects of environmental noise. This has proved to be a difficult area to evaluate, and more satisfactory methodologies are continually being sought to improve the accuracy of these tests. Several methodologies have been used recently to investigate this factor:
+
+- a) the ACR (Absolute Category Rating) method using the classical Quality scale (second selection phase of the GSM half rate speech coding algorithm candidate, 1992);
+- b) the ACR method using the Listening Effort scale (second pre-selection test of the GSM Half Rate candidate, 1992);
+- c) the DCR (Degradation Category Rating) method such as in the ITU-T test methodology for the 16 kbit/s and 8 kbit/s speech coders which is an adapted version of the standard DCR procedure (described in ITU-T Recommendation P.80) and where several types of noise at different Signal-to-Noise ratios were evaluated in a unique experiment;
+- d) the DCR procedure adapted such as in the first pre-selection phase of testing for the GSM half rate candidates in 1991, where only one distinct noise has been tested in the same experiment in order to prevent the noise from being the predominant factor within the test; two experiments were, then, designed to take into account two types of noise: babble noise at a SNR of 30 dB and vehicle noise at a SNR of 10 dB.
+
+Analysis of results gathered from these four experimental designs led to the conclusion that the last procedure - DCR test per noise (d) - is the most appropriate one to study the effects of environmental noise on a codec's behaviour.
+
+For the final characterization phase of testing, it was decided to follow up two methodologies: the ACR and the DCR methods, i.e. to formally compare two distinct modes of collecting the subjects' responses with exactly the same experimental test plan (four 24 x 24 interleaved graeco-latin squares). The following environmental noises were considered of interest: office babble, vehicular, and traffic.
+
+A listening-only test was chosen, adopting, for Exp. 4, the Absolute Category Rating (ACR) method, and subjective tests were carried out by BT (United Kingdom) and DEUTSCHE TELEKOM (Germany), while a modified version of the Degradation Category rating (DCR) was agreed for Exp. 5, and subjective tests were carried out by CNET (France) and CSELT (Italy).
+
+Table 4 and 5 report the results obtained in experiment 4 and 5, respectively: each cell shows the difference in terms of equivalent Q values between the candidate and the full rate, negative values meaning worse performance than the full rate.
+
+**Table 4: Results from experiment 4 (ACR)**
+
+| Noise             | Office Babble | Vehicular    | Traffic      |
+|-------------------|---------------|--------------|--------------|
+| Low noise         | -0,78         | -2,19        | -1,06        |
+| High Noise        | -1,75         | -0,87        | -1,25        |
+| Low Noise Tandem  | -1,75         | -2,38        | -2,66        |
+| High Noise Tandem | -2,99         | <b>-4,10</b> | <b>-3,09</b> |
+
+NOTE: The figures indicate DQ values in dB, where  $DQ = Q_{HR} - Q_{FR}$ .
+
+**Table 5: Results from experiment 5 (DCR)**
+
+| Noise             | Office Babble | Vehicular    | Traffic      |
+|-------------------|---------------|--------------|--------------|
+| Low noise         | -2,10         | -2,96        | <b>-4,53</b> |
+| High Noise        | -2,79         | -2,83        | -2,04        |
+| Low Noise Tandem  | <b>-4,03</b>  | <b>-4,39</b> | <b>-5,31</b> |
+| High Noise Tandem | <b>-4,96</b>  | <b>-5,85</b> | <b>-5,68</b> |
+
+NOTE: The figures indicate DQ values in dB, where  $DQ = Q_{HR} - Q_{FR}$ .
+
+The main conclusion that can be drawn is that the performance of the half rate codec is (always) worse than that of the full rate, the amount of perceived degradation, in terms of DQ in dB, depending on the method chosen for the test (DCR being clearly more discriminant than ACR). Such background noise effect is most pronounced in tandem conditions.
+
+## 7.2 Special background noise
+
+### 7.2.1 Introduction
+
+Some informal listening sessions were carried out to further investigate background noise effects. Speech samples from four different talkers were electronically mixed (at 3 different Signal-to-Noise Ratios; 5 dB, 10 dB, and 20 dB) with a wide range of different background noises, reflecting the following types of environment:
+
+- Industrial Setting;
+- Babble (offices and public places such as airports);
+- Trains;
+- Cars and Lorries;
+- Roadside.
+
+These were processed through a simulation of the Half Rate codec (with no DTX) and were listened to (on an informal basis) under controlled listening conditions using headphones.
+
+No formal method of voting or opinion collation was employed; observations were simply noted.
+
+### 7.2.2 Observations
+
+At the lower Signal-to-Noise Ratios, the speech was often unintelligible without considerable concentration and effort on the part of the listener. In some cases, even where the listener was familiar with the speech material, it was impossible to understand some parts of the speech.
+
+The codec had the effect of making the background noises sound "babble", which, for example, made most background noises sound more "busy". This effect was particularly bad at 5 dB SNR. At 10 dB, the listening was more comfortable although parts of it were still difficult to understand. At 20 dB the speech was clearly understandable, although the noise was still "babble".
+
+For the -12 dB and -22 dB input levels, peak clipping also distorted the speech. Understandably, this effect was worse for the higher input level and for the higher Signal-to-Noise Ratios.
+
+It must be particularly remembered when considering these results that the listening was informal and used headphones, not a handset. Also, the use of electrically summed speech and noise will not give the same results as would have been obtained if the speech used had actually been recorded in the noisy environment.
+
+# --- 8 Assessment of equivalent qdu, Experiment 6
+
+The experiment on the assessment of qdu was designed to assess the half rate codec performance, in error free conditions, in terms of Equivalent Quantization Distortion Units (qdu) as defined by the ITU-T. Two laboratories performed the experiment (CSEL and DEUTSCHE TELEKOM) and the following conclusions were drawn from their results:
+
+- a) For single encoding, the half rate codec was judged to be statistically equivalent to the full rate. Similar planning rules could therefore be applied to both algorithms if the configuration is not mobile-to-mobile. The figure of equivalent qdu for the half rate codec was found to lie somewhere between 8 and 16 qdu. A more precise figure could not be determined due to differences in the results from the two laboratories.
+
+(It is reminded that for the full rate an "average" figure of 7-8 qdu was indicated by SCEG to GSM, after considering test results showing values between a minimum of 4-5 qdu and a maximum of 21-22 qdu).
+
+- b) For tandemed conditions, a statistically significant difference in performance between the half and full rate codecs was detected in one of the two laboratories. The results confirmed that a noticeable degradation in speech quality in mobile-to-mobile connections is likely.
+
+Generally, both the Half- and Full-Rate showed a worse performance than the other standards (ITU-T Recommendations G.711 [1], G.726 [2], at 32 kbit/s, and G.728 [3]) included in the experiment.
+
+# --- 9 Talker dependency, Experiment 8
+
+From the results obtained in the two laboratories which conducted this experiment, the performance of any given condition undoubtedly varies from talker to talker.
+
+The existence of this talker dependency has been confirmed by a further analysis applied to the results from the first phase of characterization testing.
+
+Under error free conditions, it was shown in the tests carried out, that the talker dependency for the half rate codec is similar to that for the full rate.
+
+# --- 10 DTX System
+
+## 10.1 Assessment of DTX algorithm, Experiment 9
+
+The four laboratories who performed the subjective evaluation of DTX functions concentrated their expert listening on the following effects, using conversational speech;
+
+- Voice Activity Detection (VAD); and
+- Comfort Noise Insertion (CNI).
+
+For this, the speech material available was monitored for the following effects:
+
+- speech clipping;
+- noise quality;
+- noise contrast.
+
+The tests showed that malfunctions of the VAD and the CNI were only predominant with low SNRs. The VAD functions appeared to work well in most situations (i.e. rather little clipping). In many situations, the Comfort Noise Insertion did not operate properly, being poorly matched in terms of quality and/or level. The DTX performed better with hand-held terminals relative to its performance with hands-free.
+
+## 10.2 Channel activity in DTX mode
+
+### 10.2.1 Test procedure
+
+Speech material recorded during testing of the full rate DTX system was processed through the codec/DTX hardware. This material comprised real conversations in the English, French, German and Italian languages. The activity of the VAD algorithm was measured for all 480 conversations. The mean channel activity was then calculated by means of a software simulation of the TX DTX handler.
+
+### 10.2.2 Speech channel activity
+
+The percentage of speech frames scheduled for transmission by the radio sub-system (subsequently referred to as the speech channel activity) varied significantly between conversations. Speech channel activities ranged from 35 % to 85 % for individual sides of a conversation. For this reason, it was not possible to identify any significant trends in the results with regard to terminal type and environmental conditions. The mean speech channel activity, measured over all 480 conversations, was approximately 55 %.
+
+### 10.2.3 Level compensation
+
+During the expert listening, it was found that the speech material had been processed at a level 6,5 dB below the original recorded level. However, the activity of the basic VAD algorithm rises approximately 0,5 % per dB increase in input level. To compensate for this, a factor of 3 % must be added to the speech channel activity estimate.
+
+### 10.2.4 SID update rate
+
+The DTX handler simulation used a SID update period of 480 ms. The SID update rate has subsequently been reduced to 240 ms. This modification will raise the speech channel activity by approximately 2 %.
+
+### 10.2.5 Interleaving compensation
+
+The channel measurements were calculated on a signal frame basis. However, the use of interleaving (depth 4) implies that the TDMA activity will be approximately 2 % higher than the signal frame activity.
+
+### 10.2.6 Estimated mean TDMA channel activity
+
+The estimated mean TDMA channel activity is shown in table 6.
+
+**Table 6: Calculation of mean TDMA channel activity**
+
+|                             |      |
+|-----------------------------|------|
+| speech channel activity     | 55 % |
+| level compensation          | 3 %  |
+| 240 ms SID update period    | 2 %  |
+| interleaving compensation   | 2 %  |
+| total TDMA channel activity | 62 % |
+
+# 11 Performance with DTMF tones
+
+## 11.1 Introduction
+
+In the fixed telephone system, DTMF (Dual Tone Multi Frequency) signals are transmitted in the speech channel for signalling. This has led to the use of DTMF tones for applications such as the control of answering machines and mail/messaging boxes. In the GSM system, the handling of these signalling tones is dependant on the direction the signal is travelling. If it is in the uplink (from the mobile station to the network), the signalling channel is used, rather than the speech channel. In the downlink (from the network to the mobile station), these tones are carried in the speech channel. Even though it was not a requirement for the half rate speech channel to be able to carry these tones in the downlink, their transmission was tested.
+
+## 11.2 Test set-up
+
+16 DTMF signals are defined representing the 10 numeric keys, the characters "A", "B", "C", "D", "\*" and "#". Each digit consists of two sine signals of distinctive frequencies, one chosen out of 4 values from the low frequency group (or row frequency), and one out of the 4 values from the high frequency group (column frequency). Both frequencies are sent simultaneously ideally with same amplitude and at exact frequency values. For practical use, certain tolerances of the frequencies and of the signal amplitudes are specified.
+
+A DTMF receiver must be capable of detecting these tones. It should detect all the DTMF tones even under noisy conditions or when speech is present. Also, it should not interpret other signals from the voice band as valid tones. The tones can only be distinguished by their specific frequency and amplitude composition so it is important, if they are to be recognized by the half rate system, that they conform to the CEPT recommendation T/CS 46-02 (1985). Among others, the difference in the amplitudes of the 2 components (twist) shall not exceed 6 dB. The minimum signal length from sending unit is 75 ms while a 40 ms signal should be detected at the receiver side. Pauses from the generator shall last 65 ms while the receiver shall detect 20 ms.
+
+The DTMF tests were done at nominal frequencies with different pulse and pause duration and different amplitude levels on a PC based set-up. DTMF signal files were generated by means of a DTMF software package for the 16 signals with 10 samples for each tone. After processing with the HR-codes software, the result files were input to a DSP based hardware with a standard DTMF recognition S/W meeting CEPT requirements. All experiments were done also with modified DTMF receiver software. The tables in subclause 11.5 list the number of recognized tones.
+
+All dB values mentioned are for each individual component of the DTMF signal, with reference to the overload point.
+
+## 11.3 Results
+
+The results of the test with a standard DTMF detector are shown in table 7. Even at ideal conditions with nominal DTMF signal frequencies, no additional signals in the speech band, and error free transmission, the recognition is poor after processing. Only with a relatively high level of -12 dB and a tone length of 80 ms is a 100 % recognition achieved. Under all other conditions at least one tone shows severe problems. There is no linearity in this experiment, e.g. "4" is recognized well at -18 dB level but very poor at -22 dB while "7" shows the opposite behaviour. Also, when the twist is reversed, the results differ in ways which depend on the code being transmitted. The recognition of very short tones (40 ms) is not acceptable, and the longer tones (120 ms) are problematical too.
+
+A reason for the poor behaviour might be a time dependent twist generated by the GSM Half Rate codec when one of the two components develops differently from the other due to the non-linear behaviour of the codec. For more than 40 ms the twist at certain DTMF tones was observed to be greater than 6 dB and thus out of the allowed range of the specification of standard DTMF receivers. In experiment (h) with -12/-18 dB signals and 120 ms tones, 10 inputs of "A" resulted in 12 recognitions. A slow oscillation of the signal amplitudes may have generated a twist of more than 6 dB for longer than 20 ms. This made the detector observe a valid pause and a new tone, increasing the number of detected tones above the number of input tones. This might have happened also for other tones under the condition (h) where e.g. 10 detected tones may result of 8 correct detections, a double detection from one input and one failure. The test equipment could not decide such effects - as also in practise just the result counts. At 80 ms twist signals, such slow oscillations do not have the same effect because under no condition a valid 2nd tone can be detected ( $40+20+40 > 80$ ).
+
+Table 8 shows the results of the same experiments as described above with a DTMF detector tuned for recognition in GSM half rate speech codec transmission. Using knowledge of the possible reasons for detection errors in the tuned detector, the detection rate was improved. However, even at the still ideal signal conditions as described above, the results were not satisfactory where there was severe twist or short (40 ms) tones. Also, the modifications may well increase the acceptance of non-DTMF signals as valid DTMF tones. This, however, was not tested.
+
+## 11.4 Conclusions
+
+With the standard detector the recognition rate averaged over all experiments was 74 %. The tuning of the detector for the half rate channel characteristics could improve the detection rate to 92 %. As all experiments still had rather ideal conditions, in real application an even lower rate for detection has to be assumed, also due to the misinterpretation of other signals in the modified detector.
+
+In conclusion, a serious commercial application using DTMF in the speech channel should not be supported with the GSM half rate codec.
+
+## 11.5 Result tables of experiments with standard and modified DTMF detectors
+
+The tables below list the numbers of detected tones from 10 input signals at each tested condition. For twist conditions, the pair of level figures indicate the level of row frequencies and column frequencies respectively.
+
+**Table 7: Summary of DTMF tests with standard DTMF detector**
+
+| Condition\Tone                          | 1  | 2  | 3  | A          | 4  | 5  | 6  | B  | 7  | 8  | 9  | C  | *  | 0  | #  | D  | Total |
+|-----------------------------------------|----|----|----|------------|----|----|----|----|----|----|----|----|----|----|----|----|-------|
+| (a) -12 dB, 40 ms                       | 5  | 2  | 9  | 10         | 0  | 8  | 1  | 5  | 10 | 5  | 3  | 0  | 0  | 10 | 10 | 9  | 87    |
+| (b) -12 dB, 80 ms                       | 10 | 10 | 10 | 10         | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160   |
+| (c) -18 dB, 80 ms                       | 10 | 10 | 10 | 10         | 10 | 10 | 8  | 10 | 1  | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 149   |
+| (d) -22 dB, 80 ms                       | 10 | 10 | 10 | 10         | 4  | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 154   |
+| (e) 3 dB twist, -12/-15 dB, 80 ms       | 10 | 10 | 10 | 10         | 10 | 10 | 10 | 10 | 7  | 10 | 10 | 10 | 0  | 10 | 10 | 10 | 147   |
+| (f) 6 dB twist, -12/-18 dB, 80 ms       | 0  | 1  | 0  | 10         | 0  | 10 | 0  | 10 | 0  | 10 | 0  | 4  | 0  | 0  | 10 | 0  | 55    |
+| (g) 6 dB tw. reverse, -18/-12 dB, 80 ms | 10 | 10 | 4  | 10         | 6  | 3  | 0  | 0  | 0  | 0  | 10 | 10 | 0  | 0  | 6  | 10 | 79    |
+| (h) 6 dB twist, -12/-18 dB, 120 ms      | 8  | 3  | 9  | 12<br>note | 7  | 10 | 5  | 10 | 0  | 10 | 7  | 9  | 3  | 10 | 10 | 9  | 122   |
+| Total                                   | 63 | 56 | 62 | 82         | 47 | 71 | 44 | 65 | 38 | 65 | 60 | 63 | 33 | 60 | 76 | 68 | 953   |
+
+NOTE: 10 input signals in this test case resulted in 12 recognized tones. An explanation is given in subclause 11.3.
+
+**Table 8: Summary of DTMF tests with modified DTMF detector**
+
+| Condition\Tone                          | 1  | 2  | 3  | A  | 4  | 5  | 6  | B  | 7  | 8  | 9  | C  | *  | 0  | #  | D  | Total |
+|-----------------------------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|-------|
+| (a) -12 dB, 40 ms                       | 9  | 10 | 8  | 1  | 0  | 8  | 4  | 10 | 10 | 10 | 8  | 9  | 8  | 10 | 6  | 8  | 119   |
+| (b) -12 dB, 80 ms                       | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160   |
+| (c) -18 dB, 80 ms                       | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160   |
+| (d) -22 dB, 80 ms                       | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160   |
+| (e) 3 dB twist, -12/-15 dB, 80 ms       | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 160   |
+| (f) 6 dB twist, -12/-18 dB, 80 ms       | 10 | 10 | 10 | 10 | 10 | 10 | 6  | 10 | 0  | 10 | 6  | 10 | 0  | 10 | 10 | 0  | 122   |
+| (g) 6 dB tw. reverse, -18/-12 dB, 80 ms | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 10 | 7  | 10 | 10 | 10 | 7  | 0  | 10 | 10 | 144   |
+| (h) 6 dB twist, -12/-18 dB, 120 ms      | 10 | 8  | 10 | 10 | 10 | 10 | 8  | 10 | 8  | 10 | 10 | 10 | 8  | 10 | 10 | 10 | 152   |
+| Total                                   | 79 | 78 | 78 | 71 | 70 | 78 | 68 | 80 | 65 | 80 | 74 | 79 | 63 | 70 | 76 | 68 | 1177  |
+
+# 12 Performance with signalling tones
+
+The capability of the codec to transmit network information tones was assessed with 5 French signalling tones following the IUT-T recommendation: "Warn" tone, "Busy" tone, "Ring" tone, "Inf" tone and "Pay" tone (tones of length 200 ms to 1 s and silences between tones of length 30 ms to 4 s).
+
+All signalling tones are recognized. However, the half rate codec introduces a very audible distortion and performs significantly worse than the full rate codec.
+
+None of the tones is perturbed by the VAD/DTI system.
+
+# --- 13 Delay
+
+[tbd]
+
+# --- 14 Frequency response
+
+The frequency response of the GSM half rate codec, has been evaluated by computing the logarithmic gain.
+
+The codec has been tested in error free condition only, without DTX associated, by independently processing 198 sine waves files spaced by 20 Hz and spanning the range between 50 to 3 990 Hz. Each file had a duration of 8 seconds and the input signal level was fixed at -22 dB ( $V_{max} = 2\ 603$ ).
+
+The gain of the codec has been calculated by means of the formula:
+
+$$gain = 10 * \log_{10} \left( \frac{\sum_i (out_i)^2}{\sum_i (inp_i)^2} \right)$$
+
+Figures 1 and 2 report the logarithmic gain for the whole range of tones considered and for telephone bandwidth respectively.
+
+Both figures show that the codec provide a flat frequency response in the telephone bandwidth, with the algorithmic gain confined in the range  $\pm 0,2$  dB with a very few outliers.
+
+The highest attenuation observed is 0,65 dB and occurs at 1 150 Hz.
+
+It shall be noted that small deviations from these figures can be observed by using different levels and/or different initial phases for the sinewave signals.
+
+![Figure 1: Frequency response for the whole bandwidth considered. The graph shows gain [dB] on the y-axis (from -25 to 5) versus frequency [Hz] on the x-axis (from 0 to 4000). The gain is flat at 0 dB across the entire frequency range, with a slight dip at 1150 Hz.](88362167d90777ecb0aeb145832e78c2_img.jpg)
+
+The figure is a line graph showing the frequency response of a codec. The y-axis is labeled 'gain [dB]' and ranges from -25 to 5 in increments of 5. The x-axis is labeled 'frequency [Hz]' and ranges from 0 to 4000 in increments of 500. The plot shows a single data series representing the gain across the frequency spectrum. The gain is approximately 0 dB for most frequencies, with a very slight downward dip at 1150 Hz, reaching about -0.65 dB. The overall response is flat across the entire bandwidth from 50 Hz to 3990 Hz.
+
+Figure 1: Frequency response for the whole bandwidth considered. The graph shows gain [dB] on the y-axis (from -25 to 5) versus frequency [Hz] on the x-axis (from 0 to 4000). The gain is flat at 0 dB across the entire frequency range, with a slight dip at 1150 Hz.
+
+**Figure 1: Frequency response for the whole bandwidth considered**
+
+![Figure 2: Frequency response in the telephone bandwidth. The graph shows gain [dB] on the y-axis (from -0.7 to 0.3) versus frequency [Hz] on the x-axis (from 0 to 3500). The data points are connected by lines, showing a highly irregular response with many peaks and dips. The gain is generally between -0.1 dB and 0.2 dB, with a significant dip around 1100 Hz reaching approximately -0.65 dB. Another sharp dip occurs around 3300 Hz reaching approximately -0.3 dB.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg)
+
+Figure 2: Frequency response in the telephone bandwidth. The graph shows gain [dB] on the y-axis (from -0.7 to 0.3) versus frequency [Hz] on the x-axis (from 0 to 3500). The data points are connected by lines, showing a highly irregular response with many peaks and dips. The gain is generally between -0.1 dB and 0.2 dB, with a significant dip around 1100 Hz reaching approximately -0.65 dB. Another sharp dip occurs around 3300 Hz reaching approximately -0.3 dB.
+
+**Figure 2: Frequency response in the telephone bandwidth**
+
+# 15 Half Rate codec complexity
+
+The complexity of the half rate codec is characterized by the 3 following items:
+
+- the number of cycles;
+- the data memory size;
+- the program memory size.
+
+The values of these different figures depend on a specific DSP implementation. Nevertheless, the results obtained by the C description analysis can be used as references.
+
+The speech transcoding functions are specified using a set of basic arithmetic operations. The wMOPs figure quoted is a weighted sum of the operations required to perform transcoding. The weight assigned to each operation is representative of the number of instruction cycles required to perform that operation on a typical DSP device.
+
+The complexity range of the half rate codec is approximately 4,5 times that of the full rate codec.
+
+The number of cycles required by the half rate algorithm is highly dependent on the values of input samples. The execution time of an average and an extreme input case may differ by up to 20 %.
+
+That is why, to evaluate the complexity, it is necessary to compute the theoretical worst case, i.e. the maximum possible number of cycles, and not just observe the results of a simulation.
+
+The principal figures of this evaluation are the following:
+
+**Table 9: Principal figures of evaluation**
+
+|                                                              | Theoretical worst case wMOPs | Data RAM (note) (16 bits words) | Data ROM (constants) (16 bits words) | Program ROM (assembly instructions) |
+|--------------------------------------------------------------|------------------------------|---------------------------------|--------------------------------------|-------------------------------------|
+| Speech and channel half rate codec (excluding DTX functions) | 21,2                         | 5 002                           | 8 781                                | 8 000-12 000                        |
+| Ratio half rate vers. full rate                              | 4,5                          | 2,4                             | 9,7                                  | 4                                   |
+
+NOTE: The Data RAM figure can be split in 2 parts: the static variables: 2 100 words; and the dynamic variables (i.e. local to a procedure): 2 900 words.
+
+# 16 Summary of results from characterization Phase 1 and 2
+
+The whole set of individual and global data were extensively analysed and discussed within the TCH-HS expert group. The effects of different factors and their interactions were subject to analysis of variance (ANOVA). Tables 10 to 14 report the results obtained in 9 experiments.
+
+## 16.1 Summary of Results From Characterization Phase 1
+
+The whole set of individual and global data were extensively analysed and discussed within the TCH-HS expert group. The effects of different factors and their interactions were subject to analysis of variance (ANOVA). Tables 10 to 14 report the results obtained in 9 experiments.
+
+**Table 10: Summary of Characterization Phase 1 Results - Differential Q values**
+
+| Diff Q (dB)                          |                                                   |                            |                   |
+|--------------------------------------|---------------------------------------------------|----------------------------|-------------------|
+| exc.<br>(UPCM, No-IRS)<br>Exp. 1 - 3 | EP3<br>(A law-IRS and UPCM, No-IRS)<br>Exp. 1 - 3 | Noise only<br>Exp. 4 and 5 | All<br>Exp. 1 - 5 |
+| -1,09                                | -1,45                                             | -3,01                      | -2,29             |
+
+NOTE: The figures indicate DQ values in dB averaged over input level,
+
+$$\text{where } DQ = Q_{HR} - Q_{FR}.$$
+
+**Table 11: Summary of Characterization Phase 1 Results (Exp. 1, 2 and 3)**
+
+| Audio part         | Single Encoding Conditions |       |         |           | Tandemizing Conditions |       | All      | All          |
+|--------------------|----------------------------|-------|---------|-----------|------------------------|-------|----------|--------------|
+|                    | EP0                        | EP0/1 | EP0/1/2 | EP0/1/2/3 | EP0                    | EP0/1 | exc. EP3 |              |
+| 1.A-Law IRS        | +0,01                      | -0,32 | -0,43   | +0,12     | -0,32                  | -0,34 | -0,41    | +0,02        |
+| 2.NoIRS, LinearPCM | -2,16                      | -2,13 | -1,82   | -0,90     | -4,98                  | -4,50 | -2,49    | -1,62        |
+| 1 and 2.           | -1,08                      | -1,22 | -1,12   | -0,39     | -2,65                  | -2,42 | -1,45    | <b>-0,80</b> |
+
+NOTE: Dependence on Specific Conditions without Background Noise. The figures indicate DQ values in dB averaged over input level,
+
+$$\text{where } DQ = Q_{HR} - Q_{FR}.$$
+
+**Table 12: Summary of Characterization Phase 1 Results (Exp. 4 and 5)-**
+
+| Audio part | Office Babble | Vehicle | Traffic | No Tandemizing | With Tandemizing | All   |
+|------------|---------------|---------|---------|----------------|------------------|-------|
+| A-Law IRS  | -2,64         | -3,19   | -3,20   | -2,10          | -3,93            | -3,01 |
+
+NOTE: Differential Q values in Noise Conditions. The figures indicate DQ values in dB averaged over input level,
+
+where  $DQ = Q_{HR} - Q_{FR}$ .
+
+**Table 13: Summary of Characterization Phase 1 Results - Significant differences (Experiment 1 to Experiment 5)**
+
+| Laboratory       | Experiment 1 | Experiment 2 | Experiment 3 | Experiment 4 | Experiment 5 |
+|------------------|--------------|--------------|--------------|--------------|--------------|
+| BT               | HR = FR      | HR < FR      | HR < FR      | HR < FR      | x            |
+| CNET             | x            | x            | x            | x            | HR < FR      |
+| CSELT            | HR = FR      | HR = FR      | HR = FR      | x            | HR < FR      |
+| Deutsche Telekom | HR = FR      | HR = FR      | HR < FR      | HR < FR      | x            |
+| Global           | HR = FR      | HR < FR      | HR < FR      | HR < FR      | HR < FR      |
+
+NOTE: See legend in subclause 16.2 for symbol explanation.
+
+## 16.2 Summary of Results From Characterization Phase 2
+
+**Table 14: Summary of Characterization Phase 2 Results (Experiment 6 to Experiment 9)**
+
+| Subject:   | qdu                      | Tandem with other Standards | Talker Dependency | DTX Functions                                                  |
+|------------|--------------------------|-----------------------------|-------------------|----------------------------------------------------------------|
+| Laboratory | Experiment 6             | Experiment 7                | Experiment 8      | Experiment 9                                                   |
+| BT         |                          | HR+any < any+HR             | see clause 9      | DTX operation appears to be satisfactory.                      |
+| CNET       |                          | HR+any < any+HR             |                   | DTX fairly satisfactory, concerns over CNI.                    |
+| CSELT      | HR = FR<br>HR+HR < FR+FR |                             |                   | DTX satisfactory, concerns over CNI and comfort noise quality. |
+| DBP        | HR = FR<br>HR+HR = FR+FR |                             | see clause 9      | DTX fairly satisfactory, concerns over comfort noise quality.  |
+
+### Legend
+
+| Symbol | Definition                                                   |
+|--------|--------------------------------------------------------------|
+| =      | no significant difference at the 95 % confidence level       |
+| HR     | Half rate codec                                              |
+| FR     | Full rate codec                                              |
+| x      | Experiment not performed by laboratory                       |
+| HR<FR  | HR significantly worse than FR at the 95 % confidence level. |
+| any    | All tested codecs, except HR (G.726 [2], G.728 [3], and FR)  |
+
+The candidate codec performed equally well or slightly worse than the full rate for most cases, the overall figure of merit being **-0,8 dB** (weighted) signal-to-quantization distortion (without taking into account the noise conditions). The requirement was to provide a half rate standard with speech quality approximately equivalent to the GSM full rate codec with 1 dB of tolerance in terms of equivalent (weighted) signal-to-quantization distortion.
+
+Under UPCM No IRS audio part conditions, particularly when tandemed, the full rate performed consistently better than the half-rate.
+
+In environmental noise conditions, formal tests using two different methods, ACR and DCR were used to determine the difference in performance between the full and half-rate systems. It was found that differential Q (dB) values (comparing full and half-rate codecs) are more pronounced when using the DCR procedure than when using the ACR procedure, leading to a larger measured difference between the systems in the DCR experiments. The half-rate always performed worse than the full rate under the noise conditions, often with the difference in performance falling outside the -3 dB limit.
+
+TCH-HS significantly improved the methodology for measuring subjectively the performance of candidate codec. Since the most important requirements set by SMG and tested by TCH-HS were met by the optimized algorithm, SMG approved the optimized codec.
+
+Further information can be found in annex A reference 9).
+
+## 16.3 Conclusion
+
+A subjective test methodology for the quality assessment of ETSI's half rate algorithm has been implemented, based on listening opinion tests.
+
+The test methodology reflected international telephony assessment methods that are described extensively in the ITU-T Series P Recommendations, and that have shown to be suitable for characterizing both the GSM full rate and half rate algorithm performance. Results of tests conducted by several organizations showed consistency when normalized to Equivalent Q, in terms of the relative performance of the half rate algorithm and full rate RPE-LTP, removing the effect of differences in absolute performance, due to different languages, interpretation of quality scales, etc.
+
+By considering the average performance across all countries, it was concluded that the half rate algorithm performance was comparable to RPE-LTP in all the experimental conditions tested, except for tandeming and background noise conditions, and met the initial requirements set out by SMG.
+
+The results confirmed that the performance of the half rate codec falls short of that normally experienced on the PSTN.
+
+For network planning purposes, it is proposed that the same rules will be adopted as for RPE-LTP, which will be adequate for most applications.
+
+# --- Annex A: Bibliography
+
+- 1) IEEE Proceedings. GLOBECOM'84, Vol. 2, pp.778-785, G. Williams and H. Suyderoud (1984): "Subjective performance evaluation of the 32-kbit/s ADPCM algorithm".
+- 2) IEEE Proceedings GLOBECOM '86, Houston, Texas, pp. 599-604, G. Modena, A. Coleman, P. Coverdale, P. Usai (1986): "Subjective performance evaluation of the 64 kbit/s (7 kHz) audio coder".
+- 3) A. Coleman, N. Gleiss, P. Usai, Speech Communication, Vol. 7, , pp.151-166, (June 1988): "A subjective testing methodology for evaluating Medium Rate Codecs for Digital Mobile Radio applications".
+- 4) IEEE Proceedings GLOBECOM '89, Dallas, Texas, pp. 1075-1079, A. Coleman, N. Gleiss, J. Sotscheck, H.Scheuermann, P. Usai (1989): "Subjective performance evaluation of the RPE-LTP codec for the Pan-European cellular digital mobile radio system".
+- 5) C. South et alii (1993), Speech Communication Vol. 13, pp.113-132: "Subjective Test Methodology for a 16 kbit/s Speech Coder".
+- 6) ITU-T Recommendation P.80 (1992): "Methods for subjective determination of transmission quality".
+- 7) ITU-T Recommendation P.81 (1988): "Modulated Noise Reference Unit",
+- 8) ITU-T Recommendation P.83 (1992): "Subjective performance assessment of telephone-band and wideband digital codecs"
+- 9) ICC '95, Session 2.2.2, P. Usai et alii (June 1995): "Subjective performance evaluation of the GSM Half Rate Speech Coding Algorithm (with voice signals)".
+
+# Annex B: Change history
+
+| Change history |           |         |                  |             |                      |
+|----------------|-----------|---------|------------------|-------------|----------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments     |
+| SMG#16         |           |         |                  | 4.0.0       | ETSI Publication     |
+| SMG#20         |           |         |                  | 5.0.0       | Release 1996 version |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version |
+
+| Change history |       |          |    |     |                                |        |        |
+|----------------|-------|----------|----|-----|--------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment                | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4          |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5          | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6          | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7          | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8          | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9          | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10         | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11         | 10.0.0 | 11.0.0 |
+| 10-2012        |       |          |    |     | Replacement of figures 1 and 2 | 11.0.0 | 11.0.1 |
+| 09-2014        | 65    |          |    |     | Version for Release 12         | 11.0.1 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13         | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46011/raw.md b/marked/Rel-16/46_series/46011/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..a194f8d867314b6d59b25fb3dc85f6205652ce7c
--- /dev/null
+++ b/marked/Rel-16/46_series/46011/raw.md
@@ -0,0 +1,170 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                            |   |
+|--------------------------------------------|---|
+| Foreword .....                             | 4 |
+| 1 Scope.....                               | 5 |
+| 2 References.....                          | 5 |
+| 3 Definitions and abbreviations .....      | 5 |
+| 4 General .....                            | 5 |
+| 5 Requirements .....                       | 5 |
+| 5.1 First lost speech frame.....           | 5 |
+| 5.2 Subsequent lost speech frames.....     | 6 |
+| 5.3 First lost SID frame .....             | 6 |
+| 5.4 Subsequent lost SID frame .....        | 6 |
+| 6 Example solution.....                    | 6 |
+| Annex A (informative): Change history..... | 8 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document defines a frame substitution and muting procedure which shall be used by the RX DTX handler when one or more lost speech or SID frames are received from the radio subsystem.
+
+The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS) and Mobile Stations (MS).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding".
+- [3] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channel".
+
+# --- 3 Definitions and abbreviations
+
+Abbreviations used in the present document are listed in GSM 01.04 [1].
+
+The definitions of terms used in the present document can be found in GSM 06.31 [3].
+
+# --- 4 General
+
+The purpose of the frame substitution is to conceal the effect of lost frames.
+
+The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user.
+
+# --- 5 Requirements
+
+## 5.1 First lost speech frame
+
+Normal decoding of lost speech frames would result in very unpleasant noise effects. In order to improve the subjective quality, the first lost speech frame shall be substituted with either a repetition or an extrapolation of the previous good speech frame(s). Lost speech frames shall not be delivered to the speech decoder, nor shall the output be muted directly.
+
+## 5.2 Subsequent lost speech frames
+
+For subsequent lost speech frames, a muting technique shall be used that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. Clause 6 gives an example solution.
+
+## 5.3 First lost SID frame
+
+A single lost SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied as described in GSM 06.31 [3].
+
+## 5.4 Subsequent lost SID frame
+
+For the second lost SID frame, a muting technique shall be used on the comfort noise that will gradually decrease the output level, resulting in silencing of the output after a maximum of 320 ms. Clause 6 gives an example solution.
+
+For subsequent lost SID frames, the muting of the output shall be maintained.
+
+# --- 6 Example solution
+
+For guidance, an example solution is given.
+
+The first lost speech frame is replaced at the speech decoder input by the previous good speech frame. Normal decoding is then performed.
+
+The muting procedure to be used in the case of subsequent lost speech frames or for comfort noise frames following the second lost SID frame is as follows:
+
+The pseudo-logarithmic encoded block amplitude  $X_{maxcr}$  (GSM 06.10 [2]), coded on the interval from 0 to 63, is decreased with a constant value  $d=4$  in each frame, down to the lowest possible value. Consequently,  $X_{maxcr}$  will be reduced gradually, and the output muted after a maximum of 320 ms. The grid position parameters are chosen randomly between 0 and 3 during this time.
+
+For subsequent unusable frames, after the frame where  $X_{maxcr}$  reached the lowest possible value, "silence frames" are passed from the RX DTX handler to the speech decoder to guarantee a low output level under all conditions. The silence frame is defined in table 1.
+
+**Table 1: Encoded parameters (GSM 06.10) of the silence frame**
+
+|                  |   |    |                                |
+|------------------|---|----|--------------------------------|
+| Log area ratio 1 | = | 42 |                                |
+| Log area ratio 2 | = | 39 |                                |
+| Log area ratio 3 | = | 21 |                                |
+| Log area ratio 4 | = | 10 |                                |
+| Log area ratio 5 | = | 9  |                                |
+| Log area ratio 6 | = | 4  |                                |
+| Log area ratio 7 | = | 3  |                                |
+| Log area ratio 8 | = | 2  |                                |
+|                  |   |    |                                |
+| LTP gain         | = | 0  |                                |
+| LTP lag          | = | 40 |                                |
+|                  |   |    |                                |
+| Grid position    | = | 1  |                                |
+| Block amplitude  | = | 0  |                                |
+|                  |   |    |                                |
+| RPE pulse no. 1  | = | 3  |                                |
+| RPE pulse no. 2  | = | 4  |                                |
+| RPE pulse no. 3  | = | 3  |                                |
+| RPE pulse no. 4  | = | 4  |                                |
+| RPE pulse no. 5  | = | 4  |                                |
+|                  |   |    |                                |
+| RPE pulse no. 6  | = | 3  | - repeated for each subsegment |
+| RPE pulse no. 7  | = | 3  |                                |
+| RPE pulse no. 8  | = | 3  |                                |
+| RPE pulse no. 9  | = | 3  |                                |
+| RPE pulse no. 10 | = | 4  |                                |
+| RPE pulse no. 11 | = | 4  |                                |
+| RPE pulse no. 12 | = | 3  |                                |
+| RPE pulse no. 13 | = | 3  |                                |
+|                  |   |    |                                |
+|                  |   | _  |                                |
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                  |             |                                                                   |
+|----------------|-----------|---------|------------------|-------------|-------------------------------------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                                                  |
+| SMG#07         |           |         |                  | 4.0.4       | ETSI Publication                                                  |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                                              |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                                              |
+| SMG#28         |           |         |                  | 6.0.1       | ETSI Publication                                                  |
+| SMG#29         |           |         |                  | 7.0.0       | Specification version 6.0.0 upgrade to Release 1998 version 7.0.0 |
+|                |           |         |                  | 7.0.1       | Version update for Publication                                    |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                                              |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46012/raw.md b/marked/Rel-16/46_series/46012/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..79ba3926d8b6ccf4730d6b0dae903f4eb2c8c4fc
--- /dev/null
+++ b/marked/Rel-16/46_series/46012/raw.md
@@ -0,0 +1,170 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                 |   |
+|-------------------------------------------------|---|
+| Foreword .....                                  | 4 |
+| 1 Scope.....                                    | 5 |
+| 2 References.....                               | 5 |
+| 3 Definitions and abbreviations .....           | 5 |
+| 4 General.....                                  | 5 |
+| 5 Functions on the transmit side .....          | 6 |
+| 5.1 Background acoustic noise evaluation .....  | 6 |
+| 5.2 SID-frame encoding .....                    | 6 |
+| 6 Functions on the receive side.....            | 7 |
+| 6.1 Comfort noise generation and updating ..... | 7 |
+| Annex A (informative): Change history.....      | 8 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on full rate speech traffic channels.
+
+The requirements described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [3] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding".
+- [4] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channel".
+
+# --- 3 Definitions and abbreviations
+
+Definitions and abbreviations used in the present document are listed in GSM 01.04 [1].
+
+The definitions of terms used in this technical specification can be found in GSM 06.31 [4].
+
+# --- 4 General
+
+The overall operation of Discontinuous Transmission is described in GSM 06.31 [4].
+
+A basic problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is cut, resulting in a modulation of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect can be very annoying for the listener - especially in a car environment with high background noise levels. In bad cases the speech may be hardly intelligible.
+
+The present document specifies the way to overcome this problem by generating on the receive side synthetic noise similar to the transmit side background noise. The parameters of this so called comfort noise are estimated on the transmit side and transmitted to the receive side before the radio transmission is cut and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the transmit side.
+
+# 5 Functions on the transmit side
+
+The comfort noise evaluation algorithm uses the unquantized block amplitude and Log Area Ratio (LAR) parameters of the full rate speech encoder, defined in subclauses 4.2.15 and 4.2.6 of GSM 06.10 [3]. These parameters give information on the level and the spectrum of the background noise, respectively.
+
+The evaluated comfort noise parameters are encoded into a special frame, called a SID (Silence Descriptor) frame, for transmission to the receive side.
+
+The SID frame also serves to initiate the comfort noise generation on the receive side, as a SID frame is always sent at the end of a speech burst, i.e. before the radio transmission is cut.
+
+The scheduling of SID or speech frames on the radio path is described in GSM 06.31 [4].
+
+## 5.1 Background acoustic noise evaluation
+
+The comfort noise parameters to be encoded into a SID frame are calculated over  $N=4$  consecutive frames marked with VAD=0, as follows:
+
+The Log Area Ratio parameters shall be averaged according to the equation:
+
+$$\text{mean (LAR}(i)) = \frac{1}{N} \sum_{n=1}^N \text{LAR} [j - n](i) \quad i = 1, 2..8$$
+
+where  $\text{LAR}[j](i)$  is the  $i$ 'th Log Area Ratio coefficient of the current frame  $j$  and  $j-n$  indicates the previous frames.
+
+The block amplitude parameter shall be averaged according to the equation:
+
+$$\text{mean (}x_{\max}\text{)} = \frac{1}{(4N)} \sum_{n=1}^N \sum_{i=1}^4 x_{\max} [j - n](i)$$
+
+where  $x_{\max}[j](i)$  is the block amplitude in sub-segment  $i$  of the current frame. The SID frame containing these averaged parameters is passed to the Radio Subsystem instead of frame number  $j$ .
+
+## 5.2 SID-frame encoding
+
+The SID-frame encoding algorithm exploits the fact that only some of the 260 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID-frame by means of a fixed bit pattern, called the SID code word.
+
+The log area ratio coefficients are replaced by the mean ( $\text{LAR}(i)$ ) values defined above and encoded as described in GSM 06.10 [3].
+
+The block amplitude values are replaced by the mean ( $x_{\max}$ ) value defined above, repeated four times inside the frame and encoded as described in GSM 06.10 [3].
+
+The SID code word consists of 95 bits which are all zero. The bits of the SID code word are inserted in the SID field defined as the positions of those 95 bits of the encoded RPE-pulses  $X_{mc}$ , which are in the error protection class I (see GSM 05.03 [2], table 2).
+
+The remaining bits in the SID frame are set to zero. The use of these bits is for further study.
+
+# --- 6 Functions on the receive side
+
+The situations in which comfort noise shall be generated on the receive side are defined in GSM 06.31 [4]. Generally speaking, the comfort noise generation is started or updated whenever a valid SID frame is received.
+
+## 6.1 Comfort noise generation and updating
+
+The comfort noise generation procedure uses the RPE-LTP speech decoder algorithm defined in GSM 06.10 [3].
+
+When comfort noise is to be generated, then the various encoded parameters are set as follows.
+
+The RPE pulses ( $X_{mcr}$ ) are replaced by a locally generated random integer sequence, uniformly distributed between 1 and 6.
+
+Also the grid position parameters ( $M_{cr}$ ) are set to random integer values, uniformly distributed between 0 and 3.
+
+The LTP gain values ( $b_{cr}$ ) are set to 0.
+
+The LTP lag values ( $N_{cr}$ ) of the 4 sub-segments are set to 40, 120, 40 and 120 respectively.
+
+The 4 block amplitude values ( $X_{maxcr}$ ) used are those received in the SID frame.
+
+The log area ratio parameters ( $LAR_{cr}$ ) used are those received in the SID frame.
+
+With these parameters, the speech decoder now performs the standard operations described in GSM 06.10 [3] and synthesizes comfort noise.
+
+Updating of the comfort noise parameters occurs each time a valid SID frame is received, as described in GSM 06.31 [4].
+
+When updating the comfort noise, the parameters above should preferably be interpolated over a few frames to obtain smooth transitions.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#07         |           |         |                  | 4.0.4       | ETSI Publication                        |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                    |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+
+| Change history |       |           |     |     |                                               |        |        |
+|----------------|-------|-----------|-----|-----|-----------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR  | Rev | Subject/Comment                               | Old    | New    |
+| 03-2001        | 11    |           |     |     | Version for Release 4                         |        | 4.0.0  |
+| 06-2001        | 12    | SP-010304 | 001 |     | Corrections of the formula for averaging Xmax | 4.0.0  | 4.1.0  |
+| 06-2002        | 16    |           |     |     | Version for Release 5                         | 4.1.0  | 5.0.0  |
+| 12-2006        | 26    |           |     |     | Version for Release 6                         | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |           |     |     | Version for Release 7                         | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |           |     |     | Version for Release 8                         | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |           |     |     | Version for Release 9                         | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |           |     |     | Version for Release 10                        | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |           |     |     | Version for Release 11                        | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |           |     |     | Version for Release 12                        | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |           |     |     | Version for Release 13                        | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46020/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/46_series/46020/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2de0e1e33812a2bcfcded03e6973898d8acd24c6
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/1eadbbe42cfcac5c0023577110aec5e3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4e0be5ffa45c6259442d2636f4d364b90a293b1c0d2f2057c07c112bdd9406b9
+size 36366
diff --git a/marked/Rel-16/46_series/46020/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/46_series/46020/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0066646415d4e5d574bb63b1b7b6f1f0b65eda42
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:90362761c87c1ad1c3de19b8a7ac4fc3edb11ec72f6b1ac9722aeb13f16a05b2
+size 23472
diff --git a/marked/Rel-16/46_series/46020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/46_series/46020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..95319ff30583cfc61c1e4f1a03ceb05037cea238
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/9c1d3678db4a12d5864cb2a4def1135d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:893965297886525493b460bdaf2de2fb7d2be950d076305f921b7072df1c923b
+size 82410
diff --git a/marked/Rel-16/46_series/46020/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/46_series/46020/b51423b6c049f5b5fcde42e50b58f18b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2715565f540de218216c48efc11197ec8842b031
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/b51423b6c049f5b5fcde42e50b58f18b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:513523304d2c9bd595df207892f0e42b5d133b42571b7c1e0e2d760a7ef7061c
+size 87516
diff --git a/marked/Rel-16/46_series/46020/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/46_series/46020/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..614fb9bb36a3bc1eb50dfea966afdac5b81e5511
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a67b5df56cd15f5ae7489834915659e88f6613611d477e56dfa8e6639bc7bda2
+size 110329
diff --git a/marked/Rel-16/46_series/46020/raw.md b/marked/Rel-16/46_series/46020/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..baabe414741e9f0646c3d20364266dcb6a10b224
--- /dev/null
+++ b/marked/Rel-16/46_series/46020/raw.md
@@ -0,0 +1,1685 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                      |           |
+|----------------------------------------------------------------------|-----------|
+| Foreword .....                                                       | 5         |
+| 1 Scope.....                                                         | 6         |
+| 2 References.....                                                    | 6         |
+| 3 Definitions, symbols and abbreviations .....                       | 6         |
+| 3.1 Definitions.....                                                 | 6         |
+| 3.2 Symbols.....                                                     | 8         |
+| 3.3 Abbreviations .....                                              | 9         |
+| 4 Functional description of the GSM half rate speech codec .....     | 10        |
+| 4.1 GSM half rate speech encoder .....                               | 10        |
+| 4.1.1 High-pass filter .....                                         | 12        |
+| 4.1.2 Segmentation .....                                             | 13        |
+| 4.1.3 Fixed Point Lattice Technique (FLAT).....                      | 13        |
+| 4.1.4 Spectral quantization .....                                    | 14        |
+| 4.1.4.1 Autocorrelation Fixed Point Lattice Technique (AFLAT) .....  | 14        |
+| 4.1.5 Frame energy calculation and quantization.....                 | 16        |
+| 4.1.6 Soft interpolation of the spectral parameters.....             | 16        |
+| 4.1.7 Spectral noise weighting filter coefficients .....             | 17        |
+| 4.1.8 Long Term Predictor lag determination .....                    | 18        |
+| 4.1.8.1 Open loop long term search initialization.....               | 19        |
+| 4.1.8.2 Open loop lag search.....                                    | 20        |
+| 4.1.8.3 Frame lag trajectory search (Mode $\neq$ 0).....             | 25        |
+| 4.1.8.4 Voicing mode selection .....                                 | 27        |
+| 4.1.8.5 Closed loop lag search .....                                 | 27        |
+| 4.1.9 Harmonic noise weighting.....                                  | 28        |
+| 4.1.10 Code search algorithm.....                                    | 30        |
+| 4.1.10.1 Decorrelation of filtered basis vectors .....               | 31        |
+| 4.1.10.2 Fast search technique .....                                 | 32        |
+| 4.1.11 Multimode gain vector quantization.....                       | 33        |
+| 4.1.11.1 Coding GS and P0.....                                       | 33        |
+| 4.2 GSM half rate speech decoder .....                               | 36        |
+| 4.2.1 Excitation generation.....                                     | 37        |
+| 4.2.2 Adaptive pitch prefilter.....                                  | 37        |
+| 4.2.3 Synthesis Filter .....                                         | 37        |
+| 4.2.4 Adaptive spectral postfilter.....                              | 37        |
+| 4.2.5 Updating decoder states.....                                   | 39        |
+| 5 Homing sequences .....                                             | 39        |
+| 5.1 Functional description .....                                     | 39        |
+| 5.2 Definitions.....                                                 | 39        |
+| 5.3 Encoder homing .....                                             | 40        |
+| 5.4 Decoder homing .....                                             | 40        |
+| 5.5 Encoder home state .....                                         | 40        |
+| 5.6 Decoder home state .....                                         | 40        |
+| <b>Annex A (normative):</b> <b>Codec parameter description .....</b> | <b>41</b> |
+| A.1 Codec parameter description.....                                 | 41        |
+| A.1.1 MODE.....                                                      | 41        |
+| A.1.2 R0.....                                                        | 41        |
+| A.1.3 LPC1 - LPC3.....                                               | 42        |
+| A.1.4 LAG_1 - LAG_4.....                                             | 42        |
+| A.1.5 CODEx_1 - CODEx_4.....                                         | 42        |
+| A.1.6 GSP0_1 - GSP0_4.....                                           | 42        |
+
+A.2 Basic coder parameters ..... 42
+
+**Annex B (normative): Order of occurrence of the codec parameters over Abis ..... 43**
+
+**Annex C (informative): Bibliography ..... 44**
+
+Annex D (informative): Change history..... 45
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the speech codec to be used for the GSM half rate channel for the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".**
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+
+GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the speech codec to be used for the GSM half rate channel. It also specifies the test methods to be used to verify that the codec implementation complies with the present document.
+
+The requirements are mandatory for the codec to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half rate GSM speech traffic channel.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- [2] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- [3] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following definitions apply:
+
+**adaptive codebook:** adaptive codebook is derived from the long term filter state. The lag value can be viewed as an index into the adaptive codebook.
+
+**adaptive pitch prefilter:** in the GSM half rate speech decoder, this filter is applied to the excitation signal to enhance the periodicity of the reconstructed speech. Note that this is done prior to the application of the short term filter.
+
+**adaptive spectral postfilter:** in the GSM half rate speech decoder, this filter is applied to the output of the short term filter to enhance the perceptual quality of the reconstructed speech.
+
+**allowable lags:** set of lag values which may be coded by the GSM half rate speech encoder and transmitted to the GSM half rate speech decoder. This set contains both integer and fractional values (see table 3).
+
+**analysis window:** for each frame, the short term filter coefficients are computed using the high pass filtered speech samples within the analysis window. The analysis window is 170 samples in length, and is centered about the last 100 samples in the frame.
+
+**basis vectors:** set of M, M1, or M2 vectors of length Ns used to generate the VSELP codebook vectors. These vectors are not necessarily orthogonal.
+
+**closed loop lag search:** process of determining the near optimal lag value from the weighted input speech and the long term filter state.
+
+**closed loop lag trajectory:** for a given frame, the sequence of near optimal lag values whose elements correspond to each of the four subframes as determined by the closed loop lag search.
+
+**codebook:** set of vectors used in a vector quantizer.
+
+**Codeword (OR Code):** M, M1, or M2 bit symbol indicating the vector to be selected from a VSELP codebook.
+
+**Delta (LAG) code:** four bit code indicating the change in lag value for a subframe relative to the previous subframe's coded lag. For frames in which the long term predictor is enabled (MODE 1, 2, or 3), the lag for subframe 1 is independently coded using eight bits, and delta codes are used for subframes 2, 3, and 4.
+
+**direct form coefficients:** one of the formats for storing the short term filter parameters. All filters which are used to modify speech samples use direct form coefficients.
+
+**fractional lags:** set of lag values having sub-sample resolution. Note that not every fractional lag value considered in the GSM half rate speech encoder is an allowable lag value.
+
+**frame:** time interval equal to 20 ms, or 160 samples at an 8 kHz sampling rate.
+
+**harmonic noise weighting filter:** this filter exploits the noise masking properties of the spectral peaks which occur at harmonics of the pitch frequency by weighting the residual error less in regions near the pitch harmonics and more in regions away from them. Note that this filter is only used when the long term filter is enabled (MODE = 1, 2 or 3).
+
+**high pass filter:** this filter is used to de-emphasize the low frequency components of the input speech signal.
+
+**integer lags:** set of lag values having whole sample resolution.
+
+**interpolating filter:** FIR filter used to estimate sub-sample resolution samples, given an input sampled with integer sample resolution.
+
+**lag:** long term filter delay. This is typically the pitch period, or a multiple or sub-multiple of it.
+
+**long term filter:** this filter is used to generate the periodic component in the excitation for the current subframe. This filter is only enabled for MODE = 1, 2 or 3.
+
+**LPC coefficients:** Linear Predictive Coding (LPC) coefficients is a generic descriptive term for describing the short term filter coefficients.
+
+**open loop lag search:** process of estimating the near optimal lag directly from the weighted speech input. This is done to narrow the range of lag values over which the closed loop lag search shall be performed.
+
+**open loop lag trajectory:** for a given frame, the sequence of near optimal lag values whose elements correspond to the four subframes as determined by the open loop lag search.
+
+**reflection coefficients:** alternative representation of the information contained in the short term filter parameters.
+
+**residual:** output signal resulting from an inverse filtering operation.
+
+**short term filter:** this filter introduces, into the excitation signal, short term correlation which models the impulse response of the vocal tract.
+
+**soft interpolation:** process wherein a decision is made for each frame to use either interpolated or uninterpolated short term filter parameters for the four subframes in that frame.
+
+**soft interpolation bit:** one bit code indicating whether or not interpolation of the short term parameters is to be used in the current frame.
+
+**spectral noise weighting filter:** this filter exploits the noise masking properties of the formants (vocal tract resonances) by weighting the residual error less in regions near the formant frequencies and more in regions away from them.
+
+**subframe:** time interval equal to 5 ms, or 40 samples at an 8 kHz sampling rate.
+
+**vector quantization:** method of grouping several parameters into a vector and quantizing them simultaneously.
+
+**GSP0 vector quantizer:** process of vector quantization, its intermediate parameters (GS and P0) for the coding of the excitation gains  $\beta$  and  $\gamma$ .
+
+**VSELP codebook:** Vector-Sum Excited Linear Predictive (VSELP) codebook, used in the GSM half rate speech coder, wherein each codebook vector is constructed as a linear combination of the fixed basis vectors.
+
+**zero input response:** output of a filter due to all past inputs, i.e. due to the present state of the filter, given that an input of zeros is applied.
+
+**zero state response:** output of a filter due to the present input, given that no past inputs have been applied, i.e. given the state information in the filter is all zeroes.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                 |                                                                                                                                                                                                                |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| $A(z)$          | Short term spectral filter.                                                                                                                                                                                    |
+| $\alpha_i$      | The LPC coefficients.                                                                                                                                                                                          |
+| $b_L(n)$        | The output of the long term filter state (adaptive codebook) for lag L.                                                                                                                                        |
+| $\beta$         | The long term filter coefficient.                                                                                                                                                                              |
+| $C(z)$          | Second weighting filter.                                                                                                                                                                                       |
+| $e(n)$          | Weighted error signal                                                                                                                                                                                          |
+| $f_j(i)$        | The coefficients of the $j^{\text{th}}$ phase of the 10th order interpolating filter used to evaluate candidate fractional lag values; $i$ ranges from 0 to $P_f-1$ .                                          |
+| $g_j(i)$        | The coefficients of the $j^{\text{th}}$ phase of the 6th order interpolating filter used to interpolate C's and G's as well as fractional lags in the harmonic noise weighting; $i$ ranges from 0 to $P_g-1$ . |
+| $\gamma$        | The gain applied to the vector(s) selected from the VSELP codebook(s).                                                                                                                                         |
+| H               | A M2 bit code indicating the vector to be selected from the second VSELP codebook (when operating in mode 0).                                                                                                  |
+| I               | A M or M1 bit code indicating the vector to be selected from one of the two first VSELP codebooks.                                                                                                             |
+| L               | The long term filter lag value.                                                                                                                                                                                |
+| $L_{\max}$      | 142 (samples), the maximum possible value for the long term filter lag.                                                                                                                                        |
+| $L_{\min}$      | 21 (samples), the minimum possible value for the long term filter lag.                                                                                                                                         |
+| M               | 9, the number of basis vectors, and the number of bits in a codeword, for the VSELP codebook used in modes 1, 2, and 3.                                                                                        |
+| M1              | 7, the number of basis vectors, and the number of bits in a codeword, for the first VSELP codebook used in mode 0.                                                                                             |
+| M2              | 7, the number of basis vectors, and the number of bits in a codeword, for the second VSELP codebook used in mode 0.                                                                                            |
+| MODE            | A two bit code indicating the mode for the current frame (see annex A).                                                                                                                                        |
+| $N_A$           | 170, the length of the analysis window. This is the number of high pass filtered speech samples used to compute the short term filter parameters for each frame.                                               |
+| $N_F$           | 160, the number of samples per frame (at a sampling rate of 8 kHz).                                                                                                                                            |
+| $N_p$           | 10, the short term filter order.                                                                                                                                                                               |
+| $N_s$           | 40, the number of samples per subframe (at a sampling rate of 8 kHz).                                                                                                                                          |
+| P1              | 6, the number of bits in the prequantizer for the $r1 - r3$ vector quantizer.                                                                                                                                  |
+| P2              | 5, the number of bits in the prequantizer for the $r4 - r6$ vector quantizer.                                                                                                                                  |
+| P3              | 4, the number of bits in the prequantizer for the $r7 - r10$ vector quantizer.                                                                                                                                 |
+| $P_f$           | The order of one phase of an interpolating filter used to evaluate candidate fractional lag values. $P_f$ equals 10 for $j \neq 0$ and equal to 1 for $j = 0$ .                                                |
+| $P_g$           | The order of one phase of an interpolating filter, $f_j(n)$ , used to interpolate C's and G's as well as fractional lags in the harmonic noise weighting, $P_g$ equals 6.                                      |
+| pitch           | The time duration between the glottal pulses which result when the vocal chords vibrate during speech production.                                                                                              |
+| Q1              | 11, the number of bits in the $r1 - r3$ reflection coefficient vector quantizer.                                                                                                                               |
+| Q2              | 9, the number of bits in the $r4 - r6$ reflection coefficient vector quantizer.                                                                                                                                |
+| Q3              | 8, the number of bits in the $r7 - r10$ reflection coefficient vector quantizer.                                                                                                                               |
+| $R0$            | A five bit code used to indicate the energy level in the current frame.                                                                                                                                        |
+| $r(n)$          | The long term filter state (the history of the excitation signal); $n < 0$                                                                                                                                     |
+| $r_L(n)$        | The long term filter state with the adaptive codebook output for lag L appended.                                                                                                                               |
+| $s'(n)$         | Synthesized speech.                                                                                                                                                                                            |
+| $W(z)$          | Spectral weighting filter.                                                                                                                                                                                     |
+| $\lambda_{hfw}$ | The harmonic noise weighting filter coefficient.                                                                                                                                                               |
+
+|                      |                                                                                                      |
+|----------------------|------------------------------------------------------------------------------------------------------|
+| $\xi$                | The adaptive pitch prefilter coefficient.                                                            |
+| $\lceil x \rceil$    | Ceiling function: the largest integer $y$ where $y < x + 1, 0$ .                                     |
+| $\lfloor x \rfloor$  | Floor function: the largest integer $y$ where $y \leq x$ .                                           |
+| $\sum_{i=j}^K x(i)$  | Summation: $x(j) + x(j+1) + \dots + x(K)$ .                                                          |
+| $\prod_{i=j}^K x(i)$ | Product: $x(j)(x(j+1))\dots(x(K))$                                                                   |
+| $\max(x,y)$          | Find the larger of two numbers $x$ and $y$ .                                                         |
+| $\min(x,y)$          | Find the smaller of two numbers $x$ and $y$ .                                                        |
+| $\text{round}(x)$    | Round the non-integer $x$ to the closest integer $y$ : $y = \lfloor x + 0,5 \rfloor$ $y = x + 0,5$ . |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| AFLAT | Autocorrelation Fixed point LAttice Technique |
+| CELP  | Code Excited Linear Prediction                |
+| FLAT  | Fixed Point Lattice Technique                 |
+| LTP   | Long Term Predictor                           |
+| SST   | Spectral Smoothing Technique                  |
+| VSELP | Vector-Sum Excited Linear Prediction          |
+
+# 4 Functional description of the GSM half rate speech codec
+
+The GSM half rate codec uses the VSELP (Vector-Sum Excited Linear Prediction) algorithm. The VSELP algorithm is an analysis-by-synthesis coding technique and belongs to the class of speech coding algorithms known as CELP (Code Excited Linear Prediction).
+
+The GSM half rate codec's encoding process is performed on a 20 ms speech frame at a time. A speech frame of the sampled speech waveform is read and based on the current waveform and the past history of the waveform, the codec encoder derives 18 parameters that describe it. The parameters extracted are grouped into the following three general classes:
+
+- energy parameters (R0 and GSP0);
+- spectral parameters (LPC and INT\_LPC);
+- excitation parameters (LAG and CODE).
+
+These parameters are quantized into 112 bits for transmission as described in annex A and their order of occurrence over Abis is given in annex B.
+
+The GSM half rate codec is an analysis-by-synthesis codec, therefore the speech decoder is primarily a subset of the speech encoder. The quantized parameters are decoded and a synthetic excitation is generated using the energy and excitation parameters. The synthetic excitation is then filtered to provide the spectral information resulting in the generation of the synthesized speech (see figure 1).
+
+![Block diagram of the GSM half rate speech codec. The diagram shows a central box labeled 'GSM half rate speech codec' containing two sub-blocks: 'Speech encoder' and 'Speech decoder'. An input labeled 'speech' enters the 'Speech encoder' from the left. An output labeled 'transmitted speech parameters' exits the 'Speech encoder' to the right. An input labeled 'received speech parameters' enters the 'Speech decoder' from the right. An output labeled 'synthesised speech' exits the 'Speech decoder' to the left.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg)
+
+```
+
+graph LR
+    subgraph GSM_half_rate_speech_codec [GSM half rate speech codec]
+        SE[Speech encoder]
+        SD[Speech decoder]
+    end
+    speech[speech] --> SE
+    SE --> transmitted[transmitted speech parameters]
+    received[received speech parameters] --> SD
+    SD --> synthesised[synthesised speech]
+  
+```
+
+Block diagram of the GSM half rate speech codec. The diagram shows a central box labeled 'GSM half rate speech codec' containing two sub-blocks: 'Speech encoder' and 'Speech decoder'. An input labeled 'speech' enters the 'Speech encoder' from the left. An output labeled 'transmitted speech parameters' exits the 'Speech encoder' to the right. An input labeled 'received speech parameters' enters the 'Speech decoder' from the right. An output labeled 'synthesised speech' exits the 'Speech decoder' to the left.
+
+Figure 1: Block diagram of the GSM half rate speech codec
+
+The ANSI-C code that describes the GSM half rate speech codec is given in GSM 06.06 [2] and the test sequences in GSM 06.07 [3] (see clause 5 for the codec homing test sequences).
+
+## 4.1 GSM half rate speech encoder
+
+The GSM half rate speech encoder uses an analysis by synthesis approach to determine the code to use to represent the excitation for each subframe. The codebook search procedure consists of trying each codevector as a possible excitation for the Code Excited Linear Predictive (CELP) synthesizer. The synthesized speech  $s'(n)$  is compared against the input speech and a difference signal is generated. This difference signal is then filtered by a spectral weighting filter,  $W(z)$ , (and possibly a second weighting filter,  $C(z)$ ) to generate a weighted error signal,  $e(n)$ . The power in  $e(n)$  is computed. The codevector which generates the minimum weighted error power is chosen as the codevector for that subframe. The spectral weighting filter serves to weight the error spectrum based on perceptual considerations. This weighting filter is a function of the speech spectrum and can be expressed in terms of the  $\alpha$  parameters of the short term (spectral) filter.
+
+$$W(z) = \frac{1 - \sum_{i=1}^{N_p} \alpha_i z^{-i}}{1 - \sum_{i=1}^{N_p} \tilde{\alpha}_i z^{-i}} \quad (1)$$
+
+The computation of the  $\tilde{\alpha}_i$  coefficients is described in subclause 4.1.7.
+
+The second weighting filter  $C(z)$ , if used, is a harmonic weighting filter and is used to control the amount of error in the harmonics of the speech signal. If the weighting filter(s) are moved to both input paths to the subtracter, an equivalent configuration is obtained as shown in figure 2.
+
+![Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3).](d26959f4514c26ca19c3d6f00da85956_img.jpg)
+
+The diagram illustrates the signal processing flow of the GSM half rate speech encoder. The input speech  $s(n)$  is split into two paths. One path goes through a spectral weighting filter  $W(z)$  and a harmonic weighting filter  $C(z)$  to produce  $y(n)$ . The other path goes to a block labeled 'Determine LPC coefficients', which outputs parameters: LPC 1, LPC 2, LPC 3, R0, and INT\_LPC. These parameters are used to configure the synthesis filter  $H(z)$ . The synthesis filter  $H(z)$  is a combination of the short-term filter  $A(z)$  and the weighting filter  $W(z)$ . The output of  $H(z)$  is then processed by a second harmonic weighting filter  $C(z)$  to produce  $y'(n)$ . A subtracter calculates the error  $e(n) = y(n) - y'(n)$ . This error is squared and summed to produce the 'total weighted error'. A block labeled 'Find Minimum over L and all I' searches for the optimal codebook index  $I$  and lag  $L$ . This is followed by a block 'find optimal gains  $\beta$  and  $\gamma$ '. The final output parameters include MODE, LAG-1, CODE\_1, LAG\_2, CODE\_2, LAG\_3, CODE\_3, LAG\_4, CODE\_4, GSP 0-1, GSP 0\_2, GSP 0\_3, and GSP 0\_4. The optimal gains  $\beta$  and  $\gamma$  are fed back to the synthesis filter  $H(z)$  and the gain  $\gamma$  is also used in the VSELP Codebook search.
+
+Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3).
+
+Figure 2: Block diagram of the GSM half rate speech encoder (MODE = 1, 2 and 3)
+
+Here  $H(z)$  is the combination of  $A(z)$ , the short term (spectral) filter, and  $W(z)$ , the spectral weighting filter. These filters are combined since the denominator of  $A(z)$  is cancelled by the numerator of  $W(z)$ .
+
+$$H(z) = \frac{1}{1 - \sum_{i=1}^{N_p} \alpha_i z^{-i}} \quad (2)$$
+
+There are two approaches that can be used for calculating the gain,  $\gamma$ . The gain can be determined prior to codebook search based on residual energy. This gain would then be fixed for the codebook search. Another approach is to optimize the gain for each codevector during the codebook search. The codevector which yields the minimum weighted error would be chosen and its corresponding optimal gain would be used for  $\gamma$ . The latter approach generally yields better results since the gain is optimized for each codevector. This approach also implies that the gain term needs to be updated at the subframe rate. The optimal code and gain for this technique can be computed as follows.
+
+The input speech is first filtered by a high pass filter as described in subclause 4.1.1. The short term filter parameters are computed from the filtered input speech once per frame. A fast fixed point covariance lattice technique is used.
+
+Subclauses 4.1.3 and 4.1.4 describes in detail how the short term parameters are determined and quantized. An overall frame energy is also computed and coded once per frame. Once per frame, one of the four voicing modes is selected. If MODE $\neq$ 0, the long term predictor is used and the long term predictor lag, L, is updated at the subframe rate. L and a VSELP codeword are selected sequentially. Each is chosen to minimize the weighted mean square error. The long-term filter coefficient,  $\beta$ , and the codebook gain,  $\gamma$ , are optimized jointly. Subclause 4.1.8 describes the technique for selecting from among the voicing modes and, if one of voiced modes is chosen, determining the long-term filter lag. Subclause 4.1.10 describes an efficient technique for jointly optimizing  $\beta$ ,  $\gamma$  and the codeword selection. Subclause 4.1.10 also includes the description of the fast VSELP codebook search technique. The  $\beta$  and  $\gamma$  parameters are transformed to equivalent parameters using the frame energy term, and are vector quantized every subframe. The coding of the frame energy and the  $\beta$  and  $\gamma$  parameters is described in subclause 4.1.11.
+
+### 4.1.1 High-pass filter
+
+The 13 bit linear Pulse Code Modulated (PCM) input speech,  $x(n)$ , is filtered by a fourth order pole-zero high pass filter. This filter suppresses the frequency components of the input speech which are below 120 Hz. The filter is implemented as a cascade of two second-order Infinite Impulse Response (IIR) filters. Incorporated into the filter coefficients is a gain of 0,5. The difference equation for the first filter is:
+
+$$y(n) = \sum_{i=0}^2 b_{1,i}x(n-i) + \sum_{j=1}^2 a_{1,j}y(n-j) \quad (3)$$
+
+where:
+
+$$b_{10} = 0,335052$$
+
+$$b_{11} = -0,669983 \quad a_{11} = 0,926117$$
+
+$$b_{12} = 0,335052 \quad a_{12} = -0,429413$$
+
+The difference equation for the second filter is:
+
+$$y(n) = \sum_{i=0}^2 b_{2,i}\tilde{y}(n-i) + \sum_{j=1}^2 a_{2,j}y(n-j) \quad (4)$$
+
+where:
+
+$$b_{20} = 0,335052$$
+
+$$b_{21} = -0,669434 \quad a_{21} = 0,965332$$
+
+$$b_{22} = 0,335052 \quad a_{22} = -0,469513$$
+
+### 4.1.2 Segmentation
+
+A sample buffer containing the previous 195 input high pass filtered speech samples,  $y(n)$ , is shifted so that the oldest 160 samples are shifted out while the next 160 input samples are shifted in. The oldest 160 samples in the buffer correspond to the next frame of samples to be encoded. The analysis interval comprises the most recent 170 samples in the buffer. The samples in the buffer are labelled as  $s(n)$  where  $0 \leq n \leq 194$  and  $s(0)$  is the first (oldest) sample.
+
+### 4.1.3 Fixed Point Lattice Technique (FLAT)
+
+Let  $r_j$  represent the  $j^{\text{th}}$  reflection coefficient. The FLAT algorithm for the determination of the reflection coefficients is stated as follows:
+
+STEP 1 Compute the covariance (autocorrelation) matrix from the input speech:
+
+$$f(i, k) = \sum_{n=N_p}^{N_A} s(n + 24 - i) s(n + 24 - k) \quad 0 \leq i, k \leq N_p \quad (5)$$
+
+STEP 2 The  $\phi(i,k)$  array is modified by windowing
+
+$$\text{EMBED Equation } f'(i, k) = f(i, k)w(|i - k|) \quad 0 \leq i, k \leq N_p \quad (6)$$
+
+$$\text{STEP } 3 \quad F_0(i, k) = f'(i, k) \quad 0 \leq i, k \leq N_p - 1 \quad (7)$$
+
+$$B_0(i, k) = f'(i + 1, k + 1) \quad 0 \leq i, k \leq N_p - 1 \quad (8)$$
+
+$$C_0(i, k) = f'(i, k + 1) \quad 0 \leq i, k \leq N_p - 1 \quad (9)$$
+
+STEP 4 set  $j = 1$
+
+STEP 5 Compute  $r_j$
+
+$$\text{EMBED Equation } r_j = -2 \frac{C_{j-1}(0,0) + C_{j-1}(N_p - j, N_p - j)}{F_{j-1}(0,0) + B_{j-1}(0,0) + F_{j-1}(N_p - j, N_p - j) + B_{j-1}(N_p - j, N_p - j)} \quad (10)$$
+
+STEP 6 If  $j = N_p$  then done.
+
+STEP 7 Update  $F_j(i, k), B_j(i, k), C_j(i, k) \quad 0 \leq i, k \leq N_p - j - 1$
+
+$$\text{EMBED Equation } F_j(i, k) = F_{j-1}(i, k) + r_j (C_{j-1}(i, k) + C_{j-1}(k, i)) + r_j^2 B_{j-1}(i, k) \quad (11)$$
+
+$$\text{EMBED Equation } B_j(i, k) = B_{j-1}(i + 1, k + 1) + r_j (C_{j-1}(i + 1, k + 1) + C_{j-1}(k + 1, i + 1)) + r_j^2 F_{j-1}(i + 1, k + 1), \quad (12)$$
+
+$$\text{EMBED Equation } C_j(i, k) = C_{j-1}(i, k + 1) + r_j (B_{j-1}(i, k + 1) + F_{j-1}(i, k + 1)) + r_j^2 C_{j-1}(k + 1, i) \quad (13)$$
+
+STEP 8  $j = j + 1$
+
+STEP 9 go to step 5.
+
+The windowing coefficients,  $w(|i-k|)$ , are found in the table 1.
+
+**Table 1: Windowing coefficients**
+
+|      |          |      |          |
+|------|----------|------|----------|
+| w(0) | 0,998966 | w(5) | 0,974915 |
+| w(1) | 0,996037 | w(6) | 0,969054 |
+| w(2) | 0,991663 | w(7) | 0,963060 |
+| w(3) | 0,986399 | w(8) | 0,956796 |
+| w(4) | 0,980722 | w(9) | 0,950127 |
+
+This algorithm can be simplified by noting that the  $\phi', F$  and  $B$  matrices are symmetric such that only the upper triangular part of the matrices need to be computed or updated. Also, step 7 is done so that  $F_j(i, k), B_j(i-1, k-1), C_j(i, k-1)$ , and  $C_j(k, i-1)$  are updated together and common terms are computed once and the recursion is done in place.
+
+### 4.1.4 Spectral quantization
+
+A three segment vector quantizer of the reflection coefficients is employed. A reduced complexity search technique is used to select the vector of reflection coefficients for each segment. The reflection coefficient vector quantizer codebooks are stored in compressed form to minimize their memory requirements.
+
+The three segments of the vector quantizer span reflection coefficients  $r_1 - r_3, r_4 - r_6$ , and  $r_7 - r_{10}$  respectively. The bit allocations for the vector quantizer segments are:
+
+|       |         |
+|-------|---------|
+| $Q_1$ | 11 bits |
+| $Q_2$ | 9 bits  |
+| $Q_3$ | 8 bits  |
+
+A reflection coefficient vector prequantizer is used at each segment. The prequantizer size at each segment is:
+
+|       |        |
+|-------|--------|
+| $P_1$ | 6 bits |
+| $P_2$ | 5 bits |
+| $P_3$ | 4 bits |
+
+At a given segment, the residual error due to each vector from the prequantizer is computed and stored in temporary memory. This list is searched to identify the four prequantizer vectors which have the lowest distortion. The index of each selected prequantizer vector is used to calculate an offset into the vector quantizer table at which the contiguous subset of quantizer vectors associated with that prequantizer vector begins. The size of each vector quantizer subset at the k-th segment is given by:
+
+$$S_k = \frac{2^{Q_k}}{2^{P_k}} \quad (14)$$
+
+The four subsets of quantizer vectors, associated with the selected prequantizer vectors, are searched for the quantizer vector which yields the lowest residual error. Thus at the first segment, 64 prequantizer vectors and 128 quantizer vectors are evaluated, 32 prequantizer vectors and 64 quantizer vectors are evaluated at the second segment, and 16 prequantizer vectors and 64 quantizer vectors are evaluated at the third segment.
+
+#### 4.1.4.1 Autocorrelation Fixed Point Lattice Technique (AFLAT)
+
+An autocorrelation version of the FLAT algorithm, AFLAT, is used to compute the residual error energy for a reflection coefficient vector being evaluated. Compute the autocorrelation sequence  $R(i)$ , from the optimal reflection coefficients,  $r_j$ , over the range  $0 \leq i \leq N_p$ .
+
+STEP 1 Define the initial conditions for the AFLAT recursion:
+
+$$\bar{P}_0(i) = R(i), 0 \leq i \leq N_p - 1 \quad (15)$$
+
+$$\bar{V}_0(i) = R(|i + 1|), 1 - N_p \leq i \leq N_p - 1 \quad (16)$$
+
+STEP 2 Initialize k, the vector quantizer segment index:
+
+$$k = 1 \quad (17)$$
+
+STEP 3 Let  $I_l(k)$  be the index of the first lattice stage in the k-th segment, and  $I_h(k)$  be the index of the last lattice stage in the k-th segment.
+
+STEP 4 Initialize j, the index of the lattice stage, to point to the beginning of the k-th segment:
+
+$$\text{EMBED Equation } j = I_l(k) \quad (18)$$
+
+STEP 5 Set the initial conditions  $P_{j-1}$  and  $V_{j-1}$  to:
+
+$$P_{j-1}(i) = \bar{P}_{j-1}(i), 0 \leq i \leq I_h(k) - I_l(k) \quad (19)$$
+
+$$V_{j-1}(i) = \bar{V}_{j-1}(i), -I_h(k) + I_l(k) \leq i \leq I_h(k) - I_l(k) \quad (20)$$
+
+STEP 6 Compute the values of  $V_j$  and  $P_j$  arrays using:
+
+$$P_j(i) = (1 + \hat{r}_j^2)P_{j-1}(i) + \hat{r}_j[V_{j-1}(i) + V_{j-1}(-i)], 0 \leq i \leq I_h(k) - j - 1 \quad (21)$$
+
+$$V_j(i) = V_{j-1}(i + 1) + \hat{r}_j^2 V_{j-1}(-i - 1) + 2\hat{r}_j P_{j-1}(|i + 1|), 1 + j - N_p \leq i \leq N_p - j - 1 \quad (22)$$
+
+STEP 7 Increment j:
+
+$$j = j+1$$
+
+STEP 8 If  $j < I_h(k)$  go to STEP 6.
+
+STEP 9 The residual error out of lattice stage  $I_h(k)$ , given the reflection coefficient vector  $\hat{r}$ , is computed using equation (21):
+
+$$\text{EMBED Equation } E_r = P_{I_h(k)}(0) \quad (23)$$
+
+STEP 10 Using the AFLAT recursion outlined, the residual error due to each vector from the prequantizer at the k-th segment is evaluated, the four subsets of quantizer vectors to be searched are identified, and residual error due to each quantizer vector from the selected four subsets is computed. The index of  $\tilde{r}$ , the quantizer vector which minimized  $E_r$  over all the quantizer vectors in the four subsets, is encoded with  $Q_k$  bits.
+
+STEP 11 If  $k < 3$  then the initial conditions for doing the recursion at segment  $k+1$  need to be computed. Set j, the lattice stage index, equal to:
+
+$$\text{EMBED Equation } j = I_l(k) \quad (24)$$
+
+STEP 12 Compute:
+
+$$\bar{P}_j(i) = (1 + \kappa_j^2)\bar{P}_{j-1}(i) + \kappa_j[\bar{V}_{j-1}(i) + \bar{V}_{j-1}(-i)], 0 \leq i \leq N_p - j - 1 \quad (25)$$
+
+$$\bar{V}_j(i) = \bar{V}_{j-1}(i+1) + \kappa_j^2\bar{V}_{j-1}(-i-1) + 2\kappa_j\bar{P}_{j-1}(|i+1|), 1 + j - N_p \leq i \leq N_p - j - 1 \quad (26)$$
+
+STEP 13 Increment j,
+
+$$j = j+1$$
+
+STEP 14 If  $j \leq I_h(k)$  go to STEP 12
+
+STEP 15 Increment k, the vector quantizer segment index:
+
+$$k = k+1$$
+
+STEP 16 If  $k \leq 3$  go to STEP 4.
+
+Otherwise, the indices of the reflection coefficient vectors for the three segments have been chosen, and the search of the reflection coefficient vector quantizer is terminated.
+
+To minimize the storage requirements for the reflection coefficient vector quantizer, eight bit codes for the individual reflection coefficients are stored in the vector quantizer table, instead of the actual reflection coefficient values. The codes are used to look up the values of the reflection coefficients from a scalar quantization table with 256 entries.
+
+### 4.1.5 Frame energy calculation and quantization
+
+The unquantized value of  $R_0$ ,  $R(0)$ , is computed during the computation of the short term predictor parameters.
+
+$$R(0) = \frac{\phi(0,0) + \phi(10,10)}{320} \quad (27)$$
+
+where  $\phi(i,k)$  is defined by equation (5).  $R(0)$  is then converted into dB relative to full scale (full scale,  $R_{\max}$ , is defined as the square of the maximum sample amplitude).
+
+$$R_{\text{dB}} = 10 \log_{10} \left( \frac{R(0)}{R_{\max}} \right) \quad (28)$$
+
+$R_{dB}$  is then quantized to 32 levels. The 32 quantized values for  $R_{dB}$  range from a minimum of -66 (corresponding to a code of 0 for  $R_0$ ) to a maximum of -4 (corresponding to a code of 31 for  $R_0$ ). The step size of the quantizer is 2 (2 dB steps).  $R_0$  is chosen as:
+
+$$R_0 \text{ which minimizes} \quad \text{abs}(R_0 - (R_{dB} + 66)/2) \quad (29)$$
+
+where  $R_0$  can take on the integer values from 0 to 31 corresponding to the 32 codes for  $R_0$ .
+
+Decoding of the  $R_0$  code is given by:
+
+$$R(0) = R_{\max} 10^{((2R_0)-66)/10} \quad (30)$$
+
+### 4.1.6 Soft interpolation of the spectral parameters
+
+Interpolation of the short term filter parameters improves the performance of the GSM half rate encoder. The direct form filter coefficients ( $\alpha_i$ 's), which correspond to quantized reflection coefficients, are the spectral parameters used for interpolation. The GSM half rate speech encoder uses either an interpolated set of  $\alpha_i$ 's or an uninterpolated set of  $\alpha_i$ 's, choosing the set which gives better prediction gain for the frame.
+
+Two sets of LPC coefficient vectors are generated: the first corresponds to the interpolated coefficients, the second to the uninterpolated coefficients. The frame's speech samples are inverse filtered using each of the two coefficient sets, and the residual frame energy corresponding to each set is computed. The coefficient set yielding the lower frame residual energy is then selected to be used. If the residual energies are equal, the uninterpolated coefficient set is used. INT\_LPC, a soft interpolation bit, is set to 1 when interpolation is selected or to 0 otherwise.
+
+To generate the interpolated coefficient set, the coder interpolates the  $\alpha_i$ 's for the first, second, and third subframes of each frame. The fourth subframe uses the uninterpolated  $\alpha_i$ 's for that frame.
+
+The interpolation is done as follows. Let  $\alpha_{i,L}$  be the direct-form LPC coefficients corresponding to the last frame,  $\alpha_{i,C}$  be the direct-form LPC coefficients corresponding to the current frame, and  $Del$  to be the interpolation curve used. The interpolated direct-form LPC coefficient vector at the  $j$ -th subframe of the current frame,  $\alpha_{i,j}$ , is given by:
+
+$$\alpha_{i,j} = \alpha_{i,L} + Del(j, INT\_SOFT)(\alpha_{i,C} - \alpha_{i,L}), \quad 1 \leq i \leq N_p, 1 \leq j \leq 4 \quad (31)$$
+
+The values of the interpolation curve  $Del$  are given in table 2.
+
+**Table 2: Values of the interpolation curve  $Del$**
+
+| $j$ | $Del(j,0)$ | $Del(j,1)$ |
+|-----|------------|------------|
+| 1   | 0,0        | 0,30       |
+| 2   | 1,0        | 0,62       |
+| 3   | 1,0        | 0,92       |
+| 4   | 1,0        | 1,00       |
+
+From this point on, the subframe index  $j$  is omitted for simplicity when referring to  $\alpha_{i,j}$  coefficients, although it is implied. For interpolated subframes, the  $\alpha_i$ 's are converted to reflection coefficients to check for filter stability. If the resulting filter is unstable, then uninterpolated coefficients are used for that subframe. The uninterpolated coefficients used for subframe 1 are the previous frame's coefficients. The uninterpolated coefficients used for subframes 2, 3, and 4 are the current frame's coefficients.
+
+### 4.1.7 Spectral noise weighting filter coefficients
+
+To exploit the noise masking potential of the formants, spectral noise weighting is applied. The computation of the  $\tilde{\alpha}_i$  coefficients, used by spectral noise weighting filters  $W(z)$  and  $H(z)$ , is now described. Define an impulse sequence  $\delta(n)$  over  $N_s$  samples:
+
+$$\begin{aligned}\delta(0) &= 1, 0 \\ \delta(n) &= 0, 0\end{aligned}\quad (32)$$
+
+where  $1 \leq n \leq N_s-1$  and  $h_3(n)$  is the zero-state response of the cascade of three filters to  $\delta(n)$ . The three filters are an LPC synthesis filter, an inverse filter using a weighting factor of 0,93 and a synthesis filter with a weighting factor of 0,7. In equation form:
+
+$$h_1(n) = \delta(n) + \sum_{i=1}^{N_p} \alpha_i h_1(n-i) \quad 0 \leq n \leq N_s-1 \quad (33)$$
+
+$$h_2(n) = h_1(n) - \sum_{i=1}^{N_p} (0,93)^i \alpha_i h_1(n-i) \quad 0 \leq n \leq N_s-1 \quad (34)$$
+
+$$h_3(n) = h_2(n) + \sum_{i=1}^{N_p} (0,7)^i \alpha_i h_3(n-i), \quad 0 \leq n \leq N_s-1 \quad (35)$$
+
+where  $\alpha_i$ 's are the direct form LP coefficients. The autocorrelation sequence of  $h_3(n)$  is calculated using:
+
+$$R_{h_3}(i) = \sum_{n=i}^{N_s-1} h_3(n) h_3(n-i), \quad 0 \leq i \leq N_p \quad (36)$$
+
+From  $R_{h_3}(i)$  the reflection coefficients which define the combined spectrally noise weighted synthesis filter are computed using the AFLAT recursion once per frame.
+
+STEP 1 Define the initial conditions for the AFLAT recursion:
+
+$$P_0(i) = R_{h_3}(i), \quad 0 \leq i \leq N_p-1 \quad (37)$$
+
+$$V_0(i) = R_{h_3}(|i+1|), \quad 1-N_p \leq i \leq N_p-1 \quad (38)$$
+
+STEP 2 Initialize  $j$ , the index of the lattice stage, to point to the first lattice stage:
+
+$$j = 1$$
+
+STEP 3 Compute  $r_j$ , the  $j$ -th reflection coefficient, using:
+
+$$r_j = -\frac{V_{j-1}(0)}{P_{j-1}(0)} \quad (39)$$
+
+STEP 4 Given  $r_j$ , update the values of  $V_j$  and  $P_j$  arrays using:
+
+$$P_j(i) = (1 + r_j^2)P_{j-1}(i) + r_j[V_{j-1}(i) + V_{j-1}(-i)], \quad 0 \leq i \leq N_p - j - 1 \quad (40)$$
+
+$$V_j(i) = V_{j-1}(i+1) + r_j^2 V_{j-1}(-i-1) + 2r_j P_{j-1}(|i+1|), \quad 1+j-N_p \leq i \leq N_p - j - 1 \quad (41)$$
+
+STEP 5 Increment  $j$ :
+
+$$j = j+1$$
+
+STEP 6 If  $j \leq N_p$  go to STEP 3, otherwise all  $N_p$  reflection coefficients have been obtained.
+
+STEP 7 The reflection coefficients,  $r_j$ , are then converted to direct-form LPC filter coefficients,  $\tilde{\alpha}_i$ , for implementing the combined spectrally noise weighted synthesis filter  $H(z)$  and the filter  $W(z)$ .
+
+The method for the spectral noise weighting filter coefficient update mimicks how the direct form LPC filter coefficients are updated at subframes of a frame (subclause 4.1.6). No stability check of interpolated spectral noise weighting filter coefficients is done at subframes 1, 2, or 3 if the interpolation flag, INT\_LPC="1", but if uninterpolated coefficients are used at subframes 1, 2, and/or 3 due to instability of the unweighted coefficients (INT\_LPC = "0"), uninterpolated weighting filter coefficients are also used at those subframes.
+
+### 4.1.8 Long Term Predictor lag determination
+
+Figure 3 illustrates that the long term lag optimization looks just like a codebook search where the codebook is defined by the long term filter state and the specific vector in the codebook is pointed to by the long term predictor lag, L. The input  $p(n)$  is the weighted input speech for the subframe minus the zero input response of just the  $H(z)$  filter.
+
+![Figure 3: Long term predictor lag search block diagram. The diagram shows a signal flow starting with 'Long term filter state' (input L) and 'b(n)' (input beta) entering a multiplier (X). The output of the multiplier passes through a filter H(z) to produce p'(n). This signal is then subtracted from the input p(n) to produce an error signal e(n). The error signal is then squared and summed to produce the 'total weighted error'.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg)
+
+```
+
+graph LR
+    L[L] --> LTF[Long term filter state]
+    beta[β] --> X((X))
+    LTF --> X
+    X --> HZ[H(z)]
+    HZ --> pn_prime[p'(n)]
+    pn[p(n)] --> Minus((-))
+    pn_prime --> Minus
+    Minus --> en[e(n)]
+    en --> Sum[Σ( )²]
+    Sum --> Error[total weighted error]
+  
+```
+
+Figure 3: Long term predictor lag search block diagram. The diagram shows a signal flow starting with 'Long term filter state' (input L) and 'b(n)' (input beta) entering a multiplier (X). The output of the multiplier passes through a filter H(z) to produce p'(n). This signal is then subtracted from the input p(n) to produce an error signal e(n). The error signal is then squared and summed to produce the 'total weighted error'.
+
+Figure 3: Long term predictor lag search
+
+The GSM half rate speech encoder uses a combination of open loop and closed loop techniques in choosing the long term predictor lag. First an open loop search is conducted to determine "candidate" lags at each subframe. Then at most, two best candidate lags at each subframe are selected, with each serving as an anchor point for constructing an open loop frame lag trajectory, subject to a maximum delta coding constraint. The frame lag trajectory which minimizes the open loop LTP spectrally weighted error energy for the frame is then chosen. The open loop LTP prediction gains corresponding to the winning trajectory are used to select the voicing mode 1, 2 or 3. If MODE≠0, the closed loop lag evaluation is initiated. The winning trajectory has associated with it a list of lags to be searched closed loop at each subframe.
+
+It is possible to allow L to take on fractional values, thus increasing the resolution, and in turn the performance, of the adaptive codebook. Table 3 shows the allowable lags.
+
+Table 3: Allowable lags
+
+| Range        | Resolution | Number of lags in range |
+|--------------|------------|-------------------------|
+| 21 to 22 2/3 | 1/3        | 6                       |
+| 23 to 34 5/6 | 1/6        | 72                      |
+| 35 to 49 2/3 | 1/3        | 45                      |
+| 50 to 89 1/2 | 1/2        | 80                      |
+| 90 to 142    | 1          | 53                      |
+
+The resolution of the long term filter state may be increased by upsampling and filtering the state. In this implementation, a non-causal, zero-phase Finite Impulse Response (FIR) filter is used. Where needed, the future samples for the non-causal filtering operation are replaced by the output of the predictor.
+
+#### 4.1.8.1 Open loop long term search initialization
+
+An open-loop lag search is done to narrow the range of lags over which a closed-loop search will eventually be performed.
+
+The first steps of the open-loop subframe lag search are as follows:
+
+STEP 1 Initialize the subframe counter
+
+$m=1$
+
+STEP 2 The autocorrelation sequence of  $y(n)$  the input speech,  $s(n)$ , filtered by  $W$ , is calculated for all allowable integer lags, and for a few integer lags below and above the lower and upper limits for the current subframe.
+
+$$C(k, m) = \sum_{n=0}^{N_s-1} y(n + (m - 1)N_s) y(n + (m - 1)N_s - k), \quad L_{\min} - \frac{P_g}{2} \leq k \leq L_{\max} + \frac{P_g}{2} - 1 \quad (42)$$
+
+where  $L_{\min} = 21$  and  $L_{\max} = 142$ .
+
+The value  $P_g$  is the order of one phase of the interpolating FIR filter used to interpolate the correlations. The energy of  $y(n)$  for the subframe is computed:
+
+$$G(k, m) = \sum_{n=0}^{N_s-1} y^2(n + (m - 1)N_s - k), \quad L_{\min} - \frac{P_g}{2} \leq k \leq L_{\max} + \frac{P_g}{2} - 1 \quad (43)$$
+
+STEP 3 These arrays,  $C(k, m)$  and  $G(k, m)$ , are searched for the integer lag which maximizes  $C^2(k, m)/G(k, m)$  where  $C(k, m)$  and  $G(k, m)$  need to be greater than 0.
+
+STEP 4 If a valid maximum is found in step 3, the values for the lag,  $C$ , and  $G$  corresponding to the maximum are retained in the arrays as  $L_{\text{peak}}(0, m)$ ,  $C_{\text{peak}}(0, m)$ , and  $G_{\text{peak}}(0, m)$ .
+
+$$\text{Otherwise, } L_{\text{peak}}(0, m) = L_{\min} \quad (44)$$
+
+$$C_{\text{peak}}(0, m) = 0 \quad (45)$$
+
+$$G_{\text{peak}}(0, m) = 1 \quad (46)$$
+
+STEP 5  $m = m + 1$
+
+STEP 6 If  $m \leq 4$ , go to step 2
+
+STEP 7 Calculate the open loop frame LTP prediction gain:
+
+$$P_v = 10 \log_{10} \left[ \frac{\sum_{m=1}^4 R(0, m)}{\sum_{m=1}^4 \left[ R(0, m) - \frac{C_{\text{peak}}^2(0, m)}{G_{\text{peak}}(0, m)} \right]} \right] \quad (47)$$
+
+where
+
+$$R(0, m) = \sum_{n=0}^{N_s-1} y^2(n + (m - 1)N_s), \quad (48)$$
+
+STEP 8 Determine if the voicing mode is unvoiced:
+
+If  $P_v < 1,7$  then  $\text{MODE} = 0$ , the long term predictor is disabled and the open loop and closed loop lag searches are aborted. In this case, proceed to subclause 4.1.10.
+
+#### 4.1.8.2 Open loop lag search
+
+When  $\text{MODE} \neq 0$ , the lag search processing is continued. The next part of the search finds the allowable lag (see
+
+table 3) which maximizes  $\frac{C^2}{G}$  in the vicinity of the best open-loop integer resolution lag,  $L_{\text{peak}}(0, m)$ , for values of  $C > 0$ .
+
+STEP 1 Initialize the subframe counter
+
+$$m=1$$
+
+STEP 2 Initialize the peak index
+
+$$L_{p,m} = 0$$
+
+STEP 3 Using interpolated versions of the C and G arrays, allowable lag values  $k'$  in the range:
+
+$$L_{\text{peak}}(0,m) - 1 < k' < L_{\text{peak}}(0,m) + 1 \quad (49)$$
+
+are searched for a  $k$  which maximizes
+
+$$\frac{C_I^2(k)}{G_I(k)} \quad (50)$$
+
+where
+
+$$C_I(k) = \sum_{i=0}^5 g_j(i) C([k] - 3 + i, m) \quad (51)$$
+
+$$G_I(k) = \sum_{i=0}^5 g_j(i) G([k] - 3 + i, m) \quad (52)$$
+
+and
+
+$$j = 6([k] - k) \quad (53)$$
+
+The coefficients of the interpolating filter are  $g_j(i)$  for  $0 \leq i \leq 5$ .
+
+Only  $C_I(k) > 0$  and  $G_I(k) > 0$  values are considered. If no positive correlation is found, then set
+
+$$\lambda_{\text{hwn},m} = 0, L_{\text{peak}}(1,m) = L_{\min}, \text{ and go to Step 22.}$$
+
+Otherwise, store the information related to the valid best allowable lag  $k$ .
+
+$$L_{p,m} = L_{p,m} + 1 \quad (54)$$
+
+$$L_{\text{peak}}(L_{p,m},m) = k \quad (55)$$
+
+$$C_{\text{peak}}(L_{p,m},m) = C_I(k) \quad (56)$$
+
+$$G_{\text{peak}}(L_{p,m},m) = G_I(k) \quad (57)$$
+
+The next part of the search evaluates  $\frac{C^2}{G}$ , for  $C > 0$  and  $G > 0$ , at the submultiples of the lag  $L_{\text{peak}}(L_{p,m},m)$  to find candidate peaks.
+
+STEP 4 Initialize the divisor
+
+$$J = 2$$
+
+STEP 5 Find nearest integer lag corresponding to submultiple of maximum peak
+
+$$k_1 = \text{round}[L_{\text{peak}}(1,m)/J] \quad (58)$$
+
+STEP 6 Determine if submultiple is within allowable lag range
+
+$$\text{If } k_1 < L_{\min}$$
+
+Go to step 12
+
+STEP 7 Find value of  $k'$  where  $C^2(k',m)/G(k',m)$  is a maximum for
+
+$$\max(L_{\min}, k_1-3) \leq k' \leq \min(L_{\max}, k_1+3) \quad (59)$$
+
+If either  $C(k',m) \leq 0$  or  $G(k',m) \leq 0$  go to step 11.
+
+STEP 8 Determine if maximum in step 7 is a peak
+
+If
+
+$$\frac{C^2(k'-1,m)}{G(k'-1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (60)$$
+
+Go to step 11
+
+If
+
+$$\frac{C^2(k'+1,m)}{G(k'+1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (61)$$
+
+Go to step 11
+
+STEP 9 A peak has been found at an integer lag,  $k'$ . Using interpolated versions of the C and G arrays, allowable lag values within  $\pm 1$  (exclusive) of  $k'$  are searched.
+
+Find  $k$  where
+
+$$\frac{C_I^2(k)}{G_I(k)} \quad (62)$$
+
+is a maximum, where
+
+$$C_I(k) = \sum_{i=0}^5 g_j(i) C([k] - 3 + i, m) \quad (63)$$
+
+$$G_I(k) = \sum_{i=0}^5 g_j(i) G([k] - 3 + i, m) \quad (64)$$
+
+where
+
+$$j = 6([k] - k) \quad (65)$$
+
+$$\text{and } k'-1 < k < k'+1 \quad (66)$$
+
+Only  $C_I(k) > 0$  and  $G_I(k) > 0$  are considered.
+
+STEP 10 If the prediction gain exceeds a threshold, the corresponding lag,  $C_I$ , and  $G_I$  are stored in the  $L_{\text{peak}}()$ ,  $C_{\text{peak}}()$ , and  $G_{\text{peak}}()$  arrays; otherwise, these values are not stored.
+
+If
+
+$$\frac{C_I^2(k)}{G_I(k)} > R(0,m) - \frac{R(0,m)}{10^x}, \quad \text{where } x = 7,5 \log_{10} \left( \frac{R(0,m)}{R(0,m) - \frac{C_{\text{peak}}^2(0,m)}{G_{\text{peak}}(0,m)}} \right) \quad (67)$$
+
+then
+
+$$L_{p,m} = L_{p,m} + 1 \quad (68)$$
+
+$$L_{\text{peak}}(L_{p,m}, m) = k \quad (69)$$
+
+$$C_{\text{peak}}(L_{p,m}, m) = C_I(k) \quad (70)$$
+
+$$G_{\text{peak}}(L_{p,m}, m) = G_I(k) \quad (71)$$
+
+STEP 11 Increment divisor and check the next submultiple
+
+$J=J+1$
+
+Go to step 5
+
+STEP 12 A full-resolution search (1/6 sample resolution) is done for a peak within 1 integer lag (exclusive) of the shortest lag.
+
+Find  $k$  such that
+
+$$\frac{C_I^2(k)}{G_I(k)} \quad (72)$$
+
+is a maximum, where
+
+$$C_I(k) = \sum_{i=0}^5 g_j(i) C([k] - 3 + i, m) \quad (73)$$
+
+$$G_I(k) = \sum_{i=0}^5 g_j(i) G([k] - 3 + i, m) \quad (74)$$
+
+$$j = 6([k] - k) \quad (75)$$
+
+$$\max\left(L_{\min} - \frac{1}{6}, L_{\text{peak}}(L_{p,m}) - 1\right) < k < \min\left(L_{\max} + \frac{1}{6}, L_{\text{peak}}(L_{p,m}) + 1\right) \quad (76)$$
+
+The fractional lag corresponding to the maximum is referred to as  $L_{\text{pitch},m}$ . This lag is used by the harmonic noise weighting function  $C(z)$  at subframe  $m$ . Then
+
+$$C_{\text{pitch},m} = C_I(L_{\text{pitch},m}) \quad (77)$$
+
+$$G_{\text{pitch},m} = G_I(L_{\text{pitch},m}) \quad (78)$$
+
+STEP 13 The harmonic noise weighting coefficient for subframe  $m$  is calculated in this step (see subclause 4.1.9)
+
+$$\lambda_{\text{hnw},m} = 0,4 \frac{C_{\text{pitch},m}}{G_{\text{pitch},m}} \quad (79)$$
+
+Once all the correlation peaks associated with submultiples of the  $L_{\text{peak}}(1,m)$  have been examined, the correlation peaks associated with multiples of  $L_{\text{pitch},m}$  are examined.
+
+STEP 14 Initialize the multiplier
+
+$J = 2$
+
+STEP 15 Find nearest integer lag corresponding to a multiple of the fundamental lag
+
+$$k_1 = \text{round}[L_{\text{pitch},m} * J] \quad (80)$$
+
+STEP 16 Determine if multiple is within allowable lag range
+
+If
+
+$$k_1 > L_{\max}$$
+
+Go to step 22
+
+STEP 17 Find value of  $k'$  where  $C^2(k',m)/G(k',m)$  is a maximum for
+
+$$\max(L_{\min}, k_1 - 3) \leq k' \leq \min(L_{\max}, k_1 + 3) \quad (81)$$
+
+If either  $C(k',m) \leq 0$  or  $G(k',m) \leq 0$  go to step 21.
+
+STEP 18 Determine if maximum in step 17 is a peak
+
+If
+
+$$\frac{C^2(k'-1,m)}{G(k'-1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (82)$$
+
+Go to step 21
+
+If
+
+$$\frac{C^2(k'+1,m)}{G(k'+1,m)} > \frac{C^2(k',m)}{G(k',m)} \quad (83)$$
+
+Go to step 21
+
+STEP 19 A peak has been found at an integer lag,  $k'$ . Using interpolated versions of the C and G arrays, allowable lag values within  $\pm 1$  (exclusive) of  $k'$  are searched.
+
+Find  $k$  where
+
+$$\frac{C_I^2(k)}{G_I(k)} \quad (84)$$
+
+is a maximum, where
+
+$$C_I(k) = \sum_{i=0}^5 g_j(i) C([k] - 3 + i, m) \quad (85)$$
+
+$$G_I(k) = \sum_{i=0}^5 g_j(i) G([k] - 3 + i, m) \quad (86)$$
+
+where
+
+$$j = 6([k] - k) \quad (87)$$
+
+$$\text{and } k'-1 < k < k'+1 \quad (88)$$
+
+Only  $C_I(k) > 0$  and  $G_I(k) > 0$  are considered.
+
+STEP 20 If the prediction gain exceeds a threshold, the corresponding lag,  $C_I$ , and  $G_I$  are stored.
+
+If
+
+$$\frac{C_I^2(k)}{G_I(k)} > R(0,m) - \frac{R(0,m)}{10^x}, \quad \text{where } x = 7,5 \log_{10} \left( \frac{R(0,m)}{R(0,m) - \frac{C_{\text{peak}}^2(0,m)}{G_{\text{peak}}(0,m)}} \right) \quad (89)$$
+
+then
+
+$$L_{p,m} = L_{p,m} + 1 \quad (90)$$
+
+$$L_{\text{peak}}(L_{p,m}) = k \quad (91)$$
+
+$$C_{\text{peak}}(L_{p,m}) = C_I(k) \quad (92)$$
+
+$$G_{\text{peak}}(L_{p,m}) = G_I(k) \quad (93)$$
+
+STEP 21 Increment multiplier and check the next multiple
+
+$$J = J + 1$$
+
+Go to step 15
+
+STEP 22 Increment subframe pointer and repeat for all subframes
+
+$m=m+1$
+
+If  $m \leq 4$
+
+Go to step 2.
+
+Otherwise, the list of correlation peaks and the harmonic noise weighting filter parameters for each subframe have been found.
+
+#### 4.1.8.3 Frame lag trajectory search (Mode $\neq 0$ )
+
+The frame lag trajectory search uses the list of potential lag values to determine the one lag value for each subframe which minimizes the open loop prediction error energy for the frame subject to the constraints of the delta lag coding employed for subframes 2, 3 and 4. Several candidate lag trajectories are determined. The trajectory which minimizes the open loop prediction error energy for the frame is chosen.
+
+In subclause 4.1.8.2, the open loop lag search found a list of lags,  $L_{\text{peak}}(i,m)$ , corresponding to the  $\frac{C^2}{G}$  peaks, for each subframe. Each trajectory evaluation begins with one of the subframes and selects a lag corresponding to a  $\frac{C^2}{G}$  peak for that subframe as the anchor for that candidate trajectory.
+
+A maximum of 2 trajectories are anchored per subframe. From the anchor lag, the trajectory is extended forward and backward to the adjacent subframes in the frame subject to the lag differential coding constraints. The lag for each subframe on the trajectory is chosen to minimize the open loop frame prediction error energy. The trajectory search is described below.
+
+The steps involved in the frame lag trajectory evaluation and selection are:
+
+STEP 1 Set  $m$ , the pointer to the selected subframe, equal to 1.
+
+STEP 2 Choose the lag at the selected subframe,  $m$ , to be an anchor lag for the frame lag trajectory; i.e., the frame lag trajectory being evaluated needs to pass through that lag. The lag which is chosen,
+
+corresponds to the highest peak in the list of  $\frac{C_I^2}{G_I}$  peaks at subframe  $m$ , which has not been crossed by a trajectory evaluated previously. If no peaks qualify, no peaks are left, or two trajectories have already been anchored and evaluated at subframe  $m$ , go to step 7. Otherwise, compute the open loop subframe weighted error energy corresponding to the chosen lag, and store the result in the frame weighted error accumulator corresponding to the trajectory currently being evaluated.
+
+STEP 3 If  $m < 4$ , begin the forward search:
+
+STEP 3a Define the current subframe to be  $m+1$ .
+
+STEP 3b Define the forward search range as -7 to +6 levels relative to the current subframe's lag level.
+
+STEP 3c Check that the lower bound does not point to a level below the lowest allowable lag level, clipping if necessary. Similarly, check that the upper bound does not point past the highest allowable lag level; clip if necessary.
+
+STEP 3d Find the lag within the range which maximizes  $\frac{C_I}{\sqrt{G_I}}$ .
+
+NOTE: negative values of  $C_I$  are allowed. Compute the open loop subframe weighted error energy corresponding to that lag at the current subframe, and add the result to the frame weighted error accumulator corresponding to the trajectory being evaluated.
+
+STEP 3e If the current subframe  $< 4$ , increment the pointer to the current subframe, and go to step 3b.
+
+STEP 4 If  $m > 1$ , initiate the backward search:
+
+STEP 4a Define the current subframe to be  $m-1$ .
+
+STEP 4b Define the backward search range as  $-6$  to  $+7$  levels relative to the current subframe's lag level.
+
+STEP 4c Check that the lower bound does not point to a level below the lowest allowable lag level, clipping if necessary. Similarly, check that the upper bound does not point past the highest allowable lag level; clip if necessary.
+
+STEP 4d Find lag within the range which maximizes  $\frac{C_I}{\sqrt{G_I}}$ .
+
+NOTE: negative values of  $C_I$  are allowed. Compute the open loop subframe weighted error energy corresponding to that lag at the current subframe, and add the result to the frame weighted error accumulator corresponding to the trajectory being evaluated.
+
+STEP 4e If the current subframe index is  $> 1$ , decrement the pointer to the current subframe, and go to step 4a.
+
+STEP 5 Store the lags defining the frame lag trajectory derived and the open loop LTP frame weighted error energy which this trajectory yields. Increment the counter of evaluated frame lag trajectories.
+
+STEP 6 Go to step 2.
+
+STEP 7 If  $m < 4$ , increment  $m$  and go to step 2.
+
+STEP 8 Choose, from the set of constructed frame lag trajectories, a lag trajectory which yields the lowest LTP weighted error energy for the frame, as the selected frame lag trajectory.
+
+#### 4.1.8.4 Voicing mode selection
+
+The frame lag trajectory is specified by a vector  $K=\{k_1,k_2,k_3,k_4\}$ , where  $k_m$  is the open loop LTP lag at the  $m$ -th subframe. Define the interpolated correlation of the input spectrally weighted speech  $y(n)$  at the  $m$ -th subframe, specified by lag  $k_m$ , as  $C_I(k_m,m)$  and the interpolated energy of  $y(n)$ , delayed by  $k_m$  samples relative to the  $m$ -th subframe, as  $G_I(k_m,m)$ .
+
+The open loop LTP prediction gain in dB at the  $m$ -th subframe is:
+
+$$P_m = 10\log_{10} \left[ \frac{R(0,m)}{R(0,m) - \frac{C_I^2(k_m,m)}{G_I(k_m,m)}} \right] \quad (94)$$
+
+The open loop frame LTP prediction gain, is given by:
+
+$$P_v = 10\log_{10} \left[ \frac{\sum_{m=1}^4 R(0,m)}{\sum_{m=1}^4 \left[ R(0,m) - \frac{C_{\text{peak}}^2(0,m)}{G_{\text{peak}}(0,m)} \right]} \right] \quad (95)$$
+
+The rules for mode selection are specified as follows:
+
+$$\text{MODE}=0 \text{ if } P_v < 1,7 \quad (96)$$
+
+$$\text{MODE}=1 \text{ if } P_v \geq 1,7 \text{ and } P_m < 3,5 \text{ for any } m \quad (97)$$
+
+$$\text{MODE}=2 \text{ if } P_m \geq 3,5 \text{ for all } m \text{ and } P_m < 7 \text{ for any } m \quad (98)$$
+
+$$\text{MODE}=3 \text{ if } P_m \geq 7,0 \text{ for all } m \quad (99)$$
+
+#### 4.1.8.5 Closed loop lag search
+
+From the selected frame lag trajectory, develop a list of lags to be searched closed loop. At each subframe, three allowable lag levels centered around the subframe lag, specified by the selected frame lag trajectory, will be searched. If the lag points to the lowest or the highest level in the table of quantized lag values, only two closed loop lag evaluations will be done at that subframe, with the lag outside the quantizer range being eliminated from consideration. The closed loop evaluation of the subframe lags is not performed if MODE=0. What follows is a description of the construction of the output of the long term predictor (adaptive codebook) for a given, possibly fractional lag, L. Defining:
+
+|                  |                                                                                                                       |
+|------------------|-----------------------------------------------------------------------------------------------------------------------|
+| $L_{\max}$       | maximum possible value for long term lag L                                                                            |
+| $r(n)$           | long term filter state; $n < 0$ (history of the excitation signal)                                                    |
+| $r_L(n)$         | long term filter state with adaptive codebook output for L appended                                                   |
+| $b_L(n)$         | output of long term filter state (adaptive codebook) for lag L                                                        |
+| $P_f$            | order of one phase of the interpolating FIR filter ( $P_f = 10$ except for the special case when $j = 0$ , see below) |
+| $\tilde{f}_j(i)$ | coefficients of jth phase of interpolating FIR filter, $i=0$ to $i=P_f-1$                                             |
+| $N_s$            | number of samples per subframe ( $N_s = 40$ )                                                                         |
+
+The sequence  $r_L(n)$  is defined as:
+
+$$r_L(n) = \begin{cases} r(n) & ; -L_{\max} \leq n \leq -1 \\ \sum_{i=0}^{P_f-1} \tilde{f}_j(i) r_L\left(n - \Lambda - \frac{P_f}{2} + i\right) & ; 0 \leq n \leq N_s - 1 \end{cases} \quad (100)$$
+
+$$q = \left\lfloor \frac{n + L + \frac{5}{6}}{L} \right\rfloor L, \quad \Lambda = \lfloor q \rfloor, \text{ and } j = 6(q - \lfloor q \rfloor)$$
+
+where;
+
+The portion of the sequence  $r_L(n)$  from  $n=0$  to  $n=N_s-1$  shall be calculated in order from 0 to  $N_s-1$ , so that the necessary terms in the sum will be available. The 0<sup>th</sup> phase of the interpolating filter,  $\tilde{f}_0(i)$ , is a special case and has only one non-zero tap, so that if  $q$  is an integer, the summation reduces to the single term,  $r_L(n-q)$ .
+
+The output of the codebook for lag L is just the last  $N_s$  samples in the sequence  $r_L(n)$ .
+
+$$b_L(n) = r_L(n) \quad ; 0 \leq n \leq N_s-1 \quad (101)$$
+
+The closed loop search minimizes the weighted error by maximizing the term  $\frac{C^2}{G}$ , where
+
+$$C = \sum_{n=0}^{N_s-1} b_L(n) p(n) \quad (102)$$
+
+$$G = \sum_{n=0}^{N_s-1} b_L^2(n) \quad (103)$$
+
+The sequence  $b_L(n)$  is the zero state response of  $H(z)$  to the adaptive codebook output for lag  $L$ . The sequence  $p(n)$  is the input speech, weighted by the filter  $W(z)$ , minus the zero input response of  $H(z)$ . The error minimization is done
+
+over only those lags in the list supplied by the open loop search. The lag  $L$  which maximizes  $\frac{C}{\sqrt{G}}$  ( $C$  is allowed to be negative) is then chosen as the lag for the subframe.
+
+### 4.1.9 Harmonic noise weighting
+
+If  $MODE = 1, 2$  or  $3$ , then  $C(z)$ , the harmonic noise weighting transfer function, is activated. The excitation codebook vector and gains codebook vector are selected to minimize the spectrally and harmonically weighted error. The harmonic weighting filter,  $C(z)$ , can be expressed as:
+
+$$C(z) = 1 - \lambda_{hnw} z^{-L_{pitch}} \quad (104)$$
+
+where
+
+$$\lambda_{hnw} = 0,4 \frac{C_{pitch}}{G_{pitch}} \quad (105)$$
+
+$C_{pitch}$ ,  $G_{pitch}$  and  $L_{pitch}$  were determined during the open loop lag search where the subscript  $m$  denoting the subframe has been dropped from  $L_{pitch,m}$  and  $\lambda_{hnw,m}$  for notational convenience.  $L_{pitch}$  can take on fractional values so the interpolating filter employed for the open loop lag search is utilized to generate the fractionally delayed samples. Let  $x(n)$  represent the input of the harmonic noise weighting filter and  $y(n)$  represent the output. The filter can then be described by equation (106) and equation (107).
+
+$$y(n) = x(n) - \lambda_{hnw} x(n - L_{pitch}) \quad (106)$$
+
+$$x(n - L_{pitch}) = \sum_{i=0}^{P_g-1} g_j(i) x\left(n - \lfloor L_{pitch} \rfloor - \frac{P_g}{2} + i\right) \quad (107)$$
+
+where
+
+$$j = (L_{pitch} - \lfloor L_{pitch} \rfloor) 6$$
+
+Figure 4 incorporates harmonic noise weighting (for  $MODE = 1, 2$  or  $3$ ) and shows the VSELP excitation source. All error minimizations done after lag selection utilize the combination of spectral and harmonic noise weighting.
+
+For  $MODE \neq 0$ ,  $P(n)$  is the input speech signal weighted by  $W(z)C(z)$  minus the input response of  $H(z)C(z)$ . For  $MODE = 0$ ,  $P(n)$  is the input speech signal weighted by  $W(z)$  minus the zero input response of  $H(z)$ .
+
+![Figure 4: Long term predictor lag and code search. The diagram shows two signal flow graphs for MODE=1,2,or 3 and MODE=0. Both graphs show the process of calculating the total weighted error by filtering the excitation signal through H(z)C(z) and comparing it with the target signal p(n).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg)
+
+The diagram illustrates two signal flow graphs for long term predictor lag and code search, labeled MODE=1,2,or 3 and MODE=0.
+
+**MODE=1,2,or 3:** The input  $L$  is processed by a "Long term Filter state" block to produce  $b_L(n)$ . This signal is multiplied by  $\beta$  and then added to the output of a "VSELP Codebook" block (input  $I$ ) multiplied by  $\gamma$ . The sum is filtered by  $H(z)$  and then  $C(z)$  to produce  $p''(n)$ . The target signal  $p(n)$  is subtracted from  $p''(n)$  to produce the error  $e(n)$ , which is then squared and summed to produce the "total weighted error".
+
+**MODE=0:** The input  $I$  is processed by "VSELP Codebook 1" to produce a signal multiplied by  $\beta$ . The input  $H$  is processed by "VSELP Codebook 2" to produce a signal multiplied by  $\gamma$ . These two signals are multiplied together and then filtered by  $H(z)$  to produce  $p''(n)$ . The target signal  $p(n)$  is subtracted from  $p''(n)$  to produce the error  $e(n)$ , which is then squared and summed to produce the "total weighted error".
+
+Figure 4: Long term predictor lag and code search. The diagram shows two signal flow graphs for MODE=1,2,or 3 and MODE=0. Both graphs show the process of calculating the total weighted error by filtering the excitation signal through H(z)C(z) and comparing it with the target signal p(n).
+
+Figure 4: Long term predictor lag and code search
+
+The zero state response of  $H(z)C(z)$  to the pitch predictor (adaptive codebook) vector,  $b_L(n)$ , needs to be computed prior to the search of the excitation codebook. This spectrally and harmonically weighted adaptive codebook vector is represented by  $b''_L(n)$ .
+
+### 4.1.10 Code search algorithm
+
+For  $MODE \neq 0$ , the excitation codebook search procedure takes place after the long term predictor lag,  $L$ , has been determined. The codebook search procedure then chooses one codevector from the VSELP codebook. The GSM half rate speech encoder uses an excitation codebook of  $2^M$  codevectors which is constructed from  $M$  basis vectors. Defining  $v_m(n)$  as the  $m^{\text{th}}$  basis vector and  $u_i(n)$  as the  $i^{\text{th}}$  codevector in the codebook, then:
+
+$$u_i(n) = \sum_{m=1}^M \theta_{im} v_m(n) \quad (108)$$
+
+where  $0 \leq i \leq 2^M-1$ ;  $0 \leq n \leq N_S-1$ . In other words, each codevector in the codebook is constructed as a linear combination of the  $M$  basis vectors. The linear combinations are defined by the  $\theta$  parameters.
+
+$\theta_{im}$  is defined as:
+
+$$\theta_{im} = +1 \text{ if bit } m \text{ of codeword } i = 1$$
+
+$$\theta_{im} = -1 \text{ if bit } m \text{ of codeword } i = 0$$
+
+The codebook construction for the GSM half rate speech encoder can be restated as follows. Codevector  $i$  is constructed as the sum of the  $M$  basis vectors where the sign (plus or minus) of each basis vector is determined by the state of the corresponding bit in codeword  $i$ . The codebook search procedure finds the codevector which will produce the minimum total spectral and harmonic weighted error for the subframe given  $b''_L(n)$  (the zero state response of  $H(z)C(z)$  to  $b_L(n)$ ) and allowing both the gain,  $\gamma$ , and the long term filter coefficient,  $\beta$ , to be optimized for each codevector being evaluated.
+
+The filtered codevector  $f_i(n)$ , can be expressed as:
+
+$$f_i(n) = \sum_{m=1}^M \theta_{im} q_m(n) \quad (109)$$
+
+where  $q_m(n)$  is the zero state response of  $H(z)C(z)$  to basis vector  $v_m(n)$ .
+
+If  $MODE=0$ , two VSELP codebooks are the excitation sources and are searched sequentially to identify the codeword  $I$  specifying the codevector selected from the first codebook, and codeword  $H$ , identifying the codevector chosen from the second VSELP codebook. Harmonic noise weighting is not used. When searching the second VSELP codebook, each codevector is evaluated assuming optimal gains for the codevector  $I$ , and the potential codevector  $H$ .
+
+#### 4.1.10.1 Decorrelation of filtered basis vectors
+
+For  $MODE \neq 0$ , each filtered codevector,  $f_i(n)$ , is decorrelated to the long term predictor vector,  $b''_L(n)$ . If  $MODE=0$ , the  $b_L(n)$  vector and the single VSELP codebook excitation are replaced by two VSELP codebook excitations, as the excitation sources. In this case, decorrelation is only performed for the second VSELP codebook. In this case, the orthogonalization is done with respect to the filtered codevector chosen from the first VSELP codebook.
+
+Defining:
+
+$$G = \sum_{n=0}^{N_S-1} b''_L(n)^2 \quad (110)$$
+
+and
+
+$$\Psi_m = \sum_{n=0}^{N_S-1} b''_L(n) q_m(n) \quad (111)$$
+
+for  $1 \leq m \leq M$ ; then  $q'_m(n)$ , the decorrelated filtered basis vectors, can be computed by:
+
+$$q'_m(n) = q_m(n) - \left( \frac{\Psi_m}{G} \right) b''_L(n) \quad (112)$$
+
+for  $1 \leq m \leq M$  and  $0 \leq n \leq N_S-1$ .
+
+The decorrelated filtered codevectors can now be expressed as:
+
+$$f'_i(n) = \sum_{m=1}^M \theta_{im} q'_m(n) \quad (113)$$
+
+for  $0 \leq i \leq 2^M-1$  and  $0 \leq n \leq N_S-1$ .
+
+#### 4.1.10.2 Fast search technique
+
+The codebook search procedure should find the codeword  $i$  which minimizes:
+
+$$E'^i = \sum_{n=0}^{N_s-1} (p(n) - g f'^i(n))^2 \quad (114)$$
+
+Defining :
+
+$$C_i = \sum_{n=0}^{N_s-1} f'^i(n) p(n) \quad (115)$$
+
+and
+
+$$G_i = \sum_{n=0}^{N_s-1} (f'^i(n))^2 \quad (116)$$
+
+then the best codevector is the one which maximizes:
+
+$$\frac{(C_i)^2}{G_i} \quad (117)$$
+
+and the corresponding optimal gain is given by:
+
+$$\gamma_i = \frac{C_i}{G_i} \quad (118)$$
+
+The search process needs to evaluate equation (117) for each codevector. The codevector which maximizes equation (117) is then chosen. Using properties of the VSELP codebook construction, the computations required for computing  $C_i$  and  $G_i$  can be greatly simplified.
+
+defining:
+
+$$R_m = 2 \sum_{n=0}^{N_s-1} q'^m(n) p(n) \quad (119)$$
+
+for  $1 \leq m \leq M$  and
+
+$$D_{mj} = 4 \sum_{n=0}^{N_s-1} q'^m(n) q'^j(n) \quad (120)$$
+
+for  $1 \leq m \leq j \leq M$
+
+$C_i$  can be expressed as:
+
+$$C_i = \frac{1}{2} \sum_{m=1}^M \theta_{im} R_m \quad (121)$$
+
+and  $G_i$  can be expressed as:
+
+$$G_i = \frac{1}{2} \sum_{j=2}^M \sum_{m=1}^{j-1} \theta_{im} \theta_{ij} D_{mj} + \frac{1}{4} \sum_{j=1}^M D_{jj} \quad (122)$$
+
+Assuming that codeword  $u$  differs from codeword  $i$  in only one bit position, say position  $v$  such that  $\theta_{uv} = -\theta_{iv}$  and  $\theta_{um} = \theta_{im}$  for  $m \neq v$  then:
+
+$$C_u = C_i + \theta_{uv} R_v \quad (123)$$
+
+and
+
+$$G_u = G_i + \sum_{j=1}^{v-1} \theta_{uj} \theta_{uv} D_{jv} + \sum_{j=v+1}^M \theta_{uj} \theta_{uv} D_{vj} \quad (124)$$
+
+The codebook search is structured such that each successive codeword evaluated differs from the previous codeword in only one bit position, then equation (123) and equation (124) can be used to update  $C_i$  and  $G_i$  in a very efficient manner. Sequencing of the codewords in this manner is accomplished using a binary Gray code. This updating operation for both equation (123) and equation (124) can be accomplished with a total of only  $M$  multiply-accumulates per codevector.
+
+With this technique for computing  $C_i$  and  $G_i$  for the codevectors in a VSELP codebook, it is necessary to find the  $i$  which maximizes equation (117). Note that complementary codewords (see subclause 3.1.10) will have equivalent values for equation (117). Therefore only half of the codevectors need to be evaluated. Once the codevector which maximizes equation (117) is found, the sign of  $C_i$  for that codevector will determine whether that codevector or its complement will yield a positive gain,  $\gamma$ .
+
+A running maximum for equation (117) is kept during the code search then for each codevector evaluated, evaluate equation (117) and compare to the running maximum.
+
+$$\frac{(C_i)^2}{G_i} > \frac{(C_{best})^2}{G_{best}} \quad (125)$$
+
+Evaluating equation (125) directly from  $C_i$  and  $G_i$  requires one multiply, one divide and one compare operation. By cross multiplying equation (117) can be expressed as:
+
+$$(C_i)^2 G_{best} > (C_{best})^2 G_i \quad (126)$$
+
+Using equation (126) requires only three multiplies and a compare per evaluation (and no divides) where  $(C_{best})^2$  and  $G_{best}$  are updated throughout the search to reflect the running best codeword.
+
+### 4.1.11 Multimode gain vector quantization
+
+A separate GSP0 vector quantizer is derived for each of the four voicing modes. Once the frame voicing mode is selected, the vector quantizer, corresponding to that mode, is searched to select the excitation gains at each subframe of the frame.
+
+Although the interpretation of what the excitation sources are differs between MODE=0 and the remaining MODE values, the procedure for searching the gain vector quantizer is identical. In each case, the P0 term specifies the relative contribution of the first of the two excitation vectors to the total excitation energy at the subframe, where the first excitation vector is the long term prediction vector for MODE=1, 2 or 3, while the vector selected from the first of the two VSELP codebooks is used in the MODE=0 case.
+
+#### 4.1.11.1 Coding GS and P0
+
+Define  $ex(n)$  to be the excitation function at a given subframe. For MODE=1, 2 or 3,  $ex(n)$  is a linear combination of the pitch prediction vector scaled by  $\beta$ , the long term predictor coefficient, and of the codevector scaled by  $\gamma$ , its gain. In equation form
+
+$$ex(n) = \beta c_0(n) + \gamma c_1(n) \quad 0 \leq n \leq N_s - 1 \quad (127)$$
+
+where for MODE $\neq$ 0
+
+$c_0(n)$  is the unweighted long term prediction vector,  $b_L(n)$
+
+$c_1(n)$  is the unweighted codevector selected,  $u_I(n)$
+
+and for MODE=0
+
+$c_0(n)$  is the unweighted codevector selected from the first VSELP codebook,  $u_{I,1}(n)$
+
+$c_1(n)$  is the unweighted codevector selected from the second VSELP codebook,  $u_{H,2}(n)$
+
+The variable  $c'_j(n)$  is a weighted version of  $c_j(n)$ . The power in each excitation vector is given by
+
+$$R_x(k) = \sum_{n=0}^{N_s-1} c^{2k}(n) \quad 0 \leq k \leq 1 \quad (128)$$
+
+Let  $R$  be the total power in the coder subframe excitation
+
+$$R = \beta^2 R_x(0) + g^2 R_x(1) \quad (129)$$
+
+$P_0$ , the power contribution of the pitch prediction vector as a fraction of the total excitation power at a subframe,
+
+$$P_0 = \frac{\beta^2 R_x(0)}{R} \quad \text{where } 0 \leq P_0 \leq 1 \quad (130)$$
+
+Define  $R'_q(0)$  to be the quantized value of  $R(0)$  to be used for the current subframe and  $R_q(0)$  to be the quantized value of  $R(0)$ . Then:
+
+$$R'_q(0) = R_q(0)_{\text{previous frame}} \quad \text{for subframe 1} \quad (131a)$$
+
+$$R'_q(0) = R_q(0)_{\text{current frame}} \quad \text{for subframes 2, 3, 4} \quad (131b)$$
+
+Let  $RS$  be
+
+$$RS = N_s R'_q(0) \prod_{i=1}^{N_p} (1 - r_i^2) \quad (132)$$
+
+The term  $GS$  is the energy tweak parameter defined as
+
+$$R = GS \cdot RS \rightarrow GS = \frac{R}{RS} \quad (133)$$
+
+$P_0$  represents the fraction of the total subframe excitation energy which is due to the first codebook vector, and  $GS$ , the energy tweak factor which bridges the gap between  $R$ , the actual energy in the coder excitation, and  $RS$ , its estimated value.
+
+The gain bias factor  $\chi$ , formulated to force a better energy match between  $p(n)$  and the weighted synthetic excitation, is given below where.
+
+$$\chi = \min \left[ \sqrt{2, 0}, \left\{ \max \left[ 1, 0, \sqrt{\frac{R_{pp}}{\beta_{opt}^2 R_{cc}(0,0) + \gamma_{opt}^2 R_{cc}(1,1) + 2\beta_{opt} \gamma_{opt} R_{cc}(0,1)}}} \right] \right\} \right] \quad (134)$$
+
+The weighted error equation is
+
+$$E = c^2 R_{pp} - a\sqrt{GS P_0} - b\sqrt{GS(1 - P_0)} + cGS\sqrt{P_0(1 - P_0)} + dGS P_0 + eGS(1 - P_0) \quad (135)$$
+
+where
+
+$$a = 2c R_{pc}(0) \sqrt{\frac{RS}{R_x(0)}} \quad (136)$$
+
+$$b = 2c R_{pc}(1) \sqrt{\frac{RS}{R_x(1)}} \quad (137)$$
+
+$$c = \frac{2R_{cc}(0,1)RS}{\sqrt{R_x(0)R_x(1)}} \quad (138)$$
+
+$$d = \frac{RS R_{cc}(0,0)}{R_x(0)} \quad (139)$$
+
+$$e = \frac{RS R_{cc}(1,1)}{R_x(1)} \quad (140)$$
+
+$$R_{pc}(k) = \sum_{n=0}^{N_s-1} p(n)c'_k(n) \quad k=0,1 \quad (141)$$
+
+$$R_{cc}(k,j) = \sum_{n=0}^{N_s-1} c'_k(n)c'_j(n) \quad k=0,1, j=k,1 \quad (142)$$
+
+$$R_{cc}(k,j) = R_{cc}(j,k) \quad (143)$$
+
+$$R_{pp} = \sum_{n=0}^{N_s-1} p^2(n) \quad (144)$$
+
+Four separate vector quantizers for jointly coding P0 and GS are defined, one for each of the four voicing modes. The first step in quantizing of P0 and GS consists of calculating the parameters required by the error equation:
+
+$$R_{cc}(k,j) \quad k = 0, 1, j = k, 1$$
+
+$$R_x(k) \quad k = 0, 1$$
+
+$$RS$$
+
+$$R_{pc}(k) \quad k = 0, 1$$
+
+$$a, b, c, d, e$$
+
+Next equation (135) is evaluated for each of the 32 vectors in the {P0,GS} codebook, corresponding to the selected voicing mode, and the vector which minimizes the weighted error is chosen. Note that in conducting the code search
+
+$\chi^2 R_{pp}$  may be ignored in equation (135), since it is a constant.  $\beta_q$ , the quantized long term predictor coefficient, and  $\gamma_q$ , the quantized gain, are reconstructed from
+
+$$\beta_q = \sqrt{\frac{RSGS_{vq} P0_{vq}}{R_x(0)}} \quad (145)$$
+
+$$g_q = \sqrt{\frac{RSGS_{vq}(1-P0_{vq})}{R_x(1)}} \quad (146)$$
+
+where P0<sub>vq</sub> and GS<sub>vq</sub> are the elements of the vector chosen from the {P0,GS} codebook.
+
+A special case occurs when the long term predictor is disabled for a certain subframe, but voicing MODE≠0. This will occur when the state of the long term predictor is populated entirely by zeroes.
+
+For that case, the following error equation is used:
+
+$$E \cong \chi^2 R_{pp} - b\sqrt{GS} + eGS \quad (147)$$
+
+For this case the quantized codevector gains are:
+
+$$\beta_q = 0 \quad (148)$$
+
+$$g_q = \sqrt{\frac{RSGS_{vq}(1-P0_{vq})}{R_x(1)}} \quad (149)$$
+
+## 4.2 GSM half rate speech decoder
+
+![Block diagram of the GSM half rate speech decoder for MODE = 1, 2 or 3. The diagram shows the flow from input parameters (LPC 1-3, R0, INT_LPC, MODE, LAG_1-4, CODE_1-4, GSP 0_1-4) through various processing blocks including Long Term Filter State, gain calculations, VSELP Codebook, pitch prefilter, synthesis filter, spectral postfilter, and automatic gain control to produce the output speech signal s(n).](b51423b6c049f5b5fcde42e50b58f18b_img.jpg)
+
+The diagram illustrates the GSM half rate speech decoder architecture for MODE = 1, 2 or 3. The input parameters are grouped into three sets:
+
+- LPC parameters:** LPC 1, LPC 2, LPC 3, R0, and INT\_LPC. These are fed into the 'Long Term Filter State' block and the 'calculation of gains' block.
+- MODE and LAG parameters:** MODE, LAG\_1, CODE\_1, LAG\_2, CODE\_2, LAG\_3, CODE\_3, LAG\_4, and CODE\_4. These are fed into the 'calculation of gains' block and the 'VSELP Codebook' block.
+- GSP parameters:** GSP 0\_1, GSP 0\_2, GSP 0\_3, and GSP 0\_4. These are fed into the 'calculation of gains' block.
+
+The processing flow is as follows:
+
+- The 'calculation of gains' block takes the input parameters and produces gain values  $L$ ,  $\beta$ ,  $\gamma$ , and  $I$ .
+- The 'Long Term Filter State' block takes the LPC parameters and the gain  $L$  to produce the long-term filter state  $b_L(n)$ .
+- The gain  $\beta$  is multiplied by  $b_L(n)$  to produce an intermediate signal.
+- The gain  $\gamma$  is multiplied by the output of the 'VSELP Codebook' (which takes gain  $I$  as input) to produce another intermediate signal.
+- These two signals are summed to produce the combined excitation signal  $ex(n)$ .
+- The signal  $ex(n)$  is processed by the 'pitch prefilter' to produce the prefiltered excitation  $ex_{ps}(n)$ .
+- The signal  $ex_{ps}(n)$  is then processed by the 'synthesis filter' to produce the reconstructed speech signal  $s(n)$ .
+- The signal  $s(n)$  is processed by the 'spectral postfilter'.
+- Finally, the signal is processed by the 'automatic gain control' block to produce the final 'output speech'.
+
+Feedback loops are shown from the 'synthesis filter' output  $s(n)$  back to the 'Long Term Filter State' and the 'spectral postfilter'.
+
+Block diagram of the GSM half rate speech decoder for MODE = 1, 2 or 3. The diagram shows the flow from input parameters (LPC 1-3, R0, INT\_LPC, MODE, LAG\_1-4, CODE\_1-4, GSP 0\_1-4) through various processing blocks including Long Term Filter State, gain calculations, VSELP Codebook, pitch prefilter, synthesis filter, spectral postfilter, and automatic gain control to produce the output speech signal s(n).
+
+Figure 5: The GSM half rate speech decoder for MODE = 1, 2 or 3
+
+A block diagram of the GSM half rate speech decoder for MODE=1, 2 or 3 is given in figure 5. The speech decoder creates the combined excitation signal,  $ex(n)$ , from the long term filter state and the VSELP codevector. For MODE=0, the long term filter state is replaced by another VSELP codebook and the pitch prefilter is not used. The combined excitation is then processed by an adaptive pitch prefilter and gain. The prefiltered excitation is applied to the LPC synthesis filter. After reconstructing the speech signal with the synthesis filter, an adaptive spectral postfilter is applied followed by an automatic gain control which is the final processing step in the speech decoder.
+
+### 4.2.1 Excitation generation
+
+The combined excitation,  $ex(n)$ , shall be computed as shown in equation (127)
+
+The combined excitation,  $ex(n)$ , is filtered by the synthesis filter to generate the speech signal. The synthesis filter is a tenth order all pole filter. The filter coefficients for the subframe are the  $\alpha_i$ 's defined in subclause 4.1.6. The filter coefficients will change from subframe to subframe. The filter state shall be preserved from subframe to subframe. A direct form filter shall be used for the synthesis filter.
+
+### 4.2.2 Adaptive pitch prefilter
+
+Given  $ex(n)$  as the input,  $ex_p(n)$ , the pitch prefiltered output, is defined by
+
+$$ex_p(n) = ex(n) + \xi ex_p(n - L) \quad ; \text{for } 0 \leq n \leq N_s - 1 \quad (150)$$
+
+where
+
+$$x = \begin{cases} 0,3\text{Min}[\beta, \sqrt{P0}] & ; \text{MODE}^1 0 \\ 0 & ; \text{MODE} = 0 \end{cases} \quad (151)$$
+
+Since L can be fractional in value, an interpolating filter is used. This is the same interpolating filter which is used for the open loop lag search. A gain scale factor is computed and is used to scale the pitch prefiltered excitation, prior to applying it to the LPC synthesis filter.  $P_{\text{scale}}$ , the gain scale factor, is
+
+$$P_{\text{scale}} = \sqrt{\frac{\sum_{n=0}^{N-1} \text{ex}^2(n)}{\sum_{n=0}^{N-1} \text{ex}_p^2(n)}} \quad (152)$$
+
+Thus  $\text{ex}_{\text{ps}}(n)$ , the gain corrected pitch prefiltered excitation which drives the LPC synthesis filter, is given by
+
+$$\text{ex}_{\text{ps}}(n) = P_{\text{scale}} \text{ex}_p(n) \quad ; \text{for } 0 \leq n \leq N_s-1 \quad (153)$$
+
+### 4.2.3 Synthesis Filter
+
+A direct form synthesis filter is used:
+
+$$s(n) = \text{ex}_{\text{ps}}(n) + \sum_{i=1}^{10} \alpha_i s(n-i) \quad , 0 \leq n \leq N_s-1 \quad (154)$$
+
+### 4.2.4 Adaptive spectral postfilter
+
+The perceptual quality of the synthetic speech is enhanced by using an adaptive postfilter as the final processing step. The general form of the postfilter is given by:
+
+$$\bar{s}(n) = s(n) - \sum_{i=1}^{N_p} r_i^j \alpha_i s(n-i) \quad , 0 \leq n \leq N_s-1 \quad (155)$$
+
+$$\mathbf{s}(n) = \bar{s}(n) + \sum_{i=1}^{N_p} (0,75)^i \alpha_i \mathbf{s}(n-i) \quad , 0 \leq n \leq N_s-1 \quad (156)$$
+
+$$\hat{s}(n) = \tilde{s}(n) - 0,2 \tilde{s}(n-1) \quad , 0 \leq n \leq N_s-1 \quad (157)$$
+
+The adaptive spectral postfilter numerator polynomial equation (155) is replaced by a spectrally smoothed version of the adaptive spectral postfilter denominator polynomial equation (156). To derive the coefficients of the numerator polynomial, the denominator polynomial coefficients are converted to the autocorrelation coefficients  $R(i)$ . The SST bandwidth expansion function is then applied to the autocorrelation sequence,
+
+$$R_{\text{sst}}(i) = R(i) W_{\text{sst}}(i) \quad , 0 \leq i \leq N_p \quad (158)$$
+
+and the numerator polynomial coefficients are calculated from the modified autocorrelation sequence via the AFLAT recursion.
+
+From  $R_{\text{sst}}(i)$  the reflection coefficients which define the combined spectrally noise weighted synthesis filter are computed using the AFLAT recursion once per frame.
+
+STEP 1 Define the initial conditions for the AFLAT recursion:
+
+$$P_o(i) = R_{\text{sst}}(i) \quad , 0 \leq i \leq N_p \quad (159)$$
+
+$$V_o(i) = R_{\text{sst}}(|i+1|) \quad , 1-N_p \leq i \leq N_p-1 \quad (160)$$
+
+STEP 2 Initialize  $j$ , the index of the lattice stage, to point to the first lattice stage:
+
+$$j=1 \quad (161)$$
+
+STEP 3 Compute  $r_j$ , the  $j$ -th reflection coefficient, using:
+
+$$r_j = -\frac{V_{j-1}(0)}{P_{j-1}(0)} \quad (162)$$
+
+STEP 4 Given  $r_j$ , update the values of  $V_j$  and  $P_j$  arrays using:
+
+$$P_j(i) = (1 + r_j^2)P_{j-1}(i) + r_j[V_{j-1}(i) + V_{j-1}(-i)] \quad , 0 \leq i \leq N_p - j - 1 \quad (163)$$
+
+$$V_j(i) = V_{j-1}(i + 1) + r_j^2 V_{j-1}(-i - 1) + 2r_j P_{j-1}(|i + 1|) \quad , 1+j-N_p \leq i \leq N_p - j - 1 \quad (164)$$
+
+STEP 5 Increment  $j$ :
+
+$$j = j + 1$$
+
+STEP 6 If  $j \leq N_p$  go to step 3, otherwise all  $N_p$  reflection coefficients have been obtained.
+
+STEP 7 The reflection coefficients,  $r_j$ , are then converted to  $\bar{\alpha}_i$ , the direct-form LP filter coefficients for use in the adaptive spectral postfilter numerator polynomial.
+
+The resultant adaptive spectral postfilter is derived from equations 155, 156 and 157:
+
+$$\bar{s}(n) = s(n) - \sum_{i=1}^{N_p} \bar{\alpha}_i s(n-i) \quad , 0 \leq n \leq N_s - 1 \quad (165)$$
+
+$$\tilde{s}(n) = \bar{s}(n) + \sum_{i=1}^{N_p} (0,75)^i \alpha_i \tilde{s}(n-i) \quad , 0 \leq n \leq N_s - 1 \quad (166)$$
+
+$$\hat{s}(n) = \tilde{s}(n) - 0,2 \tilde{s}(n-1) \quad , 0 \leq n \leq N_s - 1 \quad (167)$$
+
+In order to reduce the computations needed to compute the spectrally smoothed numerator coefficients, the spectral smoothing operation is performed once per frame on the denominator coefficients corresponding to the uninterpolated coefficients. This will yield the coefficients for the numerator of the spectral postfilter for subframe four. The numerator coefficients for subframes one, two, and three are interpolated using the same interpolation scheme that is used for the LPC synthesis coefficients (see subclause 4.1.6).
+
+As in the case of the pitch prefilter, a means of automatic gain control is needed to ensure unity gain through the spectral postfilter. A scale factor,  $S_{\text{scale}}$ , is given by:
+
+$$S'_{\text{scale}}(n) = (0,9875 S'_{\text{scale}}(n-1) ) + (0,0125 S_{\text{scale}} ) \quad (168)$$
+
+Scale factor,  $S_{\text{scale}}$ , is the square root of the ratio of the input signal energy to the output signal energy over the subframe.
+
+The output of the spectral postfilter is then multiplied by  $S'_{\text{scale}}$  as the last step in reconstructing the speech signal in the speech decoder.
+
+### 4.2.5 Updating decoder states
+
+The long term predictor state,  $r(n)$ , is updated by:
+
+$$r(n) = r(n+40) \quad \text{for } -146 \leq n \leq -41 \quad (169)$$
+
+$$r(n) = ex(n+40) \quad \text{for } -40 \leq n \leq -1 \quad (170)$$
+
+# --- 5 Homing sequences
+
+## 5.1 Functional description
+
+The half rate speech codec as well as the DTX system and comfort noise generator are described in a bit exact arithmetic to allow for easy type approval as well as general testing purposes of the half rate speech codec.
+
+The response of the codec to a predefined input sequence can only be foreseen if the internal state variables of the codec are in a predefined state at the beginning of the experiment. Therefore, the codec has to be put in a so called home state before a bit exact test can be performed. This is usually done by a reset.
+
+To allow a reset of the codec in remote locations, special homing frames have been defined for the encoder and the decoder, thus enabling a codec homing by inband signalling.
+
+The codec homing procedure is defined in such a way, that on either direction (encoder or decoder), the homing functions are called after processing the homing frame that is input. The output corresponding to the first homing frame is therefore dependent on the codec state when receiving that frame and hence usually not known. The response to any further homing frame in one direction is by definition a homing frame of the other direction. This procedure allows homing of both, the encoder and decoder from either side, if a loop back configuration is implemented, taking proper framing into account.
+
+## 5.2 Definitions
+
+**encoder homing frame:** The encoder homing frame consists of 160 identical samples, each 13 bit long, with the least significant bit set to "one" and all other bits set to "zero". When written to 16 bit long words with left justifications, the samples have a value of 0008 hex. Test sequence SEQ05.INP described in GSM 06.07 [3] defines the encoder homing frame. The speech decoder has to produce this frame as a response to the second and any further decoder homing frame if at least two decoder homing frames were input to the decoder consecutively.
+
+**decoder homing frame:** The decoder homing frame has a fixed set of speech parameters as defined in test sequence SEQ05.INP described in GSM 06.07 [3]. It is the natural response of the speech encoder to the second and any further encoder homing frame if at least two encoder homing frames were input to the encoder consecutively.
+
+## 5.3 Encoder homing
+
+Whenever the half rate speech encoder receives at its input an encoder homing frame exactly aligned with its internal speech frame segmentation, the following events take place:
+
+- Step 1: The speech encoder performs its normal operation including VAD and DTX and produces a speech parameter frame at its output which is in general unknown. But if the speech encoder was in its home state at the beginning of that frame, then the resulting speech parameter frame is identical to the decoder homing frame (this is the way how the decoder homing frame was constructed).
+- Step 2: After successful termination of that operation, the speech encoder provokes the homing functions for all submodules including VAD and DTX and sets all state variables into their home state. On the reception of the next input frame, the speech encoder will start from its home state.
+
+NOTE: Applying a sequence of N encoder homing frames will cause at least N-1 decoder homing frames at the output of the speech encoder.
+
+## 5.4 Decoder homing
+
+Whenever the speech decoder receives at its input a decoder homing frame, then the following events take place:
+
+- Step 1: The speech decoder performs its normal operation including comfort noise generation and produces a speech frame at its output which is in general unknown. But if the speech decoder was in its home state at the beginning of that frame, then the resulting speech frame is replaced by the encoder homing frame. This would not naturally be the case but is forced by this definition here.
+
+Step 2: After successful termination of that operation, the speech decoder provokes the homing functions for all submodules including the comfort noise generator and sets all state variables into their home state. On the reception of the next input frame, the speech decoder will start from its home state.
+
+NOTE 1: Applying a sequence of N decoder homing frames will cause at least N-1 encoder homing frames at the output of the speech decoder.
+
+NOTE 2: By definition the first 58 bits of the decoder homing frame must differ in at least one bit position from the first 58 bits of any of the decoder test sequences. Therefore, if the decoder is in its home state, it is sufficient to check only these first 58 bits to detect a subsequent decoder homing frame. This definition is made to support a delay optimised implementation in the TRAUs uplink direction.
+
+## 5.5 Encoder home state
+
+In GSM 06.06 [2], a listing of all the encoder state variables with their predefined values when in the home state is given.
+
+## 5.6 Decoder home state
+
+In GSM 06.06 [2], a listing of all the decoder state variables with their predefined values when in the home state is given.
+
+# Annex A (normative): Codec parameter description
+
+## A.1 Codec parameter description
+
+The following is a list of all the parameters which are coded for each 20 ms speech frame. The basic data rate of the speech coder is 5,6 kbps. Therefore each 20 ms speech frame consists of 112 bits. These bits are given in table A.1.
+
+**Table A.1: Codec parameter description**
+
+| Parameter                        | No. of bits | Description                                    |
+|----------------------------------|-------------|------------------------------------------------|
+| Frame bits:                      |             |                                                |
+| MODE                             | 2           | voicing mode                                   |
+| R0                               | 5           | frame energy                                   |
+| LPC1                             | 11          | reflection coefficient vector $r_1$ - $r_3$    |
+| LPC2                             | 9           | reflection coefficient vector $r_4$ - $r_6$    |
+| LPC3                             | 8           | reflection coefficient vector $r_7$ - $r_{10}$ |
+| INT_LPC                          | 1           | the soft interpolation bit for the frame       |
+| Subframe bits (MODE = 1,2 or 3): |             |                                                |
+| LAG_1                            | 8           | lag for first subframe                         |
+| LAG 2                            | 4           | lag delta code for second subframe             |
+| LAG 3                            | 4           | lag delta code for third subframe              |
+| LAG 4                            | 4           | lag delta code for fourth subframe             |
+| CODE 1                           | 9           | codebook, I, for first subframe                |
+| CODE 2                           | 9           | codebook, I, for second subframe               |
+| CODE 3                           | 9           | codebook, I, for third subframe                |
+| CODE 4                           | 9           | codebook, I, for fourth subframe               |
+| GSP0 1                           | 5           | {P0,GS} code for first subframe                |
+| GSP0 2                           | 5           | {P0,GS} code for second subframe               |
+| GSP0 3                           | 5           | {P0,GS} code for third subframe                |
+| GSP0 4                           | 5           | {P0,GS} code for fourth subframe               |
+| Subframe bits (MODE=0):          |             |                                                |
+| CODE1_1                          | 7           | codebook code, I, for first subframe           |
+| CODE2_1                          | 7           | codebook code, H, for first subframe           |
+| CODE1_2                          | 7           | codebook code, I, for second subframe          |
+| CODE2_2                          | 7           | codebook code, H, for second subframe          |
+| CODE1_3                          | 7           | codebook code, I, for third subframe           |
+| CODE2_3                          | 7           | codebook code, H, for third subframe           |
+| CODE1_4                          | 7           | codebook code, I, for fourth subframe          |
+| CODE2_4                          | 7           | codebook code, H, for fourth subframe          |
+| GSP0 1                           | 5           | {P0,GS} code for first subframe                |
+| GSP0 2                           | 5           | {P0,GS} code for second subframe               |
+| GSP0 3                           | 5           | {P0,GS} code for third subframe                |
+| GSP0 4                           | 5           | {P0,GS} code for fourth subframe               |
+
+### A.1.1 MODE
+
+The speech coder is defined by 4 voicing modes. MODE is a two bit code which specifies which of the four voicing modes is used at the current frame. The MODE indicates which definition of the frame bits to apply to the current frame.
+
+### A.1.2 R0
+
+R0 is a code which represents the average signal power of the input speech for the frame. The average signal power is computed using an analysis window which is centered over the last 100 samples of the frame.
+
+### A.1.3 LPC1 - LPC3
+
+The 10 reflection coefficients are vector quantized in three vector segments. The first vector segment codes reflection coefficients  $r_1 - r_3$ , the second vector segment codes coefficients  $r_4 - r_6$ , the third vector segment codes coefficients  $r_7 - r_{10}$ .
+
+### A.1.4 LAG\_1 - LAG\_4
+
+LAG\_1, the lag for the first subframe, can take on the value in the range of 21 to 142. Eight bits are used to encode the lag which may be fractional in value. Each of the remaining lag values ( LAG\_2 through LAG\_4) is delta coded relative to the preceding subframe's coded value of the lag, with a deviation of -8 to +7 allowable lag value levels specified by a four bit code.
+
+### A.1.5 CODEx\_1 - CODEx\_4
+
+If  $MODE \neq 0$ , the code value for the VSELP codebook is the codeword I as derived by the codebook search procedure. If  $MODE=0$ , two VSELP codebooks are sequentially searched, with codeword I, specifying the codevector from the first VSELP codebook, assigned onto CODE1\_x, and codeword H, specifying the codeword selected from the second VSELP codebook, assigned onto CODE2\_x, where x is the subframe number.
+
+### A.1.6 GSP0\_1 - GSP0\_4
+
+The {P0,GS} codebook contains the values needed to determine the gain factors for the excitation vectors of a given subframe. The index of the corresponding codebook entry is assigned to GSP0\_x.
+
+The speech coder is a multimode speech coder, defined by four voicing modes:
+
+|          |                   |
+|----------|-------------------|
+| MODE = 0 | unvoiced          |
+| MODE = 1 | slightly voiced   |
+| MODE = 2 | moderately voiced |
+| MODE = 3 | strongly voiced   |
+
+If  $MODE=0$ , the adaptive codebook (long-term predictor) and the VSELP codebook are replaced by two other VSELP codebooks.
+
+## A.2 Basic coder parameters
+
+The following are the basic parameters for the 5 600 bps GSM half rate speech codec system.
+
+|                |                            |                     |
+|----------------|----------------------------|---------------------|
+|                | sampling rate              | 8 kHz               |
+| N <sub>F</sub> | frame length               | 160 samples (20 ms) |
+| N <sub>s</sub> | subframe length            | 40 samples (5 ms)   |
+| N <sub>p</sub> | short term predictor order | 10                  |
+
+# Annex B (normative): Order of occurrence of the codec parameters over Abis
+
+The order of occurrence of the codec parameters over the Abis is defined for unvoiced speech (MODE = 0) and voiced speech (MODE = 1, 2 or 3) in tables B.1 and B.2 respectively.
+
+**Table B.1: Occurrence of the codec parameters over Abis for unvoiced speech (MODE = 0)**
+
+| Parameter | No. of bits | Bit No. (MSB - LSB) |
+|-----------|-------------|---------------------|
+| R0        | 5           | b1 - b5             |
+| LPC1      | 11          | b6 - b16            |
+| LPC2      | 9           | b17 - b25           |
+| LPC3      | 8           | b26 - b33           |
+| INT_LPC   | 1           | b34                 |
+| MODE      | 2           | b35 - b36           |
+|           |             |                     |
+| CODE1 1   | 7           | b37 - b43           |
+| CODE2 1   | 7           | b44 - b50           |
+| GSP0 1    | 5           | b51 - b55           |
+|           |             |                     |
+| CODE1 2   | 7           | b56 - b62           |
+| CODE2 2   | 7           | b63 - b69           |
+| GSP0 2    | 5           | b70 - b74           |
+|           |             |                     |
+| CODE1 3   | 7           | b75 - b81           |
+| CODE2 3   | 7           | b82 - b88           |
+| GSP0 3    | 5           | b89 - b93           |
+|           |             |                     |
+| CODE1 4   | 7           | b94 - b100          |
+| CODE2 4   | 7           | b101 - b107         |
+| GSP0 4    | 5           | b108 - b112         |
+
+**Table B.2: Occurrence of the codec parameters over Abis for voiced speech (MODE = 1, 2 or 3)**
+
+| Parameter | No. of bits | Bit No. (MSB - LSB) |
+|-----------|-------------|---------------------|
+| R0        | 5           | b1 - b5             |
+| LPC1      | 11          | b6 - b16            |
+| LPC2      | 9           | b17 - b25           |
+| LPC3      | 8           | b26 - b33           |
+| INT_LPC   | 1           | b34                 |
+| MODE      | 2           | b35 - b36           |
+|           |             |                     |
+| LAG 1     | 8           | b37 - b44           |
+| CODE1     | 9           | b45 - b53           |
+| GSP0 1    | 5           | b54 - b58           |
+|           |             |                     |
+| LAG 2     | 4           | b59 - b62           |
+| CODE2     | 9           | b63 - b71           |
+| GSP0 2    | 5           | b72 - b76           |
+|           |             |                     |
+| LAG 3     | 4           | b77 - b80           |
+| CODE3     | 9           | b81 - b89           |
+| GSP0 3    | 5           | b90 - b94           |
+|           |             |                     |
+| LAG 4     | 4           | b95 - b98           |
+| CODE4     | 9           | b99 - b107          |
+| GSP0 4    | 5           | b108 - b112         |
+
+# --- Annex C (informative): Bibliography
+
+M. R. Schroeder and B. S. Atal, "Code-Excited Linear Prediction (CELP): High Quality Speech at Very Low Bit Rates", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 937-940, March 1985.
+
+G. Davidson and A. Gersho, "Complexity Reduction Methods for Vector Excitation Coding", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 3055-3058, April 1986.
+
+I. Gerson and M. Jasiuk, "Vector Sum Excited Linear Prediction (VSELP) Speech Coding at 8 kbps", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 461-464, April 1990.
+
+P. Kroon and B. S. Atal, "Pitch Predictors with High Temporal Resolution", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 661-664, April 1990.
+
+I. A. Gerson, "Method and Means of Determining Coefficients for Linear Predictive Coding", U. S. Patent #4,544,919, Oct. 1985.
+
+A. Cumani, "On a Covariance-Lattice Algorithm for Linear Prediction", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 651-654, May 1982.
+
+M. McLaughlin, I. Gerson, F. Hudziak, and K. Kloker, "High Performance Processor for Real-Time Speech Applications", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 859-863, April 1980.
+
+Y. Tohkura, F. Itakura and S. Hashimoto, "Spectral Smoothing Technique in PARCOR Speech Analysis-Synthesis", **IEEE Trans. Acoustics, Speech and Signal Processing**, vol. ASSP-26, pp. 591-596, Dec. 1978.
+
+W. Kleijn, D. Krasinski, and R. Ketchum, "Improved Speech Quality and Efficient Vector Quantization in SELP", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 155-158, April 1988.
+
+Y. Linde, A. Buzo, and R. M. Gray, "An Algorithm for Vector Quantizer Design", **IEEE Trans. Comm.**, vol. COM-28, pp. 84-95, Jan. 1980.
+
+Juin-Hwey Chen and Allen Gersho, "Real-Time Vector APC Speech Coding at 4800 bps with Adaptive Postfiltering", **Proc. IEEE Int. Conf. on Acoustics, Speech and Signal Processing**, pp. 2185-2188, 1987.
+
+# Annex D (informative): Change history
+
+| Change history |           |         |                  |             |                      |
+|----------------|-----------|---------|------------------|-------------|----------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments     |
+| SMG#13         |           |         |                  | 4.0.0       | ETSI Publication     |
+| SMG#20         |           |         |                  | 5.0.0       | Release 1996 version |
+| SMG#22         | 430/97    | A001    |                  | 5.1.1       | UAP 60 comments      |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46022/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-16/46_series/46022/367926125450c2bc3f4bdca9d59a62ba_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f92a6645674d520da3b61bc2d6f7caed8a101cf
--- /dev/null
+++ b/marked/Rel-16/46_series/46022/367926125450c2bc3f4bdca9d59a62ba_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:13a1285f433cbcb11c3fe5515710c542aa98f22bc014743f922838e24551398a
+size 58544
diff --git a/marked/Rel-16/46_series/46022/raw.md b/marked/Rel-16/46_series/46022/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..40e757e246945eec87ce534171a8340beb12bed8
--- /dev/null
+++ b/marked/Rel-16/46_series/46022/raw.md
@@ -0,0 +1,381 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                    |    |
+|------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                     | 4  |
+| 1 Scope.....                                                                       | 5  |
+| 2 References.....                                                                  | 5  |
+| 3 Definitions, symbols and abbreviations .....                                     | 5  |
+| 3.1 Definitions.....                                                               | 5  |
+| 3.2 Symbols.....                                                                   | 6  |
+| 3.3 Abbreviations .....                                                            | 6  |
+| 4 General.....                                                                     | 6  |
+| 5 Functions on the transmit (TX) side .....                                        | 7  |
+| 5.1 Background acoustic noise evaluation .....                                     | 7  |
+| 5.2 Modification of the speech encoding algorithm during SID frame generation..... | 8  |
+| 5.3 SID-frame encoding .....                                                       | 9  |
+| 6 Functions on the receive (RX) side.....                                          | 10 |
+| 6.1 Averaging of the GS parameters .....                                           | 10 |
+| 6.2 Comfort noise generation and updating .....                                    | 11 |
+| 7 Computational details .....                                                      | 11 |
+| Annex A (informative): Change Request History.....                                 | 12 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".**
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX) on half rate speech traffic channels.
+
+The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the half rate speech traffic channel.
+
+The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the half rate speech traffic channel, the transmitter requirements are only for those where downlink DTX will be used.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech transcoding".
+- [3] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [4] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); "Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply.
+
+**frame:** time interval of 20 ms corresponding to the time segmentation of the half rate speech transcoder, also used as a short term for a traffic frame.
+
+**H(Z):** combination of the short term (spectral) filter A(z) and the spectral weighting filter W(z).
+
+**SID codeword:** fixed bit pattern for labelling a traffic frame as a SID frame.
+
+**SID field:** bit positions of the SID codeword within a SID frame.
+
+**SID frame:** frame characterized by the SID (Silence Descriptor) codeword. It conveys information on the acoustic background noise.
+
+**SP flag:** speech flag.
+
+**speech frame:** traffic frame that cannot be classified as a SID frame.
+
+**VAD flag:** Voice Activity Detector flag.
+
+**W(Z):** spectral weighting filter of the GSM half rate speech codec.
+
+Other definitions of terms used in the present document can be found in GSM 06.20 [2] and GSM 06.41 [3]. The overall operation of DTX is described in GSM 06.41 [3].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|               |                                                                                                              |
+|---------------|--------------------------------------------------------------------------------------------------------------|
+| GS            | Energy tweak parameter.                                                                                      |
+| R0            | Frame energy value.                                                                                          |
+| R(i)          | Unquantised (normalized) autocorrelation sequence.                                                           |
+| $r_j$         | Optimal reflection coefficient.                                                                              |
+| b             |                                                                                                              |
+| SUM ( x(n) )  | = x(a) + x(a+1) + .... + x(b-1) + x(b); (Accumulation).                                                      |
+| n=a           |                                                                                                              |
+| GSP0 codeword | Vector quantization index, joint vector quantization of the parameters GS and P0.                            |
+| P0            | Power contribution of the first excitation vector as a fraction of the total excitation power at a subframe. |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                                                                                                            |
+|-------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| AFLAT | Autocorrelation Fixed Point LAttice Technique (used in the GSM half rate speech codec for the vector quantization of the LPC coefficients) |
+| BSS   | Base Station System                                                                                                                        |
+| DTX   | Discontinuous Transmission                                                                                                                 |
+| ETS   | European Telecommunication Standard                                                                                                        |
+| GSM   | Global System for Mobile communications                                                                                                    |
+| MS    | Mobile Station                                                                                                                             |
+| SID   | SIlence Descriptor                                                                                                                         |
+| RX    | Receive                                                                                                                                    |
+| TX    | Transmit                                                                                                                                   |
+| VAD   | Voice Activity Detector                                                                                                                    |
+| VQ    | Vector Quantization                                                                                                                        |
+
+For abbreviations not given in this subclause, see GSM 01.04 [1].
+
+# --- 4 General
+
+A problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is switched off, resulting in a modulation of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect may be annoying for the listener, especially in a car environment with high background noise levels. In bad cases, the speech may be hardly intelligible.
+
+The present document specifies a solution to overcome this problem by generating synthetic noise similar to the transmit (TX) side background noise on the receive (RX) side. The comfort noise parameters are estimated on the TX side and transmitted to the RX side before the radio transmission is switched off and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the TX side.
+
+# --- 5 Functions on the transmit (TX) side
+
+The comfort noise evaluation algorithm uses the following parameters of the GSM half rate speech encoder, defined in GSM 06.20 [2]:
+
+- the unquantized frame energy value R0;
+- the unquantized (normalized) autocorrelation sequence R(i) derived from the optimal reflection coefficients  $r_j$ ;
+
+- the quantized energy tweak parameter GS.
+
+These parameters give information on the level (R0 and GS) and the spectrum (R(i)) of the background noise.
+
+Two of the evaluated comfort noise parameters (R0 and R(i)) are encoded into a special frame, called a Silence Descriptor (SID) frame, for transmission to the RX side. While the energy tweak parameter GS can be evaluated in the encoder and decoder in the same way as given in subclause 5.1, therefore no transmission of GS is necessary.
+
+The SID frame also serves to initiate the comfort noise generation on the RX side, as a SID frame is always sent at the end of a speech burst, i.e. before the radio transmission is terminated.
+
+The scheduling of SID or speech frames on the radio path is described in GSM 06.41 [3].
+
+## 5.1 Background acoustic noise evaluation
+
+The comfort noise parameters to be encoded into a SID frame are calculated over 8 consecutive frames marked with Voice Activated Detector (VAD) flag = "0", as follows:
+
+The frame energy values shall be averaged according to the equation:
+
+$$\text{mean}(R0[j]) = 1/8 \sum_{n=0}^7 R0[j-n];$$
+
+where:
+
+$R0[j]$  is the frame energy value of the current frame  $j$  ( $n=0$ );
+
+$R0[j-n]$  is the frame energy of the previous frames ( $n=1, \dots, 7$ );
+
+$n$  is the averaging period index  $n=0, 1, \dots, 7$ ;
+
+$j$  is the frame index.
+
+The averaged value  $\text{mean}(R0[j])$  is encoded using the same encoding table that is also used by the GSM half rate speech codec for the encoding of the non-averaged R0 values in ordinary speech encoding mode.
+
+The (normalized) autocorrelation sequence  $R(i)$  shall be averaged according to the equation:
+
+$$\text{mean}(R[j](i)) = 1/8 \sum_{n=0}^7 R[j-n](i) \quad i = 0, 1, 2, \dots, 10;$$
+
+where:
+
+$R[j](i)$  is the  $i$ 'th autocorrelation value of the current frame  $j$  ( $n=0$ );
+
+$R[j-n](i)$  is the  $i$ 'th autocorrelation value of one of the previous frames ( $n=1, \dots, 7$ );
+
+$n$  is the averaging period index  $n=0, 1, \dots, 7$ ;
+
+$j$  is the frame index.
+
+The averaged values  $\text{mean}(R[j](i))$  are used as input parameters of the Autocorrelation Fixed Point LAttice Technique (AFLAT) recursion algorithm which calculates the Vector Quantization (VQ) indices of the reflection coefficients, see GSM 06.20 [2].
+
+The SID frame containing the quantization index of  $\text{mean}(R0[j])$ , the VQ indices of  $\text{mean}(R[j](i))$  and the SID codeword is passed to the radio subsystem instead of frame number  $j$  (see subclause 5.3, SID-frame encoding).
+
+The averaging of the energy tweak parameters GS is made on the basis of the quantized GS parameters. The quantized GS parameters can be derived from the GSP0 indices. These indices are used as pointers to the GSP0 vector
+
+quantization codebook. The GS components of the selected GSP0 vectors are the quantized GS values which will be averaged.
+
+The quantized energy tweak parameters GS shall be averaged according to the equation:
+
+$$\text{mean (GS[j])} = 1/28 \sum_{n=1}^7 \sum_{i=1}^4 \text{GS}[j-n](i);$$
+
+where:
+
+GS[j](i) is the quantized energy tweak parameter in subframe i of the current frame j (n=0);
+
+GS[j-n](i) is the quantized energy tweak parameter in subframe i of one of the last frames (n=1,...,7);
+
+n is the averaging period index n=1,2,...,7;
+
+i is the subframe index i=1,2,3,4;
+
+j is the frame index.
+
+NOTE: The averaging of GS is made over 7 frames only.
+
+For each comfort noise insertion period, the averaging of the GS parameters is done only once before sending the first SID frame to the decoder and for the rest of the comfort noise insertion period, the averaged value mean(GS[j]) will be frozen.
+
+Under normal conditions, the averaging of the GS parameters is done during the hangover period, but in case of short speech bursts handling, the hangover period can be skipped under certain conditions, see GSM 06.41 [3]. In such cases, the GS parameters of the last seven speech frames marked with SP flag="1" are averaged.
+
+The hangover period is defined in GSM 06.41 [3]. It is a period added at the end of a speech burst in which no voice activity is detected (VAD flag="0"), but the speech encoder stays for the processing of 7 speech frames in speech encoding mode (SP flag="1"). This hangover period and the first SID frame are used for averaging the comfort noise parameters contained in the first SID frame.
+
+mean(GS[j]) can be evaluated at the decoder in the same way as in the encoder, because in both the encoder and decoder, the GSP0 indexes of the last 7 speech frames shall be kept in memory. In case of an error free transmission, the GSP0 indexes are identical at the encoder and decoder.
+
+## 5.2 Modification of the speech encoding algorithm during SID frame generation
+
+When the SP flag is equal to "0", the speech encoding algorithm is modified in the following way:
+
+- the non-averaged reflection coefficients which are used to derive the filter coefficients of the filters H(z) and W(z) of the speech encoder are not quantized;
+- the unvoiced speech encoding mode is forced. This simplifies the open loop long term prediction processing: only the integer lags have to be calculated, no determination of fractional lags is necessary and the frame lag trajectory derivation can be avoided;
+- no fixed codebook search is made. In each subframe, the indices of both fixed codebooks (CODE1\_1, ..., CODE1\_4 and CODE2\_1, ..., CODE2\_4) are replaced by pseudo random numbers uniformly distributed in [0,127] (7 bit random numbers);
+- no GSP0 determination is made. The GSP0 codeword is selected as follows:
+  - at the beginning of a comfort noise insertion period, mean(GS[j]) is calculated as defined in subclause 5.1. Then mean(GS[j]) is quantized, using only the GS component of the GSP0 vector quantization codebook of the unvoiced speech encoding mode as quantization table. The P0 parameter is not averaged. For this parameter, the value is used which is associated with the quantized mean(GS[j]) value in the GSP0 codebook
+
+of the unvoiced speech encoding mode. For the rest of the comfort noise insertion period, the GSP0 indices are frozen.
+
+A simplified block diagram of the GSM half rate speech encoder in comfort noise insertion mode is shown in figure 1.
+
+![Figure 1: GSM half rate speech encoder in comfort noise insertion mode. The diagram shows the signal flow for generating the error signal e(n). The input signal s(n) is processed by a weighting filter W(z) with coefficients (alpha_i, alpha_tilde_i). The output of W(z) is subtracted from the sum of two scaled pseudo-noise (PN) signals. The first PN signal, generated by PN block I, is processed by VSELP Codebook 1 and then multiplied by beta. The second PN signal, generated by PN block H, is processed by VSELP Codebook 2 and then multiplied by gamma. The scaled signals are summed and then processed by a synthesis filter H(z) with coefficients (alpha_tilde_i). The output of H(z) is subtracted from the output of W(z) to produce the error signal e(n). A Long Term Filter State Update block receives the sum of the scaled PN signals and updates the filter state. A legend defines Mode = 0 (unvoiced), alpha_i as direct form LPC coeff. / unquantized, alpha_tilde_i as weighted direct form LPC coeff. / unquantized, and PN as pseudo noise generator.](367926125450c2bc3f4bdca9d59a62ba_img.jpg)
+
+Mode = 0 (unvoiced);
+
+$\alpha_i$  : direct form LPC coeff. / unquantized;
+
+$\tilde{\alpha}_i$  : weighted direct form LPC coeff. / unquantized;
+
+PN : pseudo noise generator.
+
+Figure 1: GSM half rate speech encoder in comfort noise insertion mode. The diagram shows the signal flow for generating the error signal e(n). The input signal s(n) is processed by a weighting filter W(z) with coefficients (alpha\_i, alpha\_tilde\_i). The output of W(z) is subtracted from the sum of two scaled pseudo-noise (PN) signals. The first PN signal, generated by PN block I, is processed by VSELP Codebook 1 and then multiplied by beta. The second PN signal, generated by PN block H, is processed by VSELP Codebook 2 and then multiplied by gamma. The scaled signals are summed and then processed by a synthesis filter H(z) with coefficients (alpha\_tilde\_i). The output of H(z) is subtracted from the output of W(z) to produce the error signal e(n). A Long Term Filter State Update block receives the sum of the scaled PN signals and updates the filter state. A legend defines Mode = 0 (unvoiced), alpha\_i as direct form LPC coeff. / unquantized, alpha\_tilde\_i as weighted direct form LPC coeff. / unquantized, and PN as pseudo noise generator.
+
+Figure 1: GSM half rate speech encoder in comfort noise insertion mode
+
+## 5.3 SID-frame encoding
+
+The SID frame encoding algorithm exploits the fact that only some of the 112 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID frame by means of a fixed bit pattern, called the SID codeword.
+
+SID frames are encoded in the encoder output format for voiced frames (MODE = 3), because the two voicing mode bits are part of the SID codeword.
+
+The index of the frame energy value  $R_0$  is replaced by the quantization index derived from  $\text{mean}(R_0[j])$ .  $\text{mean}(R_0[j])$  is defined in subclause 5.1 and is encoded as described in GSM 06.20 [2].
+
+The VQ indices of the reflection coefficients are replaced by VQ indices derived from  $\text{mean}(R[j](i))$ .  $\text{mean}(R[j](i))$  is defined in subclause 5.1 and the VQ of the reflection coefficients is described in GSM 06.20 [2].
+
+The SID codeword consists of 79 bits which are all "1". To mark a frame as a SID frame, the parameters in table 1 have to be set as shown.
+
+**Table 1: SID codeword**
+
+| Parameter | Number of bits | Value (Hex) |
+|-----------|----------------|-------------|
+| MODE      | 2              | 0x0003      |
+| INT LPC   | 1              | 0x0001      |
+| LAG 1     | 8              | 0x00ff      |
+| LAG 2     | 4              | 0x000f      |
+| LAG 3     | 4              | 0x000f      |
+| LAG 4     | 4              | 0x000f      |
+| CODE 1    | 9              | 0x01ff      |
+| CODE 2    | 9              | 0x01ff      |
+| CODE 3    | 9              | 0x01ff      |
+| CODE 4    | 9              | 0x01ff      |
+| GSP0 1    | 5              | 0x001f      |
+| GSP0 2    | 5              | 0x001f      |
+| GSP0 3    | 5              | 0x001f      |
+| GSP0 4    | 5              | 0x001f      |
+
+The parameters in table 1 are defined in GSM 06.20 [2].
+
+# 6 Functions on the receive (RX) side
+
+The situations in which comfort noise shall be generated on the RX side are defined in GSM 06.41 [3] and may be started or updated whenever a valid SID frame is received.
+
+## 6.1 Averaging of the GS parameters
+
+When speech frames are received by the decoder, the GS parameters of the last seven speech frames shall be kept in memory. As soon as a SID frame is received, these stored GS parameters shall be averaged. The averaged GS value will be frozen and used for the actual comfort noise insertion period.
+
+The averaging procedure works as follows:
+
+- when a speech frame is received, the GSP0 indices are decoded and the decoded GS parts of these parameters are stored in memory;
+- when the first SID frame is received, the stored GS values are averaged in the same way as in the speech encoder as follows (see also subclause 5.1):
+
+$$\begin{aligned} & 7 \quad 4 \\ \text{mean (GS[j])} &= 1/28 \text{ SUM ( SUM GS[j-n](i) );} \\ & n=1 \quad i=1; \end{aligned}$$
+
+where:
+
+GS[j](i) is the quantized energy tweak parameter in subframe i of the current frame j;
+
+GS[j-n](i) is the quantized energy tweak parameter in subframe i of one of the last frames;
+
+n is the averaging period index n=1,2,...,7;
+
+i is the subframe index i=1,2,3,4;
+
+j is the frame index;
+
+- then  $\text{mean}(\text{GS}[j])$  is quantized, using the GS component of the GSP0 vector quantization codebook for the unvoiced speech encoding mode as quantization table. The resulting index of this quantization is used for one complete comfort noise insertion period as GSP0 codeword. The P0 parameter is not averaged. For this parameter, the value is used which is associated with the quantized  $\text{mean}(\text{GS}[j])$  value in the GSP0 codebook of the unvoiced speech encoding mode.
+
+## 6.2 Comfort noise generation and updating
+
+The comfort noise generation procedure uses the GSM half rate speech decoder algorithm defined in GSM 06.20 [2].
+
+When comfort noise is to be generated, then the various encoded parameters are set as in table 2.
+
+**Table 2: Comfort noise encoded parameters**
+
+| Parameter                                                                            | Value                                                                                                                                         |
+|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
+| MODE                                                                                 | 0                                                                                                                                             |
+| R0                                                                                   | interpolation of the values received in the last two valid SID frames                                                                         |
+| LPC1<br>LPC2<br>LPC3                                                                 | interpolation of the values received in the last two valid SID frames                                                                         |
+| INT LPC                                                                              | 1                                                                                                                                             |
+| CODE1_1<br>CODE1_2<br>CODE1_3<br>CODE1_4<br>CODE2_1<br>CODE2_2<br>CODE2_3<br>CODE2_4 | pseudo random numbers uniformly distributed in [0,127] (7 bit numbers)                                                                        |
+| GSP0_1<br>GSP0_2<br>GSP0_3<br>GSP0_4                                                 | index of the averaged GS parameter (calculated at the beginning of each comfort noise insertion period and frozen for the rest of the period) |
+
+With these parameters, the speech decoder now performs the standard operations described in GSM 06.20 [2] and thereby synthesizes comfort noise.
+
+Updating of the comfort noise parameters (frame energy and LPC coefficients) occurs each time a valid SID frame is received, as described in GSM 06.41 [3].
+
+NOTE: The GSP0 codewords are not updated, they are frozen during each comfort noise insertion period.
+
+When updating the comfort noise parameters (frame energy and LPC coefficients), these parameters shall be interpolated over the SID update period to obtain smooth transitions.
+
+# --- 7 Computational details
+
+A low level description has been prepared in form of an ANSI C source code which is part of GSM 06.06 [5].
+
+# Annex A (informative): Change Request History
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#15         |           |         |                  | 4.1.1       | ETSI Publication                        |
+| SMG#20         |           |         |                  | 5.1.0       | Release 1996 version                    |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46031/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-16/46_series/46031/07b17a620c75522d53916a11e12d1bff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1f4c013261c9511b8c11ae0442055478c2e39a9f
--- /dev/null
+++ b/marked/Rel-16/46_series/46031/07b17a620c75522d53916a11e12d1bff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1dfd3961c079ce7c9c824b3c416b45306ad5881adb74fe97fbe913a3c78473dd
+size 64115
diff --git a/marked/Rel-16/46_series/46031/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46031/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1d8d1947348fc3893c041521c350e1df9e748c12
--- /dev/null
+++ b/marked/Rel-16/46_series/46031/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4a2a27131eaf95f9d780971673d6738bedde1b486a9c1f746672cdda561471d1
+size 69692
diff --git a/marked/Rel-16/46_series/46031/c9d8a18a6137ad054b841d7a614afb48_img.jpg b/marked/Rel-16/46_series/46031/c9d8a18a6137ad054b841d7a614afb48_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a0309639c1c59060266aa2b8306bee9cee89518d
--- /dev/null
+++ b/marked/Rel-16/46_series/46031/c9d8a18a6137ad054b841d7a614afb48_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:acd5f1e8600497b3380952542681f903522bd74ef141b15ba0cff73384aab628
+size 45969
diff --git a/marked/Rel-16/46_series/46031/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/46_series/46031/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4e2dd6d0d9b5c219b8e95912bb9a8c1b2d9374de
--- /dev/null
+++ b/marked/Rel-16/46_series/46031/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b6c495794b40cbf0619cdbafda72cc387be3f0d5ff2eb1db074f33c835f74ed
+size 45211
diff --git a/marked/Rel-16/46_series/46031/raw.md b/marked/Rel-16/46_series/46031/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b72b5ad5b132a987a9a9bc89a34cfa6d6741533a
--- /dev/null
+++ b/marked/Rel-16/46_series/46031/raw.md
@@ -0,0 +1,314 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                   |    |
+|---------------------------------------------------|----|
+| Foreword .....                                    | 4  |
+| 1 Scope.....                                      | 5  |
+| 2 References.....                                 | 5  |
+| 3 Definitions and abbreviations .....             | 6  |
+| 3.1 Definition of general terms .....             | 6  |
+| 3.2 Definition of terms on the receive side ..... | 6  |
+| 4 General .....                                   | 6  |
+| 4.1 General organization .....                    | 7  |
+| 4.2 Naming convention .....                       | 7  |
+| 5 Transmit side.....                              | 7  |
+| 5.1 General operation .....                       | 7  |
+| 5.1.1 Functions of the TX DTX handler.....        | 8  |
+| 5.1.2 Functions of the TX radio subsystem.....    | 9  |
+| 6 Receive side .....                              | 9  |
+| 6.1 General operation .....                       | 10 |
+| 6.1.1 Functions of the RX Radio Subsystem.....    | 10 |
+| 6.1.2 Functions of the RX DTX handler .....       | 11 |
+| Annex A (informative): Change history.....        | 12 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives a description of the general baseband operation of full rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
+
+For clarity, the description is structured according the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
+
+In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Subsystem (RSS) as described in the present document together with all their flags is mandatory, being a part of the A-bis- interface as described in GSM 08.60. In this case the various flags also serve to avoid additional delays.
+
+The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used.
+
+DTX shall be in operation in GSM MSs if commanded so by the network, see GSM 04.08.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification".
+- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [4] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception".
+- [5] GSM 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
+- [6] GSM 06.01: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Processing functions".
+- [7] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding".
+- [8] GSM 06.11: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels".
+- [9] GSM 06.12: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels".
+- [10] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD)".
+
+[11] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels".
+
+# --- 3 Definitions and abbreviations
+
+Abbreviations used in the present document are listed in GSM 01.04.
+
+## 3.1 Definition of general terms
+
+**frame:** time interval of 20 msec. corresponding to the time segmentation of the full rate speech transcoder (GSM 06.10), also used as a short term for a traffic frame.
+
+**traffic frame:** block of 260 information bits (see GSM 05.03) transmitted on the full rate speech traffic channel.
+
+**(SID) silence descriptor frame:** frame characterized by the SID code word. It conveys information on the acoustic background noise.
+
+**SID code word:** fixed bit pattern defined in GSM 06.12, for labelling a traffic frame as a SID frame.
+
+**SID field:** bit positions defined in GSM 06.12, of the SID codeword within a SID frame.
+
+**speech frame:** traffic frame that cannot be classified as a SID frame.
+
+## 3.2 Definition of terms on the receive side
+
+**bad traffic frame:** traffic frame flagged BFI=1 (Bad Frame Indication) by the Radio Subsystem.
+
+**good traffic frame:** traffic frame flagged BFI=0 by the Radio Subsystem.
+
+**good speech frame:** good traffic frame which is not an accepted SID frame.
+
+**accepted SID frame:** traffic frame in which the SID field deviates in less than 16 bit positions from the SID code word (flag SID=2 or SID=1).
+
+**valid SID frame:** good traffic frame in which the SID field deviates in less than 2 bit positions from the SID code word (flag SID=2). This frame is valid for updating of comfort noise parameters at any time.
+
+**invalid SID frame:** accepted SID frame with BFI=1, or accepted SID frame with BFI=0, in which the SID field deviates in more than 1 bit position from the SID code word (flag SID=1). This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued.
+
+**unusable frame:** bad traffic frame that is not an accepted SID frame.
+
+**lost SID frame:** unusable frame received when the RX DTX Handler is generating comfort noise and a SID frame is expected (Time Alignment Flag, TAF=1).
+
+**lost speech frame:** unusable frame received when the RX DTX Handler is passing on traffic frames directly to the speech decoder.
+
+# --- 4 General
+
+Discontinuous Transmission is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes:
+
+- to save power in the MS;
+- to reduce the overall interference level on the air.
+
+## 4.1 General organization
+
+The overall DTX mechanism described in the present document requires the following functions:
+
+- a Voice Activity Detector on the transmit side;
+
+- evaluation of the background acoustic noise on the transmit side, in order to transmit characteristic parameters to the receive side;
+- generation on the receive side of a similar noise, called comfort noise, during periods where the radio transmission is cut.
+
+The Voice Activity Detector is defined in GSM 06.32 "Voice Activity Detector", the comfort noise functions in GSM 06.12 "Comfort Noise Aspects". Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.10 "GSM Full Rate Speech Transcoding".
+
+In addition to these functions, if the parameters arriving at the receive side are detected to be seriously corrupted by errors, the speech or comfort noise must be generated from substituted data in order to avoid seriously annoying effects for the listener. This function is defined in GSM 06.11 "Substitution and Muting of Lost Frames".
+
+An overall description of the speech processing parts can be found in GSM 06.01 "Processing functions".
+
+## 4.2 Naming convention
+
+Clause 3 lists the definitions of terms relevant for the DTX functions, as used in this and the technical specifications mentioned above.
+
+# 5 Transmit side
+
+A block diagram of the transmit side DTX functions is shown in figure 1.
+
+![Block diagram of the transmit side DTX functions. The diagram shows two main components: TX DTX handler and TX radio subsystem. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detection, and Comfort Noise Computation. The Speech encoder outputs 'Information bits' (260) to the Channel encoding block in the TX radio subsystem. The Voice Activity Detection and Comfort Noise Computation blocks output an 'SP flag' (1) to the SP flag monitoring block in the TX radio subsystem.](c9d8a18a6137ad054b841d7a614afb48_img.jpg)
+
+```
+graph LR; subgraph TX_DTX_handler [TX DTX handler]; SE[Speech encoder]; VAD[Voice Activity Detection]; CNC[Comfort Noise Computation]; end; subgraph TX_radio_subsystem [TX radio subsystem]; CE[Channel encoding]; SFM[SP flag monitoring]; end; SE -- "Information bits 260" --> CE; VAD -- "SP flag 1" --> SFM; CNC -- "SP flag 1" --> SFM;
+```
+
+Block diagram of the transmit side DTX functions. The diagram shows two main components: TX DTX handler and TX radio subsystem. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detection, and Comfort Noise Computation. The Speech encoder outputs 'Information bits' (260) to the Channel encoding block in the TX radio subsystem. The Voice Activity Detection and Comfort Noise Computation blocks output an 'SP flag' (1) to the SP flag monitoring block in the TX radio subsystem.
+
+Figure 1: Block diagram of the transmit side DTX functions
+
+## 5.1 General operation
+
+The TX DTX Handler continuously passes traffic frames, individually marked by a flag SP, to the Radio Subsystem. This binary flag is redundant to the SID code word labelling. SP=1 indicates a speech frame, SP=0 a SID frame.
+
+The scheduling of the frames for transmission on the air interface is controlled by the radio subsystem alone, on the basis of the SP flag as described next.
+
+### 5.1.1 Functions of the TX DTX handler
+
+To allow an exact verification of the TX DTX handler functions, all frames before the reset of the system have to be treated as if there would have been speech frames for an infinitely long time. Therefore, the first N frames after the reset are always marked with SP=1, even if VAD=0 (hangover period, see below).
+
+The Voice Activity Detector must be operating all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD=1 or VAD=0, respectively) on a frame by frame basis (see GSM 06.32).
+
+The VAD flag controls indirectly, via the TX DTX Handler operations described below, the overall DTX operation on the transmit side.
+
+Whenever VAD=1, the speech encoder output frame shall be passed directly to the radio subsystem, marked with SP=1.
+
+At the end of a speech burst (transition VAD=1 to VAD=0), it takes N+1 consecutive frames to make a new updated SID frame available (see GSM 06.12). Normally, the first N speech encoder output frames after the end of the speech burst shall therefore be passed directly to the radio subsystem, marked with SP=1 ("hangover period"). The first new SID frame is then passed to the RSS as frame N+1 after the end of the speech burst, marked with SP=0 (see figure 2).
+
+![Figure 2: 'Normal' hangover procedure (N_elapsed > 23). The diagram illustrates the timing and signaling for a speech burst and its hangover period. It consists of four horizontal timelines: VAD, SP, N_elapsed, and Frames to RSS. The VAD timeline shows a transition from high to low at the 'end of speech burst'. The SP timeline shows a 'hangover' period of N frames following the end of the burst. The N_elapsed timeline shows frame numbers 49 to 54, then 0. The Frames to RSS timeline shows 'SPEECH' frames followed by 'SID k+1' and 'SID k+2' frames. Arrows indicate the flow of frames and the averaging periods for SID frames.](07b17a620c75522d53916a11e12d1bff_img.jpg)
+
+The diagram illustrates the 'Normal' hangover procedure. It features four horizontal timelines:
+
+- VAD:** Shows the Voice Activity Detector flag. It is high (1) during the speech burst and drops to low (0) at the 'end of speech burst'. The 'last "speech" frame' is the last frame where VAD=1, and the 'first "pause" frame' is the first frame where VAD=0.
+- SP:** Shows the speech flag. It is high (1) during the speech burst and remains high for N frames after the end of the burst (the 'hangover' period), then drops to low (0).
+- N<sub>elapsed</sub>:** Shows the number of elapsed frames since the last SID update. It is marked with values 49, 50, 51, 52, 53, 54, 0, 0. The 'e.g.' label is above the 49.
+- Frames to RSS:** Shows the sequence of frames passed to the radio subsystem. It includes 'SPEECH' frames, a 'hangover' period of N frames (also marked as 'SPEECH'), and then 'SID k+1' and 'SID k+2' frames. Arrows indicate the 'SID averaging periods' for the SID frames.
+
+A scale bar indicates that one frame corresponds to 20 ms.
+
+(N<sub>elapsed</sub> : No. of elapsed frames since last updates SID)
+
+Figure 2: 'Normal' hangover procedure (N\_elapsed > 23). The diagram illustrates the timing and signaling for a speech burst and its hangover period. It consists of four horizontal timelines: VAD, SP, N\_elapsed, and Frames to RSS. The VAD timeline shows a transition from high to low at the 'end of speech burst'. The SP timeline shows a 'hangover' period of N frames following the end of the burst. The N\_elapsed timeline shows frame numbers 49 to 54, then 0. The Frames to RSS timeline shows 'SPEECH' frames followed by 'SID k+1' and 'SID k+2' frames. Arrows indicate the flow of frames and the averaging periods for SID frames.
+
+**Figure 2: "Normal" hangover procedure (N<sub>elapsed</sub> > 23)**
+
+If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (N+1 consecutive frames marked with VAD=0). This reduces the activity on the air in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see also figure 3: Note that figure 3 shows as example the longest possible speech burst without hangover).
+
+![Figure 3: Handling of short speech bursts (N_elapsed < 24) (Example). The diagram shows three horizontal timelines: VAD, SP, and Frames to RSS. The VAD timeline shows a high state during a speech burst, with an arrow pointing to the end of the burst. The SP timeline shows a high state during the speech burst and a low state otherwise. The Frames to RSS timeline shows a sequence of frames: three frames marked with '?', followed by a SID frame marked 'SID k', then a 'Speech' burst, then four frames marked 'SID k', then another 'Speech' burst, and finally five frames marked 'SID k' and 'SID k+1'. Brackets below the timeline indicate 'SID averaging period' for the first and last groups of SID frames. Arrows point from the 'end of speech burst' in the VAD timeline to the start of the second 'Speech' burst. A bracket below the second 'Speech' burst indicates 'repeat previous SID'. A bracket below the last group of SID frames indicates 'repeat previous SID'. An arrow points to the last frame, 'SID k+1', labeled 'new (updated) SID'. A note at the bottom states '(N_elapsed : No. of elapsed frames since last updates SID)'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+(N<sub>elapsed</sub> : No. of elapsed frames since last updates SID)
+
+Figure 3: Handling of short speech bursts (N\_elapsed < 24) (Example). The diagram shows three horizontal timelines: VAD, SP, and Frames to RSS. The VAD timeline shows a high state during a speech burst, with an arrow pointing to the end of the burst. The SP timeline shows a high state during the speech burst and a low state otherwise. The Frames to RSS timeline shows a sequence of frames: three frames marked with '?', followed by a SID frame marked 'SID k', then a 'Speech' burst, then four frames marked 'SID k', then another 'Speech' burst, and finally five frames marked 'SID k' and 'SID k+1'. Brackets below the timeline indicate 'SID averaging period' for the first and last groups of SID frames. Arrows point from the 'end of speech burst' in the VAD timeline to the start of the second 'Speech' burst. A bracket below the second 'Speech' burst indicates 'repeat previous SID'. A bracket below the last group of SID frames indicates 'repeat previous SID'. An arrow points to the last frame, 'SID k+1', labeled 'new (updated) SID'. A note at the bottom states '(N\_elapsed : No. of elapsed frames since last updates SID)'.
+
+**Figure 3: Handling of short speech bursts (N<sub>elapsed</sub> < 24) (Example)**
+
+Once the first SID frame after the end of a speech burst has been computed and passed to the Radio Subsystem, the TX DTX Handler shall continuously compute and pass updated SID frames to the Radio Subsystem, marked with SP=0 as long as VAD remains VAD=0.
+
+Consequently, the speech encoder must be operating all the time.
+
+### 5.1.2 Functions of the TX radio subsystem
+
+The following traffic frames shall be scheduled for transmission:
+
+- 1) all frames marked with SP=1;
+- 2) the first one with SP = 0 after one or more frames with SP=1;
+- 3) those marked with SP=0 and aligned with the SACCH multiframe structure as described in GSM 05.08.
+
+This has the overall function, that the radio transmission is cut after the transmission of a SID frame when the speaker stops talking. During speech pauses the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the receive side (and to improve the measurement of the link quality by the radio subsystem).
+
+If a SID frame (SP=0), scheduled for transmission is stolen for signalling (FACCH) purposes, then the subsequent frame shall be scheduled for transmission instead.
+
+# 6 Receive side
+
+A block diagram of the receive side DTX functions is shown in figure 4.
+
+![Block diagram of the receive side DTX functions showing the RX radio subsystem and RX DTX handler components and their interactions.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the receive side DTX functions, showing the interaction between the RX radio subsystem and the RX DTX handler.
+
+**RX radio subsystem** (Right side):
+
+- Contains two blocks: **Error correction & detection** and **SID frame detection**.
+- Outputs to the RX DTX handler:
+  - Information bits** (260 bits) from Error correction & detection.
+  - BFI** (1 bit) from Error correction & detection.
+  - SID** (1 bit) from SID frame detection.
+  - TAF** (1 bit) from SID frame detection.
+
+**RX DTX handler** (Left side):
+
+- Contains two blocks: **Comfort Noise Computation** and **Speech decoder**.
+- Receives inputs from the RX radio subsystem:
+  - Information bits** (260 bits) to Comfort Noise Computation.
+  - BFI** (1 bit) to Comfort Noise Computation.
+  - SID** (1 bit) to Speech decoder.
+  - TAF** (1 bit) to Speech decoder.
+
+Block diagram of the receive side DTX functions showing the RX radio subsystem and RX DTX handler components and their interactions.
+
+**Figure 4: Block diagram of the receive side DTX functions**
+
+## 6.1 General operation
+
+Whatever their context (speech, SID, FACCH or none), the Radio Subsystem continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 3 flags. These are the BFI, the SID and the TAF flags described below, which serve to classify the traffic frame according to the list of terms defined in clause 3. This classification, summarized in table 1 below, in turn allows the RX DTX Handler to determine in a simple way how the received frame is to be handled.
+
+**Table 1: Classification of traffic frames**
+
+| BFI | SID               |   |                   |
+|-----|-------------------|---|-------------------|
+|     | 2                 | 1 | 0                 |
+| 0   | Valid SID frame   |   | Good speech frame |
+| 1   | Invalid SID frame |   | Unusable frame    |
+
+### 6.1.1 Functions of the RX Radio Subsystem
+
+The binary BFI flag (Bad Frame Indication, see also GSM 05.05) indicates whether the traffic frame is considered to contain meaningful information bits (BFI=0) or not (BFI=1). In the context of this technical specification, a FACCH frame is considered not to contain meaningful bits and must also be marked with BFI=1. The BFI flag must fulfil the performance requirements of GSM 05.05.
+
+The ternary SID flag is the output of a SID frame detector, which compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.12. The flag is coded as follows, where n designates the number of bit deviation:
+
+- SID=2 when  $n < 2$ ;
+- SID=1 when  $2 \leq n < 16$ ;
+- SID=0 when  $n \geq 16$ .
+
+The binary TAF flag (Time Alignment Flag) marks with TAF=1 those traffic frames that are aligned with the SACCH multiframe structure as described in the technical specifications referenced in subclause 5.1.2.
+
+### 6.1.2 Functions of the RX DTX handler
+
+The RX DTX Handler is responsible for the overall DTX operation on the receive side, which shall be as follows:
+
+- whenever a good speech frame is detected, the DTX Handler shall pass it directly on to the speech decoder;
+- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.11 shall be applied;
+- valid SID frames shall result in comfort noise generation, as defined in GSM 06.12, until the next SID frame is expected (TAF=1) or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the Radio Subsystem;
+- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied.
+
+NOTE: If the first SID frame after a speech burst (a series of good speech frames) is invalid, then the comfort noise parameters can be taken from the last valid SID frame or from the last received good speech frame which, because of the VAD hangover time (see GSM 06.32), may be supposed to contain noise only.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#07         |           |         |                  | 4.0.5       | ETSI Publication                        |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                    |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46032/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46032/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..929e5df7f9a22ef9c603e06ba50bdd14eb259339
--- /dev/null
+++ b/marked/Rel-16/46_series/46032/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ba4dd3d570291f2f5edc82d72e66e97f7ca507d2a65159bbceae436b7f7dd1ea
+size 100042
diff --git a/marked/Rel-16/46_series/46032/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/46_series/46032/90ddb84c323b956e2d50a54d3f870566_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..646a0d7334bb03ecc80d4d72a8519e5b8c15aead
--- /dev/null
+++ b/marked/Rel-16/46_series/46032/90ddb84c323b956e2d50a54d3f870566_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c20a03835f2bb07c0a6ccfaa9eddce9b28c2a3179311538fb70e4cdf05bb249a
+size 39783
diff --git a/marked/Rel-16/46_series/46032/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/46_series/46032/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e1ac298872db445cd63eba32f40e2382b5b8cc86
--- /dev/null
+++ b/marked/Rel-16/46_series/46032/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:32915e00310a1738ceee3c9206f3a7cf88265d3f73e762ab27f515b4bcc1e656
+size 74164
diff --git a/marked/Rel-16/46_series/46032/raw.md b/marked/Rel-16/46_series/46032/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a15fd02a54eb3748bd1f52ece98e0d3c076d5a8
--- /dev/null
+++ b/marked/Rel-16/46_series/46032/raw.md
@@ -0,0 +1,1677 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                |           |
+|----------------------------------------------------------------|-----------|
+| Foreword .....                                                 | 5         |
+| 1 Scope .....                                                  | 6         |
+| 2 References .....                                             | 6         |
+| 3 Abbreviations .....                                          | 6         |
+| 4 General .....                                                | 6         |
+| 5 Functional description .....                                 | 7         |
+| 5.1 Overview and principles of operation .....                 | 7         |
+| 5.2 Algorithm description .....                                | 7         |
+| 5.2.1 Adaptive filtering and energy computation .....          | 9         |
+| 5.2.2 <i>ACF</i> averaging .....                               | 9         |
+| 5.2.3 Predictor values computation .....                       | 9         |
+| 5.2.4 Spectral comparison .....                                | 10        |
+| 5.2.5 Periodicity detection .....                              | 10        |
+| 5.2.6 Information tone detection .....                         | 11        |
+| 5.2.7 Threshold adaptation .....                               | 12        |
+| 5.2.8 VAD decision .....                                       | 15        |
+| 5.2.9 VAD hangover addition .....                              | 15        |
+| 6 Computational details .....                                  | 15        |
+| 6.1 Adaptive filtering and energy computation .....            | 17        |
+| 6.2 ACF averaging .....                                        | 18        |
+| 6.3 Predictor values computation .....                         | 18        |
+| 6.3.1 Schur recursion to compute reflection coefficients ..... | 19        |
+| 6.3.2 Step-up procedure to obtain the aav1[0..8] .....         | 19        |
+| 6.3.3 Computation of the rav1[0..8] .....                      | 20        |
+| 6.4 Spectral comparison .....                                  | 20        |
+| 6.5 Periodicity detection .....                                | 21        |
+| 6.6 Threshold adaptation .....                                 | 21        |
+| 6.7 VAD decision .....                                         | 23        |
+| 6.8 VAD hangover addition .....                                | 23        |
+| 6.9 Periodicity updating .....                                 | 24        |
+| 6.10 Tone detection .....                                      | 24        |
+| 6.10.1 Windowing .....                                         | 24        |
+| 6.10.2 Auto-correlation .....                                  | 24        |
+| 6.10.3 Computation of the reflection coefficients .....        | 25        |
+| 6.10.4 Filter coefficient calculation .....                    | 26        |
+| 6.10.5 Pole Frequency Test .....                               | 26        |
+| 6.10.6 Prediction gain test .....                              | 26        |
+| 7 Digital test sequences .....                                 | 27        |
+| 7.1 Test configuration .....                                   | 27        |
+| 7.2 Test sequences .....                                       | 28        |
+| <b>Annex A (informative):</b>                                  | <b>29</b> |
+| A.1 Simplified block filtering operation .....                 | 29        |
+| A.2 Description of digital test sequences .....                | 29        |
+| A.2.1 Test sequences .....                                     | 29        |
+| A.2.2 File format description .....                            | 31        |
+| A.3 VAD performance .....                                      | 33        |
+| A.4 Pole frequency calculation .....                           | 34        |
+| <b>Annex B (normative): Test sequences .....</b>               | <b>35</b> |
+| Annex C (informative): Change history .....                    | 36        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) for the digital cellular telecommunications system.
+
+Archive en\_300965v080000p0.zip which accompanies the present document, contains test sequences, as described in clause A.2.
+
+en\_300965v080000p0.zip Annex B: Test sequences for the GSM Full Rate speech codec; Test sequences files \*.inp, \*.cod, \*.vad.
+
+The specification from which the present document has been derived was originally based on CEPT documentation, hence the presentation of the present document may not be entirely in accordance with the ETSI/PNE Rules.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# 1 Scope
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.31. It also specifies the test methods to be used to verify that a VAD complies with the technical specification.
+
+The requirements are mandatory on any VAD to be used either in the GSM Mobile Stations (MS)s or Base Station Systems (BSS)s.
+
+# 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.10: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Transcoding".
+- [3] GSM 06.12: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels".
+- [4] GSM 06.31: "Digital cellular telecommunications system(Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels".
+
+# --- 3 Abbreviations
+
+Abbreviations used in the present document are listed in GSM 01.04 [1].
+
+# --- 4 General
+
+The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a binary flag which is used by the TX DTX handler defined in GSM 06.31 [4].
+
+The ETS is organized as follows.
+
+Clause 2 describes the principles of operation of the VAD.
+
+In clause 3, the computational details necessary for the fixed point implementation of the VAD algorithm are given. This clause uses the same notation as used for computational details in GSM 06.10.
+
+The verification of the VAD is based on the use of digital test sequences. Clause 4 defines the input and output signals and the test configuration, whereas the detailed description of the test sequences is contained in clause A.2.
+
+The performance of the VAD algorithm is characterized by the amount of audible speech clipping it introduces and the percentage activity it indicates. These characteristics for the VAD defined in the present document have been established by extensive testing under a wide range of operating conditions. The results are summarized in clause A.3.
+
+# --- 5 Functional description
+
+The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas the detailed description is given in clause 3. In case of discrepancy between the two descriptions, the detailed description of clause 3 shall prevail.
+
+In the following subclauses of clause 2, a Pascal programming type of notation has been used to describe the algorithm.
+
+## 5.1 Overview and principles of operation
+
+The function of the VAD is to distinguish between noise with speech present and noise without speech present. The biggest difficulty for detecting speech in a mobile environment is the very low speech/noise ratios which are often encountered. The accuracy of the VAD is improved by using filtering to increase the speech/noise ratio before the decision is made.
+
+For a mobile environment, the worst speech/noise ratios are encountered in moving vehicles. It has been found that the noise is relatively stationary for quite long periods in a mobile environment. It is therefore possible to use an adaptive filter with coefficients obtained during noise, to remove much of the vehicle noise.
+
+The VAD is basically an energy detector. The energy of the filtered signal is compared with a threshold; speech is indicated whenever the threshold is exceeded.
+
+The noise encountered in mobile environments may be constantly changing in level. The spectrum of the noise can also change, and varies greatly over different vehicles. Because of these changes the VAD threshold and adaptive filter coefficients must be constantly adapted. To give reliable detection the threshold must be sufficiently above the noise level to avoid noise being identified as speech but not so far above it that low level parts of speech are identified as noise. The threshold and the adaptive filter coefficients are only updated when speech is not present. It is, of course, potentially dangerous for a VAD to update these values on the basis of its own decision. This adaptation therefore only occurs when the signal seems stationary in the frequency domain but does not have the pitch component inherent in voiced speech. A tone detector is also used to prevent adaptation during information tones.
+
+A further mechanism is used to ensure that low level noise (which is often not stationary over long periods) is not detected as speech. Here, an additional fixed threshold is used.
+
+A VAD hangover period is used to eliminate mid-burst clipping of low level speech. Hangover is only added to speech-bursts which exceed a certain duration to avoid extending noise spikes.
+
+## 5.2 Algorithm description
+
+The block diagram of the VAD algorithm is shown in figure 2.1. The individual blocks are described in the following subclauses. ACF, N and sof are calculated in the speech encoder.
+
+![Functional block diagram of the VAD (Voice Activity Detection) system. The diagram shows the flow of data from input ACF, N, and sof through various processing blocks to produce the final vad output. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Global variables shown are r_vad, p_vad, ptch, tone, r_av1, av1, av0, th_vad, stat, v_vad, and vad.](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+```
+
+graph LR
+    ACF[ACF] --> AFE[Adaptive filtering and energy computation]
+    N[N] --> PD[Periodicity detection]
+    sof[sof] --> TD[Tone detection]
+    ACF --> AA[ACF averaging]
+    ACF --> PVE[Predictor values computation]
+    
+    PD -- ptch --> TA[Threshold adaptation]
+    TD -- tone --> TA
+    AA -- av0 --> SC[Spectral comparison]
+    AA -- av1 --> PVE
+    PVE -- r_av1 --> SC
+    PVE -- r_vad --> AFE
+    PVE -- th_vad --> VD[VAD decision]
+    
+    AFE -- p_vad --> VD
+    VD -- v_vad --> VHA[VAD hangover addition]
+    VHA -- vad --> Output[vad]
+  
+```
+
+Functional block diagram of the VAD (Voice Activity Detection) system. The diagram shows the flow of data from input ACF, N, and sof through various processing blocks to produce the final vad output. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Global variables shown are r\_vad, p\_vad, ptch, tone, r\_av1, av1, av0, th\_vad, stat, v\_vad, and vad.
+
+**Figure 2.1: Functional block diagram of the VAD**
+
+The global variables shown in the block diagram are described as follows:
+
+- ACF are auto-correlation coefficients which are calculated in the speech encoder defined in GSM 06.10 (subclause 3.1.4, see also clause A.1). The inputs to the speech encoder are 16 bit 2's complement numbers, as described in GSM 06.10, subclause 4.2.0;
+- av0 and av1 are averaged ACF vectors;
+- r\_av1 are autocorrelated predictor values obtained from av1;
+- r\_vad are the autocorrelated predictor values of the adaptive filter;
+- N is the long term predictor lag value which is obtained every sub-segment in the speech coder defined in GSM 06.10;
+- ptch indicates whether the signal has a steady periodic component;
+- sof is the offset compensated signal frame obtained in the speech coder defined in GSM 06.10;
+- p\_vad is the energy in the current frame of the input signal after filtering;
+- th\_vad is an adaptive threshold;
+- stat indicates spectral stationarity;
+- v\_vad indicates the VAD decision before hangover is added;
+- vad is the final VAD decision with hangover included.
+
+### 5.2.1 Adaptive filtering and energy computation
+
+Pvad is computed as follows:
+
+$$Pvad = rvad_0 acf_0 + 2 \sum_{i=1}^8 rvad_i acf_i$$
+
+This corresponds to performing an 8th order block filtering on the input samples to the speech encoder, after zero offset compensation and pre-emphasis. This is explained in clause A.1.
+
+### 5.2.2 ACF averaging
+
+Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the auto-correlation values for several consecutive frames. This averaging is given by the following equations:
+
+$$av0\{n\}_i = \sum_{j=0}^{frames-1} acf\{n - j\}_i; i = 0..8$$
+
+$$av1\{n\}_i = av0\{n - frames\}_i; i = 0..8$$
+
+Where n represents the current frame,  $n-1$  represents the previous frame etc. The values of constants are given in table 2.1.
+
+**Table 2.1: Constants and variables for ACF averaging**
+
+| Constant | Value | Variable                    | Initial value |
+|----------|-------|-----------------------------|---------------|
+| frames   | 4     | previous ACF's<br>av0 & av1 | All set to 0  |
+
+### 5.2.3 Predictor values computation
+
+The filter predictor values aav1 are obtained from the auto-correlation values av1 according to the equation:
+
+$$\underline{a} = \underline{R}^{-1} \underline{p}$$
+
+where:
+
+$$\underline{R} = \begin{bmatrix} av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5], & av1[6], & av1[7] \\ av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5], & av1[6] \\ av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4], & av1[5] \\ av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3], & av1[4] \\ av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2], & av1[3] \\ av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1], & av1[2] \\ av1[6], & av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0], & av1[1] \\ av1[7], & av1[6], & av1[5], & av1[4], & av1[3], & av1[2], & av1[1], & av1[0] \end{bmatrix}$$
+
+and:
+
+$$\mathbf{p} = \begin{bmatrix} |av1[1]| \\ |av1[2]| \\ |av1[3]| \\ |av1[4]| \\ |av1[5]| \\ |av1[6]| \\ |av1[7]| \\ |av1[8]| \end{bmatrix} \quad \mathbf{a} = \begin{bmatrix} |aav1[1]| \\ |aav1[2]| \\ |aav1[3]| \\ |aav1[4]| \\ |aav1[5]| \\ |aav1[6]| \\ |aav1[7]| \\ |aav1[8]| \end{bmatrix}$$
+
+$$aav1[0] = -1$$
+
+av1 is used in preference to av0 as av0 may contain speech.
+
+The autocorrelated predictor values rav1 are then obtained:
+
+$$rav1_i = \sum_{k=0}^{8-i} aav1_k aav1_{k+i}; i = 0..8$$
+
+### 5.2.4 Spectral comparison
+
+The spectra represented by the autocorrelated predictor values rav1 and the averaged auto-correlation values av0 are compared using the distortion measure dm defined below. This measure is used to produce a Boolean value stat every 20 ms, as given by these equations:
+
+$$dm = \frac{(rav1_0 av0_0 + 2 \sum_{i=1}^8 rav1_i av0_i)}{av0_0}$$
+
+$$difference = |dm - lastdm|$$
+
+$$lastdm = dm$$
+
+$$stat = difference < thresh$$
+
+The values of constants and initial values are given in table 2.2.
+
+**Table 2.2: Constants and variables for spectral comparison**
+
+| Constant | Value | Variable | Initial value |
+|----------|-------|----------|---------------|
+| thresh   | 0.05  | lastdm   | 0             |
+
+### 5.2.5 Periodicity detection
+
+The frequency spectrum of mobile noise is relatively stationary over quite long periods. The Inverse Filter Autocorrelated Predictor coefficients of the adaptive filter rvad are only updated when this stationarity is detected. Vowel sounds however, also have this stationarity, but can be excluded by detecting the periodicity of these sounds using the long term predictor lag values (Nj) which are obtained every sub-segment from the speech codec defined in GSM 06.10. Consecutive lag values are compared. Cases in which one lag value is a factor of the other are catered for, however cases in which both lag values have a common factor, are not. This case is not important for speech input but this method of periodicity detection may fail for some sine waves. The Boolean variable ptch is updated every 20 ms and is true when periodicity is detected. It is calculated according to the following equation:
+
+$$ptch = oldlagcount + veryoldlagcount \geq nthresh$$
+
+The following operations are done after the VAD decision and when the current LTP lag values (N0 .. N3) are available, this reduces the delay of the VAD decision. ( $N\{-1\} = N3$  of previous segment.)
+
+```
+lagcount = 0
+for j = 0 to 3 do
+begin
+```
+
+```
+
+smalllag = maximum(Nj,N{j-1}) mod minimum(Nj,N{j-1})
+if minimum(smalllag,minimum(Nj,N{j-1})-smalllag) < lthresh
+    then increment(lagcount)
+end
+
+veryoldlagcount = oldlagcount
+
+oldlagcount = lagcount
+
+```
+
+The values of constants and initial values are given in table 2..
+
+**Table 2.3: Constants and variables for periodicity detection**
+
+| Constant | Value | Variable        | Initial value |
+|----------|-------|-----------------|---------------|
+| lthresh  | 2     | oldlagcount     | 0             |
+| nthresh  | 4     | veryoldlagcount | 0             |
+|          |       | N3              | 40            |
+
+### 5.2.6 Information tone detection
+
+The tone flag is only evaluated in the downlink VAD. In the uplink VAD, tone detection is not performed and tone = false.
+
+Computation of the tone flag is complex. It is therefore evaluated after the processing of the current speech encoder frame. In this way transmission of the speech or SID frame is not delayed.
+
+Information tones and environmental noise can be classified by inspecting the short term prediction gain, information tones resulting in higher prediction gains than environmental noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for environmental noise.
+
+The prediction gain decision is implemented by comparing the normalized prediction error with a threshold. This measure is used to evaluate the Boolean variable tone every 20 ms. The signal is classified as a tone if the prediction error is smaller than the threshold predth. This is equivalent to a prediction gain threshold of 13,5 dB.
+
+Mobile noise can contain very strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz. The pole frequency calculation is described in clause A.4.
+
+The algorithm for detecting information tones is as follows:
+
+```
+
+tone = false
+
+den = a[1]*a[1]
+num = 4*a[2] - a[1]*a[1]
+
+if ( num <= 0 )
+    return
+
+if ( ( a[1] < 0 ) AND ( num / den < freqth ) )
+    return
+
+          4
+prederr = MULT ( 1 - RC[i]*RC[i] )
+         i=1
+
+if (prederr < predth)
+    tone = true
+
+return
+
+```
+
+The values of the constants are given in table 2.4. The coefficients a[1..2] are transversal filter coefficients calculated from rc[1..2]. The calculation of the reflection coefficients rc[1..4] is described below.
+
+The offset compensated signal frame sof[0..159] is multiplied by the Hanning window to give the windowed frame sofh[0..159]:
+
+$$sofh_i = sof_i \cdot hann_i \quad i = 0..159$$
+
+where
+
+$$\text{hann}_i = 0.5 \left( 1 - \cos \left( 2\pi \left( \frac{i}{159} \right) \right) \right) \quad i = 0..159$$
+
+The auto-correlation  $\text{acfh}[0..4]$  of the windowed signal frame is then calculated:
+
+$$\text{acfh}_k = \sum_{i=k}^{159} \text{sofh}_i \text{sofh}_{i-k}; \quad k = 0..4$$
+
+$\text{rc}[1..4]$  are then calculated from  $\text{acfh}[0..4]$  using the Schur recursion described in the RPE-LTP codec.
+
+**Table 2.4: Constants for information tone detection**
+
+| Constant | Value  |
+|----------|--------|
+| freqth   | 0,0973 |
+| predth   | 0,0158 |
+
+NOTE: Reflection coefficients are available in the RPE-LTP codec. However, they are calculated after pre-emphasis using a rectangular window and do not give good tone detection results.
+
+### 5.2.7 Threshold adaptation
+
+A check is made every 20 ms to determine whether the VAD decision threshold (thvad) should be changed. This adaptation is carried out according to the flowchart shown in figure 2.2. The constants used are given in table 2.5.
+
+Adaptation takes place in two different situations: firstly whenever  $\text{ACF}[0]$  is very low and secondly whenever there is a very high probability that speech and information tones are not present.
+
+In the first case, the threshold is adapted if the energy of the input signal is less than  $\text{pth}$ . The threshold is set to  $\text{plev}$  without carrying out any further tests because at these very low levels the effect of the signal quantization makes it impossible to obtain reliable results from these tests.
+
+In the second case, the decision threshold (thvad) and the adaptive filter coefficients (rvad) are only updated with the  $\text{ravl}$  values when there is a very high probability that speech and information tones are not present. Adaptation occurs if the following conditions are met over a number ( $\text{adp}$ ) of signal frames:
+
+- stationarity is detected in the frequency domain;
+- the signal does not contain a periodic component;
+- information tones are not present.
+
+The step-size by which the threshold is adapted is not constant but a proportion of the current value (determined by constants  $\text{dec}$  and  $\text{inc}$ ). The adaptation begins by experimentally multiplying the threshold by a factor of  $(1-1/\text{dec})$ . If the new threshold is now higher than or equal to  $\text{Pvad}$  times  $\text{fac}$  then the threshold needed to be decreased and it is left at this new lower level. If, on the other hand, the new threshold level is less than  $\text{Pvad}$  times  $\text{fac}$  then the threshold either needed to be increased or kept constant. In this case it is set to  $\text{Pvad}$  times  $\text{fac}$  unless this would mean multiplying it by more than a factor of  $(1+1/\text{inc})$  (in which case it is multiplied by a factor of  $(1+1/\text{inc})$ ). The threshold is never allowed to be greater than  $\text{Pvad}+\text{margin}$ .
+
+**Table 2.5: Constants and variables for threshold adaptation**
+
+| Constant        | Value      | Variable            | Initial value |
+|-----------------|------------|---------------------|---------------|
+| $\text{pth}$    | 300 000    | $\text{adaptcount}$ | 0             |
+| $\text{plev}$   | 800 000    | $\text{thvad}$      | 1 000 000     |
+| $\text{fac}$    | 3.0        | $\text{rvad}[0]$    | 6             |
+| $\text{adp}$    | 8          | $\text{rvad}[1]$    | -4            |
+| $\text{inc}$    | 16         | $\text{rvad}[2]$    | 1             |
+| $\text{dec}$    | 32         | $\text{rvad}[3]$ to |               |
+| $\text{margin}$ | 80 000 000 | $\text{rvad}[8]$    | All 0         |
+
+![Flow diagram for threshold adaptation](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph TD; BEGIN --> ACF{ACF[0] < pth ?}; ACF -- yes --> th_vad_init[th_vad = plev]; ACF -- no --> stat{stat and not ptch and not tone ?}; stat -- yes --> increment[increment adaptcount]; stat -- no --> adaptcount_reset[adaptcount = 0]; increment --> adaptcount_gt{adaptcount > adp ?}; adaptcount_reset --> adaptcount_gt; adaptcount_gt -- yes --> th_vad_dec[th_vad = th_vad - th_vad / dec]; adaptcount_gt -- no --> END; th_vad_init --> END; th_vad_dec --> th_vad_min{th_vad < p_vad * fac ?}; th_vad_min -- yes --> th_vad_min_calc[th_vad = min(th_vad + th_vad / inc, p_vad * fac)]; th_vad_min -- no --> th_vad_max{th_vad > p_vad + margin ?}; th_vad_min_calc --> th_vad_max; th_vad_max -- yes --> th_vad_add[th_vad = p_vad + margin]; th_vad_max -- no --> r_vad[r_vad = r_av1]; th_vad_add --> adaptcount_inc[adaptcount = adp + 1]; r_vad --> adaptcount_inc; adaptcount_inc --> END;
+```
+
+The flow diagram for threshold adaptation starts with **BEGIN** and proceeds to a decision diamond **ACF[0] < pth ?**. If **yes**, it goes to **th<sub>vad</sub> = plev** and then to **END**. If **no**, it goes to a decision diamond **stat and not ptch and not tone ?**. If **yes**, it goes to **increment adaptcount**. If **no**, it goes to **adaptcount = 0**. Both **increment adaptcount** and **adaptcount = 0** lead to a decision diamond **adaptcount > adp ?**. If **yes**, it goes to **th<sub>vad</sub> = th<sub>vad</sub> - th<sub>vad</sub> / dec**. If **no**, it goes to **END**. **th<sub>vad</sub> = th<sub>vad</sub> - th<sub>vad</sub> / dec** leads to a decision diamond **th<sub>vad</sub> < p<sub>vad</sub> \* fac ?**. If **yes**, it goes to **th<sub>vad</sub> = min(th<sub>vad</sub> + th<sub>vad</sub> / inc, p<sub>vad</sub> \* fac)**. If **no**, it goes to a decision diamond **th<sub>vad</sub> > p<sub>vad</sub> + margin ?**. **th<sub>vad</sub> = min(th<sub>vad</sub> + th<sub>vad</sub> / inc, p<sub>vad</sub> \* fac)** also leads to this decision diamond. If **yes**, it goes to **th<sub>vad</sub> = p<sub>vad</sub> + margin**. If **no**, it goes to **r<sub>vad</sub> = r<sub>av1</sub>**. Both **th<sub>vad</sub> = p<sub>vad</sub> + margin** and **r<sub>vad</sub> = r<sub>av1</sub>** lead to **adaptcount = adp + 1**, which then leads to **END**.
+
+Flow diagram for threshold adaptation
+
+Figure 2.2: Flow diagram for threshold adaptation
+
+### 5.2.8 VAD decision
+
+Prior to hangover the VAD decision condition is:
+
+```
+vvad = pvad > thvad
+```
+
+### 5.2.9 VAD hangover addition
+
+VAD hangover is only added to bursts of speech greater than or equal to burstconst blocks. The Boolean variable vad indicates the decision of the VAD with hangover included. The values of the constants are given in table 2.6. The hangover algorithm is as follows:
+
+```
+if vvad then increment(burstcount) else burstcount = 0
+
+if burstcount >= burstconst then
+begin
+  hangcount = hangconst;
+  burstcount = burstconst
+end
+
+vad = vvad or (hangcount >= 0)
+
+if hangcount >= 0 then decrement(hangcount)
+```
+
+**Table 2.6: Constants and variables for VAD hangover addition**
+
+| Constant   | Value | Variable   | Initial value |
+|------------|-------|------------|---------------|
+| burstconst | 3     | burstcount | 0             |
+| hangconst  | 5     | hangcount  | -1            |
+
+# --- 6 Computational details
+
+In the next paragraphs, the detailed description of the VAD algorithm follows the preceding high level description. This detailed description is divided in ten clauses related to the blocks of figure 2.1 (except periodicity updating) in the high level description of the VAD algorithm.
+
+Those clauses are:
+
+- 1) adaptive filtering and energy computation;
+- 2) ACF averaging;
+- 3) predictor values computation;
+- 4) spectral comparison;
+- 5) periodicity detection;
+- 6) threshold adaptation;
+- 7) VAD decision;
+- 8) VAD hangover addition;
+- 9) periodicity updating;
+- 10) information tone detection.
+
+The VAD algorithm takes as input the following variables of the RPE-LTP encoder (see the detailed description of the RPE-LTP encoder GSM 06.10):
+
+- L\_ACF[0..8], auto-correlation function (GSM 06.10/4.2.4);
+- scalauto, scaling factor to compute the L\_ACF[0..8] (GSM 06.10/4.2.4);
+
+- Nc, LTP lag (one for each sub-segment, GSM 06.10/4.2.11);
+- sof, offset compensated signal frame (GSM 06.10/4.2.2).
+
+So four Nc values are needed for the VAD algorithm.
+
+The VAD computation can start as soon as the L\_ACF[0..8] and scalauto variables are known. This means that the VAD computation can take place after part 4.2.4 of GSM 06.10 (Auto-correlation) of the LPC analysis clause of the RPE-LTP encoder. This scheme will reduce the delay to yield the VAD information. The periodicity updating (included in subclause 2.2.5) and information tone detection, are done after the processing of the current speech encoder frame.
+
+All the arithmetic operations and names of the variables follow the RPE-LTP detailed description. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This stands for the following variables (and related constants) of the VAD algorithm:
+
+pvad: Energy of filtered signal;
+
+thvad: Threshold of the VAD decision;
+
+acf0: Energy of input signal.
+
+For the representation of these variables, two integers (16 bits) are needed:
+
+- one for the exponent (e\_pvad, e\_thvad, e\_acf0);
+- one for the mantissa (m\_pvad, m\_thvad, m\_acf0).
+
+The value e\_pvad represents the lowest power of 2 just greater or equal to the actual value of pvad and the m\_pvad value represents a integer which is always greater or equal to 16384 (normalized mantissa). It means that the pvad value is equal to:
+
+$$\text{pvad} = 2^{e\_pvad} * (m\_pvad / 32768)$$
+
+This scheme guarantees a large dynamic range for the pvad value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables and the VAD algorithm needs only one pseudo-floating point addition. All the computations related to the pseudo-floating point variables require very simple 16 or 32 bits arithmetic operations defined in the detailed description of the RPE-LTP encoder. This pseudo-floating point arithmetic is only used in subclauses 3.1 and 3.6.
+
+Table 3.1 gives a list of all the variables of the VAD algorithm that must be initialized in the reset procedure and kept in memory for processing the subsequent frame of the RPE- LTP encoder. The types (16 or 32 bits) and initial values of all these variables are clearly indicated and their related subclause is also mentioned. The bit exact implementation uses other temporary variables that are introduced in the detailed description whenever it is needed.
+
+**Table 3.1: Initial values for variables to be stored in memory**
+
+| <b>Names of variables:</b>                                                         | <b>type (# of bits):</b> | <b>Initialization:</b>              | <b>Subclause:</b>                                |
+|------------------------------------------------------------------------------------|--------------------------|-------------------------------------|--------------------------------------------------|
+| Adaptive filter coefficients:<br>rvad[0]<br>rvad[1]<br>rvad[2]<br>rvad[3..8]       | <br>16<br>16<br>16<br>16 | <br>24 576<br>-16 384<br>4 096<br>0 | <br>3.1, 3.6<br>3.1, 3.6<br>3.1, 3.6<br>3.1, 3.6 |
+| Scaling factor of rvad[0..8]:<br>normrvad                                          | <br>16                   | <br>7                               | <br>3.1, 3.6                                     |
+| Delay line of the auto-correlation coefficients:<br>L_sacf[0..26]<br>L_sav0[0..35] | <br>32<br>32             | <br>0<br>0                          | <br>3.2<br>3.2                                   |
+| Pointers on the delay lines:<br>pt_sacf<br>pt_sav0                                 | <br>16<br>16             | <br>0<br>0                          | <br>3.2<br>3.2                                   |
+| Distance measure:<br>L_lastdm                                                      | <br>32                   | <br>0                               | <br>3.4                                          |
+| Periodicity counters:<br>oldlagcount<br>veryoldlagcount                            | <br>16<br>16             | <br>0<br>0                          | <br>3.5, 3.9<br>3.5, 3.9                         |
+| Adaptive threshold:<br>e_thvad (exponent)<br>m_thvad (mantissa)                    | <br>16<br>16             | <br>20<br>31 250                    | <br>3.6<br>3.6                                   |
+| Counter for adaptation:<br>adaptcount                                              | <br>16                   | <br>0                               | <br>3.6                                          |
+| Hangover flags:<br>burstcount<br>hangcount                                         | <br>16<br>16             | <br>0<br>-1                         | <br>3.8<br>3.8                                   |
+| LTP lag memory:<br>oldlag                                                          | <br>16                   | <br>40                              | <br>3.9                                          |
+| Tone Detection<br>tone                                                             | <br>16                   | <br>0                               | <br>3.10                                         |
+
+## 6.1 Adaptive filtering and energy computation
+
+This subclause computes the e\_pvad and m\_pvad variables which represent the pvad value. It needs the L\_ACF[0..8] and scalauto variables of the RPE-LTP algorithm and the rvad[0..8] and normrvad variables produced by subclause 3.6 of the VAD algorithm. It also computes a floating point representation of L\_ACF[0] (e\_acf0 and m\_acf0) used in subclause 3.6.
+
+### Test if L\_ACF[0] is equal to 0:
+
+```
+IF ( scalauto < 0 ) THEN scalvad = 0;
+ELSE scalvad = scalauto; / keep scalvad for use in subclause 3.2 /
+
+IF ( L_ACF[0] == 0 ) THEN
+    | e_pvad = -32768;
+    | m_pvad = 0;
+    | e_acf0 = -32768;
+    | m_acf0 = 0;
+    | EXIT /continue with subclause 3.2/
+```
+
+### Re-normalization of the L\_ACF[0..8]:
+
+```
+normacf = norm( L_ACF[0] );
+
+| FOR i = 0 to 8:
+|   sacf[i] = ( L_ACF[i] << normacf ) >> 19;
+| NEXT i:
+```
+
+### Computation of e\_acf0 and m\_acf0:
+
+```
+e_acf0 = add( 32, (scalvad << 1 ) );
+e_acf0 = sub( e_acf0, normacf);
+m_acf0 = sacf[0] << 3;
+```
+
+### Computation of e\_pvad and m\_pvad:
+
+```
+e_pvad = add( e_acf0, 14 );
+e_pvad = sub( e_pvad, normrvad );
+
+L_temp = 0;
+
+| FOR i = 1 to 8:
+|   L_temp = L_add( L_temp, L_mult( sacf[i], rvad[i] ) );
+| NEXT i:
+
+L_temp = L_add( L_temp, L_mult( sacf[0], rvad[0] ) >> 1 );
+
+IF ( L_temp <= 0 ) THEN L_temp = 1;
+
+normprod = norm( L_temp );
+e_pvad = sub( e_pvad, normprod );
+m_pvad = ( L_temp << normprod ) >> 16;
+```
+
+## 6.2 ACF averaging
+
+This subclause uses the L\_ACF[0..8] and the scalvad variables to compute the array L\_av0[0..8] and L\_av1[0..8] used in subclause 3.3 and 3.4.
+
+### Computation of the scaling factor:
+
+```
+scal = sub( 10, (scalvad << 1) );
+```
+
+### Computation of the arrays L\_av0[0..8] and L\_av1[0..8]:
+
+```
+| FOR i = 0 to 8:
+|   L_temp = L_ACF[i] >> scal;
+|   L_av0[i] = L_add( L_sacf[i], L_temp );
+|   L_av0[i] = L_add( L_sacf[i+9], L_av0[i] );
+|   L_av0[i] = L_add( L_sacf[i+18], L_av0[i] );
+|   L_sacf[ pt_sacf + i ] = L_temp;
+|   L_av1[i] = L_sav0[ pt_sav0 + i ];
+|   L_sav0[ pt_sav0 + i ] = L_av0[i];
+| NEXT i:
+```
+
+### Update of the array pointers:
+
+```
+IF ( pt_sacf == 18 ) THEN pt_sacf = 0;
+ELSE pt_sacf = add( pt_sacf, 9);
+
+IF ( pt_sav0 == 27 ) THEN pt_sav0 = 0;
+ELSE pt_sav0 = add( pt_sav0, 9);
+```
+
+## 6.3 Predictor values computation
+
+This subclause computes the array rav1[0..8] needed for the spectral comparison and the threshold adaptation. It uses the L\_av1[0..8] computed in subclause 3.2, and is divided in the three following subclauses:
+
+- Schur recursion to compute reflection coefficients.
+- Step up procedure to obtain the aav1[0..8].
+- Computation of the rav1[0..8].
+
+### 6.3.1 Schur recursion to compute reflection coefficients
+
+This subclause is identical to the one used in the RPE-LTP algorithm. The array vpar[1..8] is computed with the array L\_av1[0..8] as an input.
+
+#### Schur recursion with 16 bits arithmetic:
+
+```
+IF( L_av1[0] == 0 ) THEN
+    |== FOR i = 1 to 8:
+    |   vpar[i] = 0;
+    |== NEXT i:
+    |   EXIT; /continue with subclause 3.3.2/
+temp = norm( L_av1[0] );
+|== FOR k=0 to 8:
+|   sacf[k] = ( L_av1[k] << temp ) >> 16;
+|== NEXT k:
+```
+
+#### Initialize array P[..] and K[..] for the recursion:
+
+```
+|== FOR i=1 to 7:
+|   K[9-i] = sacf[i];
+|== NEXT i:
+
+|== FOR i=0 to 8:
+|   P[i] = sacf[i];
+|== NEXT i:
+```
+
+#### Compute reflection coefficients:
+
+```
+|== FOR n=1 to 8:
+|   IF( P[0] < abs( P[1] ) ) THEN
+|       |== FOR i = n to 8:
+|       |   vpar[i] = 0;
+|       |== NEXT i:
+|       |   EXIT; /continue with
+|       |   subclause 3.3.2/
+|   vpar[n] = div( abs( P[1] ), P[0] );
+|   IF ( P[1] > 0 ) THEN vpar[n] = sub( 0, vpar[n] );
+|   IF ( n == 8 ) THEN EXIT; /continue with subclause 3.3.2/
+|   Schur recursion:
+|   P[0] = add( P[0], mult_r( P[1], vpar[n] ) );
+|   |=== FOR m=1 to 8-n:
+|   |   P[m] = add( P[m+1], mult_r( K[9-m], vpar[n] ) );
+|   |   K[9-m] = add( K[9-m], mult_r( P[m+1], vpar[n] ) );
+|   |=== NEXT m:
+|   |== NEXT n:
+```
+
+### 6.3.2 Step-up procedure to obtain the aav1[0..8]
+
+#### Initialization of the step-up recursion:
+
+```
+L_coef[0] = 16384 << 15;
+L_coef[1] = vpar[1] << 14;
+```
+
+#### Loop on the LPC analysis order:
+
+```
+|= FOR m = 2 to 8:
+|== FOR i = 1 to m-1:
+|== temp = L_coef[m-i] >> 16; / takes the msb /
+|== L_work[i] = L_add( L_coef[i], L_mult( vpar[m], temp ) );
+|== NEXT i
+|
+|== FOR i = 1 to m-1:
+|== L_coef[i] = L_work[i];
+```
+
+```
+
+|== NEXT i
+|
+| L_coef[m] = vpar[m] << 14;
+| NEXT m:
+
+```
+
+**Keep the aav1[0..8] on 13 bits for next clause:**
+
+```
+
+| FOR i = 0 to 8:
+|   aav1[i] = L_coef[i] >> 19;
+| NEXT i:
+
+```
+
+### 6.3.3 Computation of the rav1[0..8]
+
+```
+
+| FOR i= 0 to 8:
+| L_work[i] = 0;
+|== FOR k = 0 to 8-i:
+|==   L_work[i] = L_add( L_work[i], L_mult( aav1[k], aav1[k+i] ) );
+|== NEXT k:
+| NEXT i:
+
+IF ( L_work[0] == 0 ) THEN normrav1 =0;
+ELSE normrav1 = norm( L_work[0] );
+
+| FOR i= 0 to 8:
+|   rav1[i] = ( L_work[i] << normrav1 ) >> 16;
+| NEXT i:
+
+```
+
+Keep the normrav1 for use in subclause 3.4 and 3.6.
+
+## 6.4 Spectral comparison
+
+This subclause computes the variable stat needed for the threshold adaptation. It uses the array L\_av0[0..8] computed in subclause 3.2 and the array rav1[0..8] computed in subclause 3.3.3.
+
+**Re-normalize L\_av0[0..8]:**
+
+```
+
+IF ( L_av0[0] == 0 ) THEN
+| FOR i = 0 to 8:
+|   sav0[i] = 4095;
+| NEXT i:
+ELSE
+| shift = norm( L_av0[0] );
+| FOR i = 0 to 8:
+|   sav0[i] = ( L_av0[i] << shift-3 ) >> 16;
+| NEXT i:
+
+```
+
+**Compute partial  $\sum$  of dm:**
+
+```
+
+L_Σ p = 0;
+| FOR i = 1 to 8:
+|   L_Σ p = L_add( L_Σ p, L_mult( rav1[i], sav0[i] ) );
+| NEXT i:
+
+```
+
+**Compute the division of partial  $\sum$  by sav0[0]:**
+
+```
+
+IF ( L_Σ p < 0 ) THEN L_temp = L_sub( 0, L_Σ p );
+ELSE L_temp = L_Σ p;
+
+IF ( L_temp == 0 ) THEN
+| L_dm = 0;
+| shift = 0;
+ELSE
+| sav0[0] = sav0[0] << 3;
+| shift = norm( L_temp );
+| temp = ( L_temp << shift ) >> 16;
+
+```
+
+```
+
+| IF ( sav0[0] >= temp ) THEN
+|     | divshift = 0;
+|     | temp = div( temp, sav0[0] );
+| ELSE
+|     | divshift = 1;
+|     | temp = sub( temp, sav0[0] );
+|     | temp = div( temp, sav0[0] );
+|
+| IF( divshift == 1 ) THEN L_dm = 32768;
+| ELSE L_dm = 0;
+|
+| L_dm = L_add( L_dm, temp) << 1;
+| IF( L_Σ p < 0 ) THEN L_dm = L_sub( 0, L_dm);
+
+```
+
+### Re-normalization and final computation of L\_dm:
+
+```
+
+L_dm = ( L_dm << 14 );
+L_dm = L_dm >> shift;
+L_dm = L_add( L_dm, ( rav1[0] << 11 ) );
+L_dm = L_dm >> normrav1;
+
+```
+
+### Compute the difference and save L\_dm:
+
+```
+
+L_temp = L_sub( L_dm, L_lastdm );
+L_lastdm = L_dm;
+IF ( L_temp < 0 ) THEN L_temp = L_sub( 0, L_temp );
+L_temp = L_sub( L_temp, 3277 );
+
+```
+
+### Evaluation of the stat flag:
+
+```
+
+IF ( L_temp < 0 ) THEN stat = 1;
+ELSE stat = 0;
+
+```
+
+## 6.5 Periodicity detection
+
+This subclause just sets the ptch flag needed for the threshold adaptation.
+
+```
+
+temp = add( oldlagcount, veryoldlagcount );
+IF ( temp >= 4 ) THEN ptch = 1;
+ELSE ptch = 0;
+
+```
+
+## 6.6 Threshold adaptation
+
+This subclause uses the variables e\_pvad, m\_pvad, e\_acf0 and m\_acf0 computed in subclause 3.1. It also uses the flags stat (see subclause 3.4) and ptch (see subclause 3.5). It follows the flowchart represented on figure 2.2.
+
+Some constants, represented by a floating point format, are needed and a symbolic name (in capital letter) for their exponent and mantissa is used; table 3.2 lists all these constants with the symbolic names associated and their numerical constant values.
+
+**Table 3.2: List of constants**
+
+| Constant | Exponent      | Mantissa          |
+|----------|---------------|-------------------|
+| pth      | E_PTH = 19    | M_PTH = 18 750    |
+| margin   | E_MARGIN = 27 | M_MARGIN = 19 531 |
+| plev     | E_PLEV = 20   | M_PLEV = 25 000   |
+
+NOTE: Floating point representation of constants used in subclause 3.6:  
+ pth = 2(E\_PTH)x(M\_PTH/32768).  
+ margin = 2(E\_MARGIN)x(M\_MARGIN/32768).  
+ plev = 2(E\_PLEV)x(M\_PLEV/32768).
+
+**Test if acf0 < pth; if yes set thvad to plev:**
+
+```
+
+comp = 0;
+IF ( e_acf0 < E_PTH ) THEN comp = 1;
+IF ( e_acf0 == E_PTH ) THEN IF ( m_acf0 < M_PTH ) THEN comp =1;
+IF ( comp == 1 ) THEN
+    | e_thvad = E_PLEV;
+    | m_thvad = M_PLEV;
+    | EXIT; /continue with subclause 3.7/
+
+```
+
+### **Test if an adaptation is needed:**
+
+```
+
+comp = 0;
+IF ( ptch == 1 ) THEN comp = 1;
+IF ( stat == 0 ) THEN comp = 1;
+IF ( tone == 1 ) THEN comp = 1;
+IF ( comp == 1 ) THEN
+    | adaptcount = 0;
+    | EXIT; /continue with subclause 3.7/
+
+```
+
+### **Incrementation of adaptcount:**
+
+```
+
+adaptcount = add( adaptcount, 1 );
+IF ( adaptcount <= 8 ) THEN EXIT; /continue with subclause 3.7/
+
+```
+
+### **Computation of thvad-(thvad/dec):**
+
+```
+
+m_thvad = sub( m_thvad, (m_thvad >> 5) );
+IF ( m_thvad < 16384 ) THEN
+    | m_thvad = m_thvad << 1;
+    | e_thvad = sub( e_thvad, 1 );
+
+```
+
+### **Computation of pvad\*fac:**
+
+```
+
+L_temp = L_add( m_pvad, m_pvad );
+L_temp = L_add( L_temp, m_pvad );
+L_temp = L_temp >> 1;
+e_temp = add( e_pvad, 1 );
+IF ( L_temp > 32767 ) THEN
+    | L_temp = L_temp >> 1;
+    | e_temp = add( e_temp, 1 );
+m_temp = L_temp;
+
+```
+
+### **Test if thvad < pvad\*fac:**
+
+```
+
+comp = 0;
+IF ( e_thvad < e_temp ) THEN comp = 1;
+IF ( e_thvad == e_temp ) THEN IF ( m_thvad < m_temp ) THEN comp =1;
+
+```
+
+### **Computation of minimum (thvad+(thvad/inc), pvad\*fac) if comp = 1:**
+
+```
+
+IF ( comp == 1 ) THEN
+| Compute thvad +(thvad/inc).
+| L_temp = L_add( m_thvad, (m_thvad >> 4) );
+| IF ( L_temp > 32767 ) THEN
+| | m_thvad = L_temp >> 1;
+| | e_thvad = add( e_thvad, 1 );
+| ELSE m_thvad = L_temp;
+| comp2 = 0;
+| IF ( e_temp < e_thvad ) THEN comp2 = 1;
+| IF ( e_temp == e_thvad ) THEN IF ( m_temp < m_thvad ) THEN comp2 = 1;
+| IF ( comp2 == 1 ) THEN
+| | e_thvad = e_temp;
+| | m_thvad = m_temp;
+
+```
+
+### **Computation of pvad + margin:**
+
+```
+
+IF ( e_pvad == E_MARGIN ) THEN
+    | L_temp = L_add(m_pvad, M_MARGIN);
+    | m_temp = L_temp >> 1;
+
+```
+
+```
+
+                | e_temp = add( e_pvad, 1 );
+ELSE
+| IF ( e_pvad > E_MARGIN ) THEN
+| | temp = sub( e_pvad, E_MARGIN );
+| | temp = M_MARGIN >> temp;
+| | L_temp = L_add( m_pvad, temp );
+| | IF ( L_temp > 32767) THEN
+| | | e_temp = add( e_pvad, 1 );
+| | | m_temp = L_temp >> 1;
+| | ELSE
+| | | e_temp = e_pvad;
+| | | m_temp = L_temp;
+| ELSE
+| | temp = sub( E_MARGIN, e_pvad );
+| | temp = m_pvad >> temp;
+| | L_temp = L_add( M_MARGIN, temp );
+| | IF ( L_temp > 32767) THEN
+| | | e_temp = add( E_MARGIN, 1 );
+| | | m_temp = L_temp >> 1;
+| | ELSE
+| | | e_temp = E_MARGIN;
+| | | m_temp = L_temp;
+
+```
+
+### **Test if thvad > pvad + margin:**
+
+```
+
+comp = 0;
+IF ( e_thvad > e_temp) THEN comp = 1;
+IF (e_thvad == e_temp) THEN IF (m_thvad > m_temp) THEN comp =1;
+
+IF ( comp == 1 ) THEN
+| e_thvad = e_temp;
+| m_thvad = m_temp;
+
+```
+
+### **Initialize new rvad[0..8] in memory:**
+
+```
+
+normrvad = normrav1;
+
+|= FOR i = 0 to 8:
+|= rvad[i] = rav1[i];
+|= NEXT i:
+
+```
+
+### **Set adaptcount to adp + 1:**
+
+```
+
+adaptcount = 9;
+
+```
+
+## 6.7 VAD decision
+
+This subclause only outputs the result of the comparison between pvad and thvad using the pseudo-floating point representation of thvad and pvad. The values e\_pvad and m\_pvad are computed in subclause 3.1 and the values e\_thvad and m\_thvad are computed in subclause 3.6.
+
+```
+
+vvad = 0;
+IF (e_pvad > e_thvad) THEN vvad = 1;
+IF (e_pvad == e_thvad) THEN IF (m_pvad > m_thvad) THEN vvad =1;
+
+```
+
+## 6.8 VAD hangover addition
+
+This subclause finally sets the vad decision for the current frame to be processed.
+
+```
+
+IF ( vvad == 1 ) THEN burstcount = add( burstcount, 1 );
+ELSE burstcount = 0;
+
+IF ( burstcount >= 3 ) THEN
+| hangcount = 5;
+| burstcount = 3;
+
+vad = vvad;
+IF ( hangcount >= 0 ) THEN
+| vad = 1;
+
+```
+
+```
+| hangcount = sub( hangcount, 1 );
+```
+
+## 6.9 Periodicity updating
+
+This subclause must be delayed until the LTP lags are computed by the RPE-LTP algorithm. The LTP lags called Nc in the speech encoder are renamed lags[0..3] (index 0 for the first sub- segment of the frame, 1 for the second and so on).
+
+### Loop on sub-segments for the frame:
+
+```
+lagcount = 0;
+
+|= FOR i = 0 to 3:
+|= Search the maximum and minimum of consecutive lags.
+|= IF ( oldlag > lags[i] ) THEN
+|= | minlag = lags[i];
+|= | maxlag = oldlag;
+|= ELSE
+|= | minlag = oldlag;
+|= | maxlag = lags[i] ;
+|=
+|= Compute smallag (modulo operation not defined ):
+|=
+|= smallag = maxlag;
+|== | FOR j = 0 to 2:
+|== | IF (smallag >= minlag) THEN smallag =sub( smallag, minlag);
+|== | NEXT j;
+|=
+|= Minimum of smallag and minlag - smallag:
+|=
+|= temp = sub( minlag, smallag );
+|= IF ( temp < smallag ) THEN smallag = temp;
+|= IF ( smallag < 2 ) THEN lagcount = add( lagcount, 1 );
+|= Save the current LTP lag.
+|= oldlag = lags[i];
+|= NEXT i:
+```
+
+### Update the veryoldlagcount and oldlagcount:
+
+```
+veryoldlagcount = oldlagcount;
+oldlagcount = lagcount;
+```
+
+## 6.10 Tone detection
+
+This subclause computes the tone variable needed for the threshold adaptation. Tone is only calculated for the VAD in the downlink. In the uplink VAD tone=0.
+
+To reduce delay, this subclause should be calculated after the processing of the current speech encoder frame.
+
+### 6.10.1 Windowing
+
+This subclause applies a Hanning window to the input frame sof[0..159] to form the output frame sofh[0..159]. The input frame is the current offset compensated signal frame calculated in the RPE-LTP codec. The array of constants hann[i] is defined in table 3.2.
+
+#### Multiply signal frame by Hanning window :
+
+```
+|== FOR i = 0 to 79:
+|   sofh[i] = mult_r( sof[i], hann[i] );
+|   sofh[159-i] = mult_r( sof[159-i], hann[i] );
+|== NEXT i;
+```
+
+### 6.10.2 Auto-correlation
+
+This subclause computes the auto-correlation vector L\_acfh[0..5] from the windowed input frame sofh[0..159]. The input frame must be scaled in order to avoid an overflow situation. This subclause is identical to the one used in the RPE-LTP algorithm, with the exception that only five auto-correlation values are calculated.
+
+#### Dynamic scaling of the array sofh[0..159]:
+
+#### Search for the maximum :
+
+```
+smax = 0;
+
+|== FOR k = 0 to 159:
+|   temp = abs( sofh[k] );
+|   IF ( temp > smax ) THEN smax = temp;
+|== NEXT k;
+```
+
+#### Computation of the scaling factor :
+
+```
+IF ( smax == 0 ) THEN scalauto = 0;
+ELSE scalauto = sub( 4, norm( smax << 16) );
+```
+
+#### Scaling of the array sofh[0..159]:
+
+```
+IF ( scalauto > 0 ) THEN
+    | temp = 16384 >> sub( scalauto,1);
+    |== FOR k = 0 to 159:
+    |   sofh[k] = mult_r( sofh[k], temp);
+    |== NEXT k;
+```
+
+#### Compute the L\_ACF[..]:
+
+```
+|== FOR k=0 to 4:
+|   L_acfh[k] = 0;
+|=== FOR i=k to 159:
+|       L_temp = L_mult( sofh[i], sofh[i-k] );
+|       L_acfh[k] = L_add( L_acfh[k], L_temp );
+|=== NEXT i:
+|== NEXT k:
+```
+
+### 6.10.3 Computation of the reflection coefficients
+
+This subclause calculates the reflection coefficients rc[1..4] from the input array L\_acfh[0..4]. This procedure is identical to the one in subclause 3.3.1 and the RPE-LTP codec, with the exception that only four reflection coefficients are calculated.
+
+#### Schur recursion with 16 bits arithmetic :
+
+```
+IF( L_acfh[0] == 0 ) THEN
+    |== FOR i = 1 to 4:
+    |   rc[i] = 0;
+    |== NEXT i:
+    | EXIT; /continue with subclause 3.10.4/
+temp = norm( L_acfh[0] );
+|== FOR k=0 to 4:
+|   sacf[k] = ( L_acfh[k] << temp ) >> 16;
+|== NEXT k:
+```
+
+#### Initialize array P[..] and K[..] for the recursion :
+
+```
+|== FOR i=1 to 3:
+|   K[5-i] = sacf[i];
+|== NEXT i:
+
+|== FOR i=0 to 4:
+|   P[i] = sacf[i];
+|== NEXT i:
+```
+
+#### Compute reflection coefficients :
+
+```
+|== FOR n=1 to 4:
+|   IF( P[0] < abs( P[1] ) ) THEN
+|       |== FOR i = n to 4:
+|       |   rc[i] = 0;
+|       |== NEXT i:
+|       | EXIT; /continue with subclause 3.10.4/
+|   rc[n] = div( abs( P[1] ), P[0] );
+|   IF ( P[1] > 0 ) THEN rc[n] = sub( 0, rc[n] );
+|   IF ( n == 4 ) THEN EXIT; /continue with subclause 3.10.4/
+```
+
+```
+
+|
+| Schur recursion :
+|
+|   P[0] = add( P[0], mult_r( P[1], rc[n] ) );
+|=== FOR m=1 to 4-n:
+|     P[m] = add( P[m+1], mult_r( K[5-m], rc[n] ) );
+|     K[5-m] = add( K[5-m], mult_r( P[m+1], rc[n] ) );
+|=== NEXT m:
+|
+|== NEXT n:
+
+```
+
+### 6.10.4 Filter coefficient calculation
+
+This subclause calculates the direct form filter coefficients a[1..2] from the reflection coefficients rc[1..4].
+
+#### Step-up procedure to obtain the a[1..2]:
+
+```
+
+temp = rc[1] >> 2;
+a[1] = add( temp, mult_r( rc[2], temp ) );
+a[2] = rc[2] >> 2;
+
+```
+
+### 6.10.5 Pole Frequency Test
+
+This subclause uses the direct form filter coefficients a[1..2] to determine the pole frequency of the second order LPC analysis. If the pole frequency is less than 385 Hz tone is set to 0 and clause 3 terminates.
+
+```
+
+L_den = L_mult ( a[1], a[1] );
+
+L_temp = a[2] << 16;
+L_num = L_sub ( L_temp, L_den );
+
+```
+
+#### If pole is not complex then exit :
+
+```
+
+IF ( L_num <= 0 ) THEN
+| tone = 0;
+| EXIT; /clause 3 complete/
+
+```
+
+#### If pole frequency is less than 385 Hz then exit :
+
+```
+
+IF ( a[1] < 0 ) THEN
+| temp = L_den >> 16;
+| L_den = L_mult ( temp, 3189 );
+| L_temp = L_sub ( L_num, L_den );
+| IF ( L_temp < 0 ) THEN
+| | tone = 0;
+| | EXIT; /clause 3 complete/
+
+```
+
+### 6.10.6 Prediction gain test
+
+This subclause uses the reflection coefficients rc[1..4] to calculate the prediction gain. If the prediction gain is greater than 13,5 dB then tone is set to 1 otherwise tone is set to 0.
+
+#### Calculate normalized prediction error :
+
+```
+
+prederr = 32767;
+
+|== FOR i=1 to 4
+|   temp = mult ( rc[i], rc[i] );
+|   temp = sub ( 32767, temp );
+|   prederr = mult( prederr, temp );
+|== NEXT i;
+
+```
+
+#### Test if prediction error is smaller than threshold :
+
+```
+
+temp = sub ( prederr, 1464 );
+
+IF ( temp < 0 ) THEN tone = 1;
+ELSE tone = 0;
+
+```
+
+**Table 3.2: Values of the Hanning window array hann[i]**
+
+| i  | hann | i  | hann  | i  | hann  | i  | hann  |
+|----|------|----|-------|----|-------|----|-------|
+| 0  | 0    | 20 | 4856  | 40 | 16545 | 60 | 28139 |
+| 1  | 12   | 21 | 5325  | 41 | 17192 | 61 | 28581 |
+| 2  | 51   | 22 | 5811  | 42 | 17838 | 62 | 29003 |
+| 3  | 114  | 23 | 6314  | 43 | 18482 | 63 | 29406 |
+| 4  | 204  | 24 | 6832  | 44 | 19122 | 64 | 29789 |
+| 5  | 318  | 25 | 7365  | 45 | 19758 | 65 | 30151 |
+| 6  | 458  | 26 | 7913  | 46 | 20389 | 66 | 30491 |
+| 7  | 622  | 27 | 8473  | 47 | 21014 | 67 | 30809 |
+| 8  | 811  | 28 | 9046  | 48 | 21631 | 68 | 31105 |
+| 9  | 1025 | 29 | 9631  | 49 | 22240 | 69 | 31377 |
+| 10 | 1262 | 30 | 10226 | 50 | 22840 | 70 | 31626 |
+| 11 | 1523 | 31 | 10831 | 51 | 23430 | 71 | 31852 |
+| 12 | 1807 | 32 | 11444 | 52 | 24009 | 72 | 32053 |
+| 13 | 2114 | 33 | 12065 | 53 | 24575 | 73 | 32230 |
+| 14 | 2444 | 34 | 12693 | 54 | 25130 | 74 | 32382 |
+| 15 | 2795 | 35 | 13326 | 55 | 25670 | 75 | 32509 |
+| 16 | 3167 | 36 | 13964 | 56 | 26196 | 76 | 32611 |
+| 17 | 3560 | 37 | 14607 | 57 | 26707 | 77 | 32688 |
+| 18 | 3972 | 38 | 15251 | 58 | 27201 | 78 | 32739 |
+| 19 | 4405 | 39 | 15898 | 59 | 27679 | 79 | 32764 |
+
+# 7 Digital test sequences
+
+This clause provides information on the digital test sequences that have been designed to help the verification of implementations of the Voice Activity Detector. Copies of these sequences are available (see clause A.2).
+
+## 7.1 Test configuration
+
+The VAD must be tested in conjunction with the speech encoder defined in GSM 06.10. The test configuration is shown in figure 4.1. The input signal to the speech encoder is the sop[...] signal as defined in GSM 06.10 table 5.1. The relevant parameters produced by the speech encoder are input to the VAD algorithm to produce the VAD output. This output has to be checked against some reference files.
+
+The file format of the encoder output parameters given in GSM 06.10 table 5.1 is extended to carry the VAD information.
+
+The VAD information is placed in the unused bit 15 (MSB) of the first encoded parameter:
+
+```
+LAR(1): bit 15 = 1 if VAD on
+        bit 15 = 0 if VAD off
+```
+
+Furthermore, in order to facilitate approval testing over the air interface, the SP flag generated by the TX DTX handler (see GSM 06.31) on the basis of the VAD flag is placed in the MSB position of the second encoded parameter:
+
+```
+LAR(2): bit 15 = 1 if SP on
+        bit 15 = 0 if SP off
+```
+
+The output file will also contain the SID codeword and the comfort noise parameters as described in GSM 06.12 and GSM 06.31.
+
+![Block diagram of VAD test configuration showing RPE-LTP encoder, VAD under test, and TX DTX handler blocks with their respective inputs and outputs.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+The diagram illustrates the VAD test configuration. It consists of three main blocks: an RPE-LTP encoder, a VAD under test, and a TX DTX handler. The RPE-LTP encoder receives a 13 bit PCM input and a Reset signal. It is also connected to an 8kHz clock. The encoder outputs 260 bits to the TX DTX handler. The VAD under test receives the same Reset signal and outputs a 1 bit VAD flag to the TX DTX handler. The TX DTX handler outputs SID or speech (260 bits) and an SP flag (1 bit). The word 'COMPARISON' is also present within the TX DTX handler block.
+
+```
+graph LR; Clock[8kHz clock] --> RPE[RPE-LTP encoder]; PCM[13 bit PCM] --> RPE; Reset[Reset] --> RPE; Reset --> VAD[VAD under test]; RPE -- "260 bits" --> TX[TX DTX handler]; VAD -- "VAD flag 1 bit" --> TX; TX -- "SID or speech 260 bits" --> Out1[SID or speech 260 bits]; TX -- "SP flag 1 bit" --> Out2[SP flag 1 bit]; subgraph TX [TX DTX handler]; COMPARISON[COMPARISON]; end;
+```
+
+Block diagram of VAD test configuration showing RPE-LTP encoder, VAD under test, and TX DTX handler blocks with their respective inputs and outputs.
+
+Figure 4.1: VAD test configuration
+
+## 7.2 Test sequences
+
+The test sequences are described in detail in clause A.2.
+
+# --- Annex A (informative):
+
+## A.1 Simplified block filtering operation
+
+Consider an 8th order transversal filter with filter coefficients  $a_0..a_8$ , through which a signal is being passed, the output of the filter being:
+
+$$s'(n) = -\sum_{i=0}^8 a_i s(n-i) \quad (1)$$
+
+If we apply block filtering over 20 ms segments, then this equation becomes:
+
+$$s'(n) = -\sum_{i=0}^8 a_i s(n-i); 0 \leq n-i \leq 159; 0 \leq n \leq 167 \quad (2)$$
+
+If the energy of the filtered signal is then obtained for every 20 ms segment, the equation for this is:
+
+$$Pvad = \sum_{n=0}^{167} \left\{ -\sum_{i=0}^8 a_i s(n-i) \right\}^2; 0 \leq n-i \leq 159 \quad (3)$$
+
+We know that (see GSM 06.10, subclause 3.1.4):
+
+$$acf_i = \sum_{n=0}^{159} s_n s_{n-i}; 0 \leq n-i \leq 159; i = 0..8 \quad (4)$$
+
+If equation (3) is expanded and  $acf_0..acf_8$  are substituted for  $s_n$  then we arrive at the equations:
+
+$$Pvad = r_0 acf_0 + 2 \sum_{i=1}^8 r_i acf_i \quad (5)$$
+
+Where:
+
+$$r_i = \sum_{k=0}^{8-i} a_k a_{k+i}; i = 0..8 \quad (6)$$
+
+## --- A.2 Description of digital test sequences
+
+### A.2.1 Test sequences
+
+The VAD algorithm uses results from the full rate speech encoder defined in GSM 06.10. In the testing of the VAD, it is assumed that the relevant speech encoder functions have been verified by the test sequences defined in GSM 06.10.
+
+The five types of input sequences are briefly described below.
+
+#### Spectral comparison
+
+The two kinds of statements of the spectral comparison algorithm (subclause 3.4), arithmetic statements and control statements, are tested by separate test sequences.
+
+Arithmetic statements:
+
+spec\_a1.\*
+
+spec\_a2.\*
+
+Control statements
+
+spec\_c1.\*
+
+spec\_c2.\*
+
+spec\_c3.\*
+
+spec\_c4.\*
+
+#### Threshold adaptation
+
+There are two types of tests to verify the threshold adaptation described in subclause 3.6:
+
+adapt\_i1.\*  
+adapt\_i2.\*
+
+The initial test sequences test the acf0 and VAD decision. A fault in the VAD decision will cause all the other sequences to fail, so it is recommended that this test is run before all other tests.
+
+adapt\_m1.\*  
+adapt\_m2.\*
+
+The main test sequences will check the basic threshold adaptation mechanism.
+
+#### Periodicity detection
+
+pitch1.\*  
+pitch2.\*
+
+These sequences check the periodicity detection algorithm described in subclause 3.5.
+
+#### Tone detection
+
+The tone detector test sequences are only required for downlink VAD implementations. There are three types of test to verify the tone detection algorithm described in subclause 3.10. The first test sequence tests the operation of the tone detector by means of a frequency sweep:
+
+freq\_sw.\*
+
+The following test sequences test the prediction gain calculation within the tone detector:
+
+pred1.\*  
+pred2.\*
+
+The following sequences test the second order pole frequency calculation within the tone detector:
+
+pole1.\*  
+pole2.\*
+
+#### "Safety" and initialization
+
+safety.\*
+
+This sequence checks that safety tests have been implemented to prevent zero values being passed to the norm function. It checks the functions described in the Adaptive Filtering and Energy Computation subclause (subclause 3.1), and the Predictor Values Computation (subclause 3.3). This sequence also checks the initialization of thvad and the rvad array.
+
+#### Real speech
+
+good\_sp.\*  
+bad\_sp.\*
+
+Because the test sequences cannot be guaranteed to find every possible error, there is a small possibility that an implementation of the correct output for test sequences, but fail with real speech. Because of this, an extra set of sequences are included that consist of barely detectable speech and very clean speech.
+
+There are 3 different file extensions:
+
+\*.inp: speech encoder input sequences, binary files
+
+\*.vad: output flag of the VAD algorithm, ASCII files
+
+\*.cod: TX DTX handler output sequences, binary files for comparison with VAD/DTX handler output.
+
+The \*.cod files contain speech coder output information in the format described in clause 4.
+
+It should be noted that there is no requirement in GSM 06.12 for a bit exact implementation of the averaging procedure to calculate the "LAR" and "xmax" parameters in the SID frames. Different implementations are allowed.
+
+The algorithms used for the calculation of the LAR and xmax parameters of the SID frames are therefore reproduced below:
+
+#### **LAR averaging:**
+
+```
+| FOR i = 1 to 8:
+|   L_Temp = 2; /* const. for rounding*/
+|   | FOR n = 1 to 4:
+|   |   L_Temp1 = LAR[j-n](i); /*conversion 16 --> 32 bit*/
+|   |   L_Temp = L_Add( L_Temp , L_Temp1 );
+|   | NEXT n
+|   L_Temp = L_Temp >> 2;
+|   mean (LAR(i)) = L_Temp; /*conversion 32 --> 16 bit*/
+| NEXT i;
+```
+
+#### **xmax averaging**
+
+```
+L_Temp = 8; /* const. for rounding*/
+
+| FOR n = 1 to 4:
+|   | FOR i = 1 to 4:
+|   |   L_Temp1 = xmax[j-n](i); /*conversion 16 --> 32 bit*/
+|   |   L_Temp = L_Add( L_Temp , L_Temp1 );
+|   | NEXT i
+| NEXT n
+
+L_Temp = L_Temp >> 4;
+
+mean (xmax) = L_Temp; /*conversion 32 --> 16 bit*/
+```
+
+### **A.2.2 File format description**
+
+All the \*.inp and \*.cod files are written in binary using 16 bit words, while all \*.vad files are written in ASCII format. The sizes of the files are shown in table A.2.1, A.2.2 and A.2.3. The detailed format of the \*.inp and \*.cod files is in accordance with the descriptions given in GSM 06.10 clause 5.
+
+**Table A.2.1: File sizes for \*.inp extension files**
+
+| <b>File:</b> | <b>Frames:</b> | <b>Size in bytes:</b> |
+|--------------|----------------|-----------------------|
+| spec_a1.inp  | 22             | 7 040                 |
+| spec_a2.inp  | 22             | 7 040                 |
+| spec_c1.inp  | 48             | 15 360                |
+| spec_c2.inp  | 48             | 15 360                |
+| spec_c3.inp  | 48             | 15 360                |
+| spec_c4.inp  | 48             | 15 360                |
+| adapt_i1.inp | 67             | 21 440                |
+| adapt_i2.inp | 48             | 15 360                |
+| adapt_m1.inp | 403            | 128 960               |
+| adapt_m2.inp | 376            | 120 320               |
+| pitch1.inp   | 35             | 11 200                |
+| pitch2.inp   | 35             | 11 200                |
+| freq_sw.inp  | 560            | 179 200               |
+| pred1.inp    | 126            | 40 320                |
+| pred2.inp    | 126            | 40 320                |
+| pole1.inp    | 97             | 31 040                |
+| pole2.inp    | 42             | 13 440                |
+| safety.inp   | 5              | 16 00                 |
+| good_sp.inp  | 312            | 99 840                |
+| bad_sp.inp   | 312            | 99 840                |
+
+**Table A.2.2: File sizes for \*.cod extension files**
+
+| <b>File:</b> | <b>Frames:</b> | <b>Size in bytes:</b> |
+|--------------|----------------|-----------------------|
+| spec_a1.cod  | 22             | 3 344                 |
+| spec_a2.cod  | 22             | 3 344                 |
+| spec_c1.cod  | 48             | 7 296                 |
+| spec_c2.cod  | 48             | 7 296                 |
+| spec_c3.cod  | 48             | 7 296                 |
+| spec_c4.cod  | 48             | 7 296                 |
+| adapt_i1.cod | 67             | 10 184                |
+| adapt_i2.cod | 48             | 7 296                 |
+| adapt_m1.cod | 403            | 61 256                |
+| adapt_m2.cod | 376            | 57 152                |
+| pitch1.cod   | 35             | 5 320                 |
+| pitch2.cod   | 35             | 5 320                 |
+| freq_sw.cod  | 560            | 85 120                |
+| pred1.cod    | 126            | 19 152                |
+| pred2.cod    | 126            | 19 152                |
+| pole1.cod    | 97             | 14 744                |
+| pole2.cod    | 42             | 6 384                 |
+| safety.cod   | 5              | 760                   |
+| good_sp.cod  | 312            | 47 424                |
+| bad_sp.cod   | 312            | 47 424                |
+
+**Table A.2.3: File sizes for \*.vad extension files**
+
+| File:        | Frames: | Size in bytes: |
+|--------------|---------|----------------|
+| spec_a1.vad  | 22      | 88             |
+| spec_a2.vad  | 22      | 88             |
+| spec_c1.vad  | 48      | 192            |
+| spec_c2.vad  | 48      | 192            |
+| spec_c3.vad  | 48      | 192            |
+| spec_c4.vad  | 48      | 192            |
+| adapt_i1.vad | 67      | 268            |
+| adapt_i2.vad | 48      | 192            |
+| adapt_m1.vad | 403     | 1 612          |
+| adapt_m2.vad | 376     | 1504           |
+| pitch1.vad   | 35      | 140            |
+| pitch2.vad   | 35      | 140            |
+| freq_sw.inp  | 560     | 2 240          |
+| pred1.vad    | 126     | 504            |
+| pred2.vad    | 126     | 504            |
+| pole1.vad    | 97      | 388            |
+| pole2.vad    | 42      | 168            |
+| safety.vad   | 5       | 20             |
+| good_sp.vad  | 312     | 1 248          |
+| bad_sp.vad   | 312     | 1 248          |
+
+## A.3 VAD performance
+
+In optimizing a VAD a difficult trade-off has to be made between speech clipping which reduces the subjective performance of the system, and the average activity factor. The benefit of DTX is increased as the average activity factor is reduced. However, in general, a reduction of the activity will be associated with a greater risk for audible speech clipping.
+
+In the optimization process, great emphasis has been placed on avoiding unnecessary speech clipping. However, it has been found that a VAD with virtually no audible clipping would result in a very high activity and very little DTX advantage.
+
+The VAD specified in this technical specification introduces audible and possibly objectionable clipping in certain cases, mainly with low input levels. However, a comprehensive evaluation programme consisting of about 600 individual conversations conducted in a wide range of realistic conditions, it was found that about 90% of the conversations were free from objectionable clipping.
+
+The voice activity performance of the VAD is summarized in table A.3.1. The activity figures are averages of a large number of conversations covering factors like different talkers, noise characteristics and locations. It should be noted that the actual activity of a particular talker in a specific conversation may vary considerably relative to the averages given. This is due both to the variation in talker behaviour as well as to the level dependency of the VAD (the channel activity has been found to decrease by about 0,5 points of percentage per dB level reduction). However, as mentioned above, a decreased speech input level increases the risk of objectionable speech clipping.
+
+All the values given are activity figures, i.e. the % of time the radio channel has to be on.
+
+**Table A.3.1: Summary of channel activity**
+
+| Telephone instrument | Situation                                                | Typical channel activity factor: |
+|----------------------|----------------------------------------------------------|----------------------------------|
+| Handset              | Quiet location                                           | 55%                              |
+| Handset              | Moderate office noise with voice interference            | 60%                              |
+| Handset              | Strong voice interference (e.g. airport/railway station) | 65-70%                           |
+| Handsfree/handset    | Variable vehicle noise                                   | 60%                              |
+
+## A.4 Pole frequency calculation
+
+This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz.
+
+The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients  $rc[1..2]$  obtained from the speech encoder. This is done using the routine described in subclause 3.10.4. If the filter coefficients  $a[0..2]$  are defined such that the synthesis filter response is given by:
+
+$$H(z) = 1 / (a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$
+
+Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic:
+
+$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$
+
+The positions of the poles,  $z$ , are therefore:
+
+$$z = re \pm j*sqrt(im), \quad j^2 = -1 \quad (3)$$
+
+where:
+
+$$re = - a[1] / 2 \quad (4)$$
+
+$$im = (4*a[2] - a[1]^2) / 4 \quad (5)$$
+
+If  $im$  is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If  $re$  is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2 000 Hz and the prediction error test can be performed.
+
+If  $im$  is positive and  $re$  is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to  $re$  and  $im$  by the expression:
+
+$$freq = \arctan(sqrt(im)/re) * 4\,000 / \pi \quad (6)$$
+
+Having ensured that both  $im$  and  $re$  are positive, the test for a dominant frequency less than 385 Hz can be derived by substituting Equations 4 and 5 into Equation 6 and re-arranging:
+
+$$(4*a[2] - a[1]^2) / a[1]^2 < (\tan(\pi*385/4\,000))^2 \quad (7)$$
+
+or
+
+$$(4*a[2] - a[1]^2) / a[1]^2 < 0.0973 \quad (8)$$
+
+If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed.
+
+# --- Annex B (normative):Test sequences
+
+The test vectors are described in the present document are supplied in archive en\_300965v080000p0.zip which accompanies the present document. The files contained in this archive are listed in clause A.2.
+
+The full rate test vectors apply to both GSM Phase 1 and Phase 2. However, the files pole1.\* pole2.\* pred1.\* pred2.\* and freq\_sw.\* are not required for Phase 1 (uplink and downlink) and Phase 2 uplink implementations.
+
+# Annex C (informative): Change history
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#09         |           |         |                  | 4.0.5       | ETSI Publication                        |
+| SMG#17         |           |         |                  | 4.2.1       | ETSI Publication                        |
+| SMG#23         |           |         |                  | 4.3.1       | ETSI Publication                        |
+| SMG#23         |           |         |                  | 5.0.3       | Release 1996 version                    |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46041/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/46_series/46041/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..40bf91f18b74704427baa764729b236e49115f42
--- /dev/null
+++ b/marked/Rel-16/46_series/46041/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b8b4d8d01b8b90f83872f6329e2cfee7348c943e907f4545f0c77efea5e76a0
+size 41997
diff --git a/marked/Rel-16/46_series/46041/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46041/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5856b32a2631d4e9ea131b2a3f1670909d3cc910
--- /dev/null
+++ b/marked/Rel-16/46_series/46041/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2bc3dcbc1c6f13fd364149afd900bb2fa4f25f4b246c2c22e639139b8576d51
+size 77442
diff --git a/marked/Rel-16/46_series/46041/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/46_series/46041/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..947196dcc8b91e3f1a97a10b777260ab7ee6d020
--- /dev/null
+++ b/marked/Rel-16/46_series/46041/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b35297d12f15dc4f736b7ff2e7156883d597b6233c27f7b20bcde3c673ba78be
+size 37333
diff --git a/marked/Rel-16/46_series/46041/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/46_series/46041/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ef5da50539a8364f890dc902169dd615c52ac948
--- /dev/null
+++ b/marked/Rel-16/46_series/46041/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d7a5ced7b9fc7768e672283ba251f9ea709d4ebe6f720f7e818a6977621e3a89
+size 91633
diff --git a/marked/Rel-16/46_series/46041/raw.md b/marked/Rel-16/46_series/46041/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..24c305242f11030c4c55892b978773672efc6908
--- /dev/null
+++ b/marked/Rel-16/46_series/46041/raw.md
@@ -0,0 +1,383 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                |    |
+|------------------------------------------------|----|
+| Foreword .....                                 | 4  |
+| 1 Scope.....                                   | 5  |
+| 2 References.....                              | 5  |
+| 3 Definitions, symbols and abbreviations.....  | 6  |
+| 3.1 Definitions.....                           | 6  |
+| 3.2 Symbols.....                               | 7  |
+| 3.3 Abbreviations .....                        | 7  |
+| 4 General.....                                 | 7  |
+| 4.1 General Organisation.....                  | 7  |
+| 5 Transmit (TX) side.....                      | 8  |
+| 5.1 General Operation .....                    | 8  |
+| 5.1.1 Functions of the TX DTX handler.....     | 8  |
+| 5.1.2 Functions of the TX radio subsystem..... | 9  |
+| 6 Receive (RX) side .....                      | 11 |
+| 6.1 General operation .....                    | 11 |
+| 6.1.1 Functions of the RX radio subsystem..... | 11 |
+| 6.1.2 Functions of the RX DTX handler .....    | 12 |
+| Annex A (informative): Change history.....     | 13 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document is a GSM technical specification version 7 and is part of the 1998 release of the GSM Technical Specifications. The present document is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".**
+
+GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives a description of the general baseband operation of half rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
+
+For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described below, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
+
+In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX Handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being a part of the A-bis interface as described in GSM 08.61 [10].
+
+The DTX functions described in the present document are mandatory for implementation in all GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 04.08: "Digital cellular telecommunication system (Phase 2+); Mobile radio interface layer 3 specification".
+- [3] GSM 05.05: "Digital cellular telecommunications system (Phase 2+); Radio transmission and reception".
+- [4] GSM 05.08: "Digital cellular telecommunication system (Phase 2+); Radio subsystem link control".
+- [5] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech Part 1: Half rate speech processing functions".
+- [6] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [7] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- [8] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- [9] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- [10] GSM 08.61: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for half rate traffic channels".
+
+[11] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech Part 7: ANSI-C code for the GSM half rate speech codec".
+
+# 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**accepted SID frame:** traffic frame which is flagged with SID= "1" or SID= "2" by the Radio Subsystem.
+
+**bad traffic frame:** traffic frame flagged BFI= "1" (Bad Frame Indication) or with UFI= "1" (Unreliable Frame Indication) by the Radio Subsystem.
+
+**frame:** time interval of 20 ms corresponding to the time segmentation of the half rate speech transcoder defined in GSM 06.20 (ETS 300 969) [6], also used as a short term for a traffic frame.
+
+**good speech frame:** good traffic frame which is not an accepted SID frame.
+
+**good traffic frame:** traffic frame flagged BFI= "0" and UFI= "0" by the Radio Subsystem.
+
+**GS averaging period:** period in which the quantized energy tweak parameters GS are averaged: it corresponds to the hangover period.
+
+**hangover period:** period of 7 frames added at the end of a speech burst in which VAD flag= "0" and SP flag= "1".
+
+**invalid SID frame:** accepted SID frame which was not classified as valid SID frame. This frame is not valid for updating comfort noise parameters, but the frame conveys information that comfort noise generations should be started or continued.
+
+**lost SID frame:** unusable frame received when the RX DTX Handler is generating comfort noise and a SID frame is expected (Time Alignment Flag TAF= "1").
+
+**lost speech frame:** unusable frame received when the RX DTX Handler is passing on traffic frames directly to the speech decoder.
+
+**SID code word:** fixed bit pattern defined in GSM 06.22 [8], for labelling a traffic frame as a SID frame.
+
+**SID field:** bit positions defined in GSM 06.22 [8], of the SID codeword within a SID frame.
+
+**SID frame:** frame characterised by the SID (Silence Descriptor) code word. It conveys information on the acoustic background noise.
+
+**SP flag:** boolean flag, generated by the TX DTX handler, indicating the presence of a speech frame ("1") or the presence of a SID frame ("0").
+
+**speech frame:** traffic frame that cannot be classified as a SID frame.
+
+**traffic frame:** block of 112 information bits transmitted on the half rate speech traffic channel.
+
+**unusable frame:** bad traffic frame that is not an accepted SID frame.
+
+**VAD flag:** boolean flag, generated by the VAD algorithm defined in GSM 06.42 [9], indicating the presence ("1") or the absence ("0") of a speech frame.
+
+**valid SID frame:** good traffic frame flagged with SID= "2" by the Radio Subsystem. This frame is valid for updating comfort noise parameters at any time.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                      |                                                           |
+|----------------------|-----------------------------------------------------------|
+| GS                   | Energy tweak parameter                                    |
+| N <sub>elapsed</sub> | Number of elapsed frames since the last updated SID frame |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                         |
+|-------|-----------------------------------------|
+| BFI   | Bad Frame Indicator                     |
+| BSC   | Base Station Controller                 |
+| BSS   | Base Station System                     |
+| DTX   | Discontinuous Transmission              |
+| FACCH | Fast Associated Control CHannel         |
+| FEC   | Forward Error Correction                |
+| GSM   | Global System for Mobile communications |
+| MS    | Mobile Station                          |
+| RSS   | Radio Sub System                        |
+| RX    | Receive                                 |
+| SACCH | Slow Associated Control CHannel         |
+| SID   | SIlence Descriptor                      |
+| TAF   | Time Alignment Flag                     |
+| TX    | Transmit                                |
+| UFI   | Unreliable Frame Indicator              |
+| VAD   | Voice Activity Detector                 |
+
+For abbreviations not given in this clause, see GSM 01.04 [1].
+
+# --- 4 General
+
+DTX is a mechanism which allows the radio transmitter to be switched off most of the time during speech pauses for the following two purposes:
+
+- to save power in the MS;
+- to reduce the overall interference level over the air interface.
+
+DTX shall be in operation in GSM MS if commanded so by the network, see GSM 04.08 [2].
+
+## 4.1 General Organisation
+
+The overall DTX mechanism described in the present document requires the following functions:
+
+- a Voice Activity Detector (VAD) on the transmit (TX) side;
+- evaluation of the background acoustic noise on the TX side, in order to TX characteristic parameters to the receive (RX) side;
+- generation on the RX side of a similar noise, called comfort noise, during periods where the radio transmission is switched off.
+
+The VAD is defined in GSM 06.42 [9], the comfort noise functions in GSM 06.22 [8]. Both are based partly on the speech transcoder and its internal variables, defined in GSM 06.20 [6].
+
+In addition to these functions, if the parameters arriving at the (RX) side are detected to be corrupted by errors, the speech or comfort noise shall be generated from substituted data in order to avoid sound defects for the listener. This function is defined in GSM 06.21 [7].
+
+An overall description of the speech processing parts can be found in GSM 06.02 [5].
+
+# --- 5 Transmit (TX) side
+
+A block diagram of the TX side DTX functions is shown in figure 1.
+
+![Block diagram of the transmit side DTX functions. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The Speech encoder outputs 'Information bits' (112) to the TX radio subsystem's 'Channel Encoding' block. The Voice Activity Detector outputs an 'SP flag' (1) to the TX radio subsystem's 'SP flag monitoring' block. The Comfort Noise Computation block is present but not connected to the radio subsystem.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+```
+
+graph LR
+    subgraph TX_DTX_handler [TX DTX handler]
+        SE[Speech encoder]
+        VAD[Voice Activity Detector]
+        CNC[Comfort Noise Computation]
+    end
+    SE -- "Information bits  
+112" --> CE[Channel Encoding]
+    VAD -- "SP flag  
+1" --> SFM[SP flag monitoring]
+    subgraph TX_radio_subsystem [TX radio subsystem]
+        CE
+        SFM
+    end
+  
+```
+
+Block diagram of the transmit side DTX functions. The TX DTX handler contains three sub-blocks: Speech encoder, Voice Activity Detector, and Comfort Noise Computation. The Speech encoder outputs 'Information bits' (112) to the TX radio subsystem's 'Channel Encoding' block. The Voice Activity Detector outputs an 'SP flag' (1) to the TX radio subsystem's 'SP flag monitoring' block. The Comfort Noise Computation block is present but not connected to the radio subsystem.
+
+Figure 1: Block diagram of the transmit side DTX functions
+
+## 5.1 General Operation
+
+The TX DTX handler continuously passes traffic frames, individually marked by the SP flag, to the RSS. This binary flag is redundant to the Silence Descriptor (SID) code word labelling. SP flag = "1" indicates a speech frame, SP flag = "0" a SID frame.
+
+The scheduling of the frames for transmission on the air interface is controlled by the RSS alone, on the basis of the SP flag as described in clause 5.1.1.
+
+### 5.1.1 Functions of the TX DTX handler
+
+To allow verification of the TX DTX handler functions, all frames before the reset of the system are treated as if they were speech frames of an infinitely long time. Therefore, the first 7 frames after the reset are marked with SP flag = "1", even if VAD flag = "0" (hangover period, see figure 2).
+
+The VAD shall operate all the time in order to assess whether the input signal contains speech or not. The output is a binary flag (VAD flag = "1" or VAD flag = "0", respectively) on a frame by frame basis (see GSM 06.42 [9]).
+
+The VAD flag controls indirectly, via the TX DTX handler operations described below, the overall DTX operation on the TX side.
+
+Whenever the VAD flag = "1", the speech encoder output frame shall be passed directly to the RSS, marked with SP flag = "1".
+
+At the end of a speech burst (transition VAD flag = "1" to VAD flag = "0"), it takes 8 consecutive frames to make a new updated SID frame available (see GSM 06.22 [8]). Normally, the first 7 speech encoder output frames after the end of the speech burst shall therefore be passed directly to the RSS, marked with SP flag = "1" ("hangover period"). The first new SID frame is then passed to the RSS as frame 8 after the end of the speech burst, marked with SP flag = "0" (see figure 2).
+
+![Figure 2: Normal hangover procedure (N_elapsed > 23). The diagram illustrates the timing of VAD, SP, and SID flags across a sequence of frames. The VAD flag shows the transition from speech to pause. The SP flag shows a 'hangover' period. The N_elapsed counter tracks frames since the last SID frame. The bottom row shows the sequence of frames: Speech, Speech, Speech, Speech, Speech, SID k+1, SID k+2. Arrows indicate the SID averaging periods for R0 and LPC coefficients.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+The diagram shows the following sequence of events and flags across frames:
+
+- VAD Flag:** Shows the transition from a speech burst to a pause. Labels include "last 'speech' frame", "end of speech burst", and "first 'pause' frame".
+- SP Flag:** Shows a "hangover" period (GS averaging period) following the end of the speech burst.
+- N<sub>elapsed</sub>:** A counter tracking frames since the last SID frame. The sequence shown is: e.g. 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 0, 0, 0.
+- Frames to RSS:** A sequence of frames containing "Speech" and "SID" frames (SID k+1, SID k+2). Arrows indicate "SID averaging periods (averaging periods of R0 and LPC coefficients)".
+- Frame Duration:** A single frame is labeled as "Frame (20 ms)".
+
+Figure 2: Normal hangover procedure (N\_elapsed > 23). The diagram illustrates the timing of VAD, SP, and SID flags across a sequence of frames. The VAD flag shows the transition from speech to pause. The SP flag shows a 'hangover' period. The N\_elapsed counter tracks frames since the last SID frame. The bottom row shows the sequence of frames: Speech, Speech, Speech, Speech, Speech, SID k+1, SID k+2. Arrows indicate the SID averaging periods for R0 and LPC coefficients.
+
+**Figure 2: Normal hangover procedure ( $N_{\text{elapsed}} > 23$ )**
+
+If, however, at the end of the speech burst, less than 24 frames have elapsed since the last SID frame was computed and passed to the RSS, then this last SID frame shall repeatedly be passed to the RSS, until a new updated SID frame is available (8 consecutive frames marked with VAD flag = "0"). This reduces the activity on the air interface in cases where short background noise spikes are taken for speech, by avoiding the "hangover" waiting for the SID frame computation (see figure 3).
+
+NOTE: Figure 3 shows an example of the longest possible speech burst without hangover.
+
+Once the first SID frame after the end of a speech burst has been computed and passed to the RSS, the TX DTX Handler shall continuously compute and pass updated SID frames to the RSS, marked with SP flag = "0" as long as the VAD flag = "0".
+
+The speech encoder is operated in full speech modality if SP flag = "1" and in a simplified mode if SP flag = "0", because not all encoder functions are required for the evaluation of comfort noise parameters (see GSM 06.22 [8]).
+
+### 5.1.2 Functions of the TX radio subsystem
+
+The following traffic frames shall be scheduled for transmission:
+
+- all frames marked with SP flag = "1";
+- the first one with SP flag = "0" after one or more frames with SP flag = "1";
+- those marked with SP flag = "0" and aligned with the Slow Associated Control CHannel (SACCH) multiframe structure as described in GSM 05.08 [4].
+
+This has the overall function, that the radio transmission is turned off after the transmission of a SID frame when the speaker stops talking. During speech pauses, the transmission is resumed at regular intervals for transmission of one SID frame, in order to update the generated comfort noise on the RX side (and to improve the measurement of the link quality by the RSS).
+
+If a SID frame (SP flag = "0"), scheduled for transmission is stolen for Fast Associated Control CHannel (FACCH) signalling purposes, then the subsequent frame shall be scheduled for transmission instead.
+
+![Timing diagram for SID update logic. It shows VAD and SP flags over time, a table of Frames to RSS with SID values, and periods for SID averaging and updating.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+The diagram illustrates the timing for updating the Spectral Inverse Distortion (SID) parameters based on Voice Activity Detection (VAD) and Speech Presence (SP) flags.
+
+**Top Section: Flag Timing**
+
+- VAD Flag:** Shows a pulse indicating the "end of speech burst".
+- SP Flag:** Shows a pulse indicating speech presence.
+- Frame:** A 20 ms duration frame is highlighted.
+
+**Bottom Section: SID Update Logic**
+
+The logic is based on the following table of Frames to RSS and their associated SID values:
+
+|               |   |   |   |                  |        |        |                  |                  |                  |                  |                  |                  |        |                  |                  |                  |                  |                    |                    |  |
+|---------------|---|---|---|------------------|--------|--------|------------------|------------------|------------------|------------------|------------------|------------------|--------|------------------|------------------|------------------|------------------|--------------------|--------------------|--|
+| Frames to RSS | ? | ? | ? | 0                | 1      | 2      | 3                | 4                | 5                | 6                | 7                | 8                | ...    | 22               | 23               | 24...            | 28               | 29                 | 0                  |  |
+| SID           | ? | ? | ? | SID <sub>k</sub> | Speech | Speech | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | Speech | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k</sub> | SID <sub>k+1</sub> | SID <sub>k+1</sub> |  |
+
+**Timing Periods:**
+
+- SID averaging period:** Occurs during the initial frames (columns 1-3).
+- repeat previous SID:** Occurs when the SP flag is active (columns 5-8).
+- SID averaging period:** Occurs again during the burst end (columns 22-28).
+- new (updated) SID:** The updated SID<sub>k+1</sub> is applied starting at frame 0.
+
+Timing diagram for SID update logic. It shows VAD and SP flags over time, a table of Frames to RSS with SID values, and periods for SID averaging and updating.
+
+Figure 3: Handling of short speech bursts for  $N_{\text{elapsed}} < 24$  (An example)
+
+# 6 Receive (RX) side
+
+A block diagram of the RX side DTX functions is shown in figure 4.
+
+![Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX DTX handler contains three sub-blocks: Speech decoder, Comfort Noise Generation, and Error Concealment. The RX radio subsystem contains two sub-blocks: Error Correction & Detection and SID frame detection. Arrows indicate data flow from the RX radio subsystem to the RX DTX handler. The data is labeled 'Information bits' and includes: 112 (to Speech decoder), BFI (to Comfort Noise Generation), UFI (to Comfort Noise Generation), SID (to Error Concealment), and TAF (to Error Concealment).](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+Block diagram of the receive side DTX functions. The diagram shows two main components: RX DTX handler and RX radio subsystem. The RX DTX handler contains three sub-blocks: Speech decoder, Comfort Noise Generation, and Error Concealment. The RX radio subsystem contains two sub-blocks: Error Correction & Detection and SID frame detection. Arrows indicate data flow from the RX radio subsystem to the RX DTX handler. The data is labeled 'Information bits' and includes: 112 (to Speech decoder), BFI (to Comfort Noise Generation), UFI (to Comfort Noise Generation), SID (to Error Concealment), and TAF (to Error Concealment).
+
+Figure 4: Block diagram of the receive side DTX functions
+
+## 6.1 General operation
+
+Whatever their context (speech, SID, FACCH or none), the RSS continuously passes the received traffic frames to the RX DTX handler, individually marked by various pre-processing functions with 4 flags. These are the Bad Frame Indicator (BFI) flag, the Unreliable Frame Indicator (UFI) flag, the SIlence Descriptor (SID) flag and the Time Alignment Flag (TAF) described in clause 6.1.1 and table 1, which serve to classify the traffic frame according to the list of terms defined in clause 3.1. This classification, summarised in table 1, allows the RX DTX handler to determine how the received frame is to be handled.
+
+Table 1 Classification of traffic frames
+
+| BFI "OR" UFI* | SID               |   |                   |
+|---------------|-------------------|---|-------------------|
+|               | 2                 | 1 | 0                 |
+| 0             | Valid SID frame   |   | Good speech frame |
+| 1             | Invalid SID frame |   | Unusable frame    |
+
+\* BFI "OR" UFI indicates a logical OR combination of the BFI and UFI flags.
+
+NOTE: The SID computation is left open to manufacturers with the constraint to meet the performance requirements given in the GSM 05.05 [3]. An example solution is given in the C-code (GSM 06.06 [11]).
+
+### 6.1.1 Functions of the RX radio subsystem
+
+The binary BFI flag (see GSM 05.05 [3]) indicates whether the traffic frame is considered to contain meaningful information bits (BFI flag = "0") or not (BFI flag = "1"). In the context of the present document, a FACCH frame is considered not to contain meaningful bits and shall be marked with BFI flag = "1". The BFI flag shall fulfil the performance requirements of GSM 05.05 [3].
+
+NOTE: That the BFI flag, which is generated by the channel error correction scheme, will in some cases be modified by the SID frame detection unit.
+
+The UFI flag is the output of the Forward Error Correction (FEC) procedure and give indications about the channel performance. The UFI flag shall fulfil the performance requirements of GSM 05.05 [3].
+
+The SID frame detector compares bit by bit the relevant bits of the received traffic frame (the SID field) with the SID code word defined in GSM 06.22 [8] and gives back the ternary SID flag. The SID flag shall fulfil the performance requirements of GSM 05.05 [3]. The binary TAF flag marks with TAF = "1" those traffic frames that are aligned with the SACCH multiframe structure as described in GSM 05.08 [4].
+
+### 6.1.2 Functions of the RX DTX handler
+
+The RX DTX handler shall be responsible for the overall DTX operation on the RX side.
+
+The DTX operation on the RX side shall be as follows:
+
+- whenever a good speech frame is detected, the DTX Handler shall pass it directly on to the speech decoder;
+- when lost speech or lost SID frames are detected, the substitution and muting procedure defined in GSM 06.21 [7] shall be applied;
+- valid SID frames shall result in comfort noise generation, as defined in GSM 06.22 [8], until the next SID frame is expected (TAF="1") or good speech frames are detected. During this period, the RX DTX handler shall ignore any unusable frames delivered by the RSS;
+- an invalid SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied.
+
+NOTE: If the first SID frame after a speech burst (a series of good speech frames) is invalid, then the comfort noise parameters can be taken from the last valid SID frame or, if the series of good speech frames received was longer than 30 (23+7), from the last received good speech frame which, because of the VAD hangover time (see GSM 06.42 [9]), may be supposed to contain noise only.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#13         |           |         |                  | 4.0.2       | ETSI Publication                        |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                    |
+| SMG#23         | 430/97    | A001    |                  | 5.1.1       | UAP 60                                  |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+|                |           |         |                  | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46042/raw.md b/marked/Rel-16/46_series/46042/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..47594f7bd8b46772045bfb64fddff933e2a91682
--- /dev/null
+++ b/marked/Rel-16/46_series/46042/raw.md
@@ -0,0 +1,654 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                         |           |
+|-------------------------------------------------------------------------|-----------|
+| Foreword .....                                                          | 4         |
+| 1 Scope.....                                                            | 5         |
+| 2 References.....                                                       | 5         |
+| 3 Definitions, symbols and abbreviations .....                          | 5         |
+| 3.1 Definitions.....                                                    | 5         |
+| 3.2 Symbols.....                                                        | 6         |
+| 3.2.1 Variables.....                                                    | 6         |
+| 3.2.2 Constants .....                                                   | 6         |
+| 3.2.3 Functions .....                                                   | 7         |
+| 3.3 Abbreviations .....                                                 | 7         |
+| 4 General.....                                                          | 7         |
+| 5 Functional description.....                                           | 7         |
+| 5.1 Overview and principles of operation .....                          | 8         |
+| 5.2 Algorithm description .....                                         | 8         |
+| 5.2.1 Adaptive filtering and energy computation .....                   | 9         |
+| 5.2.2 ACF averaging.....                                                | 9         |
+| 5.2.3 Predictor values computation .....                                | 10        |
+| 5.2.4 Spectral comparison .....                                         | 10        |
+| 5.2.5 Information tone detection .....                                  | 11        |
+| 5.2.6 Threshold adaptation .....                                        | 11        |
+| 5.2.7 VAD decision .....                                                | 14        |
+| 5.2.8 VAD hangover addition .....                                       | 14        |
+| 5.2.9 Periodicity detection.....                                        | 14        |
+| 6 Computational description overview .....                              | 15        |
+| 6.1 VAD modules.....                                                    | 15        |
+| 6.2 Pseudo-floating point arithmetic .....                              | 15        |
+| <b>Annex A (informative): VAD performance .....</b>                     | <b>17</b> |
+| <b>Annex B (informative): Simplified block filtering operation.....</b> | <b>18</b> |
+| <b>Annex C (informative): Pole frequency calculation.....</b>           | <b>19</b> |
+| <b>Annex D (informative): Change history.....</b>                       | <b>20</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) within the digital cellular telecommunications system. The present document is part of a series covering the half rate speech traffic channels as described below:
+
+- GSM 06.02 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- GSM 06.06 "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- GSM 06.07 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- GSM 06.20 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- GSM 06.21 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels".
+- GSM 06.22 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- GSM 06.41 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- GSM 06.42 "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.41 [4]. It also specifies the test methods to be used to verify that a VAD implementation complies with the present document.
+
+The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half-rate GSM speech traffic channel.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [3] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+- [4] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [5] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI C code for the GSM half rate speech codec".
+- [6] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**mobile environment:** any environment in which MSs may be used.
+
+**noise:** signal component resulting from acoustic environmental noise.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+### 3.2.1 Variables
+
+|            |                                                                          |
+|------------|--------------------------------------------------------------------------|
+| aav1       | filter predictor values, see clause 5.2.3                                |
+| acf        | the ACF vector which is calculated in the speech encoder (GSM 06.20 [2]) |
+| adaptcount | secondary hangover counter, see clause 5.2.6                             |
+| av0        | averaged ACF vector, see clause 5.2.2                                    |
+
+|                 |                                                                                                         |
+|-----------------|---------------------------------------------------------------------------------------------------------|
+| av1             | a previous value of av0, see clause 5.2.2                                                               |
+| burstcount      | speech burst length counter, see clause 5.2.7                                                           |
+| den             | denominator of left hand side of equation 8 in annex C, see clause 5.2.5                                |
+| difference      | difference between consecutive values of dm, see clause 5.2.4                                           |
+| dm              | spectral distortion measure, see clause 5.2.4                                                           |
+| hangcount       | primary hangover counter, see clause 5.2.7                                                              |
+| lagcount        | number of subframes in current frame meeting periodicity criterion, see clause 5.2.9                    |
+| lastdm          | previous value of dm, see clause 5.2.4                                                                  |
+| lags            | the open loop long term predictor lags for the four speech encoder subframes (GSM 06.20 [2].)           |
+| num             | numerator of left hand side of equation 8 in annex C, see clause 5.2.5                                  |
+| oldlagcount     | previous value of lagcount, see clause 5.2.9                                                            |
+| prederr         | fourth order short term prediction error, see clause 5.2.5                                              |
+| ptch            | Boolean flag indicating the presence of a periodic signal component, see clause 5.2.9                   |
+| pvad            | energy in the current filtered signal frame, see clause 5.2.1                                           |
+| rav1            | autocorrelation vector obtained from av1, see clause 5.2.3                                              |
+| rc              | the first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.20 [2])     |
+| rvad            | autocorrelation vector of the adaptive filter predictor values, see clause 5.2.6                        |
+| smalllag        | difference between consecutive lag values, see clause 5.2.9                                             |
+| stat            | Boolean flag indicating that the frequency spectrum of the input signal is stationary, see clause 5.2.4 |
+| thvad           | adaptive primary VAD threshold, see clause 5.2.6                                                        |
+| tone            | Boolean flag indicating the presence of an information tone, see clause 5.2.5                           |
+| vadflag         | Boolean VAD decision with hangover included, see clause 5.2.8                                           |
+| veryoldlagcount | previous value of oldlagcount, see clause 5.2.9                                                         |
+| vvad            | Boolean VAD decision before hangover, see clause 5.2.7                                                  |
+
+### 3.2.2 Constants
+
+|            |                                                                             |
+|------------|-----------------------------------------------------------------------------|
+| adp        | number of frames of hangover for secondary VAD, see clause 5.2.6            |
+| burstconst | minimum length of speech burst to which hangover is added, see clause 5.2.8 |
+| dec        | determines rate of decrease in adaptive threshold, see clause 5.2.6         |
+| fac        | determines steady state adaptive threshold, see clause 5.2.6                |
+| frames     | number of frames over which av0 and av1 are calculated, see clause 5.2.2    |
+| freqth     | threshold for pole frequency decision, see clause 5.2.5                     |
+| hangconst  | number of frames of hangover for primary VAD, see clause 5.2.8              |
+| inc        | determines rate of increase in adaptive threshold, see clause 5.2.6         |
+| lthresh    | lag difference threshold for periodicity decision, see clause 5.2.9         |
+| margin     | determines upper limit for adaptive threshold, see clause 5.2.6             |
+| nthresh    | frame count threshold for periodicity decision, see clause 5.2.9            |
+| plev       | lower limit for adaptive threshold, see clause 5.2.6                        |
+| predth     | threshold for short term prediction error, see clause 5.2.5                 |
+| pth        | energy threshold, see clause 5.2.6                                          |
+| thresh     | decision threshold for evaluation of stat flag, clause 5.2.4                |
+
+### 3.2.3 Functions
+
+|                   |                                             |
+|-------------------|---------------------------------------------|
+| +                 | addition                                    |
+| -                 | subtraction                                 |
+| *                 | multiplication                              |
+| /                 | division                                    |
+| x                 | absolute value of x                         |
+| AND               | Boolean AND                                 |
+| OR                | Boolean OR                                  |
+| b                 |                                             |
+| MULT(x(i))<br>i=a | the product of the series x(i) for i=a to b |
+
+b  
+SUM(x(i))      the sum of the series x(i) for i=a to b  
+i=a
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                               |
+|-------|-----------------------------------------------|
+| ACF   | Autocorrelation Function                      |
+| AFLAT | Autocorrelation Fixed point LAttice Technique |
+| ANSI  | American National Standards Institute         |
+| DTX   | Discontinuous Transmission                    |
+| LTP   | Long Term Predictor                           |
+| TX    | Transmission                                  |
+| VAD   | Voice Activity Detector                       |
+
+For abbreviations not given in this clause see GSM 01.04 [1].
+
+# --- 4 General
+
+The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a Boolean flag (vadflag) which is used by the Transmit (TX) DTX handler defined in GSM 06.41 [4].
+
+The present document is organized as follows.
+
+Clause 5 describes the principles of operation of the VAD. Clause 6 provides an overview of the computational description of the VAD. The computational details necessary for the fixed point implementation of the VAD algorithm are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.06 [5].
+
+The verification of the VAD is based on the use of digital test sequences which are described in GSM 06.07 [6].
+
+The performance of the VAD algorithm is characterized by the amount of audible speech clipping it introduces and the percentage activity it indicates. The characteristics for the VAD defined in the present document have been established by extensive testing under a wide range of operating conditions. The results are summarized in annex A.
+
+# --- 5 Functional description
+
+The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas GSM 06.06 [5] contains the fixed point computational description of the VAD. In the case of discrepancy between the two descriptions, the description in GSM 06.06 [5] will prevail.
+
+## 5.1 Overview and principles of operation
+
+The function of the VAD is to distinguish between noise with speech present and noise without speech present. This is achieved by comparing the energy of a filtered version of the input signal with a threshold. The presence of speech is indicated whenever the threshold is exceeded.
+
+The detection of speech in mobile environments is difficult due to the low speech/noise ratios which are encountered, particularly in moving vehicles. To increase the probability of detecting speech, the input signal is adaptively filtered (see clause 5.2.1) to reduce its noise content before the voice activity decision is made (see clause 5.2.7).
+
+The frequency spectrum and level of the noise may vary within a given environment as well as between different environments. It is therefore necessary to adapt the input filter coefficients and energy threshold at regular intervals as described in clause 5.2.6.
+
+## 5.2 Algorithm description
+
+The block diagram of the VAD algorithm is shown in figure 1. The individual blocks are described in the following clauses. The global variables shown in the block diagram are described in table 1.
+
+**Table 1: Description of variables in figure 1**
+
+| Var     | Description                                                                                          |
+|---------|------------------------------------------------------------------------------------------------------|
+| acf     | The ACF vector which is calculated in the speech encoder (GSM 06.20 [2]).                            |
+| av0     | Averaged ACF vector.                                                                                 |
+| av1     | A previous value of av0.                                                                             |
+| lags    | The open loop long term predictor lags for the four speech encoder subframes (GSM 06.20 [2]).        |
+| ptch    | Boolean flag indicating the presence of a periodic signal component.                                 |
+| pvad    | Energy in the current filtered signal frame.                                                         |
+| rav1    | Autocorrelation vector obtained from av1.                                                            |
+| rc      | The first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.20 [2]). |
+| rvad    | Autocorrelation vector of the adaptive filter predictor values.                                      |
+| stat    | Boolean flag indicating that the frequency spectrum of the input signal is stationary.               |
+| thvad   | Adaptive primary VAD threshold.                                                                      |
+| tone    | Boolean flag indicating the presence of an information tone.                                         |
+| vadflag | Boolean VAD decision with hangover included.                                                         |
+| vvad    | Boolean VAD decision before hangover.                                                                |
+
+![Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to produce the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows with variable names like pvad, ptch, tone, r_vad, r_acf1, av0, av1, stat, th_vad, v_vad, and vadflag.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg)
+
+```
+
+graph LR
+    acf --> AFE[Adaptive filtering and energy computation]
+    lags --> PD[Periodicity detection]
+    rc --> TD[Tone detection]
+    acf --> AVC[ACF averaging]
+    acf --> PVE[Predictor values computation]
+    PD -- ptch --> TA[Threshold adaptation]
+    TD -- tone --> TA
+    AVC -- av0 --> SC[Spectral comparison]
+    AVC -- av1 --> PVE
+    PVE -- r_acf1 --> SC
+    PVE -- r_vad --> TA
+    SC -- stat --> TA
+    AFE -- pvad --> VD[VAD decision]
+    AFE -- th_vad --> TA
+    TA -- th_vad --> VD
+    VD -- v_vad --> VHA[VAD hangover addition]
+    VHA -- vadflag --> Output[vadflag]
+  
+```
+
+Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to produce the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows with variable names like pvad, ptch, tone, r\_vad, r\_acf1, av0, av1, stat, th\_vad, v\_vad, and vadflag.
+
+**Figure 1: Functional block diagram of the VAD**
+
+### 5.2.1 Adaptive filtering and energy computation
+
+The energy in the current filtered signal frame (pvad) is computed as follows:
+
+$$pvad = rvad[0]*acf[0] + 2*SUM_{i=1}^8 (rvad[i]*acf[i])$$
+
+This corresponds to performing an 8th order block filtering on the filtered input samples to the speech encoder. This is explained in annex B.
+
+### 5.2.2 ACF averaging
+
+Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the ACF (autocorrelation function) vectors for several consecutive frames. The averaging is given by the following equations:
+
+$$\begin{aligned} av0\{n\}[i] &= \sum_{j=0}^{frames-1} (acf\{n-j\}[i]) & ; \quad i = 0..8 \\ av1\{n\}[i] &= av0\{n-frames\}[i] & ; \quad i = 0..8 \end{aligned}$$
+
+where (n) represents the current frame, (n-1) represents the previous frame etc. The values of the constants and initial variable values are given in table 2.
+
+**Table 2: Constants and variables for ACF averaging**
+
+| Constant | Value | Variable                  | Initial value |
+|----------|-------|---------------------------|---------------|
+| frames   | 4     | previous ACF's, av0 & av1 | All set to 0  |
+
+### 5.2.3 Predictor values computation
+
+The filter predictor values aav1 are obtained from the autocorrelation values av1 according to the equation:
+
+$$a = R^{-1} p$$
+
+where:
+
+$$R = \begin{bmatrix} av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] & av1[6] & av1[7] \\ av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] & av1[6] \\ av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] & av1[5] \\ av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] & av1[4] \\ av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] & av1[3] \\ av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] & av1[2] \\ av1[6] & av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] & av1[1] \\ av1[7] & av1[6] & av1[5] & av1[4] & av1[3] & av1[2] & av1[1] & av1[0] \end{bmatrix}$$
+
+and:
+
+$$p = \begin{bmatrix} av1[1] \\ av1[2] \\ av1[3] \\ av1[4] \\ av1[5] \\ av1[6] \\ av1[7] \\ av1[8] \end{bmatrix} \quad a = \begin{bmatrix} aav1[1] \\ aav1[2] \\ aav1[3] \\ aav1[4] \\ aav1[5] \\ aav1[6] \\ aav1[7] \\ aav1[8] \end{bmatrix}$$
+
+$$aav1[0] = -1$$
+
+av1 is used in preference to av0 as the latter may contain speech. The autocorrelated predictor values rav1 are then obtained:
+
+$$rav1[i] = \sum_{k=0}^{8-i} (aav1[k] * aav1[k+i]) \quad ; \quad i = 0..8$$
+
+### 5.2.4 Spectral comparison
+
+The spectra represented by the autocorrelated predictor values  $ra1$  and the averaged autocorrelation values  $av0$  are compared using the distortion measure ( $dm$ ), defined below. This measure is used to produce a Boolean value  $stat$  every 20 ms, as shown in the following equations:
+
+$$dm = (ra1[0]*av0[0] + 2*SUM_{i=1}^8 (ra1[i]*av0[i])) / av0[0]$$
+
+```
+
+difference = | dm - lastdm |
+lastdm = dm
+stat = (difference < thresh)
+  
+```
+
+The values of the constants and initial variable values are given in table 3.
+
+**Table 3: Constants and variables for spectral comparison**
+
+| Constant | Value | Variable | Initial value |
+|----------|-------|----------|---------------|
+| thresh   | 0,068 | lastdm   | 0             |
+
+### 5.2.5 Information tone detection
+
+Information tones and noise can be classified by inspecting the short term prediction gain, information tones resulting in a higher prediction gain than noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for noise.
+
+The prediction gain decision is implemented by comparing the normalized short term prediction error with the short term prediction error threshold ( $predth$ ). This measure is used to produce a Boolean value,  $tone$ , every 20 ms. The signal is classified as a tone if the prediction error is less than  $predth$ . This is equivalent to a prediction gain threshold of 13,5 dB.
+
+Vehicle noise can contain strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz.
+
+The algorithm for evaluating the Boolean tone flag is as follows:
+
+```
+
+tone = false
+
+den = a[1]*a[1]
+num = 4*a[2] - a[1]*a[1]
+
+if (num <= 0)
+    return
+
+if ((a[1] < 0) AND (num/den < freqth))
+    return
+
+prederr = MULT_{i=1}^4 (1 - rc[i]*rc[i])
+
+if (prederr < predth)
+    tone = true
+
+return
+  
+```
+
+$rc[1..4]$  are the first four unquantized reflection coefficients obtained from the speech encoder short term predictor. The coefficients  $a[0..2]$  are transversal filter coefficients calculated from  $rc[1..2]$ . The pole frequency calculation is described in annex C.
+
+The values of the constants are given in table 4.
+
+**Table 4: Constants for information tone detection**
+
+| Constant | Value  |
+|----------|--------|
+| freqth   | 0,0973 |
+| predth   | 0,0447 |
+
+### 5.2.6 Threshold adaptation
+
+A check is made every 20 ms to determine whether the adaptive primary VAD threshold, (thvad) should be changed. This adaptation is carried out according to the flow chart in figure 2. The values of the constants and initial variable values are given in table 5.
+
+Adaptation of thvad takes place in two different situations:
+
+In the first case, the decision threshold (thvad) is set to the lower limit for the adaptive threshold (plev) if the input signal frame energy (acf[0]) is less than the energy threshold (pth). The autocorrelation vector of the adaptive filter predictor values (rvad) remains unchanged.
+
+In the second case, thvad and rvad are adapted if there is a low probability that speech or information tones are present. This occurs when the following conditions are met:
+
+- a) the frequency spectrum of the input signal is stationary (clause 5.2.4);
+- b) the signal does not contain a periodic component (clause 5.2.9);
+- c) information tones are not present (clause 5.2.5).
+
+The autocorrelation vector of the adaptive filter predictor values (rvad) is updated with the rav1 values. The step size by which thvad is adapted is not constant but a proportion of the current value and its rate of increase or decrease is determined by constants inc and dec respectively.
+
+The adaptation begins by experimentally multiplying thvad by a factor of  $(1 - 1/\text{dec})$ . If thvad is now higher than or equal to pvad times, the steady state adaptive threshold constant (fac), then thvad needed to be decreased and it is left at this new lower level. If, on the other hand, thvad is less than pvad times fac, then it either needs to be increased or kept constant. In this case, it is multiplied by a factor of  $(1 + 1/\text{inc})$  or set to pvad times fac whichever yields the lower value. thvad is never allowed to be greater than pvad+upper adaptive threshold limit (margin).
+
+**Table 5: Constants and variables threshold adaptation**
+
+| Constant | Value  | Variable   | Initial value |
+|----------|--------|------------|---------------|
+| pth      | 210000 | margin     | 112000000     |
+| plev     | 560000 | adaptcount | 0             |
+| fac      | 2,55   | thvad      | 1400000       |
+| adp      | 8      | rvad[0]    | 6             |
+| inc      | 16     | rvad[1] to | All 0         |
+| dec      | 32     | rvad[8]    |               |
+
+![Flow diagram for threshold adaptation](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph TD; BEGIN --> D1{acf[0] < pth?}; D1 -- yes --> P1[th_vad = plev]; D1 -- no --> D2{stat and not ptch and not tone?}; D2 -- yes --> P2[increment adaptcount]; D2 -- no --> P3[adaptcount = 0]; P2 --> D3{adaptcount > adp?}; P3 --> D3; D3 -- yes --> P4[th_vad = th_vad - th_vad / dec]; D3 -- no --> END1[END]; P4 --> D4{th_vad < pvad * fac?}; D4 -- yes --> P5[th_vad = min(th_vad + th_vad / inc, pvad * fac)]; D4 -- no --> D5{th_vad > pvad + margin?}; P5 --> D5; D5 -- yes --> P6[th_vad = pvad + margin]; D5 -- no --> P7[r_vad = r_av1]; P6 --> P7; P7 --> P8[adaptcount = adp + 1]; P8 --> END2[END];
+```
+
+The flow diagram for threshold adaptation starts with 'BEGIN' and proceeds to a decision diamond 'acf[0] < pth?'. If 'yes', it goes to 'th\_vad = plev'. If 'no', it goes to 'stat and not ptch and not tone?'. If 'yes', it goes to 'increment adaptcount'. If 'no', it goes to 'adaptcount = 0'. Both 'increment adaptcount' and 'adaptcount = 0' lead to 'adaptcount > adp?'. If 'yes', it goes to 'th\_vad = th\_vad - th\_vad / dec'. If 'no', it ends. 'th\_vad = th\_vad - th\_vad / dec' leads to 'th\_vad < pvad \* fac?'. If 'yes', it goes to 'th\_vad = min(th\_vad + th\_vad / inc, pvad \* fac)'. If 'no', it goes to 'th\_vad > pvad + margin?'. 'th\_vad = min(th\_vad + th\_vad / inc, pvad \* fac)' also leads to 'th\_vad > pvad + margin?'. If 'yes', it goes to 'th\_vad = pvad + margin'. If 'no', it goes to 'r\_vad = r\_av1'. 'th\_vad = pvad + margin' also leads to 'r\_vad = r\_av1'. 'r\_vad = r\_av1' leads to 'adaptcount = adp + 1', which ends.
+
+Flow diagram for threshold adaptation
+
+Figure 2: Flow diagram for threshold adaptation
+
+### 5.2.7 VAD decision
+
+Prior to hangover the Boolean VAD decision is defined as:
+
+```
+vvad = (pvad > thvad)
+```
+
+### 5.2.8 VAD hangover addition
+
+VAD hangover is only added to bursts of speech greater than or equal to burstcount blocks. The Boolean variable vadflag indicates the decision of the VAD with hangover included. The values of the constants and initial variable values are given in table 6. The hangover algorithm is as follows:
+
+```
+if (vvad)
+    increment(burstcount)
+else
+    burstcount = 0
+
+if (burstcount >= burstconst)
+{
+    hangcount = hangconst
+    burstcount = burstconst
+}
+
+vadflag = (vvad OR (hangcount >= 0))
+
+if (hangcount >= 0)
+    decrement(hangcount)
+```
+
+**Table 6: Constants and variables for VAD hangover addition**
+
+| Constant   | Value | Variable   | Initial value |
+|------------|-------|------------|---------------|
+| burstconst | 3     | burstcount | 0             |
+| hangconst  | 5     | hangcount  | -1            |
+
+### 5.2.9 Periodicity detection
+
+thvad and rvad are updated when the frequency spectrum of the input signal is stationary. However, vowel sounds also have a stationary frequency spectrum. The Boolean variable ptch indicates the presence of a periodic signal component and prevents adaptation of thvad and rvad. ptch is updated every 20 ms and is true when periodicity (a vowel sound) is detected. The periodicity detector identifies the vowel sounds by comparing consecutive Long Term Predictor (LTP) lag values lags[1..4] which are obtained every sub frame from the speech codec defined in GSM 06.20 [2]. Cases in which one lag value is a factor of the other are catered for. However, consecutive lags with a ratio which is either non-integer or greater than 3 are not classified as periodic.
+
+```
+lagcount = 0
+
+for ( j=1; j<=4; j++ )
+{
+    smalllag=maximum(lags[j], lags[j-1])
+    for ( i=1; i<=3; i++ )
+        if (smalllag >= minimum(lags[i], lags[i-1]))
+            smalllag = smalllag - minimum(lags[i], lags[i-1])
+    if (minimum(smalllag, minimum(lags[j], lags[j-1]) - smalllag) < lthresh)
+        increment(lagcount)
+}
+
+veryoldlagcount = oldlagcount
+oldlagcount = lagcount
+
+ptch = (oldlagcount + veryoldlagcount >= nthresh)
+```
+
+The values of constants and initial values are given in table 7. lags[0] = lags[4] of the previous frame.
+
+ptch is calculated after the VAD decision and when the current LTP lag values lags[1..4] are available. This reduces the delay of the VAD decision.
+
+**Table 7: Constants and variables for periodicity detection**
+
+| Constant | Value | Variable        | Initial value |
+|----------|-------|-----------------|---------------|
+| lthresh  | 2     | ptch            | 1             |
+| nthresh  | 7     | oldlagcount     | 0             |
+|          |       | veryoldlagcount | 0             |
+|          |       | lags[0]         | 21            |
+
+# 6 Computational description overview
+
+The computational details necessary for the fixed point implementation of the speech transcoding and DTX functions are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.06 [5]. This clause provides an overview of the modules which describe the computation of the VAD algorithm.
+
+## 6.1 VAD modules
+
+The computational description of the VAD is divided into three ANSI C modules. These modules are:
+
+- vad\_reset;
+- vad\_algorithm;
+- periodicity\_update.
+
+The vad\_reset module sets the VAD variables to their initial values.
+
+The vad\_algorithm module is divided into nine sub-modules which correspond to the blocks of figure 1 in the high level description of the VAD algorithm. The vad\_algorithm module can be called as soon as the acf[0..8] and rc[1..4] variables are known. This means that the VAD computation can take place after the Autocorrelation Fixed point LAttice Technique (AFLAT) routine in the speech encoder (GSM 06.20 [2]). The vad\_algorithm module also requires the value of the ptch variable calculated in the previous frame.
+
+The ptch variable is calculated by the periodicity\_update module from the lags[1..4] variable. The individual lag values are calculated for each subframe in the LTP routine of the speech encoder (GSM 06.20 [2]). The periodicity\_update module is called after the current 20 ms signal frame has been encoded.
+
+## 6.2 Pseudo-floating point arithmetic
+
+All the arithmetic operations follow the precision and format used in the computational description of the speech codec in GSM 06.06 [5]. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This applies to the following variables (and related constants) of the VAD algorithm:
+
+- **pvad:** Energy of filtered signal;
+- **thvad:** Threshold of the VAD decision;
+- **acf0:** Energy of the input signal.
+
+For the representation of these variables, two 16-bit integers are needed:
+
+- one for the exponent (e\_pvad, e\_thvad, e\_acf0);
+- one for the mantissa (m\_pvad, m\_thvad, m\_acf0).
+
+The value e\_pvad represents the lowest power of 2 just greater or equal to the actual value of pvad, and the m\_pvad value represents an integer which is always greater than or equal to 16384 (normalized mantissa). It means that the pvad value is equal to
+
+$$\text{pvad} = 2^{e\_pvad} * (m\_pvad/32768)$$
+
+This scheme provides a large dynamic range for the pvad value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables, and the VAD algorithm needs only one
+
+pseudo floating point addition and multiplication. All the computations related to the pseudo-floating point variables require simple 16 or 32-bit arithmetic operations defined in the detailed description of the speech codec.
+
+Some constants, represented by a floating point format, are needed and symbolic names (in capital letters) for their exponent and mantissa are used; table 8 lists all these constants with the associated symbolic names and their numerical constant values.
+
+**Table 8: List of floating point constants**
+
+| <b>Constant</b> | <b>Exponent</b> | <b>Mantissa</b>  |
+|-----------------|-----------------|------------------|
+| pth             | E_PTH = 18      | M_PTH = 26250    |
+| margin          | E_MARGIN = 27   | M_MARGIN = 27343 |
+| plev            | E_PLEV = 20     | M_PLEV = 17500   |
+
+# --- Annex A (informative): VAD performance
+
+In the optimization of a VAD, a trade-off has to be made between speech clipping, which reduces the subjective performance of the system, and the mean channel activity factor. The benefit of DTX is increased as the activity factor is reduced. However, in general, a reduction of the activity factor will be associated with a greater risk of audible speech clipping.
+
+In the optimization process, emphasis has been placed on avoiding unnecessary speech clipping. However, it has been found that a VAD with virtually no audible clipping would result in a high activity and little DTX advantage. The VAD specified in the present document introduces audible and possibly objectionable clipping in certain cases, mainly for low input levels and low signal to noise ratios.
+
+An indication of the mean channel activity in DTX mode is given in table A.1. The figure quoted is the average calculated over a large number of conversations covering factors such as different talkers, noise characteristics and locations. It should be noted that the actual activity of a particular talker in a specific conversation may vary considerably from the figure given in the table. This is due to both talker behaviour and the level dependency of the VAD (the channel activity has been found to decrease by about 0.5% per dB of level reduction). However, as mentioned above, a decreased speech input level increases the risk of objectionable clipping.
+
+**Table A.1: Mean channel activity factor in DTX mode**
+
+| <b>Channel activity factor</b> |
+|--------------------------------|
+| 60%                            |
+
+# Annex B (informative): Simplified block filtering operation
+
+Consider an 8th order transversal filter with filter coefficients  $a[0..8]$ , through which a signal is being passed, the output of the filter being:
+
+$$s'n = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad (1)$$
+
+If we apply block filtering over 20 ms frames, then this equation becomes:
+
+$$s'n = - \sum_{i=0}^{\min(8,n)} (a[i]*s[n-i]) \quad ; \quad n = 0..167 \quad (2)$$
+
+$$\quad ; \quad 0 \leq n \leq 167$$
+
+If the energy of the filtered signal is then obtained for every 20 ms frame, the equation for this is:
+
+$$pvad = \sum_{n=0}^{167} \left( - \sum_{i=0}^{\min(8,n)} (a[i]*s[n-i]) \right)^2 \quad ; \quad 0 \leq n-i \leq 159 \quad (3)$$
+
+We know that:
+
+$$acf[i] = \sum_{n=i}^{159} (s[n]*s[n-i]) \quad ; \quad i = 0..8 \quad (4)$$
+
+$$\quad ; \quad 0 \leq n-i \leq 159$$
+
+If equation (3) is expanded and  $acf[0..8]$  are substituted for  $s[n]$  then we arrive at the equations:
+
+$$pvad = r[0]*acf[0] + 2*\sum_{i=1}^8 (r[i]*acf[i]) \quad (5)$$
+
+Where:
+
+$$r[i] = \sum_{k=0}^{8-i} (a[k]*a[k+i]) \quad ; \quad i = 0..8 \quad (6)$$
+
+# Annex C (informative): Pole frequency calculation
+
+This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz.
+
+The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients  $rc[1..2]$  obtained from the speech encoder. If the filter coefficients  $a[0..2]$  are defined such that the synthesis filter response is given by:
+
+$$H(z) = 1 / (a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$
+
+Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic:
+
+$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$
+
+The positions of the poles,  $z$ , are therefore:
+
+$$z = re \pm j \cdot \sqrt{im}, \quad j^2 = -1 \quad (3)$$
+
+where:
+
+$$re = -a[1] / 2 \quad (4)$$
+
+$$im = (4 \cdot a[2] - a[1]^2) / 4 \quad (5)$$
+
+If  $im$  is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If  $re$  is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2000 Hz and the prediction error test can be performed.
+
+If  $im$  is positive and  $re$  is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to  $re$  and  $im$  by the expression:
+
+$$freq = \arctan(\sqrt{im} / re) \cdot 4000 / \pi \quad (6)$$
+
+Having ensured that both  $im$  and  $re$  are positive the test for a pole frequency less than 385 Hz can be derived by substituting equations 4 and 5 into equation 6 and re-arranging:
+
+$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < \tan^2(\pi \cdot 385 / 4000) \quad (7)$$
+
+or
+
+$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < 0.0973 \quad (8)$$
+
+If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed.
+
+# Annex D (informative): Change history
+
+| Change history |           |         |                  |             |                                         |
+|----------------|-----------|---------|------------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                        |
+| SMG#15         |           |         |                  | 4.1.1       | ETSI Publication                        |
+| SMG#20         |           |         |                  | 5.0.1       | Release 1996 version                    |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                    |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                    |
+|                |           |         |                  | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46051/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-16/46_series/46051/5d76c2e9976aaf97001ee189908830fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..38869f4021f47dabc2fddceb1f67bb54e9ccfb06
--- /dev/null
+++ b/marked/Rel-16/46_series/46051/5d76c2e9976aaf97001ee189908830fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:39d8802cee65b77d78b5b5d7d63c362ac4af0554db5c04a348449e158bd333bf
+size 66260
diff --git a/marked/Rel-16/46_series/46051/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/46_series/46051/997233d405f0d4b89ddeb7683e047f66_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d53b19492dd6d00bcb5977e833a523a1982766d8
--- /dev/null
+++ b/marked/Rel-16/46_series/46051/997233d405f0d4b89ddeb7683e047f66_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:40747ab7edbe12779650268360e8a6f4052ef12d90b886e7a23e1a657bd3acbc
+size 64573
diff --git a/marked/Rel-16/46_series/46051/raw.md b/marked/Rel-16/46_series/46051/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8da56f3062a49ca990bbe169807deeee197b66e0
--- /dev/null
+++ b/marked/Rel-16/46_series/46051/raw.md
@@ -0,0 +1,258 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                                       |    |
+|-------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                        | 4  |
+| 1 Scope.....                                                                                          | 5  |
+| 2 References.....                                                                                     | 5  |
+| 3 Definitions and abbreviations .....                                                                 | 5  |
+| 3.1 Definitions.....                                                                                  | 5  |
+| 3.2 Abbreviations .....                                                                               | 6  |
+| 4 General .....                                                                                       | 6  |
+| 5 Enhanced Full Rate speech channel transcoding .....                                                 | 7  |
+| 6 Enhanced Full Rate speech channel discontinuous transmission (DTX) .....                            | 7  |
+| 7 Enhanced Full Rate speech channel Voice Activity Detection (VAD) .....                              | 8  |
+| 8 Enhanced Full Rate speech channel comfort noise insertion.....                                      | 8  |
+| 9 Enhanced Full Rate speech channel lost speech frame substitution and muting .....                   | 9  |
+| 10 Enhanced Full Rate codec homing.....                                                               | 9  |
+| 11 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode ..... | 9  |
+| Annex A (informative): Change History.....                                                            | 11 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document is an introduction to GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10] ENs dealing with the speech processing functions in the Enhanced Full Rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the ENs where each function is specified in detail.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
+- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [4] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [5] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec".
+- [6] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [7] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels".
+- [8] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels".
+- [9] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+- [10] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|         |                                                                |
+|---------|----------------------------------------------------------------|
+| ACELP   | Algebraic Code Excited Linear Prediction                       |
+| BFI     | Bad Frame Indication                                           |
+| BSS     | Base Station System                                            |
+| CCITT   | Comité Consultatif International Télégraphique et Téléphonique |
+| DTX     | Discontinuous Transmission                                     |
+| ETS     | European Telecommunication Standard                            |
+| GSM     | Global System for Mobile communications                        |
+| MS      | Mobile Station                                                 |
+| PCM     | Pulse Code Modulated                                           |
+| PLMN    | Public Land Mobile Network                                     |
+| PSTN    | Public Switched Telephone Network                              |
+| RF      | Radio Frequency                                                |
+| RSS     | Radio SubSystem                                                |
+| RX      | Receive                                                        |
+| SACCH   | Slow Associated Control CHannel                                |
+| SID     | Silence Descriptor                                             |
+| SP flag | SPeech flag                                                    |
+| TAF     | Time Alignment Flag                                            |
+| TX      | Transmit                                                       |
+
+For abbreviations not given in this subclause, see GSM 01.04 [1].
+
+# 4 General
+
+Figure 1 presents a reference configuration where the various speech processing functions are identified. In this figure, the relevant Standards for each function are also indicated.
+
+In figure 1, the audio parts including analogue to digital and digital to analogue conversion are included, to show the complete speech path between the audio input/output in the Mobile Station (MS) and the digital interface of the PSTN. The detailed specification of the audio parts are contained in GSM 03.50 [2]. These aspects are only considered to the extent that the performance of the audio parts affect the performance of the speech transcoder.
+
+An alternative and fully interoperable implementation using as a basis the 12.2 kbit/s mode of the Adaptive Multi Rate speech coder is described in section 11.
+
+![Figure 1: Reference configuration of speech processing functions. The diagram is divided into two main sections: TRANSMIT SIDE and RECEIVE SIDE. The TRANSMIT SIDE includes a BSS side (GSM 06.60) with a 8-bit /A-law to 13-bit uniform converter (1) and an MS side (GSM 03.50) with LPF and A/D converters. The output of the BSS side is connected to the MS side via a junction (2). The output of the MS side is connected to the Speech encoder (GSM 06.60) via a junction (2). The Speech encoder outputs a Speech frame (4) to the DTX control and operation block (GSM 06.81). The DTX control and operation block outputs an SP flag (6) and Info. bits (7). The DTX control and operation block also outputs a VAD (3) to the Voice Activity Detector (GSM 06.82). The Voice Activity Detector outputs a SID frame (5) to the Comfort noise TX functions (GSM 06.62).](5d76c2e9976aaf97001ee189908830fb_img.jpg)
+
+The diagram illustrates the speech processing flow on the transmit side. It starts with the BSS side (GSM 06.60) where a 8-bit /A-law to 13-bit uniform converter (1) processes the input. Simultaneously, the MS side (GSM 03.50) processes the input through LPF and A/D converters. The outputs from both sides are combined at junction (2) and fed into the Speech encoder (GSM 06.60). The Speech encoder generates a Speech frame (4) which is sent to the DTX control and operation block (GSM 06.81). This block also receives a VAD (3) from the Voice Activity Detector (GSM 06.82) and produces an SP flag (6) and Info. bits (7). Additionally, the DTX control and operation block sends a SID frame (5) to the Comfort noise TX functions (GSM 06.62).
+
+Figure 1: Reference configuration of speech processing functions. The diagram is divided into two main sections: TRANSMIT SIDE and RECEIVE SIDE. The TRANSMIT SIDE includes a BSS side (GSM 06.60) with a 8-bit /A-law to 13-bit uniform converter (1) and an MS side (GSM 03.50) with LPF and A/D converters. The output of the BSS side is connected to the MS side via a junction (2). The output of the MS side is connected to the Speech encoder (GSM 06.60) via a junction (2). The Speech encoder outputs a Speech frame (4) to the DTX control and operation block (GSM 06.81). The DTX control and operation block outputs an SP flag (6) and Info. bits (7). The DTX control and operation block also outputs a VAD (3) to the Voice Activity Detector (GSM 06.82). The Voice Activity Detector outputs a SID frame (5) to the Comfort noise TX functions (GSM 06.62).
+
+![Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between GSM 06.81 (DTX control and operation), GSM 06.61 (Speech frame substitution), GSM 06.60 (Speech decoder), and GSM 06.62 (Comfort noise RX functions) on the transmit side, and GSM 06.60 (13-bit uniform to 8-bit/A-law) and GSM 03.50 (D/A, LPF) on the receive side. Inputs include Info. bits (8), BFI (9), SID (10), and TAF (11).](997233d405f0d4b89ddeb7683e047f66_img.jpg)
+
+The diagram illustrates the audio processing functions in a GSM system. On the left, the 'GSM 06.81' block represents 'DTX control and operation'. It receives four inputs: 'Info. bits' (8), 'BFI' (9), 'SID' (10), and 'TAF' (11). It outputs a 'Speech frame' (4) to the 'Speech decoder' (GSM 06.60) and a 'SID frame' (5) to 'Comfort noise RX functions' (GSM 06.62). The 'Speech decoder' also receives a 'Speech frame' (2) from the 'RECEIVE SIDE'. The 'RECEIVE SIDE' consists of two parts: 'BSS side only' (GSM 06.60) which contains a '13-bit uniform to 8-bit/A-law' converter (1), and 'MS side only' (GSM 03.50) which contains a 'D/A' converter and an 'LPF' (Low Pass Filter). The 'Speech frame' (4) from the decoder is sent to the '13-bit uniform to 8-bit/A-law' converter. The 'SID frame' (5) from the 'Comfort noise RX functions' is also sent to the '13-bit uniform to 8-bit/A-law' converter. The '13-bit uniform to 8-bit/A-law' converter outputs to the 'D/A' converter, which then outputs to the 'LPF'.
+
+Figure 1: Overview of audio processing functions. The diagram shows the flow of audio data between GSM 06.81 (DTX control and operation), GSM 06.61 (Speech frame substitution), GSM 06.60 (Speech decoder), and GSM 06.62 (Comfort noise RX functions) on the transmit side, and GSM 06.60 (13-bit uniform to 8-bit/A-law) and GSM 03.50 (D/A, LPF) on the receive side. Inputs include Info. bits (8), BFI (9), SID (10), and TAF (11).
+
+- 1) 8-bit /A-law or  $\mu$ -law (PCS 1900) PCM (CCITT recommendation G.711), 8 000 samples/s.
+- 2) 13-bit uniform PCM, 8 000 samples/s.
+- 3) Voice Activity Detector (VAD) flag.
+- 4) Encoded speech frame, 50 frames/s, 244 bits/frame.
+- 5) Silence Descriptor (SID) frame, 244 bits/frame.
+- 6) SPeech (SP) flag, indicates whether information bits are speech or SID information.
+- 7) Information bits delivered to the radio subsystem.
+- 8) Information bits received from the radio subsystem.
+- 9) Bad Frame Indication.
+- 10) Silence Descriptor (SID) flag.
+- 11) Time Alignment Flag (TAF), marks the position of the SID frame within the Slow Associated Control CHannel (SACCH) multiframe.
+
+Figure 1: Overview of audio processing functions
+
+# 5 Enhanced Full Rate speech channel transcoding
+
+As shown in figure 1, the speech encoder takes its input as a 13-bit uniform Pulse Code Modulated (PCM) signal either from the audio part of the Mobile Station or on the network side, from the Public Switched Telephone Network (PSTN) via an 8-bit/A-law or  $\mu$ -law (PCS 1900) to 13-bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to the channel coding function defined in GSM 05.03 [3] to produce an encoded block consisting of 456 bits leading to a gross bit rate of 22,8 kbit/s.
+
+In the receive direction, the inverse operations take place. GSM 06.60 [6] describes the detailed mapping between input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to a bit rate for the encoded bit stream of 12,2 kbit/s. The coding scheme is the so-called Algebraic Code Excited Linear Prediction, hereafter referred to as ACELP.
+
+GSM 06.60 [6] describes the codec and GSM 06.53 [4] defines the C code, thus enabling the verification of compliance to GSM 06.60 [6] to a high degree of confidence by use of a set of digital test sequences given in GSM 06.54 [5].
+
+# 6 Enhanced Full Rate speech channel discontinuous transmission (DTX)
+
+During a normal phone conversation, the participants alternate so that, on the average, each direction of transmission is occupied about 50 % of the time. Discontinuous transmission (DTX) is a mode of operation where the transmitters are switched on only for those frames which contain useful information. This may be done for the following two purposes:
+
+- 1) In the MS, battery life will be prolonged or a smaller battery could be used for a given operational duration.
+
+- 2) The average interference level over the air interface is reduced, leading to better Radio Frequency (RF) spectrum efficiency.
+
+The overall DTX mechanism is implemented in the DTX handlers (Transmit (TX) and Receive (RX)) described in GSM 06.81 [9] and requires the following functions:
+
+- a Voice Activity Detector (VAD) on the TX side, see GSM 06.82 [10];
+- evaluation of the background acoustic noise on the TX side, in order to transmit characteristic parameters to the RX side, see GSM 06.62 [8];
+- generation of comfort noise on the RX side during periods where the radio transmission is turned off, see GSM 06.62 [8].
+
+The transmission of comfort noise information to the RX side is achieved by means of a Silence Descriptor (SID) frame. The SID frame is transmitted at the end of speech bursts and serves as an end of speech marker for the RX side. In order to update the comfort noise characteristics at the RX side, SID frames are transmitted at regular intervals also during speech pauses. This also serves the purpose of improving the measurement of the radio link quality by the Radio SubSystem (RSS).
+
+The DTX handlers interwork with the RSS using flags. The RSS is in control of the actual transmitter keying on the TX side, and performs various pre-processing functions on the RX side. This is described in GSM 06.81 [9].
+
+The speech flag (SP) indicates whether information bits are speech or SID information. The SP flag is calculated from the VAD flag by the TX DTX handler. When SID information is transmitted (SP="0") the operation of the speech encoder is modified to reduce the remaining computation for that frame. This is described in GSM 06.62 [8].
+
+# --- 7 Enhanced Full Rate speech channel Voice Activity Detection (VAD)
+
+The Enhanced Full Rate VAD function is described in GSM 06.82 [10].
+
+The input to the VAD is a set of parameters computed by the Enhanced Full Rate speech encoder defined in GSM 06.60 [6]. The VAD uses this information to decide whether each 20 ms speech coder frame contains speech or not. Note that the VAD flag is an input to TX DTX handler and does not control the transmitter keying directly.
+
+GSM 06.82 [10] describes the VAD algorithm and GSM 06.53 [4] defines the C code. The verification of compliance to GSM 06.82 [10] is achieved by use of digital test sequences (see GSM 06.54 [5]) applied to the same interface as the test sequences for the speech codec.
+
+# --- 8 Enhanced Full Rate speech channel comfort noise insertion
+
+The Enhanced Full Rate noise comfort insertion function is described in GSM 06.62 [8].
+
+When switching the transmission on and off during DTX operation, the effect would be a modulation of the background noise at the receiving end, if no precautions were taken. When transmission is on, the background noise is transmitted together with the speech to the receiving end. As the speech burst ends, the connection is off and the perceived noise would drop to a very low level. This step modulation of noise may be perceived as annoying and reduce the intelligibility of speech, if presented to a listener without modification.
+
+This "noise contrast effect" is reduced in the GSM system by inserting an artificial noise, termed comfort noise, at the receiving end when speech is absent.
+
+The comfort noise processes are as follows:
+
+- the evaluation of the acoustic background noise in the transmitter;
+- the noise parameter encoding (SID frames) and decoding;
+- and the generation of comfort noise in the receiver.
+
+The comfort noise processes and the algorithm for updating the noise parameters during speech pauses are defined in detail in GSM 06.62 [8].
+
+The comfort noise mechanism is based on the Enhanced Full Rate speech codec defined in GSM 06.60 [6].
+
+# --- 9 Enhanced Full Rate speech channel lost speech frame substitution and muting
+
+The Enhanced Full Rate speech frame substitution and muting function is described in GSM 06.61 [7].
+
+In the receiver, frames may be lost due to transmission errors or frame stealing. GSM 06.61 [7] describes the actions to be taken in these cases, both for lost speech frames and for lost SID frames in DTX operation.
+
+In order to mask the effect of an isolated lost frame, the lost speech frame is substituted by a predicted frame based on previous frames. Insertion of silence frames is not allowed. For several subsequent lost frames, a muting technique shall be used to indicate to the listener that transmission has been interrupted.
+
+# --- 10 Enhanced Full Rate codec homing
+
+The GSM Enhanced Full Rate speech transcoder, VAD, DTX system and comfort noise parts of the audio processing functions (see figure 1) are defined in bit exact arithmetic. Consequently, they shall react on a given input sequence always with the corresponding bit exact output sequence, provided that the internal state variables are also always exactly in the same state at the beginning of the experiment.
+
+The input test sequences provided in GSM 06.54 [5] shall force the corresponding output test sequences, provided that the tested modules are in their home-state when starting.
+
+The modules may be set into their home states by provoking the appropriate homing-functions.
+
+NOTE: This is normally done during reset (initialization of the codec).
+
+Special inband signalling frames (encoder-homing-frame and decoder-homing-frame) described in GSM 06.60 [6] have been defined to provoke these homing-functions also in remotely placed modules.
+
+This mechanism is specified to support three main areas:
+
+- type approval of mobile terminal equipment;
+- type approval of infrastructure equipment;
+- remote control and testing for operation and maintenance.
+
+At the end of the first received homing frame, the audio functions that are defined in a bit exact way shall go into their predefined home states. The output corresponding to the first homing frame is dependent on the codec state when the frame was received. Any consecutive homing frames shall produce corresponding homing frames at the output.
+
+# --- 11 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode
+
+The 12.2 kbit/s mode of the Adaptive Multi Rate speech coder described in TS 26.071 is functionally equivalent to the GSM Enhanced Full Rate speech coder. An alternative implementation of the Enhanced Full Rate speech service based on the 12.2 kbit/s mode of the Adaptive Multi Rate coder is allowed. Alternative implementations shall implement the functionality specified in TS 26.071 for the 12.2 kbit/s mode, with the difference that the DTX transmission format from GSM 06.81, the comfort noise generation from GSM 06.62 and the decoder-homing-frame from GSM 06.60 shall be used.
+
+Verification of compliance using the alternative implementation is achieved by use of a set of digital test sequences given in GSM 06.54.
+
+NOTE: The alternative implementation of the GSM Enhanced Full Rate speech coder incurs an additional 5ms look-ahead delay, and the implementation in this specification (GSM 06.51) is the preferred option.
+
+# Annex A (informative): Change History
+
+| Change history |           |         |                  |             |                                                        |
+|----------------|-----------|---------|------------------|-------------|--------------------------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                                       |
+| SMG#21         |           |         |                  | 4.0.1       | ETSI Publication                                       |
+| SMG#20         |           |         |                  | 5.1.2       | Release 1996 version                                   |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                                   |
+| SMG#28         | P-99-139  | A003    | Figure 1, Sect.5 | 7.0.0       | Addition of mu-law (PCS 1900)                          |
+|                |           |         |                  | 7.0.2       | Update to Version 7.0.2 for Publication                |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                                   |
+| SMG#32         | P-00-273  | A008    | 4 and 11         | 8.1.0       | Alternative EFR implementation using the AMR 12.2 mode |
+
+| Change history |         |           |      |     |                                                                       |        |        |
+|----------------|---------|-----------|------|-----|-----------------------------------------------------------------------|--------|--------|
+| Date           | TSG SA# | TSG Doc.  | CR   | Rev | Subject/Comment                                                       | Old    | New    |
+| 12-2000        | 10      | SP-000572 | A013 |     | Definition of the homing frame for the alternative EFR implementation | 8.1.0  | 8.2.0  |
+| 03-2001        | 11      |           |      |     | Version for Release 4                                                 |        | 4.0.0  |
+| 06-2002        | 16      |           |      |     | Version for Release 5                                                 | 4.0.0  | 5.0.0  |
+| 12-2004        | 26      |           |      |     | Version for Release 6                                                 | 5.0.0  | 6.0.0  |
+| 06-2007        | 36      |           |      |     | Version for Release 7                                                 | 6.0.0  | 7.0.0  |
+| 12-2008        | 42      |           |      |     | Version for Release 8                                                 | 7.0.0  | 8.0.0  |
+| 12-2009        | 46      |           |      |     | Version for Release 9                                                 | 8.0.0  | 9.0.0  |
+| 03-2011        | 51      |           |      |     | Version for Release 10                                                | 9.0.0  | 10.0.0 |
+| 09-2012        | 57      |           |      |     | Version for Release 11                                                | 10.0.0 | 11.0.0 |
+| 09-2014        | 65      |           |      |     | Version for Release 12                                                | 11.0.0 | 12.0.0 |
+| 12-2015        | 70      |           |      |     | Version for Release 13                                                | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46053/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46053/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da57623c6618ed3833b0f055911854068766db3c
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:604e34840b8c371dbe6b710ad447123c3db691183913c59393c42aca388f75a0
+size 22944
diff --git a/marked/Rel-16/46_series/46053/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/46_series/46053/5a4e62bead259c258d069fd3663ea670_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6ea64da62b4ae1456f04d1e516f50995fb463ed4
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/5a4e62bead259c258d069fd3663ea670_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be5ebac2d8984a1476ada4d6cd21610260f863c170b1570c8b2b003d4b5c7e95
+size 123875
diff --git a/marked/Rel-16/46_series/46053/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/46_series/46053/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9d4c072d4108544ca7351e76b9b0efca26d818ed
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:726bf61168920fad3f86e850226705d93bd86887c6ad4342d515439b73fc4a26
+size 90831
diff --git a/marked/Rel-16/46_series/46053/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/46_series/46053/d0abac95583b52a3b35f74a215567334_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..250cbdfdf073cc862f52cbc3a4b7d7404c57a11e
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/d0abac95583b52a3b35f74a215567334_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:754c0b9bab2da7872194c67e41c3530c26d30d2a333c57545e29e9dae0a089ba
+size 109619
diff --git a/marked/Rel-16/46_series/46053/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/46_series/46053/e6df2733626a85205c1db682e6259c46_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..658f5a532cad8de8ad00b081064158b87dffd164
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/e6df2733626a85205c1db682e6259c46_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:438215586ddf6e67fd68820b96e97c3529bb215264c235ef4f1701cab3321d52
+size 48445
diff --git a/marked/Rel-16/46_series/46053/raw.md b/marked/Rel-16/46_series/46053/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..1639dd21a7e46d04abe97f2fe4e56f478167d32b
--- /dev/null
+++ b/marked/Rel-16/46_series/46053/raw.md
@@ -0,0 +1,309 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                             |    |
+|---------------------------------------------|----|
+| Foreword .....                              | 4  |
+| 1 Scope.....                                | 5  |
+| 2 References.....                           | 5  |
+| 3 Definitions and abbreviations .....       | 5  |
+| 3.1 Definitions.....                        | 5  |
+| 3.2 Abbreviations .....                     | 6  |
+| 4 C code structure .....                    | 6  |
+| 4.1 Contents of the C source code disk..... | 6  |
+| 4.2 Program execution.....                  | 7  |
+| 4.3 Code hierarchy .....                    | 7  |
+| Annex A (informative): Change History.....  | 13 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document provides the bit exact definition of the Enhanced Full Rate (EFR) speech traffic codec for the digital cellular telecommunications system.
+
+An electronic attachment accompanies the present document, containing clause 5, the bit-exact ANSI-C code for the Enhanced Full Rate speech transcoder.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document contains an electronic copy of the ANSI-C code for the GSM Enhanced Full Rate codec. The ANSI-C code is necessary for a bit exact implementation of the Enhanced Full Rate speech transcoder (GSM 06.60 [3]), Voice Activity Detection (GSM 06.82 [7]), comfort noise (GSM 06.62 [5]), Discontinuous Transmission (GSM 06.81 [6]) and example solutions for substituting and muting of lost frames (GSM 06.61 [4]).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test sequences for the GSM Enhanced Full Rate (EFR) speech codec".
+- [3] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [4] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels".
+- [5] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels".
+- [6] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+- [7] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD) for Enhanced Full Rate (EFR) speech traffic channels".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.60 [3], GSM 06.61 [4], GSM 06.62 [5], GSM 06.81 [6] and GSM 06.82 [7].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                         |
+|-------|-----------------------------------------|
+| ANSI  | American National Standards Institute   |
+| DS-HD | Double Sided High Density               |
+| ETS   | European Telecommunication Standard     |
+| GSM   | Global System for Mobile communications |
+| I/O   | Input/Output                            |
+| ROM   | Read Only Memory                        |
+
+For abbreviations not given in this clause see GSM 01.04 [1].
+
+# 4 C code structure
+
+This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the archive en\_300724v080000o0.ZIP which accompanies the present document.
+
+The C code has been verified on the following systems:
+
+- Sun Microsystems <sup>1)</sup> workstations and Sun Microsystems cc compiler and gcc compiler;
+- IBM <sup>2)</sup> PC/AT compatible computers and Borland Turbo-C++ <sup>3)</sup> compiler;
+- Hewlett Packard's <sup>4)</sup> workstations and HP cc compiler;
+
+ANSI-C 9899 was selected as the programming language because portability was desirable.
+
+## 4.1 Contents of the C source code disk
+
+The C code disk has all of the files in the root level.
+
+In this disk, the files with suffix "c" contain the source code and the files with suffix "h" are the header files. The ROM data is contained mostly in files with suffix "tab". All text files are formatted such that they are correct for an IBM PC/AT compatible.
+
+The archive en\_300724v080000o0.ZIP which accompanies the present document contains one speech coder installation verification data file, "spch\_dos.inp". The reference encoder output file is named "spch\_dos.cod", the reference decoder input file is named "spch\_dos.dec" and the reference decoder output file is named "spch\_dos.out". These four files are formatted such that they are correct for an IBM PC/AT compatible. The same files with reversed byte order of the 16 bit words are named "spch\_unx.inp", "spch\_unx.cod", "spch\_unx.dec" and "spch\_unx.out", respectively.
+
+In an IBM PC/AT compatible platform, the installation verification can be performed by running the batch file "ts\_dos.bat". In most UNIX platforms, the installation verification can be performed by running the batch file "ts\_unx.bat". Final verification is to be performed using the GSM Enhanced Full Rate test sequences described in GSM 06.54 [2].
+
+Makefiles are provided for the three platforms in which the C code has been verified (listed above). Once the software is installed, this directory will have compiled versions of *coder* and *decoder* (the bit-exact C executables of the speech codec), *ed\_iface* (interface program between coder and decoder) and all the object files.
+
+The programs *coder* and *decoder* are the GSM Enhanced Full Rate encoder and decoder executable files, respectively. A third program, *ed\_iface*, is also contained in this directory. This is the program which provides the format conversion between the encoder output file format and the decoder input file format.
+
+## 4.2 Program execution
+
+The GSM enhanced full rate speech codec is implemented as three separate programs:
+
+- (*coder*) speech encoder;
+- (*ed\_iface*) encoder/decoder interface;
+- (*decoder*) speech decoder.
+
+For encoding using the *coder* program, the input is a binary speech file (\*.inp) and the output is a binary encoded parameter file (\*.cod). For decoding using the *decoder* program, the input is a binary parameter file (\*.dec) and the output is a binary synthesized speech file (\*.out).
+
+---
+
+<sup>1)</sup> ) Registered trade mark of Sun Microsystems
+
+<sup>2)</sup> ) Registered trade mark of International Business Machines
+
+<sup>3)</sup> ) Registered trade mark of Borland
+
+<sup>4)</sup> ) Registered trade mark of Hewlett Packard
+
+NOTE: The format for the parameter input file required for decoding (\*.dec) is not the same as the format of the parameter output file generated by encoding (\*.cod). The *ed\_iface* program will translate an \*.cod file into a \*.dec file.
+
+See the file readme.txt for more information on how to run the coder, *ed\_iface* and *decoder* programs.
+
+## 4.3 Code hierarchy
+
+Figures 1 to 5 are call graphs that show the functions used in the speech codec, including the functions of VAD, DTX, and comfort noise generation.
+
+The encode call graph is broken down into three separate call graphs, and the decode call graph is broken down into two separate call graphs. Those clauses which are large are separated from the primary call tree and given their own call tree. Each vertical column represents a call level. For example, main() is at level 0, Coder\_12k2() at level 1, Int\_lpc2() at level 2, Lsp\_Az() at level 3, Get\_lsp\_pol() at level 4, etc. The basic operations are not counted as extending the depth, therefore the deepest level in this software is level 4.
+
+Some items have been omitted from this call graph. All standard C functions: printf(), fwrite(), etc. have been omitted. Also, no basic operations (add(), L\_add(), mac(), etc.) or double precision extended operations (e.g. L\_Extract()) appear in the graphs. The reset functions of the encoder and decoder are only visible as the functions reset\_enc and reset\_dec, respectively. There are several subroutine calls from inside these functions.
+
+The time order in the call graphs is from the bottom upwards as the processing of a frame advances.
+
+![Speech encoder call graph showing the hierarchy of functions starting from 'main'.](d0abac95583b52a3b35f74a215567334_img.jpg)
+
+```
+
+graph TD
+    main --> sid_codeword_encoding
+    main --> Prm2bits_12k2
+    main --> CN_encoding
+    main --> Coder_12k2
+    main --> Pre_Process
+    main --> encoder_homing_frame_test
+    main --> reset_enc
+
+    Coder_12k2 --> Int2bin
+    Coder_12k2 --> periodicity_update
+    Coder_12k2 --> Pitch_ol
+    Coder_12k2 --> Syn_filt
+    Coder_12k2 --> Residu
+    Coder_12k2 --> Weight_A1
+    Coder_12k2 --> Int_lpc
+    Coder_12k2 --> Int_lpc2
+    Coder_12k2 --> Q_plsf_5
+    Coder_12k2 --> tx_dtx
+    Coder_12k2 --> vad_computation
+    Coder_12k2 --> Az_lsp
+    Coder_12k2 --> Levinson
+    Coder_12k2 --> Lag_window
+    Coder_12k2 --> Autocorr
+
+    Az_lsp --> Lag_max
+    Az_lsp --> Lsp_Az
+    Az_lsp --> Lsf_lsp
+    Az_lsp --> Reorder_lsf
+    Az_lsp --> Vq_subvec_s
+    Az_lsp --> Vq_subvec
+    Az_lsp --> Lsf_wt
+    Az_lsp --> update_lsf_history
+    Az_lsp --> aver_lsf_history
+    Az_lsp --> update_lsf_p_CN
+    Az_lsp --> Lsp_lsf
+    Az_lsp --> Chebbs
+
+    Lag_max --> Inv_sqrt
+    Lsp_Az --> Get_lsp_pol
+  
+```
+
+Speech encoder call graph showing the hierarchy of functions starting from 'main'.
+
+Figure 1: Speech encoder call graph (see figures 2 and 3)
+
+![Speech encoder subframe processing call graph](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+This call graph illustrates the processing flow for a speech encoder subframe. The process begins with the input `Coder_12k2`, which branches into several parallel processing paths. One path leads to `q_gain_code`, which then branches into `aver_gain_code_history`, `update_gcode0_CN`, `update_gain_code_history_tx`, `Pow2`, and `Log2`. Another path from `Coder_12k2` leads to `G_code`, which then leads to `build_CN_code`. `build_CN_code` branches into `pseudonoise` and `q_p`. A third path from `Coder_12k2` leads to `code_10140_35bits`, which then branches into `q_gain_pitch`, `G_pitch`, `Convolve`, `Pred_lt_6`, `Enc_lag6`, `Pitch_fr6`, `Copy`, and `compute_CN_excitation_gain`. `code_10140_35bits` also branches into `build_code`, `search_10140`, `cor_h`, `set_sign`, and `cor_h_x`. `q_p` branches into `build_code`, `search_10140`, `cor_h`, `set_sign`, and `cor_h_x`. `search_10140` branches into `cor_h`, `set_sign`, and `cor_h_x`. `cor_h` branches into `set_sign` and `cor_h_x`. `set_sign` branches into `cor_h_x`. `cor_h_x` branches into `Inv_sqrt` and `Convolve`. `compute_CN_excitation_gain` branches into `Interpol_6` and `Norm_Corr`. `Interpol_6` branches into `Inv_sqrt` and `Convolve`. `Norm_Corr` branches into `Inv_sqrt` and `Convolve`.
+
+Speech encoder subframe processing call graph
+
+Figure 2: Speech encoder subframe processing call graph
+
+![Voice Activity Detector (VAD) call graph showing vad_computation calling various sub-functions including vad_hangover, vad_decision, threshold_adaptation, tone_detection, spectral_comparison, predictor_values, acf_averaging, and energy_computation. tone_detection calls step_up. predictor_values calls step_up, compute_rav1, and schur_recursion.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+```
+graph LR; vad_computation --> vad_hangover; vad_computation --> vad_decision; vad_computation --> threshold_adaptation; vad_computation --> tone_detection; vad_computation --> spectral_comparison; vad_computation --> predictor_values; vad_computation --> acf_averaging; vad_computation --> energy_computation; tone_detection --> step_up; predictor_values --> step_up; predictor_values --> compute_rav1; predictor_values --> schur_recursion;
+```
+
+Voice Activity Detector (VAD) call graph showing vad\_computation calling various sub-functions including vad\_hangover, vad\_decision, threshold\_adaptation, tone\_detection, spectral\_comparison, predictor\_values, acf\_averaging, and energy\_computation. tone\_detection calls step\_up. predictor\_values calls step\_up, compute\_rav1, and schur\_recursion.
+
+**Figure 3: Voice Activity Detector (VAD) call graph**
+
+![Speech decoder call graph showing the hierarchy of function calls starting from 'main'.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+```
+
+graph TD
+    main --> Post_Filter
+    main --> Decoder_12k2
+    main --> decoder_homing_frame_test
+    main --> Bits2prm_12k2
+    main --> reset_dec
+
+    Decoder_12k2 --> Copy
+    Decoder_12k2 --> Syn_filt
+    Decoder_12k2 --> agc2
+    Decoder_12k2 --> d_gain_code
+    Decoder_12k2 --> build_CN_code
+    Decoder_12k2 --> dec_10i40_35bits
+    Decoder_12k2 --> d_gain_pitch
+    Decoder_12k2 --> Pred_lt_6
+    Decoder_12k2 --> Dec_lag6
+    Decoder_12k2 --> Lsp_Az
+    Decoder_12k2 --> Int_lpc
+    Decoder_12k2 --> D_plsf_5
+    Decoder_12k2 --> rx_dtx
+
+    d_gain_code --> Inv_sqrt
+    d_gain_code --> Pow2
+    d_gain_code --> Log2
+    d_gain_code --> update_gain_code_history_rx
+    d_gain_code --> interpolate_CN_param
+    d_gain_code --> update_gcode0_CN
+    d_gain_code --> pseudonoise
+    d_gain_code --> gmed5
+
+    dec_10i40_35bits --> Get_lsp_pol
+    Get_lsp_pol --> Lsp_Az
+    Lsp_Az --> update_lsf_history
+    update_lsf_history --> Reorder_lsf
+    Reorder_lsf --> Lsf_lsp
+    Lsf_lsp --> interpolate_CN_lsf
+    interpolate_CN_lsf --> interpolate_CN_param
+    update_lsf_p_CN --> interpolate_CN_param
+
+    D_plsf_5 --> Bits2int
+    Bits2int --> decoder_homing_frame_test
+  
+```
+
+Speech decoder call graph showing the hierarchy of function calls starting from 'main'.
+
+Figure 4: Speech decoder call graph (see figure 5)
+
+![Speech decoder postfilter call graph](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+graph LR; Post_Filter --> age; Post_Filter --> preemphasis; Post_Filter --> Syn_filt; Post_Filter --> Set_zero; Post_Filter --> Copy; Post_Filter --> Residu; Post_Filter --> Weight_Ai; age --> Inv_sqrt;
+```
+
+The diagram illustrates the call graph for the Post\_Filter function. It shows seven outgoing calls from Post\_Filter to various sub-functions: age, preemphasis, Syn\_filt, Set\_zero, Copy, Residu, and Weight\_Ai. Additionally, the age function has a call to Inv\_sqrt.
+
+Speech decoder postfilter call graph
+
+**Figure 5: Speech decoder postfilter call graph**
+
+# Annex A (informative): Change History
+
+| Change history |           |         |                 |             |                                         |
+|----------------|-----------|---------|-----------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments                        |
+| SMG#23         |           |         |                 | 4.0.1       | ETSI Publication                        |
+| SMG#20         |           |         |                 | 5.1.2       | Release 1996 version                    |
+| SMG#27         |           |         |                 | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                 | 7.0.0       | Release 1998 version                    |
+|                |           |         |                 | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                 | 8.0.0       | Release 1999 version                    |
+|                |           |         |                 | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   | -    | -  | -   | -   | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46054/raw.md b/marked/Rel-16/46_series/46054/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..3885abd6306b670389021fd7dfa1bfbf8f96bb8e
--- /dev/null
+++ b/marked/Rel-16/46_series/46054/raw.md
@@ -0,0 +1,709 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                                      |    |
+|------------------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                                       | 4  |
+| 1 Scope.....                                                                                         | 5  |
+| 2 References.....                                                                                    | 5  |
+| 3 Definitions and abbreviations .....                                                                | 6  |
+| 3.1 Definitions.....                                                                                 | 6  |
+| 3.2 Abbreviations .....                                                                              | 6  |
+| 4 General .....                                                                                      | 6  |
+| 5 Test sequence format .....                                                                         | 6  |
+| 5.1 File format.....                                                                                 | 6  |
+| 5.2 Codec homing .....                                                                               | 7  |
+| 6 Speech codec test sequences.....                                                                   | 8  |
+| 6.1 Codec configuration .....                                                                        | 8  |
+| 6.2 Speech codec test sequences .....                                                                | 8  |
+| 6.2.1 Speech encoder test sequences .....                                                            | 8  |
+| 6.2.2 Speech decoder test sequences .....                                                            | 9  |
+| 6.2.3 Codec homing sequence .....                                                                    | 9  |
+| 7 DTX test sequences.....                                                                            | 11 |
+| 7.1 Codec configuration .....                                                                        | 11 |
+| 7.2 DTX test sequences.....                                                                          | 11 |
+| 7.2.1 Predictor values computation .....                                                             | 12 |
+| 7.2.2 Spectral comparison .....                                                                      | 12 |
+| 7.2.3 Threshold adaptation .....                                                                     | 12 |
+| 7.2.4 Periodicity detection .....                                                                    | 12 |
+| 7.2.5 Tone detection .....                                                                           | 12 |
+| 7.2.6 Safety and initialisation .....                                                                | 12 |
+| 7.2.7 Comfort noise test sequence .....                                                              | 12 |
+| 7.2.8 Real speech and tones.....                                                                     | 12 |
+| 8 Sequences for finding the 20 ms framing of the GSM enhanced full rate speech encoder .....         | 13 |
+| 8.1 Bit synchronisation.....                                                                         | 13 |
+| 8.2 Frame synchronisation .....                                                                      | 14 |
+| 8.3 Formats and sizes of the synchronisation sequences .....                                         | 14 |
+| 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences .....                                 | 15 |
+| 10 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode..... | 17 |
+| Annex A (informative): Change History.....                                                           | 19 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+Test sequences for a bit exact implementation of the Enhanced Full Rate (EFR) speech transcoder are contained in the archive files which accompany the present document.
+
+The archive contains ZIP compressed files, as follows:
+
+|                       |                                                                                                                                                                          |
+|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Disk1_8               | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST0.xxx to TEST8.xxx.                                               |
+| Disk2_8               | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST09.xxx to TEST16.xxx.                                             |
+| Disk3_8               | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; Speech test sequences TEST17.xxx to TEST20.xxx, Codec homing and synchronisation sequences. |
+| Disk4_8               | Clause 10: Test sequences for the GSM Enhanced Full Rate (EFR) speech codec; DTX test sequences.                                                                         |
+| Disk5_8 to<br>Disk8_8 | Clause 10: Test sequences for the GSM Enhance Full Rate (EFR) speech codec; 8 bit A- and $\mu$ -law compressed test sequences for alternative TRAU testing.              |
+| amr122_efr            | Test sequences for the GSM-EFR speech codec using the Adaptive Multi-Rate (AMR) speech codec mode MR122 (GSM 06.74)                                                      |
+
+The present document specifies the digital test sequences for the GSM enhanced full rate speech codec for the digital cellular telecommunications system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+  
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+  
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the digital test sequences for the GSM enhanced full rate speech codec. These sequences test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]).
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [3] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Enhanced Full Rate (EFR) speech traffic channels".
+- [4] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels".
+- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+- [6] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Enhanced Full Rate (EFR) speech traffic channels".
+- [7] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [8] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech coding functions; General description".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06.60 [2], GSM 06.61 [3], GSM 06.62 [4], GSM 06.81 [5] and GSM 06.82 [6].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                                         |
+|-----|-----------------------------------------|
+| ETS | European Telecommunication Standard     |
+| GSM | Global System for Mobile communications |
+
+For abbreviations not given in this subclause see GSM 01.04 [1].
+
+# --- 4 General
+
+Digital test sequences are necessary to test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Digital test Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]).
+
+The test sequences may also be used to verify installations of the ANSI C code in GSM 06.53 [7].
+
+Clause 5 describes the format of the files which contain the digital test sequences. Clause 6 describes the test sequences for the speech transcoder. Clause 7 describes the test sequences for the VAD, comfort noise and discontinuous transmission.
+
+Clause 8 describes the method by which synchronisation is obtained between the test sequences and the speech codec under test.
+
+Clause 9 describes the alternative acceptance testing of the speech encoder and decoder in the TRAUs by means of 8 bit A- or  $\mu$ -law compressed test sequences on the A-Interface.
+
+Test sequences for an alternative and fully interoperable implementation using as a basis the 12.2 kbit/s mode of the Adaptive Multi Rate speech coder are described in section 10.
+
+Electronic copies of the digital test sequences are provided as clause 10, these digital test sequences are contained in the archive ts\_100725v080100p0.zip which accompanies the present document.
+
+# --- 5 Test sequence format
+
+This clause provides information on the format of the digital test sequences for the GSM enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]).
+
+## 5.1 File format
+
+The test sequence files are provided in archive ts\_100725v080100p0.zip which accompanies the present document.
+
+Following decompression, four types of file are provided:
+
+- Files for input to the GSM enhanced full rate speech encoder: \*.INP
+- Files for comparison with the encoder output: \*.COD
+- Files for input to the GSM enhanced full rate speech decoder: \*.DEC
+- Files for comparison with the decoder output: \*.OUT
+
+The \*.DEC files are generated from the corresponding \*.COD files.
+
+Tables 1, 2, 3 and 4 define the formats of the four types of file.
+
+Each speech parameter within the speech frame of 244 bits/20 ms is contained in a serial string of 16 bit words, where each word contains the value of one bit of the parameter. In each string of  $n$  16 bit words containing the  $n$  bits of a parameter, the most significant bit of the parameter is written first, and the least significant bit is written last. The bit value contained in a single 16 bit word is either 0x0000 or 0x0001 (right justified) for the binary values of “0” and “1”, respectively. See table 6 of GSM 06.60 [2] for the order of occurrence and bit allocation of speech parameters within the speech frame of 244 bits/20 ms.
+
+The samples in the encoder input signal and in the decoder output signal are left justified.
+
+## 5.2 Codec homing
+
+Each \*.INP file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech encoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.53 [7]), all speech encoder output frames shall be identical to the corresponding frame in the \*.COD file. In the case of a correct hardware implementation undergoing testing, the first speech encoder output frame is undefined
+
+and need not be identical to the first frame in the \*.COD file, but all remaining speech encoder output frames shall be identical to the corresponding frames in the \*.COD file.
+
+Each \*.DEC file includes two homing frames at the start of the test sequence. The function of these frames is to reset the speech decoder state variables to their initial value. In the case of a correct installation of the ANSI-C simulation (GSM 06.53 [7]), all speech decoder output frames shall be identical to the corresponding frame in the \*.OUT file. In the case of a correct hardware implementation undergoing testing, the first speech decoder output frame is undefined and need not be identical to first frame in the \*.OUT file, but all remaining speech decoder output frames shall be identical to the corresponding frames in the \*.OUT file.
+
+**Table 1: Encoder input sequence (\*.INP) format**
+
+| Name | Description          | No. of bits | Justification |
+|------|----------------------|-------------|---------------|
+| s(n) | Encoder input signal | 13          | Left          |
+
+**Table 2: Encoder output sequence (\*.COD) format**
+
+| Name                   | Description                                                   | No. of bits | Justification |
+|------------------------|---------------------------------------------------------------|-------------|---------------|
+| Speech parameters      |                                                               |             |               |
+| SPEECH                 | Serial stream of speech parameter bits to the channel encoder | 244         | Right         |
+| Additional information |                                                               |             |               |
+| VAD                    | Voice activity detection flag                                 | 1           | Right         |
+| SP                     | SP flag                                                       | 1           | Right         |
+
+**Table 3: Decoder input sequence (\*.DEC) format**
+
+| Name                   | Description                                                   | No. of bits | Justification |
+|------------------------|---------------------------------------------------------------|-------------|---------------|
+| Additional information |                                                               |             |               |
+| BFI                    | Bad Frame Indicator flag                                      | 1           | Right         |
+| Speech parameters      |                                                               |             |               |
+| SPEECH                 | Serial stream of speech parameter bits to the channel encoder | 244         | Right         |
+| Additional information |                                                               |             |               |
+| SID                    | Silence Descriptor flag                                       | 1           | Right         |
+| TAF                    | Time Alignment Flag                                           | 1           | Right         |
+
+**Table 4: Decoder output sequence (\*.OUT) format**
+
+| Name  | Description           | No. of bits | Justification |
+|-------|-----------------------|-------------|---------------|
+| s'(n) | Decoder output signal | 13          | Left          |
+
+# 6 Speech codec test sequences
+
+This clause describes the test sequences designed to exercise the GSM enhanced full rate speech transcoder (GSM 06.60 [2]).
+
+## 6.1 Codec configuration
+
+The speech encoder shall be configured to operate in the non-DTX mode. The VAD and SP flags shall be set to 1 at the speech encoder output.
+
+## 6.2 Speech codec test sequences
+
+Table 5 lists the location and size of the speech codec test sequences.
+
+### 6.2.1 Speech encoder test sequences
+
+Twenty-one encoder input sequences are provided. Note that for the input sequences TEST0.INP to TEST3.INP, the amplitude figures are given in 13-bit precision. The active speech levels are given in dBov.
+
+- TEST0.INP - Synthetic harmonic signal. The pitch delay varies slowly from 18 to 143.5 samples. The minimum and maximum amplitudes are -997 and +971.
+- TEST1.INP - Synthetic harmonic signal. The pitch delay varies slowly from 144 down to 18.5 samples. Amplitudes at saturation point -4096 and +4095.
+- TEST2.INP - Sinusoidal sweep varying from 150 Hz to 3400 Hz. Amplitudes  $\pm$  1250.
+- TEST3.INP - Sinusoidal sweep varying from 150 Hz to 3400 Hz. Amplitudes  $\pm$  4000.
+- TEST4.INP - Female speech, active speech level: -19.4 dBov, flat frequency response.
+- TEST5.INP - Male speech, active speech level: -18.7 dBov, flat frequency response.
+- TEST6.INP - Female speech, ambient noise, active speech level: -35.0 dBov, flat frequency response.
+- TEST7.INP - Female speech, ambient noise, active speech level: -25.0 dBov, flat frequency response.
+- TEST8.INP - Female speech, ambient noise, active speech level: -15.6 dBov, flat frequency response.
+- TEST9.INP - Female speech, car noise, active speech level: -35.5 dBov, flat frequency response.
+- TEST10.INP - Female speech, car noise, active speech level: -26.1 dBov, flat frequency response.
+- TEST11.INP - Female speech, car noise, active speech level: -15.8 dBov, flat frequency response.
+- TEST12.INP - Male speech, ambient noise, active speech level: -34.9 dBov, flat frequency response.
+- TEST13.INP - Male speech, ambient noise, active speech level: -24.8 dBov, flat frequency response.
+- TEST14.INP - Male speech, ambient noise, active speech level: -15.0 dBov, flat frequency response.
+- TEST15.INP - Male speech, babble noise, active speech level: -34.1 dBov, flat frequency response.
+- TEST16.INP - Male speech, babble noise, active speech level: -24.3 dBov, flat frequency response.
+- TEST17.INP - Male speech, babble noise, active speech level: -14.4 dBov, flat frequency response.
+- TEST18.INP - Female speech, ambient noise, active speech level: -26.0 dBov, modified IRS frequency response, with many zero frames.
+- TEST19.INP - Male speech, ambient noise, active speech level: -36.0 dBov, modified IRS frequency response, with many zero frames.
+- TEST20.INP - Sequence for exercising the LPC vector quantisation codebooks and ROM tables of the codec.
+
+The TEST0.INP and TEST1.INP sequences were designed to test the pitch lag of the GSM enhanced full rate speech encoder. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST0.COD and TEST1.COD sequences, respectively.
+
+The TEST2.INP and TEST3.INP sequences are particularly suited for testing the LPC analysis, as well as for finding saturation problems. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST2.COD and TEST3.COD sequences, respectively.
+
+The TEST4.INP and TEST5.INP sequences contain a lot of low-frequency components. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST4.COD and TEST5.COD sequences, respectively.
+
+The TEST18.INP and TEST19.INP sequences contain some “all zeros” frames (silence) in between segments of speech. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST18.COD and TEST19.COD sequences, respectively.
+
+The TEST20.INP sequence was designed to force the encoder to select each of the LPC code indices and each but one of the the ROM table indices of the codec.
+
+The remaining sequences (TEST6.INP to TEST17.INP) were selected on the basis of bringing various input characteristics (background noise) and levels to the test sequence set. In a correct implementation, the resulting speech encoder output parameters shall be identical to those specified in the TEST6.COD to TEST17.COD sequences, respectively.
+
+### 6.2.2 Speech decoder test sequences
+
+Twenty-one speech decoder input sequences TESTXX.DEC (XX = 0..20) are provided. These are derived from the corresponding TESTXX.INP sequences. In a correct implementation, the resulting speech decoder output shall be identical to the corresponding TESTXX.OUT sequences.
+
+### 6.2.3 Codec homing sequence
+
+In addition to the test sequences described above, two homing sequences are provided to assist in codec testing. TEST21.INP contains one encoder-homing-frame. TEST21.DEC contains one decoder-homing-frame. The use of these sequences is described in GSM 06.51 [8].
+
+**Table 5: Location and size of speech codec test sequences**
+
+| Disk No. | File Name  | No. of frames | Size (bytes) |
+|----------|------------|---------------|--------------|
+| 1/8      | TEST0.INP  | 285           | 91 200       |
+| 1/8      | TEST0.COD  |               | 140 220      |
+| 1/8      | TEST0.DEC  |               | 140 790      |
+| 1/8      | TEST0.OUT  |               | 91 200       |
+| 1/8      | TEST1.INP  | 285           | 91 200       |
+| 1/8      | TEST1.COD  |               | 140 220      |
+| 1/8      | TEST1.DEC  |               | 140 790      |
+| 1/8      | TEST1.OUT  |               | 91 200       |
+| 1/8      | TEST2.INP  | 402           | 128 640      |
+| 1/8      | TEST2.COD  |               | 197 784      |
+| 1/8      | TEST2.DEC  |               | 198 588      |
+| 1/8      | TEST2.OUT  |               | 128 640      |
+| 1/8      | TEST3.INP  | 402           | 128 640      |
+| 1/8      | TEST3.COD  |               | 197 784      |
+| 1/8      | TEST3.DEC  |               | 198 588      |
+| 1/8      | TEST3.OUT  |               | 128 640      |
+| 1/8      | TEST4.INP  | 301           | 96 320       |
+| 1/8      | TEST4.COD  |               | 148 092      |
+| 1/8      | TEST4.DEC  |               | 148 694      |
+| 1/8      | TEST4.OUT  |               | 96 320       |
+| 1/8      | TEST5.INP  | 224           | 71 680       |
+| 1/8      | TEST5.COD  |               | 110 208      |
+| 1/8      | TEST5.DEC  |               | 110 656      |
+| 1/8      | TEST5.OUT  |               | 71 680       |
+| 1/8      | TEST6.INP  | 335           | 107 200      |
+| 1/8      | TEST6.COD  |               | 164 820      |
+| 1/8      | TEST6.DEC  |               | 165 490      |
+| 1/8      | TEST6.OUT  |               | 107 200      |
+| 1/8      | TEST7.INP  | 363           | 116 160      |
+| 1/8      | TEST7.COD  |               | 178 596      |
+| 1/8      | TEST7.DEC  |               | 179 322      |
+| 1/8      | TEST7.OUT  |               | 116 160      |
+| 1/8      | TEST8.INP  | 340           | 108 800      |
+| 1/8      | TEST8.COD  |               | 167 280      |
+| 1/8      | TEST8.DEC  |               | 167 960      |
+| 1/8      | TEST8.OUT  |               | 108 800      |
+| 2/8      | TEST9.INP  | 407           | 130 240      |
+| 2/8      | TEST9.COD  |               | 200 244      |
+| 2/8      | TEST9.DEC  |               | 201 058      |
+| 2/8      | TEST9.OUT  |               | 130 240      |
+| 2/8      | TEST10.INP | 383           | 122 560      |
+| 2/8      | TEST10.COD |               | 188 436      |
+| 2/8      | TEST10.DEC |               | 189 202      |
+| 2/8      | TEST10.OUT |               | 122 560      |
+| 2/8      | TEST11.INP | 367           | 117 440      |
+| 2/8      | TEST11.COD |               | 180 564      |
+| 2/8      | TEST11.DEC |               | 181 298      |
+| 2/8      | TEST11.OUT |               | 117 440      |
+| 2/8      | TEST12.INP | 298           | 95 360       |
+| 2/8      | TEST12.COD |               | 146 616      |
+| 2/8      | TEST12.DEC |               | 147 212      |
+| 2/8      | TEST12.OUT |               | 95 360       |
+| 2/8      | TEST13.INP | 338           | 108 160      |
+| 2/8      | TEST13.COD |               | 166 296      |
+| 2/8      | TEST13.DEC |               | 166 972      |
+| 2/8      | TEST13.OUT |               | 108 160      |
+| 2/8      | TEST14.INP | 318           | 101 760      |
+| 2/8      | TEST14.COD |               | 156 456      |
+| 2/8      | TEST14.DEC |               | 157 092      |
+| 2/8      | TEST14.OUT |               | 101 760      |
+
+(continued)
+
+**Table 5 (concluded): Location and size of speech codec test sequences**
+
+| Disk No. | File Name  | No. of frames | Size (bytes) |
+|----------|------------|---------------|--------------|
+| 2/8      | TEST15.INP | 328           | 104 960      |
+| 2/8      | TEST15.COD |               | 161 376      |
+| 2/8      | TEST15.DEC |               | 162 032      |
+| 2/8      | TEST15.OUT |               | 104 960      |
+| 2/8      | TEST16.INP | 354           | 113 280      |
+| 2/8      | TEST16.COD |               | 174 168      |
+| 2/8      | TEST16.DEC |               | 174 876      |
+| 2/8      | TEST16.OUT |               | 113 280      |
+| 3/8      | TEST17.INP | 316           | 101 120      |
+| 3/8      | TEST17.COD |               | 155 472      |
+| 3/8      | TEST17.DEC |               | 156 104      |
+| 3/8      | TEST17.OUT |               | 101 120      |
+| 3/8      | TEST18.INP | 402           | 128 640      |
+| 3/8      | TEST18.COD |               | 197 784      |
+| 3/8      | TEST18.DEC |               | 198 588      |
+| 3/8      | TEST18.OUT |               | 128 640      |
+| 3/8      | TEST19.INP | 402           | 128 640      |
+| 3/8      | TEST19.COD |               | 197 784      |
+| 3/8      | TEST19.DEC |               | 198 588      |
+| 3/8      | TEST19.OUT |               | 128 640      |
+| 3/8      | TEST20.INP | 631           | 201 920      |
+| 3/8      | TEST20.COD |               | 310 452      |
+| 3/8      | TEST20.DEC |               | 311 714      |
+| 3/8      | TEST20.OUT |               | 201 920      |
+| 3/8      | TEST21.INP | 1             | 320          |
+| 3/8      | TEST21.DEC |               | 494          |
+
+# 7 DTX test sequences
+
+This subclause describes the test sequences designed to exercise the VAD algorithm (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and discontinuous transmission (GSM 06.81 [5]).
+
+## 7.1 Codec configuration
+
+The VAD, comfort noise and discontinuous transmission shall be tested in conjunction with the speech encoder (GSM 06.60 [2]). The speech encoder shall be configured to operate in the DTX mode defined in GSM 06.62 [4].
+
+## 7.2 DTX test sequences
+
+Each DTX test sequence consists of four files:
+
+- Files for input to the GSM enhanced full rate speech encoder: \*.INP
+- Files for comparison with the encoder output: \*.COD
+- Files for input to the GSM enhanced full rate speech decoder: \*.DEC
+- Files for comparison with the decoder output: \*.OUT
+
+The \*.DEC files are generated from the corresponding \*.COD files.
+
+In a correct implementation, the speech encoder parameters generated by the \*.INP file shall be identical to those specified in the \*.COD file; and the speech decoder output generated by the \*.DEC file shall be identical to that specified in the \*.OUT file.
+
+Table 6 lists the DTX test sequences and their size in frames.
+
+### 7.2.1 Predictor values computation
+
+The computation of the predictor values described in GSM 06.82 [6] is not tested explicitly, since the results from the computation are tested many times via the spectral comparison and threshold adaptation tests.
+
+### 7.2.2 Spectral comparison
+
+The spectral comparison algorithm described in GSM 06.82 [6] is tested by the following test sequence:
+
+- DTX01.\*
+
+### 7.2.3 Threshold adaptation
+
+The threshold adaptation algorithm described in GSM 06.82 [6] is tested by the following test sequence:
+
+- DTX02.\*
+
+### 7.2.4 Periodicity detection
+
+The periodicity detection algorithm described in GSM 06.82 [6] is tested by the following test sequence:
+
+- DTX03.\*
+
+### 7.2.5 Tone detection
+
+The tone detection algorithm described in GSM 06.82 [6] is tested by the following test sequence:
+
+- DTX04.\*
+
+### 7.2.6 Safety and initialisation
+
+This sequence checks the safety paths used to prevent zero values being passed to the norm function. It checks the functions described in the adaptive filtering and energy computation, and the prediction values computation given in GSM 06.82 [6]. This sequence also checks the initialisation of thvad and the rvad array:
+
+- DTX05.\*
+
+### 7.2.7 Comfort noise test sequence
+
+The test sequences described in sub-subclauses 7.2.2 to 7.2.6 are designed to exercise the VAD described in GSM 06.82 [6] and the discontinuous transmission described in GSM 06.81 [5]. The following test sequence is defined to exercise the comfort noise algorithm described in GSM 06.62 [4]:
+
+- DTX06.\*
+
+### 7.2.8 Real speech and tones
+
+The test sequences cannot be guaranteed to find every possible error. There is therefore a small possibility that an incorrect implementation produces the correct output for the test sequences, but fails with real signals. Consequently, an extra sequence is included, which consists of very clean speech, barely detectable speech and a swept frequency tone:
+
+- DTX07.\*
+
+NOTE: Some of the DTX test sequences contain homing frames. The DTX test sequences are therefore only suitable for testing a single transcoding.
+
+**Table 6: Location and size of DTX test sequences**
+
+| Disk No. | File Name | No. of Frames | size (bytes) |         |         |         |
+|----------|-----------|---------------|--------------|---------|---------|---------|
+|          |           |               | *.INP        | *.COD   | *.DEC   | *.OUT   |
+| 4/8      | DTX01     | 710           | 227 200      | 349 320 | 350 740 | 227 200 |
+| 4/8      | DTX02     | 933           | 298 560      | 459 036 | 460 902 | 298 560 |
+| 4/8      | DTX03     | 156           | 49 920       | 76 752  | 77 064  | 49 920  |
+| 4/8      | DTX04     | 245           | 78 400       | 120 540 | 121 030 | 78 400  |
+| 4/8      | DTX05     | 56            | 17 920       | 27 552  | 27 664  | 17 920  |
+| 4/8      | DTX06     | 771           | 246 720      | 379 332 | 380 874 | 246 720 |
+| 4/8      | DTX07     | 1188          | 380 160      | 584 496 | 586 872 | 380 160 |
+
+# 8 Sequences for finding the 20 ms framing of the GSM enhanced full rate speech encoder
+
+When testing the decoder, alignment of the test sequences used to the decoder framing is achieved by the air interface (testing of MS) or can be reached easily on the A<sub>bis</sub>-interface (testing on network side).
+
+When testing the encoder, usually there is no information available about where the encoder starts its 20 ms segments of speech input to the encoder.
+
+In the following, a procedure is described to find the 20 ms framing of the encoder using special synchronisation sequences. This procedure can be used for MS as well as for network side.
+
+Synchronisation can be achieved in two steps. First, bit synchronisation has to be found. In a second step, frame synchronisation can be determined. This procedure takes advantage of the codec homing feature of the enhanced full rate codec, which puts the codec in a defined home state after the reception of the first homing frame. On the reception of further homing frames, the output of the codec is predefined and can be triggered to.
+
+## 8.1 Bit synchronisation
+
+The input to the speech encoder is a series of 13 bit long words (104 kbits/s, 13 bit linear PCM). When starting to test the speech encoder, no knowledge is available on bit synchronisation, i.e., where the encoder expects its least significant bits, and where it expects the most significant bits.
+
+The encoder homing frame consists of 160 samples, all set to zero with the exception of the least significant bit, which is set to one (0 0000 0000 0001 binary, or 0x0008 hex if written into 16 bit words left justified). If two such encoder homing frames are input to the encoder consecutively, the decoder homing frame is expected at the output as a reaction of the second encoder homing frame.
+
+Since there are only 13 possibilities for bit synchronisation, after a maximum of 13 trials bit synchronisation can be reached. In each trial three consecutive encoder homing frames are input to the encoder. If the decoder homing frame is not detected at the output, the relative bit position of the three input frames is shifted by one and another trial is performed. As soon as the decoder homing frame is detected at the output, bit synchronisation is found, and the first step can be terminated.
+
+The reason why three consecutive encoder homing frames are needed is that frame synchronisation is not known at this stage. To be sure that the encoder reads two complete homing frames, three frames have to be input. Wherever the encoder has its 20 ms segmentation, it will always read at least two complete encoder homing frames.
+
+An example of the 13 different frame triplets is given in sequence BITSYNC.INP (see table 7).
+
+## 8.2 Frame synchronisation
+
+Once bit synchronisation is found, frame synchronisation can be found by inputting one special frame that delivers 160 different output frames, depending on the 160 different positions that this frame can possibly have with respect to the encoder framing.
+
+This special synchronisation frame was found by taking one input frame and shifting it through the positions 0 to 159. The corresponding 160 encoded speech frames were calculated and it was verified that all 160 output frames were
+
+different. When shifting the input synchronisation frame, the samples at the beginning were set to 0x0008 hex, which corresponds to the samples of the encoder homing frame.
+
+Before inputting this special synchronisation frame to the encoder, again the encoder has to be reset by one encoder homing frame. A second encoder homing frame is needed to provoke a decoder homing frame at the output that can be triggered to. And since the framing of the encoder is not known at that stage, three encoder homing frames have to precede the special synchronisation frame to ensure that the encoder reads at least two homing frames, and at least one decoder homing frame is produced at the output, serving as a trigger for recording.
+
+The special synchronisation frame preceded by the three encoder homing frames are given in SEQSYNC.INP. The corresponding 160 different output frames are given in SYNC000.COD through SYNC159.COD. The three digit number in the filename indicates the number of samples by which the input was retarded with respect to the encoder framing. By a corresponding shift in the opposite direction, alignment with the encoder framing can be reached.
+
+## 8.3 Formats and sizes of the synchronisation sequences
+
+### BIT SYNC.INP:
+
+This sequence consists of 13 frame triplets. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero).
+
+The size of it is therefore:
+
+$$\text{SIZE (BITSYNC.INP)} = 13 * 3 * 160 * 2 \text{ bytes} = 12480 \text{ bytes}$$
+
+### SEQSYNC.INP:
+
+This sequence consists of 3 encoder reset frames and the special synchronisation frame. It has the format of the speech encoder input test sequences (13 bit left justified with the three least significant bits set to zero).
+
+The size of it is therefore:
+
+$$\text{SIZE (SEQSYNC.INP)} = 4 * 160 * 2 \text{ bytes} = 1280 \text{ bytes}$$
+
+### SYNCXXX.COD:
+
+These sequences consist of 1 encoder output frame each. They have the format of the speech encoder output test sequences (16 bit words right justified). The values of the VAD and SP flags are set to one in these files.
+
+The size of them is therefore:
+
+$$\text{SIZE (SYNCXXX.COD)} = (244 + 2) * 2 \text{ bytes} = 492 \text{ bytes}$$
+
+Table 7 summarises this information.
+
+**Table 7: Location, size and justification of synchronisation sequences**
+
+| Disk No. | Purpose of Sequence            | Name of Sequence | No. of Frames | Size in Bytes | Justification |
+|----------|--------------------------------|------------------|---------------|---------------|---------------|
+| 3/8      | Bit Synchronisation            | BITSYNC.INP      | 39            | 1 2480        | Left          |
+| 3/8      | Frame Synchronisation (input)  | SEQSYNC.INP      | 4             | 1 280         | Left          |
+| 3/8      | Frame Synchronisation (output) | SYNC000.COD      | 1             | 492           | Right         |
+| 3/8      |                                | SYNC001.COD      | 1             | 492           | Right         |
+| 3/8      |                                | SYNC002.COD      | 1             | 492           | Right         |
+| "        |                                | "                | "             | "             | "             |
+| "        |                                | "                | "             | "             | "             |
+| "        |                                | "                | "             | "             | "             |
+| "        |                                | "                | "             | "             | "             |
+| 3/8      |                                | SYNC159.COD      | 1             | 492           | Right         |
+
+# --- 9 Trau Testing with 8 Bit A- and $\mu$ -law PCM Test Sequences
+
+In the previous clauses, tests for the transcoder in the TRAU are described, using 13 bit linear test sequences. However, these 13 bit test sequences require a special interface in the TRAU and do not allow testing in the field. In most cases the TRAU has to be set in special mode before testing.
+
+As an alternative, the speech codec tests in the TRAU can be performed using A- or  $\mu$ -law compressed 8 bit PCM test sequences on the A interface. For this purpose modified input test sequences (\*-X.INP) are generated from the original sequences by A or  $\mu$  law compression. As an input to the encoder they result in modified encoder output sequences (\*-X.COD). The same \*.dec decoder input sequences as in subclause 6.2.2. are then used to produce the output sequences \*-X.OUT, which are A- or  $\mu$  compressed.
+
+The A- and  $\mu$ -law compression and decompression does not change the homing frames at the encoder input. The format of all A- and  $\mu$ -law PCM files \*-X.INP and \*-X.OUT is one sample (8 bit) per byte. The format of all other files is as described in clause 5.
+
+All files are contained in archive ts\_100725v080100p0.zip which accompanies the present document. The 'X' in the tables below with the filenames stands for A (A-law) and U ( $\mu$ -law), respectively. The decoder input files \*.dec are the same as in table 5 and are not described in this clause.
+
+**Table 8: Location and size of compressed 8 bit PCM speech codec test sequences**
+
+| Disk No. | File Name    | No. of frames | Size (bytes) |
+|----------|--------------|---------------|--------------|
+| 5-8/8    | TEST0-X.INP  | 285           | 45 600       |
+| 5-8/8    | TEST0-X.COD  |               | 140 220      |
+| 5-8/8    | TEST0-X.OUT  |               | 45 600       |
+| 5-8/8    | TEST1-X.INP  | 285           | 45 600       |
+| 5-8/8    | TEST1-X.COD  |               | 140 220      |
+| 5-8/8    | TEST1-X.OUT  |               | 45 600       |
+| 5-8/8    | TEST2-X.INP  | 402           | 64 320       |
+| 5-8/8    | TEST2-X.COD  |               | 197 784      |
+| 5-8/8    | TEST2-X.OUT  |               | 64 320       |
+| 5-8/8    | TEST3-X.INP  | 402           | 64 320       |
+| 5-8/8    | TEST3-X.COD  |               | 197 784      |
+| 5-8/8    | TEST3-X.OUT  |               | 64 320       |
+| 5-8/8    | TEST4-X.INP  | 301           | 48 160       |
+| 5-8/8    | TEST4-X.COD  |               | 148 092      |
+| 5-8/8    | TEST4-X.OUT  |               | 48 160       |
+| 5-8/8    | TEST5-X.INP  | 224           | 35 840       |
+| 5-8/8    | TEST5-X.COD  |               | 110 208      |
+| 5-8/8    | TEST5-X.OUT  |               | 35 840       |
+| 5-8/8    | TEST6-X.INP  | 335           | 53 600       |
+| 5-8/8    | TEST6-X.COD  |               | 164 820      |
+| 5-8/8    | TEST6-X.OUT  |               | 53 600       |
+| 5-8/8    | TEST7-X.INP  | 363           | 58 080       |
+| 5-8/8    | TEST7-X.COD  |               | 178 596      |
+| 5-8/8    | TEST7-X.OUT  |               | 58 080       |
+| 5-8/8    | TEST8-X.INP  | 340           | 54 400       |
+| 5-8/8    | TEST8-X.COD  |               | 167 280      |
+| 5-8/8    | TEST8-X.OUT  |               | 54 400       |
+| 5-8/8    | TEST9-X.INP  | 407           | 65 120       |
+| 5-8/8    | TEST9-X.COD  |               | 200 244      |
+| 5-8/8    | TEST9-X.OUT  |               | 65 120       |
+| 5-8/8    | TEST10-X.INP | 383           | 61 280       |
+| 5-8/8    | TEST10-X.COD |               | 188 436      |
+| 5-8/8    | TEST10-X.OUT |               | 61 280       |
+| 5-8/8    | TEST11-X.INP | 367           | 58 720       |
+| 5-8/8    | TEST11-X.COD |               | 180 564      |
+| 5-8/8    | TEST11-X.OUT |               | 58 720       |
+| 5-8/8    | TEST12-X.INP | 298           | 47 680       |
+| 5-8/8    | TEST12-X.COD |               | 146 616      |
+| 5-8/8    | TEST12-X.OUT |               | 47 680       |
+| 5-8/8    | TEST13-X.INP | 338           | 54 080       |
+| 5-8/8    | TEST13-X.COD |               | 166 296      |
+| 5-8/8    | TEST13-X.OUT |               | 54 080       |
+| 5-8/8    | TEST14-X.INP | 318           | 50 880       |
+| 5-8/8    | TEST14-X.COD |               | 156 456      |
+| 5-8/8    | TEST14-X.OUT |               | 50 880       |
+| 5-8/8    | TEST15-X.INP | 328           | 52 480       |
+| 5-8/8    | TEST15-X.COD |               | 161 376      |
+| 5-8/8    | TEST15-X.OUT |               | 52 480       |
+| 5-8/8    | TEST16-X.INP | 354           | 56 640       |
+| 5-8/8    | TEST16-X.COD |               | 174 168      |
+| 5-8/8    | TEST16-X.OUT |               | 56 640       |
+| 5-8/8    | TEST17-X.INP | 316           | 50 560       |
+| 5-8/8    | TEST17-X.COD |               | 155 472      |
+| 5-8/8    | TEST17-X.OUT |               | 50 560       |
+| 5-8/8    | TEST18-X.INP | 402           | 64 320       |
+| 5-8/8    | TEST18-X.COD |               | 197 784      |
+| 5-8/8    | TEST18-X.OUT |               | 64 320       |
+| 5-8/8    | TEST19-X.INP | 402           | 64 320       |
+| 5-8/8    | TEST19-X.COD |               | 197 784      |
+| 5-8/8    | TEST19-X.OUT |               | 64 320       |
+| 5-8/8    | TEST20-X.INP | 631           | 100 960      |
+| 5-8/8    | TEST20-X.COD |               | 310 452      |
+| 5-8/8    | TEST20-X.OUT |               | 100 960      |
+| 5-8/8    | TEST21-X.INP | 1             | 160          |
+
+**Table 9: Location and size of compressed 8 bit PCM DTX test sequences**
+
+| Disk No. | File Name | No. of Frames | size bytes |         |         |
+|----------|-----------|---------------|------------|---------|---------|
+|          |           |               | *.INP      | *.COD   | *.OUT   |
+| 5-8/8    | DTX01-X   | 710           | 113 600    | 349 320 | 113 600 |
+| 5-8/8    | DTX02-X   | 933           | 149 280    | 459 036 | 149 280 |
+| 5-8/8    | DTX03-X   | 156           | 24 960     | 76 752  | 24 960  |
+| 5-8/8    | DTX04-X   | 245           | 39 200     | 120 540 | 39 200  |
+| 5-8/8    | DTX05-X   | 56            | 8 960      | 27 552  | 8 960   |
+| 5-8/8    | DTX06-X   | 771           | 123 360    | 379 332 | 123 360 |
+| 5-8/8    | DTX07-X   | 1188          | 190 080    | 584 496 | 190 080 |
+
+In addition to the test sequences above, special input (seqsyncX.inp) and output (syncxxxX.cod) sequences for frame synchronization are provided. The X again stands for A and  $\mu$  law compressed PCM. The synchronization procedure is described in clause 8.
+
+**Table 10: Location, size and justification of compressed 8 bit PCM test sequences**
+
+| Disk No. | Purpose of Sequence            | Name of Sequence | No. of Frames | Size in Bytes | Justification |
+|----------|--------------------------------|------------------|---------------|---------------|---------------|
+| 5-8/8    | Frame Synchronisation (input)  | SEQSYNCX.INP     | 4             | 640           | -             |
+| 5-8/8    | Frame Synchronisation (output) | SYNC000X.COD     | 1             | 492           | Right         |
+| 5-8/8    |                                | SYNC001X.COD     | 1             | 492           | Right         |
+| 5-8/8    |                                | SYNC002X.COD     | 1             | 492           | Right         |
+| "        |                                | "                | "             | "             | "             |
+| "        |                                | "                | "             | "             | "             |
+| "        |                                | "                | "             | "             | "             |
+| 5-8/8    |                                | SYNC159X.COD     | 1             | 492           | Right         |
+
+|       |                                |              |   |     |       |
+|-------|--------------------------------|--------------|---|-----|-------|
+| 5-8/8 | Frame Synchronisation (output) | SYNC000X.COD | 1 | 492 | Right |
+| 5-8/8 |                                | SYNC001X.COD | 1 | 492 | Right |
+| 5-8/8 |                                | SYNC002X.COD | 1 | 492 | Right |
+| "     |                                | "            | " | "   | "     |
+| "     |                                | "            | " | "   | "     |
+| "     |                                | "            | " | "   | "     |
+| 5-8/8 |                                | SYNC159X.COD | 1 | 492 | Right |
+
+# 10 Alternative Enhanced Full Rate implementation using the Adaptive Multi Rate 12.2 kbit/s mode
+
+The 12.2 kbit/s mode of the Adaptive Multi Rate speech coder described in TS 26.071 is functionally equivalent to the GSM Enhanced Full Rate speech coder. An alternative implementation of the Enhanced Full Rate speech service based on the 12.2 kbit/s mode of the Adaptive Multi Rate coder is allowed. Alternative implementations shall implement the functionality specified in TS 26.071 for the 12.2 kbit/s mode, with the difference that the DTX transmission format from GSM 06.81, the comfort noise generation from GSM 06.62 and the decoder homing frame from GSM 06.60 shall be used.
+
+The test sequences are derived from the corresponding AMR test sequences. The modifications that were made and the use of the respective sequences are described below. The input sequences are identical to the AMR test input sequences \*.inp.
+
+# Speech codec test sequences
+
+- with DTX disabled
+  - t00.inp ... t22.inp (encoder input, from TS 26.074)
+  - t00\_efr.cod ... t22\_efr.cod (encoder output)
+
+t00\_efr.dec ... t22\_efr.dec (decoder input)
+
+t00\_efr.out ... t22\_efr.out (decoder output)
+
+- with DTX enabled, VAD option 1
+
+Dtx1.inp ... Dtx4.inp (encoder input, from TS 26.074)
+
+Dtx1\_efr.cod ... Dtx4\_efr.cod (encoder output)
+
+Dtx1\_efr.dec ... Dtx4\_efr.dec (decoder input)
+
+Dtx1\_efr.out ... Dtx4\_efr.out (decoder output)
+
+- with DTX enabled, VAD option 2
+
+Dt21.inp .... Dt24.inp (encoder input, from TS 26.074)
+
+Dt21\_efr.cod ... Dt24\_efr.cod (encoder output)
+
+Dt21\_efr.dec ... Dt24\_efr.dec (decoder input)
+
+Dt21\_efr.out ... Dt24\_efr.out (decoder output)
+
+The format of the \*.cod files is identical to the GSM\_EFR \*.cod file format (244 Data Bits, VadFlag, SpFlag equaling 246 Words per 20ms frame). The format of the \*.dec files is identical to the GSM\_EFR \*.dec file format, that is (Bfi, 244 Data Bits, Sid, Taf equaling 247 Words per frame (20ms).
+
+In summary, the differences to the AMR Mode MR122 test sequences are:
+
+- DTX handling (VadFlag and SpFlag instead of TxType; different SID frames)
+- Decoder homing frame (Decoder homing frame for GSM\_EFR is different than for AMR MR122).
+
+# Annex A (informative): Change History
+
+| Change history |           |         |                  |             |                                                        |
+|----------------|-----------|---------|------------------|-------------|--------------------------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments                                       |
+| SMG#23         |           |         |                  | 4.0.1       | ETSI Publication                                       |
+| SMG#23         |           |         |                  | 5.1.0       | Release 1996 version                                   |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version                                   |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version                                   |
+|                |           |         |                  | 7.0.1       | Version update to 7.0.1 for Publication                |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version                                   |
+| SMG#32         | P-00-274  | A006    | 4 and new 10     | 8.1.0       | Alternative EFR implementation using the AMR 12.2 mode |
+
+| Change history |         |           |      |     |                                                               |        |        |
+|----------------|---------|-----------|------|-----|---------------------------------------------------------------|--------|--------|
+| Date           | TSG SA# | TSG Doc.  | CR   | Rev | Subject/Comment                                               | Old    | New    |
+| 12-2000        | 10      | SP-000573 | A011 |     | Correction to the test vectors of the alternative EFR version | 8.1.0  | 8.2.0  |
+| 03-2001        | 11      |           |      |     | Version for Release 4                                         |        | 4.0.0  |
+| 06-2002        | 16      |           |      |     | Version for Release 5                                         | 4.0.0  | 5.0.0  |
+| 12-2004        | 26      |           |      |     | Version for Release 6                                         | 5.0.0  | 6.0.0  |
+| 06-2007        | 36      |           |      |     | Version for Release 7                                         | 6.0.0  | 7.0.0  |
+| 12-2008        | 42      |           |      |     | Version for Release 8                                         | 7.0.0  | 8.0.0  |
+| 12-2009        | 46      |           |      |     | Version for Release 9                                         | 8.0.0  | 9.0.0  |
+| 03-2011        | 51      |           |      |     | Version for Release 10                                        | 9.0.0  | 10.0.0 |
+| 09-2012        | 57      |           |      |     | Version for Release 11                                        | 10.0.0 | 11.0.0 |
+| 09-2014        | 65      |           |      |     | Version for Release 12                                        | 11.0.0 | 12.0.0 |
+| 12-2015        | 70      |           |      |     | Version for Release 13                                        | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46055/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-16/46_series/46055/1c427123350e0e73e2a109b79069314b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..159102014575826d9c91db42078a1c8020ce161b
--- /dev/null
+++ b/marked/Rel-16/46_series/46055/1c427123350e0e73e2a109b79069314b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c2b44544a6516adf7bd69344ae0d669441b6b9b80c59a22a32d65ec0e8acb376
+size 60626
diff --git a/marked/Rel-16/46_series/46055/c19f313a256eec398179c6859dc32a5b_img.jpg b/marked/Rel-16/46_series/46055/c19f313a256eec398179c6859dc32a5b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..57fc95cf5d93787d3c69322bb2ebdd2a95813dec
--- /dev/null
+++ b/marked/Rel-16/46_series/46055/c19f313a256eec398179c6859dc32a5b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d4d12f93b2bf8ffdf5b3a161593dbc724378713cd5e1b5233f5c8c81ffad090f
+size 30484
diff --git a/marked/Rel-16/46_series/46055/raw.md b/marked/Rel-16/46_series/46055/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f4d573d029f917d1694f92aa4c23e4eccb8c3cc
--- /dev/null
+++ b/marked/Rel-16/46_series/46055/raw.md
@@ -0,0 +1,874 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                                 |           |
+|-------------------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                                  | 4         |
+| Introduction .....                                                                              | 5         |
+| 1 Scope.....                                                                                    | 7         |
+| 2 References.....                                                                               | 7         |
+| 3 Abbreviations .....                                                                           | 7         |
+| 4 Quality under error (EP0 – EP3) and tandeming conditions (Exp Number 1 and Exp Number 5)..... | 8         |
+| 5 Quality under background noise conditions (Exp Number 2 and Exp Number 3).....                | 9         |
+| 6 Talker dependency (Exp Number 4).....                                                         | 9         |
+| 7 DTX system .....                                                                              | 9         |
+| 7.1 Channel activity in DTX mode .....                                                          | 9         |
+| 7.1.1 Test procedure .....                                                                      | 9         |
+| 7.1.2 Speech channel activity .....                                                             | 9         |
+| 7.1.3 Level compensation.....                                                                   | 9         |
+| 7.1.4 Interleaving compensation.....                                                            | 10        |
+| 7.1.5 Estimated mean TDMA channel activity .....                                                | 10        |
+| 7.2 DTX/CNI Informal Expert Listening tests.....                                                | 10        |
+| 7.2.1 Introduction .....                                                                        | 10        |
+| 7.2.2 Test environment.....                                                                     | 10        |
+| 7.2.3 Results .....                                                                             | 10        |
+| 8 Performance with DTMF tones.....                                                              | 10        |
+| 8.1 Introduction .....                                                                          | 10        |
+| 8.2 Test environment.....                                                                       | 11        |
+| 8.3 Results .....                                                                               | 11        |
+| 9 Network information tones .....                                                               | 12        |
+| 10 Performance with special input signals.....                                                  | 12        |
+| 10.1 Music signals.....                                                                         | 12        |
+| 10.2 Noise signals .....                                                                        | 13        |
+| 11 Performance with different languages .....                                                   | 13        |
+| 12 Delay .....                                                                                  | 14        |
+| 13 Frequency response.....                                                                      | 17        |
+| 13.1 Introduction .....                                                                         | 17        |
+| 13.2 Test environment.....                                                                      | 17        |
+| 13.3 Results .....                                                                              | 17        |
+| 14 Complexity .....                                                                             | 18        |
+| 15 Summary of the results from the subjective testing.....                                      | 19        |
+| <b>Annex A: Summary of results (lab by lab).....</b>                                            | <b>21</b> |
+| A.1 Quality under Error and tandeming conditions.....                                           | 21        |
+| A.2 Quality under Background noise conditions.....                                              | 23        |
+| A.3 Quality for Talker Dependency (DMOS and SD) .....                                           | 24        |
+| Annex B: Change history .....                                                                   | 25        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Introduction
+
+The SMG2-Speech experts Group (SEG) started its activity early in 1995 for the standardization of an Enhanced Full Rate speech codec. The Group produced a test plan for the first phase of testing (pre-selection phase) which is described in permanent document SEG-4 (ETSI SMG2 SEG: SEG-4 (v 1.0) "A Subjective Pre-Selection Test Plan for the Enhanced Full Rate Speech Coding Algorithm") to assess the performance of the submitted candidates. This test plan is based on the general knowledge coming from past ITU-T and ETSI activities on codec evaluation (GSM half rate and ITU-T 8 kbit/s recent exercises for instance). At the end of this Pre-selection Phase, SMG decided to standardize the PCS 1 900 codec, known as the US-1 codec and no formal characterisation testing has been performed for the selected codec.
+
+The present document therefore reports the results from the Pre-selection and Verification Phase of testing only. Consequently, the results reported here are less detailed, and the confidence intervals for them are wider, than those obtained for the GSM half rate standardization (GSM 06.08, [3]) where specific and detailed characterisation testing was performed. In addition, not all laboratories followed the same pre-selection test plan, further complicating the interpretation of the results.
+
+The following experiments included in SEG-4 were carried out by several laboratories in the Pre-selection Phase:
+
+- Experiment 1: Quality under error and tandeming conditions (A-law, Modified IRS);
+- Experiment 2: Quality under background noise conditions (Vehicular noise, UPCM, NoIRS);
+- Experiment 3: Quality under background noise conditions (Background music, UPCM, NoIRS);
+- Experiment 4: Talker Dependency (UPCM, NoIRS);
+- Experiment 5: Quality under high error conditions –EP3 (A-law, Modified IRS).
+
+A practical 'indirect' method of performance comparison between different results was adopted utilising the Modulated Noise Reference Unit (MNRU) (see note) as a reference degradation. The MNRU provides the additional function of allowing normalisation of results across different laboratories carrying out the same experiment, through the conversion of MOS scores to Equivalent Q (dB). The Q (dB) values introduced in a test normally range from 0 to 50 dB. In SEG-4, both Experiment#1 and Experiment#5 on error conditions covers this range, the other experiments do not.
+
+NOTE: The MNRU is a device designed for producing speech correlated noise that sounds subjectively like the quantising noise produced by log-companded PCM codecs. The device is subjectively calibrated for Mean Opinion Scores (MOS) against Q dB (where Q is the ratio of the speech to speech-correlated noise power). The 'Equivalent Q' of the codecs under test can be found from the corresponding MOS on the calibration curve of the MNRU (S-shaped curve).
+
+Only four laboratories ran tests which followed the Pre-selection Test Plan described in SEG-4 (BT/lab1, CNET/lab2, Tele Denmark/lab3, NEC/lab4). MOTOROLA/lab5 participated in the Pre-selection Phase but their experiments did not comply with SEG-4. TI/lab8 ran one experiment only from SEG-4. Results produced by COMSAT/lab6 following a NOKIA-designed test plan are part of standardization of the codec in North America and NOKIA/lab7 performed complementary experiments during the ETSI Pre-selection Phase.
+
+As no further analysis have been undertaken to allow the averaging of scores across the different laboratories, results are reported in the annex on a laboratory-by-laboratory basis. For error and tandeming conditions, results are reported in terms of Equivalent Q (dB) values. For background noise conditions and talker dependency, results are reported in terms of DMOS values with either Confidence Interval (CI) or Standard Deviation (SD) as there is insufficient data available to normalise across laboratories via MNRU conditions.
+
+The quality performance of the EFR codec is compared to High and Low references introduced in permanent documents SEG-3 (ETSI SMG2 SEG: SEG-3 "Selection Criteria for the Enhanced Full Rate Speech Coding Algorithm – Speech Quality Requirements") and SEG-4 (ETSI SMG2 SEG: SEG-4 (v 1.0) "A Subjective Pre-Selection Test Plan for the Enhanced Full Rate Speech Coding Algorithm", Section 7). These references were chosen as representative of the "minimum" and "objective" performance targets respectively, and are reported in table 1.
+
+**Table 1: References per condition: High Ref., Low Ref. And G.728**
+
+| <b>EXPERIMENTS<br/>(SEG-4)</b> | <b>Conditions</b> | <b>High Ref</b> | <b>Low Ref</b>      |
+|--------------------------------|-------------------|-----------------|---------------------|
+| EXP#1                          | EP0               | G.728           | G.728               |
+| EXP#1                          | EP1               | MNRU 24 dB      | TCH-FS (EP1)        |
+| EXP#1                          | EP2               | TCH-FS (EP1)    | TCH-FS (EP2)        |
+| EXP#5                          | EP3               | TCH-FS (EP2)    | TCH-FS (EP3)        |
+| EXP#1                          | EP0 (tandem)      | G.728           | G.728               |
+| EXP#1                          | EP1 (tandem)      | TCH-FS (EP1)    | TCH-FS (EP1 tandem) |
+| EXP#2                          | Vehicle 10        | G.728           | G.728               |
+| EXP#3                          | Music 20          | G.728           | G.728               |
+| EXP#4                          | Male Talkers      | G.728           | G.728               |
+| EXP#4                          | Female Talkers    | G.728           | G.728               |
+| EXP#4                          | Children          | G.728           | G.728               |
+
+A figure showing the general trend of the EFR behaviour for error conditions in noise-free environment, compared to the high (G.728) and low (TCH-FS) references is added to individual laboratories' quantitative results (figure 15). The general quality performance of the EFR codec is summarised in table 15.
+
+In the Verification Phase, the behaviour of the EFR codec under the following test conditions was tested:
+
+- behaviour of the DTX System;
+- performance with DTMF tones;
+- performance with network information tones;
+- performance with special input signals;
+- performance with music signals;
+- performance with noise signals;
+- performance with different languages;
+- delay of the TCH-EFR;
+- frequency response;
+- complexity.
+
+The results of these tests are also included in this report under the respective clauses.
+
+Furthermore, the EFR codec was checked for correct functioning for the following items:
+
+- test of overload point;
+- SID frame encoding;
+- muting behaviour;
+- idle channel behaviour.
+
+No artefact or malfunctioning was detected for these items.
+
+# --- 1 Scope
+
+The present document gives background information on the performance of the GSM enhanced full rate speech codec. Experimental results from the Pre-selection and Verification tests carried out during the standardization process by the SEG (Speech Expert Group) are reported to give a more detailed picture of the behaviour of the GSM enhanced full rate speech codec under different conditions of operation.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+- For a specific reference, subsequent revisions do not apply.
+
+For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+
+- [1] GSM 03.05: "Digital cellular telecommunications system (Phase 2+); Technical performance objectives".
+- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
+- [3] GSM 06.08: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Performance of the GSM half rate speech codec".
+- [4] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech transcoding".
+- [5] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech transcoding".
+
+# --- 3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|       |                                                                             |
+|-------|-----------------------------------------------------------------------------|
+| A/D   | Analogue to Digital                                                         |
+| ADPCM | Adaptive Differential Pulse Code Modulation                                 |
+| ACR   | Absolute Category Rating                                                    |
+| BSC   | Base Station Controller                                                     |
+| BTS   | Base Transceiver Station                                                    |
+| C/I   | Carrier-to-Interferer ratio                                                 |
+| CI    | Confidence Interval                                                         |
+| CNI   | Comfort Noise Insertion                                                     |
+| CRC   | Cyclic Redundancy Check                                                     |
+| D/A   | Digital to Analogue                                                         |
+| DAT   | Digital Audio Tape                                                          |
+| DCR   | Degradation Category Rating                                                 |
+| DSP   | Digital Signal Processor                                                    |
+| DTMF  | Dual Tone Multi Frequency                                                   |
+| DTX   | Discontinuous Transmission for power consumption and interference reduction |
+| EFR   | Enhanced Full Rate                                                          |
+| ESP   | Product of E (Efficiency), S (Speed) and P (Percentage of Power) of the DSP |
+| FR    | Full Rate                                                                   |
+| GBER  | Average gross bit error rate                                                |
+| GSM   | Global System for Mobile communications                                     |
+| HR    | Half Rate                                                                   |
+
+|          |                                                                                   |
+|----------|-----------------------------------------------------------------------------------|
+| IRS      | Intermediate Reference System, No IRS= rather flat                                |
+| ITU-T    | International Telecommunication Union – Telecommunications Standardization Sector |
+| MNRU     | Modulated Noise Reference Unit                                                    |
+| Mod. IRS | Modified IRS                                                                      |
+| MOPS     | Million of Operation per Seconds                                                  |
+| MOS      | Mean Opinion Score                                                                |
+| MS       | Mobile Station                                                                    |
+| MSC      | Mobile Switching Centre                                                           |
+| PCM      | Pulse Code Modulation                                                             |
+| PSTN     | Public Switched Telecommunications Network                                        |
+| Q        | Speech-to-speech correlated noise power ratio in dB                               |
+| SD       | Standard Deviation                                                                |
+| SEG      | Speech Expert Group                                                               |
+| SID      | Silence Descriptor                                                                |
+| SMG      | Special Mobile Group                                                              |
+| TCH-EFS  | Traffic Channel Enhanced Full rate Speech                                         |
+| TCH-FS   | Traffic Channel Full rate Speech                                                  |
+| TCH-HS   | Traffic Channel Half rate Speech                                                  |
+| TDMA     | Time Division Multiple Access                                                     |
+| TMOPS    | True Million of Operation per Seconds                                             |
+| UPCM     | Uniform or Linear PCM                                                             |
+| VAD      | Voice Activity Detector                                                           |
+| WMOPS    | Weighted Million of Operations per Seconds                                        |
+
+Four different Error Patterns (EP0, EP1, EP2 and EP3) were used, where:
+
+|     |                                         |
+|-----|-----------------------------------------|
+| EP0 | without channel errors                  |
+| EP1 | C/I=10 dB; 5% GBER (well inside a cell) |
+| EP2 | C/I= 7 dB; 8% GBER (at a cell boundary) |
+| EP3 | C/I= 4 dB; 13% GBER (outside a cell)    |
+
+# 4 Quality under error (EP0 – EP3) and tandeming conditions (Exp Number 1 and Exp Number 5)
+
+A listening-only test was adopted using the Absolute Category Rating (ACR) method. The results are reported in terms of Equivalent Q (dB) values and Differential Q values (which compare the codec results to the High and Low references). For error and tandeming conditions, results are available from eight laboratories (lab1 to lab8). Tables of results on a lab-by-lab basis are shown in the annex of the present document (table A.1.1 to table A.1.8), negative values indicating worse performance than the reference.
+
+In general, across all laboratories, the EFR codec performs better than the reference TCH-FS for clear speech (EP0), for error conditions EP1 and EP2 and for tandeming under error EP1 conditions. For severe error condition (EP3), the performance is worse than TCH-FS in one laboratory. The EFR is equivalent to the reference G.728 (high reference) for clear speech in all laboratories. Under error conditions, the high reference threshold for severe error condition (EP3) is not met in all laboratories while the threshold for EP1 and EP2 is met for, roughly, half of the laboratories. Under tandeming, the clear condition was tested in only one laboratory where it was compared to another standard G.721; the results indicate that the performance of the EFR (EP0 tandem) is equivalent to that of G.721 (EP0). For tandeming under error condition EP1, equivalence with TCH-FS (EP1) without tandeming is demonstrated in all laboratories except one. Additional results coming from one lab only can be found in table A.1.6 (effect of input levels, other error conditions, tandeming with other standards).
+
+The advantage of the EFR compared to the actual TCH-FS is not independent of the quality of the network. As channel errors increase, this advantage is reduced. The general trend of the EFR behaviour in error conditions is shown in figure 15.
+
+# --- 5 Quality under background noise conditions (Exp Number 2 and Exp Number 3)
+
+This was assessed with a listening-only test, using the Degradation Category Rating (DCR) method. The results are reported for the EFR codec, the Reference G.728 and the TCH-FS codec in terms of DMOS values with Confidence Interval (CI). Six laboratories (lab1 to lab4, lab6 and lab7) performed this experiment, the first four complying with SEG-4 (see table A.2.1 and table A.2.2).
+
+For each laboratory, the differences in DMOS scores between the EFR codec and the Reference G.728 are of the same order as the confidence intervals for the EFR codec results, with the exception of one point (vehicle noise) in one laboratory. From this, it can be concluded that the performance of the EFR codec, under the background noise conditions tested is equivalent to that of the quality reference G.728 for all laboratories and also to G.721 (tested in one lab only). The degradation introduced by the EFR codec compared to the DIRECT connection in background noise conditions is rated between "unnoticeable" and "noticeable but not annoying". A substantial improvement is achieved over the full rate with music in the background. Additional results from one laboratory can be found in table A.2.2.
+
+# --- 6 Talker dependency (Exp Number 4)
+
+A listening-only test was used with the Degradation Category Rating (DCR) methodology. Results, available from five laboratories (lab1 to lab4 and lab7), are reported in terms of DMOS values with their associated Standard Deviation (SD) to give a measure of the spread of the scores about the averages for each gender for both the EFR codec and the Reference G.728. These experiments clearly show that the standard deviation of the scores of EFR codec for each gender is smaller than the standard deviation of the reference G.728 in each laboratory. The talker dependency performance for the EFR codec is therefore equivalent to that of G.728. Also, the gender dependency is equivalent to that of the G.728 codec. Tables of results lab-by-lab are shown in the annex (table A.3.1 to table A.3.2).
+
+# --- 7 DTX system
+
+## 7.1 Channel activity in DTX mode
+
+### 7.1.1 Test procedure
+
+A carefully selected subset of the speech material recorded for testing the half rate DTX system was processed through the codec/DTX C-language simulation. This material comprised 48 real conversations in the English, German and Italian languages. The channel activity of the system was measured for all 48 conversations, and the mean channel activity was then calculated.
+
+### 7.1.2 Speech channel activity
+
+The percentage of speech frames scheduled for transmission by the radio subsystem (subsequently referred to as the speech channel activity) varied significantly between conversations. Speech channel activities ranged from 29% to 93% for individual sides of a conversation. For this reason, it was not possible to identify any significant trends in the results with regard to terminal type and environmental conditions. The mean speech channel activity, measured over all 48 conversations, was 61 %.
+
+### 7.1.3 Level compensation
+
+After calculating the mean speech channel activity, it was found that the speech material had been processed at a level 6,5 dB below the original recorded level. However, the activity of the basic VAD algorithm rises approximately 0,5 per cent per dB increase in input level. To compensate for this, a factor of 3 % must be added to the speech channel activity estimate.
+
+### 7.1.4 Interleaving compensation
+
+The channel activity measurements were calculated on a signal frame basis. However, the use of interleaving (depth 4) implies that the TDMA activity will be approximately 2 % higher than the signal frame activity.
+
+### 7.1.5 Estimated mean TDMA channel activity
+
+The estimated mean TDMA channel activity is shown in table 7.1.5.1.
+
+**Table 7.1.5.1: Calculation of mean TDMA channel activity**
+
+|                             |      |
+|-----------------------------|------|
+| speech channel activity     | 61 % |
+| level compensation          | 3 %  |
+| interleaving compensation   | 2 %  |
+| total TDMA channel activity | 66 % |
+
+## 7.2 DTX/CNI Informal Expert Listening tests
+
+### 7.2.1 Introduction
+
+To check the performance of the DTX / CNI system of the ETSI GSM EFR codec, informal expert listening tests were done in Italian and German language. Also a very brief check of English speech samples was done. Special attention was given to clipping effects and noise.
+
+### 7.2.2 Test environment
+
+Out of the speech samples from the HR codec DTX tests, 8 conversations were selected by CSELT, Deutsche Telekom and British Telecom, respectively. These samples were processed by Nokia and recorded on a DAT, one track without VAD/DTX processing and one track with the DTX / CNI system. By comparing the non-DTX and DTX speech, the listeners could judge the degradation to be not noticeable, minor, moderate or severe. It was allowed to rewind the tape to repeat listening to critical sections. The listening device was a high quality head set in mono operation to have either track 0 or track 1 signal on both speakers.
+
+### 7.2.3 Results
+
+In all the speech samples, only two clippings were judged to be noticeable. On comfort noise insertion, conversations with almost no or low background noise were found to have no noticeable degradation. With increasing background noise, the noise related degradation was judged from minor to moderate (the latter in two sections of two conversations). The overall performance of the DTX / CNI system was seen to be fully satisfactory with mostly no or minor degradation.
+
+# --- 8 Performance with DTMF tones
+
+## 8.1 Introduction
+
+A desirable requirement for the GSM Enhanced Full Rate speech codec is a DTMF transparency not worse than the GSM Full Rate codec. For the verification of the ETSI Enhanced Full Rate codec, the DTMF transmission was tested.
+
+## 8.2 Test environment
+
+A DSP (NEC µPD77016) based PC board was used to measure the transmission of the codec under test. The DTMF software is derived from the Goertzel algorithm which allows to calculate the spectral powers of distinctive frequencies by means of a recursive digital filter scheme. The DTMF signal detection is based on "quality factors" calculated from the Distinctive Frequency Test results. Within a wide dynamic range this technique is independent from an absolute signal level. Based on the same hardware and software, PTT approvals are available with equipment of European Telecom houses.
+
+DTMF signals were tested only under ideal transmission conditions. Error patterns like in the half rate case were not simulated. In the different experiments the input signals were modified in tone and pause length, amplitude (also introducing twist, i.e. different amplitude in the two components of the tone) and frequency. In all experiments 10 tones were input to the codec. The resulting files were processed by the DTMF detector. As the minimum tone length specified for an input signal of a detector is 80 ms while the minimum output length of a DTMF generator may be smaller, a test was also done with a 60 ms tone to the codec.
+
+## 8.3 Results
+
+The test results shown in table 8.3.1 represent the detected tones from the 10 input signals. Table 8.3.2 summarises the test conditions. With input signals fully in the specified range no detection problems were observed. The shortest allowed input signal to a transmission line (80 ms) was detected 100 % in all experiments with different input levels, twist and frequency deviations. A strange effect known from the HR codec tests with long tones detected as two tones was not observed. Only in case of tones shorter than 80 ms the detection rate was down to 96 %, without a sharp decrease and without a distinct tone showing problems.
+
+As a conclusion, the codec is tested to be 100 % transparent to DTMF signals under nominal conditions. Only tones shorter than minimum input specifications of 80 ms are not fully detected. The results are better compared to the FR codec. The requirement is fulfilled.
+
+**Table 8.3.1: Results of DTMF experiments**
+
+| experiment tone | N18 | N22 | N18-22 | N22-26 | D18 | D18-22 | L 120 | L 200 | S 60 |
+|-----------------|-----|-----|--------|--------|-----|--------|-------|-------|------|
+| 1               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 2               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 9    |
+| 3               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 4               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 9    |
+| 5               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 6               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 7               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 8               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 9               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| 0               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| *               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| #               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 9    |
+| A               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| B               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 9    |
+| C               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 9    |
+| D               | 10  | 10  | 10     | 10     | 10  | 10     | 10    | 10    | 10   |
+| total d         | 160 | 160 | 160    | 160    | 160 | 160    | 160   | 160   | 155  |
+| det_rate        | 100 | 100 | 100    | 100    | 100 | 100    | 100   | 100   | 96   |
+
+In rows 1 – D the number of detected tones from 10 inputs is shown
+
+**Table 8.3.2: Conditions of above listed experiments**
+
+| experiment | N18 | N22 | N18-22 | N22-26 | D18 | D18-22 | L 120 | L 200 | S 60 |    |
+|------------|-----|-----|--------|--------|-----|--------|-------|-------|------|----|
+| tone       | 80  | 80  | 80     | 80     | 80  | 80     | 120   | 200   | 60   | ms |
+| pause      | 80  | 80  | 80     | 80     | 80  | 80     | 120   | 80    | 60   | ms |
+| r_amp      | -18 | -22 | -18    | -22    | -22 | -18    | -22   | -28   | -22  | dB |
+| c_amp      | -18 | -22 | -22    | -26    | -22 | -22    | -22   | -28   | -22  | dB |
+| delta f    | 0   | 0   | 0      | 0      | 2   | 2      | 0     | 0     | 0    | %  |
+
+r\_amp and c\_amp are the row amplitude and column amplitude respectively, dB values are relative to the overload point.
+
+# 9 Network information tones
+
+The signals shown in table 9 were first compressed by the encoder, then decompressed by the decoder, and then listened to via quality headphones using a high-quality PC audio card. The codec showed no perceivable degradation to the transmission of these PSTN network information tones both with and without the VAD/DTX system switched on. No clipping or other disturbing artefacts were noticed when DTX was enabled. Checking tones in use around the world as listed in ITU Recommendation E.180 Supplement 2 (Jan 94) indicated that this test achieves almost 100 % global coverage by simply testing UK, German, and USA tones.
+
+**Table 9: PSTN Information Tones Tested**
+
+| <i>German (no DTX)</i>                           | <i>German (with DTX)</i>                              |
+|--------------------------------------------------|-------------------------------------------------------|
+| 3 dial tones                                     | 2 dial                                                |
+| 1 ringing tone                                   | 1 ringing                                             |
+| 2 busy tones (subscriber engaged)                | 2 busy                                                |
+| 1 special information tone (number unobtainable) | 1 special information tone                            |
+| 2 congestion tones (network equipment engaged)   | 1 fax modem call setup tone sequence                  |
+| <i>United Kingdom (no DTX)</i>                   | <i>United Kingdom (with DTX)</i>                      |
+| 3 dial tones                                     | 1 dial                                                |
+| 1 ringing tone                                   | 1 ring                                                |
+| 1 busy tone (subscriber engaged)                 | 1 busy                                                |
+| 1 congestion tone (network equipment engaged)    | 1 congest                                             |
+| -                                                | 1 sustained, low-level sinusoid (number unobtainable) |
+| <i>USA (no DTX)</i>                              | <i>USA (with DTX ... not tested)</i>                  |
+| 1 dial tone                                      | -                                                     |
+| 1 ringing tone                                   | -                                                     |
+| 1 busy tone (subscriber engaged)                 | -                                                     |
+| 1 special information tone                       | -                                                     |
+| 1 congestion tone (network equipment engaged)    | -                                                     |
+
+Tones were computer generated for the tests in which DTX was switched off. Authentic DAT recordings of PSTN information tones were used to check the performance with DTX switched on, except the low-level sinusoid signal for "UK number unobtainable" which was computer generated.
+
+# 10 Performance with special input signals
+
+Two kinds of special input signals have been chosen to be tested in the verification phase of the Enhanced Full Rate: music signals and noise signals.
+
+## 10.1 Music signals
+
+This subclause reports on the informal listening tests conducted in CSELT to evaluate the performance of the EFR codec with music signals.
+
+The tests have been based on informal pair comparison tests (A versus B without repetition) by considering the Full-rate codec, the Enhanced Full-Rate as well as the ITU-T ADPCM G.726 codec at 32 kbit/s. The tests involved 6 music items taken from those selected by ISO-MPEG to test audio codec standards. The duration of the different music items lasts in the range between 8 and 10 seconds. Music items have been downsampled to 8 kHz before processing. Listening was performed by 12 naive listeners through headphones.
+
+The results are reported in tables 10.1.1 and 10.1.2.
+
+**Table 10.1.1: Results of the informal test on performance with music signals: Enhanced Full Rate versus Full Rate**
+
+| Music Items          | Enhanced Full Rate preferred to Full Rate | Enhanced Full Rate equal to Full Rate | Full Rate preferred to Enhanced Full Rate |
+|----------------------|-------------------------------------------|---------------------------------------|-------------------------------------------|
+| Harpsichord          | 100 %                                     | 0 %                                   | 0 %                                       |
+| Carmen               | 25 %                                      | 41,7 %                                | 33,3 %                                    |
+| Trumpet              | 100 %                                     | 0 %                                   | 0 %                                       |
+| Castanets            | 33,3 %                                    | 41,7 %                                | 25 %                                      |
+| Mediterraneo         | 41,7 %                                    | 33,3 %                                | 25 %                                      |
+| Vivaldi "The spring" | 100 %                                     | 0 %                                   | 0 %                                       |
+| Total                | 66,7 %                                    | 19,4 %                                | 13,9 %                                    |
+
+**Table 10.1.2: Results of the informal test on performance with music signals: Enhanced Full Rate versus ADPCM 32 kbit/s**
+
+| Music Items          | Enhanced Full Rate preferred to ADPCM | Enhanced Full Rate equal to ADPCM | ADPCM preferred to Enhanced Full Rate |
+|----------------------|---------------------------------------|-----------------------------------|---------------------------------------|
+| Harpsichord          | 50 %                                  | 8,3 %                             | 41,7 %                                |
+| Carmen               | 0 %                                   | 25 %                              | 75 %                                  |
+| Trumpet              | 33,3 %                                | 33,3 %                            | 33,3 %                                |
+| Castanets            | 8,3 %                                 | 41,7 %                            | 50 %                                  |
+| Mediterraneo         | 16,7 %                                | 25 %                              | 58,3 %                                |
+| Vivaldi "The spring" | 16,7 %                                | 25 %                              | 58,3 %                                |
+| Total                | 20,9 %                                | 26,4 %                            | 52,7 %                                |
+
+The analysis of results shows a certain dependency of performance on the music item. There is at least one item in which the FR has been judged better than the EFR. Nevertheless, on the average, the EFR provides better performance than the FR, whilst it appears to perform worse than the ADPCM.
+
+## 10.2 Noise signals
+
+To check the scaling performance of the fixed point algorithm a noise signal with levels ranging from -10 dB down to -70 dB have been processed by encoder and decoder in error free conditions. The level of the decoder output signal was examined. It was found that for all signals the reconstructed output level followed the input level. Even for very low signal levels no problems were detected.
+
+# 11 Performance with different languages
+
+This clause deals with the results of an informal listening test to evaluate the performance of the EFR for some languages which were not tested formally.
+
+The tests have been based on informal pair comparison (A versus B without repetition) by considering the Full-rate codec, the Enhanced Full-Rate as well as the ITU-T ADPCM G.726 codec at 32 kbit/s. The tests involved 5 different languages (Arab, Chinese, Japanese, Polish and Portuguese). Listening and recording was performed by naive, mother tongue people. For most languages, however, it was possible to use only one listener thus suggesting to take the results with the due caution.
+
+The test was performed by collecting people of different mother-tongue at CSELT premises. Subjects were asked to record a list of sentences in their own languages. The sentence length was in the range from 4 to 6 seconds. The list of languages, number of listeners and samples is reported in table 11.1.
+
+**Table 11.1: List of languages and the number of listeners and sentences used**
+
+| LANGUAGE   | NUMBER OF LISTENERS | NUMBER OF SENTENCES |
+|------------|---------------------|---------------------|
+| Arab       | 2                   | 8                   |
+| Chinese    | 1                   | 8                   |
+| Japanese   | 1                   | 8                   |
+| Polish     | 2                   | 8                   |
+| Portuguese | 1                   | 8                   |
+
+The subject were asked to listen to an A-B sequence and allowed to express a preference as well as to judge the perceived quality to be the same. The results of the test are reported in tables 11.2 and 11.3.
+
+**Table 11.2: Results of the informal test on languages not covered in the formal tests: Enhanced Full Rate versus Full Rate**
+
+| Languages  | Enhanced Full Rate preferred to Full Rate | Enhanced Full Rate equal to Full Rate | Full Rate preferred to Enhanced Full Rate |
+|------------|-------------------------------------------|---------------------------------------|-------------------------------------------|
+| Arab       | 37,5 %                                    | 50 %                                  | 12,5 %                                    |
+| Chinese    | 100 %                                     | 0 %                                   | 0 %                                       |
+| Japanese   | 100 %                                     | 0 %                                   | 0 %                                       |
+| Polish     | 68,7 %                                    | 12,5 %                                | 18,8 %                                    |
+| Portuguese | 75 %                                      | 25 %                                  | 0 %                                       |
+
+**Table 11.3: Results of the informal test on languages not covered in the formal tests: Enhanced Full Rate versus ADPCM at 32 kbit/s**
+
+| Languages  | Enhanced Full Rate preferred to ADPCM | Enhanced Full Rate equal to ADPCM | ADPCM preferred to Enhanced Full Rate |
+|------------|---------------------------------------|-----------------------------------|---------------------------------------|
+| Arab       | 18,75 %                               | 75 %                              | 6,25 %                                |
+| Chinese    | 87,5 %                                | 12,5 %                            | 0 %                                   |
+| Japanese   | 87,5 %                                | 12,5 %                            | 0 %                                   |
+| Polish     | 25 %                                  | 37,5 %                            | 37,5 %                                |
+| Portuguese | 12,5 %                                | 50 %                              | 37,5 %                                |
+
+The analysis of the results confirms the good performance of the Enhanced full-rate also for languages not considered in the formal experiments.
+
+This seems to be the case for all the languages tested, even though the test size was very small. The EFR was always preferred in comparison to the Full-rate. For Chinese and Japanese the preference is stronger and, for these languages, the EFR is preferred also to the ADPCM at 32 kbit/s in most of the cases.
+
+# 12 Delay
+
+The round-trip delay of a communication using a TCH-EFS has been estimated taking into account all the system and processing delays.
+
+The symbol definitions for the calculations in this section are:
+
+|          |                                                                                                                                                                                                                                                                                                                        |
+|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Tabisd   | The time required to transmit the 260 speech frame data bits (bits D1 – D260, C16 and the 17 synchronization bits -> 278 bits) over the 16 kbit/s A-bis-interface in the downlink direction (system dependent).                                                                                                        |
+| Tabisu   | The time required to transmit the first 137 TRAU frame bits, the first 34 of which can be sent by anticipation, leading to a delay of 103 TRAU frame bits (D2 – D98 speech frame data bits including the CRCs + 6 synchronization bits) over the 16 kbit/s A-bis-interface in the uplink direction (system dependent). |
+| Tad      | Delay in the analogue to digital converter in the uplink.                                                                                                                                                                                                                                                              |
+| Tbsc     | Switching delay in the BSC (implementation dependent).                                                                                                                                                                                                                                                                 |
+| Tbuff    | Due to the time alignment procedure for inband control of the remote transcoder in case of a 16 kbit/s A-bis-interface in the downlink direction, it is required to have a buffer in the BTS of 1 ms + one 250 s regulation step (system dependent).                                                                   |
+| Tda      | Delay in the digital to analogue converter in the downlink.                                                                                                                                                                                                                                                            |
+| Techo    | Delay due to the echo canceller.                                                                                                                                                                                                                                                                                       |
+| Tencode: | The time required for the channel encoder to perform channel encoding (implementation dependent).                                                                                                                                                                                                                      |
+| Tmsc     | Switching delay in the MSC.                                                                                                                                                                                                                                                                                            |
+| Tpcm     | The duration of a segment of PCM speech for the downlink processing delay.                                                                                                                                                                                                                                             |
+
+|          |                                                                                                                                                                                                                                                              |
+|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Tproc:   | The time required after reception of the last encoded speech parameter of the first subframe (FCB-Gain1) to process the speech encoded data for the enhanced full rate speech decoder and to produce the first PCM output sample (implementation dependent). |
+| Trftx:   | The time required for transmission of a TCH radio interface frame over the air interface due to the interleaving and de-interleaving (system dependent).                                                                                                     |
+| Trxproc: | The time required after reception over the radio interface to perform equalization, channel decoding and SID-frame detection (implementation dependent).                                                                                                     |
+| Tsample: | The duration of the segment of PCM speech operated on by the speech transcoder.                                                                                                                                                                              |
+| Tsp      | Delay of the speech encoder in the BSC after reception of the last PCM sample until availability of the first encoded bit (implementation dependent).                                                                                                        |
+| Ttransc: | The MS speech encoder processing time, from input of the last PCM sample to output of the final encoded bit (implementation dependent).                                                                                                                      |
+
+The processing delays were estimated from the detailed complexity figure that has been previously computed in the verification phase. The complexity estimation is based on rules that are supposed to be relevant from an implementation point of view and independent from specific DSPs at the same time. Therefore it was tried to follow the same philosophy for the processing delays. The DSP that runs the codec has been modelled through three parameters E, S and P.
+
+E stands for the Efficiency of the DSP. This corresponds to the ratio TMOPS/WMOPS of the implementation of the codec on the DSP.
+
+S stands for the Speed of the DSP: Maximum Number of Operations that the DSP can run in 1 second. This number is expressed in MOPS.
+
+P stands for the percentage of DSP processing power assigned to the codec.
+
+The processing delay of a task whose complexity is X can then be computed using the formula:
+
+$$D = X * 20 / ESP,$$
+
+the time unit being ms.
+
+The following assumptions were made when computing the round-trip delay:
+
+- for the enhanced Full Rate MS delay, it is assumed that the DSP has the same performance as the DSP used for GSM HR [5];
+- for the Enhanced Full Rate BSC delays, it is assumed that the DSP of the TRAÜ will have the same performance as the DSP used for GSM HR;
+- for the Enhanced Full Rate BTS delay, it is assumed that the DSP will have the same performance as the DSP used for GSM FR [4]. The reason is that it is assumed that the GSM Full Rate BTS will be reused during first GSM EFR deployments;
+- a 16 kbit/s submultiplexed A-bis is used between the BTS and the BSC-TRAÜ.
+
+From these assumptions and following the complexity of GSM HR [3] and its delay requirement for the MS [2], the ESP value has been computed for EFR:
+
+$$ESP = 25$$
+
+The following list of delays provided in [1] and [2] for the GSM Full Rate and common to the GSM Enhanced Full rate are considered realistic and therefore retain the same value:
+
+- *MSC* T<sub>m</sub>sc  
+margin
+- *BSC* T<sub>b</sub>sc  
+margin
+
+- *BTS* Trxproc
+- margin
+- *MS* Trftx
+- Tda
+
+The results of the estimation are provided in table 12.1 for uplink and table 12.2 for downlink. The time unit for all delays is ms ( $10^{-3}$  s).
+
+**Table 12.1: Uplink delay**
+
+| Equipment                                                                                                                     | Speed Parameter | Delay (ms) | Data              |
+|-------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|-------------------|
+| MSC                                                                                                                           | Tmsc            | 0,5        |                   |
+|                                                                                                                               | margin          | 0,5        |                   |
+| BSC                                                                                                                           | Tbsc            | 0,5        |                   |
+|                                                                                                                               | Tproc           | 1,27       | 1,59 WMOPS        |
+|                                                                                                                               | margin          | 0,5        |                   |
+| BTS                                                                                                                           | Tabisu          | 6,4375     | 103 bits          |
+|                                                                                                                               | Trxproc         | 8,8        | 2,45 WMOPS (note) |
+|                                                                                                                               | margin          | 3          |                   |
+| MS                                                                                                                            | Trftx           | 37,5       |                   |
+|                                                                                                                               | Tencode         | 0,32       | 0,20 WMOPS        |
+|                                                                                                                               | Ttransc         | 12,17      | 15,21 WMOPS       |
+|                                                                                                                               | Tsample         | 20         |                   |
+|                                                                                                                               | Tmargin         | 2          |                   |
+|                                                                                                                               | Tad             | 1          |                   |
+| SUM                                                                                                                           | Uplink          | 94,4975    |                   |
+| NOTE: This theoretical complexity corresponds to the channel decoding only. This leaves 6,84 ms for the equaliser in Trxproc. |                 |            |                   |
+
+**Table 12.2: Downlink delay**
+
+| Equipment                                                                                                                     | Speed Parameter | Delay (ms) | Data              |
+|-------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|-------------------|
+| MSC                                                                                                                           | Techo           | 1          |                   |
+|                                                                                                                               | Tmsc            | 0,5        |                   |
+|                                                                                                                               | margin          | 0,5        |                   |
+| BSC                                                                                                                           | Tbsc            | 0,5        |                   |
+|                                                                                                                               | Tsample         | 20         |                   |
+|                                                                                                                               | Tsps            | 2,3        |                   |
+|                                                                                                                               | Tabisd          | 17,375     | 278 bits          |
+|                                                                                                                               | margin          | 0,5        |                   |
+| BTS                                                                                                                           | Tbuff           | 1,25       |                   |
+|                                                                                                                               | Tencode         | 1,60       | 0,20 WMOPS        |
+|                                                                                                                               | margin          | 0,45       |                   |
+| MS                                                                                                                            | Trftx           | 37,5       |                   |
+|                                                                                                                               | Trxproc         | 8,8        | 2,45 WMOPS (note) |
+|                                                                                                                               | Tproc           | 1,27       | 1,59 WMOPS        |
+|                                                                                                                               | margin          | 2          |                   |
+|                                                                                                                               | Tda             | 1          |                   |
+| SUM                                                                                                                           | Downlink        | 96,547     |                   |
+| NOTE: This theoretical complexity corresponds to the channel decoding only. This leaves 6,84 ms for the equaliser in Trxproc. |                 |            |                   |
+
+|                                                                     |
+|---------------------------------------------------------------------|
+| <b>Round-trip delay = Uplink delay + Downlink delay = 191,04 ms</b> |
+|---------------------------------------------------------------------|
+
+This delay is very close to the delay indicated in [1], [2] and [3] for GSM Full Rate: 188,5 ms. The difference should be unnoticeable.
+
+# 13 Frequency response
+
+## 13.1 Introduction
+
+A characteristic test in the verification of GSM speech codecs is the frequency response test. Sine tones in the telephony frequency band are input to the codecs, and after decoding the gain is calculated. It has to be pointed out that the frequency response measurement is given just as a piece of additional information and does not add information on the actual behaviour of the codec in terms of perceived quality or DTMF transparency.
+
+## 13.2 Test environment
+
+The tones were calculated to a nominal level of 22 dB below the overload point. Tones ranging from 80 Hz to 3 600 Hz in steps of 21 Hz with a nominal length of 2 s were input to the codec under test. After decoding the gain was calculated with averaged results of 400 ms intervals and again averaged for the total duration of one frequency to get the frequency response curve. This was done to check the transition behaviour of the codec and eventually disregard the first samples.
+
+## 13.3 Results
+
+Within the telephony band the frequency response is very flat. No abnormal deviations were observed. Also additional experiments with different input level (-18 dB, -28 dB), or different tone length (500 ms, 4 s) resulted in almost identical curves. The decreasing gain above 3 kHz is relative small and far away from a 3 dB margin. The transition behaviour was very good.
+
+![Figure 13: GSM EFR codec frequency response at different input levels. The graph shows gain [dB] on the y-axis (from -9 to 3) versus frequency f [Hz] on a logarithmic x-axis (from 100 to 10000). Two curves are plotted: L -22 dB (blue line with circles) and L -28 dB (magenta line with squares). Both curves show a flat response around 0 dB gain from approximately 100 Hz to 3000 Hz, with a slight decrease in gain starting around 3000 Hz.](c19f313a256eec398179c6859dc32a5b_img.jpg)
+
+| Frequency [Hz] | Gain [dB] (L -22 dB) | Gain [dB] (L -28 dB) |
+|----------------|----------------------|----------------------|
+| 100            | -6                   | -6                   |
+| 200            | -1                   | -1                   |
+| 500            | 0                    | 0                    |
+| 1000           | 0                    | 0                    |
+| 2000           | 0                    | 0                    |
+| 3000           | -0.5                 | -0.5                 |
+| 4000           | -1                   | -1                   |
+| 5000           | -1.5                 | -1.5                 |
+| 6000           | -2                   | -2                   |
+| 7000           | -2.5                 | -2.5                 |
+| 8000           | -3                   | -3                   |
+| 9000           | -3.5                 | -3.5                 |
+| 10000          | -4                   | -4                   |
+
+Figure 13: GSM EFR codec frequency response at different input levels. The graph shows gain [dB] on the y-axis (from -9 to 3) versus frequency f [Hz] on a logarithmic x-axis (from 100 to 10000). Two curves are plotted: L -22 dB (blue line with circles) and L -28 dB (magenta line with squares). Both curves show a flat response around 0 dB gain from approximately 100 Hz to 3000 Hz, with a slight decrease in gain starting around 3000 Hz.
+
+Figure 13: GSM EFR codec frequency response at different input levels
+
+# 14 Complexity
+
+The complexity of the Enhanced Full Rate is characterised by the 3 following items:
+
+- the number of cycles;
+- the data memory size;
+- the program memory size.
+
+The values of these different figures depend on a specific DSP implementation. Nevertheless, the results obtained by the C description analysis can be used as references.
+
+The speech transcoding functions are specified using a set of basic arithmetic operations. The WMOPS figure quoted is a weighted sum of the operations required to perform transcoding. The weight assigned to each operation is representative of the number of instruction cycles required to perform that operation on a typical DSP device.
+
+The complexity range of the Enhanced Full Rate is equivalent to the Half Rate codec complexity.
+
+The number of cycles required by the Enhanced Full Rate algorithm is relatively independent on the values of the input samples. The execution time of an average and an extreme input case are equivalent.
+
+Nevertheless the following table presents the theoretical worst case evaluation, i.e. the maximum possible number of cycles, which is consistent with the results indicated in [3].
+
+The following figures are associated to the Speech and Channel part excluding the DTX functions.
+
+**Table 14: Principal complexity figure**
+
+|                    | Theoretical worst case WMOPS | Data RAM (note) (16 bits words) | Data ROM (constants) (16 bits words) | Program ROM (assembly instructions) |
+|--------------------|------------------------------|---------------------------------|--------------------------------------|-------------------------------------|
+| Enhanced Full Rate | 18,1                         | 4 708                           | 5 363                                | 6 000 – 9 000                       |
+| Half Rate          | 21,2                         | 5 002                           | 8 781                                | 8 000 – 12 000                      |
+
+NOTE: The Data RAM figure can be split in 2 parts: the static variables: 2 240 words; and the dynamic variables (i.e. local to a procedure ): 2 468 words.
+
+# 15 Summary of the results from the subjective testing
+
+The EFR codec is better than the actual FR codec for clear speech, for all error conditions (EP1, EP2 and EP3) and for tandeming under error EP1; it is equivalent to G.728 for its intrinsic quality, for background noise conditions and talker dependency. The EFR codec does not reach the objective performance target (TCH-FS EP2) for severe error condition EP3; for error conditions EP1 and EP2 it does not reach the objective performance target for half of the results. The EFR quality under tandeming condition without error was not tested against the target G.728 but is found equivalent to G.721. The advantage of the EFR compared to the TCH-FS is dependant of the quality of the network. As channel errors increase, this advantage is reduced.
+
+**Table 15: Summary of Results**
+
+| Conditions     | High Ref                                           | Low Ref                                                |
+|----------------|----------------------------------------------------|--------------------------------------------------------|
+| EP0            | Equivalent to G.728                                | Equivalent to G.728<br>Better than TCH-FS              |
+| EP1            | Worse than MNRU 24 dB<br><i>for half of labs</i>   | Better than TCH-FS (EP1)                               |
+| EP2            | Worse than TCH-FS (EP1)<br><i>for half of labs</i> | Better than TCH-FS (EP2)                               |
+| EP3            | Worse than TCH-FS (EP2)                            | Better than TCH-FS (EP3)<br><i>except for one lab.</i> |
+| EP0 (tandem)   | G.728 (not tested)<br>Equivalent to G.721          | G.728 (not tested)<br>Equivalent to G.721              |
+| EP1 (tandem)   | Equivalent to TCH-FS (EP1)                         | Better than TCH-FS (EP1 tandem)                        |
+| Vehicle 10     | Equivalent to G.728                                | Equivalent to G.728                                    |
+| Music 20       | Equivalent to G.728                                | Equivalent to G.728<br>Better than TCH-FS              |
+| Male Talkers   | Equivalent to G.728                                | Equivalent to G.728                                    |
+| Female Talkers | Equivalent to G.728                                | Equivalent to G.728                                    |
+| Children       | Equivalent to G.728                                | Equivalent to G.728                                    |
+
+![Line graph showing speech quality vs error rate for G.728, GSM FR, and GSM EFR. The y-axis is 'Speech quality' and the x-axis is 'Error rate' with categories: zero, moderate, high, very high. G.728 (reference) is a horizontal dashed line. GSM FR is a dashed line that decreases as error rate increases. GSM EFR is a solid line that stays above GSM FR and decreases more sharply after the moderate error rate point.](1c427123350e0e73e2a109b79069314b_img.jpg)
+
+### Tendency of subjective listening tests
+
+#### Error rate vs. speech quality without background noise
+
+The graph illustrates the relationship between speech quality and error rate for three different speech coding standards in a noise-free environment. The y-axis represents 'Speech quality' and the x-axis represents 'Error rate' with categories: zero, moderate, high, and very high. The G.728 (reference) is shown as a horizontal dashed line, indicating a constant quality level. The GSM FR (Full Rate) is shown as a dashed line that starts at a lower quality than G.728 and decreases as the error rate increases. The GSM EFR (Enhanced Full Rate) is shown as a solid line that starts at the same quality as G.728 at zero error rate, remains relatively flat until the moderate error rate, and then decreases sharply, crossing below the G.728 line and ending at a lower quality than GSM FR at the very high error rate.
+
+| Error Rate Category | G.728 (reference) | GSM FR      | GSM EFR    |
+|---------------------|-------------------|-------------|------------|
+| zero                | High              | Medium-High | High       |
+| moderate            | High              | Medium-Low  | High       |
+| high                | High              | Low         | Medium-Low |
+| very high           | High              | Very Low    | Very Low   |
+
+Line graph showing speech quality vs error rate for G.728, GSM FR, and GSM EFR. The y-axis is 'Speech quality' and the x-axis is 'Error rate' with categories: zero, moderate, high, very high. G.728 (reference) is a horizontal dashed line. GSM FR is a dashed line that decreases as error rate increases. GSM EFR is a solid line that stays above GSM FR and decreases more sharply after the moderate error rate point.
+
+Figure 15: General trend of the EFR behaviour for error conditions in noise-free environment
+
+# Annex A: Summary of results (lab by lab)
+
+## A.1 Quality under Error and tandeming conditions
+
+**Table A.1.1: Q values and Differential Q (dB) values from References for error and tandeming conditions (BT/lab1, Mod. IRS input characteristics – SEG-4, Exp#1 and Exp#5)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | +3,71                            | +3,71                           | 29,86        | 26,15              | 26,15             |
+| EP1          | -2,42                            | +2,96                           | 21,58        | 24                 | 18,62             |
+| EP2          | -2,97                            | +0,96                           | 15,65        | 18,62              | 14,69             |
+| EP3          | -11,30                           | -0,55                           | 0,41         | 11,71              | 0,96              |
+| EP0 (tandem) | -                                | -                               | -            | 22,94              | 22,94             |
+| EP1 (tandem) | --2,72                           | +1,26                           | 15,90        | 18,62              | 14,64             |
+
+**Table A.1.2: Q values and Differential Q (dB) values from References for error and tandeming conditions (CNET/lab2, Mod. IRS input characteristics – SEG-4, Exp#1 and Exp#5)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | +12,59                           | +12,59                          | 39,06        | 26,47              | 26,47             |
+| EP1          | 0 / -1,33                        | +6,14                           | 22,67        | 22,67 / 24         | 16,53             |
+| EP2          | +0,15                            | +2,32                           | 16,68        | 16,53              | 14,36             |
+| EP3          | -11,95                           | +1,21                           | 2,41         | 14,36              | 1,20              |
+| EP0 (tandem) | -                                | -                               | -            | 25,71              | 25,71             |
+| EP1 (tandem) | +2,22                            | +5,29                           | 18,75        | 16,53              | 13,46             |
+
+**Table A.1.3: Q values and Differential Q (dB) values from References for error and tandeming conditions (TD/lab3, Mod. IRS input characteristics – SEG-4, Exp#1 and Exp#5)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | +1,98                            | +1,98                           | 28,66        | 26,68              | 26,68             |
+| EP1          | +2,74 / +2,60                    | +7,06                           | 26,60        | 23,86 / 24         | 19,54             |
+| EP2          | -1,53                            | +2,50                           | 18,01        | 19,54              | 15,51             |
+| EP3          | -15,33                           | > +0,18                         | 0,18         | 15,51              | < 0               |
+| EP0 (tandem) | -                                | -                               | -            | 23,66              | 23,66             |
+| EP1 (tandem) | +0,76                            | +6,06                           | 20,30        | 19,54              | 14,24             |
+
+**Table A.1.4: Q values and Differential Q (dB) values from References for error and tandeming conditions (NEC/lab4, Mod. IRS input characteristics – SEG-4, Exp#1 and Exp#5)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | +3,70                            | +3,70                           | 26,32        | 22,62              | 22,62             |
+| EP1          | -1,50                            | +5,50                           | 22,50        | 24                 | 17,00             |
+| EP2          | +4,63                            | +6,76                           | 21,63        | 17,00              | 14,87             |
+| EP3          | -10,49                           | +2,70                           | 4,38         | 14,87              | 1,68              |
+| EP0 (tandem) | -                                | -                               | -            | 19,32              | 19,32             |
+| EP1 (tandem) | +2,92                            | +8,49                           | 19,92        | 17,00              | 11,43             |
+
+**Table A.1.5: Q values and Differential Q (dB) values from References for error and tandeming conditions (MOTOROLA/lab5, Mod. IRS input characteristics)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | -                                | -                               | 24,82        | ?                  | -                 |
+| EP1          | -4,41                            | +3,79                           | 19,59        | 24                 | 15,80             |
+| EP2          | -1,17                            | +3,35                           | 14,63        | 15,80              | 11,28             |
+| EP3          | -7,23                            | > +4,05                         | 4,05         | 11,28              | < 0               |
+| EP0 (tandem) | -                                | -                               | -            | -                  | -                 |
+| EP1 (tandem) | -                                | -                               | -            | 15,80              | -                 |
+
+**Table A.1.6: Q values and Differential Q (dB) values from References for error and tandeming conditions (COMSAT/lab6)**
+
+| Conditions                                                                             | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref.       | Q Values Low Ref.        |
+|----------------------------------------------------------------------------------------|----------------------------------|---------------------------------|--------------|--------------------------|--------------------------|
+| EP0 – (flat input)                                                                     | +1,39                            | +1,39                           | 31,03        | 29,64                    | 29,64                    |
+| EP1 (Mod. IRS)                                                                         | ~ +2,79                          | > +5,86                         | > 25         | -(24)                    | 19,14                    |
+| EP2 (Mod. IRS)                                                                         | +1,03                            | +4,15                           | 20,17        | 19,14                    | 14,99                    |
+| EP3                                                                                    | -                                | -                               |              | 14,99                    | -                        |
+| EP0 (tandem) – (flat input)                                                            | (G.728)<br>+2,35 (G.721)         | (G.728)<br>+2,35 (G.721)        | 28,78        | (G.728)<br>26,43 (G.721) | (G.728)<br>26,43 (G.721) |
+| EP1 (tandem) – (flat input)                                                            | -                                | -                               | -            | 19,14                    | -                        |
+| Extra Conditions (not included in SEG-4, High and Low references not formally defined) |                                  |                                 |              | G.721 (same condition)   | TCH-FS (same condition)  |
+| EP0 –16 dBmOL – (flat input)                                                           | +2,31 (G.721)                    | +7,80                           | 34,40        | 32,09 (G.721)            | 27,32                    |
+| EP0 –36 dBmOL – (flat input)                                                           | -0,61 (G.721)                    | +2,41                           | 25,08        | 25,69 (G.721)            | 22,67                    |
+| C/I 10 dB, 1.5 mph (Mod. IRS)                                                          |                                  | > +5,99                         | > 25         |                          | 19,01                    |
+| C/I 13 dB (Mod. IRS)                                                                   |                                  | > +4,04                         | > 25         |                          | 20,96                    |
+| C/I 13 dB tandem (Mod. IRS)                                                            |                                  | > +9,80                         | > 25         |                          | 15,20                    |
+| EP1 tandem EFR/TCH-FS – (flat)                                                         |                                  | -                               | 24,46        |                          | -                        |
+| EP1 tandem EFR/G.721 – (flat)                                                          |                                  | +2,93                           | 27,36        |                          | 24,43                    |
+
+*Differences compared to the SEG-4:* Different input characteristics (flat, except for error conditions), Additional input levels, tandemings and standards, G.721 as extra High Reference, Different MNRU selection, Separate experiment for error conditions (Non static, no frequency hopping 10 and 7 dB C/I, 30 mph, typical urban multipath, Mod. IRS input characteristics, MNRUmax = 25), No EP3 experiment.
+
+**Table A.1.7: Q values and Differential Q (dB) values from References for error and tandeming conditions (NOKIA/lab7)**
+
+| Conditions                                  | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref.     | Q Values Low Ref. |
+|---------------------------------------------|----------------------------------|---------------------------------|--------------|------------------------|-------------------|
+| EP0                                         | > +2,12                          | > +2,12                         | > 30         | 27,88                  | 27,88             |
+| EP1                                         | ~ -3                             | +14,79                          | 27,88        | -<br>(MNRU25<br>31,97) | 13,09             |
+| EP2                                         | +4,90                            | +8,65                           | 17,99        | 13,09                  | 9,34              |
+| EP3                                         | -7,49                            | > +1,85                         | 1,85         | 9,34                   | < 0               |
+| EP0 (tandem)                                | -                                | -                               | -            | 21,85                  | 21,85             |
+| EP1 (tandem)                                | +5,63                            | +7,99                           | 18,72        | 13,09?                 | 10,73             |
+| Extra conditions<br>(not included in SEG-4) |                                  |                                 |              |                        |                   |
+| C/I 13 dB                                   | -                                | > 14,91                         | > 30         | -                      | 15,09             |
+
+**Table A.1.8: Q values and Differential Q (dB) values from References for error and tandeming conditions (TI/lab8, Mod. IRS input characteristics –SEG-4, Exp#1 and Exp#5)**
+
+| Conditions   | Differential Q Values (High Ref) | Differential Q Values (Low Ref) | Q Values EFR | Q Values High Ref. | Q Values Low Ref. |
+|--------------|----------------------------------|---------------------------------|--------------|--------------------|-------------------|
+| EP0          | +2,36                            | +2,36                           | 20,41        | 18,05              | 18,05             |
+| EP1          | -5,21                            | +5,15                           | 18,79        | 24                 | 13,64             |
+| EP2          | -0,48                            | +2,60                           | 13,16        | 13,64              | 10,56             |
+| EP3          | -                                | -                               | -            | 10,56              | -                 |
+| EP0 (tandem) | -                                | -                               | -            | 17,18              | 17,18             |
+| EP1 (tandem) | +1,03                            | +5,16                           | 14,67        | 13,64              | 9,51              |
+
+## A.2 Quality under Background noise conditions
+
+**Table A.2.1: DMOS (and CI) values for EFR codec, G.728 Reference and TCH-FS (for lab1 to lab4, flat input characteristics – SEG-4, Exp#2 and Exp#3)**
+
+| Conditions        | Lab1 BT     | Lab2 CNET   | Lab3 TD     | Lab4 NEC    |
+|-------------------|-------------|-------------|-------------|-------------|
+| EFR Vehicle 10    | 4,36 (0,17) | 4,49 (0,12) | 4,26 (0,16) | 4,44 (0,18) |
+| EFR Music 20      | 4,29 (0,15) | 4,55 (0,11) | 4,20 (0,14) | 4,48 (0,18) |
+| G.728 Vehicle 10  | 4,54 (0,15) | 4,47 (0,14) | 4,59 (0,13) | 4,48 (0,14) |
+| G.728 Music 20    | 4,46 (0,13) | 4,52 (0,17) | 4,24 (0,11) | 4,52 (0,16) |
+| TCH-FS Vehicle 10 | 4,20 (0,17) | 4,50 (0,11) | 4,16 (0,16) | 4,06 (0,19) |
+| TCH-FS Music 20   | 3,36 (0,15) | 3,47 (0,15) | 3,11 (0,15) | 3,31 (0,20) |
+
+**Table A.2.2: DMOS (and CI) values for EFR codec, G.728 Reference and extra Standards  
+(for lab5 to lab8, flat input characteristics)**
+
+| Conditions                                  | Lab6/Comsat<br>(1) (2) | Lab7/Nokia<br>(1) | Differences compared to<br>SEG-4:<br><br>1) Different selection of<br>MNRUs with noise added<br>for Lab6 and Lab7.<br>2) Different noise types,<br>G.721 as High Reference,<br>Additional standards for<br>Lab6. |
+|---------------------------------------------|------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| EFR Vehicle 10                              | -                      | 4,47 (0,12)       |                                                                                                                                                                                                                  |
+| EFR Music 20                                | -                      | 4,57 (0,10)       |                                                                                                                                                                                                                  |
+| G.728 Vehicle 10                            | -                      | 4,45 (0,12)       |                                                                                                                                                                                                                  |
+| G.728 Music 20                              | -                      | 4,46 (0,11)       |                                                                                                                                                                                                                  |
+| TCH-FS Vehicle 10                           | -                      | 3,75 (0,15)       |                                                                                                                                                                                                                  |
+| TCH-FS Music 20                             | -                      | 3,54 (0,17)       |                                                                                                                                                                                                                  |
+| Extra Conditions<br>(not included in SEG-4) |                        |                   |                                                                                                                                                                                                                  |
+| EFR Home 20 dB                              | 4,79 (0,08)            | -                 |                                                                                                                                                                                                                  |
+| EFR Vehicle 15 dB                           | 4,61 (0,10)            | -                 |                                                                                                                                                                                                                  |
+| EFR Vehicle 25 dB                           | 4,65 (0,09)            | -                 |                                                                                                                                                                                                                  |
+| EFR Street 10 dB                            | 4,41 (0,13)            | -                 |                                                                                                                                                                                                                  |
+| EFR Office 20 dB                            | 4,66 (0,10)            | -                 |                                                                                                                                                                                                                  |
+| TCH-FS Home 20 dB                           | 4,35 (0,12)            | -                 |                                                                                                                                                                                                                  |
+| TCH-FS Vehicle 15 dB                        | 4,06 (0,13)            | -                 |                                                                                                                                                                                                                  |
+| TCH-FS Vehicle 25 dB                        | 4,15 (0,14)            | -                 |                                                                                                                                                                                                                  |
+| TCH-FS Street 10 dB                         | 3,54 (0,18)            | -                 |                                                                                                                                                                                                                  |
+| TCH-FS Office 20 dB                         | 3,86 (0,15)            | -                 |                                                                                                                                                                                                                  |
+| G.721 Home 20 dB                            | 4,67 (0,11)            | -                 |                                                                                                                                                                                                                  |
+| G.721 Vehicle 15 dB                         | 4,56 (0,11)            | -                 |                                                                                                                                                                                                                  |
+| G.721 Vehicle 25 dB                         | 4,65 (0,10)            | -                 |                                                                                                                                                                                                                  |
+| G.721 Street 10 dB                          | 3,90 (0,17)            | -                 |                                                                                                                                                                                                                  |
+| G.721 Office 20 dB                          | 4,49 (0,12)            | -                 |                                                                                                                                                                                                                  |
+
+## A.3 Quality for Talker Dependency (DMOS and SD)
+
+**Table A.3.1: DMOS (and SD) for EFR codec and G.728 for talker dependency  
+(lab1 to lab4, flat, - SEG-4, Exp#4)**
+
+| Conditions           | Lab1<br>BT  | Lab2<br>CNET | Lab3<br>TD  | Lab4<br>NEC |
+|----------------------|-------------|--------------|-------------|-------------|
+| EFR Male Talkers     | 4,89 (0,38) | 4,70 (0,46)  | 4,77 (0,45) | 4,41 (0,73) |
+| EFR Female Talkers   | 4,91 (0,29) | 4,65 (0,56)  | 4,81 (0,47) | 4,49 (0,65) |
+| EFR Children         | 4,82 (0,39) | 4,65 (0,53)  | 4,83 (0,43) | 4,48 (0,71) |
+| G.728 Male Talkers   | 4,56 (0,59) | 4,32 (0,57)  | 4,34 (0,61) | 4,36 (0,74) |
+| G.728 Female Talkers | 4,61 (0,59) | 4,41 (0,55)  | 4,36 (0,56) | 4,35 (0,74) |
+| G.728 Children       | 4,80 (0,46) | 4,40 (0,52)  | 4,38 (0,57) | 4,50 (0,71) |
+
+**Table A.3.2: DMOS (and SD) for EFR codec and G.728 for talker dependency (lab7, flat)**
+
+| Conditions     | EFR         | G.728       |
+|----------------|-------------|-------------|
+| Male Talkers   | 4,73 (0,51) | 4,49 (0,57) |
+| Female Talkers | 4,64 (0,50) | 4,43 (0,56) |
+| Children       | 4,62 (0,59) | 4,37 (0,58) |
+
+*Differences compared to SEG-4:*
+
+Different selection of MNRUs, extra condition (TCH-FS), 16 listeners instead of 24
+
+# Annex B: Change history
+
+| Change history |           |         |                  |             |                      |
+|----------------|-----------|---------|------------------|-------------|----------------------|
+| SMG No.        | Tdoc. No. | CR. No. | Section affected | New version | Subject/Comments     |
+| SMG#19         |           |         |                  | 5.0.0       | Phase 2+ version     |
+| SMG#22         |           |         |                  | 4.0.0       | Phase 2 version      |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46060/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg b/marked/Rel-16/46_series/46060/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc072567833e150079df6c3c01ea30121f75f056
--- /dev/null
+++ b/marked/Rel-16/46_series/46060/0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:278a2bd5e6c9cb9078c63a4d4b82831d28fd35df84e1d4520aee82afb7fa0367
+size 39553
diff --git a/marked/Rel-16/46_series/46060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/46_series/46060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dae237335656c95152673c91b61fbe2a69434b08
--- /dev/null
+++ b/marked/Rel-16/46_series/46060/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2680b6f24d2af93170fe96370e64bdd1461ff17786ae81eaa115f381d745810
+size 36904
diff --git a/marked/Rel-16/46_series/46060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/46_series/46060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8e000b775f3a73dd7b1f1dfcf318d3bec8ae751
--- /dev/null
+++ b/marked/Rel-16/46_series/46060/2837ffdadcdb1e5bababa56b564e56ed_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:25012e1aa9eb2d651ac0900f11a0e1bd63b889f8976ab6990ec11d8e6e680250
+size 83278
diff --git a/marked/Rel-16/46_series/46060/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/46_series/46060/6e15fc9ea763541c5913d26f85072ae1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..89fd75dd49f7f46432b5853cca95704ad447455e
--- /dev/null
+++ b/marked/Rel-16/46_series/46060/6e15fc9ea763541c5913d26f85072ae1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6d6f91c585c56c5e7c36ab72f347163361c876527f2d321a156301eb4a92ee92
+size 196241
diff --git a/marked/Rel-16/46_series/46060/raw.md b/marked/Rel-16/46_series/46060/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9af4a4e3b291d686d48a54f2b7036f7e3361a29
--- /dev/null
+++ b/marked/Rel-16/46_series/46060/raw.md
@@ -0,0 +1,1440 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                            |    |
+|----------------------------------------------------------------------------|----|
+| Foreword .....                                                             | 4  |
+| 1 Scope.....                                                               | 5  |
+| 2 References.....                                                          | 5  |
+| 3 Definitions, symbols and abbreviations.....                              | 6  |
+| 3.1 Definitions.....                                                       | 6  |
+| 3.2 Symbols.....                                                           | 7  |
+| 3.3 Abbreviations .....                                                    | 11 |
+| 4 Outline description.....                                                 | 11 |
+| 4.1 Functional description of audio parts.....                             | 11 |
+| 4.2 Preparation of speech samples .....                                    | 12 |
+| 4.2.1 PCM format conversion .....                                          | 12 |
+| 4.3 Principles of the GSM enhanced full rate speech encoder.....           | 12 |
+| 4.4 Principles of the GSM enhanced full rate speech decoder.....           | 14 |
+| 4.5 Sequence and subjective importance of encoded parameters .....         | 14 |
+| 5 Functional description of the encoder.....                               | 14 |
+| 5.1 Pre-processing .....                                                   | 14 |
+| 5.2 Linear prediction analysis and quantization.....                       | 15 |
+| 5.2.1 Windowing and auto-correlation computation.....                      | 15 |
+| 5.2.2 Levinson-Durbin algorithm .....                                      | 16 |
+| 5.2.3 LP to LSP conversion.....                                            | 17 |
+| 5.2.4 LSP to LP conversion.....                                            | 18 |
+| 5.2.5 Quantization of the LSP coefficients.....                            | 19 |
+| 5.2.6 Interpolation of the LSPs.....                                       | 20 |
+| 5.3 Open-loop pitch analysis.....                                          | 20 |
+| 5.4 Impulse response computation.....                                      | 21 |
+| 5.5 Target signal computation.....                                         | 21 |
+| 5.6 Adaptive codebook search .....                                         | 22 |
+| 5.7 Algebraic codebook structure and search.....                           | 23 |
+| 5.8 Quantization of the fixed codebook gain .....                          | 26 |
+| 5.9 Memory update .....                                                    | 27 |
+| 6 Functional description of the decoder.....                               | 27 |
+| 6.1 Decoding and speech synthesis.....                                     | 27 |
+| 6.2 Post-processing.....                                                   | 29 |
+| 6.2.1 Adaptive post-filtering.....                                         | 29 |
+| 6.2.2 Up-scaling.....                                                      | 30 |
+| 7 Variables, constants and tables in the C-code of the GSM EFR codec ..... | 30 |
+| 7.1 Description of the constants and variables used in the C code .....    | 30 |
+| 8 Homing sequences .....                                                   | 33 |
+| 8.1 Functional description.....                                            | 33 |
+| 8.2 Definitions.....                                                       | 33 |
+| 8.3 Encoder homing .....                                                   | 35 |
+| 8.4 Decoder homing .....                                                   | 35 |
+| 8.5 Encoder home state .....                                               | 36 |
+| 8.6 Decoder home state .....                                               | 37 |
+| 9 Bibliography.....                                                        | 42 |
+| Annex A (informative): Change history.....                                 | 43 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document describes the detailed mapping between input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples within the digital cellular telecommunications system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document describes the detailed mapping between input blocks of 160 speech samples in 13-bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to a bit rate for the encoded bit stream of 12,2 kbit/s. The coding scheme is the so-called Algebraic Code Excited Linear Prediction Coder, hereafter referred to as ACELP.
+
+The present document also specifies the conversion between A-law or  $\mu$ -law (PCS 1900) PCM and 13-bit uniform PCM. Performance requirements for the audio input and output parts are included only to the extent that they affect the transcoder performance. This part also describes the codec down to the bit level, thus enabling the verification of compliance to the part to a high degree of confidence by use of a set of digital test sequences. These test sequences are described in GSM 06.54 [7] and are available on disks.
+
+In case of discrepancy between the requirements described in the present document and the fixed point computational description (ANSI-C code) of these requirements contained in GSM 06.53 [6], the description in GSM 06.53 [6] will prevail.
+
+The transcoding procedure specified in the present document is applicable for the enhanced full rate speech traffic channel (TCH) in the GSM system.
+
+In GSM 06.51 [5], a reference configuration for the speech transmission chain of the GSM enhanced full rate (EFR) system is shown. According to this reference configuration, the speech encoder takes its input as a 13-bit uniform PCM signal either from the audio part of the Mobile Station or on the network side, from the PSTN via an 8-bit/A-law or  $\mu$ -law (PCS 1900) to 13-bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to a channel encoder unit which is specified in GSM 05.03 [3]. In the receive direction, the inverse operations take place.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 03.50: "Digital cellular telecommunications system (Phase 2+); Transmission planning aspects of the speech service in the GSM Public Land Mobile Network (PLMN) system".
+- [3] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [4] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD)".
+- [5] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech processing functions General description".
+- [6] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [7] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec".
+- [8] ITU-T Recommendation G.711 (1988): "Coding of analogue signals by pulse code modulation Pulse code modulation (PCM) of voice frequencies".
+
+[9] ITU-T Recommendation G.726: "40, 32, 24, 16 kbit/s adaptive differential pulse code modulation (ADPCM)".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**adaptive codebook:** adaptive codebook contains excitation vectors that are adapted for every subframe. The adaptive codebook is derived from the long term filter state. The lag value can be viewed as an index into the adaptive codebook.
+
+**adaptive postfilter:** this filter is applied to the output of the short term synthesis filter to enhance the perceptual quality of the reconstructed speech. In the GSM enhanced full rate codec, the adaptive postfilter is a cascade of two filters: a formant postfilter and a tilt compensation filter.
+
+**algebraic codebook:** fixed codebook where algebraic code is used to populate the excitation vectors (innovation vectors). The excitation contains a small number of nonzero pulses with predefined interlaced sets of positions.
+
+**closed-loop pitch analysis:** this is the adaptive codebook search, i.e., a process of estimating the pitch (lag) value from the weighted input speech and the long term filter state. In the closed-loop search, the lag is searched using error minimization loop (analysis-by-synthesis). In the GSM enhanced full rate codec, closed-loop pitch search is performed for every subframe.
+
+**direct form coefficients:** one of the formats for storing the short term filter parameters. In the GSM enhanced full rate codec, all filters which are used to modify speech samples use direct form coefficients.
+
+**fixed codebook:** fixed codebook contains excitation vectors for speech synthesis filters. The contents of the codebook are non-adaptive (i.e., fixed). In the GSM enhanced full rate codec, the fixed codebook is implemented using an algebraic codebook.
+
+**fractional lags:** set of lag values having sub-sample resolution. In the GSM enhanced full rate codec a sub-sample resolution of 1/6th of a sample is used.
+
+**frame:** time interval equal to 20 ms (160 samples at an 8 kHz sampling rate).
+
+**integer lags:** set of lag values having whole sample resolution.
+
+**interpolating filter:** FIR filter used to produce an estimate of sub-sample resolution samples, given an input sampled with integer sample resolution.
+
+**inverse filter:** this filter removes the short term correlation from the speech signal. The filter models an inverse frequency response of the vocal tract.
+
+**lag:** long term filter delay. This is typically the true pitch period, or a multiple or sub-multiple of it.
+
+**Line Spectral Frequencies:** (see Line Spectral Pair).
+
+**Line Spectral Pair:** transformation of LPC parameters. Line Spectral Pairs are obtained by decomposing the inverse filter transfer function  $A(z)$  to a set of two transfer functions, one having even symmetry and the other having odd symmetry. The Line Spectral Pairs (also called as Line Spectral Frequencies) are the roots of these polynomials on the z-unit circle).
+
+**LP analysis window:** for each frame, the short term filter coefficients are computed using the high pass filtered speech samples within the analysis window. In the GSM enhanced full rate codec, the length of the analysis window is 240 samples. For each frame, two asymmetric windows are used to generate two sets of LP coefficients. No samples of the future frames are used (no lookahead).
+
+**LP coefficients:** Linear Prediction (LP) coefficients (also referred as Linear Predictive Coding (LPC) coefficients) is a generic descriptive term for describing the short term filter coefficients.
+
+**open-loop pitch search:** process of estimating the near optimal lag directly from the weighted speech input. This is done to simplify the pitch analysis and confine the closed-loop pitch search to a small number of lags around the open-loop estimated lags. In the GSM enhanced full rate codec, open-loop pitch search is performed every 10 ms.
+
+**residual:** output signal resulting from an inverse filtering operation.
+
+**short term synthesis filter:** this filter introduces, into the excitation signal, short term correlation which models the impulse response of the vocal tract.
+
+**perceptual weighting filter:** this filter is employed in the analysis-by-synthesis search of the codebooks. The filter exploits the noise masking properties of the formants (vocal tract resonances) by weighting the error less in regions near the formant frequencies and more in regions away from them.
+
+**subframe:** time interval equal to 5 ms (40 samples at an 8 kHz sampling rate).
+
+**vector quantization:** method of grouping several parameters into a vector and quantizing them simultaneously.
+
+**zero input response:** output of a filter due to past inputs, i.e. due to the present state of the filter, given that an input of zeros is applied.
+
+**zero state response:** output of a filter due to the present input, given that no past inputs have been applied, i.e., given the state information in the filter is all zeroes.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+|                                                  |                                                                                       |
+|--------------------------------------------------|---------------------------------------------------------------------------------------|
+| $A(z)$                                           | The inverse filter with unquantized coefficients                                      |
+| $\hat{A}(z)$                                     | The inverse filter with quantified coefficients                                       |
+| $H(z) = \frac{1}{\hat{A}(z)}$                    | The speech synthesis filter with quantified coefficients                              |
+| $a_i$                                            | The unquantized linear prediction parameters (direct form coefficients)               |
+| $\hat{a}_i$                                      | The quantified linear prediction parameters                                           |
+| $m$                                              | The order of the LP model                                                             |
+| $\frac{1}{B(z)}$                                 | The long-term synthesis filter                                                        |
+| $W(z)$                                           | The perceptual weighting filter (unquantized coefficients)                            |
+| $g_1, g_2$                                       | The perceptual weighting factors                                                      |
+| $F_E(z)$                                         | Adaptive pre-filter                                                                   |
+| $T$                                              | The nearest integer pitch lag to the closed-loop fractional pitch lag of the subframe |
+| $\beta$                                          | The adaptive pre-filter coefficient (the quantified pitch gain)                       |
+| $H_f(z) = \frac{\hat{A}(z/g_n)}{\hat{A}(z/g_d)}$ | The formant postfilter                                                                |
+| $g_n$                                            | Control coefficient for the amount of the formant post-filtering                      |
+| $g_d$                                            | Control coefficient for the amount of the formant post-filtering                      |
+| $H_t(z)$                                         | Tilt compensation filter                                                              |
+| $g_t$                                            | Control coefficient for the amount of the tilt compensation filtering                 |
+| $m = g_t k_1'$                                   | A tilt factor, with $k_1'$ being the first reflection coefficient                     |
+| $h_f(n)$                                         | The truncated impulse response of the formant postfilter                              |
+| $L_h$                                            | The length of $h_f(n)$                                                                |
+| $r_h(i)$                                         | The auto-correlations of $h_f(n)$                                                     |
+| $\hat{A}(z/g_n)$                                 | The inverse filter (numerator) part of the formant postfilter                         |
+| $1/\hat{A}(z/g_d)$                               | The synthesis filter (denominator) part of the formant postfilter                     |
+| $\hat{r}(n)$                                     | The residual signal of the inverse filter $\hat{A}(z/g_n)$                            |
+| $h_t(z)$                                         | Impulse response of the tilt compensation filter                                      |
+| $\beta_{sc}(n)$                                  | The AGC-controlled gain scaling factor of the adaptive postfilter                     |
+| $\alpha$                                         | The AGC factor of the adaptive postfilter                                             |
+| $H_{h1}(z)$                                      | Pre-processing high-pass filter                                                       |
+| $w_I(n), w_{II}(n)$                              | LP analysis windows                                                                   |
+| $L_1(I)$                                         | Length of the first part of the LP analysis window $w_I(n)$                           |
+| $L_2(I)$                                         | Length of the second part of the LP analysis window $w_I(n)$                          |
+| $L_1(II)$                                        | Length of the first part of the LP analysis window $w_{II}(n)$                        |
+| $L_2(II)$                                        | Length of the second part of the LP analysis window $w_{II}(n)$                       |
+| $r_{ac}(k)$                                      | The auto-correlations of the windowed speech $s'(n)$                                  |
+| $w_{lag}(i)$                                     | Lag window for the auto-correlations (60 Hz bandwidth expansion)                      |
+
+|                                        |                                                                                         |
+|----------------------------------------|-----------------------------------------------------------------------------------------|
+| $f_0$                                  | The bandwidth expansion in Hz                                                           |
+| $f_s$                                  | The sampling frequency in Hz                                                            |
+| $r'_{ac}(k)$                           | The modified (bandwidth expanded) auto-correlations                                     |
+| $E_{LD}(i)$                            | The prediction error in the $i$ th iteration of the Levinson algorithm                  |
+| $k_i$                                  | The $i$ th reflection coefficient                                                       |
+| $a_j^{(i)}$                            | The $j$ th direct form coefficient in the $i$ th iteration of the Levinson algorithm    |
+| $F'_1(z)$                              | Symmetric LSF polynomial                                                                |
+| $F'_2(z)$                              | Antisymmetric LSF polynomial                                                            |
+| $F_1(z)$                               | Polynomial $F_{1^e}(z)$ with root $z=-1$ eliminated                                     |
+| $F_2(z)$                               | Polynomial $F_{2^e}(z)$ with root $z = 1$ eliminated                                    |
+| $q_i$                                  | The line spectral pairs (LSPs) in the cosine domain                                     |
+| $q$                                    | An LSP vector in the cosine domain                                                      |
+| $\hat{q}_i^{(n)}$                      | The quantified LSP vector at the $i$ th subframe of the frame $n$                       |
+| $w_i$                                  | The line spectral frequencies (LSFs)                                                    |
+| $T_m(x)$                               | A $m$ th order Chebyshev polynomial                                                     |
+| $f_1(i), f_2(i)$                       | The coefficients of the polynomials $F_1(z)$ and $F_2(z)$                               |
+| $f'_1(i), f'_2(i)$                     | The coefficients of the polynomials $F_{1^e}(z)$ and $F_{2^e}(z)$                       |
+| $f(i)$                                 | The coefficients of either $F_1(z)$ or $F_2(z)$                                         |
+| $C(x)$                                 | Sum polynomial of the Chebyshev polynomials                                             |
+| $x$                                    | Cosine of angular frequency $w$                                                         |
+| $\lambda_k$                            | Recursion coefficients for the Chebyshev polynomial evaluation                          |
+| $f_i$                                  | The line spectral frequencies (LSFs) in Hz                                              |
+| $f^t = [f_1 f_2 K f_{10}]$             | The vector representation of the LSFs in Hz                                             |
+| $z^{(1)}(n), z^{(2)}(n)$               | The mean-removed LSF vectors at frame $n$                                               |
+| $r^{(1)}(n), r^{(2)}(n)$               | The LSF prediction residual vectors at frame $n$                                        |
+| $p(n)$                                 | The predicted LSF vector at frame $n$                                                   |
+| $\hat{r}^{(2)}(n-1)$                   | The quantified second residual vector at the past frame                                 |
+| $\hat{f}^k$                            | The quantified LSF vector at quantization index $k$                                     |
+| $E_{LSP}$                              | The LSP quantization error                                                              |
+| $w_i, i = 1, K, 10$                    | LSP-quantization weighting factors                                                      |
+| $d_i$                                  | The distance between the line spectral frequencies $f_{i+1}$ and $f_{i-1}$              |
+| $h(n)$                                 | The impulse response of the weighted synthesis filter                                   |
+| $O_k$                                  | The correlation maximum of open-loop pitch analysis at delay $k$                        |
+| $O_{t_i}, i = 1, K, 3$                 | The correlation maxima at delays $t_i, i = 1, K, 3$                                     |
+| $(M_i, t_i), i = 1, K, 3$              | The normalized correlation maxima $M_i$ and the corresponding delays $t_i, i = 1, K, 3$ |
+| $H(z)W(z) = \frac{A(z/g_1)}{A(z/g_2)}$ | The weighted synthesis filter                                                           |
+| $A(z/g_1)$                             | The numerator of the perceptual weighting filter                                        |
+| $1/A(z/g_2)$                           | The denominator of the perceptual weighting filter                                      |
+| $T_1$                                  | The nearest integer to the fractional pitch lag of the previous (1st or 3rd) subframe   |
+| $s'(n)$                                | The windowed speech signal                                                              |
+| $s_w(n)$                               | The weighted speech signal                                                              |
+| $\hat{s}(n)$                           | Reconstructed speech signal                                                             |
+| $\hat{s}'(n)$                          | The gain-scaled post-filtered signal                                                    |
+| $\hat{s}_f(n)$                         | Post-filtered speech signal (before scaling)                                            |
+| $x(n)$                                 | The target signal for adaptive codebook search                                          |
+| $x_2(n), x_2^t$                        | The target signal for algebraic codebook search                                         |
+| $res_{LP}(n)$                          | The LP residual signal                                                                  |
+| $c(n)$                                 | The fixed codebook vector                                                               |
+| $v(n)$                                 | The adaptive codebook vector                                                            |
+| $y(n) = v(n) * h(n)$                   | The filtered adaptive codebook vector                                                   |
+| $y_k(n)$                               | The past filtered excitation                                                            |
+| $u(n)$                                 | The excitation signal                                                                   |
+| $\hat{u}(n)$                           | The emphasized adaptive codebook vector                                                 |
+| $\hat{u}'(n)$                          | The gain-scaled emphasized excitation signal                                            |
+| $T_{op}$                               | The best open-loop lag                                                                  |
+| $t_{min}$                              | Minimum lag search value                                                                |
+
+|                              |                                                                                                                      |
+|------------------------------|----------------------------------------------------------------------------------------------------------------------|
+| $t_{\max}$                   | Maximum lag search value                                                                                             |
+| $R(k)$                       | Correlation term to be maximized in the adaptive codebook search                                                     |
+| $b_{24}$                     | The FIR filter for interpolating the normalized correlation term $R(k)$                                              |
+| $R(k)_t$                     | The interpolated value of $R(k)$ for the integer delay $k$ and fraction $t$                                          |
+| $b_{60}$                     | The FIR filter for interpolating the past excitation signal $u(n)$ to yield the adaptive codebook vector $v(n)$      |
+| $A_k$                        | Correlation term to be maximized in the algebraic codebook search at index $k$                                       |
+| $C_k$                        | The correlation in the numerator of $A_k$ at index $k$                                                               |
+| $E_{D_k}$                    | The energy in the denominator of $A_k$ at index $k$                                                                  |
+| $d = H^t x_2$                | The correlation between the target signal $x_2(n)$ and the impulse response $h(n)$ , i.e., backward filtered target  |
+| $H$                          | The lower triangular Toeplitz convolution matrix with diagonal $h(0)$ and lower diagonals $h(1), h(2), \dots, h(39)$ |
+| $F = H^t H$                  | The matrix of correlations of $h(n)$                                                                                 |
+| $d(n)$                       | The elements of the vector <b>d</b>                                                                                  |
+| $f(i, j)$                    | The elements of the symmetric matrix $F$                                                                             |
+| $c_k$                        | The innovation vector                                                                                                |
+| $C$                          | The correlation in the numerator of $A_k$                                                                            |
+| $m_i$                        | The position of the $i$ th pulse                                                                                     |
+| $J_i$                        | The amplitude of the $i$ th pulse                                                                                    |
+| $N_p$                        | The number of pulses in the fixed codebook excitation                                                                |
+| $E_D$                        | The energy in the denominator of $A_k$                                                                               |
+| $\text{res}_{\text{LTP}}(n)$ | The normalized long-term prediction residual                                                                         |
+| $b(n)$                       | The sum of the normalized $d(n)$ vector and normalized long-term prediction residual $\text{res}_{\text{LTP}}(n)$    |
+| $s_b(n)$                     | The sign signal for the algebraic codebook search                                                                    |
+| $d'(n)$                      | Sign extended backward filtered target                                                                               |
+| $f'(i, j)$                   | The modified elements of the matrix $F$ , including sign information                                                 |
+| $z^t, z(n)$                  | The fixed codebook vector convolved with $h(n)$                                                                      |
+| $E(n)$                       | The mean-removed innovation energy (in dB)                                                                           |
+| $\bar{E}$                    | The mean of the innovation energy                                                                                    |
+| $\bar{E}(n)$                 | The predicted energy                                                                                                 |
+| $[b_1 b_2 b_3 b_4]$          | The MA prediction coefficients                                                                                       |
+| $\hat{R}(k)$                 | The quantified prediction error at subframe $k$                                                                      |
+| $E_I$                        | The mean innovation energy                                                                                           |
+| $R(n)$                       | The prediction error of the fixed-codebook gain quantization                                                         |
+| $E_Q$                        | The quantization error of the fixed-codebook gain quantization                                                       |
+| $e(n)$                       | The states of the synthesis filter $1/\hat{A}(z)$                                                                    |
+| $e_w(n)$                     | The perceptually weighted error of the analysis-by-synthesis search                                                  |
+| $h$                          | The gain scaling factor for the emphasized excitation                                                                |
+| $g_c$                        | The fixed-codebook gain                                                                                              |
+| $g'_c$                       | The predicted fixed-codebook gain                                                                                    |
+| $\hat{g}_c$                  | The quantified fixed codebook gain                                                                                   |
+| $g_p$                        | The adaptive codebook gain                                                                                           |
+| $\hat{g}_p$                  | The quantified adaptive codebook gain                                                                                |
+| $g_{gc} = g_c / g'_c$        | A correction factor between the gain $g_c$ and the estimated one $g'_c$                                              |
+| $\hat{g}_{gc}$               | The optimum value for $g_{gc}$                                                                                       |
+| $g_{sc}$                     | Gain scaling factor                                                                                                  |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply. Further GSM related abbreviations may be found in GSM 01.04 [1].
+
+|       |                                          |
+|-------|------------------------------------------|
+| ACELP | Algebraic Code Excited Linear Prediction |
+| AGC   | Adaptive Gain Control                    |
+| CELP  | Code Excited Linear Prediction           |
+| FIR   | Finite Impulse Response                  |
+| ISPP  | Interleaved Single-Pulse Permutation     |
+| LP    | Linear Prediction                        |
+| LPC   | Linear Predictive Coding                 |
+
+|     |                                               |
+|-----|-----------------------------------------------|
+| LSF | Line Spectral Frequency                       |
+| LSP | Line Spectral Pair                            |
+| LTP | Long Term Predictor (or Long Term Prediction) |
+| MA  | Moving Average                                |
+
+# --- 4 Outline description
+
+The present document is structured as follows.
+
+Subclause 4.1 contains a functional description of the audio parts including the A/D and D/A functions. Subclause 4.2 describes the conversion between 13-bit uniform and 8-bit A-law or  $\mu$ -law (PCS 1900) samples. Subclauses 4.3 and 4.4 present a simplified description of the principles of the GSM EFR encoding and decoding process respectively. In clause 4.5, the sequence and subjective importance of encoded parameters are given.
+
+Clause 5 presents the functional description of the GSM EFR encoding, whereas clause 6 describes the decoding procedures. Clause 7 describes variables, constants and tables of the C-code of the GSM EFR codec.
+
+## 4.1 Functional description of audio parts
+
+The analogue-to-digital and digital-to-analogue conversion will in principle comprise the following elements:
+
+### 1) analogue to uniform digital PCM:
+
+- microphone;
+- input level adjustment device;
+- input anti-aliasing filter;
+- sample-hold device sampling at 8 kHz;
+- analogue-to-uniform digital conversion to 13-bit representation.
+
+The uniform format shall be represented in two's complement.
+
+### 2) uniform digital PCM to analogue:
+
+- conversion from 13-bit/8 kHz uniform PCM to analogue;
+- a hold device;
+- reconstruction filter including  $x/\sin(x)$  correction;
+- output level adjustment device;
+- earphone or loudspeaker.
+
+In the terminal equipment, the A/D function may be achieved either:
+
+- by direct conversion to 13-bit uniform PCM format;
+- or by conversion to 8-bit/A-law or  $\mu$ -law (PCS 1900) compounded format, based on a standard A-law or  $\mu$ -law (PCS 1900) codec/filter according to ITU-T Recommendations G.711 [8] and G.714, followed by the 8-bit to 13-bit conversion as specified in clause 4.2.1.
+
+For the D/A operation, the inverse operations take place.
+
+In the latter case it should be noted that the specifications in ITU-T G.714 (superseded by G.712) are concerned with PCM equipment located in the central parts of the network. When used in the terminal equipment, the present document does not on its own ensure sufficient out-of-band attenuation. The specification of out-of-band signals is defined in GSM 03.50 [2] in clause 2.
+
+## 4.2 Preparation of speech samples
+
+The encoder is fed with data comprising of samples with a resolution of 13 bits left justified in a 16-bit word. The three least significant bits are set to '0'. The decoder outputs data in the same format. Outside the speech codec further processing must be applied if the traffic data occurs in a different representation.
+
+### 4.2.1 PCM format conversion
+
+The conversion between 8-bit A-Law or  $\mu$ -law (PCS 1900) compressed data and linear data with 13-bit resolution at the speech encoder input shall be as defined in ITU-T Rec. G.711 [8].
+
+ITU-T Recommendation G.711 [8] specifies the A-Law or  $\mu$ -law (PCS 1900) to linear conversion and vice versa by providing table entries. Examples on how to perform the conversion by fixed-point arithmetic can be found in ITU-T Recommendation G.726 [9]. Subclause 4.2.1 of G.726 [9] describes A-Law and  $\mu$ -law (PCS 1900) to linear expansion and clause 4.2.7 of G.726 [9] provides a solution for linear to A-Law and  $\mu$ -law (PCS 1900) compression.
+
+## 4.3 Principles of the GSM enhanced full rate speech encoder
+
+The codec is based on the code-excited linear predictive (CELP) coding model. A 10th order linear prediction (LP), or short-term, synthesis filter is used which is given by:
+
+$$H(z) = \frac{1}{\hat{A}(z)} = \frac{1}{1 + \sum_{i=1}^m \hat{a}_i z^{-i}} \quad (1)$$
+
+where  $\hat{a}_i, i = 1, \dots, m$ , are the (quantified) linear prediction (LP) parameters, and  $m = 10$  is the predictor order. The long-term, or pitch, synthesis filter is given by:
+
+$$\frac{1}{B(z)} = \frac{1}{1 - g_p z^{-T}} \quad (2)$$
+
+where  $T$  is the pitch delay and  $g_p$  is the pitch gain. The pitch synthesis filter is implemented using the so-called adaptive codebook approach.
+
+The CELP speech synthesis model is shown in figure 2. In this model, the excitation signal at the input of the short-term LP synthesis filter is constructed by adding two excitation vectors from adaptive and fixed (innovative) codebooks. The speech is synthesized by feeding the two properly chosen vectors from these codebooks through the short-term synthesis filter. The optimum excitation sequence in a codebook is chosen using an analysis-by-synthesis search procedure in which the error between the original and synthesized speech is minimized according to a perceptually weighted distortion measure.
+
+The perceptual weighting filter used in the analysis-by-synthesis search technique is given by:
+
+$$W(z) = \frac{A(z/g_1)}{A(z/g_2)} \quad (3)$$
+
+where  $A(z)$  is the unquantized LP filter and  $0 < g_2 < g_1 \leq 1$  are the perceptual weighting factors. The values  $g_1 = 0.9$  and  $g_2 = 0.6$  are used. The weighting filter uses the unquantized LP parameters while the formant synthesis filter uses the quantified ones.
+
+The coder operates on speech frames of 20 ms corresponding to 160 samples at the sampling frequency of 8 000 sample/s. At each 160 speech samples, the speech signal is analysed to extract the parameters of the CELP model (LP filter coefficients, adaptive and fixed codebooks' indices and gains). These parameters are encoded and transmitted. At the decoder, these parameters are decoded and speech is synthesized by filtering the reconstructed excitation signal through the LP synthesis filter.
+
+The signal flow at the encoder is shown in figure 3. LP analysis is performed twice per frame. The two sets of LP parameters are converted to line spectrum pairs (LSP) and jointly quantified using split matrix quantization (SMQ) with 38 bits. The speech frame is divided into 4 subframes of 5 ms each (40 samples). The adaptive and fixed codebook parameters are transmitted every subframe. The two sets of quantified and unquantized LP filters are used for the second and fourth subframes while in the first and third subframes interpolated LP filters are used (both quantified and unquantized). An open-loop pitch lag is estimated twice per frame (every 10 ms) based on the perceptually weighted speech signal.
+
+Then the following operations are repeated for each subframe:
+
+The target signal  $x(n)$  is computed by filtering the LP residual through the weighted synthesis filter  $W(z)H(z)$  with the initial states of the filters having been updated by filtering the error between LP residual and excitation (this is equivalent to the common approach of subtracting the zero input response of the weighted synthesis filter from the weighted speech signal).
+
+The impulse response,  $h(n)$  of the weighted synthesis filter is computed.
+
+Closed-loop pitch analysis is then performed (to find the pitch lag and gain), using the target  $x(n)$  and impulse response  $h(n)$ , by searching around the open-loop pitch lag. Fractional pitch with 1/6th of a sample resolution is used. The pitch lag is encoded with 9 bits in the first and third subframes and relatively encoded with 6 bits in the second and fourth subframes.
+
+The target signal  $x(n)$  is updated by removing the adaptive codebook contribution (filtered adaptive codevector), and this new target,  $x_2(n)$ , is used in the fixed algebraic codebook search (to find the optimum innovation). An algebraic codebook with 35 bits is used for the innovative excitation.
+
+The gains of the adaptive and fixed codebook are scalar quantified with 4 and 5 bits respectively (with moving average (MA) prediction applied to the fixed codebook gain).
+
+Finally, the filter memories are updated (using the determined excitation signal) for finding the target signal in the next subframe.
+
+The bit allocation of the codec is shown in table 1. In each 20 ms speech frame, 244 bits are produced, corresponding to a bit rate of 12.2 kbit/s. More detailed bit allocation is available in table 6. Note that the most significant bits (MSB) are always sent first.
+
+**Table 1: Bit allocation of the 12.2 kbit/s coding algorithm for 20 ms frame**
+
+| Parameter      | 1st & 3rd subframes | 2nd & 4th subframes | total per frame |
+|----------------|---------------------|---------------------|-----------------|
+| 2 LSP sets     |                     |                     | 38              |
+|                |                     |                     |                 |
+| Pitch delay    | 9                   | 6                   | 30              |
+| Pitch gain     | 4                   | 4                   | 16              |
+| Algebraic code | 35                  | 35                  | 140             |
+| Codebook gain  | 5                   | 5                   | 20              |
+| Total          |                     |                     | 244             |
+
+## 4.4 Principles of the GSM enhanced full rate speech decoder
+
+The signal flow at the decoder is shown in figure 4. At the decoder, the transmitted indices are extracted from the received bitstream. The indices are decoded to obtain the coder parameters at each transmission frame. These parameters are the two LSP vectors, the 4 fractional pitch lags, the 4 innovative codevectors, and the 4 sets of pitch and innovative gains. The LSP vectors are converted to the LP filter coefficients and interpolated to obtain LP filters at each subframe. Then, at each 40-sample subframe:
+
+- the excitation is constructed by adding the adaptive and innovative codevectors scaled by their respective gains;
+- the speech is reconstructed by filtering the excitation through the LP synthesis filter.
+
+Finally, the reconstructed speech signal is passed through an adaptive postfilter.
+
+## 4.5 Sequence and subjective importance of encoded parameters
+
+The encoder will produce the output information in a unique sequence and format, and the decoder must receive the same information in the same way. In table 6, the sequence of output bits s1 to s244 and the bit allocation for each parameter is shown.
+
+The different parameters of the encoded speech and their individual bits have unequal importance with respect to subjective quality. Before being submitted to the channel encoding function the bits have to be rearranged in the sequence of importance as given in table 6 in 05.03 [3].
+
+# 5 Functional description of the encoder
+
+In this clause, the different functions of the encoder represented in figure 3 are described.
+
+## 5.1 Pre-processing
+
+Two pre-processing functions are applied prior to the encoding process: high-pass filtering and signal down-scaling.
+
+Down-scaling consists of dividing the input by a factor of 2 to reduce the possibility of overflows in the fixed-point implementation.
+
+The high-pass filter serves as a precaution against undesired low frequency components. A filter with a cut off frequency of 80 Hz is used, and it is given by:
+
+$$H_{h1}(z) = \frac{0.92727435 - 1.8544941z^{-1} + 0.92727435z^{-2}}{1 - 1.9059465z^{-1} + 0.9114024z^{-2}}. \quad (4)$$
+
+Down-scaling and high-pass filtering are combined by dividing the coefficients at the numerator of  $H_{h1}(z)$  by 2.
+
+## 5.2 Linear prediction analysis and quantization
+
+Short-term prediction, or linear prediction (LP), analysis is performed twice per speech frame using the auto-correlation approach with 30 ms asymmetric windows. No lookahead is used in the auto-correlation computation.
+
+The auto-correlations of windowed speech are converted to the LP coefficients using the Levinson-Durbin algorithm. Then the LP coefficients are transformed to the Line Spectral Pair (LSP) domain for quantization and interpolation purposes. The interpolated quantified and unquantized filter coefficients are converted back to the LP filter coefficients (to construct the synthesis and weighting filters at each subframe).
+
+### 5.2.1 Windowing and auto-correlation computation
+
+LP analysis is performed twice per frame using two different asymmetric windows. The first window has its weight concentrated at the second subframe and it consists of two halves of Hamming windows with different sizes. The window is given by:
+
+$$w_I(n) = \begin{cases} 0.54 - 0.46\cos\left(\frac{\pi n}{L_1(n)-1}\right), & n = 0, K, L_1(n) - 1, \\ 0.54 + 0.46\cos\left(\frac{\pi(n-L_1(n))}{L_2(n)-1}\right), & n = L_1(n), K, L_1(n) + L_2(n) - 1. \end{cases} \quad (5)$$
+
+The values  $L_1(n) = 160$  and  $L_2(n) = 80$  are used. The second window has its weight concentrated at the fourth subframe and it consists of two parts: the first part is half a Hamming window and the second part is a quarter of a cosine function cycle. The window is given by:
+
+$$w_{II}(n) = \begin{cases} 0.54 - 0.46\cos\left(\frac{2\pi n}{2L_1(n)-1}\right), & n = 0, K, L_1(n) - 1, \\ \cos\left(\frac{2\pi(n-L_1(n))}{4L_2(n)-1}\right), & n = L_1(n), K, L_1(n) + L_2(n) - 1 \end{cases} \quad (6)$$
+
+where the values  $L_1(n) = 232$  and  $L_2(n) = 8$  are used.
+
+Note that both LP analyses are performed on the same set of speech samples. The windows are applied to 80 samples from past speech frame in addition to the 160 samples of the present speech frame. No samples from future frames are used (no lookahead). A diagram of the two LP analysis windows is depicted below.
+
+![Figure 1: LP analysis windows. The diagram shows two overlapping window functions, w_I(n) and w_II(n), plotted against time t. The horizontal axis is divided into 'frame n-1' and 'frame n'. 'frame n-1' is a 20 ms duration (160 samples). 'frame n' starts 5 ms after 'frame n-1' and contains a 'sub frame' of 40 samples. The window w_I(n) is a smooth curve that rises and falls within frame n-1. The window w_II(n) is a curve that starts at the beginning of frame n and falls to zero at the end of the sub frame.](0332672e127cd13bb6d2fc8d1e27bfa2_img.jpg)
+
+Figure 1: LP analysis windows. The diagram shows two overlapping window functions, w\_I(n) and w\_II(n), plotted against time t. The horizontal axis is divided into 'frame n-1' and 'frame n'. 'frame n-1' is a 20 ms duration (160 samples). 'frame n' starts 5 ms after 'frame n-1' and contains a 'sub frame' of 40 samples. The window w\_I(n) is a smooth curve that rises and falls within frame n-1. The window w\_II(n) is a curve that starts at the beginning of frame n and falls to zero at the end of the sub frame.
+
+**Figure 1: LP analysis windows**
+
+The auto-correlations of the windowed speech  $s'(n)$ ,  $n = 0, K, 239$ , are computed by:
+
+$$r_{ac}(k) = \sum_{n=k}^{239} s'(n)s'(n-k), \quad k = 0, K, 10, \quad (7)$$
+
+and a 60 Hz bandwidth expansion is used by lag windowing the auto-correlations using the window:
+
+$$w_{lag}(i) = \exp \left[ -\frac{1}{2} \left( \frac{2p f_0 i}{f_s} \right)^2 \right], \quad i = 1, K, 10, \quad (8)$$
+
+where  $f_0 = 60$  Hz is the bandwidth expansion and  $f_s = 8000$  Hz is the sampling frequency. Further,  $r_{ac}(0)$  is multiplied by the white noise correction factor 1.0001 which is equivalent to adding a noise floor at -40 dB.
+
+### 5.2.2 Levinson-Durbin algorithm
+
+The modified auto-correlations  $r'_{ac}(0) = 1.0001 r_{ac}(0)$  and  $r'_{ac}(k) = r_{ac}(k) w_{lag}(k)$ ,  $k = 1, K, 10$ , are used to obtain the direct form LP filter coefficients  $a_k$ ,  $k = 1, K, 10$ , by solving the set of equations.
+
+$$\sum_{k=1}^{10} a_k r'_{ac}(|i-k|) = -r'_{ac}(i), \quad i = 1, K, 10. \quad (9)$$
+
+The set of equations in (9) is solved using the Levinson-Durbin algorithm. This algorithm uses the following recursion:
+
+$$\begin{aligned} E_{LD}(0) &= r'_{ac}(0) \\ \text{for } i &= 1 \text{ to } 10 \text{ do} \\ a_0^{(i-1)} &= 1 \\ k_i &= -\left[ \sum_{j=1}^{i-1} a_j^{(i-1)} r'_{ac}(i-j) \right] / E_{LD}(i-1) \\ a_i^{(i)} &= k_i \\ \text{for } j &= 1 \text{ to } i-1 \text{ do} \\ a_j^{(i)} &= a_j^{(i-1)} + k_i a_{i-j}^{(i-1)} \\ \text{end} \\ E_{LD}(i) &= (1 - k_i^2) E_{LD}(i-1) \\ \text{end} \end{aligned}$$
+
+The final solution is given as  $a_j = a_j^{(10)}$ ,  $j = 1, K, 10$ .
+
+The LP filter coefficients are converted to the line spectral pair (LSP) representation for quantization and interpolation purposes. The conversions to the LSP domain and back to the LP filter coefficient domain are described in the next clause.
+
+### 5.2.3 LP to LSP conversion
+
+The LP filter coefficients  $a_k, k = 1, K, 10$ , are converted to the line spectral pair (LSP) representation for quantization and interpolation purposes. For a 10th order LP filter, the LSPs are defined as the roots of the sum and difference polynomials:
+
+$$F'_1(z) = A(z) + z^{-11}A(z^{-1}) \quad (10)$$
+
+and
+
+$$F'_2(z) = A(z) - z^{-11}A(z^{-1}), \quad (11)$$
+
+respectively. The polynomial  $F'_1(z)$  and  $F'_2(z)$  are symmetric and anti-symmetric, respectively. It can be proven that all roots of these polynomials are on the unit circle and they alternate each other.  $F'_1(z)$  has a root  $z = -1 (w = \pi)$  and  $F'_2(z)$  has a root  $z = 1 (w = 0)$ . To eliminate these two roots, we define the new polynomials:
+
+$$F_1(z) = F'_1(z)/(1 + z^{-1}) \quad (12)$$
+
+and
+
+$$F_2(z) = F'_2(z)/(1 - z^{-1}). \quad (13)$$
+
+Each polynomial has 5 conjugate roots on the unit circle ( $e^{\pm jw_i}$ ), therefore, the polynomials can be written as
+
+$$F_1(z) = \prod_{i=1,3,5,7,9} (1 - 2q_i z^{-1} + z^{-2}) \quad (14)$$
+
+and
+
+$$F_2(z) = \prod_{i=2,4,6,8,10} (1 - 2q_i z^{-1} + z^{-2}), \quad (15)$$
+
+where  $q_i = \cos(w_i)$  with  $w_i$  being the line spectral frequencies (LSF) and they satisfy the ordering property  $0 < w_1 < w_2 < \dots < w_{10} < \pi$ . We refer to  $q_i$  as the LSPs in the cosine domain.
+
+Since both polynomials  $F_1(z)$  and  $F_2(z)$  are symmetric only the first 5 coefficients of each polynomial need to be computed. The coefficients of these polynomials are found by the recursive relations (for  $i = 0$  to 4):
+
+$$\begin{aligned} f_1(i+1) &= a_{i+1} + a_{m-i} - f_1(i), \\ f_2(i+1) &= a_{i+1} - a_{m-i} + f_2(i), \end{aligned} \quad (16)$$
+
+where  $m = 10$  is the predictor order.
+
+The LSPs are found by evaluating the polynomials  $F_1(z)$  and  $F_2(z)$  at 60 points equally spaced between 0 and  $\pi$  and checking for sign changes. A sign change signifies the existence of a root and the sign change interval is then divided 4 times to better track the root. The Chebyshev polynomials are used to evaluate  $F_1(z)$  and  $F_2(z)$ . In this method the roots are found directly in the cosine domain  $\{q_i\}$ . The polynomials  $F_1(z)$  or  $F_2(z)$  evaluated at  $z = e^{jw}$  can be written as:
+
+$$F(w) = 2e^{-j5w}C(x),$$
+
+with:
+
+$$C(x) = T_5(x) + f(1)T_4(x) + f(2)T_3(x) + f(3)T_2(x) + f(4)T_1(x) + f(5)/2, \quad (17)$$
+
+where  $T_m(x) = \cos(mw)$  is the  $m$ th order Chebyshev polynomial, and  $f(i), i = 1, 2, 3, 4, 5$ , are the coefficients of either  $F_1(z)$  or  $F_2(z)$ , computed using the equations in (16). The polynomial  $C(x)$  is evaluated at a certain value of  $x = \cos(w)$  using the recursive relation:
+
+$$\begin{aligned} &\text{for } k = 4 \text{ down to } 1 \\ \lambda_k &= 2x\lambda_{k+1} - \lambda_{k+2} + f(5 - k) \text{ end} \\ C(x) &= x\lambda_1 - \lambda_2 + f(5)/2, \end{aligned}$$
+
+with initial values  $\lambda_5 = 1$  and  $\lambda_6 = 0$ . The details of the Chebyshev polynomial evaluation method are found in P. Kabal and R.P. Ramachandran [6].
+
+### 5.2.4 LSP to LP conversion
+
+Once the LSPs are quantified and interpolated, they are converted back to the LP coefficient domain  $\{a_k\}$ . The conversion to the LP domain is done as follows. The coefficients of  $F_1(z)$  or  $F_2(z)$  are found by expanding equations (14) and (15) knowing the quantified and interpolated LSPs  $q_i, i=1, K, 10$ . The following recursive relation is used to compute  $f_1(i)$ :
+
+```
+
+    for  $i = 1$  to  $5$ 
+ $f_1(i) = -2q_{2i-1}f_1(i-1) + 2f_1(i-2)$ 
+    for  $j = i-1$  down to  $1$ 
+ $f_1(j) = f_1(j) - 2q_{2i-1}f_1(j-1) + f_1(j-2)$ 
+    end
+end
+
+```
+
+with initial values  $f_1(0) = 1$  and  $f_1(-1) = 0$ . The coefficients  $f_2(i)$  are computed similarly by replacing  $q_{2i-1}$  by  $q_{2i}$ .
+
+Once the coefficients  $f_1(i)$  and  $f_2(i)$  are found,  $F_1(z)$  and  $F_2(z)$  are multiplied by  $1 + z^{-1}$  and  $1 - z^{-1}$ , respectively, to obtain  $F'_1(z)$  and  $F'_2(z)$ ; that is:
+
+$$\begin{aligned} f'_1(i) &= f_1(i) + f_1(i-1), & i = 1, K, 5, \\ f'_2(i) &= f_2(i) - f_2(i-1), & i = 1, K, 5. \end{aligned} \quad (18)$$
+
+Finally the LP coefficients are found by:
+
+$$a_i = \begin{cases} 0.5f'_1(i) + 0.5f'_2(i), & i = 1, K, 5, \\ 0.5f'_1(11-i) - 0.5f'_2(11-i), & i = 6, K, 10. \end{cases} \quad (19)$$
+
+This is directly derived from the relation  $A(z) = (F'_1(z) + F'_2(z))/2$ , and considering the fact that  $F'_1(z)$  and  $F'_2(z)$  are symmetric and anti-symmetric polynomials, respectively.
+
+### 5.2.5 Quantization of the LSP coefficients
+
+The two sets of LP filter coefficients per frame are quantified using the LSP representation in the frequency domain; that is:
+
+$$f_i = \frac{f_s}{2\pi} \arccos(q_i), i = 1, K, 10, \quad (20)$$
+
+where  $f_i$  are the line spectral frequencies (LSF) in Hz [0,4000] and  $f_s = 8000$  is the sampling frequency. The LSF vector is given by  $f^t = [f_1 f_2 K f_{10}]$ , with  $t$  denoting transpose.
+
+A 1st order MA prediction is applied, and the two residual LSF vectors are jointly quantified using split matrix quantization (SMQ). The prediction and quantization are performed as follows. Let  $z^{(1)}(n)$  and  $z^{(2)}(n)$  denote the mean-removed LSF vectors at frame  $n$ . The prediction residual vectors  $r^{(1)}(n)$  and  $r^{(2)}(n)$  are given by:
+
+$$\begin{aligned} r^{(1)}(n) &= z^{(1)}(n) - p(n), \text{ and} \\ r^{(2)}(n) &= z^{(2)}(n) - p(n), \end{aligned} \quad (21)$$
+
+where  $p(n)$  is the predicted LSF vector at frame  $n$ . First order moving-average (MA) prediction is used where:
+
+$$p(n) = 0.65 \{\hat{r}^{(2)}(n-1)\} \quad (22)$$
+
+where  $\hat{r}^{(2)}(n-1)$  is the quantified second residual vector at the past frame.
+
+The two LSF residual vectors  $r^{(1)}$  and  $r^{(2)}$  are jointly quantified using split matrix quantization (SMQ). The matrix  $(r^{(1)} r^{(2)})$  is split into 5 submatrices of dimension  $2 \times 2$  (two elements from each vector). For example, the first submatrix consists of the elements  $r_{1(1)}, r_{2(1)}, r_{1(2)}$ , and  $r_{2(2)}$ . The 5 submatrices are quantified with 7, 8, 8+1, 8, and 6 bits, respectively. The third submatrix uses a 256-entry signed codebook (8-bit index plus 1-bit sign).
+
+A weighted LSP distortion measure is used in the quantization process. In general, for an input LSP vector  $f$  and a quantified vector at index  $k$ ,  $\hat{f}^k$ , the quantization is performed by finding the index  $k$  which minimizes:
+
+$$E_{\text{LSP}} = \sum_{i=1}^{10} [f_i w_i - \hat{f}_i^k w_i]^2. \quad (23)$$
+
+The weighting factors  $w_i, i = 1, K, 10$ , are given by
+
+$$\begin{aligned} w_i &= 3.347 - \frac{1.547}{450} d_i \text{ for } d_i < 450, \\ &= 1.8 - \frac{0.8}{1050} (d_i - 450) \text{ otherwise,} \end{aligned} \quad (24)$$
+
+where  $d_i = f_{i+1} - f_{i-1}$  with  $f_0 = 0$  and  $f_{11} = 4000$ . Here, two sets of weighting coefficients are computed for the two LSF vectors. In the quantization of each submatrix, two weighting coefficients from each set are used with their corresponding LSFs.
+
+### 5.2.6 Interpolation of the LSPs
+
+The two sets of quantified (and unquantized) LP parameters are used for the second and fourth subframes whereas the first and third subframes use a linear interpolation of the parameters in the adjacent subframes. The interpolation is performed on the LSPs in the  $q$  domain. Let  $q_4^{(n)}$  be the LSP vector at the 4th subframe of the present frame  $n$ ,  $q_2^{(n)}$  be the LSP vector at the 2nd subframe of the present frame  $n$ , and  $q_4^{(n-1)}$  the LSP vector at the 4th subframe of the past frame  $n - 1$ . The interpolated LSP vectors at the 1st and 3rd subframes are given by:
+
+$$\begin{aligned} q_1^{(n)} &= 0.5 q_4^{(n-1)} + 0.5 q_2^{(n)}, \\ q_3^{(n)} &= 0.5 q_2^{(n)} + 0.5 q_4^{(n)}. \end{aligned} \quad (25)$$
+
+The interpolated LSP vectors are used to compute a different LP filter at each subframe (both quantified and unquantized coefficients) using the LSP to LP conversion method described in clause 5.2.4.
+
+## 5.3 Open-loop pitch analysis
+
+Open-loop pitch analysis is performed twice per frame (each 10 ms) to find two estimates of the pitch lag in each frame. This is done in order to simplify the pitch analysis and confine the closed-loop pitch search to a small number of lags around the open-loop estimated lags.
+
+Open-loop pitch estimation is based on the weighted speech signal  $s_w(n)$  which is obtained by filtering the input speech signal through the weighting filter  $W(z) = \frac{A(z/g_1)}{A(z/g_2)}$ . That is, in a subframe of size  $L$ , the weighted speech is given by:
+
+$$s_w(n) = s(n) + \sum_{i=1}^{10} a_i g_1^i s(n-i) - \sum_{i=1}^{10} a_i g_2^i s_w(n-i), n = 0, K, L-1. \quad (26)$$
+
+Open-loop pitch analysis is performed as follows. In the first step, 3 maxima of the correlation:
+
+$$O_k = \sum_{n=0}^{79} s_w(n) s_w(n-k) \quad (27)$$
+
+are found in the three ranges:
+
+$$\begin{aligned} i &= 3: 18, K, 35, \\ i &= 2: 36, K, 71, \\ i &= 1: 72, K, 143. \end{aligned}$$
+
+The retained maxima  $O_{t_i}, i = 1, K, 3$ , are normalized by dividing by  $\sqrt{\sum s_w^2(n-t_i)}, i = 1, K, 3$ , respectively. The normalized maxima and corresponding delays are denoted by  $(M_i, t_i), i = 1, K, 3$ . The winner,  $T_{op}$ , among the three normalized correlations is selected by favouring the delays with the values in the lower range. This is performed by weighting the normalized correlations corresponding to the longer delays. The best open-loop delay  $T_{op}$  is determined as follows:
+
+```
+
+ $T_{op} = t_1$ 
+ $M(T_{op}) = M_1$ 
+if  $M_2 > 0.85M(T_{op})$ 
+   $M(T_{op}) = M_2$ 
+   $T_{op} = t_2$ 
+end
+if  $M_3 > 0.85M(T_{op})$ 
+   $M(T_{op}) = M_3$ 
+   $T_{op} = t_3$ 
+end
+
+```
+
+This procedure of dividing the delay range into 3 clauses and favouring the lower clauses is used to avoid choosing pitch multiples.
+
+## 5.4 Impulse response computation
+
+The impulse response,  $h(n)$ , of the weighted synthesis filter  $H(z)W(z) = A(z/g_1)/[\hat{A}(z)A(z/g_2)]$  is computed each subframe. This impulse response is needed for the search of adaptive and fixed codebooks. The impulse response  $h(n)$  is computed by filtering the vector of coefficients of the filter  $A(z/g_1)$  extended by zeros through the two filters  $1/\hat{A}(z)$  and  $1/A(z/g_2)$ .
+
+## 5.5 Target signal computation
+
+The target signal for adaptive codebook search is usually computed by subtracting the zero input response of the weighted synthesis filter  $H(z)W(z) = A(z/g_1)/[\hat{A}(z)A(z/g_2)]$  from the weighted speech signal  $s_w(n)$ . This is performed on a subframe basis.
+
+An equivalent procedure for computing the target signal, which is used in the present document, is the filtering of the LP residual signal  $res_{LP}(n)$  through the combination of synthesis filter  $1/\hat{A}(z)$  and the weighting filter  $A(z/g_1)/A(z/g_2)$ . After determining the excitation for the subframe, the initial states of these filters are updated by filtering the difference between the LP residual and excitation. The memory update of these filters is explained in clause 5.9.
+
+The residual signal  $res_{LP}(n)$  which is needed for finding the target vector is also used in the adaptive codebook search to extend the past excitation buffer. This simplifies the adaptive codebook search procedure for delays less than the subframe size of 40 as will be explained in the next clause. The LP residual is given by:
+
+$$res_{LP}(n) = s(n) + \sum_{i=1}^{10} \hat{a}_i s(n-i). \quad (28)$$
+
+## 5.6 Adaptive codebook search
+
+Adaptive codebook search is performed on a subframe basis. It consists of performing closed-loop pitch search, and then computing the adaptive codevector by interpolating the past excitation at the selected fractional pitch lag.
+
+The adaptive codebook parameters (or pitch parameters) are the delay and gain of the pitch filter. In the adaptive codebook approach for implementing the pitch filter, the excitation is repeated for delays less than the subframe length. In the search stage, the excitation is extended by the LP residual to simplify the closed-loop search.
+
+In the first and third subframes, a fractional pitch delay is used with resolutions:  $1/6$  in the range  $[17\frac{3}{6}, 94\frac{3}{6}]$  and integers only in the range [95, 143]. For the second and fourth subframes, a pitch resolution of  $1/6$  is always used in the range  $[T_1 - 5\frac{3}{6}, T_1 + 4\frac{3}{6}]$ , where  $T_1$  is nearest integer to the fractional pitch lag of the previous (1st or 3rd) subframe, bounded by 18...143.
+
+Closed-loop pitch analysis is performed around the open-loop pitch estimates on a subframe basis. In the first (and third) subframe the range  $T_{op} \pm 3$ , bounded by 18...143, is searched. For the other subframes, closed-loop pitch analysis is performed around the integer pitch selected in the previous subframe, as described above. The pitch delay is encoded with 9 bits in the first and third subframes and the relative delay of the other subframes is encoded with 6 bits.
+
+The closed-loop pitch search is performed by minimizing the mean-square weighted error between the original and synthesized speech. This is achieved by maximizing the term:
+
+$$R(k) = \frac{\sum x(n)y_k(n)}{\sqrt{\sum y_k(n)y_k(n)}}, \quad (29)$$
+
+where  $x(n)$  is the target signal and  $y_k(n)$  is the past filtered excitation at delay  $k$  (past excitation convolved with  $h(n)$ ). Note that the search range is limited around the open-loop pitch as explained earlier.
+
+The convolution  $y_k(n)$  is computed for the first delay  $t_{min}$  in the searched range, and for the other delays in the search range  $k = t_{min} + 1, \dots, t_{max}$ , it is updated using the recursive relation:
+
+$$y_k(n) = y_{k-1}(n-1) + u(-k)h(n), \quad (30)$$
+
+where  $u(n), n = -(143 + 11), K, 39$ , is the excitation buffer. Note that in search stage, the samples  $u(n), n = 0, K, 39$ , are not known, and they are needed for pitch delays less than 40. To simplify the search, the LP residual is copied to  $u(n)$  in order to make the relation in equation (30) valid for all delays.
+
+Once the optimum integer pitch delay is determined, the fractions from  $-\frac{3}{6}$  to  $\frac{3}{6}$  with a step of  $\frac{1}{6}$  around that integer are tested. The fractional pitch search is performed by interpolating the normalized correlation in equation (29) and searching for its maximum. The interpolation is performed using an FIR filter  $b_{24}$  based on a Hamming windowed  $\sin(x)/x$  function truncated at  $\pm 23$  and padded with zeros at  $\pm 24$  ( $b_{24}(24) = 0$ ). The filter has its cut-off frequency (-3 dB) at 3 600 Hz in the over-sampled domain. The interpolated values of  $R(k)$  for the fractions  $-\frac{3}{6}$  to  $\frac{3}{6}$  are obtained using the interpolation formula:
+
+$$R(k)_t = \sum_{i=0}^3 R(k-i)b_{24}(t+i \cdot 6) + \sum_{i=0}^3 R(k+1+i)b_{24}(6-t+i \cdot 6), t = 0, K, 5, \quad (31)$$
+
+where  $t = 0, K, 5$  corresponds to the fractions  $0, \frac{1}{6}, \frac{2}{6}, \frac{3}{6}, -\frac{2}{6}$ , and  $-\frac{1}{6}$ , respectively. Note that it is necessary to compute the correlation terms in equation (29) using a range  $t_{min} - 4, t_{max} + 4$ , to allow for the proper interpolation.
+
+Once the fractional pitch lag is determined, the adaptive codebook vector  $v(n)$  is computed by interpolating the past excitation signal  $u(n)$  at the given integer delay  $k$  and phase (fraction)  $t$ :
+
+$$v(n) = \sum_{i=0}^9 u(n-k-i)b_{60}(t+i \cdot 6) + \sum_{i=0}^9 u(n-k+1+i)b_{60}(6-t+i \cdot 6), n = 0, K, 39, t = 0, K, 5. \quad (32)$$
+
+The interpolation filter  $b_{60}$  is based on a Hamming windowed  $\sin(x)/x$  function truncated at  $\pm 59$  and padded with zeros at  $\pm 60$  ( $b_{60}(60) = 0$ ). The filter has a cut-off frequency (-3 dB) at 3 600 Hz in the over-sampled domain.
+
+The adaptive codebook gain is then found by:
+
+$$g_p = \frac{\sum x(n)y(n)}{\sum y(n)y(n)} \text{ bounded by } 0 \leq g_p \leq 1.2, \quad (33)$$
+
+where  $y(n) = v(n) * h(n)$  is the filtered adaptive codebook vector (zero state response of  $H(z)W(z)$  to  $v(n)$ ).
+
+The computed adaptive codebook gain is quantified using 4-bit non-uniform scalar quantization in the range [0.0, 1.2].
+
+## 5.7 Algebraic codebook structure and search
+
+The algebraic codebook structure is based on interleaved single-pulse permutation (ISPP) design. In this codebook, the innovation vector contains 10 non-zero pulses. All pulses can have the amplitudes +1 or -1. The 40 positions in a subframe are divided into 5 tracks, where each track contains two pulses, as shown in table 2.
+
+**Table 2: Potential positions of individual pulses in the algebraic codebook**
+
+| Track | Pulse                           | positions                    |
+|-------|---------------------------------|------------------------------|
+| 1     | i <sub>0</sub> , i <sub>5</sub> | 0, 5, 10, 15, 20, 25, 30, 35 |
+| 2     | i <sub>1</sub> , i <sub>6</sub> | 1, 6, 11, 16, 21, 26, 31, 36 |
+| 3     | i <sub>2</sub> , i <sub>7</sub> | 2, 7, 12, 17, 22, 27, 32, 37 |
+| 4     | i <sub>3</sub> , i <sub>8</sub> | 3, 8, 13, 18, 23, 28, 33, 38 |
+| 5     | i <sub>4</sub> , i <sub>9</sub> | 4, 9, 14, 19, 24, 29, 34, 39 |
+
+Each two pulse positions in one track are encoded with 6 bits (total of 30 bits, 3 bits for the position of every pulse), and the sign of the first pulse in the track is encoded with 1 bit (total of 5 bits).
+
+For two pulses located in the same track, only one sign bit is needed. This sign bit indicates the sign of the first pulse. The sign of the second pulse depends on its position relative to the first pulse. If the position of the second pulse is smaller, then it has opposite sign, otherwise it has the same sign than in the first pulse.
+
+All the 3-bit pulse positions are Gray coded in order to improve robustness against channel errors. This gives a total of 35 bits for the algebraic code.
+
+The algebraic codebook is searched by minimizing the mean square error between the weighted input speech and the weighted synthesized speech. The target signal used in the closed-loop pitch search is updated by subtracting the adaptive codebook contribution. That is:
+
+$$x_2(n) = x(n) - \hat{g}_p y(n), n = 0, K, 39, \quad (34)$$
+
+where  $y(n) = v(n) * h(n)$  is the filtered adaptive codebook vector and  $\hat{g}_p$  is the quantified adaptive codebook gain. If  $c_k$  is the algebraic codevector at index  $k$ , then the algebraic codebook is searched by maximizing the term:
+
+$$A_k = \frac{(c_k)^2}{E_{D_k}} = \frac{(d^t c_k)^2}{c_k^t F c_k} \quad (35)$$
+
+where  $d = H^t x_2$  is the correlation between the target signal  $x_2(n)$  and the impulse response  $h(n)$ ,  $H$  is a the lower triangular Toeplitz convolution matrix with diagonal  $h(0)$  and lower diagonals  $h(1), K, h(39)$ , and  $F = H^t H$  is the matrix of correlations of  $h(n)$ . The vector  $d$  (backward filtered target) and the matrix  $F$  are computed prior to the codebook search. The elements of the vector  $d$  are computed by
+
+$$d(n) = \sum_{i=n}^{39} x_2(i)h(i-n), n = 0, K, 39, \quad (36)$$
+
+and the elements of the symmetric matrix  $F$  are computed by:
+
+$$f(i, j) = \sum_{n=j}^{39} h(n-i)h(n-j), (j^3 i). \quad (37)$$
+
+The algebraic structure of the codebooks allows for very fast search procedures since the innovation vector  $c_k$  contains only a few nonzero pulses. The correlation in the numerator of Equation (35) is given by:
+
+$$C = \sum_{i=0}^{N_p-1} J_i d(m_i) \quad (38)$$
+
+where  $m_i$  is the position of the  $i$ th pulse,  $J_i$  is its amplitude, and  $N_p$  is the number of pulses ( $N_p = 10$ ). The energy in the denominator of equation (35) is given by:
+
+$$E_D = \sum_{i=0}^{N_p-1} f(m_i, m_i) + 2 \sum_{i=0}^{N_p-2} \sum_{j=i+1}^{N_p-1} J_i J_j f(m_i, m_j). \quad (39)$$
+
+To simplify the search procedure, the pulse amplitudes are preset by the mere quantization of an appropriate signal. In this case the signal  $b(n)$ , which is a sum of the normalized  $d(n)$  vector and normalized long-term prediction residual  $res_{LTP}(n)$ :
+
+$$b(n) = \frac{res_{LTP}(n)}{\sqrt{\sum res_{LTP}(i)res_{LTP}(i)}} + \frac{d(n)}{\sqrt{\sum d(i)d(i)}}, n = 0, K, 39, \quad (40)$$
+
+is used. This is simply done by setting the amplitude of a pulse at a certain position equal to the sign of  $b(n)$  at that position. The simplification proceeds as follows (prior to the codebook search). First, the sign signal  $s_b(n) = \text{sign}[b(n)]$  and the signal  $d'(n) = d(n)s_b(n)$  are computed. Second, the matrix  $F$  is modified by including the sign information; that is,  $f'(i, j) = s_b(i)s_b(j)f(i, j)$ . The correlation in equation (38) is now given by:
+
+$$C = \sum_{i=0}^{N_p-1} d'(m_i) \quad (41)$$
+
+and the energy in equation (39) is given by:
+
+$$E_D = \sum_{i=0}^{N_p-1} f'(m_i, m_i) + 2 \sum_{i=0}^{N_p-2} \sum_{j=i+1}^{N_p-1} f'(m_i, m_j). \quad (42)$$
+
+Having preset the pulse amplitudes, as explained above, the optimal pulse positions are determined using an efficient non-exhaustive analysis-by-synthesis search technique. In this technique, the term in equation (35) is tested for a small percentage of position combinations.
+
+First, for each of the five tracks the pulse positions with maximum absolute values of  $b(n)$  are searched. From these the global maximum value for all the pulse positions is selected. The first pulse  $i_0$  is always set into the position corresponding to the global maximum value.
+
+Next, four iterations are carried out. During each iteration the position of pulse  $i_1$  is set to the local maximum of one track. The rest of the pulses are searched in pairs by sequentially searching each of the pulse pairs  $\{i_2, i_3\}$ ,  $\{i_4, i_5\}$ ,  $\{i_6, i_7\}$  and  $\{i_8, i_9\}$  in nested loops. Every pulse has 8 possible positions, i.e., there are four 8x8-loops, resulting in 256 different combinations of pulse positions for each iteration.
+
+In each iteration all the 9 pulse starting positions are cyclically shifted, so that the pulse pairs are changed and the pulse  $i_1$  is placed in a local maximum of a different track. The rest of the pulses are searched also for the other positions in the tracks. At least one pulse is located in a position corresponding to the global maximum and one pulse is located in a position corresponding to one of the 4 local maxima.
+
+A special feature incorporated in the codebook is that the selected codevector is filtered through an adaptive pre-filter  $F_E(z)$  which enhances special spectral components in order to improve the synthesized speech quality. Here the filter  $F_E(z) = 1/(1 - \beta z^{-T})$  is used, where  $T$  is the nearest integer pitch lag to the closed-loop fractional pitch lag of the subframe, and  $\beta$  is a pitch gain. In the present document,  $\beta$  is given by the quantified pitch gain bounded by  $[0.0, 1.0]$ . Note that prior to the codebook search, the impulse response  $h(n)$  must include the pre-filter  $F_E(z)$ . That is,  $h(n) = h(n) + \beta h(n - T)$ ,  $n = T, K, 39$ .
+
+The fixed codebook gain is then found by:
+
+$$g_c = \frac{x_2^t z}{z^t z} \quad (43)$$
+
+where  $x_2$  is the target vector for fixed codebook search and  $z$  is the fixed codebook vector convolved with  $h(n)$ ,
+
+$$z(n) = \sum_{i=0}^n c(i)h(n - i), n = 0, K, 39. \quad (44)$$
+
+## 5.8 Quantization of the fixed codebook gain
+
+The fixed codebook gain quantization is performed using MA prediction with fixed coefficients. The 4th order MA prediction is performed on the innovation energy as follows. Let  $E(n)$  be the mean-removed innovation energy (in dB) at subframe  $n$ , and given by:
+
+$$E(n) = 10\log\left(\frac{1}{N} \sum_{i=0}^{N-1} c^2(i)\right) - \bar{E}, \quad (45)$$
+
+where  $N = 40$  is the subframe size,  $c(i)$  is the fixed codebook excitation, and  $\bar{E} = 36$  dB is the mean of the innovation energy. The predicted energy is given by:
+
+$$\bar{E}(n) = \sum_{i=1}^4 b_i \hat{R}(n - i), \quad (46)$$
+
+where  $[b_1 b_2 b_3 b_4] = [0.680.580.340.19]$  are the MA prediction coefficients, and  $\hat{R}(k)$  is the quantified prediction error at subframe  $k$ . The predicted energy is used to compute a predicted fixed-codebook gain  $g'_c$  as in equation (45) (by substituting  $E(n)$  by  $\bar{E}(n)$  and  $g_c$  by  $g'_c$ ). This is done as follows. First, the mean innovation energy is found by:
+
+$$E_I = 10\log\left(\frac{1}{N} \sum_{j=0}^{N-1} c^2(j)\right) \quad (47)$$
+
+and then the predicted gain  $g'_c$  is found by:
+
+$$g'_c = 10^{0.05(\bar{E}(n) + \bar{E} - E_I)}. \quad (48)$$
+
+A correction factor between the gain  $g_c$  and the estimated one  $g'_c$  is given by:
+
+$$g_{gc} = g_c / g'_c. \quad (49)$$
+
+Note that the prediction error is given by:
+
+$$R(n) = E(n) - \bar{E}(n) = 20\log(g_{gc}). \quad (50)$$
+
+The correction factor  $g_{gc}$  is quantified using a 5-bit codebook. The quantization table search is performed by minimizing the error:
+
+$$E_Q = (g_c - \hat{g}_{gc}g'_c)^2. \quad (51)$$
+
+Once the optimum value  $\hat{g}_{gc}$  is chosen, the quantified fixed codebook gain is given by  $\hat{g}_c = \hat{g}_{gc}g'_c$ .
+
+## 5.9 Memory update
+
+An update of the states of the synthesis and weighting filters is needed in order to compute the target signal in the next subframe.
+
+After the two gains are quantified, the excitation signal,  $u(n)$ , in the present subframe is found by:
+
+$$u(n) = \hat{g}_p v(n) + \hat{g}_c c(n), n = 0, K, 39, \quad (52)$$
+
+where  $\hat{g}_p$  and  $\hat{g}_c$  are the quantified adaptive and fixed codebook gains, respectively,  $v(n)$  the adaptive codebook vector (interpolated past excitation), and  $c(n)$  is the fixed codebook vector (algebraic code including pitch sharpening). The states of the filters can be updated by filtering the signal  $\text{res}_{LP}(n) - u(n)$  (difference between residual and excitation) through the filters  $1/\hat{A}(z)$  and  $A(z/g_1)/A(z/g_2)$  for the 40-sample subframe and saving the states of the filters. This would require 3 filterings. A simpler approach which requires only one filtering is as follows. The local synthesized speech,  $\hat{s}(n)$ , is computed by filtering the excitation signal through  $1/\hat{A}(z)$ . The output of the filter due to the input  $\text{res}_{LP}(n) - u(n)$  is equivalent to  $e(n) = s(n) - \hat{s}(n)$ . So the states of the synthesis filter  $1/\hat{A}(z)$  are given by  $e(n), n = 30, K, 39$ . Updating the states of the filter  $A(z/g_1)/A(z/g_2)$  can be done by filtering the error signal  $e(n)$  through this filter to find the perceptually weighted error  $e_w(n)$ . However, the signal  $e_w(n)$  can be equivalently found by:
+
+$$e_w(n) = x(n) - \hat{g}_p y(n) - \hat{g}_c z(n). \quad (53)$$
+
+Since the signals  $x(n)$ ,  $y(n)$ , and  $z(n)$  are available, the states of the weighting filter are updated by computing  $e_w(n)$  as in equation (53) for  $n = 30, K, 39$ . This saves two filterings.
+
+# 6 Functional description of the decoder
+
+The function of the decoder consists of decoding the transmitted parameters (LP parameters, adaptive codebook vector, adaptive codebook gain, fixed codebook vector, fixed codebook gain) and performing synthesis to obtain the reconstructed speech. The reconstructed speech is then post-filtered and upsampled. The signal flow at the decoder is shown in figure 4.
+
+## 6.1 Decoding and speech synthesis
+
+The decoding process is performed in the following order:
+
+**Decoding of LP filter parameters:** The received indices of LSP quantization are used to reconstruct the two quantified LSP vectors. The interpolation described in clause 5.2.6 is performed to obtain 4 interpolated LSP vectors (corresponding to 4 subframes). For each subframe, the interpolated LSP vector is converted to LP filter coefficient domain  $a_k$ , which is used for synthesizing the reconstructed speech in the subframe.
+
+The following steps are repeated for each subframe:
+
+- 1) **Decoding of the adaptive codebook vector:** The received pitch index (adaptive codebook index) is used to find the integer and fractional parts of the pitch lag. The adaptive codebook vector  $v(n)$  is found by interpolating the past excitation  $u(n)$  (at the pitch delay) using the FIR filter described in clause 5.6.
+- 2) **Decoding of the adaptive codebook gain:** The received index is used to readily find the quantified adaptive codebook gain,  $\hat{g}_p$  from the quantization table.
+- 3) **Decoding of the innovative codebook vector:** The received algebraic codebook index is used to extract the positions and amplitudes (signs) of the excitation pulses and to find the algebraic codevector  $c(n)$ . If the integer
+
+part of the pitch lag is less than the subframe size 40, the pitch sharpening procedure is applied which translates into modifying  $c(n)$  by  $c(n) = c(n) + \beta c(n - T)$ , where  $\beta$  is the decoded pitch gain,  $\hat{g}_p$ , bounded by  $[0.0, 1.0]$ .
+
+- 4) **Decoding of the fixed codebook gain:** The received index gives the fixed codebook gain correction factor  $\hat{g}_{gc}$ . The estimated fixed codebook gain  $g'_c$  is found as described in clause 5.7. First, the predicted energy is found by:
+
+$$\bar{E}(n) = \sum_{i=1}^4 b_i \hat{R}(n - i) \quad (54)$$
+
+and then the mean innovation energy is found by:
+
+$$E_I = 10 \log \left( \frac{1}{N} \sum_{j=0}^{N-1} c^2(j) \right) \quad (55)$$
+
+The predicted gain  $g'_c$  is found by:
+
+$$g'_c = 10^{0.05(\bar{E}(n) + \bar{E} - E_I)} \quad (56)$$
+
+The quantified fixed codebook gain is given by:
+
+$$\hat{g}_c = \hat{g}_{gc} g'_c \quad (57)$$
+
+- 5) **Computing the reconstructed speech:** The excitation at the input of the synthesis filter is given by:
+
+$$u(n) = \hat{g}_p v(n) + \hat{g}_c c(n) \quad (58)$$
+
+Before the speech synthesis, a post-processing of excitation elements is performed. This means that the total excitation is modified by emphasizing the contribution of the adaptive codebook vector:
+
+$$\hat{u}(n) = \begin{cases} u(n) + 0.25\beta \hat{g}_p v(n), & \hat{g}_p > 0.5 \\ u(n), & \hat{g}_p \leq 0.5 \end{cases} \quad (59)$$
+
+Adaptive gain control (AGC) is used to compensate for the gain difference between the non-emphasized excitation  $u(n)$  and emphasized excitation  $\hat{u}(n)$ . The gain scaling factor  $\eta$  for the emphasized excitation is computed by:
+
+$$h = \begin{cases} \sqrt{\frac{\sum u^2(n)}{\sum \hat{u}^2(n)}}, & \hat{g}_p > 0.5 \\ 1.0 & \hat{g}_p \leq 0.5 \end{cases} \quad (60)$$
+
+The gain-scaled emphasized excitation signal  $\hat{u}'(n)$  is given by:
+
+$$\hat{u}'(n) = \hat{u}(n)h \quad (61)$$
+
+The reconstructed speech for the subframe of size 40 is given by:
+
+$$\hat{s}(n) = \hat{u}'(n) - \sum_{i=1}^{10} \hat{a}_i \hat{s}(n - i), \quad n = 0, K, 39. \quad (62)$$
+
+where  $\hat{a}_i$  are the interpolated LP filter coefficients.
+
+The synthesized speech  $\hat{s}(n)$  is then passed through an adaptive postfilter which is described in the following clause.
+
+## 6.2 Post-processing
+
+Post-processing consists of two functions: adaptive post-filtering and signal up-scaling.
+
+### 6.2.1 Adaptive post-filtering
+
+The adaptive postfilter is the cascade of two filters: a formant postfilter, and a tilt compensation filter. The postfilter is updated every subframe of 5 ms.
+
+The formant postfilter is given by:
+
+$$H_f(z) = \frac{A(z/g_n)}{A(z/g_d)} \quad (63)$$
+
+where  $\hat{A}(z)$  is the received quantified (and interpolated) LP inverse filter (LP analysis is not performed at the decoder), and the factors  $g_n$  and  $g_d$  control the amount of the formant post-filtering.
+
+Finally, the filter  $H_t(z)$  compensates for the tilt in the formant postfilter  $H_f(z)$  and is given by:
+
+$$H_t(z) = (1 - mz^{-1}) \quad (64)$$
+
+where  $m = g_t k_1'$  is a tilt factor, with  $k_1'$  being the first reflection coefficient calculated on the truncated ( $L_h = 22$ ) impulse response,  $h_f(n)$ , of the filter  $\hat{A}(z/g_n)/\hat{A}(z/g_d)$ .  $k_1'$  is given by:
+
+$$k_1' = \frac{r_h(1)}{r_h(0)}; r_h(i) = \sum_{j=0}^{L_h-i-1} h_f(j)h_f(j+i) \quad (65)$$
+
+The post-filtering process is performed as follows. First, the synthesized speech  $\hat{s}(n)$  is inverse filtered through  $\hat{A}(z/g_n)$  to produce the residual signal  $\hat{r}(n)$ . The signal  $\hat{r}(n)$  is filtered by the synthesis filter  $1/\hat{A}(z/g_d)$ . Finally, the signal at the output of the synthesis filter  $1/\hat{A}(z/g_d)$  is passed to the tilt compensation filter  $h_t(z)$  resulting in the post-filtered speech signal  $\hat{s}_f(n)$ .
+
+Adaptive gain control (AGC) is used to compensate for the gain difference between the synthesized speech signal  $\hat{s}(n)$  and the post-filtered signal  $\hat{s}_f(n)$ . The gain scaling factor  $g_{sc}$  for the present subframe is computed by:
+
+$$g_{sc} = \sqrt{\frac{\sum_{n=0}^{39} \hat{s}^2(n)}{\sum_{n=0}^{39} \hat{s}_f^2(n)}} \quad (66)$$
+
+The gain-scaled post-filtered signal  $\hat{s}'(n)$  is given by:
+
+$$\hat{s}'(n) = \beta_{sc}(n)\hat{s}_f(n) \quad (67)$$
+
+where  $\beta_{sc}(n)$  is updated in sample-by-sample basis and given by:
+
+$$\beta_{sc}(n) = \alpha\beta_{sc}(n-1) + (1-\alpha)g_{sc} \quad (68)$$
+
+where  $\alpha$  is a AGC factor with value of 0.9.
+
+The adaptive post-filtering factors are given by:  $g_n = 0.7$ ,  $g_d = 0.75$  and
+
+$$g_t = \begin{cases} 0.8, k_1' > 0 \\ 0, \text{otherwise} \end{cases} \quad (69)$$
+
+### 6.2.2 Up-scaling
+
+Up-scaling consists of multiplying the post-filtered speech by a factor of 2 to compensate for the down-scaling by 2 which is applied to the input signal.
+
+# 7 Variables, constants and tables in the C-code of the GSM EFR codec
+
+The various components of the 12,2 kbit/s GSM enhanced full rate codec are described in the form of a fixed-point bit-exact ANSI C code, which is found in GSM 06.53 [6]. This C simulation is an integrated software of the speech codec, VAD/DTX, comfort noise and bad frame handler functions. In the fixed-point ANSI C simulation, all the computations are performed using a predefined set of basic operators.
+
+Two types of variables are used in the fixed-point implementation. These two types are signed integers in 2's complement representation, defined by:
+
+**Word16** 16 bit variables
+
+**Word32** 32 bit variables
+
+The variables of the **Word16** type are denoted *var1*, *var2*, ..., *varn*, and those of type **Word32** are denoted *L\_var1*, *L\_var2*, ..., *L\_varn*.
+
+## 7.1 Description of the constants and variables used in the C code
+
+The ANSI C code simulation of the codec is, to a large extent, self-documented. However, a description of the variables and constants used in the code is given to facilitate the understanding of the code. The fixed-point precision (in terms of Q format, double precision (DP), or normalized precision) of the vectors and variables is given, along with the vectors dimensions and constant values.
+
+Table 3 gives the coder global constants and table 4 describes the variables and vectors used in the encoder routine with their precision. Table 5 describes the fixed tables in the codec.
+
+**Table 3: Codec global constants**
+
+| Parameter   | Value | Description                                                                      |
+|-------------|-------|----------------------------------------------------------------------------------|
+| L_TOTAL     | 240   | size of speech buffer                                                            |
+| L_WINDOW    | 240   | size of LP analysis window                                                       |
+| L_FRAME     | 160   | size of speech frame                                                             |
+| L_FRAME_BY2 | 80    | half the speech frame size                                                       |
+| L_SUBFR     | 40    | size of subframe                                                                 |
+| M           | 10    | order of LP analysis                                                             |
+| MP1         | 11    | $M+1$                                                                            |
+| AZ_SIZE     | 44    | $4*M+4$                                                                          |
+| PIT_MAX     | 143   | maximum pitch lag                                                                |
+| PIT_MIN     | 18    | minimum pitch lag                                                                |
+| L_INTERPOL  | 10    | order of sinc filter for interpolating<br>the excitations is $2*L\_INTERPOL*6+1$ |
+| PRM_SIZE    | 57    | size of vector of analysis parameters                                            |
+| SERIAL_SIZE | 245   | number of speech bits + bfi                                                      |
+| MU          | 26214 | tilt compensation filter factor (0.8 in Q15)                                     |
+| AGC_FAC     | 29491 | automatic gain control factor (0.9 in Q15)                                       |
+
+**Table 4: Description of the coder vectors and variables**
+
+| Parameter | Size           | Precision            | Description                                      |
+|-----------|----------------|----------------------|--------------------------------------------------|
+| speech    | -80..159       | Q0                   | speech buffer                                    |
+| wsp       | -143..159      | Q0                   | weighted speech buffer                           |
+| exc       | -(143+11)..159 | Q0                   | LP excitation                                    |
+| F_gamma1  | 0..9           | Q15                  | spectral expansion factors                       |
+| F_gamma2  | 0..9           | Q15                  | spectral expansion factors                       |
+| lsp_old   | 0..9           | Q15                  | LSP vector in past frame                         |
+| lsp_old_q | 0..9           | Q15                  | quantified LSP vector in past frame              |
+| mem_syn   | 0..9           | Q0                   | memory of synthesis filter                       |
+| mem_w     | 0..9           | Q0                   | memory of weighting filter (applied to input)    |
+| mem_wO    | 0..9           | Q0                   | memory of weighting filter (applied to error)    |
+| error     | -10..39        | Q0                   | error signal (input minus synthesized speech)    |
+| r_1 & r_h | 0..10          | normalized DP        | correlations of windowed speech (low and hi)     |
+| A_t       | 11x4           | Q12                  | LP filter coefficients in 4 subframes            |
+| Aq_t      | 11x4           | Q12                  | quantified LP filter coefficients in 4 subframes |
+| Ap1       | 0..10          | Q12                  | LP coefficients with spectral expansion          |
+| Ap2       | 0..10          | Q12                  | LP coefficients with spectral expansion          |
+| lsp_new   | 0..9           | Q15                  | LSP vector in 4th subframe                       |
+| lsp_new_q | 0..9           | Q15                  | quantified LSP vector in 4th subframe            |
+| lsp_mid   | 0..9           | Q15                  | LSP vector in 2nd subframe                       |
+| lsp_mid_q | 0..9           | Q15                  | quantified LSP vector in 2nd subframe            |
+| code      | 0..39          | Q12                  | fixed codebook excitation vector                 |
+| h1        | 0..39          | Q12                  | impulse response of weighted synthesis filter    |
+| xn        | 0..39          | Q0                   | target vector in pitch search                    |
+| xn2       | 0..39          | Q0                   | target vector in algebraic codebook search       |
+| dn        | 0..39          | scaled max<br>< 8192 | backward filtered target vector                  |
+| y1        | 0..39          | Q0                   | filtered adaptive codebook vector                |
+| y2        | 0..39          | Q12                  | filtered fixed codebook vector                   |
+| zero      | 0..39          |                      | zero vector                                      |
+| res2      | 0..39          |                      | long-term prediction residual                    |
+| gain_pit  | scalar         | Q12                  | adaptive codebook gain                           |
+| gain_code | scalar         | Q0                   | algebraic codebook gain                          |
+
+**Table 5: Codec fixed tables**
+
+| Parameter                     | Size    | Precision | Description                                              |
+|-------------------------------|---------|-----------|----------------------------------------------------------|
+| grid [ ]                      | 61      | Q15       | grid points at which Chebyshev polynomials are evaluated |
+| lag_h [ ] and lag_l [ ]       | 10      | DP        | higher and lower parts of the lag window table           |
+| window_160_80 [ ]             | 240     | Q15       | 1st LP analysis window                                   |
+| window_232_8 [ ]              | 240     | Q15       | 2nd LP analysis window                                   |
+| table [ ] in Lsf_lsp ( )      | 65      | Q15       | table to compute cos(x) in Lsf_lsp ( )                   |
+| slope [ ] in Lsp_lsf ( )      | 64      | Q12       | table to compute acos(x) in LSP_lsf ( )                  |
+| table [ ] in Inv_sqrt ( )     | 49      |           | table used in inverse square root computation            |
+| table [ ] in Log2 ( )         | 33      |           | table used in base 2 logarithm computation               |
+| table [ ] in Pow2 ( )         | 33      |           | table used in 2 to the power computation                 |
+| mean_lsf [ ]                  | 10      | Q15       | LSF means in normalized frequency [0.0, 0.5]             |
+| dico1_lsf [ ]                 | 128 x 4 | Q15       | 1st LSF quantizer in normalized frequency [0.0, 0.5]     |
+| dico2_lsf [ ]                 | 256 x 4 | Q15       | 2nd LSF quantizer in normalized frequency [0.0, 0.5]     |
+| dico3_lsf [ ]                 | 256 x 4 | Q15       | 3rd LSF quantizer in normalized frequency [0.0, 0.5]     |
+| dico4_lsf [ ]                 | 256 x 4 | Q15       | 4th LSF quantizer in normalized frequency [0.0, 0.5]     |
+| dico5_lsf [ ]                 | 64 x 4  | Q15       | 5th LSF quantizer in normalized frequency [0.0, 0.5]     |
+| qua_gain_pitch [ ]            | 16      | Q14       | quantization table of adaptive codebook gain             |
+| qua_gain_code [ ]             | 32      | Q11       | quantization table of fixed codebook gain                |
+| inter_6 [ ] in Interpol_6 ( ) | 25      | Q15       | interpolation filter coefficients in Interpol_6 ( )      |
+| inter_6 [ ] in Pred_lt_6 ( )  | 61      | Q15       | interpolation filter coefficients in Pred_lt_6 ( )       |
+| b [ ]                         | 3       | Q12       | HP filter coefficients (numerator) in Pre_Process ( )    |
+| a [ ]                         | 3       | Q12       | HP filter coefficients (denominator) in Pre_Process ( )  |
+| bitno [ ]                     | 57      | Q0        | number of bits corresponding to transmitted parameters   |
+
+**Table 6: Source Encoder output parameters in order of occurrence and bit allocation within the speech frame of 244 bits/20 ms**
+
+| Bits (MSB-LSB) | Description                              |
+|----------------|------------------------------------------|
+| s1 - s7        | index of 1st LSF submatrix               |
+| s8 - s15       | index of 2nd LSF submatrix               |
+| s16 - s23      | index of 3rd LSF submatrix               |
+| s24            | sign of 3rd LSF submatrix                |
+| s25 - s32      | index of 4th LSF submatrix               |
+| s33 - s38      | index of 5th LSF submatrix               |
+| subframe 1     |                                          |
+| s39 - s47      | adaptive codebook index                  |
+| s48 - s51      | adaptive codebook gain                   |
+| s52            | sign information for 1st and 6th pulses  |
+| s53 - s55      | position of 1st pulse                    |
+| s56            | sign information for 2nd and 7th pulses  |
+| s57 - s59      | position of 2nd pulse                    |
+| s60            | sign information for 3rd and 8th pulses  |
+| s61 - s63      | position of 3rd pulse                    |
+| s64            | sign information for 4th and 9th pulses  |
+| s65 - s67      | position of 4th pulse                    |
+| s68            | sign information for 5th and 10th pulses |
+| s69 - s71      | position of 5th pulse                    |
+| s72 - s74      | position of 6th pulse                    |
+| s75 - s77      | position of 7th pulse                    |
+| s78 - s80      | position of 8th pulse                    |
+| s81 - s83      | position of 9th pulse                    |
+| s84 - s86      | position of 10th pulse                   |
+| s87 - s91      | fixed codebook gain                      |
+| subframe 2     |                                          |
+| s92 - s97      | adaptive codebook index (relative)       |
+| s98 - s141     | same description as s48 - s91            |
+| subframe 3     |                                          |
+| s142 - s194    | same description as s39 - s91            |
+| subframe 4     |                                          |
+| s195 - s244    | same description as s92 - s141           |
+
+# 8 Homing sequences
+
+## 8.1 Functional description
+
+The enhanced full rate speech codec is described in a bit-exact arithmetic to allow for easy type approval as well as general testing purposes of the enhanced full rate speech codec.
+
+The response of the codec to a predefined input sequence can only be foreseen if the internal state variables of the codec are in a predefined state at the beginning of the experiment. Therefore, the codec has to be put in a so called home state before a bit-exact test can be performed. This is usually done by a reset (a procedure in which the internal state variables of the codec are set to their defined initial values).
+
+To allow a reset of the codec in remote locations, special homing frames have been defined for the encoder and the decoder, thus enabling a codec homing by inband signalling.
+
+The codec homing procedure is defined in such a way, that in either direction (encoder or decoder) the homing functions are called after processing the homing frame that is input. The output corresponding to the first homing frame is therefore dependent on the codec state when receiving that frame and hence usually not known. The response to any further homing frame in one direction is by definition a homing frame of the other direction. This procedure allows homing of both, the encoder and decoder from either side, if a loop back configuration is implemented, taking proper framing into account.
+
+## 8.2 Definitions
+
+**Encoder homing frame:** The encoder homing frame consists of 160 identical samples, each 13 bits long, with the least significant bit set to "one" and all other bits set to "zero". When written to 16-bit words with left justification, the samples have a value of 0008 hex. The speech decoder has to produce this frame as a response to the second and any further decoder homing frame if at least two decoder homing frames were input to the decoder consecutively.
+
+**Decoder homing frame:** The decoder homing frame has a fixed set of speech parameters as described in table 7. It is the natural response of the speech encoder to the second and any further encoder homing frame if at least two encoder homing frames were input to the encoder consecutively.
+
+**Table7: Parameter values for the decoder homing frame**
+
+| <b>Parameter</b> | <b>Value<br/>(LSB=b0)</b> |
+|------------------|---------------------------|
+| LPC 1            | 0x0004                    |
+| LPC 2            | 0x002F                    |
+| LPC 3            | 0x00B4                    |
+| LPC 4            | 0x0090                    |
+| LPC 5            | 0x003E                    |
+| LTP-LAG 1        | 0x0156                    |
+| LTP-LAG 2        | 0x0036                    |
+| LTP-LAG 3        | 0x0156                    |
+| LTP-LAG 4        | 0x0036                    |
+| LTP-GAIN 1       | 0x000B                    |
+| LTP-GAIN 2       | 0x0001                    |
+| LTP-GAIN 3       | 0x0000                    |
+| LTP-GAIN 4       | 0x000B                    |
+| FCB-GAIN 1       | 0x0003                    |
+| FCB-GAIN 2       | 0x0000                    |
+| FCB-GAIN 3       | 0x0000                    |
+| FCB-GAIN 4       | 0x0000                    |
+| PULSE 1_1        | 0x0000                    |
+| PULSE 1_2        | 0x0001                    |
+| PULSE 1_3        | 0x000F                    |
+| PULSE 1_4        | 0x0001                    |
+| PULSE 1_5        | 0x000D                    |
+| PULSE 1_6        | 0x0000                    |
+| PULSE 1_7        | 0x0003                    |
+| PULSE 1_8        | 0x0000                    |
+| PULSE 1_9        | 0x0003                    |
+| PULSE 1_10       | 0x0000                    |
+| PULSE 2_1        | 0x0008                    |
+| PULSE 2_2        | 0x0008                    |
+| PULSE 2_3        | 0x0005                    |
+| PULSE 2_4        | 0x0008                    |
+| PULSE 2_5        | 0x0001                    |
+| PULSE 2_6        | 0x0000                    |
+| PULSE 2_7        | 0x0000                    |
+| PULSE 2_8        | 0x0001                    |
+| PULSE 2_9        | 0x0001                    |
+| PULSE 2_10       | 0x0000                    |
+| PULSE 3_1        | 0x0000                    |
+| PULSE 3_2        | 0x0000                    |
+| PULSE 3_3        | 0x0000                    |
+| PULSE 3_4        | 0x0000                    |
+| PULSE 3_5        | 0x0000                    |
+| PULSE 3_6        | 0x0000                    |
+| PULSE 3_7        | 0x0000                    |
+| PULSE 3_8        | 0x0000                    |
+| PULSE 3_9        | 0x0000                    |
+| PULSE 3_10       | 0x0000                    |
+| PULSE 4_1        | 0x0000                    |
+| PULSE 4_2        | 0x0000                    |
+| PULSE 4_3        | 0x0000                    |
+| PULSE 4_4        | 0x0000                    |
+| PULSE 4_5        | 0x0000                    |
+| PULSE 4_6        | 0x0000                    |
+| PULSE 4_7        | 0x0000                    |
+| PULSE 4_8        | 0x0000                    |
+| PULSE 4_9        | 0x0000                    |
+| PULSE 4_10       | 0x0000                    |
+
+## 8.3 Encoder homing
+
+Whenever the enhanced full rate speech encoder receives at its input an encoder homing frame exactly aligned with its internal speech frame segmentation, the following events take place:
+
+- Step 1: The speech encoder performs its normal operation including VAD and DTX and produces a speech parameter frame at its output which is in general unknown. But if the speech encoder was in its home state at the beginning of that frame, then the resulting speech parameter frame is identical to the decoder homing frame (this is the way how the decoder homing frame was constructed).
+- Step 2: After successful termination of that operation the speech encoder provokes the homing functions for all sub-modules including VAD and DTX and sets all state variables into their home state. On the reception of the next input frame, the speech encoder will start from its home state.
+
+NOTE: Applying a sequence of N encoder homing frames will cause at least N-1 decoder homing frames at the output of the speech encoder.
+
+## 8.4 Decoder homing
+
+Whenever the speech decoder receives at its input a decoder homing frame, then the following events take place:
+
+- Step 1: The speech decoder performs its normal operation and produces a speech frame at its output which is in general unknown. But if the speech decoder was in its home state at the beginning of that frame, then the resulting speech frame is replaced by the encoder homing frame. This would not naturally be the case but is forced by this definition here.
+- Step 2: After successful termination of that operation the speech decoder provokes the homing functions for all sub-modules including the comfort noise generator and sets all state variables into their home state. On the reception of the next input frame, the speech decoder will start from its home state.
+
+NOTE 1: Applying a sequence of N decoder homing frames will cause at least N-1 encoder homing frames at the output of the speech decoder.
+
+NOTE 2: By definition (!) the first frame of each decoder test sequence must differ from the decoder homing frame at least in one bit position within the parameters for LPC and first subframe. Therefore, if the decoder is in its home state, it is sufficient to check only these parameters to detect a subsequent decoder homing frame. This definition is made to support a delay-optimized implementation in the TRAUP uplink direction.
+
+## 8.5 Encoder home state
+
+In table 8, a listing of all the encoder state variables with their predefined values when in the home state is given.
+
+**Table 8: Initial values of the encoder state variables**
+
+| File       | Variable                           | Initial value    |
+|------------|------------------------------------|------------------|
+| cod_12k2.c | old_speech[0:319]                  | All set to 0     |
+|            | old_exc[0:153]                     | All set to 0     |
+|            | old_wsp[0:142]                     | All set to 0     |
+|            | mem_syn[0:9]                       | All set to 0     |
+|            | mem_w[0:9]                         | All set to 0     |
+|            | mem_w0[0:9]                        | All set to 0     |
+|            | mem_err[0:9]                       | All set to 0     |
+|            | ai_zero[11:50]                     | All set to 0     |
+|            | hvec[0:39]                         | All set to 0     |
+|            | lsp_old[0], lsp_old_q[0]           | 30000            |
+|            | lsp_old[1], lsp_old_q[1]           | 26000            |
+|            | lsp_old[2], lsp_old_q[2]           | 21000            |
+|            | lsp_old[3], lsp_old_q[3]           | 15000            |
+|            | lsp_old[4], lsp_old_q[4]           | 8000             |
+|            | lsp_old[5], lsp_old_q[5]           | 0                |
+|            | lsp_old[6], lsp_old_q[6]           | -8000            |
+|            | lsp_old[7], lsp_old_q[7]           | -15000           |
+|            | lsp_old[8], lsp_old_q[8]           | -21000           |
+|            | lsp_old[9], lsp_old_q[9]           | -26000           |
+| levinson.c | old_A[0]                           | 4096             |
+|            | old_A[1:10]                        | All set to 0     |
+| pre_proc.c | y2_hi, y2_lo, y1_hi, y1_lo, x1, x0 | All set to 0     |
+| q_plsf_5.c | past_r2_q[0:9]                     | All set to 0     |
+| q_gains.c  | past_qua_en[0:3]                   | All set to -2381 |
+|            | pred[0]                            | 44               |
+|            | pred[1]                            | 37               |
+|            | pred[2]                            | 22               |
+|            | pred[3]                            | 12               |
+| dtx.c      | txdtx_hangover                     | 7                |
+|            | txdtx_N_elapsed                    | 0x7fff           |
+|            | txdtx_ctrl                         | 0x0003           |
+|            | old_CN_mem_tx[0:5]                 | All set to 0     |
+|            | lsf_old_tx[0:6][0]                 | 1384             |
+|            | lsf_old_tx[0:6][1]                 | 2077             |
+|            | lsf_old_tx[0:6][2]                 | 3420             |
+|            | lsf_old_tx[0:6][3]                 | 5108             |
+|            | lsf_old_tx[0:6][4]                 | 6742             |
+|            | lsf_old_tx[0:6][5]                 | 8122             |
+|            | lsf_old_tx[0:6][6]                 | 9863             |
+|            | lsf_old_tx[0:6][7]                 | 11092            |
+|            | lsf_old_tx[0:6][8]                 | 12714            |
+|            | lsf_old_tx[0:6][9]                 | 13701            |
+|            | gain_code_old_tx[0:27]             | All set to 0     |
+|            | L_pn_seed_tx                       | 0x70816958       |
+|            | buf_p_tx                           | 0                |
+
+Initial values for variables used by the VAD algorithm are listed in GSM 06.32 [4].
+
+## 8.6 Decoder home state
+
+In table 9, a listing of all the decoder state variables with their predefined values when in the home state is given.
+
+**Table 9: Initial values of the decoder state variables**
+
+| File       | Variable                                                    | Initial value    |
+|------------|-------------------------------------------------------------|------------------|
+| decoder.c  | synth_buf[0:9]                                              | All set to 0     |
+| dec_12k2.c | old_exc[0:153]                                              | All set to 0     |
+|            | mem_syn[0:9]                                                | All set to 0     |
+|            | lsp_old[0]                                                  | 30000            |
+|            | lsp_old[1]                                                  | 26000            |
+|            | lsp_old[2]                                                  | 21000            |
+|            | lsp_old[3]                                                  | 15000            |
+|            | lsp_old[4]                                                  | 8000             |
+|            | lsp_old[5]                                                  | 0                |
+|            | lsp_old[6]                                                  | -8000            |
+|            | lsp_old[7]                                                  | -15000           |
+|            | lsp_old[8]                                                  | -21000           |
+|            | lsp_old[9]                                                  | -26000           |
+| agc.c      | prev_bf                                                     | 0                |
+|            | state                                                       | 0                |
+| agc.c      | past_gain                                                   | 4096             |
+| d_plsf_5.c | past_r2_q[0:9]                                              | All set to 0     |
+|            | past_lsf_q[0], lsf_p_CN[0],<br>lsf_old_CN[0], lsf_new_CN[0] | 1384             |
+|            | past_lsf_q[1], lsf_p_CN[1],<br>lsf_old_CN[1], lsf_new_CN[1] | 2077             |
+|            | past_lsf_q[2], lsf_p_CN[2],<br>lsf_old_CN[2], lsf_new_CN[2] | 3420             |
+|            | past_lsf_q[3], lsf_p_CN[3],<br>lsf_old_CN[3], lsf_new_CN[3] | 5108             |
+|            | past_lsf_q[4], lsf_p_CN[4],<br>lsf_old_CN[4], lsf_new_CN[4] | 6742             |
+|            | past_lsf_q[5], lsf_p_CN[5],<br>lsf_old_CN[5], lsf_new_CN[5] | 8122             |
+|            | past_lsf_q[6], lsf_p_CN[6],<br>lsf_old_CN[6], lsf_new_CN[6] | 9863             |
+|            | past_lsf_q[7], lsf_p_CN[7],<br>lsf_old_CN[7], lsf_new_CN[7] | 11092            |
+|            | past_lsf_q[8], lsf_p_CN[8],<br>lsf_old_CN[8], lsf_new_CN[8] | 12714            |
+| d_gains.c  | past_lsf_q[9], lsf_p_CN[9],<br>lsf_old_CN[9], lsf_new_CN[9] | 13701            |
+|            | pbuf[0:4]                                                   | All set to 410   |
+|            | gbuf[0:4]                                                   | All set to 1     |
+|            | past_gain_pit                                               | 0                |
+|            | past_gain_code                                              | 0                |
+|            | prev_gp                                                     | 4096             |
+|            | prev_gc                                                     | 1                |
+|            | gcode0_CN                                                   | 0                |
+|            | gain_code_old_CN                                            | 0                |
+|            | gain_code_new_CN                                            | 0                |
+|            | gain_code_muting_CN                                         | 0                |
+|            | past_qua_en[0:3]                                            | All set to -2381 |
+|            | pred[0]                                                     | 44               |
+|            | pred[1]                                                     | 37               |
+|            | pred[2]                                                     | 22               |
+|            | pred[3]                                                     | 12               |
+
+(continued)
+
+**Table 9 (concluded): Initial values of the decoder state variables**
+
+| File       | Variable               | Initial value |
+|------------|------------------------|---------------|
+| dtx.c      | rxdtx_aver_period      | 7             |
+|            | rxdtx_N_elapsed        | 0x7fff        |
+|            | rxdtx_ctrl             | 0x0001        |
+|            | lsf_old_rx[0:6][0]     | 1384          |
+|            | lsf_old_rx[0:6][1]     | 2077          |
+|            | lsf_old_rx[0:6][2]     | 3420          |
+|            | lsf_old_rx[0:6][3]     | 5108          |
+|            | lsf_old_rx[0:6][4]     | 6742          |
+|            | lsf_old_rx[0:6][5]     | 8122          |
+|            | lsf_old_rx[0:6][6]     | 9863          |
+|            | lsf_old_rx[0:6][7]     | 11092         |
+|            | lsf_old_rx[0:6][8]     | 12714         |
+|            | lsf_old_rx[0:6][9]     | 13701         |
+|            | gain_code_old_rx[0:27] | All set to 0  |
+|            | L_pn_seed_rx           | 0x70816958    |
+|            | rx_dtx_state           | 23            |
+|            | prev_SID_frames_lost   | 0             |
+|            | buf_p_rx               | 0             |
+| dec_lag6.c | old_T0                 | 40            |
+| preemph.c  | mem_pre                | 0             |
+| pstfilt2.c | mem_syn_pst[0:9]       | All set to 0  |
+|            | res2[0:39]             | All set to 0  |
+
+![Simplified block diagram of the CELP synthesis model. It shows two codebooks (adaptive and fixed) feeding into a summer via gain blocks gp and gc. The output u(n) is processed by an LP synthesis filter 1/A(z) and then post-filtering to produce the final output s_hat(n). A feedback loop from the output of the LP synthesis filter goes back to the adaptive codebook.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg)
+
+The diagram illustrates the CELP synthesis model. It consists of the following components and signal flow:
+
+- adaptive codebook**: A block containing a waveform icon. It receives a feedback signal and outputs a signal  $v(n)$  which is then scaled by a gain  $g_p$ .
+- fixed codebook**: A block containing three impulse-like icons. It outputs a signal  $c(n)$  which is then scaled by a gain  $g_c$ .
+- Summer**: A circular node with a '+' sign that adds the scaled signals  $g_p v(n)$  and  $g_c c(n)$  to produce the excitation signal  $u(n)$ .
+- LP synthesis**: A block containing the transfer function  $\frac{1}{A(z)}$ . It takes the excitation signal  $u(n)$  as input and produces an intermediate signal  $\hat{s}(n)$ .
+- post-filtering**: A block that takes  $\hat{s}(n)$  as input and produces the final synthesized signal  $\hat{s}'(n)$ .
+- Feedback Loop**: A line that branches off from the output of the LP synthesis block and feeds back into the adaptive codebook.
+
+Simplified block diagram of the CELP synthesis model. It shows two codebooks (adaptive and fixed) feeding into a summer via gain blocks gp and gc. The output u(n) is processed by an LP synthesis filter 1/A(z) and then post-filtering to produce the final output s\_hat(n). A feedback loop from the output of the LP synthesis filter goes back to the adaptive codebook.
+
+Figure 2: Simplified block diagram of the CELP synthesis model
+
+![Simplified block diagram of the GSM enhanced full rate encoder. The diagram is divided into 'frame' and 'subframe' sections. The 'frame' section includes pre-processing, LPC analysis (twice per frame), and open-loop pitch search (twice per frame). The 'subframe' section includes adaptive codebook search, innovative codebook search, and filter memory update. The signal flow starts with s(n) entering pre-processing, then branches into LPC analysis and open-loop pitch search. LPC analysis involves windowing, Levinson-Durbin, and LSP quantization. Open-loop pitch search involves interpolation and weighted speech computation. Both paths lead into the subframe processing, which includes target computation, delay/gain finding, quantization, and excitation computation.](6e15fc9ea763541c5913d26f85072ae1_img.jpg)
+
+The diagram illustrates the signal processing flow of the GSM enhanced full rate encoder, organized into **frame** and **subframe** stages.
+
+**frame** stages:
+
+- Pre-processing**: Input  $s(n)$  is processed here.
+- LPC analysis (twice per frame)**:
+  - $s(n)$  is processed through **windowing and autocorrelation  $R[ ]$** , then **Levinson-Durbin  $R[ ] \rightarrow A(z)$** , and  **$A(z) \rightarrow LSP$** .
+  - LSP quantization** produces **LSP indices** and feeds into **interpolation for the 4 subframes  $LSP \rightarrow \hat{A}(z)$** .
+  - Another path from  $s(n)$  goes through **interpolation for the 4 subframes  $LSP \rightarrow A(z)$** .
+- Open-loop pitch search (twice per frame)**:
+  - $s(n)$  is processed through **compute weighted speech (4 subframes)** (using  $A(z)$  from interpolation) and **find open-loop pitch**.
+
+**subframe** stages:
+
+- Adaptive codebook search**:
+  - Inputs:  $x(n)$ ,  $\hat{A}(z)$ ,  $T_o$ , and  $h(n)$ .
+  - Blocks: **compute target for adaptive codebook**, **find best delay and gain**, **quantize LTP-gain** (outputting **LTP gain index**), and **compute adaptive codebook contribution**.
+- Innovative codebook search**:
+  - Inputs:  $x(n)$ ,  $x_2(n)$ , and  $h(n)$ .
+  - Blocks: **compute target for innovation**, **find best innovation** (outputting **code index**), and **compute excitation**.
+- Filter memory update**:
+  - Inputs: **compute excitation** and **fixed codebook gain quantization**.
+  - Block: **update filter memories for next subframe**.
+
+Additional processing blocks and signal paths:
+
+- compute impulse response**: Takes  $A(z)$  and  $\hat{A}(z)$  as input to produce  $h(n)$ .
+- fixed codebook gain quantization**: Receives input from **compute excitation** and outputs the **fixed codebook gain index**.
+
+Simplified block diagram of the GSM enhanced full rate encoder. The diagram is divided into 'frame' and 'subframe' sections. The 'frame' section includes pre-processing, LPC analysis (twice per frame), and open-loop pitch search (twice per frame). The 'subframe' section includes adaptive codebook search, innovative codebook search, and filter memory update. The signal flow starts with s(n) entering pre-processing, then branches into LPC analysis and open-loop pitch search. LPC analysis involves windowing, Levinson-Durbin, and LSP quantization. Open-loop pitch search involves interpolation and weighted speech computation. Both paths lead into the subframe processing, which includes target computation, delay/gain finding, quantization, and excitation computation.
+
+Figure 3: Simplified block diagram of the GSM enhanced full rate encoder
+
+![Simplified block diagram of the GSM enhanced full rate decoder. The diagram is divided into three sections: frame, subframe, and post-processing. In the frame section, LSP indices are input to a 'decode LSP' block, which outputs to an 'interpolation of LSP for the 4 subframes' block. This block outputs to an 'LSP -> A_hat(z)' block. In the subframe section, the 'pitch index' from 'decode LSP' goes to 'decode adaptive codebook'. The 'gains indices' from 'interpolation' go to 'decode gains'. The 'code index' from 'interpolation' goes to 'decode innovative codebook'. The outputs of 'decode adaptive codebook', 'decode gains', and 'decode innovative codebook' are combined in 'construct excitation'. The 'construct excitation' block outputs to a 'synthesis filter'. The 'synthesis filter' also receives input from the 'LSP -> A_hat(z)' block. The output of the 'synthesis filter' is s_hat(n). In the post-processing section, s_hat(n) is input to a 'post filter', which outputs s'_hat(n).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg)
+
+```
+
+graph LR
+    subgraph frame [frame]
+        LSP_indices[LSP indices] --> decode_LSP[decode LSP]
+        decode_LSP --> interpolation[interpolation of LSP for the 4 subframes]
+        interpolation --> LSP_A_hat["LSP → Â(z)"]
+    end
+
+    subgraph subframe [subframe]
+        pitch_index[pitch index] --> decode_adaptive[decode adaptive codebook]
+        gains_indices[gains indices] --> decode_gains[decode gains]
+        code_index[code index] --> decode_innovative[decode innovative codebook]
+        
+        decode_adaptive --> construct_excitation[construct excitation]
+        decode_gains --> construct_excitation
+        decode_innovative --> construct_excitation
+    end
+
+    subgraph post_processing [post-processing]
+        construct_excitation --> synthesis_filter[synthesis filter]
+        LSP_A_hat --> synthesis_filter
+        synthesis_filter --> s_hat["ŝ(n)"]
+        s_hat --> post_filter[post filter]
+        post_filter --> s_prime_hat["ŝ'(n)"]
+    end
+    
+```
+
+Simplified block diagram of the GSM enhanced full rate decoder. The diagram is divided into three sections: frame, subframe, and post-processing. In the frame section, LSP indices are input to a 'decode LSP' block, which outputs to an 'interpolation of LSP for the 4 subframes' block. This block outputs to an 'LSP -> A\_hat(z)' block. In the subframe section, the 'pitch index' from 'decode LSP' goes to 'decode adaptive codebook'. The 'gains indices' from 'interpolation' go to 'decode gains'. The 'code index' from 'interpolation' goes to 'decode innovative codebook'. The outputs of 'decode adaptive codebook', 'decode gains', and 'decode innovative codebook' are combined in 'construct excitation'. The 'construct excitation' block outputs to a 'synthesis filter'. The 'synthesis filter' also receives input from the 'LSP -> A\_hat(z)' block. The output of the 'synthesis filter' is s\_hat(n). In the post-processing section, s\_hat(n) is input to a 'post filter', which outputs s'\_hat(n).
+
+Figure 4: Simplified block diagram of the GSM enhanced full rate decoder
+
+# --- 9 Bibliography
+
+- 1) M.R. Schroeder and B.S. Atal, "Code-Excited Linear Prediction (CELP): High quality speech at very low bit rates," *Proc. ICASSP'85*, pp. 937-940, 1985.
+- 2) Y. Tohkura and F. Itakura, "Spectral smoothing technique in PARCOR speech analysis-synthesis," *IEEE Trans. on ASSP*, vol. 26, no. 6, pp. 587-596, Dec. 1978.
+- 3) L.R. Rabiner and R.W. Schaefer. *Digital processing of speech signals*. Prentice-Hall Int., 1978.
+- 4) F. Itakura, "Line spectral representation of linear predictive coefficients of speech signals," *J. Acoust. Soc. Amer*, vol. 57, Supplement no. 1, S35, 1975.
+- 5) F.K. Soong and B.H. Juang, "Line spectrum pair (LSP) and speech data compression", *Proc. ICASSP'84*, pp. 1.10.1-1.10.4, 1984.
+- 6) P. Kabal and R.P. Ramachandran, "The computation of line spectral frequencies using Chebyshev polynomials", *IEEE Trans. on ASSP*, vol. 34, no. 6, pp. 1419-1426, Dec. 1986.
+- 7) C. Laflamme, J-P. Adoul, R. Salami, S. Morissette, and P. Mabilleau, "16 kpbs wideband speech coding technique based on algebraic CELP" *Proc. ICASSP'91*, pp. 13-16.
+
+# Annex A (informative): Change history
+
+| SMG | SPEC  | CR   | PH | VER   | NEW_VE | SUBJECT                                 |
+|-----|-------|------|----|-------|--------|-----------------------------------------|
+| s23 | 06.60 | A003 | 2  | 4.0.0 | 4.0.1  | Vote 115 comments                       |
+| s25 | 06.60 | A005 | 2  | 4.0.1 | 4.1.0  | Corrections to GSM 06.60                |
+| s28 | 06.60 |      |    | 4.1.0 | 6.0.0  | Release 1997 version                    |
+| s28 | 06.60 | A007 |    | 6.0.0 | 7.0.0  | Addition of mu-Law (PCS 1900)           |
+|     | 06.60 |      |    | 7.0.1 | 7.0.2  | Update to Version 7.0.2 for Publication |
+| s31 | 06.60 |      |    | 7.0.2 | 8.0.0  | Release 1999 version                    |
+|     | 06.60 |      |    | 8.0.0 | 8.0.1  | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |  |  |        |        |
+|----------------|-------|----------|----|-----|------------------------|--|--|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        |  |  | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |  |  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  |  |  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  |  |  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  |  |  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  |  |  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  |  |  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 |  |  | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 |  |  | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 |  |  | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 |  |  | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |  |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|--|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                |  | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         |  | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         |  | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) |  | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46061/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-16/46_series/46061/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8958150e9d84d41aed3f012b39c5325cfdf02a4
--- /dev/null
+++ b/marked/Rel-16/46_series/46061/1c953f32bd34345dfd68fddf8a3736d6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a28cc885578d75d00c70a1c60905bf9e53bf9daca2b369a777987e2b2a869a4d
+size 60777
diff --git a/marked/Rel-16/46_series/46061/raw.md b/marked/Rel-16/46_series/46061/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..92cff06aa1c2ce1aedcc0cb02c5a46d6598e30d4
--- /dev/null
+++ b/marked/Rel-16/46_series/46061/raw.md
@@ -0,0 +1,279 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                              |    |
+|------------------------------------------------------------------------------|----|
+| Foreword .....                                                               | 4  |
+| 1 Scope.....                                                                 | 5  |
+| 2 References.....                                                            | 5  |
+| 3 Definitions and abbreviations .....                                        | 5  |
+| 3.1 Definitions.....                                                         | 5  |
+| 3.2 Abbreviations .....                                                      | 5  |
+| 4 General .....                                                              | 6  |
+| 5 Requirements .....                                                         | 6  |
+| 5.1 Error detection.....                                                     | 6  |
+| 5.2 Lost speech frames .....                                                 | 6  |
+| 5.3 First lost SID frame .....                                               | 6  |
+| 5.4 Subsequent lost SID frames .....                                         | 6  |
+| 6 Example solution.....                                                      | 6  |
+| 6.1 Example solution for substitution and muting of lost speech frames ..... | 7  |
+| 6.2 Example solution for substitution and muting of lost SID frames .....    | 9  |
+| Annex A (informative): Change history.....                                   | 10 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document defines a frame substitution and muting procedure which is used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS) within the digital cellular telecommunications system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS).
+
+The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the enhanced Full Rate speech traffic channel. It is not mandatory to follow the bit exact implementation outlined in the present document and the corresponding C-source code.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding".
+- [2] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [3] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+- [4] GSM 08.60: "Digital cellular telecommunications system (Phase 2+); Inband control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following term and definition applies:
+
+**5-point median operation:** consists of sorting the 5 elements belonging to the set for which the median operation is to be performed in an ascending order according to their values, and selecting the third largest value of the sorted set as the median value.
+
+Further definitions of terms used in the present document can be found in GSM 06.60 [2], GSM 06.81 [3], GSM 05.03 [1] and GSM 08.60 [4].
+
+## 3.2 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|          |                                                         |
+|----------|---------------------------------------------------------|
+| BFI      | Bad Frame Indication from Radio Sub System              |
+| BSI_Abis | Bad Sub-block Indication obtained from A-bis CRC checks |
+| CCU      | Channel Coding Unit                                     |
+| CRC      | Cyclic Redundancy Check                                 |
+| DTX      | Discontinuous transmission                              |
+| median5  | 5-point median operation                                |
+
+|         |                                        |
+|---------|----------------------------------------|
+| PrevBFI | Bad Frame Indication of Previous frame |
+| RSS     | Radio Sub System                       |
+| RX      | Receive                                |
+| SID     | Silence Descriptor frame               |
+| TRAU    | Transcoding Rate Adaptation Unit       |
+
+# --- 4 General
+
+The purpose of frame substitution is to conceal the effect of lost frames. The purpose of muting the output in the case of several lost frames is to indicate the breakdown of the channel to the user and to avoid generating possible annoying sounds as a result from frame substitution procedure.
+
+The RSS indicates lost speech or SID frames by setting its Bad Frame Indication flag (BFI) based on its 3-bit and 8-bit CRCs and possibly other error detection mechanisms. The TRAU calculates from the CRCs inserted by the CCU in the TRAU frames one BSI\_Abis flag for every sub-block of speech parameters. If either one or more of these flags is set, the speech decoder shall either perform frame substitution or subframe substitution.
+
+The example solution provided in clause 6 applies only for bad frame handling on a complete speech frame basis. However some parts could be modified for substitution of bad sub-blocks.
+
+# --- 5 Requirements
+
+## 5.1 Error detection
+
+An error is detected and the BFI-flag is set by the RSS according to the principle described in clause 4.
+
+## 5.2 Lost speech frames
+
+Normal decoding of lost speech frames would result in very unpleasant noise effects. In order to improve the subjective quality, lost speech frames shall be substituted with either a repetition or an extrapolation of the previous good speech frame(s). This substitution is done so that it will gradually decrease the output level, resulting in silencing of the output. Clause 6.1 gives an example solution.
+
+## 5.3 First lost SID frame
+
+A single lost SID frame shall be substituted by the last valid SID frame and the procedure for valid SID frames be applied as described in GSM 06.81 [3].
+
+## 5.4 Subsequent lost SID frames
+
+For the second lost SID frame, a muting technique shall be used on the comfort noise that will gradually decrease the output level (-3 dB/frame), resulting in silencing of the output of the decoder.
+
+For subsequent lost SID frames, the muting of the output shall be maintained. Clause 6.2 gives an example solution.
+
+# --- 6 Example solution
+
+The C-code of the following example is embedded in the bit exact software of the enhanced full rate codec.
+
+## 6.1 Example solution for substitution and muting of lost speech frames
+
+This example solution for substitution and muting is based on a state machine with seven states (figure 1).
+
+The system starts in state 0. Each time a bad frame is detected, the state counter is incremented by one and is saturated when it reaches 6. Each time a good speech frame is detected, the state counter is reset to zero, except when we are in state 6, where we set the state counter to 5. The state indicates the quality of the channel: the bigger the state counter,
+
+the worse the channel quality is. The control flow of the state machine can be described with the following C-code (**BFI** = bad frame indicator, **State** = state variable):
+
+```
+if(BFI != 0 )
+    State = State + 1;
+else if(State == 6)
+    State = 5;
+else
+    State = 0;
+if(State > 6 )
+    State = 6;
+```
+
+In addition to this state machine, the **Bad Frame Flag** from the previous frame is checked (**PrevBFI**). The processing depends on the value of the **State**-variable. In states 0 and 5, the processing depends also on the two flags **BFI** and **PrevBFI**.
+
+The procedure can be described as follows:
+
+![State machine diagram for controlling bad frame substitution. The diagram shows seven states (STATE 0 to STATE 6) in a vertical sequence. STATE 0 is the initial state with BFI=0 and PrevBFI=0 or 1. Transitions between states are triggered by BFI=1 (Bad frame). STATE 0 transitions to STATE 1. STATE 1 to STATE 2, STATE 2 to STATE 3, STATE 3 to STATE 4, and STATE 4 to STATE 5 are all triggered by BFI=1. STATE 5 transitions to STATE 6 if BFI=1. STATE 6 has a self-loop for BFI=1 and transitions back to STATE 5 if BFI=0 (Good frame). STATE 5 also has a self-loop for BFI=0. All states (STATE 1 to STATE 6) have a transition back to STATE 0 if BFI=0. STATE 0 has a self-loop for BFI=0.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg)
+
+```
+
+graph TD
+    S0["STATE = 0  
+BFI = 0  
+PrevBFI = 0 or 1"] --> S0
+    S0 -- "Bad frame (BFI=1)" --> S1["STATE = 1  
+BFI = 1  
+PrevBFI = 0"]
+    S1 -- "Bad frame (BFI=1)" --> S2["STATE = 2  
+BFI = 1  
+PrevBFI = 1"]
+    S2 -- "Bad frame (BFI=1)" --> S3["STATE = 3  
+BFI = 1  
+PrevBFI = 1"]
+    S3 -- "Bad frame (BFI=1)" --> S4["STATE = 4  
+BFI = 1  
+PrevBFI = 1"]
+    S4 -- "Bad frame (BFI=1)" --> S5["STATE = 5  
+BFI = 0 or 1  
+PrevBFI = 1"]
+    S5 -- "Bad frame (BFI=1)" --> S6["STATE = 6  
+BFI = 1  
+PrevBFI = 0 or 1"]
+    S6 -- "Bad frame (BFI=1)" --> S6
+    S6 -- "Good frame (BFI=0)" --> S5
+    S5 -- "Good frame (BFI=0)" --> S5
+    S1 -- "Good frame (BFI=0)" --> S0
+    S2 -- "Good frame (BFI=0)" --> S0
+    S3 -- "Good frame (BFI=0)" --> S0
+    S4 -- "Good frame (BFI=0)" --> S0
+    S5 -- "Good frame (BFI=0)" --> S0
+    S6 -- "Good frame (BFI=0)" --> S0
+  
+```
+
+Legend:  
+ → Bad frame (BFI=1)  
+ → Good frame (BFI=0)
+
+State machine diagram for controlling bad frame substitution. The diagram shows seven states (STATE 0 to STATE 6) in a vertical sequence. STATE 0 is the initial state with BFI=0 and PrevBFI=0 or 1. Transitions between states are triggered by BFI=1 (Bad frame). STATE 0 transitions to STATE 1. STATE 1 to STATE 2, STATE 2 to STATE 3, STATE 3 to STATE 4, and STATE 4 to STATE 5 are all triggered by BFI=1. STATE 5 transitions to STATE 6 if BFI=1. STATE 6 has a self-loop for BFI=1 and transitions back to STATE 5 if BFI=0 (Good frame). STATE 5 also has a self-loop for BFI=0. All states (STATE 1 to STATE 6) have a transition back to STATE 0 if BFI=0. STATE 0 has a self-loop for BFI=0.
+
+Figure 1: State machine for controlling the bad frame substitution
+
+### **BFI = 0, PrevBFI = 0, State = 0**
+
+No error is detected in the received or in the previous received speech frame. The received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved.
+
+### **BFI = 0, PrevBFI = 1, State = 0 or 5**
+
+No error is detected in the received speech frame but the previous received speech frame was bad. The LTP-gain and fixed codebook gain are limited below the values used for the last received good subframe:
+
+$$g^p = \begin{cases} g^p, & g^p \leq g^p(-1) \\ g^p(-1), & g^p > g^p(-1) \end{cases} \quad (1)$$
+
+where  $g^p$  = current decoded LTP-gain,  $g^p(-1)$  = LTP-gain used for the last good subframe (BFI = 0), and
+
+$$g^c = \begin{cases} g^c, & g^c \leq g^c(-1) \\ g^c(-1), & g^c > g^c(-1) \end{cases} \quad (2)$$
+
+where  $g^c$  = current decoded fixed codebook-gain and  $g^c(-1)$  = fixed codebook gain used for the last good subframe (BFI = 0).
+
+The rest of the received speech parameters are used normally in the speech synthesis. The current frame of speech parameters is saved.
+
+### **BFI = 1, PrevBFI = 0 or 1, State = 1...6**
+
+An error is detected in the received speech frame and the substitution and muting procedure is started. The LTP-gain and fixed codebook gain are replaced by attenuated values from the previous subframes:
+
+$$g^p = \begin{cases} P(\text{state})g^p(-1), & g^p(-1) \leq \text{median5}(g^p(-1), \dots, g^p(-5)) \\ P(\text{state})\text{median5}(g^p(-1), \dots, g^p(-5)), & g^p(-1) > \text{median5}(g^p(-1), \dots, g^p(-5)) \end{cases} \quad (3)$$
+
+where  $g^p$  = current decoded LTP-gain,  $g^p(-1), \dots, g^p(-n)$  = LTP-gains used for the last n subframes,  $\text{median5}()$  = 5-point median operation,  $P(\text{state})$  = attenuation factor ( $P(1) = 0.98, P(2) = 0.98, P(3) = 0.8, P(4) = 0.3, P(5) = 0.2, P(6) = 0.2$ ),  $\text{state}$  = state number, and
+
+$$g^c = \begin{cases} C(\text{state})g^c(-1), & g^c(-1) \leq \text{median5}(g^c(-1), \dots, g^c(-5)) \\ C(\text{state})\text{median5}(g^c(-1), \dots, g^c(-5)), & g^c(-1) > \text{median5}(g^c(-1), \dots, g^c(-5)) \end{cases} \quad (4)$$
+
+where  $g^c$  = current decoded fixed codebook gain,  $g^c(-1), \dots, g^c(-n)$  = fixed codebook gains used for the last n subframes,  $\text{median5}()$  = 5-point median operation,  $C(\text{state})$  = attenuation factor ( $C(1) = 0.98, C(2) = 0.98, C(3) = 0.98, C(4) = 0.98, C(5) = 0.98, C(6) = 0.7$ ), and  $\text{state}$  = state number.
+
+The higher the state value is, the more the gains are attenuated. Also the memory of the predictive fixed codebook gain is updated by using the average value of the past four values in the memory:
+
+$$\text{ener}(0) = \frac{1}{4} \sum_{i=1}^4 \text{ener}(-i) \quad (5)$$
+
+The past LSFs are used by shifting their values towards their mean:
+
+$$\text{lsf}_{q1}(i) = \text{lsf}_{q2}(i) = \alpha \text{past\_lsf}_q(i) + (1 - \alpha) \text{mean\_lsf}(i), i = 0 \dots 9 \quad (6)$$
+
+where  $\alpha = 0.95$ ,  $\text{lsf\_q1}$  and  $\text{lsf\_q2}$  are two sets of LSF-vectors for current frame,  $\text{past\_lsf\_q}$  is  $\text{lsf\_q2}$  from the previous frame, and  $\text{mean\_lsf}$  is the average LSF-vector.
+
+The LTP-lag values are replaced by the past value from the 4th subframe of the previous frame.
+
+The received fixed codebook excitation pulses from the erroneous frame are always used as such.
+
+## 6.2 Example solution for substitution and muting of lost SID frames
+
+The first lost SID frame is replaced by the last valid SID frame.
+
+For subsequent lost SID frames, the last valid SID frame is repeated, but the fixed codebook gain is decreased with a constant value of -3 dB in each frame down to the minimum value of 0. This value is maintained if additional lost SID frames occur.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                 |             |                                         |
+|----------------|-----------|---------|-----------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments                        |
+| SMG#22         |           |         |                 | 4.0.1       | ETSI Publication                        |
+| SMG#20         |           |         |                 | 5.1.2       | Release 1996 version                    |
+| SMG#27         |           |         |                 | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                 | 7.0.0       | Release 1998 version                    |
+|                |           |         |                 | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                 | 8.0.0       | Release 1999 version                    |
+|                |           |         |                 | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46062/raw.md b/marked/Rel-16/46_series/46062/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..10e5b061d382766767f7e88d985edad80cbb143d
--- /dev/null
+++ b/marked/Rel-16/46_series/46062/raw.md
@@ -0,0 +1,501 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                    |    |
+|------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                     | 4  |
+| 1 Scope.....                                                                       | 5  |
+| 2 References.....                                                                  | 5  |
+| 3 Definitions, symbols and abbreviations .....                                     | 5  |
+| 3.1 Definitions.....                                                               | 5  |
+| 3.2 Symbols.....                                                                   | 6  |
+| 3.3 Abbreviations .....                                                            | 6  |
+| 4 General.....                                                                     | 7  |
+| 5 Functions on the transmit (TX) side .....                                        | 7  |
+| 5.1 Background acoustic noise evaluation .....                                     | 8  |
+| 5.2 Modification of the speech encoding algorithm during SID frame generation..... | 11 |
+| 5.3 SID-frame encoding .....                                                       | 11 |
+| 6 Functions on the receive (RX) side.....                                          | 12 |
+| 6.1 Averaging and decoding of the LP and fixed codebook gain parameters.....       | 12 |
+| 6.2 Comfort noise generation and updating .....                                    | 14 |
+| 7 Computational details .....                                                      | 15 |
+| Annex A (informative): Change history.....                                         | 16 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document defines operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels within the digital cellular telecommunications system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels.
+
+The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the Enhanced Full Rate speech traffic channel.
+
+The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the Enhanced Full Rate speech traffic channel, the transmitter requirements only for those where downlink DTX will be used.
+
+In case of discrepancy between the requirements described in the present document and the fixed point computational description of these requirements contained in GSM 06.53 [2], the description in GSM 06.53 [2] will prevail.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [3] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [4] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frame for Enhanced Full Rate (EFR) speech traffic channels".
+- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**frame:** time interval of 20 ms corresponding to the time segmentation of the Enhanced Full Rate speech transcoder, also used as a short term traffic frame.
+
+**SID frame:** frame characterized by the SID (Silence Descriptor) codeword. It conveys information on the acoustic background noise.
+
+**SID codeword:** fixed bit pattern for labelling a traffic frame as a SID frame.
+
+**SID field:** bit positions of the SID codeword within a SID frame.
+
+**speech frame:** traffic frame that cannot be classified as a SID frame.
+
+**VAD flag:** Voice Activity Detection flag.
+
+**SP flag:** SPeech flag.
+
+Other definitions of terms used in the present document can be found in GSM 06.60 [3] and GSM 06.81 [5]. The overall operation of DTX is described in GSM 06.81 [5].
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply. Boldface symbols are used for vector variables.
+
+$\mathbf{f}^T = [f_1 \ f_2 \ \dots \ f_{10}]$  Unquantized LSF vector
+
+$\hat{\mathbf{f}}^T = [\hat{f}_1 \ \hat{f}_2 \ \dots \ \hat{f}_{10}]$  Quantized LSF vector
+
+$\mathbf{f}^{(m)}$   $m$ th unquantized LSF vector of the frame
+
+$\hat{\mathbf{f}}^{(m)}$   $m$ th quantized LSF vector of the frame
+
+$\mathbf{f}^{ref}$  Reference LSF parameter vector
+
+$\mathbf{f}^{mean}$  Averaged LSF parameter vector
+
+$g_c$  Unquantized fixed codebook gain
+
+$\hat{g}_c$  Quantized fixed codebook gain
+
+$\hat{g}_c^{ref}$  Reference fixed codebook gain
+
+$g_c^{mean}$  Averaged fixed codebook gain
+
+$e_{LP}$  Linear prediction residual signal
+
+$\mathbf{e}$  Computed LSF parameter prediction residual
+
+$\hat{\mathbf{e}}$  Quantized LSF parameter prediction residual
+
+$\gamma$  Computed fixed codebook gain correction factor
+
+$\hat{\gamma}$  Quantized fixed codebook gain correction factor
+
+$$\sum_{n=a}^b x(n) = x(a) + x(a+1) + \dots + x(b-1) + x(b)$$
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|     |                            |
+|-----|----------------------------|
+| BSS | Base Station Subsystem     |
+| DTX | Discontinuous Transmission |
+| LP  | Linear Prediction          |
+| LSF | Line Spectral Frequency    |
+| LSP | Line Spectral Pair         |
+| MS  | Mobile Station             |
+| RX  | Receive                    |
+
+|     |                         |
+|-----|-------------------------|
+| SID | Silence Descriptor      |
+| TX  | Transmit                |
+| VAD | Voice Activity Detector |
+
+For abbreviations not given in this clause, see GSM 01.04 [1].
+
+# 4 General
+
+A basic problem when using DTX is that the background acoustic noise, which is transmitted together with the speech, would disappear when the radio transmission is cut, resulting in discontinuities of the background noise. Since the DTX switching can take place rapidly, it has been found that this effect can be very annoying for the listener - especially in a car environment with high background noise levels. In bad cases, the speech may be hardly intelligible.
+
+The present document specifies the way to overcome this problem by generating on the receive (RX) side synthetic noise similar to the transmit (TX) side background noise. The comfort noise parameters are estimated on the TX side and transmitted to the RX side before the radio transmission is switched off and at a regular low rate afterwards. This allows the comfort noise to adapt to the changes of the noise on the TX side.
+
+# 5 Functions on the transmit (TX) side
+
+The comfort noise evaluation algorithm uses the following parameters of the GSM Enhanced Full Rate speech encoder, defined in GSM 06.60 [3]:
+
+- the unquantized and quantized Linear Prediction (LP) parameters, using the Line Spectral Pair (LSP) representation, where the unquantized Line Spectral Frequency (LSF) vector is given by  $\mathbf{f}^T = [f_1 \ f_2 \ \dots \ f_{10}]$ , the quantized LSF vector is given by  $\hat{\mathbf{f}}^T = [\hat{f}_1 \ \hat{f}_2 \ \dots \ \hat{f}_{10}]$ , and the two sets of unquantized and quantized LSF vectors (one for each half of a frame) are given by  $\mathbf{f}^{(1)}$ ,  $\mathbf{f}^{(2)}$ ,  $\hat{\mathbf{f}}^{(1)}$  and  $\hat{\mathbf{f}}^{(2)}$ , respectively;
+- the quantized fixed-codebook gain  $\hat{g}_c$ .
+
+The algorithm also computes the following parameters to assist in comfort noise generation:
+
+- the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  (average of the quantized LSF parameters of the hangover period);
+- the averaged LSF parameter vector  $\mathbf{f}^{mean}$  (average of the LSF parameters of the eight most recent frames);
+- the reference fixed codebook gain  $\hat{g}_c^{ref}$  (average of the quantized fixed codebook gain values of the hangover period);
+- the averaged fixed codebook gain  $g_c^{mean}$  (average of the fixed codebook gain values of the eight most recent frames);
+- the unquantized fixed codebook gain  $g_c$ .
+
+These parameters give information on the level ( $g_c$ ,  $\hat{g}_c$ ,  $\hat{g}_c^{ref}$ ,  $g_c^{mean}$ ) and the spectrum ( $\mathbf{f}^{(1)}$ ,  $\mathbf{f}^{(2)}$ ,  $\hat{\mathbf{f}}^{(1)}$ ,  $\hat{\mathbf{f}}^{(2)}$ ,  $\hat{\mathbf{f}}^{ref}$ ,  $\mathbf{f}^{mean}$ ) of the background noise.
+
+Two of the evaluated comfort noise parameters ( $\mathbf{f}^{mean}$  and  $g_c^{mean}$ ) are encoded into a special frame, called a Silence Descriptor (SID) frame, for transmission to the RX side. Since the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  and the reference fixed codebook gain  $\hat{g}_c^{ref}$  can be evaluated in the same way in the encoder and decoder, as given in clause 5.1, no transmission of these parameters is necessary.
+
+The averaged LSF parameter and fixed codebook gain values,  $\mathbf{f}^{mean}$  and  $g_c^{mean}$ , are computed in the encoder using both quantized and unquantized parameter values if the period of the eight most recent frames (the SID averaging period) is overlapping with the hangover period (the parameters from the frames overlapping with the hangover period have quantized values, while the parameters of the more recent frames of the SID averaging period have unquantized values). If the period of the eight most recent frames is non-overlapping with the hangover period, the averaged LSF parameter and fixed codebook gain values are computed using only unquantized parameter values.
+
+The SID frame also serves to initiate the comfort noise generation on the receive side, as a SID frame is always sent at the end of a speech burst, i.e., before the radio transmission is terminated.
+
+The scheduling of SID or speech frames on the radio path is described in GSM 06.81 [5].
+
+## 5.1 Background acoustic noise evaluation
+
+The comfort noise parameters to be encoded into a SID frame are calculated over  $N = 8$  consecutive frames marked with VAD = 0, as follows:
+
+The averaged LSF parameter vector  $\mathbf{f}^{mean}(i)$  of the frame  $i$  shall be computed according to the equation:
+
+$$\mathbf{f}^{mean}(i) = \frac{1}{8} \sum_{n=0}^7 \left( \frac{1}{2} \sum_{m=1}^2 \mathbf{f}^{(m)}(i-n) \right) \quad (1)$$
+
+where:
+
+$\mathbf{f}^{(m)}(i)$  is the  $m$ th (unquantized) LSF parameter vector of the current frame  $i$  ( $n = 0$ );
+
+$\mathbf{f}^{(m)}(i-n)$  is the  $m$ th (quantized or unquantized) LSF parameter vector of one of the last frames ( $n = 1, \dots, 7$ );
+
+$n$  is the averaging period index ( $n = 0, 1, \dots, 7$ );
+
+$m$  is the LSF parameter vector index within a frame (1 or 2);
+
+$i$  is the frame index.
+
+NOTE: When the averaging is performed at the end of the hangover period (first SID update), all of the LSF parameter vectors  $\mathbf{f}^{(m)}(i-n)$  of the 7 previous frames (the hangover period) have quantized values, while the LSF parameter vectors  $\mathbf{f}^{(m)}(i)$  of the current frame  $i$  have unquantized values. In the subsequent SID updates, the LSF parameter vectors of the SID averaging period in the frames overlapping with the hangover period have quantized values, while the parameter vectors of the more recent frames of the SID averaging period have unquantized values.
+
+The averaged LSF parameter vector  $\mathbf{f}^{mean}(i)$  of the frame  $i$  is encoded using the same encoding tables that are also used by the GSM Enhanced Full Rate speech codec for the encoding of the non-averaged LSF parameter vectors in ordinary speech encoding mode, but the quantization algorithm is modified in order to support the quantization of comfort noise. The LSF parameter prediction residual to be quantized is obtained according to the following equation:
+
+$$\mathbf{e}(i) = \mathbf{f}^{mean}(i) - \hat{\mathbf{f}}^{ref} \quad (2)$$
+
+where:
+
+$\mathbf{f}^{mean}(i)$  is the averaged LSF parameter vector at the current frame  $i$
+
+$\hat{\mathbf{f}}^{ref}$  is the reference LSF parameter vector
+
+$\mathbf{e}(i)$  is the computed LSF parameter prediction residual at the current frame  $i$
+
+$i$  is the frame index;
+
+NOTE: This prediction residual is used for both halves of the frame in the quantization algorithm. The computation of the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  is made on the basis of the quantized LSF parameters,  $\hat{\mathbf{f}}^{(1)}$  and  $\hat{\mathbf{f}}^{(2)}$ , by averaging the parameters over the hangover period of 7 frames, according to the following equation:
+
+$$\mathbf{f}^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{2} \sum_{m=1}^2 \mathbf{f}^{(m)}(k-n) \right) \quad (3)$$
+
+where:
+
+$\mathbf{f}^{(m)}(k-n)$  is the  $m$ th quantized LSF parameter vector of one of the frames of the hangover period ( $n = 1, \dots, 7$ );
+
+$n$  is the hangover period frame index ( $n = 1, \dots, 7$ );
+
+$m$  is the LSF parameter index within a frame (1 or 2);
+
+$k$  is the frame index.
+
+For each comfort noise insertion period, the computation of the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  is done only once at the end of the hangover period and for the rest of the comfort noise insertion period  $\hat{\mathbf{f}}^{ref}$  will be frozen. The reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  is evaluated in the decoder in the same way as in the encoder, because during the hangover period the same LSF parameter vectors  $\hat{\mathbf{f}}^{(m)}$  are available at the encoder and decoder. An exception to this are the cases when transmission errors are severe enough to cause the parameters to become unusable, and the frame substitution procedure is activated (see GSM 06.61 [4]). In these cases, the modified parameters obtained from the frame substitution procedure are used instead of the received parameters.
+
+The fixed codebook gain values shall be averaged and updated in every subframe according to the equation:
+
+$$g_c^{mean} = \frac{1}{29} \sum_{n=0}^{28} g_c(-n) \quad (4)$$
+
+where:
+
+$g_c(0)$  is the (unquantized) fixed codebook gain in the current subframe ( $n=0$ );
+
+$g_c(-n)$  is the (quantized or unquantized) fixed codebook gain in one of the past subframes ( $n = 1, \dots, 28$ );
+
+$n$  is the averaging period index ( $n = 0, 1, \dots, 28$ );
+
+NOTE: When the averaging is started at the end of the hangover period (first SID update), all of the fixed codebook gains  $g_c(-n)$  of the 28 ( $n=1, \dots, 28$ ) previous subframes (the hangover period) have quantized values, while the fixed codebook gains  $g_c(0)$  of the current subframe has an unquantized value. In the subsequent SID updates, the fixed codebook gain values of the SID averaging period in the subframes overlapping with the hangover period have quantized values, while the parameter vectors of the more recent subframes of the SID averaging period have unquantized values.
+
+Since most parts of the subframe processing clause in the encoder are switched off when the SP flag = "0" (to minimize the average complexity of the speech encoder algorithm), the unquantized fixed codebook gain is not directly available for gain averaging. Due to this, the unquantized fixed codebook gain is separately computed, based on the energy of the LP residual signal in each subframe, according to the following equation:
+
+$$g_c(j) = \sqrt{\frac{\sum_{l=1}^{40} (e_{LP}(j)(l))^2}{10}} \quad (5)$$
+
+where:
+
+$g_c(j)$  is the unquantized fixed codebook gain of the current subframe  $j$ ;
+
+$e_{LP}(j)(l)$  is the  $l$ th sample of the LP residual in the current subframe  $j$ ;
+
+$j$  is the subframe index ( $j = 1, \dots, 4$ );
+
+$l$  is the sample index ( $l = 1, \dots, 40$ ).
+
+NOTE: The computed energy of the LP residual signal is divided by the value of 10 to yield the energy for one excitation pulse, since during comfort noise generation, the subframe excitation signal (pseudo noise) has 10 non-zero samples, whose amplitudes can take values of +1 or -1.
+
+The averaged fixed codebook gain value  $g_c^{mean}$  of the current subframe is encoded using the non-averaged fixed codebook gain values in ordinary speech encoding mode, but the quantization algorithm is modified in order to support comfort noise quantization. The fixed codebook gain correction factor  $\gamma$  to be quantized is obtained according to the following equation:
+
+$$\gamma = g_c^{mean} / \hat{g}_c^{ref} \quad (6)$$
+
+where:
+
+$g_c^{mean}$  is the averaged fixed codebook gain value in the current subframe;
+
+$\hat{g}_c^{ref}$  is the reference fixed codebook gain;
+
+The computation of the reference fixed codebook gain  $\hat{g}_c^{ref}$  is made on the basis of the quantized fixed codebook gain parameters  $\hat{g}_c$ , by averaging the parameter values over the hangover period of 7 frames according to the following equation:
+
+$$\hat{g}_c^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{4} \sum_{j=1}^4 \hat{g}_c(k-n)(j) \right) \quad (7)$$
+
+where:
+
+$\hat{g}_c(k-n)(j)$  is the quantized fixed codebook gain parameter value in subframe  $j$  of one of the frames of the hangover period ( $n = 1, \dots, 7$ );
+
+$n$  is the hangover period frame index ( $n = 1, 2, \dots, 7$ );
+
+$k$  is the frame index;
+
+$j$  is the subframe index ( $j = 1, \dots, 4$ );
+
+For each comfort noise insertion period, the computation of the reference fixed codebook gain  $\hat{g}_c^{ref}$  is done only once at the end of the hangover period and for the rest of the comfort noise insertion period  $\hat{g}_c^{ref}$  will be frozen. The reference fixed codebook gain  $\hat{g}_c^{ref}$  can be evaluated in the decoder in the same way as in the encoder, because during the hangover period the same quantized fixed codebook gain values  $\hat{g}_c$  are available at the encoder and decoder. An exception to this are the cases when transmission errors are severe enough to cause the parameters to become unusable,
+
+and the frame substitution procedure is activated (see GSM 06.61 [4]). In these cases, the modified parameters obtained from the frame substitution procedure are used instead of the received parameters.
+
+The hangover period is defined in GSM 06.81 [5]. It is a period added at the end of a speech burst in which no voice activity is detected (VAD flag = "0"), but the speech encoder stays for the processing of 7 speech frames in speech encoding mode (SP flag = "1"). This hangover period and the first SID frame are used for averaging the comfort noise parameters contained in the first SID frame.
+
+## 5.2 Modification of the speech encoding algorithm during SID frame generation
+
+When the SP flag is equal to "0" the speech encoding algorithm is modified in the following way:
+
+- The non-averaged LP parameters which are used to derive the filter coefficients of the filters  $H(z)$  and  $W(z)$  of the speech encoder are not quantized.
+- The open loop pitch lag search is performed, but the closed loop pitch lag search is inactivated. The adaptive codebook gain is set to zero.
+- No fixed codebook search is made. In each subframe the pulse positions and signs of the fixed codebook excitation are locally generated using uniformly distributed pseudo random numbers. The excitation pulses take values of +1 and -1 when comfort noise is generated. The fixed codebook comfort noise excitation generation algorithm is defined in clause 6.2.
+- The memory of weighting filter  $W(z)$  is set to zero, i.e., the memory of  $W(z)$  is not updated.
+- The ordinary LP parameter quantization algorithm is inactive. At the end of the hangover period the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  is calculated as defined in clause 5.1. For the rest of the comfort noise insertion period  $\hat{\mathbf{f}}^{ref}$  is frozen. The averaged LSF parameter vector  $\mathbf{f}^{mean}$  is calculated each time a new SID frame is to be sent to the Radio Subsystem. This parameter vector is encoded into the SID frame as defined in clause 5.1.
+- The ordinary fixed codebook gain quantization algorithm is inactive. At the end of the hangover period the reference fixed codebook gain  $\hat{g}_c^{ref}$  is calculated as defined in clause 5.1. For the rest of the comfort noise insertion period  $\hat{g}_c^{ref}$  is frozen. The averaged fixed codebook gain value  $g_c^{mean}$  is calculated each time a new SID frame is to be sent to the Radio Subsystem. This gain value is encoded into the SID frame as defined in clause 5.1.
+- The predictor memories of the ordinary LP parameter quantization and fixed codebook gain quantization algorithms are reset when SP flag = "0", so that the quantizers start from their initial states when the speech activity begins again.
+- The computation of the unquantized fixed codebook gain is performed based on the energy of the LP residual signal.
+
+## 5.3 SID-frame encoding
+
+The SID-frame encoding algorithm exploits the fact that only some of the 244 bits in a frame are needed to code the comfort noise parameters. The other bits can then be used to mark the SID-frame by means of a fixed bit pattern, called the SID code word.
+
+The quantization indices of the LP parameters are replaced by the quantization indices derived from the averaged LSF parameter vector  $\mathbf{f}^{mean}$ . The encoding of the quantization indices is defined in clause 5.1.
+
+The fixed codebook gain quantization indices are replaced by the quantization index derived from the averaged fixed codebook gain value  $g_c^{mean}$ , encoded as defined in clause 5.1, repeated four times inside the frame.
+
+The SID code word consists of 95 bits which are all set to one. The bits of the SID code word are inserted in the SID field as defined in table 1. All of the bits in the SID field are in the error protection Class I.
+
+The remaining bits in the SID frame are set to zero. The use of these bits is for further study.
+
+**Table 1: SID codeword**
+
+| Parameter             | Number of bits | Bit positions<br>(b0 = LSB) |
+|-----------------------|----------------|-----------------------------|
+| LTP LAG 1             | 2              | b0, b1                      |
+| LTP LAG 2             | 3              | b0, b1, b2                  |
+| LTP LAG 3             | 2              | b0, b1                      |
+| LTP LAG 4             | 4              | b0, b1, b2, b3              |
+| LTP GAIN 1            | 3              | b0, b1, b2                  |
+| LTP GAIN 2            | 3              | b0, b1, b2                  |
+| LTP GAIN 3            | 4              | b0, b1, b2, b3              |
+| LTP GAIN 4            | 4              | b0, b1, b2, b3              |
+| PULSE 1 of 1st subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 2 of 1st subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 3 of 1st subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 4 of 1st subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 5 of 1st subfr. | 2              | b2,b3                       |
+| PULSE 1 of 2nd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 2 of 2nd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 3 of 2nd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 4 of 2nd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 5 of 2nd subfr. | 2              | b2,b3                       |
+| PULSE 1 of 3rd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 2 of 3rd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 3 of 3rd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 4 of 3rd subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 5 of 3rd subfr. | 2              | b2,b3                       |
+| PULSE 1 of 4th subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 2 of 4th subfr. | 2              | b2, b3                      |
+| PULSE 3 of 4th subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 4 of 4th subfr. | 4              | b0, b1, b2, b3              |
+| PULSE 5 of 4th subfr. | 2              | b2,b3                       |
+
+The parameters in table 1 are defined in GSM 06.60 [3].
+
+# 6 Functions on the receive (RX) side
+
+The situations in which comfort noise shall be generated on the receive side are defined in GSM 06.81 [5]. Generally speaking, the comfort noise generation is started or updated whenever a valid SID frame is received.
+
+## 6.1 Averaging and decoding of the LP and fixed codebook gain parameters
+
+When speech frames are received by the decoder the LP and the fixed codebook gain parameters of the last seven speech frames shall be kept in memory. The decoder counts the number of frames elapsed since the last SID frame was updated and passed to the RSS by the encoder. Based on this count, the decoder determines whether or not there is a hangover period at the end of the speech burst (if at least 31 frames have elapsed since the last SID update when the first SID frame after a speech burst arrives, the hangover period has existed at the end of the speech burst).
+
+As soon as a SID frame is received, and the hangover period is detected at the end of the speech burst, the stored LP and fixed codebook gain parameters shall be averaged to obtain the reference LSF parameter vector  $\hat{\mathbf{f}}^{ref}$  and the reference fixed gain codebook value  $g_c^{ref}$ . The reference LSF parameter vector and the reference fixed codebook gain value shall be frozen and used for the actual comfort noise insertion period.
+
+The averaging procedure for obtaining the reference parameters is as follows:
+
+- when a speech frame is received, the LSF and fixed codebook gain parameters are decoded and stored in memory;
+- when the first SID frame is received, and the hangover period is detected at the end of the speech burst, the stored LSF and fixed codebook gain parameters are averaged in the same way as in the speech encoder as follows (see also clause 5.1):
+
+$$\hat{f}^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{2} \sum_{m=1}^2 f^{(m)}(k-n) \right) \quad (8)$$
+
+where:
+
+$f^{(m)}(k-n)$  is the  $m$ th quantized LSF parameter vector of one of the frames of the hangover period ( $n = 1, \dots, 7$ );
+
+$n$  is the hangover period frame index ( $n = 1, 2, \dots, 7$ );
+
+$m$  is the LSF parameter index within a frame (1 or 2);
+
+$k$  is the frame index.
+
+and
+
+$$\hat{g}_c^{ref} = \frac{1}{7} \sum_{n=1}^7 \left( \frac{1}{4} \sum_{j=1}^4 \hat{g}_c(k-n)(j) \right) \quad (9)$$
+
+where:
+
+$\hat{g}_c(k-n)(j)$  is the quantized fixed codebook gain parameter value in subframe  $j$  of one of the frames of the hangover period ( $n = 1, \dots, 7$ );
+
+$n$  is the hangover period frame index ( $n = 1, \dots, 7$ );
+
+$k$  is the frame index;
+
+$j$  is the subframe index ( $j = 1, \dots, 4$ ).
+
+Once the reference LSF parameter vector has been computed, the averaged LSF parameter vector  $\hat{f}^{mean}(i)$  of the frame  $i$  (encoded into the SID frame) can be reproduced at the decoder each time a SID update frame is received, according to the equation:
+
+$$\hat{f}^{mean}(i) = \hat{e}(i) + \hat{f}^{ref} \quad (10)$$
+
+where:
+
+$\hat{f}^{mean}(i)$  is the quantized, averaged LSF parameter vector at the current frame  $i$  to be used for comfort noise generation;
+
+$\hat{f}^{ref}$  is the reference LSF parameter vector;
+
+$\hat{e}(i)$  is the received quantized LSF parameter prediction residual at the current frame  $i$ ;
+
+$i$  is the frame index.
+
+The averaged fixed codebook gain  $\hat{g}_c^{mean}(i)$  of the frame  $i$  (encoded into the SID frame) can be similarly reproduced at the decoder each time a SID update frame is received, according to the following equation:
+
+$$\hat{g}_c^{mean}(i) = \hat{g}_c^{ref} \cdot \hat{\gamma}(i) \quad (11)$$
+
+where:
+
+$\hat{g}_c^{mean}(i)$  is the averaged fixed codebook gain value in the current frame  $i$  to be used for comfort noise generation;
+
+$\hat{g}_c^{ref}$  is the reference fixed codebook gain;
+
+$\hat{\gamma}(i)$  is the received quantized fixed codebook gain correction factor in the current frame  $i$ ;
+
+$i$  is the frame index.
+
+## 6.2 Comfort noise generation and updating
+
+The comfort noise generation procedure uses the GSM Enhanced Full Rate speech decoder algorithm defined in GSM 06.60 [3].
+
+When comfort noise is to be generated, the various encoded parameters are set as follows:
+
+In each subframe, the pulse positions and signs of the fixed codebook excitation are locally generated using uniformly distributed pseudo random numbers. The excitation pulses take values of +1 and -1 when comfort noise is generated. The fixed codebook comfort noise excitation generation algorithm works as follows:
+
+```
+for (i = 0; i < 40; i++) code[i] = 0;
+for (i = 0; i < 10; i++) {
+    j = random(4);
+    idx = j * 10 + i;
+    if (random(2) == 1) code[idx] = 1;
+    else                code[idx] = -1;
+}
+```
+
+where:
+
+**code[0..39]** fixed codebook excitation buffer;
+
+**random(4)** generates a random integer value, uniformly distributed between 0 and 3;
+
+**random(2)** generates a random integer value, uniformly distributed between 0 and 1.
+
+The fixed codebook gain values are those received in the SID frame.
+
+The adaptive codebook gain values in each subframe are set to 0.
+
+The pitch delay values in each subframe are set to 40.
+
+The LP filter parameters used are those received in the SID frame.
+
+The predictor memories of the ordinary LP parameter and fixed codebook gain quantization algorithms are reset when SP flag = "0", so that the quantizers start from their initial states when the speech activity begins again.
+
+With these parameters, the speech decoder now performs the standard operations described in GSM 06.60 [3] and synthesizes comfort noise.
+
+Updating of the comfort noise parameters (fixed codebook gain and LP filter parameters) occurs each time a valid SID frame is received, as described in GSM 06.81 [5].
+
+When updating the comfort noise, the parameters above should preferably be interpolated over the SID update period to obtain smooth transitions.
+
+# --- 7 Computational details
+
+A low level description has been prepared in form of an ANSI C source code which is part of GSM 06.53 [2].
+
+# Annex A (informative): Change history
+
+| Change history |           |         |                 |             |                                         |
+|----------------|-----------|---------|-----------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments                        |
+| SMG#22         |           |         |                 | 4.0.1       | ETSI Publication                        |
+| SMG#20         |           |         |                 | 5.1.2       | Release 1996 version                    |
+| SMG#27         |           |         |                 | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                 | 7.0.0       | Release 1998 version                    |
+|                |           |         |                 | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                 | 8.0.0       | Release 1999 version                    |
+|                |           |         |                 | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                        |        |        |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46076/17008b9a61bfe35b1e2c8fe2fbd1d801_img.jpg b/marked/Rel-16/46_series/46076/17008b9a61bfe35b1e2c8fe2fbd1d801_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..842e27a64b54ba42f91d6936adcb870048921284
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/17008b9a61bfe35b1e2c8fe2fbd1d801_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c015fe426afba2d81d2b67bb01f39151ef13f4ea4111ed8654eed21f951462e2
+size 85343
diff --git a/marked/Rel-16/46_series/46076/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/46_series/46076/171115f072e42b379238ed0dd438e9d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c6df71feb45b5b08e77954e8e701e6d786639e1d
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/171115f072e42b379238ed0dd438e9d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d58e93c71075c6bcaf4148fe4483fea54b79d6621c8da54e34dfd0383a64633d
+size 24185
diff --git a/marked/Rel-16/46_series/46076/1c427123350e0e73e2a109b79069314b_img.jpg b/marked/Rel-16/46_series/46076/1c427123350e0e73e2a109b79069314b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..54a0cccda494f8e8d153e0c1a1f0d4f0ec230c83
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/1c427123350e0e73e2a109b79069314b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2c657399de8178e326b4a7a1f51721cc13b66b2dc12629f1cf83203d4b3e2f2d
+size 75871
diff --git a/marked/Rel-16/46_series/46076/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/46_series/46076/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e7aebc55e3b312f12a84903fd67f0204f1be94b3
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/329c96049bb432e9c2cbda4e224a0c9c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:254f42f68f520f4acb9f26f194a0342aa7584dd12b6c58701afb26a22bdd9517
+size 133902
diff --git a/marked/Rel-16/46_series/46076/72d357d406618f3f884c3876fc3058ee_img.jpg b/marked/Rel-16/46_series/46076/72d357d406618f3f884c3876fc3058ee_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53ec278997646e4f1d0d1c91dd92a72a3f8d1474
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/72d357d406618f3f884c3876fc3058ee_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1db736a569c12a01b6e01470650e04eb21e1631f46ef605d377051d664809300
+size 27074
diff --git a/marked/Rel-16/46_series/46076/79d61011f426d34fb542d86176482d2c_img.jpg b/marked/Rel-16/46_series/46076/79d61011f426d34fb542d86176482d2c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..caa637dbdf622134315c900b8d4d242cde9cf11c
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/79d61011f426d34fb542d86176482d2c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd856870b0226f965353d22f2ef663ab00a0241c6918fc40a84607d7e27c411f
+size 22271
diff --git a/marked/Rel-16/46_series/46076/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg b/marked/Rel-16/46_series/46076/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d530a81960ac17013e5eeaf4711b7669e3924d23
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/9260ae281f6b6470331f4a0f82dbc2b1_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9db38541660d90f44d1fb2140314b3fbbbe7a38136f7441394a954f8c51fa98c
+size 104641
diff --git a/marked/Rel-16/46_series/46076/bd4617f25d15430eb78c2d6d75a99dde_img.jpg b/marked/Rel-16/46_series/46076/bd4617f25d15430eb78c2d6d75a99dde_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..05bbe35dd37c4bfc0697f5a2eeb95478dc8b56fc
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/bd4617f25d15430eb78c2d6d75a99dde_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d51765c569cb25e6353386dc574612a721fb9e405a962689eb859316107843c4
+size 57035
diff --git a/marked/Rel-16/46_series/46076/raw.md b/marked/Rel-16/46_series/46076/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..91262157b02deaee84c0144016468983a108d9c8
--- /dev/null
+++ b/marked/Rel-16/46_series/46076/raw.md
@@ -0,0 +1,1312 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                       |    |
+|-----------------------------------------------------------------------|----|
+| Foreword .....                                                        | 5  |
+| Executive summary and recommendations .....                           | 6  |
+| Introduction .....                                                    | 6  |
+| Benefits 6                                                            |    |
+| Performance .....                                                     | 6  |
+| Risk areas 7                                                          |    |
+| Codec development and selection .....                                 | 7  |
+| Recommendations .....                                                 | 8  |
+| 0 Scope.....                                                          | 9  |
+| 1 Goals of AMR codec.....                                             | 9  |
+| 2 Terminology.....                                                    | 9  |
+| 3 Overview of the AMR system and its applications.....                | 9  |
+| 3.1 Basic operation.....                                              | 9  |
+| 3.2 Application scenarios .....                                       | 10 |
+| 4 Development Time-scales.....                                        | 10 |
+| 5 Baseline description and working assumptions .....                  | 11 |
+| 5.1 Generic operation .....                                           | 11 |
+| 5.2 Constraints.....                                                  | 11 |
+| 5.3 Speech and channel codecs .....                                   | 12 |
+| 5.4 Rate adaptation.....                                              | 13 |
+| 5.4.1 Channel mode adaptation .....                                   | 13 |
+| 5.4.2 Codec mode adaptation .....                                     | 13 |
+| 5.5 Support of TFO .....                                              | 13 |
+| 5.6 Support of DTX.....                                               | 14 |
+| 5.7 Support of 8 and 16 kbit/s A-ter sub-multiplexing .....           | 14 |
+| 5.8 Active noise suppression.....                                     | 14 |
+| 6 Feasibility issues .....                                            | 14 |
+| 6.1 Codec performance .....                                           | 14 |
+| 6.1.1 Basic, error and background noise performance .....             | 15 |
+| 6.1.2 Tandeming.....                                                  | 16 |
+| 6.1.3 Seamless codec mode bit-rate changes.....                       | 16 |
+| 6.1.4 Complexity .....                                                | 16 |
+| 6.2 Quality and Capacity benefits of AMR.....                         | 17 |
+| 6.2.1 General AMR performance .....                                   | 17 |
+| 6.2.2 Improved coverage from the improved robustness in FR mode ..... | 17 |
+| 6.2.3 Capacity benefits from the improved robustness in FR mode ..... | 18 |
+| 6.2.4 Quality/capacity trade-offs by use of the HR mode .....         | 18 |
+| 6.2.5 System aspects of capacity/quality .....                        | 20 |
+| 6.2.6 MS penetration .....                                            | 21 |
+| 6.3 Codec adaptation.....                                             | 21 |
+| 6.3.1 Codec mode .....                                                | 21 |
+| 6.3.2 Channel mode.....                                               | 22 |
+| 6.3.3 Channel metrics (accuracy, update rate).....                    | 22 |
+| 6.3.4 Channel dynamics, effects on performance.....                   | 22 |
+| 6.3.5 Location of codec mode and channel mode control .....           | 23 |
+| 6.3.6 Radio resource allocation .....                                 | 23 |
+| 6.4 Support of other features .....                                   | 24 |
+| 6.4.1 TFO.....                                                        | 24 |
+| 6.4.2 DTX.....                                                        | 24 |
+| 6.4.3 Power control.....                                              | 24 |
+| 6.4.4 Handover .....                                                  | 25 |
+| 6.4.5 8 and 16 kbit/s A-ter sub-multiplexing.....                     | 25 |
+| 6.5 Wideband service option.....                                      | 25 |
+
+|                 |                                               |           |
+|-----------------|-----------------------------------------------|-----------|
+| 7               | Requirements specification.....               | 26        |
+| 8               | Implementation factors .....                  | 26        |
+| 9               | Codec development and selection.....          | 26        |
+| 9.1             | Test and selection methodologies .....        | 26        |
+| 9.2             | Asymmetry of up and down links .....          | 27        |
+| 9.3             | Speech traffic channel simulation model ..... | 27        |
+| 9.4             | Schedule .....                                | 28        |
+| 9.5             | Programme management.....                     | 29        |
+| 10              | Open issues and risks .....                   | 29        |
+| 11              | Recommendations .....                         | 30        |
+| <b>Annex A:</b> | <b>Terminology .....</b>                      | <b>31</b> |
+| <b>Annex B:</b> | <b>Application scenarios .....</b>            | <b>34</b> |
+| <b>Annex C:</b> | <b>Codec requirement specification.....</b>   | <b>35</b> |
+| C.1             | Static conditions .....                       | 35        |
+| C.2             | Dynamic conditions .....                      | 37        |
+| <b>Annex D:</b> | <b>AMR implementation requirements.....</b>   | <b>38</b> |
+| D.1             | Network.....                                  | 38        |
+| D.2             | MS.....                                       | 40        |
+| <b>Annex E:</b> | <b>Speech traffic channel simulator.....</b>  | <b>42</b> |
+| <b>Annex F:</b> | <b>Schedule for AMR development .....</b>     | <b>44</b> |
+| <b>Annex G:</b> | <b>Work Item Description for AMR.....</b>     | <b>46</b> |
+| <b>Annex H:</b> | <b>Change history .....</b>                   | <b>48</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present technical report contains the GSM Adaptive Multi-Rate (AMR) speech codec Study Phase Report.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- Executive summary and recommendations
+
+## Introduction
+
+As tasked by SMG in October 1996, SMG11 and SMG2 have conducted a study into the feasibility of the AMR codec concept. The study not only addressed technical feasibility but also the benefits of AMR in realistic applications, the development plan, time-scales and the resources needed to take the AMR codec and associated network support to completion of the standards.
+
+## Benefits
+
+Unlike previous GSM speech codecs which operate at a fixed rate with a fixed level of error protection, the AMR system adapts to local radio channel and traffic conditions and selects the optimum channel (half- or full- rate) and codec mode (speech and channel bit rates) to deliver the best combination of speech quality and capacity. This flexibility provides a number of important benefits:
+
+- improved speech quality in both half-rate and full-rate modes by means of codec mode adaptation i.e. varying the balance between speech and channel coding for the same gross bit-rate;
+- ability to trade speech quality and capacity smoothly and flexibly by a combination of channel and codec mode adaptation; this can be controlled by the network operator on a cell by cell basis;
+- improved robustness to channel errors under marginal radio signal conditions in full-rate mode. This increased robustness to errors and hence to interference may instead be used to increase capacity by operating a tighter frequency re-use pattern;
+- ability to tailor AMR operation to meet the many different needs of operators;
+- potential for improved handover and power control resulting from additional signaling transmitted rapidly in-band.
+
+To investigate the feasibility of realizing these benefits, a wide-ranging study has been carried out. This has considered not only speech and channel codec performance, but perhaps more critically, channel and codec mode adaptation, the associated signaling and the operation of AMR in realistic radio environments. The one-year timeframe allowed for the Study Phase has prevented a thorough assessment of all aspects. However, it has been possible to assess expected performance (quality and capacity) and to identify and assess the risks of the critical areas from a feasibility perspective.
+
+## Performance
+
+The performance benefits have been estimated for some of the main applications of AMR, assuming certain system assumptions such as frequency hopping and making a number of simplifications:
+
+- in full-rate mode only, the robustness to high error levels is substantially increased such that the quality level of EFR at a C/I of 10dB is extended down to a C/I of 4 dB, measured at the input to the channel equalizer. This will give coverage in-fill advantages in areas of marginal radio coverage. This equates to an improvement of sensitivity of between 4 dB and 6 dB depending on the robustness of the signaling channels;
+- quality and capacity can be traded against each other in a controlled manner. Using as a reference an EFR/HR combination with a conventional resource allocation, for the same capacity improvement, AMR will give an *average quality improvement* corresponding to about 70 % of the difference between FR and EFR. This improvement is relatively insensitive to C/I.
+
+It has also been estimated that for a capacity improvement of about 30 % (relative to FR only), 80 % of calls would have G.728 quality of better, i.e. "wireline" quality. This tradeoff between % capacity improvement and % of mobiles having wireline quality is sensitive to the local C/I distributions. These have proved to be difficult to estimate reliably. Other individual estimates have shown more optimistic results and the figures quoted probably represent the lower end of the range.
+
+- In half-rate mode only which gives the maximum capacity advantage (in excess of 100 % as for normal half-rate), quality improvements are also given (deriving from codec mode adaptation) especially in background noise conditions and at low errors. Under these conditions, the quality level will be at least as good as that of FR.
+
+- The increased resilience channel errors in full-rate mode may allow a tighter frequency re-use giving capacity improvements estimated at up to 30 %, but at the expense of lower speech quality. However, it is unclear at present how terminals without AMR e.g. with FR or EFR codecs or data terminals should be handled, as they do not have the improved resilience to errors and the speech quality would be degraded. This application requires further study.
+
+## Risk areas
+
+The main performance limitations and technical risk areas have been identified as follows:
+
+- codec performance: to achieve the wireline quality benchmark of G.728 in HR mode, the C/I threshold had to be increased from 10 dB to about 18 dB. This will allow the speech quality target still to be achieved but at the expense of lower capacity gain. This is already reflected in the performance results above.
+- background noise: the original performance objective in HR mode was G.728 is better than EFR. This is too demanding and was relaxed to "the better of GSM-FR or G.729" quality for each type of background noise (vehicle, street, office). This still represents a substantial improvement over the existing HR codec.
+- the difficulties of measuring C/I distributions representative of high capacity networks using other capacity enhancing techniques (e.g. power control, frequency hopping) has made it difficult to make accurate estimates of capacity and quality. Pessimistic forecasts have therefore been made to illustrate the lower limit. **Risk: medium.**
+- channel and codec mode adaptation algorithms. These are crucial to the success of AMR operation and improvements to initial implementations will be possible to optimize performance for real network operating conditions. **Risk: medium.**
+- channel quality metric. It is important that the estimate of the channel quality is sufficiently accurate to ensure that the optimum codec mode is selected. While some solutions have been considered, the feasibility of providing such an accurate metric remains a risk.
+
+**Risk assessment by SMG2, high; by SMG11, medium.**
+
+- TFO. Although some potential candidate TFO solutions for AMR have been identified, effective solutions will require significant development. **Risk to TFO: medium.**
+- AMR system complexity. The AMR system is relatively complex and introduces new techniques. **Risk level: medium.**
+
+At the conclusion of the Study Phase, there remain open design issues. However, working assumptions have been reached for most critical areas and other open issues can be resolved in due course without prejudice.
+
+## Codec development and selection
+
+It is recommended that the optimum AMR solution be selected from a number of candidate proposals. To promote integrated solutions with the greatest flexibility for innovative techniques, designers should submit complete solutions including not only the speech and channel codecs, but also the control and signaling system, subject to agreed constraints and working assumptions.
+
+To test the codecs, in addition to traditional static testing for each mode of the codec, dynamic tests will be essential to evaluate performance under dynamically varying radio conditions. New test methodologies for dynamic testing will be needed, as well as new error patterns. These are in the process of being developed.
+
+In response to the requirements declared by the MOU to SMG#20, the possibility of running with a schedule which would deliver the codec and signaling specifications in time for Release 1998 has been examined. However, so far a schedule has not been agreed by SMG11 and SMG2, which would meet Release 1998 deadlines. The feasibility of achieving Release 1998 is therefore unclear although it is evident that such a schedule would have to be very aggressive and high risk. Further urgent discussions are needed by the two committees to reach a conclusion.
+
+For the formal codec testing, independent host and test laboratories will be needed. They will require funding estimated at 400 k ECU.
+
+# Recommendations
+
+On basis of the performance benefits and risks highlighted above, the following recommendations are submitted to SMG for approval:
+
+- initiate a program to develop, test, select and specify AMR speech and channel codecs together with related features such as VAD, DTX and comfort noise generation. The associated control, signaling procedures and TFO should also be developed and specified;
+- SMG11 and SMG2 should agree an acceptable and workable time-plan as soon as possible after SMG#23 with the priority of meeting Release 1998 deadlines;
+- approve the performance requirement specification in annex C;
+- SMG to secure funding of 400 kECU for the purposes of codec testing;
+- approve Work Item Description (see annex G);
+- decide whether to include wideband option on AMR (see separate Liaison Statement).
+
+# --- 0 Scope
+
+The present document presents the outcome of the Study Phase initiated at SMG#20 on the concept of the Adaptive Multi-Rate (AMR) codec. The AMR concept represents a new approach to achieving consistent high quality speech combined with efficient spectrum usage. It was recognized at SMG#20 that this would require novel techniques whose feasibility should first be assessed before proceeding with a full development of the AMR system and its control.
+
+Clauses 1 to 4 provide an overview and background to the AMR concept. Clause 5 provides a basic description of the AMR system functionality including working assumptions that have been agreed during the Study Phase. Feasibility aspects are considered in clause 6. The requirement specification, which will form the basis for the development phase, is contained in clause 7. Clause 8 gives an indication of the MS and network upgrades needed to support AMR. Clause 9 outlines how the AMR codec will be developed, tested and selected including the proposed time-plan. Clauses 10 and 11 conclude with a summary of the risks and recommendations.
+
+# --- 1 Goals of AMR codec
+
+The principal goals of the AMR codec as presented to SMG#20 (October 1996) (see SQSG report, Tdoc SMG 447/96) are to provide:
+
+- wireline quality combined with capacity advantages offered by half-rate operation;
+- increased robustness to high channel error rates when operating at full-rate.
+
+This is to be achieved by controlling the channel and codec modes according to the radio channel conditions and traffic loading.
+
+To address the needs of certain GSM markets, especially in the US, and to ensure the earliest provision and penetration of AMR handsets, it was also decided at SMG#20 to set an aggressive time-scale for the development and standardization of the AMR. This requires that the AMR specifications be ready for GSM Release 1998, i.e. end of 1998.
+
+# --- 2 Terminology
+
+The terminology and acronyms used in this report are given in annex A.
+
+# --- 3 Overview of the AMR system and its applications
+
+## 3.1 Basic operation
+
+Most speech codecs including the existing GSM codecs (FR, HR and EFR) operate at a fixed coding rate. Channel protection (against errors) is added also at a fixed rate. The coding rates are chosen as a compromise between best clear channel performance and robustness to channel errors. The AMR system exploits the implied performance compromises by adapting the speech and channel coding rates according to the quality of the radio channel. This gives better clear channel quality and better robustness to errors. These benefits are realized whether operating in full-rate or half-rate channels.
+
+As well as quality improvements, the need to enhance capacity by allocating half-rate channels to some or all mobiles is also recognized. The radio resource algorithm, enhanced to support AMR operation, allocates a half-rate or full-rate channel according to channel quality and the traffic load on the cell in order to obtain the best balance between quality and capacity. It is intended that the control system should not be fixed but can be enhanced as experience of the AMR system is gained on real networks; it may also be tuned to meet particular operator's network needs.
+
+## 3.2 Application scenarios
+
+The AMR codec concept is adaptable not only in terms of its ability to respond to radio and traffic conditions but also to be customized to the specific needs of network operators. There are three levels of adaptation of the AMR system:
+
+- handovers between half-rate and full-rate channels according to traffic demands;
+
+- variable partitioning between speech and channel coding bit-rates to adapt to channel conditions in order to obtain best speech quality;
+- optimization of channel and codec control algorithms to meet specific operator needs and network conditions.
+
+This allows the codec to be applied in many ways of which three important examples are:
+
+- full-rate only for maximum robustness to channel errors but no capacity advantage. This additional robustness may be used not only to extend coverage in marginal signal conditions, but also to improve capacity through tighter frequency re-use, assuming high AMR MS penetration;
+- half-rate only for maximum capacity advantage; more than 100 % capacity increase achievable relative to FR or EFR (i.e. same as existing HR); significant quality improvements relative to existing HR will be given for a large proportion of mobiles as a result of codec mode adaptation to channel conditions;
+- mixed half/full rate operation allowing a trade-off between quality and capacity enhancements according to radio and traffic conditions and operator priorities.
+
+This is explained further in annex B.
+
+# --- 4 Development Time-scales
+
+A number of operators have expressed the urgent requirement for the availability of the AMR system by 1999. This was reflected in a statement from the MOU at SMG#20 when the AMR Study phase was initiated (see Tdoc SMG 96). The target for the completion of the AMR codec specifications has been set for Release 1998. Two reasons for this early availability is to reduce the cost of introduction of AMR on networks (lower write-off costs of redundant equipment) and to maximize the opportunity for early AMR handset penetration to optimize the capacity advantage of the codec.
+
+The feasibility of achieving this delivery date has formed part of the Feasibility Study. Consistent with this goal, the Study Phase was restricted to one year notwithstanding the complexity and novelty of the AMR system concept.
+
+## Phased Approach
+
+The early delivery of the AMR codec will reduce the cost of introduction to operators since the network capacity will be less and the write-off costs of redundant equipment lower. Therefore a phased approach is being followed:
+
+Phase 1: The complete AMR speech and channel codecs will be defined, together with the *codec mode adaptation* control processes, possible new link performance metrics and their transmission in-band on the traffic channel.
+
+The *channel mode adaptation* will be based closely on existing intra-cell handover methods in terms of signaling procedures i.e. will rely on the handover command. However, the *channel mode adaptation* decision algorithm will probably be extended and use the currently available metrics, RxQual and RxLev and possible newly defined metrics. This algorithm will be left open to manufacturers to develop and improve with time. Re-packing of half-rate radio channels required by AMR operation will rely again on existing signaling procedures.
+
+The circuit allocation procedures are assumed to be left unchanged. Constraints on the possible codec mode changes may appear for the half-rate mode. In particular, changes between codecs, without channel mode change, may be allowed only if the same Ater bit rate is possible.
+
+Phase 2: This will introduce new mode *adaptation* control algorithms, enhanced by means e.g. of new link quality metrics, more advanced handover, enhanced re-packing algorithms, etc.
+
+Phase 1 should of itself deliver substantial performance benefits both in terms of speech quality and capacity enhancements. The need or otherwise for a more complicated Phase 2 will be determined after Phase 1 is complete.
+
+# --- 5 Baseline description and working assumptions
+
+This clause deals with the basic description of the AMR concept together with a summary of the working assumptions agreed during the feasibility phase. The section also explains the main constraints on the codec design.
+
+## 5.1 Generic operation
+
+The *AMR* codec is a single speech and channel codec whose *channel mode* and *codec mode* bit-rates can be varied to suit the prevailing channel and traffic conditions. The codec can operate in two channel modes, *full-rate* and *half-rate*, corresponding to the TCH/F and TCH/H channels.
+
+For each *channel mode*, the codec speech and channel bit-rates (i.e. the *codec mode* bit-rates), can be varied rapidly (several times a second) to track the channel error rates or C/I of the channel near-instantaneously. This gives significant performance improvement over a corresponding fixed rate codec, which is a compromise between the full range of channel conditions encountered. The channel measurement reports and any other information for the codec mode adaptation will be transmitted in-band in the traffic channel or using stealing flag techniques. The *codec mode* bit-rate can also be varied in consideration of other environmental conditions like the acoustic background noise. This would allow the well-known failures of low bit-rate codecs with high background noise conditions to be dealt with. Adaptation of the codec mode bit-rate driven by the encoder at the MS can be, however, superseded by the network.
+
+In addition, the *channel mode* of the codec can be switched in order to increase channel capacity while maintaining the speech quality to (operator specified) limits. These variations are carried out by means of *AMR handovers*, which will occur far less frequently than the codec mode changes (probably no more than a maximum of a few times per minute). This range of operation of the two *channel-modes* is illustrated in Figure 5.1. AMR handovers may be based on a combination of RxLev and RxQual measurement reports and on new metrics derived from the measurement reports transmitted in-band for *codec mode adaptation*. A conventional HO between HR & FR based only on capacity considerations by the network operator is also possible.
+
+![Figure 5.1: Preferred operating ranges for HR and FR channel modes. The graph shows two horizontal bars representing the operating ranges for Full Rate (FR) and Half Rate (HR) modes. The x-axis is labeled 'C/I' and has three markers: 'limit of sensitivity (e.g. 4 dB)', 'limit for recommended HR operation (Operator specified)', and '∞'. The y-axis is labeled 'TCH mode' and has two markers: 'FR' and 'HR'. The FR bar starts at the 'limit of sensitivity' and extends to '∞'. The HR bar starts at the 'limit of sensitivity', has a dashed section until the 'limit for recommended HR operation', and then a solid section extending to '∞'.](72d357d406618f3f884c3876fc3058ee_img.jpg)
+
+Figure 5.1: Preferred operating ranges for HR and FR channel modes. The graph shows two horizontal bars representing the operating ranges for Full Rate (FR) and Half Rate (HR) modes. The x-axis is labeled 'C/I' and has three markers: 'limit of sensitivity (e.g. 4 dB)', 'limit for recommended HR operation (Operator specified)', and '∞'. The y-axis is labeled 'TCH mode' and has two markers: 'FR' and 'HR'. The FR bar starts at the 'limit of sensitivity' and extends to '∞'. The HR bar starts at the 'limit of sensitivity', has a dashed section until the 'limit for recommended HR operation', and then a solid section extending to '∞'.
+
+Figure 5.1: Preferred operating ranges for HR and FR channel modes
+
+## 5.2 Constraints
+
+Due to the challenging quality/capacity targets of AMR, the feasibility phase identified the need for a high degree of freedom to be left to the codec proponents in order to meet the requirements. Nonetheless, a number of constraints to the AMR codec design have been identified. They are reported in the following.
+
+**Radio interface:** The AMR codec and its control will operate without any changes to the air-interface channel multiplexing, with the possible exception of the interleaving depth. Conventional TCH-F and TCH-H channels will be used for FR and HR *channel modes* of the codec.
+
+**Channel mode handovers:** These will be executed in the same way as existing intra-cell handovers. However, the algorithm used to determine when and whether to perform an AMR handover will be new and specific to the BSS manufacturer.
+
+**Codec mode signaling:** Signaling and measurement reporting for codec mode changes shall be transmitted on the radio interface in-band or using frame stealing flag techniques to avoid the need for new out-of-band signaling channel. Signaling information can be different on the up and down links.
+
+**Frequency hopping:** The greatest quality benefits of AMR will be achieved when frequency hopping is applied. Without it, the benefits may be reduced especially for slow moving or stationary mobiles.
+
+**Power control:** It shall be possible to operate power control independently of the AMR adaptation. However, operators may choose to optimize the AMR control according to the power control settings. Fast power control may also be introduced provided that the measurement reports are transmitted in-band for AMR codec adaptation control.
+
+**TFO:** The AMR codec shall support Tandem Free Operation. TFO shall not decrease the capacity gain achievable using the AMR codec.
+
+**DTX:** The AMR codec shall support DTX operation. The increase in radio channel activity in terms of average transmission power during speech inactivity shall not significantly affect the gain of DTX operation i.e. the interference reduction and the battery saving should be similar to that of current DTX operation.
+
+(See also subclause 5.6).
+
+**A-ter Sub-multiplexing:** At least one codec mode at HR should be consistent with 8 kbps sub-multiplexing on the A-ter interface (see subclause 5.7).
+
+**Complexity:** The complexity of the channel codec shall be no greater than that of the HR channel codec. The complexity of the source codec shall be no greater than 8 times that of the FR codec.
+
+## 5.3 Speech and channel codecs
+
+The AMR codec will operate at a number of different codec mode bit-rates for each of the two channel modes (FR and HR). The precise number of modes for each channel is left open to be decided by the codec proponent. It has a strong dependency on the codec mode adaptation algorithm employed. Each of these codec modes is expected to provide different performance as a function of the channel quality (C/I) that can be represented by a family of curves like those reported in Figure 5.2.
+
+![Figure 5.2: Family of curves showing performance for different codec modes. The graph plots performance (Y-axis) against C/I (X-axis). Three curves are shown: Mode 1 (blue diamonds), Mode 2 (pink squares), and Mode 3 (black triangles). The curves show that performance increases with C/I. Mode 1 starts at a lower performance at low C/I but reaches the highest performance at high C/I. Mode 2 and Mode 3 show intermediate performance levels. The Y-axis is labeled with M, O, and S at the top, and the X-axis is labeled C/I.](79d61011f426d34fb542d86176482d2c_img.jpg)
+
+Figure 5.2: Family of curves showing performance for different codec modes. The graph plots performance (Y-axis) against C/I (X-axis). Three curves are shown: Mode 1 (blue diamonds), Mode 2 (pink squares), and Mode 3 (black triangles). The curves show that performance increases with C/I. Mode 1 starts at a lower performance at low C/I but reaches the highest performance at high C/I. Mode 2 and Mode 3 show intermediate performance levels. The Y-axis is labeled with M, O, and S at the top, and the X-axis is labeled C/I.
+
+**Figure 5.2: Family of curves showing performance for different codec modes**
+
+To achieve the expected improvements in terms of quality, the AMR concept is based on switching among modes to the aim of tracking always the best performance as a function of channel conditions. This corresponds, in principle, to have the codec operating in the mode whose performance is the highest for a given C/I value. Since *codec mode adaptation* may occur rapidly, *codec mode rate changes* must occur seamlessly, i.e. with no perceptible speech degradation.
+
+Moreover, to account for failures of the control system, a minimum level of performance shall also be granted for any point of the family of curves. For this reason, assessment of performance must consider the whole family of curves as well as the performance under dynamic behavior. This implies that testing of the AMR codec will be more extensive than for EFR.
+
+## 5.4 Rate adaptation
+
+Two types of rate adaptation are needed; *channel mode* (i.e. handovers between FR and HR) and *codec mode* (i.e. source and channel bit-rates for a given *channel mode*). *Conventional handovers* can be performed independently of AMR operation.
+
+### 5.4.1 Channel mode adaptation
+
+The *channel mode* (FR or HR) is switched to achieve the optimum balance between speech quality and capacity enhancements. The up- and down-links shall use the same *channel mode*. The *channel mode* is selected by the network (probably the BSC) based on measurements of the quality of the up- and down-links. These measurements may be combinations of conventional RxLev and RxQual reports and additional data transmitted in-band in the traffic channel or via flag stealing techniques.
+
+The *channel mode* control algorithm should limit the frequency of *AMR handovers* performed to minimize the associated speech degradation as well as potential problems with channel re-packing and A-ter sub-multiplexing.
+
+### 5.4.2 Codec mode adaptation
+
+The *codec mode bit-rate*, i.e. the bit-rate partitioning between the speech and channel coding for a given *channel mode* may be varied rapidly to track changes in the radio link and to account for specific input conditions (speech signal characteristics, acoustic environmental characteristics, etc.).
+
+*Codec mode adaptation* will operate independently on the up- and down- links. It will be transparent to the channel allocation and operate independently of it. Control will depend mainly on measurements of the quality of the respective links. The radio link quality metrics currently available, RxQual and RxLev, may not be adequate for *codec mode adaptation* (e.g. because they do not provide a sufficiently good measure of the impact of the link quality on speech quality or they are not transmitted frequently enough). Therefore, a new metric(s) may be desirable in addition to the existing ones and may be transmitted in-band on the traffic channels.
+
+While the control of the *channel mode adaptation* will be mandatory located in the network side, there are several options of where the *codec mode adaptation* control algorithm could be located, e.g.:
+
+- uniquely from the network for both links;
+- by the relevant receiving entity (i.e. the MS for the downlink and the BTS for the uplink);
+- by the relevant transmitter based on reported measurements.
+
+It is however assumed that the *codec mode* decision could be overridden by the network entity.
+
+The three scenarios differ in terms of signaling capacity needs and in the delay introduced in the adaptation process.
+
+The current working assumption is to locate the codec mode adaptation control in the network. With such assumption, it is most likely that the in-band signaling channels in uplink and downlink would be asymmetric. This implies that the amount of bit-rate devoted to channel coding of the speech information can be different in uplink and downlink, thus allowing the use of two different channel coding algorithms for the two links. In order to preserve TFO, the possible source coding modes, instead, shall be the same in uplink and downlink.
+
+The maximum rate of adaptation will be determined by the in-band signaling data rate and the loop delay. Early analysis suggests that *codec mode rate* changes of several times a second can be supported. A further constraint to the maximum adaptation rate is given by the increase in the channel activity when operating in DTX mode (see subclause 5.6 for further details).
+
+## 5.5 Support of TFO
+
+For the same reasons as for the existing GSM codecs (improved mobile to mobile performance), TFO is required for AMR. The optimum solutions have yet to be determined at this stage, however, the feasibility aspects are considered in subclause 6.4.1.
+
+## 5.6 Support of DTX
+
+The AMR codec shall support DTX operation. Therefore VAD algorithm and Comfort Noise generation algorithm are part of the specification of the AMR codec. However, the DTX algorithms are not required to be included in the proposals of candidates until after the selection phase.
+
+While the DTX mechanism in today's GSM codecs is activated by the input signal content only, when considering the signaling needs of the AMR codec, it may be necessary transmit in-band signaling data even during periods where the channel could be switched off. This could imply an increase of the SID frame transmission rate when compared to the current situation. To limit the impact of such effect on the DTX gain, the increase of the radio channel activity in terms of average transmission power should not exceed [8 %].
+
+## 5.7 Support of 8 and 16 kbit/s A-ter sub-multiplexing
+
+The AMR codec shall support A-ter sub-multiplexing at 16 kbit/s. Sub-multiplexing at 8 kbit/s for HR channel mode is desirable but imposes a severe constraint on the maximum source bit-rate (in the range of 6,5 kbit/s to 7,5 kbit/s) which could undermine the performance quality target matching. In addition, switching between codec modes of the AMR
+
+codec could imply rapid switching between 8 and 16 kbit/s sub-multiplexing that could be difficult to achieve and cause quality degradations. It is expected therefore that 8 kbps sub-multiplexing would only be used when a low HR codec rate is maintained for relatively long periods of time (e.g. 30 seconds or more).
+
+A proposal was also received for a 6:1 multiplexing scheme, which could be applicable, when the majority of calls are AMR. This is for further study.
+
+## 5.8 Active noise suppression
+
+The possibility to include a noise suppresser in the AMR codec has been discussed. It was felt that a noise suppresser would improve the performance in background noise conditions of any candidate, especially in half rate mode. At the same time, it is essential to check the consistency of the improvement with multiple noise sources and noise levels, and to verify that the noise suppresser does not degrade the speech quality in clean speech conditions. These additional requirements would imply a dedicated test plan incompatible with the aggressive codec selection time frame.
+
+As a consequence, in order to compare all solutions in the same conditions, and select the candidate with the best intrinsic quality, it was decided that noise suppressers would not be included during the qualification and selection phases, or that any noise suppresser integrated to a source codec should be turned off for these tests.
+
+The selection and possible standardization of a noise suppresser will then be addressed in a separate phase in parallel with the definition of the VAD algorithm.
+
+# 6 Feasibility issues
+
+This Section discusses the main issues determining the feasibility of the AMR approach.
+
+## 6.1 Codec performance
+
+The original performance benchmarks set by SQSG for AMR are reproduced in Annex C. Several organizations ran extensive subjective tests of high performance codecs, representative of the types of codecs that would be submitted as candidates for AMR, to assess the feasibility of meeting these performance targets.
+
+The possibility for AMR to provide robustness in error conditions by increased channel coding and hence lower rate speech coding on the one hand, and increased basic speech quality (higher source coding rate) at the expense of reduced error robustness on poor channels on the other hand, depends strongly on the channel error statistics.
+
+It is anticipated that the performance gain of AMR under high error conditions will be significant under close to ideal frequency hopping situations, but that there will be no or marginal performance improvements under slow moving conditions without frequency hopping, due to the high frame erasure rates. Note that in this Section, figures of C/I (carrier to interference ratios) are referenced to the input to the channel equalizer. In GSM 05.05, a 2 dB implementation margin is assumed in the receive path so that a C/I of 7 dB at the channel equalizer corresponds to 9 dB at the antenna.
+
+### 6.1.1 Basic, error and background noise performance
+
+From the point of view of the envisaged applications for AMR (see subclause 3.2.), the critical performance benchmarks can be reduced to the following:
+
+#### Full-rate mode:
+
+|                        |              |
+|------------------------|--------------|
+| Clear (EP0)            | EFR at EP0 * |
+| EP3                    | EFR at EP1   |
+| Background noise (EP0) | Same as EFR  |
+
+#### Half-rate mode:
+
+|             |            |
+|-------------|------------|
+| Clear (EP0) | G.728      |
+| EP1         | EFR at EP1 |
+| EP3         | FR at EP3  |
+
+Background noise at EP0
+
+G.728
+
+The definitions of EP0, EP1, EP2 and EP3 are given in Annex A under "Acronyms".
+
+#### Full-rate mode
+
+In full-rate mode, the main challenge is the EP3 performance and the tests so far performed indicate this target could be difficult to achieve, representing a small risk. EFR at EP0 can be met (cf. Existing EFR codec) for which a codec bit rate approaching 12 kbps is likely to be necessary.
+
+It is expected that the performance for lower rate codec modes in the presence of background noise will be noticeably lower than that of EFR (in clear conditions).
+
+#### Half-rate mode
+
+More challenging is the performance that is to be achieved in half-rate mode. The "wireline" criterion for HR mode was interpreted by SQSG as G.728 (similar to G.726 at 32 kbps used on DECT and CT2). The corresponding objective at EP1 was EFR EP1 performance. EP1 corresponds to a C/I of 10 dB at the channel equalizer input. Results from trial codecs have shown that this C/I figure is too low to achieve EFR EP1 performance because the speech codec bit rate needed for G.728 quality is likely to be close to 8,0 kbps, leaving very little room for channel protection. Test results on several different codecs have shown that a more realistic target to reach EFR EP1 quality is a C/I threshold of 16 dB to 20 dB. Similarly, the quality objective in HR mode at EP1 has been relaxed to FR at EP1.
+
+This means that to maintain the quality target, a lesser proportion of calls will be in half-rate mode; alternatively with the same proportion of half-rate mode calls, the average quality will be degraded in half-rate mode. The implications are discussed further in subclause 6.3.
+
+The EP3 target can be met as evidenced by the existing GSM HR (5,6 kbps) codec.
+
+The background noise performance in the half-rate channel mode is a critical AMR area. The background noise performance will be lower than in the full-rate channel mode. On examination, the background noise target of G.728 (the original objective for AMR in HR) was found in fact to be even higher than that of EFR. Neither G.728 nor EFR background noise performance is likely to be achieved at a data rate of around 8 kbps. It is recommended instead that the background noise requirement be relaxed to "Better than both GSM FR and G.729".
+
+The reason for choosing two references is that the GSM FR codec performs better with vehicle noise while G.729 performs better with street noise and babble.
+
+In the presence of background noise, the channel error performance of the AMR half-rate code modes will be noticeably worse than without background noise. One result showed that GSM FR performance might be difficult to achieve around 10 dB.
+
+### 6.1.2 Tandeming
+
+The performance under tandeming conditions has not been measured. As a general rule, if good/excellent performance is being achieved under single codec conditions, then it is unlikely that a serious loss of quality will be encountered under tandeming of the AMR codecs, except possibly under background noise and error conditions. However, this is less evidently the case for mismatched codecs. The lack of data on tandeming performance therefore represents a small level of risk.
+
+When AMR reaches a significant level of penetration, it is very likely that a large proportion of calls will be MS-to-MS. The management of the AMR by TFO is therefore important to minimize tandeming of codecs.
+
+Furthermore the interoperability with any GSM codec (including the AMR) will have to be assessed.
+
+### 6.1.3 Seamless codec mode bit-rate changes
+
+Codec mode bit rate changes may occur rapidly (more than once a second) and it is required that the switching between codec modes (for the same channel mode) must occur without any audible impairment. Tests conducted by two organizations have shown that with appropriate care to the codec structure, this is achievable.
+
+While the switching itself should not cause any audible glitches, the fact that the speech codec bit rates is changing will itself cause some change in speech quality which will be audible. However, the reason for changing codec mode will normally be a change of channel errors and the effect of *not* changing codec mode will be worse.
+
+### 6.1.4 Complexity
+
+The complexity of the AMR source and channel codecs is governed on the one hand by the need to meet the required performance levels and on the other, to allow AMR to be introduced at the lowest cost. To meet these needs, the following constraints have been agreed.
+
+Considering:
+
+- that an increase of the channel codec complexity may not allow significant improvement of the speech quality;
+- the high cost of BTS hardware upgrade.
+
+The complexity requirement for:
+
+- the channel part of the AMR codec when in half-rate mode (including control loop management) is not to exceed the Half Rate channel codec complexity figure;
+- the channel part of the AMR codec when in full-rate mode (including control loop management) is not to exceed twice that of the Half-rate channel codec complexity figure.
+
+Considering:
+
+- that quality improvements could be achieved in the speech codec with an increase of the complexity figure;
+- the DSP technology increase in the time frame of AMR introduction (during 1999).
+
+The complexity limit for the speech part of the AMR codec (excluding VAD/DTX) is 8 times the complexity figure of the speech part of the Full Rate codec.
+
+Nevertheless an AMR speech codec with a complexity figure less or equal than the existing codecs (EFR or HR) will present significant advantage. This will lead to a complete reuse of the existing platforms for both MS and TRAUs.
+
+#### Requirements summary
+
+|                                                                      | Complexity requirement                                                |
+|----------------------------------------------------------------------|-----------------------------------------------------------------------|
+| Half-rate channel coder/decoder (including control loop management ) | less than or equal to that of the HR channel codec                    |
+| Full-rate channel coder/decoder (including control loop management ) | less than or equal to twice that of the HR channel codec              |
+| Speech coder/decoder (excluding VAD/DTX)                             | less than or equal to 8 times the FR speech codec (excluding VAD/DTX) |
+
+Appropriate ways of measuring complexity for the purposes of codec test and selection have still to be determined.
+
+## 6.2 Quality and Capacity benefits of AMR
+
+AMR may be used in different ways in a system. The basic features of AMR are the higher robustness to low C/I conditions on full rate channels and the higher quality on half rate channels at high C/I levels. These basic features may be used in different ways to obtain higher quality or higher capacity.
+
+### 6.2.1 General AMR performance
+
+A central principle of AMR is the ability to dynamically change the allocation of source and channel coding bits, in order to always provide the highest possible speech quality. The overall quality and capacity improvements with AMR are dependent on several factors:
+
+- codec performance as a function of channel quality;
+- C/I distribution in the selected area, as well as actual C/I variations in calls;
+- precision and update frequency of the AMR control system;
+
+- system characteristics (type of FH, number of TRX's etc.).
+- a) The basic codec performance as a function of channel quality (e.g. C/I) provides an upper limit to the achievable quality by AMR. I.e. the envelope of the performance curves defines the best possible performance assuming perfect channel quality tracking. For FH systems and non-FH systems at high speeds different allocation of bits for the speech coder and for error protection gives a possibility for trading capacity and quality (see subclause 3.2). A crucial point is the estimation of channel quality, and the relation between channel quality measurements and speech quality. This has only partly been assessed. (See subclause 6.3.3.)
+- b) In general there is a relatively large spread of C/I values, indicating that an AMR coder with adaptive allocation of speech and channel coding bits can provide higher quality or capacity by change of working point (bit allocation). The actual channel quality may however vary significantly between and within calls, and the possibility to accurately track the channel with sufficient resolution may limit the AMR gain. Limited sets of measured data were made available, indicating very large variations within as well as between calls. The conclusion is that AMR needs to be very robust to a large span of channel variations.
+- c) Channel quality variations may be both rapid and large. In the design of the control system there is a trade-off between in-band channel information and speech coder bits. The performance of the channel tracking algorithm will also highly influence the AMR performance.
+- d) The specifics of the system, such as the use of different FH, the number of TRX's per cell, the efficiency of the power control if activated and particular frequency and cell planning strategies etc. will have an influence on the codec performance and the possible quality/capacity gains. The characteristics of specific networks have indeed a direct influence on the C/I statistical distribution, leading to potentially reduced spread of the C/I in "optimized" systems and hence potential lower additional gain brought by AMR.
+
+### 6.2.2 Improved coverage from the improved robustness in FR mode
+
+Under high channel errors, a FR codec mode will normally be selected which has a low source coding rate and a high level of error protection. This will allow good speech quality to be maintained under S/N conditions 6 dB worse than the corresponding level for EFR. This translates to an improvement in terminal or BTS sensitivity but is subject to the limit of robustness of the signaling channels [not estimated during the Study Phase]. This improvement in sensitivity is at least 2 dB and could be as high as 4 dB or 6 dB.
+
+This extension may be exploited for improved coverage in marginal conditions such as in buildings or potentially for range extension. The latter would only apply to new networks where site spacing has still to be selected and where the great majority of terminals are AMR. Even then, there could be performance problems with terminals without AMR such as roamers and data terminals. This was not investigated.
+
+### 6.2.3 Capacity benefits from the improved robustness in FR mode
+
+The GSM system capacity is a direct function of the minimum acceptable C/I ratio for an expected Grade of Service (for example 99 % of the cell area). The distribution of the C/I over a GSM network is in turn a function of the frequency re-use pattern, and directly related to the activation and performances of the radio features of the system, such as Slow FH, Power Control, DTX etc. The capacity also depends on the propagation conditions in the area of concern, such as shadowing characteristics, applicable propagation losses, antenna heights and apertures. Finally the actual performances of the infrastructure will generally impact the system capacity.
+
+With AMR in full rate mode, the C/I threshold for an acceptable speech quality level may be reduced by 4 dB to 6 dB compared to the system operation with the current speech coders (FR, HR or EFR). This improvement will translate in the possibility to operate the system with a reduced re-use cluster, or with a higher traffic loading. For example a system operating in a 12-cell cluster could be upgraded to a 9-cell re-use cluster providing a direct 30 % capacity increase.
+
+This improvement is applicable if AMR is used in Full Rate mode at low C/I conditions or severe error conditions, i.e. for applications where AMR is used in Full Rate mode only or in both Half and Full rate modes according to the propagation conditions (application scenarios 1 and 3 of annex B).
+
+However, an improvement gained by a re-planning of existing systems should be considered with care as it does not apply to the GSM signaling channels, to the speech service when using speech coders other than AMR or to the data services, i.e. in networks with a mix of services where the penetration of AMR is limited.
+
+### 6.2.4 Quality/capacity trade-offs by use of the HR mode
+
+A number of simplified studies on the quality/capacity aspects have been made. It is generally agreed that there is a possibility for a trade-off between quality and capacity using AMR; Full Rate only (for maximum quality), half rate only (for maximum capacity) or a mix of full rate and half rate (in a similar manner as for the existing coders). The actual quality and capacity will however depend heavily on the system assumptions as well as the specific AMR solution. In particular, there are significant difficulties in estimating actual C/I distributions in systems. Two main approaches have been used to estimate the capacity gain, as described below.
+
+#### Estimated C/I distribution approach
+
+In one approach the capacity increase has been estimated assuming the half rate channel mode can be used above a certain C/I threshold, where it provides G.728 quality. This threshold has been estimated at 16 dB to 20 dB using ideal FH. Capacity gain, assuming full penetration of AMR mobiles, was then derived from the instantaneous C/I distribution within the cell, by applying a "safety" margin on top of the previously discussed threshold. The C/I distribution used was a distribution used in earlier work on 14,4 kbps data, which includes the effects of shadowing. The safety margin has to count for all the effects not taken into account in such evaluation i.e. the channel quality estimation error, the variability of the channel quality, the channel adaptation control delay, the blocking of resources, imbalance in up- and down-link etc. With that approach the corresponding capacity increase has been *estimated to be 30% - 40%* using a C/I threshold of 18 dB and safety margin of 7 dB. It should be noted that the safety margin is an estimate.
+
+Another estimation with different system assumptions using actual C/I distributions from a planning tool (for a particular dense area of the network) used by one operator have also been performed. The estimated C/I distribution in each cell was then used, as well as the traffic distribution and BTS configuration. In general, the C/I distribution obtained has a higher mean value than the above approach, which uses a "typical" C/I distribution. The higher mean value translates into a higher number of mobiles, which can use the HR channel mode at any given time, resulting in higher capacity gains. The study also indicated that there are clear differences in the calculated C/I distributions for different areas. Assuming satisfactory speech quality is obtained on the HR channel for C/I values exceeding 18 dB, and using a "safety" margin of 7 dB, the resulting capacity figures for 100 % AMR penetration are in the range 80 % up to 110 % (trunking gain included) depending on the actual planning area. These results clearly indicate that the capacity gain for a certain quality is strongly dependent on the C/I distribution in the system.
+
+#### System simulator approach
+
+An alternative approach uses a radio system simulator to estimate the quality and capacity. In this approach a representative family of codec performance curves are used to describe the speech quality of the different AMR codec modes depending on C/I. An AMR control system, which incorporates measurement errors as well as decision delays, is used to select codec modes and perform channel mode handovers.
+
+Figure 6.1 indicates the trade-off between relative capacity and "average" speech quality in a system, assuming 100 % AMR penetration, with ideal FH and power control using 4 TRX's per cells.
+
+![Line graph titled 'Average speech quality' showing speech quality [dB Q] vs relative capacity for AMR and EFR/HR.](1c427123350e0e73e2a109b79069314b_img.jpg)
+
+The graph shows the average speech quality (in dB Q) as a function of relative capacity for two systems: AMR and EFR/HR. The x-axis represents 'Relative capacity' from 1 to 2.25. The y-axis represents 'Speech quality [dB Q]' from 16 to 28. The AMR curve starts at approximately 26.8 dB Q at a relative capacity of 1 and decreases to about 21.8 dB Q at a relative capacity of 2.25. The EFR/HR curve starts at approximately 25.3 dB Q at a relative capacity of 1 and decreases to about 18.8 dB Q at a relative capacity of 2.25. The AMR curve is consistently above the EFR/HR curve, indicating better speech quality across the range of relative capacities shown.
+
+| Relative capacity | AMR [dB Q] | EFR/HR [dB Q] |
+|-------------------|------------|---------------|
+| 1.0               | 26.8       | 25.3          |
+| 1.25              | 25.3       | 22.8          |
+| 1.5               | 24.0       | 20.8          |
+| 1.75              | 22.8       | 19.3          |
+| 2.0               | 22.0       | 18.8          |
+| 2.25              | 21.8       | 18.8          |
+
+Line graph titled 'Average speech quality' showing speech quality [dB Q] vs relative capacity for AMR and EFR/HR.
+
+**Figure 6.1: Average speech quality vs. relative capacity for AMR and EFR/HR**
+
+Speech quality is presented in equivalent dBQ. As a reference, the existing FR has a quality of approximately 22 dBQ under error free conditions. A comparison with a solution using the existing EFR and HR to gain capacity is included. The quality gain of AMR is approximately 3 dBQ. At a capacity increase of 85 % for AMR, the average quality is approximately the same as for the EFR/HR system at a capacity increase of 25 %. The average quality if only half rate channels are used is also noticeably increased for AMR due to the higher basic quality of AMR. If two TRX's are used the quality is lowered by approximately 1 dBQ and if six TRX's are used the quality is raised by approximately 1 dBQ, but the difference between AMR and EFR/HR remains.
+
+Figure 6.2 is similar to figure 6.1, except instead of the average speech quality, the quality at a certain proportion of the speech quality distribution in the system is shown.
+
+![Line graph showing Speech quality [dB CQ] vs. Relative capacity for AMR and EFR/HR at 3% and 10% levels. The graph shows four curves: AMR 10% level (solid line), EFR/HR 10% level (dashed line), AMR 3% level (solid line), and EFR/HR 3% level (dashed line). All curves show a decrease in speech quality as relative capacity increases. The 10% level curves are higher than the 3% level curves. AMR curves are generally higher than EFR/HR curves at the same level and capacity.](9260ae281f6b6470331f4a0f82dbc2b1_img.jpg)
+
+Speech quality vs. relative capacity
+
+| Relative Capacity | AMR 10% level [dB CQ] | EFR/HR 10% level [dB CQ] | AMR 3% level [dB CQ] | EFR/HR 3% level [dB CQ] |
+|-------------------|-----------------------|--------------------------|----------------------|-------------------------|
+| 1.0               | 24.8                  | 22.0                     | 16.0                 | 16.0                    |
+| 1.25              | 23.0                  | 20.0                     | 15.0                 | 15.0                    |
+| 1.5               | 21.0                  | 19.0                     | 14.0                 | 14.0                    |
+| 1.75              | 19.0                  | 18.0                     | 13.0                 | 13.0                    |
+| 2.0               | 17.0                  | 17.0                     | 12.0                 | 12.0                    |
+| 2.25              | 15.0                  | 16.0                     | 10.0                 | 10.0                    |
+
+Line graph showing Speech quality [dB CQ] vs. Relative capacity for AMR and EFR/HR at 3% and 10% levels. The graph shows four curves: AMR 10% level (solid line), EFR/HR 10% level (dashed line), AMR 3% level (solid line), and EFR/HR 3% level (dashed line). All curves show a decrease in speech quality as relative capacity increases. The 10% level curves are higher than the 3% level curves. AMR curves are generally higher than EFR/HR curves at the same level and capacity.
+
+**Figure 6.2: Speech quality for AMR and EFR/HR at the 3 % and 10 % levels**
+
+The 3 % curve can be interpreted as the quality of the 3 % of the calls (or parts of the calls) which have the worst quality in the system. If capacity increases are limited to approximately 70 %, there is a significant increase in quality for the calls with the lowest quality due to the robust operation on the full-rate channel.
+
+### 6.2.5 System aspects of capacity/quality
+
+In the above section, the capacity gain was computed with a number of simplifying assumptions, given the difficulty to have a complete picture of the actual behavior of the system. Some of the following aspects have partly, or not, been modeled in the previously computed gain.
+
+The re-packing of half rate and full rate channels on the air interface may potentially cause high system load as well as degradation due to intra-cell handovers. The results presented in the previous section do not require a sophisticated re-packing strategy. Results have also been presented indicating slightly higher gains if more sophisticated re-packing strategies are used.
+
+It is desirable to limit the channel mode handovers to at most a few AMR handovers per 2-min. call. Results have been presented indicating that the quality/capacity degradation due to such limitations is small.
+
+In connections where the quality of up- and down-links differ substantially, there is potentially a loss, since the two links are required to use the same channels (full-rate or half-rate). [Contributions needed]
+
+A further impact on quality and capacity may be due to resource allocation constraints. Indeed among other aspects, the assumption that time-slots within a cell do not, on a short term basis, provide the same quality leads to the need to combine the channel mode adaptation and the resource allocation in order to avoid Ping-Pong between modes as
+
+explained in Section 6.3.6. This has a direct impact on the "re-packing efficiency" and hence on the expected capacity gain since mobiles cannot be simply moved onto any time-slot.
+
+### 6.2.6 MS penetration
+
+Studies on the impact of AMR penetration on capacity gain have been conducted following the approach of an estimated C/I distribution in subclause 6.2.3. The results presented in figure 6.3 gives an indication of capacity gain depending on AMR penetration for different levels of the half rate C/I operating thresholds (including the "safety" margin described in subclause 6.2.4). The case when AMR is operated in HR mode only is also indicated. The results for 100 % AMR penetration is consistent with 30 % to 40 % capacity gain obtained with an aggregated C/I threshold of approximately 25dB.
+
+![Figure 6.3: AMR capacity gain as a function of AMR penetration. The graph shows Capacity Improvement (Y-axis, 0.0% to 120.0%) versus AMR Penetration (X-axis, 50% to 100%). Four curves are shown: HR Only (red), 15 dB (cyan), 20 dB (purple), and 25 dB (teal). All curves show an increasing trend in capacity improvement as AMR penetration increases. The HR Only curve reaches approximately 115% at 100% penetration, while the 25 dB curve reaches approximately 38%.](bd4617f25d15430eb78c2d6d75a99dde_img.jpg)
+
+| AMR Penetration (%) | HR Only (%) | 15 dB (%) | 20 dB (%) | 25 dB (%) |
+|---------------------|-------------|-----------|-----------|-----------|
+| 50%                 | 60          | 45        | 35        | 20        |
+| 60%                 | 70          | 55        | 40        | 22        |
+| 70%                 | 80          | 65        | 45        | 25        |
+| 80%                 | 90          | 70        | 50        | 30        |
+| 90%                 | 100         | 75        | 55        | 32        |
+| 100%                | 115         | 85        | 60        | 38        |
+
+Figure 6.3: AMR capacity gain as a function of AMR penetration. The graph shows Capacity Improvement (Y-axis, 0.0% to 120.0%) versus AMR Penetration (X-axis, 50% to 100%). Four curves are shown: HR Only (red), 15 dB (cyan), 20 dB (purple), and 25 dB (teal). All curves show an increasing trend in capacity improvement as AMR penetration increases. The HR Only curve reaches approximately 115% at 100% penetration, while the 25 dB curve reaches approximately 38%.
+
+Figure 6.3: AMR capacity gain as a function of AMR penetration
+
+## 6.3 Codec adaptation
+
+The working assumptions for the mechanisms for codec adaptation are described in clause 5. Here, the feasibility aspects only are addressed.
+
+### 6.3.1 Codec mode
+
+The codec mode (bit-rate partitioning between the source and channel coding) should be changed rapidly to respond to the rapidly changing radio conditions. For this an accurate channel metric is needed and measurement reports should be reported frequently across the air-interface.
+
+The schemes for doing this are assumed to be part of the proposals from the AMR candidates. Nonetheless, their feasibility should be assessed here.
+
+Signaling data transmitted over the radio interface for codec mode control may include channel quality measurements, codec mode preferences from the MS, codec mode commands from the network and possibly other information depending on the specific proposal.
+
+In the case of a very small amount of information, in principle the stealing flag bits can be used, otherwise a certain portion of the speech frame bits must be used.
+
+How fast the update rate of such information should be, depends on the dynamic behavior of the channel conditions.
+
+An update rate of 10 times a second (five times faster than that of the RxQual and RxLev reporting) should be adequate to maintain good quality in response to changing radio conditions. In practice, a fading margin of typically [3 dB - 6 dB] should be introduced to avoid quality variations (see subclause 6.3.4). With this margin, consistent quality should be maintained although possibly at the expense of some loss of capacity enhancement (more channels forced to full-rate). The precise trade-off will not be known until AMR solutions are tested under realistic radio conditions. While this remains an issue for further study, it is not seen as a particular risk factor.
+
+On the other hand, the actual transmission rate of the in-band side information depends on the protocol used to convey the information. This could imply spreading the information on subsequent frames to save transmission bits, but at the expense of an additional delay in the control loop. A constraint to the signaling rate is due to the DTX operation that switches off the transmitter. Although a frequent signaling of the side information is an essential requirement for AMR operation, this has not to increase the channel activity such that to undermine the effectiveness of DTX.
+
+The requirements of the channel metric itself are discussed in subclause 6.3.3.
+
+### 6.3.2 Channel mode
+
+The execution of channel mode handovers should be identical to conventional intra-cell handovers although the algorithm for their initiation will be different. The frequency of such handovers should be restricted because of the quality degradation (due to frame stealing for signaling) and more significantly, the load on the BSC processor, associated signaling and possible consequential re-packing. Moreover, the channel mode selection algorithm should be integrated into the radio resource algorithm (see subclause 6.3.6). The channel mode control will most likely be incorporated into the radio resource algorithm and the frequency of AMR handovers controlled by means of Hysteresis etc.
+
+The impact of restricting handovers is that the quality in AMR HR mode could be impaired (since it could be operating outside its intended limits) or the capacity would be reduced, if in FR mode. It is not evident at this time how often handover restrictions would come into play nor how significant would be its impact on performance. Evaluations of a very limited range of actual calls using a simple channel mode algorithm (based on RxLev and RxQual) showed that many calls require no handovers while others require many. These results suggest that average handover rate could be doubled as a result of AMR operation and some calls may have fewer AMR handovers than ideal.
+
+### 6.3.3 Channel metrics (accuracy, update rate)
+
+The AMR link adaptation algorithm will be based on a channel metric, such a metric being representative of the speech quality as perceived by the user. It is anticipated that that metric will use the estimated residual error rate available from the output of the channel decoder and a number of other factors to assist in assessing the trend of the error rate. These may include the burst wise RxLev, the BFI and information from the equalizer but also system information such as DTX activation and frequency hopping activation. This information can be vector quantized to provide information of the position on a performance surface for the codec and the trend of channel quality, i.e. improving or degrading. The performance surface is created through characterizing the subjective quality of the codec as perceived by the customer against the residual error rate.
+
+Inputs made to SMG-11 have shown how the different codec rates can be chosen according to an averaged residual error rate and deliver acceptable speech quality under simplifying assumptions.
+
+The AMR codec will operate and be controlled over a wide range of C/I conditions. In full-rate mode, it will be possible to operate at very bad error conditions corresponding to C/I values worse than 4 dB (at the channel equalizer). In half-rate mode, G.728 quality is only expected at C/I values in excess of [18 dB]. Best performance will only be achieved by selecting the codec mode matching the channel condition.
+
+It is also critical that the metric is accurate since if the wrong codec mode is selected, the quality will be reduced undermining one of the basic principles of AMR.
+
+It is assumed that the channel metric will form part of the candidate's solution.
+
+### 6.3.4 Channel dynamics, effects on performance
+
+As seen above (subclause 6.4.1), the codec mode can be changed to track the radio signal dynamics with time constants as short as [100 msec]. Assuming that the codec mode adaptation algorithm is based on a comparison between the channel metric and a set of thresholds, the decision thresholds should count the codec performance crossing point and allow for a "fading" margin. Such a margin should be chosen to take into account fast variations of the error rates and hence the correlation time of the channel dynamic to avoid Ping-Pong effects. On these time-scales, the signal dynamics are dominated by Rayleigh fading although under some fast moving conditions, shadow fading can also come into play as far as the useful signal is concerned, the same dynamic applying also to the interferers. Measurements and simulations of the radio channel suggest that a margin of [?? dB] should be allowed. The exact margins will have to be fine-tuned once AMR systems have been developed and operated in real radio environments.
+
+The effect on performance of allowing for this margin is estimated in subclause 6.3.
+
+### 6.3.5 Location of codec mode and channel mode control
+
+#### Channel mode
+
+As the control of the AMR channel mode will have to be integrated with the Radio Resource algorithm, it is assumed that they will be co-located in the BSC or distributed between the BTS and BSC. This combined algorithm will use the existing channel measurement reports, RxLev and RxQual and the new channel metric yet to be defined.
+
+#### Codec mode
+
+Since the additional channel measurement reports for AMR will be transmitted in-band, there are several alternatives for the location of the codec mode control and the associated transmission of measurement reports and mode commands. These have been reviewed and the recommended approach is that:
+
+- codec mode control relating to capacity or radio link quality should be located in the network (BSS);
+- MS can autonomously select the codec mode of the up-link on the basis of speech source content (e.g. background noise); however, the network should have the option to e.g. override the MS preferred selection or restrict the range of selectable modes.
+
+The first point is seen as important because it allows the flexibility to upgrade the control algorithms of both the up- and down-links retrospectively. However, this may imply an increase of the data to be exchanged between the MS and the BTS when compared to solutions where no metric-related data are exchanged. Advantages were also shown in using a scheme where the control is distributed between the MS and BSS. However, unless very clear advantages over the centralized approach are demonstrated, the centralized approach will become the firm requirement at the start of the development.
+
+The reason for emphasizing source-controlled selection in the MS is that it is more difficult to achieve good quality with background noise, especially at low codec bit-rates. Selecting the codec mode locally at the MS allows good quality to be maintained with background noise, provided that the radio conditions allow a possible increase of the source bit-rate, without unnecessary reporting to the network. When operating in the HR channel mode, switching to the FR channel mode may be necessary to achieve good quality with background noise.
+
+#### Transmission of measurement and control data
+
+Channel quality information will need to be transmitted via an in-band signaling channel over-the-air with suitable protection (in the MS to BSS direction only for the centralized control). Such quality information can be assumed to represent an intermediate stage in the computation of the metric, obtained by processing of the in-band information and potentially other system parameters. It is believed that a good trade-off can be reached between the bit rate of the implied in-band signaling, including channel protection, and the speech coding bit rate.
+
+As well as transmitting channel quality or control data in-band, it has also been proposed to use frame stealing flags. This would allow greater capacity on the radio interface for the transmission of speech data and channel protection.
+
+### 6.3.6 Radio resource allocation
+
+The existing resource allocation strategies applied to Full Rate (or EFR) codecs combined with the Half Rate codecs, or a fortiori Full rate only codecs, will have to be revisited with the introduction of the AMR, especially when handovers between Half Rate and Full Rate modes are allowed. Indeed, in contrast to the already difficult case of coexistence of Half Rate and Full Rate traffic channels, the channel mode can be modified during the call based on the channel quality estimates.
+
+With AMR, the resource allocation strategy and the channel mode adaptation have to be coordinated such that the channel mode and the quality provided by the allocated resource are well paired. The objective is to reach the best trade-off between the carried traffic and the quality of the call.
+
+Limitations will arise due to avoid Ping-Pong as well as too numerous channel mode changes (i.e. AMR handovers). Otherwise extensive use of layer 3 signaling will be required and this degrades the call (speech interruption) in addition to loading up the BSC. An important side effect of these limitations is that it decreases the capacity gain from the AMR. It is currently difficult to evaluate this decrease as the exact effect will depend on the AMR handover algorithm which is manufacturer specific in a similar way to intra-cell handover.
+
+## 6.4 Support of other features
+
+### 6.4.1 TFO
+
+One example of a tandem free configuration is shown in figure 6.4.
+
+![Figure 6.4: Mobile to mobile communication link diagram. The diagram shows a mobile station (MS) on the left connected to a Channel decoder, which is connected to an Abis interface. The Abis interface connects to a TRAU (Traffic Rate Adaptation Unit) and an IFQ (Interfacial Queue). The TRAU and IFQ are connected to another Abis interface, which connects to another TRAU and IFQ. This second TRAU and IFQ are connected to a Channel encoder, which is connected to another mobile station (MS) on the right. The diagram illustrates a tandem-free (TFO) configuration where the speech data is passed through the network without being re-encoded at the intermediate TRAU units.](171115f072e42b379238ed0dd438e9d7_img.jpg)
+
+Figure 6.4: Mobile to mobile communication link diagram. The diagram shows a mobile station (MS) on the left connected to a Channel decoder, which is connected to an Abis interface. The Abis interface connects to a TRAU (Traffic Rate Adaptation Unit) and an IFQ (Interfacial Queue). The TRAU and IFQ are connected to another Abis interface, which connects to another TRAU and IFQ. This second TRAU and IFQ are connected to a Channel encoder, which is connected to another mobile station (MS) on the right. The diagram illustrates a tandem-free (TFO) configuration where the speech data is passed through the network without being re-encoded at the intermediate TRAU units.
+
+**Figure 6.4: Mobile to mobile communication link**
+
+TFO mode can be operated only if both mobile links in a mobile-to-mobile direction (e.g. up-link MS-A to network and downlink, network to MS-B) use the same speech coding bit-rate and algorithm. In principle this does not imply that the same *channel mode* has to be used, but can be achieved only if the AMR decoder is capable of operating at the same source rates for both FR and HR *channel modes*.
+
+Several options are possible to deal with the TFO management when combined with AMR.
+
+However, for AMR, the fact that the codec rates are varied, sometimes rapidly, presents special difficulties not previously encountered. Alternative approaches to this problem have been considered but the optimum method will demand detailed evaluation outside of the scope of the Study Phase.
+
+Nevertheless it was identified that at least the BTS would have to be informed whether a call is TFO or not. In consequence provisions must be taken to convey such an information between the TRAU and the BTS.
+
+Furthermore depending on the specific solution for the TFO scheme precautions may have to be taken in the basic AMR, e.g. the codec types designed for HR mode may have also to be adapted for the TCH/F.
+
+Taking all these considerations into account, it is still felt that the implementation of TFO for AMR is feasible.
+
+### 6.4.2 DTX
+
+For the same reasons as for the other GSM codecs, AMR should support DTX for which VAD and comfort noise algorithms will be needed.
+
+One concern is that if conventional DTX is invoked, the frequency of in-band channel measurement reports will be severely reduced. This could be offset by transmitting SID frames more frequently. This may also provide higher quality of the reproduced background noise. Different ways of implementing AMR DTX operation which retain most of the DTX gains are conceivable, possibly using lower transmission power.
+
+How the channel measurements are to be reported during DTX will be at the discretion of the codec proponent. However, the restrictions and their significance need further evaluation.
+
+This needs further study and currently represents a risk.
+
+### 6.4.3 Power control
+
+The availability of an accurate channel metric which is provided more frequently than RxLev could in principle allow power control to be exercised more precisely and rapidly than at present. This should enhance the advantages of reduced interference and longer battery life. However, it could also have the effect of reducing the C/I distribution (fewer calls at high C/I) and potentially constricting the range of operation of the AMR codec. This would reduce the capacity and quality gains of AMR operation.
+
+A separate point is that there may also be interactions between a rapidly changing power control and codec modes. To counter this, there would be advantages to integrating the two into a common algorithm. In the shorter term, there should not be any conflicts if the existing power control methods are combined with the short time constants of codec mode control.
+
+This area requires further study but is only seen as a minor risk.
+
+### 6.4.4 Handover
+
+In a similar way to power control, the new channel metric should also allow (conventional) handovers to be controlled more precisely since the metric will give a more accurate measure of channel quality and over a wider range of C/I than is possible with RxQual. This is only highlighted here as an advantage and has no bearing on the feasibility of AMR.
+
+### 6.4.5 8 and 16 kbit/s A-ter sub-multiplexing
+
+#### a) Full-rate mode
+
+The maximum source coding rate for full-rate mode (using 16 kbit sub-multiplexing) is about ?? kbps which is sufficient for the highest expected AMR rate even with the inclusion of some channel protection (as for EFR).
+
+#### b) Half-rate mode
+
+The existing HR codec can be transmitted on the A-ter interface using 8 kbps instead of 16 kbps sub-multiplexing thereby doubling transmission capacity. Operators see this as a useful feature and it is desirable that this is also available for HR mode of the AMR codec. This has been evaluated.
+
+The maximum source coding rates that can be supported on the A-ter interface will depend on the precise data formatting and signaling schemes. According to the compromises selected, this rate is estimated to lie between 6,5 kbps and 7,5 kbps, although the higher figure would require significant compromises in terms of backward compatibility with the existing TRAU frame formats leading to dedicated TRAU for AMR or new TRAU frames for existing codecs. Codec tests have also suggested that the bit-rates needed to achieve G.728 quality in HR mode is likely to be close to 8 kbps. This implies that to achieve the AMR target quality in HR mode, a sub-multiplexing rate higher than 8 kbps may be necessary.
+
+A new proposal was discussed based on 6:1 multiplexing (instead of 4:1 or 8:1) which would support an 8kbs source coding rate. However, this would be most applicable when most channels are AMR rather than a mixture of the other GSM codec types and is seen as a longer term solution. Nonetheless, it remains a potentially attractive solution. As the approach is new and raises a number of issues, it is recommended the approach be studied further.
+
+In the shorter term, attention is focused on 8 kbps and 16 kbps sub-multiplexing [which can be mixed – *check*]. It is probable that there will have to be at least two codec modes at HR, one for high C/I (e.g. > 18 dB) and one for low C/I. Since codec mode changes can occur rapidly and switching between 8 kbps and 16 kbps sub-multiplexing will cause quality degradations, it is anticipated that a fixed sub-multiplexing rate will have to be used for HR mode. Therefore to support 8 sub-multiplexing, the HR codec mode may have to be restricted to the lower source coding rate in HR mode, significantly limiting the quality and value of AMR. Nonetheless, as some operators may need this flexibility under certain circumstances, it is recommended that at least one codec mode in HR is provided which supports 8kbs sub-multiplexing.
+
+Recommendation:
+
+- no constraint applied on the upper limit of the source codec bit-rate in HR mode;
+- at least one source coding bit-rate in HR mode to be consistent with 8 kbps sub-multiplexing;
+- study potential for 6:1 or similar compression scheme as a longer term solution.
+
+## 6.5 Wideband service option
+
+The feasibility of adding a special mode to AMR, which would support a wideband speech service (e.g. 7 kHz), has been assessed but many aspects have not been resolved due to lack of time. The broad question of whether to add a wideband mode to AMR was the subject of considerable discussion but there were conflicting options. Nonetheless, there is agreement that the AMR program should not be delayed for the sake of introducing a wideband mode. The issues are summarized in a separate liaison statement to SMG in which SMG are requested to decide how the development of a wideband service should proceed.
+
+Some of the main points are identified below:
+
+- a wideband service would give a substantial quality uplift over narrowband and there is foreseen to be a market for mobile-to-mobile wideband users (or mobile-to-fixed), although the service will initially be restricted by the number of users having the necessary wideband terminals;
+- noting the need to avoid the proliferation of GSM codec standards, including wideband on AMR gives the best opportunity to deliver a wideband capability in the near term;
+- a wideband mode may be accommodated within the Release 1998 AMR development program by only testing it in the Qualification Phase and then giving preference to AMR candidates, which include a wideband option, which meets the performance specification. The wideband mode would be given lower priority than narrowband. This approach has not yet been agreed by SMG11 as workable and needs to be reviewed and elaborated;
+- there are also serious concerns that adding wideband to narrowband AMR adds risk to the program due to the additional testing and selection tasks and reduces the chances of meeting the Release 1998 deadline;
+- it has not been established that the wideband performance capability achievable with a single TDMA timeslot (i.e. 13 kbps approx.) will be adequate for a commercially competitive wideband service. This is substantiated by the recent failure of any of the candidates to meet the performance targets for an ITU-T 16kbs wideband speech codec under certain conditions;
+- there exist examples of wideband speech codecs with bit-rates in the range 12 kbps to 13 kbps, which show promising performance.
+
+# --- 7 Requirements specification
+
+The target performance requirements for the AMR codec was set out in the report SQSG presented to SMG#20 in October 1996 (see Tdoc SMG 447/96). These requirements have been reviewed and in the light of feasibility assessments made during the Study Phase (see subclause 6.1.1), a revised requirement specification has been produced (see annex C). This is more complete and precise to enable the candidate codecs to be properly developed, tested and selected. Some of the targets have also been modified in the light of assessments of the performance that can practically be achieved. These concern mainly the performance in HR mode under medium error conditions and the performance in the presence of background noise.
+
+Time has not allowed the requirements to be defined and agreed in respect of the performance under dynamic conditions. This work is in progress but is not ready to be approved. These requirements will have to be approved by SMG11 and frozen for the start of the Qualification Phase in November 1997.
+
+# --- 8 Implementation factors
+
+The main logical entities in the network and MS that will need to be upgraded to support AMR are identified in annex D.
+
+The costs of implementation of the upgrades to existing networks will depend on particular manufacturer's implementations and no attempt has been made to estimate them here.
+
+# --- 9 Codec development and selection
+
+## 9.1 Test and selection methodologies
+
+The candidate AMR codecs will be tested by a combination of static and dynamic tests. For the static tests, conventional, well-established methods will be used to evaluate each of the codec modes in clear, error conditions, with and without background noise under specific, static radio conditions (including Rayleigh fading, excluding shadow fading). In addition, the effects of switching between codec modes (for a given channel mode) will be tested by forcing rapid codec mode changes.
+
+The dynamic tests in contrast will require completely new test methodologies. The purpose of these tests is to evaluate the performance of complete AMR system, including the codec adaptation system, in response to dynamic radio conditions. This requires a system simulator (see subclause 9.3) and error patterns corresponding to a widely varying
+
+radio path. These tests will evaluate the performance of codec mode adaptation in the absence of channel mode changes. New subjective test procedures will also be necessary evaluate and score the performance. The reference condition for such tests will be existing codec standards.
+
+The dynamic test methodology and the system simulator is in the process of being formulated.
+
+## 9.2 Asymmetry of up and down links
+
+The test methodology for static and dynamic testing needs to recognize the asymmetry of the in-band signaling in the uplink and downlink and the recommended approach is outlined below.
+
+### Assumptions
+
+It is assumed that for a given codec mode, the algorithm and bit rate of the speech codec will be identical for the uplink and downlink (note that this does not imply that the uplink and downlink must operate in the same mode simultaneously).
+
+### Static tests
+
+If, for a given mode, there is a difference in the net channel coding rate of the speech between the uplink and downlink (i.e. after taking in-band signaling bits into account), the link with the least protected speech bits will be tested.
+
+In static tests involving bit errors and mode switching, the channel coding will be included in the speech processing stages. However, the impact of bit errors in the signaling channel will be ignored; the codec mode will be determined only by the experimental condition, i.e. it will be fixed or switched at a pre-determined rate.
+
+### Dynamic tests
+
+In dynamic tests, each experimental condition will be tested for both the uplink and downlink directions. The signaling system used for mode adaptation will be included in the speech processing stages, with the effect of bit-errors on the signaling bits incorporated. If signaling bits are external to the traffic channel, e.g. frame stealing flags, the effect of errors in these bits must also be simulated.
+
+## 9.3 Speech traffic channel simulation model
+
+Due to the need to take into account the adaptation concept of AMR, the traffic channel simulation model for AMR has to consider both transmission links simultaneously. The high-level block diagram of such simulator is reported in figure 9.1 referring to uplink configuration.
+
+![Block diagram of the AMR speech traffic channel simulation model. The diagram shows the flow of data and control signals through various processing blocks. At the top, an 'Input Signal' enters an 'AMR encoder' block. The encoder also receives 'HR/FR mode' and 'Side information for codec mode adaptation'. It outputs a 'Data stream' and an 'HR/FR flag' to an 'EID' block. The 'EID' block also receives 'In-band signalling' and 'Soft-chip errors (uplink)' from an 'Error patterns' block. It outputs a 'Data stream' and an 'HR/FR flag' to an 'AMR decoder' block. The 'AMR decoder' outputs an 'Output Signal' and a 'Delay' signal. The 'Delay' signal is fed into an 'AMR signalling encoder' block, which also receives 'DTX pattern' and 'Side information for codec mode adaptation'. The 'AMR signalling encoder' outputs 'In-band signalling' to an 'EID' block. This 'EID' block outputs 'In-band signalling' to an 'AMR signalling decoder' block. The 'AMR signalling decoder' outputs 'Side information for codec mode adaptation' to the 'AMR encoder'. The 'Error patterns' block also receives 'Rx qual' and 'Rx lev' from the 'AMR decoder' and outputs 'Soft-chip errors (downlink)' to the 'EID' block.](17008b9a61bfe35b1e2c8fe2fbd1d801_img.jpg)
+
+Block diagram of the AMR speech traffic channel simulation model. The diagram shows the flow of data and control signals through various processing blocks. At the top, an 'Input Signal' enters an 'AMR encoder' block. The encoder also receives 'HR/FR mode' and 'Side information for codec mode adaptation'. It outputs a 'Data stream' and an 'HR/FR flag' to an 'EID' block. The 'EID' block also receives 'In-band signalling' and 'Soft-chip errors (uplink)' from an 'Error patterns' block. It outputs a 'Data stream' and an 'HR/FR flag' to an 'AMR decoder' block. The 'AMR decoder' outputs an 'Output Signal' and a 'Delay' signal. The 'Delay' signal is fed into an 'AMR signalling encoder' block, which also receives 'DTX pattern' and 'Side information for codec mode adaptation'. The 'AMR signalling encoder' outputs 'In-band signalling' to an 'EID' block. This 'EID' block outputs 'In-band signalling' to an 'AMR signalling decoder' block. The 'AMR signalling decoder' outputs 'Side information for codec mode adaptation' to the 'AMR encoder'. The 'Error patterns' block also receives 'Rx qual' and 'Rx lev' from the 'AMR decoder' and outputs 'Soft-chip errors (downlink)' to the 'EID' block.
+
+Figure 9.1: Block diagram of the AMR speech traffic channel simulation model
+
+The error patterns are assumed to carry also the information on RxQual and RxLev. The backward channel (downlink in this case) is used to take into account the effect of delay and channel errors on the in-band signaling data that are used to take decision on the codec mode bit-rate. The HR/FR channel mode flag is used to simulate AMR handovers. It is also used in the EID to select the proper error pattern.
+
+Details of the definition of the various blocks as well as specification of interfaces are reported in annex E.
+
+## 9.4 Schedule
+
+In response to the terms of reference of the AMR project, SMG11 and SMG2 have assessed the feasibility of a schedule that would deliver the AMR specifications in time for Release 1998. The schedule has to include the following main activities:
+
+- pre-qualification phase: Performance requirements, test plans, static and dynamic error patterns, system simulator specification, design constraints;
+- qualification phase testing;
+- optimization;
+- selection testing;
+- production of specifications followed by period of stabilization.
+
+A draft schedule for the AMR codec testing, selection and standardization is shown in annex F. This incorporates the standardization of the associated control system and signaling. This schedule is itself very aggressive. Since it was produced, SMG2 have indicated that more time will be needed to produce the error patterns which are not expected to be available until December 1997 (static patterns) and March 1998 (dynamic patterns). The schedule therefore needs to be reviewed urgently and at the time of writing, it is not clear that Release 1998 can be achieved.
+
+Since a Release 1998 schedule will carry a high degree of risk, the Qualification Phase of testing includes dynamic as well as static tests to reveal at the conclusion of this phase [March 1998] the extent to which the candidate solutions meet the performance requirements. If they pass or come close, the selection phase will proceed (possibly with a short optimization phase). Otherwise, time will be allowed for an extended optimization period in which case, AMR would probably be postponed to Release 1999.
+
+## 9.5 Programme management
+
+Prime responsibility for the AMR development will be held by SMG11 with SMG2 and SMG3 having secondary responsibilities.
+
+The proposed Work Item description is contained in Annex G.
+
+# --- 10 Open issues and risks
+
+The feasibility study has evaluated to a greater or lesser degree the main aspects of the function and operation of the AMR codec. Preliminary evaluations as well as some advanced codec developments and testing have shown to a satisfactory level of confidence that the performance requirements are achievable. However, there remain a few areas that present some risks to the successful realization and application of AMR.
+
+| <b>Issue</b>                                                   | <b>Impact on AMR performance</b>                                                                                                                                               | <b>Risk levels assessed by SMG2 and SMG11</b> | <b>Risk assessment.</b>                                                                                                                                |
+|----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Speech quality                                                 | The performance requirements in HR mode under error and background noise conditions have been relaxed to be realistic.                                                         | Medium                                        | The benefits are still significant even with the relaxation.                                                                                           |
+| Channel and mode adaptation algorithms                         | The effectiveness of these algorithms is crucial to good AMR operation. Initial implementations may not realize the full potential of AMR. (Cf. Handover algorithms).          | Medium                                        | Performance will improve with experience with real networks.                                                                                           |
+| Impact of actual C/I distribution on capacity/quality benefits | Performance will depend on the actual C/I distribution. This has proved to be difficult to estimate reliably and the C/I forecasts produced so far have shown wide variations. | Medium                                        | The main performance benefits (see Section 6.2.2.) have been estimated on the basis of the lower (i.e. more pessimistic) C/I distributions.            |
+| Provision of accurate channel metric over wide C/I range       | If accuracy falls below the target, the non-optimum codec mode may be selected, significantly reducing the quality and capacity benefits.                                      | SMG2:<br>high<br>SMG11:<br>medium             | Proposals for the complete control mechanism including the channel metric have shown that viable solutions can be achieved.                            |
+| Tracking of rapid signal dynamics by control system            | This has been estimated but its impact cannot be properly assessed until sophisticated simulation tools or trial results become available.                                     | SMG2:<br>medium<br>SMG11:<br>low              | If the estimates have been optimistic, an additional safety margin should be allowed for.                                                              |
+| TFO                                                            | Finding an effective TFO solution for AMR may require significant effort.                                                                                                      | Medium.                                       | Effective solutions will demand detailed investigations. Although highly desirable, AMR can operate without TFO.                                       |
+| Novelty and complexity of AMR                                  | The AMR concept is introducing new methods not previously attempted.                                                                                                           | Medium                                        | The novelty of these techniques is also the reason for the advantages of AMR. Without the additional complexity, the advantages would not be realized. |
+
+# 11 Recommendations
+
+On basis of the performance benefits and risks highlighted above, the following recommendations are submitted to SMG for approval:
+
+- initiate a program to develop, test, select and specify AMR speech and channel codecs together with related features such as VAD, DTX and comfort noise generation. The associated control, signaling procedures and TFO should also be developed and specified;
+- an acceptable and workable time-plan should be agreed by SMG11 and SMG2 as soon as possible after SMG#23 with the priority of meeting Release 1998 deadlines;
+- approve the performance requirement specification in annex C;
+- decide on whether a wideband mode should be included in AMR (see separate liaison statement);
+
+- approve the allocation of 400 kECU for the purposes of codec testing;
+- approve the Work Item Description contained in annex G.
+
+# Annex A: Terminology
+
+The terminology used in the present document and recommended for other work on AMR is listed below.
+
+|                                        |                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>Adaptive Multi-Rate (AMR) codec</b> | Speech and channel codec capable of operating at gross bit-rates of 11.4 kbps (" <i>half-rate</i> ") and 22.8 kbps (" <i>full-rate</i> "). In addition, the codec may operate at various combinations of speech and channel coding ( <i>codec mode</i> ) bit-rates for each <i>channel mode</i> .                                                                                                                                                   |
+| <b>AMR handover</b>                    | Handover between the <i>FR</i> and <i>HR channel modes</i> to optimize AMR operation.                                                                                                                                                                                                                                                                                                                                                               |
+| <b>Bit-rate change</b>                 | Change of the <i>codec mode</i> bit-rates for a given (HR/FR) <i>channel mode</i> .                                                                                                                                                                                                                                                                                                                                                                 |
+| <b>Channel mode</b>                    | Half-rate or full-rate operation                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| <b>Channel mode adaptation</b>         | The control and selection of the (FR or HR) <i>channel mode</i> .                                                                                                                                                                                                                                                                                                                                                                                   |
+| <b>Channel Re-packing</b>              | Re-packing of HR (and FR) radio channels of a given radio cell to achieve higher capacity within the cell. Controlled by in-band signaling (future) or out-of-band signaling (today). May influence the A-bis / A-ter interface.                                                                                                                                                                                                                    |
+| <b>Codec mode</b>                      | For a given <i>channel mode</i> , the bit partitioning between the speech and channel codecs.                                                                                                                                                                                                                                                                                                                                                       |
+| <b>Codec mode adaptation</b>           | The control and selection of the <i>codec mode</i> bit-rates. Normally, implies no change to the <i>channel mode</i> .                                                                                                                                                                                                                                                                                                                              |
+| <b>Conventional handover</b>           | Inter- or intra- cell handover performed for non-speech coding reasons.                                                                                                                                                                                                                                                                                                                                                                             |
+| <b>Embedded Speech Codecs</b>          | <p>Family of speech codecs based on a "Core Codec" where the next "higher" codec fully includes (embeds) the next "lower" codec. Decoding of a "lower" codec mode is always possible without loss in quality below the quality of that lower codec mode. As a consequence higher codec modes can always be "stripped off" to lower codec modes on the way from encoder to decoder.</p> <p>Embedded Speech Codecs are naturally rate compatible.</p> |
+| <b>Error Patterns</b>                  | Result of offline simulations (or measurements?) stored on files. To be used by the "Error Insertion Device" to model the radio transmission from the output of the channel decoder and interleaver to the input of the deinterleaver and channel decoder.                                                                                                                                                                                          |
+| <b>Error Insertion Device</b>          |                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| <b>Error Profiles</b>                  | Error Patterns plus additional information like RXQual, RxLev etc.                                                                                                                                                                                                                                                                                                                                                                                  |
+| <b>Full-rate (FR)</b>                  | Full-rate channel or <i>channel mode</i>                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>Gross bit-rate</b>                  | The bit-rate of the <i>channel mode</i> selected (22.8 kbps or 11.4 kbps).                                                                                                                                                                                                                                                                                                                                                                          |
+| <b>Half-rate (HR)</b>                  | Half-rate channel or <i>channel mode</i>                                                                                                                                                                                                                                                                                                                                                                                                            |
+| <b>In-Band Signaling</b>               | Signaling for DTX, Link Control, Channel and codec mode modification, etc. carried within the traffic channel by reserving or stealing bits normally used for speech transmission. Maybe on the radio channel or other channels inside the fixed network (e.g. A-bis, A-ter, A).                                                                                                                                                                    |
+
+|                                      |                                                                                                                                                                                                                                                                                                                                   |
+|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| <b>ISDN Quality</b>                  | Speech quality achieved on wireline telephones with a full duplex transparent digital connection over 64 kbit/s links.                                                                                                                                                                                                            |
+| <b>Out-of-Band Signaling</b>         | <p>Signaling on the GSM control channels to support link control. May be on the radio channel or other channels inside the fixed network (e.g. A-bis, A-ter, A).</p> <p>Note: Out-Of-Band Signaling on the radio channel sometimes "steals" capacity from the speech traffic channel (FACCH) thus creating speech distortion.</p> |
+| <b>Rate compatible speech codecs</b> | Speech codecs (typically belonging to a family) which can be modified in net bit rate (typically on a frame by frame basis) without speech quality degradation below the quality of the worst mode.                                                                                                                               |
+| <b>RXLEV</b>                         | GSM defined Receive Carrier Level Estimates, averaged over 480 ms                                                                                                                                                                                                                                                                 |
+| <b>RXQual</b>                        | GSM defined Receive Quality Estimates, averaged over 480 ms                                                                                                                                                                                                                                                                       |
+| <b>Speech Codec Family</b>           | <p>All speech coding algorithms which belong to an algorithm family.</p> <p>Typically they have common architectures and can share program code.</p>                                                                                                                                                                              |
+| <b>Toll Quality</b>                  | <p>Speech quality normally achieved on modern wireline telephones.</p> <p>Synonym with "ISDN quality" in most western countries.</p>                                                                                                                                                                                              |
+| <b>Wireline quality</b>              | Speech quality provided by modern wireline networks. Normally taken to imply quality at least as good as that of 32kbs G.726 or G.728 codecs.                                                                                                                                                                                     |
+
+## Acronyms
+
+|         |                                                                                   |
+|---------|-----------------------------------------------------------------------------------|
+| ACR     | Absolute Category Rating                                                          |
+| AMR     | Adaptive Multi-Rate                                                               |
+| C/I     | Carrier-to-Interferer ratio                                                       |
+| CNI     | Comfort Noise Insertion                                                           |
+| DCR     | Degradation Category Rating                                                       |
+| DSP     | Digital Signal Processor                                                          |
+| DTMF    | Dual Tone Multi Frequency                                                         |
+| DTX     | Discontinuous Transmission for power consumption and interference reduction       |
+| EFR     | Enhanced Full Rate                                                                |
+| EID     | Error Insertion Device                                                            |
+| ETSI    | European Telecommunications Standards Institute                                   |
+| FR      | Full-rate                                                                         |
+| FH      | Frequency Hopping                                                                 |
+| G.726   | ITU 16kbs/24kbs/32kbs ADPCM codec                                                 |
+| G.728   | ITU 16kbs LD-CELP codec                                                           |
+| GSM     | Global System for Mobile communications                                           |
+| HR      | Half-rate                                                                         |
+| IRS     | Intermediate Reference System, No IRS= rather flat                                |
+| ITU-T   | International Telecommunication Union – Telecommunications Standardization Sector |
+| MNRU    | Modulated Noise Reference Unit                                                    |
+| MOS     | Mean Opinion Score                                                                |
+| MS      | Mobile Station                                                                    |
+| OVL     | Overload point                                                                    |
+| PCM     | Pulse Code Modulation                                                             |
+| Q       | Speech-to-speech correlated noise power ratio in dB                               |
+| qdu     | quantization distortion unit                                                      |
+| RPE-LTP | Regular Pulse Excited codec with Long Term Prediction                             |
+| SID     | Silence Descriptor                                                                |
+| SMG     | Special Mobile Group                                                              |
+| SNR     | Signal to Noise Ratio                                                             |
+| TCH-HS  | Traffic Channel Half rate Speech                                                  |
+| TCH-FS  | Traffic Channel Full rate Speech                                                  |
+| TDMA    | Time Division Multiple Access                                                     |
+| TFO     | Tandem Free Operation                                                             |
+| UPCM    | Uniform or Linear PCM                                                             |
+| VAD     | Voice Activity Detector                                                           |
+
+Error Patterns (EP0, EP1, EP2 and EP3):
+
+- EP0 without channel errors;
+- EP1 C/I=10 dB; 5 % Gross BER (well inside a cell); TU3, Ideal Frequency Hopping
+- EP2 C/I= 7 dB; 8 % Gross BER (at a cell boundary);
+- EP3 C/I= 4 dB; 13 % Gross BER (outside a cell).
+
+# --- Annex B: Application scenarios
+
+With the intrinsic flexibility of the AMR system, it will be possible to customize the application of the codec to meet specific network and service needs. Some of the potential application scenarios are identified below (in no particular order) together with the advantages offered and the types of networks to which they may be suited.
+
+## 1) Full-rate only; High quality over full range of channel errors.
+
+This provides improved resilience to errors compared to GSM EFR so that when in call, the speech quality varies little with channel errors. It also provides significantly improved quality under marginal coverage conditions (e.g. at cell edge, coverage holes etc.).
+
+Some capacity advantage may also be derived from the improved resilience under low C/I conditions. May support tighter frequency re-use.
+
+Potential service applications: suitable for operators who do not need to increase capacity through half-rate operation but wish to offer the best speech quality possible to all users.
+
+## 2) Half-rate only; Improved quality over current HR codec.
+
+To gain maximum capacity advantage, the AMR codec can be operated in half-rate channel mode only. In this case, the AMR codec is likely to provide significant improvements in speech quality over the existing HR codec under low error conditions by using codec mode adaptation. Other improvements under background noise and tandeming conditions can also be expected.
+
+Potential service applications: suitable for operators who need the greatest capacity enhancement from half-rate operation, but who are also seeking quality improvements. Some loss of quality at high channel error rates and in background noise can be expected (but still better than the existing HR codec).
+
+## 3) Full- and Half-rate operation; simple HR/FR handover.
+
+In this case, handover between FR and HR channel modes will be supported but probably only using the current intra-cell HR/FR handover capabilities. Such handovers would not be expected to be frequent (e.g. less than [5] in a two-minute call). *[Check]*
+
+*AMR handover* will be controlled according to whether greatest emphasis is to be placed on quality or capacity enhancements.
+
+This will allow combined quality and capacity enhancements but the simple handover mechanisms may lead to some short-term variation of speech quality as the variations of the error rate on the half-rate channel may not be tracked sufficiently rapidly.
+
+Potential service applications: suitable for operators who want to combine speech quality and capacity improvements (less than that achievable through half-rate only operation).
+
+## 4) Full- and Half-rate operation; advanced HR/FR handover.
+
+In this case, an advanced handover scheme between FR and HR channel modes would operate. This may involve more handovers and the aim would be to "fine-tune" the selection of the FR and HR channel modes to obtain the best balance between capacity and quality. This may involve more handovers than 3) but as handovers themselves are a source of quality degradation, their number will still need to be restricted.
+
+The particular FR/HR algorithm (on the BSC) may be customized to meet the operator's specific needs.
+
+Subject to establishing the feasibility of this approach, this mode or operation should provide consistent high speech quality subject to only small variations in quality and an increase in capacity. The level of capacity improvement will depend on the FR/HR handover algorithm implemented.
+
+Potential service applications: suitable for operators who want to combine speech quality and capacity improvements (less than that achievable through half-rate only operation).
+
+# Annex C: Codec requirement specification
+
+## C.1 Static conditions
+
+This annex presents performance requirements and objectives for the speech quality of the GSM AMR system under static test conditions.
+
+The half-rate and full-rate channels will be assessed separately. For each channel the speech quality of the codec modes associated with that channel will be assessed over a range of C/I and background noise conditions to provide a 'family' of performance curves.
+
+Separate requirements and objectives are specified for clean speech and background noise. The type of the background noise, e.g. babble or vehicle, and signal-to-noise ratio (SNR) are specified in the associated subjective test plan.
+
+The requirements and objectives for the full-rate and half-rate traffic channels under static test conditions are specified in table 1. The following notes apply.
+
+- NOTE 1: 'Ideal case performance' assumes that optimum mode selection has occurred for the given channel, and is defined as the performance of the codec mode which provides the *best* subjective performance under the specified C/I and background noise condition.
+- NOTE 2: 'Worst case performance' assumes that the mode selection algorithm has made the poorest choice for the given channel, and is defined as the performance of the codec mode which provides the *worst* subjective performance under the specified C/I and background noise condition.
+- NOTE 3: Unless otherwise stated, the requirement shall be assumed to be 'not worse than'. In the case where two reference codecs are specified, the candidate codec must meet the stated requirement for both reference codecs.
+- NOTE 4: The 'not worse than' and 'better than' requirements will be interpreted statistically at the 95% confidence levels.
+
+**Table 1a: Clean speech requirements and objectives under static test conditions**
+
+| C/I       | Full-Rate Channel                    |                                    | Half-Rate Channel                    |                                    |
+|-----------|--------------------------------------|------------------------------------|--------------------------------------|------------------------------------|
+|           | Ideal case performance (requirement) | Worst case performance (objective) | Ideal case performance (requirement) | Worst case performance (objective) |
+| no errors | EFR no errors                        | G.728 no errors                    | G.728 no errors                      | FR no errors                       |
+| 19 dB     | EFR no errors                        | G.728 no errors                    | G.728 no errors                      | FR no errors                       |
+| 16 dB     | EFR no errors                        | G.728 no errors                    | G.728 no errors                      | FR at 10 dB                        |
+| 13 dB     | EFR no errors                        | G.728 no errors                    | FR at 13 dB                          | FR at 7 dB                         |
+| 10 dB     | G.728 no errors                      | EFR at 10 dB                       | FR at 10 dB                          | FR at 4 dB                         |
+| 7 dB      | G.728 no errors                      | EFR at 7 dB                        | FR at 7 dB                           |                                    |
+| 4 dB      | EFR at 10 dB                         | EFR at 4 dB                        | FR at 4 dB                           |                                    |
+
+**Table 1b: Background noise requirements and objectives under static test conditions**
+
+| C/I       | Full-Rate Channel                    |                                    | Half-Rate Channel                    |                                    |
+|-----------|--------------------------------------|------------------------------------|--------------------------------------|------------------------------------|
+|           | Ideal case performance (requirement) | Worst case performance (objective) | Ideal case performance (requirement) | Worst case performance (objective) |
+| no errors | EFR no errors                        | G.729 and FR no errors             | better than G.729 and FR no errors   | G.729 and FR no errors             |
+| 19 dB     | EFR no errors                        | G.729 and FR no errors             | better than G.729 and FR no errors   | G.729 and FR no errors             |
+| 16 dB     | EFR no errors                        | G.729 and FR no errors             | better than G.729 and FR no errors   | FR at 10 dB                        |
+| 13 dB     | EFR no errors                        | G.729 and FR no errors             | FR at 13 dB                          | FR at 7 dB                         |
+| 10 dB     | G.729 and FR no errors               | FR at 10 dB                        | FR at 10 dB                          | FR at 4 dB                         |
+| 7 dB      | G.729 and FR no errors               | FR at 7 dB                         | FR at 7 dB                           |                                    |
+| 4 dB      | FR at 10 dB                          | FR at 4 dB                         | FR at 4 dB                           |                                    |
+
+### Original SQSG performance benchmarks
+
+The performance benchmarks originally set by SQSG for AMR are reproduced below.
+
+#### Full-rate mode
+
+Speech quality, talker dependency, background noise<sup>1</sup> and tandeming:
+
+|     |               |
+|-----|---------------|
+| EP0 | EFR under EP0 |
+| EP3 | EFR under EP1 |
+
+#### Half-rate mode
+
+Speech quality, talker dependency, background noise and tandeming:
+
+|     |               |
+|-----|---------------|
+| EP0 | G.728         |
+| EP1 | EFR under EP1 |
+| EP2 | FR under EP2  |
+| EP3 | FR under EP3  |
+
+Complexity target for speech no higher than 8 times the complexity and channel codecs combined of the TCH-FS speech and channel codecs
+
+Other points that need to be checked for adaptability:
+
+- varying channel condition test to ensure that channel adaptive technique does not seriously degrade performance including when DTX is operated;
+- the ability for the coder to signal its need to be handed over to FR;
+- no annoying artifacts when changing channel modes.
+
+NOTE 5: The background noise specification should recognize realistic usage environments and the expected minimum noise differentiation performance (DELSM) of the MS.
+
+## C.2 Dynamic conditions
+
+*[In the process of being defined.]*
+
+# Annex D: AMR implementation requirements
+
+## D.1 Network
+
+The following table lists the basic network functions, which would be impacted by the introduction of AMR. The table also identifies whether a similar modification was required for the introduction of EFR.
+
+**Table D.1: Overview of the network modifications**
+
+| Device | Upgrade for AMR                                                                                                                                                                                                                                                                           |
+|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| BTS    | New Channel Codec,<br>In-band Transmission of metrics and signaling data,<br>Codec mode adaptation algorithm based on the characteristics of the radio channel,<br>DTX,<br>New TRAU frames,<br><i>Transmission to the BSC of information related to the quality of the radio channel.</i> |
+| BSC    | Radio resource algorithm to incorporate channel mode adaptation and enhanced channel re-packing                                                                                                                                                                                           |
+| TRAU   | New TRAU frames,<br>New Speech Codec,<br>Codec mode adaptation algorithm based on the characteristics of the input signal,<br><i>G.722 may be needed in case of wideband codec</i>                                                                                                        |
+| MSC    | Minor signaling extensions for e.g. handover, circuit pooling<br><i>In case of wideband extension of the ISUP might be necessary to identify that wideband can be used in both terminals.</i>                                                                                             |
+| OMC-R  | Configuration of the AMR codec (e.g. TCH/H only)                                                                                                                                                                                                                                          |
+
+The modifications in the network required for introducing the AMR will be dependent on the level of actual adaptation desired. As a matter of fact the AMR is a toolbox and thus does not oblige to implement all the features. This specific aspect allows a smooth introduction of the AMR in the sense that it can be done in several steps.
+
+A general comment is that much more functions of the network have to be modified. An attempt of listing the functions to be modified is provided in table YY. Hardware upgrades may be necessary especially for the first generation devices (BTS, BSC and TRAU).
+
+The OMC will have also to be modified if the operators want to take advantage of the high flexibility offered by the AMR.
+
+**Table D.2: Detailed list of network modifications**
+
+| <b>Generic Function</b>                                    | <b>Upgrade Required</b>                                                                                                                                                                                                                                                                        | <b>Equivalent upgrade required for EFR</b>                                                                       |
+|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| Speech Frame Coding                                        | Support of the multiple Half Rate and Full Rate Speech Codecs<br>Support of embedded In Band signaling                                                                                                                                                                                         | Only one new speech codec required for EFR                                                                       |
+| Voice Activity Detection                                   | Support of a new VAD algorithm(s) for the half rate and full rate modes of AMR                                                                                                                                                                                                                 | Only one new VAD algorithm for EFR                                                                               |
+| Ater                                                       | New TRAU frames<br>8 and 16 kbit/s sub-multiplexing<br>Increase of transmission means                                                                                                                                                                                                          | New TRAU frames<br>16 kbit/s sub-multiplexing                                                                    |
+| Codec Selection                                            | Processing of the RX In band signaling<br>Support of a dynamic codec selection on a frame basis based on the RX In Band signaling and possibly on the characteristics of the source signal                                                                                                     | Support of codec selection at call set up (Bearer Capabilities)                                                  |
+| Channel Coding                                             | Support of new channel coding for each codec                                                                                                                                                                                                                                                   | Same channel coding as the FR                                                                                    |
+| Interleaving                                               | Possible new interleaving schemes for some or all channel modes of AMR                                                                                                                                                                                                                         | Same as for the FR                                                                                               |
+| Stealing flag                                              | Possible extension of the stealing flag use to indicate the channel mode and/or carry some in band signaling                                                                                                                                                                                   | No modification of the stealing flag for the EFR                                                                 |
+| Channel Measurement                                        | Support of a new metric for an accurate evaluation of the propagation conditions                                                                                                                                                                                                               | No additional channel measurements for the EFR                                                                   |
+| Stealing Flag Extraction                                   | Possible exploitation of the stealing to determine the channel mode and/or recover some in-band signaling                                                                                                                                                                                      | Not needed                                                                                                       |
+| De-Interleaving                                            | Possible new De-interleaving schemes for some or all channel modes of AMR                                                                                                                                                                                                                      | Not needed                                                                                                       |
+| Channel Decoding                                           | Support of a new channel decoding mode for each codec                                                                                                                                                                                                                                          | Minor modifications of the TCH-FS channel decoder                                                                |
+| Speech Decoding<br>Bad Frame Handling<br>In Band Signaling | Support of a set of new speech decoding algorithms for the full rate and half rate modes of AMR<br>Possible new bad frame handling algorithms<br>Extraction of the In Band signaling                                                                                                           | Only one new speech decoding algorithm for EFR.<br>New bad frame handling needed for EFR.                        |
+| TX In Band signaling                                       | Generation of an In Band signaling message containing either measurement reports and/or downlink codec requirement and/or indication.                                                                                                                                                          | Not needed                                                                                                       |
+| Resource Management                                        | Possible impacted messages/procedures include:<br>Measurement Reports (to partially report the new metric on the SACCH)<br>System Information (to define the operation thresholds of the channel adaptation).<br>Channel re-packing must be implemented to achieve significant capacity gains. | Optimization of existing procedure                                                                               |
+| Call Control Layer 3                                       | Codec negotiation/selection at call set up (Bearer Capabilities)<br>Channel Mode indication in Assignment/Handover Command                                                                                                                                                                     | Codec indication at call set up (Bearer Capabilities)<br>Channel Mode indication in Assignment/Handover Commands |
+| Channel Mode adaptation                                    | The BSC manages the channel mode adaptation based on information received from the BTS.<br>More layer 3 messages per call. Processing power must be increased to maintain the number of Erlang managed by a BSC.                                                                               | Not needed                                                                                                       |
+| Power Control                                              | The Power Control may have to be modified in order to ensure a good coexistence with the Adaptation feature of the AMR (Ping-Pong effects must be avoided).                                                                                                                                    | Not needed                                                                                                       |
+| OMC                                                        | Configuration of the operation mode of the AMR                                                                                                                                                                                                                                                 | Not needed                                                                                                       |
+| Abis                                                       | Increase of the LAPD transmission capacity                                                                                                                                                                                                                                                     | Not needed                                                                                                       |
+
+## D.2 MS
+
+The following table lists the basic Mobile Station functions, which would be impacted by the introduction of AMR. The table also identifies whether a similar modification was required for the introduction of EFR. Note that it is assumed that the management of half rate channels is already supported by the MS and does not require any upgrade as a result of the introduction of AMR.
+
+The figure below presents a simplified architecture of a Mobile Station. The new functions or functions requiring an upgrade are framed by a double line.
+
+**Table D.3**
+
+| Generic Function                                           | Upgrade Required                                                                                                                                                                                             | Equivalent upgrade required for EFR                                                                              |
+|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
+| Speech Frame Coding                                        | Support of the multiple Half Rate and Full Rate Speech Codecs<br>Support of embedded In Band signaling                                                                                                       | Only one new speech codec required for EFR                                                                       |
+| Voice Activity Detection                                   | Support of a new VAD algorithm(s) for the half rate and full rate modes of AMR                                                                                                                               | Only one new VAD algorithm for EFR                                                                               |
+| Codec Selection                                            | Processing of the RX In band signaling<br>Support of a dynamic codec selection on a frame basis based on the RX In Band signaling and possibly on the characteristics of the source signal                   | Support of codec selection at call set up (Bearer Capabilities)                                                  |
+| Channel Coding                                             | Support of new channel coding for each codec                                                                                                                                                                 |                                                                                                                  |
+| Interleaving                                               | Possible new interleaving schemes for some or all channel modes of AMR                                                                                                                                       |                                                                                                                  |
+| Stealing flag                                              | Possible extension of the stealing flag use to indicate the channel mode and/or carry some in band signaling                                                                                                 |                                                                                                                  |
+| Channel Measurement                                        | Support of a new metric for an accurate evaluation of the propagation conditions                                                                                                                             |                                                                                                                  |
+| Stealing Flag Extraction                                   | Possible exploitation of the stealing to determine the channel mode and/or recover some in-band signaling                                                                                                    |                                                                                                                  |
+| De-Interleaving                                            | Possible new De-interleaving schemes for some or all channel modes of AMR                                                                                                                                    |                                                                                                                  |
+| Channel Decoding                                           | Support of a new channel decoding mode for each codec                                                                                                                                                        |                                                                                                                  |
+| Speech Decoding<br>Bad Frame Handling<br>In Band Signaling | Support of a set of new speech decoding algorithms for the full rate and half rate modes of AMR<br>Possible new bad frame handling algorithms<br>Extraction of the In Band signaling                         | New speech decoding algorithm for EFR<br>New bad frame handling algorithm                                        |
+| TX In Band signaling                                       | Generation of an In Band signaling message containing either measurement reports and/or downlink codec requirement and/or indication.                                                                        |                                                                                                                  |
+| Resource Management                                        | Possible impacted messages/procedures include:<br>Measurement Reports (to partially report the new metric on the SACCH)<br>System Information (to define the operation thresholds of the channel adaptation) |                                                                                                                  |
+| Call Control Layer 3                                       | Codec negotiation/selection at call set up (Bearer Capabilities)<br>Channel Mode indication in Assignment/Handover Command                                                                                   | Codec indication at call set up (Bearer Capabilities)<br>Channel Mode indication in Assignment/Handover Commands |
+
+![Block diagram of MS Architecture showing Transmit and Receive chains. The Transmit Chain includes Acoustic Parts, Sampling, Voice Activity Detection, Speech Frame Coding, Multiplexing, Channel Coding, Interleaving, Burst Generation, Encryption, Modulator, and Transmitter. The Receive Chain includes Receiver, Demodulator/Equalizer, De-Encryption, De-Interleaving, Channel Decoding, Demultiplexing, Speech Frame Decoding, Acoustic Echo Control, DAC, and Acoustic Parts. A central LAPDM block contains SMSCC, SSCC, CC, MM, and RR. A legend indicates 'Functions not likely to be modified' (white boxes) and 'New Functions or Functions likely to be modified' (shaded boxes).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg)
+
+**Transmit Chain**
+
+Microphone → Acoustic Parts → Sampling → Voice Activity Detection → Speech Frame Coding → Multiplexing → Channel Coding → Interleaving → Burst Generation → Encryption → Modulator → Transmitter → Antenna
+
+**Receive Chain**
+
+Antenna → Receiver → Demodulator/Equalizer → De-Encryption → De-Interleaving → Channel Decoding → Demultiplexing → Speech Frame Decoding → Acoustic Echo Control → DAC → Acoustic Parts → Microphone
+
+**Central Components**
+
+- LAPDM (containing SMSCC, SSCC, CC, MM, RR)
+- TX In Band Signaling
+- RX In Band Signaling
+- Sealing Flags
+- Training Sequence
+- Signaling Message
+- Speech Frame
+- Flags Extraction
+- Channel Measurement
+- RSQual
+- RSLoz
+- New Metric
+- Measurement Results
+
+**MS Architecture**
+
+MMI, SIM Control, External Ports, Power Mngt, Clock Mngt, Utilities
+
+**Legend:**
+
+- Functions not likely to be modified (White box)
+- New Functions or Functions likely to be modified (Shaded box)
+
+Block diagram of MS Architecture showing Transmit and Receive chains. The Transmit Chain includes Acoustic Parts, Sampling, Voice Activity Detection, Speech Frame Coding, Multiplexing, Channel Coding, Interleaving, Burst Generation, Encryption, Modulator, and Transmitter. The Receive Chain includes Receiver, Demodulator/Equalizer, De-Encryption, De-Interleaving, Channel Decoding, Demultiplexing, Speech Frame Decoding, Acoustic Echo Control, DAC, and Acoustic Parts. A central LAPDM block contains SMSCC, SSCC, CC, MM, and RR. A legend indicates 'Functions not likely to be modified' (white boxes) and 'New Functions or Functions likely to be modified' (shaded boxes).
+
+Figure D.1
+
+# --- Annex E: Speech traffic channel simulator
+
+This annex contains a short description of the different blocks involved in the speech traffic channel simulator.
+
+## AMR encoder
+
+It contains the algorithms for speech encoding, channel encoding as well as voice activity detection and DTX functions. All these algorithms are considered to be part of the *codec proposal* and are left to the proponent. [*DTX algorithms are not mandatory to be included in the first proposal, still to be confirmed !!!*]. The encoder shall be capable to operate at HR or FR mode on demand (driven by the HR/FR flag). The encoder shall be capable to operate at different codec modes selected on the basis of the side information for codec control. The AMR encoder can also contain a suitable algorithm for codec mode adaptation.
+
+The information on the encoding rate is considered to be part of the speech information and it is signaled in-band or using frame stealing flag techniques according to the codec proponent algorithm.
+
+The information on HR/FR mode is intended to be signaled out of band with the current mechanism.
+
+The input signal is the standard 16 bit linear PCM signal. The output signal is the data stream at 11,4 kbit/s or 22,8 kbit/s already interleaved as in the cases of half-rate and enhanced full-rate exercises. It also shall contain the necessary in-band signaling for proper operation, this means for instance the actual operating rate and the feedback on the channel quality estimation.
+
+### EID Error Insertion Device
+
+The error insertion device allows error insertion with soft-chip output in either HR or FR operating modes.
+
+It is complying with the assumptions made in the HR and EFR specifications.
+
+The HR/FR flag is used to properly consider the soft-chip error patterns.
+
+The HR/FR flag is transferred without any error simulation on it.
+
+### Error pattern
+
+Suitable error patterns shall be defined and made available for testing. They should carry the information on the soft chip errors as well as associated RxQual and RxLev.
+
+## AMR decoder
+
+The AMR decoder contains the algorithms for channel decoding, error concealment, speech decoding as well as comfort noise and DTX functions. All the algorithms are up to the codec proponents.
+
+The AMR decoder can also contain a suitable algorithm for codec mode adaptation.
+
+### Delay
+
+The side information for codec mode control shall be transferred to the backward channel by taking into account the proper delay involved that can be different for different proposals depending on the location of the codec mode adaptation algorithm and on the in-band signaling protocol used.
+
+## AMR signaling encoder
+
+The AMR signaling encoder has the purpose to encode the required side information for codec mode adaptation. It could contain the complete AMR encoder, or it can be a simplified version in which only the signaling part is included. The other portion of information can be filled with random bits. It is part of the candidate proposal.
+
+A suitable DTX pattern must however be used in order to take into account of switching on and off the transmitter and consequently the impact on the signaling rate and on the performance in dynamic operation.
+
+## AMR signaling decoder
+
+It contains the decoding functions of the in-band signaling. Also in this case it can be the complete AMR decoder or a simplified version. It is again up to the codec proponent. Its use is to decode the side information for codec mode adaptation.
+
+# --- Annex F: Schedule for AMR development
+
+The schedule for the AMR development and standardization outlined below was produced by SMG11 at its meeting in September 1997. Subsequently, SMG2 WPB indicated that the static and dynamic error patterns needed for the Qualification Tests would not be available until December 1997 and March 1998 respectively. This will clearly impact the feasibility of completing the work in time for Release 1998. The schedule therefore needs to be reviewed by SMG11 and SMG2 to arrive at a common acceptable plan.
+
+| <b>Date</b>                                   | <b>Activity</b>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| October 1997                                  | <ul style="list-style-type: none"> <li>- Definition of the Terms of Reference.</li> <li>- Approval of the Feasibility Report at TC SMG#23.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| November 1997                                 | <ul style="list-style-type: none"> <li>- Definition of the system simulator, references and error profiles.</li> <li>- Definition of qualification test plan / Provision of references.</li> <li>- Definition of qualification and selection rules.</li> <li>- Declaration of intention to submit a candidate.</li> <li>- Start the development of the system simulator for the selection phase.</li> <li>- Start the definition of test plans for the selection phase.</li> <li>- Start the organization of the host laboratory session for selection phase.</li> </ul>                                                                                                                                                                                                                                                                                                                                     |
+| T <sub>0</sub><br>March 1998                  | <ul style="list-style-type: none"> <li>- Information to be provided for consideration of candidate algorithms:</li> <li>- High-level description of the proposed algorithm.</li> <li>- Qualification test results of the candidate algorithm according to the qualification test procedure.</li> <li>- Additional information from the proponents, e.g. convergence time and complexity of the proposed algorithm.</li> <li>- Demo-tape, e.g. a DAT tape, with processed speech (+ noise) material. - Description of the acoustic/environmental conditions used for the recordings (e.g. audio parts, S/N ratios, frequency bandwidth, etc.)</li> <li>- Written statement on IPR (according to the "<i>ETSI Patent Policy</i>")</li> <li>- Continue the definition of test plan for the selection phase.</li> <li>- Continue the organization of the laboratory sessions for the selection phase.</li> </ul> |
+| T <sub>0</sub> + 2 months<br>(May 1998)       | <ul style="list-style-type: none"> <li>- Completion of test plans for the selection phase.</li> <li>- Submission of detailed description of candidate algorithms.</li> <li>- Completion of the system simulator</li> <li>- Submission of software simulations to host laborator(y)ies.</li> <li>- Start subjective tests for the selection phase</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| T <sub>0</sub> + 4 months<br>(July 1998)      | <ul style="list-style-type: none"> <li>- Evaluation of the results of the selection phase.</li> <li>- Evaluation of algorithm complexity.</li> <li>- Selection of one candidate for further consideration (optimization).</li> <li>- Start of the definition of test plan for the characterization phase.</li> <li>- TFO Outline Enhancement.</li> <li>- SMG2 Outline Channel Control Standard.</li> <li>- Start DTX definition.</li> <li>- Start development of test vectors and signaling type approval testing.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                |
+| T <sub>0</sub> + 6 months<br>(September 1998) | <ul style="list-style-type: none"> <li>- Review of available results for candidate or compromise algorithm.</li> <li>- Agreement on selected algorithm.</li> <li>- Definition of test plan for the characterization phase.</li> <li>- Definition of the laboratory session for the characterization test.</li> <li>- Start development of algorithm implementation verification tests.</li> <li>- Description of TFO mechanism.</li> <li>- SMG2 Channel Control metric definition.</li> <li>- Description of DTX proposal.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                        |
+| T <sub>0</sub> + 8 months<br>(November 1998)  | <ul style="list-style-type: none"> <li>- Completion of the characterization phase.</li> <li>- Evaluation of the results of the characterization test.</li> <li>- Complete the set of AMR standards.</li> <li>- Finalize Channel Control/Metric specifications.</li> <li>- Finalize TFO mechanism.</li> <li>- Complete the DTX standard.</li> <li>- STCs (SMG2/SMG3/SMG7/SMG8/SMG11) approval.</li> <li>- Implementation of algorithm on different platforms</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| T <sub>0</sub> + 9 months<br>(December 1998)  | <ul style="list-style-type: none"> <li>- Completion of algorithm implementation verification test procedures.</li> <li>- TC SMG approval.</li> </ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+Start of Phase 2
+
+# --- Annex G: Work Item Description for AMR
+
+## Adaptive Multi-Rate codec
+
+## Justification
+
+During 1995/6, the SQSG (Speech Quality Strategy Group) reviewed the need for any future GSM codecs and presented its recommendations to SMG#20. It concluded that the future needs of GSM users would be well served by the development of a single new speech codec.
+
+With competition in the fast changing Telecommunications environment, the convergence of different forms of network access, and customer expectations will place great demands on network quality. For GSM to successfully compete in this environment, GSM must be capable of offering wireline speech quality that is robust to adverse conditions such as channel errors, background noise and tandeming. Whilst current codecs achieve good performance under most conditions, there remain some shortfalls, particularly in respect of realizing wireline quality half-rate operation and maintaining good quality under high error conditions.
+
+The Adaptive Multi-Rate (AMR) solution offers high quality half-rate operation yielding capacity enhancements and cost savings and it also offers wireline quality in full-rate mode that is highly robust to channel errors.
+
+## Wideband
+
+There is also growing market interest in a wideband speech service (e.g. 7 kHz) and a wideband mode may also be included in the AMR codec. If this mode is to be included, it should not delay the development of the narrowband speech application of AMR.
+
+## Service Aspects
+
+The main requirements of the AMR codec are to provide:
+
+- consistent wireline quality even under variable radio channel conditions;
+- wireline half-rate operation, possibly restricted to low error rates;
+- the flexibility for operators to optimize the balance of capacity and quality.
+
+If the scope of AMR is extended to include a new wideband speech service option, the nature of this service will need to be determined.
+
+## MMI-Aspects
+
+None.
+
+## Charging Aspects
+
+The option to be able to charge for use of the AMR codec is to be reviewed.
+
+## Security Aspects
+
+None.
+
+## Impacts
+
+| Affects:   | SIM | ME | NW | Others |
+|------------|-----|----|----|--------|
+| Yes        |     | ✓  | ✓  |        |
+| No         | ✓   |    |    |        |
+| Don't know |     |    |    |        |
+
+## **Expected Output and Time-scales (to be updated at each plenary)**
+
+| <b>New specifications</b> |              |                       |                               |                                          |                         |                 |
+|---------------------------|--------------|-----------------------|-------------------------------|------------------------------------------|-------------------------|-----------------|
+| <b>GSM No.</b>            | <b>Title</b> | <b>Prime rsp. STC</b> | <b>Secondary resp. STC(s)</b> | <b>presented for information at SMG#</b> | <b>approved at SMG#</b> | <b>Comments</b> |
+|                           | tbd          | SMG11                 | SMG2<br>SMG3                  |                                          |                         |                 |
+|                           |              |                       |                               |                                          |                         |                 |
+
+| <b>Affected existing specifications</b> |           |                |                         |                 |
+|-----------------------------------------|-----------|----------------|-------------------------|-----------------|
+| <b>GSM No.</b>                          | <b>CR</b> | <b>Subject</b> | <b>Approved at SMG#</b> | <b>Comments</b> |
+|                                         |           | tbd            |                         |                 |
+|                                         |           |                |                         |                 |
+
+[ffs]
+
+## **Rapporteur(s)**
+
+K. Järvinen
+
+## **Others**
+
+# Annex H: Change history
+
+| Change history |       |           |    |     |                                                      |        |        |
+|----------------|-------|-----------|----|-----|------------------------------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc.  | CR | Rev | Subject/Comment                                      | Old    | New    |
+| March 00       | SA#7  | SP-000023 |    |     | Approved at TSG SA#7 and placed under Change Control |        | 7.0.0  |
+| March 00       |       |           |    |     | Version for Release 1999                             |        | 8.0.0  |
+| March 01       | SA#11 |           |    |     | Version for Release 4                                |        | 4.0.0  |
+| December 01    |       |           |    |     | Figures 6.1 and 6.2 visible                          | 4.0.0  | 4.0.1  |
+| December 04    | SA#26 |           |    |     | Version for Release 6                                | 4.0.1  | 6.0.0  |
+| June 07        | SA#36 |           |    |     | Version for Release 7                                | 6.0.0  | 7.0.0  |
+| December 08    | SA#42 |           |    |     | Version for Release 8                                | 7.0.0  | 8.0.0  |
+| December 09    | SA#46 |           |    |     | Version for Release 9                                | 8.0.0  | 9.0.0  |
+| March 2011     | SA#51 |           |    |     | Version for Release 10                               | 9.0.0  | 10.0.0 |
+| September 12   | SA#57 |           |    |     | Version for Release 11                               | 10.0.0 | 11.0.0 |
+| September 14   | SA#65 |           |    |     | Version for Release 12                               | 11.0.0 | 12.0.0 |
+| December 15    | SA#70 |           |    |     | Version for Release 13                               | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46082/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/46_series/46082/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9a82e38f4453674486dca150ce966159196a52d9
--- /dev/null
+++ b/marked/Rel-16/46_series/46082/27b06ec9f42b5d727a2630f61a5f1861_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:df7b4e08adbe89db5faa9325f23d1209d53515b1c5b6722658b2b53a3119c807
+size 78500
diff --git a/marked/Rel-16/46_series/46082/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/46_series/46082/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5359258c27dd0b2fb5884319e7ed3b9ffef53047
--- /dev/null
+++ b/marked/Rel-16/46_series/46082/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d4479c52c7e2a6f9c9702142e43618d84072ce0937f375424fc6ce172cbb5ac
+size 59181
diff --git a/marked/Rel-16/46_series/46082/raw.md b/marked/Rel-16/46_series/46082/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b6c3e210cb16c9b37c86603cd7791e8ab7419fd
--- /dev/null
+++ b/marked/Rel-16/46_series/46082/raw.md
@@ -0,0 +1,647 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                         |           |
+|-------------------------------------------------------------------------|-----------|
+| Foreword .....                                                          | 4         |
+| 1 Scope.....                                                            | 5         |
+| 2 References.....                                                       | 5         |
+| 3 Definitions, symbols and abbreviations .....                          | 5         |
+| 3.1 Definitions.....                                                    | 5         |
+| 3.2 Symbols.....                                                        | 5         |
+| 3.2.1 Variables.....                                                    | 5         |
+| 3.2.2 Constants .....                                                   | 6         |
+| 3.2.3 Functions .....                                                   | 6         |
+| 3.3 Abbreviations .....                                                 | 7         |
+| 4 General.....                                                          | 7         |
+| 5 Functional description.....                                           | 7         |
+| 5.1 Overview and principles of operation .....                          | 7         |
+| 5.2 Algorithm description .....                                         | 7         |
+| 5.2.1 Adaptive filtering and energy computation .....                   | 8         |
+| 5.2.2 ACF averaging.....                                                | 9         |
+| 5.2.3 Predictor values computation .....                                | 9         |
+| 5.2.4 Spectral comparison .....                                         | 10        |
+| 5.2.5 Information tone detection .....                                  | 10        |
+| 5.2.6 Threshold adaptation .....                                        | 11        |
+| 5.2.7 VAD decision .....                                                | 12        |
+| 5.2.8 VAD hangover addition .....                                       | 13        |
+| 5.2.9 Periodicity detection.....                                        | 13        |
+| 6 Computational description overview .....                              | 14        |
+| 6.1 VAD modules.....                                                    | 14        |
+| 6.2 Pseudo-floating point arithmetic .....                              | 14        |
+| <b>Annex A (informative): Simplified block filtering operation.....</b> | <b>16</b> |
+| <b>Annex B (informative): Pole frequency calculation.....</b>           | <b>17</b> |
+| Annex C (informative): Change history.....                              | 18        |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels within the digital cellular telecommunications system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.81 [5] Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels.
+
+The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the enhanced full-rate speech traffic channel.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [3] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test vectors for the GSM Enhanced Full Rate (EFR) speech codec".
+- [4] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [5] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+For the purposes of the present document, the following terms and definitions apply:
+
+**noise:** signal component resulting from acoustic environmental noise.
+
+**mobile environment:** any environment in which mobile stations may be used.
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+### 3.2.1 Variables
+
+|            |                                                                          |
+|------------|--------------------------------------------------------------------------|
+| aav1       | filter predictor values, see clause 5.2.3                                |
+| acf        | the ACF vector which is calculated in the speech encoder (GSM 06.60 [4]) |
+| adaptcount | secondary hangover counter, see clause 5.2.6                             |
+| av0        | averaged ACF vector, see clause 5.2.2                                    |
+| av1        | a previous value of av0, see clause 5.2.2                                |
+| burstcount | speech burst length counter, see clause 5.2.8                            |
+
+|                 |                                                                                                         |
+|-----------------|---------------------------------------------------------------------------------------------------------|
+| den             | denominator of left hand side of equation 8 in annex B, see clause 5.2.5                                |
+| difference      | difference between consecutive values of dm, see clause 5.2.4                                           |
+| dm              | spectral distortion measure, see clause 5.2.4                                                           |
+| hangcount       | primary hangover counter, see clause 5.2.8                                                              |
+| lagcount        | number of subframes in current frame meeting periodicity criterion, see clause 5.2.9                    |
+| lastdm          | previous value of dm, see clause 5.2.4                                                                  |
+| lags            | the open loop long term predictor lags for the two halves of the speech encoder frame (GSM 06.60 [4])   |
+| num             | numerator of left hand side of equation 8 in annex B, see clause 5.2.5                                  |
+| oldlagcount     | previous value of lagcount, see clause 5.2.9                                                            |
+| prederr         | fourth order short term prediction error, see clause 5.2.5                                              |
+| ptch            | Boolean flag indicating the presence of a periodic signal component, see clause 5.2.9                   |
+| pvad            | energy in the current filtered signal frame, see clause 5.2.1                                           |
+| rav1            | autocorrelation vector obtained from av1, see clause 5.2.3                                              |
+| rc              | the first four unquantized reflection coefficients calculated in the speech encoder (GSM 06.60 [4])     |
+| rvad            | autocorrelation vector of the adaptive filter predictor values, see clause 5.2.6                        |
+| smallag         | difference between consecutive lag values, see clause 5.2.9                                             |
+| stat            | Boolean flag indicating that the frequency spectrum of the input signal is stationary, see clause 5.2.4 |
+| thvad           | adaptive primary VAD threshold, see clause 5.2.6                                                        |
+| tone            | Boolean flag indicating the presence of an information tone, see clause 5.2.5                           |
+| vadflag         | Boolean VAD decision with hangover included, see clause 5.2.8                                           |
+| veryoldlagcount | previous value of oldlagcount, see clause 5.2.9                                                         |
+| vvad            | Boolean VAD decision before hangover, see clause 5.2.7                                                  |
+
+### 3.2.2 Constants
+
+|            |                                                                             |
+|------------|-----------------------------------------------------------------------------|
+| adp        | number of frames of hangover for secondary VAD, see clause 5.2.6            |
+| burstconst | minimum length of speech burst to which hangover is added, see clause 5.2.8 |
+| dec        | determines rate of decrease in adaptive threshold, see clause 5.2.6         |
+| fac        | determines steady state adaptive threshold, see clause 5.2.6                |
+| frames     | number of frames over which av0 and av1 are calculated, see clause 5.2.2    |
+| freqth     | threshold for pole frequency decision, see clause 5.2.5                     |
+| hangconst  | number of frames of hangover for primary VAD, see clause 5.2.8              |
+| inc        | determines rate of increase in adaptive threshold, see clause 5.2.6         |
+| lthresh    | lag difference threshold for periodicity decision, see clause 5.2.9         |
+| margin     | determines upper limit for adaptive threshold, see clause 5.2.6             |
+| nthresh    | frame count threshold for periodicity decision, see clause 5.2.9            |
+| plev       | lower limit for adaptive threshold, see clause 5.2.6                        |
+| predth     | threshold for short term prediction error, see clause 5.2.5                 |
+| pth        | energy threshold, see clause 5.2.6                                          |
+| thresh     | decision threshold for evaluation of stat flag, see clause 5.2.4            |
+
+### 3.2.3 Functions
+
+|                   |                                             |
+|-------------------|---------------------------------------------|
+| +                 | addition                                    |
+| -                 | subtraction                                 |
+| *                 | multiplication                              |
+| /                 | division                                    |
+| x                 | absolute value of x                         |
+| AND               | Boolean AND                                 |
+| OR                | Boolean OR                                  |
+| b                 |                                             |
+| MULT(x(i))<br>i=a | the product of the series x(i) for i=a to b |
+| b                 |                                             |
+| SUM(x(i))<br>i=a  | the sum of the series x(i) for i=a to b     |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the following abbreviations apply:
+
+|      |                                       |
+|------|---------------------------------------|
+| ACF  | Autocorrelation function              |
+| ANSI | American National Standards Institute |
+| DTX  | Discontinuous Transmission            |
+| LTP  | Long Term Predictor                   |
+| TX   | Transmission                          |
+| VAD  | Voice Activity Detector               |
+
+For abbreviations not given in this clause, see GSM 01.04 [1].
+
+# --- 4 General
+
+The function of the VAD is to indicate whether each 20 ms frame produced by the speech encoder contains speech or not. The output is a Boolean flag (vadflag) which is used by the Transmit (TX) DTX handler defined in GSM 06.81 [5].
+
+The present document is organized as follows.
+
+Clause 5 describes the principles of operation of the VAD. Clause 6 provides an overview of the computational description of the VAD. The computational details necessary for the fixed point implementation of the VAD algorithm are given in the form of ANSI C program contained in GSM 06.53 [2].
+
+The verification of the VAD is based on the use of digital test sequences which are described in GSM 06.54 [3].
+
+# --- 5 Functional description
+
+The purpose of this clause is to give the reader an understanding of the principles of operation of the VAD, whereas GSM 06.53 [2] contains the fixed point computational description of the VAD. In the case of discrepancy between the two descriptions, the description in GSM 06.53 [2] will prevail.
+
+## 5.1 Overview and principles of operation
+
+The function of the VAD is to distinguish between noise with speech present and noise without speech present. This is achieved by comparing the energy of a filtered version of the input signal with a threshold. The presence of speech is indicated whenever the threshold is exceeded.
+
+The detection of speech in a mobile environment is difficult due to the low speech/noise ratios which are encountered, particularly in moving vehicles. To increase the probability of detecting speech the input signal is adaptively filtered (see clause 5.2.1) to reduce its noise content before the voice activity decision is made (see clause 5.2.7).
+
+The frequency spectrum and level of the noise may vary within a given environment as well as between different environments. It is therefore necessary to adapt the input filter coefficients and energy threshold at regular intervals as described in clause 5.2.6.
+
+## 5.2 Algorithm description
+
+The block diagram of the VAD algorithm is shown in figure 1. The individual blocks are described in the following clauses. The variables shown in the block diagram are described in table 1.
+
+Table 1: Description of variables in figure 1
+
+| Var     | Description                                                                                            |
+|---------|--------------------------------------------------------------------------------------------------------|
+| acf     | The ACF vector which is calculated in the speech encoder (GSM 06.60 [4]).                              |
+| av0     | Averaged ACF vector.                                                                                   |
+| av1     | A previous value of av0.                                                                               |
+| lags    | The open loop long term predictor lags for the two halves of the speech encoder frame (GSM 06.60 [4]). |
+| ptch    | Boolean flag indicating the presence of a periodic signal component.                                   |
+| pvad    | Energy in the current filtered signal frame.                                                           |
+| rav1    | Autocorrelation vector obtained from av1.                                                              |
+| rc      | The first four reflection coefficients calculated in the speech encoder (GSM 06.60 [4]).               |
+| rvad    | Autocorrelation vector of the adaptive filter predictor values.                                        |
+| stat    | Boolean flag indicating that the frequency spectrum of the input signal is stationary.                 |
+| thvad   | Adaptive primary VAD threshold.                                                                        |
+| tone    | Boolean flag indicating the presence of an information tone.                                           |
+| vadflag | Boolean VAD decision with hangover included.                                                           |
+| vvad    | Boolean VAD decision before hangover.                                                                  |
+
+![Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows, with some blocks providing feedback or control signals to others.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg)
+
+```
+
+graph LR
+    acf --> AFE[Adaptive filtering and energy computation]
+    lags --> PD[Periodicity detection]
+    rc --> TD[Tone detection]
+    acf --> AV[ACF averaging]
+    PD -- ptch --> TA[Threshold adaptation]
+    TD -- tone --> TA
+    AV -- av0 --> SC[Spectral comparison]
+    AV -- av1 --> PWC[Predictor values computation]
+    PWC -- rav1 --> SC
+    PWC -- stat --> SC
+    SC -- th_vad --> TA
+    TA -- th_vad --> VD[VAD decision]
+    AFE -- pvad --> VD
+    AFE -- rvad --> TA
+    VD -- vvad --> VHA[VAD hangover addition]
+    VHA -- vadflag --> Output
+  
+```
+
+Functional block diagram of the VAD. The diagram shows the flow of data from input variables (acf, lags, rc) through various processing blocks to the output vadflag. The blocks include Adaptive filtering and energy computation, Periodicity detection, Tone detection, Predictor values computation, ACF averaging, Threshold adaptation, Spectral comparison, VAD decision, and VAD hangover addition. Data flow is indicated by arrows, with some blocks providing feedback or control signals to others.
+
+Figure 1: Functional block diagram of the VAD
+
+### 5.2.1 Adaptive filtering and energy computation
+
+The energy in the current filtered signal frame (pvad) is computed as follows:
+
+$$pvad = rvad[0] * acf[0] + 2 * \sum_{i=1}^8 (rvad[i] * acf[i]) \quad (1)$$
+
+This corresponds to performing an 8th order block filtering on the filtered input samples to the speech encoder. This is explained in annex A.
+
+### 5.2.2 ACF averaging
+
+Spectral characteristics of the input signal have to be obtained using blocks that are larger than one 20 ms frame. This is done by averaging the ACF (autocorrelation function) values for several consecutive frames. The averaging is given by the following equations:
+
+$$\text{av0}\{n\}[i] = \sum_{j=0}^{\text{frames}-1} (\text{acf}\{n-j\}[i]) \quad ; i = 0..8 \quad (2)$$
+
+$$\text{av1}\{n\}[i] = \text{av0}\{n-\text{frames}\}[i] \quad ; i = 0..8 \quad (3)$$
+
+where (n) represents the current frame, (n-1) represents the previous frame. The values of constants are given in table 2.
+
+**Table 2: Constants and variables for ACF averaging**
+
+| Constant | Value | Variable                     | Initial value |
+|----------|-------|------------------------------|---------------|
+| frames   | 4     | previous ACF's,<br>av0 & av1 | All set to 0  |
+
+### 5.2.3 Predictor values computation
+
+The filter predictor values aav1 are obtained from the autocorrelation values av1 according to the equation:
+
+$$a = R^{-1}p \quad (4)$$
+
+where:
+
+$$R = \begin{bmatrix} \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] & \text{av1}[6] & \text{av1}[7] \\ \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] & \text{av1}[6] \\ \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] & \text{av1}[5] \\ \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] & \text{av1}[4] \\ \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] & \text{av1}[3] \\ \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] & \text{av1}[2] \\ \text{av1}[6] & \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] & \text{av1}[1] \\ \text{av1}[7] & \text{av1}[6] & \text{av1}[5] & \text{av1}[4] & \text{av1}[3] & \text{av1}[2] & \text{av1}[1] & \text{av1}[0] \end{bmatrix}$$
+
+and:
+
+$$p = \begin{bmatrix} \text{av1}[1] \\ \text{av1}[2] \\ \text{av1}[3] \\ \text{av1}[4] \\ \text{av1}[5] \\ \text{av1}[6] \\ \text{av1}[7] \\ \text{av1}[8] \end{bmatrix} \quad a = \begin{bmatrix} \text{aav1}[1] \\ \text{aav1}[2] \\ \text{aav1}[3] \\ \text{aav1}[4] \\ \text{aav1}[5] \\ \text{aav1}[6] \\ \text{aav1}[7] \\ \text{aav1}[8] \end{bmatrix}$$
+
+```
+aav1[0] = -1
+```
+
+av1 is used in preference to av0 as the latter may contain speech. The autocorrelated predictor values rav1 are then obtained:
+
+$$rav1[i] = \sum_{k=0}^{8-i} (aav1[k] * aav1[k+i]) \quad ; i = 0..8 \hfill (5)$$
+
+### 5.2.4 Spectral comparison
+
+The spectra represented by the autocorrelated predictor values rav1 and the averaged autocorrelation values av0 are compared using the distortion measure (dm) defined below. This measure is used to produce a Boolean value stat every 20 ms, as shown in the following equations:
+
+$$dm = (rav1[0] * av0[0] + 2 * \sum_{i=1}^{8} (rav1[i] * av0[i])) / av0[0] \hfill (6a)$$
+
+difference = |dm - lastdm| (6b)
+
+lastdm = dm (6c)
+
+stat = (difference < thresh) (6d)
+
+The values of constants and initial values are given in table 3.
+
+**Table 3: Constants and variables for spectral comparison**
+
+| Constant | Value | Variable | Initial value |
+|----------|-------|----------|---------------|
+| thresh   | 0.056 | lastdm   | 0             |
+
+### 5.2.5 Information tone detection
+
+Information tones and noise can be classified by inspecting the short term prediction gain, information tones resulting in a higher prediction gain than noise. Tones can therefore be detected by comparing the prediction gain to a fixed threshold. By limiting the prediction gain calculation to a fourth order analysis, information signals consisting of one or two tones can be detected whilst minimizing the prediction gain for noise.
+
+The prediction gain decision is implemented by comparing the normalized short term prediction error with the short term prediction error threshold (predth). This measure is used to produce a Boolean value, tone, every 20 ms. The signal is classified as a tone if the prediction error is less than predth. This is equivalent to a prediction gain threshold of 13.5 dB.
+
+Vehicle noise can contain strong resonances at low frequencies, resulting in a high prediction gain. A further test is therefore made to determine the pole frequency of a second order analysis of the signal frame. The signal is classified as noise if the frequency of the pole is less than 385 Hz.
+
+The algorithm for evaluating the Boolean tone flag is as follows:
+
+```
+
+tone = false
+den = a[1]*a[1]
+num = 4*a[2] - a[1]*a[1]
+if (num <= 0)
+    return
+
+if ((a[1] < 0) AND (num/den < freqth))
+    return
+
+prederr = MULT (1 - rc[i] * rc[i])
+          i=1..4
+
+```
+
+Note: The last line represents a product over i from 1 to 4.
+
+```
+
+if (prederr < predth)
+    tone = true
+
+return
+
+```
+
+rc[1..4] are the first four unquantized reflection coefficients obtained from the speech encoder short term predictor. The coefficients a[0..2] are transversal filter coefficients calculated from rc[1..2] using the step up routine. The pole frequency calculation is described in annex B.
+
+The values of the constants are given in table 4.
+
+**Table 4: Constants for information tone detection**
+
+| <b>Constant</b> | <b>Value</b> |
+|-----------------|--------------|
+| freqth          | 0,0973       |
+| predth          | 0,0447       |
+
+### 5.2.6 Threshold adaptation
+
+A check is made every 20 ms to determine whether the VAD decision threshold, (thvad) should be changed. This adaptation is carried out according to the flowchart shown in figure 2. The values of the constants and initial variable values are given in table 5.
+
+Adaptation of thvad takes place in two different situations:
+
+In the first case, the decision threshold (thvad) is set to the lower limit for the adaptive threshold (plev) if the input signal frame energy (acf[0]) is less than the energy threshold (pth). The autocorrelation vector of the adaptive filter predictor values (rvad) remains unchanged.
+
+In the second case, thvad and rvad are adapted if there is a low probability that speech or information tones are present. This occurs when the following conditions are met:
+
+- The frequency spectrum of the input signal is stationary (clause 5.2.4).
+- The signal does not contain a periodic component (clause 5.2.9).
+- Information tones are not present (clause 5.2.5).
+
+The autocorrelation vector of the adaptive filter predictor values (rvad) is updated with the rav1 values. The step size by which thvad is adapted is not constant but a proportion of the current value and its rate of increase or decrease is determined by constants inc and dec respectively.
+
+The adaptation begins by experimentally multiplying thvad by a factor of  $(1-1/\text{dec})$ . If thvad is now higher than or equal to pvad times the steady state adaptive threshold constant (fac), then thvad needed to be decreased and it is left at this new lower level. If, on the other hand, thvad is less than pvad times fac then it either needs to be increased or kept constant. In this case, it is multiplied by a factor of  $(1+1/\text{inc})$  or set to pvad times fac whichever yields the lower value. Thvad is never allowed to be greater than pvad+upper adaptive threshold limit (margin).
+
+**Table 5: Constants and variables threshold adaptation**
+
+| <b>Constant</b> | <b>Value</b> | <b>Variable</b> | <b>Initial value</b> |
+|-----------------|--------------|-----------------|----------------------|
+| pth             | 130000       | margin          | 69333340             |
+| plev            | 346667       | adaptcount      | 0                    |
+| fac             | 2,1          | thvad           | 866656               |
+| adp             | 8            | rvad[0]         | 6                    |
+| inc             | 16           | rvad[1..8]      | All set to 0         |
+| dec             | 32           |                 |                      |
+
+![Flow diagram for threshold adaptation. The process starts at BEGIN, checks if acf[0] < pth. If yes, th_vad = plev. If no, checks if stat and not ptch and not tone. If yes, increment adaptcount. If no, adaptcount = 0. Then checks if adaptcount > adp. If yes, th_vad = th_vad - th_vad / dec. Then checks if th_vad < pvad * fac. If yes, th_vad = min(th_vad + th_vad / inc, pvad * fac). Then checks if th_vad > pvad + margin. If yes, th_vad = pvad + margin. Finally, r_vad = r_av1, adaptcount = adp + 1, and ends at END.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+```
+
+graph TD
+    BEGIN((BEGIN)) --> D1{acf[0] < pth ?}
+    D1 -- yes --> P1[th_vad = plev]
+    D1 -- no --> D2{stat and not ptch and not tone ?}
+    D2 -- yes --> P2[increment adaptcount]
+    D2 -- no --> P3[adaptcount = 0]
+    P2 --> D3{adaptcount > adp ?}
+    P3 --> D3
+    D3 -- yes --> P4[th_vad = th_vad - th_vad / dec]
+    D3 -- no --> END((END))
+    P4 --> D4{th_vad < pvad * fac ?}
+    D4 -- yes --> P5[th_vad = min(th_vad + th_vad / inc, pvad * fac)]
+    D4 -- no --> D5{th_vad > pvad + margin ?}
+    P5 --> D5
+    D5 -- yes --> P6[th_vad = pvad + margin]
+    D5 -- no --> P7[r_vad = r_av1]
+    P6 --> P7
+    P7 --> P8[adaptcount = adp + 1]
+    P8 --> END
+  
+```
+
+Flow diagram for threshold adaptation. The process starts at BEGIN, checks if acf[0] < pth. If yes, th\_vad = plev. If no, checks if stat and not ptch and not tone. If yes, increment adaptcount. If no, adaptcount = 0. Then checks if adaptcount > adp. If yes, th\_vad = th\_vad - th\_vad / dec. Then checks if th\_vad < pvad \* fac. If yes, th\_vad = min(th\_vad + th\_vad / inc, pvad \* fac). Then checks if th\_vad > pvad + margin. If yes, th\_vad = pvad + margin. Finally, r\_vad = r\_av1, adaptcount = adp + 1, and ends at END.
+
+Figure 2: Flow diagram for threshold adaptation
+
+### 5.2.7 VAD decision
+
+Prior to hangover the Boolean VAD decision is defined as:
+
+$$vvvad = (pvad > thvad)$$
+
+### 5.2.8 VAD hangover addition
+
+VAD hangover is only added to bursts of speech greater than or equal to burstconst blocks. The Boolean variable vadflag indicates the decision of the VAD with hangover included. The values of the constants and initial variable values are given in table 6. The hangover algorithm is as follows:
+
+```
+
+if (vvad)
+    increment(burstcount)
+else
+    burstcount = 0
+
+if (burstcount >= burstconst)
+{
+    hangcount = hangconst
+    burstcount = burstconst
+}
+
+vadflag = (vvad OR (hangcount >= 0))
+
+if (hangcount >= 0)
+    decrement(hangcount)
+
+```
+
+**Table 6: Constants and variables for VAD hangover addition**
+
+| Constant   | Value | Variable   | Initial value |
+|------------|-------|------------|---------------|
+| burstconst | 3     | burstcount | 0             |
+| hangconst  | 10    | hangcount  | -1            |
+
+### 5.2.9 Periodicity detection
+
+The variables thvad and rvad are updated when the frequency spectrum of the input signal is stationary. However, vowel sounds also have a stationary frequency spectrum. The Boolean variable ptch indicates the presence of a periodic signal component and prevents adaptation of thvad and rvad. The variable ptch is updated every 20 ms and is true when periodicity (a vowel sound) is detected. The periodicity detector identifies the vowel sounds by comparing consecutive Long Term Predictor (LTP) lag values lags[1..2] which are obtained during the open loop pitch lag search from the speech codec defined in GSM 06.60 [4]. Cases in which one lag value is near the other are catered for, however the cases in which one lag value is a factor of the other, or in which both lag values have a common factor, are not.
+
+```
+
+lagcount = 0
+
+for (j = 1; j <= 2; j++)
+{
+    smallag = maximum(lags[j], lags[j-1]) - minimum(lags[j], lags[j-1])
+
+    if ((smallag - lthresh) < 0)
+        increment(lagcount)
+}
+
+veryoldlagcount = oldlagcount
+oldlagcount = lagcount
+
+ptch = (oldlagcount + veryoldlagcount >= nthresh)
+
+```
+
+The values of constants and initial values are given in table 7. lags[0] = lags[2] of the previous frame.
+
+ptch is calculated after the VAD decision and when the current LTP lag values lags[1..2] are available. This reduces the delay of the VAD decision.
+
+**Table 7: Constants and variables for periodicity detection**
+
+| Constant | Value | Variable        | Initial value |
+|----------|-------|-----------------|---------------|
+| lthresh  | 2     | ptch            | 1             |
+| nthresh  | 4     | oldlagcount     | 0             |
+|          |       | veryoldlagcount | 0             |
+|          |       | lags[0]         | 18            |
+
+# 6 Computational description overview
+
+The computational details necessary for the fixed point implementation of the speech transcoding and DTX functions are given in the form of an American National Standards Institute (ANSI) C program contained in GSM 06.53 [2]. This clause provides an overview of the modules which describe the computation of the VAD algorithm.
+
+## 6.1 VAD modules
+
+The computational description of the VAD is divided into three ANSI C modules. These modules are:
+
+- vad\_reset;
+- vad\_computation;
+- periodicity\_update.
+
+The vad\_reset module sets the VAD variables to their initial values.
+
+The vad\_computation module is divided into nine sub-modules which correspond to the blocks of figure 1 in the high level description of the VAD algorithm. The vad\_computation module can be called as soon as the acf[0..8] and rc[1..4] variables are known. This means that the VAD computation can take place after the levinson routine of the second half of the frame in the speech encoder (GSM 06.60 [4]). The vad\_computation module also requires the value of the ptch variable calculated in the previous frame.
+
+The ptch variable is calculated by the periodicity\_update module from the lags[1..2] variable. The individual lag values are calculated by the open loop pitch search routine in the speech encoder (GSM 06.60 [4]). The periodicity\_update module is called after the VAD decision and when the current LTP lag values lags[1..2] are available.
+
+## 6.2 Pseudo-floating point arithmetic
+
+All the arithmetic operations follow the precision and format used in the computational description of the speech codec in GSM 06.53 [2]. To increase the precision within the fixed point implementation, a pseudo-floating point representation of some variables is used. This applies to the following variables (and related constants) of the VAD algorithm:
+
+- pvad: Energy of filtered signal;
+- thvad: Threshold of the VAD decision;
+- acf0: Energy of input signal.
+
+For the representation of these variables, two 16-bit integers are needed:
+
+- one for the exponent (e\_pvad, e\_thvad, e\_acf0);
+- one for the mantissa (m\_pvad, m\_thvad, m\_acf0).
+
+The value e\_pvad represents the lowest power of 2 just greater or equal to the actual value of pvad and the m\_pvad value represents an integer which is always greater or equal to 16 384 (normalized mantissa). It means that the pvad value is equal to:
+
+$$pvad = 2^{e\_pvad} * (m\_pvad/32768) \quad (7)$$
+
+This scheme provides a large dynamic range for the pvad value and always keeps a precision of 16 bits. All the comparisons are easy to make by comparing the exponents of two variables. The VAD algorithm needs only one pseudo-floating point addition and multiplication. All the computations related to the pseudo-floating point variables require simple 16- or 32-bit arithmetic operations defined in the detailed description of the speech codec.
+
+Some constants, represented by a pseudo-floating point format, are needed and symbolic names (in capital letters) for their exponent and mantissa are used; table 8 lists all these constants with the associated symbolic names and their numerical constant values.
+
+**Table 8: List of floating point constants**
+
+| Constant | Exponent      | Mantissa         |
+|----------|---------------|------------------|
+| pth      | E_PTH = 17    | M_PTH = 32500    |
+| margin   | E_MARGIN = 27 | M_MARGIN = 16927 |
+| plev     | E_PLEV = 19   | M_PLEV = 21667   |
+
+# Annex A (informative): Simplified block filtering operation
+
+Consider an 8th order transversal filter with filter coefficients  $a_0..a_8$ , through which a signal is being passed, the output of the filter being:
+
+$$s'[n] = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad (1)$$
+
+If we apply block filtering over 20 ms segments, then this equation becomes:
+
+$$s'[n] = - \sum_{i=0}^8 (a[i]*s[n-i]) \quad ; \quad n = 0..167 \quad (2)$$
+
+$$\quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad ; \quad 0 \leq n-i \leq 159$$
+
+If the energy of the filtered signal is then obtained for every 20 ms segment, the equation for this is:
+
+$$pvad = \sum_{n=0}^{167} \left( - \sum_{i=0}^8 (a[i]*s[n-i]) \right)^2 \quad ; \quad 0 \leq n-i \leq 159 \quad (3)$$
+
+We know that:
+
+$$acf[i] = \sum_{n=0}^{159} (s[n]*s[n-i]) \quad ; \quad i = 0..8 \quad (4)$$
+
+$$\quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad \quad ; \quad 0 \leq n-i \leq 159$$
+
+If equation (3) is expanded and  $acf[0..8]$  are substituted for  $s[n]$  then we arrive at the equations:
+
+$$pvad = r[0]*acf[0] + 2* \sum_{i=1}^8 (r[i]*acf[i]) \quad (5)$$
+
+Where:
+
+$$r[i] = \sum_{k=0}^{8-i} (a[k]*a[k+i]) \quad ; \quad i = 0..8 \quad (6)$$
+
+# Annex B (informative): Pole frequency calculation
+
+This annex describes the algorithm used to determine whether the pole frequency for a second order analysis of the signal frame is less than 385 Hz.
+
+The filter coefficients for a second order synthesis filter are calculated from the first two unquantized reflection coefficients  $rc[1..2]$  obtained from the speech encoder. This is done using the step up routine described in GSM 06.53 [2]. If the filter coefficients  $a[0..2]$  are defined such that the synthesis filter response is given by:
+
+$$H(z) = 1 / (a[0] + a[1]z^{-1} + a[2]z^{-2}) \quad (1)$$
+
+Then the positions of the poles in the Z-plane are given by the solutions to the following quadratic:
+
+$$a[0]z^2 + a[1]z + a[2] = 0, \quad a[0] = 1 \quad (2)$$
+
+The positions of the poles,  $z$ , are therefore:
+
+$$z = re \pm j \cdot \sqrt{im}, \quad j^2 = -1 \quad (3)$$
+
+where:
+
+$$re = -a[1] / 2 \quad (4)$$
+
+$$im = (4 \cdot a[2] - a[1]^2) / 4 \quad (5)$$
+
+If  $im$  is negative then the poles lie on the real axis of the Z-plane and the signal is not a tone and the algorithm terminates. If  $re$  is negative then the poles lie in the left hand side of the Z-plane and the frequency is greater than 2000 Hz and the prediction error test can be performed.
+
+If  $im$  is positive and  $re$  is positive then the poles are complex and lie in the right hand side of the Z-plane and the frequency in Hz is related to  $re$  and  $im$  by the expression:
+
+$$freq = \arctan(\sqrt{im} / re) \cdot 4000 / \pi \quad (6)$$
+
+Having ensured that both  $im$  and  $re$  are positive the test for a pole frequency less than 385 Hz can be derived by substituting equations 4 and 5 into equation 6 and re-arranging:
+
+$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < \tan^2(\pi \cdot 385 / 4000) \quad (7)$$
+
+or
+
+$$(4 \cdot a[2] - a[1]^2) / a[1]^2 < 0.0973 \quad (8)$$
+
+If this test is true then the signal is not a tone and the algorithm terminates, otherwise the prediction error test is performed.
+
+# Annex C (informative): Change history
+
+| Change history |           |         |                 |             |                                         |
+|----------------|-----------|---------|-----------------|-------------|-----------------------------------------|
+| SMG No.        | TDoc. No. | CR. No. | Clause affected | New version | Subject/Comments                        |
+| SMG#22         |           |         |                 | 4.0.1       | ETSI Publication                        |
+| SMG#20         |           |         |                 | 5.0.3       | Release 1996 version                    |
+| SMG#27         |           |         |                 | 6.0.0       | Release 1997 version                    |
+| SMG#29         |           |         |                 | 7.0.0       | Release 1998 version                    |
+|                |           |         |                 | 7.0.1       | Version update to 7.0.1 for Publication |
+| SMG#31         |           |         |                 | 8.0.0       | Release 1999 version                    |
+|                |           |         |                 | 8.0.1       | Update to Version 8.0.1 for Publication |
+
+| Change history |       |          |    |     |                                  |        |        |
+|----------------|-------|----------|----|-----|----------------------------------|--------|--------|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment                  | Old    | New    |
+| 03-2001        | 11    |          |    |     | Version for Release 4            |        | 4.0.0  |
+| 06-2002        | 16    |          |    |     | Version for Release 5            | 4.0.0  | 5.0.0  |
+| 12-2004        | 26    |          |    |     | Version for Release 6            | 5.0.0  | 6.0.0  |
+| 06-2007        | 36    |          |    |     | Version for Release 7            | 6.0.0  | 7.0.0  |
+| 07-2007        |       |          |    |     | Makes matrices in §5.2.3 visible | 7.0.0  | 7.0.1  |
+| 12-2008        | 42    |          |    |     | Version for Release 8            | 7.0.1  | 8.0.0  |
+| 12-2009        | 46    |          |    |     | Version for Release 9            | 8.0.0  | 9.0.0  |
+| 03-2011        | 51    |          |    |     | Version for Release 10           | 9.0.0  | 10.0.0 |
+| 09-2012        | 57    |          |    |     | Version for Release 11           | 10.0.0 | 11.0.0 |
+| 09-2014        | 65    |          |    |     | Version for Release 12           | 11.0.0 | 12.0.0 |
+| 12-2015        | 70    |          |    |     | Version for Release 13           | 12.0.0 | 13.0.0 |
+
+| Change history |         |      |    |     |     |                                |               |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |
\ No newline at end of file
diff --git a/marked/Rel-16/46_series/46085/011fecb4a85637472f0c697a6cbdb15d_img.jpg b/marked/Rel-16/46_series/46085/011fecb4a85637472f0c697a6cbdb15d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ca968d85801c705048202502c155ffcb3c69f0b2
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/011fecb4a85637472f0c697a6cbdb15d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:eb0dc3f60edac0987f247c1a0c65a8799c1ce97147e05a9327cb579ab175474c
+size 16327
diff --git a/marked/Rel-16/46_series/46085/239211fa511b4ffa685b54b5132ec927_img.jpg b/marked/Rel-16/46_series/46085/239211fa511b4ffa685b54b5132ec927_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0580c871b40e6a536eca8e9ebaec5be310f0932b
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/239211fa511b4ffa685b54b5132ec927_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:69061609b3fd55e8102b0a2da2b9dd7789fa98863ae9f9666e6190c738f18bcd
+size 23035
diff --git a/marked/Rel-16/46_series/46085/3468bcffa38de23cef94bfb460ccb301_img.jpg b/marked/Rel-16/46_series/46085/3468bcffa38de23cef94bfb460ccb301_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cc859d429b09683ec8bed6274206586fd13d4263
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/3468bcffa38de23cef94bfb460ccb301_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d15860a685d3c4912b9daba35324fd7e0b479689c885f4d392a16ba3424e6354
+size 147616
diff --git a/marked/Rel-16/46_series/46085/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg b/marked/Rel-16/46_series/46085/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d47015463ed4cba6bca3ce36e4d6c9e9492b0d30
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55c4b771e47b07d0bc97c7a073b08c32c749ce139154f69ce4023ecd26832d34
+size 136781
diff --git a/marked/Rel-16/46_series/46085/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/46_series/46085/410562339ce067fdc6fa41940c118658_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2048088ea65839a344700b9b86d27464eb1ee2d3
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/410562339ce067fdc6fa41940c118658_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:14a10c14a31eb6d494901ad03fe799f62aaee5b5ae0d7f46e5bd823bd5b49d41
+size 46935
diff --git a/marked/Rel-16/46_series/46085/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg b/marked/Rel-16/46_series/46085/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ced9ab07deb84e0cd28ee3aa73424ef8854052dc
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9ce47913d5f3a4a600f1f34dfc7204383f2b5e29222ae81b69355d5a62f66176
+size 26498
diff --git a/marked/Rel-16/46_series/46085/4a8166688ed7276efb173f550ba47eb4_img.jpg b/marked/Rel-16/46_series/46085/4a8166688ed7276efb173f550ba47eb4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3436a83c60c2c7c7ea3a54ef8cf58b1ce35572cd
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/4a8166688ed7276efb173f550ba47eb4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e5527bdfcbbfb6c9faeab82757f0de72458e8409ac9d46083260fcb21231d134
+size 25239
diff --git a/marked/Rel-16/46_series/46085/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg b/marked/Rel-16/46_series/46085/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2050f153eb65661236c4460b5d7ff0e14c7ce323
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:51ec3efac6b64e3648c9f04c2ac52533ab2de65f35d44a89b6de0c034185ca86
+size 16544
diff --git a/marked/Rel-16/46_series/46085/602ada2a012ff3cc38d91de2eec5b450_img.jpg b/marked/Rel-16/46_series/46085/602ada2a012ff3cc38d91de2eec5b450_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34b1e90b0b4a4f4d9316294fe217ab91b13d5e00
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/602ada2a012ff3cc38d91de2eec5b450_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:18078fa5ba0c71fd684e763198964999838c6cd54c6043e73c8ee2eab0a74847
+size 25310
diff --git a/marked/Rel-16/46_series/46085/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg b/marked/Rel-16/46_series/46085/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dd8ab5d90b700443d7bbb6ae211717df54fa8ca6
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/65a9654ccb3d0d452378b0f4c0c392f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c69471020ec52605435a79e2f0f679df709ac1d231efffc65f14fa3e62be8e65
+size 17993
diff --git a/marked/Rel-16/46_series/46085/70f5f44cb855bbb0c203c00187b2113e_img.jpg b/marked/Rel-16/46_series/46085/70f5f44cb855bbb0c203c00187b2113e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..4511b7736d6401df6a27fca7d3b472d17dddf4b6
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/70f5f44cb855bbb0c203c00187b2113e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e089c42e527109ef4fbd0a86e19504a409e6ee90d6576b3659e462f3dc82794f
+size 37622
diff --git a/marked/Rel-16/46_series/46085/723827e0738d2743c3b3423760a5c48e_img.jpg b/marked/Rel-16/46_series/46085/723827e0738d2743c3b3423760a5c48e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8243833e9a1b2563c08112ec148c5858142af24b
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/723827e0738d2743c3b3423760a5c48e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:248f135e68d74aa8066daebc9f4bb9269fcdc5850d4d9fd698ab04dcc0bd4b2d
+size 70222
diff --git a/marked/Rel-16/46_series/46085/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/46_series/46085/7e670a2b556b53ea9002dfff3a420e08_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..154bc235f1628508df5d1635761610d2df0dfe36
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/7e670a2b556b53ea9002dfff3a420e08_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c57fa1347f399fd3eb9743354eab5d2d3061fe7042becdb196a22022aacae4ae
+size 77373
diff --git a/marked/Rel-16/46_series/46085/7f687094e6abe34a9cf491942b296d9a_img.jpg b/marked/Rel-16/46_series/46085/7f687094e6abe34a9cf491942b296d9a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b255efb4a609e3da4ce17ead619b2bdee9f3b383
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/7f687094e6abe34a9cf491942b296d9a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6696d11bd6a10d21bcfa2a38c176be1e1ad374deb42618f0f72e65bee96d4d50
+size 140602
diff --git a/marked/Rel-16/46_series/46085/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg b/marked/Rel-16/46_series/46085/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9ce4110559c6a96283f695261b2930f98531e21b
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86bcc8aa070d3aa0b9b3cf7492365421df7408e7497341705e2c15c88e4214ce
+size 19806
diff --git a/marked/Rel-16/46_series/46085/a430996a9e8993deb0c6b25da234744b_img.jpg b/marked/Rel-16/46_series/46085/a430996a9e8993deb0c6b25da234744b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d2dda3aef077ebc47c3f63d965311d64be86f978
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/a430996a9e8993deb0c6b25da234744b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1f1d119689304327628d1394fa6c471e5623b5085d15c428d546d87da2e632dd
+size 16240
diff --git a/marked/Rel-16/46_series/46085/b8261918596971c3801af23435c5ea50_img.jpg b/marked/Rel-16/46_series/46085/b8261918596971c3801af23435c5ea50_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7cc2a33a35d4a4defa0cb62551aab6a96a9dcdc1
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/b8261918596971c3801af23435c5ea50_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f8cb866bc58590947c561f26428d7ac116503a8383dad7074e95275ccfe49c01
+size 14440
diff --git a/marked/Rel-16/46_series/46085/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg b/marked/Rel-16/46_series/46085/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..cdbdc59d85bda6e844e0c45bc0f034f65c1d22e7
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/c531b0e7e06671c980f2ed0d753d2fbc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d6ff11298d0bcb2f7caa0d115ada7717546c30dac61ac13516b989374634df2c
+size 74320
diff --git a/marked/Rel-16/46_series/46085/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg b/marked/Rel-16/46_series/46085/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d83dcc5bdc08fc8bc410e8e3a3e6d585dcfbeb1d
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/cbc4516eb885829fe8c9dabc0946dcbe_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:522a6fb05a4123d9a198bebc148985e42157348f1271ad750fe8072354656e20
+size 28243
diff --git a/marked/Rel-16/46_series/46085/dbc1673750fd53d4203f4d93963fdab6_img.jpg b/marked/Rel-16/46_series/46085/dbc1673750fd53d4203f4d93963fdab6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e482646daa0e947ecb2d44eb762a46eab9eba2f
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/dbc1673750fd53d4203f4d93963fdab6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0f5fcc850d7a919e81e1f7c9a51dfebe30da7bc992195637b8bec0822968466
+size 20157
diff --git a/marked/Rel-16/46_series/46085/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg b/marked/Rel-16/46_series/46085/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..341e48079f86c4631a7438604f8244a39458e6b7
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/df7cb4ea9bd6c3f445f3e264773b125f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1c6a942a24296ea37a1910e259309e89d9f4f3a33dfbf83f48c7aeab85b4d9b
+size 24993
diff --git a/marked/Rel-16/46_series/46085/ebce355620876e10f907f8b71926c112_img.jpg b/marked/Rel-16/46_series/46085/ebce355620876e10f907f8b71926c112_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0cc634db1ef45a859bb65321b2f3aad8ca6064ae
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/ebce355620876e10f907f8b71926c112_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:783621365acc2f0a1ad161fa5293407422bc6ca41f670adb8e96075ce8e61018
+size 73771
diff --git a/marked/Rel-16/46_series/46085/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg b/marked/Rel-16/46_series/46085/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1cb6f97a14ff9f12e617c537591f89a1d04ea8b
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/ef177a7090c8da3fcd9beb78e78fd68f_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9179a3e30b0c6264fa5948d3ab712a67788d409494fadd94205b5f722c59966a
+size 25244
diff --git a/marked/Rel-16/46_series/46085/f85bf99d372e735d228361bf4d3cf7e6_img.jpg b/marked/Rel-16/46_series/46085/f85bf99d372e735d228361bf4d3cf7e6_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..988f25a9c2bcaf35fdbf9072eb8d86eaf7432c2f
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/f85bf99d372e735d228361bf4d3cf7e6_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d726778c1c058a46a4c7ff28ed2400594e18eb158973cd4f6961a03d55223181
+size 77821
diff --git a/marked/Rel-16/46_series/46085/fc857414626a8d94d132e12d9afe52a4_img.jpg b/marked/Rel-16/46_series/46085/fc857414626a8d94d132e12d9afe52a4_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..77a95b66307e247976e105451a7780e425cbca1a
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/fc857414626a8d94d132e12d9afe52a4_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1c63ecbef5fb8799233ab8269b3dfa25b9acde9f86ed6823924f427233a685ed
+size 22658
diff --git a/marked/Rel-16/46_series/46085/fe61ee8618403cf584b2e28c4bada03a_img.jpg b/marked/Rel-16/46_series/46085/fe61ee8618403cf584b2e28c4bada03a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b9d6d01af7b23075db20af1a5a0057e35580c3d5
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/fe61ee8618403cf584b2e28c4bada03a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cf101e9d99b785c24183492c2b840f7220a60f02eccaa223cf0941e8fe2023e
+size 32668
diff --git a/marked/Rel-16/46_series/46085/raw.md b/marked/Rel-16/46_series/46085/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ead9cbef6adaf83f2b2e8ea85f2c91295934d52
--- /dev/null
+++ b/marked/Rel-16/46_series/46085/raw.md
@@ -0,0 +1,1082 @@
+
+
+
+
+
+
+# --- Contents
+
+|                                                                                         |           |
+|-----------------------------------------------------------------------------------------|-----------|
+| Foreword .....                                                                          | 4         |
+| 1 Scope.....                                                                            | 5         |
+| 2 References.....                                                                       | 5         |
+| 3 Definitions and abbreviations .....                                                   | 6         |
+| 3.1 Definitions.....                                                                    | 6         |
+| 3.2 Abbreviations .....                                                                 | 6         |
+| 4 General.....                                                                          | 7         |
+| 5 Testing methodology.....                                                              | 7         |
+| 5.1 Phase 1: Investigation under conditions free of environmental noise.....            | 8         |
+| 5.2 Phase 2: Investigation under conditions with far end environmental noise.....       | 8         |
+| 6 Test set-up.....                                                                      | 9         |
+| 6.1 Host Lab processing for the evaluation of HR-FR-EFR interoperability (phase 1)..... | 10        |
+| 6.2 Error concealment for TCH/FS.....                                                   | 11        |
+| 6.3 Control of codec simulation.....                                                    | 11        |
+| 6.4 Pre-processing and post-processing procedure .....                                  | 11        |
+| 6.5 Conclusion of Phase 1 .....                                                         | 12        |
+| 6.6 Host Lab processing for the evaluation of HR-FR-EFR interoperability (phase 2)..... | 12        |
+| 6.7 Processing.....                                                                     | 13        |
+| 6.8 Conclusion of Phase 2 .....                                                         | 13        |
+| 7 Summary of results .....                                                              | 13        |
+| 7.1 Quality under error conditions .....                                                | 14        |
+| 7.2 Quality under tandeming conditions .....                                            | 15        |
+| 7.3 Quality with far end background noise .....                                         | 17        |
+| 7.4 Quality enhancement using TFO techniques .....                                      | 22        |
+| 7.5 Effects of input frequency response.....                                            | 23        |
+| 8 Conclusion .....                                                                      | 23        |
+| <b>Annex A: Bibliography.....</b>                                                       | <b>25</b> |
+| <b>Annex B: Deliverables to ETSI.....</b>                                               | <b>26</b> |
+| <b>Annex C: Phase 1: Tables of experimental results .....</b>                           | <b>27</b> |
+| <b>Annex D: Phase 2: Tables of experimental results .....</b>                           | <b>32</b> |
+| <b>Annex E: Change history .....</b>                                                    | <b>34</b> |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3<sup>rd</sup> Generation Partnership Project (3GPP).
+
+The present document reports the subjective testing results concerning the performance of the GSM Half, Full, and Enhanced Full Rate speech codecs (including the estimated advantages obtainable by using Tandem Free Operation) for the simulated digital cellular telecommunications system. The experimental conditions adopted for this set of tests reflected, as much as possible, "realistic" mobile-to-mobile connections. The present document will be part of GSM specification series covering the half rate, full rate, and enhanced full rate speech traffic channels (and TFO).
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version x.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 or greater indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the document.
+
+# --- 1 Scope
+
+The present document contains the results obtained from an internationally co-ordinated subjective evaluation conducted by four laboratories to estimate the performance in mobile-to-mobile connections of the GSM half, full, and enhanced full rate speech codecs (including the expected advantages of the Tandem Free Operation), in case of interoperability in the digital cellular telecommunications system. These (listening-only) tests did not include the effects of Voice Activity Detector, Comfort Noise Insertion and the Discontinuous Transmission.
+
+# --- 2 References
+
+The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
+
+- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
+  - For a specific reference, subsequent revisions do not apply.
+  - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*.
+- [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".
+- [2] GSM 06.01: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Processing functions".
+- [3] GSM 06.10: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Transcoding".
+- [4] GSM 06.11: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Substitution and muting of lost frames for full rate speech channels".
+- [5] GSM 06.12: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Comfort noise aspect for full rate speech traffic channels".
+- [6] GSM 06.31: "Digital cellular telecommunications system (Phase 2+); Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels".
+- [7] GSM 06.32: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detector (VAD)".
+- [8] GSM 06.02: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech processing functions".
+- [9] GSM 06.06: "Digital cellular telecommunications system (Phase 2+); Half rate speech; ANSI-C code for the GSM half rate speech codec".
+- [10] GSM 06.07: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Test sequences for the GSM half rate speech codec".
+- [11] GSM 06.08: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Performance Characterization of the GSM half rate speech codec".
+- [12] GSM 06.20: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Half rate speech transcoding".
+- [13] GSM 06.21: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Substitution and muting of lost frame for half rate speech traffic channels".
+- [14] GSM 06.22: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Comfort noise aspects for half rate speech traffic channels".
+
+- [15] GSM 06.41: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels".
+- [16] GSM 06.42: "Digital cellular telecommunications system (Phase 2+); Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels".
+- [17] GSM 06.51: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech coding functions; General description".
+- [18] GSM 06.53: "Digital cellular telecommunications system (Phase 2+); ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec".
+- [19] GSM 06.54: "Digital cellular telecommunications system (Phase 2+); Test sequences for the GSM Enhanced Full Rate (EFR) speech codec".
+- [20] GSM 06.55: "Digital cellular telecommunications system (Phase 2+); Performance Characterization of the GSM Enhanced Full Rate (EFR) speech codec".
+- [21] GSM 06.60: "Digital cellular telecommunications system (Phase 2+); Enhanced Full Rate (EFR) speech transcoding".
+- [22] GSM 06.61: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Enhanced Full Rate (EFR) speech traffic channels".
+- [23] GSM 06.62: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels".
+- [24] GSM 06.81: "Digital cellular telecommunications system (Phase 2+); Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels".
+- [25] GSM 06.82: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Enhanced Full Rate (EFR) speech traffic channels".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Definitions
+
+Definition of terms used in the present document can be found in GSM 06 Series.
+
+## 3.2 Abbreviations
+
+For the purpose of the present document, the following abbreviations apply:
+
+|       |                                                      |
+|-------|------------------------------------------------------|
+| BFH   | Bad Frame Handling                                   |
+| BFI   | Bad Frame Indicator                                  |
+| CCITT | Comité Consultatif du Téléphone et du Télégraphe     |
+| CODEC | enCODer + DECoder                                    |
+| DL    | Down-Link                                            |
+| DT    | Deutsch Telekom                                      |
+| EFR   | Enhanced Full Rate                                   |
+| EID   | Error Insertion Device                               |
+| EP    | Error Pattern                                        |
+| ETS   | European Telecommunication Standard                  |
+| ETSI  | European Telecommunication Standardization Institute |
+| FR    | Full Rate                                            |
+| FTP   | File Transfer Protocol                               |
+| GSM   | Global System for Mobile communications              |
+| HR    | Half-Rate                                            |
+| IRS   | Intermediate Reference System                        |
+| ITU   | International telecommunication Union                |
+| LAN   | Local Area Network                                   |
+| M-IRS | Modified Intermediate Reference System               |
+
+|      |                                             |
+|------|---------------------------------------------|
+| PCM  | Pulse Coded Modulation                      |
+| MNRU | Modulated Noise reference Unit              |
+| SEG  | Speech Expert Group                         |
+| SMG  | Special Mobile Group                        |
+| STL  | Software Tool Library                       |
+| TFO  | Tandem Free Operation                       |
+| TR   | Technical Report                            |
+| UFI  | Unreliable Frame Indicator                  |
+| UIT  | Union Internationale des Télécommunications |
+| UL   | Up-Link                                     |
+
+For abbreviations not given in this subclause, see GSM 01.04 (ETR 350) [1].
+
+# --- 4 General
+
+Clause 5 describes the testing methodologies adopted for the internationally co-ordinated subjective evaluation of the interoperability HR-FR-EFR.
+
+Clause 6 describes the tools and procedures used by the host laboratory to produce the processed speech material (speech was added with environmental noise, when requested by the experimental design).
+
+Clause 7 describes the results obtained from the set of tests carried out by four laboratories.
+
+Clause 8 describes the conclusions that can be drawn from the analysis of all data that were produced over the two main phases of testing.
+
+# --- 5 Testing methodology
+
+A series of internationally co-ordinated subjective listening experiments were carried out in four different laboratories. These experiments were designed to investigate the performance issues surrounding interoperability across the three GSM standards; Full Rate, Half Rate, and Enhanced Full Rate GSM. The purpose of the experiments was to determine the:
+
+- 1) quality under error conditions for single encodings, providing a baseline when considering the results for tandemed connections;
+- 2) quality under tandem conditions, where all possible tandemings of the three GSM standards are characterised under a range of channel errors;
+- 3) quality with far end background noise, where both single encodings and all possible combinations of the three GSM standards are characterised under a range of channel errors;
+- 4) quality enhancements through the use of the TFO scheme;
+- 5) differences in perceived quality between the input frequency responses "flat" and "complying with ITU-T Modified IRS definition".
+
+To investigate these aspects, the testing was split into two phases:
+
+- phase 1 investigated all the possible tandem connections between the three GSM standards in environments free of background noise. Also, the potential quality benefits resulting from tandem-free operation were investigated, as well as the effects of input frequency response;
+- phase 2 investigated all the possible tandem connections with the far end was immersed in noisy environment. The noisy environments used were street noise (with a 15 dB Signal to Noise Ratio) and vehicular noise (with a 10 dB Signal to Noise Ratio). Only the Modified IRS input frequency characteristic was used.
+
+In both these phases, all of the investigations spanned the range of channel error conditions; no errors, EP1, and EP2 (corresponding to  $C/I = 10$  dB and 7 dB, respectively, with ideal Frequency Hopping). Both phases also checked the performance of each of the three GSM standards as a single encoding (i.e. no tandeming).
+
+MNRU reference conditions were included in all experiments. These serve two main purposes. The first is to ensure that a suitable range of qualities is presented to the subjects; not doing so can lead to unusual results. The second is to
+
+provide a calibration of the judgement scale, which allows for the possibility of comparing results across experiments and laboratories.
+
+Previous Technical Reports on GSM standards (GSM 06.08 and 06.55) used an input level to the speech codec of -16 dBm0 (22 dB OVL). However, in light of the recent availability of updated average distributions of speech levels in fixed networks throughout the world (source ITU-T Rec. G.117), a new nominal level of -20 dBm0 (-26 dB OVL) was used in the investigations reported here. The use of this figure, sourced from information drawn from the fixed network was selected in the absence of any reliable statistics on the levels found in mobile networks. It should also be noted that no reliable information is available on the responses of microphones adopted for use in mobile terminals. It was for this reason that the Modified IRS response (again sourced from information on the fixed network) was used in the majority of these experiments.
+
+The remainder of this clause will discuss the two phases of experimentation.
+
+## 5.1 Phase 1: Investigation under conditions free of environmental noise
+
+Phase one was designed to characterise GSM performance in noise free environments in order to provide information on the optimum performance figures likely to be obtained across the three different standards. Single encodings as well as tandemed connections between the available GSM standards, both with and without the use of the TFO scheme were investigated. The methodology used the ACR (Absolute Category Rating) method based on a 5-point rating scale, as given in ITU-T Recommendation P.800. To ensure that the maximum amount of information could be extracted from the experiment, the following precautions were taken in the experiment design:
+
+- to ensure that all the subjects started the experiments with similar levels of expectation, a standard set of instructions was given to each subject, and they were all given the same set of practice trials at the start of the experiment. These practice trials covered a range of conditions representative of the qualities in the main body of the experiment. The scores from the practice trials are recorded, but are not used in any further analysis, and hence are not reported on in the present document;
+- it is known, particularly in ACR tests, that the order in which the test material is presented to the subjects can have an effect on the results due to carry-over effects. Three different presentation orders were therefore used to minimise this;
+- subjects can experience fatigue if listening sessions are too long, leading to an increase in the inherent variability of the results. The phase 1 tests, required subjects to spend approximately one hour in the experiment. For the reasons given, this was split into three sessions, each of approximately 20 minutes separated by short breaks.
+
+The results from this phase are discussed in subclauses 7.1 (single encoding), 7.2 (tandem operation), 7.4 (TFO enhancements), and 7.5 (input frequency response).
+
+## 5.2 Phase 2: Investigation under conditions with far end environmental noise
+
+Phase two was designed to evaluate the GSM algorithms with regard to transmission quality in the presence of far end background noise. Two types of noise were investigated, street noise at a signal to noise ratio of 15 dB and vehicle noise at a signal to noise ratio of 10 dB. The phase was split into two experiments, each of which investigated one of the noise types. Other than this difference, these experiments were identical in design. The methodology used the DCR (Degradation Category Rating) method, where the opinions given by subjects are a measure of the perceived difference between a quality reference and a degraded sample. To ensure that the maximum amount of information could be extracted from the experiment, the following precautions were taken in the experiment design:
+
+- when investigating far end background noise, the effects of the noise itself can dominate the results to such an extent that the influence of the factors of interest are hidden. The Degradation Category Rating method was selected to minimise this, as was the decision to place each of the two different types of noise in separate experiments;
+- to ensure that all the subjects started the experiments with similar levels of expectation, a standard set of instructions was given to each subject, and they were all given the same set of practice trials at the start of the experiment. These practice trials covered a range of conditions representative of the qualities in the main body of the experiment. The scores from the practice trials are recorded, but are not used in any further analysis, and hence are not reported on in the present document;
+
+- three different presentation orders were used to minimise the possibility of carry-over effects;
+- subjects can experience fatigue if listening sessions are too long, leading to an increase in the inherent variability of the results. The phase 2 tests, required subjects to spend approximately one hour 15 minutes in the experiment. For the reasons given, this was split into four sessions, each of just over 20 minutes separated by short breaks.
+
+The results from this phase are discussed in subclause 7.3.
+
+# --- 6 Test set-up
+
+## Overview of the Host Lab Simulation Tool
+
+In this section the different software components that are used by the Host Lab simulation. We present also the way they are used by the simulator.
+
+### The software components
+
+### The UIT-T STL96
+
+In 1990 a group was set up within the CCITT to develop common software tools to help the development of speech coding standards. The first formal release of the library was the STL92. Matra Communication had used "IUT-T Software Tool Library Manual," ITU-T Users' Group on Software Tools, Geneva, May 1996, to develop the Software Tool used for the optimization of the Half Rate GSM codec.
+
+It includes many different tools but more precisely all the tools needed to properly condition speech signals. It was mainly used for pre-processing and post-processing. However it was also used for A-Law PCM and MNRU.
+
+### The Speech codecs
+
+The three speech codecs were simulated using 16-bit fixed point libraries that are part of the codecs' source code.
+
+The test vectors of the three GSM speech codecs were successfully processed by their respective codecs.
+
+#### The Full Rate GSM
+
+The Full-Rate GSM simulation used (ETSI GSM Recommendation 06.10, "GSM full-rate speech transcoding") has been developed in Matra's Speech Processing Department. It was found easier to use this version rather than the one which is provided in STL96. Bad Frame Handling was included in the channel decoder function delivered by Nokia.
+
+#### The Half-Rate GSM
+
+The Half-Rate simulation used is based on that described in ETSI GSM Recommendation 06.20, "GSM half-rate speech transcoding". It was checked that it corresponds to the latest version available on the ETSI ftp server. The Bad Frame Handling simulation was that provided in ETSI GSM Recommendation 06.06, "ANSI-C code for the GSM half rate speech codec".
+
+#### The Enhanced Full Rate GSM
+
+The Enhanced Full Rate (ETSI GSM Recommendation 06.60, "GSM enhanced full-rate speech transcoding") simulation was based on versions 5.0 and 5.1 of ETSI GSM Recommendation 06.53, , "ANSI-C code for the GSM enhanced full rate codec"). Version 5.0 was upgraded taking into account the changes brought by version 5.1, i.e. initialization in the pulse search and modification of the basic operators. The pre-channel coding and the post-channel decoding of version 5.0 were kept.
+
+#### The G.711 PCM codec
+
+A-Law PCM coding was performed using the functions provided in the STL96 ["IUT-T Software Tool Library Manual," ITU-T Users' Group on Software Tools, Geneva, May 1996].
+
+### The Channel codecs
+
+#### The Full Rate GSM
+
+It was agreed that the channel codec and above all the error Concealment would have to be "state-of-the-art" as it had already been done for the pre-qualification test of the EFR. In consequence it was asked to Nokia if they could, as they had already done for the pre-qualification tests, deliver such a simulation to the Host Lab.
+
+An NDA was signed between Nokia and Matra Communication to enable the use of these functions. Since Sun workstation are used in both companies, it was decided to exchange object code compiled for such systems.
+
+#### The Half Rate GSM
+
+An NDA was signed between Motorola and Matra Communication in order to use the Channel codec simulation that has already been used during the complexity estimation and the Optimization of the Half Rate GSM.
+
+The interfaces were updated with the help of Eric Winter of Motorola.
+
+#### The Enhanced full Rate GSM
+
+Matra Communication received together with the source code of the EFR v1.4 speech codec the source code of the channel codec. This was the one that has been used so far to measure the performances of the EFR codec in error conditions.
+
+Therefore it was decided to use it in the Host Lab simulation.
+
+#### The Modulated Noise Reference Unit (MNRU)
+
+The so-called "Duo-MNRU" [11] [12] tool of STL96 was included in the Host LAB simulation.
+
+## 6.1 Host Lab processing for the evaluation of HR-FR-EFR interoperability (phase 1)
+
+The processing carried out by Matra Communication under contract of the ETSI were made using a Host Lab simulator. This section contains the description of the Host Lab simulator.
+
+### Modified IRS filtering procedure
+
+The first problem in phase 1A was due to a wrong interpretation of the test plan by the Host Lab. The « HQN » key word of the command line was wrongly interpreted as "the spectral characteristic must be flat".
+
+We replace the « HQN » key word by « MIRS » in the test plan file and we created a pre-processing procedure to filter and adjust the level of the speech material. This procedure is based on the function available in the STL96. Figure 1 shows the scheme of this pre-processing.
+
+![Figure 1: Scheme of the pre-processing procedure: M-IRS filtering and level adjustment. The diagram shows a flow from left to right: an input signal (16 kHz, 16 bit unweighted signals, -30 dBov) represented by a cylinder icon, followed by a block labeled 'FIR - M-IRS' containing a trapezoidal filter shape, then a block labeled 'P.56 speech voltmeter' with '-30 dBov' written above it, and finally an output signal (16 kHz, 16 bit M-IRS signals, -30 dBov) represented by another cylinder icon.](fe61ee8618403cf584b2e28c4bada03a_img.jpg)
+
+Figure 1: Scheme of the pre-processing procedure: M-IRS filtering and level adjustment. The diagram shows a flow from left to right: an input signal (16 kHz, 16 bit unweighted signals, -30 dBov) represented by a cylinder icon, followed by a block labeled 'FIR - M-IRS' containing a trapezoidal filter shape, then a block labeled 'P.56 speech voltmeter' with '-30 dBov' written above it, and finally an output signal (16 kHz, 16 bit M-IRS signals, -30 dBov) represented by another cylinder icon.
+
+**Figure 1: Scheme of the pre-processing procedure: M-IRS filtering and level adjustment**
+
+## 6.2 Error concealment for TCH/FS
+
+The second problem in phase 1A concerns the Error Concealment function included in the TCH - FS Channel Codec Libraries. During phase 1A this function has been implicitly switched off by the provider. As decided during the SEG #8 meeting the provider sent to Matra a correct version of the libraries. This version works correctly for all the possible channel simulations (with or without noise insertion). In the demo tape delivered by Matra (cf. SMG11 Tdoc 18/96) we provided some examples of sentences in EP1 and EP2 conditions obtained by using the old and the new versions of these libraries.
+
+## 6.3 Control of codec simulation
+
+All the codecs used in this simulation have been tested using the test vectors defined in the GSM recommendations. When the Host Lab simulator is used in the « test mode » the pre-processing, post-processing and channel coding procedure are bypassed as illustrated by figure 2. No errors have been observed in the output file.
+
+![Figure 2: Scheme of the testing procedure using the test vectors. The diagram shows a flow from Test vectors to Preprocessing, then to Speech Encoder, then to Channel Encoder, then to EID, then to Channel Decoder, then to Speech Decoder, then to Postprocessing, and finally to Decoder output for test vectors. A Test plan verification mode is shown as a control input to the Speech Encoder and Speech Decoder. A cylinder representing data storage is shown between the Speech Encoder and Speech Decoder, labeled Encoder output for test vectors.](7e670a2b556b53ea9002dfff3a420e08_img.jpg)
+
+```
+graph TD; TV[Test vectors] --> P[Preprocessing]; P --> SE[Speech Encoder]; SE --> CE[Channel Encoder]; CE --> EID[EID]; EID --> CD[Channel Decoder]; CD --> SD[Speech Decoder]; SD --> Post[Postprocessing]; Post --> DO[Decoder output for test vectors]; TPVM[Test plan verification mode] --> SE; TPVM --> SD; EO[Encoder output for test vectors] --> SD;
+```
+
+Figure 2: Scheme of the testing procedure using the test vectors. The diagram shows a flow from Test vectors to Preprocessing, then to Speech Encoder, then to Channel Encoder, then to EID, then to Channel Decoder, then to Speech Decoder, then to Postprocessing, and finally to Decoder output for test vectors. A Test plan verification mode is shown as a control input to the Speech Encoder and Speech Decoder. A cylinder representing data storage is shown between the Speech Encoder and Speech Decoder, labeled Encoder output for test vectors.
+
+Figure 2: Scheme of the testing procedure using the test vectors
+
+## 6.4 Pre-processing and post-processing procedure
+
+Figure 3 and figure 4 show the frequency response of the M-IRS filtering module and the frequency response for the pre and post processing. The behaviours of these frequency responses are closed to the frequency responses presented in the STL96 documents.
+
+![Figure 3: Frequency response of the M-IRS filtering module. The graph shows gain in dB on the y-axis (ranging from 20 to 110) against frequency in Hz on a logarithmic x-axis (ranging from 10^1 to 10^4). The response is relatively flat between 100 Hz and 1000 Hz, with a sharp roll-off above 1000 Hz.](42ff8b598a0818ca8b6ef30850ad5f4e_img.jpg)
+
+Figure 3: Frequency response of the M-IRS filtering module. The graph shows gain in dB on the y-axis (ranging from 20 to 110) against frequency in Hz on a logarithmic x-axis (ranging from 10^1 to 10^4). The response is relatively flat between 100 Hz and 1000 Hz, with a sharp roll-off above 1000 Hz.
+
+**Figure 3: Frequency response of the M-IRS filtering module**
+
+![Figure 4: Frequency response of the global simulator filtering modules. The graph shows gain in dB on the y-axis (ranging from 10 to 100) against frequency in Hz on a logarithmic x-axis (ranging from 10^1 to 10^4). The response is relatively flat between 100 Hz and 1000 Hz, with a sharp roll-off above 1000 Hz.](602ada2a012ff3cc38d91de2eec5b450_img.jpg)
+
+Figure 4: Frequency response of the global simulator filtering modules. The graph shows gain in dB on the y-axis (ranging from 10 to 100) against frequency in Hz on a logarithmic x-axis (ranging from 10^1 to 10^4). The response is relatively flat between 100 Hz and 1000 Hz, with a sharp roll-off above 1000 Hz.
+
+**Figure 4: Frequency response of the global simulator filtering modules**
+
+## 6.5 Conclusion of Phase 1
+
+All the accessible components of the Host Lab simulator have been tested by Matra. No particular problem was observed during this phase of test.
+
+## 6.6 Host Lab processing for the evaluation of HR-FR-EFR interoperability (phase 2)
+
+The phase 2 of interoperability test have been carried out to evaluate the performances of GSM speech codecs in environmental noise conditions. The present document describes the noise mixing procedure used to produce the speech material.
+
+### Noise mixing process
+
+The original speech material used during phase 1 of test has been the starting point to produce the input databases for phase 2. The procedure used to produce these samples is the following (cf. figure 6). First of all the sources (speech and noise) are filtered using the FIR version of Modified IRS filter (M-IRS). Then they are gain-scaled to obtain a -30 dBov level for speech samples and the (-30-SNR) dBov level for noise source. The value of SNR is dependent on the noise characteristic: this value is fixed to 15 dB for street noise and 10 dB for car noise.
+
+![Figure 6: Noise and speech mixing procedure diagram. The diagram shows two parallel processing paths for speech and noise. The top path takes '16 kHz, 16 bit unweighted signals, -30 dBov' through an 'FIR - M-IRS' filter, then scales it to '-30 dBov' using a 'P.56 speech voltmeter'. The bottom path takes '16 kHz, 16 bit unweighted noise signals' through an 'FIR - M-IRS' filter, then scales it to '(-30-SNR) dBov' using an 'RMS mesure'. An 'SNR' block is shown between the two scaling stages. Both scaled signals are then summed at a circular node with a '+' sign. The final output is '16 kHz, 16 bit M-IRS signals+noise, ~ -30 dBov' for speech and '16 kHz, 16 bit M-IRS noise, (-30-SNR) dBov' for noise.](410562339ce067fdc6fa41940c118658_img.jpg)
+
+Figure 6: Noise and speech mixing procedure diagram. The diagram shows two parallel processing paths for speech and noise. The top path takes '16 kHz, 16 bit unweighted signals, -30 dBov' through an 'FIR - M-IRS' filter, then scales it to '-30 dBov' using a 'P.56 speech voltmeter'. The bottom path takes '16 kHz, 16 bit unweighted noise signals' through an 'FIR - M-IRS' filter, then scales it to '(-30-SNR) dBov' using an 'RMS mesure'. An 'SNR' block is shown between the two scaling stages. Both scaled signals are then summed at a circular node with a '+' sign. The final output is '16 kHz, 16 bit M-IRS signals+noise, ~ -30 dBov' for speech and '16 kHz, 16 bit M-IRS noise, (-30-SNR) dBov' for noise.
+
+**Figure 6: Noise and speech mixing procedure**
+
+The gain scaling values are obtained using the STL'96 speech voltmeter for the speech samples (according with ITU-T Recommendation. P.56) and using RMS measure for noise files.
+
+The files filtered and scaled are then mixed by summing the samples. An automatic control of overload is performed during the mixing procedure. If a saturation occurred an expert listener checked if the quality of the speech + noise sample is acceptable. If the clipping effect was annoying the level of the speech after the M-IRS filter was down-scaled in a maximum range of 1 dB and the mixing procedure is restarted. During the mixing procedure any saturation has been observed.
+
+## 6.7 Processing
+
+The data-bases obtained by the noise mixing procedure are processed according to the test using the Host-Lab simulator.
+
+## 6.8 Conclusion of Phase 2
+
+During phase 2, test have been performed without any problem. Quality of processed speech has been checked by MATRA speech expert. The processed files were sent to the listening test laboratories in January 1997, according to the time schedule defined during the first SMG11 meeting.
+
+# 7 Summary of results
+
+The test results obtained from the subjective evaluation of the interoperability HR-FR-EFR, considering the different combinations of the three GSM standards, and also the so called TFO (Tandem-Free or Transcoding-Free Operation), are summarised in the following sub-clauses.
+
+## 7.1 Quality under error conditions
+
+Statistical analysis and significance tests (at 95 % confidence level) on the full set of raw data were performed in terms of Mean Opinion Scores (MOS) and confidence intervals (C. I.), that were calculated to interpret the statistical significance of differences between the given scores.
+
+An analysis of variance (using the General Linear Model) of all opinion scores was carried out to show which factors under test (laboratories, talkers, order of presentation, experimental conditions, and listeners) did account for the
+
+subjective judgements. The analysis showed that all factors were significant; anyway, the 'common behaviour' showed by all the individual results, justified the decision of amalgamating the data coming from the different laboratories.
+
+A statistical method based on a simple Tukey's Honestly Significant Difference (HSD) procedure, by utilising the measure MSE obtained from the analysis of variance, at the 95% confidence level, was used to accept or reject the hypothesis that the average score obtained by a certain condition was "significantly" (in statistical sense) worse than another one.
+
+The number of votes cast by each listener was: 4 (talkers) x 48 (conditions) = **192**. There were 24 listeners (e.g. 12 male and 12 female) per experiment, organized in a number of sub-groups, e.g. 3 sub-groups made up of 8 persons each, each sub-group of listeners hearing the sequence in a different order. The number of votes per condition was: 4 (talkers) x 4 (languages/countries) x 24 (subjects) = **384**.
+
+A primary elaboration of data was performed for the individual raw data, averaging Male and Female talkers (see Annex C for Tables of experimental results).
+
+The following figure was obtained for the "reference conditions" inserted in the tests, i.e. the MNRU (Modulated Noise Reference Unit) and the "Direct" signal. The figure correlates Mean Opinion Scores (MOS, Yq) with Equivalent Q (dB) values, and is usually considered the "transfer curve" to convert data coming from different countries, i.e. taking into account cultural, or language, or other differences among laboratories conducting the "same" subjective test.
+
+![Line graph showing Mean Opinion Scores (Yq) versus Equivalent Q (dB) for MNRU and Direct signals. The Y-axis (Yq) ranges from 1 to 5. The X-axis (dB) has values 6, 12, 18, 24, 30, and Dir. The data points show a linear increase in Yq as dB increases, starting at approximately (6, 1.5) and ending at (Dir, 4.8).](b8261918596971c3801af23435c5ea50_img.jpg)
+
+**MNRU & Direct**
+
+| dB  | Yq  |
+|-----|-----|
+| 6   | 1.5 |
+| 12  | 2.2 |
+| 18  | 3.0 |
+| 24  | 3.8 |
+| 30  | 4.5 |
+| Dir | 4.8 |
+
+Line graph showing Mean Opinion Scores (Yq) versus Equivalent Q (dB) for MNRU and Direct signals. The Y-axis (Yq) ranges from 1 to 5. The X-axis (dB) has values 6, 12, 18, 24, 30, and Dir. The data points show a linear increase in Yq as dB increases, starting at approximately (6, 1.5) and ending at (Dir, 4.8).
+
+The effect of errors on the three algorithms, HR FR, EFR, in single encoding and for quiet conditions is depicted in the following figure.
+
+![Bar chart showing Mean Opinion Scores (Yq) for three algorithms (HR, FR, EFR) under three error conditions (EP0, EP1, EP2). The Y-axis (Yq) ranges from 0 to 5. The X-axis shows the algorithms HR, FR, and EFR. The legend indicates EP0 (blue), EP1 (maroon), and EP2 (yellow). For HR, scores are approximately 4.0, 3.8, 3.5. For FR, scores are approximately 3.8, 3.5, 2.8. For EFR, scores are approximately 4.5, 4.2, 3.8.](70f5f44cb855bbb0c203c00187b2113e_img.jpg)
+
+**Single encoding**
+
+| Algorithm | EP0 | EP1 | EP2 |
+|-----------|-----|-----|-----|
+| HR        | 4.0 | 3.8 | 3.5 |
+| FR        | 3.8 | 3.5 | 2.8 |
+| EFR       | 4.5 | 4.2 | 3.8 |
+
+Bar chart showing Mean Opinion Scores (Yq) for three algorithms (HR, FR, EFR) under three error conditions (EP0, EP1, EP2). The Y-axis (Yq) ranges from 0 to 5. The X-axis shows the algorithms HR, FR, and EFR. The legend indicates EP0 (blue), EP1 (maroon), and EP2 (yellow). For HR, scores are approximately 4.0, 3.8, 3.5. For FR, scores are approximately 3.8, 3.5, 2.8. For EFR, scores are approximately 4.5, 4.2, 3.8.
+
+## 7.2 Quality under tandeming conditions
+
+Tandeming conditions were tested in EP0, EP1 and EP2 error conditions (see Annex C for tables of results). The following figures clearly indicate the performance of HR, FR, and EFR when interworking with each of the other standards (i.e. the combinations of codecs in the figures should be read: Coder in the Legend is tandemed with codec in the abscissa). The following figures were obtained from the experiments that adopted the Modified IRS input frequency characteristics.
+
+EP0 Tandem
+
+![Line graph titled 'EP0 Tandem' showing quality scores for HR, FR, and EFR codecs under EP0 error conditions. The x-axis lists the codecs (HR, FR, EFR) and the y-axis shows quality scores from 0 to 5. Three lines represent different tandeming combinations: HR-> (blue diamonds), FR-> (magenta squares), and EFR-> (orange triangles).](239211fa511b4ffa685b54b5132ec927_img.jpg)
+
+| Coder (Legend) | HR  | FR  | EFR |
+|----------------|-----|-----|-----|
+| HR- >          | 3.2 | 3.0 | 3.8 |
+| FR- >          | 3.3 | 3.2 | 3.8 |
+| EFR- >         | 3.7 | 3.6 | 4.3 |
+
+Line graph titled 'EP0 Tandem' showing quality scores for HR, FR, and EFR codecs under EP0 error conditions. The x-axis lists the codecs (HR, FR, EFR) and the y-axis shows quality scores from 0 to 5. Three lines represent different tandeming combinations: HR-> (blue diamonds), FR-> (magenta squares), and EFR-> (orange triangles).
+
+EP1 Tandem
+
+![Line graph titled 'EP1 Tandem' showing quality scores for HR, FR, and EFR codecs under EP1 error conditions. The x-axis lists the codecs (HR, FR, EFR) and the y-axis shows quality scores from 0 to 3.5. Three lines represent different tandeming combinations: HR-> (blue diamonds), FR-> (magenta squares), and EFR-> (orange triangles).](4a8166688ed7276efb173f550ba47eb4_img.jpg)
+
+| Coder (Legend) | HR  | FR  | EFR |
+|----------------|-----|-----|-----|
+| HR- >          | 2.7 | 2.6 | 3.2 |
+| FR- >          | 2.8 | 2.7 | 3.1 |
+| EFR- >         | 3.2 | 2.9 | 3.4 |
+
+Line graph titled 'EP1 Tandem' showing quality scores for HR, FR, and EFR codecs under EP1 error conditions. The x-axis lists the codecs (HR, FR, EFR) and the y-axis shows quality scores from 0 to 3.5. Three lines represent different tandeming combinations: HR-> (blue diamonds), FR-> (magenta squares), and EFR-> (orange triangles).
+
+![Line graph for EP2 Tandem showing HR, FR, and EFR values across HR, FR, and EFR categories. The y-axis ranges from 0 to 2.5. HR (blue diamonds) starts at ~2.2, dips to ~1.8 at FR, and rises to ~2.2 at EFR. FR (magenta squares) starts at ~2.1, dips to ~1.7 at FR, and rises to ~2.2 at EFR. EFR (orange triangles) starts at ~2.3, dips to ~2.1 at FR, and rises to ~2.4 at EFR.](cbc4516eb885829fe8c9dabc0946dcbe_img.jpg)
+
+### EP2 Tandem
+
+| Category | HR- > | FR- > | EFR- > |
+|----------|-------|-------|--------|
+| HR       | 2.2   | 2.1   | 2.3    |
+| FR       | 1.8   | 1.7   | 2.1    |
+| EFR      | 2.2   | 2.2   | 2.4    |
+
+Line graph for EP2 Tandem showing HR, FR, and EFR values across HR, FR, and EFR categories. The y-axis ranges from 0 to 2.5. HR (blue diamonds) starts at ~2.2, dips to ~1.8 at FR, and rises to ~2.2 at EFR. FR (magenta squares) starts at ~2.1, dips to ~1.7 at FR, and rises to ~2.2 at EFR. EFR (orange triangles) starts at ~2.3, dips to ~2.1 at FR, and rises to ~2.4 at EFR.
+
+The following figures were obtained from the experiments adopting the flat input frequency characteristics.
+
+![Line graph for EP0 Tandem showing HR, FR, and EFR values across HR, FR, and EFR categories. The y-axis ranges from 0 to 5. All three series (HR: blue diamonds, FR: magenta squares, EFR: yellow triangles) are nearly flat, starting around 3.5 and ending around 4.0.](fc857414626a8d94d132e12d9afe52a4_img.jpg)
+
+### EP0 Tandem
+
+| Category | HR- > | FR- > | EFR- > |
+|----------|-------|-------|--------|
+| HR       | 3.5   | 3.5   | 3.8    |
+| FR       | 3.6   | 3.6   | 3.9    |
+| EFR      | 3.8   | 3.8   | 4.0    |
+
+Line graph for EP0 Tandem showing HR, FR, and EFR values across HR, FR, and EFR categories. The y-axis ranges from 0 to 5. All three series (HR: blue diamonds, FR: magenta squares, EFR: yellow triangles) are nearly flat, starting around 3.5 and ending around 4.0.
+
+![Line graph for EP1 Tandem showing HR and EFR values across HR and EFR categories. The y-axis ranges from 0 to 4. HR (blue diamonds) starts at ~2.8 and rises to ~3.2 at EFR. EFR (yellow triangles) starts at ~3.2 and rises to ~3.8 at EFR.](011fecb4a85637472f0c697a6cbdb15d_img.jpg)
+
+### EP1 Tandem
+
+| Category | HR- > | EFR- > |
+|----------|-------|--------|
+| HR       | 2.8   | 3.2    |
+| EFR      | 3.2   | 3.8    |
+
+Line graph for EP1 Tandem showing HR and EFR values across HR and EFR categories. The y-axis ranges from 0 to 4. HR (blue diamonds) starts at ~2.8 and rises to ~3.2 at EFR. EFR (yellow triangles) starts at ~3.2 and rises to ~3.8 at EFR.
+
+![Line graph for EP2 Tandem showing HR and EFR values across HR and EFR categories. The y-axis ranges from 0 to 3. HR (blue diamonds) starts at ~2.2 and rises to ~2.4 at EFR. EFR (yellow triangles) starts at ~2.4 and rises to ~2.8 at EFR.](a430996a9e8993deb0c6b25da234744b_img.jpg)
+
+### EP2 Tandem
+
+| Category | HR- > | EFR- > |
+|----------|-------|--------|
+| HR       | 2.2   | 2.4    |
+| EFR      | 2.4   | 2.8    |
+
+Line graph for EP2 Tandem showing HR and EFR values across HR and EFR categories. The y-axis ranges from 0 to 3. HR (blue diamonds) starts at ~2.2 and rises to ~2.4 at EFR. EFR (yellow triangles) starts at ~2.4 and rises to ~2.8 at EFR.
+
+## 7.3 Quality with far end background noise
+
+Any of the listening laboratories had to report their results from Exp#1 or Exp#2 in a way that the effects of environmental noise, error pattern and transcoding of the different standards are documented as DMOS values with their confidence interval (two-tailed t-distribution with  $\alpha=0,05$ ).
+
+An individual analysis of data was conducted by each participant laboratory (see Bibliography). Tables of "averaged" results are given in DMOS, and confidence intervals. An analysis of variance revealed that conditions, talkers and groups of listeners were highly significant factors ( $p < 0,0001$ ) in both experiments.
+
+A global analysis over the laboratories was performed and results were produced in a similar form to the one produced for global analysis for Phase 1 of testing (see Annex D for Tables of results).
+
+In Exp. 1 the two laboratories were not significantly different each other, while in Exp. 2 the LAB factor was a highly significant one. The Tukey's minimum significant difference between DMOS values was around 0,35 in both experiments, such value being used to group conditions that were not "statistically" different in the same "class". The following figures illustrate the results obtained during Phase 2 of testing.
+
+**Street noise added to speech (S/N = 15 dB)**
+
+![Line graph showing DMOS values for street noise added to speech at S/N = 15 dB. The x-axis represents dB levels (6, 12, 18, 24, 30, D, DN) and the y-axis represents DMOS (1 to 5). The data points show an increase in DMOS from approximately 1.8 at 6 dB to a peak of about 4.8 at 30 dB, followed by a slight decrease to about 4.5 at DN.](dbc1673750fd53d4203f4d93963fdab6_img.jpg)
+
+**MNRU & Direct**
+
+**DMOS**
+
+| dB | DMOS |
+|----|------|
+| 6  | 1.8  |
+| 12 | 2.5  |
+| 18 | 4.2  |
+| 24 | 4.7  |
+| 30 | 4.8  |
+| D  | 4.8  |
+| DN | 4.5  |
+
+**dB**
+
+Line graph showing DMOS values for street noise added to speech at S/N = 15 dB. The x-axis represents dB levels (6, 12, 18, 24, 30, D, DN) and the y-axis represents DMOS (1 to 5). The data points show an increase in DMOS from approximately 1.8 at 6 dB to a peak of about 4.8 at 30 dB, followed by a slight decrease to about 4.5 at DN.
+
+**Vehicular noise added to speech (S/N = 10 dB)**
+
+![Line graph showing DMOS values for vehicular noise added to speech at S/N = 10 dB. The x-axis represents dB levels (6, 12, 18, 24, 30, D, DN) and the y-axis represents DMOS (1 to 5). The data points show an increase in DMOS from approximately 1.8 at 6 dB to a peak of about 4.8 at 30 dB, followed by a slight decrease to about 4.5 at DN.](a3ee9a6f9fa9251ee0cac2d16e67e620_img.jpg)
+
+**MNRU & Direct**
+
+**DMOS**
+
+| dB | DMOS |
+|----|------|
+| 6  | 1.8  |
+| 12 | 2.5  |
+| 18 | 4.2  |
+| 24 | 4.7  |
+| 30 | 4.8  |
+| D  | 4.8  |
+| DN | 4.5  |
+
+**dB**
+
+Line graph showing DMOS values for vehicular noise added to speech at S/N = 10 dB. The x-axis represents dB levels (6, 12, 18, 24, 30, D, DN) and the y-axis represents DMOS (1 to 5). The data points show an increase in DMOS from approximately 1.8 at 6 dB to a peak of about 4.8 at 30 dB, followed by a slight decrease to about 4.5 at DN.
+
+### **Street noise added to speech (S/N = 15 dB)**
+
+### **Single encoding (DMOS)**
+
+![Bar chart showing DMOS scores for HR, FR, and EFR encodings with street noise (S/N = 15 dB). EP0 (blue) scores are approximately 3.7, 4.0, and 4.3. EP1 (maroon) scores are approximately 3.7, 3.8, and 3.9. EP2 (yellow) scores are approximately 3.3, 3.2, and 3.5.](df7cb4ea9bd6c3f445f3e264773b125f_img.jpg)
+
+| Encoding | EP0 | EP1 | EP2 |
+|----------|-----|-----|-----|
+| HR       | 3.7 | 3.7 | 3.3 |
+| FR       | 4.0 | 3.8 | 3.2 |
+| EFR      | 4.3 | 3.9 | 3.5 |
+
+Bar chart showing DMOS scores for HR, FR, and EFR encodings with street noise (S/N = 15 dB). EP0 (blue) scores are approximately 3.7, 4.0, and 4.3. EP1 (maroon) scores are approximately 3.7, 3.8, and 3.9. EP2 (yellow) scores are approximately 3.3, 3.2, and 3.5.
+
+### **Vehicular noise added to speech (S/N = 10 dB)**
+
+#### **Single encoding (DMOS)**
+
+![Bar chart showing DMOS scores for HR, FR, and EFR encodings with vehicular noise (S/N = 10 dB). EP0 (blue) scores are approximately 3.6, 3.9, and 4.4. EP1 (maroon) scores are approximately 3.5, 3.7, and 4.2. EP2 (yellow) scores are approximately 3.2, 3.0, and 3.6.](ef177a7090c8da3fcd9beb78e78fd68f_img.jpg)
+
+| Encoding | EP0 | EP1 | EP2 |
+|----------|-----|-----|-----|
+| HR       | 3.6 | 3.5 | 3.2 |
+| FR       | 3.9 | 3.7 | 3.0 |
+| EFR      | 4.4 | 4.2 | 3.6 |
+
+Bar chart showing DMOS scores for HR, FR, and EFR encodings with vehicular noise (S/N = 10 dB). EP0 (blue) scores are approximately 3.6, 3.9, and 4.4. EP1 (maroon) scores are approximately 3.5, 3.7, and 4.2. EP2 (yellow) scores are approximately 3.2, 3.0, and 3.6.
+
+### **Street noise added to speech (S/N = 15 dB)**
+
+![Bar chart titled 'Overview of all results' for Street noise added to speech (S/N = 15 dB). The Y-axis is labeled 'Y/DMOS+CI' and ranges from 1 to 5. The X-axis shows various conditions: HR, HR>HR, HR>FR, HR>EFR, FR, FR>HR, FR>FR, FR>EFR, EFR, EFR>HR, EFR>FR, EFR>EFR. The legend includes CNET:EP0, Nortel:EP0, CNET:EP1, Nortel:EP1, CNET:EP2, and Nortel:EP2.](3468bcffa38de23cef94bfb460ccb301_img.jpg)
+
+**Overview of all results**
+
+Y/DMOS+CI
+
+Legend: CNET:EP0, Nortel:EP0, CNET:EP1, Nortel:EP1, CNET:EP2, Nortel:EP2
+
+| Condition | CNET:EP0 | Nortel:EP0 | CNET:EP1 | Nortel:EP1 | CNET:EP2 | Nortel:EP2 |
+|-----------|----------|------------|----------|------------|----------|------------|
+| HR        | 3.6      | 3.5        | 3.7      | 3.4        | 3.4      | 2.9        |
+| HR>HR     | 2.5      | 2.6        | 2.2      | 2.4        | 1.8      | 1.8        |
+| HR>FR     | 3.2      | 3.3        | 2.6      | 2.6        | 2.0      | 2.1        |
+| HR>EFR    | 3.0      | 3.2        | 2.5      | 2.9        | 1.8      | 2.0        |
+| FR        | 4.2      | 3.7        | 3.8      | 3.5        | 3.2      | 2.9        |
+| FR>HR     | 3.0      | 3.0        | 2.5      | 2.6        | 1.9      | 1.8        |
+| FR>FR     | 3.7      | 3.3        | 3.1      | 2.8        | 2.2      | 2.3        |
+| FR>EFR    | 3.8      | 3.7        | 3.0      | 2.9        | 1.8      | 2.2        |
+| EFR       | 4.3      | 4.1        | 3.7      | 3.9        | 3.4      | 3.3        |
+| EFR>HR    | 3.4      | 3.3        | 2.8      | 2.8        | 2.0      | 2.1        |
+| EFR>FR    | 3.8      | 3.7        | 3.0      | 3.0        | 1.8      | 2.1        |
+| EFR>EFR   | 3.9      | 3.7        | 2.8      | 2.9        | 1.9      | 2.1        |
+
+Bar chart titled 'Overview of all results' for Street noise added to speech (S/N = 15 dB). The Y-axis is labeled 'Y/DMOS+CI' and ranges from 1 to 5. The X-axis shows various conditions: HR, HR>HR, HR>FR, HR>EFR, FR, FR>HR, FR>FR, FR>EFR, EFR, EFR>HR, EFR>FR, EFR>EFR. The legend includes CNET:EP0, Nortel:EP0, CNET:EP1, Nortel:EP1, CNET:EP2, and Nortel:EP2.
+
+### **Vehicular noise added to speech (S/N = 10 dB)**
+
+![Bar chart titled 'Overview of all results' for Vehicular noise added to speech (S/N = 10 dB). The Y-axis is labeled 'Y/DMOS +CI' and ranges from 1.00 to 5.00. The X-axis shows various conditions: HR, HR>HR, HR>FR, HR>EFR, FR, FR>HR, FR>FR, FR>EFR, EFR, EFR>HR, EFR>FR, EFR>EFR. The legend includes CSELT:EP0, DTAG:EP0, CSELT:EP1, DTAG:EP1, CSELT:EP2, and DTAG:EP2.](3e0c2bf6c51c575d096c7fc95c1e8454_img.jpg)
+
+**Overview of all results**
+
+Y/DMOS +CI
+
+Legend: CSELT:EP0, DTAG:EP0, CSELT:EP1, DTAG:EP1, CSELT:EP2, DTAG:EP2
+
+| Condition | CSELT:EP0 | DTAG:EP0 | CSELT:EP1 | DTAG:EP1 | CSELT:EP2 | DTAG:EP2 |
+|-----------|-----------|----------|-----------|----------|-----------|----------|
+| HR        | 3.9       | 3.0      | 3.7       | 3.0      | 3.2       | 2.9      |
+| HR>HR     | 2.5       | 2.2      | 2.2       | 2.0      | 1.6       | 1.9      |
+| HR>FR     | 3.1       | 3.0      | 3.0       | 2.4      | 2.0       | 2.2      |
+| HR>EFR    | 3.2       | 2.8      | 3.1       | 2.3      | 1.9       | 2.0      |
+| FR        | 4.1       | 3.5      | 3.8       | 3.3      | 3.0       | 2.7      |
+| FR>HR     | 3.2       | 2.6      | 2.6       | 2.4      | 1.9       | 1.8      |
+| FR>FR     | 3.7       | 2.9      | 2.9       | 2.7      | 2.1       | 2.1      |
+| FR>EFR    | 4.1       | 3.1      | 3.1       | 2.7      | 1.9       | 2.1      |
+| EFR       | 4.7       | 3.8      | 4.5       | 3.7      | 3.8       | 3.2      |
+| EFR>HR    | 3.5       | 2.7      | 2.9       | 2.4      | 1.7       | 2.1      |
+| EFR>FR    | 4.1       | 3.2      | 3.2       | 2.8      | 2.2       | 2.3      |
+| EFR>EFR   | 4.3       | 3.4      | 3.4       | 2.9      | 1.9       | 2.0      |
+
+Bar chart titled 'Overview of all results' for Vehicular noise added to speech (S/N = 10 dB). The Y-axis is labeled 'Y/DMOS +CI' and ranges from 1.00 to 5.00. The X-axis shows various conditions: HR, HR>HR, HR>FR, HR>EFR, FR, FR>HR, FR>FR, FR>EFR, EFR, EFR>HR, EFR>FR, EFR>EFR. The legend includes CSELT:EP0, DTAG:EP0, CSELT:EP1, DTAG:EP1, CSELT:EP2, and DTAG:EP2.
+
+### Street noise added to speech (S/N = 15 dB)
+
+![Bar chart for EP0 showing Y/DMOS+CI scores for CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR. CNET is represented by blue bars and Nortel by maroon bars.](f85bf99d372e735d228361bf4d3cf7e6_img.jpg)
+
+**Y/DMOS+CI**
+
+**EP0**
+
+| Configuration | CNET | Nortel |
+|---------------|------|--------|
+| HR            | 3.6  | 3.5    |
+| HR->HR        | 2.5  | 2.6    |
+| HR->FR        | 3.2  | 3.3    |
+| HR->EFR       | 3.0  | 3.2    |
+| FR            | 4.1  | 3.7    |
+| FR->HR        | 3.1  | 3.0    |
+| FR->FR        | 3.7  | 3.3    |
+| FR->EFR       | 3.8  | 3.7    |
+| EFR           | 4.2  | 4.1    |
+| EFR->HR       | 3.4  | 3.3    |
+| EFR->FR       | 3.8  | 3.7    |
+| EFR->EFR      | 3.9  | 3.8    |
+
+Bar chart for EP0 showing Y/DMOS+CI scores for CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR. CNET is represented by blue bars and Nortel by maroon bars.
+
+![Bar chart for EP1 showing Y/DMOS+CI scores for CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR. CNET is represented by blue bars and Nortel by maroon bars.](c531b0e7e06671c980f2ed0d753d2fbc_img.jpg)
+
+**EP1**
+
+| Configuration | CNET | Nortel |
+|---------------|------|--------|
+| HR            | 3.6  | 3.3    |
+| HR->HR        | 2.1  | 2.4    |
+| HR->FR        | 2.6  | 2.6    |
+| HR->EFR       | 2.6  | 2.9    |
+| FR            | 3.8  | 3.5    |
+| FR->HR        | 2.6  | 2.6    |
+| FR->FR        | 3.1  | 2.9    |
+| FR->EFR       | 3.0  | 2.9    |
+| EFR           | 3.7  | 3.9    |
+| EFR->HR       | 2.8  | 2.8    |
+| EFR->FR       | 3.0  | 3.0    |
+| EFR->EFR      | 2.8  | 3.0    |
+
+Bar chart for EP1 showing Y/DMOS+CI scores for CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR. CNET is represented by blue bars and Nortel by maroon bars.
+
+![Bar chart for EP2 comparing CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR.](ebce355620876e10f907f8b71926c112_img.jpg)
+
+### EP2
+
+Legend: CNET (blue), Nortel (maroon)
+
+| Configuration | CNET | Nortel |
+|---------------|------|--------|
+| HR            | 3.4  | 2.9    |
+| HR->HR        | 1.8  | 1.8    |
+| HR->FR        | 2.0  | 2.1    |
+| HR->EFR       | 1.9  | 2.0    |
+| FR            | 3.2  | 2.9    |
+| FR->HR        | 1.9  | 1.8    |
+| FR->FR        | 2.1  | 2.2    |
+| FR->EFR       | 1.8  | 2.1    |
+| EFR           | 3.4  | 3.3    |
+| EFR->HR       | 2.0  | 2.1    |
+| EFR->FR       | 1.8  | 2.1    |
+| EFR->EFR      | 1.9  | 2.1    |
+
+Bar chart for EP2 comparing CNET and Nortel across various configurations. The y-axis ranges from 1 to 5. The x-axis labels are HR, HR->HR, HR->FR, HR->EFR, FR, FR->HR, FR->FR, FR->EFR, EFR, EFR->HR, EFR->FR, EFR->EFR.
+
+Vehicle noise added to speech (S/N = 10 dB)
+
+![Bar chart for EP0 comparing CSELT and DTAG across various configurations. The y-axis ranges from 1.00 to 5.00. The x-axis labels are HR, HR->FR, FR->HR, FR->EFR, EFR, EFR->FR.](723827e0738d2743c3b3423760a5c48e_img.jpg)
+
+### EP0
+
+Y/DMOS +CI
+
+Legend: CSELT (blue), DTAG (maroon)
+
+| Configuration | CSELT | DTAG |
+|---------------|-------|------|
+| HR            | 3.9   | 3.0  |
+| HR->FR        | 3.2   | 3.0  |
+| FR->HR        | 3.2   | 2.7  |
+| FR->EFR       | 4.1   | 3.1  |
+| EFR           | 4.7   | 3.8  |
+| EFR->FR       | 4.1   | 3.2  |
+
+Bar chart for EP0 comparing CSELT and DTAG across various configurations. The y-axis ranges from 1.00 to 5.00. The x-axis labels are HR, HR->FR, FR->HR, FR->EFR, EFR, EFR->FR.
+
+![Two bar charts showing Y/DMOS + CI scores for CSELT and DTAG techniques across different TFO conditions (HR, HR->FR, FR->HR, FR->EFR, EFR, EFR->FR) for EP1 and EP2 experiments. The Y-axis ranges from 1.00 to 5.00. In both charts, CSELT generally shows higher scores than DTAG, with the highest scores for CSELT in the EFR condition (approx. 4.5 for EP1 and 3.8 for EP2).](7f687094e6abe34a9cf491942b296d9a_img.jpg)
+
+**EP1**
+
+| Condition | CSELT | DTAG |
+|-----------|-------|------|
+| HR        | 3.7   | 3.0  |
+| HR->FR    | 3.0   | 2.4  |
+| FR->HR    | 3.8   | 3.4  |
+| FR->EFR   | 3.1   | 2.7  |
+| EFR       | 4.5   | 3.7  |
+| EFR->FR   | 3.2   | 2.8  |
+
+**EP2**
+
+| Condition | CSELT | DTAG |
+|-----------|-------|------|
+| HR        | 3.2   | 2.9  |
+| HR->FR    | 2.0   | 2.2  |
+| FR->HR    | 3.0   | 2.8  |
+| FR->EFR   | 2.1   | 2.1  |
+| EFR       | 3.8   | 3.2  |
+| EFR->FR   | 2.2   | 2.3  |
+
+Two bar charts showing Y/DMOS + CI scores for CSELT and DTAG techniques across different TFO conditions (HR, HR->FR, FR->HR, FR->EFR, EFR, EFR->FR) for EP1 and EP2 experiments. The Y-axis ranges from 1.00 to 5.00. In both charts, CSELT generally shows higher scores than DTAG, with the highest scores for CSELT in the EFR condition (approx. 4.5 for EP1 and 3.8 for EP2).
+
+## 7.4 Quality enhancement using TFO techniques
+
+The following table summarises the relevant results for the TFO conditions, i.e. the average improvement achievable with TFO technique (DMOS, **bold** means significant, NA stands for NOT APPLICABLE). Values were calculated using the Honestly Significant Difference (HSD) Tukey's test at the 95% significance level. The Table was derived from the experiments that used the flat input characteristics for recording speech.
+
+|     | EP0 | EP1 | EP2 |
+|-----|-----|-----|-----|
+| HR  | .85 | .68 | .39 |
+| FR  | .53 | NA  | NA  |
+| EFR | .32 | .46 | .19 |
+
+The following figures summarise the relevant results for the TFO conditions, i.e. the average improvement achievable with TFO technique. The figures was derived from the experiments that used the Modified IRS input characteristics for recording speech.
+
+EP1 Tandem TFO/No TFO
+
+![Bar chart showing EP1 Tandem TFO/No TFO results for HR, FR, and EFR codecs. The Y-axis represents Mean Opinion Score (MOS) from 0 to 4. For each codec, two bars are shown: a blue bar for 'No TFO' and a yellow bar for 'TFO'. For HR, the 'No TFO' bar is approximately 3.5 and the 'TFO' bar is approximately 2.8. For FR, the 'No TFO' bar is approximately 3.2 and the 'TFO' bar is approximately 2.8. For EFR, the 'No TFO' bar is approximately 4.0 and the 'TFO' bar is approximately 3.5.](50fecd0e7c9bf4ebf321d8367d42cc94_img.jpg)
+
+| Codec | No TFO (MOS) | TFO (MOS) |
+|-------|--------------|-----------|
+| HR    | ~3.5         | ~2.8      |
+| FR    | ~3.2         | ~2.8      |
+| EFR   | ~4.0         | ~3.5      |
+
+Bar chart showing EP1 Tandem TFO/No TFO results for HR, FR, and EFR codecs. The Y-axis represents Mean Opinion Score (MOS) from 0 to 4. For each codec, two bars are shown: a blue bar for 'No TFO' and a yellow bar for 'TFO'. For HR, the 'No TFO' bar is approximately 3.5 and the 'TFO' bar is approximately 2.8. For FR, the 'No TFO' bar is approximately 3.2 and the 'TFO' bar is approximately 2.8. For EFR, the 'No TFO' bar is approximately 4.0 and the 'TFO' bar is approximately 3.5.
+
+EP2 Tandem TFO/No TFO
+
+![Bar chart showing EP2 Tandem TFO/No TFO results for HR, FR, and EFR codecs. The Y-axis represents Mean Opinion Score (MOS) from 0 to 3. For each codec, two bars are shown: a blue bar for 'No TFO' and a yellow bar for 'TFO'. For HR, the 'No TFO' bar is approximately 2.6 and the 'TFO' bar is approximately 2.3. For FR, the 'No TFO' bar is approximately 2.1 and the 'TFO' bar is approximately 1.8. For EFR, the 'No TFO' bar is approximately 2.7 and the 'TFO' bar is approximately 2.4.](65a9654ccb3d0d452378b0f4c0c392f7_img.jpg)
+
+| Codec | No TFO (MOS) | TFO (MOS) |
+|-------|--------------|-----------|
+| HR    | ~2.6         | ~2.3      |
+| FR    | ~2.1         | ~1.8      |
+| EFR   | ~2.7         | ~2.4      |
+
+Bar chart showing EP2 Tandem TFO/No TFO results for HR, FR, and EFR codecs. The Y-axis represents Mean Opinion Score (MOS) from 0 to 3. For each codec, two bars are shown: a blue bar for 'No TFO' and a yellow bar for 'TFO'. For HR, the 'No TFO' bar is approximately 2.6 and the 'TFO' bar is approximately 2.3. For FR, the 'No TFO' bar is approximately 2.1 and the 'TFO' bar is approximately 1.8. For EFR, the 'No TFO' bar is approximately 2.7 and the 'TFO' bar is approximately 2.4.
+
+## 7.5 Effects of input frequency response
+
+The results show that the "Modified IRS" input frequency characteristic was slightly preferred to the "flat" one.
+
+# 8 Conclusion
+
+A number of experimental conditions for the performance characterisation of GSM interworking standards, including codecs in single, tandem, and tandem-free operation with and without errors, plus some MNRU conditions and Direct, have been tested subjectively.
+
+The present document summarised the subjective test results obtained by CNET, CSELT, DT AG and NORTEL.
+
+The similar or slightly lower quality behaviour showed by the FR codec in all conditions, in comparison with the HR codec, suggested to consider the analysis of results from previous exercises pertaining to those experimental conditions, and to undertake proper investigations on their reliability. Even if the results seem to be in line with the content of GSM 06.08, it is not advised to draw any conclusion on the relative performances of the HR and FR codecs from the limited test results contained in the present document. The HR characterization test results (GSM 06.08) provides a more complete picture of the HR performances in multiple environment. Specifically, GSM 06.08 shows that the HR is more sensitive than the GSM FR to the type of filtering (Modified IRS or Linear 'flat') used for the pre-processing of the speech samples (see subclause 6.1, table 3 of GSM 06.08).
+
+On grounds of the estimated Mean Opinion Scores, and considering the statistically significant differences among the simulated network configurations (computed using the Honestly Significant Difference (HSD) Tukey's test at the 95% significance level), the main positive results from this test are in general the rather good performance showed by the EFR and the quantification of improvement achievable by implementing the proposed TFO schemes, and by replacing the present FR by the EFR codec.
+
+For the HR-HR tandem and EP1, the TFO scheme showed a significant improvement of 0,7 MOS; the same significant improvement (0.7 MOS) was obtained by EFR codec for both error-free (EP0) and EP1 (C/I=10 dB) conditions.
+
+Based on the analysis of experimental results, the following conclusions can be drawn, in general, for speech mixed to street noise at SNR = 15 dB, or to vehicular noise at SNR = 10 dB:
+
+- 1) in single encoding, the Enhanced Full-Rate codec performs significantly better than the Full-Rate and Half-Rate codecs, respectively;
+- 2) in tandem encoding, for EP0 and EP1 error conditions (i.e. error-free and  $C/I=10$  dB), the ranking order EFR, FR and HR is still kept, with HR performance significantly worse, while differences between Full-Rate and Enhanced Full-Rate were in a few cases "statistically" NOT significant;
+- 3) In tandem encoding, for EP2 error conditions (i.e.  $C/I= 7$  dB), the performance differences between the codecs decline.
+
+# --- Annex A: Bibliography
+
+[1] **UIT-T Recommendation P.800:** " Methods for subjective determination of transmission quality", Rev. September 1995.
+
+[2] **UIT-T Recommendation P.830:** " Subjective performance assessment of telephone-band and wide band digital codecs", 1992.
+
+[3] **CCITT Recommendation P.810:** "Modulated Noise Reference Unit", Blue Book, Volume V, 1988 and proposed revisions (SG12 meeting, 1994).
+
+[4] **D.J. Finney** "Probit Analysis- A statistical analysis of the Sigmoid Response Curve", Cambridge University Press.
+
+[5] **R.E. Kirk** "Experimental Design: Procedures for the Behavioral Sciences", 2nd ed., Brooks/cole Publishing Co., California, 1982.
+
+# Annex B: Deliverables to ETSI
+
+Other Deliverables to ETSI from subjective tests on the interoperability HR/FR/EFR & TFO:
+
+| <b>Tdoc</b> | <b>SMG2-SEG</b>                                                                                                         | <b>Source</b>  |
+|-------------|-------------------------------------------------------------------------------------------------------------------------|----------------|
+| 34/96R      | Test plan for the evaluation of the interoperability HR-FR-EFR (Phase 1).                                               | CSELT          |
+| 92/96       | Evaluation of the interoperability HR-FR-EFR (Phase 1)                                                                  | STSG of SEG    |
+| 102/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: global analysis of results (Phase 1a of testing).             | CSELT          |
+| 103/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: (Phase 1a of testing). Results from CNET.                     | CNET           |
+| 104/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: (Phase 1a of testing). Results from CSELT.                    | CSELT          |
+| 105/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: (Phase 1a of testing). Results from DT AG.                    | DT AG          |
+| 106/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: (Phase 1a of testing). Results from NORTEL.                   | NORTEL         |
+| 107/96      | Subjective tests on the interoperability HR/FR/EFR & TFO: (Phase 1a of testing). Report of the host laboratory session. | MATRA          |
+| 127/96      | Demostration to SEG (Phase 1a)                                                                                          | MATRA          |
+| Tdoc        | SMG11                                                                                                                   |                |
+| 7/96        | Test results Phase 1b of testing                                                                                        | CSELT          |
+| 8/96        | Test results Phase 1b of testing                                                                                        | Nortel         |
+| 9/96        | Global analysis Phase 1b of testing                                                                                     | CSELT          |
+| 13/96 R2    | Test plan Phase 2 of testing                                                                                            | DT and FT/CNET |
+| 14/96       | Test results Phase 1b of testing                                                                                        | CNET           |
+| 17/96       | Host laboratory processing for the evaluation of HR/FR/EFR interoperability (Phase 1b)                                  | Matra          |
+| 18/96       | Demonstration tape to SMG11 (TFO Phase 1b of testing)                                                                   | Matra          |
+| 14/97       | Phase 2 of testing, report from CNET                                                                                    | CNET           |
+| 15/97       | Phase 2 of testing, report from CSELT                                                                                   | CSELT          |
+| 16/97       | Phase 2 of testing, report from DeTeBerkom                                                                              | DeTeBerkom     |
+| 17/97       | Phase 2 of testing, report from NORTEL                                                                                  | Nortel         |
+| 18/97       | Phase 2 of testing, report from host laboratory                                                                         | MATRA          |
+| 19/97       | Phase 2 of testing, global analysis                                                                                     | CSELT          |
+
+# Annex C: Phase 1: Tables of experimental results
+
+Phase 1 of testing: experimental conditions and results.
+
+| Condition | Error Pattern | Codec / Reference | M.O.S                    | Confidence Interval      |
+|-----------|---------------|-------------------|--------------------------|--------------------------|
+|           |               |                   | Male + Female<br>Talkers | Male + Female<br>Talkers |
+| 1         | EP0           | HR -> HR          | 3.15                     | 0.10                     |
+| 2         | EP0           | HR -> FR          | 3.03                     | 0.08                     |
+| 3         | EP0           | HR -> EFR         | 3.72                     | 0.08                     |
+| 4         | EP0           | FR -> HR          | 3.18                     | 0.08                     |
+| 5         | EP0           | FR -> FR          | 3.13                     | 0.08                     |
+| 6         | EP0           | FR -> EFR         | 3.79                     | 0.08                     |
+| 7         | EP0           | EFR -> HR         | 3.72                     | 0.08                     |
+| 8         | EP0           | EFR -> FR         | 3.60                     | 0.09                     |
+| 9         | EP0           | EFR -> EFR        | 4.29                     | 0.08                     |
+| 10        | EP1           | HR -> HR          | 2.77                     | 0.09                     |
+| 11        | EP1           | HR -> FR          | 2.59                     | 0.08                     |
+| 12        | EP1           | HR -> EFR         | 3.17                     | 0.09                     |
+| 13        | EP1           | FR -> HR          | 2.82                     | 0.09                     |
+| 14        | EP1           | FR -> FR          | 2.64                     | 0.09                     |
+| 15        | EP1           | FR -> EFR         | 3.03                     | 0.09                     |
+| 16        | EP1           | EFR -> HR         | 3.22                     | 0.09                     |
+| 17        | EP1           | EFR -> FR         | 2.89                     | 0.08                     |
+| 18        | EP1           | EFR -> EFR        | 3.45                     | 0.09                     |
+| 19        | EP2           | HR -> HR          | 2.24                     | 0.09                     |
+| 20        | EP2           | HR -> FR          | 1.85                     | 0.08                     |
+| 21        | EP2           | HR -> EFR         | 2.15                     | 0.09                     |
+| 22        | EP2           | FR -> HR          | 2.07                     | 0.08                     |
+| 23        | EP2           | FR -> FR          | 1.68                     | 0.08                     |
+| 24        | EP2           | FR -> EFR         | 2.15                     | 0.09                     |
+| 25        | EP2           | EFR -> HR         | 2.34                     | 0.09                     |
+|           |               |                   |                          |                          |
+
+(continued)
+
+## **Phase 1 of testing (concluded): experimental conditions and results.**
+
+| <b>Condition</b> | <b>Error Pattern</b> | <b>Codec / Reference</b> | <b>M.O.S</b> | <b>Confidence Interval</b> |
+|------------------|----------------------|--------------------------|--------------|----------------------------|
+| 26               | EP2                  | EFR -> FR                | 2.13         | 0.09                       |
+| 27               | EP2                  | EFR -> EFR               | 2.38         | 0.09                       |
+| 28               | EP1                  | HR -> HR TFO             | 3.46         | 0.09                       |
+| 29               | EP1                  | FR -> FR TFO             | 3.10         | 0.08                       |
+| 30               | EP1                  | EFR -> EFR TFO           | 3.87         | 0.08                       |
+| 31               | EP2                  | HR -> HR TFO             | 2.55         | 0.10                       |
+| 32               | EP2                  | FR -> FR TFO             | 2.03         | 0.09                       |
+| 33               | EP2                  | EFR -> EFR TFO           | 2.71         | 0.10                       |
+| 34               | EP0                  | HR                       | 3.85         | 0.08                       |
+| 35               | EP0                  | FR                       | 3.71         | 0.08                       |
+| 36               | EP0                  | EFR                      | 4.43         | 0.07                       |
+| 37               | EP1                  | HR                       | 3.68         | 0.08                       |
+| 38               | EP1                  | FR                       | 3.41         | 0.08                       |
+| 39               | EP1                  | EFR                      | 4.12         | 0.07                       |
+| 40               | EP2                  | HR                       | 3.30         | 0.09                       |
+| 41               | EP2                  | FR                       | 2.73         | 0.09                       |
+| 42               | EP2                  | EFR                      | 3.53         | 0.09                       |
+| 43               |                      | MNRU = 6 dB              | 1.26         | 0.06                       |
+| 44               |                      | MNRU = 12 dB             | 1.93         | 0.08                       |
+| 45               |                      | MNRU = 18 dB             | 3.03         | 0.08                       |
+| 46               |                      | MNRU = 24 dB             | 3.94         | 0.08                       |
+| 47               |                      | MNRU = 30 dB             | 4.35         | 0.07                       |
+| 48               |                      | Direct                   | 4.61         | 0.06                       |
+
+Analysis of Variance
+
+General Linear Models Procedure
+
+Number of observations in data set = 18432
+
+Dependent Variable: SCORE
+
+| Source          | DF    | Sum of Squares | Mean Square | F Value | Pr > F |
+|-----------------|-------|----------------|-------------|---------|--------|
+| Model           | 76    | 12655.81       | 166.52      | 261.80  | 0.0001 |
+| Error           | 18355 | 11674.99       | 0.63        |         |        |
+| Corrected Total | 18431 | 24330.81       |             |         |        |
+
+| R-Square | C.V.  | Root MSE | SCORE Mean |
+|----------|-------|----------|------------|
+| 0.52     | 26.08 | 0.80     | 3.06       |
+
+| Source           | DF | Type I SS | Mean Square | F Value | Pr > F |
+|------------------|----|-----------|-------------|---------|--------|
+| LAB              | 3  | 310.00    | 103.33      | 162.46  | 0.0001 |
+| COND             | 47 | 11153.85  | 237.31      | 373.10  | 0.0001 |
+| TALKER           | 3  | 352.45    | 117.48      | 184.70  | 0.0001 |
+| GROUP            | 2  | 82.13     | 41.06       | 64.56   | 0.0001 |
+| LISTENER (GROUP) | 21 | 757.38    | 36.07       | 56.70   | 0.0001 |
+
+General Linear Models Procedure
+
+Tukey's Studentized Range (HSD) Test for variable: SCORE
+
+NOTE: This test controls the type I experimentwise error rate, but generally has a higher type II error rate than REGWQ.
+
+Alpha= 0,05 df= 18355 MSE= 0.636
+
+Critical Value of Studentized Range = 5.62
+
+Minimum Significant Difference = 0.2287
+
+Means with the same letter are not significantly different.
+
+| Tukey Grouping |  |   |  | Mean | Condition No. | Condition Description |
+|----------------|--|---|--|------|---------------|-----------------------|
+|                |  | A |  | 4.61 | 48            | Direct                |
+| B              |  | A |  | 4.43 | 36            | EP0 EFR               |
+| B              |  |   |  | 4.35 | 47            | MNRU = 30 dB          |
+| B              |  | C |  | 4.29 | 9             | EP0 EFR-EFR           |
+| D              |  | C |  | 4.12 | 39            | EP1 EFR               |
+| D              |  | E |  | 3.94 | 46            | MNRU = 24 dB          |
+| F              |  | E |  | 3.87 | 30            | EP1 EFR-EFR TFO       |
+| F              |  | E |  | 3.85 | 34            | EP0 HR                |
+|                |  |   |  |      |               |                       |
+
+|
+
+(continued)
+
+|
+
+| Tukey Grouping |   |   |   | Mean | Condition No. | Condition Description |
+|----------------|---|---|---|------|---------------|-----------------------|
+| F              |   | E | G | 3.79 | 6             | EP0 FR-EFR            |
+| F              | H | E | G | 3.72 | 7             | EP0 EFR-HR            |
+| F              | H | E | G | 3.72 | 3             | EP0 HR-EFR            |
+| F              | H |   | G | 3.71 | 35            | EP0 FR                |
+| F              | H |   | G | 3.68 | 37            | EP1 HR                |
+|                | H | I | G | 3.60 | 8             | EP0 EFR-FR            |
+|                | H | I |   | 3.53 | 42            | EP2 EFR               |
+| J              |   | I |   | 3.46 | 28            | EP1 HR-HR TFO         |
+| J              |   | I | K | 3.45 | 18            | EP1 EFR-EFR           |
+| J              |   | I | K | 3.41 | 38            | EP1 FR                |
+| J              |   | L | K | 3.30 | 40            | EP2 HR                |
+| M              |   | L | K | 3.22 | 16            | EP1 EFR-HR            |
+| M              |   | L |   | 3.18 | 4             | EP0 FR-HR             |
+| M              |   | L |   | 3.17 | 12            | EP1 HR-FR             |
+| M              |   | L |   | 3.15 | 1             | EP0 HR-HR             |
+| M              |   | L |   | 3.13 | 5             | EP0 FR-FR             |
+| M              |   | L | N | 3.10 | 29            | EP1 FR-FR TFO         |
+| M              |   | O | N | 3.03 | 45            | MNRU = 18 dB          |
+| M              |   | O | N | 3.03 | 15            | EP1 FR-EFR            |
+| M              |   | O | N | 3.03 | 2             | EP0 HR-FR             |
+| P              |   | O | N | 2.89 | 17            | EP1 EFR-FR            |
+| P              |   | O | Q | 2.82 | 13            | EP1 FR-HR             |
+| P              |   | R | Q | 2.77 | 10            | EP1 HR-HR             |
+| P              |   | R | Q | 2.73 | 41            | EP2 FR                |
+| P              |   | R | Q | 2.71 | 33            | EP2 EFR-EFR TFO       |
+|                |   | R | Q | 2.64 | 14            | EP1 FR-FR             |
+| S              |   | R |   | 2.59 | 11            | EP1 HR-FR             |
+| S              |   | R | T | 2.55 | 31            | EP2 HR-HR TFO         |
+|                |   |   |   |      |               |                       |
+
+(continued)
+
+(concluded)
+
+| Tukey Grouping |   |   |   | Mean | Condition No. | Condition Description |
+|----------------|---|---|---|------|---------------|-----------------------|
+| S              |   | U | T | 2.38 | 27            | EP2 EFR-EFR           |
+| V              |   | U | T | 2.34 | 25            | EP2 EFR-HR            |
+| V              |   | U | W | 2.24 | 19            | EP2 HR-HR             |
+| V              | X | U | W | 2.15 | 24            | EP2 FR-EFR            |
+| V              | X |   | W | 2.15 | 21            | EP2 HR-EFR            |
+| V              | X |   | W | 2.13 | 26            | EP2 EFR-FR            |
+|                | X | Y | W | 2.07 | 22            | EP2 FR-HR             |
+|                | X | Y | W | 2.03 | 32            | EP2 FR-FR TFO         |
+|                | X | Y |   | 1.93 | 44            | MNRU = 12 dB          |
+| Z              |   | Y |   | 1.85 | 20            | EP2 HR-FR             |
+| Z              |   |   |   | 1.69 | 23            | EP2 FR-FR             |
+|                |   | A |   | 1.26 | 43            | MNRU = 6 dB           |
+
+# Annex D: Phase 2: Tables of experimental results
+
+**HR-FR-EFR Interoperability Phase 2 of testing:** Exp. 1 & 2 average results.
+
+| N  | Experimental condition | Street Noise | (CNET & Nortel) | Vehicle Noise | CSELT &    |
+|----|------------------------|--------------|-----------------|---------------|------------|
+|    |                        | SNR = 15 dB  |                 | SNR = 10 dB   | DeTeBerkom |
+|    |                        | DMOS         | C.I.            | DMOS          | C.I.       |
+| 1  | HR>HR_EP0_S+N          | 2.55         | 0.15            | 2.38          | 0.14       |
+| 2  | HR>FR_EP0_S+N          | 3.21         | 0.14            | 3.07          | 0.13       |
+| 3  | HR>EFR_EP0_S+N         | 3.07         | 0.15            | 3.03          | 0.14       |
+| 4  | FR>HR_EP0_S+N          | 3.03         | 0.14            | 2.95          | 0.14       |
+| 5  | FR>FR_EP0_S+N          | 3.52         | 0.13            | 3.34          | 0.14       |
+| 6  | FR>EFR_EP0_S+N         | 3.76         | 0.14            | 3.63          | 0.15       |
+| 7  | EFR>HR_EP0_S+N         | 3.33         | 0.16            | 3.14          | 0.15       |
+| 8  | EFR>FR_EP0_S+N         | 3.78         | 0.14            | 3.69          | 0.14       |
+| 9  | EFR>EFR_EP0_S+N        | 3.85         | 0.14            | 3.87          | 0.14       |
+| 10 | HR>HR_EP1_S+N          | 2.21         | 0.14            | 2.12          | 0.14       |
+| 11 | HR>FR_EP1_S+N          | 2.60         | 0.14            | 2.69          | 0.15       |
+| 12 | HR>EFR_EP1_S+N         | 2.70         | 0.15            | 2.71          | 0.15       |
+| 13 | FR>HR_EP1_S+N          | 2.57         | 0.15            | 2.53          | 0.15       |
+| 14 | FR>FR_EP1_S+N          | 2.96         | 0.15            | 2.82          | 0.14       |
+| 15 | FR>EFR_EP1_S+N         | 2.95         | 0.14            | 2.91          | 0.15       |
+| 16 | EFR>HR_EP1_S+N         | 2.76         | 0.15            | 2.64          | 0.14       |
+| 17 | EFR>FR_EP1_S+N         | 2.98         | 0.15            | 3.00          | 0.14       |
+| 18 | EFR>EFR_EP1_S+N        | 2.85         | 0.15            | 3.19          | 0.14       |
+| 19 | HR>HR_EP2_S+N          | 1.83         | 0.14            | 1.76          | 0.14       |
+| 20 | HR>FR_EP2_S+N          | 2.04         | 0.15            | 2.07          | 0.16       |
+| 21 | HR>EFR_EP2_S+N         | 1.93         | 0.14            | 1.93          | 0.15       |
+| 22 | FR>HR_EP2_S+N          | 1.91         | 0.14            | 1.85          | 0.15       |
+| 23 | FR>FR_EP2_S+N          | 2.21         | 0.15            | 2.10          | 0.15       |
+| 24 | FR>EFR_EP2_S+N         | 2.00         | 0.15            | 1.96          | 0.15       |
+| 25 | EFR>HR_EP2_S+N         | 2.04         | 0.13            | 1.90          | 0.14       |
+
+(continued)
+
+## **HR-FR-EFR Interoperability Phase 2 of testing (concluded): Exp. 1 & 2 average results.**
+
+| <b>N</b> | <b>Experimental condition</b> | <b>Street Noise<br/>SNR = 15 dB</b> | <b>(CNET &amp; Nortel)</b> | <b>Vehicle Noise<br/>SNR = 10 dB</b> | <b>CSELT &amp;<br/>DeTeBerkom</b> |
+|----------|-------------------------------|-------------------------------------|----------------------------|--------------------------------------|-----------------------------------|
+| 26       | EFR>FR_EP2_S+N                | 1.96                                | 0.14                       | 2.23                                 | 0.15                              |
+| 27       | EFR>EFR_EP2_S+N               | 2.00                                | 0.15                       | 1.95                                 | 0.14                              |
+| 28       | HR_EP0_S+N                    | 3.56                                | 0.14                       | 3.45                                 | 0.15                              |
+| 29       | HR_EP1_S+N                    | 3.51                                | 0.15                       | 3.32                                 | 0.14                              |
+| 30       | HR_EP2_S+N                    | 3.16                                | 0.14                       | 3.04                                 | 0.15                              |
+| 31       | FR_EP0_S+N                    | 3.92                                | 0.14                       | 3.83                                 | 0.14                              |
+| 32       | FR_EP1_S+N                    | 3.67                                | 0.14                       | 3.58                                 | 0.14                              |
+| 33       | FR_EP2_S+N                    | 3.04                                | 0.14                       | 2.85                                 | 0.13                              |
+| 34       | EFR_EP0_S+N                   | 4.18                                | 0.13                       | 4.25                                 | 0.14                              |
+| 35       | EFR_EP1_S+N                   | 3.79                                | 0.15                       | 4.08                                 | 0.13                              |
+| 36       | EFR_EP2_S+N                   | 3.32                                | 0.16                       | 3.49                                 | 0.15                              |
+| 37       | MNRU=6dB                      | 1.59                                | 0.12                       | 1.81                                 | 0.12                              |
+| 38       | MNRU=12dB                     | 2.92                                | 0.14                       | 3.12                                 | 0.12                              |
+| 39       | MNRU=18dB                     | 4.08                                | 0.11                       | 4.07                                 | 0.11                              |
+| 40       | MNRU=24dB                     | 4.66                                | 0.10                       | 4.70                                 | 0.07                              |
+| 41       | MNRU=30dB                     | 4.76                                | 0.10                       | 4.77                                 | 0.06                              |
+| 42       | Direct,clean                  | 4.81                                | 0.09                       | 4.81                                 | 0.06                              |
+| 43       | Direct+Noise                  | 4.35                                | 0.12                       | 4.42                                 | 0.12                              |
+
+# Annex E: Change history
+
+| Change history |           |         |                  |             |                      |
+|----------------|-----------|---------|------------------|-------------|----------------------|
+| SMG No.        | TDoc. No. | CR. No. | Section affected | New version | Subject/Comments     |
+| SMG#26         |           |         |                  | 5.0.0       | Phase 2+ version     |
+| SMG#27         |           |         |                  | 6.0.0       | Release 1997 version |
+| SMG#29         |           |         |                  | 7.0.0       | Release 1998 version |
+| SMG#31         |           |         |                  | 8.0.0       | Release 1999 version |
+
+| Change history |       |          |    |     |                        |        |        |  |
+|----------------|-------|----------|----|-----|------------------------|--------|--------|--|
+| Date           | TSG # | TSG Doc. | CR | Rev | Subject/Comment        | Old    | New    |  |
+| 03-2001        | 11    |          |    |     | Version for Release 4  |        | 4.0.0  |  |
+| 06-2002        | 16    |          |    |     | Version for Release 5  | 4.0.0  | 5.0.0  |  |
+| 12-2004        | 26    |          |    |     | Version for Release 6  | 5.0.0  | 6.0.0  |  |
+| 06-2007        | 36    |          |    |     | Version for Release 7  | 6.0.0  | 7.0.0  |  |
+| 12-2008        | 42    |          |    |     | Version for Release 8  | 7.0.0  | 8.0.0  |  |
+| 12-2009        | 46    |          |    |     | Version for Release 9  | 8.0.0  | 9.0.0  |  |
+| 03-2011        | 51    |          |    |     | Version for Release 10 | 9.0.0  | 10.0.0 |  |
+| 09-2012        | 57    |          |    |     | Version for Release 11 | 10.0.0 | 11.0.0 |  |
+| 09-2014        | 65    |          |    |     | Version for Release 12 | 11.0.0 | 12.0.0 |  |
+| 12-2015        | 70    |          |    |     | Version for Release 13 | 12.0.0 | 13.0.0 |  |
+
+| Change history |         |      |    |     |     |                                |               |  |
+|----------------|---------|------|----|-----|-----|--------------------------------|---------------|--|
+| Date           | Meeting | TDoc | CR | Rev | Cat | Subject/Comment                | New version   |  |
+| 03-2017        | SA#75   |      |    |     |     | Version for Release 14         | 14.0.0        |  |
+| 06-2018        | SA#80   |      |    |     |     | Version for Release 15         | 15.0.0        |  |
+| 2020-07        | -       | -    | -  | -   | -   | Update to Rel-16 version (MCC) | <b>16.0.0</b> |  |
\ No newline at end of file